(Optional) Displays statistics for all diagnostic signature IDs on a device. The statistics include diagnostic signature average run time, maximum run time, and the number of times the diagnostic signature was triggered, uninstalled, or maximum triggered times limit; associated with all diagnostic signature IDs on the device.

Command Default

If you do not specify any optional keywords and arguments, only the current diagnostic signature settings such as diagnostic signature status (enabled or disabled), profile, and environment variable, along with details associated with the downloaded diagnostic signature files, such as the diagnostic signature name, revision number, status, and last updated date and time are displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

15.3(2)T

This command was introduced.

Usage Guidelines

Use the show call-home diagnostic-signatureds-id command to display all attributes, such as, ID, name, functionality, event, action, prerequisites, prompts, and variables that are associated with a diagnostic signature file. If you want to view a particular aspect of the diagnostic signature file, use any of the optional keywords (actions,
events, prerequisite, prompt, or variables)
with the ds-id argument.

Use the show call-home diagnostic-signature failure command to display any malfunctions that occur with a diagnostic signature file or a set of diagnostic signature files during any of the following stages:

Downloading—The diagnostic signature fails while being downloaded onto a device.

Parsing—The diagnostic signature fails during parsing.

File saving—The diagnostic signature fails during file saving.

Acting—The diagnostic signature fails while performing an action on the device.

Unknown—The diagnostic signature fails due to an unknown factor.

Registration—The diagnostic signature fails during registration on a device.

Examples

The following is sample output from the show call-home diagnostic-signature command. The command output displays the active diagnostic signature profile prof-1, environment variable name ds_env1, and environment variable value value1.

registered—The diagnostic signature monitors and registers the predefined events and waits for such events to occur.

running—The diagnostic signature executes the specified actions for events that are registered.

terminated—The diagnostic signature is terminated and unregistered when a diagnostic signature has performed the specified action for the maximum number of times.

pending—The diagnostic signature is in a pending state when some required environment variable has no value configured. In the case of an interactive diagnostic signature, it must be manually installed using the call-home diagnostic-signature install command.

Last Update

The date and time when the diagnostic signature file was last updated on the device through periodic or on-demand download.

Functionality

event trigger

action

The functionality of a particular diagnostic signature file.

The event trigger indicates the event when the diagnostic signature performs a specific action.

The action indicates the specific action that the diagnostic signature performs when an event occurs.

Event

Event tag

Type

Timer Type

Timer Detail

The event details defined within the diagnostic signature file.

Event tag indicates the event name.

Type indicates whether the event is checked for periodically or if the check is on an on-demand basis.

Timer Type and Timer Detail indicate the clock system and the time period assigned to check for the event.

Action

Type

Element List

DATA

The action defined within the diagnostic signature file.

Type indicates the kind of action that is performed in response to a certain event.

Element List and DATA indicate the various aspects of the device that are affected when the action is performed.

Triggered/Max/Deinstall

Triggered indicates the number of times a specific diagnostic signature was performed.

Max indicates the number of times specific diagnostic signature files are limit from being performed.

Deinstall indicates whether or not a particular diagnostic signature was subjected to uninstallation.

Average Run Time (sec)

The average time, in seconds, taken for a particular diagnostic signature file to execute its actions in response to the predefined events across various sessions on a device.

Max Run Time (sec)

The maximum time, in seconds, taken for a particular diagnostic signature file to perform its action in response to the predefined event for a particular session on a device.

Download-type

Type of downloading method for diagnostic signature files; either periodic or on-demand.

Periodic indicates that the diagnostic signature file downloading type is periodic, that is, the device is configured to automatically request for the download of new or updated diagnostic signature files at regular intervals.

Ondemand indicates that the diagnostic signature file downloading type is on-demand, that is, the device must be manually configured to request for the download of new or updated diagnostic signature files.

In-queue

Indicates the number of diagnostic signature files that are in the queue waiting to be downloaded on to the device. 0 indicates there are no files waiting in the queue.

Fail

Indicates the number of diagnostic signature files that failed while downloading. 0 indicates there is no failure during the download.

Success

Indicates the number of diagnostic signature files that are successfully downloaded on to the device. 0 indicates no files have been downloaded.

Last request sent

The date and time when the last request for download was initiated from the device.

Stage

D—Download

P—Parsing

F—File saving

A—Acting

U—Unknown

R—Registration

S—Sign Verification

Indicates the stage when the diagnostic signature failed.

Last Failed Time

Indicates the date and time when the diagnostic signature failed.

Error String

Indicates the errors associated with the diagnostic signature failure.

Related Commands

Command

Description

call-home diagnostic-signature

Downloads, installs, and uninstalls diagnostic signature files on a device.

diagnostic-signature

Enables the diagnostic signature feature on a device.

show cef nsf

To show the current Cisco nonstop forwarding (NSF) state of Cisco Express Forwarding on both the active and standby Route Processors (RPs), use the
showcefnsfcommand in privileged EXEC mode.

showcefnsf

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(22)S

This command was introduced.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(20)S

Support for the Cisco 7304 router was added.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

Command History

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

If you enter the
showcefnsf command before a switchover occurs, no switchover activity is reported. After a switchover occurs, you can enter the
showcefnsf command to display details about the switchover as reported by the newly active RP. On the Cisco 12000 and 7500 series Internet routers, details about line card switchover are also provided.

show ip rsvp high-availability counters

To display all Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) counters that are being maintained by a Route Processor (RP), use the
show ip rsvp high-availability counters command in user EXEC or privileged EXEC mode.

showiprsvphigh-availabilitycounters

Syntax Description

This command has no arguments or keywords.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRA

This command was introduced.

12.2(33)SRB

Support for In-Service Software Upgrade (ISSU) was added.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

15.0(1)S

This command was modified. The output was updated to display information for point-to-point (P2P) and point-to-multipoint traffic engineering (P2MP) counters.

15.2(2)S

This command was modified. The output was enhanced to show checkpoint information for MPLS traffic engineering autotunnel and automesh stateful switchover (SSO) tunnels.

Cisco IOS XE Release 3.6S

This command was modified. The output was enhanced to show checkpoint information for MPLS traffic engineering autotunnel and automesh stateful switchover (SSO) tunnels.

Usage Guidelines

Use the
show ip rsvp high-availability counters command to display the HA counters, which include state, ISSU, checkpoint messages, resource failures, and errors.

The command output differs depending on whether the RP is active or standby. (See the “Examples” section for more information.)

Use the
clear ip rsvp high-availability counters command to clear all counters.

Examples

The following is sample output from the
show ip rsvp high-availability counters command on the active RP:

The table below describes the significant fields shown in the display.

Table 8 show ip rsvp interface detail Field Descriptions

Field

Description

RSVP

Status of the Resource Reservation Protocol (RSVP) (Enabled or Disabled).

Interface State

Status of the interface (Up or Down).

Curr allocated

Amount of bandwidth (in bits per second [b/s]) currently allocated.

Max. allowed (total)

Total maximum amount of bandwidth (in b/s) allowed.

Max. allowed (per flow)

Maximum amount of bandwidth (in b/s) allowed per flow.

Max. allowed for LSP tunnels using sub-pools

Maximum amount of bandwidth permitted for the label switched path (LSP) tunnels that obtain their bandwidth from subpools.

Tunnel IP Overhead percent

Overhead percent to override the RSVP bandwidth manually.

Tunnel Bandwidth considered

Indicates if the tunnel bandwidth is considered.

DSCP value used in RSVP msgs

Differentiated services code point (DSCP) value in the RSVP messages.

show isis nsf

To display current state information regarding Intermediate System-to-Intermediate System (IS-IS) Cisco nonstop forwarding (NSF), use the
showisisnsf command in user EXEC mode.

showisisnsf

Syntax Description

This command has no arguments or keywords.

Command Modes

User EXEC

Command History

Release

Modification

12.0(22)S

This command was introduced.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(20)S

Support for the Cisco 7304 router was added.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

Theshowisisnsfcommand can be used with both Cisco proprietary IS-IS NSF and Internet Engineering Task Force (IETF) IS-IS NSF. The information displayed when this command is entered depends on which protocol has been configured. To configure nsf for a specific routing protocol, use the
routerbgp,
routerospf, or
routerisis commands in global configuration mode.

Examples

The following example shows state information for an active RP that is configured to use Cisco proprietary IS-IS NSF:

Related Commands

Command

Description

debugisisnsf

Displays information about the IS-IS state during an NSF restart.

nsf(IS-IS)

Configures NSF operations for IS-IS.

nsft3

Specifies the methodology used to determine how long IETF NSF will wait for the LSP database to synchronize before generating overloaded link state information for itself and flooding that information out to its neighbors.

nsfinterfacewait

Specifies how long a NSF restart will wait for all interfaces with IS-IS adjacencies to come up before completing the restart.

nsfinterval

Specifies the minimum time between NSF restart attempts.

showclnsneighbors

Displays both ES and IS neighbors.

show issu

To display Enhanced Fast Software Upgrade (eFSU) information, use the
show issu command.

Related Commands

Command

Description

issu

Sets up an Enhanced Fast Software Upgrade (eFSU).

show issu clients

To display a list of the current In Service Software Upgrade (ISSU) clients--that is, the network applications and protocols supported by ISSU--use the
showissuclientscommand in user EXEC or privileged EXEC mode.

showissuclients

Syntax Description

This command has no arguments or keywords.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

12.2(33)SRE

This command was integrated into Cisco IOS Release 12.2(33)SRE.

Usage Guidelines

This command lists all ISSU clients currently operating in the network, along with their Client ID numbers and the number of entities each client contains.

You should enter this command before you enter the
issurunversion command, because if a client (application or protocol) that needs to continue operating in the network does not appear in the displayed list, you will know not to continue the software upgrade (because proceeding further with ISSU would then halt the operation of that application or protocol).

Examples

The following example shows a client list displayed by entering this command:

The table below describes the significant fields shown in the display.

Table 10 show issu clients Field Descriptions

Field

Description

Client_ID

The identification number used by ISSU for that client.

Client_Name

A character string describing the client.

“Base Clients” are a subset, which includes:

Inter-Process Communications (IPC)

Redundancy Framework (RF)

Checkpoint Facility (CF)

Cisco Express Forwarding

Network RF (for IDB stateful switchover)

EHSA Services (including ifIndex)

Configuration Synchronization.

Entity_Count

The number of entities within this client. An entity is a logical group of sessions with some common attributes.

Related Commands

Command

Description

showissumessagetypes

Displays the formats, versions, and size of ISSU messages supported by a particular client.

showissunegotiated

Displays results of a negotiation that occurred concerning message versions or client capabilities.

showissusessions

Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.

show issu comp-matrix

To display
information regarding the In Service Software Upgrade (ISSU) compatibility
matrix, use the
showissucomp-matrix command in user EXEC or privileged
EXEC mode.

showissucomp-matrix
{ negotiated
| stored
| xml }

Syntax Description

negotiated

Displays
ISSU negotiated matrix information.

stored

Displays
ISSU stored matrix information.

xml

Displays
ISSU XML matrix information.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This
command was introduced.

12.2(31)SGA

This
command was integrated into Cisco IOS Release 12.2(31)SGA.

12.2(33)SRB1

This
command was integrated into Cisco IOS Release 12.2(33)SRB1. Support for ISSU
was introduced on the Cisco 7600 series routers.

12.2(33)SRE

This
command was integrated into Cisco IOS Release 12.2(33)SRE.

Usage Guidelines

Perform an ISSU when
the Cisco software on both the active and the standby RP is capable of ISSU and
the old and new images are compatible. The compatibility matrix information
stores the compatibility among releases in the following manner:

Base-level
compatible—One or more of the optional HA-aware subsystems is not compatible.
An in-service upgrade or downgrade between these versions will succeed;
however, some subsystems will not be able to maintain state during the
transition. The matrix entry designates the images to be base-level compatible
(B). You can perform an ISSU upgrade without any functionality loss even if the
matrix entry is B. However, you might experience some functionality loss with a
downgrade, if the new image has additional functionality.

Incompatible—A
core set of system infrastructure exists that interoperates in a stateful
manner for SSO to function correctly. If any of these required features or
protocols is not interoperable, the two versions of the Cisco software images
are declared to be incompatible. An in-service upgrade or downgrade between
these versions is not possible. The matrix entry designates the images to be
incompatible (I). When the Cisco IOS versions at the active and standby
supervisor engines are incompatible, the system operates in route processor
redundancy (RPR) mode.

Note

when you try to perform an ISSU with a peer that does not support
ISSU, the system automatically uses RPR mode.

The compatibility
matrix represents the compatibility relationship a Cisco software image has
with all other Cisco software versions within the designated support window
(for example, all the software versions the image is aware of) and is populated
and released with every image. The matrix stores compatibility information
between its own release and prior releases. It is always the current release
that contains latest information about compatibility with existing releases in
the field. The compatibility matrix is available within the Cisco software
image and on Cisco.com so that users can determine in advance whether an
upgrade can be done using the ISSU process.

Use the
show issu comp-matrix
negotiated command to display information on the negotiation of
the compatibility matrix data between two software versions on a device.

Compatibility
matrix data is stored with each Cisco software image that supports the ISSU
capability. Use the
show issu comp-matrix
stored to display stored compatibility matrix information.

Examples

The following is
sample output from the
show issu comp-matrix
negotiated command:

The following table describes the significant fields in the order in
which they appear in the displays.

Table 11 show issu comp-matrix Field
Description

Field

Description

CardType

The type of line card installed in the slot.

Uid

The unique identification number for the current endpoint.

Image Ver

The image verison installed on the device.

Image Name

The name of the image installed on the device.

Cid

The identification number used by ISSU for the client.

Eid

The identification number used by ISSU for each entity within
this client.

Sid

The identification number of the session being reported on.

pSid

The peer session ID at the other endpoint.

pUid

The peer unique ID on the other endpoint where the session
terminates.

Compatibility

The compatibility status means that the ISSU session is
compatible.

GrpId

The group ID number of the message group used for the session.

Client Name

The client name used for the image to interoperate.

Base/Non-Base

The client required for the image to interoperate.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients—that is, the applications
and protocols on this network supported by ISSU.

showissusessions

Displays detailed information about a particular ISSU
client—including whether the client status for the impending software upgrade
is Compatible.

show issu entities

To display information about entities within one or more In Service Software Upgrade (ISSU) clients, use the
showissuentitiescommand in user EXEC or privileged EXEC mode.

showissuentities [client-id]

Syntax Description

client-id

(Optional) The identification number of a single ISSU client.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

Usage Guidelines

An entity is a logical group of sessions that possess some common attributes. Enter a Client_ID if you are interested in seeing information only about one client’s entities. If a Client_ID is not specified, the command will display all ISSU clients’ entities known to the device.

If you are not sure of the precise Client_ID number to enter for the client you are interested in, use the
showissuclients command to display the current list of clients with their names and ID numbers.

Examples

The following example shows detailed information about the entities within the virtual routing and forwarding (VRF) (“Table ID”) client:

The identification number used by ISSU for each entity within this client.

Entity_Name

A character string describing the entity.

MsgType Count

The number of message types within the identified entity.

MsgGroup Count

The number of message groups within the identified entity. A message group is a list of message types.

CapType Count

The number of capability types within the identified entity.

CapEntry Count

The number of capability entries within the identified entity. A capability entry is a list of all mutually dependent capability types within a particular client session and, optionally, other capability types belonging to that client session.

CapGroup Count

The number of capability groups within the identified entity. A capability group is a list of capability entries given in priority sequence.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications and protocols on this network supported by ISSU.

showissusessions

Displays detailed information about a particular ISSU client--including whether the client status for the impending software upgrade is COMPATIBLE.

show issu message types

To display formats (“types”), versions, and maximum packet size of the In Service Software Upgrade (ISSU) messages supported by a particular client, use the
showissumessagetypescommand in user EXEC or privileged EXEC mode.

showissumessagetypesclient-id

Syntax Description

client-id

The identification number used by ISSU for a client application.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

Usage Guidelines

If you are not sure of the Client_ID number to enter into this command, use the
showissuclients command. It displays the current list of clients, along with their names and ID numbers.

The table below describes the significant fields shown in the display.

Table 13 show issu message types Field Descriptions

Field

Description

Client_ID

The identification number used by ISSU for this client.

Entity_ID

The identification number used by ISSU for this entity.

Message_Type

An identification number that uniquely identifies the format used in the ISSU messages conveyed between the two endpoints.

Version_Range

The lowest and highest message-version numbers contained in the client application.

Message_Ver

Message version. Because each client application contains one or more versions of its messages, ISSU needs to discover these versions and negotiate between the new and old system software which version to use in its preparatory communications.

Message_Mtu

Maximum size (in bytes) of the transmitted message.

A value of 0 means there is no restriction on size; fragmentation and reassembly are therefore being handled in a manner transparent to the ISSU infrastructure.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications on this network supported by ISSU.

showissunegotiated

Displays results of a negotiation that occurred concerning message versions or client capabilities.

showissusessions

Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.

show issu negotiated

To display details of the session’s negotiation about message version or client capabilities, use the
showissunegotiatedcommand in user EXEC or privileged EXEC mode.

showissunegotiated
{ version | capability }
session-id

Syntax Description

version

Displays results of a negotiation about versions of the messages exchanged during the specified session, between the active and standby endpoints.

capability

Displays results of a negotiation about the client application’s capabilities for the specified session.

session-id

The number used by In Service Software Upgrade (ISSU) to identify a particular communication session between the active and the standby devices.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

Usage Guidelines

If you are not sure of the session_ID number to enter into this command, enter the
showissusessions command. It will display the session_ID.

Examples

The following example displays the results of a negotiation about message versions:

The table below describes the significant fields shown in the display.

Table 15 show issu negotiated capability Field Descriptions

Field

Description

Session_ID

The identification number of the session being reported on.

Negotiated_Cap_Entry

A numeral that stands for a list of the negotiated capabilities in the specified client session.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications on this network supported by ISSU.

showissumessagetypes

Displays the formats, versions, and maximum packet size of ISSU messages supported by a particular client.

showissusessions

Displays detailed information about a particular ISSU client, including whether the client status is compatible for the impending software upgrade.

show issu outage

To display the maximum outage time for installed line cards during an in service software upgrade (ISSU), use the
showissuoutage command from the switch processor (SP) console.

showissuoutageslot
{ slot-num | all }

Syntax Description

slot-num

Displays the maximum outage time for the line card in the specified slot.

all

Displays the maximum outage time for all installed line cards.

Command Modes

SP console

Command History

Release

Modification

12.2(33)SRB1

This command was introduced on Cisco 7600 series routers.

Usage Guidelines

Once the new software is downloaded onto the router (after you issue the
issuloadversion command), you can issue
showissuoutageslotall from the SP console to display the maximum outage time for installed line cards.

During an ISSU, the router preloads line card software onto line cards that support enhanced Fast Service Upgrade (eFSU). Then, when the switchover occurs between active and standby processors, the line cards that support eFSU are restarted with the new, preloaded software, which helps to minimize outage time during the upgrade. Line cards that do not support eFSU undergo a hard reset at switchover, and the software image is loaded after the line card is restarted.

The output for the
showissuoutage command shows the type of reload that the line card will perform along with the maximum outage time (see the “Examples” section).

Note

In the MDR Mode field of the command output, NSF_RELOAD indicates that the line card will not be reloaded, which means that outage time will be 0 to 3 seconds. NSF_RELOAD applies only to ISSU upgrades between two software releases that have the same line card software.

Examples

The following command examples show the maximum outage time for installed line cards:

The type of software reload that the line card will perform after the ISSU switchover:

NSF_RELOAD indicates that the line card will undergo an SSO/NSF type of switchover, which means that the line card will not be restarted or reloaded. This option applies only to ISSU upgrades between two software releases that have the same line card software.

WARM_RELOAD indicates that software was preloaded onto the line card, but the line card must be restarted with the new software. This option is equivalent to a soft reset of the line card.

RELOAD indicates that software was not preloaded onto the line card, which means that the line card will be reloaded. This option is equivalent to a hard reset of the line card.

INVALID indicates that you entered the
showissuoutage command outside the ISSU command sequence.

Max Outage Time

The length of time the line card will be unavailable after it is restarted.

Related Commands

Command

Description

issuloadversion

Starts the ISSU process.

show issu patch

To provide information about upgrade installation on both active and standby routers, use the
showissupatchcommand in privileged EXEC mode.

showissupatch
{ pendingdisk | context | type
{ image | patch } }

Syntax Description

pending

Provides information about the impact of a pending upgrade.

disk

The disk on which the upgrade will occur.

context

Provides information about the installation and upgrade during the upgrade procedure.

type

Provides information about the patch or image to which the system is being upgraded.

image

Provides information about the image to which the system is being upgraded.

patch

Provides information about the upgrade.

Command Default

No information about the upgrade is displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SXI

This command was introduced.

Usage Guidelines

Theshowissupatchcommand provides an overview of the impact on a system upgrade before and during the upgrade procedure.

Examples

The following example provides information about a pending upgrade on disk0:

The command output shows the overall impact of an upgrade on a specified disk.

Search Root: disk0:/sys

Disk on which the upgrade will occur.

Type of upgrade: New base image

Type of upgrade. The upgrade could be a new image or a patch.

Action: Go Standby

Activates the upgrade on the standby router.

Slot #

Slot number on the router.

Card type

Type of card installed in the specified slot.

Impacted

States whether or not the card in the specified slot is affected by the upgrade.

show issu platform img-dnld

To display the progression of image download from slave to the Versatile Interface Processors (VIPs) and to display Minimal Disruptive Restart (MDR) details on Cisco 7600 series routers, use the
showissuplatformimg-dnldcommand in user EXEC or privileged EXEC mode.

showissuplatformimg-dnld

Syntax Description

This command has no arguments or keywords.

Command Default

This command is disabled by default.

Command Modes

User EXEC Privileged EXEC

Command History

Release

Modification

12.2(33)SRB

This command was introduced.

Usage Guidelines

The
showissuplatformimg-dnld command is specific to Cisco 7600 series routers.

The
showissuplatformimg-dnld command provides information to help you troubleshoot problems that may occur when performing an enhanced Fast Software Upgrade (eFSU). Entering this command allows you to display the progression of the image download from the slave unit to the VIPs and to display other details such as the following:

Percentage completion of image downloads to the VIPs

For each VIP in the router, the following is displayed:

The name of the VIP

Whether the slot is enabled

Whether a specified slot supports MDR

How much free memory is available if a slot is MDR-feasible

A message about image download if a slot supports MDR

Information regarding whether single line card reload (SLCR) is enabled

Number of MDR nonsupported slots

Number of nonempty slots

Number of line cards

Number of MDR-feasible cards

Number of MDR-incapable cards

Number of MDR-capable cards

MDR-ready cards

This command is available for eFSU on the Cisco 7600 series router platform only.

Examples

The following example output displays information before the download has been started:

Slot 9, which holds a VIP6-80 RM7000B line card, supports MDR and has approximately 205 MB of free space.

SLCR : enabled

SLCR is enabled.

MDR Unsupported slots: 1 5

Slots holding line cards that are MDR-feasible but do not have enough memory in the VIP to download the image.

MDR Supported slots: 9

Slots holding line cards that are MDR-capable.

No. of Non empty slots: 5

Total number of nonlegacy cards, legacy cards, and Route Processors (RPs) in the router.

No. of Line cards : 3

Total number of nonlegacy line cards.

No. of MDR feasible cards:1

Total number of nonlegacy line cards that are one of the following types:

VIP 4-50 controller

VIP 4-80 controller

VIP 6-80 controller

GEIP+ controller.

No. of MDR Incapable cards : 2

Total number of slots holding MDR unsupported line cards.

No. of MDR capable cards: 1 (0 LC(s) disabled)

Total number of line cards that are both MDR-feasible and have free memory to support at least image size plus 5 MB.

MDR ready cards: 0

Line cards in which the image has been downloaded.

The following sample output occurred during image download. The example shows that 25 percent of the image is downloaded to VIPs. Because slot 1 and slot 5 are not MDR supported, these two line cards will be reloaded during switchover.

Related Commands

Cancels the ISSU upgrade or downgrade process in progress and restores the router to its state before the process had started.

issuacceptversion

Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.

issucommitversion

Allows the new Cisco IOS software image to be loaded into the standby RP.

issurunversion

Forces a switchover of the active to the standby processor and causes the newly active processor to run the new image.

showissustate

Displays the state and current version of the RPs during the ISSU process.

show issu rollback timer

To display the current setting of the In Service Software Upgrade (ISSU) rollback timer, use the
showissurollbacktimercommand in user EXEC or privileged EXEC mode.

showissurollbacktimer

Syntax Description

This command has no arguments or keywords.

Command Default

The default rollback timer value is 45 minutes.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(28)SB2

Enhanced Fast Software Upgrade (eFSU) support was added on the Cisco 7500 series routers.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

12.2(33)SRE

This command was integrated into Cisco IOS Release 12.2(33)SRE.

Usage Guidelines

If the ISSU rollback timer value has never been set, then the default rollback timer value of 45 minutes is displayed.

Examples

The following example shows the default rollback timer value:

Router# show issu rollback-timer
Rollback Process State = Not in progress
Configured Rollback Time = 45:00

The table below describes the significant fields shown in the display.

Table 19 show issu rollback-timer Field Descriptions

Field

Description

Rollback Process State = Not in progress

State of the rollback process.

Configured Rollback Time = 45:00

Rollback timer value.

Related Commands

Command

Description

configureissusetrollbacktimer

Configures the rollback timer value.

show issu sessions

To display detailed information about a particular In Service Software Upgrade (ISSU) client--including whether the client status for the impending software upgrade is compatible--use the
showissusessionscommand in user EXEC or privileged EXEC mode.

showissusessionsclient-id

Syntax Description

client-id

The identification number used by ISSU for the client.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

12.2(33)SRE

This command was integrated into Cisco IOS Release 12.2(33)SRE.

Usage Guidelines

If you are not sure of the Client_ID number to enter into this command, use the
showissuclients command to display the current list of clients with their names and ID numbers.

Examples

The following example shows detailed information about the LDP Client:

The table below describes the significant fields shown in the display.

Table 20 show issu sessions Field Descriptions

Field

Description

Client_ID

The identification number used by ISSU for that client.

Entity_ID

The identification number used by ISSU for each entity within this client.

Session_ID

The identification number used by ISSU for this session.

Session_Name

A character string describing the session.

Peer UniqueID

An identification number used by ISSU for a particular endpoint, such as a Route Processor or line card (could be a value based on slot number, for example).

The peer that has the smaller unique_ID becomes the Primary (initiating) side in the capability and message version negotiations.

Peer Sid

Peer session ID.

Negotiate Role

Negotiation role of the endpoint: either PRIMARY (in which case the device initiates the negotiation) or PASSIVE (in which case the device responds to a negotiation initiated by the other device).

Negotiated Result

The features (“capabilities”) of this client’s new software were found to be either COMPATIBLE or INCOMPATIBLE with the intended upgrade process.

(“Policy” means that an override of the negotiation result has been allowed by the software. Likewise, “no policy” means that no such override is present to be invoked).

Cap GroupID

Capability group ID: the identification number used for a list of distinct functionalities that the client application contains.

Msg GroupID

Message group ID: the identification number used for a list of formats employed when conveying information between the active device and the standby device.

Session Signature

Session signature: a unique ID to identify a current session in a shared negotiation scenario.

Nego_Session_ID

Negotiation session ID: the identification number used by ISSU for this negotiation session.

Nego_Session_Name

Negotiation session name: a character string describing this negotiation session.

Transport_Mtu

Maximum packet size (in bytes) of the ISSU messages conveyed between the two endpoints.

A value of 0 means there is no restriction on size; in this case, fragmentation and reassembly then are handled in a manner transparent to the ISSU infrastructure.

Related Commands

Command

Description

showissuclients

Lists the current ISSU clients--that is, the applications on this network supported by ISSU.

showissumessagetypes

Displays the formats, versions, and maximum packet size of ISSU messages supported by a particular client.

showissunegotiated

Displays results of a negotiation that occurred concerning message versions or client capabilities.

show issu state

To display the state and current version of the Route Processors (RPs) during the In Service Software Upgrade (ISSU) process, use the
showissustate command in user EXEC or privileged EXEC mode.

showissustate
[ slot/port ]
[detail]

Syntax Description

slot

(Optional) PRE slot number.

port

(Optional) PRE port number.

detail

(Optional) Provides detailed information about the state of the active and standby RPs.

Command Modes

User EXEC (>) Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB

This command was introduced.

12.2(31)SGA

This command was integrated into Cisco IOS Release 12.2(31)SGA.

12.2(33)SRB

Enhanced Fast Software Upgrade (eFSU) support was added on the Cisco 7600 series routers.

In Service Software Upgrade (ISSU) is not supported in Cisco IOS Release 12.2(33)SRB.

12.2(33)SRB1

ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB1.

12.2(33)SRE

This command was integrated into Cisco IOS Release 12.2(33)SRE.

12.2(33)SCD2

This command was implemented on the Cisco CMTS routers in Cisco IOS Release 12.2(33)SCD2.

Usage Guidelines

Use the
showissustate command to display the state and current version of each RP.

It may take several seconds after the
issuloadversion command is entered for Cisco IOS software to load onto the standby RP and the standby RP to transition to stateful switchover (SSO) mode. If you enter the
showissustate command too soon, you may not see the information you need.

Examples

The following example displays the manner in which the ISSU state is verified.

The table below describes the significant fields shown in the display.

Note

Fields that are described after the Slot field under the “Standby RP” section in the table refer to the line card ISSU status.

Table 21 show issu state Field Descriptions

Field

Description

ActiveRP

Slot = A

The RP slot that is being used.

RP State = Active

State of this RP.

ISSU State = Init

The in service software upgrade (ISSU) process is in its initial state.

Boot Variable = N/A

The RP’s boot variable.

Operating Mode = SSO

The RP’s operating mode.

Primary Version = N/A

The primary software image running on the RP.

Secondary Version = N/A

The secondary software image running on the RP.

Current Version = disk0:c10k2-p11-mz.1.20040830

The current software image running on the RP.

StandbyRP

Slot = B

The slot/subslot number pair for line card.

RP State = Standby

State of this RP.

Slot

The slot number of the line card.

Red Role

Redundancy role of the line card.

Peer

The slot/ subslot pair of the protect line card.

Act/ Sby

The line card’s current redundancy status.

Image Match RP

Indicates if the line card image matches the image of the current active RP.

LC ISSU State

The current line card ISSU state.

ISSU Proc

Indicates the progress of the current ISSU state.

Related Commands

Command

Description

issuabortversion

Cancels the ISSU upgrade or downgrade process in progress and restores the router to its state before the process had started.

issuacceptversion

Halts the rollback timer and ensures the new Cisco IOS software image is not automatically aborted during the ISSU process.

issuchangeversion

Performs a single-step complete ISSU upgrade process cycle.

issucommitversion

Allows the new Cisco IOS software image to be loaded into the standby RP.

issuloadversion

Starts the ISSU process.

issurunversion

Forces a switchover of the active to the standby processor and causes the newly active processor to run the new image.

show mdr download image

To display the amount of memory needed to store the new software image on line cards that support enhanced Fast Software Upgrade (eFSU), use the
showmdrdownloadimagecommand from the switch processor (SP) console in privileged EXEC mode.

showmdrdownloadimage

Syntax Description

This command has no arguments or keywords.

Command Modes

SP console

Command History

Release

Modification

12.2(33)SRB1

This command was introduced on Cisco 7600 series routers.

Usage Guidelines

You must issue the
showmdrdownloadimage command from the SP console. You cannot issue the command from the line card or from the route processor (RP) console.

During an in service software upgrade (ISSU), the router preloads line card software onto line cards that support eFSU. As part of the software preload, the router automatically reserves memory on the line card to store the new software image (decompressed format).

You can use the
showmdrdownloadimage command to determine how much memory is needed on the line cards for the new software image.

Note

If a line card does not have enough memory available to hold the new software image, software preload fails and the card undergoes a reset during the software upgrade.

Examples

The following example shows how much memory will be reserved for the new software on the installed line cards:

Syntax Description

Specifies how far back from the current time you want to view messages. For example, you can display messages from the last 30 minutes.

minutes

Time argument in minutes. The time argument is specified in minutes format (mmm).

hours:minutes

Time argument in hours and minutes. The time argument is specified in hours and minutes format (hh:mm).

clock

Displays event trace messages starting from a specific clock time in hours and minutes format (hh:mm).

daymonth

(Optional) The day of the month from 1 to 31 and the name of the month of the year.

from-boot

Displays event trace messages starting after booting.

seconds

(Optional) Specified number of seconds to display event trace messages after booting. Range: 0 to the number of seconds elapsed since the boot.

latest

Displays only the event trace messages since the last
showmonitorevent-tracesbchacommand was entered.

parameters

Displays the trace parameters. The parameters displayed are the size (number of trace messages) of the trace file and whether stacktrace is disabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

Cisco IOS XE Release 2.1

This command was introduced.

Cisco IOS XE Release 2.3

The
sbc_hakeyword was changed to two keywords,
sbc and
ha.

Usage Guidelines

Use the
showmonitorevent-tracesbchacommand to display trace message information for SBC HA.

The trace function is not locked while information is displayed to the console, which means that new trace messages can accumulate in memory. If entries accumulate faster than they can be displayed, some messages can be lost. If this happens, the
showmonitorevent-tracesbchacommand generates a message indicating that some messages might be lost; however, messages continue to display on the console. If the number of lost messages is excessive, the
showmonitorevent-tracesbchacommand stops displaying messages.

Examples

The following is sample output from the
showmonitorevent-tracesbchaallcommand. In the following example, all messages from SBC HA events are displayed.

Syntax Description

Displays the LDMs for the routing table you specify. Table 0 is the default or global routing table.

vrf

(Optional) Displays the LDMs for the VPN routing and forwarding (VRF) instance you specify.

vrf-name

(Optional) The name of the VRF instance. You can find VRF names with the show ip vrf command.

ipv4

(Optional) Displays IPv4 LDMs.

ipv6

(Optional) Displays IPv6 LDMs.

Note

Applies to Cisco 7500 series routers only.

Command Default

If you do not specify any keywords or parameters, the command displays the LDMs for the global routing table (the default).

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SSH.

12.4(20)T

This command was integrated into Cisco IOS Release 12.4(20)T.

Usage Guidelines

This command displays the IP LDMs registered with IPRM.

Examples

The command in the following example displays the LDMs for the global routing tables. It shows that two LDMs (lcatm and ldp) are registered for the ipv4 global routing table, and that one LDM (bgp ipv6) is registered for the ipv6 global routing table.

(Optional) Displays redundancy-related states: disabled, initialization, standby, active (various substates for the latter two), client ID and name, length of time since the client was sent the progression, and event history for the progression that was sent to the client.

switchover

(Optional) Displays the switchover counts, the uptime since active, and the total system uptime.

switchoverhistory

(Optional) Displays redundancy switchover history.

Command Modes

User EXEC (>)
Privileged EXEC (#)

Command History

Release

Modification

11.3(6)AA

This command was introduced in privileged EXEC mode.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T. Support for the Cisco AS5800 and Cisco AS5850 is not included in this release.

12.2(8)MC2

This command was modified. This command was made available in user EXEC mode.

12.2(11)T

The privileged EXEC mode form of this command was implemented on the Cisco AS5800 and Cisco AS5850.

12.2(14)SX

The user EXEC mode form of this command was implemented on the Supervisor Engine 720.

Examples

The following is sample output from two Cisco AS5800 router shelves configured as a failover pair. The active router shelf is initially RouterA. The showredundancyhistory and showredundancy commands have been issued. The showredundancy command shows that failover is enabled, shows the configured group number, and shows that this router shelf is the active one of the pair. Compare this output with that from the backup router shelf (RouterB) that follows.

Note

When RouterA is reloaded, thereby forcing a failover, new entries are shown on RouterB when theshowredundancyhistory command is issued after failover has occurred.

Related Commands

call-home(globalconfiguration)

Enters call home configuration mode for configuration of Call Home settings.

showcall-home

Displays Call Home configuration information.

snmp-server enable traps

To enable all Simple Network Management Protocol (SNMP) notification types that are available on your system, use the
snmp-server enable traps command in global configuration mode. To disable all available SNMP notifications, use the
noform of this command.

snmp-serverenabletraps [notification-type] [vrrp]

nosnmp-serverenabletraps [notification-type] [vrrp]

Syntax Description

notification-type

(Optional) Type of notification (trap or inform) to enable or disable. If no type is specified, all notifications available on your device are enabled or disabled (if the
no form is used). The notification type can be one of the following keywords:

alarms--Enables alarm filtering to limit the number of syslog messages generated. Alarms are generated for the severity configured as well as for the higher severity values.

The
severityargument is an integer or string value that identifies the severity of an alarm. Integer values are from 1 to 4. String values are critical, major, minor, and informational. The default is 4 (informational). Severity levels are defined as follows:

ds0-busyout--Sends notification when the busyout of a DS0 interface changes state (Cisco AS5300 platform only). This notification is defined in the CISCO-POP-MGMT-MIB (enterprise 1.3.6.1.4.1.9.10.19.2), and the notification type is (1) cpmDS0BusyoutNotification.

license--Enables licensing notifications as traps or informs. The notifications are grouped into categories that can be individually controlled by combining the keywords with the
license keyword, or as a group by using the
license keyword by itself.

deploy--Controls notifications generated as a result of install, clear, or revoke license events.

error--Controls notifications generated as a result of a problem with the license or with the usage of the license.

imagelevel--Controls notifications related to the image level of the license.

Support for this command was implemented on the Supervisor Engine 720.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(17d)SXB

Support for this command on the Supervisor Engine 2 was integrated into Cisco IOS Release 12.2(17d)SXB.

12.3(11)T

The
vrrpnotification type was added in Cisco IOS Release 12.3(11)T.

12.4(4)T

Support for the
alarmsseverity notification type and argument was added in Cisco IOS Release 12.4(4)T. Support for the
dsp and
dsp oper-state notification types was added in Cisco IOS Release 12.4(4)T.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(11)T

The
dot1x notification type was added in Cisco IOS Release 12.4(11)T.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX

This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

12.4(20)T

The
license notification type keyword was added.

12.2(33)SXH

The
l2tc keyword was added and supported on the Catalyst 6500 series switch.

12.2(33)SXI

The following keywords were added and supported on the Catalyst 6500 series switch:

auth-fail-vlan

entity-diag

guest-vlan

module-auto-shutdown

no-auth-fail-vlan

no-guest-vlan

sys-threshold

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Catalyst 6500 Series Switches

For additional notification types, see the Related Commands table for this command.

SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the
snmp-server host [traps |
informs] command.

To configure the router to send these SNMP notifications, you must enter at least one
snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of notifications, you must issue a separate
snmp-server enable traps command for each notification type and notification option.

Most notification types are disabled by default but some cannot be controlled with the
snmp-server enable traps command.

The
snmp-server enable traps command is used in conjunction with the
snmp-server host command. Use the
snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, you must configure at least one
snmp-server host command.

The following MIBs were enhanced or supported in Cisco IOS Release 12.2(33)SXI and later releases on the Catalyst 6500 series switch:

The following example shows how to send no traps to any host. The Border Gateway Protocol (BGP) traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).

Specifies whether you want the SNMP notifications sent as traps or informs, the version of SNMP to use, the security level of the notifications (for SNMPv3), and the destination host (recipient) for the notifications.

snmp-server informs

Specifies inform request options.

snmp-server trap-source

Specifies the interface (and the corresponding IP address) from which an SNMP trap should originate.

snmp-server trap illegal-address

Issues an SNMP trap when a MAC address violation is detected on an Ethernet hub port of a Cisco 2505, Cisco 2507, or Cisco 2516 router.

vrrp shutdown

Disables a VRRP group.

source-interface

To specify the name of the source interface that the Call-Home service uses to send out e-mail messages, use the source-interface command in call home configuration mode.

source-interfaceinterface-name

nosource-interface

Syntax Description

interface-name

Source-interface name. Maximum length is 64.

Command Default

Call-Home service sends out the e-mail messages using the packet outbound interface as its source interface.

Command Modes

Call home configuration (cfg-call-home)

Command History

Release

Modification

15.2(2)T

This command was introduced.

Usage Guidelines

You can specify either the source-interface name or the source-ip-address when sending Call-Home e-mail messages but not both. The Call-Home service sends out a warning when either the source-interface name or the source-ip-address has already been configured and you attempt to configure one of these options again. If neither of these two are specified, the Call-Home service uses the outbound interface as its source interface and uses that interface's IP address as the source IP address to send out the e-mail messages.

If the specified source interface's status is up and has at least one IP address configured when the Call-Home message is sent out, the e-mail message shows the source interface’s IP address. To verify the IP address, use the debugcall-homemail command or select the e-mail Internet headers option. When the specified source interface is down or has no IP address configured, the Call-Home message is not sent out.

Note

For HTTP messages, use the iphttpclientsource-interfaceinterface-name command in global configuration mode to configure the source interface name. This allows all HTTP clients on the device to use the same source interface.

Examples

The following example specifies loopback1 as the name of the source interface that the Call-Home service uses to send out e-mail messages:

Router(cfg-call-home)# source-interface loopback1

Related Commands

Command

Description

call-home

Enters call home configuration mode.

iphttpclientsource-interface

Specifies the source interface name for HTTP messages.

source-ip-address

Specifies the source IP address with which the Call-Home e-mail messages are sent out.

source-ip-address

To specify the source IP address with which the Call-Home e-mail
messages are sent out, use the
source-ip-address command in call home
configuration mode.

nosource-ip-address { ipv4
address | /ipv6 address }

nosource-ip-address

Syntax Description

ipv4 address |
/ipv6 address

Source IP (ipv4 or ipv6) address. Maximum length is 64.

Command Default

Call-Home service sends out the e-mail messages using the IP address
of the outbound interface as its source IP address.

Command Modes

Call home configuration (cfg-call-home)

Command History

Release

Modification

15.2(2)T

This command was introduced.

Usage Guidelines

You can specify either the source-interface name or the
source-ip-address when sending Call-Home e-mail messages but not both. The
Call-Home service sends out a warning when either the source-interface name or
the source-ip-address has already been configured and you attempt to configure
one of these options again. If neither of these two are specified, the
Call-Home service uses the IP address configured on the message outbound
interface as source IP address to send the e-mail message out.

If the specified source-ip-address is also configured as an IP
address of any workable device interface when the Call-Home message is sent
out, the e-mail message uses it as its source IP address. To verify the IP
address, use the
debugcall-homemailcommand or select the e-mail Internet headers option. When the
specified source-ip-address is not any of the IP addresses configured on
workable interfaces, the Call-Home message is not sent out.

Note

For HTTP messages, use the
iphttpclientsource-interfaceinterface-name command in global
configuration mode to configure the source interface name. This allows all HTTP
clients on the device to use the same source interface.

Examples

The following example specifies 209.165.200.226 as the source IP
address that the Call-Home service uses to send out e-mail messages:

Router(cfg-call-home)# source-ip-address 209.165.200.226

Related Commands

Command

Description

call-home

Enters call home configuration mode.

iphttpclientsource-interface

Specifies the source interface name for HTTP messages.

source-interface

Specifies the name of the source interface that the
Call-Home service uses to send out e-mail messages.

show ip bgp

To display entries in the Border Gateway Protocol (BGP) routing table, use the
showipbgp command in user EXEC or privileged EXEC mode.

(Optional) Displays prefixes that are pending deletion from the BGP routing table.

route-map name

(Optional) Filters the output based on the specified route map.

version version-number

(Optional) Displays all prefixes with network versions greater than or equal to the specified version number. The range is from 1 to 4294967295.

recent offset-value

(Optional) Displays the offset from the current routing table version. The range is from 1 to 4294967295.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release

Modification

10.0

This command was introduced.

12.0

This command was modified. The display of prefix advertisement statistics was added.

12.0(6)T

This command was modified. The display of a message indicating support for route refresh capability was added.

12.0(14)ST

This command was modified. The
prefix-list,
route-map, and
shorter-prefixes keywords were added.

12.2(2)T

This command was modified. The output was modified to display multipaths and the best path to the specified network.

12.0(21)ST

This command was modified. The output was modified to show the number of Multiprotocol Label Switching (MPLS) labels that arrive at and depart from a prefix.

12.0(22)S

This command was modified. A new status code indicating stale routes was added to support BGP graceful restart.

12.2(14)S

This command was modified. A message indicating support for BGP policy accounting was added.

12.2(14)SX

This command was integrated into Cisco IOS Release 12.2(14)SX.

12.2(15)T

This command was modified. A new status code indicating stale routes was added to support BGP graceful restart.

12.3(2)T

This command was modified. The
all keyword was added.

12.2(17b)SXA

This command was integrated into Cisco IOS Release 12.2(17b)SXA.

12.3(8)T

This command was modified. The
oer-paths keyword was added.

12.4(15)T

This command was modified. The
pending-prefixes,bestpath,
multipaths, and
subnets keywords were added.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2.

12.0(32)S12

This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation was added.

12.0(32)SY8

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

12.4(22)T

This command was modified. The version version-number and the recent offset-value keyword and argument pairs were added.

12.4(24)T

This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation was added.

Cisco IOS XE Release 2.3

This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation was added.

12.2(33)SXI1

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

12.0(33)S3

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format was changed to asplain.

Cisco IOS XE Release 2.4

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format was changed to asplain.

12.2(33)SRE

This command was modified. The command output was modified to show the backup path and the best external path information. Support for the best external route and backup path was added. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

12.2(33)XNE

This command was integrated into Cisco IOS Release 12.2(33)XNE.

15.0(1)S

This command was integrated into Cisco IOS Release 15.0(1)S.

15.2(1)S

This command was modified to display an Resource Public Key Infrastructure (RPKI) validation code per network, if one applies.

Cisco IOS XE Release 3.5S

This command was modified to display an RPKI validation code per network, if one applies.

15.1(1)SG

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

Cisco IOS XE Release 3.3SG

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

15.2(4)S

This command was modified. Output about discarded or unknown path attributes was added for the BGP Attribute Filter feature. Output about additional path selection was added for the BGP Additional Paths feature. Output about paths imported from a virtual routing and forwarding (VRF) table to the global table was added for the BGP Support for IP Prefix Export from a VRF table into the global table.

Cisco IOS XE Release 3.7S

This command was modified. Output about discarded or unknown path attributes was added for the BGP Attribute Filter feature. Output about additional path selection was added for the BGP Additional Paths feature. Output about paths imported from a VRF table to the global table was added for the BGP Support for IP Prefix Export from a VRF table into the global table.

15.1(1)SY

This command was integrated into Cisco IOS Release 15.1(1)SY.

15.2(1)E

This command was integrated into Cisco IOS Release 15.2(1)E.

Usage Guidelines

The
showipbgp command is used to display the contents of the BGP routing table. The output can be filtered to display entries for a specific prefix, prefix length, and prefixes injected through a prefix list, route map, or conditional advertisement.

When changes are made to the network address, the network version number is incremented. Use the version keyword to view a specific network version.

In Cisco IOS Release 12.0(32)SY8, 12.0(33)S3, 12.2(33)SRE, 12.2(33)XNE, 12.2(33)SXI1, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538, for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the
bgpasnotationdot command followed by the
clearipbgp* command to perform a hard reset of all current BGP sessions.

The table below describes the significant fields shown in the display.

Table 27 show ip bgp Field Descriptions

Field

Description

BGP table version

Internal version number of the table. This number is incremented whenever the table changes.

local router ID

IP address of the router.

Status codes

Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following values:

s—The table entry is suppressed.

d—The table entry is dampened.

h—The table entry history.

*—The table entry is valid.

>—The table entry is the best entry to use for that network.

i—The table entry was learned via an internal BGP (iBGP) session.

r—The table entry is a RIB-failure.

S—The table entry is stale.

m—The table entry has multipath to use for that network.

b—The table entry has a backup path to use for that network.

x—The table entry has a best external route to use for the network.

Origin codes

Origin of the entry. The origin code is placed at the end of each line in the table. It can be one of the following values:

a—Path is selected as an additional path.

i—Entry originated from an Interior Gateway Protocol (IGP) and was advertised with a
network router configuration command.

e—Entry originated from an Exterior Gateway Protocol (EGP).

?—Origin of the path is not clear. Usually, this is a router that is redistributed into BGP from an IGP.

RPKI validation codes

If shown, the RPKI validation state for the network prefix, which is downloaded from the RPKI server. The codes are shown only if the
bgp rpki server or
neighbor announce rpki state command is configured.

Network

IP address of a network entity.

Next Hop

IP address of the next system that is used when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the router has some non-BGP routes to this network.

Metric

If shown, the value of the interautonomous system metric.

LocPrf

Local preference value as set with the
setlocal-preference route-map configuration command. The default value is 100.

Weight

Weight of the route as set via autonomous system filters.

Path

Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path.

(stale)

Indicates that the following path for the specified autonomous system is marked as “stale” during a graceful restart process.

The table below describes the significant fields shown in the display.

Table 28 show ip bgp ip-address Field Descriptions

Field

Description

BGP routing table entry for

IP address or network number of the routing table entry.

version

Internal version number of the table. This number is incremented whenever the table changes.

Paths

The number of available paths, and the number of installed best paths. This line displays “Default-IP-Routing-Table” when the best path is installed in the IP routing table.

Multipath

This field is displayed when multipath load sharing is enabled. This field will indicate if the multipaths are iBGP or eBGP.

Advertised to update-groups

The number of each update group for which advertisements are processed.

Origin

Origin of the entry. The origin can be IGP, EGP, or incomplete. This line displays the configured metric (0 if no metric is configured), the local preference value (100 is default), and the status and type of route (internal, external, multipath, best).

Extended Community

This field is displayed if the route carries an extended community attribute. The attribute code is displayed on this line. Information about the extended community is displayed on a subsequent line.

The following is sample output from the
showipbgp command entered with the
all keyword. Information about all configured address families is displayed.

The following output indicates (for each neighbor) whether any of the additional path tags (group-best, all, best 2 or best 3) are applied to the path. A line of output indicates rx pathid (received from neighbor) and tx pathid (announcing to neighbors). Note that the “Path advertised to update-groups:” is now per-path when the BGP Additional Paths feature is enabled.

(Optional) Displays all received routes (both accepted and rejected) from the specified neighbor.

routes

(Optional) Displays all routes that are received and accepted. The output displayed when this keyword is entered is a subset of the output displayed by the
received-routes keyword.

Command Default

The output of this command displays information for all neighbors.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Mainline and T Release

Modification

10.0

This command was introduced.

11.2

This command was modified. Thereceived-routes keyword was added.

12.2(4)T

This command was modified. The
received and
prefix-filter keywords were added.

12.2(15)T

This command was modified. Support for the display of BGP graceful restart capability information was added.

12.3(7)T

This command was modified. The command output was modified to support the BGP TTL Security Check feature and to display explicit-null label information.

12.4(4)T

This command was modified. Support for the display of Bidirectional Forwarding Detection (BFD) information was added.

12.4(11)T

This command was modified. Support for the
policy and
detail keywords was added.

12.4(20)T

This command was modified. The output was modified to support BGP TCP path MTU discovery.

12.4(24)T

This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation was added.

Command History

S Release

Modification

12.0(18)S

This command was modifed. The output was modified to display the no-prepend configuration option.

12.0(21)ST

This command was modifed. The output was modified to display Multiprotocol Label Switching (MPLS) label information.

12.0(22)S

This command was modified. Support for the display of BGP graceful restart capability information was added. Support for the Cisco 12000 series routers (Engine 0 and Engine 2) was also added.

12.0(25)S

This command was modified. The
policy and
detail keywords were added.

12.0(27)S

This command was modified. The command output was modified to support the BGP TTL Security Check feature and to display explicit-null label information.

12.0(31)S

This command was modified. Support for the display of BFD information was added.

12.0(32)S12

This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation was added.

12.0(32)SY8

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

12.0(33)S3

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format became asplain.

12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.2(17b)SXA

This command was integrated into Cisco IOS Release 12.2(17b)SXA.

12.2(18)SXE

This command was modified. Support for the display of BFD information was added.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was modified. The output was modified to support BGP TCP path Maximum Transmission Unit (MTU) discovery.

12.2(33)SRB

This command was modified. Support for the
policy and
detail keywords was added.

12.2(33)SXH

This command was modified. Support for displaying BGP dynamic neighbor information was added.

12.2(33)SRC

This command was modified. Support for displaying BGP graceful restart information was added.

12.2(33)SB

This command was modified. Support for displaying BFD and the BGP graceful restart per peer information was added, and support for the
policy and
detail keywords was integrated into Cisco IOS Release 12.2(33)SB.

12.2(33)SXI1

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

12.2(33)SRE

This command was modified. Support for displaying BGP best external and BGP additional path features information was added. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.

12.2(33)XNE

This command was modified. Support for 4-byte autonomous system numbers in asplain and asdot notation was added.

15.0(1)S

This command was modified. The
slow keyword was added.

15.0(1)SY

This command was integrated into Cisco IOS Release 15.0(1)SY.

15.1(1)S

This command was modified. The Layer 2 VPN address family is displayed if graceful restart or nonstop forwarding (NSF) is enabled.

15.1(1)SG

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format became asplain.

15.2(4)S

This command was modified and implemented on the Cisco 7200 series router. The configured discard and treat-as-withdraw attributes are displayed, along with counts of incoming Updates with a matching discard attribute or treat-as-withdraw attribute, and number of times a malformed Update is treat-as-withdraw. The capabilities of the neighbor to send and receive additional paths that are advertised or received are added.

15.1(2)SNG

This command was implemented on the Cisco ASR 901 Series Aggregation Services Routers.

15.2(1)E

This command was integrated into Cisco IOS Release 15.2(1)E.

Command History

Cisco IOS XE

Modification

Cisco IOS XE Release 2.1

This command was integrated into Cisco IOS XE Release 2.1.

Cisco IOS XE Release 2.4

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format became asplain.

Cisco IOS XE Release 3.1S

This command was modified. The
slow keyword was added.

Cisco IOS XE Release 3.6S

This command was modified. Support for displaying BGP BFD multihop and C-bit information was added.

Cisco IOS XE Release 3.3SG

This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format became asplain.

Cisco IOS XE Release 3.7S

This command was implemented on the Cisco ASR 903 router and the output modified. The configured discard and treat-as-withdraw attributes are displayed, along with counts of incoming Updates with a matching discard attribute or treat-as-withdraw attribute, and number of times a malformed Update is treat-as-withdraw. The capabilities of the neighbor to send and receive additional paths that are advertised or received are added.

Cisco IOS XE Release 3.8S

This command was modified. In support of the BGP Multi-Cluster ID feature, the cluster ID of a neighbor is displayed if the neighbor is assigned a cluster.

Usage Guidelines

Use the
showipbgpneighbors command to display BGP and TCP connection information for neighbor sessions. For BGP, this includes detailed neighbor attribute, capability, path, and prefix information. For TCP, this includes statistics related to BGP neighbor session establishment and maintenance.

Prefix activity is displayed based on the number of prefixes that are advertised and withdrawn. Policy denials display the number of routes that were advertised but then ignored based on the function or attribute that is displayed in the output.

In Cisco IOS Release 12.0(32)SY8, 12.0(33)S3, 12.2(33)SRE, 12.2(33)XNE, 12.2(33)SXI1, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538, for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the
bgpasnotationdot command followed by the
clearipbgp* command to perform a hard reset of all current BGP sessions.

When BGP neighbors use multiple levels of peer templates, determining which policies are applied to the neighbor can be difficult.

In Cisco IOS Release 12.0(25)S, 12.4(11)T, 12.2(33)SRB, 12.2(33)SB, and later releases, the
policy and
detail keywords were added to display the inherited policies and the policies configured directly on the specified neighbor. Inherited policies are policies that the neighbor inherits from a peer group or a peer policy template.

Examples

Example output is different for the various keywords available for the
showipbgpneighbors command. Examples using the various keywords appear in the following sections.

Examples

The following example shows output for the BGP neighbor at 10.108.50.2. This neighbor is an internal BGP (iBGP) peer. This neighbor supports the route refresh and graceful restart capabilities.

The table below describes the significant fields shown in the display. Fields that are preceded by the asterisk character (*) are displayed only when the counter has a nonzero value.

Table 29 show ip bgp neighbors Field Descriptions

Field

Description

BGP neighbor

IP address of the BGP neighbor and its autonomous system number.

remote AS

Autonomous system number of the neighbor.

local AS 300 no-prepend (not shown in display)

Verifies that the local autonomous system number is not prepended to received external routes. This output supports the hiding of the local autonomous systems when a network administrator is migrating autonomous systems.

Delayed receive window—data the local host has read from the connection, but has not yet subtracted from the receive window the host has advertised to the remote host. The value in this field gradually increases until it is higher than a full-sized packet, at which point it is applied to the rcvwnd field.

SRTT:

A calculated smoothed round-trip timeout.

RTTO:

Round-trip timeout.

RTV:

Variance of the round-trip time.

KRTT:

New round-trip timeout (using the Karn algorithm). This field separately tracks the round-trip time of packets that have been re-sent.

minRTT:

Shortest recorded round-trip timeout (hard-wire value used for calculation).

maxRTT:

Longest recorded round-trip timeout.

ACK hold:

Length of time the local host will delay an acknowledgment to carry (piggyback) additional data.

IP Precedence value:

IP precedence of the BGP packets.

Datagrams

Number of update packets received from a neighbor.

Rcvd:

Number of received packets.

out of order:

Number of packets received out of sequence.

with data

Number of update packets sent with data.

total data bytes

Total amount of data received, in bytes.

Sent

Number of update packets sent.

Second Congestion

Number of update packets with data sent.

Datagrams: Rcvd

Number of update packets received from a neighbor.

retransmit

Number of packets retransmitted.

fastretransmit

Number of duplicate acknowledgments retransmitted for an out of order segment before the retransmission timer expires.

partialack

Number of retransmissions for partial acknowledgments (transmissions before or without subsequent acknowledgments).

The table below describes the significant fields shown in the display.

Table 32 show ip bgp neighbors received prefix-filter Field Descriptions

Field

Description

Address family

Address family mode in which the prefix filter is received.

ip prefix-list

Prefix list sent from the specified neighbor.

Examples

The following sample output shows the policies applied to the neighbor at 192.168.1.2. The output displays both inherited policies and policies configured on the neighbor device. Inherited polices are policies that the neighbor inherits from a peer group or a peer-policy template.

Examples

The following is sample output from the
showipbgpneighbors command that verifies that Bidirectional Forwarding Detection (BFD) is being used to detect fast fallover for the BGP neighbor that is a BFD peer:

Examples

The following is sample output from the
showipbgpneighbors command that verifies that the neighbor 192.168.3.2 is a member of the peer group group192 and belongs to the subnet range group 192.168.0.0/16, which shows that this BGP neighbor was dynamically created:

Examples

The following is partial output from the
showipbgpneighbors command that verifies the status of the BGP graceful restart capability for the external BGP peer at 192.168.3.2. Graceful restart is shown as disabled for this BGP peer.

Examples

The following is sample output from the
showipbgpneighbors command that indicates the discard attribute values and treat-as-withdraw attribute values configured. It also provides a count of received Updates matching a treat-as-withdraw attribute, a count of received Updates matching a discard attribute, and a count of received malformed Updates that are treat-as-withdraw.

Examples

The following output indicates that the neighbor is capable of advertising additional paths and sending additional paths it receives. It is also capable of receiving additional paths and advertised paths.

Examples

In the following output, the cluster ID of the neighbor is displayed. (The vertical bar and letter “i” for “include” cause the device to display only lines that include the user's input after the “i”, in this case, “cluster-id.”) The cluster ID displayed is the one directly configured through a neighbor or a template.

Syntax Description

Displays NLRI prefixes associated with the named VPN routing and forwarding (VRF) instance.

ip-prefix/length

(Optional) IP prefix address (in dotted decimal format) and the length of the mask (0 to 32). The slash mark must be included.

longer-prefixes

(Optional) Displays the entry, if any, that exactly matches the specified prefix parameter and all entries that match the prefix in a “longest-match” sense. That is, prefixes for which the specified prefix is an initial substring.

network-address

(Optional) IP address of a network in the BGP routing table.

mask

(Optional) Mask of the network address, in dotted decimal format.

cidr-only

(Optional) Displays only routes that have nonclassful netmasks.

cluster-ids

(Optional) Displays configured cluster IDs.

community

(Optional) Displays routes that match this community.

community-list

(Optional) Displays routes that match this community list.

dampening

(Optional) Displays paths suppressed because of dampening (BGP route from peer is up and down).

extcommunity-listextended-community-list-name

(Optional) Displays routes that match the extended community list.

filter-list

(Optional) Displays routes that conform to the filter list.

inconsistency nexthop-label

(Optional) Displays all inconsistent paths.

inconsistent-as

(Optional) Displays only routes that have inconsistent autonomous systems of origin.

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series router. The display output was modified to indicate whether BGP nonstop routing (NSR) with stateful switchover (SSO) is enabled and the reason the last BGP lost SSO capability.

12.2(33)SRA

This command was modified. The output was modified to support per-VRF assignment of the BGP router ID.

12.2(31)SB2

This command was modified. The output was modified to support per-VRF assignment of the BGP router ID.

12.2(33)SXH

This command was modified. The output was modified to support per-VRF assignment of the BGP router ID.

Note

In Cisco IOS Release 12.2(33)SXH, the command output does not display on the standby Route Processor in NSF/SSO mode.

12.4(20)T

This command was modified. The output was modified to support per-VRF assignment of the BGP router ID.

15.0(1)M

This command was modified. The output was modified to support the BGP Event-Based VPN Import feature.

12.2(33)SRE

This command was modified. The command output was modified to support the BGP Event-Based VPN Import, BGP best external, and BGP additional path features.

12.2(33)XNE

This command was integrated into Cisco IOS Release 12.2(33)XNE.

Cisco IOS XE Release 2.5

This command was integrated into Cisco IOS XE Release 2.5.

15.0(1)S

This command was integrated into Cisco IOS Release 15.0(1)S.

15.0(1)SY

This command was integrated into Cisco IOS Release 15.0(1)SY.

15.2(3)T

This command was integrated into Cisco IOS Release 15.2(3)T.

15.2(4)S

This command was implemented on the Cisco 7200 series router and the output was modified to display unknown attributes and discarded attributes associated with a prefix.

Cisco IOS XE Release 3.7S

This command was implemented on the Cisco ASR 903 router and the output modified to display unknown attributes and discarded attributes associated with a prefix.

15.2(2)SNG

This command was implemented on the Cisco ASR 901 Series Aggregation Services Routers.

Usage Guidelines

Use this command to display VPNv4 information from the BGP database. The
showipbgpvpnv4all command displays all available VPNv4 information. The
showipbgpvpnv4allsummary command displays BGP neighbor status. The
showipbgpvpnv4alllabels command displays explicit-null label information.

Examples

The following example shows all available VPNv4 information in a BGP routing table:

The table below describes the significant fields shown in the display.

Table 37 show ip bgp vpnv4 vrf rib-failure Field Descriptions

Field

Description

Network

IP address of a network entity.

Next Hop

IP address of the next system that is used when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the router has some non-BGP routes to this network.

RIB-failure

Cause of the Routing Information Base (RIB) failure. Higher admin distance means that a route with a better (lower) administrative distance, such as a static route, already exists in the IP routing table.

RIB-NH Matches

Route status that applies only when Higher admin distance appears in the RIB-failure column and the
bgpsuppress-inactive command is configured for the address family being used. There are three choices:

Yes—Means that the route in the RIB has the same next hop as the BGP route or that the next hop recurses down to the same adjacency as the BGP next hop.

No—Means that the next hop in the RIB recurses down differently from the next hop of the BGP route.

n/a—Means that the
bgpsuppress-inactive command is not configured for the address family being used.

The following example shows the information displayed on the active and standby Route Processors when they are configured for NSF/SSO: MPLS VPN.

Note

In Cisco IOS Release 12.2(33)SXH, the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature incurred various infrastructure changes. The result of those changes affects the output of this command on the standby Route Processor (RP). In Cisco IOS Release 12.2(33)SXH, the standby RP does not display any output from the
showipbgpvpnv4 command.

The table below describes the significant fields shown in the display.

Table 39 show ip bgp vpnv4 all labels Field Descriptions

Field

Description

Network

Displays the network address from the BGP table.

Next Hop

Displays the address of the BGP next hop.

In label

Displays the label (if any) assigned by this router.

Out label

Displays the label assigned by the BGP next-hop router.

Route Distinguisher

Displays an 8-byte value added to an IPv4 prefix to create a VPN IPv4 prefix.

The following example displays separate router IDs for each VRF in the output from an image in Cisco IOS Release 12.2(31)SB2, 12.2(33)SRA, 12.2(33)SXH, 12.4(20)T, Cisco IOS XE Release 2.1, and later releases with the Per-VRF Assignment of BGP Router ID feature configured. The router ID is shown next to the VRF name.

The table below describes the significant fields shown in the display.

Table 40 show ip bgp vpnv4 all (VRF Router ID) Field Descriptions

Field

Description

Route Distinguisher

Displays an 8-byte value added to an IPv4 prefix to create a VPN IPv4 prefix.

vrf

Name of the VRF.

VRF Router ID

Router ID for the VRF.

In the following example, the BGP Event-Based VPN Import feature is configured in Cisco IOS Release 15.0(1)M, 12.2(33)SRE, and later releases. When the
importpathselection command is configured, but the
strict keyword is not included, then a safe import path selection policy is in effect. When a path is imported as the best available path (when the best path or multipaths are not eligible for import), the imported path includes the wording “imported safety path,” as shown in the output.

In the following example, BGP Event-Based VPN Import feature configuration information is shown for Cisco IOS Release 15.0(1)M, 12.2(33)SRE, and later releases. When the
importpathselection command is configured with the
all keyword, any path that matches an RD of the specified VRF will be imported, even though the path does not match the Route Targets (RT) imported by the specified VRF. In this situation, the imported path is marked as “not-in-vrf” as shown in the output. Note that on the net for vrf-A, this path is not the best path because any paths that are not in the VRFs appear less attractive than paths in the VRF.

The following example includes “allow-policy” in the output, indicating that the BGP—Support for iBGP Local-AS feature was configured for the specified neighbor by configuring the neighbor allow-policy command.

show redundancy config-sync

To display failure information generated during a bulk synchronization from the active Performance Routing Engine (PRE) to the standby PRE, use the
show redundancy config-sync command in user EXEC or privileged EXEC modes.

show redundancy config-sync

Syntax Description

failures

Displays failures related to bulk synchronisation of the standby PRE.

bem

Displays Best Effort Method (BEM) failure list.

mcl

Displays Mismatched Command List (MCL) failure list.

prc

Displays Parser Return Code (PRC) failure list.

ignored failures mcl

Displays mismatched commands in the MCL that are ignored.

Command Default

No default behavior or values.

Command Modes

User EXEC (>)
Privileged EXEC (#)

Command History

Release

Modification

This command was introduced.

Usage Guidelines

This command is used on the active PRE only.

If there are mismatched commands between the active and standby PRE, remove the configuration lines that are not supported on the standby image. If it is not possible to remove the mismatched lines, or it has been determined that the mismatched lines are not critical to the operation of the system, use the command
redundancy config-sync ignore mismatched-commands to temporarily ignore them.

show redundancy config-sync ignored failures mcl

To display failure information generated during a bulk synchronization of commands from an active Route Processor (RP) module to a standby RP module, use the
show redundancy config-sync ignored failures mcl command in user EXEC or privileged EXEC modes.

show redundancy config-sync ignoredfailuresmcl

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values.

Command Modes

User EXEC (>)

Privileged EXEC (#)

Command History

Release

Modification

15.2(4)M

This command was introduced.

Usage Guidelines

This command is used on the active RP module only.

If there are mismatched commands between active and standby RP modules, remove configuration lines that are not supported on the standby RP module. If it is not possible to remove mismatched lines, or if mismatched lines are not critical to the operation of the system, use the
redundancy config-sync ignore mismatched-commands command to temporarily ignore them.

Examples

The following is sample output from the
show redundancy config-sync ignored failures mcl command when there are no mismatched commands:

Related Commands

Forces the standby RP module to assume the role of the active RP module.

show redundancy

Displays the redundancy status of the current active and standby RP modules.

show redundancy platform

Displays active and standby RP modules and software information.

standby initialization delay

To configure the standby Route Processor (RP) initialization delay, use the
standby initialization delay command in main-CPU redundancy configuration mode. To disable the standby RP initialization delay configuration, use the
no form of this command.

standby initialization delayseconds
[ boot-only ]

no standby initialization delayseconds
[ boot-only ]

Syntax Description

seconds

Duration of the standby RP initialization delay. The range is from 30 to 1800.

boot-only

(Optional) Specifies that the standby RP initialization is delayed only when the system boots up.

Command Default

The standby RP initialization delay is not configured.

Command Modes

Main-CPU redundancy configuration (config-r-mc)

Command History

Release

Modification

12.2(33)XNE

This command was introduced.

Usage Guidelines

If the
boot-only is used, standby RP initialization is delayed only when the system boots up. If
boot-only is not used, standby RP initialization will be delayed when the system boots up and also after an RP switchover.

Examples

The following example shows how to configure a standby RP initialization delay of 60 seconds:

Related Commands

Command

Description

redundancy

Enters redundancy configuration mode.

redundancy force-switchover

Forces the standby RP to assume the role of the active RP.

street-address

To specify a street address where RMA equipment for Call Home can be sent, use the street-address command in call home configuration mode. To remove the street address, use the no form of this command.

street-addressalphanumeric

nostreet-addressalphanumeric

Syntax Description

alphanumeric

Street address, using up to 200 alphanumeric characters, including commas and spaces. If you include spaces, you must enclose your entry in quotes (“ ”).

Command Default

No street address is specified.

Command Modes

Call home configuration (cfg-call-home)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

The street-address command is optional to specify where return materials authorization (RMA) equipment for Call Home should be sent.

Examples

The following example configures “1234AnyStreet,AnyCity,AnyState,12345” as the street address without spaces:

Related Commands

call-home(globalconfiguration)

Enters call home configuration mode for configuration of Call Home settings.

showcall-home

Displays Call Home configuration information.

subscriber redundancy

To configure the broadband subscriber session redundancy policy for synchronization between High Availability (HA) active and standby processors, use the
subscriber redundancy command in global configuration mode. To delete the policy, use the
no form of this command.

Specifies the number of sessions per time period for bulk and dynamic synchronization.

sessions—Range: 1 to 32000. Default: 250.

seconds—Range: 1 to 33550. Default: 1.

disable

Disables stateful switchover (SSO) for all subscriber sessions.

Command Default

The default subscriber redundancy policy is applied.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.2(31)SB2

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

Cisco IOS XE Release 3.3S

This command was integrated into Cisco IOS XE Release 3.3S.

Cisco IOS XE Release 3.5S

This command was modified. The
periodic-update interval keyword and
minutes argument were added.

15.2(1)S

This command was modified. The
disable keyword was added.

Usage Guidelines

Cisco IOS HA functionality for broadband protocols and applications allows for SSO and In-Service Software Upgrade (ISSU) features that minimize planned and unplanned downtime and failures. HA uses the cluster control manager (CCM) to manage the capability to synchronize subscriber session initiation on the standby processor of a redundant processor system.

Use the
bulk keyword to create and modify the redundancy policy used during bulk (startup) synchronization.

Use the
dynamic
keyword with the
limit
keyword to tune subscriber redundancy policies that throttle dynamic synchronization by monitoring CPU usage and synchronization rates.

Use the delay keyword to establish the minimum session duration for synchronization and to manage dynamic synchronization of short-duration calls.

Use the
rate keyword to throttle the number of sessions to be synchronized per period.

Use the
dynamic
keyword with the
periodic-update interval keyword to enable subscriber sessions to periodically synchronize their dynamic accounting statistics (counters) on the standby processor. The periodic update applies to new and existing subscriber sessions. All subscriber sessions do not synchronize their data at exactly the same time. Session synchronization is spread out based on the session creation time and other factors. This command is rejected if a previous instance of the command has not finished processing.

Use the
disable keyword to disable SSO for all subscriber sessions.

Examples

The following example shows how to configure a 10-second delay when CPU usage exceeds 90 percent during bulk synchronization, after which 25 sessions will be synchronized before the CCM again checks the CPU usage:

The following example shows how to configure a maximum time of 90 seconds for bulk synchronization to be completed:

Router(config)# subscriber redundancy bulk limit time 90

The following example shows how to configure a 15-second delay when CPU usage exceeds 90 percent during dynamic synchronization, after which 25 sessions will be synchronized before the CCM again checks the CPU usage:

The following example shows how to disable SSO for all subscriber sessions:

Router(config)# subscriber redundancy disable

Related Commands

Command

Description

show ccm sessions

Displays CCM session information.

show pppatm statistics

Displays PPPoA statistics.

show pppoe statistics

Displays PPPoE statistics.

show ppp subscriber statistics

Displays PPP subscriber statistics.

subscribe-to-alert-group

To subscribe a destination profile to an alert group, use the subscribe-to-alert-group command in destination profile configuration mode. To unsubscribe from an alert group or all alert groups, use the no form of this command.

Syntax Description

(Optional) Specifies the time to begin daily Call Home messages. The valid values for the time are based on a 24-hour clock.

periodic
monthlydayhh:mm

(Optional) Specifies the time to begin monthly Call Home messages; the valid values are as follows:

day is 1 to 31.

hh:mm is based on a 24-hour clock.

periodic weeklydayhh:mm

(Optional) Specifies the time to begin weekly Call Home messages; the valid values are as follows:

day is 1 to 31.

hh:mm is based on a 24-hour clock.

diagnostic

Subscribes to diagnostic information groups.

severitylevel

Specifies the severity level of the diagnostic.

environment

Subscribes to environmental information groups.

inventory

Subscribes to inventory information groups.

syslog

Subscribes to system logging (syslog) information groups.

Command Default

Destination profiles are not subscribed to alert groups by default.

Command Modes

Destination profile configuration

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

Usage Guidelines

The valid values for the level argument are as follows:

catastrophic--Catastrophic event

critical--Critical event

debugging--Debugging event

disaster--Disaster event

fatal--Fatal event

major--Major event

minor--Minor event

normal--Normal event

notification--Notification event

warning--Warning event

Selecting the lowest severity level includes all higher severity events. The types of severity levels are as follows:

Catastrophic--Anetwork-wide catastrophic failure (Highest severity)

Disaster--A significant network impact

Fatal--System is unusable (System log level 0)

Critical--Immediate attention needed (System log level 1)

Major--Major condition (System log level 2)

Minor--Minor condition (System log level 3)

Warning--Warning condition (System log level 4)

Notification--Informational message (System log level 5)

Normal--Signifying returning to normal state (System log level 6)

Debug--Debugging message (Lowest severity)

Examples

The following examples shows how to subscribe to all alert groups:

subscribe-to-alert-group all

subscribe-to-alert-group all

To configure a destination profile to receive messages for all available alert groups for Call Home, use the subscribe-to-alert-group all command in call home profile configuration mode. To remove the subscription, use the
no form of this command.

subscribe-to-alert-groupall

nosubscribe-to-alert-groupall

Syntax Description

This command has no arguments or keywords.

Command Default

This command has no default behavior or values.

Command Modes

Call home profile configuration (cfg-call-home-profile)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

To enter call home profile configuration mode, use the
profile(callhome) command in call home configuration mode.

Note

Alert group trigger events and the commands that are executed because of a trigger are platform-dependent. For more information, see the corresponding Call Home configuration documentation for your platform.

Caution

The
subscribe-to-alert-groupall command subscribes you to all debug-level syslog messages. The number of messages produced can overload the system.

Examples

The following example shows how to configure a profile to receive messages for all available alert groups:

Related Commands

Enters call home configuration mode for configuration of Call Home settings.

profile(callhome)

Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.

subscribe-to-alert-groupconfiguration

Configures a destination profile to receive messages for the Configuration alert group for Call Home.

subscribe-to-alert-groupdiagnostic

Configures a destination profile to receive messages for the Diagnostic alert group for Call Home.

subscribe-to-alert-groupenvironment

Configures a destination profile to receive messages for the Environment alert group for Call Home.

subscribe-to-alert-groupinventory

Configures a destination profile to receive messages for the Inventory alert group for Call Home.

subscribe-to-alert-groupsyslog

Configures a destination profile to receive messages for the Syslog alert group for Call Home.

subscribe-to-alert-group configuration

To configure a destination profile to receive messages for the Configuration alert group for Call Home, use the
subscribe-to-alert-group configuration command in call home profile configuration mode. To remove the subscription, use the no form of this command.

Syntax Description

monthlydayhh:mm
--Numeric day of the month (from 1 to 31) and time [in 24-hour format (hh:mm
)] for a monthly Call Home alert notification to be sent.

weeklydayhh:mm
--Day of the week (Monday through Saturday) and time [in 24-hour format (hh:mm
)] for a weekly Call Home alert notification to be sent.

Command Default

This command has no default behavior or values.

Command Modes

Call home profile configuration (cfg-call-home-profile)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

To enter call home profile configuration mode, use the profile(callhome) command in call home configuration mode.

When you subscribe to the Configuration alert group without the periodic option, a notification occurs whenever a configuration change occurs. Otherwise, the notification occurs at the date and time specified.

Note

Alert group trigger events and the commands that are executed because of a trigger are platform-dependent. For more information, see the corresponding Call Home configuration documentation for your platform.

Examples

The following example shows how to configure a profile to receive a weekly periodic configuration alert notification every Tuesday at 9:16 PM (21:16):

Related Commands

Enters call home configuration mode for configuration of Call Home settings.

profile(callhome)

Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.

subscribe-to-alert-groupall

Configures a destination profile to receive messages for all available alert groups for Call Home.

subscribe-to-alert-groupdiagnostic

Configures a destination profile to receive messages for the Diagnostic alert group for Call Home.

subscribe-to-alert-groupenvironment

Configures a destination profile to receive messages for the Environment alert group for Call Home.

subscribe-to-alert-groupinventory

Configures a destination profile to receive messages for the Inventory alert group for Call Home.

subscribe-to-alert-groupsyslog

Configures a destination profile to receive messages the Syslog alert group for Call Home.

subscribe-to-alert-group diagnostic

To configure a destination profile to receive messages for the Diagnostic alert group for Call Home, use the
subscribe-to-alert-group diagnostic command in call home profile configuration mode. To remove the subscription, use the no form of this command.

Command Default

When you configure the subscribe-to-alert-groupdiagnostic command without specifying any severity, the default is normal severity.

Command Modes

Call home profile configuration (cfg-call-home-profile)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

To enter call home profile configuration mode, use the profile(callhome) command in call home configuration mode.

When specifying severity, selecting a lower level severity includes notification of events with any higher severity.

Note

Alert group trigger events and the commands that are executed because of a trigger are platform-dependent. For more information, see the corresponding Call Home configuration documentation for your platform.

Examples

The following example shows how to configure a profile to receive diagnostic alerts for events with severity level 2 or higher:

Related Commands

Enters call home configuration mode for configuration of Call Home settings.

profile(callhome)

Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.

subscribe-to-alert-groupall

Configures a destination profile to receive messages for all available alert groups for Call Home.

subscribe-to-alert-groupconfiguration

Configures a destination profile to receive messages for the Configuration alert group for Call Home.

subscribe-to-alert-groupenvironment

Configures a destination profile to receive messages for the Environment alert group for Call Home.

subscribe-to-alert-groupinventory

Configures a destination profile to receive messages for the Inventory alert group for Call Home.

subscribe-to-alert-groupsyslog

Configures a destination profile to receive messages for the Syslog alert group for Call Home.

subscribe-to-alert-group environment

To configure a destination profile to receive messages for the Environment alert group for Call Home, use the
subscribe-to-alert-group environment command in call home profile configuration mode. To remove the subscription, use the no form of this command.

Command Default

When you configure the subscribe-to-alert-groupenvironment command without specifying any severity, the default is normal severity.

Command Modes

Call home profile configuration (cfg-call-home-profile)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

To enter call home profile configuration mode, use the profile(callhome) command in call home configuration mode.

When specifying severity, selecting a lower level severity includes notification of events with any higher severity.

Note

Alert group trigger events and the commands that are executed because of a trigger are platform-dependent. For more information, see the corresponding Call Home configuration documentation for your platform.

Examples

The following example shows how to configure a profile to receive environment alerts for events with severity level 2 or higher:

Related Commands

Enters call home configuration mode for configuration of Call Home settings.

profile(callhome)

Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.

subscribe-to-alert-groupall

Configures a destination profile to receive messages for all available alert groups for Call Home.

subscribe-to-alert-groupconfiguration

Configures a destination profile to receive messages for the Configuration alert group for Call Home.

subscribe-to-alert-groupdiagnostic

Configures a destination profile to receive messages for the Diagnostic alert group for Call Home.

subscribe-to-alert-groupinventory

Configures a destination profile to receive messages for the Inventory alert group for Call Home.

subscribe-to-alert-groupsyslog

Configures a destination profile to receive messages for the Syslog alert group for Call Home.

subscribe-to-alert-group inventory

To configure a destination profile to receive messages for the Inventory alert group for Call Home, use the
subscribe-to-alert-group inventory command in call home profile configuration mode. To remove the subscription, use the no form of this command.

Syntax Description

monthlydayhh:mm
--Numeric day of the month (from 1 to 31) and time [in 24-hour format (hh:mm
)] for a monthly Call Home alert notification to be sent.

weeklydayhh:mm
--Day of the week (Monday through Saturday) and time [in 24-hour format (hh:mm
)] for a weekly Call Home alert notification to be sent.

Command Default

This command has no default behavior or values.

Command Modes

Call home profile configuration (cfg-call-home-profile)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

To enter call home profile configuration mode, use the profile(callhome) command in call home configuration mode.

When you subscribe to the Inventory alert group without the periodic option, a notification occurs whenever a device is cold-booted, or when field-replaceable units (FRUs) are inserted or removed. Otherwise, the notification occurs at the date and time specified.

Note

Alert group trigger events and the commands that are executed because of a trigger are platform-dependent. For more information, see the corresponding Call Home configuration documentation for your platform.

Examples

The following example shows how to configure a profile to receive periodic configuration alert notifications every day at 9:12 PM (21:12):

Related Commands

Enters call home configuration mode for configuration of Call Home settings.

profile(callhome)

Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.

subscribe-to-alert-groupall

Configures a destination profile to receive messages for all available alert groups for Call Home.

subscribe-to-alert-groupconfiguration

Configures a destination profile to receive messages for the Configuration alert group for Call Home.

subscribe-to-alert-groupdiagnostic

Configures a destination profile to receive messages for the Diagnostic alert group for Call Home.

subscribe-to-alert-groupenvironment

Configures a destination profile to receive messages for the Environment alert group for Call Home.

subscribe-to-alert-groupsyslog

Configures a destination profile to receive messages for the Syslog alert group for Call Home.

subscribe-to-alert-group syslog

To configure a destination profile to receive messages for the Syslog alert group for Call Home, use the
subscribe-to-alert-group syslog command in call home profile configuration mode. To remove the subscription, use the no form of this command.

(Optional) Specifies a word string in the match
argument that should appear in the syslog message to be included in the alert notification. If the pattern contains spaces, you must enclose it in quotes (“ ”).

Command Default

When you configure the subscribe-to-alert-groupsyslog command without specifying any severity, the default is normal severity.

Command Modes

Call home profile configuration (cfg-call-home-profile)

Command History

Release

Modification

12.2(33)SXH

This command was introduced.

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

12.4(24)T

This command was integrated into Cisco IOS Release 12.4(24)T.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

To enter call home profile configuration mode, use the profile(callhome) command in call home configuration mode.

You can configure the Syslog alert group to filter messages based on severity and also by specifying a pattern to be matched in the syslog message. If the pattern contains spaces, you must enclose it in quotes (“ ”).

When specifying severity, selecting a lower level severity includes notification of events with any higher severity.

Note

Alert group trigger events and the commands that are executed because of a trigger are platform-dependent. For more information, see the corresponding Call Home configuration documentation for your platform.

Examples

The following example shows how to configure a profile to receive syslog alerts for events with severity level 5 or higher, where the syslog message includes the string “UPDOWN”:

Related Commands

Enters call home configuration mode for configuration of Call Home settings.

profile(callhome)

Configures a destination profile to specify how alert notifications are delivered for Call Home and enters call home profile configuration mode.

subscribe-to-alert-groupall

Configures a destination profile to receive messages for all available alert groups for Call Home.

subscribe-to-alert-groupconfiguration

Configures a destination profile to receive messages for the Configuration alert group for Call Home.

subscribe-to-alert-groupdiagnostic

Configures a destination profile to receive messages for the Diagnostic alert group for Call Home.

subscribe-to-alert-groupenvironment

Configures a destination profile to receive messages for the Environment alert group for Call Home.

subscribe-to-alert-groupinventory

Configures a destination profile to receive messages for the Inventory alert group for Call Home.

syslog-throttling

To enable Call-Home syslog message throttling and avoid sending repetitive Call-Home syslog messages, use the syslog-throttling command in call home configuration mode. To disable, use the no form of this command.

syslog-throttling

nosyslog-throttling

Syntax Description

This command has no arguments or keywords.

Command Default

Call-Home syslog message throttling is enabled.

Command Modes

Call home configuration (cfg-call-home)

Command History

Release

Modification

15.2(2)T

This command was introduced.

Examples

The following example shows syslog throttling enabled in call home configuration mode:

Router(cfg-call-home)# syslog-throttling

Related Commands

Command

Description

call-home

Enters call home configuration mode.

timers nsf converge

To adjust the maximum time that a restarting router must wait for the end-of-table (EOT) notification from a nonstop forwarding (NSF)-capable or NSF-aware peer, use the
timersnsfconverge command in router configuration or address family configuration mode. To return the signal timer to the default value, use the
no form of this command.

timersnsfconvergeseconds

notimersnsfconverge

Syntax Description

seconds

Time, in seconds, for which a restarting router must wait for an EOT notification. The range is from 60 to 180. The default is 120.

Command Default

The default converge timer is 120 seconds.

Command Modes

Router configuration (config-router)

Address family configuration (config-router-af)

Command History

Release

Modification

12.2(18)S

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

15.0(1)M

This command was modified. Support for Address family configuration mode was added.

12.2(33)SRE

This command was modified. Support for Address family configuration mode was added.

12.2(33)XNE

This command was integrated into Cisco IOS Release 12.2(33)XNE.

Cisco IOS XE Release 2.5

This command was integrated into Cisco IOS XE Release 2.5.

Cisco IOS XE Release 3.6S

This command was modified. Support for IPv6 and IPv6 VPN Routing and Forwarding (VRF) was added.

15.2(2)S

This command was modified. Support for IPv6 and IPv6 VRF was added.

Usage Guidelines

The
timersnsfconverge command is entered only on an NSF-capable router to wait for the last EOT update if all startup updates have not been received within the signal timer period. If an EIGRP process discovers no neighbor, or if it has received all startup updates from its neighbor within the signal timer period, the converge timer will not be started.

Note

The
timersnsfconverge command is supported only on platforms that support High Availability.

Examples

The following example shows how to adjust the converge timer to 60 seconds on an NSF-capable router:

Related Commands

Displays notifications and information about NSF events for an EIGRP routing process.

debugipeigrpnotifications

Displays information and notifications for an EIGRP routing process.

nsf(EIGRP)

Enables EIGRP NSF or EIGRP IPv6 NSF on an NSF-capable router.

showeigrpneighbors

Displays the neighbors discovered by EIGRP.

showipprotocols

Displays the parameters and the current state of the active routing protocol process.

showipv6protocols

Displays the parameters and the current state of the active IPv6 routing protocol process.

timersgraceful-restartpurge-time

Sets the graceful-restart purge-time timer to determine how long an NSF-aware router that is running EIGRP must hold routes for an inactive peer.

timersnsfsignal

Sets the maximum time for the initial restart period.

timers nsf route-hold

Note

Effective with Cisco IOS Release 15.0(1)M and 12.2(33)SRE, the
timersnsfroute-hold command was replaced by the
timersgraceful-restartpurge-timecommand. See the
timersgraceful-restartpurge-timecommand for more information.

To set the route-hold timer to determine how long a nonstop forwarding (NSF)-aware router that is running Enhanced Interior Gateway Routing Protocol (EIGRP) will hold routes for an inactive peer, use the timers nsf route-hold command in router configuration mode. To return the route-hold timer to the default value, use the
no form of this command.

timersnsfroute-holdseconds

notimersnsfroute-hold

Syntax Description

seconds

Time, in seconds, for which EIGRP will hold routes for an inactive peer. Valid range is 20 to 300 seconds. The default is 240 seconds.

Command Default

EIGRP NSF awareness is enabled by default. The default value for the route-hold timer is 240 seconds.

Command Modes

Router configuration (config-router)

Command History

Release

Modification

12.2(15)T

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

15.0(1)M

This command was replaced by the
timersgraceful-restartpurge-timecommand.

12.2(33)SRE

This command was replaced by the
timersgraceful-restartpurge-timecommand.

Usage Guidelines

The route-hold timer sets the maximum period of time that the NSF-aware router will hold known routes for an NSF-capable neighbor during a switchover operation or a well-known failure condition. The route-hold timer is configurable so that you can tune network performance and avoid undesired effects, such as “black holing” routes if the switchover operation takes too much time. When this timer expires, the NSF-aware router scans the topology table and discards any stale routes, allowing EIGRP peers to find alternate routes instead of waiting during a long switchover operation.

Examples

The following configuration example sets the route-hold timer value for an NSF-aware router. In the example, the route-hold timer is set to 2 minutes:

Router(config-router)# timers nsf route-hold 120

Related Commands

Command

Description

debugeigrpnsf

Displays EIGRP NSF-specific events in the console of a router.

debugipeigrpnotifications

Displays EIGRP events and notifications in the console of the router.

showipeigrpneighbors

Displays the neighbors discovered by IP EIGRP.

showipprotocols

Displays the parameters and current state of the active routing protocol process.

timers nsf signal

To adjust the maximum time for the initial signal timer restart period, use the
timersnsfsignal command in router configuration or address family configuration mode. To return the signal timer to the default value, use the
no form of this command.

timersnsfsignalseconds

notimersnsfsignal

Syntax Description

seconds

Time, in seconds, for which the Enhanced Interior Gateway Routing Protocol (EIGRP) must hold routes for an inactive peer. The range is from 10 to 30. The default is 20.

Command Default

The default signal timer is 20 seconds.

Command Modes

Router configuration (config-router)

Address family configuration (config-router-af)

Command History

Release

Modification

12.2(15)T

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

15.0(1)M

This command was modified. Support for Address family configuration mode was added.

12.2(33)SRE

This command was modified. Support for Address family configuration mode was added.

12.2(33)XNE

This command was integrated into Cisco IOS Release 12.2(33)XNE.

Cisco IOS XE Release 2.5

This command was integrated into Cisco IOS XE Release 2.5.

Cisco IOS XE Release 3.6S

This command was modified. Support for IPv6 and IPv6 VPN Routing and Forwarding (VRF) was added.

15.2(2)S

This command was modified. Support for IPv6 and IPv6 VRF was added.

Usage Guidelines

The
timersnsfsignal command is entered only on a nonstop forwarding (NSF)-capable router. The EIGRP process starts a signal timer when it is notified of a switchover event. Hello packets with the RS bit set are sent during this period.

The converge timer is used to wait for the last end-of-table (EOT) update if all startup updates have not been received within the signal timer period. If an EIGRP process discovers no neighbor, or if it has received all startup updates from its neighbor within the signal timer period, the converge timer will not be started.

Note

The
timersnsfsignal command is supported only on platforms that support High Availability.

Examples

The following example shows how to adjust the signal timer to 30 seconds on an NSF-capable router:

Related Commands

Displays notifications and information about NSF events for an EIGRP routing process.

debugipeigrpnotifications

Displays information and notifications for an EIGRP routing process.

nsf(EIGRP)

Enables EIGRP NSF or EIGRP IPv6 NSF on an NSF-capable router.

showeigrpneighbors

Displays the neighbors discovered by EIGRP.

showipprotocols

Displays the parameters and the current state of the active routing protocol process.

showipv6protocols

Displays the parameters and the current state of the active IPv6 routing protocol process.

timersgraceful-restartpurge-time

Sets the graceful-restart purge-time timer to determine how long an NSF-aware router that is running EIGRP must hold routes for an inactive peer.

timersnsfconverge

Sets the maximum time that the restarting router must wait for the end-of-table notification from an NSF-capable or NSF-aware peer.

vrf (call home)

To associate a virtual routing and forwarding (VRF) instance for Call Home email message transport, use the
vrf command in call home configuration mode. To remove the VRF association, use the
no form of this command.

vrfname

novrfname

Syntax Description

name

Name of a configured VRF instance.

Command Default

No VRF is associated for Call Home. On platforms other than the Cisco ASR 1000 Series Aggregation Services Routers, the global routing table is used when this command is not configured.

Command Modes

Call home configuration (cfg-call-home)

Command History

Release

Modification

12.2(33)SXI1

This command was introduced.

12.2(52)SG

This command was integrated into Cisco IOS Release 12.2(52)SG.

Cisco IOS XE Release 2.6

This command was integrated into Cisco IOS XE Release 2.6 on the Cisco ASR 1000 Series Routers.

12.2(33)SRE1

This command was integrated into Cisco IOS Release 12.2(33)SRE1 on the Cisco 7200 Series Routers.

Usage Guidelines

This command is used to configure VRF support in the Call Home feature for email transport only.

To use this command, the VRF instance must be configured on the router.

On the Cisco ASR 1000 Series Aggregation Services Routers, this command is required to support email message transport and uses the Gigabit Ethernet management interface VRF (Mgmt-intf). Therefore, to correctly use the
vrf(call-home) command on the Cisco ASR 1000 Series Router, the Gigabit Ethernet management interface VRF must be configured.

VRF configuration for Call Home on other platforms is optional. If no VRF is specified on those platforms, the global routing table is used.

Note

To configure VRF support in the Call Home feature for HTTP transport, you do not use the
vrf(call-home) command to associate the VRF. Configure the
iphttpclientsource-interface command instead.

Examples

The following example shows how to associate the Mgmt-intf VRF for Call Home on the Cisco ASR 1000 Series Routers:

Router(config)# call-home
Router(cfg-call-home)# vrf Mgmt-intf

The following example shows how to associate the VRF instance for Call Home on the Cisco 7200 Series Routers:

Router(config)# call-home
Router(cfg-call-home)# vrf mgmt-vrf

Related Commands

Command

Description

call-home(globalconfiguration)

Enters call home configuration mode for configuration of Call Home settings.

ipvrf

Defines a VRF instance and enters VRF configuration mode.

ipvrfforwarding (interface
configuration)

Associates a VRF instance with an interface or subinterface.

vrrp sso

To enable Virtual Router Redundancy Protocol (VRRP) support of Stateful Switchover (SSO) if it has been disabled, use the
vrrpsso command in global configuration mode. To disable VRRP support of SSO, use the
no form of this command.

vrrpsso

novrrpsso

Syntax Description

This command has no arguments or keywords.

Command Default

VRRP support of SSO is enabled by default.

Command Modes

Global configuration (config)

Command History

Release

Modification

12.2(33)SRC

This command was introduced.

Cisco IOS XE Release 2.1

This command was integrated into Cisco IOS XE Release 2.1.

12.2(33)SXI

This command was integrated into Cisco IOS Release 12.2(33)SXI.

Usage Guidelines

Use this command to enable VRRP support of SSO if it has been manually disabled by the
novrrpsso command.

Examples

The following example shows how to disable VRRP support of SSO:

Router(config)# no vrrp sso

Related Commands

Command

Description

debugvrrpall

Displays debugging messages for VRRP errors, events, and state transitions.

debugvrrpha

Displays debugging messages for VRRP high availability.

showvrrp

Displays a brief or detailed status of one or all configured VRRP groups.