vx1000 UseGuide v11

VX1000LD
User's Guide
Disclaimer: All functions and features are subject to revision due to changes and requests applied to the
latest firmware versions released for the current product. The manual is only a reference and sample.
2002 Versa Technology, Inc.

VersaXpress VX1000LD User's Guide DOC-VXDSL-UG-1.0
Contents
1. Purpose ........................................................................................................................................ 4
1.1 Scope ........................................................................................................................................ 4
1.2 Audience ................................................................................................................................... 4
1.3 Related Documents................................................................................................................... 4
1.4 Summary of Contents ............................................................................................................... 4
2. Product Overview ........................................................................................................................ 5

2.1 ADSL Technology ..................................................................................................................... 5
2.2 Product Features....................................................................................................................... 5
2.3 Network Configurations and Protocols ..................................................................................... 6
2.3.1 PC-Attached Configurations ............................................................................................................. 6
2.3.2 Gateway Configurations ................................................................................................................... 7
2.3.2.1 Bridge Configurations................................................................................................................... 7
2.3.2.2 Router Configurations .................................................................................................................. 7
2.3.2.2.1 IP-over-ATM (IPoA)................................................................................................................ 8
2.3.2.2.2 PPP ........................................................................................................................................ 9
2.3.2.2.3 Network Address Translator (NAT) ...................................................................................... 10
2.3.2.2.4 Dynamic Host Configuration Protocol (DHCP) Server.......................................................... 12
3. Installation.................................................................................................................................. 13
3.1 Hardware Installation .............................................................................................................. 13
4. Operation and Configuration ................................................................................................... 14

4.1 Web Operation and Configuration .......................................................................................... 14
4.1.1 PC Configuration ............................................................................................................................ 14
4.1.2 PC Web Browser Configuration...................................................................................................... 16
4.1.3 Ethernet-Gateway Configuration Via the Web Interface ................................................................. 16
4.1.3.1 ADSL (WAN) Web-based Configuration..................................................................................... 16
4.1.3.2 ADSL (WAN) Web-based Status................................................................................................ 21
4.2 CLI (Command Line Interface) Operation and Configuration ................................................. 22
4.2.1 Using the Console .......................................................................................................................... 22
4.2.2 ADSL CLI-based Configuration ...................................................................................................... 22
4.2.3 Line Activation................................................................................................................................ 23
4.2.4 Protocol Configuration.................................................................................................................... 23
4.2.4.1 PC-Attached Configuration......................................................................................................... 23
4.2.4.2 Bridge Configurations................................................................................................................. 23
4.2.4.2.1 Gateway Bridge Configuration.............................................................................................. 23
4.2.4.2.2 Gateway Router Configurations ........................................................................................... 24
4.2.4.2.3 Gateway IPoA Routing ......................................................................................................... 24
5. Software Update Procedure ..................................................................................................... 26

5.1 Setting the IP Address ............................................................................................................ 26
5.2 BootP/TFTP............................................................................................................................. 26
6. Status Indicators ....................................................................................................................... 27
Appendix A BOOTP and TFTP Example Setup ............................................................................. 28
Appendix B Troubleshooting .......................................................................................................... 29

No response from console ..................................................................................................................... 29
ADSL activates, but doesnt connect...................................................................................................... 29
ADSL connects, but drops the link ......................................................................................................... 29
ADSL connects, but doesnt pass data .................................................................................................. 29
2002 Versa Technology, Inc. Page 2 of 29

List of Figures
Figure 1: Bridged Network ................................................................................................................... 7
Figure 2: Routed Network..................................................................................................................... 7
Figure 3: IPoA Protocol......................................................................................................................... 8
Figure 4: PPP Protocol.......................................................................................................................... 9
Figure 5: IP Dial-in over PPP ................................................................................................................ 9
Figure 6: NAT Protocol ....................................................................................................................... 10

