Chapter 19: Alarm Management and Troubleshooting (CLI)
Performing Diagnostics (CLI)
phn-3963_008v000
Page 19-15
•
•
•
Displaying MEP and Remote MEP Attributes (CLI)
•
Displaying Detailed MEP Error Information (CLI)
•
SOAM Overview (CLI)
The Y.1731 standard and the MEF-30 specifications define Service OAM (SOAM). SOAM is concerned with
detecting, isolating, and reporting connectivity faults spanning networks comprising multiple LANs, including LANs
other than IEEE 802.3 media.
Y.1731 Ethernet FM (Fault Management) consists of three protocols that operate together to aid in fault
management:
•
Continuity check
•
Link trace
•
Loopback
Note
Link trace is planned for future release.
PTP 850 utilizes these protocols to maintain smooth system operation and non-stop data flow.
The following are the basic building blocks of FM:
•
MD (Maintenance Domain)
– An MD defines the management space on a network, typically owned and
operated by a single entity, for which connectivity faults are managed via SOAM.
•
MA/MEG (Maintenance Association/Maintenance Entity Group)
– An MA/MEG contains a set of MEPs or
MIPs.
•
MEP (MEG End Points) – Each MEP is located on a service point of an Ethernet service at the boundary of the
MEG. By exchanging CCMs (Continuity Check Messages), local and remote MEPs have the ability to detect the
network status, discover the MAC address of the remote unit/port where the peer MEP is defined, and
identify network failures.
•
MIP –(MEG Intermediate Points) – Similar to MEPs, but located inside the MEG and can only respond to, not
initiate, CCM messages.
•
CCM (Continuity Check Message) – MEPs in the network exchange CCMs with their peers at defined intervals.
This enables each MEP to detect loss of connectivity or failure in the remote MEP.
Configuring MDs (CLI)
In the current release, you can define one MD, with an
MD Format
of
None
.
To add an MD, enter the following command in root view:
