Activate a NetOps Module
The NetOps module license is installed on Lighthouse and contains a preset number of available node activations. Each supported node that is activated for the NetOps module provisioning, consumes an available activation. Lighthouse itself does not consume an activation.
Installing the NetOps module license automatically activates the module on Lighthouse, at which point the NetOps Automation platform deploys the central module software components, including the module's UI, to Lighthouse.
The process of automatically or manually activating a NetOps module on a node deploys the remote module software components to that node, securely over Lighthouse VPN.
Preparation
-
Install the Lighthouse VM and ensure it is running.
-
Login to the Lighthouse web UI as root or a Lighthouse Administrator.
-
Install the Lighthouse node subscription (SKU OGLH) under
> SYSTEM > Subscriptions.
Procedure
-
Ensure you have a valid NetOps module subscription installed under
> SYSTEM > Subscriptions.
Note: For more information, see Subscription Types.
-
It will take a few minutes for the module to activate on Lighthouse. View the progress under
NetOps > Manage NetOps Modules.
Nodes may now be automatically activated for the module as they enroll, or manually activated after enrollment.
'Always Activate' Mode on All Nodes (Automatic)
In the Always Activate mode, NetOps automatically activates the NetOps module on all nodes, provided a license is present and activations are available. All nodes are activated for the module as they enroll.
Procedure
-
In the Menu Pane, select
NetOps > Manage NetOps Modules.
The MANAGE NETOPS MODULES page displays. -
Under Always Activate, select ENABLED as required for the module:
-
SECURE PROVISIONING
-
IP ACCESS
-
AUTOMATION GATEWAY
-
-
Click Apply.
To activate a new node, enroll the node into Lighthouse.
Activate NetOps on Selected Nodes (Automatic)
You may selectively activate the module on a subset of nodes using Enrollment Bundles. Only nodes enrolling using one of these bundles will be automatically activated.
Procedure
-
In the Menu Pane, select
NetOps > Manage NetOps Modules.
The MANAGE NETOPS MODULES page displays. -
Under Always Activate, select DISABLED as required for the module:
-
SECURE PROVISIONING
-
IP ACCESS
-
AUTOMATION GATEWAY
-
-
Click Apply.
-
In the Menu Pane, select
Node Tools > Enrollment Bundles.
The ENROLLMENT BUNDLES page displays. -
Click Add Enrollment Bundle to add a new bundle (you may also edit an existing bundle).
The NEW ENROLLMENT BUNDLE page displays. -
Enter the details and choose whether or not to Auto-Approve enrollment.
-
Under the NETOPS SECTION select Add Module.
The CHOOSE MODULE dialog is displayed. -
Select the module from the drop-down.
-
Click Apply.
Note: Lighthouse-initiated manual enrollment (for example, clicking the Add Node button in the Lighthouse web UI) does not support bundles, you must use a node-initiated enrollment method.
Activate the NetOps Module on Nodes (Manual)
To activate nodes manually after enrollment, the process is performed across three phases:
-
Select Nodes
-
Pre-Flight Test
-
Push
Select Nodes
-
Ensure the Always Activate option is DISABLED and applied for each module on the
NetOps > Manage NetOps Modules dashboard.
-
In the Menu Pane, select
Node Tools > Config Templates.
The CONFIG TEMPLATES dashboard is displayed defaulted to the AUTHENTICATION tab. -
Select the NETOPS MODULES tab.
-
Select the
Push Template from the actions available on the module.
The PUSHING TEMPLATE page displays. -
Check the NODE ID to push the template to.
Pre-Flight Test
-
Click Run Pre-Flight Test.
The page displays the current Pre-Flight Status per node.
Push
-
On successful completion of the Pre-Flight Test, select Push Configuration.
The page displays the current Push Status per node.
Note: Under the NetOps licensing arrangement, when a node is activated for the NetOps module, the activation is consumed by and locked to that node. Unenrolling the node returns the activation to the available pool. Under NetOps subscription arrangements, it would be counted towards the node assignment of the subscription.