CISCO-MGX82XX-CARD-FEATURE-MIB device MIB details by Stratacom
CISCO-MGX82XX-CARD-FEATURE-MIB file content
The SNMP protocol is used to for conveying information and commands between agents and managing entities. SNMP uses the User Datagram Protocol (UDP) as the transport protocol for passing data between managers and agents. The reasons for using UDP for SNMP are, firstly it has low overheads in comparison to TCP, which uses a 3-way hand shake for connection. Secondly, in congested networks, SNMP over TCP is a bad idea because TCP in order to maintain reliability will flood the network with retransmissions.
Management information (MIB) is represented as a collection of managed objects. These objects together form a virtual information base called MIB. An agent may implement many MIBs, but all agents must implement a particular MIB called MIB-II [16]. This standard defines variables for things such as interface statistics (interface speeds, MTU, octets sent, octets received, etc.) as well as various other things pertaining to the system itself (system location, system contact, etc.). The main goal of MIB-II is to provide general TCP/IP management information.
Use ActiveXperts Network Monitor 2024 to import vendor-specific MIB files, inclusing CISCO-MGX82XX-CARD-FEATURE-MIB.
| Vendor: | Stratacom |
|---|---|
| Mib: | CISCO-MGX82XX-CARD-FEATURE-MIB [download] [view objects] |
| Tool: | ActiveXperts Network Monitor 2024 [download] (ships with advanced SNMP/MIB tools) |
-- ***************************************************************** -- ciscoMgx82xxCardFeatureMIB -- -- May 2003, Subra Hegde -- -- Copyright (c) 2003 by cisco Systems, Inc. -- All rights reserved. -- **************************************************************** CISCO-MGX82XX-CARD-FEATURE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF cardSpecific FROM BASIS-MIB ciscoWan FROM CISCOWAN-SMI; ciscoMgx82xxCardFeatureMIB MODULE-IDENTITY LAST-UPDATED "200305050000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-wanatm@cisco.com" DESCRIPTION "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. Terminologies used: PXM : Processor Switch Module. This is controller card in MGX8250. ASC : AXIS Shelf Controller. This is controller card in MGX8220. VSI : Virtual Switch Interface, a hardware-independent switch control protocol. This allows a Switch to be controlled by a multiple controllers such as PNNI, MPLS. These control planes can be internal or external to the switch.The VSI interface defines the messages and associated functions which allow communication between the controller and the switch.This interface is expected to support all types of connections (voice,data,frame relay,ATM) for PVCs, SPVCs and SVCs. Controller - Software ( and possibly hardware) which manages topology and network resources and performs VSI Master function. This performs source routing for end-to-end SVCs, including general call acceptance GCAC,setup calls with other controllers. PNNI and MPLS are examples of controllers." REVISION "200305050000Z" DESCRIPTION "Initial version of the MIB. The content of this MIB was originally available in CISCO-WAN-AXIPOP-MIB defined using SMIv1. The applicable objects from CISCO-WAN-AXIPOP-MIB are defined using SMIv2 in this MIB. Also the descriptions of some of the objects have been modified." ::= { ciscoWan 74 } ascFeatures OBJECT IDENTIFIER ::= { cardSpecific 5 } pxmFeatures OBJECT IDENTIFIER ::= { cardSpecific 15 } coreCardCommands OBJECT IDENTIFIER ::= { cardSpecific 20 } vsiControllersAllowed OBJECT-TYPE SYNTAX Integer32 (0..16777215) MAX-ACCESS read-only STATUS current DESCRIPTION "This respesents bit map of the VSI Controllers supported. The bit positions are : BIT 0 - PAR(Portable AutoRoute Controller) BIT 1 - PNNI(Private network to network Interface) BIT 2 - TAG(Tag Switching or MPLS Controller) (e.g. A value of 1 in BIT 0 indicates the presence of PAR ) Remaining bits are set to 0." ::= { pxmFeatures 1 } apsCardAttributes OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "This respesents bit map of the APS card attributes supported. The bit position supported are: BITs 0, 1 - unused BIT 2 - APS standard protocol configured (1 = TRUE ; 0 = FALSE) BIT 3, 4 ,5 - unused BIT 6 - Card HW supports APS 1+1 on two cards (1 = TRUE ; 0 = FALSE) BIT 7 - Card FW supports APS (1 = TRUE ; 0 = FALSE) Remaining bits are set to 0." ::= { pxmFeatures 2 } trkCACEnable OBJECT-TYPE SYNTAX INTEGER { disable (1), enable (2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This MIB variable allows to add a new connection on the feeder trunk even if it is over-subscribed." DEFVAL { disable } ::= { pxmFeatures 3 } pxmCardCacMode OBJECT-TYPE SYNTAX INTEGER { pcrBasedCac (1), scrBasedCac (2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object identifies the CAC mode set on a card. If this is set to pcrBasedCAC(1) then the CAC calculations will be done based on PCR on the connection. If this set to scrBasedCAC(2) then the CAC calculations are done based on the scr of the connections. This will be applicable only if CAC is enabled (i.e trkCACEnable is set to enable(2))." DEFVAL { pcrBasedCac } ::= { pxmFeatures 4 } redundancyAllowed OBJECT-TYPE SYNTAX INTEGER { redNotAllowed (1), redAllowed (2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies whether redundancy is allowed in MGX82XX shelf." ::= { ascFeatures 1 } switchCoreCard OBJECT-TYPE SYNTAX INTEGER { noAction (1), doswitchcc (2), instswitchcc (3), fallbackswitchcc (4) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used for performing switchover of core card set. The core card set includes Controller Card and Service Redundancy Module(SRM). The possible values are : noAction (1): No operation doswitchcc (2): Perform switchover operation instswitchcc (3): Perform switchover operation fallbackswitchcc(4): " ::= { coreCardCommands 1 } -- conformance information cmCardFeatureMIBConformance OBJECT IDENTIFIER ::= { ciscoMgx82xxCardFeatureMIB 2 } cmCardFeatureMIBGroups OBJECT IDENTIFIER ::= { cmCardFeatureMIBConformance 1 } cmCardFeatureMIBCompliances OBJECT IDENTIFIER ::= { cmCardFeatureMIBConformance 2 } -- compliance statements cmCardFeatureCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for objects related to Frame Relay Ports." MODULE -- this module MANDATORY-GROUPS { cmPxmCardFeatureGroup, cmAscCardFeatureGroup, cmCoreCardFeatureGroup } ::= { cmCardFeatureMIBCompliances 1 } cmPxmCardFeatureGroup OBJECT-GROUP OBJECTS { vsiControllersAllowed, apsCardAttributes, trkCACEnable, pxmCardCacMode } STATUS current DESCRIPTION "The collection of objects which are used to represent Processor Module(PXM) Features." ::= { cmCardFeatureMIBGroups 1 } cmAscCardFeatureGroup OBJECT-GROUP OBJECTS { redundancyAllowed } STATUS current DESCRIPTION "The collection of objects which are used to represent Axis Shelf Controller(ASC) Features." ::= { cmCardFeatureMIBGroups 2 } cmCoreCardFeatureGroup OBJECT-GROUP OBJECTS { switchCoreCard } STATUS current DESCRIPTION "The collection of objects which are used to represent core card related objects." ::= { cmCardFeatureMIBGroups 3 } END