expand accelarator - exos4.0userguide

7/31/2019 Expand Accelarator - Exos4.0UserGuide

1/328

Expand NetworksExpandOS 4.0

User's Guide

US Headquarters

103 Eisenhower ParkwayRoseland, NJ 07068

Telephone: +1-973-618-9000

Toll Free: +1-888-892-1250

Fax: +1-973-618-9254

2001 Expand NetworksPublication No. 99-123-24-08/01


2/328

ExpandOS 4.0 User's Guideii

Important NoticeThis guide is delivered subject to the following conditions and restrictions:

! This guide contains proprietary information belonging to Expand

Networks Inc. Such information is supplied solely for the purpose of

assisting explicitly and properly authorized users of the Expand product

series.

! No part of its contents may be used for any other purpose, disclosed to

any person or firm or reproduced by any means, electronic,

photographic or mechanical, without the express prior written

permission of Expand Networks, Inc.

! The text and graphics are for the purpose of illustration and reference

only. The specifications on which they are based are subject to change

without notice.

! The software described in this guide is furnished under a license. The

software may be used or copied only in accordance with the terms of

that agreement.

! Information in this guide is subject to change without notice. Corporate

and individual names and data used in examples herein are fictitious

unless otherwise noted.

Copyright 2001 Expand Networks Inc. All rights reserved.

ExpandOS 4.0, ACCELERATOR 2700, ACCELERATOR 4000 andAdaptive Packet Compression are trademarks of Expand Networks Inc.

Flex 2.5

includes software developed by the University of California,Berkeley and its contributors. Copyright

1990, The Regents of the

University of California. All rights reserved.

Other company and brand product and service names are trademarks or

registered trademarks of their respective holders.


3/328

Terms and Conditions of Saleiii

Terms and Conditions of SalePLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THE

PRODUCT. BY USING THE PRODUCT YOU AGREE TO BE BOUND BY THE TERMS AND

CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE WITH THE PROVISIONS OFTHESE TERMS AND CONDITIONS, PROMPTLY RETURN THE UNUSED PRODUCTS,

MANUAL, AND RELATED EQUIPMENT (WITH PROOF OF PAYMENT) TO THE PLACE OF

PURCHASE FOR A FULL REFUND.

AcceptanceThese terms and conditions of sale ("Terms and Conditions") are the terms and conditions upon which

Expand Networks, Ltd. and its affiliates and subsidiaries (together "Expand") make all sales. Expand

will not accept any other terms and conditions of sale, unless Purchaser and Expand have executed an

agreement that expressly supersedes and replaces these Terms and Conditions. Acceptance of all

purchase orders is expressly made conditional upon Purchaser's assent, expressed or implied, to the

Terms and Conditions set forth herein without modification or addition. Purchaser's acceptance of these

Terms and Conditions shall be indicated by Purchaser's acceptance of any shipment of any part of the

items specified for delivery (the "Products") or any other act or expression of acceptance by Purchaser.

Expand's acceptance is expressly limited to the Terms and Conditions hereof in their entirety without

addition, modification or exception, and any term, condition or proposals hereafter submitted by

Purchaser (whether oral or in writing) which is inconsistent with or in addition to the Terms and

Conditions set forth hereon is objected to and is hereby rejected by Expand.

Price and PaymentThe Purchaser agrees to pay the purchase price for the Products as set forth in Expand's invoice on the

date of installation. Purchaser shall bear all applicable federal, state, municipal and other government

taxes (such as sales, use and similar taxes), as well as import or customs duties, license fees and similar

charges, however designated or levied on the sale of the Products (or the delivery thereof) or measured

by the purchase price paid for the Products. (Expand's prices set forth on the front side of the invoice

does not include such taxes, fees and charges.) Unless otherwise specified, payment terms are COD in

United States Dollars. Expand, at its discretion, may require reasonable advance assurances of payment

through irrevocable bank letters of credit or otherwise. All unpaid invoices shall bear interest at an

amount equal to 1-1/2% of the outstanding balance per month (or the maximum rate of interest allowed

to be contracted for by law, whichever is less), commencing upon the date payment is due. Expand shallhave no continuing obligation to deliver Products on credit, and any credit approval may be withdrawn

by Expand at any time and without prior notice.

Title and Security InterestTitle to the Products shall vest in the Purchaser upon date of shipment of the Products to Purchaser.

Expand shall retain a security interest in the Products until the Products price and all other monies

payable hereunder are paid in full. The Purchaser shall execute, upon request by Expand, financing

statements deemed necessary or desirable by Expand to perfect its security interest in the Products.

Purchaser authorizes Expand to file a copy of the invoice, these Terms and Conditions or a financing

statement with the appropriate state authorities at any time thereafter as a financing statement in order to

perfect Expand's security interest. A financing statement may be filed without Purchaser's signature on

the basis of Expand's invoice or these Terms and Conditions where permitted by law. Purchaser shall

keep the Products in good order and condition until the purchase price has been paid in full and shall

promptly pay all taxes and assessments upon the Products or use of the Products.


4/328

ExpandOS 4.0 User's Guideiv

Risk of LossRisk of loss or damage to the Products shall pass to the Purchaser upon delivery of the Products to the

common carrier, regardless of whether the purchase price has been paid in full. Unless advised

otherwise, Expand may insure the Products shipped to full value and all such insurance costs shall befor the Purchaser's account. The Purchaser shall inspect the Products immediately upon receipt and shall

promptly file any applicable claims with the carrier when there is evidence of damage during shipping.

WarrantyEXPAND WARRANTS TO THE PURCHASER FOR A PERIOD OF NINETY (90) DAYS FROM

SHIPMENT THAT THE PRODUCTS SHALL BE FREE FROM DEFECTS IN MATERIAL AND

WORKMANSHIP AND SHALL PERFORM IN SUBSTANTIAL CONFORMANCE WITH

SPECIFICATIONS PUBLISHED BY EXPAND. EXPAND'S OBLIGATIONS UNDER THESE

TERMS AND CONDITIONS SHALL BE LIMITED SOLELY TO EXPAND MAKING, AT

EXPAND'S COST AND EXPENSE, SUCH REPAIRS AND REPLACEMENTS AS ARE

NECESSARY TO PLACE THE PRODUCTS IN GOOD WORKING ORDER AND TO CONFORM

THE PRODUCTS TO EXPAND'S PUBLISHED SPECIFICATIONS. THIS WARRANTY IS IN LIEU

OF ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT

LIMITATION, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE.

Product ReturnsReturn of Products purchased hereunder shall be governed by Expand's RMA policies in effect on the

date of the invoice. Expand reserves the right to modify or eliminate such policies at any time. The right

to return defective Products, as previously described, shall constitute Expand's sole liability and

Purchaser's exclusive remedy in connection with any claim of any kind relating to the quality, condition

or performance of any Product, whether such claim is based upon principles of contract, warranty,

negligence or other tort, breach of any statutory duty, principles of indemnity or contribution, the failure

of any limited or exclusive remedy to achieve its essential purpose, or otherwise. In the event Expand

issues a return authorization to Purchaser allowing Purchaser to return Product to Expand, Purchaser

will deliver the Product to Expand's address in the United States, if so required by Expand, and

Purchaser shall bear all applicable federal, state, municipal and other government taxes (such as sales,

use and similar taxes) as well as import or customs duties, license fees and similar charges, however

designated or levied, on any replacement Product to be shipped by Expand to Purchaser.

License GrantThe Products, though primarily composed of hardware components, contain software that is proprietary

to Expand or its licensors. Expand hereby grants to Purchaser, and Purchaser accepts, a personal

nonexclusive, nontransferable license to use the Program, in object code form only, and the

accompanying documentation (collectively referred to as the "Software") only as authorized in these

Terms and Conditions. The Software is licensed for Purchaser's internal use and the Software or any

derivative or by-product of the Software may not be used by, sub-licensed, re-sold, rented or distributed

to any other party. Purchaser agrees that Purchaser will not assign, sublicense, transfer, pledge, lease,

rent, or share Purchaser's rights under these Terms and Conditions. Purchaser shall not copy, modify,

reverse assemble, reverse engineer, reverse compile, or otherwise translate all or any portions of the

Software. The Software and the Documentation are proprietary to Expand and are protected under U.S.

and international copyright, trademark, trade secret and patent laws. All right, title, and interest in and to

the Software, including associated intellectual property rights, are and shall remain with Expand.


5/328

Terms and Conditions of Salev

Limitation of LiabilityIn no event shall Expand be liable for loss of profits, indirect, special, incidental, or consequential

damages (including, without limitation, loss of use, income or profits, losses sustained as a result of

personal injury or death, or loss of or damage to property including, but not limited to, property handledor processed by the use or application of the products) arising out of any breach of these Terms and

Conditions or obligations under these Terms and Conditions. Expand shall not be liable for any

damages caused by delay in delivery, installation, or furnishing of the Products hereunder. No action

arising out of any claimed breach of these Terms and Conditions or transactions under these Terms and

Conditions may be brought by either party more than two years after the cause of action has accrued.

Expand's liability under these Terms and Conditions shall in no event exceed the purchase price of the

Products.

DefaultThe failure of the Purchaser to perform its obligations under these Terms and Conditions including but

not limited to payment in full of the purchase price for the Products, or the filing of any voluntary or

involuntary petition under the Bankruptcy Code, insolvency, assignment for the benefit of creditors, or

liquidation of the Purchaser's business shall constitute a default under these Terms and Conditions and

shall afford Expand all the remedies of a secured party under the Uniform Commercial Code. In the

event of default, Expand may, with or without demand or notice to Purchaser, declare the entire unpaid

amount immediately due and payable, enter the premises where the Products is located and remove it,

and sell any or all the Products as permitted under applicable law. Expand may, in addition to any other

remedies which Expand may have, refuse to provide service on the Products under any applicable

maintenance agreement relating to the Products then in effect between the parties at the time of the

default.

IndemnityExpand shall defend or settle any suit or proceeding brought against Purchaser based on a claim that

Products sold hereunder constitutes an infringement of any existing United States patent, copyright or

trade secret providing that Expand is notified promptly in writing and is given complete authority and

information required for the defense. Expand shall pay all damages and costs awarded against

Purchaser, but shall not be responsible for any cost, expense or compromise incurred or made by

Purchaser without Expand's prior written consent. If any Products is in the opinion of Expand likely to

or does become the subject of a claim for patent infringement, Expand may, at its sole option, procurefor the Purchaser the right to continue using the Products or modify it to become non-infringing. If

Expand is not reasonably able to modify or otherwise secure the Purchaser the right to continue using

the Products, Expand shall remove the Products and refund the Purchaser the amounts paid in excess of

a reasonable rental for past use. Expand shall not be liable for any infringement or claim based upon use

of the Products in combination with other Products or with software not supplied by Expand or with

modifications made by the Purchaser.


6/328

ExpandOS 4.0 User's Guidevi

GeneralExpand shall not be liable for Expand's failure to perform or for delay in performance of Expand's

obligations under these Terms and Conditions if such performance is prevented, hindered or delayed by

reason of any cause beyond the reasonable control of Expand. These Terms and Conditions and therights and duties hereunder shall not be assignable by either party hereto except upon written consent of

the other. Purchaser agrees to pay to Expand any reasonable attorney's fees and other costs and expenses

incurred by Expand in connection with the enforcement of these Terms and Conditions. These Terms

and Conditions and performance hereunder shall be governed by and construed in accordance with the

laws of the State of New York. Each party acknowledges that it has read, fully understands and agrees

to be bound by these Terms and Conditions, and further agrees that it is the complete and exclusive

statement of the agreement between the parties, which supersedes and merges all prior proposals,

understandings and all other agreements, oral and written, between the parties relating to the subject

matter of these Terms and Conditions. These Terms and Conditions may not be modified or altered

except by a written instrument duly executed by both parties. If any provision of these Terms and

Conditions shall be held to be invalid, illegal or unenforceable, the validity, legality and enforceability

of the remaining provisions shall in no way be affected or impaired thereby. The failure of either party

to exercise in any respect any right provided for herein shall not be deemed a waiver of any right

hereunder.


7/328


8/328

ExpandOS 4.0 User's Guideviii

! Chapter 10, Upgrading ExpandOS, describes how to upgrade

ExpandOS to newer versions, using standard TFTP.

! Chapter 11, Command Reference, provides a reference for the

commands that are available for configuration of the ACCELERATOR.

! Chapter 12, LAN Resilience, describes HSRP configuration.


9/328

Introducing the ACCELERATOR Series1-1

ntrod

ucingtheAcceleratorSeries

I

Chapter 1

Introducing theACCELERATOR

Series

About This Chapter

This chapter provides an introduction to Expand's ACCELERATORs and

how they fit into a communications network. It also describes how to

access the ACCELERATOR configuration options.

This chapter includes the following sections:

! What are ACCELERATORs?, page 1-2, provides an overview of the

Expand ACCELERATOR Series, and illustrates why

ACCELERATORs provide an effective solution for increased network

performance.! ACCELERATOR Connection to a Network, page 1-7, describes

how ACCELERATORs are installed in an existing network.

! Configuration and Management, page 1-7, provides a basic

introduction to the range of configuration and management options

provided by the ACCELERATOR's operating system, ExpandOS.

! Installing the ACCELERATOR, page 1-8, describes where to find

installation information.

! Connecting to the Console, page 1-8, describes how to connect the

ACCELERATOR to a console.


10/328

ExpandOS 4.0 User's Guide1-2

What are ACCELERATORs?

ACCELERATORs are devices that enable the transparent acceleration of

data transmitted over a WAN. The ACCELERATORs dramatically expand

the bandwidth of existing WAN lines, while maintaining full transparency,

data integrity and network fairness. In fact, enterprise bandwidth can be

increased by as much as 100% to 400%.

This is very significant in today's IT world, in which the need for increased

bandwidth is a fact of life. Corporations see bandwidth as a strategic

communications resource that enables their business-critical applications to

run unhindered.

The challenge is to have the capacity to transmit ever-increasing amounts

of data in the shortest amount of time. The problem is that constantly

acquiring more bandwidth incurs recurring costs. Other solutions, such as

data compression, bandwidth management and protocol "enhancement"

have therefore been sought in order to address the need for increased

available bandwidth, with minimal costs.

The Expand ACCELERATOR Series offers an effective solution for

improving network performance. It provides a means of dramatically

expanding the effective bandwidth ofexisting WAN lines and multiplying

throughput, with a one-time financial outlay only.


11/328


ntrod


IHow the ACCELERATOR Works

The ACCELERATOR is a device that can be seamlessly integrated into an

existing network. The enhanced network options possible with the

ACCELERATOR include point-to-point over a private WAN link, and

point-to-multipoint over a Frame Relay line.

Private Line Network

In an ACCELERATOR-enhanced network on a private WAN link, two

ACCELERATORs are used. One ACCELERATOR is positioned at each

end of the line, between the WAN termination product (for example,

CSU/DSU) and the router.

The following diagram shows a typical installation of a T1 private line

equipped with the ACCELERATOR 4000:

A data packet is passed from the router to the ACCELERATOR, where it is

accelerated using Expand Networks' unique Enterprise Caching technology.

The packet is transmitted over the WAN and reaches the second

ACCELERATOR. Here, the packet is reconstructed, and then passed to therouter and on to its final destination, arriving with no modification to the

packet whatsoever.


12/328


Frame Relay Network

In an ACCELERATOR enhanced network on a Frame Relay line, an

ACCELERATOR can be positioned at each end of each permanent virtual

circuit (PVC) on the WAN, between the CSU/DSU and the router.

The ACCELERATOR automatically identifies if there is another

ACCELERATOR at the other side of the PVC and handles the data

accordingly. If there is no unit at the other side, the ACCELERATOR

sends the data packets unaccelerated.

The following diagram shows typical integration of ACCELERATORs in a

Frame Relay network:

2700

27002700

4000

Frame RelayNetwork

Public or Private

Each ACCELERATOR can synchronize with every other

ACCELERATOR on the network, provided that there is a PVC established

between the sending location and the destination. A data packet is passed

from the router to the ACCELERATOR, where it is accelerated using

Enterprise Caching technology. The packet is then transmitted over the

appropriate PVC on the WAN, and reaches the ACCELERATOR at the

required destination location. Here, the packet is reconstructed, and then

