Appends a file on a PCMCIA flash card to the end of another file.

EXAMPLE:

BigServerIron# append newacls.cfg startup-config.cfg

This command appends a file called “newacls.cfg” to the end of a file called “startup-config.cfg” file. This example assumes that both files are present on the PCMCIA slot and in the subdirectory level that currently have the management focus.

The following command appends a file in the current subdirectory to the end of a file in another subdirectory:

BigServerIron# append newacls.cfg \TEST\startup-config.cfg

Syntax: append [<from-card> <to-card>] [\<from-dir-path>\]<from-name> [\<to-dir-path>\]<to-name>

The <from-card> and <to-card> parameters specify the source and destination flash cards when you are appending a file on one flash card to a file located on another flash card.

The [\<from-dir-path>\]<from-name> parameter specifies the file you are adding to the end of another file. If the file is not located in the current subdirectory (the subdirectory that currently has the management focus), specify the subdirectory path in front of the file name.

The [\<to-dir-path>\]<to-name> parameter specifies the file to which you are appending the other file. If the file is not located in the current subdirectory, specify the subdirectory path in front of the file name.

Possible values: See above

Default value: N/A

Changes the read-write attribute of a file on a flash card in a Management IV module’s PCMCIA slot.

The read-write attribute specifies whether a file on a flash card can be changed or deleted.

• Read-only – You can display or copy the file but you cannot replace (copy over) or delete the file.

• Read-write – You can replace (copy over) or delete the file. This is the default.

Use the following method to change the read-write attribute of a file.

EXAMPLE:

To protect a file from accidental changes by changing the read-write attribute from read-write to read-only, enter a command such as the following:

BigServerIron# attrib ro goodcfg.cfg

Syntax: attrib [slot1 | slot2] ro | rw <file-name>

To determine the read-write attribute of a file, use the dir command to list the directory information for the file. Files set to read-only are listed with “R” in front of the file name. See "dir" .

To change all files on a flash card to read-only, enter a command such as the following:

BigServerIron# attrib ro *.*

This command changes the read-write attribute for all files on the flash card that currently has the management focus to read-only.

Possible values: See above.

Default value: rw (read-write)

Initiates a system boot from a BootP server. You can specify the preferred initial boot source and boot sequence in the startup-config file. If upon boot, the user-specified boot source and sequence fails, then by default, the ServerIron will attempt to load the software image from a different source. The following sources will be tried one at a time, in the order noted, until a software load is successful.

• flash primary

• flash secondary

• TFTP

• BootP

If the image does not load successfully from the above sources, you are prompted to enter alternative locations from which to load an image:

• boot system bootp

• boot system flash primary

• boot system flash secondary

• boot system tftp

EXAMPLE:

ServerIron# boot system bootp

Syntax: boot system bootp

Possible values: N/A

Default value: N/A

Initiates a system boot from the primary software image stored in flash.

EXAMPLE:

ServerIron(config)# boot system flash primary

Syntax: boot system flash primary

Possible values: N/A

Default value: N/A

Initiates a system boot from the secondary software image stored in flash.

EXAMPLE:

ServerIron(config)# boot system flash secondary

Syntax: boot system flash secondary

Possible values: N/A

Default value: N/A

Initiates a system boot from an image file on a PCMCIA flash card.

EXAMPLE:

To reboot the device using a software image file on the flash card, enter a command such as the following at the Privileged Exec level of the CLI:

BigServerIron# boot system slot1 BSI07101.bin

The command in this example reboots the device using the image file BSI07101.bin located on the PCMCIA flash card in slot 1. This example assumes the image file is in the root directory on the flash card. If the image file is in a subdirectory, specify the subdirectory path. For example, to boot using an image in a subdirectory called “BSI”, enter command such as the following:

BigServerIron# boot system slot1 \BSI\BSI07101.bin

Syntax: boot system slot1 | slot2 [\<dir-path>\]<file-name>

The slot1 | slot2 parameter indicates the flash card slot.

The <file-name> parameter specifies the file name. If the file is in a subdirectory, specify the subdirectory path in front of the file name. If the file name you specify is not a full path name, the CLI assumes that the name (and path, if applicable) you enter are relative to the subdirectory that currently has the management focus.

Possible values: See above

Default value: N/A

Initiates a system boot of the software image from a TFTP server.

EXAMPLE:

ServerIron(config)# boot system tftp 192.22.33.44 current.img

Syntax: boot system tftp <ip-addr> <filename>

Possible values: N/A

Default value: N/A

Before entering the TFTP boot command, you must first assign an IP address, IP mask and default gateway (if applicable) at the boot prompt as shown.

