This 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.
ication 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.
cpwVcUp
.1.3.6.1.4.1.9.10.106.2.2
ication 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.