Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Intern
et
ISDN
DSL
Plug-i
r
Powe
Ethern
WLAN
et
Thomson Gateway
ATM Quality of Service
Configuration Guide
Copyright
Copyright 1999-2008 THOMSON. All rights reserved.
Distribution and copying of this document, use and communication of its contents is not permitted without written authorization
from THOMSON. The content of this document is furnished for informational use only, may be subject to change without notice,
and should not be construed as a commitment by THOMSON. THOMSON assumes no responsibility or liability for any errors or
inaccuracies that may appear in this document.
Thomson Telecom Belgium
Prins Boudewijnlaan, 47
B-2650 Edegem
Belgium
http://www.thomson-broadband.com
Trademarks
The following trademarks may be used in this document:
Bluetooth word mark and logos are owned by the Bluetooth SIG, Inc.
Wi-Fi, WMM and the Wi-Fi logo are registered trademarks of the Wi-Fi Alliance. "Wi-Fi CERTIFIED", "Wi-Fi ZONE",
"Wi-Fi Protected Access", "Wi-Fi Multimedia", "Wi-Fi Protected Setup", WPA", WPA2" and their respective logos of the WiFi Alliance.
Microsoft, MS-DOS, Windows, Windows NT and Windows Vista are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries.
Apple and Mac OS are registered trademarks of Apple Computer, Incorporated, registered in the United States and
other countries.
Adobe, the Adobe logo, Acrobat and Acrobat Reader are trademarks or registered trademarks of Adobe Systems, Incorporated, registered in the United States and/or other countries.
Other brands and product names may be trademarks or registered trademarks of their respective holders.
Document Information
Status: v1.0 (April 2008)
Reference: E-DOC-CTC-20080307-0002
Short Title: ATM Quality of Service Configuration Guide R7.4 and higher
Contents
1.1
Basic Concepts................................................................................................ 4
1.2
2.1
2.2
2.2.1
2.2.2
2.2.3
ILMI ........................................................................................................................................................ 16
2.3
2.4
3.1
3.2
Example: Real-time Multimedia Data and Label Based Routing with ToS-byte
Marking ......................................................................................................... 25
3.3
3.4
E-DOC-CTC-20080307-0002 v1.0
Contents
ii
E-DOC-CTC-20080307-0002 v1.0
A caution warns you about potential problems or specific precautions that need to be taken.
Applicability
This Configuration Guide applies to all Thomson Gateway Software Release R5.4 and higher and higher.
Typographical Conventions
Following typographical convention is used throughout this manual:
Sample text indicates a GUI element (commands on menus and buttons, dialog box elements, file
names, paths and folders).
Example: On the File menu, click Open to open a file.
E-DOC-CTC-20080307-0002 v1.0
E-DOC-CTC-20080307-0002 v1.0
General Overview
General Overview
Introduction
This chapter provides a technical overview of Quality of Service in general. Some basic concepts are briefly
touched, followed by a more detailed introduction to ATM Quality of Service principles and mechanisms.
E-DOC-CTC-20080307-0002 v1.0
General Overview
1.1
Basic Concepts
E-DOC-CTC-20080307-0002 v1.0
General Overview
Shaping
To prevent data being discarded in the network by policing, it is in the originator of the datas interest to make
sure that the data sent is conform the connection parameters (again in case of guaranteed QoS). This may
involve changing data characteristics and is called shaping.
Control Plane
Service Level agreements or QoS connection parameters may be signalled via a control protocol. Examples
for ATM are Switched Virtual Circuits (SVCs) and Integrated Local Management Interface (ILMI). Example on
IP level is the Resource Reservation Protocol (RSVP).
A control plane is very important for each QoS mechanism application. It addresses both the configuration of
the Service Level Agreement across the network and prevents end users from using QoS guarantees or CoS
classes that are not part of the SLA.
QoS control planes are most commonly used for guaranteed QoS, but can also be applied to relative QoS.
E-DOC-CTC-20080307-0002 v1.0
General Overview
1.2
QoS Categories
This section presents a brief introduction to ATM Quality of Service, with focus on the QoS service categories
that are most applicable to the Thomson Gateway and its functionality. Other ATM service categories may be
implemented in future Thomson Gateway products.
ATM is commonly used in the DSL access network because it is perfectly suited for the QoS requirements
mentioned in 1.1 Basic Concepts on page 4.
ATM has following benefits:
Suitable for data that is both sensitive and insensitive to delay and/or data loss
Peak Cell Rate (PCR): maximum number of ATM cells per second that may be sent on the connection.
Sustainable Cell Rate (SCR): average number of ATM cells per second that may be sent on the
connection.
Maximum Burst Size (MBS): Maximum number of ATM cells per second that may be sent in a burst, and
thus exceeding the average number of cells (SCR) up to the maximum number of cells (PCR) for a limited
number of ATM cells defined by MBS.
Cell Delay Variation Tolerance (CDVT): defines the tolerated variation in ATM cell delay (e.g. due to the
occurrence of cell multiplexing). May be explicitly or implicitly defined by the network.
Cell Loss Ratio (CLR): Number of lost cells with regard to the total number of transmitted cells. This is an
objective for the entire network.
Maximum Cell Transfer Delay (maxCTD): defines the maximum delay an ATM cell may experience during
transfer throughout the ATM network. Cells that are delayed beyond the maxCTD value are considered of
less importance. This parameter is mainly used to characterize real-time connections.
E-DOC-CTC-20080307-0002 v1.0
General Overview
Constant Bit Rate (CBR): real-time connection with a specified amount of guaranteed bandwidth (PCR)
that is continuously available during the connection life-time. The maximum cell delay is characterized by
maxCTD as illustrated below. CBR is typically used for interactive video and/or audio distribution and/or
retrieval.
bps
NON-CONFORMING
PCR
GUARANTEED
maxCTD
Time
Real-Time Variable Bit Rate (VBR-rt): similar as CBR intended for real-time applications with constrained
delay and delay variation values, but which can benefit from variable bit-rates. The average guaranteed
bandwidth is SCR, but data up to PCR may be sent for a limited amount of data specified by MBS. A VBRrt connection is characterized by PCR, SCR, MBS, and maxCTD parameters, as illustrated below. Typically
used for real-time traffic with a burst-characteristic.
bps
PCR
NON-CONFORMING
SCR
GUARANTEED
maxCTD
Time
MBS
Non-Real-Time Variable Bit Rate (VBR-nrt): intended for non-real-time applications that have bursty
traffic characteristics and no strict transfer delay requirements but which require an amount of
guaranteed bandwidth. A VBR-nrt connection is characterized by an average guaranteed bandwidth
(SCR) up to a maximum guaranteed bandwidth (PCR) for a burst with specified maximum size (MBS) as
illustrated in the figure below. VBR-nrt is typically used for bursty data transfer, banking transactions,
ERP,
bps
PCR
NON-CONFORMING
SCR
GUARANTEED
Time
MBS
E-DOC-CTC-20080307-0002 v1.0
General Overview
Unspecified Bit Rate (UBR): intended for non-real-time applications that require no guaranteed
bandwidth. A UBR connection is characterized by a maximum available bandwidth (PCR), as illustrated in
the figure below. All UBR traffic is non-guaranteed, and may be tagged/discarded or experience variable
delay throughout the network. UBR is the most common used service class/category and used for text/
data/image transfer and non-critical applications.
bps
PCR
NON-CONFORMING
NON-GUARANTEED
Time
It is important to be aware of the notion of guaranteed bandwidth and non-guaranteed bandwidth. The
figures that illustrate the service categories clearly show which part of the bandwidth is guaranteed and
which part isnt. Important is that the entire ATM network commits to delivery of data traffic up till the
guaranteed bandwidth. Non-guaranteed bandwidth is best-effort, and is unpredictable in availability
and transfer delay.
Shaping
Obviously, the source of the ATM data benefits from sending data that is conform the service category. Data
that is non-conforming may be discarded, which will probably result in retransmission of data and an overall
reduced quality of service. Most sources of ATM data (and other network elements) will use shaping to adjust
the data traffic characteristics to the specified connection parameters. Shaping is achieved by queuing data
and limiting the upstream data rate to the PCR (for UBR and CBR) or SCR up to PCR (for VBR-rt and VBR-nrt),
and limiting the burst length to MBS (for VBR-rt and VBR-nrt) if necessary.
E-DOC-CTC-20080307-0002 v1.0
Overview
The Thomson Gateway supports ATM Quality of Service in combination with an extensive way of forwarding
data via a certain ATM connection with corresponding QoS configuration.
E-DOC-CTC-20080307-0002 v1.0
2.1
QoS Category
Specified
Parameter
Characteristics
UBR
PCR
Non-real-time, non-guaranteed
bandwidth.
Non-critical data
e.g. http, ftp, e-mail.
VBR-nrt
PCR
Real-time streaming
multimedia with variable data
rate.
Real-time streaming
multimedia.
e.g. video distribution, audio
distribution, voice,
SCR
MBS
VBR-rt
PCR
SCR
MBS
CBR
10
PCR
E-DOC-CTC-20080307-0002 v1.0
Shaping
All terminated ATM connections are shaped to the ATM QoS category connection parameters. Even in case of
UBR connections with the PCR parameter set to line rate, after segmentation into ATM cells each connection
is shaped to the line rate of that moment.
Shaping is done in hardware according to the connection parameters:
Shaped user ATM cells are sent to the ATM switch with the ATM CLP flag set to 0 (indicating normal priority).
E-DOC-CTC-20080307-0002 v1.0
11
2.2
12
The definition of the RX connection traffic descriptor (ctd). This contains the ATM QoS parameters for the
down stream traffic. (See ATM QoS parameters on page 16)
The definition of the TX connection traffic descriptor (ctd). This contains the ATM QoS parameters for the
down stream traffic. (See ATM QoS parameters on page 16)
E-DOC-CTC-20080307-0002 v1.0
2.2.1
Introduction
All ATM QoS categories and their connection parameters are organized and configurable in the Thomson
Gateway QoSbook. This QoSbook allows creation of profiles that at a later stage can be linked to VP/VC
connections.
The QoSbook is configurable via the Command Line Interface (CLI).
Parameter
Value or Unit
Comment
Name
Entry name
Conformance
Peakrate
In kb/s or cps
Sustrate
In kb/s or cps
Maxburst
In bytes or cells
realtime
Enabled / Disabled
Conformance definition.
The ATM QoSbook config format parameter applies to all ATM QoSbook entries. Only one format
can be chosen. If the QoSbook config format parameter is changed, the QoSbook parameters
already configured will automatically be converted by the Thomson Gateway.
Assuming the unit is configured as cells per second, the following steps are needed to create a new QoSbook
profile for a VBR-rt ATM QoS category.
1
E-DOC-CTC-20080307-0002 v1.0
13
Create a QoSbook entry using the ctd entries we have just created:
=>:atm qosbook add
name = vbr1-rt
[txctd] = vbr1-rt-tx
[rxctd] = vbr1-rt-rx
If the maximum burst size unit is bytes, this burst size (without AAL5 and ATM encapsulation) is
recalculated into the corresponding MBS in ATM cells. Note that this may result in a different
burstsize being displayed because of the recalculation into a multiple of ATM cell payload (48
bytes).
Entering 0 as PCR is interpreted as PCR shaping to the available DSL bandwidth (called line rate). If
the DSL line is at this stage not yet initialized, 800kb/s is chosen as default for ADSL but adjusted to
the actual value as soon as the line initialization takes place. Note that linerate shaping is only useful
for UBR, and should not be applied for VBR-nrt, VBR-rt or CBR.
14
E-DOC-CTC-20080307-0002 v1.0
2.2.2
E-DOC-CTC-20080307-0002 v1.0
15
2.2.3
ILMI
ILMI Principles
ILMI uses a dedicated ATM VPI/VCI 0/16 channel to configure the ATM Connection parameters on the
Thomson Gateway. The protocol used is SNMP encapsulated in AAL5.
Via SNMP trap commands, the remote site (for example a DSLAM) can notify the Thomson Gateway of
changed ATM connection parameters. The Thomson Gateway will issue SNMP get commands to retrieve
all parameters and update the ATM Interface Management Information Base (MIB). This ATM Interface MIB
contains ATM VP/VC configuration including the ATM QoS category and QoS connection parameters.
MIBs supported by the Thomson Gateway are:
Upon ATM Connection parameter configuration via ILMI, the Thomson Gateway will automatically create
phonebook entries and/or ATM QoSbook profiles.
Connections already using these phonebook entries (PPPoA, PPPoE, IPoA, Routed Ethernet) will be updated
with references to the applicable new ILMI QoSbook entries if configured as ILMI PVC type. In case no
connections are using the dynamic phonebook entries, bridge or PPPoE connection will be created and
bound to these phonebook entries.
Overall, connection parameters configured via ILMI will result in proper shaping, QoS category queuing and
scheduling.
The Thomson Gateway is compliant with the standards defined by DSL-Forum in TR-37 and TR-62.
Configuring ILMI
Two ILMI modes are configurable via the CLI
Active: enable both ILMI (VP/VC 0/16) and pseudo-ILMI (VP/VC 15/16). When connection parameters are
written to the MIB, use these parameters to configure phonebook entries, QoSbook profiles and bind
bridge or PPPoE interfaces on top.
Passive: enable both ILMI (VP/VC 0/16) and pseudo-ILMI (VP/VC 15/16). When connection parameters are
written to the MIB, display this information on CLI or web interface but do not use these parameters for
configuration.
For a PVC connection that is automatically configured via ILMI, the type of interface that will be bound (if no
other interfaces are already bound) to this PVC can be configured. Execute the following command to select
the type of interface to be bound to the ILMI PVC:
:autopvc config type=pppoe
16
E-DOC-CTC-20080307-0002 v1.0
Thomson Gateway gateways and routers also support overruling the ILMI UBR PVC PCR connection
parameter with a configurable PCR value. This allows for example configuring the UBR PCR to the line rate of
the DSL connection. Indeed, for UBR connections without explicit PCR configuration (because the network
might do policing or UBR connections), the PCR can be configured to use any available DSL bandwidth.
To configure the overwriting of the ILMI PVC PCR in case of UBR connections, proceed as follows:
1
E-DOC-CTC-20080307-0002 v1.0
17
2.3
Introduction
ATM QoS is specified on a VP/VC level. This means that data will experience Quality of Service depending on
the ATM VP/VC it is forwarded on.
Forwarding is in this context a generic term covering the decision over which ATM VP/VC a frame or packet is
to be sent, and not only referring to IP forwarding.
Bridged connections
For bridge connections, the transparent self-learning bridge learns which MAC addresses are reachable via
which bridge ports (and connections). This way, any Ethernet node will be reached via the ATM connection
on which the ARP reply was received.
Routed connections
For routed connections (IPoA, Routed Ethernet, PPPoA, PPPoE), destination IP address routing can be used to
determine the IP gateway and corresponding IP interface and ATM VC to forward to. If the destination
networks differ or a proxy server is used for a particular service, destination IP address routing allows
configuring static destination routes (gateway routes or interface routes) or dynamic routes (injected into the
routing table when the PPP connection is up.
For routed connections (IPoA, Routed Ethernet, PPPoA, PPPoE), classification-based routing can be used to
determine the IP gateway and corresponding IP interface and ATM VC to forward to. IP packets are classified
by classification rules and can be forwarded based upon this classification. Classification criteria include
source and destination IP address (or range), source and destination port (or range), protocol number, DSCP
and more.
For PPTP-to-PPP Relay connections, a number of PPTP profiles can be created via the CLI. Each PPTP profile
has a corresponding QoSbook profile configured upon creation. ATM VC and PPTP profile are selected via
two dial strings (entered by the PPTP or VPN client typically on the host). The first dial string determines the
destination phonebook entry (ATM VP/VC), the second dial string determines the PPTP profile (and
corresponding QoSBook profile) to be used.
Network Address Translation (NAT) can have an impact on the forwarding of downstream incoming
packets from the WAN. Via static NAT entries or configuration of a NAT default server, the
destination address translation for incoming packets from the WAN can determine the forwarding
entry that will be used for these packets.
For more information, see to the The Thomson Gateway and Hyper-NAT Application Note.
The remainder of this chapter presents a brief overview of IP packet classification and classification based IP
forwarding features of the Thomson Gateway. For more detailed information please refer to the Thomson
Gateway CLI Reference Guide.
18
E-DOC-CTC-20080307-0002 v1.0
2.4
Summary / Overview
QoS features
As a summary, this chapter provides a brief overview of the Thomson Gateway QoS features.
Upstream PCR (UBR, CBR) and PCR/SCR/MBS (VBR-nrt and VBR-rt) shaping per VC.
Connection Admission Control (CAC) using statistical multiplexing to guarantee bandwidth. Overbooking
can optionally be enabled.
Per VC queuing on frame level (for SAR) for terminated ATM connections.
ILMI 4.0 auto-configuration of ATM connection parameters (with binding to existing or new interfaces).
ILMI will consume one of the eight VP/VCs that can be used.
E-DOC-CTC-20080307-0002 v1.0
19
20
E-DOC-CTC-20080307-0002 v1.0
Introduction
This chapter presents a number of practical examples on how to use and configure Quality of Service on the
Thomson Gateway.
Configuration will typically be done via the Command Line Interface (CLI). Please refer to the Thomson
Gateway CLI Reference Guide.
E-DOC-CTC-20080307-0002 v1.0
21
3.1
Illustration
Lets considers a first practical example. Imagine a household were the DSL connection is used both for
pleasure (http, e-mail, chatting, messaging,) and professional use (home working or VPN) via two
computers. In this application scenario the data that is transferred for professional use has obviously higher
priority than the chatting data for example sent by another member of the family.
Typically the home network will be 100Base-T Ethernet, so the point at which the two types of data start
affecting each other is the DSL upstream bandwidth, which is typically limited. This example will assume an
upstream bandwidth of 128kb/s and a downstream bandwidth of 1mb/s.
Leisure PC
192.168.1.1/24
PVC 8*35
UBR
Internet
Network
192.168.1.254/24
PVC 8*36
VBR-nrt
Homeworking PC
192.168.1.2/24
Quality of Service for the high priority data can be achieved by configuring 2 ATM connections (suppose in
this case PVCs) with each a different QoS profile. The choice for the low priority data is an UBR service
category (see1.2 ATM Quality of Servicefor characteristics) and the choice for the high-priority data is a
VBR-nrt service category because of the bursty characteristics of this data.
A second ctd entry is created for the high priority profile. The required configuration parameters in this
case are: a given name, VBR service category, PCR, SCR (as example half of the bandwidth), MBS and a
real-time conformance.
22
E-DOC-CTC-20080307-0002 v1.0
Proceed as follows to assign the created ctd entries to the QoSbook profiles:
=>:atm qosbook add name=ubr txctd=ubr_1 rxctd=ubr_1
=>:atm qosbook add name=vbr_64 txctd=vbr_64 rxctd=vbr_64
The QoSbook ctdlist command gives an overview of all configured Connection Traffic Descriptors.
=>:atm qosbook ctdlist
Name
Ref Conf Peak
Sust
(cps)
(cps)
ubr_1 2 UBR linerate 0
vbr_64 0 VBR 128
64
Burst
(cells)
0
32
The QoSbook list command gives an overview of all configured QoSbook entries.
=>:atm qosbook list
Name
Ref
ubr
1
vbr_64
1
Tx CTD
ubr_1
vbr_64
Rx CTD
ubr_1
vbr_64
The Ref column in the QoSbook overview indicates the number of protocol interfaces that are actually
configured with this QoS profile. For example, typically there are a number of default connections configured
that use the default QoS profile.
E-DOC-CTC-20080307-0002 v1.0
23
The QoS profiles (QoSbook entries) are linked to these PPTP profiles. At this stage, the Thomson
Gateway is properly configured and the actual connections can be established.
Please make sure no PPP interfaces are configured with destination the relay_low and relay_high ATM
connections, otherwise these ATM connections will no longer be available for PPTP relaying.
The active PPTP relay connections and their associated Quality of Service profiles can be retrieved using the
PPTP list command.
=>:pptp list
Dialstr
Destination QoS
Encaps AC
State
User
relay_low home relay_low
UBR
vcmux never CONNECTED (192.168.1.25)
relay_high work relay_high VBR_64 vcmux never CONNECTED (192.168.1.26)
Summary
Although PPTP-to-PPP relay is not very commonly used, this example introduces configuration of ATM
Qosbook profiles. Using PPTP clients on the end user computers allows a very clear separation between
homeworking data and leisure data.
24
E-DOC-CTC-20080307-0002 v1.0
3.2
Illustration
A second practical example covers the configuration of QoS for real-time data.
Suppose a SOHO with three computers that have Internet access mainly for e-mail purposes. Besides these
three computers, one computer is a dedicated video conferencing machine running NetMeeting. All data
originated from the conference computer will have the IP header TOS-byte marked with a DiffServ Expedited
Forwarding DiffServ-Codepoint (DSCP).
PC1
192.168.1.1/24
PC2
192.168.1.2/24
8*35 UBR
Internet
Network
192.168.1.254/24
192.168.2.254/24
8*36 UBR
PC3
192.168.1.3/24
Conference
192.168.2.1/24
This example will assume an upstream bandwidth of 512Kb/s and a downstream bandwidth of 4Mb/s.
Because of the real-time characteristics and higher priority of the video-conferencing data, this data will be
sent and received on a separate ATM PVC with appropriate Quality of Service configuration.
To achieve this, assume that the video conferencing computer has a static IP address 192.168.2.1 in a
192.168.2.0/24 subnet. The other three computers have dynamic IP addresses in a 192.168.1.0/24 subnet that
are assigned by the Thomson Gateway as DHCP server.
E-DOC-CTC-20080307-0002 v1.0
25
Proceed as follows to create two ATM interfaces, one for data and one for conference:
=>:atm ifadd intf=atm_conference
=>:atm ifconfig intf=atm_conference dest=conference qos=My_CBR
encaps=llc retry=10 fcs=disabled ulp=ppp
=>:atm ifadd intf=atm_data
=>:atm ifconfig intf=atm_data dest=data qos=My_UBR encaps=llc retry=10
fcs=disabled ulp=ppp
26
E-DOC-CTC-20080307-0002 v1.0
The second PPP interface is configured as an always-on connection with UBR ATM QoS profile and NAPT
enabled. A routing entry is created to forward all other data to this interface.
Because of priority of label routes over destination routes the conference interface routing entry is
applied before the data interface entry
To create the second PPP interface proceed as follows:
=>:ppp
=>:ppp
=>:ppp
=>:nat
=>:ppp
ifadd intf=data
rtadd intf=data dst=0.0.0.0/0 src=0.0.0.0/0 metric 1
ifconfig intf=data dest=atm_data accomp=enabled user=data_user password=data_pwd
ifconfig intf=data translation=enabled
ifattach intf=data
E-DOC-CTC-20080307-0002 v1.0
27
Summary
Once this configuration has been made, the video conferencing computer can accept incoming NetMeeting
calls, and the H.323 data will always be forwarded over the connection with 256Kbps guaranteed bandwidth.
Important remark is that if no guaranteed bandwidth is in use (no active video conferencing), this bandwidth
will be available as non-guaranteed bandwidth for data from other computers.
28
E-DOC-CTC-20080307-0002 v1.0
3.3
Illustration
This practical example covers dynamic configuration of ATM VPI/VCI and ATM QoS connection parameters
via ILMI. A number of computers (this example assumes two) on the LAN retrieve an IP address from the
Thomson Gateway as DHCP server.
Because of the dynamic configuration of the ATM connection, the required configuration is limited to
attaching an embedded PPPoE client to the PPPoE relay.
Leisure PC
192.168.1.1/24
PVC 8*35
UBR
Internet
Network
192.168.1.254/24
PVC 8*36
VBR-nrt
Homeworking PC
192.168.1.2/24
The first part of this example covers the use of ILMI to retrieve the VPI/VCI of a UBR ATM connection.
A second part will continue with a description of the steps needed to enable the dynamic configuration of a
gold-service second VP/VC with CBR QoS category.
Configuring ILMI
Because of the dynamic configuration, there is no need for a ATM VP/VC or ATM Qosbook configuration on
the Thomson Gateway. Typically, a phonebook entry and a default ATM Qosbook entry may be configured.
In any case, new Qosbook entries will be added based upon the received ATM connection parameters and
will be bound to the either an existing or a new interface.
The ATM QoS configuration is in this case limited to ILMI configuration.
Execute the following command to set the AutoPVC mode to active with overwriting of the PCR with the
available DSL line-rate.
:autopvc config mode=active peakrate=0 overwrite=enabled
E-DOC-CTC-20080307-0002 v1.0
29
In case the dynamically received ATM connection VPI/VCI is not configured on the Thomson Gateway, an
automatic phonebook entry will be created. Via the AutoPVC type configuration, a new interface can be
created and bound to the phonebook entry.
Execute the following command to set the autopvc type to PPPoE relay:
=>:autopvc config type=pppoerelay
ifadd intf=pppoe1
rtadd intf=pppoe1 dst=0.0.0.0 dstmsk=0 src 0.0.0.0 srcmsk=0 metric=1
ifconfig intf=pppoe1 dest=RELAY dnsmetric=0 user=YourUsername password=YourPassword
ifconfig intf=pppoe1 translation enabled
ifattach intf=pppoe1
The interface can be configured without username and password. The user will then need to
configure username and password via the web-interface.
Connecting
After DSL synchronization, the correct VPI/VCI and connection parameters are received via ILMI. The
appropriate phonebook entry (VP/VC) and qosbook entry (QoS connection parameters) will be created. An
ETHoA interface will be added pointing to the newly created phonebook en Qosbook entries and bound to the
PPPoE Relay.
From this point on the PPPoE connection will connect to the service provider and the user (or multiple users
because of the use of X:Y NAT) is on-line.
30
E-DOC-CTC-20080307-0002 v1.0
Suppose a second embedded PPPoE interface is bound to the PPPoE Relay. This interface has a PPPoE access
concentrator and PPPoE service name configured. The PPPoE connection will only select the configured
service name to establish a PPP connection. Use classification and labels to determine which data will be
forwarded to the gold service.
ifadd intf=GoldService
rtadd intf=GoldService dst=0.0.0.0 dstmsk=0 label=MyGoldServiceData metric=1
ifconfig intf=GoldService dest=RELAY dnsmetric=0
ifconfig intf=GoldService acname="ServiceProvider"
ifconfig intf=GoldService servicename="GoldService" user=GoldUserName
ifconfig intf=GoldService password=GoldPassword
ifattach intf=GoldService
Summary
Via ILMI dynamic configuration of ATM VP/VC connections, the user only has to configure username and
password of both connections and is ready to experience Internet access and dynamic activation of a gold
service. Via the PPPoE relay or PPPoE client, the local computers can establish a connection to the Internet or
use the dynamically selected gold service when it becomes available.
E-DOC-CTC-20080307-0002 v1.0
31
3.4
Illustration
This example covers a basic SOHO configuration with one main site and a remote site. Both sites are
connected via a VBR-nrt category ATM connection, and the main site is connected to the service provider and
to the Internet via an UBR category ATM connection. This QoS application guarantees the site-to-site data
traffic and leaves HTTP data from the proxy or to the web-server best effort.
The main site has a local proxy server and a public web-server to host the SOHO website where customers
can place order or trace their project progress. Local computers can only access the Internet via the local
proxy server. There is no direct HTTP (or other) connectivity allowed from local computers to the Internet and
all incoming HTTP requests from the Internet are forwarded to the internal web-server.
This is of course a simplified example that is easily extendable with e.g. a local mail-server or an additional
UBR category ATM VC connection between the two SOHO sites for best-effort traffic (with ERP or real-time
project collaboration tools using the VBR-nrt QoS category).
Webserver
192.168.1.1/24
180.162.10.1/32
Internet
Network
BR
5U
3
8*
Proxy
192.168.1.2/24
SpeedTouch
Router 1
192.168.1.254/24
PC11
192.168.1.3/24
180.162.10.1/32
8*
36
VB
R-
nr
SpeedTouch Router 2
192.168.1.254/24
30.0.0.1/32
PC12
192.168.2.1/24
32
E-DOC-CTC-20080307-0002 v1.0
QoS parameters
The UBR QoS category ATM connection is configured with PCR equal to line-rate. The VBR-nrt QoS category
ATM connection is configured with PCR equal to
1152Kb/s, SCR equal to 576Kb/s and MBS equal to 3072bytes (64 ATM cells).
The connection towards the Internet is using an IPoA connection with a static IP address to host the web
server.
The connection between the two sites is using IPoA but can in case of a Thomson Gateway 620/605/608(WL)
be secured via IPSec.
The focus of this configuration example is on the Thomson Gateway Router 1 because this router has the
most complicated configuration. Thomson Gateway Router 2 is DHCP server in the 193.168.1.0/24 network
and has a default route pointing to the Thomson Gateway Router 1.
Proceed as follows:
=>:atm qosbook ctdadd name=VBR conformance=VBR peakrate=1152 sustrate=576 maxburst=3072
Proceed as follows to created two qosbook entries with the connection traffic descriptors:
=>:atm qosbook add name=default txctd=default rxctd=default
=>:atm qosbook add name=VBR txctd=VBR rxctd=VBR
E-DOC-CTC-20080307-0002 v1.0
33
Adding IP Routes
Two routes need to be added to the Thomson Gateway Router 1 forwarding table.
One route for the 193.168.1.0/24 network towards the remote SOHO site network.
Proceed as follows:
=>:ip rtadd dst=193.168.1.0/24 gateway=30.0.0.1
=>:ip rtadd dst=0.0.0.0/0 gateway=180.162.10.1
The source TCP port of a HTTP GET message is random, while the destination port is typically 80.
Configuring DNS
This example uses the service providers primary and secondary DNS servers for name resolution. The DNS
servers IP addresses are sent in the DHCP Offer messages by both Router 1 and Router 2 as DHCP server.
This configuration is done in the LAN IP Addressing. Suppose the following server provider DNS
configuration:
To prevent the Thomson Gateway from advertising itself as primary DNS server, stop the internal DNS server.
Execute the following command to disable the DNS server:
:dns server config state=disabled
The Thomson Gateway can be configured as local DNS server (e.g. in a LAN domain) with DNS forwarding
for unknown domains, but in typical scenarios the local computers are configured as Windows clients using
e.g. NetBIOS for name resolution or are using Apple Rendez Vous for local name and service discovery.
34
E-DOC-CTC-20080307-0002 v1.0
Summary
Connecting two SOHO sites via two Thomson Gateway Routers is a cost effective and efficient mechanism to
achieve a secure and Quality of Service based local network interconnection. Two ATM VP/VC connections
are used for a high-priority site-to-site interconnection and a best-effort connection to the Internet.
E-DOC-CTC-20080307-0002 v1.0
35
36
E-DOC-CTC-20080307-0002 v1.0
www.thomson-broadband.com
THOMSON 2008. All rights reserved.
E-DOC-CTC-20080307-0002 v1.0.