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

How to insert a M500 into a M1000-M3000 STM-1 SNCP ring

Publication Date:  2012-07-24 Views:  53 Downloads:  0
Issue Description

Customer has an sncp ring with M1000. Then customer inserted a second equipment in the protection system, a M500, but he got the message: `"not integrity snc"
in the field "Source protected subnet" inside SDH Service Configuration. Customer needs to know whether this is a normal message or it is a problem.

Alarm Information
      NULL
Handling Process
1-Modify involved NEs (in this case M3000 e M1000) to Pre-Configuration (Right click on NE and select Attribute). 
2-Delete fiber where NE M500 will be inserted (Topology->Fiber/Cable Management).  At this moment, protection and trails will be erased from T2000.
3- Desconect fibers between M3000 and M1000 and make the new links inserting M500. In case of service running through this fiber, it will be switched. 
4- Create new  NE (M500)
5-Create new fibers
6-Create the protection again (Protection View: Protection Subnet->Create->PP(Uniform Route). M3000 and M1000 as SNC node. And M500 as PP node.
7-Create pass-through services in the new NE (Configuration: SDH Configuration->SDH Service Configuration, Direction: Bidirectional)
8-Update trail database (Trail View: Trail->Trail Search)
9-Modify involved NEs attributes, removing  pre-configuration setting (Right click on NE and select Attribute) of M3000 and M1000   

 

Root Cause

We had followed a procedure to test M500 NE insertion into a ring formed by M1000 and M3000 NE's. After the insertion, M1000 and M3000 were set as SNC node,
while M500 was set as PP node. Now service in the customer is running OK.
                          M500  VERSION INFORMATION                              
                  NESOFTNAME  VER               DATE      STATE                  
                  NSF1        5240420           20050707    active                  
                  NSF2        5240420           20050707    inactive                
                  BIOS        8.02.06           20040302      inactive                
                  ExtBIOS     9.02.03           20050617   inactive                
                  Logic       (U201)220                           active

Suggestions
            NULL

END