HPN-ICF-MPLSOAM-MIB

All MIBs › HPN-ICF-MPLSOAM-MIB

Last Updated: 2007-03-31

Category: Technology: OAM, Vendor: H3C/HH3C, Vendor: HP/HPE

Description: Manages MPLS OAM BFD/LSP-ping detection and continuity-check sessions on HP/Comware MPLS networks.

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 HPN-ICF-MPLSOAM-MIB?

HPN-ICF-MPLSOAM-MIB is an HP Networking vendor-specific MIB (registered under the shared hpnicf enterprise branch used by HP/H3C Comware-based platforms) that models MPLS OAM continuity-check and failure-detection sessions -- the CV (Connectivity Verification) and FFD (Fast Failure Detection) mechanisms defined by ITU-T Y.1711 -- for monitoring the health of MPLS Label Switched Paths. It exposes global OAM enable/trap state (hpnicfMplsOamCapability, hpnicfMplsOamTrapOpen) and per-LSP ingress/egress session tables (hpnicfMplsOamIgrTable, hpnicfMplsOamEgrTable) carrying detect type (CV/FFD), detect frequency, reverse-LSP configuration for Backward Defect Indication, and a defect-type object (HpnicfMplsOAMDefectType) enumerating specific failure conditions such as loss of connectivity verification, TTSI mismatch/mismerge, or excess CV/FFD rate. This lets an operator confirm each monitored LSP is actively defect-free and, when it is not, quickly identify the specific OAM defect category causing the fault. It depends on the vendor's HPN-ICF-OID-MIB registration branch and standard SNMPv2-SMI/TC constructs. It is deployed on HP Networking (Comware-based) MPLS-capable routers acting as LSRs, and engineers evaluating the HPN-ICF-MPLSOAM-MIB MIB for their monitoring stack can map each ingress/egress table row directly to a specific LSP's OAM session.

IPNetwork Monitor allows you to monitor SNMP objects defined in HPN-ICF-MPLSOAM-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

HP Networking (Comware-based) MPLS-capable routers/LSRs

Monitoring Examples

An operator polls hpnicfMplsOamIgrTable for a monitored LSP to check hpnicfMplsOamIgrDefectType; a value other than noDefect(11) -- for example dLOCV(3), loss of connectivity verification -- combined with an hpnicfMplsOamIgrLSPInDefect notification would indicate the LSP has lost end-to-end continuity and traffic on that path may be black-holed.

What Can Be Monitored

global MPLS OAM capability and trap-enable state
per-LSP ingress/egress OAM enable state
CV/FFD detect type and frequency configuration
reverse-LSP (BDI) type and name
OAM defect-type indication per LSP
in-defect/out-of-defect notifications

Imported Objects

From HPN-ICF-OID-MIB

hpnicfCommon

OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
hpnicfMplsOam	1.3.6.1.4.1.11.2.14.11.15.2.79			This MIB contains objects to configure OAM module. The Operation, Administration and Maintenance (OAM) is an effective means for decreasing the cost of network maintenance. The MPLS OAM is used to administrate and maintain MPLS.
hpnicfMplsOamScalarGroup	1.3.6.1.4.1.11.2.14.11.15.2.79.1
T/F hpnicfMplsOamCapability	1.3.6.1.4.1.11.2.14.11.15.2.79.1.1	TruthValue	read-write	Whether OAM is globally capable. false: incapable; true: capable; The default value is incapable.
T/F hpnicfMplsOamTrapOpen	1.3.6.1.4.1.11.2.14.11.15.2.79.1.2	TruthValue	read-write	Whether OAM trap is globally enabled. false: disable; true: enable; The default value is disable.
hpnicfMplsOamTable	1.3.6.1.4.1.11.2.14.11.15.2.79.2
hpnicfMplsOamIgrTable	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1		not-accessible	This table specifies per-LSP MPLS OAM ingress capability and associated information, such as IgrLspName and IgrDetType.
hpnicfMplsOamIgrEntry	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1		not-accessible	An entry in this table is created by an LSR for every LSP capable of supporting MPLS OAM at ingress.
U32 hpnicfMplsOamIgrIndex	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.1	Unsigned32	not-accessible	This is an unique index for an OAM ingress entry in the OAM table.
OCT hpnicfMplsOamIgrLspName	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.2	OCTET STRING	read-create	The name of an LSP. It means the LSP name of the detected LSP.
INT hpnicfMplsOamIgrDetectType	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.3	INTEGER	read-create	There are two types of OAM packets, CV and FFD. The CV flow is generated at the source LSR of the LSP with a nominal frequency of 1/s and terminated at the sink LSR of the LSP. FFD provides failure detection option for an LSP independent of the CV based availability model and is not tied to the CV insertion rate. Insertion rates at 1/s or faster may also be used. The CV/FFD packet contains a network-unique identifier (TTSI) so that all types of defects can be detected. 1: CV; 2: FFD.
HPN hpnicfMplsOamIgrDetectFreq	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.4	HpnicfMplsOAMDetectFreq	read-create	Indication of the OAM's frequent type.
INT hpnicfMplsOamIgrRevType	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.5	INTEGER	read-create	When an LSP is found to be in defect, the sink LSR of the LSP should send BDI to inform the source LSR of the LSP, the BDI is transferred through the reverse LSP. The type of reverse LSP can be private or shared. If private, then the reverse LSP can be used only by the oam ingress; If shared, the reverse LSP which is shared between many forward LSPs, whose source LSRs are the same and sink LSRs are the same. 1: private; 2: share.
OCT hpnicfMplsOamIgrRevLspName	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.6	OCTET STRING	read-create	The object indicates the name of the reverse LSP.
I32 hpnicfMplsOamIgrLspId	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.7	Integer32	read-create	For ingress, the object indicates the lsp ID of the detected LSP.
T/F hpnicfMplsOamIgrEnable	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.8	TruthValue	read-create	Whether one LSP is OAM enable. If disable, LSP is not monitored; If enable, CV/FFD is generated at the source LSR of the LSP and checked at the sink LSR of the LSP, and user can set other configuration. false: The OAM function is disabled on the ingress; true: The OAM function is enabled on the ingress.
HPN hpnicfMplsOamIgrDefectType	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.9	HpnicfMplsOAMDefectType	read-only	Indication of the OAM's defect type.
ROW hpnicfMplsOamIgrRowStatus	1.3.6.1.4.1.11.2.14.11.15.2.79.2.1.1.10	RowStatus	read-create	This object is responsible for managing the creation, deletion and modification of rows, which support active status and CreatAndGo, destroy operation. To create a new row, hpnicfMplsOamIgrLspName, hpnicfMplsOamIgrDetectType, hpnicfMplsOamIgrDetectFreq, hpnicfMplsOamIgrRevType, hpnicfMplsOamIgrRevLspName, and hpnicfMplsOamIgrLspId must be specified.
hpnicfMplsOamEgrTable	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2		not-accessible	This table specifies per-LSP MPLS OAM capability and associated information, such as DetectType, DetectFrequency.
hpnicfMplsOamEgrEntry	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1		not-accessible	An entry in this table is created by an LSR for every LSP capable of supporting MPLS OAM at egress.
U32 hpnicfMplsOamEgrIndex	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.1	Unsigned32	not-accessible	This is a unique index for an OAM egress entry in the OAM table.
OCT hpnicfMplsOamEgrLspName	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.2	OCTET STRING	read-create	The object indicates the name of static LSP at egress.
INT hpnicfMplsOamEgrDetectType	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.3	INTEGER	read-create	There are two types of OAM packets, CV and FFD. The CV flow is generated at the source LSR of the LSP with a nominal frequency of 1/s and terminated at the sink LSR of the LSP. FFD provides failure detection option for an LSP independent of the CV based availability model and is not tied to the CV insertion rate. Insertion rates at 1/s or faster may also be used. The CV/FFD packet contains a network-unique identifier (TTSI) so that all types of defects can be detected. 1: CV; 2: FFD.
HPN hpnicfMplsOamEgrDetectFreq	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.4	HpnicfMplsOAMDetectFreq	read-create	Indication of the OAM's frequent type.
INT hpnicfMplsOamEgrRevType	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.5	INTEGER	read-create	When an LSP is found to be in defect, the sink LSR of the LSP should send BDI to inform the source LSR of the LSP, the BDI is transferred through the reverse LSP. The type of reverse LSP can be private or shared. If private, then the reverse LSP can be used only when the only LSP in defect; If shared, the reverse LSP, which is shared between many forward LSPs that have the same source LSRs and sink LSRs. 1: private; 2: share.
OCT hpnicfMplsOamEgrRevLspName	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.6	OCTET STRING	read-create	The object indicates the name of a reverse static-lsp.
IP hpnicfMplsOamEgrLsrId	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.7	IpAddress	read-create	The object indicates the Ingress LSR ID of the LSP.
I32 hpnicfMplsOamEgrLspId	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.8	Integer32	read-create	The object indicates the the Ingress session lsp ID of the detected static-LSP.
T/F hpnicfMplsOamEgrEnable	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.9	TruthValue	read-create	Whether one LSP is enabled with OAM. If disable, LSP is not monitored; If enable, CV/FFD is generated at the source LSR of the LSP and checked at the sink LSR of the LSP, and user can set other configuration. false: The OAM function is disabled on the egress; true: The OAM function is enabled on the egress.
HPN hpnicfMplsOamEgrDefectType	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.10	HpnicfMplsOAMDefectType	read-only	Indication of the OAM's defect type.
ROW hpnicfMplsOamEgrRowStatus	1.3.6.1.4.1.11.2.14.11.15.2.79.2.2.1.11	RowStatus	read-create	This object is responsible for managing the creation, deletion and modification of rows, which support active status and CreatAndGo, destroy operation. To create a new row, hpnicfMplsOamEgrLspName, hpnicfMplsOamEgrDetectType, hpnicfMplsOamEgrDetectFreq, hpnicfMplsOamEgrRevType, hpnicfMplsOamEgrRevLspName, hpnicfMplsOamEgrLsrId and hpnicfMplsOamEgrLspId must be specified.
hpnicfMplsOamNotifications	1.3.6.1.4.1.11.2.14.11.15.2.79.3
NTF hpnicfMplsOamIgrLSPOutDefect	1.3.6.1.4.1.11.2.14.11.15.2.79.3.1			This notification is generated when the LSP is found out of the defect state at the LSP ingress.
NTF hpnicfMplsOamIgrLSPInDefect	1.3.6.1.4.1.11.2.14.11.15.2.79.3.2			This notification is generated when the LSP is found in the defect state at the LSP ingress.
NTF hpnicfMplsOamEgrLSPOutDefect	1.3.6.1.4.1.11.2.14.11.15.2.79.3.3			This notification is generated when the LSP is found out of the defect state at the LSP egress.
NTF hpnicfMplsOamEgrLSPInDefect	1.3.6.1.4.1.11.2.14.11.15.2.79.3.4			This notification is generated when the LSP is found in the defect state at the LSP egress.

RFC description

HP/Arista Networks SNMP MIB module for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM) functionality, managing maintenance entities and monitoring objects for MPLS-based transport paths.

Start monitoring HP Networking (Comware-based) MPLS-capable router/LSR (LSP OAM fault detection) 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 HPN-ICF-MPLSOAM-MIB

What Is HPN-ICF-MPLSOAM-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description