TMS zl Management and Configuration Guide ST.1.1.100430

10-121
Troubleshooting
Troubleshooting the TMS zl Module in Routing Mode
10. Verify that the participant can access the external server. For example:
hostswitch(tms-module-C)# ping 172.16.40.10
PING 172.16.40.10 (172.16.40.10) 32(60) bytes of data.
40 bytes from 172.16.40.10: icmp_seq=1 ttl=64
time=4.88 ms 40 bytes from 172.16.40.10: icmp_seq=2
ttl=64 time=0.121 ms 40 bytes from 172.16.40.10:
icmp_seq=3 ttl=64 time=0.102 ms 40 bytes from
172.16.40.10: icmp_seq=4 ttl=64 time=0.107 ms
--- 172.16.40.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time
3004ms rtt min/avg/max/mdev = 0.102/1.303/4.884/2.067
ms
11. You can now take a snapshot (if needed for troubleshooting a problem).
hostswitch(tms-module-C)# snapshot
Starting to capture the system snapshot...
Gathering Summary information
Gathering Kernel information
Gathering Hardware information
Gathering Log-Files information
Gathering Software information
Gathering File-Systems information
Gathering Network information
Gathering Services information
Gathering Stats information
Gathering Misc-Files information
Gathering TMS information
Gathering Third-Party-SW information
Successfully captured the system snapshot for trouble-
shooting purpose.
The snapshot file size: 2098133
12. Copy the snaphot to an external server (such as an SCP server). HP
recommends that this external host is in the VLAN you created on the
participant. Otherwise, you must add static routes to reach it and then
delete those static routes after you have copied the file to the external
server.