eclipse connect es - Описание.pdf

Corporate Headquarters

Stratex Networks

120 Rose Orchard Way

San Jose, CA 95134

Telephone: +1.408.943.0777

Facsimile: +1.408.944.1648/9

North America

[email protected]

Latin America

[email protected]

Asia Pacific

[email protected]

Europe

[email protected]

Middle East and Africa

[email protected]

Sub-Saharan Africa

[email protected]

www.stratexnet.com

Product Description

Eclipse Connect ES ETSI

Introduction

Eclipse Connect ES is a wireless link for Ethernet. It supports Fast Ethernet to 200 Mbps with up to 8xE1 wayside circuits to provide an uncomplicated and cost effective alternative to fiber.

Connect ES is packaged as a link, with each terminal comprising an Indoor Unit (IDU ES) and Outdoor Unit (ODU 300), with options for a direct-mount parabolic antennas ranging in diameter from 0.3 m to 1.8 m.

Connect ES terminals include a Layer 2 switch to support four customer 10/100base-T ports, two over-air transport channels and comprehensive VLAN and QoS options.

Channel bandwidths are selectable through a range of modulation options, from QPSK to 128 QAM, to support operator selection of radio system performance.

Connect ES may be used in single-link and networked applications, and can be over-air interfaced to Eclipse Node comprising the INU, DAC ES, DAC 4x/16x and ODU 300. It is also fully supported by Portal, the Eclipse craft tool, and by ProVision, Stratex Networks’ network management system.

Figure. Eclipse Connect ES Terminal Comprising IDU ES, ODU 300 and Antenna

EclipseConnectES_ PD_ ETSI_A4_ Oct05 of 26

Product Description

Connect ES Capacity and Bandwidth Options Eclipse Connect ES is a 1+0 link package comprising two terminals with an Ethernet base capacity of 50 Mbps and up to 8xE1 wayside circuits. This is the Connect 50.

Connect 50 may be user-configured to support lower throughputs on narrower channel bandwidths with options of Connect 20, Connect 30 and Connect 40, for throughputs to 20, 30 and 40 Mbps respectively.

For higher throughputs the Connect ES options are Connect 100, Connect 150 and Connect 200, for throughputs to 100, 150 and 200 Mbps respectively. These higher capacities use the same base Connect 50 platform, with access to the higher capacities provided by an additional software-keyed license.

The maximum data throughput for each Connect ES option may be assigned to Ethernet traffic, or split between Ethernet and wayside E1 circuits. Where available link capacity is fully assigned to Ethernet, Ethernet throughput is reduced by 2 Mbps (2.048 Mbps) for each E1 assigned, up to a maximum 8xE1 circuits.

Figure 1 illustrates Connect ES capacity and channel bandwidth options.

Figure 2. Connect ES Capacity and Bandwidth Options


Product Description

Table 1 shows available Ethernet data throughput with and without E1 wayside circuits, for configurations with 4 or 8 waysides. Waysides can be configured in 1xE1 increments to the 8xE1 maximum.

Table 1. Connect ES Options for Ethernet Data and 4/8xE1 Wayside

Ethernet Data Throughput (Duplex), Mbps

Channel BW, MHz

Modulation N*QAM

Option Link Capacity NxE1 Data Only Data +

4xE1 Data + 8xE1

16 Connect 20 10 20.5 12.3 4.1 7

64 Connect 30 16 32.8 24.6 16.3

16 Connect 40 20 41.0 32.8 24.6 13.75/14

32 Connect 50 27 55.3 47.1 38.9

16 Connect 50 32 65.5 57.3 49.2 32 Connect 100 52 106.5 98.3 90.1 27.5/28

128 Connect 150 75 153.6 145.4 137.2

16 Connect 50 75 153.6 145.4 137.2 55/56

64 Connect 200 106 196.6 196.6 196.6

Connect ES Ordering and Capacity Upgrades Eclipse Connect ES Links are ordered in a base configuration providing up to 50 Mbps data throughput. Higher capacities are obtained by ordering additional capacity upgrades as downloadable software licenses. The licensed steps are:

• 50 Mbps, base configuration

• 100 Mbps = base configuration + 50 Mbps upgrade



Antenna and IDU/ODU cable options are ordered separately.

Connect ES Compatibility with Eclipse Node A mid-air meet is supported between an Eclipse Connect ES terminal and an Eclipse Node[1]. The plug-in option cards required at the Node are DAC ES and RAC 3X. For wayside E1 circuits a DAC 4x or DAC 16x is also required. Similarly, an AUX is required to support auxiliary data and alarm I/O interconnection.

[1] Check with Stratex Networks or your supplier for availability of RAC 3X versions for over-air operation to an

IDU ES.


Product Description

Connect ES Indoor Unit (IDU ES) The IDU ES includes a 4-port Layer 2 Ethernet switch, with four 10/100Base-T Fast Ethernet interfaces, and eight RJ-45 E1 75 ohm unbalanced, or 120 ohm balanced tributary interfaces.

Auxiliary data is supported at 64 kbps synchronous or up to 19.2 kbps asynchronous, and an alarm I/O enables 2 TTL alarm inputs and 4 TTL Form-C relay outputs.

The power supply requirements are -48 Vdc with limits of -40.5 to -60 Vdc.

Two redundant fan units provide forced-air cooling.

Figure 3 shows the IDU ES front panel. Table 2 describes the interfaces.

Figure 3. IDU ES front panel

Table 2. IDU ES front panel interfaces

No Item Description 1 -48 Vdc power connector 2-pin polarized D-series 2W2C power connector

2 Fuse/switch 5A fuse with integral power on/off switch

3 To ODU connector Type-N female connector for ODU cable

4 Maint. V.24 RJ-45 for serial V.24 connection to Portal PC

5 AUX Data DB-9 connector for auxiliary V.24 or V.11 data

6 Alarm I/O HD-15 connector for TTL alarm inputs and relay outputs

7 Status LEDs Status LEDs for IDU and companion ODU

8 NMS 10/100Base-T RJ-45 for Ethernet connection to Portal PC or ProVision

9 Ethernet ports 1 to 4 RJ-45 Ethernet 10/100Base-T traffic ports

10 E1 tributary interfaces 1 to 8 RJ-45 interfaces individually configurable for balanced or unbalanced operation

Connect ES Outdoor Unit

Eclipse Connect ES uses the compact ODU300 to convert the transmission payload to/from the required radio frequency channel. ODU 300 is available in standard ETSI bands from 5 to 23 GHz.

For 6 to 23 GHz the ODUs are designed for direct antenna attachment via an Eclipse-specific mounting collar supplied with the antennas. They are fixed for Tx High or Tx Low operation and polarization is determined by the position of a polarization rotator fitted within the mounting collar. Remote-mounting and indoor mounting kits are available for use with standard antennas. Remote mounting requires a short length of flexible waveguide; indoor mounting requires a normal waveguide feeder installation.


Product Description

At 5GHz the ODU must be remote or indoor-mounted and a 7/16” DIN connector and coax cable used to connect to a standard antenna. Unlike the 6 GHz+ ODUs it can be software switched for Tx High or Tx Low operation.

All ODUs meet the ASTME standard for a 2000 hour salt-spray test, and relevant IEC, UL, and Bellcore standards for wind-driven rain.

Figure 4. Eclipse Connect ES ODU with 0.3 m integrated antenna

Eclipse Connect ES Operation

The IDU ES processes all traffic and auxiliary data between the front panel customer interfaces and the ODU cable IF. ODU 300 converts the IF to/from the radio channel Tx and Rx frequencies.

The main modules within the IDU ES and their function are illustrated in Figure 5.

Figure 5. IDU ES Block Diagram


Product Description

Ethernet Module The Ethernet module incorporates an intelligent ISO layer 2+ switch, to provide the switching, prioritization and queuing functions between ports and transport channels, C1 and C2. It supports address learning for efficient management of Ethernet traffic in multi-host situations, and advanced layer 3 and layer 2 settings for traffic prioritization.

A gate array supports channel assignment and mux/demux to the digital baseband.

The four 10/100Base-T Fast Ethernet ports may be connected to the transport channels in transparent, VLAN or mixed modes. Channel capacity is determined by the number of E1 circuits mapped to the channel, where each E1 supports a 2.048 Mbps throughput. With one exception[2] the full NxE1 capacity of the radio link can be dedicated to Ethernet, or to a mix of Ethernet and E1 waysides up to a maximum 8xE1 waysides in 1xE1 increments.

Each channel supports a maximum 48xE1 for a maximum throughput of 98.3 Mbps per channel, and a combined Ethernet maximum of 196.6 Mbps.

Ethernet Traffic Configuration Eclipse Connect ES is configured using Portal, the Eclipse craft tool. User-friendly screens prompt for channel size (Ethernet bandwidth), modes of operation, QoS settings, and interface options.

Three modes of operation are supported, which define LAN connection options between the ports and channels. These options are Transparent, VLAN or Mixed:

• Transparent Mode This is the default, broadcast mode; all ports and channels are interconnected. It supports up to four customer connections (ports 1 to 4) with bridging to and between the two transport channels (C1, C2).

Transparent Mode

• VLAN Mode VLAN or transport mode supports up to four separate LAN connections. Port 1 is dedicated to channel 1, and ports 2 to 4 are multiplexed to channel 2 to provide three virtual LANs (VLANs 2, 3 and 4). Internal VLAN port tagging of packets provides correct end-to-end matching of port traffic over the channel 2 link. Tags are removed before port egress at the far end.

[2] The exception is Connect 200, where its 106xE1 link capacity (217 Mbps) exceeds the Ethernet module maximum

of 96xE1 / 196.6 Mbps. The additional Connect 200 capacity may be used to transport up to 8xE1 waysides without impacting the 196.6 Mbps Ethernet maximum.


Product Description

VLAN Mode

• Mixed Mode Mixed or hybrid mode provides a two-LAN solution. The first provides a dedicated port 1 to channel 1 connection. The second provides a transparent (broadcast) connection, tying ports 2, 3 and 4 to channel 1. Packets received on any of these ports will be allowed to broadcast to the other three ports, but not to port 1 or channel 1.

Mixed Mode

Transport Channel Configuration Selection is provided for channel capacity on a per-channel basis:

• Channel capacity is selected in multiples of E1 to a maximum 48xE1 for an Ethernet maximum of 98.3 Mbps.

• Both channels can be operated over the same radio path, to provide a total throughput of 196.6 Mbps Ethernet (96xE1) on a Connect 200 link. The two channels can be operated as separate fast Ethernet VLANs, or aggregated (combined) using an external trunking switch.

QoS Configuration On networks where bandwidth is restricted or when priority for low-latency traffic such as voice and interactive video must be assured, Eclipse Connect ES supports industry standard QoS (Quality of Service) queue management techniques. Selections are provided for layer 3 ToS (Type of Service) and layer 2 CoS (Class of Service) priority settings plus simple port-based queuing.

IDU ES supports traffic prioritization options of:

• Port Priority Provides selection of a simple port priority, where each port may be assigned a 1 to 4 priority, where 4 is the highest. This prioritization only has relevance to ports using a shared channel. Ports with higher priority will have their data packets accepted by the queue controller ahead of the lower priority ports on a 8:4:2:1 weighted basis where, for example, eight priority 4 packets will be sent for every one priority 1 packet.


Product Description

• Priority Mode Enables traffic prioritization over a network based on tagging applied within the ToS field of a layer 3 packet header, or more commonly within the CoS field of a layer 2 header. For the IDU ES it is a read-only selection, and a selection applies to all ports (IDU ES cannot set tags).

A four-level priority queuing stack is supported, which means:

- Each of the possible 63 levels in the ToS (DiffServ) field in a layer 3 header are mapped into a four-level (2-bit) priority level within the IDU ES.

- Each of the possible eight priority values in the CoS (802.1p) field in the layer 2 header are mapped into a four-level (2-bit) priority level within the IDU ES.

Priority mode mapping data is shown in Table 3.

Table 3. Priority Mapping Table

Priority Level VLAN 802.1p DiffServ Value Port Default

4 high/premium 6,7 48 - 63 4

3 4,5 32 - 47 3

2 2,3 16 - 31 2

1 low 0,1 0 - 15 1

The Priority Mode options are:

- Port Default means that only the port priority settings will apply (priority options 1 to 4 above). Any layer 2 802.1p or layer 3 DiffServ tagging is ignored.

- 802.1p provides prioritization based on the layer 2 CoS field. - DiffServ provides prioritization based on the layer 3 ToS field. - 802.1p-then-DiffServ provides prioritization based first on the 802.1p tagging, then

on DiffServ . - DiffServ-then-802.1p provides prioritization based first on DiffServ tagging, then

on 802.1p. Port-priority prioritization will apply to incoming packets if packets are not tagged.

Flow Control Flow Control is an option for full-duplex links only. It is implemented through use of IEEE 802.3x pause frames, which tell the remote node to stop or restart transmission to ensure that the amount of data in the receive buffer does not exceed a ‘high water mark’. The receiver will signal to the transmitter to stop transmitting until sufficient data has been read from the buffer, triggered by a ‘low water mark’, at which point the receiver signals to the transmitter to resume transmission.

To be effective, flow control must be established from the originating source through to the end point, and vice versa, which means the equipment connected to the IDU ES ports and beyond must also be enabled for flow control.

Latency Network latency refers to the time taken for a data packet to get from source to destination. For an IP network it is particularly relevant to voice (VoIP) or videoconferencing; the lower the latency, the better the quality.

Latency is typically measured in milliseconds for one-way and two-way (round-trip) transits. For phone conversations a one-way latency of 200 ms is considered acceptable. Other


Product Description

applications are more tolerant; Intranet access should be less than 5 seconds, whereas for non real-time applications such as email and file transfers, latency issues do not normally apply.

Within an Eclipse network, the per-hop delay time is primarily dependent on the capacity of the radio link; the lower the capacity, the greater the delay. Table 4 shows nominal delay times.

Table 4. Typical Eclipse Connect ES and Eclipse Node Delay Times (one-way)

Capacity 50 Mbps 100 Mbps 150 Mbps

Delay Per Hop 0.7 ms 0.35 ms 0.17 ms

Max. Delay for 16 Hops 11.2 ms 5.6 ms 2.8 ms

Other contributors to overall latency are the devices connected to the Eclipse network, which for a VoIP circuit will include the external gateway processes of voice encoding and decoding, IP framing, packetization and jitter buffers. Contributing to external network latency are devices such as routers and firewalls.

Wayside Traffic Module The Wayside Traffic Module supports 8xE1 tributary circuits. Each is accessed on an RJ-45 connector.

A line interface unit (LIU) provides line isolation and surge protection, software selection of 75 ohms unbalanced or 120 ohms balanced operation, and switching for trib and radio facing loopbacks.

In the link transmit direction trib data is converted from serial to parallel and multiplexed to the digital baseband in blocks of NxE1 data, where N is the number of tribs configured.

In the link receive direction, baseband data is de-multiplexed to extract the tribs and trib clocking, de-jitterized, and converted back to a serial E1 data.

The module also supports AIS insertion, and a PRBS generator and receiver for trib BER measurement.

Auxiliary Data and Alarm I/O Module This module supports sync or async data, and TTL alarm inputs and relay outputs:

Auxiliary Data The DB-9 AUX Data connector supports one synchronous or asynchronous auxiliary data channel, which may be used to transport 3rd party NMS (or other data):

• Synchronous conforms to TIA/EIA-422 / V.11 at 64kbps, with selectable clock. The source of the transmit clock can be set to internal (provided by Connect ES) or external (provided by the user). For an external clock, channel synchronization is supported by a selectable clock phase (rising or dropping edge of the clock pulse).

• Asynchronous conforms to TIA/EIA-562 (electrically compatible with V.24)

• Asynchronous rates are 1200, 2400, 4800, 9600, or 19200 bps, with parity and stop bit selection.

Auxiliary data is transported within the link overhead, which is shared with NMS data.

Alarm I/O The HD-15 Alarm I/O connector supports two TTL alarm inputs and four Form-C relay outputs.


Product Description

• Individual alarm inputs are mapped to any output within an Eclipse network. Similarly, individual internal events can be mapped to any output.

• Multiple input or internal events may be mapped to a common output. Mapping is achieved using IP addressing for the destination Connect ES terminal, or if the destination is an Eclipse Node, to its IP address plus the slot location and output number for the AUX plug-in.

Alarm Inputs

The active state of each TTL alarm input is configurable to be active if the voltage on the input is high, or active if the voltage is low. The alarm software detects a change in the state of each input circuit, and raises or clears an input accordingly. The nominal alarm polling rate is 1 second.

Alarm Outputs

Outputs are user configurable to be normally high or normally low. Default is normally low (relay inactive). Additionally, a user can select on the Alarm I/O connector, a normally closed or normally open contact pair.

IF Module The IF module is the intermediary between the digital baseband and ODU 300. It provides the primary modulation and demodulation processes to/from the ODU, and configuration of the radio modulation/bandwidth options. Via its N-Plexor it also provides a telemetry channel for ODU management, and -48 Vdc for ODU power.

Management Module The management module provides: • Terminal control and management • DC/DC converter • Boot (start-up) flash • License and configuration flash • Network management access • Alarms and sensor management

The management module also supports two long-life axial fans. Fan operation is temperature controlled such that under normal conditions one fan operates. Operation is cycled between the two, but both will operate if one fails to keep the temperature below a preset threshold.

ODU 300 The quadrature modulated signal from the IF module is processed to derive separate I and Q signals to modulate a Tx IF, which when mixed with the transmit local oscillator at the mixer stage, provides the selected transmit frequency. Local oscillators are synthesizer types.

Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx power.

After the mixer, the transmit signal is amplified and passed via the diplexer to the antenna feed port.

A microprocessor in the ODU supports configuration of the synthesizers, transmit power, and alarm and performance monitoring.

A DC-DC converter provides the required low-voltage DC rails from the -48 Vdc supply.


Product Description

