MPLS-CEM-MIB: View SNMP OID List / Download MIB

This MIB contains managed object definitions for Circuit Emulation over MPLS as in: Malis, A., Vogelsang, S., and Martini, L. 'SONET/SDH Circuit Emulation Service Over MPLS (CEM) encapsulation', Internet Draft , February 2001. This MIB is dependant on the MIBs as defined by T. Nadeau, C. Srinivasan, and A. Viswanathan and

This notification is generated when a mplsCemVcOperStatus object for one of the configured CEM VC entries is about to leave the down state and transition into some other state (but not into the notPresent state). This other state is indicated by the included value of mplsCemVcOperStatus.

This notification is generated when a mplsCemVcOperStatus object for one of the configured CEM VC entries is about to enter the down state and transition into some other state (but not from the notPresent state). This other state is indicated by the included value of mplsCemVcOperStatus.

This notification is generated when the CEM VC APS mechanism has initiated a switch from the specified Index/Instance to find a 'good' CEM VC within the same group. To reduce the number of Traps, it is recommended to only generate mplsCemVcApsFrom when first initiating attempt to find a good CEM VC instance. That is, do not generate Traps if the APS mechanism is continuing to switch looking for an CEM VC group member that is good.

This notification is generated when the CEM VC APS mechanism has switched to and settled on a CEM VC Index and Instance that is 'good' (whether from a bad VC or when reverting).

This object contains an appropriate value to be used for mplsCemVcIndex when creating entries in the mplsCemVcTable. The value 0 indicates that no unassigned entries are available. To obtain the value of mplsCemVcIndex for a new entry in the mplsCemVcTable, the manager issues a management protocol retrieval operation to obtain the current value of mplsCemVcIndex. After each retrieval operation, the agent should modify the value to reflect the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.

This table specifies information for connecting SONET paths and MPLS Tunnels.

A row in this table represents a connection for CEM. It is indexed by : - The mplsCemVcIndex. Uniquely identifying a singular CEM connection or a group. If a group, individual CEM connections are identified by the Instance. - The mplsCemVcInstance.

Primary index for the conceptual row identifying a group of CEM VCs.

Uniquely identifies an instance of a CEM VC. It is useful to identify multiple instances for the purpose of backup VCs.

This is a unique index within the ifTable. It represents the interface index for the SONET path. A value of zero indicates an ifIndex that has yet to be configured or has since disappeared.

The incoming and outgoing label for this VC. This value is placed in the Label field of the outgoing MPLS shim header.

Used when resources on a tunnel or backup tunnel are overbooked. The agent (connection admission control) can sort CEM VC entries that share an overbooked tunnel. Lower mplsCemVcPriority values have higher priority. VCs dropped will be set 'dormant' (as indicated in mplsCemVcOperStatus).

The canonical name assigned to the CEM VC. This name can be used to refer to the CEM VC on the LSRs console port.

A textual string containing information about the CEM VC. If there is no description this object contains a zero length string.

System time when theis CEM VC was created.

Number of consecutive ticks this CEM VC has been 'up' as observed in mplsCemVcOperStatus.

Part of set of indexes for inbound tunnel

Part of set of indexes for inbound tunnel

Part of set of indexes for inbound tunnel

Part of set of indexes for inbound tunnel

Part of set of indexes for outbound tunnel

Part of set of indexes for outbound tunnel

Part of set of indexes for outbound tunnel

Part of set of indexes for outbound tunnel

This is the packet or payload length for this CEM VC. It is fixed and applies to inbound and outbound packets carrying user payload. Note: DBA packets have their own length and are not effected by this.

This value is placed in the EXP bit field of the outbound MPLS shim header (with the VC Label). These EXP bits convey to the LSR the PHB to be applied to these packets.

Reports if implementation provides packet re-sequencing. With this, as inbound packets are queued in the jitter buffer, out of order packets are re-sequenced. The maximum sequence number differential (order correction can occur within) is dependant on the depth of the jitter buffer. See mplsCemVcJtrBfrDepth.

