[nsp] Setting router ospf passive-interface default

[Lupi, Guy]

I have never heard of a way to implement "passive-interface default" on an
active configuration with adjacencies without having the adjacencies go down
and have to establish again.  

Interestingly enough, in certain IOS releases, you also can't enter the
"passive-interface default" command even if it is already in your
configuration, it will knock all the sessions down and you have to enter
your "no passive-interface" commands again.

-----Original Message-----
From: John Kristoff [mailto:jtk at northwestern.edu] 
Sent: Tuesday, June 15, 2004 11:44 AM
To: cisco-nsp at puck.nether.net
Subject: [nsp] Setting router ospf passive-interface default


Perhaps I've missed something, but is there a way to implement on a router
already running OSPF, where routing interfaces are not going to be change
the following:

  router ospf [process-id]
   passive-interface default

Without having adjacency changes occur?  In my limited testing, either with
a quick copy and paste or tftp upload to the running config, it seems that
either will result in OSPF dropping all interfaces causing neighbor
adjacencies to have to be reestablished.  Since in my example, the routing
interfaces will have 'no passive-interface', routing really doesn't change
so it would be nice if reconvergence didn't have to occur either.

John
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/