[Info-vax] Integrity iLO Configuration?

[Norbert Schönartz]

I have worked with many different VAX, Alpha and three Itanium (rx2620, 
rx2660 ans rx2800i6) systems. Once you know iLO, wou don't want to miss 
it. And it is really not that complicated.

For some iLO variants ssh support required an extra license, so maybe 
your machine does not support it. Then I recommend using telnet, if your 
environment is sufficiently isolated from the internet.

However, for both ssh and telnet you must have the login credentials and 
know the network configuration. If you don't, you should use the serial 
iLO console which always works (normally at 9600 baud) if you have 
physical access to the system. From the serial console you can then set 
the parameters for ssh or telnet access through the network port.

For the rx2620 you need a special cable to access the serial port since 
the serial port is part of a special connector which has some other 
additional functionality (don't rember which). Maybe I could find out 
how to solder a suitable cable if you need it. For the rx2660 and rx2800 
the serial iLO port has a standard 9 pin connector, if I remember correctly.

And I would use RAID unless the machine is a rx2660 with only the 
onboard RAID controller which has very poor performance. The performance 
with a good RAID controller is much better and it is really easy to 
recover from a disk failure even if your backup is not quite current. 
Boot the distribution media and use MSA$UTIL to configure the RAID setup 
which best fits your needs. And believe me, the noise of the disks is 
negigible compared to the noise of the system.

Am 27.06.2021 um 05:41 schrieb Dave Froble:
> On 6/26/2021 10:33 PM, Stephen Hoffman wrote:
>> On 2021-06-27 01:42:04 +0000, Dave Froble said:
>>
>>> Ok, back to the iLO....
>>>
>>> My next question is "what good methods are there for learning to talk
>>> to the iLO?"  If I got to play with this beast, at least I can try to
>>> do it correctly.
>>
>> Setup and general info for using iLO 2:
>> http://h10032.www1.hp.com/ctg/Manual/c00553302.pdf
>>
>> Connect the iLO port to the network, configure the iLO for a static IP
>> address either outside of your DHCP address pool or coordinated with
>> your DHCP by MAC address, disable IMPI access on the iLO, and then use
>> ssh to access the iLO. If your ssh is new enough, you'll have to
>> downgrade the connection. If your ssh is outdated, it'll probably also
>> not notice the ssh problems with the iLO. Probably want to reset the
>> default passwords and/or add your own iLO admin user, too.
>>
>> From a semi-recent Unix or Linux or macOS system: ssh -o
>> HostKeyAlgorithms=ssh-rsa,ssh-dss -o
>> KexAlgorithms=diffie-hellman-group1-sha1 -o Ciphers=aes128-cbc,3des-cbc
>> -o MACs=hmac-md5,hmac-sha1 User at Server.Example.Com
>>
>> telnet access is also possible, with all the issues incumbent in that 
>> path.
>>
>> How to disable IPMI access from the management processor command menu:
>> MP:CM> sa -lanipmi d
>>
>> Remote access monitoring tools can or do require IPMI be enabled,
>> unfortunately.
>>
>> iLO 2 scripting: http://h10032.www1.hp.com/ctg/Manual/c02237707.pdf
>>
>> Some of the iLO docs around are for ProLiant, so you might have to
>> ignore some parts of the doc related to that.
>>
>>
> 
> Thanks ...
> 
> My intentions are to change the iLO IP address to be accessable from my 
> internal network, then after looking at what is there, get VMS V8l.4 2L3 
> and the latest TCP/IP, install on system disk, and clear the other 
> disks.  Currently has a RAID set-up, but I will do away with that. 
> Perhaps remove most of the disk drives, unless I can shut them off while 
> still installed in the box.
> 
> One system disk, one disk for backup of system, and one disk with VMS 
> distribution image.  Should be all I need.


-- 
Norbert Schönartz