Abstract: A policy driven zero touch provisioning (ZTP) system implements techniques for policy driven ZTP of network devices. One or more ZTP policies, configurations and/or boot images associated with one or more network devices are stored in a database. Upon execution of a boot sequence, a network device automatically sends a DHCP request including network device identification information to the policy driven ZTP system. The policy driven ZTP system identifies a matching ZTP policy having conditions that match the network device identification information. The ZTP system generates a DHCP response including IP leasing information, a boot configuration information by which a boot configuration may be automatically obtained, and/or boot image information by which a boot image may be automatically obtained as defined by the matching ZTP policy. The techniques allow ZTP policies to be defined with device-level granularity for boot configuration and/or boot images.

Abstract: A policy driven zero touch provisioning (ZTP) system implements techniques for policy driven ZTP of network devices. One or more ZTP policies, configurations and/or boot images associated with one or more network devices are stored in a database. Upon execution of a boot sequence, a network device automatically sends a DHCP request including network device identification information to the policy driven ZTP system. The policy driven ZTP system identifies a matching ZTP policy having conditions that match the network device identification information. The ZTP system generates a DHCP response including IP leasing information, a boot configuration information by which a boot configuration may be automatically obtained, and/or boot image information by which a boot image may be automatically obtained as defined by the matching ZTP policy. The techniques allow ZTP policies to be defined with device-level granularity for boot configuration and/or boot images.

Abstract: Scalable, robust cloud-based network management systems (NMSs) are described. In one, an NMS includes a set of NMS applications, a pool of device communication managers (DCMs), and a pool of device operations managers (DOMs). Each of the DCMs and DOMs executed by the processors as software containers. The NMS includes an API gateway configured to route remote procedure calls (RPCs) from the DCMs to the DOMs via the APIs exposed by the DOMs and according to device identifiers of the managed elements. The DOMs are configured to establish a set of persistent application-layer communication sessions from the DOMs to the DCMs and to direct communications from the NMS applications to the DCMs over the persistent application-layer communication sessions according to a mapping between device identifiers associated with the managed elements and network addresses associated with the DCMs.

Abstract: Scalable, robust cloud-based network management systems (NMSs) are described. In one, an NMS includes a set of NMS applications, a pool of device communication managers (DCMs), and a pool of device operations managers (DOMs). Each of the DCMs and DOMs executed by the processors as software containers. The NMS includes an API gateway configured to route remote procedure calls (RPCs) from the DCMs to the DOMs via the APIs exposed by the DOMs and according to device identifiers of the managed elements. The DOMs are configured to establish a set of persistent application-layer communication sessions from the DOMs to the DCMs and to direct communications from the NMS applications to the DCMs over the persistent application-layer communication sessions according to a mapping between device identifiers associated with the managed elements and network addresses associated with the DCMs.