[Linux-PowerEdge] @Dell staff - Unable to read public file /usr/libexec/dell_dup/0x756ba70b1019ced6.asc

[lejeczek]

[EXTERNAL EMAIL] 

hi guys,

There seems to be a problem with keys.

$ dsu --import-public-key
DELL EMC System Update 1.8.0
Copyright (C) 2014 DELL EMC Proprietary.
Unable to read public file
/usr/libexec/dell_dup/0x756ba70b1019ced6.asc
Importing public key(s) failed
Progress report is available
at:/usr/libexec/dell_dup/DSU_STATUS.json
Exiting DSU!

regards, L.
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] perccli (or storcli) in RHEL 8 - how ?

[lejeczek]

[EXTERNAL EMAIL] 

Hi guys,
would any of you know how to get perccli to work in RHEL 8?
I have it installed but it does not detect nor show any of
of the PERC controllers.

many thanks, L.
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] Are Dell's days in Linux real numbered?

[lejeczek]

[EXTERNAL EMAIL] 
Please report any suspicious attachments, links, or requests for sensitive information.



... now when IBM acquired Redhat. What do you guys think? (thinking of 
my purchases in near future)


cheers, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] DSU - does not dectect/find any NICs

[lejeczek]

On 17/10/2018 14:41, venugopal...@dell.com wrote:

Thanks for sharing the details.

Out of 3 NICs mentioned in omreport-nics.txt, 2 have reached end of life and 1 
is not supported by Inventory collector (DSU). Details below.

Broadcom NetXtreme II 5709C Quad-port GbE Adapter---End of Life
NetXtreme II BCM5709 Gigabit Ethernet  ---End 
of Life
SFN5162F-R7 SFP+ Server Adapter ---
Solarflare not supported


and these Broadcoms are built-in/embedded NICs.

and if we have to bombard places like this mailing list for info to try 
to understand what is happening(not working) then it is very 
objectionable design, unsuitable philosophy guys who are responsible for 
DSU deploy in development process of this piece of software - cannot! 
just silently skip some parts.


Make DSU tell us those things, inform us. Especially! if the rest of 
Dell OMSA does - what we all expect - not! ignore these bits.


thanks.



Thanks,
Venugopal

-Original Message-
From: lejeczek 
Sent: Monday, October 15, 2018 5:28 PM
To: P1, Venugopal; linux-poweredge-Lists
Subject: Re: [Linux-PowerEdge] DSU - does not dectect/find any NICs


[EXTERNAL EMAIL]
Please report any suspicious attachments, links, or requests for sensitive 
information.


On 15/10/2018 10:57, venugopal...@dell.com wrote:

Hi,

Please provide card details, DSU inventory report and omreport/racadm report.

Run below command to generate inventory report from DSU:
dsu --output-inventory-xml=inv.xml

Thanks,
Venugopal

here is one system(notice that not even embedded ones DSU can find)� -
attached.

regards, L.



-Original Message-
From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: Saturday, October 13, 2018 2:36 AM
To: linux-poweredge-Lists
Subject: [Linux-PowerEdge] DSU - does not dectect/find any NICs

hi guys

I wonder if your dsu also lost (a while ago would find only some NICs but not 
all) ability to detect any NICs?
I have a few R815 and while omreport/racadm see all the bits as you would 
expect, dsu completely fails to find any NICs on my systems.

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge




___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] DSU - does not dectect/find any NICs

[lejeczek]

hi guys

I wonder if your dsu also lost (a while ago would find only 
some NICs but not all) ability to detect any NICs?
I have a few R815 and while omreport/racadm see all the bits 
as you would expect, dsu completely fails to find any NICs 
on my systems.


many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] EXT : omconfig biossetup & passwords

[lejeczek]

On 30/10/2017 16:46, Gottloeb, Jeff [US] (ES) wrote:

 From Dell Tech Support:


Dell OpenManage Server Administrator Version 8.5 Command Line Interface Guide
http://topics-cdn.dell.com/pdf/dell-openmanage-server-administrator-8.5_user's%20guide2_en-us.pdf

See 'System Security' on Page 71:

omconfig chassis biossetup attribute=setuppassword setting=
Would anybody know why, if it was in earlier versions, Dell 
removed this attribute from ver. 9.x


$ omconfig chassis biossetup attribute=setuppassword 
setting=_passwd
Error! Unrecognized parameter value: 
attribute=


Thus, again, same question - OMSA: how to re/set BIOS admin 
password?


many thanks,
L.


Lilly Edwards
Enterprise Technical Support Senior Analyst, Linux & Virtualization Technology 
Support
Certifications: VCP-DCV6 | NPP | PowerEdge Associate
Dell EMC | Global Support & Deployment
Office + 1-800-945-3355, Press * to enter Ext 513-4080


Jeff Gottloeb
Northrop Grumman IT Solutions
310 812 4395

-Original Message-
From: Linux-PowerEdge [mailto:linux-poweredge-boun...@dell.com] On Behalf Of 
lejeczek
Sent: Monday, October 30, 2017 9:28 AM
To: linux-powere...@lists.us.dell.com
Subject: EXT :[Linux-PowerEdge] omconfig biossetup & passwords

hi everyone

I cannot remember for certain - did we have features/options for bios 
security/passwords in omsa?
I'm looking but it does not seem like omsa could re/set/clear BIOS' passwords?

regards, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] linux.dell.com down again?

[lejeczek]

On 15/09/18 01:52, jose.delar...@dell.com wrote:


Matt,

Apologies that you are experiencing issues. We have heard of similar 
reports of unavailability and timeouts in the past, so I will check 
with our IT group and see if there’s something we can do to minimize 
these kind of issues in the future.


*Jose Delarosa*

Linux Engineering

*Dell**EMC*|Infrastructure Solutions Group

**

**

*From:*linux-poweredge-bounces-Lists *On Behalf Of *Matt Vander Werf
*Sent:* Friday, September 14, 2018 1:01 PM
*To:* linux-poweredge-Lists
*Subject:* [Linux-PowerEdge] linux.dell.com down again?

Looks like the linux.dell.com  system/site 
(which is also the same system that hosts lists.us.dell.com 
, which hosts this mailing list) is having 
major issues again...


I've been able to reach lists.us.dell.com  
sites in a web browser off and on today, so thought I'd try sending to 
the list to see if it gets through...


But I'm unable to reach linux.dell.com  for 
Dell RPM repos or the bootstrap script to set up Dell repos. It comes 
back with a "ERROR 504: Gateway Timeout":


[root@host ~]# wget https://linux.dell.com/repo/hardware/dsu/bootstrap.cgi
--2018-09-14 13:55:07-- 
https://linux.dell.com/repo/hardware/dsu/bootstrap.cgi
Resolving linux.dell.com  (linux.dell.com 
)... 143.166.156.113
Connecting to linux.dell.com  (linux.dell.com 
)|143.166.156.113|:443... connected.

HTTP request sent, awaiting response... 504 Gateway Timeout
2018-09-14 13:57:18 ERROR 504: Gateway Timeout.

Can someone from Dell take a look and follow up on this?

Thanks.

--

Matt Vander Werf
HPC System Administrator
University of Notre Dame
Center for Research Computing - Union Station
506 W. South Street
South Bend, IN 46601

Phone: (574) 631-0692



___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


not again!

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] off topic - ecryptfs (from centosplus) and libvirt lxc quest on it - quest upon start shoots host in the head

[lejeczek]

hi guys

I have a lxc guest on Dell's R815(AMD Opterons) which I just 
moved to an ecryptfs mounted folder(using centosplus' kernel 
C7.5)


Copying data to that folder seems to work just fine, but I 
as soon as I start the quest the host gets shot in the head 
almost immediately, hard reboot, no dump.


I also have another, virtually identical guest but on Intel 
platform and that one does not do anything but runs okey.


Any of you guys has experience such gross abnormality?

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] off topic - PowerEdge & Solarflare SFC9000

[lejeczek]

On 11/07/18 17:31, Stefan M. Radman wrote:

hi lejeczek

You wrote "one box gets shoot in the head".
Are you running the Pacemaker cluster framework with Corosync and STONITH?

Stefan


On Jul 11, 2018, at 6:03 PM, lejeczek  wrote:

hi guys

I wonder if any of you might be using SFC9000(same firmware everywhere, Centos 
7.5 too) with your poweredge. I'm on r815.

I'm trying poor man's setup to get the servers onto 10GbE network.

Setup is such that three R815 are connected to each other, each has one 
Solarflare(SFP ports) and each Solarflare is set as net-team(both ports on a 
card are net-team device) with runner in broadcast mode. And it all seems to 
work, they ping each other, iperf okey.

The problem, big problem is that when traffic start to flow between all three 
servers simultaneously, with rsync for example, then!! one box gets shoot in 
the head, hard reset, gone.

Now, I know you would normally put it via a switch, but like I said: poor man's 
config, but you would not expect system to die like this neither, right?

Anybody?

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

I do but it's not that, no stonith.
I use those words for they best describe what happens, it's 
get shot and gone, hard reset.



___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] off topic - PowerEdge & Solarflare SFC9000

[lejeczek]

hi guys

I wonder if any of you might be using SFC9000(same firmware everywhere, 
Centos 7.5 too) with your poweredge. I'm on r815.


I'm trying poor man's setup to get the servers onto 10GbE network.

Setup is such that three R815 are connected to each other, each has one 
Solarflare(SFP ports) and each Solarflare is set as net-team(both ports 
on a card are net-team device) with runner in broadcast mode. And it all 
seems to work, they ping each other, iperf okey.


The problem, big problem is that when traffic start to flow between all 
three servers simultaneously, with rsync for example, then!! one box 
gets shoot in the head, hard reset, gone.


Now, I know you would normally put it via a switch, but like I said: 
poor man's config, but you would not expect system to die like this 
neither, right?


Anybody?

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] multipath recipe for an enclosure ? - off topic

[lejeczek]

hi guys,

In hope that some experts roam around I post this one question - how do 
you multipath disks(all disks) that sit in one specific SAS enclosure? 
Blacklist everything else.


And I'm hoping for something like "globing", so you do not want to go 
through it on by single disk/wwin basis.


some experts?(or maybe even not, it could be that I do not get it)

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] significance of dsm_dupbios_restore.service ?

[lejeczek]

hi guys

Have you seen maybe dsm_dupbios_restore.service failing 
after you updated your BIOS?
I'am on r815 and after update to 3.4.1 this services fails 
and I cannot start it.


b.w. L

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't mitigate

[lejeczek]

hi Dave

do you have some update(s) on that front?

many thanks, L.

On 03/05/18 15:52, david.waggo...@dell.com wrote:

Thanks for bringing this to our attention.  We are investigating the Spectre 
mitigations in our R715/815 BIOS.  I'll provide further updates once we are 
clear on exactly what's happening.

Dave

-Original Message-
From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists
Sent: Thursday, May 3, 2018 8:58 AM
To: linux-poweredge-Lists
Subject: Linux-PowerEdge Digest, Vol 168, Issue 3

Send Linux-PowerEdge mailing list submissions to
linux-poweredge@dell.com

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
or, via email, send a message with subject or body 'help' to
linux-poweredge-requ...@dell.com

You can reach the person managing the list at
linux-poweredge-ow...@dell.com

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of Linux-PowerEdge digest..."


Today's Topics:

1. Re:  R815 BIOS updates to mitigate Spectre don't mitigate
   Spectre (lejeczek)
2. Re:  R815 BIOS updates to mitigate Spectre don't mitigate
   Spectre (Paul Menzel)
3. Re:  R815 BIOS updates to mitigate Spectre don't mitigate
   Spectre (Matt Vander Werf)


--

Message: 1
Date: Thu, 3 May 2018 13:04:30 +0100
From: lejeczek <pelj...@yahoo.co.uk>
To: sash...@dell.com, linux-powere...@lists.us.dell.com
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre
Message-ID: <dd0976c1-3446-d754-cd85-5782d33fe...@yahoo.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed

hi Sashi

maybe more frequently!?
maybe, more promptly for such a critical!!! vulnerabilities as spectre/meltdown.

sure you must understand what it means a day, an hour, with system that 
exposed, right?

we all relay on DSU, even it it only partly solves a problem, it still is often 
a critical part!

many thanks, L.

On 30/04/18 20:11, sash...@dell.com wrote:

