N-node virtual link trunking (VLT) systems management plane
Aspects of the present invention include an N-Node virtual link trunking (VLT) system comprising a set of N nodes collectively provide a logical fabric-level view that is consistent across the set of N nodes. Embodiments of the N-Node VLT system comprise a control plane mechanism to provide Layer 2 multipathing between access network devices (switches or servers) and the core network. The N-Node VLT system provides a loop-free topology with active-active load-sharing of uplinks from access to the core. Accordingly, the N-Node VLT system eliminates the disadvantage of Spanning Tree Protocol (STP) (active-standby links) by allowing link aggregation group (LAG) terminations on multiple separate distribution or core switches and also supporting a loop-free topology. Additional benefits of an N-Node VLT system include, but are not limited to, higher resiliency, improved link utilization, and improved manageability of the network.
1. A management plane system for configuring one or more settings to form an n-node virtual link trunking (VLT) system comprising a plurality of nodes communicatively coupled via inter-node port links (INLs) and at least some of the plurality of nodes of the n-node VLT system being communicatively coupled via one or more input/output (I/O) ports to at least one client device to form a VLT link aggregation group (LAG), the management plane system comprising:
a management client operating on a first computing system that provides a centralized interface to a user to configure one or more fabric-level settings for the n-node VLT system to provide consistency of fabric-level settings while allowing individualized configuration of node-level settings for nodes in the n-node VLT system;
a fabric master operating on a node in the n-node VLT system that is communicatively coupled to the management client and communicatively coupled to the other nodes in the n-node VLT system and that, responsive to receiving a fabric-level configuration transaction from the management client, transforms the fabric-level configuration transaction into one or more configuration requests; and
a fabric standby operating on at least one of the other nodes in the n-node VLT system that is communicatively coupled to the fabric master.
2. The system of claim 1 wherein the fabric-level configuration transaction comprises affecting configuration of at least one or more VLT fabric entities, the VLT fabric entities comprising:
a domain entity, the domain entity having a domain identifier and its configuration parameter comprising a system media access control (MAC) address for the n-node VLT system;
nodes entities comprising, for each node in the n-node VLT system, a node identifier and configuration parameters comprising management port identifier and its IP address, and default route;
port channels entities comprising, for each port channel, a port channel identifier and configuration parameters comprising a list of ports, port channel type (INL or VLT), mode, and listing of virtual local area network or networks to which the port channel participates;
inter-node link (INL) entities comprising, for each INL, an INL identifier and configuration parameters comprising a pair of node identifiers of the nodes that are connected by the INL and corresponding port channel identifier; and
virtual link trunking (VLT) entities comprising, for each VLT, a VLT identifier and configuration parameters comprising a list of ports that participate in the VLT and corresponding port channel identifier.
3. The system of claim 1 wherein the management client provides a single point of management for the n-node VLT system via a virtual Internet Protocol (IP) address.
4. The system of claim 3 wherein, responsive to the node with fabric master failing, the fabric standby of one of the other nodes is elevated to the role of fabric master.
5. The system of claim 4 wherein an election mechanism operating on one or more of the fabric standbys selects a node in the n-node VLT system to become the fabric master.
6. The system of claim 1 wherein the fabric manager synchronizes a set of changes to the n-node VLT system to one or more databases of the fabric standbys.
7. The system of claim 6 wherein the fabric manager uses transaction-based configuration with commit/rollback capability across all the nodes in the n-node VLT system.
8. The system of claim 1 wherein two or more nodes in the n-node system act as fabric master and synchronize fabric-level changes across the nodes of the n-node VLT system.
9. A network node device comprising:
a plurality of input/output (I/O) ports, at least a portion of which facilitate communications with one or more client devices and configurable to participate in one or more virtual link trunkings (VLT), each of the one or more VLTs including the network node device and at least one of the one or more client devices;
a plurality of inter-node-link (INL) ports, at least a portion of which facilitate communications with one or more of network node devices in an n-node virtual link trunking (VLT) system, which comprises the network node device and a plurality of network node devices;
a data processing component that processes data packets, and receives data from and sends data to at least some of the plurality of I/O ports and at least some of the plurality of inter-node-link ports;
a fabric master that is communicatively coupled to a management client and communicatively coupled to the other network nodes in the n-node VLT system and that, responsive to receiving a fabric-level configuration transaction from the management client, transforms the fabric-level configuration transaction into one or more configuration requests for applicable network nodes in the n-node VLT system; and
at least one fabric-level logical-components database that stores information with respect to the n-node VLT system such that each of the one or more VLTs that includes the network node device and at least one of the one or more peer network node devices of the n-node VLT system is identified in the at least one fabric-level logical-components database with a VLT identifier that is common to the network node device and the at least one of the one or more peer network node devices but that is unique to that VLT.
10. The network node device of claim 9 wherein the plurality of INL ports are configured such that the network node device is in a full mesh topology with the plurality of peer network node devices of the n-node VLT system.
11. The network node of claim 9 wherein the fabric-level configuration transaction comprises affecting configuration of at least one or more VLT fabric entities, the VLT fabric entities comprising:
a domain entity, the domain entity having a domain identifier and its configuration parameter comprising a system media access control (MAC) address for the n-node VLT system;
nodes entities comprising, for each network node in the n-node VLT system, a node identifier and configuration parameters comprising management port identifier and its IP address, and default route;
port channels entities comprising, for each port channel, a port channel identifier and configuration parameters comprising a list of ports, port channel type (INL or VLT), mode, and listing of virtual local area network or networks to which the port channel participates;
inter-node link (INL) entities comprising, for each INL, an INL identifier and configuration parameters comprising a pair of network node identifiers of the network nodes that are connected by the INL and corresponding port channel identifier; and
virtual link trunking (VLT) entities comprising, for each VLT, a VLT identifier and configuration parameters comprising a list of ports that participate in the VLT and corresponding port channel identifier.
12. The network node device of claim 9 wherein the fabric manager communicates the one or more configuration requests to application programming interfaces of the network nodes in the n-node VLT system.
13. The network node device of claim 9 wherein a fabric standby operates on at least one of the other network nodes in the n-node VLT system that is communicatively coupled to the fabric master.
14. The network node device of claim 9 wherein the fabric manager is accessed by the management client via a virtual Internet Protocol (IP) address.
15. The network node device of claim 13 wherein the fabric standby comprises a fabric-level logical-components database and the fabric manager synchronize a set of changes to the n-node VLT system to databases of the fabric standby.
16. The network node device of claim 15 wherein the fabric manager uses transaction-based configuration with commit/rollback capability across all the network nodes in the n-node VLT system.
17. A method for managing fabric-level entities of a n-node virtual link trunking (VLT) system that comprises a plurality of nodes communicatively coupled via inter-node port links (INLs) and at least some of the plurality of nodes of the n-node VLT system being communicatively coupled via one or more input/output (I/O) ports to one or more client devices to form one or more VLTs, the method comprising:
presenting to a user via a management interface operating on a first computing device a centralized interface to configure one or more fabric-level settings for the n-node VLT system, the management interface communicatively coupled to a fabric master operating on a first node in the n-node VLT system that is communicatively coupled to the other nodes in the n-node VLT system; and
responsive to sending a fabric-level configuration transaction from the management client to the fabric master, transforming the fabric-level configuration transaction into one or more configuration requests for applicable nodes in the n-node VLT system; and
communicating the one or more configuration requests from the fabric master to the applicable nodes in the n-node VLT system.
18. The method of claim 17 wherein the fabric-level configuration transaction comprises affecting configuration of at least one or more VLT fabric entities, the VLT fabric entities comprising:
a domain entity, the domain entity having a domain identifier and its configuration parameter comprising a system media access control (MAC) address for the n-node VLT system;
node entities comprising, for each node in the n-node VLT system, a node identifier and configuration parameters comprising management port identifier and its IP address, and default route;
port channels entities comprising, for each port channel, a port channel identifier and configuration parameters comprising a list of ports, port channel type (INL or VLT), mode, and listing of virtual local area network or networks to which the port channel participates;
inter-node link (INL) entities comprising, for each INL, an INL identifier and configuration parameters comprising a pair of node identifiers of the nodes that are connected by the INL and corresponding port channel identifier; and
virtual link trunking (VLT) entities comprising, for each VLT, a VLT identifier and configuration parameters comprising a list of ports that participate in the VLT and corresponding port channel identifier.
19. The method of claim 17 further comprising:
maintaining a consistent representation of the fabric level of the n-node VLT system by synchronizing fabric-level information across the plurality of nodes of the n-node VLT systems.
20. The method of claim 17 wherein the step of communicating comprises:
using a single distributed transaction to invoke one or more nodes-level application programming interfaces in parallel to propagate the request across the nodes of the n-node VLT system.