RE: HSRP and 2ndary addresses

From: Nisar, Munsar (munsar.nisar@citigroup.com)
Date: Thu Feb 09 2006 - 16:08:47 GMT-3


Why are you using the "secondary" keyword for your HSRP group 11? Why don't you just configure group 11 as a normal HSRP group and have users point to this new address? I don't see a reason for you to use secondary in HSRP config. Just my .002 cents. Thanks.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Alec
Sent: Thursday, February 09, 2006 12:05 PM
To: Group Study
Subject: HSRP and 2ndary addresses

Hi Guys,
   
  Im involved with a small IP re-addressing project.
   
  And, something strange is going on. I thought Id bounce this off the brain trust to see what thought's people have.
   
  In this small switched network, we have a 6509. Within the 6509, there are 2 routers, RT01 and RT02 which are running HSRP for redundancy and doing inter-vlan routing.
   
  In preparation for the new ip addressing, secondary ip addresses were added to each interface and a second HSRP group was also configured for the new address space.
   
  But, its not working.
   
  Pings to the secondary physical addresses work but pings to the Virtual IP for the secondary ip addresses dont work.
   
  Output of some show commands are below.
   
  Have any thoughts on this?
   
  Thanks,
   
  Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8b)E9, EARLY DEPLOYMENT RE
LEASE SOFTWARE (fc3)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sun 17-Feb-02 19:16 by eaarmas
Image text-base: 0x40008980, data-base: 0x418D4000
  ROM: System Bootstrap, Version 12.1(3r)E2, RELEASE SOFTWARE (fc1)
BOOTFLASH: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(2)E, EARLY DEPLOYMENT R
ELEASE SOFTWARE (fc1)
  usnysmsrt02 uptime is 2 years, 25 weeks, 4 days, 5 hours, 6 minutes
System returned to ROM by power-on
Running default software
  cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory.
Processor board ID SAD04360AAJ
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache
Last reset from power-on
   
  ************************
  The new ip address will be 10.12.x.x and the old address space, 162.49.49.x/16, will be going away. So, the 10.12.x.x were added in preparation of the cutover.
   
  ##################
   
  RT01
interface Vlan1
 description Network Management VLAN1
 ip address 10.12.105.193 255.255.255.192 secondary
 ip address 162.49.49.162 255.255.255.224
 no ip redirects
 standby 1 ip 162.49.49.161
 standby 11 ip
 standby 11 ip 10.12.105.195 secondary
  
RT02
sh run int vlan 1
!
interface Vlan1
 description Network Management VLAN1
 ip address 10.12.105.194 255.255.255.192 secondary
 ip address 162.49.49.163 255.255.255.224
 no ip redirects
 standby 1 ip 162.49.49.161
 standby 11 ip
 standby 11 ip 10.12.105.195 secondary
end
  
RT02#show standby vlan 1
Vlan1 - Group 1
  Local state is Standby, priority 100
  Hellotime 3 holdtime 10
  Next hello sent in 00:00:02.512
  Virtual IP address is 162.49.49.161 configured
  Active router is 162.49.49.162 expires in 00:00:07, priority 100
  Standby router is local
  1 state changes, last state change 2y25w
Vlan1 - Group 11
  Local state is Learn, priority 100
  Hellotime 3 holdtime 10
  Virtual IP address is 0.0.0.0
    Secondary virtual IP address 10.12.105.195
  Active router is unknown expires in 00:00:05
  Standby router is unknown expires in 00:00:05
  0 state changes, last state change never

  
RT01#
  sh standby brie
                     P indicates configured to preempt.
                     |
Interface Grp Prio P State Active addr Standby addr Group addr
Vl1 1 100 Active local 162.49.49.163 162.49.49.161
Vl1 11 100 Learn unknown unknown unknown
  
RT02#
  sh standby brief
                     P indicates configured to preempt.
                     |
Interface Grp Prio P State Active addr Standby addr Group addr
Vl1 1 100 Standby 162.49.49.162 local 162.49.49.161
Vl1 11 100 Learn unknown unknown unknown

   
   
   



This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:17 GMT-3