Comment 2 for bug 1751124

Hari,

I have a setup in problem state

1. one compute in 4.1 - 10.88.0.81/24
2. second compute in 4.0.2 - 10.88.0.82/24

Internal network VIP = 10.88.0.20/24

The compute (4.0.2) is able to ping the VIP - 10.88.0.20 even when the IP statement is commented out in contrail-vrouter-agent.conf

whereas the compute node ( 4.1 ) is not able to ping the VIP - 10.88.0.20 when the IP statement is commented out in the contrail-vrouter-agent.conf

What we found is that when the

nh --get shows that for 4.1 ( when the IP statement is commented out) - type = drop
where as
for 4.0.2 - the type is resolve .

Please see Kiran's findings :

In the working case, nh for the local ip is receive nh.
But in the non working case, the nh is drop.
You may need to check with Hari why the behavior changed.

Non-working:
[root@overcloud-contraildpdk-1 ~]# rt --get 10.88.0.81/32 --vrf 0
Match 10.88.0.81/32 in vRouter inet4 table 0/0/unicast

Flags: L=Label Valid, P=Proxy ARP, T=Trap ARP, F=Flood ARP
vRouter inet4 routing table 0/0/unicast
Destination PPL Flags Label Nexthop Stitched MAC(Index)
0.0.0.0/0 0 T - 1 -
[root@overcloud-contraildpdk-1 ~]# nh --get 1
Id:1 Type:Drop Fmly: AF_INET Rid:0 Ref_cnt:1278 Vrf:0
              Flags:Valid, Etree Root,

Working:
[root@overcloud-contraildpdk-1 ~]# rt --get 10.88.0.81/32 --vrf 0
Match 10.88.0.81/32 in vRouter inet4 table 0/0/unicast

Flags: L=Label Valid, P=Proxy ARP, T=Trap ARP, F=Flood ARP
vRouter inet4 routing table 0/0/unicast
Destination PPL Flags Label Nexthop Stitched MAC(Index)
10.88.0.81/32 0 T - 9 -
[root@overcloud-contraildpdk-1 ~]# nh --get 9
Id:9 Type:Receive Fmly: AF_INET Rid:0 Ref_cnt:4 Vrf:1
              Flags:Valid, Policy(R), Etree Root,
              Oif:1