Hi,

Latest R815 BIOS (SWB - PDFYH) is not yet carried in 18.04.00 DSU 
repository(latest available) as it is released after our repository refresh.
We refresh DSU repository 3rd week of every month.
Since the current available repository was refreshed on 20th of April, next 
repository refresh (18th of May) shall carry this update.

Regards,
Sashi

-Original Message-
From: K, Sashi
Sent: Monday, April 30, 2018 11:12 PM
To: linux-poweredge-Lists
Subject: RE: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre

Hi,

We'll check and get back to you at the earliest.

Regards,
Sashi

From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: 27 April 2018 19:17
Cc: linux-poweredge-Lists
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre



On 27/04/18 14:24, Paul Menzel wrote:

Dear lejeczek,


On 04/27/18 15:18, lejeczek wrote:

more importantly !! why dsu does not find this new BIOS versions -
@dell guys?

Why is your issue more important?

Why?? Maybe because
https://linux.dell.com/repo/hardware/dsu/ references this mailing list, and 
though not exclusively, mainly Dell tech team is here for that reason.

And nowhere near hijacking - if Dell guys read this they should see
these are directly connected. And since, I'd imagine most of us here
use DSU we are disappointed again that we learn again(this way) that
maintenance of the repo is bit shoddy.(nothing to do whit you)


And, please be more polite, and do not hijack threads, and follow the
netiquette ? [1] is one example.

Anyway, from the device page for my system I get with the service
tag, I find [2].


Kind regards,

Paul


[1] https://en.opensuse.org/openSUSE:Mailing_list_netiquette
[2]
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driv
e
rId=PDFYH


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge



--

Message: 2
Date: Thu, 3 May 2018 15:04:58 +0200
From: Paul Menzel <pmen...@molgen.mpg.de>
To: Matt Vander Werf <mvand...@nd.edu>
Cc: linux-poweredge@dell.com
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre
Message-ID: <be21204e-547f-69ea-e697-c28ede98e...@molgen.mpg.de>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Dear Matt,


On 04/30/18 16:44, Matt Vander Werf wrote:


I did actually test also on an R815 running Opteron 6234 as well, and
got the same result. Microcode version is different (0x600063d) but

Re: [Linux-PowerEdge] iDRAC 6 enterprise console not working with newest java

[lejeczek]

On 11/05/18 04:06, linux-powere...@davidnewall.com wrote:
Obviously I'm not talking about situations where you 
update to fix a problem that does affect you, which is 
rare, and so my advice is to not upgrade without good reason. 


Advice is to follow advices from the vendor and read all 
readmes.
I replied earlier that it had nothing with BIOS upgrade, 
iDrac6's broken virtual console has more to do with the fact 
that its firmware is bit (too)old and new software does not 
agree with it.


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] r815 new BIOS 3.4.0 major problem

[lejeczek]

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 one r815 and it seems 
that it actually might be iDrac6 =! new Java.


I wonder if users of newer iDracs also experience this problem?

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] iDRAC 6 enterprise console not working with newest java

[lejeczek]

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 gen) it is BIOS 
update that broke virtual console. Windows also fails to 
connect.


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] r815 new BIOS 3.4.0 major problem

[lejeczek]

On 09/05/18 17:54, R S wrote:
I'm having problems Lauching Console in an iDRAC6 on a 
R710 with BIOS 6.5.0 and iDRC 2.90

It errors out:


Tried with 3 different browser on 3 different OS and they 
all fail.​


I'm going to downgrade to 2.85 first and see if it 
connects. If not I'm going to downgrade BIOS to 6.4.0


Is DELL planning to update the cert that will expire in 
about 7 month. Just a heads up as thing take time



On Wed, May 9, 2018 at 6:04 AM, lejeczek 
<pelj...@yahoo.co.uk <mailto:pelj...@yahoo.co.uk>> wrote:


guys, can you get to "virtual console" in your
iDrac(2.90 (Build 04))?
It seems to me 3.4.0 BIOS has broken something.

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com <mailto:Linux-PowerEdge@dell.com>
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
<https://lists.us.dell.com/mailman/listinfo/linux-poweredge>




--
Tech III * AppControl * Endpoint Protection * Server 
Maintenance

Buncombe County Schools Technology Department Network Group
ComicSans Awareness Campaign <http://comicsanscriminal.com>


that is what I get. Though in case if r815 it's iDrac. I've 
had 2.90 for ... well, a long time. Only recent BIOS update 
to 3.4.0 broke the console.


@dell team - this is rather urgent. Can you help guys?

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't mitigate

[lejeczek]

thanks Dave and guys@Dell
having this fixed asap, thoroughly and for good, I'm sure 
all! of us will be grateful for.


I have a few of r815 and the thought of users playing there 
on the edge of such a black hole makes me feel shaky...


@guys who took trouble finding out and then sharing, also 
big thanks.



On 03/05/18 15:52, david.waggo...@dell.com wrote:

Thanks for bringing this to our attention.  We are investigating the Spectre 
mitigations in our R715/815 BIOS.  I'll provide further updates once we are 
clear on exactly what's happening.

Dave

-Original Message-
From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists
Sent: Thursday, May 3, 2018 8:58 AM
To: linux-poweredge-Lists
Subject: Linux-PowerEdge Digest, Vol 168, Issue 3

Send Linux-PowerEdge mailing list submissions to
linux-poweredge@dell.com

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
or, via email, send a message with subject or body 'help' to
linux-poweredge-requ...@dell.com

You can reach the person managing the list at
linux-poweredge-ow...@dell.com

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of Linux-PowerEdge digest..."


Today's Topics:

1. Re:  R815 BIOS updates to mitigate Spectre don't mitigate
   Spectre (lejeczek)
2. Re:  R815 BIOS updates to mitigate Spectre don't mitigate
   Spectre (Paul Menzel)
3. Re:  R815 BIOS updates to mitigate Spectre don't mitigate
   Spectre (Matt Vander Werf)


--

Message: 1
Date: Thu, 3 May 2018 13:04:30 +0100
From: lejeczek <pelj...@yahoo.co.uk>
To: sash...@dell.com, linux-powere...@lists.us.dell.com
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre
Message-ID: <dd0976c1-3446-d754-cd85-5782d33fe...@yahoo.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed

hi Sashi

maybe more frequently!?
maybe, more promptly for such a critical!!! vulnerabilities as spectre/meltdown.

sure you must understand what it means a day, an hour, with system that 
exposed, right?

we all relay on DSU, even it it only partly solves a problem, it still is often 
a critical part!

many thanks, L.

On 30/04/18 20:11, sash...@dell.com wrote:

Hi,

Latest R815 BIOS (SWB - PDFYH) is not yet carried in 18.04.00 DSU 
repository(latest available) as it is released after our repository refresh.
We refresh DSU repository 3rd week of every month.
Since the current available repository was refreshed on 20th of April, next 
repository refresh (18th of May) shall carry this update.

Regards,
Sashi

-Original Message-
From: K, Sashi
Sent: Monday, April 30, 2018 11:12 PM
To: linux-poweredge-Lists
Subject: RE: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre

Hi,

We'll check and get back to you at the earliest.

Regards,
Sashi

From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: 27 April 2018 19:17
Cc: linux-poweredge-Lists
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre



On 27/04/18 14:24, Paul Menzel wrote:

Dear lejeczek,


On 04/27/18 15:18, lejeczek wrote:

more importantly !! why dsu does not find this new BIOS versions -
@dell guys?

Why is your issue more important?

Why?? Maybe because
https://linux.dell.com/repo/hardware/dsu/ references this mailing list, and 
though not exclusively, mainly Dell tech team is here for that reason.

And nowhere near hijacking - if Dell guys read this they should see
these are directly connected. And since, I'd imagine most of us here
use DSU we are disappointed again that we learn again(this way) that
maintenance of the repo is bit shoddy.(nothing to do whit you)


And, please be more polite, and do not hijack threads, and follow the
netiquette ? [1] is one example.

Anyway, from the device page for my system I get with the service
tag, I find [2].


Kind regards,

Paul


[1] https://en.opensuse.org/openSUSE:Mailing_list_netiquette
[2]
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driv
e
rId=PDFYH


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge



--

Message: 2
Date: Thu, 3 May 2018 15:04:58 +0200
From: Paul Menzel <pmen...@molgen.mpg.de>
To: Matt Vander Werf <mvand...@nd.edu>
Cc: linux-poweredge@dell.com
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre
don't mitigate Spectre
Message-ID: <be21204e-547f-69ea-e697-c28ede98e...@molgen.mpg.de>
Content-Type: text/plain; charset="utf-

[Linux-PowerEdge] @dell team - libsmbios

[lejeczek]

hi guys

is new version of libsmbios 2.3.3-6.el7 okey to update to?

regards, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't mitigate Spectre

[lejeczek]

hi Sashi

maybe more frequently!?
maybe, more promptly for such a critical!!! vulnerabilities 
as spectre/meltdown.


sure you must understand what it means a day, an hour, with 
system that exposed, right?


we all relay on DSU, even it it only partly solves a 
problem, it still is often a critical part!


many thanks, L.

On 30/04/18 20:11, sash...@dell.com wrote:

Hi,

Latest R815 BIOS (SWB - PDFYH) is not yet carried in 18.04.00 DSU 
repository(latest available) as it is released after our repository refresh.
We refresh DSU repository 3rd week of every month.
Since the current available repository was refreshed on 20th of April, next 
repository refresh (18th of May) shall carry this update.

Regards,
Sashi

-Original Message-
From: K, Sashi
Sent: Monday, April 30, 2018 11:12 PM
To: linux-poweredge-Lists
Subject: RE: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't 
mitigate Spectre

Hi,

We'll check and get back to you at the earliest.

Regards,
Sashi

From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: 27 April 2018 19:17
Cc: linux-poweredge-Lists
Subject: Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't 
mitigate Spectre



On 27/04/18 14:24, Paul Menzel wrote:

Dear lejeczek,


On 04/27/18 15:18, lejeczek wrote:

more importantly !! why dsu does not find this new BIOS versions -
@dell guys?

Why is your issue more important?

Why?? Maybe because
https://linux.dell.com/repo/hardware/dsu/ references this mailing list, and 
though not exclusively, mainly Dell tech team is here for that reason.

And nowhere near hijacking - if Dell guys read this they should see these are 
directly connected. And since, I'd imagine most of us here use DSU we are 
disappointed again that we learn again(this way) that maintenance of the repo 
is bit shoddy.(nothing to do whit you)


And, please be more polite, and do not hijack threads, and follow the
netiquette – [1] is one example.

Anyway, from the device page for my system I get with the service tag,
I find [2].


Kind regards,

Paul


[1] https://en.opensuse.org/openSUSE:Mailing_list_netiquette
[2]
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?drive
rId=PDFYH


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't mitigate Spectre

[lejeczek]

On 27/04/18 14:24, Paul Menzel wrote:

Dear lejeczek,


On 04/27/18 15:18, lejeczek wrote:
more importantly !! why dsu does not find this new BIOS 
versions - @dell guys?


Why is your issue more important?


Why?? Maybe because 
https://linux.dell.com/repo/hardware/dsu/ references this 
mailing list, and though not exclusively, mainly Dell tech 
team is here for that reason.


And nowhere near hijacking - if Dell guys read this they 
should see these are directly connected. And since, I'd 
imagine most of us here use DSU we are disappointed again 
that we learn again(this way) that maintenance of the repo 
is bit shoddy.(nothing to do whit you)




And, please be more polite, and do not hijack threads, and 
follow the netiquette – [1] is one example.


Anyway, from the device page for my system I get with the 
service tag, I find [2].



Kind regards,

Paul


[1] https://en.opensuse.org/openSUSE:Mailing_list_netiquette
[2] 
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=PDFYH




___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] R815 BIOS updates to mitigate Spectre don't mitigate Spectre

[lejeczek]

more importantly !! why dsu does not find this new BIOS 
versions - @dell guys?


On 26/04/18 21:55, Matt Vander Werf wrote:

Hello,

I noticed that Dell released BIOS updates for R815 systems 
to address the Spectre vulnerability (variant #2, 
CVE-2017-5715) at [1]. The new version is 3.4.0 and the 
previous latest version is 3.2.2. We have quite a few R815 
systems running AMD Opteron processors, mostly Opteron 
6378, but some 6200 series too. AMD says it released 
updates to OEMs going as far back as the first "Bulldozer" 
Opteron processors released in 2011 [2], so I'd expect 
this BIOS update to address Spectre for all our R815 
systems...


