CISCO-NBAR-PROTOCOL-DISCOVERY-MIB: View SNMP OID List / Download MIB

Cisco NBAR Protocol Discovery MIB NBAR - Network Based Application Recognition is an intelligent classification engine that recognizes applications that are static (which use fixed TCP or UDP port numbers), and stateful (which dynamically assign TCP or UDP port numbers). Protocol Discovery - uses NBAR to show you the mix of applications currently running on the network. Key statistics are associated with each protocol. These statistics can be used to define traffic classes and QoS policies. Functionality: 1. To enable/disable Protocol Discovery per interface. 2. Display the protocols/applications which NBAR currently recognizes. 3. To display various Protocol Discovery statistics. 4. A configurable top N table which lists protocols using user defined criteria. 5. To configure notifications (traps) based on configurable statistic thresholds. 6. To maintain a history table of all notification events.

A cnpdThresholdRisingEvent is sent whenever a notification entry crosses its rising threshold and generates an event that is added to the cnpdThresholdHistoryTable.

A cnpdThresholdConfigFallingEvent is sent whenever a notification entry crosses its falling threshold and generates an event that is added to the cnpdThresholdHistoryTable.

The cnpdStatusTable is used to enable and disable Protocol Discovery on an interface.

An entry in the cnpdStatusTable contains objects for enabling or disabling Protocol Discovery on a per interface basis.

This object is used to enable or disable Protocol Discovery on an interface. If set to 'true' - Protocol Discovery is enabled on this Interface. If set to 'false' - Protocol Discovery is disabled on this Interface.

The value of sysUpTime at the time Protocol Discovery was last enabled on an interface. If the interface does not have Protocol Discovery enabled this value is zero.

The cnpdAllStatsTable contains all the statistics available for all the protocols/applications currently recognized by NBAR Protocol Discovery for a particular interface. In the event of an overflow, the 32 bit counters are not valid. There is no overflow support.

An entry in the cnpdAllStatsTable table. This entry contains the statistics collected on all the protocols which NBAR classifies for a particular interface.

An object which represents a unique identifier for a protocol or application which NBAR currently recognizes. This object is an index into the SupportedProtocolsTable where details of the protocol can be found.

Name of the application or protocol, a unique textual string, assigned in the cnpdSupportedProtocolsTable.

The packet count of inbound packets as determined by Protocol Discovery.

The packet count of outbound packets as determined by Protocol Discovery.

The byte count of inbound octets as determined by Protocol Discovery.

The byte count of outbound octets as determined by Protocol Discovery.

The packet count of inbound packets as determined by Protocol Discovery. This is the 64-bit (High Capacity) version of cnpdAllStatsInPkts.

The packet count of outbound packets as determined by Protocol Discovery. This is the 64-bit (High Capacity) version of cnpdAllStatsOutPkts.

The byte count of inbound octets as determined by Protocol Discovery. This is the 64-bit (High Capacity) version of cnpdAllStatsInBytes.

The byte count of outbound octets as determined by Protocol Discovery. This is the 64-bit (High Capacity) version of cnpdAllStatsOutBytes.

The inbound bit rate as determined by Protocol Discovery.

The outbound bit rate as determined by Protocol Discovery.

The cnpdTopNConfigTable is used to configure cnpdTopNStatsTable's.

This entry provides the objects to configure and thus initiate the generation of a cnpdTopNStatsTable..

A monotonically increasing integer which uniquely identifies a cnpdTopNConfigEntry in the cnpdTopNConfigTable.

This object allows the management station to select the interface, which Protocol Discovery is running on, to be used to create this cnpdTopNConfigEntry.

This object allows the management station to select the statistic used to base the order of the top-n table on. For example: a cnpdTopNConfigStatsSelect of bitRateSum means order this table based on each applications/protocols combined in and out bitrate.

If the cnpdTopNConfigStatsSelect is bitRateIn, bitRateOut or bitRateSum, then this value is the interval in seconds that the bitrate is sampled. This has no effect if the cnpdTopNConfigStatsSelect is byte or packet based. When this object is modified by the management station, a new sample period is started regardless of whether the original cnpdTopNConfigSampleTime was finished.

