-
Cisco IOS High Availability Command Reference
-
Introduction
-
action cli through configure replace
-
control-plane through debug mpls ldp checkpoint
-
debug mpls ldp graceful-restart through event wdsysmon
-
frame-relay redundancy auto-sync lmi-sequence-numbers through issu set rollback-timer
-
match mpls-label through route-target
-
service call-home through show ip pim interface
-
show ip pim neighbor through show ppp subscriber statistics
-
show pppatm statistics through vrrp timers learn
-
Table Of Contents
show event manager directory user
show event manager environment
show event manager history events
show event manager history traps
show event manager metric processes
show event manager policy available
show event manager policy pending
show event manager policy registered
show event manager session cli username
show ip bgp vpnv4 all sso summary
show ip multicast redundancy state
show ip multicast redundancy statistics
service call-home
To enable the call-home service, use the service call-home command in global configuration mode. To disable the call-home service, use the no form of this command.
service call-home
no service call-home
Syntax Description
This command has no arguments or keywords.
Command Default
Call-home service is disabled.
Command Modes
Global configuration (config)
Command History
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Examples
This example shows how to enable the call-home service:
Router(config)# service call-homeThis example shows how to disable the call-home service:
Router(config)# no service call-homeRelated Commands
service image-version efsu
To enable Enhanced Fast Software Upgrade (eFSU) functionality, use the no version of the service image-version efsu command in global configuration mode.
no service image-version efsu
Syntax Description
This command has no arguments or keywords.
Defaults
eFSU functionality is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The no service image-version efsu command functionality is similar to that of the service image-version compatibility command. The no service image-version efsu command is used to omit the compatibility matrix creation for Cisco 7600 series router eFSU images.
Examples
The following example enables eFSU functionality:
Router# no service image-version efsuRelated Commands
set (EEM)
Note
Effective with Cisco IOS Release 12.4(22)T, the set (EEM) command is replaced by the action set (EEM) command. See the action set (EEM) command for more information.
To set the value of a local Embedded Event Manager (EEM) applet variable, use the set command in applet configuration mode. To remove the value of an EEM applet variable, use the no form of this command.
set label variable-name variable-value
no set label variable-name variable-value
Syntax Description
Command Default
No EEM applet variable values are set.
Command Modes
Applet configuration (config-applet)
Command History
Usage Guidelines
In EEM applet configuration mode, three types of configuration statements are supported. The event commands are used to specify the event criteria to trigger the applet to run, the action commands are used to specify an action to perform when the EEM applet is triggered, and the set command is used to set the value of an EEM applet variable. Currently only the _exit_status variable is supported for the set command.
Examples
The following example shows how to set the _exit_status variable to represent a successful status after an event has occurred three times and an action has been performed:
Router(config)# event manager applet cli-matchRouter(config-applet)# event cli pattern {.*interface loopback*} sync yes occurs 3Router(config-applet)# action 1.0 cli command "no shutdown"Router(config-applet)# set 1.0 _exit_status 0Related Commands
event manager applet
Registers an event applet with the Embedded Event Manager and enters applet configuration mode.
set mpls-label
To enable a route to be distributed with a Multiprotocol Label Switching (MPLS) label if the route matches the conditions specified in the route map, use the set mpls-label command in route-map configuration mode. To disable this function, use the no form of this command.
set mpls-label
no set mpls-label
Syntax Description
This command has no arguments or keywords.
Command Default
No route with an MPLS label is distributed.
Command Modes
Route-map configuration
Command History
Usage Guidelines
This command can be used only with the neighbor route-map out command to manage outbound route maps for a Border Gateway Protocol (BGP) session.
Use the route-map global configuration command with match and set route-map commands to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
Examples
The following example shows how to create a route map that enables the route to be distributed with a label if the IP address of the route matches an IP address in ACL1:
Router(config-router)# route-map incoming permit 10Router(config-route-map)# match ip address 1Router(config-route-map)# set mpls-labelRelated Commands
show acircuit checkpoint
To display checkpointing information for each attachment circuit (AC), use the show acircuit checkpoint command in privileged EXEC mode.
show acircuit checkpoint
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command is used for interface-based attachment circuits. For Frame Relay and ATM circuits, use the following commands to show redundancy information:
•
•
•
•
•
Examples
The following show acircuit checkpoint command displays information about the ACs that have been check-pointed. The output varies, depending on whether the command output is for the active or standby Route Processor (RP).
On the active RP, the command displays the following output:
Router# show acircuit checkpointAC HA Checkpoint info:Last Bulk Sync: 1 ACsAC IW XC Id VCId Switch Segment St Chkpt---- ---- ---- --- ---- -------- -------- -- -----HDLC LIKE ATOM 3 100 1000 1000 0 NVLAN LIKE ATOM 2 1002 2001 2001 3 YOn the standby RP, the command displays the following output::
Router# show acircuit checkpointAC HA Checkpoint info:AC IW XC Id VCId Switch Segment St F-SLP---- ---- ---- --- ---- -------- -------- -- -----HDLC LIKE ATOM 3 100 0 0 0 001VLAN LIKE ATOM 2 1002 2001 2001 2 000Table 24 describes the significant fields shown in the display.
Related Commands
show archive
To display information about the files saved in the Cisco IOS configuration archive, use the show archive command in privileged EXEC mode.
show archive
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the show archive command:
Router# show archiveThere are currently 1 archive configurations saved.The next archive file will be named disk0:myconfig-2Archive # Name01 disk0:myconfig-1 <- Most Recent234567891011121314The following is sample output from the show archive command after several archive files of the running configuration have been saved. In this example, the maximum number of archive files to be saved is set to three.
Router# show archiveThere are currently 3 archive configurations saved.The next archive file will be named disk0:myconfig-8Archive # Name01 :Deleted2 :Deleted3 :Deleted4 :Deleted5 disk0:myconfig-56 disk0:myconfig-67 disk0:myconfig-7 <- Most Recent891011121314Table 25 describes the significant fields shown in the displays.
Related Commands
show bfd neighbors
To display a line-by-line listing of existing Bidirectional Forwarding Detection (BFD) adjacencies, use the show bfd neighbors command in user EXEC or privileged EXEC mode.
show bfd neighbors [client {bgp | eigrp | isis | ospf | rsvp | te-frr} | details | [interface type number] | internal | ipv4 ip-address | ipv6 ipv6-address | vrf vrf-name]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show bfd neighbors command can be used to help troubleshoot the BFD feature.
The full output for the details keyword is not supported on the Route Processor (RP) for the Cisco 12000 series Internet router. If you want to enter the show bfd neighbors command with the details keyword for the Cisco 12000 series Internet router, you must enter it on the line card. Use the attach slot command to establish a command-line interface (CLI) session with a line card.
Examples
Examples for 12.0(31)S, 12.2(18)SXE, 12.2(33)SRA, 12.2(33)SB, and 12.4(4)T
The following sample output shows the status of the adjacency or neighbor:
Router# show bfd neighborsOurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.1 172.16.10.2 1/6 1 260 (3 ) Up Fa0/1The following sample output from the show bfd neighbors command entered with the details keyword shows BFD protocol parameters and timers for each neighbor:
Router# show bfd neighbors detailsNeighAddr LD/RD RH/RS State Int10.1.1.2 1/1 1(RH) Up Et0/0Session state is UP and not using echo function.OurAddr: 10.1.1.1Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 50000, Multiplier: 3 Received MinRxInt: 50000, Received Multiplier: 3 Holddown (hits): 150(0), Hello (hits): 50(2223) Rx Count: 2212, Rx Interval (ms) min/max/avg: 8/68/49 last: 0 ms ago Tx Count: 2222, Tx Interval (ms) min/max/avg: 40/60/49 last: 20 ms ago Elapsed time watermarks: 0 0 (last: 0) Registered protocols: CEF StubUptime: 00:01:49Last packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 1 - Your Discr.: 1Min tx interval: 50000 - Min rx interval: 50000Min Echo interval: 50000The following sample output from the RP on a Cisco 12000 series router shows the status of the adjacency or neighbor:
Router# show bfd neighborsCleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 2/0 0 0 (0 ) Up Fa6/0Total Adjs Found: 1The following sample output from the RP on a Cisco 12000 series router shows the status of the adjacency or neighbor with the details keyword:
RouterB# show bfd neighbors detailsCleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 2/0 0 0 (0 ) Up Fa6/0Registered protocols: OSPFUptime: never%% BFD Neighbor statistics are not available on RP. Please execute this command on Line Card.The following sample output from a line card on a Cisco 12000 series router shows the status of the adjacency or neighbor:
Router# attach 6Entering Console for 8 Port Fast Ethernet in Slot: 6Type "exit" to end this sessionPress RETURN to get started!Router> show bfd neighborsCleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 2/1 1 848 (5 ) Up Fa6/0Total Adjs Found: 1The following sample output from a line card on a Cisco 12000 series router shows the status of the adjacency or neighbor with the details keyword:
Router# attach 6Entering Console for 8 Port Fast Ethernet in Slot: 6Type "exit" to end this sessionPress RETURN to get started!Router> show bfd neighbors detailsCleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 2/1 1 892 (5 ) Up Fa6/0Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 1000, Multiplier: 3Received MinRxInt: 200000, Received Multiplier: 5Holdown (hits): 1000(0), Hello (hits): 200(193745)Rx Count: 327406, Rx Interval (ms) min/max/avg: 152/248/196 last: 108 ms agoTx Count: 193748, Tx Interval (ms) min/max/avg: 204/440/331 last: 408 ms agoLast packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 5 - Length: 24My Discr.: 1 - Your Discr.: 2Min tx interval: 200000 - Min rx interval: 200000Min Echo interval: 0Uptime: 17:54:07SSO Cleanup Timer called: 0SSO Cleanup Action Taken: 0Pseudo pre-emptive process count: 7728507 min/max/avg: 8/16/8 last: 12 ms agoIPC Tx Failure Count: 0IPC Rx Failure Count: 0Total Adjs Found: 1LC-Slot6>Example for 12.4(9)T and Later Releases
The following sample output verifies that the BFD neighbor router is also running BFD Version 1 and that the BFD session is up and running in echo mode:
Router# show bfd neighbors detailsOurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int172.16.1.2 172.16.1.1 1/6 Up 0 (3 ) Up Fa0/1Session state is UP and using echo function with 50 ms interval.Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3Received MinRxInt: 1000000, Received Multiplier: 3Holdown (hits): 3000(0), Hello (hits): 1000(337)Rx Count: 341, Rx Interval (ms) min/max/avg: 1/1008/882 last: 364 ms agoTx Count: 339, Tx Interval (ms) min/max/avg: 1/1016/886 last: 632 ms agoRegistered protocols: EIGRPUptime: 00:05:00Last packet: Version: 1 - Diagnostic: 0State bit: Up - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 6 - Your Discr.: 1Min tx interval: 1000000 - Min rx interval: 1000000Min Echo interval: 50000Example for Cisco IOS XE Release 2.1 and Later Releases
The following example displays all IPv6 sessions:
Router# show bfd neighbors ipv6 2001::1OurAddr NeighAddr LD/RD RH/RS Holddown(mult) State Int1:1::5 1:1::6 2/2 Up 0 (3 ) Up Et0/02:2::5 2:2::6 4/4 Up 0 (3 ) Up Et1/0Table 26 describes the significant fields shown in the display.
Related Commands
attach
Connects to a specific line card for the purpose of executing monitoring and maintenance commands on that line card only.
show c7300
To display the types and status of cards installed in a Cisco 7304 router, use the show c7300 command in privileged EXEC mode.
show c7300
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the types and status of cards installed in a Cisco 7304 router (such as network services engines [NSEs], RPs, line cards, MSCs, and SPAs), and information about incompatible FPGA images. When the bundled and current FPGA images are compatible, they are not displayed.
This command also displays whether your system is in compliance with line card configuration guidelines. For NSEs and line cards, empty slots are not displayed in the output. However, for SPAs, several status values are reported, including an empty subslot, which is reported as "missing."
If your system contains an unsupported line card or RP with no matching bundled FPGA image in Cisco IOS software, then this command displays "None" instead of the bundled FPGA version number.
Use this command to display information about the status of the active and standby NSEs.
Examples
The following example displays information about a Cisco 7304 router that has current FPGA images:
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE-100 Active 00:13:16 ago4 1OC48-POS Active 00:01:43 agoSystem is compliant with hardware configuration guidelines.All the FPGAs in the system are up-to-dateNetwork IO Interrupt Throttling:throttle count=3, timer count=3active=0, configured=1netint usec=3999, netint mask usec=200The following example displays information about a Cisco 7304 router that has incompatible FPGA images that need to be updated. If your system contains an unsupported line card or RP with no matching bundled FPGA image in Cisco IOS software, "None" is displayed instead of a bundled FPGA version number.
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE-100 Active 00:02:26 ago4 6T3 Active 00:02:23 ago5 6T3 Active 00:02:23 agoSystem is compliant with hardware configuration guidelines.%WARNING:The following FPGAs in the system may need an update.Slot Card Type Current FPGA Bundled FPGA---- --------- ------------ ------------0 NSE-100 (MB) 0.12 NoneNetwork IO Interrupt Throttling:throttle count=0, timer count=0active=0, configured=1netint usec=3999, netint mask usec=200The following example displays sample output information about the redundancy status of the NSEs installed in the system. In the following example, the active RP is the NSE-100 installed in slot 0 and slot 1. The standby is the NSE-100 installed in slot 2 and slot 3.
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE-100 Active 00:02:03 ago2,3 NSE-100 Standby 00:02:03 ago4 4OC3-POS Active 00:01:59 ago5 6T3 Active 00:01:59 agoSystem is compliant with hardware configuration guidelines.Network IO Interrupt Throttling:throttle count=0, timer count=0active=0, configured=1netint usec=3999, netint mask usec=200The following example displays information about a Cisco 7304 router with an NSE-100, MSC-100s, and 4-Port 10/100 Fast Ethernet SPAs:
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE100 Active 00:45:29 ago2 7304-MSC-100 Active 00:44:36 ago3 7304-MSC-100 Active 00:44:36 ago4 7304-MSC-100 Active 00:44:36 ago5 7304-MSC-100 Active 00:14:39 agoThe FPGA versions for the cards listed above are currentShared Port Adapter information:Slot/Subslot SPA Type Status Insertion time------------ -------- ------ --------------2/0 SPA-4FE-7304 ok 00:44:36 ago2/1 SPA-4FE-7304 ok 00:44:36 ago3/0 SPA-4FE-7304 ok 00:44:35 ago3/1 not present missing never4/0 SPA-4FE-7304 ok 00:44:35 ago4/1 SPA-4FE-7304 ok 00:44:35 ago5/0 SPA-4FE-7304 ok 00:14:36 ago5/1 SPA-4FE-7304 ok 00:14:36 agoNetwork IO Interrupt Throttling:throttle count=1, timer count=1active=0, configured=1netint usec=3999, netint mask usec=200Table 27 provides a description for each of the possible status fields for SPAs.
Related Commands
show call-home
To display the configured call-home information, use the show call-home command in privileged EXEC mode.
show call-home [alert-group | detail | mail-server | profile {all | name} | statistics]
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example displays the configured call-home settings:
Router# show call-homeCurrent call home settings:call home feature : disablecall home message's from address: switch@example.comcall home message's reply-to address: support@example.comcontact person's email address: technical@example.comcontact person's phone number: +1-111-111-1111street address: 1234 Any Street, Any city, Any state, 12345customer ID: ExampleCorpcontract ID: X123456789site ID: SantaClaraMail-server[1]: Address: smtp.example.com Priority: 1Mail-server[2]: Address: 192.168.0.1 Priority: 2Rate-limit: 20 message(s) per minuteAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Disable configuration infodiagnostic Disable diagnostic infoenvironment Disable environmental infoinventory Enable inventory infosyslog Disable syslog infoProfiles:Profile Name: campus-nocProfile Name: CiscoTAC-1The following example displays detailed call-home configuration information:
Router# show call-home detailCurrent call home settings:call home feature : disablecall home message's from address: switch@example.comcall home message's reply-to address: support@example.comcontact person's email address: technical@example.comcontact person's phone number: +1-111-111-1111street address: 1234 Any Street, Any city, Any state, 12345customer ID: ExampleCorpcontract ID: X123456789site ID: SantaClaraMail-server[1]: Address: smtp.example.com Priority: 1Mail-server[2]: Address: 192.168.0.1 Priority: 2Rate-limit: 20 message(s) per minuteAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Disable configuration infodiagnostic Disable diagnostic infoenvironment Disable environmental infoinventory Enable inventory infosyslog Disable syslog infoProfiles:Profile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): noc@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AProfile Name: CiscoTAC-1Profile status: INACTIVEPreferred Message Format: xmlMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): callhome@cisco.comHTTP address(es): Not yet set upPeriodic configuration info message is scheduled every 1 day of the month at 09:27Periodic inventory info message is scheduled every 1 day of the month at 09:12Alert-group Severity------------------------ ------------diagnostic minorenvironment minorSyslog-Pattern Severity------------------------ ------------.* majorThe following example displays available call home alert groups:
Router# show call-home alert-groupAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Disable configuration infodiagnostic Disable diagnostic infoenvironment Disable environmental infoinventory Enable inventory infosyslog Disable syslog infoThe following example displays e-mail server status information:
Router# show call-home mail-server statusPlease wait. Checking for mail server status ...Translating "smtp.example.com"Mail-server[1]: Address: smtp.example.com Priority: 1 [Not Available]Mail-server[2]: Address: 192.168.0.1 Priority: 2 [Not Available]The following example displays information for all predefined and user-defined profiles:
Router# show call-home profile allProfile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): noc@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AProfile Name: CiscoTAC-1Profile status: INACTIVEPreferred Message Format: xmlMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): callhome@cisco.comHTTP address(es): Not yet set upPeriodic configuration info message is scheduled every 1 day of the month at 09:27Periodic inventory info message is scheduled every 1 day of the month at 09:12Alert-group Severity------------------------ ------------diagnostic minorenvironment minorSyslog-Pattern Severity------------------------ ------------.* majorThe following example displays information for a user-defined destination profile:
Router# show call-home profile campus-nocProfile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesPreferred Transport Method: emailEmail address(es): noc@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AThe following example displays the call-home statistics:
Router# show call-home statisticsSuccessful Call-Home Events: 0Dropped Call-Home Events due to Rate Limiting: 0Related Commands
show ccm clients
To display information about cluster control manager (CCM) clients on high availability (HA), dual Route Processor systems, use the show ccm clients command in privileged EXEC mode.
show ccm clients
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(31)SB2
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Usage Guidelines
The CCM manages the capability to synchronize session initiation on the standby processor of a dual Route Processor HA system. Use the show ccm clients command to display information about CCM clients.
Examples
The following is sample output from the show ccm clients command on a router's active processor:
Router# show ccm clientsCCM bundles sent since peer up:Sent Queued for flow controlSync Session 10 1Update Session 6 1Active Bulk Sync End 1 0Session Down 10 0ISSU client msgs 115 0Dynamic Session Sync 0 0Unknown msgs 0 0Client events sent since peer up:PPP 66PPPoE 0PPPoA 0AAA 44PPP SIP 11LTERM 11AC 0SSS FM 0IP SIP 0IP IF 0DPM 0COA 0The following is sample output from the show ccm clients command on a router's standby processor:
Router# show ccm clientsCCM bundles rcvd since last boot:Sync Session 8Update Session 0Active Bulk Sync 1Session Down 8ISSU client msgs 59Dynamic Session Sync 0Unknown msgs 0Client events extracted since last boot:PPP 72PPPoE 50PPPoA 0AAA 32PPP SIP 0LTERM 8AC 0SSS FM 0IP SIP 0IP IF 0DPM 0COA 0Auto Svc 0Table 28 describes the significant fields shown in the display. Any data not described in Table 28 is used for Cisco internal debugging purposes.
c
Related Commands
show ccm queues
Displays CCM queue statistics.
show ccm sessions
Displays CCM session information.
show ccm queues
To display cluster control manager (CCM) queue statistics for high availability (HA) dual Route Processor systems, use the show ccm queues command in privileged EXEC mode.
show ccm queues
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(31)SB2
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Usage Guidelines
The CCM manages the capability to synchronize session initiation on the standby processor of a redundant processor HA system. Use the show ccm queues command to display queue statistics for CCM sessions on active and standby processors. This command is generally used only by Cisco engineers for internal debugging of CCM processes.
Examples
The following is sample output from the show ccm queues command. No field descriptions are provided because command output is used for Cisco internal debugging purposes only.
Router# show ccm queues8 Event Queuessize max kicks starts false suspends ticks(ms)4 CCM 0 7 16167 16168 1 0 20Event NamesEvents Queued MaxQueued Suspends usec/evt max/evt1 4 Sync Session 0 0 0 0 0 02 4 Sync Client 0 0 0 0 0 03 4 Update 0 0 0 0 0 04 4 Session Down 0 0 0 0 0 05 4 Bulk Sync Begi 1 0 1 0 0 06 4 Bulk Sync Cont 2 0 2 0 0 07 4 Bulk Sync End 1 0 1 0 0 08 4 Rcv Bulk End 0 0 0 0 0 09 4 Dynamic Sync C 0 0 0 0 0 010 4 Going Active 0 0 0 0 0 011 4 Going Standby 0 0 0 0 0 012 4 Standby Presen 1 0 1 0 0 013 4 Standby Gone 0 0 0 0 0 015 4 CP Message 188 0 7 0 0 016 4 Recr Session 0 0 0 0 0 017 4 Recr Update 0 0 0 0 0 018 4 Recr Sess Down 0 0 0 0 0 019 4 ISSU Session N 1 0 1 0 0 020 4 ISSU Peer Comm 0 0 0 0 0 021 4 Free Session 16103 0 1 0 0 022 4 Sync Dyn Sessi 0 0 0 0 0 023 4 Recr Dyn Sessi 0 0 0 0 0 024 4 Session Ready 0 0 0 0 0 0FSM Event Names Events0 Invalid 01 All Ready 02 Required Not Re 03 Update 04 Down 161035 Error 06 Ready 07 Not Syncable 08 Recreate Down 0Related Commands
show ccm clients
Displays CCM client information.
show ccm sessions
Displays CCM session information.
show ccm sessions
To display information about cluster control manager (CCM) sessions on high availability (HA) dual Route Processor systems, use the show ccm sessions command in privileged EXEC mode.
show ccm sessions
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(31)SB2
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Usage Guidelines
The CCM manages the capability to synchronize session initiation on the standby processor of a redundant processor HA system. Use the show ccm sessions command to display information on CCM sessions on active and standby processors, and also to display information on subscriber redundancy policies configured using the subscriber redundancy command.
Examples
The following is sample output from the show ccm sessions command on a Cisco 10000 series router active processor:
Router# show ccm sessionsGlobal CCM state: CCM HA Active - Dynamic SyncGlobal ISSU state: Compatible, Clients Cap 0x0Number of sessions in state Down: 0Number of sessions in state Not Ready: 0Number of sessions in state Ready: 0Number of sessions in state Dyn Sync: 0Timeout: Timer Type Delay Remaining Starts CPU Limit CPU Last------------ -------- --------- --------- --------- --------Rate 00:00:01 - 2 - -Dynamic CPU 00:00:10 - 0 90 0The following is sample output from the show ccm sessions command on a Cisco 10000 series router standby processor:
Router# show ccm sessionsGlobal CCM state: CCM HA Standby - CollectingGlobal ISSU state: Compatible, Clients Cap 0xFFECurrent Bulk Sent Bulk Rcvd----------- ----------- -----------Number of sessions in state Down: 0 0 0Number of sessions in state Not Ready: 0 0 0Number of sessions in state Ready: 0 0 0Number of sessions in state Dyn Sync: 0 0 0Timeout: Timer Type Delay Remaining Starts CPU Limit CPU Last------------ -------- --------- ----------- --------- --------Rate 00:00:01 - 0 - -Dynamic CPU 00:00:10 - 0 90 0Bulk Time Li 00:08:00 - 0 - -RF Notif Ext 00:00:20 - 0 - -The following is sample output from the show ccm sessions command on a Cisco 7600 series router active processor:
Router# show ccm sessionsGlobal CCM state: CCM HA Active - Dynamic SyncGlobal ISSU state: Compatible, Clients Cap 0xFFFECurrent Bulk Sent Bulk Rcvd----------- ----------- -----------Number of sessions in state Down: 0 0 0Number of sessions in state Not Ready: 7424 0 0Number of sessions in state Ready: 0 0 0Number of sessions in state Dyn Sync: 20002 28001 0Timeout: Timer Type Delay Remaining Starts CPU Limit CPU Last------------ -------- --------- ----------- --------- --------Rate 00:00:01 - 924 - -Dynamic CPU 00:00:10 - 0 90 2Bulk Time Li 00:08:00 - 0 - -RF Notif Ext 00:00:20 - 18 - -The following is sample output from the show ccm sessions command on a Cisco 7600 series router standby processor:
Router# show ccm sessionsGlobal CCM state: CCM HA Standby - CollectingGlobal ISSU state: Compatible, Clients Cap 0xFFECurrent Bulk Sent Bulk Rcvd----------- ----------- -----------Number of sessions in state Down: 0 0 0Number of sessions in state Not Ready: 8038 0 0Number of sessions in state Ready: 20002 0 28001Number of sessions in state Dyn Sync: 0 0 0Timeout: Timer Type Delay Remaining Starts CPU Limit CPU Last------------ -------- --------- ----------- --------- --------Rate 00:00:01 - 0 - -Dynamic CPU 00:00:10 - 0 90 0Bulk Time Li 00:08:00 - 1 - -RF Notif Ext 00:00:20 - 0 - -Table 29 describes the significant fields shown in the display. Any data not described in the table is used for Cisco internal debugging.
Related Commands
show ccm clients
Displays CCM client information.
show ccm queues
Displays CCM queue information.
subscriber redundancy
Configures subscriber session redundancy policies.
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 show cef nsf command in privileged EXEC mode.
show cef nsf
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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 show cef nsf command before a switchover occurs, no switchover activity is reported. After a switchover occurs, you can enter the show cef nsf 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.
Examples
The following example shows the current NSF state:
Router# show cef nsfLast switchover occurred: 00:01:30.088 agoRouting convergence duration: 00:00:34.728FIB stale entry purge durations:00:00:01.728 - Default00:00:00.088 - RedSwitchoverSlot Count Type Quiesce Period1 2 sso 00:00:00.1082 1 rpr+ 00:00:00.9483 2 sso 00:00:00.1525 2 sso 00:00:00.0926 1 rpr+ 00:00:00.632No NSF stats available for the following linecards:4 7Table 30 describes the significant fields shown in the display.
Related Commands
show cef state
To display the state of Cisco Express Forwarding on a networking device, use the show cef state command in privileged EXEC mode.
show cef state
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
Example for Cisco IOS Releases 12.2(25)S, 12.2(28)SB, 12,2(33)SRA, 12,2(33)SXH, 12.4(20T, and Later Releases
The following example shows the state of Cisco Express Forwarding on the active route processor (RP):
Router# show cef stateCEF Status:RP instancecommon CEF enabledIPv4 CEF Status:CEF enabled/runningdCEF disabled/not runningCEF switching enabled/runninguniversal per-destination load sharing algorithm, id A189DD49IPv6 CEF Status:CEF enabled/runningdCEF disabled/not runningoriginal per-destination load sharing algorithm, id A189DD49Table 32 describes the significant fields shown in the display.
Example for Cisco IOS Releases Before Cisco IOS 12.2(25)S
The following example shows the state of Cisco Express Forwarding on the active route processor (RP):
Router# show cef stateRRP state:I am standby RRP: noRF Peer Presence: yesRF PeerComm reached: yesRedundancy mode: SSO(7)CEF NSF: enabled/runningTable 32 describes the significant fields shown in the display.
The following example shows the state of Cisco Express Forwarding on the standby RP:
Router# show cef stateRRP state:I am standby RRP: yesMy logical slot: 0RF Peer Presence: yesRF PeerComm reached: yesCEF NSF: runningRelated Commands
show clns interface
To list the CLNS-specific information about each interface, use the show clns interface command in privileged EXEC mode.
show clns interface [type number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show clns interface command that includes information for Token Ring and serial interfaces:
Router# show clns interfaceTokenRing 0 is administratively down, line protocol is downCLNS protocol processing disabledTokenRing 1 is up, line protocol is upChecksums enabled, MTU 4461, Encapsulation SNAPERPDUs enabled, min. interval 10 msec.RDPDUs enabled, min. interval 100 msec., Addr Mask enabledCongestion Experienced bit set at 4 packetsCLNS fast switching disabledDEC compatibility mode OFF for this interfaceNext ESH/ISH in 18 secondsRouting Protocol: ISO IGRPRouting Domain/Area: <39.0003> <0020>Serial 2 is up, line protocol is upChecksums enabled, MTU 1497, Encapsulation HDLCERPDUs enabled, min. interval 10 msec.RDPDUs enabled, min. interval 100 msec., Addr Mask enabledCongestion Experienced bit set at 4 packetsCLNS fast switching enabledDEC compatibility mode OFF for this interfaceCLNS cluster alias enabled on this interfaceNext ESH/ISH in 48 secondsRouting Protocol: IS-ISCircuit Type: level-1-2Level-1 Metric: 10, Priority: 64, Circuit ID: 0000.0C00.2D55.0ANumber of active level-1 adjacencies: 0Level-2 Metric: 10, Priority: 64, Circuit ID: 0000.0000.0000.00Number of active level-2 adjacencies: 0Next IS-IS LAN Level-1 hello in 3 secondsNext IS-IS LAN Level-2 hello in 3 secondsCisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)T
The following is sample output from the show clns interface command that verifies that the BFD feature has been enabled on Ethernet interface 3/0. The relevant command output is shown in bold in the output.
Router# show clns interface ethernet 3/0Ethernet3/0 is up, line protocol is upChecksums enabled, MTU 1497, Encapsulation SAPERPDUs enabled, min. interval 10 msec.CLNS fast switching enabledCLNS SSE switching disabledDEC compatibility mode OFF for this interfaceNext ESH/ISH in 42 secondsRouting Protocol: IS-ISCircuit Type: level-1-2Interface number 0x1, local circuit ID 0x2Level-1 Metric: 10, Priority: 64, Circuit ID: RouterA.02DR ID: 0000.0000.0000.00Level-1 IPv6 Metric: 10Number of active level-1 adjacencies: 0Level-2 Metric: 10, Priority: 64, Circuit ID: RouterA.02DR ID: 0000.0000.0000.00Level-2 IPv6 Metric: 10Number of active level-2 adjacencies: 0Next IS-IS LAN Level-1 Hello in 3 secondsNext IS-IS LAN Level-2 Hello in 5 secondsBFD enabledTable 33 describes the significant fields shown in the display.
show clns neighbors
To display end system (ES), intermediate system (IS), and multitopology Integrated Intermediate System-to-Intermediate System (M-ISIS) neighbors, use the show clns neighbors command in user EXEC or privileged EXEC mode.
show clns neighbors [process-tag] [interface-type interface-number] [area] [detail]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show clns neighbors command displays the adjacency that is learned through multitopology IS-IS for IPv6.
Examples
The following is sample output from the show clns neighbors command:
Router# show clns neighborsSystem Id Interface SNPA State Holdtime Type Protocol0000.0000.0007 Et3/3 aa00.0400.6408 UP 26 L1 IS-IS0000.0C00.0C35 Et3/2 0000.0c00.0c36 Up 91 L1 IS-IS0800.2B16.24EA Et3/3 aa00.0400.2d05 Up 27 L1 M-ISIS0800.2B14.060E Et3/2 aa00.0400.9205 Up 8 L1 IS-ISThe following is sample output from the show clns neighbors command using the process-tag argument to display information about the VRF-aware IS-IS instance tag1:
Router# show clns tagRED neighborsTag tag1:System Id Interface SNPA State Holdtime Type Protocoligp-03 Fa0/ 200d0.2b7f.9502 Up 9 L2 IS-ISigp-03 PO2/2.1 DLCI 211 Up 27 L2 IS-ISigp-02 PO2/0.1 DLCI 131 Up 29 L2 IS-ISigp-11 Fa0/4 000e.d79d.7920 Up 7 L2 IS-ISigp-11 Fa0/5 000e.d79d.7921 Up 8 L2 IS-ISigp-11 PO3/2.1 DLCI 451 Up 24 L2 IS-ISThe following is sample output from the show clns neighbors command using the detail keyword:
Router# show clns neighbors detailSystem Id Interface SNPA State Holdtime Type Protocol0000.0000.0007 Et3/3 aa00.0400.6408 UP 26 L1 IS-ISArea Address(es): 20IP Address(es): 172.16.0.42*Uptime: 00:21:490000.0C00.0C35 Et3/2 0000.0c00.0c36 Up 91 L1 IS-ISArea Address(es): 20IP Address(es): 192.168.0.42*Uptime: 00:21:520800.2B16.24EA Et3/3 aa00.0400.2d05 Up 27 L1 M-ISISArea Address(es): 20IP Address(es): 192.168.0.42*IPv6 Address(es): FE80::2B0:8EFF:FE31:EC57Uptime: 00:00:27Topology: IPv60800.2B14.060E Et3/2 aa00.0400.9205 Up 8 L1 IS-ISArea Address(es): 20IP Address(es): 192.168.0.30*Uptime: 00:21:52The following is sample output from the show clns neighbors command using the process-tag argument to display information about the VRF-aware IS-IS instance tagSecond:
Router# show clns tagSecond neighborsTag tagSecond:System Id Interface SNPA State Holdtime Type Protocoligp-03 Fa0/2 00d0.2b7f.9502 Up 9 L2 IS-ISigp-03 PO2/2.1 DLCI 211 Up 27 L2 IS-ISigp-02 PO2/0.1 DLCI 131 Up 29 L2 IS-ISigp-11 Fa0/4 000e.d79d.7920 Up 7 L2 IS-ISigp-11 Fa0/5 000e.d79d.7921 Up 8 L2 IS-ISigp-11 PO3/2.1 DLCI 451 Up 24 L2 IS-ISTable 34 describes the significant fields shown in the display.
Notice that the information displayed in the show clns neighbors detail command output includes everything shown in show clns neighbors command output in addition to the area address associated with the IS neighbor and its uptime. When IP routing is enabled, Integrated-ISIS adds information to the output of the show clns commands. The show clns neighbors detail command output shows the IP addresses that are defined for the directly connected interface and an asterisk (*) to indicate which IP address is the next hop.
show configuration lock
To display information about the lock status of the running configuration file during a configuration replace operation, use the show configuration lock command in privileged EXEC mode.
show configuration lock
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC(#)
Command History
Examples
The following is sample output from the show configuration lock command when the running configuration file is locked by another user.
Cisco IOS Release 12.2(25)S, Release 12.2(28)SB, Release 12.3(14)T, and Later Releases
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# configuration mode exclusive ?auto Lock configuration mode automaticallymanual Lock configuration mode on-demandRouter(config)# configuration mode exclusive autoRouter(config)# endRouter# show running-config | include configurationconfiguration mode exclusive autoRouter# configure terminal !<----------- Acquires the lockEnter configuration commands, one per line. End with CNTL/Z.Router(config)# show configuration lockParser Configure Lock --------------------- Owner PID : 3 User : unknown TTY : 0 Type : EXCLUSIVE State : LOCKED Class : EXPOSED Count : 1 Pending Requests : 0 User debug info : configure terminal Router(config)# Router(config)# end ! <------------ Releases the lockThe following is sample output from the show configuration lock command when the running configuration file is not locked by another user.
Router# show configuration lockParser Configure Lock --------------------- Owner PID : -1 User : unknown TTY : -1 Type : NO LOCK State : FREE Class : unknown Count : 0 Pending Requests : 0 User debug info :Cisco IOS Release 12.0(31)S, 12.2(33)SRA, and Later Releases
Router# show configuration lockParser Configure Lock------------------------------------------------------Owner PID : 3User : unknownTTY : 0Type : EXCLUSIVEState : LOCKEDClass : EXPOSEDCount : 1Pending Requests : 0User debug info : configure terminalSession idle state : TRUENo of exec cmds getting executed : 0No of exec cmds blocked : 0Config wait for show completion : FALSERemote ip address : UnknownLock active time (in Sec) : 6Lock Expiration timer (in Sec) : 593Table 35 describes the significant fields shown in the displays.
The following example shows how to configure the configuration file for single user auto configuration mode (using the configuration mode exclusive auto command). Use the configure terminal command to enter global configuration mode and lock the configuration mode exclusively. Once the Cisco IOS configuration mode is locked exclusively, you can verify the lock using the show configuration lock command.
Router# configure terminalRouter(config)# configuration mode exclusive autoRouter(config)# endRouter# configure terminalRouter(config)# show configuration lockParser Configure LockOwner PID : 10User : User1TTY : 3Type : EXCLUSIVEState : LOCKEDClass : ExposedCount : 0Pending Requests : 0User debug info : 0Related Commands
show dampening interface
To display a summary of dampened interfaces, use the show damping interface command in user EXEC or privileged EXEC mode.
show dampening interface
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show damping interface command in privileged EXEC mode:
Router# show dampening interface3 interfaces are configured with dampening.No interface is being suppressed.Features that are using interface dampening:IP RoutingCLNS RoutingTable 36 describes the significant fields shown in the sample output of the show dampening interface command.
Related Commands
show event manager directory user
To display the directory to use for storing user library files or user-defined Embedded Event Manager (EEM) policies, use the show event manager directory user command in privileged EXEC mode.
show event manager directory user [library | policy]
Syntax Description
Command Default
The directories for both user library and user policy files are displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the event manager directory user command to specify the directory to use for storing user library or user policy files.
Examples
The following example shows the /usr/fm_policies folder on disk 0 as the directory to use for storing EEM user library files:
Router# show event manager directory user librarydisk0:/usr/fm_policiesRelated Commands
event manager directory user
Specifies a directory to use for storing user library files or user-defined EEM policies.
show event manager environment
To display the name and value of Embedded Event Manager (EEM) environment variables, use the show event manager environment command in privileged EXEC mode.
show event manager environment [all | variable-name]
Syntax Description
all
(Optional) Displays information for all environment variables. This is the default.
variable-name
(Optional) Displays information about the specified environment variable.
Command Default
If no argument or keyword is specified, information for all environment variables is displayed.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show event manager environment command:
Router# show event manager environmentNo. Name Value1 _cron_entry 0-59/1 0-23/1 * * 0-72 _show_cmd show version3 _syslog_pattern .*UPDOWN.*Ethernet1/0.*4 _config_cmd1 interface Ethernet1/05 _config_cmd2 no shutdownTable 37 describes the significant fields shown in the display.
Related Commands
show event manager history events
To display the Embedded Event Manager (EEM) events that have been triggered, use the show event manager history events command in privileged EXEC mode.
show event manager history events [detailed] [maximum number]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show event manager history events command to track information about the EEM events that have been triggered.
Examples
The following is sample output from the show event manager history events command showing that two types of events, Simple Network Management Protocol (SNMP) and application, have been triggered.
Router# show event manager history eventsNo. Time of Event Event Type Name1 Fri Aug13 21:42:57 2004 snmp applet: SAAping12 Fri Aug13 22:20:29 2004 snmp applet: SAAping13 Wed Aug18 21:54:48 2004 snmp applet: SAAping14 Wed Aug18 22:06:38 2004 snmp applet: SAAping15 Wed Aug18 22:30:58 2004 snmp applet: SAAping16 Wed Aug18 22:34:58 2004 snmp applet: SAAping17 Wed Aug18 22:51:18 2004 snmp applet: SAAping18 Wed Aug18 22:51:18 2004 application applet: CustApp1The following is sample output from the show event manager history events command that includes the Job ID and Status fields:
Router# show event manager history eventsNo. Job ID Status Time of Event Event Type Name1 1 success Thu Sep 7 02:54:04 2006 syslog applet: two2 2 success Thu Sep 7 02:54:04 2006 syslog applet: three3 3 success Thu Sep 7 02:54:04 2006 syslog applet: four4 4 abort Thu Sep 7 02:54:04 2006 syslog applet: five5 5 abort Thu Sep 7 02:54:04 2006 syslog applet: six6 6 abort Thu Sep 7 02:54:04 2006 syslog applet: seven7 7 abort Thu Sep 7 02:54:04 2006 syslog applet: eight8 8 cleared Thu Sep 7 02:54:04 2006 syslog applet: nine9 9 cleared Thu Sep 7 02:54:04 2006 syslog applet: ten10 10 cleared Thu Sep 7 02:54:04 2006 syslog applet: elevenThe following is sample output from the show event manager history events command using the detailed keyword:
Router# show event manager history events detailedNo. Job ID Status Time of Event Event Type Name1 1 success Thu Sep 7 02:54:04 2006 syslog applet: twomsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}2 2 success Thu Sep 7 02:54:04 2006 syslog applet: threemsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}3 3 success Thu Sep 7 02:54:04 2006 syslog applet: fourmsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}4 4 abort Thu Sep 7 02:54:04 2006 syslog applet: fivemsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}5 5 abort Thu Sep 7 02:54:04 2006 syslog applet: sixmsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}6 6 abort Thu Sep 7 02:54:04 2006 syslog applet: sevenmsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}7 7 cleared Thu Sep 7 02:54:04 2006 syslog applet: eightmsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}8 8 cleared Thu Sep 7 02:54:04 2006 syslog applet: ninemsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}9 9 cleared Thu Sep 7 02:54:04 2006 syslog applet: tenmsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}10 10 success Thu Sep 7 02:54:04 2006 syslog applet: elevenmsg {23:13:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console}Table 38 describes the significant fields shown in the displays.
Related Commands
event manager history size
Modifies the size of the EEM history tables.
event manager scheduler clear
Clears EEM policies that are executing or pending execution.
show event manager history traps
To display the Embedded Event Manager (EEM) Simple Network Management Protocol (SNMP) traps that have been sent, use the show event manager history traps command in privileged EXEC mode.
show event manager history traps [server | policy]
Syntax Description
server
(Optional) Displays SNMP traps that were triggered from the EEM server.
policy
(Optional) Displays SNMP traps that were triggered from within an EEM policy.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show event manager history traps command to identify whether the SNMP traps were implemented from the EEM server or from an EEM policy.
Examples
The following is sample output from the show event manager history traps command:
Router# show event manager history traps policyNo. Time Trap Type Name1 Wed Aug18 22:30:58 2004 policy EEM Policy Director2 Wed Aug18 22:34:58 2004 policy EEM Policy Director3 Wed Aug18 22:51:18 2004 policy EEM Policy DirectorTable 39 describes the significant fields shown in the display.
Related Commands
show event manager metric processes
To display Embedded Event Manager (EEM) reliability metric data for Cisco IOS Software Modularity processes, use the show event manager metric processes command in privileged EXEC mode.
show event manager metric processes {all | process-name}
Syntax Description
all
Displays the process metric data for all Cisco IOS Software Modularity processes.
process-name
Specific process name.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the reliability metric data for Cisco IOS Software Modularity processes. The system keeps a record of when processes start and end, and this data is used as the basis for reliability analysis.
The information provided by this command allows you to get availability information for a process or group of processes. A process is considered available when it is running.
Examples
The following is partial sample output from the show event manager metric processes command. In this partial example, the first and last entries showing the metric data for the processes on all the cards inserted in the system are displayed.
Router# show event manager metric processes all=====================================node name: node0process name: devc-pty, instance: 1sub_system: 0, version: 00.00.0000--------------------------------last event type: process startrecent start time: Fri Oct10 20:34:40 2003recent normal end time: n/arecent abnormal end time: n/anumber of times started: 1number of times ended normally: 0number of times ended abnormally: 0most recent 10 process start times:--------------------------Fri Oct10 20:34:40 2003--------------------------most recent 10 process end times and types:cumulative process available time: 6 hours 30 minutes 7 seconds 378 millisecondscumulative process unavailable time: 0 hours 0 minutes 0 seconds 0 millisecondsprocess availability: 0.100000000number of abnormal ends within the past 60 minutes (since reload): 0number of abnormal ends within the past 24 hours (since reload): 0number of abnormal ends within the past 30 days (since reload): 0...=====================================node name: node0process name: cdp2.iosproc, instance: 1sub_system: 0, version: 00.00.0000--------------------------------last event type: process startrecent start time: Fri Oct10 20:35:02 2003recent normal end time: n/arecent abnormal end time: n/anumber of times started: 1number of times ended normally: 0number of times ended abnormally: 0most recent 10 process start times:--------------------------Fri Oct10 20:35:02 2003--------------------------most recent 10 process end times and types:cumulative process available time: 6 hours 29 minutes 45 seconds 506 millisecondscumulative process unavailable time: 0 hours 0 minutes 0 seconds 0 millisecondsprocess availability: 0.100000000number of abnormal ends within the past 60 minutes (since reload): 0number of abnormal ends within the past 24 hours (since reload): 0number of abnormal ends within the past 30 days (since reload): 0Table 40 describes the significant fields shown in the display.
show event manager policy available
To display Embedded Event Manager (EEM) policies that are available to be registered, use the show event manager policy available command in privileged EXEC mode.
show event manager policy available [description [policy-name] | [detailed policy-filename] [system | user]]
Syntax Description
Command Default
If no keyword is specified, information for all available system and user policies is displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command is useful if you forget the exact name of a policy required for the event manager policy command.
The detailed keyword displays the actual specified sample policy. Use description policy-name to describe a policy. If policy-name is not specified, the output of show command displays the description of all the available policies.
In Cisco IOS Release 12.4(20)T, EEM 2.4 introduced bytecode support to allow storage of Tcl scripts in bytecode format, and the output of this command was modified to display files with a .tbc extension as well as the usual .tcl extension for Tcl scripts.
Examples
The following is sample output from the show event manager policy available command:
Router# show event manager policy availableNo. Type Time Created Name1 system Tue Sep 12 09:41:32 2002 sl_intf_down.tcl2 system Tue Sep 12 09:41:32 2002 tm_cli_cmd.tclTable 41 describes the fields shown in the display.
The following is sample output from the show event manager policy available command with the detailed keyword and a policy name specified:
Router# show event manager policy available detailed tm_cli_cmd.tcl::cisco::eem::event_register_timer cron name crontimer2 cron_entry $_cron_entry maxrun 240#------------------------------------------------------------------# EEM policy that will periodically execute a cli command and email the# results to a user.## July 2005, Cisco EEM team## Copyright (c) 2005 by cisco Systems, Inc.# All rights reserved.#------------------------------------------------------------------### The following EEM environment variables are used:###### _cron_entry (mandatory) - A CRON specification that determines### when the policy will run. See the### IOS Embedded Event Manager### documentation for more information### on how to specify a cron entry.### Example: _cron_entry 0-59/1 0-23/1 * * 0-7###### _email_server (mandatory) - A Simple Mail Transfer Protocol (SMTP)### mail server used to send e-mail.### Example: _email_server mailserver.customer.com###The following is sample output from the show event manager policy available command showing a Tcl script with a .tcl filename extension and a bytecode script with a filename extension of .tbc. This example is for a Cisco IOS Release 12.4(20)T or later image.
Router# show event manager policy availableNo. Type Time Created Name1 system Tue Jun 10 09:41:32 2008 sl_intf_down.tcl2 system Tue Jun 10 09:41:32 2008 tm_cli_cmd.tbcRelated Commands
show event manager policy pending
To display Embedded Event Manager (EEM) policies that are pending for execution, use the show event manager policy pending command in privileged EXEC mode.
show event manager policy pending [queue-type {applet | call-home | axp | script} | class class-options | detailed]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Pending policies are policies that are pending execution in the EEM server execution queue. When an event is triggered, the policy that is registered to handle the event is queued for execution in the EEM server. Use the show event manager policy pending command to display the policies in this queue and to view the policy details.
Examples
The following is sample output from the show event manager policy pending command:
Router# show event manager policy pendingno. job id p s status time of event event type name1 12851 N A pend Mon Oct29 20:51:18 2007 timer watchdog loop.tcl2 12868 N A pend Mon Oct29 20:51:24 2007 timer watchdog loop.tcl3 12873 N A pend Mon Oct29 20:51:27 2007 timer watchdog loop.tcl4 12907 N A pend Mon Oct29 20:51:41 2007 timer watchdog loop.tcl5 13100 N A pend Mon Oct29 20:52:55 2007 timer watchdog loop.tclTable 42 describes the significant fields shown in the displays.
Related Commands
show event manager policy registered
To display Embedded Event Manager (EEM) policies that are already registered, use the show event manager policy registered command in privileged EXEC mode.
show event manager policy registered [description [policy-name] | detailed policy-filename [system | user] | [event-type event-name] [system | user] [time-ordered | name-ordered]]
Syntax Description
Command Default
If this command is invoked with no optional keywords, it displays all registered EEM system and user policies for all event types. The policies are displayed according to the time at which they were registered.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The output shows registered policy information in two parts. The first line in each policy description lists the index number assigned to the policy, the policy type (system), the type of event registered, the time when the policy was registered, and the name of the policy file. The remaining lines of each policy description display information about the registered event and how the event is to be handled; the information comes directly from the Tool Command Language (Tcl) command arguments that make up the policy file. Output of the show event manager policy registered command is most helpful to persons who are writing and monitoring EEM policies.
The detailed keyword displays the actual specified sample policy including details about the environment variables used by the policy and instructions for running the policy.
Examples
The following is sample output from the show event manager policy registered command:
Router# show event manager policy registeredNo. Class Type Event Type Trap Time Registered Name1 applet system snmp Off Fri Aug 13 17:42:52 2004 IPSLAping1oid {1.3.6.1.4.1.9.9.42.1.2.9.1.6.4} get-type exact entry-op eq entry-val {1}exit-op eq exit-val {2} poll-interval 5.000action 1.0 syslog priority critical msg Server IPecho Failed: OID=$_snmp_oid_valaction 1.1 snmp-trap strdata EEM detected server reachability failure to 10.1.88.9action 1.2 publish-event sub-system 88000101 type 1 arg1 10.1.88.9 arg2 IPSLAEcho arg3 failaction 1.3 counter name _IPSLA1F value 1 op incTable 43 describes the significant fields shown in the display.
The following is sample output from the show event manager policy registered command showing the use of the detailed keyword for the policy named tm_cli_cmd.tcl:
Router# show event manager policy registered detailed tm_cli_cmd.tcl::cisco::eem::event_register_timer cron name crontimer2 cron_entry $_cron_entry maxrun 240#------------------------------------------------------------------# EEM policy that will periodically execute a cli command and email the# results to a user.## July 2005, Cisco EEM team## Copyright (c) 2005 by cisco Systems, Inc.# All rights reserved.#------------------------------------------------------------------### The following EEM environment variables are used:###### _cron_entry (mandatory) - A CRON specification that determines### when the policy will run. See the### IOS Embedded Event Manager### documentation for more information### on how to specify a cron entry.### Example: _cron_entry 0-59/1 0-23/1 * * 0-7###### _email_server (mandatory) - A Simple Mail Transfer Protocol (SMTP)### mail server used to send e-mail.### Example: _email_server mailserver.example.com###Related Commands
show event manager session cli username
To display the username associated with Embedded Event Manager (EEM) policies that use the command-line interface (CLI) library, use the show event manager session cli username command in privileged EXEC mode.
show event manager session cli username
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the username associated with a Tool Command Language (Tcl) EEM policy. If you are using authentication, authorization, and accounting (AAA) security and implement authorization on a command basis, you should use the event manager session cli username command to set a username to be associated with a Tcl session. The username is used when a Tcl policy executes a CLI command. TACACS+ verifies each CLI command using the username associated with the Tcl session that is running the policy. Commands from Tcl policies are not usually verified because the router must be in privileged EXEC mode to register the policy.
Examples
The following example shows that the username of eemuser is associated with a Tcl session:
Router# show event manager session cli usernameRelated Commands
event manager session cli username
Associates a username with EEM policies that use the CLI library.
show glbp
To display Gateway Load Balancing Protocol (GLBP) information, use the show glbp command in privileged EXEC mode.
show glbp [capability [interface-type interface-number ]] | [[interface-type interface-number [group-number] [state] [brief ] [detail] [client-cache [[age number] [forwarder number]] | [mac-address address] | [summary]]]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show glbp command to display information about GLBP groups on a router. The brief keyword displays a single line of information about each virtual gateway or virtual forwarder. The client-cache keyword displays the client cache details and the capability keyword displays all GLBP-capable interfaces.
Examples
The following is sample output from the show glbp command:
Router# show glbpFastEthernet0/0 - Group 10State is Active2 state changes, last state change 23:50:33Virtual IP address is 10.21.8.10Hello time 5 sec, hold time 18 secNext hello sent in 4.300 secsRedirect time 600 sec, forwarder time-out 7200 secAuthentication MD5, key-stringPreemption enabled, min delay 60 secActive is localStandby is unknownPriority 254 (configured)Weighting 105 (configured 110), thresholds: lower 95, upper 105Track object 2 state Down decrement 5Load balancing: host-dependentThere is 1 forwarder (1 active)Forwarder 1State is Active1 state change, last state change 23:50:15MAC address is 0007.b400.0101 (default)Owner ID is 0005.0050.6c08Redirection enabledPreemption enabled, min delay 60 secActive is local, weighting 105The following is sample output from the show glbp command with the brief keyword specified:
Router# show glbp briefInterface Grp Fwd Pri State Address Active router Standby routerFa0/0 10 - 254 Active 10.21.8.10 local unknownFa0/0 10 1 7 Active 0007.b400.0101 local -The following is sample output from the show glbp command that displays GLBP group 10:
Router# show glbp 10FastEthernet0/0 - Group 10State is Active2 state changes, last state change 23:50:33Virtual IP address is 10.21.8.10Hello time 5 sec, hold time 18 secNext hello sent in 4.300 secsRedirect time 600 sec, forwarder time-out 7200 secAuthentication MD5, key-stringPreemption enabled, min delay 60 secActive is localStandby is unknownPriority 254 (configured)Weighting 105 (configured 110), thresholds: lower 95, upper 105Track object 2 state Down decrement 5Load balancing: host-dependentThere is 1 forwarder (1 active)Forwarder 1State is Active1 state change, last state change 23:50:15MAC address is 0007.b400.0101 (default)Owner ID is 0005.0050.6c08Redirection enabledPreemption enabled, min delay 60 secActive is local, weighting 105The following output shows that the redundancy name has been assigned to the "glbp1" group:
Router# show glbp ethernet0/1 1
Ethernet0/1 - Group 1
State is Listen
64 state changes, last state change 00:00:54
Virtual IP address is 10.1.0.7
Hello time 50 msec, hold time 200 msec
Next hello sent in 0.030 secs
Redirect time 600 sec, forwarder time-out 14400 sec
Authentication text, string "authword"Preemption enabled, min delay 0 sec
Active is 10.1.0.2, priority 105 (expires in 0.184 sec)
Standby is 10.1.0.3, priority 100 (expires in 0.176 sec)
Priority 96 (configured)
Weighting 100 (configured 100), thresholds: lower 95, upper 100
Track object 1 state Up decrement 10
Load balancing: round-robin
IP redundancy name is "glbp1"
Group members:
0004.4d83.4801 (10.0.0.0)
0010.7b5a.fa41 (10.0.0.1)
00d0.bbd3.bc21 (10.0.0.2) local
The following output shows GLBP support for SSO mode on an active RP:
Router# show glbpEthernet0/0 - Group 1State is Standby1 state change, last state change 00:00:20Virtual IP address is 172.24.1.254Hello time 3 sec, hold time 10 secNext hello sent in 0.232 secsRedirect time 600 sec, forwarder time-out 14400 secPreemption disabledActive is 172.24.1.2, priority 100 (expires in 7.472 sec)Standby is localPriority 100 (default)Weighting 100 (default 100), thresholds: lower 1, upper 100Load balancing: round-robinGroup members:aabb.cc00.0100 (172.24.1.1) localaabb.cc00.0200 (172.24.1.2)There are 2 forwarders (1 active)Forwarder 1State is ListenMAC address is 0007.b400.0101 (learnt)Owner ID is aabb.cc00.0200Time to live: 14397.472 sec (maximum 14400 sec)Preemption enabled, min delay 30 secActive is 172.24.1.2 (primary), weighting 100 (expires in 9.540 sec)Forwarder 2State is Active1 state change, last state change 00:00:28MAC address is 0007.b400.0102 (default)Owner ID is aabb.cc00.0100Preemption enabled, min delay 30 secActive is local, weighting 100The following output shows GLBP support for SSO mode on a standby RP:
RouterRP-standby# show glbpEthernet0/0 - Group 1State is Init (standby RP, peer state is Standby)Virtual IP address is 172.24.1.254Hello time 3 sec, hold time 10 secRedirect time 600 sec, forwarder time-out 14400 secPreemption disabledActive is unknownStandby is unknownPriority 100 (default)Weighting 100 (default 100), thresholds: lower 1, upper 100Load balancing: round-robinGroup members:aabb.cc00.0100 (172.24.1.1) localaabb.cc00.0200 (172.24.1.2)There are 2 forwarders (0 active)Forwarder 1State is Init (standby RP, peer state is Listen)MAC address is 0007.b400.0101 (learnt)Owner ID is aabb.cc00.0200Preemption enabled, min delay 30 secActive is unknownForwarder 2State is Init (standby RP, peer state is Active)MAC address is 0007.b400.0102 (default)Owner ID is aabb.cc00.0100Preemption enabled, min delay 30 secActive is unknownGLBP support for Stateful Switchover (SSO) mode is enabled by default but may be disabled by the no glbp sso command. If GLBP support for SSO mode is disabled, the output of the show glbp command on the standby RP will display a warning:
RouterRP-standby# show glbpEthernet0/0 - Group 1State is Init (GLBP SSO disabled) <------ GLBP SSO is disabled.Virtual IP address is 172.24.1.254Hello time 3 sec, hold time 10 secRedirect time 600 sec, forwarder time-out 14400 secPreemption disabledActive is unknownStandby is unknownPriority 100 (default)Weighting 100 (default 100), thresholds: lower 1, upper 100Load balancing: round-robinGroup members:aabb.cc00.0100 (172.24.1.1) localThere are 2 forwarders (0 active)Forwarder 1State is Init (GLBP SSO disabled)MAC address is 0007.b400.0101 (learnt)Owner ID is aabb.cc00.0200Preemption enabled, min delay 30 secActive is unknownForwarder 2State is Init (GLBP SSO disabled)MAC address is 0007.b400.0102 (default)Owner ID is aabb.cc00.0100Preemption enabled, min delay 30 secActive is unknownTable 44 describes the significant fields shown in the displays.
Related Commands
show interface dampening
To display dampened interfaces on the local router, use the show interface dampening command in privileged EXEC mode.
show interface dampening
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show interface dampening command:
Router# show interface dampeningFlaps Penalty Supp ReuseTm HalfL ReuseV SuppV MaxSTm MaxP Restart0 0 FALSE 0 5 1000 2000 20 16000 0Table 45 describes the significant fields shown in the display.
Related Commands
clear counters
Clears the interface counters.
dampening
Enables IP event dampening at the interface level.
show dampening interface
Displays a summary of interface dampening.
show ip bgp
To display entries in the Border Gateway Protocol (BGP) routing table, use the show ip bgp command in user EXEC or privileged EXEC mode.
show ip bgp [ip-address [mask [longer-prefixes [injected] | shorter-prefixes [length]]] | all | oer-paths | prefix-list name | route-map name]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show ip bgp 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.
In Cisco IOS Release 12.0(32)SY8, 12.0(33)S3, 12.2(33)SRE, 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 bgp asnotation dot command followed by the clear ip bgp * command to perform a hard reset of all current BGP sessions.
In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, the Cisco implementation of 4-byte autonomous system numbers uses asdot—1.2 for example—as the only configuration format, regular expression match, and output display, with no asplain support.
oer-paths Keyword
In Cisco IOS Release 12.3(8)T, and later releases, BGP prefixes that are monitored and controlled by OER are displayed by entering the show ip bgp command with the oer-paths keyword.
Examples
•
•
•
•
•
•
show ip bgp: Example
The following example output shows the BGP routing table:
Router# show ip bgpBGP table version is 22, local router ID is 10.1.1.1Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,r RIB-failure, S Stale, m multipath, b backup-path, x best-externalOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 10.1.1.1/32 0.0.0.0 0 32768 i*>i10.2.2.2/32 172.16.1.2 0 100 0 i*bi10.9.9.9/32 192.168.3.2 0 100 0 10 10 i*> 192.168.1.2 0 10 10 i* i172.16.1.0/24 172.16.1.2 0 100 0 i*> 0.0.0.0 0 32768 i*> 192.168.1.0 0.0.0.0 0 32768 i*>i192.168.3.0 172.16.1.2 0 100 0 i*bi192.168.9.0 192.168.3.2 0 100 0 10 10 i*> 192.168.1.2 0 10 10 i*bi192.168.13.0 192.168.3.2 0 100 0 10 10 i*> 192.168.1.2 0 10 10 iTable 46 describes the significant fields shown in the display.
show ip bgp (4-Byte Autonomous System Numbers): Example
The following example output shows the BGP routing table with 4-byte autonomous system numbers, 65536 and 65550, shown under the Path field. This example requires Cisco IOS Release 12.0(32)SY8, 12.0(33)S3, 12.2(33)SRE, 12.2(33)SXI1, Cisco IOS XE Release 2.4, or a later release.
RouterB# show ip bgpBGP table version is 4, local router ID is 172.17.1.99Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,r RIB-failure, S StaleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 10.1.1.0/24 192.168.1.2 0 0 65536 i*> 10.2.2.0/24 192.168.3.2 0 0 65550 i*> 172.17.1.0/24 0.0.0.0 0 32768 ishow ip bgp ip-address: Example
The following example displays information about the 192.168.1.0 entry in the BGP routing table:
Router# show ip bgp 192.168.1.0BGP routing table entry for 192.168.1.0/24, version 22Paths: (2 available, best #2, table default)Additional-pathAdvertised to update-groups:310 10192.168.3.2 from 172.16.1.2 (10.2.2.2)Origin IGP, metric 0, localpref 100, valid, internal, backup/repair10 10192.168.1.2 from 192.168.1.2 (10.3.3.3)Origin IGP, localpref 100, valid, external, best , recursive-via-connectedRouter# show ip bgp 10.3.3.3 255.255.255.255BGP routing table entry for 10.3.3.3/32, version 35Paths: (3 available, best #2, table default)Multipath: eBGPFlag: 0x860Advertised to update-groups:120010.71.8.165 from 10.71.8.165 (192.168.0.102)Origin incomplete, localpref 100, valid, external, backup/repairOnly allowed to recurse through connected route20010.71.11.165 from 10.71.11.165 (192.168.0.102)Origin incomplete, localpref 100, weight 100, valid, external, bestOnly allowed to recurse through connected route20010.71.10.165 from 10.71.10.165 (192.168.0.104)Origin incomplete, localpref 100, valid, external,Only allowed to recurse through connected routeTable 47 describes the significant fields shown in the display.
show ip bgp all: Example
The following example output from the show ip bgp command entered with the all keyword. Information about all configured address families is displayed.
Router# show ip bgp allFor address family: IPv4 Unicast *****BGP table version is 27, local router ID is 10.1.1.1Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,r RIB-failureOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 10.1.1.0/24 0.0.0.0 0 32768 ?*> 10.13.13.0/24 0.0.0.0 0 32768 ?*> 10.15.15.0/24 0.0.0.0 0 32768 ?*>i10.18.18.0/24 172.16.14.105 1388 91351 0 100 e*>i10.100.0.0/16 172.16.14.107 262 272 0 1 2 3 i*>i10.100.0.0/16 172.16.14.105 1388 91351 0 100 e*>i10.101.0.0/16 172.16.14.105 1388 91351 0 100 e*>i10.103.0.0/16 172.16.14.101 1388 173 173 100 e*>i10.104.0.0/16 172.16.14.101 1388 173 173 100 e*>i10.100.0.0/16 172.16.14.106 2219 20889 0 53285 33299 51178 47751 e*>i10.101.0.0/16 172.16.14.106 2219 20889 0 53285 33299 51178 47751 e* 10.100.0.0/16 172.16.14.109 2309 0 200 300 e*> 172.16.14.108 1388 0 100 e* 10.101.0.0/16 172.16.14.109 2309 0 200 300 e*> 172.16.14.108 1388 0 100 e*> 10.102.0.0/16 172.16.14.108 1388 0 100 e*> 172.16.14.0/24 0.0.0.0 0 32768 ?*> 192.168.5.0 0.0.0.0 0 32768 ?*> 10.80.0.0/16 172.16.14.108 1388 0 50 e*> 10.80.0.0/16 172.16.14.108 1388 0 50 eFor address family: VPNv4 Unicast *****BGP table version is 21, local router ID is 10.1.1.1Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,r RIB-failureOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight PathRoute Distinguisher: 1:1 (default for vrf vpn1)*> 10.1.1.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e*> 10.1.2.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e*> 10.1.3.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e*> 10.1.4.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e*> 10.1.5.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e*>i172.17.1.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?*>i172.17.2.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?*>i172.17.3.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?*>i172.17.4.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?*>i172.17.5.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?For address family: IPv4 Multicast *****BGP table version is 11, local router ID is 10.1.1.1Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,r RIB-failureOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 10.40.40.0/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e* 10.1.1.1 1622 0 15 20 1 {2} e*> 10.40.40.64/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e* 10.1.1.1 1622 0 15 20 1 {2} e*> 10.40.40.128/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e* 10.1.1.1 2563 0 15 20 1 {2} e*> 10.40.40.192/26 10.1.1.1 2563 0 15 20 1 {2} e*> 10.40.41.0/26 10.1.1.1 1209 0 15 20 1 {2} e*>i10.102.0.0/16 10.1.1.1 300 500 0 5 4 {101,102} e*>i10.103.0.0/16 10.1.1.1 300 500 0 5 4 {101,102} eFor address family: NSAP Unicast *****BGP table version is 1, local router ID is 10.1.1.1Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,r RIB-failureOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path* i45.0000.0002.0001.000c.0049.0001.0000.0000.0a00100 0 ?* i46.0001.0000.0000.0000.0a0049.0001.0000.0000.0a00100 0 ?* i47.0001.0000.0000.000b.0049.0001.0000.0000.0a00100 0 ?* i47.0001.0000.0000.000e.0049.0001.0000.0000.0a00show ip bgp longer-prefixes: Example
The following is example output from the show ip bgp command entered with the longer-prefixes keyword:
Router# show ip bgp 10.92.0.0 255.255.0.0 longer-prefixesBGP table version is 1738, local router ID is 192.168.72.24Status codes: s suppressed, * valid, > best, i - internalOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 10.92.0.0 10.92.72.30 8896 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.1.0 10.92.72.30 8796 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.11.0 10.92.72.30 42482 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.14.0 10.92.72.30 8796 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.15.0 10.92.72.30 8696 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.16.0 10.92.72.30 1400 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.17.0 10.92.72.30 1400 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.18.0 10.92.72.30 8876 32768 ?* 10.92.72.30 0 109 108 ?*> 10.92.19.0 10.92.72.30 8876 32768 ?* 10.92.72.30 0 109 108 ?show ip bgp shorter-prefixes: Example
The following is example output from the show ip bgp command entered with the shorter-prefixes keyword. An 8-bit prefix length is specified.
Router# show ip bgp 172.16.0.0/16 shorter-prefixes 8*> 172.16.0.0 10.0.0.2 0 ?* 10.0.0.2 0 0 200 ?show ip bgp prefix-list: Example
The following is example output from the show ip bgp command entered with the prefix-list keyword:
Router# show ip bgp prefix-list ROUTEBGP table version is 39, local router ID is 10.0.0.1Status codes:s suppressed, d damped, h history, * valid, > best, i -internalOrigin codes:i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 192.168.1.0 10.0.0.2 0 ?* 10.0.0.2 0 0 200 ?show ip bgp route-map: Example
The following is example output from the show ip bgp command entered with the route-map keyword:
Router# show ip bgp route-map LEARNED_PATHBGP table version is 40, local router ID is 10.0.0.1Status codes:s suppressed, d damped, h history, * valid, > best, i -internalOrigin codes:i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 192.168.1.0 10.0.0.2 0 ?* 10.0.0.2 0 0 200 ?Related Commands
show ip bgp labels
To display information about Multiprotocol Label Switching (MPLS) labels from the external Border Gateway Protocol (eBGP) route table, use the show ip bgp labels command in privileged EXEC mode.
show ip bgp labels
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display eBGP labels associated with an Autonomous System Boundary Router (ASBR).
This command displays labels for BGP routes in the default table only. To display labels in the Virtual Private Network (VPN) routing and forwarding (VRF) tables, use the show ip bgp vpnv4 {all | vrf vrf-name} command with the optional labels keyword.
Examples
The following example shows output for an ASBR using BGP as a label distribution protocol:
Router# show ip bgp labelsNetwork Next Hop In Label/Out Label10.3.0.0/16 0.0.0.0 imp-null/exp-null10.15.15.15/32 10.15.15.15 18/exp-null10.16.16.16/32 0.0.0.0 imp-null/exp-null10.17.17.17/32 10.0.0.1 20/exp-null10.18.18.18/32 10.0.0.1 24/3110.18.18.18/32 10.0.0.1 24/33Table 48 describes the significant fields shown in the display.
Related Commands
show ip bgp neighbors
To display information about Border Gateway Protocol (BGP) and TCP connections to neighbors, use the show ip bgp neighbors command in user or privileged EXEC mode.
show ip bgp neighbors [ip-address [advertised-routes | dampened-routes | flap-statistics |
paths [reg-exp] | received prefix-filter | received-routes | routes | policy [detail]]]Syntax Description
Command Default
The output of this command displays information for all neighbors.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
Use the show ip bgp neighbors 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)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 a