Any bits set here MUST enable the DBA (dynamic bandwidth allocation) feature for the specified condition. Setting allOnesOnAis will cause CEM packet payload suppression when AIS is detected on the associated SONET path. Similarly, allZerosOnUnequipped will cause payload suppression when the SONET path is un-equipped. During these conditions, CEM packets will continue to be sent, but with indicators set in the CEM header instructing the remote to play all ones or zeros onto its SONET path. Note: some implementations may not support this feature. Bits: 'allOnesOnAis': 0, 'allZerosOnUnequipped': 1.

This setting configures the number of packet buffers reserved for this CEM VC. (This object would not apply in implementations that support CEM VC groups, but cannot process inbound packets on CEM VCs that are currently in standby.) This object essentially sets the maximum amount of time allowed between CEM packets before the jitter buffer empties. This variable should be set based on the SONET path width (speed) and the amount of delay variation expected to be introduced by the network. Like bandwidth, jitter buffers are likely to be a limited resource to be managed.

These are the actions to take when inbound packets are missing due to gap in sequence numbers (uncorrectable via available re-sequencing), jitter buffer underruns, or packets with bad CEM headers. These patterns are sent (played) on the SONET path. These settings are used for immediate errors and (unless the mplsCemVcDownAction is 'none') are not in effect once the CEM VC is 'down'. Enumeration: 'playAllZeros': 2, 'playAllOnes': 1, 'playPseudoRandom': 3.

These are the actions to take once the CEM VC has been declared 'down' (as observed in mplsCemVcOperStatus). These patterns are sent (played) on the SONET path. See Integration Timers for events causing CEM VC 'down'. If 'errorAction' is selected, then the mplsCemVcErrorAction settings stay in effect even after the CEM VC is 'down'. Enumeration: 'playAllZeros': 3, 'playAllOnes': 2, 'playPseudoRandom': 4, 'errorAction': 1.

See comment above - units are microseconds.

See comment above - units are microseconds.

See comment above - units are microseconds.

See comment above - units are microseconds.

Enables this CEM VC (as part of a group) to be used for APS. A CEM VC group is created when a unique CEM VC index (in mplsCemVcTable) has multiple instances. Setting mplsCemVcApsEnable to 'false' may be useful when a CEM VC is suspect, being debugged, or not fully configured. Note: some implementations may not support APS.

Bits set here represent defects and modes for switching the SONET path from the active CEM VC to another within this VC's group. Defects include: CEM errors (jitter buffer errors, missing packets, bad CEM headers). Separating these CEM defects into individually selectable bits, or adding other types of defect indications (e.g. OAM status) is for future study. Modes: The 'cemErrorStbyOK' mode setting is useful in APS network configurations where CEM traffic is not present on standby inbound VCs. Therefore they are expected to have CEM errors, but are still to be considered as viable switch- over candidates. cemErrorStbyOK essentially masks CEM errors when this CEM VC is in standby. 'revertive' mode is useful for non-preferred CEM VCs where you may want to switch back to a preferred VC that has no defects while the currently active VC also has no defects (see mplsCemVcApsRevertTimer). 'revertive' should NOT be used when standby VCs have no defect indications available. If 'revertive' is not set, then manual reversion is possible by simply setting the active CEM VC's admin status 'down', then 'up'. Preferred should NOT have 'revertive' set. 'hunt' mode is useful when standby VCs offer no defect indications (see mplsCemVcApsHoldOffTimer). 'hunt' should not be used when standby VCs have available defect indications. Hunting assumes standby VCs are good, if not the down timers will determine it's bad, and hunting continues. 'hunt' and 'revertive' are mutually exclusive. Bits: 'cemError': 0, 'hunt': 1024, 'revertive': 512, 'cemErrorStbyOK': 256.

Current state of these CEM VC defects. The cemError indicator is a summary of any error associated with processing inbound CEM packets. Separately displaying CEM errors types (buffer errors, missing packets, and header errors) are for future study. Also other bits here may be defined here to show results of error trend analysis. These bits MUST be aligned with mplsCemVcApsCriteria bits so mplsCemVcApsCriteria can be used as a mask. Note: other defect indications (e.g. from OAM) are for future study. Bits: 'cemError': 0.

Used to hold-off an APS switch after the CEM VC has been determined 'down'. The purpose is to allow potential recovery schemes within lower communications layers a chance to recover. Also useful in 'hunt' mode to hold off switching to the next CEM VC (slows oscillation when all VCs are down).

