[Linux-PowerEdge] Plans for RHEL 9?

2022-08-09 Thread Chris Adams
Is there any update on Dell's plans for RHEL 9 for the Linux software
and repos?
-- 
Chris Adams 

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


Re: [Linux-PowerEdge] racadm command to reset BIOS to factory defaults?

2020-12-01 Thread Chris Adams


[EXTERNAL EMAIL] 

Once upon a time, Hamelin, Patrice (SSC/SPC)  said:
> I think this is going to do the job, never tested myself, let me know if it 
> solves it
> 
> racadm systemerase ,,

Yes, it looks like "racadm systemerase bios" did it - thanks.
-- 
Chris Adams 

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


[Linux-PowerEdge] racadm command to reset BIOS to factory defaults?

2020-11-25 Thread Chris Adams


[EXTERNAL EMAIL] 

I am trying to reset all the BIOS settings to factory default on a
system - is there a way to do that remotely with racadm?  I see how to
reset the iDRAC settings, but haven't found a way to reset the BIOS too.
-- 
Chris Adams 

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


Re: [Linux-PowerEdge] Key retrieval failure

2020-07-22 Thread Chris Adams


[EXTERNAL EMAIL] 

Once upon a time, Adam Goldman  said:
> When attempting to follow the instructions on an ubuntu 18.04 server today, I 
> was unable to pull the gpg key from pool.sks-keyservers.net using the 
> commands as written.
> 
>  sudo gpg --keyserver pool.sks-keyservers.net --recv-key 1285491434D8786F

Hmm, I just get the keys straight from Dell - that's available at:

https://linux.dell.com/repo/pgp_pubkeys/0x1285491434D8786F.asc

-- 
Chris Adams 

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


Re: [Linux-PowerEdge] BIOS legacy boot with BOSS controller card

2020-06-01 Thread Chris Adams


[EXTERNAL EMAIL] 

Once upon a time, mohammad kashif  said:
> Thanks for kind offer. Can you please let me know whether you use
> bootnetx64.efi
> or grubx64.efi for UEFI boot?  Also what is your dhcp config option to
> differentiate between UEFI and legacy boot mode for 'filename' .

I'm not Raoul, but here's how I PXE boot for BIOS and UEFI.

