Brocade Secure Fabric OS Administrator's Guide - Supporting Fabric OS v3.2.0, v4.4.0, v5.0.1, v5.1.0, 5.2.0, and 5.3.0 (53-1000244-02, June 2007)

72 Secure Fabric OS Administrator’s Guide
53-1000244-02
4
For information on upgrading firmware, refer to the Fabric OS Administrator’s Guide.
d. Customize the account passwords from the default values.
e. Repeat for each switch that you intend to include in the final merged fabric.
3. If the final merged fabric will contain switches running Fabric OS v2.6.2 or v3.2.0 and switches
running Fabric OS v4.4.0, v5.0.1, v5.1.0, or v5.2.0, the PID mode on all switches must be
compatible; for more information about PID modes, refer to the Fabric OS Administrator’s
Guide.
4. Ensure that the Management Server Platform Database Service is consistently enabled or
disabled across all the switches to be merged.
For information about management server support provided by Fabric OS, refer to the Fabric
OS Command Reference.
5. Ensure that all switches to be merged have activated Secure Fabric OS and Advanced Zoning
licenses, as described in “Verifying or Activating Secure Fabric OS and Advanced Zoning
Licenses” on page 9.
6. Ensure that all switches to be merged have the required PKI objects (private key passphrase,
switch private key, CSR, and root certificate) and a digital certificate installed.
a. Log in to the switch as admin.
b. Type the command supported by the Fabric OS installed on the switch:
• For Fabric OS v4.4.0 v5.0.1, v5.1.0, and v5.2.0, type pkiShow.
• For Fabric OS v2.6.2 and v3.2.0, type configShow “pki”.
A list displays the PKI objects currently installed on the switch.
NOTE
“Certificate” is the digital certificate. “Root Certificate” is an internal PKI object.
c. Verify that all of the objects display “Exist”.
If the digital certificate displays “Empty”, repeat the procedure provided in “Distributing
Digital Certificates to the Switches” on page 18. If any of the PKI objects other than the
digital certificate displays “Empty”, you can either reboot the switch to automatically
re-create the objects or re-create them as described in “Creating PKI Objects” on page 11.
d. Repeat for the remaining switches in the fabric.
7. Install a supported CLI client on the computer workstations that you will be using to manage
the merged fabric.
Supported CLI clients include sectelnet and SSH and are discussed in “Installing a Supported
CLI Client on a Workstation” on page 31.
8. Enable secure mode on all switches to be merged by entering the secModeEnable command
on the primary FCS switches of any fabrics that do not already have secure mode enabled.
For more information about enabling secure mode, refer to “Enabling Secure Mode” on
page 34.
9. Determine which switches you want to designate as primary FCS switch and backup FCS
switches for the merged fabric; then, modify the FCS policy for each fabric to list these switches
as the primary FCS switch and backup FCS switches.