Downloads |
 Feedback
|
Table Of Contents
S Commands
This chapter describes the Cisco NX-OS unicast routing commands that begin with the letter S, except for the show commands.
set as-path
To modify an autonomous system path (as-path) for BGP routes, use the set as-path command in route-map configuration mode. 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
Autonomous system path is not modified.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You must enter the feature pbr global configuration mode command to enable 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, increasing the autonomous system path length.
Examples
The following example converts the tag of a redistributed route into an autonomous system path:
switch(config)# route-map test1switch(config-route-map)# set as-path tagThe following example prepends 100 to all the routes advertised to 10.108.1.1:
switch(config)# route-map test1switch(config-route-map)# match as-path 1switch(config-route-map)# set as-path prepend 100!switch(config)# router bgp 64496switch(config-router)# neighbor 10.108.1.1 remote-as 64497switch(config-router-neighbor)# address-family ipv4 unicastswitch(config-router-neighbor-af)# route-map set-as-path test1 outRelated 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 in route-map configuration mode. To remove a previous set comm-list delete command, use the no form of this command.
set comm-list community-list-name delete
no set comm-list
Syntax Description
community-list-name
A standard or expanded community list name. The name is any alphanumeric string up to 63 characters.
Command Default
No communities are removed.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This set route-map configuration 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 will be 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:
switch(config)# ip community-list 500 permit 10:10switch(config)# ip community-list 500 permit 10:20The following format for a community list entry, while acceptable otherwise, does not work with the set comm-list delete command:
switch(config)# ip community-list 500 permit 10:10 10:20When both the set community community-number and set comm-list 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).
This command does not require a license.
Examples
The following example shows how to remove communities from the community attribute of an inbound or outbound update:
switch(config)# route-map test1switch(config-route-map)# match as-path 1switch(config-route-map)# set comm-list list1 deleteRelated Commands
set community
To set the BGP communities attribute, use the set community route map configuration 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
Command Default
No BGP communities attributes exist.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
This command does not require a license.
Examples
In the following example, 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 permitswitch(config-route-map)# match as-path 1switch(config-route-map)# set community 109:02 33:40switch(config-route-map)# exitswitch(config)# route-map test1 20 permitswitch(config-route-map)# match as-path 2switch(config-route-map)# set community no-exportIn the following similar example, 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 permitswitch(config-route-map)# match as-path 1switch(config-route-map)# set community 109:30 additiveswitch(config-route-map)# exitswitch(config)# route-map test1 20 permitswitch(config-route-map)# match as-path 2switch(config-route-map)# set community local-asRelated Commands
set dampening
To set the BGP route dampening factors, use the set dampening route map configuration command. To disable this function, use the no form of this command.
set dampening half-life reuse suppress max-suppress-time
no set dampening
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
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.
When a BGP peer is reset, the route is withdrawn and the flap statistics cleared. In this instance, the withdrawal does not incur a penalty even though route flap dampening is enabled.
This command does not require a license.
Examples
The following example sets the half life to 30 minutes, the reuse value to 1500, the suppress value to 10000; and the maximum suppress time to 120 minutes:
switch(config)# route-map test1 10 permitswitch(config-route-map)# set dampening 30 1500 10000 120Related Commands
set etxcommunity
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
Command Default
No BGP communities attributes exist.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
This command does not require a license.
Examples
The following example shows how to configure a route map that sets the extended community to 1.5:
switch(config)# route-map test1 10 permitswitch(config-route-map)# match as-path 1switch(config-route-map)# set extcommunity generic transitive 1.5switch(config-route-map)# exitRelated 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
no set extcomm-list
Syntax Description
community-list-name
Standard or expanded extended community list name. The name is any alphanumeric string up to 63 characters.
Command Default
No communities are removed.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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 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-list 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).
This command does not require a license.
Examples
The following example shows how to remove extended communities from the extended community attribute of an inbound or outbound update:
switch(config)# route-map test1switch(config-route-map)# match as-path 1switch(config-route-map)# set extcomm-list list1 deleteRelated Commands
match as-path
Matches a BGP autonomous system path access list.
match extcommunity
Matches a BGP extended community.
set extcommunity
Sets the BGP extended communities attribute.
set forwarding-address
To set the OSPF forwarding address for redistributed type-5 LSAs, use the set forwarding-address route-map configuration mode command. To remove the address, use the no form of this command.
set forwarding-address
no forwarding-address
Syntax Description
This command has no arguments or keywords.
Command Default
No forwarding address is set as a default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command is used by the Open Shortest Path First (OSPF) to set the forwarding address in the 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 determined by these conditions:
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 in the figure 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 non-zero address:
•
OSPF is enabled on the ASBR's next hop interface.
•
•
•
Any other conditions besides those listed previously, set the forwarding address to 0.0.0.0.
This command does not require a license.
Examples
The following example shows how to set the forwarding address:
switch(config)# route-map test1 10 permitswitch(config-route-map)# set forwarding-addressRelated Commands
set ip 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 ip default next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
set ip default next-hop ip-address [...ip-address] [load-share]
no set ip default next-hop ip-address [...ip-address]
Syntax Description
ip-address
IP 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.
load-share
(Optional) Enables load sharing.
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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, then 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 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 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 in conjunction with one another. They are evaluated in the following order:
1.
2.
Note
This command does not require a license.
Examples
The following example shows how to configure a route map that sets the IPv6 default next-hop address.
switch(config)# ip access-list testswitch(config-ip-acl)# permit ip 192.0.2.0/24 anyswitch(config-ip-acl)# exitswitch(config)# route-map equal-accessswitch(config-route-map)# match ip address testswitch(config-route-map)# set ip default next-hop ip 192.0.2.3switch(config-route-map))# exitswitch(config)# interface externet 2/1switch(config-if)# ip policy route-map equal-accessRelated Commands
set ip next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing, 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}
no set ip next-hop {ip-address [... ip-address] [load-share] | peer-address}
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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 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 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. So 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, thus disabling 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 others. The neighbor next-hop-self command sets the next hop for all routes sent to that neighbor.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
This command does not require a license.
Examples
In the following example, three routers are on the same LAN (with IP addresses 10.1.1.1, 10.1.1.2, and 10.1.1.3). Each is in a different autonomous system. The set ip next-hop peer-address command 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, rather than sent directly to the router (10.1.1.1) in autonomous system 100 over their mutual connection to the LAN.
switch(config)# router bgp 64498switch(config-router)# neighbor 10.1.1.3 remote-as 64496switch(config-router)# neighbor 10.1.1.3 route-map set-peer-address outswitch(config-router)# neighbor 10.1.1.1 remote-as 64497!switch(config)# route-map set-peer-address permit 10switch(config-route-map)# set ip next-hop peer-addressRelated 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 in route-map configuration mode. To delete an entry, use the no form of this command.
set ipv6 default next-hop ipv6-address [...ipv6-address] [load-share]
no set ipv6 default next-hop ipv6-address [...ipv6-address]
Syntax Description
ipv6-address
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.
load-share
(Optional) Enables load sharing.
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
Note
This command does not require a license.
Examples
The following example shows how to configure a route map that sets the IPv6 default next-hop address.
switch(config)# ipv6 access-list testswitch(config-ipv6-acl)# permit ipv6 2001:0DB8::/48 anyswitch(config-ipv6-acl)# exitswitch(config)# route-map equal-accessswitch(config-route-map)# match ipv6 address testswitch(config-route-map)# set ipv6 default next-hop 2001:0DB8::3switch(config-route-map))# exitswitch(config)# interface externet 2/1switch(config-if)# ipv6 policy route-map equal-accessRelated Commands
set ipv6 next-hop
To indicate where to output packets that pass a match clause of a 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.
sset ipv6 next-hop {ipv6-address [... ipv6-address] [load-share] | peer-address}
no set ipv6 next-hop {ipv6-address [... ipv6-address] [load-share] | peer-address}
Syntax Description
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
Note
This command does not require a license.
Examples
The following example shows how to configure a route map that sets the IPv6 next-hop address.
switch(config)# ipv6 access-list testswitch(config-ipv6-acl)# permit ipv6 2001:0DB8::/48 anyswitch(config-ipv6-acl)# exitswitch(config)# route-map equal-accessswitch(config-route-map)# match ipv6 address testswitch(config-route-map)# set ipv6 next-hop 2001:0DB8::3switch(config-route-map))# exitswitch(config)# interface externet 2/1switch(config-if)# ipv6 policy route-map equal-accessRelated Commands
set level
To indicate where to import routes, use the set level command in route-map configuration mode. 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
level-1
Imports routes into a Level 1 area.
level-2
Imports routes into a Level 2 subdomain.
level-1-2
Imports routes into Level 1 and Level 2.
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
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 the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
This command does not require a license.
Examples
In the following example, routes will be imported into the Level 1 area:
switch(config-router)# route-map testcaseswitch(config-route-map)# set level level-lRelated 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
Command Default
Preference value of 100 by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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 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 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.
This command does not require a license.
Examples
The following example sets the local preference to 100 for all routes that are included in access list 1:
switch(config-router)# route-map map-preferenceswitch(config-route-map)# match as-path 1switch(config-route-map)# set local-preference 100Related Commands
set metric
To set the metric value for a routing protocol, use the set metric command in route-map configuration mode. 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]
no set metric
Syntax Description
Command Default
None
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the set metric command to modify the IGRP metric values.
Note
When you confiture 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 global configuration command and the match and set route-map configuration 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 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.
This command does not require a license.
Examples
The following example shows how to set the bandwith metric value for the routing protocol to 100:
switch(config)# route-map set-metricswitch(config-route-map)# set metric 100The following example shows how to increase the bandwith metric value for the routing protocol by 100:
switch(config)# route-map set-metricswitch(config-route-map)# set metric +100Related Commands
route-map
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 in route-map configuration mode. 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
Command Default
This command is disabled by default.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
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. 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.
Note
This command does not require a license.
Examples
The following example sets the metric type of the destination protocol to OSPF external Type 1:
switch(config)# route-map map-typeswitch(config-route-map)# set metric-type type-1Related Commands
set origin
To set the BGP origin code, use the set origin route-map configuration mode command. To delete the entry, use the no form of this command.
set origin {egp as-num [:as-num] | igp | incomplete}
no set origin
Syntax Description
Command Default
Default origin, based on route in main IP routing table.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
This command does not require a license.
Examples
The following example sets the origin of routes that pass the route map to IGP:
switch(config)# route-map set_originswitch(config-route-map)# match as-path 10switch(config-route-map)# set origin igpRelated Commands
set tag
To set a tag value of the destination routing protocol, use the set tag command in route-map configuration mode. To delete the entry, use the no form of this command.
set tag tag-value
no set tag tag-value
Syntax Description
Command Default
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)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
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 the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
This command does not require a license.
Examples
The following example sets the tag value of the destination routing protocol to 5:
switch(config)# route-map testswitch(config-route-map)# set tag 5Related Commands
set vrf
To enable virtual routing/forwarding instance (VRF) selection within a route map for policy-based routing VRF selection, use the set vrf command in route-map configuration mode. 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
vrf-name
Name assigned to the VRF.
default
Sets the VRF to the default VRF.
management
Sets the VRF to the management VRF.
Command Default
No default behavior or values
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The set vrf route-map configuration 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. The VRF must be defined prior to the configuration of this command, and the ip policy route-map interface configuration command must be configured to enable policy routing under the interface or subinterface. If the VRF is not defined or if policy routing is not enabled, an error message will be printed in the console when you attempt to configure the set vrf command.
Note
This command does not require a license.
Examples
The following example shows a route-map sequence that selects and sets a VRF 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 will be dropped if the destination is local.
switch(config)# route-map PBR-VRF-Selection permit 10switch(config-route-map)# match ip address 40switch(config-route-map)# set vrf VRF_1!switch(config)# route-map PBR-VRF-Selection permit 20switch(config-route-map)# match ip address 50switch(config-route-map)# set vrf VRF_2!switch(config)# route-map PBR-VRF-Selection permit 30switch(config-route-map)# match ip address 60switch(config-route-map)# set vrf VRF_3Related Commands
set weight
To specify the BGP weight for the routing table, use the set weight command in route-map configuration mode. To delete an entry, use the no form of this command.
set weight number
no set weight [number]
Syntax Description
Defaults
The weight is not changed by the specified route map.
Command Modes
Route-map configuration (config-route-map)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The implemented weight is based on the first matched autonomous system path. Weights indicated when an autonomous system path is matched override the weights assigned by global neighbor commands. In other words, the weights assigned with the set weight route-map configuration command override the weights assigned using the neighbor weight command.
This command does not require a license.
Examples
The following example sets the BGP weight for the routes matching the autonomous system path access list to 200:
switch(config)# route-map set-weightswitch(config-route-map)# match as-path 10switch(config-route-map)# set weight 200Related 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.
set-attached-bit
no set-attached-bit
Syntax Description
This command has no keywords or arguments.
Defaults
Enabled
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use 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-bit command is disabled, the "attached-bit" will not be advertised by the router in its Level 1 LSP, and other Level 1 routers in the area will not use this router as the default router outside the area.
This command requires the Enterprise Services license.
Examples
The following example shows how to unset the attached bit:
switch(config)# router isis Border1switch(config-router)# no set-attached-bitRelated Commands
set-overload-bit
To configure the router to signal other routers not to use this router as an intermediate hop in their shortest path first (SPF) calculations, use the set-overload-bit command. To remove the designation, use the no form of this command.
set-overload-bit {always | {on-startup {seconds | wait-for bgp as-num[.as-num]}} [suppress [[interlevel] [external]]]
no set-overload-bit
Syntax Description
Command Default
The overload bit is not set by default.
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The set-overload-bit command forces the router to set the overload bit in its nonpseudonode link-state packets (LSPs). Normally, the setting of the overload bit is allowed only when a router runs into problems. For example, when a router is experiencing a memory shortage, it might be that the link-state database is not complete, resulting in an incomplete or inaccurate routing table. By setting the overload bit in its LSPs, other routers can ignore the unreliable router in their SPF calculations until the router has recovered from its problems.
The results are that no paths through this router are seen by other routers in the IS-IS area. However, IP and Connectionless Network Service (CLNS) prefixes directly connected to this router are reachable.
This command can be useful when you want to connect a router to an IS-IS network but do not want real traffic flowing through it under any circumstances. Examples situations are as follows:
•
•
•
Unless you specify the on-startup keyword, this command sets the overload bit immediately.
In addition to setting the overload bit, you might want to suppress certain types of IP prefix advertisements from LSPs. For example, allowing IP prefix propagation between level 1 and level 2 effectively makes a node a transit node for IP traffic, which might be undesirable. The suppress keyword used with the interlevel or external keyword (or both) accomplishes that suppression while the overload bit is set.
This command does not require a license.
Examples
The following example sets the overload bit upon startup and until BGP has converged:
switch(config)# router isis firstcompanyswitch(config-router)# set-overload-bit on-startup wait for-bgp suppress interlevel external
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.
shutdown
no shutdown
Syntax Description
This command has no keywords or arguments.
Defaults
Enabled
Command Modes
Router configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the shutdown command to disable an instance of BGP without removing the configuration.
This command requires the Enterprise Services license.
Examples
The following example shows how to disable BGP 64496:
switch(config)# router BGP 64496switch(config-router)# shutdownshutdown (EIGRP)
To shut down an instance of Enhanced Interior Gateway Routing Protocol (EIGRP), use the shutdown command. To disable this function, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no keywords or arguments.
Defaults
Enabled
Command Modes
Address family configuration
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the shutdown command to disable an instance of EIGRP without removing the configuration.
This command requires the Enterprise Services license.
Examples
The following example shows how to disable eigrp 209:
switch(config)# router eigrp 209switch(config-router)# shutdownshutdown (IS-IS)
To stop an 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.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Command Default
No process is stopped.
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand 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.
This command requires the Enterprise Services license.
Examples
The following example stops an active IS-IS process:
switch(config)# router isis firstcompanyswitch(config-router)# shutdownThe following example starts a stopped a IS-IS process:
switch(config)# router isis firstcompanyswitch(config-router)# no shutdownRelated 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.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Command Default
No process is stopped.
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand 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.
This command requires the Enterprise Services license.
Examples
This example stops an active OSPF instance:
switch(config)# router ospf firstcompanyswitch(config-router)# shutdownRelated Commands
feature ospf
Enables OSPF on the router.
router ospf
Configures an OSPF instance.
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.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Command Default
No process is stopped.
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand 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.
This command requires the Enterprise Services license.
Examples
This example stops an active OSPFv3 instance:
switch(config)# router ospfv3 firstcompanyswitch(config-router)# shutdownRelated Commands
feature ospfv3
Enables OSPFv3 on the router.
router ospv3f
Configures an OSPF v3 instance.
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.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
VRRP configuration mode
Supported User Rolesnetwork-admin
VDC administratorCommand 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 administrative shut down state. Enter the no shutdown command to update the virtual router state after completing configuration.
This command does not require a license.
Examples
This example shows how to shut down a VRRP group:
switch(config-if)# vrrp 45switch(config-if-vrrp)# shutdownswitch(config-if-vrrp)# address 6.6.6.45switch(config-if-vrrp)# no shutdownRelated Commands
feature vrrp
Enables VRRP.
show vrrp
Displays VRRP configuration information.
clear vrrp
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]
no spf-interval
Syntax Description
Command Default
None
Command Modes
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
An LSA is used to advertise connected networks.
This command requires the Enterprise Services license.
Examples
The following example shows how to set the minimum interval time between arrivals of a LSA:
switch(config)# router isis firstcompanyswitch(config-router)# spf-interval level-1 500 500 500Related 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 | leak-map map-name| receive-only | redistributed]
no stub [direct | leak-map map-name| receive-only | redistributed]]
Syntax Description
Command Default
Disabled
Command Modes
Address-family configuration
Router configuration
Router VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
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.
This command requires the Enterprise Services license.
Usage Guidelines
The following example shows how to configure the router as a receive-only neighbor:
switch(config)# router eigrp 1switch(config-router)# stub receive-onlysummary-address
To create the 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
None
Command Modes
Address-family configuration
Router configuration
VRF configurationSupported User Rolesnetwork-admin
vdc-adminCommand 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 helps reduce the size of the routing table.
This command also reduces the size of the link-state packets (LSPs) and thus the link-state database (LSDB). It also helps network stability because a summary advertisement is depending on many more 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 the most optimal routing table for all individual destinations are used.
This command requires the Enterprise Services license.
Examples
The following example redistributes directly connected routes into IS-IS. This example advertises only 10.1.0.0 into the IS-IS level-1 link-state protocol data unit (PDU). The summary address is tagged with 100.
switch(config)# router isis 100switch(config-router)# address-family ipv4 unicastswitch(config-router-af)# redistribute direct route-map CORE1switch(config-router-af)# summary-address 10.1.0.0 255.255.0.0Related Commands
address-family
Enters the address family mode or a VRF address-family mode.
feature isis
Enables IS-IS on the router.
router isis
Enables IS-IS.
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
None
Command Modes
Router configuration
Supported User Rolesnetwork-admin
vdc-adminCommand 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 help 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.
This command requires the Enterprise Services license.
Examples
The following 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.
switch(config)# router ospf 201switch(config-router)# summary-address 192.0.0.0/16Related 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
None
Command Modes
Address-family configuration
Supported User Rolesnetwork-admin
vdc-adminCommand 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 help 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.
This command requires the Enterprise Services license.
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.
switch(config)# router ospfv3 201switch(config-router)# address-family ipv6 unicastswitch(config-router)# summary-address 2001:0DB8::0/16Related Commands
redistribute (OSPFv3
Redistributes external routing protocol routes into OSPFv3.
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.
suppress-inactive
no | default suppress-inactive
Syntax Description
This command has no keywords or arguments.
Command Default
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
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the suppress-inactive command to advertise only active routes to a BGP peer.
This command requires the Enterprise Services license.
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.
switch(config)# router bgp 64496switch(config-router)# neighbor 192.0.2.1/8 remote-as 64497switch(config-router-neighbor)# address-family ipv4 unicastswitch(config-router-neighbor af)# suppress-inactiveRelated Commands