However, when I apply the new BIOS update to one of these 
R815 systems running Operton 6378 processors and reboot 
the system, the machine still shows up as being vulnerable 
[3].


Checking the CPU flags, I don't see any flags that 
indicate protection against Spectre, like ibpb, ibrs, or 
spec_ctl [4]. The only new CPU flag that shows up with the 
BIOS update is the vmmcall flag, which is unrelated to the 
Spectre vulnerability. The CPU microcode didn't change 
either from 0x600084f. The machine shows it is running the 
new BIOS version [5] but it doesn't appear to be doing 
anything to address Spectre, even though the R815 BIOS 
firmware page says it does... Here's [6] some more info 
about the Opteron 6378 processor in one of our R815 
systems. They are all running RHEL 7.



Are others seeing the same thing?

@Dell: Did this BIOS update only address Spectre for 
certain Opteron processors and not all possible R815 
Opteron processors?? If so, could it be indicated on the 
firmware page what processors it fixes? Can we get updates 
for Opteron 6378 please?


Thank you.



[1]
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=PDFYH
http://www.dell.com/support/article/us/en/04/sln308588/microprocessor-side-channel-vulnerabilities-cve-2017-5715-cve-2017-5753-cve-2017-5754-impact-on-dell-emc-products-dell-enterprise-servers-storage-and-networking-?lang=en#bios

[2]
https://www.amd.com/en/corporate/security-updates

[3]
[root@host ~]# grep . 
/sys/devices/system/cpu/vulnerabilities/*

/sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: 
Load fences
*/sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable: 
Retpoline without IBPB*


[4]
[root@host ~]# lscpu  | grep "Flags"
Flags: fpu vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse 
sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc art rep_good nopl nonstop_tsc extd_apicid 
amd_dcm aperfmperf pni pclmulqdq monitor ssse3 fma cx16 
sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy 
svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch 
osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb cpb hw_pstate 
retpoline_amd vmmcall bmi1 arat npt lbrv svm_lock 
nrip_save tsc_scale vmcb_clean flushbyasid decodeassists 
pausefilter pfthreshold


[5]
[root@host~]# dmidecode -t 0 | grep "BIOS Revision"
    BIOS Revision: 3.4

[6]
vendor_id    : AuthenticAMD
cpu family    : 21
model        : 2
model name    : AMD Opteron(tm) Processor 6378
stepping    : 0
microcode    : 0x600084f


--
Matt Vander Werf
HPC System Administrator
University of Notre Dame
Center for Research Computing - Union Station


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] more downgrades: @Dell -why?

[lejeczek]

But why dsu would even suggest downgrades? Does it have a 
valid reason(s) when it does that?
You know, software(not just Dell) downgrades happens 
sometimes and then it's usually something critical.
I'm hoping for some clarification as to why DSU would 
propose a downgrade.
It's not first time I'm seeing this and I must admit if 
again there are no clear answers and as for DSU it will no 
improve its programming logic - should be crystal clear with 
full info - then I'm another step closer to a path away from 
Dell.


many thanks, L.


On 16/02/18 14:02, Patrick Boutilier wrote:

I always use -u to avoid seeing downgrades.

u,   --apply-upgrades-only  List only 
upgradable updates





On 02/16/2018 09:55 AM, Stefan M. Radman wrote:

Kidding, are you?

DSU contradicts the official Dell Support resource (not 
the first time).


http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=80XJ1 



Dell Lifecycle Controller v1.7.5
Version 1.7.5.4, A00
Release date 25 Jun 2015
Last Updated 09 Mar 2016
Importance: Recommended

Other versions
1.6.5.12,A00 14 Apr 2014    4:20:04 PM

Would you really?

Stefan

On Feb 16, 2018, at 2:01 PM, lejeczek 
<pelj...@yahoo.co.uk> wrote:


hi everyone, hi Dell guys

would you know if that dsu on my R815s says is correct 
and should be executed?


[ ]1 Dell LifeCycle Controller v1.7.5, 1.7.5.4, A00
Current Version : 1.7.5.4 Downgrade to : 1.6.5.12, 
Criticality : Recommended


many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge





___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] more downgrades: @Dell -why?

[lejeczek]

hi everyone, hi Dell guys

would you know if that dsu on my R815s says is correct and 
should be executed?


[ ]1 Dell LifeCycle Controller v1.7.5, 1.7.5.4, A00
Current Version : 1.7.5.4 Downgrade to : 1.6.5.12, 
Criticality : Recommended


many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] @dell tech - dsu does not show/find all components

[lejeczek]

hi people@Dell

it's been a while, I've had some updates from dell yum repo, 
yet still dsu on all my PE r815 does not show all network 
interfaces:

Can please somebody @Dell look into it?

01:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
02:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
06:00.0 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
06:00.1 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
06:00.2 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
06:00.3 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
23:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
23:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
24:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
24:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)


and dsu:

warning: Inventory collector returned with partial failure.
Determining Applicable Updates ...

|DELL EMC System Update---|
[ ] represents 'not selected'
[*] represents 'selected'
[-] represents 'Component already at repository version (can 
be selected only if -e option is used)'
Choose:  q - Quit without update, c to Commit,  - To 
Select/Deselect, a - Select All, n - Select None


[-]1 NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p1)
Current Version : 7.10.64 same as : 7.10.64, Criticality : 
Recommended


[-]2 NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p3)
Current Version : 7.10.64 same as : 7.10.64, Criticality : 
Recommended


[-]3 NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p4)
Current Version : 7.10.64 same as : 7.10.64, Criticality : 
Recommended


[-]4 NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p2)
Current Version : 7.10.64 same as : 7.10.64, Criticality : 
Recommended


[-]5 SAS/SATA Backplane 0:0 Backplane Firmware
Current Version : 1.07 same as : 1.07, Criticality : Optional

[-]6 PERC H200I Controller 0 Firmware
Current Version : 07.03.06.00 same as : 07.03.06.00, 
Criticality : Recommended


[-]7 BIOS
Current Version : 3.2.2 same as : 3.2.2, Criticality : 
Recommended


[-]8 PERC H700 Integrated Controller 0 Firmware
Current Version : 12.10.7-0001 same as : 12.10.7-0001, 
Criticality : Urgent


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] dsu segfaults

[lejeczek]

with just updated dsu to ver 1.5.1 I still see only 1 
NIC(four ports) out of 3(12 ports in total)


$ dsu --inventory --log-level=4 --output-log-file=dsu.log/log
DELL EMC System Update 1.5.1
Copyright (C) 2014 DELL EMC Proprietary.
Verifying catalog installation ...
Installing catalog from repository ...
Fetching dsucatalog ...
Reading the catalog ...
Verifying inventory collector installation ...
Getting System Inventory ...
warning: Inventory collector returned with partial failure.

1. OpenManage Server Administrator  ( Version : 8.5.0 )


And in the log:

$ tailf dsu.log/log
#ID : cda44105-3441-4637-991e-156749142b90
#DSU Version: 1.5.1 - cda44105-3441-4637-991e-156749142b90
#System IP: 252.127.0.0 - cda44105-3441-4637-991e-156749142b90
#Date: 22-11-2017 11:48:58 - 
cda44105-3441-4637-991e-156749142b90
#Fields:      ID   |    Date 
Time | Level    | Message
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
11:48:58 |    INFO    |    Verifying catalog installation ...
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
11:49:06 |    INFO    |    Installing catalog from 
repository ...
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
11:49:15 |    INFO    |    Fetching dsucatalog ...
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
11:49:25 |    INFO    |    Reading the catalog ...
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
11:49:33 |    INFO    |    Verifying inventory collector 
installation ...
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
11:49:33 |    INFO    |    Getting System Inventory ...
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
12:12:41 |    WARNING    |    warning: Inventory collector 
returned with partial failure.
    cda44105-3441-4637-991e-156749142b90  |    22-11-2017 
12:12:42 |    INFO    |    Exiting DSU!



What might be wrong? Most importantly - Would you know when 
it might get fixed?


regards, L.


On 30/10/17 15:51, santosh.g...@dell.com wrote:

Dell - Internal Use - Confidential


The segmentation fault issue is not related to NIC report issue. We are 
checking with internal team about the NIC inventory issue.



Thanks

Santosh

-Original Message-
From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: Monday, October 30, 2017 9:04 PM
To: Gore, Santosh <santosh_g...@dell.com>; linux-poweredge-Lists 
<linux-powere...@lists.us.dell.com>
Subject: Re: [Linux-PowerEdge] dsu segfaults



hi Santhos



would it be right to assume that the segfaults have something to do or are 
direct cause for dsu on my r815 to see/report only one NIC out of three?



regards, L.



On 30/10/17 04:55, santosh.g...@dell.com<mailto:santosh.g...@dell.com> wrote:


Dell - Internal Use - Confidential
Hi
Thanks for providing the information. This issue is fixed and will be available 
in the next DSU release.
Thanks
Santosh
-Original Message-
From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: Friday, October 27, 2017 6:52 PM
To: linux-poweredge-Lists 
<linux-powere...@lists.us.dell.com<mailto:linux-powere...@lists.us.dell.com>>
Subject: [Linux-PowerEdge] dsu segfaults
@dell developers
during dsu operation, like here:
$ dsu -u --log-level=4
DELL EMC System Update 1.5.0
Copyright (C) 2014 DELL EMC Proprietary.
Verifying catalog installation ...
Installing catalog from repository ...
Fetching dsucatalog ...
Reading the catalog ...
Verifying inventory collector installation ...
Getting System Inventory ...
warning: Inventory collector returned with partial failure.
Determining Applicable Updates ...
No Applicable Updates Available
Exiting DSU!
$ echo $?
R815, OS, Centos 7.4 reports:

[Fri Oct 27 14:17:24 2017] sasdupie[114626]: segfault at
7ffb9440c5b0 ip 7f06627f6f5b sp 7ffc12009f98 error 4 in 
libc-2.17.so[7f06626c+1b8000] [Fri Oct 27 14:18:11 2017] traps: 
MarvCtrlIE[116522] general protection ip:7f9c4546338b sp:7ffd6583fe50 error:0 
in libc-2.17.so[7f9c453f8000+1b8000] ...
regards, L.
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com<mailto:Linux-PowerEdge@dell.com>
https://lists.us.dell.com/mailman/listinfo/linux-poweredge



___

Linux-PowerEdge mailing list

Linux-PowerEdge@dell.com<mailto:Linux-PowerEdge@dell.com>

https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] DSU on CentOS Linux release 7.4.1708

[lejeczek]

it should work on Centos, I run ver 1.5.1 and no problems, 
well.. not this problem.


On 14/11/17 16:54, Cashmore, Lee (CHKS) wrote:


Hi I have been trying to use DSU to update the hardware on 
my R710  but it fails at the inventory collection stage.


After digging into the errors it seems the problem is the 
inventory collector:


# /usr/libexec/dell_dup/invcol_N5JVK_LN64_17_09_000_1266_A00



invcolVersion="17.09.000 (BLD_1266)" invcolBuild="1266" 
timeStamp="2017-11-14T16:26:25">


    osArch="x64" majorVersion="package redhat-release-server 
is not installed" minorVersion="3.10.0-693.5.2.el7.x86_64"/>


    componentID="2331" display="OpenManage Server Administrator">


display="OpenManage Server Administrator"/>


I’m guessing that the error above about the 
redhat-release-server package not being installed is the 
issue, this package is not available on CentOS.


Any suggestions of a workaround would be fantastic as I 
would like to get these servers updated and have several 
to do.


Kind Regards

Lee

*Lee Cashmore*



This email and any attachment to it are confidential.  
Unless you are the intended recipient, you may not use, 
copy or disclose either the message or any information 
contained in the message. If you are not the intended 
recipient, you should delete this email and notify the 
sender immediately.


Any views or opinions expressed in this email are those of 
the sender only, unless otherwise stated.  All copyright 
in any Capita material in this email is reserved.


All emails, incoming and outgoing, may be recorded by 
Capita and monitored for legitimate business purposes.


Capita exclude all liability for any loss or damage 
arising or resulting from the receipt, use or transmission 
of this email to the fullest extent permitted by law.


 This message has been scanned for malware by Websense. 
