NE_POWER_OVER alarm on OSN 3500 due to limitation in software version 5.21.18.12
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.Following steps were taken to resolve the issue:
- 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.
- Then we login the NE by OptiX navigator software & run the following command:
:cfg-get-powerinfoPOWER-INFOBID LOG-BDYPE ACTIVE-STATE LOG-POWER PHY-BDYPE PHY-POWER1 ssn2pq1 active 13 ssn2pq1 132 bdtype null 0000 0 bdtype null 03 bdtype null 0000 0 ssn2egs2 434 bdtype null 0000 0 ssn2egs2 435 ssn3sl16 active 22 ssn3sl16 226 ssn3egs4 active 70 ssn3egs4 707 ssn3sl16 active 22 ssn3sl16 228 ssn1sl64 active 30 ssn1sl64 309 ssn1uxcsb active 65 ssn1uxcsb 6510 ssn1uxcsb active 65 ssn1uxcsb 6511 ssn1sl64 active 30 ssn1sl64 3012 bdtype null 0000 0 ssn1slq16 013 ssn2egs2 active 43 ssn2egs2 4314 ssn2egs2 active 43 ssn2egs2 4315 ssn2egs2 active 43 ssn2egs2 4316 ssn2egs2 active 43 ssn2egs2 4317 bdtype null 0000 0 bdtype null 018 gscc active 16 gscc 1619 bdtype null 0000 0 bdtype null 020 bdtype null 0000 0 bdtype null 021 bdtype null 0000 0 bdtype null 022 bdtype null 0000 0 bdtype null 023 bdtype null 0000 0 bdtype null 024 bdtype null 0000 0 bdtype null 025 bdtype null 0000 0 bdtype null 026 bdtype null 0000 0 bdtype null 027 piu active 0 piu 028 piu active 0 piu 029 bdtype null 0000 0 bdtype null 030 bdtype null 0000 0 bdtype null 031 bdtype null 0000 0 bdtype null 032 bdtype null 0000 0 bdtype null 033 bdtype null 0000 0 bdtype null 034 bdtype null 0000 0 bdtype null 035 bdtype null 0000 0 bdtype null 036 bdtype null 0000 0 bdtype null 037 ssn1aux active 19 ssn1aux 1938 ssn1fan active 16 ssn1fan 1639 ssn1fan active 16 ssn1fan 1640 ssn1fan active 16 ssn1fan 1650 bdtype null 0000 0 bdtype null 051 bdtype null 0000 0 bdtype null 052 bdtype null 0000 0 bdtype null 053 bdtype null 0000 0 bdtype null 054 bdtype null 0000 0 bdtype null 055 bdtype null 0000 0 bdtype null 056 bdtype null 0000 0 bdtype null 057 bdtype null 0000 0 bdtype null 058 bdtype null 0000 0 bdtype null 059 bdtype null 0000 0 bdtype null 060 bdtype null 0000 0 bdtype null 061 bdtype null 0000 0 bdtype null 062 bdtype null 0000 0 bdtype null 063 bdtype null 0000 0 bdtype null 064 bdtype null 0000 0 bdtype null 065 bdtype null 0000 0 bdtype null 066 bdtype null 0000 0 bdtype null 067 bdtype null 0000 0 bdtype null 068 bdtype null 0000 0 bdtype null 069 bdtype null 0000 0 bdtype null 070 bdtype null 0000 0 bdtype null 071 bdtype null 0000 0 bdtype null 072 bdtype null 0000 0 bdtype null 073 bdtype null 0000 0 bdtype null 074 bdtype null 0000 0 bdtype null 075 bdtype null 0000 0 bdtype null 076 bdtype null 0000 0 bdtype null 077 bdtype null 0000 0 bdtype null 078 bdtype null 0000 0 bdtype null 079 bdtype null 0000 0 bdtype null 080 bdtype null 0000 0 bdtype null 081 bdtype null 0000 0 bdtype null 082 bdtype null 0000 0 bdtype null 083 bdtype null 0000 0 bdtype null 084 bdtype null 0000 0 bdtype null 085 bdtype null 0000 0 bdtype null 086 bdtype null 0000 0 bdtype null 087 bdtype null 0000 0 bdtype null 088 bdtype null 0000 0 bdtype null 089 bdtype null 0000 0 bdtype null 090 bdtype null 0000 0 bdtype null 0101 bdtype null 0000 0 bdtype null 0102 bdtype null 0000 0 bdtype null 0103 bdtype null 0000 0 bdtype null 0254 bdtype null 0xff 572 bdtype null 658255 bdtype null 0xff 600 bdtype null 550Total records :864. 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 outage5. 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.559. 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
The version 5.21.18.12 doesnot support high power.Upgrade the node to 5.21.18.55 resolved the issue of enabling high power on the nodeAlways keep all the nodes upgraded to the latest maintenance version so that such type of issue don’t occur.
Thunder-link.com, a leading huawei optical transmission equipment supplier, we are dedicated and professional at Huawei optical products, if you have any problem during your operation, please sign in to our blog, www.thunder-link.com/blog; or you have any requirement please come to visit www.thunder-link.com; or just email for inquire: sales@thunder-link.com.
Comments are closed