If you are using the current version of Cumulus NetQ, the content on this page may not be up to date. The current version of the documentation is available here. If you are redirected to the main page of the user guide, then this page may have been renamed; please search for it there.

Lifecycle Management

Using the NetQ UI or CLI, lifecycle management (LCM) allows you to:

Lifecycle management is enabled for on-premises deployments and disabled for cloud deployments by default. Contact your NVIDIA sales representative or submit a support ticket to activate LCM on cloud deployments.

Access Lifecycle Management in the UI

To access the lifecycle management dashboard, expand the Menu, then select Manage switches:

dashboard displaying switch management tab

LCM Summary

This table summarizes LCM functionalities in the UI and CLI:

Function
Description
NetQ UI Cards
NetQ CLI Commands
Switch management Discover switches, view switch inventory, assign roles, set user access credentials, perform software installation and upgrade networkwide
  • Switches
  • Access profiles
  • netq lcm show switches
  • netq lcm add role
  • netq lcm upgrade
  • netq lcm add/del/show credentials
  • netq lcm discover
Image management View, add, and remove images for software installation and upgrade
  • Cumulus Linux images
  • NetQ images
  • netq lcm add/del/show netq-image
  • netq lcm add/del/show cl-images
  • netq lcm add/show default-version
NetQ agent configurations Customize configuration profiles for NetQ Agents running on switches
  • NetQ agent configurations
  • netq lcm add/del/show netq-config
Job history View the results of installation, upgrade, and configuration assignment jobs
  • CL upgrade history
  • NetQ install and upgrade history
  • netq lcm show status
  • netq lcm show upgrade-jobs

LCM Support for In-band Management

If you manage a switch using an in-band network interface, the inband-interface option must be specified in the initial agent configuration for LCM operations to function as expected. You can configure the agent by specifying the in-band interface in the /etc/netq/netq.yml file. Alternately, you can use the CLI and include the inband-interface option.

  • /etc/netq/netq.yml configuration file example:

    netq-agent:
        inband-interface: swp1
        port: 31980
        server: 192.168.1.254
        vrf: default
    
  • CLI configuration example:

    sudo netq config add agent server 192.168.1.254 vrf default inband-interface swp1
    

After the NetQ Agent is configured for in-band connections, you can create custom agent configuration profiles, then apply the custom profiles to switches during upgrades.