16/32-Port E1/T1 over Ethernet chassis

Product Overview

The PacketBand-TDM32 is a highly-featured 2U chassis supporting 16 or 32 E1/T1 and/or V.35/X.21 circuits. These
“leased lines” can be transported across many different types of packet networks.

• Highly accurate and stable clock recovery processes maintains end-to-end synchronisation of the E1/T1 interfaces.
• G.823 Synchronisation Mask levels of accuracy achievable equalling the stability of traditional leased lines
• Dual load-sharing hot-swappable AC/DC PSUs
• Inter-works with the wide range of smaller PacketBand units
• Support for:
  • Clear-channel and channelised
  • Clear channel G.703
  • G.704 "Grooming"
  • External clock sources
  • Support for RSTP and LACP
  • Link “Backup” for resilience
  • Multiple UTP and fibre (SFPs)
  • Jumbo packets
    
• Enhanced Multicast clocking mode for larger networks
• “Tuneable” algorithms to match network characteristics
• Various clocking options to suit different network types
• Compact 2U chassis mounts 300mm deep
• Optional cooling fans for Extended Temperature environments.
• All interfaces front presenting
• Robust, reliable and professional quality
• Excellent management, network visibility, diagnostic and statistics

PacketBand excels in delivering stable and accurately clocked E1/T1 “leased lines” over various types of packet networks.

E1/T1 circuits can be individually configured without constraints. V.35 and X.21 interfaces are ordered as such, and as DCE or
DTE in blocks of 4 ports; thereafter there are no individual configuration constraints. Reconfiguring any port does not impact
on any other and no “re-boots” are required to action configuration changes.

The system also supports “grooming” whereby a single E1 can support multiple remote low-speed devices, such as the
PacketBand-TDM-VX which delivers V.35 and V.11/X.21 services.

PacketBand-TDM32 can support links to a maximum of 128 different PacketBand units.

Connectivity Overview

A single PacketBand-TDM32 chassis can support up to 32 E1/T1 circuits in G.704 or G.703 mode, up to 32 V.35/X.21
ports or 16 E1/T1 and 16 V.35/X.21. These circuits can be connected to other chassis and/or to stand-alone smaller

Cards and Interfaces

• All cards are front insertable The chassis supports:

One or two PSUs

• AC and DC options are available
• “Hot-Swappable” according to the ATCA PICMG 3.0 specification
• One PSU supports a full chassis

Ethernet Card

• Standard Card1 x SFP cage and 2 x RJ45 UTP
• Optional Card 2 x SFP cages and 2 x RJ45 UTP

Terminal Card

• Standard Card1 x RJ12 control port and 1 x RJ12 alarm relay
• Optional Card 1 1 x RJ12 control port, 1 x RJ12 alarm relay and 2 x RJ45 external clock inputs 2.048Mbps HDB3
• Optional Card 2 1 x RJ12 control port and 1 x RJ12 alarm relay with 2 x RJ45 external clock inputs 2.048Mbps HDB3 encoded and 2 x 50 Ohms BNC 10MHz external clock sources

E1/T1 over Ethernet or IP Card

• Each card supports 16 user-switchable E1 T1 interfaces
• 8 port E1/T1 cards are available with Telecoms Approvals for direct connection to carrier leased lines
• The chassis supports two cards
• RJ45 connectors
• 75 Ohm (75 Ohm RJ45 to BNC passive conversion cable required)
• Full E1/T1 or full/fractional G.704  

V.35/X.21 Card

• 16-port card
• Order as V.35 or X.21 in blocks of 4 ports.
• Specify each block of 4 as DCE or DTE
• High-density HDMI sockets
• Various cable adaptors available

Clocking

• Clock recovery, acuracy and stability is key to many TDM applications and the clock recovery performance must be maintained when migrating to a packet network solution. Many types of equipment expect similar performance to that of traditional leased lines which are generally referenced to the
  G.823 Synchronous Interface mask. The PacketBand range is specifically designed and optimised to excel in this area and when used on high-quality networks can meet and exceed the G.823 requirements. Knowing when a clock moves out of historical parameters, for whatever reason, means action can be taken before the service is significantly impacted. PacketBand monitors the stability of the recovered clock and provides an Alarm should it wander from its average trend.

