Re: [c-nsp] Multicast over VRF possible?
Jeff, At this point multicast on VRF interfaces is only supported with Sup6-E and 4900M. http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/52sg/conf iguration/guide/vrf.html#wp1064137 6500 does it on any PFC3 based sup since SXE. Cheers, Ben -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Douglas C. Stephens Sent: Wednesday, May 27, 2009 7:48 PM To: Jeff Kell Cc: 'NSP List' Subject: Re: [c-nsp] Multicast over VRF possible? Jeff, I've successfully used ip pim sparse-mode on SVIs assigned to VRF-lite contexts on all my 6500s. This was on Sup720+MSFC3+PFC3B blades running both ADVENTERPRISEK9_WAN-M and ADVIPSERVICESK9_WAN-M feature sets of the 12.2(18)SXF release. I've not run into this problem on my 4500 switches, but then I'm running them with SupV blades, and I've not yet had much call for VRF-lite there. At 07:54 PM 5/27/2009, Jeff Kell wrote: In the process of an upgrade/reconfiguration today, I discovered that PIM multicast routing and VRF-lite are apparently mutually exclusive on a 4506. In this case, specifically IOS cat4500-entservicesk9-mz.122-50.SG1 on a Sup-IV WS-X4515. With an ip vrf forwarding ... directive, there is no ip pim option available, it disappears from the configuration options. OK, that was the old school fix to make some limited multicast work in this situation (Symantec Ghost for imaging remote labs). Is there another way to achieve routed multicasting in a VRF environment? Specifically, the imaging server resides in a public services VRF, while the target labs are in other VRFs. Is this a platform-specific restriction? Or is it Catalyst-wide? Can the 6500 handle it (on a 'ip vrf forward'ed interface or SVI)? There are some imaging alternatives (just relocate a suitable master copy to the local subnet), but there are some other multicast plans on the table that aren't so easily bypassed. Thanks in advance, Jeff ___ 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/ -- Douglas C. Stephens | UNIX/Windows/Email Admin System Support Specialist | Network/DNS Admin Information Systems | Phone: (515) 294-6102 Ames Laboratory, US DOE | Email: steph...@ameslab.gov ___ 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] Remove BGP AS path number number from an AS PATH
Hello All Is their a way to remove the first AS number (not private) from an AS path? For example we are receiving a route with AS PATH 123 456 456 456 and we want to remove the 123 AS and put in the BGP table the route with AS 456 456 456 . Thanks for your reply ___ 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] router 7609
Hi Uuganbat, The 10-port GE SPA is a module residing in the SIP-600 card (which is required) and the SFP is the actual optical module. Due to pricing, I would believe you get cheaper ports by using another 24-port optical GE linecard, as the 10-port SPA would cost the additional SIP-600 which isn't cheap at all. __ Med venlig hilsen / Kind regards Lars Lystrup Christensen Director of Engineering, CCIE(tm) #20292 Danske Telecom A/S Sundkrogsgade 13, 4 2100 København Ø -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of uugnaa Sent: 28. maj 2009 06:49 To: cisco-nsp@puck.nether.net Subject: [c-nsp] router 7609 hello all, I am going to make an order for Cisco Router 7609 with Cisco 7600 Series Supervisor Engine 32 (8 ports Gigabit Ethernet). My question is I need 24 Optical GE ports line card and another 7 Optical GE ports line card. I have seen the line card of 10-Port Gigabit Ethernet Shared Port Adapters. Please somebody make me clear on this what is the SPA(Shared Port Adapter). The difference between SPA and SFP. regards, uuganbat ___ 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] ITP Deployment Guide
Hi Team, A messaging company that wants to sell a solution to a mobile carrier has subcontracted a portion of implementation for their demo solution to my company. My portion of the project requires deploying SSoIP using Cisco ITP with two 2811 routers at both sides of a link, in a staged lab. Frankly, the contractor's ITP requirements are yet to be defined. Coming from a purely IP background, I expect this to be a challenge. I should be glad if any on this list could share with me links to useful guides, examples, scenarios, experiences, caveats, etc on Cisco's ITP offering. Thanks for your responses. Felix ___ 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] Remove BGP AS path number number from an AS PATH
I doubt that you can do that... but if this is to influence your outgoing traffic, then I would use local-preferences. Christophe -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Michalis Palis Sent: Thursday, May 28, 2009 9:49 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Remove BGP AS path number number from an AS PATH Hello All Is their a way to remove the first AS number (not private) from an AS path? For example we are receiving a route with AS PATH 123 456 456 456 and we want to remove the 123 AS and put in the BGP table the route with AS 456 456 456 . Thanks for your reply ___ 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/ __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com ___ 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] Remove BGP AS path number number from an AS PATH
yup, you can't remove public AS from AS path. would you please share the idea why you wana remove it :) there are many other attributes to tweak bgp, y not u use them. BR\\ Masood I doubt that you can do that... but if this is to influence your outgoing traffic, then I would use local-preferences. Christophe -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Michalis Palis Sent: Thursday, May 28, 2009 9:49 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Remove BGP AS path number number from an AS PATH Hello All Is their a way to remove the first AS number (not private) from an AS path? For example we are receiving a route with AS PATH 123 456 456 456 and we want to remove the 123 AS and put in the BGP table the route with AS 456 456 456 . Thanks for your reply ___ 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/ __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com ___ 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] heat fins popping loose on WS-X67xx cards
In the past 9 days I've found that 3 of our Catalyst 6500 WS-X67xx cards (2 WS-X6748-GE-TX 1 WS-X6748-SFP) had dislodged heat fins. The fins are supposed to be tethered by a spring hooked into a small wire loop which seems to be soldered onto the circuit board. In the case at hand the wire loop pulls out of the board the heat fin then flops around free in 1 case the wire loop was rattling around on the card. Not good. I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? Jay Ford, Network Engineering Group, Information Technology Services University of Iowa, Iowa City, IA 52242 email: jay-f...@uiowa.edu, phone: 319-335-, fax: 319-335-2951 ___ 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] Remove BGP AS path number number from an AS PATH
Let's be more precise. There is no publicly known way to remove a non-private AS number from AS-path on a device running Cisco IOS ... but you could always adapt Quagga source code to your needs. As pointed out by previous replies, tweaking AS-PATH is a really bad idea. BGP has numerous other tools. Ivan http://www.ioshints.info/about http://blog.ioshints.info/ -Original Message- From: mas...@nexlinx.net.pk [mailto:mas...@nexlinx.net.pk] Sent: Thursday, May 28, 2009 6:56 PM To: Varaillon Jean Christophe Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Remove BGP AS path number number from an AS PATH yup, you can't remove public AS from AS path. would you please share the idea why you wana remove it :) there are many other attributes to tweak bgp, y not u use them. BR\\ Masood I doubt that you can do that... but if this is to influence your outgoing traffic, then I would use local-preferences. Christophe -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Michalis Palis Sent: Thursday, May 28, 2009 9:49 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Remove BGP AS path number number from an AS PATH Hello All Is their a way to remove the first AS number (not private) from an AS path? For example we are receiving a route with AS PATH 123 456 456 456 and we want to remove the 123 AS and put in the BGP table the route with AS 456 456 456 . Thanks for your reply ___ 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/ __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com ___ 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] Sup720-3B Gig port mac address strangeness
On Wed, May 27, 2009 at 08:21:22PM +0100, Jared Gillis wrote: Hello all, I'm working with 2 7606s, each with 1 Sup720-3B, and noticed something strange when moving the Supervisors between the two chassis. The MAC address assigned to the gig ports on the Supervisor seems to stick with a chassis, rather than follow the Supervisor. For example, I plug Supervisor A into chassis A, and the first gig port on the supervisor gets assigned MAC address A. Sup B in chassis B gets MAC B likewise. I then write erase both Supervisors, power down both chassis, and swap the Supervisors. Now Sup A is in chassis B, and Sup B in chassis A. However, Sup A in chassis B gets MAC B, and Sup B in chassis A gets MAC A. This is contrary to how I would expect this to work, as MACs are usually programmed into the EEPROM on the interface card. This is supported by the Cisco docs here: http://www.cisco.com/en/US/docs/routers/7600/Hardware/Hardware_Guides/Supervisor_Engine_and_Route_Switch_Processor_Guide/SupE01.html#wp1015861 Is this a known feature of the 7600/Sup720-3B? IIRC SVIs use the chassis mac address, and routed ports use the phy MAC address. L2 PDUs (STP, CDP, LLDP) always use the phy mac. -- Jared Gillis - ja...@corp.sonic.net Sonic.net, Inc. Network Operations2260 Apollo Way 707.522.1000 (Voice) Santa Rosa, CA 95407 707.547.3400 (Support)http://www.sonic.net/ ___ 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] CPUHOG - BGP Scheduler
Hi, I would start by looking at upgrading. SRB1 has a lot of known BGP bugs. Most notably is BGP process hogging CPU on large table convergence. SRB3 is stable as long as you don't do sh mem, will crash active proc SRB5 is stable as long as you don't care about netflow SRD1 so far ok If you don't need the latest features in SRD I would stick with the latest SRB train. RR On Wed, May 27, 2009 at 3:13 PM, Bill Blackford bblackf...@nwresd.k12.or.us wrote: So this started showing up: May 27 14:45:26: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (0/0),process = BGP Scheduler. -Traceback= 824C1AC 8261AF8 8261D84 94FA00C 8263BB0 8263CCC A6DCBC8 A6D2A54 May 27 14:46:34: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (1/1),process = BGP Scheduler. -Traceback= 824C214 8261AF8 8261D84 94FA00C 8263BB0 8263CCC A6DCBC8 A6D2A54 May 27 14:47:26: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (1/0),process = BGP Scheduler. -Traceback= 824C1D8 8261AF8 8261D84 94FA00C 8263BB0 8263CCC A6DCBC8 A6D2A54 7606/RSP720-3CXL/12.2(33)SRB1 Uptime is 1 year, 26 weeks. Two full feeds and 10 other peers. Where should I start looking? Thanks -b -- Bill Blackford bblackf...@nwresd.k12.or.us Senior Network Engineer 503-614-1460 Desk Technology Systems Group 503-863-0561 Cell Northwest Regional ESD 503-614-1400 Helpdesk 5825 Ray Circle 503-614-1281 Fax Hillsboro, Oregon 97124 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/
Re: [c-nsp] heat fins popping loose on WS-X67xx cards
On Thu, 2009-05-28 at 11:19 -0500, Jay Ford wrote: In the past 9 days I've found that 3 of our Catalyst 6500 WS-X67xx cards (2 WS-X6748-GE-TX 1 WS-X6748-SFP) had dislodged heat fins. The fins are supposed to be tethered by a spring hooked into a small wire loop which seems to be soldered onto the circuit board. In the case at hand the wire loop pulls out of the board the heat fin then flops around free in 1 case the wire loop was rattling around on the card. Not good. I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? We had this happen to three 6748-GE-TX cards. We discovered it while performing some physical relocations/upgrades. It might have happened to other modules that we didn't look at. For some reason we decided to let one of the systems run, just to see what effect it had. FWIW it has had no problems for ~1 year now. It was no problem RMAing them. 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] heat fins popping loose on WS-X67xx cards
On Thu, 28 May 2009, Jay Ford wrote: I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? I've seen this sort of failure on the chipset heatsink on a Soyo P4 motherboard. I used superglue to 're-anchor' the wire loop into the motherboard. The repair outlasted the motherboard (which eventually died due to bad [expanding leaking] capacitors). -- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net| _ http://www.lewis.org/~jlewis/pgp for PGP public key_ ___ 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 debugging on C2924
On Tue, May 26, 2009 at 02:01:25PM -0400, Tuc at T-B-O-H wrote: If I had physical access, thats exactly what I'd do. But I don't, so I need it to dump the packets into syslog for me. I don't have debug packet available on the IOS on the unit, nor does debug interface seem to be generating anything There's nothing available on that hardware. Port monitor is your only choice. That makes bunny sad. Ok, thanks. I guess I'm SOL until the next site visit. Tuc ___ 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] heat fins popping loose on WS-X67xx cards
Hi Jay, I've RMA'ed at least one board and could suspect other boards with the same flaw, so I believe this might be either a design fault or simply a faulty batch. __ Med venlig hilsen / Kind regards Lars Lystrup Christensen Director of Engineering, CCIE(tm) #20292 Danske Telecom A/S Sundkrogsgade 13, 4 2100 København Ø -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jay Ford Sent: 28. maj 2009 18:19 To: cisco-nsp Subject: [c-nsp] heat fins popping loose on WS-X67xx cards In the past 9 days I've found that 3 of our Catalyst 6500 WS-X67xx cards (2 WS-X6748-GE-TX 1 WS-X6748-SFP) had dislodged heat fins. The fins are supposed to be tethered by a spring hooked into a small wire loop which seems to be soldered onto the circuit board. In the case at hand the wire loop pulls out of the board the heat fin then flops around free in 1 case the wire loop was rattling around on the card. Not good. I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? Jay Ford, Network Engineering Group, Information Technology Services University of Iowa, Iowa City, IA 52242 email: jay-f...@uiowa.edu, phone: 319-335-, fax: 319-335-2951 ___ 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] heat fins popping loose on WS-X67xx cards
In the past 9 days I've found that 3 of our Catalyst 6500 WS-X67xx cards (2 WS-X6748-GE-TX 1 WS-X6748-SFP) had dislodged heat fins. The fins are supposed to be tethered by a spring hooked into a small wire loop which seems to be soldered onto the circuit board. In the case at hand the wire loop pulls out of the board the heat fin then flops around free in 1 case the wire loop was rattling around on the card. Not good. I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? It sounds like a design flaw. The spring force on the loop is upward. Heat from the chip is conducted to the fins, the spring, and the loop which softens the solder. Tension on the loop pulls it out. They probably need to come up with a different means of attaching the loop, maybe a stamped part with a base on the underside of the board, or at the least use a high-melting-point solder for that attachment point. -- -- 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] Remove BGP AS path number number from an AS PATH
This list does tend to focus on public internet issues and forget that BGP is used in corporate or other non-internet environments that don't follow nice conventions and after 15+ years of corporate take-overs,mergers and demergers can often find situations where AS Paths need to be cleanedor manipulated with something more flexible than a straight pre-pend. IOS allows every other key BGP metric to be tweaked and we accept the risks that brings - so this sort of manipulation of the AS-Path is long overdue. Examples where I have had to dump BGP routes into an IGP for a hop and stick them back into BGP with a clean AS-Path. :- A) 2 independant organisations both use MPLS VPN from the same provider and want to exchange routes across a private peering. The MPLS provider AS is in the AS-Path on both sides and the provider drops routes. The provider doesn't offer any of the provider side workarounds. B) 1 Organisation that has historically been a fully private network and has some historic peerings that use non-private AS/non-registered AS now wants to have a private peering with a proper public network. The AS-Path needs to have the junk removed before the routes could be advertised. Yes the historic networks should be migrated away but the fact is there is often no resource and no money to do that when the workaround is simply another Router. C) Organisation wants to Dual Home to 2 ISPs at 2 locations for a new internet service. It wants to use its private network for backhaul between the sites but can't have free flow of routes between because if they traverse the MPLS VPN they get the provider AS inserted in the path. I don't intend to debate the abovethey happened and the solutions were ratified by Cisco but in all cases manipulating the AS-Path (usually to remove the MPLS provider public AS) would have been much much easier than the final solutions. The summary is...BGP isn't just used on the Internet, and corporate networks get messy when CEOs get ambitious (or fired). Dean -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of mas...@nexlinx.net.pk Sent: 28 May 2009 17:56 To: Varaillon Jean Christophe Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Remove BGP AS path number number from an AS PATH yup, you can't remove public AS from AS path. would you please share the idea why you wana remove it :) there are many other attributes to tweak bgp, y not u use them. BR\\ Masood I doubt that you can do that... but if this is to influence your outgoing traffic, then I would use local-preferences. Christophe -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Michalis Palis Sent: Thursday, May 28, 2009 9:49 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Remove BGP AS path number number from an AS PATH Hello All Is their a way to remove the first AS number (not private) from an AS path? For example we are receiving a route with AS PATH 123 456 456 456 and we want to remove the 123 AS and put in the BGP table the route with AS 456 456 456 . Thanks for your reply ___ 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/ __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4112 (20090528) __ The message was checked by ESET Smart Security. http://www.eset.com ___ 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/
Re: [c-nsp] heat fins popping loose on WS-X67xx cards
Can someone please take a photo and upload it somewhere, so everyone else can better understand what exactly is the issue you're talking about? -- Tassos Jay Hennigan wrote on 29/05/2009 00:23: In the past 9 days I've found that 3 of our Catalyst 6500 WS-X67xx cards (2 WS-X6748-GE-TX 1 WS-X6748-SFP) had dislodged heat fins. The fins are supposed to be tethered by a spring hooked into a small wire loop which seems to be soldered onto the circuit board. In the case at hand the wire loop pulls out of the board the heat fin then flops around free in 1 case the wire loop was rattling around on the card. Not good. I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? It sounds like a design flaw. The spring force on the loop is upward. Heat from the chip is conducted to the fins, the spring, and the loop which softens the solder. Tension on the loop pulls it out. They probably need to come up with a different means of attaching the loop, maybe a stamped part with a base on the underside of the board, or at the least use a high-melting-point solder for that attachment point. ___ 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] heat fins popping loose on WS-X67xx cards
We experienced the same problem on a number of 6748 blades, and requested failure analysis from Cisco (report below). We were performing a chassis swap, and the heatsink/fin/whatever literally fell off upon card removal, which led to the discovery of the faulty bracket on multiple cards -- but not all cards. Here's the failure analysis report: *FA case Number: FA-0063752 Fault Isolated The customer reported that the line cards had faulty Heatsink latches. The customer's symptom was duplicated. The line cards failed visual inspection. The line card with serial number REMOVED had a Z1 latch became detached. The Z1 came off and caused the heatsink to become loose. No damage was done to the baseboard. The line card with serial number REMOVED had both Z1 and Z2 missing. The latches were not on the card, which caused the Heatsink to move around. Only some minor scratches were observed on the baseboard. This case was closed as fault isolated due to the detached latches on the boards. MM/CG* -- Eric Cables On Thu, May 28, 2009 at 9:19 AM, Jay Ford jay-f...@uiowa.edu wrote: In the past 9 days I've found that 3 of our Catalyst 6500 WS-X67xx cards (2 WS-X6748-GE-TX 1 WS-X6748-SFP) had dislodged heat fins. The fins are supposed to be tethered by a spring hooked into a small wire loop which seems to be soldered onto the circuit board. In the case at hand the wire loop pulls out of the board the heat fin then flops around free in 1 case the wire loop was rattling around on the card. Not good. I'm trying to determine if this is a systemic problem or just a fluke. It seems like a design flaw, with the spring being too much for the soldered wire loop. Has anybody else seen this? If so, with how many cards of what types? Jay Ford, Network Engineering Group, Information Technology Services University of Iowa, Iowa City, IA 52242 email: jay-f...@uiowa.edu, phone: 319-335-, fax: 319-335-2951 ___ 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] heat fins popping loose on WS-X67xx cards
On Fri, 29 May 2009, Tassos Chatzithomaoglou wrote: Can someone please take a photo and upload it somewhere, so everyone else can better understand what exactly is the issue you're talking about? Pardon the crappy cellphone pic...but http://www.lewis.org/~jlewis/heatsink.jpg The anchor points (at least on this motherboard) basically look like jumper posts that have been joined with an arch. The heatsink is held in place by spring tension against the four anchors. Just one anchor failing results in the heatsink popping up off the chip and in my case resulted in very frequent system crashes. -- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net| _ http://www.lewis.org/~jlewis/pgp for PGP public key_ ___ 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] Comparison chart of 6509-E vs 4506-E
Hello Jeff I work for the government so we do have cisco, i will ask him for the NDA and thank you the info you have provided is very helpful Renelson On Wed, May 27, 2009 at 4:31 PM, Jeff Wolfe wo...@ems.psu.edu wrote: Do you have access to a Cisco sales team and SE? You should ask for an NDA on the 4500 and 6500. The architecture of the 4500 is different than the 6500. In the 4500, the linecards are basically smart PHYs, all the packets go back to the SUP for switching/forwarding.. The E chassis currently has 24Gb/s per slot back to the Sup, resulting in 2:1 oversubscription on all ports. Compare that with the 6500, where it depends. 61xx modules put all packets on a 16Gb/s ring bus that passes through the SUP. Packets go on the bus regardless of where they exit the switch. 67xx modules have 20 or 40Gb/s 'taps' to the SUP. Packets go to the SUP for forwarding, unless the card has a DFC module, in which case the packets only go to the SUP if the destination port is not on the same slot. 6500 can hold other non-linecard modules, 4500 can not. 6500 does netflow. 4500 Sup5 does netflow, but Sup6E does *not* do netflow. We like the 4500 a lot. It's not perfect, but it fits our current and future needs in our enterprise LAN. We have 4507R-E chassis with redundant SUPs and full of 48p 1G linecards. They provide all the same functionality that a 6509 would, but they're physically smaller, consume half the power and are approximately half the price of the DFC enabled 6509 with 67xx modules. Compared to a 6509 with 61xx modules and Sup32, the 4500 is a considerably better switch from a performance and capacity perspective. You should ask your Cisco reps for an NDA on the 4500 and 6500. They have detailed comparisons, but they're only shown under NDA. $0.02 -JEff Renelson Panosky wrote: Hey James Thank you that's the same thing i found on the cisco website but i was hoping for something a little better but thanks anyway ___ 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/
