What is the Purpose of This Test
IPv6 Route Table Dump command lists the complete Routing table in IPv6.
When Can You Run This Test
Run this test if you want to verify the Route in the FIB table of IPv6. You can run the test by specifying any of the following options:
- Segment - Select the segment for which routes must be displayed. Select "all" for all segments.
- Prefix - Specify a particular prefix for which routes must be displayed.
- Routes - Select any of the following options from the drop-down menu:
- all - Display all the routes for every prefix.
- preferred - Display the most preferred route alone for every prefix (this is the route being used for data forwarding).
For instructions on how to run a remote diagnostic test on Edges, see Run Remote Diagnostic Tests on Edges.
Note: The Route Table Dump command output has a limit of 16000 routes.
What to Check in the Test Output
Following is an example of the test output:
The Remote Diagnostics output displays the following information:
| Field | Description |
|---|---|
| Address | Specifies the IPv6 Routes available in the table. |
| Segment | Specifies the segment in which the Routes are available and handled by the Edge. |
| Netmask | Specifies the range of addresses in IPv6. |
| Type | Specifies the Route type, such as Cloud, Edge2Edge, any (Underlay or Connected), and so on. |
| Cost | Specifies the Route Cost or Metric used in selection of Route criteria. |
| Reachable | Specifies the Status of the Route:
|
| Next Hop | Indicates the local exit interface in case of local routes. In case of overlay/remote routes, it indicates the type of next hop. For example, "Cloud gateway" in case of cloud routes, "Cloud VPN" in case of datacenter, or "edge to edge" routes etc., |
| Next Hop Name | Specifies the name of the next hop device. |
| Destination Name | Specifies the name of the destination device. |
| Lost Reason | Specifies the codes for different reasons for the routes being lost to next preferred route on the Edge. |
| (Not) Reachable Reason | Specifies the reason for the route being reachable or not reachable. |
Note: An unresolved route, learnt over multi-hop BGP, might point to an intermediate interface.
The following table lists the reason codes and the corresponding description:
| Reason Code | Description |
|---|---|
| PR_UNREACHABLE | In case of overlay routes, the remote peer, which is either Gateway or Edge, is not reachable. |
| IF_DOWN | Egress Interface is down. |
| INVALID_IFIDX | Egress Interface if-index for this route is invalid. |
| SLA_STATE_DOWN | State given by IP SLA tracking is down. |
| HA_STANDBY | When the local Edge is a Standby, all routes synced from the active are marked as reachable for operational convenience. |
| LOCAL_MGMT | Management routes are always reachable. |
| LOOPBACK | Loopback IP address is always reachable. |
| SELF_ROUTE | Self IP routes are always reachable. |
| RECUR_UNRES | Recursive routes are marked as reachable so that recursive resolution can be done for operational convenience. |
| VPN_VIA_NAT | vpnViaNat routes are always reachable. |
| SLA_STATE_UP | State given by IP SLA tracking is up. |
| IF_RESOLVED | Egress interface is up and resolved. |
| PR_REACHABLE | In case of overlay routes, the remote peer, which is either Gateway or Edge, is reachable. |
