[j-nsp] OSPF problem

Kirstin nitsrik1 at gmx.de
Fri Jan 20 12:54:21 EST 2006


Hallo Harry,

thank you for your answer.


> I suggest that you modify your tracing to include error, lsa-update, and
> route, all with the detail switch. Then clear adjacencies with clear
> ospf neighbor and send the trace file result back out to the list.

I did that:

root at juniper.rz2# show protocols ospf
traceoptions {
    file ospf-log;
    flag error detail;
    flag lsa-update detail;
    flag route detail;


> 
> The only things that jump out in the config are:
> 
> 1. Authentication is disabled by default, so you should not need the
> authentication-type statement.
> 
> 2. The OSPF to OSPF redistribution term is not needed. This is the
> default OSPF behavior.


thanks, I took these two points out.


regards,
Kirstin

here is the log:

Jan 20 18:24:45 OSPF LSA Extern 86.10.222.0 133.213.96.166 from
239.213.240.204 newer than db
Jan 20 18:24:45 ospf_set_lsdb_state: Extern LSA 86.10.222.0 adv-rtr
133.213.96.166 state QUIET->QUIET
Jan 20 18:24:45 OSPF LSA Extern 86.10.228.184 133.213.96.166 from
239.213.240.204 newer than db
Jan 20 18:24:45 ospf_set_lsdb_state: Extern LSA 86.10.228.184 adv-rtr
133.213.96.166 state QUIET->QUIET
Jan 20 18:24:49 OSPF LSA rexmit
Jan 20 18:24:49 OSPF sent LSUpdate 239.213.240.199 -> 239.213.240.204
(ge-0/0/0.0, IFL 0x42)
Jan 20 18:24:49   Version 2, length 1396, ID 133.213.96.3, area 0.0.0.0
Jan 20 18:24:49   checksum 0x0, authtype 0
Jan 20 18:24:49   adv count 38
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.198
(ge-0/0/0.0) state changed from Full to Down due to Kill all neighbors
Jan 20 18:24:53 ospf_set_lsdb_state: Router LSA 133.213.96.3 adv-rtr
133.213.96.3 state QUIET->GEN_PENDING
Jan 20 18:24:53 OSPF trigger router LSA build for area 0.0.0.0
Jan 20 18:24:53 ospf_trigger_build_telink_lsas : No peer found
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.204
(ge-0/0/0.0) state changed from Exchange to Down due to Kill all neighbors
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.202
(ge-0/0/0.0) state changed from 2Way to Down due to Kill all neighbors
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.193
(ge-0/0/0.0) state changed from 2Way to Down due to Kill all neighbors
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.196
(ge-0/0/0.0) state changed from 2Way to Down due to Kill all neighbors
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.195
(ge-0/0/0.0) state changed from 2Way to Down due to Kill all neighbors
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.197
(ge-0/0/0.0) state changed from 2Way to Down due to Kill all neighbors
Jan 20 18:24:53 RPD_OSPF_NBRDOWN: OSPF neighbor 239.213.240.194
(ge-0/0/0.0) state changed from 2Way to Down due to Kill all neighbors
Jan 20 18:24:53 OSPF trigger router LSA build for area 0.0.0.0
Jan 20 18:24:53 ospf_trigger_build_telink_lsas : No peer found
Jan 20 18:24:53 ospf_set_lsdb_state: Network LSA 239.213.240.199 adv-rtr
133.213.96.3 state PURGE_PENDING->GEN_PENDING
Jan 20 18:24:53 OSPF trigger network LSA build for ge-0/0/0.0
Jan 20 18:24:53 OSPF trigger router LSA build for area 0.0.0.0
Jan 20 18:24:53 ospf_trigger_build_telink_lsas : No peer found
Jan 20 18:24:53 RPD_OSPF_NBRUP: OSPF neighbor 239.213.240.204
(ge-0/0/0.0) state changed from Init to ExStart due to Two way
communication established
Jan 20 18:24:53 OSPF trigger router LSA build for area 0.0.0.0
Jan 20 18:24:53 ospf_trigger_build_telink_lsas : No peer found
Jan 20 18:24:53 ospf_set_lsdb_state: Network LSA 239.213.240.199 adv-rtr
133.213.96.3 state GEN_PENDING->PURGE_PENDING
Jan 20 18:24:53 OSPF trigger router LSA build for area 0.0.0.0
Jan 20 18:24:53 ospf_trigger_build_telink_lsas : No peer found
Jan 20 18:24:53 ospf_set_lsdb_state: Router LSA 133.213.96.3 adv-rtr
133.213.96.3 state GEN_PENDING->QUIET
Jan 20 18:24:53 OSPF built router LSA, area 0.0.0.0
Jan 20 18:24:53 RPD_OSPF_NBRUP: OSPF neighbor 239.213.240.195
(ge-0/0/0.0) state changed from Init to ExStart due to Two way
communication established
Jan 20 18:24:55 OSPF sent LSUpdate 239.213.240.199 -> 224.0.0.5
(ge-0/0/0.0, IFL 0x42)
Jan 20 18:24:55   Version 2, length 76, ID 133.213.96.3, area 0.0.0.0
Jan 20 18:24:55   checksum 0x0, authtype 0
Jan 20 18:24:55   adv count 1
Jan 20 18:24:56 RPD_OSPF_NBRUP: OSPF neighbor 239.213.240.196
(ge-0/0/0.0) state changed from Init to ExStart due to Two way
communication established
Jan 20 18:24:56 RPD_OSPF_NBRUP: OSPF neighbor 239.213.240.193
(ge-0/0/0.0) state changed from Init to ExStart due to Two way
communication established
Jan 20 18:24:58 OSPF LSA rexmit
Jan 20 18:24:58 OSPF sent LSUpdate 239.213.240.199 -> 239.213.240.204
(ge-0/0/0.0, IFL 0x42)
Jan 20 18:24:58   Version 2, length 64, ID 133.213.96.3, area 0.0.0.0
Jan 20 18:24:58   checksum 0x0, authtype 0
Jan 20 18:24:58   adv count 1




>>-----Original Message-----
>>From: juniper-nsp-bounces at puck.nether.net 
>>[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Kirstin
>>Sent: Friday, January 20, 2006 3:26 AM
>>To: juniper-nsp at puck.nether.net
>>Subject: [j-nsp] OSPF problem
>>
>>Hello everybody,
>>
>>we are seeing a weird problem with our M10. Since yesterday 
>>OSPF doesn't seem to work anymore.
>>
>>
>>The router receives and accepts all routes from the other 
>>routers via OSPF but it doesn't import them into its routing-table.
>>
>>That means if we do a "show ospf database" we see all the 
>>existing routes. Doing a "show route" shows, that the 
>>routing-table contains only its own routes.
>>
>>I am pretty new to juniper so I might have missed an 
>>important thing in the configuration. The router is not 
>>really productive yet but it has been working very well for a 
>>couple of month.
>>
>>We are using Junos 7.2R1.7
>>
>>Any hints are greatly appreciated.
>>
>>Thank you for your time,
>>Kirstin
>>
>>
>>
>>Here is part of the config:
>>
>>show interfaces:
>>
>>ge-0/0/0 {
>>    description GB-LX-Karte;
>>    traceoptions {
>>        flag media;
>>        flag event;
>>    }
>>    vlan-tagging;
>>    mtu 1522;
>>    gigether-options {
>>        no-loopback;
>>        flow-control;
>>    }
>>    unit 0 {
>>        description "Mitglied HOS-Backbone";
>>        vlan-id 101;
>>        family inet {
>>            address 1.2.3.4/26;
>>        }
>>    }
>>fxp0 {
>>    unit 0 {
>>        family inet {
>>            address 5.6.7.8/27;
>>        }
>>    }
>>}
>>lo0 {
>>    unit 0 {
>>        family inet {
>>            address 9.10.11.12/32;
>>        }
>>    }
>>}
>>
>>##################################
>>
>>OSPF Config:
>>
>>root at juniper.rz2# show protocols ospf
>>export OSPF;
>>lsa-refresh-interval 30;
>>area 0.0.0.0 {
>>    authentication-type none;
>>    interface fxp0.0 {
>>        disable;
>>    }
>>    interface ge-0/0/0.0 {
>>        priority 1;
>>    }
>>      interface lo0.0;
>>}
>>
>>#################################
>>
>>root at juniper.rz2# show policy-options
>>
>>
>>policy-statement OSPF {
>>    term static-to-ospf {
>>        from protocol static;
>>        then accept;
>>    }
>>    term ospf-to-ospf {
>>        from protocol ospf;
>>        then accept;
>>    }
>>    term direct-to-ospf {
>>        from protocol direct;
>>        then accept;
>>    }
>>
>>
>>
>>
>>_______________________________________________
>>juniper-nsp mailing list juniper-nsp at puck.nether.net 
>>http://puck.nether.net/mailman/listinfo/juniper-nsp
>>
> 
> 
> 





More information about the juniper-nsp mailing list