Table of Contents
Advertisement
Appendix B
Troubleshooting
Cannot Access the Sensor Through the IDM or Telnet and/or SSH
Step 1
Step 2
Step 3
Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
78-15597-02
If you cannot access the sensor through the IDM or through Telnet and/or SSH,
follow these steps:
Ping the sensor's IP address:
The ping fails. Go to Step 2.
•
sensor# ping 10.89.149.81
PING 10.89.149.81 (10.89.149.81) from 10.89.149.56 : 56(84) bytes
of data.
From 10.89.149.56 icmp_seq=1 Destination Host Unreachable
From 10.89.149.56 icmp_seq=2 Destination Host Unreachable
From 10.89.149.56 icmp_seq=3 Destination Host Unreachable
—- 10.89.149.81 ping statistics —-
3 packets transmitted, 0 received, +3 errors, 100% loss, time
2013ms , pipe 3
•
The ping succeeds. Go to Step 4.
sensor# ping 10.89.149.81
PING 10.89.149.81 (10.89.149.81) from 10.89.149.110 : 56(84) bytes
of data.
64 bytes from 10.89.149.81: icmp_seq=1 ttl=254 time=0.273 ms
64 bytes from 10.89.149.81: icmp_seq=2 ttl=254 time=0.176 ms
64 bytes from 10.89.149.81: icmp_seq=3 ttl=254 time=0.178 ms
64 bytes from 10.89.149.81: icmp_seq=4 ttl=254 time=0.187 ms
—- 10.89.149.81 ping statistics —-
4 packets transmitted, 4 received, 0% loss, time 3001ms rtt
min/avg/max/mdev = 0.176/0.203/0.273/0.042 ms
Run a trace route to the sensor to find out where the route is broken.
sensor# traceroute to 172.21.172.24 (172.21.172.24), 30 hops max, 40
byte packets 1 171.69.162.2 (171.69.162.2) 1.25 ms 1.37 ms 1.58 ms 2
172.21.172.24 (172.21.172.24) 0.77 ms 0.66 ms 0.68 ms
sensor#
Make sure the sensor's IP address and default gateway are set correctly. Make sure
the router, switch, and/or the firewall are configured to interface with the sensor.
sensor# setup
—- System Configuration Dialog —-
At any point you may enter a question mark '?' for help.
Troubleshooting the 4200 Series Appliance
B-5
Advertisement
Table of Contents
Troubleshooting
