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

This MIB contains managed object definitions for Circuit Emulation over Packet (CEP) as in: Malis, A., Prayson, P., Cohen, R. and Zelig, D. 'SONET/SDH Circuit Emulation Over Packet (CEP) encapsulation', Internet Draft . This MIB reports to the PW-STD-MIB as in: Zelig, D., Nadeau, T. 'Pseudo Wire (PW) Management Information Base'. The PW-STD-MIB contains structures and MIB associations generic to Pseudo-Wire (PW) emulation. PW-specific MIBs (such as this) contain config and stats for specific PW types. Copyright (C) The Internet Society (date). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices. -- RFC Ed.: replace yyyy with actual RFC number & remove this note

This table contains the index to the entry SONET path table for this CEP PW, and the index to the CEP config table.

This MIB reports to the PW-STD-MIB. This table is indexed by the same index that was created for the associated entry in the PW Table (in the PW-STD-MIB). - The PwVcIndex. An entry is created in this table by the agent for every entry in the pwVcTable with a pwVcType of 'cep'.

Specifies the type of CEP PW. Currently only structured types are supported. Other CEP Types may be defined in the future. Currently supported CEP types are: 1 - spe : SONET STS-Nc signals. 2 - vt : SONET VT-x (x=1.5,2,3,6) signals. 3 - fracSpe : SONET fractional STS-1 or SDH fractional VC-3 or VC-4 carrying tributaries or Asynchronous signals. Support of vt and fracSpe 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 (RFC2558 section 3.3), an interface index for the SONET VT (RFC2558 section 3.4) if the VT to be emulated is extracted a SONET signal, or the ifIndex of the physical port emulated in VT mode if the VT to be emulated is directly feeded from a physical interface. It may represent an internal (virtual) interface if an NSP function exists between the physical interface and the emulation process. 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 pwVcCep table entry). If the agent does not delete the rows, it is recommended that the agent set this object to zero.

In structured SPE CEP, this object indicates the 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. In structured VT CEP, this object indicates the starting time slot for this tributary within the SONET path. For example, for VT1.5 tributary within STS-1, this value could range from 1 to 28.

timeslotInUse is when another CEP PW (via SONET ifIndex) has already reserved a timeslot(s) that this CEP PW is attempting to reserved. timeslotMisuse is set, for example, if specifying a starting timeslot of 45 for a SONET path of an STS-12c width. peerIncompatible bits are set if the local configuration is not compatible with the peer configuration as available from the CEP option received from the peer. for example if the remote is not capable of accepting DBA packets but the local node is configured to send DBA packets for this PW, peerDbaIncompatible will be set. Bits: 'peerEbmIncompatible': 4, 'peerDbaIncompatible': 3, 'timeslotInUse': 1, 'peerRtpIncompatible': 5, 'timeslotMisuse': 2, 'peerPidIncompatible': 6, 'other': 0, 'peerAsyncIncompatible': 7.

Index to CEP configuration table below. It is likely that multiple CEP PWs will share 1 CEP Cfg table entry.

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 of previous 15-minute intervals for which data was collected. An agent with CEP capability must be capable of supporting at least n intervals. The minimum value of n is 4, The default of n is 32 and the maximum value of n is 96. The value will be unless the measurement was (re-) started within the last (*15) minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.

Definitions: missingPkt - While playing out a sequence of packets, a packet(s) was determined to be missing based on a gap in the CEP sequence number. Note: If the implementation supports packet re-ordering, detecting gaps should not take place as packets arrive, only as they are played out - this gives time for mis-ordered packets to arrive late. ooRngDropped - Packet(s) arrives that is 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 addresses an already occupied buffer within range. Whether or not packet re-ordering is supported by the implementation, this indication MUST be supported. jtrBfrUnder - The jitter buffer underflowed due to not enough packets arriving as packets were being played out. pktBadLength - Non-bandwidth-saving packet arrives larger or smaller than pwVcCepCfgSonetPayloadLength, or when a fractional SPE packet length does not match the extension header or manual configuration indicating the number of equipped VTs. lops - Loss Of Packet Sync. See draft-ietf-pwe3-sonet. cepRdi - Circuit Emulation over Packet Remote Defect Indication. Generated by the remote CEP de-packetizer when detecting LOPS. Note: not generated by the remote SONET function. See draft-ietf-pwe3-sonet. cepAis - Remote CEP packetizer has detected AIS on its incoming SONET stream. See draft-ietf-pwe3- sonet. Note: cepAis MUST NOT (in itself) cause a CEP down notification. This would be a layer violation. badHdrStack - This indication is set when the number of CEP header extensions detected in incoming packets does not match the expected number. Note: currently there is no hierarchy of CEP defects. Note: the algorithm used to capture these indications is implementation specific. Bits: 'lops': 4, 'cepRdi': 5, 'ooRngDropped': 1, 'cepAis': 6, 'jtrBfrUnder': 2, 'badHdrStack': 7, 'missingPkt': 0, 'pktBadLength': 3.

The state of CEP indicators when the CEP PW last declared an errored second (either as ES, SES or a second with errors inside a UAS) condition. At this time, only LOPS can create a failure. Since indicators other than LOPS are useful, all are latched here. For bit definitions, see pwVcCepCurrentIndications above. Note: the algorithm used to latch these indications when entering an defect state is implementation specific. Bits: 'lops': 4, 'cepRdi': 5, 'ooRngDropped': 1, 'cepAis': 6, 'jtrBfrUnder': 2, 'badHdrStack': 7, 'missingPkt': 0, 'pktBadLength': 3.

The value of sysUpTime on the most recent occasion at which the CEP PW entered the ES or SES state.

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

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

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

Primary index to this table

Various configurations errors. Illegal settings within the pwVcCepCfg or pwVcCepSonetExt tables. Bits: 'dba': 1, 'jtrBfrDepth': 4, 'other': 0, 'pktLength': 3, 'lopsPktCount': 2.

The number of SONET bytes of the Path or VT carried as payload within one packet. For example, for STS-1 SPE circuits, value of 783 bytes indicates that each packet carries payload equivalent to one frame. For VT1.5 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. 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 pwVcCepPerf...PktsBadLength.)

This is 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.

If set True: as inbound packets are queued in the jitter buffer, out of order packets are re-ordered. The maximum sequence number differential (i.e., the range in which re-sequencing can occur) is dependant on the depth of the jitter buffer. See pwVcCepCfgJtrBfrDepth. NOTE: Some implementations may not support this feature. The agent is then required to set this False.

Bits set here MUST enable the DBA (dynamic bandwidth allocation) feature for the specified condition. 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 un-equipped condition is detected on the SONET path. During these conditions, 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 un-equipped) onto its SONET path. NOTE: Some implementations may not support this feature. In these cases, if the 'ais' or 'unequipped' bits are set, then 'dba' error code MUST be set in pwVcCepConfigError. Bits: 'unequipped': 1, 'ais': 0.

If set True: an RTP header is not pre-pended to the CEP packet.

This setting configures 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, and is implementation specific. If configured to a value not supported by the implementation, the agent MUST return an error code 'jtrBfrDepth' in 'pwVcCepConfigError ' NOTE: Like bandwidth and time-slots, jitter buffers are 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.

This is 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.

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

Number of consecutive SESs before declaring PW in UAS state (and at which point pwVcCepPerfUASs starts counting). The SesToUas default value is 10 seconds. NOTE: Similar to RFC 3592, If the agent chooses to update the various performance statistics in real time then it must be prepared to retroactively reduce the ES, SES, counts by this value and increase the UAS count by this value when it determines that UAS state has been entered. NOTE: See pwVcCepPerfSESs and pwVcCepPerfUASs.

Number of consecutive nonSESs before declaring PW is NOT in UAS state (and at which point pwVcCepPerfUASs stops counting).

This variable indicates the storage type for this row.

For creating, modifying, and deleting this row.

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

An entry of this table can be created in two options: - By the 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 an 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 incoming signal.

This is the primary index of this table. It is a unique index within the ifTable. It represents the interface index for the SONET path (RFC 3592 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 circuits: notApplicable - When this is not STS-1/VC-3 signal. 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': 0, 'static': 2, 'staticWithEbm': 3, 'dynamic': 1, 'staticAsync': 4.

vtgMapEbmConflict 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 is set when there is a conflict between the mode, the async indication and the vtgMap fields. For example, fractional mode is set to Static Async while the VtgMap indicate that the STS-1/VC-3 carries VTs. Or in fractional VC-4 circuits both async1 and Tug2Map are set. Bits: 'vtgMapEbmconflict': 1, 'other': 0, 'vtgMapAsyncConflict': 2.

The Asynchronous payload carried within the STS-1/VC-3. This variable should be set when 'staticAsync' Fractional STS-1/VC-3 pwVcCepFracMode is selected, and hold the value of 'other' otherwise.

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 pwVcCepFracMode is selected.

Static Equipped Bit Mask (EBM) for STS-1/VC-3 channel. This variable should be set when 'static' or 'staticWithEbm' Fractional STS-1/VC-3 pwVcCepFracMode is selected.

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

Fractional mode for VC-4 circuits: notApllicable - 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': 0, 'static': 2, 'staticWithEbm': 3, 'dynamic': 1.

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

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-2 within the first TUG-3 of the VC-4.

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

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

Static Equipped Bit Mask (EBM) for first TUG-3 within the VC-4. This variable should be set when 'static' or 'staticWithEbm' Fractional VC-4 pwVcCepFracMode is selected.

Static Equipped Bit Mask (EBM) for second TUG-3 within the VC-4. This variable should be set when 'static' or 'StaticWithEbm' Fractional VC-4 pwVcCepFracMode is selected.

Static Equipped Bit Mask (EBM) for third TUG-3 within the VC-4. This variable should be set when 'Static' or 'staticWithEbm' Fractional VC-4 pwVcCepFracMode is selected.

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

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

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

For creating, modifying, and deleting this row.

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 don't stop. In the SONET world, counts are kept in 15 minute intervals. The 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. HC (high capacity) 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 pwVcCep entry. After 15 minutes, the contents of this table entry are copied to a new entry in the pwVcCepPerfInterval 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 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 CEP packets.

Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP 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 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 re-ordered. Note: some implementations may not support this feature (see pwVcCepCfgPktReorder).

Number of packets detected out of range (via CEP header sequence numbers), and could not be re- ordered, 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 normal (non-bandwidth-saving packets received) larger or smaller than pwVcCepCfgNormalPktLength.

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 pwVcCepPerfCurrentTable 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 pwVcCepPerfCurrentEntry 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. pwVcCepIndex is found in the pwVcCepCfg 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. 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 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 CEP packets.

Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP 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 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 re-ordered. Note: some implementations mat not support this feature (see pwVcCepCfgPktReorder).

Number of packets detected out of range (via CEP header sequence numbers), and could not be re- ordered, 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 received larger or smaller than pwVcCepCfgNormalPktLength.

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 pwVcCepPerfIntervalTable above. However, these counts represent complete historical information. NOTE: Counter64 objects are used here, Counter32 is too small for OC-768 CEP PWs.

An entry is created in this table by the agent for every entry in the pwVcCep table.

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 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 CEP packets.

Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP 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 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 re-ordered. Note: some implementations may not support this feature (see pwVcCepCfgPktReorder).

Number of packets detected out of range (via CEP header sequence numbers), and could not be re- ordered, 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 received larger or smaller than pwVcCepCfgNormalPktLength.

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. See draft-ietf-pwe3-sonet for definition of ES.

The counter associated with the number of Severely Errored Seconds. See pwVcCepCfgMissingPktsToSes. Also see draft-ietf-pwe3-sonet for definition.

The counter associated with the number of UnAvailable Seconds. See pwVcCepCfgSesToUAS. 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 RFC 2558, If the agent chooses to update the various performance statistics in real time then it must be prepared to retroactively reduce the ES, SES, counts (by the value of pwVcCepCfgSesToUas) 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.

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 provides the means for the agent to declare whether certain CEP PW statistics objects are supported (conformed to) or not. If not supported, then the object MUST be return 0.

The agent MUST create a single entry in this table.

Any arbitrary number

Tells whether the pwVcCepPerf...DbaInPacketsHC in the pwVcCepPerf...Table is supported.

Explanation for pwVcCepPerf...DbaInPacketsHC support in the pwVcCepPerf...Table.

Tells whether the pwVcCepPerf...DbaOutPacketsHC in the pwVcCepPerf...Table is supported.

Explanation for pwVcCepPerf...DbaOutPacketsHC support in the pwVcCepPerf...Table.

Tells whether the pwVcCepPerf...PktsOoseq in the pwVcCepPerf...Table is supported.

Explanation for pwVcCepPerf...PktsOoseq support in the pwVcCepPerf...Table.

Tells whether the pwVcCepPerf...PktsOoRngDropped in the pwVcCepPerf...Table is supported.

Explanation for pwVcCepPerf...PktsOoRngDropped support in the pwVcCepPerf...Table.

Tells whether the pwVcCepPerf...SummaryError in the pwVcCepPerf...Table is supported.

Explanation for pwVcCepPerf...SummaryError support in the pwVcCepPerf...Table.

Collection of objects for basic CEP PW config and status.

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 groups. These objects are optional and should be supported only if fractional SPE is supported within the network element.

Collection of objects declaring conformance to other objects.

The compliance statement for agent that support PW over CEP PSN operation.