Re: [c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-15 Thread Mattias Gyllenvarg
This whole protecting/verifying redundant customer functionality is a difficult problem. I have found it difficult to implement mechanisms that detect all possible faults on the main connection without making things very complicated. Mostly for remote areas where there is only one local POP that

[c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-14 Thread John Neiberger
We need to upgrade some ASR9Ks that have a lot of connected devices with complex interrelationships and we have to do a lot of work to make sure all the correct redundancy is in place prior to the upgrade. Since the router takes so long to reload, I'd like to find a way to essentially simulate the

Re: [c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-14 Thread Pete Lumbis
Copy/paste a bunch of null0 routes? deny any acls on interfaces? On Wed, Aug 14, 2013 at 10:54 AM, John Neiberger jneiber...@gmail.comwrote: We need to upgrade some ASR9Ks that have a lot of connected devices with complex interrelationships and we have to do a lot of work to make sure all

Re: [c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-14 Thread Tim Durack
I have wondered the same thing (on C6K/N7K.) I have since given up wondering and stick to using ospf max-metric int range shedload of interfaces shutdown That atleast works whilst exposing us to the minimum amount of surprise code features. Given enough time, I'm sure SDN/OpenFluff will solve

Re: [c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-14 Thread arulgobinath emmanuel
null0 doesn't cause the NHRP to trigger IMHO this will be a disaster . shut / no shut is the easiest but it doesn't simulate the whole part. real test comes when the modules crash when reloading specially after couple of years... :) what if we copy a empty config ??? and rollback the config ?

Re: [c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-14 Thread Pete Lumbis
This raises a good point. Is the goal to simulate a black-hole that could be seen with an incorrect adjacency, where control plane is healthy but data plane is broken, or is the goal to simulate taking this device offline? Do we care about carrier on the interfaces? On Wed, Aug 14, 2013 at

Re: [c-nsp] Temporarily disable all forwarding on ASR9K

2013-08-14 Thread John Neiberger
In my case, the best result would be to simulate taking the entire device offline, but I don't know if that's possible to reverse quickly. Taking the interfaces down would be great. Really, the simplest thing to do is just spend a minute to create a SMOP that shuts down the interfaces and be done