Network equipment monitoring and early warning method and device of data center, electronic equipment and storage medium

Abstract

The invention discloses a network equipment monitoring and early warning method and device for a data center, electronic equipment and a storage medium, and the method comprises the steps: collecting the port information of network equipment deployed in the data center, and enabling the port information to at least comprise a port type; maintaining the port category and establishing a corresponding matching relationship with a pre-configured early warning rule, wherein the early warning rule can be unbound or bound with the port category; and monitoring the state of the port information based on the early warning rule, and generating early warning information. According to the invention, on one hand, automatic monitoring and early warning of massive ports of network equipment in a data center are realized, and on the other hand, flexible configuration of early warning rules is realized.

Description

Technical Field

[0001] The present application relates to the technical field of intelligent analysis and early warning of network equipment, and in particular to a network equipment monitoring and early warning method, device, electronic equipment, and storage medium for a data center. Background Art

[0002] With the increasing number of system operation and maintenance tasks in data centers, monitoring of network devices becomes particularly important. Network devices include but are not limited to switches, routers, etc.

[0003] The monitoring method for network devices in related technologies is mainly based on selecting network device ports for configuration monitoring. This method may be feasible when the number of device ports is small, but as the number of device ports increases sharply, a lot of manual maintenance work is required, which is not only heavy, but also prone to monitoring omissions. This not only increases the workload of operation and maintenance personnel, but also poses a potential threat to the overall operation safety of the data center. Furthermore, after an alarm occurs, since there is no intuitive information about the port connection device, the operation and maintenance personnel often need to spend a lot of time troubleshooting, which not only prolongs the time for fault recovery, but also may have a serious impact on business continuity. Summary of the invention

[0004] The embodiments of the present application provide a data center network equipment monitoring and early warning method, device, electronic device, and storage medium to achieve automated monitoring and early warning of massive ports of network equipment in the data center.

[0005] The present application embodiment adopts the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a network device monitoring and early warning method for a data center, wherein the method comprises:

[0007] Collecting port information of network devices deployed in the data center, where the port information at least includes port categories;

[0008] Maintaining the port category and establishing a corresponding matching relationship with a pre-configured warning rule, wherein the warning rule can be unbound or bound to the port category;

[0009] The status of the port information is monitored based on the warning rule, and warning information is generated.

[0010] In some embodiments, collecting port information of network devices deployed in the data center includes:

[0011] Acquire the port information of the network device, wherein the port information further includes one of the following: port name, bandwidth, inbound and outbound rate, and inbound and outbound bandwidth usage;

[0012] Identify whether the port category belongs to a downlink server interface or a non-downlink server interface, the downlink server interface is used to characterize an operating system type resource connected to the port, and the non-downlink server interface is used to characterize a non-operating system type.

[0013] In some embodiments, maintaining the port category and establishing a corresponding matching relationship with a pre-configured warning rule includes:

[0014] According to the next hop IP address of the ARP table carried by the network device, query the CMDB for resources corresponding to the matching port category;

[0015] If the query matching result is matched, it is used as the downlink server interface, and the downlink type field of the network port CMDB of the port category is refilled as the downlink server interface, and the information of the port category associated resources is refilled into the network port downlink information field;

[0016] If the query result is no match, the IP information of the hardware device is retrieved;

[0017] If a match is found, it will be used as a non-downlink server interface.

[0018] In some embodiments, maintaining the port category and establishing a corresponding matching relationship with a pre-configured warning rule includes:

[0019] If a change in the port category is detected, identifying the changed port category in response to a change result of the ARP table carried by the network device;

[0020] If it is a downstream server port, the changed port category information is maintained in the CMDB and the current port is rebound to the warning rule of the downstream server port.

[0021] In some embodiments, the monitoring the status of the port information based on the warning rule and generating the warning information includes:

[0022] The warning rules are configured to set warning rules and warning levels according to indicators in the port information of the network device, and store them in a relational database;

[0023] In response to the identification result of the port category in the port information, binding a corresponding threshold policy according to the port category;

[0024] The binding relationship of the changed threshold policy is pushed to a rule message queue, and the rule message queue is consumed by the warning rule in the Spark engine to monitor the network port of the network device according to the port category.

[0025] In some embodiments, the monitoring the status of the port information based on the warning rule and generating warning information further includes:

[0026] Push the collected network port indicator information of the network device to the message queue, consume the indicator data from the message queue through the Spark engine, and write the indicator data into the ES database;

