Re: [c-nsp] x6148 vs. x6548
I stand corrected... I have double checked, and I remembered it all wrong (assumed it's like with the 6748...). Only 1x8G. BTW, if you want to use an etherchannel with one port on a 65XX and another on a 61XX (or another combination of qos-wise incompatible cards) you need to use the following command no mls qos channel-consistency Arie -Original Message- From: Sachin Gupta (sagupta) Sent: Sunday, June 14, 2009 07:00 To: Arie Vayner (avayner); 'ge...@pendery.net'; 'bblackf...@nwresd.k12.or.us' Cc: 'cisco-nsp@puck.nether.net' Subject: Re: [c-nsp] x6148 vs. x6548 The 6548 has a single 8G fabric connection. Sachin - Original Message - From: cisco-nsp-boun...@puck.nether.net cisco-nsp-boun...@puck.nether.net To: Geoffrey Pendery ge...@pendery.net; Bill Blackford bblackf...@nwresd.k12.or.us Cc: cisco-nsp@puck.nether.net cisco-nsp@puck.nether.net Sent: Sat Jun 13 20:48:17 2009 Subject: Re: [c-nsp] x6148 vs. x6548 Geoffrey, A small correction. The x6548 is an 8G card, but it has 2 fabric connections, so the limit would be 16G. As long as you do not use the other 7 ports out of each 8 port group, each port group can give you 1G, but take into consideration that the x6148 is a classic card, so it has no fabric connections, and uses the shared bus. In general the x6148 is not supposed to be a core card. It's for connecting low end desktops etc. Arie -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Geoffrey Pendery Sent: Friday, June 12, 2009 16:36 To: Bill Blackford Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] x6148 vs. x6548 Well, with the 6548, you're still going to be limited to 8 Gbps, rather than 6 Gbps. It's a CEF256 card, which means it has an 8 Gbps fabric connection to the supervisor, instead of just sharing the 32 Gbps like the 6148 does. So if you're looking to drive more than a gig through an Etherchannel, it will do it, but only for a limited number of them. The 6748 would bump your bottleneck up to 40 Gbps. I have a question of my own, since this subject has come up a time or two - regarding the 6148's, the statement is made a couple times that Etherchannel will get you port redundancy but no extra bandwidth, since the ASIC is only a gig. But if I distribute my channel across two slots, say Gig 1/1 and Gig 2/1, does that get me around the gig limit? Or even Gig 1/1 and Gig 1/48, since it's separate ASICs? Logic tells me yes, but I've heard the 1 gig limit mentioned as if it's a hard platform limitation, not just a result of a particular bottleneck. My instinctive behavior with channels is to span them across blades anyway, to guard against blade failure -Geoff On Thu, Jun 11, 2009 at 9:20 PM, Bill Blackfordbblackf...@nwresd.k12.or.us wrote: I've recently learned that the ws-x6148-ge-tx has 6 gig ASICs, one for every 8 ports thusly rendering this line card to a 8:1 oversubscription ratio. I've also learned that an etherchannel is limited to 1 gig, great for redundancy, but slow as all get up. I'm buying a ws-x6548-ge-tx in hope that it can do much better (I didn't have enough in my budget for a x6748). How does the 6548 compare to the 6148? I have a pair of shiny new sup720-3bxl's. Thank you for any insight from the field as Cisco's site seems best suited for the marketing of products. -b -- Bill Blackford Senior Network Engineer Technology Systems Group Northwest Regional ESD my /home away from home ___ cisco-nsp mailing list cisco-...@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/ ___ 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/
[c-nsp] port channel overruns
hey all i have Cisco 7606 and i configured port channel consisting of 5 links now the individual ports (Gig) , do not have overruns but the port channel has even though the ports in the mentioned port channel have 8 ports spacing to overcome the issue of ASIC can anyone help ? Router#sh int po20 | inc overr 0 input errors, 0 CRC, 0 frame, 468063 overrun, 0 ignored Thanks in advance _ Drag n’ drop—Get easy photo sharing with Windows Live™ Photos. http://www.microsoft.com/windows/windowslive/products/photos.aspx ___ 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] port channel overruns
i have Cisco 7606 and i configured port channel consisting of 5 links now the individual ports (Gig) , do not have overruns but the port channel has even though the ports in the mentioned port channel have 8 ports spacing to overcome the issue of ASIC can anyone help ? What type of card are your ports on? What type of Supervisor? Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ 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] 6500/SUP32 - RP ROMMON upgrade?
Hi all, I just updated the SP¹s ROMMON on a Sup32 to the latest, c6ksup32-rm2.srec.122-18r.SX9. However, can this same file be applied to update the RP's ROMMON as well? While logged into CCO I have only came across docs that referred to the SP upgrade. I guess no biggie if the SP and RP have difference ROMMON versions, I was just curious. Thanks, -graham ___ 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] 6500/SUP32 - RP ROMMON upgrade?
Hi, semi-hijack On Mon, Jun 15, 2009 at 8:52 AM, Graham Woodengra...@g-rock.net wrote: I just updated the SP¹s ROMMON on a Sup32 to the latest, c6ksup32-rm2.srec.122-18r.SX9. However, can this same file be applied to update the RP's ROMMON as well? While logged into CCO I have only came across docs that referred to the SP upgrade. I guess no biggie if the SP and RP have difference ROMMON versions, I was just curious. I'm curious about how many people out there manage ROMMON/bootflash images in the same way the 'main' image is managed. In one customer network, there are tens of 7200s running 12.4T code with 12.3-based boot code. The same network has 20+ 6500s (sup32/sup720) running various 12.2(18)SXF images and I doubt anyone's ever given a second thought to 'auxiliary' code like ROMMON or any other flashable components. So, is stuff like ROMMON a set-and-forget or never-even-thought-about-it thing for you, or do you actively track image availability and factor upgrades in to your broader platform management activities? Is it considered good practice, for example, to match 7200 series boot flash revs with the main image, or does this fall into the if it ain't broke, .. category? cheers, Dale ___ 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] 6500/SUP32 - RP ROMMON upgrade?
The key issue with the boot image is being able to access the flash device where the real image exists. A number of devices, ie Majority, no longer need this but in the past upgrading to an ATA Flash card / disk0:, from linear flash / slot0: meant that you needed a boot image that could support the flash. The 7500 is an absolute for having the two in sync. 6500 MSFC3 ROMMON http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/rommon/OL_4497.htm l David -- http://dcp.dcptech.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Dale Shaw Sent: Sunday, June 14, 2009 7:54 PM To: Graham Wooden Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] 6500/SUP32 - RP ROMMON upgrade? Hi, semi-hijack On Mon, Jun 15, 2009 at 8:52 AM, Graham Woodengra...@g-rock.net wrote: I just updated the SP¹s ROMMON on a Sup32 to the latest, c6ksup32-rm2.srec.122-18r.SX9. However, can this same file be applied to update the RP's ROMMON as well? While logged into CCO I have only came across docs that referred to the SP upgrade. I guess no biggie if the SP and RP have difference ROMMON versions, I was just curious. I'm curious about how many people out there manage ROMMON/bootflash images in the same way the 'main' image is managed. In one customer network, there are tens of 7200s running 12.4T code with 12.3-based boot code. The same network has 20+ 6500s (sup32/sup720) running various 12.2(18)SXF images and I doubt anyone's ever given a second thought to 'auxiliary' code like ROMMON or any other flashable components. So, is stuff like ROMMON a set-and-forget or never-even-thought-about-it thing for you, or do you actively track image availability and factor upgrades in to your broader platform management activities? Is it considered good practice, for example, to match 7200 series boot flash revs with the main image, or does this fall into the if it ain't broke, .. category? cheers, Dale ___ 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] 6500/SUP32 - RP ROMMON upgrade?
Dale Shaw wrote: I'm curious about how many people out there manage ROMMON/bootflash images in the same way the 'main' image is managed. In one customer network, there are tens of 7200s running 12.4T code with 12.3-based boot code. The same network has 20+ 6500s (sup32/sup720) running various 12.2(18)SXF images and I doubt anyone's ever given a second thought to 'auxiliary' code like ROMMON or any other flashable components. So, is stuff like ROMMON a set-and-forget or never-even-thought-about-it thing for you, or do you actively track image availability and factor upgrades in to your broader platform management activities? Is it considered good practice, for example, to match 7200 series boot flash revs with the main image, or does this fall into the if it ain't broke, .. category? 7200s have three places where code is stored, ROMMON, Bootflash, and the main image. ROMMON is a physical Yank this chip out of its socket and replace it with another chip so not flashable. Not DIY unless you have an EPROM burner and a factory chip with newer code to dump. I typically don't worry about bootflash unless there's a compatibility issue with that and a newer IOS, but this is indeed flashable and images are available on CCO. On smaller platforms the ROMMON and bootflash are combined onto a single BootROM. This is also a Yank the physical chip and replace it type of thing. Occasionally this needs to be upgraded when newer code becomes too large for the original design to address, but it's been a long time since I've needed to deal with it, IIRC the 2500 and maybe early 2600 series routers. In my experience on most platforms these are set and forget, but I don't have a lot of hands-on with the 6500. -- Jay Hennigan - CCIE #7880 - Network Engineering - j...@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV ___ 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] 6500/SUP32 - RP ROMMON upgrade?
7200s have three places where code is stored, ROMMON, Bootflash, and the main image. ROMMON is a physical Yank this chip out of its socket and replace it with another chip so not flashable. Not DIY unless you have an EPROM burner and a factory chip with newer code to dump. Depends on the NPE. NPE-G1 rommon can be upgraded, most notably for the short- lived MPF functionality. ___ 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] 6500/SUP32 - RP ROMMON upgrade?
Thanks David and Dale for the insights. SP Rommon was pretty far back, and upgrading it solved an issue I was having. However, after reading the caveats listed for the MSFC2A, I don't think I am going to mess with the RP - until I really need to. Thanks again, -graham On 6/14/09 7:07 PM, David Prall d...@dcptech.com wrote: The key issue with the boot image is being able to access the flash device where the real image exists. A number of devices, ie Majority, no longer need this but in the past upgrading to an ATA Flash card / disk0:, from linear flash / slot0: meant that you needed a boot image that could support the flash. The 7500 is an absolute for having the two in sync. 6500 MSFC3 ROMMON http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/rommon/OL_4497.htm l David -- http://dcp.dcptech.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Dale Shaw Sent: Sunday, June 14, 2009 7:54 PM To: Graham Wooden Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] 6500/SUP32 - RP ROMMON upgrade? Hi, semi-hijack On Mon, Jun 15, 2009 at 8:52 AM, Graham Woodengra...@g-rock.net wrote: I just updated the SP¹s ROMMON on a Sup32 to the latest, c6ksup32-rm2.srec.122-18r.SX9. However, can this same file be applied to update the RP's ROMMON as well? While logged into CCO I have only came across docs that referred to the SP upgrade. I guess no biggie if the SP and RP have difference ROMMON versions, I was just curious. I'm curious about how many people out there manage ROMMON/bootflash images in the same way the 'main' image is managed. In one customer network, there are tens of 7200s running 12.4T code with 12.3-based boot code. The same network has 20+ 6500s (sup32/sup720) running various 12.2(18)SXF images and I doubt anyone's ever given a second thought to 'auxiliary' code like ROMMON or any other flashable components. So, is stuff like ROMMON a set-and-forget or never-even-thought-about-it thing for you, or do you actively track image availability and factor upgrades in to your broader platform management activities? Is it considered good practice, for example, to match 7200 series boot flash revs with the main image, or does this fall into the if it ain't broke, .. category? cheers, Dale ___ 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/
[c-nsp] Two events in EEM
hi i work for cisco in UC technology. i am very new to EEM. I dont deal with scripting at all but i have to create one for one of my customers I have created an event manager applet with an ' #event syslog pattern pattern. Now after matching the pattern i want it wait for a countdown timer and the execute certain cli commands. what's the easiest way to do it ? i think with EEM i cant make my first applet to call another applet which has a countdown timer because with #action 1.0 cli command event manager run 2nd applet in this 2nd applet should have event none if i need to call it manually from 1st applet but thats not the case because 2nd applet will have a countdown timer as its event. any help on this would be highly appreciated thanks and regards inder ___ 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/
