Re: [c-nsp] sdn/nfv

2014-06-20 Thread Mark Tinka
On Thursday, June 19, 2014 10:33:16 PM Aaron wrote: Is anyone out there yet working with any sdn controllers? or nfv objects in servers. or openflow? If running a route reflector over IOS XE over CSR1000v over VMware ESXi over an HP server counts as NFV, then I'm doing that :-). Mark.

Re: [c-nsp] sdn/nfv

2014-06-20 Thread Vitkovský Adam
I think vendors have grasped this emerging opportunity very well. Take Cisco for example the openflow APIs are available to the majority of their high-end products and they have virtualized their OSes as well. I know for a fact that majority of SPs use some kind of NFV already. However I'd

[c-nsp] Blocking arp / DAI

2014-06-20 Thread Mike
Hi, I have 3560G switches configured for dhcp snooping, and I can see that the switches have a database of dhcp bindings per interface. I am wondering if there might be some way to configure the switch to block all traffic (arp for example) for addresses not in the binding database? eg:

Re: [c-nsp] sdn/nfv

2014-06-20 Thread Scott Granados
I don’t think equipment vendors are scared by the idea of software networks because they are participating in that space in a big way. Look at what Cisco is doing or Juniper for that matter with contrails. I haven’t worked with the Cisco virtualized objects but I have used Junipers VFirefly

Re: [c-nsp] Blocking arp / DAI

2014-06-20 Thread Lukas Tribus
Hi, I have 3560G switches configured for dhcp snooping, and I can see that the switches have a database of dhcp bindings per interface. I am wondering if there might be some way to configure the switch to block all traffic (arp for example) for addresses not in the binding database? eg: Can

Re: [c-nsp] Blocking arp / DAI

2014-06-20 Thread Casper Gondelach
Mike, Are you looking for ip source guard? http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/swdhcp82.html This uses the binding database to block everything except the database. We use this to prevent static ip's / address

[c-nsp] QOS on asr901

2014-06-20 Thread Vitkovský Adam
Hi folks, I'm just evaluating asr901 and came across some QOS issues. Anyone using egress QOS with priority and random-detect discard-class-based on ASR901 please? I'm getting so many errors and limitations. Had to strip the priority queue config to basically this: class core_realtime

