Abstract: In one embodiment, a system includes at least one processor and logic integrated with and/or executable by the processor, the logic being configured to instantiate, using an interface definition language (IDL) on a first server, a remote procedure call (RPC) function to exchange information between the first server and a second server, generate at least one stub on the first server using the RPC, and generate at least one stub on the second server using the RPC, wherein the at least one stub generated on the second server does not perform any marshalling or un-marshaling of data when endianess of the two servers is the same. Other systems, methods, and computer program products for exchanging information between servers using RPCs are described in more embodiments.

Abstract: In one embodiment, a method includes receiving one or more logging events from a client application during a period of time when a logging control configuration has not been fully applied, handling any logging events directed toward at least one of a library code and one or more client applications by storing information relating to an originator of the logging events in a log file and dispatching the logging events directed toward at least one of the library code and the one or more client applications to a syslog daemon, and en-queuing all other logging events for later processing in a circular buffer maintained in non-persistent memory of a shared memory for later retrieval, wherein the other logging events are en-queued for later processing regardless of a severity indicated for any individual logging events. Other methods, systems, and computer program products are described according to more embodiments.

Abstract: In one embodiment, a method includes receiving one or more logging events from a client application during a period of time when a logging control configuration has not been fully applied, handling any logging events directed toward at least one of a library code and one or more client applications by storing information relating to an originator of the logging events in a log file and dispatching the logging events directed toward at least one of the library code and the one or more client applications to a syslog daemon, and en-queuing all other logging events for later processing in a circular buffer maintained in non-persistent memory of a shared memory for later retrieval, wherein the other logging events are en-queued for later processing regardless of a severity indicated for any individual logging events. Other methods, systems, and computer program products are described according to more embodiments.

Abstract: In one embodiment, a system includes at least one processor and logic integrated with and/or executable by the processor, the logic being configured to instantiate, using an interface definition language (IDL) on a first server, a remote procedure call (RPC) function to exchange information between the first server and a second server, generate at least one stub on the first server using the RPC, and generate at least one stub on the second server using the RPC, wherein the at least one stub generated on the second server does not perform any marshalling or un-marshaling of data when endianess of the two servers is the same. Other systems, methods, and computer program products for exchanging information between servers using RPCs are described in more embodiments.

Abstract: A method for software change modeling for network devices provides dynamic (on the device) and static (computer) change modeling. The same source code and libraries are used for both modeling applications, allowing a user to see the impact of activating or deactivating specific software modules without affecting the actual node. A master node passes a node the identity of the software package(s) to be updated and the dependencies. The node notifies its running processes about the update. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, it returns a veto to the node which sends a list of the processes that are impacted along with the reasons why to the master node.

Abstract: A method for dynamic installation and activation of software packages in a distributed networking device. A master node provides a software package database that contains software packages for all nodes. It notifies a node that a software update is being requested, which examines the package identifiers and the dependencies and determines the running processes that will be affected by the update. The processes evaluate the effect that the update will have on their operation. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, the process will veto the update. If the master node receives no vetoes, it updates the node which installs and activates without interrupting the normal operation of the node.

Abstract: A development and build environment creates information used by the master node and nodes in a network of nodes to perform software loading and evaluation during boot and normal runtime. The invention creates metadata and dependency data for packages and modules. Module metadata are created and inserted into the package that includes information such as the module's: binary signature, name, directory path, characteristics, and API dependency information. Packages are formed based on features/characteristics or purpose. A package contains one or more modules. Metadata are created for each package and inserted into the package that includes information such as the package's: name, build date, and characteristics.

Abstract: A method for software change modeling for network devices provides dynamic (on the device) and static (computer) change modeling. The same source code and libraries are used for both modeling applications, allowing a user to see the impact of activating or deactivating specific software modules without affecting the actual node. A master node passes a node the identity of the software package(s) to be updated and the dependencies. The node notifies its running processes about the update. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, it returns a veto to the node which sends a list of the processes that are impacted along with the reasons why to the master node.

Abstract: A method for software change modeling for network devices provides dynamic (on the device) and static (computer) change modeling. The same source code and libraries are used for both modeling applications, allowing a user to see the impact of activating or deactivating specific software modules without affecting the actual node. A master node passes a node the identity of the software package(s) to be updated and the dependencies. The node notifies its running processes about the update. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, it returns a veto to the node which sends a list of the processes that are impacted along with the reasons why to the master node.