Abstract: When the license module processes interchange messages for hot standby between the working and protection main control boards, commissioning information will accumulate to the flash and finally exhaust the flash space. As a result, configuration data fails to be saved and database backup fails.
[Problem Description]
Trigger conditions:
Two main control boards are configured on an NE of a version listed in “Involved Versions”.
Symptom:
The flash space on the protection main control board is consumed at a speed twice of that on the working main control board. Therefore, this issue occurs on the protection main control board earlier than on the working main control board.
1. If no sufficient flash space is available for periodic database backup, the backup will fail and the DBMS_ERROR alarm will be reported.
2. Extra small files need to be generated in the case of configuration deployment or dynamic services. If no sufficient flash space is available, these files cannot be generated, causing an NE reset and inconsistency between the working and protection main control boards (the result of :hbu-get-backup-info is 0x00000002).
3. If the flash space is insufficient during an NE upgrade, the upgrade will fail.
Identification method
- An NE of a version listed in “Involved Versions” is deployed.
- The NE has two main control boards.
[Root Cause]
When the license module processes interchange messages for hot standby between the working and protection main control boards, commissioning information will accumulate to the flash and finally exhaust the flash space. (The working main control board consumes 1 M flash space per 20 days and the protection main control board consumes 1 M flash space per 10 days.)
[Impact and Risks]
The flash space will be exhausted.
1. If the flash space is insufficient for periodic database backup, the backup will fail and all new configuration data may be lost upon a reset.
2. If the flash space is insufficient, desired small files cannot be generated, causing an NE reset and inconsistency between the working and protection main control boards (the result of :hbu-get-backup-info is 0x00000002). In addition, a rest on the working main control board may result in loss of new configuration data. .
3. If the flash space is insufficient during an NE upgrade, the upgrade fails.
[Measures and Solutions]
Recovery measures:
- If the DBMS_ERROR alarm is reported, do as follows:
1. Run the following commands to query whether the HBUMSG.TXT file exists on the working or protection main control board:
:sftm-show-dir:working board,”ofs1/license”
:sftm-show-dir:protection board,”ofs1/license”
2. If yes, run the following commands to delete the file:
:sftm-delete-file:working board,”ofs1/license/HBUMSG.TXT”
:sftm-delete-file:protection board,”ofs1/license/HBUMSG.TXT”
- If the protection main control board is reset, do as follows:
1. If data synchronization fails between the working and protection Huawei main control board, issue the following command to the working main control board:
:sm-set-nebusy:0,0,0,0,none
2. Run the following commands to query whether the HBUMSG.TXT file exists on the working or protection main control board:
:sftm-show-dir:working board,”ofs1/license”
:sftm-show-dir:protection board,”ofs1/license”
3. If yes, run the following commands to delete the file:
:sftm-delete-file:working board,”ofs1/license/HBUMSG.TXT”
:sftm-delete-file:protection board,”ofs1/license/HBUMSG.TXT”
- If the working main control board is reset, do as follows:
1. If data synchronization fails between the working and protection main control board, issue the following command to the working main control board:
:sm-set-nebusy:0,0,0,0,none
2. Run the following commands to query whether the HBUMSG.TXT file exists on the working or protection main control board:
:sftm-show-dir:working board,”ofs1/license”:sftm-show-dir:protection board,”ofs1/license”
3. If yes, run the following commands to delete the file:
sftm-delete-file:working board,”ofs1/license/HBUMSG.TXT”
:sftm-delete-file:protection board,”ofs1/license/HBUMSG.TXT”
4. If new configuration data is lost, reconfigure the new services.
Workarounds:
Use the health check tool to periodically (recommended: every six months) check the NEs of the involved versions on the live network. For details on the health check tool, see “Support for the Health Check Tool.”
Solution:
For OSN 3500/OSN 7500 product, upgrade software to V200R011C00SPC300 or a later version.
For OSN 1500 product, upgrade software to V200R011C00SPC300 or a later version; or upgrade software to V200R011C01SPC103 or a later version.
Material handling after replacement:
None
[Support for the Health Check Tool]
The SmartKit NSE2700 V200R006C00 Inspector is supported and can be upgraded to the latest version. The health check item is “Common_Platform_Checking/Check if HBUMSG.TXT file exist in active and standby SCC”.
[Rectification Scope and Time Requirements]
None
Comments are closed