1. Home
    2. /
  2. Manuals
    3. /
  3. Allied-Telesis
    4. /
  4. AT-iMG624A
    5. /
  5. 155
Page 771 / 998 Scroll up to view Page 766 - 770
ADSL upload interface
Overview
8-1
iMG/RG Software Reference Manual (ADSL Port)
8. ADSL Port
8.1
Overview
8.1.1
ADSL upload interface
The Allied Telesis Gateway product provide an ADSL
access to WAN Network, this interface is commonly
called upload interface. This chapter will describe the interaction between the ADSL physical port
a1
and the
TCP/IP stack of the system using different kind of transport layer.
8.1.2
Documentation Structure
After a brief description of the ADSL module and its interaction with other modules of the system all the CLI
(command line interface) commands will be described to allow a correct configuration of all the parameters
available configuring
an ADSL Allied Media Gateway product.
We will start from a description of the physical ADSL port a1 and its parameters and all possible setting in
accord with any DSLAM access device. Then, following the main indication of network topology after some
example of configuration there will be a complete and exhaustive description of all CLI command available on
Allied Telesis Media Gateway.
Page 772 / 998
ADSL System description
Overview
iMG/RG Software Reference Manual (ADSL Port)
8-2
8.2
ADSL System description
8.2.1
Overview
FIGURE 8-1
ADSL upload interface module
The ADSL port of a Media Gateway can be connected both to an Ethernet DSLAM or to an ATM DSLAM,
observing
the figure the connection between the ADSL port and the TCP/IP stack would be done via rfc1483
encapsulation transport in case of an Ethernet DSLAM while will be done using a Point to Point Protocol trans-
port in case of a connection to an ATM DSLAM.
8.2.2
ADSL connection via RFC1483 bridged mode
In order to allow the management of the VLAN directly from the Allied Media Gateway using only one ADSL
PVC (permanent virtual circuit)
it is possible to set up an RFC1483 transport attached to the ATI Bridge mod-
ule; ATI Bridge module provides support for virtual VLAN creating a domain, one for each VLAN, in which
RFC1483 bridged transport can carry on frames tagged for each different domain on the Bridge that will corre-
spond to different
VLAN the Bridge module provide also standard interfaces for attachment to the system
IP INT
ip0
TRANSPORT
t1
(Type=
Ethernet
)
TRANSPORT
pvc_0_35
(Type=
RFC1483
)
BUN PORT
a1
ADSL physical port
TRANSPORT
pvc_1_38
(Type=
RFC1483
)
BUN PORT
a1
IP INT
ip_pvc_1_38
ADSL physical port
TRANSPORT
ppoa_transport
(Type=
PPP
)
BUN PORT
a1
IP INT
ip_ppoa
ADSL physical port
on ATM DSLAM
qinterface
BRIDGE
IP STACK
BRIDGE IF pvc_0_35_if
Page 773 / 998
ADSL connection via RFC1483 bridged mode
ADSL System description
8-3
iMG/RG Software Reference Manual (ADSL Port)
TCP/IP Stack allowing the termination of IP frames belonging to a specific VLAN to a well defined IP interface
(see proper chapter of this manual for further information about ATI Bridge module).
Example
#Typical set up for ADSL B and ADSL C group of devices
#Create a vlan with vid 666 and name vlan666
-->vlan create vlan666 666
#Create rfc1483 transport with VPI/VCI: 1/34
-->rfc1483 add transport pvc_1_34 a1 1 34
#Create a bridge interface
-->bridge add interface pvc_1_34_if
#Attach the bridge interface to the bridge
-->bridge attach pvc_1_34_if pvc_1_34
#Put the interface in the correct vlan on the bridge
-->bridge add vlaninterface vlan666 untagged pvc_1_34_if
#Create IP interface
-->ip add interface ip666
#Attach rfc1483 transport to the defined IP interface
-->ip attach ip666 vlan666
#Set a static IP address on the IP interface
-->ip set interface ip666 ipaddress 192.168.99.1 255.255.255.0
See also
vlan (chapter 2-Layer 2 functions)
rfc1483 (chapter 7-ADSL Port)
bridge (chapter 7-ADSL Port)
ip (chapter 2-Layer 2 functions)
Example
#Typical set up for ADSL A group of devices
#Create a vlan with vid 666 and name vlan666
-->vlan add vlan666 vid 666
#Add ethernet transport type named vlan666
-->ethernet add transport vlan666
#Create rfc1483 transport with VPI/VCI: 1/34
-->rfc1483 add transport pvc_1_34 a1 1 34
# set transport to manage frame untagged on vlan666
-->rfc1483 set transport pvc_1_34 vlan vlan666 frame untagged
#Create BRIDGE interface and attach to the transport
bridge
add interface pvc_1_34_if
bridge
attach pvc_1_34_if pvc_1_34
#Create IP interface
-->ip add interface ip666
#Attach rfc1483 transport to the defined IP interface
-->ip attach ip666 vlan666
Page 774 / 998
ADSL System description
ADSL connection via RFC1483 routed mode
iMG/RG Software Reference Manual (ADSL Port)
8-4
#Set a static IP address on the IP interface
-->ip set interface ip666 ipaddress 192.168.99.1 255.255.255.0
See also
vlan (chapter 2-Layer 2 functions)
ethernet (chapter 7-ADSL Port)
rfc1483 (chapter 7-ADSL Port)
bridge (chapter 7-ADSL Port)
ip (chapter 2-Layer 2 functions)
8.2.3
ADSL connection via RFC1483 routed mode
When it is not necessary to make ATI media gateway manage virtual vlans but it is preferable to leave the
Ethernet DSLAM manages directly one or more IP interfaces on different ADSL permanent virtual circuit then
the connection between the physical adsl port and the TCP/IP stack will be done using directly a transport of
type
RFC1483 since not using ATI Bridge it will be routed directly to the ADSL port
This approach let the Ethernet DSLAM to manage a multiple ADSL PVC connection and multiple vlan network.
Example
#Typical set up for all ADSL group of devices
#Create rfc1483 transport with VPI/VCI: 1/34
-->rfc1483 add transport pvc_1_34 a1 1 34
#Create IP interface
-->ip add interface ip666
#Attach rfc1483 transport to the defined IP interface
-->ip attach ip666 pvc_1_34
#Set a static IP address on the IP interface
-->ip set interface ip666 ipaddress 192.168.99.1 255.255.255.0
See also
rfc1483 (chapter 7-ADSL Port)
ip (chapter 2-Layer 2 functions)
8.2.4
ADSL connection via Point to Point Protocol over ATM (PPPOA)
To maintain the compatibility with old type of network topography it is possible to set up a connection
between Allied Telesis media gateway TCP/IP stack and an ATM DSLAM using a Point to Point Protocol con-
nection transport over ATM cells.
Example
#Typical set up for all ADSL group of devices
#Create PPPoA transport with VPI/VCI: 8/35
-->pppoa add transport trpppoa dialout pvc 2 a1 8 35
#Create IP interface
-->ip add interface ip_pppoa
#Attach PPPoA transport to the defined IP interface
-->ip attach ip_pppoa trpppoa
# Set PPPoA account parameters
-->pppoa set transport trpppoa username <username>
Page 775 / 998
Port a1 command reference
Port a1
8-5
iMG/RG Software Reference Manual (ADSL Port)
-->pppoa set transport trpppoa password <password>
-->pppoa set transport trpppoa welogin auto
-->pppoa set transport trpppoa headers llc enabled
-->pppoa set transport trpppoa enable
See also
rfc1483 (chapter 7-ADSL Port)
pppoa (chapter 7-ADSL Port)
ip (chapter 2-Layer 2 functions)
8.3
Port a1
The following chapter describes all the ADSL port available parameters. Note the ADSL port is physically iden-
tified in the system with the name
a1
.
Under the Port command section it’s also possible display other ports (ethernet0, bunbridge, tel1 tel2, etc).
Some of these ports are real physical ports while others are virtual ports used by software modules as logical
ports.
Only ADSL a1 port is described in this section.
8.3.1
Port a1 command reference
8.3.1.1 Port a1 CLI commands
This chapter describes the
Port a1
commands provided by the CLI:
8.3.1.1.1 PORT LIST
Syntax
PORT LIST ? | <port class>
Description
The
PORT LIST ?
command lists all possible types of port and their port classes.
THE
PORT LIST
<port class> command allows you to display the port names that belong to
a specific class.
TABLE 8-1
Port a1 Commands
Functions
Fiber
A
Fiber
B
Fiber
C
Fiber
D
Fiber
E
Modular
ADSL
A
ADSL
B
ADSL
C
PORT LIST
X
X
X
PORT A1 SET
X
X
X
PORT A1 SHOW
X
X
X
PORT A1 STATUS
X
X
X

Rate

4 / 5 based on 3 votes.

Popular Allied-Telesis Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top