Methods and systems are provided for managing dynamic devices of an IHS (Information Handling System) that include re-programmable logic circuitry. The dynamic devices of the IHS are identified and the type of a dynamic device is determined based on operations implemented by the re-programmable logic circuitry of that dynamic device. The dynamic device is enrolled for management by a remote access controller of the IHS based on its determined type. Messages are registered for management of the dynamic device, where the messages are selected based on its determined type. Remote management of the dynamic device is initiated using the registered messages. Any programming that changes the type of the dynamic device of the dynamic device is detected. If a change is detected, the dynamic device is enrolled for remote management using updated messages based on its updated type.

Methods and devices provide fault injection testing techniques in a production network environment without risking service outages for hosted computing services, by providing examples of a remote network controller configured to communicate with network devices of a network; a remote fault injection communication protocol configuring a remote network controller in communication with a network device to signal a failure injection; and a failure injection module configuring a network device to configure a network device processor to implement a failure injection signaled according to the remote failure injection communication protocol. The method includes a network controller transmitting a failure injection signal in a control plane packet over a network connection to a network device, and the network device creating a child process by executing, in a dedicated runtime environment, a copy of one or more processes impacted by a parsed failure type.

Embodiments herein relate to a method performed by a RAN node (12), for managing communication on a first network slice in a communications network (1). The communications network (1) comprises partitioned sets of functionalities. A first set of functionalities belongs to the first network slice. The first set of functionalities is at least 5 partly separated from another set of functionalities out of a total set of functionalities in the communications network (1). The RAN node (12) receives, from a CN node (16), information regarding requested resources for a first network slice identified by a network slice identifier. The RAN node (12) determines that the received information does not correspond to a Service Level Agreement (SLA) for the first network slice.

One or more non-transitory computer readable media contain program instructions that, when executed by one or more processors, cause the one or more processors to perform operations including generating a database of interconnected smart entities. The smart entities include sensor object entities representing each of the plurality of sensors and data entities representing measurements received from the sensors. The smart entities are interconnected by relational objects indicating relationships between the smart entities. The instructions cause the one or more processors to receive a new measurement from a first sensor, identify a first data entity from a relational object for the first sensor, the first data entity including a plurality of past measurements received from the first sensor, and modify the first data entity within the database of smart entities to include the new measurement received from the first sensor.

One or more non-transitory computer readable media containing program instructions that, when executed by one or more processors, cause the one or more processors to perform operations: generating a database of interconnected smart entities, the smart entities including object entities representing each of the plurality of physical devices and data entities representing data generated by the devices, the smart entities being interconnected by relational objects indicating relationships between the object entities and the data entities; receiving data from a first device of the plurality of physical devices; determining a second device from a relational object for the first device based on the received data; and modifying a data entity connected to an object entity of the second device within the database of smart entities based on the received data for the first device.

A server system comprising storage devices, processing devices and a storage fabric all operating according to a storage fabric protocol. The storage fabric comprises a plurality of individual switches having a modular design from which an overall switch is built, and the individual switches have individual respective configuration settings which determine which processing devices are allocated to use which of the storage devices. The system comprises an API enabling a software control function to configure the overall switch. The API is operable to receive from the control function an overall mapping of the storage devices to the processing devices instead of requiring the individual configuration settings of each of the individual switches to be specified by the control function, the API being configured to convert the overall mapping into the individual configuration settings of the individual switches to produce the overall mapping.

A bidirectional out-of-band management (OOBM) dongle comprises a serial port for receiving console traffic from a console port of a managed switch and an Ethernet port for receiving management port traffic from a management port of the managed switch. In operation, the OOBM dongle multiplexes, via an optional adapter, the console traffic and the management port traffic and generates Ethernet traffic that is then communicated, via an OOBM port on the dongle, to an OOBM switch port of an OOBM switch that acts as a power sourcing device for the OOBM dongle.

Methods and apparatus to orchestrate infrastructure installation of a hybrid system are disclosed. An example apparatus includes a first virtual appliance including a management endpoint. The first virtual appliance is to organize tasks to be executed to install a computing infrastructure. The example apparatus includes a first component server to execute tasks. The component server includes a management agent to communicate with the management endpoint to receive a task to be executed to install the computing infrastructure. The first virtual appliance is to associate a role with the first component server and to determine whether the first component server satisfies a prerequisite associated with the role. The first virtual appliance is to facilitate addressing an error when the first component server is determined not to satisfy the prerequisite.

Systems and methods of creating and managing a multi-edge EtherChannel (MEEC) include, with a control node communicatively coupled to a plurality of edge nodes within a network, receiving including data defining a bundle of a plurality of links communicatively coupling the plurality of edge nodes and a first server and data identifying the first server. A map-notify message is sent to an edge node defining a link state for at least the first edge node. A map-proxy register message defining a plurality of link states for the plurality of the edge nodes within the bundle is sent to at least a second edge node to synchronize the first edge node with respect to at least the second edge node of the plurality of edge nodes. A map-reply message indicating load balancing data of a plurality of the edge nodes may be sent to an ingress edge node and data packets may be load balanced based on the load balancing data.

A method supporting distributed resilient network interconnect (DRNI) in a link aggregation group at a network device is disclosed. The method starts with encapsulating a distributed relay control protocol data unit (DRCPDU) in a frame, wherein the DRCPDU includes a protocol data unit (PDU) structure. The PDU structure includes a type field indicating that the DRCPDU is for DRCP, a version field indicating a version number of the DRCP, and a set of type/length/values (TLVs) including: a terminator TLV indicating an end of the PDU structure, a portal information TLV indicating characteristics of the first portal, a portal configuration information TLV indicating configuration information of the first portal, a DRCP state TLV indicating variables associated with an intra-portal link (IPP), a home ports information TLV and a neighbor ports information TLV. The method continues with transmitting the frame encapsulating the DRCPDU from the network device to a neighbor network device.