Cisco ASR 901 and 901S Series Aggregation Services Router Series MIB Specifications Guide

Contains one entry per BGP peer, information about the connections with BGP peers.

Contains information about paths to destination networks received from all peers running BGP version 3 or less.

Contains information about paths to destination networks received from all BGP4 peers.

Contains information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included.

Contains port-specific information for the Spanning Tree Protocol.

Contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.

Contains information about every port that is associated with this transparent bridge.

Contains filtering information configured into the bridge by local or network management specifying the set of ports to which frames received from specific ports and containing specific destination addresses are allowed to be forwarded. The value of zero in this table, as the port number from which frames with a specific destination address are received, is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast and group/broadcast addresses.

• casAddress

Read-only.

• casAuthenPort

Read-only. The default value is 1645.

• casAcctPort

Read-only. The default value is 1646.

• casKey

Read-only. This value is always shown as " " (null string) for security reasons.

• casConfigRowStatus

Read-only.

• casAuthorRequests

For RADIUS servers, thevalues are always 0. (RADIUS does not make authorization requests.) Only TACACS+ servers can have non-zero values.

Contains the additional power supply information that are not covered in the ciscoEnvMonSupplyStatusTable of CISCO-ENVMON-MIB.

Contains rate limit configuration entries. Rate Limit is a method of traffic control. It allows a set of rate limits to be configured and applied to packets flowing into/out of an interface to regulate network traffic.

Contains rate limit status entries.

The (conceptual) table containing the status of CDP on the device’s interfaces.

This table contains the additional CDP configuration on the device’s interfaces.

The (conceptual) table containing the cached information obtained via receiving CDP messages.

The (conceptual) table contains the list of network-layer addresses of a neighbor interface, as reported in the Address TLV of the most recently received CDP message. The first address included in the Address TLV is saved in cdpCacheAddress. This table contains the remainder of the addresses in the Address TLV.

This table contains the summary information for the cefPrefixTable.

A list of CEF forwarding prefixes.

A table of Longest Match Prefix Query requests. Generator application should utilize the cefLMPrefixSpinLock to try to avoid collisions. See DESCRIPTION clause of cefLMPrefixSpinLock.

CEF prefix path is a valid route to reach to a destination IP prefix. Multiple paths may exist out of a router to the same destination prefix. This table specify lists of CEF paths.

This table contains the summary information for the cefAdjTable.

A list of CEF adjacencies.

A list of forwarding element selection entries.

This table contains global config parameter of CEF on the Managed device.

This table contains global resource information of CEF on the Managed device.

This Table contains interface specific information of CEF on the Managed device.

Entity acting as RP (Routing Processor) keeps the CEF states for the entities and communicates with the entities using XDR. This Table contains the CEF information related to peer entities on the managed device.

Entity acting as RP (Routing Processor) keep the CEF FIB states for the entities and communicate with the entities using XDR. This Table contains the CEF FIB State related to peer entities on the managed device.

This table specifies the CEF stats based on the Prefix Length.

This table specifies the CEF switch stats.

This table contains CEF consistency checker (CC) global parameters for the managed device.

This table contains CEF consistency checker types specific parameters on the managed device. All detected inconsistency are signaled to the Management Station via cefInconsistencyDetection notification.

This table contains CEF inconsistency records.

Specifies the configuration information for weighted queue limit action per IP precedence basis.

Specifies configuration information for measure type IPSLA action. The measure action relates the policy class to a specific IPSLAs auto group. Configuration of measure action of type IPSLA results in automatic generation of IPSLAs synthetic test operations when the policy is attached to interface. The operations are created according to the characteristics specified and to the destinations specified in IPSLA auto group. The IPSLAs sythentic test operations measure network statistics such as latency, packet loss and jitter. This table is to be used only for retrieving the measure action configuration information.

Describes the logical interfaces/media types and the policymap that are attached to it.

Describes the service polices that are attached to main and sub interfaces.

Describes the service polices that are attached to Frame Relay DLCIs.

Describes the policies that are attached to a ATM PVC.

Specifies QoS objects (classmap, policymap, match statements, and actions) hierarchy. It also provide relationship between each PolicyIndex/ObjectsIndex pair and the ConfigIndex. ConfigIndex is essential for querying any configuration tables.

Specifies Policymap configuration information

Specifies ClassMap configuration information

Specifies ClassMap configuration information

Specifies Queueing Action configuration information

Specifies WRED Action configuration information

Specifies WRED Action configuration information on a per IP precedence basis.

Specifies Police Action configuration information.

Specifies Police Action configuration information.

Specifies traffic-shaping Action configuration information.

Specifies Packet Marking Action configuration information.

Specifies ClassMap related Statistical information.

This table specifies Match Statement related statistical information.

Specifies Police Action related Statistical information.

Specifies Queueing Action related Statistical information.

Specifies traffic-shaping Action related Statistical information.

Specifies per Precedence WRED Action related Statistical information.

Specifies IP Header Compression configuration information.

Specifies IP Header Compression statistical information.

Specifies packet marking statistical information.

Specifies Police Action related Statistical information for two rate color aware marker.

Specifies Table Map basic configuration information.

Specifies Specifies the from-value to to-value conversion pairs for a tablemap.

Specifies enhanced packet marking configuration using a pre-defined tablemap.

Specifies Estimate Bandwidth related configuration information.

Specifies Estimate Bandwidth related statistical information.

Specifies C3pl Account Action configuration information

Specifies C3pl Account Action related statistics information.

Contains config-copy requests.

Contains information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to ’failed’ for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = ’runningConfig’ ccCopyDestFileType = ’fabricStartupConfig’. In the case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be ’fabricStartupConfig’, it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState ’failed’, but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, ’success’. Once the config copy operation completes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. Once an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. In order to prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out.

Contains CLI commands that took effect during configuration events.

This table contains the primary controls and status for the OAM capabilities of an Ethernet like interface. There will be one row in this table for each Ethernet like interface in the system that supports the OAM functions defined in [802.3ah].

This table contains information about the OAM peer for a particular Ethernet like interface. OAM entities communicate with a single OAM peer entity on Ethernet links on which OAM is enabled and operating properly. There is one entry in this table for each entry in the cdot3OamTable for which information on the peer OAM entity is available.

This table contains controls for the loopback state of the local link as well as indicating the status of the loopback function. There is one entry in this table for each entry in cdot3OamTable that supports loopback functionality (where cdot3OamFunctionsSupported includes the loopbackSupport bit set). Loopback can be used to place the remote OAM entity in a state where every received frame (except OAMPDUs) is echoed back over the same interface on which they were received. In this state, at the remote entity, ’normal’ traffic is disabled as only the looped back frames are transmitted on the interface. Loopback is thus an intrusive operation that prohibits normal data flow and should be used accordingly.

This table contains statistics for the OAM function on a particular Ethernet like interface. There is an entry in the table for every entry in the cdot3OamTable. The counters in this table are defined as 32-bit entries to match the counter size as defined in [802.3ah]. Given the OAM protocol is a slow protocol, the counters increment at a slow rate.

Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in cdot3OamTable that supports OAM events (where cdot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to cdot3OamOperStatus. The standard threshold crossing events are: - Errored Symbol Period Event. Generated when the number of symbol errors exceeds a threshold within a given window defined by a number of symbols (for example, 1,000 symbols out of 1,000,000 had errors). - Errored Frame Period Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a number of frames (for example, 10 frames out of 1000 had errors). - Errored Frame Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a period of time (for example, 10 frames in 1 second had errors). - Errored Frame Seconds Summary Event. Generated when the number of errored frame seconds exceeds a threshold within a given time period (for example, 10 errored frame seconds within the last 100 seconds). An errored frame second is defined as a 1 second interval which had 0 frame errors. There are other events (dying gasp, critical events) that are not threshold crossing events but which can be enabled/disabled via this table.

MAX-ACCESS not-accessible STATUS current "This table records a history of the events that have occurred at the Ethernet OAM level. These events can include locally detected events, which may result in locally generated OAMPDUs, and remotely detected events, which are detected by the OAM peer entity and signaled to the local entity via Ethernet OAM. Ethernet OAM events can be signaled by Event Notification OAMPDUs or by the flags field in any OAMPDU. This table contains both threshold crossing events and non-threshold crossing events. The parameters for the threshold window, threshold value, and actual value (cdot3OamEventLogWindowXX, cdot3OamEventLogThresholdXX, cdot3OamEventLogValue) are only applicable to threshold crossing events, and are returned as all F’s (2^32 - 1) for non-threshold crossing events. Entries in the table are automatically created when such events are detected. The size of the table is implementation dependent. When the table reaches its maximum size, older entries are automatically deleted to make room for newer entries.

This table contains information on those VPN’s configured to run EIGRP. The VPN creation on a router is independent of the routing protocol to be used over it. A VPN is given a name and has a dedicated routing table associated with it. This routing table is identified internally by a unique integer value.

Table of EIGRP traffic statistics and information associated with all EIGRP autonomous systems.

The table of EIGRP routes and their associated attributes for an Autonomous System (AS) configured in a VPN is called a topology table. All route entries in the topology table will be indexed by IP network type, IP network number and network mask (prefix) size.

The table of established EIGRP peers (neighbors) in the selected autonomous system. Peers are indexed by their unique internal handle id, as well as the AS number and VPN id. The peer entry is removed from the table if the peer is declared down.

The table of interfaces over which EIGRP is running, and their associated statistics. This table is independent of whether any peer adjacencies have been formed over the interfaces or not. Interfaces running EIGRP are determined by whether their assigned IP addresses fall within configured EIGRP network statements.

Contains memory pool monitoring entries for all physical entities on a managed system.

Contains entries in this table define entities (buffer pools in this case) which are contained in an entity (memory pool) defined by an entry from cempMemPoolTable. -- Basic Pool Architecture -- 1)Pools are classified as being either Static or Dynamic. Static pools make no attempt to increase the number of buffers contained within them if the number of free buffers (cempMemBufferFree) are less than the number of minimum buffers (cempMemBufferMin). With Dynamic pools, the pool attempts to meet the demands of its users. 2)Buffers in a pool are classified as being either Permanent or Temporary. Permanent buffers, as their name suggests, are always in the pool and are never destroyed unless the number of permanent buffers (cempMemBufferPermanent) is changed. Temporary buffers are transient buffers that are created in dynamic pools whenever the free count (cempMemBufferFree) of buffers in the pool drops below the minimum (cempMemBufferMin). 3)Buffers pools are classified as either Public or Private. Public pools are available for all users to allocate buffers from. Private pools are primarily used by interface drivers.

Lists the cache buffer pools configured on a managed system. 1)To provide a noticeable performance boost, Cache Pool can be used. A Cache Pool is effectively a lookaside list of free buffers that can be accessed quickly. Cache Pool is tied to Buffer Pool. 2)Cache pools can optionally have a threshold value on the number of cache buffers used in a pool. This can provide flow control management by having a implementation specific approach such as invoking a vector when pool cache rises above the optional threshold set for it on creation.

Lists the orderable part number, serial number, hardware revision, manufacturing assembly number and revision, firmwareID and revision if any, and softwareID and revision if any, of relevant entities listed in the ENTITY-MIB entPhysicalTable. Entities for which none of this data is available are not listed in this table. This is a sparse table so some of these variables may not exist for a particular entity at a particular time. For example, a powered-off module does not have softwareID and revision; a power-supply would probably never have firmware or software information. Although the data may have other items encoded in it (for example manufacturing-date in the serial number) please treat all data items as monolithic. Do not decompose them or parse them. Use only string equals and unequals operations on them.

Contains the type, scale, and present value of a sensor listed in the Entity-MIB entPhysicalTable.

Contains voltage status maintained by the environmental monitor.

Contains ambient temperature status maintained by the environmental monitor.

Contains fan status maintained by the environmental monitor.

Contains power supply status maintained by the environmental monitor card.

Contains Flash device properties for each initialized Flash device. Each Flash device installed in a system is detected, sized, and initialized when the system image boots up. For removable Flash devices, the device properties will be dynamically deleted and recreated as the device is removed and inserted. Note that in this case, the newly inserted device may not be the same as the earlier removed one. The ciscoFlashDeviceInitTime object is available for a management station to determine the time at which a device was initialized, and thereby detect the change of a removable device. A removable device that has not been installed will also have an entry in this table. This is to let a management station know about a removable device that has been removed. Since a removed device obviously cannot be sized and initialized, the table entry for such a device will have ciscoFlashDeviceSize equal to zero, and the following objects will have an indeterminate value: ciscoFlashDeviceMinPartitionSize, ciscoFlashDeviceMaxPartitions, ciscoFlashDevicePartitions, and ciscoFlashDeviceChipCount. ciscoFlashDeviceRemovable will be true to indicate it is removable.

Contains Flash device chip properties for each initialized Flash device. This table is meant primarily for aiding error diagnosis.

Contains flash device partition properties for each initialized flash partition. Whenever there is no explicit partitioning done, a single partition spanning the entire device will be assumed to exist. There will therefore always be atleast one partition on a device.

Contains information for files in a Flash partition.

Contains information for files on the manageable flash devices sorted by File Types.

Contains Flash copy operation entries. Each entry represents a Flash copy operation (to or from Flash) that has been initiated.

Contains Flash partitioning operation entries. Each entry represents a Flash partitioning operation that has been initiated.

Contains misc Flash operation entries. Each entry represents a Flash operation that has been initiated.

The BFD Session Table describes the BFD sessions.

This table specifies BFD Session performance counters.

The BFD Session Mapping Table maps the complex indexing of the BFD sessions to the flat CiscoBfdSessIndexTC used in the ciscoBfdSessTable.

The BFD Session Discriminator Mapping Table maps a local discriminator value to associated BFD sessions’ CiscoBfdSessIndexTC used in the ciscoBfdSessTable.

The BFD Session IP Mapping Table maps given ciscoBfdSessInterface, ciscoBfdSessAddrType, and ciscoBbfdSessAddr to an associated BFD sessions’ CiscoBfdSessIndexTC used in the ciscoBfdSessTable. This table SHOULD contains those BFD sessions are of IP type: singleHop(1) and multiHop(2).

This object enables the emission of ciscoBfdSessUp and ciscoBfdSessDown notifications; otherwise these notifications are not emitted.

This object shows the compliance statement for agents that provide full support for CISCO-IETF-BFD-MIB. Such devices can then be monitored and also be configured using this MIB module.

Contains information for connecting various emulated services to various tunnel type.

Contains per-VC performance information for the current interval.

Contains per-VC performance information for each interval.

Contains per-VC Performance information from VC start time.

Contains reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs.

Contains reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs.

This table contains interface packet statistics which are not available in IF-MIB(RFC2863). As an example, some interfaces to which objects in this table are applicable are as follows : o Ethernet o FastEthernet o ATM o BRI o Sonet o GigabitEthernet Some objects defined in this table may be applicable to physical interfaces only. As a result, this table may be sparse for some logical interfaces.

This table contains objects which provide more information about interface properties not available in IF-MIB (RFC 2863). Some objects defined in this table may be applicable to physical interfaces only. As a result, this table may be sparse for logical interfaces.

This table contains objects for providing the ’ifIndex’, interface operational mode and interface operational cause for all the interfaces in the modules. This table contains one entry for each 64 interfaces in an module. This table provides efficient way of encoding ’ifIndex’, interface operational mode and interface operational cause, from the point of retrieval, by combining the values a set of 64 interfaces in a single MIB object.