1. Purpose
The purpose of this Users Guide is to explain the workings and functions of the Modular
Development System (MDS) blade combining GlobespanViratas Helium210-80 communications
processor and the GS7070 ADSL PHY. This Users Guide assists the user with operation of the
RD7312 ADSL Router.
1.1 Scope
The scope of this document is to provide the user of the reference design enough information to use
the reference design in testing and development for the users own product development. This
publication is designed for the people that will install, configure and use the ADSL router.
1.2 Audience
The intended audience is an ADSL modem/router/gateway developer who is familiar with the
configuration of GlobespanViratas ATMOS software.
1.3 Related Documents

GlobespanVirata Documents:
DO-008841-TC ISOS Software 8.1 Release Notes
DO-009286-PS BUN Devices: GS7070 ADSL PHY
DO-008045-TC BD3000 Users Guide
1.4 Summary of Contents

Following are the sections contained within this document:
Product Overview provides an overview of ADSL, networking configurations and the feature
list.
Installation describes how to install the product as either a USB modem or an Ethernet
router/bridge.
Operation provides the procedures to configure and use the ADSL router.
Software Update Procedure describes how to update the software on the ADSL router.
Connector Specifications describes all of the ADSL router connectors.

2. Product Overview
This section provides a brief description of ADSL, the feature list included with the RD7312, an overview
of the hardware components and networking configurations.
2.1 ADSL Technology

Asymmetric Digital Subscriber Line (ADSL) is a modem technology that uses existing copper twisted-
pair telephone lines to provide high speed Internet access. Compared to the older analog modem,
this technology greatly increases data transfer rates. ADSL transmits an asymmetric data stream with
a higher bandwidth rate going downstream to the subscriber than the rate going upstream to the CO.
Rates depend on the distance to the CO with the maximum downstream rate of 8Mbps and the
maximum upstream rate of 640Kbps.
2.2 Product Features

Network Configuration Modes
Gateway
PC-Attached
PC-Attached Gateway
ADSL Support
ANSI T1.413 Issue 2
ITU-T G.992.1 (G.dmt)
ITU-T G.992.2 (G.lite)
Multimode (automatic modulation detection)
Routing
IP routing from Ethernet to IPoA or PPP
Network Address Translation (NAT)
DHCP Server
10/100BaseT Ethernet Support
ATM Support
ATM Signaling UNI 3.1 & 4.0
PPP (RFC 2364) over ATM
RFC 1483
RFC 1577 (IP over ATM)
AAL0, AAL2, AAL5
ATM Service Class: UBR/VBR/CBR
32 VCs
Console Management
Web Management

2.3 Network Configurations and Protocols

There are multiple software images for the RD7312 that determine the type of network configuration.
The following network configurations are supported:
PC-Attached configurations, in which the product acts as a network interface module directly
attached to a PC via the USB or PCI bus.
Gateway configurations, where the product act as a standalone bridge/router between Ethernet
and ATM/ADSL.
In PC-Attached configurations, there is only one operational mode. In Gateway or PC-Attached
Gateway configurations, the device can operate as a bridge or router. The following sections describe
these network configurations and associated protocols.
2.3.1 PC-Attached Configurations

A modem attached to the host PC via USB behaves as a network card. It does not require any
network signaling or protocol software since the host PC (Windows 98 Second Edition or Windows
2000) performs these functions. This means that the modem does not have a TCP/IP stack, and does
not have an IP address. All of the network signaling and protocol software for the broadband network
interface also runs on the host PC (e.g. ILMI, Q.2931).
The AAL5 segmentation and reassembly sub layer (SAR) is provided by the modem. This relieves
the host PC from segmenting and reassembling the higher-level protocol packets into ATM cells.

2.3.2 Gateway Configurations

In these two types of configurations the network device can be operated as either a bridge or a
router. The examples here assume the PC is attached to the network device via an Ethernet link.
2.3.2.1 Bridge Configurations
In a typical bridged configuration, the ADSL router is transparent to the network. It bridges the ADSL
line to the Ethernet line, making both sides appear as a single subnet. In this configuration, an IP
address only needs to be provided to the PC. It may still be beneficial to provide an IP address to the
ADSL router for management.
Subnet 1 Subnet 1
Internet
ADSL
PC Modem
DSLAM
Figure 1: Bridged Network
2.3.2.2 Router Configurations
In a typical routed configuration, the ADSL router is treated as a separate device on the network that
receives packets from the PC and DSLAM. The Ethernet and ADSL networks are configured as
separate IP subnets. The PC must have the ADSL router set up as its default gateway. Descriptions
of the protocols supported in this mode of operation are discussed in the next sections.
Subnet 1 Subnet 2
Internet
ADSL
PC Modem
DSLAM
Figure 2: Routed Network

