Re: [c-nsp] IPSEC + TFTP don't work

This is a common problem caused by the TFTP program/PXE chip being unable to reassemble fragmented packets, as I think others may have mentioned. Depending on the PXE boot server you're using, you can generally set the maximum size for TFTP packets. I know SCCM can, as a registry entry, but

Re: [c-nsp] 7600 AtoM mpls issue (Gert Doering)

Hi, In 7600 with 67xx Cards you can make in interface Vlan EoMPLS. I have implement this with SRD and SRE IOS Take care that both end of the xconnect has the same MTU!! If you put the following command it should inform you for any problems! sh mpls l2transport vc 701 detail Local interface:

Re: [c-nsp] 7600 AtoM mpls issue (Gert Doering)

Hi, On Fri, Apr 06, 2012 at 10:41:20AM +0300, michalis.bersi...@hq.cyta.gr wrote: In 7600 with 67xx Cards you can make in interface Vlan EoMPLS. As far as I understand, only if you have ES(+) or SIP cards on the core-facing side of your 7600. gert -- USENET is *not* the non-clickable part

Re: [c-nsp] 7600 AtoM mpls issue

Hi, On Thu, Apr 05, 2012 at 05:09:15PM -0400, Chris Lane wrote: Thanks for your reply, i may just grab an 2 ES+ cards... If you have the moneys lying around... I don't think i can do the sub int ~ my p2p is L3, wouldn't i have to change that to a sub int as well?? If the VLAN is coming in

Re: [c-nsp] 7600 AtoM mpls issue (Gert Doering)

Yes this might be true, for the CORE-facing side, in our implementation we have these cards facing the CORE. -Original Message- From: Gert Doering [mailto:g...@greenie.muc.de] Sent: Friday, April 06, 2012 10:55 AM To: Μπερσίμης Μιχάλης (900356) Cc: cisco-nsp@puck.nether.net Subject: Re:

Re: [c-nsp] 7600 AtoM mpls issue (Gert Doering)

Hi, On Fri, Apr 06, 2012 at 11:15:32AM +0300, michalis.bersi...@hq.cyta.gr wrote: Yes this might be true, for the CORE-facing side, in our implementation we have these cards facing the CORE. And that's the trick - the 7600 packet forwarding side knows that the core-facing side has a few extra

Re: [c-nsp] ME3600X architecture

Bacon, I'll unicast you the slides. Regarding MVPN, it is supported in hardware. EFT image is available for testing. -Waris -Original Message- From: Jeff Bacon [mailto:ba...@walleyesoftware.com] Sent: Thursday, April 05, 2012 5:08 AM To: Waris Sagheer (waris) Cc:

Re: [c-nsp] IPSEC + TFTP don't work

Victor Sudakov v...@mpeks.tomsk.su writes: Randy wrote: Victor wrote: RS wrote: Try setting the MTU on the ethernet on the TFTP server to 1400 or so rather than 1500.  That oughta fix the problem, assuming that the tftp server software is sanely written.  If it were TCP

Re: [c-nsp] real world experience - ASR901 / ASR903

I have about (10) asr 901's bought and deployed and currently testing. I'm testing MPLS L2VPN's (eompls pw's with 802.1q tagging within) currently and it's working nicely. The policing on the ingress tagged traffic within the service instance doesn't seem to be working and I have TAC and

Re: [c-nsp] 7600 AtoM mpls issue

Hi, (copying in cisco-nsp again, as I assume that someone else will eventually have the same problem and want to research the answer) On Fri, Apr 06, 2012 at 08:24:38AM -0400, Chris Lane wrote: yep its single ethernet port, ~ i looked up Mux-UNI ~ trying that but oddly now the vlan i am using

[c-nsp] OSPF's handling of secondary IP addresses on subinterfaces

I have a FastEthernet interface with multiple 802.1Q based subinterfaces. OSPF properly advertises routes for the subnets directly defined on these subinterfaces. However if I add secondary IP addresses to these subinterfaces, the subnets defined using the secondary command show up in the local

[c-nsp] 2547oDMVPN

I'm curious if anyone has deployed 2547oDMVPN, and if so what your experience has been. I'm considering it as an overlay on a carrier provided MPLS/private cloud. -- Eric Cables ___ cisco-nsp mailing list cisco-nsp@puck.nether.net