Article Title : VMS Troubleshooting Creation Date : 06/14/94 Message ID : JGRNSQ Last Update : Expiration Rules : unknown Location : NCD-Articles/Host_Systems/VMS ================================================================= Common NCDware Trouble Shooting Q & A for (OPEN)VMS and DECnet -------------------------------------------------------------- +====================================+ || Standard questions to always ask || +====================================+ It is very important to have this basic background information in order to trouble shoot the problem. Q: What model NCD is it? Q: What version of NCDware is it? Q: What version of the boot prom is it? Q: How much memory is in the NCD? Q: What kind of network and ethernet taps are being used? Q: What version of (OPEN)VMS is installed on the host? Q: What window manger is used: NCDwm, DECwindows MWM, etc? Q: Is it DECwindowns Motif or DECwindowns XUI on the host? Q: What kind of host is it: VAX 4000, Alpha, cluster member, stand alone, etc? Q: What is the history: new install, used to work, others still work, etc? Q: What exactly is the problem in detail? +=====================================+ || Problem specific questions to ask || +=====================================+ The problems below are listed in the order that they may happen in the NCD unit boot sequence. It is very important to solve the first error seen because the later errors may often be a result of the first. +============================+ || PROBLEM: VMSINSTAL fails || +============================+ Q: Was VMSINSTAL used (by miskake) to copy the save sets to disk before the install? A: As described in the NCD documentation, the VMS copy command must be used. Q: Was the install logged to a file? A: Ask the customer to use this command to log the install to a file: $ SET HOST 0 /LOG=NCD.LOG Q: What was the error message when the install failed? A: Ask the customer for the error message. +==============================+ || PROBLEM: NCD will not boot || +==============================+ Q: Do the external/internal ethernet loopback tests from the boot monitor pass on the NCD? A: Ask the customer to try these tests. Q: Does the host log the NCD unit's MOP requests? A: Ask the user to do this on the host: $ REPLY/ENABLE=NETWORK A: If this fails, check the network connection again. A: If this fails, make sure DECnet network logging is enabled: $ mc ncp show log monitor $ mc ncp set log monitor event 0.0-9 $ mc ncp set log monitor state on Q: What is the MOP request message on the host? A: Ask the customer for the MOP log message. A: Find out if it is a protection or file not found error and fix it. Q: Does the ethernet address for the request match that found in ncdconfig and NCP? A: Run ncdconfig and list the NCD units. A: Do: $ mc ncp show node YourNCDname char Q: Does the ncdconfig entry have all the correct load file information? A: Make sure ncdconfig is set to down load the correct server and not set to in prom. Q: Was MOP down loading disabled on the host? A: Check with the customer to see if MOP has been disabled. A: Start ncdconfig to have it check that network services are enabled. Q: Is the NCD's node name or DECnet number in use by another host? A: Use ncdconfig to try another name and number that are known to be available. +=============================================+ || PROBLEM: Remote config file does not load || +=============================================+ Q: What are the messages in the NCD diagnostics? A: Enable extended diagnostics, save to NVRAM, reboot, and read the error. Q: Does sys$manager:sylogin.com have the correct privs? A: Do $ dir/prot sys$manager:sylogin.com to make sure they are world read and execute. A: Use $ set file/prot=w:re sys$manager:sylogin.com, to fix the wrong protections. Q: Does sys$manager:sylogin.com have the NCD recommended changes for set term, or is there some other logic problem in it? A: Try making the first line of sylogin.com "$EXIT", and then reboot the NCD. Q: Is the correct NCDnet key ( needed before 3.2) being used? A: Check the licensed features menu and input the key to test it. Q: Is the NCD_NDS proxy correct? A: Compare the one on the host with this: $ set def sys$system $ run authorize UAF> sh /proxy *nds* Default proxies are flagged with (D) *::NCD_NDS UAF> sh /proxy *nds* Q: Is the NCD_NDS account correct? A: Compare the one on the host with the one in the AUG. $ set def sys$system UAF> sh *nds* Q: Has the NCD_NDS account been tested on the host? A: Here is how to test it: 1. Login as SYSTEM 2. $ SET DEF SYS$SYSTEM 3. $ RUN AUTHORIZE 4. UAF> SHOW/PROXY *NCD* Default proxies are flagged with (D) *::NCD_NDS NCD_NDS (D) 5. UAF> ADD/PROXY *::RICK NCD_NDS /DEF 6. UAF> EXIT 7. SET HOST 0 8. Login as RICK 9. DIR/PROT NCDVAX::NCD_ROOT:[CONFIGS] 10. DIR/PROT NCDVAX::NCD_ROOT:[CONFIGS]01_0381.DAT 11. TYPE NCDVAX::NCD_ROOT:[CONFIGS]01_0381.DAT Please use the actual name of the customer's test account in place of RICK, the name of the customer's VAX in place of NCDVAX, and the name of the customer's NCD config file in place of the 01_0381.DAT file. If the DIR and TYPE commands do not work, please check to see that SYLOGIN.COM, file protections, and the ncd_nds account are correct. ++=====================================+ || PROBLEM: DECwindows does not start || +======================================+ Q: Is XDM (for 3.x) running? A: Do $ show system/out=sys.t $ search sys.t xdm $ del sys.t;0 A: Use ncdconfig to start xdm and then reboot the NCD unit. Q: Does a CTERM login start the DECWindows log box? A: Start a CTERM and login to this account: nds_login Q: Does sys$manager:sylogin.com have the correct privs? A: Do $ dir/prot sys$manager:sylogin.com to make sure they are world read and execute. A: Use $ set file/prot=w:re sys$manager:sylogin.com, to fix the wrong protections. Q: Does sys$manager:sylogin.com have the NCD recommended changes for set term, or is there some other logic problem in it? A: Try making the first line of sylogin.com "$EXIT", and then reboot the NCD. Q: What messages are in the DECW$SM.LOG file? A: Have the customer check out the sys$login:DECW$SM.LOG file. Q: Can a DECwindows application be started by hand? A: Try the following: Make an LAT or CTERM connection to the host, login, then do $ set display/creat/node=NCDname $ create/term $ set def sys$system $ run DECW$CLOCK Q: Is there a font problem? A: Turn on extended file diags and font diags to verify there is no problem. +===========================================+ || PROBLEM: DECwindows performance is slow || +===========================================+ Q: Have the recommended AUM sysgen changes been made? A: DECwindows requires this to be done. Q: Is autogen being run with feedback regularly? A: DECwindows can drastically change the host load. Q: Have the recommended DECnet changes been made in NCP? A: Show the customer these changes in the AUG and ask them to be made.