Search

EP-3886365-B1 - DETECTION OF MULTIHOMING MISCONFIGURATION

EP3886365B1EP 3886365 B1EP3886365 B1EP 3886365B1EP-3886365-B1

Inventors

  • VENKATRAMAN, Vasudevan
  • KUMAR, SUSHANT

Dates

Publication Date
20260506
Application Date
20200518

Claims (9)

  1. A method, comprising: receiving (410), by a network device and from an endpoint device, a first message that includes first endpoint identification information, wherein the network device is connected to the endpoint device via a plurality of links in an active state; receiving (420), by the network device and from another network device, a second message that includes second endpoint identification information, wherein the network device and the other network device are associated with the same Ethernet segment identifier, ESI; determining (430), by the network device, whether the first endpoint identification information corresponds to the second endpoint identification information; in response to the first endpoint identification information not corresponding to the second endpoint identification information, causing, by the network device and based on one or more conditions being satisfied, a state of the plurality of links to be changed from the active state to an inactive state; or causing, by the network device and based on one or more conditions being satisfied, the active state of the plurality of links to be maintained.
  2. The method of claim 1, wherein the network device and the other network device are leaf network devices in a spine and leaf network device architecture.
  3. The method of claim 1 or claim 2, wherein the first message comprises a link aggregation control protocol, LACP, protocol data unit, PDU, and the second message comprises a border gateway protocol, BGP, Ethernet virtual private network, EVPN, route.
  4. The method of any preceding claim, wherein determining whether the first endpoint identification information corresponds to the second endpoint identification information comprises: processing the first message to identify the first endpoint identification information; processing the second message to identify the second endpoint identification information; and comparing the first endpoint identification information and the second endpoint identification information to determine whether at least some of the first endpoint identification information matches at least some of the second endpoint identification information.
  5. The method of any preceding claim, wherein determining whether the first endpoint identification information corresponds to the second endpoint identification information comprises: processing the first message to identify the first endpoint identification information; processing the second message to identify the second endpoint identification information; causing a data structure to include a data structure element that indicates whether at least some of the first endpoint identification information and at least some of the second endpoint identification information match; and determining, based on the data structure element, whether the first endpoint identification information corresponds to the second endpoint identification information.
  6. The method of any preceding claim, wherein in response to the first endpoint identification information corresponding to the second endpoint identification information, causing the active state of the plurality of links to be maintained.
  7. The method of any preceding claim, wherein causing the state of the plurality of links to change to the inactive state comprises: sending a message, via the plurality of links and to the endpoint device, to cause at least one interface of the endpoint device that is associated with the plurality of links to deactivate; and causing at least one interface of the network device that is associated with the plurality of links to deactivate.
  8. A network device, comprising: one or more memories; and one or more processors configure to perform the method of any of claims 1 to 7.
  9. A computer-readable medium comprising computer-implementable instructions configured to cause a computer to carry out the method of any of claims 1 to 8.

Description

BACKGROUND A spine and leaf topology of network devices is a multilayer data center network topology that includes leaf network devices (e.g., to which servers and storage devices connect) and spine network devices (e.g., to which leaf network devices connect). The leaf network devices may mesh into a spine to form an access layer that delivers network connection points for servers. US 2013/315255 A1 relates to signaling of attachment circuit status and automatic discovery of inter-chassis communication peers. US 2018/367400 A1 relates to validation of a virtual port channel (VPC) endpoint in the network fabric. US 2013/315097 A1 relates to client auto-configuration in a multi-switch link aggregation SUMMARY The invention is defined in the appended claims. Further embodiments are defined in their respective dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS Figs. 1A-1F are diagrams of one or more example implementations described herein.Fig. 2 is a diagram of an example environment in which systems and/or methods described herein may be implemented.Figs. 3A-3B are diagrams of example components of one or more devices of Fig. 2.Figs. 4-6 are flowcharts of example processes for detecting an occurrence of a multihoming misconfiguration. DETAILED DESCRIPTION The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. A data center may include a plurality of network devices configured in a spine and leaf network topology. The spine and leaf network topology may include a leaf layer and a spine layer. The leaf layer may include leaf network devices (e.g., routers, gateways, bridges, switches, network interface controllers (NICs), and/or the like) that connect to endpoint devices (e.g., servers, firewalls, edge devices, and/or the like). The spine layer may include spine network devices (e.g., routers, gateways, bridges, switches, network interface controllers (NICs), and/or the like) that form the backbone of the network. Every leaf network device may be interconnected with each and every spine network device. An endpoint device may be connected to one or more leaf network devices. In a multihoming scenario, an endpoint device is connected to two or more leaf network devices to increase throughput and/or to provide redundancy. Each of the leaf network devices, to which an endpoint device is multihomed, may be configured to transmit data to and from the endpoint device via a physical connection between the leaf network device and the endpoint device. In practice, the data center may include large numbers of devices (e.g., endpoint devices, leaf network devices, and/or spine network devices) and, in some cases, the large numbers of devices may lead to an occurrence of a multihoming misconfiguration. A multihoming misconfiguration may occur a leaf network device is configured to be multihomed with one endpoint device, but is physically connected to a different endpoint device. A multihoming misconfiguration may cause the leaf network device to incorrectly route traffic to and/or from the endpoint device to which the leaf network device is connected. Incorrectly routing the traffic may result in additional computing resources (e.g., processing resources, memory resources, communication resources, and/or the like) being utilized to process, receive, and/or re-transmit the incorrectly routed traffic. According to some implementations described herein, a network device detects a multihoming misconfiguration when the network device is configured to be multihomed with a particular endpoint device but is actually physically connected to a different endpoint device. In some implementations, the network device may be connected to an endpoint device via a plurality of links. The network device may receive a first message that includes first endpoint identification information from the endpoint device. The network device may receive a second message that includes second endpoint identification information from another network device. The network device may determine whether the first endpoint identification information corresponds to the second endpoint identification information. The network device may cause a state of the plurality of links connecting the network device to the endpoint device to change based on whether the first endpoint identification information corresponds to the second endpoint identification information. For example, the network device may cause the plurality of links to change from an active state (e.g., used to transmit data to/from the endpoint device) to an inactive state (e.g., not used to transmit data to/from the endpoint device). In this way, the network device prevents traffic to and/or from the endpoint device from being misrouted by detecting instances when the network device is configured to be connected to a particular endpoint device but is physically connecte