Worked Perfectly on my Cluster with 3x Poweredge R610's Thank you for the information!
[TUTORIAL] Dell Openmanage on Proxmox 6.x
- Thread starter Lokytech
- Start date
-
- Tags
- dell omsa openmanage proxmox 6
I able to get it working using the bullseye iSM repo:
Bash:
echo 'deb [signed-by=/etc/apt/trusted.gpg.d/dell.asc] http://linux.dell.com/repo/community/openmanage/iSM/5300/bullseye bullseye main' | tee -a /etc/apt/sources.list.d/linux.dell.com.sources.list
curl https://linux.dell.com/repo/pgp_pubkeys/0x1285491434D8786F.asc > /etc/apt/trusted.gpg.d/dell.asc
apt update
apt install dcism
service dcismeng startWorks perfectly but by adding ubuntu repo to the system (I don't recommend doing this in production system, test it first!).
Dell R750 with OMSA 10.3, using Proxmox 7.4 system.
---------------------------------------------------------------------------
$ cat /etc/apt/sources.list.d/linux.dell.com.sources.list
deb http://linux.dell.com/repo/community/openmanage/10300/focal focal main
---------------------------------------------------------------------------
$ cat /etc/apt/sources.list.d/ubuntu.list
deb http://archive.ubuntu.com/ubuntu focal main universe multiverse
---------------------------------------------------------------------------
$ cat /etc/apt/sources.list
deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib
# security updates
deb http://security.debian.org bullseye-security main contrib
deb http://deb.debian.org/debian bullseye main contrib
deb-src http://deb.debian.org/debian bullseye main contrib
deb http://deb.debian.org/debian bullseye-updates main contrib
deb-src http://deb.debian.org/debian bullseye-updates main contrib
deb http://deb.debian.org/debian bullseye-backports main contrib
========================================================================================
Download it so you can copy it to another system without internet
apt-get download $(apt-rdepends openwsman |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libcimcclient0 |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends cim-schema |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libsfcutil0 |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends sfcb |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libcmpicppimpl0 |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends srvadmin-all |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libncurses5 libxslt1-dev linux-libc-dev |grep -v "^ " | grep -v "^debconf-2.0$" | grep -v "^libc-dev$")
=========================================================================================
Remove srvadmin
apt purge srvadmin-*
Install the packages that was downloaded
dpkg -i *.deb
If you encounter a lot of errors in installing srvadmin packages, execute it again
dpkg -i *.deb
(Same as OP) If you have NVME disk, dataeng will segfault. To correct that problem :
Bash:
nano /opt/dell/srvadmin/etc/srvadmin-storage/stsvc.ini
And comment the line
Code:
vil7=dsm_sm_psrvil
like that :
Code:
; vil7=dsm_sm_psrvil
relogin then execute:
srvadmin-services.sh restart
Dell R750 with OMSA 10.3, using Proxmox 7.4 system.
---------------------------------------------------------------------------
$ cat /etc/apt/sources.list.d/linux.dell.com.sources.list
deb http://linux.dell.com/repo/community/openmanage/10300/focal focal main
---------------------------------------------------------------------------
$ cat /etc/apt/sources.list.d/ubuntu.list
deb http://archive.ubuntu.com/ubuntu focal main universe multiverse
---------------------------------------------------------------------------
$ cat /etc/apt/sources.list
deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib
# security updates
deb http://security.debian.org bullseye-security main contrib
deb http://deb.debian.org/debian bullseye main contrib
deb-src http://deb.debian.org/debian bullseye main contrib
deb http://deb.debian.org/debian bullseye-updates main contrib
deb-src http://deb.debian.org/debian bullseye-updates main contrib
deb http://deb.debian.org/debian bullseye-backports main contrib
========================================================================================
Download it so you can copy it to another system without internet
apt-get download $(apt-rdepends openwsman |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libcimcclient0 |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends cim-schema |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libsfcutil0 |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends sfcb |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libcmpicppimpl0 |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends srvadmin-all |grep -v "^ " | grep -v "^debconf-2.0$")
apt-get download $(apt-rdepends libncurses5 libxslt1-dev linux-libc-dev |grep -v "^ " | grep -v "^debconf-2.0$" | grep -v "^libc-dev$")
=========================================================================================
Remove srvadmin
apt purge srvadmin-*
Install the packages that was downloaded
dpkg -i *.deb
If you encounter a lot of errors in installing srvadmin packages, execute it again
dpkg -i *.deb
(Same as OP) If you have NVME disk, dataeng will segfault. To correct that problem :
Bash:
nano /opt/dell/srvadmin/etc/srvadmin-storage/stsvc.ini
And comment the line
Code:
vil7=dsm_sm_psrvil
like that :
Code:
; vil7=dsm_sm_psrvil
relogin then execute:
srvadmin-services.sh restart
Last edited:
Love it!
My thanks to all for keeping this alive.
Proxmox 7 support is nearing its end, so I'm looking into a direct upgrade to 8.
I see two choices.
1) Remove OMSA 10.1 (see how I did this install here.) / move to SNMP monitoring IDRAC or learn checkmk.
2) Update to OMSA 10.3 via the WGETs in this thread so that I'm ready to move to Proxmox 8.
Can anyone point me in the right direction to understand what's involved in removing OMSA vs updating it as well as the various components?
best,
James
My thanks to all for keeping this alive.
Proxmox 7 support is nearing its end, so I'm looking into a direct upgrade to 8.
I see two choices.
1) Remove OMSA 10.1 (see how I did this install here.) / move to SNMP monitoring IDRAC or learn checkmk.
2) Update to OMSA 10.3 via the WGETs in this thread so that I'm ready to move to Proxmox 8.
Can anyone point me in the right direction to understand what's involved in removing OMSA vs updating it as well as the various components?
best,
James
Thanks JavierChapparo, your method worked for me on a brand new Dell PE R650xs installed with Proxmox 8.2.
But I have an error, or at least missing information for my BOSS-S1 card on second controller (controller=1), where I obtain 'State Unknow" for physical disks, so an error for my Nagios plugin, see below.
I wonder if it is a problem with the version of OMSA (10.3)... Does any one has a clue ?
Thanks in advance.
But I have an error, or at least missing information for my BOSS-S1 card on second controller (controller=1), where I obtain 'State Unknow" for physical disks, so an error for my Nagios plugin, see below.
Code:
# omreport storage pdisk controller=1
Controller (Embedded)
ID : 0
Status :
Name : Physical Disk 0
State : Unknown
Power Status : Not Applicable
Bus Protocol : Not Available
Media : SSD
...I wonder if it is a problem with the version of OMSA (10.3)... Does any one has a clue ?
Thanks in advance.
I have this installed on my server (VE 8.3.1), but I am getting a ton of errors in the PVE > System > System Log and would love to know if there's a way to resolve this.
It loops this over and over.
My server is a PowerEdge T410 with a perc6/i raid controller. Any ideas on where to start with this?
Drives 0:0-0:3 are the physical disks in the RAID, and I believe 1:4 and 1:5 may be iDRAC virtual drives
It loops this over and over.
My server is a PowerEdge T410 with a perc6/i raid controller. Any ideas on where to start with this?
Code:
Jan 15 09:36:26 pve Server_Administrator[1707169]: 1707169 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: 5 Sense code: 24 Sense qualifier: 0) received from Physical Disk 0:0 on Controller 0 at Connector 0 at Enclosure 0.
Jan 15 09:36:26 pve Server_Administrator[1707169]: 1707169 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: 5 Sense code: 24 Sense qualifier: 0) received from Physical Disk 0:1 on Controller 0 at Connector 0 at Enclosure 1.
Jan 15 09:36:26 pve Server_Administrator[1707169]: 1707169 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: 5 Sense code: 24 Sense qualifier: 0) received from Physical Disk 0:2 on Controller 0 at Connector 0 at Enclosure 2.
Jan 15 09:36:27 pve Server_Administrator[1707169]: 1707169 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: 5 Sense code: 24 Sense qualifier: 0) received from Physical Disk 0:3 on Controller 0 at Connector 0 at Enclosure 3.
Jan 15 09:36:27 pve Server_Administrator[1707169]: 1707169 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: 5 Sense code: 24 Sense qualifier: 0) received from Physical Disk 1:4 on Controller 0 at Connector 1 at Enclosure 4.
Jan 15 09:36:27 pve Server_Administrator[1707169]: 1707169 2095 - Storage Service Severity: Informational, Category: Storage, MessageID: STOR0210, Message: SCSI sense data (Sense key: 5 Sense code: 24 Sense qualifier: 0) received from Physical Disk 1:5 on Controller 0 at Connector 1 at Enclosure 5.Drives 0:0-0:3 are the physical disks in the RAID, and I believe 1:4 and 1:5 may be iDRAC virtual drives
Code:
srvadmin-all is already the newest version (10.3.0.0).
Last edited: