AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Stratacom » CISCO-WAN-BBIF-ATM-CONN-MIB » Objects

CISCO-WAN-BBIF-ATM-CONN-MIB.mib object view, vendor Stratacom

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-WAN-BBIF-ATM-CONN-MIB and use it to monitor vendor specific OID's.

CISCO-WAN-BBIF-ATM-CONN-MIB file content

Object view of CISCO-WAN-BBIF-ATM-CONN-MIB:

Scalar Object
bbChanCnfGrpEntry .1.3.6.1.4.1.351.110.5.2.7.1.1.1
The config table is for logical channel.
bbChanNumNextAvailable .1.3.6.1.4.1.351.110.5.2.7.1.2
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
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
bbChanStateGrpEntry .1.3.6.1.4.1.351.110.5.2.7.2.1.1
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.
Tabular Object
bbChanCnfNum .1.3.6.1.4.1.351.110.5.2.7.1.1.1.1
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
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.
bbChanConnType .1.3.6.1.4.1.351.110.5.2.7.1.1.1.3
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.
bbChanServiceType .1.3.6.1.4.1.351.110.5.2.7.1.1.1.4
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.
bbChanConnDesc .1.3.6.1.4.1.351.110.5.2.7.1.1.1.5
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
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
bbChanSvcConnId .1.3.6.1.4.1.351.110.5.2.7.1.1.1.7
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
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
VPI for the connection.
bbChanVci .1.3.6.1.4.1.351.110.5.2.7.1.1.1.10
VCI for the connection.
bbChanUpcEnable .1.3.6.1.4.1.351.110.5.2.7.1.1.1.11
enables/disables UPC for Ingress cells.
bbChanUpcPCR .1.3.6.1.4.1.351.110.5.2.7.1.1.1.12
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
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
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
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
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.
bbChanGcra2Action .1.3.6.1.4.1.351.110.5.2.7.1.1.1.17
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.
bbChanUpcSCRPolicing .1.3.6.1.4.1.351.110.5.2.7.1.1.1.18
Selects SCR policing for CLP = 0 or all cells.
bbChanEfciThreshold .1.3.6.1.4.1.351.110.5.2.7.1.1.1.19
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
Enable Frame Discard or CLP Hysteresis.
bbChanFrmDiscardThreshold .1.3.6.1.4.1.351.110.5.2.7.1.1.1.21
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
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
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
Ingress Channel Congestion Update Code.
bbChanMaxCellMemThreshold .1.3.6.1.4.1.351.110.5.2.7.1.1.1.25
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
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
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
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
Channel Over Subscrive Override This MIB variable allows one to add a new connection on a port even if it is over subscribed.
bbChanLocalVpi .1.3.6.1.4.1.351.110.5.2.7.1.1.1.30
The VPI value for this channel.
bbChanLocalVci .1.3.6.1.4.1.351.110.5.2.7.1.1.1.31
The VCI value for this channel.
bbChanLocalNsapAddr .1.3.6.1.4.1.351.110.5.2.7.1.1.1.32
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
The VPI value for this channel.
bbChanRemoteVci .1.3.6.1.4.1.351.110.5.2.7.1.1.1.34
The VCI value for this channel.
bbChanRemoteNsapAddr .1.3.6.1.4.1.351.110.5.2.7.1.1.1.35
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
This is used by the PXM switch platform module, to determine if this endpoint ia master or slave.
bbChanRtePriority .1.3.6.1.4.1.351.110.5.2.7.1.1.1.37
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
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
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.
bbChanTestType .1.3.6.1.4.1.351.110.5.2.7.1.1.1.40
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.
bbChanTestState .1.3.6.1.4.1.351.110.5.2.7.1.1.1.41
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
bbChanTestResult .1.3.6.1.4.1.351.110.5.2.7.1.1.1.42
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
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.
bbChanTestStateCPESide .1.3.6.1.4.1.351.110.5.2.7.1.1.1.44
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
bbConnVpcFlag .1.3.6.1.4.1.351.110.5.2.7.1.1.1.45
This represents the connection type, used for PXM to identify VPC/VCC.
bbConnServiceType .1.3.6.1.4.1.351.110.5.2.7.1.1.1.46
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
bbConnPCR .1.3.6.1.4.1.351.110.5.2.7.1.1.1.47
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
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
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
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
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
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
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
bbChanStateNum .1.3.6.1.4.1.351.110.5.2.7.2.1.1.1
Refers to the logical channel number.
bbChanState .1.3.6.1.4.1.351.110.5.2.7.2.1.1.2
This variable indicates the state of the VC (channel).
bbChanEgrXmtState .1.3.6.1.4.1.351.110.5.2.7.2.1.1.3
Indicates the status of port transmit(Egress).
bbChanIngrRcvState .1.3.6.1.4.1.351.110.5.2.7.2.1.1.4
indicates the status of port receive(Ingress).
Table
bbChanCnfGrpTable .1.3.6.1.4.1.351.110.5.2.7.1.1
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
bbChanStateGrpTable .1.3.6.1.4.1.351.110.5.2.7.2.1
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.
Object Identifier
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
cwbAtmConnMIBCompliances .1.3.6.1.4.1.351.150.35.2.2
Group
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.