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

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. If set, then an error code is set in pwVcCemConfigError.

, July 2001. This MIB reports to the PW-MIB. The PW-MIB contains structures and MIB associations generic to Pseudo-Wire Virtual Circuit (VC) emulation. VC-specific MIBs (such as this) contain config and stats for specific VC types.

This notification is generated when a CEM VC has exited the failure state.

This notification is generated when a CEM VC has entered the failure state. See description of pwVcCemPerfLastDefectsAtFailure object.

This table contains the index to the entry SONET path table for this CEM VC, the index to the CEM config table, and CEM statistics.

This MIB reports to the PW-MIB. This table is indexed by the same index that was created for the associated entry in the PW VC Table (in the PW-MIB). - The PwVcIndex. - The PwVcInstance. An entry is created in this table by the agent for every entry in the pwVc table with a VcType of cem. This table provides per CEM VC performance information. HC (high capacity) counters are required for some counts due to the high speeds expected with CEM services. A SONET path of width 48 (STS-48c) can rollover non-HC counters in a few minutes. CEM bridges the SONET and packet worlds. In the packet world, counts typically start from the time of service creation - and dont stop. In the SONET world, counts are kept in 15 minute intervals. The CEM-MIB supports both methods. Thestats in the VC CEM table count forever. The 15 minute interval counts are in the tables following this. NOTE: Outbound errors are currently not considered in the CEM-MIB. It is assumed that CEM packets are forwarded as they are generated. i.e., It is assumed that there are no congestion issues at the point of CEM adaptation.

This is a unique index within the ifTable. It represents the interface index for the SONET path. A value of zero indicates an interface index that has yet to be configured or has since disappeared. Note: if there are multiple instances of CEM VC, then the pathIfIndex object MUST be identical in each instance.

Index to CEM configuration table below. It is likely that multiple CEM VCs will share 1 CEM conf table entry.

Number of DBA packets received.

Number of DBA packets sent.

Number of DBA packets received.

Number of DBA packets sent.

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

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

Number of seconds in which a pos or neg pointer adjustment was sent on the SONET path.

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 seconds in which a pos or neg pointer adjustment was seen on the SONET path.

Absolute Pointer adjustments is relative adjustment drifts between inbound and outbound streams. It is calculated as such : ( InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)

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. Note: some implementations may not support this feature (see pwVcCemConfPktResequence).

Number of packets detected out of sequence (via CEM header sequence numbers), but were unable to be re- sequenced.

Number of times the jitter buffer transitioned to empty.

Number of packets received while jitter buffer is full.

Number of packets received larger or smaller than pwVcCemConfPktLength.

The counter associated with the number of Errored Seconds encountered. See future versions of draft-malis-sonet-ces-mpls for definition of ES.

The counter associated with the number of Severely Errored Seconds. See future versions of draft-malis-sonet-ces-mpls for definition of SES.

The counter associated with the number of UnAvailable Seconds. See pwVcCemConfSesToUAS. NOTE: When first entering the UAS state, the number of SesToUas is added to this object, then as each additional UAS occurs, this object increments by one.

The state of defects when CEM VC last entered the a failure state. Since more than one defect can contributed to a CEM VC failure, all are shown here. Note: currently there is no hierarchy of CEM defects. Note: the algorithm used to capture these defects when entering failure state is implementation specific. Note: definition of CEM failure is for further study. One possible definition: in LOPS state for 2.5 seconds. A CEM failure may be also be determined (via software) as a result of trend analysis (e.g., missing packet ratio over time).

The value of sysUpTime on the most recent occasion at which the CEM enterd the failure state.

The value of sysUpTime on the most recent occasion at which any one or more of this segments 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 object contains an appropriate value to be used for pwVcCemConfIndex when creating entries in the pwVcCemConfTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwVcCemConfIndex for a new entry in the pwVcCemConfTable, the manager issues a management protocol retrieval operation to obtain the current value of pwVcCemConfIndex. 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 contains a set of parameters that may be referenced by 1 or more CEM VCs by pwVcCemTable.

