Verify the Static Route on a Tier-0 Router

Use the CLI to verify that the static route is connected. You must also verify the external router can ping the internal VMs and the internal VMs can ping the external router.

Prerequisites

Verify that a static route is configured. See Configure a Static Route in Manager Mode.

Procedure

1. Log in to the NSX Manager CLI.
2. Confirm the static route.
   1. Get the service router UUID information.
      get logical-routers

      nsx-edge1> get logical-routers
      Logical Router
      UUID        : 736a80e3-23f6-5a2d-81d6-bbefb2786666
      vrf         : 2
      type        : TUNNEL
      
      Logical Router
      UUID        : d40bbfa4-3e3d-4178-8615-6f42ea335037
      vrf         : 4
      type        : SERVICE_ROUTER_TIER0
      
      Logical Router
      UUID        : d0289ba4-250e-41b4-8ffc-7cab4a46c3e4
      vrf         : 5
      type        : DISTRIBUTED_ROUTER
      
      Logical Router
      UUID        : a6ee6316-2212-4171-99cc-930c98bcad7f
      vrf         : 6
      type        : DISTRIBUTED_ROUTER
      

   2. Locate the UUID information from the output.

      Logical Router
      UUID        : d40bbfa4-3e3d-4178-8615-6f42ea335037
      vrf         : 4
      type        : SERVICE_ROUTER_TIER0
      

   3. Verify that the static route works.
      get logical-router d40bbfa4-3e3d-4178-8615-6f42ea335037 route static

      Flags: c - connected, s - static, b - BGP, ns - nsx_static
      nc - nsx_connected, rl - router_link, t0n: Tier0-NAT, t1n: Tier1-NAT
      
      s    10.10.10.0/24        [1/1]         via 192.168.100.254
      rl   100.64.1.0/31        [0/0]         via 169.0.0.1
      ns   172.16.10.0/24       [3/3]         via 169.0.0.1
      ns   172.16.20.0/24       [3/3]         via 169.0.0.1
      

3. From the external router, ping the internal VMs to confirm that they are reachable through the NSX-T Data Center overlay.
   1. Connect to the external router.
      ping 172.16.10.10

                                                  
      PING 172.16.10.10 (172.16.10.10) 56(84) bytes of data.
      64 bytes from 172.16.10.10: icmp_req=1 ttl=62 time=127 ms
      64 bytes from 172.16.10.10: icmp_req=2 ttl=62 time=1.96 ms
      ^C
      --- 172.16.10.10 ping statistics ---
      2 packets transmitted, 2 received, 0% packet loss, time 1001ms
      rtt min/avg/max/mdev = 1.966/64.793/127.620/62.827 ms
      

   2. Test the network connectivity.
      traceroute 172.16.10.10

       
      traceroute to 172.16.10.10 (172.16.10.10), 30 hops max, 60 byte packets
       1  192.168.100.3 (192.168.100.3)  0.640 ms  0.575 ms  0.696 ms
       2  100.64.1.1 (100.64.1.1)  0.656 ms  0.604 ms  0.578 ms
       3  172.16.10.10 (172.16.10.10)  3.397 ms  3.703 ms  3.790 ms
      
      

4. From the VMs, ping the external IP address.
   ping 10.10.10.10

   PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
   64 bytes from 10.10.10.10: icmp_req=1 ttl=62 time=119 ms
   64 bytes from 10.10.10.10: icmp_req=2 ttl=62 time=1.93 ms
   ^C
   --- 10.10.10.10 ping statistics ---
   2 packets transmitted, 2 received, 0% packet loss, time 1001ms
   rtt min/avg/max/mdev = 1.936/60.865/119.795/58.930 ms