You can add a static route for a destination subnet or host.

Procedure

  1. In the vSphere Client, navigate to Networking & Security > NSX Edges.
  2. Click an NSX Edge.
  3. Click Routing > Static Routes.
  4. Click Add.
  5. Enter the Network in CIDR notation.
  6. Enter the IP address of the Next Hop.
    The router must be able to reach the next hop directly. If ECMP is enabled, you can enter multiple next hops as a comma-separated list of IP addresses.
    • In NSX 6.4.4 or earlier, next hop is mandatory. Starting in NSX 6.4.5, next hop is optional for ESG. You can specify either the next hop or the interface. When you specify the next hop, interface is unavailable for selection, and conversely.
    • When multicast traffic is sent through a GRE tunnel interface on the ESG, you must specify the IP address of the remote GRE tunnel endpoint in the next hop when configuring the static routes.
    • For DLR and UDLR, next hop is mandatory.
  7. Select the Interface on which you want to add a static route.
    The Interface drop-down menu does not display the GRE tunnel interfaces.
  8. For MTU, edit the maximum transmission value for the data packets if necessary.
    The MTU cannot be higher than the MTU set on the NSX Edge interface.
  9. If prompted, enter the Admin Distance.
    Choose a value between 1 and 255. The admin distance is used to choose which route to use when there are multiple routes for a given network. The lower the admin distance, the higher the preference for the route.
    Table 1. Default Admin Distances
    Route Source Default admin distance
    Connected 0
    Static 1
    External BGP 20
    OSPF Intra-Area 30
    OSPF Inter-Area 110
    Internal BGP 200

    An administrative distance of 255 causes the static route to be excluded from the routing table (RIB) and the data plane, so the route is not used.

  10. (Optional) Enter the Locale ID.
    By default, routes have the same locale ID as the NSX Manager. The locale ID specified here associates the route with this locale ID. These routes are sent only to those hosts that have a matching locale ID. See Cross-vCenter NSX Topologies for more information.
  11. (Optional) Enter a Description for the static route.
  12. Click OK.