[c-nsp] 6500 redundant supervisors and non-NFS aware RIP

Andrew Miehs andrew at 2sheds.de
Mon Jul 14 17:41:09 EDT 2014


If all your ISPs are connected on the one box, I would recommend buying a second 6500 and splitting the links across both rather than dual sup...

Sent from a mobile device

> On 15 Jul 2014, at 0:38, "Jeffrey G. Fitzwater" <jfitz at Princeton.EDU> wrote:
> 
> We are planning on installing a second supervisor in one of our border 6500Es thats connects to our 3 ISPs.
> 
> 
> The systems runs both BGP for ISP peering and RIP for internal routing to core.
> 
> The sup is a 720-10G with VS-F6K-PFC3CXL running 122-33.SXJ5
> 
> 
> 
> 
> 
> Q1 Since BGP is NFS aware but only after the second SUP is installed, will BGP peering stop and restart?
> 
> We see that two of our ISP are currently sending GRACEFUL RESTART messages but our end is not yet because no secondary sup.
> 
> 
> 
> Q2 What happens with the RIP routes?
> 
> We know we have to move to OSPF, but thats another day;  Soon I hope.
> 
> 
> 
> 
> We are trying to understand how long this system might be down and have testing redundant sups in lab, but thats never really the same.
> 
> 
> 
> 
> Thanks in advance for any help.
> 
> 
> 
> 
> 
> Jeff FItzwater
> OIT Network Systems
> Princeton University
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list