Falcon
M-Class
| User Guide
311
4.22.2.3
OAM Messages
Service OAM uses standard Ethernet frames Service OAM frames are distinguishable by Ether Type
and for multicast messages by MAC address. Service OAM frames are sourced, terminated,
processed, and relayed by bridges. Routers can support only limited Service OAM functions. Bridges
that cannot interpret Service OAM messages forward them as normal data frames. All Service OAM
messages are confined to a maintenance domain and to an S-VLAN (PE-VLAN or Provider-VLAN)
and support three types of messages:
•
Continuity Check
•
Loopback
•
Link Trace
Continuity Check Messages (CCM)
CFM Continuity Check Messages (CCMs) are multicast heartbeat messages exchanged periodically
among MEPs. They allow MEPs to discover other MEPs within a domain and allow MIPs to discover
MEPs. CCMs are confined to a domain and S-VLAN. Service OAM CCMs have the following
characteristics:
•
Transmitted at a configurable periodic interval by MEPs. The interval is defined in milliseconds
and can be set to values from 10 milliseconds to 10 minutes (600000 mS), the default is 1
second (1000 mS).
•
Contain a configurable hold-time value to indicate to the receiver the validity of the message.
The default is 2.5 times the transmit interval.
•
Catalogued by MIPs at the same maintenance level.
•
Terminated by remote MEPs at the same maintenance level.
•
Unidirectional and do not solicit a response.
•
Carry the status of the port on which the MEP is configured.
Loopback Messages
Service OAM loopback messages are unicast frames that a MEP transmits, at the request of an
administrator, to verify connectivity to a particular maintenance point. A reply to a loopback
message indicates whether a destination is reachable but does not allow hop-by-hop discovery of
the path. A loopback message is similar in concept to an Internet Control Message Protocol (ICMP)
Echo (ping) message.
A Service OAM loopback message can be generated on demand using the CLI. The source of a
loopback message must be a MEP; the destination may be a MEP or a MIP. Service OAM loopback
messages are unicast; replies to loopback messages also are unicast. Service OAM loopback
messages specify the destination MAC address, VLAN, and maintenance domain.
Link Trace Messages
Содержание Falcon Gen-3 M-Class
Страница 1: ...Falcon Gen 3 M Class User Guide nFalcon M Falcon MX Falcon MX Software version 7 4 0 www fibrolan com...
Страница 16: ...Falcon M Class User Guide 16 2 System Description 2 1 Block Diagram Figure 1 7 M Class functional block diagram...
Страница 90: ...Falcon M Class User Guide 90...
Страница 107: ...Falcon M Class User Guide 107 Figure 4 57 DSCP Translation...
Страница 139: ...Falcon M Class User Guide 139...
Страница 187: ...Falcon M Class User Guide 187 Figure 4 99 RADIUS Statistics for Server...
Страница 197: ...Falcon M Class User Guide 197 4 11 6 SyncCenter Status Figure 4 104 Sync Center Status...
Страница 214: ...Falcon M Class User Guide 214...
Страница 227: ...Falcon M Class User Guide 227...
Страница 234: ...Falcon M Class User Guide 234...
Страница 328: ...Falcon M Class User Guide 328 Figure 4 189 Connectivity check to a MIP and MEP using Loopback function...
Страница 358: ...Falcon M Class User Guide 358 Figure 4 216 sFlow Configuration displays...
Страница 376: ...Falcon M Class User Guide 376...
Страница 403: ...Falcon M Class User Guide 403...
