Usage Scenario
On a simple network, static routes alone can ensure that the network runs properly. If theDevice cannot run dynamic routing protocols to generate routes to the destination, configure static routes on the Device.
After recursive-lookup host-route is configured, static routes can recurse only to 32-bit host routes.
In network maintenance scenarios, static routes are required to verify services. If you do not want these static routes to be imported by other protocols, specify no-advertise to prevent these static routes from being advertised.
no-advertise takes effect only when it is configured for all the active static routes with the same destination address and mask.
You can configure description description-text to configure a description for static routes so that the administrator can check and maintain static routes easily. To check the configured description, run the display this or
display current-configuration command in the system view.
Precautions
When configuring unicast static routes in a topology instance, note the following points:
- The default priority of a static route is 60.
- When deleting a route, you can specify preference, tag, or description. The parameters, however, are not displayed in the command line help.
- When both the destination IP address and the mask are 0.0.0.0, the configured route is a default route. If no matching route is available in the routing table, the default route is used for packet forwarding.
- Setting different priorities can implement different RM policies. For example, if the same priority is configured for multiple routes to the same destination, load balancing can be implemented. If different priorities are configured for multiple routes to the same destination, route backup can be implemented.
- When configuring static routes, you can specify outbound interfaces or next hop addresses as required. You can specify outbound interfaces or next hop addresses for the interfaces that support resolution from network addresses to link layer addresses or P2P interfaces, excluding NBMA interfaces that support P2MP, such as the interfaces that use X.25 for encapsulation and dialling interfaces. At the link layer, both IP addresses and slave routes must be configured. Specifically, IP addresses must be mapped to link layer addresses using the dialer map ip, x.25 map ip, or frame-relay map ip command. In this case, when configuring static routes, you can specify only next hop addresses rather than outbound interfaces.
- If the outbound interface is a non-P2P interface, a next hop address is required.
- In some cases, for example, the link layer is encapsulated with PPP, you can also specify outbound interfaces even if the remote address is unknown. In this manner, you do not need to modify thedevice configuration if the remote address changes.