This section describes how to verify the floating IP on an MX Series router and a virtual router.
The floating IP verification process is as follows:
To verify a route propagation on the vMX/vSRX routers:
Note
Use the Junos CLI during the verification procedure.
Log in to the vsrx1
router.
Run the following command:
root@vsrx1> run show route table public.inet.0
Example of system response:
public.inet.0: 8 destinations, 13 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0.0.0.0/0 *[Static/5] 4w6d 22:49:22
> to 172.17.32.193 via ge-0/0/0.0
172.17.32.192/26 *[Direct/0] 4w6d 22:49:22
> via ge-0/0/0.0
172.17.32.240/32 *[Local/0] 4w6d 22:49:22
Local via ge-0/0/0.0
<floating_ip0>/32 *[BGP/170] 4w3d 00:41:07, MED 100, localpref 200, from 10.167.4.22
AS path: ?
> via gr-0/0/0.32769, Push 40
[BGP/170] 3w3d 00:30:48, MED 100, localpref 200, from 10.167.4.23
AS path: ?
> via gr-0/0/0.32769, Push 40
In the output of the previous command, find the floating IP address that you want to debug.
Run the following command to output details of the floating IP in question. For example:
root@vsrx1> show route <floating_ip0>/32 detail
Ping the floating IP in question using the following command:
root@vsrx1> ping <floating_ip0> routing-instance public count 10
To check a route exchange on the Mirantis OpenContrail controller nodes:
Validate the presence of the routing instance for each virtual network in the following sample system:
http://<ntw_node_vip>:8083/Snh_ShowRoutingInstanceReq?name=
Using the link from the previous step, find public network with floating IP pool.
Using the same link, find and click the public:inet.0
table.
On the opened page, find and click a floating IP that you want to check. For example:
For a detailed MX troubleshooting procedure, see: Troubleshoot the vMX router.
To verify forward and reverse flow on a vRouter
The OpenContrail vRouter is located on the compute cmp
nodes.
Use the following steps to troubleshoot the OpenContrail user issues
related to service chaining, communication issues between virtual machines,
between two virtual networks, and so on.
Log in to any compute node of your MCP cluster. For example, cmp002
.
Run the following command:
flow -l | grep '<floating_ip>\|192.168.0.100'
Example of system response:
Index Source:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------
492152<=>1500364 <floating_ip>:792 1 (5)
192.168.0.100:0
(Gen: 1, K(nh):83, Action:F, Flags:, QOS:-1, S(nh):83, Stats:487/519142,
1500364<=>492152 192.168.0.100:792 1 (5)
<floating_ip>:0
(Gen: 1, K(nh):83, Action:F, Flags:, QOS:-1, S(nh):35, Stats:487/519142,
For a detailed forward and reverse flow troubleshooting procedure, see: Troubleshoot a VM forward and reverse flow.