RE: [nsp] Unusual Cat 6509 MSFC Problem

From: Rubens Kuhl Jr. (rkuhljr@uol.com.br)
Date: Fri Jan 19 2001 - 12:14:53 EST


The failover of the supervisor when sup runs CatOS and MSFC runs IOS will
almost always generate a L3 disruption.
Run CatOS on density boxes with 2 supervisors and no MSFC, run 2 boxes with
MSFC/SupIOS and 1 sup on each box.

Rubens Kuhl Jr.

-----Original Message-----
From: Chin Wey Jake [mailto:jakechin@pacific.net.sg]
Sent: quinta-feira, 18 de janeiro de 2001 13:25
To: Rob Tucker; Greene, Patrick; 'Desmarais, Jonathan';
cisco-nsp@puck.nether.net
Subject: RE: [nsp] Unusual Cat 6509 MSFC Problem

Hi,
Just wanted to chip in on this. We had similar problems in our network. We
have pair of 6509s and we had some real problems making sure HSRP was able
to run properly on the both of them. We had static routes to a certain
segment but placed them initially on only 1 of the MSFCs, but when the
active MSFC was failovered on one of them, the whole segment went haywire.
We realised that because the MSFCs do not sync, we had to place the same
static routes on all of them.

And I don't quite understand what Patrick Greene means when he said "Keep in
mind the MSFC's are always active and are not in standby mode even though
the supervisor module it resides on may be in standby" I though in HSRP,
only 1 of the MSFCs are active while the rest is on standby. Correct me if I
am wrong.

Is there a way to make sure the MSFC configs are synced if you are running
12.0(10)S? I am asking besides copying the config from 1 MSFC to the other
of course.

Jake
------------------------------------------------------------------------
Cable and Wireless Network Services (Singapore)
A Pacific Century Cyberworks company.
------------------------------------------------------------------------
-----Original Message-----
From: Rob Tucker [mailto:rob.tucker@usa.net]
Sent: Thursday, January 18, 2001 11:54 AM
To: Greene, Patrick; 'Desmarais, Jonathan'; cisco-nsp@puck.nether.net
Subject: Re: [nsp] Unusual Cat 6509 MSFC Problem

Actually, you do have the ability to sync msfc configs beginning w/
12.1(3a)E4:

http://www.cisco.com/warp/partner/synchronicd/cc/pd/si/casi/ca6000/tech/hafc
6_wp.htm#xtocid48718

-Rob
----- Original Message -----
From: Greene, Patrick
To: 'Desmarais, Jonathan' ; cisco-nsp@puck.nether.net
Sent: Wednesday, January 17, 2001 10:20 PM
Subject: RE: [nsp] Unusual Cat 6509 MSFC Problem

You do realize that the MSFC's do not synchronize configurations like the
superivisor modules. If you want redundancy at the Layer 3 level you must
use HSRP on the MSFC's for your VLANs. Keep in mind the MSFC's are always
active and are not in standby mode even though the supervisor module it
resides on may be in standby.
Patrick Greene
-----Original Message-----
From: Desmarais, Jonathan [mailto:JDesmarais@colt-telecom.com]
Sent: Wednesday, January 17, 2001 3:50 AM
To: cisco-nsp@puck.nether.net
Subject: [nsp] Unusual Cat 6509 MSFC Problem

After failing the Sup modules over to the standby, as a test, the layer 3
connectivity to the Switch seems to be fried. On the Switch console we can
see the cdp entries for all the cisco devices directly connected to it, but
we cannot ping any of these devices from the MSFC card.
Any Idea's?
Jon

**********************************************************************
COLT Telecommunications
Registered in England No. 2452736
Registered Office: Bishopsgate Court, 4 Norton Folgate, London E1 6DQ
Tel. 020 7390 3900
This message is subject to and does not create or vary any contractual
relationship between COLT Telecommunications, its subsidiaries or
affiliates ("COLT") and you. Internet communications are not secure
and therefore COLT does not accept legal responsibility for the
contents of this message. Any view or opinions expressed are those of
the author. The message is intended for the addressee only and its
contents and any attached files are strictly confidential. If you have
received it in error, please telephone the number above. Thank you.

**********************************************************************



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:25 EDT