BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

Moving ILO/OA to Out-of-Band (OOB) network

 
chuckk281
Trusted Contributor

Moving ILO/OA to Out-of-Band (OOB) network

Mark had a customer question:

 

*************

 

One of my customers would like to move there ILO connections on numerous C7K blade servers to an OOB network. Presently, all SERVER/OA/ILO network ports are on the same subnet. The C7K chassis have CISCO Catalyst Interconnect 3020 switches for the servers production LAN. Most of the servers are older and use ILO2, a few are ILO3.

 

If they move the ILOs all to an OOB network, should they also move the OA? I think they should, but is it required? Can anyone recommend a doc on doing this? Or is it a matter of changing the values within the “Enclosure Settings” from the OA? If they move the OA to the OOB network, is there a certain sequence on what should be changed first, OA’s then ILO’s?

They are using EBIPA with static addresses.

 

***************

 

Reply from Dan:

 

************

 

I’ll assume you mean EBIPA since Static would ignore EBIPA/DHCP.

 

Static = Each Server’s iLO is Set to a Static IP.  DHCP and EBIPA ignored.

EBIPA = Each Server’s iLO is Set to DHCP, OA is providing/allocating IP Addresses via EBIPA

DHCP = Each Server’s iLO is Set to DHCP, External DHCP Server is providing IP Addresses (Disable EBIPA in the OA to avoid conflicts and use DHCP Reservations to allocate IPs to specific iLOs.)

 

Here is a basic script to change 16 blades and the OAs to new IPs.

 

 

#Set Enclosure Bay IP Addressing (EBIPA) Information for Device Bays

#NOTE: SET EBIPA commands are only valid for OA v3.00 and later

 

SET EBIPA SERVER GATEWAY 10.1.42.254 1-16

SET EBIPA SERVER DOMAIN "corp.mydomain.com" 1-16

 

SET EBIPA SERVER 10.1.42.101 255.255.255.0 1

SET EBIPA SERVER 10.1.42.102 255.255.255.0 2

SET EBIPA SERVER 10.1.42.103 255.255.255.0 3

SET EBIPA SERVER 10.1.42.104 255.255.255.0 4

SET EBIPA SERVER 10.1.42.105 255.255.255.0 5

SET EBIPA SERVER 10.1.42.106 255.255.255.0 6

SET EBIPA SERVER 10.1.42.107 255.255.255.0 7

SET EBIPA SERVER 10.1.42.108 255.255.255.0 8

SET EBIPA SERVER 10.1.42.109 255.255.255.0 9

SET EBIPA SERVER 10.1.42.110 255.255.255.0 10

SET EBIPA SERVER 10.1.42.111 255.255.255.0 11

SET EBIPA SERVER 10.1.42.112 255.255.255.0 12

SET EBIPA SERVER 10.1.42.113 255.255.255.0 13

SET EBIPA SERVER 10.1.42.114 255.255.255.0 14

SET EBIPA SERVER 10.1.42.115 255.255.255.0 15

SET EBIPA SERVER 10.1.42.116 255.255.255.0 16

 

ENABLE EBIPA SERVER 1-16

 

 

#Set Network Information

#NOTE: Setting your network information through a script while

#      remotely accessing the server could drop your connection.

#      If your connection is dropped this script may not execute to conclusion.

SET OA NAME 1 MyEnc01a

SET IPCONFIG STATIC 1 10.1.42.117 255.255.255.0 10.1.1.11 10.1.1.12 0.0.0.0

SET OA NAME 2 MyEnc01a

SET IPCONFIG STATIC 2 10.1.42.118 255.255.255.0 10.1.1.11 10.1.1.12 0.0.0.0

 

Reference the OA CLI Guide if you need to break down any of those commands.

 

**************

 

Questions?

 

1 REPLY
Jimmy Vance
HPE Pro

Re: Moving ILO/OA to Out-of-Band (OOB) network


chuckk281 wrote:

Mark had a customer question:

 If they move the ILOs all to an OOB network, should they also move the OA?


Since the iLO's are accessed via the OA port, it is kind of hard to move one without the other.

 




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!