This table contains VL (Virtual Link) statistics for a capable interface. Objects defined in this table may be applicable to physical interfaces only.

This table lists configuration data relating to ifIndex persistence. This table has a sparse dependent relationship on the ifTable, containing a row for each ifEntry corresponding to an interface for which ifIndex persistence is supported.

A list of the interfaces that support the 802.1q custom Ethertype feature.

This table contains the interface utilization rates for inbound and outbound traffic on an interface.

This table contains the mappings of the ifIndex of an interface to its corresponding dot1dBasePort value.

This table contains objects for providing the ’ifName’ to ’ifIndex’ mapping. This table contains one entry for each valid ’ifName’ available in the system. Upon the first request, the implementation of this table will get all the available ifNames, and it will populate the entries in this table, it maintains this ifNames in a cache.

Provides content describing the executing IOS image.

The IPsec Phase-1 Internet Key Exchange Peer Table. There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. The IPsec Phase-1 IKE Tunnel associated with this IPsec Phase-1 IKE peer association may or may not be currently active.

The IPsec Phase-1 Internet Key Exchange Tunnel Table. There is one entry in this table for each active IPsec Phase-1 IKE Tunnel.

The IPsec Phase-1 Internet Key Exchange Peer Association to IPsec Phase-2 Tunnel Correlation Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.

The IPsec Phase-2 Tunnel Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.

The IPsec Phase-2 Tunnel Endpoint Table. This table contains an entry for each active endpoint associated with an IPsec Phase-2 Tunnel.

The IPsec Phase-2 Security Protection Index Table. This table contains an entry for each active and expiring security association.

The IPsec Phase-1 Internet Key Exchange Tunnel History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

The IPsec Phase-2 Tunnel History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

The IPsec Phase-2 Tunnel Endpoint History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

The IPsec Phase-1 Failure Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object.

The IPsec Phase-2 Failure Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object.

The table containing the list of all ISAKMP policy entries configured by the operator.

The table containing the list of all cryptomap sets that are fully specified and are not wild-carded. The operator may include different types of cryptomaps in such a set - manual, CET, ISAKMP or dynamic.

The table ilisting the member cryptomaps of the cryptomap sets that are configured on the managed entity.

This table contains Auto-Ethernet-CFM control data. When a row transition to the ’active’ state, the IP SLA agent will discover all the MEPs inside the specified VLAN and maintenance domain and create IP SLA ethernet operations based on the value of ipslaEthernetGrpCtrlRttType for each MEP. All the values in this table will be passed to the corresponding objects in the rttMonCtrlAdminTable and rttMonEchoAdminTable of CISCO-RTTMON-MIB so that each IP SLA Ethernet operation will have the same configuration as specified for Auto-Ethernet-CFM.

A table that contains the reaction configurations for Auto-Ethernet-CFM operation. The reaction configuration specifies the network perfomance parameter needs to be monitored, the threshold for the parameter, the type of threshold violation that will trigger a reaction, and how to react upon a threshold being violated. This allows for proactive monitoring in an environment where user can be alerted to potential network problems, rather than having to manually examine data. Each conceptual row in ipslaEthernetGrpReactTable corresponds to a reaction configured for a corresponding Auto-Ethernet-CFM operation. Each Auto-Ethernet-CFM operation can have multiple parameters monitored and hence there can be multiple reaction configuration rows for a particular Auto-Ethernet-CFM operation. The reaction configurations in this table for a particular Auto-Ethernet-CFM operation will be passed to the corresponding objects in rttMonReactTable of CISCO-RTTMON-MIB for all the IP SLA operations created by this Auto-Ethernet-CFM. This makes the IP SLA operation capable of reacting to certain measured network condition such as long round trip delay, big jitter, etc., by generating a notification to a network management application based on defined thresholds. This table is coupled with ipslaEthernetGrpCtrlTable. When an entry in the ipslaEthernetGrpCtrlTable is destroyed, the corresponding entries in this table will be destroyed too.

The ’ethernetJitter’ operation sends out frames at the frequency specified by rttMonCtrlAdminFrequency. This table contains the statistics calculated for the latest sent frames. Each conceptual row in this table corresponds to an ’ethernetJitter’ operation defined in rttMonCtrlAdminTable and has same index as rttMonCtrlAdminTable.

The ’ethernetJitter’ statistics table contains summarized information of the results for a conceptual control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. When ipslaEtherJAggStatsStartTimeId groups exceeds the rttMonStatisticsAdminNumHourGroups value, the oldest corresponding hourly group will be deleted and will be replaced with the new ipslaEtherJAggStatsStartTimeId hourly group.

Contains memory pool monitoring entries.

Contains memory pool utilization entries. Each of the objects provides a general idea of how much of the memory pool has been used over a given period of time. It is determined as a weighted decaying average.

G.781 clock selection process table. This table contains the global parameters for the G.781 clock selection process.

T0 selected clock source table. This table contains the selected clock source for the input T0 clock.

T0 clock source table. This table contains a list of input sources for input T0 clock selection.

T4 external output table. This table contains a list of T4 external outputs. Each T4 external output is associated with clock source(s) to be found in cnsT4ClockSourceTable. The clock selection process considers all the available clock sources and select the T4 clock source based on the G.781 clock selection algorithm.

T4 clock source table. This table contains a list of input sources for a specific T4 external output. An entry shall be added to cnsExtOutputTable first. Then clock sources shall be added in this table for the selection process to select the appropriate T4 clock source.

Provides information on the peers with which the local NTP server has associations. The peers are also NTP servers but running on different hosts.

Contains NTP state variables used by the NTP clock filter and selection algorithms. This table depicts a shift register. Each stage in the shift register is a 3-tuple consisting of the measured clock offset, measured clock delay and measured clock dispersion associated with a single observation. An important factor affecting the accuracy and reliability of time distribution is the complex of algorithms used to reduce the effect of statistical errors and falsetickers due to failure of various subnet components, reference sources or propagation media. The NTP clock-filter and selection algorithms are designed to do exactly this. The objects in the filter register table below are used by these algorthims to minimize the error in the calculated time.

Information describing the configured parameters and cumulative statistics of the router’s attached areas.

The OSPF Process’s Link State Database. This table is meant for Opaque LSA’s

The OSPF Interface Table describes the inter- faces from the viewpoint of OSPF.

Information about this router’s virtual inter- faces.

Information about this router’s sham links

Information about this router’s sham links.

A table of sham link neighbor information.

The OSPF Process’s Link-Local Link State Database for non-virtual links.

The OSPF Process’s Link-Local Link State Database for virtual links.

Lists the storm control threshold configuration entries.

Lists the storm control action entries.

Lists the storm control status entries.

Represents the history of storm events on an interface.

• cpscStatus

Not implemented.

• cpscCurrentLevel

Not implemented.

Not implemented.

Contains ping request entries.

Contains overall CPU statistics.

Contains generic information on all active processes on this device.

Contains information that may or may not be available on all cisco devices. It contains additional objects for the more general cpmProcessTable. This object is deprecated by cpmProcessExtRevTable.

Contains information that may or may not be available on all cisco devices. It contains additional objects for the more general cpmProcessTable. This object deprecates cpmProcessExtTable.

Contains the information about the thresholding values for CPU , configured by the user.

A list of CPU utilization history entries.

Contains generic information about POSIX threads in the device.

Contains information about virtual processes in a virtual machine.

Contains CPU utilization of processes which crossed the cpmCPUHistoryThreshold.

Table of count information about the PTP system for all domains.

Table of information about the PTP system for all clock modes -- ordinary, boundary or transparent.

Table of information about the PTP system for a given domain.

Table of information about the PTP clock Current Datasets for all domains.

