Patent classifications
H04L12/4666
Logical Router Comprising Disaggregated Network Elements
A logical router includes disaggregated network elements that function as a single router and that are not coupled to a common backplane. The logical router includes spine elements and leaf elements implementing a network fabric with front panel ports being defined by leaf elements. Control plane elements program the spine units and leaf to function a logical router. The control plane may define operating system interfaces mapped to front panel ports of the leaf elements and referenced by tags associated with packets traversing the logical router. Redundancy and checkpoints may be implemented for a route database implemented by the control plane elements. The logical router may include a standalone fabric and may implement label tables that are used to label packets according to egress port and path through the fabric.
Logical Router Comprising Disaggregated Network Elements
A logical router includes disaggregated network elements that function as a single router and that are not coupled to a common backplane. The logical router includes spine elements and leaf elements implementing a network fabric with front panel ports being defined by leaf elements. Control plane elements program the spine units and leaf to function a logical router. The control plane may define operating system interfaces mapped to front panel ports of the leaf elements and referenced by tags associated with packets traversing the logical router. Redundancy and checkpoints may be implemented for a route database implemented by the control plane elements. The logical router may include a standalone fabric and may implement label tables that are used to label packets according to egress port and path through the fabric.
Logical Router Comprising Disaggregated Network Elements
A logical router includes disaggregated network elements that function as a single router and that are not coupled to a common backplane. The logical router includes spine elements and leaf elements implementing a network fabric with front panel ports being defined by leaf elements. Control plane elements program the spine units and leaf to function a logical router. The control plane may define operating system interfaces mapped to front panel ports of the leaf elements and referenced by tags associated with packets traversing the logical router. Redundancy and checkpoints may be implemented for a route database implemented by the control plane elements. The logical router may include a standalone fabric and may implement label tables that are used to label packets according to egress port and path through the fabric.
VLAN reflection
A network edge device may be placed at a location to participate in a VLAN using a specific VLAN ID without expressly programming the network edge device to use that specific VLAN ID. The network edge device is connected to a network to receive ingressing frames from the network and to send egressing frames to the network. The network edge device copies a specific VLAN ID from an ingressing VLAN message into memory and subsequently reads the specific VLAN ID from the memory for use in tagging frames egressing from the network edge device with the specific VLAN ID so that the egressing frames are VLAN conformant. The network edge device may communicate with non-edge devices at the same location as the network edge device.
PROVIDING VIRTUAL NETWORKING FUNCTIONALITY FOR MANAGED COMPUTER NETWORKS
Techniques are described for providing virtual networking functionality for managed computer networks. In some situations, a user may configure or otherwise specify one or more virtual local area networks (VLANs) for a managed computer network being provided for the user, such as with each VLAN including multiple computing nodes of the managed computer network. Networking functionality corresponding to the specified VLAN(s) may then be provided in various manners, such as if the managed computer network itself is a distinct virtual computer network overlaid on one or more other computer networks, and communications between computing nodes of the managed virtual computer network are handled in accordance with the specified VLAN(s) of the managed virtual computer network by emulating functionality that would be provided by networking devices of the managed virtual computer network if they were physically present and configured to support the specified VLAN(s).
FORWARDING PACKET
Provided are a method and an apparatus for forwarding a packet. Based on an example of the method, in a case of receiving an upstream Q-in-Q protocol packet through a port connected to an access device, an Edge Stream Gateway (ESGW) device forwards the upstream Q-in-Q protocol packet to a Virtual Broadband Remote Access Server (vBRAS) device through a Virtual eXtensible Local Area Network (VXLAN) tunnel between the ESGW device and the vBRAS device; in a case of receiving an upstream Q-in-Q data packet through a port connected to the access device, the ESGW device removes a Q-in-Q tag of the upstream Q-in-Q data packet, determines that a destination Media Access Control (MAC) address of the upstream Ethernet data packet without the Q-in-Q tag is an MAC address of the ESGW device, and performs layer-3 forwarding based on a destination IP address of the upstream Ethernet data packet.
SYSTEM AND METHOD FOR A MULTI-TENANT DATACENTER WITH LAYER 2 INTERCONNECTION
Provided is a system and method for a multi-tenant datacenter with layer 2 cloud interconnection and cloud storage. More specifically, the datacenter providing cloud storage, includes a plurality of Client Systems coupled to a first datacenter each Client System having a set of infrastructure resources and an initial networking configuration; and a first cloud computing environment established in the first datacenter, and coupled to the Client Systems by OSI Layer 2 as a data link layer for the transfer of data frames, each frame having a plurality of OSI Layer 2 tags, the first cloud computing environment providing storage resources for allocation to at least two Client Systems, the plurality of OSI Layer 2 tags permitting the at least two Client Systems to have overlapping network configurations. An associated method of providing a multi-tenant datacenter with layer 2 cloud interconnection and cloud storage is also provided.
METHODS AND SYSTEMS FOR VIRTUAL TOR IMPLEMENTATION
In one aspect, a computerized method includes the step of providing a first virtual machine on first server. The method includes the step of, with the first virtual machine, communicating a network traffic to a second virtual machine on a second server using a virtual network identified with a virtual local area network (VLAN). The method includes the step of, with a virtual function (VF) on a physical network interface controller (pNIC) of the second server, assigning to the VLAN to a specified VF. The method includes the step of, sending a data packet is sent out of the pNIC towards a TOR switch, wherein the TOR switch has the VLAN enabled and other user specific policies configured. The method includes the step of, sending the data packet to a second TOR switch. The method includes the step of, with the second TOR switch, sending the data packet towards the pNIC on the second server based on a destination the second virtual machine's MAC address. The method includes the step of, with the VF on pNIC on the second server, receiving the data packet via the VLAN. The method includes the step of determining the destination MAC address and sends the data packet to the VM on the second server after removing a VLAN tag.
SELECTION OF MANAGED FORWARDING ELEMENT FOR BRIDGE SPANNING MULTIPLE DATACENTERS
Some embodiments provide a method for a set of central controllers that manages forwarding elements operating in a plurality of datacenters. The method receives a configuration for a bridge between (i) a logical L2 network that spans at least two datacenters and (ii) a physical L2 network. The configuration specifies a particular one of the datacenters for implementation of the bridge. The method identifies multiple managed forwarding elements that implement the logical L2 network and are operating in the particular datacenter. The method selects one of the identified managed forwarding elements to implement the bridge. The method distributes bridge configuration data to the selected managed forwarding element.
SWITCHING DEVICE, COMMUNICATION CONTROL METHOD AND COMMUNICATION CONTROL PROGRAM
A switching device relays data in an on-vehicle network and has a plurality of communication ports. The switching device comprises: a detection unit that detects a failure in communication with another switching device connected to one of the communication ports; and a processing unit that transmits failure information indicating at least any one of a site where the failure in communication occurs and a communication port to be used when the failure in communication occurs by a target switching device being a switching device different from said another switching device, to the target switching device if the failure in communication is detected by the detection unit.