[0027] The Spark engine job consumes the port indicator information of the message queue for analysis and calculation. If the indicator meets the configured warning rules, an alert is generated.

[0028] In some embodiments, the method further comprises:

[0029] According to the network device, the port information is displayed on the front-end page;

[0030] According to the port category, the downstream resources and the system to which the network device port belongs are displayed on the front-end page, supporting click-to-jump to any one or more monitoring information in the downstream resources.

[0031] In a second aspect, an embodiment of the present application further provides a network equipment monitoring and early warning device for a data center, wherein the device comprises:

[0032] A collection module, used to collect port information of network devices deployed in the data center, wherein the port information at least includes a port category;

[0033] A maintenance module, used to maintain the port category and establish a corresponding matching relationship with a pre-configured warning rule, wherein the warning rule can be unbound or bound to the port category;

[0034] A generating module is used to monitor the status of the port information based on the warning rule and generate warning information.

[0035] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor; and a memory arranged to store computer executable instructions, wherein the executable instructions, when executed, cause the processor to perform the above method.

[0036] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple application programs, the electronic device executes the above method.

[0037] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: by collecting the port information of the network equipment deployed in the data center, since the port information includes the port category, the relevant early warning rules can be matched by identifying the port category. Then the port category is maintained and a corresponding matching relationship is established with the pre-configured early warning rules. Since the early warning rules can be unbound or bound to the port category, the flexible configuration of the early warning rules is improved. Finally, the status of the port information is monitored based on the early warning rules, and early warning information is generated. Through the above method, intelligent analysis and early warning are realized based on the port category, so that the risk of failure can be warned in time, and the problem can be quickly located, thereby improving the stability of the business operation of the data center. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0039] Figure 1 A flowchart of a method for monitoring and early warning of network equipment in a data center according to an embodiment of the present application;

[0040] Figure 2 This is a schematic diagram of the structure of a network equipment monitoring and early warning device for a data center in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of a specific process of a network device monitoring and early warning method for a data center in an embodiment of the present application;

[0042] Figure 4 It is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0044] The port monitoring method of network devices in the data center is to monitor through port configuration policies, which requires manual maintenance of configuration information of hundreds of thousands of ports, which is costly and prone to errors. Because the network ports connected to different types of devices need to be configured with different alarm thresholds.

[0045] In view of the above-mentioned deficiencies, a configurable and automated implementation scheme is adopted in the embodiment of the present application to realize intelligent analysis and warning based on port category, by automatically determining the port category and configuring intelligent analysis and warning according to the warning threshold.

[0046] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0047] The present application embodiment provides a data center network equipment monitoring and early warning method, such as Figure 1 As shown, a flowchart of a method for monitoring and warning network equipment in a data center according to an embodiment of the present application is provided, wherein the method at least includes the following steps S110 to S130:

[0048] Step S110, collect port information of network devices deployed in the data center, the port information at least includes port category. When collecting port information, it is also used to periodically obtain port name, bandwidth, in / out rate, in / out bandwidth usage information, etc., which is not specifically limited in the embodiments of the present application.

[0049] A data center is a physical facility that is used to centrally store, manage, and operate a large number of information technology hardware devices, network devices, storage systems, and related components. In particular, data is collected from the network devices in the data center to obtain port information of the network devices. The specific collection function is divided into two types of data: one is basic port information, including but not limited to port name, category, and bandwidth. The other is indicator information, including but not limited to rate, bandwidth usage, packet loss, etc.

[0050] In an embodiment of the present application, the port information includes a port category, based on which an alarm rule associated with the port category can be determined, and subsequent monitoring alarms can be further implemented according to the prediction rule.

[0051] Step S120: Maintain the port category and establish a corresponding matching relationship with a pre-configured warning rule. The warning rule can be bound or unbound from the port category.

[0052] By maintaining the port category and establishing a corresponding matching relationship with the warning rules, after identifying the port category, it can be automatically bound according to the configured port category threshold policy. The maintenance of the port category includes but is not limited to adding ports, reducing ports, adding links, etc.

[0053] By establishing a corresponding matching relationship between the port category and the pre-configured warning rules, you can get the configuration results and start the monitoring process.

[0054] It should be noted that the warning rule implements warning monitoring by binding the port category, and the warning rule is re-matched or deployed by unbinding from the port category.

[0055] Step S130: monitor the status of the port information based on the warning rule and generate warning information.

[0056] The status of all port information is monitored through the warning rules, and warning information is generated according to abnormal conditions of status changes.

[0057] Through the above method, by maintaining the port category and establishing a corresponding matching relationship with the pre-configured warning rules, the network device port indicators are automatically managed and monitored.

[0058] Through the above method, the port information of the network equipment deployed in the data center is collected, and the port information at least includes the port category. The port category is maintained and a corresponding matching relationship is established with the pre-configured warning rules. The warning rules can be unbound or bound to the port category. When setting the warning rules, they can be set according to the port category. Therefore, when the port association relationship changes and causes the port category to change, the warning rules can be automatically bound incrementally, and a warning can be generated according to the set warning rules without manual maintenance.

[0059] Different from the related technologies, most monitoring methods are based on manually selecting network device ports for configuration monitoring. As the number of device ports increases, the workload required for manual maintenance also increases, and it is easy to have problems such as missed monitoring. Through the above method, intelligent analysis and early warning based on port categories are realized, the status of the port information is monitored based on the early warning rules, and early warning information is generated to perform intelligent analysis and early warning according to port categories. In addition, the association relationship of network devices can be intuitively displayed, which improves the timeliness of port early warning in the data center and saves time for troubleshooting.

[0060] In one embodiment of the present application, the port information of the network equipment deployed in the data center is collected, including: obtaining the port information of the network equipment, the port information also including one of the following: port name, bandwidth, input and output rate, input and output bandwidth utilization rate; identifying whether the port category belongs to a downstream server interface or a non-downstream server interface, the downstream server interface is used to characterize the operating system type resource connected to the port, and the non-downstream server interface is used to characterize the non-operating system type.

[0061] like Figure 3 As shown in the figure, in the monitoring system of the data center, the network equipment port is monitored, and the indicators such as port on / off status, in / out rate, in / out bandwidth usage rate are collected, and the warning is issued according to the specified warning rules.

[0062] It should be noted that in the monitoring system of the data center, the monitoring of the network device ports not only obtains the port on / off status, input and output rates, input and output bandwidth usage and other indicators of the network device, but also automatically identifies whether the port category belongs to a downstream server interface or a non-downstream server interface.

[0063] It should be noted that when the threshold rules that automatically identify the port category and automatically bind do not meet the actual production needs, you can also manually set custom threshold rules and control the threshold rules for port binding by adjusting the priority.

[0064] When identifying whether the port category belongs to a downlink server interface or a non-downlink server interface, the following method may be specifically adopted:

[0065] If it is an operating system type resource such as Linux, it can be used as a downlink server interface. If it is a non-operating system type resource, it can be used as a non-downlink server interface. If the Linux network port card information is identified through the next-hop IP address in the APR table, the corresponding network port associated resource is Linux. In other words, when the port category is divided according to the peer resource information connected to the port, the IP corresponding to the port is based on the port name in the APR table of the network device. That is, the message corresponding to the IP of the port is forwarded by this port, so it is considered that the port and this IP resource have a connection relationship.

[0066] In addition, the port category can also be expanded according to the actual situation. If the name of the downstream server resource contains names such as "cloud, cluster", it is a cloud server or cluster server category.

[0067] It can be understood that a downlink server refers to a server connected to the downstream port of a switch in a network architecture. This configuration is usually used to implement network resource management and data transmission. Taking the network device as an interactive machine as an example, a downlink server means that this port of the network device is connected to a server, and the application system is deployed on the server. A non-downlink server means that this port is connected to a switch, router, or other device.

[0068] Considering that the downstream server is the core node of the network, it processes and responds to requests from clients, ensures the availability and stability of network services, and is responsible for storing most of the data and information on the network. The data processing capability directly affects the quality of network services. Therefore, it is necessary to monitor and warn the downstream servers of network equipment to ensure the quality of network services.

[0069] In one embodiment of the present application, the maintaining of the port category and establishing a corresponding matching relationship with the pre-configured warning rules include: according to the IP address corresponding to the port in the ARP table carried by the network device, querying the CMDB for the resources corresponding to the IP corresponding to the port; when the query matching result is that the operating system resources have been matched, it is used as a downlink server interface, and at the same time, the downlink type field of the network port CMDB of the port category is refilled as the downlink server interface, and the information of the port category-associated resources is refilled into the network port downlink information field; when the query matching result is no match, the IP information of the hardware device is retrieved; if there is a match, it is used as a non-downlink server interface.

[0070] In the embodiments of the present application, "port" refers to a port of a network device, which can be divided into a virtual port and a physical port. "CMDB" refers to a data center configuration management library, which is used to maintain and manage configuration item data and relationship data.

