configure interfaces
examples
of interface configurations
Details
about configuration tasks , refer to “ examples of interface configuration”.
Details
about hardware technology description and information about installing
interface, refer to manual of hardware installing and configuration, Details
about interface instructions, refer to “interface configuration
instructions”.
This
chapter will discuss how to configure Ethernet interface. The router support
10Mbps Ethernet interface and 100Mbps quick Ethernet interface. Details are
following, the first step is necessary, other steps are optional.
appoint Ethernet or quick Ethernet interface
You
can input instructions following in overall situation configure mode to enter
the mode of ethernet interface
configuration
instruction |
purpose |
interface
ethernet slot/port |
Enter
the mode of ethernet interface
configuration |
interface
fastethernet slot/port |
the
mode of quick ethernet interface
configuration |
“show
interface Ethernet” can display Ethernet interface state. show interface
Ethernet can display quick Ethernet interface state.
configure 100Mbps quick Ethernet interface
Our routers’quick ethernet interface support routers ,hubs and switchs with 10Mbps and 100Mbps or with 100BaseT or 10BaseT interface . it can support 10Mbps and 100Mbps auto-adapted speed, that is to say, it can choose a fit speed according to connecting equipment. The configuration courses from management are following:
step |
instruction |
purpose |
1 |
configure |
Enter the mode of overall configuration |
2 |
interface fastethernet slot/port |
Enter quick Ethernet configuration mode |
3 |
ip address address subnet-mask |
Set IP address and mask on interface |
configure the speed of quick ethernet
The
speed of quick Ethernet can realize auto or through
configuring interface
instruction |
purpose |
Speed
{10|100|auto} |
Set
speed to 10M,100M or auto |
No
speed |
Renew
to default ,speed is auto |
quick
ehternet duplex mode configuration
Duplex mode of quick Ethernet can realize auto or through configuring
interface
instruction |
purpose |
Duplex
half |
Set
to semi-duplex mode |
Duplex
full |
Set
to full-duplex mode |
No
duplex |
Renew
to default, duplex mode is auto |
configure Ethernet sub-interface
This
part will introduce how to configure Ethernet sub-interface. Router support iEEE
802.1Q on Ethernet sub-interface. Details are following:
appoint
Ethernet sub-interface
You
can input instructions below to enter the mode “Ethernet
interface configuration” in “overall situation configuration” mode.
instruction |
purpose |
interface
ethernet slot/port。subinterface-number |
Enter
Ethernet sub-interface configuration mode |
interface
fastethernet slot/port。subinterface-number |
Enter
quick Ethernet sub-interface
configuration mode |
You
must encapsulate 802.1Q to Ethernet
sub-interface or it can not be used, or
the protocol can not UP.
instruction |
purpose |
encapsulation
dot1q vlan-identifier |
encapsulation
802.1Q and appoint vlan ID |
This
part will introduce how to configure serial interface, Details about hardware ,
please refer to “hardware install and configure”. Details about serial
interface instruction ,please refer to “interface instructions”, Other
instructions documents can lookup from instructions index. The content
are:
configure
synchronization serial interface
configure
low-speed serial interface
configure synchronization serial interface
Steps
are following, the first step is necessarry, others are optional.
appoint
sychronization serial interface
set
appoint sychronization serial interface encapsulation
For
examples ,refer to “ examples of interface configurations”.
appoint
sychronization serial interface
You
can input instructions below to appoint synchronization serial interface and
enter the mode " interface configuration" in "overall situation
configuration" mode.(if it is a asynchronism card, you should replace
“serial” by “async.”
instruction |
purpose |
interface
serial slot/port |
Enter”
interface configuration” |
interface
serial slot/port:channel-group |
Enter”
channel E1 interface configurations” |
Set appoint sychronization serial interface encapsulation
If
default , sychronization serial interface take HDLC encapsulation. It provides
“synchronization framing” and “error checking “ of HDLC in mode of
without windows or re-transmit. Sychronization serial interface
support following protocols:
HDLC
Frame
Relay
PPP
·X.25
SDLC
You
can set encapsulation protocol through following instructions in the mode of
interface configuration:
instruction |
purpose |
encapsulation
{hdlc|frame-relay|ppp|x25|sdlc} |
Configure
synchronization serial encapsulation protocol |
The kind of encapsulation should depend on practical application. You can also get knowledge in “interface configuration instructions”.
configure low-speed serial interface
This part will introduce to how to configure low speed serial interface, you can get an example form “ examples of low speed serial interface”.
Low speed serial interface often support synchronization and asynchronism , you can use following instructions to choose one way:
instruction |
purpose |
physical-layer
mode {sync |async} |
Choose
“synchronization” or “asynchronism” |
In asynchronism mode ,the interface will support all instructions on standard asynchronism interface. The default is synchronization .If you want to change from asynchronism to synchronization, you can use following instructions in interface configurations mode:
instruction |
purpose |
no physical-layer mode |
Going back to default-- synchronization |
You
can configure its speed in the interface, use
following instructions in interface configurations mode:
instrution |
purpose |
physical-layer
speed speed |
Set
interface speed |
The
speed values supported by asynchronism or
synchronization are following:
Synchronization
interface |
Asynchronism
interface |
1200,2400,4800,9600,14400,19200,38400,
57600,64000,115200,128000,256000,512000,1024000,2048000 |
1200,2400,4800,9600,14400,19200,38400,57600,115200 |
Introduction of E1 interface
There
are two configurations to E1 interface:
Use as channelized E1 interface
Interface can be divided into 31 time intervals physically , you can
divide them into some groups as you like, every tied group will be served as a
interface, its logic features is the same as synchronization serial interface,
support PPP, frame relay, LAPB , X.25 and etc. link layer protocols.
Use as unchannelized E1 interface
This interface can be seen as a 2Mbps G.703 synchronization serial
interface, support PPP, frame relay, LAPB , X.25 and etc. link layer protocols.
E1 interface configurations
You
need to firstly input “controller E1” in "overall situation
configuration" mode to configure E1 interface.
instruction |
purpose |
controller
E1 <slot>/<group> |
Configure
E1 interface Slot
is serial number E1 controller locating Group
is line serial number to E1 controller |
for
an example:
Router_config#controller
E1 2/0
Router_config_controller_E1_2/0#
E1
interface configurations tasks include:
l
configure E1 interface physical parameter, including frame verify way, line
coding/decoding format, line clock, back-loop transportation mode and etc.
usually, the default value is ok.
l
Channelized E1 need to configure channel-group parameter, to set time interval
binding way.
l
Unchannelized E1 do not need to configure channel- group parameter.
l
configure interface parameter
Default
is Channelized , but you can change to unchannelized by “unframed”.
instruction |
purpose |
unframed |
Configure
to “unchannelized” |
No
unframed |
Configure
to “ Channelized” |
for
an example:
Router_config#controller
E1 2/0
Router_config_controller_E1_2/0#
unframed
Router_config_controller_E1_2/0#
no unframed
E1
interface support” CRC32 verify” to physical frame, default is “ no
verify”
instruction |
purpose |
Framing
crc4 |
Configure
E1 interface frame verify mode into 4bytes “CRC verify” |
No
framing or framing no-crc4 |
Configure
E1 interface without frame verify |
E1
interface line support two coding/decoding format: AMI and HDB3
Default
is HDB3 .
instruction |
purpose |
Linecode
ami |
configure
E1 interface line coding/decoding format into AMI |
No
linecode or linecode hdb3 |
configure
E1 interface line coding/decoding format INTO HDB3 |
When
E1 is used as synchronization interface, there are two work modes: “DTE” and
“DCE”, you need to choose line clock also. When E1 interfaces of two routers
are directly connected , it is necessary to let two interfaces work at “DTE”
OR “DCE”; when E1 of a router is connected into a switch ,because switch is
a “DCE” device, E1 of a router need
to work at “DTE”
mode.
The
default work mode of E1 is DTE.
instruction |
purpose |
Clock
interval |
Configure
E1 to “DCE”, use synchronization in chip |
Clock
external |
Configure
E1 to “DTE”, use line asynchronism |
In
remote back-loop transportation mode, E1 will send back message from the tunnel
from which it receives the message.
instruction |
purpose |
Loopback
local |
Configure
E1 to remote loopback mode |
No
loop |
Cancel
remote loopback setting |
Choose
send pulse mode. When cable is 120Ω twisted-pair, choose Cable 120.
Default
is 75Ω coax cable, according with “ITU-T G.703”.
They send pulse differently.
instruction |
purpose |
Cable
120 |
Configure
E1 interface cable to “120Ω twisted-pair” |
No
cable |
Default
is 75Ω coax cable |
You
can disabled some E1. Just make all
lines state on interface is “down”.
instruction |
purpose |
shutdown |
Disabled
E1 interface line |
No
shutdown |
Restart
E1 interface line |
for
an example:
Router_config#controller
E1 2/0
Router_config_controller_E1_2/0#shutdown
Router_config_controller_E1_2/0#no
shutdown
Channel-group
is tunnel number of E1, ranging from 0-30, timeslot is time interval number of
E1, ranging from 1-31. Tunnel can use any indistributive timslot, and can group
timeslot free. New interface will form after successfully configuring E1.
“no
channel-group” will clear channel-group timeslots binding ,the
corresponding interface will delete also.
instruction |
purpose |
channel-group
channel-group timeslots { number | number1-number2 } [,number |
number1-number2 ... ] |
Binding
timeslots of E1 to channel-group |
no
channel-group channel-group |
Cancel
channel-group timeslots binding |
for
an example:
Router_config#controller
E1 2/0
Router_config_controller_E1_2/0#channel
5 timeslots 18,11-13,20,22,30-28,24-25
Router_config_controller_E1_2/0#interface
s0/0:5
Router_config_interface_s1/0:5#
In
Channelized mode, after configuring E1 channel-group parameter, a new interface
will appear. Its logic characters are the same as synchronization. Its name is
“ serial<slot>/<group>:<channel-group>”, and
<slot> and <group> are consistent with <slot> and
<group> in “controller E1 <slot>/<group>”.
In
Unchannelized mode, after configuring E1 channel-group parameter, a new
interface will appear. Its name is serial<slot>/<group>:0
You
can encapsulate PPP, frame relay, HDLC , SDLC ,X.25 and etc.line layer protocols
on interface.
for
an example:
in
Chanelized mode:
Router_config#controller
E1 2/0
Router_config_controller_E1_2/0#channel
1 timeslots 1-31
Router_config_controller_E1_2/0#int
s0/0:1
Router_config_controller_s1/0:1#enca
fr
Router_config_controller_s1/0:1#ip
add 130.130.0.1 255.255.255.0
In
Unchannelized mode
Router_config#controller
E1 2/0
Router_config_controller_E1_2/0#unframed
Router_config_controller_E1_2/0#int
s0/0:0
Router_config_controller_s1/0:0#enca
fr
Router_config_controller_s1/0:0#ip add 130.130.0.1 255.255.255.0
Introduction to T1 interface
As a channelized T1 interface.
Interface is separated into 24 slots on physics, which can be
separated into several units. Bind up each unit to be an interface. It supports
data link layer protocol such as PPP, FR,LAPB, and X.25.
T1 Interface Configuration
To
configure T1 interface, enter controller T1Command under Global
configuration mode.
Command |
Function
|
controller
T1 <slot>/<group>
|
Configure
T1 interface Slot
is the slot number in T1 controller Group
is link number in T1 controller |
Example:
Router_config#controller T1 2/0
Router_config_controller_T1_2/0#
T1
interface configuration tasks including:
l To
configure T1 interface physical parameter, including Frame mode,
decoding/encoding format, line timer,and loop back transmission mode. Use
default parameters.
l Channelized
T1 interface requests for channel-groupparameter configuration. Confirm the
method to binding slots.
l Configure
interface
parameter,
Configuring T1 interface Frame mode
T1 interface supports 2
modes: ESFmode and SFmode.
The default is ESFmode.
Command |
Function |
framing sf |
Configure T1
interface Frame mode as SFmode |
no framing
or framing esf |
Configure T1
interface Frame mode as ESFmode |
Configure T1 interface encoding/decoding
format
T1
interface supports one encoding/decoding format: B8ZS
B8ZS
is default.
Command |
Function |
no linecode or
linecode b8zs |
Configure T1
interface encoding/decoding format as B8ZS |
Configure
T interface timer
When
T1 is used as synchronizing interface, DTE and DCE needs to choose timer as
well. When 2 routers T1 interfaces connect to each other, the routers have to
work under DTE and DCE. When T1 interface connects to a switch, the switch is
DCE and router's T1 interface has to work under DTE.
T1
interface works under DTE by default.
Command |
Function |
clock internal |
Configure T1 interface works under DCE
and uses chip synchronized signal |
clock external |
Configure T1 interface works under DTE
and uses line synchronized signal |
Configure T1 interface transmission mode
Under remote loop transmission mode, T1 transfers back the packet
received from the interface.
Command |
Function |
loopback local |
Configure the local
loop in T1 interface |
Loopback remote |
Configure the remote
loop in T1 interface |
no loop
|
Cancel remote loop
configuration |
Configure T1 sending pulse mode
choose
a pulse sending mode. The cable is 100 ohm. There are 5 distances for Short type
cables: 133ft, 266ft,
399ft, 533ft, 655ft;
when the cable type is Long Haul, there are 4 decreasing level: 0db, -7.5db, -15db, -22.5db.
Long and 0db by default.
Command |
Function |
Cablelength long
{0db, -7.5db, -15db, -22.5db} |
Configure T1interface cable type as Long |
Cablelength short
{133ft, 266ft, 399ft, 533ft, 655ft}
|
Configure T1 interface cable type as
Short |
No cable |
Long and 0db by
default. |
example:
Router_config#controller
T1 2/0
Router_config_controller_T1_2/0#cablelength
short 133ft
Router_config_controller_T1_2/0#no
cablelength
Router_config_controller_T1_2/0#cablelength
long –15db
Disable
T1 interface link
Users
can
disable a T1 interface. it can make each line statue on the
interface as down.
Command |
Function |
Shutdown |
Disable T1 interface
link |
No shutdown
|
Restore the T1
interface link |
example:
Router_config#controller
T1 2/0
Router_config_controller_T1_2/0#shutdown
Router_config_controller_T1_2/0#no
shutdown
Configure chann el-groupparameter for T1
interface
channel-group is T1 channel No., ranging from 0-23. Timeslot is T1
slot, ranging from 0-23. Channels can use any slots that is not allocated, and
channels can compose any slots together as well. Configuring a T1 channel
produce a new interface.
no channel-group clears channel-group slot binding and the
corresponding interfaces are also deleted.
Command |
Function |
channel-group
channel-group timeslots { number | number1-number2
} [,number |
number1-number2 ... ] speed
{
56 |
64 } |
Bind up T1 interface
slots as channel-group and limit its speed as 56 K or 64 K. (64K by
default) |
no channel-group
channel-group
|
Cancel channel-group
slot binding |
Example:
Router_config#controller
T1 2/0
Router_config_controller_T1_2/0#channel
5 timeslots 18, 11-13,
20, 22 speed 56
Router_config_controller_T1_2/0#interface
s0/0:5
Router_config_interface_s1/0:5#
Configuring T1 interface parameters
Under
channelized method, after configuring channel-groupparameter, the system produce
a new interface. The name is
serial<slot>/<group>:<channel-group>, where <slot> and
<group> are the same as controller T1 <slot>/<group>.
This
is able to encapsulate link layer protocol such as PPP, HDLC, SDLC and X.25 on the
interface.
Example:
Channelizing
methods are as follows:
Router_config#controller
T1 2/0
Router_config_controller_T1_2/0#channel
0 timeslots 0-23
Router_config_controller_T1_2/0#int
s2/0:0
Router_config_controller_s1/0:1#enca
fr
Router_config_controller_s1/0:1#ip
add 130.130.0.1 255.255.255.0
Introduction to PRI interface
PRI
interface is a 30B+D ISDN interface. The number of B channel of our PRI
interface can be configured according to users requirement. No need to take up
30 B channels. With E1 interface, users are able to dynamically establish or
delete PRI interface. E1 interface can configure E1 slots to be a normal serial
interface or a B channel of PRI interface by Command way. When a E1
interface configure one or several slots as B channel(s) for PRI, the 15th
slot is always taken by PRI interface ,as a D channel for PRI interface alternate
signal.
PRI interface Configuration
To
Configure PRI interface,Enter
controller E1 Command under global configuration mode.
Command |
Function
|
controller E1 <slot>/<group>
|
Configure
E1 interface slot
is the slot number in E1 controller group
is link number in E1 controller |
Command |
Function
|
Pri-group
timeslot
num |
num:
B channel may allocate several slots. When these slots are in successive
order, use “-”,
if not, use “,”. |
Use
int serial slot/port:15 to enter D channels. After entering D
channel, users may encapsulate protocol , set dial group and set dial mapping.
Introduction to BRI interface
BRI
is a 2B+D ISDN interface. D channel is used to establish the signal alternating
channel with the interface , B channel is used for data transmission.
BRI interface Configuration
To
configure BRI interface, users must be under ISDN BRI interface configuration
mode.
Command |
Function |
interface
bri <slot>/<group>
|
Enter
ISDN BRI interface slot
is the slot number in BRI controller group
is the link number in BRI controller |
This part will introduce how to configure DTU interface. Router 1750/26202621/2630and 2650 support DTU interface. Steps are following:
·
configure
DTU interface work mode
·configure
DTU interface rate mode
· configure DTU interface speed
·configure DTU interface loop function
You can input instructions below
to enter the mode "DTU interface configuration" in "overall
situation configuration" mode.
instrution
|
purpose
|
interface
bm <slot>/<port> |
Configure
DTU interface |
for an example:
router_ config #interface bm2/0
configure DTU interface work mode
instrution |
purpose |
linemode nt |
Configure DTU interface to NT work mode |
linemode lt |
Configure DTU interface to LT work mode |
Default
is NT work mode.
For
an example: configure DTU interface to work in LT mode.
router_ config bm2/0#linemode lt
configure
DTU interface rate mode
instrution |
purpose |
ratemode A |
Configure DTU interface to A
rate mode (normal mode) |
ratemode B |
Configure DTU interface to B
rate mode (X50 compatible mode ) |
Default is A rate mode.
For an example: configure DTU interface to work in B
rate mode.
router_ config bm2/0#ratemode B
instruction
|
purpose
|
physical-layer
speed
speed |
Appoint
interface speed |
supported speed values
are following:
Speed
value |
explains
|
9600,19200,38400,64000,128000 |
Default
is 128000 |
for an example: configure
DTU interface speed to 64K.
configure
DTU interface loop function
instrution |
purpose |
loopback local |
Configure DTU interface to
local loop mode |
loopback remote |
Configure DTU interface to
remote loop mode |
For an example: configure DTU interface to
work in remote loop mode.
router_
config bm2/0#loopback remote
This part will introduce how to configure logic interface, include:
·
how
to connect to v.92 MODEM and the MODEM which does not support V.42bis
· SOLVE THE PROBLEM THAT AM CARD CANNOT CONNECT WITH OTHER MODEM
You
can input instructions below to enter the mode "MODEM interface
configuration" in "overall situation configuration" mode.
instruction |
purpose |
interface async <slot>/<port> |
Configure
MODEM interface |
for
an example:
router_
config #interface async2/0
MODEM interface is a asynchronous port which connects to another
MODEM. See configuring asynchronous port and dialing configuration for its
configuration.
Note: To configure MODEM interface speed, interactivemode and flow
control are invalid. Users need to configure AT Command to implement that.
Example:
router_config#interface async2/0
router_config_a2/0#line
dial (modeminterface只能在拨号mode下收发数据)
router_config_a2/0#line dial (modeminterface receives and sends data only under dial mode)
router_config_a2/0#ip add 10.1.1.1 255.255.255.0
router_config_a2/0#dialer
string 50800666
how to connect to v.92 MODEM and the MODEM which does not support V.42bis
Because
MODEM chips only support V.90protocol, when connecting MODEMs with V.92, it may
not be able to dial to V.92MODEM, but V.92MODEM can dial to V.90 MODEM. Users
can write an original script and add “AT&H4 OK” in the line to adjust
the mode to V.32bis multimode and MODEM may dial to V.92MODEM now. If the MODEM
is unable to dial other older version MODEM, users may adjust the mode as well.
In addition, if the MODEM on the other end does not support V.42 bis compression
protocol, users may add “AT%C0 OK” in the script line to close compression
funtion. Network mode and Command types are as follows:
AT
Command |
Network
mode |
AT
Command |
Flow
control |
AT&H0
|
V.92
multimode |
AT&K0
|
Bi-directional
no flow control |
AT&H1
|
V.90/V.34
|
AT&K2
|
CTS
flow control (Default) |
AT&H2
|
V.34
multimode |
AT&K3
|
RTS/CTS
flow control |
AT&H3
|
V.34
only |
AT&K4
|
Bi-directional
soft flow control |
AT&H4
|
V.32bis
multimode |
ATCommand
|
country |
AT&H5
|
V.32bis
only |
AT*Y162K=86
|
china
|
AT&H6
|
V.22bis
|
AT*Y162K=1
|
America、canada |
AT&H7
|
V.22
|
AT
Command |
Adjust
speed (V90) |
AT&H8
|
Bell
212 |
AT&L4
|
32000bps
|
AT&H9
|
Bell
103 |
AT&L13
|
44000bps
|
AT&H10
|
V.21
|
AT&L19
|
52000bps
|
AT&H12
|
V.23
|
AT&L22
|
56000bps
|
Example:
router_config#chat
V92 ABORT ERROR "" AT OK ATE0S0=1 OK AT&C1&D2&S0&H4 OK
router_config#chat V92 ABORT ERROR "" AT OK ATE0S0=1 OK AT&C1&D2&S0&H4 OK
(script
communicating with V92modem)
router_config#chat
no_V42bis ABORT ERROR "" AT OK ATE0S0=1 OK AT&C1&D2&S0 OK
AT%C0 OK
(script communicating with modem that does not support V42bis)
router_config#chat V92_no_V42bis ABORT ERROR "" AT OK ATE0S0=1 OK AT&C1&D2&S0&H4 OK AT%C0 OK
(script communicating with modems with the above situations)
router_config#line tty #
(# is the vty number of the modem, ranging from 1-64. Users may view this with show line)
router_config_line#script reset ###
(### is the
script name configured for V92, no_V42bis and V92_no_v42bis)
SOLVE THE PROBLEM THAT AM CARD CANNOT CONNECT WITH OTHER MODEM
<1>phenomena:LED CD doesn't shine.LED CD shine,but the port protocol isn't up.
means: add AT&H?(? is the number from 0 to 12,which means different network mode).First configure AM for V.90/v.34 mode(AT&H1),then AT&H2,AT&H3,AT&H4 and AT&H5.
<2>If the opponent MODEM doesn't support V.42bis compression protocol, you should close data compression fuction with adding AT%C0 to reset script.Then do as <1> until AM can connect with other modem.
<3>Becasue the highest protocol for 2 MODEM connection is V.34 ,we suggest you change reset script to "ABORT ERROR "" AT OK ATE0S0=1 OK AT&C1&D2&S0&H2 OK".
This
part will introduce how to configure logic interface, include:
· configure null interface(null interface)
·
configure
loopback interface(loopback interface)
· configure dialer interface(dialer interface)
· configure Virtual template and Virtual access interfaces
· configure Multilink interface
Software
supports a null interface. It is like a null equipment applied to mass operation
systems.
It will be in effect ,but will not transmit and receive data.
A
only instruction “no
ip unreachable” can be used on null interface. Null interface provide a
optional way to filter communication, you can route a unexpected communication
to null interface to avoid inordinate uses to visiting control listings.
You
can appoint null interface through instructions below in "overall situation
configuration" mode.
instruction |
purpose |
interface
null
0 |
Enter
“null
interface configuration” mode |
ip route 192.168.20.0 255.255.255.0 null 0
Null
interface can be used as a parameter to any instruction used interface types.
For an example: to configure a null interface to IP route “192.168.20.0”.
ip
route 192.168.20.0 255.255.255.0 null 0
Loopback
interface is a logic interface, it will be in effect for always, and permit BGP
session to run always even shutting off interface to out. You can use a loopback
interface as a terminal address , that can be used to BGP sessions and etc. .
When
other router tries to access this loopback , you should configure a dynamic
route protocol to spread route including loopback interface address.
Message
routed to loopback interface is routed back again to router and disposed in
local; and the message whose target ip-address is not ip-address of loopback
will be deleted. That is to say that loopback interface is still used as a null
interface.
To
appoint a loopback interface , enter the mode " interface
configuration" ,use following instructions in "overall situation
configuration" mode.
instrution |
purpose |
interface
loopback number |
Enter
to loopback interface configuration mode |
Interface
dialer is a logic interface , it can configure public dial configurations of
multiple physical interfaces to a virtual interface, to setup a relation between
physical interfaces and a interface dialer to manage multiple interfaces at the
same time.
You
can use following instructions to configure interface dialer:
instruction |
purpose |
interface
dialer numbe |
Enter
interface dialer configuration mode |
dialer
rotary-group number |
setup
a relation between physical interfaces and a interface dialer |
configure Virtual template and Virtual access
Virtual
template and virtual access are used together. Virtual access is dynamic created
depend on protocol need, its configuration information derives from
configurations of virtual template . Virtual template and virtual access are
often used in special conditions as protocol transition (PPP over X.25,
Multilink PPP and etc.).
You can define Virtual template use following instruction:
instruction |
purpose |
Interface
virtual-template number |
Configure
virtual template |
Mulitlink is a interface defined for Multilink PPP. This
interface is usually used to serial interface Multilink PPP.
You can define multilink interface through following
instructions:
instruction |
purpose |
Interface
multilink number |
Configure multilink interface |
Tunnel interface is defined for some encapsulation
protocols. Current version support GRE/IP
encapsulation protocol.
You
can input instructions below to enter the mode " interface
configuration" to appoint a Tunnel interface in "overall situation
configuration" mode.
instruction |
purpose |
Interface
Tunnel number |
Configure
Tunnel interface |
examples of interface configurations
This part include:
l
an
example of high speed interface configurations
l
an example
of low speed interface configurations
l an example of ethernet interface configurations
an
example of high speed interface configurations
An
example to introduce how to begin to configure on a serial interface. It appoint
interface1/0 PPP ancapsulation.
interface
serial 1/0
encapsulation
ppp
an
example of low speed interface configurations
An
example to introduce how to change synchronization to asynchronism on low speed
serial interface:
interface
serial 1/0
physical-layer
mode async
An
example to introduce how to change asynchronism to synchronization on low speed
serial interface:
interface
serial 1/0
physical-layer
mode sync
or
interface
serial 1/0
no
physical-layer mode
an
typical example of asychronism serial interface configuration:
interface
serial 1/0
(note: if it is a 16 asynchronism card ,it
is inter async 0/0)
physical-layer mode async
ip address 192.168.1.1 255.255.255.0
encapsualtion ppp
an typical example of synchronization serial
interface configuration:
interface serial 1/0
physical-layer mode sync
ip address 192.168.1.2 255.255.255.0
no shutdown
an example Ethernet sub-interface configurations
ROUTER A configurations:
int f0/0.1
encapsulation dot1q 1
ip address 192.168.20.11 255.255.255.0
ROUTER B configurations:
int f0/0.1
encapsulation dot1q 2
ip address 192.168.20.22 255.255.255.0
ROUTER C configurations:
int f0/0.1
encapsulation dot1q 1
ip address 192.168.20.33 255.255.255.0
ROUTER D configurations:
int f0/0.1
encapsulation dot1q 2
ip address 192.168.20.44 255.255.255.0
In such a configuration, A can only ping to C ;B can only ping to D.
an
example of DTU interface configurations
an configuration on Router 2630: Router 2630 connects DDN through DTU interface.
router_ config #interface bm2/0
router_
config bm2/0#linemode nt
//NT mode(default)
router_ config bm2/0#ratemode A //normal Rate mode(default)
router_ config bm2/0# physical-layer speed 64000 //interface speed 64k
router_
config bm2/0# ip add 192.168.21.3 255.255.255.0