US20230208718A1 - Network topology planning and validation - Google Patents

Network topology planning and validation Download PDF

Info

Publication number
US20230208718A1
US20230208718A1 US17/575,472 US202217575472A US2023208718A1 US 20230208718 A1 US20230208718 A1 US 20230208718A1 US 202217575472 A US202217575472 A US 202217575472A US 2023208718 A1 US2023208718 A1 US 2023208718A1
Authority
US
United States
Prior art keywords
equipment
topology
data network
information handling
handling system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US17/575,472
Other languages
English (en)
Inventor
Hong Yuan
Honggang Liu
Yining CHU
Zhe Huang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dell Products LP
Original Assignee
Dell Products LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dell Products LP filed Critical Dell Products LP
Assigned to DELL PRODUCTS L.P. reassignment DELL PRODUCTS L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHU, YINING, HUANG, ZHE, LIU, HONGGANG, YUAN, HONG
Publication of US20230208718A1 publication Critical patent/US20230208718A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/25—Routing or path finding in a switch fabric
    • H04L49/253—Routing or path finding in a switch fabric using establishment or release of connections between ports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/25—Routing or path finding in a switch fabric
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/25—Routing or path finding in a switch fabric
    • H04L49/252—Store and forward routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/344—Out-of-band transfers

Definitions

  • the present disclosure relates in general to information handling systems, and more particularly to the planning and topology of network links in clusters of information handling systems.
  • An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information.
  • information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated.
  • the variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications.
  • information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
  • Hyper-converged infrastructure is an IT framework that combines storage, computing, and networking into a single system in an effort to reduce data center complexity and increase scalability.
  • Hyper-converged platforms may include a hypervisor for virtualized computing, software-defined storage, and virtualized networking, and they typically run on standard, off-the-shelf servers.
  • One type of HCI solution is the Dell EMC VxRailTM system.
  • HCI systems may operate in various environments (e.g., an HCI management system such as the VMware® vSphere® ESXiTM environment, or any other HCI management system).
  • HCI systems may operate as software-defined storage (SDS) cluster systems (e.g., an SDS cluster system such as the VMware® vSANTM system, or any other SDS cluster system).
  • SDS software-defined storage
  • topology may require a high degree of understanding of the target implementation, including knowledge about switches, hosts, racks, cabling, equipment distribution in the datacenter, and networking requirements.
  • topology should be understood to include information regarding which systems (e.g., information handling systems, switches, routers, etc.) should be coupled together via network cabling, which ports should be coupled to one another, etc.
  • embodiments of this disclosure may provide a device topology map and wiring design to ease the planning and implementation of a network topology.
  • This disclosure provides ways to generate such a map before planning, and it also provides the capability of validating the topology as soon as the implementation is complete.
  • an information handling system may include at least one processor and a memory.
  • the information handling system may be configured to: receive information regarding equipment that is to be communicatively coupled to a data network; determine a topology for communicatively coupling the equipment to the data network, wherein the topology includes information regarding which equipment ports of the equipment are to be coupled to data network ports of the data network; and transmit information regarding the topology to a user.
  • a method may include receiving, at an information handling system, information regarding equipment that is to be communicatively coupled to a data network; determining, by the information handling system, a topology for communicatively coupling the equipment to the data network, wherein the topology includes information regarding which equipment ports of the equipment are to be coupled to data network ports of the data network; and transmitting information regarding the topology from the information handling system to a user.
  • an article of manufacture may include a non-transitory, computer-readable medium having computer-executable instructions thereon that are executable by a processor of an information handling system for: receiving information regarding equipment that is to be communicatively coupled to a data network; determining a topology for communicatively coupling the equipment to the data network, wherein the topology includes information regarding which equipment ports of the equipment are to be coupled to data network ports of the data network; and transmitting information regarding the topology to a user.
  • FIG. 1 illustrates a block diagram of an example information handling system, in accordance with embodiments of the present disclosure
  • FIG. 2 illustrates a block diagram of an example set of information handling systems, in accordance with embodiments of the present disclosure
  • FIG. 3 illustrates a block diagram of an example network topology, in accordance with embodiments of the present disclosure.
  • FIG. 4 illustrates a block diagram of validation of an example network topology, in accordance with embodiments of the present disclosure.
  • FIGS. 1 through 4 Preferred embodiments and their advantages are best understood by reference to FIGS. 1 through 4 , wherein like numbers are used to indicate like and corresponding parts.
  • an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes.
  • an information handling system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price.
  • the information handling system may include memory, one or more processing resources such as a central processing unit (“CPU”) or hardware or software control logic.
  • Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input/output (“I/O”) devices, such as a keyboard, a mouse, and a video display.
  • the information handling system may also include one or more buses operable to transmit communication between the various hardware components.
  • Coupleable When two or more elements are referred to as “coupleable” to one another, such term indicates that they are capable of being coupled together.
  • Computer-readable medium may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time.
  • Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.
  • storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (
  • information handling resource may broadly refer to any component system, device, or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems, buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, and/or any other components and/or elements of an information handling system.
  • management controller may broadly refer to an information handling system that provides management functionality (typically out-of-band management functionality) to one or more other information handling systems.
  • a management controller may be (or may be an integral part of) a service processor, a baseboard management controller (BMC), a chassis management controller (CMC), or a remote access controller (e.g., a Dell Remote Access Controller (DRAC) or Integrated Dell Remote Access Controller (iDRAC)).
  • BMC baseboard management controller
  • CMC chassis management controller
  • remote access controller e.g., a Dell Remote Access Controller (DRAC) or Integrated Dell Remote Access Controller (iDRAC)
  • FIG. 1 illustrates a block diagram of an example information handling system 102 , in accordance with embodiments of the present disclosure.
  • information handling system 102 may comprise a server chassis configured to house a plurality of servers or “blades.”
  • information handling system 102 may comprise a personal computer (e.g., a desktop computer, laptop computer, mobile computer, and/or notebook computer).
  • information handling system 102 may comprise a storage enclosure configured to house a plurality of physical disk drives and/or other computer-readable media for storing data (which may generally be referred to as “physical storage resources”). As shown in FIG.
  • information handling system 102 may comprise a processor 103 , a memory 104 communicatively coupled to processor 103 , a BIOS 105 (e.g., a UEFI BIOS) communicatively coupled to processor 103 , a network interface 108 communicatively coupled to processor 103 , and a management controller 112 communicatively coupled to processor 103 .
  • BIOS 105 e.g., a UEFI BIOS
  • network interface 108 communicatively coupled to processor 103
  • management controller 112 communicatively coupled to processor 103 .
  • processor 103 may comprise at least a portion of a host system 98 of information handling system 102 .
  • information handling system 102 may include one or more other information handling resources.
  • Processor 103 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation, a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data.
  • processor 103 may interpret and/or execute program instructions and/or process data stored in memory 104 and/or another component of information handling system 102 .
  • Memory 104 may be communicatively coupled to processor 103 and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media).
  • Memory 104 may include RAM, EEPROM, a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.
  • memory 104 may have stored thereon an operating system 106 .
  • Operating system 106 may comprise any program of executable instructions (or aggregation of programs of executable instructions) configured to manage and/or control the allocation and usage of hardware resources such as memory, processor time, disk space, and input and output devices, and provide an interface between such hardware resources and application programs hosted by operating system 106 .
  • operating system 106 may include all or a portion of a network stack for network communication via a network interface (e.g., network interface 108 for communication over a data network).
  • network interface e.g., network interface 108 for communication over a data network
  • Network interface 108 may comprise one or more suitable systems, apparatuses, or devices operable to serve as an interface between information handling system 102 and one or more other information handling systems via an in-band network.
  • Network interface 108 may enable information handling system 102 to communicate using any suitable transmission protocol and/or standard.
  • network interface 108 may comprise a network interface card, or “NIC.”
  • network interface 108 may be enabled as a local area network (LAN)-on-motherboard (LOM) card.
  • LAN local area network
  • LOM local area network
  • Management controller 112 may be configured to provide management functionality for the management of information handling system 102 . Such management may be made by management controller 112 even if information handling system 102 and/or host system 98 are powered off or powered to a standby state. Management controller 112 may include a processor 113 , memory, and a network interface 118 separate from and physically isolated from network interface 108 .
  • processor 113 of management controller 112 may be communicatively coupled to processor 103 .
  • Such coupling may be via a Universal Serial Bus (USB), System Management Bus (SMBus), and/or one or more other communications channels.
  • USB Universal Serial Bus
  • SMBs System Management Bus
  • Network interface 118 may be coupled to a management network, which may be separate from and physically isolated from the data network as shown.
  • Network interface 118 of management controller 112 may comprise any suitable system, apparatus, or device operable to serve as an interface between management controller 112 and one or more other information handling systems via an out-of-band management network.
  • Network interface 118 may enable management controller 112 to communicate using any suitable transmission protocol and/or standard.
  • network interface 118 may comprise a network interface card, or “NIC.”
  • Network interface 118 may be the same type of device as network interface 108 , or in other embodiments it may be a device of a different type.
  • this disclosure provides ways of generating a device topology map and/or cabling design to ease the planning and/or implementation of a network topology. For example, when a datacenter is being built, or when additional equipment (e.g., new information handling systems 102 , new switches, new routers, new racks, etc.) are being added to a datacenter, such a topology map may be employed to make the task less burdensome. Further, once installation and cabling is complete (e.g., with Ethernet cables, optical fiber, and/or any other suitable data transmission media), embodiments may allow for validation of the as-installed topology to ensure that it conforms to the design.
  • additional equipment e.g., new information handling systems 102 , new switches, new routers, new racks, etc.
  • a planning/validation tool may be implemented in an information handling system such as information handling system 102 via hardware, software, and/or firmware components.
  • a planning/validation tool may include a web interface to allow administrators to interact with it in a visual manner. Such a web interface may provide a graphical view of the network topology, as discussed in more detail below with reference to FIGS. 3 and 4 .
  • other interface styles e.g., textual
  • a single tool may be used for both planning and validation; in other embodiments, separate tools may be used.
  • planning/validation tool refers to one or more tools that provide such functionality, regardless of whether implemented as a single tool or multiple separate tools.
  • such a planning/validation tool may execute on information handling systems that are a part of the existing infrastructure of the datacenter, or on information handling systems that are separate from the existing infrastructure.
  • Some embodiments may provide an agent program that can be downloaded to a client system (e.g., a laptop, a virtual machine, etc.). This client system may then be used as a “jumpbox,” and the agent may communicatively couple to one or more network switches of the datacenter as discussed herein.
  • a client system e.g., a laptop, a virtual machine, etc.
  • This client system may then be used as a “jumpbox,” and the agent may communicatively couple to one or more network switches of the datacenter as discussed herein.
  • switches When new devices are to be installed in a datacenter, various tasks may be undertaken. For example, administrators may determine which racks and switches the new devices will be distributed to. If existing switches are to be used, then the locations, IP addresses, and access credentials (e.g., for SSH access) for those switches may be determined.
  • access credentials e.g., for SSH access
  • Administrators may then input various information into the planning/validation tool. For example, information about the new devices (e.g., device model, number of network interfaces, other hardware and/or software details, etc.) may be transmitted to a planning/validation tool. The tool may then store such information in a database for later usage. The administrator may also input the switch IP addresses and SSH credentials (if any). The tool may then obtain additional configuration information directly from those switches automatically (e.g., which ports are in use, virtual local area network (VLAN) information, etc.).
  • VLAN virtual local area network
  • the planning/validation tool may include an interface to allow an administrator to draw a “map” of how devices should be distributed (e.g., based on rack locations, etc.).
  • Any suitable user interface e.g., including keyboard, mouse, touchpad, touchscreen, and/or other interfaces
  • FIG. 2 provides one example of such a map.
  • rack 210 A is to be populated with a new management switch, two new top-of-rack (TOR) switches, and six new information handling systems.
  • Rack 210 B includes an existing management switch, two existing TOR switches, and is to be populated with two new information handling systems.
  • the administrator may also define connectivity rules at this stage.
  • Some examples of connectivity rules may include elements such as:
  • such connectivity rules may also be inherited from existing setups, so that the step of entering new rules may be shortened or omitted when setting up an environment similar to an existing environment. Rules may also be selected from a list of example rules (e.g., with optional modifications as necessary).
  • the planning/validation tool may generate a topology. Any suitable method may be used for generation of such a topology.
  • a greedy algorithm may be used in one embodiment, such that, for example, for each desired network connection between a switch and an information handling system, the tool is configured to connect the first available port of the switch to the first available port of the information handling system.
  • Backtracking or other techniques may then be used if necessary to rearrange connections if rule-based constraints are not met or if incompatible connections are generated.
  • techniques such as depth-first search, breadth-first search, exhaustive search, or any other suitable technique may be used to determine a topology that satisfies the desired constraints.
  • the planning/validation tool may help to generate VLANs to meet specified rules.
  • the cabling for the generated topology may then be displayed graphically for the administrator.
  • FIG. 3 illustrates a portion of an example topology that may be generated by a planning/validation tool according to this disclosure.
  • the generated topology includes the planned network connections between management switch 302 , TOR switches 304 A and 304 B, and information handling systems 306 A- 306 D.
  • color coding or another visual scheme such as dashed lines may be used to indicate cable status. For example, cables that have not yet been installed may be indicated in red, while existing cabling may be indicated in green. Cables to connect to different types of switches may be shown in different types of lines (e.g., dotted/dashed vs. solid lines).
  • port color may be used to indicate whether or not a port is in use, whether it is connected correctly or incorrectly, whether it is unconfigured, configured, or partially configured, etc.
  • Information handling system color may be used for similar purposes as well in some embodiments.
  • the three switches show that ports 1-4 are “occupied,” which may indicate that those ports are in use by other environment.
  • Certain interconnection ports such as ports 33-36 on TOR switches 304 A and 304 B may be shown in a designated color (e.g., green) indicating that they are already configured. (The wiring associated with those ports may also be displayed in green.)
  • the uplink from TOR switch 304 A to management switch 302 is port 43, and the link may be shown in a designated color (e.g., green) indicating that it is already wired.
  • port 43's VLAN is not configured as expected, and thus it is shown in a designated color (e.g., white) indicating this state.
  • the planning/validation tool may also allow the administrator to input changes as needed in some embodiments.
  • information handling system 306 A is shown highlighted because it is currently selected by the administrator. Further, the network links from the selected element may also be shown highlighted or in a different color. Based on this selection, the planning validation tool may also provide configuration suggestions regarding information handling system 306 A (e.g., VLAN configuration suggestions such as:
  • the administrator may instruct the planning/validation tool to validate the as-installed wiring.
  • FIG. 4 illustrates a portion of the example topology from FIG. 3 , as it may be shown after implementation.
  • the validated topology includes the detected network connections between management switch 402 , TOR switches 404 A and 404 B, and information handling systems 406 A- 406 D.
  • Verified network connections may be shown in a particular color (e.g., green). Missing or malfunctioning connections may be shown in another color (e.g., red).
  • Ports that do not satisfy specified rules may be shown in red as well. Ports that are configured and satisfy the rules may be shown in green. Partially configured ports may be shown in yellow.
  • the planning/validation tool may also provide a textual description of various issues with the validation.
  • the tool may outline issues such as missing wiring, misconfigured VLANs, etc.
  • references in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.
US17/575,472 2021-12-23 2022-01-13 Network topology planning and validation Pending US20230208718A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111593321.3 2021-12-23
CN202111593321.3A CN116346750A (zh) 2021-12-23 2021-12-23 网络拓扑规划和验证

Publications (1)

Publication Number Publication Date
US20230208718A1 true US20230208718A1 (en) 2023-06-29

Family

ID=86890110

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/575,472 Pending US20230208718A1 (en) 2021-12-23 2022-01-13 Network topology planning and validation

Country Status (2)

Country Link
US (1) US20230208718A1 (zh)
CN (1) CN116346750A (zh)

Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7310774B1 (en) * 2000-08-28 2007-12-18 Sanavigator, Inc. Method for displaying switch port information in a network topology display
US7342891B2 (en) * 2002-12-20 2008-03-11 Hon Hai Precision Industry Co., Ltd. Port information display system and method for displaying port performance of network devices
US20100115415A1 (en) * 2008-10-31 2010-05-06 Hickey James P Graphic for network switches
US8543957B2 (en) * 2010-08-27 2013-09-24 Fujitsu Limited Optical network design apparatus and method
US9049146B2 (en) * 2008-10-22 2015-06-02 Accenture Global Services Limited Automatically connecting remote network equipment through a graphical user interface
US9384113B1 (en) * 2012-11-21 2016-07-05 Qlogic, Corporation Systems and methods for identifying port protocols using LEDs
US9385924B2 (en) * 2011-03-15 2016-07-05 Omron Corporation Assistance system
US9397897B2 (en) * 2011-03-15 2016-07-19 Omron Corporation Assistance system
US20160378630A1 (en) * 2015-06-25 2016-12-29 Dell Products L.P. Port monitoring system
US9641390B2 (en) * 2015-05-27 2017-05-02 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Automatic configuration of switch port settings based on the device attached to the switch port
US9769036B1 (en) * 2014-10-23 2017-09-19 VCE IP Holding Company LLC Port assignment of network devices reference and management
US10057137B1 (en) * 2012-11-12 2018-08-21 Marvell International Ltd. Cable discovery with visual display of a network topology
US20190372861A1 (en) * 2018-06-01 2019-12-05 Hewlett Packard Enterprise Development Lp Network device modifications via augmented reality user interfaces
US10581688B2 (en) * 2017-06-19 2020-03-03 Quanta Computer Inc. Methods for automatically configuring multiple chassis link aggregation group (MC-LAG)
US10756984B2 (en) * 2015-04-13 2020-08-25 Wirepath Home Systems, Llc Method and apparatus for creating and managing network device port VLAN configurations
US20210367848A1 (en) * 2017-09-28 2021-11-25 Signify Holding B.V. A method of commissioning a wired communication network
US11258794B2 (en) * 2019-01-09 2022-02-22 Hewlett Packard Enterprise Development Lp Device category based authentication
US20220070114A1 (en) * 2020-08-27 2022-03-03 Abb Schweiz Ag System and method for enabling tsn-stream configuration
US11379334B1 (en) * 2021-01-21 2022-07-05 Juniper Networks, Inc. Network device having dynamic port or link status indicators
US11394622B1 (en) * 2020-03-19 2022-07-19 Juniper Networks, Inc Systems and methods for efficient presentation of device-level information via scalable interactive device-visualization interfaces
US11405273B1 (en) * 2021-09-22 2022-08-02 Future Dial, Inc. Network device data erasure
US11451449B1 (en) * 2021-09-13 2022-09-20 Juniper Networks, Inc. Configuration of EVPN topologies using a user interface
US20230078773A1 (en) * 2021-09-13 2023-03-16 Juniper Networks, Inc. Configuration of evpn topologies using a user interface
US11646807B2 (en) * 2019-08-21 2023-05-09 Commscope Technologies Llc Methods including detecting cables connected to ports of communications network equipment and related systems
US20230166404A1 (en) * 2021-11-12 2023-06-01 Future Dial, Inc. Electronic device remote controller

Patent Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7310774B1 (en) * 2000-08-28 2007-12-18 Sanavigator, Inc. Method for displaying switch port information in a network topology display
US7342891B2 (en) * 2002-12-20 2008-03-11 Hon Hai Precision Industry Co., Ltd. Port information display system and method for displaying port performance of network devices
US9049146B2 (en) * 2008-10-22 2015-06-02 Accenture Global Services Limited Automatically connecting remote network equipment through a graphical user interface
US20100115415A1 (en) * 2008-10-31 2010-05-06 Hickey James P Graphic for network switches
US8543957B2 (en) * 2010-08-27 2013-09-24 Fujitsu Limited Optical network design apparatus and method
US9385924B2 (en) * 2011-03-15 2016-07-05 Omron Corporation Assistance system
US9397897B2 (en) * 2011-03-15 2016-07-19 Omron Corporation Assistance system
US10057137B1 (en) * 2012-11-12 2018-08-21 Marvell International Ltd. Cable discovery with visual display of a network topology
US9384113B1 (en) * 2012-11-21 2016-07-05 Qlogic, Corporation Systems and methods for identifying port protocols using LEDs
US9769036B1 (en) * 2014-10-23 2017-09-19 VCE IP Holding Company LLC Port assignment of network devices reference and management
US10756984B2 (en) * 2015-04-13 2020-08-25 Wirepath Home Systems, Llc Method and apparatus for creating and managing network device port VLAN configurations
US9641390B2 (en) * 2015-05-27 2017-05-02 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Automatic configuration of switch port settings based on the device attached to the switch port
US20160378630A1 (en) * 2015-06-25 2016-12-29 Dell Products L.P. Port monitoring system
US10581688B2 (en) * 2017-06-19 2020-03-03 Quanta Computer Inc. Methods for automatically configuring multiple chassis link aggregation group (MC-LAG)
US20210367848A1 (en) * 2017-09-28 2021-11-25 Signify Holding B.V. A method of commissioning a wired communication network
US20190372861A1 (en) * 2018-06-01 2019-12-05 Hewlett Packard Enterprise Development Lp Network device modifications via augmented reality user interfaces
US11258794B2 (en) * 2019-01-09 2022-02-22 Hewlett Packard Enterprise Development Lp Device category based authentication
US11646807B2 (en) * 2019-08-21 2023-05-09 Commscope Technologies Llc Methods including detecting cables connected to ports of communications network equipment and related systems
US11394622B1 (en) * 2020-03-19 2022-07-19 Juniper Networks, Inc Systems and methods for efficient presentation of device-level information via scalable interactive device-visualization interfaces
US20220070114A1 (en) * 2020-08-27 2022-03-03 Abb Schweiz Ag System and method for enabling tsn-stream configuration
US11652757B2 (en) * 2020-08-27 2023-05-16 Abb Schweiz Ag System and method for enabling TSN-stream configuration
US11379334B1 (en) * 2021-01-21 2022-07-05 Juniper Networks, Inc. Network device having dynamic port or link status indicators
US11451449B1 (en) * 2021-09-13 2022-09-20 Juniper Networks, Inc. Configuration of EVPN topologies using a user interface
US20230078773A1 (en) * 2021-09-13 2023-03-16 Juniper Networks, Inc. Configuration of evpn topologies using a user interface
US11405273B1 (en) * 2021-09-22 2022-08-02 Future Dial, Inc. Network device data erasure
US20230166404A1 (en) * 2021-11-12 2023-06-01 Future Dial, Inc. Electronic device remote controller

Also Published As

Publication number Publication date
CN116346750A (zh) 2023-06-27

Similar Documents

Publication Publication Date Title
US20180024838A1 (en) Techniques to detect non-enumerable devices via a firmware interface table
US8495208B2 (en) Migrating virtual machines among networked servers upon detection of degrading network link operation
US8495255B2 (en) Discovery and configuration of device configurations
US10425287B2 (en) Systems and methods for network topology discovery
US10992526B1 (en) Hyper-converged infrastructure networking configuration system
WO2015127851A1 (en) System and method for creating service chains and virtual networks in the cloud
CN109039788A (zh) 网络设备的端口配置方法、装置和存储介质
US11782694B2 (en) Pipeline rolling update
US9832074B2 (en) Converged infrastructure local management system
US20130315096A1 (en) Network infrastructure provisioning with automated channel assignment
US11514951B2 (en) Identification of storage resources in multiple domains
US20150006700A1 (en) Establishing connectivity of modular nodes in a pre-boot environment
US8064469B2 (en) Parallel VLAN and non-VLAN device configuration
US20210392038A1 (en) Configuring hci management network via management controller
US20230208718A1 (en) Network topology planning and validation
US10534728B2 (en) Systems and methods for providing adaptable virtual backplane support for processor-attached storage resources
US10303568B2 (en) Systems and methods for high availability of management controllers
US10785118B2 (en) Systems and methods for network topology validation
US11431552B1 (en) Zero traffic loss in VLT fabric
US20240126903A1 (en) Simulation of edge computing nodes for hci performance testing
US11977562B2 (en) Knowledge base for correcting baseline for cluster scaling
US9832079B2 (en) Determining the topology of a network
US11656879B2 (en) Automated OS networking configuration system
NL2027692B1 (en) Pre-provisioning server hardware for deployment on an edge network
US20240103991A1 (en) Hci performance capability evaluation

Legal Events

Date Code Title Description
AS Assignment

Owner name: DELL PRODUCTS L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YUAN, HONG;LIU, HONGGANG;CHU, YINING;AND OTHERS;REEL/FRAME:058657/0088

Effective date: 20211227

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED