Communication Problems; Cannot Access The Sensor Cli Through Telnet Or Ssh - Cisco 4215 - Intrusion Detection Sys Sensor Configuration Manual

Troubleshooting the 4200 Series Appliance
This section contains the following topics:
•
•
•
•
•
•
•

Communication Problems

This section helps you troubleshoot communication problems with the 4200 series sensor. It contains the
following topics:
•
•
•

Cannot Access the Sensor CLI Through Telnet or SSH

If you cannot access the sensor CLI through Telnet (if you already have it enabled) or SSH, follow these
steps:
For the procedure for enabling and disabling Telnet on the sensor, see
Note
page
Log in to the sensor CLI through a console, terminal, or module session.
Step 1
For the various ways to open a CLI session directly on the sensor, see
Sensor."
Make sure that the sensor's management interface is enabled:
Step 2
sensor# show interfaces
Interface Statistics
Total Packets Received = 0
Total Bytes Received = 0
Missed Packet Percentage = 0
Current Bypass Mode = Auto_off
MAC statistics from interface GigabitEthernet0/1
Media Type = backplane
Missed Packet Percentage = 0
Inline Mode = Unpaired
Pair Status = N/A
Link Status = Up
Link Speed = Auto_1000
Link Duplex = Auto_Full
Total Packets Received = 0
Total Bytes Received = 0
Total Multicast Packets Received = 0
Total Broadcast Packets Received = 0
Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 5.0
C-4
Communication Problems, page C-4
SensorApp and Alerting, page C-8
Blocking, page C-15
Logging, page C-23
Verifying the Sensor is Synchronized with the NTP Server, page C-29
TCP Reset Not Occurring for a Signature, page C-29
Software Upgrades, page C-31
Cannot Access the Sensor CLI Through Telnet or SSH, page C-4
Misconfigured Access List, page C-6
Duplicate IP Address Shuts Interface Down, page C-7
4-4.
Appendix C Troubleshooting
Enabling and Disabling Telnet,
Chapter 2, "Logging In to the
78-16527-01