01-05 CPOS Interface Configuration

HUAWEI NetEngine40E Universal Service Router
Configuration Guide - WAN Access 5 CPOS Interface Configuration
5 CPOS Interface Configuration
About This Chapter
CPOS interfaces are used to aggregate multiple E1 links to improve low-speed access.
5.1 Overview of CPOS Interfaces

This section describes packet over SONET/SDH (POS) and channelized POS (CPOS)
interfaces in terms of the basic concepts of synchronous optical network (SONET) and
synchronous digital hierarchy (SDH), channelization and non-channelization, and SDH frame
structure.
5.2 Configuring a CPOS Interface
Before you configure a channelized packet over SONET/SDH (CPOS) interface, familiarize
yourself with the usage scenario and complete the pre-configuration tasks. Here, SDH stands
for synchronous digital hierarchy.
5.3 Configuring a CPOS-Trunk Interface
Configuring a CPOS-Trunk interface includes creating a CPOS-Trunk interface, adding a
CPOS interface to the CPOS-Trunk interface, and creating a trunk serial interface on the
CPOS-Trunk interface.
5.4 Maintaining a CPOS Interface
You can test the bit error rate of a CPOS E1 link to maintain the CPOS interface.
5.5 Configuration Examples for CPOS Interfaces
This section provides CPOS configuration examples.
5.1 Overview of CPOS Interfaces

This section describes packet over SONET/SDH (POS) and channelized POS (CPOS)
interfaces in terms of the basic concepts of synchronous optical network (SONET) and
synchronous digital hierarchy (SDH), channelization and non-channelization, and SDH frame
structure.
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 42

Introduction to SONET and SDH

SONET is a synchronous digital transmission standard defined by the American National
Standards Institute (ANSI) and mainly used in North America and Japan. Clocks at each
network level are synchronized with a very precise master clock.
SONET defines the line rate hierarchical structure of synchronous transmission for the optical
transmission system. The basic SONET transmission rate is 51.84 Mbit/s:
l An electrical signal with the transmission rate is called Level 1 Synchronous Transport
Signal (STS-1).
l An optical signal with the transmission rate is called Level 1 Optical Carrier (OC-1).
SONET, which uses synchronous signals, can easily multiplex signals.
SONET-based SDH is an international standard defined by the International

Telecommunication Union Telecommunication Standardization Sector (ITU-T) and mainly
used in Europe. The corresponding SDH standard is based on the proposals from G.707 to G.
709 passed in 1988 and the proposals added in 1992.
SDH is similar to SONET to a great extent. The basic transmission rate of SDH is 155.52
Mbit/s, which is called Level 1 Synchronous Transfer Module (STM-1). This rate equals the
OC-3 rate in SONET.
SDH, which uses synchronous multiplexing and flexible mapping, can multiplex or
demultiplex low-speed tributary signals from SDH signals without using many multiplexing
or demultiplexing devices. SDH reduces signal consumption and equipment investment.
Table 5-1 lists the common SONET and SDH transmission rates. For convenience, the
approximations of these transmission rates are placed in the parentheses.
Table 5-1 Common SONET and SDH transmission rates

SONET SDH Transmission Rate
(Mbit/s)
Electrical Optical Signal Optical Signal
Signal
STS-1 OC-1 - 51.840
STS-3 OC-3 STM-1 155.520 (155)
STS-9 OC-9 STM-3 466.560
STS-12 OC-12 STM-4 622.080 (622)
STS-18 OC-18 STM-6 933.120
STS-24 OC-24 STM-8 1244.160
STS-36 OC-36 STM-12 1866.240
STS-48 OC-48 STM-16 2488.320 (2.5 Gbit/s)
STS-96 OC-96 STM-32 4876.640
STS-192 OC-192 STM-64 9953.280 (10 Gbit/s)

Channelization and Unchannelization

When SDH signals are formed by multiplexing low-speed tributary signals, these tributary
signals are called channels.
Channelization means that multiple independent channels of data are transmitted over an
optical fiber by using low-speed tributary STM-N signals. During the transmission, each
channel has its own bandwidth and start and end points and follows its own monitoring
policy.
Unchannelization means that all data is transmitted through a single channel over an optical
fiber by using all STM-N signals. During the transmission, all the data has the same ID and
start and end points and follows the same monitoring policy.
Channelization can utilize bandwidth more efficiently by transmitting multiple channels of

low-speed signals. Unchannelization is used to transmit a single channel of high-speed
signals.
Introduction to Channelized Serial Interfaces

The serial interface formed by a CPOS interface is called a channelized serial interface, which
has the same logical features as a synchronous serial interface.
An E1 channel of a CPOS interface can work in either clear channel mode (unframed mode)
or channelized mode:
l In clear channel mode, an E1 channel without timeslot division forms a 2.048 Mbit/s
serial interface.
The naming convention for a serial interface is "serial interface-number/e1-number:0,"
where interface-number specifies the name of the CPOS interface, and e1-number
specifies the number of the E1 channel.
l In channelized mode, 31 timeslots across an E1 channel, excluding timeslot 0, can be
randomly bundled into serial interfaces.
The naming convention for a channelized serial interface is "serial interface-number/e1-
number:set-number," where interface-number specifies the name of the CPOS interface,
e1-number specifies the number of an E1 channel, and set-number specifies the number
of the interface formed by bundling the timeslots of the E1 channel.
The NE40E supports only STM-1 Channelized POS.
Pos andCPOS
POS applies to metropolitan area networks (MANs) and wide area networks (WANs) and
supports packet data, such as IP packets.
CPOS interfaces make full use of the SDH system and have the following functions:
l Perform refined division of bandwidth.
l Reduce the number of low-speed physical ports required on a router.
l Enhance the aggregation capability of the low-speed interfaces of a router.
l Improve the dedicated line access capability of a router.

SDH Frame Structure

