The DS34S132 evaluation kit (EV kit) is an easy-to-use
EV kit for evaluating the DS34S132 32-port TDM-overpacket (TDMoP) IC. The EV kit is a stand-alone system
with a TDMoP chip, local oscillator, local control processor, memory, external E1/T1 LIUs and framers, power
supply, and user interface software included in a 2.5
RU enclosure. The EV kit is controlled over an RS-232
serial link from an external ASCII terminal (typically using
terminal emulation software running on a PC) or through
a telnet session. The ASCII user interface is menu driven
and hierarchical for easy use. The behavior and performance of the TDMoP IC can be evaluated with a single
EV kit where the Ethernet signal is looped back to the kit,
or with two EV kits configured as separate end points.
EV Kit Contents
DS34S132 EV Kit System
TDMoP IC Daughter Card (Factory Installed)
MPC8313 CPU Daughter Card (Factory Installed)
User Interface Software (Factory Installed)
Ordering Information
PARTTYPE
DS34S132DKEV Kit
Features
S Complete System: Motherboard and Daughter
Cards in a Convenient 2.5 RU Enclosure
S Menu-Driven ASCII Text User Interface Software
S System Processor on a Separate Daughter Card
S Ethernet PHYs, I/O Jacks, E1/T1 Transceivers, and
Clock Sources on Motherboard
S Built-In AC Power-Supply Module
S Several Popular TCXO and OCXO Oscillators from
Which to Select and BNC Connectors for Lab
References
S 9-Pin Serial Jack to Connect an ASCII Terminal
for Configuration and Status
S System TCP/IP Stack for Configuration and Status
Over IP/Ethernet
S One RJ45 Ethernet Jack for Connection to the
Ethernet Network
S One RJ45 Jack for Each E1/T1 Port
S RJ45 External Clock Input Jack
S BNC Common Clock Input Jack
S BNC Reference Clock Input Jack
S 16-Bit CPU Interface to TDMoP IC
TDMoIP® Evaluation System with No Lid
TDMoIP is a registered trademark of RAD Data Communications, Ltd.
For pricing, delivery, and ordering information, please contact Maxim Direct
at 1-888-629-4642, or visit Maxim’s website at www.maximintegrated.com.
Three operating modes for E1/T1 are supported:
unframed, framed, and framed-with-CAS. Bundles consisting of carrying entire TDM data streams or selected
TDM time slots are transported over the network based
on IP/MPLS/MEF addressing.
VLAN tagging and priority labeling are supported,
according to 802.1p and Q. The type of service (ToS) of
outgoing IP packets is user-configurable.
Synchronization between TDM interfaces is maintained
by deploying advanced clock distribution mechanisms.
The clocking options include internal, loopback, recovered clock (either adaptive or common clock), or an
externally provided E1/T1 station clock.
The TDMoP IC is connected to 32 E1/T1 transceivers
(four DS26518s) on the motherboard to complete the
TDM-to-packet path.
Note: In the following sections, software-related items
are identified by bolding. Text in bold refers to items
within the terminal emulator menu system. Text that is
bold and underlined indicates user input.
1) Connect cables as shown in Figure 1-2.
2) Connect the EV kit to a PC equipped with ASCII terminal emulation software (e.g., Windows HyperTerminal
or PuTTY).
3) Configure the BERT to send a pseudorandom pattern
over E1 framed.
4) Power-up both DS34S132 EV kits.
5) Follow the initialization sequence as noted in 3.2 User
Interface Software (this is copied below for conve-
nience).
a. Set the port parameters of the control terminal
PC to 115.2kbps, 8 bits/character, 1 stop bit, no
parity. If available, set the terminal emulator to
ANSI VT100 emulation (for optimal view of system
menus).
b. At the end of the initialization and self-test, system
software detects the part number of the TDMoP IC
on the internal daughter card and displays it on
the terminal screen as:
login:
The login ID is target and the password is pass-
word. After giving the password, the screen
appears as:
~ $
Write the following commands in sequence as
shown:
~ $ su
~ $ password: root
~ $ ./ins132
~ $ ./top32App
The Main Configuration (S132) menu is dis-
played in the terminal.
6) Master DS34S132 EV kit configuration (at the Main Configuration (S132) menu) (this configures the
device for E1 operation, which is the default):
a. Select 2. General Configuration.
b. Select 3. Source IP 1.
Windows is a registered trademark of Microsoft Corp.
8 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
c. Set to 10.10.10.4.
d. Type s to save.
e. Press ESC to return to Main Configuration (S132)
menu.
f. Select 3. Interface Configuration.
g. Select 1. Frame Type, set to Unframed.
h. Select 7. Clock Source, set to Loopback.
i. Select 11. IF Type, set to Unbalanced.
j. Type s to save.
k. Press ESC to return to the Main Configuration
(S132) menu.
l. Select 4. Bundle Configuration.
m. Select 1. Bundle Type, set to SAToP.
n. Select 2. Assign this Bundle to PCM port, set to 1.
o. Select 6. TX Bundle Number, set to 1.
p. Select 7. RX Bundle Number, set to 1.
q. Select 10. Destination IP Address, set to
10.10.10.5.
r. Select 22. Clock Recovery, set to No.
s. Select 36. Size in Bytes, set to 1280 (E1 payload
size) .
t. Type s to save.
u. Press ESC to return to the Main Configuration
(S132) menu.
7) Slave DS34S132 EV kit configuration (at the Main Configuration (S132) menu):
a. Select 2. General Configuration.
b. Select 3. Source IP 1.
c. Set to 10.10.10.5.
d. Type s to save.
e. Press ESC to return to the Main Configuration
(S132) menu.
f. Select 3. Interface Configuration.
g. Select 1. Frame Type, set to Unframed.
h. Select 7. Clock Source, set to Recovery.
i. Select 11. IF Type, set to Unbalanced.
j. Type s to save.
k. Press ESC to return to the Main Configuration
(S132) menu.
l. Select 4. Bundle Configuration.
m. Select 1. Bundle Type, set to SAToP.
n. Select 2. Assign this Bundle to PCM port, set to 1.
o. Select 6. TX Bundle Number, set to 1.
p. Select 7. RX Bundle Number, set to 1.
q. Select 10. Destination IP Address, set to
10.10.10.4.
r. Select 22. Clock Recovery, set to Yes.
s. Select 36. Size in Bytes, set to 1280 (E1 payload
size).
t. Type s to save.
u. Press ESC to return to the Main Configuration
(S132) menu.
8) This completes the configuration of both boxes, and
packets should be flowing in both direction over the
Ethernet link.
Verify setup is operational without errors.
1) Check the BERT for errors.
2) Check the DS34S132 EV kit performance monitors
(on either the master or the slave).
a. From the Main Configuration (S132) menu, select
8. Performance (PM).
b. Select 1. Ethernet Performance.
c. Line 1. displays Correct Bytes (RX) and Correct
Bytes (TX). These two numbers should match.
d. Press ESC to return to the Performance (PM)
menu.
e. Select 3. Bundle Performance.
f. It prompts Please enter the Bundle ID:, enter 1.
g. Lines 1. and 2. report Correct Frames Tx to LAN
and Correct Frames Rx from LAN. These two
values should match.
1.5 Functional Description
1.5.1 Interfaces
E1. The E1 interface complies with the following stan-
dards: ITU-T Rec. G.703, G.704, G.706, G.732, and
G.823. The E1 framers support unframed (pass-through),
framed, and framed-with-CAS. Long-haul/short-haul
options can be selected by configuration.
T1. The T1 interface complies with the following standards: AT&T TR-62411, ITU-T Rec. G.703, G.704, ANSI
T1.403, and G.824. The T1 framers support unframed
(pass-through), SF, and ESF.
9Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Ethernet Uplink. The Ethernet uplink interface complies with the following standards: IEEE 802.3, 802.3u,
and 802.1p and Q. This interface is a standard
100/1000BASE-T full-duplex Ethernet port with autonegotiation support. The EV kit supports VLAN tagging
and priority. A different VLAN can be configured for each
bundle. The data stream coming from the E1/T1 interfaces is encapsulated into IP/MPLS/MEF packets and
transferred over the Ethernet port, and vice versa. When
using IP, a destination IP address should be configured
for each bundle. When using MPLS, a bundle should be
configured with an MPLS label.
Ethernet Management. The local Ethernet management
interface enables the connection of a software debugger
to the DS34S132 EV kit CPU. The interface is a standard
RJ45 + MAGNETIC
10/100/1000
ETHERNET
RJ45/1, 2
RJ45/3, 4
RJ45/5, 6
RJ45/7, 8
RJ45/9, 10
RJ45/11, 12
RJ45/13, 14
RJ45/15, 16
RJ45/17, 18
RJ45/19, 20
RJ45/21, 22
RJ45/23, 24
RJ45/25, 26
RJ45/27, 28
RJ45/29, 30
RJ45/31, 32
RJ45/E1/T1
CLK
RJ45/ETH
MNG
DB9
THERMINAL CONNECTOR
ETHERNET
UPLINK
COMMON
CLOCK
REFCLK
TCXO
E1/T1
OCTAL
TRANSCEIVER
DS26518 #1
E1/T1
OCTAL
TRANSCEIVER
DS26518 #2
E1/T1
OCTAL
TRANSCEIVER
DS26518 #3
E1/T1
OCTAL
TRANSCEIVER
DS26518 #4
STATION CLOCK
E1/T1
MCLK
DS3100
CLOCK SYNC
OSC
LIUCLK
PORT 31, 32 CPLD
CLOCK CPLD
TCXOOCXO
10/100/1000BASE-T Ethernet port with autonegotiation
support that complies with the IEEE 802.3 standard.
E1/T1 External Clock. The E1/T1 external clock port
enables connection of an external clock source to support the station clock mode.
Common Clock. The common clock port enables connection of a common clock source through LVTTL input.
It supports frequencies of up to 25MHz. The common
clock is used for differential mode clock recovery.
Reference Clock. The reference clock port allows for an
external source to be used for TDM clock recovery from
the Ethernet link.
RS-232 Control. The RS-232 control interface enables
connection an ASCII terminal for configuring the EV kit.
DDRCLK
AND
ETHCLK
VOLTAGE SUPPLY
3V, 2.5V, 1.8V
CMNCLK
REFCLK
EXTCLK[0,1]
TDM CLOCK/DATA
TDM CLOCK/DATA
TDM CLOCK/DATA
TDM CLOCK/DATA
HEADER
A/D BUS
DDR
SDRAM
DS34S132
DAUGHTER CARD
FPGA
POWER QUICC II PRO
MPC8313 DAUGHTER
ETHERNET PHY
10/100/1000
RS-232 DRIVER
CONNECTORS
FOR
DEBUG
SYSCLK
CARD
SMC
DDR2
SDRAM
MPC8313
OSC
Figure 1-3. DS34S132 EV Kit Block Diagram
10 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
E1/T1
E1/T1
E1/T1
E1/T1
E1/T1
E1/T1 - 1
E1/T1 - 2
E1/T1 - 3
E1/T1 - 4
E1/T1 - 32
EXT-CLKCONTROLCOMM-CLK
E1/T1 EXTERNAL
CLOCK
COMMON
CLOCK
Figure 1-4. Representation of DS34S132 EV Kit Interfaces
TDATTSER
E1/T1
FRAMER
RSER
TSIG
RSIG
RSYSCLK
TCLK
TSYNC
RSYNC
RFSYNC
RCLK
RDAT
TSIG
RSIG
DS34S132
TCLKO
TSYNC
RSYNC
RCLK
Figure 1-5. E1/T1 Per Port Clock Distribution
1.5.2 Modes of Operation
The EV kit modes of operation for E1/T1 are the following:
• Unframed
• Framed
• Framed-with-CAS
In unframed mode, the entire incoming bit stream from
each interface is encapsulated into IP/MPLS/MEF-over-
ETHERNET
REF-CLK
REFERENCE
CLOCK
RS-232
CONTROL
ETH-UPLINK
ETH-MNG
ETHERNET
MANAGEMENT
Ethernet packets without regard for frame alignment.
This option provides clear channel end-to-end service.
In framed and framed-with-CAS modes, the incoming
bit stream is regarded as a sequence of n x 64kbps
channel groups. This mode allows fractional or full E1/
T1 transmission.
1.5.3 Timing Modes
The E1/T1 transmit (Tx) clock operates in several timing
modes to provide maximum flexibility for the EV kit TDM
interface. The available timing modes are the following:
• Loopback Timing: The clock is derived from the
received TDM clock.
• Recovered Clock Timing: The clock is regener-
ated from the ETH network using the clock recovery
mechanism.
• Internal Clock Timing: The clock is provided by an
internal oscillator.
• E1/T1 Station Clock Timing: The clock is provided
by the external E1/T1 clock source.
These selections are accessed through the user interface software. See 4.3 Configuring TDM Interfaces for
more information. Figure 1-5 shows the TDM backplane
wiring for one E1/T1 port of the system (there are 32 total
E1/T1 TDM ports).
11Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
1.5.4 Ethernet Clock Recovery
The DS34S132 uses either CMNCLK or REFCLK pins
as its reference clock input to recover the TDM timing
from the Ethernet source using either “Adaptive Clock
Recovery” or “Differential Clock Recovery.” These clock
inputs are sourced from the on-board CPLD and are
user-selectable from TCXOs, an OCXO, an E1/T1 station
clock, or an external reference on one of the BNC jacks
(CMNCLK or REFCLK BNC jacks).
1.5.5 Motherboard
The motherboard consists of four octal T1/E1 transceivers, a timing synthesizer (DS3100 clock sync), various
TCXOs, an OCXO, two CPLDs, and an FPGA.
The DS3100 clock sync provides clock sources to the
CPLD, which acts as a mux to allow software selection of
the various clock sources to the DS34S132.
The FPGA provides CPU timing signals to the devices
on the address/data bus. One CPLD provides userselectable clock sources and the other CPLD breaks out
ports 31 and 32 of the TDM backplane for connection to
an alternative LIU (e.g., the T3/E3 LIU, DS3150).
1.5.6 CPU Board
Figure 1-6 shows the CPU and peripherals block dia-
gram. The CPU clock is obtained from an on-board local
crystal oscillator.
The flash device has a 64Mb memory capacity. The
flash is used for storage of software and configuration
data that should not be lost when system power is off.
The RAM memory consists of a DDR2 SDRAM device
with a capacity of 512Mb. The CPU provides 16-bit data
bus synchronous with the address bus. The CPU can
accept and prioritize multiple external interrupts. One
interrupt is connected to the TDMoP IC daughter card.
MPC8313’s SMC communication port, used as a UART,
is connected through an RS-232 transceiver to the DB9
control port on the front panel of the system. An ASCII
terminal connected to the control port can be used to
configure the system. The MPC8313’s Ethernet communication controller is connected through an Ethernet
PHY to the Ethernet management port (MNG) on the front
panel of the system.
ETH PHY
ETH
CONTROLLER
MPC8313
TXD
SERIAL Tx/Rx
Figure 1-6. CPU and Peripherals Block Diagram
12 Maxim Integrated
RXD
SMC
FLASH
A/D BUS
INCLUDING
BOOT
ETH PHY
DDR2
DS34S132 Evaluation Kit
Evaluates: DS34S132
1.5.7 TDMoP IC Daughter Card
The TDMoP IC daughter card is populated with a Maxim
TDMoP IC (DS34S132) and a 512Mb DDR SDRAM. The
core voltage is 1.8V for the TDMoP IC. I/Os are supplied
with 3.3V. In addition, 2.5V is made from the 3.3V power
supply through an on-board linear regulator.
1.5.8 Bundles
A bundle is defined as a stream of bits originating from
one TDM interface that are transmitted from a TDMoP
source device to a TDMoP destination device. For
example, a bundle can comprise any number of 64kbps
time slots originating from a single E1 or T1 interface.
Bundles are single-direction streams, frequently coupled
with bundles in the opposite direction to enable fullduplex communications. More than one bundle can be
transmitted between two TDMoP edge devices. Each
bundle transmitted or received by the EV kit uses one of
the following payload type methods:
Up to 256 bundles are supported. Each TDMoP bundle/
connection can be assigned to one of the payload type
machines or to the CPU.
1.5.9 Packet Formats
DA
MAC_addr/
BROADCAST/
MULTICAST
*THE UDP SOURCE PORT NUMBER IS USED AS THE BUNDLE NUMBER DESIGNATOR, WHILE UDP DESTINATION PORT NUMBER IS SET TO 0x085E (2142), THE USER PORT NUMBER
ASSIGNED BY IANA TO TDMoIP.
SA
VLAN TAG
UP TO 2 TAGS
ETH TYPE
IP
IP HEADER
DEST. IP = IP_Add1/
IP_Add2
Figure 1-7. TDMoIP Packet with VLAN Tag
UDP* OR L2TPv3
HEADER
Bundle no. = Bundle_Identifier/
OAM_bundle_num
CONTROL
WORD
PAYLOAD TYPE
HDLC/OAM/SAToP/
CESoPSN
CRC32
DA
MAC_addr/
BROADCAST/
MULTICAST
*A STACK OF UP TO THREE MPLS LABELS IS SUPPORTED, WHERE THE INNER LABEL IS USED AS THE BUNDLE NUMBER DESIGNATOR.
SA
VLAN TAG
UP TO 2 TAGS
ETH TYPE
MPLS
UP TO 2 MPLS LABELS
OPTIONAL
MPLS LABEL*
Bundle no. = Bundle_Identifier/
OAM_bundle_num
Figure 1-8. TDMoMPLS Packet with VLAN Tag
DA
MAC_addr/
BROADCAST/
MULTICAST
SA
VLAN TAG
UP TO 2 TAGS
ETH TYPE
MEF
ECID = Bundle_Identifier
Figure 1-9. TDMoMEF Packet with VLAN Tag
CONTROL
WORD
CONTROL
WORD
PAYLOAD TYPE
HDLC/OAM/SAToP/
CESoPSN
PAYLOAD TYPE
HDLC/OAM/SAToP/
CESoPSN
CRC32
CRC32
13Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
1.5.10 TDMoP Mappings
To transport TDM data through packet switched networks, the EV kit encapsulates it into Ethernet packets,
as shown in Figure 1-10. The UDP/IP, L2TPv3/IP, MEF,
and MPLS headers, as well as the TDMoIP control word,
are detailed in the packets formats section of Maxim's
TDMoP IC data sheets.
1.5.11 Payload Type Machines
SAToP. The SAToP payload type machine converts
unframed E1/T1 or serial data flows into IP, MPLS, or
Ethernet packets and vice versa according to ITU-T
Y.1413, MEF 8, MFA 8.0.0, and IETF RFC 4553.
CESoPSN. The CESoPSN payload type machine converts structured E1/T1 data flows into IP, MPLS, or
Ethernet packets and vice versa with static assignment
PREAMBLE
START OF FRAME
DELIMITER
1 BYTE
DESTINATION
ADDRESS
6 BYTES
SOURCE
ADDRESS
6 BYTES
of time slots inside a bundle according to ITU-T Y.1413,
MEF 8, MFA 8.0.0, and IETF RFC 5086.
HDLC. The HDLC payload type machine, for efficient
transfer or termination of frame-based traffic, provides an
HDLC controller for each bundle assigned to it. It supports 2, 7, and 8-bit time-slot resolution (i.e., 16, 56, and
64kbps, respectively), as well as N x 64kbps bundles (N
= 1 to 32). This is useful in applications where HDLCbased signaling interpretation is required (such as ISDN
D-channel signaling termination, V.51/2, or GR-303), or
for trunking packet-based applications (such as frame
relay), according to IETF RFC 4618.
1.5.12 OAM
OAM is used to detect a valid connection. It can be
set to enable or disable. When a bundle in the EV kit is
VLAN
TAG1
4 BYTES
UDP/IPv4
HEADER
26 BYTES
UDP/IPv6
HEADER
48 BYTES
OR
OPTIONAL
VLAN
TAG2
4 BYTES
TYPE
2 BYTES7 BYTES
OPTIONAL
RTP
HEADER
12 BYTES
DATA AND
PADDING
46–1500 BYTES
TDMoIP
CONTROL WORD
4 BYTES
FRAME CHECK
SEQUENCE
4 BYTES
TDMoIP
PAYLOAD
OPTIONAL
OR
L2TPv3/IPv4
HEADER
24, 28, OR 32 BYTES
OR
L2TPv3/IPv6
HEADER
44, 48, OR 52 BYTES
OR
MEF
HEADER
4 BYTES
OR
MPLS
HEADER
4, 8, OR 12 BYTES
TDMoIP
CONTROL WORD
4 BYTES
OPTIONAL
RTP
HEADER
12 BYTES
TDMoIP
PAYLOAD
Figure 1-10. TDMoIP Encapsulation in an Ethernet Frame
14 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
assigned with OAM, TDMoIP traffic is not sent immediately. First, a TDMoIP echo request packet is sent once
every five seconds. This continues until a valid echo
reply arrives. The remote TDMoP system receives the
echo request packet and sends a valid echo reply only
if all parameters in the echo request match its local
configuration. When a valid echo reply arrives, the transmitting echo request message stops, and TDMoP traffic
flow begins at full rate for that bundle. If there is a break
in the connection, the initialization process begins again.
Refer to the VCCV OAM and UDP/IP-specific OAM sections of the DS34S132 IC data sheet for details of the
OAM payload types.
1.5.13 Packet Delay Variation
Packets are transmitted at set intervals. Packet delay
variation (PDV) is the maximum deviation from the
nominal time the packets are expected to arrive at the
receiving device. The TDMoP IC controls a buffer that
compensates for the deviation from the expected packet
arrival time to prevent buffer overflow or underflow.
Packet delay variation is an important network parameter. Large PDV (exceeding the jitter buffer configuration)
causes receive buffer overflow or underflow and errors
in the recovered E1/T1 signal. To compensate for large
PDV, the packet delay variation tolerance (PDVT) (jitter)
buffer should be configured to a higher value.
1.5.13.1 Differential Time
The TDMoP IC is equipped with a PDVT buffer. The PDVT
buffer is filled by the payload of incoming packets and
emptied to fill the outgoing E1/T1 or serial data stream.
The jitter buffer depth is defined by the Rx_max_buff_size
parameter. When the jitter buffer level reaches the value
of Rx_max_buff_size, an overrun situation is declared.
The differential time parameter defines the amount of data
to be stored in the jitter buffer to compensate for network
delay variation. This parameter has two implications:
• Thedataarrivingfromthenetworkisdelayedbydifferential time before it is sent to the TDM interface.
Differential time should be smaller than Rx_max_buff_
size. Also, the difference between Rx_max_buff_size and
differential time should be larger than the time required to
reconstruct a packet (otherwise an overrun can occur).
Configuring the jitter buffer parameters correctly avoids
underrun and overrun situations. Underrun occurs when
the jitter buffer becomes empty (data is being written to
the buffer more slowly than data is being read out of the
buffer). Overrun occurs when the jitter buffer is full and
there is no room for new data (data is being read out of
the buffer more slowly than data is being written to the
buffer). See Figure 1-12.
Table 1-1 shows the maximum configurable value for
10/100/1000BASE-TX half/
full-duplex port with autonegotiation support
120I or 100I
LVTTL input (square wave
0/3.3V)
Off when line is not connected;
On when line is connected
Off when no activity;
On when a frame is being
transmitted or received on
the line
On when there is no data
in Rx
On when loss of frame is
detected
100 to 240V AC, 50Hz to
60Hz
2. Installation
2.1 Introduction
The EV kit is delivered completely assembled and
ready to use. Configure the EV kit using an ASCII
terminal connected to the EV kit control port as
described in 3. Operation. If problems are encountered, see 5. Troubleshooting and Diagnostics for
test and diagnostics instructions.
2.2 Making Internal Settings
The EV kit contains jumpers and switches that provide
preliminary configuration of the device. It should not
be necessary to change these settings from the factory
default. If it becomes necessary to change them, follow
these instructions:
1) Open the EV kit enclosure.
2) Set jumpers or switches located on the motherboard
or on the daughter card.
3) Close the EV kit enclosure.
2.2.1 Opening the DS34S132 EV Kit Case
Open the EV kit case to gain access. Caution: The EV
kit contains components sensitive to electrostatic
discharge (ESD). To prevent ESD damage, avoid
touching the internal components. Before moving the
jumpers, touch the EV kit frame.
To open the unit’s case:
1) Disconnect all cables from the EV kit.
2) Unscrew all the cover screws on the top and side
panels of the unit.
3) Remove the top cover by pulling it straight up.
2.2.2 Setting the Internal Jumpers
Internal jumpers are located on the motherboard and the
CPU daughter card. To set the motherboard jumpers:
1) See Figure 2-1 to locate internal jumpers on the
motherboard PCB.
2) Set the motherboard jumpers while referring to
Table 2-1.
To set the CPU daughter card jumpers:
1) See Figure 2-2 to locate internal jumpers on the
daughter card.
2) Set the daughter card jumpers referring to Table 2-2.
17Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
SW2
Figure 2-1. Motherboard Jumper Locations
JMP1
JMP2
JMP3
DS34S132 EV KIT DAUGHTER CARD
SW1
CPU DAUGHTER CARD
JMP30
SW5
JMP34
Table 2-1. Motherboard Jumper and Switch Settings
JUMPERFUNCTIONPOSSIBLE SETTINGS
JMP1Controls DDRCLKPHY clock or BNC for DDRPHY clock
JMP2Selects clock for MACPHY clock or BNC for MACUnconnected
JMP3Selects clock for MACPHY clock or not for MACPHY clock
JMP30PWR ONBypasses SW5Connected
JMP34DS26518s’ MCLK selector
SW1Resets DS34S132 EV kitResets DS34S132 daughter cardN/A
SW2Board resetResets motherboardN/A
SW5Powers down boardThis powers down the board if JMP30 is not connectedN/A
Note: The motherboard includes additional factory-set jumpers and switches that must not be changed by the user.
18 Maxim Integrated
Selects between LIUCLK output of DS34S132 and
2.048MHz oscillator
FACTORY
SETTING
Oscillator
DS34S132 Evaluation Kit
Evaluates: DS34S132
J26
S2
MPC8313
S1
S3S4
Figure 2-2. CPU Daughter Card Jumper Locations
Table 2-2. CPU Daughter Card Jumper Settings
JUMPERFUNCTIONPOSSIBLE SETTINGSFACTORY SETTING
J26SYS_CLK_IN selectionBNC or oscillatorOscillator
S1Reset CPU cardN/AN/A
S2UnusedN/AN/A
S3CPU control switchesDo not changeAll on
S4CPU control switchesDo not changeAll off
Note: The CPU board includes additional factory-set jumpers and switches that must not be changed by the user.
19Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
2.3 Connecting to the Ethernet Network
Equipment
The EV kit is connected to Ethernet network equipment
through the 8-pin RJ45 port designated UPLINK. See
Appendix A. Connector Wiring for the connector pin
arrangement. Connect the EV kit to the Ethernet network
equipment using a standard straight UTP cable. See
Figure 2-3.
Figure 2-3. UPLINK Connector
2.4 Connecting to the TDM Equipment
The EV kit is connected to the TDM equipment through
T1/E1 balanced RJ45 ports. See Appendix A. Connector
Wiring for the connector pin arrangement. Connect the
EV kit to the TDM equipment using standard straight E1/
T1 cables. See Figure 2-4.
Figure 2-4. T1/E1 Connectors
20 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
2.5 Connecting to the Clock Sources
2.5.1 Connecting to the External Clock Source
The EV kit is connected to an external BITS clock source
through a balanced RJ45 connector designated EXT CLK. See Appendix A. Connector Wiring for the connec-
tor pin arrangement. See Figure 2-5.
Figure 2-5. EXT CLK Connector
2.5.2 Connecting to the Common Clock Source
The EV kit is connected to a common clock source
through an unbalanced BNC connector designated
COMM CLK. Connect the EV kit to the common clock
source using a using a 50I coaxial cable. The input
signal must be LVTTL (square wave with 0V/3.3V levels).
See Figure 2-6.
Figure 2-6. COMM CLK Connector
21Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Figure 2-7. REF CLK Connector
Figure 2-8. CONSOLE Connector
2.5.3 Connecting to the Reference Clock Source
The EV kit is connected to a reference clock source
through an unbalanced BNC connector designated
REF CLK. Connect the EV kit to the reference clock
source using a using a 50I coaxial cable. The input
signal must be LVTTL (square wave with 0V/3.3V levels).
See Figure 2-7.
2.5.4 Connecting to an ASCII Terminal
The EV kit is connected to an ASCII terminal through a
9-pin, D-type, female connector designated CONSOLE.
See Appendix A. Connector Wiring for the connector pin
arrangement. See Figure 2-8.
22 Maxim Integrated
To connect to an ASCII terminal:
1) Connect a serial cable with a male 9-pin, D-type connector to the CONSOLE connector.
2) Connect the other end of the serial cable to an ASCII
terminal.
3. Operation
This section provides a detailed description of the
front panel indicators and their functions, and explains
the EV kit configuration using an ASCII terminal. See
4. Configuration for detailed explanations of param-
eters on the menus.
DS34S132 Evaluation Kit
Evaluates: DS34S132
3.1 Front Panel Indicators
The unit’s LEDs are located on the front panel (see
Figure 3-1). Table 3-1 lists the functions of the EV kit LED
indicators.
3.2 User Interface Software
3.2.1 Using the Control Port and an ASCII Terminal
The EV kit can be configured and monitored using an
ASCII terminal connected to the control port on the EV
kit front panel. The control port is a V.24/RS-232 asynchronous DCE port terminated in a 9-pin, D-type female
connector. The EV kit continuously monitors control
port signals from the ASCII terminal and immediately
responds to any input string received through this port.
To access the user interface software using an ASCII
terminal:
1) Ensure all DS34S132 EV kit cables and connectors
are properly connected.
2) Connect the DS34S132 EV kit to a PC equipped
with ASCII terminal emulation software (for example,
Windows Hyper Terminal or PuTTY).
3) Set the port parameters of the control terminal PC to
115.2kbps, 8 bits/character, 1 stop bit, no parity. If
available, set the terminal emulator to ANSI VT100
emulation (for optimal view of system menus).
4) At the end of the initialization and self-test, system
software detects the part number of the TDMoP IC
on the internal daughter card and displays it on the
terminal screen as:
login:
The login ID is target and the password is password.
After giving the password, the screen shows:
~ $
Write the following commands in sequence as shown:
~ $ su
~ $ password: root
~ $ ./ins132
~ $ ./top32App
The Main Configuration (S132) menu is displayed in
the terminal.
top32App can be executed again after exiting the
Main Configuration (S132) menu.
Figure 3-1. DS34S132 EV Kit Front Panel
Table 3-1. DS34S132 EV Kit LEDs and Controls
NAMETYPEFUNCTION
LOSRed LEDOn: Loss of signal (LEDs on the left refer to the top port, LEDs on the right refer to the bottom port).
LOFRed LEDOn: Loss of E1/T1 synchronization has been detected.
LINKGreen LED
ACTYellow LED
Note: LINK and ACT are not shown in Figure 3-1.
On: Ethernet link is connected.
Off: Ethernet link is disconnected.
On: Data is being transmitted/received at the Ethernet interface.
Off: No data is being transmitted/received at the Ethernet interface.
23Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
3.2.2 Using Telnet Through the Ethernet
Management Port
The EV kit can be configured and monitored remotely
over an IP/Ethernet network. Currently, the DS34S132
only supports static IP (factory default is 10.16.34.18) so
the user needs to program the correct IP address. Use
the following steps to do this. Remember that the user
only needs to do this once.
To configure the static IP address of the DS34S132 EV
board:
1) Power the DS34S132 EV kit.
2) Connect the MNG port of the EV kit to the local IP/
Ethernet network.
3) Use an ASCII terminal connected as previously
described.
login:
The login ID is root and the password is also root.
After giving the password, the screen shows:
~ #
Write the following commands in sequence as shown
below:
~ # cd /etc/rc.d
/etc/rc.d # vi rc.conf
The user then needs to change the necessary param-
eters for ‘eth0’ (lines between ‘net interface 0’ and ‘net
interface 1’). Once complete, save and exit.
/etc/rc.d # reboot
To access the user interface software using a telnet session:
1) Power the DS32S132 EV kit.
2) Connect the MNG port of the DS34S132 EV kit to the
local IP/Ethernet network.
3) IP address was decided above.
4) On a PC is connected to the IP/Ethernet network, run
“cmd” to get a DOS-like text interface window.
5) At the command prompt, type telnet followed by the
IP address determined in step 3.
6) At the login prompt, type target. At the password
prompt, type password.
Write the following commands in sequence as shown
below:
~ $ su
~ $ password: root
~ $ ./ins132
~ $ ./top32App
The Main Configuration (S132) menu is displayed in
the terminal.
top32App can be executed again after exiting the
Main Configuration (S132) menu.
3.2.3 Choosing Options
To select a menu item, type the corresponding item
number and then press Enter. If the selected item leads
to another menu, the EV kit software displays the menu.
If the selected item is a configurable parameter, the
software displays descriptive text about the parameter
and then, for parameters with only a few possible settings, displays a numbered list of possible values (e.g.,
1: Enable, 2: Disable) and a prompt such as Please
enter your choice:. For parameters with many possible
values, the software displays descriptive text followed by
SW Version 1.0.0
Main Conguration (S132)
1. Precong Conguration
2. General Conguration
3. Interface Conguration
4. Bundle Conguration
5. Bundle Management
6. Restore Default Congurations
7. Alarms
8. Performance (PM)
9. Utilities
Please select item <1 to 9>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Figure 3-2. Main Configuration Menu
24 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
a prompt at which a value can be entered (e.g., Please
enter your clock rate:).
The selection or value entered for each parameter is
checked after pressing Enter, and only valid entries are
accepted. If an entry is invalid, the software displays a
prompt such as Please enter a valid choice: and gives
another opportunity to enter a valid selection number or
value. To navigate upward in the menu hierarchy toward
the main menu, press Esc.
3.2.4 Redisplaying the Current Menu
To redisplay the current menu, type r and press Enter or
simply press Enter.
3.2.5 Saving Changes
After changing the values of one or more parameters
in a configuration menu, type s then Enter to save the
changes and write them to the TDMoP IC. If changes are
not saved in each menu, attempts to change parameters in other menus may not behave as expected.
For example, changes in the Interface Configuration
menu must be saved before activities in the Bundle Configuration menu behave correctly, especially when
saving a bundle configuration.
4. Configuration
This section discusses the EV kit configuration menus
and explains their parameters:
• PreliminaryConfiguration
• ConfiguringGeneralParameters
• ConfiguringTDMInterfaces
Configuring E1 Interface
Configuring T1 Interfaces
• ConfiguringBundles
Configuring SAToP Bundles
Configuring CESoPSN Bundles
• DeletingBundles
• DisplayingActiveBundles
• RestoringDefaultConfigurations
4.1 Preliminary Configuration
For the convenience of the user, parameters that must
be configured, such as link type, TDMoIP and IP versions, and clock recovery statistics, are given in the
PreConfig Configuration menu. See Figure 4-1.
PreCong Conguration
1. Device Num (1 - 1) 1
2. Max. Bundles (1 - 256) 64
3. Link Type T1
4. Bundle Number ID Location Bundle Conguration Decides
5. UDP Port Check Yes
6. VCCV OAM Mask [0 - 4] 1
7. VCCV OAM Value 1000
8. MEF Ethernet Type 88D8
9. MEF OAM Type 889C
10. TDMoIP Port Number 1 85E
11. TDMoIP Port Number 2 85E
12. VLAN Inner Label 8100
13. VLAN Outer Label 9100
14. Oscillator Type OCXO (Stratum 3E)
15. Common clock Freq 19440000
16. Reference Clock Frequency 38880000
17. Reference Clock Frequency PPM Offset 0
18. Clock Recovery DSP File Name rom_code.asm.patch.txt
19. Driver Type Kernel Mode
Please select item <1 to 19>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Specifies the type of TDM interface (link); all TDM
interfaces on a TDMoP IC must be the same type
Defines location of the bundle identification
number
Indicates which of the 16 MSBs of the control
word are used to identify VCCV OAM packets; the
mask is active when one of the bits is set to 0
Indicates the value of the 16 MSBs of the control
word that identifies VCCV OAM packets
Ethertype for MEF packets; must be set to a value
greater than 0x5DC
Ethertype for MEF OAM packets; must be set to a
value greater than 0x5DC
Used to identify UDP/IP TDMoIP packets; its value
is compared to either UDP_SRC_PORT_NUM
or UDP_DST_PORT_NUM, according to Bundle
Number ID Location (above)
Any number from 1–256
Default: 64
E1, T1
Default: T1
1: Bundle configuration decides
(BCDR4)
2: Either UDP SRC or DST. port
3: Bundle in DST UDP PORT
4: Bundle in SRC UDP PORT
5: Combined SRC and DST UDP ports
Default: Bundle Configuration Decides
Yes, No
Default: Yes
0–4
Default: 1
0–0xFFFF
Default: 1000
0–0xFFFF
Default: 88D8
0–0xFFFF
Default: 889C
0–0xFFFF
Default: 85E
Used to identify UDP/IP TDMoIP packets; its value
TDMoIP Port Number 2
VLAN Inner Label
VLAN Outer Label
Oscillator Type
Common clock Freq
26 Maxim Integrated
is compared to either UDP_SRC_PORT_NUM
or UDP_DST_PORT_NUM, according to Bundle
Number ID Location (above)
Defines the tag protocol identifier (TPID) to use
when using VLAN tags
Defines the tag protocol identifier (TPID) to use
when using VLAN tags
The oscillator used as the clock recovery reference clock
The common clock frequency supplied in the differential mode clock recovery
Figure 4-2. General Configuration (Main Menu→General Configuration)
8. Wrong IP Discard
9. ARP My IP CPU
10. Not TDMoIP Type CPU
11. Not UDP Type CPU
12. OAM Packet CPU
13. Bundle Not Exist Discard
14. Max HDLC Frame Size[1 - 1800] 1468
15. Ethernet Rate & Duplex 100M_FDX, ANEG
16. OAM Conguration >
Please select item <1 to 14>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Please enter your choice:
27Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Table 4-2. General Configuration Parameter Descriptions
PARAMETERDESCRIPTIONPOSSIBLE VALUES
Source Mac Address 1Port local MAC address
Source Mac Address 2Second host MAC address.
Source IP 1Host IP address (see note).
Source IP 2Second host IP address (see note).
Default GatewayIP address of default gateway.
Specifies what to do with packets received from
Not Eth Type
ARP Wrong IP
Wrong IP
ARP My IP
Not TDMoIP Type
Not UDP Type
OAM PacketSpecifies what to do with TDMoIP OAM packets.
Bundle Not Exist
Max HDLC Frame Size
[1 - 1800]
Ethernet Rate & Duplex
OAM Configuration
Note: Source IP 1 and Source IP 2 can reside in different subnets. However, the IP mask is used for both source IPs. Either
Source IP 1 or Source IP 2 can be selected in the Bundle Configuration menu (see section 4.4 Configuring Bundles).
UPLINK port, where Ethertype does not match one of
the following: IP, MPLS, ARP, MEF, MEF OAM, or CPU.
Specifies what to do with ARP packets received from
UPLINK port, where IP is different from source IP.
Specifies what to do with packets received from
UPLINK port with IP different from all source IPs.
Specifies what to do with ARP packets received from
UPLINK port, where IP is identical to source IP.
Specifies what to do with packets received from
UPLINK port, where UDP destination/source port is not
TDMoIP.
Specifies what to do with packets received from
UPLINK port, where protocol is not UDP.
Specifies what to do with packets received from
UPLINK port, where bundle identifier is not one of the
identifiers assigned in the TDMoP IC.
Maximum size of HDLC packet in bytes (header and
FCS are not included).
If autonegotiation is enabled, rate and duplex must be
configured to a value equal or greater than the rate
and duplex mode of the network. If autonegotiation
is disabled, the rate and duplex must be configured
equal to the rate and duplex of the network.
Selecting this options causes the OAM Configuration
submenu to be displayed.
Up to 12 alphanumeric characters
Default: 08002E289D53
Up to 12 alphanumeric characters
Default: 08002E2896C0D
0.0.0.0 to 255.255.255.255
Default: 10.10.10.5
0.0.0.0 to 255.255.255.255
Default: 10.10.10.5
0.0.0.0 to 255.255.255.255
Default: 0.0.0.0
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Default: CPU
Discard: Drops these packets
CPU: Passes these packets to the CPU
Specifies OAM ID n (2 P n P 8). These IDs are bundle IDs for UDP/
IP-specific OAM. If the bundle ID of an incoming packet matches an
enabled OAM ID, the packet classifier in the TDMoP IC considers the
packet to be an OAM packet and discards or forwards it to the CPU as
specified by the OAM packet field described above.
4.3 Configuring TDM Interfaces
The number of TDM interfaces available depends on the
TDMoP IC on the daughter card. A DS34S132 has 32
TDM interfaces. The user interface software only allows
configuration of the number of TDM interfaces actually
supported by the installed IC.
To configure a TDM interface, select Interface Configuration from the Main Configuration (S132)
menu and enter the interface number at the prompt
(Figure 4-4). The Interface Configuration menu is then
displayed, either Figure 4-5 (E1) or Figure 4-6 (T1),
depending on the setting of the Link Type parameter in
the PreConfig Configuration menu.
Please select item <1 to 41>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Please enter your choice:
NOTE: THE SETTINGS FOR SOME PARAMETERS IN THIS CONFIGURATION MENU DETERMINE WHETHER OR NOT OTHER PARAMETERS IN THE MENU ARE
DISPLAYED. FOR EXAMPLE, IF RECOVERY CLK MODE IS SET TO AUTO, THEN ITEMS 13–25 AND 27–31 ARE NOT DISPLAYED BECAUSE THEIR VALUES ARE
IGNORED IN THAT MODE. THE PARAMETER DESCRIPTIONS IN TABLE 4-4 HAVE NOTES INDICATING THE NECESSARY CONDITIONS FOR A PARAMETER TO BE
DISPLAYED. SEE THE ACQUISITION SWITCH PARAMETER.
Unframed: Framer is configured to pass-through mode
Framing mode and operation mode for each con-
Frame Type
figuration.
Note: Before changing the E1 frame type, you
must close all bundles assigned to the link.
Determines the maximum attenuation of the
Rx Config Gain
Limit
receive signal that can be compensated for by
the E1 link receive path, to obtain the BER perfor-
mance required by the standards.
OOS Code TypeDefines what to send if an OOS state occurred.
and the operation mode is set to unframed.
Framed: The E1 framer is set for simple FAS/NFAS
framing and the TDMoP block is set to fractional.
Multiframe: The E1 framer is set to MF mode and the
TDMoP block is set to fractional with CAS.
Default: UnFramed
Long Haul: Maximum attenuation of 36dB.
Short Haul: Maximum attenuation of 10dB. This con-
figuration can actually improve the performance when
operating over relatively short line sections, especially
when operating over multipair cables. In such cables,
significant interference is generated by the signals
carried by other pairs, and therefore a weak desired
signal can be masked by the interference.
Default: Short Haul
Can also be applied to time slots transmitted
Data TX/RX OOS
[0 - 0xFF]
TX/RX OOS
Signal Mask
Clock Source
toward the E1 line when packet receive buffer
overrun or underrun occurs. In unframed mode,
OOS state results in AIS transmission. This is
applied when an LOS is detected at the E1 line,
or when packet receive buffer overrun or under-
run occurs.
Out-of-service signaling method. OOS signal is
sent in the Ethernet direction when loss of signal,
loss of frame, or AIS is detected at the E1 line.
The OOS signal is also sent toward the E1 line
when packet receive buffer overrun or underrun
occur.
Defines transmit clock source used by the inter-
face.
0–FF
Default: 7F
Space: Transmit CAS all 0s, when the Ethernet or TDM
link is down
Mark: Transmit CAS all 1s, when the Ethernet or TDM
link is down
Space + Mark: Transmit all 0s in CAS for the first 2.5s,
then switch to all 1s
Mark + Space: Transmit all 1s in CAS for the first 2.5s,
then switch to all 0s
Default: Space
Adaptive Recovery: Clock recovery regeneration from
UPLINK
LIU Loopback: T1 recovered receive clock is used as
the transmit clock
Global Adaptive Recovery: Selecting recovered clock
from port 1 (future version will select one of the 32
ports)
EXTCLK0: Not supported (future version will select
one of the 32 ports)
EXTCLK1: Not supported (future version will select
one of the 32 ports)
Default: Loopback
Link Sync
Connect/
Disconnect
CRC4
IF TypeDefines E1 interface type.
Selects the E1 local sync loss alarm recovery
time.
Defines if link is connected.
Enables the generation of CRC bits (in accor-
dance with the CRC-4 polynomial specified by
ITU-T Rec. G.704) for the frames transmitted on
the E1 link, and the checking of the CRC bits car-
ried by the received E1 link frames.
CCITT:
Complies with ITU-Rec.G.732
62411: 10s
Sync Fast: 1s
Default: CCITT
Connect: Link is connected
Disconnect: Link is disconnected
Default: Connect
No: CRC-4 option is disabled
Yes: CRC-4 option is enabled
Please select item <1 to 40>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Please enter your choice:
NOTE: THE SETTINGS FOR SOME PARAMETERS IN THIS CONFIGURATION MENU DETERMINE WHETHER OR NOT OTHER PARAMETERS IN THE MENU ARE
DISPLAYED. FOR EXAMPLE, IF RECOVERY CLOCK MODE IS SET TO AUTO, THEN ITEMS 13–25 AND 27–31 ARE NOT DISPLAYED BECAUSE THEIR VALUES ARE
IGNORED IN THAT MODE. THE PARAMETER DESCRIPTIONS IN TABLE 4-5 HAVE NOTES INDICATING THE NECESSARY CONDITIONS FOR A PARAMETER TO BE
DISPLAYED. SEE THE ACQUISITION SWITCH PARAMETER.
Unframed: Framer is configured to passthrough mode
and the operation mode is set to unframed.
ESF: Framer is configured to T1-ESF mode. Operation
mode is set by the robbed bit field to either fractional or
fractional with CAS.
SF: Framer is configured to T1-SF mode. Operation
mode is set by the robbed bit field to either fractional or
fractional with CAS.
Default: UnFramed
Long Haul: Maximum attenuation of 36dB.
Short Haul: Maximum attenuation of 10dB. This con-
figuration can actually improve the performance when
operating over relatively short line sections, especially
when operating over multipair cables. In such cables,
significant interference is generated by the signals carried by other pairs, and therefore a weak desired signal
can be masked by the interference.
Default: Short Haul
Frame Type
Rx Config Gain
Limit
Framing mode and operation mode for each
configuration.
Note: Before changing the T1 frame type, you
must close all bundles assigned to the link.
Determines the maximum attenuation of the
receive signal that can be compensated for by
the T1 link receive path, to obtain the BER performance required by the standards.
OOS Code Type
Data TX/RX OOS
[0 - 0xFF]
TX/RX OOS Signal
Mask
Inserted into unassigned time slots by the system at the transmit path towards the T1 equipment. This parameter is not displayed when
the frame type is set to unframed.
Can be applied to time slots transmitted
towards the ETH network when loss of signal,
loss of frame, or AIS is detected at the T1 line.
Can also be applied to time slots transmitted
towards the T1 line when a packet receive buffer overrun or underrun occurs. In unframed
mode, voice/data OOS state results in AIS
transmission. This is applied when an LOS
is detected at the T1 line, or when a packet
receive buffer overrun or underrun occurs.
Out-of-service signaling method. OOS signal
is sent in the Ethernet direction when loss of
signal, loss of frame, or AIS is detected at the
T1 line. The OOS signal is also sent toward the
T1 line when packet receive buffer overrun or
underrun occur.
OOS Code: OOS code is sent.
Default: OOS Code
00–FF
Default: 7F
Space: Transmitting CAS all 0s, when the Ethernet or
TDM link is down.
Mark: Transmitting CAS all 1s, when the Ethernet or
TDM link is down.
Space + Mark: Transmitting all 0s in CAS for the first
2.5s, then switching to all 1s.
Mark + Space: Transmitting all 1s in CAS for the first
Adaptive Recovery: Clock recovery regeneration from
UPLINK.
LIU Loopback: T1 recovered receive clock is used as
the transmit clock
Global Adaptive Recovery: Selecting reovered clock
Clock Source
Link Sync Selects the T1 red alarm recovery time.
Connect/
Disconnect
DSU / CSU—
Defines transmit clock source used by the
interface.
Defines if link is connected.
from port 1 (future version will select one of the 32
ports).
EXTCLK0: Not supported (future version will select one
of the 32 ports).
EXTCLK1: Not supported (future version will select one
of the 32 ports).
Default: Loopback
Sync Fast: 1s
62411: 10s
Default: Sync Fast
Connect: Link is connected.
Disconnect: Link is disconnected.
Default: Connect
CSU: If the port interface operates as a CSU, it is necessary to adjust the T1 output transmit level for reliable
operation of the network and for compliance with FCC
Rules Part 68A. This adjustment is used to minimize
the interference caused by a local transmit signal to
other users that transmit their signals on other pairs of
the same cable. The required setting depends mainly
on the length of the cable that connects between the
T1 port and the first repeater down the link. Repeaters
are usually located every mile, and, therefore, they are
designed to optimally handle signals attenuated by
one-mile length of cable. If the T1 port is closer, the
repeater receives a T1 signal at a higher level. This
does not significantly improve handling of the T1 signal, but certainly increases the interference coupled
from the T1 pair to repeaters that serve other pairs in
the cable. To prevent this, an attenuation value can be
selected that brings the T1 signal level closer to the
expected repeater signal level. This is achieved by
enabling circuitry in the T1 transmitter that preattenuates the signal by 7.5dB, 15dB, or 22.5dB, effectively
emulating 1000ft, 2000ft, or 3000ft of cable.
DSU: In this case, the transmit signal mask can be
selected in accordance with the transmit line length, to
meet DSX-1 requirements, as specified by AT&T CB-119,
or operation in accordance with FCC Rules Part 68. For
compliance with DSX-1 specifications per AT&T CB-119
and ANSI T1.102-1987, select the value corresponding
to the length of the cable (in feet) connected between
the T1 port connector and network entry point.
Default: DSU
CSU:
Mask 0: No attenuation.
Mask 1: Attenuation of 7.5dB relative to nominal.
Mask 2: Attenuation of 15dB relative to nominal.
Mask 3: Attenuation of 22.5dB relative to nominal.
Please select item <1 to 43>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
NOTE: THE SETTINGS FOR SOME PARAMETERS IN THIS CONFIGURATION MENU (FOR EXAMPLE, BUNDLE TYPE AND PSN TYPE) DETERMINE WHETHER OR NOT
OTHER PARAMETERS IN THE MENU ARE DISPLAYED. THEREFORE, IT IS NORMAL TO HAVE GAPS IN THE ITEM NUMBERING, SUCH AS HAVING NOTHING LISTED
BETWEEN ITEMS 14 AND 20. THE PARAMETER DESCRIPTIONS IN TABLE 4-6 HAVE NOTES INDICATING THE NECESSARY CONDITIONS FOR A PARAMETER TO BE
DISPLAYED. SEE THE IP TOS PARAMETER.
4.4.1 Configuring SAToP Bundles
See Figure 4-7 and Table 4-6 for SAToP bundle options.
4.4.2 Configuring CESoPSN Bundles
36 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Table 4-6. SAToP Bundle Parameter Descriptions
PARAMETERDESCRIPTIONPOSSIBLE VALUES
HDLC
Bundle TypeSelect the bundle type.
Assign this Bundle
to PCM port
TX Bundle
Destination
Number of the TDM port to which the bundle is assigned.
Destination of the Tx data flow toward the ETH port.
Note: The Tx bundle destination cannot be changed after the
bundle configuration has been saved.
SAToP
CES
1–32
Ethernet: TDM to Ethernet
CPU: TDM to CPU
Cross Connect: Don’t support yet
Default: Ethernet
RX Bundle
Destination
TX Bundle
Number
[0 - 65535]
Rx Bundle
Number
[0 - 65535]
Source IP Address
Destination Main
MAC address
Destination IP
Address
Next Hop IP
Destination of the Rx data flow from the ETH port.
Note: The Rx bundle destination cannot be changed after the
bundle configuration has been saved.
Number of the desired Tx bundle.Default: 2
Number of the desired Rx bundle.
Note: Must be unique for each bundle ID.
Assign the bundle one of the source IP addresses configured in
the General Configuration menu.
MAC address of destination device.
Note: If the destination Main MAC address is different from the
default value, the MAC is not learned in the ARP process.
IP address of the destination device.
The Next Hop parameter should be used when the Destination IP
Address is not in the device subnet. In such cases the Ethernet
packet is sent to the Next Hop IP. The default value of the Next
Hop field is the default gateway.
Note: The Next Hop must be in the same subset as the Source IP
address of the bundle ID.
CPU: CPU
PCM: TDM (PCM bus)
Discard: Discarded
Default: PCM
Default: 2
IP 1, IP 2
Default: IP 1
Default: 000000000000
0.0.0.0 – 255.255.255.255
0.0.0.0 – 255.255.255.255
IP ToS [0 - 255]
IP TTL [0 - 255]
Sets the IP ToS field in the IP ETH packets leaving the EV kit.
The ToS setting defines the whole byte, since different vendors
could use different bits to tag packets for traffic prioritization. ToS
assignment applies to all ETH packets leaving the EV kit for this
bundle.
Note: This parameter is displayed only if PSN Type is set to IP.
Sets the IP TTL field in the IP packets transmitted by the device.
TTL assignment applies to all ETH packets leaving the EV kit for
this bundle.
Note: This parameter is displayed only if PSN Type is set to IP.
Defines the maximum size of the jitter buffer. When this parameter
is set to zero, the maximum jitter buffer size equals (2 x PDVT) +
(2 x packet fill).
Defines how the OOS condition at the TDM interface is transmitted
towards the Ethernet side.
1–512000μs
Default: 5000
0–512000μs
Default: 0
1. OOS Mode Conditioning: OOS
condition is reported by the OOS
(ETH cond data) code and L-bit of
the TDMoIP frame.
2. OOS Disable: OOS condition is
not reported, but user data with L-bit
keeps on being sent towards the
Ethernet interface.
3. OOS Mode Tx Off: OOS condition is not reported and faulty user
data is not transmitted towards the
Ethernet interface.
4. OOS Mode Conditioning with JB
reset: OOS condition is reported by
the OOS (ETH cond data) code and
L-bit of the TDMoIP frame. Reset jitter buffer when L-bit cleared.
5. OOS Disable with JB reset: OOS
condition is not reported, but user
data with L-bit keeps on being sent
towards the Ethernet interface. Reset
jitter buffer when L-bit cleared.
6. OOS Mode Tx Off with JB reset:
OOS condition is not reported and
faulty user data is not transmitted
towards the Ethernet interface. Reset
jitter buffer when L-bit cleared.
Redundant
RTP Mode
Next Hop Type
Defines whether this bundle is a redundant bundle.
Note: The bundle redundancy cannot be changed after the
bundle configuration has been saved. Redundant mode not supported
Determines if an RTP header is used for the bundle. Must be used
for common clock mode.
Must be set to MAC for next hops that do not reply to ARP
requests.
Enable: Current bundle is redundant
Disable: Current bundle is not
redundant
Default: Disable
Enable: RTP header is used
Disable: RTP header is not used
the working level of the jitter buffer is
determined by the timing the bundle
was first opened
On N Times: Up to N times of bundle reset is allowed
Endless: Bundle reset is allowed
with unlimited number of resets
Default: On N Times
2–127
Default: 83
0: L2TPV3 cookies are not used
1: One L2TPV3 cookie is used
2: Two L2TPV3 cookies are used
Default: 0
Enable JB Reset
Window Size
[2 - 127]
Number Of Outer
Cookies
A mechanism that enables setting an optimum level for the jitter
buffer working level. It enables the reset of a bundle, until a satisfactory jitter buffer level is reached, to minimize the delay.
The maximum number of conditioning Ethernet packets that can
be inserted upon a loss of received Ethernet packets. If the difference in packet SN is greater than the configured window, there is
no insertion of conditioning packets.
Determines if L2TPV3 cookies are used and how many.
Note: This parameter is displayed only when PSN Type = L2TPV3.
Cookie 1
Cookie 2
Number Of Outer
Labels
MPLS Outer
Label 1
MPLS Outer
Label 2
Optional field that contains a randomly selected value used to validate association of the packet with the expected bundle identifier.
Note: This parameter is displayed only when PSN Type = L2TPV3
and Number of Outer Cookies is 1 or 2.
Optional field that contains a randomly selected value used to validate association of the packet with the expected bundle identifier.
Note: This parameter is displayed only when PSN Type = L2TPV3
and Number of Outer Cookies is 2.
Determines if MPLS outer labels are used and how many.
Note: This parameter is displayed only when PSN Type = MPLS.
MPLS Outer Label (only when not equal to 0) identifies the MPLS
LSP, which is used to tunnel the TDM packets through the MPLS
network.
Note: When equal to 0, only the Inner Label exists. This parameter
is displayed only when PSN Type = MPLS and Number of Outer
Labels is 1 or 2.
MPLS Outer Label (only when not equal to 0) identifies the MPLS
LSP, which is used to tunnel the TDM packets through the MPLS
network.
Note: When equal to 0, only the Inner Label exists. This parameter
is displayed only when PSN Type = MPLS and Number of Outer
Labels is 2.
0–4294967295
Default: 0
0–4294967295
Default: 0
0: MPLS outer labels not used
1: One MPLS outer label is used
2: Two MPLS outer labels are used
ReorderingDetermines whether to reorder received misordered packets.
Sets the value of the MPLS experimental bits.
Note: This parameter is displayed only when PSN Type = MPLS.
0–7
Default: 0
Yes: Received misordered packets
are reordered
No: Received misordered packets
are not reordered
Default: Yes
Size in Bytes
[24 - 1600]
Eth Cond Octet
Type
TDM Cond Octet
Type
RTP Source
Identifier
RTP Payload
TX Bundle
Number Location
at UDP port
RX Bundle
Number Location
at UDP port
SAToP payload size in bytes.
Conditioning octet used in the Ethernet direction when no data is
available.
Conditioning octet used in the TDM direction when no data is
available.
The RTP header Source Identifier value for transmitted packet.
Note: This parameter is displayed only when RTP Mode is
Enabled.
The RTP header Payload value for transmitted packet.
Note: This parameter is displayed only when RTP Mode is
Enabled.
Indicating the location of the Transmitting Bundles UDP port.
Indicating the location of the Receiving Bundles UDP port.
24–1600
Default: 965
Octet A
Octet B
Octet C
Octet D
Default: Octet A
Octet A
Octet B
Octet C
Octet D
Default: Octet A
0–4294967295
Default: 111111111
0–255
Default: 96
Source: UDP port number is at
Source Port side
Destination: UDP port number is at
Destination Port side
Source: UDP port number is at
Source Port side
Destination: UDP port number is at
Destination Port side
41Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
See Figure 4-8 and Table 4-7 for CESoPSN bundle options.
4.5 Deleting Bundles
Bundle Conguration for ID 2
1. Bundle Type CES
2. Assign this Bundle to PCM port 2
3. Timeslot Assignment [1-24] 1-24
4. TX Bundle Destination Ethernet
5. RX Bundle Destination PCM
6. TX Bundle Number[0 - 65535] 2
7. RX Bundle Number[0 - 65535] 2
8. Source IP Address IP 1
9. Destination Main MAC Address 0020D224A346
10. Destination IP Address 10.10.10.5
11. Next Hop IP 0.0.0.0
12. IP ToS[0 - 255] 0
13. IP TTL[0 - 255] 128
MAIN MENU
↓
BUNDLE
CONFIGURATION
↓
CES BUNDLE
CONFIGURATION
14. Number of VLAN Tags[0 - 2] 0
20. PSN Type IP
21. Switches Sanity Check Discard
22. Clock Recovery No
23. Differential Time (usec)[1 - 512000] 5000
24. Max Buffer Size (usec)[0 - 512000] 15000
25. L Bit & OOS OOS Mode Conditioning
26. Redundant Disable
27. RTP Mode Disable
28. Next Hop Type IP
29. Enable JB Reset On N Times
30. Window Size[2 - 127] 83
35. Payload Type Data
36. Reordering Yes
37. Number of Frames[1 - 1500] 40
38. Eth Cond Octet Type Octet A
39. TDM Cond Octet Type Octet A
45. Far End Interface Type ESF
46. TX Bundle Number Location at UDP port Source
47. RX Bundle Number Location at UDP port Source
Please select item <1 to 44>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
NOTE: THE SETTINGS FOR SOME PARAMETERS IN THIS CONFIGURATION MENU (FOR EXAMPLE, BUNDLE TYPE AND PSN TYPE) DETERMINE WHETHER OR NOT
OTHER PARAMETERS IN THE MENU ARE DISPLAYED. THEREFORE, IT IS NORMAL TO HAVE GAPS IN THE ITEM NUMBERING, SUCH AS HAVING NOTHING LISTED
BETWEEN ITEMS 14 AND 20. THE PARAMETER DESCRIPTIONS IN TABLE 4-7 HAVE NOTES INDICATING THE NECESSARY CONDITIONS FOR A PARAMETER TO BE
DISPLAYED. SEE THE IP TOS PARAMETER.
Number of the TDM port to which the bundle is assigned.
Assigns time slots to the previously selected bundle, for
example, 1–5, 7, 8, 9, 12–15.
Destination of the Tx data flow toward the ETH port.
Note: The Tx bundle destination cannot be changed after the
bundle configuration has been saved.
SAToP
CES
1–32
T1: 1–24
E1: 1–31
Ethernet: TDM to Ethernet
CPU: TDM to CPU
Cross connect: TDM to TDM (not supported
yet)
Default: Ethernet
RX Bundle
Destination
TX Bundle
Number
[0 - 65535]
RX Bundle
Number
[0 - 65535]
Source IP
Address
Destination
Main MAC
Address
Destination IP
Address
Next Hop IP
IP ToS
[0 - 255]
Destination of the Rx data flow from the ETH port
Note: The Rx bundle destination cannot be changed after the
bundle configuration has been saved.
Number of the desired Tx bundle.Default: 2
Number of the desired Rx bundle.
Note: Must be unique for each bundle ID.
Assign the bundle one of the source IP addresses configured
in the General Configuration menu.
MAC address of destination device.
Note: If the destination Main MAC address is different from
the default value, the MAC is not learned in the ARP process.
IP address of the destination device10.10.10.5
The Next Hop parameter should be used when the
Destination IP Address is not in the device subnet. In such
cases the Ethernet packet is sent to the Next Hop IP. The
default value of the Next Hop field is the default gateway.
Note: The Next Hop must be in the same subset as the
Source IP address of the bundle ID.
Sets the IP ToS field in the IP ETH packets leaving the EV kit.
ToS setting defines the whole byte, since different vendors
could use different bits to tag packets for traffic prioritization.
The ToS assignment applies to all ETH packets leaving the
EV kit for this bundle.
Note: This parameter is displayed only if PSN Type is set to IP.
Determines whether this bundle is used by the clock recovery
mechanism.
Desired depth of the jitter buffer.
Defines the maximum size of the jitter buffer. When this
parameter is set to zero, the maximum jitter buffer size equals
(2 x PDVT) + (2 x packet fill time).
Defines how the OOS condition at the TDM interface is trans-
mitted towards the Ethernet side.
mechanism
No: Bundle is not used by clock recovery
mechanism
Default: No
1–512000μs
Default: 5000
0–512000μs
Default: 0
1. OOS Mode Conditioning: OOS condition is reported by the OOS (ETH cond data)
code and L-bit of the TDMoIP frame.
2. OOS Disable: OOS condition is not reported, but user data with L-bit keeps on being
sent towards the Ethernet interface.
3. OOS Mode Tx Off: OOS condition is not
reported and faulty user data is not transmitted towards the Ethernet interface.
4. OOS Mode Conditioning with JB reset:
OOS condition is reported by the OOS (ETH
cond data) code and L-bit of the TDMoIP
frame. Reset jitter buffer when L-bit cleared.
5. OOS Disable with JB reset: OOS condition is not reported, but user data with L-bit
keeps on being sent towards the Ethernet
interface. Reset jitter buffer when L-bit
cleared.
6. OOS Mode Tx Off with JB reset: OOS
condition is not reported and faulty user data
is not transmitted towards the Ethernet interface. Reset jitter buffer when L-bit cleared.
Redundant
RTP Mode
Next Hop
Type
Defines whether this bundle is a redundant bundle.
Note: The bundle redundancy cannot be changed after the
bundle configuration has been saved.
Note: Redundant mode not supported
Determines if an RTP header is used for the bundle. Must be
used for common clock mode.
Must be set to MAC for next hops that do not reply to ARP
requests.
Enable: Current bundle is redundant
Disable: Current bundle is not redundant
Default: Disable
Enable: RTP header is used
Disable: RTP header is not used
level of the jitter buffer is determined by the
timing the bundle was first opened
On N Times: Up to N times of bundle reset
is allowed
Endless: Bundle reset is allowed with unlimited number of resets
Default: On N Times
2–127
Default: 83
Enable JB
Reset
Window Size
[2 - 127]
A mechanism that enables setting an optimum level for the
jitter buffer working level. It enables the reset of a bundle
until a satisfactory jitter buffer level is reached to minimize the
delay.
The maximum number of conditioning Ethernet packets that
can be inserted upon a loss of received Ethernet packets.
If the difference in packet SN is greater than the configured
window, there is no insertion of conditioning packets.
Number Of
Outer Cookies
Cookie 1
Cookie 2
Number Of
Outer Labels
MPLS Outer
Label 1
Determines if L2TPV3 cookies are used and how many.
Note: This parameter is displayed only when
PSN Type = L2TPV3.
Optional field that contains a randomly selected value used
to validate association of the packet with the expected bun-
dle identifier.
Note: This parameter is displayed only when PSN Type =
L2TPV3 and Number of Outer Cookies is 1 or 2.
Optional field that contains a randomly selected value used
to validate association of the packet with the expected bun-
dle identifier.
Note: This parameter is displayed only when PSN Type =
L2TPV3 and Number of Outer Cookies is 2.
Determines if MPLS outer labels are used and how many.
Note: This parameter is displayed only when PSN Type =
MPLS.
MPLS Outer Label (only when not equal to 0) identifies the
MPLS LSP which is used to tunnel the TDM packets through
the MPLS network.
Note: When equal to 0, only the Inner Label exists. Note: This
parameter is displayed only when PSN Type = MPLS and
Number of Outer Labels is 1 or 2.
0: L2TPV3 cookies are not used
1: One L2TPV3 cookie is used
2: Two L2TPV3 cookies are used
Default: 0
0–4294967295
Default: 0
0–4294967295
Default: 0
0: MPLS outer labels not used
1: One MPLS outer label is used
2: Two MPLS outer labels are used
Default: 0
0–1048575
Default: 0
MPLS Outer Label (only when not equal to 0) identifies the
MPLS LSP which is used to tunnel the TDM packets through
MPLS Outer
Label 2
Experimental
Bits
46 Maxim Integrated
the MPLS network.
Note: When equal to 0, only the Inner Label exists. Note: This
parameter is displayed only when PSN Type = MPLS and
Number of Outer Labels is 2.
Sets the value of the MPLS experimental bits.
Note: This parameter is displayed only when PSN Type = MPLS.
(without CAS).
Voice CAS: The bundle is configured as
Structured with CAS. For units with T1 interface the payload type can be set to voice
Payload TypeDetermines the bundle structure.
ReorderingDetermines whether to reorder received misordered packets.
with CAS, if the interface type of the far-end
unit is set to T1 SF or T1 ESF.
Note: For redundant or cross-connect
bundles, both bundles must be the same
payload type. The payload type cannot be
changed after the bundle configuration has
been saved.
Yes: Received misordered packets are
reordered
No: Received misordered packets are not
reordered
Default: Yes
Number of
Frames
[1 - 1500]
Eth Cond
Octet Type
TDM Cond
Octet Type
RTP Source
Identifier
RTP Payload
Redundant
Type
The number of TDM frames included in the CESoPSN payload.
Condition octet used in the Ethernet direction when no data
is available.
Condition octet used in the TDM direction when no data is
available.
The RTP header Source Identifier value for transmitted packet.
Note: This parameter is displayed only when RTP Mode is
Enabled.
The RTP header Payload value for transmitted packet.
Note: This parameter is displayed only when RTP Mode is
Enabled.
Note: This parameter is displayed only when Redundant is
Enabled.
1–1500
Default: 24
Octet A
Octet B
Octet C
Octet D
Default: Octet A
Octet A
Octet B
Octet C
Octet D
Default: Octet A
0–4294967295
Default: 111111111
0–255
Default: 96
None: Redundancy disabled (no bundles are
transmitted)
1 and 1
1 plus 1
1 and 1 HW: Only one of the redundant bun-
dles (primary or secondary) is transmitted
1 plus 1 HW: Both redundant bundles (primary and secondary) are transmitted
Default: 1 plus 1 HW
To view alarms select Alarms from the Main Configuration
(S132) menu. The TopAlarms Menu appears as shown
in Figure 5-1.
5.1.1 Displaying General Alarms
To display general alarms, from the TopAlarms Menu
(Figure 5-1) select General Alarms. The General
Alarms menu appears (Figure 5-2).
Table 5-1. General Alarms Parameter Descriptions
PARAMETERDESCRIPTIONPOSSIBLE VALUES
SW Tx TDM packet loss
SW Rx LAN packet loss
Rx FIFO SizeIndicates the current Rx FIFO level given in dwords (32 bits)0–3FF
Rx Ip Ver Err StatusReceived packet IP version does not match the configured IP version.ON, OFF
Rx Fifo Sof Err
Rx MPLS ErrMPLS packet received with more than three labels (packet is discarded).ON, OFF
MAC Receive Fifo OverrunMAC receive FIFO has overflowed.ON, OFF
Packets received from TDM to CPU were discarded due to lack of buffers in the TDMoP IC.
Packets received from LAN to CPU were discarded due to lack of buffers in the TDMoP IC.
Start of packet indication mismatch in Rx FIFO (indicates a bundle
configuration error). Results in flushing the Rx FIFO’s contents.
ON, OFF
ON, OFF
ON, OFF
49Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
5.1.2 Displaying Interface Alarms
To display E1/T1 interface alarms:
1) From the TopAlarms Menu (Figure 5-1) select Interface Alarms.
Loss of FrameLoss of frame synchronization.ON, OFF
AISAIS is detected on the link.ON, OFF
RAIRAI is detected on the link.ON, OFF
RX FRAME SLIP,
TX FRAME SLIP
cated by the front panel SYNC LOS
LED being lit.
E1 frame slips are detected (not
displayed during local loss of frame
synchronization). Updated once per
second.
POSSIBLE
VALUES
ON, OFF
ON, OFF
2) Enter the TDM link (port) number.
3) From the Interface Alarm menu, select TDM Alarms.
The TDM Alarms menu is displayed (Figure 5-3).
CORRECTIVE ACTIONS
Check cable connection to the E1 link connector.
Check line and/or other communication equipment
connected to the link of the remote unit.
Check the remote equipment. Perform the following:
Check cable connection to the E1 connector of the
remote device.
Check line and/or other communication equipment
providing the E1 link to the remote equipment.
Replace the remote equipment.
Check equipment connected to the remote end of
the E1 link.
Check equipment connected to the remote end of
the E1 link.
Verify the clock settings.
Check the far end (unstable clock source).
Replace the EV kit only if previous steps do not correct the problem.
Bipolar violations or code violations
BPV/CV ERRORs
50 Maxim Integrated
on the link receive signal. Updated
once per second.
0, 1, . . .
Check the TDM equipment and cable connecting it
to the E1 port.
Replace the EV kit.
DS34S132 Evaluation Kit
Evaluates: DS34S132
To display adaptive alarms:
1) From the TopAlarms Menu (Figure 5-1), select InterfaceAlarms.
2) Enter the TDM link (port) number.
3) From the Interface Alarms menu, select Adaptive Alarms. The Adaptive Alarms menu is displayed
(Figure 5-4).
If a problem cannot be corrected by carrying out the
5.1.3 Displaying Bundle Alarms
The EV kit displays various per-bundle alarms. To display bundle alarms:
1) From the TopAlarms Menu (Figure 5-1), select Bundle Alarms.
2) Enter the bundle ID.
Depending on the bundle type, one of the alarm menus
shown in Figure 5-5 is displayed.
actions listed in Table 5-2 or Table 5-3, perform the
actions corresponding to the problem symptoms in
accordance with Table 5-4.
No recovery: Clock recovery mechanism is disabled.
Idle: Clock recovery mechanism is in its idle state
Acquisition: Frequency acquisition state.
Tracking 1, Tracking 2: In these phases, the clock
recovery mechanism performs slow and precise phase
tracking.
ON, OFF—
Free Running with Calibration
Locked
Unlocked
Verify that the bundle
is configured as clock
recovery enabled, and
that the link clock is configured to be recovered.
—
51Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
5.1.3.1 SAToP/CES Bundle Alarms
See Figure 5-5 and Table 5-4 for the SAToP/CES bundle alarm options.
Tx Frame with M bitsTransmit packets with Modifier bits (M-bits) set.ON, OFF
HW lack of Tx buffers
Rx TDMoIP Length Mismatch
Rx Frame with R bit (Remote
Fail)
Rx Frame with L bit (Remote
TDM Fail)
Rx Frame with M bitsReceived packets with Modifier bits (M-bits) set.ON, OFF
Overrun OccurredOverrun has occurred in jitter buffer.ON, OFF
Underrun OccurredUnderrun has occurred in jitter buffer.ON, OFF
JB Reset OccurredThe jitter buffer was reset.ON, OFF
RX Fragmentation BitPacket fragmentation status.
Transmit packets with Remote Fail indication (R-bit) set.ON, OFF
Transmit packets with Local Fail indication (L-bit) set.ON, OFF
Packet received from TDM was discarded due to lack of buffers associated with this bundle.
The length of an incoming packet did not match the length
expected for the bundle configuration.
ON, OFF
ON, OFF
Received packets with Remote Fail indication (R-bit) set.ON, OFF
Received packets with Local Fail indication (L-bit) set.ON, OFF
ON: Packet is fragmented
OFF: Entire (unfragmented)
multiframe structure is
carried in a single packet
52 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Table 5-4. SAToP or CES Bundle Alarm Descriptions (continued)
PARAMETERDESCRIPTIONPOSSIBLE VALUES
Start frame or multiframe
insertion (CES bundles only)
Frame Count Err
Jump Overflow Err
Sequence Number Drop Err
Miss Ordered Discard
Start frame or multiframe mismatch.ON, OFF
Packets that belong to structured with CAS bundles were
received with incorrect number of frames.
Packets received with incorrect sequence number (higher than
the expected sequence number and within the window allowed
by the configured Rx_max_lost_packets value) and could not
be inserted into the jitter buffer due to insufficient space.
Packets discarded due to incorrect sequence number (SN
equal to the former or gap between them exceeds limit determined by ‘Rx_max_lost_packets’ parameter).
Packets discarded because they were considered duplicated,
or because they were received too late to be inserted into the
jitter buffer.
ON, OFF
ON, OFF
ON, OFF
ON, OFF
5.2 Displaying Performance Monitoring
Counters
The EV kit provides statistics collection for the Ethernet
interface and bundles.
5.2.1 Displaying Ethernet Counters
To display the Ethernet counters:
1) From the Main Configuration (S132) menu (Figure 3-2),
select Performance (PM). The TopPMs Menu (perfor-
mance monitoring) is displayed (Figure 5-6).
TopPMs Menu
1. Ethernet Performance
2. Interface Performance
3. Bundle Performance
Please select item <1 to 3>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Please enter your choice:
Figure 5-6. Performance Monitoring Menu
2) Select Ethernet Performance. The Ethernet
Performance Data menu is displayed (Figure 5-7).
This menu is automatically redisplayed every few seconds. To disable automatic updates, select d from the
menu. To reset the Ethernet performance monitoring
counters, select c.
The number of ETH packet octets successfully received (not including
Correct Bytes (RX)
Correct Frames (RX)
Pause Packets (RX)
CRC). When a valid connection is established the number increases steadily. This counter wraps around to 0 after reaching the maximum value.
The number of ETH packets successfully received. When a valid connection
is established the number increases steadily. This counter wraps around to
0 after reaching the maximum value.
The number of good ETH pause packets received. A good packet has a
length of 64 to 1518 (1536 if bit 8 is set in the network configuration register)
and has no FCS, alignment, or receive symbol errors.
32-bit number
32-bit number
0–511
Counts the number of packets received that do not pass the FCS check
(RFC 1643). An FCS check is a mathematical way to ensure that all the
FCS Error
Alignment Errors
Symbol ErrorsThe number of packets from PHY that had Rx_err during reception.
Excessive Length Ers
Jabbers Error
Under size Packets
54 Maxim Integrated
frame bits are correct without the system having to examine each bit and
compare it against the original. Recommendation: Check for physical problem such as hardware problem, or a bad line, or noisy environment.
The number of packets received that are not an integral number of octets in
length (RFC 1643). All frames should end on an 8-bit boundary, but physical
problems on the network could cause the number of bits to deviate from the
multiple of eight. Recommendation: Check physical connections, devices
and configuration.
The number of received packets where the length exceeds 1518 bytes, and
without CRC error, alignment error or symbol error.
The number of received packets exceeding 1518 bytes (1536 if bit 8 set in
network configuration register) in length and have either a CRC error, an
alignment error or a receive symbol error.
The number of received packets where the length is less than 64 bytes,
without CRC error or alignment error.
0–255
0–255
0–255
0–255
0–255
DS34S132 Evaluation Kit
Evaluates: DS34S132
Table 5-5. Ethernet Performance Data Descriptions (continued)
PARAMETERDESCRIPTIONPOSSIBLE VALUES
Classified PacketsThe number of packets that passed packet classifier.32-bit number
Checksum Err PacketsThe number of packets with IP checksum errors.
Stray PacketsThe number of strayed packets.
Correct Bytes (TX)
Correct Frames (TX)
Pause Packets (TX)The number of pause packets transmitted.
Single Collision
Multiple Collision
Deferred Frames
Underrun
Excessive CollisionThe number of packets that were not transmitted due to 16 collisions.
Late Collision
The number of octets successfully transmitted (not including CRC). When a
valid connection is established the number increases steadily.
The number of packets successfully transmitted. When a valid connection is
established the number increases steadily.
Counter of successfully transmitted packets for which transmission is inhibited by exactly one collision. Recommendation: Use a full-duplex mode if
possible.
Counter of successfully transmitted packets for which transmission is inhibited by 2 to 15 collisions. Recommendation: Use a full-duplex mode if possible.
The number of packets experiencing deferral due to carrier sense being
active on the first attempt at transmission. Packets involved in any collision
are not counted nor are packets that experienced a transmit underrun.
The number of packets that were not transmitted due to transmit FIFO
underrun.
To allow collision detection to work properly, the period in which collisions
are detected is restricted (512 bit-times). For 10BASE-T Ethernet (10Mbps),
it is 51.2Fs; for Fast Ethernet (100Mbps) it is 5.12Fs. For Ethernet stations,
collisions can be detected up to 51.2 Fs after the beginning of the transmission, or in other words, up to the 512th bit of the frame. When a station
detects a collision after it has sent the 512th bit of its frame, this is counted
as a late collision. Note: A late collision is counted twice—as a collision and
as a late collision.
Recommendation: Check if there is incorrect cabling or a non-compliant
number of hubs in the network. Bad network interface cards (NICs) can also
cause late collisions.
Valid only in
half-duplex mode
(RFC 1643)
Valid only in
half-duplex mode
(RFC 1643)
0–511
0–255
Valid only in
half-duplex mode
(RFC 1643)
0–255
Carrier Sense
Sqe Tst Errors
The number of packets transmitted where carrier sense was not seen during
transmission or where it was deasserted after being asserted in the transmit
packet without collision. Recommendation: Check connection between the
UPLINK interface and its Ethernet transceiver.
The number of packets where COL was not asserted within 96 bit-times (an
interpacket gap) of TX_EN being deasserted in half-duplex mode.
Valid only in
half-duplex mode
(RFC 1643)
0–255
0–255
55Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
5.2.2 Displaying Bundle Counters
The EV kit displays counters for HDLC, SAToP, and CES
bundles. To display bundle counters:
1) From the Main Configuration (S132) menu (Figure 3-2),
select Performance (PM).
2) The TopPMs Menu (performance monitoring) is dis-
played (Figure 5-6). Select Bundle Performance.
3) A list of open bundles is displayed. Enter the ID number of the bundle for which you want to display the
performance monitoring counters. The Bundle PMs
menu is displayed (SAToP/CESoPSN: Figure 5-8).
This menu is automatically redisplayed every few seconds. To disable automatic updates, select d from the
menu. To reset the Ethernet performance monitoring
counters, select c.
5.2.2.1 Displaying SAToP/CES Bundle Counters
See Figure 5-8 and Table 5-6 for SAToP/CES bundle
counter options.
Table 5-6. SAToP/CES Bundle Counter Descriptions
PARAMETERDESCRIPTION
Correct Frames Tx to LAN
Correct Frames Rx from LAN
Lost Frames in Rx
Minimum JB Level [Usec]The minimum jitter buffer level for the current bundle.
56 Maxim Integrated
The number of packets successfully transmitted for the bundle. When a valid connection is
established, the number increases steadily.
The number of packets successfully received for a bundle. When a valid connection is established, the number increases steadily.
There are two possible reasons for lost frames:
Packet or packets are dropped or lost somewhere along the network.
Reordering of packets by network. Packet reordering can occur due to queuing mechanisms,
rerouting by the network, or when the router updates very large routing tables and is therefore overloaded.
Recommendations:
Ensure the EV kit traffic has sufficient bandwidth.
Ensure the Ethernet connection is functioning properly.
Ensure the Ethernet/IP network provides priority (quality of service) to the EV kit traffic. Priority
can be achieved by two means: VLAN tagging and IP ToS marking.
Verify that the IP network devices (switches/routers/modems/etc.) can handle the EV kit PPS
(packets per second) rate.
Ensure the network devices do not drop/lose/ignore packets by checking their statistics.
Maximum JB Level [Usec]The maximum jitter buffer level for the current bundle.
Discarded Packets in RxNumber of received packets that were discarded by SAToP/CESoPSN payload type machine.
Reordered Packets in Rx
Underrun Occurred
Number of received misordered packets that were successfully reordered by SAToP/
CESoPSN payload type machine.
An underrun situation can be caused by:
Buffer starvation: Packets delay variation causes the buffer to empty out gradually until it
underflows.
Continuous sequence errors: The sequence error means a halt in the valid stream of packet
arrival into the jitter buffer.
Packets are stopped/lost/dropped.
Differential timing (PDVT) configuration that is not large enough to compensate for the network delay variation.
In a TDM network, all system elements must be locked to one master clock. If not, it leads to
a situation in which data is clocked out of the jitter buffer at a rate different from the one that
is clocked in. This gradually results in either an overflow or underflow event, depending on
which rate is higher. The event repeats itself periodically as long as the system clock is not
locked.
Recommendations: Try increasing the differential timing (PDVT) in a bundle configuration.
Check reasons for sequence errors or lost/dropped packets (if present), system clocking
configuration, Ethernet environment (full duplex), and connection, packets drop/loss/ignore
by routers/switches or nonuniform packets output by routers/switches due to queuing mechanisms.
Ensure the same number of time slots for bundle is configured on each end.
Ensure the Ethernet/IP network provides priority (quality of service) to the TDMoP traffic.
Priority can be achieved by two means: VLAN tagging and IP TOS marking.
Number of jumped packets encountered by SAToP/CESoPSN payload type machine. System
Jump Packets in Rx
MisOrdered Packets in RxReceived misordered packets.
Rx MalFormed PacketsReceived malformed packets.
Rx R-bit PacketsReceived packets with R-bits.
Tx L-bit PacketsTransmitted packets with L-bits.
Overrun OccurredNumber of overrun occurred.
Loss of Frames OccurredTotal loss of frames occurred.
software can calculate the number of lost packets using the following equation: Lost Packets
= (Jumped Packets - Reordered Packets).
57Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
5.2.3 Displaying TDM Interface Counters
This is not yet implemented in the DS34S132 EV kit user
interface software.
5.3 Utility Menu
5.3.1 Read Memory/Write Memory
For advanced troubleshooting, the system software
has menu options to read and write the registers of
the DS34S132 and other peripherals. From the Main Configuration (S132) menu, select either Read Memory
or Write Memory and follow the prompts. These selections (options 1 and 2) can access the DS34S132 registers, but not DSP memory or DDR memory. To access
DSP or DDR memory, the user must use options 11–14.
5.3.2 Update ToP Application
This option allows the user to upgrade the Linux-based
software package to the newest version, if necessary.
This option is for debug purposes only. Maxim Technical
Support provides support for this function.
5.4.4 Management Network Information
This option displays the Ethernet management port information. It displays the MAC address, IP address, and
other network information.
5.3.5 Loopbacks
The DS34S132 EV kit supports local and remote loopbacks that can be run on the physical interfaces and
bundles. The loopbacks can be used to check internal
circuitry of the unit and its physical network and bundle
connections. Options 1–4 refer to loopbacks on the T1/
E1 transceivers. Refer to the DS26518 IC data sheet for
more information.
5.3.5.1 Enabling Loopbacks
To run a loopback on a physical port:
1) From the Main Configuration (S132) menu, select
Utilities.
2) The Utility menu is displayed.
3) From the Utility menu, select Loopbacks.
4) Specify the TDM interface number.
5) The Loopbacks Menu is displayed (Figure 5-9).
6) Select Remote Loopback, Local Loopback, or any
of several other loopback types.
7) Select Enable.
Loopbacks Menu
1. Remote Loopback Disable
2. Payload Loopback Disable
3. Framer Loopback Disable
4. Local Loopback Disable
5. Ethernet Loopback Unknown
6. PHY Loopback Unknown
Please select item <1 to 6>
q: exit, s: save, ESC: previous menu, r or Enter: reprint screen
Please enter your choice:
Figure 5-9. Loopbacks Menu
58 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
5.3.5.2 Framer Loopback and Payload Loopback
These loopbacks are not necessary for troubleshooting
purposes. Remote and local loopbacks are sufficient.
Refer to the DS26518 IC data sheet for more information
on the use of these loopbacks.
5.3.5.3 Local Loopback
Local loopback returns packets received through the
IP interface towards the network. Figure 5-10 shows the
signal path for a typical local loopback.
T1/E1
TRANSCEIVER TDMoP
DS34S132 EV KIT
TDM INTERFACEIP INTERFACE
Figure 5-10. Local Loopback Diagram
ETH
PHY
5.3.5.4 Remote Loopback
Remote loopback returns the data received on the TDM
receive port to the test equipment connected to the TDM
transmit port. See Figure 5-11.
5.3.5.5 Ethernet Loopback
The Ethernet loopback loops data at the transmit MAC
interface (internal on the DS34S132) to the receive MAC
interface. Data coming from the TDM side is looped back
to the TDM interface. See Figure 5-12.
PACKET
SWITCHED
NETWORK
TESTING
EQUIPMENT
T1/E1
TRANSCEIVER TDMoP
ETH
PHY
TESTING
EQUIPMENT
Figure 5-11. Remote Loopback Diagram
TESTING
EQUIPMENT
Figure 5-12. Ethernet Loopback Diagram
DS34S132 EV KIT
TDM INTERFACEIP INTERFACE
T1/E1
TRANSCEIVER TDMoP
DS34S132 EV KIT
TDM INTERFACEIP INTERFACE
ETH
PHY
59Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
TESTING
EQUIPMENT
TDM INTERFACEIP INTERFACE
Figure 5-13. PHY Loopback Diagram
5.3.5.6 PHY Loopback
The PHY loopback loops data at the Ethernet PHY
received from the TDM interface (through the DS34S132)
back to the TDM interface. See Figure 5-13.
5.3.6 Reboot System
Reboots the whole EV kit (hardware and software reboot).
5.3.7 UART Baud Rate
Allows the user to change to change the serial-port baud
rate (default 115200bps).
5.3.8 Read Script Configuration File from
Terminal
This option is not functional at this time.
T1/E1
TRANSCEIVER TDMoP
DS34S132 EV KIT
ETH
PHY
5.3.10 Read S132 Memory/Write S132 Memory
(DDR Memory)
Access to the DS34S132 memory and DDR SDRAM.
5.3.11 Read DSP Memory/Write DSP Memory
Access to DSP embedded in the DS34S132 for clock
recovery. No offset required. Debugging use only.
5.3.12 System Information
Describes SW Version, S132 revision, HAL (driver) revision, and DSP Version (embedded in the DS34S132).
5.3.13 Execute Linux Command
This option allows the user to execute a Linux command
without exiting the EV kit software program.
5.3.9 Send OAM Packet to Other Party
This option is not functional at this time.
60 Maxim Integrated
5.4 Troubleshooting Chart
Table 5-8 lists possible faults, probable causes, and the
actions necessary to correct the situation.
Table 5-8. Troubleshooting Chart
FAULTPROBABLE CAUSECORRECTIVE ACTIONS
The E1/T1 equipment
connected to EV kit is not
synchronized (E1/T1 level)
with the EV kit.
Slips and errors in E1/T1
equipment.
Echo in voice.End-to-end delay is too large
Ethernet interface LINK
indicator is not lit.
Configuration problemsCheck the EV kit port configuration.
—Check E1/T1 alarms to indicate the exact cause.
Ethernet port is set to work in half-duplex
mode (can cause extreme PDV because
of collisions and back-offs).
Ethernet ports of the local and remote
devices are not set to the auto negotiation
mode or set to different rates.
Timing configuration is not properly set
(periodicbufferunder/overflows—bundle
connection status menu).
Network PDV or lost frames
No active station on the LANCheck that at least one station is active on the LAN.
Cable problem
Problem on the LANCheck LAN media.
Defective EV kitReplace the EV kit if a failure is detected.
DS34S132 Evaluation Kit
Evaluates: DS34S132
Check the EV kit port configuration (autonegotiation,
rate, duplex mode) and check Ethernet PM.
Check the timing settings.
Check PDV introduced by the network, and, if necessary, increase differential time (PDVT) setting.
Check network delay and try to decrease it. Try to
decrease differential time (PDVT).
Decrease Ethernet packet size by changing bundle
configuration.
Check and replace, if necessary, the cable that connects the EV kit UPLINK connector to the LAN.
61Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Appendix A. Connector Wiring
A.1 E1/T1 and External Clock Connectors
The E1/T1 and external clock interfaces of the DS34S132
EV kit terminate in 8-pin RJ45 connectors, wired in
accordance with Table A-1.
A.3 ASCII Terminal Connector
The control terminal interface terminates in a V.24/
RS-232, 9-pin, D-type female DCE connector, wired in
accordance with Table A-3.
A.2 Ethernet Connectors
The Ethernet uplink and Ethernet management electrical
interfaces terminate in 8-pin RJ45 connectors, wired in
accordance with Table A-2.
Table A-1. E1/T1 and External Clock Interface Connector Pinout
PINDESIGNATIONDIRECTIONFUNCTION
1RD (R)InputReceive data (ring)
2RD (T)InputReceive data (tip)
3, 6——FGND
4TD (R)OutputTransmit data (ring)
5TD (T)OutputTransmit data (tip)
7, 8—N/ANot connected
Table A-2. Ethernet Connector PinoutTable A-3. Control Interface Pinout
PINFUNCTION
1Tx+
2Tx3Rx+
6Rx-
4, 5, 7, 8—
PINFUNCTION
1–
2Tx
3Rx
4—
5GND
6, 7, 8—
62 Maxim Integrated
DS34S132 Evaluation Kit
Evaluates: DS34S132
Revision History
REVISION
NUMBER
05/11Initial release—
REVISION
DATE
DESCRIPTION
PAGES
CHANGED
Maxim Integrated cannot assume responsibility for use of any circuitry other than circuitry entirely embodied in a Maxim Integrated product. No circuit patent
licenses are implied. Maxim Integrated reserves the right to change the circuitry and specifications without notice at any time. The parametric values (min and
max limits) shown in the Electrical Characteristics table are guaranteed. Other parametric values quoted in this data sheet are provided for guidance.
Maxim Integrated 160 Rio Robles, San Jose, CA 95134 USA 1-408-601-1000 63