Fabric OS 5.2.x administrator guide 117
6
Maintaining configurations
It is important to maintain consistent configuration settings on all switches in the same fabric, because
inconsistent parameters (such as inconsistent PID formats) can cause fabric segmentation. As part of
standard configuration maintenance procedures, it is recommended that you back up all important
configuration data for every switch on a host computer server for emergency reference.
NOTE:
For information about AD-enabled switches using Fabric OS 5.2.x or later, see ”
Managing
administrative domains
” on page 127.
Displaying configuration settings
There are two ways to view configuration settings for a switch in an HP fabric:
•
Issue the
configShow
command (less information)
To display configuration settings using the CLI, connect to the switch, log in as admin, and enter the
configShow
command at the command line. The configuration settings vary depending on switch
model and configuration.
•
Upload an ASCII text file from the switch or switch module using the
configUpload
command (more
information)
The switch configuration file contains the following sections, and is organized as follows:
•
Introduction—Fabric OS version and time stamp
•
Boot Parameters—contains variables such as the switch's name and IP address.
•
Licenses—lists the licenses that are active on the switch.
•
Chassis Configuration—contains configuration variables such as diagnostic settings, fabric
configuration settings, and SNMP settings.
•
Configuration—contains licensed option configuration parameters.
•
Zoning—contains zoning configuration information.
•
Defined Security Policie—lists all of the defined security policies.
•
Active Security Policies—lists the active security policies.
•
FICU SAVED FILES—contains FICON CUP configurations.
•
fcRouting—lists the Fibre Channel Routing information.
•
iSCSI—iSCSI configuration parameters
•
Banner—security banner text.
Backing up a configuration
In case the configuration is lost or unintentional changes are made, keep a backup copy of the configuration
file (if using a SAN Director 2/128 with two domains, configuration
files
–one for each logical switch), which is
what gets saved when you enter the
configUpload
command. You should keep individual backup files for
all switches in the fabric. You should avoid copying configurations from one switch to another.
The following information is
not
saved
in a backup:
•
dnsconfig
information
•
passwords
If your setup supports anonymous users, and you log in as an anonymous user, password is still a required
field, even though its value may be ignored by the FTP service.
You can specify the use of secure file copy (scp) during the procedure. For instructions on configuring the
use of scp by default, refer to ”
Configuring secure file copy
” on page 112.
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......