This section describes the frame structure of an SDH signal, that is, the structure of an STM-
N frame.
To add or drop low-speed tributary signals to or from high-speed signals, try to distribute
tributary signals in the frame evenly and regularly. The ITU-T regulates that STM-N frames
are rectangular and expressed in bytes, as shown in Figure 5-1.
Figure 5-1 STM-N frame structure
STM-N is a frame with the dimension of 9 rows x 270 x N columns. Here, N is the same as
that in STM-N, indicating how many STM-1 signals are multiplexed to this STM-N signal.
An STM-N frame consists of the following parts:
l Section overhead (SOH): includes regenerator section overhead (RSOH) and multiplex
section overhead (MSOH).
l Administration unit pointer (AU-PTR): is the pointer that specifies the first byte of the
payload. The receiver can correctly extract the payload based on the location of the
pointer.
l Payload
Related Concepts
l Multiplexing units: Basic SDH multiplexing units include container (C-n), virtual
container (VC-n), tributary unit (TU-n), tributary unit group (TUG-n), administrative
unit (AU-n), and administrative unit group (AUG-n). Here, n stands for the number of
the unit level.
l Container: It is used to carry service signals that are transmitted at different rates. G.709
defines specifications for five types of standard containers: C-11, C-12, C-2, C-3, and
C-4.

l VC: It is an information terminal of SDH channels and is used to support connections

between SDH channel layers. VCs are classified as lower-order VCs or higher-order
VCs. VC-3 in AU-3 and VC-4 are higher-order VCs.
l TU and TUG: A TU provides adaptation between lower-order and higher-order path
layers. A collection of TUs, occupying a fixed position in the payload of the higher-order
VC, is called a TUG.
l AU and AUG: An AU provides adaptation between higher-order channel layer and
multiplex section layer. A collection of AUs, occupying a fixed position in the payload
of STM-N, is called an AUG.
Multiplexing E1 to STM-1
In the SDH multiplexing process outlined in the G.709 recommendation, there is more than
one multiplexing path from a valid payload to STM-N. Figure 5-2 shows the multiplexing
process from E1 to STM-1.
Figure 5-2 E1 to STM-1 multiplexing process
In practice, different countries and regions may use different multiplexing paths.
Calculation of E1 Path Sequence Numbers

CPOS interfaces use the byte interleave multiplexing mode so that the lower-order VCs in a
higher-order VC are not arranged in sequence. To facilitate configuration, the following
section uses E1 in CPOS with the AU-4 multiplexing path as an example to demonstrate the
TU number calculation method.
The multiplexing process in Figure 5-3 shows that the 2 Mbit/s multiplexing structure is
3-7-3 when the AU-4 multiplexing path is used. The following formula shows how to
calculate the TU-12 numbers located in different positions in a VC-4:
VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21
In a VC-4, all TUG-3s are numbered the same; all TUG-2s are numbered the same; two
TU-12s with a number difference of 1 are adjacent.

l The numbers listed in the preceding formula stand for the positions in a VC-4 frame.
l The TUG-3 number ranges from 1 to 3; the TUG-2 number ranges from 1 to 7; the TU-12 number
ranges from 1 to 3.
l The TU-12 number indicates which one of the 63 TU-12s is in the VC-4 frame based on the
sequence and also indicates the E1 channel number.
Figure 5-3 Sequence for arranging TUG-3, TUG-2, and TU-12 in a VC-4 frame
If the AU-3 multiplexing path is used, the TU-12 number calculation can be deduced in a
similar manner.
If 63 E1 channels are configured on a CPOS interface, these channels can be directly
numbered from 1 to 63. If a router of Huawei is connected to a channelized STM-1 interface
of a router from another vendor, take note of the differences in channel numbers.
Overhead Bytes
SDH provides monitoring and management at layers. Monitoring is classified as section
monitoring or path monitoring. Section monitoring is classified as regenerator section
monitoring or multiplex section monitoring. Path monitoring is classified as higher-order path
monitoring or lower-order path monitoring. Different overhead bytes help to implement the
monitoring functions.
This section describes only the SDH overhead bytes used in configuration.

l SOH
SOH consists of RSOH and MSOH.
The payload of an STM-N frame contains the path overhead (POH) that monitors low-
speed tributary signals.
J0, the regenerator section trace byte, is contained in RSOH. This byte is used to transmit
the service access point identifiers (SAPIs) repeatedly to check the connection between
the receiver and the transmitter. The byte can be any character in a carrier's network,
whereas the J0 bytes of the receiver and transmitter must match each other at the border
of two carriers' networks. With the J0 byte, a carrier can locate and rectify faults in
advance to speed up network recovery.
l Path overhead
SOH monitors section layers, whereas POH monitors path layers. POH is classified as
lower-order path overhead or higher-order path overhead.
The higher-order path overhead monitors the paths at VC-4 and VC-3 levels.
J1, the higher-order VC-N path trace byte, is contained in the higher-order path
overhead. Similar to J0, J1 is used to transmit SAPIs repeatedly to check the connection
between the receiver and the transmitter. The J1 bytes of the receiver and transmitter
must match each other.
C2, the path signal label byte, is contained in higher-order path overhead. C2 is used to
specify the multiplexing structure and the attributes of the information payload in a VC
frame, including whether the path is loaded with services, service types, and the mapping
mode. The C2 bytes of the receiver and transmitter must match each other.
CPOS Interface Types

As shown in Figure 5-4, some governmental agencies and enterprises use low-end and mid-
range devices to access the transmission network over E1 leased lines. Users with bandwidth
requirements between E1 and T3 (44 Mbit/s), such as data centers, use several E1 leased lines
simultaneously.
The bandwidth of these users aggregates on one or more CPOS interfaces over the
transmission network. CPOS interfaces are then connected to the high-end device that
identifies each low-end device based on timeslots.
Figure 5-4 Networking diagram of typical CPOS implementation

In practice, there may be more than one level of transmission networks between CPOS
interfaces and low-end devices. Other transmission devices are needed to relay
communication between low-end devices and transmission networks. Logically, such an
implementation is equivalent to the networking mode in which each low-end device is
connected to Device A over an E1 leased line or N x E1 leased lines.
5.2 Configuring a CPOS Interface

Before you configure a channelized packet over SONET/SDH (CPOS) interface, familiarize
yourself with the usage scenario and complete the pre-configuration tasks. Here, SDH stands
for synchronous digital hierarchy.
Usage Scenario
Before you use the serial interfaces formed by the E1 channels of a CPOS interface to
transmit packets, configure the physical attributes and E1 channels of the CPOS interface.
Pre-configuration Tasks
Before configuring a CPOS interface, power on the device and ensure that it is working
properly.
5.2.1 Configuring the Working Mode of a CPOS Interface

A CPOS interface can work in either clear channel mode or channelized mode. Synchronous
serial interfaces with different transmission rates can be generated in the two modes to meet
different bandwidth requirements of services.
Context
If a CPOS interface works in clear channel mode, synchronous serial interfaces with higher
transmission rates can be generated, so that the CPOS interface can provide sufficient
bandwidth for service bearer.
If a CPOS interface works in channelized mode, the E1 channels of the CPOS interface can
generate synchronous serial interfaces with different transmission rates when they work in
different modes:
l In clear channel mode, an E1 channel functions as a synchronous serial interface without
timeslot division and with a transmission rate of 2.048 Mbit/s.
l In channelized mode, an E1 channel is divided into 32 timeslots numbered from 0 to 31.
Timeslots 1 to 31 can be randomly bundled to generate logical channels with
transmission rates of N x 64 kbit/s.
Procedure
l Configure a CPOS interface to work in channelized mode.
– Configure an E1 channel of the CPOS interface to work in clear channel mode so
that a trunk serial interface is generated.
i. Run system-view
The system view is displayed.

ii. Run controller cpos cpos-number

The CPOS interface view is displayed.
iii. Run e1 e1-number unframed
The specified E1 channel is configured to work in clear channel mode, and a
serial interface with a transmission rate of 2.048 Mbit/s is created.
By default, an E1 channel works in channelized mode.
In VS mode, this command is supported only by the admin VS.
After the serial interface is created, you can run the interface serial cpos-
number/e1-number:0 command to enter the serial interface view.
iv. Run commit
The configuration is committed.
– Configure an E1 channel of a CPOS interface to work in channelized mode so that a
trunk serial interface in channelized mode can be generated.
i. Run system-view
ii. Run controller cpos cpos-number
iii. Run e1 e1-number channel-set set-number timeslot-list { slot-list [ ts0 ] |
[ ts0 ] }
The specified timeslots of the specified E1 channel are bundled to generate a
serial interface with a transmission rate of N x 64 kbit/s. N indicates the
number of bundled timeslots.
In VS mode, this command is supported only by the admin VS.
After the serial interface is configured, you can run the interface serial cpos-
number/e1-number:set-number command to enter the serial interface view.
iv. Run commit
l Configure a CPOS interface to work in clear channel mode.
a. Run system-view
b. Run controller cpos cpos-number
c. Run using vc4
The CPOS interface is configured to work in clear channel mode, and a
synchronous serial interface is created on the CPOS interface. The synchronous
serial interface transmits data at 150.336 Mbit/s, without timeslot division.
After the synchronous serial interface is created, you can run the interface serial
cpos-number/0:0 command to enter the serial interface view.
d. Run commit

5.2.2 Configuring the Clock Mode for a CPOS Interface

A CPOS interface works in either master clock mode or slave clock mode. You can configure
the clock mode for a CPOS interface.
Context
A CPOS interface supports the following clock modes:
l Master clock mode: uses internal clock signals.

l Slave clock mode: uses line clock signals.
When a CPOS interface is connected to an SDH device, configure the CPOS interface to work
in slave clock mode because the precision of the clock in the SDH network is higher than the
precision of the internal clock source of the CPOS interface.
Procedure
Step 1 Run system-view
Step 2 Run controller cpos cpos-number
Step 3 Run clock { master | slave }
A clock mode is configured for the CPOS interface.
Step 4 Run commit
----End
5.2.3 Configuring the Working Modes for the E1 Channels of a

CPOS Interface
This section describes how to configure the working modes for the E1 channels of a
channelized packet over SONET/SDH (CPOS) interface. Here, SONET stands for
synchronous optical network, and SDH stands for synchronous digital hierarchy.
Context
The E1 channels of a CPOS interface can form serial interfaces with different transmission
rates when they work in different modes:
l In clear channel mode, an E1 channel functions as a serial interface without timeslot
division and with a transmission rate of 2.048 Mbit/s.
l In channelized mode, an E1 channel is divided into 32 timeslots numbered from 0 to 31.
Timeslots 1 to 31 can be randomly bundled to form logical channels with transmission
rates of N x 64 kbit/s.

Procedure
l Create a serial interface in clear channel mode.
a. Run system-view
c. Run e1 e1-number unframed
The specified E1 channel is configured to work in clear channel mode, and a serial
interface with a transmission rate of 2.048 Mbit/s is created.
By default, an E1 channel works in channelized mode.
After the serial interface is created, you can run the interface serial cpos-
number/e1-number:0 command to enter the serial interface view.
d. Run commit
l Create a serial interface in channelized mode.
a. Run system-view
c. Run e1 e1-number channel-set set-number timeslot-list { slot-list [ ts0 ] | [ ts0 ] }
The specified timeslots of the specified E1 channel are bundled to form a serial
interface with a transmission rate of N x 64 kbit/s. N indicates the number of
bundled timeslots.
After the serial interface is configured, you can run the interface serial cpos-
number/e1-number:set-number command to enter the serial interface view.
d. Run commit
5.2.4 Configuring Overhead Bytes for a CPOS Interface

SDH provides a variety of overhead bytes. You can configure overhead bytes for CPOS
interfaces to implement monitoring at different levels.
Context
SDH provides a variety of overhead bytes, which perform the monitoring function of different
levels.
l C2, the path signal label byte, is contained in the higher-order path overhead. C2 is used
to specify the multiplexing structure and the attributes of the information payload in a
VC frame.
l J0, the regenerator section trace byte, is contained in the section overhead. J0 is used to
check the continuity between two ports at the section layer.
l J1, the higher-order VC-N path trace byte, is used to check the continuity between two
ports at the path layer.

