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

1

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.

Other related questions:
Software loading modes and their application environments on a BWS 1600G
Question: What are the software loading modes and their application environments on a BWS 1600G? None Analysis: None Answer: Currently, software loading modes on a BWS 1600G are as follows: 1. The software can be loaded by using the Navigator tool, which is an NE communication tool used for all OptiX series products. This mode is called Navigator tool loading for short in the following content. The software loading page varies slightly with different Navigator versions. 2. The software can be loaded by issuing a command line dedicated for the BWS 1600G. The procedure is to upload the file to be loaded to the NE, and then download the file form the NE to the board. The loading is implemented by issuing a command to the NE. This mode is called "NE command line loading" for short in the following content. Objects applicable to software loading: Navigator tool loading: 1. Common files of small size, such as the FPGA file and parameter table 2. In case of remote loading, only a few boards (such as the FIU, M40, and OAU boards) of the same model on an NE need to be upgraded. 3. This mode is recommended. NE command line loading: 1. Remote large files, which are the .dbd files (Note: The .dbd files are converted from the .esw files by using the clamv.exe tool.) 2. A lot of boards of the same model (such as the LWF, LWS, LRS, and LRF boards) on an NE need to be upgraded in remote loading manner. NE command line loading is recommended in this case and is designed for this requirement. Suggestion and conclusion: None

Whether an OHP2 board of a BWS1600G can be replaced by an OHP board of a BWS320G
An OHP2 board of a BWS 1600G cannot be replaced by an OHP board of a BWS 320G. BWS 320G also has 71OHP and 72OHP boards.

Whether OSN 6800 boards can be used in the BWS 1600G
No NG WDM board can be used in the BWS 1600G.

Whether the SC2 board on BWS 320G can be used on BWS 1600G
The SC2 board on BWS 320G cannot be used on BWS 1600G.

Whether the OHP2 board of BWS 1600G can be replaced by the OHP board of BWS 320G
The OHP2 board of BWS 1600G cannot be replaced by the OHP board of BWS 320G. BWS 320G also has 71OHP and 72OHP boards.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top