Keywords: MA5616, Access network product line
Summary
In MA5616 V800R312 equipped with an H831CCUB or H831CCUC control board, if data is
frequently saved into the database, the database malfunctions after the MA5616 runs for a
period of time. As a result, the MA5616 resets and starts from an empty database.
Problem Description
Trigger Conditions
This issue occurs if data is frequently saved into the database.
Each data saving reduces 256 bytes from the flash memory. When the remaining flash
memory is about 1 KB larger than the database file size, this issue occurs sometimes.
Symptom
The MA5616 database is cleared.
Identification Method
l For risky MA5616s:
Case 1:
This issue occurs after the MA5616 resets if the sizes of the database files in active and
standby partitions are both 0 KB.
MA5616(su)%%filesystem cmd dir /all
Directory of flash:/
0 -rw- 15361414 May 13 2013 05:07:43 program.efs
………………………………
51 -rw- 59668 Aug 14 2013 04:04:16 log_oper00.dat
52 -rw- 0 Aug 11 2013 22:31:25 data.dat
53 -rw- 0 Aug 13 2013 02:27:19 data_bak.dat
57785 KB total (83 KB free)
Case 2:
This issue occurs after data is saved into the database several times and the MA5616
resets if the size of the database file in a partition is 0 KB.
MA5616(su)%%filesystem cmd dir /all
Directory of flash:/
0 -rw- 15361414 May 15 2013 00:20:39 program.efs
……………………………………
51 -rw- 58467 Aug 07 2013 14:57:17 log_oper00.dat
52 -rw- 95309 Aug 27 2013 22:35:31 data.dat
53 -rw- 0 Aug 27 2013 22:35:15 data_bak.dat
57785 KB total (94 KB free)
Case 3:
This issue occurs sometimes after the MA5616 runs a period of time and meanwhile
data is frequently saved into the database if the sizes of the database files in active and
standby partitions are greater than 0 KB but the remaining flash memory is nearly the
same as the size of the database file.
MA5616(su)%%filesystem cmd dir /all
Directory of flash:/
0 -rw- 15361414 May 21 2013 21:51:07 program.efs
………………………………
49 -rw- 65296 Aug 22 2013 01:53:29 log_oper00.dat
50 -rw- 91636 Aug 27 2013 23:50:05 data.dat
51 -rw- 91636 Aug 27 2013 23:49:55 data_bak.dat
57785 KB total (107 KB free)
l For affected MA5616s:
Log in to the MA5616s to query configuration files after confirming that the database
is not manually cleared.
MA5616(config)%% display current-configuration
If only original configuration data remains in the configuration file, this issue has occurred.
Root Cause
The mechanism of writing data into the MA5616 database is defective. As a result, the
dbupdate.bin redundant file uses the flash memory. If the remaining flash memory is
about 1 KB larger than the database file size, saving data into the database results in a
database exception. After the MA5616 resets, the database is cleared.
Impact and Risk
The MA5616 configuration restores to default settings, which results in service failures.
Measures and Solutions
Recovery Measures
For the affected MA5616s, perform the following operations:
1. Configure data again or import the correct database file into the MA5616s. Then,
reset the MA5616s.
2. Run the save command to save the data.
3. Run the following command to delete the dbupdate.bin file:
MA5616(su)%%filesystem cmd delete dbupdate.bin
The contents cannot be recycled!!! Delete flash:/dbupdate.bin?[confirm]:y
Workarounds
For the risky MA5616s, perform the following operations:
1. Delete the dbupdate.bin file to ensure that the remaining flash memory is sufficient.
MA5616(su)%%filesystem cmd delete dbupdate.bin
The contents cannot be recycled!!! Delete flash:/dbupdate.bin?[confirm]:y
2. In su mode, delete invalid database files (size: 0 KB), regardless whether the database
file is in the active or standby partition.
MA5616(su)%%filesystem cmd delete data.dat
The contents cannot be recycled!!! Delete flash:/ data.dat?[confirm]:y
MA5616(su)%%filesystem cmd delete data_bak.dat
The contents cannot be recycled!!! Delete flash:/ data_bak.dat?[confirm]:y
3. Manually save the database file. If the database file can be saved, the issue is rectified.
Preventive Measures
Load V800R312C00SPH206.
Prewarning Retraction Conditions
This prewarning can be retracted if issue triggering conditions are not met.
Attachment
None
Comments are closed