Chapter 7. Node and Terminal Plug-ins
Vol. IV-7-46 Alcatel-Lucent
MXC DAC ES to SDH mux Ethernet LAN card).
- The TVT mode is not compatible with byte synchronous mapping,
though if a byte synchronous payload is injected into the 9500 MXC
network through a DAC 155oM, it should be configured for TVT to try
to preserve the byte alignment. Note however that if this payload is
delivered through a DAC 16x or DAC 4x it will lose its byte boundary.
(Byte synchronous mapping synchronizes both rate and framing of an
E1/DS1 signal to the SDH signal, meaning G.704 framing is required on
the E1/DS1 signals).
10. Enter a name (optional - recommended) for the module by right-clicking in
the relevant DATA module in the System Summary screen, selecting
Rename, and typing. The default name is ‘unnamed’.
11. To commit the configuration, click
Send.
Next Step: Go to the Circuits screen to configure circuit cross-connects. Refer to
Procedure for Configuring Circuits - Traffic on page 9-9, Volume IV, Chapter 9.
DAC ES and IDU ES Configuration
This section applies to the DAC ES and to configuration of the Ethernet module
of the IDU ES. Their Ethernet ‘engines’ are identical.
Both support 10/100Base-T traffic for transparent (broadcast), mixed, or VLAN
operation.
• DAC ES traffic can be directed over Link (RAC), Ring (RAC), or Data (DAC
155oM) links.
• IDU ES traffic can only be carried over the radio Link.
DAC ES Configuration Screen
Figure 7-12 shows a typical DAC ES Plug-ins screen. The same screen supports
the Ethernet module in the IDU ES.
To Next Page
Loading...
