UDB banner

Serial Y Cable Pinout
Memory Configuration
Cache Configuration
SROM LED Codes
Firmware updates
Jumper settings
Spares Part Numbers
NETWORK TROUBLESHOOTING
The UDB contains two console firmware systems. The ARC console supports the WindowsNT and Linux operating systems, and the SRM console is used for diagnostics. After completing these diagnostic tests be sure to return to the ARC console by entering ARC at the SRM prompt.

The most common network problem is the inability to access the ethernet, in which case the following procedure should be followed.

  1. Enter the SRM console by selecting the following option from the main ARC menu. Select either non-WindowsNT option from the subsequent menu, and follow the power cycle instructions. 
    Switch to OpenVMS or Digital UNIX console
  2. At the >>> prompt, enter SHOW DEVICE, you should see the following display 
    dka0.0.6.0     DKA0  DEC RZ26F
dva0.0.0.0.1   DVA0
ewa0.0.0.11.0  EWA0   08-00-2B-12-34-56
pka0.7.0.6.0   PKA0   SCSI Bus ID 7
  3. If EWA0 is not in the list of devices replace the system board, otherwise when EWA0 is in the list of devices, install Twisted Pair, Thinwire and AUI loopback connectors, then enter the following commands 
    >>> SET EWA0_MODE TWISTED
>>> TUNET
  4. Wait 30 seconds, if a failure occurs replace the system board, otherwise proceed with the steps below
  5. Enter the following command 
    >>> SET EWA0_MODE AUI
  6. Wait 30 seconds, if a failure occurs replace the system board, otherwise continue
  7. Enter the following command 
    SET EWA0_MODE THIN
  8. Wait 30 seconds, if a failure occurs replace the system board, otherwise continue
  9. Enter the following command, CAUTION, be sure to perform this step, if EWA0_MODE is not set back to AUTO all future UDB functions will fail 
    >>> SET EWA0_MODE AUTO
  10. Power down the UDB system
  11. Remove loopback connectors
  12. Connect the UDB to your network
  13. Power up the UDB
  14. At the >>> prompt, enter the following command 
    >>> TUNET
  15. Wait 30 seconds, if a failure occurs it is due to a problem with the building network, or the cable between the UDB systems and the building network. Should no failure occur the network is operating properly