Professional Documents
Culture Documents
The E-carrier system uses European 30 -channel pulse code modulation (PCM), which is also
called E1.
Working Mode
E-carrier interfaces can work in any of the following modes:
l Channelized mode: It is a framed mode in which all timeslots can be allocated to
multiple channels.
l Unchannelized mode: It is a framed mode in which all timeslots can be bundled only
once and allocated to only one channel.
l Clear channel mode: It is also called an unframed mode. There is no frame flag in the
data stream, and all bits in the data stream are data. The data in the data stream belongs
to only one channel.
Introduction to E1 Interfaces
A physical interface that is formed by E1 and can work only in clear channel is an E1
interface. A physical interface that is formed by E1 and can work in unchannelized or
channelized mode is a CE1 interface.
l In clear channel mode, or unframed mode:
An E1 interface forms a synchronous serial interface without timeslot division and with a
transmission rate of 2.048 Mbit/s. The E1 interface has the same logical features as a
synchronous serial interface. It supports link-layer protocols, such as PPP, TDM ,
HDLCand ATM, MP bundling,and network protocols, such as IP.
l In unchannelized mode, or framed mode:
A CE1 interface is physically divided into 31 timeslots numbered from 1 to 31. The
timeslots can be bundled once into one channel. For example, if timeslots 1 and 2 are
bundled into a serial interface of 128 kbit/s, the remaining timeslots cannot be bundled.
The serial interface has the same logical features as a synchronous serial interface. It
supports link-layer protocols, such as PPP, TDM , HDLCand ATM, MP bundling,and
network protocols, such as IP.
l In channelized mode, or framed mode:
A CE1 interface is physically divided into 31 timeslots numbered from 1 to 31. The
timeslots can be randomly bundled to form logical channels, each with a transmission
rate of N x 64 kbit/s.
All the timeslots can be grouped into multiple channel-sets. Each bundled channel-set of
timeslots is used as an interface with the same logical features as a synchronous serial
interface. It supports link-layer protocols, such as PPP, TDM , HDLCand ATM, MP
bundling,and network protocols, such as IP.
l In clear channel mode, also called the unframed mode, a CE3 interface functions like an
interface with the transmission rate of 34.368 Mbit/s and without timeslot division. The
CE3 interface has the same logical features as a synchronous serial interface and
supports link-layer protocols (such as PPP and HDLC).
l In unchannelized mode, also called the framed mode, all timeslots of a CE3 interface are
bundled to form a serial interface with the transmission rate of 32.768 Mbit/s. The serial
interface supports link-layer protocols (such as PPP and HDLC).
Precautions
Before you use a E1 interface to carry upper-layer services, configure the E1 interface. Note
that:
l If a physical interface has no cable connected, run the shutdown command to disable
this interface to prevent interference with the interface.
l After you configure services on an interface, run the shutdown and then undo
shutdown commands in the current interface view to ensure that the configured services
are loaded onto the interface.
NOTICE
Running the shutdown command in a E1 interface view will disable the E1 interface and may
affect the normal operation of its channel-sets.
Pre-configuration Tasks
Before configuring a E1 interface, power on the device and ensure that it is working properly.
Context
An E1 interface can form serial interfaces with different transmission rates:
Procedure
l Create a serial interface that works in clear channel mode.
a. Run system-view
The system view is displayed.
b. Run controller e1 controller-number
The E1 interface view is displayed.
c. Run using e1
The E1 interface is configured to work in clear channel mode, establishing a serial
interface without timeslot division and with a transmission rate of 2.048 Mbit/s.
You can run the interface serial controller-number:0 command to enter the serial
interface view.
d. Run commit
The configuration is committed.
l Create a serial interface that works in channelized mode.
a. Run system-view
The system view is displayed.
b. Run controller e1 controller-number
The E1 interface view is displayed.
c. Run using ce1
The interface is configured to work in channelized mode.
d. Run channel-set set-number timeslot-list slot-list
A serial interface with a transmission rate of N x 64 kbit/s is created. N stands for
the number of bundled timeslots.
To change the working mode of an E1 interface:
n Delete serial interfaces and their configurations and channelization
configurations before you run the using e1 command to switch an E1 interface
from the channelized mode to the clear channel mode.
n Delete clear channel configurations and serial interface configurations before
you run the using ce1 command to switch an E1 interface from the clear
channel mode to the channelized mode.
You can run the interface serial controller-number:set-number command to enter
the serial interface view.
e. Run commit
The configuration is committed.
Context
A CE1 interface works in either of the following clock modes:
l Master clock mode: In master clock mode, a CE1 interface uses internal clock signals.
l Slave clock mode: In slave clock mode, a CE1 interface uses line clock signals.
When CE1 interfaces of two NE20Es are directly connected, you must configure one interface
to work in master clock mode and the other interface in slave clock mode. When the CE1
interface of the NE20E is connected to a transmission device, you must configure this
interface to work in slave clock mode and use the clock signals provided by the transmission
device.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run controller e1 controller-number
The CE1 interface view is displayed.
Step 3 Run clock { master | slave }
A clock mode is configured for the CE1 interface.
Step 4 Run commit
The configuration is committed.
----End
Context
You can configure the frame format for a CE1 interface only when it works in channelized
mode.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run controller e1controller-number
When setting the frame format of a CE1 interface, ensure that the local and remote ends are configured
with the same frame format.
----End
Context
The loopback function has two types:
l Local loopback: is used to locate a system fault.
l Remote loopback: is used to locate a link fault or test the quality of a link.
l To enable local loopback on an E1 interface, ensure that the clock of the E1 interface works in
master mode.
l To enable remote loopback on an E1 interface, ensure that the clock of the E1 interface works in
slave mode.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run controller e1 controller-number
The E1 interface view is displayed.
Step 3 Run loopback { local | remote } [ autoclear period hold-time ]
The loopback function is enabled on the E1 interface.
To enable the E1 interface to delete the loopback configuration after a specified period,
specify autoclear period hold-time in the command. This function takes effect when
loopback is enabled. After the time specified by hold-time elapses, the loopback configuration
is automatically deleted.
Step 4 Restart the E1 interface.
1. Run shutdown
After the configuration is complete, the configuration takes effect only after the interface is restarted.
----End
Procedure
Step 1 Run system-view
The thresholds for triggering and clearing an ES-TCA alarm are set.
----End
Prerequisites
A CE1 interface has been configured.
Procedure
l Run the display interface serial [ interface-number ] command to check the status and
statistics of a serial interface.
Precautions
When configuring E3 interfaces to carry upper-layer services, note the following:
l If an E3 interface on the device is idle (no cable is connected to the interface), run the
shutdown command to shut down the E3 interface to prevent it from being interfered.
l After configuring services on an E3 interface, run the shutdown and then undo
shutdown commands in the interface view for the services to take effect.
l The shutdown and undo shutdown commands run on an E3 interface also take effect
with the serial interface created on the E3 interface. However, the shutdown and undo
shutdown commands run on a serial interface takes effect only with the serial interface.
Pre-configuration Tasks
Before configuring an E3 interface, power on the device and ensure that the self-check
succeeds.
Context
Depending on the E3 interface working modes, you can create the following two types of
synchronous serial interfaces on an E3 interface:
l If the E3 interface works in clear channel mode, an unframed synchronous serial
interface with a bandwidth of 34.368 Mbit/s is created.
l If the E3 interface works in unchannelized mode, a synchronous serial interface with a
bandwidth of 33.831 Mbit/s is created after you manually create a framed E3 channel.
By default, an E3 interface works in unchannelized mode.
This configuration process is supported only on the Admin-VS.
Procedure
l Create a synchronous serial interface on an E3 interface working in clear channel mode.
a. Run system-view
The system view is displayed.
b. Run controller e3 controller-number
The specified E3 interface view is displayed.
c. Run using e3
The E3 interface is configured to work in clear channel mode, and an unframed
synchronous serial interface with a bandwidth of 34.368 Mbit/s is created.
After the synchronous serial interface is created, you can run the interface serial
controller-number command to display the view of the synchronous serial interface.
d. Run commit
The configuration is committed.
l Create a synchronous serial interface on an E3 interface working in unchannelized mode.
a. Run system-view
The system view is displayed.
b. Run controller e3 controller-number
The specified E3 interface view is displayed.
c. Run using ce3
The E3 interface is configured to work in unchannelized mode.
d. Run e3 framed
A framed E3 channel is created, and an unframed synchronous serial interface with
a bandwidth of 33.831 Mbit/s is created.
After the synchronous serial interface is created, you can run the interface serial
controller-number command to display the view of the synchronous serial interface.
e. Run commit
The configuration is committed.
----End
Context
Loopback can be either local loopback or remote loopback.
l To locate a system fault, enable local loopback on an E3 interface.
l To locate a link fault or test the link quality, enable remote loopback on an E3 interface.
NOTICE
Local loopback must be configured in master clock mode, and remote loopback must be
configured in slave clock mode.
Running the loopback command will cause interfaces or links unable to work properly.
Therefore, exercise caution when running the loopback command. After checking the
interface or link status, immediately run the undo loopback command to disable loopback.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run controller e3 controller-number
The view of the E3 interface to be checked is displayed.
Step 3 Run loopback { local | remote }
Loopback is enabled on the E3 interface.
Note the following when enabling loopback on an interface:
l The interface that has local loopback enabled must work in master clock mode.
l The interface that has remote loopback enabled must work in slave clock mode.
By default, loopback is disabled.
Step 4 Run commit
The configuration is committed.
----End
Context
An E3 interface has two clock modes:
l Master clock mode: The E3 interface uses internal clock signals.
l Slave clock mode: The E3 interface uses clock signals provided by an external device.
When two routers are directly connected through E3 interfaces, configure one E3 interface as
the master clock and the other E3 interface as the slave clock.
By default, an E3 interface works in master clock mode.
Perform the following steps on a router.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run controller e3 controller-number
The specified E3 interface view is displayed.
Step 3 Run clock { master | slave }
The clock mode of the E3 interface is configured.
Step 4 Run commit
----End
Procedure
Step 1 Run the display controller e3 [ controller-number ] command to check E3 interface
configurations.
----End
Context
When faults occur on a CE1 interface, you can run the test connectivity controller e1
command for fault locating.
Prerequisites
The serial interface service has been configured.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run test connectivity controller e1 controller-number { unframed | channelized timeslot-
list slot-list } duration time
The bit error rate is tested on a specified CE1 interface.
----End
Networking Requirements
On the network shown in Figure 4-1, Device A and Device B need to communicate with each
other through E1 interfaces.
In this example, interface1 and interface2 represent E1 0/1/0 and E1 0/2/0, respectively.
Configuration Roadmap
The configuration roadmap is as follows:
1. Create synchronous serial interfaces.
2. Create the mp-group.
3. Bundle the synchronous serial interfaces into the mp-group.
4. Restart all the interfaces to make the configuration take effect.
Data Preparation
To complete the configuration, you need the following data:
l E1 interface number of Device A
l E1 interface number of Device B
l Mp-group number of Device A
l Mp-group number of Device B
Procedure
Step 1 Create a synchronous serial interface on Device A.
# Configure the E1 interface on Device A as a synchronous serial interface.
<HUAWEI> system-view
[~HUAWEI] sysname DeviceA
[*HUAWEI] commit
[~DeviceA] controller e1 0/1/0
[~DeviceA-E1 0/1/0] using e1
[*DeviceA-E1 0/1/0] commit
[~DeviceA-E1 0/1/0] quit
Step 4 Restart all the interfaces to make the configuration take effect.
# Restart the synchronous serial interface on Device A.
[~DeviceA] interface serial 0/1/0:0
[~DeviceA-Serial0/1/0:0] undo shutdown
[*DeviceA-Serial0/1/0:0] commit
[~DeviceA-Serial0/1/0:0] quit
----End
Configuration Files
l Device A configuration file
#
sysname DeviceA
#
controller E1 0/1/0
using e1
undo shutdown
#
interface Serial0/1/0:0
link-protocol ppp
ppp mp mp-group 0/1/1
undo shutdown
#
interface mp-group 0/1/1
ip address 10.1.1.1 255.255.255.0
#
return
l Device B configuration file
#
sysname DeviceB
#
controller E1 0/2/0
using e1
undo shutdown
#
interface Serial0/2/0:0
link-protocol ppp
ppp mp mp-group 0/2/1
undo shutdown
#
interface mp-group 0/2/1
ip address 10.1.1.2 255.255.255.0
#
return
Networking Requirements
On the network shown in Figure 4-2, Device A and Device B need to communicate with each
other through CE1 interfaces.
In this example, interface1 and interface2 represent CE1 0/1/0 and CE1 0/2/0, respectively.
Configuration Roadmap
The configuration roadmap is as follows:
1. Create synchronous serial interfaces.
2. Create the mp-group.
3. Bundle the synchronous serial interfaces into the mp-group.
4. Restart all the interfaces to make the configuration take effect.
Data Preparation
To complete the configuration, you need the following data:
l CE1 interface number of Device A
l CE1 interface number of Device B
l Mp-group number of Device A
l Mp-group number of Device B
The timeslot channels of the serial interfaces on Device A must be the same as those on Device B.
Procedure
Step 1 Create synchronous serial interfaces.
# Configure the CE1 interface on Device A as a synchronous serial interface.
<HUAWEI> system-view
[~HUAWEI] sysname DeviceA
[*HUAWEI] commit
[~DeviceA] controller e1 0/1/0
[~DeviceA-E1 0/1/0] channel-set 1 timeslot-list 1-15
[*DeviceA-E1 0/1/0] commit
[~DeviceA-E1 0/1/0] quit
Step 4 Restart all the interfaces to make the configuration take effect.
# Restart the synchronous serial interface on Device A.
[~DeviceA] interface serial 0/1/0:1
[~DeviceA-Serial0/1/0:1] undo shutdown
[*DeviceA-Serial0/1/0:1] commit
[~DeviceA-Serial0/1/0:1] quit
----End
Configuration Files
l Device A configuration file
#
sysname DeviceA
#
controller E1 0/1/0