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
Configuring administration options
Pipeline User’s Guide Preliminary January 30, 1998 8-7
Syslog messages
Syslog messages have a standard format that is described below. In addition to
the normal traffic logged by Syslog, information may be generated for packets
seen by the Secure Access firewall, if specified by SAM. By default, SAM will
cause a syslog message to be generated for all packets blocked by a firewall.
Syslog messages use the format:
<date> <time> <router name> ASCEND: <interface> <message>
• <date> indicates the date the message was logged by syslog.
• <time> indicates the time the message was logged by syslog.
• <router name> indicates the router this message was sent from.
• <interface> is the name of the interface (ie0, wan0, and so on) or ‘call’ if the
packet is logged by the call filter as it brings up the link.
• The <message> format has a number of fields, one or more of which may be
present:
protocol The 4 hexadecimal digit Ether Type, or the network protocol
name—“arp,” “rarp,” “ipx,” “appletalk.”
The protocol for IP protocols, is either the IP protocol number (up
to 3 decimal digits) or one of the following names:
•ip-in-ip
•tcp
• icmp—In the special case of icmp, it will also include the
ICMP Code and Type ([Code]/[Type]/icmp).
•udp
•esp
•ah