TRIP 10004
MESSAGE
Missed more than # pings from TMS Chs/Slt chassis / BPS -
restarting
SEVERITY
9
POSSIBLE CAUSE
TRIP is in the ‘controlling’ state and it failed to communicate with the TMS. Possible
reasons are:
1. Network link failure between Avaya MPS and TMS
2. TMS failure
ACTION
The component will automatically be restarted and attempt to reconnect to the TMS. If
the reconnect fails:
1. Check the network connections (switches and cables) between the TMS
and Application Processor. Use the ping command to check if the TMS is
reachable from AP.
2. If the TMS cannot boot, use a terminal connected to the TMS serial port
to check TMS settings. If the TMS boot method is set to FIXED (as
shown in a tip window), check that TMS IP address, boot server IP
address, and the name of boot file is correct. If the TMS boot method is
set to BOOTP, check that the boot server has correct entries in the
bootptab file (Solaris: /etc/bootptab, Windows:
\WINNT\system32\drivers\etc\bootptab ). Check that TMS
boot file (e.g., tms_860.smod) exists on the boot server.
Contact technical support if the system does not recover after performing the above.
Kommentare zu diesen Handbüchern