In this section:
The staticRoute
object is used to configure static IP routes for the IP interfaces. A static route indicates the nextHop gateway and IP interface that is used for a particular peer network IP prefix.
A route preference
may be configured for static routes as shown in the command syntax. The lower the preference value, the more likely the route is to be used.
The SBC 52x0 and SBC 7000 systems support creating IP Interface Groups containing sets of IP interfaces that are not "processor friendly" (i.e. carried on physical Ethernet ports served by separate processors). However, restrictions exist regarding the usage of such Interface Groups.
(This ability does not apply to the SBC 51x0 and SBC 5400 systems which have only two physical media ports. IP interfaces from the two physical ports may be configured within the same IP Interface Groups without restriction.)
For complete details, refer to Configuring IP Interface Groups and Interfaces.
% set addressContext <addressContext_name> staticRoute <destinationIpAddress> <ip_prefix_length> <nextHopIPaddress> <ipInterfaceGroupName> <ipInterfaceName> condition ceName (node name) preference <100-2147483647> % show addressContext <addressContext_name> staticRoute % delete addressContext <addressContext> staticRoute <IpAddress>
To display static routes:
% show addressContext default staticRoute staticRoute 10.6.30.105 32 10.34.26.1 LIF2 lif_eth3 { preference 10; } staticRoute 10.34.9.70 32 10.34.25.1 LIF1 lif_eth2 { preference 10; } staticRoute 10.34.9.95 32 10.34.26.1 LIF2 lif_eth3 { preference 10; } staticRoute 10.34.13.194 32 10.34.25.1 LIF1 lif_eth2 { preference 1; } staticRoute 10.34.13.195 32 10.34.26.1 LIF2 lif_eth3 { preference 10;
The staticRoute
object is used to configure static IP routes for the management interfaces. A static route indicates the nextHop gateway and management interface that is used for a particular peer network IP prefix.