Bulk Configlet for Network Device Mass Activation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large enterprises face challenges in mass deploying and activating network devices across remote geographic locations due to the need for precise configuration and management, often requiring trained administrators to ensure proper installation and activation, which can be difficult to manage, especially when devices are shipped directly to remote facilities.

Innovation Solution

The development of a bulk configlet that includes common configuration data for similar network devices, allowing them to connect to a centralized management system, with a bulk identifier for identification and specific configuration data retrieval, simplifying the deployment and activation process by enabling devices to bootstrap and connect automatically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If devices are shipped directly from manufacturer to remote facilities, then shipping costs are reduced and central IT burden is alleviated, but proper installation and activation cannot be ensured due to lack of trained administrators at remote locations

Engineering Contradiction:
Improveshipping costsVSAvoidproper installation and activation
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The network device is designed to automatically perform configuration and activation functions that previously required human administrators. The device autonomously retrieves configuration data from a configlet, configures itself, and activates without human intervention, thereby compensating for the absence of trained administrators at remote locations while maintaining installation reliability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Configuration data is prepared in advance and embedded in a configlet that is attached to or associated with each network device before shipping. This preliminary preparation of configuration data allows the device to self-configure upon arrival at the remote facility, eliminating the need for on-site administrative intervention while ensuring proper installation

Inventive Principle:
Principle #10Preliminary action

2Reliability

If device-specific configlets are created and distributed to each remote facility, then proper device configuration can be ensured, but the complexity of managing and tracking configlet distribution increases significantly

Engineering Contradiction:
Improvedevice configurationVSAvoidconfiglet management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Multiple device-specific configlets are merged into a single bulk configlet that contains configuration data for multiple network devices. This consolidation reduces the number of separate configlet files that must be managed and distributed, while each individual device can still retrieve its specific configuration data from the bulk configlet through unique identifiers

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The bulk configlet is designed to serve multiple functions: it can configure multiple different network devices, accommodate various device types, and provide both bulk configuration capabilities and individual device-specific configuration retrieval. This multi-functionality eliminates the need for separate configlet files for each device while maintaining configuration precision

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If a bulk configlet is used for multiple devices, then deployment process is simplified and administrative burden is reduced, but the ability to provide device-specific configuration data becomes more challenging

Engineering Contradiction:
Improvedeployment processVSAvoiddevice-specific configuration
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The bulk configlet is segmented into multiple configuration data sets, each associated with a specific network device through unique identifiers. When a device retrieves configuration from the bulk configlet, it identifies itself and receives the appropriate segmented configuration data, thereby maintaining device-specific configuration precision while using a unified bulk configlet structure

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The bulk configlet acts as an intermediary between the centralized configuration system and multiple individual network devices. It receives bulk configuration data, processes and segments it into device-specific configurations, and distributes appropriate configuration data to each device, thereby simplifying the deployment process while preserving configuration precision

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9253034B1Mass activation of network devices
Publication Date: 2016.02.02 JUNIPER NETWORKS INC

AI summary

Techniques are described for initializing a plurality of network devices with similar network configurations, such as a common management device, platform, operating system, and network hostname. In one example, a management device comprises a computer-readable medium encoded with instructions for a configlet generator module and a device manager module and a processor to execute modules stored in the computer-readable medium of the management device. The processor executes the configlet generator module to generate a bulk configlet for a plurality of network devices, wherein the bulk configlet comprises a bulk identifier. The processor also executes the device manager module to receive a network session request from one of the plurality of network devices, wherein the network session request includes the bulk identifier, and to send specific configuration data to the one of the plurality of network devices in response to the network session request.