Abstract: Technology described herein can globally perform management of security tokens of plural nodes of a multi-node system. In an embodiment, a system can comprise an interconnected group of server nodes, and an administrator node communicatively connected to the interconnected group of server nodes and comprising a processor, and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise selecting a server node of the interconnected group of server nodes as a leader server node, resulting in a selection of the leader server node, in response, receiving, by the administrator node from the leader server node, a request for a new security token, and sending, to the leader server node, the new security token, and broadcasting, by the leader server node across a link layer discovery (LLDP) network, the new security token to additional nodes of the interconnected group of nodes.

Abstract: Support is provided for remote monitoring and management of non-standard devices of an IHS (Information Handling System) that are not supported by a remote management interface, such as the Redfish management interface. The IHS may be configured for remote management of a non-standard device as part of the manufacture of the IHS. Software for management of the non-standard device is validated against a checksum stored to the IHS during its manufacture to confirm the software for managing the non-standard device has not been altered. If the software is validated, the software is used to initialize a plugin for management of the non-standard device. Data collected by the plugin from monitoring of the non-standard device is provided to a remote access controller of the IHS and the remote access controller issues commands to the non-standard device via the plugin.

Abstract: Embodiments are described for supporting remote monitoring and management of non-standard devices of an IHS (Information Handling System) that are not supported by a remote management interface, such as the Redfish management interface. The IHS may be configured for remote management of a non-standard device as part of the manufacture of the IHS. Software for management of the non-standard device is validated against a checksum stored to the IHS during its manufacture to confirm the software for managing the non-standard device has not been altered. If the software is validated, the software is used to initialize a plugin for management of the non-standard device according. Data collected by the plugin from monitoring of the non-standard device is provided to a remote access controller of the IHS and the remote access controller issues commands to the non-standard device via the plugin.

Abstract: Method and systems provide tools for evaluating the impact of component deprecations with a datacenter formed from a plurality of IHSs. Upon receiving a notification of a deprecated component, configuration files that invoke the deprecated component and are in use within the datacenter are identified. Estimates are generated for the resources that would be required to replace references to the deprecated component within the identified configuration files. Estimates may be generated based on compilation errors, test suite failures and historical error repair data. A tree is generated of the dependencies on the deprecated component within the identified configuration files. Based on characteristics of the dependency tree and also based on the resource estimates for replacing references to the deprecated component, a risk level is generated for the deprecated component. The risk level may be generated for individual IHSs, groups of IHSs, or an entire data center.

Abstract: Method and systems support management of deprecated components within a system of IHSs (Information Handling Systems), such as within a datacenter. Upon receiving notification of a deprecated component, instances of the deprecated component are identified within the datacenter. Usage information is collected for the deprecated component by remote access capabilities of the IHSs and by management capabilities of chassis in which the IHSs may be housed. Based on the collected usage information, usages are determined for individual features of the deprecated component. Even though a component has been deprecated, some features of the component may still be supported. Such supported features of the deprecated components are identified. Licenses may be provided for use of features that are that are supported and that are actually utilized, as determined from the usage information.

Abstract: Method and systems provide tools for evaluating the impact of component deprecations with a datacenter formed from a plurality of IHSs. Upon receiving a notification of a deprecated component, configuration files that invoke the deprecated component and are in use within the datacenter are identified. Estimates are generated for the resources that would be required to replace references to the deprecated component within the identified configuration files. Estimates may be generated based on compilation errors, test suite failures and historical error repair data. A tree is generated of the dependencies on the deprecated component within the identified configuration files. Based on characteristics of the dependency tree and also based on the resource estimates for replacing references to the deprecated component, a risk level is generated for the deprecated component. The risk level may be generated for individual IHSs, groups of IHSs, or an entire data center.

Abstract: Method and systems support management of deprecated components within a system of IHSs (Information Handling Systems), such as within a datacenter. Upon receiving notification of a deprecated component, instances of the deprecated component are identified within the datacenter. Usage information is collected for the deprecated component by remote access capabilities of the IHSs and by management capabilities of chassis in which the IHSs may be housed. Based on the collected usage information, usages are determined for individual features of the deprecated component. Even though a component has been deprecated, some features of the component may still be supported. Such supported features of the deprecated components are identified. Licenses may be provided for use of features that are that are supported and that are actually utilized, as determined from the usage information.