Troubleshooting the Floating IP Address Pool in Contrail

https://techwiki.juniper.net/Documentation/Contrail/Contrail_Common_Support_Answers/Troubleshooting_the_Floating_IP_Address_Pool_in_Contrail

vRouter Command Line Utilities:
https://techwiki.juniper.net/Documentation/Contrail/Contrail_Controller_Feature_Guide/Optimizing_Contrail/vRouter_Command_Line_Utilities

1)
Create a virtual network (public) from contrail ui with following infos

Virtual network name:         public
subnet 10.204.219.0/24
Public addresses range:     10.204.219.32 to 10.204.219.37
Route Target:                      64512:10003
Floating IP pool name:         public_pool

2)
Create another virtual network (private) from contrail ui with following infos
Virtual network name:         vn1
Subnet:                                10.1.1.0/24

3)
Create a virtual machine in the virtual network VN1 with the name VN1_VM1 and with the IP address 10.1.1.253 from openstack ui.

4)
Allocate a floating ip from contrail ui
https://192.168.56.102:8143/#p=config_net_fip

A floating IP address of 10.204.219.37 is associated to the VN1_VM1 instance from openstack UI.

5)
You can see that, a router is configured in following conrail ui
https://192.168.56.102:8143/#p=config_infra_bgp

6)
Create an another vm "vm_pub" in "public" network from openstack ui.

7)
SSH to "vm_pub" using its link local address and ping/ssh to public ip of VM "VN1_VM1", this should work.

8)
View the BGP Peer Status on the Control Node
Using Contrail U
https://192.168.56.102:8143/#p=mon_infra_control&q[tab]=peers&q[node]=ubuntu

Using the control-node introspect
http://192.168.56.102:8083/Snh_BgpNeighborReq?ip_address=&domain=

9)
Query Routes in the Public Virtual Network named "public"
Using Contrail U
https://192.168.56.102:8143/#p=mon_infra_control&q[tab]=routes&q[node]=ubuntu

Using the control-node introspect
http://192.168.56.102:8083/Snh_ShowRouteReq?x=default-domain:admin:public:public.inet.0

10)
Query Routes in the Private Virtual Network named "vn1"
Using Contrail U
https://192.168.56.102:8143/#p=mon_infra_control&q[tab]=routes&q[node]=ubuntu

Using the control-node introspect
http://192.168.56.102:8083/Snh_ShowRouteReq?x=default-domain:admin:vn1:vn1.inet.0

11)
View Corresponding BGP L3VPN Routes
Using Contrail U
https://192.168.56.102:8143/#p=mon_infra_control&q[tab]=routes&q[node]=ubuntu

Using the control-node introspect
http://192.168.56.102:8083/Snh_ShowRouteReq?x=bgp.l3vpn.0

12)
View Routing Instance Next Hops
Using Contrail UI
https://192.168.56.102:8143/#p=mon_infra_vrouter&q[tab]=routes&q[node]=ubuntu
Alternatively, from the agent introspect.
http://192.168.56.102:8085/Snh_VrfListReq?x=default-domain:admin:public:public

13)
Next, perform a route request query on ucindex 2, as shown in the following. The tunnel detail indicates the source and destination endpoints of the tunnel and the MPLS label 16 (the label of the virtual machine).
The query should also show a route for 10.204.219.37 with an interface next hop of tap-interface.
From the agent introspect.
http://192.168.56.102:8085/Snh_Inet4UcRouteReq?x=2

14)
Getting Details of the tap-interface
Using Contrail UI
https://192.168.56.102:8143/#p=mon_infra_vrouter&q[tab]=interfaces&q[node]=ubuntu

Alternatively, from the agent introspect.
http://192.168.56.102:8085/Snh_ItfReq?x=tap118cdbd5-60

15)
Advanced Troubleshooting

a)
Check to see if  any packet drops occur in the kernel vrouter module:
From the agent introspect.
http://192.168.56.102:8085/Snh_KDropStatsReq?