A networking topology generation and presentation method and apparatus

Abstract

This application discloses a method and device for generating and displaying network topology. The method includes: generating an initial topology map based on device and link information of the managed network; grouping the device nodes in the initial topology map according to the grouping dimension to generate folded virtual nodes; determining the state of the virtual nodes based on the state of each device node within a group; aggregating the physical links between each device node within a group and other devices outside the group to generate aggregated links for the virtual nodes; determining the state of the aggregated links based on the single link state of each physical link in the aggregated links; and when displaying the virtual nodes, expanding the virtual nodes to restore them to all device nodes within the group, and splitting the aggregated links into their internal links. This eliminates the problems of interface congestion and information clutter in large-scale networking, balancing a global overview (folded mode) and link details (expanded mode), significantly optimizing the operation and maintenance experience.

Description

Technical Field

[0001] This application relates to the field of network operation and maintenance visualization technology, and in particular to a method and device for generating and displaying network topology. Background Technology

[0002] Network topology visualization is a core capability of network operations and maintenance, used to intuitively present devices, links, hierarchical relationships, and operational status. With the development of AIGC, cloud computing, and big data, network scale has expanded from dozens of nodes to thousands or even tens of thousands of nodes, posing a serious challenge to traditional topology visualization.

[0003] In current large-scale computing centers, data centers, campus networks, and other networking scenarios, with the surge in the number of nodes and links, traditional topology displays suffer from problems such as crowded interfaces and cluttered information, making it difficult for operations and maintenance personnel to observe the network status globally and quickly locate faults, resulting in low operation and maintenance efficiency and high risks. Summary of the Invention

[0004] To address the aforementioned issues, this application proposes a method for generating and displaying network topology, comprising: Generate an initial topology map based on the device and link information of the managed network; Based on a preset grouping dimension, the device nodes in the initial topology graph are grouped to generate folded virtual nodes; The status of the virtual nodes is determined based on the status of each device node within the group; The physical links between each device node within a group and other devices outside the group are aggregated to generate aggregated links for virtual nodes; The status of the aggregated link is determined based on the individual link status of each physical link in the aggregated link. When displaying the virtual node, the virtual node is expanded and restored to all device nodes within the group, and the aggregated link is split into individual links within the group.

[0005] In one example, an initial topology map is generated based on the device and link information of the managed network, specifically including: The link information is filtered according to the preset set of managed device identifiers, and links whose endpoints do not belong to the set of managed device identifiers are removed. Based on the preset role priority, the device nodes are arranged in layers; the device nodes within the same layer are arranged according to the uniform distribution rule; Each link is drawn according to the preset color mapping relationship corresponding to the link status.

[0006] In one example, device nodes in the initial topology graph are grouped based on a preset grouping dimension to generate virtual nodes, specifically including: Based on the preset grouping dimensions, the device nodes in the initial topology are grouped, and device nodes with the same dimension attribute values ​​are grouped into the same group. When the total number of device nodes in a group is greater than or equal to the node number threshold, the group collapse operation is automatically triggered, and the device nodes in the group are collapsed into virtual nodes. Create a virtual group node object for each group; the virtual group node object includes at least one of the following: a list of device node identifiers within the group, the number of devices, a set of device roles, and a status aggregation result; In the topology view, the virtual group node object is rendered as a single virtual node icon, and the total number of device nodes and role information within the group are displayed on the virtual node icon.

[0007] In one example, the method further includes: The numerical labels superimposed on the virtual node icons correspond to the total number of device nodes, and the role labels superimposed on the icons correspond to the device roles.

[0008] In one example, the state of a virtual node is determined based on the state of each device node within the group, specifically including: Map the state of each device node within the group to obtain the state priority of each device node; The node state with the highest state priority is selected as the virtual node state in descending order of priority.

