[go: up one dir, main page]

WO2019175631A1 - Passive centralised health check manager - Google Patents

Passive centralised health check manager Download PDF

Info

Publication number
WO2019175631A1
WO2019175631A1 PCT/IB2018/051718 IB2018051718W WO2019175631A1 WO 2019175631 A1 WO2019175631 A1 WO 2019175631A1 IB 2018051718 W IB2018051718 W IB 2018051718W WO 2019175631 A1 WO2019175631 A1 WO 2019175631A1
Authority
WO
WIPO (PCT)
Prior art keywords
manager
cluster
health check
centralised
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IB2018/051718
Other languages
French (fr)
Inventor
Pratik Sharma
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to PCT/IB2018/051718 priority Critical patent/WO2019175631A1/en
Publication of WO2019175631A1 publication Critical patent/WO2019175631A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/301—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is a virtual computing platform, e.g. logically partitioned systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/164—Adaptation or special uses of UDP protocol
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
    • G06F11/3082—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting the data filtering being achieved by aggregating or compressing the monitored data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G06F11/3419—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment by assessing time
    • G06F11/3423—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment by assessing time where the assessed time is active or idle time

Definitions

  • Node Manager is the first virtual machine node to boot up in the cluster.
  • Other virtual machine nodes in the cluster on boot up, running different system and software services establish User Datagram Protocol (UDP) connection with the Centralised Health Check Manager running on the Node Manager in the cluster.
  • UDP User Datagram Protocol
  • each of the other virtual machine nodes in the cluster (except for the Node Manager) will periodically send to the Centralised Health Check Manager running on the Node Manager detailed Health Check Object of the format consisting of Central Processing Unit Load, Idle time for Central Processing Unit, Memory Usage and then in order of software stack running on the virtual node for each software or service we will include service identifier, changed service attributes that were being monitored and current health parameters for the service.
  • Centralised Health Check Manager running on Node Manager is passive in nature in the sense that it does not send anything to the other virtual machine nodes in the cluster, rather just keeps aggregating health information from other virtual machine nodes in the cluster.
  • Node Manager here can be a light weight virtual machine just for passive health checks in the cluster or it can be a virtual machine with comparable resources to other virtual machines in the cluster but in that case the Centralised Health Check Manager software module will collect health check information from the Node Manager too may be through a Unix Domain socket. If the Centralised Health Check Manager does not get any health information from a particular virtual machine node in the cluster for fixed number of consecutive cycles it assumes that the virtual machine is down. Also Centralised Health Check Manager will have one or more backup software modules running on different virtual machines which are periodically updated by the Node Manager. Likewise if the backed up versions of Centralised Health Check Manager software module do not get any health information of the cluster from the Node Manager for a consecutive set of cycles then one of the virtual machines running the backed up version of
  • Centralised Health Check Manager becomes the Node Manager and the other virtual machines in the cluster will form a User Datagram Protocol (UDP) connection with it to send Health Check Object.
  • UDP User Datagram Protocol

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mathematical Physics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Debugging And Monitoring (AREA)

Abstract

Here we have a Centralised Health Check Manager running on one of the virtual machine nodes in the cluster called Node Manager. Node Manager is the first virtual machine node to boot up in the cluster. Other virtual machine nodes in the cluster on boot up, running different system and software services establish UDP connection with the Centralised Health Check Manager. Then each of the other virtual machine nodes in the cluster (except for the Node Manager) will periodically send to the Centralised Health Check Manager running on the Node Manager detailed Health Check Object of the format consisting of Central Processing Unit Load, Idle time for Central Processing Unit, Memory Usage and then in order of software stack running on the virtual node for each software or service we will include service identifier, changed service attributes that were being monitored and current health parameters for the service.

Description

Passive Centralised Health Check Manager
In this invention we have a Centralised Health Check Manager running on one of the virtual machine nodes in the cluster called Node Manager. Node Manager is the first virtual machine node to boot up in the cluster. Other virtual machine nodes in the cluster on boot up, running different system and software services establish User Datagram Protocol (UDP) connection with the Centralised Health Check Manager running on the Node Manager in the cluster. Then each of the other virtual machine nodes in the cluster (except for the Node Manager) will periodically send to the Centralised Health Check Manager running on the Node Manager detailed Health Check Object of the format consisting of Central Processing Unit Load, Idle time for Central Processing Unit, Memory Usage and then in order of software stack running on the virtual node for each software or service we will include service identifier, changed service attributes that were being monitored and current health parameters for the service. Centralised Health Check Manager running on Node Manager is passive in nature in the sense that it does not send anything to the other virtual machine nodes in the cluster, rather just keeps aggregating health information from other virtual machine nodes in the cluster. Node Manager here can be a light weight virtual machine just for passive health checks in the cluster or it can be a virtual machine with comparable resources to other virtual machines in the cluster but in that case the Centralised Health Check Manager software module will collect health check information from the Node Manager too may be through a Unix Domain socket. If the Centralised Health Check Manager does not get any health information from a particular virtual machine node in the cluster for fixed number of consecutive cycles it assumes that the virtual machine is down. Also Centralised Health Check Manager will have one or more backup software modules running on different virtual machines which are periodically updated by the Node Manager. Likewise if the backed up versions of Centralised Health Check Manager software module do not get any health information of the cluster from the Node Manager for a consecutive set of cycles then one of the virtual machines running the backed up version of
Centralised Health Check Manager becomes the Node Manager and the other virtual machines in the cluster will form a User Datagram Protocol (UDP) connection with it to send Health Check Object.

Claims

Claims Following is the claim for this invention: -
1 . In this invention we have a Centralised Health Check Manager running on one of the virtual machine nodes in the cluster called Node Manager. Node Manager is the first virtual machine node to boot up in the cluster. Other virtual machine nodes in the cluster on boot up, running different system and software services establish User Datagram Protocol (UDP) connection with the Centralised Health Check Manager running on the Node Manager in the cluster. Then each of the other virtual machine nodes in the cluster (except for the Node Manager) will periodically send to the Centralised Health Check Manager running on the Node Manager detailed Health Check Object of the format consisting of Central
Processing Unit Load, Idle time for Central Processing Unit, Memory Usage and then in order of software stack running on the virtual node for each software or service we will include service identifier, changed service attributes that were being monitored and current health parameters for the service. Centralised Health Check Manager running on Node Manager is passive in nature in the sense that it does not send anything to the other virtual machine nodes in the cluster, rather just keeps aggregating health information from other virtual machine nodes in the cluster. Node Manager here can be a light weight virtual machine just for passive health checks in the cluster or it can be a virtual machine with comparable resources to other virtual machines in the cluster but in that case the Centralised Health Check Manager software module will collect health check information from the Node Manager too may be through a Unix Domain socket. If the
Centralised Health Check Manager does not get any health information from a particular virtual machine node in the cluster for fixed number of consecutive cycles it assumes that the virtual machine is down. Also Centralised Health Check Manager will have one or more backup software modules running on different virtual machines which are periodically updated by the Node Manager. Likewise if the backed up versions of Centralised Health Check Manager software module do not get any health information of the cluster from the Node Manager for a consecutive set of cycles then one of the virtual machines running the backed up version of Centralised Health Check Manager becomes the Node Manager and the other virtual machines in the cluster will form a User Datagram Protocol (UDP) connection with it to send Health Check Object. The above novel technique of providing a passive centralised health check mechanism is the claim for this invention.
PCT/IB2018/051718 2018-03-14 2018-03-14 Passive centralised health check manager Ceased WO2019175631A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2018/051718 WO2019175631A1 (en) 2018-03-14 2018-03-14 Passive centralised health check manager

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2018/051718 WO2019175631A1 (en) 2018-03-14 2018-03-14 Passive centralised health check manager

Publications (1)

Publication Number Publication Date
WO2019175631A1 true WO2019175631A1 (en) 2019-09-19

Family

ID=67907447

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2018/051718 Ceased WO2019175631A1 (en) 2018-03-14 2018-03-14 Passive centralised health check manager

Country Status (1)

Country Link
WO (1) WO2019175631A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887185A (en) * 2019-11-29 2021-06-01 华为技术有限公司 Communication method and device of overlay network

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002037224A2 (en) * 2000-11-02 2002-05-10 Pirus Networks Load balanced storage system
US6816905B1 (en) * 2000-11-10 2004-11-09 Galactic Computing Corporation Bvi/Bc Method and system for providing dynamic hosted service management across disparate accounts/sites

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002037224A2 (en) * 2000-11-02 2002-05-10 Pirus Networks Load balanced storage system
US6816905B1 (en) * 2000-11-10 2004-11-09 Galactic Computing Corporation Bvi/Bc Method and system for providing dynamic hosted service management across disparate accounts/sites

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112887185A (en) * 2019-11-29 2021-06-01 华为技术有限公司 Communication method and device of overlay network
CN112887185B (en) * 2019-11-29 2024-03-15 华为云计算技术有限公司 Communication method and device of overlay network

Similar Documents

Publication Publication Date Title
US10862760B2 (en) Network functions virtualization
US11706102B2 (en) Dynamically deployable self configuring distributed network management system
EP2335162B1 (en) Dynamic distribution of virtual machines in a communication network
EP2989545B1 (en) Defining interdependent virtualized network functions for service level orchestration
US20190373052A1 (en) Aggregation of scalable network flow events
US20160344582A1 (en) Call home cluster
US20150331777A1 (en) System and method of generating data center alarms for missing events
US9960964B2 (en) System, method and apparatus to manage services in a network
CN110266822B (en) Shared load balancing implementation method based on nginx
CN107231399A (en) The expansion method and device of High Availabitity server cluster
TW201423398A (en) Method and system for analyzing root causes of relating performance issues among virtual machines to physical machines
CN106294713A (en) The method of data synchronization resolved based on Incremental Log and data synchronization unit
US9026632B2 (en) Network with a network wide extended policy framework
CN105165054A (en) Network service troubleshooting method, service management system and system management module
CN104935672A (en) High available realizing method and equipment of load balancing service
US10530669B2 (en) Network service aware routers, and applications thereof
CN104618521A (en) Node de-duplication in a network monitoring system
CN105847352B (en) Expansion method, device and distributed cache system based on distributed cache system
CN112231123A (en) Message processing method, device, storage medium and electronic device
CN117492944A (en) Task scheduling method and device, electronic equipment and readable storage medium
CN105656661B (en) A software management method and system for a single board
CN106385330B (en) Implementation method and device of a network function virtualization orchestrator
CN102437921B (en) Memory method and network device of configuration information
CN112953982A (en) Service processing method, service configuration method and related device
WO2019175631A1 (en) Passive centralised health check manager

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18909869

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18909869

Country of ref document: EP

Kind code of ref document: A1