Got it

CSHNU

Created: Sep 14, 2020 09:09:02Latest reply: Sep 14, 2020 11:57:07 612 7 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

hi! I have a problem need your support. 

- We have purchased CSHNU board within 02 difference phases and we have tried to combine those 02 boards (phase-1 and 2) together into a single sub-rack RTN980 but there were alarms SYN_FAILED and COMMFAILED (if i'm not mistake).

- We confirmed that those 02 boards are the same Item, version and BOM.


thanks!

Featured Answers

Recommended answer

BetterMing
Created Sep 14, 2020 11:57:07

You can refer to the following information for alarm handling.

SYNC_FAIL

Description

The SYNC_FAIL alarm indicates that the batch backup on SCC boards fails.

Attribute

Alarm SeverityAlarm Type
MinorProcessing alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

NameMeaning
Parameter 1

Indicates the cause of the failure.

  • 0x1F: The database backup fails.

  • 0x20: Software version verification fails on the main and standby SCC boards.

  • 0x21: Communication between the main and standby SCC boards fails.

  • 0x22: The main and standby SCC boards have different data after an upgrade.

  • 0x23: Forced switching occurs between the main and standby SCC boards before database backup is completed.

Parameter 2Always 0xff
Parameter 3Always 0xff

Impact on the System

Data synchronization between the main and standby SCC boards fails, and the switching between the two boards is unavailable.

Possible Causes

  • Cause 1: The main and standby SCC boards have different versions of software.

  • Cause 2: Databases on the main and standby SCC boards are damaged.

  • Cause 3: The main and standby SCC boards have different data after an upgrade.

  • Cause 4: Communication between the main and standby SCC boards fails.

  • Cause 5: Forced switching occurs between the main and standby SCC boards before database backup is completed.

Procedure

  1. Cause 1: The main and standby SCC boards have different versions of software.

    1. Query and record the software versions of the main and standby SCC boards according to Querying the Board Information Report.

    2. If the software versions are different, determine the correct version based on the version mapping table and replace the SCC board with an incorrect version. For details, see Replacing the System Control, Switching and Timing Board.

  2. Cause 2: Databases on the main and standby SCC boards are damaged.

    1. Check whether the system reports the DBMS_ERROR alarm. For details, see Browsing Current Alarms.

    2. If yes, clear the DBMS_ERROR alarm. Then, check whether the SYNC_FAIL alarm is cleared.

  3. Cause 3: The main and standby SCC boards have different data after an upgrade.

    1. Re-install the standby SCC board.

  4. Cause 4: Communication between the main and standby SCC boards fails.

    1. Check whether the system reports the COMMUN_FAIL alarm.

    2. If yes, clear the COMMUN_FAIL alarm. The system will start batch backup automatically.

  5. Cause 5: Forced switching occurs between the main and standby SCC boards before database backup is completed.

    1. Warm reset the alarmed board by following instructions in Warm Reset.

COMMUN_FAIL

Description

The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This alarm is reported when the communication between a board and the SCC board is interrupted.

Attribute

Alarm SeverityAlarm Type

Major

Equipment alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.
NameMeaning

Parameter 1

Indicates the ID of the port. The value is always 0x01.

Parameter 2, Parameter 3

Indicates the ID of the path on which the alarm is generated. Parameter 2 is always 0x00. Parameter 3 has the following meanings:

0x03: inter-board Ethernet communication

Parameter 4, Parameter 5

Parameters 4 and 5 are reserved, and their values are always 0xFF.

Impact on the System

The NE configuration cannot be delivered to the board or the board cannot work. Consequently, the services cannot be configured or the protection switching function is unavailable.

Possible Causes

  • Cause 1: A certain board is reset.

  • Cause 2: A board and the backplane are connected improperly.

  • Cause 3: The alarmed board is faulty.

  • Cause 4: A slot is faulty.

  • Cause 5: When the active and standby system control boards switch over, communication between them are interrupted transiently.

Procedure

  1. Cause 1: A certain board is reset.

    1. After you reset the board, the alarm is cleared automatically.

  2. Cause 2: A board and the backplane are connected improperly.

    1. Remove and insert the alarmed board. For details, see Removing a Board and Inserting a Board. Then, check whether the alarm is cleared.

      If...

      Then...

      The alarm is cleared after the board is removed and inserted

      The fault is rectified. End the alarm handling.

      The alarm persists after the board is replaced.

      Clear the alarm according to the solution for the alarm that is generated when a board is faulty.

  3. Cause 3: The alarmed board is faulty.

    1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see Part Replacement.

      If...

      Then...

      The alarm is cleared after the board is replaced

      The fault is rectified. End the alarm handling.

      The alarm persists after the board is replaced

      Clear the alarm according to the solution for the alarm that is generated when a slot is faulty.

  4. Cause 3: A slot is faulty.

    1. Contact Huawei technical support engineers to handle the faulty slot.

      note_3.0-en-us.png

      The slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to check whether any pins are broken or bent.

    2. If a vacant slot is available, insert the board in the vacant slot, and then update the data on the NMS so that the board can work normally.

  5. Cause 5: When the active and standby system control boards switch over, communication between them are interrupted transiently.

    1. It is normal that this alarm is reported during the switchover, so this alarm does not need to be handled.


View more
  • x
  • convention:

Chanphirun
Chanphirun Created Sep 15, 2020 02:09:42 (0) (0)
we have tried all your possible solution but it doesn't fix. Those boards are all the same BOM, item ID,...  
BetterMing
BetterMing Reply Chanphirun  Created Sep 15, 2020 06:07:31 (0) (0)
If it still cannot be handled, I suggest you contact your local Huawei representative office for technical support. https://e.huawei.com/en/service-hotline-query  
All Answers

Dear friend!
Please rest assured that we'll be back with an answer shortly.
View more
  • x
  • convention:

Chanphirun
Chanphirun Created Sep 14, 2020 11:04:17 (0) (0)
hi!
my mistake. here are an alarms, SYNC_FAIL, COMMUN_FAIL.  
Hello, Chanphirun.
The alarm is not found on the OptiX RTN 980. Check the alarm name.
View more
  • x
  • convention:

Posted by BetterMing at 2020-09-14 10:33 Hello, Chanphirun.The alarm is not found on the OptiX RTN 980. Check the alarm name.
hi!
my mistake. here are an alarms, SYNC_FAIL, COMMUN_FAIL.
View more
  • x
  • convention:

You can refer to the following information for alarm handling.

SYNC_FAIL

Description

The SYNC_FAIL alarm indicates that the batch backup on SCC boards fails.

Attribute

Alarm SeverityAlarm Type
MinorProcessing alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

NameMeaning
Parameter 1

Indicates the cause of the failure.

  • 0x1F: The database backup fails.

  • 0x20: Software version verification fails on the main and standby SCC boards.

  • 0x21: Communication between the main and standby SCC boards fails.

  • 0x22: The main and standby SCC boards have different data after an upgrade.

  • 0x23: Forced switching occurs between the main and standby SCC boards before database backup is completed.

Parameter 2Always 0xff
Parameter 3Always 0xff

Impact on the System

Data synchronization between the main and standby SCC boards fails, and the switching between the two boards is unavailable.

Possible Causes

  • Cause 1: The main and standby SCC boards have different versions of software.

  • Cause 2: Databases on the main and standby SCC boards are damaged.

  • Cause 3: The main and standby SCC boards have different data after an upgrade.

  • Cause 4: Communication between the main and standby SCC boards fails.

  • Cause 5: Forced switching occurs between the main and standby SCC boards before database backup is completed.

Procedure

  1. Cause 1: The main and standby SCC boards have different versions of software.

    1. Query and record the software versions of the main and standby SCC boards according to Querying the Board Information Report.

    2. If the software versions are different, determine the correct version based on the version mapping table and replace the SCC board with an incorrect version. For details, see Replacing the System Control, Switching and Timing Board.

  2. Cause 2: Databases on the main and standby SCC boards are damaged.

    1. Check whether the system reports the DBMS_ERROR alarm. For details, see Browsing Current Alarms.

    2. If yes, clear the DBMS_ERROR alarm. Then, check whether the SYNC_FAIL alarm is cleared.

  3. Cause 3: The main and standby SCC boards have different data after an upgrade.

    1. Re-install the standby SCC board.

  4. Cause 4: Communication between the main and standby SCC boards fails.

    1. Check whether the system reports the COMMUN_FAIL alarm.

    2. If yes, clear the COMMUN_FAIL alarm. The system will start batch backup automatically.

  5. Cause 5: Forced switching occurs between the main and standby SCC boards before database backup is completed.

    1. Warm reset the alarmed board by following instructions in Warm Reset.

COMMUN_FAIL

Description

The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This alarm is reported when the communication between a board and the SCC board is interrupted.

Attribute

Alarm SeverityAlarm Type

Major

Equipment alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.
NameMeaning

Parameter 1

Indicates the ID of the port. The value is always 0x01.

Parameter 2, Parameter 3

Indicates the ID of the path on which the alarm is generated. Parameter 2 is always 0x00. Parameter 3 has the following meanings:

0x03: inter-board Ethernet communication

Parameter 4, Parameter 5

Parameters 4 and 5 are reserved, and their values are always 0xFF.

Impact on the System

The NE configuration cannot be delivered to the board or the board cannot work. Consequently, the services cannot be configured or the protection switching function is unavailable.

Possible Causes

  • Cause 1: A certain board is reset.

  • Cause 2: A board and the backplane are connected improperly.

  • Cause 3: The alarmed board is faulty.

  • Cause 4: A slot is faulty.

  • Cause 5: When the active and standby system control boards switch over, communication between them are interrupted transiently.

Procedure

  1. Cause 1: A certain board is reset.

    1. After you reset the board, the alarm is cleared automatically.

  2. Cause 2: A board and the backplane are connected improperly.

    1. Remove and insert the alarmed board. For details, see Removing a Board and Inserting a Board. Then, check whether the alarm is cleared.

      If...

      Then...

      The alarm is cleared after the board is removed and inserted

      The fault is rectified. End the alarm handling.

      The alarm persists after the board is replaced.

      Clear the alarm according to the solution for the alarm that is generated when a board is faulty.

  3. Cause 3: The alarmed board is faulty.

    1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see Part Replacement.

      If...

      Then...

      The alarm is cleared after the board is replaced

      The fault is rectified. End the alarm handling.

      The alarm persists after the board is replaced

      Clear the alarm according to the solution for the alarm that is generated when a slot is faulty.

  4. Cause 3: A slot is faulty.

    1. Contact Huawei technical support engineers to handle the faulty slot.

      note_3.0-en-us.png

      The slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to check whether any pins are broken or bent.

    2. If a vacant slot is available, insert the board in the vacant slot, and then update the data on the NMS so that the board can work normally.

  5. Cause 5: When the active and standby system control boards switch over, communication between them are interrupted transiently.

    1. It is normal that this alarm is reported during the switchover, so this alarm does not need to be handled.


View more
  • x
  • convention:

Chanphirun
Chanphirun Created Sep 15, 2020 02:09:42 (0) (0)
we have tried all your possible solution but it doesn't fix. Those boards are all the same BOM, item ID,...  
BetterMing
BetterMing Reply Chanphirun  Created Sep 15, 2020 06:07:31 (0) (0)
If it still cannot be handled, I suggest you contact your local Huawei representative office for technical support. https://e.huawei.com/en/service-hotline-query  

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.