Managing virtual port channel switch peers from software-defined network controller
US-2018069754-A1 · Mar 8, 2018 · US
US11431548B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11431548-B2 |
| Application number | US-202016813142-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 9, 2020 |
| Priority date | Apr 29, 2016 |
| Publication date | Aug 30, 2022 |
| Grant date | Aug 30, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments for a method of implementing multiple domains in a network switching device are disclosed. The method includes assigning a plurality of hardware ports to a plurality of domains. Ports are assigned to at least two of the plurality of domains, and none of the ports are concurrently assigned to multiple domains. The method also includes loading rules for forwarding packets between the plurality of ports into a data plane. The rules direct the data plane to forward only between ports in a common domain of the plurality of domains. The method also includes assuring that a packet received at any port assigned to a first domain is not sent in legible form from any port assigned to a second domain if an error causes the data plane to forward or request forwarding the packet to any port assigned to a second domain.
Opening claim text (preview).
What is claimed is: 1. A program product for implementing multiple domains in a network switching device having a plurality of hardware ports, the program product comprising: instructions which, when executed by one or more processing devices, cause the one or more processing devices to: assign the plurality of hardware ports to a plurality of domains with a port assignment manager, wherein hardware ports are assigned to at least two of the plurality of domains, and none of the plurality of hardware ports are concurrently assigned to multiple domains of the plurality of domains, wherein hardware ports can only be assigned by the port assignment manager; maintain first forwarding rules for a first domain with a first forwarding rule custodian, wherein the first forwarding rules direct forwarding only between hardware ports assigned to the first domain in accordance with the assignment from the port assignment manager; and maintain second forwarding rules for a second domain with a second forwarding rule custodian, wherein the second forwarding rules direct forwarding only between hardware ports assigned to the second domain in accordance with the assignment from the port assignment manager. 2. The program product of claim 1 , wherein the instructions cause the one or more processing devices to: restrict access of the first forwarding rule custodian to hardware ports, wherein access is restricted for ports assigned to a domain other than the first domain; and restrict access of the second forwarding rule custodian to hardware ports, wherein access is restricted for ports assigned to a domain other than the second domain. 3. The program product of claim 1 , wherein the first forwarding rule custodian is executed in a first virtual machine of a hypervisor, the second forwarding rule custodian is executed in a second virtual machine of the hypervisor, and the port assignment manager is executed in a third virtual machine of the hypervisor. 4. The program product of claim 1 , wherein the first forwarding rule custodian, the second forwarding rule custodian, and the port assignment manager are executed on a secure kernel. 5. The program product of claim 1 , wherein the instructions cause the one or more processing devices to: forward packets for the first domain with a first software implemented traffic forwarding engine, wherein the first software implemented traffic forwarding engine forwards packets only, in accordance with the first forwarding rules from the first forwarding rule custodian; and forward packets for the second domain with a second software implemented traffic forwarding engine, wherein the second software implemented traffic forwarding engine forwards packets only in accordance with the second forwarding rules from the second forwarding rule custodian. 6. The program product of claim 5 , wherein the instructions cause the one or more processing devices to: deny requests of the first software implemented traffic forwarding engine that are directed to hardware ports assigned to a domain other than the first domain; and deny requests of the second software implemented traffic forwarding engine that are directed to hardware ports assigned to a domain other than the second domain. 7. The program product of claim 5 , wherein the first forwarding rule custodian is executed in a first virtual machine of a hypervisor, the second forwarding rule custodian is executed in a second virtual machine of the hypervisor, the port assignment manager is executed in a third virtual machine of the hypervisor, the first software implemented traffic forwarding engine is executed in a fourth virtual machine of the hypervisor, and the second software implemented traffic forwarding engine is executed in a fifth virtual machine of the hypervisor. 8. The program product of claim 7 , wherein a first set of hardware ports are assigned to the first domain and a second set of hardware ports are assigned to the second domain, wherein the instructions cause the one or more processing devices to: execute a first one or more port hardware controllers for the first set of hardware ports, and a second one or more port hardware controllers for the second set of hardware ports, each port hardware controller of the first one or more port hardware controllers and the second one or more port hardware controllers executing in a distinct virtual machine implemented by the hypervisor, wherein each port hardware controller of the first one or more port hardware controllers and the second one or more port hardware controllers implements a TCP/IP stack for a corresponding hardware port. 9. The program product of claim 8 , wherein the instructions cause the one or more processing devices to: re-assigning one or more ports of the first set of ports by: removing the one or more ports from the first domain, wherein removing the one or more ports from the first domain includes: destroying the respective port hardware controller corresponding to each of the one or more ports or revoking access to the respective port hardware controller corresponding to each of the one or more ports for the virtual machine corresponding to the first software implemented traffic forwarding engine; and instructing the first forwarding rule custodian to no longer direct forwarding to or from the one or more ports; assigning the one or more ports to the second domain, wherein assigning the one or more ports to the second domain includes: granting access to a respective port hardware controller for each of the one or more ports for the virtual machine corresponding to the second software implemented traffic forwarding engine; and instructing the second forwarding rule custodian to direct forwarding to and from the one or more ports. 10. The program product of claim 5 , wherein the first forwarding rule custodian, the second forwarding rule custodian, the port assignment manager, the first software implemented traffic forwarding engine, and the second software implemented traffic forwarding engine are executed on a secure kernel. 11. The program product of claim 1 , wherein the port assignment manager only assigns a hardware port to a domain in response to a command from the network manager, wherein the network switching device receives the command from the network manager over a network link. 12. The program product of claim 11 , wherein a first pair of hardware ports on the network switching device are not assigned to any domain and are used for network communications between the port assignment manager and the network manager, the communications including commands instructing the port assignment manager to assign a first set of hardware ports to the first domain and a second set of hardware ports to the second domain. 13. The program product of claim 1 , wherein the first forwarding rule custodian directs forwarding between all the ports of the plurality of ports assigned to the first domain, wherein the second forwarding rule custodian directs forwarding between all the ports of the plurality of ports assigned to the second domain. 14. The program product of claim 1 , wherein the port assignment manager is configured to: direct the first forwarding rule custodian to use only memory within a first block; and direct the second forwarding rule custodian to use only memory within a second block, wherein the second block does not overlap the first block. 15. The program product of claim 1 , wherein the instructions cause the one or more processing devices to: encrypt outgoing packets and decrypt incoming packets at the plurality of hardware ports using a differen
Routing or path finding in a switch fabric · CPC title
Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272) · CPC title
among multiple network domains, e.g. multilateral agreements · CPC title
Interdomain routing, e.g. hierarchical routing · CPC title
LAN interconnection over a bridge based backbone · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.