No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Frequently Reset of EGS2 Board due to Version Inconsistency Issue in OptiX OSN 3500

Publication Date:  2012-07-25 Views:  32 Downloads:  0
Issue Description
Problem reported by customer that on OptiX OSN 3500 NE Ethernet board SSN2EGS2 frequently reset and alarm BD_STATUS and COMMUN_FAIL reported on Transmission NMS T2000 end for only 20 seconds and after that board normal. According to the information provided by the customer that services are continuously fluctuating. That SSN2EGS2 frequently reset when we insert it in same SDH another slot.




Alarm Information
Frequently on random period of time BD_STATUS alarm comes on SSN2EGS2 board for only 15-20 second and service interrupted during this time. Means SSN2EGS2 board partially cold reset. This was due to version inconsistency of SSN2EGS2 in installed NG-SDH GSCC or due to when the sum of the traffic on GE1 and the traffic on GE2 occupies all the 24 VC-3s, the EGS2 board may undergo cold resets repeatedly or the services may be interrupted for a long time.






                                    Figure 1

Alarms information during board reseting.

  Severity   Alarm Name   Monitored Object   Rising Time   Cleared Time   Alarm Type   Node Type   Affiliated Subnet   Alarm Parameters(hex)    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 11:35:16   2012-04-03 11:35:40   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 11:35:11   2012-04-03 11:35:16   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 09:36:10   2012-04-03 09:36:38   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 09:36:05   2012-04-03 09:36:10   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    
  Critical   ETH_LOS   265-SHAH LATIF-13-N2EGS2-2(PORT-2)-MAC:1   2012-04-03 09:28:59   2012-04-03 09:29:06   Communication   OptiX OSN 3500   -    0x02 0x00 0x01 0xff 0xff    
  Critical   ETH_LOS   265-SHAH LATIF-13-N2EGS2-1(PORT-1)-MAC:1   2012-04-03 09:28:50   2012-04-03 09:28:59   Communication   OptiX OSN 3500   -    0x01 0x00 0x01 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 09:27:46   2012-04-03 09:28:16   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Critical   ETH_LOS   265-SHAH LATIF-13-N2EGS2-1(PORT-1)-MAC:1   2012-04-03 09:20:23   2012-04-03 09:20:27   Communication   OptiX OSN 3500   -    0x01 0x00 0x01 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 09:19:46   2012-04-03 09:19:51   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 09:19:22   2012-04-03 09:19:39   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 07:13:48   2012-04-03 07:14:16   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 07:13:43   2012-04-03 07:13:48   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    
  Critical   ETH_LOS   265-SHAH LATIF-13-N2EGS2-1(PORT-1)-MAC:1   2012-04-03 05:25:06   2012-04-03 05:25:11   Communication   OptiX OSN 3500   -    0x01 0x00 0x01 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 05:24:04   2012-04-03 05:24:33   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 03:04:52   2012-04-03 03:05:21   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    
  Critical   ETH_LOS   265-SHAH LATIF-13-N2EGS2-1(PORT-1)-MAC:1   2012-04-03 01:03:24   2012-04-03 01:03:32   Communication   OptiX OSN 3500   -    0x01 0x00 0x01 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 01:02:22   2012-04-03 01:02:52   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-03 00:53:56   2012-04-03 00:54:26   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-02 22:49:46   2012-04-02 22:50:15   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-02 20:45:36   2012-04-02 20:46:06   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Major   BD_STATUS   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-02 20:37:01   2012-04-02 20:37:30   Equipment   OptiX OSN 3500   -    0xff 0xff 0xff 0xff 0xff    
  Critical   ETH_LOS   265-SHAH LATIF-13-N2EGS2-1(PORT-1)-MAC:1   2012-04-02 19:23:38   2012-04-02 19:23:47   Communication   OptiX OSN 3500   -    0x01 0x00 0x01 0xff 0xff    
  Major   COMMUN_FAIL   265-SHAH LATIF-13-N2EGS2-OTHER   2012-04-02 18:16:47   2012-04-02 18:17:18   Equipment   OptiX OSN 3500   -    0x01 0x00 0x03 0xff 0xff    


Handling Process
  1. You can’t upgrade installed SSN2EGS2 version in installed SDH slot because BD_STATUS and COMM_FAIL continuously reporting and software loading will be failed.
  2. Installed new upgraded version of SSN2EGS2 in same slot but its version should be matched with installed GSCC.
  3. Or Plug out the SSN2EGS2 from SDH install it in free sub rack SDH and upgrade the version of SSN2EGS2 according to installed GSCC version i.e 5.21.18.50 in above case.
  4. According version table 5.21.18.50 the version of SSN2EGS2 according version table, which is same after upgrading the EGS2 board.
      SSN2EGS2 \ \ VER.E
    VER.F
    BDSOFT \ SSN2EGS201,SSNEGS206,Board Software,Program  05025912 5.32
    FPGA \ SSSN1EGS201,SSNEGS201,FPGA Logic,FPGA         05026242   (U5)310    
    FPGA \ SSN1EGS201,SSNEGS205,PL215 Ethernet VC12/VC3 Mapper Logic,Logic  05026527   (U41)210                                                                                                                        (U42)210 
    BIOS \ SSN1EGS201, SSNEGS204,Board BIOS,BIOS 05026473 2.14/2.19
    EXTBIOS \ SSN1EFT801,SSNEFT803,Board Extended BIOS,BIOS 05026257 2.34



Root Cause
Frequently BD_STATUS and COMM_FAIL alarm report on SSN2EGS2 for a very short time and services was interrupted. This issue occurs when new more services made on SSN2EGS2 for MSAN and after that board reseting automatically frequently. This is was due to miss match of SSN2EGS2 with installed GSCC in SDH.

Use the command to find version of SSN2EGS2 
:cfg-get-bdverinfo:5
BOARD-VER-INFO
PCB      Version : SSN2EGS2 VER.F
BIOS     Version : 2.14
ExtBIOS  Version : 2.34
Software Version : 5.12
Logic    Version : (U5)310(U41)211(U42)211
 
Use the command to find version of GSCC-         
:sftm-get-nesoftver:18
                               VERSION-INFORMATION                               
                  NESOFTNAME  VER               DATE      STATE                  
                  NSF1        5.21.18.50        20090425  active                 
                  NSF2        5.21.18.50        20090425  inactive               
                  INI1        5.21.18.50        20090123  active                 
                  INI2        5.21.18.50        20090123  inactive               
                  BIOS        08.09.45          20060106  inactive               
                  ExtBIOS     09.09.69          20081113  active                 
                  PCB         VER.B                                              
                  Logic       (U2)310                                            
  Total records :8
 
Installed SSN2EGS2 version doesn’t match with GSCC according to version matching table.

Suggestions
For permanent solution upgrade NE software version V100R008C02SPC500 (5.21.18.55) or version of all boards should be consistent with installed GSCC in SDH.




END