Table Of Contents
capability lls
capability vrf-lite
clear bgp nsap
clear bgp nsap dampening
clear bgp nsap external
clear bgp nsap flap-statistics
clear bgp nsap peer-group
clear ip bgp
clear ip bgp dampening
clear ip bgp external
clear ip bgp flap-statistics
clear ip bgp peer-group
clear ip eigrp neighbors
clear ip eigrp vrf neighbor
clear ip ospf
clear ip prefix-list
compatible rfc1583
dampening
default-information
default-information originate (RIP)
default-information originate (BGP)
default-information originate (IS-IS)
default-information originate (OSPF)
default-metric (BGP)
default-metric (EIGRP)
default-metric (OSPF)
default-metric (RIP)
discard-route
distance (IP)
distance bgp
distance eigrp
distance ospf
distribute-list in (BGP)
distribute-list in (IP)
distribute-list out (BGP)
distribute-list out (IP)
domain-password
domain-tag
eigrp log-neighbor-changes
eigrp log-neighbor-warnings
eigrp router-id
eigrp stub
exit-address-family
export map
flash-update-threshold
hello padding
hostname dynamic
capability lls
To enable the use of the Link-Local Signalling (LLS) data block in originated OSPF packets and reenable OSPF nonstop forwarding (NSF) awareness, use the capability lls command in router configuration mode. To disable LLS and OSPF NSF awareness, use the no form of this command.
capability lls
no capability lls
Syntax Description
This command has no arguments or keywords.
Defaults
LLS is enabled.
Command Modes
Router configuration
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
You might want to disable NSF awareness by disabling the use of the LLS data block in originated OSPF packets. You might want to disable NSF awareness if the router has no applications using LLS.
If NSF is configured and you try to disable LLS, you will receive the error message, "OSPF Non-Stop Forwarding (NSF) must be disabled first."
If LLS is disabled and you try to configure NSF, you will receive the error message, "OSPF Link-Local Signaling (LLS) capability must be enabled first."
Examples
The following example disables LLS support and OSPF NSF awareness:
capability vrf-lite
To suppress the Provider Edge (PE) specific checks on a router when the OSPF process is associated with the VRF, use the capability vrf-lite command in router configuration mode. To restore the checks, use the no form of this command.
capability vrf-lite
no capability vrf-lite
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled. PE specific checks are performed if the process is associated with VRF command modes.
Command Modes
Router configuration
Command History
Release
|
Modification
|
12.0(21)ST
|
This command was introduced.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(8)B
|
This command was integrated into Cisco IOS Release 12.2(8)B.
|
Usage Guidelines
This command works only if the OSPF process is associated with the VRF.
When the OSPF process is associated with the VRF, several checks are performed when link-state advertisements (LSAs) are received. PE checks are needed to prevent loops when the PE is performing a mutual redistribution between OSPF and BGP interfaces.
Type-3 LSA received
|
The DN bit is checked. If the DN bit is set, the Type-3 LSA is not considered during the SPF calculation.
|
Type-5 or -7 LSA received
|
If the Tag in the LSA is equal to the VPN-tag, the Type-5 or-7 LSA is not considered during the SPF calculation.
|
In some situations, performing PE checks might not be desirable. The concept of VRFs can be used on a router that is not a PE router (that is, a router that is not running BGP). With the capability vrf-lite command, the checks can be turned off to allow correct population of the VRF routing table with routes to IP prefixes.
Examples
This example shows a router configured with multi-VRF.
clear bgp nsap
To clear and then reset Connectionless Network Service (CLNS) network service access point (NSAP) Border Gateway Protocol (BGP) sessions, use the clear bgp nsap command in privileged EXEC mode.
clear bgp nsap {* | as-number | ip-address} [soft] [in | out]
Syntax Description
*
|
Clears and then resets all current BGP sessions.
|
as-number
|
Clears and then resets BGP sessions for BGP neighbors within the specified autonomous system.
|
ip-address
|
Clears the TCP connection to the specified BGP neighbor and removes all routes learned from the connection from the BGP table. The TCP connections are then reset.
|
soft
|
(Optional) Soft reset. Allows routing tables to be reconfigured and activated without clearing the BGP session.
|
in | out
|
(Optional) Triggers inbound or outbound soft reconfiguration. If the in or out option is not specified, both inbound and outbound soft reset are triggered.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
The clear bgp nsap command is similar to the clear ip bgp command, except that it is NSAP address family-specific.
Use of the clear bgp nsap command allows a reset of the neighbor sessions with varying degrees of severity, depending on the specified keywords and arguments.
Use the * keyword to reset all neighbor sessions. The software will clear and then reset the neighbor connections. Use this form of the command in the following situations:
•
BGP timer specification change
•
BGP administrative distance changes
Use the soft out keywords to clear and reset only the outbound neighbor connections. Inbound neighbor sessions will not be reset. Use this form of the command in the following situations:
•
Additions or changes are made to the BGP-related access lists
•
BGP-related weights change
•
BGP-related distribution lists change
•
BGP-related route maps change
Use the in keyword to clear only the inbound neighbor connections. Outbound neighbor sessions will not be reset. Use this form of the command in the following situations:
•
BGP-related access lists change or get additions
•
BGP-related weights change
•
BGP-related distribution lists change
•
BGP-related route maps change
Examples
The following example clears the inbound session with the neighbor 172.20.16.6 without the outbound session being reset:
Router# clear bgp nsap 172.20.16.6 in
The following example clears the outbound session with the neighbors in autonomous system 65000 without the inbound session being reset:
Router# clear bgp nsap 65000 soft out
Related Commands
Command
|
Description
|
show bgp nsap
|
Displays entries in the BGP routing table for the NSAP address family.
|
clear bgp nsap dampening
To clear Border Gateway Protocol (BGP) route dampening information for the network service access point (NSAP) address family and unsuppress the suppressed routes, use the clear bgp nsap dampening command in privileged EXEC mode.
clear bgp nsap dampening [nsap-prefix]
Syntax Description
nsap-prefix
|
(Optional) NSAP prefix about which to clear dampening information. This argument can be up to 20 octets long.
|
Defaults
When the nsap-prefix argument is not specified, the clear bgp nsap dampening command clears route dampening information for the entire BGP routing table for the NSAP address family.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
The clear bgp nsap dampening command is similar to the clear ip bgp dampening command, except that it is specific to the NSAP address family.
Examples
The following example clears route dampening information about the route to NSAP prefix 49.6001 and unsuppresses its suppressed routes:
Router# clear bgp nsap dampening 49.6001
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
show bgp nsap dampened-paths
|
Displays BGP dampened routes for the NSAP address family.
|
clear bgp nsap external
To clear all external Border Gateway Protocol (BGP) peers for the network service access point (NSAP) address family, use the clear bgp nsap external command in privileged EXEC mode.
clear bgp nsap external [soft] [in | out]
Syntax Description
soft
|
(Optional) Soft reset. Does not reset the session.
|
in | out
|
(Optional) Triggers inbound or outbound soft reconfiguration. If the in or out option is not specified, both inbound and outbound soft reset are triggered.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
The clear bgp nsap external command is similar to the clear ip bgp external command, except that it is specific to the NSAP address family.
Examples
The following example clears the inbound session with external BGP peers without the outbound session being reset:
Router# clear bgp nsap external soft in
Related Commands
Command
|
Description
|
clear bgp nsap
|
Resets an NSAP BGP connection by dropping all neighbor sessions.
|
clear bgp nsap flap-statistics
To clear Border Gateway Protocol (BGP) flap statistics for the network service access point (NSAP) address family, use the clear bgp nsap flap-statistics command in privileged EXEC mode.
clear bgp nsap flap-statistics [nsap-prefix] [regexp regexp | filter-list access-list-number]
Syntax Description
nsap-prefix
|
(Optional) NSAP prefix about which to clear dampening information. This argument can be up to 20 octets long.
|
regexp regexp
|
(Optional) Clears flap statistics for all the paths that match the regular expression.
|
filter-list access-list-number
|
(Optional) Clears flap statistics for all the paths that pass the access list. The acceptable access list number range is from 1 to 199.
|
Defaults
No statistics are cleared.
If no arguments or keywords are specified, the software clears flap statistics for all routes.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
The clear bgp nsap flap-statistics command is similar to the clear ip bgp flap-statistics command, except that it is specific to the NSAP address family.
The flap statistics for a route are also cleared when an NSAP BGP peer is reset. Although the reset withdraws the route, no penalty is applied in this instance even though route flap dampening is enabled.
Examples
The following example clears all of the flap statistics for paths that pass access list 3:
Router# clear bgp nsap flap-statistics filter-list 3
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
show bgp nsap flap-statistics
|
Displays BGP flap statistics for the NSAP address family.
|
clear bgp nsap peer-group
To clear the Border Gateway Protocol (BGP) TCP connections to all members of a BGP peer group for the network service access point (NSAP) address family, use the clear bgp nsap peer-group command in privileged EXEC mode.
clear bgp nsap peer-group peer-group-name
Syntax Description
peer-group-name
|
Name of the NSAP BGP peer group.
|
Defaults
No BGP TCP connections are cleared.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
The clear bgp nsap peer-group command is similar to the clear ip bgp peer-group command, except that it is specific to the NSAP address family.
Examples
The following example shows the BGP TCP connections being cleared for all members of the NSAP BGP peer group named internal:
Router# clear bgp nsap peer-group internal
Related Commands
Command
|
Description
|
neighbor peer-group (assigning members)
|
Configures a BGP neighbor to be a member of a peer group.
|
clear ip bgp
To reset a BGP connection using BGP soft reconfiguration, use the clear ip bgp command in privileged EXEC mode at the system prompt.
clear ip bgp {* | neighbor-address | peer-group-name} [soft [in | out]]
Syntax Description
*
|
Specifies that all current BGP sessions will be reset.
|
neighbor-address
|
Specifies that only the identified BGP neighbor will be reset.
|
peer-group-name
|
Specifies that the specified BGP peer group will be reset.
|
soft
|
(Optional) Soft reset. Does not reset the session.
|
in | out
|
(Optional) Triggers inbound or outbound soft reconfiguration. If the in or out option is not specified, both inbound and outbound soft reset is triggered.
|
Defaults
No reset is initiated.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(6)T
|
The dynamic inbound soft reset capability was added.
|
12.0(2)S
|
The dynamic inbound soft reset capability was added.
|
Usage Guidelines
You can reset inbound routing table updates dynamically or by generating new updates using stored update information. Using stored update information required additional memory for storing the updates.
To reset inbound routing table updates dynamically, all BGP routers must support the route refresh capability. To determine whether a BGP router supports this capability, use the show ip bgp neighbors command. If a router supports the route refresh capability, the following message is displayed:
Received route refresh capability from peer.
If all BGP routers support the route refresh capability, use the clear ip bgp {* | address | peer-group-name} in command. You need not use the soft keyword, because soft reset is automatically assumed when the route refresh capability is supported.
To generate new inbound updates from stored update information (rather than dynamically) without resetting the BGP session, you must preconfigure the local BGP router using the neighbor soft-reconfiguration inbound command. This preconfiguration causes the software to store all received updates without modification regardless of whether an update is accepted by the inbound policy. Storing updates is memory intensive and should be avoided if possible.
Outbound BGP soft configuration has no memory overhead and does not require any preconfiguration. You can trigger an outbound reconfiguration on the other side of the BGP session to make the new inbound policy take effect.
Use this command whenever any of the following changes occur:
•
Additions or changes to the BGP-related access lists
•
Changes to BGP-related weights
•
Changes to BGP-related distribution lists
•
Changes to BGP-related route maps
Examples
The following example clears the inbound session with the neighbor 10.108.1.1 without resetting the session:
Router# clear ip bgp 10.108.1.1 soft in
The following example clears the outbound session with the peer group named corp without resetting the session:
Router# clear ip bgp corp soft out
Related Commands
Command
|
Description
|
neighbor soft-reconfiguration
|
Configures the Cisco IOS software to start storing updates.
|
show ip bgp
|
Displays entries in the BGP routing table.
|
clear ip bgp dampening
To clear BGP route dampening information and unsuppress the suppressed routes, use the clear ip bgp dampening command in privileged EXEC mode.
clear ip bgp dampening [ip-address network-mask]
Syntax Description
ip-address
|
(Optional) IP address of the network about which to clear dampening information.
|
network-mask
|
(Optional) Network mask applied to the ip-address argument.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Examples
The following example clears route dampening information about the route to network 192.168.0.0 and unsuppresses its suppressed routes. When the address and mask arguments are not specified, the clear ip bgp dampening command clears route dampening information for the entire BGP routing table.
Router# clear ip bgp dampening 192.168.0.0 255.255.0.0
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
show ip bgp dampened-paths
|
Displays BGP dampened routes.
|
clear ip bgp external
To clear external Border Gateway Protocol (eBGP) peers, use the clear ip bgp external command in privileged EXEC mode.
clear ip bgp external [in | out]
clear ip bgp external [soft [in | out]]
clear ip bgp external {ipv4 | ipv6 {multicast | unicast [in | out | soft]}}
clear ip bgp external [vpn4 unicast {in | out | soft}}
Syntax Description
in | out
|
(Optional) Triggers inbound or outbound soft reconfiguration.
|
soft
|
(Optional) Triggers soft reconfiguration.
|
ipv4 | ipv6 | vpn4
|
(Optional) Triggers reset of IPv4, IPv6, or VPNn4 address family session.
|
multicast
|
(Optional) Triggers reset of IPv4 or IPv6 multicast address family session.
|
unicast
|
(Optional) Triggers reset of IPv4, IPv6, or VPNv4 unicast family session.
|
Defaults
A reset is not initiated.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(2)S
|
This command was introduced.
|
Usage Guidelines
Using the clear ip bgp external command without the soft keyword will reset the session.
Examples
The following examples clear an inbound session with the eBGP peers:
Router# clear ip bgp external in
or
clear ip bgp external soft in
The following example clears an outbound address family IPv4 multicast session with the eBGP peers:
Router# clear ip bgp external ipv4 multicast out
Related Commands
Command
|
Description
|
clear ip bgp
|
Resets a BGP connection or session.
|
neighbor soft-reconfiguration
|
Configures the Cisco IOS software to start storing updates.
|
show ip bgp
|
Displays entries in the BGP routing table.
|
clear ip bgp flap-statistics
To clear BGP flap statistics, use the clear ip bgp flap-statistics command in privileged EXEC mode.
clear ip bgp flap-statistics [{regexp regexp} | {filter-list list-name} | {ip-address network-mask}]
clear ip bgp [ip-address] flap-statistics
Syntax Description
ip-address
|
(Optional) Clears flap statistics for a single entry at this IP address. If this argument is placed before flap-statistics, the router clears flap statistics for all paths from the neighbor at this address.
|
regexp regexp
|
(Optional) Clears flap statistics for all the paths that match the regular expression.
|
filter-list list-name
|
(Optional) Clears flap statistics for all the paths that pass the access list.
|
network-mask
|
(Optional) Network mask applied to the ip-address argument.
|
Defaults
No statistics are cleared.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Usage Guidelines
If no arguments or keywords are specified, the router will clear BGP flap statistics for all routes.
The flap statistics for a route are also cleared when a BGP peer is reset. Although the reset withdraws the route, no penalty is applied in this instance even though route flap dampening is enabled.
Examples
The following example clears all of the flap statistics for paths that pass filter list 3:
Router# clear ip bgp flap-statistics filter-list 3
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
clear ip bgp peer-group
To clear all the members of a BGP peer group, use the clear ip bgp peer-group command in privileged EXEC mode.
clear ip bgp peer-group tag
Syntax Description
tag
|
Name of the BGP peer group to clear.
|
Defaults
No BGP peer group members are cleared.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Examples
The following example clears all members from the BGP peer group named internal:
Router# clear ip bgp peer-group internal
Related Commands
Command
|
Description
|
neighbor peer-group (assigning members)
|
Configures a BGP neighbor to be a member of a peer group.
|
clear ip eigrp neighbors
To delete entries from the neighbor table, use the clear ip eigrp neighbors command in EXEC mode.
clear ip eigrp neighbors [ip-address | interface-type interface-number]
Syntax Description
ip-address
|
(Optional) Address of the neighbor.
|
interface-type interface-number
|
(Optional) Interface type and number. Specifying these arguments removes the specified interface type from the neighbor table that all entries learned via this interface.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following example removes the neighbor whose address is 172.16.8.3:
Router# clear ip eigrp neighbors 172.16.8.3
Related Commands
Command
|
Description
|
show ip eigrp interfaces
|
Displays information about interfaces configured for EIGRP.
|
clear ip eigrp vrf neighbor
To clear neighbor entries of the specified Enhanced Interior Gateway Routing Protocol (EIGRP) virtual routing and forwarding instance (VRF) from the Routing Information Base (RIB), use the clear ip eigrp vrf command in privileged EXEC mode.
clear ip eigrp vrf {vrf-name as-number} neighbor [interface-number]
Syntax Description
vrf-name
|
Specifies the name of the VRF whose EIGRP neighbors will be cleared. The * keyword can be used as a wild card to specify all VRFs
|
as-number
|
Specifies the autonomous system number of the VRF whose neighbors will be cleared.
|
interface-number
|
(optional) Specifies the interface that VRF neighbors were learned through. The exact interface is specified by interface number with the interface-number argument.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(15)T
|
This command was integrated into 12.2(15)T.
|
Examples
The following example clears EIGRP neighbors reached through the VRF named VRF-RED in autonomous system 101:
clear ip eigrp vrf VRF-RED 101 neighbor
The following example clears EIGRP neighbors reached through the VRF named VRF-GREEN in autonomous-system 101 learned through Ethernet interface 0/0:
clear ip eigrp vrf VRF-RED 101 neighbor ethernet 0/0
Related Commands
Command
|
Description
|
show ip eigrp vrf interfaces
|
Displays EIGRP interfaces that are defined under the specified VRF.
|
show ip eigrp vrf neighbors
|
Displays neighbors discovered by EIGRP that carry VRF information.
|
show ip eigrp vrf topology
|
Displays VRF entries in the EIGRP topology table.
|
show ip eigrp vrf traffic
|
Displays EIGRP VRF traffic statistics.
|
show ip route vrf
|
Displays routing protocol information that is associated with a VRF.
|
clear ip ospf
To clear redistribution based on the OSPF routing process ID, use the clear ip ospf command in privileged EXEC mode.
clear ip ospf [pid] {process | redistribution | counters [neighbor [neighbor-interface]
[neighbor-id]]}
Syntax Description
pid
|
(Optional) Process ID.
|
process
|
Reset OSPF process.
|
redistribution
|
Clear OSPF route redistribution.
|
counters
|
OSPF counters.
|
neighbor
|
(Optional) Neighbor statistics per interface.
|
neighbor-interface
|
(Optional) Neighbor interface.
|
neighbor-id
|
(Optional) Neighbor ID.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
Use the pid argument to clear only one OSPF process. If the pid argument is not specified, all OSPF processes are cleared.
Examples
The following example clears all OSPF processes:
clear ip prefix-list
To reset the hit count of the prefix list entries, use the clear ip prefix-list command in privileged EXEC mode.
clear ip prefix-list [prefix-list-name] [network/length]
Syntax Description
prefix-list-name
|
(Optional) The name of the prefix list from which the hit count is to be cleared.
|
network/length
|
(Optional) The network number and length (in bits) of the network mask. The slash mark is required.
|
Defaults
Does not clear the hit count.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
The hit count is a value indicating the number of matches to a specific prefix list entry.
Examples
The following example clears the hit count from the prefix list entries for the prefix list named first_list that match the network mask 10.0.0.0/8:
Router# clear ip prefix-list first_list 10.0.0.0/8
Related Commands
Command
|
Description
|
distribute-list in (IP)
|
Filters networks received in updates.
|
distribute-list out (IP)
|
Suppresses networks from being advertised in updates.
|
ip prefix-list
|
Creates an entry in a prefix list.
|
ip prefix-list description
|
Adds a text description of a prefix list.
|
ip prefix-list sequence-number
|
Enables the generation of sequence numbers for entries in a prefix list.
|
redistribute (IP)
|
Redistributes routes from one routing domain into another routing domain.
|
show ip bgp regexp
|
Displays information about a prefix list or prefix list entries.
|
compatible rfc1583
To restore the method used to calculate summary route costs per RFC 1583, use the compatible rfc1583 command in router configuration mode. To disable RFC 1583 compatibility, use the no form of this command.
compatible rfc1583
no compatible rfc1583
Syntax Description
This command has no arguments or keywords.
Defaults
Compatible with RFC 1583.
Command Modes
Router configuration
Command History
Release
|
Modification
|
12.1(2)T
|
This command was introduced.
|
Usage Guidelines
This command is backward compatible with Cisco IOS Release 12.0.
To minimize the chance of routing loops, all OSPF routers in an OSPF routing domain should have RFC compatibility set identically.
Because of the introduction of RFC 2328, OSPF Version 2, the method used to calculate summary route costs has changed. Use the no compatible rfc1583 command to enable the calculation method used per RFC 2328.
Examples
The following example specifies that the router process is compatible with RFC 1583:
router ospf 1
compatible rfc1583
dampening
To configure a router to automatically dampen a flapping interface, use the dampening command in interface configuration mode. To disable automatic route dampening, use the no form of this command.
dampening[half-life-period reuse-threshold] [suppress-threshold max-suppress-time
[restart-penalty]]
no dampening
Syntax Description
half-life-period
|
(optional) Time (in seconds) after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period expires. The range of the half-life period is from 1 to 30 seconds. The default time is 5 seconds.
|
reuse-threshold
|
(optional) Reuse value based on the number of penalties. When the accumulated penalty decreases enough to fall below this value, the route is unsuppressed. The range of the reuse value is from 1 to 20000; the default is 1000.
|
suppress-threshold
|
(optional) Value of the accumulated penalty that triggers the router to dampen a flapping interface.A route is suppressed when its penalty exceeds this limit. The range is from 1 to 20000; the default is 2000.
|
max-suppress-time
|
(optional) Maximum time (in seconds) a route can be suppressed. The range is from 1 to 20000; the default is four times the half-life-period value. If the half-life-period value is allowed to default, the maximum suppress time defaults to 20 seconds.
|
restart-penalty
|
(optional) Penalty to applied to the interface when it comes up for the first time after the router reloads. The configurable range is from 1 to 20000 penalties. The default is 2000 penalties. This argument is not required for any other configurations.
|
Defaults
This command is disabled by default. To manually configure the timer for the restart-penalty argument, the value for all arguments must be manually entered.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
he IP Event Dampening feature will function on a subinterface but cannot be configured on only the subinterface. Only the primary interface can be configured with this feature, and all the subinterfaces are subject to the same dampening configuration.
When an interface is dampened, the interface is dampened to both IP and Connectionless Network Services (CLNS) routing equally. The interface is dampened to both IP and CLNS because integrated routing protocols like Intermediate System-to-Intermediate System (IS-IS), IP, and CLNS routing protocols are closely interconnected, so it is impossible to apply dampening separately.
This occurs because for integrated protocols like Intermediate System-to-Intermediate System (IS-IS), IP, and CLNS routing are closely interconnected, so it is impossible to apply dampening separately.
Copying a dampening configuration from virtual templates to virtual access interfaces is not supported because dampening has limited usefulness to existing applications using virtual templates. Virtual access interfaces are released when an interface flaps, and new connections and virtual access interfaces are acquired when the interface comes up and is made available to the network. Because dampening states are attached to the interface, the dampening states would not survive an interface flap.
If this command is applied to an interface that already has dampening configured, all dampening states are reset and the accumulated penalty will be set to 0. If the interface has been dampened, the accumulated penalty will fall into the reuse threshold range, and the dampened interface will be made available to the network. The flap counts, however, are retained.
Examples
The following example sets the half life to 30 seconds, the reuse threshold to 1500, the suppress threshold to 10000, and the maximum suppress time to 120 seconds:
dampening 30 1500 10000 120
The following example configures the router to apply a penalty of 500 on Ethernet interface 0/0 when the interface comes up for the first time after the router is reloaded:
dampening 5 500 1000 20 500
Related Commands
Command
|
Description
|
clear counters
|
Clears the interface counters.
|
show dampening interface
|
Displays a summary of interface dampening.
|
show interface dampening
|
Displays a summary of the dampening parameters and status.
|
default-information
To control the candidate default routing information or Enhanced Interior Gateway Routing Protocol (EIGRP) processes, use the default-information command in router configuration mode. To suppress EIGRP candidate information in incoming or outbound updates, use the no default-information in command.
default-information {allowed {in | out} | in | out} [acl-number | acl-name]
no default-information {allowed {in | out} | in | out}
Syntax Description
allowed
|
Configures EIGRP to accept default routing information.
|
in
|
Configures EIGRP to accept exterior or default routing information.
|
out
|
Configures EIGRP to advertise external routing information.
|
acl-number
|
(Optional) Standard access list number from 1 to 99 or an expanded standard access list from 1300 to 1999.
|
acl-name
|
(Optional) Named standard access list.
|
Defaults
Normally, exterior routes are always accepted and default information is passed between EIGRP processes when redistribution occurs.
Command Modes
Router configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.2
|
The access-list-number and access-list-name arguments were added.
|
Usage Guidelines
The default network of 0.0.0.0 used by Routing Information Protocol (RIP) can be redistributed by EIGRP.
Examples
The following example allows exterior or default routes to be received by an EIGRP peer in autonomous system 23:
default-information originate (RIP)
To generate a default route into Routing Information Protocol (RIP), use the default-information originate command in router configuration mode. To disable this feature, use the no form of this command.
default-information originate [route-map map-name]
no default-information originate
Syntax Description
route-map map-name
|
(Optional) Routing process will generate the default route if the route map is satisfied.
|
Defaults
This command is disabled by default.
Command Modes
Router configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
The route map referenced in the default-information originate command cannot use an extended access list; it can use a standard access list.
Examples
The following example originates a default route (0.0.0.0/0) over a certain interface when 172.68.0.0/16 is present. Applying a condition (in this case a route map) to determine when the default route is originated is called "conditional default origination."
default-information originate route-map condition
route-map condition permit 10
access-list 10 permit 172.68.16.0 0.0.0.255
default-information originate (BGP)
To control the redistribution of a protocol or network into the BGP, use the default-information originate command in address family or router configuration mode. To disable this function, use the no form of this command.
default-information originate
no default-information originate
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Address family configuration
Router configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(7)T
|
Address family configuration mode was added.
|