Purpose	* To be used for evaluations and emergency recovery procedures only. Contact your F5 representative for more information.* Use the clear global-config command to erase all global-config parameters. The global-config parameters are shared among both ARX peers in a redundant pair: primarily, namespaces and global servers. The traditional running-config applies only to the local switch.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	clear global-config
Default(s)	None
Guidelines	This causes the switch to reboot. A prompt asks for confirmation before the CLI reboots the switch; enter yes to proceed. If the switch is part of a redundant pair, you can only run this command on the senior switch. This reboots both switches in the pair. Use this command to remove all namespaces, global servers, and other global-config parameters. This can be a useful alternative to delete startup-config, which deletes all running-config and global-config parameters. By preserving the running-config parameters, the network configuration remains intact; you can use the in-band (VLAN) management interfaces after clearing the global config. However, this may leave back-end filers in a non-deterministic state. We strongly recommend using nsck ... destage on every active namespace before using this command.
Sample	bstnA# clear global-config This removes all global configuration and reboots both chassis in the redundant pair in order to ensure services are removed properly.   Are you sure? [yes/no] yes bstnA# Broadcast message (Fri Sep 24 13:53:15 2004):   The system is going down for reboot NOW! ... deletes all namespaces, global servers, and other shared parameters.
Related Commands	delete startup-config nsck ... destage

Purpose	The global-config parameters are shared among both ARXes in a redundant pair. The traditional running-config applies only to the local switch. We recommend copying the global config to a remote server after any global-configuration change. Use the copy global-config command to copy the switchs global configuration to a local file, a remote server, an ARX volume, a remote ARX, or an email recipient.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax: FTP Upload	copy global-config ftp://[user[:password]@]server/file-name   ftp://[user[:password]@]server/file-name (1-1024 characters) is the syntax for uploading the startup-config: user[:password]@ (optional) are the credentials for FTP access. If you omit them altogether, they default to the credentials set by the ip ftp-user command. If you enter the user but omit the password, the CLI prompts for the password before continuing. server is the IP address or hostname for the FTP server. file-name is the destination-file path. Lead with an extra slash (/) if the path is absolute (for example, ftp://10.1.1.5//var/cfgs/ac-gbl.cfg). Use only one slash if the path is local to the home directory for user (for example, ftp://10.1.1.5/ac-gbl.cfg).
Syntax: SCP Upload	copy global-config scp://user@server:dest-file [accept-host-key]   scp://user@server:dest-file (1-1024 characters) is the URL for the destination file: user@ is the username to present to the other end of the SCP connection. This user must be valid at the remote host. server: is the IP address or hostname for SCP host. End with a colon (:). dest-file is the destination-file path. Lead with a slash (/) if the path is absolute (for example, scp://root@10.1.1.5:/var/configs/gblConf). Use no slash if the path is local to the home directory for user (for example, scp://root@10.1.1.5:myGlobal.cfg). accept-host-key (optional) indicates that if the other end of the connection has an unknown SSH host key (that is, if it is new, or if its key has changed since the last time the host was contacted), the ARX should accept the new host key and continue with the upload. Otherwise, the ARX stops the upload if the host presents an unknown key.
Syntax: Sending to an ARX Volume	copy global-config {nfs|cifs} namespace vol file-name   nfs | cifs is a required choice. This chooses the protocol for the file transfer. namespace (1-30 characters) identifies the namespace to hold the global-config file. vol (1-1024 characters) is the volume name. file-name (1-1024 characters) is the path to the config file, starting at the root of the volume.
Syntax: Sending to Another ARX	copy global-config ron remote-arx {configs|scripts} file-name   remote-arx (1-30 characters) is the hostname of the remote ARX to which you are sending the copy. This must be an ARX in the same Resilient-Overlay Network (RON); use show ron for a full list of hosts on the RON. The remote host checks your administrative credentials to confirm you have permission to copy the configuration file: the credentials are the ip ron-user, or the credentials you used to log into the CLI if no RON user is set. configs | scripts is the destination directory at the remote host. This is a required choice. file-name (1-1024 characters) is a destination-file name, for example, gblcfgbeta01.cfg, to which you copy/save the switchs global-configuration information.
Syntax: TFTP Upload	copy global-config tftp://server/file-name   tftp://server/file-name (1-1024 characters) is the URL for the global-config file: server is the machine name (for example, mymachine.myco.com). file-name is the desired path name for the file. Lead with an extra slash (/) if the path is absolute: for example, ...myserver//var/configs/gblConf specifies /var/configs/gblConf on myserver. Use only one slash if the path is local to the servers tftpboot directory. This conforms with the specification for FTP URLs in RFC 1738.
Syntax: Send in an Email	copy global-config smtp://[email-address/]file-name   smtp://[email-address/]file-name (1-1024 characters) is an email destination for the file: smtp:// is required. This declares that the destination is an email address. email-address (optional) is the recipient of the email in username@host format (for example, jsmith@myco.com). If you omit this, the CLI uses the default address set by the cfg-smtp to command. file-name is the name of the global-config file. This is sent as an attachment to the outbound email message. You must configure SMTP on the ARX before you use this syntax. Start with the smtp command in cfg mode.
Syntax: Local Copy	copy global-config {configs | diag-info | scripts} file-name   configs | diag-info | scripts is the destination directory. This is a required choice. file-name (1-1024 characters) is a destination-file name, for example, gblcfgbeta01.cfg, to which you copy/save the switchs global-configuration information.
Default(s)	None
Guidelines	If you upload using SCP (a secure protocol), the CLI asks for a password. Provide a password for user. The user name and password must be valid at the SCP server. The CLI also prompts for a password if you use FTP and enter a user without a password. Use this command to save the current global config to a file. The global-config contains all parameters that you set in gbl mode, such as namespaces, filers, and global servers. These parameters are shared between both peers in a redundant pair. You should make a copy of the global config after any change to these parameters. To save the global-config on a regular schedule, you can use this command with the at command.
	You can use this file later to recreate the global configuration, if necessary; copy it to the scripts or config directory and use the run scripts config-file-name command.
Note: A global-config run changes the global config for both members of a redundant pair.
	Use show directories to view all the local-directory listings. To save all the local-config parameters, such as layer-2 and layer-3, use the copy running-config command. To save both running- and global-config into a single file, use copy startup-config. To view the global config, use show global-config. Note that this command, copy global-config, immediately creates the global-config file from the database and then copies it, so its date stamp is either the time you invoked the command or the time that the file was created at the remote server. This is different from copy configs boot-config, which copies a file that was created when the system was installed: the boot-config file may have a time stamp with the system-install time.
Samples	bstnA# copy global-config scripts ron.cfg copies the global config into a new file, ron.cfg, in the scripts directory.   bstnA# copy global-config ftp://ftpuser:ftpuser@10.1.1.19/acopia-gbl.cfg copies the global config to an FTP server at 10.1.1.19.   bstnA# copy global-config scp://juser@10.1.1.35:acopia-gbl.cfg Password: jpasswd copies the running config to an SCP server at 10.1.1.35.
Related Commands	copy ftp copy scp copy {nfs|cifs} copy ron copy tftp copy smtp run ip ftp-user ip ron-user smtp show directories copy running-config copy startup-config show global-config at

Purpose	The running-config is the parameters that apply to the local switch only, as opposed to a redundant peer. We strongly recommend saving the running-config after any configuration change. Use the copy running-config command to copy the switchs current running configuration to a local file, upload it to a remote server, place it into an ARX volume, or send it in an email message.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax: FTP Upload	copy running-config ftp://[user[:password]@]server/file-name   ftp://[user[:password]@]server/file-name (1-1024 characters) is the syntax for uploading the startup-config: user[:password]@ (optional) are the credentials for FTP access. If you omit them altogether, they default to the credentials set by the ip ftp-user command. If you enter the user but omit the password, the CLI prompts for the password before continuing. server is the IP address or hostname for the FTP server. file-name is the destination-file path. Lead with an extra slash (/) if the path is absolute (for example, ftp://10.1.1.5//var/cfgs/ac-run.cfg). Use only one slash if the path is local to the home directory for user (for example, ftp://10.1.1.5/ac-run.cfg).
Syntax: SCP Upload	copy running-config scp://user@server:dest-file [accept-host-key]   scp://user@server:dest-file (1-1024 characters) is the URL for the destination file: user@ is the username to present to the other end of the SCP connection. This user must be valid at the remote host. server: is the IP address or hostname for SCP host. End with a colon (:). dest-file is the destination-file path. Lead with a slash (/) if the path is absolute (for example, scp://root@10.1.1.5:/var/configs/runConf). Use no slash if the path is local to the home directory for user (for example, scp://root@10.1.1.5:myrun.cfg). accept-host-key (optional) indicates that if the other end of the connection has an unknown SSH host key (that is, if it is new, or if its key has changed since the last time the host was contacted), the ARX should accept the new host key and continue with the upload. Otherwise, the ARX stops the upload if the host presents an unknown key.
Syntax: Sending to an ARX Volume	copy running-config {nfs|cifs} namespace vol file-name   nfs | cifs is a required choice. This chooses the protocol for the file transfer. namespace (1-30 characters) identifies the namespace to hold the running-config file. vol (1-1024 characters) is the volume name. file-name (1-1024 characters) is the path to the config file, starting at the root of the volume.
Syntax: Sending to Another ARX	copy running-config ron remote-arx {configs|scripts} file-name   remote-arx (1-30 characters) is the hostname of the remote ARX to which you are sending the copy. This must be an ARX in the same Resilient-Overlay Network (RON); use show ron for a full list of hosts on the RON. The remote host checks your administrative credentials to confirm you have permission to copy the configuration file: the credentials are the ip ron-user, or the credentials you used to log into the CLI if no RON user is set. configs | scripts is the destination directory at the remote host. This is a required choice. file-name (1-1024 characters) is a destination-file name, for example, rnngcfgPrtlnd.cfg, to which you copy/save the switchs running-configuration information.
Syntax: TFTP Upload	copy running-config tftp://server/file-name   tftp://server/file-name (1-1024 characters) is the URL for the running-config file: server is the machine name (for example, mymachine.myco.com). file-name is the desired path name for the file. Lead with an extra slash (/) if the path is absolute: for example, ...myserver//var/configs/runConf specifies /var/configs/runConf on myserver. Use only one slash if the path is local to the servers tftpboot directory. This conforms with the specification for FTP URLs in RFC 1738.
Syntax: Send in an Email	copy running-config smtp://[e-mail-address/]file-name   smtp://[e-mail-address/]file-name (1-1024 characters) is an E-mail destination for the file: smtp:// is required. This declares that the destination is an E-mail address. e-mail-address (optional) is the recipient of the E-mail in username@host format (for example, jsmith@myco.com). If you omit this, the CLI uses the default address set by the cfg-smtp to command. file-name is the name of the running-config file. This is sent as an attachment to the outbound E-mail message. You must configure SMTP on the ARX before you use this syntax. Start with the smtp command in cfg mode.
Syntax: Local Copy	copy running-config {configs | diag-info | scripts} file-name   configs | diag-info | scripts is the destination directory. This is a required choice. file-name (1-1024 characters) is a file name (for example, arxbeta02.cfg) to which you copy the switchs running-config information.
Default(s)	None
Guidelines	If you upload using SCP (a secure protocol), the CLI asks for a password. Provide a password for user. The user name and password must be valid at the SCP server. The CLI also prompts for a password if you use FTP and enter a user without a password. Use this command to save the current running configuration to a file in the event you need to recreate the local configuration later. The running-config contains all of the parameters that you create under cfg mode, such as layer-2 and layer-3 configuration. These parameters apply only to the current switch, as opposed to a redundant peer. You should save a copy of the running config after any configuration change. To save the running-config on a regular schedule, you can use this command with the at command. To copy global parameters to a file, such as namespaces and global servers, use the copy global-config command. To save both running- and global-config into a single file, use copy startup-config. The show running-config command shows the config at the CLI prompt. To recreate the running config (either on the same switch or a replacement switch), copy it to the scripts or config directory and use the run scripts config-file-name command. Note that this command, copy running-config, immediately creates the running-config file from the database and then copies it, so its date stamp is either the time you invoked the command or the time that the file was created at the remote server. This is different from copy configs boot-config, which copies a file that was created when the system was installed: the boot-config file may have a time stamp with the system-install time.
Samples	bstnA# copy running-config config aco-run.cfg copies the running config into the new aco-run.cfg file in the config directory.   bstnA# copy running-config ftp://10.1.1.19/acopia-run.cfg copies the running config to an FTP server at 10.1.1.19.   bstnA# copy running-config smtp://jsmith@myco.com/ARX-run.cfg sends the running config in an E-mail to jsmith@myco.com.   bstnA# copy running-config scp://juser@10.1.1.35:acopia-run.cfg Password: jpasswd copies the running config to an SCP server at 10.1.1.35.
Related Commands	copy ftp copy scp copy {nfs|cifs} copy ron copy tftp copy smtp run ip ftp-user ip ron-user smtp show configs copy global-config copy startup-config show running-config at

Purpose	Use the copy startup-config command to copy the switchs full configuration (both running-config and global-config) to a specified directory and file. You can also use this command to upload the file to a remote server or send it in an E-mail message.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax: FTP Upload	copy startup-config ftp://[user[:password]@]server/file-name   ftp://[user[:password]@]server/file-name (1-1024 characters) is the syntax for uploading the startup-config: user[:password]@ (optional) are the credentials for FTP access. If you omit them altogether, they default to the credentials set by the ip ftp-user command. If you enter the user but omit the password, the CLI prompts for the password before continuing. server is the IP address or hostname for the FTP server. file-name is the destination-file path. Lead with an extra slash (/) if the path is absolute (for example, ftp://10.1.1.5//var/cfgs/ac-start.cfg). Use only one slash if the path is local to the home directory for user (for example, ftp://10.1.1.5/ac-start.cfg).
Syntax: SCP Upload	copy startup-config scp://user@server:dest-file [accept-host-key]   scp://user@server:dest-file (1-1024 characters) is the URL for the destination file: user@ is the username to present to the other end of the SCP connection. This user must be valid at the remote host. server: is the IP address or hostname for SCP host. End with a colon (:). dest-file is the destination-file path. Lead with a slash (/) if the path is absolute (for example, scp://root@10.1.1.5:/var/configs/startConf). Use no slash if the path is local to the home directory for user (for example, scp://root@10.1.1.5:mystart.cfg). accept-host-key (optional) indicates that if the other end of the connection has an unknown SSH host key (that is, if it is new, or if its key has changed since the last time the host was contacted), the ARX should accept the new host key and continue with the upload. Otherwise, the ARX stops the upload if the host presents an unknown key.
Syntax: Sending to an ARX Volume	copy startup-config {nfs|cifs} namespace vol file-name   nfs | cifs is a required choice. This chooses the protocol for the file transfer. namespace (1-30 characters) identifies the namespace to hold the startup-config file. vol (1-1024 characters) is the volume name. file-name (1-1024 characters) is the path to the config file, starting at the root of the volume.
Syntax: Sending to Another ARX	copy startup-config ron remote-arx {configs|scripts} file-name   remote-arx (1-30 characters) is the hostname of the remote ARX to which you are sending the copy. This must be an ARX in the same Resilient-Overlay Network (RON); use show ron for a full list of hosts on the RON. The remote host checks your administrative credentials to confirm you have permission to copy the configuration file: the credentials are the ip ron-user, or the credentials you used to log into the CLI if no RON user is set. configs | scripts is the destination directory at the remote host. This is a required choice. file-name (1-1024 characters) is a destination-file name, for example, strtUpBstn.cfg, to which you copy/save the switchs startup-configuration information.
Syntax: TFTP Upload	copy startup-config tftp://server/file-name   tftp://server/file.tgz (1-1024 characters) is the URL for the startup-config file: server is the machine name (for example, mymachine.myco.com). file-name is the desired path name for the file. Lead with an extra slash (/) if the path is absolute: for example, ...myserver//var/configs/startConf specifies /var/configs/startConf on myserver. Use only one slash if the path is local to the servers tftpboot directory. This conforms with the specification for FTP URLs in RFC 1738.
Syntax: Send in an E-Mail	copy startup-config smtp://[e-mail-address/]file-name   smtp://[e-mail-address/]file-name (1-1024 characters) is an E-mail destination for the file: smtp:// is required. This declares that the destination is an E-mail address. e-mail-address (optional) is the recipient of the E-mail in username@host format (for example, jsmith@myco.com). If you omit this, the CLI uses the default address set by the cfg-smtp to command. file-name is the name of the startup-config file. This is sent as an attachment to the outbound E-mail message. You must configure SMTP on the ARX before you use this syntax. Start with the smtp command in cfg mode.
Syntax: Local Copy	copy startup-config {configs | diag-info | scripts} file-name   configs | diag-info | scripts selects a local destination directory. You can run the file as a script later if you save it to the configs or scripts directory. file-name (1-1024 characters) is a local-file name (for example, arxbeta02.cfg) to which you copy the switchs startup-config information.
Default(s)	None
Guidelines	If you upload using SCP (a secure protocol), the CLI asks for a password. Provide a password for user. The user name and password must be valid at the SCP server. The CLI also prompts for a password if you use FTP and enter a user without a password. Use this command to save both the running-config and the global config to a file in the event you need to recreate the configuration. The running-config has all of the configuration parameters that apply to the current switch, and the global config has all the shared parameters for the redundant pair. To copy these configs individually, use copy running-config and/or copy global-config. After any configuration change, we recommend saving a copy of the changed configuration to an external server. You can use this file later to recreate the full configuration, if necessary; copy it to the scripts directory and use the run scripts config-file-name command.
Note: A startup-config run changes the global config for both members of a redundant pair.
	To erase all configuration parameters and restart the configuration, you can delete the startup-config file (delete startup-config) and reboot (reload). This brings you back to the initial-boot script. Note that this command, copy startup-config, immediately creates the startup-config file from the database and then copies it, so its date stamp is either the time you invoked the command or the time that the file was created at the remote server. This is different from copy configs boot-config, which copies a file that was created when the system was installed: the boot-config file may have a time stamp with the system-install time.