EXAMPLE:

boot> ip address 192.22.33.44 255.255.255.0

boot> ip default-gateway 192.22.33.1

You now can proceed with the boot system tftp... command.

Another form of the chdir command. See "chdir" .

Switches the management focus from one flash card in a Management IV module’s PCMCIA slot to the other slot.

The effect of file management commands depends on the flash card that has the management focus. For example, if you enter a command to delete a file, the software deletes the specified file from the flash card that currently has the management focus.

EXAMPLE:

To switch the focus of the CLI from one flash card to the other, enter a command such as the following:

BigServerIron# cd slot2
BigServerIron#

Syntax: cd | chdir slot1 | slot2

Syntax: cd | chdir <dir-name>

When you enter the cd command, the software changes the management focus to the slot or subdirectory path you specify, then displays a new command prompt.

If a slot you specify does not contain a flash card, the software displays the message shown in the following example.

BigServerIron# cd slot2
The system can not find the drive specified

To switch the management focus to a different subdirectory, enter a commands such as the following:

BigServerIron# cd PLOOK
Current directory of slot1 is: \PLOOK

This command changes the focus from the root directory level ( \) to the subdirectory named “PLOOK”.

If you specify an invalid subdirectory path, the CLI displays a message such as the following:

BigServerIron# cd PLOOK
Path not found

If you are certain the path you specified exists, make sure you are at the correct level for reaching the path. For example, if you are already at the PLOOK level, the CLI cannot find the subdirectory “\PLOOK” because it is not a subdirectory from the level that currently has the management focus.

Possible values: N/A

Default value: N/A

Removes all data from the ARP cache.

EXAMPLE:

ServerIron# clear arp

The following command clears all ARP entries for port 2 on the module in slot 3.

ServerIron# clear arp ethernet 3/2

Syntax: clear arp [ethernet <num> | mac-address <xxxx.xxxx.xxxx> [<mask>] | <ip-addr> [<ip-mask>]]

Specify the MAC address mask as “f”s and “0”s, where “f”s are significant bits. Specify IP address masks in standard decimal mask format (for example, 255.255.0.0).

Possible values: N/A

Default value: N/A

Clears DNS selection counters globally or per zone, without reloading the software. Use this procedure when you want to clear out any DNS requests for any client.

EXAMPLE:

SLB-ServerIron# clear gslb dns zone zone1

Syntax: clear gslb dns zone [zone-name]

Possible values:

[zone-name] is the zone for which you want to clear the DNS selection counters

To clear the counters globally (for all zones), do not enter a zone name.

Default value: N/A

Clears health-check policy statistics.

EXAMPLE:

ServerIron(config)# clear healthck statistics

Syntax: clear healthck statistics

Possible values: N/A

Default value: N/A

Removes all entries from the IP cache.

EXAMPLE:

ServerIron# clear ip cache

Syntax: clear ip cache

Possible values: N/A

Default value: N/A

Clears entries from the NAT table. The software provides the following clear options:

• Clear all entries (static and dynamic)

• Clear an entry for a specific NAT entry based on the private and global IP addresses

• Clear an entry for a specific NAT entry based on the IP addresses and the TCP or UDP port number. Use this option when you are trying to clear specific entries created using the Port Address Translation feature.

EXAMPLE:

To clear all dynamic entries from the NAT translation table, enter the following command at the Privileged EXEC level of the CLI:

ServerIron# clear ip nat all

Syntax: clear ip nat all

To clear only the entries for a specific address entry, enter a command such as the following:

ServerIron# clear ip nat inside 209.157.1.43 10.10.10.5

This command clears the inside NAT entry that maps private address 10.10.10.5 to Internet address 209.157.1.43. Here is the syntax for this form of the command.

Syntax: clear ip nat inside <global-ip> <private-ip>

If you use Port Address Translation, you can selectively clear entries based on the TCP or UDP port number assigned to an entry by the feature. For example, the following command clears one of the entries associated with Internet address 209.157.1.44 but does not clear other entries associated with the same address.

ServerIron# clear ip nat inside 209.157.1.43 1081 10.10.10.5 80

The command above clears all inside NAT entries that match the specified global IP address, private IP address, and TCP or UDP ports.

Syntax: clear ip nat <protocol> inside <global-ip> <internet-tcp/udp-port> <private-ip> <private-tcp/udp-port>

The <protocol> parameter specifies the protocol type and can be tcp or udp.

Possible values: N/A

Default value: N/A

Clears the IP traffic statistics.

EXAMPLE:

ServerIron# clear ip traffic

Syntax: clear ip traffic

Possible values: N/A

Default value: N/A

