[c-nsp] OSPF interoperability with ME6524 and RS15800

[Hiromasa Sekiguchi]

Hello,

Thank you for your e-mail.

This phenomenon could reproduce in our lab.

> What is the output of the commands:
> RS15800# show ip ospf retransmission-list GE0/0/4
> ME6524# show ip ospf retransmission-list Ge1/25

We try to get the above in our lab.

> If you have 2 links with equal cost then the traffic is load-balanced.
> What do you meen by "then, we have no works" ?  If you have problems
> with one link you still must have OSPF neighbors in FULL state on the
> operational one?
>
> What is the output of the commands:
> RS15800#sh ip ospf neighbor
> when you have problems ?

The OSPF status is still FULL.
It doesn't changed.

> Did you try to eliminate layer 1 issues ? Change patch cords, modules or
> switch ports ? Did you see any errors on this ports ?
>
> What is the output of the commands:
> RS15800#sh int GE0/0/4 | i err
> ME6524#sh int Ge1/25 | i err

We checked our lab and custoemr network, there were no layer 1 issues.

> Just currious: did you use MPLS traffic on this links ?

No.

+--------+GE1/25        GE0/0/4+---------+GE0/0/0
| ME6524 |=====================| RS15800 |----------
+--------+GE1/26        GE0/0/5+---------+
          <------- OSPF ------->          <---- MPLS cloud

           Area 0.0.0.1 ------->          <---- Area 0.0.0.0

The two links don't use MPLS-TE and OSPF-TE.
The RS15800 work OSPF ABR between area 0.0.0.0 and 0.0.0.1 .

The uplink of RS15800(GE0/0/0) use MPLS-TE and OSPF-TE.

Regards,
Hiromasa

Liviu Pislaru wrote:
> hello,
> 
> OSPF must send acknowledgment of each newly received link-state 
> advertisement (LSA). It does this by sending LSA packets. LSAs are 
> retransmitted until they are acknowledged. The link-state retransmit 
> interval defines the time between retransmissions. The default interval 
> in 5 seconds. Did  you use the command "ip ospf retransmit-interval" to 
> modifie the default value of 5 seconds ?
> 
> What is the output of the commands:
> RS15800# show ip ospf retransmission-list GE0/0/4
> ME6524# show ip ospf retransmission-list Ge1/25
> 
> If you have 2 links with equal cost then the traffic is load-balanced. 
> What do you meen by "then, we have no works" ?  If you have problems 
> with one link you still must have OSPF neighbors in FULL state on the 
> operational one?
> 
> What is the output of the commands:
> RS15800#sh ip ospf neighbor
> when you have problems ?
> 
> Did you try to eliminate layer 1 issues ? Change patch cords, modules or 
> switch ports ? Did you see any errors on this ports ?
> 
> What is the output of the commands:
> RS15800#sh int GE0/0/4 | i err
> ME6524#sh int Ge1/25 | i err
> 
> Just currious: did you use MPLS traffic on this links ?
> 
> -- 
> liviu.
> 
> ----- Original Message ----- From: "Hiromasa Sekiguchi" 
> <hiromasa.sekiguchi at ctc-g.co.jp>
> To: <cisco-nsp at puck.nether.net>
> Sent: Friday, April 06, 2007 4:33 AM
> Subject: [c-nsp] OSPF interoperability with ME6524 and RS15800
> 
> 
>> Hello,
>>
>> We have some problems about OSPF connection between ME6524 and RS15800.
>>
>> +--------+GE1/25        GE0/0/4+---------+
>> | ME6524 |=====================| RS15800 |
>> +--------+GE1/26        GE0/0/5+---------+
>>
>> They have about 700 OSPF routes.
>> The ME6524 has two links of cost 10(ECMP to RS15800).
>>
>> Sometimes, many OSPF retransmit traps was generate from RS15800.
>> It was generate only between GE1/25 and GE0/0/4.
>> Then, we have no works...
>>
>> If it is interoperability issue, are there any similar phenomenon?
>> What is the cause of this phenomenon?
>>
>> Please help us!!
>>
>> Regards,
>> Hiromasa
>>
> 
> 
> -------------------------------------------------------------------------------- 
> 
> 
> 
>> _______________________________________________
>> 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/ 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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/