If this CEM VC is active and 'up', then this timer is used in conjunction with 'revertive' (if set above). The reversion would be delayed for this time.

If part of a CEM VC group, this indicates if the CEM VC has been selected (via APS algorithm/protocol) to connect the associated Tunnel to the SONET path. If not part of a group, then always 'active'. Enumeration: 'active': 1, 'standby': 2.

For use by LDP signaling

For use by LDP signaling

For use by LDP signaling

For use by LDP signaling

If this object is true, generation of mplsCemVcUp and mplsCemVcDown traps aare enabled for this CEM VC, otherwise these traps are not emitted.

The desired operational status of this CEM VC. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

Indicates the actual operational status of this CEM VC. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'unknown': 4, 'testing': 3, 'up': 1, 'down': 2, 'notPresent': 6.

For creating, modifying, and deleting this row.

This variable indicates the storage type for this object.

This table provides per CEM VC performance information. Note: outbound errors are not being considered. It is assumed (at this time) that CEM packets will be forwarded as they are generated. i.e., it is assumed that there are no local outbound packet congestion issues. HC (high capacity) counters are needed for packet counts due to the high speeds expected with CEM. A SONET path of width 48 can rollover a non-HC counter in a few minutes.

An entry in this table is created by the agent for every mplsCemVcEntry. It is an extension to mplsCemVcEntry.

Number of inbound packets received.

Number of outbound packets sent.

Number of DBA packets received.

Number of DBA packets sent.

Number of negative pointer adjustments made on the SONET path based on CEM pointer adjustments received.

Number of postive pointer adjustments made on the SONET path based on CEM pointer adjustments received.

Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEM packets.

Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEM packets.

Number of correctable CEM header errors detected on inbound CEM packets.

Number of uncorrectable CEM header errors detected on inbound CEM packets.

Number of missing packets (as detected via CEM header sequence number gaps).

Number of packets detected out of sequence (via CEM header sequence numbers), but were able to be re-sequenced. That is, the differential in sequence numbers was less than the jitter buffer depth. Note: some implementations may not support this feature (see mplsCemVcPktResequence). Any packets so far out of sequence that a re-sequencer can not correct for would be counted as missing packet.

Number of times the jitter buffer transitioned to empty.

Number of packets received while jitter buffer is full.

The value of sysUpTime on the most recent occasion at which any one or more of this segment's Counter32 or Counter64 suffered a discontinuity. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.

This table maps an inbound Tunnel/VcLabel to a CEM VC.

A row in this table represents the inbound connection between a Tunnel/VcLabel and CEM VC/instance. It is indexed by the same 4 indexes that index the inbound Tunnel, then adds the VC Label as a 5th index. The Tunnel referenced here is in the mplsTunnelTable. - The mplsCemMappingInTunnelIndex uniquely identifies a singular Tunnel or a group. If a group, individual Tunnels are identified by the Instance. - The mplsCemMappingInTunnelInstance. - ID (normally an IP address) for the ingress LSR, mplsCemMappingInTunnelIngressLSR. - ID (normally an IP address) of the Local (egress) LSR, mplsCemMappingInTunnelLocalLSR, - and the VC Label, mplsCemMappingVcLabel.

Primary index for the conceptual row identifying a group of Tunnel/VcLabel to CEM VC mappings.

Uniquely identifies an instance of a mapping

Uniquely identifies an ingress LSR

Uniquely identifies the local LSR

Identifies a unique label on this tunnel

Index for entry (or group of entries, in the case of backup VCs) in the mplsCemVcTable. This value can also be thought of as the Circuit ID.

Identifies a unique member within a CEM VC group. (This could of course be a group of one.)

For creating, modifying, and deleting this row.

This variable indicates the storage type for this object.

This table is an extension to the mplsTunnelTable. This table exists to configure parameters useful for CEM APS.

A row in this table represents a Tunnel used for CEM VCs. The Tunnel referenced here is in the mplsTunnelTable. It is indexed by the same 4 indexes of the inbound Tunnel: - The mplsCemTunnelExtIndex uniquely identifies a singular Tunnel or a group. If a group, individual Tunnels are identified by the Instance. - The mplsCemTunnelExtInstance. - ID (normally an IP address) for the ingress LSR, mplsCemTunnelExtIngressLSR. - ID (normally an IP address) of the Local (egress) LSR, mplsCemTunnelExtLocalLSR. In the mplsTunnelTable, this index would be referred to as the Egress LSR ID. Since CEM is always at a tunnel termination, the egress LSR is always the local (edge) LSR. The local agent creates an entry here for every entry created in the mplsCemMappingTable.