The requested size of the associated cnpdTopNStatsTable entry. For example a cnpdTopNConfigRequestedSize of 20 indicates the management station wants to create an associated cnpdTopNStatsTable entry of 20 protocol/application's

The actual size of the associated cnpdTopNStatsTable entry. The reason this may differ from cnpdTopNConfigRequestedSize is because a management station may request a number of protocols that is greater than the number of protocols actually found by Protocol Discovery.

The value of sysUpTime when the associated cnpdTopNStatsTable entry was created.

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.

A cnpdTopNStatsTable describes an ordered list of protocols.

This entry is used to store a set of objects which describe a cnpdTopNStatsTable. A cnpdTopNStatsTable is a number of protocols and statistics sorted according to the criteria in the associated cnpdTopNConfigEntry. Therefore a cnpdTopNStatsTable can differ in content and size according to what was configured in the associated cnpdTopNConfigTableEntry.

A monotonically increasing integer which uniquely identifies a cnpdTopNStatsEntry in the cnpdTopNStatsTable.

Name of the application or protocol, a unique textual string, assigned in the cnpdSupportedProtocolsTable.

The amount of change in the selected statistic during this sampling interval. The selected statistic is the cnpdTopNConfigStatsSelect from the associated cnpdTopNConfigStatsEntry.

The amount of change in the selected statistic during this sampling interval. The selected statistic is the cnpdTopNConfigStatsSelect from the associated cnpdTopNConfigStatsEntry. This is the 64-bit (High Capacity) version of cnpdTopNStatsRate.

The cnpdThresholdConfigTable allows the management station to create thresholds for the purpose of sending notifications if breached, and creating a history of breached thresholds.

This entry contains configuration information to set thresholds for the purpose of notifications. The management station is allowed to set thresholds on individual statistics for individual protocols on an interface. If the threshold is breached by the protocol statistic, a new event is written to the cnpdThresholdHistoryTable, which in turn will generate a Notification Event. This function has a hysteresis mechanism to limit the generation of events. This mechanism generates one event as a threshold is crossed in the appropriate direction. No more events are generated for that threshold until the opposite threshold is crossed. This stops repeated Notification events being generated each time the value is sampled, when the value is above the threshold. Instead one notification is sent when the threshold is breached and one notification when the statistic drops below the threshold value again.

A monotonically increasing integer which uniquely identifies an entry in the cnpdThresholdConfigTable.

This object allows the management station to select the interface, which Protocol Discovery is running on, to be used to create this cnpdThresholdConfigTable entry.

The interval in seconds over which the data is sampled and compared with cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds.

The method of sampling the selected statistic and calculating the value to be compared against cnpdThresholdConfigRising or cnpdThresholdConfigFalling thresholds. If the value of this object is absoluteValue(1), the value at the end of the sampling interval cnpdThresholdConfigInterval, will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. In this mode, when cnpdThresholdConfigStatsSelect is byte or packet based, a maximum of two cnpdThresholdHistory entries will be created per application, as these byte and packet counts monotonically increase from zero. If the value of this object is deltaValue(2), the difference between the samples at the beginning and end of the cnpdThresholdConfigInterval will be compared with the cnpdThresholdConfigRising and cnpdThresholdConfigFalling thresholds. Because the difference in the previous and current samples are compared over the sample period cnpdThresholdConfigInterval, this mode provides more granularity to the thresholds because the NMS is now provided with the gradient or change in the cnpdThresholdConfigStatsSelect. Note that even though the sample value is monotonically increasing for byte and packet counts, cnpdThresholdConfigSampleType set to deltaValue, can generate falling cnpdThresholdHistory entries, because the gradient can be lower than the cnpdThresholdConfigFalling value. Enumeration: 'absoluteValue': 1, 'deltaValue': 2.

The application or protocol which the management station wishes to configure a threshold on. This object is an index into the SupportedProtocolsTable where details of the protocol can be found. If cnpdThresholdConfigProtocolAny is set to TRUE this value will be ignored. If it is set to FALSE, then cnpdThresholdConfigProtocol will be the only protocol that is checked to see if it has breached the threshold.

If set to 'true' - this threshold is configured to check for any protocol which meets the threshold criteria. This means that multiple protocols can generate ThresholdHistoryTable entries. Each protocol is subject to the hysterisis mechanism. If set to 'false' - this threshold is configured to check for the protocol which meets the threshold criteria referred to by cnpdThresholdConfigProtocol.

