A network administrator configures 'ipv6 nd raguard' on a switch port connected to a router. The router is sending Router Advertisements with a non-zero Router Lifetime. The switch logs indicate that RAs are being dropped, and the port goes into err-disable state. The engineer checks the RA Guard policy and sees that the default policy is applied. What is the most likely reason for the drops?
RA Guard expects hop-limit of 255 for locally generated RAs.
Why this answer
The default RA Guard policy on Cisco switches blocks Router Advertisements (RAs) that do not have a hop limit of 255. This is because legitimate routers always send RAs with a hop limit of 255, as specified in RFC 4861. When the router sends an RA with a hop limit less than 255, RA Guard treats it as invalid and drops it, which can also trigger err-disable state on the port.
Exam trap
Cisco often tests the specific hop-limit validation in the default RA Guard policy, where candidates mistakenly think the issue is with port mode or MAC addressing rather than the hop-limit field.
How to eliminate wrong answers
Option B is wrong because the default RA Guard policy does not block all RAs; it uses a device-role-based approach that validates specific fields like hop limit and source address. Option C is wrong because RA Guard does not filter based on multicast MAC addresses; it validates the IPv6 source address and hop limit, not the MAC layer. Option D is wrong because RA Guard works on both access and trunk ports; the port mode does not affect RA Guard functionality.