First, I used dnsmasq for DHCP, so obviously, adapt for other servers.
I have this in my config (replace tftp.example.com with your TFTP server
and 192.168.1.2 with its IP address - haven't set PXE up for IPv6 yet):

   # EFI boot will set ARCH option (93)
   dhcp-match=set:efi32,option:client-arch,6
   dhcp-match=set:efi64,option:client-arch,7
   tag-if=set:bios,tag:!efi32,tag:!efi64

   # PXE boot
   dhcp-boot=tag:efi64,shimx64.efi,tftp.example.com,192.168.1.2
   dhcp-boot=tag:bios,bios/lpxelinux.0,tftp.example.com,192.168.1.2
   dhcp-option-force=lan,209,pxelinux.conf

Then in my TFTP root, I have:

   shimx64.efi   # from shim-x64 RPM: /boot/efi/EFI/fedora/shimx64.efi
   grubx64.efi   # from grub2-efi-x64 RPM: /boot/efi/EFI/fedora/grubx64.efi
   EFI/fedora# from grub2-efi-x64-modules RPM: /usr/lib/grub/fedora
   bios/ldlinux.c32  # from syslinux-tftpboot RPM: /tftpboot/ldlinux.c32
   bios/libutil.c32  # from syslinux-tftpboot RPM: /tftpboot/libutil.c32
   bios/lpxelinux.0  # from syslinux-tftpboot RPM: /tftpboot/lpxelinux.0
   bios/menu.c32 # from syslinux-tftpboot RPM: /tftpboot/menu.c32

   # local configs
   grub.cfg
  source (http,tftp.example.com)/local/grub2.cgi
   bios/pxelinux.conf
  ui menu.c32 http://tftp.example.com/local/pxe.cgi


I load the rest over HTTP from the same server; so much faster and more
reliable than TFTP, and the configs can be auto-generated this way.  The
referenced CGIs generate configs like:

grub2.cgi:

terminal_input console
loadfont /12x26.pf2
insmod gfxterm
set gfxmode=auto
terminal_output gfxterm

set timeout=-1

menuentry 'Install Fedora release 32 x86_64' {
set root=(http,tftp.example.com)
linuxefi 
/pub/fedora/linux/releases/32/Server/x86_64/os/images/pxeboot/vmlinuz 
inst.root=http://tftp.example.com/pub/fedora/linux/releases/32/Server/x86_64/os/
 
inst.stage2=http://tftp.example.com/pub/fedora/linux/releases/32/Server/x86_64/os/
 repo=http://tftp.example.com/pub/fedora/linux/releases/32/Everything/x86_64/os 
quiet BOOTIF=$net_default_mac
initrdefi 
/pub/fedora/linux/releases/32/Server/x86_64/os/images/pxeboot/initrd.img
}


pxe.cgi:

timeout 100

menu title Select a network boot option
menu rows 15
menu tabmsgrow -5
menu cmdlinerow -3
menu timeoutrow -2
menu helpmsgrow -4

label f32_x86_64
menu label Fedora release 32 x86_64
text help
Hit [TAB] and add " rescue" for rescue mode
endtext
kernel 
http://tftp.example.com/pub/fedora/linux/releases/32/Server/x86_64/os/images/pxeboot/vmlinuz
initrd 
http://tftp.example.com/pub/fedora/linux/releases/32/Server/x86_64/os/images/pxeboot/initrd.img
append 
inst.root=http://tftp.example.com/pub/fedora/linux/releases/32/Server/x86_64/os/
 
inst.stage2=http://tftp.example.com/pub/fedora/linux/releases/32/Server/x86_64/os/
 repo=http://tftp.example.com/pub/fedora/linux/releases/32/Everything/x86_64/os
ipappend 2
####

-- 
Chris Adams 

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


Re: [Linux-PowerEdge] RHEL 8.x dell-system-update RPM should include libssh2 RPM as a dependency...

2020-02-21 Thread Chris Adams

[EXTERNAL EMAIL] 

libssh is a completely different library from libssh2, so that's not
going to work.

libssh2 has been deprecated in RHEL 8.1 in favor of libssh - libssh2
_may_ get added to EPEL, but it has not so far.  Dell should probably
look at either updating their code to use the alternate, or they could
include libssh2 in their RHEL 8 repo.

Once upon a time, Patrick Boutilier  said:
> 
> [EXTERNAL EMAIL]
> 
> Or just make a symbolic link.
> 
> 
> 
> cd /usr/lib64
> 
> ln -s libssh.so.4 libssh2.so.1
> 
> 
> On 2/21/20 1:05 PM, Aram Mirzadeh wrote:
> >I downloaded libssh from github and compiled it.  I just needed
> >the regular "Development Tools" group install.
> >
> >On Fri, Feb 21, 2020 at 11:47 AM  ><mailto:spike.wh...@dell.com>> wrote:
> >
> >All,
> >
> >__ __
> >
> >On RHEL8.1, when installing dell-system-update RPM as per usual
> >instructions, dsu fails on the command line as so:
> >
> >__ __
> >
> >[root@austgcore17 ~]# dsu --help
> >
> >dsu: error while loading shared libraries: libssh2.so.1: cannot open
> >shared object file: No such file or directory
> >
> >__ __
> >
> >It’s trivial to fix, just install the libssh2 RPM:
> >
> >__ __
> >
> >[root@austgcore17 ~]# yum -y install libssh2
> >
> >…
> >
> >[root@austgcore17 ~]# dsu --help
> >
> >__ __
> >
> >Usage: dsu [OPTION]...
> >
> >     Options:
> >
> >     …
> >
> >__ __
> >
> >However, for completeness the dell-system-update RPM for RHEL8
> >should add libssh2 RPM as an RPM dependency.
> >
> >__ __
> >
> >Spike
> >
> >___
> >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
> >

> begin:vcard
> fn:Patrick Boutilier
> n:Boutilier;Patrick
> org:;Nova Scotia Department of Education
> adr:;;2021 Brunswick Street;Halifax;NS;B3K 2Y5;Canada
> email;internet:bouti...@ednet.ns.ca
> title:WAN Communications Specialist
> tel;work:902-424-6800
> tel;fax:902-424-0874
> version:2.1
> end:vcard
> 

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


-- 
Chris Adams 

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


Re: [Linux-PowerEdge] Missing PGP files for dsu 1.7.0

2019-05-21 Thread Chris Adams


[EXTERNAL EMAIL] 

Once upon a time, Chris Adams  said:
> Right.  The correct way is to distribute the key, not expect it to be
> installed manually after a "yum update" (I expect an update to work
> automatically).

So apparently, the Dell keys need to be imported in GPG as well as RPM
for DSU, and the bootstrap.cgi hack does that.  Auto-importing keys into
GPG is bad (especially without notice); if DSU needs to use GPG to
check, then it should have a private GPG keyring, not use root's.

-- 
Chris Adams 

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


Re: [Linux-PowerEdge] Missing PGP files for dsu 1.7.0

2019-05-21 Thread Chris Adams


[EXTERNAL EMAIL] 

Once upon a time, Gregory Matthews  said:
> On 20/05/2019 11:46, Ben Argyle wrote:
> >I've been informed that I needed to rerun
> >
> >curl -s https://linux.dell.com/repo/hardware/dsu/bootstrap.cgi | bash
> 
> but this will also write a repo file which breaks things if you
> mirror locally. Also, it might not be clear - you need to import the
> keys on EVERY server so this doesn't exactly scale.

Right.  The correct way is to distribute the key, not expect it to be
installed manually after a "yum update" (I expect an update to work
automatically).

> and am I the only one who hates the idea of running a curl fetch and
> piping it directly to a shell AS ROOT!? This is not just bad
> practice, its a sackable offence.

Yeah, this is a bad setup.  Distribute an RPM with the repo files and
keys, so it can be installed with regular automated tools.  Right now, I
just have the repos created manually with Ansible tasks.  I didn't
realize the key had changed (hadn't updated Dell stuff on a server yet).

Other enterprise companies "get" this - Chrome, Slack, and Teamviewer
for example (just things I have installed on my desktop) each have a
repo file owned by an RPM that can be updated, including keys as
necessary.

-- 
Chris Adams 

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


[Linux-PowerEdge] OMSA 9.1 and SAS 6/iR

2018-11-06 Thread Chris Adams


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


When OMSA 9.1 came out for Linux (around the start of 2018), the SAS
6/iR cards stopped showing up in OMSA (still work fine with Linux
kernel, just can't be managed), like:

# omreport storage controller
No controllers found

After a lot of back and forth, IIRC someone from Dell said this would be
fixed in an October release (which was already way too long of a wait),
but October has come and gone and there's still no update.

Can we get an update from Dell on this?
-- 
Chris Adams 

___
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

2018-05-10 Thread Chris Adams
Once upon a time, R S <rene.shus...@bcsemail.org> said:
> We shouldn't be asked to downgrade our Java version, nor mess with the
> security setting of JDK/JRE/IcedT. If this really is java-related then it's
> up to Dell to fix this and restore functionality of the iDRAC.

I'm curious; if a Java upgrade broke an application, why do you blame
the application?  Java upgrades have been known to introduce bugs
before; it is quite possible the problem is on the Java end, not the
application end.

If Microsoft sends out a Windows update and your Logitech mouse stops
working, do you blame Logitech?  No, it is probably a Microsoft bug.

-- 
Chris Adams <li...@cmadams.net>

___
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

2018-05-10 Thread Chris Adams
Once upon a time, Peter Holl <peter.h...@pnsensor.de> said:
> after updating from Java 8/162 to 8/171 I can't connect to the
> console using the Virutual Console Client (i.e, by opening the
> downloaded viewer.jnlp).

I just tried an R610 with DRAC 2.90 from Fedora Linux with OpenJDK
1.8.0.171 and IcedTea-Web 1.7.1, and it worked for me.

IIRC there is some Java applet cache somewhere that can get screwed up,
keep old versions, or something like that - might dig around to see if
clearing that helps.  I seem to remember having a similar problem to
what you describe after a Fedora update, and cleaning that up helped.

-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] no storage controllers detected

2018-04-24 Thread Chris Adams
Once upon a time, vivek...@dell.com <vivek...@dell.com> said:
> Could you see if the latest FW are flashed. Believe RHEL 6.9 supports native 
> drivers for these storage controllers.

It is not RHEL that doesn't find the controller, but Dell's OpenManage.
I have a server with the same condition; "omreport storage controller"
just says "No controllers found" on a system where an older version of
omreport worked fine.

In my case, it's an R410, with the same SAS 6/iR, running CentOS 7 (with
the latest firmware).

This used to work just fine, but the last Dell OpenManage release broke
it.
-- 
Chris Adams <li...@cmadams.net>

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


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

2018-02-18 Thread Chris Adams
Once upon a time, Stefan M. Radman <s...@kmi.com> said:
> while it is clear that the ability to downgrade is essential, DSU's attempt 
> in this case is totally unrelated to Meltdown and Spectre as both BIOS 
> versions long precede the patches.

I have a R410 (I bought used for personal use) where DSU has wanted to
downgrade the LifeCycle Controller from 1.7.5.4 to 1.6.5.12 for a long
time now.  I have no idea why; 1.7.5.4 is the current version on the
website and was released almost 2 years ago.

Oddly, DSU also wants to "upgrade" the 10gig NIC firmware.  The NIC is
not even a Dell (just uses the same Intel 82599 chip); it wants to go
from 0.0.0 to 16.5.20.

-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] PXE boot in UEFI mode