[0009] In one example, the physical links between each device node within a group and other devices outside the group are aggregated to generate aggregated links for virtual nodes, specifically including: Aggregate all physical links between each device node in the group and the upper-layer device node into an uplink aggregated link, and / or aggregate all physical links between each device node in the group and the lower-layer device into a downlink aggregated link; In the topology view, the connection between a virtual node and an upper-layer device node and / or between a virtual node and a lower-layer device node is rendered as a single line, and the number of all aggregated uplink physical links and / or all aggregated downlink physical links, as well as the number of currently online links, are marked on the virtual node.

[0010] In one example, the aggregated link status is determined based on the individual link status of each physical link in the aggregated link, specifically including: Map the individual link status of each physical link in the aggregated link to obtain the priority of each individual link; The link state with the highest priority is selected as the aggregated link state in descending order of priority.

[0011] In one example, the method further includes: When the user performs the first preset interactive operation on the aggregated link, a details window pops up; The details window displays the link information of each physical link aggregated by the aggregated link; When a user performs a second preset interactive operation on a single link, the single link is located and displayed in the topology view.

[0012] In one example, the method further includes: When the total number of device nodes is less than the node number threshold, the group expansion operation is automatically triggered, restoring the collapsed group to each device node.

[0013] On the other hand, embodiments of this application provide a network topology generation and display device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute any of the above-described network topology generation and display methods.

[0014] On the other hand, embodiments of this application provide a non-volatile computer storage medium for generating and displaying network topology, which stores computer-executable instructions that can execute any of the above-described methods for generating and displaying network topology.

[0015] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects: Based on preset dimensions, a large number of device nodes are grouped and collapsed into virtual nodes, so that multiple nodes are converged into a small number of icons, eliminating interface crowding and making the global architecture clear at a glance.

[0016] The physical links between each device node within a group and other devices outside the group are aggregated into a single aggregated link, and multiple physical links are converged into a single connection, which greatly simplifies the topology.

[0017] The status of virtual nodes is not independently marked, but is determined by the aggregation of the operating status of all device nodes within the group. Operations personnel can perceive device anomalies at any depth from the top-level global view. Similarly, the status of aggregated links is determined by the aggregation of the individual link statuses of each physical link within the group, and link-level faults are also exposed in the global view.

[0018] When a user performs a display operation on a virtual node, the view can be expanded and restored to show all device nodes and internal links within the group, allowing for a one-click switch from a global overview to a detailed view. More importantly, device node and link information are fully preserved and their status is synchronized in real time during the expansion and restoration process, ensuring no information loss when switching between the global and detailed views. Attached Figure Description

[0019] To more clearly illustrate the technical solution of this application, some embodiments of this application will be described in detail below with reference to the accompanying drawings, in which: Figure 1 A flowchart illustrating a method for generating and displaying network topology, provided as an embodiment of this application; Figure 2 This application provides a schematic diagram of an automatic topology construction method. Figure 3 This application provides a schematic diagram of a large-scale topology grouping folding method. Figure 4 A schematic diagram of the folding and unfolding linkage provided in an embodiment of this application; Figure 5 A schematic diagram of a node fault state provided in an embodiment of this application; Figure 6 An embodiment provided in this application Figure 5 The virtual node status of the device node shown; Figure 7 This is a schematic diagram of a network topology generation and display device provided in an embodiment of this application. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] Some embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0022] Figure 1 This is a flowchart illustrating a method for generating and displaying network topology, as provided in an embodiment of this application. Certain input parameters or intermediate results in this process can be manually adjusted to help improve accuracy.

[0023] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a controller as an example.

[0024] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations on this.

[0025] The relevant terms used in this application are explained as follows: LLDP: Link Layer Discovery Protocol, used for neighbor device discovery and link information acquisition.

[0026] SNMP: Simple Network Management Protocol, used for collecting device status and performance data.

[0027] SSH: Secure Shell protocol, used for device configuration and information collection.

[0028] Leaf: Leaf node, access layer / service forwarding node.