passed to the router and on to its final destination, arriving with no

modification to the packet.

The possible number of PVCs handling accelerated data in a network is

determined by the memory capacity of the ACCELERATOR. The possiblenumber of unaccelerated PVCs is unlimited.


13/328


ntrod


ILAN Applications

In an ACCELERATOR enhanced IP network, an Expand Networks

ACCELERATOR can be positioned between the router and the WAN

termination device (e.g. CSU/DSU) or on the LAN side of the router.

The ACCELERATOR can be located either On-Path or On-LAN.

NOTE:

If you have a firewall placed in between the two routers, it is essential that you openaccess, in the firewall, for the IPcomp protocol or for the ACCELERATORs specificIP addresses.

On-Path

On-Path configuration places the ACCELERATOR between the LAN and

the router on both sides of the IP network. The data from the LAN segmentpasses through the ACCELERATOR before it reaches the router. The

ACCELERATOR changes the destination IP address of the accelerated

data, rerouting it via the far-end ACCELERATOR to be reconstructed

before it is passed on to its final destination IP address. See the sample

On-Path application in the following figure.

ACCELERATOR 4800 ACCELERATOR 4800

PUBLIC NETWORK

Data passes through and is accelerated before it reaches the router. In this

configuration, an internal-bypass circuit short circuits the two LAN ports

making the ACCELERATOR invisible to protect the network in the

unlikely event of failure.


14/328


On-LAN

On-LAN configuration places the ACCELERATOR directly on the LAN

as a host. The ACCELERATOR is considered the next hop for all traffic onthe LAN. The accelerated data is redirected to the far-end

ACCELERATOR where it is reconstructed before it reaches its final IP

address. See the sample On-LAN application in the following figure.

ACCELERATOR 4800

ACCELERATOR 4800

ACCELERATOR 4800

PUBLIC NETWORK

In this configuration, Hot Standby Routing Protocol (HSRP) or Virtual

Router Redundancy Protocol (VRRP) enables the ACCELERATOR to take

part in HSRP/VRRP groups with available routers (or even other available

ACCELERATORs) to provide backup in the rare case of ACCELERATOR

failure.

NOTE:

Usually, one ACCELERATOR is installed on the LAN segment. However, ifresilience is to be enhanced, two ACCELERATORs can be installed. Resiliencemethods are discussed in the ExpandOS Users Guide, version 4.0.


15/328


ntrod


I

ACCELERATOR Connection to aNetwork

An ACCELERATOR can be added to a network with minimal changes.

Each ACCELERATOR connects to the WAN using an industry-standard

interface, such as V.35, X.21, RS-530, DDS, T1 or E1.

NOTE:

Refer to the ACCELERATOR Series Hardware Installation Guidefor informationabout interface availability.

In a standard network configuration, one or more private or Frame Relay

lines provide point-to-point or point-to-multipoint connectivity between

various locations. Each line is likely to be connected to a router.

Acceleration on a line is achieved by connecting an ACCELERATOR ateach end of the line, or at either end of each PVC. The router may be

connected to the ACCELERATOR using one or two serial links. The

ACCELERATOR is completely transparent the router is not aware of its

existence.

Configuration and Management

ExpandOS can be managed either via a connected console, via SNMP or

via the Web User Interface.

The ACCELERATOR operating system, ExpandOS, provides a wide range

of management features. Most of these features are used for monitoring

purposes, since only minimal configuration is required.

The ACCELERATOR requires some basic initial configuration in order to

function. This configuration is performed locally using an RS-232 console,

and includes specifying the ACCELERATOR's IP address. The initial

configuration also involves defining passwords, and the time and date at the

ACCELERATOR site.


16/328


Installing the ACCELERATOR

The installation and connection procedures for the ACCELERATOR and

its cables, together with physical descriptions of the hardware, can be found

in the relevantACCELERATOR Series Hardware Installation Guide for

your ACCELERATOR model.

Connecting to the Console

After the ACCELERATOR is mounted on a rack or tabletop and the

required cables are connected to the back panel, the ACCELERATOR

should be connected to a console in order to access ExpandOS

configuration options. Use a local RS-232 terminal, such as

HyperTerminal, connected to the Console port on the back panel of the

ACCELERATOR.


17/328


ntrod


I! To connect t he console in ter face:

1 Connect the console cable to the console port and fasten the screws on

the connector.2 Connect the cable to the console terminal (an ASCII terminal or a PC

running terminal emulation software).

NOTE:

The diagram below shows the back panel of the ACCELERATOR 4000 as anexample.

Accelerator 4000

Console Port

PC

Accelerator 4000

Console Port

PC


18/328



19/328

Initial Configuration2-1

nitialConfiguration

I

Chapter 2

InitialConfiguration

About This Chapter

Following successful installation of the hardware, the ACCELERATOR is

powered on. It is then necessary to configure the ACCELERATOR via the

ACCELERATOR operating system, ExpandOS. The required parameters

are accessed using a local RS-232 console, since the first time that

ACCELERATOR is configured, it does not have an IP address. The cable

from the console is connected to the console port on the back panel of the

ACCELERATOR, as described in Chapter 1,Introducing the

ACCELERATOR Series.

This chapter includes the following sections:

! Accessing Configuration Options, page 2-2.! Defining the IP Address and the Default Gateway, page 2-4.

! Writing the Configuration to the Flash, page 2-5.

! Configuring Passwords, page 2-6.

! Configuring the Time and Date, page 2-6.

! Configuring the Modem, page 2-7.

! Monitoring the Power Supplies, page 2-9.

! Setting the Configuration Defaults, page 2-10.


20/328


Accessing Configuration Options

!To a ccess confi gur ati on opti ons:1 Run your terminal-based application, configuring it as follows:

Baud rate: 9600 bps

Parity: none

Data bits: 8

Stop bits: 1

2 Connect to ExpandOS Command Line Interface (CLI). Press

several times until the Expand prompt is displayed:

Password:

Expand>

NOTE:

A > symbol at the end of the Expand prompt indicates that configuration

options are disabled.

3 Type enable, and press to enable configuration. You will be

prompted for your password.

4 Type Expand(this is the factory default password) and press .

A # symbol at the end of the prompt indicates that configuration

options are enabled, as shown below.

Password:

Expand>Expand>enable

Password:

Expand#

NOTE:

It is recommended that you change the password. For further information, referto Configuring Passwords, on page 2-6.


21/328


nitialConfiguration

I

5 In Enable mode, type configure terminal, and press .

The Expand prompt is now followed by (config), indicating that

ExpandOS is now in Primary Configuration mode, as shown below:

Password:

Expand>

Expand>enable

Password:

Expand#

Expand #configure terminal

Expand (config)#

NOTE:

When entering commands, you can type in a unique command prefix insteadof the full command word and ExpandOS will recognize the command. Forexample, type conf for configure. If you press after typing the

unique prefix, the full command word will be displayed.


22/328


Defining the IP Address and the DefaultGateway

The IP address and default gateway of ExpandOS must be defined to enable

remote management.

! To defi ne th e IP ad dr ess:

1 In Primary Configuration mode, as described on page 2-3, type

interface ethernet 0(when using the ACCELERATOR

4000), and press . The eth0 prompt is displayed.

NOTE:

Ethernet 0 is the LAN interface connected to the LAN for managementpurposes.

6 Type ip address,followed by a space, then the actual IP address,

space, and then the subnet mask, for example,

ip address 10.0.214.3 255.0.0.0, and press , as

follows:

Password:

Expand>

Expand>enable

Password:

Expand#

Expand #configure terminal

Expand (config)#

Expand (config)#interface ethernet 0

Expand (eth0)#ip address 10.0.214.3 255.0.0.0

Expand (eth0)#

! To define the defa ult ga teway:

1 Press to return to Primary Configuration mode.

2 Type route-rules,and press to enter Route Rules

configuration mode. The route-rules prompt is displayed.


23/328


nitialConfiguration

I

3 Type ip default-gateway,followed by a space, and then the IP

address, as follows:

Expand (eth0)#^z

Expand (config)#route-rules

Expand (route-rules)#ip default-gateway 10.0.0.1

Expand (route-rules)#

3 Press .

NOTE:

The configuration must be saved to the flash in order for it to be available whenExpandOS is rebooted.

