IBM3229P2035
Advance
IBM Packet Routing Switch Serial Interface Converter
3.7.1.1 Normal Operating Mode
Data sent by the PE to the switch core is transferred to the ingress interface where it is parity checked, LU
formatted, and queued to both planes for transmission by the DASL. Data transmitted by the switch core is
checked for framing consistency, header parity, queued, and word formatted for transmission by the egress
interface to the PE.
Figure 17: Configuration in Normal Operating Mode
Y
IBM Packet Routing Switch Serial Interface Converter
X
X/Y
Ingress
Egress
DASL
DASL
X
Y
IBM 28.4 G
Packet
Routing
Protocol
Engine
Switch
X/Y
(Switch Core)
3.7.1.2 Protocol Engine X/Y Loopback
Protocol engine X/Y loopback provides a connection from the ingress protocol engine bus to the egress
protocol engine bus. This loopback mode can be activated on either path X or path Y but not on both simulta-
neously. The converter in loopback mode is internally disconnected from the DASL macro for both the data
and control buses and does not test the DASL macro. The loopback is initiated on a packet boundary.
Note: A switch plane (or substitute) clock must be present on the converter’s switch interface.
Figure 18: Protocol Engine Loopback Through Path X or Path Y
IBM Packet Routing Switch Serial Interface
Y
X
X/Y
Ingress
Egress
DASL
DASL
X
Y
IBM 28.4 G
Packet
Routing
Switch
Protocol
Engine
X/Y
Perform the following to execute the PE X/Y domain loopback (starting from operational mode):
1. Reset the path to be set in loopback.
2. Force X or Y switch plane in service (switch control can also decide in this mode).
3. Select the clock source (switch or microprocessor) for the plane to be wrapped.
4. Set the PE loopback bit corresponding to the plane to be set in loopback.
5. Initiate the traffic from the PE.
prssi.02.fm
Functional Description
Page 43 of 154
March 1, 2001
IBM [ IBM ]
