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 IP Routing
Managing the routing table
Pipeline User’s Guide Preliminary January 30, 1998 2-29
This is a count of the number of times the route has been referenced since it
was created. (Many of the references are internal, so this is not a count of the
number of packets sent using this route.)
Unused routes are indicated by a 0 in the Use column.
•Age
This is the age of the route in seconds. It is used for troubleshooting, to
determine when routes are changing rapidly (referred to as “flapping”).
Removing down routes to a host
The Pipeline advertises addresses associated with Connection profiles as routes
to which it can connect. By default, it advertises these addresses even when a link
is down, because they are necessary for the on-demand connections that the
Pipeline establishes.
For a nailed connection, it is assumed that the connection is always up. If it is not,
the routes to that connection are not necessary until the connection comes back
up. For example:
Pipeline 1 and Pipeline 2 are on the same local LAN.
• Pipeline 1 has a nailed connection to a remote site.
The remote address has a metric of 4.
• Pipeline 2 is a backup connection.
It has a remote address with a metric of 7.
Traffic goes through Pipeline 1 because of the lower metric. If its connection
goes down, its route to the remote network is still advertised by default.
Therefore, the connection specified by Pipeline 2 never comes up.
To remove the route of a down, nailed connection, set the Temporary parameter
in Ethernet > Connection > profile of down connection > IP options submenu to
Yes. When the Temporary parameter is set to Yes, a route to a nailed connection
is removed from the routing table when the link is down, including all routes
dynamically learned on this connection, and discontinues advertising the route.
The routes are advertised and reappear in the routing table only when you re-
establish the connection.