OSN2500 device SSQ2CXL single board non-stop reset network elements can not be logged on-Optical transimission network

News

OSN2500 device SSQ2CXL single board non-stop reset network elements can not be logged on

| 2025-11-21|Back

The OSN2500 device SSQ2CXL single board has two functional versions, Q2 and Q3. Q3CXL1 has been discontinued. CXL1 provides signal processing, service scheduling, clock input/output, and communication control in the OptiX OSN system, etc.The CXL single board provides timing information to the other single boards in the system, carries out the SDH signal processing, and completes the service scheduling of the various line boards and the services between the branch boards, and completes the communication with other single boards in the system and the configuration management of other single boards. CXL single board provides timing information to other single boards in the system, processes SDH signals, accomplishes the scheduling of services between line boards and branch boards, and accomplishes communication with other single boards in the system and configuration management of other single boards.Support optical module information detection and query. Supports VC-12/VC-3/VC-4 services.Support STM-1 signal segment overhead processing.Supports laser open and close settings and laser automatic shutdown function.Supports the use and monitoring of SFP pluggable optical modules, which facilitates the maintenance and upgrading of optical modules.Provides rich alarms and performance events for easy equipment management and maintenance.

Problem Description

The SSQ2CXL of a newly opened OSN2500 keeps resetting after powering up and is unable to log in.

Alarm message

None

Processing

1. After formatting the SSQ2CXL single board and working in BIOS state, analyzing the single board log file, the following records can be seen:

2007-12-5 No. 0:18:26 or so for the clearing and resetting operation

dmm say board 83 online time:2007: 12: 5: 0: 8: 38Call PLCallBackFuncForClrDB:dwRgnNo = 2

Call PLCallBackFuncForClrDB:dwRgnNo = 0

VFS_BackupToFlash time:2007-12-5 0: 13: 51Call PLCallBackFuncForClrDB:dwRgnNo = 1

VFS_BackupToFlash time:2007-12-5 0: 14: 7Call PLCallBackFuncForClrDB:dwRgnNo = 6

Init OCP Log OK 2007-12- 5 0:18:26 82 0

I pulled the board without waiting for the OCP database to finish storing, and waited until 2008-1-16 14:51:1 or so to re-power up the board.

2008-1-16 14:51:1 82 0xF0000004 0x2

Up OCP database is incomplete (10310001.F00 size is only 8 bytes, i.e. empty MO data)

Init OCP Log OK 2008- 1-16 14:51:28 82 0

/mfs/ocp/1310000.1 27

/mfs/ocp/10310001.F80 201620

/mfs/ocp/10310001.F00 8

To summarize: the reason for the constant reset of the bad parts of the single board opening is that the single board has been cleared after the production debugging, but the single board is pulled out or the power is cut off without waiting for the OCP database to be fully stocked, which leads to the incomplete preservation of the database and thus causes the constant reset.

2, reload the single board software, the single board normal start.

Root cause

not have

Recommendations and conclusions

1, SSQ2CXL single board opening bad constantly reset is caused by improper production debugging: single board in the production of debugging after the clearing operation, but did not wait for the OCP database inventory is complete before pulling out the single board or power-off operation, resulting in incomplete database preservation, which caused the single board constantly reset.

2, the normal operation of production debugging is as follows: SSQ2CXL single-board production debugging is completed, clearing operations, you should wait until the single-board reset and restart, you can normally log on to Navigator and then continue to wait for 3-5 minutes before pulling out of the board or power failure, to ensure that the database is preserved intact.

3、If you can log in Navigator, follow the instructions below to clear the database;

bms-delete-data:drdb

dbms-delete-data:fdb0

dbms-delete-data:fdb1

dbms-delete-data:nvfldb

sftm-delete-file:motherboard,"/mfs/ocp/mover"

sftm-delete-file:motherboard,"/mfs/ocp/mofile"

sftm-delete-file:motherboard,"/mfs/ocp/moptr"

sftm-delete-file:motherboard,"/mfs/ocp/dbfver"

sftm-delete-file:motherboard,"/ofs1/ocp/mover"

sftm-delete-file:motherboard,"/ofs1/ocp/mofile"

sftm-delete-file:motherboard,"/ofs1/ocp/moptr"