# US 2021/0279112 A1 · Intelligent system to prioritize servers for envisaged requests

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0279112 A1
- Document ID: US20210279112A1
- Status: Published application
- Kind: A1
- Application number: 16/812,897
- Filed: 2020-03-09
- Published: 2021-09-09
- Earliest claimed: 2020-03-09
- Assignees: EMC IP Holding Company LLC
- Applicants: Emc IP Holding Company LLC
- Inventors: Tamilarasan Janakiraman; Kannan Subbaraman; Sivaram Selvam; Mark Arakelian; Debra Robitaille
- Web page: https://patentgrep.com/patent/US20210279112A1

## CPC

- H04L 43/0817: by checking functioning
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5038: {considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups)}
- G06F 9/505: {considering the load}
- G06F 9/5083: {Techniques for rebalancing the load in a distributed system}
- H04L 41/069: using logs of notifications; Post-processing of notifications
- H04L 41/5016: {based on statistics of service availability, e.g. in percentage or over a given time}
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 67/1029: using data related to the state of servers by a load balancer
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A workload manager uses on-band and off-band metrics to select a host server in a cluster to handle a connection request. The on-band metrics include CPU usage, memory usage, and vulnerability metrics. The off-band metrics include hardware component error logs. Utilization and vulnerability scores are calculated for each host server from the on-band metrics. A reliability score is calculated for each host server from the off-band metrics. A health score for each host server is calculated from the vulnerability and reliability scores. The health score is used to exclude unhealthy host servers from consideration. A priority score is calculated for each host server from the utilization, vulnerability, and reliability scores. The host server that has not been excluded and has the greatest priority score is selected to handle the connection request.

## Claims

### Claim 1

An apparatus comprising:
a load balancer comprising:
a processor;
memory; and
a workload manager that collects on-band metrics and off-band metrics from each of a plurality of host servers of a cluster, calculates at least one score for each of the host servers based on the on-band metrics and off-band metrics collected from that host servers, and assigns a connection request to a selected one of the host servers based on a comparison of the scores of the host servers.

### Claim 2 (depends on 1)

The apparatus of claim 1 wherein the on-band metrics comprise CPU usage, memory usage, and vulnerability metrics.

### Claim 3 (depends on 2)

The apparatus of claim 2 wherein the off-band metrics comprise hardware component error logs.

### Claim 4 (depends on 3)

The apparatus of claim 3 wherein the workload manager calculates a utilization score for each of the host servers based on CPU usage and memory usage.

### Claim 5 (depends on 4)

The apparatus of claim 4 wherein the workload manager calculates a vulnerability score for each of the host servers based on the vulnerability metrics using a cumulative common vulnerability scoring system.

### Claim 6 (depends on 5)

The apparatus of claim 5 wherein the workload manager calculates a reliability score for each of the host servers based on relative number of critical errors as indicated in the logs.

### Claim 7 (depends on 6)

The apparatus of claim 6 wherein the workload manager calculates a health score for each of the host servers based on the vulnerability score and the reliability score.

### Claim 8 (depends on 7)

The apparatus of claim 7 wherein the workload manager calculates a priority score for each of the host servers based on the vulnerability score and the utilization score.

### Claim 9 (depends on 8)

The apparatus of claim 8 wherein the workload manager excludes from consideration ones of the host servers based on the health scores.

### Claim 10 (depends on 8)

The apparatus of claim 8 wherein the workload manager assigns the connection request to the host server based on the priority scores.

### Claim 11

A method comprising:
collecting on-band metrics and off-band metrics from each of a plurality of host servers of a cluster;
calculating at least one score for each of the host servers based on the on-band metrics and off-band metrics collected from that host servers; and
assigning a connection request to a selected one of the host servers based on a comparison of the scores of the host servers.

### Claim 12 (depends on 11)

The method of claim 11 wherein the on-band metrics comprise CPU usage, memory usage, and vulnerability metrics, and comprising calculating a utilization score for each of the host servers based on CPU usage and memory usage.

### Claim 13 (depends on 12)

The method of claim 12 comprising calculating a vulnerability score for each of the host servers based on the vulnerability metrics using a cumulative common vulnerability scoring system.

### Claim 14 (depends on 13)

The method of claim 13 wherein the off-band metrics comprise hardware component error logs and comprising calculating a reliability score for each of the host servers based on relative number of critical errors as indicated in the logs.

### Claim 15 (depends on 14)

The method of claim 14 comprising calculating a health score for each of the host servers based on the vulnerability score and the reliability score.

### Claim 16 (depends on 15)

The method of claim 15 comprising calculating a priority score for each of the host servers based on the vulnerability score and the utilization score.

### Claim 17 (depends on 16)

The method of claim 16 comprising excluding from consideration ones of the host servers based on the health scores.

### Claim 18 (depends on 16)

The method of claim 16 comprising assigning the connection request to the host server based on the priority scores.

### Claim 19

A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for using a computer system to assign a connection request to a selected host server in a cluster of host servers, the method comprising:
collecting on-band metrics from each host server of the cluster, wherein the on-band metrics comprise CPU usage, memory usage, and vulnerability metrics;
collecting off-band metrics from each host server of the cluster, wherein the off-band metrics comprise hardware component error logs;
calculating a utilization score for each of the host servers based on CPU usage and memory usage;
calculating a vulnerability score for each of the host servers based on the vulnerability metrics using a cumulative common vulnerability scoring system;
calculating a priority score for each of the host servers based on the vulnerability score and the utilization score; and
selecting the host server to which the connection request is assigned based on the priority scores.

### Claim 20 (depends on 19)

The non-transitory computer-readable storage medium of claim 19 wherein the method further comprises calculating a reliability score for each of the host servers based on relative number of critical errors as indicated in the logs, calculating a health score for each of the host servers based on the vulnerability score and the reliability score, and excluding from consideration ones of the host servers based on the health scores.
