ADTRAN Total Access 5000 Deployment Manual page 222

Total Access 5000 Business Services Deployment Guide
7. If needed, from the MA Configuration prompt, type remote-mep <1-8191> , and press
8. From the MA Configuration prompt, type component [1|2] vlan [<1-4094>|none]
C-6
in the Fail state for 100‐minutes it will be removed from the MA's MEP database. A
Discovered RMEP will not be stored in provisioning and will need to be redis‐
covered after a system reload. A Discovered RMEP is detonated by an asterisk
preceding the MEPID.
• MEP Database Rules ‐ The following are the two supported rules for a MA's MEP
database:
–auto‐discovery ‐ If a local MEP receives a CCM from a RMEP that has not been
previously configured, it creates a RMEP whose operation mode will be
Discovered.
–auto‐learning ‐ If a local MEP receives a CCM from a RMEP that has not been previ‐
ously configured, it creates a RMEP whose operation mode will be Static.
• MEP Database Actions ‐ The following are actions that can be performed on RMEPs
in the MEP Database:
–Lock ‐ If in the auto‐discovery state, Discovered RMEPs can transition to operate as
Static by being locked.
–Clear ‐ If a Discovered peer fails, it can be manually removed or cleared. If a
Discovered peer has not failed, it can still be cleared but it will be re‐discovered on
the next received CCM from that RMEP.
• MEP Database Rule Transitions ‐ When changing the MA rule from an auto‐
discovery state to an auto‐learning state, all Discovered entries are made Static.
When transitioning from an auto‐discovery state to configured‐only state, all
Discovered entries are removed.
To configure the remote MEP database learning rule, type one of the following
commands:
• Type mep-database configured-only , and press E
configured‐only learning. This is the default
• Type mep-database auto-discovery , and press E
discovery learning
• Type mep-database auto-discovery auto-learn , and press E
rule to auto‐learning
E
NTER to create a RMEP that operates as a Static entry in the MEP‐database.
This step can be repeated to add more than one remote‐MEP to the association.
to associate a VLAN with the maintenance association:
For Component 1 Down and Up MEPs, use the VLAN ID of the EVC with which the MA
is operating on.
For Component 2 Down and Up MEPs, use a customer VLAN ID that is being mapped to
an EVC by an EVC‐map.
If none is specified, untagged CFM messages will be sent.
A Component needs to be created in the Maintenance Association to define the realm of
the MA and the VLAN of the MA. A MA can operate either on c‐tag or s‐tag.
• A Component ID of 1 indicates the Maintenance Association operates on the s‐tag
• A Component ID of 2 indicates the Maintenance Association operates on the c‐tag
A MD and MA can be terminated on an NCTE in various ways depending on the
architecture of the CFM deployment across the network.
NTER to set the rule to
to set the rule to auto‐
NTER
to set the
NTER
65K510DEP08-1A