2.3.2.2.1 IP-over-ATM (IPoA)

Support is provided for IP-over-ATM as defined in RFC 1577, using either PVCs or SVCs (with the
signaling specified in RFC 1755). None of the subsequent extensions (e.g. MARS and NHRP) are
supported. Only one IPoA device is supported, unless all are configured to use PVCs.
The following diagram shows where IPoA is positioned in the modems protocol software stack:
IP router
S
N bridge PPP
M IPoA
P
ATM
Ethernet Forum signalling
driver LANE
sscop
ATM driver
kernel
Figure 3: IPoA Protocol
LLC/SNAP encapsulation (RFC 1483) is always used.

When using PVCs, the TCP/IP stack can either be configured with the IP address of each PVC or use
inverse ATMARP (RFC 1293 and RFC 1577) to determine the address (the former is more reliable,
but the latter is more flexible). It will always respond to ATMARP and inverse ATMARP requests
appropriately.
The IPoA MTU (maximum transmission unit) is by default 1500 (the same as Ethernet) instead of the
standard 9180.

2.3.2.2.2 PPP
PPP is a widely used protocol for controlling a point-to-point link. It is used by existing ISPs (Internet
Service Providers) in providing dial-in services for the Internet. It can be used over a variety of
physical media to transport IP data, MAC data, and many other data types. Components of PPP have
been defined which provide option negotiation, compression, encryption, authentication and multi-link
facilities. For xDSL deployment, authentication is probably the single most important of these.
PPP operates over either SVCs or PVCs over the ATM WAN (PPPoA).
Protocol Architecture
The general position of the software within the protocol stack is as follows where ATM is used as its
transport and PPP provides transport to the IP stack.
IP router
S
N bridge IPoA PPP
M
P
ATM
driver LANE
sscop
ATM driver
kernel
Figure 4: PPP Protocol
IP Dial-in over PPP

A site with its own IP subnet dials in over PPP to a service provider. The service provider dynamically
allocates an IP address for the link itself, using IPCP address allocation.
IP router
PPP process
CHAP IPCP Ethernet
LCP
ATM driver
IP over PPP over ATM

VC
Figure 5: IP Dial-in over PPP
The PPP process sits between the IP router and the ATM driver. LCP, IPCP and CHAP are
components of PPP, which all operate inside the PPP process in the modem.

2.3.2.2.3 Network Address Translator (NAT)

NAT implements Network Address Port Translation (NAPT), also known as IP Masquerading. This
involves translating IP addresses in packets passing between a private local area network and a
public Internet. By using NAT the local IP addresses do not need to be administered by the service
provider. Many addresses on the local network are mapped to a single externally visible address on
the public Internet. This reduces the number of addresses that have to be visible on the Internet,
saving addresses from the global pool, as well as providing a transparent routing solution to a public
IP network and a private IP network.
NAT operates in conjunction with the IP router. The diagram below shows the arrangement of
modules in an example system where a private Ethernet network is connected to a public Internet via
PPP.
IP router
10.1.1.1 194.129.40.2
S
N bridge NAT
M
P
IPoA PPP
ATM
driver LANE
sscop
ATM driver
kernel
Figure 6: NAT Protocol
Packets originating from the private network, arriving on the Ethernet device, are passed to NAT by
the router. NAT translates the source address in the IP header to the address of the router interface.
NAT also translates the TCP/UDP source port (or the identifier field in an ICMP query) to a unique
value.
When incoming packets arrive on the PPP device, NAT is able to determine which outgoing packet
they are in response to, by examining the TCP/UDP destination port. NAT is then able to translate the
port number back to its original value, and translate the destination IP address back to the address of
the machine on the private network. The router then passes the packet to the Ethernet device driver.
Choosing the interface on which to enable NAT