Writing the Configuration to the FlashExpandOS has three separate types of memory: RAM used for internal

processing, memory allocated for the cache and Flash memory for software

updates.

ExpandOS maintains its software and configuration on a flash. In order to

ensure that the configuration will be available when the system is rebooted,

it is necessary to write the configuration on the flash.

! To wri te the config ura tion to the f l ash:

1 If you are still in Primary Configuration mode, press to

return to the Enable prompt.

2 Type write, and press . A message is displayed, indicating

that the configuration is being built. A success message is displayed

when the process is complete.

NOTE:

If a fail message is displayed, contact your reseller's technical support

department for assistance.


24/328


Configuring Passwords

Passwords are required in order to access parameters in Enable mode, and

for the initial login. ExpandOS' default password is Expand.It is

recommended that this password be changed during the initial setup

process.

! To config ure a p assword for In it ia l Login m ode:

1 Enter Primary Configuration mode, as described on page 2-3.

2 Type line telnet, and press .

3 Typepassword, then a space followed by the required password, for

example,password ncc1701E, and press .

NOTE:

Passwords may consist of letters and numbers, and are case sensitive.

4 To save the password, follow the Writing the Configuration to the

Flash procedure, on page 2-5.

! To config ure a p assword for Enab le m ode:

1 Enter Primary Configuration mode, as described on page 2-3.

2 Type enable, and press . The enable prompt is displayed.

3 Typepassword, a space, and the required password.

4 To save the password, follow the Writing the Configuration to the


Configuring the Time and Date

A time and date of the ACCELERATOR can be defined. This time and date

are used for the internal system requirements of the device (i.e. generating

log files).

!To confi gu re th e ti me a nd da te o f t he ACCELERATOR:1 Enter Primary Configuration mode, as described on page 2-3.


25/328


nitialConfiguration

I

2 Type clock, and press . The clock prompt is displayed.

3 Type set, then a space followed by the date in dd-mmm-yyyy

format, where mmm represents the first three letters of the month (in

English), for example, 18-Sep-2001.

Type another space, then the time in hh:mm:ss format.

set 04-Jul-2001 10:30:00.

NOTES:

Entering a time is optional.

The time set on the ACCELERATOR can be checked at any time by typingshow clock at the prompt.

The ACCELERATOR has an option to be set to gather time information froman SNTP server.

4 To save the configuration, follow the Writing the Configuration to the


Configuring the ModemWhen you load an ACCELERATOR 4000/2700 with ExpandOS 3.5, you

can connect a modem to the Auxiliary port. Consequently, out-of-band

management can be performed for remote monitoring and configuration.

! To config ure th e modem :

1 In Primary Configuration mode, as described on page 2-3, typemodem,

and press to enter Modem configuration mode. The modem

prompt is displayed.

2 Type show, and press to view the default modem

configuration. The show prompt and sub-menus are displayed as

follows:

Modem

modemcap default

No Echo E0

No Result Codes Q1

On Hook H0


26/328


3 Typemodemcap edit, followed by a space and the name of the

modem. Type another space, then the name of the required modem

setting followed by the modem setting value, and press , for

example,modemcap edit Modem_1 NEC E1, to create a new

modem called Modem_1 and set the No Echo setting NEC to E1.

NOTES:

A new modem is created, unless otherwise specified, with the default settingsof NEC set to E0, NRS to Q1 and ONH set to H0.

The name of the modem is case sensitive.

4 Type show, and press to view the updated modem

configuration. The show prompt and sub-menus are displayed as

follows:

Modem

modemcap

Modem_1

No Echo E1

No Result Codes Q1

On Hook H0

default

No Echo E0

No Result Codes Q1

On Hook H0

! To alter t he modem type:

1 In Enable mode, type line auxiliary, and press to enter

Line Auxiliary configuration mode. The line auxiliary prompt is

displayed.

NOTE:

This feature is only available with an ACCELERATOR 4000 loaded withExpandOS 3.5.

2 Typemodem type, followed by a space and the modem name, and

press to alter the modem type.


27/328


nitialConfiguration

I

NOTES:

The command modem clear line clears the line by sending an initialization

AT string.

The command modem hang up hangs up the connection.

Monitoring the Power SuppliesThis feature enables monitoring of the dual power supplies. The events

command enables or disables this function, while the snooze-

intervalvariable defines the interval between alerts in hours.

With the ACCELERATOR 4000 Revision B, this is conditional upon the

physical existence of two power supplies, and when the show versioncommand is invoked, the ExpandOS 3.5 displays a message stating the

presence of redundant power supplies.

! To enabl e monitor ing of the power supply and set theinterval between a lerts:

1 In Primary Configuration mode, as described on page 2-3, type

power-check, and press to enter Power-check mode.

2 Type events on,and press , to enable redundant power

check events.

3 Type snooze-interval 24,and press , to set the snoozeinterval between alerts to 24 hours.

4 Type show, and press to view the updated power supplies

configuration:

power-check

events on

snooze-interval 24


28/328


Setting the Configuration Defaults

ExpandOS 3.5 offers three ways to set the configuration file of the

ACCELERATOR:

! reset-factory-default: This command resets the default

configuration by erasing the existing configuration.

! restore-factory-default: This command returns the current

configuration to the default settings.

! set-factory-default: This command ensures that the device

will always startup configured to the factory default settings.

! To set the configuration file of the ACCELERATOR:

1 In Enable mode, type reset-factory-default,

-or-

type restore-factory-default,

-or-

type set-factory-default.

2 Press .


29/328

Configuring the ACCELERATOR3-1

Chapter 3

Configuring theACCELERATOR

About This Chapter

This chapter describes how to configure interface parameters and routing

rules for the ACCELERATOR.

This chapter includes configuration guides for the following:

! Point to Point Networks

! Frame Relay Networks

! LAN Networks

! On-LAN Applications

! On-Path Applications

This chapter also includes step-by-step detailed procedures for all available

ExpandOS initial configuration options.

Configuration Guides

The following point-to-point, Frame Relay and LAN configuration guides

include sample applications drawings accompanied by sample basic

configuration task lists and commands.


30/328

ExpandOS User's Guide3-2

Point-to-Point Networks

In a point-to-point network, a direct line connects the two

ACCELERATORs, using PPP, HDLC or LAPB encapsulation. Thefollowing drawing shows a typical point-to-point configuration:

Different parameters are configured for the DCE and DTE connections to

the network, as described in the following sections of this chapter.

Sample Point-to-Point Configuration

The following sample configuration is based on the diagram above.

Expand#configure

Expand#interface serial 0/1

Expand(conf-if)#bypass

Expand(config-if)#interface ethernet 0

Expand(conf-if)#ip address 10.30.0.2 255.255.0.0

Expand(config-if)#interface serial 0/0

In X.21 Interfaces ONLY: set port 0/0 on the DTE side to RX External Only

Expand(config-if)#encapsulation autodetect

Expand(conf-if)#interface serial 0/1

Expand(config)#encapsulation autodetectExpand(conf-if)# exit


31/328


Expand(conf)#route-rules

Expand(route-rules)#bridge route serial 0/0 serial 0/1


Expand(route-rules)#routing-policy bridge-routing-firstExpand(route-rules)#exit

Expand#configure

Expand(conf)#interface serial 0/1

Expand(config-if)#no bypass

Wait a few seconds until the encapsulation has been automatically detected and then perfor

the following commands.

Expand(conf-if)#confirm autodetection



Point-to-Point Application Required Task List

! Connect the ACCELERATOR according to instructions in

ACCELERATOR Installation and Operation Guide (Required)

! Manually Activate Bypass Mode, (Optional)

for the duration of the device configuration (in the ACCELERATOR

4000 bypass is on Serial Port 0/1, in the ACCELERATOR 2700 Series,

bypass is on port 0/0)

! Set Ethernet Interface IP Address (Required)

(make sure to set the applications subnet mask) (port 0 in the

ACCELERATOR 4000, port 3/0 in the ACCELERATOR 2700 Series)

! In X.21 Interfaces ONLY: Set port 0/0 on the DTE side to RX External

Only

! Set Encapsulation Autodetect (Required)

(ports 0/0 and 0/1 in the ACCELERATOR 4000, ports 0/0 and 1/0 in

the ACCELERATOR 2700 Series)

! Set the following Route-Rules

! Define a Bridge Route from 0/0 to 0/1(ACCELERATOR 4000) or

from 0/0 to 1/0 (ACCELERATOR 2700 Series) (Required)

! Define a Bridge Route from 0/1(ACCELERATOR 4000) or from

1/0 (ACCELERATOR 2700 Series) to 0/0 (Required)


32/328


! Set Routing Policy to Bridge Routing First (Required)

! Manually Deactivate Bypass Mode (Optional)

! Confirm Encapsulation Autodetect (Required)



! Write the configuration to the ACCELERATOR

Frame Relay Networks

In a multipoint (Frame Relay) network, an ACCELERATOR can

synchronize with every other ACCELERATOR on the network. If there is

no unit at the other side of a PVC, the ACCELERATOR sends the data

packets unaccelerated.

The following diagram shows a typical Frame Relay configuration:

In a Frame Relay configuration, logical subinterfaces are defined or

autodetected for individual serial interfaces. These subinterfaces relate to

the other connections on the Frame Relay network with which the

ACCELERATOR communicates.


33/328


Each subinterface performs like a point-to-point serial interface, providing

a logical point-to-point connection. Configuration of each subinterface is

performed in the same way as for point-to-point configuration (with the

exception of encapsulation, which is set per entire interface). The physicalserial interface in a Frame Relay configuration acts as a binder for its

subinterfaces, so that commands specified for the serial interface will affect

all its subinterfaces.

Multipoint parameters are configured for the DCE and DTE connections to

the network, as described in Point-to-Point Networks, page 3-1. For the

purpose of the following procedures, Serial Interface 0/0 is configured as an

example. However, these procedures can be used to configure any serial

interface.

Sample Frame Relay Configuration


Expand#configure

Expand#interface serial 0/1

Expand(conf-if)#bypass

Expand(config-if)#interface ethernet 0


Expand(config-if)#interface serial 0/0

In X.21 Interfaces ONLY: set port 0/0 on the DTE side to RX External Only

Expand(config-if)#encapsulation autodetect


Expand(config)#encapsulation autodetect

Expand(conf-if)# exit

Expand(conf)#route-rules



Expand(route-rules)#routing-policy bridge-routing-first

Expand(route-rules)#exit

Expand#configure

Expand(conf)#interface serial 0/1


34/328


Expand(config-if)#no bypass

Wait a few seconds until the encapsulation has been automatically detected and then perform

the next two commands.

Expand(conf-if)#confirm autodetectionExpand(conf-if)#interface serial 0/0


Frame Relay Application Task List



! Manually Activate Bypass Mode, (Optional)

for the duration of the device configuration (in the ACCELERATOR

4000 bypass is on Serial Port 0/1, in the ACCELERATOR 2700 Series,

bypass is on port 0/0)

! Set Ethernet Interface IP Address (Required)

(make sure to set the applications subnet mask) (port 0 in the

ACCELERATOR 4000, port 3/0 in the ACCELERATOR 2700 Series)

! In X.21 Interfaces ONLY: Set port 0/0 on the DTE side to RX External

Only

! Set Encapsulation Autodetect (Required)




! Define a Bridge Route from 0/0 to 0/1(ACCELERATOR 4000) or

from 0/0 to 1/0 (ACCELERATOR 2700 Series) (Required)

! Define a Bridge Route from 0/1(ACCELERATOR 4000) or from

1/0 (ACCELERATOR 2700 Series) to 0/0 (Required)

! Set Routing Policy to Bridge Routing First (Required)


! Confirm Encapsulation Autodetect (Required)


the ACCELERATOR 2700 Series)! Write the configuration to the ACCELERATOR


35/328


LAN Configuration

LAN network configuration can be set up in three different ways:

! ACCELERATORs On-Path

! ACCELERATORs On-LAN

! Mixed configuration, one ACCELERATOR On-LAN and one

ACCELERATOR On-Path

On-Path Network Configuration

On-Path configuration places the ACCELERATOR between the LAN and

the router on both sides of the IP network. The data from the LAN segment

passes through the ACCELERATOR before it reaches the router. The

ACCELERATOR changes the destination IP address of the accelerated

data, rerouting it via the far-end ACCELERATOR to be reconstructed

before it is passed on to its final destination IP address.

For further explanation of On-Path configuration, refer to Chapter 1,

Introducing the ACCELERATOR Series.

The following is a typical On-Path application:

Sample On-Path Configuration


Expand#config

Expand(config)#interface ethernet 0/0Expand(conf-if)#bypass



36/328


Expand(conf-if)#interface ethernet 0/1

Expand(conf-if)#mode on-path wan-side connecting ethernet 0/0

Expand(conf-if)#router-ip 10.30.0.1

Expand(config)#interface tunnel 5 ipv4Expand(conf-tunnel-5)#tunnel source 10.30.0.6

Expand(conf-tunnel-5)#tunnel destination 10.20.0.6

Tunnel ID was set to 5

Source 10.30.0.6

Destination 10.20.0.6

Expand(conf-tunnel-5)#route-rules

Expand(route-rules)#routing-policy on-path-policy

Expand(route-rules)#ip route 10.20.0.0 255.255.0.0 tunnel 5

Expand(route-rules)#ip route 10.20.0.6 255.255.255.255 10.30.0.

Expand(route-rules)#interface ethernet 0/1Expand(conf-if)#no bypass

On-Path Application Task List



! Manually Activate Bypass Mode, for the duration of the device

configuration (in the ACCELERATOR 4000 bypass is on Serial Port

0/1, in the ACCELERATOR 2700 Series, bypass is on port 0/0)

(Optional)

! Set Ethernet Interface IP Address for Port 0/0 (Required)

! Set Mode to On-Path (Required)

! Set Router IP to the Next Hop Router (Required)

! Create an IP Tunnel (Required)

! Set IP Tunnel Source to Local ACCELERATOR Port 0/0 IP Address

(Required)

! Set IP Tunnel Destination to Remote ACCELERATOR Port 0/0 IP

Address (Required)


! Set Routing Policy to on-path-policy(Required)


37/328


! Define an IP Route Directing Transmissions Sent to the Far-End

Network into the Tunnel (Required)

! Define an IP Route Directing Tunnel Traffic to the Next Hop Router

(Required)

! Set the IP Default Gateway to the IP Address of the Router

(Required)


On-LAN Network Configuration

On-LAN configuration can be set up in two ways: Basic On-LAN

configuration and On-LAN configuration with HSRP support.

BasicOn-LAN

BasicOn-LAN configuration places the ACCELERATOR directly on the

LAN as a host. The ACCELERATOR is considered the next hop for all

traffic on the LAN. The accelerated data is redirected to the far-end

ACCELERATOR where it is reconstructed before it reaches its final IP

address. See the sample On-LAN application in the following figure.


38/328


Sample Basic On-LAN Configuration


Expand#config

Expand(config)#interface ethernet 0


Expand(conf-if)#mode on-lan

Expand(config)#interface tunnel 5 ipv4

Expand(conf-tunnel-5)#tunnel source 10.30.0.6

Expand(conf-tunnel-5)#tunnel destination 10.20.0.6

Tunnel ID was set to 1Source 10.30.0.6

Destination 10.20.0.6

Expand(conf-tunnel-5)#route-rules

Expand(route-rules)#routing-policy ip-routing-first

Expand(route-rules)#ip route 10.20.0.0 255.255.0.0 tunnel 5

Expand(route-rules)#ip route 10.20.0.6 255.255.255.255 10.30.0.

Basic On-LAN Application Task List



! Set Ethernet Interface IP Address for Port 0

(make sure to set the applications subnet mask) (Required)

! Verify that the Mode is set to On-LAN

! Create an IP Tunnel (Required)

! Configure IP Tunnel Source IP Address (Required)

! Configure IP Tunnel Destination IP Address (Required)


!Set Routing Policy to IP Routing First (Required)

! Define the IP Default Gateway of the Network as the Router

(Required)


39/328


! Define an IP Route Directing Transmissions Sent to the Far-End

Network into the Tunnel (Required)

! Define an IP Route Directing Tunnel Traffic to the Next Hop Router

(Required)

! Make sure to set the IP Default Gateway of the NT as the

ACCELERATOR (Required)

On-LAN with HSRP

