User's Manual

260-668066-003 Rev 001 August 2010 3-13
Eclipse Installation Manual
Ring and Mesh Networks
RWPR
TM
(Resilient Wireless Packet Ring) is a fast-switched RSTP link management
protocol for layer 2 switches. RSTP, itself a fast switched evolution of the original STP,
prevents live network loops and provides path redundancy where two or more paths
exist between network nodes.
• RWPR represents a particularly effective enhanced RSTP protocol. When configured
in Eclipse ring networks, reconvergence times are as low as 50 mS.
Link Aggregation 2+0 Protection
Traffic redundancy is supported on co-channel Ethernet links using link aggregation.
If one link fails, then its traffic is recovered on the remaining link or links is shared.
While the reduced bandwidth may result in some traffic loss for low-priority traffic,
appropriate QoS settings should ensure security for all higher priority traffic. This is
often referred to as 2+0 protection.
Super PDH
Super PDH
TM
is exclusive to the Eclipse. It supports protected PDH ring configurations
for capacities to 84xDS1, with traffic switching at the node level.
A ring (closed loop) is formed by east/west facing RAC and RFU combinations from an
Eclipse node; each node is connected to two adjacent nodes, the east and west nodes.
Within the ring there are two traffic rings, one nominated as clockwise, the other
anti-clockwise. Under normal no-fault conditions, all traffic is passed on the clockwise
primary ring.
When a fault occurs, the secondary, anti-clockwise ring, provides the protection
capacity needed. Traffic is looped onto the secondary ring at one side of the break point,
and off at the other side, to bypass the break. This process is called wrapping.
One or more radio paths can be replaced by a fiber span using the DAC 155oM.
Platform Protection
Platform management functions provided by the NCC are protected using the NPC
option to protect essential Backplane Bus and power supply functions.
Bus Protection
• Protects all circuit/tributary traffic. Alarm I/O is not protected.
• Switching is not hitless for an NCC bus clock failure; restoration is within 200 ms,
during which time all traffic on the NTU is affected.
• When the bus clock has switched to NPC control, it will not automatically revert to
NCC control on restoration of the NCC. Return to NCC control requires either
withdrawal/failure of the NPC, or use of diagnostic commands.