In the receive direction, the signal from the diplexer is passed via a low noise amplifier to an Rx mixer, where it is mixed with the receive local oscillator to provide the Rx IF. It is then amplified in a gain-controlled stage to compensate for fluctuations in receive level, and converted to the cable IF for transport via the ODU cable to the IDU ES IF module.

Tx/Rx split options are based on ETSI plans for each frequency band. The actual frequency range per band and the allowable splits are range-limited to prevent incorrect user selection.

A power monitor is included in the common port of the diplexer to provide measurement of transmit power.

Connect ES Link Concepts This section introduces Eclipse Connect ES capabilities for transporting Ethernet and E1 PDH traffic. It begins with single-link concepts and progresses to star network applications. Over-air inter-operation with an Eclipse Node is also shown. Ring network applications are introduced in the following section.

Basic Link Operation Figure 6 illustrates basic link operation where the IDU ES directly supports up to 4 hosts, which may all be on a common LAN, or prioritized in VLAN mode on up to four LANs over two independent link transport channels, C1 and C2.

Figure 6. Basic Eclipse Connect ES Link

Using one transport channel, Connect ES supports Ethernet capacities to 98.3 Mbps. Using both channels, Connect ES supports two separate Ethernet LANs to a maximum 98.3 Mbps on each for a total of 196.6 Mbps (Connect 200 option).

Link capacity may be configured to support Ethernet together with E1 wayside tribs, up to maximum 8xE1 waysides in 1xE1 increments. For example, a radio configured for a throughput of 106 Mbps (Connect 100 option, 52xE1) may be used to support:

• 106 Mbps Ethernet using both transport channels and no E1 tribs. The split between channel (LAN) assignments may be 53/53 Mbps through to 98/8 Mbps.

• 104 Mbps Ethernet and 1xE1, through to 90 Mbps Ethernet and 8xE1.

LANs supported on transport channels C1 and C2 cannot be “paralleled” without use of an external aggregation or trunking switch, as doing so will create an IP loop.


Product Description

Basic Link with External Ethernet Switch While IDU ES provides full layer 2 switch functionality, it can only support a maximum of four directly connected hosts, which for most office applications is insufficient, bearing in mind each device on the LAN must be directly connected to its own port on the switch (star connected).

The solution is provided by a 3rd party industry-standard multi-port layer 2 switch, as shown in Figure 7.

Figure 7. Connect ES Link with 3rd Party Switch – Single Channel

When used in this way, the LAN mode and QoS settings would normally be configured within the external switch, and a single port connection used to the IDU ES.

With just one channel in use (C1 or C2), the maximum Ethernet capacity supported is 98.3 Mbps (48xE1). For this throughput an optimum solution is provided by the Connect 100 option, which with on over-air link capacity of 52xE1 supports a total throughput of 106.5 Mbps for 98.3 Mbps Ethernet and up to 4xE1 waysides. Where additional E1 tribs are required (to a maximum 8xE1) Ethernet capacity is reduced in 2.048 Mbps steps per trib.

The next step up in radio capacity is the Connect 150, which while easily accommodating a single channel Ethernet maximum of 98 Mbps and the maximum 8xE1 waysides, is not an efficient solution for this configuration as 39 Mbps of available throughput is not used.

However, if both IDU ES channels are used, as shown in Figure 8, then total Ethernet throughput can be to 153 Mbps for Connect 150, and to 196 Mbps for Connect 200. The IDU ES is configured for Mixed Mode to support two independent LANs/VLANs on transport channels C1 and C2, and each is separately ported to the external switch.

Figure 8. Connect ES Link with 3rd Party Switch – Both Channels

The separate LANs, (VLAN 1 and VLAN 2) cannot simply be paralleled at each end of the link to provide a single LAN entity. However a solution is provided by switches that support aggregation.

Figure 9 shows how such paralleling, or load-sharing, can be achieved using LAN link aggregation; a feature now supported by many layer-2 managed switches, or trunking switches.

Load sharing aggregates available Ethernet bandwidth from two separate physical LAN links to support a single higher capacity LAN/VLAN. Doing so also provides a more resilient end-


Product Description

end connection, and enables load balancing whereby communications activity is distributed across both Ethernet channels to help ensure that no one channel is overwhelmed.

• Link aggregation prevents a failure of one LAN channel leading to the complete disruption of traffic that would otherwise have been assigned to that channel. If one channel fails, then capacity available on the other channel is shared. While the reduced bandwidth may result in some traffic loss for low-priority traffic, it should ensure security for all higher priority traffic. Under normal situations load balancing ensures equitable traffic distribution between the two LAN channels.

• Performance is improved because with appropriate QoS settings the capacity of an aggregated LAN link is higher than each individual link.

• Standard LAN technology provides data rates of 10/100 Mbps and 1000 Mbps. Aggregation can fill the gaps when an intermediate performance level is more appropriate. For example by aggregating two 100 Mbps LANs, a step from 100 Mbps to 1000 Mbps LAN technology can be avoided where only 200 Mbps is required.

Where link aggregation is to be used, the switch function within the IDU ES should be disabled, so that it operates as a straight LAN cable. Contact your Stratex Networks Helpdesk for guidance on this procedure.

Figure 9. Connect ES Link with 3rd Party Switch – Both Channels and Load Sharing

Where Connect ES links are to be networked, they must be physically interconnected at intermediate sites. Figure 10 shows a typical small network with back-to-back IDU ES installations at site B.

• External layer 2 multi-port switches have been included at sites A, B and C s as these are required where more than four host devices are locally connected on the LAN.

• Site D shows no external switch. For a small office where no more than four host devices are connected, the IDU ES provides a complete solution.

• E1 circuits are trib-cabled as for a standard E1 link.

• NMS visibility between all IDU ES terminals requires linking of the Ethernet NMS ports at each site. As the IDU ES has a single Ethernet NMS port, where three or more are grouped at a site, as at Site B, a simple external hub must be used to provide the required porting capacity.


Product Description

Figure 10. Networked Connect ES Links

Connect ES radio links cannot be hot-standby or diversity protected. Where such protection is required, use the Eclipse Node with a DAC ES installed for Ethernet access, and one or more DAC 16x or DAC 4x plug-in cards for E1 tribs.

Eclipse Node and Connect ES may be included within the same network, either as back-to-back links or end-to-end terminals over a common radio path. The mid-air meet capability[3] of the IDU ES and DAC ES supports IDU ES spurring from an Eclipse Node, as illustrated in Figure 11.

Figure 11. Connect ES Terminal Spurring from an Eclipse Node

[3] Node-to-IDU ES linking requires RAC/ODU compatibility; contact Stratex Networks or your supplier for guidance.


Product Description

Ring Concepts Eclipse Connect ES is ideally suited to Ethernet ring topologies where traffic redundancy is provided by alternate path switching in an IP environment. The contention that would otherwise occur with the arrival of looped IP data streams is managed by the Rapid Spanning Tree Protocol (RSTP), which is supported on an externally connected switch at each ring site.

• RSTP creates a ‘tree’ that spans all of the switches in a network, forcing redundant (alternate) paths into a standby, or blocked state. If subsequently one network segment becomes unreachable because of a device or link failure, the RSTP algorithm reconfigures the tree to activate the required standby path.

• RSTP service restoration or ‘convergence’ times are typically 1 to 3 seconds.

Figure 12 illustrates the ring concept, which supports Ethernet bandwidths to 98 Mbps for a single channel connection, or as in Figure 13, to 2x98 Mbps using both channels.

Figure 12. Connect ES Links in a Ring

• Fast Ethernet to 98.3 Mbps (48xE1) is supported using the Connect 100 link option.

• Just one IDU ES transport channel (C1 or C2) is used.

• Each IDU ES is configured for Transparent Mode operation.

• One Ethernet port on each IDU ES is connected to the RSTP layer 2 switch.

• The RSTP switch may be used to support VLAN operation over the ring.

• For NMS visibility around ring, IDU ES terminals are interconnected at each site via their Ethernet NMS ports (Mdi or MdiX cable).

• E1 circuits can also be configured on each link as pt-to-pt connections (not ring protected). Up to 4xE1 may be configured without impacting the single-channel 98 Mbps Ethernet bandwidth of a Connect 100 link. Beyond 4xE1, Ethernet bandwidth is reduced by 2 Mbps for each additional E1 circuit.


Product Description

Higher ring capacities are supported by Connect 150 or Connect 200 links, as illustrated in Figure 13. For these options both IDU ES transport channels are used, which effectively operate as two concentric rings (two LANs). The RSTP switch at each site must support alternate path switching on the two independent LAN rings, and where aggregation into a single LAN is required, also support link aggregation. Refer to the Load Sharing example under Basic Link with External Ethernet Switch for more information on link aggregation.

The example network includes a spur to Site F, and has E1 circuits configured between sites.

Figure 13. Connect ES Links in an Extended Capacity Ring

• For Connect 150 and Connect 200, both IDU ES transport channels (C1 & C2) are used. For other Connect ES options (Connect 20 to Connect 100) use of C1 and C2 is optional, as only one channel is needed for these capacities.

