HH3C-MPLSOAM-MIB
AI MIB Summary
The HH3C-MPLSOAM-MIB module configures and monitors MPLS Operation, Administration, and Maintenance (OAM) parameters on H3C network devices, specifically managing OAM session states, fault detection mechanisms, and continuity check metrics to ensure MPLS label-switched path integrity.
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:
hh3cMplsOam.1.3.6.1.4.1.25506.2.79
35
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
35 total| Object Name |
|---|
hh3cMplsOamThis 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.25506.2.79 |
hh3cMplsOamScalarGroup OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.79.1 |
hh3cMplsOamCapabilityWhether OAM is globally capable. false: incapable; true: capable; The default value is incapable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.25506.2.79.1.1 |
hh3cMplsOamTrapOpenWhether OAM trap is globally enabled. false: disable; true: enable; The default value is disable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.25506.2.79.1.2 |
hh3cMplsOamTable OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.79.2 |
hh3cMplsOamIgrTableThis table specifies per-LSP MPLS OAM ingress capability and associated information, such as IgrLspName and IgrDetType. SEQUENCE OF Hh3cMplsOamIgrEntry .1.3.6.1.4.1.25506.2.79.2.1 |
hh3cMplsOamIgrEntryAn entry in this table is created by an LSR for every LSP capable of supporting MPLS OAM at ingress. Hh3cMplsOamIgrEntry .1.3.6.1.4.1.25506.2.79.2.1.1 |
hh3cMplsOamIgrIndexThis is an unique index for an OAM ingress entry in the OAM table. Unsigned32 .1.3.6.1.4.1.25506.2.79.2.1.1.1 |
hh3cMplsOamIgrLspNameThe name of an LSP. It means the LSP name of the detected LSP.rw OCTET STRING .1.3.6.1.4.1.25506.2.79.2.1.1.2 |
hh3cMplsOamIgrDetectTypeThere 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.25506.2.79.2.1.1.3 |
hh3cMplsOamIgrDetectFreqIndication of the OAM's frequent type.rw Hh3cMplsOAMDetectFreq .1.3.6.1.4.1.25506.2.79.2.1.1.4 |
hh3cMplsOamIgrRevTypeWhen 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.25506.2.79.2.1.1.5 |
hh3cMplsOamIgrRevLspNameThe object indicates the name of the reverse LSP.rw OCTET STRING .1.3.6.1.4.1.25506.2.79.2.1.1.6 |
hh3cMplsOamIgrLspIdFor ingress, the object indicates the lsp ID of the detected LSP.rw Integer32 .1.3.6.1.4.1.25506.2.79.2.1.1.7 |
hh3cMplsOamIgrEnableWhether 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.25506.2.79.2.1.1.8 |
hh3cMplsOamIgrDefectTypeIndication of the OAM's defect type.ro Hh3cMplsOAMDefectType .1.3.6.1.4.1.25506.2.79.2.1.1.9 |
hh3cMplsOamIgrRowStatusThis 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, hh3cMplsOamIgrLspName, hh3cMplsOamIgrDetectType, hh3cMplsOamIgrDetectFreq, hh3cMplsOamIgrRevType, hh3cMplsOamIgrRevLspName, and hh3cMplsOamIgrLspId must be specified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.79.2.1.1.10 |
hh3cMplsOamEgrTableThis table specifies per-LSP MPLS OAM capability and associated information, such as DetectType, DetectFrequency. SEQUENCE OF Hh3cMplsOamEgrEntry .1.3.6.1.4.1.25506.2.79.2.2 |
hh3cMplsOamEgrEntryAn entry in this table is created by an LSR for every LSP capable of supporting MPLS OAM at egress. Hh3cMplsOamEgrEntry .1.3.6.1.4.1.25506.2.79.2.2.1 |
hh3cMplsOamEgrIndexThis is a unique index for an OAM egress entry in the OAM table. Unsigned32 .1.3.6.1.4.1.25506.2.79.2.2.1.1 |
hh3cMplsOamEgrLspNameThe object indicates the name of static LSP at egress.rw OCTET STRING .1.3.6.1.4.1.25506.2.79.2.2.1.2 |
hh3cMplsOamEgrDetectTypeThere 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.25506.2.79.2.2.1.3 |
hh3cMplsOamEgrDetectFreqIndication of the OAM's frequent type.rw Hh3cMplsOAMDetectFreq .1.3.6.1.4.1.25506.2.79.2.2.1.4 |
hh3cMplsOamEgrRevTypeWhen 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.25506.2.79.2.2.1.5 |
hh3cMplsOamEgrRevLspNameThe object indicates the name of a reverse static-lsp.rw OCTET STRING .1.3.6.1.4.1.25506.2.79.2.2.1.6 |
hh3cMplsOamEgrLsrIdThe object indicates the Ingress LSR ID of the LSP.rw IpAddress .1.3.6.1.4.1.25506.2.79.2.2.1.7 |
hh3cMplsOamEgrLspIdThe object indicates the the Ingress session lsp ID of the detected static-LSP.rw Integer32 .1.3.6.1.4.1.25506.2.79.2.2.1.8 |
hh3cMplsOamEgrEnableWhether 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.25506.2.79.2.2.1.9 |
hh3cMplsOamEgrDefectTypeIndication of the OAM's defect type.ro Hh3cMplsOAMDefectType .1.3.6.1.4.1.25506.2.79.2.2.1.10 |
hh3cMplsOamEgrRowStatusThis 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, hh3cMplsOamEgrLspName, hh3cMplsOamEgrDetectType, hh3cMplsOamEgrDetectFreq, hh3cMplsOamEgrRevType, hh3cMplsOamEgrRevLspName, hh3cMplsOamEgrLsrId and hh3cMplsOamEgrLspId must be specified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.79.2.2.1.11 |
hh3cMplsOamNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.79.3 |
hh3cMplsOamIgrLSPOutDefectThis 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.25506.2.79.3.1 |
hh3cMplsOamIgrLSPInDefectThis notification is generated when the LSP is found in the defect state at the LSP ingress. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.79.3.2 |
hh3cMplsOamEgrLSPOutDefectThis 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.25506.2.79.3.3 |
hh3cMplsOamEgrLSPInDefectThis notification is generated when the LSP is found in the defect state at the LSP egress. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.79.3.4 |