Hello, everyone!
This post will tell you one issue for NE_POWER_OVER alarm on OSN 3500 due to limitation in software version 5.21.18.12.
Problem description:
Problem is reported by customer that they are facing service interruption on already running ethernet services on OSN 3500 after installing of new boards in the NE.
Handling procedure:
Following steps were taken to resolve the issue:
1.First the all the alarms on the NE are checked. It is found that NE_POWER_OVER alarms appeared on the NE after addition of new boards.
2.Then we login the NE by OptiX navigator software & run the following command:
:cfg-get-powerinfo
POWER-INFO
BID LOG-BDYPE ACTIVE-STATE LOG-POWER PHY-BDYPE PHY-POWER
1 ssn2pq1 active 13 ssn2pq1 13
2 bdtype null 0000 0 bdtype null 0
3 bdtype null 0000 0 ssn2egs2 43
4 bdtype null 0000 0 ssn2egs2 43
5 ssn3sl16 active 22 ssn3sl16 22
6 ssn3egs4 active 70 ssn3egs4 70
7 ssn3sl16 active 22 ssn3sl16 22
8 ssn1sl64 active 30 ssn1sl64 30
9 ssn1uxcsb active 65 ssn1uxcsb 65
10 ssn1uxcsb active 65 ssn1uxcsb 65
11 ssn1sl64 active 30 ssn1sl64 30
12 bdtype null 0000 0 ssn1slq16 0
13 ssn2egs2 active 43 ssn2egs2 43
14 ssn2egs2 active 43 ssn2egs2 43
15 ssn2egs2 active 43 ssn2egs2 43
16 ssn2egs2 active 43 ssn2egs2 43
17 bdtype null 0000 0 bdtype null 0
18 gscc active 16 gscc 16
19 bdtype null 0000 0 bdtype null 0
20 bdtype null 0000 0 bdtype null 0
21 bdtype null 0000 0 bdtype null 0
22 bdtype null 0000 0 bdtype null 0
23 bdtype null 0000 0 bdtype null 0
24 bdtype null 0000 0 bdtype null 0
25 bdtype null 0000 0 bdtype null 0
26 bdtype null 0000 0 bdtype null 0
27 piu active 0 piu 0
28 piu active 0 piu 0
29 bdtype null 0000 0 bdtype null 0
30 bdtype null 0000 0 bdtype null 0
31 bdtype null 0000 0 bdtype null 0
32 bdtype null 0000 0 bdtype null 0
33 bdtype null 0000 0 bdtype null 0
34 bdtype null 0000 0 bdtype null 0
35 bdtype null 0000 0 bdtype null 0
36 bdtype null 0000 0 bdtype null 0
37 ssn1aux active 19 ssn1aux 19
38 ssn1fan active 16 ssn1fan 16
39 ssn1fan active 16 ssn1fan 16
40 ssn1fan active 16 ssn1fan 16
50 bdtype null 0000 0 bdtype null 0
51 bdtype null 0000 0 bdtype null 0
52 bdtype null 0000 0 bdtype null 0
53 bdtype null 0000 0 bdtype null 0
54 bdtype null 0000 0 bdtype null 0
55 bdtype null 0000 0 bdtype null 0
56 bdtype null 0000 0 bdtype null 0
57 bdtype null 0000 0 bdtype null 0
58 bdtype null 0000 0 bdtype null 0
59 bdtype null 0000 0 bdtype null 0
60 bdtype null 0000 0 bdtype null 0
61 bdtype null 0000 0 bdtype null 0
62 bdtype null 0000 0 bdtype null 0
63 bdtype null 0000 0 bdtype null 0
64 bdtype null 0000 0 bdtype null 0
65 bdtype null 0000 0 bdtype null 0
66 bdtype null 0000 0 bdtype null 0
67 bdtype null 0000 0 bdtype null 0
68 bdtype null 0000 0 bdtype null 0
69 bdtype null 0000 0 bdtype null 0
70 bdtype null 0000 0 bdtype null 0
71 bdtype null 0000 0 bdtype null 0
72 bdtype null 0000 0 bdtype null 0
73 bdtype null 0000 0 bdtype null 0
74 bdtype null 0000 0 bdtype null 0
75 bdtype null 0000 0 bdtype null 0
76 bdtype null 0000 0 bdtype null 0
77 bdtype null 0000 0 bdtype null 0
78 bdtype null 0000 0 bdtype null 0
79 bdtype null 0000 0 bdtype null 0
80 bdtype null 0000 0 bdtype null 0
81 bdtype null 0000 0 bdtype null 0
82 bdtype null 0000 0 bdtype null 0
83 bdtype null 0000 0 bdtype null 0
84 bdtype null 0000 0 bdtype null 0
85 bdtype null 0000 0 bdtype null 0
86 bdtype null 0000 0 bdtype null 0
87 bdtype null 0000 0 bdtype null 0
88 bdtype null 0000 0 bdtype null 0
89 bdtype null 0000 0 bdtype null 0
90 bdtype null 0000 0 bdtype null 0
101 bdtype null 0000 0 bdtype null 0
102 bdtype null 0000 0 bdtype null 0
103 bdtype null 0000 0 bdtype null 0
254 bdtype null 0xff 572 bdtype null 658
255 bdtype null 0xff 600 bdtype null 550
Total records :86
4. We see that the Physical power of the boards is 658 which is exceeding the threshold of 550, hence the NE_POWER_OVER alarm & abonormal behaviour of other boards causing outage
5. We immediately plugout the unused boards to reduce the power consumption. After plugout unnecessary & unused boards, the service gets restored by still we have NE_POWER_OVER alarms as physical power consumption is 559 against the threshold of 550.
6. We then run the command :cfg-set-hpenable:enable; but we are unable to run the command.
7. We check the version of the node & find it to be 5.21.18.12.
8. We then check the release documentation & different pre-cautions & found that this version doesnot support high power. To enable high power we need to upgrade to the latest maintenance version of V1R8 5.21.18.55
9. We then upgrade the node to 5.21.18.55 & check the :cfg-get-powerinfo comand. In its output we see that the physical power threshold has been increased to 1050 & the NE_POWER_OVER alarm is cleared.
Root cause:
The version 5.21.18.12 doesnot support high power.
Solution:
Upgrade the node to 5.21.18.55 resolved the issue of enabling high power on the node.
That's all, I welcome everyone to leave a message and exchange in the comment area!
Thank you！
