cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1517
Views
0
Helpful
5
Replies

Subinterfaces configured with HSRP

Hello,

I have two ASR 1001s.  They both run HSRP.  Recently I have had to take one router and configure it as a subinterface and bind another ip address to it.  As a result of testing HSRP fail over I noticed that the secondary did not take over.  Even when I did a show standby brief the primary didnt know who its standby device was.  Is there a problem with placing HSRP on a subinterface?

Below is the config

Primary

interface GigabitEthernet0/0/3.1

encapsulation dot1Q 1400

ip address 192.30.212.2 255.255.252.0

standby 10 ip 192.30.212.1

standby 10 priority 150

standby 10 preempt

end

interface GigabitEthernet0/0/3.2

encapsulation dot1Q 59

ip address 209.31.119.236 255.255.255.224

end

Secondary

interface GigabitEthernet0/0/3

description USFS LAN Network

ip address 192.30.212.3 255.255.252.0

standby 10 ip 192.30.212.1

standby 10 priority 140

standby 10 preempt

negotiation auto

end

One big question is if I need to make the interface match?  Do I need to place a matching subinterface on the secondary router as well.  At this point in time the primary cant ping the physical ip address on the secondary and vise versa.

5 Replies 5

Rolf Fischer
Level 9
Level 9

Hi,

HSPR uses link-local Multicast IP-Addresses, so you need to have layer-2 connectivity between the active and standby interfaces.

As far as I can see, the primary side tags frames (1400) whereas the secondary is a main-interface, which doesn't tag. Is there a switch in between with corresponding switchport configurations (trunk / access vlan 1400)?

Regards

Rolf

Jon Marshall
Hall of Fame
Hall of Fame

Is gii0/0/3 on the secondary router in vlan 1400 ?

What does "sh standby brief" show ?

Jon

The original poster asks " Is there a problem with placing HSRP on a subinterface?" . The answer is that no there is not a problem with placing HSRP on a subinterface - as long as both ends of the connection treat it the same way. As Rolf and Jon have pointed out it appears that one end of this connection now is doing trunking with tagged frames while the other end of the connection is treating it as a physical interface with no tagging. It is the mismatch that is causing the problem and not any restriction on HSRP.

HTH

Rick

HTH

Rick

Thanks you all for your assistance.

I am in good shape now.

I am glad that you are in good shape now and hope that our answers were helpful.

HTH

Rick

Sent from Cisco Technical Support iPhone App

HTH

Rick
Review Cisco Networking for a $25 gift card