HP Bc1500 User Guide: HP BladeSystem PC Blade Enclosure Integrated Administrat - Page 112

Administering Security Certificates

Get HP Bc1500 - BladeSystem - Blade PC PDF manuals and user guides View all HP Bc1500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 112 highlights

Performing Advanced Functions 3. Edit the uploaded configuration file using a text editor to customize the configuration (such as user names, passwords, and network settings) for the other enclosures. ✎ Step 4 only applies if the other enclosures have been configured previously. ✎ For security reasons, passwords are never replicated in the configuration file. 4. Restore the factory defaults on each of the other enclosures to clear any previous configuration: a. Login as Administrator on an enclosure to which you intend to replicate the configuration. b. Type: SET FACTORY. This command sets the Integrated Administrator back to its factory default settings, although the password of the Administrator account does not change. The Integrated Administrator is restarted after all the changes are implemented. IMPORTANT: Only the Administrator account may execute this command. 5. Download the configuration to each of the other enclosures: a. Log in as Administrator on an enclosure to which you intend to replicate the configuration. b. Type: DOWNLOAD CONFIG . The Integrated Administrator does not check the configuration file for errors, but auto-executes the file in script mode. The file is not allowed to change the password of the Administrator account. Supported protocols are http, ftp, and tftp. Format the URL as protocol://host/path/file. If your ftp server does not support anonymous connections, specify a user name and password by replacing the host part in the above format with username:password@host. ✎ Step c applies only if you did not set user account passwords in the configuration file. c. Set the password for each user account. For commands, see Chapter 5, in section "User Account Commands." Administering Security Certificates ✎ The Integrated Administrator does not support these tasks using the Web-based user interface. Creating a Certificate Request To create a security certificate using the CLI, type: GENERATE CERTIFICATE REQUEST This command generates a PKCS#10 certificate request. This certificate request can be sent to your certification authority (CA) to obtain a PKCS#7 certificate file to use below. To create a self-signed security certificate using the CLI, type: GENERATE CERTIFICATE SELFSIGNED This command generates a self-signed PKCS#7 certificate to replace the existing SSL certificate. This certificate is signed with the current name of the enclosure and will be valid for 10 years. Users who do not have a certificate authority (CA) may use this certificate as a replacement. 8-2 HP PC Blade Enclosure Integrated Administrator for CCI v1.4 User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
8-2
HP PC Blade Enclosure Integrated Administrator for CCI v1.4 User Guide
Performing Advanced Functions
3. Edit the uploaded configuration file using a text editor to customize the configuration (such
as user names, passwords, and network settings) for the other enclosures.
✎
Step 4 only applies if the other enclosures have been configured previously.
✎
For security reasons, passwords are never replicated in the configuration file.
4. Restore the factory defaults on each of the other enclosures to clear any previous
configuration:
a.
Login as Administrator on an enclosure to which you intend to replicate the
configuration.
b.
Type:
SET FACTORY
. This command sets the Integrated Administrator back to its
factory default settings, although the password of the Administrator account does not
change. The Integrated Administrator is restarted after all the changes are implemented.
IMPORTANT:
Only the Administrator account may execute this command.
5. Download the configuration to each of the other enclosures:
a.
Log in as Administrator on an enclosure to which you intend to replicate the
configuration.
b.
Type:
DOWNLOAD CONFIG <url>
. The Integrated Administrator does not check the
configuration file for errors, but auto-executes the file in script mode. The file is not
allowed to change the password of the Administrator account. Supported protocols are
http, ftp, and tftp. Format the URL as
protocol://host/path/file
. If your ftp server does
not support anonymous connections, specify a user name and password by replacing the
host part in the above format with username:password@host.
✎
Step c applies only if you did not set user account passwords in the configuration file.
c.
Set the password for each user account. For commands, see Chapter 5,
in section “User
Account Commands.”
Administering Security Certificates
✎
The Integrated Administrator does not support these tasks using the Web-based user interface.
Creating a Certificate Request
To create a security certificate using the CLI, type:
GENERATE CERTIFICATE REQUEST
This command generates a PKCS#10 certificate request. This certificate request can be sent to
your certification authority (CA) to obtain a PKCS#7 certificate file to use below.
To create a self-signed security certificate using the CLI, type:
GENERATE CERTIFICATE
SELFSIGNED
This command generates a self-signed PKCS#7 certificate to replace the existing SSL certificate.
This certificate is signed with the current name of the enclosure and will be valid for 10 years.
Users who do not have a certificate authority (CA) may use this certificate as a replacement.