Table of information about the PTP clock Parent Datasets for all domains.

Table of information about the PTP clock Default Datasets for all domains.

Table of information about the PTP clock Running Datasets for all domains.

Table of information about the PTP clock Timeproperties Datasets for all domains.

Table of information about the PTP Transparent clock Default Datasets for all domains.

Table of information about the clock ports for a particular domain.

Table of information about the clock ports dataset for a particular domain.

Table of information about the clock ports running dataset for a particular domain.

Table of information about the Transparent clock ports running dataset for a particular domain.

Table of information about a given port’s associated ports. For a master port - multiple slave ports which have established sessions with the current master port. For a slave port - the list of masters available for a given slave port. Session information (pkts, errors) to be displayed based on availability and scenario.

Contains objects that describe the queues on a Cisco Interface. An interface queue is modeled as a collection of one or more secondary queues that feed into a device’s hardware queue. The hardware queue has a maximum depth set by the MCI tx-queue-limit command or equivalent. The secondary queues (also known as the ’hold queue’) have maximum depths set by the hold-queue command or equivalent. This table parallels the ifTable, and indicates the type of queuing in use on the interface, number of queues, and similar parameters.

Contains statistical objects that for the sub-queues of a Cisco Interface.

Describes the rotation of Custom Queuing on an Interface.

This table specifies REP segments configured on the device.

This table provides REP configuration for interfaces in the device. This table contains one entry for each interface running REP.

A table for REP interfaces statistics. This table augments the crepInterfaceConfigTable.

Contains the supported Rtt Monitor Types. See the RttMonRttType textual convention for the definition of each type.

Contains the supported Rtt Monitor Protocols. See the RttMonProtocol textual convention for the definition of each protocol.

Contains the previously configured Script Names and File IO targets. These Script Names and File IO targets are installed via a different mechanism than this application, and are specific to each platform.

Contains the definitions for key-strings that will be used in authenticating RTR Control Protocol.

The RTT administration control is in multiple tables. This first table, is used to create a conceptual RTT control row. The following tables contain objects which configure scheduling, information gathering, and notification/trigger generation. All of these tables will create the same conceptual RTT control row as this table using this tables’ index as their own index. This table is limited in size by the agent implementation. The object rttMonApplNumCtrlAdminEntry will reflect this tables maximum number of entries.

Contains Round Trip Time (RTT) specific definitions. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.

Contains Round Trip Time (RTT) monitoring ’fileIO’ specific definitions. When the RttMonRttType is not ’fileIO’ this table is not valid. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.

Contains Round Trip Time (RTT) monitoring ’script’ specific definitions. When the RttMonRttType is not ’script’ this table is not valid. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.

Contains Round Trip Time (RTT) monitoring scheduling specific definitions. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.

Contains Round Trip Time (RTT) monitoring Notification and Trigger definitions. All Notification/Reactions are applied to all RTT End-to-End operations. Thus, they do not apply to hops along a path to the target, when RttMonRttType is ’pathEcho’. The format and content of SNA NMVT’s are not defined within this module. It can be noted, however, that there are Alert NMVT’s, and traps which are sent when an abnormal condition occurs, i.e. when one of rttMonCtrlOperConnectionLostOccurred, rttMonCtrlOperTimeoutOccurred or rttMonCtrlOperOverThresholdOccurred are changed to true, and Resolution NMVT’s, and Resolution traps which are sent when that condition clears, i.e. when one of rttMonCtrlOperConnectionLostOccurred, rttMonCtrlOperTimeoutOccurred or rttMonCtrlOperOverThresholdOccurred is changed back to false. When rttMonReactAdminActionType is set to one of the following: - triggerOnly - trapAndTrigger - nmvtAndTrigger - trapNmvtAndTrigger The corresponding rows in the rttMonReactTriggerAdminTable defined via the rttMonCtrlAdminIndex will become active. This table augments the rttMonCtrlAdminTable.

Contains Round Trip Time (RTT) monitoring statistics definitions. The definitions in this table control what and how many entries will be placed into the rttMonStatsCaptureTable. The statistics capture table is a rollover table. When the rttMonStatisticsAdminNumHourGroups index value exceeds its value defined in this table, the oldest corresponding group will be deleted and will be replaced with the new group. All other indices will only fill to there maximum size. NOTE: The maximum size of this table is defined to be the product of the rttMonCtrlAdminIndex times rttMonStatisticsAdminNumHourGroups times rttMonStatisticsAdminNumPaths times rttMonStatisticsAdminNumHops times rttMonStatisticsAdminNumDistBuckets. NOTE WELL: Each of the ’Num’ objects values in this have a special behavior. When one of the objects is set to a value larger than the Rtt application can support the set will succeed, but the resultant value will be set to the applications maximum value. The setting management station must reread this object to verify the actual value. This table augments the rttMonCtrlAdminTable.

Contains Round Trip Time (RTT) monitoring history definitions. The definitions in this table control what and how many entries will be placed into the rttMonHistoryCollectionTable. The history collection table is a rollover table. When the rttMonHistoryAdminNumLives index value exceeds its value defined in this table, the oldest corresponding ’lives’ group will be deleted and will be replaced with the new ’lives’ group. All other indices will only fill to their maximum size. NOTE: The maximum size of this table is defined to be the product of the rttMonCtrlAdminIndex times rttMonHistoryAdminNumLives times rttMonHistoryAdminNumBuckets times rttMonHistoryAdminNumSamples. NOTE WELL: Each of the ’Num’ objects values in this have a special behavior. When one of the objects is set to a value larger than the Rtt application can support the set will succeed, but the resultant value will be set to the applications maximum value. The setting management station must reread this object to verify the actual value. NOTE: this table is not applicable to http and jitter probes

Contains the Operational values for the probe, and the conceptual RTT control row. This table augments the rttMonCtrlAdminTable.

Contains the status of latest RTT operation. When the RttMonRttType is ’pathEcho’, operations performed to the hops along the path will be recorded in this table. This table augments the RTT definition table, rttMonCtrlAdminTable.

Contains the status of latest HTTP RTT operation.

Containsthe status of latest Jitter operation.

Contains the list of conceptual RTT control rows that will start to collect data when a reaction condition is violated and when rttMonReactAdminActionType is set to one of the following: - triggerOnly - trapAndTrigger - nmvtAndTrigger - trapNmvtAndTrigger or when a reaction condition is violated and when any of the row in rttMonReactTable has rttMonReactActionType as one of the following: - triggerOnly - trapAndTrigger The goal of this table is to define one or more additional conceptual RTT control rows that will become active and start to collect additional history and statistics (depending on the rows configuration values), when a problem has been detected. If the conceptual RTT control row is undefined, and a trigger occurs, no action will take place. If the conceptual RTT control row is scheduled to start at a later time, triggering that row will have no effect. If the conceptual RTT control row is currently active, triggering that row will have no effect on that row, but the rttMonReactTriggerOperState object will transition to ’active’. An entry in this table can only be triggered when it is not currently in a triggered state. The object rttMonReactTriggerOperState will reflect the state of each entry in this table.

Contains the operational state of each entry in the rttMonReactTriggerAdminTable. This table augments the RTT trigger definition table, rttMonReactTriggerAdminTable.

Contains the hop addresses in a Loose Source Routing path. Response times are computed along the specified path using ping. This maximum table size is limited by the size of the maximum number of hop addresses that can fit in an IP header, which is 8. The object rttMonEchoPathAdminEntry will reflect this tables maximum number of entries. This table is coupled with rttMonCtrlAdminStatus.

Contains Round Trip Time (RTT) monitoring group scheduling specific definitions. This table is used to create a conceptual group scheduling control row. The entries in this control row contain objects used to define group schedule configuration parameters. The objects of this table will be used to schedule a group of probes identified by the conceptual rows of the rttMonCtrlAdminTable.

