Cost aware routing in a network topology to reduce costs within an egress-based pricing model. A method includes receiving telemetry data from one or more of a network device or a compute device within a cloud computing network, wherein the telemetry data is associated with a customer of the cloud computing network. The method includes retrieving an egress-based pricing scheme associated with a provider of the cloud computing network and provisioning one or more of the network device or the compute device to optimize routing decisions for the customer to reduce a predicted data egress charge for the customer.
Cost aware routing in a network topology to reduce costs within an egress-based pricing model. A method includes receiving telemetry data from one or more of a network device or a compute device within a cloud computing network, wherein the telemetry data is associated with a customer of the cloud computing network. The method includes retrieving an egress-based pricing scheme associated with a provider of the cloud computing network and provisioning one or more of the network device or the compute device to optimize routing decisions for the customer to reduce a predicted data egress charge for the customer. A route may be selected to traverse multiple clouds and/or colocation providers according to ingress, egress, and transfer charges. Segment routing and VRFs may be used to implement routes selected based on criteria such as cost, latency, throughput, and jitter.
H04L 45/76 - Routing in software-defined topologies, e.g. routing between virtual machines
H04L 41/0826 - Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network costs
Cost aware routing in a network topology to reduce costs within an egress-based pricing model. A method includes receiving telemetry data from one or more of a network device or a compute device within a cloud computing network, wherein the telemetry data is associated with a customer of the cloud computing network. The method includes retrieving an egress-based pricing scheme associated with a provider of the cloud computing network and provisioning one or more of the network device or the compute device to optimize routing decisions for the customer to reduce a predicted data egress charge for the customer.
Cost aware routing in a network topology to reduce costs within an egress-based pricing model. A method includes receiving telemetry data from one or more of a network device or a compute device within a cloud computing network, wherein the telemetry data is associated with a customer of the cloud computing network. The method includes retrieving an egress-based pricing scheme associated with a provider of the cloud computing network and provisioning one or more of the network device or the compute device to optimize routing decisions for the customer to reduce a predicted data egress charge for the customer. A route may be selected to traverse multiple clouds and/or colocation providers according to ingress, egress, and transfer charges. Segment routing and VRFs may be used to implement routes selected based on criteria such as cost, latency, throughput, and jitter.
Prevention of SIM spoofing in mobile user plane. A method includes establishing a session for a user equipment to communicate with a session management function (SMF) and a user plane function (UPF), and then snooping a message between the SMF and the UPF to acquire one or more of an address for the user equipment, a tunnel endpoint identifier, or an address for a node within a radio access network. The method includes generating a route for carrying the one or more of the address for the user equipment, the tunnel endpoint identifier, or the address for the node within the radio access network, and then providing the route to a router.
Prevention of SIM spoofing in mobile user plane. A method includes generating a border gateway protocol (BGP) flow specification based on a range of Internet Protocol (IP) addresses associated with routes for one or more user equipment devices. The method includes, in response to receiving a packet from a node within a radio access network, verifying an inner IP packet encapsulation based on the BGP flow specification.
Prevention of SIM spoofing in mobile user plane. A system includes a session management function (SMF) within a radio access network and a user plane function (UPF) within the radio access network, wherein the UPF communicates with the SMF. The system includes a packet forwarding control protocol (PFCP) proxy between the SMF and the UPF, wherein the PFCP proxy snoops PF CP messages between the SMF and the UPF.
Prevention of SIM spoofing in mobile user plane. A system includes a session management function (SMF) within a radio access network and a user plane function (UPF) within the radio access network, wherein the UPF communicates with the SMF. The system includes a packet forwarding control protocol (PFCP) proxy between the SMF and the UPF, wherein the PFCP proxy snoops PFCP messages between the SMF and the UPF.
Prevention of SIM spoofing in mobile user plane. A method includes establishing a session for a user equipment to communicate with a session management function (SMF) and a user plane function (UPF), and then snooping a message between the SMF and the UPF to acquire one or more of an address for the user equipment, a tunnel endpoint identifier, or an address for a node within a radio access network. The method includes generating a route for carrying the one or more of the address for the user equipment, the tunnel endpoint identifier, or the address for the node within the radio access network, and then providing the route to a router.
Prevention of SIM spoofing in mobile user plane. A method includes generating a border gateway protocol (BGP) flow specification based on a range of Internet Protocol (IP) addresses associated with routes for one or more user equipment devices. The method includes, in response to receiving a packet from a node within a radio access network, verifying an inner IP packet encapsulation based on the BGP flow specification.
A computing environment, such as a cloud computing environment, may include nodes performing NAT for a plurality of workloads. An active node performs NAT for the workloads, including maintaining a NAT table. The active node may create sub-interfaces for the workloads and function as a DHCP server. The NAT table and sub-interfaces may be recreated on a standby node. Upon detecting failure, a routing table is updated to direct workloads to connect to the standby node and traffic may continue to be processed by the standby node without disrupting network or application sessions.
H04L 41/0816 - Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
H04L 67/1008 - Server selection for load balancing based on parameters of servers, e.g. available memory or workload
H04L 67/1034 - Reaction to server failures by a load balancer
H04L 101/622 - Layer-2 addresses, e.g. medium access control [MAC] addresses
12.
METHOD AND APPARATUS FOR TELEMETRY MONITORING OF BGP PREFIXES IN A NETWORK TOPOLOGY
Telemetry monitoring of BGP prefixes in a network topology. A system includes a plurality of input topic streams and a plurality of processors, wherein each of the plurality of processors is dedicated to one or more of the plurality of input topic streams. The system includes a plurality of stream stores for storing data, wherein each of the plurality of stream stores is dedicated to one or more of the plurality of input topic streams. The system includes a route processor in communication with each of the plurality of stream stores, wherein the route processor determines whether a route for a network topology corresponds with an existing route stored on at least one of the plurality of stream stores.
Telemetry monitoring of BGP prefixes in a network topology. A method includes receiving a route for a network topology and determining whether the route corresponds with an existing route stored on a route store. The method includes determining whether any network routing paths have been modified between the existing route and the route in response to determining the route corresponds with the existing route. The method includes generating a path configuration key for each of the at least one network routing path in response to determining at least one network routing path was modified between the existing route and the route.
Telemetry monitoring of BGP prefixes in a network topology. A method includes receiving a route for a network topology and determining whether the route corresponds with an existing route stored on a route store. The method includes determining whether any network routing paths have been modified between the existing route and the route in response to determining the route corresponds with the existing route. The method includes generating a path configuration key for each of the at least one network routing path in response to determining at least one network routing path was modified between the existing route and the route.
Telemetry monitoring of BGP prefixes in a network topology. A system includes a plurality of input topic streams and a plurality of processors, wherein each of the plurality of processors is dedicated to one or more of the plurality of input topic streams. The system includes a plurality of stream stores for storing data, wherein each of the plurality of stream stores is dedicated to one or more of the plurality of input topic streams. The system includes a route processor in communication with each of the plurality of stream stores, wherein the route processor determines whether a route for a network topology corresponds with an existing route stored on at least one of the plurality of stream stores.
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (IRB) service for the plurality of host virtual machines of the host routed overlay.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes a plurality of instances of a datastore node in a single networking device, each of the plurality of instances of the datastore node comprising: a datastore; a publisher independent of the datastore for publishing data to the datastore; a subscriber independent of the datastore for receiving information from the datastore; a replicator agent configured to connect to the datastore as a publisher or a subscriber; and a persistent storage agent configured to connect to the datastore as a publisher or a subscriber.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes routing chip hardware and an asynchronous object manager in communication with the routing chip hardware. The asynchronous object manager is configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include asynchronously receiving a plurality of objects from one or more producers. The instructions include identifying one or more dependencies between two or more of the plurality of objects. The instructions include reordering the plurality of objects according to the one or more dependencies. The instructions include determining whether the one or more dependencies is resolve. The instructions include, in response to determining the one or more dependencies is resolved, calling back an application and providing one or more of the plurality of objects to the application.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems and methods for improved data routing in network topologies. A method includes generating a configuration template for a network topology based on a topology descriptor file, wherein the network topology comprises a plurality of nodes, and wherein the topology descriptor file comprises a plurality of unique node tag identifiers that are each assigned to a node of the plurality of nodes within the network topology. The method includes resolving each of the plurality of unique node tag identifiers based on the plurality of nodes within the network topology and generating a network configuration for the network topology.
Systems and methods for improved data routing in network topologies. A method includes generating a configuration template for a network topology based on a topology descriptor file, wherein the network topology comprises a plurality of nodes, and wherein the topology descriptor file comprises a plurality of unique node tag identifiers that are each assigned to a node of the plurality of nodes within the network topology. The method includes resolving each of the plurality of unique node tag identifiers based on the plurality of nodes within the network topology and generating a network configuration for the network topology.
Systems, methods, and devices for offloading network data to a datastore. A system includes a publisher device in a network computing environment. The system includes a subscriber device in the network computing environment. The system includes a datastore independent of the publisher device and the subscriber device, the datastore comprising one or more processors in a processing platform configurable to execute instructions stored in non-transitory computer readable storage media. The instructions includes receiving data from the publisher device. The instructions include storing the data across one or more of a plurality of shared storage devices. The instructions include providing the data to the subscriber device.
H04L 45/00 - Routing or path finding of packets in data switching networks
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 45/28 - Routing or path finding of packets in data switching networks using route fault recovery
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
H04L 45/50 - Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
H04L 49/25 - Routing or path finding in a switch fabric
23.
Host routed overlay with deterministic host learning and localized integrated routing and bridging
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (IRB) service for the plurality of host virtual machines of the host routed overlay.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
A cellular data communication network includes a gNodeB connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy snoops information and provides it to a BGP module that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF. The BGP module may program the first translation module with an SR policy associated with a binding SID that is bound to an interface to the gNodeB. The SR policy may invoke translation according to a function. The routing module may be programmed to embed GTP information in an SRH header that is used by the first translation module. BGP module may also distribute routing and VPN updates.
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.
A cellular data communication network includes a BBU connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy intercepts control packets of the UPF. Information snooped by the PFCP proxy is provided to a routing/SDN controller that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF.
A cellular data communication network includes a gNodeB connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy snoops information and provides it to a BGP module that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF. The BGP module may program the first translation module with an SR policy associated with a binding SID that is bound to an interface to the gNodeB. The SR policy may invoke translation according to a function. The routing module may be programmed to embed GTP information in an SRH header that is used by the first translation module. BGP module may also distribute routing and VPN updates.
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.
H04W 40/06 - Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources based on characteristics of available antennas
H04W 40/24 - Connectivity information management, e.g. connectivity discovery or connectivity update
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.
A cellular data communication network includes a gNodeB connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy snoops information and provides it to a BGP module that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF. The BGP module may program the first translation module with an SR policy associated with a binding SID that is bound to an interface to the gNodeB. The SR policy may invoke translation according to a function. The routing module may be programmed to embed GTP information in an SRH header that is used by the first translation module. BGP module may also distribute routing and VPN updates.
A cellular data communication network includes a BBU connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy intercepts control packets of the UPF. Information snooped by the PFCP proxy is provided to a routing/SDN controller that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF.
A cellular data communication network includes a gNodeB connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy snoops information and provides it to a BGP module that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF. The BGP module may program the first translation module with an SR policy associated with a binding SID that is bound to an interface to the gNodeB. The SR policy may invoke translation according to a function. The routing module may be programmed to embed GTP information in an SRH header that is used by the first translation module. BGP module may also distribute routing and VPN updates.
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.
H04W 40/24 - Connectivity information management, e.g. connectivity discovery or connectivity update
H04W 40/06 - Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources based on characteristics of available antennas
34.
Use of IP networks for routing of cellular data packets
A cellular data communication network includes a BBU connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy intercepts control packets of the UPF. Information snooped by the PFCP proxy is provided to a routing/SDN controller that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF.
A cellular data communication network includes a gNodeB connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy snoops information and provides it to a BGP module that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF. The BGP module may program the first translation module with an SR policy associated with a binding SID that is bound to an interface to the gNodeB. The SR policy may invoke translation according to a function. The routing module may be programmed to embed GTP information in an SRH header that is used by the first translation module. BGP module may also distribute routing and VPN updates.
A cellular data communication network includes a gNodeB connected to a UPF by an IP network. A first translation module translates GFP packets into IP packets transmitted over the IP network. A second translation module translates the IP packets back into IP packets and forwards the IP packets to the UPF. A PFCP proxy snoops information and provides it to a BGP module that programs the translation modules and a routing module to perform routing of packets in bypass of the UPF. The BGP module may program the first translation module with an SR policy associated with a binding SID that is bound to an interface to the gNodeB. The SR policy may invoke translation according to a function. The routing module may be programmed to embed GTP information in an SRH header that is used by the first translation module. BGP module may also distribute routing and VPN updates.
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.
H04L 67/101 - Server selection for load balancing based on network conditions
H04L 67/1008 - Server selection for load balancing based on parameters of servers, e.g. available memory or workload
H04L 67/1027 - Persistence of sessions during load balancing
H04L 67/145 - Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.
Systems, methods, and devices for offloading best path computations in a networked computing environment. A method includes storing in memory, by a best path controller, a listing of a plurality of paths learnt by a device, wherein each of the plurality of paths is a route for transmitting data from the device to a destination device. The method includes receiving, by the best path controller, a message from the device. The method includes processing, by the best path controller, a best path computation to identify one or more best paths based on the message such that processing of the best path computation is offloaded from the device to the best path controller. The method includes sending the one or more best paths to the device.
Systems, methods, and devices for offloading best path computations in a networked computing environment. A method includes storing in memory, by a best path controller, a listing of a plurality of paths learnt by a device, wherein each of the plurality of paths is a route for transmitting data from the device to a destination device. The method includes receiving, by the best path controller, a message from the device. The method includes processing, by the best path controller, a best path computation to identify one or more best paths based on the message such that processing of the best path computation is offloaded from the device to the best path controller. The method includes sending the one or more best paths to the device.
Disaggregated border gateway protocol (BGP) enables an eBGP session between an internal node an external node to continue despite failover of a perimeter through which the eBGP session is established. eBGP control traffic is trapped by a perimeter router and forwarded to a BGP speaker on the internal node through an IP tunnel. Failover is detected in response to a change in a source address of the IP tunnel over which eBGP control traffic is received. The BGP speaker announces routes to the external node that include a reference to an internal address of an active perimeter router. In response to failover, the BGP speaker announces updated routes referencing the standby router for the perimeter router.
A segment identifier (SID) manager interfaces with clients by way of a library. Clients implementing network services and needing SIDs according to internet SRv6, are allocated blocks by the SID manager using the library. Clients assign SIDs from the block independent of the SID manager using the library. Where a threshold portion of the block is assigned, the library requests an additional block of SIDs from the SID manager. Clients transmit context mappings of assigned SIDs to the SID manager for use by administrators and to enable recovery in the event of failure.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
H04L 41/0604 - Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
H04L 41/0654 - Management of faults, events, alarms or notifications using network fault recovery
H04L 47/74 - Admission controlResource allocation measures in reaction to resource unavailability
H04L 101/659 - Internet protocol version 6 [IPv6] addresses
Disaggregated border gateway protocol (BGP) enables an eBGP session between an internal node an external node to continue despite failover of a perimeter through which the eBGP session is established. eBGP control traffic is trapped by a perimeter router and forwarded to a BGP speaker on the internal node through an IP tunnel. Failover is detected in response to a change in a source address of the IP tunnel over which eBGP control traffic is received. The BGP speaker announces routes to the external node that include a reference to an internal address of an active perimeter router. In response to failover, the BGP speaker announces updated routes referencing the standby router for the perimeter router.
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04J 3/16 - Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
Disaggregated border gateway protocol (BGP) enables an eBGP session between an internal node an external node to continue despite failover of a perimeter through which the eBGP session is established. eBGP control traffic is trapped by a perimeter router and forwarded to a BGP speaker on the internal node through an IP tunnel. Failover is detected in response to a change in a source address of the IP tunnel over which eBGP control traffic is received. The BGP speaker announces routes to the external node that include a reference to an internal address of an active perimeter router. In response to failover, the BGP speaker announces updated routes referencing the standby router for the perimeter router.
Systems, methods, and devices for offloading network data to a datastore. A system includes routing chip hardware and an asynchronous object manager in communication with the routing chip hardware. The asynchronous object manager is configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include asynchronously receiving a plurality of objects from one or more producers. The instructions include identifying one or more dependencies between two or more of the plurality of objects. The instructions include reordering the plurality of objects according to the one or more dependencies. The instructions include determining whether the one or more dependencies is resolve. The instructions include, in response to determining the one or more dependencies is resolved, calling back an application and providing one or more of the plurality of objects to the application.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 45/586 - Association of routers of virtual routers
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (TRB) service for the plurality of host virtual machines of the host routed overlay.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 45/586 - Association of routers of virtual routers
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a network topology comprising a spine node and a plurality of leaf nodes. The system is such that at least one of the plurality of leaf nodes is associated with one or more networking prefixes. The spine node stores a prefix table. The prefix table includes a listing of networking prefixes in the network topology. The prefix table includes an indication of at least one equal-cost multipath routing (ECMP) group associated with each of the networking prefixes in the network topology. The prefix table includes an indication of at least one leaf node of the plurality of leaf nodes associated with each of the networking prefixes in the network topology.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
A computing environment, such as a cloud computing environment, may include nodes performing NAT for a plurality of workloads. An active node performs NAT for the workloads, including maintaining a NAT table. The active node may create sub-interfaces for the workloads and function as a DHCP server. The NAT table and sub-interfaces may be recreated on a standby node. Upon detecting failure, a routing table is updated to direct workloads to connect to the standby node and traffic may continue to be processed by the standby node without disrupting network or application sessions.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 41/0668 - Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
H04L 45/00 - Routing or path finding of packets in data switching networks
H04L 61/2514 - Translation of Internet protocol [IP] addresses between local and global IP addresses
H04L 61/2567 - NAT traversal for reachability, e.g. inquiring the address of a correspondent behind a NAT server
H04L 61/2596 - Translation of addresses of the same type other than IP, e.g. translation from MAC to MAC addresses
H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
A computing environment, such as a cloud computing environment, may include nodes performing NAT for a plurality of workloads. An active node performs NAT for the workloads, including maintaining a NAT table. The active node may create sub-interfaces for the workloads and function as a DHCP server. The NAT table and sub-interfaces may be recreated on a standby node. Upon detecting failure, a routing table is updated to direct workloads to connect to the standby node and traffic may continue to be processed by the standby node without disrupting network or application sessions.
H04L 41/0816 - Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
H04L 67/1008 - Server selection for load balancing based on parameters of servers, e.g. available memory or workload
H04L 67/1034 - Reaction to server failures by a load balancer
H04L 101/622 - Layer-2 addresses, e.g. medium access control [MAC] addresses
A computing environment, such as a cloud computing environment, may include nodes performing NAT for a plurality of workloads. An active node performs NAT for the workloads, including maintaining a NAT table. The active node may create sub-interfaces for the workloads and function as a DHCP server. The NAT table and sub-interfaces may be recreated on a standby node. Upon detecting failure, a routing table is updated to direct workloads to connect to the standby node and traffic may continue to be processed by the standby node without disrupting network or application sessions.
A segment identifier (SID) manager interfaces with clients by way of a library. Clients implementing network services and needing SIDs according to internet SRv6, are allocated blocks by the SID manager using the library. Clients assign SIDs from the block independent of the SID manager using the library. Where a threshold portion of the block is assigned, the library requests an additional block of SIDs from the SID manager. Clients transmit context mappings of assigned SIDs to the SID manager for use by administrators and to enable recovery in the event of failure.
Systems, methods, and devices for offloading network data to a datastore. A system includes a publisher device in a network computing environment. The system includes a subscriber device in the network computing environment. The system includes a datastore independent of the publisher device and the subscriber device, the datastore comprising one or more processors in a processing platform configurable to execute instructions stored in non-transitory computer readable storage media. The instructions includes receiving data from the publisher device. The instructions include storing the data across one or more of a plurality of shared storage devices. The instructions include providing the data to the subscriber device.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 45/586 - Association of routers of virtual routers
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading best path computations in a networked computing environment. A method includes storing in memory, by a best path controller, a listing of a plurality of paths learnt by a device, wherein each of the plurality of paths is a route for transmitting data from the device to a destination device. The method includes receiving, by the best path controller, a message from the device. The method includes processing, by the best path controller, a best path computation to identify one or more best paths based on the message such that processing of the best path computation is offloaded from the device to the best path controller. The method includes sending the one or more best paths to the device.
A segment identifier (SID) manager interfaces with clients by way of a library. Clients implementing network services and needing SIDs according to internet SRv6, are allocated blocks by the SID manager using the library. Clients assign SIDs from the block independent of the SID manager using the library. Where a threshold portion of the block is assigned, the library requests an additional block of SIDs from the SID manager. Clients transmit context mappings of assigned SIDs to the SID manager for use by administrators and to enable recovery in the event of failure.
A segment identifier (SID) manager interfaces with clients by way of a library. Clients implementing network services and needing SIDs according to internet SRv6, are allocated blocks by the SID manager using the library. Clients assign SIDs from the block independent of the SID manager using the library. Where a threshold portion of the block is assigned, the library requests an additional block of SIDs from the SID manager. Clients transmit context mappings of assigned SIDs to the SID manager for use by administrators and to enable recovery in the event of failure.
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.
H04L 45/586 - Association of routers of virtual routers
H04L 41/0668 - Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
H04L 49/552 - Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
Systems, methods, and devices for offloading best path computations in a networked computing environment. A method includes storing in memory, by a best path controller, a listing of a plurality of paths learnt by a device, wherein each of the plurality of paths is a route for transmitting data from the device to a destination device. The method includes receiving, by the best path controller, a message from the device. The method includes processing, by the best path controller, a best path computation to identify one or more best paths based on the message such that processing of the best path computation is offloaded from the device to the best path controller. The method includes sending the one or more best paths to the device.
09 - Scientific and electric apparatus and instruments
42 - Scientific, technological and industrial services, research and design
Goods & Services
Downloadable computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; downloadable operating system programs; downloadable WAN (wide area network) and SD-WAN (software defined wide area network) and operating software; downloadable computer software for use in securing and controlling WAN (wide area network) traffic, for multi-cloud networking, and for real-time monitoring and historical reporting of application, location and networking statistics; downloadable software for creating, delivering, deploying, configuring, orchestrating, integrating and managing virtualized computer applications in the fields of communications, data security, computer system performance, security and monitoring, data center deployment, management, and reference architecture; downloadable software for use in configuring, managing, monitoring, supporting and securing data, virtualization and computer hardware, applications and networks in the field of communications Providing temporary use of non-downloadable, cloud-based networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; providing temporary use of non-downloadable operating system programs and WAN (wide area network) and SD-WAN (software defined wide area network) operating software; providing temporary use of non-downloadable computer software for use in securing and controlling WAN (wide area network) traffic, for multi-cloud networking, and for real-time monitoring and historical reporting of application, location and networking statistics; providing temporary use of non-downloadable computer software for creating, delivering, deploying, configuring, orchestrating, integrating and managing virtualized computer applications in the fields of communications, data security, computer system performance, security and monitoring, data center deployment, management, and reference architecture; providing temporary use of non-downloadable software for use in configuring, managing, monitoring, supporting and securing data, virtualization and computer hardware, applications and networks in the field of communications; computer services, namely, providing technical consultation in the field of connectivity, interoperability and management capability among networked components and systems
09 - Scientific and electric apparatus and instruments
42 - Scientific, technological and industrial services, research and design
Goods & Services
Downloadable computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; downloadable operating system programs; downloadable WAN (wide area network) and SD-WAN (software defined wide area network) and operating software; downloadable computer software for use in securing and controlling WAN (wide area network) traffic, for multi-cloud networking, and for real-time monitoring and historical reporting of application, location and networking statistics; downloadable software for creating, delivering, deploying, configuring, orchestrating, integrating and managing virtualized computer applications in the fields of communications, data security, computer system performance, security and monitoring, data center deployment, management, and reference architecture; downloadable software for use in configuring, managing, monitoring, supporting and securing data, virtualization and computer hardware, applications and networks in the field of communications Providing temporary use of non-downloadable, cloud-based networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; providing temporary use of non-downloadable operating system programs and WAN (wide area network) and SD-WAN (software defined wide area network) operating software; providing temporary use of non-downloadable computer software for use in securing and controlling WAN (wide area network) traffic, for multi-cloud networking, and for real-time monitoring and historical reporting of application, location and networking statistics; providing temporary use of non-downloadable computer software for creating, delivering, deploying, configuring, orchestrating, integrating and managing virtualized computer applications in the fields of communications, data security, computer system performance, security and monitoring, data center deployment, management, and reference architecture; providing temporary use of non-downloadable software for use in configuring, managing, monitoring, supporting and securing data, virtualization and computer hardware, applications and networks in the field of communications; computer services, namely, providing technical consultation in the field of connectivity, interoperability and management capability among networked components and systems
60.
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.
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.
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.
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.
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.
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.
H04L 41/0668 - Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
H04L 41/0893 - Assignment of logical groups to network elements
H04L 41/12 - Discovery or management of network topologies
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.
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.
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.
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 12/24 - Arrangements for maintenance or administration
H04L 12/939 - Provisions for redundant switching, e.g. using parallel switching planes
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.
H04L 45/586 - Association of routers of virtual routers
H04L 41/0668 - Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
H04L 49/552 - Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
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.
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 12/24 - Arrangements for maintenance or administration
H04L 12/939 - Provisions for redundant switching, e.g. using parallel switching planes
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.
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 12/24 - Arrangements for maintenance or administration
H04L 12/939 - Provisions for redundant switching, e.g. using parallel switching planes
09 - Scientific and electric apparatus and instruments
Goods & Services
Downloadable computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; downloadable operating system programs
73.
FIRST HOP GATEWAY REDUNDANCY IN A NETWORK COMPUTING ENVIRONMENT
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a first switch and a second switch in a network topology. The system includes a host virtual machine in communication with at least one of the first switch and the second switch. The system includes a routed peer link connecting the first switch to the second switch. The system is such that the first switch and the second switch have the same Internet protocol (IP) address and media access control (MAC) address.
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes a publisher device in a network computing environment. The system includes a subscriber device in the network computing environment. The system includes a datastore independent of the publisher device and the subscriber device, the datastore comprising one or more processors in a processing platform configurable to execute instructions stored in non-transitory computer readable storage media. The instructions includes receiving data from the publisher device. The instructions include storing the data across one or more of a plurality of shared storage devices. The instructions include providing the data to the subscriber device.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
G06F 15/173 - Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star or snowflake
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes a publisher device in a network computing environment. The system includes a subscriber device in the network computing environment. The system includes a datastore independent of the publisher device and the subscriber device, the datastore comprising one or more processors in a processing platform configurable to execute instructions stored in non-transitory computer readable storage media. The instructions includes receiving data from the publisher device. The instructions include storing the data across one or more of a plurality of shared storage devices. The instructions include providing the data to the subscriber device.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
H04L 12/753 - Routing tree discovery, e.g. converting from mesh topology to tree topology
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/721 - Routing procedures, e.g. shortest path routing, source routing, link state routing or distance vector routing
G06F 9/48 - Program initiatingProgram switching, e.g. by interrupt
H04L 12/703 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP]
H04L 12/741 - Header address processing for routing, e.g. table lookup
H04L 12/803 - Load balancing, e.g. traffic distribution over multiple links
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
H04L 12/947 - Address processing within a device, e.g. using internal ID or tags for routing within a switch
76.
Routing optimizations in a network computing environment
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a network topology comprising a spine node and a plurality of leaf nodes. The system is such that at least one of the plurality of leaf nodes is associated with one or more networking prefixes. The spine node stores a prefix table. The prefix table includes a listing of networking prefixes in the network topology. The prefix table includes an indication of at least one equal-cost multipath routing (ECMP) group associated with each of the networking prefixes in the network topology. The prefix table includes an indication of at least one leaf node of the plurality of leaf nodes associated with each of the networking prefixes in the network topology.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
G06F 9/48 - Program initiatingProgram switching, e.g. by interrupt
H04L 12/703 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP]
H04L 12/803 - Load balancing, e.g. traffic distribution over multiple links
H04L 29/06 - Communication control; Communication processing characterised by a protocol
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
H04L 12/947 - Address processing within a device, e.g. using internal ID or tags for routing within a switch
77.
Host routed overlay with deterministic host learning and localized integrated routing and bridging
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (IRB) service for the plurality of host virtual machines of the host routed overlay.
H04L 12/753 - Routing tree discovery, e.g. converting from mesh topology to tree topology
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/721 - Routing procedures, e.g. shortest path routing, source routing, link state routing or distance vector routing
G06F 9/48 - Program initiatingProgram switching, e.g. by interrupt
H04L 12/703 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP]
H04L 12/741 - Header address processing for routing, e.g. table lookup
H04L 12/803 - Load balancing, e.g. traffic distribution over multiple links
H04L 29/06 - Communication control; Communication processing characterised by a protocol
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
H04L 12/947 - Address processing within a device, e.g. using internal ID or tags for routing within a switch
78.
Loop conflict avoidance in a spine-and-leaf network topology
Systems, methods, and devices for routing operations in a network computing environment. A system includes a network topology comprising a plurality of spine nodes and a plurality of leaf nodes, wherein a link between a first spine node and a first leaf node is inactive. The first spine node includes one or more processors configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include receiving a packet to be transmitted to the first leaf node. The instructions include identifying an alternative spine node at a same level in the network topology. The instructions include attaching a tunnel label to the packet, wherein the tunnel label indicates the packet should be transmitted to the alternative spine node.
H04L 12/753 - Routing tree discovery, e.g. converting from mesh topology to tree topology
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/721 - Routing procedures, e.g. shortest path routing, source routing, link state routing or distance vector routing
G06F 9/48 - Program initiatingProgram switching, e.g. by interrupt
H04L 12/703 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP]
H04L 12/741 - Header address processing for routing, e.g. table lookup
H04L 12/803 - Load balancing, e.g. traffic distribution over multiple links
H04L 29/06 - Communication control; Communication processing characterised by a protocol
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
H04L 12/947 - Address processing within a device, e.g. using internal ID or tags for routing within a switch
79.
First hop gateway redundancy in a network computing environment
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a first switch and a second switch in a network topology. The system includes a host virtual machine in communication with at least one of the first switch and the second switch. The system includes a routed peer link connecting the first switch to the second switch. The system is such that the first switch and the second switch have the same Internet protocol (IP) address and media access control (MAC) address.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes routing chip hardware and an asynchronous object manager in communication with the routing chip hardware. The asynchronous object manager is configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include asynchronously receiving a plurality of objects from one or more producers. The instructions include identifying one or more dependencies between two or more of the plurality of objects. The instructions include reordering the plurality of objects according to the one or more dependencies. The instructions include determining whether the one or more dependencies is resolve. The instructions include, in response to determining the one or more dependencies is resolved, calling back an application and providing one or more of the plurality of objects to the application.
G06F 13/28 - Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access, cycle steal
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a network topology comprising a spine node and a plurality of leaf nodes. The system is such that at least one of the plurality of leaf nodes is associated with one or more networking prefixes. The spine node stores a prefix table. The prefix table includes a listing of networking prefixes in the network topology. The prefix table includes an indication of at least one equal-cost multipath routing (ECMP) group associated with each of the networking prefixes in the network topology. The prefix table includes an indication of at least one leaf node of the plurality of leaf nodes associated with each of the networking prefixes in the network topology.
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a network topology comprising a plurality of spine nodes and a plurality of leaf nodes, wherein a link between a first spine node and a first leaf node is inactive. The first spine node includes one or more processors configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include receiving a packet to be transmitted to the first leaf node. The instructions include identifying an alternative spine node at a same level in the network topology. The instructions include attaching a tunnel label to the packet, wherein the tunnel label indicates the packet should be transmitted to the alternative spine node.
Systems, methods, and devices for offloading network data to a datastore. A system includes routing chip hardware and an asynchronous object manager in communication with the routing chip hardware. The asynchronous object manager is configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include asynchronously receiving a plurality of objects from one or more producers. The instructions include identifying one or more dependencies between two or more of the plurality of objects. The instructions include reordering the plurality of objects according to the one or more dependencies. The instructions include determining whether the one or more dependencies is resolve. The instructions include, in response to determining the one or more dependencies is resolved, calling back an application and providing one or more of the plurality of objects to the application.
G06F 13/28 - Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access, cycle steal
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a network topology comprising a spine node and a plurality of leaf nodes. The system is such that at least one of the plurality of leaf nodes is associated with one or more networking prefixes. The spine node stores a prefix table. The prefix table includes a listing of networking prefixes in the network topology. The prefix table includes an indication of at least one equal-cost multipath routing (ECMP) group associated with each of the networking prefixes in the network topology. The prefix table includes an indication of at least one leaf node of the plurality of leaf nodes associated with each of the networking prefixes in the network topology.
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes a plurality of instances of a datastore node in a single networking device, each of the plurality of instances of the datastore node comprising: a datastore; a publisher independent of the datastore for publishing data to the datastore; a subscriber independent of the datastore for receiving information from the datastore; a replicator agent configured to connect to the datastore as a publisher or a subscriber; and a persistent storage agent configured to connect to the datastore as a publisher or a subscriber.
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (IRB) service for the plurality of host virtual machines of the host routed overlay.
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a network topology comprising a plurality of spine nodes and a plurality of leaf nodes, wherein a link between a first spine node and a first leaf node is inactive. The first spine node includes one or more processors configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include receiving a packet to be transmitted to the first leaf node. The instructions include identifying an alternative spine node at a same level in the network topology. The instructions include attaching a tunnel label to the packet, wherein the tunnel label indicates the packet should be transmitted to the alternative spine node.
H04L 47/125 - Avoiding congestionRecovering from congestion by balancing the load, e.g. traffic engineering
H04L 49/25 - Routing or path finding in a switch fabric
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes routing chip hardware and an asynchronous object manager in communication with the routing chip hardware. The asynchronous object manager is configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include asynchronously receiving a plurality of objects from one or more producers. The instructions include identifying one or more dependencies between two or more of the plurality of objects. The instructions include reordering the plurality of objects according to the one or more dependencies. The instructions include determining whether the one or more dependencies is resolve. The instructions include, in response to determining the one or more dependencies is resolved, calling back an application and providing one or more of the plurality of objects to the application.
H04L 12/753 - Routing tree discovery, e.g. converting from mesh topology to tree topology
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/721 - Routing procedures, e.g. shortest path routing, source routing, link state routing or distance vector routing
G06F 9/48 - Program initiatingProgram switching, e.g. by interrupt
H04L 12/703 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP]
H04L 12/741 - Header address processing for routing, e.g. table lookup
H04L 12/803 - Load balancing, e.g. traffic distribution over multiple links
H04L 29/06 - Communication control; Communication processing characterised by a protocol
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
H04L 12/947 - Address processing within a device, e.g. using internal ID or tags for routing within a switch
89.
Single node and multiple node datastore architecture in a network routing environment
Systems, methods, and devices for offloading network data to a datastore. A system includes a plurality of instances of a datastore node in a single networking device, each of the plurality of instances of the datastore node comprising: a datastore; a publisher independent of the datastore for publishing data to the datastore; a subscriber independent of the datastore for receiving information from the datastore; a replicator agent configured to connect to the datastore as a publisher or a subscriber; and a persistent storage agent configured to connect to the datastore as a publisher or a subscriber.
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database systemDistributed database system architectures therefor
H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
H04L 45/586 - Association of routers of virtual routers
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Systems, methods, and devices for offloading network data to a datastore. A system includes a publisher device in a network computing environment. The system includes a subscriber device in the network computing environment. The system includes a datastore independent of the publisher device and the subscriber device, the datastore comprising one or more processors in a processing platform configurable to execute instructions stored in non-transitory computer readable storage media. The instructions includes receiving data from the publisher device. The instructions include storing the data across one or more of a plurality of shared storage devices. The instructions include providing the data to the subscriber device.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
G06F 15/173 - Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star or snowflake
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
91.
SINGLE NODE AND MULTIPLE NODE DATASTORE ARCHITECTURE IN A NETWORK ROUTING ENVIRONMENT
Systems, methods, and devices for offloading network data to a datastore. A system includes a plurality of instances of a datastore node in a single networking device, each of the plurality of instances of the datastore node comprising: a datastore; a publisher independent of the datastore for publishing data to the datastore; a subscriber independent of the datastore for receiving information from the datastore; a replicator agent configured to connect to the datastore as a publisher or a subscriber; and a persistent storage agent configured to connect to the datastore as a publisher or a subscriber.
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a virtual customer edge router and a host routed overlay comprising a plurality of host virtual machines. The system includes a routed uplink from the virtual customer edge router to one or more of the plurality of leaf nodes. The system is such that the virtual customer edge router is configured to provide localized integrated routing and bridging (IRB) service for the plurality of host virtual machines of the host routed overlay.
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
93.
FIRST HOP GATEWAY REDUNDANCY IN A NETWORK COMPUTING ENVIRONMENT
Systems, methods, and devices for improved routing operations in a network computing environment. A system includes a first switch and a second switch in a network topology. The system includes a host virtual machine in communication with at least one of the first switch and the second switch. The system includes a routed peer link connecting the first switch to the second switch. The system is such that the first switch and the second switch have the same Internet protocol (IP) address and media access control (MAC) address.
H04L 29/12 - Arrangements, apparatus, circuits or systems, not covered by a single one of groups characterised by the data terminal
H04L 12/66 - Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
H04L 12/713 - Route fault prevention or recovery, e.g. rerouting, route redundancy, virtual router redundancy protocol [VRRP] or hot standby router protocol [HSRP] using node redundancy, e.g. VRRP
H04L 12/715 - Hierarchical routing, e.g. clustered networks or inter-domain routing
H04L 12/721 - Routing procedures, e.g. shortest path routing, source routing, link state routing or distance vector routing
09 - Scientific and electric apparatus and instruments
Goods & Services
Downloadable computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; downloadable operating system programs
09 - Scientific and electric apparatus and instruments
42 - Scientific, technological and industrial services, research and design
Goods & Services
Computer networking software, namely, software that provides
connectivity, interoperability and management capability
among networked components and systems. Computer services, namely, providing technical consultation
in the field of connectivity, interoperability and
management capability among networked components and
systems.
09 - Scientific and electric apparatus and instruments
Goods & Services
computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; operating system programs
09 - Scientific and electric apparatus and instruments
Goods & Services
computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; operating system programs
09 - Scientific and electric apparatus and instruments
Goods & Services
computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems; operating system programs
09 - Scientific and electric apparatus and instruments
42 - Scientific, technological and industrial services, research and design
Goods & Services
computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems computer services, namely, providing technical consultation in the field of connectivity, interoperability and management capability among networked components and systems
09 - Scientific and electric apparatus and instruments
Goods & Services
Computer networking software, namely, software that provides connectivity, interoperability and management capability among networked components and systems
