Discover Management Consoles such as iLo, iDrac, CIMC, etc.

[mike_toronto2]

Hello good people,

AFAIK, every piece of server hardware contains a management console such as iLo, iDrac, CIMC, etc.  These consoles appear in any network sweep/Cyber sweep and we're constantly being asked to identify them.  Additionally, they contain a tonne of useful hardware/asset information, and they should be captured into CMDB.

My request is to create a Management Console CI Type and have an OOTB discovery package for the various consoles out there.

[ViauJoc]

There already is a CIT named "Management processor" in uCMDB that would be a good candidate for that, but it is currently used only in one or two discoveries.

Some data may be pulled from those out-of-band (OOB) management cards using SNMP but is it usually not enough because it will not provide a key to link the management processor with the server it is installed in.

The most effective way to obtain sensible data out of the OOB management cards is to use IPMI. It can be queried through the network or via the UDA agent running on the server. Most Linux and some Unix distributions already include a tool named "ipmitool" (https://linux.die.net/man/1/ipmitool). For Windows and other platforms, there is an open source tool named "ipmiutil" that works really well (http://ipmiutil.sourceforge.net/). IPMI support is actually more common than SNMP especially on older OOB cards.

IPMI does not only return good information about the management processor itself but also more detailed information about the hardware inside the server box: memory DIMMs, PCI-E cards, chipset, etc. We found that the two most interesting aspects of the IPMI discovery is "FRU" (hardware components) and "LAN" (network address of the management processor).

Here is an example of what can be obtained in Linux using the built-in ipmitool command:

# ipmitool lan print
Set in Progress         : Set Complete
Auth Type Support       : NONE MD5 PASSWORD 
Auth Type Enable        : Callback : 
                        : User     : 
                        : Operator : 
                        : Admin    : MD5 
                        : OEM      : 
IP Address Source       : Static Address
IP Address              : 192.168.1.211
Subnet Mask             : 255.255.255.0
MAC Address             : 00:0e:0c:ea:92:a2
SNMP Community String   : 
IP Header               : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
BMC ARP Control         : ARP Responses Enabled, Gratuitous ARP Disabled
Gratituous ARP Intrvl   : 2.0 seconds
Default Gateway IP      : 192.168.1.254
Default Gateway MAC     : 00:0e:0c:aa:8e:13
Backup Gateway IP       : 0.0.0.0
Backup Gateway MAC      : 00:00:00:00:00:00
RMCP+ Cipher Suites     : None
Cipher Suite Priv Max   : XXXXXXXXXXXXXXX
                        :     X=Cipher Suite Unused
                        :     c=CALLBACK
                        :     u=USER
                        :     o=OPERATOR
                        :     a=ADMIN
                        :     O=OEM

Here is the output we got using ipmiutil ran locally on a Windows server (HP Proliant DL380 G9 hardware):

C:\ipmiutil>ipmiutil lan -rs
ipmiutil lan ver 3.13 
-- BMC version 2.60, IPMI version 2.0 
PEF Control 				: none 

ipmiutil lan, GetLanEntry for channel 2 ...
Lan Param(0) Set in progress: 00 
Lan Param(1) Auth type support: 00 
Lan Param(2) Auth type enables: 00 00 00 00 00 
Lan Param(3) IP address: 192.168.35.239
Lan Param(4) IP addr src: 01 : Static
Lan Param(5) MAC addr: 30 e1 71 66 2e 80 
Lan Param(6) Subnet mask: 255.255.254.0
GetLanEntry(7), ret = 128
Lan Param(10) BMC grat ARP: 02 : Grat-ARP disabled, ARP-resp enabled
GetLanEntry(11), ret = 128
Lan Param(12) Def gateway IP: 192.168.34.1
GetLanEntry(13), ret = 128
GetLanEntry(14), ret = 128
GetLanEntry(15), ret = 128
Lan Param(16) Community string:  
Lan Param(17) Num dest: 0f 
Lan Param(18) Dest type: 01 00 00 00 00 
Lan Param(19) Dest address: 01 00 00 [0.0.0.0] 00 00 00 00 00 00 
Lan Param(20) VLAN ID: 00 00 
Lan Param(21) VLAN Priority: 00 
Lan Param(22) Cipher Suite Support: 04 
Lan Param(23) Cipher Suites    :  0  1  2  3 
Lan Param(24) Cipher Suite Priv:  R  U  U     R    
Lan Param(25) VLAN Dest Tag: 00 00 00 00 
Channel(2=lan) Access Mode: 12 04 : Always Avail, PEF Alerts Enabled
ipmiutil lan, GetSOL for channel 2 ...
SOL Enable: 01 : enabled
SOL Auth: 04 : Admin 
SOL Accum Interval: 14 46 : 100 msec
SOL Retry Interval: 03 64 : 1000 msec
SOL nvol Baud Rate: 0a : 115.2k
SOL vol Baud Rate: 0a : 115.2k
SOL Payload Support(2): 03 00 3f 00 00 00 00 00 
SOL Payload Access(2,1): 00 00 00 00 : disabled
SOL Payload Access(2,2): 00 00 00 00 : disabled
SOL Payload Access(2,3): 00 00 00 00 : disabled
SOL Payload Access(2,4): 00 00 00 00 : disabled
SOL Payload Access(2,5): 00 00 00 00 : disabled
Users:  showing 5 of max 12 users (4 enabled)
User Access(chan2,user1): 0c 44 00 14 : IPMI, Admin  (Administrator)
User Access(chan2,user2): 0c 44 00 14 : IPMI, Admin  (oneview)
User Access(chan2,user3): 0c 44 00 14 : IPMI, Admin  (_HPOneViewAdmin)
User Access(chan2,user4): 0c 84 00 0f : No access ((Empty User))
ipmiutil lan, completed successfully

C:\ipmiutil>ipmiutil fru
ipmiutil fru version 3.13
-- BMC version 2.60, IPMI version 2.0 
--- Scanning SDR Repository for 118 SDRs ---
SDR[0062] FRU  20 ee 17 01 BMC CONTROLLER
[Component,20,ee] Component FRU Size  : 256
[Component,20,ee] Product Manufacturer: HPE
[Component,20,ee] Product Name        : BMC CONTROLLER
[Component,20,ee] Product Part Number : iLO 4
[Component,20,ee] Product Version     : 
[Component,20,ee] Product Serial Num  : 
[Component,20,ee] Product Asset Tag   : 
[Component,20,ee] Product FRU File ID : 
SDR[0063] FRU  20 ef 22 01 MB BIOS
[Component,20,ef] Component FRU Size  : 256
[Component,20,ef] Product Manufacturer: HPE
[Component,20,ef] Product Name        : SYSTEM BIOS
[Component,20,ef] Product Part Number : P89
[Component,20,ef] Product Version     : 05/21/2018
[Component,20,ef] Product Serial Num  : 
[Component,20,ef] Product Asset Tag   : 
[Component,20,ef] Product FRU File ID : 
SDR[0064] FRU  20 10 41 01 CPU 1
[Component,20,10] Component FRU Size  : 256
[Component,20,10] Product Manufacturer: Intel(R) Corporation
[Component,20,10] Product Name        : Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
[Component,20,10] Product Part Number : 
[Component,20,10] Product Version     : 
[Component,20,10] Product Serial Num  : 
[Component,20,10] Product Asset Tag   : 
[Component,20,10] Product FRU File ID : 
SDR[0065] FRU  20 11 41 02 CPU 2
[Component,20,11] Component FRU Size  : 256
[Component,20,11] Product Manufacturer: Intel(R) Corporation
[Component,20,11] Product Name        : Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
[Component,20,11] Product Part Number : 
[Component,20,11] Product Version     : 
[Component,20,11] Product Serial Num  : 
[Component,20,11] Product Asset Tag   : 
[Component,20,11] Product FRU File ID : 
SDR[0066] FRU  20 6e 20 01 CPU 1 DIMM 1
[DIMM     ,20,6e] DIMM      FRU Size  : 512
[DIMM     ,20,6e] Chassis Type        : 
[DIMM     ,20,6e] Chassis Part Number : 
[DIMM     ,20,6e] Chassis Serial Num  : 
[DIMM     ,20,6e] Chassis OEM Field   : 
[DIMM     ,20,6e] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,6e] Board Manufacturer  : 
[DIMM     ,20,6e] Board Product Name  : 
[DIMM     ,20,6e] Board Serial Number : 
[DIMM     ,20,6e] Board Part Number   : 
[DIMM     ,20,6e] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,6e] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[0067] FRU  20 6f 20 04 CPU 1 DIMM 4
[DIMM     ,20,6f] DIMM      FRU Size  : 512
[DIMM     ,20,6f] Chassis Type        : 
[DIMM     ,20,6f] Chassis Part Number : 
[DIMM     ,20,6f] Chassis Serial Num  : 
[DIMM     ,20,6f] Chassis OEM Field   : 
[DIMM     ,20,6f] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,6f] Board Manufacturer  : 
[DIMM     ,20,6f] Board Product Name  : 
[DIMM     ,20,6f] Board Serial Number : 
[DIMM     ,20,6f] Board Part Number   : 
[DIMM     ,20,6f] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,6f] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[0068] FRU  20 70 20 09 CPU 1 DIMM 9
[DIMM     ,20,70] DIMM      FRU Size  : 512
[DIMM     ,20,70] Chassis Type        : 
[DIMM     ,20,70] Chassis Part Number : 
[DIMM     ,20,70] Chassis Serial Num  : 
[DIMM     ,20,70] Chassis OEM Field   : 
[DIMM     ,20,70] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,70] Board Manufacturer  : 
[DIMM     ,20,70] Board Product Name  : 
[DIMM     ,20,70] Board Serial Number : 
[DIMM     ,20,70] Board Part Number   : 
[DIMM     ,20,70] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,70] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[0069] FRU  20 71 20 0c CPU 1 DIMM 12
[DIMM     ,20,71] DIMM      FRU Size  : 512
[DIMM     ,20,71] Chassis Type        : 
[DIMM     ,20,71] Chassis Part Number : 
[DIMM     ,20,71] Chassis Serial Num  : 
[DIMM     ,20,71] Chassis OEM Field   : 
[DIMM     ,20,71] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,71] Board Manufacturer  : 
[DIMM     ,20,71] Board Product Name  : 
[DIMM     ,20,71] Board Serial Number : 
[DIMM     ,20,71] Board Part Number   : 
[DIMM     ,20,71] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,71] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[006a] FRU  20 72 20 0d CPU 2 DIMM 1
[DIMM     ,20,72] DIMM      FRU Size  : 512
[DIMM     ,20,72] Chassis Type        : 
[DIMM     ,20,72] Chassis Part Number : 
[DIMM     ,20,72] Chassis Serial Num  : 
[DIMM     ,20,72] Chassis OEM Field   : 
[DIMM     ,20,72] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,72] Board Manufacturer  : 
[DIMM     ,20,72] Board Product Name  : 
[DIMM     ,20,72] Board Serial Number : 
[DIMM     ,20,72] Board Part Number   : 
[DIMM     ,20,72] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,72] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[006b] FRU  20 73 20 10 CPU 2 DIMM 4
[DIMM     ,20,73] DIMM      FRU Size  : 512
[DIMM     ,20,73] Chassis Type        : 
[DIMM     ,20,73] Chassis Part Number : 
[DIMM     ,20,73] Chassis Serial Num  : 
[DIMM     ,20,73] Chassis OEM Field   : 
[DIMM     ,20,73] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,73] Board Manufacturer  : 
[DIMM     ,20,73] Board Product Name  : 
[DIMM     ,20,73] Board Serial Number : 
[DIMM     ,20,73] Board Part Number   : 
[DIMM     ,20,73] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,73] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[006c] FRU  20 74 20 15 CPU 2 DIMM 9
[DIMM     ,20,74] DIMM      FRU Size  : 512
[DIMM     ,20,74] Chassis Type        : 
[DIMM     ,20,74] Chassis Part Number : 
[DIMM     ,20,74] Chassis Serial Num  : 
[DIMM     ,20,74] Chassis OEM Field   : 
[DIMM     ,20,74] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,74] Board Manufacturer  : 
[DIMM     ,20,74] Board Product Name  : 
[DIMM     ,20,74] Board Serial Number : 
[DIMM     ,20,74] Board Part Number   : 
[DIMM     ,20,74] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,74] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[006d] FRU  20 75 20 18 CPU 2 DIMM 12
[DIMM     ,20,75] DIMM      FRU Size  : 512
[DIMM     ,20,75] Chassis Type        : 
[DIMM     ,20,75] Chassis Part Number : 
[DIMM     ,20,75] Chassis Serial Num  : 
[DIMM     ,20,75] Chassis OEM Field   : 
[DIMM     ,20,75] Board Mfg DateTime  : Fri May 16 21:07:00 1997
[DIMM     ,20,75] Board Manufacturer  : 
[DIMM     ,20,75] Board Product Name  : 
[DIMM     ,20,75] Board Serial Number : 
[DIMM     ,20,75] Board Part Number   : 
[DIMM     ,20,75] Board FRU File ID   : 0df80300006e6e6e
[DIMM     ,20,75] Board OEM Field     : 087620080005700300781e2b2b00780014
SDR[006e] FRU  20 02 2c 31 Ethernet Adptr
[Component,20,02] Component FRU Size  : 4096
[Component,20,02] Board Mfg DateTime  : Tue Dec 30 16:30:00 1997
[Component,20,02] Board Manufacturer  : HP
[Component,20,02] Board Product Name  : HP Ethernet 10Gb 2-port 560FLR-SFP+ Adapter
[Component,20,02] Board Serial Number : G42955-016
[Component,20,02] Board Part Number   : 669281-001
[Component,20,02] Board FRU File ID   : 04/25/14
[Component,20,02] Board OEM Field     : d23043
[Component,20,02] Product Manufacturer: HP
[Component,20,02] Product Name        : HP Ethernet 10Gb 2-port 560FLR-SFP+ Adapter
[Component,20,02] Product Part Number : 665243-B21
[Component,20,02] Product Version     : 00
[Component,20,02] Product Serial Num  : MYI71101FX
[Component,20,02] Product Asset Tag   : 
[Component,20,02] Product FRU File ID : 
[Component,20,02] Product OEM Field   : 
[Component,20,02] Multi[0]  d0 : 0b
SDR[006f] FRU  20 03 31 02 Mezz Slot 2
[Component,20,03] Component FRU Size  : 4096
[Component,20,03] Board Mfg DateTime  : Mon Jul 07 20:00:00 2014
[Component,20,03] Board Manufacturer  : HP
[Component,20,03] Board Product Name  : HP SN1000Q 16Gb 2P FC HBA
[Component,20,03] Board Serial Number : 8C97131044
[Component,20,03] Board Part Number   : 699765-001
[Component,20,03] Board FRU File ID   : 07/08/14
[Component,20,03] Board OEM Field     : d23043
[Component,20,03] Product Manufacturer: HP
[Component,20,03] Product Name        : HP SN1000Q 16Gb 2P FC HBA
[Component,20,03] Product Part Number : QW972A
[Component,20,03] Product Version     : 00
[Component,20,03] Product Serial Num  : 8C97131044
[Component,20,03] Product Asset Tag   : 
[Component,20,03] Product FRU File ID : 
[Component,20,03] Multi[0]  d0 : 0b
SDR[0070] FRU  20 04 31 04 Mezz Slot 4
[Component,20,04] Component FRU Size  : 4096
[Component,20,04] Board Mfg DateTime  : Mon Jul 07 20:00:00 2014
[Component,20,04] Board Manufacturer  : HP
[Component,20,04] Board Product Name  : HP SN1000Q 16Gb 2P FC HBA
[Component,20,04] Board Serial Number : 8C9713102K
[Component,20,04] Board Part Number   : 699765-001
[Component,20,04] Board FRU File ID   : 07/08/14
[Component,20,04] Board OEM Field     : d23043
[Component,20,04] Product Manufacturer: HP
[Component,20,04] Product Name        : HP SN1000Q 16Gb 2P FC HBA
[Component,20,04] Product Part Number : QW972A
[Component,20,04] Product Version     : 00
[Component,20,04] Product Serial Num  : 8C9713102K
[Component,20,04] Product Asset Tag   : 
[Component,20,04] Product FRU File ID : 
[Component,20,04] Multi[0]  d0 : 0b
SDR[0071] FRU  20 05 31 05 Mezz Slot 5
[Component,20,05] Component FRU Size  : 4096
[Component,20,05] Board Mfg DateTime  : Mon Jul 07 20:00:00 2014
[Component,20,05] Board Manufacturer  : HP
[Component,20,05] Board Product Name  : HP SN1000Q 16Gb 2P FC HBA
[Component,20,05] Board Serial Number : 8C97131049
[Component,20,05] Board Part Number   : 699765-001
[Component,20,05] Board FRU File ID   : 07/08/14
[Component,20,05] Board OEM Field     : d23043
[Component,20,05] Product Manufacturer: HP
[Component,20,05] Product Name        : HP SN1000Q 16Gb 2P FC HBA
[Component,20,05] Product Part Number : QW972A
[Component,20,05] Product Version     : 00
[Component,20,05] Product Serial Num  : 8C97131049
[Component,20,05] Product Asset Tag   : 
[Component,20,05] Product FRU File ID : 
[Component,20,05] Multi[0]  d0 : 0b
SDR[0072] FRU  20 06 31 06 Mezz Slot 6
[Component,20,06] Component FRU Size  : 4096
[Component,20,06] Board Mfg DateTime  : Mon Jul 07 20:00:00 2014
[Component,20,06] Board Manufacturer  : HP
[Component,20,06] Board Product Name  : HP SN1000Q 16Gb 2P FC HBA
[Component,20,06] Board Serial Number : 8C9713103V
[Component,20,06] Board Part Number   : 699765-001
[Component,20,06] Board FRU File ID   : 07/08/14
[Component,20,06] Board OEM Field     : d23043
[Component,20,06] Product Manufacturer: HP
[Component,20,06] Product Name        : HP SN1000Q 16Gb 2P FC HBA
[Component,20,06] Product Part Number : QW972A
[Component,20,06] Product Version     : 00
[Component,20,06] Product Serial Num  : 8C9713103V
[Component,20,06] Product Asset Tag   : 
[Component,20,06] Product FRU File ID : 
[Component,20,06] Multi[0]  d0 : 0b
SDR[0073] FRU  20 07 01 01 Embedded 1
[Component,20,07] Component FRU Size  : 256
[Component,20,07] Product Manufacturer: 
[Component,20,07] Product Name        : Dynamic Smart Array B140i Controller
[Component,20,07] Product Part Number : 
SDR[0074] FRU  20 08 2c 01 Ethernet Adptr
[Component,20,08] Component FRU Size  : 256
[Component,20,08] Product Manufacturer: 
[Component,20,08] Product Name        : HPE Ethernet 1Gb 4-port 331i Adapter
[Component,20,08] Product Part Number : 
[Component,20,08] Product Version     : 
[Component,20,08] Product Serial Num  : 
[Component,20,08] Product Asset Tag   : 
[Component,20,08] Product FRU File ID : 
SDR[0075] FRU  20 09 31 03 Mezz Slot 3
[Component,20,09] Component FRU Size  : 256
[Component,20,09] Product Manufacturer: 
[Component,20,09] Product Name        : NVM Express Controller
[Component,20,09] Product Part Number : 
[Component,20,09] Product Version     : 
[Component,20,09] Product Serial Num  : 
[Component,20,09] Product Asset Tag   : 
[Component,20,09] Product FRU File ID : 