[0029] Spine: Ridge node, convergence / backbone layer node.

[0030] SuperSpine: SuperSpine node, a core backbone node for large-scale networking.

[0031] Virtual node: An aggregate node generated after device groups are collapsed, representing a group of devices.

[0032] Link aggregation: Multiple physical links are merged into a logical link to simplify topology display.

[0033] State inheritance: The state of a group / aggregate link is determined by the highest priority abnormal state of the internal node / link.

[0034] Figure 1 The process includes the following steps: S101: Generate an initial topology map based on the device and link information of the managed network.

[0035] The controller manages all network devices in a unified manner, establishing communication connections via SSH / SNMP to achieve unified device control and information collection.

[0036] The system automatically selects the appropriate protocol (e.g., SSH, SNMP, LLDP) based on the device type, and collects device model, IP address, operating status, and role information. Devices experiencing communication failures are flagged as having data collection anomalies and alerted, prompting users to check the connection.

[0037] In this example, the generation process is as follows: Step 1: Filter the link information according to the preset set of managed device identifiers and remove links whose endpoints do not belong to the set of managed device identifiers.

[0038] Network link information is obtained through the LLDP protocol. Links between non-managed devices are filtered based on a whitelist of managed devices, thus retaining links between non-managed devices.

[0039] It should be noted that the information for each link is stored in a structured manner. For example, it includes source node ID, destination node ID, bandwidth, and operating status.

[0040] Step 2: Arrange device nodes in layers according to preset role priorities; device nodes within the same layer are arranged according to a uniform distribution rule.

[0041] Nodes are layered according to device role priority. Nodes in the same layer are evenly distributed using a circular or grid layout algorithm to avoid overlap. It should be noted that if the user manually drags and drops to adjust the node position, the link will automatically adapt and refresh after the adjustment.

[0042] Step 3: Draw each link according to the preset color mapping relationship corresponding to the link status.

[0043] A connection is drawn based on the coordinates of the source and destination nodes. The link status is distinguished by color: green indicates normal, yellow indicates an alarm (such as high packet loss rate), and red indicates a broken link. Users can intuitively understand the link health.

[0044] S102: Group the device nodes in the initial topology graph based on the preset grouping dimension to generate folded virtual nodes.

[0045] In this example, the generation process is as follows: Step 1: Group the device nodes in the initial topology based on the preset grouping dimensions, and group device nodes with the same dimension attribute values ​​into the same group.

[0046] Predefine grouping dimensions such as device roles, forwarding units, regions, and business modules. Users can select single or combined dimensions based on the configuration interface and set up automatic grouping (such as automatically grouping devices in the same data center or with the same business by region or business module).

[0047] For example, at the device role level: all Spine nodes are grouped together, and all Leaf nodes are grouped together. At the forwarding unit level: devices belonging to the same POD are grouped together.

[0048] Geographic unit dimension: Group all devices in the same data center or city into one group. Business module dimension: Group devices that carry the same business (such as payment business) into one group.

[0049] It should be noted that custom grouping rules are also supported. Users can manually select device sets to form custom groups by dragging and dropping or using configuration files.

[0050] Step 2: When the total number of device nodes in a group is greater than or equal to the node number threshold, the group collapse operation is automatically triggered, and the device nodes in the group are collapsed into virtual nodes.

[0051] The node number threshold can be adaptively set according to different network sizes and display scenarios.

[0052] Based on this, it supports configuring a threshold for the number of nodes. The threshold can be set according to screen resolution, display ratio, or manually. When the number of nodes in a group exceeds the threshold, it will automatically collapse; when it falls below the threshold, it will automatically expand. No manual operation is required, which can adapt to different scales of network and display scenarios.

[0053] Step 3: Create a virtual group node object for each group.

[0054] Based on device metadata (roles, IP, business affiliation, geographical location), a group index is built to generate virtual group node objects. These objects include attributes such as the list of devices within the group, the number of devices, the set of device roles, and the status aggregation results.

[0055] The device role set refers to a deduplicated summary list of role types for all device nodes within a virtual group. The status aggregation result is a final status value representing the overall health of a group, calculated by comprehensively evaluating the operating status of all device nodes within the group according to preset priority rules. For example, if even one device in the group is faulty, the aggregation result is faulty; if there is no fault but one device is alarming, the result is alarming; only when all are normal is the result normal.

[0056] Based on this, the state aggregation result is the worst state among all devices in the group (fault > alarm > normal), which is used to determine what color the virtual node is displayed in, ensuring that fault information is not hidden due to collapsing.

[0057] Step 4: In the topology view, render the virtual group node object as a single virtual node icon, and display the total number of device nodes and role information within the group on the virtual node icon.

[0058] Specifically, the numerical labels superimposed on the virtual node icons correspond to the total number of device nodes, and the role labels superimposed on the icons correspond to the device roles.

[0059] When a user clicks on a virtual node, the group expansion logic is triggered, traversing the devices within the group and rendering the real topology; clicking on the expanded device group executes the reverse collapse logic, restoring the virtual node display, and enabling one-click switching between different display granularities.

[0060] S103: Determine the status of the virtual node based on the status of each device node within the group.

[0061] Specifically, the process of determining the state of a virtual node is as follows: Step 1: Map the state of each device node within the group to obtain the state priority of each device node.

[0062] Among them, a state priority mapping table can be preset.

[0063] Step 2: Select the node state with the highest state priority as the virtual node state in descending order.

[0064] Based on this, the state of the collapsed virtual node inherits the state of the devices within the group (e.g., fault > alarm > normal). If any device in the group fails, the virtual node is immediately marked as faulty and the fault is propagated upwards, preventing fault hiding and making global fault visibility possible.

[0065] S104: Aggregate the physical links between each device node within the group and other devices outside the group to generate aggregated links for virtual nodes.

[0066] Multiple physical links within the same group or across groups are merged into one aggregated link, and the total number of online real links is marked. The total number of online links can be used to intuitively determine whether there are any missing links.

[0067] In this example, the process of generating aggregated links for virtual nodes is as follows: Step 1: Aggregate all physical links between each device node in the group and the upper-layer device node into an uplink aggregated link, and / or aggregate all physical links between each device node in the group and the lower-layer device into a downlink aggregated link.

[0068] It should be noted that a group may have both upper-layer device nodes and lower-layer device nodes, or it may have only one type of node.

[0069] Step 2: In the topology view, render the connection between the virtual node and the upper-layer device node and / or the virtual node and the lower-layer device node as a single connection, and mark the number of all aggregated uplink physical links and / or all aggregated downlink physical links, as well as the number of currently online links on the virtual node.

[0070] It should be noted that when there are multiple lower-level device nodes, the virtual node indicates the total number of downlink physical links corresponding to all lower-level device nodes. When there are multiple upper-level device nodes, the virtual node indicates the total number of uplink physical links corresponding to all upper-level device nodes. S105: Determine the aggregated link status based on the individual link status of each physical link in the aggregated link.

[0071] In this example, the individual link status of each physical link in the aggregated link is mapped to obtain the priority of each individual link.

[0072] For example, disconnection has a higher priority than abnormality, and abnormality has a higher priority than normality.

[0073] The state with the highest priority is selected as the state of the aggregated link, in descending order of priority.

[0074] In other words, the status of the aggregated link is determined by the highest-priority abnormal link within it. A single link failure updates the aggregated link status and triggers an alarm in real time.

[0075] S106: When displaying the virtual node, expand the virtual node to restore it to all device nodes within the group, and split the aggregated link into individual links within it.

[0076] When a group is collapsed, the internal links are aggregated and connected to the virtual node; when a group is expanded, the aggregated links are automatically split into single physical links, which are accurately connected to the corresponding physical nodes, with no loss of link information and real-time synchronization of status.

