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

SQUTABM_MM alarm appears on NMS due to inconsistent squelch table generation mode on MSP ring.

Publication Date:  2012-07-25 Views:  41 Downloads:  0
Issue Description
Equipment Type:  OSN3500
Equipment Version: V1R8
Problem was escalated by customer that SQUTABM_MM alarms are appearing on 2 adjacent nodes in one MSP ring. Also customer provided the information that a new OSN-3500 node is added in MSP ring and new node and adjacent node have SQUTABM_MM alarms. 
Alarm Information
SQUTABM_MM
Handling Process
Following steps were performed to handle and resolve this problem.
1- After checking the alarm parameters (0x01 0x00 0xff 0xff 0xff) for SQUTABM_MM, it was found that the alarm is reported on Protection group 1. 
2- SQUTABM_MM alarms were appearing on NE-1469 and NE-1474 while NE-1474 was the new node added in MSP ring. Squelch mode and squelch table generation modes were checked on both NEs by using the following command. 
#9-1469:remote1 [GUJ0723_1469_OSN3500_Shahinabad                                 ][][2011-06-06 21:07:52+08:00]>
:alm-get-curdata:0,0                                                                    CUR-ALM                                                                    
  NUM         BID   EID                   SEVERITY    STATE       START-TIME           END-TIME             PARA1  PARA2  PARA3  PARA4  PARA5  
  741724      13    UP_E1_AIS             MN          start       2010-12-08 15:21:59  None                 0x01   0x00   0x03   0xff   0x01   
  784966      13    UP_E1_AIS             MN          start       2011-04-18 13:44:20  None                 0x01   0x00   0x01   0xff   0x01   
  803342      13    DOWN_E1_AIS           MN          start       2011-06-04 04:06:40  None                 0x01   0x00   0x01   0xff   0x01   
  803591      17    SQUTABM_MM            MN          start       2011-06-04 15:58:27  None                 0x01   0x00   0xff   0xff   0xff   
  Total records :4                                                                          
:cfg-get-squelchmode:1                                 MSSPR-SQUELCH-MODE                               
                          PG-ID  RINGMAP-MODE  SQUTAB-MODE                        
                          1      auto          auto                               
  Total records :1
                                                                
#9-1474:remote1 [NE1474                                                          ][][2011-06-07 18:10:40+05:00]>
:alm-get-curdata:0,0                                                                          CUR-ALM                                                                          
  NUM         BID   EID                               SEVERITY    STATE       START-TIME           END-TIME             PARA1  PARA2  PARA3  PARA4  PARA5  
  75054       18    SQUTABM_MM                        MN          start       2011-06-05 08:36:36  None                 0x01   0x01   0xff   0xff   0xff   
#9-1474:remote1 [NE1474                                                          ][][2011-06-07 18:10:50+05:00]>
:cfg-get-squelchmode:1                                 MSSPR-SQUELCH-MODE                               
                          PG-ID  RINGMAP-MODE  SQUTAB-MODE                        
                          1      auto          manual                             
  Total records :1                                                                
3- After checking squelch mode on both nodes, it was found that SQUTAB MODE at NE-1474 (new node added in MSP ring) was manual and differs from other nodes in MSP ring. 
4- SQUTAB MODE at NE-1474 was modified to "auto" by using the following command. After modification, problem resolved and SQUTABM_MM alarms disappeared from both nodes.
Root Cause
Following are the possible causes for SQUTABM_MM alarm. 
1- New NE added in MSP ring and the squelching mode differs from other nodes in MSP ring.
2- Squelch table generation mode is inconsistent in one MSP ring. 
3- Fiber connection may be faulty during the mode change. 
Suggestions
When these alarms appear on MSP ring, then check the squelch mode and compare with all other nodes in MSP ring. If inconsistent then modify the squelch mode to resolve the problem.

END