All MIBs › CISCO-NBAR-PROTOCOL-DISCOVERY-MIB › cnpdTopNConfigStatus
cnpdTopNConfigStatus
Module: CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
OID (symbolic): CISCO-NBAR-PROTOCOL-DISCOVERY-MIB::cnpdTopNConfigStatus
OID (numeric): 1.3.6.1.4.1.9.9.244.1.3.1.1.8
Node type: OBJECT-TYPE
Type: RowStatus
Access: read-write
Description: This object is used to create or delete the row entry in cnpdTopNConfigTable.
When creating a row entry the management station is required to specify a value for cnpdTopNConfigIfIndex only.
'notReady' means that a row exists but either it has no valid IfIndex or it has not been set to createAndGo or active.
'active' means that a createAndGo or active has been issued, AND a valid ifIndex exists. Therefore if a row is 'active' it means a TopNStats entry has been generated.
If you set an 'active' row to createAndWait it will get the status 'notReady'.
If you set any row to 'notReady' - it will go to the 'notReadystate'.
If you set any row to 'notInService' - it will go to the 'notInService' state and the corresponding TopNStatsEntry will be deleted.
The same TopNConfig entry can be re-used without changes by setting it to 'active'. The corresponding TopStatsTable entry will be regenerated. This can be used by the NMS to poll a particular TopNConfig Entry.
Changes to an existing TopNConfig entry can be made by setting the status to 'createAndWait' and changing the necessary objects. Setting it to 'createAndGo' or 'active' will cause the corresponding TopNStats entry to be regenerated.
What is cnpdTopNConfigStatus?
This RowStatus object creates or deletes a Top-N reporting configuration row, and per the description a newly-created row only needs cnpdTopNConfigIfIndex specified before it can go active. Its notReady versus active states are diagnostically useful: if an admin creates a row but it stays stuck at notReady, that specifically flags a missing or invalid ifIndex value rather than some other configuration problem. Seeing this stuck at notReady after a provisioning script ran would point the admin directly at re-checking the ifIndex value it supplied.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.244.1.3.1.1.8 snmpwalk -v2c -c public <target> CISCO-NBAR-PROTOCOL-DISCOVERY-MIB::cnpdTopNConfigStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.244.1.3.1.1.8.1 snmpget -v2c -c public <target> CISCO-NBAR-PROTOCOL-DISCOVERY-MIB::cnpdTopNConfigStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.244.1.3.1.1.8.1 s <value>
Start monitoring Cisco router/switch with NBAR support with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-NBAR-PROTOCOL-DISCOVERY-MIB::cnpdTopNConfigStatus OID value, configure state conditions and alerts, and monitor any Cisco router/switch with NBAR support from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.244 | ciscoNbarProtocolDiscoveryMIB | CISCO-NBAR-PROTOCOL-DISCOVERY-MIB |
| 1.3.6.1.4.1.9.9.244.1 | cnpdMIBObjects | CISCO-NBAR-PROTOCOL-DISCOVERY-MIB |
| 1.3.6.1.4.1.9.9.244.1.3 | cnpdTopNConfig | CISCO-NBAR-PROTOCOL-DISCOVERY-MIB |
| 1.3.6.1.4.1.9.9.244.1.3.1 | cnpdTopNConfigTable | CISCO-NBAR-PROTOCOL-DISCOVERY-MIB |
| 1.3.6.1.4.1.9.9.244.1.3.1.1 | cnpdTopNConfigEntry | CISCO-NBAR-PROTOCOL-DISCOVERY-MIB |
| 1.3.6.1.4.1.9.9.244.1.3.1.1.8 | cnpdTopNConfigStatus | CISCO-NBAR-PROTOCOL-DISCOVERY-MIB |