Clock Algorithms

• The TDM32 supports three advanced algorithms as standard. These are designed and optimised for different network types, broadly-speaking one for high quality managed networks with low jitter (PDV) and packet loss, one for networks with lower performance characteristics and one for applications where
  stability is paramount but the G.823 mask is not targeted. Within these options are two further settings allowing tighter optimisation if required.
  This means PacketBand can be configured to extract the best possible service for any given network.

Clock stability

• Clock frequency stability performance can exceed AT&T TR- 62411, T1.403, G.824 and G.823 on quality networks for both Traffic and the much more demanding Synchronisation requirements. This is an important strength as many applications will either require very accurate synchronisation to run correctly (for
  example mobile backhaul), or there could be multiple clock sources within the network which all require aligning accurately to ensure error-free and reliable services. PacketBand can deliver reliable services that clock as well as traditionally delivered leased lines. PacketBand alarms to DbManager should the recovered clock’s stability move outside of configured historic thresholds, giving immediate information should the clock deteriorate for any reason.

Clock Sources and Clocking

• Although easy to use and configure, PacketBand offers customers a number of solutions for different clocking scenarios as briefly described below.
  The PacketBand’s advantage is not only very accurate clocking and reliability, but also the flexibility to work in different modes to suit a variety of situations and applications.

TDM port

• The clock can be extracted from any of the attached E1 T1 user ports. This would normally be used at the “Master” end of a circuit with the remote “Slave” unit recovering clock across the packet network and clocking its attached equipment as described in “Adaptive” below.
  
  
• Adaptive
  Using sophisticated recovery algorithms, clock can be derived from any of the incoming packet streams from a remote “Master” TDM32 or any other PacketBand. The remote “Master” would generally have a high quality clock source presented on its TDM or external port. This allows the “Slave” TDM32 to adaptively recover this clock very accurately across the packet network, in effect synchronising both devices to a common clock..
• External
  The Terminal Card optionally provides 2 x RJ45 connectors which accept either a 2.048MHz or 2.048 HDB3- encoded clock. The card is also available optionally with two BNC connectors which accept 10MHz clock sources.
• Multicast
  Larger networks with many “hops” pose a particular challenge to recovering the clocks down to the very low parts per billion. This is due to the compounded tiny amounts of high frequency jitter added by each switch. To circumvent this situation, Patapsco provide a unique “Multicast” system whereby the clock recovery traffic is separated from the user traffic. This means the clocks can be sourced more locally, perhaps on a regional basis, and transported in a low-speed high-priority efficient Multicast service. A significant additional significant advantage is that the user traffic, the bulk of the capacity, is no longer transporting or needed for clocking; it can therefore be assigned a lower priority than would be usual, making network provisioning easier and more efficient.
  
  
  
  The PacketBand-TDM32 can act as either a generator of the Multicast clock for use by other remote devices, or join a Multicast feed using IGMP and thereby source its clock. More than one Multicast can be configured to provide enhanced resilience.
  See also the PacketBand-TDM-3MC and the TDM-1MC Application Overviews which have further information on the Multicast feature.
  
  
• Internal
  In the unlikely event of a PacketBand losing all external clock sources, including local E1s, it can fall back to its internal oscillator. These are very accurate with good stability characteristics and various options are available.
• External
  The standard Terminal card can be optionally upgraded to support 2 x RJ45 2.048Mbps HDB3 encoded and 2 x BNC 10MHz clock sources.
• Clock Hold-Over
  Problems in the packet network, for example a sudden increase in jitter or an interruption in packet delivery, can cause an unwanted movement in the recovered clock. To avoid this PacketBand enters a “hold-over” state, maintaining the recovered clock at the last value prior to the problem. This means the clock is always stable irrespective of issues within the network. The standard oscillator within the TDM32 maintains this hold-over clock to within 40ppb and with good temperature stability. Other options are available, including an oven-controlled source; please contact Patapsco or your supplier for information.