On-LANwith HSRP configuration places the ACCELERATOR directly

on the LAN as a host, as in the Basic On-LAN configuration. The HSRP

feature enables the ACCELERATOR to operate in the HSRP backup group

with other devices to provide backup in the unlikely event of

ACCELERATOR failure.

The following figure depicts a typical ACCELERATOR On-LAN with

HSRP application:

Sample On-LAN with HSRP Configuration

The following sample configuration should be added to the Basic On-LAN configuration and is based on the diagram above.


40/328


There are two ways to configure HSRP: automatically or manually, as

follows:

Expand#configure

Expand(conf)#interface ethernet 0Expand(config-if)#hsrp auto-config enable

OR

Expand#configure

Expand(conf)#interface ethernet 0

Expand(conf-if)#hsrp 0 preempt enable

Expand(conf-if)#hsrp 0 priority 101

Expand(conf-if)#hsrp 0 ip 10.30.0.3

On-LAN with HSRP Application Task List

! Make sure to set the IP Default Gateway of the NT as the HSRP group

(Required)

! Auto-Configure HSRP (Optional)

OR

Manually Configure HSRP as follows:

! Set the Preempt status (Required)

! Set the Priority as Higher than the Router (Required)

! Set the Timers Hello and Hold Messages in accordance with the

Router (Optional)

! Set the IP address of the Group (Required)

Mixed On-LAN/On-Path Configurations

An application can be set up in which one side of the network places the

ACCELERATOR On-LAN, while the other side of the ACCELERATOR

places the ACCELERATOR On-Path, as follows:


41/328


To configure the ACCELERATORs in this mixed configuration, configure

the On-LAN ACCELERATOR according to the On-LAN configuration

instructions and the On-Path ACCELERATOR according to the On-Path

instructions.

Configuring Serial Interfaces

The enhanced network options that are possible with

ACCELERATOR devices include point-to-point and Frame Relay

configurations. Each type of architecture requires a different configuration

and settings in ExpandOS.

ExpandOS contains an autodetection feature that enables it to detect the

type of interface and network with which it is interacting. This detection is

based on the type of data that is passed through the ACCELERATOR's

serial interfaces after the ACCELERATOR is connected to an active line.

ExpandOS uses this data to detect if it is connected to a point-to-point or

point-to-multipoint network, and then to automatically select theappropriate encapsulation protocol.


42/328


Configuring the DTE Serial Interface

The DTE Serial interface is ExpandOS' connection to the WAN through the

CSU/DSU.In order to configure the parameters described in this section,

you must be in DTE Serial Interface configuration mode, for example,

Serial Interface 0/0.

NOTE:

The ACCELERATOR 2700 labels the Serial Interface 1/0. This is equivalent toSerial Interface 0/0 for the ACCELERATOR 4000.

For the purpose of these procedures, Serial Interface 0/0 is configured.

However, these procedures can be used to configure any serial interface.

# To enter DTE Seri al I nter face confi gur ati on m ode:

1 In Enable mode, type configure, and press .

2 Typeinterface serial 0/0, and press to enter the

Serial Interface 0/0 configuration mode.

Configuring Data Encapsulation

In order to configure serial interfaces, you must set the encapsulation

method used in your network. Encapsulation refers to the way in which

data packets are encapsulated when sent from the router.

This can be accomplished either by using the automatic encapsulation

detection feature or by manually configuring encapsulation.

For the ACCELERATOR to work properly, the encapsulation method must

be stable, it is not desirable to run the system while in autodetect mode.

Confirming Autodetect

By default, the ACCELERATOR automatically detects the encapsulation

method used in your network application, based on the data packets that are

received on that interface.


43/328


Once the confirm autodetect command is performed, the

encapsulation method will be permanently set to the current, detected

method. The ACCELERATOR will discontinue detection of encapsulation

methods. To resume autodetection, use the encapsulationautodetect command, as described inManually Configuring

Encapsulation, (when changes are made in the system application, such as

updating a DLCI number, the encapsulation must be redetected).

# To confirm autodetection:

1 In Primary Configuration mode, type interface serial 0/0,

and then press to enter the Serial Interface 0/0 configuration

mode.

2 Type confirm autodetection, to confirm the interface

encapsulation,-or-

Type confirm autodetection all, to confirm the

encapsulation for both the interface and its related subinterfaces.

3 Press .

Manually Configuring EncapsulationIMPORTANT:

Expand recommends that you use the confirm autodetect command to set the

encapsulation method, unless your application dictates otherwise (for example if

encapsulation has to be specified for a Frame Relay line, or if you know that therouter specifically uses CISCO HDLC, PPP or LAPB encapsulation).

# To config ure data encapsulati on on a point- to-p oint l in e:

1 In Serial Interface 0/0 configuration mode, type encapsulation

autodetect, to enable ExpandOS to automatically select the

Encapsulation mode,

-or-

Type encapsulation hdlc, to specify CISCO HDLC

encapsulation,

(a CISCO proprietary method of encapsulating data in HDLC frames

with additional protocol label),

-or-


44/328


Type encapsulation ppp, to specify PPP encapsulation,

-or-

Type encapsulation lapb modulo-8 (or modulo-128), to

specify LAPB encapsulation,

-or-

Type encapsulation raw-hdlc, to specify an unknown protocol

encapsulation over raw HDLC.

1 Press .

# To configure raw-HDLC encapsulation:

1 In Serial Interface 0/1 configuration mode, type

encapsulation raw-hdlc, to specify raw HDLC encapsulation,

and then press .

2 Typebarker, and then press . The prompt displays Expand

(Barker) #.

3 Type show, and then press to display the following options:

Barker:A prefix is added to any Expand accelerated data in order

to distinguish between that data and non-Expand data. Its default

value can be altered manually. It should be altered in cases where

normal packets passing through the network happen to start with

the same identical prefix.

Checksum: A checksum of the Expand accelerated data is added

to ensure data integrity. By default, this option is disabled.

NOTES:

Raw-HDLC should be used only when the actual data link protocol used on theNetwork is not directly supported by ExpandOS. In order to distinguish Acceleratedpackets from regular layer 2 packets, ExpandOS adds a prefix to each packet. Thisprefixs default value is (HEX) 670256.

Raw-HDLC can only be used for point-to-point applications.

# To config ure data on a Fra me Relay l i ne:


encapsulation frame-relay ietf, to specify multipoint

encapsulation for an IETF connection,

-or-


45/328


Type encapsulation frame-relay cisco, to specify

multipoint encapsulation for a CISCO connection.

2 Press .

Setting the Bandwidth

It is necessary to specify the bandwidth that the CSU/DSU provides to the

ACCELERATOR. For example, a T1 may have a bandwidth of

1544000 bps. The bandwidth is generally specified during installation, but

it can also be changed remotely.

NOTE:

The bandwidth parameter reflects an "approximation" of the bandwidth that isavailable from the WAN termination product (for example, CSU/DSU).

# To set the ba ndwi dth:

1 In Serial Interface 0/0 configuration mode, type bandwidth, then a

space, followed by a number between 32000 and 4000000. This

number represents the bandwidth in bits per second.

2 Press .

NOTES:

It is also possible to configure bandwidth for subinterfaces. This can be performedonly after invoking the confirm autodetection all command. This impacts

the acceleration cores allocation to the subinterfaces.

Core is a logical component of the system used for acceleration. The higher thenumber of cores allocated to an interface or a subinterface, the higher theacceleration.

The system allocates cores to interfaces and subinterfaces according to theirbandwidth. By default, the bandwidth of a subinterface is assumed to be thebandwidth of its parent serial interface divided by the number of subinterfaces.However, manual modification is possible by allowing manual control.

See Flow Control in Chapter 9, Supplementary Services.

Configuring Acceleration

An ACCELERATOR can only accelerate the data if there is another

ACCELERATOR at the opposite end. If the acceleration option is for some

reason disabled or in the unlikely event of a failure, the ACCELERATOR

will not probe for another ACCELERATOR, and data is sent at normalspeed.


46/328


# To configure acceleration:

1 In Serial Interface 0/0 configuration mode, type acceleration on

to enable acceleration,

-or-

Type no acceleration to disable acceleration.

2 Press .

NOTE:

In a multipoint network, this procedure sets acceleration on/off for all the serialinterface's related subinterfaces, alternatively, you can set each subinterfaceacceleration on/off by performing the same procedure while in subinterfaceconfiguration mode.

Configuring the Clock Source

The clock source that is used by the Serial Interface when receiving or

transmitting data may be defined. The clock may be generated internally or

externally. External clock sources are generated by the WAN termination

product (for example, CSU/DSU), whereas internal clock sources are

generated internally by the ACCELERATOR.

NOTE:

In many cases, the default settings for the clock source will suffice, and will notneed to be changed.

# To config ur e th e clock sour ce:

1 In Serial Interface 0/0 configuration mode, type clock source rxexternal tx external to set an external clock source for both

receive and transmit. This is the default for DTE interfaces,

-or-

Type clock source rx external tx internal to set an

external clock source for receive and an internal clock source for

transmit,

-or-

Type clock source rx external only to set the same

external clock source for both receive and transmit. This clock source is

primarily used for X.21 interfaces.


47/328


2 Press .

NOTE:

The DDS interface card can be set to either rx external tx external or

rx internal tx internal (the rx external only and rx external txinternal modes supported by the serial card are not relevant for the DDS card).

Configuring the Clock Rate

When using a DTE port for which the default clock source configuration is

clock source rx external tx external, the DTE port will be

clocked by an external device, for example, the CSU/DSU, and no

additional clock configuration is required. When using the rx external

txinternalclock source configuration, you also need to configure the

clock rate.

NOTE:The corresponding serial ports of the ACCELERATORs at both sites (in the case ofa point-to-point application) must have identical clock rates in order to preventpacket loss.

# To set the clock ra te:

1 In Serial Interface 0/0 configuration mode, type clock rate ?,

and press to display the available clock rates, as shown below:


48/328


2 Select the highest clock rate that is supported by the CSU/DSU. Type

clock rate, then a space followed by the selected rate, and press

to set the clock rate.

NOTES:

You may only use a clock rate that is shown in the displayed list.

For DDS interfaces, the clock rate must be configured and is limited to clockrates of 56000 and 64000.

Setting Clock Polarity

Using the polarity command reduces the occurrence of errors. An interface

requires instruction on whether to sample its send data on the rising edge or

the falling edge of the clock. When you use long cables that introduce

delays into the line, which could produce errors, polarity must be set.

On V.35/RS-530, you can alter the Tx clock polarity from low to high on

Serial 0/0, or you can alter the Rx clock polarity from low to high on

Serial 0/1.

On X.21, you can set the Rx clock polarity on serial 0/0 and the Rx clock

polarity on Serial 0/1.

NOTES:

On point-to-point links, CRC errors can be viewed at the remote site. These errorscannot be viewed in Frame Relay connections.

Further information about Clock Polarity issues can be found in Expand Network'sWeb site (www.expand.com), under Support.

# To set clock p ola ri ty:

1 In Serial Interface 0/0 configuration mode, type clock rx

polarity low to sample data on the rising edge,

-or-

Type clock rx polarity high to sample data on the falling

edge.

2 Press .

Setting Description

The description is free text that describes the interface. For example, you

might describe the interface by its physical location.


49/328


# To set the d escri pti on:

In Serial Interface 0/0 configuration mode, typedescriptionfollowed

by a space,followed by a string that provides a short description of theinterface, for example, description Long Island, and then press

.

NOTE:

You can use lower case and upper case letters, numbers, spaces, and so on.

Configuring Drop Recovery Code

Drop Recovery Code (DRC) enables synchronized ACCELERATORs to

attempt recovery of dropped data packets, without the need for the

ACCELERATORs to resynchronize or for the cache to be reset. There are

three configurable states, as follows:

! Full, for performing data packet recovery and retransmission.

! Semi, for performing retransmission only.

! Off, for not attempting to recover a data packet at all.

DRC is activated only when two ACCELERATORs are synchronized.

When performing full data packet recovery, there is an overhead of data on

the line because recovery data packets are sent automatically. If a data

packet is lost, information about the lost packet can be retrieved using the

recovery data packet.

# To configure DRC:

1 In Serial Interface 0/0 configuration mode, type drc mode full

and press , to perform packet recovery and retransmission,

-or-

Type drc mode semi to perform retransmission only,

-or-

Type drc mode off to prevent packet recovery attempts.


50/328


2 Press .

NOTE:

For a detailed explanation about the DRC mechanism, refer to Appendix A, Drop

Recovery.

Configuring the Ignore Data Carrier DetectSignal

ExpandOS can be configured to ignore the Data Carrier Detect (DCD)

signal being sent by the CSU/DSU. When DCD is ignored, the

ACCELERATOR transmits data, regardless of the DCD signal (e.g. in case

of an X.21 interface or when the WAN termination device does not provide

DCD signal).

# To config ure the i gnor e Data Car ri er Detect signal :

In Serial Interface 0/0 configuration mode, type ignore dcd, to ignore

the DCD signal from the CSU/DSU, and press .

Type no ignore dcd, to use the DCD signal from the CSU/DSU.

Configuring the Interval Between KeepalivePackets

Once two ACCELERATORs are properly configured keepalive packets are

sent between them in order to maintain the synchronized communication

link. The default time interval between transmission of the keepalivepackets can be altered by configuring the keepalive command on one

ACCELERATOR in the synchronized pair. This command sets the number

of seconds that the second ACCELERATOR waits between sending each

keepalive packet back to the first ACCELERATOR.

If other data is sent between the two ACCELERATORs, keepalive packets

are not sent, thus avoiding an overhead of data on the line.

# To config ure the in terval between k eepalive pa ck ets:

In Serial Interface 0/0 configuration mode, type keepalive-interval,

then a space followed by the required number ofseconds, for example,

keepalive-interval 10, and press .


51/328


Configuring Keepalive Iterations

The keepalive iteration is the number of keepalive intervals that can be

missed before the interface is considered disconnected as follows:keepalive-intervals keepalive-iterations = connection down

# To config ure the keepal ive iterati on:

In Serial Interface 0/0 configuration mode, type

keepalive-iterations, then a space followed by the required

number ofintervals, for example, keepalive-iterations 6, and

press .

IMPORTANT:

The iteration multiple should be at least twice the keepalive-interval of the remotedevice.

Configuring a Probe

A probe is a packet that is sent from an ACCELERATOR to the other end

of a communications link to determine if another ACCELERATOR is

connected at the remote end. When a second ACCELERATOR is detected,

the two devices are able to synchronize and begin communication. The

probe command defines the frequency with which probe packets are sent.

# To config ure a pr obe:

In Serial Interface 0/0 configuration mode, type probe,then a space

followed by the required number ofseconds, for example, probe 10, and

press .


52/328


Configuring the Maximum Transmission UnitParameter

The Maximum Transmission Unit (MTU) parameter defines the maximumpacket size that the DCE serial interface passes to ExpandOS. This

parameter should be configured to reflect the MTU specified in the router.

The ACCELERATOR MTU value should be set slightly higher than the

MTU that is set within the router, in order to provide support for the

additional headers applied by the router.

# To config ure th e MTU par am eter:

1 In Serial Interface 0/1 configuration mode, type mtu, then a space,

followed by an MTU number that is greater than the one specified in

the router, for example, mtu 2000.

2 Press .

Configuring Cyclic Redundancy CheckParameters

Cyclic Redundancy Check (CRC) parameters determine the type of CRC

used in the link. They must be the same as those configured for the router.

# To configure CRC parameters:

1 In Serial Interface 0/1 configuration mode, type crc 16-bit, to set

the CRC length to 16 bits,-or-

Type crc 32-bit, to set the CRC length to 32 bits.

2 Press .

NOTE:

For information on configuring Flow Control parameters, refer to Chapter 9,Configuring Supplementary Services.

Serial Interface Statistics

It is possible to view statistics (packet and byte data) for serial interfaces.

These statistics can also be viewed for subinterfaces, with the exception of

CRC errors which are only available for the interface.


53/328


# To vi ew i nter face stat istics:

! From within the serial interface (or subinterface) configuration mode,

type show throughput. The following screen will be displayed:

Expand(conf-if)#show throughput

throughput

Data | System Up | Since Clear | Last 30 Secs---------------+-----------+-------------+--------------

