Re: [c-nsp] mpls on isrv
It seems to me, that upgrading ENCS to 3.7.1 solved this issue... On Tue, 13 Mar 2018, BALLA Attila wrote: Hello, I have just received an ENCS5412 for testing, I have installed an ISRv and connected the ENCS to an external MPLS router. The routing and LDP is working fine between them, but the baby giant frames are dropped somewhere: it means that 1500-byte long packets with two labels and DF-bit are dropped. I am sure, that the openvswitch of ENCS drops these packets. Is any possibility to change of the MTU in the openvswitch of ENCS? BR, Attila ___ 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] mpls on isrv
Hello, I have just received an ENCS5412 for testing, I have installed an ISRv and connected the ENCS to an external MPLS router. The routing and LDP is working fine between them, but the baby giant frames are dropped somewhere: it means that 1500-byte long packets with two labels and DF-bit are dropped. I am sure, that the openvswitch of ENCS drops these packets. Is any possibility to change of the MTU in the openvswitch of ENCS? BR, Attila ___ 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
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
[c-nsp] npe-g2 + shaping
Hello, I met an interesting issue: there is a Cisco 7200 NPE-G2 with 12.4(24)T7, this router terminates some broadband users, we applied shaping on the virtual-template and we surprised: shaping was not working. We upgraded (downgraded?) to 12.2(33)SRE6 and the shaping was working properly, so I think it is not a config issue. This router has a SA-VAM2+, but SRE does not support this module. First question: is it normal, that shaping is not working on virtual-template at 12.4(24)T7? Second question: is any release which supports shaping on virtual-template and sa-vam2+? BR, Attila ___ 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 bgp forward
Hello, I would like to know if "mpls bgp forward" is supported on ISR G2 platform, especially on Dialer interface. It was working in GNS3 with C7200, but in the real life it could be different. The goal is set up an MPLS/VPN on several ADSL CPE (this would be an ISR G2 router), I'd like to avoid the usage of any IGP between BRAS and ADSL CPE, so the remaining option is BGP. I didn't find any docu, if it is a supported model... Any hints are helpful. BR, Attila ___ 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] asr1000
Hello, we have an asr1000 acts as an LNS. Two weeks ago we upgraded it to XNF2, but the packet forwarding was not working at half of the pppoe sessions. We tested it with ping, the cpe received the icmp packet, and it sent the icmp replay, but the asr1000 was unable to handle it, so the pppoe connection (virtual-access interface) was up, but not working. Downgrading back to XNE1 didn't solve the issue, we had the same problem (maybe a microcode downgrade was not successful). After clearing the virtual-template and recreating the virtual-template the sessions were working again. Till now. We reloaded the box again, the first pppoe connection setup is ok, but if we cleared the session, then it didn't work any more: the connection setup was fine, but packet forwarding is broken... There no special thing in the cef table :-( Is any hint? BR, -A. ___ 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] Juniper M320 vs. 7600/SUP320-3BXL and WS-X6148A-GE-TX
what about asr9k with low-queue cards? its price and performance is reasonable as well. br, A. On Wed, 28 Jul 2010, Chris Hale wrote: Hello, Looking for options to our next upgrade from our 7200VXR platform. Someone suggested 7600 and the WS-X6148A-GE-TX cards with a SUP720-3BXL. We're doing BGP (4-5 full iBGP peers, 13 external peers (3 upstream, 10 downstream), all full routes), dot1q trunks, EoMPLS with L2VPNs. We will most likely do dot1q trunks to our agg switches at our other POPs with MPLS and L2VPNs being started/terminated on dot1q trunks. We're also looking to roll out IPv6 services in the next few months. Our options we're looking at are a Juniper M320 w/RE-1600 and SFP PIC (PB-4GE-SFP). I don't necessarily need the port density of the 48-port Cisco card, but it's always nice to have. Any reason not to start with the 6148A card and upgrade to the OSM cards, etc., I'm open to suggestions, opinions, etc, and especially any gotchas with either platform. Thanks, Chris ___ 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] Needs some help with QOS
Hi, you should use hierarchical QoS. First of all you should shape the output traffic down to the upstream speed, then you can use the llq inside the shaped class: http://www.cisco.com/en/US/tech/tk543/tk545/technologies_tech_note09186a00800b2d29.shtml BR, A. On Tue, 24 Mar 2009, Ivan Pepelnjak wrote: I have crafted and applied some rules which I thought would prioritize traffic from an 871w (via ADSL) to one specific host. The idea is that any traffic destined to this host should be prioritized over all other traffic. What is your upstream connection? If you're using PPPoE, you won't be able to do any output queuing, as the outbound LAN interface is never saturated (the bottleneck is experienced by the DSL modem). Ivan ___ 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] UDLD is err-disabling EoMPLS VC
Hello, UDLD is a Layer2 protocol, so EoMPLS transports all UDLD frames coming from CE. You should disable udld PE's interfaces connected to CE devices. BR, A. On Thu, 19 Feb 2009, Ruben Montes (Europe) wrote: Hi, We're already running 12.2(18)SXF11. I have udld enabled for the whole box, do you mean that I must explicitly disable udld in the interfaces on the PE switches where I have created the VC with x-connect? Thanks in advance, Ruben -Original Message----- From: BALLA Attila [mailto:a...@eik.bme.hu] Sent: jueves, 19 de febrero de 2009 17:00 To: Ruben Montes (Europe) Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] UDLD is err-disabling EoMPLS VC I had the same issue, it must be CSCsh99351, it is fixed in 12.2(18)SXF11. You should use udld on ce uplinks only. BR, A. On Thu, 19 Feb 2009, Ruben Montes (Europe) wrote: Hi, We have configured a new EoMPLS VC. After 3 or 5 pings, UDLD err-disables one of the interfaces. We are using port mode, is it recommended to run such a a feature in this type of connections? All the path has MPLS enabled and jumbo MTU enabled. Thanks in advance, Ruben ___ 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] UDLD is err-disabling EoMPLS VC
I had the same issue, it must be CSCsh99351, it is fixed in 12.2(18)SXF11. You should use udld on ce uplinks only. BR, A. On Thu, 19 Feb 2009, Ruben Montes (Europe) wrote: Hi, We have configured a new EoMPLS VC. After 3 or 5 pings, UDLD err-disables one of the interfaces. We are using port mode, is it recommended to run such a a feature in this type of connections? All the path has MPLS enabled and jumbo MTU enabled. Thanks in advance, Ruben ___ 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/
