Got it

Temperature alarm on OSN

Created: Mar 17, 2021 12:56:13Latest reply: Mar 18, 2021 01:16:47 398 10 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello everyone!

I cannot clear alarm temporature on baord in OSN 8800, please kindly show me how to solve it step by step with deatils.

BR,

Featured Answers
Chanbora
Created Mar 18, 2021 01:16:47

Hello friend!

Can follow these:

1. Run the :cfg-get-scc-temperature:bid command to query the actual temperature of the board. The query result is 22.3?C, which is within the normal range.
2. Run the alm-del-curdata:num command to delete the alarm from the NE. The alarm is generated again.
3. Perform a cold reset on the active and standby SCC boards. The alarm persists.
4. Suspect that the SCC board hardware is faulty and replace the SCC board in slot 18. After the board replacement, the alarm persists and the alarm generation time is the initial alarm generation time.
5. Remove both the active and standby SCC boards and then re-insert them respectively. The fault symptom persists.
6. Run the :alm-get-bdalm-new command to query the boards one by one and then determine that the SCC board in slot 118 reports the TEMP_OVER alarm.

Regards,
View more
  • x
  • convention:

chantha
chantha Created Mar 20, 2021 02:37:48 (0) (0)
Thank friend  

Recommended answer

alopez
Created Mar 17, 2021 13:11:11


Hello, dear friend!


Take a look at the following information. I hope it helps you.


TEMP_OVER

Description

Working temperature crossing the threshold. This alarm is generated when the system detects that the board working temperature is higher than the upper threshold or lower than the lower threshold.

Attribute

Alarm Severity

Alarm 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.

NameMeaning

Parameter 1

For packet service processing boards,
  • 0x00: Indicates the lower threshold is exceeded.

  • 0x01: Indicates the upper threshold is exceeded.

For other boards,
  • 0x01: Indicates the upper threshold is exceeded.

  • 0x02: Indicates the lower threshold is exceeded.

Impact on the System

The excessively high or low temperature puts the system in a highly dangerous state. If the system runs in this state for a long period of time, bit errors may be generated and services may be interrupted. Therefore, the TEMP_OVER alarm must be handled in a timely manner.

Fault Symptom

Table 1 lists the fault symptom for the TEMP_OVER alarm.
Table 1 Fault symptom for the TEMP_OVER alarm
Fault SymptomCause
On the NMS, the adjusting mode of the fan board is set to Adjustable Speed Mode and the rotating speed is set to Low Speed or Medium Speed.Cause 1: The set rotating speed of the fan board is excessively low.
The fan board reports the FAN_FAIL or FAN_FAULT alarm.Cause 2: The fan board is faulty.
The adjusting mode of the fan board is set to Auto Speed Mode and the rotating speed is set to High Speed. In addition, no other alarms are generated.Cause 3: The air filter is excessively dusty.
The fan board reports the BD_STATUS alarm.Cause 5: The fan is not in position.

NOTE: If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault according to "Handling Procedure" provided in this topic.

Possible Causes

The possible causes of the TEMP_OVER alarm are as follows:

  • Cause 1: The set rotating speed of the fan board is excessively low.

  • Cause 2: The fan board is faulty.

  • Cause 3: The air filter is excessively dusty.

  • Cause 4: The ambient temperature is excessively high or excessively low due to a cooler or heater equipment fault.

  • Cause 5: The fan is not in position.

  • Cause 6: The board that reports the alarm is faulty.

  • Cause 7: If the alarm is reported on the cross-board, the operation may be irregular. The vents on the cross-board are obstructed, causing the temperature of the board to be too high.

Procedure

  • Query the alarm parameter on the NMS. If the parameter indicates the upper threshold is exceeded, handle the alarm according to causes 1 to 6. If the parameter indicates the lower threshold is exceeded, handle the alarm according to causes 3 and 5.

Cause 1: The set rotating speed of the fan board is excessively low.

  1. Check the adjusting mode and rotating speed of the fan board on the U2000. If the adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or Medium Speed, change the rotating speed to High Speed or the adjusting mode to Auto Speed Mode.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 2.

Cause 2: The fan board is faulty.

  1. If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is generated on the fan board. If it is, handle the alarm immediately.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 3.

Cause 3: The air filter is excessively dusty.

  1. If the alarm persists, check whether the air filter is excessively dusty, causing the problem of heat dissipation. You can feel the wind and the temperature of the wind at the air exhaust vent.

  2. If the problem is caused by dusty the air filter, remove and clean the air filter.

  3. Check whether the alarm is cleared. If the alarm persists, see Cause 4.

Cause 4: The ambient temperature is excessively high or excessively low due to a cooler or heater equipment fault.

  1. Check whether the ambient temperature of the equipment room is higher than 45°C or lower than 0°C. If the temperature is higher than 45°C or lower than 0°C, use a cooler or heater to decrease or increase the ambient temperature.

    NOTE: The TEMP_OVER alarm is cleared when the board temperature is 5°C lower than the upper threshold or 5°C higher than the lower threshold so that intermittent TEMP_OVER alarms can be prevented.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 5.

Cause 5: The fan is not in position.

  1. Check whether the NE reports the BD_STATUS alarm or check whether the fan is in position on the NMS. If the fan is not in position, place it firmly.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 6.

Cause 6: The board that reports the alarm is faulty.

  1. Replace the board that reports the alarm. Refer to Replace the board.

Cause 7: If the alarm is reported on the cross-board, the operation may be irregular. The vents on the cross-board are obstructed, causing the temperature of the board to be too high.

  1. Confirm whether there is a venting block on the cross board that reports the alarm. If it exists, clean the obstruction.

  2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.

If the alarm persists, query the current working temperature of the board reporting the alarm. If the temperature is in the permitted range, adjust the threshold for the working temperature of the board based on the actual equipment room environment. Select the desired board on the NE Explorer. In the navigation tree, choose Configuration > Environment Monitor Configuration > Environment Monitor Interface. On the Temperature Attributes tab, set Temperature Upper Threshold (DEG.C) or Temperature Lower Threshold (DEG.C).

NOTE: The preceding method can be used only to temporarily clear the TEMP_OVER alarm. Exercise caution when using this method because the device lifespan may be affected if the method is used for a long period of time.


Thanks!

View more
  • x
  • convention:

liqiang185
liqiang185 Created Mar 17, 2021 13:26:44 (0) (0)
Good!  
Irina
Irina Created Mar 18, 2021 07:19:55 (0) (0)
Thank you for your solution!  
chantha
chantha Created Jun 7, 2021 05:41:29 (0) (0)
well note  
All Answers
Hello,
We're working on your problem. Please be patient.
View more
  • x
  • convention:

chantha
chantha Created Jun 7, 2021 05:41:35 (0) (0)
 


Hello, dear friend!


Take a look at the following information. I hope it helps you.


TEMP_OVER

Description

Working temperature crossing the threshold. This alarm is generated when the system detects that the board working temperature is higher than the upper threshold or lower than the lower threshold.

Attribute

Alarm Severity

Alarm 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.

NameMeaning

Parameter 1

For packet service processing boards,
  • 0x00: Indicates the lower threshold is exceeded.

  • 0x01: Indicates the upper threshold is exceeded.

For other boards,
  • 0x01: Indicates the upper threshold is exceeded.

  • 0x02: Indicates the lower threshold is exceeded.

Impact on the System

The excessively high or low temperature puts the system in a highly dangerous state. If the system runs in this state for a long period of time, bit errors may be generated and services may be interrupted. Therefore, the TEMP_OVER alarm must be handled in a timely manner.

Fault Symptom

Table 1 lists the fault symptom for the TEMP_OVER alarm.
Table 1 Fault symptom for the TEMP_OVER alarm
Fault SymptomCause
On the NMS, the adjusting mode of the fan board is set to Adjustable Speed Mode and the rotating speed is set to Low Speed or Medium Speed.Cause 1: The set rotating speed of the fan board is excessively low.
The fan board reports the FAN_FAIL or FAN_FAULT alarm.Cause 2: The fan board is faulty.
The adjusting mode of the fan board is set to Auto Speed Mode and the rotating speed is set to High Speed. In addition, no other alarms are generated.Cause 3: The air filter is excessively dusty.
The fan board reports the BD_STATUS alarm.Cause 5: The fan is not in position.

NOTE: If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault according to "Handling Procedure" provided in this topic.

Possible Causes

The possible causes of the TEMP_OVER alarm are as follows:

  • Cause 1: The set rotating speed of the fan board is excessively low.

  • Cause 2: The fan board is faulty.

  • Cause 3: The air filter is excessively dusty.

  • Cause 4: The ambient temperature is excessively high or excessively low due to a cooler or heater equipment fault.

  • Cause 5: The fan is not in position.

  • Cause 6: The board that reports the alarm is faulty.

  • Cause 7: If the alarm is reported on the cross-board, the operation may be irregular. The vents on the cross-board are obstructed, causing the temperature of the board to be too high.

Procedure

  • Query the alarm parameter on the NMS. If the parameter indicates the upper threshold is exceeded, handle the alarm according to causes 1 to 6. If the parameter indicates the lower threshold is exceeded, handle the alarm according to causes 3 and 5.

Cause 1: The set rotating speed of the fan board is excessively low.

  1. Check the adjusting mode and rotating speed of the fan board on the U2000. If the adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or Medium Speed, change the rotating speed to High Speed or the adjusting mode to Auto Speed Mode.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 2.

