- set-attached-bit
- set as-path
- set comm-list delete
- set community
- set distance (bgp)
- set distance
- set extcommunity
- set extcommunity cost
- set extcomm-list delete
- set extcommunity rt
- set forwarding-address
- set interface
- set ip address prefix-list
- set ip default next-hop
- set ip next-hop
- set ip precedence
- set ipv6 address prefix-list
- set ipv6 default next-hop
- set ipv6 next-hop
- set ipv6 precedence
- set level
- set local-preference
- set metric
- set metric-type
- set nssa-only
- set origin
- set path-selection all advertise
- set tag
- set vrf
- set weight
- shutdown (BGP)
- shutdown (EIGRP)
- shutdown (IS-IS)
- shutdown (OSPF)
- shutdown (OSPFv3)
- shutdown (VRRP)
- spf-interval
- stub
- summary-address
- summary-address (OSPF)
- summary-address (OSPFv3)
- suppress-inactive
S Commands
This chapter describes the Cisco NX-OS unicast routing commands that begin with the letter S, except for the show commands.
set-attached-bit
To set the attached (ATT) bit for Intermediate-System-to-Intermediate System (IS-IS), use the set-attached-bit command. To disable this function, use the no form of this command.
Syntax Description
Defaults
Command Modes
Router configuration
VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the set-attached-bit command to configure whether to use a Level 1/Level 2 IS-IS router as the default router for Level 1 routers in the same area. If the set-attached-bi t command is disabled, the attached-bit will not be advertised by the router in its Level 1 Link-State Packet (LSP), and other Level 1 routers in the area will not use this router as the default router outside the area.
Examples
This example shows how to unset the attached bit:
Related Commands
|
|
|
|---|---|
set as-path
To modify an autonomous system path (as-path) for Border Gateway Protocol (BGP) routes, use the set as-path command. To not modify the autonomous system (AS) path, use the no form of this command.
set as-path { tag | { prepend as-num [ ... as-num ] | last-as num }}
no as-path { tag | { prepend as-num [.. . as-num ] | last-as num }}
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
You must enter the feature pbr command to enable policy-based routing (PBR) before entering the route-map command.
Use the route-map command to enter route-map configuration mode. Once you enter the route-map command, the prompt changes to the following:
switch(config-route-map)#
Once you enter route-map configuration mode, you can enter the set command.
The only global BGP metric available to influence the best-path selection is the autonomous system path length. By varying the length of the autonomous system path, a BGP speaker can influence the best-path selection by a peer further away.
By allowing you to convert the tag into an autonomous system path, the set as-path tag variation of this command modifies the autonomous system length. The set as-path prepend variation allows you to prepend an arbitrary autonomous system path string to BGP routes. Usually, the local autonomous system number is prepended multiple times which increasing the autonomous system path length.
Examples
This example shows how to converts the tag of a redistributed route into an autonomous system path:
switch(config)# route-map test1
switch(config-route-map)# set as-path tag
This example shows how to prepend 100 to all the routes advertised to 10.108.1.1:
switch(config)# route-map test1
switch(config-route-map)# match as-path 1
switch(config-route-map)# set as-path prepend 100
switch(config)# router bgp 64496
switch(config-router)# neighbor 10.108.1.1 remote-as 64497
switch(config-router-neighbor)# address-family ipv4 unicast
switch(config-router-neighbor-af)# route-map set-as-path test1 out
Related Commands
set comm-list delete
To remove communities from the community attribute of an inbound or outbound update, use the set comm-list delete command. To remove a previous set comm-list delete command, use the no form of this command.
set comm-list community-list-name delete
Syntax Description
Standard or expanded community list name. The name is any alphanumeric string up to 63 characters. |
Command Default
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
This set command removes communities from the community attribute of an inbound or outbound update using a route map to filter and determine the communities to be deleted. Depending upon whether the route map is applied to the inbound or outbound update for a neighbor, each community that passes the route map permit clause and matches the given community list is removed from the community attribute being received from or sent to the Border Gateway Protocol (BGP) neighbor.
Each entry of a standard community list should list only one community when used with the set comm-list delete command. For example, in order to be able to delete communities 10:10 and 10:20, you must use the following format to create the entries:
The following format for a community list entry, while acceptable otherwise, does not work with the set comm-list delete command:
When both the set community community-number and set comm-lis t delete commands are configured in the same sequence of a route-map attribute, the deletion operation ( set comm-list delete) is performed before the set operation ( set community community-number).
Examples
This example shows how to remove communities from the community attribute of an inbound or outbound update:
switch(config)# route-map test1
switch(config-route-map)# match as-path 1
switch(config-route-map)# set comm-list list1 delete
Related Commands
set community
To set the Border Gateway Protocol (BGP) communities attribute, use the set community command. To delete the entry, use the no form of this command.
set community { none | { aa : nn [... aa:nn ] | additive | local-as | no-advertise | no-export }}
no set community { none | { aa : nn | additive | local-as | no-advertise | no-export }}
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
You must have a match clause (even if it points to a “permit everything” list) if you want to set tags.
Use the route-map global configuration command, and the match and set route map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route map configuration commands specify the redistribution set actions to be performed when all of the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
This example shows how to configure the routes that pass the autonomous system path access list 1 have the community set to 109:02 and 33:40. Routes that pass the autonomous system path access list 2 have the community set to no-export (these routes will not be advertised to any external BGP [eBGP] peers).
switch(config)# route-map test1 10 permit
switch(config-route-map)# match as-path 1
switch(config-route-map)# set community 109:02 33:40
switch(config-route-map)# exit
switch(config)# route-map test1 20 permit
switch(config-route-map)# match as-path 2
switch(config-route-map)# set community no-export
This example shows how to configure the routes that pass the autonomous system path access list 1 have the community set to 109:30. Routes that pass the autonomous system path access list 2 have the community set to local-as (the router will not advertise this route to peers outside the local autonomous system.
switch(config)# route-map test1 10 permit
switch(config-route-map)# match as-path 1
switch(config-route-map)# set community 109:30 additive
switch(config-route-map)# exit
switch(config)# route-map test1 20 permit
switch(config-route-map)# match as-path 2
switch(config-route-map)# set community local-as
Related Commands
set distance (bgp)
To set the administrative distance for iBGP or eBGP routes, use the set distance command. To disable this function, use the no form of this command.
set distance <value1> <value2> <value3>
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
This command requires the Enterprise Services license.
After you enter the value for the external administrative distance, you must enter the value for the administrative distance for the internal routes or/and the value for the administrative distance for the local routes depending on your requirement; so that the internal/local routes are also considered in the route administration.
Examples
This example shows how to set the administrative distance of route:
Related Commands
|
|
|
|---|---|
set distance
To set the administrative distance of OSPF routes, use the set distance command. To disable this function, use the no form of this command.
Syntax Description
Specifies the administrative distance for iBGP or eBGP routes. The range is from 1 to 255. |
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to set the administrative distance of route:
Related Commands
|
|
|
|---|---|
set extcommunity
To set the Border Gateway Protocol (BGP) extended communities attribute, use the set extcommunity command. To delete the entry, use the no form of this command.
set extcommunity { none | { generic { transitive | nontransitive } aa4 : nn [... aa4:nn ]} | additive }
no set extcommunity { none | { generic { transitive | nontransitive } aa4 : nn [... aa4:nn ]} | additive }
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the set extcommunity command in a route map to set the extended community attribute in a BGP route.
You must have a match clause in a route map (even if it points to a “permit everything” list) if you want to use set commands.
The set commands specify the set actions to be performed when all of the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
This example shows how to configure a route map that sets the extended community to 1.5:
switch(config)# route-map test1 10 permit
switch(config-route-map)# match as-path 1
switch(config-route-map)# set extcommunity generic transitive 1.5
switch(config-route-map)# exit
Related Commands
|
|
|
Defines the conditions for redistributing routes from one routing protocol into another. |
|
Configures BGP to propagate community attributes to BGP peers. |
|
set extcommunity cost
To configure the Border Gateway Protocol (BGP) cost-extended community attribute, use the set extcommunity cost command. To remove the BGP cost-extended community attribute, use the no form of this command.
set extcommunity cost [ 0-255 | igp community-id cost-value | pre-bestpath community-id cost-value ]
no set extcommunity cost [ 0- 255 | igp community-id cost-value | pre-bestpath community-id cost-value ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can configure multiple cost community attributes in each route map block or sequence. Each cost community set clause must have a unique ID.
The cost community set clause with the lowest cost is preferred by the best-path selection process when all other attributes are equal.
If you configure a new cost-extended community attribute against an existing community ID, the new cost replaces the old cost.
Examples
This example shows how to configure the BGP cost-extended community value:
This example shows how to remove the BGP cost-extended community value:
Related Commands
set extcomm-list delete
To remove extended communities from the extended community attribute of an inbound or outbound Border Gateway Protocol (BGP) update, use the set extcomm-list delete command. To remove a previous set extcomm-list delete command, use the no form of this command.
set extcomm-list community-list-name delete
Syntax Description
Standard or expanded extended community list name. The name is any alphanumeric string up to 63 characters. |
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the set extcomm-list command in a route map to delete the extended community attribute in a BGP route.
You must have a match clause in a route-map (even if it points to a “permit everything” list) if you want to use the set commands.
The set commands specify the set actions to be performed when all of the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
When you configure both the set extcommunity community-number and set ext comm-lis t delete commands in the same sequence of a route-map attribute, the deletion operation ( set extcomm-list delete) is performed before the set operation ( set extcommunity community-number).
Examples
This example shows how to remove extended communities from the extended community attribute of an inbound or outbound update:
switch(config)# route-map test1
switch(config-route-map)# match as-path 1
switch(config-route-map)# set extcomm-list list1 delete
Related Commands
|
|
|
|---|---|
set extcommunity rt
To configure the Border Gateway Protocol (BGP) route target RT-extended community attribute, use the set extcommunity rt command. To remove the BGP RT attribute, use the no form of this command.
set extcommunity rt { extended-community additive ] | [ additive ]}
no set extcommunity rt { extended-community additive ] | [ additive ]}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the show running-config command to display the format in which the RT-extended communities were configured. The RT extended communities are stored in an ascending order.
Examples
This example shows how to configure the BGP RT-extended community attribute:
This example shows how to remove the BGP RT-extended community attribute:
Related Commands
|
|
|
|---|---|
Defines the conditions for redistributing routes from one routing protocol into another. |
|
Configures BGP to propagate community attributes to BGP peers. |
|
set forwarding-address
To set the Open Shortest Path First (OSPF) forwarding address for redistributed type-5 link-state advertisements (LSAs), use the set forwarding-address command. To remove the address, use the no form of this command.
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
This command is used by the OSPF to set the forwarding address for the redistributed type-5 LSAs. The value of the forwarding address specified by the autonomous system boundary router (ASBR) can be either 0.0.0.0 or non zero. The 0.0.0.0 address indicates that the originating router (the ASBR) is the next hop:
The forwarding address is set to 0.0.0.0 if the ASBR redistributes routes and OSPF is not enabled on the next hop interface for those routes. This is true if Router 1 does not have OSPF enabled on the Ethernet interface.
All of the following conditions must be met to set the forwarding address field to a nonzero address:
- OSPF is enabled on the ASBR's next-hop interface.
- ASBR’s next-hop interface is non passive under OSPF.
- ASBR’s next-hop interface is not point to point.
- ASBR’s next-hop interface is not point to multipoint.
Any other conditions besides those listed previously, set the forwarding address to 0.0.0.0.
Examples
This example shows how to set the forwarding address:
switch(config)# route-map test1 10 permit
switch(config-route-map)# set forwarding-address
Related Commands
set interface
To configure an interface to be used for routing, use the set interface command. To revert to the default settings, use the no form of this command.
set interface [ null 0 | tunnel-te ]
no set interface [ null 0 | tunnel-te ]
Syntax Description
(Optional) Specifies the null interface. The valid value is 0. |
|
(Optional) Specifies the traffic engineering (TE) interface. The range is from 0 to 65503. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The set interface command is used only for policy-based routing (PBR) and is ignored if it is present in a route map that is used for route redistribution or filtering. To remove the static routing for tunnels, use the no set interface command.
When you enter the null 0 keywords, packets drop.
When you enter the tunnel-te keyword, packet are redirected to that TE tunnel if the TE tunnel is up. If the TE tunnel is down, packets are routed to the default tunnel.
Examples
This example shows how to configure an interface to be used for routing:
This example shows how to remove the static routing for tunnels:
Related Commands
|
|
|
|---|---|
Defines the conditions for redistributing routes from one routing protocol into another. |
|
Specifies a preference value for the autonomous system path. |
set ip address prefix-list
To specify the IPv4 map routes to be injected, use the set ip address prefix-list command. To remove the prefix-list, use the no form of this command.
set ip address prefix-list prefix-list-name
no set ip address prefix-list prefix-list-name
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify the map routes to be injected:
Related Commands
set ip default next-hop
To configure a route map that sets the next-hop IPv4 address as the default, use the set ip default next-hop command. To delete an entry, use the no form of this command.
set ip default next-hop ip-address [ ...ip-address ] [ load-share | verify-availability ]
no set ip default next-hop ip-address [ ...ip-address ]
Syntax Description
IPv4 address of the next hop to which packets are output.The next hop must be an adjacent router. You can configure up to 32 IP addresses. |
|
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, it routes the packet to this next hop. The first next hop specified with the set ip default next-hop command needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ip policy route-map command, the route-map global configuration command, and the match and set commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which policy routing occurs. The set commands specify the set actions —the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used with one another. They are evaluated in the following order:
Note
The set ip next-hop and set ip default next-hop commands are similar but have a different order of operations. Configuring the set ip next-hop command causes the system to use policy routing first and then use the routing table. Configuring the set ip default next-hop command causes the system to use the routing table first and then policy route the specified next hop.
For software-forwarded traffic, the route that is present in the unicast routing table (of the VRF in which packet was received) for the packet-specified destination takes preference over what is specified in the set ip default next-hop command when there is condition match. Even if there is a default route present in the VRF, that default route overrides what is set in the command. This applies to software-forwarded traffic only.
Examples
This example shows how to configure a route map that sets the IPv4 default next-hop address as the default:
Related Commands
set ip next-hop
To configure a route map that sets the next-hop IPv4 address, use the set ip next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
set ip next-hop { ip-address [ ... ip-address ] [ load-share] | peer-address | unchanged | verify-availability }
no set ip next-hop { ip-address [ ... ip-address ] [ load-share] | peer-address | unchanged | verify-availability }
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use the ip policy route-map command, the route-map command, and the match and set commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which policy routing occurs. The set commands specify the set actions —the particular routing actions to perform if the criteria enforced by the match commands are met.
If the first next hop specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn.
When the set ip next-hop command is used with the peer-address keyword in an inbound route map of a BGP peer, the next hop of the received matching routes will be set to be the neighbor peering address, overriding any third-party next hops. The same route map can be applied to multiple BGP peers to override third-party next hops.
When the set ip next-hop command is used with the peer-address keyword in an outbound route map of a BGP peer, the next-hop of the advertised matching routes will be set to be the peering address of the local router which disables the next-hop calculation. The set ip next-hop command has finer granularity than the (per-neighbor) neighbor next-hop-self command, because you can set the next hop for some routes, but not for others. The neighbor next-hop-self command sets the next hop for all routes sent to that neighbor.
The set clauses can be used with one another. They are evaluated in the following order:
By default, for eBGP, the next hop to reach a connected network is the IP address of the neighbor that sent the update. Therefore, as an update goes from device to device, the next hop typically changes to be the address of the neighbor that sent the update (the device’s own address).
However, there might be a scenario where you want the next hop to remain unchanged. The set ip next-hop unchanged command is used to propagate the next hop unchanged for multihop eBGP peering sessions.
Examples
This example shows three routers on the same LAN (with IP addresses 10.1.1.1, 10.1.1.2, and 10.1.1.3). Each router is in a different autonomous system. The set ip next-hop peer-address configuration specifies that traffic:
- from the router (10.1.1.3) in remote autonomous system 64496
- for the router (10.1.1.1) in remote autonomous system 64497
- that matches the route map
is passed through the router bgp 64498 and is not sent directly to the router (10.1.1.1) in autonomous system 100.
The set ip next-hop unchanged command specifies that the next hop attribute in the BGP update to the eBGP peer is unmodified.
Related Commands
set ip precedence
To set the precedence value in the IPv4 packet header, use the set ip precedence command in route-map configuration mode. To remove the precedence value, use the no form of this command.
set ip precedence precedence-value
no set ip precedence precedence-value
Syntax Description
A number from 0 to 7 that sets the precedence bit in the packet header. |
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
The way the network gives priority (or some type of expedited handling) to the marked traffic is through the application of weighted fair queuing (WFQ) or weighted random early detection (WRED) at points downstream in the network. Typically, you would set IPv4 precedence at the edge of the network (or administrative domain) and have queuing act on it thereafter. WFQ can speed up handling for high precedence traffic at congestion points. WRED ensures that high precedence traffic has lower loss rates than other traffic during times of congestion.
The mapping from keywords such as routine and priority to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. You can define the meaning of a precedence value by enabling other features that use the value. In the case of Cisco high-end Internet quality of service (QoS), IPv4 precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network. For example, IPv4 precedence 2 can be given 90 percent of the bandwidth on output links in the network, and IPv4 precedence 6 can be given 5 percent using the distributed weight fair queuing (DWFQ) implementation on the Versatile Interface Processors (VIPs).
Use the route-map global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution or policy routing is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the IPv4 precedence value to 5 for packets that pass the route map match:
Related Commands
set ipv6 address prefix-list
To specify the IPv6 map routes to be injected, use the set ipv6 address prefix-list command. To remove the prefix-list, use the no form of this command
set ipv6 address prefix-list prefix-list-name
no set ipv6 address prefix-list prefix-list-name
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify the map routes to be injected:
Related Commands
set ipv6 default next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing and for which the Cisco NX-OS software has no explicit route to a destination, use the set ipv6 default next-hop command. To delete an entry, use the no form of this command.
set ipv6 default next-hop ipv6-address [ ...ipv6-address ] [ load-share | verify-availability ]
no set ipv6 default next-hop ipv6-address [ ...ipv6-address ] [ load-share | verify-availability ]
Syntax Description
IPv6 address of the next hop to which packets are output.The next hop must be an adjacent router. You can configure up to 32 IPv6 addresses. |
|
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ipv6-address argument.
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, then it routes the packet to this next hop. The first next hop specified with the set ipv6 default next-hop command needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ipv6 policy route-map i nterface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ipv6 policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which policy routing occurs. The set commands specify the set actions —the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used with one another. They are evaluated in the following order:
Note The set ipv6 next-hop and set ipv6 default next-hop are similar commands but have a different order of operations. Configuring the set ipv6 next-hop command causes the system to use policy routing first and then use the routing table. Configuring the set ipv6 default next-hop command causes the system to use the routing table first and then policy route the specified next hop.
Examples
This example shows how to configure a route map that sets the IPv6 default next-hop address:
Related Commands
set ipv6 next-hop
To indicate the IP address to which the packets are sent when they match a clause of route map for policy routing, use the set ipv6 next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
set ipv6 next-hop { ipv6-address [ ... ipv6-address ] [ load-share] | peer-address | unchanged | verify-availability }
no set ipv6 next-hop { ipv6-address [ ... ipv6-address ] [ load-share] | peer-address | unchanged | verify-availability }
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ipv6-address argument.
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, then it routes the packet to this next hop. The first next hop specified with the set ipv6 default next-hop command needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ipv6 policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ipv6 policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which policy routing occurs. The set commands specify the set actions —the particular routing actions to perform if the criteria enforced by the match commands are met.
When the set ipv6 next-hop command is used with the peer-address keyword in an inbound route map of a BGP peer, the next hop of the received matching routes will be set to be the neighbor peering address, overriding any third-party next hops. The same route map can be applied to multiple BGP peers to override third-party next hops.
When the set ipv6 next-hop command is used with the peer-address keyword in an outbound route map of a BGP peer, the next-hop of the advertised matching routes will be set to be the peering address of the local router which disables the next-hop calculation. The set ipv6 next-hop command has finer granularity than the (per-neighbor) neighbor next-hop-self command, because you can set the next hop for some routes, but not for others. The neighbor next-hop-self command sets the next hop for all routes sent to that neighbor.
The set clauses can be used with one another. They are evaluated in the following order:
Note The set ipv6 next-hop and set ipv6 default next-hop commands are similar but have a different order of operations. Configuring the set ipv6 next-hop command causes the system to use policy routing first and then use the routing table. Configuring the set ipv6 default next-hop command causes the system to use the routing table first and then policy route the specified next hop.
Examples
This example shows how to configure a route map that sets the IPv6 next-hop address:
set ipv6 precedence
To set the precedence value in the IPv6 packet header, use the set ipv6 precedence command in route-map configuration mode. To remove the precedence value, use the no form of this command.
set ipv6 precedence precedence-value
no set ipv6 precedence precedence-value
Syntax Description
A number from 0 to 7 that sets the precedence bit in the packet header. |
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
The way the network gives priority (or some type of expedited handling) to the marked traffic is through the application of weighted fair queueing (WFQ) or weighted random early detection (WRED) at points downstream in the network. Typically, you would set IPv6 precedence at the edge of the network (or administrative domain) and have queueing act on it thereafter. WFQ can speed up handling for high precedence traffic at congestion points. WRED ensures that high precedence traffic has lower loss rates than other traffic during times of congestion.
The mapping from keywords such as routine and priority to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. You can define the meaning of a precedence value by enabling other features that use the value. In the case of Cisco high-end Internet quality of service (QoS), IPv6 precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network. For example, IPv6 precedence 2 can be given 90 percent of the bandwidth on output links in the network, and IPv6 precedence 6 can be given 5 percent using the distributed weight fair queueing (DWFQ) implementation on the Versatile Interface Processors (VIPs).
Use the route-map global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution or policy routing is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the IPv6 precedence value to 5 for packets that pass the route map match:
Related Commands
set level
To indicate where to import routes, use the set level command. To delete an entry, use the no form of this command.
set level { level-1 | level-2 | level-1-2 }
no set level { level-1 | level-2 | level-1-2 }
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the route-map command, and the match and set commands to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
This example shows how to import the routes into the Level 1 area:
Related Commands
set local-preference
To specify a preference value for the autonomous system path, use the set local-preference command in route-map configuration mode. To delete an entry, use the no form of this command.
set local-preference number-value
no set local-preference number-value
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
The preference is sent only to all routers in the local autonomous system.
You must have a match clause (even if it points to a “permit everything” list) if you want to set tags.
Use the route-map command, and the match and set to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
You can change the default preference value with the bgp default local-preference command.
Examples
This example shows how to set the local preference to 100 for all routes that are included in access list 1:
Related Commands
set metric
To set the metric value for a routing protocol, use the set metric command. To return to the default metric value, use the no form of this command.
set metric [ + | - ] bandwidth-metric
set metric bandwidth-metric [ delay-metric reliability-metric load-metric mtu ]
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the set metric command to modify the IGRP metric values.
Note We recommend that you consult your Cisco technical support representative before changing the default value.
When you configure the reliability-metric and the load-metric arguments, 255 means 100 percent reliability.
Use the + or - keywords to modify the existing delay metric value. You can modify only the delay metric with these keywords.
Use the route-map command and the match and set command to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
This example shows how to set the bandwidth metric value for the routing protocol to 100:
This example shows how to increase the bandwidth metric value for the routing protocol by 100:
Related Commands
|
|
|
|---|---|
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
set metric-type
To set the metric type for the destination routing protocol, use the set metric-type command. To return to the default, use the no form of this command.
set metric-type { internal | external | type-1 | type-2 }
no set metric-type { internal | external | type-1 | type-2 }
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the route-map command with the match and set commands to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Note This command is not supported for redistributing routes into the Border Gateway Protocol (BGP).
Examples
This example sets the metric type of the destination protocol to OSPF external Type 1:
Related Commands
set nssa-only
To set a type-7 link-state advertisement (LSA) generated on the Autonomous System Boundary Router (ASBR) with no P-bit set and prevent the type-7 to type-5 LSA conversion in Open Shortest Path First (OSPF), use the set nssa-only command. To remove the type-7 configuration control, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When you use the set nssa-only command, the settings are applied to all not-so-stubby areas (NSSA) with the type-7 LSA that corresponding to that LSA with no has its P-bit set.
Examples
This example shows how to set a type-7 LSA generated on the ASBR and with no P-bit set and prevent the type-7 to type-5 LSA conversion in OSPF:
This example shows how to remove the type-7 configuration control:
Related Commands
|
|
|
|---|---|
Defines the conditions for redistributing routes from one routing protocol into another. |
|
set origin
To set the Border gateway Protocol (BGP) origin code, use the set origin command. To delete the entry, use the no form of this command.
set origin { egp as-num [: as-num ] | igp | incomplete }
Syntax Description
Specifies the AS number for a remote exterior gateway protocol (EGP) system. You can specify the AS number as a 2-byte integer, or a 4-byte integer in aa:nn format. The range is from 1 to 65535. |
|
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
You must have a match clause (even if it points to a “permit everything” list) if you want to set tags.
Use the route-map command, and the match and set command, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map commands specify the redistribution set actions to be performed when all of the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
This example shows how to set the origin of routes that pass the route map to IGP:
Related Commands
set path-selection all advertise
To set the path selection criteria for Border Gateway Protocol (BGP), use the set path-selection all advertise command. To delete the entry, use the no form of this command.
set path-selection all advertise
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify that all paths be advertised for the specified prefix:
Related Commands
|
|
|
|---|---|
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. |
set tag
To set a tag value of the destination routing protocol, use the set tag command. To delete the entry, use the no form of this command.
Syntax Description
Name for the tag. The value is an integer from 0 to 4294967295. |
Defaults
If not specified, the default action is to forward the tag in the source routing protocol onto the new destination protocol.
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the route-map command, and the match and set commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
This example shows how to set the tag value of the destination routing protocol to 5:
Related Commands
set vrf
To enable a virtual routing and forwarding (VRF) instance selection within a route map for policy-based routing, use the set vrf command. To disable VRF selection within a route map, use the no form of this command.
set vrf { vrf-name | default | management }
no set vrf [ vrf-name | default | management ]
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
The set vrf command was introduced with the MPLS VPN—VRF Selection using Policy Based Routing feature to provide a PBR mechanism for VRF selection. This command is used to enable VRF selection by policy routing packets through a route map. The route map is attached to the incoming interface. Match criteria is defined in an IP access list or in an IP prefix list. Match criteria can also be defined based on packet length with the match length route map command. You must define the VRF prior to the configuring this command, and you must configure the ip policy route-map interface configuration command must be configured to enable policy routing under the interface or subinterface. If the VRF instance is not defined or if policy routing is not enabled, an error message appears in the console when you attempt to configure the set vrf command.
A PBR routing route map can have only one match or set statement per route-map statement. In addition, a match command cannot refer to more than one Access Control list (ACL) for PBR.
Note You cannot configure with the set ip default next-hop, and set ip next-hop list policy routing commands because a packet cannot be set to an interface and the next hop cannot be changed when the VRF instance is specified. An error message will appear in the console if you attempt to configure the set vrf command with any of the four above set clauses.
Examples
This example shows how to configure a route-map sequence that selects and sets a VRF instance based on match criteria defined in three different access lists. (The access list configuration is not shown in this example.) If the route map falls through and a match does not occur, the packet is dropped if the destination is local.
Related Commands
set weight
To specify the Border Gateway Protocol (BGP) weight for the routing table, use the set weight command. To delete an entry, use the no form of this command.
Syntax Description
Defaults
Command Modes
Route-map configuration (config-route-map)
Command History
|
|
|
|---|---|
Usage Guidelines
The weight is based on the first matched autonomous system path. The weights assigned with the set weight command override the weights assigned using the neighbor weight command.
Examples
This example shows how to set the BGP weight for the routes that match the autonomous system path access list to 200:
Related Commands
shutdown (BGP)
To shut down an instance of the Border Gateway Protocol (BGP), use the shutdown command. To disable this function, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the shutdown command to disable an instance of BGP without removing the configuration.
Examples
This example shows how to disable BGP 64496:
shutdown (EIGRP)
To shut down an instance of the Enhanced Interior Gateway Routing Protocol (EIGRP), use the shutdown command. To disable this function, use the no form of this command.
Syntax Description
Defaults
Command Modes
Address family configuration
Router configuration
Router VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the shutdown command to disable an instance of EIGRP without removing the configuration.
Examples
This example shows how to disable EIGRP 209:
shutdown (IS-IS)
To stop an Intermediate System-to-Intermediate System (IS-IS) router process without removing the process configuration, use the shutdown command. To start a stopped IS-IS process, use the no form of this command.
Syntax Description
Defaults
Command Modes
Router configuration
VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Entering the shutdown command stops a router process but does not remove any configuration parameters. The shutdown command is displayed in the running configuration file when enabled.
Examples
This example shows how to stop an active IS-IS process:
This example shows how to start a stopped a IS-IS process:
Related Commands
|
|
|
|---|---|
shutdown (OSPF)
To stop an Open Shortest Path First (OSPF) instance without removing the configuration, use the shutdown command. To start a stopped OSPF instance, use the no form of this command.
Syntax Description
Defaults
Command Modes
Router configuration
VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Entering the shutdown command stops a router process but does not remove any configuration parameters. The shutdown command is displayed in the running configuration file when enabled.
Examples
This example shows how to stop an active OSPF instance:
Related Commands
|
|
|
|---|---|
shutdown (OSPFv3)
To stop an Open Shortest Path First (OSPFv3) instance without removing the configuration, use the shutdown command. To start a stopped OSPF instance, use the no form of this command.
Syntax Description
Defaults
Command Modes
Router configuration
VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Entering the shutdown command stops a router process but does not remove any configuration parameters. The shutdown command is displayed in the running configuration file when enabled.
Examples
This example shows how to stop an active OSPFv3 instance:
Related Commands
|
|
|
|---|---|
shutdown (VRRP)
To disable a Virtual Router Redundancy Protocol (VRRP) configuration, use the shutdown command. To enable a VRRP configuration, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Shut down the virtual router before configuring the virtual router parameters; you can only configure the virtual router after it is in an administrative shutdown state. Enter the no shutdown command to update the virtual router state after completing configuration.
Examples
This example shows how to shut down a VRRP group:
Related Commands
|
|
|
|---|---|
Clears all the software counters for the specified virtual router. |
spf-interval
To configure the minimum interval between arrivals of a link-state advertisement (LSA), use the spf-interval command. To return to the default setting, use the no form of this command.
spf-interval [ level-1 | level-2 ] spf-max-wait [ spf-initial-wait spf-second-wait ]
Syntax Description
Defaults
The default are as follows: spf-max-wait is 8000 milliseconds; spf-initial-wait is 50 milliseconds, and spf-second-wait is 50 milliseconds.
Command Modes
Router configuration
VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to set the minimum interval time between arrivals of LSA:
Related Commands
|
|
|
|---|---|
stub
To configure a router as a stub using the Enhanced Interior Gateway Routing Protocol (EIGRP), use the stub command. To disable the EIGRP stub routing feature, use the no form of this command.
stub [[ direct | static | summary | redistributed ]] + [ leak-map map-name] | receive-only ]
no stub [[ direct | static | summary | redistributed ]] + [ leak-map map-name] | receive-only ]
Syntax Description
(Optional) Advertises redistributed routes from other protocols and autonomous systems. |
|
(Optional) Advertises redistributed routes from other protocols and autonomous systems. |
Defaults
Command Modes
Address-family configuration
Router configuration
Router VRF configuration
Command History
|
|
|
|---|---|
Added static and summary keywords to the syntax description. |
|
Usage Guidelines
Use the stub command to configure a router as a stub where the router directs all IP traffic to a distribution router.
The direct keyword permits EIGRP stub routing to advertise connected routes. This option is enabled by default.
The receive-only keyword restricts the router from sharing any of its routes with any other router in that EIGRP autonomous system, and the receive-only keyword does not permit any other option to be specified because it prevents any type of route from being sent.
The redistributed keyword permits the EIGRP Stub Routing feature to send other routing protocols and autonomous systems. Without the configuration of this option, EIGRP will not advertise redistributed routes.
If you use any of these four keywords ( direct, leak-map, receive-only, redistributed) with the stub command, only the route types specified by the particular keyword(s) are advertised.
Examples
This example shows how to configure the router as a receive-only neighbor:
summary-address
To create the Intermediate-System-to Intermediate System (IS-IS) aggregate addresses, use the summary-address command. To remove the aggregate address, use the no form of this command.
summary-address { ip-addr | ip-prefix / length | ipv6-addr | ipv6-prefix / length } level
Syntax Description
Command Default
Command Modes
Address-family configuration
Router configuration
VRF configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Multiple groups of addresses can be summarized for a given level. Routes learned from other routing protocols can also be summarized. The metric used to advertise the summary is the smallest metric of all the more specific routes. This command reduces the size of the routing table and also reduces the size of the link-state packets (LSPs) and the link-state database (LSDB). It also helps to stabilize the network stability because a summary advertisement depend on many specific routes. A single route flap does not cause the summary advertisement to flap in most cases.
Note that when using summary addresses, other routes might have less information to calculate because the most optimal routing table for all individual destinations are used.
Examples
This example shows how to redistribute directly connected routes into IS-IS. Only the 10.1.0.0 address is advertised the IS-IS level-1 link-state protocol data unit (PDU). The summary address is tagged with 100.
Related Commands
|
|
|
|---|---|
Enters the address family mode or a VRF address-family mode. |
|
summary-address (OSPF)
To create aggregate addresses for the Open Shortest Path First (OSPF) protocol, use the summary-address command. To return to the default, use the no form of this command.
summary-address ip-prefix/length [ not-advertise ] [ tag tag ]
no summary-address ip-prefix/length [ not-advertise ] [ tag tag ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the summary-address command to create an aggregate address to replace a series of more-specific addresses. The metric used to advertise the summary is the smallest metric of all the more specific routes.
Use this command to reduce the size of the routing table and allow an OSPF Autonomous System Boundary Router (ASBR) to advertise one external route as an aggregate for all redistributed routes that are covered by the address.
Examples
This example shows how to configure the summary address 192.0.0.0 to include address 192.0.1.0, 192.0.2.0, 192.0.3.0, and so on. Only the address 192.0.0.0 is advertised in an external link-state advertisement.
Related Commands
|
|
|
|---|---|
summary-address (OSPFv3)
To create aggregate addresses for the Open Shortest Path First version 3 (OSPFv3) protocol, use the summary-address command. To return to the default, use the no form of this command.
summary-address ipv6-prefix/length [ not-advertise ] [ tag tag ]
no summary-address ipv6-prefix/length [ not-advertise ] [ tag tag ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the summary-address command to create an aggregate address to replace a series of more-specific addresses. The metric used to advertise the summary is the smallest metric of all the more specific routes.
Use this command to reduce the size of the routing table and allow an OSPFv3 Autonomous System Boundary Router (ASBR) to advertise one external route as an aggregate for all redistributed routes that are covered by the address.
Examples
This example shows how to configure the summary address 192.0.0.0 to include address 192.0.1.0, 192.0.2.0, 192.0.3.0, and so on. Only the address 192.0.0.0 is advertised in an external link-state advertisement.
Related Commands
|
|
|
|---|---|
suppress-inactive
To advertise the active routes to a Border Gateway Protocol (BGP) peer only, use the suppress-inactive command. To remove the restriction, use the no form of this command. To return to the default setting, use the default form of this command.
no | default suppress-inactive
Syntax Description
Defaults
BGP advertises routes to a peer as soon as they are installed in the local routing table, even if the routes are not the active routes in the table.
Command Modes
Neighbor address-family configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the suppress-inactive command to advertise only active routes to a BGP peer.
Examples
This example shows how to create a summary address. The path advertised for this route is an autonomous system set consisting of all elements contained in all paths that are being summarized.
suppress-inactive
Related Commands
|
|
|
Feedback