Configuration

V2.
04 Documentation Addendum
Table of contents
Table of Contents
Chapter 1 Interface Configuration Overview .............................................................................. 1-1
1.1 Interface Overview ............................................................................................................. 1-1
1.2 Interface Configuration ...................................................................................................... 1-1
1.2.1 Interface View.......................................................................................................... 1-1
1.2.2 Configuring Interface Description............................................................................ 1-2
1.2.3 Configuring an Average Interface Rate Measurement Period ................................ 1-2
1.2.4 Configuring an Interface.......................................................................................... 1-2
1.3 Displaying and Debugging Interfaces ................................................................................ 1-3
Chapter 2 LAN Interface Configuration....................................................................................... 2-1
2.1 Ethernet Interface .............................................................................................................. 2-1
2.1.1 Introduction to Ethernet Interface............................................................................ 2-1
2.1.2 Ethernet Interface Configuration ............................................................................. 2-1
2.1.3 Configuring Flow-Control Mode of Ethernet Interface............................................. 2-5
2.1.4 Displaying and Debugging Ethernet Interface ........................................................ 2-6
2.1.5 Ethernet Configuration Example ............................................................................. 2-6
2.1.6 Troubleshooting....................................................................................................... 2-7
Chapter 3 WAN Interface Configuration...................................................................................... 3-1
3.1 Asynchronous Serial Interface........................................................................................... 3-1
3.1.1 Introduction to Asynchronous Serial Interface ........................................................ 3-1
3.1.2 Configuring Asynchronous Serial Interface............................................................. 3-1
3.2 AUX Interface..................................................................................................................... 3-5
3.2.1 Introduction to AUX Interface .................................................................................. 3-5
3.2.2 Configuring AUX Interface ...................................................................................... 3-6
3.3 Synchronous Serial Interface............................................................................................. 3-7
3.3.1 Introduction to Synchronous Serial Interface .......................................................... 3-7
3.3.2 Configuring Synchronous Serial Interface .............................................................. 3-8
3.4 AM Interface..................................................................................................................... 3-14
3.4.1 AM Interface Overview.......................................................................................... 3-14
3.4.2 Configuring AM Interface ...................................................................................... 3-14
3.5 ISDN BRI Interface .......................................................................................................... 3-15
3.5.1 Introduction to the ISDN BRI Interface.................................................................. 3-15
3.5.2 Configuring an ISDN BRI Interface ....................................................................... 3-17
3.6 CE1/PRI Interface ............................................................................................................ 3-17
3.6.1 Introduction to CE1/PRI Interface ......................................................................... 3-17
3.6.2 Configuring CE1/PRI Interface.............................................................................. 3-18
3.6.3 Displaying and Debugging CE1/PRI Interface Information................................... 3-23
3.7 CT1/PRI Interface ............................................................................................................ 3-24
3Comi
V2.04 Documentation Addendum
Table of contents
3.7.1 Introduction to CT1/PRI Interface.......................................................................... 3-24

3.7.2 Configuring CT1/PRI Interface .............................................................................. 3-24
3.7.3 Displaying and Debugging CT1/PRI Interface Information ................................... 3-29
3.8 E1-F Interface .................................................................................................................. 3-30
3.8.1 Introduction to E1-F Interfaces.............................................................................. 3-30
3.8.2 Configuring E1-F Interface .................................................................................... 3-30
3.8.3 Displaying and Debugging E1-F Interface ............................................................ 3-34
3.9 T1-F Interface .................................................................................................................. 3-34
3.9.1 Introduction to T1-F Interface................................................................................ 3-34
3.9.2 Configuring T1-F Interface .................................................................................... 3-34
3.9.3 Displaying and Debugging T1-F Interface ............................................................ 3-38
3.10 CE3 Interface ................................................................................................................. 3-38
3.10.1 Introduction to CE3 Interface .............................................................................. 3-38
3.10.2 Configuring a CE3 Interface................................................................................ 3-38
3.10.3 Displaying and Debugging CE3 Interface Information ........................................ 3-42
3.11 CT3 Interface ................................................................................................................. 3-43
3.11.1 Introduction to CT3 Interface............................................................................... 3-43
3.11.2 Configuring a CT3 Interface ................................................................................ 3-43
3.11.3 Displaying and Debugging the CT3 Interface Information .................................. 3-47
Chapter 4 ATM/DSL Interface Configuration .............................................................................. 4-1
4.1 ATM/DSL Interface ............................................................................................................ 4-1
4.2 Configuring ATM E3/T3 Interface ...................................................................................... 4-2
4.2.1 Entering Specified ATM E3/T3 Interface View........................................................ 4-2
4.2.2 Configuring Clock Mode of ATM T3 interface ......................................................... 4-2
4.2.3 Configuring Cable Mode of ATM T3 Interface ........................................................ 4-3
4.2.4 Configuring Frame Format of ATM E3/T3 interface................................................ 4-3
4.2.5 Configuring Scramble Function of ATM E3/T3 interface......................................... 4-4
4.2.6 Configuring Loopback Mode ................................................................................... 4-4
4.3 ATM 25M Interface ............................................................................................................ 4-4
4.3.1 Configuring ATM 25M Interface .............................................................................. 4-5
4.4 ATM OC-3c/STM-1 Interface ............................................................................................. 4-6
4.4.1 Configuring ATM OC-3c/STM-1 Interface............................................................... 4-6
4.5 ADSL Interface................................................................................................................... 4-9
4.5.1 Configuring an ADSL Interface ............................................................................. 4-10
4.6 G.SHDSL Interface .......................................................................................................... 4-11
4.6.1 Configuring G.SHDSL Interface ............................................................................ 4-12
4.7 Displaying and Debugging the ATM and DSL Interface Information............................... 4-16
4.8 Troubleshooting ............................................................................................................... 4-17
Chapter 5 Logic Interface Configuration .................................................................................... 5-1
5.1 Dialer Interface................................................................................................................... 5-1
5.1.1 Introduction to Dialer Interface ................................................................................ 5-1
5.2 Loopback Interface ............................................................................................................ 5-1
3Comii
Table of contents
5.2.1 Introduction to Loopback Interface.......................................................................... 5-1

5.2.2 Configuring a Loopback Interface ........................................................................... 5-1
5.3 Null Interface...................................................................................................................... 5-2
5.3.1 Introduction to Null Interface ................................................................................... 5-2
5.3.2 Configuring a Null Interface..................................................................................... 5-2
5.4 Subinterface....................................................................................................................... 5-3
5.4.1 Introduction to Subinterface .................................................................................... 5-3
5.4.2 Configuring a Subinterface...................................................................................... 5-3
5.5 Logic-Channel of Backup Center....................................................................................... 5-7
5.5.1 Introduction to Logic-Channel of Backup Center .................................................... 5-7
5.5.2 Configuring a Backup Center Logic-Channel.......................................................... 5-7
5.6 Virtual-Template and Virtual Interface ............................................................................... 5-7
5.6.1 Introduction to Virtual-Template and Virtual Interface............................................. 5-7
5.6.2 Configuring a Virtual-Template ............................................................................... 5-7
5.6.3 Displaying and Debugging Virtual-Template and Virtual Interface ......................... 5-9
5.6.4 Troubleshooting....................................................................................................... 5-9
5.7 Virtual Ethernet Interface ................................................................................................... 5-9
5.7.1 Introduction to Virtual Ethernet Interface ................................................................ 5-9
5.7.2 Virtual Ethernet Interface Configuration................................................................ 5-10
3Comiii
Documentation Addendum - Interface

V2.04
Chapter 1 Interface Configuration Overview

1.1 Interface Overview
Router interface refers to the part through which a router system exchanges data and
interacts with other devices on the network. It functions to accomplish the data
exchange between the router and other network devices.
V 2.04 supports physical and logical interfaces on routers.
Physical interfaces are those interfaces that physically exist and have the supported
components. Ethernet interfaces and synchronous/asynchronous serial interfaces are
such examples. Physical interfaces include the LAN interface and the WAN interface.
LAN interface mainly refers to the Ethernet interface through which a router exchanges
data with other network devices on the local LAN. WAN interface mainly refers to the
interface through which the router exchanges data with the network devices on an
external network. WAN interfaces include synchronous/asynchronous serial interface,
asynchronous serial interface, AUX interface, AM interface, CE1/PRI interface, and
ISDN BRI interface. Through the WAN interfaces, the router can exchange data with
external network devices.
Logical interface refers to the interface that can implement data exchange but does not
physically exist and needs to be set up through configuration. It can be a dialer
interface, subinterface, backup center logic-channel or virtual-template.
1.2 Interface Configuration

1.2.1 Interface View
Interface view is designed in the V 2.04 software for the convenience of configuration
and maintenance. All the commands related to an interface can become valid only
when they are used in the view of the interface.
I. Method to enter the interface view

Perform the following configuration in system view to enter the specified interface view.
Table 1-1 Entering specified interface view
Operation
Command
Enter specified interface view
interface type number
3Com Corporation
1-1

V2.04
Note:
In V 2.04, the command used for entering the E1/T1 interface view is controller { e1 |
t1 }, which is different from those for entering other interface views.
II. Method to exit interface view

Return to system view by executing the quit command in interface view.
1.2.2 Configuring Interface Description

In V 2.04, there is an interface description configuration entry for each physical
interface on routers for the purpose of identifying the function of the interface. Perform
the following configuration in interface view.
Table 1-2 Configuring interface description
Operation
Command
Configure interface description
description interface-description
Restore the interface description to default
undo description
1.2.3 Configuring an Average Interface Rate Measurement Period

In system view, you can configure the average interface rate measurement period on
all the interfaces; in interface view, you can the measurement period on the current
interface.
Table 1-3 Configuring an average interface rate measurement period
Operation
Command
Configure an average interface rate

measurement period.
flow-interval seconds
Restore the default average interface

rate measurement period.
undo flow-interval seconds
1.2.4 Configuring an Interface

Before configuring an interface, you should make sure that you have fully understood
the networking requirements and the networking diagram. Configuring an interface
includes the following tasks:
3Com Corporation
1-2

V2.04
z
If the interface is a physical one, you should specify its connection state, operating
mode, and the relevant operating parameters.
If the interface is a WAN interface, you should configure the link layer protocol
agreed by the connected remote interface as well as the operating parameters.
Assign a network protocol (such as IP) address to the interface
Configure the static routing of the destination network reachable through the
interface, or configure the working parameters of the dynamic routing protocol on
the interface.
If the interface supports dial-up, you should also configure parameters in Dial
Control Center (DCC) operation and modem management.
If the interface is working as a master interface or standby interface in the backup

center, you should configure the relevant backup center operating parameters.
If you want to set up a firewall on the interface, you should configure the
parameters in packet filtering, address translation and so on.
Many parameters need to be configured in interface view. This part mainly introduces
some specific parameter configurations of physical interfaces and makes a simple
introduction to logical interfaces. For the sake of simplicity and clarity, this part will not
cover the configuration in link layer and network layer protocols, their relevant
parameters, and some special functions (such as dial, backup center, and firewall) that
have been discussed in other parts of the manual.
1.3 Displaying and Debugging Interfaces

Table 1-4 Displaying and debugging interfaces
Operation
Command
Display the current operating state and

statistics of interfaces in any view
display interface [type number ]
Display the major configuration

information of interfaces in any view
display ip interface [type number ]
Clear the interface statistic information

in any view
reset counters interface [ type

number ]
Shut down an interface in interface view
shutdown
Re-enable the interface in interface view
undo shutdown
Enable debugging at a specified

interface
debugging physical { all | error | cell |

packet } interface interface-type
interface-number
Disable debugging at a specified

interface
undo debugging physical { all | error |

cell | packet } interface interface-type
interface-number
3Com Corporation
1-3

V2.04
When the physical or the protocol status changes, the system will automatically output
the corresponding prompting information as shown in the following table, taking the
interface Serial0/0/0 as an example.
Table 1-5 Interface status information
Interface status information
Definition
% Interface Serial0/0/0 is down
The interface is shutdown by the user
% Interface Serial0/0/0 is reset
The interface is re-enabled by the user
%01:10:34: Interface Serial0/0/0

changed state to DOWN
The physical status of the interface

changed to DOWN
%01:11:03: Interface Serial0/0/0

changed state to UP
The physical status of the interface

changed to up
%01:12:02: Line protocol ip on interface

Serial0/0/0, changed state to DOWN
The protocol status of the interface

changed to down
%01:11:34: Line protocol ip on interface

Serial0/0/0, changed state to UP
The protocol status of the interface

changed to up
Note:
When a certain physical interface of the router is not in use, i.e., not connected with
cables, the shutdown command can be used to disable the interface. In this way, the
abnormal interface caused by disturbance can be avoided.
3Com Corporation
1-4
Chapter 2 LAN Interface Configuration

The local area network (LAN) mainly includes Ethernet and Token-Ring network.
Currently, Ethernet has become the most important LAN networking technology thanks
to its high flexibility, relative simplicity and easy implementation.
So far, LAN interfaces supported by V 2.04 are Ethernet interfaces which include the
traditional Ethernet interface and the FE interface.
2.1 Ethernet Interface

2.1.1 Introduction to Ethernet Interface
I. Ethernet interface types
Fast Ethernet (FE) interfaces supported by 3Com Routers include electrical and optical
interfaces, complying with 100Base-TX and 100Base-FX physical layer criteria
respectively. The supported Gigabit Ethernet (GE) interfaces also include electrical and
optical interfaces. GE electrical interfaces comply with 1000Base-TX criterion, and GE
optical interfaces comply with 1000Base-LX and 1000Base-SX criteria.
II. Operating speed and mode

FE electrical interfaces can work at the speeds of 10Mbps and 100Mbps; GE electrical
interfaces can work at the speeds of 10Mbps, 100Mbps, and 1000Mbps.
In terms of operating modes, both FE and GE electrical interfaces support half and full
duplex modes.
To simplify system configuration and management, both FE and GE electrical
interfaces support auto-negotiation, allowing them to negotiate with other network
devices for the optimum working modes and rates.
Optical interfaces can only work in full duplex modes and their speeds cannot be
changed. FE optical interfaces can only work at the speed of 100Mbps and GE optical
interfaces can only work at 1000Mbps.
III. Supported frame formats

Both FE and GE interfaces support the Ethernet frames in Ethernet_II or
Ethernet_SNAP format, and can automatically identify their formats. They send frames
in Ethernet_II format.
2.1.2 Ethernet Interface Configuration

Ethernet Interface configuration includes:
3Com Corporation
2-1
Enter specified Ethernet interface view
Set the network protocol address
Configure Maximum Transmission Unit (MTU)
Select the operating speed of Ethernet interface
Select the operating mode of Ethernet interface
Enable or disable remote loopback
Configure flow-control mode of GE interface
The specified Ethernet interface can not be configured unless you enter its interface
view. It's necessary to configure IP address. You are recommended not to enable other
configuration tasks of Ethernet interface, as their default settings are enough for the
normal operation of the system in most circumstances.
I. Entering specified Ethernet interface view

Perform the following configuration in system view.
Table 2-1 Entering the specified Ethernet interface view
Operation
Command
Enter the specified Ethernet interface

view
interface ethernet number
Enter GE interface view
interface GigabitEthernet
interface-number
II. Setting network protocol address

Perform the following configuration in Ethernet interface view.
Table 2-2 Assigning an IP address to the interface
Operation
Command
Assign an IP address to the interface
ip address ip-address mask [ sub ]
Remove the IP address of the interface
undo ip address [ ip-address mask ]

[ sub ]
When an Ethernet interface is configured with two or more IP addresses, use the
keyword "sub" to identify the second one and those behind it (that is, the secondary IP
addresses).
III. Configuring MTU

The configuration of MTU can affect the fragment and reassembly of IP packets.
3Com Corporation
2-2
Table 2-3 Configuring MTU

Operation
Command
Configure MTU
mtu size
Restore MTU to default
undo mtu
The frame format defaults to Ethernet_II and MTU size is in the range of 46 to 1500
bytes.
Note:
MTU only affects IP packet assembly/disassembly. MTU can reach 1500 bytes in the
Ethernet_II format. After using the mtu command to change the MTU of an interface,
you need to execute the shutdown command and then the undo shutdown command
to restart the interface, so as to validate MTU configuration.
Since QoS queue length is limited, too small MTU and too big packet may result in a lot
of fragments and QoS queues discarding packets. To avoid this, you can increase QoS
queue length. By default, the queue scheduling mechanism adopted on the interfaces
of 3Com Routers is FIFO. You can use the qos fifo queue-length command to change
the queue length. For detailed QoS queue configuration, see the section of QoS
configuration in this manual.
IV. Selecting operating speed of Ethernet interface

Ethernet interfaces support multiple speeds. FE electrical interfaces support 10Mbps
and 100Mbps. FE optical interfaces only support 100Mbps. GE electrical interfaces
support 10Mbps, 100Mbps, and 1000Mbps. GE optical interfaces can only work at
1000Mbps. Thus, you only need to configure Ethernet electrical interfaces while do not
need to configure optical interfaces.
Table 2-4 Selecting an operating speed for an Ethernet interface
Operation
Command
Select an operating speed for the FE

interface
speed { 100 | 10 | negotiation }
Configure the operating speed for a GE

electrical interface
speed { 10 | 100 | 1000 | negotiation }
Restore the default operating speed
undo speed
3Com Corporation
2-3
By default, negotiation is selected, i.e., the system automatically chooses an optimum

