From: James Ventre (messageboard@ventrefamily.com)
Date: Mon Feb 13 2006 - 13:58:49 GMT-3
>We're not sure why HSRP didn't fail over properly but we suspect the
code may be the culprit.
I'd open a TAC Case. You could have a problem that may also break with
SRM/SSO (hardware??). It's best to find out what went wrong and fix the
problem (if you can) before you work around it.
>We're also looking into upgrading the code to a much more recent
release.
Might want to check the RAM requirements before you do a lot of
upgrading. I know they've risen over the years.
It might be worth it to goto a CatOS release that supports RSTP+. I'm
fond of 8.4 and 8.5 but I've never run them on a Sup1A.
The paticular problems I've had with 12.2(18)SXF is that EIGRP packets
(control packets) are punted to the MSFC without the proper priority
(only with some linecards). So in bouts of heavy EIGRP traffic I lose
neighbors. I'm hoping development has a fix for this soon - we just got
the BugID assigned on Friday.
James
Tim wrote:
Hi James,
Thanks for looking into this and taking the time to share your expertise.
Actually, there are 2 sup1A in the 6500. The overall design is fairly
basic. The closet switches have 2 uplinks to the 6500 with STP putting 1
link in blocking mode. On each MSFC, multiple interface vlan's are
configured and each int vlan is part of an HSRP group.
We did some testing and discovered that connectivity was lost after HSRP
failed over to the standby router. So, we're now considering using SRM
instead. We're not sure why HSRP didn't fail over properly but we suspect
the code may be the culprit.
We're also looking into upgrading the code to a much more recent release.
If you have any suggestions, please feel free to mention them. I'm not
exactly sure how old this equipment and software is but it's probably over 4
years maybe even 6 years or so. And, I doubt it's ever been upgraded.
Below is the output of the show version commands:
routers (MSFC's)
rt02#sh ver
Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8b)E9, EARLY
DEPLOYMENT RELEASE 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 RELEASE SOFTWARE (fc1)
rt02 uptime is 1 day, 1 hour, 12 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
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
9 Virtual Ethernet/IEEE 802.3 interface(s)
509K bytes of non-volatile configuration memory.
16384K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x102
rt01>sh ver
Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8b)E9, EARLY
DEPLOYMENT RELEASE 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(2r)E, RELEASE SOFTWARE (fc1)
BOOTFLASH: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(2)E, EARLY
DEPLOYMENT RELEASE SOFTWARE (fc1)
rt01 uptime is 1 day, 1 hour, 13 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 SAD04350AVM
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache
Last reset from power-on
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
9 Virtual Ethernet/IEEE 802.3 interface(s)
509K bytes of non-volatile configuration memory.
16384K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
switch
sw02a> sh ver
WS-C6509 Software, Version NmpSW: 6.3(5)
Copyright (c) 1995-2002 by Cisco Systems
NMP S/W compiled on Feb 7 2002, 19:52:15
System Bootstrap Version: 5.3(1)
Hardware Version: 2.0 Model: WS-C6509 Serial #: SCA044102SD
PS1 Module: WS-CAC-1300W Serial #: SON04373345
PS2 Module: WS-CAC-1300W Serial #: SON04380445
Mod Port Model Serial # Versions
--- ---- ------------------- -----------
--------------------------------------
1 2 WS-X6K-SUP1A-2GE SAD0434017A Hw : 3.2
Fw : 5.3(1)
Fw1: 5.4(2)
Sw : 6.3(5)
Sw1: 6.3(5)
WS-F6K-PFC SAD04360930 Hw : 1.1
2 2 WS-X6K-SUP1A-2GE SAD043001EW Hw : 3.2
Fw : 5.3(1)
Fw1: 5.4(2)
Sw : 6.3(5)
Sw1: 6.3(5)
WS-F6K-PFC SAD043405EW Hw : 1.1
3 8 WS-X6408A-GBIC SAD043500YR Hw : 1.3
Fw : 5.4(2)
Sw : 6.3(5)
4 8 WS-X6408A-GBIC SAD04270K3Y Hw : 1.3
Fw : 5.4(2)
Sw : 6.3(5)
5 48 WS-X6348-RJ-45 SAD04290WAV Hw : 1.2
Fw : 5.4(2)
Sw : 6.3(5)
WS-F6K-VPWR Hw : 1.0
6 48 WS-X6348-RJ-45 SAD04290TZH Hw : 1.2
Fw : 5.4(2)
Sw : 6.3(5)
WS-F6K-VPWR Hw : 1.0
7 48 WS-X6348-RJ-45 SAD04290WLK Hw : 1.1
Fw : 5.4(2)
Sw : 6.3(5)
WS-F6K-VPWR Hw : 1.0
8 48 WS-X6348-RJ-45 SAD04290P95 Hw : 1.2
Fw : 5.4(2)
Sw : 6.3(5)
WS-F6K-VPWR Hw : 1.0
15 1 WS-F6K-MSFC2 SAD04350AVM Hw : 1.1
Fw : 12.1(8b)E9
Sw : 12.1(8b)E9
16 1 WS-F6K-MSFC2 SAD04360AAJ Hw : 1.1
Fw : 12.1(8b)E9
Sw : 12.1(8b)E9
DRAM FLASH NVRAM
Module Total Used Free Total Used Free Total Used Free
------ ------- ------- ------- ------- ------- ------- ----- ----- -----
1 65408K 48316K 17092K 16384K 15653K 731K 512K 353K 159K
Uptime is 912 days, 3 hours, 58 minutes
-----Original Message-----
From: James Ventre [ mailto:messageboard@ventrefamily.com ]
Sent: Monday, February 13, 2006 10:38 AM
To: Tim
Cc: 'Group Study'
Subject: Re: SRM vs HSRP
I'm going to make a few assumptions:
You're not using a Sup720 becuase DRM isn't an option for that platform.
Since you're not on a Sup720 you're likely in 12.1E and not 12.2
12.2(18)SXF is the first 12.2 code to support the older supervosors
12.2(18)SXF introduces SSO for hybrid but is pretty *new* (ie.
buggy) code.
That being the case SRM is often much easier to configure/maintain since
you're only touching one device when you make edits like adding static
routes and maintaining config templates. But, SRM failover in 12.1E
compared to 12.2 wasn't all that fast (like comparing RPR to RPR+), so
you could see faster failover times with DRM and HSRP). Realistically,
DRM is getting pushed to the curb first (not supported on a Sup720 at
all), SRM is not all that far behind though, because 12.2(18)SXF
supports SSO in hybrid mode (no more SRM).
Realistically, SSO is the future, and you'll be there eventually. I can
see a good argument for going with the config that puts you closer to
that so there are less changes in the future. SRM to SSO is only a
line or two in the config. But I can see the argment for going with
the fastest failover times since it's faster!
I'd need to know more requirements before I picked one over the other.
James
Tim wrote:
Hi Guys,
I just learned about a 6500 feature called Single Router Mode (SRM). With
this feature enabled on a 6500 with dual MSFC's, if one MSFC goes down the
other takes over.
_______________________________________________________________________
Subscription information may be found at: http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:18 GMT-3