Fabric OS 6.2 administrator guide 109
5.
Install the certificate on each switch. Once the certificate is loaded on the switch, HTTPS starts
automatically.
6.
If necessary, install the root certificate to the browser on the management workstation.
7.
Add the root certificate to the Java Plug-in keystore on the management workstation.
Certificate authorities
To ease maintenance and allow secure out-of-band communication between switches, consider using one
certificate authority (CA) to sign all management certificates for a fabric. If you use different CAs,
management services operate correctly, but the Web Tools
Fabric Events
button is unable to retrieve events
for the entire fabric.
Each CA (for example, Verisign or GeoTrust) has slightly different requirements; for example, some
generate certificates based on IP address, while others require an FQDN, and most require a 1024-bit
public/private key while some may accept a 2048-bit key. Consider your fabric configuration, check CA
Web sites for requirements, and gather all the information that the CA requires.
Generating a public and private key
Perform this procedure on each switch.
1.
Connect to the switch and log in as admin.
2.
Enter the following command to generate a public/private key pair:
switch:admin>
seccertutil genkey
The system reports that this process will disable secure protocols, delete any existing CSR, and delete
any existing certificates.
3.
Respond to the prompts to continue and select the key size:
Continue (yes, y, no, n): [no]
y
Select key size [1024 or 2048]:
1024
Generating new rsa public/private key pair
Done.
Because CA support for the 2048-bit key size is limited, you should select 1024 in most cases.
Generating and storing a CSR
After generating a public/private key, perform this procedure on each switch.
1.
Connect to the switch and log in as admin.
2.
Enter the following command:
switch:admin>
seccertutil gencsr
3.
Enter the requested information:
Country Name (2 letter code, eg, US):
US
State or Province Name (full name, eg, California):
California
Locality Name (eg, city name):
San Jose
Organization Name (eg, company name):
Brocade
Organizational Unit Name (eg, department name):
Eng
Common Name (Fully qualified Domain Name, or IP address):
192.1.2.3
Generating CSR, file name is: 192.1.2.3.csr
Done.
Your CA may require specific codes for Country, State or Province, Locality, Organization, and
Organizational Unit names. Make sure that your spelling is correct and matches the CA requirements.
If the CA requires that the Common Name be specified as an FQDN, make sure that the fully qualified
domain name is set on the domain name server. The IP address or FQDN will be the server where the
certificate will be placed.
4.
Enter the following command to store the CSR:
switch:admin>
seccertutil export
Summary of Contents for A7533A - Brocade 4Gb SAN Switch Base
Page 1: ...HP StorageWorks Fabric OS 6 2 administrator guide Part number 5697 0016 Edition May 2009 ...
Page 24: ...24 ...
Page 99: ...Fabric OS 6 2 administrator guide 99 ...
Page 100: ...100 Managing user accounts ...
Page 118: ...116 Configuring standard security features ...
Page 164: ...162 Configuring advanced security features ...
Page 234: ...232 Installing and maintaining firmware ...
Page 268: ...266 Administering advanced zoning ...
Page 284: ...282 Configuring Enterprise class platforms ...
Page 292: ...290 Routing traffic ...
Page 294: ...292 Interoperability for merged SANs ...
Page 302: ...300 Configuring the Distributed Management Server ...
Page 334: ...332 iSCSI gateway service ...
Page 340: ...338 Administering NPIV ...
Page 407: ...Fabric OS 6 2 administrator guide 405 ...
Page 408: ...406 Using the FC FC routing service ...
Page 438: ...434 Administering extended fabrics ...
Page 460: ...456 Administering ISL trunking ...
Page 516: ...512 FICON fabrics ...
Page 526: ...522 Configuring and monitoring FICON Extension Services ...
Page 540: ...536 Configuring the PID format ...
Page 544: ...540 Understanding legacy password behavior ...
Page 546: ...542 Mixed fabric configurations for non merge SANs ...
Page 550: ...546 Migrating from an MP Router to a 400 MP Router ...
Page 558: ...554 Inband Management ...
Page 572: ...568 ...