• Loop-Timing
• In instances where both ends of the circuit have a good quality common clock source (for example ISDN clocks into PABXs) both PacketBands can be set to clock from this local source.

Oscillators

If the PacketBand is recovering clock, the quality of the oscillator used as part of the recovery process is very important.

• The receive PacketBand running “Adaptive” clocking uses a variety of different information and many calculations to ascertain how to modify its
  on-board oscillator’s output to match the clock of the remote or “Master” end. It can be seen that the more stable the on-board oscillator, the more stable the recovered clock. TDM32 is fitted as standard with a temperature stabilised stratum 3 Enhanced TCXO oscillator which is ideal for all but the very
  exacting applications. This delivers +/-12ppb over the full temperature range and typically in “Hold-Over” better than +/-15ppb in a 24 hour period with the unit operating at ambient room temperature.
  The equipment is optionally available with an oven stabilised oscillator (OCXO) which may be relevant in environments where the temperature varies considerably. Note that the quoted figures are for the stability of the on-board oscillator itself, not the actual clock provided to attached devices.
  PacketBand adds/subtracts from this internal clock to derive the recovered clock which in the majority of instances is significantly superior to the base oscillator with zero wander/drift over a period of time. Oscillators comply with G8261/Y.1361 and detailed specifications are available on request.

PDV (Packet Delay Variation or jitter)

• The PacketBand-TDM32 has the ability to support large amounts of network jitter. The absolute maximum buffering available which depends on a number of variables including the number of channels, circuit emulation protocol and frames per packet (Patapsco have a spread sheet available).
  As an example, 16 full E1s running UDP/RTP and VLANs with IPv4 (a protocol combination with a high packet overhead) and 8 frames per packet, gives a maximum configurable jitter of 256msecs (+/-128msecs). Running 32 full E1s in the same configuration provides for 128msecs.
  The jitter buffer can be set in msec granularity and adjusted manually or automatically whilst the circuit is in place, overcoming ‘skew’ at start up time caused by the first packet in the buffer being slower or faster than average.
  The buffer re-orders out of sequence packets. If packets are lost by the network the data to be transmitted to the attached device by PacketBand is user configurable. Statistics are available to provide information on usage (see below).

Ethernet and the Packet Switch

• Support for 10/100/1GE.
• Support for “Jumbo-packets” up to 10,240 bytes in size.
• Single MAC and IP address, Default Gateway and SubNet Mask, support for DHCP. Disordered packets are reordered automatically. IPv4 (IPv6 Q2 ’09).

Prioritisation

• TDM packets can be assigned IP Diffserv ( DSCP ) or ToS and 802.1p CoS values.
• PacketBand supports full 802.1q tagging and the associated 802.1p CoS prioritisation levels.
• All egress packets including TDM links can be prioritised across four output queues using CoS (802.1p) or Diffserv/ToS values.

VLAN Handling

• PacketBand’s powerful and latest-generation on-board packet switch offers advanced 802.1Q VLAN facilities such as multiple TAGing, TAG insertion/removal, port routing based on default TAG or a Global TAG table. Egress packets can be TAGed, have multiple TAGs or be stripped of TAGs according to configuration.
• PacketBand also supports Provider Mode whereby customer packets are TAGed for transport across the network with the TAGs being removed before passing back to the customer at the far end.

Link Aggregation Control Protocol (LACP) –

• This powerful optional feature enables two or more Ethernet ports to be connected between PacketBand and the network switch and for the links to be aggregated together as defined in LACP IEEE 802.3-
• 2005. This aggregation makes it appear as if the multiple links are acting as a single high capacity circuit. Furthermore, it adds an important level of redundancy with automatic rerouting.
• See the TDM-4E and TDM-1MC Application Overviews for further information.

Rapid Spanning Tree Protocol (RSTP) –

• RSTP (as defined in IEEE 802.1D-2004) identified the means to build an Ethernet network which contains physical loops between bridges. This optional facility enables PacketBands to be connected
• to more than one network switch via different circuits and to provide an automatic fall-back in the case of a link failure. This is covered in more detail in the PacketBand-TDM-4E and TDM-3MC Application Overview.

Stand-by or Backup Link

• For resilience purposes, a second Ethernet/IP network port can be configured to which PacketBand will switch should the primary path fail.
  No “intelligence” in the network is required as this is handled and co-ordinated between PacketBands. Appropriate Alarms are generated with changes to the DbManager’s Map.

Rate Limiting

• Packet Ports can individually have the traffic capacity restricted in various ways, even though the access is 10/100/1GE. This is particularly useful on Ethernet ports when connected to users LANs where the main link to the network could be “swamped” by data from attached devices.

Overheads

• In order to transport TDM data over the packet network, there is some overhead caused by caused by encapsulating the data inside the packet network protocol.

The Protocol

• PacketBand supports a number of different packet network protocols. The user’s choice of a particular network will affect the overall size of packet headers.

Size of Packet

• PacketBand supports a configurable packet size per Logical Link. There is a trade off between transmitting small packets at a fast rate (low latency, larger overhead due to protocol headers) and transmitting larger packets at a slower rate (bigger latency, smaller overhead).
• Typical overheads are in the 5% to 10% range. Patapsco have a spreadsheet available which identifies overheads based on a number of different parameters. Contact Patapsco or your supplier.

Latency

The total end-to-end latency experienced between two E1 over Ethernet/IP devices using PacketBands is made up of four elements:

• Processing Delay
  The latency or processing delay through each PacketBand is optimised to be as low as possible. Typical processing delay is less than 1msec.
• Transmit Delay
  This is the time necessary to wait for sufficient incoming data to arrive from the attached device so a packet of the configured size can be built and transmitted over the network. This is typically around the 1msec range.
• Jitter
  Packet network networks differ in how consistently packets pass though them; some packets take more or less time than the average. PacketBand provides a synchronous clocked circuit to the attached devices and therefore has to have data ready and available for the relevant clock pulse. PacketBand buffers the fast packets so as to ensure the slow ones can arrive in time to be used. The amount of buffering is user-configurable and will depend upon the performance of the network. Note that this buffering is only required on the PacketBand receive data path and the amount of buffering needed (which equates to latency) is a result of the network, not PacketBand.
• Transit Delay
  All IP networks have different average transit delays. These vary depending upon a large number of criteria, including the number of “hops” and whether satellites are involved. Typically, domestic links are very fast, inter-continental around 60msec and a satellite can add 250msecs. Please consult your network supplier.
• Summary:
  Between any pair of PacketBands on a terrestrial network, the most significant element contributing to latency is size of the Jitter Buffer (which is user configurable). This is directly dependant on the performance of the network and outside the control of PacketBand.

CESoP Modes

• PacketBand supports both “Structure Aware” and “Structure Agnostic” E1 over Ethernet modes.
• Complies with ITU-T recommendation Y.1413, IETF PWE3 draft standards CESoPSN, SAToP and CES draft IAs from MEF and MFA .

“Logical Links” and “Grooming”

• A Logical Link is the emulated circuit over the packet network between a pair of PacketBand devices.
• If running G.703 or G.704 between end points each circuit requires 1 Logical Link.
• If “grooming” multiple time slots from many remote destinations into a single G.704, every individual link between PacketBands (irrespective of speed) requires 1 Logical Link.
• The PacketBand TDM32 as standard supports 32 Logical Links and optionally up to 128.
• Channelised, groomed and unstructured E1/T1s can be supported on a per interface basis with no constraints.
• The IP ToS, Diff Serv and Ethernet VLAN Tagging is configurable on a per-Logical Link basis

Approvals

• All approvals completed in a UK Accredited laboratory. Reports available. CE marked.
• Safety and Emissions ( EMC ) approvals (CE and FCC).
• Telecoms Approvals for connection to carrier leased lines is optionally available as an 8 port card. The TDM32 can support 2 of these cards.
• PacketBand TDM32 is RoHS compliant.

Management Overview

• PacketBand can be locally or remotely configured using Patapsco’s easy-to-use high functionality DbManager GUI software.
• DbLite is supplied free with each unit.
• Optionally available are different versions to support requirements for larger or more integrated networks. It is sophisticated but simple to use via an intuitive Graphical User Interface (GUI) which controls, configures and monitors individual Patapsco units and complete networks.
• Options support multiple real-time work-stations, a network of PacketBands and links, and have additional capabilities such as SNMP Traps & Alarms and continuous polling of devices. A document identifying the differences between DbLite and other versions is available to download from this page.
• Used by various organisations with different network sizes - up to and including carriers - versions of DbManager deliver a network-wide view of all PacketBands and links via a 4-layer “tree-structured” overview. The status of all PacketBands and links are easy to identify with Alarms being colour coded and passed up the tree. Separate windows provide Event and Alarm information with the ability for operators to add comments etc.
• Different access levels and passwords provide operators with appropriate capabilities within the program.
• An option to encrypt the management traffic across the packet network is available, together with a key management/update system.
• Demonstration software is available which illustrates both the DbManager and the PacketBand features. Please ask for information.

Configuration Changes

• Configuration changes on PacketBand are via the DbManager. All configurations can be stored on DbManager. Installations require little or no expertise in the field as most configurations (other than IP address) can be performed remotely.
• DHCP is supported.

Management Tools

• A wide number of statistics are available for the E1/T1 circuit and Ethernet port.

Alarms/Events

• All Alarms are reported back to the DbManager and presented in a dedicated window with descriptor.
  Events and Alarms are held locally in the TDM32 for access via DbManager.
• G.703 Alarms
  AIS and LOS
• V.35/X.21 Alarms
  On loss of a Rx control signal
  Control signal status also visible via DbManager
• Recovered Clock Alarm
  Should the recovered clock move from its long-term stability by
  a user-defined amount (in parts per billion), PacketBand will
  generate an Alarm.
• Jitter Buffer Under-Run
  If the jitter buffer under-runs, indicating a service-affecting
  change in the performance of the packet network, PacketBand
  can be configured to generate an Alarm
• Loop-Backs
  Loops can be placed on the TDM port in either direction and
  at the Ethernet level.
• Pings
  PacketBand generates Ping/Trace Route and responds to Ping
  and UDP Echo requests. PacketBand can be used to Ping
  local devices on the customer LAN to help identify local
  failures and assist with fault-finding.
• “Sniffer” port
  The second Packet port on PacketBand can be configured as
  a “sniffer” port duplicating TX and/or RX packets on the
  network Packet Port. This is a very useful diagnostic tool.
• Boot Test
  Internal test on power-up with results visible via DbManager.

Graphs

DbManager and PacketBand provide several network monitoring tools available with graphical out-put:

• Maximum, minimum and average jitter buffer usage over time. This useful screen shows how the network and link are performing. Particularly useful information includes Lost and Late packets and jitter buffer usage figures.
• Average network jitter over time. A graphical representation showing Minimum, Maximum and Average buffer usage which provides important information on network performance.
• Recovered clock movement over time. This graph shows frequency stability and the status of the acquiring clock.

These are invaluable tools for optimising PacketBand and for ascertaining information on network performance. Together these statistics, which are updated for each Logical Link every 10 seconds, gives accurate and invaluable information on the performance of the network and are vital when installing. The information also identifies whether the jitter buffer settings are correct and if the jitter buffer can be reduced to remove any unnecessary latency.

Software/Firmware Updates

• New software can be loaded via the DbManager to PacketBand- TDM32. New software is loaded to the off-line sector of Flash and is confirmed via a CRC. Users can switch to the new software at any time.

Power

• PacketBand-TDM32A can be powered by a single AC or DC supply and optionally be fitted with dual ‘hot-swappable’ units for resilience. Any combination of PSUs is possible.
• The PacketBand-TDM32 is a resilient, compact and highly-flexible central-site or larger-site E1 T1 over Ethernet/IP solution. Apart from the absolutely key ability to extract clocks across the packet network very accurately, it has a large number of features which will prove to be invaluable once installed “in the real world”.

Specifications

Clock Recovery
Advanced algorithms tuneable for different
network characteristics as standard.
Capable of exceeding G.823 Synchronous
Interface requirements (subject to network
performance)

E1/T1 Card
16 x RJ45 connectors
Presents as DCE (crossed cable for DTE)
1 x LED with various states per interface
Support for E1 and T1 on a per-port basis.

E1
120 Ohm
75 Ohm unbalanced via converter cable
G.703 unstructured
G.704 channelised
ITU G.706
Selectable CRC/CRC4
HDB3 encoded
Transparent to user signalling

T1
100 Ohm
Unframed 1.544Mbps
Framed 1.536Mbps (robbed-bit)
ESF or D4 selectable
B8ZS or AMI selectable
Transparent to user signalling

C. V.35/X.21 Card
16 x HDMI sockets
Various cable adaptors available
Specify V.35 or X.21 in blocks of 4 ports
Specify above blocks as DCE (gives clock) or
DTE (receives clock)

V.35
Tx, Rx, TxClock, RxClock, ExternalClock,
RTS, CTS, DSR, DCD, DTR
Cable available as “flying lead”, MRAC
or RS530 25-way “D”.

X.21/V.11
Tx, Rx, S (clock), C, I
Cable available as “flying lead” or
15-way “D”.

Ethernet Card
Standard card
1 x standard SFP cage
SFP “enabled” warning LED
Default to 1GE
Options for 10/100 and single fibre
modules

2 x RJ45 UTP ports
10/100/1GE
Auto-sensing
Optional card
As above plus second SFP cage
E. Terminal Card
Standard card
1 x RJ12 asynchronous control port.
For use by DbLite/DbManager
[Remote management access also
available via Ethernet LAN/WAN]
Speeds to 115kbps.
Dry contact Alarm Relay. Pins as below
1 x RJ12 alarm port.
Dry-contact alarm relay: “Common”
pin 5; “normally open” 6; “normally
closed” 4
Optional card
As above plus
2 x RJ45 external clock inputs –
2Mbit square wave or HDB3
Optional card
As above plus
2 x BNC external clock inputs – 10MHz
F. Oscillator Performance*

Standard
Hold-over 24hrs 15ppb
Aging per day 10ppb
Temperature Stability 12ppb
Standard (from March ‘09)
Hold-over 24hrs 4ppb
Aging per day 0.5ppb
Temperature Stability 14ppb

Oven
Hold-over 24hrs 10ppb
Aging per day 0.3ppb
Temperature Stability 10ppb

* Figures based on typical parts and performances.
Individual oscillators may vary slightly either way.
Temperature Stability range -5DegC to +70DegC
assumes 20 minutes from power on. Aging and holdover
at constant temperature

Power Supplies
TDM32 supports 1 or 2 supplies these are
hot swappable to ATCA. 1 Supply can
power a fully populated chassis.

AC
Auto-sensing 96VAC – 240VAC
Max consumption 0.2A RMS @230VAC

DC
4mm terminal Block
36VDC tp 57VDC
1.2A max

IP & MAC Address
Single MAC address, IP address, subnet mask
and default gateway
Support for DHCP

Configuration
Held in non-volatile memory

Real-Time Clock
For time-stamping Events and Alarms
K. Dimensions and Environment
Metal chassis and front/rear panels
W – 225; D – 320 (300 from mounting); H-
88mm
Weight – 10.5Kg max
Standard operating temperature -20°C to
+50°C radiated cooling
Humidity 10-90% non-condensing
Optional cooling fans for 60°C

Maintenance
There are no serviceable parts or
maintenance required
Real-time battery-backed clock life in excess
of 7 years.

Approvals
EMC
EN55022:1988
EN55014:1988
EN61000-3-2/3:1995
AS/NZ CISPR22:2000
FCC Part 15(B)
CE marked
RoHS compliant

Safety
EC EN60950-1:2002
ACA TS001:1997
ACS/NZ60950:2000
AS/NZ3260:1993
IEC950

Telecomms (optional)
8 port E1/T1 card
TBR12/TBR13
TBR4/TBR3
TIA/E1A-1S/968
TNA117
AS-ACIF S006/S016