[0077] Furthermore, you can view the details of the aggregated link, including the following process: When a user performs the first preset interactive operation on the aggregated link, a details window pops up. The details window displays the link information of each physical link aggregated by the aggregated link.

[0078] For example, clicking on an aggregated link will bring up a details window that displays the source / destination nodes, bandwidth, status, and port information for all individual links.

[0079] When a user performs a second preset interactive operation on a single link, the single link is located and displayed in the topology view.

[0080] Based on this, it supports clicking on a single link to quickly locate the corresponding position in the topology, enabling rapid troubleshooting.

[0081] In one example, if the number of nodes is below a threshold, the groups can be automatically expanded without manual intervention, adapting to different network sizes and display scenarios.

[0082] Specifically, when the total number of device nodes is less than the node number threshold, the group expansion operation is automatically triggered, restoring the collapsed group to each device node.

[0083] It should be noted that the topology hierarchy can also be flexibly customized: breaking the fixed Host / Leaf / Spine three-layer limitation, it supports users to customize the number of layers, layer names and sorting rules; the layers are identified by numbers, and the nodes in the same layer are evenly arranged horizontally, which is compatible with mainstream architectures such as flat networking, Spine-Leaf, and SuperSpine-Spine-Leaf, and has strong scalability.

[0084] Node / link status can be synchronized: When the status of physical nodes / links changes, the status of virtual nodes and aggregated links is updated in real time, and the status change takes effect in milliseconds.

[0085] Anomalies propagate upwards: Anomalies in the lower-level nodes / links are propagated upwards to the upper-level virtual nodes, and the global topology displays the anomaly distribution in real time, allowing maintenance personnel to quickly locate the abnormal areas.

[0086] Rapid fault location: Clicking on an abnormal node / link automatically highlights the associated link / device and displays abnormal details and alarm information. It supports one-click navigation to the device management interface, achieving a closed-loop process for topology visualization, alarms, troubleshooting, and management.

[0087] In summary, the large-scale topology visualization capability has been significantly improved: by folding device groups and intelligent link aggregation, the problems of interface congestion and information clutter under large-scale networking are eliminated; while taking into account both the global overview (folded mode) and link details (expanded mode), the operation and maintenance experience has been greatly optimized.

[0088] Zero fault omissions and enhanced network reliability: The node and link state inheritance and anomaly upward propagation mechanism ensure that faults within folded groups are exposed in real time and are globally visible, avoiding operational risks caused by fault hiding and improving network stability.

[0089] Significantly improved operational efficiency: Adaptive folding and expanding thresholds reduce manual operations, while link aggregation details viewing and rapid anomaly location functions improve troubleshooting efficiency by more than 50% and reduce operational costs.

[0090] High scalability and adaptability to multiple scenarios: The topology-level custom mechanism is compatible with mainstream networking architectures such as flattened, Spine-Leaf, and SuperSpine-Spine-Leaf, adapting to network operation and maintenance needs of different scales and business scenarios, with strong compatibility and scalability.

[0091] Highly adaptable and low-cost: No need to modify the underlying forwarding hardware, logic is only implemented on the controller and network management platform side, resulting in low development costs, convenient deployment, and rapid adaptation to existing network management systems.

[0092] Specifically, this is reflected in the following ways: Multi-dimensional device grouping and virtual node display: Automatically group devices by role, region, business and other dimensions, collapse them into virtual nodes and mark the quantity, simplifying the display of large-scale topology.

[0093] Intelligent link aggregation and status inheritance mechanism: Multiple links are merged into an aggregated link, and the internal link status is inherited using the priority rule of disconnection > abnormality > normal, so that the aggregated link status accurately reflects the health of the internal links.

[0094] Collapsing and expanding links are linked and information is not lost: when the group is collapsed, the links are aggregated to virtual nodes, and when expanded, they are split back into physical links. There is no loss of link information and status, and they are synchronized in real time.