When NAT is enabled on an IP router interface, all outgoing IP packets have their source address set
to the address of that interface.
Therefore, the interface connecting the router to the public Internet should have NAT enabled. The
interface connecting the router to the private local area network must not have NAT enabled.
Once NAT has been enabled on an interface, no further configuration is necessary.

Incoming connections
Normally, NAT is used in a situation where clients on the private network make outgoing connections
to servers on the public network. Since the IP addresses on the private network are not visible and
cannot be routed to or from the public network, it is not possible for a client on the public network to
originate a connection directly to a server on the private network. NAT will normally reject any
incoming packets that are not in response to a previous outgoing packet.
However, NAT can be configured to allow incoming connections. This is achieved by sending packets
destined for a specific port on the one, externally visible IP address to a new machine within the
private network. These rules can be added from the console or in a configuration file. Packets arriving
with different destination port numbers can have their destination IP addresses re-written to different
values; for example TCP packets destined for port 80 can be redirected to a web server, and TCP
packets sent to port 25 can be sent to a separate mail server.

2.3.2.2.4 Dynamic Host Configuration Protocol (DHCP) Server

The DHCP server software provided with the RD7312 can be used to assign IP address to PCs when
the RD7312 is configured as a bridge or router. In order to support this functionality, the RD7312
must have an IP address assigned to it.
The DHCP protocol allows a host, which is unknown to the network administrator, to be automatically
assigned a new IP address out of a pool of IP addresses for its network. In order for this to work, the
network administrator allocates address pools for each available subnet.
When a client requests an address using the DHCP protocol, the server allocates an address for it.
Each client is assigned a lease, which expires after an amount of time (12 hours by default). At some
time before a lease expires, the client to whom the lease is assigned is expected to renew it in order
to continue to use the address. Once a lease has expired, the client to which the leased IP address
was assigned is no longer permitted to use the leased IP address and must go back to discovering a
new IP address.
In order to keep track of leases across system reboots and server restarts, the DHCP server
maintains a list of leases in a file. Before a lease is granted to a host, it is recorded in the lease file.
The DHCP server also provides BOOTP support. Unlike DHCP, the BOOTP protocol does not
provide a protocol for recovering dynamically assigned addresses once they are no longer needed. It
is still possible to dynamically assign addresses to BOOTP clients, but some administrative process
for reclaiming addresses is required.

3. Installation
3.1 Hardware Installation

Attach power supply cable to plug on the VX1000LD.
Plug power supply cable into standard electrical socket.
Connect the RJ11 port to the DSLAM using the phone line cable.
For Ethernet operation, connect one end of the Ethernet cable to the modem and the other end to
the PC.

4. Operation and Configuration

This section describes how to configure and operate the RD7312. Note that the default settings will
allow the RD7312 to attempt to connect to a DSLAM upon power up. Additional settings are
described below.
4.1 Web Operation and Configuration

Modem status and configuration is available through a web browser. By default, this can only be
accomplished via HTTP on the modems LAN ports (Ethernet or USB). Remote access (via the WAN
- or ADSL interface) is supported, but its configuration is beyond the scope of this document.
To interface to the modems on-board web server, a PC configured with network support, running a
web browser should be attached to the modem via an Ethernet crossover cable (USB is also an
option with the USB-gateway firmware load). Note that the default IP address of the modem (as
shipped from GlobespanVirata ) is 10.0.0.1. The examples shown below are from a PC running
Windows 98 and using MS Internet Explorer.
4.1.1 PC Configuration
To interface to the modems on-board web server, a PC configured with network support, running a
web browser should be attached to the modem via an Ethernet crossover cable (USB is also an
option using the USB-gateway firmware load).
Next, assign the PC an IP address on the same subnet as the modem (for example 10.0.0.2). This is
done from the Windows Network application from the Windows Control Panel (see snap shot
below).

Next, using the gateway tab, make the modem the default gateway for the PC.
Finally, select OK and Yes to restart your computer, implementing the new selections. After this
step, the PC should be properly configured to configure the modem via the web-based interface.

4.1.2 PC Web Browser Configuration

After reboot, launch a web browser (e.g., MS Internet Explorer). To connect to the modem enter
10.0.0.1 in the address field. Details such as browser configuration are beyond the scope of this
document.
4.1.3 Ethernet-Gateway Configuration Via the Web Interface

Virtually all aspects of modem configuration and status are available through the web interface. Using
the web interface allows the user to easily adapt the modem to whatever environment is desired (e.g.,
PPP, DHCP, etc.). The four main options available with the VX1000LD are System, Status, and
Configuration
The System link allows the user to view errors and generic information regarding the build. The
Status link allows the user to get feed back on the current operating parameters of the modem. The
Configuration link allows the user to strap the modem for its supported operating modes.
4.1.3.1 ADSL (WAN) Web-based Configuration
The ADSL link can be configured from the web interface by selecting the WAN connections link.


Then select the desired ATM and ADSL configurations. Pictured below is IPoA (IP Routing over
ATM).

Then select the details of the protocol. Pictured below are options for IPoA. This example depicts a
static IP address for the WAN (or ATM) interface, on VC 0/506. Selecting Use DHCP enables
DHCP-client on the port, and forces the modem to request an IP address from the Telcos network
(other end of WAN connection). Note that the Description field is mandatory, and must be
configured with any desired name.
After completing the information, select Apply to activate the ADSL link.

If the configuration was successful, a web page will be displayed as pictured below. Use the
description entered above to identify this VC. To add additional VCs, repeat this process.
To save the configuration to non-volatile memory, click the Save config link under Configuration.

4.1.3.2 ADSL (WAN) Web-based Status
To view the current status of the ADSL link from the web browsers, select the name entered in the
previous configuration section. For the previous example, select Show Statistics for ADSL from the
Defined Interfaces under the STATUS link.

4.2 CLI (Command Line Interface) Operation and Configuration

The modem configuration and status can also be viewed and modified through the console, which is
accessible through the RS-232 serial connection or through a Telnet connection over Ethernet.
To use the serial interface, a straight-through cable is needed between the modem and a terminal
(could be a PC running a terminal emulation package). The default serial configuration is 9600 bps, 8
data bits, one stop bit, no parity bits, and no flow control (i.e., 8-N-1).
4.2.1 Using the Console

The console commands needed for each mode of operation are described in the following sections.
Some general commands that are needed include:
Help for CLI is obtained by typing a command followed by a ? or simply ?:
This command lists the keywords that can be used. If a keyword is included, help for the particular
keyword is displayed.
system config save
This command causes each software module to write its new configuration to flash.
4.2.2 ADSL CLI-based Configuration
The following table further describes the commands
Command Description
show Displays all gs7070 attributes
set ActivateLine Set to true to initiate a DSL connection set to false to put PHY into Idle
mode
set ConnectMode Sets the connection mode (g.lite, g.dmt, t1.413, auto)
set UtopiaInterface Sets the Utopia level (Level1, Level2)
set PhysicalPort Sets the physical Utopia port (0-31)
set TestMode Puts the GS7070 into testmode(None, AnalogLbTest, DigitalLbTest,
SpectrumReverbTest, SpectrumReverbRxTest, SpectrumMedleyTest,
SpectrumPilotTest, SpectrumRMtprTest, SpectrumCMtprRxTest)
set Set to true allows the PHY to escape from G.HS to fast retrain
EscapeToFastRetrain
set FastRetrainEnable Set to true enables fast retrain
set MaxBitsPerBin Sets the maximum number of bits allowed per bin (1-15)
set RxAutoBinAdjust Set to Enable to allow the PHY to automatically adjust the bin numbers used
for Rx
set RxStartBin Sets the lowest bin number used for Rx if RxAutoBinAdjust is set to Disable
(6-255)

set RxEndBin Sets the highest bin number used for Rx if RxAutoBinAdjust is set to Disable
(6-255)
set TxStartBin Sets the lowest bin number used for Tx (6-255)
set TxEndBin Sets the highest bin number used for Tx (6-255)
set TxAttenuation Sets the TX attenuation value (0-12 db)
4.2.3 Line Activation

Use the set ActivateLine true and set ActivateLine false commands to activate and deactivate the
ADSL link.
4.2.4 Protocol Configuration

The modem provides different elements of the ISOS protocol stack based on how it is configured.
When configured as a PC-Attached device, the PC provides most of the protocol layers to
communicate with the service provider.
When attached as a Gateway or PC-Attached Gateway device, the modem is set up to run as either
a bridge or router and provides most of the protocol layers to communicate with the service provider.
In addition, the modem can be configured as a DHCP server to provide local IP addresses.
4.2.4.1 PC-Attached Configuration
Since the protocols are handled by the host operating system in this mode of operation, there is no
protocol configuration that needs to be performed on the VX1000LD for the USB configuration.
4.2.4.2 Bridge Configurations
4.2.4.2.1 Gateway Bridge Configuration

In the Gateway bridge configuration, the VX1000LD bridges data between the local Ethernet LAN and
the service provider. The ADSL link must be set up in RFC 1483 mode with a PVC for
communications. The PVC is assigned by the service provider. The bridge needs to be told about
both the Ethernet interface and the 1483 interface. Since the modem is transparent, the PCs default
gateway must be set to the service providers IP address.
192.168.101.1 192.168.101.2
Internet
PVC 700
ADSL
PC Modem
Subnet is 255.255.255.0 DSLAM
The following configuration must be performed to set up the VX1000LD for bridge mode:
Clear any existing IP interfaces or Ethernet transports by typing the following commands:
ip clear interfaces
ethernet clear transports
Add an Ethernet device to the bridge. In the following commands, eth1 is the transport name,
ethernet is the port name and bridge1 is the bridge interface name:
ethernet add transport myether ethernet

bridge add interface ethernet

bridge attach ethernet myether
Add an RFC1483 device to the bridge, with RFC1483 configured to run on port adsl, using
VCI 700 and LLC mode. In the following commands, my1483 is the transport name and
bridge2 is the bridge interface name:
rfc1483 add transport my1483 a1 0 700 llc bridged

bridge add interface rfc1483
bridge attach rfc1483 my1483
4.2.4.2.2 Gateway Router Configurations

There are multiple ways to configure routing depending on the requirements of the service provider.
The following routing methods are described below:
IPoA Routing
PPP Routing
Routing using NAT (can be used with either IPoA or PPP)
4.2.4.2.3 Gateway IPoA Routing

When configured for IPoA, data is routed between Ethernet and Classical IP over ATM (RFC1577).
The IPoA data runs over a PVC between the RD7312 and the service provider. IP addresses, the
PVC and the peak cell rate need to be defined by the service provider. Since the modem is routing,
an IP address needs to be assigned to both modem interfaces. The PCs default gateway must be set
to the Ethernet IP address of the modem.
192.168.101.1 192.168.102.3
192.168.101.2 192.168.102.2
Internet
PVC 700
ADSL
PC Modem
All subnets are 255.255.255.0 DSLAM
The following configuration must be performed to set up the RD7312 for the above example. From
the console command line, the following commands must be entered:
ip clear interfaces
Add the Ethernet device to the router. In the following command, eth1 is the transport name,
ethernet is the port name and ip1 is the interface name:
ethernet add transport eth1 ethernet

ip add interface ip1 192.168.101.2
ip attach ip1 eth1
Add the IPOA device to the router configured to run on PVC 700 using the port named adsl. In
the following commands, ipoa1 is the transport name and ip2 is the interface name:
ipoa add transport ipoa1 pvc a1 0 700

ipoa transport ipoa1 set pvc 1 port atm
ip add interface ip2 192.168.102.2
ip attach ip2 ipoa1

Add a default route, with the DSLAM as the gateway:
ip add route default 0.0.0.0 0.0.0.0 gateway 192.168.102.3

Save the configuration and reboot the system.
system config save

5. Software Update Procedure

To change the configuration of the VX1000LD to either a Gateway, PC-Attached, or PC-Attached
Gateway, the software image on the VX1000LD needs to be updated. In addition, from time to time it
may be necessary to update the software on the VX1000LD to the latest version available.
This section describes how to perform the update for the VX1000LD. The binary image running on
the Helium 210 TM is referred to as the ATMOS image. Only the ATMOS image needs to be updated
when changing the VX1000LD configuration between Gateway, PC-Attached and PC-Attached
Gateway.
5.1 Setting the IP Address

The board must have an IP address in order to use TFTP to update the software. If an IP address
needs to be set, use the following commands.
This example assumes the standard Ethernet Gateway builds.
The following commands can be used with the default console command line:
ip clear interfaces
Set the IP address:
ethernet add transport myether ethernet
ip add interface myip 172.16.1.239
(substitute any valid IP address)
ip attach myip myether
Save the configuration and reboot the system.
system config save
5.2 BootP/TFTP
During development it is usually much easier to load and test new images on the VX1000LD by using
BootP/TFTP to transfer flash images into the device. In order to perform a network boot on the
VX1000LD, simply restart the device and quickly press * on the console, that is connected to the
VX1000LD over the RS-232 port. The following prompt (or similar) will appear on the console that
allows the selection of the boot method:
He2xx Family Ethernet / USB boot v3.8
Network boot disabled: trying flash or UART
MAC 00:20:2b:00:bb:e0
SDRAM 0x00800000 bytes
Boot from Ethernet, USB or Flash? (E/U/F)
Enter E for Ethernet and BootP/TFTP will be used to boot up the device. The desired image must be
copied to the appropriate TFTP boot directory. Please see Appendix A for more information on
BootP/TFTP.

6. Status Indicators
There are two LEDs on the VX1000LD. The table below describes the status provided by these
LEDs.
Label Function Status if LED is ON

ATM- ADSL activity Data is being transceived on the ADSL interface
TX/RX
SHOW ADSL connection Slow blink: activating DSLAM not found
TIME
Fast blink: connecting DSLAM found
On: Showtime
Off: ADSL link disabled

Appendix A BOOTP and TFTP Example Setup

Several demonstration applications are available from the Internet that will allow the user to install
BOOTP and TFTP. A single client demo BOOTP program (BOOTP 95) is available from:
http://www.weird-solutions.com/download/index.html
The installation instructions included with the download will allow the user to install the application on a
Windows 95 or Windows 98 machine. Once the application is installed, click on Service->Properties and
select the client tab. The following steps will complete the set up:
In the hardware address field insert the MAC address of the VX1000LD
Select Template = <no template>
Select Available options Boot file and fill in the value field with the complete path and file name
of the binary image file that the VX1000LD should boot.
Select Available options Boot file size and fill in the value field with the file size in bytes as can
be found by right clicking on the file in windows explorer and selecting Properties.
Select Available options IP address and give the VX1000LD an IP address.
This will allow the VX1000LD to initiate the appropriate TFTP request for its boot file.
The installation instructions included with the download will allow the user to install a TFTP server that is
very easy to set up. Once the installation is complete, the boot file simply needs to be located exactly as
specified in the Boot file option as configured in the BOOTP application, and the TFTP server should not
have any restrictions on outbound files. This is the default TFTP server configuration.
It should be noted that Walusoft also has a BOOTP application available for download.
Note that no association with Walusoft or Weird solutions is implied, nor is this an endorsement of their
products. The user is strongly encouraged to read the usage agreements provided with each product and
to abide by them. GlobespanVirata can assume no responsibility for users that do not follow the
instructions provided with each product.

Appendix B Troubleshooting
If problems persist after referring to this section, additional support can be obtained by contacting
support@globespanvirata.com
No response from console

Verify COM port settings on the host terminal.
Verify a straight-through (DTE-to-DCE) RS-232 cable is used and properly connected. (Not a null-
modem cable.)
Verify proper gender changer is being used (if present).
ADSL activates, but doesnt connect

Verify the modem is properly connected to the telephone line via the telco jack using a standard
phone cord.
Take the line down (see section 4.2.3).
Enable debugging (see section 4.3.4).
Activate the line (see section 4.2.3).
Monitor the console for information regarding link failures:
Verify State:Training is displayed, if not reset the modem with a power-cycle.
Verify State:Handshake is displayed, if not, a DSLAM is not present at the Telco.
Note that the exact display may differ.
ADSL connects, but drops the link

Using the diagnostic capabilities (see section 4.2.2 bsp line command), observe the
Near End statistics. Poor noise margin or attenuation may indicate a noisy line, probably not suitable
for ADSL operation.
ADSL connects, but doesnt pass data

Verify proper protocol and transport configuration for the Router (see section 4.2.5.2.4) or Bridge (see
section 4.2.5.2.1).

vx1000 UseGuide v11

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

vx1000 UseGuide v11

Enviado por

Direitos autorais:

Formatos disponíveis

VX1000LD

2002 Versa Technology, Inc.

2. Product Overview ........................................................................................................................ 5

4. Operation and Configuration ................................................................................................... 14

5. Software Update Procedure ..................................................................................................... 26

6. Status Indicators ....................................................................................................................... 27

Appendix A BOOTP and TFTP Example Setup ............................................................................. 28

Appendix B Troubleshooting .......................................................................................................... 29

2002 Versa Technology, Inc. Page 2 of 29

Figure 2: Routed Network..................................................................................................................... 7

Figure 3: IPoA Protocol......................................................................................................................... 8

Figure 4: PPP Protocol.......................................................................................................................... 9

Figure 5: IP Dial-in over PPP ................................................................................................................ 9

Figure 6: NAT Protocol ....................................................................................................................... 10

2002 Versa Technology, Inc. Page 3 of 29

1.3 Related Documents

1.4 Summary of Contents

2002 Versa Technology, Inc. Page 4 of 29

2.1 ADSL Technology

2.2 Product Features

2002 Versa Technology, Inc. Page 5 of 29

2.3 Network Configurations and Protocols

2.3.1 PC-Attached Configurations

2002 Versa Technology, Inc. Page 6 of 29

2.3.2 Gateway Configurations

2.3.2.1 Bridge Configurations

Figure 1: Bridged Network

2.3.2.2 Router Configurations

Figure 2: Routed Network

2002 Versa Technology, Inc. Page 7 of 29

2.3.2.2.1 IP-over-ATM (IPoA)

Figure 3: IPoA Protocol

LLC/SNAP encapsulation (RFC 1483) is always used.

2002 Versa Technology, Inc. Page 8 of 29

Figure 4: PPP Protocol

IP Dial-in over PPP

CHAP IPCP Ethernet

IP over PPP over ATM

Figure 5: IP Dial-in over PPP

2002 Versa Technology, Inc. Page 9 of 29

2.3.2.2.3 Network Address Translator (NAT)

Figure 6: NAT Protocol

Choosing the interface on which to enable NAT

2002 Versa Technology, Inc. Page 10 of 29

2002 Versa Technology, Inc. Page 11 of 29

2.3.2.2.4 Dynamic Host Configuration Protocol (DHCP) Server

2002 Versa Technology, Inc. Page 12 of 29

3.1 Hardware Installation

2002 Versa Technology, Inc. Page 13 of 29

4. Operation and Configuration

4.1 Web Operation and Configuration

2002 Versa Technology, Inc. Page 14 of 29

2002 Versa Technology, Inc. Page 15 of 29

4.1.2 PC Web Browser Configuration

4.1.3 Ethernet-Gateway Configuration Via the Web Interface

4.1.3.1 ADSL (WAN) Web-based Configuration

2002 Versa Technology, Inc. Page 16 of 29

2002 Versa Technology, Inc. Page 17 of 29

2002 Versa Technology, Inc. Page 18 of 29

2002 Versa Technology, Inc. Page 19 of 29

2002 Versa Technology, Inc. Page 20 of 29

4.1.3.2 ADSL (WAN) Web-based Status

2002 Versa Technology, Inc. Page 21 of 29