Procedure
Step 3 Perform the following commands as required.
l To configure the regenerator section trace byte J0, run:
flag j0 sdh j0
l To configure the path trace byte J1, run:

flag j1 { 1byte-mode 1byte-value | 16byte-mode 16byte-value | 64byte-mode
64byte-value }
l To configure path signal label byte C2, run:

flag c2 c2
l To configure the lower-order path signal label byte V5, run:

flag v5 1byte-mode e1 e1-list v5
l To configure the lower-order path trace byte J2, run:

flag j2 16byte-mode e1 e1-list j2
C2, J0, J1, J2 and V5 of the receiver must be the same as those of the transmitter; otherwise,
an alarm is generated.
Step 4 Run commit
----End
5.2.5 Configuring the Mapping Mode for the E1 Channels of a

CPOS Interface
CPOS interfaces support three E1 channel mapping modes: a-mode, h-mode, and l-mode.
Context
Different vendors' devices have different number calculation formulas for multiplexing CPOS
E1 to STM-1.
To enable a device to interwork with other vendors' devices using CPOS interfaces, you must
ensure that the E1 channel mapping mode on the device is the same as that on other vendors'
devices.
Procedure

Step 3 Run mapping-mode { a-mode | h-mode | l-mode }
An E1 channel mapping mode is configured for the CPOS interface.
NOTICE
Before configuring the E1 channel mapping mode of a CPOS interface, ensure that no E1
channel is created on the CPOS interface.
l a-mode:
Configures the Alcatel mode (a-mode) as the E1 channel mapping mode of a CPOS
interface. This mode applies when the E1 channel mapping mode of the interconnected
device is the Alcatel mode. In this mode, E1 channel number = (TUG-3 number – 1) x
21 + TUG-2 number + (TU-12 number – 1) x 7.
l h-mode:
Configures the Huawei mode (h-mode) as the E1 channel mapping mode of a CPOS
device is the Huawei mode. In this mode, E1 channel number = TUG-3 number +
(TUG-2 number – 1) x 3 + (TU-12 number – 1) x 21.
l l-mode:
Configures the Lucent mode (l-mode) as the E1 channel mapping mode of a CPOS
device is the Lucent mode. In this mode, E1 channel number = (TUG-3 number – 1) ×
21 + (TUG-2 number – 1) x 3 + TU-12 number
The numbers listed in the preceding formula stand for the positions in a VC-4 frame. The TUG-3
number ranges from 1 to 3; the TUG-2 number ranges from 1 to 7; the TU-12 number ranges from 1 to
3.
Step 4 Run commit
----End
5.2.6 Configuring the Clock Mode for the E1 Channels of a CPOS

Interface
An E1 channel works in either master clock mode or slave clock mode.
Context
The clock modes of different E1 channels on the same CPOS interface are independent of
each other.
When CPOS interfaces on two devices are directly connected, one E1 channel must be
configured to work in master clock mode and use internal clock signals, and the other E1
channel must be configured to work in slave clock mode and use line clock signals.

Procedure
Step 3 Run e1 e1-number set clock { master | slave }
A clock mode is configured for the E1 channel.
Step 4 Run commit
----End
5.2.7 Configuring the Frame Format for the E1 Channels of a

CPOS Interface
E1 channels support the frame format with a 4-bit CRC code.
Procedure
Step 3 Run e1 e1-number set frame-format { crc4 | no-crc4 }
A frame format is configured for the E1 channel.
NOTICE
The frame format of the E1 channel must be the same on the local and remote devices.
Step 4 Run commit
----End
5.2.8 Configuring the Loopback Function for the E1 Channels of a

CPOS Interface
You can enable the loopback function on an interface to check whether the interface or the
link works properly.

Procedure
Step 3 Run e1 e1-number set loopback { local | remote } [ autoclear period hold-time ]
A loopback mode is configured for the E1 channel.
l To enable local loopback for an E1 channel, the channel must work in master clock mode.
l To enable remote loopback for an E1 channel, the channel must work in slave clock mode.
Step 4 Run commit

----End
5.2.9 Configuring the Loopback Function for a CPOS Interface

This section describes how to configure the loopback function on a channelized packet over
SONET/SDH (CPOS) interface. Here, SONET stands for synchronous optical network, and
SDH stands for synchronous digital hierarchy. The loopback function is used to check
interface or cable status when devices are malfunctioning and must be disabled when devices
are working properly.
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 a CPOS interface, ensure that the clock of the CPOS interface works in
master mode.
This configuration process is supported only on the Admin-VS.
Procedure
Step 3 Run loopback { local | remote } [ autoclear period hold-time ]
The loopback function is enabled on the CPOS interface.

To enable the CPOS 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.
By default, the loopback function is disabled on a CPOS interface.
Step 4 Run commit
----End
5.2.10 Verifying the CPOS Interface Configuration

After you configure a channelized packet over SONET/SDH (CPOS) interface, you can check
the clock mode, frame format, overhead byte, and administrative unit group (AUG)
multiplexing path of the interface and the clock mode and frame format of its E1 channels.
Here, SONET stands for synchronous optical network, and SDH stands for synchronous
digital hierarchy.
Prerequisites
A CPOS interface has been configured.
Procedure
l Run the display interface serial [ interface-number ] command to check the status and
statistics of a serial interface.
l Run the display controller cpos [ cpos-number ] command to check the status and
configurations of a CPOS interface.
----End
5.3 Configuring a CPOS-Trunk Interface

Configuring a CPOS-Trunk interface includes creating a CPOS-Trunk interface, adding a
CPOS interface to the CPOS-Trunk interface, and creating a trunk serial interface on the
CPOS-Trunk interface.
Usage Scenario
A CPOS-Trunk interface is a logical interface that has all the functions of a CPOS interface. It
is more reliable because it has multiple CPOS interfaces bundled using the link aggregation
technology.
After a CPOS-Trunk interface is created, APS can be configured on the interface.
Pre-configuration Tasks
Before configuring a CPOS-Trunk interface, power on the device and ensure that the self-
check succeeds.

5.3.1 Creating a CPOS-Trunk Interface

Before adding a CPOS interface to a CPOS-Trunk interface, create the CPOS-Trunk interface.
Context
APS can be configured on the trunk serial interface channelized from a CPOS-Trunk interface
only after CPOS interfaces are added to the CPOS-Trunk interface.
Procedure
Step 1 Create a CPOS-Trunk interface.
1. Run system-view
2. Run interface cpos-trunk trunk-id
A CPOS-Trunk interface is created. If the CPOS-Trunk interface already exists, the
CPOS-Trunk interface view is displayed.
Step 2 Add a CPOS interface to the CPOS-Trunk interface.
1. Run controller cpos cpos-number
2. Run cpos-trunk trunk-id
The CPOS interface is added to the CPOS-Trunk interface.
Before adding a CPOS interface to a CPOS-Trunk interface, run the aps group command on the CPOS
interface to add it to an LMSP group, and configure the interface as a working interface or a protection
interface. For more details, see LMSP Configuration.
After a CPOS interface is added to a CPOS-Trunk interface, the following situations occur:
l If you run the shutdown command on the CPOS-Trunk interface, the physical status of both the
CPOS-Trunk and CPOS interfaces becomes Administratively DOWN, and the shutdown
command configuration is automatically generated for the CPOS interface in the configuration
file.
l If you run the undo shutdown command on the CPOS-Trunk interface, the undo shutdown
command configuration is automatically generated for the CPOS interface in the configuration
file.
Step 3 Run commit

----End
5.3.2 Configuring the Working Mode of a CPOS-Trunk Interface

Context
A CPOS-Trunk interface can work in either clear channel mode or channelized mode. Trunk
serial interfaces with different transmission rates can be generated in the two modes to meet
different bandwidth requirements of services.

The configuration of channelized mode is supported only on the Admin-VS.
Procedure
l Configure a CPOS-Trunk interface to work in channelized mode.
– Configure an E1 channel of a CPOS-Trunk interface to work in clear channel mode
so that a trunk serial interface is generated.
i. Run system-view
ii. Run interface cpos-trunk trunk-id
The CPOS-Trunk interface view is displayed.
iii. Run e1 e1-number unframed
An E1 channel of the CPOS-Trunk interface is configured to work in clear
channel mode, and a trunk serial interface is generated.
After the trunk serial interface in clear channel mode is generated, you can run
the interface trunk-serial cpos-trunk-id/e1-number:0 command to enter the
trunk serial interface view.
iv. Run commit
– Configure an E1 channel of a CPOS-Trunk interface to work in channelized mode
so that a trunk serial interface in channelized mode can be generated.
i. Run system-view
ii. Run interface cpos-trunk trunk-id
iii. Run e1 e1-number channel-set set-number timeslot-list { slot-list [ ts0 ] |
[ ts0 ] }
Timeslots of an E1 channel of the CPOS-Trunk interface are bundled, and a
trunk serial interface is generated.
After the trunk serial interface in channelized mode is generated, you can run
the interface trunk-serial cpos-trunk-id/e1-number:set-number command to
enter the trunk serial interface view.
iv. Run commit
l Configure a CPOS-Trunk interface to work in clear channel mode.
a. Run system-view
b. Run interface cpos-trunk trunk-id
c. Run using vc4
The CPOS-Trunk interface is configured to work in clear channel mode, and a trunk
serial interface is created on the CPOS-Trunk interface. The trunk serial interface
transmits data at a high rate, without timeslot division.

After the trunk serial interface is created, you can run the interface trunk-serial
cpos-trunk-id/0:0 command to enter the trunk serial interface view.
d. Run commit
5.3.3 Configuring a Working Mode for an E1 Channel of a CPOS-

Trunk Interface
An E1 channel of a CPOS-Trunk interface can be configured to work in clear channel or
channelized mode to form trunk serial interfaces with different bandwidths.
Procedure
l Configure an E1 channel of a CPOS-Trunk interface to work in clear channel mode so
that a trunk serial interface is generated.
a. Run system-view
c. Run e1 e1-number unframed
An E1 channel of the CPOS-Trunk interface is configured to work in clear channel
mode, and a trunk serial interface is generated.
After the trunk serial interface in clear channel mode is generated, you can run the
interface trunk-serial cpos-trunk-id/e1-number:0 command to enter the trunk
serial interface view.
d. Run commit
l Configure an E1 channel of a CPOS-Trunk interface to work in channelized mode so that
a trunk serial interface in channelized mode can be generated.
a. Run system-view
c. Run e1 e1-number channel-set set-number timeslot-list { slot-list [ ts0 ] | [ ts0 ] }
Timeslots of an E1 channel of the CPOS-Trunk interface are bundled, and a trunk
serial interface is generated.
After the trunk serial interface in channelized mode is generated, you can run the
interface trunk-serial cpos-trunk-id/e1-number:set-number command to enter the
trunk serial interface view.
d. Run commit
----End

5.3.4 Creating a Global MP-Group or IMA-Group Interface and

Adding a Trunk Serial Interface to It
To increase transmission bandwidth and improve network reliability, add trunk serial
interfaces to a global MP-group or IMA-group interface.
Context
To improve network reliability, a protection channel can be configured to take over traffic
from one or more working channels if the working channels fail.
Before deploying and protecting PPP or ATM services on CPOS interfaces, add two CPOS
interfaces to a CPOS-Trunk interface and channelize the CPOS-Trunk interface into trunk
serial interfaces. Then, add the trunk serial interfaces to a global MP-group or IMA-group
interface to carry the PPP or ATM services. If one CPOS link fails, the other CPOS link takes
over traffic.
Procedure
l Create a global MP-group interface and add a trunk serial interface to it.
a. Create a global MP-group interface.
i. Run system-view
ii. Run interface global-mp-group global-mp-group-number
A global MP-group interface is created.
iii. Run commit
b. Add a trunk serial interface to the global MP-group interface.
i. Run system-view
ii. Run interface trunk-serial trunk-serial-id
The trunk serial interface view is displayed.
iii. Run link-protocol ppp
The link layer protocol is configured as PPP for the trunk serial interface.
iv. Run ppp mp-global global-mp-group global-mp-group-number
The trunk serial interface is added to the global MP-group interface.
v. Run commit
l Create a global IMA-group interface and add a trunk serial interface to it.
a. Create a global IMA-group interface.
i. Run system-view
ii. Run interface global-ima-group global-ima-group-number
A global IMA-group interface is created.

iii. Run commit

b. Add a trunk serial interface to the global IMA-group interface.
i. Run system-view
ii. Run interface trunk-serial trunk-serial-id
The trunk serial interface view is displayed.
iii. Run link-protocol atm
The link layer protocol is configured as ATM for the trunk serial interface.
iv. Run ima global-ima-group global-ima-group-number
The trunk serial interface is added to the global IMA-group interface.
v. Run commit
----End
5.3.5 Verifying the CPOS-Trunk Interface Configuration

After configuring a CPOS-Trunk interface, check the configurations and status of the CPOS-
Trunk interface.
Prerequisites
A CPOS-Trunk interface has been configured.
Procedure
l Run the display cpos-trunk trunk-id command to check the configurations of a CPOS-
Trunk interface.
l Run the display interface trunk-serial [ trunk-serial-id ] command to check the status
and packet statistics of a specified or all trunk serial interfaces.
l Run the display ppp mp-global [ interface global-mp-group interface-number ]
command to check the configurations of a global MP-group interface.
l Run the display interface global-ima-group [ global-ima-group-number ] command to
check configurations and status of a global IMA-group interface.
----End
5.4 Maintaining a CPOS Interface

You can test the bit error rate of a CPOS E1 link to maintain the CPOS interface.
5.4.1 Testing the Bit Error Rate of a CPOS E1 Link

The testing results can be used to locate link faults.

Context
In VS mode, this configuration process is supported only by the admin VS.
When faults occur on a CPOS E1 link, you can run the test connectivity controller cpos e1
command for fault locating.
Procedure
Step 2 Run test connectivity controller cpos e1 controller-number { unframed | channelized
timeslot-list slot-list } duration time
The bit error rate is tested on a specified CPOS E1 link.
----End
5.4.2 Clearing Error Statistics and Alarm Status Information on an

E1 Interface or on a CPOS Interface's E1 Channels
Context
In VS mode, this configuration process is supported only by the admin VS.
This section describes how to clear error statistics and alarm status information on an E1
interface or on a CPOS interface's E1 channels.
Procedure
Step 1 Run the system-view command to enter the system view.
Step 2 Run the reset e1 counters controller cpos controller-number e1 e1-number command to
clear error statistics and alarm status information on a CPOS interface's E1 channels or run
the reset e1 counters controller e1 controller-number command to clear error statistics and
alarm status information on an E1 interface.
----End
5.4.3 Monitoring the Physical Status of E1 Links

To ensure correct link connections, you must monitor the physical status of E1 links.
Context
Monitoring the physical status of E1 links can help you locate E1 link faults, ensuring correct
link connections. You can configure the system to monitor the physical status of multiple E1
links simultaneously while not affecting existing services.
Perform the following steps on a device to be checked:

Procedure
Step 1 Run monitor e1 { interface-type interface-number | interface-name } &<1-16> [ interval
interval [ times times ] | times times [ interval interval ] ]
The physical status of E1 links is monitored.
----End
5.5 Configuration Examples for CPOS Interfaces

This section provides CPOS configuration examples.
5.5.1 Example for Configuring CPOS Interfaces

This example shows how to interconnect devices through CPOS interfaces over an FR
network.
Networking Requirements
CPOS interfaces are used to improve the convergence capability of low-speed access for
routers. STM-1 CPOS interfaces are often used to converge multiple E1/T1 interfaces.
At present, some governmental agencies and enterprises use low-end and mid-range devices
to access the transmission network through E1/T1 leased lines. Users requiring bandwidth
between E1/T1 and T3 (44M), such as the date center, lease several E1/T1 interfaces
simultaneously. Bandwidth of these users converges on one or multiple CPOS interfaces
through the transmission network. CPOS interfaces are then connected to DeviceA that
identifies each low-end device through timeslots.
In application, there may be more than one level of transmission networks between CPOS
interfaces and low-end devices. Other transmission devices are needed to relay
communication between low-end devices and transmission networks.

Figure 5-5 Networking diagram of using STM-1 CPOS interface
Configuration Roadmap
The configuration roadmap is as follows:
1. Create the channel.

2. Create the channel-set.
3. Bundle the channel into the channel-set.
Data Preparation
To complete the configuration, you need the following data:
l Channel number and timeslot number of each E1 channel

l Number of the channel-set of each interface

Procedure
Step 1 Configure DeviceA.
# Create a channel on the CPOS interface.
<HUAWEI> system-view
[~HUAWEI] sysname DeviceA
[*DeviceA] controller cpos 3/0/0
[*DeviceA-Cpos3/0/0] e1 1 channel-set 1 timeslot-list 1-10
[*DeviceA-Cpos3/0/0] undo shutdown
[*DeviceA-Cpos3/0/0] quit
[*DeviceA] commit
# Create a channel-set and configure the endpoint authenticator.

[~DeviceA] interface mp-group 3/0/1
[*DeviceA-Mpgroup3/0/1] discriminator
[*DeviceA-Mpgroup3/0/1] undo shutdown
[*DeviceA-Mpgroup3/0/1] quit
[*DeviceA] commit
# Bundle the channel into the channel-set.

[~DeviceA] interface Serial 3/0/0/1:1
[~DeviceA-Serial3/0/0/1:1] link-protocol ppp
[*DeviceA-Serial3/0/0/1:1] ppp mp mp-group 3/0/1
[*DeviceA-Serial3/0/0/1:1] quit
[*DeviceA] interface Serial 3/0/0/2:2
[*DeviceA-Serial3/0/0/2:2] link-protocol ppp
[*DeviceA] commit
Step 2 Configure DeviceB.

# Create the channel on the E1 interface.
[~HUAWEI] sysname DeviceB
[*DeviceB] controller E1 5/0/0
[*DeviceB-E15/0/0] channel-set 0 timeslot-list 1-31
[*DeviceB-E15/0/0] undo shutdown
[*DeviceB-E15/0/0] quit
[*DeviceB] commit
# Create a channel-set.
[~DeviceB] interface mp-group 5/0/1
[*DeviceB-Mp-group5/0/1] discriminator
[*DeviceB-Mp-group5/0/1] undo shutdown
[*DeviceB-Mp-group5/0/1] quit
[*DeviceB] commit
# Bundle the channel into the channel-set.

[~DeviceB] interface Serial5/0/0:0
[~DeviceB-Serial5/0/0:0] link-protocol ppp

[*DeviceB-Serial5/0/0:0] ppp mp mp-group 5/0/1

[*DeviceB] commit
----End
Configuration Files
l Configuration file of DeviceA
#
sysname DeviceA
#
controller Cpos3/0/0
e1 1 channel-set 1 timeslot-list 1-10
undo shutdown
#
interface Serial3/0/0/1:1
link-protocol ppp
ppp mp Mp-group 3/0/1
#
link-protocol ppp
#
link-protocol ppp
#
link-protocol ppp
#
interface Mp-group3/0/1
#
return
l Configuration file of DeviceB

#
sysname DeviceB
#
controller E1 5/0/0
channel-set 0 timeslot-list 1-31
undo shutdown
#
interface Mp-group 5/0/1
#
interface Serial5/0/0:0
link-protocol ppp
#
return
5.5.2 Example for Configuring CPOS Interface Interconnection

This section provides an example on how to interconnect devices through CPOS interfaces
and how to configure MP-group interfaces for link bundling.
On the network shown in Figure 5-6, Device A and Device B need to communicate with each
other through CPOS interfaces, and MP-group interfaces need to be configured for link
bundling.

Figure 5-6 Configuring CPOS interface interconnection
In this example, interface1 and interface2 represent CPOS 3/0/0 and CPOS 5/0/0, respectively.
1. Configure a working mode for CPOS interfaces and channelize them into synchronous
serial interfaces.
2. Configure MP-group interfaces and add the synchronous serial interfaces to the MP-
group interfaces.
Data Preparation
l Channel number and timeslot number of each E1 channel
l IP addresses of MP-group interfaces
The interface to be added to an MP-group interface must have the same slot number and card number as
the MP-group interface.
The timeslot channels of the serial interfaces on Device A must be the same as those on Device B.
Procedure
Step 1 Configure a working mode for CPOS interfaces and channelize them into synchronous serial
interfaces.
# Create synchronous serial interfaces on the CPOS interface of Device A.
[*DeviceA-Cpos3/0/0] commit
[~DeviceA-Cpos3/0/0] quit
# Create synchronous serial interfaces on the CPOS interface of Device B.

[*DeviceB] controller cpos 5/0/0
[*DeviceB-Cpos5/0/0] e1 1 channel-set 1 timeslot-list 1-15
[*DeviceB-Cpos5/0/0] e1 2 channel-set 1 timeslot-list 16-31
[*DeviceB-Cpos5/0/0] undo shutdown
[*DeviceB-Cpos5/0/0] commit
[~DeviceB-Cpos5/0/0] quit

Step 2 Configure MP-group interfaces and add the synchronous serial interfaces to the MP-group
interfaces.
# Create an MP-group interface on Device A.

[*DeviceA-Mp-group3/0/1] ip address 10.1.1.1 255.255.255.0
[*DeviceA-Mp-group3/0/1] undo shutdown
[*DeviceA-Mp-group3/0/1] commit
[~DeviceA-Mp-group3/0/1] quit
# Add the synchronous serial interfaces to the MP-group interface on Device A.

[~DeviceA] interface serial 3/0/0/1:1
[*DeviceA-Serial3/0/0/1:1] commit
[~DeviceA-Serial3/0/0/1:1] quit
# Create an MP-group interface on Device B.

[*DeviceB-Mp-group5/0/1] ip address 10.1.1.2 255.255.255.0
[*DeviceB-Mp-group5/0/1] commit
[~DeviceB-Mp-group5/0/1] quit
# Add the synchronous serial interfaces to the MP-group interface on Device B.

[~DeviceB] interface serial 5/0/0/1:1
[~DeviceB-Serial5/0/0/1:1] link-protocol ppp
[*DeviceB-Serial5/0/0/1:1] ppp mp mp-group 5/0/1
[*DeviceB-Serial5/0/0/1:1] commit
[~DeviceB-Serial5/0/0/1:1] quit
[~DeviceB] interface serial 5/0/0/2:1
[~DeviceB-Serial5/0/0/2:1] link-protocol ppp
[*DeviceB-Serial5/0/0/2:1] ppp mp mp-group 5/0/1
[*DeviceB-Serial5/0/0/2:1] commit
[~DeviceB-Serial5/0/0/2:1] quit
Step 3 Verify the configuration.
# On Device A, ping the IP address of the MP-group interface on Device B. The command
output shows that the ping is successful.
[~DeviceA] ping 10.1.1.2
PING 10.1.1.2: 56 data bytes, press CTRL_C to break
Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=29 ms
--- 10.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 29/29/31 ms
----End

Configuration Files
l Device A configuration file
#
sysname DeviceA
#
undo shutdown
#
#
link-protocol ppp
ppp mp Mp-group3/0/1
#
link-protocol ppp
#
return
l Device B configuration file

#
sysname DeviceB
#
undo shutdown
#
#
link-protocol ppp
#
link-protocol ppp
#
return
5.5.3 Example for Configuring CPOS Interface and E1 Interface

Interconnection
This section provides an example on how to interconnect devices through CPOS interface and
E1 interface, and how to configure MP-group interfaces for link bundling.
On the network shown in Figure 5-7, Device A and Device B need to communicate with each
other through CPOS interface and E1 interfaces, and MP-group interfaces need to be
configured for link bundling.
Figure 5-7 Configuring CPOS interface and E1 Interface interconnection
In this example, interface1, interface2, and interface3 represent CPOS 3/0/0, E1 2/0/0, and E1 2/0/1,
respectively.

1. Configure a working mode for CPOS interfaces.
2. Configure MP-group interfaces and add the synchronous serial interfaces to the MP-
group interfaces.
Data Preparation
l IP addresses of MP-group interfaces
The interface to be added to an MP-group interface must have the same slot number and card number as
the MP-group interface.
Procedure
Step 1 Configure a working mode for CPOS interfaces and create synchronous serial interfaces.
# Create synchronous serial interfaces on the CPOS interface of Device A.
[*DeviceA-Cpos3/0/0] e1 1 unframed
[*DeviceA-Cpos3/0/0] e1 2 unframed
[*DeviceA-Cpos3/0/0] commit
[~DeviceA-Cpos3/0/0] quit
# # Create synchronous serial interfaces on the E1 interface of Device B.

[*DeviceB] controller e1 2/0/0
[*DeviceB-E12/0/0] using e1
[*DeviceB-E12/0/0] commit
[~DeviceB-E12/0/0] quit
[*DeviceB] controller e1 2/0/1
[*DeviceB-E12/0/1] using e1
[*DeviceB-E12/0/1] commit
[~DeviceB-E12/0/1] quit
Step 2 Configure MP-group interfaces and add the synchronous serial interfaces to the MP-group
interfaces.
# Create an MP-group interface on Device A.
[*DeviceA-Mp-group3/0/1] ip address 10.1.1.1 255.255.255.0

[*DeviceA-Mp-group3/0/1] undo shutdown

[*DeviceA-Mp-group3/0/1] commit
[~DeviceA-Mp-group3/0/1] quit
# Add the synchronous serial interfaces to the MP-group interface on Device A.

# Create an MP-group interface on Device B.

[*DeviceB-Mp-group2/0/1] ip address 10.1.1.2 255.255.255.0
[*DeviceB-Mp-group2/0/1] commit
[~DeviceB-Mp-group2/0/1] quit
# Add the synchronous serial interfaces to the MP-group interface on Device B.

[~DeviceB] interface serial 2/0/0:0
[*DeviceB-Serial2/0/0:0] commit
[~DeviceB-Serial2/0/0:0] quit
[~DeviceB] interface serial 2/0/1:0
[*DeviceB-Serial2/0/1:0] commit
[~DeviceB-Serial2/0/1:0] quit
Step 3 Verify the configuration.

# On Device A, ping the IP address of the MP-group interface on Device B. The command
output shows that the ping is successful.
[~DeviceA] ping 10.1.1.2
PING 10.1.1.2: 56 data bytes, press CTRL_C to break
--- 10.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 29/29/31 ms
----End
Configuration Files
l Device A configuration file
#
sysname DeviceA
#
e1 1 unframed
e1 2 unframed
undo shutdown

#
#
link-protocol ppp
#
link-protocol ppp
#
return
l Device B configuration file

#
sysname DeviceB
#
controller E1 2/0/0
using e1
undo shutdown
#
controller E1 2/0/1
using e1
undo shutdown
#
#
link-protocol ppp
#
link-protocol ppp
#
return

01-05 CPOS Interface Configuration

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

01-05 CPOS Interface Configuration

Загружено:

Авторское право:

Доступные форматы

HUAWEI NetEngine40E Universal Service Router

Configuration Guide - WAN Access 5 CPOS Interface Configuration

5 CPOS Interface Configuration

About This Chapter

5.1 Overview of CPOS Interfaces

5.1 Overview of CPOS Interfaces

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 42

Introduction to SONET and SDH

SONET, which uses synchronous signals, can easily multiplex signals.

SONET-based SDH is an international standard defined by the International

Table 5-1 Common SONET and SDH transmission rates

STS-1 OC-1 - 51.840

STS-3 OC-3 STM-1 155.520 (155)

STS-9 OC-9 STM-3 466.560

STS-12 OC-12 STM-4 622.080 (622)

STS-18 OC-18 STM-6 933.120

STS-24 OC-24 STM-8 1244.160

STS-36 OC-36 STM-12 1866.240

STS-48 OC-48 STM-16 2488.320 (2.5 Gbit/s)

STS-96 OC-96 STM-32 4876.640

STS-192 OC-192 STM-64 9953.280 (10 Gbit/s)

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 43

Channelization and Unchannelization

Channelization can utilize bandwidth more efficiently by transmitting multiple channels of

Introduction to Channelized Serial Interfaces

The NE40E supports only STM-1 Channelized POS.

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 44

SDH Frame Structure

Figure 5-1 STM-N frame structure

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 45

l VC: It is an information terminal of SDH channels and is used to support connections

Figure 5-2 E1 to STM-1 multiplexing process

Calculation of E1 Path Sequence Numbers

VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 46

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 47

CPOS Interface Types

Figure 5-4 Networking diagram of typical CPOS implementation

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 48

5.2 Configuring a CPOS Interface

5.2.1 Configuring the Working Mode of a CPOS Interface

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 49

ii. Run controller cpos cpos-number

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 50

5.2.2 Configuring the Clock Mode for a CPOS Interface

l Master clock mode: uses internal clock signals.

The system view is displayed.

Step 2 Run controller cpos cpos-number

The CPOS interface view is displayed.

Step 3 Run clock { master | slave }

A clock mode is configured for the CPOS interface.

Step 4 Run commit

The configuration is committed.

5.2.3 Configuring the Working Modes for the E1 Channels of a

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 51

5.2.4 Configuring Overhead Bytes for a CPOS Interface

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 52

l To configure the path trace byte J1, run:

l To configure path signal label byte C2, run:

l To configure the lower-order path signal label byte V5, run:

l To configure the lower-order path trace byte J2, run:

5.2.5 Configuring the Mapping Mode for the E1 Channels of a

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 53

Step 3 Run mapping-mode { a-mode | h-mode | l-mode }