ECLIPSE PROTECTION
Company Confidential 1
Eclipse Protection
Protection Options:
• Eclipse Node
• Hot-standby
• Diversity (space, frequency)
• Ring (ring wrapping)
• Dual protection
• DAC
• NCC
• Eclipse Terminal
• Hot-standby, space diversity (on selected terminals)
• Ethernet spanning-tree protocol
• Applies to Eclipse Ethernet traffic where alternate-path protection is
enabled in an Ethernet ring or mesh network using an RSTP switch
2 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
RACs & ODUs are used in pairs to support hot-standby,
space diversity, frequency diversity, or ring protection
Protected links can also be dual-protected whereby a master
protection option protects two subordinate protected links, or
one protected link with one non-protected link
INU supports three non-protected links, or one protected plus
one non-protected link
INUe supports up to three protected links
Equal & unequal loss couplers are available
for single antenna protected operation
3 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
DACs are paired for tributary protection:
• All DACs are protectable except for DAC 4x, DAC 16x, DAC ES
& DAC GE
• For most applications ‘Y’ splitter/combiner trib cable sets are
used
NCC is protected using an NPC
• Protects TDM bus management (clocking)
• Protects the power supply rails
4 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
Link Hot-Standby and Diversity
• Rx switching
• Rx path switching (voting) is hitless (errorless) between two online-
receiving RACs
• A switch of the online Rx bus driving function is not hitless:
- Maximum 200 ms restoration time for an online RAC switch
• Tx switching (hot-standby & space diversity) is not
hitless:
• Less than 200 ms restoration time for an online Tx switch
• Silent Tx switch:
• Restoration time typically less than 5 sec
5 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
Block diagram:
hot-standby or
diversity link protection
6 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
Coupler
• Direct mounting of ODUs
• Mounts directly to antenna
• Standard 3.5 / 3.5 dB splitter
• Optional 1.5 / 6.5 dB coupler
• Used for single-antenna hot-
standby & frequency diversity links
• Also used for 2+0 co-polar
arrangements
7 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
Ring Protection
• Applies to ‘Super PDH’ Nx E1 rings
• Implemented by ‘east-west’ facing RAC/ODU combinations from a
single INU/INUe
• Eclipse manages failure detection & circuit re-routing - no external
equipment required
• Capacities up to 100x E1
• For ‘single gateway’ rings where all traffic on the ring is sourced at
one site, typical maximum ring capacities are 64x E1
8 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
• Primary & Secondary rings:
• Under normal conditions all traffic is transported on the primary
‘clockwise’ ring; the secondary ring is not used
• Under fault conditions, traffic is wrapped onto the secondary ring at one
side of the break, and off at the other side, to bypass the break; circuits
are ‘ring-wrapped’
• Ring wrapping & unwrapping is not hitless
• Wrapping: typically less than 100 ms restoration (traffic interruption) time
• Unwrapping: revertive switch command is initiated on expiry of an error-
free timer, and optional time-of-day timer. Traffic interruption on
restoration is not more than 100 ms.
9 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
– Ring Mechanism
•Simple & Fast
•Local Decision
•Nodes Adjacent to Failure loop
(wrap) the traffic
PDH Ring
10 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Super PDH Rings
Gateway
Ring not broken
11 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Super PDH Rings
Gateway
Ring broken
12 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Ring Capacity: Gateway or Any-to-Any Rings
Applies to Eclipse ring-wrap protection
• Gateway Ring
• A gateway ring has all traffic sourced/sunk at one ‘head office’ site
• Eclipse backplane capacity limits ring traffic to 64x E1
• Any-to-Any Ring
• An any-to-any ring supports multiple network connections (multiple
gateways) between two or more sites
• Can support ring traffic up to 100x E1
• Most rings are ‘Gateway’
13 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Ring Capacity: Gateway or Any-to-Any Rings
Contd
Ring capacity limits are determined by:
• Eclipse backplane bus maximum of 100x E1
• Eclipse radio path maximum of 100x E1 (RAC 30)
• Backplane usage equates to the number of circuits on the
ring plus half the number of drop-insert circuits. The total
must not exceed 100. This is captured in the formula
R + d/2 = / < 100, where R is the number of circuits on
the ring, and d the number of drop-insert circuits.
14 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Ring Protection Backplane Capacity Calculation
15 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
Ethernet Network RSTP Protection Options
• RSTP-capable switches provide the mechanism to prevent Ethernet loops.
Contesting paths are forced into either a forwarding or blocked state by the
spanning tree protocol. In the event a path (link) fails the protocol switches
the blocked path (redundant path) to forwarding.
• For ring networks using DAC ES an external RSTP switch is required (Layer
2 switch with RSTP capability)
• For ring networks based on the DAC GE external RSTP switches are not
required; DAC GE includes an enhanced RSTP function (RWPR).
16 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
DAC protection
• Trib protection is available for all E3, DAC16x V2 & STM1 DACs
• When a switch occurs, all tribs either Tx or RX or Tx & Rx,
depending on the failure mode & DAC type, are switched together
• The primary DAC is default online for Rx and Tx
• Protection switching is not hitless: maximum 200ms restoration time
17 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
DAC protection contd
• Two protection configurations: tributary protection, & always-on:
• Tributary Protection
• Y cables connect the paired DACs to customer equipment
• In the Rx direction (from the customer) both DACs receive data, but
only the online Rx DAC sends this data to the TDM bus
• In the Tx direction, the online Tx DAC sends data to the customer,
the other mutes its Tx line interface
• Tributary Always On
• Separate cables connect each DAC to customer equipment
• In the Rx direction (from the customer) both DACs receive data, but
only the online Rx DAC sends this data to the TDM bus
• In the transmit direction both DACs send data to customer
equipment, & the customer equipment switches between these two
always on tributaries
18 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
NCC Protection
• NPC plug-in provides protection for NCC TDM bus management
(bus clock) & power supply functions
• Bus protection protects all tributary & auxiliary traffic; Alarm I/O
is not protected
• Switching is not hitless for a TDM bus clock failure. Restoration
occurs within 200ms, during which time all traffic on the node is
affected.
• Protection is hitless for a power supply failure. If the NCC
converter or one of its supply rails fails, the NPC will take over
without interruption, & vice versa.
19 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Node Protection
Contd
Dual Protection
• Two protected subordinate links are in turn protected by a
higher, master protection option:
• RACs (RAC 30 or RAC 3X) must be located in the same INUe
• Except for Space Diversity pairings where two vertically separated
antennas are required, a single dual-polarized antenna can be used
• Dual protection options are:
• Frequency diversity over hot-standby
• Frequency diversity over space diversity
20 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Terminal Protection
• Paired IDUs & ODUs
Protectable Protection Switching
• Tribs connected with “Y” or IDUs
straight cables IDU 20x Hot-standby Not hitless
• Equal or unequal couplers for IDU 300 8x Hot-standby Not hitless
single antenna operation
IDU 300 20x Hot-standby Not hitless
• Tx and Rx switched separately
IDUsp 16x Hot-standby Not hitless
• Protection applies only to the
IDU 300 20xV2 Hot-standby Rx hitless
payload; auxiliary data is not Space diversity Tx not hitless
protected IDU 155o Hot-standby Rx hitless
• Alarm I/O actions can be protected Space diversity Tx not hitless
– application dependent
21 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Terminal Protection: PDH
A protected PDH terminal comprises two IDUs with companion ODUs, and
inter-connecting RJ-45 protection & NMS cables
Y cables are used for trib split/merge
22 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Terminal Protection: SDH
Protected IDU 155o terminals require inter-connecting RJ-45 protection & NMS
cables
Optical Y cables are used for trib split/merge
23 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Terminal Protection: Ethernet
The IDU ES cannot be paired to provide protection for its
Ethernet data or E1 waysides
The IDU GE can be paired to provide protection
for its Ethernet data or E1 waysides
• Protected 1+1 hot-standby or space diversity
operation is configured by adding a second IDU
GE 20x. Ethernet traffic is supported on a single
interface to one of the IDUs.
• E1/DS1 traffic is supported on interfaces to both
IDUs using Y-cables.
24 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
Eclipse Terminal: Protection Switching
Restoration Times for IDUs:
• IDU Transmit Switch:
• Within 200 ms for IDUsp 16x, IDU 300 8x, IDU 300 20x,
IDU 300 20xV2 and IDU 155o
• Within 500 ms for IDU 20x
• Within 5 seconds for a silent Tx switch
• IDU Receive Switch:
• IDU 300 20xV2 & IDU 155o
- Hitless (errorless) on Rx path failure
- Within 200 ms for an online Rx switch
• Other IDUs except IDU 20x:
•- Within 200 ms for an Rx software load, LIU or trib output failures
(IDU 20x is within 500 ms)
•- Within 1.2 sec for an Rx path failure
25 AVIAT NETWORKS | JANUARY 28, 2010 Company Confidential
