PW-CEP-STD-MIB: View SNMP OID List / Download MIB

This MIB module contains managed object definitions for Circuit Emulation over Packet (CEP) as in [RFC4842]: Malis, A., Prayson, P., Cohen, R., and D. Zelig. 'Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)', RFC 4842. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).

This table contains objects and parameters for managing and monitoring the CEP PW.

Each entry represents the association of a SONET/SDH path or VT to a PW. This table is indexed by the pwIndex of the applicable PW entry in the pwTable. An entry is created in this table by the agent for every entry in the pwTable with a pwType equal to 'cep'. All read-write objects in this table MAY be changed at any time; however, change of some objects (for example pwCepCfgIndex) during PW forwarding state may cause traffic disruption. Manual entries in this table SHOULD be preserved after a reboot. The agent MUST ensure the integrity of those entries. If the set of entries of a specific row are found to be inconsistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5).

Specifies the sub-type of CEP PW. Currently only structured types are supported: 'spe'(1) : SONET STS-Nc signals. 'vt' (2) : SONET VT-x (x=1.5,2,3,6) signals. 'fracSpe' (3) : SONET fractional STS-1 or SDH fractional VC-3 or VC-4 carrying tributaries or asynchronous signals. Support of 'vt' mode or 'fracSpe' mode is optional. Enumeration: 'fracSpe': 3, 'vt': 2, 'spe': 1.

This is a unique index within the ifTable. It represents the interface index for the SONET path for SPE emulation ([RFC3592], Section 3.3), an interface index for the SONET VT ([RFC3592], Section 3.4) if the VT to be emulated is extracted from a SONET signal or locally mapped from a physical interface. A value of zero indicates an interface index that has yet to be determined. Once set, if the SONET ifIndex is (for some reason) later removed, the agent MAY delete the associated PW rows (e.g., this pwCepTableEntry). If the agent does not delete the rows, it is RECOMMENDED that the agent set this object to zero.

This object reports a configuration mismatch inside the local node or between the local node and the peer node. Some bits indicate an error, and some are simply status reports that do not affect the forwarding process. 'timeslotInUse'(1) is set when another CEP PW has already reserved a timeslot (or timeslots) that this CEP PW is attempting to reserve. 'timeslotMisuse'(2) is set when the stated timeslot this PW is trying to use is not legal, for example, if specifying a starting timeslot of 45 for a SONET path of an STS-12c width. The peerZZZIncompatible bits are set if the local configuration is not compatible with the peer configuration as available from the CEP option received from the peer through the signaling process and the local node cannot support such asymmetric configuration. The peerZZZAsymmetric bits are set if the local configuration is not compatible with the peer configuration as available from the CEP option received from the peer through the signaling process, but the local node can support such asymmetric configuration. Bits: 'peerEbmIncompatible': 4, 'peerDbaIncompatible': 3, 'timeslotInUse': 1, 'peerRtpIncompatible': 5, 'timeslotMisuse': 2, 'peerEbmAsymmetric': 8, 'peerRtpAsymmetric': 9, 'other': 0, 'peerDbaAsymmetric': 7, 'peerAsyncAsymmetric': 10, 'peerAsyncIncompatible': 6.

Index to CEP configuration table below. Multiple CEP PWs MAY share a single pwCepCfgEntry. The value 0 indicates that no entries are available.

The number of seconds, including partial seconds, that have elapsed since the beginning of the current measurement period. If, for some reason such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.

The number (n) of previous 15-minute intervals for which data was collected. An agent with CEP capability MUST be capable of supporting at least 4 intervals. The RECOMMENDED default value for n is 32, and n MUST NOT exceed 96.

Definitions: 'missingPkt'(0) - While playing out a sequence of packets, at least one packet was determined to be missing based on a gap in the CEP sequence number. Note: If the implementation supports packet reordering, detecting gaps SHOULD take place as they are played out, not as they arrive. This provides time for misordered packets to arrive late. 'ooRngDropped'(1) - At least one packet arrived outside the range of the jitter buffer. This may be because the jitter buffer is full or the sequence number addresses a buffer outside the current jitter buffer range or an already occupied buffer within range. Whether or not packet reordering is supported by the implementation, this indication MUST be supported. 'jtrBfrUnder'(2) - The jitter buffer underflowed because not enough packets arrived as packets were being played out. 'pktMalformed'(3) - Any error related to unexpected packet format (except bad header stack) or unexpected length. 'lops'(4) - Loss of Packet Synchronization. 'cepRdi'(5) - Circuit Emulation over Packet Remote Defect Indication. Remote Defect Indication (RDI) is generated by the remote CEP de-packetizer when LOPS is detected. 'cepAis'(6) - Remote CEP packetizer has detected an Alarm Indication Signal (AIS) on its incoming SONET stream. cepAis MUST NOT (in itself) cause a CEP PW down notification. 'badHdrStack'(7) - Set when the number of CEP header extensions detected in incoming packets does not match the expected number. 'cepNeFailure'(8) - Set when CEP-NE failure is currently declared. 'cepFeFailure'(8) - Set when CEP-FE failure is currently declared. This object MUST hold the accumulated indications until the next SNMP write that clear the indication(s). Writing a non-zero value MUST fail. Currently, there is no hierarchy of CEP defects. The algorithm used to capture these indications is implementation specific. Bits: 'lops': 4, 'cepRdi': 5, 'ooRngDropped': 1, 'cepFeFailure': 9, 'cepAis': 6, 'jtrBfrUnder': 2, 'cepNeFailure': 8, 'badHdrStack': 7, 'missingPkt': 0, 'pktMalformed': 3.

The value of sysUpTime on the most recent occasion at which the CEP PW entered the Errored Seconds (ES) or Severely Errored Seconds (SES) state.

The value of the CEP option parameter as received from the peer by the PW signaling protocol.

This object contains an appropriate value to be used for pwCepCfgIndex when creating entries in the pwCepCfgTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwCepCfgIndex for a new entry in the pwCepCfgTable, the manager issues a management protocol retrieval operation to obtain the current value of pwCepCfgIndex. 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 one or more CEP PWs by pwCepTable.

These parameters define the characteristics of a CEP PW. They are grouped here to ease Network Management System (NMS) burden. Once an entry is created here, it may be reused by many PWs. By default, all the read-create objects MUST NOT be changed after row activation unless specifically indicated in the individual object description. If the operator wishes to change value of a read-create object, the pwCepCfgRowStatus MUST be set to notInService(2). The agent MUST NOT allow the change of the pwCepCfgRowStatus from the active(1) state for pwCepCfgEntry, which is in use by at least one active PW. Manual entries in this table SHOULD be preserved after a reboot, the agent MUST ensure the integrity of those entries. If the set of entries of a specific row are found to be inconsistent after reboot, the affected PWs' pwOperStatus MUST be declared as notPresent(5).

Primary index to this table.

The number of SONET bytes of the Path or VT carried as payload within one packet. For example, for STS-1/VC-3 SPE circuits, a value of 783 bytes indicates that each packet carries the payload equivalent to one frame. For VT1.5/VC11 circuits, a payload length of 104 bytes indicates that each packet carries payload equivalent to one VT1.5 super-frame. The actual payload size may be different due to bandwidth reduction modes, e.g., Dynamic Bandwidth Allocation (DBA) mode or dynamically assigned fractional SPE. This length 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 pwCepPerf...Malformed.) The default values are determined by the pwCepType: 783 for pwCepType equal to spe(2) or fracSpe(3). For vt(3) modes, the applicable super-frame payload size is the default value.

This object defines the minimum CEP packet length in number of bytes (including CEP header and payload). It applies to CEP's bandwidth-savings packets. Currently, DBA is the only bandwidth-savings packet type (in the future, CEP may support compression). Minimum packet length is necessary in some systems or networks. Setting zero here indicates that there is no minimum packet restriction.

This object defines if reordering is applied for incoming packets. If set 'true', as inbound packets are queued in the jitter buffer, out-of-order packets are reordered. The maximum sequence number differential (i.e., the range in which resequencing can occur) is dependant on the depth of the jitter buffer. If the local agent supports packet reordering, the default value SHOULD be set to 'true'; otherwise, this value SHOULD be set to 'false'.

This object defines when DBA is applied for packets sent toward the PSN. Setting 'ais' MUST cause CEP packet payload suppression when AIS is detected on the associated SONET path. Similarly, 'unequipped' MUST cause payload suppression when an unequipped condition is detected on the SONET/SDH PATH/VT. During DBA condition, CEP packets will continue to be sent, but with indicators set in the CEP header instructing the remote to play all ones (for AIS) or all zeros (for unequipped) onto its SONET/SDH path. NOTE: Some implementations may not support this feature. In these cases, this object should be read-only. Bits: 'unequipped': 1, 'ais': 0.

