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

Pipeline System Administration
Accessing a local Pipeline via Telnet
Pipeline User’s Guide Preliminary January 30, 1998 8-21
Accessing a local Pipeline via Telnet
If a remote user Telnets to the Pipeline and the Ethernet > Mod Config > Telnet
PW has been set, the user is prompted for the Telnet password. Local users
Telneting to the Pipeline over the Ethernet must also supply this password.
The Telnet password verification trap reports the IP address of the Telnet client
whose login attempts failed. The address is included in the security violation
message issued whenever the maximum number of Telnet login attempts to a
Pipeline has been exceeded.
To Telnet into a Pipeline, a user must supply the appropriate password, which is
then verified. If the user cannot supply the correct password, an SNMP trap
message is sent to all SNMP clients enabled for SNMP security messages.
The message includes the following information:
• The session number for the attempted Telnet session.
• The IP address of the host (the Pipeline).
• The associated IP address of the Telnet client that attempted the connection.
The format of the message is as follows:
Where:
mm.mmm.mmm.mmm Enterprise Specific Trap (15) Uptime: xx:xx:xx
Name.iso.org.dod.internet.private.enterprises.ascend.sessionStatus Group.
IpAddress: ttt.ttt.ttt.ttt
sessionStatusTable.sessionStatusEntry.ssnStatusUserIPAddress%d
mmm.mmm.mmm.mmm
Host's IP address
ttt.ttt.ttt.ttt
Telnet client's IP address
%d
attempted Telnet session number