A value between 0 and 10 that should rarely
get above 3. If this is non-zero the sensor
has stopped enforcing policy on some traffic in
order to keep up with the current traffic load;
the sensor is oversubscribed. The higher the
number the more oversubscribed the sensor. It
could be oversubscribed from a memory prospective
and not traffic speed. For example on a 200 Mbit
sensor this number might be 3 if the sensor was
only seeing 100Mbit of traffic but 6000
connections per second which is over the rated
capacity of the sensor. When the sensor is
in Memory Critical state then a ciscoCidsError
trap will be sent accordingly.
Parsed from file CISCO-CIDS-MIB.mib
Module: CISCO-CIDS-MIB
A value between 0 and 10 that should rarely
get above 3. If this is non-zero the sensor
has stopped enforcing policy on some traffic in
order to keep up with the current traffic load;
the sensor is oversubscribed. The higher the
number the more oversubscribed the sensor. It
could be oversubscribed from a memory prospective
and not traffic speed. For example on a 200 Mbit
sensor this number might be 3 if the sensor was
only seeing 100Mbit of traffic but 6000
connections per second which is over the rated
capacity of the sensor. When the sensor is
in Memory Critical state then a ciscoCidsError
trap will be sent accordingly.
A value between 0 and 10 that should rarely
get above 3. If this is non-zero the sensor
has stopped enforcing policy on some traffic in
order to keep up with the current traffic load;
the sensor is oversubscribed. The higher the
number the more oversubscribed the sensor. It
could be oversubscribed from a memory prospective
and not traffic speed. For example on a 200 Mbit
sensor this number might be 3 if the sensor was
only seeing 100Mbit of traffic but 6000
connections per second which is over the rated
capacity of the sensor. When the sensor is
in Memory Critical state then a ciscoCidsError
trap will be sent accordingly.
Parsed from file CISCO-CIDS-MIB.my.txt
Company: None
Module: CISCO-CIDS-MIB
A value between 0 and 10 that should rarely
get above 3. If this is non-zero the sensor
has stopped enforcing policy on some traffic in
order to keep up with the current traffic load;
the sensor is oversubscribed. The higher the
number the more oversubscribed the sensor. It
could be oversubscribed from a memory prospective
and not traffic speed. For example on a 200 Mbit
sensor this number might be 3 if the sensor was
only seeing 100Mbit of traffic but 6000
connections per second which is over the rated
capacity of the sensor. When the sensor is
in Memory Critical state then a ciscoCidsError
trap will be sent accordingly.
cidsHealthIsSensorMemoryCritical OBJECT-TYPE SYNTAX Unsigned32 ( 0..10 ) MAX-ACCESS read-only STATUS current DESCRIPTION "A value between 0 and 10 that should rarely get above 3. If this is non-zero the sensor has stopped enforcing policy on some traffic in order to keep up with the current traffic load; the sensor is oversubscribed. The higher the number the more oversubscribed the sensor. It could be oversubscribed from a memory prospective and not traffic speed. For example on a 200 Mbit sensor this number might be 3 if the sensor was only seeing 100Mbit of traffic but 6000 connections per second which is over the rated capacity of the sensor. When the sensor is in Memory Critical state then a ciscoCidsError trap will be sent accordingly." ::= { cidsHealth 14 }
cidsHealthIsSensorMemoryCritical OBJECT-TYPE SYNTAX Gauge(0..10) ACCESS read-only STATUS mandatory DESCRIPTION "A value between 0 and 10 that should rarely get above 3. If this is non-zero the sensor has stopped enforcing policy on some traffic in order to keep up with the current traffic load; the sensor is oversubscribed. The higher the number the more oversubscribed the sensor. It could be oversubscribed from a memory prospective and not traffic speed. For example on a 200 Mbit sensor this number might be 3 if the sensor was only seeing 100Mbit of traffic but 6000 connections per second which is over the rated capacity of the sensor. When the sensor is in Memory Critical state then a ciscoCidsError trap will be sent accordingly." ::= { cidsHealth 14 }
Vendor: Cisco
Module: CISCO-CIDS-MIB
[Automatically extracted from oidview.com]
cidsHealthIsSensorMemoryCritical OBJECT-TYPE SYNTAX Unsigned32 ( 0..10 ) MAX-ACCESS read-only STATUS current DESCRIPTION "A value between 0 and 10 that should rarely get above 3. If this is non-zero the sensor has stopped enforcing policy on some traffic in order to keep up with the current traffic load; the sensor is oversubscribed. The higher the number the more oversubscribed the sensor. It could be oversubscribed from a memory prospective and not traffic speed. For example on a 200 Mbit sensor this number might be 3 if the sensor was only seeing 100Mbit of traffic but 6000 connections per second which is over the rated capacity of the sensor. When the sensor is in Memory Critical state then a ciscoCidsError trap will be sent accordingly." ::= { cidsHealth 14 }
cidsHealthIsSensorMemoryCritical OBJECT-TYPE SYNTAX Unsigned32 (0..10) MAX-ACCESS read-only STATUS current DESCRIPTION "A value between 0 and 10 that should rarely get above 3. If this is non-zero the sensor has stopped enforcing policy on some traffic in order to keep up with the current traffic load; the sensor is oversubscribed. The higher the number the more oversubscribed the sensor. It could be oversubscribed from a memory prospective and not traffic speed. For example on a 200 Mbit sensor this number might be 3 if the sensor was only seeing 100Mbit of traffic but 6000 connections per second which is over the rated capacity of the sensor. When the sensor is in Memory Critical state then a ciscoCidsError trap will be sent accordingly." ::= { cidsHealth 14 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.383.1.4.14.0 | cidsHealthIsSensorMemoryCritical | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.383.1.4.1 | cidsHealthPacketLoss | 1 | 1 | The percentage of packets lost at the device interface level. |
| 1.3.6.1.4.1.9.9.383.1.4.2 | cidsHealthPacketDenialRate | 1 | 1 | The percentage of packets denied due to protocol and security violations. |
| 1.3.6.1.4.1.9.9.383.1.4.3 | cidsHealthAlarmsGenerated | 1 | 1 | The number of alarms generated, includes all currently defined alarm severities. |
| 1.3.6.1.4.1.9.9.383.1.4.4 | cidsHealthFragmentsInFRU | 1 | 1 | The number of fragments currently queued in the fragment reassembly unit. |
| 1.3.6.1.4.1.9.9.383.1.4.5 | cidsHealthDatagramsInFRU | 1 | 1 | The number of datagrams currently queued in the fragment reassembly unit. |
| 1.3.6.1.4.1.9.9.383.1.4.6 | cidsHealthTcpEmbryonicStreams | 1 | 1 | cidsHealthtcpEmbryonicStreams |
| 1.3.6.1.4.1.9.9.383.1.4.7 | cidsHealthTCPEstablishedStreams | 1 | 1 | cidsHealthtCPEstablishedStreams |
| 1.3.6.1.4.1.9.9.383.1.4.8 | cidsHealthTcpClosingStreams | 1 | 1 | cidsHealthtcpClosingStreams |
| 1.3.6.1.4.1.9.9.383.1.4.9 | cidsHealthTcpStreams | 1 | 1 | cidsHealthtcpStreams |
| 1.3.6.1.4.1.9.9.383.1.4.10 | cidsHealthActiveNodes | 1 | 1 | The number of active nodes currently queued in the device. |
| 1.3.6.1.4.1.9.9.383.1.4.11 | cidsHealthTcpDualIpAndPorts | 1 | 1 | cidsHealthtcpDualIpAndPorts |
| 1.3.6.1.4.1.9.9.383.1.4.12 | cidsHealthUdpDualIpAndPorts | 1 | 1 | The number UDP nodes keyed on both IP addresses and both ports currently queued in the device. |
| 1.3.6.1.4.1.9.9.383.1.4.13 | cidsHealthIpDualIp | 1 | 1 | The number IP nodes keyed on both IP addresses currently queued in the device. |
| 1.3.6.1.4.1.9.9.383.1.4.15 | cidsHealthIsSensorActive | 1 | 1 | Indicates the failover status of the device. True indicates the device is currently active. False indicates it is in a standby mo… |
| 1.3.6.1.4.1.9.9.383.1.4.16 | cidsHealthCommandAndControlPort | 1 | 1 | The status and network statistics of the currently configured Command and Control interface on the device. The Command and Contro… |
| 1.3.6.1.4.1.9.9.383.1.4.17 | cidsHealthSensorStatsResetTime | 1 | 1 | The value of SNMPv2-MIB::sysUpTime when the Sensor specific statistics was reset. The reset time is collectively for the followin… |
| 1.3.6.1.4.1.9.9.383.1.4.18 | cidsHealthSecMonAvailability | 0 | 0 | This object indicates the availability of health and security monitor statistics. If the IPS health and security monitoring serv… |
| 1.3.6.1.4.1.9.9.383.1.4.19 | cidsHealthSecMonOverallHealth | 0 | 0 | This object indicates IPS sensor's overall health value - green, yellow or red. The overall health status is set to the highest … |
| 1.3.6.1.4.1.9.9.383.1.4.20 | cidsHealthSecMonSoftwareVersion | 0 | 0 | This object indicates the IPS software version number (e.g., 6.2(1)E3). This object is instantiated only if the value of cidsHealt… |
| 1.3.6.1.4.1.9.9.383.1.4.21 | cidsHealthSecMonSignatureVersion | 0 | 0 | This object indicates IPS signature version (e.g., 365.0). This object is instantiated only if the value of cidsHealthSecMonAvail… |
| 1.3.6.1.4.1.9.9.383.1.4.22 | cidsHealthSecMonLicenseStatus | 0 | 0 | This object indicates IPS license status along with expiration date. For example it will contain the following possible values: - … |
| 1.3.6.1.4.1.9.9.383.1.4.23 | cidsHealthSecMonOverallAppColor | 0 | 0 | This object indicates the aggregate health status of the applications - Main, Analysis Engine, Collaboration - where the status i… |
| 1.3.6.1.4.1.9.9.383.1.4.24 | cidsHealthSecMonMainAppStatus | 0 | 0 | This object indicates the running status for the control plane. This object is instantiated only if the value of cidsHealthSecMon… |
| 1.3.6.1.4.1.9.9.383.1.4.25 | cidsHealthSecMonAnalysisEngineStatus | 0 | 0 | This object indicates the running status for the Analysis Engine. This object is instantiated only if the value of cidsHealthSecM… |
| 1.3.6.1.4.1.9.9.383.1.4.26 | cidsHealthSecMonCollaborationAppStatus | 0 | 0 | This object indicates the running status for the Collaboration Application. This object is instantiated only if the value of cids… |
| 1.3.6.1.4.1.9.9.383.1.4.27 | cidsHealthSecMonByPassMode | 0 | 0 | This object indicates the bypass mode. A value of 'true' indicates bypass mode is on and a value of 'false' indicates it is off.… |
| 1.3.6.1.4.1.9.9.383.1.4.28 | cidsHealthSecMonMissedPktPctAndThresh | 0 | 0 | This object indicates the missed packet percentage and missed packets percentage threshold aggregated for all interfaces. For exa… |
| 1.3.6.1.4.1.9.9.383.1.4.29 | cidsHealthSecMonAnalysisEngMemPercent | 0 | 0 | This object indicates the percentage of memory used by Analysis Engine. This object is instantiated only if the value of cidsHealt… |
| 1.3.6.1.4.1.9.9.383.1.4.30 | cidsHealthSecMonSensorLoad | 0 | 0 | This object indicates sensor inspection load. This object is instantiated only if the value of cidsHealthSecMonAvailability is se… |
| 1.3.6.1.4.1.9.9.383.1.4.31 | cidsHealthSecMonSensorLoadColor | 0 | 0 | This object indicates the status of current sensor load, indicated using status colors. The color is determined based on the sens… |
| 1.3.6.1.4.1.9.9.383.1.4.32 | cidsHealthSecMonVirtSensorStatusTable | 1 | 3 | This table contains the status of each virtual sensor. There will be one entry per virtual sensor in the system. This is the stat… |
| 1.3.6.1.4.1.9.9.383.1.4.33 | cidsHealthSecMonDataStorageTable | 1 | 4 | This is the table of disk partition details: Partition Name Total Space In Partition Utilized Space This table tells how each of th… |