HP BladeSystem bc2800 HP BladeSystem PC Blade Enclosure Integrated Administrat - Page 119

Configuring Blade PC Boot Order

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

Page 119 highlights

This command downloads and install a file containing one or more SSH keys which are authorized to log into the Integrated Administrator. The new file will replace any existing keys. Supported protocols are http, ftp and tftp. Format the URL as: protocol://host/path/file. If your ftp server does not support anonymous logins, you can specify a username and password by replacing the host part (in previous format) with: username:password@host. The Integrated Administrator supports multiple SSH keys in one downloaded file. Max file size for SSH keys is 16K. Key-based SSH logins has an advantage for use with scripting as well. Remote commands can be sent to any Integrated Administrator after installing the appropriate authorized key without having to enter a password between each command. Using the OpenSSH package, the user can send commands using the following syntax: ssh user@host command You can group together commands to perform a series of actions. To view the health status of the enclosure and all blades with a single command, type: ssh user@host "SHOW ENCLOSURE STATUS; SHOW STATUS BAY ALL" By having an authorized key file installed on the Integrated Administrator, the user can combine these without having to enter a password between each command sent to the Integrated Administrator. Configuring Blade PC Boot Order Enclosure and group administrators may change the boot order, sometimes referred to as Initial Program Load (IPL), of their blade PCs by using the CLI of the Integrated Administrator. The change can be made permanently or only for the next reboot. Several commands are available in the CLI to control the blades in this manner. This feature requires version 1.20 or higher of the Integrated Administrator firmware and a blade ROM dated 06/15/02 or newer to be controlled in this manner. To set a blade PC boot order, type: SET BAY BOOT FIRST [HDD | PXE] [ALL | {[,|-] }] During the next reboot, this will set the specified blade PC boot order to use the given boot device first. This has the same effect as changing the Standard Boot Order (IPL) setting in the RBSU on the blade PC. To set a blade PC boot order for the next boot only, type: SET BAY BOOT [ONCE | ALWAYS] [HDD | PXE | RBSU] [ALL | {[,|-] }] This will force the specified blade PC to boot to the specified media on the next boot only. The RBSU setting will make the blade PC(s) boot into the RBSU which can be viewed with the Remote Console functionality. The HDD setting forces the blade PC to boot from the hard drive first, and the PXE setting forces it to boot from the integrated NIC first. To reset blade boot order settings which have not yet taken effect, type: CLEAR BAY BOOT [FIRST | ONCE | ALWAYS] [ALL | {[,|-] }] This will clear changes to the specified blade PC boot order that were made with the SET BAY BOOT command. It only affects pending changes so if the blade PC has been rebooted since the SET BAY BOOT command, this command will have no effect. ENWW Configuring Blade PC Boot Order 111

  • 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
This command downloads and install a file containing one or more SSH keys which are authorized
to log into the Integrated Administrator. The new file will replace any existing keys.
Supported protocols are http, ftp and tftp. Format the URL as:
protocol://host/path/file
.
If your ftp server does not support anonymous logins, you can specify a username and password by
replacing the host part (in previous format) with: username:password@host.
The Integrated Administrator supports multiple SSH keys in one downloaded file. Max file size for SSH
keys is 16K.
Key-based SSH logins has an advantage for use with scripting as well. Remote commands can be sent
to any Integrated Administrator after installing the appropriate authorized key without having to enter a
password between each command. Using the OpenSSH package, the user can send commands using
the following syntax:
ssh user@host command
You can group together commands to perform a series of actions. To view the health status of the
enclosure and all blades with a single command, type:
ssh user@host “SHOW ENCLOSURE STATUS; SHOW STATUS BAY ALL”
By having an authorized key file installed on the Integrated Administrator, the user can combine these
without having to enter a password between each command sent to the Integrated Administrator.
Configuring Blade PC Boot Order
Enclosure and group administrators may change the boot order, sometimes referred to as Initial Program
Load (IPL), of their blade PCs by using the CLI of the Integrated Administrator. The change can be made
permanently or only for the next reboot. Several commands are available in the CLI to control the blades
in this manner. This feature requires version 1.20 or higher of the Integrated Administrator firmware and
a blade ROM dated 06/15/02 or newer to be controlled in this manner.
To set a blade PC boot order, type:
SET BAY BOOT FIRST [HDD | PXE] [ALL | <bay number> {[,|-] <bay number>}]
During the next reboot, this will set the specified blade PC boot order to use the given boot device first.
This has the same effect as changing the Standard Boot Order (IPL) setting in the RBSU on the blade
PC.
To set a blade PC boot order for the next boot only, type:
SET BAY BOOT [ONCE | ALWAYS] [HDD | PXE | RBSU] [ALL | <bay number> {[,|-]
<bay number>}]
This will force the specified blade PC to boot to the specified media on the next boot only. The RBSU
setting will make the blade PC(s) boot into the RBSU which can be viewed with the Remote Console
functionality. The HDD setting forces the blade PC to boot from the hard drive first, and the PXE setting
forces it to boot from the integrated NIC first.
To reset blade boot order settings which have not yet taken effect, type:
CLEAR BAY BOOT [FIRST | ONCE | ALWAYS] [ALL | <bay number> {[,|-] <bay
number>}]
This will clear changes to the specified blade PC boot order that were made with the SET BAY BOOT
command. It only affects pending changes so if the blade PC has been rebooted since the SET BAY
BOOT command, this command will have no effect.
ENWW
Configuring Blade PC Boot Order
111