g-bougard
commented
6 years ago Hi @Stoatwblr
are you telling about IPMI discovered via SNMP tasks or via running Generic::IPMI module which one parses the output of ipmitool lan print command ?
Open Stoatwblr opened 7 years ago
g-bougard
commented
6 years ago Hi @Stoatwblr
are you telling about IPMI discovered via SNMP tasks or via running Generic::IPMI module which one parses the output of ipmitool lan print command ?
guillomovitch
commented
6 years ago Linking assets is a server issue, not an agent one, anyway.
g-bougard
commented
6 years ago On the other side, we will be able to detect iLO card via Netdiscovery & Netinventory tasks and they will be shown as new and independent Network devices. The associated computer can be identified via a SNMP OID showing the computer UUID. We could have here an asset linking like VMs with their host server, but this time around the RemoteManagement tab in GLPi.
In the IPMI case, the remote management board is shown, when detected, as a computer network component. IMHO, this is definitively a mistake as a management board can be available while the computer is shut-downed. The related information should effectively just be used to link the computer to a RemoteManagement network device. In fact we should probably create a independent inventory when we detect the management board from the computer via IPMI.
Evgen000
commented
3 years ago Fusion reacts to detecting this second device by creating an "orphan" hub, which is confusing. We (should) already know that the MAC is associated with the computer and any hub device like this should be automatically linked into the asset - the only other alternative is to create each server as an appliance to hold the computer and hub device.
Faced the same problem. When performing the inventory task via SNMP on the switch, it became necessary not to import about 20 MAC addresses (IPMI). Tried adding them to blacklist but import rules ignore it. How to solve this problem?
Many servers (at least Dell, Supermicro, Intel, Asus that I've found so far) configure their IPMI devices to "piggyback" on the primary ethernet interface.
In some cases this is the only IPMI access, in others it is an accessory to a dedicated IPMI port, but in all cases, the IPMI is a separate physical device with its own MAC internal to the computer using the port's tranceivers.
Fusion reacts to detecting this second device by creating an "orphan" hub, which is confusing. We (should) already know that the MAC is associated with the computer and any hub device like this should be automatically linked into the asset - the only other alternative is to create each server as an appliance to hold the computer and hub device.
Just to make things "interesting", at least some servers (ASUS) tie the same IPMI MAC to piggyback on multiple ports unless explicitly configured not to.