99-Book 761843 1285 0

H3C SR8800 10G Core Routers
Interface Configuration Guide
Hangzhou H3C Technologies Co., Ltd.

http://www.h3c.com
Software version: SR8800-CMW520-R3347

Document version: 6W103-20120224
Copyright © 2011-2012, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,

SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,
XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co.,
Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Preface
The H3C SR8800 documentation set includes 13 configuration guides, which describe the software
features for the H3C SR8800 10G Core Routers and guide you through the software configuration
procedures. These configuration guides also provide configuration examples to help you apply software
features to different network scenarios.
The Interface Configuration Guide describes the fundamentals and configuration of Ethernet, WAN, POS,
CPOS, E-CPOS, loopback, and null interfaces.
This preface includes:
• Audience
• Conventions
• About the H3C SR8800 documentation set
• Obtaining documentation
• Technical support
• Documentation feedback
Audience
This documentation is intended for:
• Network planners
• Field technical support and servicing engineers
• Network administrators working with the SR8800
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[] Square brackets enclose syntax choices (keywords or arguments) that are optional.
Braces enclose a set of required syntax choices separated by vertical bars, from which
{ x | y | ... }
you select one.
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
[ x | y | ... ]
which you select one or none.
Asterisk marked braces enclose a set of required syntax choices separated by vertical
{ x | y | ... } *
bars, from which you select at least one.
Asterisk marked square brackets enclose optional syntax choices separated by vertical
[ x | y | ... ] *
bars, from which you select one choice, multiple choices, or none.
The argument or keyword and argument combination before the ampersand (&) sign can
&<1-n>
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Window names, button names, field names, and menu items are in Boldface. For
Boldface
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
An alert that calls attention to important information that if not understood or followed can
WARNING result in personal injury.
An alert that calls attention to important information that if not understood or followed can
CAUTION result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Port numbering in examples

The port numbers in this document are for illustration only and might be unavailable on your router.
About the H3C SR8800 documentation set

The H3C SR8800 documentation set includes:
Category Documents Purposes
Marketing brochures Describe product specifications and benefits.
Product description and Provide an in-depth description of software features

Technology white papers
specifications and technologies.
Card datasheets Describe card specifications, features, and standards.

Category Documents Purposes
Compliance and safety Provides regulatory information and the safety
manual instructions that must be followed during installation.
Provides a complete guide to hardware installation

Installation guide
and hardware specifications.
H3C N68 Cabinet

Guides you through installing and remodeling H3C
Installation and Remodel
N68 cabinets.
Hardware specifications Introduction
and installation
H3C Pluggable SFP
[SFP+][XFP] Transceiver Guides you through installing SFP/SFP+/XFP
Modules Installation transceiver modules.
Guide
H3C High-End Network Describes the hot-swappable modules available for

Products Hot-Swappable the H3C high-end network products, their external
Module Manual views, and specifications.
Describe software features and configuration

Configuration guides
Software configuration procedures.
Command references Provide a quick reference to all available commands.
Provide information about the product release,

including the version history, hardware and software
Operations and
Release notes compatibility matrix, version upgrade information,
maintenance
technical support information, and software
upgrading.
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
service@h3c.com
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to info@h3c.com.
We appreciate your comments.
Contents
Configuring Ethernet interfaces ··································································································································· 1

Ethernet interface overview ·············································································································································· 1
Performing general configurations ·································································································································· 1
Configuring a combo interface ·······························································································································1
Configuring the operating mode for a 10-GE interface······················································································· 2
Configuring basic settings of an Ethernet interface or subinterface ··································································· 3
Shutting down an Ethernet interface or subinterface ···························································································· 5
Configuring flow control on an Ethernet interface ································································································ 5
Configuring physical state change suppression on an Ethernet interface·························································· 6
Configuring loopback testing on an Ethernet interface ························································································ 6
Setting the interval for collecting Ethernet interface statistics ··············································································· 7
Configuring the link mode of an Ethernet interface ······························································································ 7
Configuring a Layer 2 Ethernet interface ······················································································································· 8
Layer 2 Ethernet interface configuration task list ·································································································· 8
Configuring a port group ········································································································································ 8
Setting speed options for auto negotiation on an Ethernet interface ·································································· 9
Configuring storm suppression for an Ethernet interface ·················································································· 10
Enabling forwarding of jumbo frames ················································································································ 10
Configuring the MDI mode for an Ethernet interface ························································································ 11
Configuring a Layer 3 Ethernet interface or subinterface ·························································································· 12
Layer 3 Ethernet interface or subinterface configuration task list ····································································· 12
Setting the MTU for an Ethernet interface or subinterface ················································································ 12
Enabling traffic statistics collection on an Ethernet subinterface ······································································ 12
Configuring a VE interface ··········································································································································· 13
Introduction ···························································································································································· 13
Configuration procedure ······································································································································ 13
Displaying and maintaining an Ethernet interface or subinterface··········································································· 14
Configuring WAN interfaces ···································································································································· 16

CE1 interface ·································································································································································· 16
Overview ································································································································································ 16
Configuring a CE1 interface (in E1 mode) ········································································································· 16
Configuring a CE1 interface (in CE1 mode) ······································································································ 17
Configuring other CE1 interface parameters ····································································································· 17
Displaying and maintaining CE1 interfaces ······································································································· 18
CT1 interface ·································································································································································· 19
Overview ································································································································································ 19
Configuring a CT1 interface ································································································································ 19
Configuring other CT1 interface parameters ····································································································· 19
Displaying and maintaining CT1 interfaces ······································································································· 21
Configuring POS interfaces ······································································································································· 22

Overview········································································································································································· 22
SONET···································································································································································· 22
SDH ········································································································································································· 22
POS ········································································································································································· 22
Configuring a POS interface ········································································································································ 22
Configuring a POS interface ································································································································ 22
Switching interface type between POS and Layer 3 GE ·················································································· 24
Displaying and maintaining POS interfaces ··············································································································· 24
i
POS interface configuration example ·························································································································· 25
Directly connecting routers through POS interfaces ·························································································· 25
Connecting routers through POS interfaces across frame relay ······································································· 25
Troubleshooting POS interfaces···································································································································· 27
Configuring CPOS interfaces ···································································································································· 28

Overview········································································································································································· 28
SONET···································································································································································· 28
SDH ········································································································································································· 28
CPOS ······································································································································································ 28
SDH frame structure ·············································································································································· 28
Terms······································································································································································· 29
Multiplexing E1/T1/E3/T3 channels to form STM-1 ························································································ 29
Calculating E1/T1/E3/T3 channel sequence numbers ···················································································· 31
Overhead bytes ····················································································································································· 32
CPOS interface application scenario ·················································································································· 33
Configuring a CPOS interface ······································································································································ 34
Configuring an E1 channel ··········································································································································· 35
Configuring a T1 channel ············································································································································· 36
Configuring an E3 channel ··········································································································································· 37
Configuring a T3 channel ············································································································································· 38
Displaying and maintaining CPOS interfaces ············································································································ 39
CPOS interface configuration example ······················································································································· 39
Troubleshooting CPOS interfaces ································································································································· 41
Interface physical status is up, link protocol status is down, and loopback is detected ································ 41
Configuring E-CPOS interfaces ································································································································· 42

Overview········································································································································································· 42
SONET···································································································································································· 42
SDH ········································································································································································· 42
E-CPOS ··································································································································································· 46
Configuring an E-CPOS interface································································································································· 47
Configuring an E-CPOS interface ························································································································ 47
Configuring the operating mode of an E-CPOS interface/channel ································································· 48
Displaying and maintaining E-CPOS interfaces ········································································································· 52
E-CPOS interface configuration example ···················································································································· 52
Troubleshooting E-CPOS interfaces ······························································································································ 55
Symptom ································································································································································· 55
Solution ··································································································································································· 55
Configuring Loopback and null interfaces ··············································································································· 56

Loopback interface ························································································································································· 56
Introduction ···························································································································································· 56
Configuring a loopback interface ······················································································································· 56
Null interface ·································································································································································· 57
Introduction ···························································································································································· 57
Configuring interface Null 0 ································································································································ 57
Displaying and maintaining loopback and null interfaces ························································································ 58
Index ··········································································································································································· 59
ii
Configuring Ethernet interfaces
NOTE:
In this documentation, SPE cards refer to the cards prefixed with SPE, for example, SPE-1020-E-II.
Ethernet interface overview

Ethernet is the most widespread wired LAN technology due to its flexibility, simplicity, and easy
implementation. Your router supports the following types of Ethernet interfaces:
• Layer 2 Ethernet interfaces—They are physical interfaces operating on the data link layer for Layer
2 packet forwarding. They can only forward packets carrying source and destination IP addresses
that belong to the same network segment.
• Layer 3 Ethernet interfaces—They are physical interfaces operating on the network layer for Layer
3 packet forwarding, and forward packets carrying source and destination IP addresses that
belong to different network segments. You can assign an IP address to a Layer 3 Ethernet interface.
• Layer 2-Layer 3 Ethernet interfaces—They are physical interfaces that can operate on both the data
link layer and the network layer. When operating on the data link layer, a Layer 2-Layer 3 Ethernet
interface acts as a Layer 2 Ethernet interface. When operating on the network layer, a Layer 2-Layer
3 Ethernet interface acts as a Layer 3 Ethernet interface.
• Layer 3 Ethernet subinterfaces—They are logical interfaces operating on the network layer. You
can assign an IP address to a Layer 3 Ethernet subinterface. By creating subinterfaces on a Layer 3
Ethernet interface, you can enable the interface to carry packets for multiple VLANs, which provides
great networking flexibility.
• Virtual Ethernet interfaces—Including Layer 3 Virtual-Ethernet (VE) interfaces and Layer 2 VE
(VE-bridge) interfaces. They are used on interface modules for carrying data link layer protocols
over Ethernet.
Performing general configurations

This section describes the attributes and configurations common to Layer 2 and Layer 3 Ethernet
interfaces/subinterfaces. For more information about the attributes and configuration, see “Configuring
a Layer 2 Ethernet interface” and “Configuring a Layer 3 Ethernet interface or subinterface.”
Configuring a combo interface

Introduction to combo interfaces
A combo interface is a logical interface that comprises one optical (fiber) port and one electrical (copper)
port. The two ports cannot work simultaneously. When you enable one port, the other is automatically
disabled.
The fiber combo port and copper combo port share the same interface view, in which you can activate
the fiber or copper combo port, and configure other port attributes such as the interface rate and duplex
mode.
1
Configuration prerequisites
Before configuring a combo interface, identify which port of the interface is active with the display
interface command:
• If the output includes “Media type is twisted pair, Port hardware type is 1000_BASE_T”, the copper
combo port is active.
• If the output includes “Media type is not sure, Port hardware type is No connector”, the fiber combo
port is active.
Changing the active port of a combo interface

To change the active port of a combo interface:
Step Command Remarks

1. Enter system view. system-view N/A
interface interface-type
2. Enter Ethernet interface view. N/A
interface-number
Optional.
3. Activate the fiber or copper
combo enable { copper | fiber } By default, the copper combo port
combo port.
is active.
CAUTION:
After you activate the fiber combo port, the speed, duplex, and MDI settings will be automatically removed
if the port does not support them.
Configuring the operating mode for a 10-GE interface

Introduction to the operating modes
A ten-GigabitEthernet (10-GE) interface can operate in LAN or WAN mode.
• In LAN mode, the 10-GE interface transmits Ethernet packets, providing access to an Ethernet
network.
• In WAN mode, the 10-GE interface transmits synchronous digital hierarchy (SDH) packets,
providing access to an SDH network. In this mode, the interface supports only point-to-point
connections.
CAUTION:
A 10-GE interface in WAN mode encapsulates Ethernet packets as SDH frames, and a 10G packet over
SDH (POS) interface encapsulates PPP packets as SDH frames. However, the two types of interfaces
cannot communicate with each other, because the framing formats used by them are different.
Introduction to J0 and J1 overhead bytes

SDH frames have diversified overhead bytes, which accomplish the operation and maintenance
functions such as hierarchical management of the transport network. J0 and J1 are used to provide
internetworking support between different countries, regions, or vendors.
The regenerator section trace byte J0 is usually set to a section access point identifier. The sending end
keeps connected with the receiving end by sending this byte repeatedly.
2
The path trace byte J1, usually set to a high-order path access point identifier, functions in a similar way
to keep connected with the receiving end of the path.
To ensure smooth communication, the J0 and J1 bytes should be matched respectively at the sending and
receiving ends.
Configuration procedure
To configure a 10-GE interface to operate in LAN or WAN mode:

2. Enter ten-GigabitEthernet interface ten-gigabitethernet

N/A
interface view. interface-number
3. Configure a 10-GE interface Optional.

to operate in LAN or WAN port-mode { lan | wan } By default, a 10-GE interface
mode. operates in LAN mode.
4. Configure a value for J0 or J1 Optional.
bytes when the 10-GE
flag { j0 | j1 } sdh value By default, the value of the J0 and
interface operates in WAN
mode. J1 bytes is 0.
NOTE:
The flag command can only take effect on 10-GE interfaces operating in WAN mode.
Configuring basic settings of an Ethernet interface or

subinterface
Configuring an Ethernet interface
You can set an Ethernet interface to operate in one of the following duplex modes:
• Full-duplex mode (full)—Interfaces operating in this mode can send and receive packets
simultaneously.
• Half-duplex mode (half)—Interfaces operating in this mode can either send or receive packets at a
given time.
• Auto-negotiation mode (auto)—Interfaces operating in this mode determine their duplex mode
through auto-negotiation.
Similarly, you can set the speed of an Ethernet interface or enable it to automatically negotiate a speed
with its peer. For a 100-Mbps or 1000-Mbps Layer 2 Ethernet interface, you can also set speed options
for auto negotiation. The two ends can pick a speed only from the available options. For more
information, see “Setting speed options for auto negotiation on an Ethernet interface.”
To configure an Ethernet interface:

interface-number
3
Optional.
By default, the description of an
3. Set the description. description text interface is in the format of
interface-name Interface. For
example, M-Ethernet0/0/0
Interface.
Optional.
By default, the duplex mode is auto
for Ethernet interfaces.
4. Set the duplex mode. duplex { auto | full | half } Optical interfaces do not support the
half keyword.
10-GE interfaces do not support this
command.
Optional.
5. Set the transmission rate. speed { 10 | 100 | 1000 | auto }
The default setting is auto.
6. Restore the default settings. default Optional.
NOTE:
After you modify the rate or duplex mode of an interface, you must use the shutdown command to disable
the interface and then use the undo shutdown command to enable it again, so as to start a new
auto-negotiation process to make the new configuration take effect.
Configuring an Ethernet subinterface

Layer 3 Ethernet subinterface enables Layer 3 Ethernet interfaces to identify packets by VLANs. By
configuring multiple subinterfaces on an Ethernet interface, you can have packets of different VLANs
forwarded through their corresponding subinterfaces, thus achieving flexibility.
To configure an Ethernet subinterface:

2. Create an Ethernet interface interface-type This command also leads you to

subinterface. interface-number.subnumber Ethernet subinterface view.
Optional.
3. Set the interface description. description text interface is in the format of
interface-name Interface. For
example, GigabitEthernet2/1/7.20
Interface.
4
NOTE:
• You can configure IP addresses for Ethernet subinterfaces. For more information about IP addressing,
see Layer 3—IP Services Configuration Guide.
• For the local and remote Ethernet subinterfaces to transmit traffic correctly, configure them with the same
subinterface number and VLAN ID.
Shutting down an Ethernet interface or subinterface

You may need to shut down and then bring up an Ethernet interface or subinterface to activate some
configuration changes, for example, the speed or duplex mode changes.
To shut down an Ethernet interface or subinterface:

• Enter Ethernet interface view:

Use any command.
interface-number
• Enter port group view: To shut down an Ethernet interface
2. Enter Ethernet interface or or subinterface, enter Ethernet
port-group manual
subinterface view, or port interface or subinterface view. To
port-group-name
group view. shut down all Ethernet interfaces in
• Enter Ethernet subinterface a port group, enter port group
view:
view.
interface-number.subnumber
3. Shut down the Ethernet By default, Ethernet interfaces and

shutdown
interface or subinterface. subinterfaces are up.
Configuring flow control on an Ethernet interface

You can avoid packet drops on a link by enabling flow control at both ends of the link. When traffic
congestion occurs at the receiving end, the receiving end sends a flow control (Pause) frame to ask the
sending end to suspend sending packets. In this way, flow control helps avoid packet drops.
To enable flow control on an Ethernet interface:

2. Enter Ethernet interface
interface interface-type interface-number N/A
view.
By default, flow control is
3. Enable flow control. flow-control
disabled.
5
Configuring physical state change suppression on an Ethernet
interface
The physical link state of an Ethernet interface is either up or down. Each time the physical link of a port
goes up or comes down, the physical layer reports the change to the upper layers, and the upper layers
handle the change, resulting in increased overhead.
To prevent physical link flapping from affecting system performance, configure physical state change
suppression to delay the reporting of physical link state changes. The physical layer reports the changes
only when the delay expires.
To configure physical state change suppression on an Ethernet interface:

interface-number
3. Set the physical state change
link-delay delay-time The default setting is one second.
suppression interval.
Configuring loopback testing on an Ethernet interface

If an Ethernet interface does not work normally, you can enable loopback testing on it to identify the
problem. Loopback testing has the following types:
• Internal loopback testing—Packets sent from the interface are internally looped back to the
interface without being sent onto the line. If the internal operation of the interface is normal, the
interface should be able to receive the self-sent packets.
• External loopback testing—To perform external loopback testing on an Ethernet interface, connect
a loopback plug to the Ethernet interface. The device sends test packets out the interface, which are
expected to loop over the plug and back to the interface. If the interface fails to receive any test
packet, the hardware of the interface is faulty.
An Ethernet interface in a loopback test does not forward data traffic.
To enable loopback testing on an Ethernet interface:

interface-number
Optional.
3. Enable loopback testing. loopback { external | internal } By default, loopback test is
disabled.
6
NOTE:
• The router does not support the loopback external command.
• As for internal loopback testing and external loopback testing, if an interface is down, only the former
is available on it; if the interface is shut down, both are unavailable.
• The speed, duplex, mdi, combo enable, and shutdown commands are not applicable during
loopback test.
• With loopback test enabled, the Ethernet interface operates in full duplex mode. With loopback test
disabled, the original configurations will be restored.
• After configuring the loopback internal command and then the undo loopback command on an
Ethernet interface, you should re-enable the interface with the shutdown command and then the undo
shutdown command to trigger an auto-negotiation on the interface.
Setting the interval for collecting Ethernet interface statistics

To configure the interval for collecting interface statistics:

2. Configure the interval for Optional

flow-interval interval
collecting interface statistics. The default setting is 300 seconds.
Configuring the link mode of an Ethernet interface

Depending on the layer (data link layer or network layer) at which the device processes the packets
received on an interface, an interface can be as a Layer 2 Ethernet interface (in bridge mode) or as a
Layer 3 Ethernet interface (in route mode). You can configure an Ethernet interface as a Layer 2 Ethernet
interface or Layer 3 Ethernet interface by setting the link mode to bridge or route.
To change the link mode of an Ethernet interface:

• (Approach I) In system view:
port link-mode { bridge |
route } interface-list
• (Approach II) In Ethernet Use either approach.
2. Change the link mode of
interface view: By default, Ethernet interfaces work
Ethernet interfaces.
a. interface interface-type in route mode.
interface-number
b. port link-mode { bridge |
route }
7
CAUTION:
• After you change the link mode of an Ethernet interface, all the settings of the Ethernet interface are
restored to their defaults under the new link mode.
• The link mode configuration for an Ethernet interface in system view and in interface view supersedes
each other.
Configuring a Layer 2 Ethernet interface

Layer 2 Ethernet interface configuration task list
Complete these tasks to configure an Ethernet interface operating in bridge mode:
Task Remarks
Configuring a port group Optional
Optional
Setting speed options for auto negotiation on an Ethernet
interface Applicable to 100-Mbps or 1000-Mbps Layer
2 Ethernet interfaces
Configuring storm suppression for an Ethernet interface Optional
Enabling forwarding of jumbo frames Optional
Configuring the MDI mode for an Ethernet interface Optional
Configuring a port group

The SR8800 routers allow you to configure some functions on multiple interfaces at a time. For example,
you can configure a traffic suppression threshold (see “Setting speed options for auto negotiation on an
Ethernet interface”) for multiple interfaces in bulk by assigning these interfaces to a port group.
A port group is created manually and the settings you made on it apply to all group member interfaces.
Note that even though the settings are made on the port group, they are saved on an interface basis
rather than on a port group basis. Thus, you can only view the settings in the view of each interface with
the display current-configuration command or the display this command.
To configure a manual port group:
Step Command
1. Enter system view. system-view
2. Create a manual port group and enter
port-group manual port-group-name
manual port group view.
3. Add Ethernet interfaces to the manual port
group-member interface-list
group.
8
Setting speed options for auto negotiation on an Ethernet
interface
Speed auto negotiation enables an Ethernet interface to negotiate with its peer for the highest speed
supported by both ends by default. You can narrow down the speed option list for negotiation.
Figure 1 Speed auto negotiation application scenario
IP network
GE3/1/4 Router A
G
1/
E3
/1
E3
/1
/
G
Server 1 Server 2 Server 3
As shown in Figure 1, all ports on Router A are operating in speed auto negotiation mode, with the
highest speed of 1000 Mbps. If the transmission rate of each server in the server cluster is 1000 Mbps,
their total transmission rate will exceed the capability of port GigabitEthernet 3/1/4, the port providing
access to the Internet for the servers.
To avoid congestion on GigabitEthernet 3/1/4, set 100 Mbps as the only option available for speed
negotiation on port GigabitEthernet 3/1/1, GigabitEthernet 3/1/2, and GigabitEthernet 3/1/3. As a
result, the transmission rate on each port connected to a server is limited to 100 Mbps.
To set speed options for auto negotiation on an Ethernet interface:

interface-number
Optional.
3. Set speed options for auto
speed auto [ 10 | 100 | 1000 ] * By default, the options for auto
negotiation.
negotiation are not restricted.
NOTE:
• Support for this feature varies with interface cards or subcards.
• The speed and speed auto commands supersede each other, and whichever is configured last takes
effect.
9
Configuring storm suppression for an Ethernet interface
You can use the storm suppression function to limit the size of a particular type of traffic (broadcast,
multicast, or unknown unicast traffic).
You can set the upper limit of broadcast, multicast, or unknown unicast traffic allowed to pass through the
system as a whole. When the sum of broadcast, multicast, or unknown unicast traffic arriving on all
interfaces of the system exceeds this threshold, the system discards packets until the traffic drops below
this threshold.
To set storm suppression thresholds on one or multiple Ethernet interfaces:

Use either command.

• Enter Ethernet interface view:
To configure storm suppression
on an Ethernet interface, enter
2. Enter Ethernet interface interface-number
Ethernet interface view.
view or port group view. • Enter port group view:
port-group manual To configure storm suppression
port-group-name on a group of Ethernet interfaces,
enter port group view.
Optional.
By default, broadcast traffic is
3. Configure broadcast storm broadcast-suppression { ratio | pps
not suppressed.
suppression. max-pps | kbps max-kbps }
SPE cards support only the ratio
argument.
Optional.
By default, multicast traffic is not
4. Set the multicast multicast-suppression { ratio | pps
suppressed.
suppression threshold ratio. max-pps | kbps max-kbps }
SPE cards do not support the
command.
Optional.
By default, unknown unicast
5. Set the unknown unicast unicast-suppression { ratio | pps
traffic is not suppressed.
suppression threshold ratio. max-pps | kbps max-kbps }
SPE cards do not support the
command.
NOTE:
If you set storm suppression ratios in Ethernet interface view or port group view repeatedly for an Ethernet
interface that belongs to a port group, only the latest settings take effect.
Enabling forwarding of jumbo frames

Due to tremendous amount of traffic occurring in Ethernet, it is likely that some frames might have a frame
size greater than the standard Ethernet frame size. If you have not configured the system to allow such
frames (called jumbo frames) to pass through Ethernet interfaces, the system will drop these frames. After
you enable this function in the system, the system processes jumbo frames that are within the length range
you specified.
10
To enable forwarding of jumbo frames:

By default, the router allows

2. Enable forwarding of jumbo jumboframe enable [ value ] slot
9216-byte jumbo frames to pass
frames. slot-num
through Ethernet interfaces.
Configuring the MDI mode for an Ethernet interface

NOTE:
Optical ports do not support this function.
Two types of Ethernet cables can be used to connect Ethernet devices: crossover cable and
straight-through cable. To accommodate these two types of cables, an Ethernet interface on the router
may operate in one of the following three Medium Dependent Interface (MDI) modes:
• Across mode
• Normal mode
• Auto mode
An Ethernet interface is composed of eight pins. By default, each pin has its particular role. For example,
pin 1 and pin 2 transmit signals; pin 3 and pin 6 receive signals. You can change the pin roles by setting
the MDI mode. For an Ethernet interface in normal mode, the pin roles are not changed. For an Ethernet
interface in across mode, pin 1 and pin 2 are used for receiving signals; pin 3 and pin 6 are used for
transmitting signals. To ensure normal communication, you must connect the local transmit pins to the
remote receive pins. Therefore, you should configure the MDI mode depending on cable type.
• Normally, the auto mode is used. The other two modes are useful only when the router cannot
determine the cable type.
• When straight-through cables are used, the local MDI mode must be different from the remote MDI
mode.
• When crossover cables are used, the local MDI mode must be the same as the remote MDI mode,
or the MDI mode of at least one end must be set to auto.
To configure the MDI mode for an Ethernet interface:

interface-number
Optional.
3. Configure the MDI mode for The default setting is auto. That is,
mdi { across | auto | normal } the Ethernet interface determines
the Ethernet interface.
the physical pin roles (transmit or
receive) through negotiation.
11
Configuring a Layer 3 Ethernet interface or
subinterface
Layer 3 Ethernet interface or subinterface configuration task list
Complete the following task to configure a Layer 3 Ethernet interface or subinterface:
Task Remarks
Setting the MTU for an Ethernet interface Optional
or subinterface Applicable to Layer 3 Ethernet interfaces and subinterfaces
Enabling traffic statistics collection on an Optional

Ethernet subinterface Applicable to Layer 3 Ethernet subinterfaces
Setting the MTU for an Ethernet interface or subinterface

The value of maximum transmission unit (MTU) affects the fragmentation and re-assembly of IP packets.
To set the MTU for an Ethernet interface or subinterface:

2. Enter Ethernet interface or
{ interface-number | N/A
subinterface view.
interface-number.subnumber }
3. Set the MTU. mtu size The default setting is 1500 bytes.
Enabling traffic statistics collection on an Ethernet subinterface

This feature enables you to monitor traffic by providing the statistics about the inbound and outbound
unicast packets, multicasts, and broadcasts of a subinterface.
To enable traffic statistics collection on an Ethernet subinterface:

2. Enter Ethernet subinterface interface interface-type

N/A
view. interface-number.subnumber
3. Enable traffic statistics By default, traffic statistics

collection on the Ethernet traffic-statistic enable collection is disabled on an
subinterface. Ethernet subinterface.
12
CAUTION:
• To view the traffic statistics on Ethernet subinterfaces, use the display interface command.
• Do not simultaneously enable traffic statistics collection and ACL functions (such as packet filtering and
Portal) that may conflict with the traffic statistics collection.
• This feature is available only on SPE cards.
Configuring a VE interface
Introduction
Virtual Ethernet (VE) interfaces are logical interfaces implemented on interface cards. They fall into Layer
3 VE interfaces and Layer 2 VE-bridge interfaces. The VE interfaces are mainly used for IPoEoA and EoA.
IPoEoA and EoA carry Ethernet packets over ATM by binding VE interfaces to permanent virtual channels
(PVCs). IPoEoA is for Layer 3 VE interface binding, and EoA is for Layer 2 VE interface binding. For more
information, see Layer 2—WAN Configuration Guide.
When implementing IPoEoA and EoA through a PVC, you must associate the PVC with a VE interface.
Otherwise, you cannot configure the PVC.
Configuring a Layer 3 VE interface

To configure a Layer 3 VE Interface:

If the specified Layer 3 VE interface

2. Create a Layer 3 VE interface already exists, you enter Layer 3
interface virtual-ethernet VE interface view directly.
and enter Layer 3 VE interface
interface-number
view. You can create up to 1024 Layer 3
VE interfaces.
Optional.
After configuring this command,
run the reset arp command to make
3. Change the MAC address of the new MAC address take effect.
mac-address mac-address
the Layer 3 VE interface. For more information about the
reset arp command, see Layer
3—IP Services Command
Reference.
Configuring a Layer 2 VE interface

To configure a Layer 2 VE Interface:

13
If the specified Layer 2 VE interface
2. Create a Layer 2 VE interface already exists, you enter Layer 2
interface ve-bridge VE interface view directly.
and enter Layer 2 VE interface
interface-number
view. You can create up to 1024 Layer 2
VE interfaces.
NOTE:
• Due to the restriction of hardware resources, each VLAN can contain a maximum number of 64 Layer
2 VE interfaces on each card.
• For more information about the IPoEoA and EoA configuration, see Layer 2—WAN Configuration
Guide.
Displaying and maintaining an Ethernet interface or

subinterface
Task Command Remarks
display interface [ interface-type ] brief [ down ] [ |
{ begin | exclude | include } regular-expression ]
Display Ethernet interface or
display interface interface-type { interface-number | Available in any view
subinterface information.
interface-number.subnumber } [ brief ] [ | { begin |
exclude | include } regular-expression ]
display counters { inbound | outbound } interface

Display traffic statistics for the
[ interface-type ] [ | { begin | exclude | include } Available in any view
specified interfaces.
regular-expression ]
Display traffic rate statistics display counters rate { inbound | outbound }

over the last sampling interface [ interface-type ] [ | { begin | exclude | Available in any view
interval. include } regular-expression ]
Display the information about display port-group manual [ all | name

a manual port group or all port-group-name ] [ | { begin | exclude | include } Available in any view
manual port groups. regular-expression ]
display interface [ ve-bridge ] [ brief [ down ] ] [ |

Display Layer 2 VE interface { begin | exclude | include } regular-expression ]
Available in any view
information. display interface ve-bridge interface-number [ brief ]
[ | { begin | exclude | include } regular-expression ]
display interface [ virtual-ethernet ] [ brief [ down ] ]

[ | { begin | exclude | include } regular-expression ]
Display Layer 3 VE interface
display interface virtual-ethernet { interface-number Available in any view
information.
| interface-number.subnumber } [ brief ] [ | { begin |
Clear the interface or reset counters interface [ interface-type

Available in user view
subinterface statistics. [ interface-number | interface-number.subnumber ] ]
Clear the Layer 2 VE interface reset counters interface [ ve-bridge

statistics. [ interface-number ] ]
14
Clear the Layer 3 VE interface reset counters interface [ virtual-ethernet
statistics. [ interface-number ] ]
15
Configuring WAN interfaces
In terms of line type, wide area networks (WANs) fall into these types: X.25, Frame Relay (FR), ATM, and
ISDN.
The router supports CE1 interfaces (see “CE1 interface”) and CT1 interfaces (see “CT1 interface”).
CE1 interface
Overview
In 1960s, the time division multiplexing (TDM) technology gained increasingly wide application in data
communications systems along with the introduction of pulse code modulation (PCM) technology.
So far, there are two TDM systems in the data communications system.
• E1 system—Recommended by ITU-T- and widely used in Europe and P.R. China.
• T1 system—Recommended by ANSI- and widely used in North American and Japan. (Japan
actually uses the J1 system. It is regarded as a T1 system due to the high level of similarity between
them.)
A CE1 interface can work in either E1 mode (also called non-channelized mode) and CE1 mode (also
called channelized mode).
• A CE1 interface in E1 mode equals an interface of 2.048 Mbps data bandwidth, on which, no
timeslots are divided. Its logical features are the same as those of a synchronous serial interface. It
supports the link layer protocols PPP and HDLC and the network protocol IP.
• A CE1 interface in CE1 mode is physically divided into 32 timeslots numbered 0 to 31. Among them,
timeslot 0 is used to transmit synchronizing information. All the timeslots except timeslot 0 can be
randomly divided into multiple channel sets and each set can be used as an interface upon timeslot
bundling. The logical features of the interface thus created are the same as those of a synchronous
serial interface. This interface supports link layer protocols PPP, HDLC, and FR, and network
protocol IP.
Configuring a CE1 interface (in E1 mode)

To configure a CE1 interface in E1 mode:

2. Enter CE1 interface view. controller e1 number N/A
3. Set the interface to operate in The default operating mode is CE1

using e1
E1 mode. mode.
4. Set other interface See “Configuring other CE1

Optional.
parameters. interface parameters.”
16
After you set the CE1 interface to operate in E1 mode, the system automatically creates a serial interface
numbered serial interface-number:0. This interface is logically equivalent to a synchronous serial
interface where you can configure other settings such as:
• Parameters of data link protocols such as PPP and HDLC
• IP address
Configuring a CE1 interface (in CE1 mode)

To configure a CE1 interface in CE1 mode:

Optional.
3. Set the interface to operate in
using ce1 The default operating mode is CE1
CE1 mode.
mode.
4. Bundle timeslots on the channel-set set-number timeslot-list

N/A
interface into a channel set. list
5. Set other interface See “Configuring other CE1

Optional.
A CE1 interface in CE1 mode can be used as a CE1 interface where a serial interface is created upon
creation of a channel set. You may bundle the timeslots on a CE1 interface into up to 31 channel sets.
For each channel set, the system automatically creates a serial interface numbered serial
interface-number:set-number. This interface is logically equivalent to a synchronous serial interface
where you can configure other settings such as:
• Parameters of data link protocol such as PPP and HDLC
• IP addressing
Configuring other CE1 interface parameters

To configure other CE1 interface parameters:

Optional.
3. Configure the interface
description text The default description is Interface
description.
name Interface.
Optional.
4. Set the line code format. code { ami | hdb3 } The default is high density bipolar
3 (HDB3).
Optional.
5. Set the cable type. cable { long | short }
The default cable type is long.
17
Optional.
6. Set the clock mode. clock { master | slave } The default is slave, that is, line
clock.
7. Enable automatic clock mode Optional.

clock-change auto
change. Disabled by default.
Optional.
8. Set the framing format. frame-format { crc4 | no-crc4 }
The default is no-CRC4.
9. Enable loopback and set the loopback { local | payload | Optional.

loopback mode. remote } Loopback is disabled by default.
Optional.
11. Disable the CE1 interface. shutdown A CE1 interface is enabled by
default.
12. Return to system view. quit N/A

• interface serial
13. Enter the view of the
interface-number:set-number
synchronous serial interface Use either command.
created on the CE1 interface. • interface serial
interface-number:0
Optional.
14. Set the CRC mode. crc { 16 | 32 | none }
By default, 16-bit CRC is adopted.
Optional.
15. Set the MTU. mtu mtu
1500 by default.
16. Set the keepalive transmission Optional.

timer hold seconds
interval. 10 seconds by default.
Optional.
PPP by default.
17. Specify the link layer protocol. link-protocol { fr | hdlc | ppp }
Support for Frame Relay depends
on the daughter cards.
NOTE:
Do not configure loopback on a CE1 interface configured with MP-group bundles. Otherwise, MP
interface out-of-sequence problems will occur.
Displaying and maintaining CE1 interfaces

display controller e1 [ interface-number ]
Display the operating state of a
[ | { begin | exclude | include } Available in any view
CE1 interface.
18
display interface serial
Display the operating state of a [ interface-number:set-number ] [ |
serial interface. { begin | exclude | include }
Clear the controller counter of a reset counters controller e1

CE1 interface. interface-number
CT1 interface
Overview
A CT1 interface can operate only in channelized mode. All the timeslots (numbered from 1 to 24) can be
randomly divided into groups. Each of these groups can form one channel set for which the system
automatically creates an interface logically equivalent to a synchronous serial interface. This interface
supports link layer protocols PPP, HDLC, and FR, and network protocol IP.
Configuring a CT1 interface

To configure a CT1 interface:

2. Enter CT1 interface view. controller t1 number N/A
Up to 24 channel sets can be

3. Bundle timeslots on the channel-set set-number timeslot-list bundled.
interface into a channel set. list [ speed { 56k | 64k } ] The default timeslot speed is 64
kbps.
4. Set other interface See “Configuring other CT1

Optional.
For each channel set, the system automatically creates a serial interface numbered serial
number:set-number. This interface is logically equivalent to a synchronous serial interface where you can
make other configurations about:
• Data link protocol such as PPP and HDLC
• IP address
Configuring other CT1 interface parameters

To configure other CT1 interface parameters:

2. Enter CT1 interface view. controller t1 number N/A
19
Optional.
3. Configure the interface
description text The default description is Interface
description.
name Interface.
• cable long { 0db | -7.5db | Optional.
4. Set the cable length and -15db | -22.5db }
cable attenuation. The long 0db keywords apply by
• cable short { 133ft | 266ft |
default.
399ft | 533ft | 655ft }
Optional.
5. Set the line code format. code { ami | b8zs }
The default is B8ZS1.
Optional.
6. Set the clock mode. clock { master | slave } The default is slave, that is, line
clock.
Optional.
7. Set the framing format. frame-format { esf | sf }
The default is ESF.
8. Set the behavior of the Optional.

interface on the FDL in ESF fdl { ansi | att | both | none } The default is none, meaning that
framing. FDL is forbidden.
loopback { local | remote | Optional.

9. Enable loopback.
payload } Disabled by default.
sendloopcode { fdl-ansi-llb-down |
fdl-ansi-llb-up | fdl-ansi-plb-down Optional.
10. Send remote loopback control
| fdl-ansi-plb-up | No remote loopback control code
code.
fdl-att-plb-down | fdl-att-plb-up | is sent by default.
inband-llb-down | inband-llb-up }
Optional.
12. Shut down the CT1 interface. shutdown A CT1 interface is enabled by
default.
13. Return to system view. quit N/A

14. Enter the view of the
interface serial
synchronous serial interface N/A
interface-number:set-number
created on the CT1 interface.
Optional.
15. Set the CRC mode. crc { 16 | 32 | none }
By default, 16-bit CRC is adopted.
16. Set the MTU of the serial Optional.

mtu mtu
interface. 1500 bytes by default
17. Set the keepalive transmission Optional.

timer hold seconds
interval. 10 seconds by default
Optional.
18. Configure the link layer
PPP by default.
protocol of the serial link-protocol { fr | hdlc | ppp }
interface. Support for Frame Relay depends
on the daughter cards.
20
IMPORTANT:
1. B8ZS = Bipolar 8 zeros substitution; 2. ESF = Extended super frame; 3. LOS = Loss of signal; 4. AIS = Alarm
indication signal; 5. LFA = Loss of frame align
Displaying and maintaining CT1 interfaces

display controller t1
Display the operating state of CT1 [ interface-number ] [ | { begin |
interfaces. exclude | include }

Display the operating state of a interface-number:set-number [ |
serial interface. { begin | exclude | include }
Clear the controller counter of a reset counters controller t1

CT1 interface. interface-number
21
Configuring POS interfaces
Overview
SONET
Synchronous Optical Network (SONET), a synchronous transmission system defined by ANSI, is an
international standard transmission protocol. It uses optical transmission where transmission rates form a
sequence of STM-1, STM-4, and STM-16, each four times the immediate lower level. Because signals are
synchronous, SDH can multiplex multiple signals conveniently.
SDH
Synchronous Digital Hierarchy (SDH), defined by the CCITT (the ITU-T at present), uses a SONET rate
subset. SDH adopts synchronous multiplexing and allows for flexible mapping structure. It can add or
drop low-speed tributary signals to or from SDH signals without a large amount of
multiplexing/demultiplexing devices. This reduces signal attenuation and investment in network devices.
POS
Packet over SONET/SDH (POS) is a technology popular on WAN and MAN. It can support packet data
such as IP packets.
POS maps length-variable packets directly to SONET synchronous payloads and uses the SONET
physical layer transmission standard. It offers high-speed, reliable, and point-to-point data connectivity.
The POS interfaces on your router support PPP, HDLC and FR at the data link layer and IP at the network
layer. Depending on the subcards of a POS interfaces, its transmission rate can be STM-1, STM-4, and
STM-16, each four times the immediate lower level.
Configuring a POS interface

Before you configure the link layer and network layer protocols on a POS interface, you must configure
its physical parameters.
Configuring a POS interface

To configure a POS interface:

2. Enter POS interface view. interface pos interface-number N/A
22
Optional.
By default, the description of a
3. Set the interface description. description text POS interface is interface name
Interface, for example, Pos2/1/1
Interface.
Optional.
4. Set the clock mode. clock { master | slave }
The default is slave.
Optional.
5. Set the CRC length. crc { 16 | 32 }
The default is 32 bits.
Optional.
Loopback is disabled by default.
6. Set the loopback mode. loopback { local | remote }
Enable it only when special test is
desired.
Optional.
• The default is hexadecimal 16
• flag c2 flag-value for C2.
7. Configure the overhead bytes. • flag { j0 | j1 } { sdh | sonet } • By default, SDH framing
flag-value applies. In SDH framing, the
defaults are null for both J0 and
J1.
Optional.
8. Set the framing format. frame-format { sdh | sonet }
The default is SDH.
Optional.
9. Configure scrambling. scramble
Enabled by default.
link-protocol { ppp | hdlc | fr [ ietf Optional.

10. Specify the link layer protocol.
| nonstandard ] } The default is PPP.
Optional.
The MTU in bytes ranges from 46
11. Set the interface MTU. mtu size to 10240and defaults to 1500.
The maximum MTU for POS
interfaces is 9216 bytes.
Optional.
12. Set the SD/SF threshold for
threshold { sd | sf } value The SD threshold defaults to 10e-6.
the interface.
The SF threshold defaults to 10e-4.
Optional.
By default, the rate of a POS
13. Set the rate of the POS interface on a super sub-card is
speed speed-value
interface. 155 Mbps.
This command is available only on
interfaces of sub-card PIC-TCP8L.
14. Set the link state change delay Optional.

link-delay msec milliseconds
for the interface. 1000 milliseconds by default.
23
Optional.
15. Shut down the POS interface. shutdown By default, a POS interface is
enabled.
NOTE:
• The POS interface can work in the master clock mode only when the SRPU (or the main control board)
is installed with a clock daughter card.
• IPv6CP of PPP cannot get the peer IPv6 address through auto negotiation. Therefore, when a POS
interface is used for IPv6 hardware forwarding, you need to configure static routes or routing protocols
on it.
• If no cable is connected to a physical interface, shut down the interface with the shutdown command to
prevent anomalies caused by interference. Use the shutdown command with caution, because once an
interface is shut down, it stops operating.
• You cannot add a POS interface to an MP group, so you cannot configure the ppp mp { mp-group
mp-number | short-sequence } command on a POS interface.
Switching interface type between POS and Layer 3 GE

On sub-card PIC-TCP8L, you can switch the interface type of a POS interface to Layer 3 Gigabit Ethernet
(GE) and vice versa to adapt to different circumstances.
To switch the type of an interface:

• Enter POS interface view:
interface pos Use either command.
interface-number In POS interface view you can switch the
2. Enter interface view. • Enter Layer-3 GE interface type of the interface from POS to Layer-3
view: GE, and in Layer-3 GE interface view
interface GigabitEthernet from Layer-3 GE to POS.
interface-number
3. Switch the interface type. port-type switch interface-type N/A
Displaying and maintaining POS interfaces

Display the status and display interface [ pos ] [ brief [ down ] ] [ | { begin |
configuration information exclude | include } regular-expression ]
of one or all POS display interface pos interface-number [ brief ] [ |
interfaces. { begin | exclude | include } regular-expression ]
Clear statistics on one or

reset counters interface [ pos [ interface-number ] ] Available in user view
all POS interfaces.
24
POS interface configuration example
Directly connecting routers through POS interfaces
Network requirements
As shown in Figure 2,
• Use a pair of single mode optic fiber (respectively for receiving and sending data) to connect the
POS interfaces on Router A and Router B.
• Enable PPP encapsulation on the interfaces.
Figure 2 Network diagram
1. Configure Router A:
# Configure interface POS 2/1/1, setting its physical parameters to defaults.
<RouterA> system-view
[RouterA] interface Pos 2/1/1
[RouterA-Pos2/1/1] ip address 10.110.1.10 255.255.255.0
[RouterA-Pos2/1/1] link-protocol ppp
[RouterA-Pos2/1/1] mtu 1500
[RouterA-Pos2/1/1] shutdown
[RouterA-Pos2/1/1] undo shutdown
2. Configure Router B:
# Configure interface POS 2/1/1.
<RouterB> system-view
[RouterB] interface Pos 2/1/1
# Set the clock mode to master and other physical parameters to defaults.
[RouterB-Pos2/1/1] clock master
[RouterB-Pos2/1/1] ip address 10.110.1.11 255.255.255.0
[RouterB-Pos2/1/1] link-protocol ppp
[RouterB-Pos2/1/1] mtu 1500
[RouterB-Pos2/1/1] shutdown
[RouterB-Pos2/1/1] undo shutdown
You can check the interface connectivity between the POS interfaces with the display interface pos
command and test network connectivity with the ping command.
Connecting routers through POS interfaces across frame relay

As shown in Figure 3, connect routers to a public frame relay network through POS interfaces. The routers
are premise equipment that work as DTE side of frame relay.
25
Router A uses frame relay sub-interfaces to connect Router B and Router C in different network segments.
# Configure POS interface 3/1/1.
<RouterA> system-view
[RouterA] interface Pos 3/1/1
[RouterA-Pos3/1/1] clock slave
# Configure frame relay encapsulation on the interface.
[RouterA-Pos3/1/1] link-protocol fr
[RouterA-Pos3/1/1] fr interface-type dte
[RouterA-Pos3/1/1] quit
# Create sub-interface 1 on the interface.
[RouterA] interface Pos 3/1/1.1
[RouterA-Pos3/1/1.1] ip address 10.10.10.1 255.255.255.0
[RouterA-Pos3/1/1.1] fr dlci 50
[RouterA-Pos3/1/1.1] fr map ip 10.10.10.2 50
[RouterA-Pos3/1/1.1] mtu 1500
[RouterA-Pos3/1/1.1] quit
# Create sub-interface 2 on the interface.
[RouterA] interface Pos 3/1/1.2
[RouterA-Pos3/1/1.2] ip address 20.10.10.1 255.255.255.0
[RouterA-Pos3/1/1.2] fr dlci 60
[RouterA-Pos3/1/1.2] fr map ip 20.10.10.2 60
[RouterA-Pos3/1/1.2] mtu 1500
[RouterA-Pos3/1/1.2] quit
# Configure interface POS 3/1/1.
[RouterB] interface Pos 3/1/1
[RouterB-Pos3/1/1] clock slave
# Configure frame relay encapsulation on the interface.
[RouterB-Pos3/1/1] link-protocol fr
[RouterB-Pos3/1/1] fr interface-type dte
[RouterB-Pos3/1/1] ip address 10.10.10.2 255.255.255.0
26
[RouterB-Pos3/1/1] fr dlci 70
[RouterB-Pos3/1/1] fr map ip 10.10.10.1 70
[RouterB-Pos3/1/1] mtu 1500
Follow the same way to configure Router C.

Check interface connectivity with the display interface pos command and test network connectivity with
the ping command.
Troubleshooting POS interfaces

Symptom 1
The physical state of POS interface is down.
Solution
• Check that the transmitting and receiving fibers-optic are correctly connected to the POS interface.
If you connect the two ends of a fiber-optic to the transmitting end and the receiving end of the same
POS interface, when you execute the display interface command, a “loopback detected” message
is displayed on the screen even if loopback is not enabled.
• If the two routers are directly connected back to back, check that the internal clock is enabled on
either of the two POS interfaces. POS interfaces use line clock by default. However, when two
routers are directly connected, one side must use the internal clock.
Symptom 2
The physical layer is up but the link is down.
Solution
Check the following items:
• The configurations of clock, scrambling and other physical parameters are consistent on the
connected two POS interfaces.
• The same link layer protocol is configured on two sides.
• Both ends are assigned IP addresses.
Symptom 3
A great amount of IP packets are dropped.
Solution
Check the following items:
• The correct clock mode is configured on the POS interface. If not, enormous amount of CRC errors
can be generated.
• The MTU configuration is appropriate.
27
Configuring CPOS interfaces
NOTE:
Only the PIC-CLF2G8L and PIC-CLF4G8L sub-cards have channelized E3/T3 interfaces.
Overview
SONET
Synchronous Optical Network (SONET), a synchronous transmission system defined by the ANSI, is an
international standard transmission protocol. It adopts optical transmission.
SDH
Synchronous Digital Hierarchy (SDH), defined by the CCITT (today’s ITU-T), uses a SONET rate subset.
As SDH uses synchronous multiplexing and a flexible mapping structure, low-speed tributary signals can
be added to or dropped from an SDH signal without a large amount of multiplexing/demultiplexing
devices. This reduces signal attenuation and investment in network devices.
CPOS
The Low-speed tributary signals multiplexed to form an SDH signal are called channels. The channelized
POS (CPOS) interface makes full use of SDH to provide precise bandwidth division, reduce the number
of low-speed physical interfaces on network devices, enhance their aggregation capacity, and improve
the access capacity of leased lines.
The CPOS interface operates at the rate of STM-1.
SDH frame structure

To understand the benefits of CPOS, you need to first understand the frame structure of SDH signal
STM-N.
Low-speed tributary signals should distribute in one frame regularly and evenly for the convenience of
adding them to or dropping them from high-speed signals. The ITU-T specifies that STM-N frames adopt
the structure of rectangle blocks in bytes, as illustrated in Figure 4:
28
Figure 4 STM-N frame structure
9×270×N （bytes)
1 Regenerator
2
Section
3
Overhead
4
5 AU-PTR Payload
6 Multiplex
7 Section
8 Overhead
9
9×N 261×N
STM-N is a rectangle-block frame structure of 9 rows x 270 x N columns, where the N in STM-N equals
the N columns. N takes the value 1, 4, 16, and so on, indicating the number of STM-1 signals that form
SDH signal.
The STM-N frame structure consists of three parts: the section overhead (SOH), which includes the
regenerator section overhead (RSOH) and the multiplex section overhead (MSOH); the administration
unit pointer (AU-PTR); and payload. AU-PTR is the pointer that indicates the location of the first byte of the
payload in an STM-N frame so that the receiving end can correctly extract the payload.
Terms
• Multiplex unit—A basic SDH multiplex unit includes multiple containers (C-n), virtual containers
(VC-n), tributary units (TU-n), tributary unit groups (TUG-n), administrative units (AU-n) and
administrative unit groups (AUG-n), where n is the hierarchical sequence number of unit level.
• Container—Information structure unit that carries service signals at different rates. G.709 defines
the criteria for five standard containers: C-11, C-12, C-2, C-3 and C-4.
• Virtual container (VC)—Information structure unit supporting channel layer connection of SDH. It
terminates an SDH channel. VC is divided into lower-order and higher-order VCs. VC-4 and VC-3
in AU-3 are higher-order virtual containers.
• Tributary unit (TU) and tributary unit group (TUG)—TU is the information structure that provides
adaptation between higher-order and lower-order channel layers. TUG is a set of one or more TUs
whose location is fixed in higher-order VC payload.
• Administrative unit (AU) and administrative unit group (AUG)—AU is the information structure that
provides adaptation between higher-order channel layer and multiplex section layer. AUG is a set
of one or more AUs whose locations are fixed in the payload of STM-N.
Multiplexing E1/T1/E3/T3 channels to form STM-1

In the SDH multiplexing recommended by G.709, more than one path is available for a valid payload
to be multiplexed to form STM-N. The following figures illustrate the multiplexing processes from E1, T1,
E3, and T3 to STM-1.
29
Figure 5 Process of multiplexing E1 channels to form STM-1
Figure 6 Process of multiplexing T1 channels to form STM-1
Figure 7 Process of multiplexing E3 channels to form STM-1
30
Figure 8 Process of multiplexing T3 channels to form STM-1
In actual applications, different countries and regions may adopt different multiplexing structures. To
ensure interoperability, the multiplex mode command is provided on CPOS interfaces. This allows you to
select the AU-3 or AU-4 multiplexing structure.
Calculating E1/T1/E3/T3 channel sequence numbers

Since CPOS interfaces adopt the byte interleaved multiplexing mode, the lower-order VCs are not
arranged in sequential order in a higher-order VC. To understand how TU numbers are calculated, see
the following example where E1 channels are multiplexed to form STM-1 through the AU-4.
As shown in Figure 5, when the AU-4 path is used, the multiplexing structure for 2 Mbps is 3-7-3. The
formula for calculating the TU-12 sequence numbers of different locations in the same VC-4 is as follows:
Sequence number of TU-12 = TUG-3 number + (TUG-2 number – 1) x 3 + (TU-12 Number – 1) x 21
The two TU-12s are adjacent to each other, if they have the same TUG-3 number and TUG-2 number but
different TU-12 numbers with a discrepancy of 1.
NOTE:
The numbers in the aforementioned formula refer to the location numbers in a VC-4 frame. TUG-3 can be
numbered in the range of 1 to 3; TUG-2 in the range of 1 to 7 and TU-12 in the range of 1 to 3. TU-12
numbers indicate the order in which the 63 TU-12s in a VC-4 frame are multiplexed, that is, E1 channel
numbers.
31
Figure 9 Order of TUG-3s, TUG-2s, and TU-12s in a VC-4 frame
TU-12 1
1 1
VC-4 TUG-3 TUG-2 TU-12 2
TU-12 3
TU-12 1
2
TUG-2 TU-12 2
.
TU-12 3
2
.
TUG-3
. TU-12 1
7
TUG-2 TU-12 2
3
TUG-3 TU-12 3
You can calculate TU-12 numbers in the same way when the AU-3 path is used.
When 63 E1 channels or 84 T1 channels are configured on a CPOS interface, you can reference E1 or
T1 channels by referencing the numbers in the range of 1 to 63 or 1 to 84. When connecting your router
to channelized STM-1 interfaces on routers of other vendors, you should consider the possible numbering
differences due to different channel referencing approaches.
Figure 10 Order of TUG-3, VC-3, and C-3 in a VC-4 frame
1
VC-4 TUG-3 TU-3 VC-3 C-3
TUG-3 TU-3 VC-3 C-3
TUG-3 TU-3 VC-3 C-3
The channel number calculation for E3/T3 channels is simpler than that for E1/T1 channels. As shown
in Figure 10, when the AU-4 multiplexing path is used, as TUG-3 and VC-3 are not divided into
lower-order paths, the E3/T3 channel numbers are the TUG-3 numbers. When the AU-3 multiplexing
path is used, you can get the E3/T3 channel numbers in the same way.
Overhead bytes
SDH provides layered monitoring and management of precise division.
It provides monitoring at section and channel levels, where sections are subdivided into regenerator and
multiplex sections, and channels are subdivided into higher-order and lower-order paths. These
monitoring functions are implemented using overhead bytes.
NOTE:
SDH provides a variety of overhead bytes, but only those involved in CPOS configuration are discussed in
this section.
32
• SOH
Section overhead (SOH) consists of regenerator section overhead (RSOH) and multiplex section
overhead (MSOH).
The regeneration section trace message J0 is included in RSOH to send the section access point
identifier repeatedly. Based on the identifier, the receiver can make sure that it is in continuous
connection with the sender. This byte can be any character in the network of the same operator.
If the networks of two operators are involved, the sending and receiving devices at network
borders must use the same J0 byte. With the j0 byte, operators can detect and troubleshoot faults
in advance or use less time to recover networks.
• POH
The payload of an STM-N frame includes path overhead (POH), which monitors low-speed
tributary signals.
While the SOH monitors the section layer, the POH monitors the path layer. The POH is divided
into the higher-order path overhead and the lower-order path overhead.
Higher-order path overhead monitors paths at the VC-4/VC-3 level.
Similar to the J0 byte, the higher-order VC-N path trace byte J1 is included in the higher-order path
overhead to send the higher-order path access point identifier repeatedly. Based on the identifier,
the receiving end of the path can make sure that it is in continuous connection with the specified
sending end. The J1 byte at the receiving and transmission ends should be matched.
In addition, the path signal label byte C2 is also included in the higher-order path overhead to
indicate the multiplexing structure of VC frames and the property of payload, for instance, whether
the path is carrying services, what type of services are carried, and how they are mapped. The
sender and receiver must use the same C2 byte.
CPOS interface application scenario

CPOS is used to enhance the capability of a router in low-speed access aggregation. STM-1 CPOS is
especially suitable for aggregating E1/T1 channels.
At present, some government agencies and enterprises use low-end and mid-range network devices to
access transmission networks through E1/T1 leased lines. Users who require bandwidth between E1 (2
Mbps)/T1 (1.5 Mbps) and E3 (34 Mbps)/T3 (44 Mbps), a data center for example, lease multiple
E1/T1 lines.
The bandwidth of all these users is aggregated to one or more CPOS interfaces through a transmission
network, and then connected to a high-end router where the low-end routers are uniquely identified by
timeslots.
In actual applications, the connection between these low-end routers and the CPOS interfaces may span
more than one transmission network and as such, may require relay. This is similar to the scenario where
low-end devices are connected to a high-end device through one or multiple E1/T1 leased lines. Figure
11 shows such an application scenario.
33
Configuring a CPOS interface

To configure a CPOS interface:

2. Enter CPOS interface view. controller cpos cpos-number N/A
By default, the description of a

CPOS interface is interface name
3. Set the interface description. description text
Interface, for example,
Cpos2/1/9 Interface.
Optional.
SDH by default.
Optional.
5. Set the clock mode. clock { master | slave }
Slave by default.
Optional.
6. Set the loopback mode. loopback { local | remote }
Disabled by default.
Optional.
7. Configure the AUG
multiplex mode { au-3 | au-4 } The default is au-3 for SONET and
multiplexing mode.
au-4 for SDH.
34
Optional.
• The default value of c2 is 0x02
(hexadecimal) and s1 is 0x0f
(hexadecimal). The default
value of s1s0 is 0x0 for SONET
• flag { c2 path-number c2-value and 0x2 for SDH.
8. Configure the SOH and | s1 s1-value | s1s0
• For SONET frames, the default
higher-order path overhead path-number s1s0-value }
value of j0 is 0x01 and that of
bytes. • flag { j0 | j1 path-number } j1 is null; for SDH frames, the
{ sdh | sonet } flag-value initial values (for example, the
value when the router is initially
powered on) of both j0 and j1
are SR8800, and the values
change to null after a change in
the framing format.
10. Shut down the CPOS Optional.

shutdown
interface. By default, a CPOS interface is up.
Optional.
11. Bring up the CPOS interface. undo shutdown
By default, a CPOS interface is up.
Optional.
By default, the SD alarm threshold
12. Configure the signal degrade is 10e-6; the SF alarm threshold is
(SD) threshold and the signal threshold { sd | sf } value 10e-4 for PIC-CLF2G8L and
fail (SF) threshold. PIC-CLF4G8L CPOS sub-cards and
10e-3 for other types of CPOS
sub-cards.
• See “Configuring an E1
channel.”
• See “Configuring a T1
13. Configure E1/T1/E3/T3 channel.”
Optional.
channel attributes. • See “Configuring an E3
channel.”
• See “Configuring a T3
channel.”
NOTE:
• E1 configuration is supported on the CPOS(E) interface module but T1 configuration is supported on the
CPOS (T) interface module.
prevent anomalies caused by interference.
• Use the shutdown command with caution, because once an interface is shut down, it stops operating.
Configuring an E1 channel
To configure an E1 channel:
35
Optional.
The default is no-CRC4.
3. Set the framing format for an e1 e1-number set frame-format
E1 channel. { crc4 | no-crc4 } An E1 channel working in
unframed mode does not support
framing format setting.
4. Set the clock mode for an E1 e1 e1-number set clock { master | Optional.
channel. slave } The default is slave.
5. Set the loopback mode for an e1 e1-number set loopback { local Optional.
E1 channel. | payload | remote } Disabled by default.
Optional.
The default value of C2 is 0x02 (in
e1 e1-number set flag c2 c2-value hexadecimal). The initial value (for
6. Set the overhead bytes for an example, the value when the router
E1 channel. e1 e1-number set flag j2 { sdh |
is initially powered on) of J2 is
sonet } j2-string
“SR8800”, but it changes to null
(the default value) after a change
in the framing format.
• Configure an E1 channel to
operate in unframed mode:
e1 e1-number unframed
• Configure an E1 channel to
operate in framed mode and Use either approach.
7. Configure the operating mode perform timeslot bundling to
for an E1 channel. generate a serial interface By default, the E1 channel
operates in framed mode.
a. (Optional) undo e1
e1-number unframed
b. e1 e1-number channel-set
set-number timeslot-list
range
Optional.
8. Shut down an E1 channel. e1 e1-number shutdown
By default, an E1 channel is up.
Configuring a T1 channel
To configure a T1 channel:

36
Optional.
The default is ESF.
3. Set the framing format for a T1 t1 t1-number set frame-format { esf
channel. | sf } A T1 channel working in unframed
mode does not support framing
format setting.
4. Set the clock mode for a T1 t1 t1-number set clock { master | Optional.
channel. slave } The default is slave.
5. Set the loopback mode for a t1 t1-number set loopback { local | Optional.
T1 channel. payload | remote } Disabled by default.
Optional.
The default value of C2 is 0x02.
• t1 t1-number set flag c2 The initial value (for example, the
6. Set the overhead bytes for a c2-value value when the router is initially
T1 channel. • t1 t1-number set flag j2 { sdh | powered on) of J2 is “SR8800”
sonet } j2-string and the value changes to null (the
default value) after a change in the
framing format.
• Approach I:
Configure a T1 channel to
t1 t1-number unframed
• Approach II:
Configure a T1 channel to
operate in unframed mode and Use either approach.
7. Configure the operating mode
perform timeslot bundling to By default, the T1 channel operates
for a T1 channel.
generate a serial interface: in framed mode.
a. (Optional) undo t1
t1-number unframed
b. t1 t1-number channel-set
set-number timeslot-list
range [ speed { 56k |
64k } ]
Optional.
8. Shut down a T1 channel. t1 t1-number shutdown
By default, a T1 channel is up.
Configuring an E3 channel
To configure an E3 channel:

3. Create a serial interface Optional.

corresponding to the using e3 e3-number By default, no serial interface is
unframed E3 channel. created.
37
4. Configure a serial port Optional.
corresponding to the framed e3 e3-number framed By default, no serial port is
E3 channel. configured.
5. Configure the clock mode of e3 e3-number set clock { master | Optional.

the E3 channel. slave } Slave by default.
6. Enable loopback in the Optional.
e3 e3-number set loopback { local
specified mode on the E3
| payload | remote } Disabled by default.
channel.
Optional.
1 by default.
7. Set the national bit of the E3 e3 e3-number set national-bit { 0 |
channel. 1} This command is unavailable when
an E3 channel works in unframed
mode.
Optional.
8. Shut down the E3 channel. e3 e3-number shutdown
Up by default.
NOTE:
The router does not support adding a serial interface corresponding to the E3 channel to the specified
MP-group.
Configuring a T3 channel
To configure a T3 channel:

3. Create a serial interface Optional.

corresponding to the using t3 t3-number By default, no serial interface is
unframed T3 channel. created.
4. Configure a serial port Optional.

corresponding to the framed t3 t3-number framed By default, no serial port is
T3 channel. configured.
5. Configure the clock mode of t3 t3-number set clock { master | Optional.

the T3 channel. slave } Slave by default
Optional.
C-bit framing by default
6. Set the framing format of the t3 t3-number set frame-format
T3 interface. { c-bit | m23 } A T3 channel working in unframed
mode does not support framing
format setting.
7. Enable loopback in the Optional.
t3 t3-number set loopback { local |
specified mode on the T3
payload | remote } Disabled by default.
channel.
38
NOTE:
The router does not support adding a serial interface corresponding to the T3 channel to the specified
MP-group.
Displaying and maintaining CPOS interfaces

display controller cpos
Display information about
[ cpos-number ] [ | { begin |
channels on a specified or all Available in any view
exclude | include }
CPOS interfaces.

Display information about a
cpos-number e1 e1-number [ |
specified E1 channel on a CPOS Available in any view
{ begin | exclude | include }
interface.

cpos-number t1 t1-number [ |
specified T1 channel on a CPOS Available in any view
interface.

cpos-number e3 e3-number [ |
specified E3 channel on a CPOS Available in any view
interface.

cpos-number t3 t3-number [ |
specified T3 channel on a CPOS Available in any view
interface.

Display information about an [ interface-number:set-number ] [ |
E1/T1/E3/T3 serial interface. { begin | exclude | include }
Clear the controller counter of a reset counters controller cpos

CPOS interface. interface-number
NOTE:
For more information about the display interface and display interface serial commands, see Interface
Command Reference.
CPOS interface configuration example

As shown in Figure 12, branch nodes Router B through Router H are uplinked to the central node Router
A through E1 links and Router A aggregates these E1 links with a CPOS interface.
Add one more E1 link on Router B to expand its capacity. In addition, bind the two E1 links through an
MP-group interface.
39
NOTE:
• Because the clock source of a SONET/SDH network is more precise than the internal clock source of the
router, when connecting the router to a SONET/SDH router, configure the clock mode of the
SONET/SDH router as master.
• This section describes only the important steps in configuring CPOS and E1 interfaces. Other
configurations are not shown.
# Configure the E1 channels of CPOS interface CPOS 3/1/9 to operate in unframed mode.
<Sysname> system-view
[Sysname] controller Cpos 3/1/9
[Sysname-Cpos3/1/9] e1 1 unframed
[Sysname-Cpos3/1/9] e1 2 unframed
# Create MP-group interface 3/1/28 and assign an IP address for it.
[Sysname] interface Mp-group 3/1/28
[Sysname-Mp-group3/1/28] ip address 10.1.1.1 24
[Sysname-Mp-group3/1/28] quit
# Configure interfaces Serial 3/1/9/1:0 and Serial 3/1/9/2:0.
[Sysname] interface Serial3/1/9/1:0
[Sysname-Serial3/1/9/1:0] ppp mp Mp-group 3/1/28
[Sysname-Serial3/1/9/1:0] quit
[Sysname] interface Serial3/1/9/2:0
[Sysname-Serial3/1/9/2:0] ppp mp Mp-group 3/1/28
[Sysname-Serial3/1/9/2:0] quit
The configuration on Router B is similar to that on other branch nodes.
[Sysname] controller E1 3/1/9
[Sysname-E1 3/1/9] using e1
[Sysname-E1 3/1/9] quit
[Sysname] controller E1 3/1/10
[Sysname-E1 3/1/10] using e1
40
[Sysname-E1 3/1/10] quit
# Create MP-group 3/1/28 and assign an IP address for it.
[Sysname] interface Mp-group 3/1/28
[Sysname-Mp-group 3/1/28] ip address 10.1.1.2 24
[Sysname-Mp-group 3/1/28] quit
# Configure Serial 3/1/9:0 and Serial 3/1/10:0.
[Sysname] interface Serial3/1/9:0
[Sysname-Serial3/1/9:0] ppp mp Mp-group 3/1/28
[Sysname-Serial3/1/9:0] quit
[Sysname] interface Serial3/1/10:0
[Sysname-Serial3/1/10:0] ppp mp Mp-group 3/1/28
[Sysname-Serial3/1/10:0] quit
You can use the display interface serial 3/1/9:0 command, the display interface mp-group 3/1/28
command, and the display ppp mp command to display the connection status, and use the ping
command to check network reachability.
Troubleshooting CPOS interfaces

Interface physical status is up, link protocol status is down, and
loopback is detected
Symptom
Connect the CPOS interface of your router to that of another vendor through SDH, bundle E1 channels
on the interface to form a serial interface and encapsulate it with PPP.
Perform the display interface serial command to check information on interface status. It shows that the
physical state of the interface is UP, but the link protocol is DOWN; and loopback, though not configured,
is detected on some interfaces.
Solution
The fault occurs when the multiplex unit configurations on the SDH transmission device mismatch the E1
channel numbers on the CPOS interface on your router. This can result in timeslot inconsistency at the two
ends of transmission and also PPP negotiation failures and LCP anomalies.
In addition, if an idle timeslot on a looped serial interface on the transmission device is used in
transmission, the information that loopback is detected is displayed. Use the debugging ppp lcp error
command to check loopback information.
Follow these steps to solve the problem:
• Use the display controller cpos e1 command to view the multiplexing paths of the E1 channels or
calculate the multiplexing path as shown in “Calculating E1/T1/E3/T3 channel sequence
numbers.”
• Check the configurations on the transmission devices against the calculating result in the last step to
make sure the same E1 multiplexing path is configured.
41
Configuring E-CPOS interfaces
Overview
SONET
Synchronous Optical Network (SONET), a synchronous transmission system defined by the ANSI, is an
international standard transmission protocol over fiber-optic. SONET transmission rates form a sequence
of OC-1 (51.84 Mbps), OC-3 (155 Mbps), OC-12 (622 Mbps), and OC-48 (2.5 Gbps). Because signals
are synchronous, SONET can multiplex signals conveniently.
SDH
Synchronous Digital Hierarchy (SDH), defined by the CCITT (today’s ITU-T) uses a SONET rate subset. As
SDH adopts synchronous multiplexing and allows for flexible mapping, low-speed tributary signals can
be added to or dropped from SDH signals without a large number of multiplexing/demultiplexing
devices. This reduces signal attenuation and investment in network devices.
SDH frame structure

Low-speed tributary signals should distribute in a frame regularly and evenly for the convenience of
adding them to or dropping them from high-speed signals. The ITU-T stipulates that STM-N frames adopt
the structure of rectangle blocks in bytes, as shown in Figure 13:
Figure 13 STM-N frame structure
STM-N is a rectangle-block frame structure of 9 rows x 270 x N columns, where the N in STM-N equals
the N columns. N takes the value 1, 4, 16, and so on, indicating the number of STM-1 signals that form
SDH signal.
The STM-N frame structure consists of three parts: the section overhead (SOH), which includes the
regenerator section overhead (RSOH) and the multiplex section overhead (MSOH); the administration
unit pointer (AU-PTR); and payload. AU-PTR is the pointer that indicates the location of the first byte of the
payload in an STM-N frame so that the receiving end can correctly extract the payload.
42
Multiplexing STM frames
An STM-1 frame adopts the rectangular structure of 270 columns and 9 rows, with the first 10 columns as
the overhead and the rest 260 columns as the payload. An STM-N frame is formed by interleaving N
STM-1 frames.
Figure 14 STM-1 frame structure
• SOH—The SDH section overhead. It is used for monitoring the entire STM-1 frame and does not
carry user data. The SOH consists of the regenerator section overhead (RSOH) and the multiplex
section overhead (MSOH). For example, B1 and B2 are used for bit error rate test (BERT) for the
frame; A1 and A2 are frame synchronization bytes.
• AU-PTR—The administration unit pointer. It indicates the location of the payload in the STM-1
frame.
• POH—Path overhead. It is used for monitoring the payload. For example, the C2 byte in the POH
indicates the payload type, and the G1 byte of the POH indicates whether a bit error is present in
the payload.
• Payload—If channelization stops, the payload carries user data; if channelization continues, the
payload carries the data of multiplexed lower-order channels.
The following figure shows how four STM-1 frames are multiplexed into an STM-4 frame. In the same way,
four STM-4 frames can be multiplexed into an STM-16 frame.
43
Figure 15 Process of multiplexing four STM-1 frames into an STM-4 frame
D
C Section overhead
B Section AUoverhead
pointer payload
A SectionAU
overhead
pointer payload
Section overhead
AUSection
pointer overhead
P payload
Section overhead
AU pointer O payload
Section overheadH
Section overhead
A B C D A B C D
The recipient will demultiplex a received STM-4 frame into four STM-1 frames. During the multiplexing
process, the A1, A2, J0, Z0, B1, E1, F1, D1, D2, and D3 fields in the RSOH of the first frame are
multiplexed into the STM-4 frame while those of the rest three frames are treated as invalid. The other
fields of each frame are multiplexed into the STM-4 frame separately.
Figure 16 shows how an STM-16 frame in the SDH frame format is demultiplexed.
Figure 16 The process of demultiplexing an STM-16 frame in the SDH frame format
Rate hierarchy of SONET/SDH

SDH frames at different rates are identified in the form of STM-N (N equals 1, 4, 16, 64, and so on,
indicating that the frame is formed through multiplexing and interleaving N STM-1 frames). SONET
frames at different rates are identified in the form of STS-N (N equals 1, 3, 12, 48, and so on, indicating
that the frame is formed through multiplexing and interleaving N STS-1 frames. The following table lists
the rate hierarchies of SONET and SDH.
Table 1 Rate hierarchy of SONET/SDH
SONET SDH Rate

STS-1 N/A 51.840 Mbps
44
SONET SDH Rate
STS-3 STM-1 155.52 Mbps
STS-12 STM-4 622.080 Mbps
STS-48 STM-16 2488.320 Mbps
Overhead bytes
SDH provides hierarchical monitoring and management functions. It provides section level monitoring
and path level monitoring. Section level monitoring is subdivided into regenerator section level
monitoring and multiplex section level monitoring, while the path level monitoring is subdivided into
higher-order path level monitoring and lower-order path level monitoring. These monitoring functions are
implemented using overhead bytes.
NOTE:
SDH provides a variety of overhead bytes, but only those involved in E-CPOS configuration are discussed
in this section.
• SOH
The SOH consists of the RSOH and the MSOH.
The regeneration section trace message J0 is included in the RSOH to send the section access point
identifier repeatedly. Based on the identifier, the receiver can make sure that it is in continuous
connection with the sender. This byte can be any character in the network of the same operator.
If the networks of two operators are involved, the sending and receiving devices at network
borders must use the same J0 byte. With the J0 byte, operators can detect and troubleshoot faults
in advance or use less time to recover networks.
• POH
The payload of an STM-N frame includes the path overhead (POH), which monitors low-speed
tributary signals.
While the SOH monitors the section layer, the POH monitors the path layer. The POH is divided
into the higher-order path overhead and the lower-order path overhead.
The higher-order path overhead monitors lower-level paths.
Similar to the J0 byte, the higher-order VC-N path trace byte J1 is included in the higher-order path
overhead to send the higher-order path access point identifier repeatedly. Based on the identifier,
the receiving end of the path can make sure that it is in continuous connection with the specified
sending end. The sender and the recipient must use the same J1 byte.
In addition, the path signal label byte C2 is included in the higher-order path overhead to indicate
the multiplexing structure of VC frames and the properties of payload such as whether the path is
carrying services, what type of services are carried, and how they are mapped. The sender and
the recipient must use the same C2 byte.
45
Terms
• Multiplex unit—A basic SDH multiplex unit includes containers (C-n), virtual containers (VC-n),
tributary units (TU-n), tributary unit groups (TUG-n), administrative units (AU-n), and administrative
unit groups (AUG-n), where n is the unit level sequence number.
• Container—Information structure unit that carries service signals at different rates. G.709 defines
the criteria for five standard containers: C-11, C-12, C-2, C-3 and C-4.
• Virtual container (VC)—Information structure unit supporting path level connection of SDH. It
terminates an SDH path. VCs are divided into lower-order and higher-order VCs. VC-3 in AU-3 and
VC-4 are higher-order VCs.
• Tributary unit (TU) and tributary unit group (TUG)—TU is the information structure that provides
adaptation between higher-order paths and lower-order paths. TUG is a set of one or more TUs
whose locations are fixed in higher-order VC payload.
• Administrative unit (AU) and administrative unit group (AUG)—AU is the information structure that
provides adaptation between the higher-order path layer and the multiplex section layer. AUG is a
set of one or more AUs whose locations are fixed in the STM-N payload.
• Optical carrier (OC)—OC is a series of physical protocols (including OC-1, OC-2, and so on)
defined for optical transmission over an SONET network. The number in an OC level corresponds
to a rate for STS frames. The base rate is 51.84 Mbps (OC-1), the rate of OC-3 is 155.52 Mbps, and
so on.
E-CPOS
The low-speed tributary signals multiplexed to form an SDH signal are called channels. A channelized
POS (CPOS) interface makes full use of SDH to provide precise bandwidth division, reduce the number
of low-speed physical interfaces on network devices, enhance their distribution capacity, and improve
the access capacity of dedicated lines.
The basic functions of enhanced CPOS (E-CPOS) interfaces and CPOS interfaces are the same but their
port rate hierarchies and channelization levels are different. For more information, see “Configuring the
operating mode of an E-CPOS interface/channel.”
Channelized and unchannelized

• A channelized POS interface uses the low-speed tributary signals of STM-N to transmit multiple
streams of data independent of one another over an optical fiber. Each data stream shares
separate bandwidth and has its own start point, end point, and monitoring policy. They are called
channels.
• An unchannelized POS interface uses all STM-N signals to transmit a stream of data over an optical
fiber. The transmitted data has the same identifier, start point, and end point, and is regulated by
the same monitoring policy.
When multiple streams of low-speed signals are to be transmitted, channelization can make better use of
bandwidth. When a single high-speed stream of data is to be transmitted, the unchannelized mode is
recommended.
Operating modes of E-CPOS interfaces

An E-CPOS interface can operate in channelized mode or concatenated mode:
• In channelized mode, a higher-order STM-N frame is regarded as being formed by four lower-order
STM-N frames through time-division multiplexing. In this case, a higher-order STM-N frame will be
demultiplexed into multiple lower-order STM-N frames for processing.
46
• In concatenated mode, STM-N frames are processed without being demultiplexed.
E-CPOS interface application scenario

E-CPOS enhances the capability of network devices in low-speed access redistribution. STM-1 E-CPOS is
especially suitable for aggregating E3/T3 channels. As shown in Figure 17, some government agencies
and enterprises use low-end and mid-range routers to access the transmission network through E3/T3
leased lines. Users who require bandwidth between E3 and T3, for a data center for example, lease
multiple E3/T3 lines. The bandwidth of all these users is aggregated to one or more CPOS interfaces
through the transmission network, and then connected to a high-end router where the low-end routers are
uniquely identified by timeslots.
In actual applications, the connection between these low-end routers and the E-POS interfaces may span
more than one transmission network and as such, may require relay. This is similar to the scenario where
low-end network devices are connected to Router A through one or multiple E3/T3 leased lines.
Configuring an E-CPOS interface

Before transmitting data over SONET/SDH optical interfaces and using low-speed ports for accessing,
configure the E-CPOS interface first.
Complete the following tasks to configure an E-CPOS interface:
• Configuring an E-CPOS interface
• Configuring the operating mode of an E-CPOS interface/channel
Configuring an E-CPOS interface

To configure an E-CPOS interface:

2. Enter E-CPOS interface view. controller e-cpos interface-number N/A
Optional.
3. Set the interface description. description text E-CPOS interface is interface name
Interface, for example,
E-Cpos7/1/6 Interface.
47
Optional.
SDH by default.
Optional.
5. Configure the clocking mode. clock { master | slave }
Slave clocking mode by default.
6. Configure the loopback Optional.

mode. loopback { local | remote }
Disabled by default.
Optional.
AU-4 for SDH, and AU-3 for
7. Configure the AUG SONET by default.
multiplexing path. multiplex mode { au-3 | au-4 }
Only subcards PIC-CLS4G4L and
PIC-CHS1G4L support this
command.
8. Configure the J0 byte. flag j0 { sdh j0-string | sonet

Optional.
j0-value }
Optional.
9. Configure the signal degrade
(SD) threshold and signal fail threshold { sd | sf } value By default, the SD threshold is
(SF) threshold. 10e-6 and the SF threshold is
10e-3.
11. Shut down the E-CPOS Optional.

interface. shutdown
Up by default.
NOTE:
prevent anomalies caused by interference.
• Use the shutdown command with caution, because once an interface is shut down, it stops operating.
Configuring the operating mode of an E-CPOS

interface/channel
As mentioned earlier, E-CPOS interfaces are different from CPOS interfaces in rate hierarchy and
channelization hierarchy. The major types of E-CPOS interfaces supported currently include:
• STM-16 E-CPOS interfaces (at 2488 Mbps), which can be channelized into 2.5 Gbps/622
Mbps/155 Mbps POS channels.
• STM-4 E-CPOS interfaces (at 622 Mbps), which can be channelized into 622 Mbps/155 Mbps
POS channels or E3/T3 serial interfaces.
• STM-1 E-CPOS interfaces (at 155 Mbps), which can be channelized into 155 Mbps POS channels
or E3/T3 serial interfaces.
Configuring the interface/channel operating mode on a 2.5 Gbps E-CPOS interface

You can use the using command to configure a 2.5 Gbps E-CPOS interface to operate in channelized
mode or concatenated mode.
48
To create POS channels, configure the concatenated mode. On a 2.5 Gbps E-CPOS interface in
concatenated mode, you can create sixteen 155 Mbps channels, four 622 Mbps channels, or one 2.5
Gbps POS channel.
1. Configure the operating mode of a 2.5 Gbps E-CPOS interface
To create a 2.5 Gbps POS channel and configure its operating mode on a 2.5 Gbps E-CPOS
interface:

3. Configure the 2.5 Gbps
E-CPOS interface to operate The default is the channelized
using oc-48c
in concatenated mode. mode.
2. Create a 622 Mbps POS channel and configure its operating mode
To create a 622 Mbps POS channel and configure its operating mode on a 2.5 Gbps E-CPOS
interface:

Optional.
By default, a 2.5 Gbps E-CPOS
3. Configure the 2.5 Gbps interface operates in channelized
E-CPOS interface to operate mode.
using oc-48
in channelized mode. Before creating a 622 Mbps POS
channel, you must configure the
2.5 Gbps E-CPOS interface to
operate in channelized mode.
4. Create a 622 Mbps channel
and enter its view. oc-12 oc-12-number N/A
5. Configure the 622 Mbps

channel to operate in The default is the channelized
using oc-12c
concatenated mode. mode.
To create a 155 Mbps POS channel and configure its operating mode on a 2.5 Gbps E-CPOS
interface:

2. Enter E-CPOS interface view. controller e-cpos

N/A
interface-number
49
Optional.
By default, a 622 Mbps E-CPOS
4. Configure the 622 Mbps interface operates in channelized mode.
E-CPOS interface to operate using oc-12 Before creating a 155 Mbps POS
in channelized mode
channel, you must configure the 2.5
Gbps E-CPOS interface to operate in
channelized mode.

channel to operate in using oc-3c Channelized mode by default.
concatenated mode.
Configuring the interface/channel operating mode on a 622 Mbps E-CPOS interface

Use the using command to configure a 622 Mbps E-CPOS interface to operate in channelized mode or
concatenated mode:
• To create POS channels, configure the concatenated mode. On a 622 Mbps E-CPOS interface in
concatenated mode, you can create four 155 Mbps or one 622 Mbps POS interface.
• To create E3 or T3 channels, configure the channelized mode.
1. Configure the operating mode of a 622 Mbps E-CPOS interface
To create a 622 Mbps POS channel and configure its operating mode on a 622 Mbps E-CPOS
interface:

2. Enter 622 Mbps E-CPOS
interface view. controller e-cpos interface-number N/A
3. Configure the interface to

operate in concatenated The default is the channelized
using { oc-12 | oc-12c }
mode. mode.
To create a 155 Mbps POS channel and configure its operating mode on a 622 Mbps E-CPOS
interface:

2. Enter 622 Mbps E-CPOS
interface view. controller e-cpos interface-number N/A

4. Configure the 155 Mbps Optional.

channel to operate in using { oc-3 | oc-3c } The default is the channelized
concatenated mode. mode.
50
3. Create an E3/T3 channel and configure its operating mode
To create an E3/T3 channel and configure its operating mode on a 622 Mbps E-CPOS interface:

2. Enter 622 Mbps E-CPOS interface controller e-cpos
view. N/A
interface-number
3. Enter OC-3 view (the view of a 155
Mbps channel). oc-3 oc-3-number N/A
• Configure the E3 channel to

e3 number unframed Use either approach.
4. Configure the operating mode of the
E3/T3 channel. By default, no E3/T3 channel
• Configure the T3 channel to
is created.
t3 number unframed
Configuring the operating mode for a 155 Mbps E-CPOS interface

You can use the using command to configure a 155 Mbps E-CPOS interface to operate in channelized
mode or concatenated mode.
• To create POS channels, configure the concatenated mode. On a 155 Mbps E-CPOS interface in
concatenated mode, you can create one 155 Mbps POS interface.
• To create E3 or T3 channels, configure the channelized mode.
1. Configure the operating mode of a 155 Mbps E-CPOS interface
To configure the operating mode of a 155 Mbps E-CPOS interface:

E-CPOS interface to operate The default is the channelized
in concatenated mode. mode.
2. Create an E3/T3 channel and configure its operating mode

To configure the operating mode of an E3/T3 channel on a 155 Mbps E-CPOS interface:

2. Enter 155 Mbps E-CPOS interface
view. controller e-cpos interface-number N/A
3. Configure the 155 Mbps E-CPOS

interface to operate in channelized The default is the channelized
mode. mode.
51
• Configure the E3 channel to
e3 number unframed Use either approach.
4. Configure the operating mode for
the E3/T3 channel. By default, no E3/T3 channel
• Configure the T3 channel to
is created.
t3 number unframed
NOTE:
• oc-48 and oc-48c correspond to 2.5 Gbps E-CPOS interfaces.
• oc-12 and oc-12c correspond to 622 Mbps E-CPOS interfaces or 622 Mbps channels channelized from
2.5 Gbps E-CPOS interfaces.
• oc-3 and oc-3c correspond to 155 Mbps E-CPOS interfaces or 155 Mbps channels channelized from
2.5 Gbps E-CPOS interfaces or 622 Mbps E-CPOS interfaces.
Displaying and maintaining E-CPOS interfaces

display controller e-cpos
Display information about all channels of the [ e-cpos-number ] [ | { begin |
specified E-CPOS interface. exclude | include }

Display information about the E3/T3 [ interface-number:set-number ] [ |
channels of the specified E-CPOS interface. { begin | exclude | include }
display interface pos

Display information about the POS channels [ interface-number ] [ | { begin |
of the specified E-CPOS interface. exclude | include }
Clear the controller counter of the specified reset counters controller e-cpos
E-CPOS interface. interface-number
NOTE:
For more information about the display interface serial command, see the chapter “Configuring WAN
interfaces.”
E-CPOS interface configuration example

As shown in Figure 18,
• Router A and Router B provide 622 Mbps E-CPOS interfaces, while Router C and Router D provide
155 Mbps E-CPOS interfaces.
52
• Channelized interface POS 6/1/1/1:0 of Router A is connected to channelized interface POS
6/1/1/1:0 of Router B through an SDH transmission router.
• Channelized interface POS 6/1/1/2:0 of Router A is connected to interface POS 6/1/1:0 of
Router C through an SDH transmission router.
• Channelized interface POS 6/1/1/2:0 of Router B is connected to interface POS 6/1/1:0 of
Router D through an SDH transmission router.
• Each interface uses PPP on the data link layer; all routers use the clock of the SDH transmission
router; the MTU of each interface is 9100 bytes.
# Configure the clock mode of interface E-CPOS 6/1/1.
[Sysname] controller E-Cpos 6/1/1
[Sysname-E-Cpos6/1/1] clock master
# Create two 155 Mbps POS interfaces on interface E-CPOS 6/1/1.
[Sysname-E-Cpos6/1/1] using oc-12
[Sysname-E-Cpos6/1/1] oc-3 1
[Sysname-E-Cpos6/1/1-oc-3-1] using oc-3c
[Sysname-E-Cpos6/1/1-oc-3-1] quit
[Sysname-E-Cpos6/1/1] quit
# Configure channelized interface POS 6/1/1/1:0.
[Sysname] interface Pos6/1/1/1:0
[Sysname-Pos6/1/1/1:0] ip address 10.110.4.1 255.255.255.0
[Sysname-Pos6/1/1/1:0] mtu 9100
[Sysname-Pos6/1/1/1:0] quit
53
# Configure the clock mode of interface E-CPOS 6/1/1.
[Sysname-E-Cpos6/1/1] clock slave
# Create two 155 Mbps POS interfaces for E-CPOS 6/1/1.
[Sysname-E-Cpos6/1/1] quit
3. Configure Router C:
# Create a 155-Mbps POS channel on E-CPOS 6/1/1.
[Sysname-E-Cpos6/1/1] using oc-3c
# Configure POS interface POS 6/1/1:0.
[Sysname]interface Pos6/1/1:0
[Sysname-Pos6/1/1:0] ip address 10.110.5.2 255.255.255.0
[Sysname-Pos6/1/1:0] mtu 9100
[Sysname-Pos6/1/1:0] quit
4. Configure Router D:
# Create a 155-Mbps POS channel on E-CPOS 6/1/1.
[Sysname-E-Cpos6/1/1] using oc-3c
# Configure POS interface POS 6/1/1:0.
[Sysname] interface Pos6/1/1:0
[Sysname-Pos6/1/1:0] ip address 10.110.6.2 255.255.255.0
[Sysname-Pos6/1/1:0] mtu 9100
Use the display interface pos 6/1/1:0 command to check the connectivity status, and use the ping
command to check whether the network is reachable.
54
Troubleshooting E-CPOS interfaces
Symptom
An E-CPOS interface is physically up, the channelized POS interfaces on it are up, but its link layer is
down.
Solution
• The physical parameter settings (such as clock source and scrambling) on the E-CPOS interface do
not match those on the remote E-CPOS interface.
• The link layer protocol of the POS channel does match that of the remote POS channel.
• The bandwidth of POS interfaces channelized from the local E-CPOS interface is not the same as
that of POS interfaces channelized from the remote E-CPOS interface.
• POS interfaces channelized from the local E-CPOS interface are not the same as POS interfaces
channelized from the remote E-CPOS interface in POS interface number.
• PPP authentication fails on the virtual POS interface. PPP authentication maybe fails due to incorrect
PPP authentication parameters.
You can use the display interface pos interface-number command to display the multiplexing path and
PPP link negotiation information of the specified POS interface.
An interface may be in one of the following four states:
• Posinterface-number current state: DOWN ( Administratively ). Line protocol current state: DOWN,
indicating that the interface is administratively shut down.
• Posinterface-number current state: DOWN. Line protocol current state: DOWN, indicating that the
interface is not enabled or has not gone up on the physical layer
• Posinterface-number current state: UP. Line protocol current state: UP, indicating that the interface
has passed LCP negotiation.
• Posinterface-number current state: UP. Line protocol current state: DOWN, indicating that the
interface has been activated but has not passed LCP negotiation.
55
Configuring Loopback and null interfaces
Loopback interface
Introduction
A loopback interface is a software-only virtual interface. It delivers the following benefits.
• The physical layer state and link layer protocols of a loopback interface are always up unless the
loopback interface is manually shut down.
• You must assign a loopback interface an IP address with an all-F mask to save the IP address
resources. When you assign an IPv4 address whose mask is not 32-bit, the system automatically
changes the mask into a 32-bit mask. When you assign an IPv6 address whose mask is not 128-bit,
the system automatically changes the mask into a 128-bit mask.
• You can enable routing protocols on a loopback interface, and a loopback interface can send and
receive routing protocol packets.
Because of the benefits mentioned above, loopback interfaces are widely used in the following
scenarios:
• You can configure a loopback interface address as the source address of the IP packets that the
device generates. Because loopback interface addresses are stable unicast addresses, they are
usually used as device identifications. Therefore, when you configure a rule on an authentication or
security server to permit or deny packets generated by a device, you can simplify the rule by
configuring it to permit or deny packets carrying the loopback interface address identifying the
device. Note that, when you use a loopback interface address as the source address of IP packets,
make sure that the route from the loopback interface to the peer is reachable by performing routing
configuration. All data packets sent to the loopback interface are considered as packets sent to the
device itself, so the device does not forward these packets.
• Because a loopback interface is always up unless you manually shut it down, it can be used in
dynamic routing protocols. For example, if no router ID is configured for a dynamic routing protocol,
the highest loopback interface IP address is selected as the router ID. In BGP, to avoid BGP sessions
being interrupted by physical port failure, you can use a loopback interface as the source interface
of BGP packets.
Configuring a loopback interface

To configure a loopback interface:

2. Create a Loopback interface
interface loopback The loopback interface number
and enter loopback interface
interface-number ranges from 0 to 1023.
view.
56
Optional.
3. Set a description for the By default, the description of an
description text
loopback interface. interface is the interface name
followed by the “Interface” string.
Optional.
4. Shut down the loopback
shutdown A loopback interface is up once
interface.
created.
CAUTION:
Parameters such as IP addresses can be configured on loopback interfaces. For more information, see
Layer 3—IP Services Configuration Guide.
Null interface
Introduction
A null interface is a completely software-based logical interface, and is always up. However, you cannot
use it to forward data packets or configure an IP address or link layer protocol on it. With a null interface
specified as the next hop of a static route to a specific network segment, any packets routed to the
network segment are dropped. The null interface provides a simpler way to filter packets than ACL. You
can filter uninteresting traffic by transmitting it to a null interface instead of applying an ACL.
For example, by executing the ip route-static 92.101.0.0 255.255.0.0 null 0 command (which configures
a static route leading to null interface 0), you can have all the packets destined for the network segment
92.101.0.0/16 discarded.
Currently, only one null interface, interface Null 0, is supported on your router. You cannot remove or
create a null interface.
Configuring interface Null 0

To configure interface Null 0:

Interface Null 0 is the default null

2. Enter null interface view. interface null 0 interface on a router. It can neither
be created nor removed.
Optional.
3. Set a description for the null By default, the description of an
description text
interface. interface is the interface name
followed by the “Interface” string.
57
Displaying and maintaining loopback and null
interfaces
display interface [ loopback ] [ brief
[ down ] ] [ | { begin | exclude |
Display information about loopback include } regular-expression ]
interfaces. display interface loopback
interface-number [ brief ] [ | { begin |
display interface [ null ] [ brief

[ down ] ] [ | { begin | exclude |
Display information about the null include } regular-expression ]
interface. display interface null 0 [ brief ] [ |
Clear the statistics on a loopback reset counters interface [ interface-type

interface or the null interface. [ interface-number ] ]
58
Index
CDELNOPT
C Displaying and maintaining POS interfaces,24
CE1 interface,16 E
Configuring a CPOS interface,34 E-CPOS interface configuration example,52
Configuring a Layer 2 Ethernet interface,8 Ethernet interface overview,1
Configuring a Layer 3 Ethernet interface or L
subinterface,12
Loopback interface,56
Configuring a POS interface,22
Configuring a T1 channel,36 N
Configuring a T3 channel,38 Null interface,57
Configuring a VE interface,13
O
Configuring an E1 channel,35
Configuring an E3 channel,37 Overview,22
Configuring an E-CPOS interface,47 Overview,28
CPOS interface configuration example,39 Overview,42
CT1 interface,19 P
D Performing general configurations,1
Displaying and maintaining an Ethernet interface or POS interface configuration example,25
subinterface,14 T
Displaying and maintaining CPOS interfaces,39
Troubleshooting CPOS interfaces,41
Displaying and maintaining E-CPOS interfaces,52
Troubleshooting E-CPOS interfaces,55
Displaying and maintaining loopback and null
Troubleshooting POS interfaces,27
interfaces,58
59

99-Book 761843 1285 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

99-Book 761843 1285 0

Uploaded by

Copyright:

Available Formats

H3C SR8800 10G Core Routers

Interface Configuration Guide

Hangzhou H3C Technologies Co., Ltd.

Software version: SR8800-CMW520-R3347

All rights reserved

H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,

# A line that starts with a pound (#) sign is comments.

IMPORTANT An alert that calls attention to essential information.

NOTE An alert that contains additional or supplementary information.

TIP An alert that provides helpful information.

Network topology icons

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Port numbering in examples

About the H3C SR8800 documentation set

Product description and Provide an in-depth description of software features

Card datasheets Describe card specifications, features, and standards.

Provides a complete guide to hardware installation

H3C N68 Cabinet

H3C High-End Network Describes the hot-swappable modules available for

Describe software features and configuration

Command references Provide a quick reference to all available commands.

Provide information about the product release,

Configuring Ethernet interfaces ··································································································································· 1

Configuring WAN interfaces ···································································································································· 16

Configuring CPOS interfaces ···································································································································· 28

Configuring E-CPOS interfaces ································································································································· 42

Configuring Loopback and null interfaces ··············································································································· 56

Ethernet interface overview

Performing general configurations

Configuring a combo interface

Changing the active port of a combo interface

Step Command Remarks

Configuring the operating mode for a 10-GE interface

Introduction to J0 and J1 overhead bytes

Step Command Remarks

2. Enter ten-GigabitEthernet interface ten-gigabitethernet

3. Configure a 10-GE interface Optional.

Configuring basic settings of an Ethernet interface or

Step Command Remarks

6. Restore the default settings. default Optional.

Configuring an Ethernet subinterface

Step Command Remarks

2. Create an Ethernet interface interface-type This command also leads you to

4. Restore the default settings. default Optional.

Shutting down an Ethernet interface or subinterface

Step Command Remarks

• Enter Ethernet interface view:

3. Shut down the Ethernet By default, Ethernet interfaces and

Configuring flow control on an Ethernet interface

Step Command Remarks

Step Command Remarks

Configuring loopback testing on an Ethernet interface

Step Command Remarks

Setting the interval for collecting Ethernet interface statistics

Step Command Remarks

2. Configure the interval for Optional

Configuring the link mode of an Ethernet interface

Step Command Remarks

Configuring a Layer 2 Ethernet interface

Configuring storm suppression for an Ethernet interface Optional

Enabling forwarding of jumbo frames Optional

Configuring the MDI mode for an Ethernet interface Optional