HP Integrity rx2800 HP Integrity iLO 3 Operations Guide - Page 23

Auto login, User Accounts, Remote Console Access, Virtual Power and Reset

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 23 highlights

IMPORTANT: Invalid IP addresses will disable the ability for the OA to do Single Sign On (SSO) to the AUX blade(s). Alternatively, assigning a valid IP address and Gateway such as 192.168.2.x (local only to the enclosure) will enable the OA for minor blade management without requiring network DHCP addresses. For more information on assigning IP addresses on auxiliary blades, see the HP BladeSystem Onboard Administrator User Guide on the HP website at HP BladeSystem c-Class Onboard Administrator. Auto login Auto login provides direct access to iLO 3 from the OA for users who already logged in to the OA. A user who has authenticated the connection to the OA can follow a link to a server blade in the enclosure without an additional login step. Auto login features and usage are as follows: • A user who has authenticated a connection to the OA is able to establish a connection with iLO 3 without providing the user login and password to iLO 3. • The OA provides the following auto login connection methods to iLO 3 links to users to launch these connections to iLO 3: iLO CLI SSH connection If you logged in to the OA CLI through SSH, enter connect server to establish an SSH connection with iLO 3. iLO web GUI connection If you logged in to the OA web GUI, click on the link to launch the iLO web GUI. • Auto login is implemented using IPMI over Ethernet between the OA and iLO 3 to create and delete user commands. • Supports a maximum of five simultaneous OA user accounts. The OA keeps track of these users locally. The information maintained for each user is the user name, password, and privilege levels. • User accounts for the auto login feature are created in the MP database when an auto login session is established. These accounts are deleted when the auto login session is terminated. • If a maximum number of user accounts has already been reached, and the OA creates another account on iLO 3. The OA sends a request to iLO 3 to delete one of the previously created accounts, before attempting to create a new one. • If iLO 3 is rebooted or power-cycled, it verifies any previously created OA user accounts in the iLO 3 user database when it boots up. If there are any previously-created OA user accounts, it deletes those accounts. • View and manage user accounts created in iLO 3 by the OA like any other local user account on iLO 3. To view and manage user accounts, use the TUI WHO, UC commands; or use the User Administration page in the web GUI. • View and disconnect user connections established through the auto login feature just like other connections to iLO 3. To view and disconnect user connections, use the TUI WHO, DI commands, or use the User Administration pages in the web GUI. • The OA supports three types of users: administrators, operators, and users. These user types map to the following iLO 3 capabilities: Administrators Can perform any function including iLO 3 MP configuration. This level equates to an iLO 3 user with all privilege levels such as, Administer User Accounts, Remote Console Access, Virtual Power and Reset, Virtual Media, and Configure iLO MP settings. It enables access to all aspects of the OA including configuration, firmware updates, user management, and resetting default settings. Server blade connection 23

  • 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
IMPORTANT:
Invalid IP addresses will disable the ability for the OA to do Single Sign On (SSO)
to the AUX blade(s). Alternatively, assigning a valid IP address and Gateway such as 192.168.2.x
(local only to the enclosure) will enable the OA for minor blade management without requiring
network DHCP addresses.
For more information on assigning IP addresses on auxiliary blades, see the
HP BladeSystem
Onboard Administrator User Guide
on the HP website at
HP
Blade
S
y
s
t
e
m
c
-C
la
s
s
Onboar
d
A
dminis
tr
at
o
r
.
Auto login
Auto login provides direct access to iLO 3 from the OA for users who already logged in to the
OA. A user who has authenticated the connection to the OA can follow a link to a server blade
in the enclosure without an additional login step. Auto login features and usage are as follows:
•
A user who has authenticated a connection to the OA is able to establish a connection with
iLO 3 without providing the user login and password to iLO 3.
•
The OA provides the following auto login connection methods to iLO 3 links to users to launch
these connections to iLO 3:
iLO CLI SSH connection
If you logged in to the OA CLI through SSH, enter
connect server <bay number>
to establish an SSH
connection with iLO 3.
iLO web GUI connection
If you logged in to the OA web GUI, click on the link to
launch the iLO web GUI.
•
Auto login is implemented using IPMI over Ethernet between the OA and iLO 3 to create and
delete user commands.
•
Supports a maximum of five simultaneous OA user accounts. The OA keeps track of these
users locally. The information maintained for each user is the user name, password, and
privilege levels.
•
User accounts for the auto login feature are created in the MP database when an auto login
session is established. These accounts are deleted when the auto login session is terminated.
•
If a maximum number of user accounts has already been reached, and the OA creates another
account on iLO 3. The OA sends a request to iLO 3 to delete one of the previously created
accounts, before attempting to create a new one.
•
If iLO 3 is rebooted or power-cycled, it verifies any previously created OA user accounts in
the iLO 3 user database when it boots up. If there are any previously-created OA user accounts,
it deletes those accounts.
•
View and manage user accounts created in iLO 3 by the OA like any other local user account
on iLO 3. To view and manage user accounts, use the TUI
WHO, UC
commands; or use the
User Administration page in the web GUI.
•
View and disconnect user connections established through the auto login feature just like other
connections to iLO 3. To view and disconnect user connections, use the TUI
WHO, DI
commands, or use the User Administration pages in the web GUI.
•
The OA supports three types of users: administrators, operators, and users. These user types
map to the following iLO 3 capabilities:
Administrators
Can perform any function including iLO 3 MP configuration. This level
equates to an iLO 3 user with all privilege levels such as, Administer
User Accounts, Remote Console Access, Virtual Power and Reset,
Virtual Media, and Configure iLO MP settings. It enables access to all
aspects of the OA including configuration, firmware updates, user
management, and resetting default settings.
Server blade connection
23