IBM Heritage User Manual

Download

Heritage Series ADSL Brid

Heritage Series

User’s Manual

e/ Router

Multi-Mode

xDSL Router

Dec. 2003

Heritage Series ADSL Bridge/ Router

Changes are periodically made to the information in this document. They will be incorporated in subsequent editions. The product manufacturer may make improvements and/or changes in the product described in this document at any time.

Heritage Series ADSL Bridge/ Router

Table of Contents

Chapter 1 Introduction

1.1 Overview 1-1

1.2 Features and Compatibility

1.3 What’s in the package? 1-4

1.4 Important Rules for Safe Operation

1.5 Front Panel

1.6 Real Panel 1-9

Chapter 2 Installing and Configuring your xDSL

Router

2.1 Preparation for Hardware and Software Installation 2-2

2.2 Hardware Installation

2.3 Windows 95/98 setting for Ethernet LAN connection

2.3.1 Check TCP/IP protocol

2.3.2 TCP/IP installation

2.3.3 TCP/IP setting

2.4 Configuring the Router

2.4.1 Using TELNET via Ethernet interface

2.4.2 Using terminal program via serial console port

1-1

2-1

2-12 2-12 2-13

1-2

1-5 1-8

2-4 2-5 2-5 2-7 2-9

Chapter 3 Basic Configurations

3.1 Factory default configuration 3-2

3.2 Bridged RFC1483 3-3

3.3 Routed RFC1483

3.4 Classical IP (RFC1577)

3.5 PPP Over ATM (RFC2364)

3.6 PPP Over Ethernet (RFC2516) 3-13

3-1

3-5 3-7 3-9

Chapter 4 Advanced Configurations 4-1

4.1 Add NAT to Classic IP, PPP over ATM and PPP over Ethernet

4-2

4.2 Enables NAT to RFC1483, Classic IP (RFC1577), PPP over ATM (RFC2364) and PPP over Ethernet (RFC2516) in Routing mode

4.3 Changing DHCP server configuration

4.4 Changing DHCP client configuration 4-9

4.5 PPTP Tunneling Configuration

4-4 4-6

4-11

Chapter 5 Managing The xDSL Router

5.1 Booting the xDSL Router from Ethernet Network

5.2 Upgrading on-board flash memory from Ethernet Network 5-2

5.3 SNMP

Chapter 6 xDSL Link Performance Statistics

Chapter 7 Command Sets for Command Line

Interface

Command Line Interface Conventions 7-1 Basic system command sets Commands for ISFS and FLASHFS process Commands for Bridge process Commands for DHCP server process Commands for DHCP client process Commands for IP process Commands for NAT process 7-38 Commands for PPP process Commands for SNMP process Commands for DSL process

5-1

5-3

6-1

7-1

7-2 7-5

7-7 7-16 7-18 7-20

7-42 7-52 7-54

Chapter 8 DHCP Server Operation

8.1 DHCP Server Overview 8-1

8.2 DHCP Server Configuration

8.3 Informal configuration guide 8-2

8-1

8-2

Heritage Series ADSL Bridge/ Router

8.4 Configuration reference guide 8-4

Chapter 9 DHCP Client Configuration

9.1 Protocol Timing 9-2

9.2 Lease requirements and requests

9.3 Other declarations

9.4 DHCP Options

9-1

9-3 9-4 9-5

Appendix A Product Specifications Appendix B Troubleshooting Appendix C Glossary

A-1 A-4 A-8

Appendix D Government Compliance Notices A-16

Heritage Series ADSL Brid

e/ Router

Introduction

1-1

Chapter 1 Introduction

1.1 Overview

This xDSL Router features two broadband technologies such as ADSL and SHDSL. Multi-mode ADSL technology that provides a downstream rate of up to 8Mbps over existing copper wire lines, which is more than 100 times faster than a traditional 56K analog modem. SHDSL technology that provides a symmetric upstream and downstream rate of up to 2.3Mbps over existing copper wire lines.

And it can be connected to your PC or LAN through the 10Base-T or 100Base-T Ethernet interface.

This xDSL Router is designed to meet both the needs of single user, and multiple users at small offi ce a nd home offic e who wa nt f ast Inte rnet a cce ss. A wide variety of features and interoperability offer scalability and flexibility for all the applications

1-2

Introductio

1.2 Features and Compatibility

This Heritage series Router provides the followi ng fe atures:

! Multi- mode ADSL technology supports ITU-T G.dmt, G.lite, G.hs

and ANSI T1.413 issue 2 to provide interoperability with most of DSLAM equipments.

! SHDSL technology supports ITU-T G.shdsl, G.hs and ANSI

T1E1.4 to provide interoperability with most of DSLAM equipments.

! A T M (Asynchronous Transfer Mode) protocol allows the

QoS(Quality of Service) transmission over a network

! Su ppor t for text-based and Windows-GUI based conso le

management over Telnet and serial connec tion

! Su ppor t for remote configur ation by your network ad ministrator

via IP network.

! Support IEEE 802.1d transparent bridging with spanning tree

algorithm.

! Br id ge filtering allows a network admini strator to control the

flow of packets across the router

! NAT : let multiple users on the LAN share one Interne t

connection simult aneously

! SNMP agent: allows monitoring and configuration by a standard

SNMP manager.

! BOOTP/TFTP enable the remote configuration ! DHCP client : let an ISP dynamically issue an a d d r ess upon initial

connection.

! DHCP server : a utomatically assigns IP addresses to all computer

on the LAN.

! DNS relay : allows for automatic name resolution when no DNS

information is configured by the user.

! PPTP tunneling enable VPN configuration. ! Point-to-Point Protocol (PPP) ! RFC 1483 Link Protocol ! Pa ssword Authenticati on Protocol (PAP) and C hallenge

Handshake Authentication Protocol (CHAP) security under PPP protocol

! IP routin g su pport inc lud es the RIP( Rou tin g I nformati on Prot ocol )

which allows the exc hange of routing information on a TCP/IP

Heritage Series ADSL Brid

e/ Router

Introduction

network

! Flash memory for Software upgrade ! Status LEDs for easy monitoring and troubleshooting

Some models of xDSL Router provides more features:

! Including 4-port 10/100 Base-T Ethernet Stackable Switch Hub.

1-3

1-4

Introductio

1.3 What’s in the package?

! One xDSL Router ! One 9VDC or 12VDC Adaptor, depend on different mo del ! One RJ-11 Telephone Cable ! One 10Base -T Ethernet straight-t hrough Cable ! One 9-pin to 9-pin RS-232 Cable (option) ! One User’s Guide

All packages have been checked carefully for their completeness and functionality before shipped. Please contact the pla c e of purchase if any of the above listed items are missing or d amaged.

If you encountered any difficulty in using this product while all the above items are complete, please refer to Appendix C for Troubleshooting information before ma king the decision to r eturn your xDSL Route r to your dealer.

Heritage Series ADSL Brid

e/ Router

Introduction

1-5

1.4 Important Rules for Safe Operation

In addition to the careful attention devoted to quality standards on the manufacture of your ADSL Router, safety is a major factor in the design of every product. However, safety is your responsibility, too. This section lists important information that will help assure your enjoyment and proper use of the ADSL Router and accessory equipment. Please read them carefully before operation and using your Router.

! Read and Follow Instructions – you should read all the safety and

operating instructions before operating the Router.

! Retain Instructions – You should save all the safety and operating

instructions, for your future reference.

! Heed Warning – Comply with all warnings on the prod ucts and in

the operating instructions.

! Check Power Sources – Operate this product only from the type of

power source indicated on the product’s marking la bel. If you are not sure of the type of power supplied to your home, consult your dealer or local power company.

! Be Careful of Overloading – Do not overload wall outlets or

extension cords, a s this ca n r esult in a ris k of f ire or ele c tric sh ock. Overloaded AC outlets, extension cords, frayed power cords, damaged or cracked wire insulation, and broken plugs are dangerous. They may result in a shock or fire hazard. Periodically examine the cord, and if its appearance indicates damage or deteriorated insulation, have it replaced by your service technician.

! Protect Power Cords – Route power supply cords so that they are

not likely to be walked on or pinched by items placed upon or against them. Pay particular attention to cords where they are attached to plugs and convenience receptacles, and examine the point where they exit from the product.

! Check Ventilation – Slots and openings in the enclosure are

provided for ventilation to ensure reliable operati on of the product and to protect it from overheating. Do not block or cover these openings. Never block these openings b y placing the product on a bed, sofa, rug, or other similar surface. Never place this product near or over a radiator or heat r egister, or any other

1-6

heat source (including amplifiers). Do not place this product in a built-in installation, such as a bookcase or equipment rack, unless you provide proper ventilation.

! Do Not Use Accessories – Do not use attachments, unless they are

recommended by your vendor, as they may cause electrical or fire hazards.

! Use the Recommended Power Adaptor – You m ust use the Power

Adaptor that comes with your ADSL Router.

! Do Not Use Near Water – Do not use this product near water. For

example, near a swimming pool, bath tub, wash bowl, and the like.

! Do Not place Near High Temperature Source – For example near

a steamer, kitchen range fire, and the like.

! Use Caution in Mounting This Product – Do not place this

product on an unstable surface or support. The product may fall, causing serious injury to a child or ad ult, as well as serious damage to the product.

! Use Care in Moving Product-and-Cart Combinations – Quick

stops, excessive, force and uneven surfaces may cause the product-and-cart combina tion to overturn.

! Unplug Power Before Cleaning – Do not use liquid cleaner or

aerosol cleaner. Use a damp cloth for cleaning.

! Keep Objects Out of Openin gs – Never push objects of any kind

into this product through openings, as they may touch dangerous voltage or “short-out” parts, whic h could result in a fire or electric shock. Never spill liquid on the product.

! Protect From Lightning – F or added protection for thi s product

during a lightning storm, or when it is left una ttended and unused for long periods of time, unplug it from the wall outlet, and disconnect the cable system. This will prevent damage to the product due to lightning and power line surges.

! Turn Off the Power Switch Between DC Plug Off and On. ! Do Not Remove Covers – Do not attempt to service this product

yourself, as opening or removing covers may expose you to dangerous voltage or other hazards.

! Unplug this Product From Wall Outlet Carefully, as the Power

Adaptor May Be Hot.

Introductio

Heritage Series ADSL Brid

e/ Router

Introduction

! Refer Servicing to Qualified Service Personnel Under the

Conditions Listed Below.

# When the power supply cord or plug is damaged. # If liquid has been spilled or objects have fallen into the

product.

# If the product has been exposed to rain or water. # If the product does not operate normall y by following the

operating instructions. Adjust only those controls that are covered by the operating instructions.

# If the product has been dropped or the cabinet has been

damaged.

# When the product exhibits a distinct change in

performance, such as the inability to perform basic functions – this indicates a need for service.

! Require Safety Check – Upon completion of any service or repairs

to this product, ask the service technician to perform safety checks recommended by service point to determine that the products is in safe operating condition.

1-7

1-8

Introductio

1.5 Front Panel

The xDSL Router has five status LEDs for diag nostics. You can monitor the LEDs during operation. Following table shows the xDSL Router status LEDs and identifies what each LED light means.

Function Behavior Definition

Dark Power off POWER Light Power on

Flashing slowly xDSL training in progress xDSL Light xDSL link is establish and ready to

transfer data

Dark Ethernet link absent or power off PC

Light Ethernet link present RX Flashing Receiving data from xDSL link TX Flashing Transmitting data to xDSL link

The xDSL Router which including 4-port stackable switch hub that has several status LEDs for diagnostics. You can monitor the LEDs during operation. Following table shows the xDSL Router status LEDs and identifies what each LED light means.

Function Behavior Definition

Dark Power off POWER

Light Power on TX/RX Flashing Transmitting/Receiving data to/from

xDSL link Flashing slowly xDSL training in progress LINK Light xDSL link is establish and ready to

transfer data Dark Ethernet link absent or power off L1 ~ L4

Light Ethernet link present

Heritage Series ADSL Brid

e/ Router

Introduction

1-9

1.6 Rear Panel

The rear panel of the xDSL Router consist of power jack, Console Port connector, Ethernet connect and xDSL link jack which they means as below:

Function Definition

xDSL xDSL jack connect to DSL line from TelCo. 10Base-T or 10/100Base-T

Console This is RS232C interface and use to

DC 9V or DC12V

The rear panel of the xDSL Router which including 4-port stackable switch hub consist of power jack, Console Port connector, Ethernet c onnects and xDSL link jack which they means a s below:

Function Definition

xDSL xDSL jack connect to xDSL line from TelCo. Up-Link This is HUB feature cascade to another HUB for

L1 ~ L4 Ethernet Ports: Port1 to Port4 Console This is RS232C interface and use to

DC 9V The power jack connects to Adaptor from wall

Ethernet interfac e connect to PC or HUB for LAN.

management xDSL R oute r. The power jack connects to Adaptor from wall

outlet.

expand LAN.

management xDSL R oute r.

outlet.

1-10

Introductio

Heritage Series ADSL Brid

Installing and Configuring your xDSL Router

e/ Router

2-1

Chapter 2 Installing and

Configuring your xDSL Router

The major function s of the xDSL Router are performed by using Ethe rnet 10Base-T or 10/100Base-T network interface. Your computer has to install an Ethernet NIC card and set up the TCP/IP protocol before start to using the xDSL Router.

The xDSL Router also provides a serial console port for monitoring and configuring the Rou t e r via the xDSL Configura tion Tool or HyperTerminal program.

2-2

Installin

and Configuring your xDSL Router

2.1 Preparation for Hardware and software installation

Before start the hardware installation. Please prepare all the materials listed below regarding to your application.

1. Connect to a computer directly

! xDS L service provider or ISP/NS P se rvice contract. Please

sign an appropriate Internet connection contract with a reliable ISP/NSP and get necessary c onnection information that will help you configuring your Router.

! Personal computer with OS that support Ethernet inter f ace ! TCP/IP protocol installed i n your pe rsonal computer ! Ethernet card (10 or 10/100Base-T) ! Ethernet straight-through cable (included in this package) ! RJ-11 telephone cable (included in this package) ! RS-232 serial cable (optional) ! Power ad aptor (include in this package)

Serial Port

Ethernet Port

Console Port

Ethernet Port

DSLAM/ISP

PC B

Heritage Series ADSL Brid

2. Connect to more than one computer

Installing and Configuring your xDSL Router

Excepts the items listed on step 1 above, you still need following items:

e/ Router

! Additional PC with OS that support Ethernet

interface.

! Additional Ethernet card for e ach PC you want

to connect

! Additional Ethernet Straight-through cable for

each PC you want to connect.

! One Ethernet Hub is required for more than one

computer connection.

! If your up-link hub without cascade switch,

please prepare an Ethernet crossover cable instead of the straight-through cable that listed on step 1 above.

Serial Port

PC A

Ethernet Port

PC C

2-3

Console Port

Ethernet Port

HUB

Up-Link

DSLAM/ISP

2-4

Installin

and Configuring your xDSL Router

2.2 Hardware Installation

Before start to configure your Router, you have to co mplete all the hardware installation. The following steps provide instructions for installing your Router.

1. Be sure the power switch on the right side of the Router is at the

OFF status.

2. Connect the power adaptor to the power jack that marked Power

at the rear panel of the Router, then plug in the DC power adaptor to the wall electrical outlet.

3. Connect the Ethernet cable.

A) If connect to computer directly

Connect one end of Ethernet straight-through cable to the Ethernet port on your computer, then connect the other end of Ethernet straight-though cable to the c onnector that marked 10/100Base-T at the rear panel of the Router.

B) If connect to more than one computer via Hub Connect one

end of Ethernet straight-through cable (If your up- link hub without cascade switch, please use an Ethernet crossover cable instead) to the uplink port on the Ethernet Hub, then connect the other e nd of Ethernet cable to the connector that marked 10/100Base-T at the rear panel of the Router.

4. Connect one end of RJ11 telephone cable to the xDSL line jack

that marked xDSL at the rear panel of the Router, then connect the other end of RJ-11 telephone cable to the xDSL service port that your xDSL service provider or ISP installed.

5. Connect the male (9 pin) end of the RS-232 serial cable to the

connector that marked Console port at the rear panel of the Router, then plug the other end of the RS-232 serial cable to the RS-232 serial port of your computer.

6. Turn on the power switch. The Router should perform a self-test,

and then be ready for use.

Heritage Series ADSL Brid

Installing and Configuring your xDSL Router

e/ Router

2-5

2.3 Windows 95/98 setting for Ethernet LAN

connection

Either connect to Internet or configure the Router via Ethernet, the TCP/IP protocol is really necessary. And your computer must be on the same subnet with the Router.

When you directly connect the Router to your computer through the Ethernet network, yo u will first configure your computer to obtain an IP

address automatically from your Router’s DHCP server, or specify an IP address and Subnet Mask to the same subnet as remote host. The

following steps provides the instruct ions to setup your computer to obtain an IP address by using Windows 95/98 on a PC

2.3.1 Check TCP /IP protocol

To check if TCP/IP is properly installed, please proceed to the following steps.

1. Double-click on My computer->Control Panel->Network

2-6

2. In Network window, check if TCP/IP is shown and proper ly

Installin

setup for the Ethernet card that installed in your computer (for example, TCP/IP->Realtek RTL8029(AS) PCI Ethernet NIC).

and Configuring your xDSL Router

3. When TCP/IP has properly installed, please proceed to 2.3.3

TCP/IP Setting

4. When TCP/IP has not properly installed, go to next section to

install the TCP/IP protocol.

Heritage Series ADSL Brid

Installing and Configuring your xDSL Router

e/ Router

2.3.2 TCP/IP installation

Attention: When install TCP/IP protocol, you need Windows CD-ROM

1. In Network window, click the Add button.

2. Choose the Protocol and click Add.

3. In Select Network Protocol window, choose Microsoft in

Manufacturers and TCP/IP in Network Protocols. Then click OK

2-7

2-8

4. Confirm if the TCP/IP protocol has been corr ectly setup with

Installin

your Ethernet card.

and Configuring your xDSL Router

Heritage Series ADSL Brid

Installing and Configuring your xDSL Router

e/ Router

2-9

2.3.3 TCP/IP setting

Attention: When connecting your xD SL Router with existing LAN, consult

your network manager for correct configurations

1. In Network window, double-click the TCP/IP service for the

Ethernet card that installed in your computer (for example, TCP/IP > Realtek RTL8029(AS) PCI Ethernet NIC).

2. Click the Gateway tab, and remove any installed gateways.

2-10

3. Click the DNS configuration tab, and click the disable DNS

Installin

button.

and Configuring your xDSL Router

4. For DHCP client, Click the IP address tab, and click the Obtain

an IP address automatically button.

Heritage Series ADSL Brid

Installing and Configuring your xDSL Router

e/ Router

For Fixed IP or DHCP server, Click the IP address tab, and click the Specify an IP address button. Then set IP Address and Subnet Mask to the same subnet as remote host. Refer to Chapter

3.2 for example.

5. Click OK to save the new setting.

6. Click Yes when prompted for “Do you want to restart you r

computer ?”. Your computer will restart to make the n e w setting in effects.

7. Now your computer is ready to access your Router via Ethernet

network.

2-11

2-12

Installin

and Configuring your xDSL Router

2.4 Configuring the Router

There is some setup required to get your xDSL Router working properly. The configuration of the xDSL Router can be accessed in three ways:

# Using TELNET via Ethernet interface # Using terminal program via serial console port # Using xDSL Configuration Tool ( ACT) via serial console port

2.4.1 Using TELNE T via Ethernet interface

To access the command line interface via Ethernet interface, you can use TELNET to log in the Router from the local Ethernet network using the Ethernet IP address that assigned to your xDSL Router. The Ethernet IP of the xDSL Router is default set to 192.168.7.1.

1. Select Start->Programs->MS-DOS Prompt.

2. Find the IP address of the Router’s Ethernet port. Then use

TELNET to login the Router. For example, TELNET

192.168.7.1

3. You will see that a telnet dialog pops up asking for password

(case sensitive), then enter admin ↵

Heritage Series ADSL Brid

Installing and Configuring your xDSL Router

e/ Router

2-13

4. Then you will see the following prompt, DSL >

5. Now you are ready to configure the Router by using command.

Please contact your ISP/NSP to obtai n the detail command sets of your Router. If the Router does not return any message, refer to Appendix B for troubleshooting information.

2.4.2 Using termin al program via serial console port

A terminal can be connec ted directly to the Serial console port. This requires the use of a terminal emulation software package such as Microsoft HyperTermi nal. By default setting, the R outer is configured to communicate at a baud rate of 9600. Any standard terminal that support baud rate of 9600 can be connected to the Router’s console port. Please configure your serial port as: BPS : 9600 Data bits : 8 Parity : None Stop Bits : 1 Flow Control : None

Following steps provide the instructions to log on to the Router via Microsoft HyperTerminal.

1. Select Start->Programs->Accessories->HyperTerminal

2-14

2. Enter a connect ion name and click OK

Installin

and Configuring your xDSL Router

3. Select properly COM port and click OK

Heritage Series ADSL Brid

4. Enter the following parameters :

Installing and Configuring your xDSL Router

Then click OK

e/ Router

Bits per second 9600 Data bits 8 Parity None Stop bits 1 Flow Control None

2-15

6. When the HyperTerminal window appears, you must press the

enter key several time to get the command prompt for the Router’s command line interface.

7. Now you are ready to configure the Router by using command.

Please contact your ISP/NSP to obtai n the detail command sets of your Router. If the Router does not return any message, refer to Appendix B for troubleshooting information.

2-16

Installin

and Configuring your xDSL Router

Heritage Series ADSL Brid

e/ Router

Basic Configurations

3-1

Chapter 3 Basic Configurations

This chapter contains c onfiguration information, instructions and examples for the basic link protocols that supported by the xDSL Router. The information needed to configure the Router is depending on the chosen link protocol. The link protocol is determined by your NSP(Network Service Provider). Therefore, It is necessary to know the link protocol which your NSP support before you ref e r to the configuration information that will apply to your setup.

3-2

Basic Confi

urations

3.1 Factory default configuration

The Router is shipped with factory default settings. You may or may not need to change them depend on what kind of network that your Router is going to be installed.

Configuration item Default settings of xDSL Router Ethernet Interface IP address 192.168.7.1

Network Mask 255.255.255.0 xDSL interface IP address None Network Mask None ATM VPI/VCI number 0/32 Data Encapsulation Protocol RFC1483 Machine Name DSL Domain name Disabled DHCP Server Disabled DHCP Client Disabled DNS Relay Disabled NAT Disabled RIP Disabled IP filtering Disabled Bridge filtering Disabled Spanning Tree Disabled Telnet login password SNMP access password

admin admin

Heritage Series ADSL Brid

e/ Router

Basic Configurations

3-3

3.2 Bridged RFC1483

(Default configuration for Router)

[System configuration]

192.168.7.2

Ethernet Port

192.168.7.1

[ISP/DSLAM configuration]

IP address : 192.168.7.3 Subnet mask : 255.255.255.0 Gateway : None

[Local PC configuration]

IP address : 192.168.7.2

Subnet mask : 255.255.255.0 Gateway : None

The Router already default to support the RFC 1483. However, you can use following procedure to reconfigure the Router to support the RFC 1483 again.

> ip device flush > bridge device add edd > bridge device add bun/port=r1483/rfc1483=true/mode=<x>/

txvpi=<y>/txvci=<z>/rxvpi=<y>/rxvci=<z>

(<x> is the encapsulation mode of RFC1483, it can be one of LlcBridged and VcMuxBridged, and the setting of encapsulation mode is case sensitivity. <y> is the VPI value, and <z> is the VCI value)

> config save > restart

DSLAM/NSP

192.168.7.3

// r1483

r1483

3-4

Basic Confi

urations

The following describes how to remove a ll configurations properly so that we start from a fresh configuration.

> isfs rm resolve↵ > isfs rm initbridge > isfs rm initppp↵ > restart ↵

↵

Heritage Series ADSL Brid

e/ Router

Basic Configurations

3.3 Routed RFC1483

[System configuration]

PC A

PC B

[ISP/DSLAM configuration]

IP address : 10.99.48.1 Subnet mask : 255.255.255.0 Gateway : 10.99.48.50

[Local PC A configuration]

IP address : 10.107.1.130

Subnet mask : 255.255.255.248 Gateway : 10.107.1.129

[Local PC B configuration]

IP address : 10.107.1.131

Subnet mask : 255.255.255.248 Gateway : 10.107.1.129

> home ↵

(ignores any error message, just ensures back to root prompt)

> ip device add ethernet ether //edd 10.107.1.129 ↵

(set 10.107.1.129 as the IP address for your xDSL Router)

Ethernet Port

10.107.1.130

10.107.1.131

10.107.1.132

PC C

Ethernet Port

10.107.1.129

HUB

Up-Link

DSLAM/ISP

3-5

10.99.

48.50

10.99.48.1

3-6

> ip device add mpoa ptp //bun/port=r1483/rfc1483=true/mode=<x>/ txvpi=<y>/txvci=<z>/rxvpi=<y>/rxvci=<z> 10.99.48.50↵

Basic Confi

urations

(assume 10.99.48.50 is the static IP address assigned by your service provider fo r the PC); (<x> is the encapsulation mode of RFC1483, it can be one of LlcRouted and VcMuxRouted, and the setting of encapsulation mode is case sensitivity. <y> is the VPI value, and <z> is the VCI value)

> ip route add default 0.0.0.0 10.99.48.1 0:0:0:0 ↵

(10.99.48.1 is the IP address of your service provider)

> ip relay all↵

(enable routing between rfc1483 and ethernet ports)

config save ↵ restart ↵

You can use following procedure to remove existing RFC 1483 setting.

> isfs rm resolve↵ > isfs rm initbridge > isfs rm initppp↵ > restart ↵

↵

Heritage Series ADSL Brid

e/ Router

Basic Configurations

3-7

3.4 Classical IP (RFC1577)

[System configuration]

202.1.136.100

Ethernet Port

202.1.136.254

[ISP/DSLAM Configuration]

IP Address : 192.168.1.1 Subnet Mask : 255.255.255.0 Default Gateway : 192.168.1.2

[Local PC Configuration]

IP Address : 202.1.136.100 Subnet Mask : 255.255.255.0 Default Gateway : 202.1.136.254

The following describes how to remove a ll configurations properly so that we start from a fresh configuration.

Remove all existing bridge module confi guration

> home ↵ > config reset bridge ↵ > config save ↵ > restart ↵

Remove all existing router module confi gur atio n

> home ↵ > ip device flush ↵ > ip norelay > ip ipatm pvc delete ipoa r1483 0/32

↵

DSLAM/NSP

192.168.1.1

↵

192.168.

1.2

3-8

Basic Confi

urations

(use the same VPI/VCI of RFC 1577 setting)

> config save ↵ > restart

↵

Remove all existing IP module configuration device

> home ↵ > ip device flush ↵ > config save ↵ > restart ↵

We are ready for RFC1577 setup

Specify the gateway (RFC1577 on ISP/DSLAM site and Ethernet on local PC site)

> home ↵ > ip device add ethernet ether //edd 202.1.136.254 ↵ > ip device add ipoa atm //atm 192.168.1.2 ↵ > config save ↵ > restart ↵

Enable forwarding between router interface

> home ↵ > ip relay all ↵ > ip ipatm pvc add ipoa r1483 x/y remoteip 192.168.1.1 ↵

(‘ x’ is the VPI, ‘ y’ is the VCI. Check with your service provider)

> config save ↵ > restart ↵

Heritage Series ADSL Brid

e/ Router

Basic Configurations

3-9

3.5 PPP Over ATM (RFC2364)

[System configuration]

202.1.136.100

Ethernet

[ISP/DSLAM Configuration]

IP Address : 192.168.1.1 Subnet Mask : 255.255.255.0 Default Gateway : 192.168.1.2

[Local PC Configuration]

IP Address : 202.1.136.100 Subnet Mask : 255.255.255.0 Default Gateway : 202.1.136.254

The xDSL Router also can be setup to support RFC 2364(PPP over ATM) with following procedure. Before setup RFC 2364, you have to ensure remove existing RFC 1483 or RFC 1577 configuration with the procedure mentioned above.

• IP dial out over PPPoA

> ip device add Ethernet ether //edd 202.1.136.254 ↵

(This is the IP of Ethernet port of xDSL Router)

> ip device add ppp_device ether //ppp/DEVICE=1 ↵ > config save ↵ > restart ↵

> ppp 1 pvc 0 32 ↵

(Set channel 1 to VPI=0, VCI=32)

> ppp 1 welogin <name> <password> ↵

(This is the login name and password of PPP server)

> ppp 1 enable ↵

Ethernet Port

202.1.136.254

DSLAM/NSP

192.168.1.1

192.168.

1.2

3-10

> config save ↵ > restart ↵

> ip relay all ↵ > config save ↵ > restart ↵

Basic Confi

urations

• Remote bridging over PPPoA

> bridge device add edd ↵ > bridge device add ppp/DEVICE=2 ↵ > config save ↵ > restart ↵

> ppp 1 pvc 32 mac ↵ > ppp 1 interface 2 ↵ > ppp 1 enable ↵ > restart ↵

The RFC 2364 configuration also can be removed by following procedure. Please ensure to remove the RFC 2364 configuration before set the xDSL Router to other co nfiguration.

• IP dial out over PPPoA

> ip device flush ↵ > config save ↵ > restart ↵

> ppp 1 pvc none ↵ > ppp 1 welogin none ↵ > ppp 1 interface 0 ↵ > ppp 1 disable ↵ > restart ↵

> ip norelay ↵ > config save ↵ > restart ↵

Heritage Series ADSL Brid

e/ Router

Basic Configurations

• Remote bridging over PPPoA

> config reset bridge ↵ > config save ↵ > restart ↵

> ppp 1 pvc none ↵ > ppp 1 interface 0 ↵ > ppp 1 disable ↵ > restart ↵

3-11

3-12

Basic Confi

urations

Heritage Series ADSL Brid

e/ Router

Basic Configurations

3-13

3.6 PPP Over Ethernet (RFC2516)

[System configuration]

202.1.136.100

Ethernet

[ISP/DSLAM Configuration]

IP Address : 192.168.1.1 Subnet Mask : 255.255.255.0 Default Gateway : 192.168.1.2

[Local PC Configuration]

IP Address : 202.1.136.100 Subnet Mask : 255.255.255.0 Default Gateway : 202.1.136.254

The xDSL Router also can be setup to support RFC 2516(PPP over Ethernet) with following procedure. Before setup RFC 2516, you have to ensure remove existing RFC 1483 or RFC 1577 or RFC 2364 configuration with the procedure mentioned above.

• IP dial out over PPPoE

> ip device add ethernet ether //edd 202.1.136.254 ↵

(This is the IP of Ethernet port of xDSL Router)

> ip device add ppp_device ether //ppp/DEVICE=1 ↵ > ppp 1 pppoe 0 32 ↵

(Set channel 1 to VPI=0, VCI=32)

> ppp 1 welogin <name> <password> chap↵

(This is the login name and password of PPP server)

> ppp 1 enable ↵ > config save ↵ > restart ↵

Ethernet Port

202.1.136.254

DSLAM/NSP

192.168.1.1

192.168.

1.2

3-14

> ip relay all ↵ > config save ↵ > restart ↵

Basic Confi

urations

The RFC 2516 configuration also can be removed by following procedure. Please ensure to remove the RFC 2516 configuration before set the xDSL Router to other co nfiguration.

> isfs rm resolve

> isfs rm initppp

> restart

Heritage Series ADSL Brid

e/ Router

Advanced Configurations

4-1

Chapter 4 Advanced Configurations

This Chapter described the advanced features that are primarily intended for experienced users and network administrators to perform network management and mor e complex configurati ons.

4-2

Advanced Confi

urations

4.1 Add NAT to Classic IP, PPP over ATM or PPP

over Ethernet

NAT is an IP address conversion feature that translates a PC’s local (internal) address into a temporary global (outside/Internet) IP a ddress. NAT is needed when a PC (or several PCs) on a Local A rea Network wants to connect to the outside Internet to get to a remote network: NAT s wa ps the local IP address to a global IP address. Our version of NAT goes one step further by allowing several PCs to shar e one single IP address to the Internet, thus reducing connection costs. In effect, it allows a whole LAN to connect to the Internet as a single user.

[System configuration]

PC 1

202.1.136.101

Ethernet Port

HUB

[ISP/DSLAM configuration]

IP address : 192.168.102.3 Subnet mask : 255.255.255.0 Gateway : None

[Local PC 1 configuration]

IP address : 202.1.136.101

Subnet mask : 255.255.255.0 Gateway : 202.1.136.254

[Local PC 8 configuration]

IP address : 202.1.136.108

Subnet mask : 255.255.255.0 Gateway : 202.1.136.254

PC 8

202.1.136.108

Ethernet Port

Up-Link

DSLAM/NSP

Heritage Series ADSL Brid

e/ Router

Advanced Configurations

4-3

The following comma nd tell you how to adding a Network Address Translation protocol to the Classic IP(RFC1577) or PPP over ATM(RFC2364) or PPP over Ethernet(RFC2516) configuration that mentioned above. The following comma nd must be added after the “ip device add …” commands have been given and the Router restarted.

Enables NAT on a Classic IP (RFC1577)

> ip nat add ipoa ↵

Enables NAT on a PPP over ATM (RFC2364) or PPP over Ethernet (RFC2516)

> ip nat add ppp_device ↵

4-4

Advanced Confi

urations

4.2 Enables NAT to RFC1483, Classic IP (RFC1577),

