Granted Patent B2

US 12,647,313 · App. 18/751,948 · Granted Jun 2, 2026

Inventors: Kareemuddin Syed (Hyderabad, IN); Sunny Bhattacharjee (Ghaziabad, IN); Ganesh Javvadi (Hyderabad, IN); Rohit Prakash Kadam (Pune, IN); Surya Pradeep V V S Sundarapu (Hyderabad, IN)

Assignee: BANK OF AMERICA CORPORATION

H04L41/0654H04L41/0627H04L41/5074

Abstract

Claims (45)

1 . A system for physical server crash response assistance, the system comprising:

a cluster comprising a plurality of physical servers, each of the plurality of physical servers executing a hypervisor operating system that is configured to host a plurality of virtual machine servers, wherein the plurality of virtual machine servers execute one of at least two different guest operating systems; and

a computing platform including a memory and one or more computing processor devices in communication with the memory, wherein the memory stores a crash response assistance sub-system that is executable by at least one of the one or more computing processor devices and includes:

a physical server crash register module configured to, in response to a first physical server from amongst the plurality of physical servers experiencing at least one of a hardware failure and a software failure that results in the hypervisor operating system failing to execute, invoke one or more first Application Programming Interface (API) calls and instantiate a connection to one or more databases to retrieve details associated with the at least one of the hardware failure and the software failure experienced by the first physical server,

a physical to virtual device mapping transformer module configured to identify, based at least on the retrieved details associated with the at least one of the hardware failure and the software failure experienced by the first physical server, a plurality of impacted virtual machine servers from amongst the plurality of virtual machine servers that were powered off as a result of the first physical server experiencing the at least one of the hardware failure and the software failure by:

invoking one or more second API calls to and instantiating a connection to a Virtual Center database,

extracting event tokens from records associated with the plurality of physical servers and the plurality of virtual machine servers,

executing keyword searches across the extracted event tokens to narrow down search criteria, and

identifying the plurality of impacted virtual machine servers from the narrowed down search criteria,

a feedback module configured to (i) perform one or more validation checks to validate whether each of the plurality of impacted virtual machine servers (a) recovered to a powered-on state after migrating to another server in the cluster or (b) remain in a powered-off state, and (ii) identify impacted stakeholders for at least one of the first physical server, and one or more applications executing on each impacted virtual machine server, and

a notification module configured to initiate communication of service interruption notification to the identified impacted stakeholders, wherein the service interruption notification includes at least one of the impacted virtual machine servers, one or more applications interrupted on the least one of the impacted virtual machine servers and whether the at least one of the impacted virtual machine servers (a) recovered to a powered-on state after migrating to another server in the cluster or (b) remains in a powered-off state.

2 . The system of claim 1 , wherein the physical server crash register module configured to invoke the one or more first Application Programming Interface (API) calls to one or more databases to retrieve details associated with the first physical server, wherein the one or more databases include a Cloud Inventory database and the details associated with the first physical server include one or more of (i) a server region in which the first physical server resides, (ii) a data center within the server region in which the first physical service resides, (iii) a cluster within the data center that includes the first physical server, and (iv) a cluster service offering type for the cluster.

3 . The system of claim 1 , wherein the physical server crash register module configured to invoke the one or more first Application Programming Interface (API) calls to one or more databases to retrieve details associated with the first physical server, wherein the one or more databases include a configuration management database and the details associated with the first physical server include one or more support groups that manage one or more of (i) the first physical server, (ii) a hardware component related to the hardware failure, and (iii) a software application related to the software failure.

4 . The system of claim 1 , wherein the physical to virtual device mapping transformer module is further configured to initiate a health check on the plurality of impacted virtual machine servers by pinging each of the plurality of impacted virtual machine servers and receiving a response to the ping as an indication that a corresponding impacted virtual machine server recovered to a powered-on state after migrating to another server in the cluster.

5 . The system of claim 1 , wherein the feedback module is further configured to identify a functional environment for each of the one or more applications executing on each impacted virtual machine server and details surrounding the functional environment.

6 . The system of claim 1 , wherein the notification module is further configured to initiate communication of the service interruption notification via at least one of electronic mail, paging or communications portal posting.

7 . The system of claim 1 , wherein the crash response assistance subsystem further comprises a correlation module configured to receive data related to the at least one of the hardware failure and the software failure experienced by the physical server and the plurality of impacted virtual machine servers and correlate the data with at least one of a hardware failure ticket and a software failure ticket in a corresponding failure ticketing system database.

8 . A computer-implemented method for physical server crash response assistance, the computer-implemented method is executable by one or more computing processor devices and comprises:

in response to a physical server experiencing at least one of a hardware failure and a software failure that results in a hypervisor operating system failing to execute on the physical server, invoking one or more first Application Programming Interface (API) calls and instantiating a connection to one or more databases to retrieve details associated with the at least one of hardware failure and software failure experienced by a first physical server;

identifying, based at least on the retrieved details associated with the first physical server, a plurality of impacted virtual machine servers that were executing on the first physical server and were powered off as a result of the first physical server experiencing the at least one of the hardware failure and the software failure, wherein identifying further comprises:

invoking one or more second API calls to and instantiating a connection to a Virtual Center database;

extracting event tokens from records associated with the plurality of physical servers and the plurality of virtual machine servers;

