How to test NSX-T Appliance can access Internet via its uplink port

Modified on Wed, 3 Apr at 2:10 PM

SSH and login to the NSX-T CLI as the admin user


get logical-router


demo-nsxt-dc2> get logical-router
Wed Apr 03 2024 UTC 12:43:16.670
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      3       0/5000
f07e06d9-f134-4a21-ae8e-f5fe4e7c0127   1      1      SR-Tier0                          SERVICE_ROUTER_TIER0        6       1/20000


get logical-router <ROUTER_UUID> forwarding



demo-nsxt-dc2> get logical-router  f07e06d9-f134-4a21-ae8e-f5fe4e7c0127 forwarding
Wed Apr 03 2024 UTC 12:46:49.314
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
f07e06d9-f134-4a21-ae8e-f5fe4e7c0127   1      1      SR-Tier0                          SERVICE_ROUTER_TIER0
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          192.168.100.254                           route       fc3138a8-3caf-480e-b82c-4098290b57f5   00:50:56:8f:8c:82
127.0.0.1/32                                                 route       5e6c354a-f06d-4b1a-81f5-6782155382db
169.254.64.1/32                                              route       809350de-e7a0-4da8-b6f0-c0d1a5e6f475
169.254.64.2/32                                              route       3f27984d-3572-55b3-8baa-3cc44e9be7bd
192.168.100.0/24                                             route       fc3138a8-3caf-480e-b82c-4098290b57f5
192.168.100.200/32                                           route       725f8646-0d1b-5733-8e63-eac78b4186f6
192.168.222.0/24                                             route       809350de-e7a0-4da8-b6f0-c0d1a5e6f475
192.168.222.2/32                                             route       725f8646-0d1b-5733-8e63-eac78b4186f6



ping <GATEWAY_IP> source <EDGE_TEP_IP> vrfid <TUNNEL_VRF_ID> dfbit enable repeat 5


Confirm the uplink port can ping its default gateway


demo-nsxt-dc2> ping 192.168.100.254 source 192.168.100.200 vrfid 1 dfbit enable repeat 5
PING 192.168.100.254 (192.168.100.254) from 192.168.100.200: 56 data bytes
64 bytes from 192.168.100.254: icmp_seq=0 ttl=64 time=2.450 ms
64 bytes from 192.168.100.254: icmp_seq=1 ttl=64 time=2.126 ms
64 bytes from 192.168.100.254: icmp_seq=2 ttl=64 time=2.340 ms
64 bytes from 192.168.100.254: icmp_seq=3 ttl=64 time=1.865 ms
64 bytes from 192.168.100.254: icmp_seq=4 ttl=64 time=1.545 ms


--- 192.168.100.254 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.545/2.065/2.450/0.328 ms


confirm the uplink port can ping the Internet (using Google name server 8.8.8.8)


demo-nsxt-dc2> ping 8.8.8.8 source 192.168.100.200 vrfid 1 dfbit enable repeat 5
PING 8.8.8.8 (8.8.8.8) from 192.168.100.200: 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=5.743 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=5.513 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=4.180 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=5.022 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=4.145 ms


--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.145/4.921/5.743/0.661 ms



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article