www.websense.com 




___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] omconfig biossetup & passwords

[lejeczek]

hi everyone

I cannot remember for certain - did we have features/options 
for bios security/passwords in omsa?
I'm looking but it does not seem like omsa could 
re/set/clear BIOS' passwords?


regards, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] dsu segfaults

[lejeczek]

hi Santhos

would it be right to assume that the segfaults have 
something to do or are direct cause for dsu on my r815 to 
see/report only one NIC out of three?


regards, L.

On 30/10/17 04:55, santosh.g...@dell.com wrote:

Dell - Internal Use - Confidential

Hi

Thanks for providing the information. This issue is fixed and will be available 
in the next DSU release.

Thanks
Santosh

-Original Message-
From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: Friday, October 27, 2017 6:52 PM
To: linux-poweredge-Lists <linux-powere...@lists.us.dell.com>
Subject: [Linux-PowerEdge] dsu segfaults

@dell developers

during dsu operation, like here:

$ dsu -u --log-level=4
DELL EMC System Update 1.5.0
Copyright (C) 2014 DELL EMC Proprietary.
Verifying catalog installation ...
Installing catalog from repository ...
Fetching dsucatalog ...
Reading the catalog ...
Verifying inventory collector installation ...
Getting System Inventory ...
warning: Inventory collector returned with partial failure.
Determining Applicable Updates ...
No Applicable Updates Available
Exiting DSU!
$ echo $?

R815, OS, Centos 7.4 reports:


[Fri Oct 27 14:17:24 2017] sasdupie[114626]: segfault at
7ffb9440c5b0 ip 7f06627f6f5b sp 7ffc12009f98 error 4 in 
libc-2.17.so[7f06626c+1b8000] [Fri Oct 27 14:18:11 2017] traps: 
MarvCtrlIE[116522] general protection ip:7f9c4546338b sp:7ffd6583fe50 error:0 
in libc-2.17.so[7f9c453f8000+1b8000] ...

regards, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] dsu segfaults

[lejeczek]

@dell developers

during dsu operation, like here:

$ dsu -u --log-level=4
DELL EMC System Update 1.5.0
Copyright (C) 2014 DELL EMC Proprietary.
Verifying catalog installation ...
Installing catalog from repository ...
Fetching dsucatalog ...
Reading the catalog ...
Verifying inventory collector installation ...
Getting System Inventory ...
warning: Inventory collector returned with partial failure.
Determining Applicable Updates ...
No Applicable Updates Available
Exiting DSU!
$ echo $?

R815, OS, Centos 7.4 reports:


[Fri Oct 27 14:17:24 2017] sasdupie[114626]: segfault at 
7ffb9440c5b0 ip 7f06627f6f5b sp 7ffc12009f98 error 4 
in libc-2.17.so[7f06626c+1b8000]
[Fri Oct 27 14:18:11 2017] traps: MarvCtrlIE[116522] general 
protection ip:7f9c4546338b sp:7ffd6583fe50 error:0 in 
libc-2.17.so[7f9c453f8000+1b8000]

...

regards, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] dsu does not show/see all NICs?

[lejeczek]

hi everyone

@dell

In my r815s(plural) I have three NICs in total, embedded 
4-port, and two more, like this:


$ lspci | grep -i net
01:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
02:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
06:00.0 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
06:00.1 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
06:00.2 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
06:00.3 Ethernet controller: Broadcom Limited NetXtreme 
BCM5719 Gigabit Ethernet PCIe (rev 01)
23:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
23:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
24:00.0 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)
24:00.1 Ethernet controller: Broadcom Limited NetXtreme II 
BCM5709 Gigabit Ethernet (rev 20)


Yet! output of dsu is this:

$ dsu --inventory
DELL EMC System Update 1.5.0
Copyright (C) 2014 DELL EMC Proprietary.
Verifying catalog installation ...
Installing catalog from repository ...
Fetching dsucatalog ...
Reading the catalog ...
Verifying inventory collector installation ...
Getting System Inventory ...
warning: Inventory collector returned with partial failure.

1. OpenManage Server Administrator  ( Version : 8.5.0 )

2. BIOS  ( Version : 3.2.2 )

3. Dell LifeCycle Controller v1.7.5, 1.7.5.4, A00  ( Version 
: 1.7.5.4 )


4. Dell 32 Bit Diagnostics, version 5162 Installer Revision 
14.05.00, 5162A0, 5162.1  ( Version : 5162A0 )


5. iDRAC6  ( Version : 2.90 )

6. Power Supply  ( Version : M1.01.04 )

7. Power Supply  ( Version : M1.01.04 )

8. NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p1)  ( 
Version : 7.10.64 )


9. NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p2)  ( 
Version : 7.10.64 )


10. NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p3)  ( 
Version : 7.10.64 )


11. NetXtreme BCM5719 Gigabit Ethernet PCIe rev 01 (p2p4)  ( 
Version : 7.10.64 )


12. QLogic QLE2462 Adapter  ( Version : 02.23.06 )

13. QLogic QLE2462 Adapter  ( Version : 02.23.06 )

Exiting DSU!


Is above all? Is above correct?

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] dsu catalog missing

[lejeczek]

@dell

problem:

1508837038.974    248 10.5.6.100 TCP_MISS/404 1277 GET 
http://linux.dell.com/repo/hardware/dsu/os_independent/noarch/dsucatalog-17.09.01-2N7GF.noarch.rpm


$ dsu -v
DELL EMC System Update 1.5.0
Copyright (C) 2014 DELL EMC Proprietary.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] tape libraries

[lejeczek]

hi everyone,

and @dell devel

should DSU not include hardware such as LT2000? So we, it, 
would be capable of doing some maintenance but most 
importantly firmware upgrades.

In ver. 8.5 when I do inventory DSU does not notice the 
presence of this hardware, since it's Dell's it should, 
right? It would be very desired bits to have, I think.

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] do we have a tool to flash hdd firmware

[lejeczek]

hi fellas

Seagate's dl_sea_fw-0.2.3_32 fails and sg_write_buffer too 
is unsuccessful when I try to flash ST32000444SS(in external 
enclosure, jbod) connected to just a HBA 12Gbps.
So I wonder if there is any tool Dell's linux offer, would 
you know?

Also, I wonder naturally if you had any thoughts why it 
fails. My one thought is: would it matter that enclosure is 
connected to multiple hosts when I try to flash..

thank, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] dsu download only

[lejeczek]

@dell-tech

could we ask, unless it's already there, that future 
versions of dsu would be able to "download only" updates.
Such an option would be very useful, --download-only or 
something like it.

many thanks, L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] dsu want so downgrade @dell tech

[lejeczek]

hi,
thanks,
I should clarify that the v5162A0 most 100% likely came in 
via dsu as I've been doing only dsu for last few years.
My guess - dsu's repo got it mixed up?

regards
L.

On 26/07/17 14:55, sash...@dell.com wrote:
> Hi,
>
> The Diagnostics updates available on your system is already the latest i.e. 
> v5162A0. However in the latest DSU repository, there's an N-1 update also 
> available (v5158A3) due to which DSU shows as Downgrade.
> We'll check regarding the N-1 update inclusion in DSU repository and get back 
> to you accordingly.
>
> Regards,
> Sashi
>
>
> -Original Message-
> From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists
> Sent: Tuesday, July 25, 2017 10:30 PM
> To: linux-poweredge-Lists <linux-powere...@lists.us.dell.com>
> Subject: Linux-PowerEdge Digest, Vol 158, Issue 11
>
> Send Linux-PowerEdge mailing list submissions to
>   linux-poweredge@dell.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> or, via email, send a message with subject or body 'help' to
>   linux-poweredge-requ...@dell.com
>
> You can reach the person managing the list at
>   linux-poweredge-ow...@dell.com
>
> When replying, please edit your Subject line so it is more specific than "Re: 
> Contents of Linux-PowerEdge digest..."
>
>
> Today's Topics:
>
> 1.  dsu want so downgrade @dell tech (lejeczek)
> 2.  reset LCD with a command? (lejeczek)
> 3. Re:  dsu want so downgrade @dell tech (vinc...@cojot.name)
>
>
> ------
>
> Message: 1
> Date: Tue, 25 Jul 2017 11:00:32 +0100
> From: lejeczek <pelj...@yahoo.co.uk>
> Subject: [Linux-PowerEdge] dsu want so downgrade @dell tech
> To: Linux-PowerEdge@dell.com
> Message-ID: <e5a2d462-5bdc-f67d-36fb-294b15268...@yahoo.co.uk>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> @dell tech
> could you please confirm this is desired action?
>
> [ ]2 Dell 32 Bit Diagnostics, version 5162 Installer Revision 14.05.00, 
> 5162A0, 5162.1 Current Version : 5162A0 Downgrade to : 5158A3
>
> thanks
> L.
>
>
>
> --
>
> Message: 2
> Date: Tue, 25 Jul 2017 15:09:30 +0100
> From: lejeczek <pelj...@yahoo.co.uk>
> Subject: [Linux-PowerEdge] reset LCD with a command?
> To: Linux-PowerEdge@dell.com
> Message-ID: <f012efe6-53dc-ad90-614a-956720a7e...@yahoo.co.uk>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> hi fellas
>
> command line - is there one to reset/clear errors to the normal state?
>
> many thanks
> L.
>
>
>
> --
>
> Message: 3
> Date: Tue, 25 Jul 2017 12:13:15 -0400 (EDT)
> From: vinc...@cojot.name
> Subject: Re: [Linux-PowerEdge] dsu want so downgrade @dell tech
> To: lejeczek <pelj...@yahoo.co.uk>
> Cc: Linux-PowerEdge@dell.com
> Message-ID:
>   <alpine.LRH.2.21.1707251211510.4221@daltigoth.lasthome.solace.krynn>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>
> Hi lejeczek,
>
> I don't think you should say yes. Dsu is probably pointing to the older 
> revision of the firmware. This will probably go away when Dell updates dsu. 
> Until next time, that is..
>
> Regards,
>
> Vincent
>
>
> On Tue, 25 Jul 2017, lejeczek wrote:
>
>> @dell tech
>> could you please confirm this is desired action?
>>
>> [ ]2 Dell 32 Bit Diagnostics, version 5162 Installer Revision
>> 14.05.00, 5162A0, 5162.1 Current Version : 5162A0 Downgrade to :
>> 5158A3
>>
>> thanks
>> L.
>>
>> ___
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge@dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>
>
> --
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
> End of Linux-PowerEdge Digest, Vol 158, Issue 11
> 
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] reset LCD with a command?

[lejeczek]

hi fellas

command line - is there one to reset/clear errors to the 
normal state?

many thanks
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] dsu want so downgrade @dell tech

[lejeczek]

@dell tech
could you please confirm this is desired action?

[ ]2 Dell 32 Bit Diagnostics, version 5162 Installer 
Revision 14.05.00, 5162A0, 5162.1
Current Version : 5162A0 Downgrade to : 5158A3

thanks
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] and a PowerEdge dies..

[lejeczek]

hi guys,

have you seen anything like it or similar on any PE?

PE r815 dies - PSUs do power on but everything else stays 
quiet, no signs of life.

regards
L

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Feedback on OMSA web interface access

[lejeczek]

On 13/03/17 11:55, chandrasekha...@dell.com wrote:


Hello,

A reverse proxy server is a type of proxy server that 
typically sits behind the firewall in a private network 
and directs client requests to the appropriate backend 
server. A reverse proxy provides an additional level of 
abstraction and control to ensure the smooth flow of 
network traffic between clients and servers.


The backend server that could be OMSA web server. And this 
configuration of proxy server and firewall is beyond scope 
of the OMSA application.



not really, a simple example guide would be nice.

Would you have some suggestions on how to troubleshoot 
this(webserver does not start)? :


[Mar 13 21:32:41 2017] (11767) RunServer:daemon sigwait 
returned 0 with sig 15
[Mar 13 21:32:41 2017] (11767) RunServer:daemon waiting for 
shutdown status
[Mar 13 21:32:41 2017] (11768) RunServer:worker recieved 
pipe msg -6.
[Mar 13 21:32:41 2017] (11768) RunServer:worker shutting 
down now

[Mar 13 21:32:41 2017] (11768) ModuleDetach: entry 1
[Mar 13 21:32:41 2017] (11768) ModuleDetach(ERROR): Java 
main thread exited before calling shutdown!
[Mar 13 21:32:41 2017] (11768) ModuleDetach: waiting for 
StartServer thread to finish...

[Mar 13 21:32:41 2017] (11768) ModuleDetach: exit
[Mar 13 21:32:41 2017] (11768) RunServer:worker process EXIT 
status(0)

[Mar 13 21:32:41 2017] (11768) RunServer exit with status(0)
[Mar 13 21:32:41 2017] (11767) RunServer:daemon process EXIT 
status(0)

[Mar 13 21:32:42 2017] (11966) RunServer: entry...
[Mar 13 21:32:42 2017] (11966) RunServer:parent preparing to 
fork daemon process

[Mar 13 21:32:42 2017] (11966) RunServer:parent daemon forked
[Mar 13 21:32:42 2017] (11966) RunServer:parent waiting for 
daemon init status

[Mar 13 21:32:42 2017] (11967) RunServer:daemon process entry
[Mar 13 21:32:42 2017] (11967) RunServer:daemon worker forked
[Mar 13 21:32:42 2017] (11967) RunServer:daemon waiting for 
worker init status

[Mar 13 21:32:42 2017] (11968) RunServer:worker process entry
[Mar 13 21:32:42 2017] (11968) ModuleAttach: entry 0
[Mar 13 21:32:42 2017] (11968) ModuleAttach: starting the 
startserver thread

[Mar 13 21:32:42 2017] (11968) ModuleAttach: exit
[Mar 13 21:32:42 2017] (11968) RunServer: ModuleAttach success
[Mar 13 21:32:42 2017] (11968) RunServer:worker waiting for 
shutdown message...
[Mar 13 21:32:42 2017] (11967) RunServer:daemon waiting for 
shutdown signal...
[Mar 13 21:32:42 2017] (11966) RunServer:parent process EXIT 
status(0)

r$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 6 more
Exception in thread "RegisterThread" 
java.lang.NoClassDefFoundError: com/dell/oma/db/DataBridgeBroker
at 
com.dell.oma.common.OMACSUtil.OMACSSendCmdToDA(Unknown Source)

at com.dell.oma.common.OMACSUtil.a(Unknown Source)
at com.dell.oma.common.OMACSUtil.getCSDAData(Unknown 
Source)
at 
com.dell.oma.common.OMACSUtil.getOMAInstallPath(Unknown Source)
at 
com.dell.oma.registration.OMARegistrationEngine.addClass(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.addClass(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.b(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.a(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.getInstance(Unknown 
Source)
at com.dell.oma.registration.OMAWebServer.run(Unknown 
Source)

at java.lang.Thread.run(Thread.java:745)

Above is logged just after - srvadmin-services.sh restart 
dsm_om_connsvc - and then nothing seems to attach to 1311 port.


many thank,
L



Regards

Chandra

*From:*lejeczek [mailto:pelj...@yahoo.co.uk]
*Sent:* Saturday, March 11, 2017 6:58 PM
*To:* R, Chandrasekhar <chandrasekha...@dell.com>; 
linux-poweredge-Lists <linux-powere...@lists.us.dell.com>

*Subject:* Re: Feedback on OMSA web interface access

great! thanks.

Would you also have a howto on "reverse proxy"? I imagine 
that must be something many ask for.


regards
L.

On 10/03/17 10:54, chandrasekha...@dell.com 
<mailto:chandrasekha...@dell.com> wrote:


Hello,

Thank you for using Dell EMC OpenManage.

By default, OMSA Connection service (Web service) is
running and listening on a default secure port which
is 1311. However, the default port can be changed to
your preferred port number through web interface.
Kindly refer OMSA UG (page 32) for detailed steps to
change the default port number.
OMSA UG can be downloaded at:

http://topics-cdn.dell.com/pdf/dell-openmanage-server-administrator-8.4_User's%20Guide2_en-us.pdf

<http://topics-cdn.dell.com/pdf/dell-openmanage-server-administrator-8.4_User%27s%20Guide2_en-us.pdf>

Kindly let us know if you need more details.

Regards

Chandra

--

Message: 1
Date: Thu, 9 Mar 2017 17:14

[Linux-PowerEdge] webserver: Exception in thread "RegisterThread" java.lang.NoClassDefFoundError: com/dell/oma/db/DataBridgeBroker

[lejeczek]

hi folks

on one box, curiously, another one seems fine, webserver 
fails to start and I see:


...
Mar 11 13:47:05 2017] (61750) RunServer:daemon process entry
[Mar 11 13:47:05 2017] (61750) RunServer:daemon worker forked
[Mar 11 13:47:05 2017] (61750) RunServer:daemon waiting for 
worker init status

[Mar 11 13:47:05 2017] (61751) RunServer:worker process entry
[Mar 11 13:47:05 2017] (61751) ModuleAttach: entry 0
[Mar 11 13:47:05 2017] (61751) ModuleAttach: starting the 
startserver thread

[Mar 11 13:47:05 2017] (61751) ModuleAttach: exit
[Mar 11 13:47:05 2017] (61751) RunServer: ModuleAttach success
[Mar 11 13:47:05 2017] (61751) RunServer:worker waiting for 
shutdown message...
[Mar 11 13:47:05 2017] (61750) RunServer:daemon waiting for 
shutdown signal...
[Mar 11 13:47:05 2017] (61749) RunServer:parent process EXIT 
status(0)

r$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 6 more
Exception in thread "RegisterThread" 
java.lang.NoClassDefFoundError: com/dell/oma/db/DataBridgeBroker
at 
com.dell.oma.common.OMACSUtil.OMACSSendCmdToDA(Unknown Source)

at com.dell.oma.common.OMACSUtil.a(Unknown Source)
at com.dell.oma.common.OMACSUtil.getCSDAData(Unknown 
Source)
at 
com.dell.oma.common.OMACSUtil.getOMAInstallPath(Unknown Source)
at 
com.dell.oma.registration.OMARegistrationEngine.addClass(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.addClass(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.b(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.a(Unknown 
Source)
at 
com.dell.oma.registration.OMARegistrationEngine.getInstance(Unknown 
Source)
at com.dell.oma.registration.OMAWebServer.run(Unknown 
Source)

at java.lang.Thread.run(Thread.java:745)

I sroogled it but found nothing concrete. Would you have 
some suggestions?

b.w.
L.
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Feedback on OMSA web interface access

[lejeczek]

great! thanks.

Would you also have a howto on "reverse proxy"? I imagine 
that must be something many ask for.


regards
L.

On 10/03/17 10:54, chandrasekha...@dell.com wrote:


Hello,

Thank you for using Dell EMC OpenManage.

By default, OMSA Connection service (Web service) is 
running and listening on a default secure port which is 
1311. However, the default port can be changed to your 
preferred port number through web interface. Kindly refer 
OMSA UG (page 32) for detailed steps to change the default 
port number.
OMSA UG can be downloaded at: 
http://topics-cdn.dell.com/pdf/dell-openmanage-server-administrator-8.4_User's%20Guide2_en-us.pdf 
<http://topics-cdn.dell.com/pdf/dell-openmanage-server-administrator-8.4_User%27s%20Guide2_en-us.pdf>


Kindly let us know if you need more details.

Regards

Chandra

--

Message: 1
Date: Thu, 9 Mar 2017 17:14:44 +0000
From: lejeczek
Subject: Re: [Linux-PowerEdge] Feedback on OMSA web 
interface access

To: omsa_feedb...@dell.com, linux-powere...@lists.us.dell.com
Message-ID:
Content-Type: text/plain; charset="utf-8"

I've been fond of cli but wanting to try web gui (would 
like to consolidate, centralize my installations) and... I 
have a

question: why this(by default)?

$ netstat -utapn | grep 1311
tcp6 0 0 :::1311 :::* LISTEN
14412/dsm_om_connsv

And yes, these documentation bits are missing.
Would be great to have a separate pdf for 
web-server(tomcat, etc), or even better! have docs/man 
pages included in rpm package! (though, now when I think 
about it, these pdfs / docs should be in repo anyway, repo 
is best place, we don't have to sroogle then).


And it seems that Dell ignores the concept of man pages. 
Man page is the first place a user, an admin will go to, 
expecting most comprehensive and up to date information.


yes, please, keep developing & improving Linux OMSA, 
including web bits.

L

On 06/12/16 17:20, omsa_feedb...@dell.com wrote:
>
> *Dell - Internal Use - Confidential *
>
> [ if you are not comfortable responding to the entire 
mailing list,

> please respond directly to *omsa_feedb...@dell.com*]
>
> Hi!
>
> Dell is conducting a survey to determine how customers are
> using the OpenManage Server Administrator
> (OMSA) web browser interface in a Linux environment. We 
request you to
> take out few minutes from your busy schedule, your 
feedback will help

> us make better decisions in future releases of OMSA.
>
> If you are using OMSA on either of the supported OS 
(RHEL/SUSE Linux
> Enterprise) or community supported OS (Ubuntu), we would 
like to hear
> from you. Request you to provide responses for the 
following

> questions -
>
> 1.Do you access the web browser interface provided by 
OMSA? If yes,

> please provide your primary activity in the web interface.
>
> 2.OS Type in use (RHEL/SLES/Ubuntu...)
>
> 3.Number of OMSA installations in your organization
>
> Regards
>
> Dell team
>
>
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20170309/9a34b057/attachment-0001.html 



--

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

End of Linux-PowerEdge Digest, Vol 154, Issue 9
***



___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Feedback on OMSA web interface access

[lejeczek]

I've been fond of cli but wanting to try web gui (would like 
to consolidate, centralize my installations) and... I have a 
question: why this(by default)?


$ netstat -utapn | grep 1311
tcp6   0  0 :::1311 :::* LISTEN  
14412/dsm_om_connsv


And yes, these documentation bits are missing.
Would be great to have a separate pdf for web-server(tomcat, 
etc), or even better! have docs/man pages included in rpm 
package! (though, now when I think about it, these pdfs / 
docs should be in repo anyway, repo is best place, we don't 
have to sroogle then).


And it seems that Dell ignores the concept of man pages. Man 
page is the first place a user, an admin will go to, 
expecting most comprehensive and up to date information.


yes, please, keep developing & improving Linux OMSA, 
including web bits.

L

On 06/12/16 17:20, omsa_feedb...@dell.com wrote:


*Dell - Internal Use - Confidential *

[ if you are not comfortable responding to the entire 
mailing list, please respond directly to 
*omsa_feedb...@dell.com*]


Hi!

   Dell is conducting a survey to determine how 
customers are using the OpenManage Server Administrator 
(OMSA) web browser interface in a Linux environment. We 
request you to take out few minutes from your busy 
schedule, your feedback will help us make better decisions 
in future releases of OMSA.


If you are using OMSA on either of the supported OS 
(RHEL/SUSE Linux Enterprise) or community supported OS 
(Ubuntu), we would like to hear from you.  Request you to 
provide responses for the following questions -


1.Do you access the web browser interface provided by 
OMSA?  If yes, please provide your primary activity in the 
web interface.


2.OS Type in use (RHEL/SLES/Ubuntu...)

3.Number of OMSA installations in your organization

Regards

Dell team



___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Invalid SAS topology detected - from H800

[lejeczek]

On 23/02/17 17:04, patrick.b...@dell.com wrote:

Dell - Internal Use - Confidential

This message is typically due to a loop in the SAS topology. You should make 
sure you have the system cabled correctly.


I also see:

13036 (541181531s/0x0010/CRIT) - SAS topology error: Table 
to table


would this confirm loop problem?
Is there a way to troubleshoot, gather more info?



From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: Thursday, February 23, 2017 11:00 AM
To: linux-poweredge-Lists <linux-powere...@lists.us.dell.com>
Subject: [Linux-PowerEdge] Invalid SAS topology detected - from H800

hi everyone

I hooked a sas3 chassis to Perc H800 and first thing, controller moans:

"Invalid SAS topology detected. Please check your cable configurations, repair the 
problem, and restart your system"

Has somebody seen it? I wonder how much o a dysfunctional array that makes it.

b.w.
L


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Invalid SAS topology detected - from H800

[lejeczek]

On 23/02/17 17:04, patrick.b...@dell.com wrote:

Dell - Internal Use - Confidential

This message is typically due to a loop in the SAS topology. You should make 
sure you have the system cabled correctly.


how much of this actually can be due to actually cable?
I'm using:
Manufacturer Part# : GJD6D
Dell Part# : 470-A

And just one port 0 of H800 connected.
many thanks,
L.



From: linux-poweredge-bounces-Lists On Behalf Of lejeczek
Sent: Thursday, February 23, 2017 11:00 AM
To: linux-poweredge-Lists <linux-powere...@lists.us.dell.com>
Subject: [Linux-PowerEdge] Invalid SAS topology detected - from H800

hi everyone

I hooked a sas3 chassis to Perc H800 and first thing, controller moans:

"Invalid SAS topology detected. Please check your cable configurations, repair the 
problem, and restart your system"

Has somebody seen it? I wonder how much o a dysfunctional array that makes it.

b.w.
L


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] dsm_sa_datamgrd segfault that crahses whole system

[lejeczek]

hi everybody
also hopefully Dell tech as this should be directly hardware 
related I believe.


I manage to segfault omsa(which then crashes the whole system):

[ 1117.103438] dsm_sa_datamgrd[28952]: segfault at 0 ip 
7f2e1ab57b46 sp 7f2e1197c020 error 4 in 
libdsm_sm_sasvil.so[7f2e1aae8000+bb000]


Simply by having one H700 in one specific PCI slot in my 
R815 servers.
Server(s) setup in somewhat not-usual, I've stumbled upon 
this segfault purely by a chance.


I have "embedded" H200 in "integrated storage controller 
card slot"

I have a Dell Broadcom 4port NIC in "expansion-card slot 2"
I have a H700 in "expansion-card riser 1"
Lastly I have a H800 in "expansion-card slot 5"

H700 was installed for we are going to move hdd array from 
H200 to H700(but not just yet so we put the H700 card only).


1)Now:
when H700 is in "expansion-card slot 2" everything is 
working perfectly fine, no segfaults.
But "expansion-card slot 1" is pcieX8 which matches H700, 
and "expansion-card slot 2" is only pcieX4.


2)Now: segfault seems to occur only when I run omxxx storage 
on that specific H700 controller.


$ omreport storage vdisk vdisk=0 controller=1 - H200, no 
segfaults

$ omreport storage vdisk vdisk=0 controller=0 - H700, segfaul!

omreport system summary - does not cause it.
After ~20sec after segfault the system suffers from 
hard/cold power cycle.


So this seems critical. It would be expected of tech-team to 
investigate it.
Separately I'm going to report "tech support request" but 
felt sharing with other R815's I should do.


b.w.
L


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] should perccli report raid10 inconsistent

[lejeczek]

hi everyone
I'm seeing this below and I wonder why?
...
/c0/v1 :
==

---
DG/VD TYPE   State Access Consist Cache Cac sCC  Size Name
---
3/1   RAID10 Optl  RW No  RWBC  R   OFF 18.188 TB
---

Cac=CacheCade|Rec=Recovery|OfLn=OffLine|Pdgd=Partially 
Degraded|dgrd=Degraded
Optl=Optimal|RO=Read Only|RW=Read 
Write|B=Blocked|Consist=Consistent|
R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack|
AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct 
IO|sCC=Scheduled
Check Consistency


PDs for VD 1 :


---
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp
---
50:0 76 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1 75 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:2 57 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:3181 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:4 33 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:5179 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:6 37 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:7 45 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:8 36 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:9 28 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1046 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1131 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1226 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1343 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1427 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1529 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1753 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1855 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:1989 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
50:2054 Onln   3 1.818 TB SAS  HDD N   N  512B 
ST32000444SS U
---

EID-Enclosure Device ID|Slt-Slot No.|DID-Device ID|DG-DriveGroup
DHS-Dedicated Hot Spare|UGood-Unconfigured Good|GHS-Global 
Hotspare
UBad-Unconfigured Bad|Onln-Online|Offln-Offline|Intf-Interface
Med-Media Type|SED-Self Encryptive Drive|PI-Protection Info
SeSz-Sector Size|Sp-Spun|U-Up|D-Down|T-Transition|F-Foreign
UGUnsp-Unsupported|UGShld-UnConfigured 
shielded|HSPShld-Hotspare shielded
CFShld-Configured shielded


VD1 Properties :
==
Strip Size = 64 KB
Number of Blocks = 39059456000
Span Depth = 2
Number of Drives Per Span = 10
Write Cache(initial setting) = WriteBack
Disk Cache Policy = Enabled
Encryption = None
Data Protection = None
Active Operations = Background Initialization (0%)
Exposed to OS = Yes
Creation Date = 03-02-2017
Creation Time = 04:14:41 PM
Emulation type = None

#end
Would you know if this is normal?
I also cannot start consistency check:

$ perccli /c0/v1 start cc force
Controller = 0
Status = Failure
Description = None

Detailed Status :
===


VD Operation Status ErrCd ErrMsg

  1 CCFailed  1001 Start CC not possible


to me it's weird, but then, it's my fist raid10 on Dell 
hardware.
many thanks,
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] iDracs as fencing device in ha cluster

[lejeczek]

On 17/01/17 19:00, Stefan M. Radman wrote:
> Hi Lejeczek
>
>> my iDrac6 currently runs off a dedicated NIC, and afaik it can be either 
>> that or "shared".
> If your iDRAC6 has a dedicated NIC it's an iDRAC6 Enterprise.
> Available modes on the iDRAC6 Enterprise are: Dedicated, Shared, Shared with 
> Failover LOM2, and Shared with Failover All LOMs.
> http://www.dell.com/support/article/us/en/19/SLN85572
>
>> Thus, with "dedicated" not failover, am I right?
> With "dedicated" the switch your iDRAC6 is connected to becomes a single 
> point of failure in your fencing logic.

it must have begged the question - why Dell would not make 
"Dedicated with Failover to..."
I wonder if ever Dell answered this.

>> And one would not sacrifice "dedicated" for redundancy, would one?
> Yes, I would. What do you gain with "Dedicated"?
> Use one of the "Shared with Failover" modes and redundant network paths the 
> same way you do with other cluster interfaces.
>
> Stefan
>
>> On Jan 17, 2017, at 6:32 PM, lejeczek <pelj...@yahoo.co.uk> wrote:
>>
>>
>>
>> On 14/12/16 12:52, Stefan M. Radman wrote:
>>> Hi Lejeczek,
>>>
>>> The Red Hat Access website has two solution documents (content restricted 
>>> to subscribers).
>>> One for rgmanager (RHEL5-6)
>>> How to configure fence_ipmilan with Red Hat Enterprise Linux High 
>>> Availability Add On
>>> https://access.redhat.com/solutions/54843
>>> and one for pacemaker (RHEL 6-7)
>>> How to configure fence_ipmilan with Red Hat Enterprise Linux High 
>>> Availability Pacemaker Add On on RHEL 6, 7
>>> https://access.redhat.com/solutions/2271811
>>>
>>> One of my favorite open resources is Clusterlabs
>>> http://wiki.clusterlabs.org/wiki/Configure_Multiple_Fencing_Devices_Using_pcs
>>>
>>> The pacemaker solution has been working reliably here (RHEL6,HA 
>>> AddOn,PE720) for more than two years now and actually triggered a few 
>>> times, at least once during an actual hardware issue.
>>>
>>> Here is the stonith configuration we're using in a 2-node HA cluster 
>>> running pacemaker on RHEL6:
>>>
>>> # pcs stonith create node1-pwr fence_ipmilan ipaddr=192.168.1.1 
>>> lanplus=true login=root passwd=calvin pcmk_host_list=node1
>>> # pcs resource ban node1-pwr node1
>>> # pcs stonith create node2-pwr fence_ipmilan ipaddr=192.168.1.2 
>>> lanplus=true login=root passwd=calvin pcmk_host_list=node2
>>> # pcs resource ban node2-pwr node2
>>> # pcs stonith show
>>>   node2-pwr (stonith:fence_ipmilan): Started node1
>>>   node1-pwr (stonith:fence_ipmilan): Started node2
>>>
>>> Make sure you have IPMI and redundancy (NIC failover) properly set up on 
>>> your iDRAC.
>>>
>>> Stefan
>> oh, this is nice, many! thanks Stefan
>> my iDrac6 currently runs off a dedicated NIC, and afaik it can be either 
>> that or "shared".
>> Thus, with "dedicated" not failover, am I right?
>> And one would not sacrifice "dedicated" for redundancy, would one?
>> regards
>>
>>
>>> On Dec 14, 2016, at 11:55 AM, lejeczek 
>>> <pelj...@yahoo.co.uk<mailto:pelj...@yahoo.co.uk>> wrote:
>>>
>>> hi everybody
>>>
>>> just a quick question, probably very easy for you guys -
>>> iDracs as fencing device in HA configs(rhel's)? Would there
>>> be any docs/howtos?
>>> Or maybe there is better way to do that with PE servers?
>>>
>>> many thanks,
>>> L.
>>>
>>> ___
>>> Linux-PowerEdge mailing list
>>> Linux-PowerEdge@dell.com<mailto:Linux-PowerEdge@dell.com>
>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>>

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] iDracs as fencing device in ha cluster

[lejeczek]

On 14/12/16 12:52, Stefan M. Radman wrote:
> Hi Lejeczek,
>
> The Red Hat Access website has two solution documents (content restricted to 
> subscribers).
> One for rgmanager (RHEL5-6)
> How to configure fence_ipmilan with Red Hat Enterprise Linux High 
> Availability Add On
> https://access.redhat.com/solutions/54843
> and one for pacemaker (RHEL 6-7)
> How to configure fence_ipmilan with Red Hat Enterprise Linux High 
> Availability Pacemaker Add On on RHEL 6, 7
> https://access.redhat.com/solutions/2271811
>
> One of my favorite open resources is Clusterlabs
> http://wiki.clusterlabs.org/wiki/Configure_Multiple_Fencing_Devices_Using_pcs
>
> The pacemaker solution has been working reliably here (RHEL6,HA AddOn,PE720) 
> for more than two years now and actually triggered a few times, at least once 
> during an actual hardware issue.
>
> Here is the stonith configuration we're using in a 2-node HA cluster running 
> pacemaker on RHEL6:
>
> # pcs stonith create node1-pwr fence_ipmilan ipaddr=192.168.1.1 lanplus=true 
> login=root passwd=calvin pcmk_host_list=node1
> # pcs resource ban node1-pwr node1
> # pcs stonith create node2-pwr fence_ipmilan ipaddr=192.168.1.2 lanplus=true 
> login=root passwd=calvin pcmk_host_list=node2
> # pcs resource ban node2-pwr node2
> # pcs stonith show
>   node2-pwr (stonith:fence_ipmilan): Started node1
>   node1-pwr (stonith:fence_ipmilan): Started node2
>
> Make sure you have IPMI and redundancy (NIC failover) properly set up on your 
> iDRAC.
>
> Stefan
oh, this is nice, many! thanks Stefan
my iDrac6 currently runs off a dedicated NIC, and afaik it 
can be either that or "shared".
Thus, with "dedicated" not failover, am I right?
And one would not sacrifice "dedicated" for redundancy, 
would one?
regards


>
> On Dec 14, 2016, at 11:55 AM, lejeczek 
> <pelj...@yahoo.co.uk<mailto:pelj...@yahoo.co.uk>> wrote:
>
> hi everybody
>
> just a quick question, probably very easy for you guys -
> iDracs as fencing device in HA configs(rhel's)? Would there
> be any docs/howtos?
> Or maybe there is better way to do that with PE servers?
>
> many thanks,
> L.
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com<mailto:Linux-PowerEdge@dell.com>
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Firmware-upgrades for the network-controllers after the Broadcom NX -> QLogic handover seem to fail with dsu

[lejeczek]

I understand it may take a while, if there is indeed some 
problem with that new firmware.
It's only an observation, nothing deterministic, but on my 
R815 having a second(one is already on-board) NIC would make 
system spit "PCI Fatal error" regarding that second card, 
although system would seemingly continue to work without any 
network interruption. This would happen with both Linux & 
Windows. This would happen more likely when I take ports 
down & up and either by software or manually unplugging cables.
To solidly investigate it may take Dell tech a wile, I'd 
wish not too long one.
L.

On 16/01/17 13:52, Malte Schmidt wrote:
> Is there any update on this?
>
> Am 12.01.2017 um 16:59 schrieb kalyan.moha...@dell.com:
>> We are looking into the issue, will respond back asap.
>> Thanks,
>> Kalyan.
>> 
>> From: linux-poweredge-bounces-Lists On Behalf Of lejeczek 
>> [pelj...@yahoo.co.uk]
>> Sent: Thursday, January 12, 2017 8:11 PM
>> To: Malte Schmidt; linux-poweredge-Lists
>> Subject: Re: [Linux-PowerEdge] Firmware-upgrades for the network-controllers 
>> after the Broadcom NX -> QLogic handover seem to fail with dsu
>>
>> I've asked very similar question a few weeks ago, and have also emailed 
>> directly couple of Dell's tech guys who post here, but.. no reply?! 
>> whatsoever.
>>
>> the subject of that email of mine was "NetXtreme II BCM5709 - DSU want to 
>> dowgrade - ok?"
>>
>> I think at that point it qualifies for official support request ticket - if 
>> you have support contract for you systems - and also official complaint.
>>
>> Anybody else is having NetXtreme II BCM5709 ?
>>
>>
>> On 11/01/17 17:08, Malte Schmidt wrote:
>>
>> Forgot to mention the dsu- and catalog-Versions:
>>
>> dell-system-update.x86_64
>> 0:1.3.1-16.12.00
>> dsucatalog.noarch 0:16.12.00-684PR
>>
>>
>> Am 11.01.2017 um 18:02 schrieb Malte Schmidt:
>>
>>
>> I am currently running a PowerEdge R210 II with the BCM 5716 controller
>> and trying to upgrade the firmware as follows:
>>
>> 08.07.25 -> 08.07.26
>>
>> but dsu shows me that only a downgrade (to a version from February)
>> would be possible:
>>
>> [ ]3 NetXtreme II BCM5716 Gigabit Ethernet rev 20 (em2)
>>   Current Version : 08.07.25 Downgrade to : 7.12.19
>>
>> [ ]4 NetXtreme II BCM5716 Gigabit Ethernet rev 20 (em1)
>>   Current Version : 08.07.25 Downgrade to : 7.12.19
>>
>> Is this some sort of a bug?
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge@dell.com<mailto:Linux-PowerEdge@dell.com>
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>>
>
>
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Firmware-upgrades for the network-controllers after the Broadcom NX -> QLogic handover seem to fail with dsu

[lejeczek]

I've asked very similar question a few weeks ago, and have 
also emailed directly couple of Dell's tech guys who post 
here, but.. no reply?! whatsoever.


the subject of that email of mine was "NetXtreme II BCM5709 
- DSU want to dowgrade - ok?"


I think at that point it qualifies for official support 
request ticket - if you have support contract for you 
systems - and also official complaint.


Anybody else is having NetXtreme II BCM5709 ?


On 11/01/17 17:08, Malte Schmidt wrote:

Forgot to mention the dsu- and catalog-Versions:

dell-system-update.x86_64
0:1.3.1-16.12.00
dsucatalog.noarch 0:16.12.00-684PR


Am 11.01.2017 um 18:02 schrieb Malte Schmidt:

I am currently running a PowerEdge R210 II with the BCM 5716 controller
and trying to upgrade the firmware as follows:

08.07.25 -> 08.07.26

but dsu shows me that only a downgrade (to a version from February)
would be possible:

[ ]3 NetXtreme II BCM5716 Gigabit Ethernet rev 20 (em2)
  Current Version : 08.07.25 Downgrade to : 7.12.19

[ ]4 NetXtreme II BCM5716 Gigabit Ethernet rev 20 (em1)
  Current Version : 08.07.25 Downgrade to : 7.12.19

Is this some sort of a bug?




___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge


___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] does your kdump work?

[lejeczek]

like I said "..Different kernels, official and 
third-parties, still fails..."
Same Centos on a VM (as a guest on the box where kdump 
fails) starts kdump fine.

smells like the hardware. Dell tech, are you there guys?


On 06/01/17 17:00, vinc...@cojot.name wrote:
>
> Oh and btw, is there any reason that you're running 4.9.0 
> and not the usual 3.10.0 kernel on el7/centos? That might 
> explain some of the breakage..
>
> Vincent
>
> On Fri, 6 Jan 2017, lejeczek wrote:
>
>> it does not start at all
>>
>> lrwxrwxrwx   1 root root   11 Jan  6 12:45 
>> var/lock -> ../run/lock
>> lrwxrwxrwx   1 root root6 Jan  6 12:45 
>> var/run -> ../run
>>  
>>
>> *** Creating initramfs image file 
>> '/boot/initramfs-4.9.0-1.el7.elrepo.x86_64kdump.img' done 
>> ***
>> No memory reserved for crash kernel.
>> Starting kdump: [FAILED]
>> kdump.service: main process exited, code=exited, 
>> status=1/FAILURE
>>
>> Centos 7.x
>> I've tried various args to crashkernel= but no help from 
>> it. Different kernels, official and third-parties, still 
>> fails.
>> BIOS?? Some advise on Intel switch off IOMMU, which I did 
>> although it's AMD.
>>
>>
>> On 06/01/17 14:57, vinc...@cojot.name wrote:
>>> What's your OS and what are the relevant parts of your 
>>> kdump.conf?
>>> when you mention it does work. is it that it doesn't 
>>> kdump at all, panics
>>> upon entering the kdump kernel or some other thing?
>>>
>>> Vincent
>>>
>>> On Fri, 6 Jan 2017, lejeczek wrote:
>>>
>>>> hi all
>>>>
>>>> mine does not, I have a few R815 none is good, and I've
>>>> tampered with it in many ways, cannot get it to work.
>>>> With IOMMU disabled still no good gee.
>>>>
>>>> best,
>>>> L.
>>>>
>>>> ___
>>>> Linux-PowerEdge mailing list
>>>> Linux-PowerEdge@dell.com
>>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>>>
>>> ___
>>> Linux-PowerEdge mailing list
>>> Linux-PowerEdge@dell.com
>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>>

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] does your kdump work?

[lejeczek]

it does not start at all

lrwxrwxrwx   1 root root   11 Jan  6 12:45 
var/lock -> ../run/lock
lrwxrwxrwx   1 root root6 Jan  6 12:45 
var/run -> ../run

*** Creating initramfs image file 
'/boot/initramfs-4.9.0-1.el7.elrepo.x86_64kdump.img' done ***
No memory reserved for crash kernel.
Starting kdump: [FAILED]
kdump.service: main process exited, code=exited, 
status=1/FAILURE

Centos 7.x
I've tried various args to crashkernel= but no help from it. 
Different kernels, official and third-parties, still fails.
BIOS?? Some advise on Intel switch off IOMMU, which I did 
although it's AMD.


On 06/01/17 14:57, vinc...@cojot.name wrote:
> What's your OS and what are the relevant parts of your kdump.conf?
> when you mention it does work. is it that it doesn't kdump at all, panics
> upon entering the kdump kernel or some other thing?
>
> Vincent
>
> On Fri, 6 Jan 2017, lejeczek wrote:
>
>> hi all
>>
>> mine does not, I have a few R815 none is good, and I've
>> tampered with it in many ways, cannot get it to work.
>> With IOMMU disabled still no good gee.
>>
>> best,
>> L.
>>
>> ___
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge@dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] does your kdump work?

[lejeczek]

hi all

mine does not, I have a few R815 none is good, and I've 
tampered with it in many ways, cannot get it to work.
With IOMMU disabled still no good gee.

best,
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] NetXtreme II BCM5709 - DSU want to dowgrade - ok?

[lejeczek]

could somebody @Dell confirm this please?

On 19/12/16 11:41, lejeczek wrote:
> hi Dell tech
>
> looking for a confirmation that this is really meant:
>
> |---Dell System Updates---|
> [ ] represents 'not selected'
> [*] represents 'selected'
> [-] represents 'Component already at repository version 
> (can be selected only if -e option is used)'
> Choose:  q - Quit without update, c to Commit,  - 
> To Select/Deselect, a - Select All, n - Select None
>
> [-]1 PERC H700 Integrated Controller 0 Firmware
>  Current Version : 12.10.7-0001 same as : 12.10.7-0001
>
> [-]2 PERC H800 Adapter Controller 1 Firmware
>  Current Version : 12.10.7-0001 same as : 12.10.7-0001
>
> [ ]3 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (p4p2)
>  Current Version : 08.07.25 Downgrade to : 7.12.19
>
> [ ]4 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (p4p1)
>  Current Version : 08.07.25 Downgrade to : 7.12.19
>
> [ ]5 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (em3)
>  Current Version : 08.07.25 Downgrade to : 7.12.19
>
> [ ]6 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (p4p3)
>  Current Version : 08.07.25 Downgrade to : 7.12.19
> ...
> ..
>
> I have a strange problem with my R815s where dis-plugging 
> and re-plugging network leads, or even disabling an 
> enabling NICs from OS would/could render "PCI falal 
> error... stot 5" or similar, off top of my head.
> I wonder if this downgrade has some root cause?
>
> Also, would be great (like any another software does) if 
> DSU (or relevant cli tools) included something like 
> --changelog or something similar, so we could read any 
> important ReadME(s) from CLI.
>
> thanks Dell,
> L

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] NetXtreme II BCM5709 - DSU want to dowgrade - ok?

[lejeczek]

hi Dell tech

looking for a confirmation that this is really meant:

|---Dell System Updates---|
[ ] represents 'not selected'
[*] represents 'selected'
[-] represents 'Component already at repository version (can 
be selected only if -e option is used)'
Choose:  q - Quit without update, c to Commit,  - To 
Select/Deselect, a - Select All, n - Select None

[-]1 PERC H700 Integrated Controller 0 Firmware
  Current Version : 12.10.7-0001 same as : 12.10.7-0001

[-]2 PERC H800 Adapter Controller 1 Firmware
  Current Version : 12.10.7-0001 same as : 12.10.7-0001

[ ]3 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (p4p2)
  Current Version : 08.07.25 Downgrade to : 7.12.19

[ ]4 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (p4p1)
  Current Version : 08.07.25 Downgrade to : 7.12.19

[ ]5 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (em3)
  Current Version : 08.07.25 Downgrade to : 7.12.19

[ ]6 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (p4p3)
  Current Version : 08.07.25 Downgrade to : 7.12.19
...
..

I have a strange problem with my R815s where dis-plugging 
and re-plugging network leads, or even disabling an enabling 
NICs from OS would/could render "PCI falal error... stot 5" 
or similar, off top of my head.
I wonder if this downgrade has some root cause?

Also, would be great (like any another software does) if DSU 
(or relevant cli tools) included something like --changelog 
or something similar, so we could read any important 
ReadME(s) from CLI.

thanks Dell,
L

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] can omsa monitor windows?

[lejeczek]

hi everybody

I'll probably have to sacrifice one box to windows and I 
wonder if you know (long list of different stuff made lost a 
bit) which package(s) should be installed on a windows box 
so OMSA could monitor that windows? (if it is possible at all?)

many thanks,
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] raid incompatibility H310 <=> H700

[lejeczek]

I have raid5 created by H700 but there seem to be a problem 
when I have it under H310.
VD is there and OS sees it but fsck and mount fail.

Any Dell representative or you guys could confirm H700 <=> 
H310 should work?
many thanks,
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] PERC H310 refuses to create raid?

[lejeczek]

On 22/11/16 14:12, Mark Dominik Buerkle wrote:
>
> Hi,
>
> "JBOD" reads to me as if the single drives are all visible 
> to the O/S as single drives.
>
> Ie. Your drives are "in use" and can't be assigned to a 
> virtual drive.
>
> Kind regards,
> Dominik
>
>
weird thing is that - I powered down the system, replaced 
H310 with H700 and it worked. There were PVs and an LVM LV 
on those JBODs but I removed them as first thing before gave 
perccli a try.
I'll see, maybe I'll get a chance to revert controllers, if 
then H310 still fails that would maybe mean firmware problem 
(although DSU says: the latest)


