I don't think so:
Why then it works with the older Java?
Moreover, yesterday I wanted to monitor booting of a machine
before/during BIOS update, so it didn't work with active BIOS 6.4.0 nor
later, after upgrading to BIOS 6.5.0
And I know that it worked before on my other R610 already
Hello,
after updating from Java 8/162 to 8/171 I can't connect to the console
using the Virutual Console Client (i.e, by opening the downloaded
viewer.jnlp).
The screenshot shows the "Connection failed." message I got.
I this on tested this in various combinations, with two R610 as iDRAC
Have you checked your Java exceptions.sites list didn't get wiped? I found
we get that error if the drac isn't in the list. Also check you have the
relevant jdk algorithms enabled (although that might only be for drac5).
On Thu, 10 May 2018, Peter Holl wrote:
Date: Thu, 10 May 2018 15:18:48
Hello Chris,
thanks for your answer. However, I did clean the cache and I also tried
on a machine, which had no Java before - so it was a fresh install, and
I tried with Java 9. Nothing helped.
But I never tried from a linux machine.
Best,
Peter
On 5/10/18 2:42 PM, Chris Adams wrote:
On 10/05/18 13:30, Peter Holl wrote:
after updating from Java 8/162 to 8/171 I can't connect to
the console using the Virutual Console Client (i.e, by
opening the downloaded viewer.jnlp).
Probably has nothing to do with the OS's end. On my r815,
which also use iDrac6(as probably all 11th
Yes! Without exception I can't get that far to see that "Connection
failed" error.
On 5/10/18 3:23 PM, li...@cloned.org.uk wrote:
Have you checked your Java exceptions.sites list didn't get wiped? I
found we get that error if the drac isn't in the list. Also check you
have the relevant jdk
Hello!
This is on an PowerEdge R730xd with BIOS 2.7.1 running RHEL 7.4 (x64,
fully updated)
RPMs:
dell-system-update-1.5.3-18.03.00.x86_64
invcol_JCV76_LN64_17_12_201_178_A00-17.12.201_178-JCV76.x86_64
When trying to run dsu, I get crashes in 'sasdupie' and 'MarvCtrlIE' and
no storage
On 09/05/18 22:34, R S wrote:
Is there a mechanism that prevents me to downgrade from
v6.5.0 back to v6.4.0 on a R710/T710? I downgraded the
iDRAC from 2.90 to v2.80 and the 'Connection Failed' issue
is still there, so I'm trying to downgrade the BIOS.
I've just downgraded back to 3.2.2 on
On 05/10/2018 10:34 AM, lejeczek wrote:
On 09/05/18 22:34, R S wrote:
Is there a mechanism that prevents me to downgrade from v6.5.0 back to
v6.4.0 on a R710/T710? I downgraded the iDRAC from 2.90 to v2.80 and
the 'Connection Failed' issue is still there, so I'm trying to
downgrade the
Once upon a time, Peter Holl said:
> after updating from Java 8/162 to 8/171 I can't connect to the
> console using the Virutual Console Client (i.e, by opening the
> downloaded viewer.jnlp).
I just tried an R610 with DRAC 2.90 from Fedora Linux with OpenJDK
1.8.0.171 and
We shouldn't be asked to downgrade our Java version, nor mess with the
security setting of JDK/JRE/IcedT. If this really is java-related then it's
up to Dell to fix this and restore functionality of the iDRAC.
On Thu, May 10, 2018 at 10:00 AM, lejeczek wrote:
>
>
> On
Dell, please confirm that there are issues with iDRAC and Java 8 Update 161
and Update 171.
On Thu, May 10, 2018 at 10:43 AM, R S wrote:
> We shouldn't be asked to downgrade our Java version, nor mess with the
> security setting of JDK/JRE/IcedT. If this really is
Hi Sashi,
I couldn't see an obvious version in that file. If you have a command to
get it I can run it. Note: that file is part of the previously mentioned
invcol_JCV76...rpm package (ie provided by Dell).
FWIW, I found a similar crash report in Sept 2017. I didn't find any
followup or
Fairly Confident IDRAC6 is unsupported, and likely isn't going to receive
an update. The latest builds of Java broke because they are removing the
old ciphers that are "less secure". This is a work around for now until
dell either makes an update or determines they won't for IDRAC6.
I've had
On 05/10/2018 12:37 PM, Stephen John Smoogen wrote:
On 10 May 2018 at 09:57, Patrick Boutilier wrote:
On 05/10/2018 10:34 AM, lejeczek wrote:
On 09/05/18 22:34, R S wrote:
Is there a mechanism that prevents me to downgrade from v6.5.0 back to
v6.4.0 on a R710/T710?
Nah, the SSL/TLS backend in the iDRAC6 most likely needs to be updated and
that will fix it (see other email thread from Mr. S. Smoogen). Instead we
are insecuring our Java clients to make it work with insecure iDRAC6.
If it were possible, I'd get a kick out of the results on SSLLabs. It's
seems
Once upon a time, R S said:
> We shouldn't be asked to downgrade our Java version, nor mess with the
> security setting of JDK/JRE/IcedT. If this really is java-related then it's
> up to Dell to fix this and restore functionality of the iDRAC.
I'm curious; if a Java
inux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
-- next part --
A non-text attachment was scrubbed...
Name: boutilpj.vcf
Type: text/x-vcard
Size: 286 bytes
Desc: not availa
*iDRAC6*
v2.90 was released in summer last year, so they might or might not still
support it. Vendor-dependancy. Another case for open-sourcing this stuff.
Perfectly working hardware, but vendor drops support while server admins
all around the world rely on this.
On Thu, May 10, 2018 at 11:13 AM,
Smoogen, I just tested commenting out "jdk.jar.disabledAlgorithms" and
connecting to the iDRAC Remote Console now works on Java 8 Update 162.
Depending on your distro the path to the java.security file might be
different from /usr/lib/jvm/java-openjdk/jre/lib/security/java.security
I'm running a
Tested and confirmed.
The compromising elements that the iDRAC6 still relies on is either a 1024
certificate key and MD5 or MD2 both of which are deprecated for like 10
years[1]?
[1] https://events.ccc.de/congress/2008/Fahrplan/events/3023.en.html
On Thu, May 10, 2018 at 12:09 PM, R S
Cool. I was not aware of that. Thank you for that answer.
On 10 May 2018 at 13:44, R S wrote:
> They did that just last year. All of the SSL backend was updated. They
> removed RC4, updated OpenSSL etc etc. See
>
On 10 May 2018 at 10:00, lejeczek wrote:
>
>
> On 10/05/18 14:28, Gould, Josh wrote:
>>
>> Work around is to disable some of the security settings for JAVA in your
>> java.security file:
>
>
> Which distro are you on? Which java?
>
I can't vouch for it working on idrac6
This worked for me at home on Debian Stretch and Chrome. Not sure of the
security implications.
On 2018-05-10 09:28, Gould, Josh wrote:
Same problem with IDRAC6, 7, and 8 with latest Java. Upgrade to IDRAC
7&8 fixes it for them, but IDRAC 6 still doesnt' work.
Work around is to disable some
On 10/05/18 22:40, lejeczek wrote:
On 10/05/18 13:30, Peter Holl wrote:
after updating from Java 8/162 to 8/171 I can't connect to the
console using the Virutual Console Client (i.e, by opening the
downloaded viewer.jnlp).
Probably has nothing to do with the OS's end. On my r815, which also
25 matches
Mail list logo