hi, I can ssh to the ILO with out an issue, but when I try to browse to it no luck, and when I try to use parstatus to connect again no luck. we had another 8640 that worked fine, when I ran parstatus. could it be a setting inside the ILO that isn't set up or a faulty module?

thanks
pc

On Tuesday, June 6, 2023 at 3:30:44 PM UTC-4, pcov...@gmail.com wrote:
> hi, I can ssh to the ILO with out an issue, but when I try to browse to it no luck, and when I try to use parstatus to connect again no luck. we had another 8640 that worked fine, when I ran parstatus. could it be a setting inside the ILO that isn't set up or a faulty module?
>
> thanks
> pc
pc,

If I recall correctly, there are separate settings that enable the various protocols. Check the HELP text or the manual. There is also the possibility that the LAN segment has a configured limitation.

EFI help is fairly useful in identifying the command.

Been in similar situations with client systems. Best procedure is to check each and every relevant setting.

- Bob Gezelter, http://www.rlgsc.com

On Tuesday, June 6, 2023 at 8:30:41 PM UTC-4, Bob Gezelter wrote:
> On Tuesday, June 6, 2023 at 3:30:44 PM UTC-4, pcov...@gmail.com wrote:
> > hi, I can ssh to the ILO with out an issue, but when I try to browse to it no luck, and when I try to use parstatus to connect again no luck. we had another 8640 that worked fine, when I ran parstatus. could it be a setting inside the ILO that isn't set up or a faulty module?
> >
> > thanks
> > pc
> pc,
>
> If I recall correctly, there are separate settings that enable the various protocols. Check the HELP text or the manual. There is also the possibility that the LAN segment has a configured limitation.
>
> EFI help is fairly useful in identifying the command.
>
> Been in similar situations with client systems. Best procedure is to check each and every relevant setting.
>
> - Bob Gezelter, http://www.rlgsc.com

I took out any network limitations with a 4 port switch and a single machine still the same issue.

when I go into CM and issue HE I'm not seeing anything obvious for a setting.

thanks
pc

On Wednesday, June 7, 2023 at 9:23:20 AM UTC-4, pcov...@gmail.com wrote:
> On Tuesday, June 6, 2023 at 8:30:41 PM UTC-4, Bob Gezelter wrote:
> > On Tuesday, June 6, 2023 at 3:30:44 PM UTC-4, pcov...@gmail.com wrote:
> > > hi, I can ssh to the ILO with out an issue, but when I try to browse to it no luck, and when I try to use parstatus to connect again no luck. we had another 8640 that worked fine, when I ran parstatus. could it be a setting inside the ILO that isn't set up or a faulty module?
> > >
> > > thanks
> > > pc
> > pc,
> >
> > If I recall correctly, there are separate settings that enable the various protocols. Check the HELP text or the manual. There is also the possibility that the LAN segment has a configured limitation.
> >
> > EFI help is fairly useful in identifying the command.
> >
> > Been in similar situations with client systems. Best procedure is to check each and every relevant setting.
> >
> > - Bob Gezelter, http://www.rlgsc.com
> I took out any network limitations with a 4 port switch and a single machine still the same issue.
>
> when I go into CM and issue HE I'm not seeing anything obvious for a setting.
>
> thanks
> pc
here is the error

C:\Users\Administrator>parstatus -u Admin:PASSWORD -h 10.xxx.xx.xxx
Note: No action specified. Default behavior is display all.
Error: Unable to connect to the nPar Provider on 10.xxx.xx.xxx.
1. Verify that the HP nPar Provider (WMINParProvider on Windows) is installed and running on 10.xxx.xx.xxx.
2. Verify that you are logged-in to the correct account (or have provided the correct username & password) to access the provider on 10.xxx.xx.xxx.
3. Verify that you have copied the server's SSL certificate from 10.xxx.xx.xxx to the trusted certificate store on the local machine (see man/help/readme).
Cannot connect to 10.xxx.xx.xxx:5989. Connection failed.

C:\Users\Administrator>parstatus -g Admin:PASSWORD -h 10.xxx.xx.xxx
Note: No action specified. Default behavior is display all.
Note: The -g option may require up to 2 minutes to complete. Please wait....
Error: Failed to connect to target partition or complex.

On Wednesday, June 7, 2023 at 1:09:29 PM UTC-4, pcov...@gmail.com wrote:
> On Wednesday, June 7, 2023 at 9:23:20 AM UTC-4, pcov...@gmail.com wrote:
> > On Tuesday, June 6, 2023 at 8:30:41 PM UTC-4, Bob Gezelter wrote:
> > > On Tuesday, June 6, 2023 at 3:30:44 PM UTC-4, pcov...@gmail.com wrote:
> > > > hi, I can ssh to the ILO with out an issue, but when I try to browse to it no luck, and when I try to use parstatus to connect again no luck. we had another 8640 that worked fine, when I ran parstatus. could it be a setting inside the ILO that isn't set up or a faulty module?
> > > >
> > > > thanks
> > > > pc
> > > pc,
> > >
> > > If I recall correctly, there are separate settings that enable the various protocols. Check the HELP text or the manual. There is also the possibility that the LAN segment has a configured limitation.
> > >
> > > EFI help is fairly useful in identifying the command.
> > >
> > > Been in similar situations with client systems. Best procedure is to check each and every relevant setting.
> > >
> > > - Bob Gezelter, http://www.rlgsc.com
> > I took out any network limitations with a 4 port switch and a single machine still the same issue.
> >
> > when I go into CM and issue HE I'm not seeing anything obvious for a setting.
> >
> > thanks
> > pc
> here is the error
>
> C:\Users\Administrator>parstatus -u Admin:PASSWORD -h 10.xxx.xx.xxx
> Note: No action specified. Default behavior is display all.
> Error: Unable to connect to the nPar Provider on 10.xxx.xx.xxx.
> 1. Verify that the HP nPar Provider (WMINParProvider on Windows) is installed and running on 10.xxx.xx.xxx.
> 2. Verify that you are logged-in to the correct account (or have provided the correct username & password) to access the provider on 10.xxx.xx.xxx.
> 3. Verify that you have copied the server's SSL certificate from 10.xxx.xx.xxx to the trusted certificate store on the local machine (see man/help/readme).
> Cannot connect to 10.xxx.xx.xxx:5989. Connection failed.
>
> C:\Users\Administrator>parstatus -g Admin:PASSWORD -h 10.xxx.xx.xxx
> Note: No action specified. Default behavior is display all.
> Note: The -g option may require up to 2 minutes to complete. Please wait....
> Error: Failed to connect to target partition or complex.

as an update to this I did update the cert, still haven't figured out how to download it, if it's even possible!

On 2023-06-12 15:53:20 +0000, pcoviello@gmail.com said:

> as an update to this I did update the cert, still haven't figured out
> how to download it, if it's even possible!

For ssh and certificates within iLO 2 itself, see page 45ff:
http://h10032.www1.hp.com/ctg/Manual/c00553302.pdf#page45

If it's generating its own self-signed cert as I'd expect by default,
that cert might need to be re-generated as some clients are getting
cranky about certificate details and lifetimes.

I haven't run parstatus, but it wouldn't surprise to learn it's based
on this: https://github.com/HewlettPackard/python-ilorest-library

As an alternative for remotely scripting iLO:
https://seveas.github.io/python-hpilo/index.html

And iLO 2 ssh connections will need a severe downgrade, as has been
discussed here before. I've previously posted a "sethost" ssh shell
script as an example of that too, and that script can be tailored for
other connections including (ugh) telnet.

Semi-related iLO "fun"...

An unfixed iLO 2 boo-boo:
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04197764
To disable that access path: MP:CM> sa -lanipmi d

An iLO 4 boo-boo:
https://airbus-seclab.github.io/ilo/SSTIC2018-Slides-EN-Backdooring_your_server_through_its_BMC_the_HPE_iLO4_case-perigaud-gazet-czarny.pdf

curl -H "Connection: AAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
(haven't tried this on iLO 2)

--
Pure Personal Opinion | HoffmanLabs LLC

On Monday, June 12, 2023 at 1:11:58 PM UTC-4, Stephen Hoffman wrote:
> On 2023-06-12 15:53:20 +0000, pcov...@gmail.com said:
>
> > as an update to this I did update the cert, still haven't figured out
> > how to download it, if it's even possible!
> For ssh and certificates within iLO 2 itself, see page 45ff:
> http://h10032.www1.hp.com/ctg/Manual/c00553302.pdf#page45
>
> If it's generating its own self-signed cert as I'd expect by default,
> that cert might need to be re-generated as some clients are getting
> cranky about certificate details and lifetimes.
>
> I haven't run parstatus, but it wouldn't surprise to learn it's based
> on this: https://github.com/HewlettPackard/python-ilorest-library
>
> As an alternative for remotely scripting iLO:
> https://seveas.github.io/python-hpilo/index.html
>
> And iLO 2 ssh connections will need a severe downgrade, as has been
> discussed here before. I've previously posted a "sethost" ssh shell
> script as an example of that too, and that script can be tailored for
> other connections including (ugh) telnet.
>
> Semi-related iLO "fun"...
>
> An unfixed iLO 2 boo-boo:
> https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04197764
> To disable that access path: MP:CM> sa -lanipmi d
>
> An iLO 4 boo-boo:
> https://airbus-seclab.github.io/ilo/SSTIC2018-Slides-EN-Backdooring_your_server_through_its_BMC_the_HPE_iLO4_case-perigaud-gazet-czarny.pdf
>
> curl -H "Connection: AAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
> (haven't tried this on iLO 2)
>
> --
> Pure Personal Opinion | HoffmanLabs LLC

thanks for this... though the web option isn't working and looking through the doc for CLI...

Try an old windows 7 box that wasn't recently updated and then connect to it
SSH and Browsers all fail here when I try to connect to an rx2660. New
SSL/TLS requirements prevent connection
Pain in the aXX

On 6/12/2023 2:00 PM, pcoviello@gmail.com wrote:
> On Monday, June 12, 2023 at 1:11:58 PM UTC-4, Stephen Hoffman wrote:
>> On 2023-06-12 15:53:20 +0000, pcov...@gmail.com said:
>>
>>> as an update to this I did update the cert, still haven't figured out
>>> how to download it, if it's even possible!
>> For ssh and certificates within iLO 2 itself, see page 45ff:
>> http://h10032.www1.hp.com/ctg/Manual/c00553302.pdf#page45
>>
>> If it's generating its own self-signed cert as I'd expect by default,
>> that cert might need to be re-generated as some clients are getting
>> cranky about certificate details and lifetimes.
>>
>> I haven't run parstatus, but it wouldn't surprise to learn it's based
>> on this: https://github.com/HewlettPackard/python-ilorest-library
>>
>> As an alternative for remotely scripting iLO:
>> https://seveas.github.io/python-hpilo/index.html
>>
>> And iLO 2 ssh connections will need a severe downgrade, as has been
>> discussed here before. I've previously posted a "sethost" ssh shell
>> script as an example of that too, and that script can be tailored for
>> other connections including (ugh) telnet.
>>
>> Semi-related iLO "fun"...
>>
>> An unfixed iLO 2 boo-boo:
>> https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04197764
>> To disable that access path: MP:CM> sa -lanipmi d
>>
>> An iLO 4 boo-boo:
>> https://airbus-seclab.github.io/ilo/SSTIC2018-Slides-EN-Backdooring_your_server_through_its_BMC_the_HPE_iLO4_case-perigaud-gazet-czarny.pdf
>>
>> curl -H "Connection: AAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
>> (haven't tried this on iLO 2)
>>
>> --
>> Pure Personal Opinion | HoffmanLabs LLC
>
> thanks for this... though the web option isn't working and looking through the doc for CLI...
>

On 2023-07-11, David Turner <dturner@islandco.com> wrote:
> Try an old windows 7 box that wasn't recently updated and then connect to it
> SSH and Browsers all fail here when I try to connect to an rx2660. New
> SSL/TLS requirements prevent connection
> Pain in the aXX
>

Security can be a pain sometimes. However, the alternative is far worse.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 2023-07-11 09:15:05 +0000, David Turner said:

> Try an old windows 7 box that wasn't recently updated and then connect
> to it SSH and Browsers all fail here when I try to connect to an
> rx2660. New SSL/TLS requirements prevent connection
> Pain in the aXX

Ayup.

Under-maintained and unmaintained configurations—Windows prior to 10,
iLO 2 and 3, OpenVMS itself up to the work by VSI—will block access
when connecting from or to maintained configurations.

We're on a treadmill of upgrades; software and hardware.

If what you're connecting from is more recent—Windows 7, not so
much—then ssh connections can be downgraded. ssh servers you control
can also be downgraded. Otherwise, yes, blockages arise.

The following sethost bash might work with WSL or WSL2 on Windows too,
not that I have a way to test that configuration. Check the local
Windows ssh client for its particularly connection upgrade and
downgrade details.

It is also possible to add host-specific connection scripts into the
local ssh configuration files. Local preference is to avoid that,
though it does work.

Windows 8.1 is 2013, 8 was 2012, 7 from 2009 with its last service pack
in 2011. (That's all before VSI even existed, too.)

#!/bin/bash
# sethost script to connect to remote systems, using whatever
# connection protocol and command is appropriate for the
# target server. ssh, telnet, whatever.
# # with ssh, this script can be substituted for an entry added into
# the ssh configuration file to downgrade the connection. When
# connecting into HPE OpenVMS servers:
# #Host server.example.com
# HostKeyAlgorithms ssh-dss
# KexAlgorithms diffie-hellman-group1-sha1
# # This as most HPE OpenVMS systems and iLO have too-old
# ssh servers. VSI OpenVMS does better, here.
# # The related ssh downgrade command follows:
# # 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@Server.Example.Com
# if [ "$1" = "-h" ]
then
echo "Issues the ssh command to the specified host"
echo "usage: $0 [option] [host]"
echo " -h display this help text"
exit
fi

host=`echo $1 | tr a-z A-Z`
case "${host}" in
FOO)
ssh -q hoffman@foo.example.net
;;
CLUSTER | VMS1 | VMS2 )
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 Hoffman@Example.Org
;;
IOT)
telnet hoffman@iot.example.net
;;
* )
echo "Unrecognized destination host $1 specified"
;;
esac
echo " "

--
Pure Personal Opinion | HoffmanLabs LLC

On 7/11/2023 9:02 AM, Simon Clubley wrote:
> On 2023-07-11, David Turner <dturner@islandco.com> wrote:
>> Try an old windows 7 box that wasn't recently updated and then connect to it
>> SSH and Browsers all fail here when I try to connect to an rx2660. New
>> SSL/TLS requirements prevent connection
>> Pain in the aXX
>>
>
> Security can be a pain sometimes. However, the alternative is far worse.
>
> Simon.
>

Gee Simon, just how much of a pain is being unable to continue to use a system?
Can anything be worse?

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 2023-07-11, Dave Froble <davef@tsoft-inc.com> wrote:
> On 7/11/2023 9:02 AM, Simon Clubley wrote:
>> On 2023-07-11, David Turner <dturner@islandco.com> wrote:
>>> Try an old windows 7 box that wasn't recently updated and then connect to it
>>> SSH and Browsers all fail here when I try to connect to an rx2660. New
>>> SSL/TLS requirements prevent connection
>>> Pain in the aXX
>>>
>>
>> Security can be a pain sometimes. However, the alternative is far worse.
>>
>
> Gee Simon, just how much of a pain is being unable to continue to use a system?
> Can anything be worse?
>

Yes. Having the data which you have been trusted with stolen or destroyed.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 7/11/2023 1:36 PM, Simon Clubley wrote:
> On 2023-07-11, Dave Froble <davef@tsoft-inc.com> wrote:
>> On 7/11/2023 9:02 AM, Simon Clubley wrote:
>>> On 2023-07-11, David Turner <dturner@islandco.com> wrote:
>>>> Try an old windows 7 box that wasn't recently updated and then connect to it
>>>> SSH and Browsers all fail here when I try to connect to an rx2660. New
>>>> SSL/TLS requirements prevent connection
>>>> Pain in the aXX
>>>>
>>>
>>> Security can be a pain sometimes. However, the alternative is far worse.
>>>
>>
>> Gee Simon, just how much of a pain is being unable to continue to use a system?
>> Can anything be worse?
>>
>
> Yes. Having the data which you have been trusted with stolen or destroyed.
>
> Simon.
>

Ok, let me see if I understand this.

Case 1: No system to use, therefore no data to be stolen.

Case 2: Use the system, and perhaps, just perhaps, there might be some nefarious
activity.

Case 1 is absolute, case 2 is a maybe. Both bad, but, I'm not so sure you have
correctly identified the worst case.

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 7/11/2023 5:15 AM, David Turner wrote:
> Try an old windows 7 box that wasn't recently updated and then connect
> to it
> SSH and Browsers all fail here when I try to connect to an rx2660. New
> SSL/TLS requirements prevent connection
> Pain in the aXX

The browser you use for general browsing is probably not good. Difficult
to change configuration and dangerous to risk use a "downgraded"
configuration on the internet.

A VM with an old browser only used for accessing your VMS
boxes could work.

I believe it is possible to specify a config file to SSH
so if you create a working config file and use that to
connect, then it should also work. If SSH refuses to use
old algorithms then get an old version of SSH.

Arne

On Tuesday, July 11, 2023 at 7:42:23 PM UTC-4, Arne Vajhøj wrote:
> On 7/11/2023 5:15 AM, David Turner wrote:
> > Try an old windows 7 box that wasn't recently updated and then connect
> > to it
> > SSH and Browsers all fail here when I try to connect to an rx2660. New
> > SSL/TLS requirements prevent connection
> > Pain in the aXX
> The browser you use for general browsing is probably not good. Difficult
> to change configuration and dangerous to risk use a "downgraded"
> configuration on the internet.
>
> A VM with an old browser only used for accessing your VMS
> boxes could work.
>
> I believe it is possible to specify a config file to SSH
> so if you create a working config file and use that to
> connect, then it should also work. If SSH refuses to use
> old algorithms then get an old version of SSH.
>
> Arne

ok just to be clear, SSH works. I am trying to run parstatus/npartition from the command prompt on a windows 10 machine. does anyone know what needs to be changed to connect to this ILO. I'm not sure how running the linux script is going to help with running this command. yes the web interface doesn't work either. which I will try to find an old browser

thanks
Paul

On Tuesday, July 11, 2023 at 9:02:14 AM UTC-4, Simon Clubley wrote:
> Security can be a pain sometimes. However, the alternative is far worse.

You may want to read a blog post of mine from several years ago:
Is no crypto always better than bad crypto?
https://www.glaver.org/blog/?p=853

Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>On 2023-07-11, David Turner <dturner@islandco.com> wrote:
>> Try an old windows 7 box that wasn't recently updated and then connect to it
>> SSH and Browsers all fail here when I try to connect to an rx2660. New
>> SSL/TLS requirements prevent connection
>> Pain in the aXX
>
>Security can be a pain sometimes. However, the alternative is far worse.

The problem is that hardware is difficult to change, and software people see
change for change's sake as being a good thing, and there is a fault line
between them where the earthquakes happen. And that fault line includes
embedded web servers.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."

On 7/16/2023 10:29 AM, Scott Dorsey wrote:
> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>> On 2023-07-11, David Turner <dturner@islandco.com> wrote:
>>> Try an old windows 7 box that wasn't recently updated and then connect to it
>>> SSH and Browsers all fail here when I try to connect to an rx2660. New
>>> SSL/TLS requirements prevent connection
>>> Pain in the aXX
>>
>> Security can be a pain sometimes. However, the alternative is far worse.
>
> The problem is that hardware is difficult to change, and software people see
> change for change's sake as being a good thing, and there is a fault line
> between them where the earthquakes happen. And that fault line includes
> embedded web servers.

If it has to be secure then it has to happen.

The vendors need to ensure that the thing is upgradeable.

And the owners need to do the upgrades.

Arne

=?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk> wrote:
>On 7/16/2023 10:29 AM, Scott Dorsey wrote:
>> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>>> On 2023-07-11, David Turner <dturner@islandco.com> wrote:
>>>> Try an old windows 7 box that wasn't recently updated and then connect to it
>>>> SSH and Browsers all fail here when I try to connect to an rx2660. New
>>>> SSL/TLS requirements prevent connection
>>>> Pain in the aXX
>>>
>>> Security can be a pain sometimes. However, the alternative is far worse.
>>
>> The problem is that hardware is difficult to change, and software people see
>> change for change's sake as being a good thing, and there is a fault line
>> between them where the earthquakes happen. And that fault line includes
>> embedded web servers.
>
>If it has to be secure then it has to happen.

