This concept is used by an IPv4 IES interface to affect the operational state of the IP interface monitoring the operational group. Individual SAP and spoke SDPs are supported as monitoring objects.
The following rules apply:
An object can only belong to one group at a time.
An object that is part of a group cannot monitor the status of a group.
An object that monitors the status of a group cannot be part of a group.
An operational group may contain any combination of member types, SAP or Spoke-SDPs.
An operational group may contain members from different VPLS service instances.
Objects from different services may monitor the oper-group.
There are two steps involved in enabling the functionality:
Identify a set of objects whose forwarding state should be considered as a whole group then group them under an operational group using the oper-group command.
Associate the IP interface to the oper-group using the monitor-group command.
The status of the operational group (oper-group) is dictated by the status of one or more members according to the following rules:
The oper-group goes down if all the objects in the oper-group go down. The oper-group comes up if at least one component is up.
An object in the group is considered down if it is not forwarding traffic in at least one direction. That could be because the operational state is down or the direction is blocked through some validation mechanism.
If a group is configured but no members are specified yet, then its status is considered up.
As soon as the first object is configured the status of the operational group is dictated by the status of the provisioned members.
The following configuration shows the oper-group g1, the VPLS SAP that is mapped to it and the IP interfaces in IES service 2001 monitoring the oper-group g1. This example uses an R-VPLS context. The VPLS instance includes the allow-ip-int-bind and the name v1. The IES interface links to the VPLS using the vpls v1 option. All commands are under the configuration service hierarchy.
To further describe the configuration. Oper-group g1 has a single SAP (1/1/1:2001) mapped to it and the IP interfaces in the IES service 2001 derive its state from the state of oper-group g1.
oper-group g1 create
vpls 1 name "v1" customer 1 create
allow-ip-int-bind
stp
shutdown
exit
sap 1/1/1:2001 create
oper-group g1
eth-cfm
mep domain 1 association 1 direction down
ccm-enable
no shutdown
exit
exit
sap 1/1/2:2001 create
exit
sap 1/1/3:2001 create
exit
no shutdown
ies 2001 customer 1 create
interface "i2001" create
address 192.168.1.1/24
monitor-oper-group "g1"
vpls "v1"
exit
no shutdown
exit