Removes all entries from the SNMP event log.

EXAMPLE:

ServerIron# clear logging

Syntax: clear logging

Possible values: N/A

Default value: N/A

Removes all static MAC address entries from the address table.

EXAMPLE:

ServerIron# clear mac-address

Syntax: clear mac-address

Possible values: N/A

Default value: N/A

Clears the public keys from the active configuration.

EXAMPLE:

ServerIron# clear public-key

Syntax: clear public-key

Possible values: N/A

Default value: N/A

Clears packet statistics displayed by the show rmon statistics command. See "show rmon statistics" .

EXAMPLE:

ServerIron# clear rmon

Syntax: clear rmon

Possible values: N/A

Default value: N/A

Clears traffic statistics for real and virtual servers.

EXAMPLE:

ServerIron# clear server traffic

Syntax: clear server traffic

Possible values: N/A

Default value: N/A

Clears all session table entries for a deleted real server.

When you delete a real server, the ServerIron attempts to clear all the session entries for that real server from the session table. The ServerIron requires all the sessions to be cleared from the table before performing these operations. If you use the force shutdown option (server force-delete command), the ServerIron ends the sessions within one minute. Otherwise, the ServerIron allows active sessions to end normally before removing them.

When you enter the command to delete a real server (no server real <name>), the ServerIron changes the server’s state to "await_delete". The real server remains in this state until all its sessions are cleared from the session table. Occasionally, the ServerIron cannot clear all of a deleted real server’s sessions from the table. When this occurs, the real server cannot be fully deleted. To complete deletion of the server in this case, enter the clear server session <name> command after entering the no server real <name> command.

EXAMPLE:

View image

The no server real command deletes real server "rs1". The show server real command displays the states of the real servers. Notice that rs1 is still listed as a valid real server, and has the state "await_delete". If the no server real command does not list the deleted server, the server has been completely deleted.

If the server continues to be listed with the "await_delete" state after several minutes, enter the clear server session command to finish deleting the server. The clear server session command deletes the remaining sessions for rs1, after which the ServerIron can finish deleting the server. You can enter this command immediately after entering the no server real command. You do not need to wait for any sessions to end normally.

Syntax: clear server session <name> [<name> [<name> [<name>]]]

The <name> parameter specifies the name of the real server. You can enter up to four real server names. It can take up to three minutes for the command to take effect. This command is supported only on the MP (the main processor management session). The command is not valid if entered in a WSM CPU management session.

Possible values: up to four real server names

Default value: N/A

Clears the total connections counter (tot-conn) in show commands for real and virtual servers. You can clear the counter for real servers only, virtual servers only, or both.

EXAMPLE:

To clear the total connections counter for both real and virtual servers, enter the following command:

ServerIron(config-vs-Foundry)# clear server tot-conn virtual

Syntax: clear server tot-conn [real | virtual]

Possible values:

• real – clears the total connections counter for real servers only.

• virtual – clears the total connections counter for virtual servers only.

Default value: N/A

Clears statistics for SNMP server traffic.

EXAMPLE:

ServerIron# clear snmp-server traffic

Syntax: clear snmp-server traffic

Possible values: N/A

Default value: N/A

Clears packet statistics displayed by the show statistics command. See "show statistics" .

EXAMPLE:

ServerIron# clear statistics

Syntax: clear statistics

Possible values: N/A

Default value: N/A

Resets counters for ICMP and TCP SYN packet burst thresholds.

EXAMPLE:

ServerIron# clear statistics dos-attack

Syntax: clear statistics dos-attack

Possible values: N/A

Default value: N/A

Clears all Web management interface sessions with the ServerIron. The sessions are immediately ended when you enter the command.

EXAMPLE:

ServerIron# clear web-connection

Syntax: clear web-connection

Possible values: N/A

Default value: N/A

The system clock can be set for a ServerIron. This command allows you to set the time and date. The time zone must be set using the clock timezone... command at the global CONFIG level.

EXAMPLE:

ServerIron# clock set 10:15:05 10-15-98

Syntax: [no] clock set <hh:mm:ss> <mm-dd-yy> | <mm-dd-yyyy>

Possible values: N/A

Default value: N/A

Launches you into the global CONFIG level.

EXAMPLE:

ServerIron# configure terminal

ServerIron(config)#

Syntax: configure terminal

Possible values: N/A

Default value: N/A

Copies files from one PCMCIA flash card on a management module to the other card.

EXAMPLE:

To copy a file from one flash card to the other, enter the following command:

BigServerIron# copy slot1 slot2 sales.cfg

Syntax: copy <from-card> <to-card> [\<from-dir-path>\]<from-name> [[\<to-dir-path>\]<to-name>]

