PW-MIB
This MIB contains managed object definitions for Pseudo Wire operation as in: Pate, P., et al, <draft-ietf-pwe3- framework>, Xiao, X., et al, <draft-ietf-pwe3- requirements>, Martini, L., et al, <draft-martini- l2circuit-trans-mpls>, and Martini, L., et al, <draft-martini-l2circuit-encap-mpls>. 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 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.
Main OID:
pwVcMIB.1.3.6.1.3.1
81
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
81 total| Object Name |
|---|
pwVcMIBThis MIB contains managed object definitions for Pseudo Wire operation as in: Pate, P., et al, <draft-ietf-pwe3- framework>, Xiao, X., et al, <draft-ietf-pwe3- requirements>, Martini, L., et al, <draft-martini- l2circuit-trans-mpls>, and Martini, L., et al, <draft-martini-l2circuit-encap-mpls>. 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 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. MODULE-IDENTITY .1.3.6.1.3.1 |
pwVcObjects OBJECT IDENTIFIER .1.3.6.1.3.1.1 |
pwVcIndexNextThis object contains an appropriate value to be used for pwVcIndex when creating entries in the pwVcTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwVcIndex for a new entry in the pwVcTable, the manager issues a management protocol retrieval operation to obtain the current value of pwVcIndex. 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.ro Unsigned32 .1.3.6.1.3.1.1.1 |
pwVcTableThis table specifies information for connecting various emulated services to various tunnel type. SEQUENCE OF PwVcEntry .1.3.6.1.3.1.1.2 |
pwVcEntryA row in this table represents an emulated virtual connection (VC) across a packet network. It is indexed by pwVcIndex, which uniquely identifying a singular connection. PwVcEntry .1.3.6.1.3.1.1.2.1 |
pwVcIndexIndex for the conceptual row identifying a VC within this PW Emulation VC table. PwVcIndexType (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.1 |
pwVcTypeThis 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.rw PwVcType (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.2 |
pwVcOwnerSet 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 <draft- draft-martini- l2circuit-trans-mpls> or L2TP control protocol. Value 'other' is used for other types of signaling.rw Enumeration .1.3.6.1.3.1.1.2.1.3 |
pwVcPsnTypeSet 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 pwVcMplsTable, which further define the MPLS PSN configuration. Note: the exact set of PSN types is yet to be worked out by the WG.rw Enumeration .1.3.6.1.3.1.1.2.1.4 |
pwVcSetUpPriorityThis 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 pwVcOperStatus). 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.rw Integer32 .1.3.6.1.3.1.1.2.1.5 |
pwVcHoldingPriorityThis 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 pwVcOperStatus). 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.rw Integer32 .1.3.6.1.3.1.1.2.1.6 |
pwVcInboundModeThis 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.rw Enumeration .1.3.6.1.3.1.1.2.1.7 |
pwVcPeerAddrTypeDenotes 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. pwVcOwner is set to 'manual'.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.3.1.1.2.1.8 |
pwVcPeerAddrThis object conatin 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).rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.3.1.1.2.1.9 |
pwVcIDUsed in the outgoing VC ID field within the 'Virtual Circuit FEC Element' when LDP signaling is used or PW ID AVP for L2TP.rw PwVcIDType (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.10 |
pwVcLocalGroupIDUsed in the Group ID field sent to the peer PWES within the maintenance protocol used for VC setup, zero if not used.rw PwGroupID (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.11 |
pwVcControlWordDefine if the control word will be sent with each packet by the local node.rw TruthValue (SNMPv2-TC) .1.3.6.1.3.1.1.2.1.12 |
pwVcLocalIfMtuIf 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.rw Unsigned32 .1.3.6.1.3.1.1.2.1.13 |
pwVcLocalIfStringEach 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.3.1.1.2.1.14 |
pwVcRemoteGroupIDObtained 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.ro PwGroupID (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.15 |
pwVcRemoteControlWordIf 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.rw Enumeration .1.3.6.1.3.1.1.2.1.16 |
pwVcRemoteIfMtuThe 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.ro Unsigned32 .1.3.6.1.3.1.1.2.1.17 |
pwVcRemoteIfStringIndicate the interface description string as received by the maintenance protocol, MUST be NULL string if not applicable or not known yet.ro SnmpAdminString .1.3.6.1.3.1.1.2.1.18 |
pwVcOutboundVcLabelThe 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.rw Unsigned32 .1.3.6.1.3.1.1.2.1.19 |
pwVcInboundVcLabelThe 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.rw Unsigned32 .1.3.6.1.3.1.1.2.1.20 |
pwVcNameThe canonical name assigned to the VC.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.3.1.1.2.1.21 |
pwVcDescrA textual string containing information about the VC. If there is no description this object contains a zero length string.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.3.1.1.2.1.22 |
pwVcCreateTimeSystem time when this VC was created.ro TimeStamp (SNMPv2-TC) .1.3.6.1.3.1.1.2.1.23 |
pwVcUpTimeNumber of consecutive ticks this VC has been 'up' in both directions together (i.e. 'up' is observed in pwVcOperStatus.)ro TimeTicks (SNMPv2-SMI) .1.3.6.1.3.1.1.2.1.24 |
pwVcAdminStatusThe desired operational status of this VC.rw Enumeration .1.3.6.1.3.1.1.2.1.25 |
pwVcOperStatusIndicates the actual combined operational status of this VC. It is 'up' if both pwVcInboundOperStatus and pwVcOutboundOperStatus 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.ro PwOperStatus (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.26 |
pwVcInboundOperStatusIndicates 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'.ro PwOperStatus (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.27 |
pwVcOutboundOperStatusIndicates 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'.ro PwOperStatus (PW-TC-MIB) .1.3.6.1.3.1.1.2.1.28 |
pwVcTimeElapsedThe 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.ro Integer32 .1.3.6.1.3.1.1.2.1.29 |
pwVcValidIntervalsThe 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 <n> unless the measurement was (re-) started within the last (<n>*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.ro Integer32 .1.3.6.1.3.1.1.2.1.30 |
pwVcRowStatusFor creating, modifying, and deleting this row.rw RowStatus (SNMPv2-TC) .1.3.6.1.3.1.1.2.1.31 |
pwVcStorageTypeThis variable indicates the storage type for this object.rw StorageType (SNMPv2-TC) .1.3.6.1.3.1.1.2.1.32 |
pwVcPerfCurrentTableThis table provides per-VC performance information for the current interval. SEQUENCE OF PwVcPerfCurrentEntry .1.3.6.1.3.1.1.3 |
pwVcPerfCurrentEntryAn entry in this table is created by the agent for every VC. PwVcPerfCurrentEntry .1.3.6.1.3.1.1.3.1 |
pwVcPerfCurrentInHCPacketsHigh capacity counter for number of packets received by the VC (from the PSN) in the current 15 minute interval.ro Counter64 .1.3.6.1.3.1.1.3.1.1 |
pwVcPerfCurrentInHCBytesHigh capacity counter for number of bytes received by the VC (from the PSN) in the current 15 minute interval.ro Counter64 .1.3.6.1.3.1.1.3.1.2 |
pwVcPerfCurrentOutHCPacketsHigh capacity counter for number of packets forwarded by the VC (to the PSN) in the current 15 minute interval.ro Counter64 .1.3.6.1.3.1.1.3.1.3 |
pwVcPerfCurrentOutHCBytesHigh capacity counter for number of bytes forwarded by the VC (to the PSN) in the current 15 minute interval.ro Counter64 .1.3.6.1.3.1.1.3.1.4 |
pwVcPerfIntervalTableThis table provides per-VC performance information for each interval. SEQUENCE OF PwVcPerfIntervalEntry .1.3.6.1.3.1.1.4 |
pwVcPerfIntervalEntryAn entry in this table is created agent for every VC. PwVcPerfIntervalEntry .1.3.6.1.3.1.1.4.1 |
pwVcPerfIntervalNumberA 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. Integer32 .1.3.6.1.3.1.1.4.1.1 |
pwVcPerfIntervalValidDataThis variable indicates if the data for this interval is valid.ro TruthValue (SNMPv2-TC) .1.3.6.1.3.1.1.4.1.2 |
pwVcPerfIntervalTimeElapsedThe 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.ro Integer32 .1.3.6.1.3.1.1.4.1.3 |
pwVcPerfIntervalInHCPacketsHigh capacity counter for number of packets received by the VC (from the PSN) in a particular 15-minute interval.ro Counter64 .1.3.6.1.3.1.1.4.1.4 |
pwVcPerfIntervalInHCBytesHigh capacity counter for number of bytes received by the VC (from the PSN) in a particular 15-minute interval.ro Counter64 .1.3.6.1.3.1.1.4.1.5 |
pwVcPerfIntervalOutHCPacketsHigh capacity counter for number of packets forwarded by the VC (to the PSN) in a particular 15-minute interval.ro Counter64 .1.3.6.1.3.1.1.4.1.6 |
pwVcPerfIntervalOutHCBytesHigh capacity counter for number of bytes forwarded by the VC (to the PSN) in a particular 15-minute interval.ro Counter64 .1.3.6.1.3.1.1.4.1.7 |
pwVcPerfTotalTableThis table provides per-VC Performance information from VC start time. SEQUENCE OF PwVcPerfTotalEntry .1.3.6.1.3.1.1.5 |
pwVcPerfTotalEntryAn entry in this table is created agent for every VC. PwVcPerfTotalEntry .1.3.6.1.3.1.1.5.1 |
pwVcPerfTotalInHCPacketsHigh capacity counter for number of packets received by the VC (from the PSN).ro Counter64 .1.3.6.1.3.1.1.5.1.1 |
pwVcPerfTotalInHCBytesHigh capacity counter for number of bytes received by the VC (from the PSN).ro Counter64 .1.3.6.1.3.1.1.5.1.2 |
pwVcPerfTotalOutHCPacketsHigh capacity counter for number of packets forwarded by the VC (to the PSN).ro Counter64 .1.3.6.1.3.1.1.5.1.3 |
pwVcPerfTotalOutHCBytesHigh capacity counter for number of bytes forwarded by the VC (to the PSN).ro Counter64 .1.3.6.1.3.1.1.5.1.4 |
pwVcPerfTotalDiscontinuityTimeThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.3.1.1.5.1.5 |
pwVcPerfTotalErrorPacketsCounter for number of error at VC level processing, for example packets received with unknown VC label.ro Counter64 .1.3.6.1.3.1.1.6 |
pwVcIdMappingTableThis 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. SEQUENCE OF PwVcIdMappingEntry .1.3.6.1.3.1.1.7 |
pwVcIdMappingEntryAn entry in this table is created by the agent for every VC configured by the pwVcTable. PwVcIdMappingEntry .1.3.6.1.3.1.1.7.1 |
pwVcIdMappingVcTypeThe VC type (indicate the service) of this VC. PwVcType (PW-TC-MIB) .1.3.6.1.3.1.1.7.1.1 |
pwVcIdMappingVcIDThe VC ID of this VC. Zero if the VC is configured manually. PwVcIDType (PW-TC-MIB) .1.3.6.1.3.1.1.7.1.2 |
pwVcIdMappingPeerAddrTypeIP address type of the peer node. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.3.1.1.7.1.3 |
pwVcIdMappingPeerAddrIP address type of the peer node. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.3.1.1.7.1.4 |
pwVcIdMappingVcIndexThe value that represent the VC in the pwVcTable.ro PwVcIndexType (PW-TC-MIB) .1.3.6.1.3.1.1.7.1.5 |
pwVcPeerMappingTableThis 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. SEQUENCE OF PwVcPeerMappingEntry .1.3.6.1.3.1.1.8 |
pwVcPeerMappingEntryAn entry in this table is created by the agent for every VC configured in pwVcTable. PwVcPeerMappingEntry .1.3.6.1.3.1.1.8.1 |
pwVcPeerMappingPeerAddrTypeIP address type of the peer node. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.3.1.1.8.1.1 |
pwVcPeerMappingPeerAddrIP address type of the peer node. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.3.1.1.8.1.2 |
pwVcPeerMappingVcTypeThe VC type (indicate the service) of this VC. PwVcType (PW-TC-MIB) .1.3.6.1.3.1.1.8.1.3 |
pwVcPeerMappingVcIDThe VC ID of this VC. Zero if the VC is configured manually. PwVcIDType (PW-TC-MIB) .1.3.6.1.3.1.1.8.1.4 |
pwVcPeerMappingVcIndexThe value that represent the VC in the pwVcTable.ro PwVcIndexType (PW-TC-MIB) .1.3.6.1.3.1.1.8.1.5 |
pwVcConformance OBJECT IDENTIFIER .1.3.6.1.3.1.2 |
pwVcGroups OBJECT IDENTIFIER .1.3.6.1.3.1.2.1 |
pwVcGroupCollection of objects needed for PW VC configuration. Unknown .1.3.6.1.3.1.2.1.1 |
pwVcPeformanceGroupCollection of objects needed for PW VC performance. Unknown .1.3.6.1.3.1.2.1.2 |
pwVcMappingTablesGroupCollection of objects contained in the reverse mapping tables. Unknown .1.3.6.1.3.1.2.1.3 |
pwVcCompliances OBJECT IDENTIFIER .1.3.6.1.3.1.2.2 |
pwModuleComplianceThe compliance statement for agent that support PW operation. Unknown .1.3.6.1.3.1.2.2.1 |