Abstract: A method includes obtaining data associated with a volatile storage device and a non-volatile storage device of an information handling system during a normal mode of operation of the information handling system, and calculating a first data transfer frequency and a first transfer data size from the volatile storage device to the non-volatile storage device based on the data associated with the volatile storage device and the non-volatile storage device during the normal mode of operation of the information handling system. The method also includes detecting an event indicating a power outage of the information handling system, and in response to the detecting the event, determining a data management policy to be applied to the information handling system during the safe mode of operation of the information handling system.

Abstract: An information handling system may include a processor and a management controller communicatively coupled to the processor and configured to perform out-of-band management of the information handling system, the management controller further configured to, in response to a request from a management utility remote from the information handling system to create a firmware image for an item of firmware for a cluster comprising the information handling system retrieve a firmware update package, store the firmware update package in a repository integral to the management controller, and communicate a uniform resource locator to the management utility setting forth a path of the firmware update package within the repository, such that the management utility may later use the uniform resource locator to perform a firmware update for another information handling system of the cluster.

Abstract: A method comprises receiving an input of at least one image associated with an issue. In the method, text is extracted from the at least one image, and an intent is determined from the extracted text. The method further includes recommending a response to the issue based at least in part on the determined intent, and transmitting the recommended response to a user. The extracting, determining and recommending are performed at least in part using one or more machine learning models.

Abstract: A network (e.g. cloud or enterprise network) includes servers (110) and switches (120) each of which has multiple ports. A bare-metal server's ports are configured for different roles, e.g. management role or data role. The configuration is at least partially automated using a blueprint (340) which does not necessarily specify the roles for the server ports, but may associate a role with a network parameter, e.g. Maximum Transfer Unit (MTU) or QoS. A management computer (320) obtains, from switches, (i) network parameters configured on switch ports, and (ii) MAC addresses for the adjacent server ports. The management computer matches the blueprint's parameters with the switch ports' parameters, and associates matched parameters with the roles specified by the blueprint. These roles are configured on the corresponding server ports. Other features are also provided.

Abstract: An information handling system may include a processor and a management controller communicatively coupled to the processor and configured to perform out-of-band management of the information handling system, the management controller further configured to, in response to a request from a management utility remote from the information handling system to create a firmware image for an item of firmware for a cluster comprising the information handling system retrieve a firmware update package, store the firmware update package in a repository integral to the management controller, and communicate a uniform resource locator to the management utility setting forth a path of the firmware update package within the repository, such that the management utility may later use the uniform resource locator to perform a firmware update for another information handling system of the cluster.

Abstract: Applying failure policy during updating of components, including receiving metadata of each of the components, the metadata indicating a respective classification of each of the components; sorting the components based on the metadata, including identifying a first subset of the components as critical components and a second subset of the components as non-critical components; receiving a first update package for a first component; detecting a failure to apply the first update package to the first component; in response to detecting the failure to apply the first update package to the first component: determining that the first component belongs to the first subset of components; in response to determining that the first component belongs to the first subset of components, identifying a remediation policy associated with critical components; applying the remediation policy to the first component, including rollback of the first update package at the first component.

Abstract: Applying failure policy during updating of components, including receiving metadata of each of the components, the metadata indicating a respective classification of each of the components; sorting the components based on the metadata, including identifying a first subset of the components as critical components and a second subset of the components as non-critical components; receiving a first update package for a first component; detecting a failure to apply the first update package to the first component; in response to detecting the failure to apply the first update package to the first component: determining that the first component belongs to the first subset of components; in response to determining that the first component belongs to the first subset of components, identifying a remediation policy associated with critical components; applying the remediation policy to the first component, including rollback of the first update package at the first component.

Abstract: A method comprises retrieving operating conditions data comprising operational details of one or more components in at least one computing environment. Component replacement data and no fault found (NFF) data of the computing environment are also retrieved. The component replacement data comprises details about components that have been replaced in the computing environment. The NFF data comprises details about components incorrectly identified as having failed in the computing environment and symptoms leading to the incorrect identifications. The method also comprises generating a first mapping between given ones of the operational details and given ones of the replaced components, and generating a second mapping between given ones of the incorrectly identified components and given ones of the symptoms using one or more machine learning algorithms. Using the first and second mappings, at least one failed component is predicted based on one or more symptoms identified in a received support case.

Abstract: A method comprises receiving an input of at least one image associated with an issue. In the method, text is extracted from the at least one image, and an intent is determined from the extracted text. The method further includes recommending a response to the issue based at least in part on the determined intent, and transmitting the recommended response to a user. The extracting, determining and recommending are performed at least in part using one or more machine learning models.

