[c-nsp] Certificate Update and Resource of CCIE
Hello Cisco -nsp group, My CCNP certificate is about to expire and want to renew it with CCIE SP written exam, can someone help me to find CCIE SP V3 (350-02) book? From where i can get this book or someone please mail me the soft copy if you have, it will be great help. Thank You Regards Four Pros ___ 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] Maximum traffic on Gigabit Ethernet
Normal Configuration: interface GigabitEthernet5/2 ip address x.x.x.x no ip redirects no ip proxy-arp media-type rj45 MTU is default 1500 -Original Message- From: Scott Granados Sent: Monday, October 03, 2011 5:25 PM To: Manaf Al Oqlah ; Group Study ; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Maximum traffic on Gigabit Ethernet Depends on the traffic type, packet sizes and what features you have enabled. Can you detail the port configurationa bit more? -Original Message- From: Manaf Al Oqlah Sent: Monday, October 03, 2011 9:47 AM To: Group Study ; cisco-nsp@puck.nether.net Subject: [c-nsp] Maximum traffic on Gigabit Ethernet Hi, What is the maximum traffic that a gigabit Ethernet interface can handle on Cisco 7600 router RSP720-3C-GE before dropping packets . we are able to reach 750 mbps / 125 mbps input/out rate! thank you ___ 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] download IOS for EOL/EOS hardware
Hey, I'm wonder what's up with access to IOS software for EOL/EOS hardware for example 3600 router serises EOL is 31 dec 2008. Downdload section still saying I need contract to download, while it's been EOS for years. Maybe I miss something and it not completely EOS? Yes we still using these old boxes as ISDN to IP gateways in some remote sites. Some of them running 12.2 just fine, but some experience crashes, so we though maybe we could upgrade to latest stable release. ___ 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] C7600 vs. ASR 9000
On (2011-10-04 00:26 -0400), Jason Lixfeld wrote: The ASR line cards resemble the ES series on the 7600. Where? If one is using an ES port on a 7600, I'd assume one is likely using EVCs on said port. The ES ports on the 7600s do not support SPAN on a physical interface that is configured with EVCs. The ASR9k thankfully supports this extremely basic feature. The 7600 ES port's lack of SPAN on an EVC would lead me to believe that the ASIC controlling the ES is very different than the ASIC controlling the ASR linecards. ASR9k does not have any PFC engines, like 7600 must have. But indeed ES+ EZchip is same chip ASR9k uses exclusively (there are no PFCs in ASR9k). Also IIRC the fabric ASR9k uses is from 'cat' BU, same fabric nexus7k uses (i.e. next-gen cat6k fabric). (In this sense 7600 with ES+ is lot more complex than ASR9k, as you need to have both ES+ and PFC chips) -- ++ytti ___ 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] Certificate Update and Resource of CCIE
Suggested Cisco Press titles for written and lab exams v3.0 MPLS Fundamentals (Luc De Ghein, ISBN-10: 1-58705-197-4 ,ISBN-13: 978-1-58705-197-5) MPLS and Next-Generation Networks: Foundations for NGN and Enterprise Virtualization (Azhar Sayeed, Monique J. Morrow, ISBN-10: 1-58720-120-8, ISBN-13: 978-1-58720-120-2) Comparing, Designing, and Deploying VPNs(Mark Lewis, ISBN-10: 1-58705-179-6, ISBN-13: 978-1-58705-179-1) Selecting MPLS VPN Services (Chris Lewis, Steve Pickavance, ISBN-10: 1-58705-191-5, ISBN-13: 978-1-58705-191-3) Advanced MPLS Design and Implementation (Alwayn, ISBN# 158705020X) Building MPLS-Based Broadband Access VPNs (Reddy, ISBN# 1587051362) Definitive MPLS Network Designs (Guichard, Le Faucheur, Vasseur, ISBN# 1587051869) Layer 2 VPN Architectures (Luo, Pignataro, Chan, Bokotey, ISBN# 1587051680) MPLS and VPN Architectures (Pepelnjak, Guichard, ISBN# 1587050021) MPLS and VPN Architectures, Volume II (Pepelnjak, Guichard, Apcar, ISBN# 1587051125) Traffic Engineering with MPLS (Osborne, Simha, ISBN# 1587050315) BGP Design and Implementation (Bartell, Zhang, ISBN# 1587051095) Cisco Self-Study: Building Cisco Metro Optical Networks (METRO) (Hartmann, Warren, ISBN# 1587050706) Definitive MPLS Network Designs (Guichard, Le Faucheur, Vasseur, ISBN# 1587051869) End-to-End Qos Network Design: Quality of Service in LANs, WANs, and VPNs (Hattingh, Szigeti, ISBN# 1587051761) High Availability Network Fundamentals (Oggerino, ISBN# 1587130173) Interdomain Multicast Solutions Guide (Cisco Systems, Inc., ISBN# 1587050838) IP Quality of Service (Vegesna, ISBN# 1578701163) IS-IS Network Design Solutions (Martey, ISBN# 1578702208) Layer 2 VPN Architectures (Bokotey, Chan, Luo, Pignataro, ISBN# 1587051680) Metro Ethernet (Halabi, ISBN# 158705096X) MPLS Configuration on Cisco IOS Software (Lakshman, Lobo, ISBN# 1587051990) MPLS VPN Security (Behringer, Morrow, ISBN# 1587051834) QoS for IP/MPLS Networks (Santiago Alvarez) Next-Generation Network Services (Wood, ISBN# 1587051591) Traffic Engineering with MPLS (Osborne, Simha, ISBN# 1587050315) Troubleshooting Virtual Private Networks (VPN) (Lewis, ISBN# 1587051044) Cisco IOS XR Fundamentals (Mobeen Tahir, Mark Ghattas, Dawit Birhanu, Syed Natif Nawaz, ISBN-10: 1-58705-271-7, ISBN-13: 978-1-58705-271-2) Global IPv6 Strategies: From Business Analysis to Operational Planning (Patrick Grossetete, Ciprian P. Popoviciu, Fred Wettling, Fred Wettling) Deploying IPv6 Networks (Ciprian Popoviciu, Eric Levy-Abegnoli, Patrick Grossetete) Other Publications MPLS: Next Steps (Bruce S. Davie; Adrian Farrel) MPLS and Label Switching Networks (2nd Edition) (Uyless D. Black) Designing and Implementing IP/MPLS-Based Ethernet Layer 2 VPN Services: An Advanced Guide for VPLS and VLL (zhuo Xu) The Complete IS-IS Routing Protocol (Hannes Gredler and Walter Goralski) MPLS-Enabled Applications: Emerging Developments and New Technologies (Ina Minei; Julian Lucek) ATM Resource Library, Volumes 1, 2 And 3 (Black, Prentice Hall, ISBN# 0137937792) Implementing ADSL (Ginsburg, Addison Wesley, ISBN #0201657600) Routing In the Internet, Second Edition (Huitema, Prentice Hall, ISBN# 0130226475 ) TCP/IP Illustrated : Volumes 1, 2 and 3 (Stevens/Wright, Addison Wesley, ISBN# 0201633469) adam -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Fourpros it Sent: Tuesday, October 04, 2011 8:02 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Certificate Update and Resource of CCIE Hello Cisco -nsp group, My CCNP certificate is about to expire and want to renew it with CCIE SP written exam, can someone help me to find CCIE SP V3 (350-02) book? From where i can get this book or someone please mail me the soft copy if you have, it will be great help. Thank You Regards Four Pros ___ 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] Certificate Update and Resource of CCIE
Suggested Cisco Press titles for written and lab exams v3.0 [snip list] And a big stack of CRS docs. Because obviously you *can't* run a Service Provider without CRSen. Just saying... ;) Regards, Tim. ___ 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] Maximum traffic on Gigabit Ethernet
On 04/10/2011 07:38, Manaf Al Oqlah wrote: Normal Configuration: interface GigabitEthernet5/2 ip address x.x.x.x no ip redirects no ip proxy-arp media-type rj45 MTU is default 1500 The GE ports on a VS-S720-10G-3C supervisor are each provisioned with 9.6MB RX and 8.1MB TX buffers. This is quite a respectable amount of buffer space for a GE port, although if you have mls qos enabled, the default TX configuration is 1p3q4t, configured as: SP: 1.2MB Q3: 1.2MB Q2: 1.6MB Q1: 4.1MB This may not suit your traffic profile if everything is in a default priority class, as you'll end up putting everything into q1. reference paper: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper09186a0080131086.html Nick ___ 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] Certificate Update and Resource of CCIE
Speaking of CRSes :) have anyone seen the XR compiled for AIX somewhere on the net? adam -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Tim Franklin Sent: Tuesday, October 04, 2011 11:01 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Certificate Update and Resource of CCIE Suggested Cisco Press titles for written and lab exams v3.0 [snip list] And a big stack of CRS docs. Because obviously you *can't* run a Service Provider without CRSen. Just saying... ;) Regards, Tim. ___ 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] Maximum traffic on Gigabit Ethernet
Manaf, Your rate may be fine depending on packet size, for example 65 byte frames are less efficient in the hardware path and buffers than 64 bytes. You wouldn't expect more than about 760Mb/s in the best case with that size frame. With no congestion and one continuous input, 9000B frames can achieve about 990Mb/s. So, the question here: is this a problem or an observation? What rate do you expect? Has anything changed? Let's see if you have drops, also if you have CPU-switched flows, that will cause noticeable latency and will limit throughput. Sniffing the traffic may show retransmissions, which would mean drops occur somewhere in the path. The only thing you can do at this point, without changing the traffic flows (or can you?) is to look at drops and adjust buffer settings if desired. For dropping traffic, you can look at show int gi 5/2 and see if Total output drops is increasing. Also look at show queueing interface gi 5/2 and at the bottom you should see packets dropped on transmit and dropped on receive. See if these are incrementing. Finally, if you are getting software drops somewhere on input, you need to look at all other L3 interfaces that could possibly send traffic here (including this one) for input queue drops in software: sh int | inc is up|queue Interesting output would look like this: ... TenGigabitEthernet2/3 is up, line protocol is up (connected) Input queue: 3/2000/189/15 (size/max/drops/flushes); Total output drops:0 ... TenGigabitEthernet2/3 is up, line protocol is up (connected) Input queue: 18/2000/264/16 (size/max/drops/flushes); Total output drops: 0 Notice how drops and flushes have incremented here, indicating congestion to the software path (CPU punt). There are many reasons traffic might be punted, but let's see if that's the case first. Regards, John Gill cisco On 10/4/11 5:49 AM, Nick Hilliard wrote: On 04/10/2011 07:38, Manaf Al Oqlah wrote: Normal Configuration: interface GigabitEthernet5/2 ip address x.x.x.x no ip redirects no ip proxy-arp media-type rj45 MTU is default 1500 The GE ports on a VS-S720-10G-3C supervisor are each provisioned with 9.6MB RX and 8.1MB TX buffers. This is quite a respectable amount of buffer space for a GE port, although if you have mls qos enabled, the default TX configuration is 1p3q4t, configured as: SP: 1.2MB Q3: 1.2MB Q2: 1.6MB Q1: 4.1MB This may not suit your traffic profile if everything is in a default priority class, as you'll end up putting everything into q1. reference paper: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper09186a0080131086.html Nick ___ 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] Max IPv6 route entries for Cisco 4948E
Thanks for the info! Jose On 10/1/2011 6:07 PM, Tóth András wrote: Hi Jose, The 57000 is shared between IPv4 and IPv6. Best regards, Andras On Fri, Sep 30, 2011 at 4:39 PM, Loboloboti...@gmail.com wrote: Hey everyone. We're looking at the 4948E as a possible replacement for our aging 3550-12Ts and we were wondering if anyone has any information with regards to the maximum number of ipv6 routes that it will be able to hold. The only information I've found is that the device has 57,000 routes maximum but it doesn't say if that number also applies for ipv6. Based on other platforms, I'm thinking that maybe it will be half of that? Thanks for any info you guys can provide. Jose ___ 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] GBIC requires restart after link loss
On Tue, 4 Oct 2011, Martin T wrote: WS-C2960G-24TC-L[Gi0/22] - [Gi3/4]WS-C4506 SFP in WS-C2960G-24TC-L is a noname 1000BASE-LX10 transceiver working thanks to service unsupported-transceiver. GBIC in WS-C4506 is an Avago AFCT-5611Z 1000BASE-LX10. Linecard model in WS-C4506 is WS-X4306-GB. I had a situation where WS-C2960G-24TC-L reloaded, but link between WS-C2960G-24TC-L and WS-C4506 did not came up until I did shutdown and no shutdown to port Gi3/4 in WS-C4506. I have seen similar behaviour with GBIC transceivers on WS-X4306 linecard as well(in another WS-C4506) and for example in case there is a fibre cut between the switches, once the cable is repaired, sometimes one needs to make shutdown and no shutdow to GBIC port in order for line protocol to come up. Martin, check this bugid: CSCsq54639 Regards, John ___ 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] C7600 vs. ASR 9000
The 9K uses a crossbar fabric evolved from the 6500/7600 (not the same as the GSR - CRS evolved fabric) The port interface chips are the same. The NPU chip is the same as used in the ES cards. Primary difference is in the way the FIB is run on the 9K vs DFC on the 7600. Basically they 9K uses the NPU to do more than the 7600 so it is in a lot of ways more efficient but it is also more 'software' based (not necessarily a bad thing as it is more flexible). Being evolved from the 7600 should give users confidence that it is solid. That is a good thing. But it isn't so revolutionary that the 7600 is completely obsolete. After discounts the 9K still cost more but has a longer life expectancy. Mack -Original Message- From: Jason Lixfeld [mailto:ja...@lixfeld.ca] Sent: Monday, October 03, 2011 10:27 PM To: Mack McBride Cc: mti...@globaltransit.net; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] C7600 vs. ASR 9000 On 2011-10-03, at 11:37 PM, Mack McBride wrote: The 7600 and ASR9000 use a lot of similar hardware (Cisco didn't reinvent the wheel they just added rims). Where? The ASR line cards resemble the ES series on the 7600. Where? If one is using an ES port on a 7600, I'd assume one is likely using EVCs on said port. The ES ports on the 7600s do not support SPAN on a physical interface that is configured with EVCs. The ASR9k thankfully supports this extremely basic feature. The 7600 ES port's lack of SPAN on an EVC would lead me to believe that the ASIC controlling the ES is very different than the ASIC controlling the ASR linecards. ___ 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] C7600 vs. ASR 9000
7600 is 80G per slot ASR9K is 180G per slot (with both RP working) in future with new RP you can get more density per slot, so more salable. Sent from my BlackBerry device on the Rogers Wireless Network -Original Message- From: Mack McBride mack.mcbr...@viawest.com Sender: cisco-nsp-boun...@puck.nether.net Date: Tue, 4 Oct 2011 10:49:22 To: Jason Lixfeldja...@lixfeld.ca Cc: cisco-nsp@puck.nether.netcisco-nsp@puck.nether.net Subject: Re: [c-nsp] C7600 vs. ASR 9000 The 9K uses a crossbar fabric evolved from the 6500/7600 (not the same as the GSR - CRS evolved fabric) The port interface chips are the same. The NPU chip is the same as used in the ES cards. Primary difference is in the way the FIB is run on the 9K vs DFC on the 7600. Basically they 9K uses the NPU to do more than the 7600 so it is in a lot of ways more efficient but it is also more 'software' based (not necessarily a bad thing as it is more flexible). Being evolved from the 7600 should give users confidence that it is solid. That is a good thing. But it isn't so revolutionary that the 7600 is completely obsolete. After discounts the 9K still cost more but has a longer life expectancy. Mack -Original Message- From: Jason Lixfeld [mailto:ja...@lixfeld.ca] Sent: Monday, October 03, 2011 10:27 PM To: Mack McBride Cc: mti...@globaltransit.net; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] C7600 vs. ASR 9000 On 2011-10-03, at 11:37 PM, Mack McBride wrote: The 7600 and ASR9000 use a lot of similar hardware (Cisco didn't reinvent the wheel they just added rims). Where? The ASR line cards resemble the ES series on the 7600. Where? If one is using an ES port on a 7600, I'd assume one is likely using EVCs on said port. The ES ports on the 7600s do not support SPAN on a physical interface that is configured with EVCs. The ASR9k thankfully supports this extremely basic feature. The 7600 ES port's lack of SPAN on an EVC would lead me to believe that the ASIC controlling the ES is very different than the ASIC controlling the ASR linecards. ___ 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] C7600 vs. ASR 9000
It is an improvement but not much (with current gen RP). The primary improvement is using both fabric channels as active/active. Mack -Original Message- From: guru6...@gmail.com [mailto:guru6...@gmail.com] Sent: Tuesday, October 04, 2011 12:06 PM To: Mack McBride; cisco-nsp-boun...@puck.nether.net; Jason Lixfeld Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] C7600 vs. ASR 9000 7600 is 80G per slot ASR9K is 180G per slot (with both RP working) in future with new RP you can get more density per slot, so more salable. Sent from my BlackBerry device on the Rogers Wireless Network -Original Message- From: Mack McBride mack.mcbr...@viawest.com Sender: cisco-nsp-boun...@puck.nether.net Date: Tue, 4 Oct 2011 10:49:22 To: Jason Lixfeldja...@lixfeld.ca Cc: cisco-nsp@puck.nether.netcisco-nsp@puck.nether.net Subject: Re: [c-nsp] C7600 vs. ASR 9000 The 9K uses a crossbar fabric evolved from the 6500/7600 (not the same as the GSR - CRS evolved fabric) The port interface chips are the same. The NPU chip is the same as used in the ES cards. Primary difference is in the way the FIB is run on the 9K vs DFC on the 7600. Basically they 9K uses the NPU to do more than the 7600 so it is in a lot of ways more efficient but it is also more 'software' based (not necessarily a bad thing as it is more flexible). Being evolved from the 7600 should give users confidence that it is solid. That is a good thing. But it isn't so revolutionary that the 7600 is completely obsolete. After discounts the 9K still cost more but has a longer life expectancy. Mack -Original Message- From: Jason Lixfeld [mailto:ja...@lixfeld.ca] Sent: Monday, October 03, 2011 10:27 PM To: Mack McBride Cc: mti...@globaltransit.net; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] C7600 vs. ASR 9000 On 2011-10-03, at 11:37 PM, Mack McBride wrote: The 7600 and ASR9000 use a lot of similar hardware (Cisco didn't reinvent the wheel they just added rims). Where? The ASR line cards resemble the ES series on the 7600. Where? If one is using an ES port on a 7600, I'd assume one is likely using EVCs on said port. The ES ports on the 7600s do not support SPAN on a physical interface that is configured with EVCs. The ASR9k thankfully supports this extremely basic feature. The 7600 ES port's lack of SPAN on an EVC would lead me to believe that the ASIC controlling the ES is very different than the ASIC controlling the ASR linecards. ___ 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] GBIC requires restart after link loss
John, thank you for this bug ID! In case I'll have an opportunity to test those Avago AFCT-5611Z GBIC's further, I'll let you all know about the results. regards, martin 2011/10/4 John Kougoulos k...@intracom.gr: On Tue, 4 Oct 2011, Martin T wrote: WS-C2960G-24TC-L[Gi0/22] - [Gi3/4]WS-C4506 SFP in WS-C2960G-24TC-L is a noname 1000BASE-LX10 transceiver working thanks to service unsupported-transceiver. GBIC in WS-C4506 is an Avago AFCT-5611Z 1000BASE-LX10. Linecard model in WS-C4506 is WS-X4306-GB. I had a situation where WS-C2960G-24TC-L reloaded, but link between WS-C2960G-24TC-L and WS-C4506 did not came up until I did shutdown and no shutdown to port Gi3/4 in WS-C4506. I have seen similar behaviour with GBIC transceivers on WS-X4306 linecard as well(in another WS-C4506) and for example in case there is a fibre cut between the switches, once the cable is repaired, sometimes one needs to make shutdown and no shutdow to GBIC port in order for line protocol to come up. Martin, check this bugid: CSCsq54639 Regards, John ___ 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] 2800 series IOS versions.
Have a 2811 and a 2801. The 2801 runs this: c2801-ipbase-mz.124-1c.bin The 2811 runs: c2800nm-ipbase-mz.123-8.T5.bin What does the nm part of the version mean on the 2811? These are just routers we bought as we had some budget and have used them for lab stuff off and on. THanks. ___ 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] 2800 series IOS versions.
On Tue, Oct 04, 2011 at 19:00:37, Keith wrote: Subject: [c-nsp] 2800 series IOS versions. Have a 2811 and a 2801. The 2801 runs this: c2801-ipbase-mz.124-1c.bin The 2811 runs: c2800nm-ipbase-mz.123-8.T5.bin What does the nm part of the version mean on the 2811? Network module. And that's just the naming convention of the 2801 vs the rest of the 2800 line. -ryan ___ 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] 2800 series IOS versions.
On Tue, 4 Oct 2011, Jay Hennigan wrote: |-On 10/4/11 4:00 PM, Keith wrote: |- |- Have a 2811 and a 2801. |- |- The 2801 runs this: |- |- c2801-ipbase-mz.124-1c.bin |- |- The 2811 runs: |- |- c2800nm-ipbase-mz.123-8.T5.bin |- |- What does the nm part of the version mean on the 2811? |- |-The nm means that it supports network modules (the trapezoidal plug-ins |-for expansion). All of the 28xx series except the 2801 support these. |- |-I've never tried it but suspect that IOS between the two is not going to |-be interchangeable. Thanks Jay. Not looking to upgrade them at the moment, we just bang on them in our little lab room. Been looking over Cisco's website but could not find what the nm acutally stood for and what it meant. Thanks again. Keith. ___ 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] 2800 series IOS versions.
On 10/4/11 4:00 PM, Keith wrote: Have a 2811 and a 2801. The 2801 runs this: c2801-ipbase-mz.124-1c.bin The 2811 runs: c2800nm-ipbase-mz.123-8.T5.bin What does the nm part of the version mean on the 2811? The nm means that it supports network modules (the trapezoidal plug-ins for expansion). All of the 28xx series except the 2801 support these. I've never tried it but suspect that IOS between the two is not going to be interchangeable. -- 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] Nexus 7K - Multicast Question
Youre right, it works if the N7K is the DR is that segment. Now the mroute table shows what I was expecting: N7K12(config-if)# sh ip mroute IP Multicast Routing Table for VRF default (*, 232.0.0.0/8), uptime: 00:13:29, pim ip Incoming interface: Null, RPF nbr: 0.0.0.0 Outgoing interface list: (count: 0) (*, 239.1.2.3/32), uptime: 00:04:55, pim ip igmp Incoming interface: Ethernet1/27, RPF nbr: 10.12.2.2 Outgoing interface list: (count: 1) Ethernet1/27, uptime: 00:00:30, igmp, (RPF) (10.12.1.1/32, 239.1.2.3/32), uptime: 00:04:53, ip mrib pim Incoming interface: Ethernet1/27, RPF nbr: 10.12.2.2 Outgoing interface list: (count: 1) Ethernet1/27, uptime: 00:00:30, mrib, (RPF) N7K12(config-if)# Thank you for clarifying this difference between IOS and NXOS. Regards, Antonio Soares, CCIE #18473 (RS/SP) mailto:amsoa...@netcabo.pt amsoa...@netcabo.pt http://www.ccie18473.net http://www.ccie18473.net From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: domingo, 2 de Outubro de 2011 01:35 To: Antonio Soares; Phil Mayers; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] Nexus 7K - Multicast Question Interface e1/27 on n7k12 appears to be connected to g2/2 on the 6500. I rest my case. ;) Tim At 12:40 PM 10/1/2011, Antonio Soares contended: Hello Tim, Very simple setup: N7K11===CAT6500===N7K12 The RP is the CAT6500. The relevant configs bellow: CAT6500 (The RP): ip multicast-routing ! interface Loopback0 ip address 3.3.3.3 255.255.255.255 ip pim sparse-mode ! interface GigabitEthernet2/1 ip address 10.12.1.2 255.255.255.0 ip pim sparse-mode ! interface GigabitEthernet2/2 ip address 10.12.2.2 255.255.255.0 ip pim sparse-mode no ip mroute-cache ! ip pim rp-address 3.3.3.3 ! N7K11 (The source): feature ospf feature pim interface Ethernet1/27 ip address 10.12.1.1/24 ip router ospf 1 area 0.0.0.0 ip pim sparse-mode no shutdown ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4 ip pim ssm range 232.0.0.0/8 N7K12 (The destination) feature ospf feature pim interface Ethernet1/27 ip address 10.12.2.1/24 ip router ospf 1 area 0.0.0.0 ip pim sparse-mode ip igmp join-group 239.1.2.3 no shutdown ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4 ip pim ssm range 232.0.0.0/8 It works if the ip igmp join is moved to the loopback interface on the N7K12. Thanks. Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net http://www.ccie18473.net/ From: Tim Stevenson [ mailto:tstev...@cisco.com mailto:tstev...@cisco.com ] Sent: sábado, 1 de Outubro de 2011 16:06 To: Antonio Soares; Phil Mayers; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K - Multicast Question Hi Antonio, Can you please describe the exact topology here? Which interfaces you're using, what they're connected to, and where is the RP? One thing to be aware of with NXOS is that things only show up in sh ip mroute if the client protocol/process (eg IGMP in this case) has reason to feed them there. sh ip mroute is basically looking at the MRIB view of the world and nothing else. WRT the ip igmp join-group command, it does two things: one is it causes that interface to send IGMP joins for that group out that interface as if it were a host. The other is that, if the router is PIM DR on that interface, it feeds the *G the OIF to the MRIB. It's only at that point you'll see the entry in sh ip mroute. Otherwise, you'll only see it in the IGMP group membership table, ie, sh ip igmp group. My guess here is you're not DR on this interface, so I assume there's another router on the segment that IS the DR. If you check the mrouting there I suspect you'll see the *G entry joined to the RPT (driven by the IGMP joins sent on that segment from the router w/the join-group command). WRT the loopback working, what you're seeing is that this router is now the only means by which to reach that 'network segment' (ie, it's obviously going to be DR on its own loopback) so it will report the *G OIF to the MRIB and then you'll see the entry in sh ip mroute. Hope that helps, Tim At 03:24 AM 10/1/2011, Antonio Soares contended: This is lab environment, I'm just testing basic multicast features with nexus. The command reference says the following: When you enter this command, the traffic generated is handled by the device CPU, not the hardware. http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c ommand/reference/mcr_cmds_i.html#wp1230243 The ip igmp static-group was replaced by the command: ip igmp static-oif http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/multicast/c ommand/reference/mcr_cmds_i.html#wp1034808 When I have the igmp joing on the physical interface, the (*,G) entry is created then it disappears. But I see the (*,G) entry on the RP and I verified that the traffic is actually sent to the nexus. Thanks. Regards, Antonio Soares, CCIE #18473
Re: [c-nsp] Nexus 7K - Multicast Question
Hi Antonio, Just would like to be perfectly clear what's going on here: sh ip mroute on NXOS shows the MRIB. The MRIB is specifically for multicast *routing* information. In the original scenario you described, where the join-group is configured on the upstream (RPF) interface and the 7k is not the PIM DR, no *mrouting* is required or being performed - the 7k is behaving as a host, ie, sending IGMP joins to pull the traffic. So you'll only see that state in sh ip igmp groups, not sh ip mroute. Note that you should still see the multicast traffic arriving on the n7k RPF interface (thru sh int). In the case of the loopback, mrouting *is* required, ie, in order to multicast route the multicast from the RPF interface to the loopback - so IGMP feeds the group information and OIF to the MRIB to enable the mrouting. This is all just a side effect of the modular architecture of the NXOS software - IGMP, the MRIB, PIM, MSDP etc etc are all independent processes and each maintains its own state based on what it needs to know; and each only tells other process(es) about that state when its actually necessary. Hope that helps, Tim At 04:56 PM 10/4/2011, Antonio Soares contended: Youre right, it works if the N7K is the DR is that segment. Now the mroute table shows what I was expecting: N7K12(config-if)# sh ip mroute IP Multicast Routing Table for VRF default (*, 232.0.0.0/8), uptime: 00:13:29, pim ip Incoming interface: Null, RPF nbr: 0.0.0.0 Outgoing interface list: (count: 0) (*, 239.1.2.3/32), uptime: 00:04:55, pim ip igmp Incoming interface: Ethernet1/27, RPF nbr: 10.12.2.2 Outgoing interface list: (count: 1) Ethernet1/27, uptime: 00:00:30, igmp, (RPF) (10.12.1.1/32, 239.1.2.3/32), uptime: 00:04:53, ip mrib pim Incoming interface: Ethernet1/27, RPF nbr: 10.12.2.2 Outgoing interface list: (count: 1) Ethernet1/27, uptime: 00:00:30, mrib, (RPF) N7K12(config-if)# Thank you for clarifying this difference between IOS and NXOS. Regards, Antonio Soares, CCIE #18473 (RS/SP) mailto:amsoa...@netcabo.ptamsoa...@netcabo.pt http://www.ccie18473.net From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: domingo, 2 de Outubro de 2011 01:35 To: Antonio Soares; Phil Mayers; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] Nexus 7K - Multicast Question Interface e1/27 on n7k12 appears to be connected to g2/2 on the 6500. I rest my case. ;) Tim At 12:40 PM 10/1/2011, Antonio Soares contended: Hello Tim, Very simple setup: N7K11===CAT6500===N7K12 The RP is the CAT6500. The relevant configs bellow: CAT6500 (The RP): ip multicast-routing ! interface Loopback0 ip address 3.3.3.3 255.255.255.255 ip pim sparse-mode ! interface GigabitEthernet2/1 ip address 10.12.1.2 255.255.255.0 ip pim sparse-mode ! interface GigabitEthernet2/2 ip address 10.12.2.2 255.255.255.0 ip pim sparse-mode no ip mroute-cache ! ip pim rp-address 3.3.3.3 ! N7K11 (The source): feature ospf feature pim interface Ethernet1/27 ip address 10.12.1.1/24 ip router ospf 1 area 0.0.0.0 ip pim sparse-mode no shutdown ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4 ip pim ssm range 232.0.0.0/8 N7K12 (The destination) feature ospf feature pim interface Ethernet1/27 ip address 10.12.2.1/24 ip router ospf 1 area 0.0.0.0 ip pim sparse-mode ip igmp join-group 239.1.2.3 no shutdown ip pim rp-address 3.3.3.3 group-list 224.0.0.0/4 ip pim ssm range 232.0.0.0/8 It works if the ip igmp join is moved to the loopback interface on the N7K12. Thanks. Regards, Antonio Soares, CCIE #18473 (RS/SP) mailto:amsoa...@netcabo.ptamsoa...@netcabo.pt http://www.ccie18473.net From: Tim Stevenson [ mailto:tstev...@cisco.com] Sent: sábado, 1 de Outubro de 2011 16:06 To: Antonio Soares; Phil Mayers; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K - Multicast Question Hi Antonio, Can you please describe the exact topology here? Which interfaces you're using, what they're connected to, and where is the RP? One thing to be aware of with NXOS is that things only show up in sh ip mroute if the client protocol/process (eg IGMP in this case) has reason to feed them there. sh ip mroute is basically looking at the MRIB view of the world and nothing else. WRT the ip igmp join-group command, it does two things: one is it causes that interface to send IGMP joins for that group out that interface as if it were a host. The other is that, if the router is PIM DR on that interface, it feeds the *G the OIF to the MRIB. It's only at that point you'll see the entry in sh ip mroute. Otherwise, you'll only see it in the IGMP group membership table, ie, sh ip igmp group. My guess here is you're not DR on this interface, so I assume there's another router on the segment that IS the DR. If you check the mrouting there I suspect you'll see the *G entry joined to the RPT (driven by the IGMP joins sent on that segment from the router w/the join-group command). WRT the loopback working,
Re: [c-nsp] C7600 vs. ASR 9000
On Wednesday, October 05, 2011 02:12:53 AM Mack McBride wrote: It is an improvement but not much (with current gen RP). The primary improvement is using both fabric channels as active/active. On the software side, one thing I would say is that before you buy an ASR9000, make sure RPL does what you want. If it doesn't, that's not an excuse not to buy it either, but just one to ask your SE to get the features you want implemented. As I've said on this list before, the RPL model, while much improved from the route-map one, is less intuitive and not on par with what we've known from classic IOS. A number of features I requested are in the works, but your environment might be a little more different. Simple installations should not have an issue, as RPL covers pretty much everything for your basic routing policy. Mark. signature.asc Description: This is a digitally signed message part. ___ 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/
