Closed
Bug 946887
Opened 12 years ago
Closed 12 years ago
configure ilo for pp-zlb11.phx.mozilla.net
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: van, Unassigned)
Details
motherboard was replaced in 905276 so iLO needs to be reconfigured.
Reporter | ||
Comment 1•12 years ago
|
||
spoke to aj and this can be done remotely. he's going to write a quick guide and add it to mana.
colo-trip: --- → phx1
Reporter | ||
Comment 2•12 years ago
|
||
iLo cable might never been ran, having the tech come back for a 2nd look. Otherwise we'll have to run the cable when we get on site.
On 12/5/13 1:17 PM, Herrera, Cesar wrote:
> I should have mentioned to you that I didn't see any cable plugged into the iLO port. The system only had the 2 fiber cables connected to the system. I wasn't sure which cable it was for the iLO but I figured someone else was working on this system since it had a video and USB cables attached to the front. I can be there tomorrow morning again at 10am, no problem.
>
> Thank you,
>
>
> Cesar Herrera
> Field Service Engineer
> ESSN - Arizona
> cesar.g.herrera@hp.com
> cell 623.208.9280
Comment 3•12 years ago
|
||
Howto - configure ilo from within OS (linux);
# dump current configuration
sudo hponcfg -w current_ilo.cfg
cp current_ilo.cfg new_ilo.cfg
vi new_ilo.cfg
Update the following (replace $ variables with actual values):
# For network, search for; MOD_NETWORK_SETTINGS
# then update the following:
IP_ADDRESS VALUE = "$IP"
SUBNET_MASK VALUE = "$NETMASK"
GATEWAY_IP_ADDRESS VALUE = "$GW"
PRIM_DNS_SERVER value = ""
DHCP_ENABLE VALUE = "N"
PRIM_WINS_SERVER value = "0.0.0.0"
# Add user for ilo, search for <USER_INFO MODE="write">
# Add the following right after;
<ADD_USER
USER_NAME = "$REPLACEWITHACTUALUSER"
USER_LOGIN = "$REPLACEWITHACTUALUSER"
PASSWORD = "$REPLACEWITHACTUALPASS">
<ADMIN_PRIV value = "Y"/>
<REMOTE_CONS_PRIV value = "Y"/>
<RESET_SERVER_PRIV value = "Y"/>
<VIRTUAL_MEDIA_PRIV value = "Y"/>
<CONFIG_ILO_PRIV value = "Y"/>
</ADD_USER>
Save the file, then run;
$ sudo hponcfg -f new_ilo.cfg
(wait a few minutes for ilo to reset)
then confirm ilo network access/login.
This was done on the host but seems iLO ethernet cable is not connected, so OOB IP still down.
Comment 4•12 years ago
|
||
Comment 5•12 years ago
|
||
And while we are on it... is the BMC firmware in a new version? Just sayin' :)
Comment 6•12 years ago
|
||
:michal` - iLo firmware is updated automatically on modern HP Linux boxes that run puppet.
Comment 7•12 years ago
|
||
I don't know what the state/requirement for the iLo ethernet interface is but this *was* working before the HP tech was there. It just broke every time an iLo firmware update was done and had to be manually fixed remotely by reinstalling the firmware update via ftp recovery.
Comment 8•12 years ago
|
||
OOB cable was ran but no active lights came on. I've replaced the cat 5 cable and it is now lit up.
iLO should now be reachable.
ping 10.8.0.204
PING 10.8.0.204 (10.8.0.204): 56 data bytes
64 bytes from 10.8.0.204: icmp_seq=0 ttl=254 time=82.080 ms
64 bytes from 10.8.0.204: icmp_seq=1 ttl=254 time=90.198 ms
ssh 10.8.0.204
The authenticity of host '10.8.0.204 (10.8.0.204)' can't be established.
DSA key fingerprint is 41:89:f2:00:8d:9b:52:d8:42:5e:d0:e1:0c:50:df:fd.
Are you sure you want to continue connecting (yes/no)?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•