topic Re: Unable to access OnBoard Administrator, but it can be pinged. in BladeSystem - General

Unable to access OnBoard Administrator, but it can be pinged.

Ardihikaru — Wed, 12 Apr 2017 07:41:37 GMT

Recently, our team have got an HP Server (Blade C3000) which had not been used for months. Initially, this Server had been configured once (by the other team) before we had it. It has complete components except the OA Module in Bay 2 (Slot in the Bay 1 is empty).

Until now, we have successfully configured it like this:

It has 1x OA Module which is located in Bay 2. Until now, we do not know whether OA Module in Bay 1 is exist or not. The module has: (a) upLink, (b) downLink, (c) OA 1, and (d) OA 2.
All of the components are installed correctly (Checked in Health Summary)
For the networking we use Mikrotik CRS226 and set IP in this class: 10.252.37.*
AO 2 port is connected to the RouterBoard (Mikrotik)
The IPs are configured as follows: OA 2 (10.252.37.200), Blade 1 (10.252.37.201), Blade 2 (10.252.37.202), Blade 3 (10.252.37.203)
Telnet, SSH, and Web-based (iLO) of each Blade is working properly (tested)
OA's IP (10.252.37.200) can be pinged successfully.

With this setup, I face some problems:

Though OA's IP can be pinged, we unable to access it through: Serial Port, Telnet, SSH, or either Web.
Due to this issue, we tried to Reset it into factory default, yet, we unable to access it through Serial Port

Until now, we have search similar issues, but still not yet found the solutions. Maybe anyone here ever had similar problems or maybe someone has solution for this issues.

Here I provided some pictures: https://goo.gl/Iel8Cz (Tried to upload .jpg files, but it keeps saying "does not have a valid extension")

Regards,
Ardi

Re: Unable to access OnBoard Administrator, but it can be pinged.

Torsten. — Wed, 12 Apr 2017 13:21:07 GMT

Sure you used the correct settings for serial connection?

Parameter                                   Value
Transmission rate                           9600 bps
Data bits                                           8
Parity                                               None
Stop bits    1
Protocol                                            None

and a null modem cable?

Re: Unable to access OnBoard Administrator, but it can be pinged.

Phillip Thayer — Tue, 16 May 2017 20:33:45 GMT

I know it seems trivial, but did you try to swap the OAS and put it in OA slot 1? Then check the LKCD panel and make sure it is configured with the proper IP, Subnet and Gateway.

Phil

Re: Unable to access OnBoard Administrator, but it can be pinged.

Ardihikaru — Tue, 16 May 2017 23:15:40 GMT

I tried it but the OA Module's shape/body seems different. It looks like
that the module is designed differently, Module which should be located in
the left body and located in the right body of the Blade.

Yesterday I was able to connect to the OA Administrator through SERIAL PORT
and able to login and configure it. (OA is currently attached in BAY 2)
I checked its status, and it showed that HTTP is enabled, yet, the web page
still not accessible (Via IP in the browser). When I checked it more
detail, it did not has any open port compared with the other 3 web view of
iLO 1,2,&3, in which they have 3 ports opened each (80,xx,xx).

Alternatively, I am looking for the way how to configure the VLAN and any
other configuration through this CLI. Any reference is okay to help me to
solve this issue.

Regards,
Ardi