Abstract: A method includes obtaining data associated with a volatile storage device and a non-volatile storage device of an information handling system during a normal mode of operation of the information handling system, and calculating a first data transfer frequency and a first transfer data size from the volatile storage device to the non-volatile storage device based on the data associated with the volatile storage device and the non-volatile storage device during the normal mode of operation of the information handling system. The method also includes detecting an event indicating a power outage of the information handling system, and in response to the detecting the event, determining a data management policy to be applied to the information handling system during the safe mode of operation of the information handling system.

Abstract: A method comprises retrieving operating conditions data comprising operational details of one or more components in at least one computing environment. Component replacement data and no fault found (NFF) data of the computing environment are also retrieved. The component replacement data comprises details about components that have been replaced in the computing environment. The NFF data comprises details about components incorrectly identified as having failed in the computing environment and symptoms leading to the incorrect identifications. The method also comprises generating a first mapping between given ones of the operational details and given ones of the replaced components, and generating a second mapping between given ones of the incorrectly identified components and given ones of the symptoms using one or more machine learning algorithms. Using the first and second mappings, at least one failed component is predicted based on one or more symptoms identified in a received support case.

Abstract: A method includes obtaining data associated with a volatile storage device and a non-volatile storage device of an information handling system during a normal mode of operation of the information handling system, and calculating a first data transfer frequency and a first transfer data size from the volatile storage device to the non-volatile storage device based on the data associated with the volatile storage device and the non-volatile storage device during the normal mode of operation of the information handling system. The method also includes detecting an event indicating a power outage of the information handling system, and in response to the detecting the event, determining a data management policy to be applied to the information handling system during the safe mode of operation of the information handling system.

Abstract: A network (e.g. cloud or enterprise network) includes servers (110) and switches (120) each of which has multiple ports. A bare-metal server's ports are configured for different roles, e.g. management role or data role. The configuration is at least partially automated using a blueprint (340) which does not necessarily specify the roles for the server ports, but may associate a role with a network parameter, e.g. Maximum Transfer Unit (MTU) or QoS. A management computer (320) obtains, from switches, (i) network parameters configured on switch ports, and (ii) MAC addresses for the adjacent server ports. The management computer matches the blueprint's parameters with the switch ports' parameters, and associates matched parameters with the roles specified by the blueprint. These roles are configured on the corresponding server ports. Other features are also provided.

Abstract: In accordance with the present disclosure, a system and method are herein disclosed for providing a virtualization aware server maintenance mode. In one embodiment, an event is triggered in when a system action request is received by an information handling system. The event is processed and the hypervisor is placed in maintenance mode. The virtualization manager is notified that the mode of the hypervisor has changed and the virtualization manager stores the information associated with the mode status change. The virtualization manager may also notify other remote access consoles or virtualization managers of the mode status change of the hypervisor. A maintenance mode lock may be acquired when the hypervisor is placed in maintenance mode and released after the system action has been processed.

Abstract: In accordance with the present disclosure, a system and method are herein disclosed for providing a virtualization aware server maintenance mode. In one embodiment, an event is triggered in when a system action request is received by an information handling system. The event is processed and the hypervisor is placed in maintenance mode. The virtualization manager is notified that the mode of the hypervisor has changed and the virtualization manager stores the information associated with the mode status change. The virtualization manager may also notify other remote access consoles or virtualization managers of the mode status change of the hypervisor. A maintenance mode lock may be acquired when the hypervisor is placed in maintenance mode and released after the system action has been processed.

Abstract: In accordance with the present disclosure, a system and method are herein disclosed for providing a virtualization aware server maintenance mode. In one embodiment, an event is triggered in when a system action request is received by an information handling system. The event is processed and the hypervisor is placed in maintenance mode. The virtualization manager is notified that the mode of the hypervisor has changed and the virtualization manager stores the information associated with the mode status change. The virtualization manager may also notify other remote access consoles or virtualization managers of the mode status change of the hypervisor. A maintenance mode lock may be acquired when the hypervisor is placed in maintenance mode and released after the system action has been processed.

Abstract: In accordance with the present disclosure, a system and method are herein disclosed for providing a virtualization aware server maintenance mode. In one embodiment, an event is triggered in when a system action request is received by an information handling system. The event is processed and the hypervisor is placed in maintenance mode. The virtualization manager is notified that the mode of the hypervisor has changed and the virtualization manager stores the information associated with the mode status change. The virtualization manager may also notify other remote access consoles or virtualization managers of the mode status change of the hypervisor. A maintenance mode lock may be acquired when the hypervisor is placed in maintenance mode and released after the system action has been processed.