When a tier-1 logical router advertises routes to a tier-0 logical router, the routes are listed in the tier-0 router's routing table as NSX static routes.
Procedure
- On the NSX Edge, run the get logical-routers command to find the VRF number of the tier-0 service router.
nsx-edge-1> get logical-routers Logical Router UUID : 736a80e3-23f6-5a2d-81d6-bbefb2786666 vrf : 0 type : TUNNEL Logical Router UUID : 421a2d0d-f423-46f1-93a1-2f9e366176c8 vrf : 5 type : SERVICE_ROUTER_TIER0 Logical Router UUID : f3ce9d7d-7123-47d6-aba6-45cf1388ca7b vrf : 6 type : DISTRIBUTED_ROUTER Logical Router UUID : c8e64eff-02b2-4462-94ff-89f3788f1a61 vrf : 7 type : SERVICE_ROUTER_TIER1 Logical Router UUID : fb6c3f1f-599f-4421-af8a-99692dff3dd4 vrf : 8 type : DISTRIBUTED_ROUTER
- Run the vrf <number> command to enter the tier-0 service router context.
nsx-edge-1> vrf 5 nsx-edge1(tier0_sr)>
- On the tier-0 service router, run the get route command and make sure the expected routes appear in the routing table.
Notice that the NSX static routes (ns) are learned by the tier-0 router because the tier-1 router is advertising routes.
nsx-edge1(tier0_sr)> get route Flags: c - connected, s - static, b - BGP, ns - nsx_static nc - nsx_connected, rl - router_link, t0n: Tier0-NAT, t1n: Tier1-NAT Total number of routes: 7 b 10.10.10.0/24 [20/0] via 192.168.100.254 rl 100.91.176.0/31 [0/0] via 169.254.0.1 c 169.254.0.0/28 [0/0] via 169.254.0.2 ns 172.16.10.0/24 [3/3] via 169.254.0.1 ns 172.16.20.0/24 [3/3] via 169.254.0.1 c 192.168.100.0/24 [0/0] via 192.168.100.2