PW-CEP-DRAFT04-MIB

All MIBs › PW-CEP-DRAFT04-MIB

Organization: Pseudo-Wire Emulation Edge-to-Edge (PWE3) Working Group

Last Updated: 2003-11-30

Description: IETF PWE3 draft MIB (draft-05 text) for Circuit Emulation Protocol pseudo-wire VCs over packet-switched networks, managing CEP interface configuration and counters

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is PW-CEP-DRAFT04-MIB?

PW-CEP-DRAFT04-MIB is an IETF PWE3 (Pseudo Wire Emulation Edge-to-Edge) working group draft MIB defining managed objects for Circuit Emulation over Packet (CEP), the technique used to carry SONET/SDH circuits across a packet-switched network as a pseudowire. It is a vendor-neutral standards-track module exposing configuration data (CEP type, SONET interface index and time-slot mapping) and performance/fault counters (elapsed time, valid intervals, current and latched defect indications, last errored-second timestamp) for each emulated circuit. Its monitoring role centers on circuit emulation health and fault detection — tracking defect indications and error timing per pseudowire VC lets an operator detect signal loss, timing slips, or configuration errors on the emulated SONET/SDH circuit riding over the packet network. It explicitly depends on and reports up to the PW-STD-MIB, which defines the generic pseudowire structures this MIB augments with CEP-specific detail. It is deployed in carrier networks performing SONET/SDH circuit emulation over MPLS or other packet-switched infrastructure, typically on PE routers or edge devices with pseudowire/TDM interworking capability. Engineers can download the PW-CEP-DRAFT04-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PW-CEP-DRAFT04-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based IETF PWE3 MIB, not tied to a specific manufacturer
carrier-grade PE routers/edge devices with SONET/SDH circuit emulation over pseudowire

Monitoring Examples

An operator would poll the pwVcCepTable/pwVcCepEntry for a given circuit to check pwVcCepSonetIfIndex and pwVcCepSonetTimeSlot mapping alongside pwVcCepCurrentIndications and pwVcCepLatchedIndications for active or historical defect flags. If pwVcCepCurrentIndications shows a persistent alarm and pwVcCepLastEsTimeStamp shows recent errored seconds, that points to a live problem on the emulated SONET/SDH circuit — such as timing drift or packet loss on the underlying pseudowire — that pwVcCepConfigError can further help isolate to a configuration mismatch versus a transport fault.

What Can Be Monitored

CEP circuit type
SONET interface/time-slot mapping
configuration errors
current defect indications
latched defect indications
elapsed time / errored-second timestamps

Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From PerfHist-TC-MIB

PerfCurrentCount
PerfIntervalCount

From PW-DRAFT04-MIB

pwVcIndex

OBJECT-TYPE

From PW-TC-DRAFT04-MIB

pwStdMIB

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
StorageType
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using pwVcCepPerfCurrentDbaInPacketsHC OID:

Select a device implementing PW-CEP-DRAFT04-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type pwVcCepPerfCurrentDbaInPacketsHC into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the number of DBA packets received. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
pwVcCepMIB	1.3.6.1.4.1.99999.52.4			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
pwVcCepObjects	1.3.6.1.4.1.99999.52.4.1
pwVcCepTable	1.3.6.1.4.1.99999.52.4.1.1		not-accessible	This table contains the index to the entry SONET path table for this CEP PW, and the index to the CEP config table.
pwVcCepEntry	1.3.6.1.4.1.99999.52.4.1.1.1		not-accessible	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'.
INT pwVcCepType	1.3.6.1.4.1.99999.52.4.1.1.1.1	INTEGER	read-write	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.
NUM pwVcCepSonetIfIndex	1.3.6.1.4.1.99999.52.4.1.1.1.2	InterfaceIndexOrZero	read-write	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.
U32 pwVcCepSonetTimeSlot	1.3.6.1.4.1.99999.52.4.1.1.1.3	Unsigned32	read-write	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.
BIT pwVcCepSonetConfigError	1.3.6.1.4.1.99999.52.4.1.1.1.4	Bits	read-only	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.
PWV pwVcCepCfgIndex	1.3.6.1.4.1.99999.52.4.1.1.1.5	PwVcCepCfgIndex	read-write	Index to CEP configuration table below. It is likely that multiple CEP PWs will share 1 CEP Cfg table entry.
I32 pwVcCepTimeElapsed	1.3.6.1.4.1.99999.52.4.1.1.1.6	Integer32	read-only	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.
I32 pwVcCepValidIntervals	1.3.6.1.4.1.99999.52.4.1.1.1.7	Integer32	read-only	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.
BIT pwVcCepCurrentIndications	1.3.6.1.4.1.99999.52.4.1.1.1.8	Bits	read-only	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.
BIT pwVcCepLatchedIndications	1.3.6.1.4.1.99999.52.4.1.1.1.9	Bits	read-only	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.
TIM pwVcCepLastEsTimeStamp	1.3.6.1.4.1.99999.52.4.1.1.1.10	TimeStamp	read-only	The value of sysUpTime on the most recent occasion at which the CEP PW entered the ES or SES state.
U32 pwVcCepPeerCepOption	1.3.6.1.4.1.99999.52.4.1.1.1.11	Unsigned32	read-only	The value of CEP option parameter as received from the peer by the PW signaling protocol.
PWV pwVcCepCfgIndexNext	1.3.6.1.4.1.99999.52.4.1.2	PwVcCepCfgIndex	read-only	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.
pwVcCepCfgTable	1.3.6.1.4.1.99999.52.4.1.3		not-accessible	This table contains a set of parameters that may be referenced by 1 or more CEP PWs by pwVcCepTable.
pwVcCepCfgEntry	1.3.6.1.4.1.99999.52.4.1.3.1		not-accessible	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.
PWV pwVcCepCfgTableIndex	1.3.6.1.4.1.99999.52.4.1.3.1.1	PwVcCepCfgIndex	not-accessible	Primary index to this table
BIT pwVcCepConfigError	1.3.6.1.4.1.99999.52.4.1.3.1.2	Bits	read-only	Various configurations errors. Illegal settings within the pwVcCepCfg or pwVcCepSonetExt tables.
U32 pwVcCepSonetPayloadLength	1.3.6.1.4.1.99999.52.4.1.3.1.3	Unsigned32	read-create	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.)
U32 pwVcCepCfgMinPktLength	1.3.6.1.4.1.99999.52.4.1.3.1.4	Unsigned32	read-create	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.
T/F pwVcCepCfgPktReorder	1.3.6.1.4.1.99999.52.4.1.3.1.5	TruthValue	read-only	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.
BIT pwVcCepCfgEnableDBA	1.3.6.1.4.1.99999.52.4.1.3.1.6	Bits	read-create	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.
T/F pwVcCepCfgRtpHdrSuppress	1.3.6.1.4.1.99999.52.4.1.3.1.7	TruthValue	read-only	If set True: an RTP header is not pre-pended to the CEP packet.
U32 pwVcCepCfgJtrBfrDepth	1.3.6.1.4.1.99999.52.4.1.3.1.8	Unsigned32	read-create	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.
U32 pwVcCepCfgConsecPktsInsync	1.3.6.1.4.1.99999.52.4.1.3.1.9	Unsigned32	read-create	Consecutive pkts with sequential sequence numbers required to exit the LOPS state.
U32 pwVcCepCfgConsecMissingOutSync	1.3.6.1.4.1.99999.52.4.1.3.1.10	Unsigned32	read-create	Consecutive missing pkts required to enter the LOPS state.
U32 pwVcCepCfgPktErrorPlayOutValue	1.3.6.1.4.1.99999.52.4.1.3.1.11	Unsigned32	read-create	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.
U32 pwVcCepCfgMissingPktsToSes	1.3.6.1.4.1.99999.52.4.1.3.1.12	Unsigned32	read-create	Number of missing packets detected (consecutive or not) within a 1 second window to cause a Severely Errored Second (SES) to be counted.
U32 pwVcCepCfgSesToUas	1.3.6.1.4.1.99999.52.4.1.3.1.13	Unsigned32	read-create	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.
U32 pwVcCepCfgSecsToExitUas	1.3.6.1.4.1.99999.52.4.1.3.1.14	Unsigned32	read-create	Number of consecutive nonSESs before declaring PW is NOT in UAS state (and at which point pwVcCepPerfUASs stops counting).
STO pwVcCepCfgStorageType	1.3.6.1.4.1.99999.52.4.1.3.1.15	StorageType	read-create	This variable indicates the storage type for this row.
ROW pwVcCepCfgRowStatus	1.3.6.1.4.1.99999.52.4.1.3.1.16	RowStatus	read-create	For creating, modifying, and deleting this row.
pwVcCepFracTable	1.3.6.1.4.1.99999.52.4.1.4		not-accessible	This table contains a set of parameters for CEP PWs with pwVcCepType FRAC type.
pwVcCepFracEntry	1.3.6.1.4.1.99999.52.4.1.4.1		not-accessible	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.
NUM pwVcCepFracIndex	1.3.6.1.4.1.99999.52.4.1.4.1.1	InterfaceIndex	not-accessible	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.
INT pwVcCepFracMode	1.3.6.1.4.1.99999.52.4.1.4.1.2	INTEGER	read-create	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.
BIT pwVcCepFracConfigError	1.3.6.1.4.1.99999.52.4.1.4.1.3	Bits	read-create	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.
PWV pwVcCepFracAsync	1.3.6.1.4.1.99999.52.4.1.4.1.4	PwVcCepFracAsyncMap	read-create	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.
PWV pwVcCepFracVtgMap	1.3.6.1.4.1.99999.52.4.1.4.1.5	PwVcCepSonetVtgMap	read-create	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.
PWV pwVcCepFracEbm	1.3.6.1.4.1.99999.52.4.1.4.1.6	PwVcCepSonetEbm	read-create	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.
PWV pwVcCepFracPeerEbm	1.3.6.1.4.1.99999.52.4.1.4.1.7	PwVcCepSonetEbm	read-create	Equipped Bit Mask (EBM) for STS-1/VC-3 channel received from the peer within the CEP extension header.
INT pwVcCepFracSdhVc4Mode	1.3.6.1.4.1.99999.52.4.1.4.1.8	INTEGER	read-create	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.
PWV pwVcCepFracSdhVc4Tu3Map1	1.3.6.1.4.1.99999.52.4.1.4.1.9	PwVcCepFracAsyncMap	read-create	If the first TUG-3 within the VC-4 contains a TU-3, this variable must be set.
PWV pwVcCepFracSdhVc4Tu3Map2	1.3.6.1.4.1.99999.52.4.1.4.1.10	PwVcCepFracAsyncMap	read-create	If the second TUG-3 within the VC-4 contains a TU-3, this variable must be set.
PWV pwVcCepFracSdhVc4Tu3Map3	1.3.6.1.4.1.99999.52.4.1.4.1.11	PwVcCepFracAsyncMap	read-create	If the third TUG-3 within the VC-4 contains a TU-3, this variable must be set.
PWV pwVcCepFracSdhVc4Tug2Map1	1.3.6.1.4.1.99999.52.4.1.4.1.12	PwVcCepSonetVtgMap	read-create	The VC types of the seven TUG-2 within the first TUG-3 of the VC-4.
PWV pwVcCepFracSdhVc4Tug2Map2	1.3.6.1.4.1.99999.52.4.1.4.1.13	PwVcCepSonetVtgMap	read-create	The VC types of the seven TUG-2 within the second TUG-3 of the VC-4.
PWV pwVcCepFracSdhVc4Tug2Map3	1.3.6.1.4.1.99999.52.4.1.4.1.14	PwVcCepSonetVtgMap	read-create	The VC types of the seven TUG-2 within the third TUG-3 of the VC-4.
PWV pwVcCepFracSdhVc4Ebm1	1.3.6.1.4.1.99999.52.4.1.4.1.15	PwVcCepSdhVc4Ebm	read-create	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.
PWV pwVcCepFracSdhVc4Ebm2	1.3.6.1.4.1.99999.52.4.1.4.1.16	PwVcCepSdhVc4Ebm	read-create	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.
PWV pwVcCepFracSdhVc4Ebm3	1.3.6.1.4.1.99999.52.4.1.4.1.17	PwVcCepSdhVc4Ebm	read-create	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.
PWV pwVcCepFracSdhVc4PeerEbm1	1.3.6.1.4.1.99999.52.4.1.4.1.18	PwVcCepSdhVc4Ebm	read-create	Equipped Bit Mask (EBM) for the first TUG-3 within the fractional VC-4 channel received from peer within the CEP extension header.
PWV pwVcCepFracSdhVc4PeerEbm2	1.3.6.1.4.1.99999.52.4.1.4.1.19	PwVcCepSdhVc4Ebm	read-create	Equipped Bit Mask (EBM) for the second TUG-3 within the fractional VC-4 channel received from peer within the CEP extension header.
PWV pwVcCepFracSdhVc4PeerEbm3	1.3.6.1.4.1.99999.52.4.1.4.1.20	PwVcCepSdhVc4Ebm	read-create	Equipped Bit Mask (EBM) for the third TUG-3 within the fractional VC-4 channel received from peer within the CEP extension header.
ROW pwVcCepFracRowStatus	1.3.6.1.4.1.99999.52.4.1.4.1.21	RowStatus	read-create	For creating, modifying, and deleting this row.
STO pwVcCepFracStorageType	1.3.6.1.4.1.99999.52.4.1.4.1.22	StorageType	read-create	This variable indicates the storage type for this object.
pwVcCepPerfCurrentTable	1.3.6.1.4.1.99999.52.4.1.5		not-accessible	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.
pwVcCepPerfCurrentEntry	1.3.6.1.4.1.99999.52.4.1.5.1		not-accessible	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.
C64 pwVcCepPerfCurrentDbaInPacketsHCEx	1.3.6.1.4.1.99999.52.4.1.5.1.1	Counter64	read-only	Number of DBA packets received.
C64 pwVcCepPerfCurrentDbaOutPacketsHC	1.3.6.1.4.1.99999.52.4.1.5.1.2	Counter64	read-only	Number of DBA packets sent.
C32 pwVcCepPerfCurrentInNegPtrAdjust	1.3.6.1.4.1.99999.52.4.1.5.1.3	Counter32	read-only	Number of negative pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
C32 pwVcCepPerfCurrentInPosPtrAdjust	1.3.6.1.4.1.99999.52.4.1.5.1.4	Counter32	read-only	Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
C32 pwVcCepPerfCurrentInPtrAdjustSecs	1.3.6.1.4.1.99999.52.4.1.5.1.5	Counter32	read-only	Number of seconds in which a pos or neg pointer adjustment was sent on the SONET path.
C32 pwVcCepPerfCurrentOutNegPtrAdjust	1.3.6.1.4.1.99999.52.4.1.5.1.6	Counter32	read-only	Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
C32 pwVcCepPerfCurrentOutPosPtrAdjust	1.3.6.1.4.1.99999.52.4.1.5.1.7	Counter32	read-only	Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
C32 pwVcCepPerfCurrentOutPtrAdjustSecs	1.3.6.1.4.1.99999.52.4.1.5.1.8	Counter32	read-only	Number of seconds in which a pos or neg pointer adjustment was seen on the SONET path.
I32 pwVcCepPerfCurrentAbsPtrAdjust	1.3.6.1.4.1.99999.52.4.1.5.1.9	Integer32	read-only	Absolute Pointer adjustments is relative adjustment drifts between inbound and outbound streams. It is calculated as absolute value of : ( InPosPtrAdjust - InNegPtrAdjust ) - (OutPosPtrAdjust - OutNegPtrAdjust)
C32 pwVcCepPerfCurrentMissingPkts	1.3.6.1.4.1.99999.52.4.1.5.1.10	Counter32	read-only	Number of missing packets (as detected via CEP header sequence number gaps).
C32 pwVcCepPerfCurrentPktsOoseq	1.3.6.1.4.1.99999.52.4.1.5.1.11	Counter32	read-only	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).
C32 pwVcCepPerfCurrentPktsOoRngDropped	1.3.6.1.4.1.99999.52.4.1.5.1.12	Counter32	read-only	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.
C32 pwVcCepPerfCurrentJtrBfrUnderruns	1.3.6.1.4.1.99999.52.4.1.5.1.13	Counter32	read-only	Number of times a packet needed to be played out and the jitter buffer was empty.
C32 pwVcCepPerfCurrentPktsBadLength	1.3.6.1.4.1.99999.52.4.1.5.1.14	Counter32	read-only	Number of normal (non-bandwidth-saving packets received) larger or smaller than pwVcCepCfgNormalPktLength.
C32 pwVcCepPerfCurrentSummaryErrors	1.3.6.1.4.1.99999.52.4.1.5.1.15	Counter32	read-only	A summary of all the packet error types above (from missing packets to bad length packets).
PER pwVcCepPerfCurrentESs	1.3.6.1.4.1.99999.52.4.1.5.1.16	PerfCurrentCount	read-only	The counter associated with the number of Errored Seconds encountered.
PER pwVcCepPerfCurrentSESs	1.3.6.1.4.1.99999.52.4.1.5.1.17	PerfCurrentCount	read-only	The counter associated with the number of Severely Errored Seconds encountered.
PER pwVcCepPerfCurrentUASs	1.3.6.1.4.1.99999.52.4.1.5.1.18	PerfCurrentCount	read-only	The counter associated with the number of Unavailable Seconds encountered.
PER pwVcCepPerfCurrentFC	1.3.6.1.4.1.99999.52.4.1.5.1.19	PerfCurrentCount	read-only	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.
pwVcCepPerfIntervalTable	1.3.6.1.4.1.99999.52.4.1.6		not-accessible	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.
pwVcCepPerfIntervalEntry	1.3.6.1.4.1.99999.52.4.1.6.1		not-accessible	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.
U32 pwVcCepPerfIntervalNumber	1.3.6.1.4.1.99999.52.4.1.6.1.1	Unsigned32	not-accessible	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.
T/F pwVcCepPerfIntervalValidData	1.3.6.1.4.1.99999.52.4.1.6.1.2	TruthValue	read-only	This variable indicates if the data for this interval is valid.
INT pwVcCepPerfIntervalReset	1.3.6.1.4.1.99999.52.4.1.6.1.3	INTEGER	read-create	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.
I32 pwVcCepPerfIntervalTimeElapsed	1.3.6.1.4.1.99999.52.4.1.6.1.4	Integer32	read-only	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.
C64 pwVcCepPerfIntervalDbaInPacketsHC	1.3.6.1.4.1.99999.52.4.1.6.1.5	Counter64	read-only	Number of DBA packets received.
C64 pwVcCepPerfIntervalDbaOutPacketsHC	1.3.6.1.4.1.99999.52.4.1.6.1.6	Counter64	read-only	Number of DBA packets sent.
C32 pwVcCepPerfIntervalInNegPtrAdjust	1.3.6.1.4.1.99999.52.4.1.6.1.7	Counter32	read-only	Number of negative pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
C32 pwVcCepPerfIntervalInPosPtrAdjust	1.3.6.1.4.1.99999.52.4.1.6.1.8	Counter32	read-only	Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
C32 pwVcCepPerfIntervalInPtrAdjustSecs	1.3.6.1.4.1.99999.52.4.1.6.1.9	Counter32	read-only	Number of seconds in which a pos or neg pointer adjustment was sent on the SONET path.
C32 pwVcCepPerfIntervalOutNegPtrAdjust	1.3.6.1.4.1.99999.52.4.1.6.1.10	Counter32	read-only	Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
C32 pwVcCepPerfIntervalOutPosPtrAdjust	1.3.6.1.4.1.99999.52.4.1.6.1.11	Counter32	read-only	Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
C32 pwVcCepPerfIntervalOutPtrAdjustSecs	1.3.6.1.4.1.99999.52.4.1.6.1.12	Counter32	read-only	Number of seconds in which a pos or neg pointer adjustment was seen on the SONET path.
I32 pwVcCepPerfIntervalAbsPtrAdjust	1.3.6.1.4.1.99999.52.4.1.6.1.13	Integer32	read-only	Absolute Pointer adjustments is relative adjustment drifts between inbound and outbound streams. It is calculated as absolute value of : ( InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)
C32 pwVcCepPerfIntervalMissingPkts	1.3.6.1.4.1.99999.52.4.1.6.1.14	Counter32	read-only	Number of missing packets (as detected via CEP header sequence number gaps).
C32 pwVcCepPerfIntervalPktsOoseq	1.3.6.1.4.1.99999.52.4.1.6.1.15	Counter32	read-only	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).
C32 pwVcCepPerfIntervalPktsOoRngDropped	1.3.6.1.4.1.99999.52.4.1.6.1.16	Counter32	read-only	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.
C32 pwVcCepPerfIntervalJtrBfrUnderruns	1.3.6.1.4.1.99999.52.4.1.6.1.17	Counter32	read-only	Number of times a packet needed to be played out and the jitter buffer was empty.
C32 pwVcCepPerfIntervalPktsBadLength	1.3.6.1.4.1.99999.52.4.1.6.1.18	Counter32	read-only	Number of packets received larger or smaller than pwVcCepCfgNormalPktLength.
C32 pwVcCepPerfIntervalSummaryErrors	1.3.6.1.4.1.99999.52.4.1.6.1.19	Counter32	read-only	A summary of all the packet error types above (from missing packets to bad length packets).
NUM pwVcCepPerfIntervalESs	1.3.6.1.4.1.99999.52.4.1.6.1.20	PerfIntervalCount	read-only	The counter associated with the number of Errored Seconds encountered.
NUM pwVcCepPerfIntervalSESs	1.3.6.1.4.1.99999.52.4.1.6.1.21	PerfIntervalCount	read-only	The counter associated with the number of Severely Errored Seconds encountered.
NUM pwVcCepPerfIntervalUASs	1.3.6.1.4.1.99999.52.4.1.6.1.22	PerfIntervalCount	read-only	The counter associated with the number of Unavailable Seconds encountered.
NUM pwVcCepPerfIntervalFC	1.3.6.1.4.1.99999.52.4.1.6.1.23	PerfIntervalCount	read-only	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.
pwVcCepPerfTotalTable	1.3.6.1.4.1.99999.52.4.1.7		not-accessible	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.
pwVcCepPerfTotalEntry	1.3.6.1.4.1.99999.52.4.1.7.1		not-accessible	An entry is created in this table by the agent for every entry in the pwVcCep table.
C64 pwVcCepPerfTotalDbaInPacketsHC	1.3.6.1.4.1.99999.52.4.1.7.1.1	Counter64	read-only	Number of DBA packets received.
C64 pwVcCepPerfTotalDbaOutPacketsHC	1.3.6.1.4.1.99999.52.4.1.7.1.2	Counter64	read-only	Number of DBA packets sent.
C32 pwVcCepPerfTotalInNegPtrAdjust	1.3.6.1.4.1.99999.52.4.1.7.1.3	Counter32	read-only	Number of negative pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
C32 pwVcCepPerfTotalInPosPtrAdjust	1.3.6.1.4.1.99999.52.4.1.7.1.4	Counter32	read-only	Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
C32 pwVcCepPerfTotalInPtrAdjustSecs	1.3.6.1.4.1.99999.52.4.1.7.1.5	Counter32	read-only	Number of seconds in which a pos or neg pointer adjustment was sent on the SONET path.
C32 pwVcCepPerfTotalOutNegPtrAdjust	1.3.6.1.4.1.99999.52.4.1.7.1.6	Counter32	read-only	Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
C32 pwVcCepPerfTotalOutPosPtrAdjust	1.3.6.1.4.1.99999.52.4.1.7.1.7	Counter32	read-only	Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
C32 pwVcCepPerfTotalOutPtrAdjustSecs	1.3.6.1.4.1.99999.52.4.1.7.1.8	Counter32	read-only	Number of seconds in which a pos or neg pointer adjustment was seen on the SONET path.
I32 pwVcCepPerfTotalAbsPtrAdjust	1.3.6.1.4.1.99999.52.4.1.7.1.9	Integer32	read-only	Absolute Pointer adjustments is relative adjustment drifts between inbound and outbound streams. It is calculated as absolute value of : ( InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)
C32 pwVcCepPerfTotalMissingPkts	1.3.6.1.4.1.99999.52.4.1.7.1.10	Counter32	read-only	Number of missing packets (as detected via CEP header sequence number gaps).
C32 pwVcCepPerfTotalPktsOoseq	1.3.6.1.4.1.99999.52.4.1.7.1.11	Counter32	read-only	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).
C32 pwVcCepPerfTotalPktsOoRngDropped	1.3.6.1.4.1.99999.52.4.1.7.1.12	Counter32	read-only	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.
C32 pwVcCepPerfTotalJtrBfrUnderruns	1.3.6.1.4.1.99999.52.4.1.7.1.13	Counter32	read-only	Number of times a packet needed to be played out and the jitter buffer was empty.
C32 pwVcCepPerfTotalPktsBadLength	1.3.6.1.4.1.99999.52.4.1.7.1.14	Counter32	read-only	Number of packets received larger or smaller than pwVcCepCfgNormalPktLength.
C32 pwVcCepPerfTotalSummaryErrors	1.3.6.1.4.1.99999.52.4.1.7.1.15	Counter32	read-only	A summary of all the packet error types above (from missing packets to bad length packets).
C32 pwVcCepPerfTotalESs	1.3.6.1.4.1.99999.52.4.1.7.1.16	Counter32	read-only	The counter associated with the number of Errored Seconds encountered. See draft-ietf-pwe3-sonet for definition of ES.
C32 pwVcCepPerfTotalSESs	1.3.6.1.4.1.99999.52.4.1.7.1.17	Counter32	read-only	The counter associated with the number of Severely Errored Seconds. See pwVcCepCfgMissingPktsToSes. Also see draft-ietf-pwe3-sonet for definition.
C32 pwVcCepPerfTotalUASs	1.3.6.1.4.1.99999.52.4.1.7.1.18	Counter32	read-only	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.
C32 pwVcCepPerfTotalFC	1.3.6.1.4.1.99999.52.4.1.7.1.19	Counter32	read-only	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.
TIM pwVcCepPerfTotalDiscontinuityTime	1.3.6.1.4.1.99999.52.4.1.7.1.20	TimeStamp	read-only	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.
pwVcCepConformanceCfgTable	1.3.6.1.4.1.99999.52.4.1.9		not-accessible	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.
pwVcCepConformanceCfgEntry	1.3.6.1.4.1.99999.52.4.1.9.1		not-accessible	The agent MUST create a single entry in this table.
INT pwVcCepConformanceCfgIndex	1.3.6.1.4.1.99999.52.4.1.9.1.1	INTEGER	not-accessible	Any arbitrary number
T/F pwVcCepPerfDbaInPacketsHCTruth	1.3.6.1.4.1.99999.52.4.1.9.1.2	TruthValue	read-only	Tells whether the pwVcCepPerf...DbaInPacketsHC in the pwVcCepPerf...Table is supported.
STR pwVcCepPerfDbaInPacketsHCDesc	1.3.6.1.4.1.99999.52.4.1.9.1.3	SnmpAdminString	read-only	Explanation for pwVcCepPerf...DbaInPacketsHC support in the pwVcCepPerf...Table.
T/F pwVcCepPerfDbaOutPacketsHCTruth	1.3.6.1.4.1.99999.52.4.1.9.1.4	TruthValue	read-only	Tells whether the pwVcCepPerf...DbaOutPacketsHC in the pwVcCepPerf...Table is supported.
STR pwVcCepPerfDbaOutPacketsHCDesc	1.3.6.1.4.1.99999.52.4.1.9.1.5	SnmpAdminString	read-only	Explanation for pwVcCepPerf...DbaOutPacketsHC support in the pwVcCepPerf...Table.
T/F pwVcCepPerfPktsOoseqTruth	1.3.6.1.4.1.99999.52.4.1.9.1.6	TruthValue	read-only	Tells whether the pwVcCepPerf...PktsOoseq in the pwVcCepPerf...Table is supported.
STR pwVcCepPerfPktsOoseqDesc	1.3.6.1.4.1.99999.52.4.1.9.1.7	SnmpAdminString	read-only	Explanation for pwVcCepPerf...PktsOoseq support in the pwVcCepPerf...Table.
T/F pwVcCepPerfPktsOoRngDroppedTruth	1.3.6.1.4.1.99999.52.4.1.9.1.8	TruthValue	read-only	Tells whether the pwVcCepPerf...PktsOoRngDropped in the pwVcCepPerf...Table is supported.
STR pwVcCepPerfPktsOoRngDroppedDesc	1.3.6.1.4.1.99999.52.4.1.9.1.9	SnmpAdminString	read-only	Explanation for pwVcCepPerf...PktsOoRngDropped support in the pwVcCepPerf...Table.
T/F pwVcCepPerfSummaryErrorsTruth	1.3.6.1.4.1.99999.52.4.1.9.1.10	TruthValue	read-only	Tells whether the pwVcCepPerf...SummaryError in the pwVcCepPerf...Table is supported.
STR pwVcCepPerfSummaryErrorsDesc	1.3.6.1.4.1.99999.52.4.1.9.1.11	SnmpAdminString	read-only	Explanation for pwVcCepPerf...SummaryError support in the pwVcCepPerf...Table.
pwVcCepConformance	1.3.6.1.4.1.99999.52.4.2
pwVcCepGroups	1.3.6.1.4.1.99999.52.4.2.1
pwVcCepGroup	1.3.6.1.4.1.99999.52.4.2.1.1			Collection of objects for basic CEP PW config and status.
pwVcCepCfgGroup	1.3.6.1.4.1.99999.52.4.2.1.2			Collection of detailed objects needed to configure CEP PWs.
pwVcCepPerfCurrentGroup	1.3.6.1.4.1.99999.52.4.2.1.3			Collection of statistics objects for CEP PWs.
pwVcCepPerfIntervalGroup	1.3.6.1.4.1.99999.52.4.2.1.4			Collection of statistics objects for CEP PWs.
pwVcCepPerfTotalGroup	1.3.6.1.4.1.99999.52.4.2.1.5			Collection of statistics objects for CEP PWs.
pwVcCepFracGroup	1.3.6.1.4.1.99999.52.4.2.1.6			Collection of fractional SPE groups. These objects are optional and should be supported only if fractional SPE is supported within the network element.
pwVcCepConformanceCfgGroup	1.3.6.1.4.1.99999.52.4.2.1.7			Collection of objects declaring conformance to other objects.
pwVcCepCompliances	1.3.6.1.4.1.99999.52.4.2.2
pwCepModuleCompliance	1.3.6.1.4.1.99999.52.4.2.2.1			The compliance statement for agent that support PW over CEP PSN operation.

RFC description

Manages Pseudowire Circuit Emulation over Packet (CEP) for encapsulating Time Division Multiplexed (TDM) signals over MPLS networks.

Start monitoring vendor-neutral, standards-based IETF PWE3 MIB (Circuit Emulation over Packet) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download PW-CEP-DRAFT04-MIB