operating speed.
Note:
z
By default, both operating speeds and modes of FE and GE electrical interfaces are
negotiation. You can force to change the operating speeds and modes, but should
keep the speed and mode the same as those of the peer end.
If you force to execute the duplex negotiation or speed negotiation command,

the Ethernet electrical interfaces are set to the negotiation mode, and negotiate
speed and duplex mode.
In terms of GE electrical interfaces, the operating speed 1000Mbps and half-duplex

mode are mutually exclusive. Thus, you cannot set these two values at the same
time.
V. Selecting an operating mode for an Ethernet interface

As mentioned earlier, an Ethernet interface can work at both full-duplex mode and
half-duplex mode. Connected to a hub, the Ethernet interface on a router must be
specified to work in half-duplex mode. Connected to a LAN Switch, however, it must be
specified to work in full-duplex mode. Both FE and GE electrical interfaces support
these two modes. Whereas FE and GE optical interfaces can only work in full-duplex
mode.
Perform the following configuration in Ethernet interface view to select an operating
mode.
Table 2-5 Selecting an operating mode for the FE interface
Operation
Command
Select an operating mode for the FE

interface
duplex { negotiation | full | half }
By default, negotiation is set on both FE and GE electrical interfaces. That is, the
system automatically negotiates an optimum operating mode.
Note:
In terms of GE electrical interfaces, the operating speed 1000Mbps and half-duplex
mode are mutually exclusive. Thus, you cannot set these two values at the same time.
3Com Corporation
2-4
VI. Enabling or disabling loopback

Sometimes, you need to enable local loop on an interface for the purpose of testing
some special functions. Perform the following configuration in Ethernet interface view
to enable an interface to make local loop.
Table 2-6 Enabling or disabling local loop
Operation
Command
Enable local loop
loopback
Disable local loop
undo loopback
By default, local loop is disabled.
Note:
z
Ethernet interfaces will work in full-duplex mode when loopback is enabled.
If the operating speed is 1000Mbps or negotiation, the system will force to convert
it to 100Mbps when loopback is enabled. And it will restore the original setting when
loopback is disabled.
When loopback is enabled, you can change the GE operating speed to 10Mbps or
100Mbps. If the new speed is different from the current speed, it starts loopback in
the new speed and saves the new configuration. In other cases (GE operating
speed is changed to 1000Mbps or negotiation, or operating mode is changed to
half-duplex mode), the new configuration is saved. It disables loopback and starts to
work in the new mode.
2.1.3 Configuring Flow-Control Mode of Ethernet Interface

Table 2-7 Configuring flow-control mode of Ethernet interface
Operation
Command
Enable the flow-control on Ethernet interface
flow-control
Restore the default mode
undo flow-control
By default, flow-control is disabled. Only when the peer end supports flow-control, can
this flow-control be applied.
3Com Corporation
2-5
When flow-control is set to negotiation, the system cannot enter normal UP state if the
negotiation fails. If you have set negotiation on a local interface, you are
recommended to execute the shutdown command and then the undo shutdown
command to restart the interface when the configuration of the peer end changes, so as
to keep the flow-control mode the same on both ends.
2.1.4 Displaying and Debugging Ethernet Interface

Perform the following configuration in any view.
Table 2-8 Displaying the state of a specified Ethernet interface
Operation
Command
Display the state of a specified Ethernet

interface
display interfaces ethernet number
2.1.5 Ethernet Configuration Example

I. Networking requirements
As shown in the following figure, the Ethernet interface on Router A is connected to the
IP network 192.168.0.0. The computers on the LAN are connected to the Internet via
Router A. Set the MTU on the Ethernet interface to 1492 bytes.
II. Networking diagram

LAN
Interface Address
192.168.0.1
E0
Network Address
192.168.0.0
Internet
Router A
Figure 2-1 Networking diagram of Ethernet configuration example
III. Configuration procedure

# Assign the IP address 192.168.0.1 to Ethernet 0/0/0, given the mask is 255.255.0.0.
[3Com] interface ethernet 0/0/0
[3Com-Ethernet0/0/0] ip address 192.168.0.1 255.255.0.0
# Set the MTU on the interface to 1492 bytes.

[3Com-Ethernet0/0/0] mtu 1492
3Com Corporation
2-6
2.1.6 Troubleshooting
You can perform the following operations to determine the correctness of the Ethernet
interface.
z
Ping the Ethernet interface on the router from a host locating on the same LAN,
anticipating that all the packets can be correctly returned.
Look up the statistics of the connected two parties (router and switch for example),
anticipating that the received error frames have not rapidly increased.
If the test result of either item is incompliance with the anticipation, you can conclude
that the Ethernet interface or its connection is not properly working.
After confirming the existence of a fault, you can isolate it following these steps:
Step: Check that the LAN connection between the host and the router is correct.
If the Ethernet is connected to a hub or LAN Switch, check the ON/OFF status of the
LEDs for the link to the hub or LAN Switch. ON LEDs mean that the Ethernet interface
between the host and the router and the network cable are physically normal.
Otherwise, please replace such physical devices as the network adapter, network
cable, router or the relevant interface module.
If the Ethernet is connected using Unshielded Twisted Pair (UTP) and if at least one of
the connection parties supports 100Base-TX, rate matching must be taken into
consideration. An operating rate mismatch between the two parties, i.e., one is working
at 100 Mbps and the other at 10 Mbps, will cause faults. From the perspective of the
one working at 100 Mbps, no connection can be set up. From the perspective of the one
working at 10 Mbps, the connection can be set up but the physical layer activity LED
(ACTIVE) will keep blinking quickly and data transmission and receipt cannot be carried
out properly.
When looking for the connection problems of FE interface on 3Com Routers, there are
two prompt messages that are very helpful. These two messages are displayed on the
Console screen upon your operation of selecting speed or connecting network.
Ethernet 0/0/0: Warning--the link partner do not support 100M mode
Ethernet 0/0/0: Warning--the link partner may not support 10M mode
The first prompt message indicates that the Ethernet interface on the 3Com Router has
detected that the remote end does not support 100Mbps operating speed, but the local
end is forced to work at 100Mbps. In this case, you should ensure the remote end to
make the same configuration so that it can work at 100 Mbps. The second prompt
message indicates that the Ethernet interface on the 3Com Router has detected that
the remote end does not support 10Mbps operating speed, but the local end is forced to
work at 10Mbps. In this case, the user should ensure that the remote end can work at
10Mbps. However, when the FE interface on 3Com Routers is connected to the 10/100
Mbps adaptive port of the hub, this information doesnt mean setting is incorrect.
3Com Corporation
2-7
Step 2: View whether IP addresses of the Ethernet interfaces of the host and router are
in the same subnet. In other words, they must use the same network address but
different host addresses. If they are not in the same subnet, please set a new IP
address.
Step 3: Check that the operating mode of the Ethernet interface is correct. When the
Ethernet is connected using UTP or fiber, 10Base-T/100Base-TX/100Base-FX
standard provisions two operating modes, that is, full duplex and half duplex. When a
hub is used for connecting the Ethernet, the interface should work in half-duplex mode.
When a LAN Switch working in half duplex mode is used, the Ethernet interface of the
router must also work in half duplex mode. If the LAN Switch is working in full duplex
mode, the Ethernet interface of the router must also work in full duplex mode. If the
operating mode is incorrect, i.e. one party of the connection is working in full duplex
mode while the other party in half duplex mode, fault will occur. That is, when the
network traffic increases, the party operating in half duplex mode shows frequent
network collisions. For example, if Hub is connected, all the other devices in the whole
network segment will have serious network collisions. The party operating in full duplex
mode will receive a large amount of error messages, accompanied with serious
message losses at both parties. In this case, use display interface ethernet command
to view the error ratio of transmitting and receiving messages on the Ethernet interface.
Usually, the collision can be observed through the state LEDs of the Ethernet interface.
Step 4: Check that flow-control mode of Ethernet interface is correct.
By default, flow-control is disabled on Ethernet interface. If flow-control mode is used at
the peer end, the interface might not be able to go up. In this case, please keep the
flow-control mode the same at both ends. Restart the interface using the shutdown
and undo shutdown commands.
Contact our technical support engineers if you still cannot locate the problem by using
the above methods.
3Com Corporation
2-8
Chapter 3 WAN Interface Configuration

In terms of line type, WANs can be divided into X.25 network, Frame Relay (FR)
network, ATM network, and ISDN network. Commensurate with this division, the
routers are designed to support asynchronous serial interface, synchronous serial
interface, ATM interface, ISDN BRI interface, CE1/PRI interface and so on.
So far, the WAN interfaces supported by V 2.04 include asynchronous serial interface,
AUX interface, AM interface, FCM interface, synchronous serial interface, ISDN BRI
interface, CE1/PRI interface, CT1/PRI interface, CE3 interface, and CT3 interface.
3.1 Asynchronous Serial Interface

3.1.1 Introduction to Asynchronous Serial Interface
Two types of asynchronous serial interfaces are available in V 2.04. One is the
synchronous/asynchronous serial interface working in asynchronous mode and is
named Serial and the other is the dedicated asynchronous serial interface and is
named Async.
Asynchronous serial interface can work for leased line purpose or dial purpose. Dial
approach is more commonly adopted in the applications. Connected to an external
modem or ISDN Terminal Adapter (TA), the asynchronous serial interface can be used
as a dial-up interface and the link layer protocol in this case can be set to SLIP or PPP
and the network protocols like IP and IPX can be supported.
3.1.2 Configuring Asynchronous Serial Interface

Perform the following tasks to configure an asynchronous serial interface.
z
Set the synchronous/asynchronous serial interface to work in asynchronous mode
Enter the specified asyn serial interface view
Set link layer protocol
Set baud rate
Set link setup method
Enable/Disable level detection
Enable/Disable loopback
Configure MTU
Set modem coding format
Configure the interval for sending keepalive packets
Depending on the requirements, you probably also need to configure the asynchronous
serial interface with the parameters in SLIP or PPP, DCC, IP address, firewall, backup
center, and so on. For details, refer to the relevant sections in this manual.
3Com Corporation
3-1
I. Setting the synchronous/asynchronous serial interface to work in

asynchronous mode
If the physical interface to be configured is a synchronous/asynchronous serial
interface, you must first execute the following command to set it to work in
asynchronous mode.
Perform the following configuration in synchronous/asynchronous serial interface view.
Table 3-1 Setting the synchronous/asynchronous serial interface to work in
asynchronous mode
Operation
Command
Set the synchronous/asynchronous serial

interface to work in asynchronous mode
physical-mode async
The operating mode of synchronous/asynchronous serial interface defaults to

synchronous mode.
II. Entering the specified asynchronous serial interface view

Perform the following configuration in system view to enter the specified asynchronous
serial interface view.
Table 3-2 Entering the specified asynchronous serial interface view
Operation
Command
Enter the view of the specified dedicated

asynchronous serial interface.
interface async interface-number
Enter the view of the specified

synchronous/asynchronous serial
interface (which has been set to work in
asynchronous mode)
interface serial interface-number
III. Setting link layer protocol

The link layer protocol of asynchronous serial interface can be set to SLIP or PPP.
Perform the following configuration in asynchronous serial interface view.
Table 3-3 Setting the link layer protocol of an asynchronous serial interface
Operation
Command
Set the link layer protocol of an asynchronous serial

interface
link-protocol { slip | ppp }
The link layer protocol defaults to PPP.

3Com Corporation
3-2
IV. Setting baud rate

Table 3-4 Setting baud rate of an asynchronous serial interface
Operation
Command
Set baud rate of an asynchronous serial interface
baudrate baudrate
The baud rate of asynchronous serial interface defaults to 9600 bps.

When an asynchronous serial interface is working for setting up a dial-up connection,
its baud rate is only the communication rate between it and the connected modem. As
the rate between two modems at the two ends of the link must be the one that they have
negotiated depending on the line quality, the asynchronous serial interfaces on the
routers at the two ends are allowed of difference in baud rate setting.
When the asynchronous serial interface is working as a leased line, however, its baud
rate must be the same one set on the remote device.
Note:
After the synchronous/asynchronous serial interface is set to work in asynchronous
mode, the router will automatically change the baud rate to 9600 bps.
V. Setting link setup method

There are two link setup approaches available for asynchronous serial interfaces. They
are:
z
Protocol mode, with which the local end directly adopts the configured link layer
protocol parameters to set up a link with the remote end after setting up a physical
link. This approach is normally adopted in the event that two asynchronous serial
interfaces are directly connected.
Flow mode, which is also known as interactive mode. With this approach, the two
ends set up a link by interacting with each other upon the setup a physical link.
Specifically, the calling party sends the configuration commands to the called
party (it is equal to the operation of manually inputting configuration commands at
the remote end), sets the link layer protocol operating parameters of the called
party, and then sets up the link. This approach is normally adopted in the event of
man-machine interaction.
3Com Corporation
3-3
Table 3-5 Setting the link setup approach applied to an asynchronous serial interface
Operation
Command
Configure an asynchronous serial interface

to set up a link with the protocol approach
async mode protocol
Configure an asynchronous serial interface

to set up a link with the flow approach
async mode flow
By default, the system adopts the protocol approach for link setup.
VI. Enabling/Disabling level detection

If an asynchronous serial interface has been disabled to make level detection, the
system will only detect whether the interface is connected to an external cable and
automatically report the interface state (UP or DOWN) to the user. If the interface has
been enabled to make level detection, the system will detect the DSR signal in addition
to the external cable. The interface will be regarded UP only if the detected DSR signal
is valid. Otherwise, it will be regarded DOWN.
Table 3-6 Enabling/Disabling an asynchronous serial interface to make level detection
Operation
Command
Enable an asynchronous serial interface to make level

detection
detect dsr-dtr
Disable the asynchronous serial interface to make

level detection
undo detect dsr-dtr
By default, asynchronous serial interfaces are allowed to make level detection.
VII. Enabling/Disabling loopback

You may enable an asynchronous serial interface to make local loop for the purpose of
testing some special functions.
Table 3-7 Enabling/Disabling an asynchronous serial interface to make local loop
Operation
Command
Enable an asynchronous serial interface to make

local loop
loopback
Disable an asynchronous serial interface to make

local loop
undo loopback
3Com Corporation
3-4
VIII. Configuring MTU

The MTU setting of an asynchronous serial interface can affect the fragmentation and
reassembly of IP packets on the interface.
Table 3-8 Setting MTU on an asynchronous serial interface
Operation
Command
Set MTU on an asynchronous serial

interface
mtu size
Restore the default MTU
undo mtu
The parameter size is the MTU setting made on an asynchronous interface, which is in
the range of 128 to 1500 bytes and defaults to 1500 bytes.
IX. Configuring the interval for sending keepalive packets

A serial interface detects the link state by sending keepalive packets to the remote end
at a specified regular interval.
Perform the following configuration in serial interface view.
Table 3-9 Configuring the interval for sending keepalive packets
Operation
Command
Configure the interval for sending keepalive

packets
timer hold seconds
Restore the default value of the interval for

sending keepalive packets
undo timer hold
The keepalive packet sending interval defaults to 10 seconds.
3.2 AUX Interface

3.2.1 Introduction to AUX Interface
AUX interface is a fixed interface provided by 3Com Routers. It can work as a regular
asynchronous serial interface at a speed up to 115200 bps. With this interface, you can
make remote configuration, implement line backup and some other functions on the
routers.
3Com Corporation
3-5
3.2.2 Configuring AUX Interface

Perform the following tasks to configure the AUX interface:
Set link setup method
Set level detection
Set local loop
Set link layer protocol type
I. Setting link setup method

There are two link setup approaches available for the AUX interface. They are:
z
Protocol mode, with which the local end directly adopts the configured link layer
protocol parameters to set up a link with the remote end after setting up a physical
link.
Flow mode, which is also known as interactive mode. With this approach, the two
ends set up a link by interacting with each other upon the setup of a physical link.
Specifically, the calling party sends the configuration commands to the called
party (it is equal to the operation of manually inputting configuration commands at
the remote end), sets the link layer protocol operating parameters of the called
party, and then sets up the link. This approach is normally adopted in the event of
man-machine interaction in dial access. Users in interactive mode are also called
EXEC users.
Perform the following configuration in AUX interface view.

Table 3-10 Setting a link setup mode on an AUX interface
Operation
Command
Configure the AUX interface to set up links with the

protocol approach
async mode protocol
Configure the AUX interface to set up links with the

flow approach
async mode flow
The link setup mode defaults to flow mode.
II. Setting level detection

If the AUX interface has been disabled to make level detection, the system will only
detect whether the interface is connected to an external cable and then report the
interface state (UP or DOWN) to the user. If the interface has been enabled to make
level detection, the system will detect the DSR(Data Set Ready) signal in addition to the
external cable. The interface will be regarded UP only if the detected DSR signal is
valid. Otherwise, it will be regarded DOWN.
3Com Corporation
3-6
Table 3-11 Setting the level detection function on the AUX interface
Operation
Command
Enable the AUX interface to make level detection
detect dsr-dtr
Disable the AUX interface to make level detection
undo detect dsr-dtr
By default, level detection is enabled.
III. Setting local loop

You may enable the AUX interface to make local loop for the purpose of testing some
special functions.
Table 3-12 Enabling/Disabling the AUX interface to make local loop
Operation
Command
Enable the AUX interface to make local loop
loopback
Disable the AUX interface to make local loop
undo loopback
IV. Setting link layer protocol type

Table 3-13 Setting the link layer protocol of the AUX interface
Operation
Command
Set the link layer protocol of the AUX interface to PPP
link-protocol ppp
The other configurations of the AUX interface (e.g., rate, stop bit, parity and flow control)
should be performed in user-interface view. See the User Interface Configuration
section in System Management Module of this manual.
3.3 Synchronous Serial Interface

3.3.1 Introduction to Synchronous Serial Interface
A synchronous serial interface has the following features:
z
It can work in either DTE or DCE mode. Usually, it serves as a DTE device and
accepts the clock provided by the DCE device.
3Com Corporation
3-7
It can be connected to various cables, such as V.24 , V.35, X.21, RS449, RS530
etc. As V 2.04 can automatically detect the type of external cables connected to
the synchronous serial interface and complete the selection of electric features,
you do not need to make the manual configuration in most cases.
It supports the link layer protocols PPP, FR, LAPB, X.25 etc.
It supports the network layer protocols IP and IPX.
It allows you to view information like the current external cable type and the
operating mode (DTE/DCE) by executing the display interface serial command.
3.3.2 Configuring Synchronous Serial Interface

Perform the following tasks to configure a synchronous serial interface:
z
Set the synchronous/asynchronous serial interface to work in synchronous mode
Enter the specified synchronous serial interface view
Set link layer protocol
Set digital signal coding format
Set baud rate
Select operating clock
Set clock inversion
Configure MTU
Enable/Disable level detection
Enable/Disable data carrier detection
Set the full/duplex mode of synchronous serial interface
Configure the interval for sending keepalive packets
Configure line idle-mark of synchronous serial interface
Depending on the requirements, you probably also need to configure the synchronous
serial interface with the parameters in PPP/X.25/FR, DCC, IP address, firewall, backup
center, and so on. For details, refer to the relevant sections in this manual.
I. Setting the synchronous /asynchronous serial interface to work in

synchronous mode
Before making other configurations, perform the following configuration in the view of
the synchronous/asynchronous serial interface to make it work in synchronous mode.
Table 3-14 Setting the synchronous/ asynchronous serial interface to work in
synchronous mode
Operation
Command
Set the synchronous/ asynchronous serial

interface to work in synchronous mode
3Com Corporation
3-8
physical-mode sync
By default, a synchronous/asynchronous serial interface is working in synchronous

mode.
II. Entering the specified synchronous serial interface view

Perform the following configuration in system view to enter the specified synchronous
serial interface view.
Table 3-15 Entering the specified synchronous serial interface view
Operation
Command
Enter the view of the specified

synchronous/asynchronous serial interface (which has
been set to work in synchronous mode)
interface serial number
III. Setting link layer protocol

The link layer protocol of synchronous serial interface can be set to PPP, LAPB, X.25,
Frame Relay, HDLC, SDLC etc.
Perform the following configuration in synchronous serial interface view.
Table 3-16 Setting the link layer protocol of a synchronous serial interface
Operation
Command
Set the link layer protocol of a synchronous

serial interface
link-protocol { fr | hdlc | lapb | ppp |

sdlc | x25 }
The link layer protocol defaults to PPP.
IV. Setting digital signal coding format

The synchronous serial interface supports two digital signal coding formats, namely,
non-return-to-zero (NRZ) and non-return-to-zero inverted (NRZI).
Table 3-17 Setting the digital signal coding format on a synchronous serial interface
Operation
Command
Adopt NRZI coding format
code nrzi
Adopt NRZ coding format
undo code
By default, the synchronous serial interface adopts NRZ coding format.
V. Setting baud rate

3Com Corporation
3-9
Table 3-18 Setting baud rate of a synchronous serial interface

Operation
Command
Set baud rate of a synchronous serial

interface
baudrate baudrate
Set virtual baudrate for a DTE interface
virtualbaudrate { baudrate }
Cancel the virtual baudrate setting of the

DTE interface
undo virtualbaudrate
When two synchronous serial interfaces are connected, the baud rate on the line is
determined by the DCE side. Therefore, when a synchronous serial interface is
operating in DCE mode, the baud rate must be set. However, when it acts as DTE, it is
unnecessary to set the baud rate. The baud rate of synchronous serial interface
defaults to 64000 bps.
The virtualbaudrate command allows you to manually configure DTE-side baudrate,
but the configured value must be the same as the one set at the DCE side. To validate
the configured baudrate value for routing, execute the shut command and then the
undoshut command on the interface.
Note:
After the synchronous/asynchronous serial interface is set to work in synchronous
mode, the router will automatically change the baud rate to 64000 bps.
The virtualbaudrate command is available for configuration only when the interface is
working as DTE and in synchronous mode.
VI. Selecting operating clock

Different operating clocks are selected for the synchronous serial interfaces working as
DTE and DCE.
z
As a DCE device is required to provide clock for the remote DTE device, you must
select DCEclk as the operating clock for the synchronous serial interface working
as DCE.
Working as DTE, the synchronous serial interface must accept the clock provided
by the remote DCE. As transmitting and receiving clocks of synchronization
devices are independent, the receiving clock of a DTE device can be either the
transmitting or receiving clock of the DCE device. So is the transmitting clock.
Therefore, there are four clock options are available for a DTE device.
3Com Corporation
3-10
TxClk
DCE
DTE
RxClk
Figure 3-1 Selecting a clock for a synchronous serial interface

Table 3-19 Clock options available for a synchronous serial interface working as DTE
Clock option
Description
DTE1
TxClk = TxClk, RxClk = RxClk
DTE2
TxClk = TxClk, RxClk = TxClk
DTE3
TxClk = RxClk, RxClk = TxClk
DTE4
TxClk = RxClk, RxClk = RxClk
Note:
TxClk represents transmitting clock and RxClk receiving clock. The clock ahead of
= is the DTE clock and the one behind is the DCE clock.

Table 3-20 Selecting operating clock
Operation
Command
Set the clock for the synchronous serial interface

working as DCE.
clock dceclk
Select an operating clock for the synchronous serial

interface working as DTE.
clock { dteclk1 | dteclk2 |

dteclk3 | dteclk4 }
By default, dceclk and dteclk3 are respectively selected for the synchronous serial
interfaces at DCE side and DTE side.
VII. Setting clock inversion

In some special cases, the clock will generate half-period delay on the line, which may
cause failed interconnection of equipment at two ends or large amount of messages
discarded. In this case, the transmitting clock signal of DTE-side synchronous serial
interface can be inverted to eliminate the influence of the delay.
3Com Corporation
3-11

Table 3-21 Setting clock inversion
Operation
Command
Enable the inversion of transmitting clock signal

generated by the synchronous serial interface at
DTE side.
invert transmit-clock
Disable the inversion of transmitting clock signal

generated by the synchronous serial interface at
DTE side.
undo invert transmit-clock
By default, clock signal inversion is disabled.
Note:
This command can take effect only on some clock signals generated by some DCE
devices. In addition, clock inversion should not set for common applications.
VIII. Enabling/Disabling level detection

When determining whether a synchronous serial interface is UP or DOWN, the system
will by default detect the DSR signal, DCD signal, and the signal of the external cable
connection state. The synchronous serial interface will be regarded up only when all
these three signals are valid. Otherwise, it will be regarded down. If level detection has
been disabled on a synchronous serial interface, the system will not detect the DSR
signal when determining the state of the synchronous serial interface.
Table 3-22 Enabling/Disabling a synchronous serial interface to make level detection
Operation
Command
Enable a synchronous serial interface to make level

detection.
Detect { dcd | dsr-dtr }
Disable a synchronous serial interface to make level

detection.
undo detect { dcd |

dsr-dtr }
By default, synchronous serial interfaces are allowed to make level detection.
IX. Enabling/Disabling loopback

You may enable a synchronous serial interface to make local loop for the purpose of
testing some special functions.
3Com Corporation
3-12

Table 3-23 Enabling/Disabling a synchronous serial interface to make local loop
Operation
Command
Enable a synchronous serial interface to make

local loop
loopback
Disable a synchronous serial interface to make

local loop
undo loopback
X. Configuring MTU
The MTU setting of a synchronous serial interface can affect the assembly and
fragmentation of IP packets on the interface.
Table 3-24 Setting MTU on a synchronous serial interface
Operation
Command
Set MTU on a synchronous serial

interface
mtu size
Restore the default MTU
undo mtu
MTU defaults to 1500.
XI. Configuring the interval for sending keepalive packets

A serial interface detects the link state by sending keepalive packets to the remote end
at a specified regular interval.
Table 3-25 Configuring the interval for sending keepalive packets
Operation
Command
Configure the interval for sending keepalive

packets
timer hold seconds
Restore the interval for sending keepalive packets
undo timer hold
The keepalive packet sending interval defaults to ten seconds.
3Com Corporation
3-13
Caution:
If the link layer protocol applied to a serial interface is HDLC, the same keepalive
interval must be set on the devices at both ends of the link.
XII. Configuring line idle-mark of synchronous serial interface

Table 3-26 Configuring line idle-mark of synchronous serial interface
Operation
Command
Set the line idle-mark of synchronous serial

interface to FF.
idle-mark
Restore the default line idle-mark, that is 7E, of

synchronous serial interface
undo idle-mark
The line idle-mark of synchronous serial interfaces defaults to 7E.
3.4 AM Interface
3.4.1 AM Interface Overview
AM (Analog Modem) interface is similar to the combination of asynchronous serial
interface and analog modem in terms of the function. Most of the configuration
commands used on asynchronous serial interface and Modem can be directly used on
AM interface. AM interface can be treated as a special asynchronous serial interface
during its configuration.
Theoretically, if the peer (it is always an ISP) uses a digital Modem, the AM interface
can establish connection with V.90 Modem standard, the downstream rate can be up to
56 kbps, the upstream rate can be up to 33.6 kbps. If the peer (it is always a common
user) uses an analog Modem (including AM interface), the AM interface can establish
connection with V.34 Modem standard, both the downstream and upstream rates are
33.6 kbps. But in practice, the rate of AM interface is influenced by the line quality,
program-controlled exchange and connection standard. The rate cannot reach the
theoretical value.
3.4.2 Configuring AM Interface

I. Entering AM interface view
Perform the following task in system view.
3Com Corporation
3-14
Table 3-27 Entering the view of the specified AM interface

Operation
Command
Enter the view of the specified AM

interface
interface analogmodem number
II. Configuring AM interface

The configuration of AM interface is basically the same as that of asynchronous serial
interface and Modem.
Note: The configuration commands of AM interface are identical as those of
asynchronous serial interface and Modem except that the commands baudrate and
modem auto-answer cannot be used on AM interface.
Besides, the parameters, such as SLIP parameters, PPP parameters, DCC parameters,
IP address, firewall and standby center parameters, need to be configured when AM
interface is enabled. For detailed configuration of these parameters, refer to related
sections in this manual.
3.5 ISDN BRI Interface

3.5.1 Introduction to the ISDN BRI Interface
I. Technical background
ISDN is a technology rising in 1970s. It provides digital-only terminal-to-terminal
services and fulfills the full digitizing delivery of the services integrated voice, data,
graphics and video.
ISDN is different from the conventional PSTN network. In a conventional PSTN network,
user information in the form of analog signals is transferred over an analog user loop to
the exchange where these analog signals are converted into digital signals via A/D
processing. These digital signals traverse the digital switching and transmit network
and are converted into the analog signals again upon their reach at the destination.
ISDN makes it possible to implement digital transmission on a user loop and fulfills the
end-to-end digitization. As a standardized digital interface, ISDN BRI interface can be
used to forward the digital and analog information. The standardization efforts that
ITU-T has made in provisioning the ISDN services make the implementation of ISDN
become possible. The provisions of the recommendations I.430, Q.921, and Q.931
allow all the devices meeting the ITU-T ISDN provisions of unbarring IDDN network
access.
Following is the provision standardizing the ISDN user-network interface.
ITU-T I.411 provides the referential ISDN user-network interface configuration shown in
the following figure on the basis of function group (a set of functions required for the
3Com Corporation
3-15
users to access an ISDN network) and reference point (a concept used to differentiate
function groups)
TE1
NT2
TE2
NT1
TA
Figure 3-2 Referential ISDN user-network interface configuration

Function groups include:
z
Network Terminal 1 (NT1) implements the functionality of the first layer in the OSI
reference model, such as subscriber-line transmission, loop test, D-channel
competition.
Network Terminal 2 (NT2), also known as intelligent network terminal, implements

the functionality of the layers 1 through 3.
Category-1 Terminal Equipment (TE1), also known as ISDN standard terminal, is

user equipment compliant with the ISDN interface provisions. Digital phone-set is
such an example.
Category-2 Terminal Equipment (TE2), also known as non-ISDN standard

terminal equipment, refers to the user equipment incompliant with the ISDN
interface provisions.
Terminal Adapter (TA) implements the adaptation function so that TE2 can access
a standard ISDN interface.
Reference points include:

z
R reference point between a non-ISDN equipment and TA.
S reference point between a user terminal and NT2.
T reference point between NT1 and NT2.
U reference point between NT1 and line terminal.
II. Preparing for making configuration

Before making configuration, you should:
z
Verify the type of the interface provided by your telecom service provider, whether
it is ISDN BRI U or ISDN BRI S/T. Despite ITU-T I.411 has provided an ISDN
user-network interface reference model, there are some arguments in the position
of the user-network dividing point. For this reason, some nations adopt the U
3Com Corporation
3-16
interface while some others adopt the S/T interface depending on their needs.
Therefore, you must make sure the interface type provided by your service
provider before making a router purchase decision.
z
Request for the digital service. As ISDN can provide both digital and the integrated
services like voice service, you must request for an ISDN line allowing digital call
service so that your router can make digital communications.
Select connection type, which can be a point-to-point connection or a

point-to-multipoint connection (optional). As ISDN supports semipermanent
connection, you can adopt the ISDN leased line in the event that you adopt ISDN
only for connecting two fixed points. Otherwise, you must select a
point-to-multipoint connection.
Request for the delivery of Calling Line Identification (CLI) function (optional). With
it, you can implement calling ID filtering on your ISDN line to reject some users
from accessing the local router and hence enhance the network security.
3.5.2 Configuring an ISDN BRI Interface

Perform the following configuration in system view to enter the view of the specified
ISDN BRI interface.
Table 3-28 Entering the specified ISDN BRI interface view
Operation
Command
Enter the specified ISDN BRI interface view
interface bri number
ISDN BRI interface is used in dialup. See V 2.043.3 Operation Manual Dialup for
details.
3.6 CE1/PRI Interface

3.6.1 Introduction to CE1/PRI Interface
In 1960s, the Time Division Multiplexing (TDM) technology gains increasingly wide
application in the data communications system along with the introduction of Pulse
Code Modulation (PCM) technology. So far, there exist two TDM systems in the data
communications system. One is the ITU-T recommended E1 system that is widely
adopted in Europe and P.R. China. The other is the ANSI recommended T1 system that
is widely used in North American and Japan. (The system that Japan adopts is actually
called J1. But it is usually regarded as a T1 system due to high similarity between
them.)
A CE1/PRI interface can work in either E1 mode (also called non-channelized mode)
and CE1/PRI mode (that is, channelized mode).
3Com Corporation
3-17
A CE1/PRI interface in E1 mode equals an interface of 2 Mbps data bandwidth, on

which, no timeslots are divided. Its logic features are the same like those of a
synchronous serial interface. It supports the link layer protocols such as PPP, FR,
LAPB and X.25 and the network protocols such as IP and IPX.
When working in CE1/PRI mode, it is physically divided into 32 timeslots numbered
from 0 to 31. Among them, timeslot 0 is used for transmitting the synchronizing
information. This interface can be used as either a CE1 interface or a PRI interface.
z
When this interface is used as a CE1 interface, 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. Its logic features are the same as those of a
synchronous serial interface. It supports the link layer protocols such as PPP, FR,
LAPB and X.25, and the network protocols such as IP and IPX.
When the interface is used as a PRI interface, timeslot 16 will be used as a D

channel to transmit signaling. Therefore, rather than selecting among all the
timeslots, you are only allowed to make a ransom B channel selection among the
timeslot sets except the timeslots 0 and 16. The selected set of timeslots can be
bundled together with timeslot 16 to form a pri-set that can be used as an interface.
The logic features of this interface will be the same like those of an ISDN PRI
interface. It will support the link layer protocol PPP and network protocols such as
IP and IPX and can be configured with parameters such as DCC.
3.6.2 Configuring CE1/PRI Interface

Perform the following tasks to configure a CE1/PRI interface:
z
Enter the specified interface view
Set interface operating mode
Bundle the timeslots on the interface into channel-sets
Bundle the timeslots on the interface into a pri-set
Set a line code format
Set line clock
Set frame format
I. Entering the specified interface view

Perform the following configuration in system view to enter the specified CE1/PRI
interface view.
Table 3-29 Entering the specified CE1/PRI interface view
Operation
Command
Enter the specified CE1/PRI interface view
3Com Corporation
3-18
controller e1 number
II. Setting interface operating mode

A CE1/PRI interface can work in either E1 mode or CE1/PRI mode.
Perform the following configuration in CE1 interface view.
Table 3-30 Setting the operating mode of the CE1/PRI interface
Operation
Command
Set the CE1/PRI interface to work in E1 mode
using e1
Set the CE1/PRI interface to work in CE1/PRI mode
using ce1
Restore the default working mode of CE1/PRI interface
undo using
By default, the CE1/PRI interface is working in CE1/PRI mode.

After the CE1/PRI interface is enabled to work in E1 mode using the using e1
command, the system will automatically create a serial interface numbered serial
number:0. This interface has the same logic features of a synchronous serial interface
on which you can make other configurations. If you want to use the using ce1
command to enable CE1/PRI interface to work in CE1 mode, you need to configure
channel set to create a corresponding serial interface.
Table 3-31 Entering the synchronous serial interface view
Operation
Command
Enter the synchronous serial interface view
interface serial number:0
The major configuration tasks include:

z
Configure the operating parameters of the link layer protocol PPP, FR, LAPB, X.25
etc.
Configure IP address
Configure the operating parameters of backup center if the interface will work as
the master interface or the standby interface of the backup center
Configure address translation and packet filtering rules if a firewall should be set
up on the interface.
Refer to the related sections in this manual for details
III. Bundling the timeslots on the interface into channel-sets

Perform the following configuration in CE1/PRI interface view.
3Com Corporation
3-19
Table 3-32 Bundling the timeslots on the CE1/PRI interface into channel-sets
Operation
Command
Bundle the timeslots on the CE1/PRI interface into a

channel-set
channel-set set-number
timeslot-list range
Remove the channel-set formed by bundling the

timeslots
undo channel-set
set-number
The timeslots on a CE1/PRI interface can be bundled into up to 31 channel-sets.
Note:
A CE1/PRI interface can be bundled into channel-sets only if it has been enabled to
work in CE1/PRI mode by using the using ce1 command.
Only one timeslot bundling mode can be supported on one CE1/PRI interface during a
time period, that is, the timeslots on an interface can only be bundled into either
channel-sets or a pri-set in that period.
After some timeslots on an interface are bundled into a channel-set, the system will
automatically create a serial interface numbered serial number:set-number. This
interface is logically equivalent to a synchronous serial interface on which you can
make other configurations.
Operation
Command
Enter the synchronous serial interface

view
interface serial number:set-number

z
etc.
the master interface or the standby interface in the backup center
up on the interface
Refer to the related sections in this manual for details
3Com Corporation
3-20
IV. Bundling the timeslots on the interface into a pri-set

Table 3-34 Bundling the timeslots on the interface into a pri-set
Operation
Command
Bundle the timeslots on the CE1/PRI interface

into a pri-set
pri-set [ timeslot-list range ]
Remove the pri-set formed by bundling the

timeslots
undo pri-set
Timeslots on a CE1/PRI interface can only be bundled into one pri-set.

In the event that the timeslots on a CE1/PRI interface are bundled into a pri-set,
timeslot 16 will be used as the D channel and other timeslots (excluding timeslot 0 used
for transmitting the synchronization information) will be used as B channels. If no
timeslots are specified for bundling, all the timeslots will be bundled to form an interface
similar to an ISDN PRI interface in the form of 30B+D. If only timeslot 16 is used for
bundling, the bundling operation will fail.
Note:
A CE1/PRI interface can be bundled into channel-sets only if it has been enabled to
work in CE1/PRI mode by using the using ce1 command.
Only one timeslot bundling mode can be supported on one CE1/PRI interface during a
After the timeslots on an interface are bundled into a pri-set, the system will
automatically create a serial interface numbered serial number:15. This interface is
logically equivalent to an ISDN PRI interface, and you can further configure it.
Table 3-35 Entering the ISDN interface view
Operation
Command
Enter the ISDN PRI interface view(CE1/PRI

interface)

z
Configure DCC operating parameters

3Com Corporation
3-21
Encapsulate the link layer protocol PPP and configure its authentication
parameters, etc
up on the interface
Refer to the related sections in this manual for details.
V. Setting line code format

CE1/PRI interfaces support two types of line code formats, namely, ami and hdb3.
Table 3-36 Setting the line code format on the CE1/PRI interface
Operation
Command
Set the line code format on the CE1/PRI interface
code { ami | hdb3 }
Restore the default line code format on the CE1/PRI

interface
undo code
The line code format on CE1/PRI interfaces defaults to hdb3.
VI. Setting line clock

When a CE1/PRI interface is working as DCE, chose the internal clock for it, that is,
master clock mode. When it is working as DTE, chose the line clock, that is, slave
clock mode for it.
Directly connected CE1/PRI interfaces on two routers must respectively work in line
clock (that is, slave clock) mode and internal clock (that is, master) mode. If the
CE1/PRI interface on a router is connected to a switch, the switch will be the DCE
device responsible for providing the clock and the CE1/PRI interface in this case must
work in the line clock (slave clock) mode.
Table 3-37 Setting the line clock on the CE1/PRI interface
Operation
Command
Set the line clock on the CE1/PRI interface
clock { master | slave }
Restore the default line clock on the CE1/PRI

interface
undo clock
The line clock on a CE1/PRI interface defaults to the slave clock.

3Com Corporation
3-22
VII. Setting the frame format on the interface

A CE1/PRI interface working in CE1/PRI mode supports both crc4 and no-crc4 frame
formats. Among them, crc4 supports the 4-bit Cyclic Redundancy Check (CRC) on
physical frames whereas no-crc4 does not.
Table 3-38 Setting frame format on the CE1/PRI interface
Operation
Command
Set frame format on the CE1/PRI interface
frame-format { crc4 | no-crc4 }
Restore the default frame format on a CE1/PRI

interface
undo frame-format
The frame format on a CE1/PRI interface defaults to no-crc4.
VIII. Enabling/Disabling Local Loopback / Remote Loopback

You may enable a CE1/PRI interface to make local loopback and remote echo for the
purpose of testing some special functions.
Table 3-39 Enabling/Disabling local loopback / remote echo on a CE1/PRI interface
Operation
Command
Enable the CE1/PRI interface to make local loop
Loopback local
Disable the CE1/PRI interface to make local loop
undo loopback
Enable remote loop on a CE1/PRI interface
Loopback remote
Disable remote loop on a CE1/PRI interface
undo loopback
By default, CE1/PRI interfaces are disabled to make local loopback / remote loopback.
3.6.3 Displaying and Debugging CE1/PRI Interface Information

Perform the following configuration in any view to display the state of CE1/PRI
interfaces and the related information.
Table 3-40 Displaying and debugging the CE1/PRI interface information
Operation
Command
Display the operating state of CE1/PRI interface
display controller e1
interface-number
Display the operating state of channel-set or pri-set
display interface serial

number:set-number
3Com Corporation
3-23
Generally, a CE1/PRI interface is applied to the leased line and dial-up services. For
the sake of simplicity, this part will not cover its typical configuration and fault diagnosis,
but you can find them in the relevant sections in Parts V 2.043.3 Operation Manual Link Layer Protocol and V 2.043.3 Operation Manual Dial-up.
3.7 CT1/PRI Interface

3.7.1 Introduction to CT1/PRI Interface
In 1960s, the TDM technology gains increasingly wide application in the data
communications system along with the introduction of Pulse Code Modulation (PCM)
technology. So far, there exist two TDM systems in the data communications system.
One is the ITU-T recommended E1 system that is widely adopted in Europe and P.R.
China. The other is the ANSI recommended T1 system that is widely used in North
American and Japan. (The system that Japan adopts is actually called J1. But it is
usually regarded as a T1 system due to high similarity between them.)
T1 line comprises 24 multiplexed channels. In other words, a T1 PRI frame DS1
contains 24 8-bit DS0 (64 kbps) timeslots and a framing bit, or a total number of 193 bits
(24 x 8+1=193bits). As 8000 frames can be sent per second, the transmission speed of
DS1 is 193 X 8K = 1.544 Mbps.
CT1/PRI interface must work in channelized mode. It can be used in the following two
ways:
z
When it is working as a CT1 interface, all the timeslots from 1 to 24 can be

randomly divided into a number of groups and each group can be bundled into a
channel-set. Upon the bundling of each timeslot group, the system automatically
generates an interface logically equal to a synchronous serial interface that
supports the link layer protocols such as PPP, frame relay, LAPB and X.25, and
the network protocols such as IP and IPX.
When it is working as a PRI interface, timeslot 24 will be used as a D channel for

signaling transmission. Therefore, only a group of timeslots except the timeslot 24
can be chosen as the B channel. This timeslot group can be bundled together with
timeslot 24 to form a pri-set. This pri-set will work as an interface that has the same
logic features of an ISDN PRI interface and supports PPP and network protocols
such as IP and IPX and the configuration of DCC parameters.
3.7.2 Configuring CT1/PRI Interface

Perform the following tasks to configure a CT1/PRI interface:
z
Enter the specified interface view
Bundle the timeslots on the interface into channel-sets
Bundle the timeslots on the interface into a pri-set

3Com Corporation
3-24
Set length/attenuation of the transmission cable
Set a line code format
Set line clock
Set frame format
I. Entering the specified interface view

Perform the following configuration in system view to enter the specified CT1/PRI
interface view.
Table 3-41 Entering the specified CT1/PRI interface view
Operation
Command
Enter the specified CT1/PRI interface view
controller t1 number
II. Bundling the timeslots on the interface into channel-sets

Perform the following configuration in CT1/PRI interface view.
Table 3-42 Bundling the timeslots on the interface into channel-sets
Operation
Command
Bundle the timeslots on the CT1/PRI interface

into a channel-set
channel-set set-number
timeslot-list range [ speed
{ 56k | 64k } ]
Remove the channel-set formed by bundling the

timeslots
undo channel-set set-number
The timeslots on a CT1/PRI interface can be bundled into up to 24 channel-sets.
Note:
Only one timeslot bundling mode can be supported on a CT1/PRI interface during a
After some timeslots on a CT1/PRI interface are bundled into a channel-set, the system
will automatically create a serial interface numbered serial number:set-number. This
interface has the same logic features of synchronous serial interfaces, and can be
further configured as a synchronous serial interface.
3Com Corporation
3-25

Operation
Command
Enter the synchronous serial interface view
interface serial number:set-number

z
etc.
up on the interface
III. Bundling the timeslots on the interface into a pri-set

Perform the following configuration in CT1/PRI Interface view.
Table 3-44 Bundling the timeslots on the interface into a pri-set
Operation
Command
Bundle the timeslots on the CT1/PRI interface

into a pri-set
pri-set [ timeslot-list range ]
Remove the pri-set formed by bundling the

timeslots
undo pri-set
Timeslots on the CT1/PRI interface can only be bundled into one pri-set.
In the event that the timeslots on a CT1/PRI interface are bundled into a pri-set, timeslot
24 will be used as the D channel and other timeslots will be used as B channels. If no
timeslots are specified for bundling, all the timeslots will be bundled to form an interface
similar to an ISDN PRI interface in the form of 23B+D. If only timeslot 24 is used for
bundling, the bundling operation will fail.
Note:
Only one timeslot bundling mode can be supported on a CT1/PRI interface during a
3Com Corporation
3-26
After the timeslots on a CT1/PRI interface are bundled into a pri-set, the system will
automatically create a serial interface numbered serial number:23. This interface is
logically equivalent to an ISDN PRI interface on which you can make other
configurations.
Table 3-45 Entering the ISDN interface view
Operation
Command
Enter the ISDN PRI interface view(CTI/PRI

interface)

z
Configure DCC operating parameters
Encapsulate the link layer protocol PPP and configure its authentication
parameters, etc
the master interface or the standby interface in the backup center
up on the interface
IV. Setting length/attenuation of the transmission cable

To guarantee the signal quality at the receiving end, you should set proper signal
attenuation and waveform on the CT1/PRI interface depending on the length of the
transmission cable to which the interface is connected.
Table 3-46 Setting length/attenuation of the transmission cable on the CT1/PRI
interface
Operation
Command
Set the CT1/PRI interface to use the

long-distance transmission cable
cable long { 0db | -7.5db | -15db |

-22.5db }
Set the CT1/PRI interface to use the

short-distance transmission cable
cable short { 133ft | 266ft | 399ft |

533ft | 655ft }
Restore the default setting of the

transmission cable used by the CT1/PRI
interface
undo cable
3Com Corporation
3-27
By default, the attenuation of transmission cable that the CT1/PRI interface matches is
long 0db.
V. Setting line code format

CT1/PRI interfaces support two types of line code formats, namely, ami and b8zs.
Table 3-47 Setting the line code format on the CT1/PRI interface
Operation
Command
Set the line code format on the CT1/PRI interface
code { ami | b8zs }
Restore the default line code format on the CE1/PRI

interface
undo code
The line code format on CT1/PRI interfaces defaults to b8zs.
VI. Setting line clock

When a CT1/PRI interface is working as DCE, chose the internal clock for it, that is,
master clock mode. When it is working as DTE, chose the line clock, that is, slave
clock mode for it.
Directly connected CT1/PRI interfaces on two routers must respectively work in line
clock (that is, slave clock) mode and internal clock (that is, master) mode. If the
CT1/PRI interface on a router is connected to a switch, the switch will be the DCE
device responsible for providing the clock and the CE1/PRI interface in this case must
work in the line clock (slave clock) mode.
Table 3-48 Setting the line clock on the CT1/PRI interface
Operation
Command
Set the line clock on the CT1/PRI interface
Restore the default line clock on the CT1/PRI

interface
undo clock
The clock on a CT1/PRI interface defaults to the slave clock.
VII. Setting the frame format on the interface

CT1/PRI interfaces support two frame formats, that is, Super Frame (SF) and Extended
Super Frame (ESF). In SF format, multiple frames can share the same framing
information and signaling information, so that there are more significant bits can be
used for transmitting user data. In practice, a system should be tested often. The
3Com Corporation
3-28
application of ESF makes it possible to operate the normal services while testing the
system.
Perform the following configuration in CT1 interface view.
Table 3-49 Setting the CT1/PRI frame format on the CT1/PRI interface
Operation
Command
Set frame format on the CT1/PRI interface
frame-format { sf | esf }
Restore the default frame format on the CT1/PRI

undo frame-format
interface
The frame format on a CT1/PRI interface defaults to ESF.
VIII. Enabling/Disabling loopback

You may enable a CT1/PRI interface to make local loop or remote loop for the purpose
of testing some special functions.
Perform the following configuration in CT1 Interface view.
Table 3-50 Enabling/Disabling the CT1/PRI interface to perform local loop/remote loop
Operation
Command
Enable the CT1/PRI interface to make local

loop/remote loop
loopback { remote | local }
Disable the CT1/PRI interface to perform loopback
undo loopback
By default, CT1/PRI interfaces are disabled to perform loopback.
3.7.3 Displaying and Debugging CT1/PRI Interface Information

Perform the following configuration in any view to display the state of CT1/PRI
interfaces and the related information.
Table 3-51 Displaying and debugging the CT1/PRI interface information
Operation
Command
Display the operating state of CT1/PRI

interface
display controller t1
interface-number
Display the operating state of channel-set

or pri-set

number:set-number
Generally, a CE1/PRI interface is applied to the leased line and dial-up services. For
the sake of simplicity, this part will not cover its typical configuration and fault diagnosis,
3Com Corporation
3-29
but you can find them in the relevant sections in Parts V 2.043.3 Operation Manual Link Layer Protocol and V 2.043.3 Operation Manual Dial-up.
3.8 E1-F Interface

3.8.1 Introduction to E1-F Interfaces
E1-F interface is fractional E1 interface, and it is respectively simplified CE1/PRI
interface. If there is no need to use multiple channel sets or if ISDN PRI is not
necessary in an E1 application, it is too much to use CE1/PRI interface. At this time,
E1-F interface is more than enough for meeting the simple E1 access requirements.
Compared with CE1/PRI interface, E1-F interface is a nice low-cost choice for E1
access.
Compared with CE1/PRI interfaces, E1-F interface has the following features:
z
When working in framed mode, E1-F interface can only bind time slots into one
channel set, but CE1/PRI interface can group timeslots randomly and bind them
into multiple channel sets.
E1-F interface does not support PRI operating mode.
E1-F interface can work in both framed and unframed modes.

When it works in unframed mode, it is a non-timeslot interface of 2048kbps data
bandwidth. In this case, it is logically equivalent to a synchronous serial interface,
supporting the data link layer protocols PPP, HDLC, Frame Relay, LAPB and X.25, as
well as the network protocols IP and IPX.
When it works in framed mode, however, it is physically divided into 32 time slots
numbered in the range of 0 to 31. In these time slots, except for time slot 0 used for
synchronization information transmission, all the other time slots can be randomly
bound into one channel set. E1-F interface has the rate of nx64kbps, owns logical
features of synchronous serial interface, and supports the data link layer protocols PPP,
Frame Relay, LAPB and X.25 as well as the network protocols IP and IPX.
3.8.2 Configuring E1-F Interface

E1-F interface configuration includes:
z
Enter the view of a specified interface
Set interface operating mode
Set interface rate after binding operation
Set line code format
Set line clock
Set interface frame format
Enable or disable local/remote loopback
3Com Corporation
3-30
I. Entering the view of a Specified Interface

Unlike CE1/PRI interface, E1-F interface has no Controller view. The system identify an
E1-F interface as a synchronous serial interface, so entering the view of E1-F interface
is equivalent to entering the view of the corresponding serial interface.
Table 3-52 Entering the view of an E1-F interface
Operation
Command
Enter the view of an E1-F interface
interface serial serial-number
E1-F interface is sequenced based on the same numbering and are numbered together
with the synchronous serial interfaces.
II. Setting Interface Operating Mode