PPP over ATM (RFC2364), PPP over Ethernet (RFC2516) in Routing mode

The xDSL Router can be setup to adding NAT protoc ol to a Routing Mode configuration like RFC1483, RFC 1577, RFC 2364 or RFC 2516 with following procedure. The following procedure must be typed after

device add

configure procedure) have been given and the xDSL Router restarted.

[System configuration]

command ( in RFC1483, RFC 1577, RFC 2364 or RFC2516

PC 1

202.1.136.1

Ethernet Port

HUB

Ethernet Port

202.1.136.254

Up-Link

[ISP/DSLAM configuration]

IP address : 192.168.102.3 Subnet mask : 255.255.255.0 Gateway : 192.168.102.2

[Local PC 1 configuration]

IP address : 202.1.136.1

Subnet mask : 255.255.255.0 Gateway : 202.1.136.254

[Local PC 8 configuration]

IP address : 202.1.136.100

Subnet mask : 255.255.255.0 Gateway : 202.1.136.254

PC N

202.1.136.100

DSLAM/NSP

192.168 .102.2

192.168.102.3

Heritage Series ADSL Brid

e/ Router

Advanced Configurations

4-5

• Add NAT to RFC 1483 to above RFC 1483 Routing Mode example

> ip nat add mpoa ↵

(ipoa is the device name same as you configure in RFC 1483 example)

• Remove NAT to RFC 1483 to above RFC 1483 Routing Mode example

> ip nat delete mpoa ↵

• Add NAT to RFC 1577 to above RFC 1577 Routing Mode example

> ip nat add ipoa ↵

(ipoa is the device name same as you configure in RFC 1577 example)

• Remove NAT to RFC 1577 to above RFC 1577 Routing Mode example

> ip nat delete ipoa ↵

• Add NAT to RFC 2364/RFC2516 to above RFC 2364/RFC2516 Routing

Mode example

> ip nat add ppp_device ↵

(ppp_device is the device name same as you configure in RFC 2364/RFC2516 example)

• Remove NAT to RFC 2364/RFC2516 to above RFC 2364/RFC2516 Routing Mode example

> ip nat delete ppp_device ↵

4-6

Advanced Confi

urations

4.3 Changing DH CP server configuration

DHCP is used to acquire IP addresses and options (such as the subnet mask, DNS, gateway, etc.) automatically. On the practical level, acquiring these initialization paramete rs with DHCP translates into avoiding the more involved Route r/PC process (reconfiguration of Rou ter and/or PC addresses in the same network.

[System configuration]

PC 1

202.1.136.1

[ISP/DSLAM configuration]

IP address : 192.168.102.3 Subnet mask : 255.255.255.0 Gateway : None

[Local PC configuration]

IP address : None ( obtained by DHCP) Subnet mask : None (obtained by DHCP) Gateway : None (obtained by DHCP)

By default, the xDSL Router is configured as a DHCP server with the following settings :

% Do not allocate dyna mic IP addresses to unknown clients

deny unknown-clients;

% Do not repond to BOOTP queries

deny bootp;

PC N

202.1.136.100

Ethernet Port

HUB

Ethernet Port

202.1.136.254

Up-Link

DSLAM/NSP

192.168

192.168.102.3

.102.2

Heritage Series ADSL Brid

e/ Router

Advanced Configurations

4-7

% Use 255.255.255.0 as subnet mask for all clients in 10.0.0.0 subnet

subnet 10.0.0.0 netmask 255.255.255.0 {

% Range of dynamic IP addresses (change only the last digit)

range 10.0.0.2 10.0.0.5;

% If client does not request a specific lease time allocate 3 600

% seconds

% (change as required)

default-lease-time 3600;

% If client requests specific expiration time, allocate 7200

% seconds

%(change as required)

max-lease-time 7200;

% Set clients default gateway to this (do not change)

option routers 10.0.0.1;

% Set clients primary/secondary DNS as these (change as required)

option domain-name-servers 206.13.28.12, 206.13.31.12;

% Set clients domain name as this (change as required)

option domain-name " p acbell.net";

}

% Use 255.255.255.248 as subnet mask for the IP addr 63.193.197.114

% Define subnet for the IP address used by NAT (change as needed)

subnet 63.193.197.114 netmask 255.255.255.248 {

}

The basic procedure to change the default setting is that you have to delete the existing configur ation and reentering new configuration.

> home ↵

> dhcpserver config ↵

(displays the current DHCP server configura tion)

> dhcpserver config flush ↵

(deletes current DHCP server settings)

> dhcpserver config confirm ↵

(confirm the previous action)

> config save ↵

(save the new configuration)

> dhcpserver config ↵

(displays the current DHCP server configuration. Should be empty.)

Now add the new settings for DHC P server.

4-8

> dhcpserver config add subnet 10.0.0.0 netmask 255.255.255.0 {

range 10.0.0.A 10.0.0.B; default-lease-time C; max-lease-time D; option routers 10.0.0.1; option domain-name-servers eee.fff.ggg.hhh, iii.jjj.kkk.lll; option domain-name “mmmm” } ↵

(A, B are integers in the rang e 2--255, C/D indicate time in seconds,eee.fff.ggg.hhh/iii.jjj.kkk.lll are IP addresses of primary/secondary DNS, mmmm is domain name. All these values are assigned by yo ur service provider.)

> dhcpserver config add subnet aaa.bbb.ccc.ddd netmask

eee.fff.ggg.hhh { } ↵

(aaa.bbb.ccc.ddd is the static IP address assigned by your service provider for the PC, eee.fff.ggg.hhh is the subnet mask as signed by your service provider to PC)

> dhcpserver config confirm ↵

(confirm the new configuration)

> config save ↵

(save the new configuration)

> restart ↵

(after restart new configuration will take effect)

Advanced Confi

urations

Heritage Series ADSL Brid

e/ Router

Advanced Configurations

4-9

4.4 Changing DHCP client configuration

[System configuration]

PC 1

202.1.136.1

PC N

202.1.136.100

[ISP/DSLAM configuration]

IP address : 192.168.102.3 Subnet mask : 255.255.255.0 Gateway : None

[Local PC 1 configuration]

IP address : 202.1.136.101 Subnet mask : 255.255.255.0 Gateway : 202.1.136.xxx

The basic procedure to change the current setting is that you have to delete the existing configur ation and reentering new configuration.

> home ↵

> dhcpclient config ↵

(displays the current D HCP client configurat io n)

> dhcpclient config flush ↵

(deletes current D HCP client settings)

> dhcpclient config confirm ↵

(confirm the previous action)

> config save ↵

(save the new configuration)

> dhcpclient config ↵

(displays the current D HCP client configurat io n. Should be empty.)

Ethernet Port

HUB

Ethernet Port

202.1.136.xxx

Up-Link

DSLAM/NSP

192.168 .102.2

192.168.102.3

4-10

Advanced Confi

urations

Now add the new settings for DHCP client.

> ip device add Ethernet ether //edd dhcp ↵ > dhcpclient config add timeout 300; ↵ > dhcpclient config add retry 2000; ↵ > dhcpclient config add reboot 500; ↵ > dhcpclient config add backoff-cutoff 240; ↵ > dhcpclient config add interface “ethernet” { send

dhcp-client-identifier xx:xx:xx:xx:xx:xx; send dpch-lease-time 900; } ↵

(xx:xx:xx:xx:xx:xx is the Ethernet Mac address of your xDSL Router)

> dhcpclient config confirm ↵

(confirm the new configuration)

> config save ↵

(save the new configuration)

> restart ↵

(after restart new configuration will take effect)

Heritage Series ADSL Brid

e/ Router

Advanced Configurations

4-11

4.5 PPTP Tunneling Configuration

The xDSL Router can be configured to supports PPTP as following procedure. But the xDSL Router currently provides the PPTP Access Concentrator (PAC) end of a PPTP tunnel. And the PC must run an OS, which supports PPTP, providing a PPTP Network Server (PNS). Windows 98, Me, 2000 or Windows XP provide.

• PPTP d ial out

In the following example, the PC connects to the xDSL Router firstly must be configured as:

IP address of PNS : 192.168.10.1 Subnet mask of PNS : 255.255.255.0 Gateway of PNS : 192.168.10.2 IP address of PAC : 192.168.10.2

> ip device add Ethernet ether //edd 192.168.10.2 ↵ > config save ↵ > restart ↵

> ppp 2 pvc 0 32 ↵

(Set channel 2 to VPI=0, VCI=32)

> ppp 2 interface 0 ↵ > ppp 2 tunnel 1 pptp out ↵ > ppp 2 enable ↵

> pptp bind 192.168.10.2 ↵ > pptp 1 create listen ↵

> config save ↵ > restart ↵

4-12

Advanced Confi

urations

• PPTP d ial in

In the following example, the PC connects to the xDSL Router firstly must be configured as:

IP address of PNS : 192.168.10.1 Subnet mask of PNS : 255.255.255.0 Gateway of PNS : 192.168.10.2 IP address of PAC : 192.168.10.2

> ip device add Ethernet ether //edd 192.168.10.2 ↵ > config save ↵ > restart ↵

> ppp 2 pvc 0 32 listen ↵

(Set channel 2 to VPI=0, VCI=32)

> ppp 2 interface 0 ↵ > ppp 2 tunnel 1 pptp in ↵ > ppp 2 enable ↵

> pptp bind 192.168.10.2 ↵ > pptp 1 create 192.168.10.1 ↵ > config save ↵ > restart ↵

The PPTP configuration can be removed by following procedure. Please ensure to remove the PPTP configuration before set the xDSL Router to other configuration

• Remove PPTP either dial out or dial in

> ip device flush ↵ > config save ↵ > restart ↵

> ppp 2 pvc none ↵ > ppp 2 interface 0 ↵ > ppp 2 tunnel 0 ↵ > ppp 2 disable ↵

> pptp 1 delete ↵

Heritage Series ADSL Brid

> pptp bind none ↵ > config save ↵ > restart ↵

e/ Router

Advanced Configurations

4-13

4-14

Advanced Confi

urations

Heritage Series ADSL Brid

e/ Router

Managing the xDSL Router

5-1

Chapter 5 Managing the xDSL

Router

5.1 Booting the xDSL Router from Ethernet Network

By default, the Router is configured to boot from the on-board flash memory. But it is possible boot via Ethernet network as well. The executable image is stored in the local PC and is downloaded to the Router via Ethernet network upon every reset. For this, the Router needs to be configured and also a TFTP/BOO TP utility needs to be installed on the local PC.

! Router Configuration

# Turn off the Router and turn it on again # Keep the # At the ‘

prompt type

! Local PC Configuration

To download the software you need a TFTP/BOOTP server. You can use any. Be aware that every time the board is restarted the image will be transferred from the local PC to the Router.

* key be pressed

Boot from Ethernet, USB or Flash? (E/U/F)’

E ↵

ging

5-2

Mana

the xDSL Router

5.2 Upgrading on-board flash memo ry from Ethernet network

You can update the on-board flash memory after you booting the new firmware from the Et hernet network by issue the following commands.

> home ↵ > flashfs rewrite boot.bin ↵

(

this command is available for update boot code only)

> flashfs update ↵ > flashfs ls

You should see some messages about the file name and file sizes that stored in the Router. If you get “ wrong.

↵

no flash content” something went

Heritage Series ADSL Brid

e/ Router

Managing the xDSL Router

5-3

5.3 SNMP

The xDSL Router provides SNMP agent support standard MIBs. SNMP is also used internally for configuration of the router. The active SNMP agent within the Router accepts SNMP requests for status, statistics, and configuration updates. Communication with the SNMP agent occurs over the LAN or WAN connec tion. Any management application using SNMP over UDP/IP (U ser Datagram Protoco l /Internet Protocol) has access to the local SNMP agent. The following MIBs are supported:

! MIB II (RFC 1213) ! Bridge MIB (RFC 1493) ! PPP/LCP MIB (RFC 1471) ! PPP/Security MIB (RFC 1472) ! PPP/IP MIB (RFC 1473) ! PPP/Bridge MIB (RFC 1474)

ging

5-4

Mana

the xDSL Router

Heritage Series ADSL Bridge/ Router

xDSL Link Performance Statistics

6-1

Chapter 6 xDSL Link

Performance Statistics

To see the xDSL link performance statistics, you can use the serial console port or the Ethernet interface to access the command line interface.

After power up wait till Router has reached “SHOWTIM issued at the ‘<dsl>’ prompt to retrieve various measurements. Refer to chapter 7 for the details of <dsl> process commands.

xDSL

LED glows steadily. This condition indicates

”. Now <dsl> process commands can be

6-2

xDSL Link Performance Statistics

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

Chapter 7 Command Sets for

Command Line Interface

Command line interface conventions

! Command line leng th may be up to 90 characters long. ! The command line interface is case-sensitive ! Parameters in between [ and ] are optional ! Parameters in between < and > must be entered ! The command line interface prompts for commands with a prompt

that indicates the identity of the system. It determines how to indicate the identity as follows :

# If the SNMP MIB variable sysName.0 exists and is

non-empty, that is used first;

# Otherwise, if a local IP address exists, that is used; # Otherwise, the local MAC address is used.

For example, the prompt might look like one of the following

DSL>

192.168.7.1>

0:30:eb:ff:0:ff>

7-1

7-2

Command Sets for Command Line Interface

Basic system command sets

1. <process>, <process> <command>

Syntax:

<process> version

home

home <command>

Description:

In these commands, “

names known to the console as follow ing :

ppp

snmp

config

bridge

nat

dsl

isfs

flashfs

The former variant sends the command to the process. The latter

variant remembers the process name, and sends subsequent

commands to the process, as if they had been preceded by the process

name, until the command “

reflect this; moreover, if a “

issued, it is passed to the process as usual, but then information about

home” command is appended to the process’s output by the

the “

console.

Example:

DSL> isfs help

Commands are:

ls rm cat

Type 'help all' or 'help <command>' for more details

DSL> isfs

DSL isfs> help

Commands are:

ls rm cat

Type 'help all' or 'help <command>' for more details

DSL isfs> home

DSL>

<process>” can be any of a list of pr oc ess

home” is issued. The prompt is changed to

help” command with no arguments is

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

When the console is at the prompt of a particular process, the

command "

home <command>" or "home <process> <command>" may be

used to execute a command as if the user had typed "home" followed

<command>" or "<process> <command>". However, the console

by "

will remain at the same process prom pt. The command "

process "

" will change the prompt from the current process to a new

<process>".

home

Example:

DSL> conifg

DSL config> help

Commands are:

print reset save

Type 'help all' or 'help <command>' for more details

DSL config> home help

Commands are:

dsl bridge config flashfs ip

isfs nat ppp restart snmp

system

Type 'help all' or 'help <command>' for more details

DSL config> home flashfs help

Commands are:

cat ls update

Type 'help all' or 'help <command>' for more details

DSL config> home isfs

DSL isfs> help

Commands are:

ls rm cat

Type 'help all' or 'help <command>' for more details

DSL isfs> home

DSL>

2. help

Syntax:

help

help <cmd>

help all

<process> help

<process> help all

Description:

Displays a summary of available commands, more detailed

information on a particular command, or more detailed information

on all commands.

Example:

7-3

7-4

DSL> ip help

Commands are:

Type "help all" or "help <command>" for more details

DSL> ip help arp

arp syntax:

Command Sets for Command Line Interface

arp config device disable enable help ipatm nat norelay ping relay rip route routes stats subnet

arp <cmd> - execute arp subcommand arp help - list subcommands available

3. . (history mechanism)

Syntax:

Description:

Repeats the previous console command.

Example:

DSL> ip help arp

arp syntax:

arp <cmd> - execute arp subcommand arp help - list subcommands available

DSL> .

arp syntax:

arp <cmd> - execute arp subcommand arp help - list subcommands available

4. restart

Syntax:

restart

Description:

Reboots the Router

5. system

Syntax:

system

Description:

Displays the system type, firmware version and other information.

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

7-5

Commands for ISFS and FLASHFS process

1. ISFS and FLASHFS overview

The Router requiring storage of confi guration data should make use of the ISFS file system. The FLASHFS file system provides permanent storage of files and is not normally used other than at start of day or when re-writi ng the FLASH. In addition to configuration files, FLASHFS stores the firmware image, which is loaded after system restart. After system restart and during system initialization, FLASHFS files are copied into ISFS so that they are a ccessible by application processes. Typically, applications use the ISFS files to s tore their configuration data. Changes made to the configuration can be written back into ISFS, and subsequently FLASHFS, with the ‘

config save’ command. During a

FLASHFS update, all configuration files in ISFS are written back to FLAS H irrespective of whether they have changed or not. Normally the firmware image is not rewritten. The FLASHFS configuration files can be considered the ‘master’ copies, and the ISFS files the run time copies. If the ISFS copies are written back to the FLASHFS, the current settings will be preserved. It is possible to read files from FL A SHFS directly though this use is deprecated.

2. isfs cat | flashfs cat

Syntax:

isfs cat <file>

flashfs cat <file>

Description:

The

cat command allows a console user to view the contents of the

specified file. Only printable characters are displayed, non-printable

characters are represented by a ‘

include all standard printable characters together with carriage return,

line feed, and tab.

No output formatting is pe rformed, and no scroll l oc k function

implemented.

Example:

cat ipaddresses

.’ character. Printable characters

7-6

Command Sets for Command Line Interface

3. isfs ls | flashfs ls

Syntax:

isfs ls

flashfs ls [-l]

Description:

The

ls command allows a console user to list the files present in the

filesystem.

The FLASHFS ‘

address within FLASH and linked list information).