This object allows the management station to select the statistic used to base the threshold on. For example a cnpdThresholdConfigStatsSelect of bitRateSum means cnpdThresholdConfigRising and cnpdThresholdConfigFalling are values based on the combined value of in and out bitrates.

This controls the type of notification that is sent when this threshold entry is first enabled. Because there is no previous sampling history, choosing one of these options determines the type of notification generated - Rising or Falling. If the first sample after this entry is enabled is greater than or equal to cnpdThresholdConfigRising and this object is equal to rising(1) or risingOrFalling(3), then a single rising notification will be generated. If the first sample after this entry is enabled is less than or equal to cnpdThresholdConfigFalling and this object is equal to falling(2) or risingOrFalling(3), then a single falling notification will be generated. Enumeration: 'falling': 2, 'rising': 1, 'risingOrFalling': 3.

This is the threshold object which the managment station sets to determine if it gets breached. It indicates the statistic being sampled was rising. When the current sample is greater than or equal to this object, and the value at the last sampling interval was less than this object (in other words the value is rising), an entry in the cnpdThresholdHistoryTable will be created. After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the cnpdThresholdConfigFalling value. This ensures that samples which are taken after a cnpdThresholdConfigRising threshold event has been created, do not create further thresholds and therefore notifications, until the cnpdThresholdConfigFalling threshold has been met. Thus a very short cnpdThresholdConfigInterval can be chosen without risk of multiple notifications for the same threshold breach condition.

This is the threshold object which the management station sets to determine if it gets breached. It indicates the statistic being sampled was falling. When current sample is less than or equal to this object, and the value at the last sampling interval was greater than this object (in other words the value is falling), an entry in the cnpdThresholdHistoryTable will be created. After a falling event is generated, another such event will not be generated until the sampled value rises above this object and reaches the cnpdThresholdConfigRising value.

This object is used to create or delete the row entry in cnpdThresholdConfigTable. When creating a row entry the management station is required to specify a value for cnpdThresholdConfigIfIndex, cnpdThresholdConfigRising and cnpdThresholdConfigFalling. 'active' means that a createAndGo or active has been issued, AND a valid ifIndex exists. And therefore if a row is 'active' it means a ThresholdHistory entry may have been generated if the value was breached. If you set an 'active' row to 'createAndWait' - it will in fact get the status 'notReady'. Likewise if you set any row to 'notInService' or 'notReady' it will go to the 'notReady' state.

The Threshold History table. Notifications are unreliable so this table provides a history of the last 5000 threshold breached events. A notification can be traced back to its cnpdThresholdHistoryEntry.

This entry is created each time a threshold is breached. Thus there is not necessarily a one to one relationship to cnpdThresholdConfigTable as not every Threshold configured will be breached.

A monotonically increasing integer which uniquely identifies this cnpdThresholdHistoryEntry in the cnpdThresholdHistory table.

The cnpdThresholdConfigTable entry which generated this entry. Using this object the management station can backtrack to the appropriate cnpdThresholdConfigEntry.

The actual value of the statistic when the sampling was made.

Describes whether this is an event caused by a rising or falling threshold breach. Enumeration: 'risingBreach': 1, 'fallingBreach': 2.

The value of sysUpTime of the running configuration when the event occurred.

The application or protocol which the management station configured a threshold on. This object is an index into the SupportedProtocolsTable where details of the protocol can be found.

This is the statistic used to base the threshold on.

This object is used to enable or disable Notifications on a global basis. If set to 'true' - Notifications are enabled. If set to 'false' - Notifications are disabled.

The Supported Protocols table lists all the protocols and applications which NBAR is currently capable of recognizing.

A entry in the Supported Protocols table reflecting key information about a protocol.

A unique identifier of a row in this table. Thus it also represents a unique identifier for a protocol or application which NBAR currently recognizes.

This object reflects the valid string of a protocol or application which NBAR currently recognizes.

The compliance statement for entities that implement NBAR Protocol Discovery on a Cisco router.

Required objects to provide protocol application discovery info.

The set of objects supported to record notification events.

The set of objects supported to record notification events.

The set of notification events supported.

The set of notification configuration events.

The set of objects describing a protocol or application.