[Component,20,00] Component FRU Size  : 4096
[Component,20,00] Chassis Type        : Rack-Mount Chassis
[Component,20,00] Chassis Part Number : 
[Component,20,00] Chassis Serial Num  : MXQ72202RX
[Component,20,00] Board Mfg DateTime  : Tue Jul 01 20:00:00 2014
[Component,20,00] Board Manufacturer  : HP
[Component,20,00] Board Product Name  : ProLiant DL380 Gen9
[Component,20,00] Board Serial Number : MXQ72202RX
[Component,20,00] Board Part Number   : 719064-B21
[Component,20,00] Board FRU File ID   : 
[Component,20,00] Product Manufacturer: HP
[Component,20,00] Product Name        : ProLiant DL380 Gen9
[Component,20,00] Product Part Number : 719064-B21
[Component,20,00] Product Version     : 
[Component,20,00] Product Serial Num  : MXQ72202RX
[Component,20,00] Product Asset Tag   : 
[Component,20,00] Product FRU File ID : 
[Component,20,00] System GUID         : 37313930-3634-4d58-5137-323230325258
[SysInfo  ,20,00] BIOS Version        : P89
ipmiutil fru, completed successfully

Pros for using IPMI command in the OS:

• Very easy to link the management processor to the Node it is installed in.
• Does not require any credentials to be set on the OOB card. The query is made through the IPMI driver in the OS
• Can query OOB card that are connected to a private management network which would not even be accessible by UD probes.