[0071] like Figure 3 As shown, the port category is identified by identifying the type of device connected to its port according to the ARP table of the network device, the IP connected to the port is obtained through the ARP table of the network device, and the device resource type is obtained by searching from the configuration management database CMDB according to the next-hop IP. If it is an operating system type resource such as Linux, it is a downstream server interface. If it is a non-operating system type resource, it is a non-downstream server interface. The port category can also be expanded according to actual conditions.

[0072] like Figure 3 As shown, the port category is identified based on the type of device connected to its port according to the ARP table of the network device. The IP list of the network card of the operating system needs to be retrieved through the IP connected to the port in the ARP table of the network device. If a match is found, the downlink type field of the network port CMDB is automatically filled in as the downlink server interface, and the name of the associated resource, the system to which it belongs, etc. are filled in the downlink information field of the network port. If no match is found, the IP information of hardware devices such as switches, routers, and storage is retrieved. If a match is found, it is a non-downlink server interface.

[0073] It should be noted that the above query matching scenarios and backfilling field information scenarios are imperceptible to technical personnel, that is, the monitoring and early warning processes are completed automatically.

[0074] In one embodiment of the present application, the maintaining of the port category and establishing a corresponding matching relationship with the pre-configured warning rules include: if a change in the port category is monitored, then in response to the change result of the ARP table carried by the network device, identifying the changed port category; if it is a downstream server port, maintaining the changed port category information in the CMDB and rebinding the current port with the warning rules of the downstream server port.

[0075] like Figure 3 As shown, according to the ARP information, the CMDB is linked to retrieve, the downstream resource information of the network device port is obtained, the port category is determined, and the threshold policy is automatically bound according to the port category. After identifying the port category, it can be automatically bound according to the configured port category threshold policy. At the same time, when the device port information is automatically maintained, the downstream resource type is automatically filled into the network port category information of the CMDB network device according to the downstream device information obtained.

[0076] For example, if the device link relationship changes when the network equipment in the data center is running, and the g1 / 0 / 1 port of the newly added device A is connected to server B, the ARP table will change and the port category function will automatically identify the g1 / 0 / 1 port of the newly added device A as the downstream server port. The CMDB maintains its information and binds the port to the threshold policy of the downstream server port.

[0077] The scenarios corresponding to the above process are:

[0078] When the number of ports collected by data center network equipment exceeds 1 million, more than 500,000 ports need to be monitored and configured with early warning strategies, including 100,000 non-downlink server ports and 400,000 downlink server ports. Threshold rules are configured by category. The threshold strategy of downlink server ports is configured to generate an early warning when the outbound / inbound bandwidth usage exceeds 90%, and the threshold strategy of non-downlink server port categories is configured to generate an early warning when the outbound / inbound bandwidth usage exceeds 70%.

[0079] In one embodiment of the present application, the status of the port information is monitored based on the warning rules to generate warning information, including: the warning rules are configured to set warning rules and warning levels according to indicators in the port information of the network device, and store them in a relational database; in response to the identification result of the port category in the port information, the corresponding threshold policy is bound according to the port category; the binding relationship of the changed threshold policy is pushed to the rule message queue, and the rule message queue is consumed by the warning rules in the Spark engine to monitor the network port of the network device according to the port category.

[0080] The Spark engine is a fast and general-purpose big data analysis and computing engine designed for large-scale data processing. Based on in-memory computing, it significantly improves the real-time performance of data processing in a big data environment while ensuring high fault tolerance and high scalability. The Kafka queue is a distributed message queue based on a publish / subscribe model.

[0081] After identifying the port category, it can be automatically bound according to the configured threshold policy of the port category. When a new connection relationship or a new port is automatically discovered through automatic discovery of the network port, if the port category is configured with a corresponding threshold policy, the port is bound to the corresponding policy, and the newly added policy binding relationship is pushed to the message queue Kafka. The early warning rule analysis job in Spark consumes the rule message queue to realize automatic monitoring of network ports by category.

[0082] In one embodiment of the present application, the status of the port information is monitored based on the warning rules to generate warning information, and also includes: pushing the collected network port indicator information of the network device to the message queue in a certain format, consuming the indicator data from the message queue through the Spark engine, and writing the indicator data to the ES database; consuming the port indicator information of the message queue through the Spark engine job for analysis and calculation, and if the indicator meets the configured warning rules, a warning is generated.

[0083] All network port indicators are written into the Kafka message queue in a certain format, and alarms are issued in Spark according to the bound threshold policy. Considering that the monitoring and early warning requirements are accurate and timely, the characteristics of network device port collection in the data center are large indicators, periodic reporting rates, and periodic peaks. Kafka technology is preferred. When there is a burst of upstream data traffic or insufficient downstream service processing capacity, Kafka can be used as a buffer to help smooth the data flow and prevent the loss of early warnings when the data volume is large. The performance improvement brought by the Spark engine can improve the processing performance of indicator data and ensure the timeliness of early warnings.

[0084] It can be understood that the indicator information includes but is not limited to port rate and port bandwidth usage.

[0085] During early warning monitoring, the port indicator information of the Spark engine job consumption message queue is analyzed and calculated. If the indicator meets the configured early warning rules, an early warning is generated. For example, when the bandwidth usage rate of the collection indicator of port g1 / 0 / 1 of device A reaches 91%, it reaches the threshold and an early warning is issued. Click on the port information of device A to see the name of its downstream device B and the business system it belongs to. Click to view the collection information of device B. Its network card traffic has increased, the problem has been clearly identified, and the corresponding business system is contacted for processing. The corresponding scenarios are:

[0086] When the number of ports collected by data center network equipment exceeds 1 million, more than 500,000 ports need to be monitored and configured with early warning strategies, including 100,000 non-downlink server ports and 400,000 downlink server ports. Threshold rules are configured by category. The threshold strategy of downlink server ports is configured to generate an early warning when the outbound / inbound bandwidth usage exceeds 90%, and the threshold strategy of non-downlink server port categories is configured to generate an early warning when the outbound / inbound bandwidth usage exceeds 70%.

[0087] In one embodiment of the present application, the method also includes: displaying the port information on the front-end page according to the network device; displaying the downstream resources and the system to which the network port of the network device belongs on the front-end page according to the port category, supporting click-to-jump to any one or more monitoring information in the downstream resources.

[0088] In related technologies, when an alarm occurs, the connection information of the port lacks intuitive display, which makes troubleshooting time-consuming. By displaying basic port information and indicator information according to network devices, the maximum value within the selected time can be displayed, which is convenient for troubleshooting. The name of the downstream resource of the network port and the system to which it belongs can be displayed, and you can click to jump to the monitoring information details page of the downstream resource, which is convenient for troubleshooting.

[0089] The embodiment of the present application also provides a network equipment monitoring and early warning device 200 for a data center, such as Figure 2 As shown, a schematic diagram of the structure of a network device monitoring and early warning device for a data center in an embodiment of the present application is provided. The network device monitoring and early warning device 200 for a data center includes at least: a collection module 210, a maintenance module 220 and a generation module 230, wherein:

[0090] In one embodiment of the present application, the collection module 210 is specifically used to collect port information of network devices deployed in the data center, and the port information at least includes a port category.

[0091] A data center is a physical facility that is used to centrally store, manage, and operate a large number of information technology hardware devices, network devices, storage systems, and related components. In particular, network devices in the data center are collected to obtain port information of the network devices.

[0092] The port information includes the port category, based on which the warning rule associated with the port can be determined, and the subsequent monitoring warning can be further implemented according to the prediction rule.

[0093] In one embodiment of the present application, the maintenance module 220 is specifically used to: maintain the port category and establish a corresponding matching relationship with a pre-configured warning rule, and the warning rule can be unbound or bound to the port category.

[0094] By maintaining the port category and establishing a corresponding matching relationship with the warning rules, after identifying the port category, it can be automatically bound according to the configured port category threshold policy. The maintenance of the port category includes but is not limited to adding ports, reducing ports, adding links, etc.

[0095] By establishing a corresponding matching relationship between the port category and the pre-configured warning rules, you can get the configuration results and start the monitoring process.

[0096] It should be noted that the warning rule realizes warning monitoring by binding the port category, and the warning rule is re-matched or deployed by unbinding from the port category.

[0097] In one embodiment of the present application, the generating module 230 is specifically configured to: monitor the status of the port information based on the warning rule and generate warning information.

[0098] The status of all port information is monitored through the warning rules, and warning information is generated according to abnormal conditions of status changes.

[0099] It can be understood that the network equipment monitoring and early warning device of the above-mentioned data center can implement the various steps of the network equipment monitoring and early warning method of the data center provided in the aforementioned embodiments. The relevant explanations about the network equipment monitoring and early warning method of the data center are applicable to the network equipment monitoring and early warning device of the data center, and will not be repeated here.

[0100] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 4 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0101] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0102] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0103] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a network equipment monitoring and early warning device for the data center at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0104] Collecting port information of network devices deployed in the data center, where the port information at least includes port categories;

[0105] Maintaining the port category and establishing a corresponding matching relationship with a pre-configured warning rule, wherein the warning rule can be unbound or bound to the port category;

[0106] The status of the port information is monitored based on the warning rule, and warning information is generated.

[0107] The above application Figure 1The method performed by the transaction reconciliation device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0108] The electronic device may also perform Figure 1 A method for executing a network equipment monitoring and early warning device in a data center, and realizing a network equipment monitoring and early warning device in a data center Figure 1 The functions of the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0109] The present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 1 The method executed by the network equipment monitoring and early warning device of the data center in the embodiment shown is specifically used to execute:

[0110] Collecting port information of network devices deployed in the data center, where the port information at least includes port categories;

[0111] Maintaining the port category and establishing a corresponding matching relationship with a pre-configured warning rule, wherein the warning rule can be unbound or bound to the port category;

[0112] The status of the port information is monitored based on the warning rule, and warning information is generated.

[0113] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0114] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0115] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0116] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0117] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0118] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0119] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0120] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0121] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0122] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data center network equipment monitoring and early warning method, wherein: The method comprises: Collecting port information of network devices deployed in the data center, where the port information at least includes port categories; Maintaining the port category and establishing a corresponding matching relationship with a pre-configured warning rule, wherein the warning rule can be unbound or bound to the port category; The status of the port information is monitored based on the warning rule, and warning information is generated.

2. The method of claim 1, wherein: The collecting of port information of network devices deployed in the data center includes: Acquire the port information of the network device, wherein the port information further includes one of the following: port name, bandwidth, inbound and outbound rate, and inbound and outbound bandwidth usage; Identify whether the port category belongs to a downlink server interface or a non-downlink server interface, the downlink server interface is used to characterize an operating system type resource connected to the port, and the non-downlink server interface is used to characterize a non-operating system type.

3. The method of claim 2, wherein: The maintaining of the port category and establishing a corresponding matching relationship with a pre-configured warning rule includes: According to the next hop IP address of the ARP table carried by the network device, query the CMDB for resources corresponding to the matching port category; If the query matching result is matched, it is used as the downlink server interface, and the downlink type field of the network port CMDB of the port category is refilled as the downlink server interface, and the information of the port category associated resources is refilled into the network port downlink information field; If the query result is no match, the IP information of the hardware device is retrieved; If a match is found, it will be used as a non-downlink server interface.

4. The method of claim 2, wherein: The maintaining of the port category and establishing a corresponding matching relationship with a pre-configured warning rule includes: If a change in the port category is detected, identifying the changed port category in response to a change result of the ARP table carried by the network device; If it is a downstream server port, the changed port category information is maintained in the CMDB and the current port is rebound to the warning rule of the downstream server port.

5. The method of claim 1, wherein: The step of monitoring the status of the port information based on the warning rule and generating warning information includes: The warning rules are configured to set warning rules and warning levels according to indicators in the port information of the network device, and store them in a relational database; In response to the identification result of the port category in the port information, binding a corresponding threshold policy according to the port category; The binding relationship of the changed threshold policy is pushed to a rule message queue, and the rule message queue is consumed by the warning rule in the Spark engine to monitor the network port of the network device according to the port category.

6. The method of claim 5, wherein: The monitoring the status of the port information based on the warning rule and generating warning information further includes: Push the collected network port indicator information of the network device to the message queue, consume the indicator data from the message queue through the Spark engine, and write the indicator data into the ES database; The Spark engine job consumes the port indicator information of the message queue for analysis and calculation. If the indicator meets the configured warning rules, an alert is generated.

7. The method according to any one of claims 1 to 6, further comprising: According to the network device, the port information is displayed on the front-end page; According to the port category, the downstream resources and the system to which the network device port belongs are displayed on the front-end page, supporting click-to-jump to any one or more monitoring information in the downstream resources.

8. A network equipment monitoring and early warning device for a data center, wherein: The device comprises: A collection module, used to collect port information of network devices deployed in the data center, wherein the port information at least includes a port category; A maintenance module, used to maintain the port category and establish a corresponding matching relationship with a pre-configured warning rule, wherein the warning rule can be unbound or bound to the port category; A generating module is used to monitor the status of the port information based on the warning rule and generate warning information.

9. An electronic device, comprising: processor; as well as A memory arranged to store computer executable instructions, which when executed cause the processor to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to execute any one of the methods of claims 1 to 7.

Images