ETH-CFM (802.1ag and Y.1731)
Page 66 7705 SAR OS Services Guide
CFM Frame Processing
Table 10 shows whether a CFM frame received by various MEP types is processed or not. 
Frames that are processed are extracted from the datapath for CFM processing; unprocessed 
frames are treated as user traffic and follow the user traffic rules. 
Figure 11: ETH-CFM OAMPDU Message
MD level Version
Version
Opcode
CFM TLV #1
CFM TLV #1
Flags
8 bits
3 bits
20847
Table 10:  CFM Frame Processing
MEP Details Received CFM Frame Treatment
MEP Type Direction VC-Type Port Untagged
Tagged 
(1)
Spoke SDP Down Raw Any Processed Not processed
VLAN Any Not processed  Processed
SAP Down Any Dot1q
Not processed
 
(2)
Processed
Any Null Processed Not processed
Up Any Dot1q Not processed  Processed
Any Null Processed Not processed
Notes:
1. Tagged frames are single-tagged frames. 
2. Untagged frames received on a dot1q encapsulated port are processed by the Epipe configured to handle 
untagged frames. The SAP identifier on this Epipe uses VLAN ID 0, also referred to as SAP 0 (for example, 
1/1/2:0).