Method for enabling automatic synchronization for the system control board when the SYNC_DISABLE alarm is reported

1

This alarm is not reported when the NE is running properly. This alarm is reported to instruct onsite engineers to enable automatic synchronization for the system control board if it is disabled during deployment or commissioning.

Other related questions:
Problem and solution when the controller enclosure alarm indicator is on but no alarm is reported on the storage system
You can perform the following operations when the controller enclosure alarm indicator is on but no alarm is reported on the storage system: 1. Fault location and rectification a. Log in to the storage system and check whether alarm information is reported. b. Query the SES log and confirm the cause and last time when the alarm indicator is on. c. Check the SES and message log to find why the indicator is on. 2. Fault Diagnosis a. Search start led(0x0) (off) and (0x1) (on) in the SES log. Verify the last time when the alarm indicator is on. b. Check in the historical alarms whether the alarm is recovered when the indicator is on. c. Analyze turn-off and turn-on records in the message logs of controllers A and B. Search keyword light. d. If the alarm is recovered and the controller does not send a turn-off command, send the command manually. 3. Solution Send the mml:dev sesstartlight 0 command to the controller whose indicator is turned on and then not off. Note: The controller enclosure alarm indicator follows the same rule as the disk indicator does that the same indicator is turned on and then off. The above method is only applicable to the situation where the controller enclosure alarm indicator is on.

Reason for the failure to report alarms by boards in a subrack when a large number of SHELF_AREA_POWER_OVER alarms are reported
The SHELF_AREA_POWER_OVER alarm indicates that the nominal power consumption of a subrack section exceeds the specified threshold. This alarm is reported when the total nominal power consumption of boards in a subrack section of an NE is greater than or equal to the power consumption threshold of the subrack section. This alarm is reported on the system control boards, such as SCC and 16XCH/16UXCM. If the alarm is present, the subrack is overloaded. When this occurs, you need to remove boards from the corresponding subrack section as required. If the subrack is running in overloaded state for a long time, the power supply to the subrack may be abnormal or interrupted.

Alarms that are generated when the SCC board is frequently reset
1. When the SCC board is reset, the SCC_LOC alarm is generated. When the SCC board is reset frequently, the SCC_LOC alarm is repeatedly generated and cleared. 2. Service boards transiently report the BD_STATUS or COMMUN_FAIL alarm, and the U2000 frequently reports the NE_COMMU_BREAK, NE_NOT_LOGIN, and GNE_CONNECT_FAIL alarms.

Method used to handle the TEMP_OVER alarm reported by the CXP board
1. Check whether a fan stops running on the fan board. If yes, remove and insert the fan board. If no, go to the next step. 2. Clean the air filter.

Setting the Raman board alarm reporting parameter to Enabled
The CRPC01 board supports fiber cut detection. That is, when the CRPC01 board detects an IPA trigger condition, the IPA function will shut down the transmitting laser on the CRPC01 board. This, however, can be achieved only when the following conditions are satisfied: 1. The CRPC01 board is configured as the Raman Amplifier. 2. At least one of the 192.4 THz to 192.1 THz wavelengths is configured in the system. In a system with 50 GHz channel spacing, at least one of the following wavelengths is configured in the system: 192.4 THz, 192.35 THz, 192.3 THz, 192.25 THz, 192.2 THz, 192.15 THz, and 192.1 THz. In a system with 100 GHz channel spacing, at least one of the following wavelengths is configured in the system: 192.4 THz, 192.3 THz, 192.2 THz, and 192.1 THz. 3. Raman Board Alarm Reporting is set to Enabled. 4. Raman Board Threshold (dBm) is set correctly. Note: If wavelengths 192.4THz-192.1THz are not configured in the system, Raman Board Alarm Reporting must be set to Disabled.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top