For many years I have configured HSRP on my IOS based devices with tracking configured for a Loopback without an IP so that during maintenance windows one simply needs to down the loopback to fail HSRP to the peer. However, recently when configuring the same setup on an ASR9K, I noticed that while the loopback shows up/up, HSRP sees it as down (config/output below). The only way to get HSRP to see the loopback as up is by configuring an IP on the loopback.
Does anyone know if this is intentional/expected behavior? Again, in IOS and NX-OS you do not need an IP on the loopback for HSRP to see it as up and track accordingly.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...