These parameters define the characteristics of a CEM VC. They are grouped here to ease NMS burden. Once an entry is created here it may be re-used by many VCs.

Primary index to this table

Various configurations errors. Illegal settings within the pwVcCemConf table.

This is the maximum CEM packet length in number of bytes (including CEM header and payload). It is fixed and applies to inbound and outbound packets carrying user payload. Although there is no control over inbound packets, those of illegal length are discarded and accounted for (see pwVcCemPerfPktsBadLength.) Note: DBA packets have their own (shorter) length and are not effected by this setting. If there were to be CEM payload compression, compressed packets would have their own (shorter) length not effected by this setting. Used by signaling (LDP) to fill in the Virtual Circuit FEC element and the CEM interface parameters therein.

This is the minimum CEM packet length in number of bytes (including CEM header and payload). It applies to CEMs bandwidth-savings packets. Currently DBA is the only bandwidth-savings packet type (in the future, CEM may support compression). Minimum packet length is necessary in some systems or networks. Setting Zero here indicates that there is no minimum packet restriction. If non-zero, then packets too small are be discarded and accounted for (see pwVcCemPerfPktsBadLength.) Used by signaling (LDP) to fill in the Virtual Circuit FEC element and the CEM interface parameters therein.

Used by signaling (LDP) to fill in the Virtual Circuit FEC element and the CEM interface parameters therein. CEM options are formatted into bit fields within a 16-bit word. Such fields will define CEM-DBA, STS-n starting time slot, etc.

If set True: as inbound packets are queued in the jitter buffer, out of order packets are re-sequenced. The maximum sequence number differential (i.e., the range in which resequencing can occur) is dependant on the depth of the jitter buffer. See pwVcCemConfJtrBfrDepth. NOTE: Some implementations may not support this feature. If set True, then error code is set in pwVcCemConfigError. NOTE: Some implementations may always have this feature on. If set False, then error code is set in pwVcCemConfigError.

This setting configures the number of packet buffers reserved for this CEM VC. 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.

Consecutive pkts with sequential sequence numbers required to exit the LOPS state.

Consecutive missing pkts required to enter the LOPS state.

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 pwVcCemConfUasAction is errorAction) are not in effect once the CEM VC is in UAS state. For userValue see pwVcCemConfUserErrorAction.

Used when userValue selected above. This byte value is sent on every byte in every SPE.

Number of consecutive SESs before declaring VC in UAS state (and at which point pwVcCemPerfUASs starts counting). The SesToUas default value is 10 seconds. NOTE: 10 consecutive non-SESs cause the VC to exit the UAS state. See pwVcCemPerfSESs and pwVcCemPerfUASs.

These are the actions to take once the CEM VC has been declared in UAS state (as observed in pwVcCemPerfDefects) and there are missing packets (as described in the pwVcCemConfErrorAction object, above). These patterns are sent (played) on the SONET path. If errorAction is selected, then the pwVcCemConfErrorAction settings stay in effect even after the CEM VC is in UAS. For userValue see pwVcCemConfUserUasAction.

Used when userValue selected above. This byte value is sent on every byte in every SPE.

For creating, modifying, and deleting this row.

This variable indicates the storage type for this object.

This table provides per CEM VC performance information much like the pwVcCemPerfTable above. However, these counts represent the current 15 minute interval only. NOTE: Counter64 objects are used here, Counter32 is too small for OC-768 CEM VCs.

An entry in this table is created by the agent for every pwVcCemConf entry. It is an extension to the pwVcCemConf table. After 15 minutes, the contents of this table entry are copied to a new entry in the pwVcCemPerfInterval table and the counts in this entry are reset to zero.

Number of DBA packets received.

Number of DBA packets sent.

Number of DBA packets received.

Number of DBA packets sent.

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

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

Number of seconds in which a pos or neg pointer adjustment was sent on the SONET path.

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 seconds in which a pos or neg pointer adjustment was seen on the SONET path.

Absolute Pointer adjustments is relative adjustment drifts between inbound and outbound streams. It is calculated as such : ( InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)

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. Note: some implementations may not support this feature (see pwVcCemConfPktResequence).

Number of packets detected out of sequence (via CEM header sequence numbers), but were unable to be re- sequenced.

Number of times the jitter buffer transitioned to empty.

Number of packets received while jitter buffer is full.

Number of non-bandwidth-saving packets received larger or smaller than pwVcCemConfMaxPktLength. Plus number of bandwidth-saving packets (like DBA) that are smaller than pwVcCemConfMinPktLength.

The counter associated with the number of Errored Seconds encountered.

The counter associated with the number of Severely Errored Seconds encountered.

The counter associated with the number of Unavailable Seconds encountered.

This table provides per CEM VC performance information much like the pwVcCemPerfCurrentTable above. However, these counts represent historical 15 minute intervals. Typically, this table will have a maximum of 96 entries for a 24 hour period, but is not limited to this. NOTE: Counter64 objects are used here, Counter32 is too small for OC-768 CEM VCs.

An entry in this table is created by the agent for every pwVcCemPerfCurrentEntry that is 15 minutes old. The contents of the Current entry are copied to the new entry here. The Current entry, then resets its counts to zero for the next current 15 minute interval. pwVcCemIndex is found in the pwVcCemConf table.

A number (normally between 1 and 96 to cover a 24 hour period) which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1. The minimum range of N is 1 through 4. The default range is 1 through 32. The maximum value of N is 1 through 96.

This variable indicates if the data for this interval is valid.

Used in cases where the user knows that the errors within this interval should not be counted. Writing reset sets all error counts to zero.

Number of DBA packets received.

Number of DBA packets sent.

Number of DBA packets received.

Number of DBA packets sent.

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

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

Number of seconds in which a pos or neg pointer adjustment was sent on the SONET path.

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 seconds in which a pos or neg pointer adjustment was seen on the SONET path.

Absolute Pointer adjustments is relative adjustment drifts between inbound and outbound streams. It is calculated as such : ( InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)

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. Note: some implementations mat not support this feature (see pwVcCemConfPktResequence).

Number of packets detected out of sequence (via CEM header sequence numbers), but were unable to be re- sequenced.

Number of times the jitter buffer transitioned to empty.

Number of packets received while jitter buffer is full.

Number of packets received larger or smaller than pwVcCemConfPktLength.

The counter associated with the number of Errored Seconds encountered.

The counter associated with the number of Severely Errored Seconds encountered.

The counter associated with the number of Unavailable Seconds encountered.

This table associates a SONET path with a CEM VC (or a set of CEM VCs) 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 (intended for CEM) is created in the sonetPathCurrentTable. Alternatively, an agent may create an entru in this table at the point where a valid ifIndex is written to pwVcCemSonetPathIfIndex in the pwVcCem table. The pwVcCemSonetPathExt table binds a SONET path to a PW CEM VC. A VC index of 0 indicates that the binding has not yet been set.

Index for a row in the sonetPathCurrentTable.

Index for the conceptual row identifying a VC (or set of VCs) within the generic PW VC table (in PW-MIB) or the local pwVcCemTable.

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 pwVcCemUp and pwVcCemDown notifications, otherwise these notifications are not emitted. Note: enabling/disabling notifications for individual CEM VCs is for further study.

Bits set here represent defects used as inputs into APS mechanisms (see PW-MIB). NOTE: these indications are as set within pwVcCemPerfDefects. Note: for APS applications requiring fast response, the lops trigger option is recommended. LOPS can be generated within milliseconds, while UAS is multiple seconds.