[c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Lukas Tribus
Hey guys, I feel like this is a stupid question with a simple solution, but I just not see it: When I configure a new BGP session, before I can shutdown the neighbor or apply a specific peer-group/session-template/policy-template, I need to configure the remote-as, so the first command in the

Re: [c-nsp] BGP vs OSPF (CE - PE)

2014-06-20 Thread Clinton Work
With BGP we use local-pref to select the preferred BGP exit point for the CE router/site. The CE advertises different BGP MED values to the PE routers in order to select the preferred entry link to the CE/site. Each CE router in the same VPN is given a separate private AS number. -- Clinton

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Scott Granados
So this is not a stupid question at all. I’ve wondered about this myself. I suspect the reason your terminal slows is the CPU spikes when adding a new neighbor and the session establishes. (I could be wrong that’s just a guess) In my case I never had the slow down problem so I would cut and

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Dimitris Befas
Use IOS-XR instead :-) With IOS and XE you may just configure a wrong AS number (neighbor 2001::123 remote-as 6) so the adj won't come up, then shut it (neighbor 2001::123 shut) and while in a shut state, configure the correct AS (neighbor 2001::123 remote-as 65005). Now feel free to no shut (no

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Chuck Church
Any reason you can't null route that remote neighbor host, configure the neighbor and shut it down, then remove that static route? Chuck -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Lukas Tribus Sent: Friday, June 20, 2014 10:40 AM To:

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Blake Dunlap
one way to do so is no default ipv4 activation. That said, my paste ins are generally the following: line 1: nei X as Y line 2: nei X shut I wish the sessions started by default shut. -Blake On Fri, Jun 20, 2014 at 9:39 AM, Lukas Tribus luky...@hotmail.com wrote: Hey guys, I feel like this

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Dimitris Befas
You can use peer-groups. Setup whatever setting you want for the peer-group (neighbor peer-group-name shutdown) and enable the neighbor when you want. But if you have multiple neighbors then you will affect all of them at once. -Original Message- From: Dimitris Befas

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Tim Kleefass
On 20.06.2014 4:39 PM, Lukas Tribus wrote: Let me know how you guys avoid this problem. I always shutdown the session after the remote-as statement, and hope that I'm fast enough. Hint: with an good environment you can use esc backspace to delete the remote-as from the previous statement quite

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Adam Atkinson
isn't no bgp default ipv4-unicast the solution? from http://www.cisco.com/c/en/us/td/docs/ios/iproute_bgp/command/reference/irg_book/irg_bgp1.html#wp1113664 IPv4 address family routing information is advertised by default for each BGP routing session configured with the neighbor remote-as

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Koch, Andrew
-Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Lukas Tribus Sent: Friday, June 20, 2014 09:40 To: cisco-nsp@puck.nether.net Subject: [c-nsp] IOS: catch 22 when enabling new bgp neighbors Hey guys, I feel like this is a stupid

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Tim Durack
On Fri, Jun 20, 2014 at 10:39 AM, Lukas Tribus luky...@hotmail.com wrote: Hey guys, I feel like this is a stupid question with a simple solution, but I just not see it: When I configure a new BGP session, before I can shutdown the neighbor or apply a specific

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Azher Mughal
How about neighbor 1.1.1.1 remote-as 12 shutdown. It issues two commands: neighbor 1.1.1.1 remote-as 12 neighbor 1.1.1.1 shutdown -Azher On 6/20/2014 10:00 AM, Dimitris Befas wrote: Use IOS-XR instead :-) With IOS and XE you may just configure a wrong AS number (neighbor 2001::123 remote-as

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Mark Tinka
On Friday, June 20, 2014 07:00:50 PM Dimitris Befas wrote: Use IOS-XR instead :-) With IOS and XE you may just configure a wrong AS number (neighbor 2001::123 remote-as 6) so the adj won't come up, then shut it (neighbor 2001::123 shut) and while in a shut state, configure the correct AS

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread N. Max Pierson
address-families with 'activate' keyword maybe? - m On Fri, Jun 20, 2014 at 11:38 AM, Blake Dunlap iki...@gmail.com wrote: one way to do so is no default ipv4 activation. That said, my paste ins are generally the following: line 1: nei X as Y line 2: nei X shut I wish the sessions

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Oliver Boehmer (oboehmer)
a new BGP session, before I can shutdown the neighbor or apply a specific peer-group/session-template/policy-template, I need to configure the remote-as, so the first command in the address-family is: neighbor 2001::123 remote-as 65005 Now, if I don't specify the policies right away, or

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Ge Moua
method_1: a. upload config_snippet to flash: (via method of choice tftp, sneaker-net via flash2, etc) b. copy flash:/config_snippet.txt system:running.config method_2: b. copy tftp://ip_addr/config_snippet.txt system:running.config I prefer method_1 as this mitigate dependencies on network

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Michael Loftis
ok remote-as actually sorry On Fri, Jun 20, 2014 at 11:00 AM, Michael Loftis mlof...@wgops.com wrote: neigh xx peer-as shutdown Problem solved. On Fri, Jun 20, 2014 at 9:37 AM, Scott Granados sc...@granados-llc.net wrote: So this is not a stupid question at all. I’ve wondered

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Michael Loftis
neigh xx peer-as shutdown Problem solved. On Fri, Jun 20, 2014 at 9:37 AM, Scott Granados sc...@granados-llc.net wrote: So this is not a stupid question at all. I’ve wondered about this myself. I suspect the reason your terminal slows is the CPU spikes when adding a new neighbor

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Blake Dunlap
Wow, you can do that? I feel really really dumb now... On Fri, Jun 20, 2014 at 11:30 AM, Koch, Andrew andrew.k...@tdstelecom.com wrote: -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Lukas Tribus Sent: Friday, June 20, 2014 09:40 To:

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Brandon Ewing
On Fri, Jun 20, 2014 at 08:11:10PM +0300, Dimitris Befas wrote: You can use peer-groups. Setup whatever setting you want for the peer-group (neighbor peer-group-name shutdown) and enable the neighbor when you want. But if you have multiple neighbors then you will affect all of them at once.

Re: [c-nsp] Blocking arp / DAI

2014-06-20 Thread Mike
On 06/20/2014 06:39 AM, Casper Gondelach wrote: Mike, Are you looking for ip source guard? http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/swdhcp82.html This uses the binding database to block everything except the

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Raymond Burkholder
When I configure a new BGP session, before I can shutdown the neighbor or apply a specific peer-group/session-template/policy-template, I need to configure the remote-as, so the first command in the address-family is: neighbor 2001::123 remote-as 65005 Another way to handle this is to

Re: [c-nsp] QOS on asr901

2014-06-20 Thread Caillin Bathern
Hi Adam, I am out wine tasting but I can give you some pointers later, IIRC the priority % command automatically police's to that %. I have a document that you could probably get your hands on if you poke your account manager in the right way which explains the answers but I can't share with

Re: [c-nsp] QOS on asr901

2014-06-20 Thread Sarala Akella (sakella)
Hello Adam, Jun 20 21:21:46.562: Data Qualify failed(2):-7 Jun 20 21:21:46.562: Error in programming Exp:-7 This means the config is not supported. It could be the service policy is applied in wrong place. If you need help with understanding policing and priority , feel free to open a

Re: [c-nsp] IOS: catch 22 when enabling new bgp neighbors

2014-06-20 Thread Oliver Boehmer (oboehmer)
[neighbor 192.0.2.100 remote-as 64511 shutdown] Wow, you can do that? I feel really really dumb now... so do I ;-) oli ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at

[c-nsp] 4500X trivia question...

2014-06-20 Thread Jeff Kell
Just breaking ground with some 4500X switches... and was curious... With other Catalysts the switches are often oversubscribed... at least the uplinks... but there were platform specific commands to determine which ports were mapped to which ASICs and you could try to optimize your loads across

Re: [c-nsp] 4500X trivia question...

2014-06-20 Thread Jeremy Bresley
On 6/20/2014 11:51 PM, Jeff Kell wrote: Just breaking ground with some 4500X switches... and was curious... With other Catalysts the switches are often oversubscribed... at least the uplinks... but there were platform specific commands to determine which ports were mapped to which ASICs and