H3C-MPLSOAM-MIB
AI MIB Summary
The H3C-MPLSOAM-MIB module enables the configuration and monitoring of MPLS Operation, Administration, and Maintenance (OAM) functions on H3C network devices, specifically managing fault detection, continuity checks, and performance metrics for MPLS Label Switched Paths (LSPs).
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.
Main OID:
h3cMplsOam.1.3.6.1.4.1.2011.10.2.79
35
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
35 total| Object Name |
|---|
h3cMplsOamThis 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. MODULE-IDENTITY .1.3.6.1.4.1.2011.10.2.79 |
h3cMplsOamScalarGroup OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.79.1 |
h3cMplsOamCapabilityWhether OAM is globally capable. false: incapable; true: capable; The default value is incapable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.79.1.1 |
h3cMplsOamTrapOpenWhether OAM trap is globally enabled. false: disable; true: enable; The default value is disable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.79.1.2 |
h3cMplsOamTable OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.79.2 |
h3cMplsOamIgrTableThis table specifies per-LSP MPLS OAM ingress capability and associated information, such as IgrLspName and IgrDetType. SEQUENCE OF H3cMplsOamIgrEntry .1.3.6.1.4.1.2011.10.2.79.2.1 |
h3cMplsOamIgrEntryAn entry in this table is created by an LSR for every LSP capable of supporting MPLS OAM at ingress. H3cMplsOamIgrEntry .1.3.6.1.4.1.2011.10.2.79.2.1.1 |
h3cMplsOamIgrIndexThis is an unique index for an OAM ingress entry in the OAM table. Unsigned32 .1.3.6.1.4.1.2011.10.2.79.2.1.1.1 |
h3cMplsOamIgrLspNameThe name of an LSP. It means the LSP name of the detected LSP.rw OCTET STRING .1.3.6.1.4.1.2011.10.2.79.2.1.1.2 |
h3cMplsOamIgrDetectTypeThere 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.rw Enumeration .1.3.6.1.4.1.2011.10.2.79.2.1.1.3 |
h3cMplsOamIgrDetectFreqIndication of the OAM's frequent type.rw H3cMplsOAMDetectFreq .1.3.6.1.4.1.2011.10.2.79.2.1.1.4 |
h3cMplsOamIgrRevTypeWhen 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.rw Enumeration .1.3.6.1.4.1.2011.10.2.79.2.1.1.5 |
h3cMplsOamIgrRevLspNameThe object indicates the name of the reverse LSP.rw OCTET STRING .1.3.6.1.4.1.2011.10.2.79.2.1.1.6 |
h3cMplsOamIgrLspIdFor ingress, the object indicates the lsp ID of the detected LSP.rw Integer32 .1.3.6.1.4.1.2011.10.2.79.2.1.1.7 |
h3cMplsOamIgrEnableWhether 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.79.2.1.1.8 |
h3cMplsOamIgrDefectTypeIndication of the OAM's defect type.ro H3cMplsOAMDefectType .1.3.6.1.4.1.2011.10.2.79.2.1.1.9 |
h3cMplsOamIgrRowStatusThis 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, h3cMplsOamIgrLspName, h3cMplsOamIgrDetectType, h3cMplsOamIgrDetectFreq, h3cMplsOamIgrRevType, h3cMplsOamIgrRevLspName, and h3cMplsOamIgrLspId must be specified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.79.2.1.1.10 |
h3cMplsOamEgrTableThis table specifies per-LSP MPLS OAM capability and associated information, such as DetectType, DetectFrequency. SEQUENCE OF H3cMplsOamEgrEntry .1.3.6.1.4.1.2011.10.2.79.2.2 |
h3cMplsOamEgrEntryAn entry in this table is created by an LSR for every LSP capable of supporting MPLS OAM at egress. H3cMplsOamEgrEntry .1.3.6.1.4.1.2011.10.2.79.2.2.1 |
h3cMplsOamEgrIndexThis is a unique index for an OAM egress entry in the OAM table. Unsigned32 .1.3.6.1.4.1.2011.10.2.79.2.2.1.1 |
h3cMplsOamEgrLspNameThe object indicates the name of static LSP at egress.rw OCTET STRING .1.3.6.1.4.1.2011.10.2.79.2.2.1.2 |
h3cMplsOamEgrDetectTypeThere 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.rw Enumeration .1.3.6.1.4.1.2011.10.2.79.2.2.1.3 |
h3cMplsOamEgrDetectFreqIndication of the OAM's frequent type.rw H3cMplsOAMDetectFreq .1.3.6.1.4.1.2011.10.2.79.2.2.1.4 |
h3cMplsOamEgrRevTypeWhen 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.rw Enumeration .1.3.6.1.4.1.2011.10.2.79.2.2.1.5 |
h3cMplsOamEgrRevLspNameThe object indicates the name of a reverse static-lsp.rw OCTET STRING .1.3.6.1.4.1.2011.10.2.79.2.2.1.6 |
h3cMplsOamEgrLsrIdThe object indicates the Ingress LSR ID of the LSP.rw IpAddress .1.3.6.1.4.1.2011.10.2.79.2.2.1.7 |
h3cMplsOamEgrLspIdThe object indicates the the Ingress session lsp ID of the detected static-LSP.rw Integer32 .1.3.6.1.4.1.2011.10.2.79.2.2.1.8 |
h3cMplsOamEgrEnableWhether 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.79.2.2.1.9 |
h3cMplsOamEgrDefectTypeIndication of the OAM's defect type.ro H3cMplsOAMDefectType .1.3.6.1.4.1.2011.10.2.79.2.2.1.10 |
h3cMplsOamEgrRowStatusThis 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, h3cMplsOamEgrLspName, h3cMplsOamEgrDetectType, h3cMplsOamEgrDetectFreq, h3cMplsOamEgrRevType, h3cMplsOamEgrRevLspName, h3cMplsOamEgrLsrId and h3cMplsOamEgrLspId must be specified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.79.2.2.1.11 |
h3cMplsOamNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.79.3 |
h3cMplsOamIgrLSPOutDefectThis notification is generated when the LSP is found out of the defect state at the LSP ingress. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.79.3.1 |
h3cMplsOamIgrLSPInDefectThis notification is generated when the LSP is found in the defect state at the LSP ingress. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.79.3.2 |
h3cMplsOamEgrLSPOutDefectThis notification is generated when the LSP is found out of the defect state at the LSP egress. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.79.3.3 |
h3cMplsOamEgrLSPInDefectThis notification is generated when the LSP is found in the defect state at the LSP egress. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.79.3.4 |
More MIBs from Huawei
Browse all HuaweiMIBs →HUAWEI-MIB
The HUAWEI-MIB module provides a unified namespace for monitoring and managing generic system resources, interface statistics, and hardware telemetry across Huawei network devices. It serves as the foundational OID repository for retrieving standard operational data, including CPU utilization, memory usage, interface counters, and device status, required for comprehensive network management via SNMP.
3074 objects→
HUAWEI-SERVER-IBMC-MIB
Standard SNMP MIB module defining data structures for HUAWEI-SERVER-IBMC-MIB.
2171 objects→
HUAWEI-XPON-MIB
The HUAWEI-XPON-MIB module enables Network Management Systems to monitor and configure GPON and EPON optical line terminals and optical network units, specifically tracking PON port status, optical power levels, bandwidth allocation, and subscriber session states.
1553 objects→
H3C-ENTITY-VENDORTYPE-OID-MIB
SNMP MIB module
1462 objects→
HUAWEI-WLAN-CONFIGURATION-MIB
The HUAWEI-WLAN-CONFIGURATION-MIB facilitates the configuration and monitoring of Huawei Wireless LAN access point parameters, specifically managing AP port link profiles and broadcast suppression settings. This module enables administrators to enforce traffic control policies and optimize wireless network performance by adjusting switch profile associations and limiting broadcast traffic on specific ports.
1280 objects→
HUAWEI-XQoS-MIB
The HUAWEI-XQoS-MIB enables configuration and real-time monitoring of Class Based QoS parameters on Huawei network devices, specifically tracking traffic classification rules, queue states, and policy enforcement metrics. This module facilitates granular control over bandwidth allocation and packet prioritization by exposing objects for policy definitions, interface queue depths, and dropped packet counters associated with QoS classes.
1134 objects→