Patent classifications
H04L41/045
SYSTEMS AND METHODS FOR DEPLOYING AND MANAGING SECURE LIMITED-ADMINISTRATION SERVER SYSTEMS
A method comprises creating template limited-administration ontologies, the template limited-administration ontologies each identifying a plurality of different managers, each of the different managers having distinct and limited system access privileges. A request is received for a limited-administration server system, the request being associated with a client entity. A particular template limited-administration ontology of the template limited-administration ontologies is selected based on the request. A deployment ontology is generated based on the particular template limited-administration ontology and the request. A limited-administration server system deployment package is generated based on the deployment ontology. The limited-administration server system deployment package is provided for execution, wherein execution of the limited-administration server system deployment package creates a limited-administration server system, the limited-administration server system being capable of controlling access to one or more other systems associated with the client entity, and the limited-administration server system being limited to administration according to the different managers.
SIMPLE NETWORK MANAGEMENT PROTOCOL OBJECT HISTORY COLLECTOR MANAGEMENT INFORMATION BASE TO CURTAIL MANAGEMENT TRAFFIC
A network device may poll data for counters of the network device, and may store, for a first time interval, the data polled for the counters in a data structure. The network device may maintain the data polled for the counters in the data structure for a second time interval that is longer than the first time interval, and may receive, from a network management system (NMS), a request for data polled for the counters with the second time interval. The network device may determine, based on the request, whether the NMS is authorized to receive the data polled for the counter, and may provide, to the NMS, the data polled for the counters, with the second time interval, when on the NMS is authorized to receive the data polled for the counters.
SIMPLE NETWORK MANAGEMENT PROTOCOL OBJECT HISTORY COLLECTOR MANAGEMENT INFORMATION BASE TO CURTAIL MANAGEMENT TRAFFIC
A network device may poll data for counters of the network device, and may store, for a first time interval, the data polled for the counters in a data structure. The network device may maintain the data polled for the counters in the data structure for a second time interval that is longer than the first time interval, and may receive, from a network management system (NMS), a request for data polled for the counters with the second time interval. The network device may determine, based on the request, whether the NMS is authorized to receive the data polled for the counter, and may provide, to the NMS, the data polled for the counters, with the second time interval, when on the NMS is authorized to receive the data polled for the counters.
PAYLOAD TEMPLATE GENERATOR FOR AN INFORMATION HANDLING SYSTEM
In some aspects, an apparatus includes a memory and one or more processors coupled to the memory. The one or more processors are configured to receive, from a client device, a payload template request and to transmit, to the client device based on the payload template request, a payload template response including a plurality of payload templates. The one or more processors are further configured to receive, from the client device, a management request including a payload corresponding to a payload template of the plurality of payload templates and to transmit, to the client device based on the management request, a management response indicating a result associated with the management request.
PAYLOAD TEMPLATE GENERATOR FOR AN INFORMATION HANDLING SYSTEM
In some aspects, an apparatus includes a memory and one or more processors coupled to the memory. The one or more processors are configured to receive, from a client device, a payload template request and to transmit, to the client device based on the payload template request, a payload template response including a plurality of payload templates. The one or more processors are further configured to receive, from the client device, a management request including a payload corresponding to a payload template of the plurality of payload templates and to transmit, to the client device based on the management request, a management response indicating a result associated with the management request.
Geo-location based optimized hub mesh
Systems, methods, and computer-readable media are described for establishing an optimized geo-location based hub mesh network for a group of network controllers spanning multiple regions, where the optimized mesh network includes substantially fewer connections between network controllers than conventional hub mesh networks. Geo-location information is obtained for the group of network controllers, and the network controllers are categorized into various physical regions based on the geo-location information. Then, within each region, a particular network controller is selected to serve as a primary regional hub for that region. Tunnel connections are then established between each non-hub network controller in each region and the primary regional hub for that region. In addition, tunnel connections are established between each non-hub network controller in a region and each other non-hub network controller within the same region. Moreover, connections are established between the regional hub network controllers.
Geo-location based optimized hub mesh
Systems, methods, and computer-readable media are described for establishing an optimized geo-location based hub mesh network for a group of network controllers spanning multiple regions, where the optimized mesh network includes substantially fewer connections between network controllers than conventional hub mesh networks. Geo-location information is obtained for the group of network controllers, and the network controllers are categorized into various physical regions based on the geo-location information. Then, within each region, a particular network controller is selected to serve as a primary regional hub for that region. Tunnel connections are then established between each non-hub network controller in each region and the primary regional hub for that region. In addition, tunnel connections are established between each non-hub network controller in a region and each other non-hub network controller within the same region. Moreover, connections are established between the regional hub network controllers.
FLEXIBLE PIPELINE PROCESSING METHOD AND SYSTEM
A reprogrammable software defined network device is disclosed which allows at any time the selection of a desired subset of features from all possible features, without the requirement of making available all possible features that might otherwise be programmed into the programmable switch, and without the requirement of reprogramming the interface which is used to access the features. The device comprises a standardized control API and a programmable switch capable of implementing only a subset of said plurality of switch features, each accessible via a runtime API and a control library interconnecting the control API and the runtime API such that each of the subset is accessible by the external controller using said standardized control API via said runtime API. The subset changes from time to time in response user requirements. A change in the subset of features gives tise to a change in the runtime API.
FLEXIBLE PIPELINE PROCESSING METHOD AND SYSTEM
A reprogrammable software defined network device is disclosed which allows at any time the selection of a desired subset of features from all possible features, without the requirement of making available all possible features that might otherwise be programmed into the programmable switch, and without the requirement of reprogramming the interface which is used to access the features. The device comprises a standardized control API and a programmable switch capable of implementing only a subset of said plurality of switch features, each accessible via a runtime API and a control library interconnecting the control API and the runtime API such that each of the subset is accessible by the external controller using said standardized control API via said runtime API. The subset changes from time to time in response user requirements. A change in the subset of features gives tise to a change in the runtime API.
Testing client-side rendering capabilities
In some implementations, a computing device can test the client-side rendering capabilities of a map module running on a computing device. For example, the map module can include a test module that sends test data to a rendering module of the browser. The rendering module can render the test data into a rendering context based on the test data. The test module can compare the pixel data in the rendering context to expected pixel data to determine whether the rendering module is capable of accurately rendering an image based on the test data. If the rendering module is capable of accurately rendering the rendering context based on the test data, the map module can be configured to perform client-side rendering of images. For example, the map module can be configured to perform client-side rendering of map data based on map data received from a map server.