rfc-6240

Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP) MIB Using SMIv2

D. Zelig (Editor), R. Cohen (Editor), T. Nadeau (Editor)
date2011-05 streamIETF areartg wgpwe3 statusPROPOSED STANDARD pages67 canonicalhttps://www.rfc-editor.org/rfc/rfc6240 doi10.17487/RFC6240
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) circuits over a Packet Switch Network (PSN). [STANDARDS-TRACK]

Extracted elements (27)

design-rationale §1

A CEP connection is modeled as a pseudowire and is therefore not represented in the ifTable, following the spirit of RFC 2863. This keeps the service layer cleanly separate from physical interface management.

realtime, snmp

design-rationale §7

High-capacity (HC) Counter64 objects are used in performance tables because 32-bit counters would overflow in minutes for high-speed paths; a SONET STS-48c path can roll over non-HC counters in a few minutes.

realtime, measurement

design-rationale §6.3

The MIB is structured in three layers (service/PW/PSN) following the PWE3 architecture (RFC 3985), isolating CEP service objects from both PW-generic management (PW-STD-MIB) and the underlying PSN-specific modules.

realtime, snmp

design-rationale §6.1

The pwCepCfgTable is designed so that a single configuration entry may be referenced by many pwCepTable entries. This N:1 sharing reduces NMS burden and avoids redundant configuration for PWs with identical parameters.

realtime, snmp

interoperability-note §5

The PW-CEP-STD-MIB is explicitly designed to be independent of PSN type; the same module manages CEP PWs regardless of whether the underlying packet network is MPLS, IP, or other PSN variants.

realtime, snmp

normative-requirement §7 MUST NOT

All read-create objects in pwCepCfgEntry MUST NOT be changed while pwCepCfgRowStatus is active(1). The agent MUST NOT allow pwCepCfgRowStatus to be changed from active(1) while the entry is referenced by at least one active PW.

realtime, snmp

normative-requirement §7 MUST

An agent with CEP capability MUST support at least 4 performance intervals in pwCepValidIntervals. The RECOMMENDED default is 32 intervals, and n MUST NOT exceed 96.

realtime, snmp, measurement

normative-requirement §7 MUST NOT

In the pwCepPerf1DayIntervalTable, if any error counter overflows during a one-day interval, the counter MUST NOT wrap around and MUST return the maximum value instead.

realtime, snmp, measurement

normative-requirement §7 MUST

Manual entries in the pwCepTable SHOULD be preserved after a reboot; the agent MUST ensure their integrity. If a row's entries are found inconsistent after reboot, the PW's pwOperStatus MUST be declared as notPresent(5).

realtime, snmp

normative-requirement §7 MUST

Setting the 'ais' bit in pwCepCfgEnableDBA MUST cause CEP payload suppression when AIS is detected on the SONET path; setting 'unequipped' MUST cause payload suppression when an unequipped condition is detected.

realtime

normative-requirement §7 MUST

The actual jitter buffer depth MUST be at least twice the configured pwCepCfgJtrBfrDepth value for proper operation. If the agent does not support the configured value, it MUST reject the SNMP Set operation.

realtime, qos

normative-requirement §7 MUST NOT

The cepAis indication MUST NOT in itself cause a CEP PW down notification; AIS on the incoming SONET stream is signaled to the peer but does not declare the PW down.

realtime

normative-requirement §7 MUST

The ooRngDropped indication in pwCepIndications MUST be supported regardless of whether the implementation supports packet reordering. Writing a non-zero value to pwCepIndications MUST fail.

realtime, snmp

normative-requirement §7 MUST

When the agent updates performance statistics in real time, it MUST retroactively reduce ES and SES counts by the SesToUas value and increase UAS count by that value when UAS state is entered (mirroring RFC 3592 behavior).

realtime, measurement

protocol-element §6.1

The pwCepCfgTable (pwCepObjects 3) holds shareable CEP PW configuration parameters (payload length, jitter buffer depth, DBA settings, LOPS thresholds, etc.). A single entry may be referenced by many pwCepTable entries, reducing NMS burden.

realtime, snmp

protocol-element §6.1

The pwCepFracTable (pwCepObjects 4) extends configuration for fractional-SPE PWs, covering STS-1/VC-3 and VC-4 fractional modes including EBM (Equipped Bit Mask), VTG/TUG-2 maps, and asynchronous (DS3/E3) payload types.

realtime, snmp

protocol-element §7

The pwCepIndications BITS object (pwCepEntry 7) accumulates defect indications including missingPkt, ooRngDropped, jtrBfrUnder, pktMalformed, lops, cepRdi, cepAis, badHdrStack, cepNeFailure, and cepFeFailure. It holds accumulated state until cleared by an SNMP write.

realtime, snmp

protocol-element §7

The pwCepSonetConfigErrorOrStatus BITS object (pwCepEntry 3) reports local and peer configuration mismatches, including timeslotInUse, timeslotMisuse, and per-feature Incompatible/Asymmetric peer bits for DBA, EBM, RTP, and async parameters.

realtime, snmp

protocol-element §6.1

The pwCepTable (pwCepObjects 1) is the central CEP PW table, indexed by pwIndex, associating each SONET/SDH path or VT with a pseudowire. An entry is created automatically by the agent for every pwTable entry whose pwType equals 'cep'.

realtime, snmp

protocol-element §7

The pwCepType object specifies the CEP sub-type: 'spe'(1) for SONET STS-Nc signals, 'vt'(2) for SONET VT-x signals, or 'fracSpe'(3) for fractional STS-1/VC-3/VC-4. Support for 'vt' and 'fracSpe' modes is optional.

realtime

protocol-element §6.1

Three performance tables are defined: pwCepPerfCurrentTable (current 15-minute interval, pwCepObjects 5), pwCepPerfIntervalTable (up to 96 historical 15-minute intervals, pwCepObjects 6), and pwCepPerf1DayIntervalTable (current and previous days, pwCepObjects 7). All track DBA packets, pointer adjustments, missing/malformed packets, jitter buffer events, ES, SES, UAS, and FC counters.

realtime, snmp, measurement

registry §7

The PW-CEP-STD-MIB module is assigned the OID { mib-2 200 }, registering it under the standard MIB-2 subtree managed by IANA.

registry, snmp

security-consideration §8

The MIB contains read-write and read-create objects (e.g., pwCepCfgJtrBfrDepth, pwCepCfgEnableDBA, pwCepCfgRowStatus) whose unauthorized modification can disrupt active pseudowires and corrupt performance data. Implementations should apply SNMPv3 access control to restrict write access to authorized managers.

security, snmp, realtime

state-machine §7

The LOPS (Loss of Packet Synchronization) state machine has two states: in-sync and LOPS. The trigger to enter LOPS is pwCepCfgConsecMissingOutSync consecutive missing packets (default 10); the trigger to exit LOPS is pwCepCfgConsecPktsInsync consecutive in-sequence packets (default 2).

realtime

wire-format §7

PwCepSdhVc4Ebm is a 32-bit Unsigned32 textual convention where the Equipped Bit Mask occupies the 30 least significant bits, used per TUG-3 in fractional VC-4 circuits.

realtime

wire-format §7

PwCepSonetEbm is a 32-bit Unsigned32 textual convention where the Equipped Bit Mask occupies the 28 least significant bits, used for fractional STS-1/VC-3 circuits.

realtime

wire-format §7

PwCepSonetVtgMap is a 32-bit Unsigned32 textual convention encoding the VT/VC types carried in seven VTG/TUG-2s as a 28-bit EBM in the least significant bits, specifying maximal occupancies per VTG.

realtime