Contains auto SAA L3 MPLS VPN definitions. The Auto SAA L3 MPLS VPN administration control is in multiple tables. This first table, is used to create a conceptual Auto SAA L3 MPLS VPN control row. The following tables contain objects which used in type specific configurations, scheduling and reaction configurations. All of these tables will create the same conceptual control row as this table using this table’s index as their own index. In order to a row in this table to become active the following objects must be defined. rttMplsVpnMonCtrlRttType, rttMplsVpnMonCtrlVrfName and rttMplsVpnMonSchedulePeriod.

Contains Auto SAA L3 MPLS VPN configured RTT operation specific definitions. This table is controlled via the rttMplsVpnMonCtrlTable. Entries in this table are created via the rttMplsVpnMonCtrlStatus object.

Contains auto SAA L3 MPLS VPN monitoring scheduling specific definitions. This table is controlled via the rttMplsVpnMonCtrlTable. Entries in this table are created via the rttMplsVpnMonCtrlStatus object.

Contains auto SAA L3 MPLS VPN Notification definitions. This table augments the rttMplsVpnMonCtrlTable.

Contains the reaction configurations. Each conceptual row in rttMonReactTable corresponds to a reaction configured for the probe defined in rttMonCtrlAdminTable. For each reaction configured for a probe there is an entry in the table. Each Probe can have multiple reactions and hence there can be multiple rows for a particular probe. This table is coupled with rttMonCtrlAdminTable.

Contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. Each ’group’ contains a series of ’path(s)’, each ’path’ contains a series of ’hop(s)’, each ’hop’ contains a series of ’statistics distribution bucket(s)’. Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group(s) is kept in the table until the table contains rttMonStatisticsAdminNumHourGroups groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonStatsCaptureStartTimeIndex object. If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to ’inactive’, the corresponding current hourly group in this table is ’frozen’, and a new hourly group is created when activity is resumed. If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to ’pending’ this whole table will be cleared and reset to its initial state. When the RttMonRttType is ’pathEcho’, the path exploration RTT requests’ statistics will not be accumulated in this table. NOTE: When the RttMonRttType is ’pathEcho’, a source to target rttMonStatsCapturePathIndex path will be created for each rttMonStatsCaptureStartTimeIndex to hold all errors that occur when a specific path had not been found or connection has not be setup. Using this rttMonStatsCaptureTable, a managing application can retrieve summarized data from accurately measured periods, which is synchronized across multiple conceptual RTT control rows. With the new hourly group creation being performed on a 60 minute period, the managing station has plenty of time to collect the data, and need not be concerned with the vagaries of network delays and lost PDU’s when trying to get matching data. Also, the managing station can spread the data gathering over a longer period, which removes the need for a flood of get requests in a short period which otherwise would occur.

Contains the exact behavior as the rttMonStatsCaptureTable, except it does not keep statistical distribution information. For a complete table description see the rttMonStatsCaptureTable object.

Contains the exact same behavior as the rttMonStatsCaptureTable, except it only keeps 60 minute group values. For a complete table description see the rttMonStatsCaptureTable object.

Contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. The operation of this table is same as that of rttMonStatsCaptureTable, except that this table can only store a maximum of 2 hours of data.

Contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. The operation of this table is same as that of rttMonStatsCaptureTable, except that this table will store 2 hours of data.

The Auto SAA L3 MPLS VPN LPD Group Database. The LPD Group statistics table contains summarized performance statistics for the LPD group. LPD Group - The set of ’single probes’ which are subset of the ’lspGroup’ probe traversing set of paths between two PE end points are grouped together and called as the LPD group. The LPD group will be uniquely referenced by the LPD Group ID. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group(s) is kept in the table until the table contains rttMplsVpnMonTypeLpdStatHours groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonLpdGrpStatsStartTimeIndex object.

Contains a point by point rolling history of the most recent RTT operations for each conceptual RTT control row. The rolling history of this information is maintained in a series of ’live(s)’, each containing a series of ’bucket(s)’, each ’bucket’ contains a series of ’sample(s)’. Each conceptual history row can have lives. A life is defined by the rttMonCtrlOperRttLife object. A new life will be created when rttMonCtrlOperState transitions ’active’. When the number of lives become greater than rttMonHistoryAdminNumLives the oldest life will be discarded and a new life will be created by incrementing the index. The path exploration RTT operation will be kept as an entry in this table.

Contains list of Snapshot Routing configuration entries.

Contains list of snapshot routing activity entries.

The table containing indications of which VLANs are preferred on which VLAN trunk ports. The preferred VLANs on a trunk port have a lower Path Cost value compared with the VLANs on the trunk not in the preferred list. If the value of stpxSpanningTreeType is neither pvstPlus(1) nor rapidPvstPlus(5), the configuration in this table has no effect.

A table containing a list of the ports for which a particular VLAN’s Spanning Tree has been found to have an inconsistency. Two types of inconsistency are discovered: 1) an inconsistency where two different port types have been plugged together; and 2) an inconsistency where different switches have different PVIDs for the same link.

A table containing a list of the bridge ports for which Spanning Tree RootGuard capability can be configured.

A table containing a list of the bridge ports for which a particular Spanning Tree instance has been found to have an root-inconsistency. The agent creates a new entry in this table whenever it detects a new root-inconsistency, and deletes entries when/soon after the inconsistency is no longer present.

A table containing the spanning tree port path cost configuration when stpxSpanningTreePathCostOperMode is long(2). If the value of stpxSpanningTreePathCostOperMode is short(1), this table is not instantiated.

This table contains one entry for each instance of MISTP and it contains stpxMISTPInstanceNumber entries, numbered from 1 to stpxMISTPInstanceNumber. This table is only instantiated when the value of stpxSpanningTreeType is mistp(2) or mistpPvstPlus(3).

A table containing the MISTP Instance Index of the VLANs for a particular management domain. This table is only instantiated when the value of stpxSpanningTreeType is mistp(2) or mistpPvstPlus(3).

A table containing the MISTP related information for the VLANs in the Edit Buffers for a particular management domain. This table is only instantiated when when the value of stpxSpanningTreeType is mistp(2) or mistpPvstPlus(3).

The table containing indications of which MISTP instances are preferred on which trunk ports. The preferred MISTP instances on a trunk port have a lower Path Cost value compared with the MISTP instances on the trunk not in the preferred list. This table is only instantiated when the value of stpxSpanningTreeType is mistp(2) or mistpPvstPlus(3).

A table containing a list of the bridge ports for which Spanning Tree LoopGuard capability can be configured.

A table containing a list of the bridge ports for which a particular Spanning Tree instance has been found to have a loop-inconsistency. The agent creates a new entry in this table whenever it detects a new loop-inconsistency, and deletes entries when/soon after the inconsistency is no longer present.

A table containing a list of the bridge ports for which Spanning Tree Port Fast Start can be configured.

A table containing a list of the bridge ports for a particular Spanning Tree Instance.

A table containing a list of the bridge ports for which a particular Spanning Tree instance has been detected to have BPDU skewing occurred since the object value of stpxBpduSkewingDetectionEnable was last changed to true(1). The agent creates a new entry in this table whenever a port in a particular Spanning Tree instance is detected to be BPDU skewed since the object value of stpxBpduSkewingDetectionEnable object is changed to true(1). The agent deletes all the entries in this table when the object value of stpxBpduSkewingDetectionEnable is changed to false(2) or the object value of stpxSpanningTreeType is changed.

This table contains MST instance information with one entry for an MST instance within the range of 0 to the object value of stpxMSTMaxInstanceNumber. This table is deprecated and replaced by stpxSMSTInstanceTable.

