Analytics-underlay:Prouter uve showing vrouter not directly connected to the prouter

[Sandip Dey]

Logs saved at :http://10.204.216.50/Docs/bugs/<bug-id>

Hi Raj

I removed the loops .Still nodek9 showing connected to qfx7 on iccp link.

{
PRouterFlowEntry: {
flow_export_source_ip: "40.44.1.1"
},
PRouterLinkEntry: {
link_table: [
{
remote_interface_name: "ge-0/0/41.0",
local_interface_name: "ge-0/0/47",
remote_interface_index: 585,
local_interface_index: 522,
type: 1,
remote_system_name: "bng-contrail-ex4200-2"
},
{
remote_interface_name: "ge-0/0/28",
local_interface_name: "ge-0/0/28",
remote_interface_index: 524,
local_interface_index: 558,
type: 1,
remote_system_name: "bng-contrail-qfx51-8"
},
{
remote_interface_name: "vlan4001",
local_interface_name: "ae1",
remote_interface_index: 1,
local_interface_index: 561,
type: 2,
remote_system_name: "nodek10"
},
{
remote_interface_name: "vlan4000",
local_interface_name: "ae0",
remote_interface_index: 1,
local_interface_index: 560,
type: 2,
remote_system_name: "nodek9"
},
{
remote_interface_name: "vlan4000",
local_interface_name: "ae2",
remote_interface_index: 1,
local_interface_index: 563,
type: 2,
remote_system_name: "nodek8"
}
]
},
Regards
Sandip

From: Raj Reddy <email address hidden>
Date: Friday, May 22, 2015 5:34 AM
To: Sandip Dey <email address hidden>
Cc: Ted Ghose <email address hidden>, Nagabhushana R <email address hidden>, Biswajit Mandal <email address hidden>
Subject: Re: Prouter uve showing wrong info

Hi Sandip:

Do you have physical loops on the QFX boxes? If so, you will have to disable lldp on those interfaces,
otherwise we will see some issues as below..

thanks,
-
Raj

On May 20, 2015, at 9:52 PM, Rajashekar Reddy <email address hidden> wrote:

Is there a physical loop on any of the systems?
I see bng-contrail-qfx51-7 itself showing up 5, 6 times..

Can you please check the lldp neighbor info in the corresponding boxes..

FYI, Ted is on PTO this week, you may get delayed response.

thanks,
-
Raj

On May 20, 2015, at 2:22 AM, Sandip Dey <email address hidden> wrote:

Hi Ted

Please see my attached topology.

Nodek9 is connected to qfx8 , but its showing as connected to qfx7.

Could you take a look at http://nodeg25:8081/analytics/uves/prouter/bng-contrail-qfx51-7?flat

{
remote_interface_name: "vlan4000",
local_interface_name: "ae0",
remote_interface_index: 1,
local_interface_index: 560,
type: 2,
remote_system_name: "nodek9"
},

Regards
Sandip

[Raj Reddy (rajreddy)]

This is a special case of L2 extending beyond one TOR.. In this case if a server is not connect to both MC-LAG routers, it will be 'learned' on the iccp link and shows up as neighbor to the non-connected box also.. we will see if we can ignore entries learned on iccp link during neighbor determination

[Raj Reddy (rajreddy)]

It will be very corner case where the servers are connected to only one TOR in the MC-LAG case, we have decided to live with this limitation (bug) for now.