Configuring HSRP Aware Pim
Configuring HSRP Aware Pim
status messages and one device can assume the routing responsibility of another, should it go out of commission
for either planned or unplanned reasons. Hosts continue to forward IP packets to a consistent IP and MAC
addres,s and the changeover of devices doing the routing is transparent.
HSRP is useful for hosts that do not support a router discovery protocol and cannot switch to a new device
when their selected device reloads or loses power. Because existing TCP sessions can survive the failover,
this protocol also provides a more transparent recovery for hosts that dynamically choose a next hop for
routing IP traffic.
When HSRP is configured on a network segment, it provides a virtual MAC address and an IP address that
is shared among a group of devices running HSRP. The address of this HSRP group is referred to as the virtual
IP address. One of these devices is selected by the protocol to be the active router (AR). The AR receives and
routes packets destined for the MAC address of the group.
HSRP uses a priority mechanism to determine which HSRP configured device is to be the default AR. To
configure a device as the AR, you assign it a priority that is higher than the priority of all the other
HSRP-configured devices. The default priority is 100, so if you configure just one device to have a higher
priority, that device will be the default AR.
Devices that are running HSRP send and receive multicast User Datagram Protocol (UDP)-based hello
messages to detect device failure and to designate active and standby devices. When the AR fails to send a
hello message within a configurable period of time, the standby device with the highest priority becomes the
AR. The transition of packet forwarding functions between devices is completely transparent to all hosts on
the network.
You can configure multiple Hot Standby groups on an interface, thereby making fuller use of redundant
devices and load sharing.
HSRP is not a routing protocol as it does not advertise IP routes or affect the routing table in any way.
HSRP has the ability to trigger a failover if one or more interfaces on the device fail. This can be useful for
dual branch devices each with a single serial link back to the head end. If the serial link of the primary device
goes down, the backup device takes over the primary functionality and thus retains connectivity to the head
end.
Hello will carry a new GenID in order to trigger other routers to respond to the failover. When a downstream
device receives this PIM Hello, it will add the virtual address to its PIM neighbor list. The new GenID carried
in the PIM Hello will trigger downstream routers to resend PIM Join messages towards the virtual address.
Upstream routers will process PIM Join/Prunes (J/P) based on HSRP group state.
If the J/P destination matches the HSRP group virtual address and if the destination device is in HSRP active
state, the new AR processes the PIM Join because it is now the acting PIM DR. This allows all PIM Join/Prunes
to reach the HSRP group virtual address and minimizes changes and configurations at the downstream routers
side.
The IP routing service utilizes the existing virtual routing protocol to provide basic stateless failover services
to client applications, such as PIM. Changes in the local HSRP group state and standby router responsibility
are communicated to interested client applications. Client applications may build on top of IRS to provide
stateful or stateless failover. PIM, as an HSRP client, listens to the state change notifications from HSRP and
automatically adjusts the priority of the PIM DR based on the HSRP state. The PIM client also triggers
communication between upstream and downstream devices upon failover in order to create an mroute state
on the new AR.
Procedure
Step 6 standby [group-number] timers [msec] (Optional) Configures the time between hello
hellotime [msec] holdtime packets and the time before other devices
declare an HSRP active or standby router to
Example:
be down.
Device(config-if)# standby 1 timers 5
15
Step 7 standby [group-number] priority priority (Optional) Assigns the HSRP priority to be
used to help select the HSRP active and
Example:
standby routers.
Device(config-if)# standby 1 priority
120
Step 8 standby [group-number] name group-name (Optional) Defines a name for the HSRP
group.
Example:
Device(config-if)# standby 1 name HSRP1 Note We recommend that you always
configure the standby ip name
command when configuring an
HSRP group to be used for HSRP
Aware PIM.
Step 10 show standby [type number [group]] [all | Displays HSRP group information for
brief] verifying the configuration.
Example:
Device# show standby
Procedure
Step 5 ip pim redundancy group dr-priority priority Enables PIM redundancy and assigns a
redundancy priority value to the active PIM
Example:
designated router (DR).
Device(config-if)# ip pim redundancy
HSRP1 dr-priority 60 • Because HSRP group names are case
sensitive, the value of the group argument
must match the group name configured by
using the standby ip name command.
• The redundancy priority for a PIM DR
must be greater than the configured or
default value (1) of the PIM DR priority
on any device for which the same HSRP
group is enabled.
Standard/RFC Title
MIBs
No new or modified MIBs are supported by this To locate and download MIBs for selected platforms, Cisco
feature, and support for existing MIBs has not software releases, and feature sets, use Cisco MIB Locator
been modified by this feature. found at the following URL:
http://www.cisco.com/go/mibs
Technical Assistance
Description Link