24
no set vpnv4 next-hop [<ip_addr>]
Function:
Configure the next-hop of BGP VPNv4 routing message. The “
no set vpnv4
next-hop [<ip_addr>]
” command deletes the configuration.
Parameter: <ip_addr>
is the next-hop ip address of VPNv4 route shown by dotted decimal
notation.
Command Mode:
route-map mode
Usage Guide:
To use this command, one match clause should at first be defined.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set vpnv4 next-hop 10.1.1.1
1.2.3.27 set weight
Command: set weight <weight_val>
no set weight [<weight_val>]
Function:
Configure the weight value of BGP routing message. The “
no set weight
[<weight_val>]
” command deletes this configuration.
Parameter: <weight_val>
is weight value, ranging between 0
～
4294967295
Command Mode:
route-map mode
Usage Guide:
Weight value is adopted to facilitate the best path option and validates only within
the local switch. While there are several route to the same destination the one with higher priority
is more preferred. To use this command, one match clause should at first be defined.
Example:
Switch#config terminal
Switch(config)#route-map r1 permit 5
Switch(config-route-map)#set weight 60
1.2.4 Configuration Examples
The figure below shows a network consisting of four Layer 3 switches. This example
demonstrates how to set the BGP as-path properties through route-map. BGP protocol is applied
among the Layer 3 switches. As for switchC, the network 192.68.11.0/24 can be reached
through two paths in which one is AS-PATH 1 by IBGP (going through SwitchD), the other one is
AS-PATH 2 by EBGP (going through SwitchB). BGP selects the shortest path, so AS-PATH 1 is
the preferred path. If the path 2 is wished, which is through EBGP path, we can add two extra AS
path numbers into the AS-PATH messages from SwitchA to SwitchD so as to change the
determination SwitchC take to 192.68.11.0/24.