Cisco Technology, Inc.

Matthew Balint

Glen C Darling

Badari Kakumani

Douglas Wooff

Nobushige Akiya

John K Fitzgerald

Mala Devlin

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.

Software change modeling for network devices

A method for software loading and initialization in a distributed network of nodes. A master node provides a node information database and a software package database. A node performing an initial boot requests a boot image and software package download from the master node. The master node finds the node's software configuration information in the node information database and sends the boot image and software packages to the node from the software package database. The node reboots into the boot image and verifies the software versions with the master node. If the node has the correct software, then it completes the boot sequence, otherwise, the master node sends the correct software packages to the node which then continues with the boot sequence.

Method and apparatus for software loading and initialization in a distributed network

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.

Dynamic installation and activation of software packages in a distributed networking device

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.

Growing community of inventors

San Jose, CA, United States of America

Matthew Balint