DS34S132GNA2+ Maxim Integrated, DS34S132GNA2+ Datasheet - Page 31

• Manufacturer Part Number: DS34S132GNA2+
• Description: Communication ICs - Various 32Port TDM-Over-Pack Transport Device
• Manufacturer: Maxim Integrated

Specifications of DS34S132GNA2+

• Rohs: yes
• Part # Aliases: 90-34S13+2N2

The most generalized TDMoP PW application recovers TDM timing from a TDMoP PW packet stream. However,
for some applications the timing/rate of the TDMoP PW payload data is synchronized to a distributed, common
clock reference at both ends of the PW and clock recovery is not required (e.g. for synchronous T1/E1 data
streams). For these cases the Transmit TDM Port can use an external clock signal instead of a Clock Recovery
Engine (none of the Bundles associated with that TDM Port include an RXP PW-Timing Connection). This special
application (synchronous T1/E1 data streams) should not be confused with the DCR mode that uses a Common
Clock to drive a Clock Recovery Engine that recovers the timing of a T1/E1 data stream that may be asynchronous.
Only SAT/CES Bundle/PWs can include PW-Timing. HDLC and CPU packet streams (including those for OAM
Bundles) should not be used for PW-Timing since these packet types do not provide a constant bit rate.
9.1.4 CPU Connections
CPU Connections provide the CPU with the ability to send and receive Ethernet packets. CPU Connections can be
used for VCCV connections that are used to establish and monitor PWs, for Ethernet OAM (e.g. MEF OAM), for
specialized Ethernet protocols (e.g. ARP) and for detecting unexpected or invalid packet types. The different types
of CPU Connections that are supported are listed below. The CPU Connections are described in more detail in the
“CPU Packet Classification” and “TXP CPU Packet Generation” sections.
The CPU Connection is diagramed in
Figure 9-6. CPU Connections
The S132 supports optional OAM Timestamps. The OAM Timestamps are independent of the RTP header
Timestamps (PW-Timing Connections). In the RXP direction the S132 records when each RXP CPU packet is
received and forwards an RXP Local Timestamp with each packet that is forwarded to the CPU. This RXP Local
Timestamp is always enabled for all CPU packet types (the CPU can ignore the RXP Local Timestamp if the
information is not relevant). In the TXP direction, the S132 can be programmed to add a TXP OAM Timestamp to
any outgoing CPU packet (e.g. for TDMoIP-VCCV-OAM header according to RFC5087 Appendix D).
19-4750; Rev1; 7/11
S132
Debug “Normal” Bundle
OAM Bundle
CPU Destination Ethernet Type
MEF OAM Ethernet Type
In-band VCCV OAM
CPU
Figure
Too many MPLS Labels
Unknown Ethernet DA
Unknown PW-ID
Unknown UDP Protocol
Unknown IP Protocol
RXP CPU Queue
TXP CPU Queue
9-6.
RXP Local T-stamp Gen
TXP OAM T-stamp Gen
TXP Pkt Generator
RXP Pkt Classifier
ARP with known IP DA
ARP with unknown IP DA
Unknown Ethernet Type
Unknown IP DA
Ethernet Broadcast DA
DS34S132 DATA SHEET
31 of 194