9.6.2 Monitoring MPLS-TP OAM Status
MPLS-TP OAM status can be monitored by viewing information about MPLS-TP OAM during
the operation.
Context
The following commands are run in any view during routine maintenance to show MPLS-TP
OAM status.
Procedure
l
Run the
display mpls-tp oam current-alarm
[
meg
meg-name
] command in any view to
check alarms about a MEG.
l
Run the
display mpls-tp oam me
brief
command in any view to check information about
a maintenance entity (ME) in a maintenance entity group (MEG).
l
Run the
display mpls-tp oam meg
meg-name
command in any view to check maintenance
entity group end point (MEP) configurations.
l
Run the
display mpls-tp oam
meg
meg-name
statistic-type
{
lost-measure
{
single-
ended
|
dual-ended
} |
delay-measure
{
one-way
|
two-way
} } command in any view to
check statistics about MPLS-TP OAM performance.
l
Run the
display snmp-agent trap feature-name tpoam all
command in any view to check
all trap information about the TPOAM module.
l
Run the
display mpls-tp oam current-alarm
[
meg
meg-name
] command in any view to
check alarms about a MEG.
l
Run the
ddisplay mpls-tp oam default-parameter
command in any view to check default
MPLS-TP OAM parameters.
----End
9.7 Configuration Examples
This section describes the typical application scenarios of MPLS-TP OAM, networking
requirements, configuration roadmap, and data preparation, and provides related configuration
files.
9.7.1 Example for Configuring CC and CV for an LSP
LSRs are connected using a bidirectional LSP. CC and CV need to be configured to monitor the
continuous connectivity between LSRs and detect faults on the MPLS-TP network.
Networking Requirements
As shown in
, LSRA, LSRB, and LSRC are connected using a bidirectional LSP. The
following deployment is performed to guarantee the connectivity and correct packet forwarding
between LSRA and LSRC:
l
LSRA and LSRC serve as MEPs.
l
LSRB serves as a MIP.
Configure CC and CV on the MEPs.
HUAWEI NetEngine80E/40E Router
Configuration Guide - Reliability
9 MPLS-TP OAM Configuration
Issue 02 (2014-09-30)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
957