If this object is set to 'true', an RTP header is not prepended to the CEP packet.

This object defines the number of microseconds of expected packet delay variation for this CEP PW over the PSN. The actual jitter buffer MUST be at least twice this value for proper operation. If configured to a value not supported by the implementation, the agent MUST reject the SNMP Set operation.

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

Consecutive missing packets required to enter the LOPS state.

This object defines the value played when inbound packets have over/underflowed the jitter buffer or are missing for any reason. This byte pattern is sent (played) on the SONET path.

The number of missing packets detected (consecutive or not) within a 1-second window to cause a Severely Errored Second (SES) to be counted.

The number of consecutive SESs before declaring PW in Unavailable Seconds (UAS) state (at which point pwCepPerfUASs starts counting). The SesToUas default value is 10 seconds. NOTE: Similar to [RFC3592], if the agent chooses to update the various performance statistics in real time, it MUST be prepared to retroactively reduce the ES and SES counts by this value and increase the UAS count by this value when it determines that UAS state has been entered. NOTE: See pwCepPerfSESs and pwCepPerfUASs.

The number of consecutive nonSESs before declaring PW is NOT in UAS state (at which point pwCepPerfUASs stops counting).

This variable contains the name of the Configuration entry. This name may be used to help the NMS to display the purpose of the entry.

For creating, modifying, and deleting this row. None of the read-create objects' values can be changed when pwCepCfgRowStatus is in the active(1) state. Changes are allowed when the pwRowStatus is in notInService(2) or notReady(3) states only. If the operator needs to change one of the values for an active row (for example, in order to fix a mismatch in configuration between the local node and the peer), the pwCepCfgRowStatus should be first changed to notInService(2). The objects may be changed now and later changed to active(1) in order to re-initiate the signaling process with the new values in effect. Change of status from the active(1) state or deleting a row SHOULD be blocked by the local agent if the row is referenced by any pwCepEntry those pwRowStatus is in the active(1) state.

This object indicates the storage type for this row.

This table contains a set of parameters for CEP PWs with pwCepType FRAC type.

There are two options for creating an entry in this table: - By the Element Management System (EMS) in advance for creating the PW. - By the agent automatically when the PW is set up. The first option is typically used when there is a native service processing (NSP) cross-connect option between the physical ports and the emulated (virtual ports), while the second MAY be used when there is a one-to-one mapping between the emulated signal and the physical signal.

This is the index of this table. It is a unique index within the ifTable. It represents the interface index for the SONET path ([RFC3592], Section 3.3) for fractional SPE emulation. It may represent an internal (virtual) interface if an NSP function exists between the physical interface and the emulation process.

Fractional mode for STS-1/VC-3 or VC-4 circuits: notApplicable - When this object is not applicable. dynamic - EBM carried within the CEP header. Unequipped VTs are removed from the payload on the fly. static - EBM not carried within the CEP header. Only VTs defined in the EBM are carried within the payload. staticWithEbm - EBM carried within the CEP header. Only VTs defined in the EBM are carried within the payload. staticAsync - Asynchronous E3/T3 fixed byte removal only. Enumeration: 'notApplicable': 1, 'static': 3, 'dynamic': 2, 'staticWithEbm': 4, 'staticAsync': 5.

vtgMapEbmConflict(1) is set when the configured static EBM does not match the configured vtgMap for fractional STS-1/VC-3 circuits or when the TUG2Map is in conflict with the static EBM for VC-4 circuits, for example, if the vtgMap specifies that VTG#1 carries VT2 VTs while the EBM indicate that four VTs are equipped within VTG#1. vtgMapAsyncConflict(2) is set when there is a conflict between the mode, the async indication, and the vtgMap fields. For example, fractional mode is set to staticAsync while the VtgMap indicates that the STS-1/VC-3 carries VTs, or both async1 and Tug2Map are set in fractional VC-4 circuits. Bits: 'vtgMapEbmConflict': 1, 'other': 0, 'vtgMapAsyncConflict': 2.

This object defines the asynchronous payload carried within the STS-1/VC-3. This object is applicable when pwCepFracMode equals 'staticAsync' and MUST equal to 'other' otherwise.

This object defines the VT/VC types of the seven VTG/TUG-2 within the STS-1/VC-3. This variable should be set when 'dynamic', 'static', or 'staticWithEbm' fractional STS-1/VC-3 pwCepFracMode is selected.

This object holds the static Equipped Bit Mask (EBM) for STS-1/VC-3 channel. This variable MAY be set when 'static' or 'staticWithEbm' fractional STS-1/VC-3 pwCepFracMode is selected. It is possible that the configuration of other MIB modules will define the EBM value; in these cases, this object is read-only and reflects the actual EBM that would be used.

This object reports the Equipped Bit Mask (EBM) for STS-1/VC-3 channel as received from the peer within the CEP extension header.

Fractional mode for VC-4 circuits: notApplicable - When this is not VC-4 circuit. dynamic - EBM carried within the CEP header. Unequipped VTs are removed from the payload on the fly. static - EBM not carried within the CEP header. Only VTs defined in the EBM are carried within the payload. staticWithEbm - EBM carried within the CEP header. Only VTs defined in the EBM are carried within the payload. Enumeration: 'notApplicable': 1, 'static': 3, 'dynamic': 2, 'staticWithEbm': 4.

The type of asynchronous mapping carried inside STS-1, VC-3, or TUG-3 containing TU-3 circuit.

If the second TUG-3 within the VC-4 contains a TU-3, this variable must be set.

If the third TUG-3 within the VC-4 contains a TU-3, this variable must be set.

The VC types of the seven TUG-2s within the first TUG-3 of the VC-4.

The VC types of the seven TUG-2s within the second TUG-3 of the VC-4.

The VC types of the seven TUG-2s within the third TUG-3 of the VC-4.

Static Equipped Bit Mask (EBM) for the first TUG-3 within the VC-4. This variable should be set when 'static' or 'staticWithEbm' fractional VC-4 pwCepFracMode is selected. It is possible that the EBM that would be used is available based on configuration of other MIB modules. In these cases, this object is read-only and reflects the actual EBM that would be used.

Static Equipped Bit Mask (EBM) for the second TUG-3 within the VC-4. This variable should be set when 'static' or 'staticWithEbm' fractional VC-4 pwCepFracMode is selected. It is possible that the EBM that would be used is available based on configuration of other MIB modules. In these cases, this object is read-only and reflects the actual EBM that would be used.

Static Equipped Bit Mask (EBM) for the third TUG-3 within the VC-4. This variable should be set when 'Static' or 'staticWithEbm' fractional VC-4 pwCepFracMode is selected. It is possible that the EBM that would be used is available based on configuration of other MIB modules. In these cases, this object is read-only and reflects the actual EBM that would be used.

Equipped Bit Mask (EBM) for the first TUG-3 within the fractional VC-4 channel received from the peer within the CEP extension header.

Equipped Bit Mask (EBM) for the second TUG-3 within the fractional VC-4 channel received from the peer within the CEP extension header.

Equipped Bit Mask (EBM) for the third TUG-3 within the fractional VC-4 channel received from the peer within the CEP extension header.

For creating, modifying, and deleting this row. This object MAY be changed at any time.

This variable indicates the storage type for this object.

CEP bridges the SONET and packet worlds. In the packet world, counts typically start from the time of service creation and do not stop. In the SONET world, counts are kept in 15-minute intervals. The PW CEP MIB supports both methods. The current 15-minute interval counts are in this table. The interval and total stats are in tables following this. This table provides per-CEP PW performance information. High capacity (HC) counters are required for some counts due to the high speeds expected with CEP services. A SONET path of width 48 (STS-48c) can rollover non-HC counters in a few minutes.

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

Number of DBA packets received.

Number of DBA packets sent.

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

Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.

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

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

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

Number of seconds in which a positive or negative pointer adjustment was seen on the SONET path.

Indicates the relative adjustment drift between inbound and outbound streams. It is calculated as absolute value of: (InPosPtrAdjust - InNegPtrAdjust ) - (OutPosPtrAdjust - OutNegPtrAdjust)

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

Number of packets detected out of sequence (via CEP header sequence numbers) but successfully reordered. Note: Some implementations may not support this feature (see pwCepCfgPktReorder).

Number of packets detected out of range (via CEP header sequence numbers) and could not be reordered or could not fit in the jitter buffer.

