From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Sun Jan 28 2001 - 02:14:06 GMT-3
Never have seen this one before.
I was testing out my new terminal server, and had problems getting into one
of my routers. Nothing new here. I've ditzed with this thing all day today,
and run into various odd things.
So I unplug the octopus cable plug, put a direct connection into the console
port, and discover the router taking an inordinate amount of time doing
something called "checking ospf interface" or some such. It takes forever.
I finally outwait the delay, do a show run, and see that every interface has
a line "ip ospf interface-retry 0" this is apparently undocumented within
the command interpreter. When you do a "ip ospf ?" there ain't no such
command.
Well, I try looking it up on the documentation CD. No luck. Not mentioned in
the 12.x command reference.
Real CCO ( i.e. TAC ) has a document or two, though. According to TAC:
--------
When OSPF is configured on a router, the router interfaces are polled and
interfaces that are up are enabled with OSPF. As interfaces become more
complex and the amount of interfaces increase, the time for interfaces to
come up also increases, and there is a slight chance that OSPF will poll the
interface before its state is fully up. This can result in the interface
being up, but OSPF not being enabled on it. The default number of times OSPF
polls the interfaces has been increased from 0 to 10 in order to avoid this
situation.
If you're running OSPF and upgrading to Cisco IOS(r) Software release
12.0(8)S, you'll notice the ip ospf interface-retry 0 is automatically added
to every interface. This value is the old default value. The new default
number of retry times is 10. The router displays the old behavior so the
command shows up in the configuration.
----------
my particular IOS version is 12.0.9 on this router. Other routers have
12.1.something, and I have not run into this before. I might go along with
the words of the document, but I have done ospf before on my routers, and
have not seen this. Well, I did downgrade the router in question from a 12.1
to 12.0.9 because of other issues with the 12.1 image that used to be on
there.
Any case, I mention this because, as I said, I originally interpreted my
inability to get into this router via the terminal server as a terminal
server / cable / configuration problem. Something to be aware of. I hear
tell the Lab is filled with buggy 12.x IOS images now.
Chuck
http://www.1112.net/lastpage.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:45 GMT-3