cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2428
Views
0
Helpful
3
Replies

ODL couldn't correctly update the topology for ASR9K link. In day 1, the topology of ASR9k was ok. But in Day 2, the link of ASR9k changed, but ODL couldn't get the link info correctly

yingchua
Level 1
Level 1

ODL couldn't correctly update the topology for ASR9K link. In day 1, the topology of ASR9k  was ok. But in Day 2, the link of ASR9k changed, but ODL couldn't get the link info correctly. So far, ODL can connect ASR9K. What's the possible reason for this topology issue?

1 Accepted Solution

Accepted Solutions

Hi Xing,

sorry for the delay in responding

Beryllium-SR2 is pretty old, as is XR6.0.2.   It might be worth looking at upgrading the customer to Boron-SR4 or Carbon-SR1 and XR 6.1.4 or 6.2.2.

Giles

View solution in original post

3 Replies 3

giheron
Cisco Employee
Cisco Employee

hi, are you talking about linkstate topology?

and which versions of XR and ODL are you using?

Hello Giles Heron,

Million thanks for your helping us. I am Xing from Cisco China Local AS team, we have a local customer Sinopac, they are using the ODL. and they have the issue that ODL couldn't get the link updated correctly. Yingchun Huang is the PM of this Project.

And the XR version is XR6.0.2, and the ODL version is distribution-karaf-0.4.2-Beryllium-SR2.

Hope to get your advice.

Thanks Again!

Hi Xing,

sorry for the delay in responding

Beryllium-SR2 is pretty old, as is XR6.0.2.   It might be worth looking at upgrading the customer to Boron-SR4 or Carbon-SR1 and XR 6.1.4 or 6.2.2.

Giles

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: