Professional Documents
Culture Documents
SDH Protection
OMS 1410 offers a range of different PDH and SDH protection schemes: Service Module Equipment Protection 1+1 Multiplex Section Protection (MSP) 1+1 Linear MSP Sub Network Connection Protection SNCP
The 1+1 MSP functionality is in accordance with ITU-T G.841, Clause 7.1. The following parameters are configurable on an MSP object: Enabled/disabled Mode, unidirectional or bidirectional Operation Type, revertive or non-revertive WTR (Wait to Restore) time, configurable from 0-15 minutes, default 5 minutes
The protocol used for K1 and K2 (b1-b5) is defined in ITU-T G.841, Clause 7.1.4.5.1. The protocol used is 1+1 bidirectional switching, compatible with 1:n bidirectional switching.
1.2 MSP
The MSP function provides protection for the STM-n signal against channel associated failures within a multiplex section. All possible options specified for the Multiplex Section Protection (MSP) Protocol (bytes K1 and K2), as defined in ITUT/G.783, are used. The following criteria may be used at the receive end for switching to the protection path: Signal Fail (SF) (LOS, LOF, MS-AIS or MS-EXC) at section level Signal Degrade (SD) - USE (Default) - CDEG - BER (DEG - that is, bit error rate exceeds a pre-set threshold in the range of 10-5 to 10-9) Command from the LCT or from the network management system
1.3 SNCP
OMS 1410 supports two types of SNCP: SNC/I (Sub Network Connection Protection with Inherent monitoring) and SNC/N (Sub Network Connection Protection with Non-intrusive monitoring) SNCP is supported for the following layers: VC-12 VC-3 VC-4 VC-4-4c The SNCP functionality is in accordance with ITU-T G.841 Clause 8. The following parameters are configurable on an SNCP object: Enabled/disabled Operation Type, revertive or non-revertive Hold-off time, configurable from 0-10s in 100ms steps, default 0s WTR time, configurable from 0-15minutes, default 5 minutes The application architecture supported is 1+1 unidirectional switching according to ITU-T G.841 Clause 8.3.2. The switch initiation criteria are implemented as described in ITU-T G.841 Clause 8.4. The protection algorithm is implemented according to ITU-T G.841 Clause 8.6. It is possible to switch up to 504 (such as 2 x STM-4 structured in VC-12) SNCP instances within 50 ms. A larger number of SNCP instances may be configured, but in that case the switching time may exceed 50ms.
2. Ethernet Protection
OMS 1410 supports following Ethernet protection technologies in this release: Spanning Tree Protocol including RSTP and MSTP Link Aggregation including LACP Ethernet Ring protection based on ITU-T G.8032v2.
nodes to promote and demote assigned LAG links to and from traffic carrying activity in a controlled, synchronized manner, according to each links configuration and status. Dynamic Layer 2 Link Aggregation, that is, allows configuration of link aggregation validation parameters for each link in a LAG. LACPs are then used to dynamically create/delete valid LAG constructs and dynamically assign valid links to LAGs or even switch links between different LAGs based on the configured parameters.
OMS 1410 at Release 1.0 manual platform link aggregation and manual Layer 2 Link Aggregation by L2 LACP protocol support.
The OMS 1410 architecture supports service modules that provide Ethernet ports. All of these are LAN native Ethernet Ports. The Ethernet-over-SDH service capability of mapper service modules uses generic GFP and VCAT functionality to deliver Ethernet transport over SDH VCGs. These functions provide specializations of logical Ethernet ports and are WAN Ports. OMS 1410 nodes can support both LAN and WAN LAGs, however a mix of LAN and WAN ports is not allowed in the same LAG. LAG constructs can be configured from link ports across different service modules. The Link Aggregation system can support up to 60 LAGs, using up to 120 link ports. However, any one LAG instance may support up to eight member ports.
Protecting Module 5 6
A protection switch may occur based on a module failure or an activated command from the operator. In case of a switch request based on a module fail, the switching time is less than 50ms. The switching criteria and the priority levels are outlined in the following table. Table 2: Switch Request and Priority Switch Request/State Order Of Priority 1 Clear 2 Forced switch 3 Module fail 4 Manual switch The different switch requests and switch states have the following implementation:
3.1 Clear
This command clears all the externally initiated commands listed in the table above.