• The two transport channels effectively provide two concentric LAN rings. Each channel is brought out on separate IDU ES ports for connection to an RSTP switch. They may be to independent switches, or as shown, to one switch that has support for alternate path switching for two LANs, and LAN-link aggregation to present one physical 200 Mbps LAN connection to the customer.

• The E1 circuits are point-to-point configured. 4xE1 runs counter-clockwise from Site A to drops at Sites E, D and C. 4xE1 also runs clockwise from Site A to drops at Sites B, C and D. E1 tribs are back-to-back connected between IDU ES terminals at intermediate sites.


Product Description

Example Networks This section provides example network applications. Applications are included for:

• Small office LAN extension • Small office private Intranet • Medium office-office private VLAN • Medium capacity Utility or Health Board Network

Small Office LAN Extension Figure 14 shows a main office connected to a satellite office for Ethernet and TDM circuits. Ethernet supports the LAN extension, and an E1 circuit supports a legacy PBX trunk interconnection. All communication between offices is via the Connect ES link, bypassing the local telco and resulting in just one set of access charges. Figure 14. Small Office LAN Extension

• An external layer 2 switch is used at the main office to support the 5+ devices connected. At the remote office, the DAC ES directly supports switch functions for up to four devices.

• The IDU ES is operated in transparent mode. • Legacy PBXs are shown, with an E1 trunk inter-connection. • A Connect 20 option (10xE1) is used to provide 18 Mbps Ethernet (9xE1) and

a 1xE1 trib. • The network may easily be extended to other sites using a star and/or ring

topology. See Figure 15.


Product Description

Small Office Intranet Figure 15 shows a three-office private network. All inter-site data and voice communication is by Ethernet, bypassing the local telco and resulting in just one set of access charges at the main office. Figure 15. Small Office Private Network

• External layer 2 switches are used at the main office and office A. At office B, with just four devices on the local LAN, the IDU ES provides switch support directly.

• The external switches and PBX VoIP trunk cards set QoS tagging. • VoIP traffic is 802.1p level 7 tagged (highest priority). • 802.1p tagging may also be applied on other ports to provide end-end port-

based prioritization between main and office A sites. • At all sites, the IDU ES is set for 802.1p port priority.


Product Description

- Ensures VoIP traffic has highest priority on the network, then any lower-level tagged traffic, and lastly untagged traffic.

- At office B, tagged traffic only has relevance for the VoIP port, P4. There are no other devices on the office B LAN that can set 802.1p tags. However Port Priority can be set to provide weighting in favor of one or more of the local workstations for access to the local LAN and the network.

• Radio link capacities may be extended to support up to 106 Mbps Ethernet using Connect 100 (both transport channels), 153 Mbps using Connect 150, and 196 Mbps using Connect 200.

• The network can easily be extended to other sites using star and/or ring topology.


Product Description

Medium Office Intranet Figure 16 shows an inter-site private network for a medium sized office. All inter-site data, voice and video traffic is VLAN connected. Hot standby or diversity protection is provided on the Fast Ethernet connection between Main Office and Office A using the Eclipse Node. From Office A to Office B the link is provided by a ‘mid-air-meet’ between the Node (DAC ES + RAC + ODU at Office A), and Connect ES terminal (IDU ES + ODU at Office B).

Figure 16. Medium Office Private LAN Extension

• A switch hierarchy is used to mange separate work-group LANs at and between sites.

• VLANs are used between the sites to provide workgroup segregation (sales and finance, production, development). - The DAC ES cards are configured for transparent mode, with the external

switches applying VLANs on a single DAC ES transport channel.


Product Description

• CoS and/or ToS packet header tagging can be applied by the external switches for traffic prioritization. Port Priority prioritization can also be used. - The L2 switches support 802.1p CoS tagging, and port priority. - The L3 switches support DiffServ ToS tagging, 802.1p CoS tagging, and

port priority. - QoS tagging particularly applies to voice and video traffic. - The DAC ES cards and IDU ES are configured for a 802.1p and/or

DiffServ Priority Mode, depending on the external switch settings. • The protected link capacity could be increased to 75xE1 to support two

Ethernet channels with a combined maximum of 153 Mbps. These two channels may be operated as separate fast Ethernet VLANs, or combined within the layer 3 switch to support a single aggregated 150 Mbps connection.

• The network can easily be extended to other sites using star and/or ring topology.


Product Description

Medium Capacity Ring Network Figure 17 is an example of a Fast Ethernet ring for a Utility or Health Board. The main inter-site LAN bandwidth is 98 Mbps, which is used to support all computing, PBX and land mobile communications. PDH tribs for the PBXs and land mobile connections are supported via TDMoIP.

Another 50 Mbps LAN is dedicated between HQ at Site A, and the Processing Center at Site E.

Eclipse Connect 150 links are used on the ring, with ring-protection provided via the external RSTP switches.

Traffic on the spur is hot standby protected using Eclipse Node installations at Sites G, H and J.

Figure17. Medium Capacity Ring Network for Ethernet and PDH

• To support a total 153 Mbps, both IDU ES channels are used; 98 Mbps on transport channel 1 for LAN 1, and 55 Mbps on channel 2 for LAN 2.

• Each LAN is held separate; their traffic is not aggregated in this example.

• While IDU ES supports up to 8xE1 circuits, this capability has not been used on the ring for the PBX and land mobile connections as unlike Ethernet traffic it would not be protected. By transitioning E1 circuits over Ethernet via TDMoIP


Product Description

devices at each end, they are afforded normal Ethernet alternate-path protection. Assigning an 802.1p level 7 priority (highest) on the voice ports will provide the low latency needed.

• For information on the RSTP switch, refer to Ring Concepts on page 15.

• Ring capacity could be increased to support up to 196 Mbps total throughput, using the Connect 200 option.

Summary

Eclipse Connect ES provides highly flexible and cost efficient solutions for transport of Fast Ethernet traffic, with or without companion E1 traffic. Star and ring network topologies are supported and QoS options meet industry-standards.

Stratex Networks understands the inter-networking industry and its requirements, and is well positioned to provide the support needed for radio-based solutions.


Product Description

Connect ES Feature Summary Eclipse Connect ES features include:

• Fully scalable throughputs from 20 to 200 Mbps.

• Radio capacity can be dedicated to Ethernet, or split between the Ethernet and E1 interfaces in E1 increments to a maximum 8xE1.

• Supports radio channel bandwidths from 7 MHz to 55/56 MHz.

• Licensed 50 Mbps capacity increments from a base license of 50 Mbps throughput to a maximum 200 Mbps.

• Over-air compatible with Eclipse Node comprising ODU300, RAC 3X and DAC ES. Compatibility extends to the DAC 4x/16x for tribs and to the AUX for auxiliary services.

• Front panel provides access to four 10/100Base-T Fast Ethernet ports and 8xE1 tributary circuits.

• Ethernet ports may be connected to one or two NxE1 radio transport channels in transparent, VLAN or mixed modes.

• Each transport channel can be configured for up to 98.3 Mbps Ethernet.

• Operates as an intelligent ISO layer 2+ switch for Ethernet traffic management.

• Configuration options support industry standard QoS queue management options. Selections are provided for layer 3 ToS (Type of Service) and layer 2 CoS (Class of Service) priority settings plus simple port-based queuing.

• Non-protected radio path.

• At intermediate/repeater sites each IDU ES is installed back-to-back with Ethernet, E1 and NMS interfaces cable-connected.

• Includes an AUX and alarm I/O capability:

- One Auxiliary channel at 64 kbps synchronous or up to 19.2 kbps asynchronous.

- 2 TTL alarm inputs and 4 TTL Form-C relay outputs.

• NMS channels to 512 kbps.

• 1RU 19” rack module.

• DC input voltage -40.5 to -60 Vdc.


Product Description

Glossary

802.1p An IEEE standard for providing QoS traffic prioritization using three bits in the CoS

header (defined in 802.1q) to allow switches to reorder packets based on priority level.

CoS Class of service; a layer 2 header in an IP packet.

DiffServ Differentiated services. A layer-3 protocol which tags each frame, either at the originating device or at an intermediate point, to identify the requested level of service.

NTU Network terminating unit.

PDH Pleisiochronous digital hierarchy. Asynchronous multiplexing scheme in which multiple digital synchronous circuits run at different clock rates.

QoS Quality of service. Measure of performance for a transmission system that reflects its transmission quality and service availability.

RSTP Rapid spanning tree protocol.

SDH Synchronous digital hierarchy. European standard for synchronous data communications over fiber-optic media. Transmission rates range from 51.84 Mbps (STM0) to 155.52 Mbps (STM1) through to 10+ Gbps.

SONET Synchronous optical network. North American standard for synchronous data communications over fiber-optic media. Compatible with SDH with transmission rates ranging from 51.84 Mbps (OC1) to 155.52 Mbps (OC3) through to 10+ Gbps.

STP Spanning tree protocol.

TDM Time division multiplexing. Multiple low-speed signals are multiplexed to/from a high-speed channel with each signal assigned a fixed time slot in a fixed rotation.

TDMoIP TDM over IP. A technique supporting the emulation of TDM traffic on an IP connection.

ToS Type of service; a layer 3 header in an IP packet.


Product Description


eclipse connect es - Описание.pdf

Documents