CRC Errors | 0| 0| 0 /SecDropped Bytes | 0| 0| 0Dropped Packets| 0| 0| 0

In Bytes | 0| 0| 0 KbpsIn Packets | 0| 0| 0 /Sec

Out Bytes | 0| 0| 0 KbpsOut Packets | 0| 0| 0 /Sec

Raw In Bytes | 0| 0| 0 KbpsRaw Out Bytes | 0| 0| 0 Kbps---------------+-----------+-------------+--------------

! CRC Errors

Statistics for errored packets that arrived to the hardware (Physical

layer CRC Error).

! Dropped bytes

Statistics for bytes that were discarded by the prioritization queues

or bytes that were discarded due to a bandwidth overflow

! Dropped packets

Statistics for packets that were discarded by the prioritization queues

or packets that were discarded due to a bandwidth overflow

! In bytes

Statistics for physical input of bytes on the line

! In packets

Statistics for physical input of packets on the line

! Out bytes

Statistics for physical output of bytes on the line

! Out packets

Statistics for physical output of packets on the line


54/328


! Raw In bytes

Total incoming bytes being accelerated using this (sub) interface or

tunnel

! Raw Out bytesTotal outgoing bytes being accelerated using this (sub) interface or

tunnel

Configuring the DCE Serial Interface

The DCE Serial Interface provides a connection between an

ACCELERATOR and the router. In order to configure the parameters

described in this section, you must be in DCE Serial Interface mode.

For the purposes of the procedures described below, Serial Interface 0/1 is

configured. However, these procedures can be used to configure any serial

interface.

# To enter DCE Seri al Inter face confi gur ati on m ode:

1 In Enable mode, type configure.

2 Typeinterface serial 0/1, and press to enter the

Serial Interface 0/1 configuration mode.


In order to configure serial interfaces, you must set the encapsulationmethod used in your network. Encapsulation refers to the way in which







By default, the ACCELERATOR automatically detects the encapsulationmethod used in your network application, based on the data packets that are



55/328





methods. To resume autodetection, use the encapsulationautodetect command, as described inManually Configuring






mode.


encapsulation,-or-

Type confirm autodetection all, to confirm the

encapsulation for both the interface and its related subinterfaces.

3 Press .

Manually Configuring EncapsulationIMPORTANT:

Expand recommends that you use the confirm autodetect command to set the

encapsulation method, unless your application dictates otherwise (for example if

encapsulation has to be specified for a Frame Relay line, or if you know that therouter specifically uses CISCO HDLC, PPP or LAPB encapsulation).


1 In Serial Interface 0/0 configuration mode, type encapsulation


Encapsulation mode,

-or-

Type encapsulation hdlc, to specify CISCO HDLC

encapsulation,

(a CISCO proprietary method of encapsulating data in HDLC frames

with additional protocol label),

-or-


56/328


Type encapsulation ppp, to specify PPP encapsulation,

-or-

Type encapsulation lapb modulo-8 (or modulo-128), to

specify LAPB encapsulation,

-or-

Type encapsulation raw-hdlc, to specify an unknown protocol

encapsulation over raw HDLC.

2 Press .

# To configure raw-HDLC encapsulation:


encapsulation raw-hdlc, to specify raw HDLC encapsulation,

and then press .

2 Typebarker, and then press . The prompt displays Expand

(Barker) #.

3 Type show, and then press to display the following options:

Barker:A prefix is added to any Expand accelerated data in order

to distinguish between that data and non-Expand data. Its default

value can be altered manually. It should be altered in cases where

normal packets passing through the network happen to start with

the same identical prefix.

Checksum: A checksum of the Expand accelerated data is added

to ensure data integrity. By default, this option is disabled.

NOTES:

Raw-HDLC should be used only when the actual data link protocol used on theNetwork is not directly supported by ExpandOS. In order to distinguish Acceleratedpackets from regular layer 2 packets, ExpandOS adds a prefix to each packet. Thisprefixs default value is (HEX) 670256.

Raw-HDLC can only be used for point-to-point applications.





-or-


57/328




2 Press .

Configuring the Clock Source/Clock Rate

The clock source and the clock rate are configured for the DCE Serial

Interface using the same procedure as for the DTE Serial Interface. These

configuration options can be found in Configuring the DTE Serial

Interface, page 3-14.However, in the DCE case, the ACCELERATOR is

the clock source and hence:

# To config ur e th e clock source:

In Serial Interface 0/1 (for example) configuration mode, type clock

source rx internal tx internalto set an internal clock source

for both receive and transmit. This is the default for DCE interfaces,

Configuring the Maximum Transmission UnitParameter

The Maximum Transmission Unit (MTU) parameter defines the maximum

packet size that the DCE serial interface passes to ExpandOS. This

parameter should be configured to reflect the MTU specified in the router.

The ACCELERATOR MTU value should be set slightly higher than the

MTU that is set within the router, in order to provide support for theadditional headers applied by the router.


58/328


# To config ure th e MTU par am eter:

1 In Serial Interface 0/1 configuration mode, type mtu, then a space,

followed by an MTU number that is greater than the one specified in

the router, for example, mtu 2000.

2 Press .

Configuring Cyclic Redundancy CheckParameters

Cyclic Redundancy Check (CRC) parameters determine the type of CRC

used in the link. They must be the same as those configured for the router.

# To configure CRC parameters:

1 In Serial Interface 0/1 configuration mode, type crc 16-bit, to set

the CRC length to 16 bits,

-or-

Type crc 32-bit, to set the CRC length to 32 bits.

2 Press .

Configuring Data Carrier Detect Mode

The DCD control line from ExpandOS to the router can be either on or off.

# To config ure th e Data Car ri er Detect m ode:

1 In Serial Interface Configuration 0/1 mode, type dcd enable, toenable DCD mode,

-or-

Type dcd disable, to disable DCD mode.


59/328


2 Press .

Bypass Mode

In order to provide greater network stability, the ACCELERATOR features

a built-in bypass mode. Bypass mode directs received traffic through the

hardware to the transmit port, bypassing the ACCELERATOR entirely. In

the unlikely event of a hardware failure or a power failure, the

ACCELERATOR will automatically operate in bypass mode. This provides

an automatic safeguard for the network connection, regardless of the

ACCELERATORs status. Alternatively, the ACCELRATOR can be

manually configured to operate in bypass mode.

NOTE:

In the ACCELERATOR 2700 Series, bypass is always on port 0/0.

Manual Bypass Activation

When you want to force the ACCELERATOR to operate in bypass mode, it

can be manually configured, as follows.

# To ma nual ly activate/ deactivate bypass mode:

1 In Serial Interface 0/0 configuration mode, type bypass, and then

press to activate bypass mode.

2 Type no bypass, when you are ready to deactivate the bypass

option.

$SAVE:In order to save a configuration to flash memory so that it will be available afterExpandOS is rebooted, type writeat the Enable (#)prompt.


60/328


Multipoint Networks


In order to configure serial interfaces, you must set the encapsulation

method used in your network. Encapsulation refers to the way in which







By default, the ACCELERATOR automatically detects the encapsulation

method used in your network application, based on the data packets that are





methods. To resume autodetection, use the encapsulation

autodetect command, as described inManually Configuring






mode.


encapsulation,

-or-

Type confirm autodetection all, to confirm theencapsulation for both the interface and its related subinterfaces.


61/328


3 Press .

Manually Configuring Encapsulation

IMPORTANT:Expand recommends that you use the confirm autodetect command to set the

encapsulation method, unless your application dictates otherwise (for example ifencapsulation has to be specified for a Frame Relay line, or if you know that therouter specifically uses CISCO HDLC, PPP or LAPB encapsulation).


! In Serial Interface 0/0 configuration mode, type encapsulation


Encapsulation mode,





-or-



2 Press .

Detecting Subinterfaces

Subinterfaces can be detected automatically or manually.

Automatic Subinterface Detection

The autodetect subinterfaces option enables you to configure

the ACCELERATOR to continuously detect subinterfaces. If this option is

disabled, a new connection will not be detected.

NOTE:

It is recommended that this option is left enabled.


62/328


# To confi gur e autod etect subin terf aces:



mode.

2 Type autodetect subinterfaces enable, to enable

continuous detection,

expand accelarator - exos4.0userguide

Documents