This post will share how to convert between common E1 services and E1 SNCP services.
Scenario Description
The network topology consists of four OptiX OSN 3500 and one virtual NE.
Carries two common E1 services.
Video
This video will show how to convert between common E1 services and E1 SNCP services， and how to implement conversion on virtual NEs after topology changes.
Text description
Converting common E1 services to E1 SNCP services
1. Confirm the existing E1 services.
2. Configure dual-fed and selective receiving on NE1.
A. Expanding bidirectional services into unidirectional services
B. Convert the unidirectional service whose signal source is a line board and whose signal sink is a tributary board to an SNCP service. The two services need to be configured separately.
C. Create the unidirectional service in the reverse direction by referring to the generated protection service. The two services can be configured at the same time.
3. Configure two bidirectional pass-throughs on NE3.
4. Configure the dual-fed and selective receiving service on NE4.
A. Expand bidirectional services as unidirectional services.
B. For the services forwarded to the virtual NE, convert the unidirectional services whose signal source is a dual-fed line board and whose signal sink is a selective-receiving line board into SNCP services. For the services dropped locally, select the unidirectional service whose signal source is a line board and the signal sink is a tributary board to convert the services to SNCP services.
C. Configure unidirectional services in the reverse direction according to the generated protection services.
5. Search for new SDH trails.
Searching for new SDH trails = Refreshing SDH trails
Results:
Please note:
1. On NE1 and NE4, the signal source is dual-transmit end and the signal sink is selective receive end, and the unidirectional service is converted into SNCP services. If the selection is incorrect, the conversion fails.
2. During the configuration, the timeslots occupied by the E1 services in each place must be correct. Otherwise, E1 SNCP trails cannot be searched out in the last step.
Converting E1 SNCP services to common E1 services
1. Operations on NE1
A. Expand a bidirectional path into a unidirectional path.
B. Restore the SNCP service to an unprotected service. When you select a unidirectional working service, the protection service is automatically selected.
Another simpler method is to select the protection service between, right-click, and choose Convert to Non-Protection Service from the shortcut menu. This does not require step A.
C. Delete unnecessary unidirectional services.
2. Delete the pass-through service from NE3.
3. On NE4, convert the SNCP service to the non-protection service. The operation method is the same as that of step 1.
4. Search for SDH trails again.
Service conversion on virtual NE
After NE6 is added to the topology, the virtual NE service can be used as the node of the SNCP service. Therefore, the first E1 service can be converted again. When two SNCP nodes are at both ends of an E1 path, the protection capability is the best.
1. Configure services on NE1, NE3, and NE6.
The configuration method is the same as above.
2. Configure SNCP services for virtual NEs.
Common E1 services cannot be converted to SNCP E1 services on virtual NEs.
Solution:
A. In the NE Explorer of the virtual NE, delete the original E1 service,
B. Create an SNCP service. The working timeslot must be the same as the deleted timeslot.
After the configuration is complete, the unidirectional service in the reverse direction is automatically created. It no needs to manually create the service again.
3. Search for SDH trails again.
Results:
Please note:
1. When converting an E1 SNCP service to a common E1 service, it needs to delete the entire E1 SNCP service on the virtual NE and then create the common E1 service.
2. Creating, deleting, or modifying services on virtual NEs does not affect services.
