[j-nsp] A new "OSPF neighbor" entry in 7.4
Paul Connally
paul.connally at gmail.com
Tue Jan 3 18:45:52 EST 2006
We just received a new M7i, that's running the factory installed rev
7.4R1.7. I was setting it up for testing, and noticed something I
don't think I've seen before.
When configuring OSPF, there's an entry in "show ospf neighbor" that
always stays stuck in "ExStart", but it's not an adjacency that it's
trying to build with a neighboring router, but rather it looks like
it's trying to make an adjacency with itself. I've checked on our
other Junipers and don't see this in other revisions (7.3R2.9, for
example). On those, it only shows the OSPF neighbors as being the
router at the other end of the link.
I am able to form adjacencies with a router on the other end of the
actual link fine; this doesn't seem to hurt anything, but I really
want to know WHY it's doing this. Nothing really out of the ordinary
in traceoptions; the router interface speaks hellos to 224.0.0.5, but
that's normal.
On this router, I've configured 192.168.1.1/28 on the FE interface,
and 192.168.1.254/32 on the loopback (which is also set as the
router-id in 'routing-options'). This is what it shows:
> show ospf neighbor
Address Interface State ID Pri Dead
192.168.1.1 fe-0/2/3.0 ExStart 192.168.1.254 128 32
> show ospf neighbor detail
Address Interface State ID Pri Dead
192.168.1.4 fe-0/2/3.0 Full 192.168.1.4 1 33
Area 0.0.0.0, opt 0x2, DR 192.168.1.4, BDR 0.0.0.0
Up 00:00:26, adjacent 00:00:26
192.168.1.1 fe-0/2/3.0 ExStart 192.168.1.254 128 39
Area 0.0.0.0, opt 0x2, DR 192.168.1.1, BDR 0.0.0.0
Up 00:00:26
master, seq 0x816d7bd5, rexmit DBD in 0 sec
rexmit LSREQ in 0 sec
Interface and OSPF config are pretty ordinary; no filters or anything.
fe-0/2/3 {
unit 0 {
description "Test LAN - Inside to Firewall";
family inet {
no-redirects;
address 192.168.1.1/28;
lo0 {
unit 0 {
family inet {
no-redirects;
address 192.168.1.254/32;
ospf {
traceoptions {
file ospf.log size 5m;
flag hello detail;
}
area 0.0.0.0 {
interface lo0.0;
interface fe-0/2/3.0;
}
More information about the juniper-nsp
mailing list