Samples	bstnA# copy startup-config config aco-startup.cfg copies the startup config into the config directory.   bstnA# copy startup-config ftp://10.1.1.19/aco-start.cfg copies the startup config to an FTP server at 10.1.1.19.   bstnA# copy startup-config scp://juser@10.1.1.19:aco-start.cfg Password: jpasswd copies the startup config to an SCP server at 10.1.1.19.
Related Commands	copy ftp copy scp copy {nfs|cifs} copy ron copy tftp copy smtp copy running-config copy global-config run ip ftp-user ip ron-user smtp delete startup-config show configs show running-config

Purpose	The startup-config contains all parameters in both the running config and the global config. When the switch starts up, it runs all of these CLI commands. Without this file, the switch has no network configuration (other than the OOB management interface) or global configuration (namespace, global servers, and so on). The only administrative users that remain are those with crypto-officer roles. Use this command to delete the startup-config file.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	delete startup-config
Default(s)	None
Guidelines	Before you delete the configuration, we recommend saving a copy with the copy startup-config command. The CLI prompts for confirmation before deleting the startup-config file. Enter yes to continue. After you delete the startup-config file, the chassis comes up from its next reboot with minimal configuration. You can use the reload command to invoke a reboot. Before the next reboot, you can use restore startup-config to recover a mistakenly-deleted startup-config. Note that this deletes most of your network parameters, so you will only be able to log in through the OOB management port after reboot. To clear only namespaces, global servers, and other global parameters, you can use clear global-config instead. To remove the remaining parameters and go back to the initial-boot script after the next reboot, you can also use delete configs boot-config. This eliminates the OOB management port, too, requiring you to log in through the Console port after reboot.
Sample	bstnA# delete startup-config
Related Commands	restore startup-config copy ftp copy scp copy {nfs|cifs} copy tftp copy startup-config show configs show running-config clear global-config delete configs boot-config

Purpose	The startup-config contains all parameters in both the running config and the global config. When the switch starts up, it runs all of these CLI commands. Without this information, the switch has no network configuration (other than the OOB management interface) or global configuration (namespace, global servers, and so on). The only administrative users that remain are those with crypto-officer roles. If the startup config was previously deleted, but no reboot has occurred since that delete, you can use this command to restore it.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	restore startup-config
Default(s)	None
Guidelines	The CLI prompts for confirmation before restoring the startup-config file. Enter yes to continue. This recreates the current configuration and expresses it as a series of CLI commands. You can use this command after you previously removed the startup-config with the delete startup-config command. This recovers from a mistakenly-deleted configuration. To confirm that the command was successful, you can use the show configs command and confirm that a new startup-config entry is in the listing. If you run delete startup-config and reload before running this command, the chassis boots up without any configuration parameters. The restore startup-config command is no-longer useful after the chassis reboots.
Sample	bstnA# restore startup-config   Restore file 'startup-config' in directory 'configs'? [yes/no] yes
Related Commands	delete startup-config show configs copy startup-config

Purpose	The boot-config file contains all of the parameters that are set by the initial-boot script (described in the Hardware Installation Guides). If this file is absent when the switch boots, the switch reruns this script. Use the save boot-config command to ensure that the switch keeps its boot-config for the next reboot.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	save boot-config
Default(s)	None
Guidelines	After you delete the boot-config file (with delete configs boot-config) and reboot, the Console goes to the initial-boot script (described in the Hardware Installation Guides). The CLI starts after you answer all of the questions in the initial-boot script. This command prevents re-running the initial-boot script. It creates a text file named boot-config, which you can see with the show configs command. You can use the copy command (copy ftp, copy scp, copy {nfs|cifs}, or copy tftp) to upload it to an external host, or to download a new boot-config script.
Sample	bstnA# save boot-config
Related Commands	delete configs boot-config show configs copy ftp copy scp copy {nfs|cifs} copy tftp

Purpose	Use the show global-config command to view an ordered list of CLI commands required to recreate the current global-config state.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show global-config show global-config [filer|global-server|schedule|security| config-replication] show global-config archive [file-history-archive] show global-config {nfs|cifs} [fqdn] show global-config namespace [name [volume]]   filer | global-server | policy | security | config-replication are optional choices to focus on one section of the global-config report. filer specifies external-filer details. global-server specifies global-server configurations. schedule specifies policy schedules. security specifies security information such as management services authentication providers. config-replication focuses the output on config-replication rules. archive is an optional choice to focus on the archive section of the global-config report. This section has the configuration for every file-history archive on the ARX. Unless you specify a particular file-history-archive name, this shows the configurations for all of them. file-history-archive (optional, 1-64 characters) identifies a particular archive. nfs | cifs specifies that you want to focus on NFS or CIFS services only. Unless you include an fqdn, this shows all front-end services of the given type. fqdn (optional, 1-128 characters) identifies a particular NFS or CIFS service (for example, www.medarcv.com). For a list of all NFS and CIFS services, use the show virtual service command. namespace specifies that you want to focus on namespaces only. If you omit the name, all namespaces are shown. name (optional, 1-30 characters) identifies a particular namespace (for example, medarcv). Use show namespace for a list of all namespaces. volume (optional, 1-1024 characters) identifies a particular namespace volume (for example, /usr).
Default(s)	None
Guidelines	The output appears in table format by sections. The sections correspond to groups of commands for setting up major portions of the global configuration (such as namespaces, global servers, filers, policy, security, and so on). The global-config parameters are shared among both peers in a redundant pair; they do not include parameters that apply to the current switch only. For parameters that apply to the local switch, such as layer 2 and 3 parameters, use show running-config. After changes to the configuration, we recommend using copy global-config to save this text off to a file. Later, to recreate a saved global-config, paste the text at the CLI prompt (from priv-exec mode) or copy the file from a remote server and use the run command to run it as a script. Passwords and private SSH keys appear in encrypted form. Only the current switch (or a replacement for the current switch) can interpret and use this private information.
Note: A global-config run changes the global config for both members of a redundant pair.
Samples	bstnA> show global-config shows the full global-config. Figure 33.1 shows a sample report.   bstnA> show global-config filer shows all filer-configuration settings. See Figure 33.2 on page 33-36 for sample output.   bstnA> show global-config namespace wwmed shows the CLI commands to recreate one namespace, wwmed. See Figure 33.3 on page 33-38 for sample output.   bstnA> show global-config cifs shows all configuration settings for all front-end-CIFS services.
Related Commands	copy ftp copy scp copy {nfs|cifs} copy tftp copy global-config show running-config show virtual service show namespace

Purpose	The running-config applies to the local switch only; these parameters are not shared with the redundant peer. Use the show running-config command to view an ordered list of CLI commands required to recreate the current running-config state.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show running-config
Guidelines	The output is interspersed with comments that break it into sections. Each section is labeled in the comment. You can use copy running-config to save this text off to a file, or upload it to an FTP server. The running-config parameters all apply to the current switch only. For parameters that are shared between redundant peers, such as namespace parameters, use show global-config.
Sample	bstnA> show running-config shows the running-config. Figure 33.4 shows a sample report on an ARX-4000, Figure 33.5 on page 33-47 shows a sample report on an ARX-2500, Figure 33.6 on page 33-52 shows an ARX-2000 sample, Figure 33.7 on page 33-57 shows an example from an ARX-500, and Figure 33.8 on page 33-63 shows an example from an ARX-VE.
Related Commands	copy ftp copy scp copy {nfs|cifs} copy tftp copy running-config show directories show chassis show global-config