LS100-R3-MIB

File: LS100-R3-MIB.mib (33816 bytes)

Imported modules

RFC1155-SMI RFC-1212

Imported symbols

enterprises Counter OBJECT-TYPE

Defined Types

DisplayString  
OCTET STRING Size(0..255)    

NodeIfConfEntry  
SEQUENCE    
  nodeIfConfIndex INTEGER
  nodeIfConfPhysType INTEGER
  nodeIfConfRev DisplayString
  nodeIfConfStatus INTEGER

LinfStatusEntry  
SEQUENCE    
  linfIndex INTEGER
  linfStatus INTEGER
  linfConf INTEGER
  linfFwdAvailableBandWidth INTEGER
  linfBkwdAvailableBandWidth INTEGER

ConnPvcEntry  
SEQUENCE    
  connPvcIndex INTEGER
  connPvcTopology INTEGER
  connPvcTrafficType INTEGER
  connPvcLowIfIndex INTEGER
  connPvcLowVPI INTEGER
  connPvcLowVCI INTEGER
  connPvcLowUpcParam INTEGER
  connPvcLowUpc INTEGER
  connPvcLowThroughput INTEGER
  connPvcHighIfIndex INTEGER
  connPvcHighVPI INTEGER
  connPvcHighVCI INTEGER
  connPvcHighUpcParam INTEGER
  connPvcHighUpc INTEGER
  connPvcHighThroughput INTEGER
  connPvcLowInCells Counter
  connPvcHighOutCells Counter
  connPvcHighInCells Counter
  connPvcLowOutCells Counter
  connPvcLowUpcViolatedCells Counter
  connPvcHighUpcViolatedCells Counter
  connPvcRowStatus INTEGER
  connPvcCause INTEGER
  connPvcKind INTEGER

PerfIfEntry  
SEQUENCE    
  perfIfIndex INTEGER
  perfIfLcvs Counter
  perfIfParitySections Counter
  perfIfParityLines Counter
  perfIfParityPaths Counter
  perfIfHecErrors Counter
  perfIfMisDelivdCells Counter
  perfIfOverFlowCells Counter
  perfIfInCBRCells Counter
  perfIfOutCBRCells Counter
  perfIfInVBRCells Counter
  perfIfOutVBRCells Counter
  perfIfInUBRCells Counter
  perfIfOutUBRCells Counter

Defined Values

nec 1.3.6.1.4.1.119
OBJECT IDENTIFIER    

nec-mib 1.3.6.1.4.1.119.2
OBJECT IDENTIFIER    

necProductDepend 1.3.6.1.4.1.119.2.3
OBJECT IDENTIFIER    

atomis-mib 1.3.6.1.4.1.119.2.3.14
OBJECT IDENTIFIER    

m5core-mib 1.3.6.1.4.1.119.2.3.14.3
OBJECT IDENTIFIER    

node 1.3.6.1.4.1.119.2.3.14.3.1
OBJECT IDENTIFIER    

linf 1.3.6.1.4.1.119.2.3.14.3.2
OBJECT IDENTIFIER    

conn 1.3.6.1.4.1.119.2.3.14.3.3
OBJECT IDENTIFIER    

perf 1.3.6.1.4.1.119.2.3.14.3.4
OBJECT IDENTIFIER    

nodeOperStatus 1.3.6.1.4.1.119.2.3.14.3.1.1
Operational status of the LS100.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER down(1), active(2), offLine(3), testing(4), initializing(5)  

nodeIfConfTable 1.3.6.1.4.1.119.2.3.14.3.1.2
The configuration of the line cards.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    NodeIfConfEntry

nodeIfConfEntry 1.3.6.1.4.1.119.2.3.14.3.1.2.1
The configuration of a line card.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  NodeIfConfEntry  

nodeIfConfIndex 1.3.6.1.4.1.119.2.3.14.3.1.2.1.1
The index of the table. Same as ifIndex.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

nodeIfConfPhysType 1.3.6.1.4.1.119.2.3.14.3.1.2.1.2
The PMD/physical layer format of the line card.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER other(1), sar(2), taxi100M(3), oc3cSMF(4), oc3cMMF(5), ds3PlcpScramble(6), ds3PlcpNoScramble(7), relay6Mcell(8), ds3Scramble(9), ds3NoScramble(10), e3PlcpScramble(11), e3PlcpNoScramble(12), e3Scramble(13), e3NoScramble(14), utp5(15), leasedLine3M(16), leasedLine4M(17), leasedLine6M(18), utp5classB(19), oc3cSmfShaper(20), taxi140M(21), notInstalled(99)  

nodeIfConfRev 1.3.6.1.4.1.119.2.3.14.3.1.2.1.3
The revision of the line cards.
Status: mandatory Access: read-only
OBJECT-TYPE    
  DisplayString  

nodeIfConfStatus 1.3.6.1.4.1.119.2.3.14.3.1.2.1.4
Operational status of the line card.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER other(1), inService(2), outOfService(3), testing(4), localLoopBack(5), remoteLoopBack(6), notInstalled(99)  

nodeFanStatus 1.3.6.1.4.1.119.2.3.14.3.1.3
Operational status of the Fan.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2)  

nodeUpcWindowSize 1.3.6.1.4.1.119.2.3.14.3.1.4
UPC window size. Integer Wi represents Wi X 512 cell time. Wi=1 correspond to 1.4msec. Wi=120 correspond to 168msec. It is not allowed to change window size when any PVC exists.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..120  

nodeBestEffortBufferSize 1.3.6.1.4.1.119.2.3.14.3.1.5
Input buffer capacity for Best Effort traffic(Bb). The number of cells stored in the buffer is Bb X 128. The default value is 8. The sum of the buffer capacity is 2047 cells.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..16  

nodeGuaranteedBufferSize 1.3.6.1.4.1.119.2.3.14.3.1.6
Input buffer capacity for Guaranteed traffic(Bg). The number of cells stored in the buffer is Bg X 128. The default value is 0. The sum of the buffer capacity is 2047 cells.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..16  

nodeBestEffortBufferThreshold 1.3.6.1.4.1.119.2.3.14.3.1.7
Threshold buffer capacity for Best Effort traffic. If the number of cells stored in the buffer exceeds this threshold, cells with CLP=1 and traffic defined as UBR will be discarded.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..16  

nodeGuaranteedBufferThreshold 1.3.6.1.4.1.119.2.3.14.3.1.8
Threshold buffer capacity for Guaranteed traffic. If the number of cells stored in the buffer exceeds this threshold, cells with CLP=1 and traffic defined as VBR will be discarded.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..16  

nodeSaveConf 1.3.6.1.4.1.119.2.3.14.3.1.9
Save system configuration information including the PVC table to the non-volatile memory. Writing a value of save(1) saves the configiration data. Writing the value noOperation(2) has no effect. When read, this object always has the value noOperation(2).
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER save(1), noOperation(2)  

nodeSaveResult 1.3.6.1.4.1.119.2.3.14.3.1.10
Indicates the result of the save command issued from NMS. The result is either success/temporary failure/notReady.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER temporaryFailure(1), notReady(2), ready(3), success(4), nearend(5)  

nodeReset 1.3.6.1.4.1.119.2.3.14.3.1.11
Writing the value reset(1) resets the system. Writing the value noOperation(2) has no effect. When read, this object always has the value noOperation(2).
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER reset(1), noOperation(2)  

linfStatusTable 1.3.6.1.4.1.119.2.3.14.3.2.1
Status of the line cards including ATM specific information.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    LinfStatusEntry

linfStatusEntry 1.3.6.1.4.1.119.2.3.14.3.2.1.1
Status of a line card including ATM specific information.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  LinfStatusEntry  

linfIndex 1.3.6.1.4.1.119.2.3.14.3.2.1.1.1
Same as ifIndex
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..64  

linfStatus 1.3.6.1.4.1.119.2.3.14.3.2.1.1.2
Status of line interface
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER normal(1), los(2), lof(3), loc(4), ais(5), yellowLine(6), yellowPath(7), lop(8), idle(9), yellowAlarm(10), plcpLOF(11), plcpYellow(12), maFERF(13), rai(14), payloadAllOnes(15), notInstalled(99)  

linfConf 1.3.6.1.4.1.119.2.3.14.3.2.1.1.3
Line card type.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER publicUNI(1), privateUNI(2), privateNNI(3), others(99)  

linfFwdAvailableBandWidth 1.3.6.1.4.1.119.2.3.14.3.2.1.1.4
The amount of bandwidth (Mbps) available/unallocated in the forward (incoming) direction.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

linfBkwdAvailableBandWidth 1.3.6.1.4.1.119.2.3.14.3.2.1.1.5
The amount of bandwidth (Mbps) available/unallocated in the backward (outgoing) direction.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

connPvcIndexNext 1.3.6.1.4.1.119.2.3.14.3.3.1
The next available index for a row of the connPvcTable.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..8191  

connPvcIndexEnable 1.3.6.1.4.1.119.2.3.14.3.3.2
When read, this object is the current minimum value of an index in the connPvcTable. Writing this value has no effect.
Status: deprecated Access: read-write
OBJECT-TYPE    
  INTEGER 0..8191  

connPvcTable 1.3.6.1.4.1.119.2.3.14.3.3.3
The table containing information on current PVC/SVCs. Currently, only PVCs are represented in this table. The table is also used to establish and delete PVCs. 1. PVC establishment procedure (1) Read connPvcIndexNext. This value is used as the value of connPvcIndex for the new connection. (2) Determine the value of connPvcHighIfIndex. When creating a new point-to-multipoint connection, connPvcHighIfIndex must identify the first leaf. When creating a new point-to-point connection, connPvcHighIfIndex normally identifies the interface with the higher value of ifIndex. (3) Set connPvcRowStatus to 'createAndWait' using the values of connPvcIndex and connPvcHighIfIndex as indexes. This causes the switch to create the new row with some objects being set to default values. The parameters for which there is no reasonable default are set to 0xffffffff. Object Default connPvcTopology bidirectionalVCC(2) connPvcTrafficType trafficUBR(4) connPvcLowIfIndex 0xffffffff connPvcLowVPI 0xffffffff connPvcLowVCI 0xffffffff connPvcLowUpcParam 512 connPvcLowUpc pass(1) connPvcLowThroughput 0 connPvcHighVPI 0xffffffff connPvcHighVCI 0xffffffff connPvcHighUpcParam 512 connPvcHighUpc pass(1) connPvcHighThroughput 0 The switch then sets the value of connPvcRowStatus to 'notReady'. The default values can be read by the NMS. (4) The values of the above objects which are set to 0xffffffff must be modified, and the values of any other objects can be changed. When establishing a VP connection, connPvcLowVCI and connPvcHighVCI should be set to 0. When connPvcTrafficType is set to trafficUBR, the values of connPvcLowThroughput and connPvcHighThroughput are ignored. When all parameters have acceptable values, the switch sets connPvcRowStatus to 'notInService'. (5) When the NMS sets connPvcRowStatus to 'active', the switch validates each parameter's value, and tries to establish the connection. If this operation fails, the the cause of the failure is indicated by the value of connPvcCause. At present, the switch allows connPvcRowStatus to have a value of notReady or notInService for only one row at a time. 2. Adding a new leaf to an existing pt-to-mpt connection (1) Determine the value of connPvcIndex for the existing point-to-multipoint connection to which a new leaf is to be added. (2) Determine the value of connPvcHighIfIndex as the ifIndex value of the interface to be used for the new leaf. (3) Set connPvcRowStatus to 'createAndWait' using the values of connPvcIndex and connPvcHighIfIndex as indexes. This causes the switch to create the new leaf with some objects being set to default values. The parameters for which there is no reasonable default are set to 0xffffffff. Object Default connPvcHighVPI 0xffffffff connPvcHighVCI 0xffffffff connPvcHighUpcParam 512 connPvcHighUpc pass(1) connPvcHighThroughput 0 The switch then sets the value of connPvcRowStatus to 'notReady'. The default values can be read by the NMS. (4) The NMS must modify the values of connPvcHighVPI and connPvcHighVCI, and can modify the values of connPvcHighUpc, connPvcHighUpcParam and connPvcHighThroughput. When establishing a VP connection, connPvcHighVCI should be set to 0. The NMS should not change the values of the following objects: connPvcTopology connPvcTrafficType connPvcLowIfIndex connPvcLowVPI connPvcLowVCI connPvcLowUpcParam connPvcLowUpc connPvcLowThroughput When all parameters have acceptable values, the switch sets connPvcRowStatus to 'notInService'. (5) When the NMS sets connPvcRowStatus to 'active', the switch validates each parameter's value, and tries to add the new leaf to the original connection. If this operation fails, the cause of the failure is indicated by the value of connPvcCause. 3. PVC deletion procedure (1) Set the connPvcRowStatus to 'destroy'. If the row exists but is impossible to delete, the cause of the failure is indicated by the value of connPvcCause. If the deletion is successful, the row is deleted (including the instance of connPvcCause for that row). Notes: - a row representing a terminating VP will not have instances of the following objects: connPvcLowUpc, connPvcLowUpcParam, connPvcLowThroughput, connPvcHighUpc, connPvcHighUpcParam, connPvcHighThroughput, connPvcLowOutCells, connPvcHighInCells, connPvcHighUpcViolatedCells, connPvcLowInCells, connPvcHighOutCells, and connPvcLowUpcViolatedCells. - a row representing a connection between the gateway-PAD (the switch's internal port) and a line interface will not have instances of the following objects: connPvcLowUpc, connPvcLowUpcParam, connPvcLowThroughput, connPvcHighUpc, connPvcHighUpcParam, connPvcHighThroughput, connPvcHighOutCells, connPvcHighInCells, and connPvcHighUpcViolatedCells.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ConnPvcEntry

connPvcEntry 1.3.6.1.4.1.119.2.3.14.3.3.3.1
A row in the table is used to show the current PVC/SVCs.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  ConnPvcEntry  

connPvcIndex 1.3.6.1.4.1.119.2.3.14.3.3.3.1.1
A unique value to identify this point-to-point or point-to-multipoint connection. A point-to-multipoint connection has multiple rows in this table, one for each leaf, each one having the same value of this object.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 0..8191  

connPvcTopology 1.3.6.1.4.1.119.2.3.14.3.3.3.1.2
Topology of the connection.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER uniDirectionalVCC(1), biDirectionalVCC(2), uniDirectionalVPC(3), biDirectionalVPC(4), broadcastVPC(5), broadcastVCC(6), gateway(7), vpterm(8)  

connPvcTrafficType 1.3.6.1.4.1.119.2.3.14.3.3.3.1.3
Traffic Type.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER trafficCBR(1), trafficVBR(2), trafficUBR(4)  

connPvcLowIfIndex 1.3.6.1.4.1.119.2.3.14.3.3.3.1.4
The line interface number (ifIndex) of the low port. Normally, the low port has a lower ifIndex value than the high port. However, for point-to-multipoint connections, the root is always the low port, regardless of whether it is greater or smaller than the port numbers of individual leaves.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 1..16  

connPvcLowVPI 1.3.6.1.4.1.119.2.3.14.3.3.3.1.5
VPI value of the connection on the low port.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

connPvcLowVCI 1.3.6.1.4.1.119.2.3.14.3.3.3.1.6
VCI value of the connection on the low port.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

connPvcLowUpcParam 1.3.6.1.4.1.119.2.3.14.3.3.3.1.7
Number of cells allowed to be sent in the unit cell time (512 cell times).
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..512  

connPvcLowUpc 1.3.6.1.4.1.119.2.3.14.3.3.3.1.8
The action to take on a UPC violation for this connection on the low port. The tagging action is not supported by current hardware.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER pass(1), discard(2), tagging(3)  

connPvcLowThroughput 1.3.6.1.4.1.119.2.3.14.3.3.3.1.9
Average rate of the connection (Mbps). Direction is from the low port to high port. This parameter is valid for the connection whose traffic type is CBR or VBR.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..622  

connPvcHighIfIndex 1.3.6.1.4.1.119.2.3.14.3.3.3.1.10
The line interface number (ifIndex) of the high port. Normally, the high port has a higher ifIndex value than the low port. However, for point-to-multipoint connections, the root is always the low port, regardless of whether it is greater or smaller than the port numbers of individual leaves. Line interface number 17 corresponds to gateway (the switch's internal port).
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1..17  

connPvcHighVPI 1.3.6.1.4.1.119.2.3.14.3.3.3.1.11
The VPI value of the connection on the high port.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

connPvcHighVCI 1.3.6.1.4.1.119.2.3.14.3.3.3.1.12
The VCI value of the connection on the high port.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER  

connPvcHighUpcParam 1.3.6.1.4.1.119.2.3.14.3.3.3.1.13
Number of cells allowed to be sent in the unit cell time (512 cell times).
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..512  

connPvcHighUpc 1.3.6.1.4.1.119.2.3.14.3.3.3.1.14
The action to take on a UPC violation for this connection on the high port. The tagging action is not supported by current hardware.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER pass(1), discard(2), tagging(3)  

connPvcHighThroughput 1.3.6.1.4.1.119.2.3.14.3.3.3.1.15
Average rate of the connection (Mbps). Direction is from the high port to low port. This parameter is valid for the connection whose traffic type is CBR or VBR.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..622  

connPvcLowInCells 1.3.6.1.4.1.119.2.3.14.3.3.3.1.16
Number of incoming cells on this connection on low port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

connPvcHighOutCells 1.3.6.1.4.1.119.2.3.14.3.3.3.1.17
Number of outgoing cells on this connection on the high port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

connPvcHighInCells 1.3.6.1.4.1.119.2.3.14.3.3.3.1.18
Number of incoming cells on this connection on high port. (Valid for bi-direction connections only).
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

connPvcLowOutCells 1.3.6.1.4.1.119.2.3.14.3.3.3.1.19
Number of outgoing cells on this connection on the low. port. (Valid for bi-direction connections only).
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

connPvcLowUpcViolatedCells 1.3.6.1.4.1.119.2.3.14.3.3.3.1.20
Number of UPC violation cells incoming from the low port.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

connPvcHighUpcViolatedCells 1.3.6.1.4.1.119.2.3.14.3.3.3.1.21
Number of UPC violation cells incoming from the high port. (Valid for bi-direction connections only).
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

connPvcRowStatus 1.3.6.1.4.1.119.2.3.14.3.3.3.1.22
The status of this row. 'active' indicates that the connection is in use. 'notInService' indicates that the row exists but the connection is not established. 'notReady' indicates that the row exists in the agent, but is missing information necessary in order to be established. 'createAndWait' supplied by a management station wishing to create a new row. 'destroy' supplied by a management station wishing to delete the row.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER active(1), notInService(2), notReady(3), createAndWait(5), destroy(6)  

connPvcCause 1.3.6.1.4.1.119.2.3.14.3.3.3.1.23
The result of the PVC establishment/deletion.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER existing(1), vpivciBusy(2), vpivciOutOfRange(3), rateOverFlow(4), upvpOutOfRange(5), broadcastTableFull(6), inconsistentVPVC(7), lineDiagnosis(8)  

connPvcKind 1.3.6.1.4.1.119.2.3.14.3.3.3.1.24
This object identifies the connection is SVC or PVC.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER pvc(1), svc(2)  

perfTrapEnable 1.3.6.1.4.1.119.2.3.14.3.4.1
The status of performance monitoring traps. Its value does not affect other traps, such as coldStart.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

perfIfTable 1.3.6.1.4.1.119.2.3.14.3.4.2
Table of performance monitoring information.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    PerfIfEntry

perfIfEntry 1.3.6.1.4.1.119.2.3.14.3.4.2.1
Performance monitoring information for a specific line.
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  PerfIfEntry  

perfIfIndex 1.3.6.1.4.1.119.2.3.14.3.4.2.1.1
Line interface number. Same as ifIndex.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

perfIfLcvs 1.3.6.1.4.1.119.2.3.14.3.4.2.1.2
Line Code Violation. This object is valid only for DS3/E3.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfParitySections 1.3.6.1.4.1.119.2.3.14.3.4.2.1.3
Number of B1 (BIP) errors(OC-3c, UTP-5), Number of C-bit parity violation(DS3), Number of CRC-6 violation(DS1).
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfParityLines 1.3.6.1.4.1.119.2.3.14.3.4.2.1.4
Number of B2 (BIP) errors(OC-3c, UTP-5), Number of P-bit parity violation(DS3).
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfParityPaths 1.3.6.1.4.1.119.2.3.14.3.4.2.1.5
Number of B3 (BIP) errors(OC-3c, UTP-5), Number of PLCP BIP violation(DS3).
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfHecErrors 1.3.6.1.4.1.119.2.3.14.3.4.2.1.6
Number of HEC errors detected.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfMisDelivdCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.7
Number of misdelivered cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfOverFlowCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.8
Number of cells discarded due to buffer overflow.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfInCBRCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.9
Number of received CBR cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfOutCBRCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.10
Number of transmitted CBR cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfInVBRCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.11
Number of received VBR cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfOutVBRCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.12
Number of transmitted VBR cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfInUBRCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.15
Number of received UBR cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

perfIfOutUBRCells 1.3.6.1.4.1.119.2.3.14.3.4.2.1.16
Number of transmitted UBR cells.
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter