A quick followup to my post in case someone else has this problem:
> It seems that my PMs aren't picking up their neighbors properly ...
...
> Apparently, the PMs and Cisco all on the same segment pick up each other ok
> and set Cisco as DR and "pm5" as BDR. However the "separate" PMs *only*
> see "pm5" and set IT up as DR and themselves as BDR. Does this indicate
> that the "separate" PMs think they are on another network or area?
Well, after *hours* on the phone with support, it turns out that the PMs
were having trouble neighboring with each other because of the
authentication. Adding simple password auth to all of them fixed the
problem. Someone in support there remembered this problem and the fix.
The cause is not known, however I'm guessing that I got it into that funny
situation when I tried to set MD5 on one PM and the Cisco, failed on the
Cisco and then backed it out of the PM. Some bit somewhere must have
gotten set and never cleared because most of the PMs never worked after
that. Very weird problem.
> Also, somewhere along the line of hundreds of config changes, my Cisco has
> started to have huge delays for commands like "sh ip ospf neighbor" -
> several minutes to finish. It wasn't doing this when I started - the
> output was immediate. I can't find anything I changed to cause that delay.
Seems that I accidentally did a:
conf t
ip ospf
which is shorthand for "ip ospf-name-lookup" or somesuch. Since I had no
valid DNS servers in the cisco, I was seeing name lookup expiration delays.
setting "no ip ospf" or setting the DNS servers fixed this one.
Later.
Derric
-- Derric Scott Scott Network Services, Inc. P. O. Box 361353 derric@scott.net (205)987-5889 Birmingham, AL 35236