Vrrp With Higher Priority Running As Backup; Troubleshooting Ipv6 Rsmlt; Configuration Considerations - Avaya 8800 Troubleshooting Manual

Upper layer troubleshooting

VRRP with higher priority running as backup

The VRRP router with the higher priority can display as the backup for the following reasons
• Hold-down timer is running
• The configured Critical IP is not reachable or does not exist
If the critical-IP is configured for VRRP Master, and the critical interface goes down or is
deleted, the Master transitions to the backup state. In this case, the Log shows the transition
cause as 1 like many other cases.
To determine that the issue is with the critical interface, look for the following trace message.
tMainTask RCIP6: rcip6_vrrp.c: 5152: VRF name: GlobalRouter (VRF id
0): ipv6VrrpTic: Becoming backup for Vrid 200 on IfIndex 2052 because
of invalid critical IP
If the holddown Timer is configured for VRRP Master, the holddown timer delays the
preemption, giving the device which is becoming the Master enough time to construct routing
tables.
To determine that the device is in holddown timer processing, look for the following trace
message:
tMainTask RCIP6: rcip6_vrrp.c: Enter in HoldDown processing,Vrid 200
LastRecvd 0 MasterDown 3, Holddown time remaining 970, Holddownstate
2

Troubleshooting IPv6 RSMLT

The following sections provide information for troubleshooting IPv6 RSMLT

Configuration considerations

When troubleshooting IPv6 RSMLT, note the following configuration considerations:
• Running both IPv6 RSMLT and IPv6 VRRP on the same VLAN is not supported
• You must configure IST peers with the same IPv6 subnets on the SMLT VLANs (same
as for IPv4).
• Make sure that IST MLTs on the RSMLT peers contain the same set of links (this is very
difficult to catch through regular troubleshooting)
448 Troubleshooting
Comments? infodev@avaya.com
July 2013