Pros for using IPMI over the network:

• Support OSes that cannot have UDA installed on such as VMware ESXi or prebuilt OS distributions that turns the server into an appliance.
• Do not require the deployment of a third party tool such as ipmiutil for Windows on all Nodes, just on the UD probes.
• Support any type of hardware that implement the IPMI protocol: SAN, NAS, firewall, appliances, etc.

I think that UD should support both ways and let the user decide which one is best for their IT environment. In some cases, like us, both ways would be required to ensure maximum discovery coverage.

[mike_toronto2]

I had no idea IPMI brought back such extensive results.  Thanks for the insight 👍

[csatterthwaite]

Management console discovery definitely has its place, especially on the Asset Management side. 

There are management cards all over: in a hardware blade, in the enclosure (managing the blades), in the rack.  Continue the fun down to smart power strips and other IP enabled components.  It's pretty amazing seeing it all together.  If you discover the rack, enclosures in the rack, and blades in the enclosures - the discovery jobs fill in the gaps with access/protocols/provisioning.

Specific to Hardware type discovery, I've created packages across these in the past:

• HP BladeSystem and HP blades
• IBM BladeCenter and IBM blades
• Dell’s web service, a Dell management center, and Dell servers

Protocols used were across the board: HTTP/SSL/SSH/REST/CLI. 

Depending on the endpoint and type, you get a lot more data than you may think... and not all require credentials.  Here's an example:

The more discovery/integration options you have, the better - when it comes to bridging gaps.  One engagement that used hardware component discovery, required 3 different jobs before showing a surprising percentage of their iLOs were not configured as expected (cert issues, protocol(s) not enabled, default account enabled, etc).

But while management card discovery is valuable, it has its own cost of development and upkeep.  It literally has its own domain of discovery and products... similar to how NNMi is for network device discovery.  Perhaps this idea exchange topic creates momentum for the product to shrink wrap more HW type discoveries in the future.  Though I'd expect most of this to continue like I've seen in the past... created by customer or consulting resources.  Because there's only so much a vendor can support on their end.

On the data model side, I use separate CITs to keep the data set clean and avoid recon from playing a part.  You can connect the OS (Node) when it was found by the standard jobs.  FYI in case this helps in the interim. 

[Bill_Dyck]

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

[Tobian]

Very nice idea! We currently fill this information by using HPE SIM to do the discovery and monitoring and integrating with that. tat gives a lot of information, although it can really use an update. 

I think other hardware suppliers have similar tools, wouldn't that be a good way to get this information?

[Bill_Dyck]

Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes