3com S7906E 설치 설명서

다운로드
페이지 2621
 
1-3 
Configure the IP addresses for related interfaces 
Configuration Procedure 
Follow these steps to configure a static route: 
To do… 
Use the command… 
Remarks 
Enter system view 
system-view 
— 
ip route-static dest-address mask | mask-length } 
next-hop-address | interface-type interface-number 
next-hop-address
 | vpn-instance 
d-vpn-instance-name next-hop-address } track 
track-entry-number preference preference-value 
tag tag-value ] [ description description-text 
Configure a static 
route 
ip route-static vpn-instance 
s-vpn-instance-name&<1-6> dest-address { mask | 
mask-length } { next-hop-address track 
track-entry-number public ] | interface-type 
interface-number next-hop-address | vpn-instance 
d-vpn-instance-name next-hop-address track 
track-entry-number } [ preference 
preference-value ] [ tag tag-value ] [ description 
description-text
 
Required 
By default, 
preference for 
static routes is 60, 
tag 
is 0, and no 
description 
information is 
configured. 
Configure the default 
preference for static 
routes 
ip route-static default-preference 
default-preference-value 
Optional 
60 by default 
 
 
When configuring a static route, the static route does not take effect if you specify the next hop 
address first and then configure it as the IP address of a local interface, such as VLAN interface.  
If you do not specify the preference when configuring a static route, the default preference will be 
used. Reconfiguring the default preference applies only to newly created static routes. 
You can flexibly control static routes by configuring tag values and using the tag values in the 
routing policy.  
If the destination IP address and mask are both configured as 0.0.0.0 with the ip route-static 
command, the route is the default route. 
For detailed information about track, refer to Track Configuration in the High Availability Volume.  
 
Configuring BFD for Static Routes 
Bidirectional forwarding detection (BFD) provides a general-purpose, standard, medium- and 
protocol-independent fast failure detection mechanism. It can uniformly and quickly detect the failures 
of the bidirectional forwarding paths between two routers for protocols, such as routing protocols and 
Multiprotocol Label Switching (MPLS). For details about BFD, refer to BFD Configuration in the High 
Availability Volume.