Re: [c-nsp] Basic BGP Cisco Router

2014-05-26 Thread Mark Tinka
On Sunday, May 25, 2014 10:45:31 PM Dan Brisson wrote: So I'm looking at basic default routing via BGP, about 75Mb/s of throughput needed, and would like (3) 100mb or 1Gig interfaces. Seems like a 2900 series router would work but would love to hear what folks think. If you're looking for

Re: [c-nsp] Basic BGP Cisco Router

2014-05-26 Thread Andrew Miehs
On 26 May 2014, at 3:58 pm, Mark Tinka mark.ti...@seacom.mu wrote: If you're looking for something really modest, with little to no opportunity for growth, consider the CSR1000v. Thats actually a pretty cool idea! I keep forgetting that the thing exists. Although - however, once I start

Re: [c-nsp] Basic BGP Cisco Router

2014-05-26 Thread Mark Tinka
On Monday, May 26, 2014 08:39:45 AM Andrew Miehs wrote: Thats actually a pretty cool idea! I keep forgetting that the thing exists. Although - however, once I start looking at software routers, I really wonder whether it wouldn't be just as effective running a competing product or even open

Re: [c-nsp] Basic BGP Cisco Router

2014-05-26 Thread Reuben Farrelly
On 26/05/2014 4:39 PM, Andrew Miehs wrote: On 26 May 2014, at 3:58 pm, Mark Tinka mark.ti...@seacom.mu wrote: If you're looking for something really modest, with little to no opportunity for growth, consider the CSR1000v. Thats actually a pretty cool idea! I keep forgetting that the thing

Re: [c-nsp] apply rate limit to VFI interface

2014-05-26 Thread Vitkovský Adam
Hello Alejandro, I think you can only rate-limit on EFPs ingress/egress to/from a particular PW. adam -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Alejandro Aristizabal Sent: Friday, May 23, 2014 5:13 PM To: cisco-nsp@puck.nether.net

[c-nsp] BGP funny in SXI

2014-05-26 Thread Gert Doering
Hi, saw something interesting today... not a real problem, but it should not do this. Maybe one of you has seen this and understands what the box is doing. Background: there used to be a BGP prefix 195.24.120.0/21, which was ghosted, and finally it's gone. So, BGP shows it's gone, but it does

Re: [c-nsp] Billing per Mb (Large ISPs)

2014-05-26 Thread Tony
Hi, On Sun, 25 May 2014 04:04:52 +1000, Gert Doering g...@greenie.muc.de wrote: Hi, On Sat, May 24, 2014 at 08:47:45PM +0300, Artem Viklenko wrote: we stop to bill per mb and move to bill by bandwidth. Where exactly is the difference of bill per mb and bill by used bandwith, except a

[c-nsp] PacketLight products

2014-05-26 Thread Chris Stand
For any of you who directly work with the fiber connectivity side, are you familiar with PacketLight WDM products ? I have to add a new DC to our mix and our CWDM solution is insufficiently flexible. Thank you, Chris ___ cisco-nsp mailing list

Re: [c-nsp] Log that google doesn't help

2014-05-26 Thread Pete Lumbis
Just to add a little more, XDR is the component used to send routes from the supervisor to DFCs across the fabric of a 6500/7600. Generally you'll need to engage TAC for assistance on this kind of problem. -Pete On Mon, May 19, 2014 at 5:18 AM, David beckett david.beck...@ch.ibm.comwrote:

Re: [c-nsp] Stray OSPF packets from non-link-local IPs ranges

2014-05-26 Thread Richard Hartmann
On Tue, Apr 29, 2014 at 12:48 PM, Richard Hartmann richih.mailingl...@gmail.com wrote: on ASR9k with IOS XR 4.3.4 I am seeing messages like: %ROUTING-OSPF-4-BADLENGTH : Invalid length 64765 in OSPF packet from x.x.x.x (ID 0.0.0.0), TenGigE0/0/2/3 We just had another few of those packets.

Re: [c-nsp] Cisco CMTS and ISC DHCP Strange Issue

2014-05-26 Thread Jean-Francois . Dube
Hi Rupesh, I suggest you first make sure DHCP works properly for the affected CPE. debug cable mac H.H.H debug cable dhcp These should allow you to see DHCP D.O.R.A. for a CPE with MAC H.H.H The CMTS needs to use leasequery (RFC 4388) if you experienced an outage of some sort to rebuild its

[c-nsp] m3600x-cx tx/rx of transit traffic STOPS when LFA repair path found (int enabled), 15.3(3)S1a; 15.3(3)S2.

2014-05-26 Thread Vitkovský Adam
Hi Folks, Has anyone encountered an issue where me3600 stops forwarding transit traffic when LFA repair path is found over a newly enabled interface please? This is on 15.3(3)S1a a well as on 15.3(3)S2. Ping to directly connected interfaces works however anything behind the box either in global