This table contains MST instance information in the Edit Buffer with one entry for each MST instance numbered from 0 to stpxMSTMaxInstanceNumber. This table is only instantiated when the stpxMSTRegionEditBufferStatus has the value of acquiredBySnmp(2). This table is deprecated and replaced by stpxSMSTInstanceEditTable.

The table containing indications of which MST instances are preferred on which trunk ports. The preferred MST instances on a trunk port have a lower Path Cost value compared with the MST instances on the trunk not in the preferred list.

A table containing port information for the MST Protocol on all the bridge ports existing on the system.

A table containing a list of the bridge ports for a particular MST instance. This table is only instantiated when the stpxSpanningTreeType is mst(4). This table is deprecated and replaced with stpxRSTPPortRoleTable.

A table containing port information for the RSTP Protocol on all the bridge ports existing in the system.

A table containing a list of the bridge ports for a particular Spanning Tree instance. This table is only instantiated when the stpxSpanningTreeType is mst(4) or rapidPvstPlus(5).

A table containing a list of the bridge ports for a particular Spanning Tree Instance. This table is only instantiated when the object value of stpxSpanningTreeType is rapidPvstPlus(5).

This table contains MST instance information for IEEE MST.

This table contains MST instance information in the Edit Buffer. This table is only instantiated when the object value of stpxMSTRegionEditBufferStatus has the value of acquiredBySnmp(2).

A table containing port information for the MST Protocol on all the bridge ports existing on the system. This table is only instantiated when the object value of stpxSpanningTreeType is mst(4).

Contains syslog messages generated by this device. All ’interesting’ syslog messages (i.e. severity).

Contains one row per physical entity. There is always at least one row for an “overall” physical entity.

Contains one row per logical entity.

Contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources, which are used to realize that logical entity.

Contains zero or more rows, representing mappings of logical entity and physical component to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical entity’s naming scope. A “wildcard” mechanism is provided to indicate that an identifier is associated with more than one logical entity.

Exposes the “container/containee” relationships between physical entities. This table provides all the information found by constructing the virtual containment tree for a given entPhysicalTable, but in a more direct format.

Contains statistics for a collection of ethernet-like interfaces attached to a particular system.

Statistics for a particular interface to an ethernet-like medium.

Contains an index value that uniquely identifies an interface to an ethernet-like medium.

Contains a count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check.

Contains a count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check.

Contains a count of frames that are involved in a single collision, and are subsequently transmitted successfully.

Contains a count of frames that are involved in more than one collision and are subsequently transmitted successfully.

Contains a count of times that the SQE TEST ERROR is received on a particular interface.

Contains a count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy.

The number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet.

Contains a count of frames for which transmission on a particular interface fails due to excessive collisions.

Contains a count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error.

The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface.

Contains a count of frames received on a particular interface that exceed the maximum permitted frame size.

Contains a count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error.

Contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface.

For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present.

The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined.

"'true' for interfaces operating at speeds above 1000 Mb/s that support Rate Control through lowering the average data rate of the MAC sublayer, with frame granularity, and 'false' otherwise."

Contains the current Rate Control mode of operation of the MAC sublayer of this interface.

Contains a collection of collision histograms for a particular set of interfaces.

Contains a cell in the histogram of per-frame collisions for a particular interface.

Contains number of per-frame media collisions for which a particular collision histogram cell represents the frequency on a particular interface.

Contains a count of individual MAC frames for which the transmission (successful or otherwise) on a particular interface occurs after the frame has experienced exactly the number of collisions in the associated dot3CollCount object.

Contains descriptive and status information about the MAC Control sublayer on the ethernet-like interfaces attached to a particular system.

Contains information about the MAC Control sublayer on a single ethernet-like interface.

Contains a count of MAC Control frames received on this interface that contain an opcode that is not supported by this device.

Contains a count of MAC Control frames received on this interface that contain an opcode that is not supported by this device.

Contains descriptive and status information about the MAC Control PAUSE function on the ethernet-like interfaces attached to a particular system.

Containing information about the MAC Control PAUSE function on a single ethernet-like interface.

Used to configure the default administrative PAUSE mode for this interface.

Reflects the PAUSE mode currently in use on this interface.

Contains a count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.

Contains a count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation.

Contains a count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.

Contains a count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation.

Contains 64-bit versions of error counters from the dot3StatsTable.

An entry containing 64-bit statistics for a single ethernet-like interface.

Contains a count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check.

Contains a count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check.

Contains a count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error.

Contains a count of frames received on a particular interface that exceed the maximum permitted frame size.

Contains a count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error.

For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present.

Lists the interface entries. The number of entries is given by the value of ifNumber.

Contains a list of interface entries and provides additional objects for the interface table.

Contains information on the relationships between the multiple sub-layers of network interfaces.

Contains entries for each address (broadcast, multicast, or uni-cast) for packets or frames the system receive on a particular interface.

Contains one entry per interface. It defines objects which allow a network manager to instruct an agent to test an interface for various faults.

The number of IMA groups configured on this system.

The IMA Group Configuration table.

A table mapping the ‘ifIndex’ values of ‘imaGroupIfIndex’ to the ‘imaGroupIndex’ values of the corresponding IMA group.

The IMA group Link Status and Configuration table.

Status of the IMA alarm.

The Type of IMA alarm declared or cleared. The value of ImaAlarmType identifies the type of alarm according to the definitions in the IMA specification.

The IMA Group Current table.

The IMA Group Interval table.

An entry in the IMA Group Total table.

The IMA Link Current table.

The IMA Link Interval table.

The IMA Link Total table.

The reservable attributes of the system’s in- terfaces.

Information describing the reserved flows us- ing the system’s interfaces.

The number of current ipForwardTable entries that are not invalid.

The IP Routing table.

The number of current ipCidrRouteTable entries that are not invalid.

The IP Routing table.

The number of current ipCidrRouteTable entries that are not invalid.

The number of current inetCidrRouteTable entries that are not invalid.

The IP Routing table.

The number of valid route entries discarded from inetCidrRouteTable.

Contains per-interface IPv4-specific information.

Contains per-interface IPv6-specific information.

Contains system wide, IP version specific traffic statistics. This table and the ipIfStatsTable contain similar objects whose difference is in their granularity. Where this table contains system wide traffic statistics, the ipIfStatsTable contains the same statistics but counted on a per-interface basis.

Contains per-interface traffic statistics. This table and the ipSystemStatsTable contain similar objects whose difference is in their granularity. Where this table contains per-interface statistics, the ipSystemStatsTable contains the same statistics, but counted on a system wide basis.

Allows the user to determine the source of an IP address or set of IP addresses, and allows other tables to share the information via pointer rather than by copying. For example, when the node configures both a unicast and anycast address for a prefix, the ipAddressPrefix objects for those addresses will point to a single row in this table. This table primarily provides support for IPv6 prefixes, and several of the objects are less meaningful for IPv4. The table continues to allow IPv4 addresses to allow future flexibility. In order to promote a common configuration, this document includes suggestions for default values for IPv4 prefixes. Each of these values may be overridden if an object is meaningful to the node. All prefixes used by this entity should be included in this table independent of how the entity learned the prefix. (This table isn’t limited to prefixes learned from router advertisements.)

Contains addressing information relevant to the entity’s interfaces. This table does not contain multicast address information. Tables for such information should be contained in multicast specific MIBs, such as RFC 3019. While this table is writable, the user will note that several objects, such as ipAddressOrigin, are not. The intention in allowing a user to write to this table is to allow them to add or remove any entry that isn’t permanent. The user should be allowed to modify objects and entries when that would not cause inconsistencies within the table. Allowing write access to objects, such as ipAddressOrigin, could allow a user to insert an entry and then label it incorrectly. Note well: When including IPv6 link-local addresses in this table, the entry must use an InetAddressType of ’ipv6z’ in order to differentiate between the possible interfaces.

