CISCO-IETF-PW-MIB

MIB Reference — IPNetwork Monitor

All MIBsCISCO-IETF-PW-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2004-03-17

Category: Cisco Devices, Pseudowire

Description:

Manages pseudowire emulation edge-to-edge (PWE3) connections over MPLS and IP transport networks.

Imported Objects

From CISCO-IETF-PW-TC-MIB

CpwGroupID
CpwOperStatus
CpwVcIDType
CpwVcIndexType
CpwVcType

From CISCO-SMI

ciscoExperimentOBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter64
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32
experimental

From SNMPv2-TC

RowStatus
StorageType
TimeStamp
TruthValue

What Is CISCO-IETF-PW-MIB?

CISCO-IETF-PW-MIB is a Cisco implementation of the IETF pseudowire emulation edge-to-edge (PWE3) draft standard, part of the MPLS/carrier-Ethernet transport technology area. It defines managed objects for configuring and monitoring pseudowire connections that emulate a Layer 2 circuit over an MPLS or IP packet-switched network, including PW type, encapsulation, and state. Because pseudowires are software-defined transport constructs, this module is primarily about monitoring software/service status rather than physical hardware: PW operational/administrative state, up/down transitions, and VC-type-specific parameters that reveal service faults. It has an explicit dependency, deferring VC-type-specific detail to companion PSN-specific and VC-specific MIBs (e.g. per the referenced pwe3-framework and l2circuit-trans-mpls drafts) that share its index structure. It is typically deployed on Cisco provider-edge routers delivering Layer 2 VPN / pseudowire services across an MPLS core, where engineers load the CISCO-IETF-PW-MIB module into their network management system to track pseudowire health alongside the companion PSN- and VC-specific MIBs.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-IETF-PW-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.

What Can Be Monitored

  • pseudowire operational state
  • pseudowire administrative state
  • VC type configuration
  • PSN-specific pseudowire parameters

Supported Devices

  • Cisco ASR 9001 — compact chassis in the ASR 9000 series, current flagship MPLS/pseudowire provider-edge router

Monitoring Examples

No sample runtime objects were provided for this module in the supplied data, so a concrete polling scenario cannot be grounded in real object names here; in general use an operator would monitor per-pseudowire administrative/operational status and VC-type-specific counters to detect a pseudowire that has gone down or is flapping between PSN and attachment circuit, using the shared index into the PSN-specific and VC-specific tables described in the module.

OIDs
OID symbolicOID numericTypeAccessDescription
cpwVcMIB1.3.6.1.4.1.9.3.106This MIB contains managed object definitions for Pseudo Wire operation as in: Pate, P., et al, , Xiao, X., et al, , Martini, L., et al, , and Martini, L., et al, . The indexes for this MIB are also used to index the PSN- specific tables and the VC-specific tables. The VC Type dictates which VC-specific MIB to use. For example, a 'cep' VC Type requires the use the configuration and status tables within the CEP-MIB. This MIB enable the use of any underlying packet switched network (PSN). Specific tables for the MPLS PSN is currently defined in a separate CISCO-IETF-PW-MPLS-MIB. Tables to support other PSNs (IP, L2TP for example) will be added to this MIB in future revisions. At the time of publication of this version, there are no PWE3 WG documents for all features and objects in this MIB, and the MIB is therefore subject to change based on the WG progress.
cpwVcObjects1.3.6.1.4.1.9.3.106.1
U32 cpwVcIndexNext1.3.6.1.4.1.9.3.106.1.1Unsigned32read-onlyThis object contains an appropriate value to be used for cpwVcIndex when creating entries in the cpwVcTable. The value 0 indicates that no unassigned entries are available. To obtain the value of cpwVcIndex for a new entry in the cpwVcTable, the manager issues a management protocol retrieval operation to obtain the current value of cpwVcIndex. 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.
cpwVcTable1.3.6.1.4.1.9.3.106.1.2not-accessibleThis table specifies information for connecting various emulated services to various tunnel type.
cpwVcEntry1.3.6.1.4.1.9.3.106.1.2.1not-accessibleA row in this table represents an emulated virtual connection (VC) across a packet network. It is indexed by cpwVcIndex, which uniquely identifying a singular connection.
CPW cpwVcIndex1.3.6.1.4.1.9.3.106.1.2.1.1CpwVcIndexTypenot-accessibleIndex for the conceptual row identifying a VC within this PW Emulation VC table.
CPW cpwVcType1.3.6.1.4.1.9.3.106.1.2.1.2CpwVcTyperead-createThis value indicate the service to be carried over this VC. Note: the exact set of VC types is yet to be worked out by the WG.
INT cpwVcOwner1.3.6.1.4.1.9.3.106.1.2.1.3INTEGERread-createSet by the operator to indicate the protocol responsible for establishing this VC. Value 'manual' is used in all cases where no maintenance protocol (PW signaling) is used to set-up the VC, i.e. require configuration of entries in the VC tables including VC labels, etc. The value 'maintenanceProtocol' is used in case of standard signaling of the VC for the specific PSN, for example LDP for MPLS PSN as specified in or L2TP control protocol. Value 'other' is used for other types of signaling.
INT cpwVcPsnType1.3.6.1.4.1.9.3.106.1.2.1.4INTEGERread-createSet by the operator to indicate the PSN type on which this VC will be carried. Based on this object, the relevant PSN table entries are created in the in the PSN specific MIB modules. For example, if mpls(1) is defined, the agent create an entry in cpwVcMplsTable, which further define the MPLS PSN configuration. Note: the exact set of PSN types is yet to be worked out by the WG.
I32 cpwVcSetUpPriority1.3.6.1.4.1.9.3.106.1.2.1.5Integer32read-createThis object define the relative set-up priority of the VC in a lowest-to-highest fashion, where 0 is the highest priority. VCs with the same priority are treated with equal priority. Dropped VC will be set 'dormant' (as indicated in cpwVcOperStatus). This value is significant if there are competing resources between VCs and the implementation support this feature. If not supported or not relevant, the value of zero MUST be used.
I32 cpwVcHoldingPriority1.3.6.1.4.1.9.3.106.1.2.1.6Integer32read-createThis object define the relative holding priority of the VC in a lowest-to-highest fashion, where 0 is the highest priority. VCs with the same priority are treated with equal priority. Dropped VC will be set 'dormant' (as indicated in cpwVcOperStatus). This value is significant if there are competing resources between VCs and the implementation support this feature. If not supported or not relevant, the value of zero MUST be used.
INT cpwVcInboundMode1.3.6.1.4.1.9.3.106.1.2.1.7INTEGERread-createThis object is used to enable greater security for implementation that use per platform VC label space. In strict mode, packets coming from the PSN are accepted only from tunnels that are associated to the same VC via the inbound tunnel table in the case of MPLS, or as identified by the source IP address in case of L2TP or IP PSN. The entries in the inbound tunnel table are either explicitly configured or implicitly known by the maintenance protocol used for VC set-up. If such association is not known, not configured or not desired, loose mode should be configured, and the node should accept the packet based on the VC label only regardless of the outer tunnel used to carry the VC.
IPt cpwVcPeerAddrType1.3.6.1.4.1.9.3.106.1.2.1.8InetAddressTyperead-createDenotes the address type of the peer node maintenance protocol (signaling) address if PW maintenance protocol is used for the VC creation. It should be set to 'unknown' if PE/PW maintenance protocol is not used, i.e. cpwVcOwner is set to 'manual'.
IP cpwVcPeerAddr1.3.6.1.4.1.9.3.106.1.2.1.9InetAddressread-createThis object contains the value of of the peer node address of the PW/PE maintenance protocol entity. This object should contain a value of 0 if not relevant (manual configuration of the VC).
CPW cpwVcID1.3.6.1.4.1.9.3.106.1.2.1.10CpwVcIDTyperead-createUsed in the outgoing VC ID field within the 'Virtual Circuit FEC Element' when LDP signaling is used or PW ID AVP for L2TP.
CPW cpwVcLocalGroupID1.3.6.1.4.1.9.3.106.1.2.1.11CpwGroupIDread-createUsed in the Group ID field sent to the peer PWES within the maintenance protocol used for VC setup, zero if not used.
T/F cpwVcControlWord1.3.6.1.4.1.9.3.106.1.2.1.12TruthValueread-createDefine if the control word will be sent with each packet by the local node.
U32 cpwVcLocalIfMtu1.3.6.1.4.1.9.3.106.1.2.1.13Unsigned32read-createIf not equal zero, the optional IfMtu object in the maintenance protocol will be sent with this value, representing the locally supported MTU size over the interface (or the virtual interface) associated with the VC.
T/F cpwVcLocalIfString1.3.6.1.4.1.9.3.106.1.2.1.14TruthValueread-createEach VC is associated to an interface (or a virtual interface) in the ifTable of the node as part of the service configuration. This object defines if the maintenance protocol will send the interface's name as appears on the ifTable in the name object as part of the maintenance protocol. If set to false, the optional element will not be sent.
CPW cpwVcRemoteGroupID1.3.6.1.4.1.9.3.106.1.2.1.15CpwGroupIDread-onlyObtained from the Group ID field as received via the maintenance protocol used for VC setup, zero if not used. Value of 0xFFFF shall be used if the object is yet to be defined by the VC maintenance protocol.
INT cpwVcRemoteControlWord1.3.6.1.4.1.9.3.106.1.2.1.16INTEGERread-createIf maintenance protocol is used for VC establishment, this parameter indicates the received status of the control word usage, i.e. if packets will be received with control word or not. The value of 'notYetKnown' is used while the maintenance protocol has not yet received the indication from the remote node. In manual configuration of the VC this parameters indicate to the local node what is the expected encapsulation for the received packets.
U32 cpwVcRemoteIfMtu1.3.6.1.4.1.9.3.106.1.2.1.17Unsigned32read-onlyThe remote interface MTU as (optionally) received from the remote node via the maintenance protocol. Should be zero if this parameter is not available or not used.
STR cpwVcRemoteIfString1.3.6.1.4.1.9.3.106.1.2.1.18SnmpAdminStringread-onlyIndicate the interface description string as received by the maintenance protocol, MUST be NULL string if not applicable or not known yet.
U32 cpwVcOutboundVcLabel1.3.6.1.4.1.9.3.106.1.2.1.19Unsigned32read-createThe VC label used in the outbound direction (i.e. toward the PSN). It may be set up manually if owner is 'manual' or automatically otherwise. Examples: For MPLS PSN, it represents the 20 bits of VC tag, for L2TP it represent the 32 bits Session ID. If the label is not yet known (signaling in process), the object should return a value of 0xFFFF.
U32 cpwVcInboundVcLabel1.3.6.1.4.1.9.3.106.1.2.1.20Unsigned32read-createThe VC label used in the inbound direction (i.e. packets received from the PSN. It may be set up manually if owner is 'manual' or automatically otherwise. Examples: For MPLS PSN, it represents the 20 bits of VC tag, for L2TP it represent the 32 bits Session ID. If the label is not yet known (signaling in process), the object should return a value of 0xFFFF.
STR cpwVcName1.3.6.1.4.1.9.3.106.1.2.1.21SnmpAdminStringread-createThe canonical name assigned to the VC.
STR cpwVcDescr1.3.6.1.4.1.9.3.106.1.2.1.22SnmpAdminStringread-createA textual string containing information about the VC. If there is no description this object contains a zero length string.
TIM cpwVcCreateTime1.3.6.1.4.1.9.3.106.1.2.1.23TimeStampread-onlySystem time when this VC was created.
TIK cpwVcUpTime1.3.6.1.4.1.9.3.106.1.2.1.24TimeTicksread-onlyNumber of consecutive ticks this VC has been 'up' in both directions together (i.e. 'up' is observed in cpwVcOperStatus.)
INT cpwVcAdminStatus1.3.6.1.4.1.9.3.106.1.2.1.25INTEGERread-createThe desired operational status of this VC.
CPW cpwVcOperStatus1.3.6.1.4.1.9.3.106.1.2.1.26CpwOperStatusread-onlyIndicates the actual combined operational status of this VC. It is 'up' if both cpwVcInboundOperStatus and cpwVcOutboundOperStatus are in 'up' state. For all other values, if the VCs in both directions are of the same value it reflects that value, otherwise it is set to the most severe status out of the two statuses. The order of severance from most severe to less severe is: unknown, notPresent, down, lowerLayerDown, dormant, testing, up. The operator may consult the per direction OperStatus for fault isolation per direction.
CPW cpwVcInboundOperStatus1.3.6.1.4.1.9.3.106.1.2.1.27CpwOperStatusread-onlyIndicates the actual operational status of this VC in the inbound direction. - down: if PW signaling has not yet finished, or indications available at the service level indicate that the VC is not passing packets. - testing: if AdminStatus at the VC level is set to test. - dormant: The VC is not available because of the required resources are occupied VC with higher priority VCs . - notPresent: Some component is missing to accomplish the set up of the VC. - lowerLayerDown: The underlying PSN is not in OperStatus 'up'.
CPW cpwVcOutboundOperStatus1.3.6.1.4.1.9.3.106.1.2.1.28CpwOperStatusread-onlyIndicates the actual operational status of this VC in the outbound direction - down: if PW signaling has not yet finished, or indications available at the service level indicate that the VC is not passing packets. - testing: if AdminStatus at the VC level is set to test. - dormant: The VC is not available because of the required resources are occupied VC with higher priority VCs . - notPresent: Some component is missing to accomplish the set up of the VC. - lowerLayerDown: The underlying PSN is not in OperStatus 'up'.
I32 cpwVcTimeElapsed1.3.6.1.4.1.9.3.106.1.2.1.29Integer32read-onlyThe 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 cpwVcValidIntervals1.3.6.1.4.1.9.3.106.1.2.1.30Integer32read-onlyThe number of previous 15-minute intervals for which data was collected. An agent with PW 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.
ROW cpwVcRowStatus1.3.6.1.4.1.9.3.106.1.2.1.31RowStatusread-createFor creating, modifying, and deleting this row.
STO cpwVcStorageType1.3.6.1.4.1.9.3.106.1.2.1.32StorageTyperead-createThis variable indicates the storage type for this object.
cpwVcPerfCurrentTable1.3.6.1.4.1.9.3.106.1.3not-accessibleThis table provides per-VC performance information for the current interval.
cpwVcPerfCurrentEntry1.3.6.1.4.1.9.3.106.1.3.1not-accessibleAn entry in this table is created by the agent for every VC.
C64 cpwVcPerfCurrentInHCPackets1.3.6.1.4.1.9.3.106.1.3.1.1Counter64read-onlyHigh capacity counter for number of packets received by the VC (from the PSN) in the current 15 minute interval.
C64 cpwVcPerfCurrentInHCBytes1.3.6.1.4.1.9.3.106.1.3.1.2Counter64read-onlyHigh capacity counter for number of bytes received by the VC (from the PSN) in the current 15 minute interval.
C64 cpwVcPerfCurrentOutHCPackets1.3.6.1.4.1.9.3.106.1.3.1.3Counter64read-onlyHigh capacity counter for number of packets forwarded by the VC (to the PSN) in the current 15 minute interval.
C64 cpwVcPerfCurrentOutHCBytes1.3.6.1.4.1.9.3.106.1.3.1.4Counter64read-onlyHigh capacity counter for number of bytes forwarded by the VC (to the PSN) in the current 15 minute interval.
cpwVcPerfIntervalTable1.3.6.1.4.1.9.3.106.1.4not-accessibleThis table provides per-VC performance information for each interval.
cpwVcPerfIntervalEntry1.3.6.1.4.1.9.3.106.1.4.1not-accessibleAn entry in this table is created agent for every VC.
I32 cpwVcPerfIntervalNumber1.3.6.1.4.1.9.3.106.1.4.1.1Integer32not-accessibleA number N, between 1 and 96, 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 to 32. The maximum range of N is 1 through 96.
T/F cpwVcPerfIntervalValidData1.3.6.1.4.1.9.3.106.1.4.1.2TruthValueread-onlyThis variable indicates if the data for this interval is valid.
I32 cpwVcPerfIntervalTimeElapsed1.3.6.1.4.1.9.3.106.1.4.1.3Integer32read-onlyThe 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 cpwVcPerfIntervalInHCPackets1.3.6.1.4.1.9.3.106.1.4.1.4Counter64read-onlyHigh capacity counter for number of packets received by the VC (from the PSN) in a particular 15-minute interval.
C64 cpwVcPerfIntervalInHCBytes1.3.6.1.4.1.9.3.106.1.4.1.5Counter64read-onlyHigh capacity counter for number of bytes received by the VC (from the PSN) in a particular 15-minute interval.
C64 cpwVcPerfIntervalOutHCPackets1.3.6.1.4.1.9.3.106.1.4.1.6Counter64read-onlyHigh capacity counter for number of packets forwarded by the VC (to the PSN) in a particular 15-minute interval.
C64 cpwVcPerfIntervalOutHCBytes1.3.6.1.4.1.9.3.106.1.4.1.7Counter64read-onlyHigh capacity counter for number of bytes forwarded by the VC (to the PSN) in a particular 15-minute interval.
cpwVcPerfTotalTable1.3.6.1.4.1.9.3.106.1.5not-accessibleThis table provides per-VC Performance information from VC start time.
cpwVcPerfTotalEntry1.3.6.1.4.1.9.3.106.1.5.1not-accessibleAn entry in this table is created agent for every VC.
C64 cpwVcPerfTotalInHCPackets1.3.6.1.4.1.9.3.106.1.5.1.1Counter64read-onlyHigh capacity counter for number of packets received by the VC (from the PSN).
C64 cpwVcPerfTotalInHCBytes1.3.6.1.4.1.9.3.106.1.5.1.2Counter64read-onlyHigh capacity counter for number of bytes received by the VC (from the PSN).
C64 cpwVcPerfTotalOutHCPackets1.3.6.1.4.1.9.3.106.1.5.1.3Counter64read-onlyHigh capacity counter for number of packets forwarded by the VC (to the PSN).
C64 cpwVcPerfTotalOutHCBytes1.3.6.1.4.1.9.3.106.1.5.1.4Counter64read-onlyHigh capacity counter for number of bytes forwarded by the VC (to the PSN).
TIM cpwVcPerfTotalDiscontinuityTime1.3.6.1.4.1.9.3.106.1.5.1.5TimeStampread-onlyThe value of sysUpTime on the most recent occasion at which any one or more of this row 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.
C64 cpwVcPerfTotalErrorPackets1.3.6.1.4.1.9.3.106.1.6Counter64read-onlyCounter for number of error at VC level processing, for example packets received with unknown VC label.
cpwVcIdMappingTable1.3.6.1.4.1.9.3.106.1.7not-accessibleThis table provides reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs.
cpwVcIdMappingEntry1.3.6.1.4.1.9.3.106.1.7.1not-accessibleAn entry in this table is created by the agent for every VC configured by the cpwVcTable.
CPW cpwVcIdMappingVcType1.3.6.1.4.1.9.3.106.1.7.1.1CpwVcTypenot-accessibleThe VC type (indicate the service) of this VC.
CPW cpwVcIdMappingVcID1.3.6.1.4.1.9.3.106.1.7.1.2CpwVcIDTypenot-accessibleThe VC ID of this VC. Zero if the VC is configured manually.
IPt cpwVcIdMappingPeerAddrType1.3.6.1.4.1.9.3.106.1.7.1.3InetAddressTypenot-accessibleIP address type of the peer node.
IP cpwVcIdMappingPeerAddr1.3.6.1.4.1.9.3.106.1.7.1.4InetAddressnot-accessibleIP address type of the peer node.
CPW cpwVcIdMappingVcIndex1.3.6.1.4.1.9.3.106.1.7.1.5CpwVcIndexTyperead-onlyThe value that represent the VC in the cpwVcTable.
cpwVcPeerMappingTable1.3.6.1.4.1.9.3.106.1.8not-accessibleThis table provides reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs.
cpwVcPeerMappingEntry1.3.6.1.4.1.9.3.106.1.8.1not-accessibleAn entry in this table is created by the agent for every VC configured in cpwVcTable.
IPt cpwVcPeerMappingPeerAddrType1.3.6.1.4.1.9.3.106.1.8.1.1InetAddressTypenot-accessibleIP address type of the peer node.
IP cpwVcPeerMappingPeerAddr1.3.6.1.4.1.9.3.106.1.8.1.2InetAddressnot-accessibleIP address type of the peer node.
CPW cpwVcPeerMappingVcType1.3.6.1.4.1.9.3.106.1.8.1.3CpwVcTypenot-accessibleThe VC type (indicate the service) of this VC.
CPW cpwVcPeerMappingVcID1.3.6.1.4.1.9.3.106.1.8.1.4CpwVcIDTypenot-accessibleThe VC ID of this VC. Zero if the VC is configured manually.
CPW cpwVcPeerMappingVcIndex1.3.6.1.4.1.9.3.106.1.8.1.5CpwVcIndexTyperead-onlyThe value that represent the VC in the cpwVcTable.
T/F cpwVcUpDownNotifEnable1.3.6.1.4.1.9.3.106.1.9TruthValueread-writeIf this object is set to true(1), then it enables the emission of cpwVcUp and cpwVcDown notifications; otherwise these notifications are not emitted.
U32 cpwVcNotifRate1.3.6.1.4.1.9.3.106.1.10Unsigned32read-writeThis object defines the maximum number of PW VC notifications that can be emitted from the device per second.
cpwVcNotifications1.3.6.1.4.1.9.3.106.2
NTF cpwVcDown1.3.6.1.4.1.9.3.106.2.1This notification is generated when the cpwVcOperStatus object for one or more contiguous entries in cpwVcTable are about to enter the down(2) state from some other state. The included values of cpwVcOperStatus MUST all be set equal to this down(2) state. The two instances of cpwVcOperStatus in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of cross-connects have transitioned into the down(2) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single cross-connect entry, then the instance identifier (and values) of the two cpwVcOperStatus objects MUST be identical.
NTF cpwVcUp1.3.6.1.4.1.9.3.106.2.2This notification is generated when the cpwVcOperStatus object for one or more contiguous entries in cpwVcTable are about to enter the up(1) state from some other state. The included values of cpwVcOperStatus MUST both be set equal to this new state (i.e: up(1)). The two instances of cpwVcOperStatus in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of cross-connects have transitioned into the up(1) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single cross-connect entry, then the instance identifier (and values) of the two cpwVcOperStatus objects MUST be the identical.
cpwVcConformance1.3.6.1.4.1.9.3.106.3
cpwVcGroups1.3.6.1.4.1.9.3.106.3.1
cpwVcGroup1.3.6.1.4.1.9.3.106.3.1.1Collection of objects needed for PW VC configuration.
cpwVcPeformanceGroup1.3.6.1.4.1.9.3.106.3.1.2Collection of objects needed for PW VC performance.
cpwVcMappingTablesGroup1.3.6.1.4.1.9.3.106.3.1.3Collection of objects contained in the reverse mapping tables.
cpwVcNotificationsGroup1.3.6.1.4.1.9.3.106.3.1.4Set of notifications implemented in this module. None is mandatory.
cpwVcCompliances1.3.6.1.4.1.9.3.106.3.2
cpwModuleCompliance1.3.6.1.4.1.9.3.106.3.2.1The compliance statement for agent that support PW operation.

RFC description

Cisco implementation of Pseudowire (PW) management MIB for monitoring MPLS Pseudowires and virtual circuits as defined in IETF standards.

Start monitoring Cisco ASR 9000 series MPLS/pseudowire provider-edge router 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 CISCO-IETF-PW-MIB