Table Of Contents
clear web-auth
commit
commit lda
configure
confreg
context
copy
copy tech-support
delete
dev
diagnostic start
diagnostic stop
dir—ROM monitor
dir—switch
disable
disconnect
clear web-auth
To clear the configuration of the login or the login fail page, use the clear web-auth command.
clear web-auth {login-page | login-fail-page}
Syntax Description
login-page
|
Clears the configuration of the login page.
|
login-fail-page
|
Clears the configuration of the login Fail page.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Examples
This example shows how to clear the configuration of the Login page:
Console> (enable) clear web-auth login-page
This example shows how to clear the configuration of the Login Fail page:
Console> (enable) clear web-auth login-fail-page
Related Commands
set port web-auth
set port web-auth initialize
set web-auth
set web-auth login-attempts
set web-auth login-fail-page
set web-auth login-page
set web-auth quiet-timeout
set web-auth session-timeout
show port web-auth
show web-auth summary
commit
To commit all ACEs or a specific ACE in NVRAM that has not been written to hardware, use the commit command.
commit qos acl {acl_name | all | adjacency}
commit security acl {acl_name | all | adjacency}
Syntax Description
qos acl
|
Specifies QoS ACEs.
|
acl_name
|
Name that identifies the VACL whose ACEs are to be committed.
|
all
|
Commits ACEs for all the ACLs.
|
adjacency
|
Commits adjacency table entries.
|
security acl
|
Specifies security ACEs.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Usage Guidelines
The commit command commits all ACEs in NVRAM that have not been written to hardware. Any committed ACL with no ACEs is deleted. We recommend that you enter ACEs in batches and enter the commit command to save all of them in hardware and NVRAM.
Examples
This example shows how to commit a specific QoS ACE to NVRAM:
Console> (enable) commit qos acl my_acl
Hardware programming in progress...
ACL my_acl is committed to hardware.
This example shows how to commit a specific security ACE to NVRAM:
Console> (enable) commit security acl IPACL2
ACL IPACL2 is committed to hardware.
This example shows how to commit an adjacency table entry to NVRAM:
Console> (enable) commit security acl adjacency
Commit operation in progress.
Adjacency successfully committed.
Related Commands
rollback
commit lda
To commit ASLB configuration that has not been written to hardware to NVRAM, use the commit lda command.
commit lda
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Examples
This example shows how to commit ASLB configuration to NVRAM:
Console> (enable) commit lda
Commit operation in progress...
Successfully committed Local Director Accelerator.
Related Commands
clear lda
set lda
show lda
configure
To download a configuration file from an rcp server or the network and execute each command in that file, use the configure command.
configure {host file}[rcp]
configure network
Syntax Description
host
|
IP address or IP alias of the host.
|
file
|
Name of the file.
|
rcp
|
(Optional) Specifies rcp as the file transfer method.
|
network
|
Specifies interactive prompting for the host and the file.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Usage Guidelines
Refer to the Catalyst 6500 Series Switch Software Configuration Guide on how to construct a configuration file to download using the configure command.
Following is a sample file called system5.cfg in the /tftpboot directory:
set ip alias conc7 198.133.219.207
set ip alias montreux 198.133.119.42
set ip alias cres 192.122.174.42
# empty string old password
Each line contains a command, except lines that begin with ! or #.
Examples
This example shows how to download the system5.cfg configuration file from the 192.122.174.42 host:
Console> (enable) configure 192.122.174.42 system5.cfg
Configure using system5.cfg from 192.122.174.42 (y/n) [n]? y
Done. Finished Network Download. (446 bytes)
Wed May 19 1999, 17:42:50
>> set ip alias conc7 198.133.219.207
>> set ip alias montreux 198.133.219.40
>> set ip alias cres 192.122.174.42
Enter new password: pingpong
Retype new password: pingpong
Related Commands
copy
show config
confreg
To configure the configuration register utility, use the confreg command.
confreg [num]
Syntax Description
num
|
(Optional) Valid values are 0 = ROM monitor, 1 = boot helper image, and 2 to 15 = boot system.
|
Defaults
This command has no default settings.
Command Types
ROM monitor command.
Command Modes
Normal.
Usage Guidelines
Executed with the confreg argument num, the VCR changes to match the number specified.
Without the argument, confreg dumps the contents of the VCR in English and allows you to alter the contents.
You are prompted to change or keep the information held in each bit of the VCR. In either case, the new VCR value is written into NVRAM and does not take effect until you reset or power cycle the platform.
You must issue a sync command to save your change. Otherwise, the change is not saved and a reset removes your change.
Examples
This example shows how to use the confreg command:
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]: y
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netboot fails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect"? y/n [n]:
enable "ignore system config info"? y/n [n]:
change console baud rate? y/n [n]: y
enter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400 [0]: 0
change the boot characteristics? y/n [n]: y
1 = the boot helper image
do you wish to change the configuration? y/n [n]:
You must reset or power cycle for new config to take effect
Related Commands
show boot
context
To display the context of a loaded image, use the context command.
context
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Types
ROM monitor command.
Command Modes
Normal.
Usage Guidelines
The context from the kernel mode and process mode of a booted image are displayed, if available.
Examples
This example shows how to display the context of a loaded image:
Reg MSW LSW | Reg MSW LSW
------ ---------- ---------- | ----- ---------- ----------
zero : 00000000 00000000 | s0 : 00000000 34008301
AT : 00000000 3e800000 | s1 : 00000000 00000001
v0 : 00000000 00000003 | s2 : 00000000 00000003
v1 : 00000000 00000000 | s3 : 00000000 00000000
a0 : 00000000 0000002b | s4 : 00000000 60276af8
a1 : 00000000 00000003 | s5 : ffffffff ffffffff
a2 : 00000000 00000000 | s6 : 00000000 60276c58
a3 : 00000000 60276af8 | s7 : 00000000 0000000a
t0 : 00000000 00000b84 | t8 : 00000000 34008300
t1 : 00000000 3e800004 | t9 : ffffffff ac000000
t2 : 00000000 00000239 | k0 : 00000000 00000400
t3 : 00000000 34008301 | k1 : 00000000 6024eb5c
t4 : ffffffff ffff83fd | gp : 00000000 60252920
t5 : 00000000 0000003f | sp : 00000000 60276a98
t6 : 00000000 00000000 | s8 : 00000000 601fbf33
t7 : ffffffff ffffffff | ra : 00000000 6006d380
HI : 00000000 00000008 | LO : 00000000 00000000
EPC : 00000000 60033054 | ErrPC : ffffffff bfc070c8
Stat : 34408302 | Cause : 00002020
Reg MSW LSW | Reg MSW LSW
------ ---------- ---------- | ----- ---------- ----------
zero : 00000000 00000000 | s0 : 00000000 00000074
AT : 00000000 3e820000 | s1 : 00000000 60276c58
v0 : 00000000 00000081 | s2 : 00000000 601fbac0
v1 : 00000000 00000074 | s3 : 00000000 00000036
a0 : 00000000 00000400 | s4 : 00000000 0000000f
a1 : 00000000 60276c58 | s5 : ffffffff ffffffff
a2 : 00000000 00000074 | s6 : 00000000 60276c58
a3 : 00000000 00000000 | s7 : 00000000 0000000a
t0 : 00000000 00000400 | t8 : 00000000 34008300
t1 : 00000000 00000400 | t9 : ffffffff ac000000
t2 : 00000000 00000000 | k0 : 00000000 30408401
t3 : ffffffff ffff00ff | k1 : 00000000 30410000
t4 : 00000000 600dcc10 | gp : 00000000 60252920
t5 : 00000000 0000003f | sp : ffffffff 80007ce8
t6 : 00000000 00000000 | s8 : 00000000 601fbf33
t7 : ffffffff ffffffff | ra : 00000000 600dfd20
HI : 00000000 00000008 | LO : 00000000 00000000
EPC : 00000000 600dfd38 | ErrPC : ffffffff ffffffff
Stat : 34008303 | Cause : ffffffff
copy
To upload or download a flash image or a switch configuration to or from a flash device, rcp server, TFTP server, or an SCP server, use the copy command.
copy file-id {tftp | rcp | flash | file-id | config}
copy tftp {flash | file-id | config}
copy rcp {flash | file-id | config}
copy flash {tftp | rcp | file-id | config}
copy config {flash | file-id | tftp | rcp} [all]
copy acl config {flash | file-id | tftp | rcp}
copy cfg1 {tftp | rcp | flash | config | cfg2} [all]
copy cfg2 {tftp | rcp | flash | config | cfg1} [all]
copy ftp {flash | file-id | config}
copy scp destination
copy source scp
copy log-cmd {flash | ftp | rcp | scp | tftp | file-id}
copy sftp destination
copy source sftp
Syntax Description
file-id
|
Format used to specify the file on the flash device, where the format is m/device:filename. m/ = Option that gives access to different modules, such as the standby supervisor engine or an Ethernet module. device: = Device where the flash resides. filename = Name of the configuration file.
|
tftp
|
Allows you to copy to or from a TFTP server.
|
rcp
|
Specifies the file be copied to or from an rcp server.
|
flash
|
Supports downloading of multiple modules.
|
config
|
Allows you to copy the configuration to flash memory, another flash device, or a file on a TFTP server.
|
acl config
|
Copies the ACL configuration manually to a file. See the "Usage Guidelines" section before using this command.
|
cfg1
|
Specifies the first startup configuration file on the supervisor engine.
|
cfg2
|
Specifies the second startup configuration file on the supervisor engine.
|
all
|
(Optional) Specifies that the entire configuration be copied to the specified destination configuration file.
|
ftp
|
Allows you to copy to or from an FTP server.
|
scp destination
|
Copies a file by using Secure Copy (SCP) to a specified destination on the system.
|
source scp
|
Copies a file by using SCP from a specified source on the system.
|
log-cmd
|
Copies command log to a specified device.
|
scp
|
Specifies SCP for secure images.
|
sftp destination
|
Copies a file by using Secure File Transfer Protocol (SFTP) to a specified destination on the system.
|
source sftp
|
Copies a file by using SFTP from a specified source on the system.
|
Defaults
If a source or destination device is not given, the one specified by the cd command is used. If a destination filename is omitted, the source filename is used.
Command Types
Switch command.
Command Modes
Privileged.
Usage Guidelines
Use the copy command to perform these tasks:
•
Download a system image or configuration file from a TFTP or rcp server to a flash device.
•
Upload a system image or configuration file from a flash device to a TFTP or rcp server.
•
Configure the switch using a configuration file on a flash device or on a TFTP or rcp server.
•
Copy the current configuration to a flash device or to a TFTP or rcp server.
•
Manually copy the ACL configuration to a file.
•
Upload command log entries to a flash device or to a TFTP or rcp server.
Caution 
Manual copying can only be used if
acl config is set to
flash and you enable the
auto-config append option. If you disable the
append option, the configuration clears before executing the auto-config file; see the
set boot config-register auto-config command.
If you do not specify the source or destination device, the command uses the ones specified by the cd command. If you omit the destination filename, the source filename is used.
The copy config, copy cfg1, and copy cfg2 commands copy only nondefault commands to the destination configuration file. Use the keyword all to copy both default and nondefault configurations.
If you do not specify a source or destination flash device, the default flash device (specified by the cd command) is used. Use the pwd command to display the current default flash device. If you omit the destination filename, the system uses the source filename.
The system stores image and configuration files in the sysname.cfg file when you define a system name using the set system name command; otherwise, it uses the default myswitch.cfg file.
A colon (:) is required after the specified device.
If you use the flash keyword as the copy source or destination, you are prompted for the flash device name.
If you are copying a software image to multiple intelligent switching modules of the same type, use the flash keyword as the copy destination. The switch automatically determines which modules to copy the image to based on the header in the source image file. If you want to copy a software image to a single intelligent switching module in a switch with multiple modules of the same type, you must specify the destination file-id as m/bootflash: (do not specify a filename).
Before you begin downloading a software image using SCP, make sure of the following:
•
Ensure that the workstation acting as the SCP server supports the Secure Shell (SSH).
•
Ensure that the server supports a command shell that has an SSH v1-compatible scp command available.
•
Ensure that the switch has a route to the SCP server. The switch and the SCP server must be in the same subnetwork if you do not have a router to route traffic between subnets. Check connectivity to the SCP server using the ping command.
•
A power interruption (or other problem) during the download procedure can corrupt the flash code. If the flash code is corrupted, you can connect to the switch through the console port and boot from an uncorrupted system image on a flash PC card.
Before you attempt to upload a software image to an SCP server, do the following:
•
Ensure that the workstation acting as the SCP server is configured properly.
•
Ensure that the switch has a route to the SCP server. The switch and the SCP server must be in the same subnetwork if you do not have a router to route traffic between subnets. Check connectivity to the rcp server using the ping command.
•
If you are overwriting an existing file (including an empty file, if you had to create one), ensure that the permissions on the file are set correctly. Permissions on the file should be set to write for the specific username.
For more information about downloading and uploading files by using SCP, refer to Chapter 25, "Working with System Software Images," in the Catalyst 6500 Series Switch Software Configuration Guide.
The Secure File Transfer Protocol (SFTP) is available only in crypto images.
SFTP uses the SSH protocol for establishing a secure channel between the client and the server. SFTP is supported only with SSHv2. SFTP with SSHv1 is not supported.
SFTP client functionality is supported. SFTP server functionality is not supported.
Examples
This example shows how to use the copy command to upload the switch configuration to a file named cat.cfg on the slot0 flash device:
Console> (enable) copy config slot0:cat.cfg
Upload configuration to slot0:cat.cfg
649324 bytes available on device slot0, proceed (y/n) [n]? y
Configuration has been copied successfully. (10200 bytes)
This example shows how to use the copy command to upload the switch configuration to a file named lab2.cfg on the TFTP server:
Console> (enable) copy config tftp:lab2.cfg
IP address or name of remote host [172.20.22.7]? y
Upload configuration to tftp:lab2.cfg (y/n) [n]? y
Configuration has been copied successfully. (10299 bytes).
This example shows how to use the copy command to upload the switch configuration to the cat.cfg file on the slot0 flash device:
Console> (enable) copy config flash
Flash device [bootflash]? slot0:
Name of file to copy to [test_image]? cat.cfg
Upload configuration to slot0:cat.cfg
749124 bytes available on device slot0, proceed (y/n) [n]? y
Configuration has been copied successfully. (200345 bytes).
These examples show how to use the copy command to download a configuration from a TFTP server:
Console> (enable) copy slot0:cat.cfg config
Configure using slot0:cat.cfg (y/n) [n]? y
Finished download. (10900 bytes)
>> set password $1$FMFQ$HfZR5DUszVHIRhrz4h6V70
>> set enablepass $1$FMFQ$HfZR5DUszVHIRhrz4h6V70
Console> (enable) copy tftp config
IP address or name of remote host? 172.20.22.7
Name of configuration file? cat.cfg
Configure using cat.cfg from 172.20.22.7 (y/n) [n]? y
Finished network download. (10900 bytes)
>> set password $1$FMFQ$HfZR5DUszVHIRhrz4h6V70
>> set enablepass $1$FMFQ$HfZR5DUszVHIRhrz4h6V70
Console> (enable) copy flash config
Flash device [bootflash]?
Name of configuration file? test.cfg
Configure using bootflash:test.cfg (y/n) [n]? y
Finished download. (10900 bytes)
>> set password $1$FMFQ$HfZR5DUszVHIRhrz4h6V70
>> set enablepass $1$FMFQ$HfZR5DUszVHIRhrz4h6V70
This example shows how to copy the running configuration to an rcp server for storage:
Console> (enable) copy config rcp
IP address or name of remote host []? 172.20.52.3
Name of file to copy to []? cat6000_config.cfg
Upload configuration to rcp:cat6000_config.cfg, (y/n) [n]? y
Configuration has been copied successfully.
This example shows how to configure a Catalyst 6500 series switch using a configuration file downloaded from an rcp server:
Console> (enable) copy rcp config
IP address or name of remote host []? 172.20.52.3
Name of file to copy from []? dns-config.cfg
Configure using rcp:dns-config.cfg (y/n) [n]? y
Finished network download. (134 bytes)
>> set ip dns server 172.16.10.70 primary
172.16.10.70 added to DNS server table as primary server.
>> set ip dns server 172.16.10.140
172.16.10.140 added to DNS server table as backup server.
>> set ip dns domain corp.com
Default DNS domain name set to corp.com
This example shows how to upload an image from a remote host into flash using an rcp server:
Console> (enable) copy rcp flash
IP address or name of remote host []? 172.20.52.3
Name of file to copy from []? cat6000-sup-d.6-1-1.bin
Flash device [bootflash]?
Name of file to copy to [cat6000-sup-d.6-1-1.bin]?
4369664 bytes available on device bootflash, proceed (y/n) [n]? y
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File has been copied successfully.
This example shows how to download a configuration to the first startup configuration file (cfg1) on a supervisor engine:
Console> (enable) copy tftp cfg1
IP address or name of remote host [172.20.32.10]?
Name of file to copy from [/tftpboot/my.cfg]?
Download config file from /tftpboot/my.cfg to cfg1 (y/n) [n]?
File has been copied to cfg1.
This example shows how to copy the ACL configuration to a bootflash file manually:
Console> (enable) copy acl config bootflash:switchapp.cfg
Upload configuration to bootflash:dan.cfg
2843644 bytes available on device bootflash, proceed (y/n) [n]? y
Configuration has been copied successfully.
This example shows a complete SCP download procedure of a crypto image to the switch:
Console> (enable) copy scp flash
IP address or name of remote host []? 172.20.52.3
Name of file to copy from []? cat6000-sup720cvk9.8-3-1.bin
Flash device [bootflash]?
Name of file to copy to [cat6000-sup720cvk9.8-3-1.bin]?
4369664 bytes available on device bootflash, proceed (y/n) [n]? y
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File has been copied successfully.
Console> (enable) set boot system flash bootflash:cat6000-sup720cvk9.8-3-1.bin prepend
BOOT variable =
bootflash:cat6000-sup720cvk9.8-3-1.bin,1;bootflash:cat6000-sup720cvk9.8-3-1.bin
Console> (enable) reset system
This command will reset the system.
Do you want to continue (y/n) [n]? y
Console> (enable) 11/25/2003,13:51:39:SYS-5:System reset from Console//
System Bootstrap, Version 4.2
Copyright (c) 1994-2003 by cisco Systems, Inc.
Presto processor with 32768 Kbytes of main memory
Autoboot executing command: "boot bootflash:cat6000-sup720cvk9.8-3-1.bin"
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Uncompressing file: ###########################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
################################################################################
System Power On Diagnostics
DRAM Size ....................32 MB
Testing DRAM..................Passed
Verifying Text segment .......Passed
NVRAM Size ...................512 KB
Saving NVRAM .................
Testing NVRAM ................Passed
Restoring NVRAM...............
Level2 Cache ..................Present
Level2 Cache test..............Passed
Boot image: cat6000-sup720cvk9.8-3-1.bin
Flash Size = 0X1000000, num_flash_sectors = 64
readCafe2Version: 0x00000001
RIn Local Test Mode, Pinnacle Synch Retries: 2
Running System Diagnostics from this Supervisor (Module 1)
This may take up to 2 minutes....please wait
11/25/2003,13:52:51:SYS-5:Module 1 is online
11/25/2003,13:53:11:SYS-5:Module 4 is online
11/25/2003,13:53:11:SYS-5:Module 5 is online
11/25/2003,13:53:14:PAGP-5:Port 1/1 joined bridge port 1/1.
11/25/2003,13:53:14:PAGP-5:Port 1/2 joined bridge port 1/2.
11/25/2003,13:53:40:SYS-5:Module 2 is online
11/25/2003,13:53:45:SYS-5:Module 3 is online
This example shows how to upload the crypto image to an SCP server:
Console> (enable) copy bootflash scp
Flash device [bootflash]? slot0:
Name of file to copy from []? cat6000-sup720cvk9.8-3-1.bin
IP address or name of remote host [172.20.52.3]? 172.20.52.10
Name of file to copy to [cat6000-sup720cvk9.8-3-1.bin]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC|
File has been copied successfully.
Related Commands
clear ftp
configure
reset—switch
set boot config-register
set boot config-register auto-config
set boot system flash
set ftp
show ftp
write
copy tech-support
To copy the output of the show tech-support command to the target device (ftp or tftp or file-id), use the copy tech-support command.
copy tech-support {ftp | tftp | file-id}
Syntax Description
ftp
|
Allows you to copy to an FTP server.
|
tftp
|
Allows you to copy to a TFTP server.
|
file-id
|
Specifies the file identifier. The format used to specify the file on the flash device is m/device:filename. m/ indicates the option that gives access to different modules, such as the standby supervisor engine or an Ethernet module. device: indicates the device where the flash resides. filename indicates the name of the configuration file.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Examples
This example shows how to copy the output of the show tech-support command to an FTP server:
Console> (enable) copy tech-support ftp
IP address or name of remote host []? 10.77.11.190
Username for ftp[anonymous]? cat6k
Password for User cat6k[ ]:
Name of file to copy to [/tftp/bodc-cat6k/cat/cc]?
Upload tech-support to ftp:/tftp/bodc-cat6k/cat/cc (y/n) [n]? y
Writing /tftp/bodc-cat6k/cat/cc
!!!!!!!!!!!!!!!!!!!!!!!!!!
Tech-support has been copied successfully.
This example shows how to copy the output of the show tech-support command to a TFTP server:
Console> (enable) copy tech-support tftp
IP address or name of remote host [ ]? 10.77.11.190
Name of file to copy to [ ]? /tftp/bodc-cat6k/cat/cc
Upload tech-support to tftp:/tftp/bodc-cat6k/cat/cc (y/n) [n]? y
Tech-support has been copied successfully.
This example shows how to copy the output of the show tech-support command to the filename techsupport:
Console> (enable) copy tech-support 6/bootdisk:techsupport
Upload tech-support to bootdisk:techsupport
232480768 bytes available on device bootdisk, proceed (y/n) [n]? y
Tech-support has been copied successfully.
Related Commands
show tech-support
delete
To delete a configuration file, use the delete command.
delete [[m/]device:]filename
Syntax Description
m/
|
(Optional) Module number of the supervisor engine containing the flash device.
|
device:
|
(Optional) Device where the flash resides.
|
filename
|
Name of the configuration file.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Usage Guidelines
A colon (:) is required after the specified device.
Examples
This example shows how to delete the cat6000-sup-d.5-5-1.bin configuration file from the flash device and then verify the deletion by entering the show flash command:
Console> (enable) delete bootflash:cat6000-sup-d.5-5-1.bin
Console> (enable) show flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D ffffffff 5415406e 3300b8 25 3080247 Jan 12 2000 13:22:46
cat6000-sup-d.6-1-1.bin
2 .. ffffffff 762950d6 6234d0 25 3093399 Jan 13 2000 12:33:14
cat6000-sup-d.6-1-1.bin
1428272 bytes available (6173904 bytes used)
Related Commands
dir—switch
show flash
squeeze
undelete
dev
To list the device IDs available on a switch, use the dev command.
dev
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Types
ROM monitor command.
Command Modes
Normal.
Examples
This example shows how to use the dev command:
diagnostic start
To start running a specific test based on test ID numbers, use the diagnostic start command.
diagnostic start module mod_num test {all | test_ID_num | test_list | complete | minimal |
non-disruptive | per-port} [port {all | port_num | port_list}]
Syntax Description
module mod_num
|
Specifies the module on which to start running specific tests.
|
test
|
Specifies particular online diagnostic tests.
|
all
|
Species all online diagnostic tests.
|
test_ID_num
|
Number of a specific online diagnostic test.
|
test_list
|
List of online diagnostic tests.
|
complete
|
Starts complete set of bootup diagnostic tests.
|
minimal
|
Starts minimal set of bootup diagnostic tests.
|
non-disruptive
|
Starts nondisruptive set of diagnostic tests.
|
per-port
|
Starts a per-port set of diagnostic tests.
|
port
|
Specifies port selection.
|
all
|
Specifies all ports on the module.
|
port_num
|
Number of a port.
|
port_list
|
Range of ports.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Normal.
Usage Guidelines
The diagnostic start command accepts one test ID, a range of test IDs, a subgroup of tests, or all for all tests. The test ID for a particular test can be different from one module type to another module type or even from one software release to another software release. You need to obtain the correct test ID and relevant test name using by the show diagnostic content command.
To configure generic online diagnostics, use the set commands in the "Related Commands" section.
Note
GOLD is supported on the Supervisor Engine 720 and the Supervisor Engine 32 only. Earlier diagnostic commands are still supported on the Supervisor Engine 1 and the Supervisor Engine 2.
Examples
This example shows how to start online diagnostic test 1 on module 5:
Console> diagnostic start module 5 test 1
2005 Aug 18 15:10:08 %DIAG-6-TEST_RUNNING:Module 5: Running FirmwareDiagStatus{ID=1} ...
2005 Aug 18 15:10:08 %DIAG-6-TEST_OK:Module 5: FirmwareDiagStatus{ID=1} has completed
successfully
Related Commands
clear diagnostic
set diagnostic bootup level
set diagnostic diagfail-action
set diagnostic event-log size
set diagnostic monitor
set diagnostic ondemand
set diagnostic schedule
show diagnostic
diagnostic stop
To stop running generic online diagnostics on a specified module, use the diagnostic stop command.
diagnostic stop module mod_num
Syntax Description
module mod_num
|
Specifies the module on which to stop running specific tests.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Normal.
Usage Guidelines
Because some memory tests might take hours to complete, if you want to stop them before they conclude, use this command.
Note
GOLD is supported on the Supervisor Engine 720 and the Supervisor Engine 32 only. Earlier diagnostic commands are still supported on the Supervisor Engine 1 and the Supervisor Engine 2.
Examples
This example shows the output when you enter the diagnostic stop command, but no test is running:
Console> diagnostic stop module 5
Diagnostic[Module 5]: Diagnostic is not active.
2005 Aug 18 15:38:30 %DIAG-3-NO_DIAG_RUNNING:Module 5: Diagnostic is not running
Related Commands
clear diagnostic
set diagnostic bootup level
set diagnostic diagfail-action
set diagnostic event-log size
set diagnostic monitor
set diagnostic ondemand
set diagnostic schedule
show diagnostic
dir—ROM monitor
To list the files of the named device, use the dir command.
dir device
Syntax Description
Defaults
This command has no default settings.
Command Types
ROM monitor command.
Command Modes
Normal.
Examples
This example shows how to use the dir command:
File size Checksum File name
65 bytes (0x41) 0xb49d clev/oddfile65
2229799 bytes (0x220627) 0x469e clev/sierra-k.Z
dir—switch
To display a list of files on a flash memory device, use the dir command.
dir [[m/]device:][filename] [all | deleted | long]
Syntax Description
m/
|
(Optional) Module number of the supervisor engine containing the flash device.
|
device:
|
(Optional) Device where the flash resides.
|
filename
|
(Optional) Name of the configuration file.
|
all
|
(Optional) Displays all files, deleted or not.
|
deleted
|
(Optional) Displays only deleted files.
|
long
|
(Optional) Displays files that have not been deleted, in long format.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Normal and privileged.
Usage Guidelines
A colon (:) is required after the specified device.
When you specify the all keyword, the file information is displayed in long format.
When you omit all keywords (all, deleted, or long), the system displays file information in short format. Short format is shown in Table 2-11.
Table 2-11 Short Format
Column Heading
|
Description
|
#
|
File index number
|
length
|
File length
|
date/time
|
Date and time the file was created
|
name
|
Filename
|
When you use one of the keywords (all, deleted, or long), the system displays file information in long format. The long format is shown in Table 2-12.
Table 2-12 Long Format
Column Heading
|
Description
|
#
|
File index number
|
ED
|
Letter to indicate whether the file contains an error (E) or is deleted (D)
|
type
|
File type (1 = configuration file, 2 = image file); when the file type is unknown, the system displays a zero or FFFFFFFF in this field
|
crc
|
File cyclic redundancy check
|
seek
|
Offset into the file system of the next file
|
nlen
|
Filename length
|
length
|
File length
|
date/time
|
Date and time the file was created
|
name
|
Filename
|
Examples
This example shows how to display the file information in short format:
-#- -length- -----date/time------ name
1 6061822 Mar 03 2000 15:42:49 cat6000-sup.6-1-1.bin
2 6165044 Mar 13 2000 14:40:15 cat6000-sup.5-5-1.bin
3763660 bytes available (12227124 bytes used)
This example shows how to display the file information in long format:
Console> (enable) dir long
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. ffffffff f3a3e7c1 607f80 24 6061822 Mar 03 2000 15:42:49 cat6000-sup.
2 .. ffffffff aa825ac6 be9234 24 6165044 Mar 13 2000 14:40:15 cat6000-sup.
3763660 bytes available (12227124 bytes used)
Related Commands
show flash
disable
To return to normal mode from privileged mode, use the disable command.
disable
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Examples
This example shows how to return to normal mode:
Console> (enable) disable
Related Commands
enable
disconnect
To close a session by session ID number, use the disconnect command.
disconnect session_id
Syntax Description
session_id
|
Number of the session.
|
Defaults
This command has no default settings.
Command Types
Switch command.
Command Modes
Privileged.
Usage Guidelines
To identify session ID numbers, enter the show users command.
Examples
This example shows how to close a session by entering the session ID number:
Console> (enable) disconnect 2
Telnet session from cbin3-view2.cisco.com disconnected.
Related Commands
show users
telnet