The IP Address Translation table used for mapping from IP addresses to physical addresses. The Address Translation tables contain the IP address to ’physical’ address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. While many protocols may be used to populate this table, ARP and Neighbor Discovery are the most likely options.

Describes IPv6 unicast and multicast scope zones. For those objects that have names rather than numbers, the names were chosen to coincide with the names used in the IPv6 address architecture document.

Describes the default routers known to this entity.

Contains information used to construct router advertisements.

Contains generic system-wide ICMP counters.

Contains system-wide per-version, per-message type ICMP counters.

Contains addressing information relevant to this entity’s IPv4 addresses. This table has been deprecated, as a new IP version-neutral table has been added. It is loosely replaced by the ipAddressTable although several objects that weren’t deemed useful weren’t carried forward while another (ipAdEntReasmMaxSize) was moved to the ipv4InterfaceTable.

The IPv4 Address Translation table used for mapping from IPv4 addresses to physical addresses. This table has been deprecated, as a new IP version-neutral table has been added. It is loosely replaced by the ipNetToPhysicalTable.

Contains information about the MPLS Label Distribution Protocol Entities which exist on this Label Switch Router (LSR).

Provides a way to configure Generic Labels associated with LDP entities on the LSR.

Contains information about the ATM specific information which could be used in the ‘Optional Parameters’ and other ATM specific information.

The MPLS LDP Entity Configurable ATM Label Range Table. The purpose of this table is to provide a mechanism for specifying a contiguous range of vpi’s with a contiguous range of vci’s, or a ’label range’ for LDP Entities. LDP Entities which use ATM must have at least one entry in this table.

Contains information about the Optional Parameters to specify what this Entity is going to specify for Frame Relay specific LDP Intialization Messages.

Contains information about the Optional Parameters to specify what this Entity is going to specify for Frame Relay specific LDP Intialization Messages..

This table is a read-only table which augments the mplsLdpEntityTable. The purpose of this table is to keep statistical information about the LDP Entities on the LSR.

Information about LDP peers known by Entities in the mplsLdpEntityTable. The information in this table is based on information from the Entity-Peer interaction but is not appropriate for the mplsLdpSessionTable.

ContainsHello Adjacencies for Sessions.

Contains Sessions between the LDP Entities and LDP Peers. Each row represents a single session.

A table which relates Sessions in the ‘mplsLdpSessionTable’ and their label range intersections. There could be one or more label range intersections between an LDP Entity and LDP Peer using ATM as the underlying media. Each row represents a single label range intersection. NOTE: this table cannot use the ‘AUGMENTS’ clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable.

Contains Frame Relay label range intersections between the LDP Entities and LDP Peers. Each row represents a single label range intersection. NOTE: this table cannot use the ‘AUGMENTS’ clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable.

Contains statistics for Sessions between LDP Entities and LDP Peers.

This table ’extends’ the mplsLdpSessionTable. This table is used to store Label Address Information from Label Address Messages received by this LSR from Peers. This table is read-only and should be updated when Label Withdraw Address Messages are received, i.e. Rows should be deleted as apropriate. NOTE: since more than one address may be contained in a Label Address Message, this table ’extends’, rather than ’AUGMENTS’ the mplsLdpSessionTable’s information.

Represents LIB (Label Information Base) Information. The table is read-only.

Represents the FEC (Forwarding Equivalence Class) Information associated with an LSP. The table is read-only.

Specifies per-interface MPLS capability and associated information.

Provides MPLS performance information on a per-interface basis.

Contains a collection of incoming segments to an LSR.

Contains statistical information for incoming MPLS segments to an LSR.

Contains a representation of the outgoing segments from an LSR.

Contains statistical information about outgoing segments from an LSR. The counters in this entry should behave in a manner similar to that of the interface.

Specifies information for switching between LSP segments. It supports point-to-point, point-to-multipoint and multipoint-to-point connections. mplsLabelStackTable specifies the label stack information for a cross-connect LSR and is referred to from mplsXCTable.

Specifies the label stack to be pushed onto a packet, beneath the top label. Entries into this table are referred to from mplsXCTable.

Specifies the Traffic Parameter objects for in and out-segments.

Chassis card table.

Chassis card table.

Total Size in Octets of Flash memory.

Unused Size in Octets of Flash memory.

Provides the type of Flash controller (either CCTL or CCTL2) installed in the router.

Provides the type of Flash Card installed in the router.

State of the VPP DIP jumper on the Flash memory card. Files can be written to the Flash memory card only if the VPP DIP jumper is turned on.

Request to erase flash memory.

Indicates the value of sysUptime the last time Flash memory was erased.

Status of current or last flash erasing.

Write flash entry to tftp server. Value should be the name of the flash entry to send.

Indicates the value of sysUpTime the last time a file was transfered from Flash memory on the router to a TFTP host.

Status of current or last flash to net transfer.

Write flash entry from tftp server. Value should be the name of the flash entry to write.

Indicates the value of sysUpTime the last time file was copied from a Trivial File Transfer Protocol(TFTP) server to the Flash memory on the router.

Status of current or last net to flash transfer.

Status of the availability of flash.

Number of entries in the flash directory.

Contains a list of interface entries.

Contains a list of card entries for 4T, HSSI, Mx serial or FSIP.

Contains a list of IP address entries.

Contains a list of IP routing entries.

Contains a list of accounting entries.

Contains a list of IP checkpoint accounting entries.

Contains a list of terminal server line entries.

Contains a list of terminal server line and session entries.

Information describing the configured parameters and cumulative statistics of the router’s attached areas.

The OSPF Process’s Link State Database. This table is meant for Opaque LSA’s

The OSPF Interface Table describes the inter- faces from the viewpoint of OSPF.

Information about this router’s virtual inter- faces.

Information about this router’s sham links

Information about this router’s sham links.

A table of sham link neighbor information.

The OSPF Process’s Link-Local Link State Database for non-virtual links.

The OSPF Process’s Link-Local Link State Database for virtual links.

OSPFv3 Process’s AS-Scope Link State Database (LSDB). The LSDB contains the AS-Scope Link State Advertisements from throughout the areas that the device is attached to.

OSPFv3 Process's AS-Scope LSDB. The LSDB contains the AS-Scope Link State Advertisements from throughout the areas that the device is attached to.

OSPFv3 Process's Area-Scope LSDB. The LSDB contains the Area-Scope Link State Advertisements from throughout the area that the device is attached to.

OSPFv3 Process's Link-Scope LSDB for non-virtual interfaces. The LSDB contains the Link-Scope Link State Advertisements from the interfaces that the device is attached to

Host/Metric Table indicates what hosts are directly attached to the router and their corresponding metrics.

OSPFv3 Interface Table describes the interfaces from the viewpoint of OSPFv3.

Information about this router's virtual interfaces that the OSPFv3 Process is configured to carry on.

A table describing all neighbors in the locality of the OSPFv3 router.

Table describing all virtual neighbors.

Area Aggregate Table acts as an adjunct to the Area Table. It describes those address aggregates that are configured to be propagated from an area. Its purpose is to reduce the amount of information that is known beyond an Area's borders. A range of IPv6 prefixes specified by a prefix/prefix length pair.

Note If ranges are configured such that one range subsumes another range the most specific match is the preferred one.

A 32-bit integer uniquely identifying the router in the AS. To ensure uniqueness, this may default to the value of one of the router's IPv4 interface addresses if IPv4 is configured on the router

A table describing all configured neighbors. This table provides OSPFv3 information for sending OSPFv3 packets to potential neighbors and is typically used on NBMA and Point-to-Multipoint networks.

Fields that are required for notifications.

Contains a list of interface entries. The number of entries is given by the value of ifNumber.

The Address Translation tables contain the NetworkAddress to ‘physical’ address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries.

Contains addressing information relevant to this entity’s IP addresses.

This entity’s IP Routing table.

The IP Address Translation table used for mapping from IP addresses to physical addresses.

Contains TCP connection-specific information.

Contains UDP listener information.

The EGP neighbor table.

Contains a list of Ethernet statistics entries.

Contains a list of history control entries.

Contains a list of Ethernet history entries.

Contains a list of alarm entries.

Contains a list of host table control entries.

Contains a list of host entries.

Contains a list of time-ordered host table entries.

Contains a list of top N host control entries.

Contains a list of top N host entries.

Contains a list of information entries for the traffic matrix on each interface.

Contains a list of traffic matrix entries indexed by source and destination MAC address.

Contains a list of traffic matrix entries indexed by destination and source MAC address.

Contains a list of packet filter entries.

Contains a list of packet channel entries.

Contains a list of buffers control entries.

Contains a list of packets captured off of a channel.

Contains a list of events to be generated.

Contains a list of events that have been logged.

Lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don’t support the application layer groups.

Controls the setup of protocol type distribution statistics tables. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of protocol statistics is available. Rationale: This table controls collection of very basic statistics for any or all of the protocols detected on a given interface. An NMS can use this table to quickly determine bandwidth allocation utilized by different protocols. A media-specific statistics collection could also be configured (e.g. etherStats, trPStats) to easily obtain total frame, octet, and droppedEvents for the same interface.

An entry is made in this table for every protocol in the protocolDirTable which has been seen in at least one packet. Counters are updated in this table for every protocol type that is encountered when parsing a packet, but no counters are updated for packets with MAC-layer errors. Note that if a protocolDirEntry is deleted, all associated entries in this table are removed.

Controls the collection of network layer address to physical address to interface mappings. Note that this is not like the typical RMON controlTable and dataTable in which each entry creates its own data table. Each entry in this table enables the discovery of addresses on a new interface and the placement of address mappings into the central addressMapTable. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of address mappings is available.

Contains network layer address to physical address to interface mappings. The probe will add entries to this table based on the source MAC and network addresses seen in packets without MAC-level errors. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirAddressMapConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirAddressMapConfig value of supportedOff(2).

Contains higher layer (i.e. non-MAC) host table control entries. These entries will enable the collection of the network and application level host tables indexed by network addresses. Both the network and application level host tables are controlled by this table is so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore (note that if an implementation stores application layer host records in memory, it can derive network layer host records from them). Entries in the nlHostTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alHostTable, entries in the alHostTable will be created on behalf of each entry in this table. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of host statistics is available.

A collection of statistics for a particular network layer address that has been discovered on an interface of this device. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors.

Contains higher layer (i.e. non-MAC) matrix control entries. These entries will enable the collection of the network and application level matrix tables containing conversation statistics indexed by pairs of network addresses. Both the network and application level matrix tables are controlled by this table is so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore (note that if an implementation stores application layer matrix records in memory, it can derive network layer matrix records from them). Entries in the nlMatrixSDTable and nlMatrixDSTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alMatrix tables, entries in the alMatrix tables will be created on behalf of each entry in this table.

Contains traffic matrix entries which collect statistics for conversations between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all conversations from a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixDSTable with the same source address and destination address.

Contains traffic matrix entries which collect statistics for conversations between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all conversations to a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixSDTable with the same source address and destination address.

Contains a set of parameters that control the creation of a report of the top N matrix entries according to a selected metric.

Contains a set of statistics for those network layer matrix entries that have counted the highest number of octets or packets.

Contains a collection of statistics for a particular protocol from a particular network address that has been discovered on an interface of this device. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address exists in the nlHostTable and will be deleted from this table if their address is deleted from the nlHostTable.

Contains a list of application traffic matrix entries which collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all statistics from a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixSDTable and will be deleted from this table if the address pair is deleted from the nlMatrixSDTable.

Contains application traffic matrix entries which collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all statistics to a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixDSTable and will be deleted from this table if the address pair is deleted from the nlMatrixDSTable.

Contains a set of parameters that control the creation of a report of the top N matrix entries according to a selected metric.

Contains a set of statistics for those application layer matrix entries that have counted the highest number of octets or packets.

Contains a list of data-collection configuration entries.

Contains a list of data-collection configuration entries.

Contains a list of user defined history entries.

Contains serial interface configuration entries. This data will be stored in non-volatile memory and preserved across probe resets or power loss.

Contains netConfigEntries.

Contains trap destination entries.

Contains serialConnectionEntries.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

Provides a variable-length packet filter feature to the RMON-1 filter table.

An SNMP engine's administratively-unique identifier. This information SHOULD be stored in non-volatile storage so that it remains constant across re-initializations of the SNMP engine.

The number of times that the SNMP engine has (re-)initialized itself since snmpEngineID was last configured.

The number of seconds since the value of the snmpEngineBoots object last changed. When incrementing this object's value would cause it to exceed its maximum, snmpEngineBoots is incremented as if a re-initialization had occurred, and this object's value consequently reverts to zero.

The maximum length in octets of an SNMP message which this SNMP engine can send or receive and process, determined as the minimum of the maximum message size values supported among all of the transports available to and supported by the engine.

snmpTargetAddrTable

A table of transport addresses to be used in the generation of SNMP messages.

snmpTargetParamsTable

A table of SNMP target information to be used in the generation of SNMP messages.

The (conceptual) table listing the capabilities of the local SNMP application acting as a command responder with respect to various MIB modules. SNMP entities having dynamically-configurable support of MIB modules will have a dynamically-varying number of conceptual rows.

Contains information about existing TCP connections. Note that unlike earlier TCP MIBs, there is a separate table for connections in the LISTEN state.

Contains information about TCP listeners. A listening application can be represented in three possible ways: 1. An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a tcpListenerLocalAddressType of unknown (0) and a tcpListenerLocalAddress of ’’h (a zero-length octet-string). 2. An application that is willing to accept only IPv4 or IPv6 datagrams is represented by a tcpListenerLocalAddressType of the appropriate address type and a tcpListenerLocalAddress of ’0.0.0.0’ or ’::’ respectively. 3. An application that is listening for data destined only to a specific IP address, but from any remote system, is represented by a tcpListenerLocalAddressType of an appropriate address type, with tcpListenerLocalAddress as the specific local address. NOTE: The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 ’sockets’ to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1)).

Contains information about existing IPv4-specific TCP connections or listeners. This table has been deprecated in favor of the version neutral tcpConnectionTable.

Contains information about this entity’s UDP endpoints on which a local application is currently accepting or sending datagrams. The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 ’sockets’ to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1). Unlike the udpTable in RFC 2013, this table also allows the representation of an application that completely specifies both local and remote addresses and ports. A listening application is represented in three possible ways: 1) An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a udpEndpointLocalAddressType of unknown(0) and a udpEndpointLocalAddress of ’’h (a zero-length octet-string). 2) An application that is willing to accept only IPv4 or only IPv6 datagrams is represented by a udpEndpointLocalAddressType of the appropriate address type and a udpEndpointLocalAddress of ’0.0.0.0’ or ’::’ respectively. 3) An application that is listening for datagrams only for a specific IP address but from any remote system is represented by a udpEndpointLocalAddressType of the appropriate address type, with udpEndpointLocalAddress specifying the local address. In all cases where the remote is a wildcard, the udpEndpointRemoteAddressType is unknown(0), the udpEndpointRemoteAddress is ’’h (a zero-length octet-string), and the udpEndpointRemotePort is 0. If the operating system is demultiplexing UDP packets by remote address and port, or if the application has ’connected’ the socket specifying a default remote address and port, the udpEndpointRemote* values should be used to reflect this.

Contains IPv4-specific UDP listener information. It contains information about all local IPv4 UDP end-points on which an application is currently accepting datagrams.