H04L41/0869

Verifying the integrity of data transmitted between a firmware and a baseboard management controller (BMC)

Technologies are described for verifying the integrity of data transmitted between a firmware and a baseboard management controller (“BMC”). During a first verification phase, a data integrity tool compares system inventory data provided by firmware protocols to a system inventory module to system inventory data in a device instance format. During a second verification phase, the data integrity tool verifies operation of a firmware conversion module by comparing the system inventory data in the device instance format to the system inventory data in a JavaScript Object Notation (“JSON”) format. During a third verification phase, the data integrity tool retrieves the system inventory data from a management server and compares the system inventory data retrieved from the management server to the system inventory data previously transmitted to the management server. Identified discrepancies can be utilized to modify the system inventory module, the firmware conversion module, or the management server.

Verifying the integrity of data transmitted between a firmware and a baseboard management controller (BMC)

Technologies are described for verifying the integrity of data transmitted between a firmware and a baseboard management controller (“BMC”). During a first verification phase, a data integrity tool compares system inventory data provided by firmware protocols to a system inventory module to system inventory data in a device instance format. During a second verification phase, the data integrity tool verifies operation of a firmware conversion module by comparing the system inventory data in the device instance format to the system inventory data in a JavaScript Object Notation (“JSON”) format. During a third verification phase, the data integrity tool retrieves the system inventory data from a management server and compares the system inventory data retrieved from the management server to the system inventory data previously transmitted to the management server. Identified discrepancies can be utilized to modify the system inventory module, the firmware conversion module, or the management server.

Verifying performance and operation of live services

Embodiments are directed to verifying performance and operation of live services. Applications operative in a computing environment and directed to a plurality of organizations may be provided such that the applications include data associated with different organizations. Templates that declare template objects may be provided such that the template objects may be directed to verifying features of the applications. Data associated with the organization may be provided based on the template objects. Verification objects may be generated based on the template objects and the provided data. The verification objects may be employed to verify the features of the applications based on verification conditions and the provided data. Reports that include results based on verification conditions and the provided data may be provided.

Verifying performance and operation of live services

Embodiments are directed to verifying performance and operation of live services. Applications operative in a computing environment and directed to a plurality of organizations may be provided such that the applications include data associated with different organizations. Templates that declare template objects may be provided such that the template objects may be directed to verifying features of the applications. Data associated with the organization may be provided based on the template objects. Verification objects may be generated based on the template objects and the provided data. The verification objects may be employed to verify the features of the applications based on verification conditions and the provided data. Reports that include results based on verification conditions and the provided data may be provided.

SUBSCRIBER CONFIGURATION INGESTION IN A CONTENT DELIVERY NETWORK

A method on a device in a content delivery (CD) network (CDN) that distributes content on behalf of one or more subscribers. In response to receiving configuration information from a subscriber, the configuration information relating to at least one property of the subscriber, generating subscriber-specific platform configuration information for the at least one property. Storing the subscriber-specific platform configuration information in platform configuration storage. Invalidating prior platform configuration information associated with the particular subscriber. Responsive to a request from a CDN component for platform configuration information associated with the particular subscriber: obtaining the subscriber-specific platform configuration information from the platform configuration storage; and providing the subscriber-specific platform configuration information to the CDN component.

Collision detection using state management of configuration items

Implementations of a system, method and apparatus described herein receive, for a configuration item in a configuration management database, status indicating an operational state and an automation state associated with the configuration item, and determine whether a conflict will occur with at least one of the operational state or the automation state of the configuration item as a result of a process affecting the configuration item. When the conflict will not occur, a change is made to at least one of the operational state or the automation state of the configuration item in accordance with the process. Upon a conclusion of the process, the change is removed. If the conflict will occur, the process not allowed to continue.

Sharing configuration resources for network devices among applications

In an example, a method includes receiving, by a network management system (NMS), a configuration request comprising first configuration data for a network device, the first configuration data defining a data structure comprising a first property/value pair; generating, by the NMS from the first configuration data, a corresponding first path/value pair for the first property/value pair, wherein a path of the first path/value pair uniquely identifies the first path/value pair in an associative data structure; modifying, by the NMS, the associative data structure based on the first path/value pair; generating, by the NMS, from the associative data structure, a configuration resource comprising second configuration data for the network device, the second configuration data comprising a second property/value pair that corresponds to the first path/value pair; and sending, by the NMS, the second configuration data to the network device to modify a configuration of the network device.

Template based edge cloud core deployment

The techniques described herein relate to methods that include: obtaining criteria for a mobile network deployment; selecting a server configuration template for a server configuration based upon the criteria; generating the server configuration for the mobile network deployment based upon the server configuration template; validating the server configuration to ensure the criteria are met by the mobile network deployment of the server configuration; deploying the server configuration as the mobile network deployment; obtaining key performance indicators from the mobile network deployment; updating the mobile network deployment in response to obtaining the key performance indicators; and updating the server configuration template in response to obtaining the key performance indicators.

Template based edge cloud core deployment

The techniques described herein relate to methods that include: obtaining criteria for a mobile network deployment; selecting a server configuration template for a server configuration based upon the criteria; generating the server configuration for the mobile network deployment based upon the server configuration template; validating the server configuration to ensure the criteria are met by the mobile network deployment of the server configuration; deploying the server configuration as the mobile network deployment; obtaining key performance indicators from the mobile network deployment; updating the mobile network deployment in response to obtaining the key performance indicators; and updating the server configuration template in response to obtaining the key performance indicators.

System and method for customized port configuration

The disclosed system may include (1) a modular port concentrator that connects as a modular line card within a router to forward network packets, (2) a profile module, stored in memory, that stores an allowed port configuration profile that defines supported port configurations for the modular port concentrator, (3) a configuration module, stored in memory, that receives an attempted port configuration for the modular line card, (4) an enforcement module, stored in memory, that enforces the allowed port configuration profile by taking remedial action in response to determining that the allowed port configuration profile does not allow the attempted port configuration, and (5) at least one physical processor configured to execute the modular port concentrator, the profile module, the configuration module, and the enforcement module. Various other systems and methods are also disclosed.