[0095] Node state inheritance and abnormal propagation: Virtual node state inherits the highest priority abnormal state of the device in the group, and the abnormality is propagated upwards level by level, so as to achieve global fault visibility and zero omission.

[0096] Adaptive folding and unfolding threshold control: Configurable node number thresholds; nodes fold automatically when the threshold is exceeded and unfold automatically when the threshold is below, adapting to different network and display scenarios and reducing manual operation.

[0097] Flexible topology customization: Breaking the limitations of fixed layers, it supports customizing the number of layers, names, and sorting rules, and is compatible with diverse networking architectures such as flat, Spine-Leaf, and SuperSpine-Spine-Leaf.

[0098] It should be noted that, although the embodiments in this application are based on... Figure 1 Steps S101 to S106 will be described sequentially, but this does not mean that steps S101 to S106 must be performed in a strict order. The reason this embodiment follows this order is... Figure 1 The order in which steps S101 to S106 are described is provided to facilitate understanding of the technical solutions of the embodiments of this application by those skilled in the art. In other words, in the embodiments of this application, the order of steps S101 to S106 can be appropriately adjusted according to actual needs.

[0099] pass Figure 1 The method grouped and collapsed a large number of device nodes into virtual nodes based on preset dimensions, so that dozens or even hundreds of nodes were reduced to a small number of icons, eliminating interface crowding and making the global architecture clear at a glance.

[0100] The physical links between each device node within a group and other devices outside the group are aggregated into a single aggregated link, converging dozens or even hundreds of physical links into a single connection, which greatly simplifies the topology.

[0101] The status of virtual nodes is not independently marked, but is determined by the aggregation of the operating status of all device nodes within a group. Operations personnel can perceive device anomalies at any depth from the top-level global view. Similarly, the status of an aggregated link is determined by the aggregation of the individual link statuses of its internal physical links, and link-level faults are also exposed in the global view.

[0102] When a user performs a display operation on a virtual node, the view can be expanded and restored to show all device nodes and internal links within the group, allowing for a one-click switch from a global overview to a detailed view. More importantly, device node and link information are fully preserved and their status is synchronized in real time during the expansion and restoration process, ensuring no information loss when switching between the global and detailed views.

[0103] In summary, by using grouping aggregation, state inheritance, and adaptive control to address the global, detailed, and contradictory aspects of large-scale data visualization, this approach can be widely applied to other large-scale operation and maintenance scenarios.

[0104] Server cluster visualization: grouped and collapsed displays show cluster status, and supports expanding to view individual server details.

[0105] Storage network topology: Adapts to multi-controller and multi-disk array networking, allows for customizable hierarchies and aggregated links, and enhances the visualization capabilities of storage operation and maintenance.

[0106] IoT Device Management: For massive IoT terminals, it groups and collapses terminals by region and device type, adaptively displaying terminal topology and online status, reducing management complexity.

[0107] More intuitively, Figure 2 This is a schematic diagram of an automatic topology construction provided in an embodiment of this application.

[0108] exist Figure 2 In this architecture, nodes are arranged in layers, and link status is distinguished. Spine group 1 is located at the top layer, serving as the core backbone layer; Leaf group 1 and Leaf group 2 are located in the middle layer, serving as the access aggregation layer; Server group 1 and Server group 2 are located at the bottom layer, serving as the service access layer.

[0109] Figure 3 This is a schematic diagram of a large-scale topology grouping folding provided in an embodiment of this application.

[0110] exist Figure 3 In this architecture, each level is represented by virtual nodes. For example, Spine group 1 (8 devices) means that the virtual node aggregates 8 devices, Leaf group 2 (8 devices) aggregates 8 devices, and Server group 2 (64 servers) aggregates 64 servers. Through this grouping and folding, a complex topology that may originally include hundreds of nodes and thousands of links is simplified to 5 virtual nodes and a few connections, achieving a clear overview of the global architecture.

[0111] The links between virtual nodes are presented in the form of aggregated links. The denominator represents the total number of physical links included in the aggregated link, and the numerator represents the number of links in normal status.

[0112] Figure 4 This is a schematic diagram of a folding and unfolding linkage provided in an embodiment of this application.

[0113] exist Figure 4 In the process, the virtual nodes of Leaf group 1 were expanded.

[0114] Figure 5 This is a schematic diagram of a node fault state provided in an embodiment of this application.

[0115] exist Figure 5 In Leaf group 2, there is a faulty device.

[0116] Figure 6 An embodiment provided in this application Figure 5 The virtual node status of the device node shown.

[0117] exist Figure 6 In the middle, the virtual node of Leaf group 2 is highlighted in red as a fault status.

[0118] In summary, an adaptive topology generation and visualization scheme organically combines five mechanisms: device grouping and folding, intelligent link aggregation, node / link state linkage inheritance, topology hierarchy customization, and adaptive folding / expanding threshold control. This constructs an end-to-end adaptive visualization system for large-scale networking scenarios. Device grouping and folding: Dynamically aggregates and hierarchically divides network nodes of different sizes to solve the information overload problem of ultra-large-scale topologies.

[0119] Intelligent link aggregation: Logically aggregates multiple links based on business attributes and physical paths, while retaining the traceability of key link details.

[0120] Node / link status linkage inheritance: Establish hierarchical transmission and inheritance rules for fault status to ensure that fault information is not lost or hidden during folding / expanding operations.

[0121] Customizable topology hierarchy: Users can flexibly configure the topology hierarchy and display dimensions according to their operation and maintenance scenarios, adapting to various network architectures; Adaptive collapse / expansion threshold control: The collapse / expansion strategy is dynamically adjusted based on network size, node density and user interaction behavior to achieve a smooth transition from global overview to detailed viewing.

[0122] This solution addresses the pain points of large-scale networking scenarios, such as the inability to simultaneously provide a global overview and detailed viewing, incomplete fault status transmission, and poor adaptability to multiple architectures, through the coordinated linkage of various mechanisms. It achieves a smooth display of network topologies from small-scale to ultra-large-scale, while ensuring that the global overview and link details are traceable, fault status is transmitted upwards, and it adapts to multiple networking architectures, significantly improving the visualization capabilities of operation and maintenance and the efficiency of fault location.

[0123] In addition, no changes are needed to the underlying forwarding hardware; the logic can be implemented on the controller or network management platform side, making it highly deployable and compatible.

[0124] It should be noted that using fixed layers, simple flat display, or manual grouping and folding will cause the following problems: Grouping and collapsing: Multiple devices are merged into one icon, but link information is lost after collapsing and abnormal status cannot be passed up, resulting in hidden faults.

[0125] Link aggregation: Simply merges lines, cannot view details of individual links, and the aggregated link status cannot accurately reflect internal link anomalies.

[0126] Fixed layer: Only supports three fixed layers: Host / Leaf / Spine, and cannot adapt to diverse architectures such as SuperSpine-Spine-Leaf and flat networking. No adaptive mechanism: Folding / unfolding relies on manual operation, which is cumbersome and inefficient in large-scale scenarios.

[0127] The aforementioned problems also lead to a crowded and cluttered topology interface, making it impossible to observe the entire network and causing difficulties in troubleshooting when deploying large-scale networks, which seriously affects operation and maintenance efficiency and network reliability.

[0128] Based on the same idea, some embodiments of this application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0129] Figure 7 A schematic diagram of a network topology generation and display device provided in this application embodiment includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform any of the above-described methods for generating and displaying network topology.

[0130] Some embodiments of this application provide a non-volatile computer storage medium for generating and displaying network topology, which stores computer-executable instructions capable of executing any of the above-described methods for generating and displaying network topology.

[0131] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0132] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0133] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied 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.

[0134] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0135] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0136] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0138] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0139] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0140] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0141] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the technical principles of this application should fall within the protection scope of this application.

Claims

1. A method for generating and displaying network topology, characterized in that, The method includes: Generate an initial topology map based on the device and link information of the managed network; Based on a preset grouping dimension, the device nodes in the initial topology graph are grouped to generate folded virtual nodes; The status of the virtual nodes is determined based on the status of each device node within the group; The physical links between each device node within a group and other devices outside the group are aggregated to generate aggregated links for virtual nodes; The status of the aggregated link is determined based on the individual link status of each physical link in the aggregated link. When displaying the virtual node, the virtual node is expanded and restored to all device nodes within the group, and the aggregated link is split into individual links within the group.

2. The method according to claim 1, characterized in that, Based on the device and link information of the managed network, an initial topology map is generated, specifically including: The link information is filtered according to the preset set of managed device identifiers, and links whose endpoints do not belong to the set of managed device identifiers are removed. Based on the preset role priority, the device nodes are arranged in layers; the device nodes within the same layer are arranged according to the uniform distribution rule; Each link is drawn according to the preset color mapping relationship corresponding to the link status.

3. The method according to claim 1, characterized in that, Based on a preset grouping dimension, the device nodes in the initial topology diagram are grouped to generate virtual nodes, specifically including: Based on the preset grouping dimensions, the device nodes in the initial topology are grouped, and device nodes with the same dimension attribute values ​​are grouped into the same group. When the total number of device nodes in a group is greater than or equal to the node number threshold, the group collapse operation is automatically triggered, and the device nodes in the group are collapsed into virtual nodes. Create a virtual group node object for each group; the virtual group node object includes at least one of the following: a list of device node identifiers within the group, the number of devices, a set of device roles, and a status aggregation result; In the topology view, the virtual group node object is rendered as a single virtual node icon, and the total number of device nodes and role information within the group are displayed on the virtual node icon.

4. The method according to claim 3, characterized in that, The method further includes: The numerical labels superimposed on the virtual node icons correspond to the total number of device nodes, and the role labels superimposed on the icons correspond to the device roles.

5. The method according to claim 1, characterized in that, The status of the virtual node is determined based on the status of each device node within the group, specifically including: Map the state of each device node within the group to obtain the state priority of each device node; The node state with the highest state priority is selected as the virtual node state in descending order of priority.

6. The method according to claim 1, characterized in that, The physical links between each device node within a group and other devices outside the group are aggregated to generate aggregated links for virtual nodes, specifically including: Aggregate all physical links between each device node in the group and the upper-layer device node into an uplink aggregated link, and / or aggregate all physical links between each device node in the group and the lower-layer device into a downlink aggregated link; In the topology view, the connection between a virtual node and an upper-layer device node and / or between a virtual node and a lower-layer device node is rendered as a single line, and the number of all aggregated uplink physical links and / or all aggregated downlink physical links, as well as the number of currently online links, are marked on the virtual node.

7. The method according to claim 1, characterized in that, The aggregated link status is determined based on the individual link status of each physical link in the aggregated link, specifically including: Map the individual link status of each physical link in the aggregated link to obtain the priority of each individual link; The link state with the highest priority is selected as the aggregated link state in descending order of priority.

8. The method according to claim 1, characterized in that, The method further includes: When the user performs the first preset interactive operation on the aggregated link, a details window pops up; The details window displays the link information of each physical link aggregated by the aggregated link; When a user performs a second preset interactive operation on a single link, the single link is located and displayed in the topology view.

9. The method according to claim 1, characterized in that, The method further includes: When the total number of device nodes is less than the node number threshold, the group expansion operation is automatically triggered, restoring the collapsed group to each device node.

10. A network topology generation and display device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform a network topology generation and display method according to any one of claims 1-9.

Images