> Am 22.11.2016 um 13:03 schrieb lejeczek:
>> hi everyone
>>
>> I'm trying something simple:
>>
>> $ perccli /c0 add vd raid5 drives=32:0-5 pdcache=on
>>
>> and it spits back on me:
>>
>> Controller = 0
>> Status = Failure
>> Description = physical disk does not have appropriate attributes
>>
>> currently:
>> ..
>> PD LIST :
>> ===
>>
>> -
>> EID:Slt DID State DG Size Intf Med SED PI SeSz
>> Model  Sp
>> -
>> 32:0  0 JBOD  -  1.818 TB SATA HDD N   N  512B
>> ST2000LM003 HN-M201RAD U
>> 32:1  1 JBOD  -  1.818 TB SATA HDD N   N  512B
>> ST2000LM003 HN-M201RAD U
>> 32:2  2 JBOD  -  1.818 TB SATA HDD N   N  512B
>> ST2000LM003 HN-M201RAD U
>> 32:3  3 JBOD  -  1.818 TB SATA HDD N   N  512B
>> ST2000LM003 HN-M201RAD U
>> 32:4  4 JBOD  -  1.818 TB SATA HDD N   N  512B
>> ST2000LM003 HN-M201RAD U
>> 32:5  5 JBOD  -  1.818 TB SATA HDD N   N  512B
>> ST2000LM003 HN-M201RAD U
>>
>> would you know why?
>> many thanks,
>> L.
>>
>> ___
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge@dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
> -- 
> *Mark Dominik Bürkle*
> *Linux Systemadministrator*
> 
> Gameforge 4D GmbH
> Albert-Nestler-Straße 8
> 76131 Karlsruhe
> Germany
>
> *Registered Office | Sitz der Gesellschaft* Karlsruhe
> *Register Court | Registergericht* AG Mannheim, HRB 718029
> *VAT ID | USt-IdNr.* DE 814330106
>
> *Managing Directors | Geschäftsführer* Timothy Campbell, 
> Alexander Rösner
>
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] PERC H310 refuses to create raid?

[lejeczek]

hi everyone

I'm trying something simple:

$ perccli /c0 add vd raid5 drives=32:0-5 pdcache=on

and it spits back on me:

Controller = 0
Status = Failure
Description = physical disk does not have appropriate attributes

currently:
..
PD LIST :
===

-
EID:Slt DID State DG Size Intf Med SED PI SeSz 
Model  Sp
-
32:0  0 JBOD  -  1.818 TB SATA HDD N   N  512B 
ST2000LM003 HN-M201RAD U
32:1  1 JBOD  -  1.818 TB SATA HDD N   N  512B 
ST2000LM003 HN-M201RAD U
32:2  2 JBOD  -  1.818 TB SATA HDD N   N  512B 
ST2000LM003 HN-M201RAD U
32:3  3 JBOD  -  1.818 TB SATA HDD N   N  512B 
ST2000LM003 HN-M201RAD U
32:4  4 JBOD  -  1.818 TB SATA HDD N   N  512B 
ST2000LM003 HN-M201RAD U
32:5  5 JBOD  -  1.818 TB SATA HDD N   N  512B 
ST2000LM003 HN-M201RAD U

would you know why?
many thanks,
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] @ Dell maintainers

[lejeczek]

@Dell team
can you gents please include perccli tools in the repository?

many thanks,
L

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] accees iDrac's console on LAN from the Internet

[lejeczek]

it does work 100%.

I a long list of rules in that box's firewall there was 
already something for those ports. My bad I did miss those.


On 25/09/16 12:51, Patrick Boutilier wrote:
> On 09/25/2016 06:02 AM, lejeczek wrote:
>>
>>
>> On 23/09/16 00:13, Patrick Boutilier wrote:
>>> On 09/22/2016 04:12 PM, lejeczek wrote:
>>>> is this possible?
>>>
>>> Yes.
>>>
>>>>
>>>> forwarding 5900 port both for upd & tcp does not do the
>>>> trick.
>>>>
>>>
>>> Only need TCP. Ports 5900, and 5901.
>>>
>>>
>> I now have both ports, also just in case both TCP & udp - 
>> it does not work.
>> I take pick with nmap - says port is closed, so opened, 
>> no filtering,
>> good, but nothing is listening.
>> I deployed these rule:
>>
>> -A PREROUTING -s remote.public.IP.x -d 
>> firewall.public.IP.x -i em3 -p
>> TCP -m multiport --dports 5900 -j DNAT --to-destination 
>> 192.168.2.30:5900
>>
>> for both ports & protocols. I also, naturally, forward 
>> 443 for https.
>> I even check if nating on my remote.public.IP might help, 
>> similar rules,
>> but it did not.
>
>
> Is it being blocked in FORWARD ? You might also need 
> something like:
>
>
> -I FORWARD -p tcp -m multiport -s remote.public.IP.x -d 
> 192.168.2.30 --dports 443,5900,5901 -j ACCEPT
>
>
> If that still doesn't work tcpdump the traffic when you 
> try to connect and see if traffic is travelling both ways.
>
>
>
>
>>
>>>
>>>> would you know what NAT has to take care of in order to 
>>>> get
>>>> me to my iDrac6?
>>>>
>>>> many thanks
>>>>
>>>> ___
>>>> Linux-PowerEdge mailing list
>>>> Linux-PowerEdge@dell.com
>>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>>>
>>>
>>>
>>>
>>> ___
>>> Linux-PowerEdge mailing list
>>> Linux-PowerEdge@dell.com
>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] accees iDrac's console on LAN from the Internet

[lejeczek]

On 23/09/16 00:13, Patrick Boutilier wrote:
> On 09/22/2016 04:12 PM, lejeczek wrote:
>> is this possible?
>
> Yes.
>
>>
>> forwarding 5900 port both for upd & tcp does not do the
>> trick.
>>
>
> Only need TCP. Ports 5900, and 5901.
>
>
I now have both ports, also just in case both TCP & udp - it 
does not work.
I take pick with nmap - says port is closed, so opened, no 
filtering, good, but nothing is listening.
I deployed these rule:

-A PREROUTING -s remote.public.IP.x -d firewall.public.IP.x 
-i em3 -p TCP -m multiport --dports 5900 -j DNAT 
--to-destination 192.168.2.30:5900

for both ports & protocols. I also, naturally, forward 443 
for https.
I even check if nating on my remote.public.IP might help, 
similar rules, but it did not.

>
>> would you know what NAT has to take care of in order to get
>> me to my iDrac6?
>>
>> many thanks
>>
>> ___
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge@dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>
>
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] accees iDrac's console on LAN from the Internet

[lejeczek]

is this possible?

forwarding 5900 port both for upd & tcp does not do the trick.

would you know what NAT has to take care of in order to get 
me to my iDrac6?

many thanks

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] centos/rhel and elrepo 4.7.x kernels = massive problem(s) on AMD PowerEdges

[lejeczek]

hi fellow users-admins

I wonder if you by any chance use AMD powered PowerEdges and 
might have also tried 4.7.x kernels (which I think are going 
to be in next RHEL releases) ?
And if you do, then I wonder whether you've come across any 
problems?

I with elrepo's 4.7.x kernel(s) hit a big problem, well - 
big inasmuch as when/if this is not fixed before officially 
this kernel gets into new OSes.
I get random hmm... hard/cold reboots! But even bigger issue 
is that server(s) hangs/freezes and does not start.
I find my PE 815 with "System booting" on front panel and 
nothing, no response, no keyboard no screen. Only power off 
and start helps.

This seems really major and would be good if Dell tech team 
look into it too.

regards
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] iDracs - ready for dot 1x auth/security ?

[lejeczek]

hi users,

are they?

many thanks,

L

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] equallogic ? anybody? and HIT...

[lejeczek]

how to get HIT for Linux (or any OS) when you cannot get 
support contract?
would you know?

I understand for firmware(other core soft) Dell-Eql need us 
to pay support costs - it's the nature of continues software 
devel - but should tools like HIT be prohibited?

I cannot get any updates for my Equalllogic been declared 
EOL by Dell - an absurd situation - even though I see new 
updates do mention those EOL models.

regards

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] test email - ignore

[lejeczek]

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] update iDrac from within gui?

[lejeczek]

hi everybody

which package do I need to update iDrac using its own GUI?

many thanks
L.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] EXT : ups... repo has gone

[lejeczek]

ok, I meant to say... has gone haywire, it's the repodata 
that got them out of sync, don't mind what rpm packages are 
there physically, yum does not see them other versions.
should be quick fix for chaps @OMSA.

On 23/03/16 17:10, Gottloeb, Jeff (ES & CSO) wrote:
> Here is Dell's reply on the issue:
>
> "I've spoken with our folks over in systems management that own OpenManage 
> and they are saying they are not sure how it was added to DSU, it's 
> technically not released yet. My recommendation is to uninstall 8.3 and 
> downgrade to 8.2 just to be on the safe side. I'm not sure why it was 
> removed."
>
> Jeff Gottloeb
> Northrop Grumman IT Solutions
> 310 812 4395
>
>
> -Original Message-
> From: linux-poweredge-boun...@dell.com 
> [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Gottloeb, Jeff (ES & 
> CSO)
> Sent: Wednesday, March 23, 2016 9:34 AM
> To: lejeczek; linux-powere...@lists.us.dell.com
> Subject: Re: [Linux-PowerEdge] EXT : ups... repo has gone
>
> It looks like all of the v8.3.0 release has been removed and the repository 
> only has v8.2.0 now for at least RHEL6 and RHEL7.
>
> Jeff Gottloeb
> Northrop Grumman IT Solutions
> 310 812 4395
>
> -Original Message-
> From: linux-poweredge-boun...@dell.com 
> [mailto:linux-poweredge-boun...@dell.com] On Behalf Of lejeczek
> Sent: Wednesday, March 23, 2016 8:15 AM
> To: linux-powere...@lists.us.dell.com
> Subject: EXT :[Linux-PowerEdge] ups... repo has gone
>
> is it just us?
>
> srvadmin-realssd-8.3.0-1908.90 FAILED
> http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-realssd-8.3.0-1908.9058.el7.x86_64.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> srvadmin-smcommon-8.3.0-1908.9 FAILED
> http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-smcommon-8.3.0-1908.9058.el7.x86_64.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> srvadmin-storage-8.3.0-1908.90 FAILED
> http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-storage-8.3.0-1908.9058.el7.x86_64.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> srvadmin-storage-cli-8.3.0-190 FAILED
> http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-storage-cli-8.3.0-1908.9058.el7.x86_64.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> srvadmin-storelib-8.3.0-1908.9 FAILED
> http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-storelib-8.3.0-1908.9058.el7.x86_64.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
> srvadmin-xmlsup-8.3.0-1908.905 FAILED
> http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-xmlsup-8.3.0-1908.9058.el7.x86_64.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> Trying other mirror.
>
> regards
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] ups... repo has gone

[lejeczek]

is it just us?

srvadmin-realssd-8.3.0-1908.90 FAILED
http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-realssd-8.3.0-1908.9058.el7.x86_64.rpm:
 
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
srvadmin-smcommon-8.3.0-1908.9 FAILED
http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-smcommon-8.3.0-1908.9058.el7.x86_64.rpm:
 
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
srvadmin-storage-8.3.0-1908.90 FAILED
http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-storage-8.3.0-1908.9058.el7.x86_64.rpm:
 
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
srvadmin-storage-cli-8.3.0-190 FAILED
http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-storage-cli-8.3.0-1908.9058.el7.x86_64.rpm:
 
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
srvadmin-storelib-8.3.0-1908.9 FAILED
http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-storelib-8.3.0-1908.9058.el7.x86_64.rpm:
 
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
srvadmin-xmlsup-8.3.0-1908.905 FAILED
http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL7_64/srvadmin/srvadmin-xmlsup-8.3.0-1908.9058.el7.x86_64.rpm:
 
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.

regards

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] HW watchdog on R815

[lejeczek]

hi everybody,

I'd like to ask how do you use, set up, watchdog on these boxes?
Linux does not seem to create /dev/watchdog on these.
Do you rather prefer OMSA(give it provides these functions) 
over OS'es watchdog?
I looked up in the docs but only bit related to my question 
was a mention about settings in the BIOS.

many thanks
P.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] racadm - idracadm: error while loading shared libraries...

[lejeczek]

$ racadm -h
/opt/dell/srvadmin/bin/idracadm: error while loading shared 
libraries: libargtable2.so.0: cannot open shared object 
file: No such file or directory

is Dell forgetting to put it into libraries paths config? 
(with help of scriptlets)
or should be pulling automatically during install - argtable 
- which is already in epel repo!

regards

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge