A PW port state may be linked to the state of an oper-group, such that if the oper-group goes down, the SDP binding for the PW port also goes operationally down, and therefore the corresponding PW status bit signaled (0x00000001 - Pseudowire Not Forwarding). If a status of 0x00000001 is signaled for a currently active PW, and active/standby dual homing is in use then the access PE fails over to the standby PW to the standby converged PE.
This is achieved by linking an SDP binding to an operational group for PW SAPs belonging to any supported service types (including those with group interfaces) bound to that PW port, such as IES, VPRN, or Epipe VLL. The association to an operational group is configured under the PW port config at the SDP binding level, as follows:
config
service
sdp
binding
[no] pw-port <pw-port-id> [vc-id <vc-id>] [create]
monitor-oper-group <group-name>
The monitor-oper-group command specifies the operational group to be monitored by the PW-Port under which it is configured. The oper-group name must be already configured under the config>service context before its name is referenced in this command.
The following illustrates how a PW port can track the status of VPRN uplinks using monitor-oper-group.
Uplinks in a VPRN may be monitored using a BFD session on the network facing IP interfaces in a VPRN or on the network IP interfaces supporting the uplinks.
Oper-groups monitor the state of these BFD sessions inside the VPRN as follows:
config>service>
oper-group "test-oper-grp" create
bfd-enable interface "vprn-if" dest-ip 10.0.0.20 service 105
Alternatively, the state of network interfaces can be monitored as follows:
config>service>
oper-group "test-oper-grp" create
bfd-enable interface "network-if" dest-ip 10.0.1.20
The PW port is then configured with monitor-oper-group as follows:
config>service>sdp>binding
pw-port 100 vc-id 25
monitor-oper-group "test-oper-group"