OAM Configuration
Configuring Connectivity Fault Management
To enable the connectivity fault management feature, you need to configure a CFM session.
Creating a CFM Session
Currently, OAM CFM supports only the configuration of point-to-point sessions. It does not support point-to-multipoint sessions. |
Syntax:
set oam cfm session <session-name> <attribute> <value>
Attribute | Description |
---|---|
continuity-check-interval |
Specify continuity check interval time (in seconds). Supported intervals are: 1s, 10s and 100ms. |
interface |
Logical interface name. |
level |
Specify the CFM level. Allowed range: 0 - 7. |
local-mep |
Specify the local end-point identifier. Range: 1-8191. |
maintenance-association |
Maintenance association name. |
maintenance-domain |
Maintenance domain name. |
remote-mep |
Remote end-point identifier. Range: 1-8191. |
Example:
set oam cfm session CFM_DEFAULT_LINK1 set oam cfm session CFM_DEFAULT_LINK1 level 2 set oam cfm session CFM_DEFAULT_LINK1 maintenance-domain MD_BNG set oam cfm session CFM_DEFAULT_LINK1 maintenance-association MA_DEFAULT_100 set oam cfm session CFM_DEFAULT_LINK1 continuity-check-interval 1s set oam cfm session CFM_DEFAULT_LINK1 local-mep 1000 set oam cfm session CFM_DEFAULT_LINK1 remote-mep 2000 set oam cfm session CFM_DEFAULT_LINK1 interface ifl-0/0/0/100 set oam cfm session CFM_DEFAULT_LINK2 set oam cfm session CFM_DEFAULT_LINK2 level 2 set oam cfm session CFM_DEFAULT_LINK2 maintenance-domain MD_BNG set oam cfm session CFM_DEFAULT_LINK2 maintenance-association MA_DEFAULT_200 set oam cfm session CFM_DEFAULT_LINK2 continuity-check-interval 1s set oam cfm session CFM_DEFAULT_LINK2 local-mep 1001 set oam cfm session CFM_DEFAULT_LINK2 remote-mep 2001 set oam cfm session CFM_DEFAULT_LINK2 interface ifl-0/0/1/200
supervisor@rtbrick.net: cfg> show config oam cfm session { "rtbrick-config:session": [ { "name": "CFM_DEFAULT_LINK1", "level": 2, "maintenance-domain": "MD_BNG", "maintenance-association": "MA_DEFAULT_100", "continuity-check-interval": "1s", "local-mep": 1000, "remote-mep": 2000, "interface": "ifl-0/0/0/100" }, { "name": "CFM_DEFAULT_LINK2", "level": 2, "maintenance-domain": "MD_BNG", "maintenance-association": "MA_DEFAULT_200", "continuity-check-interval": "1s", "local-mep": 1001, "remote-mep": 2001, "interface": "ifl-0/0/1/200" } ] }
Enabling Nexthop Tracking
You can enable Nexthop tracking using the following commands and options.
Syntax:
set instance <instance-name> oam cfm track <session-name> [nexthop4 | nexthop6] <ip-address>
Attribute | Description |
---|---|
<instance-name> |
Name of the instance. |
<session> |
Specify the session name. |
[nexthop4 | nexthop6] |
Specify nexthop4 to trace ipv4 nexthop and specify nexthop6 to track ipv6 nexthop. |
Example configuration:
set instance default oam cfm track CFM_DEFAULT_LINK1 set instance default oam cfm track CFM_DEFAULT_LINK1 nexthop4 12.0.1.2 set instance default oam cfm track CFM_DEFAULT_LINK1 nexthop4 182.168.0.20 set instance default oam cfm track CFM_DEFAULT_LINK1 nexthop6 182:168::20 set instance default oam cfm track CFM_DEFAULT_LINK1 nexthop6 fe80::7810:2 set instance default oam cfm track CFM_DEFAULT_LINK2 set instance default oam cfm track CFM_DEFAULT_LINK2 nexthop4 12.1.1.2 set instance default oam cfm track CFM_DEFAULT_LINK2 nexthop4 182.168.0.20 set instance default oam cfm track CFM_DEFAULT_LINK2 nexthop6 182:168::20 set instance default oam cfm track CFM_DEFAULT_LINK2 nexthop6 fe80::7810:2
supervisor@rtbrick.net: cfg> show config instance default oam cfm { "rtbrick-config:cfm": { "track": [ { "session": "CFM_DEFAULT_LINK1", "nexthop4": [ "12.0.1.2", "182.168.0.20" ], "nexthop6": [ "182:168::20", "fe80::7810:2" ] }, { "session": "CFM_DEFAULT_LINK2", "nexthop4": [ "12.1.1.2", "182.168.0.20" ], "nexthop6": [ "182:168::20", "fe80::7810:2" ] } ] } }