The multi-homed diverted AA subscriber in each peer node must be configured with the following parameters set in each node of the peer pair as displayed in Table: Parameter values for peer nodes
| Parameter | Value |
|---|---|
|
Service ID |
Node specific |
|
Interface |
Node specific |
|
SAP or spoke/SDP ID |
Node specific |
|
AA-group ID |
Node specific |
|
App-profile name |
Content must be the same in both peers as to not affect behavior. Nokia recommends using same name and content. |
|
Transit policy ID |
Same in both (only applies if transits are used) |
|
AARP ID |
Same in both |
|
shunt-sdp sdp-id:vc-id |
Node specific but must properly cross-connect the local AA subscriber service with the peer Ipipe/service shunt interface to operate properly for asymmetry removal for remote divert traffic. Peer AARPs stay in standalone mode until cross-connect is configured properly. |
|
Master-selection mode |
Same in both |
|
Other ISA-AA group configuration |
Same in both, including fail-to, divert FC, and so on |
|
IOM traffic classification into a FC |
Same in both (can affect AA divert because this is conditioned by the FC). This includes sub side, network side and shunt IOMs. |
AARP operation has the following required dependencies:
For multi-chassis, shunt links are configured and operationally Up.
For multi-chassis, peer communications established.
Dual-homed SAP or spoke configured.
app-profile configured against SAP or spoke with divert (making the subscriber an AA subscriber). This endpoint is called the primary endpoint if more than one endpoint is configured for an AARP instance.
All endpoints within an AARP instance must be of the same type (SAP or spoke).
All endpoints with an AARP instance must be within the same service.