Netvanta 800/8000 Series Ncte Configuration Procedure - ADTRAN Total Access 5000 Deployment Manual

NetVanta 800/8000 Series NCTE Configuration Procedure

Create the MD, MA, and a MEP on the Netvanta 800/8000 Series NCTE #1 (example at the
end):
1. From the Enable prompt, type configure terminal , and press E
2. From the Global Configuration prompt, enable the Ethernet OAM subsystem by typing
3. From the Global Configuration prompt, create the Ethernet OAM MD by typing
4. From the MD Configuration, type association char-string WORD to create the MA
5. From the MA Configuration prompt, type ccm interval [1-minute|1-second|10-
6. The NetVanta supports remote MEP auto‐discovery and auto‐learning within a MA.
65K510DEP08-1A
Appendix C, Ethernet OAM Provisioning - Ethernet OAM on the NetVanta 800/8000 Series NCTE
bal Configuration prompt.
, and press E
ethernet cfm
ethernet cfm domain char-string WORD level <0-7>
Use the name of the MD in place of the WORD field and specify the level of MD after the
level argument.
(or edit an existing MA).
minutes|10-seconds|100-milliseconds]
second):
Use 100‐milliseconds, 1‐second, 10‐seconds, 1‐minute, or 10‐minutes for the CCM
interval.
Auto‐discovery lets a local MEP discover its peers without committing them to a state
where they can cause RemoteCCM defects/alarms. Other alarms for invalid CCI,
MACstatus, or Xconnect will still be raised. Discovery does not commit any of the
discovered RMEPs to provisioning and if a Discovered entry fails, it will be removed
from the system after aging out. Learning allows the user to immediately learn all peers,
transition them to Static entries, and place their values in provisioning so they will be
persisten upon a restore.
There are seveal items that compose the MEP database and control how it operates.
• MEP Database ‐ Each MA manages its own MEP database. The MEP database
contains all Remote MEPs and also configures how Remote MEPs can be added.
• Connectivity Failure Interval ‐ This value cannot be directly configured by a user but
is based off of the user‐configurable CCM interval. The Connectivity Failure Interval
is 3.5 times the CCM Interval. It is often used as the timeframe during which certain
events are expected to occur within. One example is if a local MEP receives a CCM
from a RMEP and doesn't receive subsequent CCM from it within this time frame,
then the RMEP's state is set to 'Fail'. For a Maintenance Association using a 1‐second
CCM Interval, if a local MEP receives a CCM from a RMEP and does not receive
another within 3.5‐seconds, the RMEP has failed.
• Remote‐MEP ‐ Remote MEPs (RMEP) are defined by their MEPID which must be
unique across the MA. The valid range for a MEPID is 1‐8191. A RMEP can operate
in one of two modes. It can be a 'Static' RMEP or a 'Discovered' RMEP. The
operation mode of a RMEP is dictated by the MEP database rule of the Maintenance
Association.
–Static ‐ A Static RMEP raises the Remote CCM defect condition if it transitions from
the Ok state to the Fail state. A Static RMEP will also be stored in provisioning after
a write and will be restored following a subsequent reload.
–Discovered ‐ A Discovered RMEP does not raise the Remote CCM defect condition
if it transitions from the Ok state to the Fail state. After Discovered RMEP remains
NTER .
to set the CCM interval (default is 1
NTER to access the Glo‐
, and press E
NTER
C-5