Hello, everyone!
Today will share with you a case about SNCP do not work.
Problem Description:
There was fiber cut on customer network. But the SNCP do not work on problem NE.
Handling procedure:
During recreation of the service there was an error 38754 on the problem NE and service cannot be created
Check the service configuration. The SNCP ID for problem service on NE is 251. While check the state of this SNCP, NE return error
#0x99c49:cfg-get-sncpstate:251;
failed!
For this abnormal configuration, SCC cannot recognize, but XC board can. While send that command to XC board, XC board cannot create it successfully and rollback. Then the SNCP is lost. Thus mean about SNCP cannot switch.
Root cause:
It is a software bug, already resolve at V100R008C02SPH505.
In common there were many mistakenly configured services but due to the old software SCC can not to recognize the errors and allows finishing configuration procedure. But actually services was not configured correctly.
Solution:
So solution was to install SPH505 on the NE and download all configurations from NMS to NE.
Detail solution is below:
1. Upgrade to V100R008C02SPH505.
2. Recovering Databases by Deleting Database and Resetting SCC Boards
Clear the system control databases of the NE.
Stop the automatic backup and periodical backup of the databases by running the following commands.
:dbms-set-autobackup:disable
:dbms-set-cyclebackup:disable
Delete all system control database files by running the following commands.
For OptiX NG-SDH V100R008 or earlier versions:
:dbms-delete-data:drdb
:dbms-delete-data:fdb
:dbms-delete-data:fdb0
:dbms-delete-data:fdb1
:dbms-delete-data:nvfldb;//If Bad para is returned, ignore it.
:dbms-delete-data:cfdb;//Run the command if a CF card is equipped.
Run the following commands in turn. Change the "master board" to the slot ID of the main system control board and the "slave board" to the slot ID of the standby system control board. If the 0xb343 NSERR_SFTM_FILE_NOTEXIST message indicating that the file does not exist is returned, ignore it.
:sftm-delete-file:master board,"/mfs/ocp/mover"
:sftm-delete-file:master board,"/mfs/ocp/mofile"
:sftm-delete-file:master board,"/mfs/ocp/moptr"
:sftm-delete-file:master board,"/mfs/ocp/dbfver"
:sftm-delete-file:master board,"/ofs1/ocp/mover"
:sftm-delete-file:master board,"/ofs1/ocp/mofile"
:sftm-delete-file:master board,"/ofs1/ocp/moptr"
:sftm-delete-file:master board,"/ofs1/ocp/dbfver"
:sftm-delete-file:master board,"/ofs2/ocp/mover"
:sftm-delete-file:master board,"/ofs2/ocp/mofile"
:sftm-delete-file:master board,"/ofs2/ocp/moptr"
:sftm-delete-file:master board,"/ofs2/ocp/dbfver"
:sftm-delete-file:slave board,"/mfs/ocp/mover"
:sftm-delete-file:slave board,"/mfs/ocp/mofile"
:sftm-delete-file:slave board,"/mfs/ocp/moptr"
:sftm-delete-file:slave board,"/mfs/ocp/dbfver"
:sftm-delete-file:slave board,"/ofs1/ocp/mover"
:sftm-delete-file:slave board,"/ofs1/ocp/mofile"
:sftm-delete-file:slave board,"/ofs1/ocp/moptr"
:sftm-delete-file:slave board,"/ofs1/ocp/dbfver"
:sftm-delete-file:slave board,"/ofs2/ocp/mover"
:sftm-delete-file:slave board,"/ofs2/ocp/mofile"
:sftm-delete-file:slave board,"/ofs2/ocp/moptr"
:sftm-delete-file:slave board,"/ofs2/ocp/dbfver"
Check whether the system control databases have been cleared by running the following commands.
:dbms-get-list:drdb
:dbms-get-list:fdb0
:dbms-get-list:fdb1
Normally, the "failed! cmd:0x3005 error:0x9205 NSERR_DBMS_HEAD_CHECK_ERROR" message should be returned. If the message is not returned, the database clearing operation fails and you need to perform step 4 again.
For OptiX NG-SDH V100R008 and earlier versions, if database clearing commands can be executed successfully but the returned message is not "failed! cmd:0x3005 error:0x9205 NSERR_DBMS_HEAD_CHECK_ERROR", ignore it and go to the next step.
Reset the system control board.
Warm reset the standby system control board. Wait for 10s and warm reset the main system control board.
After the system control board is reset, restart the automatic backup and periodical backup of the databases by running the following commands.
:dbms-set-autobackup:enable
:dbms-set-cyclebackup:enable
3. Run below commands disable the lxcoptmz
:cfg-set-1j1lmsp-lxcoptmz:disable
:cfg-verify
4. Download NMS configuration data to the NE in uninterrupted mode.
Suggestion:
Suggestion is using the latest recommended software include recommended patches. Due to customer used only main software release but without patches problem is happened.
That's all! Hope you find my post useful. Please let me know in the comment section if you have any further concerns or remarks.
Thank you!