Enables this Tunnel (as part of a group) to be used for APS. Remember a Tunnel group is created when a unique Tunnel index (in mplsTunnelTable) has multiple instances. Tunnel disabling may be useful when a Tunnel is suspect, being debugged, or not fully configured. Note: some implementations may not support APS.

Bits set here represent defects and modes for switching all VCs within this Tunnel to another Tunnel that has no APS defects. Currently, only CEM defects are available. Separating and individually selecting CEM defects (buffer errors, header errors, etc.) is for future study. Also, for future study: determining a Tunnel's state of usefulness via other indications (such as OAM). If 'cemVcCriteria' is set, mplsCemTunnelExtApsViaCemVc is used to index the CEM VC for which defects are included. The purpose of this is in situations when CEM VCs can generate better defects than Tunnels (for example: buffer errors). Revertive and Hunt modes: 'revertive' is useful for non-primary Tunnels where you may want to switch back to a primary Tunnel that has no defects while the currently active also has no defects (see mplsCemTunnelExtApsRevertTimer). 'revertive' should NOT be used when standby Tunnels have no available defect indications. If 'revertive' is not set, then manual reversion is possible by simply setting the active Tunnel's admin status 'down', then 'up'. 'hunt' is useful when standby Tunnels offer no defect indications (see mplsCemTunnelExtApsHoldOffTimer). 'hunt' should not be used when standby Tunnels have available defect indications. Hunting assumes standby Tunnels are good, if not the down timers will determine it's bad, and hunting continues. 'hunt' and 'revertive' are mutually exclusive. Note: criteria defect bits here MUST align with mplsCemTunnelExtDefects so it can be used as a mask. Bits: 'hunt': 1024, 'revertive': 512, 'cemVcCriteria': 0.

Current state of Tunnel defect indications. Other bits here may be defined here to show results of error trend analysis. Note: These bits MUST be aligned with mplsCemTunnelExtApsCriteria bits so mplsCemTunnelExtApsCriteria can be used as a mask. Note: other defect indications (e.g. from OAM) are for future study. Bits: 'cemVcCriteria': 0.

Primarily used to hold-off an APS switch after the Tunnel has been determined 'down'. The purpose is to allow potential recovery schemes within lower communications layers a chance to recover. Also useful in 'hunt' mode to hold off switching to the next Tunnel (slows oscillation when all Tunnels are down).

If this Tunnel is active and 'up', then this timer is used in conjunction with 'revertive' (if set above). The reversion would be delayed for this time.

Index of the CEM VC from which APS defect criteria are included with this Tunnel's APS criteria.

Instance of the CEM VC from which APS defect criteria are included with this Tunnel's APS criteria.

This variable indicates the storage type for this object.

This table is an extension to the mplsTunnelTable. It provides per Tunnel performance information.

An entry in this table is created by the agent for every mplsCemTunnelExtEntry. It is an extension to mplsCemTunnelExtEntry.

Number of packets with unexpected labels received. This count is based on inbound VC labels seen that are not configured for this Tunnel.

Contains label from the packet that last failed a label lookup on this Tunnel.

This table associates a SONET path with a CEM VC (or CEM VC group) and provides the starting time-slot of the SONET path. It as assumed that the transmit and receive sides of the SONET path have the same starting time-slots. It is also assumed that STSn paths have contiguous time-slots.

This table is indexed by the SONET path ifIndex. An entry to this table is created by the agent when an entry is created in the mplsCemVcTable.

Index to entry in the mplsCemVcTable.

Starting time-slot for this SONET path within the SONET line and section. For OC-48, this value could range from 1 to 48. The SONET path width must be taken into consideration here, for example, in an OC-48 an STS-3c could not start at time-slot 47.

This variable indicates the storage type for this object.

If this object is true, then it enables the generation of mplsCemVcUp and mplsCemVcDown traps, otherwise these traps are not emitted. These traps are also individually enabled for each CEM VC.