2018-02-13 Thread Chris Adams
Once upon a time, Kilian Cavalotti <kilian.cavalotti.w...@gmail.com> said:
> Hi!
> 
> I'm trying to deploy PE servers (Rx30s and C6320s) via PXE in UEFI
> boot mode, without success.
> 
> The servers PXE-boot just fine when configured in BIOS boot mode, but
> switching to UEFI apparently makes the initial DHCP request timeout,
> and generate a PXE-E18 Server Response Timeout error.

I haven't tried UEFI PXE booting a Dell server, but I have done it with
some random (non-Dell) other devices at home: notebooks, a desktop, and
an Intel NUC.  Everything worked fine except the NUC, and IIRC it was
similar behavior to what you describe (but it has been a little bit so I
can't remember now).

It's possible that the same core Intel code is in the NUC and the Dells
and has the same problem.

It's funny that the 2017 Intel NUC, with the latest firmware, wouldn't
work, seeing as they wrote the standard (waiting to bug a friend about
it next time I see him, since I think he wrote a chapter :) ).

-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] microcode_ctl and Spectre/Meltdown

2018-01-05 Thread Chris Adams
Once upon a time, Troels Arvin <tro...@arvin.dk> said:
> Red Hat and others have released a bunch of updated software which
> provides workarounds for the Spectre/Meltdown trouble. I have
> updated some Poweredge R720s and an HPE ProLiant BL460c Gen9 server.
> On the Dell servers, the Spectre/Meltdown work-arounds are not
> enabled after boot, wereas on the HPE server, the workaround is
> enabled. All serves have the latest available firmware/BIOSes.

