To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the
showgsr command in EXEC mode.
showgsr
[ chassis-info [details] ]
Syntax Description
chassis-info
(Optional) Displays backplane NVRAM information.
details
(Optional) In addition to the information displayed, this option includes hexadecimal output of the backplane NVRAM information.
Command Modes
EXEC
Command History
Release
Modification
11.2GS
This command was introduced to support the Cisco 12000 series GSRs.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use this command to determine the type of hardware installed in your Cisco 12000 series GSR router.
Examples
The following is sample output from the
showgsrcommand for a Cisco 12012 router. This command shows the type and state of the card installed in the slot.
Router# show gsr
Slot 0 type = Route Processor
state = IOS Running MASTER
Slot 7 type = 1 Port Packet Over SONET OC-12c/STM-4c
state = Card Powered
Slot 16 type = Clock Scheduler Card
state = Card Powered PRIMARY CLOCK
The following is sample output from the
showgsrchassis-infocommand for a Cisco 12012 router:
Router# show gsr chassis-info
Backplane NVRAM [version 0x20] Contents -
Chassis: type 12012 Fab Ver: 1
Chassis S/N: ZQ24CS3WT86MGVHL
PCA: 800-3015-1 rev: A0 dev: 257 HW ver: 1.0
Backplane S/N: A109EXPR75FUNYJK
MAC Addr: base 0000.EAB2.34FF block size: 1024
RMA Number: 0x5F-0x2D-0x44 code: 0x01 hist: 0x1A
show gt64010 (7200)
To display all GT64010 internal registers and interrupt status on the Cisco 7200 series routers, use the showgt64010 command in EXEC mode.
showgt64010
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
Modification
11.2
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command displays information about the CPU interface, DRAM/device address space, device parameters, direct memory access (DMA) channels, timers and counters, and protocol control information (PCI) internal registers. The information is generally useful for diagnostic tasks performed by technical support only.
Examples
The following is a partial sample output for the showgt64010 command:
To display the hardware-specific information for a router, use theshowhardwarecommand in user EXEC or privileged EXEC mode.
showhardware
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
Modification
12.4(22)T
This command was introduced.
Usage Guidelines
Use the showhardware command to display the hardware specific information for a router.
Examples
The following is sample output from the showhardware command:
Router# show hardware
Cisco IOS Software, 7200 Software (C7200-ADVENTERPRISEK9-M), Version 12.4(22)T,)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Fri 10-Oct-08 10:10 by prod_rel_team
ROM: System Bootstrap, Version 12.2(4r)B2, RELEASE SOFTWARE (fc2)
BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.3(16), RELEASE SOFTWARE (fc4)
Router uptime is 1 day, 16 hours, 32 minutes
System returned to ROM by reload at 04:13:23 UTC Wed Aug 12 2009
System image file is "disk0:Default-IOS-Image-Do-Not-Delete"
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Cisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of memo.
Processor board ID 31410931
R7000 CPU at 350MHz, Implementation 39, Rev 3.3, 256KB L2 Cache
6 slot VXR midplane, Version 2.7
Last reset from power-on
PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb0_mb1 has a total of 600 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 180 bandwidth points
This configuration is within the PCI bus capacity and is supported.
Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.
2 FastEthernet interfaces
4 Serial interfaces
125K bytes of NVRAM.
62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
125440K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2002
Related Commands
Command
Description
showinterfaces
Displays statistics for all interfaces configured on the router or access server.
show health-monitor
To display the system Health Monitor status information, use the showhealth-monitorcommand in user EXEC or privileged EXEC mode.
showhealth-monitor [summary]
Syntax Description
summary
(Optional) Displays a summary of the status information.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)M
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M.
Usage Guidelines
Use this command to display the state of the hardware and software subsystem. Health Monitor is a Cisco IOS subsystem that monitors the state of the individual hardware and software subsystems. This monitoring helps in early detection and recovery of faults in the subsystem.
Examples
The following is sample output from showhealth-monitorcommand. The fields are self explanatory.
Router# show health-monitor summary
Chassis:
Power Supply Failure
Temperature OK
Fans OK
Memory:
Free Memory processor OK
Memory Fragmentation Processor OK
Free Memory I/O OK
Memory Fragmentation I/O OK
DFC's:
Slot 1 - Empty DFC Not in operation
Slot 2 - Empty DFC Not in operation
Slot 3 - AS5X-FC OK
Slot 4 - Empty DFC Not in operation
Slot 5 - Empty DFC Not in operation
Slot 6 - Empty DFC Not in operation
Slot 7 - Empty DFC Not in operation
show history
To list the commands you have entered in the current EXEC session,
use the
showhistorycommand in EXEC mode.
showhistory
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
Modification
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release
12.2(33)SRA.
Usage Guidelines
The command history feature provides a record of EXEC commands you
have entered. The number of commands that the history buffer will record is
determined by the
historysize line configuration command or the
terminalhistorysizeEXEC command.
The table below lists the keys and functions you can use to recall
commands from the command history buffer.
Recalls commands in the history buffer in a backward
sequence, beginning with the most recent command. Repeat the key sequence to
recall successively older commands.
Ctrl-N or Down Arrow1
Returns to more recent commands in the history buffer after
recalling commands with Ctrl-P or the Up Arrow. Repeat the key sequence to
recall successively more recent commands.
1 The arrow keys function only with
ANSI-compatible terminals.
Examples
The following is sample output from the
showhistory command, which lists the commands the user
has entered in EXEC mode for this session:
Router# show history
help
where
show hosts
show history
Router#
Related Commands
Command
Description
historysize
Enables the command history function, or changes the
command history buffer size for a particular line.
terminalhistorysize
Enables the command history feature for the current
terminal session, or changes the size of the command history buffer for the
current terminal session.
show history all
To display command history and reload information of a router, use theshowhistoryallcommand in user EXEC or privileged EXEC mode.
showhistoryall
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
Modification
12.4(22)T
This command was introduced.
Usage Guidelines
Use the showhistoryallcommand to display command history and reload information of a router.
Examples
The following is sample output from the showhistoryallcommand:
Router# show history all
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Cisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of memo.
Processor board ID 31410931
R7000 CPU at 350MHz, Implementation 39, Rev 3.3, 256KB L2, 4096KB L3 Cache
6 slot VXR midplane, Version 2.7
Last reset from power-on
PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb0_mb1 has a total of 600 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 180 bandwidth points
This configuration is within the PCI bus capacity and is supported.
Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.
2 FastEthernet interfaces
4 Serial interfaces
125K bytes of NVRAM.
Installed image archive
*Aug 12 04:17:08.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Nullp
*Aug 12 04:17:08.419: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state p
*Aug 12 04:17:08.419: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state p
*Aug 12 04:17:08.419: %LINK-3-UPDOWN: Interface Serial2/0, changed state to down
*Aug 12 04:17:08.419: %LINK-3-UPDOWN: Interface Serial2/1, changed state to down
*Aug 12 04:17:08.419: %LINK-3-UPDOWN: Interface Serial3/0, changed state to up
*Aug 12 04:17:08.419: %LINK-3-UPDOWN: Interface Serial3/1, changed state to up
*Aug 12 04:17:08.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface SSLVPN-VIp
62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
125440K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
*Aug 12 04:17:09.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEtherp
*Aug 12 04:17:09.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEtherp
*Aug 12 04:17:09.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0n
*Aug 12 04:17:09.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/1n
*Aug 12 04:17:09.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0p
*Aug 12 04:17:09.419: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1p
*Aug 12 04:17:12.411: %LINK-3-UPDOWN: Interface Serial3/0, changed state to down
*Aug 12 04:17:12.411: %LINK-3-UPDOWN: Interface Serial3/1, changed state to down
*Aug 12 04:17:13.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0n
*Aug 12 04:17:13.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1n
--- System Configuration Dialog ---
Would you like to enter the initial configuration dialog? [yes/no]:
% Please answer 'yes' or 'no'.
Would you like to enter the initial configuration dialog? [yes/no]: no
Would you like to terminate autoinstall? [yes]: yes
CMD: 'access-list 199 permit icmp host 10.10.10.10 host 20.20.20.20' 04:18:15 U9
CMD: 'crypto map NiStTeSt1 10 ipsec-manual' 04:18:15 UTC Wed Aug 12 2009
CMD: 'match address 199
' 04:18:15 UTC Wed Aug 12 2009
CMD: 'set peer 20.20.20.20
' 04:18:15 UTC Wed Aug 12 2009
CMD: 'exit' 04:18:15 UTC Wed Aug 12 2009
CMD: 'no access-list 199' 04:18:15 UTC Wed Aug 12 2009
CMD: 'no crypto map NiStTeSt1' 04:18:15 UTC Wed Aug 12 2009
*Aug 12 04:18:15.403: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 7200 Software (C7200-ADVENTERPRISEK9-M), Version 12.4(22)T,)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Fri 10-Oct-08 10:10 by prod_rel_team
*Aug 12 04:18:15.415: %ENTITY_ALARM-6-INFO: ASSERT INFO Fa0/0 Physical Port Adm
*Aug 12 04:18:15.415: %ENTITY_ALARM-6-INFO: ASSERT INFO Fa0/1 Physical Port Adm
*Aug 12 04:18:15.499: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 12 04:18:15.499: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Aug 12 04:18:15.599: %ENTITY_ALARM-6-INFO: ASSERT INFO Se2/0 Physical Port Adm
*Aug 12 04:18:15.599: %ENTITY_ALARM-6-INFO: ASSERT INFO Se2/1 Physical Port Adm
*Aug 12 04:18:15.599: %ENTITY_ALARM-6-INFO: ASSERT INFO Se3/0 Physical Port Adm
*Aug 12 04:18:15.599: %ENTITY_ALARM-6-INFO: ASSERT INFO Se3/1 Physical Port Adm
*Aug 12 04:18:15.599: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoint
*Aug 12 04:18:15.823: %SYS-6-BOOTTIME: Time taken to reboot after reload = 314s
*Aug 12 04:18:16.715: %LINK-5-CHANGED: Interface Serial2/0, changed state to adn
*Aug 12 04:18:16.719: %LINK-5-CHANGED: Interface FastEthernet0/0, changed staten
*Aug 12 04:18:16.723: %LINK-5-CHANGED: Interface FastEthernet0/1, changed staten
*Aug 12 04:18:16.727: %LINK-5-CHANGED: Interface Serial2/1, changed state to adn
*Aug 12 04:18:16.727: %LINK-5-CHANGED: Interface Serial3/0, changed state to adn
*Aug 12 04:18:16.727: %LINK-5-CHANGED: Interface Serial3/1, changed state to adn
*Aug 12 04:18:17.719: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
*Aug 12 04:18:17.723: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEther9
CMD: 'conf t' 04:18:30 UTC Wed Aug 12 2009
CMD: 'hostname 7206-3' 04:19:02 UTC Wed Aug 12 2009
CMD: 'ip host sjc-tftp02 171.69.17.17' 04:19:02 UTC Wed Aug 12 2009
CMD: 'ip host sjc-tftp01 171.69.17.19' 04:19:03 UTC Wed Aug 12 2009
CMD: 'ip host dirt 171.69.1.129' 04:19:03 UTC Wed Aug 12 2009
CMD: 'interface FastEthernet0/0' 04:19:03 UTC Wed Aug 12 2009
CMD: 'no ip proxy-arp' 04:19:03 UTC Wed Aug 12 2009
CMD: 'ip address 10.4.9.80 255.255.255.0' 04:19:03 UTC Wed Aug 12 2009
CMD: 'no shutdown' 04:19:04 UTC Wed Aug 12 2009
CMD: 'exit' 04:19:04 UTC Wed Aug 12 2009
CMD: 'ip classless' 04:19:05 UTC Wed Aug 12 2009
*Aug 12 04:19:06.123: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state p
*Aug 12 04:19:06.123: %ENTITY_ALARM-6-INFO: CLEAR INFO Fa0/0 Physical Port Admi9
CMD: 'ip default-network 0.0.0.0' 04:19:06 UTC Wed Aug 12 2009
CMD: 'ip default-gateway 10.4.9.1' 04:19:06 UTC Wed Aug 12 2009
CMD: 'config-register 0x2002' 04:19:07 UTC Wed Aug 12 2009
Related Commands
Command
Description
showhistory
Displays commands entered in the current EXEC session.
show hosts
To display the default domain name, the style of name lookup service, a list of name server hosts, and the cached list of hostnames and addresses specific to a particular Domain Name System (DNS) view or for all configured DNS views, use the
showhosts command in privileged EXEC mode.
(Optional) The
vrf-name argument specifies the name of the Virtual Private Network (VPN) routing and forwarding (VRF) instance associated with the DNS view whose hostname cache entries are to be displayed. Default is the global VRF (that is, the VRF whose name is a NULL string) with the specified or default DNS view.
Note
More than one DNS view can be associated with a VRF. To uniquely identify a DNS view, specify both the view name and the VRF with which it is associated.
viewview-name
(Optional) The
view-name argument specifies the DNS view whose hostname cache information is to be displayed. Default is the default (unnamed) DNS view associated with the specified or global VRF.
Note
More than one DNS view can be associated with a VRF. To uniquely identify a DNS view, specify both the view name and the VRF with which it is associated.
default
(Optional) Displays the default view.
all
(Optional) Display all the host tables.
hostname
(Optional) The specified hostname cache information displayed is to be limited to entries for a particular hostname. Default is the hostname cache information for all hostname entries in the cache.
summary
(Optional) The specified hostname cache information is to be displayed in brief summary format. Disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
10.0
This command was introduced.
12.2T
Support was added for Cisco modem user interface feature.
12.4(4)T
The
vrf,
all, and
summary keywords and
vrf-name and
hostname arguments were added.
12.4(9)T
The
view keyword and
view-name argument were added.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
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.
Usage Guidelines
This command displays the default domain name, the style of name lookup service, a list of name server hosts, and the cached list of hostnames and addresses specific to a particular DNS view or for all configured DNS views.
If you specify the
showhosts command without any optional keywords or arguments, only the entries in the global hostname cache will be displayed.
If the output from this command extends beyond the bottom of the screen, press the Space bar to continue or press the Q key to terminate command output.
Examples
The following is sample output from the
showhosts command with no parameters specified:
Router# show hosts
Default domain is CISCO.COM
Name/address lookup uses domain service
Name servers are 192.0.2.220
Host Flag Age Type Address(es)
EXAMPLE1.CISCO.COM (temp, OK) 1 IP 192.0.2.10
EXAMPLE2.CISCO.COM (temp, OK) 8 IP 192.0.2.50
EXAMPLE3.CISCO.COM (temp, OK) 8 IP 192.0.2.115
EXAMPLE4.CISCO.COM (temp, EX) 8 IP 192.0.2.111
EXAMPLE5.CISCO.COM (temp, EX) 0 IP 192.0.2.27
EXAMPLE6.CISCO.COM (temp, EX) 24 IP 192.0.2.30
The following is sample output from the
showhosts command that specifies the VRF vpn101:
Router# show hosts vrf vpn101
Default domain is example.com
Domain list: example1.com, example2.com, example3.com
Name/address lookup uses domain service
Name servers are 192.0.2.204, 192.0.2.205, 192.0.2.206
Codes: UN - unknown, EX - expired, OK - OK, ?? - revalidate
temp - temporary, perm - permanent
NA - Not Applicable None - Not defined
Host Port Flags Age Type Address(es)
user None (perm, OK) 0 IP 192.0.2.001
www.example.com None (perm, OK) 0 IP 192.0.2.111
192.0.2.112
The table below describes the significant fields shown in the display.
Table 2 show hosts Field Descriptions
Field
Description
Default domain
Default domain name to be used to complete unqualified names if no domain list is defined.
Domain list
List of default domain names to be tried in turn to complete unqualified names.
Name/address lookup
Style of name lookup service.
Name servers
List of name server hosts.
Host
Learned or statically defined hostname. Statically defined hostname-to-address mappings can be added to the DNS hostname cache for a DNS view by using the
iphosts command.
Port
TCP port number to connect to when using the defined hostname in conjunction with an EXEC connect or Telnet command.
Flags
Indicates additional information about the hostname-to-IP address mapping. Possible values are as follows:
EX--Entries marked EX are expired.
OK--Entries marked OK are believed to be valid.
perm--A permanent entry is entered by a configuration command and is not timed out.
temp--A temporary entry is entered by a name server; the Cisco IOS software removes the entry after 72 hours of inactivity.
??--Entries marked ?? are considered suspect and subject to revalidation.
Age
Number of hours since the software last referred to the cache entry.
Type
Type of address. For example, IP, Connectionless Network Service (CLNS), or X.121.
If you have used the
iphp-hostglobal configuration command, the
showhosts command will display these hostnames as type HP-IP.
Address(es)
IP address of the host. One host may have up to eight addresses.
Related Commands
Command
Description
clearhost
Removes static hostname-to-address mappings from the hostname cache for the specified DNS view or all DNS views.
iphost
Defines static hostname-to-address mappings in the DNS hostname cache for a DNS view.
show html
To display module and port information, use the showhtml command in privileged EXEC mode.
The following is sample output from the showhtml command using theport,all,andoptionskeywords. The ouput is self-explanatory.
Router# show html port all options
<option>FastEthernet0/0
<option>FastEthernet0/1
<option>Serial2/0
<option>Serial2/1
<option>Serial3/0
<option>Serial3/0.1
<option>Serial3/1
<option>Tunnel0
<option>Tunnel1
<option>Tunnel2
<option>Tunnel3
<option>Virtual-Access1
<option>Virtual-Template1
<option>VoIP-Null0
<option>vmi1
<option>vmi2
show idb
To display information about the status of interface descriptor blocks (IDBs), use the
showidbcommand in privileged EXEC mode.
showidb
Syntax Description
This command has nor arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1
This command was introduced.
12.2(15)T
The output of this command was changed to show additional information.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following is sample output from the
showidb command:
Router# show idb
Maximum number of Software IDBs 8192. In use 17.
HWIDBs SWIDBs
Active 5 14
Inactive 10 3
Total IDBs 15 17
Size each (bytes) 5784 2576
Total bytes 86760 43792
HWIDB#1 1 2 GigabitEthernet0/0 0 5, HW IFINDEX, Ether)
HWIDB#2 2 3 GigabitEthernet9/0 0 5, HW IFINDEX, Ether)
HWIDB#3 3 4 GigabitEthernet9/1 6 5, HW IFINDEX, Ether)
HWIDB#4 4 5 GigabitEthernet9/2 6 5, HW IFINDEX, Ether)
HWIDB#5 13 1 Ethernet0 4 5, HW IFINDEX, Ether)
The table below describes the significant fields shown in the display.
Table 3 show idb Field Descriptions
Field
Description
In use
Total number of software IDBs (SWIDBs) that have been allocated. This number never decreases. SWIDBs are never deallocated.
Active
Total number of hardware IDBs (HWIDBs) and SWIDBs that are allocated and in use.
Inactive
Total number of HWIDBs and SWIDBs that are allocated but not in use.
Total
Total number of HWIDBs and SWIDBs that are allocated.
show idprom
To display the identification programmable read-only memory (IDPROM) information for field-replaceable units (FRUs), use the
showidprom command in privileged EXEC mode.
showidprom
{ all | frutype }
[detail]
Syntax Description
all
Displays the information for all FRU types.
frutype
Type of FRU for information to be displayed; see the “Usage Guidelines” section for valid values.
detail
(Optional) Displays the detailed display of IDPROM data (verbose).
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(14)SX
This command was introduced on the Supervisor Engine 720.
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was integrated into Release 12.2(17d)SXB.
12.2(18)SXE
The
module keyword was modified to support slot/subslot addressing for shared port adapters (SPAs) and SPA interface processors (SIPs), and the optional
clei keyword was added. The
interface keyword was replaced by the
transceiver keyword.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Valid entries for
frutype are as follows:
backplane
clocknumber--1 and 2.
earlslot--See the following paragraph for valid slot values.
moduleslot/port|slot|slot/subslot[clei] }--See the following paragraphs for valid values and descriptions.
rpslot--See the following paragraph for valid slot values.
power-supply--1 and 2.
supervisorslot--See the following paragraph for valid slot values.
The
moduleslot/port argument designates the module slot location and port number.
Valid values for
slot depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48.
The
module {slot |
slot/subslot [clei]} syntax designates either the
slotlocation alone of theSIP in the chassis (to show information for the SIP only), or the
slotlocation of theSIP and the
subslot location of a SPA installed within the SIP (to display information for a SPA only). Valid values for
slot depend on the chassis model (2-13), and valid values for
subslot depend on the SIP type (such as 0-3 for a Cisco 7600 SIP-200 and Cisco 7600 SIP-400). The optional
clei keyword specifies display of the Common Language Equipment Identification ( CLEI) information for the specified SIP or SPA.
Use the
showidprombackplane command to display the chassis serial number.
Use the
transceiverslot/subslot/port form of the command to display information for transceivers installed in a SPA, where
slot designates the location of the SIP,
subslot designates the location of the SPA, and
port designates the interface number.
The
interfaceinterfaceslot keyword and arguments supported on GBIC security-enabled interfaces have been replaced by the
transceiver keyword option.
To specify LAN Gigabit Ethernet interfaces, use the
showidpromtransceiverslot/subslotGigabitEthernet form of the command.
To specify WAN Gigabit Ethernet interfaces, use the
showidpromtransceiverslot/subslotGigabitEthernetWAN form of the command.
Examples
This example shows how to display IDPROM information for clock 1:
Router#
show idprom clock 1
IDPROM for clock #1
(FRU is 'Clock FRU')
OEM String = 'Cisco Systems'
Product Number = 'WS-C6000-CL'
Serial Number = 'SMT03073115'
Manufacturing Assembly Number = '73-3047-04'
Manufacturing Assembly Revision = 'A0'
Hardware Revision = 1.0
Current supplied (+) or consumed (-) = 0.000A
The following table describes the significant fields shown in the display.
Table 4 show idprom Field Descriptions
Field
Description
FRU is
Indicates the type of the field-replacement unit (FRU) to which the information that follows applies.
OEM String
Names the original equipment manufacturer (OEM).
Product Number
A number that identifies a product line.
Serial Number
A number that uniquely identifies the product itself.
Manufacturing Assembly Number
A number that identifies the hardware identification number.
Manufacturing Assembly Revision
A number that identifies the manufacturing assembly number.
Hardware Revision
A number that represents the hardware upgrade.
Current supplied (+) or consumed (-)
Indicated the amount of electrical current that the device supples or uses.
This example shows how to display IDPROM information for power supply 1:
Router#
show idprom power-supply 1
IDPROM for power-supply #1
(FRU is '110/220v AC power supply, 1360 watt')
OEM String = 'Cisco Systems, Inc.'
Product Number = 'WS-CAC-1300W'
Serial Number = 'ACP03020001'
Manufacturing Assembly Number = '34-0918-01'
Manufacturing Assembly Revision = 'A0'
Hardware Revision = 1.0
Current supplied (+) or consumed (-) = 27.460A
This example shows how to display detailed IDPROM information for power supply 1:
Router#
show idprom power-supply 1 detail
IDPROM for power-supply #1
IDPROM image:
(FRU is '110/220v AC power supply, 1360 watt')
IDPROM image block #0:
hexadecimal contents of block:
00: AB AB 01 90 11 BE 01 00 00 02 AB 01 00 01 43 69 ..............Ci
10: 73 63 6F 20 53 79 73 74 65 6D 73 2C 20 49 6E 63 sco Systems, Inc
20: 2E 00 57 53 2D 43 41 43 2D 31 33 30 30 57 00 00 ..WS-CAC-1300W..
30: 00 00 00 00 00 00 41 43 50 30 33 30 32 30 30 30 ......ACP0302000
40: 31 00 00 00 00 00 00 00 00 00 33 34 2D 30 39 31 1.........34-091
50: 38 2D 30 31 00 00 00 00 00 00 41 30 00 00 00 00 8-01......A0....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 01 00 00 00 00 00 00 00 09 00 0C 00 03 ................
80: 00 01 00 06 00 01 00 00 00 00 0A BA 00 00 00 00 ................
block-signature = 0xABAB, block-version = 1,
block-length = 144, block-checksum = 4542
*** common-block ***
IDPROM capacity (bytes) = 256 IDPROM block-count = 2
FRU type = (0xAB01,1)
OEM String = 'Cisco Systems, Inc.'
Product Number = 'WS-CAC-1300W'
Serial Number = 'ACP03020001'
Manufacturing Assembly Number = '34-0918-01'
Manufacturing Assembly Revision = 'A0'
Hardware Revision = 1.0
Manufacturing bits = 0x0 Engineering bits = 0x0
SNMP OID = 9.12.3.1.6.1.0
Power Consumption = 2746 centiamperes RMA failure code = 0-0-0-0
*** end of common block ***
IDPROM image block #1:
hexadecimal contents of block:
00: AB 01 01 14 02 5F 00 00 00 00 00 00 00 00 0A BA ....._..........
10: 0A BA 00 16 ....
block-signature = 0xAB01, block-version = 1,
block-length = 20, block-checksum = 607
*** power supply block ***
feature-bits: 00000000 00000000
rated current at 110v: 2746 rated current at 220v: 2746 (centiamperes)
CISCO-STACK-MIB SNMP OID = 22 *** end of power supply block ***
End of IDPROM image
This example shows how to display IDPROM information for the backplane:
Router#
show idprom backplane
IDPROM for backplane #0
(FRU is 'Catalyst 6000 9-slot backplane')
OEM String = 'Cisco Systems'
Product Number = 'WS-C6009'
Serial Number = 'SCA030900JA'
Manufacturing Assembly Number = '73-3046-04'
Manufacturing Assembly Revision = 'A0'
Hardware Revision = 1.0
Current supplied (+) or consumed (-) = 0.000A
The following example shows sample output for a Cisco 7600 SIP-400 installed in slot 3 of the router:
Router# show idprom module 3
IDPROM for module #3
(FRU is '4-subslot SPA Interface Processor-400')
OEM String = 'Cisco Systems'
Product Number = '7600-SIP-400'
Serial Number = 'JAB0851042X'
Manufacturing Assembly Number = '73-8404-10'
Manufacturing Assembly Revision = '09'
Hardware Revision = 0.95
Current supplied (+) or consumed (-) = -6.31A
The following example shows sample output for the
clei form of the command on a Cisco 7600 SIP-200 installed in slot 2 of the router:
Router# show idprom module 2 clei
FRU PID VID SN CLEI
--------------- -------------------- --- ----------- ----------
module #2 7600-SIP-200 V01
The following example shows sample output for the
detail form of the command on a Cisco 7600 SIP-400 installed in slot 3 of the router:
The following example shows sample output for a 4-Port OC-3c/STM-1 ATM SPA installed in subslot 0 of the SIP installed in slot 5 of the router:
Router# show idprom module 5/0
IDPROM for SPA module #5/0
(FRU is '4-port OC3/STM1 ATM Shared Port Adapter')
Product Identifier (PID) : SPA-4XOC3-ATM
Version Identifier (VID) : V01
PCB Serial Number : PRTA2604138
Top Assy. Part Number : 68-2177-01
73/68 Board Revision : 05
73/68 Board Revision : 01
Hardware Revision : 0.224
CLEI Code : UNASSIGNED
The following example shows sample output for the
clei form of the command for a 4-Port OC-3c/STM-1 POS SPA installed in subslot 3 of the SIP installed in slot 2 of the router:
Router# show idprom module 2/3 clei
FRU PID VID SN CLEI
--------------- -------------------- --- ----------- ----------
SPA module #2/3 SPA-4XOC3-POS V01 PRTA0304155 UNASSIGNED
The following example shows sample output for the
detail form of the command for a 4-Port OC-3c/STM-1 POS SPA installed in subslot 3 of the SIP installed in slot 2 of the router:
Router# show idprom module 2/3 detail
IDPROM for SPA module #2/3
(FRU is '4-port OC3/STM1 POS Shared Port Adapter')
EEPROM version : 4
Compatible Type : 0xFF
Controller Type : 1088
Hardware Revision : 0.230
Boot Timeout : 0 msecs
PCB Serial Number : PRTA0304155
Part Number : 73-9313-02
73/68 Board Revision : 04
Fab Version : 02
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Deviation Number : 0
Product Identifier (PID) : SPA-4XOC3-POS
Version Identifier (VID) : V01
Top Assy. Part Number : 68-2169-01
73/68 Board Revision : 10
System Clock Frequency : 00 00 00 00 00 00 00 00
00 00 00 00 00
CLEI Code : UNASSIGNED
Base MAC Address : 00 00 00 00 00 00
MAC Address block size : 0
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data : 00 00 00 00 00 00 00 00
Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmV
Calibration values :
Power Consumption : 16200 mWatts (Maximum)
Environment Monitor Data : 01 08 F6 48 43 34 F6 48
43 34 02 31 0C E4 46 32
28 13 07 09 C4 46 32 28
13 07 00 00 00 00 00 00
00 05 DC 46 32 28 13 07
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 FE 02 00
00
Asset ID :
Asset Alias :
show inventory
To display the product inventory listing of all Cisco products installed in the networking device, use the
showinventory command in user EXEC or privileged EXEC mode.
showinventory [raw] [entity]
Syntax Description
raw
(Optional) Retrieves information about all of the Cisco products--referred to as entities--installed in the Cisco networking device, even if the entities do not have a product ID (PID) value, a unique device identifier (UDI), or other physical identification.
entity
(Optional) Name of a Cisco entity (for example, chassis, backplane, module, or slot). A quoted string may be used to display very specific UDI information; for example “sfslot 1” will display the UDI information for slot 1 of an entity named sfslot.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.3(4)T
This command was introduced.
12.0(27)S
This command was integrated into Cisco IOS Release 12.0(27)S.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
12.2(18)SXE5
This command was integrated into Cisco IOS Release 12.2(18)SXE5.
Cisco IOS XE Release 3.9S
This command was integrated into Cisco IOS XE Release 3.9S.
Usage Guidelines
The
showinventory command retrieves and displays inventory information about each Cisco product in the form of a UDI. The UDI is a combination of three separate data elements: a product identifier (PID), a version identifier (VID), and the serial number (SN).
The PID is the name by which the product can be ordered; it has been historically called the “Product Name” or “Part Number.” This is the identifier that one would use to order an exact replacement part.
The VID is the version of the product. Whenever a product has been revised, the VID will be incremented. The VID is incremented according to a rigorous process derived from Telcordia GR-209-CORE, an industry guideline that governs product change notices.
The SN is the vendor-unique serialization of the product. Each manufactured product will carry a unique serial number assigned at the factory, which cannot be changed in the field. This is the means by which to identify an individual, specific instance of a product.
The UDI refers to each product as an entity. Some entities, such as a chassis, will have subentities like slots. Each entity will display on a separate line in a logically ordered presentation that is arranged hierarchically by Cisco entities.
Use the
showinventory command without options to display a list of Cisco entities installed in the networking device that are assigned a PID.
Examples
The following is sample output from the
showinventorycommand without any keywords or arguments. This sample output displays a list of Cisco entities installed in a router that are assigned a PID.
The table below describes the fields shown in the display.
Table 5 show inventory Field Descriptions
Field
Description
NAME
Physical name (text string) assigned to the Cisco entity. For example, console or a simple component number (port or module number), such as “1,” depending on the physical component naming syntax of the device.
DESCR
Physical description of the Cisco entity that characterizes the object. The physical description includes the hardware serial number and the hardware revision.
PID
Entity product identifier. Equivalent to the entPhysicalModelName MIB variable in RFC 2737.
VID
Entity version identifier. Equivalent to the entPhysicalHardwareRev MIB variable in RFC 2737.
SN
Entity serial number. Equivalent to the entPhysicalSerialNum MIB variable in RFC 2737.
For diagnostic purposes, theshowinventorycommand can be used with the
raw keyword to display every RFC 2737 entity including those without a PID, UDI, or other physical identification.
Note
The
raw keyword option is primarily intended for troubleshooting problems with the
showinventory command itself.
Enter theshowinventorycommand with an
entity argument value to display the UDI information for a specific type of Cisco entity installed in the networking device. In this example, a list of Cisco entities that match the sfslot argument string is displayed.
You can request even more specific UDI information using theshowinventorycommand with an
entity argument value that is enclosed in quotation marks. In this example, only the details for the entity that exactly matches the sfslot 1 argument string are displayed.
Cisco 4400 Series Integrated Services Router (ISR)
The following sample output from the showinventory displays a list of Cisco entities installed on a Cisco 4400 Series ISR with their names (NAME), descriptions (DESCR), PIDs, and serial numbers (SN) The sample output also displays the slots assgined to each entity.
Specifies the civic, custom, and geo-spatial host location information.
identifierid
Specifies the information identifier of the civic location, custom location, and geo-spatial location.
interfacetypenumber
Specifies the interface type and interface number.
static
Specifies the configured location information.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
Modification
12.2(40)SE
This command was introduced.
12.2(55)SE
This command was modified. The output was enhanced to display location information obtained from Cisco Discovery Protocol.
15.1(1)SG
This command was modified. The
custom-location and
geo-location keywords were added.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
Examples
The following sample output from the
showlocationcivic-location command displays all the civic location information for a specific identifier:
Device# show location civic-location identifier test
Civic location information
--------------------------
Identifier : test
Building : 24
City : Milpitas
State : California
Ports : Gi1/0/10
The following sample output from theshowlocationcustom-location command displays custom location information of a host device:
Device# show location custom-location identifier
Custom location information
---------------------------
Identifier: host
Name : bgl15
Value : IDF2.5
The following sample output from the show location geo-location
command displays geo-spatial location information of a device:
Device# show location geo-location identifier apjtpk
Geo location information
------------------------
Identifier : apjtpk
Latitude : 54.45
Longitude : 37.43
Altitude : 5 floor
Resolution : 54.45
The following sample output from the show location host
command displays all host information of a device:
Device# show location host
Civic location information
--------------------------
Identifier : host
County : raps
City Division : SJ
Neighborhood : lake
Street Group : G2
Leading street direction: trav
Trailing street suffix : C76
Street number : 18
Street number suffix : 54
Landmark : park
Name : KMD
Building : bgl13
Unit : apjtpk
Floor : 3
Room : Andaman
Type of place : office
Postal community name : ios
Post office box : 12
Additional code : apjtpk
Seat : B5-10
Primary road name : outerringrd
Road section : east
Branch road name : venus
Sub branch road name : Tata
Street name postmodifier: ret
City : Boston
State : CA
Postal code : 1345
Additional location : cauveri
Custom location information
---------------------------
Identifier: host
Name : bgl15
Value : IDF2.5
Geo location information
------------------------
Identifier : host
Latitude : 12.34
Longitude : 56.78
The following table describes the significant fields shown in the display.
Table 6 show location Field Descriptions
Field
Description
Identifier
Information identifier of the civic location, custom location, and geo-spatial location.
Name
Name of the configured custom location identifier.
Value
Configured value of the custom location identifier.
Latitude
Configured latitude information of the device.
Longitude
Configured longitude information of the device.
Altitude
Configured altitude information of the device.
Resolution
Configured resolution for the latitude and longitude.
Related Commands
Command
Description
locationcivic-locationidentifier
Configures the civic location information of a device.
locationcustom-locationidentifier
Configures the custom location information of a device.
locationgeo-locationidentifier
Configures the geo-spatial location of a device such as latitude, longitude, altitude, and resolution.
show logging
To display the state of system logging (syslog) and the contents of the standard system logging buffer, use the
showlogging command in privileged EXEC mode.
showlogging
[ slotslot-number | summary ]
Syntax Description
slotslot-number
(Optional) Displays information in the syslog history table for a specific line card. Slot numbers range from 0 to 11 for the Cisco 12012 Internet router and from 0 to 7 for the Cisco 12008 Internet router.
summary
(Optional) Displays counts of messages by type for each line card.
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
This command was introduced.
11.2 GS
The
slot and
summary keywords were added for the Cisco 12000.
12.2(8)T
Command output was expanded to show the status of the logging count facility (“Count and time-stamp logging messages”).
12.2(15)T
Command output was expanded to show the status of XML syslog formatting.
12.3(2)T
Command output was expanded (on supported software images) to show details about the status of system logging processed through the Embedded Syslog Manager (ESM). These lines appear as references to “filtering” or “filter modules”.
12.3(2)XE
This command was integrated into Cisco IOS Release 12.3(2)XE.
12.2(14)SX
This command was integrated into Cisco IOS Release 12.2(14)SX.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(11)T
The CLI output was modified to show message discriminators defined at the router and syslog sessions associated with those message discriminators.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and which logging destinations (console, monitor, buffer, or host) logging is enabled. This command also displays Simple Network Management Protocol (SNMP) logging configuration parameters and protocol activity.
This command will display the contents of the standard system logging buffer, if logging to the buffer is enabled. Logging to the buffer is enabled or disabled using the [no]
loggingbuffered command. The number of system error and debugging messages in the system logging buffer is determined by the configured size of the syslog buffer. This size of the syslog buffer is also set using the
loggingbuffered command.
To enable and set the format for syslog message time stamping, use the
servicetimestampslog command.
If debugging is enabled (using any
debug command), and the logging buffer is configured to include level 7 (debugging) messages, debug output will be included in the system log. Debugging output is not formatted like system error messages and will not be preceded by the percent symbol (%).
Examples
The following is sample output from the
showlogging command on a software image that supports the Embedded Syslog Manager (ESM) feature:
The following example shows output from the
showlogging command after a message discriminator has been configured. Included in this example is the command to configure the message discriminator.
c7200-3(config)# logging discriminator ATTFLTR1 severity includes 1,2,5 rate-limit 100
Specified MD by the name ATTFLTR1 is not found.
Adding new MD instance with specified MD attribute values.
Router(config)# end
Router#
000036: *Oct 20 16:26:04.570: %SYS-5-CONFIG_I: Configured from console by console
Router# show logging
Syslog logging: enabled (11 messages dropped, 0 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
Inactive Message Discriminator:
ATTFLTR1 severity group includes 1,2,5
rate-limit not to exceed 100 messages per second
Console logging: level debugging, 25 messages logged, xml disabled, filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled
Buffer logging: level debugging, 25 messages logged, xml disabled, filtering disabled
Logging Exception size (8192 bytes)
Count and timestamp logging messages: disabled
No active filter modules.
Trap logging: level debugging, 28 message lines logged
Logging to 172.25.126.15 (udp port 1300, audit disabled, authentication disabled, encryption disabled, link up),
28 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 172.25.126.15 (tcp port 1307, audit disabled, authentication disabled, encryption disabled, link up),
28 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled, filtering disabled
Logging to 172.20.1.1 (udp port 514, audit disabled,
authentication disabled, encryption disabled, link up),
28 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Log Buffer (1000000 bytes):
The table below describes the significant fields shown in the output for the two preceding examples.
Table 7 show logging Field Descriptions
Field
Description
Syslog logging:
Shows the general state of system logging (enabled or disabled), the status of logged messages (number of messages dropped, rate-limited, or flushed), and whether XML formatting or ESM filtering is enabled.
No Active Message Discriminator
Indicates that a message discriminator is not being used.
Inactive Message Discriminator:
Identifies a configured message discriminator that has not been invoked.
Console logging:
Logging to the console port. Shows “disabled” or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
Corresponds to the configuration of the
loggingconsole,
loggingconsolefiltered, or
loggingconsolexml command.
Monitor logging:
Logging to the monitor (all TTY lines). Shows “disabled” or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
Corresponds to the configuration of the
loggingmonitor,
loggingmonitorfiltered or
loggingmonitorxml command.
Buffer logging:
Logging to the standard syslog buffer. Shows “disabled” or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
Corresponds to the configuration of the
loggingbuffered,
loggingbufferedfiltered, or
loggingbufferedxml command.
Trap logging:
Logging to a remote host (syslog collector). Shows “disabled” or, if enabled, the severity level limit, number of messages logged, and whether XML formatting or ESM filtering is enabled.
(The word “trap” means a trigger in the system software for sending error messages to a remote host.)
Corresponds to the configuration of the
logginghost command. The severity level limit is set using the
loggingtrap command.
SNMP logging
Displays whether SNMP logging is enabled, the number of messages logged, and the retransmission interval. If not shown on your platform, use the
showlogginghistory command.
Logging Exception size (8192 bytes)
Corresponds to the configuration of the
loggingexception command.
Count and timestamp logging messages:
Corresponds to the configuration of the
loggingcount command.
No active filter modules.
Appears if no syslog filter modules are configured with the
loggingfilter command.
Syslog filter modules are Tcl script files used when the Embedded Syslog Manager (ESM) is enabled. ESM is enabled when any of the
filtered keywords are used in the logging commands.
If configured, the URL and filename of configured syslog filter modules will appear at this position in the output. Syslog filter modules are executed in the order in which they appear here.
Log Buffer (8192 bytes):
The value in parentheses corresponds to the configuration of the
loggingbufferedbuffer-size command. If no messages are currently in the buffer, the output ends with this line. If messages are stored in the syslog buffer, they appear after this line.
The following example shows that syslog messages from the system buffer are included, with time stamps. In this example, the software image does not support XML formatting or ESM filtering of syslog messages.
Router# show logging
Syslog logging:enabled (2 messages dropped, 0 flushes, 0 overruns)
Console logging:disabled
Monitor logging:level debugging, 0 messages logged
Buffer logging:level debugging, 4104 messages logged
Trap logging:level debugging, 4119 message lines logged
Logging to 192.168.111.14, 4119 message lines logged
Log Buffer (262144 bytes):
Jul 11 12:17:49 EDT:%BGP-4-MAXPFX:No. of prefix received from 209.165.200.225
(afi 0) reaches 24, max 24
! THE FOLLOWING LINE IS A DEBUG MESSAGE FROM NTP.
! NOTE THAT IT IS NOT PRECEEDED BY THE % SYMBOL.
Jul 11 12:17:48 EDT: NTP: Maxslew = 213866
Jul 11 15:15:41 EDT:%SYS-5-CONFIG:Configured from
tftp://host.com/addc5505-rsm.nyiix
.Jul 11 15:30:28 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Up
.Jul 11 15:31:34 EDT:%BGP-3-MAXPFXEXCEED:No. of prefix received from
209.165.200.226 (afi 0):16444 exceed limit 375
.Jul 11 15:31:34 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Down BGP
Notification sent
.Jul 11 15:31:34 EDT:%BGP-3-NOTIFICATION:sent to neighbor 209.165.200.226 3/1
(update malformed) 0 bytes
.
.
.
The software clock keeps an “authoritative” flag that indicates whether the time is authoritative (believed to be accurate). If the software clock has been set by a timing source (for example, via Network Time Protocol (NTP), the flag is set. If the time is not authoritative, it will be used only for display purposes. Until the clock is authoritative and the “authoritative” flag is set, the flag prevents peers from synchronizing to the software clock.
The table below describes the symbols that precede the time stamp.
Table 8 Time-Stamping Symbols for Syslog Messages
Symbol
Description
Example
*
Time is not authoritative: the software clock is not in sync or has never been set.
*15:29:03.158 UTC Tue Feb 25 2003:
(blank)
Time is authoritative: the software clock is in sync or has just been set manually.
15:29:03.158 UTC Tue Feb 25 2003:
.
Time is authoritative, but NTP is not synchronized: the software clock was in sync, but has since lost contact with all configured NTP servers.
.15:29:03.158 UTC Tue Feb 25 2003:
The following is sample output from the
showloggingsummarycommand for a Cisco 12012 router. A number in the column indicates that the syslog contains that many messages for the line card. For example, the line card in slot 9 has 1 error message, 4 warning messages, and 47 notification messages.
Note
For similar log counting on other platforms, use the
showloggingcount command.
The table below describes the logging level fields shown in the display.
Table 9 show logging summary Field Descriptions
Field
Description
SLOT
Indicates the slot number of the line card. An asterisk next to the slot number indicates the GRP card whose error message counts are not displayed. For information on the GRP card, use theshowlogging command.
EMERG
Indicates that the system is unusable.
ALERT
Indicates that immediate action is needed.
CRIT
Indicates a critical condition.
ERROR
Indicates an error condition.
WARNING
Indicates a warning condition.
NOTICE
Indicates a normal but significant condition.
INFO
Indicates an informational message only.
DEBUG
Indicates a debugging message.
Related Commands
Command
Description
clearlogging
Clears messages from the logging buffer.
loggingbuffered
Enables system message logging to a local buffer.
loggingcount
Enables the error log count capability.
logginghistorysize
Changes the number of syslog messages stored in the history table of the router.
logginglinecard
Logs messages to an internal buffer on a line card and limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level.
servicetimestamps
Configures the system to time-stamp debugging or logging messages.
showloggingcount
Displays a summary of system error messages (syslog messages) by facility and severity.
showloggingxml
Displays the state of system logging and the contents of the XML-specific logging buffer.
show logging count
To display a summary of the number of times certain system error messages are occuring, use the
showlogging command in privileged EXEC mode.
showloggingcount
Syntax Description
This command has no arguements or keywords.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(8)T
This command was introduced.
Usage Guidelines
To enable the error log count capability (syslog counting feature), use the
loggingcount command in global configuration mode.
This feature works independently of the various settings of the other logging commands (such as [no]
loggingon, [no]
loggingbuffered, and so on). In other words, turning off logging by other means does not stop the counting and timestamping from occuring.
This command displays information such as the number of times a particular system error message occurs and the time stamp of the last occurrence of the specified message. System error messages are grouped into logical units called “Facilities” based on Cisco IOS software components.
To determine if system error message counting is enabled, use the
showlogging command.
The
servicetimestamps command configuration determines the timestamp format (shown in the “Last Time” column) ofshowloggingcount command output. There is not quite enough space for all options of the possible options (datetime, milliseconds, and timezone) of the
servicetimestampsdatetimecommand to be displayed at the same time. As a result, if
msec is selected,
timezone will not be displayed. If
show-timezone is selected but not
msec, then the time zone will be displayed.
Occasionally, the length of the message name plus the facility name contains too many characters to be printed on one line. The CLI attempts to keep the name and facility name on one line but, if necessary, the line will be wrapped, so that the first line contains the facility name and the second line contains the message name and the rest of the columns.
Examples
The following example shows the number of times syslog messages have occurred and the most recent time that each error message occurred. In this example, the
showlogging command is used to determine if the syslog counting feature is enabled:
Router# show logging | include count
Count and timestamp logging messages: enabled
Router# show logging count
Facility Message Name Sev Occur Last Time
=============================================================================
SYS BOOTTIME 6 1 00:00:12
SYS RESTART 5 1 00:00:11
SYS CONFIG_I 5 1 00:00:05
------------- ------------------------------- -----------------------------
SYS TOTAL 3
LINEPROTO UPDOWN 5 13 00:00:19
------------- ------------------------------- -----------------------------
LINEPROTO TOTAL 13
LINK UPDOWN 3 1 00:00:18
LINK CHANGED 5 12 00:00:09
------------- ------------------------------- -----------------------------
LINK TOTAL 13
SNMP COLDSTART 5 1 00:00:11
------------- ------------------------------- -----------------------------
SNMP TOTAL 1
The table below describes the significant fields shown in the display.
Table 10 show logging count Field Descriptions
Field
Description
Facility
The facility, such as syslog, from which these error messages are occurring.
Message Name
The name of this message.
Sev
The severity level of this message.
Occur
How many times this message has occurred.
Last Time
The last (most recent) time this message occurred. Timestamping is by default based on the system uptime (for example “3w1d” indicates 3 weeks and 1 day from the last system reboot.)
Sys Total / Lineproto Total / Link Total / SNMP Total
Total number of error messages that have occurred for the specified Facility.
In the following example, the user is interested only in the totals:
Router# show logging count | include total
SYS TOTAL 3
LINEPROTO TOTAL 13
LINK TOTAL 13
SNMP TOTAL 1
Related Commands
Command
Description
clearlogging
Clears messages from the logging buffer.
loggingcount
Enables the system error message log count capability.
servicetimestamps
Configures the system to time-stamp debugging or logging messages.
showlogging
Displays general information about the state of system logging.
show logging history
To display information about the state of the syslog history table, use the
showlogginghistory command in privileged EXEC mode.
showlogginghistory
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command displays information about the syslog history table, such as the table size, the status of messages, and text of messages stored in the table. Messages stored in the table are governed by the
logginghistory global configuration command.
Examples
The following example shows sample output from the
showlogginghistorycommand. In this example, notifications of severity level 5 (notifications) through severity level 0 (emergencies) are configured to be written to the logging history table.
Router# show logging history
Syslog History Table: 1 maximum table entries,
saving level notifications or higher
0 messages ignored, 0 dropped, 15 table entries flushed,
SNMP notifications not enabled
entry number 16: SYS-5-CONFIG_I
Configured from console by console
timestamp: 1110
Router#
The table below describes the significant fields shown in the output.
Table 11 show logging history Field Descriptions
Field
Description
maximum table entry
Number of messages that can be stored in the history table. Set with the
logginghistorysize command.
saving level notifications <x> or higher
Level of messages that are stored in the history table and sent to the SNMP server (if SNMP notification is enabled). The severity level can be configured with the
logginghistorycommand.
messages ignored
Number of messages not stored in the history table because the severity level is greater than that specified with the
logginghistory command.
dropped
Number of messages that could not be processed due to lack of system resources. Dropped messages do not appear in the history table and are not sent to the SNMP server.
table entries flushed
Number of messages that have been removed from the history table to make room for newer messages.
SNMP notifications
Whether syslog traps of the appropriate level are sent to the SNMP server. The sending of syslog traps are enabled or disabled through thesnmp-serverenabletrapssyslog command.
entry number:
Number of the message entry in the history table. In the example above, the message "SYS-5-CONFIG_I Configured from console by console" indicates a syslog message consisting of the facility name (SYS), which indicates where the message came from, the severity level (5) of the message, the message name (CONFIG_I), and the message text.
timestamp
Time, based on the up time of the router, that the message was generated.
Related Commands
Command
Description
clearlogging
Clears messages from the logging buffer.
logginghistory
Limits syslog messages sent to the router's history table to a specified severity level.
logginghistorysize
Changes the number of syslog messages that can be stored in the history table.
logginglinecard
Logs messages to an internal buffer on a line card. This command limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level.
snmp-serverenabletraps
The [no]
snmp-serverenabletrapssyslog form of this command controls (enables or disables) the sending of system-logging messages to a network management station.
show logging system
To display the System Event Archive (SEA) logs, use the
showloggingsystem command in user EXEC mode or privileged EXEC mode.
showloggingsystem
[ disk [file-location] | last [num-of-last-log-msgs] ]
Syntax Description
disk
(Optional) Displays SEA log disk, where the logs will be stored.
diskfile-location
(Optional) Displays SEA logs from the specified file location.
The
disk keyword when used along with
file-location argument displays SEA logs from the specified file location.
num-of-last-log-msgs
(Optional) Displays the specified number of log messages.
Command Default
This command has no default settings.
Command Modes
User EXEC (>) Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SXH
This command was introduced.
12.2(33)SCC
This command was introduced for the Cisco uBR10012 Router in the Cisco IOS Software Release 12.2(33)SCC.
Usage Guidelines
The
showloggingsystemcommand displays the latest messages first.
Examples
The following example shows a sample output of the show logging system command that displays the specified number of latest system log messages:
Router# show logging system
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE
=====================================================
1: 01/24/07 15:38:40 6/-1 : MAJ, GOLD, syndiagSyncPinnacle failed in slot 6
2: 01/24/07 15:38:40 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
3: 01/24/07 15:38:40 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
4: 01/24/07 15:38:40 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
5: 01/24/07 15:38:40 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
6: 01/24/07 15:38:40 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
7: 01/24/07 15:38:39 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
The table below describes the significant fields shown in the display.
Table 12 show logging system Field Descriptions
Field
Description
MOD/SUB
Module or the submodule that generated the log message.
SEV
Severity level of the message.
COMP
Software component that has logged the message.
The following example shows a sample output of the show logging system command that displays SEA logs from the specified file location:
The following example shows a sample output of the
showloggingsystem command on the Cisco uBR10012 Router:
Router# show logging system
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE
=====================================================
1: 05/06/09 04:10:11 6/0: NON, SEATEST, "Test disk1":"
The following command is used to identify the disk on PRE currently being used to store the sea_log.dat file. The following example shows a sample output of the
showloggingsystemdisk command executed on the Cisco uBR10012 router:
Router# show logging systemdisk
SEA log disk: disk1:
The following command is used to view the specified number of log messages stored in the sea_log.dat file. The following example shows a sample output of the show logging systemlast 10
command on the Cisco uBR10012 router:
Router# show logging systemlast 10
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE
=====================================================
1: 05/06/09 04:47:48 5/0: NON, SEATEST, "Second Message"
2: 05/06/09 04:47:31 6/0: NON, SEATEST, "First Message"
Related Commands
clearloggingsystem
Clears the event records stored in the SEA.
copyloggingsystem
Copies the archived system events to another location.
loggingsystem
Enables or disables the SEA logging system.
show logging xml
To display the state of system message logging in an XML format, and to display the contents of the XML syslog buffer, use the
showloggingxml command in privileged EXEC mode.
showloggingxml
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
This command displays the same syslog state information as the standard
showlogging command, but displays the information in XML format. This command also displays the content of the XML syslog buffer (if XML-formatted buffer logging is enabled).
Examples
The following example compares the output of the standard
showlogging command with the output of the
showloggingxml command so that you can see how the standard information is formatted in XML.
Router# show logging
Syslog logging: enabled (10 messages dropped, 6 messages rate-limited, 0 flushes, 0 overruns, xml enabled)
Console logging: level debugging, 28 messages logged, xml enabled
Monitor logging: level debugging, 0 messages logged, xml enabled
Buffer logging: level debugging, 2 messages logged, xml enabled (2 messages logged)
Logging Exception size (8192 bytes)
Count and timestamp logging messages: disabled
Trap logging: level informational, 35 message lines logged
Logging to 10.2.3.4, 1 message lines logged, xml disabled
Logging to 192.168.2.1, 1 message lines logged, xml enabled
Log Buffer (8192 bytes):
00:04:20: %SYS-5-CONFIG_I: Configured from console by console
00:04:41: %SYS-5-CONFIG_I: Configured from console by console
Router# show logging xml
<syslog-logging status="enabled" msg-dropped="10" msg-rate-limited="6" flushes="0" overruns="0"><xml>enabled</xml></syslog-logging>
<console-logging level="debugging" messages-logged="28"><xml>enabled</xml></console-logging>
<monitor-logging level="debugging" messages-logged="0"><xml>enabled</xml></monitor-logging>
<buffer-logging level="debugging" messages-logged="2"><xml messages-logged="2">enabled</xml></buffer-logging>
<logging-exception size="8192 bytes"></logging-exception>
<count-and-timestamp-logging status="disabled"></count-and-timestamp-logging>
<trap-logging level="informational" messages-lines-logged="35"></trap-logging>
<logging-to><dest id="0" ipaddr="10.2.3.4" message-lines-logged="1"><xml>disabled</xml><dest></logging-to>
<logging-to><dest id="1" ipaddr="192.168.2.1" message-lines-logged="1"><xml>enabled</xml><dest></logging-to>
<log-xml-buffer size="44444 bytes"></log-xml-buffer>
<ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time>00:04:20</time><args><arg id="0">console</arg><arg id="1">console</arg></args></ios-log-msg>
<ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time>00:04:41</time><args><arg id="0">console</arg><arg id="1">console</arg></args></ios-log-msg>
Router#
The table below describes the significant fields shown in the displays.
Table 13 show logging and show logging xml Field Descriptions
Field
Description
XML Tag
Syslog logging
The global state of system message logging (syslog); “enabled” or “disabled.”
syslog-logging
Console logging
State of logging to console connections.
console-logging
Monitor logging
State of logging to monitor (TTY and Telnet) connections.
monitor-logging
Buffer logging
State of logging to the local system logging buffer.
buffer-logging
Count and timestamp logging messages:
Indicates whether the logging count feature is enabled. Corresponds to the
loggingcount command.
count-and-timestamp-logging
Trap logging
State of logging to a remote host.
trap-logging
Related Commands
Command
Description
showlogging
Displays the contents of the standard syslog buffer.
showloggingcount
Displays counts of each system error message.
showlogginghistory
Displays the contents of the SNMP syslog history table.
show memory
To display statistics about memory when Cisco IOS software, Cisco IOS XE or Software Modularity images are running, use the
showmemory command in user EXEC or privileged EXEC mode.
(Optional) Memory type to display (processor,
multibus,
io, or
sram). If
memory-type is not specified, statistics for all memory types present are displayed.
free
(Optional) Displays free memory statistics.
overflow
(Optional) Displays details about memory block header corruption corrections when the
exceptionmemoryignoreoverflow global configuration command is configured.
summary
(Optional) Displays a summary of memory usage including the size and number of blocks allocated for each address of the system call that allocated the block.
poisoning
(Optional) Displays memory poisoning details, including the following:
Alloc PID
Alloc Check
Alloc PC
Alloc Name
Corrupt Ptr
Corrupt Val
TotalBytes
MarkedBytes
TIME
Command Modes
User EXEC (>) Privileged EXEC (#)
Command History
Release
Modification
10.0
This command was introduced.
12.3(7)T
This command was enhanced with the
overflow keyword to display details about memory block header corruption corrections.
12.2(25)S
The command output was updated to display information about transient memory pools.
12.3(14)T
The command output was updated to display information about transient memory pools.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
12.2(18)SXF4
This command was implemented in Cisco IOS Software Modularity images.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(20)T
The
poisoning keyword was added.
Cisco IOS XE Release 3.1.0.SG
The
showmemory stand-alone command was introduced on the Cisco Catalyst 4500e Serfies Switches. The command functions as shown in the
Cisco IOS XE or Software Modularity
examples.
Cisco IOS XE Release 3.9 S
This command was integrated into Cisco IOS XE Release 3.9 S.
Usage Guidelines
Cisco IOS Software
The
showmemory command displays information about memory available after the system image decompresses and loads.
Cisco IOS XE or Software Modularity
Use the
showmemory command when a Cisco IOS XE or Software Modularity image is running to display a summary of system-wide memory utilization. To display details about POSIX and Cisco IOS style system memory information when Software Modularity images are running, use the
showmemorydetailed command.
When used on Cisco 4400 Series ISR, the showmemory command allows you to view the amount of memory being used for running active processes.
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software images. To view the appropriate output, see the following sections:
Cisco IOS Software
Cisco IOS XE
Cisco IOS Software Modularity
Examples
The following is sample output from the
showmemory command:
The following is sample output from the
showmemoryfreecommand:
Router# show memory free
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor B0EE38 5181896 2210076 2971820 2692456 2845368
Processor memory
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
24 Free list 1
CEB844 32 CEB7A4 CEB88C 0 0 0 96B894 SSE Manager
52 Free list 2
72 Free list 3
76 Free list 4
80 Free list 5
D35ED4 80 D35E30 D35F4C 0 0 D27AE8 96B894 SSE Manager
D27AE8 80 D27A48 D27B60 0 D35ED4 0 22585E SSE Manager
88 Free list 6
100 Free list 7
D0A8F4 100 D0A8B0 D0A980 0 0 0 2258DA SSE Manager
104 Free list 8
B59EF0 108 B59E8C B59F84 0 0 0 2258DA (fragment)
The output of the
showmemoryfree command contains the same types of information as the
showmemory output, except that only free memory is displayed, and the information is ordered by free list.
The first section of the display includes summary statistics about the activities of the system memory allocator. The table below describes the significant fields shown in the first section of the display.
Table 14 show memory Field Descriptions--First Section
Field
Description
Head
Hexadecimal address of the head of the memory allocation chain.
Total(b)
Sum of used bytes plus free bytes.
Used(b)
Amount of memory in use.
Free(b)
Amount of memory not in use.
Lowest(b)
Smallest amount of free memory since last boot.
Largest(b)
Size of largest available free block.
The second section of the display is a block-by-block listing of memory use. The table below describes the significant fields shown in the second section of the display.
Table 15 Characteristics of Each Block of Memory--Second Section
Field
Description
Address
Hexadecimal address of block.
Bytes
Size of block (in bytes).
Prev.
Address of previous block (should match the address on previous line).
Next
Address of next block (should match the address on next line).
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
PrevF
Address of previous free block (if free).
NextF
Address of next free block (if free).
Alloc PC
Address of the system call that allocated the block.
What
Name of process that owns the block, or “(fragment)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
The
showmemoryio command displays the free I/O memory blocks. On the Cisco 4000 router, this command quickly shows how much unused I/O memory is available.
The following is sample output from the
showmemoryio command:
The following sample output displays details of a memory block overflow correction when the
exceptionmemoryignoreoverflow global configuration command is configured:
The report includes the amount of time since the last correction was made and the name of the file that logged the memory block overflow details.
The
showmemorysram command displays the free SRAM memory blocks. For the Cisco 4000 router, this command supports the high-speed static RAM memory pool to make it easier for you to debug or diagnose problems with allocation or freeing of such memory.
The following is sample output from the
showmemorysram command:
Router# show memory sram
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
7AE0 38178 72F0 0 0 0 0 0
Total 38178
The following sample output from the
showmemory command used on the Cisco 4000 router includes information about SRAM memory and I/O memory:
The
showmemorysummary command displays a summary of all memory pools and memory usage per Alloc PC (address of the system call that allocated the block).
The following is a partial sample output from theshowmemorysummary command. This output shows the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the other fields, see the tables above.
The table below describes the significant fields shown in the display.
Table 16 show memory (Software Modularity Image) Field Descriptions
Field
Description
total
Total amount of memory on the device, in kilobytes.
used
Amount of memory in use, in kilobytes.
free
Amount of memory not in use, in kilobytes.
kernel reserved
Amount of memory reserved by the kernel, in kilobytes.
Process
Amount of memory used by processes.
Config
Amount of memory used by the configuration.
Examples
The following is sample output from theshowmemorycommand when a Cisco IOS Software Modularity image is running.
Router# show memory
System Memory: 262144K total, 116148K used, 145996K free 4000K kernel reserved
The table below describes the significant fields shown in the display.
Table 17 show memory (Software Modularity Image) Field Descriptions
Field
Description
total
Total amount of memory on the device, in kilobytes.
used
Amount of memory in use, in kilobytes.
free
Amount of memory not in use, in kilobytes.
kernel reserved
Amount of memory reserved by the kernel, in kilobytes.
Related Commands
Command
Description
exceptionmemoryignoreoverflow
Configures the Cisco IOS software to correct corruptions in memory block headers and allow a router to continue its normal operation.
showmemorydetailed
Displays POSIX and Cisco IOS style system memory information.
showprocessesmemory
Displays memory used per process.
show memory allocating-process
To display statistics on allocated memory with corresponding allocating processes, use the
showmemoryallocating-process command in user EXEC or privileged EXEC mode.
showmemoryallocating-process [totals]
Syntax Description
totals
(Optional) Displays allocating memory totals.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Usage Guidelines
The
showmemoryallocating-processcommand displays information about memory available after the system image decompresses and loads.
Examples
The following is sample output from the
showmemoryallocating-process command:
The table below describes the significant fields shown in the display.
Table 18 show memory allocating-process Field Descriptions
Field
Description
Head
Hexadecimal address of the head of the memory allocation chain.
Total(b)
Sum of used bytes plus free bytes.
Used(b)
Amount of memory in use in bytes.
Free(b)
Amount of memory not in use (in bytes).
Lowest(b)
Smallest amount of free memory since last boot (in bytes).
Largest(b)
Size of largest available free block (in bytes).
Address
Hexadecimal address of the block.
Bytes
Size of the block (in bytes).
Prev.
Address of the preceding block (should match the address on preceding row).
Next
Address of the following block (should match the address on following row).
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
Alloc PC
Address of the system call that allocated the block.
What
Name of process that owns the block, or “(fragment)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
The following is sample output from the
showmemoryallocating-processtotalscommand:
The table below describes the significant fields shown in the display.
Table 19 show memory allocating-process totals Field Descriptions
Field
Description
Head
Hexadecimal address of the head of the memory allocation chain.
Total(b)
Sum of used bytes plus free bytes.
Used(b)
Amount of memory in use (in bytes).
Free(b)
Amount of memory not in use (in bytes).
Lowest(b)
Smallest amount of free memory since last boot (in bytes).
Largest(b)
Size of the largest available free block in bytes.
PC
Program counter
Total
Total memory allocated by the process (in bytes).
Count
Number of allocations.
Name
Name of the allocating process.
Related Commands
Command
Description
showprocessesmemory
Displays memory used per process.
show memory dead
To display statistics on memory allocated by processes that have terminated, use the show memory dead command in user EXEC or privileged EXEC mode.
showmemorydead [totals]
Syntax Description
totals
(Optional) Displays memory totals for processes that have been terminated.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
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.
Usage Guidelines
The
showmemorydeadcommand displays information about processes that have been terminated. Terminated processes accounts for memory allocated under another process.
Examples
The following is sample output from the
showmemorydead command:
The table below describes the significant fields shown in the display.
Table 20 show memory dead Field Descriptions
Field
Description
Head
Hexadecimal address of the head of the memory allocation chain.
Total(b)
Sum of used bytes plus free bytes.
Used(b)
Amount of memory in use.
Free(b)
Amount of memory not in use (in bytes).
Lowest(b)
Smallest amount of free memory since last boot (in bytes).
Largest(b)
Size of the largest available free block (in bytes).
Address
Hexadecimal address of the block (in bytes).
Bytes
Size of the block (in bytes).
Prev.
Address of the preceding block.
Next
Address of the following block.
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
PrevF
Address of the preceding free block (if free).
NextF
Address of the following free block (if free).
Alloc PC
Address of the program counter that allocated the block.
What
Name of the process that owns the block, or “(fragment)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
show memory debug incremental
To display information about memory leaks after a starting time has been established, use the
showmemorydebugincremental command in privileged EXEC mode.
Displays all memory blocks that were allocated after issuing the
setmemorydebugincrementalstarting-time command.
leaks
Displays only memory that was leaked after issuing the
setmemorydebugincrementalstarting-time command.
lowmem
(Optional) Forces the memory leak detector to work in low memory mode, making no memory allocations.
summary
(Optional) Reports summarized memory leaks based on allocator_pc and size of the memory block.
status
Displays all memory blocks that were allocated after issuing the
setmemorydebugincrementalstarting-time command.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.3(7)T
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4T
The summary keyword was added.
Usage Guidelines
The
showmemorydebugincrementalallocations command displays all the memory blocks that were allocated after the
setmemorydebugincrementalstarting-time command was entered. The displayed memory blocks are just memory allocations, they are not necessarily leaks.
The
showmemorydebugincrementalleaks command provides output similar to the
showmemorydebugleaks command, except that it displays only memory that was leaked after the
setmemorydebugincrementalstarting-time command was entered.
The
showmemorydebugincrementalleakslowmemcommand forces memory leak detection to work in low memory mode. The amount of time taken for analysis is considerably greater than that of normal mode. The output for this command is similar to the
showmemorydebugleaks command, except that it displays only memory that was leaked after the
setmemorydebugincrementalstarting-time command was entered. You can use this command when you already know that normal mode memory leak detection will fail (perhaps by an unsuccessful previous attempt to invoke normal mode memory leak detection).
The
showmemorydebugincrementalleakssummary command displays a summarized report of the memory that was leaked after the
setmemorydebugincrementalstarting-time command was entered, ordered by allocator process call address (Alloc_pc) and by memory block size.
Theshowmemorydebugincrementalstatus command displays whether a starting point for incremental analysis has been set and the elapsed time since then.
Note
All show memory debug commands must be used on customer networks only to diagnose the router for memory leaks when memory depletion is observed. These CLI’s will have high CPU utilization and might result in time sensitive protocols to flap. These CLI’s are recommended for customer use, only in the maintenance window when the router is not in a scaled condition.
Note
All memory leak detection commands invoke normal mode memory leak detection, except when the low memory option is specifically invoked by use of the
lowmem keyword. In normal mode, if memory leak detection determines that there is insufficient memory to proceed in normal mode, it will display an appropriate message and switch to low memory mode.
Examples
Examples
The following example shows output from the
showmemorydebugincrementalcommand when entered with the
allocations keyword:
The following example shows output from the
showmemorydebugincremental command when entered with the
leaks and
summary keywords:
Router# show memory debug incremental leaks summary
Adding blocks for GD...
PCI memory
Alloc PC Size Blocks Bytes What
I/O memory
Alloc PC Size Blocks Bytes What
Processor memory
Alloc PC Size Blocks Bytes What
0x60874198 0000000052 0000000001 0000000052 Exec
0x60874198 0000000060 0000000001 0000000060 Exec
0x60874198 0000000100 0000000001 0000000100 Exec
0x60874228 0000000052 0000000004 0000000208 Exec
0x60874228 0000000060 0000000002 0000000120 Exec
0x60874228 0000000100 0000000004 0000000400 Exec
Examples
The following example shows output from the
showmemorydebugincremental command entered with the
status keyword:
Router# show memory debug incremental status
Incremental debugging is enabled
Time elapsed since start of incremental debugging: 00:00:10
Related Commands
Command
Description
setmemorydebugincrementalstarting-time
Sets the current time as the starting time for incremental analysis.
showmemorydebugleaks
Displays detected memory leaks.
show memory debug leaks
To display detected memory leaks, use the
showmemorydebugleaks command in privileged EXEC mode.
Cisco IOS software
showmemorydebugleaks
[ chunks | largest | lowmem | summary ]
Cisco Catalyst 4500e Series Switches running IOS XE software
showmemorydebugleak
Syntax Description
chunks
(Optional) Displays the memory leaks in chunks.
largest
(Optional) Displays the top ten leaking allocator_pcs based on size, and the total amount of memory they have leaked.
lowmem
(Optional) Forces the memory leak detector to work in low memory mode, making no memory allocations.
summary
(Optional) Reports summarized memory leaks based on allocator_pc and size of the memory block.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.3(8)T1
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Cisco IOS XE Release 3.1.0.SG
This command was introduced on the Cisco Catalyst 4500e Serfies Switches to display per-process memory leak ammounts.
Usage Guidelines
If no optional keywords are specified, the
showmemorydebugleaks command invokes normal mode memory leak detection and does not look for memory leaks in chunks.
Theshowmemorydebugleakschunks command invokes normal mode memory leak detection and looks for leaks in chunks as well.
The
showmemorydebugleakslargest command displays the top ten leaking allocator_pcs and the total amount of memory that they have leaked. Additionally, each time this command is invoked it remembers the previous invocation's report and compares it to the current invocation's report. If there are new entries in the current report they are tagged as “inconclusive.” If the same entry appears in the previous invocation's report and the current invocation's report, the inconclusive tag is not added. It would be beneficial to run memory leak detection more than once and to consider only the consistently reported leaks.
The
showmemorydebugleakslowmem command forces memory leak detection to work in low memory mode. The amount of time taken for analysis is considerably greater than that of normal mode. The output for this command is similar to the
showmemorydebugleaks command. You can use this command when you already know that normal mode memory leak detection will fail (perhaps by an unsuccessful previous attempt to invoke normal mode memory leak detection).
The
showmemorydebugleakssummary command reports memory leaks based on allocator_pc and then on the size of the block.
Note
All show memory debug commands must be used on customer networks only to diagnose the router for memory leaks when memory depletion is observed. These CLI’s will have high CPU utilization and might result in time sensitive protocols to flap. These CLI’s are recommended for customer use, only in the maintenance window when the router is not in a scaled condition.
Note
The command
show memory debug leak lowmem is extremely CPU intensive and can result in CPUHOG/WATCHDOG crash. This command must be used only when the router has reached an unusable state due to memory exhaustion. Its use on high end platforms such as ISR and above can potentially crash the box. Use outside of these limitations can cause a console hang of 1 hour in some cases. As an alternative, use the
show memory debug leak command.
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software images. To view the appropriate output, choose one of the following sections:
The table below describes the significant fields shown in the display.
Table 22 show memory debug leaks chunks Field Descriptions
Field
Description
Address
Hexadecimal address of the leaked block.
Size
Size of the leaked block (in bytes).
Alloc_pc
Address of the system call that allocated the block.
PID
The process identifier of the process that allocated the block.
Name
The name of the process that allocated the block.
Size
(Chunk Elements) Size of the leaked element (bytes).
Parent
(Chunk Elements) Parent chunk of the leaked chunk.
Name
(Chunk Elements) The name of the leaked chunk.
Examples
The following example shows output from the
showmemorydebugleakslargest command:
Router# show memory debug leaks largest
Adding blocks for GD...
PCI memory
Alloc_pc total leak size
I/O memory
Alloc_pc total leak size
Processor memory
Alloc_pc total leak size
608D2848 32776 inconclusive
608D2FD8 32776 inconclusive
60C656AC 288 inconclusive
60C67D74 48 inconclusive
605B7E98 40 inconclusive
605B7EDC 40 inconclusive
60C659D4 40 inconclusive
605B7E70 32 inconclusive
605B7EB4 32 inconclusive
60616750 24 inconclusive
The following example shows output from the second invocation of the
showmemorydebugleakslargest command:
Router# show memory debug leaks largest
Adding blocks for GD...
PCI memory
Alloc_pc total leak size
I/O memory
Alloc_pc total leak size
Processor memory
Alloc_pc total leak size
608D2848 32776
608D2FD8 32776
60C656AC 288
60C67D74 48
605B7E98 40
605B7EDC 40
60C659D4 40
605B7E70 32
605B7EB4 32
60616750 24
Examples
The following example shows output from the
showmemorydebugleakssummary command:
Router# show memory debug leaks summary
Adding blocks for GD...
PCI memory
Alloc PC Size Blocks Bytes What
I/O memory
Alloc PC Size Blocks Bytes What
Processor memory
Alloc PC Size Blocks Bytes What
0x605B7E70 0000000032 0000000001 0000000032 Init
0x605B7E98 0000000040 0000000001 0000000040 Init
0x605B7EB4 0000000032 0000000001 0000000032 Init
0x605B7EDC 0000000040 0000000001 0000000040 Init
0x60616750 0000000024 0000000001 0000000024 Init
0x606167A0 0000000024 0000000001 0000000024 Init
0x608D2848 0000032776 0000000001 0000032776 Audit Process
0x608D2FD8 0000032776 0000000001 0000032776 Audit Process
0x60C656AC 0000000040 0000000001 0000000040 Init
0x60C656AC 0000000248 0000000001 0000000248 Init
0x60C659D4 0000000040 0000000001 0000000040 Init
0x60C67D74 0000000048 0000000001 0000000048 Init
The table below describes the significant fields shown in the display.
Table 23 show memory debug leaks summary Field Descriptions
Field
Description
Alloc_pc
Address of the system call that allocated the block.
Size
Size of the leaked block.
Blocks
Number of blocks leaked.
Bytes
Total amount of memory leaked.
What
Name of the process that owns the block.
Examples
Examples
The following example shows output from the
showmemorydebugleak command on command on a Cisco Catalyst 4500e switch, using a Cisco IOS image from Cisco IOS XE Release 3.1.0.SG and later releases:
The table below describes the significant fields shown in the display.
Table 24 show memory debug leaks summary Field Descriptions
Field
Description
Leak
Size of the leaked block.
PID
The process identifier of the process that allocated the block.
Name
Name of the process that owns the block.
Related Commands
Command
Description
setmemorydebugincrementalstarting-time
Sets the current time as the starting time for incremental analysis.
showmemorydebugincrementalallocation
Displays all memory blocks that were allocated after the issue of the
setmemorydebugincrementalstarting-time command.
showmemorydebugincrementalleaks
Displays only memory that was leaked after the issue of the
setmemorydebugincrementalstarting-time command.
showmemorydebugincrementalleakslowmem
Forces incremental memory leak detection to work in low memory mode. Displays only memory that was leaked after the issue of the
setmemorydebugincrementalstarting-time command.
showmemorydebugincrementalstatus
Displays if the starting point of incremental analysis has been defined and the time elapsed since then.
show memory debug references
To display debug information on references, use the
showmemorydebugreferencescommand in user EXEC or privileged EXEC mode.
(Optional) Displays the possible references to free memory.
start-address
(Optional) Address numbers <0-4294967295> that determine the address range.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Usage Guidelines
All show memory debug commands must be used on customer networks only to diagnose the router for memory leaks when memory depletion is observed. These CLI’s will have high CPU utilization and might result in time sensitive protocols to flap. These CLI’s are recommended for customer use, only in the maintenance window when the router is not in a scaled condition.
Examples
The following is sample output from the
showmemorydebugreferencescommand:
The table below describes the significant fields shown in the displays.
Table 25 show memory debug references Field Descriptions
Field
Description
Address
Hexadecimal address of the block having the given or dangling reference.
Reference
Address which is given or dangling.
Free_block
Address of the free block which now contains the memory referenced by the dangling reference.
Cont_block
Address of the control block which contains the block having the reference.
Cont_block_name
Name of the control block.
show memory debug unused
To display debug information on leaks that are accessible, but are no longer needed, use the
showmemorydebugunusedcommand in user EXEC or privileged EXEC mode.
showmemorydebugunused
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Examples
The following is sample output from the
showmemorydebugunusedcommand:
The table below describes the significant fields shown in the display.
Table 26 show memory debug unused Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Alloc_pc
Address of the program counter that allocated the block.
PID
Process identifier of the process that allocated the block.
size
Size of the unused block (in bytes).
Name
Name of the process that owns the block.
show memory detailed
To display detailed memory information about POSIX and Cisco IOS processes when Cisco IOS XE or Software Modularity images are running, use the
showmemorydetailedcommand in privileged EXEC mode.
(Optional) Displays information about bigger free blocks in the process.
free
(Optional) Displays free memory information.
io
(Optional) Displays the free I/O memory blocks.
overflow
(Optional) Displays details about memory block header corruption corrections when the
exceptionmemoryignoreoverflow global configuration command is configured.
physical
(Optional) Displays physical memory information.
shared
(Optional) Displays shared memory information.
statistics
(Optional) Displays detailed memory usage by address of the system call that allocated the block.
summary
(Optional) Displays summary information about memory usage per system call that allocated the block.
Command Default
No detailed memory information about POSIX and Cisco IOS processes is displayed.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(18)SXF4
This command was introduced to support Software Modularity images.
Cisco IOS XE Release 3.1.0.SG
This command was introduced on the Cisco Catalyst 4500e Serfies Switches.
Usage Guidelines
Detailed output of the process memory on the device is displayed with this command. The process memory summary is displayed first, followed by POSIX and Cisco IOS memory information. The POSIX memory information includes the address, the size in bytes, and the type of memory used by various segments such as program text, data, stack, shared memory, device memory, and heap. Cisco IOS memory information includes the native Cisco IOS display of memory blocks maintained by the Cisco IOS memory management library.
Examples
Example output varies between Cisco IOS software releases. To view the appropriate output, choose one of the following sections:
The following is partial sample output from the
showmemorydetailedcommand for a Cisco IOS process:
Router# show memory detailed cdp2.iosproc
System Memory: 131072K total, 115836K used, 15236K free 4000K kernel reserved
Process sbin/cdp2.iosproc, type IOS, PID = 12329
636K total, 4K text, 4K data, 28K stack, 600K dynamic
16384 heapsize, 3972 allocated, 10848 free
Address Bytes What
0x3B42000 4194304 Shared Memory
0x7FBB000 8192 Program Stack
0x8020000 49152 Program Text
0x802C000 4096 Program Data
0x802D000 8192 Allocated memory
0x60000000 4096 Shared Memory "SHM_IDB"
0x60001000 32768 Shared Memory
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 8034058 508152 480420 27732 17368 18716
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
08034058 0000020008 00000000 08038EB8 001 -------- -------- 727FB668 Managed Chunk Queue Elements
08038EB8 0000002568 08034058 080398F8 001 -------- -------- 72871A44 *Init*
080398F8 0000001512 08038EB8 08039F18 001 -------- -------- 728819D4 List Elements
.
.
.
The first section of the display shows system summary information. The table below describes the significant fields shown in the first section of the display.
Table 27 show memory detailed Field Descriptions--First Section
Field
Description
total
Total amount of memory on the device, in kilobytes.
used
Amount of memory in use, in kilobytes.
free
Amount of memory not in use, in kilobytes.
kernel reserved
Amount of memory reserved by the kernel, in kilobytes.
The second section of the display includes process summary statistics about the activities of the system memory allocator. The table below describes the significant fields shown in the second section of the display.
Table 28 show memory detailed Field Descriptions--Second Section
Field
Description
Process
Process name and path.
type
Type of process: POSIX or IOS.
PID
Process ID.
total
Total amount of memory used by the specified process, in kilobytes.
text
Amount of memory, in kilobytes, used by the text segment of the specified process.
data
Amount of memory, in kilobytes, used by the data segment of the specified process.
stack
Amount of memory, in kilobytes, used by the stack segment of the specified process.
dynamic
Amount of memory, in kilobytes, used by the dynamic segment of the specified process.
heapsize
Size of the process heap. Note that the Cisco IOS memory management library allocates heap dynamically. This is shown in the Cisco IOS memory details that follow the POSIX memory display.
allocated
Amount of memory, in kilobytes, allocated from the heap.
free
Amount of free memory, in kilobytes, in the heap for the specified process.
The third section of the display shows POSIX process perspective memory information. The table below describes the significant fields shown in the third section of the display.
Table 29 show memory detailed Field Descriptions--Third Section
Field
Description
Address
Hexadecimal address of block.
Bytes
Size of block (in bytes).
What
Type of memory segment that owns the block, or “(fragment)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
The fourth section of the display shows Cisco IOS memory information as a block-by-block listing of memory use. The table below describes the significant fields shown in the fourth section of the display.
Table 30 show memory detailed Field Descriptions--Fourth Section
Field
Description
Head
Hexadecimal address of the head of the memory allocation chain.
Total(b)
Sum of used bytes plus free bytes.
Used(b)
Amount of memory in use.
Free(b)
Amount of memory not in use.
Lowest(b)
Smallest amount of free memory since last boot.
Largest(b)
Size of largest available free block.
Address
Hexadecimal address of block.
Bytes
Size of block (in bytes).
Prev
Address of previous block (should match address on previous line).
Next
Address of next block (should match address on next line).
PrevF
Address of previous free block (if free).
NextF
Address of next free block (if free).
Alloc PC
Address of the system call that allocated the block.
what
Type of memory segment that owns the block, or “(fragment)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
The following is sample output from the
showmemorydetailedcommand for a POSIX process:
Router# show memory detailed 12290
System Memory: 131072K total, 115876K used, 15196K free 4000K kernel reserved
Process sbin/sysmgr.proc, type POSIX, PID = 12290
400K total, 100K text, 144K data, 12K stack, 144K dynamic
81920 heapsize, 68716 allocated, 8824 free
Address Bytes What
0x7FDF000 126976 Program Stack (pages not allocated)
0x7FFE000 4096 Program Stack
0x8000000 122880 Program Stack (pages not allocated)
0x801E000 8192 Program Stack
0x8020000 102400 Program Text
0x8039000 147456 Program Data
0x805D000 8192 Heap Memory
0x8060000 16384 Heap Memory
0x8064000 16384 Heap Memory
0x8068000 8192 Heap Memory
0x806C000 16384 Heap Memory
0x8070000 16384 Heap Memory
0x8074000 16384 Heap Memory
0x8078000 16384 Heap Memory
0x807C000 16384 Heap Memory
0x8080000 16384 Heap Memory
The following partial sample output from the
showmemorydetailed command with a process name and the
physical keyword that displays the summary of physical memory used by the specified process along with the shared memory details:
Router# show memory detailed sysmgr.proc physical
Pid Data Stack Dynamic Text Shared Maps Process
20482 304K 16K 256K 3480K 468K 60 sysmgr.proc
Total Physical Memory used or mapped by sysmgr.proc
Private memory used (Data/Stack/Dynamic) : 576K
Shared memory mapped (Text/Shared) : 3948K
Number of memory maps : 60
Dev 1:Text/Data 2:Mapped 3:Shared 4:DSO
Flags SHD:Shared PRV:Private FXD:Fixed ANN:Anon PHY:Phys
LZY:Lazy ELF:Elf STK:Stack NOC:Nocache
Phy Addr Size Pid Virt Addr What Dev Prot MapFlags
0x0 32768K 20482 0x70000000 Text 4 R-X SHD FXD ELF
0x2000000 32768K 20482 0x72000000 Text 4 R-X SHD FXD ELF
0x4000000 32768K 20482 0x74000000 Text 4 R-X SHD FXD ELF
0x522B000 4K 20482 0x1020000 Text 4 R-X SHD FXD ELF
Phy Addr Size Pid Virt Addr What Dev Prot MapFlags
0x9EFD4000 32K 20482 0x105C000 Heap 2 RW- PRV ANN
0x9EFF0000 32K 20482 0x1054000 Heap 2 RW- PRV ANN
0x9EFF8000 32K 20482 0x1034000 Heap 2 RW- PRV ANN
0x9F003000 4K 20482 0x7B43C000 Data 4 RW- PRV FXD ANN ELF
.
.
.
The table below describes the significant fields shown in the display.
Table 31 show memory detailed Field Descriptions
Field
Description
Shared
Amount of memory shared by the specified process, in kilobytes.
Maps
Number of memory maps for the specified process.
Process
Name of the process.
Private memory used
Total amount of private memory used by the process.
Shared memory mapped
Total amount of shared memory used by the process.
Number of memory maps
Total number of maps for the process.
Flags
Flags that specify information about handling of the mapped region. The available flags are as follows:
SHD:Shared--Specifies that memory is shared between different process.
PRV:Private--Specifies that memory is private to this process.
FXD:Fixed--Specifies that memory is mapped to a fixed virtual address in the process.
ANN:Anon--Specifies that physical memory was allocated by the kernel.
PHY:Phys--Specifies that the user specified the physical memory.
LZY:Lazy--Specifies that memory is lazy mapped; that is, physical memory is not allocated until the memory is either read or written to other memory.
ELF:Elf--Specifies that memory is an Executable and Linkable Format (ELF) object.
STK:Stack--Specifies that memory is used for stack.
NOC:Nocache--Specifies that memory is set up without any cache.
Phy Addr
Hexadecimal address of the physical memory block.
Size
Amount of physical memory mapped in the process of development.
Virt Addr
Virtual memory to which this memory is mapped.
Prot
Memory protection settings for the memory--read, write, and execute.
MapFlags
Represents special mapping properties used for the memory.
Examples
The following is sample output from the
showmemorydetailed command for the
iosd process:
Displays detailed memory information of all applicable processes.
show memory ecc
To display single-bit Error Code Correction (ECC) error logset data, use the show memory ecc command in privileged EXEC mode.
showmemoryecc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1(30)CC
This command was introduced in Cisco IOS Release 11.1(30)CC.
12.0(4)XE
This command was integrated into Cisco IOS Release 12.0(4)XE.
12.0(6)S
This command was integrated into Cisco IOS Release 12.0(6)S.
12.1(13)
This command was integrated into Cisco IOS Release 12.1(13).
Usage Guidelines
Use this command to determine if the router has experienced single-bit parity errors.
Examples
The following is sample output from the show memory ecc command from a 12000-series router running Cisco IOS Release 12.0(23)S:
Router# show memory ecc
ECC Single Bit error log
------------------------
Single Bit error detected and corrected at 0x574F3640
- Occured 1 time(s)
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0xE9
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write Single Bit error detected and corrected at 0x56AB3760
- Occured 1 time(s)
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0x68
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write
Total Single Bit error(s) thus far: 2
The table below describes the significant fields shown in the first section of the display.
Table 32 show memory ecc Field Descriptions
Field
Description
Occured n time(s)
Number of single-bit errors that has occurred.
Whether a scrub was attempted at this address:
Indicates whether a scrub has been performed.
Syndrome of the last error at this address:
Describes the syndrome of last error.
Error detected on a read-modify-write cycle ?
Indicates whether an error has occurred.
Address region classification: Unknown
Describes the region of the error.
Address media classification :
Describes the media of the error and correction.
Related Commands
Command
Description
showmemory
Displays statistics about memory, including memory-free pool statistics.
show memory events
To display recorded memory events, use the
showmemoryeventscommand in privileged EXEC mode.
showmemoryevents
[ outstanding [summary] ]
Syntax Description
outstanding
(Optional) Displays the outstanding allocation events in the event buffer.
summary
(Optional) Displays a summary of outstanding allocation events in the event buffer.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)M
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M.
Usage Guidelines
Before you can enable the
showmemoryevents command, you must configure the
memoryrecordevents command in global configuration mode.
Examples
The following is sample output from the
showmemoryeventscommand:
Router# configure terminal
Router(config)# memory record events
Memory event recording already enabled!
Router(config)# exit
Router# show memory events
Last recorded memory events:
When Type Block/Chunk DataPtr Size PID What Traceback/PC
4d19h FREE 695B3200 695B3230 3000 82 Iterator Hash Entry 615B75C4
The table below describes the significant fields shown in the display.
Table 33 show memory events Field Descriptions
Field
Description
When
Time when the memory event was last seen by the system (in hours and days).
Type
Allocation type.
Block/Chunk/DataPtr
Number of memory events allocated.
Size
Amount of memory, in bytes, used by the task.
PID
Packet identification number.
What
Name of the process that owns a block or fragment.
Traceback/PC
Traceback error.
The following is sample output from the
showmemoryeventscommand using the
outstandingandsummarykeywords:
Router# configure terminal
Router(config)# memory record events
Memory event recording already enabled!
Router(config)# exit
Router# show memory events outstanding summary
Last-Seen Type How-Many Size PID What Traceback/PC
5d16h ALLOC 1 320 135 Exec 61B399F4
The table below describes the significant fields shown in the display.
Table 34 show memory events Field Descriptions
Field
Description
Last-Seen
Time when the memory event was last seen by the system (in hours and days).
Type
Allocation type.
How-Many
Number of memory events allocated.
Size
Amount of memory, in bytes, used by the task.
PID
Packet identification number.
What
Name of the process that owns a block or fragment.
Traceback/PC
Traceback error.
Related Commands
Command
Description
showmemorytraceback
Displays memory traceback information.
show memory failures alloc
To display statistics about failed memory allocation requests, use the
showmemoryfailuresalloccommand in the privileged EXEC mode.
showmemoryfailuresalloc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Examples
The following is sample output from the
showmemoryfailuresalloc command:
(Optional)
Include allocating process names with the standard output.
dead
(Optional) Display only memory owned by dead processes.
free
(Optional) Display only memory not allocated to a process.
totals
(Optional) Summarizes the statistics for allocating processes, dead memory, or free memory.
Command Modes
Exec
Command History
Release
Modification
12.1
This command was introduced in a release prior to 12.1. This command replaced the showmemorysram command.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The show memory fast command displays the statistics for the fast memory. “Fast memory” is another name for “processor memory,” and is also known as “cache memory.” Cache memory is called fast memory because the processor can generally access the local cache (traditionally stored on SRAM positioned close to the processor) much more quickly than main memory or RAM.
Note
The showmemoryfast command is a command alias for the showmemoryprocessor command. These commands will issue the same output.
Examples
The following example shows sample output from the showmemoryfast and the showmemoryprocessor commands:
The following example shows sample output from the showmemoryfastallocating-process command, followed by sample output from the showmemoryfastallocating-processtotals command:
The following example shows sample output from the showmemoryfastdead command:
Router#show memory fast dead
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
8498FC20 0000000028 8498FB90 8498FC64 001 -------- -------- 81472B24 AAA MI SG NAME
-------
68
Router#show memory fast dead totals
Dead Proc Summary for: Processor
PC Total Count Name
0x81472B24 68 1 AAA MI SG NAME
Router#
show memory fragment
To display the block details of fragmented free blocks and allocated blocks, which is physically just before or after the blocks on the free list, use the showmemoryfragmentcommand in user EXEC or privileged EXEC mode.
showmemory
[ processor | io ]
fragment [detail]
Syntax Description
processor
(Optional) Displays the processor memory information.
io
(Optional) Displays the I/O memory information.
fragment
Displays the information of the free blocks and the blocks surrounding the free blocks.
detail
(Optional) Displays the detailed information of all the free blocks and the blocks surrounding the free blocks that are located between the allocated blocks.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
12.3(14)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Examples
The following is sample output from the showmemoryprocessorfragmentcommand:
The table below describes the significant fields shown in the display.
Table 36 show memory lite-chunks Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
Alloc PC
Address of the program counter that allocated the block.
show memory multibus
To display statistics about multibus memory, including memory-free pool statistics, use the
showmemorymultibuscommand in user EXEC or privileged EXEC mode.
(Optional) Displays allocating memory totals by name.
dead[totals]
(Optional) Displays memory totals on dead processes.
fragment[detail]
(Optional) Displays memory statistics for fragmented processes.
free[totals]
(Optional) Displays statistics on free memory.
statistics[history]
(Optional) Displays memory pool history statistics on all processes.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Examples
The following is sample output from the
showmemorymultibus command:
Router# show memory multibus
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes
6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes
65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes
65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k
654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k
6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)
65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s
654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles
654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas
654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*
.
.
.
The table below describes the significant fields shown in the display.
Table 37 show memory multibus Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Bytes
Size of the block (in bytes).
Prev
Address of the preceding block (should match the address on the preceding line).
Next
Address of the following block (should match the address on the following line).
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
PrevF
Address of the preceding free block (if free).
NextF
Address of the following free block (if free).
Alloc PC
Address of the program counter that allocated the block.
What
Name of the process that owns the block, or “(fragmen)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
show memory pci
To display statistics about Peripheral Component Interconnect (PCI) memory, use the
showmemorypci command in user EXEC or privileged EXEC mode.
showmemorypci
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Examples
The following is sample output from the
showmemorypci command:
The table below describes the significant fields shown in the display.
Table 38 show memory pci Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Bytes
Size of the block (in bytes).
Prev
Address of the preceding block (should match the address on the preceding line).
Next
Address of the following block (should match the address on the following line).
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
PrevF
Address of the preceding free block (if free).
NextF
Address of the following free block (if free).
Alloc PC
Address of the program counter that allocated the block.
what
Name of process that owns the block, or “(fragmen)” if the block is a fragment, or "(coalesced)" if the block was coalesced from adjacent free blocks.
show memory processor
To display statistics on the Router Processor memory, use the
showmemoryprocessor command in user EXEC or privileged EXEC mode.
showmemoryprocessor
[ allocating-process [totals] | dead [totals] | fragment [detail] | free [totals] | statistics ]
Syntax Description
allocating-process
(Optional) Displays the allocating process name.
totals
(Optional) Displays the total allocated memory.
dead
(Optional) Displays information about memory owned by dead processes.
totals
(Optional) Displays the total dead process memory.
fragment
(Optional) Displays the block details of fragmented free blocks and allocated blocks, which are shown either preceding or following the blocks on the free list.
detail
(Optional) Displays memory fragment information in detail.
free
(Optional) Displays the statistics of the available processor memory.
totals
(Optional) Displays the total free memory.
statistics
(Optional) Displays memory pool statistics.
Command Modes
User EXEC (>) Privileged EXEC (#)
Command History
Release
Modification
12.0
This command was introduced.
12.4(24)T
This command was modified in a release earlier than Cisco IOS Release 12.4(24)T. The
allocating-process and
dead keywords were added.
Examples
The following is sample output from the
showmemoryprocessorcommand:
Router# show memory processor
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes
6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes
65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes
65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k
654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k
6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)
65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s
654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles
654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas
654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*
The table below describes the significant fields shown in the display.
Table 39 show memory processor Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Bytes
Size of the block (in bytes).
Prev
Address of the preceding block (should match the address on the preceding line).
Next
Address of the following block (should match the address on the following line).
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
PrevF
Address of the preceding free block (if free).
NextF
Address of the following free block (if free).
Alloc PC
Address of the program counter that allocated the block.
What
Name of the process that owns the block or fragment.
The following is sample output from the
showmemoryprocessorallocating-processcommand:
The table below describes the significant fields shown in the display.
Table 42 show memory processor statistics Field Descriptions
Field
Description
Head
Hexadecimal address of the head of the memory allocation chain.
Total(b)
Sum of the used bytes plus free bytes.
Used(b)
Amount of memory in use (in bytes).
Free(b)
Amount of memory not in use (in bytes).
Lowest(b)
Smallest amount of free memory since the last boot (in bytes).
Largest(b)
Size of the largest available free block (in bytes).
show memory scan
To monitor the number and type of parity (memory) errors on your system, use the show memory scan command in EXEC mode.
showmemoryscan
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
Modification
12.0(4)XE
This command was introduced.
12.0(7)T
This command was implemented in Cisco IOS Release 12.0(7) T.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following example shows a result with no memory errors:
Router# show memory scan
Memory scan is on.
No parity error has been detected.
If errors are detected in the system, the show memory scan command generates an error report. In the following example, memory scan detected a parity error:
Router# show memory scan
Memory scan is on.
Total Parity Errors 1.
Address BlockPtr BlckSize Disposit Region Timestamp
6115ABCD 60D5D090 9517A4 Scrubed Local 16:57:09 UTC Thu Mar 18
The table below describes the fields contained in the error report.
Table 43 show memory scan Field Descriptions
Field
Description
Address
The byte address where the error occurred.
BlockPtr
The pointer to the block that contains the error.
BlckSize
The size of the memory block
Disposit
The action taken in response to the error:
BlockInUse--An error was detected in a busy block.
InFieldPrev--An error was detected in the previous field of a block header.
InHeader--An error was detected in a block header.
Linked--A block was linked to a bad list.
MScrubed--The same address was “scrubbed” more than once, and the block was linked to a bad list.
MultiError--Multiple errors have been found in one block.
NoBlkHdr--No block header was found.
NotYet--An error was found; no action has been taken at this time.
Scrubed--An error was “scrubbed.”
SplitLinked--A block was split, and only a small portion was linked to a bad list.
Region
The memory region in which the error was found:
IBSS--image BSS
IData--imagedata
IText--imagetext
local--heap
Timestamp
The time the error occurred.
show memory statistics history
To display the history of memory consumption, use the showmemorystatisticshistorycommand in user EXEC or privileged EXEC mode.
showmemorystatisticshistory [table]
Syntax Description
table
(Optional) Summary of memory consumption history.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
Modification
12.3(14)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Examples
The following is sample output from the showmemorystatisticshistorytable command. The field descriptions are self-explanatory.
Router# show memory statistics history table
History for Processor memory
Time: 15:48:56.806
Used(b): 422748036 Largest(b): 381064952 Free blocks :291
Maximum memory users for this period
Process Name Holding Num Alloc
Virtual Exec 26992 37
TCP Protocols 14460 6
IP Input 1212 1
Time: 14:42:54.506
Used(b): 422705876 Largest(b): 381064952 Free blocks :296
Maximum memory users for this period
Process Name Holding Num Alloc
Exec 400012740 24
Dead 1753456 90
Pool Manager 212796 257
Time: 13:37:26.918
Used(b): 20700520 Largest(b): 381064952 Free blocks :196
Maximum memory users for this period
Process Name Holding Num Alloc
Exec 8372 5
Time: 12:39:44.422
Used(b): 20701436 Largest(b): 381064952 Free blocks :193
Time: 11:46:25.135
Used(b): 20701436 Largest(b): 381064952 Free blocks :193
Maximum memory users for this period
Process Name Holding Num Alloc
CDP Protocol 3752 25
Time: 10:44:24.342
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 09:38:53.038
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 08:33:35.154
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 07:28:05.987
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 06:35:22.878
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 05:42:14.286
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 04:41:53.486
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 03:48:47.891
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 02:46:32.391
Used(b): 20701400 Largest(b): 381064952 Free blocks :194
Time: 01:54:27.931
Used(b): 20717804 Largest(b): 381064952 Free blocks :189
Time: 01:02:05.535
Used(b): 20717804 Largest(b): 381064952 Free blocks :189
Maximum memory users for this period
Process Name Holding Num Alloc
Entity MIB API 67784 16
TTY Background 12928 4
Exec 7704 3
Time: 00:00:17.936
Used(b): 21011192 Largest(b): 381064952 Free blocks :186
Maximum memory users for this period
Process Name Holding Num Alloc
Init 18653520 6600
CCPROXY_CT 599068 57
Proxy Session Applic 275424 21
History for I/O memory
Time: 15:48:56.809
Used(b): 7455520 Largest(b): 59370080 Free blocks :164
Time: 14:42:54.508
Used(b): 7458064 Largest(b): 59370080 Free blocks :165
Maximum memory users for this period
Process Name Holding Num Alloc
Pool Manager 141584 257
Time: 13:37:26.920
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 12:39:44.424
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 11:46:25.137
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 10:44:24.344
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 09:38:53.040
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 08:33:35.156
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 07:28:05.985
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 06:35:22.877
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 05:42:14.285
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 04:41:53.485
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 03:48:47.889
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 02:46:32.389
Used(b): 7297744 Largest(b): 59797664 Free blocks :25
Time: 01:54:27.929
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Time: 01:02:05.533
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Time: 00:00:17.937
Used(b): 7308336 Largest(b): 59797664 Free blocks :23
Maximum memory users for this period
Process Name Holding Num Alloc
Init 7296000 214
Pool Manager 816 3
Related Commands
Command
Description
memorystatisticshistorytable
Changes the memory log time.
show memory traceback
To display memory traceback information, use the
showmemorytracebackcommand in privileged EXEC mode.
showmemorytraceback
[ id | exclusive | totals ]
Syntax Description
id
(Optional) Traceback ID.
exclusive
(Optional) Displays the memory blocks that have traceback information.
totals
(Optional) Displays information about memory usage of blocks having tracebacks.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)M
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M.
Usage Guidelines
Before you can enable the
showmemorytraceback command, you must configure the
memoryrecordevents command in global configuration mode.
Examples
The following is sample output from the
showmemorytraceback command for traceback ID 100:
The following is sample output from the
showmemorytraceback command using the
exclusivekeyword:
Router# configure terminal
Router(config)# memory record events
Memory event recording already enabled!
Router(config)# exit
Router# show memory traceback exclusive
Address Size refcount tid What
682E53F4 0005206856 000 T43 (coalesced)
68D2739C 0000002212 000 T85 (coalesced)
The table below describes the significant fields shown in the display.
Table 44 show memory traceback Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Size
Amount of memory, in bytes, used by the task.
refcount
Reference count for the memory block, indicating how many different processes are using that block of memory.
tid
Task ID.
What
Name of the process that owns the block or fragment. Specifies if the block is a fragment or coalesced.
Related Commands
Command
Description
showmemoryevents
Displays recorded memory events.
show memory transient
To display statistics about transient memory, use the
showmemorytransientcommand in user EXEC or privileged EXEC mode.
showmemorytransient
[ allocating-process [totals] | dead [totals] | fragment [detail] | free [totals] | statistics [history] ]
Syntax Description
allocating-process
(Optional) Displays allocating memory totals by name.
dead[totals]
(Optional) Displays memory totals on dead processes.
fragment[detail]
(Optional) Displays memory statistics for fragmented processes.
free[totals]
(Optional) Displays statistics on free memory.
statistics[history]
(Optional) Displays memory pool history statistics on all processes.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.0
This command was introduced.
Examples
The following is sample output from the
showmemorytransientcommand:
Router# show memory transient
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
81F99C00 0002236408 00000000 821BBC28 000 829C8104 82776FD0 8060B6D0 (coalesc)
821BBC28 0000020004 81F99C00 821C0A7C 001 -------- -------- 8002D5C0 Managed s
821C0A7C 0000010004 821BBC28 821C31C0 001 -------- -------- 811604C0 List Eles
821C31C0 0000005004 821C0A7C 821C457C 001 -------- -------- 81160500 List Heas
The table below describes the significant fields shown in the display.
Table 45 show memory transient Field Descriptions
Field
Description
Address
Hexadecimal address of the block.
Bytes
Size of the block (in bytes).
Prev
Address of the preceding block (should match the address on preceding line).
Next
Address of the following block (should match the address on following line).
Ref
Reference count for that memory block, indicating how many different processes are using that block of memory.
PrevF
Address of the preceding free block (if free).
NextF
Address of the following free block (if free).
Alloc PC
Address of the system call that allocated the block.
what
Name of the process that owns the block, or “(fragment)” if the block is a fragment, or “(coalesced)” if the block was coalesced from adjacent free blocks.
show microcode
To display microcode image information available on line cards, use the showmicrocode command in EXEC mode.
showmicrocode
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
Modification
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following is sample output from the showmicrocode command:
Router# show microcode
Microcode bundled in system
Card Microcode Target Hardware Description
Type Version Version
---- --------- --------------- -----------
SP 2.3 11.x SP version 2.3
EIP 1.1 1.x EIP version 1.1
TRIP 1.2 1.x TRIP version 1.2
FIP 1.4 2.x FIP version 1.4
HIP 1.1 1.x HIP version 1.1
SIP 1.1 1.x SIP version 1.1
FSIP 1.1 1.x FSIP version 1.1
In the following example for the Cisco 7200 series router, the output from the showmicrocode command lists the hardware types that support microcode download. For each type, the default microcode image name is displayed. If there is a configured default override, that name also is displayed.
router# showmicrocodeMicrocode images for downloadable hardware
HW Type Microcode image names
------------------------------------------
ecpa default slot0:xcpa26-0
configured slot0:xcpa26-2
pcpa default slot0:xcpa26-4
Related Commands
Command
Description
microcode(7000/7500)
Specifies where microcode should be loaded from on Cisco 7500/7000RSP routers.
microcode(7200)
Configures a default override for the microcode that is downloaded to the hardware on a Cisco 7200 series router.
show mls statistics
To display the Multilayer Switching (MLS) statistics for the Internet Protocol (IP), Internetwork Packet Exchange (IPX), multicast, Layer 2 protocol, and quality of service (QoS), use the
showmlsstatistics command in user EXEC or privileged EXEC mode.
showmlsstatistics
[ modulenum ]
Syntax Description
modulenum
(Optional) Displays the MLS statistics for a specific module.
Command Default
This command has no default settings.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.2(14)SX
Support for this command was introduced on the Supervisor Engine 720.
12.2(17b)SXA
This command was changed to include the
modulenum keyword and argument.
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
12.2(17d)SXB1
The output was changed to include total packets switched information.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The total packets switched performance displayed is the rate calculated as the average rate in a period within the last 30 seconds.
The ingress ACL denied packet count is displayed in the Total packets L3 Switched field and in the Total packets dropped by ACL field.
The RPF failed packet count is displayed in the Total packets L3 Switched field.
If the IP multicast source sends traffic to any multicast group that does not have an (*,G) entry present in the mroute table, the
showmlsstatistics command displays these packets as incrementing in the Total Mcast Packets Switched/Routed field. These packets are dropped in the hardware because there are no receivers for that group and no entry in the mroute table.
Examples
This example shows how to display the MLS statistics for all modules:
Router#
show mls statistics
Statistics for Earl in Module 2
L2 Forwarding Engine
Total packets Switched : 20273@ 22552 pps
L3 Forwarding Engine
Total Packets Bridged : 20273
Total Packets FIB Switched : 7864
Total Packets ACL Routed : 0
Total Packets Netflow Switched : 0
Total Mcast Packets Switched/Routed : 220598
Total ip packets with TOS changed : 0
Total ip packets with COS changed : 0
Total non ip packets COS changed : 0
Total packets dropped by ACL : 0
Total packets dropped by Policing : 705757744
Statistics for Earl in Module 9
L2 Forwarding Engine
Total packets Switched : 16683@ 1 pps
L3 Forwarding Engine
Total Packets Bridged : 0
Total Packets FIB Switched : 0
Total Packets ACL Routed : 0
Total Packets Netflow Switched : 0
Total Mcast Packets Switched/Routed : 0
Total ip packets with TOS changed : 0
Total ip packets with COS changed : 0
Total non ip packets COS changed : 0
Total packets dropped by ACL : 0
Total packets dropped by Policing : 277949053
Router#
This example shows how to display the MLS statistics for a specific module:
Router#
show mls statistics module 1
Statistics for Earl in Module 1
L2 Forwarding Engine
Total packets Switched : 2748166@ 22332 pps
>>
L3 Forwarding Engine
Total Packets Bridged : 92750@ 34 pps
Total Packets FIB Switched : 7
Total Packets ACL Routed : 0
Total Packets Netflow Switched : 0
Total Mcast Packets Switched/Routed : 3079200
Total ip packets with TOS changed : 0
Total ip packets with COS changed : 0
Total non ip packets COS changed : 0
Total packets dropped by ACL : 0
Total packets dropped by Policing : 0
Total Unicast RPF failed packets : 0
Errors
MAC/IP length inconsistencies : 0
Short IP packets received : 0
IP header checksum errors : 0
MAC/IPX length inconsistencies : 0
Short IPX packets received : 0
Router
#
Related Commands
Command
Description
showmlsasic
display the application-specific integrated circuit (ASIC) version
showmlsdf-table
Displays information about the DF table.
showmlsip
Displays the Multilayer Switching (MLS) IP information.
showmlsipx
Displays the Multilayer Switching (MLS) IPX information.
showmlsqos
Displays Multilayer Switching (MLS) quality of service (QoS) information
showmlsstatistics
Displays the Multilayer Switching (MLS) statistics for the Internet Protocol (IP)
show module
To display the module status and information, use the
show module command in user EXEC or
privileged EXEC mode.
showmodule
[ mod-num | all | provision | version ]
Syntax Description
mod-num
(Optional) Number of the module.
all
(Optional) Displays the information for all modules.
provision
(Optional) Displays the status about the module
provisioning.
version
(Optional) Displays the version information.
Command Default
This command has no default settings.
Command Modes
User EXEC Privileged EXEC
Command History
Release
Modification
12.2(14)SX
Support for this command was introduced on the Supervisor
Engine 720.
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was
extended to Release 12.2(17d)SXB.
12.2(33)SRA
This command was integrated into Cisco IOS Release
12.2(33)SRA.
Usage Guidelines
In the Mod Sub-Module fields, the
showmodule command displays the supervisor engine
number but appends the uplink daughter card’s module type and information.
Entering the
showmodule command with no arguments is the same as
entering the
showmoduleall command.
Examples
This example shows how to display information for all modules on a
Cisco 7600 series router that is configured with a Supervisor Engine 720:
Router#
show module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL0843557C
2 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-45AF SAL1109HZW9
3 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-45AF SAL1114KYZ7
4 48 48 port 10/100 mb RJ45 WS-X6348-RJ-45 SAL0543DGZ1
6 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL1016KASS
7 48 48-port 10/100 mb RJ45 WS-X6148-45AF SAL08321X1H
8 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL08528ADQ
9 48 48-port 100FX SFP Ethernet Module WS-X6148-FE-SFP SAD090208MB
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0012.005c.86e0 to 0012.005c.870f 2.1 12.2(14r)S5 12.2(33)SXH Ok
2 001b.0ce4.9fb0 to 001b.0ce4.9fdf 2.2 8.4(1) 8.7(0.22)SXH Ok
3 001b.534f.0540 to 001b.534f.056f 2.2 8.4(1) 8.7(0.22)SXH Ok
4 0007.4f6c.69f8 to 0007.4f6c.6a27 5.0 5.4(2) 8.7(0.22)SXH Ok
6 0017.9441.44cc to 0017.9441.44cf 5.2 8.4(2) 12.2(33)SXH Ok
7 0011.bb0e.c260 to 0011.bb0e.c28f 1.1 5.4(2) 8.7(0.22)SXH Ok
8 0012.da89.a43c to 0012.da89.a43f 2.0 12.2(14r)S5 12.2(33)SXH Ok
9 0030.f273.baf0 to 0030.f273.bb1f 3.0 8.4(1) 8.7(0.22)SXH Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Centralized Forwarding Card WS-F6700-CFC SAL08363HL6 2.0 Ok
2 IEEE Voice Daughter Card WS-F6K-48-AF SAL1108HRB1 2.3 Ok
3 IEEE Voice Daughter Card WS-F6K-48-AF SAL1114KV3P 2.3 Ok
4 Inline Power Module WS-F6K-VPWR 1.0 Ok
6 Policy Feature Card 3 WS-F6K-PFC3B SAL1015K00Q 2.3 Ok
6 MSFC3 Daughterboard WS-SUP720 SAL1016KBY3 2.5 Ok
7 IEEE Voice Daughter Card WS-F6K-FE48-AF SAL08311GGL 1.1 Ok
8 Centralized Forwarding Card WS-F6700-CFC SAL0902040K 2.0 Ok
Mod Online Diag Status
---- -------------------
1 Bypass
2 Bypass
3 Bypass
4 Bypass
6 Bypass
7 Bypass
8 Bypass
9 Bypass
Router#
This example shows how to display information for a specific module:
Router#
show module 2
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD0644030K
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
5 00e0.aabb.cc00 to 00e0.aabb.cc3f 1.0 12.2(2003012 12.2(2003012 Ok
Mod Sub-Module Model Serial Hw Status
--- --------------------------- --------------- --------------- ------- -------
5 Policy Feature Card 3 WS-F6K-PFC3 SAD0644031P 0.302 Ok
5 MSFC3 Daughtercard WS-SUP720 SAD06460172 0.701
Mod Online Diag Status
--- -------------------
5 Not Available
Router#
This example shows how to display version information:
(Optional) Displays all event trace messages in memory to the console.
component
(Optional) Name of the Cisco IOS software subsystem component that is the object of the event trace. To get a list of components that support event tracing in this release, use the
monitorevent-trace? command.
all
Displays all event trace messages currently in memory.
backmmm |
hhh:mm}
Specifies how far back from the current time you want to view messages. For example, you can gather messages from the last 30 minutes. The time argument is specified either in minutes or in hours and minutes format (mmm or hh:mm).
clockhh:mm
Displays event trace messages starting from a specific clock time in hours and minutes format (hh:mm).
date
(Optional) Day of the month.
month
(Optional) Displays the month of the year.
from-bootseconds
Displays event trace messages starting from a specified number of seconds after booting (uptime). To display the uptime, in seconds, enter the
showmonitorevent-tracecomponentfrom-boot? command.
latest
Displays only the event trace messages since the last
showmonitorevent-trace command was entered.
component
(Optional) Name of the Cisco IOS software subsystem component that is the object of the event trace. To get a list of components that support event tracing in this release, use the
monitorevent-trace? command.
parameters
Displays the trace parameters. The only parameter displayed is the size (number of trace messages) of the trace file.
detail
(Optional) Displays detailed trace information.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(18)S
This command was introduced.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S. The
showmonitorevent-tracecef comand replaced the
showcefeventsand
showipcefevents commands.
12.2(18)SXE
This command was integrated into Cisco IOS Release 12.2(18)SXE.
The
spa component keyword was added to support online insertion and removal (OIR) event messages for shared port adapters (SPAs).
The
bfd keyword was added for the
component argument to display trace messages relating to the Bidirectional Forwarding Detection (BFD) feature.
12.4(4)T
Support for the
bfd keyword was added for Cisco IOS Release 12.4(4)T.
12.0(31)S
Support for the
bfd keyword was added for Cisco IOS Release 12.0(31)S.
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.4(9)T
The
cfd keyword was added as an entry for the
component argument to display trace messages relating to crypto fault detection.
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.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
Use the
showmonitorevent-trace command to display trace message information.
The trace function is not locked while information is being 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-trace command will generate a message indicating that some messages might be lost; however, messages will continue to display on the console. If the number of lost messages is excessive, the
showmonitorevent-tracecommand will stop displaying messages.
Use the
bfd keyword for the
component argument to display trace messages relating to the BFD feature.
Use the
cfd keyword for the
component argument to display trace messages relating to the crypto fault detection feature. This keyword displays the contents of the error trace buffers in an encryption data path.
Examples
Examples
The following is sample output from the
showmonitorevent-tracecomponent command for the interprocess communication (IPC) component. Notice that each trace message is numbered and is followed by a time stamp (derived from the device uptime). Following the time stamp is the component-specific message data.
Use the
showmonitorevent-tracebfdallcommand to display logged messages for important BFD events in the recent past. The following trace messages show BFD session state changes:
Router# show monitor event-trace bfd all
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], event Session
create, state Unknown -> Fail
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Fail -> Down
(from LC)
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Down -> Init
(from LC)
3d03h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,1], state Init -> Up
(from LC)
3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], event Session
create, state Unknown -> Fail
3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], state Fail -> Down
(from LC)
3d07h: EVENT: Session [172.16.10.2,172.16.10.1,Fa6/0,2], state Down -> Up
(from LC)
To display trace information for all components configured for event tracing on the networking device, enter the
showmonitorevent-traceall-traces command. In this example, separate output is provided for each event, and message numbers are interleaved between the events.
The following is sample output from the
showmonitorevent-tracecomponentlatest command for the
spa component:
Router# show monitor event-trace spa latest
00:01:15.364: subslot 2/3: 4xOC3 POS SPA, TSM Event:inserted New state:wait_psm
_ready
spa type 0x440
00:02:02.308: subslot 2/0: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/0: not present, TSM Event:remove_complete New state:idle
00:02:02.308: subslot 2/1: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/1: not present, TSM Event:remove_complete New state:idle
00:02:02.308: subslot 2/2: not present, TSM Event:empty New state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.308: subslot 2/2: not present, TSM Event:remove_complete New state:idle
00:02:02.312: subslot 2/3: not present(plugin 4xOC3 POS SPA), TSM Event:empty New
state:remove
spa type 0x0, fail code 0x0(none)
00:02:02.312: subslot 2/3: not present, TSM Event:remove_complete New state:idle
Examples
If you select Cisco Express Forwarding as the component for which to display event messages, you can use the following additional arguments and keywords:
showmonitorevent-tracecef [events |
interface|ipv6 |
ipv4][all].
The following example shows the IPv6 or IPv4 events related to the Cisco Express Forwarding component. Each trace message is numbered and is followed by a time stamp (derived from the device uptime). Following the time stamp is the component-specific message data.
Router# show monitor event-trace cef ipv6 all
00:00:24.612: [Default] *::*/*'00 New FIB table [OK]
Router# show monitor event-trace cef ipv4 all
00:00:24.244: [Default] 127.0.0.81/32'01 FIB insert [OK]
In the following example, all event trace messages for the Cisco Express Forwarding component are displayed:
Router# show monitor event-trace cef events all
00:00:18.884: SubSys fib_ios_chain init
00:00:18.884: Inst unknown -> RP
00:00:24.584: SubSys fib init
00:00:24.592: SubSys fib_ios init
00:00:24.592: SubSys fib_ios_if init
00:00:24.596: SubSys ipv4fib init
00:00:24.608: SubSys ipv4fib_ios init
00:00:24.612: SubSys ipv6fib_ios init
00:00:24.620: Flag IPv4 CEF enabled set to yes
00:00:24.620: Flag 0x7BF6B62C set to yes
00:00:24.620: Flag IPv4 CEF switching enabled set to yes
00:00:24.624: GState CEF enabled
00:00:24.628: SubSys ipv4fib_les init
00:00:24.628: SubSys ipv4fib_pas init
00:00:24.632: SubSys ipv4fib_util init
00:00:25.304: Process Background created
00:00:25.304: Flag IPv4 CEF running set to yes
00:00:25.304: Process Background event loop enter
00:00:25.308: Flag IPv4 CEF switching running set to yes
The following example shows Cisco Express Forwarding interface events:
The following example shows the IPv4 events related to the Cisco Express Forwarding component. Each trace message is numbered and is followed by a time stamp (derived from the device uptime). Following the time stamp is the component-specific message data.
Router# show monitor event-trace cef ipv4 all
00:00:48.244: [Default] 127.0.0.81/32'01 FIB insert [OK]
In the following example, all event trace message for the Cisco Express Forwarding component are displayed:
Router# show monitor event-trace cef events all
00:00:18.884: SubSys fib_ios_chain init
00:00:18.884: Inst unknown -> RP
00:00:24.584: SubSys fib init
00:00:24.592: SubSys fib_ios init
00:00:24.592: SubSys fib_ios_if init
00:00:24.596: SubSys ipv4fib init
00:00:24.608: SubSys ipv4fib_ios init
00:00:24.620: Flag IPv4 CEF enabled set to yes
00:00:24.620: Flag 0x7BF6B62C set to yes
00:00:24.620: Flag IPv4 CEF switching enabled set to yes
00:00:24.624: GState CEF enabled
00:00:24.628: SubSys ipv4fib_les init
00:00:24.628: SubSys ipv4fib_pas init
00:00:24.632: SubSys ipv4fib_util init
00:00:25.304: Process Background created
00:00:25.304: Flag IPv4 CEF running set to yes
00:00:25.304: Process Background event loop enter
00:00:25.308: Flag IPv4 CEF switching running set to yes
The following examples show Cisco Express Forwarding interface events:
To troubleshoot errors in an encryption datapath, enter the
showmonitorevent-tracecfdallcommand.Inthisexample,eventsareshownseparately,eachbeginningwithatimestamp,followedbydatafromtheerrortracebuffer.CiscoTechnicalAssistenceCenter(TAC)engineerscanusethisinformationtodiagnosethecauseoftheerrors.
Note
If no packets have been dropped, this command does not display any output.