IP Library › Granted Patent US 12,493,511
Granted Patent B2
US 12,493,511 · App. 18/596,226 · Granted Dec 9, 2025

Co-tenant alert apparatus, system, and method

Inventors: Gary D. Cudak (Raleigh, NC); Pravin S. Patel (Cary, NC); James Parsonese (Cary, NC); Michael J. Biersack (Cary, NC); Mehul Shah (Austin, TX)
Assignee: Lenovo Enterprise Solutions (Singapore) Pte. Ltd.
G06F11/0784G06F11/0712G06F11/0793
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,493,511
App. No.
18/596,226
Granted
Dec 9, 2025
Kind
B2
Abstract

A method is disclosed for alerting a co-tenant of a fault in a partitioned system. An apparatus and system also perform the functions of the method. The method includes monitoring, for faults, two or more partitions in a system sharing a management controller where each of the partitions is associated with a tenant. The method includes detecting a fault on a first partition and identifying an alert class of multiple alert classes for the fault. The method includes identifying the alert class of the fault as a high-level alert class indicating that the fault affects one or more other partitions different than the first partition. The method includes notifying the tenant of the first partition and each tenant of the one or more other partitions of the fault in response to the alert class being the high-level alert class.

Claims (43)

1 . A method comprising:

monitoring, for faults, each of two or more partitions in a system sharing a management controller, wherein each of the two or more partitions is associated with a tenant;

detecting a fault on a first partition of the two or more partitions;

identifying an alert class of a plurality of alert classes for the fault;

identifying that the alert class of the fault is a high-level alert class, the high-level alert class indicating that the fault affects one or more other partitions of the two or more partitions different than the first partition; and

notifying the tenant of the first partition and each tenant of the one or more other partitions of the fault in response to the alert class being the high-level alert class.

2 . The method of claim 1 , wherein the high-level alert class comprises a plurality of sub-classes, wherein each sub-class of the plurality of sub-classes is related to a response time within which a remediation action must be performed, and further comprising identifying an alert sub-class corresponding to the fault in response to identifying that the alert class of the fault is a high-level alert class.

3 . The method of claim 2 , further comprising determining, based on the identified alert sub-class, a remediation action to be performed and/or timing of the remediation action.

4 . The method of claim 3 , wherein the remediation action comprises, for the first partition and the one or more other partitions, moving data, shedding load, refusing critical loads, and redirecting new data to a non-shared drive.

5 . The method of claim 3 , further comprising, based on the identified sub-class, immediately performing, at the first partition and/or the one or more other partitions, the remediation action associated with the sub-class.

6 . The method of claim 3 , further comprising, based on the identified sub-class, scheduling, at the first partition and/or the one or more other partitions, the remediation action associated with the sub-class for a future time.

7 . The method of claim 6 , wherein in response to the identified alert class comprising the sub-class for scheduling the remediation action at a future time and in response to detecting a second fault with an identified alert class comprising a high-level alert class, further comprising changing the scheduled remediation to an earlier time.

8 . The method of claim 1 , further comprising building a map of hardware components related to more than one of the two or more partitions, wherein identifying the alert class of the plurality of alert classes for the fault and identifying that the alert class is a high-level alert class further comprises accessing information from the map to determine if a component related to the fault is related to more than one of the two or more partitions.

9 . The method of claim 1 , wherein notifying the tenants of the one or more other partitions comprises communicating, over a management network, the fault to the tenants of the one or more other partitions via the management controller.

10 . The method of claim 9 , wherein the management controller communicates with the tenants of the one or more other partitions via one of two or more sockets of a common motherboard.

11 . An apparatus comprising:

one or more processors; and

non-transitory computer readable storage media storing code, the code being executable by the one or more processors to perform operations comprising:

monitoring, for faults, each of two or more partitions in a system sharing a management controller, wherein each of the two or more partitions is associated with a tenant;

detecting a fault on a first partition of the two or more partitions;

identifying an alert class of a plurality of alert classes for the fault;

identifying that the alert class of the fault is a high-level alert class, the high-level alert class indicating that the fault affects one or more other partitions of the two or more partitions different than the first partition; and

notifying the tenant of the first partition and each tenant of the one or more other partitions of the fault in response to the alert class being a high-level alert class.

12 . The apparatus of claim 11 , wherein the high-level alert class comprises a plurality of sub-classes, wherein each sub-class of the plurality of sub-classes related to a response time within which a remediation action must be performed, and further comprising identifying an alert sub-class corresponding to the fault in response to identifying that the alert class of the fault is a high-level alert class.

13 . The apparatus of claim 12 , further comprising determining, based on the identified alert sub-class, a remediation action to be performed and/or timing of the remediation action.

14 . The apparatus of claim 13 , further comprising, based on the identified sub-class, one of:

immediately performing, at the first partition and/or the one or more other partitions, the remediation action associated with the sub-class; and

scheduling, at the first partition and/or the one or more other partitions, the remediation action associated with the sub-class for a future time.

15 . The apparatus of claim 14 , wherein in response to the identified alert class comprising the sub-class for scheduling the remediation action at a future time and in response to detecting a second fault with an identified alert class comprising a high-level alert class, further comprising changing the scheduled remediation to an earlier time.

16 . The apparatus of claim 11 , further comprising building a map of hardware components related to more than one of the two or more partitions, wherein identifying the alert class of the plurality of alert classes for the fault and identifying that the alert class is a high-level alert class further comprises accessing information from the map to determine if a component related to the fault is related to more than one of the two or more partitions.

17 . The apparatus of claim 11 , wherein notifying the tenants of the one or more other partitions comprises communicating, over a management network, the fault to the tenants of the one or more other partitions via the management controller.

18 . A system comprising:

a partitionable motherboard with two or more partitions;

a management controller configured to communicate with the two or more partitions, the management controller connected to tenants of the two or more partitions over a management network;

one or more processors on the management controller; and

non-transitory computer readable storage media storing code, the code being executable by the one or more processors to perform operations comprising:

monitoring, for faults, each of two or more partitions in a system sharing a management controller, wherein each of the two or more partitions is associated with a tenant;

detecting a fault on a first partition of the two or more partitions;

identifying an alert class of a plurality of alert classes for the fault;

identifying that the alert class of the fault is a high-level alert class, the high-level alert class indicating that the fault affects one or more other partitions of the two or more partitions different than the first partition; and

notifying the tenant of the first partition and each tenant of the one or more other partitions of the fault in response to the alert class being a high-level alert class.

19 . The system of claim 18 , wherein the high level alert class comprises a plurality of sub-classes, wherein each sub-class of the plurality of sub-classes related to a response time within which a remediation action must be performed, and further comprising identifying an alert sub-class corresponding to the fault in response to identifying that the alert class of the fault is a high level alert class.

20 . The system of claim 19 , further comprising determining, based on the identified alert sub-class, a remediation action to be performed and/or timing of the remediation action.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 8, 2024
From: LENOVO GLOBAL TECHNOLOGY (UNITED STATES) INC.
To: LENOVO ENTERPRISE SOLUTIONS (SINGAPORE) PTE LTD.
Reel/Frame 067929/0952 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 14, 2024
From: CUDAK, GARY D.; PATEL, PRAVIN S.; PARSONESE, JAMES; BIERSACK, MICHAEL J.; SHAH, MEHUL
To: LENOVO GLOBAL TECHNOLOGY (UNITED STATES) INC.
Reel/Frame 066779/0488 →
Continuity (1)
Related Publication 20250284580A1 · Sep 11, 2025
References Cited (5)
US 20030056155A1 · Austen · 2003 [cited by examiner]
US 20100011257A1 · Murakami · 2010 [cited by examiner]
US 20110154128A1 · Rajkumari · 2011 [cited by examiner]
US 20130152082A1 · Ahrens · 2013 [cited by examiner]
US 20230004432A1 · Wilding · 2023 [cited by examiner]