Number of times a packet needed to be played out and the jitter buffer was empty.

Number of packets detected with unexpected size or bad headers stack.

A summary of all the packet-error types above (from missing packets to bad length packets).

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.

CEP Failure Counts (FC-CEP). The number of CEP failure events. A failure event begins when the LOPS failure is declared and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

This table provides per-CEP PW performance information, much like the pwCepPerfCurrentTable 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 CEP PWs.

An entry in this table is created by the agent for every pwCepPerfCurrentEntry 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. pwCepIndex is found in the pwCepCfg table.

A number (between 1 and 96 to cover a 24-hour period) that 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 range 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. The value of 0 is not used here due to issues with implementations. Enumeration: 'reset': 1, 'normal': 2.

The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.

Number of DBA packets received.

Number of DBA packets sent.

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

Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.

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

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

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

Number of seconds in which a positive or negative pointer adjustment was seen on the SONET path.

The relative adjustment drift between inbound and outbound streams. It is calculated as absolute value of: (InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)

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

Number of packets detected out of sequence (via CEP header sequence numbers) but successfully reordered. Note: Some implementations mat not support this feature (see pwCepCfgPktReorder).

Number of packets detected out of range (via CEP header sequence numbers) and could not be reordered or could not fit in the jitter buffer.

Number of times a packet needed to be played out and the jitter buffer was empty.

Number of packets detected with unexpected size or bad headers stack.

A summary of all the packet-error types above (from missing packets to bad length packets).

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.

CEP Failure Counts (FC-CEP). The number of CEP failure events. A failure event begins when the LOPS failure is declared and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.

This table provides per CEP PW performance information, the current day's measurement, and the previous day's interval. In the extreme case where one of the error counters has overflowed during the one-day interval, the error counter MUST NOT wrap around and MUST return the maximum value.

An entry is created in this table by the agent for every entry in the pwCepTable and for each day interval up to the number of supported historical intervals.

History Data Interval number. Interval 1 is the current day measurement period; interval 2 is the most recent previous day; and interval 30 is 31 days ago.

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

The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in situations where performance monitoring data could not be collected for any reason or the agent clock was adjusted.

Number of DBA packets received.

Number of DBA packets sent.

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

Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.

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

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

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

Number of seconds in which a positive or negative pointer adjustment was seen on the SONET path.

The relative adjustment of drift between inbound and outbound streams. It is calculated as absolute value of: (InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)

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

Number of packets detected out of sequence (via CEP header sequence numbers) but successfully reordered. Note: Some implementations may not support this feature (see pwCepCfgPktReorder).

Number of packets detected out of range (via CEP header sequence numbers) and could not be reordered or could not fit in the jitter buffer.

Number of times a packet needed to be played out, and the jitter buffer was empty.

Number of packets detected with unexpected size or bad headers stack.

A summary of all the packet-error types above (from missing packets to bad length packets).

The counter associated with the number of Errored Seconds encountered.

The counter associated with the number of Severely Errored Seconds. See pwCepCfgMissingPktsToSes.

The counter associated with the number of unavailable seconds. See pwCepCfgSesToUAS. 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. NOTE: Similar to [RFC3592], if the agent chooses to update the various performance statistics in real time, it must be prepared to retroactively reduce the ES and SES counts (by the value of pwCepCfgSesToUas) and increase the UAS count (by that same value) when it determines that UAS state has been entered.

CEP Failure Counts (FC-CEP). The number of CEP failure events. A failure event begins when the LOPS failure is declared and ends when the failure is cleared.

Collection of objects for basic CEP PW config and status.

Collection of objects required if the network element support CEP connections signaling.

Collection of detailed objects needed to configure CEP PWs.

Collection of statistics objects for CEP PWs.

Collection of statistics objects for CEP PWs.

Collection of statistics objects for CEP PWs.

Collection of fractional SPE objects. These objects are optional and should be supported only if fractional SPE is supported within the network element.

Collection of fractional STS-1/VC3 objects. These objects are optional and should be supported only if fractional STS-1/VC3 is supported within the network element.

Collection of fractional VC4 objects. These objects are optional and should be supported only if fractional VC4 is supported within the network element.

The compliance statement for agents that support full CEP PW configuration through this MIB module.

The compliance statement for agents that provide read-only support for the PW CEP MIB Module. Such devices can be monitored but cannot be configured using this MIB module.