executing keyword searches across the extracted event tokens to narrow down search criteria; and

identifying the plurality of impacted virtual machine servers from the narrowed down search criteria;

performing one or more validation checks to validate whether each of the plurality of impacted virtual machine servers (a) recovered to a powered-on state after migrating to another server in a corresponding cluster or (b) remain in a powered-off state;

identifying impacted stakeholders for at least one of the first physical server, and one or more applications executing on each impacted virtual machine server; and

initiating communication of service interruption notification to the identified impacted stakeholders, wherein the service interruption notification includes at least one of the impacted virtual machine servers, one or more applications interrupted on the least one of the impacted virtual machine servers and whether the at least one of the impacted virtual machine servers (a) recovered to a powered-on state after migrating to another server in the corresponding cluster or (b) remains in a powered-off state.

9 . The computer-implemented method of claim 8 , wherein invoking the one or more first Application Programming Interface (API) calls to one or more databases to retrieve the details associated with the first physical server further defines the one or more databases as including a Cloud Inventory database and the details associated with the first physical server as including one or more of (i) a server region in which the first physical server resides, (ii) a data center within the server region in which the first physical service resides, (iii) a cluster within the data center that includes the first physical server, and (iv) a cluster service offering type for the cluster.

10 . The computer-implemented method of claim 8 , wherein invoking the one or more first Application Programming Interface (API) calls to one or more databases to retrieve the details associated with the first physical server further defines the one or more databases as including as a configuration management database and the details associated with the first physical server as including one or more support groups that manage one or more of (i) the first physical server, (ii) a hardware component related to the hardware failure, and (iii) a software application related to the software failure.

11 . The computer-implemented method of claim 8 , further comprising: initiating a health check on the plurality of impacted virtual machine servers by pinging each of the plurality of impacted virtual machine servers and receiving a response to the ping as an indication that a corresponding impacted virtual machine server has recovered to a powered-on state after migrating to another server in the corresponding cluster.

12 . The computer-implemented method of claim 8 , further comprising: identifying a functional environment for each of the one or more applications executing on each impacted virtual machine server and details surrounding the functional environment.

13 . A computer program product including a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising sets of codes for causing one or more computing devices to:

in response to a physical server experiencing at least one of a hardware failure and a software failure that results in a hypervisor operating system failing to execute on the physical server, invoke one or more first Application Programming Interface (API) calls and instantiate a connection to one or more databases to retrieve details associated with the at least one of hardware failure and software failure experienced by a first physical server;

identify, based at least on the retrieved details associated with the first physical server, a plurality of impacted virtual machine servers that were executing on the first physical server and were powered off as a result of the first physical server experiencing the at least one of the hardware failure and the software failure, wherein identifying further comprises:

invoking one or more second API calls to and instantiating a connection to a Virtual Center database,

extracting event tokens from records associated with the plurality of physical servers and a plurality of virtual machine servers,

executing keyword searches across the extracted event tokens to narrow down search criteria, and

identifying the plurality of impacted virtual machine servers from the narrowed down search criteria;

perform one or more validation checks to validate whether each of the plurality of impacted virtual machine servers (a) recovered to a powered-on state after migrating to another server in a corresponding cluster or (b) remain in a powered-off state;

identify impacted stakeholders for at least one of the first physical server, and one or more applications executing on each impacted virtual machine server; and

initiate communication of service interruption notification to the identified impacted stakeholders, wherein the service interruption notification includes at least one of the impacted virtual machine servers, one or more applications interrupted on the least one of the impacted virtual machine servers and whether the at least one of the impacted virtual machine servers (a) recovered to a powered-on state after migrating to another server in the corresponding cluster or (b) remains in a powered-off state.

14 . The computer program product of claim 13 , wherein the set of codes for causing the one or more computing devices to invoke the one or more first Application Programming Interface (API) calls to one or more databases to retrieve the details associated with the first physical server further defines the one or more databases as including a Cloud Inventory database and the details associated with the first physical server as including one or more of (i) a server region in which the first physical server resides, (ii) a data center within the server region in which the first physical service resides, (iii) a cluster within the data center that includes the first physical server, and (iv) a cluster service offering type for the cluster.

15 . The computer program product of claim 13 , wherein the set of codes for causing the one or more computing devices to invoke the one or more first Application Programming Interface (API) calls to one or more databases to retrieve the details associated with the first physical server further defines the one or more databases as including as a configuration management database and the details associated with the first physical server as including one or more support groups that manage one or more of (i) the first physical server, (ii) a hardware component related to the hardware failure, and (iii) a software application related to the software failure.

16 . The computer program product of claim 13 , wherein the sets of codes further comprise a set of codes for causing the one or more computing devices to: initiate a health check on the plurality of impacted virtual machine servers by pinging each of the plurality of impacted virtual machine servers and receiving a response to the ping as an indication that a corresponding impacted virtual machine server has recovered to a powered-on state after migrating to another server in the corresponding cluster.

17 . The computer program product of claim 13 , wherein the sets of codes further comprise a set of codes for causing the one or more computing devices to: identify a functional environment for each of the one or more applications executing on each impacted virtual machine server and details surrounding the functional environment.

Assignments (1)

Continuity (1)

References Cited (32)