Hi, While using DSU on a Ubuntu based Operating System, DSU by default picks up the catalog file available at https://linux.dell.com/repo/hardware/ubuntu/catalog/ unless or until a custom catalog is supplied using option like --source-location.
Otherwise, rest of the DSU operations remain the same without any change. Please let us know if you have more queries. Regards, Sashi -----Original Message----- From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists Sent: Wednesday, February 28, 2018 4:30 AM To: linux-poweredge-Lists <[email protected]> Subject: Linux-PowerEdge Digest, Vol 165, Issue 16 Send Linux-PowerEdge mailing list submissions to [email protected] 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 [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-PowerEdge digest..." Today's Topics: 1. IPMI SOL problem on C2100 (Daniel Cantar?n) 2. ubuntu vs dsu (jsl6uy js16uy) 3. MegaCLI compatibility in StorCli (with added typos) ? ([email protected]) 4. Re: MegaCLI compatibility in StorCli (with added typos) ? (Stephen Dowdy) ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Feb 2018 20:42:51 +0000 From: Daniel Cantar?n <[email protected]> To: "[email protected]" <[email protected]> Subject: [Linux-PowerEdge] IPMI SOL problem on C2100 Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi all. I'm working with automation tools on some C2100 and C1100 servers. A few weeks ago, I was able to connect to one of my servers using Serial Over Lan with ipmi-console (from freeipmi), like this: $> ipmi-console -h IPADDRESS -u USER -P This started up a SOL connection, and this way I was able to automate some interactions with the BIOS settings. However, a few days later, the same script didn't work anymore. It just says "[SOL established]", and that's it: the SOL connection never shows (or send to the server) any feedback. I'm writting to this list in order to find what could possibly change that the SOL connection is not working anymore. Is there any BIOS setting I should check? I obviously checked for anything related to SOL and IPMI, but everything looks normal. IDK what else to check. Any pointer would be nice. Thanks in advance. Daniel. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20180227/20474826/attachment-0001.html> ------------------------------ Message: 2 Date: Tue, 27 Feb 2018 15:02:42 -0600 From: jsl6uy js16uy <[email protected]> To: "<[email protected]>" <[email protected]> Subject: [Linux-PowerEdge] ubuntu vs dsu Message-ID: <CAAGD8_RO3w1SiVTw=UdOCXraON=opu3lsxafvijzxwmybkf...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello all, hope all is well Going over the docs for using dsu on ubu, they point to leveraging the Catalog_Ubuntu.gz, and that's it. What do I do with that Catalog? < be nice :) > How would I have an ubuntu host leverage this file from here https://linux.dell.com/repo/hardware/dsu/ It is recommended that for updating Ubuntu systems that the Ubuntu catalog be used (Ubuntu Catalog <https://linux.dell.com/repo/hardware/ubuntu/catalog/>) and that link just goes to this Catalog.gz apologies work with ubu a bit haven't seen use of a catalog file in package mgmt -Release.pgp Packages.gz and a Content_arch.gz like Contents-amd64.gz Would very much like to use dsu with ubu thanks and best regards all -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20180227/4a62ae2f/attachment-0001.html> ------------------------------ Message: 3 Date: Tue, 27 Feb 2018 17:47:10 -0500 (EST) From: [email protected] To: "[email protected]" <[email protected]> Subject: [Linux-PowerEdge] MegaCLI compatibility in StorCli (with added typos) ? Message-ID: <alpine.LRH.2.21.1802271718170.6383@daltigoth.lasthome.solace.krynn> Content-Type: text/plain; format=flowed; charset=US-ASCII Hi, Has anyone noticed that storcli (version 1.23.02 tested) appears to support MegaCli's syntax? Does anyone know if this is here to stay? E.g: Instead of: /opt/MegaRAID/MegaCli/MegaCli64 -PDGetNum -a0 -NoLog You could just use: /opt/MegaRAID/storcli/storcli64 -PDGetNum -a0 -NoLog In fact, the syntax compatibility between the two programs seems quite extensive and I was able to adapt my megaclisas-status utility to drive storcli just by changing the path. Details at: https://github.com/ElCoyote27/hwraid/commit/b57a3d41d780336ad3fc0fa356fb789049b46bf4#diff-9ad7624e74695a8211213f4e55109526 There are a few caveats: storcli appears to be much more strict about which controllers it will accept. In my (limited) testing, I wasn't able to make storcli work with H710's and H730's on RHEL7. The user from Russia who tipped me off to this compability was using an LSI/Avago 9361-8i HBA, perhaps that's why it worked for him. (See: https://github.com/eLvErDe/hwraid/issues/85) Also, it seems that LSI added (at least) one typo when they backported into storcli: # /opt/MegaRAID/MegaCli/MegaCli64 -PDList -a0 -NoLog|egrep -i Drive.*pos.*tion|head -2 Drive's position: DiskGroup: 0, Span: 0, Arm: 0 Drive's position: DiskGroup: 0, Span: 0, Arm: 1 While on storcli it says the following: # /opt/MegaRAID/storcli/storcli64 -PDList -a0 -NoLog|egrep -i Drive.*pos.*tion|head -2 Drive's postion: DiskGroup: 0, Span: 0, Arm: 0 Drive's postion: DiskGroup: 0, Span: 0, Arm: 1 ^^^^^^^ So much for grep'ing for output. I've now changed the regexp to: re.match(r'^Drive.s pos[a-z]*tion: DiskGroup: [0-9]+,.*$' Refs: # rpm -qa |egrep -i '(mega|storcl)' MegaCli-8.07.14-1.noarch storcli-1.23.02-1.noarch ,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-, Vincent S. Cojot, Computer Engineering. STEP project. _.,-*~'`^`'~*-,._.,-*~ Ecole Polytechnique de Montreal, Comite Micro-Informatique. _.,-*~'`^`'~*-,. Linux Xview/OpenLook resources page _.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~' http://step.polymtl.ca/~coyote _.,-*~'`^`'~*-,._ [email protected] They cannot scare me with their empty spaces Between stars - on stars where no human race is I have it in me so much nearer home To scare myself with my own desert places. - Robert Frost ------------------------------ Message: 4 Date: Tue, 27 Feb 2018 15:59:40 -0700 From: Stephen Dowdy <[email protected]> To: [email protected], "[email protected]" <[email protected]> Subject: Re: [Linux-PowerEdge] MegaCLI compatibility in StorCli (with added typos) ? Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 On 02/27/2018 03:47 PM, [email protected] wrote: > > Hi, > Has anyone noticed that storcli (version 1.23.02 tested) appears to support > MegaCli's syntax? Does anyone know if this is here to stay? I've written about this several times in the past, e.g.: http://lists.us.dell.com/pipermail/linux-poweredge/2015-January/049533.html https://www.mail-archive.com/[email protected]&q=subject:%22%5C%5BLinux%5C-PowerEdge%5C%5D+PE+r710+%5C-+MegaCli+not+working%22&o=newest&f=1 storcli/perccli help legacy --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - [email protected] - http://www.ral.ucar.edu/~sdowdy/ ------------------------------ Subject: Digest Footer _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge ------------------------------ End of Linux-PowerEdge Digest, Vol 165, Issue 16 ************************************************ _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
