NVLink Switch Firmware Update Process#
For the NVLink Switch, the firmware updates consist of the firmware of the switch itself and then the NVOS software itself.
NVLink Switch Tray Assumptions#
Non scale out design (single-rack configuration) - all NVLink ports are connected to the MN-NVLink cable cartridge
All tray interfaces are set to receive IPs using DHCP
The rack inventory import process or manual entry process must be completed, and all switch entries appear in the cmsh devices list.
Example: NVLink Switch BCM switch device list
root@T06-HEAD-01:~# cmsh -c "device; list -t switch -f hostname:15,mac:20,ip:12,status:11 |grep -i nvsw " S03-P1-NVSW-01 E0:9D:73:F0:4C:DE 10.78.195.1 [ UP ]+ S03-P1-NVSW-02 E0:9D:73:3F:EB:28 10.78.195.2 [ UP ]+ S03-P1-NVSW-03 E0:9D:73:3F:E7:30 10.78.195.3 [ UP ]+ S03-P1-NVSW-04 E0:9D:73:3F:EA:C8 10.78.195.4 [ UP ]+ S03-P1-NVSW-05 E0:9D:73:3F:E4:F0 10.78.195.5 [ UP ]+ S03-P1-NVSW-06 E0:9D:73:3F:E2:C8 10.78.195.6 [ UP ]+ S03-P1-NVSW-07 E0:9D:73:3F:E2:50 10.78.195.7 [ UP ]+ S03-P1-NVSW-08 E0:9D:73:3F:E5:18 10.78.195.8 [ UP ]+ S03-P1-NVSW-09 E0:9D:73:3F:E4:F8 10.78.195.9 [ UP ]+ S04-P1-NVSW-01 E0:9D:73:F0:41:4E 10.78.195.31 [ UP ]+ S04-P1-NVSW-02 E0:9D:73:F0:59:16 10.78.195.32 [ UP ]+ S04-P1-NVSW-03 E0:9D:73:F0:41:8E 10.78.195.33 [ UP ]+ S04-P1-NVSW-04 E0:9D:73:F0:41:36 10.78.195.34 [ UP ]+ S04-P1-NVSW-05 E0:9D:73:F0:41:A6 10.78.195.35 [ UP ]+ S04-P1-NVSW-06 E0:9D:73:F0:45:36 10.78.195.36 [ UP ]+ S04-P1-NVSW-07 E0:9D:73:F0:4D:7E 10.78.195.37 [ UP ]+ S04-P1-NVSW-08 E0:9D:73:F0:3D:56 10.78.195.38 [ UP ]+ S04-P1-NVSW-09 E0:9D:73:F0:4D:B6 10.78.195.39 [ UP ]+
Note
For switches, the cm-lite daemon needs to be up and running for the switch to appear as [UP]
Example: NVLink Switch BCM switch Information
[a03-p1-head-01->device[a05-p1-nvsw-01]]% show Parameter Value ------------------------ ------------------------------------ Hostname a05-p1-nvsw-01 IP 7.241.3.1 Network ipminet2 Revision Type Switch Mac E0:9D:73:3F:E0:50 Model Ports 0 Kind nvlink Control script Control script timeout 5 SNMP Settings <submode> Lowest port 1 Uplinks Disable port detection yes Disable port mapping no Activation Sun, 23 Feb 2025 12:55:30 PST Rack A05:19 Chassis < not set > Access Settings <submode> Priority 0 VLAN cache time 5m Has client daemon yes ZTP Settings <submode> Subnet manager no Disable SNMP yes GUID 00000000-0000-0000-0000-000000000000 Services <0 in submode> NV configuration mode AUTO Members Management network ipminet2 Power control rf0 Custom power script Custom power script argument Power distribution units Default gateway metric 0 Switch ports Interfaces <3 in submode> BMC Settings <submode> Userdefined1 Userdefined2 User defined resources Supports GNSS no Custom ping script Custom ping script argument Partition base Part number Serial number Notes <0B> Prometheus metric forwarders <0 in submode>
Example: BCM NVLink Switch interfaces output
[a03-p1-head-01->device[B05-P1-NVSW-01]->interfaces]% list Type Network device name IP Network Start if -------- --------------- ------------ ------------ ---------- -------- bmc rf0 7.241.5.21 ipminet3 always physical eth0 7.241.5.1 ipminet3 always physical eth1 7.241.5.11 ipminet3 always
All NVLink Switches per rack are reachable by its BMC and COMe0/COMe1 port IP address.
Copper connections confirmed
Speed/Bandwidth (200G for COMe0 and COMe1)
IP Address assigned by BCM to the COMe0 and COMe1 network (ipminetx)
Logical Connectivity (Access)
ssh to NVLink switch BMC can be done (default user/pass = root/JulietBmc@123
ssh to NVOS on each NVLink switch can be done (default user/pass = admin/Juliet1234).
Note
If the NVLink Switch has any issues and the default NVOS password above is not working, try admin/admin
Method 1 - BCM/NVIDIA Mission Control FW Update Integrated Process for NVLink Switch#
Get a summary of the FW update files uploaded to BCM using the /cm/local/apps/cmd/etc/htdocs/bios/firmware/gb200sw directory. If none exist, upload the flash files to that directory.
Verify the files with this command cmsh -c ‘device; firmware info’. Ensure that all the files show up with the GB200-Switch designation.
Example: Firmware Update File List for NVLink Switches
cmsh;device;firmware info \| grep -i GB200-Switch #Or get it from the individual node entry [a03-p1-head-01->device[a05-p1-nvsw-09]]% firmware info Device Filename Component Version State Progress Result Size Date ---------------- ------------------------------------------------ ------------ ------------------------ ---------- -------- -------- ------- --------------------- a03-p1-head-01 nvfw_GB200-P4978_0000_250213.1.0_dbg-signed.fwpkg GB200-Switch GB200-P4978_250213.1.0 available N/A 71MiB 2025-02-13, 10:05:51 a03-p1-head-01 nvfw_GB200-P4978_0002_250205.1.0_dbg-signed.fwpkg GB200-Switch GB200-P4978_250205.1.0 available N/A 16.2MiB 2025-02-05, 15:49:59 a03-p1-head-01 nvfw_GB200-P4978_0003_250121.1.2_custom_dbg-signed.fwpkg GB200-Switch GB200-P4978_250121.1.2_custom available N/A 1.64MiB 2025-01-21, 13:55:25
Use the firmware status command from the BCM device submenu to find the current firmware levels of the NVLink Switch
Note
CPLD4 in the example below does not apply to DG XGB300 which only has 3 CPLDs.
Example: Firmware Status Command from BCM
# Do for individual node [a03-p1-head-01->device]% firmware status -n a05-p1-nvsw-09 # Do for all nodes [a03-p1-head-01->device]% firmware status -t switch | grep -i nvsw # Can also pull at the rack level if desired [a03-p1-head-01->device]% firmware status -r <rack location> | grep -i nvsw
Example: Firmware Status Command Output
Device Filename Component Version State Progress Result Size Date ------------------ --------------------- ------------------- ---------------------- --------- --------- -------- ------- --------------------- a05-p1-nvsw-09 ASIC 35.2014.1698 current N/A N/A a05-p1-nvsw-09 BIOS 0ACTV_00.01.012 current N/A N/A a05-p1-nvsw-09 BMC 88.0002.0956 current N/A N/A a05-p1-nvsw-09 CPLD1 CPLD000370_REV0500 current N/A N/A a05-p1-nvsw-09 CPLD2 CPLD000377_REV0800 current N/A N/A a05-p1-nvsw-09 CPLD3 CPLD000373_REV0800 current N/A N/A a05-p1-nvsw-09 CPLD4 CPLD000390_REV0300 current N/A N/A a05-p1-nvsw-09 EROT 01.04.0018.0000_n04 current N/A N/A a05-p1-nvsw-09 EROT-ASIC1 01.04.0018.0000_n04 current N/A N/A a05-p1-nvsw-09 EROT-ASIC2 01.04.0018.0000_n04 current N/A N/A a05-p1-nvsw-09 EROT-BMC 01.04.0018.0000_n04 current N/A N/A a05-p1-nvsw-09 EROT-CPU 01.04.0018.0000_n04 current N/A N/A a05-p1-nvsw-09 EROT-FPGA 01.04.0018.0000_n04 current N/A N/A a05-p1-nvsw-09 FPGA 0.1A current N/A N/A a05-p1-nvsw-09 SSD CE00A400 current N/A N/A a05-p1-nvsw-09 transceiver N/A current N/A N/A
Ensure that all NVLink Switch BMCs have their firmware management mode set to gb200sw.
#within CMSH device foreach -t switch (bmcsettings; get firmwaremanagemode) #If not set foreach -n S03-P1-NVSW-[01..09] (bmcsettings; set firmwaremanagemode gb200sw;commit)
To check against the versions in the firmware update file and ascertain if an update is needed, provide the file name in firmware flash –dry run command
#Single Switch cmsh;device; firmware flash -n s03-p1-nvsw-04 nvfw_GB200-P4978_0007_250121.1.2_custom_prod-signed.fwpkg --dry-run #Multiple Switches cmsh;device; firmware flash -n S03-P1-NVSW-[01-09] nvfw_GB200-P4978_0007_250121.1.2_custom_prod-signed.fwpkg --dry-run
If the changes look correct, then remove the –dry-run switch to apply the updates.
Update the tray level firmware first in this order:
BMC+FPGA+ERoT (Switch BMC bundle).
CPLD1 CPLD2 CPLD3 CPLD4 (Switch CPLD bundle).
SBIOS+EROT (Switch BIOS bundle).
Use firmware status -n <switch host name> command to check update progress.
Once complete do an AC Cycle of the NVLink Switch to confirm the new firmware versions are active.
[a17-p1-bcm-01->device]% firmware status -n a18-p1-nvsw-09 Device Filename Component Version State Progress Result Size Date ---------------- -------------------------------- ---------------- -------------------- ---------- -------- ------------------- -------- -------- a18-p1-nvsw-09 ASIC 35.2015.1686 current N/A N/A a18-p1-nvsw-09 BIOS 0ACTV_00.01.012 current N/A N/A a18-p1-nvsw-09 BMC 88.0002.0956 completed N/A success: activated N/A a18-p1-nvsw-09 CPLD1 CPLD000370_REV0500 current N/A N/A a18-p1-nvsw-09 CPLD2 CPLD000377_REV0800 current N/A N/A a18-p1-nvsw-09 CPLD3 CPLD000373_REV0800 current N/A N/A a18-p1-nvsw-09 CPLD4 CPLD000390_REV0300 current N/A N/A a18-p1-nvsw-09 EROT 01.04.0018.0000_n04 completed N/A success: activated N/A a18-p1-nvsw-09 EROT-ASIC1 01.04.0018.0000_n04 current N/A N/A a18-p1-nvsw-09 EROT-ASIC2 01.04.0018.0000_n04 current N/A N/A a18-p1-nvsw-09 EROT-BMC 01.04.0018.0000_n04 current N/A N/A a18-p1-nvsw-09 EROT-CPU 01.04.0018.0000_n04 current N/A N/A a18-p1-nvsw-09 EROT-FPGA 01.04.0018.0000_n04 current N/A N/A a18-p1-nvsw-09 FPGA 0.1A current N/A N/A a18-p1-nvsw-09 SSD CE00A400 current N/A N/A a18-p1-nvsw-09 transceiver N/A current N/A N/A
Method 2 - Stand Alone nvfwupd Tool FW Update Process for NVLink Switch#
Doing firmware updates with the nvfwupd tool is an alternative method to using the BCM firmware upgrade process. This method is highly manual.
To start do module load cm-nvfwupd (if the NVIDIA Mission Control enabled license is active), otherwise run the command from the location of the nvfwupd tool.
Assess NVLink Switch FW Levels from the nvfwupd tool.
nvfwupd -t ip=<switch IP> user=admin password=Juliet@1234 servertype=gb200switch show_version
Compare the NVLink Switch versions found above with the versions in the update package.
nvfwupd -t ip=<switch IP> user=admin password=Juliet@1234 servertype=gb200switch show_version -p <file to compare version to>
In this example all three NVLink Switch update files are passed to nvfwupdate to compare the versions of all upgradeable components.
root@T06-HEAD-01:~/nvfwup/release files v2.0.5/aarch64# ./nvfwupd -t ip=<NVLink Switch COMe0 IP> user=admin password=Juliet@1234 servertype=gb200switch show_version -p ~/fw_0.9_releases/switch/nvfw_GB200-P4978_0004_250213.1.0_prod-signed.fwpkg ~/fw_0.9_releases/switch/nvfw_GB200-P4978_0006_250205.1.0_prod-signed.fwpkg ~/fw_0.9_releases/switch/nvfw_GB200-P4978_0007_250121.1.2_custom_prod-signed.fwpkg System Model: N5400_LD Part number: 920-9K36K-00MV-GS0 Serial number: MT250660041K Packages: ['GB200-P4978_0004_250213.1.0', 'GB200-P4978_0006_250205.1.0', 'GB200-P4978_0007_250121.1.2_custom'] Connection Status: Successful Firmware Devices: AP Name Sys Version Pkg Version Up-To-Date ------- ----------- ----------- ---------- ASIC 35.2014.1652 N/A No BIOS 0ACTV_00.01.012 00.01.012 Yes BMC 88.0002.0929 88.0002.0930 No CPLD1 CPLD000370_REV0500 CPLD000370_REV0500 Yes CPLD2 CPLD000377_REV0600 CPLD000377_REV0600 Yes CPLD3 CPLD000373_REV0500 CPLD000373_REV0500 Yes CPLD4 CPLD000390_REV0200 CPLD000390_REV0200 Yes EROT 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-ASIC1 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-ASIC2 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-BMC 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-CPU 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-FPGA 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes FPGA 0.1A 0.1A Yes SSD CE00A400 N/A No transceiver N/A N/A No ------------------------------------------------------------------------------------------------------------------------ Error Code: 0
Flash the NVLink Switch with the relevant package.
# Replace <switch IP> with the IP address of the switch nvfwupd -t ip=<switch IP> user=admin password=Juliet@1234 servertype=gb200switch update_fw -p /cm/local/apps/cmd/etc/htdocs/bios/firmware/gb200sw/nvfw_GB200-P4978_0000_241217.1.0_dbg-signed.fwpkg
Update the tray level firmware first in this order:
BMC+FPGA+ERoT (Switch BMC bundle).
CPLD1 CPLD2 CPLD3 CPLD4 (Switch CPLD bundle).
SBIOS+EROT (Switch BIOS bundle).
After a BMC update, the switch will need an AC cycle.
Reference: NVLink Switch AUX Power Cycle using the nvfwupd tool- NVLink Switch NVUE power cycle
root@T06-HEAD-01:~/nvfwup/release files v2.0.5/aarch64# ./nvfwupd -t ip=10.78.195.1 user=admin password=Juliet@1234 servertype=gb200switch activate_fw -c NVUE_PWR_CYCLE Power cycle task was created with ID 4 Status for Job Id 4: {'detail': 'File delete successfully', 'http_status': 200, 'issue': [], 'percentage': '', 'state': 'running', 'status': 'File delete successfully', 'timeout': 5, 'type': '', 'warnings': []}
Note
The CPLD and SBIOS versions can be updated sequentially without a power cycle between them. The firmware update command will automatically trigger an AC cycle on the next reboot.
After reboot, check the firmware versions to ensure the update has completed.
Reference: NVLink Switch Successful BMC Update
root@T06-HEAD-01:~/nvfwup/release files v2.0.5/aarch64# ./nvfwupd -t ip=<NVLink Switch COMe0 IP> user=admin password=Juliet@1234 servertype=gb200switch show_version -p ~/fw_0.9_releases/switch/nvfw_GB200-P4978_0004_250213.1.0_prod-signed.fwpkg ~/fw_0.9_releases/switch/nvfw_GB200-P4978_0006_250205.1.0_prod-signed.fwpkg ~/fw_0.9_releases/switch/nvfw_GB200-P4978_0007_250121.1.2_custom_prod-signed.fwpkg System Model: N5400_LD Part number: 920-9K36K-00MV-GS0 Serial number: MT250660041K Packages: ['GB200-P4978_0004_250213.1.0', 'GB200-P4978_0006_250205.1.0', 'GB200-P4978_0007_250121.1.2_custom'] Connection Status: Successful Firmware Devices: AP Name Sys Version Pkg Version Up-To-Date ------- ----------- ----------- ---------- ASIC 35.2014.1652 N/A No BIOS 0ACTV_00.01.012 00.01.012 Yes BMC 88.0002.0930 88.0002.0930 Yes CPLD1 CPLD000370_REV0500 CPLD000370_REV0500 Yes CPLD2 CPLD000377_REV0600 CPLD000377_REV0600 Yes CPLD3 CPLD000373_REV0500 CPLD000373_REV0500 Yes CPLD4 CPLD000390_REV0200 CPLD000390_REV0200 Yes EROT 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-ASIC1 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-ASIC2 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-BMC 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-CPU 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes EROT-FPGA 01.04.0008.0000_n04 01.04.0008.0000_n04 Yes FPGA 0.1A 0.1A Yes SSD CE00A400 N/A No transceiver N/A N/A No ------------------------------------------------------------------------------------------------------------------------ Error Code: 0
Method 3 - FW Updates within NVOS for NVLink Switch#
In the event that the installed license does not support NVIDIA Mission Control feature, but updates need to be done anyway, it can be done using the NVOS itself. However is it firmly recommended that all other methods are attempted first, and use this as a last resort.
Assess NVLink Switch FW Levels from the NVOS
nv show platform firmware
Example: Login to NVLink Switch and Get Firmware/Software Version Info
#Firmware admin@S04-P1-NVSW-01:~$ nv show platform firmware Name Actual FW Part Number FW Source ----------- ------------------- ------------------------------ --------- ASIC 35.2014.1652 920-9K36W-00MV-GS0_Ax default BIOS 0ACTV_00.01.012 N/A N/A BMC 88.0002.0929 692-13809-1404-000 N/A CPLD1 CPLD000370_REV0500 0x0172 N/A CPLD2 CPLD000377_REV0600 0x0179 N/A CPLD3 CPLD000373_REV0500 0x0175 N/A CPLD4 CPLD000390_REV0200 0x0186 N/A EROT 01.04.0008.0000_n04 N/A N/A EROT-ASIC1 01.04.0008.0000_n04 N/A N/A EROT-ASIC2 01.04.0008.0000_n04 N/A N/A EROT-BMC 01.04.0008.0000_n04 N/A N/A EROT-CPU 01.04.0008.0000_n04 N/A N/A EROT-FPGA 01.04.0008.0000_n04 N/A N/A FPGA 0.1A N/A N/A SSD CE00A400 Virtium VTPM24CEXI080-BM110006 N/A transceiver N/A N/A N/A
Note
Special Note on CPLD Upgrades (applicable to updating FW using NVOS only):
The CPLD archive is built into a
.fwpkgpackage file type. To perform a CPLD upgrade on the NVLink Switch, unpack this file to obtain the.vmefile required.Download the NVIDIA
fwpkg-unpacktool using PID 1090243.Unpack the CPLD
.fwpkgusing thefwpkg-unpacktool:./fwpkg-unpack --unpack nvfw_GB200-P4978_0007_250121.1.2_custom_prod-signed.fwpkg
A new CPLD file is extracted with a
.binfile extension. Rename the file to have a.vmeextension.BMC Firmware update and Reboot (BMC + FPGA + ERoT)
nv action fetch platform firmware BMC 'scp://root:nvis1234!@192.168.255.254/var/www/html/NVLink Switch/images/0.9.03/nvfw_GB200-P4978_0004_250226.1.0_prod-signed.fwpkg' nv action install platform firmware BMC files nvfw_GB200-P4978_0004_250226.1.0_prod-signed.fwpkg force
Note
System power cycle MUST be performed to force BMC to load the new FW version.
nv action power-cycle system force
CPLD Firmware update & Skip-Reboot (CPLD1 CPLD2 CPLD3 CPLD4)
nv action fetch platform firmware CPLD1 'scp://root:nvis1234!@192.168.255.254/var/www/html/nvswitch/images/0.9.03/CPLD_Prod_000370_REV0500_000377_REV0600_000373_REV0500_000390_REV0200_4717c08d_image.vme' nv action install platform firmware CPLD1 files CPLD_Prod_000370_REV0500_000377_REV0600_000373_REV0500_000390_REV0200_4717c08d_image.vme force skip-reboot
BIOS Firmware Upgrade & Skip-Reboot (SBIOS + ERoT)
nv action fetch platform firmware BIOS 'scp://root:nvis1234!@192.168.255.254/var/www/html/nvswitch/images/0.9.03/nvfw_GB200-P4978_0006_250205.1.0_prod-signed.fwpkg' nv action install platform firmware BIOS files nvfw_GB200-P4978_0006_250205.1.0_prod-signed.fwpkg force skip-reboot
NVLink Switch - Updating NVOS#
For NVOS updates, outside of doing BCM ZTP automation, must be done on the NVLink Switch itself/NVOS.
Get NVOS Version. ssh to the admin user of the NVLink Switch and run the ‘nv show system version command.
#OS Software admin@S04-P1-NVSW-01:~$ nv show system version operational ---------- ---------------------------- kernel 5.10.0-30-2-amd64 build-date Sun Feb 9 18:12:03 UTC 2025 image nvos-25.02.1877 onie 2023.11-5.3.0012-115200
To install a new version of the NVOS, get the binary onto the host:
Use scp to get the binary to the switch and save the file in /host/nvos-images/
Or use the fetch command from NVOS to pull the .bin file
nv action fetch system image 'scp://root:nvis1234!@192.168.255.254/var/www/html/nvswitch/images/0.9.03/nvos-amd64-25.02.1884.bin'
Check system images that are present.
admin@S03-P1-NVSW-07:~$ nv show system image operational ---------- --------------- current nvos-25.02.1877 next nvos-25.02.1877 partition1 nvos-25.02.1754 partition2 nvos-25.02.1877
Uninstall old images
Remove extra NVOS version image installed if present
nv action uninstall system image admin@S03-P1-NVSW-07:~$ nv action uninstall system image Action executing ... Uninstalling image: nvos-25.02.1754 Action executing ... Image nvos-25.02.1754 uninstalled successfully Action succeeded
Install the new image. After the installation is completed, the switch will automatically reboot into the updated OS.
#nv action install system image files new-nvos-image.bin admin@S03-P1-NVSW-07:~$ nv action install system image files nvos-amd64-25.02.1879.bin The operation will install the image and initiate a reboot. Type [y] to install the image and reboot. Type [N] to abort. Do you want to continue? [y/N] y Action executing ... Installing image: nvos-amd64-25.02.1879.bin Action executing ... Performing reboot ... Action executing ... Disconnecting from NVOS, system is offline during reboot Connection to s03-p1-nvsw-07 closed by remote host. Connection to s03-p1-nvsw-07 closed.
When the switch OS comes back up after the reboot, check that the new OS version was applied using nv show system image.
admin@S03-P1-NVSW-07:~$ nv show system image operational ---------- --------------- current nvos-25.02.1879 next nvos-25.02.1879 partition1 nvos-25.02.1877 partition2 nvos-25.02.1879
Check that the cluster apps are running on the switch that has been designated as the NMX-C master. This is typically NVSW-01.
admin@S04-P1-NVSW-01:~$ nv show cluster apps Name ID Version Capabilities Components Version Status Reason Additional Information Summary -------------- ------------- ---------------------- --------------------------------------------------- ----------------------------------------------------------------- ------ ------ ------------------------------ ------- nmx-controller nmx-c-nvos 0.9.0_2025-02-11_09-49 sm, gfm, fib, gw-api sm:2025.01.5, gfm:R570.120, fib-fe:0.9.0 ok CONTROL_PLANE_STATE_CONFIGURED nmx-telemetry nmx-telemetry 0.9.5 nvl telemetry, gnmi aggregation, syslog aggregation nvl-telemetry:1.20.1, gnmi-aggregator:1.0.1, nmx-connector:1.0.1 ok
If this returns No data, and this is not the NMX-C master node, no further action is required. However, if the NVSwitch is the master the apps need to be configured within the NVOS:
# Start cluster apps nv set cluster state enabled nv config apply nv config save nv show cluster apps
If the NMX controller (NMX-C) is in the ‘not ok’ and says ‘CONTROL PLANE_STATE_UNCONFIGURED’ , the fm_config.cfg file may need to be applied per this section where the fm_config.cfg file is generated.
admin@a18-p1-nvsw-01:~$ nv show cluster apps Name ID Version Capabilities Components Version Status Reason Additional Information Summary -------------- ------------- ---------------------- --------------------------------------------------- ----------------------------------------------------------------- ------ -------- -------------------------------- ------- nmx-controller nmx-c-nvos 0.9.0_2025-02-25_16-53 sm, gfm, fib, gw-api sm:2025.01.6, gfm:R570.124.02, fib-fe:0.9.0 not ok NMXC: OK CONTROL_PLANE_STATE_UNCONFIGURED
Re-run the litedaemon installation tool within BCM in order for the switch to show UP.
Note
Sometimes after a new NVOS installation, the default factory password gets reset to admin. Login with admin/admin, set the password to Juliet@1234 and then try again.
Example: NVOS Default State, Password Reset
NVOS switch admin@s03-p1-nvsw-04's password: You are required to change your password immediately (administrator enforced). ███╗ ██╗██╗ ██╗ ██████╗ ███████╗ ████╗ ██║██║ ██║██╔═══██╗██╔════╝ ██╔██╗ ██║██║ ██║██║ ██║███████╗ ██║╚██╗██║╚██╗ ██╔╝██║ ██║╚════██║ ██║ ╚████║ ╚████╔╝ ╚██████╔╝███████║ ╚═╝ ╚═══╝ ╚═══╝ ╚═════╝ ╚══════╝ Last login: Fri Mar 21 08:58:02 UTC 2025 from 10.78.192.25 on pts/0 Last failed login: Fri Mar 21 10:02:38 UTC 2025 from 10.78.192.25 on ssh:notty There was 1 failed login attempt since the last successful login. WARNING: Your password has expired. You must change your password now! New password: Retype new password: applied [rev_id: 1] Number of total successful connections since last 1 days: 3 Your password has been changed since last login
Note
A pause is expected after the new password change.