User`s guide
Table Of Contents
- Ascend Customer Service
- How to use this guide
- What you should know
- Documentation conventions
- How to use the on-board software
- Manual set
- Configuring WAN Connections
- Configuring IP Routing
- Introduction to IP routing on the Pipeline
- Managing the routing table
- Parameters that affect the routing table
- Static and dynamic routes
- Configuring static routes
- Specifying default routes on a per-user basis
- Enabling the Pipeline to use dynamic routing
- Route preferences
- Viewing the routing table
- Fields in the routing table
- Removing down routes to a host
- Identifying Temporary routes in the routing table
- Configuring IP routing connections
- Ascend Tunnel Management Protocol (ATMP)
- IP Address Management
- Connecting to a local IP network
- BOOTP Relay
- DHCP services
- Dial-in user DNS server assignments
- Local DNS host address table
- Network Address Translation (NAT) for a LAN
- Configuring IPX Routing
- How the Pipeline performs IPX routing
- Adding the Pipeline to the local IPX network
- Working with the RIP and SAP tables
- Configuring IPX routing connections
- Configuring the Pipeline as a Bridge
- Defining Filters and Firewalls
- Setting Up Pipeline Security
- Pipeline System Administration
- Pipeline 75 Voice Features
- IDSL Implementations
- APP Server utility
- About the APP Server utility
- APP Server installation and setup
- Configuring the Pipeline to use the APP server
- Using App Server with Axent SecureNet
- Creating banner text for the password prompt
- Installing and using the UNIX APP Server
- Installing and using the APP Server utility for DO...
- Installing and using the APP Server utility for Wi...
- Installing APP Server on a Macintosh
- Troubleshooting
- Upgrading system software
- What you need to upgrade system software
- Displaying the software load name
- The upgrade procedure
- Untitled

Configuring WAN Connections
Configuring Frame Relay connections
1-30 Preliminary January 30, 1998 Pipeline User’s Guide
4
Select Frame Relay encapsulation.
For example:
Encaps=FR
The Pipeline uses this encapsulation method to encapsulate packets before
routing them out to the CPE, and removes the Frame Relay encapsulation
from packets coming in from the CPE.
5
Open the Encaps Options submenu of the same profile.
FR Prof=Pac Bell
DLCI=17
6
Set the DLCI parameter to the number assigned by the Frame Relay
administrator.
For example:
DLCI=500
The Frame Relay administrator must assign the DLCI number. It determines
how packets will be routed at the Frame Relay switch.
7
Specify the name of the Frame Relay profile that defines the nailed
connection to the Frame Relay switch.
For example:
FR Prof=PacBell
The name must match the Name parameter in the Frame Relay profile
exactly, including case changes.
8
Close and save the profile.
Inverse ARP for Frame Relay
Inverse Address Resolution Protocol (InARP) allows a device to resolve the
protocol address of another device when the hardware address is known. In the
case of Frame Relay the hardware address is the DLCI. The Ascend
implementation of Inverse ARP responds only to Frame Relay and IP Inverse
ARP requests.
The ARP protocol type for Inverse ARP requests must be IP(0x8000). ARP
hardware address type must be the 2-byte Q.922 address. All other types are
discarded.