HP ProLiant 800 HP ProLiant BL e-Class Integrated Administrator User Guide - Page 131

Enabling Remote Console Sessions to Server Blades

Page 131 highlights

Setting Up the System SET USER FULLNAME {} IMPORTANT: The must be 0-20 characters long and can include all alphanumeric characters, the dash, the underscore, and spaces. SET USER CONTACT {} IMPORTANT: The must be 0-20 characters long and can include all alphanumeric characters, the dash, the underscore, and spaces. ASSIGN USER {[VIEW | MODIFY]} Enabling Remote Console Sessions to Server Blades IMPORTANT: If a server blade is running the Windows 2000 operating system, only sequences that occur before the loading of the operating system are visible using Remote Console, unless the server blade is running the HP ProLiant Serial Console for Windows 2000 Server service. To allow Remote Console access to a server blade, install the HP ProLiant Serial Console for Windows 2000 Server service, located at www.compaq.com/support/files/server The remote console feature of the Integrated Administrator enables a user to connect to the console (serial) connector of the server blade in order to access the ROM-Based Setup Utility (RBSU) and operating system of the server blade. Accessing the RBSU of the server blade requires nothing more than connecting to the server blade. For detailed instruction to perform this task, see the "Accessing ROM-Based Setup Utility of a Server Blade" section in Chapter 6, "Performing Common Administrative Tasks." Accessing the operation system for server blades running Linux requires preparatory steps that vary depending on whether you are using Linux Loader (LILO) or Grand Unified Boot Loader (GRUB). 5-18 HP ProLiant BL e-Class Integrated Administrator 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228

Setting Up the System
SET USER FULLNAME {<user name>} <full name>
IMPORTANT:
The <full name> must be 0-20 characters long and can include all
alphanumeric characters, the dash, the underscore, and spaces.
SET USER CONTACT {<user name>} <contact info>
IMPORTANT:
The <contact info> must be 0-20 characters long and can include all
alphanumeric characters, the dash, the underscore, and spaces.
ASSIGN USER <user name> <group name> {[VIEW | MODIFY]}
Enabling Remote Console Sessions to Server Blades
IMPORTANT:
If a server blade is running the Windows 2000 operating system, only
sequences that occur before the loading of the operating system are visible using Remote
Console, unless the server blade is running the HP ProLiant Serial Console for Windows 2000
Server service.
To allow Remote Console access to a server blade, install the HP ProLiant Serial Console for
Windows 2000 Server service, located at
www.compaq.com/support/files/server
The remote console feature of the Integrated Administrator enables a user to connect
to the console (serial) connector of the server blade in order to access the
ROM-Based Setup Utility (RBSU) and operating system of the server blade.
Accessing the RBSU of the server blade requires nothing more than connecting to the
server blade. For detailed instruction to perform this task, see the “Accessing
ROM-Based Setup Utility of a Server Blade” section in Chapter 6, “Performing
Common Administrative Tasks.”
Accessing the operation system for server blades running Linux requires preparatory
steps that vary depending on whether you are using Linux Loader (LILO) or Grand
Unified Boot Loader (GRUB).
5-18
HP ProLiant BL e-Class Integrated Administrator User Guide