CISCO-WAN-BBIF-ATM-CONN-MIB: View SNMP OID List / Download MIB

VENDOR: STRATACOM


 Home MIB: CISCO-WAN-BBIF-ATM-CONN-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
                 bbChanCnfGrpTable 1.3.6.1.4.1.351.110.5.2.7.1.1 no-access
The Broadband Channel config table is for a channel on logical interface. There will an entry for each of the channel added on the logical partition of the physical line. Following parameters are needed if the connection is from a PXM user port and policing is enabled. These apply to connection on PXM lines confiured as user port only. PCR/CDVT is used for GCRA1 and SCR/MBS is used for GCRA2 UpcEnable UpcPCR UpcCDVT UpcSCRPolicing for CBR conns. UpcPCR0 UpcCDVT0 for non CBR conns. UpcSCR UpcMBS
                     bbChanCnfGrpEntry 1.3.6.1.4.1.351.110.5.2.7.1.1.1 no-access
The config table is for logical channel.
                         bbChanCnfNum 1.3.6.1.4.1.351.110.5.2.7.1.1.1.1 integer32 read-only
This identifies a channel on the PXM logical interface, used as PXM port.
                         bbChanRowStatus 1.3.6.1.4.1.351.110.5.2.7.1.1.1.2 integer read-write
This object is used for adding/deleting/modifying entries in the table. add(1) : Adds the entry. delete(2) : Deletes the entry modify(3) : Set this before modifying any entries in the table. Following parameters need to be available before creating the entry: bbChanConnType, bbChanServiceType. Enumeration: 'add': 1, 'modify': 3, 'delete': 2.
                         bbChanConnType 1.3.6.1.4.1.351.110.5.2.7.1.1.1.3 integer read-write
This specifies the connection type vpc(1) : Virtual Path Connection vcc(2) : Virtual Channel Connection This object can not be modified once the connection is created. Enumeration: 'vcc': 2, 'vpc': 1.
                         bbChanServiceType 1.3.6.1.4.1.351.110.5.2.7.1.1.1.4 integer read-write
This specifies the service type cbr(1) : Constant Bit Rate vbr(2) : Variable Bit Rate abr(3) : Available Bit Rate ubr(4) : Unspecified Bit Rate vbr-rt(5): Variable Bit Rate - Real Time This object can not be modified once the connection is created. Enumeration: 'cbr': 1, 'vbr': 2, 'abr': 3, 'vbr-rt': 5, 'ubr': 4.
                         bbChanConnDesc 1.3.6.1.4.1.351.110.5.2.7.1.1.1.5 displaystring read-write
A string that has been defined to give a descriptive name to the connection.
                         bbChanSvcFlag 1.3.6.1.4.1.351.110.5.2.7.1.1.1.6 integer read-write
This specifies the connection type svc(1) : SVC connection pvc(2) : PVC connection, used by PAR(Portable Auto Route) spvc(3) : Soft PVC connection, used by PNNI Enumeration: 'spvc': 3, 'pvc': 2, 'svc': 1.
                         bbChanSvcConnId 1.3.6.1.4.1.351.110.5.2.7.1.1.1.7 integer32 read-write
This connection ID is for future use Currently not supported.
                         bbChanIfNum 1.3.6.1.4.1.351.110.5.2.7.1.1.1.8 integer32 read-write
Channel's logical Interface from which traffic of the connection will be received.
                         bbChanVpi 1.3.6.1.4.1.351.110.5.2.7.1.1.1.9 integer32 read-write
VPI for the connection.
                         bbChanVci 1.3.6.1.4.1.351.110.5.2.7.1.1.1.10 integer32 read-write
VCI for the connection.
                         bbChanUpcEnable 1.3.6.1.4.1.351.110.5.2.7.1.1.1.11 integer read-write
enables/disables UPC for Ingress cells. Enumeration: 'enable': 2, 'disable': 1.
                         bbChanUpcPCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.12 integer32 read-write
PCR(0+1), Peak Cell Rate, specifies an upper bound on rate at which traffic can be submitted on an ATM connection. This object applies to the First Leaky Bucket for leaving cells with Cell Loss Priority of 0 or 1. . Units: cells per second. . Applicable connection types: UBR, CBR, VBR, ABR . Default: 50 . Ranges: T3 : 50-96000 E3 : 50-80000 OC3 : 50-353208 OC12: 50-1412832 PCR is used for GCRA1.
                         bbChanUpcCDVT 1.3.6.1.4.1.351.110.5.2.7.1.1.1.13 integer32 read-write
Compliant Cell Delay Variation. Also known as CDVT(0+1), Cell Delay Variation Tolerance, which specifies the maximum time period for accumulated violations of cell-arrival time parameters. This object applies to the First Leaky bucket for cells with Cell Loss Priority of 0 or 1. . Units: microseconds. . Applicable connection types: UBR, CBR, VBR, ABR . Default: CBR: 10000 Others: 250000
                         bbChanUpcSCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.14 integer32 read-write
SCR, Sustainable Cell Rate, is an upper bound on the conforming average rate of an ATM connection, over time scales which are long relative to those for which the PCR is defined. Enforcement of this bound by the UPC could allow the network to allocate sufficient resources, but less than thos based on the PCR, and still ensure that the performance objectives (e.g., Cell Loss Ratio) can be achieved. . Units: cell per second. . Applicable connection types: . VBR, ABR . Ranges: T3 : 50-96000 E3 : 50-80000 OC3 : 50-353208 OC12: 50-1412832 . Default: 50
                         bbChanUpcMBS 1.3.6.1.4.1.351.110.5.2.7.1.1.1.15 integer32 read-write
Maximum Burst Size (MBS). Also known as Compliant Burst Size (CBS). . Units: cells . Applicable connection types: . VBR, ABR . Default: 1000 . Range : 1-5000000
                         bbChanGcra1Action 1.3.6.1.4.1.351.110.5.2.7.1.1.1.16 integer read-write
GCRA1 Action. 1 = No Action 2 = Tag Untagged cells 3 = Tag untagged cells and discard tagged cells 4 = Discard all (0+1) non-comforming cells. Enumeration: 'discardAllNonComformCells': 4, 'tagAndDiscard': 3, 'tagCells': 2, 'noAction': 1.
                         bbChanGcra2Action 1.3.6.1.4.1.351.110.5.2.7.1.1.1.17 integer read-write
GCRA2 Action. 1 = No Action 2 = Tag Untagged cells 3 = Tag untagged cells and discard tagged cells 4 = Discard all (0+1) non-comforming cells. Enumeration: 'discardAllNonComformCells': 4, 'tagAndDiscard': 3, 'tagCells': 2, 'noAction': 1.
                         bbChanUpcSCRPolicing 1.3.6.1.4.1.351.110.5.2.7.1.1.1.18 integer read-write
Selects SCR policing for CLP = 0 or all cells. Enumeration: 'clp0': 1, 'off': 3, 'clp0and1': 2.
                         bbChanEfciThreshold 1.3.6.1.4.1.351.110.5.2.7.1.1.1.19 integer32 read-write
Threshold above which EFCI bit is to be set. Default Value is 3/4 of max cell count.
                         bbChanDiscardOption 1.3.6.1.4.1.351.110.5.2.7.1.1.1.20 integer read-write
Enable Frame Discard or CLP Hysteresis. Enumeration: 'clpHysteresis': 1, 'frameDiscard': 2.
                         bbChanFrmDiscardThreshold 1.3.6.1.4.1.351.110.5.2.7.1.1.1.21 integer32 read-write
Ingress Frame Discard Threshold. Valid only when Ingress Frame Discard option is selected.
                         bbChanClpHiThreshold 1.3.6.1.4.1.351.110.5.2.7.1.1.1.22 integer32 read-write
Ingress CLP High Threshold. Default is 3/4 of max cell count.
                         bbChanClpLoThreshold 1.3.6.1.4.1.351.110.5.2.7.1.1.1.23 integer32 read-write
Ingress CLP Low Threshold. Valid only when Ingress CLP Hysteresis option is selected. Default Value is 1/2 of max cell count.
                         bbChanCongstUpdateCode 1.3.6.1.4.1.351.110.5.2.7.1.1.1.24 integer read-write
Ingress Channel Congestion Update Code. Enumeration: 'setEfciBit': 3, 'setCiBit': 2, 'dontUpdate': 1, 'clearEfciBit': 4.
                         bbChanMaxCellMemThreshold 1.3.6.1.4.1.351.110.5.2.7.1.1.1.25 integer32 read-write
Maximum number of cells of that connection in the memory. Assuming Total Cell Memory is 512K cells, this is defaulted to half of total size.
                         bbChanIngrPercentUtil 1.3.6.1.4.1.351.110.5.2.7.1.1.1.26 integer32 read-write
Percentage Utilization of the IngrService Rate. This is used for connection admission control.
                         bbChanEgrPercentUtil 1.3.6.1.4.1.351.110.5.2.7.1.1.1.27 integer32 read-write
Percentage Utilization of the EgrService Rate. This is used for egress bandwidth calculation and connection admission control.
                         bbChanEgrSrvRate 1.3.6.1.4.1.351.110.5.2.7.1.1.1.28 integer32 read-write
Egress service rate - This is used for egress bandwidth calculation and for connection admission control. The actual value depends on the speed of the logical interface.
                         bbChanOvrSubOvrRide 1.3.6.1.4.1.351.110.5.2.7.1.1.1.29 integer read-write
Channel Over Subscrive Override This MIB variable allows one to add a new connection on a port even if it is over subscribed. Enumeration: 'enable': 2, 'disable': 1.
                         bbChanLocalVpi 1.3.6.1.4.1.351.110.5.2.7.1.1.1.30 integer32 read-only
The VPI value for this channel.
                         bbChanLocalVci 1.3.6.1.4.1.351.110.5.2.7.1.1.1.31 integer32 read-only
The VCI value for this channel.
                         bbChanLocalNsapAddr 1.3.6.1.4.1.351.110.5.2.7.1.1.1.32 ifnsapaddress read-write
The Near End NSAP Address value for this channel.
                         bbChanRemoteVpi 1.3.6.1.4.1.351.110.5.2.7.1.1.1.33 integer32 read-write
The VPI value for this channel.
                         bbChanRemoteVci 1.3.6.1.4.1.351.110.5.2.7.1.1.1.34 integer32 read-write
The VCI value for this channel.
                         bbChanRemoteNsapAddr 1.3.6.1.4.1.351.110.5.2.7.1.1.1.35 ifnsapaddress read-write
The Far End NSAP Address value for this channel.
                         bbChanMaster 1.3.6.1.4.1.351.110.5.2.7.1.1.1.36 integer read-write
This is used by the PXM switch platform module, to determine if this endpoint ia master or slave. Enumeration: 'slave': 2, 'master': 1, 'unknown': 3.
                         bbChanRtePriority 1.3.6.1.4.1.351.110.5.2.7.1.1.1.37 integer32 read-write
This is also known as class of service, it is used by PXM to determine how important this connection is when selecting connections to route.
                         bbChanMaxCost 1.3.6.1.4.1.351.110.5.2.7.1.1.1.38 integer32 read-write
Maximum allowed cost. It is related to Cost Based Routing. This is used by PXM so that it won't choose a path with a cost greater than this configured level.
                         bbChanRestrictTrkType 1.3.6.1.4.1.351.110.5.2.7.1.1.1.39 integer read-write
Restricted trunk type for routind, used by PXM. It specifies that the connection either cannot be routed over satellite trunks or terrestrial trunks, or it can be on any type of trunk. Enumeration: 'terrestrialTrunk': 2, 'noRestriction': 1, 'satelliteTrunk': 3.
                         bbChanTestType 1.3.6.1.4.1.351.110.5.2.7.1.1.1.40 integer read-write
The chanTestType starts testing the continuity or delay of a connection. It sends specific cell patterns toward the network and the terminating end of this connection has to be an AXIS or ASI of a BPX in order for this test to be working. The receiving node would loop back when it receives these cells. The test should be done in about couple of seconds. testcon(1) : The testcon tests the continuity of the connection and testdelay uses the same test except that it measures for delay through the network. To test the delay follow this procedure: a- set chanTestType to testdelay b- read chanTestState till it is Pass or Fail c- Read chanTestResult for the delay if it is Pass * Note that the chanTestType would go back to notest when the test is completed To test the continuity follow this procedure: a- set chanTestType to testcon b- read chanTestState till it is Pass or Fail * Note that the chanTestType would go back to notest when the test is completed You CAN NOT select 2 tests back to back, you have to select one and wait for the result and then start the other one. Enumeration: 'testdelay': 2, 'notest': 3, 'testcon': 1.
                         bbChanTestState 1.3.6.1.4.1.351.110.5.2.7.1.1.1.41 integer read-only
This object provides the state of the test performed on a connection. When you add a connection then the chanTestState becomes notinprogress and when you select any test, it would go to inprogress state and after it completes the test, it will go to failed or passed state. 1 = Passed 2 = Failed 3 = In Progress 4 = Not In Progress Enumeration: 'failed': 2, 'inprogress': 3, 'notinprogress': 4, 'passed': 1.
                         bbChanTestResult 1.3.6.1.4.1.351.110.5.2.7.1.1.1.42 integer32 read-only
This is round trip delay in milliseconds. When you select testdelay option for the chanTestType, the result of the test that is measured in milliseconds can be read in chanTestResult.
                         bbChanTestTypeCPESide 1.3.6.1.4.1.351.110.5.2.7.1.1.1.43 integer read-write
The chanTestType starts testing the segment continuity of a connection. It sends OAM Segment loopback cell towards port side (CPE) The CPE would loop back the cell To test the continuity follow this procedure: a- set chanTestTypeCPEside to testconseg b- read chanTestState till it is Pass or Fail *Note that the chanTestType would go back to notest when the test is completed. Enumeration: 'testconseg': 1, 'notest': 2.
                         bbChanTestStateCPESide 1.3.6.1.4.1.351.110.5.2.7.1.1.1.44 integer read-only
This shows the state of the test When you add a connection then the chanTestState becomes notinprogress and when you select any test, it would go to inprogress state and after it completes the test, it will go to failed or passed state. 1 = Passed 2 = Failed 3 = In Progress 4 = Not In Progress Enumeration: 'failed': 2, 'inprogress': 3, 'notinprogress': 4, 'passed': 1.
                         bbConnVpcFlag 1.3.6.1.4.1.351.110.5.2.7.1.1.1.45 integer read-write
This represents the connection type, used for PXM to identify VPC/VCC. Enumeration: 'vcc': 2, 'vpc': 1.
                         bbConnServiceType 1.3.6.1.4.1.351.110.5.2.7.1.1.1.46 integer read-write
This specifies the service type 1 ==> Constant Bit Rate 2 ==> Variable Bit Rate 4 ==> Unspecified Bit Rate 6 ==> Available Bit Rate ( standard ) 8 ==> Variable Bit Rate - Real-Time Note that this is used by PXM card, Also to make it compatible with existing AUSM MIB definition, value 3 is not used. foresight ABR is not supported in PXM , i.e Virtual Service Module Enumeration: 'cbr': 1, 'vbr': 2, 'abrstd': 6, 'ubr': 4, 'vbrrt': 8.
                         bbConnPCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.47 integer32 read-write
Peak cell rate, could be derived from the end point parameter
                         bbConnSCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.48 integer32 read-write
Sustained cell rate, could be derived from the end point parameter
                         bbConnPercentUtil 1.3.6.1.4.1.351.110.5.2.7.1.1.1.49 integer32 read-write
This is the expected long-term utilization of the channel by this end-point.
                         bbRemoteConnPCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.50 integer32 read-write
Peak cell rate of the other end, if not set, will be set to the same as local end PCR (bbChanUpcPCR). However, note that if the PCRs for both local and remote end are set to the different value (i.e., asymmetric conn), then this should be set differently from local end PCR.
                         bbRemoteConnSCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.51 integer32 read-write
Sustained cell rate of the other end, if not set, will be set to the same as local end SCR (bbChanUpcSCR). However, note that if the PCRs for both local and remote end are set to the different value (i.e., asymmetric conn), then this should be set differently from local end SCR.
                         bbRemoteConnPercentUtil 1.3.6.1.4.1.351.110.5.2.7.1.1.1.52 integer32 read-write
