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

OA, individual blade and virtual connect IP change - URGENT HELP

SOLVED
Go to solution
akash1980
Advisor

OA, individual blade and virtual connect IP change - URGENT HELP

Hello, can someone please confirm the approach to change OA, individual blade and virtual connect IP? My proposed approach is as follows. Please confirm you see any issues.

 

Note: From networking point of view, all IPs are going to be in same subnet. We are configuring two switch ports with new subnet and as part of the implementation we will connect 2x OA to new ports.

 

Step1: Change OA IP.

-          Login to HP OA.

-          Navigate to enclosure TCP/IP settings

-          Change standby on-board administrator ip to new one.

-          Connect network cable to newly allocated port

-          Make sure that able to ping new IP.

-          Failover OA to standby.

-          Change active OA IP to new one.

-          Make sure that able to ping new IP.

-          Fail back OA to its actual active OA.

Step 2: Change individual blade IP.

-          Login to HP OA.

-          Navigate to Enclosure Bay IP Addressing

-          Change Device bay IP address to new ones according as allocated.

-          Make sure that able to ping new IPs.

Steps 3: Change VC IP.

-          Login to HP OA

-          Navigate to enclosure TCP/IP settings- Interconnect bays

-          Change Device bay 1,2,3 and 4 IPs to new as pre allocated.

-          Make sure that able to ping new IPs.

 

3 REPLIES
Psychonaut
Respected Contributor
Solution

Re: OA, individual blade and virtual connect IP change - URGENT HELP

Depending on your network and router config you could lose connectivity to the iLO and Interconnects as soon as you flip to that new IP and go from Standby to Active.  This is from the OA 3.60 user manual:

 

"Onboard Administrator firmware bridges the client traffic to the enclosure from the management port to the

internal enclosure management network if the destination IP address is not Onboard Administrator. Onboard
Administrator creates a route table entry for each server iLO IP address in an enclosure. This allows Onboard
Administrator to conduct IP communications with that iLO. These iLO route table entries enable you to
configure each iLO network in a different subnet than Onboard Administrator. Each iLO is configured with
a valid gateway on its subnet that is accessible through Onboard Administrators external management port
connection. Routers are needed on the network connected to Onboard Administrator management port in
order to provide the multiple subnets and gateways on the management network. Use of different subnets to
attempt to isolate iLOs and Onboard Administrator management is not complete isolation of those networks."

 

I would use the standby to test connectivity for both new ports.  Then do a mass change over with the interconnects then the iLO IP's.  Making sure no one needs to connect while you are changing over. 

 

akash1980
Advisor

Re: OA, individual blade and virtual connect IP change - URGENT HELP

Thank you very much.
We have OA 3.11. Hope this will go smooth.
akash1980
Advisor

Re: OA, individual blade and virtual connect IP change - URGENT HELP

I managed to change IPs successfully and documented above steps with some other considerations to help others.

 

http://virtualcloudzz.blogspot.com.au/2012/11/how-to-change-hp-ilo-ips-for-oa-blades_23.html

 

 

Thanks,