What's the CPU in each type of server?  I think Intel is either not
updating microcode for older CPUs (not sure where they're drawing the
line), or at least has not released an update yet.

-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] EqualLogic, Linux, and latency

2017-04-14 Thread Chris Adams
Once upon a time, Max Vernimmen <m.vernim...@comparegroup.eu> said:
> You mention that you don't see any issues with the switches. Are you tracking 
> the amount of frames that get dropped by your switches? Any other errors on 
> the switch ports? How's the link utilisation?

Yes, I'm tracking that, and there are no drops at the switches (or the
Linux servers' end).

The link utilization is pretty low.  The server 1G ports are typically
only running about 5-20 Mbps on each link (a spike is 50-100 Mbps on
each, and those are usually only on one server at a time, hosting a
busier VM).  The SAN 10G ports are running about 30-50 Mbps (spiking to
maybe 200 Mbps).  My monitoring system is pulling stats from the switch
every 60 seconds.

I could reproduce some of the latency on a server in maintenance mode,
where my script was the only thing touching the disk (so no other
storage traffic from that server).

> When you get high latency, does it affect only that node or all at the same 
> time? In that case, do you have pause frames on and are they being triggered? 
> Is there a spike in traffic at that moment (that second)?

It seems to affect multiple nodes at the same time, although not always
(or at least not always to the same extent).  Usually, the oVirt
warnings about high latency are only on one node at any given time (but
there has been a time or two where it has been two nodes).

Looking at pause frame stats on the switch, they're essentially zero
(0-100 pause frames received on some server ports with a switch uptime
of 5 months).  No pause frames on the SAN ports, and no pause frames
transmitted on any port from the switch.

> Is there any packetloss between your hosts and your eql(s) ?

Not that I see.

> Those were just some thoughts that popped into my head. I hope they can help 
> you find the cause.

Thanks.  I'm reasonably sure it isn't a network issue, but I hadn't
checked all of the above.
-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] EqualLogic, Linux, and latency

2017-04-13 Thread Chris Adams
I hadn't thought of trying that... it does look like I still see
occasional high read latency (100+ ms); I haven't seen the 1+ second
(but that's sporadic anyway).  Interestingly, it seems to only get
higher latency on the logical volumes; just reading the first block of
the iSCSI device (e.g. /dev/sdf) seems to consistently be under 1ms.

Just to explain the setup (for those not familiar with oVirt): when you
create a storage domain on an iSCSI device, oVirt sets up a Linux volume
group on it, and then creates several internal-use logical volumes
(including the "metadata" LV that I'm reading).  After that, each
virtual disk gets an LV create as well.

The network _shouldn't_ be a problem (famous last words); the servers
each have two 1G ports to a pair of N3000 switches for the storage
network, and the SAN has 10G ports (but each 10G port is under 100
megabits per second most of the time).  There's also an FS7600 with 1G
ports talking to the same SAN.

I'm going to install SAN HQ to get a better look at the SAN-side
performance (but I've got to order a copy of Windows for that, bleh!).


Once upon a time, rob.schnitzl...@dell.com <rob.schnitzl...@dell.com> said:
> Dell - Internal Use - Confidential  
> 
> If you disable multipathd and test against a single path, do you see the same 
> latency? 
> 
> I'm wondering if there is a Networking issue at play.
> 
> -Original Message-
> From: linux-poweredge-bounces-Lists On Behalf Of Chris Adams
> Sent: Thursday, April 13, 2017 1:24 PM
> To: linux-poweredge-Lists <linux-powere...@lists.us.dell.com>
> Subject: [Linux-PowerEdge] EqualLogic, Linux, and latency
> 
> I have a stack of PowerEdge servers, running CentOS 7 and oVirt 
> (virtualization environment), using an EqualLogic PS6610 for VM storage.
> I'm using the regular Linux multipath daemon, not the Dell kit, because oVirt 
> manages the multipathing (and doesn't handle the Dell kit).
> 
> I am periodically seeing high latency from the SAN, even from a host not 
> running any VMs.  I see 100+ ms reads, and sometimes even multi-second reads 
> (to read a single 4K block).  oVirt logs warnings about this; I wrote a 
> simple perl script that duplicates what oVirt does (open a metadata logical 
> volume block device with O_DIRECT, read a 4K block, and close it), and I see 
> the same thing.
> 
> I've got iscsid and multipathd configured per the recommended values, and I'm 
> not seeing any issues on Linux or at the switches (dedicated network for 
> iSCSI); it would seem to be something on the SAN itself.
> The SAN isn't reporting anything though, so I'm not sure what to look at.
> 
> Any suggestions?
> 
> --
> Chris Adams <li...@cmadams.net>
> 
> _______
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge



-- 
Chris Adams <li...@cmadams.net>

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


[Linux-PowerEdge] EqualLogic, Linux, and latency

2017-04-13 Thread Chris Adams
I have a stack of PowerEdge servers, running CentOS 7 and oVirt
(virtualization environment), using an EqualLogic PS6610 for VM storage.
I'm using the regular Linux multipath daemon, not the Dell kit, because
oVirt manages the multipathing (and doesn't handle the Dell kit).

I am periodically seeing high latency from the SAN, even from a host not
running any VMs.  I see 100+ ms reads, and sometimes even multi-second
reads (to read a single 4K block).  oVirt logs warnings about this; I
wrote a simple perl script that duplicates what oVirt does (open a
metadata logical volume block device with O_DIRECT, read a 4K block, and
close it), and I see the same thing.

I've got iscsid and multipathd configured per the recommended values,
and I'm not seeing any issues on Linux or at the switches (dedicated
network for iSCSI); it would seem to be something on the SAN itself.
The SAN isn't reporting anything though, so I'm not sure what to look
at.

Any suggestions?

-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] dell-system-update package 1.4.0-17.02.00

2017-04-03 Thread Chris Adams
Once upon a time, Paul Raines <rai...@nmr.mgh.harvard.edu> said:
> I disagree -- as long as there is a demonstrated need for the newer
> library and Dell's reply earlier implied there was - though I find
> it a bit hard to believe.

We're talking about libz.so.1 - that hasn't changed ABI in many a year.
The only library changes have been security and bug updates.  The other
libraries _could_ have newer stuff, but they're the same soname, so it
is doubtful.
-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] dell-system-update package 1.4.0-17.02.00

2017-04-03 Thread Chris Adams
Once upon a time, Kilian Cavalotti <kilian.cavalotti.w...@gmail.com> said:
> Due to all the issues that have been reported on this very mailing
> list for the last year at least, we'll be uninstalling DSU and OMSA
> from all our production systems starting today. We can't risk
> system-wide breakages to happen unexpectedly like this.

Less critical, but there's also a libxerces-c-3.1.so in there as well,
replacing the system-provided library.

Basically, if Dell doesn't understand why replacing system-provided
libraries globally is wrong (and doesn't fix it ASAP, not months down
the road), this software is uninstallable in their target market
(enterprise operating systems).

-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] iDrac 8 Network security range

2017-03-15 Thread Chris Adams
Once upon a time, Stephen Berg (Contractor) <stephen.berg@nrlssc.navy.mil> 
said:
> This has been an issue for at least 4 generations of iDrac's.  If you 
> need to lock down access to the iDrac you can only define one IP range 
> and netmask.  It's really limiting and seems to be implemented so simply 
> that it's almost unusable.

Yeah, another vendor's equivalent can have up to 10 (IIRC) entries, with
ALLOW and DENY for each.  Much more convenient...
-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] Unqualified SFP+ adapter detected

2017-02-15 Thread Chris Adams
Once upon a time, Michael Watters <watte...@watters.ws> said:
> I am setting up a Poweredge R720 server with a Broadcom BCM57810 10 Gbit
> NIC however the SFP adapters that we have appear to be incompatible.
> 
> > Warning: Unqualified SFP+ module detected, Port 0 from CISCO-TYCO part
> number 1-20553783-1
> 
> Is there an updated version of the bnx2x driver available for CentOS
> 7.3?  Would it be possible to update the kernel module to work with
> different SFP adapters?  I am willing to patch the kernel source if needed.

Does it actually not work, or does it just complain about it?  I know
lots of router/switch vendors will complain, but the optics still
actually work just fine.

I know the Intel ixgbe driver won't actually turn on unsupported SFPs by
default (which is annoying), but there's an option for the module to
turn them on, allow_unsupported_sfp (and then they work fine, including
"ethtool -m" to see DOM info).  I don't know if there's a similar option
for Broadcom.

Sigh, games vendors play with standard ports...
-- 
Chris Adams <li...@cmadams.net>

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


Re: [Linux-PowerEdge] 2nd CPU status is Unknown

2016-02-01 Thread Chris Adams
Once upon a time, Chris Lajoie <ch...@etriptrader.com> said:
> That had no effect. I also tried rebooting the server, which also had no 
> effect.
> I also opened up the iDRAC web interface and I do not see the 2nd CPU at all! 
> It reports as if I only have 1 CPU installed.
> Should I try to reseat the CPU in the socket? I'm at a loss here. While it's 
> working fine right now I wouldn't consider putting a server in production 
> like this.

Have you fully power-cycled it?  I wonder if the iDRAC just isn't
re-inventorying the hardware at some level.

I wouldn't think re-seating the CPU would have any effect; if the OS
sees it and uses it (without crashing or anything weird) it should be
fine.

-- 
Chris Adams <li...@cmadams.net>

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


[Linux-PowerEdge] A little OT: Dell EqualLogic FS series

2016-01-15 Thread Chris Adams
This is a little off-topic, but is anybody familiar with the EqualLogic
FS series NAS?  They do appear to run CentOS, so it has some relevance
here, right?

I got an FS7600 for a setup that needs NFS (to be connected to a
PS4100).  Out of the box, one controller had a bad hard drive (couldn't
mount root FS), so we got a replacement controller from Dell.  However,
the replacement controller has an older firmware rev.  Each of these
conditions keep me from creating the NAS cluster, because you have to
add in matched pairs.

I've been round and round will Dell support, trying to get a working
setup, but I'm not getting anywhere.  I'm trying to get that escalated
now (not a problem with the tech on my case, but he doesn't seem to be
getting good support from his level-2), but I'm just curious if anyone
else is familiar with the workings of the FS series and might have any
ideas (this is my first FS box).

-- 
Chris Adams <li...@cmadams.net>

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


Re: Consistent Network Device Naming for LOMs coming...

2010-11-15 Thread Chris Adams
Once upon a time, Sean Dilda s...@duke.edu said:
 I can't remember the last box I setup with non-onboard NICs.  As such, I 
 think naming the on-board NICs differently from PCI NICs is just going 
 to lead to needless confusion.

aolme too/aol

Under some OSes, ethernet device names vary depending on the driver and
such, but Linux has always named all wired ethernet devices ethX.
Some wireless get different names, but I can't remember running into any
wired devices being anything other than ethX.  It is rather late in the
game to change that.

-- 
Chris Adams cmad...@hiwaay.net
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq


Re: Consistent Network Device Naming for LOMs coming...

2010-11-15 Thread Chris Adams
Once upon a time, Matt Domsch matt_dom...@dell.com said:
 Folks, without kernel-side changes which have been rejected, changes
 that reserved the first N ethX names for on-board devices, we cannot
 simply swizzle the names within the ethX namespace using udev rules.
 I wish that weren't true.

Hmm, I thought the Fedora/RHEL initscripts had been renaming eth*
devices around for year; is that broken?

I guess to me, it would be better to spend time fixing the kernel
ordering to follow the motherboard, rather than spend time creating
tools to rename some NICs, make sure other tools can handle the new
names, etc.
-- 
Chris Adams cmad...@hiwaay.net
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq


Re: CentOS 5.5 - Deleted Partition

2010-10-30 Thread Chris Adams
Once upon a time, Brian McGrew br...@visionpro.com said:
 I guess it¹s too early to be up on a Saturday because I just made the
 biggest newbie blunder of my career.  I got my hands crossed, grabbed the
 wrong terminal and deleted /dev/sdb1 with fdisk from a mounted, production
 volume.
 
 This volume is still accessible and mounted through LVM
 (/dev/mapper/VolGroup00-LogVol00) and all the data is still accessible.
 Noting appears to be missing.
 
 But, if I do an fdisk ­l on /dev/sdb, I have no partitions listed.

The kernel won't re-read the partition table if there are open
partitions, so whatever you do, DON'T REBOOT (it'll be gone then).

Do you know the particulars of the old partition table?  If so, just
re-run fdisk and recreate the partition(s) to match.

If not, I'm not sure if there is a way to see what the running kernel
thinks the partition table looks like.
-- 
Chris Adams cmad...@hiwaay.net
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq


Re: Preventing I/O starvation on MD1000s triggered by a failed disk.

2010-08-23 Thread Chris Adams
Once upon a time, Bond Masuda bond.mas...@jlbond.com said:
 Do you know if you encountered a URE? I've been running into URE's on
 large RAID-5 arrays that use 500GB, 750GB, 1TB drives... basically,
 RAID-5 might survive a single disk failure, but the rebuild will kill it
 due to URE. In this situation, usually you can force online the disk
 that had the URE and still be able to read data in degraded state as
 long as you avoid the block that has the URE. If URE is the issue, then
 you should start considering RAID-6.

I assume you are talking about the case where one drive in a RAID-5
fails, and while rebuilding, a bad block is discovered on another drive
(which results in at least that block being unrecoverable, and possibly
turning the whole array offline, depending on the RAID controller).

Linux software RAID has a way to validate an array.  Newer RHEL and
Fedora (and others I expect) run this check weekly and report any
faults.  Is there a way to do the same thing on the hardware RAID
controllers (either internal cards or external arrays like EqualLogic)?

-- 
Chris Adams cmad...@hiwaay.net
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq