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
8-6 Preliminary January 30, 1998 Pipeline User’s Guide
90-C00 Mod Config
Log...
Syslog=Yes
Log Host=206.65.212.205
Log Port=514
Log Facility=Local0
2
Turn on Syslog.
3
Specify the IP address of the host running the Syslog daemon.
The host running a Syslog daemon is typically a UNIX host, but it may also
be a Windows system. If the log host is not on the same subnet as the
Pipeline, the Pipeline must have a route to that host, either via RIP or a static
route.
Note:
Do not configure the Pipeline to send reports to a syslog host that can
only be reached by a dial-up connection. That would cause the Pipeline to
dial the log host for every logged action, including hang ups.
4
Select Log Port and type the port number at which you want the Syslog host
to listen for messages from this Pipeline.
The default port is port 514.
5
Set the log facility level.
This parameter is used to flag messages from the Pipeline. After you set a
log facility number, you need to configure the Syslog daemon to write all
messages containing that facility number to a particular log file. (That will
be the Pipeline log file.)
6
Close the Ethernet profile.
To configure the Syslog daemon, you need to modify /etc/syslog.conf on the log
host. This file specifies which action the daemon will perform when it receives
messages from a particular log facility number (which represents the Pipeline).
For example, if you set Log Facility to Local5 in the Pipeline, and you want to
log its messages in /var/log/Pipeline, add this line to /etc/syslog.conf:
local5.info<tab>/var/log/Pipeline
Note:
The Syslog daemon must reread /etc/syslog.conf after it has been
changed.