
GeoTel Features User Manual NCD Alarm Messages
P0602482 Ver. 04.03 Avaya Page 443
TMS Initialization
Failed TMS bootup usually prevents the rest of the system from starting up properly.
To diagnose possible TMS initialization problems:
• Verify the bootp file entries. Look for invalid/conflicting MAC and IP
addresses.
• Verify that the TMS images are valid and available.
• Verify that the NIC (or hub-NIC) is installed properly (seated in the
backplane) and booted properly.
• Verify that all cables are connected and secure.
•Use the ping command from a separate system to verify TMS network
connections.
• Use a separate console hookup to further investigate the source of the TMS
initialization failure.
TMS Health Check
The TMS must establish a health check with the NIC within 5 minutes of entering the
booting state. If the TMS cannot establish a health check in that time, the NIC
assumes that the TMS has failed. A health check failure may be caused by a power
cycle or a reset command sent to the TMS. To diagnose possible TMS health check
problems:
• Verify that all cables are connected and secure.
• Verify that power is being delivered to all system components.
• Verify that the TMS configuration is correct and valid for the system (see
tms.cfg). Note that a TMS configuration may be syntactically valid but not
possible on the system because the TMS cannot support the requested
resources.
• Verify that there are no network problems (bad switch/hub, IP conflicts, etc.).
• Verify that the NIC is up and running.
• Check the system alarm logs for evidence of a TMS reset command.
Komentáře k této Příručce