E1-F interface can work in both unframed and framed modes.
Perform the following configuration in E1-F interface view.
Table 3-53 Setting Operating mode for an E1-F interface
Operation
Command
Set an E1-F interface to work in unframed mode
fe1 unframed
Set the E1-F interface to work in framed mode
undo fe1 unframed
By default, E1-F interfaces work in framed mode.
III. Setting Interface Rate after Binding Operation

When E1-F interface works in framed mode, time slot binding on the interfaces can be
made according to users demands.
Table 3-54 Setting interface rate after binding operation
Operation
Command
Bind time slots on an E1-F interface
fe1 timeslot-list { all |

range }
Restore the default setting for time slot binding on

the interface
undo fe1 timeslots
By default, binding operation will be done on all the time slots on E1-F interface.
3Com Corporation
3-31
Note:
Time slot 0 on E1-F interface is used for synchronization information transmission.
Therefore, in practice, only time slots 1 through 31 are bound when performing binding
operation on all the time slots on an E1-F interface.
Unlike CE1/PRI interface, only one channel set can be bound on an E1-F interface, and
this channel set is associated with the current synchronous serial interface. On a
CE1/PRI interface, however, multiple channel sets can be bound, and the system will
automatically generate a synchronous serial interface accordingly whenever a channel
set is formed.
IV. Setting Line Code Format

E1-F interfaces support line code formats AMI (Alternate Mark Inversion) and HDB3
(High Density Bipolar 3).
Table 3-55 Setting line code format for E1-F interfaces
Operation
Command
Set line code format for an E1-F interface
fe1 code { ami | hdb3 }
Restore the default line code format for an E1-F

interface
undo fe1 code
The line code format for an E1-F interface defaults to hdb3.
V. Setting Line Clock

If E1-F interface is used as DCE, the slave clock should be selected. If it is used as
DTE, the master clock should be selected.
If the E1-F interfaces of two routers are directly connected, they must respectively work
in slave and master clock modes. If the E1-F interface of the router is connected to an
exchange, however, the exchange is working as DCE and provides clock, so the
interface of the router should work in master clock mode.
Table 3-56 Setting line clock for an E1-F interface
Operation
Command
Set line clock for an E1-F interface
fe1 clock { master | slave }
Restore the line clock of the E1-F interface

to the default setting
undo fe1 clock
3Com Corporation
3-32
By default, the clock of E1-F interface is slave clock.
VI. Setting Interface Frame Format

When an E1-F interface is working in framed mode, it supports both CRC4 (4-bit Cyclic
Redundant Check) and no-CRC4 frame formats.
Table 3-57 Setting frame format for an E1-F interface
Operation
Command
Set frame format for an E1-F interface
fe1 frame-format { crc4 |

no-crc4 }
Restore the default frame format of the E1-F

interface
undo fe1 frame-format
By default, the frame format of E1-F interface is no-CRC4.
VII. Enabling or Disabling Local Loopback/Remote Loopback

An interface should be place in local loopback or remote loopback for some special
functionality tests.
Table 3-58 Enabling/Disabling local/remote loopback on an E1-F interface
Operation
Command
Enable local/remote loopback on an

interface
fe1 loopback { local | remote }
Disable local/remote loopback on an

interface
undo fe1 loopback [ local | remote ]
By default, no E1-F interface is placed in local or remote loopback.
Note:
On an interface, using this command but with different arguments can respectively
enable local loopback and remote loopback, but these two functions cannot be enabled
at the same time.
3Com Corporation
3-33
3.8.3 Displaying and Debugging E1-F Interface

Perform the display command in any view to display the state of E1-F interface and
other related information.
Table 3-59 Displaying and debugging E1-F interface
Operation
Command
Display configuration and state of E1-F

interface
display fe1 [ serial serial-number ]
Display the operating state of E1-F

interface
display serial serial-number
3.9 T1-F Interface

3.9.1 Introduction to T1-F Interface
T1-F interface is fractional T1 interface, and it is respectively simplified CT1/PRI
interface. If there is no need to use multiple channel sets or if ISDN PRI is not
necessary in an T1 application, it is too much to use CT1/PRI interface. At this time,
T1-F interface is more than enough for meeting the simple T1 access requirements.
Compared with CT1/PRI interface, T1-F interfaces is a nice low-cost choice for T1
access.
Compared with CT1/PRI interface, T1-F interface has the following features:
z
When working in framed mode, T1-F interface can only bind time slots into one
channel set, but CT1/PRI interface can group timeslots randomly and bind them
into multiple channel sets.
T1-F interface does not support PRI operating mode.
T1 line comprises 24 multiplexed channels. That is, a T1 primary group frame DS1
(Digital Signal Level-1) comprises 24 DS0 (64kbps) time slots, each has 8 bits and 1
framing bit for synchronization, and thus each primary group frame has 193 bits (24 X
8+1). As DS1 can transmit 8000 frames per second, its transmission speed is 193 X 8k
= 1544kbps.
T1-F interface can only work in framed mode, and it can randomly bind all time slots
(time slots 1 through 24) into one channel set. T1-F interface has the rate of nx64kbps
or nx56kbps, owns logical features of synchronous serial interface, and supports the
data link layer protocols PPP, HDLC, Frame Relay, LAPB and X.25 as well as the
network protocols IP and IPX.
3.9.2 Configuring T1-F Interface

T1-F interface configuration includes:
3Com Corporation
3-34
Enter the view of a specified interface
Set interface rate after binding operation
Set length/attenuation of transmission line
Set line code format
Set line clock
Set interface frame format
Enable or disable local/remote loopback
I. Entering the view of a Specified Interface

Unlike CT1/PRI interface, T1-F interface has no Controller view. The system identify a
T1-F interface as a synchronous serial interface, so entering the view of T1-F interface
is equivalent to entering the view of the corresponding serial interface.
Table 3-60 Entering the view of an T1-F interface
Operation
Command
Enter the view of a T1-F interface
interface serial serial-number
T1-F interface is sequenced based on the same numbering and are numbered together
with the synchronous serial interfaces.
II. Setting Interface Rate after Binding Operation

When T1-F interface works in framed mode, time slot binding on the interfaces can be
made according to users demands.
Perform the following configuration in T1-F interface view.
Table 3-61 Setting interface rate after binding operation
Operation
Command
Bind time slots on a T1-F interface
ft1 timeslot-list { all | range } [ speed

{ 56 | 64 } ]
Restore the default setting for time slot

binding on the interface
undo ft1 timeslots
By default, binding operation will be done on all the time slots on T1-F interface.
Unlike CT1/PRI interface, only one channel set can be bound on a T1/F interface, and
this channel set is associated with the current synchronous serial interface. On a
CT1/PRI interface, however, multiple channel sets can be bound, and the system will
automatically generate a synchronous serial interface accordingly whenever a channel
set is formed.
3Com Corporation
3-35
III. Setting Length/Attenuation for Transmission Line

If a T1-F interface is connected to the transmission lines of various lengths, you should
match attenuation or waveform of the interface signals with the transmission lines.
Table 3-62 Setting length/attenuation of transmission line on a T1-F interface
Operation
Command
Set the T1-F interface to use long-distance

ft1 cable long decibel
transmission line
Set the T1-F interface to use short-distance
ft1 cable short length
transmission line
Restore the default setting of the
transmission line for the T1-F interface
undo ft1 cable
By default, attenuation matched a T1-F interface is long 0db.
IV. Setting Line Code Format

T1-F interface supports line code formats AMI (Alternate Mark Inversion) and B8ZS
(Bipolar 8-Zero Substitution).
Table 3-63 Setting line code format for T1-F interface
Operation
Command
Set line code format for a T1-F interface
ft1 code { ami | b8zs }
Restore the default line code format for a T1-F

interface
undo ft1 code
The line code format for an T1-F interface defaults to b8zs.
V. Setting Line Clock

If T1-F interface is used as DCE, the slave clock should be selected. If it is used as
DTE, the master clock should be selected.
If the T1-F interfaces of two routers are directly connected, they must respectively work
in slave and master clock modes. If the T1-F interface of the router is connected to an
exchange, however, the exchange is working as DCE and provides clock, so the
interface of the router should work in master clock mode.
3Com Corporation
3-36
Table 3-64 Setting line clock for a T1-F interface

Operation
Command
Set line clock for a T1-F interface
ft1 clock { master | slave }
Restore the line clock of the T1-F interface

to the default setting
undo ft1 clock
By default, the line clock of T1-F interface is slave clock.
VI. Setting Interface Frame Format

T1-F interfaces support Super Frame (SF) and Extended Supper Frame (ESF). In SF,
multiple frames can share the same frame synchronization and signaling information,
so that more significant bits can be used for transmitting user data. In practice, the
system test is often required. The application of ESF technology can ensure normal
service when the system test is being carried out.
Table 3-65 Setting frame format of T1-F interface
Operation
Command
Set frame format for a T1-F interface
ft1 frame-format { sf | esf }
Restore the default frame format of T1-F interface
undo ft1 frame-format
By default, the frame format of T1-F interface is ESF.
VII. Enabling or Disabling Local Loopback/Remote Loopback

An interface should be place in local loopback or remote loopback for some special
functionality tests.
Table 3-66 Enabling/Disabling local/remote loopback on a T1-F interface
Operation
Command
Enable local/remote loopback on an

interface
ft1 loopback { local | remote }
Disable local/remote loopback on an

interface
undo ft1 loopback [ local | remote ]
By default, no T1-F interface is placed in local or remote loopback.
3Com Corporation
3-37
Note:
On an interface, using this command but with different arguments can respectively
enable local loopback and remote loopback, but these two functions cannot be enabled
at the same time.
3.9.3 Displaying and Debugging T1-F Interface

Perform the display command in any view to display the state of T1-F interface and
other related information.
Table 3-67 Displaying and debugging T1-F interface
Operation
Command
Display configuration and state of

T1-F interface
display ft1 [ serial serial-number ]
Display the operating state of T1-F

interface
display serial serial-number
3.10 CE3 Interface

3.10.1 Introduction to CE3 Interface
Like E1, E3 also belongs to the digital carrier system of ITU-T and is used in most areas
outside the North America. It transmits data at 34.368 Mbps and adopts HDB3 as the
line code format.
A CE3 interface can work in either E3 or CE3 mode.
z
A CE3 interface in E3 mode equals an interface of 34.368 Mbps data bandwidth,

on which, no timeslots are divided.
A CE3 interface in CE3 mode can demultiplex 16 channels of E1 signals in

compliance with the ITU-T G.751 and G.742 provisions. Each E1line can be
divided into 32 timeslots numbered from 0 to 31, of which timeslots 1 through 31
can be freely bundled into Nx64 Kbps logical channels. (Timeslot 0 for framing
signal transmission must not participate in the bundling operation.) Therefore,
CE3 can be channelized into E1 lines or 64Kbps lines.
CE3 interfaces support the link layer protocols PPP, HDLC, FR, LAPB, and X.25, as
well as the network protocols IP, IPX, etc.
3.10.2 Configuring a CE3 Interface

Perform the following tasks to configure a CE3 interface:
3Com Corporation
3-38
Enter the specified CE3 interface view
Set clock mode on the CE3 interface
Set the national bit on the CE3 interface
Set loopback mode on the CE3 interface
Set E1 frame format
Set operating mode of CE3 interface
Depending on the networking requirements, you probably also need to configure the
CE3 interface with the parameters in PPP, IP address, and so on. For details, refer to
the relevant sections in this manual.
I. Entering the specified CE3 interface view

You can enter a CE3 interface view by executing the controller command.
Perform the following configuration in system view to enter the CE3 interface view.
Table 3-68 Entering the specified CE3 interface view
Operation
Command
Enter the specified CE3 interface view
controller e3 number
II. Setting clock mode on the CE3 interface

Table 3-69 Setting clock mode on the CE3 interface
Operation
Command
Restore the default clock mode
undo clock
By default, the CE3 interface adopts the line clock (that is, slave clock).
You can also set clock mode on the E1 lines on a CE3 interface.
Table 3-70 Setting clock mode on an E1 line
Operation
Command
Set clock mode on an E1 Channel
e1 line-number set clock { master |

slave }
undo e1 line-number set clock
The clock on an E1 channel defaults to the line clock (that is, slave clock).
3Com Corporation
3-39
III. Setting national bit on the CE3 interface

Table 3-71 Setting a national bit on the CE3 interface
Operation
Command
Set national bit on the CE3 interface
national-bit { 0 | 1 }
Restore the default national bit on the

CE3 interface
undo national-bit
The national bit on a CE3 interface defaults to 1.
IV. Setting loopback mode on the CE3 interface

Table 3-72 Setting loopback mode on the CE3 interface
Operation
Command
Set the loopback mode on the CE3

interface
loopback { local | payload | remote }
Disable the CE3 interface to perform

loopback
undo loopback
By default, loopback is disabled.

Each E1 line of CE3 interface can enable or disable loopback function independently.
Table 3-73 Setting loopback mode on an E1 line
Operation
Command
Enable an E1 line to perform loopback
e1 line-number set loopback { local |

remote }
Disable the E1 line to perform loopback
undo e1 line-number set loopback
V. Setting E1 frame format

When an E1 channel is working in the framing format, you can set the frame format for
it. Perform the following configuration in CE3 interface view.
3Com Corporation
3-40
Table 3-74 Setting E1 frame format

Operation
Command
Set frame format on an E1 line
e1 line-number set frame-format { crc4 |

no-crc4 }
Restore the default frame format

of the E1 line
undo e1 line-number set frame-format
The frame format on E1 lines defaults to no-crc4.
VI. Setting operating mode of the CE3 interface

Setting operating mode of a CE3 interface includes the tasks of setting it to work in
channelized or unchannelized mode and setting its E1 lines to work in E1 or CE1 mode.
Table 3-75 Setting operating mode of the CE3 interface
Operation
Command
Set operating mode of the CE3 interface
using { e3 | ce3 }
Restore the default operating mode
undo using
By default, CE3 interfaces work in channelized mode.

When an E3 interface is working in unchannelized mode, the system automatically
creates a serial interface numbered serial number / 0:0 for it. This interface operates at
34.368 Mbps and has the same logic features of a synchronous serial interface on
which you can make other configurations.
When the E3 interface is working in channelized mode, you can set the operating mode
of its E1 channels.
Table 3-76 Setting operating mode of an E1 line
Operation
Command
Set an E1 line on the CE3 interface to

work in E1 mode (that is, unframed mode)
e1 line-number unframed
Set an E1 line on the CE3 interface to

work in CE1 mode (that is, framed mode)
undo e1 line-number unframed
Bundle the timeslots on the CE1 line
e1 line-number channel-set
set-number timeslot-list range
Cancel the bundling of the timeslots on the

CE1 line
undo e1 line-number channel-set

set-number
3Com Corporation
3-41
By default, E1 lines work in CE1 mode.

When an E1 line is working in unframed (E1) mode, the system automatically creates a
serial interface numbered serial number/line-number:0 for it. This interface operates at
2048 kbps and has the same logic features of a synchronous serial interface on which
you can make other configurations.
When an E1 line operates at framed (CE1) mode, you can bundle the timeslots on it.
The system will automatically create a serial interface numbered serial number/
line-number:set-number. This interface can operate at N x 64 Kbps and has the same
logic features of a synchronous serial interface on which you make other
configurations.
3.10.3 Displaying and Debugging CE3 Interface Information

Displaying and debugging the CE3 interface information includes the tasks of shutting
down the interface and displaying the interface information. As shutting down an
interface will make the interface stop working, you are recommended to use the
shutdown command only when necessary.
Table 3-77 Enabling and shut down the CE3 interface
Operation
Command
Shut down the CE3 interface
shutdown
Enable the CE3 interface
undo shutdown
Shut down an E1 line
e1 line-number shutdown
Enable the E1 line
undo e1 line-number shutdown
Disabling/Enabling a CE3 interface will also enable/disable the E1 lines demultiplexed

from the CE3 interface, the serial interfaces formed by the E1 lines, and the serial
interfaces that the E1 lines form by means of timeslot bundling.
Disabling/Enabling an E1 line will also disable/enable the serial interface formed by it
and the serial interface that it forms by means of timeslot bundling.
To disable/enable only a serial interface formed by E3 or E1 line, or by timeslot bundling
on an E1 line, you can perform the shutdown/undo shutdown command in the view of
the corresponding serial interface.
3Com Corporation
3-42
Table 3-78 Displaying and debug the CE3 interface information

Operation
Command
Display the state information of the CE3

interface
display controller e3 interface-number
Display the configuration and state

information of the serial interface formed
by the CE3 interface

interface-number
3.11 CT3 Interface

3.11.1 Introduction to CT3 Interface
Both T3 and T1 belong to the T-carrier system promoted by ANSI. T3 uses the digital
signal level DS-3 and operates at 44.736 Mbps.
CT3 interfaces support two operating modes, that is, T3 (unchannelized) mode and
CT3 (channelized) mode.
z
A CT3 interface in T3 mode equals a synchronous serial interface of 44736 kbps

data bandwidth, on which, no timeslots are divided.
A CE3 interface in CT3 mode can demultiplex 28 channels of T1 signals. Each T1

line can be divided into 24 timeslots numbered from 1 to 24. therefore, a CT3
interface can be channelized into up to 672 (got by multiplying 28 by 24) lines in
theory. In practice, however, only up to 300 lines are allowed. Different from E1,
each line on a T1 interface can operate at either 64 Kbps or 56 Kbps. Therefore, a
CT3 interface in CT3 mode can be randomly bundled into M x 1.536 Mbps (M is in
the range of 1 to 28) or N x 56 Kbps or N x 64 Kbps (N is in the range of 1 to 300)
logical lines.
The serial interface formed by a CT3 interface can support the link layer protocols PPP,
MP, HDLC, FR, LAPB, and X.25, as well as the network protocols IP, IPX, etc.
3.11.2 Configuring a CT3 Interface

Perform the following tasks to configure a CT3 interface:
z
Enter the specified CT3 interface view
Set cable length of the CT3 interface
Set loopback mode on the CT3 interface
Set frame format on the CT3 interface
Set operating mode of the CT3 interface
Set CRC on the serial interface
3Com Corporation
3-43
Depending on the networking requirements, you probably also need to configure the
CT3 interface with link layer protocol, IP address , and so on. For details, refer to the
relevant sections in this manual.
I. Entering the specified CT3 interface view

You can enter a CT3 interface view by executing the controller command.
Table 3-79 Entering the specified CT3 interface view
Operation
Command
Enter the specified CT3 interface view
controller t3 interface-number
II. Setting clock mode of the CT3 interface

CT3 interfaces support both the line clock mode and internal clock mode.
Table 3-80 Setting clock mode on the CT3 interface
Operation
Command
Set clock mode on the CT3 interface
undo clock
By default, CT3 interfaces use line clock as the clock source.

You can also set clock mode on the E1 lines on a CE3 interface.
Table 3-81 Setting clock mode on a T1 line
Operation
Command
Set clock mode on a T1 line
t1 line-number set clock { master |

slave }
undo t1 line-number set clock
The clock used by a T1 line defaults to the line clock (that is, slave clock).
III. Setting length of the cable connecting the CT3 interface

Use the cable command to set the distance between the router and the cable
distribution rack.
3Com Corporation
3-44
Table 3-82 Setting length of the cable connecting the CT3 interface
Operation
Command
Set cable length for the CT3 interface
cable feet
Restore the default cable length
undo cable
The cable length defaults to 49 feet.
IV. Setting loopback mode on the CT3 interface

CT3 interfaces support the loopback test on the DS-3 rate data. Please do not enable
loopback when the interface is in normal use.
Table 3-83 Configuring loopback mode on the CT3 interface
Operation
Command
Set loopback mode on the CT3 interface loopback { local | payload | remote }
Disable loopback on the CT3 interface
undo loopback
The payload loopback and the remote loopback on a CT3 interface is different in the
sense that the former requires the processing of frame overhead and the latter does not
require the frame processing..
By default, loopback is disabled on CT3 interfaces.
Each T1 line of CT3 interface can enable or disable loopback function independently.
Table 3-84 Setting loopback mode on a T1 line
Operation
Command
Set loopback mode on a T1 line
t1 line-number set loopback{ local |

remote }
Disable the T1 line to perform loopback
undo t1 line-number set loopback
V. Setting frame format on the CT3 interface

Table 3-85 Configuring a frame format on the CT3 interface
Operation
Command
Configure a frame format on the CT3 interface

3Com Corporation
3-45
frame-format { c-bit | m23 }
Operation
Command
Restore the default setting on the CT3 interface undo frame-format
By default, the CT3 interface uses the C-bit frame format.

When the CT3 interface is working in channelized mode, the frame format of T1 line
can be set.
Table 3-86 Configuring a frame format for a T1 line
Operation
Command
Configure a frame format for a T1 line t1 line-number set frame-format { esf | sf }

undo t1 line-number set frame-format
By default, T1 lines use ESF.
VI. Setting operating mode of the CT3 interface

Table 3-87 Setting operating mode of the CT3 interface
Operation
Command
Set operating mode of the CT3 interface
using { t3 | ct3 }
Restore the default setting
undo using
By default, the CT3 interface works in channelized mode.

When the CT3 interface is working in unchannelized mode, the system automatically
creates a serial interface numbered serial number / 0:0 for it. This interface operates at
44.736 Mbps and has the same logic features of a synchronous serial interface on
When the CT3 interface is working in channelized mode, you can demultiplex it into 28
T1 lines at 1.544 Mbps and set their operating modes separately.
Table 3-88 Setting operating mode of a T1 line
Operation
Command
Set a T1 line on the CT3 interface to work

in T1 (unframed) mode.
t1 line-number unframed
Set a T1 line on the CT3 interface to work

in CT1 (framed) mode.
undo t1 line-number unframed
3Com Corporation
3-46
Operation
Command
Bundle the timeslots on the CT1 line
t1 line-number channel-set
set-number timeslot-list range
[ speed { 56k | 64k } ]
Cancel the bundling of the timeslots on the

CT1 line
undo t1 line-number channel-set

set-number
By default, T1 lines work in CT1 mode.

When a T1 line is working in unframed (T1) mode, the system automatically creates a
serial interface numbered serial number/ line-number:0 for it. This interface operates
at 1544 Kbps and has the same logic features of a synchronous serial interface on
When a T1 line operates at framed (CT1) mode, you can bundle its timeslots. The
system can automatically create a serial interface numbered serial number/
line-number:set-number in this case. This interface operates at N x 64 Kbps (or N x 56
Kbps) and has the same logic features of a synchronous serial interface on which you
can make other configurations.
VII. Setting CRC on a serial interface

For a serial interface formed by T3 or T1 line or by bundling the timeslots on a T1 line,
its CRC can be configured in the corresponding serial interface view.
Table 3-89 Setting CRC on a serial interface
Operation
Command
Configure CRC for the serial interface

formed by the CT3 interface
crc { 16 | 32 | no-crc}
Restore the default CRC mode
undo crc
By default, the serial interface uses 16-bit CRC.
3.11.3 Displaying and Debugging the CT3 Interface Information

Displaying and debugging the CT3 interface information includes the tasks of shutting
down the interface and displaying the interface information. As shutting down an
interface will make the interface stop working, you are recommended to use the
shutdown command only when necessary.
3Com Corporation
3-47
Table 3-90 Enabling and shut down the CT3 interface

Operation
Command
Shut down the CT3 interface
shutdown
Enable the CT3 interface
undo shutdown
Shut down a T1 line
t1 t1-number shutdown
Enable the T1 line
undo t1 t1-number shutdown
Disabling/Enabling a CT3 interface will also enable/disable T3 serial interface, the T1

lines demultiplexed from the interface, the serial interfaces formed by the T1 lines, and
the serial interfaces that the T1 lines form by means of timeslot bundling.
Disabling/Enabling a T1 line will also disable/enable the serial interface formed by it or
the serial interface that it forms by means of timeslot bundling.
To disable/enable only a serial interface formed by T3 or T1 line, or by timeslot bundling
on a T1 line, you can perform the shutdown/undo shutdown command in the view of
the serial interface.
Table 3-91 Displaying and debug the CT3 interface information
Operation
Command
Display the states of the CT3 Controller

and all the lines on the interface
display controller t3
[ interface-number ]
Display the configuration and state

information of the serial interface formed
interface-number
by the CT3 interface
3Com Corporation
3-48
Chapter 4 ATM/DSL Interface Configuration

4.1 ATM/DSL Interface
I. ATM and DSL
The technology of Asynchronous Transfer Mode (ATM) is a backbone network
technology that is introduced to transfer voice, video, and data information. By virtue of
its flexibility and support to multi-media service, ATM is regarded as the core
technology for realizing broadband communication.
Digital Subscriber's Line (DSL) is a technology providing high-speed data transmission
over the copper wire. It includes Asymmetric Digital Subscriber Line (ADSL),
High-bit-rate Digital Subscriber Link (HDSL), Very High Rate Digital Subscriber Line
(VDSL), and Symmetric Digital Subscriber Line (SDSL). These DSL technologies are
different primarily in terms of the signal transmission speed and distance and their
symmetry state (that is, whether their uplink and the downlink speeds are the same).
The ATM physical layer lies at the bottom of the ATM reference model. Though it
involves the specific transfer medium, its functionality does not rely on the adopted
transmission mechanism and speed. Rather, it primarily delivers the significant cells
and the associated timing signals between the upper layer and the transmission
medium. The speeds of the physical access media have been standardized by the
concerning international standard organization. For example, there are ATM
OC-3c/STM-1, ATM E3/T3, and ATM E1/T1. As most DSL applications are ATM-based,
they can provide the services integrating the advantages of ATM and the low-cost
transmission feature of DSL. So far, the DSL technologies have been widely adopted
for the broadband accessing.
II. ATM Interfaces available for the medium range routers

So far, the medium-range routers can provide the following interfaces:
z
ATM OC-3c/STM-1 interface module based on SONET/SDH
ATM ADSL interface module based on the ADSL technology
ATM G.SHDSL interface module based on GSHDSL technology
ATM 25.6 M interface module
ATM E3/T3 interface module
The ATM interfaces that the medium-range routers provide support the applications of
IPoA, IPoEoA, PPPoA, and PPPoEoA. For related configurations, refer to the part ATM
Configuration in Link Layer Protocol of this manual.
3Com Corporation
4-1
4.2 Configuring ATM E3/T3 Interface

This section mainly introduces physical configuration of ATM E3/T3 interface. For
detailed configuration of ATM services (including the configuration of PVC), refer to the
part ATM configuration in Link Layer Protocol Configuration of this manual.
Configuration of physical parameters regarding ATM E3/T3 interface mainly includes:
z
Enter specified ATM E3/T3 interface view
Configure clock mode of ATM E3/T3 interface
Configure cable mode of ATM T3 interface
Configure frame format of ATM T3 interface
Configure scramble function of ATM T3 interface
Configure loopback mode of ATM T3 interface
4.2.1 Entering Specified ATM E3/T3 Interface View

Please perform the following configuration in system view.
Table 4-1 Entering view of specified ATM E3/T3 interface
Operation
Command
Enter view of ATM E3/T3 interface
interface atm interface-number
Return to system view
quit
4.2.2 Configuring Clock Mode of ATM T3 interface

ATM E3/T3 interface supports two clock modes:
z
Master clock mode: to use internal clock signal
Slave clock mode: to use line clock signal
The clock mode of interface is decided by the position of the router in the network.
When it is connected with transmission device, slave clock mode should be used on
ATM E3/T3 interface of the router. When two routers are directly connected, one port
should be configured to use master clock mode, with the other port using slave clock
mode.
Please perform the following configuration in ATM E3/T3 interface view.
Table 4-2 Configuring clock mode of ATM E3/T3 interface
Operation
Command
Set clock mode of ATM E3/T3 as master clock master

Set clock mode of ATM E3/T3 as slave
clock slave
Restore the default configuration
undo clock
3Com Corporation
4-2
By default, the clock mode of ATM E3/T3 is slave.
4.2.3 Configuring Cable Mode of ATM T3 Interface

Use the cable command to set the distance mode between the router and the cable
distribution frame for ATM T3 interface.
Perform the following configuration in ATM T3 interface view.
Table 4-3 Configuring cable mode of the ATM T3 interface
Operation
Command
Configure cable mode of the ATM T3 interface
cable { long | short }
Restore to the default setting
undo cable
By default, the cable mode of ATM T3 interface is short.
4.2.4 Configuring Frame Format of ATM E3/T3 interface

ATM E3/T3 interface supports several kinds of frame formats. Besides it supports the
two mapping mode of ATM cells to E3/T3 frame, namely Physical Layer Convergence
Protocol (PLCP) and ATM Direct Mapping (ADM).
Table 4-4 Configuring frame format of ATM E3/T3 interface
Operation
Command
Configure ATM E3 using G.832 direct frame format
frame-format g832-adm
Configure ATM E3 using G.751 direct frame format
frame-format g751-adm
Configure ATM E3 using G.751 PLCP frame format
frame-format g751-plcp
Configure ATM T3 using C-bit direct frame format
frame-format cbit-adm
Configure ATM T3 using C-bit PLCP frame format
frame-format cbit-plcp
Configure ATM T3 using m23 direct frame format
frame-format m23-adm
Configure ATM T3 using m23 PLCP frame format
frame-format m23-plcp
Restore interface frame format to default

configuration
undo frame-format
By default, G.751 PLCP format is used on ATM E3 interface, while C-bit PLCP format is
used on ATM T3 interface.
3Com Corporation
4-3
4.2.5 Configuring Scramble Function of ATM E3/T3 interface

If scramble function is enabled, the interface will perform scramble to cell payload on
forwarding data, and perform descramble to cell payload on receiving data.
If scramble function is disabled, the interface will not perform scramble to cell payload
on forwarding data, nor will perform descramble on receiving data.
Table 4-5 Configuring scramble function of ATM E3/T3 interface
Operation
Command
Enable the scramble function of ATM E3/T3 interface
scramble
Disable the scramble function of ATM E3/T3 interface
undo scramble
By default, the scramble function of ATM E3/T3 interface is enabled. The scramble of
ATM E3/T3 is only valid to payload, with no influence on cell header.
4.2.6 Configuring Loopback Mode

Table 4-6 Configuring loopback mode of ATM E3/T3 interface
Operation
Command
Configure interface internal cell loopback
loopback cell
Configure interface internal loopback
loopback local
Configure interface external payload loopback
loopback payload
Configure interface external line loopback
loopback remote
Remove loopback function of interface
undo loopback
By default, loopback function is disabled.
4.3 ATM 25M Interface

ATM 25M interface is characterized by
z
In compliance with the 25.6M physical-layer interface specifications discussed in

ATM forum (af-phy-040.000) and ITU-T I.432.5
Supporting UTP-5 cables
3Com Corporation
4-4
4.3.1 Configuring ATM 25M Interface

This section mainly introduces physical configurations of ATM 25M interface. For
configuration details of ATM services (including the configuration of PVC), refer to the
section ATM Configuration in Operation Manual - Link Layer Protocol.
Perform the following tasks to configure the physical parameters of ATM 25M interface.
z
Enter the specified ATM 25M interface view
Set clock mode at ATM 25M interface
Set loopback mode at ATM 25M interface
I. Entering the specified ATM 25M interface view

Please perform the following configurations in the system view.
Table 4-7 Entering the specified ATM 25M interface view
Operation
Command
Enter the specified ATM 25M interface view
interface atm number
Return to the system view
quit
II. Setting clock mode at ATM 25M interface

Two types of clock modes are available at the ATM 25M interface:
z
Master clock mode: Uses internal clock signals
Slave clock mode: Uses line clock signals
When an ATM interface serves as DTE, select slave mode for it. When it serves as
DCE, select mater mode. When the two ATM interfaces of two routers are connected
directly, one end uses master mode and the other end slave mode.
Please perform the following configurations in the ATM interface view.
Table 4-8 Setting clock mode at ATM 25M interface
Operation
Command
Set master clock mode at ATM 25M interface
clock master
Set slave clock mode at ATM 25M interface
clock slave
undo clock
By default, an ATM 25M interface is in slave mode.
III. Setting loopback mode at ATM 25M interface

ATM interface loopback is used in testing some particular functions.
3Com Corporation
4-5

Table 4-9 Setting loopback mode at ATM 25M interface
Operation
Command
Enable local cell loopback
loopback cell
Enable local loopback
loopback local
Enable remote loopback
loopback remote
Disable both local and remote loopback
undo loopback
4.4 ATM OC-3c/STM-1 Interface

The ATM OC-3c/STM-1 interface of the medium-range routers supports:
z
Nonreal-time Variable Bit Rate (nrt_VBR)
Real-time Variable Bit Rate (rt_VBR)
Constant Bit Rate (CBR)
Unspecified Bit Rate (UBR)
Permanent Virtual Circuit (PVC)
VC-based traffic shaping
User-to-Network Interface (UNI)
RFC1483: Multiprotocol Encapsulation over ATM Adaptation Layer 5
RFC1577: Classical IP and ARP over ATM
F5 End to End Loopback OAM
AAL5 (ATM Adaptation Layer 5)
4.4.1 Configuring ATM OC-3c/STM-1 Interface

This section mainly introduces physical configuration of ATM OC-3c/STM-1 interface.
For detailed configuration of ATM services (including the configuration of PVC), refer to
the part ATM Configuration in Link Layer Protocol of this manual.
Perform the following major tasks to configure the physical parameters of the ATM
OC-3c/STM-1 interface.
z
Enter the view of a specified ATM OC-3c/STM-1 interface
Set clock mode of the ATM OC-3c/STM-1 interface
Set frame format of the ATM OC-3c/STM-1 interface
Set scramble function of the ATM OC-3c/STM-1 interface
Set loopback mode of the ATM OC-3c/STM-1 interface
3Com Corporation
4-6
I. Entering the view of a specified ATM OC-3c/STM-1 interface

Table 4-10 Entering the view of a specified ATM OC-3c/STM-1 interface
Operation
Command
Enter the view of an ATM OC-3c/STM-1 interface
quit
II. Setting clock mode of the ATM OC-3c/STM-1 interface

ATM OC-3c/STM-1 interface supports two clock modes:
z
Master clock mode in which the internal clock signal is used
Slave clock mode in which the line clock signal is used
When the ATM interface is working as DTE, slave clock mode should be used. When
the ATM interface is working as DCE, master clock mode should be used. When ATM
interfaces of two routers are directly connected by fiber, one end should be configured
with the master clock mode and the other with the slave clock mode.
Perform the following configuration in ATM interface view.
Table 4-11 Setting clock mode of the ATM OC-3c/STM-1 interface
Operation
Command
Set clock mode of the ATM OC-3c/STM-1 interface to master
clock master
Set clock mode of the ATM OC-3c/STM-1 interface to slave
clock slave
Restore the default clock mode of the ATM interface
undo clock
By default, the clock mode of ATM OC-3c/STM-1 is slave.
III. Setting frame format of the ATM OC-3c/STM-1 interface

ATM OC-3c/STM-1 interface supports two kinds of frame formats:
SDH STM-1 frame format
SONET OC-3 frame format
3Com Corporation
4-7
Table 4-12 Setting frame format of the ATM OC-3c/STM-1 interface

Operation
Command
Set frame format of the ATM interface to SDH format
frame-format sdh
Set frame format of the ATM interface to SONET format
frame-format sonet
undo frame-format
By default, SONET OC-3 frame format is used on the ATM OC-3c/STM-1 interface.
IV. Setting scramble function of ATM OC-3c/STM-1 interface

Table 4-13 Setting scramble function of ATM OC-3c/STM-1 interface
Operation
Command
Enable the scramble function of ATM interface
scramble
Disable the scramble function of ATM interface
undo scramble
If scramble function has been enabled, scrambled transmission is to be adopted in

forwarding data, and the descramble will be performed on the received data. If
scramble function has been disabled, scrambled transmission is not to be adopted in
forwarding data and the descramble operation will not be performed on the received
data.
By default, scramble function is enabled. Scramble operation will affect the payload but
not the cell header.
V. Setting loopback mode of ATM OC-3c/STM-1 interface

ATM interface loopback is generally used for testing some special functions.
Table 4-14 Setting loopback mode of ATM OC-3c/STM-1 interface
Operation
Command
Enable the ATM interface to make local cell loopback
loopback cell
Enable the ATM interface to work as a local loop
loopback local
Enable the ATM interface to work as a remote loop
loopback remote
Disable the ATM interface to make loopback
undo loopback
By default, loopback function is disabled.
3Com Corporation
4-8
4.5 ADSL Interface

ADSL is an asymmetric transmission technology that implements the high-speed data
transmission over the twisted-pair copper wire by making use of the unused high
frequency ranges in the regular telephone line with different modulation method. Where,
the uplink band is 26kHz-138kHz that can provide a speed of 640 Kbps, and the
downlink band is 138kHz-1.104MHz that can provide a speed of 8 Mbps. The
transmission speed of ADSL is susceptible to the transmission distance and the line
quality. Normally, a longer transmission distance means a poorer line quality and a
lower transmission rate, and a shorter distance. When setting up a link, ADSL can
automatically make tuning for a reasonable speed taking into consideration the actual
line state information such as distance, noise and some other elements.
The following figure shows a networking topology that is commonly adopted for the
routers with ADSL interfaces. DSLAM at the central office end works as the CO
equipment, the router works as the Customer Premises Equipment (CPE equipment),
the DSL interface card provides the WAN interface, and the Ethernet card provides the
connection to the subscriber LAN. When making the connection, connect the input line
of the subscribers telephone line, the ADSL port on the router and the phone-set
respectively to the Line port, the DSL port and the Phone port on the splitter. As the
transmission speed of ADSL is susceptible to the transmission distance and the line
quality, you should use the standard twisted pairs and guarantee proper connection. .
Before transmitting the service, the CPE equipment must activate the line. Activation
refers to a series of operations that the CO equipment at the central office end and the
CPE make in handshake training and information exchanging. The activation
procedure will be specified in compliance with the ADSL standard, channel mode,
uplink and downlink speeds, and the noise tolerance specified in the line configuration
template. It will test the line distance and state, make the central office and the remote
device make negotiation, and confirm whether the normal operation is allowed in the
above conditions. If the activation succeeds, a communication connection will be set up
between the central office and the remote device for service transmission. When line
activation negotiates connection parameters, CO device plays a master role, while
CPE device plays a slave role, in other words, most connection parameters are
provided and decided by CO device.
Contrary to activation, deactivation will disable the connection between the office and
remote device. If the router finds that the line performance deteriorates, it will
deactivate the line, re-train and re-activate. The preferred activation time is 30 seconds.
3Com Corporation
4-9
Splitter
Line
To
ex ternal line
DSL
Ethenet
DSL
Phone
ADSL Router
Hub
Phone-set
PC
Serv er
PC
Figure 4-1 Networking topology commonly adopted for an ADSL router
4.5.1 Configuring an ADSL Interface

This section mainly introduces physical configurations of ADSL interface. For
Perform the following tasks to configure the physical parameters of ADSL interface.
Enter the specified ATM interface view
Activate/Deactivate the interface
Set the ADSL interface standard
I. Entering the specified ATM interface view

Table 4-15 Entering the specified ATM interface view
Operation
Command
Enter the view of a specified ATM interface
quit
II. Activating/Deactivating the interface

You can use the activate command to activate an ADSL interface and the undo
activate command to deactivate the interface.
You can manually activate/deactivate an ADSL line by using this command for the
purpose of line test and troubleshooting.
3Com Corporation
4-10
Table 4-16 Activating/Deactivating the ADSL interface

Operation
Command
Activate the ADSL interface
activate
Deactivate the ADSL interface
undo activate
By default, the ADSL interface is in the activated state.
III. Setting ADSL interface standard

There are four ADSL interface standards:
auto, that is, auto-sensing.
gdmt, that is, G.DMT (G992.1).
glite, that is, G.Lite (G992.2).
t1413, that is, T1.413.
Table 4-17 Setting loopback mode of the ATM OC-3c/STM-1 interface
Operation
Command
Set the interface to use the auto-sensing mode
adsl standard auto
Set the interface to use the G.DMT (G992.1)

standard
adsl standard gdmt
Set the interface to use the G.Lite (G992.2)

standard
adsl standard glite
Set the interface to use the T1.413 standard
adsl standard t1413
undo adsl standard
The ADSL interface standard defaults to auto-sensing mode.

You should note that this configuration will not take effect unless you activate the
interface again. If you want to make it take effect immediately, you can execute the
shutdown/undo shutdown command or the activate/undo activate command.
4.6 G.SHDSL Interface

G.SHDSL (G.Single-pair high-speed
Digital Subscriber Line) is a symmetric
transmission technology that implements the high-speed data transmission over the
twisted-pair copper wire by making use of the unused high frequency ranges in the with
different modulation method. Currently the 2-wire G.SHDSL and 4-wire G.SHDSL are
supported. The 2-wire transmission speed and 4-wire transmission speed can reach
2.312 Mbps,and 4.624Mbps respectively. The transmission speed of G.SHDSL is
3Com Corporation
4-11
sensitive to the transmission distance and the line quality. Normally, a longer
transmission distance and a poorer line quality mean a lower transmission rate, and
vice versa. When setting up a link, G. SHDSL can automatically make tuning for a
reasonable speed taking into consideration the actual line state information such as
distance, noise and some other elements. Unlikely ADSL, it uses no splitter.
For the networking topology for the routers with G.SHDSL interfaces, refer to that for
the routers with ADSL interfaces. But note that G.SHDSL interface requires no splitter.
4.6.1 Configuring G.SHDSL Interface

This section mainly introduces physical configurations of G.SHDSL interface. For
Perform the following tasks to configure the physical parameters of G.SHDSL interface:
z
Activate/Deactivate the interface
Set G.SHDSL interface annex
Set G.SHDSL interface mode (this mode is only used for 4-wire G.SHDSL
interface)
Set Operating Mode for the G.SHDSL interface
Set Single-pair Rate for the G.SHDSL interface
Set SNR target margin
Set PSD mode for the G.SHDSL interface
Enable/Disable link detection
I. Entering the specified ATM interface view

Please perform the following configurations in the system view.
Table 4-18 Entering the specified ATM interface view
Operation
Command
quit
II. Activate/Deactivate the interface

This command is mainly used in link test and fault diagnosis.
3Com Corporation
4-12
Table 4-19 Activating/Deactivating the interface

Operation
Command
Activate G.SHDSL interface
activate
Deactivate G.SHDSL interface
undo activate
By default, a G.SHDSL interface is active.
III. Setting G.SHDSL interface annex

Two types of annexes are available at the G.SHDSL:
z
A: G.991.2 Annex A, often used in the US
B: G.991.2 Annex B, the default setting, often used in Europe.

Table 4-20 Setting G.SHDSL interface annex
Operation
Command
Set annex A at the interface
shdsl annex a
Set annex B at the interface
shdsl annex b
undo shdsl annex
The annex type at both ends must be the same, otherwise, the interface cannot be
activated. The new configuration cannot take effect until the interface is activated next
time. If you want it to take effect immediately, you have to use the shutdown/undo
shutdown or undo activate/ activate command.
IV. Setting G.SHDSL Interface Mode

In the interface supporting 4-wire G.SHDSL, you can specify the mode for this interface
as 2-wire mode or 4-wire mode. This command can only be configured for the 4-wire
G.SHDSL interface.
Table 4-21 Set G.SHDSL interface mode
Operation
Command
Set G.SHDSL interface mode
shdsl wire {2 | 4 }
undo wire
By default, the G.SHDSL interface mode is 4-wire mode.
3Com Corporation
4-13
V. Set Operating Mode of the G.SHDSL interface

Table 4-22 Set operating mode of the G.SHDSL interface
Operation
Command
Set operating mode of the G.SHDSL

interface
shdsl mode { co | cpe }
undo shdsl mode
By default, G.SHDSL interface works in the customer premises equipment (CPE)

mode.
VI. Setting Single-pair Rate for the G.SHDSL interface

You can set the single-pair rate of G.SHDSL interface or just select auto-negotiation
mode.
z
auto: Auto-negotiation mode, the default setting
rate: Sets maximum rate.

Table 4-23 Set G.SHDSL interface rate
Operation
Command
Select auto-negotiation mode for

single-pair rate of interface
shdsl rate atuo
Set maximum rate for single-pair rate of

interface
shdsl rate rate
undo shdsl rate
By default, a 2-wire G.SHDSL interface uses auto-negotiation mode, and the single-pair
rate of 4-wire G.SHDSL interface is 2,312Kbps (the 4-wire interface rate is 4,624Kbps).
If you want the customized maximum rate to take effect immediately, you have to use
the shutdown/undo shutdown or undo activate/ activate command.
3Com Corporation
4-14
Note:
For 2-wire G.SHDSL, interface rate is single-wire rate; for 4-wire G.SHDSL,
interface rate is two times that of single-wire rate. For example, if you set the
single-pair rate to 2,312Kbps, the 4-wire interface rate is 4,624Kbps.
You cannot set to single-pair rate of 4-wire G.SHDSL interface to auto mode,
because the 4-wire interface cannot negotiate rate.
VII. Setting G.SHDSL Interface SNR

Please perform the following configurations in ATM interface view.
Table 4-24 Set ATM G.SHDSL interface mode
Operation
Command
Set SNR target margin
shdsl snr-margin [ current

current-margin-value ] [ snext
snext-margin-value ]
Restore the default value
undo shdsl snr-margin
By
default,
when
line
negotiates,
current-margin-value
is
set
to
2,
and
snext-margin-value is set to 0.
Note that the SRN is 25 at a G.SHDSL interface by default. If you want the customized
SNR to take effect immediately, you have to use the shutdown/undo shutdown or
undo activate/ activate command.
VIII. Setting PSD Mode for the G.SHDSL Interface

Power spectral density (PSD) is the amount of power per unit (density) of frequency
(spectral) as a function of the frequency. PSD describes how the power of a time series
is distributed with frequency.
You can make the PSD of the CPE interface and that of the peer interface consistent or
inconsistent.
Table 4-25 Set PSD mode for the G.SHDSL interface
Operation
Command
Set PSD mode for the G.SHDSL

interface
shdsl psd { asymmetry | symmetry }
undo shdsl psd
3Com Corporation
4-15
IX. Enabling/Disabling Link Detection

Table 4-26 Enable/Disable link detection for G.SHDSL interface
Operation
Command
Enable/Disable link detection
dsl link-check { enable | disable }
undo dsl link-check
By default, link detection is enabled for G.SHDSL interface.
4.7 Displaying and Debugging the ATM and DSL Interface

Information
After finishing the above configurations, execute the display commands in any view to
view the running state of ATM or DSL interfaces and verify the configuration effect.
Execute the shutdown/undo shutdown commands in interface view. As executing the
shutdown command will disable the ATM or DSL interface, you should use it with
cautions.
Table 4-27 Displaying and debug the ATM or DSL interface information
Operation
Command
Disable the current ATM or DSL interface
shutdown
Enable the current ATM or DSL interface
undo shutdown
Display the configuration and state of the ATM or

DSL interface
display interface atm

[ interface-number ]
Display the actual configuration information of

the DSL line
display dsl configuration

Display the state information of the DSL line
display adsl status interface

atm interface-number
Display the DSL version information and the

available capabilities
display dsl version interface

atm interface-number
Enable debugging
debugging physical error

3Com Corporation
4-16
4.8 Troubleshooting
I. ATM interface
When performing fault diagnosis on an ATM interface, test the interface by executing
the ping command or the extended ping command.
The ping command is used to examine basic network connection condition. Extended
ping command can be used to specify some options in IP header in addition to that
function. For details about the ping command, see Basic Configuration of this manual.
If the ping command fails, the disconnection state is probably caused because:
z
There is no route in the routing table as the interface is in DOWN state.
if ATM 155M interface, the AAL5 encapsulation type of PVC is not correct.
II. DSL interface

Improper line operation is one of the faults that you have a great chance to encounter in
DSL applications. Such a fault is likely to occur on whichever devices or nodes in the
hierarchical broadband network architecture. It is probably caused by the CPE device,
copper wire, splitter, DSL port on DSLAM, or even the broadband access server. For
this reason, you should segment the network for isolating the problem. Generally,
DSLAM provides you with abundant fault isolating methods and a complete guide.
At the CPE end, you can locate the problem with the following approaches:
1)
View the LEDs for the DSL interface card
If the DSL line is in the training stage of the activation, the LINK LED will be blinking.
Once the activation succeeds, the LED will keep ON while other state LINK LEDs keep
OFF. If there is data transmitting activity on the line, the Activity LED will be blinking.
2)
Display the DSL state information by executing the display dsl status command
State of driver/chipsets will display the states of the interface and the transceiver.
The common Phy states include Activating, Active, Startupping, Deactive, Test Mode
etc.
The common Xcvr states include Idle, Data Mode, HandShaking, and Training etc.
The following information will be displayed only if the line has been activated.
Dsl Counter gives the statistics of errors and the error correction information collected
from the interface card.
Dsl Defects displays the current line state. If the line state is getting deteriorate, there
will be a non-zero count. The Overall failures information in this part is an accumulative
value but other error statistic values are not. All the information will be cleared up once
the line becomes normal or is re-activated. If the line quality becomes extremely poor,
you must train and activate the line again.
3Com Corporation
4-17
3)
Enable the debugging by executing the debugging physical command to view

the details of the activation, specifically, the initiation of the activate command,
activation timeout, activation training process, and the activation success.
4)
All the line activation efforts will fail if the DSL line is being set up or unable to be
set up for a long time. This may happen if there is a problem on the line. In this
case, you should check that the telephone cable is correctly connected,
specifically, the input telephone cable of the user, the DSL port on the router and
the phone-set are respectively connected to the LINE port, DSL port and PHONE
port on the splitter. If all the connections are correct, proceed to check that the
telephone cable is reliably connected to the splitter and the indoor telephone
connector is in good condition. If there is no problem, you are recommended to
make an overall line condition and environment check.
5)
If the faults like serious line errors and interference happen too often, you are
recommended to reset the line by performing the shutdown/undo shutdown
operation or performing the power-on operation to set up the connection again. If
the problem is still there, you are recommended to make an overall line condition
and environment check.
3Com Corporation
4-18
Chapter 5 Logic Interface Configuration

Logical interface refers to such an interface that can implement data exchange but
does not physically exist and needs to be set up through configuration. It can be a dialer
interface, subinterface, LoopBack interface, NULL interface, backup center
logic-channel or a virtual-template.
5.1 Dialer Interface

5.1.1 Introduction to Dialer Interface
As the name implies, a Dialer interface is used for the dialing purpose. The
dial-supported interfaces available for 3Com
Routers include synchronous serial
interface, asynchronous serial interface, ISDN BRI interface, and ISDN PRI interface. V
2.04 has implemented the DCC (Dialup Control Center) function. In addition, V 2.04
provides the users with two DCC configuration approaches, specifically, Circular DCC
(C-DCC) and Resource-Shared DCC (RS-DCC), so that the users can make full use of
the DCC function and various Dialer interfaces.
See Dialup Configuration module of this manual for details about configuring polling
DCC and shared DCC, displaying and debugging, configuration example,
troubleshooting.
5.2 Loopback Interface

5.2.1 Introduction to Loopback Interface
The TCP/IP suite provisions that the addresses in the 127.0.0.0 segment are loopback
addresses. The interfaces at such addresses are called loopback interfaces. So far as
a 3Com Router is concerned, the interface Loopback0 is the loopback interface for
receiving all the packets sent to the local routers.
In some applications (such as configuring localpeers in an SNA), there is often the need
to assign a fixed IP address to a local interface without affecting the physical interface
configuration. To save the scarce IP address resources, this IP address must be an
address of 32-bit mask and must be advertised through a routing protocol. The
Loopback interface is introduced for satisfying such a need.
5.2.2 Configuring a Loopback Interface

Perform the following tasks to configure a loopback interface:
Create a loopback interface
3Com Corporation
5-1
Configure the operating parameters of the interface
I. Creating a loopback interface

Table 5-1 Creating/Deleting a loopback interface
Operation
Command
Create a loopback interface and enter the

loopback interface view
interface loopback number
Delete the specified loopback interface
undo interface loopback number
II. Configuring the operating parameters of the interface

You can configure the parameters like IP address and IP routing for a loopback
interface. For details, refer to V 2.043.3 Operation Manual - Network Protocol.
Caution:
You can configure a 32-bit subnet mask for a loopback interface. that is, the subnet
mask can be 255.255.255.255. In addition, the IP address with the 32-bit mask can be
advertised through a routing protocol.
You are recommended to assign a host address of 32-bit mask to a loopback interface.
In this way, you can not only save the address resources but also use the interface as
an unnumbered interface.
5.3 Null Interface

5.3.1 Introduction to Null Interface
3Com Routers support the Null interface. Such an interface is always UP but cannot
forward packets. In addition, no IP address or other
link layer protocols can be
configured on it.
Null interface is the logical interface of pure software property. Therefore, all the
network specific packets sent to the interface will be dropped.
5.3.2 Configuring a Null Interface

Perform the following tasks to configure a Null interface:
Create a Null interface
Configure the interface operating parameters
3Com Corporation
5-2
I. Creating a Null interface

Perform the following configuration in system view to create the interface Null 0 on a
3Com router.
Table 5-2 Creating/Deleting a Null interface
Operation
Command
Create a Null interface and enter the Null

interface view
interface null 0
Delete the Null interface
undo interface null 0
As a Null interface drops all the packets reaching it, it provides you with a means of
packet filtering. You can simply make the configuration to send all the undesired
network traffic to the interface Null0 rather than bothering yourself with the complex
work of configuring ACL (Access Control List).
For example, you can drop all the packets destined to the segment 192.101.0.0 by
configuring the static routing command ip route-static 192.101.0.0 255.255.0.0 null 0.
5.4 Subinterface
5.4.1 Introduction to Subinterface
Introducing the concept of subinterface into V 2.04 allows the users of 3Com Routers
of high flexibility as the users can configure multiple subinterfaces on a single physical
interface in this case.
Subinterfaces are the logical virtual interfaces configured on a physical interface. They
share the physical layer parameters of the physical interface and can be separately
configured with the link layer and network layer parameters. As they can be associated
with a physical interface, they are often called subinterfaces.
On 3Com Routers, the subinterface-supported physical interfaces include:
z
Ethernet interface. Without VLAN ID, an Ethernet subinterface can only support
IPX. Assigned with a VLAN ID, the subinterface can support both IPX and IP.
WAN interface encapsulated with FR. The subinterfaces of such a WAN interface
can support both IP and IPX.
WAN interface encapsulated with X.25. The subinterfaces of such a WAN

interface can support both IP and IPX.
5.4.2 Configuring a Subinterface

Perform the following tasks to configure a subinterface:
z
Configure Ethernet subinterface
Configure a subinterface on a WAN interface encapsulated with FR

3Com Corporation
5-3
Configure a subinterface on a WAN interface encapsulated with X.25
I. Configuring Ethernet subinterface

1)
Create/Delete an Ethernet subinterface

Table 5-3 Creating/Deleting an Ethernet subinterface
Operation
Command
Create an Ethernet subinterface and

enter the Ethernet subinterface view
interface ethernet
number.sub-number
Delete the specified Ethernet

subinterface
undo interface ethernet

number.sub-number
If the Ethernet subinterface (the same as sub-number) that you intend to create has
existed, the system will directly enter the view of the subinterface. Otherwise, the
system will create the Ethernet subinterface assigned with sub-number before entering
its view.
2)
Configure the relevant operating parameters
As an Ethernet subinterface that has not been assigned with VLAN ID can only support
IPX, you can only assign an IPX address to such an Ethernet subinterface and
configure the IPX operating parameters. But the configuration procedure is similar to
that for configuring an Ethernet interface. An Ethernet subinterface that has been
assigned with VLAN ID can support both IP and IPX. For the related configurations,
refer to V 2.043.3 Operation Manual - Network Protocol.
II. Configuring a subinterface on a WAN interface encapsulated with FR

1)
Create/Delete a WAN subinterface

Table 5-4 Creating/Deleting a WAN subinterface
Operation
Command
Create a WAN subinterface and enter

its view
interface serial number.sub-number

[p2mp | p2p ]
Delete the specified WAN

subinterface
undo interface serial number.sub-number
If the WAN subinterface (the same as sub-number) that you intend to create has
existed, the system will directly enter the view of the subinterface. Otherwise, the
system will create the WAN subinterface assigned with sub-number before entering its
view.
3Com Corporation
5-4
2)
You can make the following configurations for a subinterface on a WAN interface
encapsulated with FR.
FR address map different from that of the WAN interface (also called the main interface)
to which the subinterface belongs
IP address beyond the segment on which the main interface is located
IPX network number and other IPX parameters different from the main interface
VCs belonging to the subinterface
For more information about the configurations, refer to V 2.043.3 Operation Manual Link Layer Protocol and V 2.043.3 Operation Manual Network Protocol.
III. Configuring a subinterface on a WAN interface encapsulated with X.25

1)
Create/Delete a WAN subinterface
You can use the same commands described in Table 5-4 to create/delete a WAN
subinterface.
2)
You can make the following configurations for a subinterface on a WAN interface
encapsulated with X.25.
X.25 address map different from that of the WAN interface (also called the main
interface) to which the subinterface belongs
IP address beyond the segment on which the main interface is located
IPX network number and other IPX parameters different from the main interface
VC belonging to the subinterface
For more information about the configurations, refer to V 2.043.3 Operation Manual Link Layer Protocol and V 2.043.3 Operation Manual Network Protocol.
IV. Typical WAN subinterface configuration example

1)
Networking requirements
As shown in the following figure, the WAN interface Serial0/0/0 on Router A is

connected to Router B and Router C via a public FR network. By configuring
subinterfaces on Serial0/0/0 on Router A, you can make LAN 1 to simultaneously
access LAN 2 and LAN 3 via Serial0/0/0.
2)
Networking diagram
3Com Corporation
5-5
129.10.0.0
Ethernet 2
Router A
Ethernet 1
202.38.160.2
DLCI=70
202.38.160.1
DLCI=50
Router B
Frame Relay
Serial0
DLCI=60
202.38.161.1
DLCI=80
202.38.161.2
Router C
129.9.0.0
Ethernet 3
129.11.0.0
Figure 5-1 Networking for the WAN subinterface configuration example

3)
Configuration procedure
# Enter the view of Serial0/0/0 on Router A.

[3Com] interface serial 0/0/0
# Encapsulate the interface with FR.

[3Com-Serial0/0/0] link-protocol fr
# Specify the interface to work as DTE in FR.

[3Com-Serial0/0/0] fr interface-type dte
# Create the subinterface Serial 0/0/0.1 on Serial0/0/0 on Router A, specify it work in

point-to-point mode, and enter the view of the subinterface.
[3Com] interface serial 0/0/0.1 p2p
# Assign the IP address 202.38.160.1 to the subinterface, given the mask is

255.255.255.0.
[3Com-Serial0/0/0.1] ip address 202.38.160.1 255.255.255.0
# Assign the VC assigned with DLCI 50 to the subinterface.

[3Com-Serial0/0/0.1] fr dlci 50
# Create the subinterface Serial 0/0/0.2 on Serial0/0/0 on Router A, specify it to work in

point-to-point mode, and enter its view.
[3Com] interface serial 0/0/0.2 point-to-point
# Assign the IP address 202.38.161.1 to the subinterface, given the mask is

255.255.255.0.
[3Com-Serial0/0/0.2] ip address 202.38.161.1 255.255.255.0
# Assign the VC assigned with DLCI 60 to the subinterface.

[3Com-Serial0/0/0.2] fr dlci 60
3Com Corporation
5-6
# Configure the static routes from Router A to LAN2 and LAN3.

[3Com] ip route-static 129.10.0.0 255.255.0.0 202.38.160.2
[3Com] ip route-static 129.11.0.0 255.255.0.0 202.38.161.2
The configurations of Router B and Router C are omitted.
5.5 Logic-Channel of Backup Center

5.5.1 Introduction to Logic-Channel of Backup Center
In addition to providing the backup between interfaces, the backup center allows an
X.25 or FR VC to work as the master interface or standby interface of the backup center.
For more information about the backup center, refer to V 2.043.3 Operation Manual Reliability.
To make the configuration easier, you can specify a logic-channel for the VC discussed
above, and then configure the operating parameters of the backup center on the
logic-channel.
5.5.2 Configuring a Backup Center Logic-Channel

For the sake of simplicity, the details of backup center logic-channel configuration, its
display and debug, typical configuration example, and troubleshooting will not be
covered in this part. You can find them in V 2.043.3 Operation Manual - Reliability.
5.6 Virtual-Template and Virtual Interface

5.6.1 Introduction to Virtual-Template and Virtual Interface
Virtual-Template is a template for configuring a virtual interface. It is primarily applied in
the application environments like VPN and MP.
After setting up a VPN session, the system needs to create a virtual interface for
exchanging data with the remote end. For this purpose, the system will choose a
virtual-template according to the users configuration, and dynamically create a virtual
interface based on the configuration parameters of the template. For VPN configuration
details, refer to the related sections of VPN Configuration in this manual..
Likewise, after bundling multiple PPP links into an MP, the system also needs to create
a virtual interface for exchanging data with the remote end. In this case, you can select
a virtual-template for the purpose of dynamic creation of virtual interface.
5.6.2 Configuring a Virtual-Template

In VPN and MP application environments, the system automatically creates and
deletes virtual interfaces, which is completely transparent to the user. The user only
needs to configure VPN or MP on the involved physical interface, creates and
3Com Corporation
5-7
configures a virtual-template, and finally associates the virtual-template with the

physical interface.
Perform the following tasks to configure a virtual-template:
Create/Delete a virtual-template
Set operating parameters of virtual-template
Associate the virtual-template with the involved physical interface
I. Creating/Deleting a virtual-template
Table 5-5 Creating/Deleting a virtual-template
Operation
Command
Create a virtual-template and enter

the virtual-template view
interface virtual-template number
Delete the virtual-template
undo interface virtual-template number
If the virtual-template that you intend to create by using the interface virtual-template
command has existed, the system will directly enter the view of the virtual-template.
Otherwise, the system will create the virtual-template assigned with specified number
before entering its view.
In deleting a virtual-template, make sure that all of its derived virtual interfaces have
been removed and this virtual-template is not in use any more.
II. Setting operating parameters of virtual-template

Compared with a regular physical interface, virtual-templates only support PPP in
terms of link layer protocol and IP and IPX in terms of network protocol. accordingly,
you can perform the following tasks to set the following operating parameters:
Set PPP operating parameters
Assign an IP address to the virtual interface
Set the IP address (or IP address pool) assigned to the PPP peer
Setting these parameters on a virtual-template is the same as setting them on a regular
interface.
III. Associating the virtual-template with the involved physical interface

You are required to associate an L2TP group with the virtual-template in a VPN
environment and MP user with the virtual-template in an MP environment.
For details, refer to V 2.043.3 Operation Manual - VPN.
3Com Corporation
5-8
5.6.3 Displaying and Debugging Virtual-Template and Virtual Interface

When needed, the system can automatically create a virtual interface and operate it
with the parameters of the associated virtual-template. Therefore, manual creation and
configuration are not needed.
A virtual interface can be deleted due to the
disconnection of the bottom layer link or the interruption of the user.

Execute the following command in any view to display the state of a specified
virtual-template.
Table 5-6 Displaying the state of a specified virtual-template
Operation
Command
Display the state of a specified

virtual-template
display interfaces virtual-template

number
5.6.4 Troubleshooting
Before isolating the faults of a virtual-template, you must make sure the application
environment, specifically, whether the virtual-template is used for creating a VPN virtual
interface or for creating an MP virtual interface.
Fault 1: The system failed to create a virtual interface.
Problem solving: Such a problem may arise because:
z
The virtual-template had not been assigned with an IP address. Therefore, the
virtual interface failed to pass the PPP negotiation and hence could not go up.
The virtual-template had not been configured with the IP address (or IP address
pool) intended for the peer. Therefore, if it is necessary to allocate address for the
peer, the associated virtual interface could not satisfy the requirements of the peer
and hence could not go up.
PPP authentication parameters were incorrectly set. If the peer was not a user
defined on the router, PPP negotiation would also fail.
5.7 Virtual Ethernet Interface

5.7.1 Introduction to Virtual Ethernet Interface
Virtual Ethernet interface (VE) is a logical interface that is implemented on the interface
card. It is primarily application to Point to point Protocol over Ethernet over ATM
(PPPoEoA).
PPPoEoA adopts a three-layer architecture, with the top layer encapsulated with PPP,
the mid-layer with PPPoE (PPP over Ethernet), and the bottom layer with PPPoE over
ATM.
3Com Corporation
5-9
Typically, PPPoE is applied to the community broadband access and to the application
in which multiple hosts share a front-end bridging access device. The PPP parameters
carried over the Ethernet are implemented on the interface card of the access device
via Virtual Ethernet interface. For accessing a remote access server (for the purpose of
accessing an external network) via this device, the ATM PVC must be adopted due to
the long distance involved. In this case, the ATM port on the server is required to carry
the Ethernet packets, which is called PPPoEoA.
For details, refer to Operation Manual - Link Layer Protocol.
5.7.2 Virtual Ethernet Interface Configuration

Perform the following tasks to configure a Virtual Ethernet interface:
Create/Delete a Virtual Ethernet interface
Configure Virtual Ethernet interface parameters
I. Creating/Deleting a Virtual Ethernet Interface

Table 5-7 Creating/Deleting a Virtual Ethernet interface
Operation
Command
Create a Virtual Ethernet interface
interface virtual-ethernet number
Delete the Virtual Ethernet interface
undo interface virtual-ethernet number
The user may establish as many as 1024 Virtual Ethernet interfaces.

When configuring a PVC to carry PPPoEoA, you must associate a VE interface with
the PVC. If the specified VE interface has not been created yet, the configuration will
fail and the system will return. A VE interface can only be associated with a PVC
carrying PPPoEoA. The efforts of deleting a VE interface will fail if the VE interface has
been associated with a PVC carrying PPPoEoA.
II. Configuring Virtual Ethernet Interface parameters

You can set the VE interface parameters in the same way of setting Ethernet interface
parameters. For details, refer to Ethernet Interface in this manual.
As the debug and display operations of VE interface and Ethernet interface are the
same, this section will not cover the details for the sake of simplicity.
For the typical PPPoEoA configuration example, refer to Operation Manual - Link Layer
Protocol.
3Com Corporation
5-10

Configuration

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Configuration

Transféré par

Droits d'auteur :

Formats disponibles

V2.

V2.04 Documentation Addendum

3.7.1 Introduction to CT1/PRI Interface.......................................................................... 3-24

V2.04 Documentation Addendum

5.2.1 Introduction to Loopback Interface.......................................................................... 5-1

Documentation Addendum - Interface

Chapter 1 Interface Configuration Overview

Chapter 1 Interface Configuration Overview

1.2 Interface Configuration

I. Method to enter the interface view

Enter specified interface view

interface type number

Documentation Addendum - Interface

Chapter 1 Interface Configuration Overview

II. Method to exit interface view

1.2.2 Configuring Interface Description

Configure interface description

Restore the interface description to default

1.2.3 Configuring an Average Interface Rate Measurement Period

Configure an average interface rate

Restore the default average interface

undo flow-interval seconds

1.2.4 Configuring an Interface

Documentation Addendum - Interface

Chapter 1 Interface Configuration Overview

Assign a network protocol (such as IP) address to the interface

If the interface is working as a master interface or standby interface in the backup

1.3 Displaying and Debugging Interfaces

Display the current operating state and

display interface [type number ]

Display the major configuration

display ip interface [type number ]

Clear the interface statistic information

reset counters interface [ type

Shut down an interface in interface view

Re-enable the interface in interface view

Enable debugging at a specified

debugging physical { all | error | cell |

Disable debugging at a specified

undo debugging physical { all | error |

Documentation Addendum - Interface

Chapter 1 Interface Configuration Overview

% Interface Serial0/0/0 is down

The interface is shutdown by the user

% Interface Serial0/0/0 is reset

The interface is re-enabled by the user

%01:10:34: Interface Serial0/0/0

The physical status of the interface

%01:11:03: Interface Serial0/0/0

The physical status of the interface

%01:12:02: Line protocol ip on interface

The protocol status of the interface

%01:11:34: Line protocol ip on interface

The protocol status of the interface

V2.04 Documentation Addendum

Chapter 2 LAN Interface Configuration

Chapter 2 LAN Interface Configuration

2.1 Ethernet Interface

II. Operating speed and mode

III. Supported frame formats

2.1.2 Ethernet Interface Configuration

V2.04 Documentation Addendum

Chapter 2 LAN Interface Configuration

Enter specified Ethernet interface view