10-17-2012 10:20 AM
I am new to blade server.
We have plugged in ilo1and ilo2 are connected to ethernet ports.
This ports are assigned IP address using dhcp.
I can do a telnet to the OA IP addresses i,e both active and standby.
I can also get the login page for ILO1 and ILO2 not sure where to get the credential for the same.
Also I am unable to open the OA webinterface.
Your assistance for getting the above two appointment is highly appreciated
Thank you for sparing some of your time in advance.
Solved! Go to Solution.
10-17-2012 11:15 PM
Reg. the ilo credentials: there is a system maintanence switch on the systemboard of each blade. Locate it and set the switch 1 (
10-18-2012 12:56 AM
You should assign/configure an IP for the OA using the Insight Display.
Here is the OA user guide.
10-18-2012 04:07 AM
IP is assigned to OA and I can also do ssh and telnet to the active and standby OA.
However when I try to open the OA Webpage i.e https://ip-address it is not accessible
10-18-2012 04:48 AM
telnet OA-IP 80
Maybe a browser issue, did you disable the proxy?
Hope this helps!
There are only 10 types of people in the world -
those who understand binary, and those who don't.
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
10-18-2012 11:06 PM
Your FW version is pretty old. The current one is 3.60. An OA update can resolve the issue. Here is an advisory for a similiar issue.
10-18-2012 11:39 PM
also one thing you can try is to reset the OA if you can access it through SSH:
1) login with SSH tool to active OA
2) execute command "restart OA"
after 1-2 minutes try to access web GUI again...
10-18-2012 11:41 PM
Ah and Customer Advisory c01077618 could maybe also be an option:
(You have other error messages but maybe this is the same issue)
10-19-2012 03:06 AM
1. I had similar problem before, when active oa and standby oa were configured in the same network. So, my suggestions :
Try to unplag standby OA and see what will happen
2. Rarely I experienced stucking of OA web interface, and I reseted it. Use ssh login on active OA and run command
restart oa active
(run help restart in questions)