Re: [c-nsp] mpls ping directly-connected?
Maybe Ethernet CFM at both ends? adam ___ 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] Bracket character in SNMP community string // IOS-XR
Hi guys, I've just tried to configured a SNMP community string in IOS-XR 4.1.2 without success I got the follow error: snmp-server community %test&) RP/0/0/CPU0:ex-RR1(config)#snmp-server community %test&) ^ % Invalid input detected at '^' marker. RP/0/0/CPU0:ex-RR1(config)#snmp-server community %test&)fasar ^ % Invalid input detected at '^' marker. RP/0/0/CPU0:ex-SISRR1(config)# This community string was working well in regular IOS. Maybe that is a bug, anyway have you experimented before that error? or maybe I'm wrong. Rgds. -- Omar E.P.T - Certified Networking Professionals make better Connections! ___ 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] QinQ question
> That's right, using QinQ the provider will tag all frames (customer's > various VLAN ID frames) using the same VLAN ID at all edges. Thanks Iftikhar - The provider also offers a service where we do the QinQ(we control all client(tails) vlans)would we configure the Agg port connecting to the provider as QinQ, or would this remain a trunk and we would have a QinQ port "behind" thisand then on customer site, we would need to install a switch with QinQ port facing CE WAN(And customer would tag vlans), and we would have a trunk allowing that vlan to providers NTU? Cheers. ___ 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] vlan limit hit...but havent?
thanks Robert - vtp pruning is not enabled (And switch was reloaded recently when IOS was updated) "sh vlan br | count act" reports 254 though: Number of lines which match regexp = 254 Any idea where the switch is getting the existing vlan number of 220? Number of existing VLANs : 220 Cheers. > From: rob...@custodiandc.com > To: cisconsp_l...@hotmail.com; cisco-nsp@puck.nether.net > Date: Sat, 17 Nov 2012 08:38:51 + > Subject: RE: [c-nsp] vlan limit hit...but havent? > > Hi, > > Just an idea, but have you tried "vtp pruning" in the config? If it is a bug > then maybe it's a result of not clearing VLANs which were previously present > but have been removed or re-numbered. Perhaps they are stuck in the VTP > DB/cache pending a reload or similar event. > > I know you are in transparent mode, but interestingly we have some 2960G > units which show pruning as 'enabled' even though VTP is off globally: > > #sh run | inc vtp > vtp mode off > > #sh vtp stat > VTP Version capable : 1 to 3 > VTP version running : 3 > VTP Domain Name : > VTP Pruning Mode: Enabled > VTP Traps Generation: Disabled > Device ID : x.x.x > > Feature VLAN: > -- > VTP Operating Mode: Off > Number of existing VLANs : 42 > Number of existing extended VLANs : 0 > Maximum VLANs supported locally : 255 > > Ours are running 15.0(2) > > Maybe you can also check: > > sh vlan br | count act > sh vlan | count enet > > Just out of curiosity, cheers! > > > Robert Williams > Backline / Operations Team > Custodian DataCentre > tel: +44 (0)1622 230382 > email: rob...@custodiandc.com > http://www.custodiandc.com/disclaimer.txt > > -Original Message- > From: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP_list > CiscoNSP_list > Sent: 17 November 2012 06:32 > To: cisco-nsp@puck.nether.net > Subject: [c-nsp] vlan limit hit...but havent? > > > > Cisco 2960G - 255 vlans allowed, currently have 220 configured, but cant > create any more? > > #sh vtp status > VTP Version capable : 1 to 3 > VTP version running : 1 > VTP Domain Name : > VTP Pruning Mode: Disabled > VTP Traps Generation: Disabled > Device ID : 0024.c3f0.9100 > Configuration last modified by 0.0.0.0 at 0-0-00 00:00:00 > > > Feature VLAN: > -- > VTP Operating Mode: Transparent > Maximum VLANs supported locally : 255 > Number of existing VLANs : 220 > > > Try and create new vlan: > > (config)#vlan 300 > (config-vlan)#name test > (config-vlan)#exi > Proposed configuration exceeds the limit of 255 VLANs that can be supported > on this platform. Reduce the number of VLANs proposed to be within this > limit.APPLY VLAN changes failed. > > Anyone seen this before? (I've upgraded IOS to latest, but still have the > issue?) > > > ___ > 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] vlan limit hit...but havent?
No, Its a C2960G-48TC-L (44Gig copper + 4 SFP) From: a.l.m.bu...@lboro.ac.uk To: cisconsp_l...@hotmail.com; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] vlan limit hit...but havent? Date: Sat, 17 Nov 2012 09:15:12 + 24 port with couple of SFP ports? I've got a sneaking suspicion that this is one of those cases where resources are reserved for physical ports alan ___ 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] vlan limit hit...but havent?
Thanks - Yes, all our trunk ports only allow certain vlans. > From: rob...@custodiandc.com > To: cisconsp_l...@hotmail.com; cisco-nsp@puck.nether.net > Date: Sat, 17 Nov 2012 09:44:44 + > Subject: RE: [c-nsp] vlan limit hit...but havent? > > Hi - also check all your trunk ports and make sure you are specifying only > active/valid VLANs individually, by using: > > switchport trunk allowed vlan 1,2,101,102,etc. > > If there are unrestricted trunk ports then again you may have resources tied > up for VLANs which have since been removed but it's just not showing them to > you. > > Cheers, > > > Robert Williams > Backline / Operations Team > Custodian DataCentre > tel: +44 (0)1622 230382 > email: rob...@custodiandc.com > http://www.custodiandc.com/disclaimer.txt > > -Original Message- > From: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Robert Williams > Sent: 17 November 2012 08:39 > To: 'CiscoNSP_list CiscoNSP_list'; cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] vlan limit hit...but havent? > > Hi, > > Just an idea, but have you tried "vtp pruning" in the config? If it is a bug > then maybe it's a result of not clearing VLANs which were previously present > but have been removed or re-numbered. Perhaps they are stuck in the VTP > DB/cache pending a reload or similar event. > > I know you are in transparent mode, but interestingly we have some 2960G > units which show pruning as 'enabled' even though VTP is off globally: > > #sh run | inc vtp > vtp mode off > > #sh vtp stat > VTP Version capable : 1 to 3 > VTP version running : 3 > VTP Domain Name : > VTP Pruning Mode: Enabled > VTP Traps Generation: Disabled > Device ID : x.x.x > > Feature VLAN: > -- > VTP Operating Mode: Off > Number of existing VLANs : 42 > Number of existing extended VLANs : 0 > Maximum VLANs supported locally : 255 > > Ours are running 15.0(2) > > Maybe you can also check: > > sh vlan br | count act > sh vlan | count enet > > Just out of curiosity, cheers! > > > Robert Williams > Backline / Operations Team > Custodian DataCentre > tel: +44 (0)1622 230382 > email: rob...@custodiandc.com > http://www.custodiandc.com/disclaimer.txt > > -Original Message- > From: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP_list > CiscoNSP_list > Sent: 17 November 2012 06:32 > To: cisco-nsp@puck.nether.net > Subject: [c-nsp] vlan limit hit...but havent? > > > > Cisco 2960G - 255 vlans allowed, currently have 220 configured, but cant > create any more? > > #sh vtp status > VTP Version capable : 1 to 3 > VTP version running : 1 > VTP Domain Name : > VTP Pruning Mode: Disabled > VTP Traps Generation: Disabled > Device ID : 0024.c3f0.9100 > Configuration last modified by 0.0.0.0 at 0-0-00 00:00:00 > > > Feature VLAN: > -- > VTP Operating Mode: Transparent > Maximum VLANs supported locally : 255 > Number of existing VLANs : 220 > > > Try and create new vlan: > > (config)#vlan 300 > (config-vlan)#name test > (config-vlan)#exi > Proposed configuration exceeds the limit of 255 VLANs that can be supported > on this platform. Reduce the number of VLANs proposed to be within this > limit.APPLY VLAN changes failed. > > Anyone seen this before? (I've upgraded IOS to latest, but still have the > issue?) > > > ___ > 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] 3750x Alternatives
On 11/19/2012 8:38 PM, Andrew Miehs wrote: > The OP seemed to be having an issue with bursty traffic, which is why I would push him away from the 37xx product line. Yes. I continue to be disappointed at 2960/3560/3570 buffer performance (so much to the extent that we're currently deploying another vendor at L2). We're still somewhat L3 bound to Cisco for the moment. Also not impressed with the IPv6 capabilities (and associated restrictions if you try) of the line. They have apparently run their course without a significant architecture/hardware change. Especially given no IPv6/VRF support on the lower-end Catalysts. 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/
Re: [c-nsp] 3750x Alternatives
On Tue, Nov 20, 2012 at 12:10 PM, Jeff Kell wrote: > If you seriously have 10G on the roadmap, 4500X looks sweet, you can get > it in a 16-port version, SFP / SFP+ you upgrade as you are ready. A > pair of them in a VSS deployment is going to be pretty steep however, > especially if you need smart layer-3 (Enterprise). > Thats what I thought too - but don't know how big a deployment is planned, and you loose a couple of ports for VSS and a couple of ports for your uplink. > Otherwise perhaps a 4507E+R with a pair of Sup7Es, you can pre-load > redundant power, Supervisors, and blades to fit the need now; if the VSS > pans out you just need another chassis (and whatever else you may want > "redundantly redundant"). > Not a big fan of the redundant supervisors (old habit from the 7500s) - and spanning tree would probably be adequate based on what I have understood. Or go with 3750E/X if their mac address tables meet your needs. You get > two 10G ports per switch, you can always uplink to a dumber/cheaper L2 > 10G switch. > The OP seemed to be having an issue with bursty traffic, which is why I would push him away from the 37xx product line. Andrew ___ 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] 3750x Alternatives
Now that the price list appears to be updated on CCX and netformx, it seems the 4500X is a pretty good choice. I didn't have the same experience with steep pricing on the ent version, at least not when compared to the LAN base -> IP base -> Ent upgrade pricing for the 4500E. -ryan -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jeff Kell Sent: Monday, November 19, 2012 8:10 PM To: Andrew Miehs Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] 3750x Alternatives If you seriously have 10G on the roadmap, 4500X looks sweet, you can get it in a 16-port version, SFP / SFP+ you upgrade as you are ready. A pair of them in a VSS deployment is going to be pretty steep however, especially if you need smart layer-3 (Enterprise). Otherwise perhaps a 4507E+R with a pair of Sup7Es, you can pre-load redundant power, Supervisors, and blades to fit the need now; if the VSS pans out you just need another chassis (and whatever else you may want "redundantly redundant"). Or go with 3750E/X if their mac address tables meet your needs. You get two 10G ports per switch, you can always uplink to a dumber/cheaper L2 10G switch. Jeff On 11/19/2012 8:00 PM, Andrew Miehs wrote: > On Tue, Nov 20, 2012 at 11:34 AM, CiscoNSP_list CiscoNSP_list < > cisconsp_l...@hotmail.com> wrote: > >> 2 x 4500-e with Sup7e + WS-X4748-RJ45-E + WS-X4612-SFP-E ? >> Or 2 x 4500x with similar ports as 4500-e Or 2 x Nexus 5548 >> >> Is there a big price difference between these? >> > Contact your Cisco reseller. He may be able to provide you with a > global price list so that you can see the relative price of all the > items. You will want some form of support on these boxes as well as > you NEED to be able to download updates. > > Otherwise you will have me here all day working out Cisco prices :) > > Based on my gut feeling - I would think that the best solution for you > would probably be a c4506 with a Sup7E. You could get your redundancy > by using spanning tree rather than port channels until VSS becomes > available. The 4500s are also quite a good layer 3 switch so you ever > require layer 3 functionality. (Extra licenses however). > > NOTE: I can of course not guarantee that Cisco will bring out VSS for > the 4500s or that it won't be an extra cost on the Sup7E - I can only > state what I have read. > ___ 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] 3750x Alternatives
If you seriously have 10G on the roadmap, 4500X looks sweet, you can get it in a 16-port version, SFP / SFP+ you upgrade as you are ready. A pair of them in a VSS deployment is going to be pretty steep however, especially if you need smart layer-3 (Enterprise). Otherwise perhaps a 4507E+R with a pair of Sup7Es, you can pre-load redundant power, Supervisors, and blades to fit the need now; if the VSS pans out you just need another chassis (and whatever else you may want "redundantly redundant"). Or go with 3750E/X if their mac address tables meet your needs. You get two 10G ports per switch, you can always uplink to a dumber/cheaper L2 10G switch. Jeff On 11/19/2012 8:00 PM, Andrew Miehs wrote: > On Tue, Nov 20, 2012 at 11:34 AM, CiscoNSP_list CiscoNSP_list < > cisconsp_l...@hotmail.com> wrote: > >> 2 x 4500-e with Sup7e + WS-X4748-RJ45-E + WS-X4612-SFP-E ? >> Or 2 x 4500x with similar ports as 4500-e >> Or 2 x Nexus 5548 >> >> Is there a big price difference between these? >> > Contact your Cisco reseller. He may be able to provide you with a global > price list so that you can see the relative price of all the items. You > will want some form of support on these boxes as well as you NEED to be > able to download updates. > > Otherwise you will have me here all day working out Cisco prices :) > > Based on my gut feeling - I would think that the best solution for you > would probably be a c4506 with a Sup7E. You could get your redundancy by > using spanning tree rather than port channels until VSS becomes > available. The 4500s are also quite a good layer 3 switch so you ever > require layer 3 functionality. (Extra licenses however). > > NOTE: I can of course not guarantee that Cisco will bring out VSS for the > 4500s or that it won't be an extra cost on the Sup7E - I can only state > what I have read. > ___ 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] 3750x Alternatives
On Tue, Nov 20, 2012 at 11:34 AM, CiscoNSP_list CiscoNSP_list < cisconsp_l...@hotmail.com> wrote: > > 2 x 4500-e with Sup7e + WS-X4748-RJ45-E + WS-X4612-SFP-E ? > Or 2 x 4500x with similar ports as 4500-e > Or 2 x Nexus 5548 > > Is there a big price difference between these? > Contact your Cisco reseller. He may be able to provide you with a global price list so that you can see the relative price of all the items. You will want some form of support on these boxes as well as you NEED to be able to download updates. Otherwise you will have me here all day working out Cisco prices :) Based on my gut feeling - I would think that the best solution for you would probably be a c4506 with a Sup7E. You could get your redundancy by using spanning tree rather than port channels until VSS becomes available. The 4500s are also quite a good layer 3 switch so you ever require layer 3 functionality. (Extra licenses however). NOTE: I can of course not guarantee that Cisco will bring out VSS for the 4500s or that it won't be an extra cost on the Sup7E - I can only state what I have read. Regards Andrew ___ 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] 3750x Alternatives
Thanks Andrew (And apologies for not replying inline, stupid Hotmail make it nigh on impossible) We currently only require 1G(SFP), but would like the flexibility to go to 10G when required...so, something like: 2 x 4500-e with Sup7e + WS-X4748-RJ45-E + WS-X4612-SFP-E ? Or 2 x 4500x with similar ports as 4500-e Or 2 x Nexus 5548 Is there a big price difference between these? Date: Tue, 20 Nov 2012 10:27:06 +1100 Subject: Re: [c-nsp] 3750x Alternatives From: and...@2sheds.de To: cisconsp_l...@hotmail.com CC: cisco-nsp@puck.nether.net On Tue, Nov 20, 2012 at 9:56 AM, CiscoNSP_list CiscoNSP_list wrote: Thanks Andrew - The Nexus do look nice...The 5010/5020 are EOL'd correct?(But still able to get smartnet on them?)Is there a significant price point difference between these and the 5548(P?) The Nexus 5548 should cost about the same as the 5020 - but you would need to check this and speak with your Cisco sales rep. If the Nexus are heinously expensive, I might look at the 4500's as you suggest.or perhaps the 4900's?(I do require 6+ SFP for fibre connections though) Do you require SFP+ or SFP? (10G or 1G)? The 4500 Sup7E and 4500X should support VSS by the start of next year (probably mid until it is stable). If you can wait that long with the "VSS" requirement you could probably buy a 4500 now, and VSS it later. HP also have their own version of VSS called IRF which you will find on their H3C range of switches - I believe it is now called HP Comware. This may also be an alternative. Andrew ___ 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] 3750x Alternatives
Just one clarification. The 5548UP is around the same price as the 5010 was. The 5520 is a 2u model which closer the 5596UP. Sent from handheld. On Nov 19, 2012, at 6:28 PM, "Andrew Miehs" wrote: > On Tue, Nov 20, 2012 at 9:56 AM, CiscoNSP_list CiscoNSP_list < > cisconsp_l...@hotmail.com> wrote: > >> Thanks Andrew - The Nexus do look nice...The 5010/5020 are EOL'd >> correct?(But still able to get smartnet on them?)Is there a significant >> price point difference between these and the 5548(P?) > > The Nexus 5548 should cost about the same as the 5020 - but you would need > to check this and speak with your Cisco sales rep. > > >> If the Nexus are heinously expensive, I might look at the 4500's as you >> suggest.or perhaps the 4900's?(I do require 6+ SFP for fibre >> connections though) > > Do you require SFP+ or SFP? (10G or 1G)? > > The 4500 Sup7E and 4500X should support VSS by the start of next year > (probably mid until it is stable). If you can wait that long with the "VSS" > requirement you could probably buy a 4500 now, and VSS it later. > > HP also have their own version of VSS called IRF which you will find on > their H3C range of switches - I believe it is now called HP Comware. This > may also be an alternative. > > Andrew > ___ > 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] 3750x Alternatives
On Tue, Nov 20, 2012 at 9:56 AM, CiscoNSP_list CiscoNSP_list < cisconsp_l...@hotmail.com> wrote: > Thanks Andrew - The Nexus do look nice...The 5010/5020 are EOL'd > correct?(But still able to get smartnet on them?)Is there a significant > price point difference between these and the 5548(P?) > The Nexus 5548 should cost about the same as the 5020 - but you would need to check this and speak with your Cisco sales rep. > If the Nexus are heinously expensive, I might look at the 4500's as you > suggest.or perhaps the 4900's?(I do require 6+ SFP for fibre > connections though) > Do you require SFP+ or SFP? (10G or 1G)? The 4500 Sup7E and 4500X should support VSS by the start of next year (probably mid until it is stable). If you can wait that long with the "VSS" requirement you could probably buy a 4500 now, and VSS it later. HP also have their own version of VSS called IRF which you will find on their H3C range of switches - I believe it is now called HP Comware. This may also be an alternative. Andrew ___ 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] IPAM for Service Provider - BRAS GGSN
Gustav, Thak you for the information. We are thinking in a commercial solution ( I will check the features of EfficentIP software) About the GGSN (wireless user), PPP is the method to provide the IP to the end user. I am not an expert on IPAM Tool, but according to Infoblox Guy, they can not manage the local ip pool defined on the Aggregator devices. According to Google the scan modes used by the IPAM tool are: icmp, snmp and arp scan. In my customer, the BRAS are Juniper and the GGSN are Huawei. I known that Cisco have some MIB to monitor the local ip pool, may be we can use the same method if we had the MIB information from the vendors. Any suggestion of experience about implement IPAM for Service Provider using PPP as the method for IP Address allocation? Best Regards Juan Carlos On Mon, Nov 19, 2012 at 2:30 PM, wrote: > Hello. > We went with PHPIpam in the end. > Only other competitor for us was Efficentips system. > > > Bästa hälsningar / Best regards, > > Gustav Uhlander > Communication & Infrastructure Engineer > > Steria AB > Kungsbron 13 > Box 169 > SE-101 23 Stockholm > Sweden > > Tel: +46 8 622 42 15 > Fax: +46 8 622 42 23 > Mobile: +46 70 962 71 03 > gustav.ulan...@steria.se > www.steria.se > > > > > From:cisco-pe > To:cisco-nsp > Date:2012-11-19 16:43 > Subject:[c-nsp] IPAM for Service Provider - BRAS GGSN > Sent by:cisco-nsp-boun...@puck.nether.net > -- > > > > Hi Guys, > > Is it possible to use IPAM to manage the local ip pool on BRAS and GGSN? > > At this moment for the wireline user (BRAS) we are using PPP and for the > wirelless user (GGSN) I need to confirm if we are using PPP, DHCP or GTP. > > What are the main considerations to use IPAM for Service Provider ? > > Any recommendation of IPAM vendors (dual stack) ? > > Best Regards > > Juan Carlos > > Enviado desde mi BlackBerry de Movistar > ___ > 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] 15.1SY & draft-rosen MVPN
The command should be under the IPv4 address family... Router(config)#vrf definition test Router(config-vrf)#address-family ipv4 Router(config-vrf-af)#md Router(config-vrf-af)#mdt ? dataMDT data trees default The default group log-reuse Event logging for data MDT reuse overlay MDT Overlay Protocol preference MDT preference (default pim mldp) Arie -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Phil Mayers Sent: Monday, November 19, 2012 14:50 To: cisco-nsp@puck.nether.net Subject: [c-nsp] 15.1SY & draft-rosen MVPN It's late and I'm tired, so maybe I'm missing something, but after a reload into 15.1SY, our testing sup270 failed to take the "mdt" commands under VRFs: mdt default 239.254.1.2 ^ % Invalid input detected at '^' marker. The VRFs are all "new" format "vrf definition" if that matters, but an old-style "ip vrf" object doesn't take the command either. There's a bunch of stuff in the config guide about mLDP-based MVPNs and some new "l3vpn encap" command stuff: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.1SY/config_guide/sup720/ipv4_multicast_vpn.html Any ideas anyone? Bug? Cheers, Phil ___ 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] SRX110 and Cisco2970 MSTP issue
Hi, Does anyone has any experience of running MSTP between SRX110 and Cisco (particularly Cisco2970)? I have deployed a pair of SRX110 connected to a pair of Cisco2970, in a way that both the SRX100s are connected to both the Cisco2970 switches through trunk links. If I try to set the priority on one of the SRX110 to become root bridge, MSTP seems to be converged but there are huge packet losses in the network. I removed the priority and one of the cisco2970 became root and then everything seems to be fine. No packet loss after that. Just wondering why there is a problem if MSTP is converged and all devices seem to be agreeing on root bridge. Any experience or thoughts, please share. Regards, *Ali Sumsam CCIE* *Network Engineer - Level 3* eintellego Pty Ltd a...@eintellego.net ; www.eintellego.net Phone: 1300 753 383 ; Fax: (+612) 8572 9954 Cell +61 (0)410 603 531 facebook.com/eintellego PO Box 7726, Baulkham Hills, NSW 1755 Australia The Experts Who The Experts Call Juniper - Cisco – Brocade - IBM ___ 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] 3750x Alternatives
Thanks Andrew - The Nexus do look nice...The 5010/5020 are EOL'd correct?(But still able to get smartnet on them?)Is there a significant price point difference between these and the 5548(P?) If the Nexus are heinously expensive, I might look at the 4500's as you suggest.or perhaps the 4900's?(I do require 6+ SFP for fibre connections though) Cheers. Date: Mon, 19 Nov 2012 18:57:14 +1100 Subject: Re: [c-nsp] 3750x Alternatives From: and...@2sheds.de To: cisconsp_l...@hotmail.com CC: cisco-nsp@puck.nether.net On Mon, Nov 19, 2012 at 5:40 PM, CiscoNSP_list CiscoNSP_list wrote: We currently use 3750x stack to terminate pairs of 2960S(TOR's) - Our traffic is quite bursty, and we are getting hit with the small buffers (output drops)...any suggestions on alternative platforms? (We only do L2 on the current switches) 6503's w/ VSS? 4500x w/ VSS? Nexus w/ Vpc? If you only want to do layer 2, you could also look at a pair of Nexus 5Ks and run VPC - or look at other vendors. Do you really need two chassis/ VSS? 4500s don't have VSS yet, so you could possibly get away with a 4500 - possible a second 4500 as a cold spare. Andrew ___ 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] 15.1SY & draft-rosen MVPN
It's late and I'm tired, so maybe I'm missing something, but after a reload into 15.1SY, our testing sup270 failed to take the "mdt" commands under VRFs: mdt default 239.254.1.2 ^ % Invalid input detected at '^' marker. The VRFs are all "new" format "vrf definition" if that matters, but an old-style "ip vrf" object doesn't take the command either. There's a bunch of stuff in the config guide about mLDP-based MVPNs and some new "l3vpn encap" command stuff: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.1SY/config_guide/sup720/ipv4_multicast_vpn.html Any ideas anyone? Bug? Cheers, Phil ___ 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] Ingress QoS on ASR 1000 LACP bundles
Hi, Yes, ASR does not support ingress/egress QOS on portchan subints - It will be supported (apparently) in 15.3S/3.8.0S (Which I believe will be available by EOY?) - there is a work-around though. 1. Upgrade to 15.2(4)S1, and issue "port-channel load-balancing vlan-manual", and you will then be able to assign ingress+egress policy-maps to portchan subints Below is lab ASR1006 running 15.2(4)S1 with port-channel load-balancing vlan-manual enabled: Router#sh policy-map interface Port-channel1.90 Service-policy input: input_policy Class-map: class-default (match-any) 125 packets, 10321 bytes 5 minute offered rate bps, drop rate bps Service-policy output: ERA-LEGAL-4Mb Class-map: class-default (match-any) 1938500 packets, 198784733 bytes 5 minute offered rate bps, drop rate bps interface Port-channel1.90 description NETFLOW encapsulation dot1Q 90 ip address 10.1.1.1 255.255.255.0 no ip proxy-arp ip flow ingress service-policy input input_policy service-policy output ERA-LEGAL-4Mb HTH. > From: mdikk...@postmedia.com > To: cisco-nsp@puck.nether.net > Date: Mon, 19 Nov 2012 14:38:43 -0600 > Subject: Re: [c-nsp] Ingress QoS on ASR 1000 LACP bundles > > I cannot assign a service-policy input statement to an LACP port-channel > interface on an ASR 1002 router. The console gives an error saying it's not > possible. I have found documentation from Cisco stating that it's not > supported under any current software. Putting the service policy onto the > physical members has no effect. > > > On Mon, Nov 19, 2012 at 10:18:46AM -0600, Dikkema, Michael (Business > Technology) wrote: > > Is there any way to get ingress QoS working on LACP on ASR 1000 series? > > What do you mean with "ingress QoS" exactly? > > I'd be interested to learn about any QoS "surprises" on ASR1k. > > > ___ > 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] DHCP option 26
Yes , there are other methods to do so , but I have an old setup and i need to do it this way if applicable > CC: cisco-nsp@puck.nether.net > From: and...@2sheds.de > Subject: Re: [c-nsp] DHCP option 26 > Date: Mon, 19 Nov 2012 21:22:05 +1100 > To: gunner_...@live.com > > > > Sent from a mobile device > > On 19/11/2012, at 20:36, M K wrote: > > Hi all I have configured the belowR1#sh run | sec ip dhcpip dhcp pool TEST > > network 192.1.12.0 255.255.255.0 domain-name cisco.com option 26 hex 0578 > > Am trying to send the mtu interface vlaue through the DHCP offer but it's > > not happening578 hex = 1400 > > Can this actually work? I would imagine that this is fairly late in the > entire process on an interface to set mtu. ___ 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] mpls ping directly-connected?
Hi, On Mon, Nov 19, 2012 at 03:55:23PM -0500, Tim Durack wrote: > Thanks, that gives me something to look at. (C6K running 12.2(33)SXI6.) Has "static labels" but not "static crossconnect", which you might need to get out of the tunnel again. Well, maybe not, you could just point your static label at something that is valid at the neighbour router just at the time when you test the link... (I'm curious to hear how you get this solved in the end. Something new to learn :) ). > Have you looked at 15.1SY yet? Looks half-way decent. Even got ssh keys > finally. Read most of the release notes, looks very promising. Sitting in the flash of one of the lab routers already, but not yet booted - "no time" :-( 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 pgp8QnNA6HR3k.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/
Re: [c-nsp] mpls ping directly-connected?
Thanks, that gives me something to look at. (C6K running 12.2(33)SXI6.) Have you looked at 15.1SY yet? Looks half-way decent. Even got ssh keys finally. On Mon, Nov 19, 2012 at 3:30 PM, Gert Doering wrote: > Hi, > > On Mon, Nov 19, 2012 at 03:21:39PM -0500, Tim Durack wrote: > > Any non-invasive bright ideas? > > Well, there's this thing with static MPLS labels... I'm not sure how > I'd use it to test a single link (without building a full measurement > infrastructure), but it should be doable... potentially combined with > "ping mpls". > > Unfortunately, turning on static MPLS labels needs a reboot (reserving > a numeric range) *and* half of what you might want is not in 12.2SX* > (no rant today). > > 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-35655025 > g...@net.informatik.tu-muenchen.de > -- 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] Ingress QoS on ASR 1000 LACP bundles
I cannot assign a service-policy input statement to an LACP port-channel interface on an ASR 1002 router. The console gives an error saying it's not possible. I have found documentation from Cisco stating that it's not supported under any current software. Putting the service policy onto the physical members has no effect. On Mon, Nov 19, 2012 at 10:18:46AM -0600, Dikkema, Michael (Business Technology) wrote: > Is there any way to get ingress QoS working on LACP on ASR 1000 series? What do you mean with "ingress QoS" exactly? I'd be interested to learn about any QoS "surprises" on ASR1k. ___ 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] mpls ping directly-connected?
Hi, On Mon, Nov 19, 2012 at 03:21:39PM -0500, Tim Durack wrote: > Any non-invasive bright ideas? Well, there's this thing with static MPLS labels... I'm not sure how I'd use it to test a single link (without building a full measurement infrastructure), but it should be doable... potentially combined with "ping mpls". Unfortunately, turning on static MPLS labels needs a reboot (reserving a numeric range) *and* half of what you might want is not in 12.2SX* (no rant today). 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 pgpnCdguOQTgu.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/
[c-nsp] mpls ping directly-connected?
I'm testing a new Ethernet circuit, and need to verify that MPLS labelled frames are being forwarded correctly. Unfortunately I can't think of a simple test between the two directly connected routers which doesn't involve production traffic. (The current link is costed-out from an OSPF perspective.) Any non-invasive bright ideas? -- 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] IPAM for Service Provider - BRAS GGSN
Hello. We went with PHPIpam in the end. Only other competitor for us was Efficentips system. Bästa hälsningar / Best regards, Gustav Uhlander Communication & Infrastructure Engineer Steria AB Kungsbron 13 Box 169 SE-101 23 Stockholm Sweden Tel: +46 8 622 42 15 Fax: +46 8 622 42 23 Mobile: +46 70 962 71 03 gustav.ulan...@steria.se www.steria.se From: cisco-pe To: cisco-nsp Date: 2012-11-19 16:43 Subject:[c-nsp] IPAM for Service Provider - BRAS GGSN Sent by:cisco-nsp-boun...@puck.nether.net Hi Guys, Is it possible to use IPAM to manage the local ip pool on BRAS and GGSN? At this moment for the wireline user (BRAS) we are using PPP and for the wirelless user (GGSN) I need to confirm if we are using PPP, DHCP or GTP. What are the main considerations to use IPAM for Service Provider ? Any recommendation of IPAM vendors (dual stack) ? Best Regards Juan Carlos Enviado desde mi BlackBerry de Movistar ___ 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] Ingress QoS on ASR 1000 LACP bundles
On Mon, Nov 19, 2012 at 10:18:46AM -0600, Dikkema, Michael (Business Technology) wrote: > Is there any way to get ingress QoS working on LACP on ASR 1000 series? What do you mean with "ingress QoS" exactly? I'd be interested to learn about any QoS "surprises" on ASR1k. Best regards, Daniel -- CLUE-RIPE -- Jabber: d...@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 ___ 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] Ingress QoS on ASR 1000 LACP bundles
Is there any way to get ingress QoS working on LACP on ASR 1000 series? Either by physical interfaces or on the bundle. Is there any logical workaround for this besides moving from the bundle to the next largest interface? 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] Nexus 7K NX-OS Upgrade
I Was upgrading to 6.1(1) from a Software Standpoint, which required a requisite 6.1(1) EPLD Image Upgrade. EPLD Image upgrade took a significant amount of time to upgrade, which is standard. Neil -Original Message- From: Antonio Soares [mailto:amsoa...@netcabo.pt] Sent: Monday, November 19, 2012 10:50 AM To: 'Neil Barnett'; 'Tim Stevenson'; 'Dirk Woellhaf' Cc: 'Charles Spurgeon'; 'cisco-nsp' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade What upgrade did you make ? In my case it was from 5.2.3a to 5.2.7. The 5.2.3 EPLD was already installed. Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Neil Barnett [mailto:interarchet...@gmail.com] Sent: segunda-feira, 19 de Novembro de 2012 14:22 To: 'Antonio Soares'; 'Tim Stevenson'; 'Dirk Woellhaf' Cc: 'Charles Spurgeon'; 'cisco-nsp' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade I had an odd situation where I did a software upgrade on one box successfully. On the 2nd box the VLAN Configurations were arbitrarily missing, which was frustrating As we thought immediately that the vpc was down for other reasons. Not sure if this had anything to do with the m1, (I did do an EPLD Upgrade as well) Psion -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Antonio Soares Sent: Saturday, November 17, 2012 12:29 PM To: 'Tim Stevenson'; 'Dirk Woellhaf' Cc: 'Charles Spurgeon'; 'cisco-nsp' Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Another long night... The upgrade of one Nexus was completely clean, the second one was a nightmare. One M1-32XP card remained in the state "powered-up" forever... The reload didn't make it work, neither the re-seat or even the NX-OS downgrade... Had to open a P1 TAC case and then the engineer said it was a faulty card. Got the replacement but had to delay the installation 48 hours. Anyone has have bad experiences with this M1 type of cards card lately ? It's the second one that gets faulty in less than a year. It seems the MTBF is inversely proportional to the price :( Thanks. Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: quinta-feira, 8 de Novembro de 2012 18:21 To: Antonio Soares; 'Dirk Woellhaf' Cc: 'cisco-nsp'; 'Charles Spurgeon' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade At 09:36 AM 11/8/2012, Antonio Soares mused: >Thanks Tim, I will follow that procedure, it's the one that makes >perfect sense. > >The documentation should be more clear about this kind of situations, >don't you think ? > >There are important things that are omitted between steps 10 and 11: You mean specific to also upgrading the DRAM? This particular procedure is not intended to cover also upgrading DRAM at the same time, that's not really something we assume you're doing every time you upgrade. BTW, Sukumar does make a good point about the install script - it will potentially make some changes to the config based on updated features, CoPP being a prominent example. An alternative in your case would be to just power off, upgrade DRAM, reboot, and then install all. Clearly that involves 2 reboots with a single sup. Tim >http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/upgrad >e/gui >de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide >__Rel >ease_5.x_chapter_00.html#task_304731 > > > >Regards, > >Antonio Soares, CCIE #18473 (R&S/SP) >amsoa...@netcabo.pt >http://www.ccie18473.net > > > >-Original Message- >From: Tim Stevenson [mailto:tstev...@cisco.com] >Sent: quinta-feira, 8 de Novembro de 2012 15:51 >To: Antonio Soares; 'Dirk Woellhaf' >Cc: 'cisco-nsp'; 'Charles Spurgeon' >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade > >At 07:18 AM 11/8/2012, Antonio Soares mused: > >I just have one SUP... You are talking about dual supervisors setup, > >right >? > > >Ah. In that case, clearly, the box is going to go offline when you upgrade. >You might want to consider buying another sup. > >IMO, there is no huge benefit in using the install all script in a >single sup system - in the end, all it will do for you is a little >sanity checking and maybe save you from fat fingering a bootstring. > >In your situation, I would copy over the new images you want; manually >change the bootstrings & save to startup; power off the box, yank the >sup & add the DRAM; and then power it all back on. > >Tim > > > > >Regards, > > > >Antonio Soares, CCIE #18473 (R&S/SP) > >amsoa...@netcabo.pt > >http://www.ccie18473.net > > > > > > > >-Original Message- > >From: Dirk Woellhaf [mailto:dirk.woell...@gmail.com] > >Sent: quinta-feira, 8 de Novembro de 2012 14:10 > >To: Antonio Soares > >Cc: Charles Spurgeon; cisco-nsp > >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade > > > >Hi Antonio, > > > >You should be able to do the memory-upgrade without rebooting the
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Hello, We had a similar sitatuation. We have two n7k in a vpc domain with vdc feature as well. The upgrade of the first switch was without any issue, but we upgraded the second one too, and the M1 card failed to boot, this caused that VDC couldn't start... After removing the failed card the vdc was able to boot up. And we received a new line card from Cisco within four hours (it depends on support contract). -A. On Sat, 17 Nov 2012, Antonio Soares wrote: Another long night... The upgrade of one Nexus was completely clean, the second one was a nightmare. One M1-32XP card remained in the state "powered-up" forever... The reload didn't make it work, neither the re-seat or even the NX-OS downgrade... Had to open a P1 TAC case and then the engineer said it was a faulty card. Got the replacement but had to delay the installation 48 hours. Anyone has have bad experiences with this M1 type of cards card lately ? It's the second one that gets faulty in less than a year. It seems the MTBF is inversely proportional to the price :( Thanks. Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: quinta-feira, 8 de Novembro de 2012 18:21 To: Antonio Soares; 'Dirk Woellhaf' Cc: 'cisco-nsp'; 'Charles Spurgeon' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade At 09:36 AM 11/8/2012, Antonio Soares mused: Thanks Tim, I will follow that procedure, it's the one that makes perfect sense. The documentation should be more clear about this kind of situations, don't you think ? There are important things that are omitted between steps 10 and 11: You mean specific to also upgrading the DRAM? This particular procedure is not intended to cover also upgrading DRAM at the same time, that's not really something we assume you're doing every time you upgrade. BTW, Sukumar does make a good point about the install script - it will potentially make some changes to the config based on updated features, CoPP being a prominent example. An alternative in your case would be to just power off, upgrade DRAM, reboot, and then install all. Clearly that involves 2 reboots with a single sup. Tim http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/upgrad e/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide __Rel ease_5.x_chapter_00.html#task_304731 Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: quinta-feira, 8 de Novembro de 2012 15:51 To: Antonio Soares; 'Dirk Woellhaf' Cc: 'cisco-nsp'; 'Charles Spurgeon' Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade At 07:18 AM 11/8/2012, Antonio Soares mused: I just have one SUP... You are talking about dual supervisors setup, right ? Ah. In that case, clearly, the box is going to go offline when you upgrade. You might want to consider buying another sup. IMO, there is no huge benefit in using the install all script in a single sup system - in the end, all it will do for you is a little sanity checking and maybe save you from fat fingering a bootstring. In your situation, I would copy over the new images you want; manually change the bootstrings & save to startup; power off the box, yank the sup & add the DRAM; and then power it all back on. Tim Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Dirk Woellhaf [mailto:dirk.woell...@gmail.com] Sent: quinta-feira, 8 de Novembro de 2012 14:10 To: Antonio Soares Cc: Charles Spurgeon; cisco-nsp Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Hi Antonio, You should be able to do the memory-upgrade without rebooting the box. I've never done it on my I own but I know a few which did without any problem. I believe they first upgraded the memory and then did the update! Dirk Sent from my iPhone On 08.11.2012, at 13:42, Antonio Soares wrote: Thanks, I don't know if you noticed but somewhere in the thread the bug was mentioned and it is resolved in 5.1.5 and later. Bug CSCtn61286 - Boot variables are not set up correctly on Sup-2 after ISSU So in my case, it should not give me problems (5.2.3a to 5.2.7). But since I also need to upgrade the SUP1 RAM from 4G to 8G, I have no other option than doing the traditional upgrade. It's the only way to just send the box down 1 time: - update the boot variables - power off and upgrade the RAM - power on The install all script has another limitation: it won't let us to reboot when we chose to do it. This is what happened to me last time: + Switch will be reloaded for disruptive upgrade. Do you want to continue with the installation (y/n)? y Install is in progress, please wait. (..) A few minutes later: Finishing the upgrade, switch will reboot in 10 seconds. + I don't see how to upgrade the RAM and
Re: [c-nsp] Nexus 7K NX-OS Upgrade
What upgrade did you make ? In my case it was from 5.2.3a to 5.2.7. The 5.2.3 EPLD was already installed. Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Neil Barnett [mailto:interarchet...@gmail.com] Sent: segunda-feira, 19 de Novembro de 2012 14:22 To: 'Antonio Soares'; 'Tim Stevenson'; 'Dirk Woellhaf' Cc: 'Charles Spurgeon'; 'cisco-nsp' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade I had an odd situation where I did a software upgrade on one box successfully. On the 2nd box the VLAN Configurations were arbitrarily missing, which was frustrating As we thought immediately that the vpc was down for other reasons. Not sure if this had anything to do with the m1, (I did do an EPLD Upgrade as well) Psion -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Antonio Soares Sent: Saturday, November 17, 2012 12:29 PM To: 'Tim Stevenson'; 'Dirk Woellhaf' Cc: 'Charles Spurgeon'; 'cisco-nsp' Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Another long night... The upgrade of one Nexus was completely clean, the second one was a nightmare. One M1-32XP card remained in the state "powered-up" forever... The reload didn't make it work, neither the re-seat or even the NX-OS downgrade... Had to open a P1 TAC case and then the engineer said it was a faulty card. Got the replacement but had to delay the installation 48 hours. Anyone has have bad experiences with this M1 type of cards card lately ? It's the second one that gets faulty in less than a year. It seems the MTBF is inversely proportional to the price :( Thanks. Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: quinta-feira, 8 de Novembro de 2012 18:21 To: Antonio Soares; 'Dirk Woellhaf' Cc: 'cisco-nsp'; 'Charles Spurgeon' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade At 09:36 AM 11/8/2012, Antonio Soares mused: >Thanks Tim, I will follow that procedure, it's the one that makes >perfect sense. > >The documentation should be more clear about this kind of situations, >don't you think ? > >There are important things that are omitted between steps 10 and 11: You mean specific to also upgrading the DRAM? This particular procedure is not intended to cover also upgrading DRAM at the same time, that's not really something we assume you're doing every time you upgrade. BTW, Sukumar does make a good point about the install script - it will potentially make some changes to the config based on updated features, CoPP being a prominent example. An alternative in your case would be to just power off, upgrade DRAM, reboot, and then install all. Clearly that involves 2 reboots with a single sup. Tim >http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/upgrad >e/gui >de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide >__Rel >ease_5.x_chapter_00.html#task_304731 > > > >Regards, > >Antonio Soares, CCIE #18473 (R&S/SP) >amsoa...@netcabo.pt >http://www.ccie18473.net > > > >-Original Message- >From: Tim Stevenson [mailto:tstev...@cisco.com] >Sent: quinta-feira, 8 de Novembro de 2012 15:51 >To: Antonio Soares; 'Dirk Woellhaf' >Cc: 'cisco-nsp'; 'Charles Spurgeon' >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade > >At 07:18 AM 11/8/2012, Antonio Soares mused: > >I just have one SUP... You are talking about dual supervisors setup, > >right >? > > >Ah. In that case, clearly, the box is going to go offline when you upgrade. >You might want to consider buying another sup. > >IMO, there is no huge benefit in using the install all script in a >single sup system - in the end, all it will do for you is a little >sanity checking and maybe save you from fat fingering a bootstring. > >In your situation, I would copy over the new images you want; manually >change the bootstrings & save to startup; power off the box, yank the >sup & add the DRAM; and then power it all back on. > >Tim > > > > >Regards, > > > >Antonio Soares, CCIE #18473 (R&S/SP) > >amsoa...@netcabo.pt > >http://www.ccie18473.net > > > > > > > >-Original Message- > >From: Dirk Woellhaf [mailto:dirk.woell...@gmail.com] > >Sent: quinta-feira, 8 de Novembro de 2012 14:10 > >To: Antonio Soares > >Cc: Charles Spurgeon; cisco-nsp > >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade > > > >Hi Antonio, > > > >You should be able to do the memory-upgrade without rebooting the box. > >I've never done it on my I own but I know a few which did without any > >problem. I believe they first upgraded the memory and then did the update! > > > >Dirk > > > >Sent from my iPhone > > > >On 08.11.2012, at 13:42, Antonio Soares wrote: > > > > > Thanks, I don't know if you noticed but somewhere in the thread > > > the bug was mentioned and it is resolved in 5.1.5 and later. > > > > > > Bug CSCtn61286 - Boot variables are not set up c
[c-nsp] IPAM for Service Provider - BRAS GGSN
Hi Guys, Is it possible to use IPAM to manage the local ip pool on BRAS and GGSN? At this moment for the wireline user (BRAS) we are using PPP and for the wirelless user (GGSN) I need to confirm if we are using PPP, DHCP or GTP. What are the main considerations to use IPAM for Service Provider ? Any recommendation of IPAM vendors (dual stack) ? Best Regards Juan Carlos Enviado desde mi BlackBerry de Movistar ___ 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 NX-OS Upgrade
I had an odd situation where I did a software upgrade on one box successfully. On the 2nd box the VLAN Configurations were arbitrarily missing, which was frustrating As we thought immediately that the vpc was down for other reasons. Not sure if this had anything to do with the m1, (I did do an EPLD Upgrade as well) Psion -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Antonio Soares Sent: Saturday, November 17, 2012 12:29 PM To: 'Tim Stevenson'; 'Dirk Woellhaf' Cc: 'Charles Spurgeon'; 'cisco-nsp' Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Another long night... The upgrade of one Nexus was completely clean, the second one was a nightmare. One M1-32XP card remained in the state "powered-up" forever... The reload didn't make it work, neither the re-seat or even the NX-OS downgrade... Had to open a P1 TAC case and then the engineer said it was a faulty card. Got the replacement but had to delay the installation 48 hours. Anyone has have bad experiences with this M1 type of cards card lately ? It's the second one that gets faulty in less than a year. It seems the MTBF is inversely proportional to the price :( Thanks. Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Tim Stevenson [mailto:tstev...@cisco.com] Sent: quinta-feira, 8 de Novembro de 2012 18:21 To: Antonio Soares; 'Dirk Woellhaf' Cc: 'cisco-nsp'; 'Charles Spurgeon' Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade At 09:36 AM 11/8/2012, Antonio Soares mused: >Thanks Tim, I will follow that procedure, it's the one that makes >perfect sense. > >The documentation should be more clear about this kind of situations, >don't you think ? > >There are important things that are omitted between steps 10 and 11: You mean specific to also upgrading the DRAM? This particular procedure is not intended to cover also upgrading DRAM at the same time, that's not really something we assume you're doing every time you upgrade. BTW, Sukumar does make a good point about the install script - it will potentially make some changes to the config based on updated features, CoPP being a prominent example. An alternative in your case would be to just power off, upgrade DRAM, reboot, and then install all. Clearly that involves 2 reboots with a single sup. Tim >http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/upgrad >e/gui >de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide >__Rel >ease_5.x_chapter_00.html#task_304731 > > > >Regards, > >Antonio Soares, CCIE #18473 (R&S/SP) >amsoa...@netcabo.pt >http://www.ccie18473.net > > > >-Original Message- >From: Tim Stevenson [mailto:tstev...@cisco.com] >Sent: quinta-feira, 8 de Novembro de 2012 15:51 >To: Antonio Soares; 'Dirk Woellhaf' >Cc: 'cisco-nsp'; 'Charles Spurgeon' >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade > >At 07:18 AM 11/8/2012, Antonio Soares mused: > >I just have one SUP... You are talking about dual supervisors setup, > >right >? > > >Ah. In that case, clearly, the box is going to go offline when you upgrade. >You might want to consider buying another sup. > >IMO, there is no huge benefit in using the install all script in a >single sup system - in the end, all it will do for you is a little >sanity checking and maybe save you from fat fingering a bootstring. > >In your situation, I would copy over the new images you want; manually >change the bootstrings & save to startup; power off the box, yank the >sup & add the DRAM; and then power it all back on. > >Tim > > > > >Regards, > > > >Antonio Soares, CCIE #18473 (R&S/SP) > >amsoa...@netcabo.pt > >http://www.ccie18473.net > > > > > > > >-Original Message- > >From: Dirk Woellhaf [mailto:dirk.woell...@gmail.com] > >Sent: quinta-feira, 8 de Novembro de 2012 14:10 > >To: Antonio Soares > >Cc: Charles Spurgeon; cisco-nsp > >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade > > > >Hi Antonio, > > > >You should be able to do the memory-upgrade without rebooting the box. > >I've never done it on my I own but I know a few which did without any > >problem. I believe they first upgraded the memory and then did the update! > > > >Dirk > > > >Sent from my iPhone > > > >On 08.11.2012, at 13:42, Antonio Soares wrote: > > > > > Thanks, I don't know if you noticed but somewhere in the thread > > > the bug was mentioned and it is resolved in 5.1.5 and later. > > > > > > Bug CSCtn61286 - Boot variables are not set up correctly on Sup-2 > > > after ISSU > > > > > > So in my case, it should not give me problems (5.2.3a to 5.2.7). > > > > > > But since I also need to upgrade the SUP1 RAM from 4G to 8G, I > > > have no other option than doing the traditional upgrade. It's the > > > only way to just send the box down 1 time: > > > > > > - update the boot variables > > > - power off and upgrade the RAM > > > - power on > > > > > > The install all script has another limitation: it w
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Just for future reference if someone runs into the same issues: The hw revision of the M132XP that had no problems: 1.7 The hw revision of the M132XP that failed: 1.5 The hw revision of the spare card that had no problems: 2.3 Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Antonio Soares Sent: sábado, 17 de Novembro de 2012 21:24 To: 'Colin Whittaker'; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Unbelievable, this is a 70k card, isn't it ? Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Colin Whittaker Sent: sábado, 17 de Novembro de 2012 18:22 To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade On Sat, Nov 17, 2012 at 05:28:48PM -, Antonio Soares wrote: > Another long night... The upgrade of one Nexus was completely clean, > the second one was a nightmare. One M1-32XP card remained in the state > "powered-up" forever... The reload didn't make it work, neither the > re-seat or even the NX-OS downgrade... Had to open a P1 TAC case and > then the engineer said it was a faulty card. Got the replacement but > had to delay the installation 48 hours. > > Anyone has have bad experiences with this M1 type of cards card lately ? > It's the second one that gets faulty in less than a year. It seems the > MTBF is inversely proportional to the price :( Upgrade cycles tend to flush out latent faults in the linecards. When doing upgrades it is best to have spare cards on hand to handle those that fail. The failure rate on the M1 cards has gotten a lot better over the last two years. Gone are the days of 20% of the cards being DOA. Colin -- Colin Whittaker +353 (0)86 8211 965 http://colin.netech.ie co...@netech.ie ___ 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] can not configure modem by router
thanks Christain, you help me alot. thanks On Sun, Nov 18, 2012 at 12:29 PM, Christian Kratzer wrote: > Hi, > > > On Sun, 18 Nov 2012, s m wrote: > >> thanks Juergen >> what i've got from your words is: for connecting modem to cisco we should >> reverse send and receive while for connecting cisco to PC it should be >> straight. is it true or i misunderstand what you mean? >> > > exactly the opposite: > > For Cisco to PC you need a rolled cable as both devices classify as DTE > (Data Terminal Equipment). > > For Cisco to Modem you need a straight cable as the modem is a DCE (Date > Communication Equipment). > > The blue console cable is a rolled cable. If you look at the connectors > closely and you will see the colors reversed. > > So just grab a regular patch cable and you should be fine. > > Greetings > Christain > > > this connection is so important for me therefore i want to buy a cable but >> don't know what exactly cable i should buy. please help me to buy a >> correct >> one. >> >> thanks for your attention >> >> On Sat, Nov 17, 2012 at 6:04 PM, Juergen Marenda >> wrote: >> >> On Sat, Nov 17, 2012 at 02:22:58PM +0330, s m wrote: >>> hello guys i wanna connect a modem to a 2800 router by AUX port. this is my configuration: modem InOut modem autoconfigure discovery transport input all stopbits 1 speed 38400 flowcontrol hardware the speed value changes because "mode autoconfigure discovery" is set. i used blue console cable RJ45 to DB9 for connecting AUX port to modem. >>> >>> use the black cable or the supplied 9-to-25 CON-MODEM-adapter. >>> the light-blue cable is to connect to a PC-AT Serial Port. >>> >>> Or crimp an RJ45 Plug reverse on the router's end of the cable . >>> >>> Or use a NULLmodemcable beetween Modem and DB9 "con" . >>> >>> You should be able to telnet ip-of-your-router 2001 , >>> authenticate at router, and then speak with the modem. >>> >>> If you connect PC with Hyperterm instead of the modem, >>> and this works, then it will not work with the modem, >>> and you need to get/build a fitting cable, see above. >>> >>> >>> [...] >>> i read when the connection is correct, modem hardware stats should be CTS not noCTS. moreover i can not do reverse telnet to modem. >>> >>> YOur cabling is wrong, both sides SEND and RECIVE Lines are connected >>> together >>> (RS232 i must be shorit-ciruit proof, +-12 V...) >>> please let me know how i should fix it and configure my modem by AT commands. >>> >>> Hope this helps, >>> >>> Juergen. >>> >>> >>> ___ >> 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/ >> >> > -- > Christian Kratzer CK Software GmbH > Email: c...@cksoft.de Wildberger Weg 24/2 > Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden > Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart > Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian > Kratzer > ___ 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] IP SLA
On (2012-11-19 11:08 +0100), Christophe Fillot wrote: > About the packet handling, since I only support TCP/UDP probes, I > use the classic socket > API. It is not using AF_PACKET to support some strange probes, it only supports UDP jitter for Cisco. It is using AF_PACKET so it can see full header MAC, VLAN, IP, so it can respond to any IP, any VLAN, without needing explicit configuration in responder end. It can be huge OPEX save, when no one needs to be taught how to add VLAN to linux. When you want to add new IP SLA/RPM for L3 MPLS VPN, you just configure the PE and leave responder alone. You don't even have to know if the polling client is Cisco or Juniper. -- ++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] DHCP option 26
Sent from a mobile device On 19/11/2012, at 20:36, M K wrote: > Hi all I have configured the belowR1#sh run | sec ip dhcpip dhcp pool TEST > network 192.1.12.0 255.255.255.0 domain-name cisco.com option 26 hex 0578 > Am trying to send the mtu interface vlaue through the DHCP offer but it's not > happening578 hex = 1400 Can this actually work? I would imagine that this is fairly late in the entire process on an interface to set mtu. ___ 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] IP SLA
Saku Ytti wrote: http://tools.ietf.org/html/draft-cisco-sla-protocol-04 http://www.juniper.net/us/en/local/pdf/app-notes/3500145-en.pdf I wonder if those implicitly mean that you are allowed to build responder or not. The Cisco draft is not really what we're seeing in real-life (real-life identifies itself as version 1, draft is for version 2). Indeed the packet format is very different... How does your responder compare to the one I gave link for? Does it support microsecond precision for UDP jitter? Tbh I didn't know there was a "precision microsecond" command. From what I can see in your co-worker's code, this is handled by a different message type (with code 0x03) whereas the probe with millisecond resolution has code 0x02. Adding support for it shouldn't be very complicated. About the packet handling, since I only support TCP/UDP probes, I use the classic socket API. Christophe ___ 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] DHCP option 26
Hi all I have configured the belowR1#sh run | sec ip dhcpip dhcp pool TEST network 192.1.12.0 255.255.255.0 domain-name cisco.com option 26 hex 0578 Am trying to send the mtu interface vlaue through the DHCP offer but it's not happening578 hex = 1400 Any ideas? 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] IP SLA
On (2012-11-19 09:48 +0100), Christophe Fillot wrote: > I've written a small responder that handles TCP connect, UDP echo > and UDP jitter operations (for IPv4/IPv6), > but unfortunately I don't know if I can publish it for the reasons > you gave below. > The protocol is easy to decode anyway. http://tools.ietf.org/html/draft-cisco-sla-protocol-04 http://www.juniper.net/us/en/local/pdf/app-notes/3500145-en.pdf I wonder if those implicitly mean that you are allowed to build responder or not. The Cisco draft is not really what we're seeing in real-life (real-life identifies itself as version 1, draft is for version 2). How does your responder compare to the one I gave link for? Does it support microsecond precision for UDP jitter? -- ++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] IP SLA
Saku Ytti wrote: I have been looking at IP SLA and was wondering whether there are any appliances around which emulate Ciscos IP SLA so that you can use it as a responder, or even better, the transmitter end? Have you found any? I'd be very interested in commercial solution also. Preferably one which does hardware timestamping. I've written a small responder that handles TCP connect, UDP echo and UDP jitter operations (for IPv4/IPv6), but unfortunately I don't know if I can publish it for the reasons you gave below. The protocol is easy to decode anyway. IP SLA is proprietary protocol, so technically if you want to do commercial solution, you'd need to buy permission for it from Cisco. And I know many people buying dedicated Cisco CPE for IP SLA responders, so it might be that companies have tried to build IP SLA responders but Cisco has said 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/
Re: [c-nsp] 3750x Alternatives
On Mon, Nov 19, 2012 at 5:40 PM, CiscoNSP_list CiscoNSP_list < cisconsp_l...@hotmail.com> wrote: > We currently use 3750x stack to terminate pairs of 2960S(TOR's) - Our > traffic is quite bursty, and we are getting hit with the small buffers > (output drops)...any suggestions on alternative platforms? (We only do L2 > on the current switches) > 6503's w/ VSS? > 4500x w/ VSS? > Nexus w/ Vpc? > If you only want to do layer 2, you could also look at a pair of Nexus 5Ks and run VPC - or look at other vendors. Do you really need two chassis/ VSS? 4500s don't have VSS yet, so you could possibly get away with a 4500 - possible a second 4500 as a cold spare. Andrew ___ 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/