This is the expected long-term utilization of the channel by this end-point. If this is not specified in the connection setup request, it'll be defaulted to 100 percent
                         bbChanUpcMCR 1.3.6.1.4.1.351.110.5.2.7.1.1.1.53 integer32 read-write
SCR, Sustainable Cell Rate, is an upper bound on the conforming average rate of an ATM connection, over time scales which are long relative to those for which the PCR is defined. Enforcement of this bound by the UPC could allow the network to allocate sufficient resources, but less than thos based on the PCR, and still ensure that the performance objectives (e.g., Cell Loss Ratio) can be achieved. . Units: cell per second. . Applicable connection types: . ABR . Ranges: T3 : 50-96000 E3 : 50-80000 OC3 : 50-353208 OC12: 50-1412832 . Default: 50
                 bbChanNumNextAvailable 1.3.6.1.4.1.351.110.5.2.7.1.2 integer32 read-only
This variable contains the next unused channel number of the possible 4096 . This number can be used in channel config table. ChanNumNextAvailable gets updated whenever this number is used to create a new logical channel. Value 0 for this variable indicates that no more channels are available.
                 bbChanVpIdNextAvailable 1.3.6.1.4.1.351.110.5.2.7.1.3 integer32 read-only
This in only valid for a Service Module, will NOT be used in PXM. This variable contains the next unused local VPId of the possible 1 to 4095. This number can be used in channel config table. It gets updated if the number is used to create a new vp connection. The max. no. of VP conn.s is limited to the VPI range configured for this logical interface. Value of 0 for this variable indicates that no more vp connections are available
                 bbChanStateGrpTable 1.3.6.1.4.1.351.110.5.2.7.2.1 no-access
The Broadband Channel state table is for a channel on logical interface. There will an entry for each of the channel added on the logical partition of the physical line.
                     bbChanStateGrpEntry 1.3.6.1.4.1.351.110.5.2.7.2.1.1 no-access
The state table is for logical channel. The available number of channels on the broadband interface (user ports) on the PXM card is restricted to 4K. The PXM card has 2 Queue Engines ( QE0 and QE1). Current calculations allow 31954 GLCNs on QE0, and 31748 GLCNs on QE1.
                         bbChanStateNum 1.3.6.1.4.1.351.110.5.2.7.2.1.1.1 integer32 read-only
Refers to the logical channel number.
                         bbChanState 1.3.6.1.4.1.351.110.5.2.7.2.1.1.2 integer read-only
This variable indicates the state of the VC (channel). Enumeration: 'alarm': 3, 'notconfigured': 1, 'normal': 2.
                         bbChanEgrXmtState 1.3.6.1.4.1.351.110.5.2.7.2.1.1.3 integer read-only
Indicates the status of port transmit(Egress). Enumeration: 'sendingAis': 3, 'other': 1, 'sendingFerf': 4, 'normal': 2.
                         bbChanIngrRcvState 1.3.6.1.4.1.351.110.5.2.7.2.1.1.4 integer read-only
indicates the status of port receive(Ingress). Enumeration: 'alarm': 5, 'other': 1, 'receivingFerf': 4, 'receivingAis': 3, 'normal': 2.
 ciscoWanBbifAtmConnMIB 1.3.6.1.4.1.351.150.35
The MIB module to configure the ATM Connections on a broad band interface in PXM1 Service module.
       cwbAtmConnMIBConformance 1.3.6.1.4.1.351.150.35.2
           cwbAtmConnMIBGroups 1.3.6.1.4.1.351.150.35.2.1
               cwbAtmConnGroup 1.3.6.1.4.1.351.150.35.2.1.1
A collection of objects providing information applicable to an ATM Connection on broad band interfaces.
               cwbAtmConnStateGroup 1.3.6.1.4.1.351.150.35.2.1.2
A collection of objects related to state of ATM Connections on Broad band interface.
               cwbAtmConnGeneralGroup 1.3.6.1.4.1.351.150.35.2.1.3
A collection of objects related to next available channeli number and next available VPI value of connections supported.
           cwbAtmConnMIBCompliances 1.3.6.1.4.1.351.150.35.2.2
               cwbAtmConnCompliance 1.3.6.1.4.1.351.150.35.2.2.1
The compliance statement for SNMP entities which support Frame realy connection MIB.