Cisco Cisco IPS 4255 Sensor

application-data is using 36.5M out of 166.8M bytes of available disk space (23% usage)

boot is using 39.4M out of 68.6M bytes of available disk space (61% usage)

MainApp          2005_Feb_18_03.00   (Release)   2008-02-18T03:13:47-0600   Running   

AnalysisEngine   2005_Feb_15_03.00   (Release)   2008-02-15T12:59:35-0600   Running   

CLI              2005_Feb_18_03.00   (Release)   2008-02-18T03:13:47-0600       

Upgrade History:

IDS-K9-min-5.1-8-E3 14:16:00 UTC Thu Mar 04 2008

Recovery Partition Version 1.1 - 5.1(8)E3

sensor# 

Copy your license key from a sensor to a server to keep a backup copy of the license:

sensor# copy license-key scp://user@10.89.147.3://tftpboot/dev.lic 

Password: *******

sensor#

For the procedure for adding remote hosts to the SSH known hosts list, refer to 

For the procedure for making a remote host a TLS trusted host, refer to 

.

For more information on Cisco service contracts, see 

.

The following restrictions and limitations apply to Cisco IPS 5.1(8)E3 software and the products that 
run 5.1(8)E3:

An IPS appliance can support both promiscuous and inline monitoring at the same time; however 
you must configure each physical interface in either promiscuous or inline mode. Because inline 
monitoring requires the use of two sensing interfaces, the sensor must contain at least three physical 
sensing interfaces to perform both promiscuous and inline monitoring. The exceptions to this are 
AIP-SSM-10 and AIP-SSM-20. AIP-SSM can support both promiscuous and inline monitoring on 
its single physical back plane interface inside the ASA. The configuration on the main ASA can be 
used to designate which packets/connections should be monitored by AIP-SSM as either 
promiscuous or inline.

You can configure only one IDSM-2 for inline monitoring between two VLANs.   Configuring more 
than one IDSM-2 in inline mode between the same two VLANs can cause a packet loop in the 
switch. If you need to use more than one IDSM-2 in inline mode in the switch, you must configure 
each IDSM-2 for inline monitoring for a unique set of two VLANs.

NM-CIDS does not run in inline mode.

We do not support deploying an IPS sensor monitoring two sides of a network device that does TCP 
sequence number randomization.