Methods for loading the board software on BWS 1600G and their respective application scenarios

Currently, BWS 1600G supports the following board software loading methods:
1. Using the Navigator (unified NE communication tool of OptiX products): This method is referred to as Navigator-based loading in the following context. The loading page varies slightly depending on Navigator versions.
2. CLI dedicated to BWS 1600G: Files to be loaded are uploaded to the NE, and then downloaded from the NE to boards. The loading is started by issuing a command to the NE. This method is referred to as CLI-based loading in the following context.
Application scenarios:
Navigator-based loading:
1. Common small files, such as FPGA files and parameter table files.
2. During remote loading, only a few boards of the same type, for example, FIU, M40, or OAU, need to be upgraded on an NE subrack.
3. Generally, Navigator-based loading is recommended.
CLI-based loading:
1. Remote loading of large files, which are mainly *.dbd board software files. (*.dbd files are converted from *.esw files using the clamv.exe tool.)
2. For remote loading, a large number of boards of the same type, such as LWF, LWS, LRS, or LRF, need to be upgraded. The CLI-based loading method is designed for this special scenario and is recommended.

Scroll to top