Example:

-l’ option displays more detailed information (logical

4. isfs rm

Syntax:

isfs rm <file>

Description:

The rm command allows the user to remove a file from the ISFS file

system. The memory used to store the file is freed .A subsequent

FLASHFS update will write the new, shorter, ISFS files into FLA SHFS,

providing an implicit rm function for FLASHFS.

Note: If the file removed is the only file that would be stored in

FLASHFS as type ‘

fixed file area will not be re-written during an update.

Example:

> isfs rm foo

fixed’, the file will remain in FLASHFS as the

5. flashfs update

Syntax:

flashfs update

Description:

The ‘

update’ command instructs FLASHFS to update the FLA SH

memory from the files contained in the ISFS file system.

Example:

> flashfs update

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

Commands for Bridge process

1. device add

Syntax:

device add <device>

Description:

This command adds a device to the bridge configuration. Attempts to

add the bridge itself or an existing device to the bridge are rejected.

Attempts to add unsupported devices are rejected. There is a limit on

the number of devices that can be attached to the bridge. If a device is

successfully added to the bridge, it will only become active after the

configuration is saved and the system is rebooted. If the device being

added is from a process which supports multiple devices, the

/DEVICE

attribute must be specified as part of the device name. The table below shows devices, which may be attached to the bridge, although not all systems may support all devices.

lec1 Forum LAN emulati on alecjade edd ppp

Ethernet driver bun_ethernet Point-to-Point prot ocol pp

Configuration saving saves this information.

Example:

DSL bridge> device add edd DSL bridge> device add ppp/DEVICE=2

2. device delete

Syntax:

device delete <device>

Description:

This command deletes a device from the bridge configuration. The changes will only take place after the configuration is saved and the system is rebooted. The syntax of the device name is the same as that for the Configuration saving saves this information.

Example:

DSL bridge> device delete edd

device add command.

7-7

7-8

Command Sets for Command Line Interface

3. device list

Syntax:

device list

Description:

This command lists all the devices that are currently attached to the bridge. It does not show the stored configuration (which can be seen with the

config print command).

Example:

DSL bridge> device list

4. ethertype

Syntax:

ethertype [<port> any|ip|pppoe]

Description:

This command enables filtering of Ethernet packets according to the

ETHER_TYPE field in the header. Only packets of the type specified

using this command will be sent on the port specified; packets of all types will always be received. By default, all bridge ports are set to “any”, which means that the type of the packet will never be checked. The meaning of the other options is as fol lows:

Option Permitted ETHER_TYPE values

“ip” 0x0800

“pppoe” 0x8863, 0x8864 – PPP Over Ethernet (RFC 2516)

0x0806 – ARP

The port is specified as an integer, as displayed by the command. When using this command in the initbridge configuration file, ports are numbered i n the order in which the

device add commands are given, starting from 1.

If no arguments are given, the current settings for each port are displayed.

Example:

DSL bridge> ethertype 2 any

– IP

device list

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

5. filter

Syntax:

filter

Description:

This command shows the current contents of the bridge’s filter table. The MAC entries for each device are shown in turn together with the time that the MAC address was last seen by the bridge. The command also shows the current filter ageing time, in seconds, and the number of creation failures since the system was started. Creation failures occur when there is no room left in the filter table for a new entry.

Example:

DSL bridge> filter

6. filterage

Syntax:

filterage [<age>]

Description:

This command sets, or displays if no a r guments are given, the filter table ageing time. The ageing time is the time after whic h MAC addresses are removed from the filter table when there has been no activity. The time is specified in second s and may be any integer value in the range 10…100,000 seconds. This value may also be changed through SNMP. Changing the value of filterage has immediate effect. Configuration saving saves this information. By default the filter ageing time is set to 300 seconds.

Example:

DSL bridge> filterage

6. flush

Syntax:

flush [<port>]

Description:

This command allows the MAC entries for a specified port, or a ll ports, to be removed from the filter table. The port number for a device may be determined using the commands. If the port number is omitted, all entries for all ports are removed from the filter table.

Example:

DSL bridge> flush

device list or status

7-9

7-10

Command Sets for Command Line Interface

7. portfilter

Syntax:

portfilter [<source port> all|<destination ports>]

Description:

The

portfilter command allows control over the bridge’s

forwarding and broadcasting behavior. By def ault, when a multicast or an unknown packet is received on a port (referred to above as the source port), it will be forwarded to all other bridge ports (referred to above as the destination ports). Ea ch brid ge port may have its behavior modified separate ly. T he first example below configures the bridge so that packets arriving on port 2 will only be forwa r d e d to ports 3, 4 and 5, and packets arriving on port 3 will only be forward e d to port 1. All other ports retain their default behavior. Note that this command does not force packets arriving on the source port to be sent to all specified destination ports. The bridge retains its learning behavior, so unicast packets, once their destination is known to the bridge, will still only be sent to one port. Note also that the bridge itself (for example when attached to the IP router) will always forward to all ports, and will always be forwarded to by all ports. The default behavior can be restored by calling this command with the argument “ specified as integers, as displayed by the When using this command in the are numbered in the order in which the given, starting from 1. If no arguments are given, the current settings for each port are displayed.

Example 1:

DSL bridge> portfilter 2 3 4 5 DSL bridge> portfilter 3 1

Example 2:

DSL bridge> portfilter 2 all DSL bridge> portfilter 3 all

all”, as shown in the second example. The ports are

device list command.

initbridge configuration file, ports

device add commands are

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

8. status

Syntax:

Status

Description:

This command shows the status of the bridge and its ports. The status information for a port inclu des the SNMP type information about time exceeded packets, packets discarded, etc. It also includes the broadcast history of t he port over the last five seconds and the high water mark of packets queued on the bridge for this device.

Example:

DSL bridge> status

9. spanning disable | enable

Syntax:

spanning disable spanning enable

Description:

When spanning tree operation is disabled, the bridge operates in transparent mode and all bridge ports are set to the forwarding state. When spanning tree operation is enabled, the state of the bridge’s ports is controlled by the spanning tree proces s.

status command reports the state of the spanning tree process.

The Configuration saving saves this informatio n. By default, spanning tree operation is enabled.

Example:

DSL bridge> spanning disable DSL bridge> spanning enable

10. spanning forw arddelay

Syntax:

spanning forwarddelay [<time>]

Description:

Reads or sets the time in seconds, i n which the bridge remains in the listening or learning states, and is used when the bridge is or is attempting to become the root bridge. The forward del ay time may be any value between 4 and 30 but it is also constrained by the maximum age and hello times. The forward de lay time may also by changed by SNMP command. The

forwarddelay times are constrained as follows:

maxage, hellotime and

7-11

7-12

Configuration saving saves this information. By default the forward delay time is set to 15 seconds.

Example:

DSL bridge> spanning forwarddelay 10 ;Sets the forwar ding

Command Sets for Command Line Interface

2 × (forwarddelay - 1) ≥ maxage maxage

≥ 2 × (hellotime + 1)

delay to 10 seconds.

11. spanning hellotime

Syntax:

spanning hellotime [<time>]

Description:

Reads or sets the time in seconds, after which the spanning tree process sends notification of topology change s to the root bridge, and is used when the bridge is or is attempting to become the root bridge. The hello time may be any value between 1 and 10 and is also constrained by the for warddelay and maxa ge times. The hello time may also be changed by SNMP command. Configuration saving saves this information. By default the hello time is set to 2 seconds.

Example:

DSL bridge> spanning hellotime 5 ;Sets the hello time

to 5 seconds

12. spanning maxage

Syntax:

spanning maxage [<time>]

Description:

Reads or sets the maximum age of received spanning tree protocol information before it is discarded, and is used when the bridge is or is attempting to become the root bridge. The maxage tim e may be any value between 6 and 40 and is also constrained by the forwarddelay and hellotime times. The maxage time may also be changed by SNMP command. Configuration saving saves this information. By default the maxage time is set to 20 seconds.

Example:

DSL bridge> spanning maxage 6 ;Sets the maxage

time to 6 seconds

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

7-13

13. spanni ng port <number>

The port commands, described in subsequent sections, control the configuration of the bridge’s ports so far as the operation of the spanning tree protoco l is c oncerned. Ports ar e numbered from 1. Every port on the bridge may be specified by typing port number.

all instead of a

14. spanni ng port <number> disabled | enable

Syntax:

spanning port <number> disable | enable

Description:

Allows a port to be disabled or enabled. The state of a port may also be changed by SNMP command. A port, which is enabled will take part in the operation of the spanning tree protoc ol. If enabled, the physical port may be “enabled” or “disabled” as demanded by the operation of the protocol. Configuration saving saves this information. By default ports are enabled.

Example:

DSL bridge> spanning port 1 enable ;Enables port 1 on

the bridge.

15. spanni ng por t <number> pathcost

Syntax:

spanning port <number> pathcost [<cost>]

Description:

Reads or sets the cost of using this port. The cost may be any number between 1 and 65535. The cost of t he port is used when deciding which is the best path to the root bridge. The cost of a port may also be changed by SNMP command. Configuration saving saves this information. By default a cost of 10 is assigned to a port

Example:

DSL bridge> spanning port 2 pathcost ;Displays the path

cost for port 2 on the bridge

7-14

Command Sets for Command Line Interface

16. spanni ng port <number> priority

Syntax:

spanning port <number> priority [<portpriority>]

Description:

Reads or sets the priority of the port. The priority may be any value between 0 and 255. The priority is used in conjunction with the pathcost to determine the best root to the root bridge. The higher the priority number, the less significant, in protocol terms, the port. The port priority may also be changed by SNMP command. Configuration saving saves this informatio n. By default a port has a priority of 128.

Example:

DSL bridge> spanning port 1 priority ;Displays the

priority for port 1 on the bridge

17. spanning priority

Syntax:

spanning priority [<bridgepriority>]

Description:

Reads or sets the priority of the bridge. The priority may be a ny va lue in the range 0 to 65535. The higher the priority number, the less significant, in protocol terms, the bridge. Where two bridges have the same priority, their MAC address is compared and the smaller MAC address is treated as more significant. The priority of the bridge may be changed by SNMP command. Configuration saving saves this information. By default the bridge is assigned a priority of 32768.

Example:

DSL bridge> spanning priority 4000 ;Sets the bridge

priority to 4000.

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

18. spanning status

Syntax:

spanning status

Description:

Reports the status of the spanning tree. If spanning tree operation is disabled, a message is printed to that effect and no other information is displayed. When spanning tree operati on is enabled, the following information is displayed:

• The identifier of the bridge.

• The identifier of the root bridge.

• The root port for this bridge.

• The root path cost: how far the bridge is from the root

• The various spanning tree time values as defined by the current

root bridge:

• The maximum age of spanning tree informat ion before it is discarded: max age time.

• The amount of time between configuration protocol packets: hello time.

• The amount of time delay when ports are changing state: forward delay time.

• For each port:

• The identifier of the designated bridge

• The identifier of the designated port for the designated bridge

• The identifier of the designated root bridge

Example:

DSL bridge> spanning status

7-15

7-16

Command Sets for Command Line Interface

Commands for DHCP server process

1. dhcpserver config

Syntax:

dhcpserver config [add <text>|confirm|delete|flush]

Description:

This command display s or edits the current c onfiguration of the DHCP server. To display current configurati on, provide no arguments to the command. Use of the “add” argument adds the line

<text> to the configuration file. Use of the “confirm” argument

reparses the configuration file, confirming the changes made if the parse is successful. Use of the “delete” argument deletes the last line from the configuration file. Use of the “flush” argument deletes the whole configuration. Following any change to the configuration file, it is necessary to “confirm” the changes, issue a “flashfs update” to commit the change to FLASH, and then restart the system before the changes can take effect.

Example:

DSL> dhcpserver config

--Current DHCP server configuration

--allow unknown-clients; allow bootp; subnet 192.168.219.0 netmask 255.255.255.0 { range 192.168.219.10 192.168.219.30; max-lease-time 5000; } DSL> dhcpserver config flush Configuration file flushed. DSL> dhcpserver config

--Current DHCP server configuration (Issue "dhcpserver config confirm" followed by "flashfs update" to confirm new configuration)

--DSL>

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

2. dhcpserver status

Syntax:

dhcpserver status

Description:

This command provides a summary of all leases known to the server on each interface in turn. It also shows remaining available IP addresses (i.e. those with n o specif ie d lease time, or client identifier).

Example:

DSL> dhcpserver status DHCP Server Lease Status Interface “ethernet”

IP address Client UID Expiry

192.168.219.1 01:00:20:af:20:6f:59 11 hours

192.168.219.2 01:00:20:af:11:2a:ac 8 hours

192.168.219.3 Myclient 140 seconds

192.168.219.4 00:20:af:20:00:2b:43 2 days

192.168.219.5 <unknown> Never

192.168.219.6 <unknown> Never

192.168.219.7 <unknown> Never

192.168.219.8 <unknown> Expired

192.168.219.9 <unknown> Expired

192.168.219.10 Foobarbozzle Expired

7-17

7-18

Command Sets for Command Line Interface

Commands for DHCP Client process

1. dhcpclient config

Syntax:

dhcpclient config

Description:

This command displays the current configura t ion of the DHCP client, including selected DHCP options.

Example:

DSL> dhcpclient config

---

DHCP client configuration file: ‘//isfs/dhclient.conf’ timeout 60; retry 60; reboot 10; backoff-cutoff 40; interface “ethernet” { send dhcp-lease-time 5000; send dhcp-client-identifier “Galapagos”; }

2. dhcpclient status

Syntax:

dhcpclient status [all]

Description:

This command provides DHCP status inf ormation for the active bound lease associated with each valid interface in turn, including IP address, time until lease renewal, subnet mask and DHCP server address. Including the “all” flag shows, for each valid interface, the active lease, leases which are being, or have been offered to the interface, and any leases which are still being held by the client which are not currently active (since a single interfa c e can only have one active lease at a time).

Example:

DSL> dhcpclient status DHCP Client Lease Status (active lease only) Interface ’ethernet’

Status Server ID IP address Subnet mask Renewal

*ACTIVE* 192.168.219.151 192.168.219.1 255.255.255.0 31 seconds

3. ip device

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

Syntax:

ip device add <i/f> <type> <file> [mtu <size>] [<IP

address>|dhcp]

ip device

Description:

The ip device add command adds an interface to the configuration of the IP stack. The last parameter of the command would normally the IP address of the interface; use of the string dhcp causes the IP address to be discovered by the DHCP client software. Note that using the flag dhcp on an interface precludes running a DHCP server on that interface! The ip device command lists the current configuration of any devices a ttached to the IP stack. A device configured to use DHCP will show

“dhcp” in the “IP address” column,

followed by the actual IP address discovered and bound by DHCP, if any. For interfaces configured to use DHC P, saving configuration only marks the interface as using DHCP; it d oes not save the actual IP address discovered by DHCP, which must be renewed.

Example:

DSL> ip device add ethernet ether //edd dhcp

…DHCP then discovers the IP address for the interface…

DSL> ip device # type dev file IP address device ethernet ether //edd mtu 1500 dhcp

Commands for IP process

7-19

7-20

Command Sets for Command Line Interface

1. arp

Syntax:

arp add <i/f> <IP address> <MAC address> arp delete <i/f> <IP address> arp flush arp [list] arp help [all|<cmd>]

Description:

Allows display and manipulation of the ARP table: the list of IP addresses and corresponding MAC addr esses obtained by ARP on Ethernet-like interfaces. Normally there is no need to ad d entries to the table with “arp add”, since they should be discovered by the ARP protocol. Displaying the table with “arp list” (or just “arp”) is sometimes useful, and deleting an entry with “arp delete”, or the whole table with “arp flush”, can sometimes speed up recovery from temporary proble ms if something unusual has happened. Entries added with “arp add” do not time out like those discovered by use of the ARP protocol, but they are deleted by “arp flush” and will not survive a restart (they are not saved by configuration saving). Note that the ARP table is used only for destinations on directly connected Ethernet -like networks, not for those reache d through routers (although the ARP table may be used to discover the MAC address of the router).

Example:

DSL> ip arp add ether 192.168.50.1 8:0:20:19:9A:D9 DSL> ip arp arp add flane 192.168.2.63 00:20:2b:e0:03:87 # 8m58s arp add flane 192.168.2.109 00:20:2b:03:08:b1 # 2m24s arp add ether 192.168.50.1 08:00:20:19:9a:d9 # forever arp add ether 192.168.50.57 00:20:af:2e:fa:3c # 3m25s DSL> ip arp delete flane 192.168.2.109 DSL> ip arp list arp add flane 192.168.2.63 00:20:2b:e0:03:87 # 8m46s arp add ether 192.168.50.1 08:00:20:19:9a:d9 # forever arp add ether 192.168.50.57 00:20:af:2e:fa:3c # 3m13s DSL> ip arp flush DSL> ip arp # flane ARP table is empty # ether ARP table is empty DSL> ip arp arp add flane 192.168.2.108 00:20:2b:03:0a:72 # 10m58s # ether ARP table is empty

(The last example shows that the MAC address for 192.168.2.108 has

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

been automatically added again, having been discovered by means of the ARP protocol.)

2. config

Syntax:

config [save]

Description:

Displays the IP configuration (not includi ng the “snmp” configuration), or saves it in flash memory. The functionality of the “config” command is also accessible in the standard way through the config process (e.g. “config print ip”), if that process is present. However, when accessed through the config process, the “snmp” configuration is included.

Example:

DSL> ip config device add ether ether //nice mtu 1500 192.168.2.1 device add vlane ether //lane mtu 1500 192.168.55.1 subnet add vlane.home . 192.168.55.0 ff:ff:ff:00 subnet add ether.home . 192.168.2.0 ff:ff:ff:00 rip send ether 2 rip send vlane 2 rip accept ether 1 2 rip accept vlane 1 2 autoloop on route add default 0.0.0.0 192.168.2.7 00:00:00:00 2 # MAN relay ether ether relay ether vlane relay vlane vlane ipatm lifetime 60 # IP host table: # Port table: router 520/UDP snmp 161/UDP tftp 69/UDP telnet 23/TCP DSL> ip config save Updating flash filing system ... done ip: configuration saved

3. device

Syntax:

device

7-21

7-22

device add <i/f> <type> [<file>] [mtu <size>] [<IP address>] device delete <i/f> device flush

Command Sets for Command Line Interface

Description:

Displays the interfaces that IP is configured to use, or adds an interface to the configuration, or deletes an interfa ce, or all interfaces, from the configuration. However, the commands to change the configuration do not take effect immediatel y (except when the “device add” command is run at star t-up from the initialisation file). It is necessary to save the configuration (e.g. with “ip config save”) and restart the system (e.g. with “ip restart”) before they take effect. “device” will display both the current interfaces and those that have been configured but are not yet in effect. (Other commands apply only to the devices in effect, rather tha n to those configured; when adding a device, for example, one may need to issue the “device add” command, then the “config save” and reboot, then issue any other configuration commands that depend on the e xistence of the device, and then “config save” again.) “<i/f>” is an arbitrary label for the interface, which is used in referring to it in subsequent commands. (It is often chosen to be the same as “<type>”, though this is perhaps slightly confusing.) “<type>” specifies the class of interface: Ethernet-like, IP-over-ATM, or loopback. For an Ethernet-like or IP-over-ATM interface, “<file>” specifies the file name that will be opened to a ccess the underlying device. For a loopback interface, “<file>” is not used, and can just be specified as “-“ or omitted altogether. Several different values of “<type>” specify the same class of interface; they differ in that each implies a different default value for “<file>”. As a result, for the most common interface configurations, “<file>” can be omitted, and one nee d only specify the appropriate value of “<type>”. The supported values for “<type>” are

Class <type> Default file

Ethernet ether //nice or

//ethernet or

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

//edd vlane //lane flane //lec1 bridge //bridge

IP-over-ATM atm //q93b

atmpvc //atm

Loopback loop - “<mtu>” specifies the MTU (maximum transmission unit); that is, the size of the largest datagram (excluding media-specific headers) that IP will attempt to send through the interface. The value specified will be ignored if it is larger than the maximum supported by the interface class, which is currently 1500 except for the loopback interface, unless the IP-over-ATM MTU has been changed; normally there is no point in setting the MTU less than this, so the “<mtu>” opti on is of little use. “<IP address>” is the IP address that this system uses on the interface ; if it is not specified, the interface will be disabled until a n IP address is supplied with the “ip enable” command. For a loopback interface, the address should be set to 127.0.0.1. (All addresses of the form 127.*.*.* will then be recognized as loopback addresses, as is normal practice.) For non-loopback interfa ces, the subnet mask for the local network will be assumed to be ff:f f : ff:00 (e.g. a class C network); if the correct subnet mask is other than this then it will need to be set with the “subnet” command. If there is no initialisation file //isfs/resolve (or //isfs/arptable) at all, then default in terfaces are configured as if by the “device” commands

device add ether ether //edd device add ether ether //nice (otherwise)

device add atm atm //q93b

but in each case only if the file concerned ( “//edd”, “//nice”, or “//q93b”) can be opened. Further mor e , if the IP process is given a command line then each argument wi ll be treated as a possible Ethernet-like file to open, given names “ether1”, “ether2”, and so on. For example, if the IP process is defined in the system file as “Process ip is tcp_ip/ip //bridge //lec1 ” (and “//bridge” and “//lec1” can be opened), then the equivalents of the commands

device add ether1 ether //bridge device add ether2 ether //lec1

will be processed, in addition to the others above.

7-23

7-24

Command Sets for Command Line Interface

Configuration saving saves the interface conf iguration.

Example:

DSL> ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.55.1

DSL> ip device add loop loop 127.0.0.1 Change will have no effect until after config save and restart. DSL> ip device delete vlane Change will have no effect until after config save and restart. DSL> ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.55.1 # DELETED device loop loop - mtu 2048 127.0.0.1 # ADDED Additions/deletions will have no effect until after config save and restart.

4. disable

Syntax:

disable [<i/f>]

Description:

Disables all interfaces, or just a specified interface.

Example:

DSL> ip disable vlane DSL> ip device

# type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.55.1 # DISABLED

5. enable

Syntax:

enable [<i/f> [mtu <size>] [<IP address>]]

Description:

Enables all interfaces, or just a specified interface. Can a lso be used to set the MTU and IP address on an interface when enabling it (or change them on an interface that is already enabled); see the “device” command for details on these. Configuration saving saves the MTU and IP addresses, but not the disabled/enabled state.

Example:

DSL> ip enable vlane 192.168.56.3 ip/vlane: IP address 192.168.56.3

Heritage Series ADSL Brid

DSL> ip device # type dev file IP address device ether ether //nice mtu 1500 192.168.2.1 device vlane ether //lane mtu 1500 192.168.56.3

Command Sets for Command Line Interface

e/ Router

6. get

Syntax:

get <file>

Description:

Reads and executes commands from a file. The commands in the file are in the same format as those documented in this chapter, with no “ip” prefix. They can contain comments, introduced by the “#” character. The “get” command is “hidden”, not shown by “ip help”.

Example:

DSL> ip get //isfs/cmdfile

7. ipatm abort

Syntax:

ipatm abort <n>

Description:

Closes an IP-over-ATM SVC; the number <n> is as displayed by “ipatm files”. If there is still traffic being sent to the destination concerned, IP will soon open a new SVC to t he de stination.

Example:

DSL> ip ipatm abort 14

8. ipatm arp

Syntax:

ipatm arp [list]

Description:

Lists the cached mappings from IP addresses to ATM addresses; only relevant when using IP-over-ATM with S VCs. ( T he “list” parameter is optional and makes no difference to the behavior.)

Example:

DSL> ip ipatm arp

192.168.5.72 47.00.83.10.a2.b1.00.00 .00.00.00.00.00.00.20.2b.01.00.07.00

192.168.5.33 47.00.83.10.a4.00.00.00 .00.00.00.00.00.00.20.2b.01.00.19.00

192.168.5.111 47.00.83.10.e2.00.00.00.20.2b.01.01.a8.00.20.2b.01.01.a8.00

9. ipatm arpserver

Syntax:

ipatm arpserver [<i/f> [<ATM address>|here]]

7-25

7-26

Command Sets for Command Line Interface

Description:

Displays or sets the ATMARP server used for an interface, which must be an IP-over-ATM interface using SVCs. The interface name is optional when displaying: if omitted, the ATMARP servers for all such interfaces are listed. (Since currently there can only be one such interface, this behavior is present only for possible consistency with future versions.) The parameter “here” causes no ATMARP server to be used; only the local ATMARP cache will be consulted when setting up an SVC. This will normally be used when this machine is the ATMARP server for the local network. Configuration saving saves this information.

Example:

DSL> ip ipatm arpserver ipatm arpserver atm here DSL> ip ipatm arpserver atm 47.0.83.10.a2.0.0.0.0.0.0.0.0.0.20.2b.4.3.8.0 DSL> ip ipatm arpserver atm ipatm arpserver atm

47.00.83.10.a2.00.00.00.00.00.00.00.00.00.20.2b.04.03.08.00

10. ipatm files

Syntax:

ipatm files

Description:

Lists the IP-over-ATM connections, listens, and slots for available connections.

Example:

DSL> ip ipatm files i/f atm 0 transmissions queued, 6 free connections, 4

listeners

0: on atm Connected to 192.168.220.48, 2 rx buffers idle 0ms 1: on atm Listening, 1 rx buffers (in use) 2: on atm Listening, 1 rx buffers (in use) 3: on atm Listening, 1 rx buffers (in use) 4: on atm Listening, 1 rx buffers (in use) 5: on atm Idle, 0 rx buffers 6: on atm Idle, 0 rx buffers 7: on atm Idle, 0 rx buffers 8: on atm Idle, 0 rx buffers 9: on atm Idle, 0 rx buffers 10: on atm Idle, 0 rx buffers

11. ipatm lifetime

Syntax:

ipatm lifetime <secs>

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

Description:

Displays or sets idle time-out for IP-over-ATM S V Cs: if there is no traffic on an SVC for this period, then it will be disconnected. (It might be disconnected be fore this period in order to make room for new connections.) T he re is no way to disable the time-out, but “ip ipatm lifetime 999999” will have much the same effect. Configuration saving saves this information. The default lifetime is 6 0 seconds.

Example:

DSL> ip ipatm lifetime Idle lifetime for connections: 1m DSL> ip ipatm lifetime 90 Idle lifetime for connections: 1m30s

12. ipatm pvc

Syntax:

ipatm pvc ipatm pvc add <i/f> <vci>/[<IP address>][/<pcr>] [<port>] ipatm pvc delete <vci> [<port>] ipatm pvc flush

Description:

Lists configured PVCs for use by IP-over-ATM; conf igures another; deletes one; or deletes all. “<i/f>” is the name of an interface configured for IP-over-ATM using PVCs. “<vci>” is the VCI to use for the PVC. The range of possible VCIs depends on the system. “<IP address>” is the IP address of the machine at the other end of the PVC. If it is not specified, TCP/IP will use Inverse ATMARP (RFC

1577) to determine the IP address; if it is specified, then Inverse ATMARP will not be used. “<pcr>” is the peak cell rate, in cells per second. The default is 60000. (If neithe r IP address nor PCR is specified, the “/” after the VCI can be omitted.) “<port>” is the port name: it must be specified if the ma chine is a switch, and not otherwise . Configuration sa ving saves this information.

Example:

myswitch> ip ipatm pvc add atm 60 a3 myswitch> ip ipatm pvc add atm 61//50000 b1

7-27

7-28

myswitch> ip ipatm pvc add atm 62/192.168.4.32 b1 myswitch> ip ipatm pvc ipatm pvc atm 60//60000 A3 ipatm pvc atm 61//50000 B1 ipatm pvc atm 62/192.168.4.32/60000 B1

Command Sets for Command Line Interface

13. iphostname

Syntax:

iphostname add <IP address> <name> iphostname flush iphostname list iphostname help [all|<cmd>]

Description:

Sets up a mapping between an IP address and a symbolic name; deletes all such mappings; lists t he mappings; or displays he lp on the “iphostname” command. The symbolic names can be used in most IP commands where an IP address is required, and as values of the attributes LHOST and RHOST. They are also displayed and returned as attribute values in place of numerical add r esses, when a suitable mapping exists. The “iphostname” command is “hidden”, not shown by “ip help”. Configuration saving saves this information.

14. norelay

Syntax:

norelay [all | <i/f> [<i/f>] [forward]]

Description:

Turns off forwarding between interfaces; see the “relay” command for more details. The command “norelay” with no parameters is equivalent to “norelay all”: it turns off all forwarding. Configuration saving saves this information.

Example:

DSL> ip relay relay ether ether relay ether vlane relay vlane vlane DSL> ip norelay ether vlane forward relay ether ether relay vlane ether forward

Heritage Series ADSL Brid

relay vlane vlane

Command Sets for Command Line Interface

e/ Router

15. ping

Syntax:

ping <IP address> [<ttl> [<size>]]

Description:

Sends an ICMP Echo me ssage to the specified IP address. “<ttl>” (default 30) is the TTL (time-to-live) to use. A crude “traceroute” functionality can be obtained by repeating the “ping” command with increasing TTL values, starting with 1. “<size>” (default 56) is the data size of the Echo message. This does not include the IP header (20 bytes) and the ICMP header (8 bytes). TCP/IP waits 10 seconds for a reply to the message; if none arrives, it reports the lack of a reply. A reply is an ICMP Echo Reply message, or an ICMP error message reporting destination unreachable, time exceeded, or (as should ne ver happen) a parameter problem. ICMP redirect and source quench messages are reported, but TCP/IP continues to wait for a final reply or time-out.

Example:

DSL> ip ping 192.168.4.13 1 ip: ping - 192.168.1.9 reports pkt #5834 to 192.168.4.13:

time-to-live

exceeded DSL>

ip ping 192.168.4.13 2

ip: ping - reply received from 192.168.4.13 DSL>

ip ping 192.168.77.77

ip: ping - no reply received

16. portname

Syntax:

portname add <name> <number>[/<protocol>] portname flush portname list portname read <file> portname help [all|<cmd>]

Description:

Sets up a mapping between a UDP or TCP port and a symbolic name; deletes all such mappings; lists t he ma ppings; reads the mappings from a file; or displays help on the “portname” command. The symbolic names can be used as values of the attributes LPORT and RPORT provided the protocol type (UDP or TCP) is a ppropriate. They are also displayed in place of port numbers, when a suitable

7-29

7-30

Command Sets for Command Line Interface

mapping exists.

<protocol>” should be either “UDP” or “TCP”; it can be omitted, but

“ that is not very useful. For “

portname read”, the file is in the same

format as //isfs/services, which is t he sa me as the output from

portname list”. The “portname” command is “hidden”, not sh own

“ by “

ip help”.

Configuration saving saves this information.

Example:

DSL> ip portname flush DSL> ip portname add someport 105/tcp DSL> ip portname list someport 105/TCP DSL> ip portname read //isfs/services DSL> ip portname list router 520/UDP snmp 161/UDP tftp 69/UDP telnet 23/TCP someport 105/TCP

17. relay

Syntax:

relay relay all | <i/f> [<i/f>] [forward]

Description:

Displays or sets what forwarding TCP/IP will do between interfaces. The combinations of setting forwarding can be a bit confusing; they behave as follows:

Command: Enables forwarding:

relay all from every interface to every

non-loopback interface

relay if1 from if1 to e very non-loopbac k interface,

and from every interface to if1

relay if1 forward

from if1 to every non-loopback interface

relay if1 if2 from if1 to if2 and from if2 to if1 relay if1 if2 forward

from if1 to if2 (Don’t confuse the “ forward” keyword, which i ndicates one-way relaying, with the term “forwarding”!) To disable forwarding, use the “norelay” command. Configuration saving saves this information. By default all

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

forwarding is disabled.

Example:

DSL> ip relay No relaying is being performed

DSL> ip relay ether vlane forward relay ether vlane forward DSL> ip relay ether forward relay ether ether relay ether vlane forward DSL> ip relay ether vlane relay ether ether relay ether vlane DSL> ip relay all relay ether ether relay ether vlane relay vlane vlane

18. rip accept

Syntax:

rip accept [all|<i/f>] [none|<version>*]

Description:

Controls for which ver sion or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723) TCP/IP will accept incoming information on each interface. Configuration saving saves this information. By default both RIP versions are accepted on all interfaces ( “rip accept all 1 2 ”).

Example:

DSL> ip rip accept all 1 2 DSL> ip rip accept ether 2 DSL> ip rip allowed rip send ether none rip send vlane none rip accept ether 2 rip accept vlane 1 2

19. rip allowed

Syntax:

rip allowed

7-31

7-32

Description:

Displays the RIP versions that will be accepted and sent on each interface.

Example:

DSL> ip rip allowed rip send ether 2 rip send vlane 2 rip accept ether 1 2 rip accept vlane 1 2

Command Sets for Command Line Interface

20. rip boot

Syntax:

rip boot

Description:

Broadcasts a request for RIP information from other machines. TCP/IP does this automatically when it first starts up, and the routing information should be kept up to d ate by regular broadcasts from the other machines, so this command is normally of little use.

Example:

DSL> ip rip boot

21. rip hostroutes

Syntax:

rip hostroutes [off]

Description:

Sets or clears the “hostroutes” flag; TCP/IP will accept RIP routes to individual hosts only if this flag is on. If the flag is off, then RIP version 1 routes that appear to be to individual hosts will be treated as if they were to the network containing the host; RIP version 2 routes to individual hosts will be ignored. (The reason for this difference is that RIP version 1 does not allow specification of subnet masks; a RIP version 1 route that appears to be to an individual host might in fact be to a subnet, and treating it as a route to the whole network may be the best way to make use of the information.) To see the state of the flag without changing it, the “config” command must be used. Configuration saving saves this information. By default the “hostroutes” flag is off.

Example:

DSL> ip rip hostroutes off

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

22. rip killrelay

Syntax:

rip killrelay <relay>

Description:

Deletes a RIP relay. See “rip relay” for information on RIP relays.

23. rip poison

Syntax:

rip poison [off]

Description:

Sets or clears the “poisoned reverse” flag. If this flag is on, TCP/IP performs “poisoned reverse” as defined in RFC 1058; see that RFC for discussion of when this is a good thing. To see the state of the flag without changing it, the “config” command must be used. Configuration saving saves this information. By default the “poisoned reverse” flag is off.

Example:

DSL> ip rip poison

24. rip relay

Syntax:

rip relay <RIP version> <name> [<i/f> [<timeout>]]

Description:

Configures a RIP relay. RIP relays were de signed as a means of using RIP on a non-broadcast medium (currently, only IP-over-ATM); on such an interface, TCP/IP will send RIP information individually to each configured RIP relay, instead of broadcastin g it. However, the RIP relay support has not been recently tested and is not believed to be reliable; furthermore, configuration saving does not save the RIP relay configuratio n. On a non-broadcast medium, therefor e, it is preferable to use static (manually configured ) routes.

25. rip relays

Syntax:

rip relays

7-33

7-34

Command Sets for Command Line Interface

Description:

Displays the configured RIP rela ys. S ee “ information on RIP relays

rip relay” for

26. rip send

Syntax:

rip send [all|<i/f>] [none|<version>*]

Description:

Controls which version or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723). TCP/IP will use to broadcast routing information on each inte r face. If both versions are specified, routing information is broadcast in d uplicate, once using each version. Specifying “all” affects all interfaces except the lo opback interface (if any). Configuration saving saves this informatio n. By default RIP version 2 only is used on all non-loopback interfaces ( “rip send all 2”).

Example:

DSL> ip rip send all 2 DSL> ip rip send ether 1 DSL> ip rip allowed

rip send ether 1 rip send vlane 2 rip accept ether 1 2 rip accept vlane 1 2

27. route

Syntax:

route route add <name> <dest> <relay> [<mask> [<cost> [<timeout>]]] route delete <name> route flush

Description:

Lists routes; adds or deletes a static route; or deletes all routes. “<name>” is an arbitrary name specified to “route add” that can be used to delete the route using “route delete”. “<dest>” is the IP address of the network being routed to (only those bits of “<dest>” corresponding to bits set in “<mask>” are relevant). “<relay>” is the IP address of the next-hop gateway for the route. “<mask>” (default ff:ff:ff:00) is the subnet mask of the network being routed to, specified as four hexadecimal numbers separated by c olons. For example, 0:0:0:0 is a default route (matches everything without a

Heritage Series ADSL Brid

Command Sets for Command Line Interface

e/ Router

7-35

more specific route), ff:ff:ff:0 would matc h a Class C network, and ff:ff:ff:ff is a route to a singl e host. (Note: the default is not always sensible; in particular, if “<dest>” is 0.0.0.0 then it would be better for the mask to default to 0:0:0:0.) “<cost>” (default 1) is the number of hops counted as the cost of the route, which may affect the choice of route when the route is competing with routes acquired from RIP. (But note that using a mixture of RIP and static routing is not advised.) “<timeout>” (default 0, meaning that the route does not time out) is the number of seconds that the route will rema in in the routing table. Note that the routing table does not contain routes to the directly connected networks, without going through a gateway. TCP/IP routes packets to such destinations by using the information in the device and subnet tables instead. The “route” command (with no parameters) displays the routing table. It adds a comment to each route with the following information:

• How the route was obtained; one of MAN — configured by the “route” command RIP — obtained from RIP ICMP — obtained from an ICMP redirect message SNMP — configured by SNMP network management;

• The time-out, if the route is not permanent;

• The original time-out, if the route is not permanent;

• The name of the interface (if known) that w ill be used for the

route;

• An asterisk (“*”) if the route was added recently and RIP has not

yet processed the change (the asterisk should disappear within 30 seconds, when RIP next considers broadcasting routing i nf ormation). Configuration saving saves this information. (Only the routes configured by the “route” command are saved or displayed by “config”.)

Example:

DSL> ip route add default 0.0.0.0 192.168.2.3 0:0:0:0 DSL> ip route add testnet1 192.168.101.0 192.168.2 .34 DSL> ip route add testnet2 192.168.102.0 192.168.2.34 ff:ff:ff:0 1 60 DSL> ip route

route add testnet2 192.168.102.0 192.168.2.34 ff:ff:ff:00 1 # MAN 58s/1m via ether * route add testn et1 192.168.101.0 19 2.168.2.34 ff:ff:ff :00 1 # MAN via ether route add default 0.0.0.0 192.168.2.3 00:00:00:00 1 # MAN via ether

IBM Heritage User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual