Professional Network and Server
Monitoring Tool

Download page Order page

List of MIBs
2 3 8 A B C D E F G H I J L M N O P Q R S T U V W X Z

C-PRODUCT-BASE-L-SPECIFIC
C-PRODUCT-DS3-MIB
C-PRODUCT-E3-MIB
C-PRODUCT-TRAP-MIB
CABLE-DIAG-MIB
The MIB module for determining the status of the cables attached to the device
Cajun IPX SAP Private MIB
Cajun IPX RIP Private MIB
CAJUN-POLICY-CAPABILITIES
The MIB module for Lucent Policy Enabled CajunRules Products.
CALISTA-DPA-MIB
This MIB is for management of Cisco DPA voicemail gateway devices. These allow interfacing of Octel voicemail systems with Cisco CallManager.
CB9000-PACKET-MODULE-MIB
CHASSIS-MIB
CHIPCOMMIB
CIOMIB
This MIB contains status information about storage devices.
CISCO-5800-HEALTH-MON-MIB
MIB describing Network Access Server shelf monitoring features of the SC3640 System Controller.
CISCO-6400-CHASSIS-MIB
MIB specific to the Cisco 6400NSP product.
CISCO-90-MIB
The Cisco 90i Series MIB
CISCO-AAA-CLIENT-CAPABILITY
The capabilities description of CISCO-AAA-CLIENT-MIB.
CISCO-AAA-SERVER-CAPABILITY
Agent capbility mib for CISCO-AAA-SERVER-MIB.my
CISCO-AAA-SERVER-EXT-CAPABILITY
Agent Capabilities for CISCO-AAA-SERVER-EXT-MIB.my
CISCO-AAA-SERVER-EXT-MIB
Extension to the CISCO-AAA-SERVER-MIB
CISCO-AAA-SERVER-MIB
The MIB for monitoring communications and status of AAA Server operation.
CISCO-AAL5-EXT-MIB
This MIB is the RFC 1695 extension for Cisco product. It provides the additional AAL5 performance statistics of a VCC from RFC 1695
CISCO-AAL5-MIB
Cisco Enterprise AAL5 MIB file that provide AAL5specific information that are either excluded by RFC 1695 or specific to Cisco product.
CISCO-ADMISSION-POLICY-MIB
This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network.
CISCO-ADSL-CAP-LINE-MIB
Definitions of managed objects describing ADSL CAP line interfaces.
CISCO-ADSL-DMT-LINE-MIB
Definitions of managed objects for ADSL lines implementing DMT line code (Cisco-specific extensions).
CISCO-ALPS-MIB
The ALPS MIB provides configuration and perational information for Cisco's Airline protocol support for IBM-P1024B(ALC)and Unisys-P1024C(UTS)protocols encapsulation over TCP/IP.
CISCO-AON-STATUS-MIB
This MIB module defines managed objects that facilitate the management of AON node.
CISCO-APPLIANCE-REDUNDANCY-MIB
This mib defines SNMP objects to report the status of High Availability functionality in Cisco network management appliances.
CISCO-APPLICATION-ACCELERATION-CAPABILITY
The capabilities description of CISCO-APPLICATION-ACCELERATION-MIB.
CISCO-APPLICATION-ACCELERATION-MIB
This is a MIB for managing Application Acceleration System(s). This MIB includes instrumentation for providing the performance statistics and status of the condenser which is the core of the A pplication Acceleration System. A condenser is a software accelerator that applies several optimization techniques to accelerate Web application access.
CISCO-APS-EXT-MIB
CISCO-APS-EXT-MIB provides for all protection/working channels, the associated working/protection channel IP address
CISCO-APS-MIB
This management information module supports theconfiguration and management of SONET linear APS groups.
CISCO-ASN-GATEWAY-MIB
This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio (802.16 ) technology.
CISCO-ASPP-MIB
The Cisco MIB for the asynchronous polled Communications protocol as implemented in the ASP Tunneling feature. This MIB provides information relating to the ASP interfaces in a router; the correspondin g tunnel interface can be accessed via CISCO-BSTUN-MIB.
CISCO-ATM-ACCESS-LIST-MIB
A MIB for configuration and control of access control filters in an ATM switch
CISCO-ATM-ADDR-MIB
The MIB contains a list of the valid calling party addresses for a UNI on a per interface basis.
CISCO-ATM-CAPABILITY
The Agent Capabilities for ATM-MIB.
CISCO-ATM-CELL-LAYER-CAPABILITY
Capability file for CISCO-ATM-CELL-LAYER-MIB
CISCO-ATM-CELL-LAYER-MIB
The MIB module to describe ATM cell layer objects and statistics of a physical line.
CISCO-ATM-CONN-INFO-MIB
The MIB module for providing the parameters configured on an ATM interface.
CISCO-ATM-CONN-MIB
This MIB module is a cisco extension to VPL/VCL table defined in rfc1695 for ATM switch connection management
CISCO-ATM-DUAL-PHY-MIB
The MIB module for gathering physical layer error statistics from the ATM uplink card of a Catalyst 5000 device. It also allows users to select the "active" phy in the above card in a redundant phy configuration.
CISCO-ATM-EXT-MIB
This MIB is an extension to the Cisco ATM MIBmodule for managing ATM implementations.
CISCO-ATM-IF-MIB
The MIB module for an extension to rfc1695 ATM interface table.
CISCO-ATM-IF-PHYS-MIB
Subset of SONET and DS3 MIB for LS1010.
CISCO-ATM-NETWORK-CLOCK-MIB
The MIB module for management of network clock distribution and the Network Clock Distribution Protocol (NCDP) in Cisco devices
CISCO-ATM-PVC-MIB
This MIB allows users to configure a PVC on an ATM uplink card of a This MIB allows users to configure a PVC on an ATM uplink card of a Catalyst 5000 device, and then bind that PVC to a Virtual LAN (VLAN).
CISCO-ATM-PVCTRAP-EXTN-CAPABILITY
The Agent Capabilities for CISCO-ATM-PVCTRAP-EXTN-MIB.
CISCO-ATM-PVCTRAP-EXTN-MIB
This MIB Module is a supplement to theCISCO-IETF-ATM2-PVCTRAP-MIB
CISCO-ATM-QOS-MIB
CISCO-ATM-QOS-MIB is created to provide ATM QoS information in these areas:1. Traffic shaping on a per-VC basis2. Traffic shaping on a per-VP basis3. Per-VC queuing/buffering
CISCO-ATM-RM-MIB
The MIB module which complements standard ATM MIBs for Cisco devices, for Resource Management.
CISCO-ATM-SERVICE-REGISTRY-MIB
A MIB module to allow an NMS to monitor and configure the information which an ATM switch makes available via the ILMI's Service Registry Table.
CISCO-ATM-SIG-DIAG-MIB
Contains objects to facilitate diagnosis of signaling failures in ATM networks.
CISCO-ATM-SWITCH-ADDR-MIB
ATM Switch address MIB.
CISCO-ATM-SWITCH-CUG-MIB
This MIB is for managing Closed User Groups on an ATM Switch.
CISCO-ATM-SWITCH-FR-IWF-MIB
A MIB module for managing Frame Relay to ATM interworking connections, and Frame Relay to Frame Relay switched connections via an ATM switching fabric, on a Cisco ATM switch.
CISCO-ATM-SWITCH-FR-RM-MIB
This MIB module describes a set of objects used for switch Resource Management (RM) for Frame Relay/Frame based User-to-Network (FUNI) to ATM interworking function (IWF) connections.
CISCO-ATM-TRAFFIC-MIB
This MIB module is an extension to traffic OIDsand variables defined in rfc1695.
CISCO-ATM-TRUNK-MIB
The MIB for voice and Nx64 over ATM Trunking applications.
CISCO-ATM-TRUNK-STAT-CAPABILITY
The capabilities description of CISCO-ATM-TRUNK-STAT-MIB.
CISCO-ATM-VIRTUAL-IF-CAPABILITY
Capability file for CISCO-ATM-VIRTUAL-IF-MIB.my
CISCO-ATM-VIRTUAL-IF-MIB
The MIB module to manage ATM Virtual interface objects. ATM virtual interfaces are configured on a physical line.
CISCO-ATM2-MIB
Contains a subset of the draft Supplemental AToM MIB.
CISCO-AUTH-FRAMEWORK-CAPABILITY
The capabilities description of CISCO-AUTH-FRAMEWORK-MIB.
CISCO-AUTH-FRAMEWORK-MIB
MIB module for Authentication Framework in the system
CISCO-AUTHORIZATION-STATS-MIB
The Cisco User Authorization Statistics MIB models,counters and objects that are of management interest.
CISCO-BBSM-MIB
This mib is designed to send BBSM specific notifications. There are variables that contain detail data that are bind to a notification. The SNMP Manager that receives the notifications should look at the binding variables for further details of the notification data. BBSM stands for Building Broadband Service Manager. It is a software-based service platform that enables customers to create, market, and operate b roadband access services, such as high-speed Internet access with plug-and-play, multiple authentication and billing options and Web-based management, reporting, and configuration.
CISCO-BCP-MIB
This MIB module describes the Managed Objects forof Bridge Control Protocol (RFC2878).
CISCO-BERT-CAPABILITY
The Agent Capabilities for CISCO-BERT-MIB for Cisco Products Series.
CISCO-BERT-MIB
The MIB module to manage ATM Virtual interface objects. ATM virtual interfaces are configured on a physical line.
CISCO-BGP-POLICY-ACCOUNTING-MIB
The BGP policy accounting MIB defines fourcounters called cbpAcctInPacketCount, cbpAcctInOctetCount, cbpAcctOutPacketCount and cbpAcctOutOctetCount. Customer traffic on ingress and egress into an ISP router is classified into 1 to 64 traffic types and these are accumulated in the mentioned counters. These statistics can be used for billing purposes.
CISCO-BGP-POLICY-ACCOUNTING-MIB-CAPABILITY
CISCO-BGP-POLICY-ACCOUNTING-MIB capabilities for IOS XR release 3.0
CISCO-BGP4-MIB
Cisco BGP MIB
CISCO-BITS-CLOCK-CAPABILITY
Agent capabilities for the CISCO-BITS-CLOCK-MIB.
CISCO-BITS-CLOCK-MIB
This MIB provides information on Building Integrated Timing Supply(BITS) clocking sources and modes of operations. It is used to generate notifications to indicate when clocking sources change roles or become unavailable. GR-1233CORE sections 8.1.2 Major Alarms and 8.1.3 Critical Alarms
CISCO-BOOT-HWDIAGS-MIB
This MIB is used to configure those devices that supportboot-time hardware diagnostics. It provides the reports about the respective diagnostic tests executed by the devices as well.
CISCO-BRIDGE-CAPABILITY
The capabilities description of BRIDGE-MIB.
CISCO-BRIDGE-DOMAIN-MIB
A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternative to 802.1D bridge-groups and to 802.1Q VLAN bridging. Bridge domain is the service specification, and specifies the broadcast domain number on which this frame of this particular service instance must be made available on. The physical and virtual interfaces that can comprise a bridge domain are heterogeneous in nature comprising Ethernet service instances, WAN Virtual Circuit for ATM or Frame Relay and VFIs. However, the frame encapsulations for all interface types are essentially Ethernet. Without bridge-domains, VLANs would have to be globally unique per device and one would only be restricted to the theoretical maximum of 4095 VLANs for single tagged traffic. However with the introduction of bridge-domains, one can associate a service instance with a bridge-domain and all service instances in the same bridge-domain form a broadcast domain. Bridge-domain ID determines the broadcast domain and the VLAN id is merely used to match and map traffic. With bridge domain feature configured VLAN IDs would be unique per interface only and not globally.
CISCO-BRIDGE-EXT-CAPABILITY
Agent capabilities for CISCO-BRIDGE-EXT-MIB.
CISCO-BRIDGE-EXT-MIB
A MIB module for extending BRIDGE-MIB specified in RFC 1493.
CISCO-BSC-MIB
The BSC MIB provides the configuration and operational information on Cisco's Binary Synchronous Communications implementation. The fo llowing entities are managed: 1) BSC ports (serial interfaces) 2) BSC Control Units (stations on a port)
CISCO-BSTUN-MIB
The Cisco MIB for the Blocked Serial Tunneling protocol used to tunnel blocked serial protocols (e.g. BSC) between a Cisco router and another C isco router or host.
CISCO-BULK-FILE-CAPABILITY
CISCO-BULK-FILE-MIB Capabilities for IOS XR release 2.0
CISCO-BULK-FILE-MIB
The MIB module for creating and deleting bulk files of SNMP data for file transfer
CISCO-BUS-MIB
The Cisco MIB for monitoring the LANE BUS component. NOTE: Initial support for this MIB is read-only. Creation and deletion of the LANE BUS component is facilitated through the LES MIB (the BUS is fate shared with the LES).
CISCO-C12000-IF-HC-COUNTERS-MIB
An experimental mib module, for the 11.2GS train for the c12000 series, to break the 64 bit counters of ifHCInOctets, ifHCInUcastPkts, ifHCOutOctets, and ifHCOutUcastPkts into 2 32 bit counters that can be retrieved without the need for SNMPv2 or up.
CISCO-C2900-MIB
The MIB module for Catalyst 2900 enterprise specific information
CISCO-C6200-MIB
This Cisco MIB is the experimental platform MIB for the Cisco 6200, a DSL Access Multiplexor. This MIB provides configuration and performance statistics for this platform.
CISCO-C8500-REDUNDANCY-MIB
This MIB allows management of redundancy of CPU and switch cards for the Catalyst 8540 switch, and other products with similar implementations.
CISCO-CABLE-ADM-C-CAPABILITY
Agent capabilities for CISCO-CABLE-ADMISSION-CTR-MIB
CISCO-CABLE-ADMISSION-CTRL-MIB
SNMP MIB for Cisco Cable Service Flow Admission Control feature.
CISCO-CABLE-AVAILABILITY-MIB
This is the MIB module for management of Hot Standby Connection to Connection Protocol (HCCP) features. HCCP is a Cisco proprietary solution for High System Availability for Cable Modem Termination Systems (CMTS).
CISCO-CABLE-DIAG-CAPABILITY
The agent capabilities description of CISCO-CABLE-DIAG-MIB.
CISCO-CABLE-DIAG-MIB
This MIB module defines objects for managing cable diagnostic test capabilites supported by the Cisco devices.
CISCO-CABLE-DSG-IF-MIB
This is the MIB Module for the DOCSIS Set-top Gateway (DSG). The DSG provides a one-way IP datagram transport for Out-Of-Band (OOB) messaging to cable set-top terminals. The one-way IP datagram transport is called a DSG Tunnel. A DSG Tunnel is a multicast IP datagram stream originating at the DOCSIS Set-top Gateway and carrying Out-Of-Band messages intended for set-top terminals. It is carried over one or more downstream DOCSIS channels and is identified by a well know Ethernet unicast MAC address. The well-known Ethernet unicast MAC address is reserved and published by the Conditional Access/Point Of Deployment (CA/POD) provider. A CA/POD provider is limited to eight DSG Tunnels to transport their OOB Messaging. Multiple DSG Tunnels may exist on a single downstream DOCSIS channel.
CISCO-CABLE-L2VPN-MIB
This MIB module defines managed objects that facilitate the management of Cisco devices complying to the DOCSIS L2VPN Feature for IP/MPLS pseudo-wire. The Cisco CMTS implementation of IP/MPLS pseudo-wire is based on DOCSIS BSOD L2VPN specification. The information available through this MIB includes: Mapping information between various configuration of the pseudo-wire pertaining to DOCSIS BSOD L2VPN. The MIB tables implemented give quick access to information using either Cable Modem MAC address/VPN, peer IP address/VCID or L2vpnIndex as index in tables.
CISCO-CABLE-METERING-MIB
MIB module for Usage based Metering for DOCSIS-compliant CMTS
CISCO-CABLE-QOS-MONITOR-MIB
Provides Substriber Traffic Management configuration for CMTS.
CISCO-CABLE-SPECTRUM-CAPABILITY
Agent capabilities for CISCO-CABLE-SPECTRUM-MIB
CISCO-CABLE-SPECTRUM-MIB
Cisco Data Over Cable Spectrum Management MIB file
CISCO-CABLE-WIDEBAND-CAPABILITY
Agent capabilities for CISCO-CABLE-WIDEBAND-MIB
CISCO-CABLE-WIDEBAND-MIB
This is the MIB module for the support of Channel Bonding Protocol for the Cable Modem Termination System (CMTS).
CISCO-CAC-SYSTEM-MIB
This MIB module provides provisioning and monitoring Call Admission Control (CAC).
CISCO-CALL-APPLICATION-MIB
This MIB allows management of call applications on a network device. A 'call application' is a software module that processes calls, such as data, voice, video, or fax calls.
CISCO-CALL-HISTORY-MIB
The Cisco Call History MIB, which describes and stores the call information of the Cisco device for accounting purposes.
CISCO-CALL-RESOURCE-POOL-MIB
The MIB provides configuration and monitoring of call resource pools and acceptance, rejection, and resource assignment based on call attributes.
CISCO-CALL-TRACKER-MIB
Enhancement to Call Signaling Type.
CISCO-CALL-TRACKER-TCP-MIB
This MIB module provides TCP service connection related data for tracking the progress and status of a call.
CISCO-CALLHOME-CAPABILITY
The capabilities description ofCISCO-CALLHOME-MIB.
CISCO-CALLHOME-MIB
The MIB module for the management of Call Home feature within the framework of Cisco's Call Home architecture.
CISCO-CAR-MIB
This Cisco MIB provides the packet filtering information implemented by the Committed Access Rate (CAR) feature of a Cisco Layer 3 service.
CISCO-CAS-IF-CAPABILITY
CISCO-CAS-IF-EXT-CAPABILITY
The agent capabilities for CISCO-CAS-IF-EXT-MIB.
CISCO-CAS-IF-EXT-MIB
The MIB module is an extension of CISCO-CAS-IF-MIB.It defines the attributes of a voice interface.
CISCO-CAS-IF-MIB
Channel Associated Signal Interface MIB module. This MIB manages the generic CAS Channel Associated Signal)or DS0 clear channel Interfaces in the router.
CISCO-CASA-FA-CAPABILITY
Cisco forwarding agent capability mib
CISCO-CASA-FA-MIB
MIB for CASA forwarding agent.
CISCO-CASA-MIB
MIB for CASA entities
CISCO-CAT6K-CROSSBAR-CAPABILITY.
The capabilities description of CISCO-CAT6K-CROSSBAR-MIB.
CISCO-CAT6K-CROSSBAR-MIB.
The Catalyst 6000 Crossbar MIB provides instrumentation for configuration and operation of the crossbar switching fabric modu le, and additional functionalities for switching bus and internal bus, etc.
CISCO-CATOS-ACL-QOS-CAPABILITY
The agent capabilities description of CISCO-CATOS-ACL-QOS-MIB
CISCO-CATOS-ACL-QOS-MIB
This MIB module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on Cisco Catalyst 5000/6000 series switch running CatOS.
CISCO-CBP-TARGET-MIB
Managed objects to define targets' relationships to class-based policies.
CISCO-CBP-TARGET-TC-MIB
Textual Conventions for class based policy target representation.
CISCO-CCM-CAPABILITY
Agent capabilities for CISCO-CCM-MIB
CISCO-CCM-MIB
This MIB Module is for the management of a Cisco Unified Communications Manager(CUCM) application running with a Cisco Communication Network (CCN) System.
CISCO-CCME-MIB
This MIB allows management of Cisco CallManager Express (CCME) feature in Cisco IOS.
CISCO-CDL-MIB
This MIB module defines objects to manage Converged Data Link (CDL).
CISCO-CDMA-AHDLC-MIB
Managed Object Definitions for HDLC framing/deframing
CISCO-CDMA-PDSN-CRP-MIB
CISCO-CDMA-PDSN-EXT-MIB
This MIB is to support the CDMA PDSN(Packet Data Serving Node)4.0 feature of Cisco IOS.
CISCO-CDMA-PDSN-MIB
This MIB is to support the CDMA PDSN(Packet Data Serving Node)feature of Cisco IOS.
CISCO-CDP-CAPABILITY
CISCO-CDP-MIB capabilities for IOS XR release 2.0
CISCO-CDP-MIB
The MIB module for management of the Cisco Discovery Protocol in Cisco devices.
CISCO-CDSTV-AUTHMGR-MIB
This MIB module defines objects that describe the configuration of the authentication manager for the Cisco Content Delivery System for TV (CDS-TV). CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients. Authentication Manager is an optional feature of CDS-TV and is only for specific RTSP environments (EventIS). The Authentication Manager communicates with the back-office to validate a request received from a set-top box before setting up a session.
CISCO-CDSTV-BWMGR-MIB
This MIB module defines Bandwidth Manager configuration objects that facilitate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients. The Bandwidth Manager runs on the master streamer and keeps track of allocated streams and VOD network resources.
CISCO-CDSTV-CS-STATS-MIB
This MIB module defines objects describing the caching and streaming statistics objects that facilitate the management of the Cisco CDS-TV product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or STB clients.
CISCO-CDSTV-FSI-MIB
This MIB module defines FSI configurartion objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients.
CISCO-CDSTV-INGEST-TUNING-MIB
This MIB module defines ingest tuning configuration objects that facilitate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients.
CISCO-CDSTV-INGESTMGR-MIB
This MIB module defines ingest manager configuration objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients.
CISCO-CDSTV-ISA-MIB
This MIB module defines ISA configuration objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients.
CISCO-CDSTV-SERVER-MIB
This MIB module defines server configuration that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients.
CISCO-CDSTV-SERVICES-MIB
This MIB module defines service monitoring objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) product family. CDS-TV is a suite of products and software applications providing ingest, storage, caching, streaming, playout and on-demand delivery of video to television or set-top-box clients.
CISCO-CEF-MIB
This MIB module is used to manage CISCO Express Forwarding (CEF).
CISCO-CEF-TC
This MIB module is used to define Textual Conventions for Cisco Express Forwarding (CEF).
CISCO-CFS-MIB
MIB for managing CFS infrastructure
CISCO-CHANNEL-MIB
The Cisco Channel Interface Processor MIB, which allows management of the Channel Interface Processor or CIP.
CISCO-CIDS-MIB
Cisco Intrusion Detection System MIB. Provides trap definitions for the evAlert and evError elements of the IDIOM (Intrusion Detection and Operations Messages) document and read support for the Intrusion Detection System (sensor) health information.
CISCO-CIPCMPC-MIB
The MIB to manage Cisco Multi-Path Channel (CMPC) devices on a CMCC.
CISCO-CIPCSNA-MIB
The Cisco MIB for Systems Network Architecture (SNA) support on the Channel Interface Processor (CIP).
CISCO-CIPLAN-MIB
The Cisco MIB for managing the Cisco internal LAN support on the Channel Interface Processor.
CISCO-CIPTCPIP-MIB
The Cisco MIB for managing the Cisco TCP/IP stack running on the Channel Interface Processor (CIP).
CISCO-CIPTG-MIB
The MIB to manage Cisco Multi-Path Channel (CMPC) Transmission Groups (TGs) on a CMCC.
CISCO-CIRCUIT-INTERFACE-MIB
MIB for identifying circuits on interfaces.
CISCO-CLASS-BASED-QOS-MIB
This MIB provides read access to Quality of Service (QoS) configuration and statistics information for Cisco platforms that support the Modular Quality of Service Command-line Interface (Modular QoS CLI).
CISCO-CLASS-BASED-QOS-MIB-CAPABILITY
Agent capabilities for CISCO-CLASS-BASED-QOS-MIB
CISCO-CLUSTER-MIB
The Cisco MIB for the management of a group of devices called a 'cluster'.
CISCO-CNO-SWITCH-MIB
MIB specific to Cisco Network Office switches.
CISCO-COMMON-MGMT-CAPABILITY
Agent capabilities for CISCO-COMMON-MGMT-MIB
CISCO-COMMON-MGMT-MIB
MIB module for integrating different elements ofmanaging a device. For example, different device access methods like SNMP, CLI, XML and so on h ave different set of users which are used to communicate with the device. The ccmCommonUserTable provides framework to create one set of users which is common across all the device access methods.
CISCO-COMMON-ROLES-MIB.
MIB module for managing the common roles between access methods like Command Line Interface (CLI), SNMP and XML interfaces
CISCO-COMPRESSION-SERVICE-ADAPTER-MIB.
This MIB is intended to
- Provide performance information about a compression service adapter.
- Enable or disable the compression service adapter.
CISCO-CONFIG-COPY-CAPABILITY
CISCO-CONFIG-COPY-MIB Capabilities for IOS XR release 2.0
CISCO-CONFIG-COPY-MIB
This MIB facilitates writing of configuration files of an SNMP Agent running Cisco's IOS in the following ways: to and from the net, copying running configurations to startup configurations and vice-versa, and copying a configuration (running or startup) to and from the local IOS file system
CISCO-CONFIG-MAN-CAPABILITY
CISCO-CONFIG-MAN-MIB capabilities for IOS XR release 2.0
CISCO-CONFIG-MAN-MIB
Configuration management MIB.
CISCO-CONTACT-CENTER-APPS-MIB
The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for applications that deliver enterprise-wide intelligent contact routing, call treatment, network-to- desktop computer telephony integration (CTI), and multi-media (e.g. voice, email, chat) contact management over an IP infrastructure. Cisco enterprise contact center applications are distributed, fault-tolerant, contact routing and management solutions that encompass multiple, dependent host servers. Each host is capable of implementing one or more functions of the application. How many functions a single host is capable of providing is dependent upon capacity and/or performance limitations. However, the architecture supports virtually any combination.
CISCO-CONTENT-DELIVERY-STREAMING-MIB
This MIB instrumentation is for managing the Content Delivery and Streaming functionality on Cisco devices. Contents are ingested into content delivery network and then distributed to clients. There are two types of contents in content delivery network - live and VOD. VOD contents can be pre-positioned or dynamically cached into the content delivery network. Live stream is ingested and delivered to a large audience using one-to-many split. Streaming protocols are supported, by different streaming modules. These include HTTP, RTSP, Microsoft Media Server, RTMP and their varieties.
CISCO-CONTENT-ENGINE-MIB
The MIB module for the Cisco Content Engine from Cisco Systems, Inc.
CISCO-CONTENT-NETWORK-MIB
This MIB module defines objects for Content Network devices.
CISCO-CONTENT-SERVICES-CAPABILITY
Agent capabilities for CISCO-CONTENT-SERVICES-MIB
CISCO-CONTENT-SERVICES-MIB
Content Service is a capability to examine IP/TCP/UDP headers, payload and enable billing based on the content being provided.
CISCO-CONTEXT-MAPPING-CAPABILITY
Agent capabilities for the CISCO-CONTEXT-MAPPING-MIB.
CISCO-CONTEXT-MAPPING-MIB
A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple SNMP contexts. This typically occurs because the technology has evolved to have extra dimension(s), i.e., one or more extra data and/or identifier values which are different in t he different contexts, but were not defined in INDEX clause(s) of the original MIB module. In such cases, network management ap plications need to know the specific data/identifier values in each context, and this MIB module provides mapping tables which contain that information.This MIB provides the mapping between the snmp contexts and feature context internal to the system
CISCO-COPS-CLIENT-CAPABILITY
The capabilities description of CISCO-COPS-CLIENT-MIB.
CISCO-COPS-CLIENT-MIB
This MIB module is for configuration & statistic query of Common Open Policy Service(COPS) client feature on the Cisco device.
CISCO-CRYPTO-ACCELERATOR-MIB
The MIB module for monitoring the identity, status, activity and faults of crypto accelerator (CA) modules used in devices implementing security services. The purpose of this MIB is to facilitate the following: 1) facilitate the discovery of hardware crypto accelerator modules installed in a security device 2) monitor the activity, faults and performance of hardware crypto accelerators and help the Network Management Station (NMS) correlate the performance of the CA modules with that of the security services (IPsec, SSL, SSH, PKI etc) using the modules.
CISCO-CSG-CAPABILITY
Agent capabilities for the CISCO-CSG-MIB.
CISCO-CSG-MIB
This MIB supports the Cisco Content Services Gateway (CSG) product. It includes five traps and four tables that enable querying CSG resource statistics.
CISCO-CUICAPPS-MIB
The Cisco Unified Intelligence Center (CUIC) is a scalable robust and secure reporting solution for contact center applications. The CUIC application can be deployed on multiple servers that form a cluster, where each server hosts a reporting engine. The CISCO-CUICAPPS-MIB defines objects that describe instrumentation implemented by the components comprising CUIC.
CISCO-CVP-MIB
The Cisco Unified Customer Voice Portal (CVP) Management Information Base (MIB) module defines management instrumentation for CVP services. Each distinct CVP service exposes instrumentation related to its specific function. The bulk of this instrumentation is run-time statistics that provide insight into the health, performance and capacity utilization of the CVP solution. Notifications are also a key component of this instrumentation. This MIB also defines a notification format that offers descriptive objects as well as objects t hat ease the task of correlating events at the management station.
CISCO-DATA-COLLECTION-CAPABILITY
Agent capabilities for CISCO-DATA-COLLECTION-MIB
CISCO-DATA-COLLECTION-MIB
Data Collection mib
CISCO-DDP-IAPP-MIB
This MIB module describes the management support forthe Inter-Access Point Protocol (IAPP). IAPP is aCisco propriety Data Delivery Protocol (DDP), and theprotocol defines the function and frame formats f orcommunication between IEEE 802.11 Standard wirelessLAN stations, i.e. access point (AP), work-groupbridge, and repeater. The IAPP supports wirelessstation LAN attachment, client roaming, associationmanagement, a nd diagnostic services.
CISCO-DEVICE-EXCEPTION-REPORTING-MIB
This mib defines the SNMP objects to report exceptions to north-bound NMS. The devices implementing this MIB monitor the status of hardware and software services, and report any exceptions regarding these components. These hardware and software services could belong to the monitoring devices or other managed devices. An exception is something abnormal that the system administrators should pay attention to. The criteria for what is an exception could vary by system and should be defined by the system administrators. Certain NM devices or applications may have pre-defined exceptions. This MIB does not try to define exceptions. But rather it defines SNMP objects for devices to use SNMP notification as an exception reporting mechanism. Exceptions may be pre-defined or defined through other device management interface such as CLI, GUI, or HTTP.
CISCO-DHCP-SNOOPING-CAPABILITY
The capabilities description of CISCO-DHCP-SNOOPING-MIB
CISCO-DHCP-SNOOPING-MIB
The MIB module is for configuration of DHCP Snooping feature.
CISCO-DIAL-CONTROL-MIB
This MIB contains Cisco-specific extensions to the DIAL-CONTROL-MIB extracted from RFC 2128.
CISCO-DIAMETER-BASE-PROTOCOL-CAPABILITY
The capabilities description of CISCO-DIAMETER-BASE-PROTOCOL-MIB.
CISCO-DIAMETER-BASE-PROTOCOL-MIB
This MIB describes the SNMP MIB objects that are supported pertaining to theDiameter Base Protocol Configs/Stats.
CISCO-DIAMETER-CC-APPL-CAPABILITY
The capabilities description of CISCO-DIAMETER-CC-AAPL-MIB.
CISCO-DIAMETER-CC-APPL-MIB
This MIB describes the SNMP MIB objectsthat are supported pertaining to theDiameter Credit Control ApplicationConfigs/Stats
CISCO-DIAMETER-SG-CAPABILITY
The capabilities description of CISCO-DIAMETER-SG-MIB.
CISCO-DIAMETER-SG-MIB
This MIB describes the SNMP MIB objects that are supported in order to provide the ability to fetch/configure the Diameter Server Groups.
CISCO-DIFFSERV-EXT-MIB
Cisco extension to DIFFSERV-MIB, which is a standard MIB.
CISCO-DIGITAL-MEDIA-SYSTEMS-CAPABILITY.
The agent capabilities for CISCO-DIGITAL-MEDIA-SYSTEMS-MIB."
CISCO-DIGITAL-MEDIA-SYSTEMS-MIB.
This MIB models the physical/logical structures of a typical Digital Media Management system and its operational state.
CISCO-DISMAN-EVENT-CAPABILITY.
DISMAN-EVENT-MIB capabilities for IOS XR release 3.2.0
CISCO-DISMAN-EXPRESSION-CAPABILITY.
DISMAN-EXPRESSION-MIB capabilities for IOS XR release 3.2.0
CISCO-DIST-DIRECTOR-CAPABILITY.
Agent capabilities for CISCO-DIST-DIRECTOR-MIB
CISCO-DIST-DIRECTOR-MIB
This MIB specification contains definitions of management information of the Distributed Director that can be remotely monitored and controlled
CISCO-DLCSW-MIB
The Cisco MIB for managing FRAS sessions to the endstation. These objects are specific to downstream or enduser sessions only. The support for this MIB is read-only.
CISCO-DLSW-EXT-MIB
The MIB contains extensions to the DLSW-MIB (RFC 2024), including Traps.
CISCO-DLSW-MIB
The Cisco MIB for Managing Data Link Switching protocol. Initial support for this MIB is read-only.
CISCO-DM-MIB
The MIB module for the domain management functionality defined by the Fibre Channel standards (FC-SW2).
CISCO-DNS-CLIENT-CAPABILITY
The capabilities description of CISCO-DNS-CLIENT-MIB.
CISCO-DNS-CLIENT-MIB
The MIB module for entities implementing the clientside of the Domain Name System (DNS) protocol.
CISCO-DNS-SERVER-MIB
The MIB module for entities implementing the server side of the Domain Name System (DNS) protocol.
CISCO-DOCS-EXT-MIB
The MIB module for the Cisco specific extension objects of Data Over Cable Service Interface Specifications (DOCSIS), Radio Frequency interface. Also contains extension objects for managing Cable Modem Termination Systems (CMTS).
CISCO-DOCS-REMOTE-QUERY-MIB
This MIB module provides the management of the Cisco Cable Modem Termination Systems (CMTS) Remote Query feature.
CISCO-DOT11-ANTENNA-MIB
This MIB is intended to be implemented on 802.11 Access Points and Wireless Bridges to provide information about the antennas connected to their 802.11 interfaces. The NMS retrieves the configured antenna parameters and uses it to calculate the recommended radio settings to be applied to the Access Points being managed to achieve optimum coverage and throughput.
CISCO-DOT11-ASSOCIATION-MIB
Dot11 asociation mib.
CISCO-DOT11-CONTEXT-SERVICES-CAPABILITY
Agent capabilities forCISCO-DOT11-CONTEXT-SERVICES-MIB
CISCO-DOT11-CONTEXT-SERVICES-CLIENT-CAPABILITY
CAPABILITY file for CISCO-DOT11-CONTEXT-SERVICES-CLIENT-MIB
CISCO-DOT11-CONTEXT-SERVICES-CLIENT-MIB
This MIB gives information about the parentWDS, a non-WDS AP is registered to.
CISCO-DOT11-CONTEXT-SERVICES-MANAGER-MIB
This MIB is intended to be implemented on IEEE 802.11 Wireless LAN management devices for Access Points and Wireless Bridges participating in the context management process and making use of the services provided by entities offering WDS and WNS. This MIB allows NMS to access individual configuration of wireless stations through the SNMP agent at the management device, i.e. WSA.
CISCO-DOT11-CONTEXT-SERVICES-MIB
This MIB supports managing the devices offeringWireless Domain Services and Wireless Network Services as applicable to Structured Wireless Aware Network.
CISCO-DOT11-HT-MAC-CAPABILITY
Agent capabilities for CISCO-DOT11-HT-MAC-MIB
CISCO-DOT11-HT-MAC-MIB
This MIB is intended to be implemented on Cisco'sWLAN devices that provide the wired uplink to wirelessclients through the high-throughput dot11 radioscompliant to the 802.11n specification.The MIB describes the MAC layer parameters of the802.11n compliant radio interfaces.
CISCO-DOT11-HT-PHY-CAPABILITY
Agent capabilities for CISCO-DOT11-HT-PHY-MIB
CISCO-DOT11-HT-PHY-MIB
This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high-throughput dot11 radios compliant to the 802.11n specification. The MIB describes the PHY layer parameters of the 802.11n compliant radio interfaces.
CISCO-DOT11-IF-MIB
This MIB module provides network management support for Cisco IEEE 802.11 Wireless LAN type device (Access Point) radio interfaces.
CISCO-DOT11-LBS-MIB
This MIB module supports network management for Location Based Services on IEEE 802.11 wireless LAN devices. Location Based Services allows third party applications and positioning servers to work with Access Points to track positions of wireless clients in the network.
CISCO-DOT11-QOS-MIB
This MIB module provides network management support for QoS on wireless LAN devices. The objects defined in this MIB provide equivalent support as the objects in the IEEE 802.11E Standard draft. The original names of the objects in the standard are included in the REFERENCE clauses.
CISCO-DOT11-RADAR-MIB
This MIB module is for IEEE 802.11a/h Root device, i.e. Access Point (AP) or Root Bridge. This MIB allows dynamic frequency selection features related to DOT11 device.
CISCO-DOT11-RADIO-DIAGNOSTIC-CAPABILITY
CISCO-DOT11-RADIO-DIAGNOSTIC-MIB
This MIB is intended to be implemented on all 802.11 based Access Points and Wireless Bridges that need to participate in radio environment diagnosis. The devices mentioned above may house any one of the 802.11a/802.11b/802.11g standard- based radio interfaces in them for data communication in the form of radio waves. The administrator, through the NMS, temporarily alters the power and channel configurations of an 802.11 radio interface and the transmits power levels of the associated clients, if any, by setting appropriate values to the objects of this MIB to perform activities like discovering neighboring APs, measuring strength of the signals as received from other APs, studying RF interference levels at various APs, characterizing APs' coverage etc. These changes to the radio interface and the clients' configuration through this MIB are temporary and won't be retained across reloads.
CISCO-DOT11-SSID-SECURITY-MIB
This MIB module provides network management support for Cisco IEEE 802.11 Wireless LAN devices association and authentication.
CISCO-DOT11-WIDS-MIB
This MIB is intended to be implemented on the following IOS based network entities for the purpose of providing network management stations information about the various attempts to compromise the security in the 802.11-based wireless networks. (i) 802.11 Access Points that accept wireless client associations. The MIB reports the information about the following attacks that can happen either at the initial authentication phase or during normal data communication between the client and the AP.
CISCO-DOT3-OAM-MIB
CISCO-DOT3-OAM-MIB.myMIB to manage objects of the IEEE 802.3ah protocol
CISCO-DS0-CROSS-CONNECT-MIB
Initial version of the MIB module
CISCO-DS0BUNDLE-EXT-MIB
The MIB module for managing DS0 Bundles. This MIB contains additional objects to supplement the the IETF draft ds0Bundle MIB.
CISCO-DS0BUNDLE-MIB
The MIB module to describe DS0 Bundle interfaces objects. Note: This contains a subset of the MIB objects defined in DS0BUNDLE-MIB of draft-ietf-trunkmib-ds0-mib-06.txt, section 6; it does not include the DS0 Bonding group.
CISCO-DS1-CAPABILITY
The agent capabilities for DS1-MIB for Cisco Products Series.
CISCO-DS1-EXT-MIB
The MIB module to describe DS1/E1 interface objects. This is an extension to the standard DS1/E1 MIB (RFC 2495).
CISCO-DS3-CAPABILITY
The Agent Capabilities for DS3-MIB(RFC 2496).
CISCO-DS3-EXT-CAPABILITY
The Agent Capabilities for CISCO-DS3-MIB.
CISCO-DS3-MIB
The MIB module to describe DS3 line objects. This is an extension to the standard DS3 MIB(RFC 2496).
CISCO-DSL-PROVISION-MIB
Cisco DSL (Digital Subscriber Line) Provision MIB Module. It is used to create subscriber PPP over ATM sessions and related tasks.
CISCO-DSP-MGMT-CAPABILITY
The agent capabilities for CISCO-DSP-MGMT-MIB.
CISCO-DSP-MGMT-MIB
Digital Signal Processing (DSP) Management MIB module. The MIB module monitors the DSP resource and status.
CISCO-DSPU-MIB
Used to define and manage DSPU objects.
CISCO-DYNAMIC-ARP-INSPECTION-CAPABILITY
The capabilities description of CISCO-DYNAMIC-ARP-INSPECTION-MIB
CISCO-DYNAMIC-ARP-INSPECTION-MIB
The MIB module is for configuration of Dynamic ARP Inspection feature. Dynamic ARP Inspection is a security mechanism which validate ARP packets seen on access ports
CISCO-DYNAMIC-PORT-VSAN-MIB
The MIB module for the management of the Dynamic Port Vsan Membership (DPVM) module. DPVM provides the ability to assign (virtual storage area network) VSAN IDs dynamically to switch ports based on the device logging in on the port. The logging-in device can be identified by its port World Wide Name (pWWN) and/or its node World Wide Name (nWWN).
CISCO-EIGRP-MIB
Enhanced Interior Gateway Protocol (EIGRP) is a Cisco proprietary distance vector routing protocol. It is based on the Diffusing Update Algorithm (DUAL), which is a method of finding loop-free paths through a network. Directly connected routers running EIGRP form neighbor adjacencies in order to propagate best-path and alternate-path routing information for configured and learned routes. The tables defined within the MIB are closely aligned with how the router command-line interface for EIGRP displays information on EIGRP configurations, i.e., the topology table contains objects associated with the EIGRP topology commands, and the peer table contains objects associated withe EIGRP neighbor commands, etc.
CISCO-EMBEDDED-EVENT-MGR-MIB
The MIB module to describe and store events generated by the Cisco Embedded Event Manager. The Cisco Embedded Event Manager detects hardware and software faults, and other events (such as OIRs) for the system. It also enables users to configure fault recovery services for system wide components. The Embedded Event Manager also provides process reliability statistics. The Embedded Event Manager is a policy driven process through which faults in the system are reported through a defined API. The Embedded Event Manager policy engine receives notifications when faults and other events occur. Embedded Event Manager policies implement recovery based on the current state of the system and the actions specified in the policy for a given event. Recovery actions are triggered when the policy is run. Developers write and customize Embedded Event Manager policies to handle faults and events.
CISCO-ENERGYWISE-MIB
The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protocols for managing power on and between network devices. An entity is Cisco EnergyWise compatible, if it complies with Cisco EnergyWise specification. A Cisco EnergyWise entity is characterized by the power related attributes of a physical entity present in ENTITY-MIB. Cisco EnergyWise solves the problem of Network Power Management. One of goals of Cisco EnergyWise is to manage power on network level. Some solutions in FCAPS have focused on managing a single element but Cisco EnergyWise provides the capability to handle the management of a network of devices, as well as a single device.
CISCO-ENHANCED-IMAGE-CAPABILITY
Agent capabilities for CISCO-ENHANCED-IMAGE-MIB
CISCO-ENHANCED-IMAGE-MIB
This MIB provides information about images running on the system. It has been extended to be useful for modular operating systems. The image table provides information about currently running image on the system. A modular operating system image consists of base image and all the installables loaded on the base image. A base image can be obtained from ceImageTable and all the installables installed on this image can be obtained using ceImageInstallableTable.
CISCO-ENHANCED-IPSEC-FLOW-MIB
This is a MIB Module for monitoring the structures and status of IPSec-based networks. The MIB has been designed to be adopted as an IETF standard. Hence vendor-specific features of IPSec protocol are excluded from this MIB.
CISCO-ENHANCED-MEMPOOL-CAPABILITY
Agent capabilities for CISCO-ENHANCED-MEMPOOL-MIB.
CISCO-ENHANCED-MEMPOOL-MIB
New MIB module for monitoring the memory pools of all physical entities on a managed system.
CISCO-ENHANCED-SLB-CAPABILITY
The capabilities description of CISCO-ENHANCED-SLB-MIB.
CISCO-ENHANCED-SLB-MIB
The MIB for managing Server Load Balancing Manager(s), and products supporting Server Load Balancing(SLB) features. This MIB extends the tables(as appropriate) that are defined in CISCO-SLB-MIB and CISCO-SLB-EXT-MIB.
CISCO-ENHANCED-WRED-MIB
Cisco Weighted Random Early Detection/Drop (WRED) is a method which avoids traffic congestion on an output interface. Congestion is detected by computing the average output queue size against queue thresholds, which can be configured either per IP precedence or differentiated services code point (DSCP) based. WRED support are on the IP fast switching and IP flow switching only. It does not apply to IP process switching. The purpose of this MIB is to provide Weighted Random Early Detection/Drop packet configuration and packet filtering information. This MIB provides the WRED information about the transmit (Tx) side and receive (Rx) side of the modules, for the managed systems that support WRED on both transmit side and receive side.
CISCO-ENTITY-ALARM-MIB
This MIB module defines the managed objects that support the monitoring of alarms generated by physical entities contained by the system, including chassis, slots, modules, ports, power supplies, and fans. In order to monitor alarms generated by a physical entity, it must be represented by a row in the entPhysicalTable (see ENTITY-MIB).
CISCO-ENTITY-ASSET-MIB
Monitor the asset information of items in the ENTITY-MIB (RFC 2037) entPhysical table.
CISCO-ENTITY-CAPABILITY
The Agent Capabilities for ENTITY-MIB.
CISCO-ENTITY-DIAG-CAPABILITY
The capabilities description of CISCO-ENTITY-DIAG-MIB
CISCO-ENTITY-DIAG-MIB
This MIB module defines the managed objects that describe the online diagnostics capabilities supported by the physical entities contained by the system, including chassis, modules, ports, power supplies, fans, and sensors. In order to manage the online diagnostic capabilities supported by a physical entity, it must be represented by a conceptual row in the entPhysicalTable of the ENTITY-MIB (RFC-2737).
CISCO-ENTITY-DIAG-TC-MIB
This module defines the textual conventions used within Cisco Entity Diag MIB.
CISCO-ENTITY-DISPLAY-MIB
This MIB module provides information about the status of display devices such as Light Emitting Diodes (LEDs) and alphanumeric displays present on the physical entities contained by the managed system.
CISCO-ENTITY-EXT-MIB
This MIB is an extension of the ENTITY-MIB specified in RFC2737. This MIB module contains Cisco-defined extensions to the entityPhysicalTable to represent information related to entities of class module(entPhysicalClass = 'module') which have a Processor.
CISCO-ENTITY-FRU-CONTROL-CAPABILITY
The Agent Capabilities for CISCO-ENTITY-FRU-CONTROL-MIB.
CISCO-ENTITY-FRU-CONTROL-MIB
The CISCO-ENTITY-FRU-CONTROL-MIB is used to monitor and configure operational status of Field Replaceable Units (FRUs) and other managable physical entities of the system listed in the Entity-MIB (RFC 2737) entPhysicalTable. FRUs include assemblies such as power supplies, fans, processor modules, interface modules, etc.
CISCO-ENTITY-PERFORMANCE-MIB
This MIB module defines managed objects that facilitate to monitor performance of any physical entity, which are listed in the ENTITY-MIB (RFC 4133) entPhysicalTable. The performance monitoring includes utilization, input/output packet/byte rates, etc. This monitoring is through the measurement periods of current, 1-minute, 5-minutes, 15-minutes. The performance data calculation method would vary for each entity for a specific interval, hence users of this MIB should obtain the information using the object cepStatsAlgorithm for a specific interval. The performance statistics can be accumulated for the 1-minute, 5-minutes and 15-minutes (recommended) intervals. At any one time, an agent maintains one current (incomplete) interval for each interval type and up to 96 completed interval number. Fewer than 96 interval number of data will be available if the agent has been restarted within the last 24 hours for 15 minutes interval, 8 hours for 5 minutes interval, and 1.36 hours for 1 minute interval. There is no requirement for an agent to ensure fixed relationship between the start of a one/five/fifteen minute intervals and wall clock, however some agents may align the fifteen minutes interval with quarter hours.
CISCO-ENTITY-PFE-MIB
The Packet Forwarding Engine technology are Cisco developed Network Processors, which accelerates certain features in order to provide better network performance. An agent uses this MIB to monitor the performance history on any active PFE pipeline listed in the ENTITY-MIB (RFC 2737) entPhysicalTable. This monitoring is via measurement periods of actual, 1-minute, 5-minutes and 15-minutes. For the 1-minute and 5-minute measurement periods, perfor- mance statistics are calculated and displayed based on pre- vious 1 minute and 5 minute respectively. For the 15-minute period, the performance statistics are accumulated in fifteen minute intervals. At any one time, an agent maintains one current (incomplete) interval and up to 96 completed intervals (24 hours worth). Fewer than 96 intervals of data will be available if the agent has been restarted within the last 24 hours. In addition, there is a rolling 24-hour total of each performance statistic. There is no requirement for an agent to ensure fixed rela- tionship between the start of a fifteen minute interval and any wall clock; however some agents may align the fifteen minute intervals with quarter hours.
CISCO-ENTITY-PROVISIONING-MIB
This MIB module defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'container' to hold a specified physical entity. This allows a management client to configure the specified physical entity, including all of its subordinates physical entities, before installation. Consider a network manager of a CLEC (Competitive Local Exchange Carrier) planning for the installation of the hardware necessary to support several new subscribers. This network manager wants to pre-configure the ADSL (Asymmetric Digital Subscriber Loop) modems that will support these subscribers, thereby reducing the bring-up time once they arrive. Under normal circumstances this would not be possible. However, provisioning allows the network manager to 'create' the physical entities that represent the new modems. In essence, the device simulates the installation of the new modules into the system. This has the effect of creating all conceptual rows in all the necessary tables that support the physical entity and all its subordinate physical entities (e.g., entPhysicalTable, entAliasMappingTable, and ifTable).
CISCO-ENTITY-QFP-MIB
This MIB module defines managed objects that facilitate the management of Quantum Flow Processors (QFP), which are listed in the ENTITY-MIB (RFC 4133) entPhysicalTable as an entPhysicalClass of 'cpu'. The Quantum Flow Processors (QFP) technology is an architecture family developed by Cisco, which has fully integrated and programmable networking chip set that controls different functions of a system such as packet forwarding. This module contains objects to monitor various QFP statistics such as system, utilization, memory, etc. The utilization statistics can be used for future capacity planning. The calculation of this statistics may vary by devices which host QFPs, hence the user must refer to the specific device document of interest for the exact method of calculation.
CISCO-ENTITY-REDUNDANCY-MIB
This management information module supports configuration, control and monitoring of redundancy protection for various kinds of components on Cisco managed devices. It is meant to be generic enough to handle basic redundancy control and monitoring for many types of redundant member components and redundancy architectures as long as there is an Entity MIB entPhysicalIndex and entPhysicalVendorType assigned to each member component. It is designed so that the tables can be augmented in other extension MIBS which build upon this MIB by adding additional objects that may be specific to a particular type of redundancy or member component. This MIB can also be used in cases where some types of redundancy groups and members don't require explicit user configuration. One example may be redundant fan assemblies. In those cases, the managed system should internally assign group and member indexes, so that it can provide read-only access to the group and member tables. This allows MIB monitoring for these types of redundant entities.
CISCO-ENTITY-REDUNDANCY-TC-MIB
This module defines the textual conventions used within Cisco Entity Redundancy MIBs.
CISCO-ENTITY-SENSOR-CAPABILITY
The Agent capabilities for CISCO-ENTITY-SENSOR-MIB
CISCO-ENTITY-SENSOR-EXT-MIB
This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB also defines the notifications applicable for sensors reported in ENTITY-MIB(RFC 4133).
CISCO-ENTITY-SENSOR-HISTORY-MIB
This MIB module defines objects that describe collections and measurement information for each sensor supporting historical data collection. The sensor measurement either represents a measured value or a SMA (Simple Moving Average) value for a specified interval rate over a period of time.
CISCO-ENTITY-SENSOR-MIB
The CISCO-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable.
CISCO-ENTITY-VENDORTYPE-OID-MIB
This module defines the object identifiers that are assigned to various components on cisco products, which are used by the entPhysicalTable of the ENTITY-MIB to uniquely identify the type of each physical entry.
CISCO-ENVMON-CAPABILITY
Agent capabilities for CISCO-ENVMON-MIB.
CISCO-ENVMON-MIB
The MIB module to describe the status of the Environmental Monitor on those devices which support one
CISCO-EPC-GATEWAY-MIB
This MIB module manages the features and configuration for PDN Gateway(PGW) and Serving Gateway(SGW) in Evolved Packet Core(EPC) architecture. The PGW is the permanent IP point-of-attachment for access via the E-UTRAN. The PGW performs IP policy and charging enforcement on packet flows to and from mobile devices.
CISCO-EPM-NOTIFICATION-MIB
Notifications directly from hardware and software and processed notifications from various management applications can be further processed and forwarded by still other management applications to indicate the status of devices and software (managed objects). The status of these managed objects can be reported by traps. The CISCO-EPM-NOTIFICATION-MIB contains the trap structure which carries the identity and status info of the managed object as analyzed by such an event processor. It is not possible for receivers of these traps to query the mib objects. A unique but optional feature of the application generating the trap defined in this mib is the ability to contain multiple partitions in the same system running the application. A 'Partition' is a logical grouping of a set of managed devices. These devices can belong to only one partition at any given time. The trap structure will contain information on the exact partition number and the partition name of the device where it resides. The need for trap generation is to enable multiple management applications in the network to have a consolidated view of the whole network of Cisco and non-Cisco devices.
CISCO-ERM-MIB
Cisco Embedded Resource Manager (ERM) MIB. The Embedded Resource Manager (ERM) is a framework which helps in effectively managing resources such as cpu, memory, buffers, etc.
CISCO-ERR-DISABLE-MIB
This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature via SNMP. The error-disable feature allows other software features running in a system to operationally disable a system entity upon detecting abnormal conditions. Examples of such a system entity include interfaces, a vlan configured in the system, or a VLAN allowed on specific layer 2 multi-vlan interface.
CISCO-ETHER-CFM-MIB
This MIB module defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM). CFM is an end-to-end per service instance Ethernet layer Operations, Administration and Management (OAM) protocol.
CISCO-ETHERLIKE-EXT-MIB
The MIB module to describe generic objects for ethernet-like network interfaces. This MIB provides ethernet-like network interfaces information that are either excluded by EtherLike-MIB or specific to Cisco products.
CISCO-ETHERNET-ACCESS-MIB
The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge device in an organizations network, e.g. a Metro Ethernet network. An edge device, is a customer located equipment, this is the first device which will connect the Service Provider's network and map subscriber traffic into the next layer. The access media could be either CAT5 or fiber. The access device (edge device) can be designed for DSL, Ethernet or other technologies, however, this MIB is designed for Ethernet.
CISCO-ETHERNET-FABRIC-EXTENDER-MIB
The MIB module for configuring one or more fabric extenders to connect into a core switch. Since fabric extenders might not be manageable entities, this MIB is assumed to be instrumented on the core switch. A fabric extender may be hardwired or preconfigured with a list of uplink ports. These uplink ports are used to connect to a core switch. A fabric extender is assumed to be directly connected to its core switch. Each physical interface on the core switch is assumed to be connected to one and only one fabric extender. When an extender powers up, it runs a link local discovery protocol to find core switches. The extender puts all available self identification in its discovery report. The core switch, depending on configuration, uses the extenders identification to accept or deny an extender from connecting. A fabric extender may be connected to different core switches via different uplink ports. In that case, each core switch's instance of the MIB may refer to the same extender. Ports on core switch used to connect to extenders are known as Fabric ports. A fabric port may be a physical interface or a logical interface such as an EtherChannel. An extender may connect into a core switch via more than one fabric port. Non fabric ports on an extender are typically used to connect hosts/servers.
CISCO-EVC-MIB
Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. Using standard Ethernet interfaces, subscribers can set up secure, private Ethernet Virtual Connections, to connect their sites together and connect to business partners, suppliers and the Internet. This MIB module defines the managed objects and notifications describing Ethernet Virtual Connections. Ethernet Virtual Connections (EVC), are defined by the Metro Ethernet Forum (MEF), as an association between two or more UNIs. Frames within an EVC can only be exchanged among the associated UNIs. Frames sent into the MEN via a particular UNI must not be delivered back to the UNI from which it originated. Along an EVC path, there are demarcation flow points on associated ingress and egress interface, of every device, through which the EVC passes. A service instance represents these flow points where a service passes through an interface.
CISCO-EXT-SCSI-MIB
The Cisco extension to CISCO-SCSI-MIB which is a copy of the Internet draft, the SCSI-MIB, from the IETF.
CISCO-FABRIC-C12K-MIB
Cisco Fabric MIB module for c12000 series of routers. This MIB module is used for managing/tracking the c12000 fabric entities and fabric related configuration, status and statistics information. C12000 fabric architecture is based on NxN non-blocking crossbar switch fabric, where N stands for the maximum number of LCs that can be supported in the chassis (this includes the RP). The connections through the switch fabric is controlled by a scheduler (CSC), the CSC accepts transmission requests from line cards, issues grants to access the fabric, and provides a reference clock to all the cards in the system to synchronize data transfer across the crossbar. Some of the error status objects in the MIB are read-clear, that is the value of the object is cleared on a query of the object.
CISCO-FABRIC-HFR-MIB
Cisco Enhanced Benes fabric MIB module. This MIB module is used for managing/tracking the Ehanced Benes Fabric entities and/or fabric related configuration, state and statistics information.
CISCO-FABRIC-MCAST-APPL-MIB
Fabric multicast resource MIB module. This MIB module is used for managing/tracking the fabric multicast resource application related information.
CISCO-FABRIC-MCAST-MIB
Fabric Multicast Resource MIB module. This MIB module is used for managing/tracking the fabric multicast resource related information.
CISCO-FC-DEVICE-ALIAS-MIB
The MIB module for the management of Device Aliases in a Fibre Channel Fabric. A Fibre Channel fabric consists of devices such as disks, hosts and switches. The disks and hosts login to the switches and avail services available to them in the fabric. These devices are identified by means of their World Wide Names (WWN). The WWNs are 8-byte cryptic identifiers, which are cumbersome for human use. A Device Alias is a human readable string which can be used to alias a World Wide Name (WWN). So, a Device Alias is used to map a WWN to a user friendly name. Once configured, the Device Alias can be used in place of the WWN. On the switch, this MIB assists in defining the Device Aliases for the remote devices and using these Aliases instead of the cryptic WWNs.
CISCO-FC-FE-MIB
This is the Cisco fibre element management MIB module. It covers: - Cisco extension to the interface MIB ( IF-MIB ) - Contains all the groups from FIBRE-CHANNEL-FE-MIB relevant to Cisco fabric. - Other features specific to Cisco fabric. This MIB supports all the port types defined by the textual convention FcPortTypes. In addition it also supports Nx_port, where Nx_port can be either N_port or NL_port. The FC standards define Interconnect_Ports to be E_ports or B_Ports. This MIB supports Port Channel ports. Port Channel port is a single logical port, which contains multiple physical ports as its members. Presently only E_ports can be a member of Port Channel port. In addition it provides GigE and port channel information for all the Gigabit Ethernet (GigE) ports in the fabric.
CISCO-FC-MGMT-MIB
This module defines management information specific to Fibre Channel-attached devices. This module is an adaptation of IETF's IPS working group's draft, draft-ietf-ips-fcmgmt-mib-02
CISCO-FC-MULTICAST-MIB
MIB module for monitoring and configuring Fibre Channel Multicast feature.
CISCO-FC-PM-MIB
This MIB module defines 24 hour error statistics for Fibre Channel (FC) and FICON interfaces collected every 15 minutes.
CISCO-FC-ROUTE-MIB
The MIB module for configuring and displaying FC (Fibre Channel) Route Information.
CISCO-FC-SDV-MIB
This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devices.
CISCO-FC-SPAN-MIB
MIB module for displaying and configuring Switched Port Analyzer(SPAN) related features in a Fibre Channel device. SPAN is a feature that enables the user to analyze network traffic, passing through the ports (called SPAN source ports) in a switched network using SwitchProbe device attached to a switch port called SPAN destination (SD) port. SPAN feature is non- intrusive and does not affect switching of network traffic for any of the source ports.
CISCO-FC-TUNNEL-MIB
The CISCO-FC-TUNNEL-MIB is used to configure Fiber Channel (FC) tunneled by other protocols, i.e. TCP (Transmision Control Protocol) or UDP (User Datagram Protocol), and monitor the status of the tunnels. And Fiber Channel Command and Data messages can be tunneled by those protocols through the internet to extend the Fiber Channel network.
CISCO-FCC-MIB
The MIB module for the management of Fibre Channel Congestion Control(FCC). FCC is a Cisco proprietary flow control mechanism that alleviates congestion on Fibre Channel networks. This MIB enables managers to configure the FCC mechanism on the switch, provides statistics of the congestion control packets, notification of congestion state changes of the FC port and monitoring of the congestion state of the FC port.
CISCO-FCIP-MGMT-EXT-MIB
A MIB module for extending the CISCO-FCIP-MGMT-MIB to add objects which provide additional information about FCIP interfaces not available in other MIBS.
CISCO-FCIP-MGMT-MIB
The Fibre Channel Over TCP/IP management MIB module. This mib module is the Cisco version of the FCIP MIB draft , draft-ietf-ips-fcip-mib-02.txt, from the IETF.
CISCO-FCOE-MIB
This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtual FC (VFC) Interface as an object that represents either a VF_Port or a VE_Port on the FCF. Virtual FC interfaces can be either statically created or dynamically created at the time of FIP based FLOGI or ELP request. In this document the term VSAN ID is used interchangeably with Fabric Index defined in the T11 standards.
CISCO-FCPING-MIB
The MIB module for the management of the Fibre Channel Ping functionality.
CISCO-FCS-MIB
The MIB module for the management of a Fabric Configuration Server (FCS). An FCS is defined by the FC-GS3 standard. This MIB enables managers to configure and monitor FCS parameters.
CISCO-FCSP-MIB
MIB module for managing Fibre Channel Security for the fibre channel devices. This MIB is used to configure and monitor the Fibre-Channel Security Protocol (FC-SP)
CISCO-FCTRACEROUTE-MIB
The MIB module for the management of the Fibre Channel Trace Route functionality.
CISCO-FDMI-MIB
Fabric Device Management Interface (FDMI) MIB. This MIB module defines objects for managing the devices such as HBA (Host Bus Adapter). It provides device information which have registered with an FC fabric using FDMI.
CISCO-FEATURE-CONTROL-MIB
There are two types of features in the system: - Regular features - Optional features The Regular features may or may not need to support the user triggerd control (enabling/disabling). In case the regular features need to support such control, they need to be instrumented in their respective MIBs. The Optional features can be controlled (enabled/ disabled) by the user via CLI/SNMP. The optional features are generally disabled by default. As part of the enabling of such optional feature, the first mandatory step is to explicitly enable the feature using the CLI/SNMP. Following this mandatory step, a feature may require additional feature specific enabling steps similar to the regular features. In addition to the user triggered control, other system specific conditions like licensing may influence the operating state of such optional feature. This MIB module is to facilitate the global level control (enabling/disabling) over the optional features in the system. The disabling of such optional feature using this MIB module would make the feature disabled and the entire feature specific mib objects also unavailable.
CISCO-FICON-MIB
This is the FICON (FIber CONnection) MIB module. FICON is an IBM standard of transport mechanism for communication between the mainframes and devices and is a major consideration for enterprise data centers. The Cisco MDS Storage Area Network (SAN) switches provide the functionality of a FICON Director to the customers.
CISCO-FILTER-GROUP-MIB
The MIB module is for creating and configuring object groups to support packet filtering and access control on IP and other protocols. The cfgFilterGroupTable allows users to create delete, and get information about filter groups. Filter groups are uniquely identified by the group names. Filter groups can either be of network, protocol, service and icmp and filter group type cannot be changed once it has been created. The cfgFilterNetworkGroupTable is used for managing information about IP Addresses. The cfgFilterIpProtocolGroupTable is used for managing information about protocols. The cfgFilterIpServiceGroupTable is used for managing information about services(ports). The cfgFilterICMPGroupTable is used for managing information about ICMP protocol. The cfgFilterNestedGroupTable is used for supporting nesting of filter groups(i.e configuring filter groups inside the other filter groups).
CISCO-FIPS-STATS-MIB
The Federal Information Processing Standards (FIPS) power-up self-test status MIB module
CISCO-FIREWALL-MIB
MIB module for monitoring Cisco Firewalls.
CISCO-FLASH-MIB
This MIB provides for the management of Cisco Flash Devices.
CISCO-FLEX-LINKS-MIB
This MIB module is for configuration and status query of Flex Links feature on the Cisco device. Flex Links are a pair of Layer 2 interfaces, where one interface is configured to act as a backup to the other. The feature provides an alternative solution to the Spanning Tree Protocol (STP), allowing users to turn off STP and still provide basic link redundancy. Flex Links are typically configured in service provider or enterprise networks where users do not want to run STP on the device.
CISCO-FLOW-CLONE-MIB
This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software entity, that is responsible to clone (or duplicate) flows to the specified destination port in the device. These cloned packets will be sent to an external device for a more fine-grained analysis of the flows. A typical application of this MIB module will facilitate cloning media flows. However, by no means does the definition of this MIB module prevents other applications from using it.
CISCO-FLOW-MONITOR-MIB
This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitoring media flows, especially flows carrying video streams. However, by no means does the definition of this MIB module prevents other applications from using it.
CISCO-FRAME-RELAY-MIB
Cisco Frame Relay MIB
CISCO-FSPF-MIB
Fabric Shortest Path First (FSPF) MIB.
CISCO-FTP-CLIENT-MIB
The MIB module for invoking Internet File Transfer Protocol (FTP) operations for network management purposes.
CISCO-GATEKEEPER-MIB
The MIB Module supports the functions of a gatekeeper. The gatekeeper is a function of the H.323 Packet Based Multimedia Communications Systems, a standard of TU. The gatekeeper provides address translation and controls access to the network for H.323 terminals.
CISCO-GDOI-MIB
This MIB module defines objects for managing the GDOI protocol.
CISCO-GGSN-EXT-MIB
This MIB module extends the CISCO-GGSN-MIB. This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device provides interworking with external packet-data network of a particular GPRS service provider. It provides a combination of IP routing and GPRS specific functionality to support mobile users. A PDP context on the GGSN device contains the mobile users session information, during an active session. This information is used by the device to control the session. An active PDP context is created when a mobile station's service request is authenticated and served by the GGSN device.
CISCO-GGSN-GEO-MIB
This MIB provide additional information for passive interface configured for each OSPF process, independent of object creation in the corresponding OSPF MIB.
CISCO-GGSN-MIB
This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device provides interworking with external packet-data network of a particular GPRS service provider. It provides a combination of IP routing and GPRS specific functionality to support mobile users. GTP version1 is introduced in UMTS release 99 and Cisco GGSN will support both GTP version 1 (GTP v1) and version zero (GTP v0) simultaneously. GTP v1 supports multiple PDP contexts sharing one IP address. TFTs are introduced to achieve this. Each TFT is associated with a PDP context and there may exist one PDP context without TFT amongst all PDP contexts sharing the same IP address. Each TFT has one to eight packet filters each assigned with a precedence index. These packet filters are evaluated one at a time against the packet header information in sequence of their precedence index. A match is claimed if all the filters are matched and the PDP context that the TFT belongs to will be selected, else the checks are performed against the filters of another PDP context. If the packet header doesn't contain any TFT packet filter information, then the PDP context without the TFT is selected for further processing.
CISCO-GGSN-QOS-MIB
This MIB module manages the Quality of Service parameters of GGSN in a GPRS system. GGSN is the Gateway GPRS Support Node in the GPRS architecture. It provides interworking of GPRS network with external packet-switched networks - PDNs or other data networks.
CISCO-GGSN-SERVICE-AWARE-MIB
This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GGSN-MIB. There needs to be a tight coupling between GGSN and CSG in order to realize the enhanced GGSN, which is capable of categorizing traffic flowing within a PDP context to different services. An enhanced version of Diameter Credit Control Application (DCCA) will be used for implementing real-time credit control of end users in the IPS framework. The GGSN will act as DCCA client and will interact with DCCA server for quota negotiation and usage reporting. The credit control request (CCR) message is used between DCCA-Client (DCCA-C) and DCCA-Server to request credit authorization for a given service. The credit control request has one mandatory AVP (Attribute Value Pair) called CCR. For a session based credit control several interrogation required, the first, intermediate and final. The first interrogation must be sent before the DCCA-C allows any service event to the user, CCR type is set to INITIAL in this case. When all the granted service units for one unit type are spent by the end user or the validity time is expired the DCCA-C must send a new credit control (CC) request to CC server, this is the intermediate interrogation and the CCR type AVP is set to the value UPDATE. When the end user terminates a service session the DCCA-C must send a final CCR request message to the CC server. The CCR type AVP is set to the FINAL or TERMINATION_REQUSET. CSG will be responsible for categorizing the traffic, quota management activities and usage reporting functions. GGSN will act as a quota server for CSG. A proprietary interface based on GTP' will be used between GGSN and CSG.
CISCO-GPRS-ACC-PT-MIB
This MIB module supports access point configuration for GGSN in a GPRS system. GPRS [1] is a GSM network providing mobile wireless data communication services. GGSN is the Gateway GPRS Support Node in the GPRS architecture. It provides interworking with external packet-switched networks - PDNs or other data networks. GGSN is a software extension of a router. A GGSN provides data access for its mobile subscribers to parts of the data network identified by the list of APNs configured on the node.
CISCO-GPRS-CHARGING-MIB
This MIB module manages the charging related function on the GGSN node of a GPRS system.
CISCO-GPRS-GTP-MIB
The MIB Module for managing the General Packet Radio Service(GPRS) Tunnelling Protocol(GTP) on Gateway GPRS Support Node (GGSN) and Serving GPRS Support Node(SGSN).
CISCO-GPRS-L2RLY-MIB
The MIB Module for managing the General Packet Radio Service(GPRS) L2RLY related information on Servicing GPRS Support Node(SGSN). In GPRS network, a SGSN is typically implemented as a single node; in cisco-Alcatel joint development, it's split into Telecom part (T-node) and Datacom part (D-node). T-nodes and D-nodes are connected by two fast ethernets. A simple connectionless protocol called L2RLY is used to provide service of forwarding packet between T-unit and D-unit, flow control and defending against the failure of a FE subnet.
CISCO-GSLB-DNS-MIB
The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). The MIB defines objects for global statistical information like DNS queries received, DNS responses sent, etc. Further it defines objects for answer, answer group, domain list, source address list, proximity rule and DNS rule statistics. It also defines related notifications.
CISCO-GSLB-HEALTH-MON-MIB
The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configuration and statistics. It also defines related notifications.
CISCO-GSLB-SYSTEM-MIB
This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A GSLB device is used to allocate the least-loaded and proximate resource to the requester. The MIB objects define information about GLSB status, GSLB's peers (other GSLB devices available on its network with which it interacts) information & status, GSLB's proximity information related statistics, etc. Further it defines related notifications.
CISCO-GTP-DIRECTOR-MIB
This MIB module defines objects that are used to manage GTP Director Module. In the GPRS network, the APN is the identifier that specifies where the user is connecting. The APN identifies whether the network is a corporate network or a service provider network. The APN comprises of two parts, the network id and the operator id. The Single Access point feature enables the service provider to add new access-points to the GGSN without having to provision the HLR. The requests are sent by the SGSN to the same virtual APN. A virtual APN is not associated with any actual physical network. The GGSN processes the request and forwards the packet to the appropriate access-point that is specified in the PCO. The Single APN feature is supported only in Cisco GGSNs. The purpose of the GTP-Director is to provide a mechanism for service providers using non-Cisco GGSN to use the Single APN feature. This would enable the service providers to add access-point to the network without having to provision the HLR. This will be transparent to the SGSN. The mobile user initiates a connection request to the SGSN. The access-point name specified in the request is the virtual APN. The GTP-Director would resolve the access-point name and forward the request to the appropriate GGSN (real GGSN).
CISCO-GTP-MIB
This MIB module manages the GPRS Tunnelling Protocol (GTP) on GGSN and SGSN. GPRS provides wireless access to packet data network on the GSM infrastructure.
CISCO-GTPV2-MIB
This MIB module manages the GPRS Tunneling Protocol version 2(GTPv2) statistics for the Evolved Packet Core(EPC) architecture. SGW and PGW are the key elements of EPC architecture. The PGW is the permanent IP point-of-attachment for access via the E-UTRAN. The PGW performs IP policy and charging enforcement on packet flows to and from mobile devices. The SGW is a local mobility anchor for E-UTRAN mobility, switching packets between the S5 interface and the GTP based S1-U interface for mobiles in connected mode.
CISCO-H225-MIB
Cisco H225 MIB module. This module consists of H225 call signaling and H225 RAS (Registration, Admission and Status). These are protocols specified by H323 for transmission of real-time audio, video and data over packet-based networks. H225 call signaling is used to set up connections between H323 endpoints such as terminals and gateways, over which the real-time data can be transported. H225 RAS is the protocol between endpoints (terminals and gateways) and gatekeepers.
CISCO-H320-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.320 call information over a telephony network. ITU-T Recommandation H.320 is the ITU standard covers audio and video to be shared among narrow-band visual telephone systems and terminal equipments over ISDN.
CISCO-H324-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.324 call information over a telephony network. ITU-T Recommendation H.324 is the ITU standard covers audio and video to be shared among narrow-band visual telephone systems and terminal equipments over ISDN.
CISCO-HC-ALARM-MIB
This module defines Remote Monitoring MIB extensions for High Capacity Alarms.
CISCO-HEALTH-MONITOR-MIB
Health Monitor MIB module. The Health Monitor uses a model based on events of varying severity and frequency, and predefined rules, to generate a metric that represents a system's (and its subsystems') level of health. The events are typically internally generated notifications in response to detrimental or correctional changes in the state of the hardware or software of the system.
CISCO-HSRP-EXT-MIB
The Extension MIB module for the CISCO-HSRP-MIB which is based on RFC2281. This MIB provides an extension to the CISCO-HSRP-MIB which defines Cisco's proprietary Hot Standby Routing Protocol (HSRP), defined in RFC2281. The extensions cover assigning of secondary HSRP ip addresses, modifying an HSRP Group's priority by tracking the operational status of interfaces, etc.
CISCO-HSRP-MIB
The MIB module provides a means to monitor and configure the Cisco IOS proprietary Hot Standby Router Protocol (HSRP). Cisco HSRP protocol is defined in RFC2281.
CISCO-HW-MODULE-CONTROL-MIB
The MIB module providing configuration and control information for management of hardware modules and components on Cisco devices. The following features are managed: bandwidth oversubscription, clearing of HoL(Head of Line) blocking, etc. Bandwidth oversubscription: a group of ports are said to be operating in bandwidth oversubscription mode if the amount of internal forwarding fabric bandwidth allocated to the group of ports on a switching or routing device is less than the aggregate maximum connection speeds of these ports. Clearing of HoL blocking: refers to the process in which if any port of a port group receives a pause frame from the remote side, it will block packet transmission on all ports of the port group till a packet is delivered to the flow controlled port. If the clearing of HoL blocking feature is disabled, the device will drop packets destined for the jammed ports and continue delivering packets for the other ports.
CISCO-ICSUDSU-MIB
Integrated CSU/DSU MIB module. For T1 and Switched 56 kbps interfaces.
CISCO-IDSL-LINE-MIB
This MIB module describes IDSL (ISDN Digital Line Subscriber) line interfaces. The structure of this module resembles that of the ADSL-LINE-MIB (RFC-2662). Observe that the tables in this module do not necessarily extend the tables defined by the ADSL-LINE-MIB. Currently, only those tables that contain configuration information extend the profile tables defined by the ADSL-LINE-MIB. This allows the management client to define xDSL configuration profiles that apply across all xDSL modems, independent of the technology being utilized by the modem.
CISCO-IEEE-CFM-MIB
Connectivity Fault Management module for managing IEEE 802.1ag
CISCO-IETF-ATM2-PVCTRAP-MIB
This MIB Module is a supplement to the ATM-MIB.
CISCO-IETF-BFD-MIB
This document contains the Management information base for Bidirectional Forwarding Detection(BFD) Protocol as defined in draft-ietf-bfd-base-06.txt. BFD is a protocol intended to detect faults in the bidirectional path between two forwarding engines, including interfaces, data link(s), and to the extent possible the forwarding engines themselves, with potentially very low latency. It operates independently of media, data protocols, and routing protocols.
CISCO-IETF-DHCP-SERVER-EXT-MIB
The MIB module is an extension of the Cisco IETF Dynamic Host Configuration protocol (DHCP) MIB.
CISCO-IETF-DHCP-SERVER-MIB
The MIB module for entities implementing the server side of the Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration protocol (DHCP) for Internet Protocol version 4(IPv4). This MIB does not include support for Dynamic DNS (DDNS) updating nor for the DHCP Failover Protocol.
CISCO-IETF-DOT11-QOS-EXT-MIB
This MIB module provides network management support for QoS on IEEE 802.11 wireless LAN devices. This MIB is an extension to QoS MIB defined in IEEE 802.11E standard.
CISCO-IETF-DOT11-QOS-MIB
This MIB module provides network management support for QoS on wireless LAN devices. All objects defined in this MIB are listed (object names have been modified to adopt Cisco MIB object naming convention) in the IEEE 802.11E November 2001 draft. The original names of the objects in the standard are included in the REFERENCE clauses. The standard is still under development. The standard IEEE 802.11E MIB can replace some of the MIB objects in this MIB once the standard is finalized.
CISCO-IETF-FRR-MIB
This MIB module contains managed object definitions for MPLS Fast Reroute (FRR)
CISCO-IETF-IP-FORWARD-MIB
The MIB module for the management of CIDR multipath IP Routes.
CISCO-IETF-IP-MIB
The MIB module for managing IP and ICMP implementations, but excluding the management of IP routes.
CISCO-IETF-IPMROUTE-MIB
Address family independent MIB module for management IP Multicast routing, but independent of the specific multicast routing protocol in use. This MIB module is based on RFC 2932 with additional MIB objects to make it a address family independent MIB. This Cisco MIB was created due to non availability of RFC or an Internet Draft which can provide address family independent MIB for IP Multicast Routing. This MIB may later be deprecated with a stable RFC or an Internet Draft
CISCO-IETF-ISIS-CAPABILITY
Agent capabilities for CISCO-IETF-ISIS-MIB
CISCO-IETF-ISIS-MIB
This document describes a management information base for the IS-IS Routing protocol, as described in ISO 10589, when it is used to construct routing tables for IP networks, as described in RFC 1195. This MIB is entirely based upon the IETF draft draft-ietf-isis-wg-mib-16.
CISCO-IETF-ISNS-MGMT-MIB
The Cisco version of the ISNS Management MIB draft draft-ietf-ips-isns-mib-06.txt from the IETF.
CISCO-IETF-MEGACO-MIB
This MIB module is based on the Internet Draft draft-ietf-megaco-mib-05.txt. It defines the attributes of Megaco protocol. Reference: ITU H.248 (Rev. COM16-107).
CISCO-IETF-MPLS-TE-P2MP-STD-MIB
This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering
CISCO-IETF-MSDP-MIB
An experimental MIB module for MSDP Management and Monitoring.
CISCO-IETF-NAT-MIB
This MIB module defines the generic managed objects for NAT.
CISCO-IETF-PIM-EXT-MIB
The MIB module which extends PIM management capabilities defined in CISCO-IETF-PIM-MIB.
CISCO-IETF-PIM-MIB
Address family independent MIB module for management of PIM routers. This MIB module is based on RFC 2934 with additional MIB objects added to make it address family independent MIB. This Cisco MIB was created due to non availability of RFC or an Internet Draft, which can provide address family independent MIB for management of PIM routers. This MIB may later be deprecated with a stable RFC or an Internet Draft.
CISCO-IETF-PPVPN-MPLS-VPN-MIB
This MIB is an extension of the MPLS-VPN-MIB. It contains a new notification, mplsNumVrfRouteMaxThreshCleared, which was added with MPLS-VPN-MIB-DRAFT-05.
CISCO-IETF-PW-ATM-MIB
This MIB contains managed object definitions for Pseudo Wire emulation of ATM over Packet Switched Networks(PSN). This MIB reports to the PW-MIB. The PW-MIB contains structures and MIB associations generic to Pseudo-Wire Virtual Circuit (VC) emulation. VC-specific MIBs (such as this) contain config and stats for specific VC types.
CISCO-IETF-PW-ENET-MIB
This MIB describes a model for managing Ethernet point-to-point pseudo wire services over a Packet Switched Network (PSN).
CISCO-IETF-PW-FR-MIB
Cisco Pseudo Wire Frame Relay MIB This MIB describes network management objects defined for FRoPW services over a Packet Switched Network (PSN). As described in the IETF Frame Relay over Pseudowire (FRoPW) draft, draft-ietf-pwe3-frame-relay-01.txt, FR VCs and PW can be mapped in 2 modes: One-to-one mapping mode: a FR VC is mapped to a PW. This mode is described by cpwVcFrTable. Many-to-one mapping mode (a.k.a. port mode): multiple FR VCs assigned to a port are mapped to a PW. This mode is addressed by cpwVcFrPortModeTable. In this mode, all data frames are directed to the associated PSN tunnel regardless of DLCI.
CISCO-IETF-PW-MIB
This MIB contains managed object definitions for Pseudo Wire operation as in: Pate, P., et al, , Xiao, X., et al, , Martini, L., et al, , and Martini, L., et al, . The indexes for this MIB are also used to index the PSN- specific tables and the VC-specific tables. The VC Type dictates which VC-specific MIB to use. For example, a 'cep' VC Type requires the use the configuration and status tables within the CEP-MIB. This MIB enable the use of any underlying packet switched network (PSN). Specific tables for the MPLS PSN is currently defined in a separate CISCO-IETF-PW-MPLS-MIB. Tables to support other PSNs (IP, L2TP for example) will be added to this MIB in future revisions. At the time of publication of this version, there are no PWE3 WG documents for all features and objects in this MIB, and the MIB is therefore subject to change based on the WG progress.
CISCO-IETF-PW-MPLS-MIB
This MIB complements the CISCO-IETF-PW-MIB for PW operation over MPLS.
CISCO-IETF-PW-TDM-MIB
This MIB contains managed object definitions for encapsulating TDM (T1,E1, T3, E3, NxDS0) as pseudo-wires over packet-switching networks (PSN). This MIB supplements the CISCO-IETF-PW-MIB. The CISCO-IETF-PW-MIB contains structures and MIB associations generic to Pseudo-Wire (PW) emulation. PW-specific MIBs (such as this) contain config and stats for specific PW types.
CISCO-IETF-SCTP-EXT-MIB
An extension to the CISCO-IETF-SCTP-MIB.my used to provide additional information to manage the Stream Control Transmission Protocol (RFC 2960).
CISCO-IETF-SCTP-MIB
The MIB module for managing SCTP protocol (RFC 2960).
CISCO-IETF-VDSL-LINE-MIB
The MIB module defining objects for the management of a pair of VDSL modems at each end of the VDSL line. Each VDSL line has an entry in an ifTable. An agent may reside at either end of the VDSL line however the MIB is designed to require no management communication between them beyond that inherent in the low-level VDSL line protocol. The agent may monitor and control this protocol for its needs. VDSL lines may support optional Fast or Interleaved channels. If these are supported, additional entries corresponding to the supported channels must be created in the ifTable. Thus a VDSL line that supports both channels will have three entries in the ifTable, one for each physical, fast, and interleaved, whose ifType values are equal to vdsl(97), fast(125), and interleaved(124), respectively. The ifStackTable is used to represent the relationship between the entries.
CISCO-IETF-VPLS-BGP-EXT-MIB
This MIB module enables the use of any underlying Pseudo Wire network. This MIB extends the MIB module published in the RFC 4188 to manage object definitions for BGP signalled VPLS.
CISCO-IETF-VPLS-GENERIC-MIB
This MIB module contains generic managed object definitions for Virtual Private LAN Services as in [L2VPN-VPLS-LDP] and [L2VPN-VPLS-BGP] This MIB module enables the use of any underlying Pseudo Wire network.
CISCO-IETF-VPLS-LDP-MIB
This MIB module contains managed object definitions for LDP signalled Virtual Private LAN Services as in [L2VPN-VPLS-LDP] This MIB module enables the use of any underlying Pseudo Wire network.
CISCO-IETF-VRRP-MIB
This MIB describes objects used for managing Virtual Router Redundancy Protocol (VRRP) over IPv4 and IPv6 protocols. This MIB supports VRRP for IPv4 and IPv6 protocols simultaneously running on a given interface of a router.
CISCO-IF-CALL-SERVICE-MIB
The MIB is used to manage call service state for interfaces on media gateway.
CISCO-IF-EXTENSION-MIB
A MIB module for extending the IF-MIB (RFC2863) to add objects which provide additional information about interfaces not available in other MIBS. This MIB replaces the OLD-CISCO-INTERFACES-MIB.
CISCO-IF-LINK-CONFIG-MIB
The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interfaces).
CISCO-IF-LOOPBACK-MIB
The MIB module to configure the loopback on certain interfaces in ifTable with ifType ds1/e1, ds3/e3, ds0 etc.
CISCO-IF-MONITOR-NOTIF-MIB
Interface Monitor Notification MIB This MIB module defines the objects for sending notifications when certain errors over an interval have reached/exceeded a threshold, causing a severe condition.
CISCO-IF-THRESHOLD-MIB
This MIB module defines the managed objects that support monitoring of thresholds on interfaces. Configuration and monitoring of the thresholds is done through threshold templates that can be assigned to any subset of interfaces on the network element. More than one threshold template can be assigned to a given interface. This MIB module should be used when it is desired to apply a common set of thresholds to a subset of the available interfaces. If a threshold is to be applied to only one interface, then the EVENT-MIB or the RMON-MIB may be used as simpler alternatives. If a threshold is to be applied to all available interfaces, then the EVENT-MIB may be used as a simpler alternative.
CISCO-IGMP-FILTER-MIB
IGMP Filter configuration MIB. This MIB provides a mechanism for users to configure the system to intercept IGMP joins for IP Multicast groups identified in this MIB and only allow certain ports to join certain multicast groups.
CISCO-IGMP-SNOOPING-MIB
The MIB module for IGMP Snooping feature. Internet Group Management Protocol (IGMP) is the protocol used by IPv4 end hosts to indicate their interest in receiving multicast traffic for certain multicast groups to neighboring multicast routers. Version 3 of IGMP adds support for source based filtering; which means the end hosts can specifically indicate to receive or not-receive multicast packets from specific source addresses. This information is used by the multicast routers to restrict forwarding of multicast traffic for the host. IGMP Snooping is a switch protocol. A switch that implements IGMP Snooping listens to the IGMP messages exchanged between the hosts and router, then provides selective transmission of multicast traffic based on multicast mac destination address or multicast group address. With IGMPv3 support, IGMP Snooping can potentially provide selective transmission of multicast data based on (source address, group address) onto the ports that are interested. In addition to this, IGMP Snooping can also provide proxy reporting, report suppression and fast leave capabilities.
CISCO-IKE-CONFIGURATION-MIB
This is a MIB Module for configuring and viewing IKE parameters and policies.
CISCO-IKE-FLOW-EXT-MIB
This MIB module is an extension to CISCO-IKE-FLOW-MIB and contains Cisco Specific extensions for monitoring IKE. It is for monitoring the structures and status of IPsec control flows based on Internet Key Exchange protocol.
CISCO-IKE-FLOW-MIB
This is a MIB module for monitoring the structures and status of IPsec control flows based on Internet Key Exchange protocol. The MIB models standard aspects of the IKE protocol. Synopsis This MIB module models status, performance and failures of the IKEv1- and IKEv2-based signaling in IPsec, FC-SP(and similar) protocols. In practice, the security protocols such as IPsec, FC-SP and CTS use a signaling protocol such as IKE, KINK, or some such. A number of characteristics of these signaling protocols are generic. The generic attributes and status of signaling activity has been modeled in CISCO-IPSEC-SIGNALING-MIB. This MIB module augments CISCO-IPSEC-SIGNALING-MIB with IKE-specific MIB objects. (Signaling protocols are also referred to this document as 'Control Protocols', since they perform session control.)
CISCO-IMA-MIB
The MIB module describes Cisco IMA objects. This is an extension to the standard of ATM Forum IMA version 1.1, AF-PHY-0086.001 Spec. atmfImaMib.
CISCO-IMAGE-CHECK-MIB
Initial version of Image Check MIB.
CISCO-IMAGE-LICENSE-MGMT-MIB
The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a device on a chosen image level. This mechanism is referred to as image level licensing. Image level licensing leverages the universal image based licensing solution.
CISCO-IMAGE-MIB
Router image MIB which identify the capabilities and characteristics of the image
CISCO-IMAGE-UPGRADE-MIB
This mib provides, objects to upgrade images on modules in the system, objects showing the status of the upgrade operation, and objects showing the type of images that could be run in the system. For example the modules could be Controller card, Line card .. etc. The system fills up the ciuImageVariableTable with the type of images the system can support. For performing an upgrade operation a management application must first read this table and use this info in other tables, as explained below. The ciuImageURITable table is also filled by the system and provides the image name presently running for each type of image in the system. The user is allowed to configure a new image name for each image type as listed in ciuImageVariableTable. The system would use this image on the particular module on the next reboot. The management application on deciding to do an upgrade operation must first check if an upgrade operation is already in progress in the system. This is done by reading the ciuUpgradeOpCommand and if it contains 'none', signifies that no other upgrade operation is in progress. Any other value, signifies that upgrade is in progress and a new upgrade operation is not allowed. To start an 'install' operation, first the user must perform a 'check' operation to do the version compatibility for the given set of image files (provided using the ciuImageLocInputTable) against the current system configuration. Only if the result of this operation is 'success' can the user proceed to do an install operation. The tables, ciuVersionCompChkTable, ciuUpgradeImageVersionTable, ciuUpgradeOpStatusTable, provide the result of the 'check' or 'install' operation performed using ciuUpgradeOpCommand. These tables are in addition to objects ciuUpgradeOpStatus, ciuUpgradeOpTimeStarted, ciuUpgradeOpTimeCompleted, ciuUpgradeOpStatusReason. The ciuUpgradeOpStatus object provides the status of the selected upgrade operation. An option is available for user to upgrade only some modules, provided using ciuUpgradeTargetTable. If this table is empty than an upgrade operation would be performed on all the modules in the system.
CISCO-INTERFACE-XCVR-MONITOR-MIB
A MIB module that provides monitoring information about the transceivers plugged into interface on a system.
CISCO-INTERFACETOPN-EXT-MIB
This MIB module is an extension to INTERFACETOPN-MIB. It provides additional management information for sorting device interfaces.
CISCO-IP-CBR-METRICS-MIB
This MIB module defines objects that describe the a set of metrics used to measure the quality of a IP CBR traffic flow. An IP CBR traffic flow consists of a stream of IP datagrams sent from one application to another with a constant packet rate or bit rate.
CISCO-IP-ENCRYPTION-MIB
Used to manage the encryption feature.
CISCO-IP-IF-MIB
The MIB module for configuring IP characteristics of the interfaces of a device.
CISCO-IP-LOCAL-POOL-MIB
This MIB defines the configuration and monitoring capabilities relating to local IP pools.
CISCO-IP-NW-DISCOVERY-MIB
MIB to provide the information about the disjoint IP networks connected to the various gigabit ethernet interfaces in the 'Fabric' and objects to discover the same. It is possible that multiple disjoint IP networks may terminate on a single fibre channel switch in a Fabric. This MIB provides ability to initiate, configure and show discovery results of the IP Networks in the fabric.
CISCO-IP-PROTOCOL-FILTER-MIB
The MIB module is for management of information to support packet filtering on IP protocols. The cippfIpProfileTable allows users to create delete, and get information about filter profiles. Filter profiles are uniquely identified by the profile names. Filter profiles can either be of Simple or Extended usage types, and the usage type cannot be changed once it has been created. The cippfIfIpProfileTable applies the filtering profiles to device interfaces running IP. A filter profile can be applied to multiple interfaces. The cippfIpFilterTable contains ordered lists of IP filters for all the filtering profiles. Filters and profiles are related if they are of the same filter profile name. Filters can only be created if their associated filter profiles already exist in the cippfIpProfileTable. Filters of the same profile name belongs to a common profile. The cippfIfIpProfileTable can be configured with information independent from the other. However, if the name of a profile in the cippfIfIpProfileTable matches that of any profile in the cippfIpProfileTable and the profile name of any filter entry in the cippfIpFilterTable, the profile is 'active' and the filter entry is being applied to IP traffic passing through the attached device interfaces. Therefore, any change to the filters in the cippfIpFilterTable or the profile itself in the cippfIpProfileTable will affect all the attached interfaces.
CISCO-IP-RAN-BACKHAUL-MIB
This MIB provides information on the IP-RAN traffic from cell site to aggregation site in the following situations. In an GSM environment the cell site will be the Base station Transceiver System(BTS) and the aggregation site will be the Base Station Controller(BSC). In the UMTS environment the cell site will be the B-Node and the aggregation site will Radio Network Controller(RNC).
CISCO-IP-STAT-MIB
This MIB incorporates objects to provide support for the Cisco IP statistics as implemented in command interfaces ip accounting [ mac-address {input | ouput } | precedence { input | ouput } ] The above CLI provides additional IP statistics categorized by precedence of IP packets, as well as the MAC address associated with IP packets. This is a supplement to those defined in OLD-CISCO-IP-MIB.my.
CISCO-IP-UPLINK-REDIRECT-MIB
This MIB module is for the configuration of Cisco IP Uplink Redirect feature.
CISCO-IP-URPF-MIB
Unicast Reverse Path Forwarding (URPF) is a function that checks the validity of the source address of IP packets received on an interface. This in an attempt to prevent Denial of Service attacks based on IP address spoofing. URPF checks validity of a source address by determining whether the packet would be successfully routed as a destination address. Based on configuration, the check made can be for existence of any route for the address, or more strictly for a route out the interface on which the packet was received by the device. When a violating packet is detected, it can be dropped. This MIB allows detection of spoofing events.
CISCO-IPMCAST-MIB
The MIB module for Cisco-specific management of IP Multicast in Cisco devices.
CISCO-IPMROUTE-MIB
The MIB module for management of IP Multicast routing, but independent of the specific multicast routing protocol in use.
CISCO-IPSEC-FLOW-MONITOR-MIB
This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopted as an IETF standard. Hence Cisco-specific features of IPSec protocol are excluded from this MIB.
CISCO-IPSEC-MIB
The MIB module for modeling Cisco-specific IPsec attributes
CISCO-IPSEC-POLICY-MAP-MIB
The MIB module maps the IPSec entities created dynamically to the policy entities that caused them. This is an appendix to the IPSEC-MONITOR-MIB that has been proposed to IETF for monitoring IPSec based Virtual Private Networks.
CISCO-IPSEC-PROVISIONING-MIB
IPSec is the next-generation network layer crypto framework described in RFC2401-2411. This MIB defines the IPsec configurations. It may be used to view and provision IPsec-based VPNs. To create an IPsec tunnel, you need first configure Internet Key Exchange (IKE). IKE negotiates Security Associations with the peer for IPsec. To find out how to configure IKE, please see CISCO-IKE-CONFIGURATION-MIB for detail.
CISCO-IPSEC-SIGNALING-MIB
This MIB Module models status, performance and failures of a protocol with the generic characteristics of signalling protocols used with IPsec and FC-SP protocols. Examples of such protocols include IKE, KINK, etc. This MIB views the common attributes of such protocols. Signaling protocols are also referred in this document as 'Control Protocols', since they perform session control. This MIB is an attempt to capture the generic aspects of the signaling activity. The protocol-specific aspects of a signaling protocol still need to be captured in a protocol-specific MIB (e.g., CISCO-IKE-FLOW-MIB, etc.).
CISCO-IPSLA-AUTOMEASURE-MIB
This module defines the MIB for IP SLA Automation.
CISCO-IPSLA-ECHO-MIB
This MIB module defines the templates for IP SLA operations of ICMP echo, UDP echo and TCP connect. The ICMP echo operation measures end-to-end response time between a Cisco router and any IP enabled device by computing the time taken between sending an ICMP echo request message to the destination and receiving an ICMP echo reply. The UDP echo operation measures end-to-end response time between a Cisco router and any IP enabled device by computing the time taken between sending an UDP echo request message to the destination and receiving an UDP echo reply. The TCP connect operation measures end-to-end response time between a Cisco router and any IP enabled device by computing the time taken to perform a TCP connect operation.
CISCO-IPSLA-ETHERNET-MIB
CISCO-IPSLA-JITTER-MIB
This MIB module defines templates for IP SLA operations of UDP Jitter and ICMP Jitter. The UDP Jitter operation is designed to measure the delay variance and packet loss in IP networks by generating synthetic UDP traffic. The ICMP Jitter operation provides capability to measure metrics such as RTT (Round Trip Time), jitter, packet loss, one-way latency by sending ICMP Timestamp stream to the destination devices.
CISCO-IPSLA-VIDEO-MIB
IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, network assessment and health monitoring. This MIB defines a collection of statistics resulting from the 'video' IP SLA operation.
CISCO-IPSLA-VIDEO-PROFILE-MIB
IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, network assessment and health monitoring.
CISCO-ISCSI-GW-MIB
MIB module for monitoring and configuring iSCSI gateway functions. An iSCSI gateway represents FC (Fibre Channel) targets/initiators as iSCSI targets/initiators respectively and vice versa. It means that an iSCSI target/initiator is presented to the FC network as a virtual FC target/initiator which can be accessed by the real FC initiators or can access real FC targets, respectively. It is up to the gateway implementation how to represent the targets/initiators in each of the domains. For example, a gateway implementation may choose to represent multiple FC targets either as one iSCSI target or multiple iSCSI targets (one to one). Same applies to initiators also.
CISCO-ISCSI-MIB
The iSCSI Protocol MIB module.
CISCO-ISDN-MIB
The MIB module to describe the status of the ISDN Interfaces on the routers.
CISCO-ISDNU-IF-MIB
ISDN BRI integrated U Interface MIB module. This MIB manages the ISDN BRI integrated U Interface in the router.
CISCO-ISNS-CLIENT-MIB
MIB module for monitoring and configuring Internet Storage Name Service (iSNS) client.
CISCO-ITP-ACL-MIB
The MIB for managing access lists that control messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signaling point. The relevant ITU documents describing this technology is the ITU Q series, including ITU Q.700: Introduction to CCITT Signalling System No. 7 and ITU Q.701 Functional description of the message transfer part (MTP) of Signalling System No. 7.
CISCO-ITP-ACT-MIB
The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. This information can be used to manage messages transported over SS7 Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signaling point.
CISCO-ITP-DSMR-MIB
The MIB for providing information about Distributed Short Message Routing for Short Message Service Center. This MIB will provide information used to control and measure SS7 messages signalling units in a SS7 Network.
CISCO-ITP-DSMR-SMPP-MIB
The MIB for providing information about Distributed Short Message Routing delivery using Short Message Peer-to-Peer protocol.
CISCO-ITP-DSMR-UCP-MIB
The MIB for providing information about Distributed Short Message Routing delivery using Universal Computer Protocol.
CISCO-ITP-GACT-MIB
The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. This information can be used to manage messages transported over SS7 Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signalling point.
CISCO-ITP-GRT-MIB
This MIB is for managing information required to route messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides the functions necessary to act as a SS7 signalling point. Each signalling point is connected to other signalling point using IP based or traditional TDM links.
CISCO-ITP-GSCCP-MIB
The MIB for signalling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. This MIB provides information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 Signalling point.
CISCO-ITP-GSP-MIB
The MIB for managing Signalling Points and its associated messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. This MIB replaces the CISCO-ITP-SP-MIB and provide support multiple instances of a signalling point within same configuration. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 Signalling point. The relevant ITU documents describing this technology is the ITU Q series, including ITU Q.700: Introduction to CCITT Signalling System No. 7 and ITU Q.701 Functional description of the message transfer part (MTP) of Signalling System No. 7.
CISCO-ITP-GSP2-MIB
The MIB for providing information specified in ITU Q752 Monitoring and Measurements for signalling System No. 7(SS7) Network. This information can be used to manage messages transported over SS7 Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signalling point. The relevant ITU documents describing this technology is the ITU Q series, including ITU Q.700: Introduction to CCITT signalling System No. 7 and ITU Q.701 Functional description of the message transfer part (MTP) of signalling System No. 7. The ITP Quality of Service (QoS) model allows the definition of 8 QoS classes, 0 through 7. QoS classes can be assigned only SCTP links. Only one QoS class can be assigned to an SCTP link. Class 0 will be designated as the default class. Packets that are not classified to a designated QoS class will get assigned to the default class. Each provisioned QoS class can be assigned an IP precedence value or a Differential Services Code Point (DSCP). The default class is initialized to IP precedence zero (0). The default class initial TOS setting can be changed through the command line interface. The Type of Service (TOS) byte in the IP header will be set to the IP precedence or DSCP that is assigned to class. Every packet forwarded over an SCTP link that was provisioned for a given QoS class will have the TOS byte set.
CISCO-ITP-GTCAP-MIB
The MIB for Transaction Capabilities(TCAP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point.
CISCO-ITP-MLR-MIB
The MIB for providing information about Multi-layer Routing(MLR). This MIB will provide information used to control and measure SS7 messages signalling units in a SS7 Network. Message Signalling Units are routed based on information found in the SCCP, TCAP, MAP, and MAP-user layers. It uses information from these layers to make customizable routing decision based on the following criteria. - message A-address (origination SME) - message B-address (destination SME) - protocol identifier - operation code - called party address - calling party address The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signalling point. The Multi-layer SMS router will be developed in compliance to the following standards. - GSM MAP v1, v2 and v3 MO SMS formats - GSM MAP SMS user information for MO messages - IS-41 MAP Mobile Originated SMS formats for Revisions A thru D.
CISCO-ITP-MONITOR-MIB
The MIB for providing information related to monitoring SS7 links. This information can be used to manage the state of software used to collect all packets transported and received over a SS7 link.
CISCO-ITP-MSU-RATES-MIB
This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher level protocols require several MSUs per transaction. Traffic capacity planning is based on MSUs not transactions. This MIB will provide information to determine current traffic. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signalling point.
CISCO-ITP-RT-MIB
This MIB is for managing information required to route messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides the functions necessary to act as a SS7 signalling point. Each signalling point is connected to other signalling point using IP based or traditional TDM links.
CISCO-ITP-SCCP-MIB
The MIB for Signaling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. This MIB for provides information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signaling point.
CISCO-ITP-SP-MIB
The MIB for managing Signalling Points and its associated messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 Signalling point.
CISCO-ITP-SP2-MIB
The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signaling System No. 7(SS7) Network. This information can be used to manage messages transported over SS7 Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signaling point.
CISCO-ITP-XUA-MIB
The MIB for MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) for Cisco's IP Transfer Point (ITP) implementation. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signaling point.
CISCO-IVR-MIB
The MIB module for the management of Inter-VSAN routing within the framework of Cisco's Inter-VSAN Routing (IVR) Architecture. IVR allows traffic between VSANs. VSANs are logically separated Storage Area Networks (SANs) where traffic does not cross VSAN boundaries. Certain SAN applications need restricted communication between initiators and targets which are in different VSANs. This MIB enables the users to manage IVR. The VSANs logically separate a single physical fabric into multiple logical fabrics. Each of these physical fabrics are called Autonmous Fabrics. In addition to Inter-VSAN communication, IVR also enables communication between Autonomous Fabrics.
CISCO-L2-CONTROL-MIB
The CISCO-L2-CONTROL-MIB is used to control some layer 2 functions, including MAC limit function and unicast flooding. This device could be a router or a switch.
CISCO-L2-DEV-MONITORING-MIB
This MIB module is for monitoring of active layer 2 devices by hot standby layer 2 devices and the configuration of hot standby switch-over parameters.
CISCO-L2-TUNNEL-CONFIG-MIB
This MIB module is for layer 2 tunneling related configurations on a device. Tunneling allows separate local networks to be considered as a single VLAN. These separate networks are connected via an ISP, which will tunnel the packets from one network to another, making it appear as if the two networks are actually just one.
CISCO-L2L3-INTERFACE-CONFIG-MIB
Interface switchport mode configuration management MIB. This MIB is used to monitor and control configuration of interface switchport and routed mode.
CISCO-L4L7MODULE-REDUNDANCY-MIB
The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. This MIB provides the tables/objects that support redundancy configuration and redundancy statistics. The redundancy model supported by this MIB allows two or more SLB devices to be configured with one or more redundancy group. Each redundancy group is identified by a unique group ID. Two or more devices are redundant to each other if they use the same redundancy Group ID.
CISCO-L4L7MODULE-RESOURCE-LIMIT-MIB B
The MIB module for managing resource classes and configuring limits(max/min) to different resources. The resource referenced in this MIB are in addition to resource information availale in other MIBs. This MIB is applicable to L4-L7 modules which supports managing resource limits using a centralized approach.
CISCO-LAG-MIB
Cisco Link Aggregation module for managing IEEE Std 802.3ad. This MIB provides Link Aggregation information that are either excluded by IEEE Std 802.3ad (IEEE8023-LAG-MIB) or specific to Cisco products
CISCO-LATITUDE-MIB
The MIB module for the managment of Cisco Latitude MeetingPlace conferencing solution.
CISCO-LEC-DATA-VCC-MIB
This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. This extension identifies those VCCs which are being used to carry packets sent on LANE Data Direct VCCs.
CISCO-LEC-EXT-MIB
This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB
CISCO-LECS-MIB
The MIB module for the management of LANE Configuration in Cisco devices.
CISCO-LES-MIB
The MIB module for the management of LANE Service in Cisco devices.
CISCO-LICENSE-MGMT-MIB
The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various features in the system.
CISCO-LICENSE-MGR-MIB
The MIB module for a method of managing license files on the system. Licensing mechanism provides more flexibility in supporting various features in the system. Feature License is the specification of the permission to use a particular feature, indicated through license file. The permissions can also specify the limit on the number of concurrent usages of the feature, the limit on time period of the feature usage and the device where the feature has to be used. License files will be given to customers when they buy the licenses. User should copy the license file to some location on the system, for installing.
CISCO-LINK-ERROR-MONITOR
The MIB module for managing Link Error Monitoring Feature on devices. Link Error Monitoring Feature provides a mechanism to monitor a certain set of link error counters on an interface and take certain actions when the increase in the error counters between two consecutive samplings exceeds the configurable thresholds consecutively for a certain number of times.
CISCO-LINK-ERROR-MONITOR-MIB
The MIB module for managing Link Error Monitoring Feature on devices. Link Error Monitoring Feature provides a mechanism to monitor a certain set of link error counters on an interface and take certain actions when the increase in the error counters between two consecutive samplings exceeds the configurable thresholds consecutively for a certain number of times.
CISCO-LOCAL-DIRECTOR-MIB B
The MIB module to view information about LocalDirector. The Cisco LocalDirector is a device designed for the purpose of load balancing TCP traffic at an Internet site. To implement load balancing, an IP address (and optionally a port and a 'bind ID') is chosen to be the publically accessible 'virtual machine'. Then a number of actual Internet servers are 'bound' to this virtual machine. The servers are called 'real machines'. The relationships between virtual and real machines can be one to many, many to one, or many to many. More detailed information about the LocalDirector is available in the 'Cisco LocalDirector Installation and Configuration Guide', available online at www.cisco.com.
CISCO-LRE-CPE-MIB
The MIB module for the Cisco Long Reach Ethernet Customer Premise Equipment device information.
CISCO-LWAPP-AAA-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC), that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is used to manage AAA information on the controller.
CISCO-LWAPP-ACL-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU.
CISCO-LWAPP-AP-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the 802.11 Access Points that have joined the controller.
CISCO-LWAPP-CCX-RM-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is for CCX related features as specified in the CCX specifications.
CISCO-LWAPP-CDP-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about CDP neighbors of LWAPP APs. The MIB provides configuration of CDP feature on the LWAPP Access Points. The MIB can also be used to retrive the status of the CDP cache information on the various LWAPP LWAPP Access Points. The CDP MIB is also supported by Controller and provides configuration and status information about CDP neighbours of the controller.
CISCO-LWAPP-CLIENT-ROAMING-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is for CCX related features as specified in the CCX specifications. This MIB covers roaming RF parameters for CCX clients.
CISCO-LWAPP-DOT11-CLIENT-CALIB-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is about the configuration and monitoring of 802.11 wireless clients in the network.
CISCO-LWAPP-DOT11-CLIENT-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is about the configuration and monitoring of 802.11 wireless clients in the network.
CISCO-LWAPP-DOT11-LDAP-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is used to manage LDAP features on the controller.
CISCO-LWAPP-DOT11-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. This MIB provides the information about the operational parameters of the 802.11 networks. References about specific type of 802.11 flavors like 802.11a/b/g or 802.11n will be made whereever required to indicate that the respective parameters are applicable only to that particular type of 802.11 networks.
CISCO-LWAPP-IDS-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides the information used to integrate the LWAPP controller with external IDS/IPS applications. LWAPP controllers interact with these applications to protect the network against various threats that would compromise the overall security of the network.
CISCO-LWAPP-LINKTEST-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Link Test is performed to learn the radio link quality between AP and Client. CCX linktest is performed for CCX clients. With CCX linktest radio link can be measured in both direction i.e. AP->Client(downLink) and Client->AP(uplink). When client does not support CCX or CCX linktest fails,ping is done between AP and Client. In ping test, only uplink (client->AP) quality can be measured.
CISCO-LWAPP-LOCAL-AUTH-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is used to manage Local authentication information on the controller.
CISCO-LWAPP-MESH-BATTERY-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol (LWAPP) tunnel from Light-weight Access Points. This MIB represents information about the status of the Multipurpose Power Supply (MPS), used as backup power supply for an Access Point (AP) in the Wireless Mesh Network. The MPS reports status information to the AP periodically. The AP inturn reports the battery status information to the controller periodically as a part of the LWAPP information packet. General Infomation about Cisco Wireless Mesh network: A Mesh AP (MAP) can associate directly with another Root AP (RAP) or with another MAP AP. Each association of AP (MAP-MAP or RAP-MAP) with another AP forms parent-child relationship.
CISCO-LWAPP-MESH-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol (LWAPP) tunnel from Light-weight Access Points. This MIB represents information used in Wireless Mesh Network. MAP APs associates directly with RAP APs or with another MAP AP. Each association of AP (MAP-MAP or RAP-MAP) with another AP forms parent-child relationship.
CISCO-LWAPP-MESH-STATS-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol (LWAPP) tunnel from Light-weight Access Points. This MIB represents statistics collected for mesh node in Wireless Mesh Network.
CISCO-LWAPP-MFP-MIB.
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB instrumentation provides the parameters used by the controller to control and monitor the behavior of the associated Access Points when following the newly defined Management Frame Protocol. The controller would pass the MFP settings configured by the user through this MIB to the APs through LWAPP messages. The APs then begin to validate and verify the integrity of 802.11 Management frames and report the anomalies found, if any, to the controller.
CISCO-LWAPP-MOBILITY-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the 802.11 WLAN mobility.
CISCO-LWAPP-QOS-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is used to study the quality of service in the voice and video traffic on the WLAN.
CISCO-LWAPP-REAP-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. Information represented by this MIB is passed by the controller to those Cisco LWAPP APs, that can operate in stand-alone mode.
CISCO-LWAPP-ROGUE-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. This MIB provides information about the Rogue APs and Clients that are detected by the controller.
CISCO-LWAPP-RRM-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is used to study the RRM on the WLAN.
CISCO-LWAPP-SYS-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. This MIB provides global configuration and status information for the controller. All general system related information is presented in this MIB.
CISCO-LWAPP-TSM-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Network management stations learn the audio/video traffic quality observed on WLANs through this MIB.
CISCO-LWAPP-WEBAUTH-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. This MIB is used to configure web authentication parameters in the controller to manage clients' authentication. The mobile nodes are web-authenticated if they select the WLAN that has web security enabled.
CISCO-LWAPP-WLAN-MIB
This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. This MIB helps to manage the WLANs on the controller.
CISCO-LWAPP-WLAN-SECURITY-MIB
This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information provided by this MIB is for WLAN security related features as specified in the CCKM, CKIP specifications.
CISCO-MAC-AUTH-BYPASS-MIB
MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides controlled access to devices based on their MAC addresses. MAB allows non-dot1x compliant end devices controlled access to network and also provides a replacement technology for VLAN Management Policy Server (VMPS) environments. MAB is also an intergal part of the Network Access Control (NAC) program which enables network access for the clients and subsequently carry out a posture assessment of these clients. MAC Authentication Bypass feature provides a mechanism that uses the MAC address of the connecting device to grant or deny network access for it.
CISCO-MAC-NOTIFICATION-MIB
This MIB module is for configuration of the MAC notification feature. MAC notification is a mechanism to inform monitoring devices when there are MAC addresses learnt or removed from the forwarding database of the monitored devices.
CISCO-MAU-EXT-MIB
A MIB module for extending the MAU-MIB (RFC 3636) to add objects which provide additional management information about MAU or Jack not available in MAU-MIB.
CISCO-MDI-METRICS-MIB
This MIB module defines objects that describe the Media Delivery Index (MDI). The MDI [RFC4445] measurement describes the quality indicator of a network intended to delivery applications such as streaming media, MPEG video, VoIP, or other information sensitive to arrival time and packet loss.
CISCO-MEDIA-GATEWAY-MIB
The MIB module for managing Trunk Media Gateway. A Media Gateway is a network element that provides conversion between the audio signals carried on telephone circuits and data packets carried over the Internet or over other packet data networks. Trunk Media Gateway interface is between the telephone network and a Voice over IP/ATM network. The interface on a Trunk Gateway terminates a trunk connected to PSTN switch (e.g., Class 5, Class 4, etc.). Media Gateways use a call control architecture where the call control 'intelligence' is outside the gateways and handled by external call control elements, called Media Gateway Controllers (MGCs). The MGCs or Call Agents, synchronize with each other to send coherent commands to the gateways under their control.
CISCO-MEDIA-QUALITY-MIB
This MIB module enhances the DIAL-CONTROL-MIB (RFC2128) by providing call information and voice and video quality statistics of call legs over a telephony and voice over IP network.
CISCO-MEETINGPLACE-MIB
This MIB allows management of Cisco Unified MeetingPlace (CUMP) features, CUMP is the key conferencing solution component for Cisco Unified Communications. The CUMP MIB runs on the CUMP application server and provides the status/usage information, and minor/major system alarms to the monitoring station. The monitoring station can either pull application server information through the MIB or set as a trap destination to receive alarms.
CISCO-MEGACO-EXT-MIB
The MIB module is an extension of CISCO-IETF-MEGACO-MIB. It defines the attributes of ITU H.248 protocol.
CISCO-MEMORY-POOL-MIB
MIB module for monitoring memory pools
CISCO-METRO-PHY-MIB
This MIB module defines the managed objects for physical layer related interface configurations and objects for the protocol specific error counters for DWDM optical switches. This MIB contains three groups. The first group, cmPhyIf group, handles the physical layer related interface configurations. The cmPhyIfTable has objects for configuring protocol, rate, error monitoring, loopback mode and safety features like OFC (Open Fibre Control), laser safety control and forward laser control. The second group, cmPhyStatistics group, represents the counters that collect error statistics on the received data traffic for all protocols except SONET. The error statistics for SONET are covered in the SONET-MIB. The third group, cmPhySonetSectionTrace group, provides objects for section trace monitoring on SONET/SDH interfaces.
CISCO-MGC-MIB
This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a specific gateway(cmgwIndex). The call agent is an external element (outside of gateway) with call control intelligence to control call connection in gateway. The protocols used for communication between voice gateway and call agent included SGCP, MGCP, ... Multiple IP addresses can be associated with one call agent. An MGC group is a logical grouping of several MGCs into one group. MGC redundancy is used to support multi call agent for one gateway. With MGC redundancy, a voice gateway can send gateway-initiated-commands to the next MGC in the MGC group if it fails to receive response from any IP address(es) associated to the current MGC.
CISCO-MGX82XX-ATM-UNI-PORT-MIB
The MIB module containing objects related to user-side of the ATM UNI Port. The mib is applicable for MGX8250 and MGX8220 products.
CISCO-MGX82XX-CARD-FEATURE-MIB
The MIB module which describes the features supported in MGX82XX products. This MIB Module provides the features supported in Controller Cards in MGX8250 and MGX8220.
CISCO-MGX82XX-DSX1-MIB
The MIB module to configure DS1/E1 interface objects. This mib also contains the alarm configuration of DS1/E1 interfaces. This mib is supported in T1/E1 service modules.
CISCO-MGX82XX-DSX3-MIB
The MIB Module for DS3/E3 interface configuration , statistics and Alarm configuration. This MIB is supported in T3/E3 service modules in MGX products.
CISCO-MGX82XX-ENVMON-MIB
The MIB module to describe the status of the Environmental Monitoring devices in MGX82xx products.
CISCO-MGX82XX-MODULE-RSRC-PART-MIB
The MIB module to configure the resource partition on service modules(cards) supported in MGX82xx and MGX88xx products.
CISCO-MGX82XX-PXM-CLOCK-MIB
The MIB module to describe the clock configuration in Processor Switch Module(PXM) in MGX82xx product.
CISCO-MGX82XX-RPM-CONN-MIB
The connection MIB module for RPM(Router Blade) service module in MGX8250/MGX8230 products. The 'channel' and 'connection' and 'connection endpoint' mean same in this MIB.
CISCO-MGX82XX-RPM-RSRC-PART-MIB
The MIB module to manage resource partition objects. A resource partition is configured on a RPM subinterface. An administrator can partition connection related resources like VPI, VCI ranges, bandwidth and total amount of available connection entries in the switch through these MIB tables.
CISCO-MGX82XX-RPM-SUBIF-MIB
This MIB is used to provision backplane sub-interfaces on the MGX's Route Processor Module (RPM). This MIB is implemented on the MGX controller to manage the RPM. The RPM family of Router Modules run the IOS Operating System
CISCO-MGX82XX-VIRTUAL-PORT-MIB
The MIB module for configuration ond reporting statistics of virtual ports in PXM1 Service module in MGX82xx series.
CISCO-MGX8800-IF-MAPPING-MIB
This MIB module is used for getting the ifIndex values given physical location and/or logical information. The physical information includes the slot, back-card and physical line, IMA group ID, MFR (Multilink Frame Relay) bundle etc. The logical information includes the logical interface or virtual interface number. In this MIB back card, bay, line module are used to refer to the back card.
CISCO-MLD-SNOOPING-MIB
This MIB module defines objects that describe IGMP/MLD snooping. It provides remote network management system the ability to manage the IGMP/MLD Snooping feature when snooping is operating at the system and port level. Virtual systems and related ports data can be accessed by NMS using appropriate SNMP context. E.g. in order to access data related to a particular L2VPN bridge domain system, the user shall specify on the SNMP request the SNMP context related to that particular bridge domain.
CISCO-MMAIL-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) for providing management of dial peers on both a circuit-switched telephony network, and a mail server on IP network.
CISCO-MMODAL-CONTACT-APPS-MIB
The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure platform for providing contact center applications. The Cisco Unified Expert Advisor (CUEA) is implemented on this platform. The Cisco Unified Expert Advisor application is deployed on multiple devices that form a cluster, where each device could be classified as 'Runtime' or 'Reporting'. Each device hosts a set of services and each service performs a specific task. Not all services will be running on every device. The CISCO-MMODAL-CONTACT-APPS-MIB defines the instrumentation of the services present in the Cisco Unified Expert Advisor. The MIB mainly consists of the run-time statistics of each service and also defines a Notification format. It also defines various groups of objects that are not specific to a service.
CISCO-MOBILE-IP-MIB
An extension to the IETF MIB module defined in RFC-2006 for managing Mobile IP implementations. Mobile IP introduces the following new functional entities: Mobile Node(MN) A host or router that changes its point of attachment from one network or subnetwork to another. A mobile node may change its location without changing its IP address; it may continue to communicate with other Internet nodes at any location using its (constant) IP address, assuming link-layer connectivity to a point of attachment is available. Home Agent(HA) A router on a mobile node's home network which tunnels datagrams for delivery to the mobile node when it is away from home, and maintains current location information for the mobile node. Foreign Agent(FA) A router on a mobile node's visited network which provides routing services to the mobile node while registered. The foreign agent detunnels and delivers datagrams to the mobile node that were tunneled by the mobile node's home agent. For datagrams sent by a mobile node, the foreign agent may serve as a default router for registered mobile nodes. Mobile Router(MR) A mobile node that is a router. It provides for the mobility for one or more networks moving together. The nodes connected to the network server by the mobile router may themselves be fixed nodes, mobile nodes or routers. Mobile Network Network that moves with the mobile router.
CISCO-MOBILE-POLICY-CHARGING-CONTROL-MIB
Mobile PCC Infrastructure built on top of Policy Shim Layer, is a common interface to send and receive PCC related messages for all gateway applications that implement Gx or Ty functionality. Gx is a reference point located between the Policy and Charging Rules Function (PCRF) and the Policy and Charging Enforcement Function (PCEF). Three types of networks namely, 3G UMTS, 4G LTE and 4G WiMax use the 3GPP Gx interface as the standard policy control interface, and CDMA networks use the 3GPP2 Ty interface for the same. This MIB contains the PCC configurations/statistics which are implemented on the Mobile PCC infrastructure.
CISCO-MODEM-MGMT-MIB
This MIB module provides modem call related data for tracking the progress and status of a call
CISCO-MODULE-AUTO-SHUTDOWN-MIB
The CISCO-MODULE-AUTO-SHUTDOWN-MIB is used to configure the module automatic shutdown feature. Modules will be reset by the system when they become faulty. The module auto shutdown feature will shutdown such faulty modules when the resets occur too often. Once the modules are shutdown by this feature, they will stay shutdown until the administrator manually brings them back up. This will prevent the system from constantly resetting the faulty modules. This MIB module also covers the system initiated action occuring on a module.
CISCO-MODULE-VIRTUALIZATION-MIB
This MIB provides a way to create virtual contexts, and managing them. A virtual context is logical partition of a physical device. The Virtual context provide different type of services and can be managed independently. Each virtual context is an independent entity, with its own configuration and supports almost all the options that can be configured on stand-alone hardware. Each context can have a separate management IP address that the user can Telnet/SSH into and send other requests(SNMP, FTP etc). This MIB contains tables for creating/deleting virtual contexts and assigning interfaces and/or interface ranges to virtual contexts.
CISCO-MPLS-TE-STD-EXT-MIB
This MIB module contains Cisco specific managed object definitions for MPLS Traffic Engineering (TE), not contained in MPLS-TE-STD-MIB. The auto bandwidth feature enables MPLS TE Tunnels to adapt automatically their bandwidth to their actual load.
CISCO-MPOA-EXT-MIB
This MIB module is a Cisco extension to the ATM Forum's MPOA MIB. This MIB module consists of object groups to retrieve information about MPOA shortcut VCCs and to bind MPOA entities (MPC & MPS) to physical interfaces.
CISCO-MVPN-MIB
This MIB contains managed object definitions for Cisco implementation of multicast in VPNs defined by the Internet draft: draft-rosen-vpn-mcast-05.txt. Note that this MIB works along with the L3VPN-MPLS-VPN-MIB.
CISCO-NAC-NAD-MIB
This MIB module is for the configuration of a Network Access Device (NAD) on the Cisco Network Admission Control (NAC) system.
CISCO-NAT-EXT-MIB
This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics.
CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
Cisco NBAR Protocol Discovery MIB NBAR - Network Based Application Recognition is an intelligent classification engine that recognizes applications that are static (which use fixed TCP or UDP port numbers), and stateful (which dynamically assign TCP or UDP port numbers). Protocol Discovery - uses NBAR to show you the mix of applications currently running on the network. Key statistics are associated with each protocol. These statistics can be used to define traffic classes and QoS policies.
CISCO-NDE-MIB
The Netflow Data Export (NDE) MIB provides instrumentation for configuration and operation of the Netflow Data Export feature. A network flow is defined as an unidirectional sequence of packets between a given source and destination endpoints. Network flows are highly granular; flow endpoints are identified both by IP address as well as by transport layer application port numbers. NetFlow also utilizes the IP Protocol type, Type of Service (ToS) and the input interface identifier to uniquely identify flows. Netflow Data Export refers to the export of Netflow Data using UDP packets to Netflow Data Collector(s). A NetFlow Data Collector (NDC) captures, filters, aggregates, and stores the data from multiple NetFlow enabled devices. NDCs provide fast, scalable, and economical Netflow data.
CISCO-NETFLOW-MIB
The Netflow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics. It will enable medium to small size enterprises to take advantage of NetFlow technology over SNMP at a reduced infrastructure cost.
CISCO-NETINT-MIB
This MIB module is for Network Interrupt information on Cisco device.
CISCO-NETSYNC-MIB
The Synchronous Ethernet (SyncE) MIB is defined for monitoring network synchronization based on ITU-T G.781 clock selection. Synchronous Ethernet (SyncE) is a standard defined for delivering timing to the remote NEs through a Packet Network. SyncE is well defined by ITU-T which included G.8261, G.8262, G.8264 and G.781. It leverages the PHY layer of Ethernet to transmit frequency to the remote sites. Its functionality and accuracy mimics that of the SONET/SDH network because of its physical layer characteristic. In order to allow best clock source traceabiliy, correctly define the timing source and helps preventing timing loop, Synchronization Status Message is required for SyncE. This is similar to SONET/SDH. However, since SONET/SDH use 4 bits from the two S bytes in the SONET/SDH overhead frame for such message, Ethernet relies on a different channel called ESMC (Ethernet Synchronization Messaging Channel) which is based on IEEE 802.3 Organization Specific Slow Protocol.
CISCO-NETWORK-REGISTRAR-MIB
MIB for Cisco Network Registrar (CNR).
CISCO-NHRP-EXT-MIB
This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical events in the Next Hop Resolution Protocol, NHRP, as defined in RFC 2332. This module also contains information about Cisco proprietary enhancements to the protocol.
CISCO-NMS-APPL-HEALTH-MIB
This MIB defines Cisco NMS Application (cna) Health Status Notifications and the related objects. These notifications will be sent to the OSS/NMS to inform them about the NMS application status (started, stopped, failed, busy etc.) or any abnormal exit of applications.
CISCO-NOTIFICATION-CONTROL-MIB
This MIB provides network management support to regulate the transmission of notifications generated by a system providing networking services. The system could be generating several notifications pertaining to various events. Allowing every notification to be transmitted out may lead to the network being flooded with an excess of network management traffic. Hence it is required to regulate the generation and transmission of notifications.
CISCO-NPORT-VIRTUALIZATION-MIB
The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Architecture. N_Port virtualization reduces the number of Fibre Channel domain IDs in SANs. Switches operating in the NPV mode do not join a fabric; rather, they pass traffic between NPV core switch links and end-devices, which eliminates the domain IDs for these edge switches.
CISCO-NS-MIB
The MIB module for the management of the Cisco Name Server which realizes the FC-GS3 requirements for Name Server (NS).
CISCO-NTP-MIB
This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Management of the NTP with SNMP# TR No. 98-09 authored by A.S. Sethi and Dave Mills in the University of Delaware.
CISCO-OAM-MIB
A MIB module for invoking OAM loopback Ping on ATM connections.
CISCO-OBMI-MIB
The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is capable of running on various low-speed to high-speed satellite telemetry busses, such as the m500 bus. OBMI is similar to SNMP in principle and function, in that it allows 'getting' data from or 'setting' configurations in a device, however, OBMI is functional regardless of the software state of the device. It must be so, because OBMI is the primary control mechanism for a device operating in the harsh environment of space. OBMI transports command messages that originate from the ground to a device in space and transports telemetry messages that originate from that device in space to the ground.
CISCO-OPTICAL-IF-CROSS-CONNECT-MIB
This MIB module is used to create and monitor cross-connects (horizontal relationships) between peer interfaces on the same network element. Vertical relationships (e.g. between lambdas and the optical fiber in which the lambdas are carried) are represented in the ifStackTable from the IF-MIB. This MIB can be used to model various types of cross-connects between peer interfaces, including time-division (e.g. SDH/SONET, PDH), wavelength (lambda), and spatial switching (e.g. incoming port or fiber to outgoing port or fiber). This MIB does not apply to cross-connects between packet flows (e.g. packets in the same forwarding equivalence class at a MPLS-capable switch or router) or cell flows (e.g. ATM Virtual Path connections or ATM Virtual Channel connections), since there are scalability issues in modeling each packet flow or cell flow as a logical interface. The switching element performing the cross-connect function can be electrical (e.g. SDH/SONET switch) or optical (e.g. passive optical add/drop multiplexer) Cross-connects can be created through provisioning, automatically by the network element, or dynamically by using control protocols (e.g. GMPLS). The cross-connect model includes support for pairs of interfaces used to protect each other (e.g. SONET 1+1 Automatic Protection Switching). Cross-connects to protection interfaces may be shown in this MIB module.
CISCO-OPTICAL-IF-EXTN-MIB
A MIB module containing extensions to the IF-MIB for optical interfaces
CISCO-OPTICAL-MONITOR-MIB
This MIB module defines objects to monitor optical characteristics and set corresponding thresholds on the optical interfaces in a network element.
CISCO-OPTICAL-MONITORING-MIB
This MIB module is used to monitor optical parameters of a network element.This MIB deals with the operating parameters of the optical layer. The optical layer is a term that defines all the devices/systems that deal with the conversion of data in it's electrical form to optical form, transmission of the optical data, reception, and finally re-conversion to electrical signals.
CISCO-OPTICAL-PATCH-MIB
This MIB module is used to configure and monitor the network element view of optical patches between two ports or fibers on the same network element. It is up to the user to keep the provisioned information that is reflected in this MIB module in sync with the actual patches present between ports or fibers on the network element. Provisioning of a patch does not cause a patch to be inserted; it only informs the network element that a patch has been, or is soon to be, added or removed.
CISCO-OSCP-MIB
The MIB module for managing the Cisco Optical Supervisory Channel Protocol (OSCP). The OSCP is used to determine and maintain wavelength connectivity with remote nodes. OSCP includes support for bundles of wavelengths to a common remote node, including dynamic selection of the message channel on one wavelength to carry control and management traffic for the entire wavelength bundle.
CISCO-OSPF-MIB
An extension to the MIB module defined in RFC 1850 for managing OSPF implimentation. Most of the MIB definitions are based on the IETF draft < draft-ietf-ospf-mib-update-05.txt > . Support for OSPF Sham link is also added
CISCO-OSPF-TRAP-MIB
This MIB module describes new/modified notification objects/events, which are defined in the latest version for OSPF MIB IETF draft draftietf-ospf-mib-update-05.txt. Support for OSPF Sham link is also added
CISCO-OTN-IF-MIB
This MIB module defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performance statistics objects for protocol specific error counters in DWDM optical devices. Performance monitoring (PM) parameters are used by service providers to gather, store, set thresholds for and report performance data for early detection of problems. Thresholds are used to set error levels for each PM parameter. During the accumulation cycle, if the current value of a performance monitoring parameter reaches or exceeds its corresponding threshold value, a threshold crossing alarm (TCA) is generated. The TCAs provide early detection of performance degradation.
CISCO-OUTAGE-MONITOR-MIB
This MIB module describes, stores, and reports outage related information generated by individual hardware and software components comprising a router. They includes physical interfaces, logical interfaces, physical entities such as chassis, slots, modules, ports, power supplies, and fan, software processes running on each card, and logical entity, which can be defined by outage monitoring program, which are IOS software for each LC and RP, router device, and CPU utilization. The outage related information comprises entity or interface up and down, process start and abnormal or normal termination, unusually high CPU utilization caused, for example, by Denial of Service (DoS) attack, etc. The outage related event can be collected by means of Cisco's fault manager, Cisco's event manager, and syslog messages, etc.
CISCO-P2P-IF-MIB
The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point network interfaces with the encapsulations of PPP (Point to Point Protocol), HDLC (High Level Data Link Control) or cHDLC (CIsco extension to High Level Data Link Control) framing.
CISCO-PACKET-CAPTURE-MIB
The MIB module for the management of packet capture feature.
CISCO-PAE-MIB
Cisco Port Access Entity (PAE) module for managing IEEE Std 802.1x. This MIB provides Port Access Entity information that are either excluded by IEEE8021-PAE-MIB or specific to Cisco products.
CISCO-PAGP-MIB
The MIB module for configuration of Fast Etherchannel and the operation of the Port Aggregation Protocol (PAgP). These features allow two or more physical interfaces to be aggregated together to form a single agport. This agport behaves like a single interface with improved bandwidth and/or availability over each of its component physical interfaces. You can monitor interfaces, agports, and related statistics through the ifStackTable and ifTable entries.
CISCO-PIM-MIB
This MIB module defines the cisco specific variables for Protocol Independent Multicast (PIM) management. These definitions are an extension of those defined in the IETF PIM MIB (RFC 2934).
CISCO-PING-MIB
Modified description of ciscoPingAddress object.
CISCO-PKI-PARTICIPATION-MIB
A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities in the form of X509 certificates. The device uses these certificates (called identity certificates) to authenticate itself to various clients communicating with the device using these protocols and also to provide other protection for the communication like confidentiality, integrity and non-repudiation. In addition, the device may need to authenticate the clients which involves, among other things, verifying the certificates presented by the clients (peer certificates) during the protocol exchanges. The certificate verification, in turn, involves the certificate revocation status checking and the certificate signature verification. This MIB applies to the public key infrastructure (PKI) participation feature which enables a networking device to participate in one or more PKI services (also called Certificate Authorities) enabling it to obtain one or more X509 identity certificates for its own use as well as to verify peer certificates. This MIB organizes the various certificates, key-pairs and Certificate Authority related information into the tables: the trustpoint table for certificate and CA information and a key-pair table for the key-pair information for each type of key-pair such as RSA, DSA etc. An entry in the trustpoint table corresponds to a trusted CA for obtaining an identity certificate from and also for verifying the peer certificates issued by that CA. The entry contains information about the CA certificate, the identity certificate - if obtained - from the CA, the corresponding key-pair from a key-pair table (for which the identity certificate was obtained) and the information needed for revocation checking of certitifates issued by the CA. For each type (RSA, DSA etc.) of key-pair supported by the device, a key-pair table is present and contains an entry for each key-pair of that type present in the device. This allows future expansion of the MIB to support additional key-pair types (currently only RSA key-pair is supported). As seen above, a key-pair entry from a key-pair table can be associated to an entry in the trustpoint table. A key- pair entry can be associated to multiple trustpoint table entries but not vice versa.
CISCO-PNNI-MIB
The MIB module for managing Cisco specific extensions to the ATM Forum PNNI MIB.
CISCO-POE-PD-MIB
This MIB is intended for devices powered by external power sources, in particular Power Over Ethernet (PoE or formerly called inline power), to provide power usage configuration and information for NMS. For example, PoE supplies DC power over standard Category 5 unshielded twisted-pair (UTP) cable. Instead of requiring wall power, powered devices such as IP telephones can utilize power provided from power source equipments. By using Cisco Discovery Protocol (CDP), powered devices can negotiated with power source equipment to obtain optimum power supply.
CISCO-POLICY-GROUP-MIB
The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified by IP addresses or other means. Members of a policy group will be subjected to the same policy. In this MIB, user can apply a policy to policy group(s) as well as configure and retrieve the group membership.
CISCO-POP-MGMT-MIB
Cisco Point Of Presence Management MIB to provide DSX1 and DSX0 facilities management and call summaries.
CISCO-PORT-CHANNEL-MIB
The MIB module for management of Port Channel ports. In addition to this MIB, CISCO-FC-FE-MIB and interface mib (rfc2863) will also contain entries for Port Channel ports.
CISCO-PORT-QOS-MIB
This MIB module is for the management of Cisco's per port rate-limiting and traffic shaping on L3 switch/Router Platform(s). Per-port rate-limiting is a traffic control method. A set of rate limits are applied to the traffic traversing an interface. Each rate limit has a configurable action that is taken when rate limiting criteria is met. Per-port traffic shaping is a traffic control method. The user can restrict the amount of traffic coming out of a physical port. Excess traffic is buffered within the router/switch to the extent possible. A class represents a class of traffic. It is defined via the specification of the packet matching criteria that identifies packets that are to belong to the class. Class-default: In addition to user defined classes, a pre-existing class named 'class-default' exists to represent all packets that do not match any of the user defined classes. This class-default exists so that policies can be defined for this group of packets that do not match any user defined classes. Actions are individual policies (e.g.: policing) that can be applied to a traffic class. A policy represents a set of actions that are to be applied to a set of traffic classes. The policy is associated with a target (like a port) and the direction of traffic on that target to which the policy is to be applied. A hierarchical policy is one in which an entire policy is directly assigned to a class of traffic. Thus, a hierarchical policy is a nested policy that contains a set of the pair of a child-policy and the traffic-class to which it is applied. DSCP (Differentiated Services Code Point) is the six most significant bits of the ToS field in a IP packet header. CoS (Class of Service) is the three bits in the layer 2 header that indicates user priority value assigned to this packet. This MIB module also provides per port QoS statistics.
CISCO-PORT-SECURITY-MIB
The MIB module for managing Cisco Port Security.
CISCO-PORT-STORM-CONTROL-MIB
The MIB module for managing Cisco Port Storm Control.
CISCO-PORT-TRACK-MIB
A MIB to configure the Port-Track feature. When a link goes down, all the services which depend on the link are notified of the outage. The loss of this link may be an indirect failure to the end devices attached to the switch. The concept behind the Port-Track feature is to create a direct failure on the ports connected to end devices on event of such indirect failures. One more ports can be 'tracked' in terms of their operational status. The cptPortTrackTable lets the user associate which port(s) need to be tracked to the ports that will be tracking them. cptPortForceShutTable, lets the user configure the forced-shut mode of the linked-port.
CISCO-POWER-ETHERNET-EXT-MIB
A MIB module for extending the POWER-ETHERNET-MIB (RFC3621) to add objects which provide additional management information about Power Sourcing Equipment (PSE) not available in POWER-ETHERNET-MIB.
CISCO-PPPOE-MIB
Cisco PPPoE sessions management MIB Module.
CISCO-PREFERRED-PATH-MIB
The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters. Preferred path provides a method of routing traffic over the selected paths, not necessarily the preferred shortest path as chosen by routing protocols such as FSPF. This kind of control allows users to choose shortest paths based on characteristics, such as frames received on a selected interface or frames with selected source FC-ID. This feature allows users to ensure paths seperation between switches for different traffic between a host and a target.
CISCO-PRIVATE-VLAN-MIB
The MIB module to support Private VLAN feature on Cisco's switching devices.
CISCO-PROCESS-MIB
The MIB module to describe active system processes. Virtual Machine refers to those OS which can run the code or process of a different executional model OS. Virtual Process assume the executional model of a OS which is different from Native OS. Virtual Processes are also referred as Tasks. Thread is a sequence of instructions to be executed within a program. Thread which adhere to POSIX standard is referred as a POSIX thread.
CISCO-PROP-ATM-IF-MIB
This MIB is designed for Propietary ATM (propAtm) interfaces. The propAtm interfaces are identified in the ifTable entries with ifType 197 (as defined in IANAifType-MIB). This interface is a switch virtual interface which does not have any physical connector(jack).
CISCO-PROXY-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing Proxy management information.
CISCO-PSA-MICROCODE-MIB
Cisco PSA Microcode MIB - Overview The PSA is the Packet Switching ASIC used in module like engine 2(E2) line cards in GSR for IP and MPLS packets forwarding. The PSA performs IP and MPLS packet forwarding at 4 Mpps. The list of features supported by the PSA includes (but is not limited to): - Input and Output ACLs - Frame Relay Switching - PIRC - MPLS VPN - BGP policy accounting - IP packet coloring - Sampled Net flow - ATM over MPLS. - Source MAC Accounting. - Unicast RPF Note that all the features are not supported simultaneously on a module. Each microcode bundle/set can support one or a limited number of the features listed above. Each feature has a priority. When a feature (ACL, Sampled NetFlow) is enabled through the CLI, the higher priority feature will take precedence over the lower priority feature. The microcode for the lower priority is removed and cleaned up. The higher priority microcode will be loaded. Later, if the higher priority feature is removed, the lower priority microcode will be loaded again. This MIB contains information about the microcode bundles on modules like E2 Line Cards(LC) in GSR. Since microcode reload is a service interrupting event, this MIB also defines a notification to inform management stations that such an event has taken place.
CISCO-PSD-CLIENT-MIB
This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for configuring data-store(PSD client) feature on GGSN and monitoring the state of the PSD server(up/down/full). The Cisco Persistent Storage Device(PSD) is an extension to existing storage on the Cisco Content Services Gateway(CSG). The GGSN currently allows sending of the CDRs to an active CG, while allowing up to two standby CG's to be configured. When all the configured CG's become unavailable, the CDRs get stored at the GGSN and start using up GGSN resources such as memory. As the amount of memory is limited on GGSN and failure of GGSN shall lead to losing these stored CDRs. Using PSD as temporary storage, shall avoid losses due to these problems. When all the configured CG's are unavailable, GGSN needs to backup the live closed CDR's to a PSD. When any of the CG's shall become available, GGSN shall retrieve the stored CDR's automatically from the PSD and forwards them to the active CG. PSD supports the charging protocol(GTP'), version 0 with a few private extensions, which is used to facilitate the required functionality via UDP.
CISCO-PSM-MIB
The MIB module for the management of the Port Security Manager (PSM). The PSM consists of 2 aspects: Port binding and Fabric binding. Port binding is concerned with the security of switch ports and Fabric binding with the security of the SAN fabric as a whole.
CISCO-PTOPO-EXTN-MIB
This MIB module contains extensions to the PTOPO-MIB that provide support to distinguish between bidirectional and unidirectional physical topology connections. It also introduces a table that allows configuration of dynamic learning of the physical topology through the Cisco Discovery Protocol (CDP).
CISCO-PTP-MIB
The MIB module for PTPv2 (IEEE1588 - 2008) Overview of PTPv2 (IEEE 1588-2008) This IEEE standard defines a protocol enabling precise synchronization of clocks in measurement and control systems implemented with packet-based networks, the IEEE Standard PTPv2 1588 (2008). This MIB does not address the standard IEEE 1588 (2002). The protocol is applicable to network elements communicating using IP. The protocol enables heterogeneous systems that include clocks of various inherent precision, resolution, and stability to synchronize to a grandmaster clock. The protocol supports system-wide synchronization accuracy in the sub-microsecond range with minimal network and local clock computing resources. The standard uses UDP/IP. It includes formal mechanisms for message extensions, higher sampling rates, correction for asymmetry, a clock type to reduce error accumulation in large topologies, and specifications on how to incorporate the resulting additional data into the synchronization protocol. The standard defines conformance and management capability also. MIB description This MIB is to support the Precision Timing Protocol (PTP) feature of Cisco System devices.
CISCO-QINQ-VLAN-MIB
This MIB defines configuration and monitoring capabilities relating to 802.1QinQ interfaces. QinQ interfaces are capable of terminating QinQ traffic and translating QinQ tags.
CISCO-QLLC01-MIB
This is the MIB module for objects used to manage the QLLC protocol.
CISCO-QOS-PIB-MIB
The Cisco QOS Policy PIB for provisioning QOS policy
CISCO-QOS-POLICY-CONFIG-MIB
This MIB module defines managed objects that support the policy source configuration of Quality of Service (QoS) on the device.
CISCO-QUEUE-MIB
This is the MIB module for objects used to manage interface queuing in Cisco devices.
CISCO-RADIUS-MIB
MIB module for monitoring and configuring authentication and logging services using RADIUS (Remote Authentication Dial In User Service) related objects. The RADIUS (RFC2865) framework consists of clients and servers. A client is responsible for passing user information to designated RADIUS servers, and then acting on the response which is returned. RADIUS server is responsible for receiving user connection requests, authenticating the user, and then returning all configuration information necessary for the client to deliver service to the user. This MIB module also contains objects for enabling/disabling telnet and SSH (Secure Shell) authentication. Secure Shell is program which is used to log into another machine over a secured session.
CISCO-REMOTE-ACCESS-MONITOR-MIB
This is a MIB Module for monitoring the structures in Virtual Private Networks based remote access networks. The MIB seeks to create a common model of Remote Access across implementations of the service on layer 2 (PPTP, L2TP, L2F), layer 3 (IPsec) and layer 4 (SSL) virtual private networks. The MIB defines counters and objects of interest to performance/fault monitoring in a way which is independent of the technology of the remote access implementation.
CISCO-REPEATER-MIB
CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB B
This MIB module defines objects required for managing Resilient Ethernet Protocol (REP). Resilient Ethernet Protocol (REP) is a Cisco proprietary protocol that provides an alternative to Spanning Tree Protocol (STP) to control network loops, handle link failures and improve convergence time. REP controls a group of ports connected in a segment; ensures that the segment does not create any bridging loops, and responds to link failures within the segment.
CISCO-RF-MIB
This MIB provides configuration control and status for the Redundancy Framework (RF) subsystem. RF provides a mechanism for logical redundancy of software functionality and is designed to support 1:1 redundancy on processor cards. RF is not intended to solve all redundancy schemes. Nor is RF designed to support redundant hardware, such as power supplies. Redundancy is concerned with the duplication of data elements and software functions to provide an alternative in case of failure. It is a key component to meeting 99.999% availability requirements for Class 5 carrier solutions. In the scope of this MIB definition, peer software elements are redundant and redundant software elements are peers.
CISCO-RF-SUPPLEMENTAL-MIB
This MIB was designed to complement the CISCO-RF-MIB by providing additional optional status and configuration control for redundant CPU platforms. However, the MIB should also be applicable to redundant platforms which don't use the RF Redundancy Framework software since it makes no direct references to any CISCO-RF-MIB objects or textual conventions and no direct reference to any RF states, RF events or internal information.
CISCO-RHINO-MIB
CISCO-RMON-CONFIG-MIB
This module defines configuration extensions for some of the IETF RMON MIBs. The following terms are used throughout this MIB: A SPAN session is an association of one or more destination(s) with a set of source(s), along with other parameters, to specify the network traffic to be monitored. Each SPAN session is denoted by an unique number. The term 'remote SPAN', also called 'RSPAN', refers to the analysis of network traffic remotely, from destination port(s) for one or more source ports, distributed in one or more switches in a switched network, through a RSPAN VLAN.
CISCO-ROUTE-POLICIES-MIB
This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This module defines only this 'policy' OID space and doesn't define any other object.
CISCO-RPMS-MIB
This MIB contains objects pertinent to a Resource Policy Management System (RPMS) server. RPMS is a key component of Cisco Any Service Any Port (ASAP) solution and provides the ability to dynamically share resources across network access servers (NAS). RPMS enables enforcement of Service Level Agreements(SLA) between wholesale providers and their customers. Such SLA enforcement is done at call pre-authentication stage. An SLA is conceptually a set of clauses (limits) that dictate how voice, dial and/or virtual private data network (VPDN) services will be provided by the wholesaler.
CISCO-RSCN-MIB
The MIB module for the management of the Fibre Channel's Registered State Change Notification (RSCN) functionality, which is specified by FC-FLA and FC-FS.
CISCO-RSRB-MIB
This is the MIB module for objects used to manage RSRB. Overview of remote source-route bridging (RSRB) management and MIB MIB description
CISCO-RTP-METRICS-MIB
This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver Report packet [RFC3550].
CISCO-RTTMON-ICMP-MIB
An extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics such as RTT (Round Trip Time), Jitter, packet loss, one-way latency by sending ICMP TIMESTAMP stream to the destination devices.
CISCO-RTTMON-IP-EXT-MIB
This MIB contains extensions to tables in CISCO-RTTMON-MIB to support IP-layer extensions, specifically IPv6 addresses and other information related to IPv6 and other IP information
CISCO-RTTMON-MIB
This module defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols.
CISCO-RTTMON-RTP-MIB
An extension to the CISCO-RTTMON-MIB for Cisco IP SLA RTP operation, Real-Time Transport Protocol(RFC 1889). This operation provides capability to measure voice quality metrics such as RTT (Round Trip Time), Jitter, MOS (Mean Opinion Score) scores by setting up RTP stream between two routers. In voice communications, particularly Internet telephony, MOS provides a numerical measure of the quality of human speech at the destination end of the circuit.
CISCO-SAA-APM-MIB
A MIB for controlling SAA APM. APM provides a framework for running scripts, written in TCL language, which help emulate the data flows of an application. Through this emulation, the performance of an application across a network can be computed. The parameters required to perform an operation are defined in a 'config file' as defined by saaApmCtrlScriptCfgURL. This MIB has three OBJECT group. 'saaApmAppl' group contains global objects while 'saaApmCtrl' group contains the objects to control the APM operation. Controlling includes creation and deletion of the operation and initiating a result-transfer for the operation. 'saaApmOper' group contains objects to get the statistics of the operation.
CISCO-SAN-BASE-SVC-MIB
Common MIB module to manage services in Storage Area Network (SAN). Service is deployed on service nodes on multiple switches forming a cluster. Nodes in the same cluster pick up the workload of a failed node to provide fault tolerance. An example of service that can be deployed is IO Acceleration (IOA) service.
CISCO-SANTAP-MIB
MIB module to provide information about the SanTap service configuration. SanTap is a fibre channel switch based capability that provides a reliable copy of the data flowing between a set of one or more initiators and a set of one or more targets connected to the fabric. Adminstrator must configure the switch to create the Control Virtual Target (CVT) for the SanTap service. CVTs are used to implement the control path which process all SanTap service requests sent out by an appliance. Prior to requesting for SanTap service the appliance contacts the CVT, specifies the initiator and the target for replicating the data flowing between them. This MIB provides an interface to configure the CVT for the SanTap service on the fibre channel switch modules.
CISCO-SCAS-BB-MIB
Main SNMP MIB for Cisco SCAS BB application which runs over Service Control Engine devices.
CISCO-SCSI-FLOW-MIB B
A SCSI Flow is described as a SCSI Initiator SCSI Target combination. This MIB is used to configure and monitor SCSI Flows.
CISCO-SCSI-MIB
CISCO-SCTP-MIB
The MIB module for managing SCTP implementation.
CISCO-SDLLC-MIB
This is the MIB module for objects used to manage SDLLC.
CISCO-SDSL-LINE-MIB
This MIB module describes all variations of the symmetric DSL line interfaces. The structure of this module resembles and maintains consistency with the ADSL-LINE-MIB, ADSL-DMT-LINE-MIB, CISCO-ADSL-DMT-LINE-MIB, and CISCO-ADSL-CAP-LINE-MIB. Observe that the tables in this module do not necessarily extend the tables defined by the these mibs. Currently, only those tables that contain configuration information extend the profile tables defined by the above modules. This allows the management client to define DSL configuration profiles that apply across all DSL modems, independent of the technology being utilized by the modem.
CISCO-SECURE-SHELL-MIB
MIB module for displaying and configuring accounting and Secure Shell (SSH) related features in a device. SSH is a program to log into another computer over a network, to execute commands in a remote machine and to move files from one machine to another. It provides strong authentication and secure communications over unsecure channels.
CISCO-SELECTIVE-VRF-DOWNLOAD-MIB
This MIB module defines objects describing selective VRF download. The selective VRF download feature makes a best effort to download only those prefixes and labels to a physical entity required to forward traffic through the physical entity. The feature accomplishes this by characterizing roles for physical entities baed on their configuration.
CISCO-SERVICE-CONTROL-ATTACK-MIB
This MIB provides data related to different types of attacks detected by a service control entity. A service control entity is a network device which monitors and controls traffic. The service control entity is used as a platform for different service control applications which may perform monitoring operations beyond packet counting and delve deeper into the contents of network traffic. It provides programmable stateful inspection of bidirectional traffic flows and maps these flows with user/subscriber ownership. An attack is a malicious network activity with certain traffic characteristics and which is targeted on a certain network entity. An attack can be identified by its type, direction, source address, destination address and ports. Once an attack is detected, an attack filter is activated based on the type of the attack and corresponding actions are taken in the monitored network - this is referred to as attack start. For example the attack filter can drop the attacking traffic. When the attack detector identifies that the attack characteristics are no longer exist, it ends the mitigation action - what is referred to as attack end. The attack mitigation action is also referred to as attack filtering in this MIB. The time duration of attack filtering between attack start to attack end along with the direction (upstream, downstream) is also maintained by the service control entity. Attack filtering can be applied from the subscriber side to the network side, in the upstream direction. The downstream attack filtering is done from the network side to the subscriber side. This MIB also defines notifications generated by the service control entity when an attack is detected on a monitored network.
CISCO-SERVICE-CONTROL-LINK-MIB
This MIB module provides information about the status and configuration of links used by service control entities. The link on a service control entity is a contained entity that joins subscriber side port(s) to network side port(s).
CISCO-SERVICE-CONTROL-RDR-MIB
This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a service control entity. The Raw Data Record (RDR) formatter is a component implemented by the service control entity that gathers raw data records produced by the entity and delivers them to external entities as reports. The external entities are called RDR destinations or RDR collectors. The RDR formatter can be configured to send reports to one or multiple destinations. RDR formatter can group RDRs into potentially four categories. RDR mapping to the categories is done by the client application or the user and reflects different logical destinations or purposes. For example the application may map Quota related RDRs to category 1, and Transaction related RDRs to category 2. The user can configure these categories to different destinations and assign them with different priorities. Each category has a separate queue for forwarding the RDRs and has seperate counters for gathering of statistics (sent, dropped, queued etc.). An RDR can belong to any one of the category as chosen by the user or client application. The RDR formatter supports multiple destinations identified by IP address and a port number. Each destination is assigned with a priority for each of the categories. Priority is a number in the range of 1-100, with 100 being the highest priority. The priorities are effective only when the formatter is in forwarding mode 'Redundancy' and are configured during destination configuration (while assigning the destination with categories). For example we have destination A configured with category 1 which is configured with priority 100, destination B configured with category 1 and priority 80 and destination C with category 1 and priority 90. When in redundancy mode the formatter will set the active destination for a category to be the destination with the highest priority. For category 1 the active destination will be A. If destination A goes down then the next destination selected by the formatter as active is destination C.
CISCO-SERVICE-CONTROL-SUBSCRIBERS-MIB
This MIB provides global and specific information on subscribers managed by a service control entity, which is a network element that monitors network traffic between network subscribers based on user configured policies. The network subscribers are the end users of the network with a unique network address for each subscriber. A specific subscriber is identified by this MIB by its subscriber name which is assured to be unique, this id is used to retrieve this specific subscriber's information.
CISCO-SERVICE-CONTROL-TP-STATS-MIB
This MIB provides information and statistics on the traffic processor(s) of a service control entity, which is a network element that monitors network traffic between network subscribers based on user configured policies. A service control entity uses traffic processor(s) for packet processing and flow handling in the host network. The traffic processor(s) data obtained from this MIB may also reflect the general load in the system.
CISCO-SERVICE-CONTROLLER-MIB
This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a network device which monitors and controls traffic. The service control enitity is used as a platform for different service control applications which may perform monitoring operations beyond packet counting and delve deeper into the contents of network traffic, such as deep packet inspection. It provides programmable stateful inspection of bidirectional traffic flows, maps these flows to users or subscribers, and can control traffic flow according to different attributes. A service control entity traffic controller can act as a rather simple policer or implement more complicated logic in controlling traffic, up to actual applicative attributes of the traffic itself. The global service controller is a controller component implemented by the service control entity, which acts as a rather simple policer for traffic transiting through the service control entity. A global service controller may be configured per service control entity interface with a configurable bandwidth limitation. The controller is responsible for the enforcement of the bandwith limitation configured in the service control entity.
CISCO-SESS-BORDER-CTRLR-CALL-STATS-MIB
The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics are mainly of two types - Call statistics and Media statistics. The calls can further be categorized as SIP calls and H.248 calls.
CISCO-SESS-BORDER-CTRLR-EVENT-MIB
The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application and used to send these notifications to SNMP manager application. Each of these event/notification is explained in detail in the MIB file. The SBC service is implemented on a service card on CISCO routers. SBC application offer functionalities like firewall/NAT traversal, media bridging, policy-based call routing, signaling protocol inter-working, call billing and some degree of Call Admission Control. SBC looks to play an essential role in full-scale commercial deployment of VoIP and integration into the existing PSTN. The Session Border Controller (SBC) enables direct IP-to-IP interconnect between multiple administrative domains for session-based services providing protocol inter-working, security, and admission control and management. The SBC is a voice over IP (VoIP) device that sits on the border of a network and controls call admission to that network. The primary purpose of an SBC is to protect the interior of the network from excessive call load and malicious traffic. Additional functions provided by the SBC include media bridging and billing services.
CISCO-SESS-BORDER-CTRLR-STATS-MIB
The main purpose of this MIB is to define the statistics information for Session Border Controller application.
CISCO-SEU-MITIGATION-MIB
This MIB reports the status of non-automatic and automatic, rate-adaptive Single Event Upset (SEU) mitigation algorithms and adjusts their parameters, as well as reports the effects of those mitigations on memories, caches, and registers. SEU mitigation allows Cisco IOS to run on radiation tolerant hardware deployed in a geosynchronous Earth orbit satellites for IP communications. One of the challenges in deploying equipment in such an environment is the impact that radiation has on digital circuits. A Single Event Upset (SEU) occurs when the hardware is exposed to energetic ions and protons in the space environment. The value stored in a bit of information can change when a large enough charge is deposited on the digital circuit. This leads to adverse effects in the operation of the software; in this case Cisco IOS. While steps have been taken to reduce the occurrence of SEUs through the use of radiation tolerant hardware, these steps do not eliminate the threat. A critical requirement in running IOS on such platforms is the utilization of SEU mitigation strategies to reduce the impact of such events on the operation of the Cisco device.
CISCO-SIBU-FLASH-MIB
The MIB module that provides a simple mechanism to support firmware upgrade on Cisco low end devices.
CISCO-SIBU-MANAGERS-MIB
The MIB module that provides a simple configuration of management interfaces on managed devices.
CISCO-SIBU-STACKABLE-DUAL-SPEED-HUB-MIB
The MIB module that extends the REPEATER-MIB to manage CISCO low end stackable repeater products. For the purpose of this mib, a hub is a repeater group and stack is collection of one or more hubs interconnected via stack bus connectors.
CISCO-SIP-CALLS-MIB
The Cisco Session Initiation Protocol (SIP) Calls MIB module is designed to provide protocol-specific information on SIP calls which are currently active. SIP is an application-layer signalling protocol for creating, modifying and terminating multimedia sessions with one or more participants. SIP is defined in RFC 3261 (June 2002). The endpoints in a SIP communication are called user agents. A user agent is an application which contains both a User Agent Client (UAC) and a User Agent Server (UAS). A UAC is an application that initiates a SIP request. A UAS is an application that contacts the user when a SIP request is received and that returns a response on behalf of the user. This MIB module provides information on SIP calls and the user agents initiating these calls. Also, it provides a way to manage media forking of SIP calls.
CISCO-SIP-UA-MIB
Cisco User Agent Session Initiation Protocol (SIP) MIB module. SIP is an application-layer signalling protocol for creating, modifying and terminating multimedia sessions with one or more participants. These sessions include Internet multimedia conferences and Internet telephone calls. SIP is defined in RFC 2543 (March 1999). This MIB is defined for the management of SIP User Agents (UAs). A User Agent is an application which contains both a User Agent Client (UAC) and a User Agent Server (UAS). A UAC is an application that initiates a SIP request. A UAS is an application that contacts the user when a SIP request is received and that returns a response on behalf of the user. The response accepts, rejects, or redirects the request. A SIP transaction occurs between a client and a server and comprises all messages from the first request sent from the client to the server up to a final (non-1xx) response sent from the server to the client.
CISCO-SLB-DFP-MIB
This MIB reports the congestion status of the real server. A server can be in congested state due to high memory consumption, high CPU utilization or high number of clients being served by it. Congestion can cause delay in server response time. DFP (Dynamic Feedback Protocol) weight values are used as a metric to monitor the congestion of the server.
CISCO-SLB-EXT-MIB
The extended MIB for managing Server Load Balancing Manager(s). This MIB extends the SLB management functionality in the CISCO-SLB-MIB. The Cisco Content Switching Module (CSM) product is the first SLB product to support this MIB. SLB: Server Load Balancing. Server load balancing provides for the balancing of packets and connections arriving at the SLB device across a number of other devices, such as real servers, firewalls, or caches. A system containing an SLB device typically exhibits higher performance, scalability, and reliability than any of the devices being load balanced. An SLB device determines how to handle incoming frames and connections according to the contents of incoming data and various configuration options. In determining how to handle incoming data, an SLB device may examine the data at any OSI layer, including Layer 7. This MIB includes instrumentation for the manager-side implementation of the Dynamic Feedback Protocol (DFP). A DFP manager uses the DFP protocol to communicate with DFP agents in order to obtain information about the current load and available capacity of devices.
CISCO-SLB-HEALTH-MON-MIB
An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides for the balancing of packets and connections arriving at the SLB device across a number of other devices, such as real servers, firewalls, or caches. A system containing an SLB device typically exhibits higher performance, scalability, and reliability than any of the devices being load balanced. An SLB device determines how to handle incoming frames and connections according to the contents of incoming data and various configuration options. In determining how to handle incoming data, an SLB device may examine the data at any OSI layer, including Layer 7. This MIB includes information on the health monitoring probes that can be used for monitoring the health of real servers. Health checking provides the ability of the content switch to detect if a server is available for load balancing. Health probes used for health checking allow testing various application level functionality. The active probes are sent at regular intervals and the lack of a response can lead to a specific server or and entire group of servers being declared as not available. Following probes are based on TCP: http, https, smtp, telnet, ftp, tcp, script, ldap, tacacs, sip, echo, finger. Following probes are based on UDP: tftp, udp, sip, echo,.
CISCO-SLB-MIB
The MIB for managing Server Load Balancing Manager(s), such as the Cisco IOS SLB product. This MIB includes instrumentation for the manager-side implementation of the Dynamic Feedback Protocol (DFP). A DFP uses the DFP protocol to communicate with DFP agents in order to obtain information about Servers. This MIB includes the objects required for implementing the load balancer management side of the Server/Application State Protocol (SASP). The load balancer is responsible for registering Members with a SASP-Agent. A Member is an entity that is defined on the load balancer to service Internet traffic. The responsibility of the Agent is to monitor the Members, and report a recommended weight to the load balancer. The weight is then used in load balancing decisions.
CISCO-SM-FILE-DOWNLOAD-MIB
The MIB module for downloading files to the Service Modules specifically designed for an architecture containing a controller card and a group of sub- ordinate cards or service modules (as in a Switch). These files could contain information for performing any specific operation on the modules. For example, they could contain information on statistics retrieval like, the statistics type, bucket interval etc. The format of these files is implementation dependent.
CISCO-SMART-INSTALL-MIB
This MIB module defines managed objects that facilitate the management of Smart Install feature. Smart Install is a plug-and-play image and configuration management feature which enables zero-touch deployment of Cisco network devices in an enterprise branch network.
CISCO-SME-MIB
MIB module to manage Storage Media Encryption (SME) service. SME is an encryption service provided by an encryption node residing on a linecard in a storage device. It receives clear-text data from host, encrypts it, then sends it to be written to tape or disk. It does the reverse in the opposite direction so the service is completely transparent to the host. The purpose of this service is to enhance data security in case the tape or disk is lost or stolen. As with any important service, user requires that it provides some level of fault tolerant in a graceful manner. SME provides this by allowing encryption nodes to be grouped into cluster. Nodes in the same cluster immediately pick up the work of a failed node so user does not see service disruption.
CISCO-SMI
The Structure of Management Information for the Cisco enterprise.
CISCO-SNA-LLC-MIB
This is the MIB module for objects used to manage LLC devices.
CISCO-SNAPSHOT-MIB
Specify a correct (non-negative) range for an index object. Also, correct typo which caused syntax conflict.
CISCO-SNMP-NOTIFICATION-EXT-MIB
This MIB extends the functionality provided by SNMP-NOTIFICATION-MIB. This MIB provides for the aging of the notification filters specified in the SNMP-NOTIFICATION-MIB.
CISCO-SNMP-TARGET-EXT-MIB
This MIB is an extension of the SNMP-TARGET-MIB specified in RFC3413. This MIB module contains Cisco-defined extension to the snmpTargetAddrTable to represent information required for IPv6 Address. When Target has Link local or Multicast IPv6 address, the information of the interface on which the notification has to be sent is required. This additional information is provided by this extension MIB. This module also contains definition for set of new variable to hold the address of the host that had sent an unauthentic SNMP message to agent.
CISCO-SNMP-VACM-EXT-MIB
The management information definitions to extend the View-based Access Control Model (RFC3415) for SNMP. This MIB extends the 'SNMP-VIEW-BASED-ACM-MIB' to allow each combination of a 'securityModel' and a 'securityName' to be mapped into additional groupNames. The groups identified by these mappings are in addition to those identified by 'vacmGroupName' of the 'vacmSecurityToGroupTable'.
CISCO-SONET-MIB
The MIB module to describe SONET/SDH interfaces objects. This is an extension to the standard SONET MIB(RFC 2558).
CISCO-SP-MIB
The MIB for managing the SS7 Signalling Point (SP) implemented in the Cisco IOS SS7 offload product. The relevant ITU documents describing this technology is the ITU Q series, including ITU Q.700: Introduction to CCITT Signalling System No. 7 and ITU Q.701 Functional description of the message transfer part (MTP) of Signalling System No. 7. This MIB models the SP as follows: The SP is associated with one or more point codes. Each pointcode is associated with: an ss7 variant, timers, and linksets. Linksets contain: destination point code linkset byte/packet statistics, accounting information per DPC and OPC violation accounting information per DPC and OPC links, reference to incoming and outgoing ACL reference to a routing table for each SS7 packet type Links contain: timers, and byte/packet statistics.
CISCO-SRP-MIB
The MIB module to describe objects for Spatial Reuse Protocol (SRP) interface layer.
CISCO-SRST-MIB
This MIB allows management of Cisco Survivable Remote Site Telephony (SRST) feature in Cisco IOS. SRST is an optional software feature that provides Cisco CallManager with fallback support for Cisco IP phones attached to a Cisco router on a local network. The CISCO-CCME-MIB provides management of Cisco CallManager Express (CCME) feature in Cisco IOS. CCME is an optional software feature that enables Cisco routers to deliver IP telephony services for small office environment. Ephone, ephoneDN, button association tables are common to both CCME and SRST MIBs and are defined in CISCO-CCME-MIB. Ephone specific notifications which are common to CCME and SRST are also defined in CISCO-CCME-MIB.
CISCO-SSG-MIB
The MIB Module manages Service Selection Gateway(SSG) devices. Service Selection Gateway(SSG) is a switching solution for service providers who offer intranet,extranet, and Internet connections to subscribers using broadband access technology such as digital subscriber lines, cable modems, or wireless to allow simultaneous access to network services.
CISCO-SSL-PROXY-MIB
This MIB module is for managing a Secure Socket Layer (SSL) Proxy device which terminates and accelarates SSL and Transport Layer Security (TLS) transactions. The proxy device can act as a SSL server or a SSL client depending on the configuration and the application. In one application, the device acts as a proxy SSL server. It terminates SSL handshakes and TCP connections initiated by SSL clients. The device is configured with a key and a certificate bearing the identity of the SSL server. The device uses this identity to establish the SSL session on behalf of the server, offloading the key establishment and data encryption and decryption work. After the SSL session has been successfully established between the client and the proxy device, the device starts to receive and decrypt the encrypted data sent from the client and forward to the server. The device forwards the clear data to the server on a backend connection. Clear data sent from the server is encrypted by the proxy device before it is forwarded to the SSL client. Optionally, the proxy device is configured to reencrypt the decrypted data sent from the client to the server. The proxy device acts as a SSL client to initiate a SSL session to the server. The decrypted data is encrypted within this SSL session to be forwarded to the server. The encrypted data sent from the server to the device is decrypted and then reencrypted before it is forwarded to the client. In another application, the proxy device forwards data generated by one or more sources to the destination via a SSL session. The proxy device acts as a SSL client and intiates a SSL session to the next hop device. When data is received from the source, the proxy device forwards the data to the next hop using the SSL session. The next hop can continue to forward the data if it is not the destination. The proxy device supports a number of proxy services. Each proxy service defines the role of the proxy device, whether it acts as a SSL server or a SSL client. The rest of the configuration include cryptographic and protocol parameters. This MIB is used for monitoring the configuration, statuses and statistics of the proxy services and the protocols including TCP, SSL and TLS.
CISCO-SSM-PROV-MIB
This MIB is used to provision features on a Data Path Processor (DPP) of a Storage Service Module (SSM). A DPP is assigned to a contiguous set of ports. Each DPP can run one or more features independent of other DPPs on the module. Since the concept of a DPP is transparent to the network manager, ranges of ports are used to configure different features. A start and an end port are specified to identify a DPP and provision a feature.
CISCO-STACK-MIB
This MIB provides configuration and runtime status for chassis, modules, ports, etc. on the Catalyst systems
CISCO-STACKMAKER-MIB
The MIB module for Cisco Systems' StackMaker
CISCO-STACKWISE-MIB
This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technology. The StackWise technology provides a method for collectively utilizing a stack of switches to create a single switching unit. The data stack is used for switching data packets and, in power stack, switches are connected by special stack power cables to share power. Moreover, stackwise is the concept for combining multiple systems to give an impression of a single system so that is why both power stack and data stack are supported by single MIB.
CISCO-STP-EXTENSIONS-MIB
The MIB module for managing Cisco extensions to the 802.1D Spanning Tree Protocol (STP).
CISCO-SVC-INTERFACE-MIB
MIB module for displaying and configuring SVC (SAN Volume Controller) related features in the Storage Area Network (SAN) switches. SVC is the SAN Volume Controller that implements the specialized virtualization and caching features for storage attached to a SAN.
CISCO-SVI-AUTOSTATE-MIB
The MIB module is for configuration of the switch virtual interface (SVI) autostate feature. Autostate feature is a mechanism to calculate the state of a SVI dynamically when some condition occurs such as a failure of a participating interface in that SVI.
CISCO-SWITCH-CGMP-MIB
Switch-side Cisco Group Management Protocol MIB for Layer 2 Switch devices.
CISCO-SWITCH-ENGINE-MIB
This MIB module defines management objects for Cisco Layer 2/3 switches. These devices may either have a single (central) switching engine entity or may consist of multiple (distributed) switching engine entities which are inter-connected via a common 'switching fabric'. In the central switching engine model, all the physical ports in the system are handled by the only switching engine in the system. In the distributed switching model, each switching engine will handle a set of 'local' physical ports and when necessary, packets are also switched between switching engines over the switching fabric. Cisco L2/L3 switching devices use regular routers to assist them in learning packet 'flows' by observing how a router routes a candidate flow. A flow is some combination of source network address, destination network address and the transport port numbers, as applicable. Once a flow is established (learned), all traffic belonging to that flow will be switched at Layer 3 by the switch engine, effectively bypassing the router, until the flow has been 'aged' out. Most Cisco L2/L3 switching devices employ built-in (internal) router module(s) for integrating Layer 3 switching with Layer 2 forwarding. However, they can also learn 'flows' through other physically-separate (external) Cisco routers that are connected to the switch-engine through the network.
CISCO-SWITCH-HARDWARE-CAPACITY-MIB
This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information covers the following but not limited to features: forwarding, rate-limiter ...
CISCO-SWITCH-MULTICAST-MIB
This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices.
CISCO-SWITCH-NETFLOW-MIB
This MIB module defines management objects for the Netflow features on Cisco Layer 2 and Layer 3 devices.
CISCO-SWITCH-QOS-MIB
This MIB module extends the CISCO-CLASS-BASED-QOS-MIB by defining configuration and statistics information specific to the quality of service (QoS) features of Layer2/3 switch functionality implemented in Cisco devices. It is applicable to a device which is fully within a single QoS domain, although one or more boundaries with other QoS domains can be immediately adjacent to this device.
CISCO-SWITCH-RATE-LIMITER-MIB
This MIB module defines management objects for the Switch Rate Limiter features on Cisco Layer 2 and Layer 3 devices. Rate limits prevents redirected control packets for egress exceptions from overwhelming the supervisor module on a device.
CISCO-SWITCH-STATS-MIB
The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching devices.
CISCO-SWITCH-USAGE-MIB
This MIB defines objects related to statistics for the usage of switch fabric. The switch fabric is used by the incoming packets from the line/network to a interface. Such packets are called ingress packets. Counters are maintained for number of ingress packets/ octets switched by the switch fabric for each interface. NOTE: These counters are not counting the total number of incoming packets and octets for a particular interface. Instead only the counts of packets and octets that actually use the switch-fabric are being accounted for by this MIB. Therefore, the counters in this MIB are distinctly different from packet and octet counters found in the IF-MIB.
CISCO-SYS-INFO-LOG-MIB
This MIB provides the configuration of System Information Logging feature, which allows a certain number of commands to be executed periodically via command line interface, and stores the result into a file on a configured server.
CISCO-SYSLOG-EVENT-EXT-MIB
This MIB module extends the Cisco Syslog MIB and provides network management support to handle and process Syslog messages as device events.
CISCO-SYSLOG-EXT-MIB
MIB module for configuring and monitoring System Log related management parameters as defined by RFC 3164.
CISCO-SYSLOG-MIB
The MIB module to describe and store the system messages generated by the IOS and any other OS which supports syslogs.
CISCO-SYSTEM-EXT-MIB
MIB module for monitoring High Availability, SNMP SET errors and bandwidths. This mib module also provides the information on core files that are generated in the system.
CISCO-SYSTEM-MIB
The systemGroup (see RFC 1907) provides a standard set of basic system information. This MIB module contains Cisco-defined extensions to the systemGroup.
CISCO-TBRIDGE-DEV-IF-MIB
This MIB module provides network management support for configuration and status information of devices supporting transparent bridging functions.
CISCO-TCP-MIB
An extension to the IETF MIB module for managing TCP implementations
CISCO-TCPOFFLOAD-MIB
This is the MIB module for objects used to manage the cisco tcp offload feature. The IBM mainframe (host) supports TCP/IP. As a way to save cycles on the host, the TCP/IP stack can be run on the 3172. This offloads the host from the protocol processing and is known as TCP-OFFLOAD. This mib identifies the manageable objects for the TCP-OFFLOAD feature in the Cisco router.
CISCO-TELEPRESENCE-CALL-MIB
The MIB module defines the managed objects for Telepresence calls. Telepresence refers to a set of technologies which allow a person to feel as if they were present, to give the appearance that they were present, or to have an effect, at a location other than their true location. Telepresence call is an audio-video call; however, some Telepresence systems also support audio addin call. Different security levels are supported in some Telepresence systems; security level may be specified from call management system. Some Telepresence systems support Telepresence meeting, the agent of the corresponding systems may also support CISCO-TELEPRESENCE-MEETING-MIB.
CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB
The main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notifications for the Cisco TelePresence Exchange System (CTX System).
CISCO-TELEPRESENCE-MIB
The MIB module defines the managed objects for a Telepresence system. Telepresence refers to a set of technologies which allow a person to feel as if they were present, to give the appearance that they were present, or to have an effect, at a location other than their true location. A complete Telepresence system includes one or more Telepresence CODECS and peripherals such as display, camera, speaker, microphone and presentation device. Peripherals are attached directly to a Telepresence CODEC via an interface. Some peripherals may have more than one interface to transmit audio and/or video data and provide a configuration and/or control access.
CISCO-TELNET-SERVER-MIB
MIB module for displaying and configuring Telnet related features in a device. Telnet is a program to log into another computer over a network, to execute commands in a remote machine.
CISCO-THREAT-MITIGATION-SERVICE-MIB
This MIB provides management information about the Threat Mitigation Service(TMS) entity named 'Consumer'. TMS is part of Cisco's Network Infection Containment (NIC) security framework. The MIB is expected to be implemented on all entities that act as TMS consumers. The NIC framework deals with threat mitigation. The NIC architecture consists of controllers and one or more consumers registered with these controllers. The controller is responsible for detecting threats and conveying the information about the same to one or more consumers that could be the potential targets of the detected threat. Upon receiving the information about the threat from the controller, the consumer responds with appropriate mitigation actions according to the policies configured on it and as indicated in the threat notification message. TMS protocol is used for distribution and management of threat related information from the controller to consumers. TMS runs over TIDP layer which is used as distribution layer. TIDP layer provides a secured connection between the controller and the consumers. TIDP also provides group management services. Each consumer needs to participate in a TIDP group in order to receive threat notification message from controller in that TIDP group. To participate in a TIDP group consumer needs to register with the controller of that group, from which it intends to receive threat messages. When the controller needs to distribute the information about a threat to one or more target TIDP groups or to one particular consumer in a TIDP group, it delivers the information to the respective entities through TMS protocol messages. Upon receiving the threat notification message, consumer determines the appropriate mitigation action to be executed, with the corresponding action parameters, based on the configuration and information available in threat message. The respective action is then executed. The state of threat is set according to the result of enforcement action, e.g., upon successful application of enforcement action it is marked as Active. The consumer then responds to the controller with the results of the mitigation action carried out for the threat.
CISCO-TM
Extension of SNMPv2-TM MIB
CISCO-TN3270SERVER-MIB
The MIB module for TN3270 Server. MIB description The PU and LU MIB are defined in RFC 1666. This MIB provides additional information on IP and LU mapping.
CISCO-TPC-MIB
The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved in the process of copying data either for backup operations or restore operations.
CISCO-TRANSACTION-CONNECTION-MIB
The MIB module for retrieving Cisco Transaction Connection configuration and status. Cisco Transaction Connection routes transactions between IBM CICS (Customer Information Control System) hosts and clients using the ISC (Inter-System Communication) protocol.
CISCO-TRUSTSEC-INTERFACE-MIB
This MIB module defines management objects for configuration and monitoring of the interfaces in Cisco Trusted Security environment.
CISCO-TRUSTSEC-MIB
This MIB module is for the configuration of a network device on the Cisco Trusted Security (TrustSec) system. TrustSec secures a network fabric by authenticating and authorizing each device connecting to the network, allowing for the encryption, authentication and replay protection of data traffic on a hop by hop basis.
CISCO-TRUSTSEC-POLICY-MIB
This MIB module defines managed objects that facilitate the management of various policies within the Cisco Trusted Security (TrustSec) infrastructure.
CISCO-TRUSTSEC-SERVER-MIB
This MIB module defines management objects for configuration and monitoring of the AAA servers in Cisco Trusted Security environment.
CISCO-TRUSTSEC-SXP-MIB
This MIB module is for the configuration and status query of SGT Exchange Protocol over TCP (SXPoTCP) feature of the device on the Cisco's Trusted Security (TrustSec) system. Security Group Tag (SGT) identifying its source, assigned to a packet on ingress to a TrustSec cloud, and used to determine security and other policy to be applied to it along its path through the cloud. SXPoTCP protocol extends the original SGT Exchange Protocol (SXP) protocol to enable a much wider array of deployment scenarios. This MIB uses the term SXP to refer to SXPoTCP. TrustSec secures a network fabric by authenticating and authorizing each device connecting to the network, allowing for the encryption, authentication and replay protection of data traffic on a hop by hop basis. SXP allows the deployment of RBACL, a key component of the TrustSec architecture, in the absence of TrustSec capable hardware.
CISCO-UBE-MIB
This MIB describes objects used for managing Cisco Unified Border Element (CUBE). The Cisco Unified Border Element (CUBE) is a Cisco IOS Session Border Controller (SBC) that interconnects independent voice over IP (VoIP) and video over IP networks for data, voice, and video transport
CISCO-UDLDP-MIB
Cisco Uni Direction Link Detection Protocol MIB
CISCO-UNIFIED-COMPUTING-MIB
This MIB module defines the managed objects for Unified Computing System (UCS) Manager. Cisco UCS Manager provides centralized management capabilities, creates a unified management domain, and serves as the central nervous system of the Cisco Unified Computing System. UCS configuration is comprised of operational and administrative settings. The data is organized hierarchically in a tree structure, starts from the top (root) and contains children and parent nodes. Each node in the tree is a managed object and each object in the UCS has a unique Distinguished Name (DN) that describes the object and its place in the tree. Every managed object is also identified through a CucsManagedObjectId of type integer. Managed objects are abstractions of real world resources, they represent the physical and logical components of the UCS, for example, switch, chassis, blades, and so on. Properties on the Managed Objects (MO) are characterized as configurations and operations. Configuration Policies are the majority of the policies in the system and are used to describe configurations of different components of the UCS. Policies determine how the system behaves under specific circumstances. Certain MOs are not created by users, but are automatically created by the UCS, power supply objects and fan objects are examples of automatically created MOs.
CISCO-UNITY-EXPRESS-MIB
The MIB Module for the management of the Cisco Unity Express (CUE) service. CUE is a voicemail service that runs in a Cisco router. CUE accepts connections from Cisco Call Manager Express (CCME), or from Cisco Call Manager (CCM).
CISCO-UNITY-MIB
The MIB Module for the management of Cisco Unity server. Cisco Unity is a Unified Communications solution that provides advanced, convergence-based communication services. The MIB presents provision and statistics information.
CISCO-VIDEO-SESSION-MIB
This MIB module complements the CISCO-VOICE-DIAL-CONTROL-MIB, which provides voice telephony peer information, by providing management of video telephony peer information. This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing video call information over an IP network. A video call is different from an audio call in that a video call typically consists of 2 call legs - audio and video - and each call leg is represented by one call entry. Therefore, each video call creates 2 call entries. In order to associate the video and audio entries of the same video call, a call reference ID is used, i.e., the video and audio entries of the same video call have the same call reference ID.
CISCO-VINES-MIB
CISCO-VIRTUAL-INTERFACE-MIB
The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface mib (rfc2863) will also contain entries for virtual interfaces. There are two ways virtual interfaces can be created and bound to an interface. The MIB Object cvifGroupsSupported indicates if a particular system supports the Virtual Interface Group concept. If Virtual Interface Groups are supported, then a virtual interface is always created/deleted in conjunction with its associated Virtual Interface Group. The Virtual Interface Group, which may be associated to multiple virtual interfaces, is then bound to a physical interface or another virtual interface like an EtherChannel. If Virtual Interface Groups are not supported, then a virtual interface is created/deleted independently. And each virtual interface is bound to a physical interface or another virtual interface like an EtherChannel. In order for a virtual interface to become operational, it must be directly or indirectly (via its Virtual Interface Group) bound to a physical interface or possibly to another virtual interface such as an EtherChannel. The cvifGroupTable is only used if the MIB object cvifGroupsSupported indicates Virtual Interface Groups are supported.
CISCO-VIRTUAL-NIC-MIB
This MIB module defines MIB objects which provide mechanisms to manage the parameters used by or related to Virtual NIC. Virtual switch extends across one or more virtualization servers which host the VM instances. Each virtualization server is represented as a line card module and is assigned to a unique slot in the virtual chassis. All the ports on the virtual switch which can be hooked up to VM VNICs or to special hypervisor ports (e.g. vmk or vswif ports) are represented as virtual ethernet interfaces. Virtual ethernet interfaces(veths) represent the switching ports on the virtual switch which provide networking connectivity to virtual packet based interfaces such as the Virtual NIC (VNIC) interfaces defined on a Virtual Machine (VM). These interfaces are configurable and provide operational information to the network administrator. The assignment of virtual ethernet interface ports to a VM does not change when the VM is migrated.
CISCO-VIRTUAL-NW-IF-MIB
The MIB module for management of virtual network interfaces to VSAN and VLAN.
CISCO-VIRTUAL-SWITCH-MIB
This MIB module defines the managed objects that support the virtual switch architecture. The virtual switch concept combines several individual distributed physical switches together to build a single logical management point. The core switches are the control point for a virtual switch, all the traffic is forwarded and distributed in the core switches, including control and data traffic. The core switches are connected through a dedicated ether channel called Virtual Switch Link (VSL) that is used for both control traffic as well as some data traffic to provide the traffic load sharing and switch redundancy between the physical chassis. One or multiple core switches can be supported in the virtual switch architecture, but only one core called 'active core' switch can be active to manage the traffic. The other is called 'standby core' switch as redundancy if there is. The concept of virtual switch is to collect many physical switches chassis together to form a single management unit to simplify the whole network architecture.
CISCO-VISM-ATM-TRUNK-MIB
The MIB module contain the Bearer and CID (Channel Identifier) connection information
CISCO-VISM-CAS-MIB
The MIB module contain the CAS backhaul feature in VISM
CISCO-VISM-CODEC-MIB
The MIB module contains tables for configurating and maintaining Codec on VISM service module.
CISCO-VISM-CONN-MIB
The MIB module to contains configuration and connection state information the VISM. For VoIP(Voice over IP) support, VISM needs one active AAL5 bearer PVC and one active AAL5 control PVC between the VISM card and the PXM. The redundant PVC feature is supported for AAL5 PVCs. Each redundant PVC pair has one active PVC and one standby PVC. There can be one AAL5 bearer redundant PVC pair and one AAL5 control redundant PVC pair. All PVCs are added on the ATM virtual port=1. For the AAL2 trunking application, there can be multiple AAL2 bearer PVCs. Also, AAL2 bearer PVC in this case, is between the two media gateways, instead of just between the VISM and the PXM. Up to 64 AAL2 bearer PVCs are supported for this application.
CISCO-VISM-CONN-STAT-MIB
The MIB module contain VISM channel counters information.
CISCO-VISM-DSX0-MIB
This MIB module contains ds0 configuration, Status and DS0 related information on a DS1 interface supported in VISM module. VISM is a Voice Interworking Service Module supported in MGX8250 and MGX8850 and other MGX products.
CISCO-VISM-DSX1-MIB
The MIB module to configure DS1/E1 interface objects in a Voice Interworking Service Module (VISM) module. This MIB is an extension to CISCO-MGX82XX-DSX1-MIB for DS1/E1 configuration in VISM.
CISCO-VISM-HDLC-MIB
The MIB module containing table for configurating and maintaining counters for the HDLC channel on VISM service module.
CISCO-VISM-MODULE-MIB
This MIB module contains VISM Card specific attributes and call statistics information for VISM service module.
CISCO-VISM-PORT-MIB
The MIB module containing Port information for VISM service module.
CISCO-VISM-RSRC-PART-MIB
The MIB module containing Port Resource Partition information for VISM service module.
CISCO-VISM-SESSION-MIB
The MIB module contain the RUDP session parameter. The relationship between session set, session group and RUDP session is that: For fault tolerant case each session set contains two groups. Each group connects to one MGC(Media Gateway Controller), One active, one standby. If one MGC fails, the other MGC will inform the session mamager to switch over. If the set configuration is non-fault tolerant, each set contains one group. Each session group contains upto four RUDP sessions. Session set is explicitly created first, then session group can be created in this set. After session group is created, session can be created in the group. For deletion, session has to be deleted first. However, the last session can not be deleted if there is still LAPD(Link Access Procedure on the D-channel) entry. A group can only be deleted if there is no more session in it. Session set will be deleted when the last group in the set has been deleted.
CISCO-VISM-SVC-MIB
The MIB module containing SVC information for VISM service module.
CISCO-VISM-XGCP-EXT
The MIB module contain the XGCP MIB feature in VISM
CISCO-VLAN-BRIDGING-MIB
A set of managed objects for optimizing access to bridging related data from RFC 1493. This MIB is modeled after portions of RFC 1493, adding VLAN ID based indexing and bitmapped encoding of frequently accessed data.
CISCO-VLAN-GROUP-MIB
MIB module for monitoring and configuring VLAN Group Mapping information.
CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
Cisco VLAN ifTable Relationship MIB lists VLAN-id and ifIndex information for routed VLAN interfaces. A routed VLAN interface is the router interface or sub-interface to which the router's IP address on the VLAN is attached. For example, an ISL, SDE, or 802.1Q encapsulated subinterface, or Switched Virtual Interface (SVI).
CISCO-VLAN-MEMBERSHIP-MIB
The MIB module for the management of the VLAN Membership within the frame work of Cisco VLAN Architecture, v 2.0 by Keith McCloghrie. The MIB provides information on VLAN Membership Policy Servers used by a device and VLAN membership assignments of non-trunk bridge ports of the device.
CISCO-VLAN-TRANSLATION-MIB
The MIB module for the management of VLAN translations. VLAN translation refers to the ability of the device to translate between different virtual LANs or between VLAN and non-VLAN encapsulating interfaces at Layer 2. Translation is typically used for selective inter-VLAN switching of non-routable protocols and to extend a single VLAN topology across hybrid switching environments.
CISCO-VMPS-MIB
The MIB module for the management of the VLAN Membership Policy Server.
CISCO-VOA-MIB
This MIB module defines objects to configure and manage the Variable Optical Attenuator (VOA) modules. VOA modules are typically used to attenuate channels added by a network element, in order to equalize the input power of each wavelength before the multiplexed signal consisting of all wavelengths is sent through an EDFA. There may be a separate VOA per channel, one VOA per band of wavelengths, or one VOA for the pass through wavelengths. VOA modules are also often used before terminating optical wavelengths at optical receivers, in order to avoid receiver saturation. The VOAs may be present on various modules within the network element, for example, on an Optical Add/Drop Multiplexer (OADM) module, on the same module as an optical transceiver, or on a separate module of its own.
CISCO-VOICE-AALX-PROFILE-MIB
This MIB defines the objects specific to voice over ATM or voice over IP.
CISCO-VOICE-ANALOG-IF-MIB
Analog Voice Interface MIB module. This MIB manages the E&M, FXO, FXS Interfaces in the router.
CISCO-VOICE-APPS-MIB
The MIB Module for the management of Cisco Voice Applications. This MIB is designed to work in conjunction with the SYSAPPL-MIB to provide status monitoring, provisioning and notification.
CISCO-VOICE-ATM-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing ATM management information over a data network.
CISCO-VOICE-CARD-MIB
The MIB module to configure voice-card specific parameters such as codec complexity in voice- enabled cisco routers.
CISCO-VOICE-COMMON-DIAL-CONTROL-MIB
This MIB module contains voice related objects that are common across more than one network encapsulation i.e VoIP, VoATM and VoFR.
CISCO-VOICE-CONNECTIVITY-MIB
This MIB module provides connectivity related information for devices (e.g., 'connectivity between voice gateway, phones, gatekeepers and call processing agent'). The MIB can be used by network management applications to collect the information regarding voice connectivity among the devices in the network. The MIB can also be used to retrieve the status of voice connectivity between the devices.
CISCO-VOICE-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing management of voice telephony peers on both a circuit-switched telephony network, and an IP data network.
CISCO-VOICE-ENABLED-LINK-MIB
This MIB module provides information about Voice Enabled ATM and Frame Relay Links used by the Cisco Switched voice protocol. The Cisco Switched voice protocol passes the default MAC address for its node to the next node in the path, in both call setup messages and keepalive requests and responses. This MAC address is stored at the remote node to identify where the incoming pvc originates. This information is then used by the Cisco Voice Manager Application to determine the voice network topology.
CISCO-VOICE-FR-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing FR management information over a data network.
CISCO-VOICE-HDLC-DIAL-CONTROL-MIB
This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing HDLC management information over a data network.
CISCO-VOICE-IF-MIB
Common Voice Interface MIB module. The MIB module manages the common voice related parameters for both voice analog and ISDN interfaces.
CISCO-VOICE-LMR-MIB
This MIB module provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes tone, pause, guard/idle tone. User can configure a sequence of tone and pause to be played out before any voice sample is played out. These tones are used to wake up the radio and select the radio channel. During the voice playout, a configured guard tone will be mixed with the voice to keep the radio active. For some radio systems, there is no need for the guard tone, but a configured idle tone is needed to inform the radio that the channel is idle. It is possible that the radio system will generate guard/idle tone. In that case, the IOS can instruct the DSP to filter out the radio generated guard/idle tone by enabling digital filter. Digital filter is able to filter out either 1950HZ or 2175HZ tone.
CISCO-VOICE-TONE-CADENCE-MIB
The MIB defines the attributes of the programmable tones specified in ITU-T E.180 Supplement 2. Each country has its own regulation to the generation and detection of the call progressing tones such as dial tone, busy tone, ring back tone. The tone attributes are programmable, for example frequency, amplitude, cadence and duration of the tone.
CISCO-VOICE-URI-CLASS-MIB
This MIB provides information about Voice URI classes that are used to select Dial Peers based on URI's. A Voice URI class contains a set of configurations that is used to match a Voice URI.
CISCO-VPDN-MGMT-EXT-MIB
Cisco VPDN management MIB extension Module. This MIB is a supplement to CISCO-VPDN-MGMT-MIB
CISCO-VPDN-MGMT-MIB
This MIB is to support the Virtual Private Dialup Network (VPDN) feature of Cisco IOS. VPDN handles the forwarding of PPP links from an Internet Provider (ISP) to a Home Gateway.
CISCO-VQE-TOOLS-MIB
This MIB module defines a set of objects for monitoring the VQE Client Channel Configuration Delivery Server (VCDS) operational status: number of open connections, Real Time Streaming Protocol (RTSP) reqests received and responses sent from the VCDS. Visual Quality Experience Tools Server(VQE-Tools) is responsible for the creation, maintenance, and distribution of the channel information containing channel-lineup data.
CISCO-VQES-MIB
This MIB module defines a set of objects for monitoring the Visual Quality Experience Server (VQE-S) operational status.
CISCO-VRF-MIB
The MIB module for provisioning and managing network virtualization features. This module provides manageability for VRF, VRF-Lite and vNET. VRF stands for Virtual Routing and Forwarding. VRF is an extension of IP routing that provides multiple routing instances. VRF provides independent routing instances and hence the same or over-lapping addresses can be used without conflicting each other. VRFs are used in conjunction with MPLS VPN to provide traffic separation between multiple VPN customers. A VRF-Lite enabled device implements VRFs and does not require MPLS for end to end communication. Instead of using MPLS labels, VRF-Lite uses the interfaces to distinguish routes for different VPNs. VRF-Lite forms virtual packet-forwarding tables by associating one or more interfaces with each VRF, and interfaces cannot belong to more than one VRF at any time. VRF-Lite is an IP based hop-by-hop virtualization mechanism and it involves complex configuration of every hop in the network. vNET, virtual network, is also an IP based hop-by-hop mechanism that can provide end-to-end virtualization of the network. vNET greatly reduces the complexity in VRF-Lite deployment.
CISCO-VSAN-MIB
The MIB module for the management of the Virtual Storage Networks (VSANs) within the frame work of Cisco's VSAN Architecture. This MIB enables the users to configure and monitor VSAN parameters.
CISCO-VSI-CONTROLLER-MIB
This MIB module is used for configuring ATM Capable Switch to be aware of VSI Controller information.
CISCO-VSIMASTER-MIB
This MIB module contains objects related to the master side of the Virtual Switch Interface protocol used for control of ATM switches.
CISCO-VTP-MIB
The MIB module for entities implementing the VTP protocol and Vlan management.
CISCO-WAN-3G-MIB
This MIB module provides network management support for Cisco cellular 3G WAN products.
CISCO-WAN-AAL2-PROFILES-MIB
The MIB module for configuring AAL2 profile elements. This table will be used in AAL2 switching and trunking applications.
CISCO-WAN-ANNOUNCEMENT-MIB
The MIB module is defined to configure the Announcements feature on the Media Gateway Card. The Media Gateway Card will have the capability to play pre-recorded local announcements in switched VoIP solutions only. Under the control of a call agent, announcements can be played in either direction over existing connections (calls) or towards the Time Division Multiplexed (TDM) network on a TDM endpoint that is terminated on the the Media Gateway Card.
CISCO-WAN-ATM-CONN-MIB
This MIB is used for configuring/provisioning SPVCs on the ATM interfaces. This is used for ATM switch connection management.
CISCO-WAN-ATM-CONN-STAT-MIB
This module contains ATM switch connection related real time statistical counter objects.
CISCO-WAN-ATM-COSB-MIB
The MIB to manage CoS(Class of Service) queue/buffer related parameters. One or more virtual interfaces may exist on a physical interface or a channelized interface. Every virtual interface has certain number (e.g. 16) of CoS queues. These queues are also known as Class Of Service Buffers. Every COS queue maps to an ATM trafiic type such as CBR, VBR-rt, ABR etc. These COS queues are used to provide QOS (quality of service), depending on the corresponding ATM trafiic type. This MIB provides management functionality such as Threshold Crossing Alarms(TCA) for cell discards and interval statistics for these COS queues.
CISCO-WAN-ATM-CUG-MIB
This MIB module is intended for the management of 'Closed User Group(CUG)' in Cisco ATM switches. This MIB definition is based upon 'Closed User Group' recommended by International Telecommunication Union(ITU). The CUG supplementary service enables users to form groups, to and from which access is restricted. A specific user may be member of one or more closed user groups. Members of a specific closed user group can communicate among themselves but not, in general, with users outside the group. Specific CUG members can have additional capabilities that allow them to originate calls to destinations outside the group, and/or to receive calls from outside the group. Specific CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG, or from receiving calls from other members of the CUG. ITU-T Q.2955.1 Stage 3 description for community of interest supplementary services using B-ISDN Digital Subscriber Signalling System No.2(DSS 2): Closed User Group(CUG).
CISCO-WAN-ATM-PARTY-MIB
A management station can use this MIB to provision, manage or delete one or more 'parties' on an ATM point-to-multipoint Soft PVCC(SPVC) connection. The user must add a root endpoint to the managed system before proceed to add one or more 'parties' to the root. The provision and management of a 'root' endpoint is beyond the scope of this MIB. Please refer to CISCO-WAN-ATM-CONN-MIB.my for the provisioning and management of a 'root' endpoint.
CISCO-WAN-ATM-PREF-ROUTE-MIB
This MIB facilitates the maintenance of preferred routes configuration.
CISCO-WAN-BBIF-ATM-CONN-MIB
The MIB module to configure the ATM Connections on a broad band interface in PXM1 Service module.
CISCO-WAN-BBIF-ATM-CONN-STAT-MIB
This MIB module contains ATM Connection related real time statistical counter objects. The ATM connections are applicable to PXM1 service module. in MGX82xx products. Logical Channel refers to ATM Connection(or connection end point).
CISCO-WAN-BBIF-ILMI-MIB
The MIB module for ILMI configuration and ILMI statistics for broad band interface ports in PXM1 service module. PXM1 service module is supported in MGX82xx series products. The broadband interface referred to in this mib is for ATM logical ports.
CISCO-WAN-BBIF-PORT-MIB
The MIB module for configuration of ATM logical ports in PXM1 Service module in MGX82xx series. This MIB contains information on ATM Logical port statistics.
CISCO-WAN-CES-CONN-MIB
The MIB module to configure the Circuit Emulation connections in MGX82xx series products.
CISCO-WAN-CES-CONN-STAT-MIB
The MIB module to provide CES Connections statistics. This MIB is supported in Circuit Emulation Service Modules(CESM) in MGX82xx, MGX88xx products. The channels and connections are used interchangeably in this mib.
CISCO-WAN-CES-PORT-MIB
The MIB module to configure the Circuit Emulation Service(CES) ports.
CISCO-WAN-CES-RSRC-PART-MIB
The mib module to configure the resource partition on Circuit Emulation Service(CES) ports. This is applicable for service modules providing the Circuit Emulation Services.
CISCO-WAN-FEEDER-MIB
This MIB is used for configuring a port on an ATM switch module to be aware of feeder connection information.
CISCO-WAN-FR-CONN-MIB
The MIB module to configure the Frame Relay connection configuration.
CISCO-WAN-FR-CONN-STAT-MIB
The MIB module for frame relay connection statistics.
CISCO-WAN-FR-PORT-MIB
The MIB module to create/configure frame relay ports/interfaces. This module contains tables related to frame relay port states and statistics. The frame relay logical port is referred to as 'frame relay port' in this mib.
CISCO-WAN-FR-RSRC-PART-MIB
The MIB module to configure the resource partition on Frame Relay Ports.
CISCO-WAN-FR-SIGNALING-MIB
The MIB module to configure LMI and CLLM on a frame relay ports. This mib module also contains objects to represent LMI and CLLM statistics information. The frame relay logical port is referred to as 'frame relay port' in this mib. The 'logical port' refers to frame relay port.
CISCO-WAN-FR-X21-MIB
The MIB module to configure X.21/HSSI physical and logical interfaces. This MIB module also contains alarm configuration of X.21 interfaces.
CISCO-WAN-LAPD-TRUNK-MIB
The MIB module is defined for establishing a Trunk to transport PRI (Primary Rate Interface) signaling information over a RUDP (Reliable UDP) connection for CCS (Common Channel Signaling) VoIP(Voice Over IP) Trunking application.
CISCO-WAN-MG-MIB
The MIB module for managing Media Gateways (MGs).
CISCO-WAN-MGC-REDUN-MIB
The MIB module for Media Gateways (MGs) to allow multiple Media Gateway Controllers (MGCs) to be configured and managed on the Gateway. MGCs can be group together as part of the same MGC redundancy group.
CISCO-WAN-MODULE-MIB
The MIB to configure Connection Specific parameters and statistics related information in a Service Module. The Service Module(SM) is defined as any Module which provides services such as ATM, Frame Relay or Voice in a Wide Area Network(WAN) switch.
CISCO-WAN-NCDP-MIB
This MIB module is intended for the management of network clock distribution and the Network Clock Distribution Protocol (NCDP) in Cisco MGX ATM switches. This MIB allows enabling automatic network clock configuration and distribution as well as configuration of manual clock sources. NCDP allows automatic distribution of network clocking sources in the network. A spanning network clock distribution tree is constructed by each node in the network and each node is synchonized to one single 'master' clock reference. A source of network clock for the device may be an oscillator local to the device or a Building Integrated Timing Supply (BITS) port or an interface that supports synchronous clock recovery. An 'index'('cwnClockSourceIndex') is assigned by the NCDP protocol entity in the managed system to identify each available source of network clock on the managed system
CISCO-WAN-OPTIMIZATION-MIB
This MIB is for managing Wide Area Network (WAN) Optimization systems. The objective of WAN optimization system is to reduce as much traffic as possible on WAN link and improve the application response time for various applications, which gets affected due to bandwidth, packet loss, congestion and latency limitations of WAN link. WAN optimization system is generally peer based system. They are located at both end of WAN link and peer with each other to perform optimization. This MIB provides instrumentation for monitoring statistics for various features implemented for WAN optimization. WAN optimization features includes TCP protocol optimizations and various Application Optimizers (AOs). AOs include SMB AO, HTTP AO, CIFS AO, NFS AO, MAPI AO, VIDEO AO, SSL AO and EPM AO.
CISCO-WAN-PAR-MIB
The MIB module for configuring AutoRoute controller. The Portable AutoRoute(PAR) is a Controller providing routing capabilities in Network of Cisco MGX and BPX Switches.
CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB
The MIB module for managing CA(Call Agent) events.
CISCO-WAN-RPM-CONN-EXT-MIB
This MIB together with the CISCO-WAN-ATM-CONN-MIB support provisioning of PVC endpoints and SPVCs on the MGX's Route Processor Module (RPM).
CISCO-WAN-RSRC-PART-MIB
The MIB module to manage resource partition objects. A resource partition is configured on a virtual interface (ifType value atmVirtual(149)) or atm interface (ifType value atm(37)). An administrator can partition connection related resources like VPI, VCI ranges, bandwidth and total amount of available connection entries in the switch through these MIB tables.
CISCO-WAN-RTP-CONN-MIB
The MIB module is defined for establishing connection between an endpoint and another endpoint on a remote VISM in the case of VoIP(Voice over IP) trunking application.
CISCO-WAN-SCT-MGMT-MIB
MIB module to manage SCT files in a node. SCTs (Service Class Templates) are nodal configuration files, which define the traffic characteristics of a switch based on class of service queues. There is a unique SCT file for every combination of card type, SCT type, SCT Id and major SCT version. For instance, the file AXSM_PORT_SCT.4.V2 refers to a SCT for the card type AXSM, port type SCT, SCT id 4 and a major version of 2. SCTs are transfered to a node using FTP by NMS. The NMS adds, deletes, discovers and monitors SCT files in a node using this MIB.
CISCO-WAN-SONET-MIB
The MIB module to describe SONET/SDH interfaces objects. This is an extension to the standard SONET MIB(RFC 2558).
CISCO-WAN-SRCP-MIB
The MIB module for managing SRCP(Simple Resource Coordination Protocol) implementations. SRCP is a resource coordination protocol used between a MGC(Media Gateway Controller) and a MG(Media Gateway). SRCP MIB is applicable to both controllers (SRCP clients) and gateways (SRCP servers).
CISCO-WAN-SRM-BERT-MIB
The MIB Module for BERT(Bit Error Rate Testing) using Service Resource Module(SRM). This MIB module is used for BERT on FRSM, AUSM, CESM, VISM modules. This module contains information on results from BERT tests using DDS(Digital Data Service) pattern.
CISCO-WAN-SRM-MIB
The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interfaces). This is used for configuring bulk distribution of T3 interfaces on T1 modules supported in MGX82xx series. Some of the T1 modules are AUSM, FRSM,CESM. This MIB module also contains info. on configuring bulk distribution of SONET interfaces(VT interfaces) on T1 Modules.
CISCO-WAN-SVC-MIB
The MIB modules describe an ATM network service on a BPX-SES or a MGX ATM switch. This MIB module provides configuring, provisioning, as well as status gathering for ATM services.
CISCO-WAN-TOPOLOGY-MIB B
A management station can use this MIB module for the maintenance of persistent topology information of the PNNI network. Previously, a management station had to query the network to retrieve the network topology via an Integrated Local Management Interface (ILMI) link. The nodes that are down or the nodes whose ILMI-enabled links are down will not be included in the topology. To rectify this limitation, the concept of persistent topology is used.
CISCO-WAN-TRAP-VARS-MIB
This MIB module is for Supporting Varbinds used only in trap defintions. The NMS applications should not depend on the implementation of these objects.The SNMP Requests(GET,GET-NEXT) may not be valid for these objects.
CISCO-WDS-IDS-MIB
This MIB is intended to be implemented on all IOS based network entities that provide Wireless Domain Services, for the purpose of providing network management stations information about the various attempts to compromise the security in the 802.11-based wireless networks. Entities that can be configured to provide Wireless Domain Services could be an 802.11 Access Point, a Switch or any other IOS network device, that allows the WDS configuration. The MIB reports the information about the MAC spoofing attempts made by wireless clients to compromise the security of the network.
CISCO-WDS-INFO-MIB
This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provides a control mechanism for wireless devices that roam between Access Points residing on different layer 3 subnets. When WDS is in the Wireless LAN Services Module(WLSM), the access points providing Layer 3 mobility must register with the WDS before wireless devices are given access to the mobility network. The location of the WDS is specified in each Access Point along with LEAP device credentials that are required for authentication with the WDS. Once the Access Point and the Mobile Node are authenticated with the WDS, those are considered registered. This MIB reports the information about the Wireless Domain Servers, Access Points, Mobile Nodes, and their roaming patterns.
CISCO-WIRELESS-DOCS-EXT-MIB
This MIB module defines Cisco-specific objects that add to the functionality defined in CISCO-WIRELESS-DOCS-IF-MIB. These objects configure the scheduler that supports Quality of Service (QoS) of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces in Wireless Headends (HE).
CISCO-WIRELESS-DOCS-IF-MIB
This is the MIB Module for MCNS compliant Radio Frequency (RF) interfaces in wireless point-to-multipoint subscriber units (SU) and wireless Head-end (HE).
CISCO-WIRELESS-EXP-MIB
This is the MIB Module for the Cisco Wireless Radio Point to Point experimental components.
CISCO-WIRELESS-IF-MIB
This is the MIB Module for the Cisco Wireless Radio Point to Point interface specification.
CISCO-WIRELESS-P2MP-LINK-METRICS-MIB
This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface link metrics specification
CISCO-WIRELESS-P2MP-PHY-MIB
This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface.
CISCO-WIRELESS-P2MP-RF-METRICS-MIB
This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface specification.
CISCO-WIRELESS-P2P-BPI-MIB
This is the MIB Module for the Baseline Privacy Interface (BPI) at Point to Point Wireless Radio Card. This is a specialization on the MCNS docsBpiMib for Cisco Wireless point to point communication links.
CISCO-WLAN-MAN-MIB
This MIB module provides network management and configuration support for IEEE 802.11 Wireless LAN devices.
CISCO-WLAN-VLAN-MIB
This MIB module provides network management support for device VLAN configuration on IEEE 802.11 wireless LAN.
CISCO-WRED-MIB
Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop is a method which avoids traffic congestion on an output interface. Congestion is detected by computing the average output queue size against preset thresholds. WRED support are on the IP fast switching and IP flow switching only. It does not apply to IP process switching. This MIB incorporates objects from the Cisco WRED line interfaces. Its purpose is to provide Weighted Random Early Detection/Drop packet configuration and packet filtering information. WRED are configured/enabled through the CLI command. Defaults configuration values are assigned and values can be modified through additional CLI commands.
CISCO-WWNMGR-MIB
The World Wide Name (WWN) in the fibre channel networking technology is equivalent to the MAC address in Ethernet. There are six different types of WWNs defined in ANSI Standard for Fibre Channel Framing and Signalling (FC-FS) Spec Rev 1.4. This mib provides the mechanism to configure and report WWNs for the fibre channel devices connected to a fibre channel switch.
CISCO-XDSL-LINE-MIB
The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to different types of modems. The structure of this module resembles the ADSL-LINE-MIB, CISCO-SDSL-LINE-MIB, ADSL-DMT-LINE-MIB, CISCO-ADSL-DMT-LINE-MIB, etc. Observe that the tables in this module do not necessarily extend the tables defined by the these mibs. Currently, only the table that contains the configuration information extends the profile tables defined by the above modules.
CISCO-XGCP-EXT-MIB
This MIB module is an extension to CISCO-XGCP-MIB.
CISCO-XGCP-MIB
This MIB is an enhancement for existing XGCP-MIB. xGCP is a set of protocols, for example SGCP (Simple Gateway Control Protocol) and MGCP (Media Gateway Control Protocol), which are designed as a control protocol within a distributed system that appears to the outside as a single VoIP/VoATM gateway. This system is composed of a call agent (or MGC, Media Gateway Controller) and of a set of 'media gateways' that perform the conversion of media signals between circuits and packets. In the xGCP model, the gateways focus on the audio signal translation function, while the call agent handles the signaling and call processing functions.
CISCO-ZS-EXT-MIB
The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the FC-GS4/SW3 requirements for Zone Server. This MIB is an extension to the CISCO-ZS-MIB, which is for managing zoning conforming to FC-GS3/SW2. The FC-GS4 specification is Fibre-Channel - Generic Services - 4 T11/ Project 1505-D/Rev 7.8. The SW3 specification is Fibre-Channel - Switch Fabric - 3 T11/Project 1508- D/Rev 6.6. GS4/SW3 allows zoning to operate in either basic or enhanced mode of operation. Basic mode is essentially GS3/SW2 compatible mode (as modelled by CISCO-ZS-MIB). Enhanced mode of operation provides additional capabilities. In enhanced mode of operation, all the configuration should be done within the scope of a session. The current 'Running Configuration' on the local device for zone server is called the 'effective' database. When the first configuration command on the zone server data is received, a snapshot of the current 'effective database' is taken on the local device. This snapshot is called the 'copy' database. An implicit session is started by the Zone Server on the local device and all subsequent SET operations take place in the context of this session. The 'copy' database is used for all further modifications in the session. There can be only one session active in the entire Fibre Channel fabric. The user who initiates the creation of this 'copy', is called the owner of session. When a session has been created on a device in the Fibre Channel fabric, if an attempt is made to start a session from any other device in the fabric, it results in error. Once the modifications to the 'copy' are done, a 'commit' operation can be done. The 'commit' done on the local device, results in the local 'effective database' being overwritten with the 'copy' and then the new local 'effective database' is distributed to all other devices in the Fibre Channel fabric. The successful 'commit' operation also results in destroying the 'copy' on the local device. The 'commit' can only be performed by the owner of the session. The 'copy' can optionally be destroyed without any distribution. This can be done by performing a 'clear' operation.
CISCO-ZS-MIB
The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the FC-GS3 requirements for Zone Server. This MIB enables managers to configure and monitor zoning server parameters. Additionally, Cisco's Zoning Server allows for configuration of Lun zoning, which is an extension to the Zoning Server standard specified by FC-GS3.
CISCOWAN-SMI
The Structure of Management Information for the stratacom enterprise.
CISCOWORKS-MIB
This MIB describes the traps and trap and trap variables used by CiscoWorks. Originally the CiscoWorks classic nmlogd process forwarded messages logged by applications and devices to NM platforms as traps. Now it is used by CiscoWorks Blue to send DLSw and APPN/SNASw traps to NM platforms.
clj4500
This MIB describes all the printer model specific objects supported by the HP Color LaserJet Series 4500 printer when networked connected using a JetDirect print server.
clj8500
This MIB describes all the printer model specific objects suppported by the Color LaserJet 8500 printer when networked connected using a JetDirect print server.
community-mib
This module provides authoritative definitions for Cabletron's enterprise-specific community table MIB.
CONFIG-MIB
CPQAPLI
Compaq Server Appliance information
CPQCLUS
Compaq Cluster information
CPQCMC
Compaq Console Management Controller - (CMC) MIB
CPQCR
Compaq CR3500 RAID Controller information
CPQFCA
Compaq Fibre Array information
CPQHLTH
Compaq Server Health information
CPQHOST
Host Server Operating System information
CPQIDA
Compaq Intelligent Drive Array information
CPQIDE
Compaq IDE information
CPQNIC
Compaq Network Interface Card information
CPQRACK
Compaq Rack Information MIB
CPQRECOV
Compaq Recovery Server information
CPQSCSI
Compaq SCSI Device information
CPQSINFO
Compaq Specific PC Server information
CPQSM2
Compaq Remote Insight information
CPQSTAT
Compaq External Status information
CPQSTDEQ
Standard PC Server Equipment information
CPQSTSYS
Compaq Storage Systems information
CPQTHRSH
Settable Threshold information
CPQUPS
Compaq Uninterruptible Power Supply (UPS) information
CRESCENDO-CONCENTRATOR-MIB
CRESCENDO-MIB
Crossroads
Crossroads private mib for 4100 and 4200 Fibre Channel to SCSI Router.
CROUTE-MIB
ct-broadcast-mib
This module provides authoritative definitions for Cabletron's broadcast mib.
ct-cmmphys-mib
This module provides an enterprise-specific CMM container MIB.
ct-container-mib
This module provides authoritative definitions for Cabletron's enterprise-specific container MIB.
ct-els10-mib
ct-fastpath-arpacl-mib
This module provides authoritative definitions for Cabletron's CT-FASTPATH-ARPACL-MIB.
ct-fastpath-dhcpserver-mib
This module provides authoritative definitions for Cabletron's CT-FASTPATH-DHCPSERVER-MIB.
ct-fastpath-dhcpsnooping-mib
This module provides authoritative definitions for Cabletron's CT-FASTPATH-DHCPSNOOPING-MIB.
ct-fastpath-dynamic-arp-inspection-mib
This module provides authoritative definitions for Cabletron's CT-FASTPATH-DYNAMIC-ARP-INSPECTION-MIB.
ct-fastpath-protected-port-mib
This module provides authoritative definitions for Cabletron's CT-FASTPATH-PROTECTED-PORT-MIB
ct-flash-mib
This module provides authoritative definitions for Cabletron's flash filing system mib.
ct-fps-services-mib
This module provides authoritative definitions for Cabletron's enterprise-specific chassis MIB.
ct-hsimphys-mib
This module provides an enterprise-specific HSIM container MIB.
ct-pic-mib
This module provides authoritative definitions for part of the naming tree below: cabletron { enterprises 52 }
ct-priority-classify-mib
This module provides authoritative definitions for Cabletron's enterprise-specific priority classification MIB.
ct-priority-queuing-mib
This module provides definitions for the 802.1p priority queuing MIB.
ctatm-config-mib
This module provides authoritative definitions for part of the naming tree below: cabletron { enterprises 52 }
ctels100-ng-mib
This module provides authoritative definitions for part of the naming tree below: cabletron { enterprises 52 }
ctfps-mib
ctframer-config-mib
This module provides authoritative definitions for part of the naming tree below: cabletron { enterprises 52 }
ctif-ext-mib
This module provides authoritative definitions for part of the naming tree below: cabletron { enterprises 52 }
ctinb-mib
ctinb2-mib
This module provides authoritative definitions for Cabletron's INB2 MIB.
ctrmonxt-mib
This module provides authoritative definitions for part of the naming tree below: cabletron { enterprises 52 }
ctron-alias-mib
This module provides authoritative definitions for Enterasys Networks' Alias MIB.
ctron-ap3000-mib
ctron-appletalk-router-mib
This module provides authoritative definitions for Cabletron's enterprise specific at Routing Services MIB.
ctron-appn-mib
This module provides authoritative definitions for Cabletron's enterprise specific APPN Routing Services MIB.
ctron-bdg-mib
ctron-bridge-mib
ctron-bus-mib
ctron-cdp-mib
ctron-chassis-mib
This module provides authoritative definitions for Cabletron's enterprise-specific chassis MIB.
ctron-common-mib
ctron-csmacd-mib
ctron-dcm-mib
ctron-deciv-router-mib
ctron-device-mib
ctron-dhcp-mib
ctron-dlsw-mib
ctron-download-mib
ctron-elan-mib
ctron-entity-state-mib
ctron-entity-state-tc-mib
ctron-environment-mib
ctron-ethernet-parameters
ctron-etwmim-mib
ctron-fddi-fnb-mib
ctron-fddi-stat-mib
ctron-fnbtr-mib
ctron-frontpanel-mib
ctron-if-remap-2-mib
ctron-if-remap-mib
ctron-igmp-mib
ctron-ip-router-mib
ctron-ipx-router-mib
ctron-mib-names
ctron-nat-mib
ctron-oids
ctron-orp-hsim-mib
ctron-portmap-mib
ctron-power-supply-mib
ctron-ppc-bad-packets
ctron-priority-classify-mib
ctron-priority-extensions-mib
ctron-q-bridge-mib-ext
ctron-rate-policing-mib
ctron-remote-access-mib
ctron-routers-internal-mib
ctron-routers-mib
ctron-sfcs-mib
ctron-sfps-base-mib
ctron-sfps-bindery-mib
ctron-sfps-call-mib
ctron-sfps-chassis-mib
ctron-sfps-common-mib
ctron-sfps-conn-mib
ctron-sfps-connection-mib
ctron-sfps-diagstats-mib
ctron-sfps-directory-mib
ctron-sfps-esys-mib
ctron-sfps-eventlog-mib
ctron-sfps-flood-mib
ctron-sfps-include-mib
ctron-sfps-l4ss-mib
ctron-sfps-mcast-mib
ctron-sfps-path-mib
ctron-sfps-pktmgr-mib
ctron-sfps-policy-mib
ctron-sfps-port-mib
ctron-sfps-resolve-mib
ctron-sfps-sflsp-mib
ctron-sfps-size-mib
ctron-sfps-softlink-mib
ctron-sfps-tap-mib
ctron-sfps-topology-mib
ctron-sfps-vlan-mib
ctron-sfps-vstp-mib
ctron-smarttrunk-mib
ctron-ssr-capacity-mib
ctron-ssr-config-mib
ctron-ssr-hardware-mib
ctron-ssr-l2-mib
ctron-ssr-l3-mib
ctron-ssr-policy-mib
ctron-ssr-service-status-mib
ctron-ssr-smi-mib
ctron-ssr-trap-mib
ctron-timed-reset-mib
ctron-translation-mib
ctron-tx-queue-arbitration-mib
ctron-ups-mib
ctron-vlan-classify-mib
ctron-vlan-extensions-mib
ctron-wan-imux-mib
ctron-wan-mib
ctron-wan-multi-imux-mib
ctron-webview-mib
ctsmtmib-mib
cttraplog-mib
CYBERGUARD-MIB

2 3 8 A B C D E F G H I J L M N O P Q R S T U V W X Z


Privacy Policy