Maybe. Or maybe something else has to happen, like having more severe
restrictions on access to the network accessing the iLO interfaces. There
is almost always more than one way to skin a cat.

Security people often think of outward-facing web servers seen on the public
internet when they hear "web server." They don't think of printer maintenance
pages, iLO interfaces, or spectrum analyzers. You take security precutions
based upon vulnerabilities and the perceived or modelled risk, not because
it's "standard industry practice."

>The vendors need to ensure that the thing is upgradeable.
>
>And the owners need to do the upgrades.

You are asking for an awful lot, especially in that first case. Although in
the second case I will say that I have stopped doing any firmware upgrades
to the DL380 machines (gen7 through gen9) after twice having such "upgrades"
brick the machine. Upgrades like this I don't need.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."

On Sunday, July 16, 2023 at 12:03:12 PM UTC-4, Scott Dorsey wrote:
> =?UTF-8?Q?Arne_Vajh=c3=b8j?= <ar...@vajhoej.dk> wrote:
> >On 7/16/2023 10:29 AM, Scott Dorsey wrote:
> >> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
> >>> On 2023-07-11, David Turner <dtu...@islandco.com> wrote:
> >>>> Try an old windows 7 box that wasn't recently updated and then connect to it
> >>>> SSH and Browsers all fail here when I try to connect to an rx2660. New
> >>>> SSL/TLS requirements prevent connection
> >>>> Pain in the aXX
> >>>
> >>> Security can be a pain sometimes. However, the alternative is far worse.
> >>
> >> The problem is that hardware is difficult to change, and software people see
> >> change for change's sake as being a good thing, and there is a fault line
> >> between them where the earthquakes happen. And that fault line includes
> >> embedded web servers.
> >
> >If it has to be secure then it has to happen.
> Maybe. Or maybe something else has to happen, like having more severe
> restrictions on access to the network accessing the iLO interfaces. There
> is almost always more than one way to skin a cat.
>
> Security people often think of outward-facing web servers seen on the public
> internet when they hear "web server." They don't think of printer maintenance
> pages, iLO interfaces, or spectrum analyzers. You take security precutions
> based upon vulnerabilities and the perceived or modelled risk, not because
> it's "standard industry practice."
> >The vendors need to ensure that the thing is upgradeable.
> >
> >And the owners need to do the upgrades.
> You are asking for an awful lot, especially in that first case. Although in
> the second case I will say that I have stopped doing any firmware upgrades
> to the DL380 machines (gen7 through gen9) after twice having such "upgrades"
> brick the machine. Upgrades like this I don't need.
> --scott
>
> --
> "C'est un Nagra. C'est suisse, et tres, tres precis."

an update still no luck connecting to it. but I did find out that Port 623 is not listening. It looks like a possible hardware issue and hopefully a simple one

On Sunday, July 16, 2023 at 7:39:55 AM UTC-7, Arne Vajhøj wrote:

(snip)

> If it has to be secure then it has to happen.

And when I go from one side of the house to the other, it doesn't need to.
> The vendors need to ensure that the thing is upgradeable.

If it is in ROM, and the vendor closed down, it isn't.

> And the owners need to do the upgrades.
I have this on ILO for a Sun server. Once it boots, all is fine, but it is ILO,
or something like ILO, that powers up the machine, and tells it to boot.

I've got an update:

I figured out that you have to be in the directory where it's installed to run parmodify or parstatus.

it works but (always a but) this machine was originally set up with ICAP on 8.3-1h1. Well of course going to 8.4-1h1 VSI didn't use it.

now I'm getting Error: Unable to update the Stable Configuration Data.
which I have traced back to ICAP...

this is a rx8640. the question I have since I'm not sure who has ownership of this now? is it HPE or VSI. since this was also a thing on UX, it might be HPE which then begs the question is there anyone left there who knows it?

since ICAP has hooks into the partition, where does the information sit? would it be the LAN MP? would it be the cell board 0?
and if VMS can't stop it from running will it populate the location again?

the 2 options I have are
replace the MP LAN board which I can do.
replace cell board 0

any thoughts?

thanks
Paul