114Appendix B: EIU troubleshooting
Tools
Table 29 summarizes the tools available for troubleshooting the EIU.
Table 29 Tools for EIU troubleshooting
Tool name | Resident | Description |
|
|
|
IPOMSCI | Y | monitors internal operational measurements (OM) |
|
| generated by the different layers of Internet |
|
| Protocol stack (for example |
|
| • transmission control protocol (TCP) |
|
| • Internet Protocol (IP) |
|
| • Internet control message protocol (ICMP) |
|
| • address resolution protocol (ARP) |
|
| • SuperNode access protocol (SNAP) |
|
|
|
IPRTRACE | Y | monitors and displays the intermediate paths taken |
|
| by the IP packets (generated by SuperNode) to |
|
| their destinations. |
|
|
|
NETMAN | Y | displays information on TCP and user datagram |
|
| protocol (UDP) connections |
|
|
|
SNPINGCI | Y | use to ping remote IP nodes for checking |
|
| serviceability of these remote nodes |
|
|
|
For more information on these tools, refer to Commands Reference Manual,
Troubleshooting checklist
Much of the troubleshooting required for the EIU is handled at the frame, shelf, and software load levels. There are, however, some problems that operating company personnel can troubleshoot at the EIU level.
Table 30 lists the problems that the operating company and customers can encounter. The table also lists probable causes, referenced to the list at the end of the table.
Table 30 EIU troubleshooting checklist
Problem | Probable cause |
|
|
Cannot ping any | 1, 2, 3, 4, 5 |
node or vice versa |
|
|
|
Can ping to a | 4 |
TCP connection |
|
|
|
(Sheet 1 of 2) |
|
|
|