Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
For those interested I put the SFM's in last night without a hitch, in fact it didn't even drop a packet(1s ping intervals) it just did the usual OIR Bus pause and one packet went up to 1600ms then everything went back to normal except packets were now using the new crossbar fabric(no reboot required), very smooth. Running 12.2(18)SXF4 Before: router#sh fab swi Global switching mode is Flow through dCEF mode is not enforced for system to operate Fabric module is not required for system to operate Modules are allowed to operate in bus mode Truncated mode is not allowed unless threshold is met Threshold for truncated mode operation is 2 SFM-capable cards Module Slot Switching Mode 1 Bus 3 Bus 5 Bus After: router#sh fab swi Global switching mode is Compact dCEF mode is not enforced for system to operate Fabric module is not required for system to operate Modules are allowed to operate in bus mode Truncated mode is not allowed unless threshold is met Threshold for truncated mode operation is 2 SFM-capable cards Module Slot Switching Mode 1 dCEF 3 Crossbar 5 Crossbar 6No Interfaces router#sh fab util slotchannel Ingress % Egress % 1 0 0 0 3 0 5 1 5 0 1 5 Ben On Mon, Feb 9, 2009 at 8:02 PM, Ben Steele illcrit...@gmail.com wrote: Thanks for all the replies, personally i'm thinking it will be a few second hiccup like you often get with OIR then on its way again but the fact i'm changing how the underlying switch fabric works with this makes it more interesting... i've scheduled an outage for this Sunday evening so I will let you all know how it goes. Cheers Ben On Mon, Feb 9, 2009 at 7:37 PM, Peter Rathlev pe...@rathlev.dk wrote: On Mon, 2009-02-09 at 10:26 +1030, Ben Steele wrote: I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), Just to chime in with more non-certain knowlegde: When doing OIR the box does a bus stall AFAIK. This happens between when the pins start connecting and when all pins are connected. If this were to not cause any lost packets, the modules would have to buffer while the bus stall is in effect and retransmit whatever was on the wire when it happened. I don't think they do. Regards, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
On Mon, 2009-02-09 at 10:26 +1030, Ben Steele wrote: I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), Just to chime in with more non-certain knowlegde: When doing OIR the box does a bus stall AFAIK. This happens between when the pins start connecting and when all pins are connected. If this were to not cause any lost packets, the modules would have to buffer while the bus stall is in effect and retransmit whatever was on the wire when it happened. I don't think they do. Regards, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Thanks for all the replies, personally i'm thinking it will be a few second hiccup like you often get with OIR then on its way again but the fact i'm changing how the underlying switch fabric works with this makes it more interesting... i've scheduled an outage for this Sunday evening so I will let you all know how it goes. Cheers Ben On Mon, Feb 9, 2009 at 7:37 PM, Peter Rathlev pe...@rathlev.dk wrote: On Mon, 2009-02-09 at 10:26 +1030, Ben Steele wrote: I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), Just to chime in with more non-certain knowlegde: When doing OIR the box does a bus stall AFAIK. This happens between when the pins start connecting and when all pins are connected. If this were to not cause any lost packets, the modules would have to buffer while the bus stall is in effect and retransmit whatever was on the wire when it happened. I don't think they do. Regards, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Howdy, I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), and I want to know if the modules go from using Bus only backplane to crossbar as soon as the module initiates or whether a reload would actually be required for this. Cheers Ben ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Yea it is hot-swappable. You must install the Switch Fabric Module in either slot 5 or slot 6 of the Catalyst 6506 switch. For redundancy, you can install a standby Switch Fabric Module. The module first installed functions as the primary module. When you install two Switch Fabric Modules at the same time, the module in slot 5 acts as the primary module, and the module in slot 6 acts as the backup. If you reset the module in slot 5, the module in slot 6 becomes the primary module. Regards, Masood Blog: http://weblogs.com.pk/jahil/ -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Ben Steele Sent: Monday, February 09, 2009 4:57 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] WS-6500-SFM insertion into production box, much of an impact? Howdy, I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), and I want to know if the modules go from using Bus only backplane to crossbar as soon as the module initiates or whether a reload would actually be required for this. Cheers Ben ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Thank you for cut and pasting the information from Cisco that i've already read :) Seriously though, that doesn't answer my question. On Mon, Feb 9, 2009 at 10:49 AM, Masood Ahmad Shah mas...@nexlinx.net.pkwrote: Yea it is hot-swappable. You must install the Switch Fabric Module in either slot 5 or slot 6 of the Catalyst 6506 switch. For redundancy, you can install a standby Switch Fabric Module. The module first installed functions as the primary module. When you install two Switch Fabric Modules at the same time, the module in slot 5 acts as the primary module, and the module in slot 6 acts as the backup. If you reset the module in slot 5, the module in slot 6 becomes the primary module. Regards, Masood Blog: http://weblogs.com.pk/jahil/ -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Ben Steele Sent: Monday, February 09, 2009 4:57 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] WS-6500-SFM insertion into production box, much of an impact? Howdy, I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), and I want to know if the modules go from using Bus only backplane to crossbar as soon as the module initiates or whether a reload would actually be required for this. Cheers Ben ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Remember that full SFM usage requires all modules to be fabric-enabled. If there are any line cards that aren't fabric enabled, all traffic will still go thru the bus, doesn't matter if it is an OIR or from power-up. Your question is if this OIR stands for Online Insertion and Removal or for Online Insertion and Reboot... although I don't know the answer, what I saw over the years is that even if it doesn't require a reboot, you will want to do one, because any issues will have after that will make you wonder whether if it's due to OIR or not, so you will end up rebooting anyway. So, reboot while you have a planned window to do so, not when you are under pressure. Rubens On Sun, Feb 8, 2009 at 9:56 PM, Ben Steele illcrit...@gmail.com wrote: Howdy, I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), and I want to know if the modules go from using Bus only backplane to crossbar as soon as the module initiates or whether a reload would actually be required for this. Cheers Ben ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Thanks Rubens, i'm aware of the line card requirements to operate in full compact mode, my question i'm really interested in is during the insertion of the module is there any dropped packets while the cards move from a Bus switching mode to compact switching. On Mon, Feb 9, 2009 at 12:06 PM, Rubens Kuhl rube...@gmail.com wrote: Remember that full SFM usage requires all modules to be fabric-enabled. If there are any line cards that aren't fabric enabled, all traffic will still go thru the bus, doesn't matter if it is an OIR or from power-up. Your question is if this OIR stands for Online Insertion and Removal or for Online Insertion and Reboot... although I don't know the answer, what I saw over the years is that even if it doesn't require a reboot, you will want to do one, because any issues will have after that will make you wonder whether if it's due to OIR or not, so you will end up rebooting anyway. So, reboot while you have a planned window to do so, not when you are under pressure. Rubens On Sun, Feb 8, 2009 at 9:56 PM, Ben Steele illcrit...@gmail.com wrote: Howdy, I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), and I want to know if the modules go from using Bus only backplane to crossbar as soon as the module initiates or whether a reload would actually be required for this. Cheers Ben ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
On Mon, Feb 9, 2009 at 3:25 AM, Ben Steele illcrit...@gmail.com wrote: Thanks Rubens, i'm aware of the line card requirements to operate in full compact mode, my question i'm really interested in is during the insertion of the module is there any dropped packets while the cards move from a Bus switching mode to compact switching. It's been a while so my mind may be playing tricks on me, but as I recall the box hiccups a bit while it does its backplane sync magic and then continues on its merry way. Depending on timing and your traffic patterns this event may or may not rate as noticeable to your users. Note that I can't swear that my recollection reflects inserting a new SFM into a box currently in bus mode (as opposed to swapping out an existing SFM), so YMMV. I'll echo the recommendation to schedule downtime and reload the box just to be sure. -link ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WS-6500-SFM insertion into production box, much of an impact?
Hi, On Mon, Feb 09, 2009 at 10:26:42AM +1030, Ben Steele wrote: I'm looking for some info on the insertion of a SFM into a live 6500(Sup2 obviously), can't seem to find any info on Cisco as to the consequences this may have to traffic flowing through the Bus at the time(ie dropped packet rates), and I want to know if the modules go from using Bus only backplane to crossbar as soon as the module initiates or whether a reload would actually be required for this. I've never done this, so I can speak from personal experience. Judging from the overwall way the box decides how to do switching (if there is a 3A DFC in the system, all 3B PFCs fall back to 3A mode, and you need a reload to get it back to 3B), my guess would be you can insert it just fine, but it won't be used for switching unless you reload. So I'd schedule a maintenance window with downtime. I'm looking forward to hear about your experiences, though :-) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgpZVa40tFoKV.pgp Description: PGP signature ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
