Go to primary content
Oracle® Communications OC-CNE Installation Guide
Release 1.0
F16979-01
Go To Table Of Contents
Contents
Previous
Previous 		Next
Next

Configure Addresses for RMS iLOs, OA, EBIPA

Introduction

Prerequisites

Limitations/Expectations

References

Steps to configure Addresses for RMS iLOs, OA, EBIPA

This procedure is used to configure RMS iLO addresses and add a new user account for each RMS other than the Bootstrap Host. When the RMSs are shipped and out of box after hardware installation and powerup, the RMSs are in a factory default state with the iLO in DHCP mode waiting for DHCP service. DHCP is used to configure the ToR switches, OAs, Enclosure switches, and blade server iLOs, so DHCP can be used to configure RMS iLOs as well.

Procedure OCCNE Configure Top of Rack 93180YC-EX Switches has been completed.

All steps are executed from the ssh session of the Bootstrap server.

HPE BladeSystem Onboard Administrator User Guide

Table 3-5 Procedure to configure Addresses for RMS iLOs, OA, EBIPA

Step # Procedure Description
1.

Setup team0.2 interface 
$ nmcli con add con-name team0.2 type vlan id 2 dev team0
$ nmcli con mod team0.2 ipv4.method manual ipv4.addresses 192.168.20.11/24
$ nmcli con up team0.2
2.

Subnet and conf file address

The /etc/dhcp/dhcp.conf file should already have been configured in procedure

OCCNE Configure Top of Rack 93180YC-EX Switches and dhcp started/enabled on the bootstrap server. The second subnet 192.168.20.0 is used to assign addresses for OA and RMS iLOs. The "next-server 192.168.20.11" option is same as the server team0.2 IP address.
3.

Display the dhcpd leases file at /var/lib/dhcpd/dhcpd.leases. The DHCPD lease file will display the DHCP addresses for all RMS iLOs, Enclosure OAs. 
$ cat /var/lib/dhcpd/dhcpd.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.2.5
lease 192.168.20.101 {
  starts 4 2019/03/28 22:05:26;
  ends 4 2019/03/28 22:07:26;
  tstp 4 2019/03/28 22:07:26;
  cltt 4 2019/03/28 22:05:26;
  binding state free;
  hardware ethernet 48:df:37:7a:41:60;
}
lease 192.168.20.103 {
  starts 4 2019/03/28 22:05:28;
  ends 4 2019/03/28 22:07:28;
  tstp 4 2019/03/28 22:07:28;
  cltt 4 2019/03/28 22:05:28;
  binding state free;
  hardware ethernet 48:df:37:7a:2f:70;
}
lease 192.168.20.102 {
  starts 4 2019/03/28 22:05:16;
  ends 4 2019/03/28 23:03:29;
  tstp 4 2019/03/28 23:03:29;
  cltt 4 2019/03/28 22:05:16;
  binding state free;
  hardware ethernet 48:df:37:7a:40:40;
}
lease 192.168.20.106 {
  starts 5 2019/03/29 11:14:04;
  ends 5 2019/03/29 14:14:04;
  tstp 5 2019/03/29 14:14:04;
  cltt 5 2019/03/29 11:14:04;
  binding state free;
  hardware ethernet b8:83:03:47:5f:14;
  uid "\000\270\203\003G_\024\000\000\000";
}
lease 192.168.20.105 {
  starts 5 2019/03/29 12:56:23;
  ends 5 2019/03/29 15:56:23;
  tstp 5 2019/03/29 15:56:23;
  cltt 5 2019/03/29 12:56:23;
  binding state free;
  hardware ethernet b8:83:03:47:5e:54;
  uid "\000\270\203\003G^T\000\000\000";
}
lease 192.168.20.104 {
  starts 5 2019/03/29 13:08:21;
  ends 5 2019/03/29 16:08:21;
  tstp 5 2019/03/29 16:08:21;
  cltt 5 2019/03/29 13:08:21;
  binding state free;
  hardware ethernet b8:83:03:47:64:9c;
  uid "\000\270\203\003Gd\234\000\000\000";
}
lease 192.168.20.108 {
  starts 5 2019/03/29 09:57:02;
  ends 5 2019/03/29 21:57:02;
  tstp 5 2019/03/29 21:57:02;
  cltt 5 2019/03/29 09:57:02;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet fc:15:b4:1a:ea:05;
  uid "\001\374\025\264\032\352\005";
  client-hostname "OA-FC15B41AEA05";
}
lease 192.168.20.107 {
  starts 5 2019/03/29 12:02:50;
  ends 6 2019/03/30 00:02:50;
  tstp 6 2019/03/30 00:02:50;
  cltt 5 2019/03/29 12:02:50;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet 9c:b6:54:80:d7:d7;
  uid "\001\234\266T\200\327\327";
  client-hostname "SA-9CB65480D7D7";
}
server-duid "\000\001\000\001$#\364\344\270\203\003Gim";
lease 192.168.20.107 {
  starts 5 2019/03/29 18:09:47;
  ends 6 2019/03/30 06:09:47;
  cltt 5 2019/03/29 18:09:47;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet 9c:b6:54:80:d7:d7;
  uid "\001\234\266T\200\327\327";
  client-hostname "SA-9CB65480D7D7";
}
lease 192.168.20.108 {
  starts 5 2019/03/29 18:09:54;
  ends 6 2019/03/30 06:09:54;
  cltt 5 2019/03/29 18:09:54;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet fc:15:b4:1a:ea:05;
  uid "\001\374\025\264\032\352\005";
  client-hostname "OA-FC15B41AEA05";
}
lease 192.168.20.106 {
  starts 5 2019/03/29 18:10:04;
  ends 5 2019/03/29 21:10:04;
  cltt 5 2019/03/29 18:10:04;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet b8:83:03:47:5f:14;
  uid "\000\270\203\003G_\024\000\000\000";
  client-hostname "ILO2M2909004B";
}
lease 192.168.20.104 {
  starts 5 2019/03/29 18:10:35;
  ends 5 2019/03/29 21:10:35;
  cltt 5 2019/03/29 18:10:35;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet b8:83:03:47:64:9c;
  uid "\000\270\203\003Gd\234\000\000\000";
  client-hostname "ILO2M2909004F";
}
lease 192.168.20.105 {
  starts 5 2019/03/29 18:10:40;
  ends 5 2019/03/29 21:10:40;
  cltt 5 2019/03/29 18:10:40;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet b8:83:03:47:5e:54;
  uid "\000\270\203\003G^T\000\000\000";
  client-hostname "ILO2M29090048";
4.

Access RMS iLO from the DHCP address with default Administrator password. From the above dhcpd.leases file, find the IP address for the iLO name, the default username is Administrator, the password is on the label which can be pulled out from front of server. Note: The DNS Name on the pull-out label. The DNS Name on the pull-out label should be used to match the physical machine with the iLO IP since the same default DNS Name from the pull-out label is displayed upon logging in to the iLO command line interface, as shown in the example below. 
$ ssh Administrator@192.168.20.104
Administrator@192.168.20.104's password:
User:Administrator logged-in to ILO2M2909004F.labs.nc.tekelec.com(192.168.20.104 / FE80::BA83:3FF:FE47:649C)
iLO Standard 1.37 at  Oct 25 2018
Server Name:
Server Power: On
5.

Create RMS iLO new user. Create new user with customized username and password. 
</>hpiLO-> create /map1/accounts1 username=root password=TklcRoot group=admin,config,oemHPE_rc,oemHPE_power,oemHPE_vm
status=0
status_tag=COMMAND COMPLETED
Tue Apr  2 20:08:30 2019
User added successfully.
6.

Disable the DHCP before able to setup static IP. Setup static failed before DHCP is disabled. 
</>hpiLO-> set /map1/dhcpendpt1 EnabledState=NO
status=0
status_tag=COMMAND COMPLETED
Tue Apr  2 20:04:53 2019
Network settings change applied.
Settings change applied, iLO 5 will now be reset.
Logged Out: It may take several minutes before you can log back in.
CLI session stopped
packet_write_wait: Connection to 192.168.20.104 port 22: Broken pipe
7.

Setup RMS iLO static IP address. After a while after previous step, can login back with the same address(which is static IP now) and new username/password. If don't want to use the same address, go to next step to change the IP address. 
$ ssh <new username>@192.168.20.104
<new username>@192.168.20.104's password: <new password>
User: logged-in to ILO2M2909004F.labs.nc.tekelec.com(192.168.20.104 / FE80::BA83:3FF:FE47:649C)
iLO Standard 1.37 at  Oct 25 2018
Server Name:
Server Power: On
 
</>hpiLO-> set /map1/enetport1/lanendpt1/ipendpt1 IPv4Address=192.168.20.122 SubnetMask=255.255.255.0
 
status=0
status_tag=COMMAND COMPLETED
Tue Apr  2 20:22:23 2019
 
Network settings change applied.
Settings change applied, iLO 5 will now be reset.
Logged Out: It may take several minutes before you can log
back in.
  
CLI session stopped
 
packet_write_wait: Connection to 192.168.20.104 port 22:
Broken pipe
#
8.

Set EBIPA addresses for InterConnect Bays (Enclosure Switches). After login to OA, set EBIPA addressed for the two enclosure switches. The addresses have to be in the subnet with server team0.2 address in order for TFTP to work. 
Set address for each enclosure switch, note the last number 1 or 2 is the interconnect bay number.
  
OA-FC15B41AEA05> set ebipa interconnect 192.168.20.133 255.255.255.0 1
Entering anything other than 'YES' will result in the command not executing.
It may take each interconnect several minutes to acquire the new settings.
Are you sure you want to change the IP address for the specified
interconnect bays? yes
Successfully set 255.255.255.0 as the netmask for interconnect bays.
Successfully set interconnect bay # 1 to IP address 192.168.20.133
For the IP addresses to be assigned EBIPA must be enabled.
  
OA-FC15B41AEA05> set ebipa interconnect 192.168.20.134 255.255.255.0 2
Entering anything other than 'YES' will result in the command not executing.
It may take each interconnect several minutes to acquire the new settings.
Are you sure you want to change the IP address for the specified
interconnect bays? yes
Successfully set 255.255.255.0 as the netmask for interconnect bays.
Successfully set interconnect bay # 2 to IP address 192.168.20.134
For the IP addresses to be assigned EBIPA must be enabled.
9.

Set EBIPA addresses for Blade Servers. Set EBIPA addressed for all the blade servers. The addresses are in the same subnet with first server team0.2 address and enclosure switches. 
OA-FC15B41AEA05> set ebipa server 192.168.20.141 255.255.255.0 1-16
Entering anything other than 'YES' will result in the command not executing.
Changing the IP address for device (iLO) bays that are enabled
causes the iLOs in those bays to be reset.
Are you sure you want to change the IP address for the specified
device (iLO) bays? YES
Successfully set 255.255.255.0 as the netmask for device (iLO) bays.
Successfully set device (iLO) bay # 1 to IP address 192.168.20.141
Successfully set device (iLO) bay # 2 to IP address 192.168.20.142
Successfully set device (iLO) bay # 3 to IP address 192.168.20.143
Successfully set device (iLO) bay # 4 to IP address 192.168.20.144
Successfully set device (iLO) bay # 5 to IP address 192.168.20.145
Successfully set device (iLO) bay # 6 to IP address 192.168.20.146
Successfully set device (iLO) bay # 7 to IP address 192.168.20.147
Successfully set device (iLO) bay # 8 to IP address 192.168.20.148
Successfully set device (iLO) bay # 9 to IP address 192.168.20.149
Successfully set device (iLO) bay #10 to IP address 192.168.20.150
Successfully set device (iLO) bay #11 to IP address 192.168.20.151
Successfully set device (iLO) bay #12 to IP address 192.168.20.152
Successfully set device (iLO) bay #13 to IP address 192.168.20.153
Successfully set device (iLO) bay #14 to IP address 192.168.20.154
Successfully set device (iLO) bay #15 to IP address 192.168.20.155
Successfully set device (iLO) bay #16 to IP address 192.168.20.156
For the IP addresses to be assigned EBIPA must be enabled.
OA-FC15B41AEA05>
10.

Add New User for OA. Create new user, set access level as ADMINISTRATOR, and assign access to all blades and OAs. After that, the username and password can be used to access OAs. 
OA-FC15B41AEA05> ADD USER <username>
New Password: ********
Confirm     : ********
User "<username>" created.
You may set user privileges with the 'SET USER ACCESS' and 'ASSIGN' commands.
 
OA-FC15B41AEA05> set user access <username> ADMINISTRATOR
 
"<username>" has been given administrator level privileges.
 
OA-FC15B41AEA05> ASSIGN SERVER ALL <username>
 
<username> has been granted access to the valid requested bay(s)
 
OA-FC15B41AEA05> ASSIGN OA <username>
 
<username> has been granted access to the OA.
11.

From OA, go to each blade with "connect server <bay number>", add New User for each blade. 
OA-FC15B41AEA05> connect server 4
 
Connecting to bay 4 ...
User:OAtmp-root-5CBF2E61 logged-in to ILO2M290605KP.(192.168.20.144 / FE80::AF1:EAFF:FE89:460)
iLO Standard Blade Edition 1.37 at  Oct 25 2018
Server Name:
Server Power: On
 
</>hpiLO->
 
</>hpiLO->  create /map1/accounts1 username=root password=TklcRoot group=admin,config,oemHPE_rc,oemHPE_power,oemHPE_vm
 
status=2
status_tag=COMMAND PROCESSING FAILED
error_tag=COMMAND SYNTAX ERROR
Tue Apr 23 16:18:58 2019
User added successfully.
12.

Change to static IP on OA. In order not reply on DHCP and make the OA address stable, change to static IP.

Note: After the following change, the OA session will be stuck due to the address change, make another server session ready to ssh with the new IP address and new root user. 

OA-FC15B41AEA05> SET IPCONFIG STATIC 1 192.168.20.131 255.255.255.0
Static IP settings successfully updated.
These setting changes will take effect immediately.
  
OA-FC15B41AEA05> SET IPCONFIG STATIC 2 192.168.20.132 255.255.255.0
Static IP settings successfully updated.
These setting changes will take effect immediately.
OA-FC15B41AEA05>
Previous
Previous 		Next
Next
Go To Table Of Contents
Contents