how to integrate automatic scanning/discovery in HP enclosures:blades ? #243

New issue

Open

opened 2022-09-29 11:47:12 +02:00 by jancovic · 1 comment

jancovic commented

2022-09-29 11:47:12 +02:00

(Migrated from github.com)

Describe the bug
I am using HP enclosures \ blades.
How can I integrate automatic scanning/discovery in enclosures with your agent ?
Is it even possible not to do manually ?

Expected behavior
Goal is that each enclosure will show occupancy and bay hostnames as you can see from Onboard Admin

Configuration file
NA

Environment:
NA]

Additional context
NA

**Describe the bug** I am using HP enclosures \ blades. How can I integrate automatic scanning/discovery in enclosures with your agent ? Is it even possible not to do manually ? **Expected behavior** Goal is that each enclosure will show occupancy and bay hostnames as you can see from Onboard Admin **Configuration file** NA **Environment:** NA] **Additional context** NA

pvl1 commented

2023-06-26 15:10:12 +02:00

(Migrated from github.com)

I have successfully done this in the past.
Certain HPE chassis required some additional coding+hackery in netbox_agent/vendors/hp.py
I didn't find it worth contributing that code because doing so would create clutter. Within one chassis, i could for see 32 different software installs leading to inconsistent dmidecode output (THANKS HP)
So this is certainly possible, given that the vendors expose that information in the first place. There are vendors/chassis that do not expose this through the BIOS or BMC/OOB.
The code as it exists, is capable of this. And is also a great example for hacking.
please see #149

I have successfully done this in the past. Certain HPE chassis required some additional coding+hackery in netbox_agent/vendors/hp.py I didn't find it worth contributing that code because doing so would create clutter. Within one chassis, i could for see 32 different software installs leading to inconsistent dmidecode output (THANKS HP) So this is certainly possible, given that the vendors expose that information in the first place. There are vendors/chassis that do not expose this through the BIOS or BMC/OOB. The code as it exists, is capable of this. And is also a great example for hacking. please see #149