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

Troubleshooting
Common problems and their solutions
Pipeline User’s Guide Preliminary January 30, 1998 D-3
The first channel of an MP+ call connects, but then the call clears or does
not connect on the remaining channels
The most common error in defining Connection profiles is specifying incorrect
phone numbers. The Pipeline cannot successfully build inverse multiplexing or
MP+ calls if the phone numbers in the Connection profile of the called unit are
incorrect. The phone numbers that you specify in the Connection profile are the
numbers local to your unit. Do not enter the phone numbers of the Pipeline you
are calling in the Connection profile.
When the Pipeline tries to place a call, the error message No Channel Avail
appears in the Message Log display
Check the configuration of your line in the Configure profile.
Hardware configuration problems
If you cannot communicate with the Pipeline through the VT-100 control
terminal, you might have a terminal configuration, control port cable, or Pipeline
hardware problem.
No data is displayed on the VT-100
If the Pipeline is in this state, verify that the unit completes all of the power-on
self tests successfully by following these steps:
1
Verify that the Pipeline and your terminal are set at the same speed.
2
Locate the LED labeled CON.
3
Switch on the Pipeline.
The CON LED should remain off except during the power-on self tests. If
you are using the Control Monitor, type Ctrl-L to refresh the screen.
If the CON LED remains on longer than a minute, there is a Pipeline
hardware failure. A blinking CON LED also indicates a hardware failure.
Should these situations arise, contact Ascend Communications, Inc.
Customer Support.
The CON LED is off, but no data is displayed on the Control Monitor's VT-