status

This command displays Sensor system status, such as System Health, Manager communication, signature set details, total number of alerts detected, and total number of alerts sent to the Manager.

This command has no parameters.

Syntax:

status

Sample Output:

For Sensor, the output is as shown below:

intruShell@john> status

[Sensor]

System Initialized : yes

System Health Status : good

Layer 2 Status : normal (IDS/IPS)

Installation Status : complete

IPv6 Status : Parse and Detect Attacks

Reboot Status : Not Required

Guest Portal Status : up

Hitless Reboot : Not-Available

Last Reboot reason : reboot issued from CLI

[Signature Status]

Present : yes

Version : 8.6.0.6

Power up signature : good

Geo Location database : Present

DAT file : Present

Version : 318.0

[Manager Communications]

Trust Established : yes (RSA 1024-bit or 2048-bit)

Alert Channel : up

Log Channel : up

Authentication Channel : up

Last Error : None

Alerts Sent : 961

Logs Sent : 974

[Alerts Detected]

Signature : 4246 Alerts Suppressed : 3483

Scan : 0 Denial of Service : 2

Malware : 0

[NTBA Communication]

Status : up

IP : 10.213.174.132

Port : 8505

[MATD Communication]

Status : up

IP : 10.213.174.134

Port : 8506

The same status message appears in an NTBA Appliance also.

Note

In NS9300 Sensor, if the Sensor reboots due to mismatch in software version, the status command specifies the reason recovered from sw version mismatch in Last Reboot reason.

Note

For NS9500 and NS3500 Sensors, the status command also displays the current throughput based on the license purchased. If signature set is not detected in the Sensor, No license is displayed.

Note

If there is a failure in establishing trust between the Sensor and Manager due to mismatch in shared secret key, the Last Error displays the message Alert Channel - Install Keys Mismatch. In such an instance, check the shared secret key on the Manager and set it on the Sensor using set sensor sharedsecretkey command.

Applicable to:

NS-series Sensors