C
8
H A P T E R
Troubleshooting
This section contains information that may help you solve problems you may experience
with your inline mode deployment.
Verify that traffic is flowing through the Sensor
For any inline Sensor, you can look at the statistics for each Sensor port to confirm that
traffic is properly flowing through it, by launching the Threat Analyzer.
Note:
For step-by-step procedures on verifying how to verify traffic is flowing
through the Sensor, see the
Verify failover pair creation success
If you have configured a failover pair prior to cabling the heartbeat connection, you will
notice Failover peer status errors appearing on the
the heartbeat connection. These messages will not appear if the two communicate
properly.
The status of the communication between the Sensors can be monitored on the
View Details
page of the Manager interface or directly from the CLI of either Sensor.
The Network Security Sensor command line interface (CLI) is a valuable tool for verifying
correct configuration as well as diagnosing possible problems.
Note:
See full list of Sensor CLI commands in the
show
Shows all of the current configuration settings on the Sensor. You can use the show
command to verify information such as the Sensor's management port IP address, the
version of software currently running, McAfee
address, and the gateway IP address that connect the Sensor to the Manager.
status
Shows Sensor system status, such as Operational Status, total number of alerts detected,
and total number of alerts sent to the Manager. The status command is useful for verifying
that trust has been established between the Sensor and the Manager, and for verifying the
Sensor is detecting attacks and sending alerts to the Manager.
System Status Monitoring Guide
.
Operational Status
CLI Guide.
®
Network Security Manager's (Manager's) IP
21
page until you cable
Sensors >