Cause 2: The fan board is faulty.

  1. If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is generated on the fan board. If it is, handle the alarm immediately.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 3.

Cause 3: The air filter is excessively dusty.

  1. If the alarm persists, check whether the air filter is excessively dusty, causing the problem of heat dissipation. You can feel the wind and the temperature of the wind at the air exhaust vent.

  2. If the problem is caused by dusty the air filter, remove and clean the air filter.

  3. Check whether the alarm is cleared. If the alarm persists, see Cause 4.

Cause 4: The ambient temperature is excessively high or excessively low due to a cooler or heater equipment fault.

  1. Check whether the ambient temperature of the equipment room is higher than 45°C or lower than 0°C. If the temperature is higher than 45°C or lower than 0°C, use a cooler or heater to decrease or increase the ambient temperature.

    NOTE: The TEMP_OVER alarm is cleared when the board temperature is 5°C lower than the upper threshold or 5°C higher than the lower threshold so that intermittent TEMP_OVER alarms can be prevented.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 5.

Cause 5: The fan is not in position.

  1. Check whether the NE reports the BD_STATUS alarm or check whether the fan is in position on the NMS. If the fan is not in position, place it firmly.

  2. Check whether the alarm is cleared. If the alarm persists, see cause 6.

Cause 6: The board that reports the alarm is faulty.

  1. Replace the board that reports the alarm. Refer to Replace the board.

Cause 7: If the alarm is reported on the cross-board, the operation may be irregular. The vents on the cross-board are obstructed, causing the temperature of the board to be too high.

  1. Confirm whether there is a venting block on the cross board that reports the alarm. If it exists, clean the obstruction.

  2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.

If the alarm persists, query the current working temperature of the board reporting the alarm. If the temperature is in the permitted range, adjust the threshold for the working temperature of the board based on the actual equipment room environment. Select the desired board on the NE Explorer. In the navigation tree, choose Configuration > Environment Monitor Configuration > Environment Monitor Interface. On the Temperature Attributes tab, set Temperature Upper Threshold (DEG.C) or Temperature Lower Threshold (DEG.C).

NOTE: The preceding method can be used only to temporarily clear the TEMP_OVER alarm. Exercise caution when using this method because the device lifespan may be affected if the method is used for a long period of time.


Thanks!

View more
  • x
  • convention:

liqiang185
liqiang185 Created Mar 17, 2021 13:26:44 (0) (0)
Good!  
Irina
Irina Created Mar 18, 2021 07:19:55 (0) (0)
Thank you for your solution!  
chantha
chantha Created Jun 7, 2021 05:41:29 (0) (0)
well note  
Hello,

On the NMS, check the COMMUN_FAIL alarm parameter. The parameter is 0x01 0x00 0x03, indicating that inter-board ETH communication fails.
The NE has ever reported the SUBRACK_LOOP alarm and this alarm is cleared one minute later. The SUBRACK_LOOP alarm indicates a loopback on network ports between subracks. A loopback can cause a broadcast storm on the network and block some communication ports.
Remove and then reinsert the AUX board. After the board starts up, the alarm is cleared and is not reported again.

Thanks
View more
  • x
  • convention:

Dear friend!

The possible causes are as follows:
Cause 1: The ambient temperature exceeds the board usage threshold.
Cause 2: The cooling system of the device is damaged. For example, the fan is faulty or blocked by a large amount of dust.
Cause 3: The voltage or current of the device is too high.

Procedure
1. Check whether the ambient temperature is normal. If the ambient temperature is abnormal, improve the ambient temperature of the equipment. In addition, check whether the fan unit works normally. If any exception occurs, rectify the fault in time.
2. If the alarm persists, perform a warm reset on the system control board on the U2000.
3. If the alarm persists, remove the faulty board and re-insert it into the corresponding slot without interrupting services.
4. If the alarm persists, replace the board.

Thanks!

View more
  • x
  • convention:

Hello friend!

Can follow these:

1. Run the :cfg-get-scc-temperature:bid command to query the actual temperature of the board. The query result is 22.3?C, which is within the normal range.
2. Run the alm-del-curdata:num command to delete the alarm from the NE. The alarm is generated again.
3. Perform a cold reset on the active and standby SCC boards. The alarm persists.
4. Suspect that the SCC board hardware is faulty and replace the SCC board in slot 18. After the board replacement, the alarm persists and the alarm generation time is the initial alarm generation time.
5. Remove both the active and standby SCC boards and then re-insert them respectively. The fault symptom persists.
6. Run the :alm-get-bdalm-new command to query the boards one by one and then determine that the SCC board in slot 118 reports the TEMP_OVER alarm.

Regards,
View more
  • x
  • convention:

chantha
chantha Created Mar 20, 2021 02:37:48 (0) (0)
Thank friend  

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.