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
Connection profiles
Pipeline User’s Guide Preliminary January 30, 1998 1-19
By default, the calling unit adds or subtracts bandwidth on the basis of how much
data it transmits. To alter the default behavior, you can set the DBA Monitor
parameter to Transmit-Recv, which tells the calling unit to add or subtract
bandwidth on the basis of how much data it transmits and receives. Or, you can
set it to None to tell the Pipeline not to monitor traffic over the link. If both sides
of the link have DBA Monitor set to None, DBA is disabled.
Clearing a call on the basis of idle bandwidth
The Idle Pct parameter specifies a percentage of bandwidth utilization below
which an MP+ call is cleared. Bandwidth utilization must fall below this
percentage on both sides of the connection before the Pipeline clears the call. If
the device at the remote end of the link has an Idle Pct setting lower than the
value you specify, the Pipeline does not clear the call until bandwidth utilization
falls below the lower percentage.
The default value for Idle Pct is 0, causing the Pipeline to ignore bandwidth
utilization when determining whether to clear a call. It uses the Idle timer instead.
Example MP+ configuration
For MP+ calls, you can use one authentication method for the base channel of the
call, and require another password for authenticating subsequent channels as they
are added. For details, see “Requesting PAP-TOKEN mode” on page 7-19.
The Pipeline must have a system name if PAP, CHAP, or MS-CHAP is to be used
for outgoing calls. To assign a name to the Pipeline:
1
Open the System > Sys Config menu.
2
Specify a name for the Pipeline unit in the Name parameter.
For example:
Name=Pipe1
3
Close and save the Sys Config menu.
Next, configure the profile for MP+ connection:
1
Open Ethernet > Connection > any profile > Encaps.
2
Select MP+ encapsulation.
Encaps=MPP