The command shown in the example above copies a file from the flash card in slot 1 to the flash card in slot 2. In this case, the software uses the same name for the original file and for the copy. Optionally, you can specify a different file name for the copy.

Possible values: See above.

Default value: N/A

Copies a software image between the primary and secondary flash storage locations.

EXAMPLE:

Suppose you want to copy the software image stored in the primary flash into the secondary storage location. To do so, enter the following command.

BigServerIron# copy flash flash secondary

If you want to copy the image from the secondary flash to the primary flash, enter the following command.

BigServerIron# copy flash flash primary

In the copy flash flash...command, the first ‘flash’ refers to the origin of the image and the second ’flash’ in the command points to the destination flash. Note that in the command above, when ‘primary’ is entered, the system automatically knows that the origin flash is the secondary flash location.

Syntax: copy flash flash [primary | secondary]

Possible values: N/A

Default value: N/A

Copies a file from flash memory to a PCMCIA flash card on the management module.

EXAMPLE:

To copy a file from flash memory to a flash card, enter a command such as the following:

BigServerIron# copy flash slot2 BIS07000.bin primary
Flash Card Write (128 KBytes per dot) .......
Write to slot2 BIS07000.bin succeeded

The command in this example copies a software image file from the primary area in flash memory onto the flash card in slot 2.

If the copy does not succeed, the software lists messages to indicate the reason the copy did not work. For example, the following messages indicate that the copy did not work because the slot specified for the copy does not contain a flash card.

BigServerIron# copy flash slot2 m4s.car secondary
The system can not find the drive specified
Write to slot2 m4s.car failed

Syntax: copy flash slot1 | slot2 [\<to-dir-path>\]<to-name> primary | secondary

Possible values: See above.

Default value: N/A

Uploads a copy of the primary or secondary software image to a TFTP server.

EXAMPLE:

BigServerIron# copy flash tftp 192.22.33.4 test.img secondary

Syntax: copy flash tftp <ip-addr> <filename> primary | secondary

Possible values: See above.

Default value: N/A

Copies the currently loaded policy list used for policy-based SLB from the ServerIron to a file on a TFTP server.

EXAMPLE:

ServerIron# copy pbslb-running-config tftp 192.168.9.210 policy-list.txt

Syntax: copy pbslb-running-config tftp <tftp-server-ip-addr> <filename>

Possible values:

• <tftp-server-ip-addr> – IP address of the TFTP server.

• <filename> – name that the policy list file will be saved under.

Default value: N/A

Copies the device’s running-config to a PCMCIA flash card. The running-config contains the device’s currently active configuration information. When you copy the running-config to a flash card, you are making a copy of the device’s current configuration, including any configuration changes you have not saved to the startup-config file.

EXAMPLE:

To copy the device’s running configuration into a file on a flash card, enter a command such as the following:

BigServerIron# copy running slot1 runip.1
Write to slot1 run.sw succeeded

Syntax: copy running slot1 | slot2 [\<to-dir-path>\]<to-name>

Possible values: See above.

Default value: N/A

Uploads a copy of the running configuration file from the switch or router to a designated TFTP server.

EXAMPLE:

BigServerIron# copy running-config tftp 192.22.3.44 newrun.cfg

Syntax: copy running-config tftp <ip-addr> <filename>

Possible values: See above.

Default value: N/A

Copies a file from a PCMCIA flash card to the primary area in flash memory.

EXAMPLE:

To copy a file from a flash card to the primary area in flash memory, enter a command such as the following:

View image

Syntax: copy slot1 | slot2 flash [\<from-dir-path>\]<from-name> primary | secondary

Possible values: See above.

Default value: N/A

Loads ACLs from a running-config file into the device’s active configuration.

For example, if the device’s configuration includes a large set of Access Control Lists (ACLs), you can configure the ACLs offline in a text file on a PC, then save the file to the flash card. To load the ACLs, you can insert the flash card in the Foundry device, then copy the file to the device’s running configuration.

EXAMPLE:

To copy a running-config file from a flash card, enter a command such as the following:

BigServerIron# copy slot2 running runip.2

Syntax: copy slot1 | slot2 running [\<from-dir-path>\]<from-name>

The command in this example changes the device’s active configuration based on the information in the file.

Possible values: See above.

Default value: N/A

Copies a startup-config file from a PCMCIA flash card to flash memory. By default, the device uses the startup-config in the primary area of flash memory to configure itself when you boot or reload the device.

EXAMPLE:

To copy a startup-config file from a flash card to flash memory, enter a command such as the following:

BigServerIron# copy slot1 start test2.cfg
..Write startup-config done.

Syntax: copy slot1 | slot2 start [\<from-dir-path>\]<from-name>

This command copies a configuration file named test2.cfg from the flash card in slot 2 into the device’s flash memory. The next time you reboot or reload the device, it uses the configuration information in test2.cfg.

Possible values: See above.

Default value: N/A

Copies a file from a PCMCIA flash card to a TFTP server.

EXAMPLE:

To copy a file from a flash card to a TFTP server, enter a command such as the following:

BigServerIron# copy slot1 tftp 192.168.1.17 notes.txt
Uploading 254 bytes to tftp server ...
Upload to TFTP server done.

Syntax: copy slot1 | slot2 tftp <ip-addr> [\<from-dir-path>\]<from-name> [<to-name>]

Possible values: See above.

Default value: N/A

Copies the device’s startup-config file from flash memory onto a PCMCIA flash card.

EXAMPLE:

To copy the device’s startup-config file from flash memory onto a flash card, enter a command such as the following:

BigServerIron# copy start slot1 mfgtest.cfg
Write to slot1 cfgtest.cfg succeeded

Syntax: copy start slot1 | slot2 [\<to-dir-path>\]<to-name>

Possible values: See above.

Default value: N/A

Uploads a copy of the startup configuration file from the switch or router to a designated TFTP server.

EXAMPLE:

BigServerIron# copy startup-config tftp 192.22.3.44 new.cfg

Syntax: copy startup-config tftp <ip-addr> <filename>

Possible values: See above.

Default value: N/A

Downloads a copy of a Foundry switch or router software image from a TFTP server into the system flash in the primary or secondary storage location.

EXAMPLE:

BigServerIron# copy tftp flash 192.22.33.4 test.img primary

To download into the secondary storage location, enter the command listed below instead:

BigServerIron# copy tftp flash 192.22.33.4 test.img secondary

Syntax: copy tftp flash <ip-addr> <filename> primary | secondary

Possible values: See above.

Default value: N/A

Downloads a copy of a running-config file from a TFTP server into the running-config of the switch or router.

EXAMPLE:

BigServerIron# copy tftp running-config 192.22.33.4 newrun.cfg

Syntax: copy tftp running-config <ip-addr> <filename>

Possible values: See above.

Default value: N/A

Copies a file from a TFTP server to a PCMCIA flash card.

EXAMPLE:

To copy a file from a TFTP server to a flash card, enter a command such as the following:

BigServerIron# copy tftp slot1 192.168.1.17 notes.txt
Downloading from tftp server ...
Tftp 254 bytes done, copy to slot1 ...
Write to slot1 cfg.cfg succeeded

Syntax: copy tftp slot1 | slot2 <ip-addr> <from-name> [[\<to-dir-path>\]<to-name>]

If the file name you specify is not on the TFTP server, the CLI displays messages such as those shown in the following example:

View image

To simplify troubleshooting, especially when the file is present on your server but the command doesn’t find it, the messages list the complete TFTP path name on your TFTP server.

Possible values: See above.

Default value: N/A

Downloads a copy of a configuration file from a TFTP server into the startup configuration file of the switch or router. To activate this configuration file, reload (reset) the system.

EXAMPLE:

BigServerIron# copy tftp startup-config 192.22.33.4 new.cfg

Syntax: copy tftp startup-config <ip-addr> <filename>

Possible values: See above.

Default value: N/A

Used for debugging the distributed health check feature, this command displays messages about “health check status report received” events. Whenever a health check status report is received from a site ServerIron, a debug message is displayed on the GSLB ServerIron indicating the IP address of that ServerIron, as well as the length of that health check status report.

EXAMPLE:

GSLB-ServerIron# debug distributed-hcheck recvd-add-list
          GSLB: recvd-add-list-event debugging is on

Recvd add list msg from peer 192.9.1.1(len = 53)
Recvd add list msg from peer 192.9.1.17(len = 53)

Syntax: debug distributed-hcheck recvd-add-list-event

Possible value: N/A

Default value: N/A

Displays messages about “health check status report sent” events. When the site ServerIron sends the health check status report to the peer GSLB ServerIron, a debug message is displayed on the site ServerIron indicating the VIPs that are a part of this health check status message. These messages can help you detect if the site ServerIron is sending the health check status report at the correct interval and with the correct VIPs.

EXAMPLE:

SITE-ServerIron# debug distributed-hcheck sent-add-list
          GSLB: sent-add-list debugging is on

Sending Address List msg: VIP = 192.9.2.16, Active = 1, Host Range = 1, Num Ports = 2
Sending Address List msg: VIP = 192.9.2.17, Active = 0, Host Range = 1, Num Ports = 3
Sending Address List msg: done

Syntax: debug distributed-hcheck sent-add-list

Possible value: N/A

Default value: N/A

Places the device in diagnostic mode for Network Address Translation (NAT).

EXAMPLE:

View image

Syntax: debug ip nat icmp | tcp | udp <ip-addr>

Syntax: debug ip nat transdata

The <ip-addr> parameter specifies an IP address. The address applies to packets with the address as the source or the destination. Specify 0.0.0.0 to enable the diagnostic mode for all addresses.

The following examples show sample output from debug ip nat commands. The first three examples show the output from the diagnostic mode for ICMP NAT, TCP NAT, and UDP NAT. The fourth command shows the output for the diagnostic mode for NAT translation requests.

To disable the NAT diagnostic mode, enter a command such as the following:

Syntax: undebug ip nat icmp | tcp | udp | transdata

ServerIron# undebug ip nat tcp

This command disables the diagnostic mode for NAT performed on TCP packets. NAT diagnostics for other types of packets remain enabled.

Possible values: N/A

Default value: Disabled

Deletes a file from a flash card. This command applies only to management modules with PCMCIA slots.

EXAMPLE:

To delete a file on the flash card that has the management focus, enter a command such as the following:

BigServerIron# delete cfg.cfg

If the command is successful, the CLI displays a new command prompt.

Syntax: delete [slot1 | slot2] [<file-name>]

The command in this example deletes the specified file. To delete all files that contain a specific string of characters, enter a command such as the following:

BigServerIron# delete test*.*

This command deletes all files whose names start with “test”. To delete all the files on a flash card, enter a command such as the following:

BigServerIron# delete slot2

The command in this example deletes all files on the flash card in slot 2. In this example, slot 1 has the management focus, but the files to be deleted are on the flash card in slot 2.

Possible values: See above.

Default value: Deletes all files on the flash card!

List the files on a flash card in a Management IV module’s PCMCIA slot.

EXAMPLE:

To display a directory of all the files on the flash card that has the management focus, enter the following command:

BigServerIron# dir
Volume in slot1 has no label
Volume Serial Number is 19ED-1725

Directory of slot1

01/01/2000 00:00a    685935    POS.BIN
01/01/2000 00:00a   2157693    M4R.BIN
01/01/2000 00:00a       184    A22.CFG
01/01/2000 00:00a       254   R CFG.CFG
01/01/2000 00:00a       256    STR.CFG
01/01/2000 00:00a   1027230    M5.BIN
01/01/2000 00:00a       184    A8.CFG
01/01/2000 00:00a   1029838    M4S.BIN
01/01/2000 00:00a    687026    P3R.BIN
01/01/2000 00:00a   1029838    MM.BIN
             10 File(s)       6618438 bytes
                               74180608 bytes free

Syntax: dir [slot1 | slot2] [<file-name>]

To list only files that contain a specific pattern of characters in the name, enter a command such as the following:

BigServerIron# dir *.bin
Volume in slot1 has no label
Volume Serial Number is 19ED-1725

Directory of slot1

01/01/2000 00:00a    685935    POS.BIN
01/01/2000 00:00a   2157693    M4R.BIN
01/01/2000 00:00a   1027230    M5.BIN
01/01/2000 00:00a   1029838    M4S.BIN
01/01/2000 00:00a    687026    P3R.BIN
01/01/2000 00:00a   1029838    MM.BIN
               6 File(s)       6617560 bytes
                               74180608 bytes free

The command in this example lists all the image files on the flash card in the slot that has the management focus. (More specifically, the command lists all the files that end with “.bin”.)

For information about the command’s display, see the “Displaying a Directory of the Files on a Flash Card” section in the “Using Redundant Management Modules” chapter of the Foundry Switching Router Installation and Configuration Guide.

Possible values: See above.

Default value: Displays all files on the flash card that has the management focus.

Places the device in diagnostic mode for IP access lists. Use this diagnostic mode only if advised to do so by Foundry Technical Support.

Possible values: N/A

Default value: Disabled

Erases the image stored in primary flash.

EXAMPLE:

ServerIron# erase flash primary

Syntax: erase flash primary

Possible values: N/A

Default value: N/A

Erases the image stored in secondary flash.

EXAMPLE:

ServerIron# erase flash secondary

Syntax: erase flash secondary

Possible values: N/A

Default value: N/A

Erases the configuration stored in the startup-config file.

EXAMPLE:

ServerIron# erase startup-config

Syntax: erase startup-config

Possible values: N/A

Default value: N/A

Moves activity up one level from the current level. In this case, activity will be moved to the user level.

EXAMPLE:

To move from the privileged level, back to the user level, enter the following:

ServerIron# exit

ServerIron>

Syntax: exit

Possible values: N/A

Default value: N/A

Provides a configurable option to speed up the system startup time. By default, this option is turned off, providing a three-second pause to allow a user to break into the boot prompt, if necessary. Use fastboot on to turn this option on and eliminate the three-second pause. To turn this feature off later, enter the command fastboot off. Fastboot changes will be saved automatically but will not become active until after a system reset.

To execute an immediate reload from the console of the boot code without a three-second delay, you can enter the fast reload command.

EXAMPLE:

ServerIron# fastboot on

Syntax: fastboot [on | off]

Possible values: on or off

Default value: off

Reformats a flash card in a Management IV module’s PCMCIA slot.

EXAMPLE:

To reformat a flash card, enter the following command:

View image

As shown in this example, the software formats the sector on the flash card, then verifies the formatting. In this example, the software did not find any bad sectors, so all the bytes on the card are available.

Syntax: format slot1 | slot2 [<label>]

The slot1 | slot2 parameter specifies the PCMCIA slot that contains the flash card you are formatting.

The <label> parameter specifies the label. You can specify up to 11 alphanumeric characters. You cannot use special characters or spaces.

Possible values: See above

Default value: N/A

Displays the data in a file on a flash card in hexadecimal format. This command applies only to management modules with PCMCIA flash slots.

EXAMPLE:

To display the data in a file in hexadecimal format, enter a command such as the following:

BigServerIron# hd cfg.cfg

Syntax: hd [slot1 | slot2] <file-name>

Each row of hexadecimal output contains the following parts:

• The byte offset of the date that is displayed to the right of the offset

• A row of hexadecimal data

• The ASCII equivalent of the hexadecimal data shown in the row

Possible values: see above

Default value: N/A

Terminates the specified active CLI session and resets the CONFIG token. Once you know the session ID of a Telnet connection (using the show who command), you can terminate it with the kill command. If the terminated session was a console, the console is sent back into User EXEC mode. If the terminated CLI session was a Telnet session, the Telnet connection is closed.

EXAMPLE:

ServerIron# kill telnet 1

Syntax: kill console | telnet <session-id>

Possible values: Session ID number from show who command

Default value: N/A

Displays or changes the save location for the startup-config file.

EXAMPLE:

BigServerIron# locate startup-config

Syntax: locate startup-config

EXAMPLE:

By default, when you save configuration changes, the changes are saved to the startup-config file on the device’s flash memory module. If you want to change the save location to a PCMCIA slot, enter a command such as the following:

BigServerIron# locate startup-config slot1 router1.cfg
BigServerIron# write memory

The first command in this example sets the device to save configuration changes to the file named “router1.cfg” in the flash card in PCMCIA slot 1. The second command saves the running-config to the router1.cfg file on the flash card in slot 1.

Syntax: locate startup-config [[slot1 | slot2] <file-name>]

You can specify a relative path name or full path name as part of the file name.

Possible values: See above

Default value: N/A

Another form of the md command. See "mkdir" .

Creates a subdirectory on a PCMCIA flash card.

EXAMPLE:

BigServerIron# mkdir slot1 \TEST

To verify successful creation of the subdirectory, enter a command to change to the new subdirectory level:

BigServerIron# chdir \TEST
Current directory of slot1 is: \TEST

Syntax: md | mkdir [slot1 | slot2] <dir-name>

You can enter either md or mkdir for the command name.

The slot1 | slot2 parameter specifies a PCMCIA slot. If you do not specify a slot, the command applies to the slot that currently has the management focus.

The <dir-name> parameter specifies the subdirectory name. You can enter a name that contains any combination of the following characters. Do not enter a backslash “ / ” in front of the name.

• All upper and lowercase letters

• All digits

• Spaces

• Any of the following special characters:

  • $
  • %
  • '
  • -
  • _
  • @
  • ~
  • `
  • !
  • (
  • )
  • {
  • }
  • ^
  • #
  • &

You can use spaces in a file or subdirectory name if you enclose the name in double quotes. For example, to specify a subdirectory name that contains spaces, enter a string such as the following: “a long subdirectory name”.

A subdirectory or file name can be a maximum of 256 characters long. A complete subdirectory path name cannot contain more than 263 characters.

The name is not case sensitive. You can enter upper- or lowercase letters. The CLI displays the name using uppercase letters.

Possible values: See above

Default value: N/A

Displays the data in a file on a flash card in a Management IV module’s PCMCIA slot.

EXAMPLE:

To display the contents of a file, enter a command such as the following:

BigServerIron# more cfg.cfg

Syntax: more [slot1 | slot2] <file-name>

Possible values: See above.

Default value: N/A

Copies a file from flash memory to a PCMCIA flash card on the management module.

EXAMPLE:

To copy a file from flash memory to a flash card, enter a command such as the following:

BigServerIron# ncopy flash primary slot2 BIS07000.bin
Flash Card Write (128 KBytes per dot) .......
Write to slot2 BIS07000.bin succeeded

The command in this example copies a software image file from the primary area in flash memory onto the flash card in slot 2.

If the copy does not succeed, the software lists messages to indicate the reason the copy did not work. For example, the following messages indicate that the copy did not work because the slot specified for the copy does not contain a flash card.

BigServerIron# ncopy flash secondary slot2 m4s.car
The system can not find the drive specified
Write to slot2 m4s.car failed

Syntax: ncopy flash primary | secondary slot1 | slot2 [\<to-dir-path>\]<to-name>

Possible values: See above.

Default value: N/A

Uploads a copy of the primary or secondary software image to a TFTP server.

EXAMPLE:

BigServerIron# ncopy flash secondary tftp 192.22.33.4 test.img

Syntax: ncopy flash primary | secondary tftp <ip-addr> <from-name>

Possible values: See above.

Default value: N/A

Copies the device’s running-config to a PCMCIA flash card. The running-config contains the device’s currently active configuration information. When you copy the running-config to a flash card, you are making a copy of the device’s current configuration, including any configuration changes you have not saved to the startup-config file.

EXAMPLE:

To copy the device’s running configuration into a file on a flash card, enter a command such as the following:

BigServerIron# ncopy running slot1 runip.1
Write to slot1 run.sw succeeded

Syntax: ncopy running slot1 | slot2 [\<to-dir-path>\]<to-name>

Possible values: See above.

Default value: N/A

Uploads a copy of the running configuration file from the switch or router to a designated TFTP server.

EXAMPLE:

BigServerIron# ncopy running-config tftp 192.22.3.44 newrun.cfg

Syntax: ncopy running-config tftp <ip-addr> <from-name>

Possible values: See above.

Default value: N/A

Copies a file from a PCMCIA flash card to the primary area in flash memory.

EXAMPLE:

To copy a file from a flash card to the primary area in flash memory, enter a command such as the following:

View image

Syntax: ncopy slot1 | slot2 [\<from-dir-path>\]<from-name> flash primary | secondary

Possible values: See above.

Default value: N/A

Loads ACLs from a running-config file into the device’s active configuration.

For example, if the device’s configuration includes a large set of Access Control Lists (ACLs), you can configure the ACLs offline in a text file on a PC, then save the file to the flash card. To load the ACLs, you can insert the flash card in the Foundry device, then copy the file to the device’s running configuration.

EXAMPLE:

To copy a running-config file from a flash card, enter a command such as the following:

BigServerIron# ncopy slot2 runip.2 running

Syntax: ncopy slot1 | slot2 [\<from-dir-path>\]<from-name> running

The command in this example changes the device’s active configuration based on the information in the file.

Possible values: See above.

Default value: N/A

Copies files from one PCMCIA flash card on a management module to the other card.

EXAMPLE:

To copy a file from one flash card to the other, enter the following command:

BigServerIron# ncopy slot1 sales.cfg slot2

Syntax: ncopy slot1 | slot2 [\<from-dir-path>\]<from-name> slot1 | slot2 [[\<to-dir-path>\]<to-name>]

The command shown in the example above copies a file from the flash card in slot 1 to the flash card in slot 2. In this case, the software uses the same name for the original file and for the copy. Optionally, you can specify a different file name for the copy.

Possible values: See above.

Default value: N/A

Copies a startup-config file from a PCMCIA flash card to flash memory. By default, the device uses the startup-config in the primary area of flash memory to configure itself when you boot or reload the device.

EXAMPLE:

To copy a startup-config file from a flash card to flash memory, enter a command such as the following:

BigServerIron# ncopy slot1 test2.cfg start
..Write startup-config done.

Syntax: ncopy slot1 | slot2 [\<from-dir-path>\]<from-name> start

This command copies a configuration file named test2.cfg from the flash card in slot 2 into the device’s flash memory. The next time you reboot or reload the device, it uses the configuration information in test2.cfg.

Possible values: See above.

Default value: N/A

Copies the device’s startup-config file from flash memory onto a PCMCIA flash card.

EXAMPLE:

To copy the device’s startup-config file from flash memory onto a flash card, enter a command such as the following: