Patent classifications
H04L45/56
SOFTWARE DEFINED NETWORK CONTROLLER FOR IMPLEMENTING TENANT SPECIFIC POLICY
Example implementations may relate to a software defined networking (SDN) controller. A method may include receiving, at a SDN controller, a tagged initialization packet from a software defined network enabled switch. The method may include identifying, at the SDN controller, a tenant corresponding to or based on the tagged initialization packet. The method may include implementing a policy specific to the identified tenant.
COMMUNICATION CONTROL DEVICE AND COMMUNICATION SYSTEM
There is provided a communication control device for controlling a communication device on a communication network, the communication control device including: a memory; a processor coupled with the memory and configured to: divide a route for a communication with the communication device into a plurality of sections; determine a communication control device for a failure recovery in a section of the plurality of sections, the communication control device for the failure recovery restoring a failure in the section of the plurality of sections; specify a section of the plurality of sections where the failure occurs when the failure is detected on the route; transmit failure information to the communication control device for the failure recovery corresponding to the section specified; and set a detour to the failure in the section, based on the failure information.
MOBILE ENDPOINT NETWORK INTERFACE SELECTION USING MERGED POLICIES
Methods, systems and computer readable media for mobile endpoint network interface selection using merged policies.
Packet forwarding path programming using a high-level description language
In general, this disclosure describes a high-level forwarding path description language (FPDL) for describing internal forwarding paths within a network device. The FPDL enables developers to create a template that describes a section of an internal forwarding path within the forwarding plane of a network device. The FPDL provides syntactical elements for specifying the allocation of forwarding path structures as well as enabling the run-time construction of internal forwarding paths to interconnect the forwarding path structures in a manner specific to packet, packet flow, and/or interface properties, for example. In conjunction with late binding techniques, whereby the control plane of the network device provides arguments to template parameters that drive allocation by the packet forwarding engines of forwarding path structures specified by the FPDL, the techniques provide control plane processes a unified interface with which to manage the operation of the packet forwarding engines.
Integrated server with switching capabilities and network operating system
Methods, systems, and computer programs are presented for a switching server. One switching server includes a server, a switch module coupled to the server, and a switch controller coupled to the server and to the switch module. The server includes a processor executing an operating system that includes a network driver, and the network driver includes a first network device operating system (ndOS) program. Further, the switch module includes a switch fabric and input/output ports. The switch controller includes a processor and non-volatile storage, where the processor is configured to execute a second ndOS program. The first and second ndOS programs implement a global networking policy for a plurality of devices executing ndOS programs, the global networking policy including a definition for switching incoming packets through the plurality of devices executing the ndOS programs.
Validating a routing function
Certain examples described herein provide a system and method for validating a routing function for a network device. In one example, a network device has a run-time policy engine, wherein the run-time policy engine implements a routing configuration file and the routing configuration file defines a routing function for network traffic. A file editor is also provided that loads the routing configuration file. The file editor has an editor policy engine that duplicates a functionality of the run-time policy engine. In one example, the routing configuration file has at least one validation portion that has one or more route statements with definitions indicative of expected routing function behavior. The file editor parses the routing configuration file by implementing the routing configuration file using the editor policy engine. The editor policy engine applies the routing function defined by the routing configuration file to the one or more route statements and indicates where a result of the routing function does not conform to the definitions indicative of expected routing function behavior. These examples may help to reduce routing errors due to configuration errors in network devices.
Variable-based forwarding path construction for packet processing within a network device
In general, this disclosure describes techniques for applying, with a network device, subscriber-specific packet processing using an internal processing path that includes service objects that are commonly applied to multiple packet flows associated with multiple subscribers. In one example, a network device control plane creates subscriber records that include, for respective subscribers, one or more variable values that specify service objects as well as an identifier for a packet processing template. A forwarding plane of the network device receives and maps subscriber packets to an associated subscriber record and then processes the packet by executing the packet processing template specified by the subscriber record. When the forwarding plane reaches a variable while executing the specified packet processing template, the forwarding plane reads the associated variable value from the subscriber record to identify and then apply the subscriber-specific service object specified by the variable.
USING CLIENT DEVICE TO OPTIMIZE WIRELESS DRIVER RESTARTS IN ROUTER ON CHANGING NETWORK CONFIGURATION SETTINGS
A client device for use with a router having a radio, a first configurable feature, and a second configurable feature, the client device comprising: a memory; and a processor configured to execute instructions stored on the memory to cause the client device to: generate a first instruction to configure the first configurable feature; generate a second instruction to configure the second configurable feature; and transmit a queued-configuration signal, including the first instruction and the second instruction, to the router so as to reconfigure the first configurable feature, reconfigure the second reconfigurable feature, and turn off and restart the radio.
Data processing system with routing tables
A data processing system with routing tables comprising an operating system for supporting processes, such that the process are associated with one or more resources and the operating system being arranged to police the accessing by processes of resources so as to inhibit a process from accessing resources with which it is not associated. Part of this system is an interface for interfacing between each process and the operating system and a memory for storing state information for at least one process. The interface may be arranged to analyze instructions from the processes to the operating system, and upon detecting an instruction to re-initialize a process cause state information corresponding to that pre-existing state information to be stored in the memory as state information for the re-initialized process and to be associated with the resource.
Method and system for route hardware programming in network devices
A method for programming route hardware in network devices. The method includes: receiving, by a network device, route updates, selecting from the route updates, a set of selected routes to be used for routing, assigning multiple timestamps to the set of selected routes, programming the set of selected routes into a software-implemented forwarding information base (FIB), segmenting the set of selected routes in the software-implemented FIB into at least a first batch of routes and a second batch of routes, programming the first batch of routes into a hardware-implemented FIB, after the programming, determining a last timestamp, where the last time stamp is the oldest timestamp of the timestamps where all routes associated with the last timestamp have been successfully programmed into the hardware-implemented FIB, and advertising all routes of the first batch that are associated with a timestamp that is no older than the last timestamp.