[GH-ISSUE #54] Linux agents not populating model/serial reliably #39

Open
opened 2026-03-02 02:12:52 +03:00 by kerem · 1 comment
Owner

Originally created by @shokoah on GitHub (Dec 17, 2024).
Original GitHub issue: https://github.com/amidaware/rmmagent/issues/54

I'm noticing that the Linux agents are no longer reliably pulling serial numbers/device models. For example:

Example 1 (Dell PowerEdge T320, Kali/Debian):
-TRMM Agent:
Make: Dell Inc.
Serial: ..CN7475155N0789.
-dmidecode (grep -A3 '^System Information')
Manufacturer: Dell Inc.
Product Name: PowerEdge T320
-dmidecode (system-serial-number)
C42RS52
Example 2 (HP ProLiant DL380 G10, Debian 12)
Make: HPE
Serial: PFARAAPLMBH7UG
>> This should be an MXQ... number
Example 3 (Dell PowerEdge T140, RHEL Variant)
TRMM:
Make: Dell Inc.
Serial: .BBPQ9Z2.CNWS30097B00J0.
>> BBPQ9Z2 is the correct service tag, values separated by '.'
Example 4 (Dell OptiPlex 9010, Oracle Linux 9.5)
Make: Dell Inc.
Serial: /BHRTRW1/CN722002B609FM/
>> BHRTRW1 is the correct service tag, values separated by '/'
Working Example (Windows Server):
Make: HPE ProLiant DL360 G10
Serial: MXQ00402WN

I am not very software-dev literate, otherwise I would be happy to try to help sift through code. I have a very diverse TRMM instance, so if there is anything I can pull to help diagnose, please let me know! Thank you for the amazing software as always

Originally created by @shokoah on GitHub (Dec 17, 2024). Original GitHub issue: https://github.com/amidaware/rmmagent/issues/54 I'm noticing that the Linux agents are no longer reliably pulling serial numbers/device models. For example: ``` Example 1 (Dell PowerEdge T320, Kali/Debian): -TRMM Agent: Make: Dell Inc. Serial: ..CN7475155N0789. -dmidecode (grep -A3 '^System Information') Manufacturer: Dell Inc. Product Name: PowerEdge T320 -dmidecode (system-serial-number) C42RS52 ``` ``` Example 2 (HP ProLiant DL380 G10, Debian 12) Make: HPE Serial: PFARAAPLMBH7UG >> This should be an MXQ... number ``` ``` Example 3 (Dell PowerEdge T140, RHEL Variant) TRMM: Make: Dell Inc. Serial: .BBPQ9Z2.CNWS30097B00J0. >> BBPQ9Z2 is the correct service tag, values separated by '.' ``` ``` Example 4 (Dell OptiPlex 9010, Oracle Linux 9.5) Make: Dell Inc. Serial: /BHRTRW1/CN722002B609FM/ >> BHRTRW1 is the correct service tag, values separated by '/' ``` ``` Working Example (Windows Server): Make: HPE ProLiant DL360 G10 Serial: MXQ00402WN ``` I am not very software-dev literate, otherwise I would be happy to try to help sift through code. I have a very diverse TRMM instance, so if there is anything I can pull to help diagnose, please let me know! Thank you for the amazing software as always
Author
Owner

@shokoah commented on GitHub (Dec 17, 2024):

Edit: noticed this is related to #42 - included model with this

<!-- gh-comment-id:2549782978 --> @shokoah commented on GitHub (Dec 17, 2024): Edit: noticed this is related to #42 - included model with this
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rmmagent#39
No description provided.