From ASD Wiki

Bringing Up All Systems

Cheat Sheet

1. MSA1000 must be brought up first, if given the opportunity. If not, make sure that ASDFIBRE comes up after MSA1000. For instance, tonight I had to reset ASDFIBRE because MSA1000 didn't come up before ASDFIBRE, and therefore FIBRE couldn't see it.
2. If clustered servers came up at the same time or before MSA1000, you will probably have to unload Clustered Services on each machine (ASDAPPS1, ASDAPPS2 & ASDTEMP) with the command ULDNCS and bring it back up again (AFTER MSA1000 and ASDFIBRE are up!!) with LDNCS. If they still don't see the shared storage, you will probably need to make sure that ion.ncf has been activated. If not, you will probably want to use ioff.ncf first to make sure the connection hasn't been made. CAUTION, don't use ioff.ncf before running ULDNCS, or you will drop in a poison pill and abend the server.
3. Check VMHOST and make sure that appropriate VMs are running.
4. Inside VMHOST, make sure that Compass server has started properly.
5. Make sure ASDPRINT has started up. Most likely, you will need to select DISTRICT and the print manager to get NDPS Manager to start properly. Once you start it, make sure the printer agents come alive.
6. Make sure MAIL1 and MAILUX have started. MAIL1 will autostart, but as of this writing, you will still need to start up MAILUX's Linux MTA. This can be accomplished by logging in to MAILUX and move to superuser at the console. Change directory to /opt/novell/groupwise/agents/bin and run the command "./gwmta @strtupus.mta &". This *should* start up the MTA. The GWIA will start as a function of the GRPWISE daemon in /etc/init.d. You should also startup the script "gwmon &" This will start up groupwise monitor which you can reach here.
7. Make sure ASDCAFE and ASDTERM have started up
8. By now, you should be able to check Clustered Services. Use ConsoleOne and click on "CL1.District". Once selected, choose VIEW from the pull-down and choose "Cluster State View". This will show you what services are running on which servers. For instance, currently, all volumes and services are running on ASDAPPS1, which is a bad thing. More on what should be running where, here: Nerd:Cluster.
9. Check eDirectory and make sure it doesn't need help resyncing. Info Here
10. Make sure the Helpdesk server is up
11. Check SLPDA services. At ASDCOMM, type "DISPLAY SLP INFO". This will show the DA's and if they are running. If they aren't, type "SLPDA" at the consoles of AHSSERV1 and ASDCOMM. Reset SLP by typing "SET SLP RESET=ON" at ASDCOMM. Displaying SLP info again should list the SLPDA's now. This is a must if you want the clients to find the tree when logging in.
12. DHCP services is running on ASDPRINT now. Make sure that you can get a DHCP address (with pxe or whatever). If you can't, start the server. Info Here
13. Check ASDSQUID and make sure the squid service is running. The fastest way is to change to superuser at the console and type "/etc/init.d/squid status". This should return whether squid is up or down. The longer, GUI way is to from root console type "yast". Choose System > System Services (runlevel) and scroll down to the squid service and make sure it has a "Yes" in the Enabled column.
14. Check ASDBLOG (small workstation above KVM #2) and make sure it's running.
15. Check ASDVMHOST (lower center rack) and make sure all appropriate VM's are running.