No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Failed to configure cross connections due to abnormal NE database.

Publication Date:  2012-07-25 Views:  81 Downloads:  0
Issue Description
Equipment Type: OSN7500
Equipment version: V100R008 (5.21.18.53)
NMS version:  T2000V200R006

Problem was escalated by customer that we are unable to configure cross connections on NE. It was also checked and confirmed by the customer that ports were free upon which they tried to configure cross connections. Also it was found that upon cross configuration more than 1, 1st cross connection configuration failed and others cross connections configured successfully. Following error appeared upon configuration failure. Snap is also attached.
"Cross Connection Already Exist, Error Code: 38702"

Alarm Information
"Cross Connection Already Exist, Error Code: 38702"
Handling Process
Following steps performed to resolve this problem.

1- Before cross connection configuration, ports were checked and found free. Also there was no unidirectional cross connection exist on NE or NMS.
2- NE data was uploaded and synchronized but problem was not resolved.
3- It was checked to configure cross connections by using Navigator. Cross configuration configuration was successful from Navigator while configuration failed from T2000.

#9-213:szhw [LLRe01_OSN7500_1                                                ][][2011-08-18 19:04:30+08:00]>
:cfg-add-xc:0,5,1,15,17,6,1,5,59,vc12

#9-213:szhw [LLRe01_OSN7500_1                                                ][][2011-08-18 19:04:59+08:00]>
:cfg-add-xc:0,6,1,5,59,5,1,15,17,vc12

#9-213:szhw [LLRe01_OSN7500_1                                                ][][2011-08-18 19:05:21+08:00]>
:cfg-add-xc:0,5,1,15,17,13,1,5,59,vc12

#9-213:szhw [LLRe01_OSN7500_1                                                ][][2011-08-18 19:06:15+08:00]>
:cfg-verify
4- After above steps, GSCC active/standby switching was performed but not useful.
5- Then SSN2GSCC boards were replaced with SSN3GSCC boards to resolve this issue. But after replacing the board, same problem ocurred. 
6- After all above steps, NE database was checked with database checker tool and found abnormal logs. Upon simulation of NE database in lab, it was found that the database of this node is abnormal.
7- After above findings, NE database was deleted with following steps and configuration was downloaded from T2000. After successful configuration download, cross connections were configured and found normal.

Database deletion commands:
V100R008 and later versions:
:dbms-delete-data:drdb;
:dbms-delete-data:fdb;
:dbms-delete-data:cfdb;  (if cf card is available)
After running these commands, soft reset standby GSCC board, wait for synchronization then soft reset active GSCC board.
V100R007 version:
:dbms-delete-data:drdb;
:dbms-delete-data:fdb0;
:dbms-delete-data:fdb1;
:dbms-delete-data:nvfldb;
After running these commands, soft reset standby GSCC board, wait for synchronization then soft reset active GSCC board.
V100R003 ~ V100R006 versions:
:dbms-delete-data:drdb;
:dbms-delete-data:fdb0;
:dbms-delete-data:fdb1;
:dbms-delete-data:nvfldb;
:sftm-delete-file:active board,"/mfs/ocp/mover"
:sftm-delete-file:active board,"/mfs/ocp/mofile"
:sftm-delete-file:active board,"/mfs/ocp/moptr"
:sftm-delete-file:active board,"/mfs/ocp/dbfver"
:sftm-delete-file:active board,"/ofs1/ocp/mover"
:sftm-delete-file:active board,"/ofs1/ocp/mofile"
:sftm-delete-file:active board,"/ofs1/ocp/moptr"
:sftm-delete-file:active board,"/ofs1/ocp/dbfver"
:sftm-delete-file:active board,"/ofs2/ocp/mover"
:sftm-delete-file:active board,"/ofs2/ocp/mofile"
:sftm-delete-file:active board,"/ofs2/ocp/moptr"
:sftm-delete-file:active board,"/ofs2/ocp/dbfver"
:sftm-delete-file:standby board,"/mfs/ocp/mover"
:sftm-delete-file:standby board,"/mfs/ocp/mofile"
:sftm-delete-file:standby board,"/mfs/ocp/moptr"
:sftm-delete-file:standby board,"/mfs/ocp/dbfver"
:sftm-delete-file:standby board,"/ofs1/ocp/mover"
:sftm-delete-file:standby board,"/ofs1/ocp/mofile"
:sftm-delete-file:standby board,"/ofs1/ocp/moptr"
:sftm-delete-file:standby board,"/ofs1/ocp/dbfver"
:sftm-delete-file:standby board,"/ofs2/ocp/mover"
:sftm-delete-file:standby board,"/ofs2/ocp/mofile"
:sftm-delete-file:standby board,"/ofs2/ocp/moptr"
:sftm-delete-file:standby board,"/ofs2/ocp/dbfver"
After running these commands, soft reset standby GSCC board, wait for synchronization then soft reset active GSCC board.


Root Cause
Following are the possible causes for the above problem.

1- Ports already used.
2- Unidirectional cross connections exist on NE.
3- NE and NM data inconsistency.
4- NMS version is not compatible with NE version.
5- SCC board's fault
6- XCS board's fault.
Suggestions
Whenever this kind of problem happens, first check the NE database, if found abnormal then perform above handling steps to resolve this problem.

END