PortMaster, ComOS, and ChoiceNet are registered trademarks of Lucent Technologies, Inc. RADIUS ABM,
PMVision, IRX, PortAuthority, and AnyMedia are trademarks of Lucent Technologies, Inc. All other marks are the
property of their respective owners.
Disclaimer
Lucent Technologies, Inc. makes no express or implied representations or warranties with respect to the contents
or use of this manual, and specifically disclaims any implied warranties of merchantability or fitness for a
particular purpose. Lucent Technologies, Inc. further reserves the right to revise this manual and to make changes
to its content at any time, without obligation to notify any person or entity of such revisions or changes.
The PortMaster 4 Configuration Guide provides configuration instructions and examples
and software troubleshooting instructions for the PortMaster
Concentrator from the Remote Access Business Unit of Lucent Technologies, Inc.
This configuration guide is one of three manuals that make up the comprehensive
PortMaster 4 User Manual:
•PortMaster 4 Installation Guide
•PortMaster 4 Configuration Guide
•PortMaster 4 Command Line Reference
Consult the contents and indexes in each of these three manuals for detailed lists of
topics and specific page references.
See the additional manuals listed under “PortMaster Documentation” for configuration,
maintenance, and troubleshooting information common to all PortMaster products.
Audience
This guide is designed to be used by qualified system administrators and network
managers. Knowledge of basic networking concepts is required.
PortMaster Documentation
®
4 Integrated Access
The following manuals are available from Lucent Remote Access. They can be ordered
through your PortMaster distributor or directly from Lucent.
The manuals are also provided as PDF and PostScript files on the PortMaster Software CD
shipped with your PortMaster.
In addition, you can download PortMaster information and documentation from
http://www.livingston.com.
•ChoiceNet® Administrator’s Guide
This guide provides complete installation and configuration instructions for
ChoiceNet server software.
•PortMaster Routing Guide
This guide describes routing protocols supported by PortMaster products, and how to
use them for a wide range of routing applications.
•PortMaster Troubleshooting Guide
This guide can be used to identify and solve software and hardware problems in the
PortMaster family of products.
xiii
Additional References
•RADIUS for UNIX Administrator’s Guide
This guide provides complete installation and configuration instructions for Lucent
Remote Authentication Dial-In User Service (RADIUS) software for UNIX operating
systems.
•RADIUS for Windows NT Administrator’s Guide
This guide provides complete installation and configuration instructions for Lucent
RADIUS software for Microsoft Windows NT.
Additional References
RFCs
To find a Request for Comments (RFC) online, visit the website of the Internet
Engineering Task Force (IETF) at http://www.ietf.org/.
RFC 768, User Datagram Protocol
RFC 791, Internet Protocol
RFC 792, Internet Control Message Protocol
RFC 793, Transmission Control Protocol
RFC 854, Telnet Protocol Specification
RFC 950, Internet Standard Subnetting Procedure
RFC 1058, Routing Information Protocol
RFC 1112, Host Extensions for IP Multicasting
RFC 1144, Compressing TCP/IP Headers for Low-Speed Serial Links
RFC 1157, A Simple Network Management Protocol (SNMP)
RFC 1166, Internet Numbers
RFC 1212, Concise MIB Definitions
RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets:
MIB-II
RFC 1256, ICMP Router Discovery Messages
RFC 1321, The MD5 Message-Digest Algorithm
RFC 1331, The Point-to-Point Protocol (PPP) for the Transmission of Multiprotocol Datagrams
over Point-to-Point Links
RFC 1332, The PPP Internet Protocol Control Protocol (IPCP)
RFC 1334, PPP Authentication Protocols
RFC 1349, Type of Service in the Internet Protocol Suite
RFC 1413, Identification Protocol
RFC 1490, Multiprotocol Interconnect Over Frame Relay
RFC 1541, Dynamic Host Configuration Protocol
RFC 1542, Clarifications and Extensions for the Bootstrap Protocol
RFC 1552, The PPP Internet Packet Exchange Control Protocol (IPXCP)
RFC 1587, OSPF NSSA Options
RFC 1597, Address Allocations for Private Internets
RFC 1627, Network 10 Considered Harmful (Some Practices Shouldn’t be Codified)
RFC 1634, Novell IPX Over Various WAN Media (IPXWAN)
RFC 1661, The Point-to-Point Protocol (PPP)
RFC 1700, Assigned Numbers
RFC 1723, RIP Version 2
RFC 1771, A Border Gateway Protocol 4 (BGP-4)
RFC 1812, Requirements for IP Version 4 Routers
xivPortMaster 4 Configuration Guide
Additional References
RFC 1814, Unique Addresses are Good
RFC 1818, Best Current Practices
RFC 1824, Requirements for IP Version 4 Routers
RFC 1825, Security Architecture for the Internet Protocol
RFC 1826, IP Authentication Header
RFC 1827, IP Encapsulating Payload
RFC 1828, IP Authentication Using Keyed MD5
RFC 1829, The ESP DES-CBC Transform
RFC 1877, PPP Internet Protocol Control Protocol Extensions for Name Server Addresses
RFC 1878, Variable Length Subnet Table for IPv4
RFC 1918, Address Allocation for Private Internets
RFC 1962, The PPP Compression Control Protocol (CCP)
RFC 1965, Autonomous System Confederations for BGP
RFC 1966, BGP Route Reflection, An Alternative to Full Mesh IBGP
RFC 1974, PPP Stac LZS Compression Protocol
RFC 1990, The PPP Multilink Protocol (MP)
RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP)
RFC 1997, BGP Communities Attribute
RFC 2003, IP Encapsulation within IP
RFC 2104, HMAC: Keyed-Hashing for Message Authentication
RFC 2125, The PPP Bandwidth Allocation Protocol (BAP), The PPP Bandwidth Allocation
Control Protocol (BACP)
RFC 2138, Remote Authentication Dial In User Service (RADIUS)
RFC 2139, RADIUS Accounting
RFC 2153, PPP Vendor Extensions
RFC 2328, OSPF Version 2
RFC 2400, Internet Official Protocol Standards
RFC 2453, RIP Version 2
Books
Building Internet Firewalls. D. Brent Chapman and Elizabeth D. Zwicky. Sebastopol, CA:
DNS and BIND, 2nd ed. Paul Albitz and Cricket Liu. Sebastopol, CA: O'Reilly &
Associates, Inc., 1992. (ISBN 1-56592-236-0)
Firewalls and Internet Security: Repelling the Wily Hacker. William R. Cheswick and Steven
M. Bellovin. Reading, MA: Addison-Wesley Publishing Company, 1994.
(ISBN 0-201-63357-4) (Japanese translation: ISBN 4-89052-672-2). Errata are available
at ftp://ftp.research.att.com/dist/internet_security/firewall.book.
Internet Routing Architectures. Bassam Halabi. San Jose, CA: Cisco Press, 1997.
(ISBN 1-56205-652-2)
Internetworking with TCP/IP, Volume 1: Principles, Protocols, and Architecture. Douglas Comer.
Upper Saddle River, NJ: Prentice Hall, Inc. 1995. (ISBN 0-13-216987-8 (v.1))
Routing in the Internet. Christian Huitema. Upper Saddle River, NJ: Prentice Hall PTR,
1995. (ISBN 0-13-132192-7)
TCP/IP Illustrated, Volume 1: The Protocols. W. Richard Stevens. Reading, MA:
Addison-Wesley Publishing Company. 1994. (ISBN 0-201-63346-9)
entry—a
command, menu
option, button, or
key—or the name
of a file, directory,
or utility, except
in code samples.
Italic fontIdentifies a
command-line
placeholder.
Replace with a
real name or
value.
Square brackets ([ ])Enclose optional
keywords and
values in
command syntax.
Curly braces ({ })Enclose a
required choice
between
keywords and/or
values in
command syntax.
• Enter version to display the version
number.
• Press Enter.
•Open the permit_list file.
• setEther0addressIpaddress
•Replace Area with the name of the
OSPF area.
• set nameserver[2]Ipaddress
• setS0destinationIpaddress
[Ipmask]
set syslogLogtype {[disabled]
[Facility.Priority]}
Vertical bar (|)Separates two or
more possible
options in
command syntax.
• setS0|W1ospfon|off
• setS0host
default|prompt|Ipaddress
Document Advisories
Note – means take note. Notes contain information of importance or special interest.
✍
Caution – means be careful. You might do something—or fail to do something—that
!
xviPortMaster 4 Configuration Guide
results in equipment failure or loss of data.
Contacting Lucent Remote Access Technical Support
Warning – means danger. You might do something—or fail to do something—that
results in personal injury or equipment damage.
Contacting Lucent Remote Access Technical Support
The PortMaster comes with a 1-year hardware warranty.
For all technical support requests, record your PortMaster ComOS version number and
report it to the technical support staff or your
New releases and upgrades of PortMaster software are available by anonymous FTP from
ftp://ftp.livingston.com/pub/le/.
In North America you can schedule a 1-hour software installation appointment by
calling the technical support telephone number listed below. Appointments must be
scheduled at least one business day in advance.
authorized sales channel partner
For the EMEA Region
.
If you are an Internet service provider (ISP) or other end user in Europe, the Middle
East, Africa, India, or Pakistan, contact your local Lucent Remote Access sales channel
partner. For a list of authorized sales channel partners, see the World Wide Web at
http://www.livingston.com/International/EMEA/distributors.html.
If you are an authorized Lucent Remote Access sales channel partner in this region,
contact the Lucent Remote Access EMEA Support Center Monday through Friday
between the hours of 8 a.m. and 8 p.m. (GMT+1), excluding French public holidays.
•By voice, dial +33-4-92-92-48-48.
•By fax, dial +33-4-92-92-48-40.
•By electronic mail (email) send mail to emea-support@livingston.com.
For North America, Latin America, and the Asia Pacific Region
Contact Lucent Remote Access Monday through Friday between the hours of 7 a.m.
and 5 p.m. (GMT –8).
•By voice, dial 800-458-9966 within the United States (including Alaska and
Hawaii), Canada, and the Caribbean, or +1-925-737-2100 from elsewhere.
•By fax, dial +1-925-737-2110.
•By email, send mail as follows:
–From North America and Latin America to support@livingston.com.
–From the Asia Pacific Region to asia-support@livingston.com.
•Using the World Wide Web, see http://www.livingston.com/.
About This Guidexvii
PortMaster Training Courses
PortMaster Training Courses
Lucent Remote Access offers hands-on, technical training courses on PortMaster
products and their applications. For course information, schedules, and pricing, visit the
Lucent Remote Access website at
http://www.livingston.com/tech/training/index.html.
Subscribing to PortMaster Mailing Lists
Lucent Remote Access maintains the following Internet mailing lists for PortMaster
users:
•portmaster-users—a discussion of general and specific PortMaster issues, including
configuration and troubleshooting suggestions. To subscribe, send email to
majordomo@livingston.com with subscribe portmaster-users in the body of
the message.
The mailing list is also available in a daily digest format. To receive the digest, send
email to majordomo@livingston.com with subscribe portmaster-users-digest
in the body of the message.
•portmaster-radius—a discussion of general and specific RADIUS issues, including
configuration and troubleshooting suggestions. To subscribe, send email to
majordomo@livingston.com with subscribe portmaster-radius in the body of
the message.
The mailing list is also available in a daily digest format. To receive the digest, send
email to majordomo@livingston.com with subscribe portmaster-radius-digest in the body of the message.
•portmaster-announce—announcements of new PortMaster products and software
releases. To subscribe, send email to majordomo@livingston.com with subscribe portmaster-announce in the body of the message. All announcements to this list
also go to the portmaster-users list. You do not need to subscribe to both lists.
xviiiPortMaster 4 Configuration Guide
This chapter discusses the following topics:
•“PortMaster Software” on page 1-1
•“Preconfiguration Planning” on page 1-2
•“Setting the View” on page 1-3
•“Configuration Tips” on page 1-3
•“Basic Configuration Steps” on page 1-4
PortMaster Software
All PortMaster products are shipped with the following software:
•ComOS®—The communication software operating system already loaded in
nonvolatile RAM (also called Flash RAM) on each PortMaster. You can use the
ComOS command line interface to configure your PortMaster through a console.
Introduction1
•PMVision™—A graphical user interface (GUI) companion to the ComOS command
line interface for Microsoft Windows, UNIX, and other platforms that support the
Java Virtual Machine (JVM). Because PMVision also supports command entry, you
can use a combination of GUI panels and ComOS commands to configure, monitor,
and debug a PortMaster. When connected to one or more PortMaster products,
PMVision allows you to monitor activity and edit existing configurations. PMVision
replaces the PMconsole interface to ComOS.
This application and other Java-based configuration tools for the PortMaster are
available via anonymous FTP at
ftp://ftp.livingston.com/pub/livingston/software/java/.
•pmd or in.pmd—The optional PortMaster daemon software that can be installed
on UNIX hosts to allow the host to connect to printers or modems attached to a
PortMaster. The daemon also allows the PortMaster to multiplex incoming users
onto the host using one TCP stream instead of multiple streams like rlogin. The
daemon is available for SunOS, Solaris, AIX, HP-UX, and other platforms.
For installation and configuration instructions, copy the PortMaster software to the
UNIX host as described on the PortMaster Software CD package.
•RADIUS—The RADIUS server daemon, radiusd, runs on UNIX systems, providing
centralized authentication for dial-in users. The radiusd daemon is provided to
customers in binary and source form for SunOS, Solaris, Solaris/X8.6, AIX, HP-UX,
IRIX, Alpha OSF/1, Linux, and BSD/OS platforms.
For installation and configuration instructions, see the RADIUS for Windows NT
Administrator’s Guide and RADIUS for UNIX Administrator’s Guide.
1-1
Preconfiguration Planning
•ChoiceNet—ChoiceNet is a security technology invented by Lucent to provide a
traffic filtering mechanism for networks using dial-up remote access, synchronous
leased line, or Ethernet connections. When used with RADIUS, ChoiceNet provides
exceptional flexibility in fine-tuning the level of access provided to users.
For installation and configuration instructions, see the ChoiceNet Administrator’s Guide.
Preconfiguration Planning
Before the PortMaster can be used to connect wide area networks (WANs), you must
install the hardware using the instructions in the PortMaster 4 Installation Guide.
This configuration guide is designed to introduce the most common configuration
options available for the PortMaster 4. Review this material before you configure your
PortMaster and, if possible, answer the following questions:
•What general configuration do you want to implement?
•Do you want to use a synchronous connection to a high-speed line?
•Will your high-speed lines use Frame Relay, ISDN, switched 56Kbps, or PPP?
•If you want dial-on-demand routing, do you want multiline load-balancing?
•Do you want Multilink Point-to-Point Protocol (PPP) (RFC 1717)?
•Do you want packet filtering for Internet connections?
•Do you want packet filtering for connections to other offices?
•Do you want dial-in users to use Serial Line Internet Protocol (SLIP), PPP, or both?
•If you use PPP, do you want Password Authentication Protocol (PAP) or Challenge
Authentication Protocol (CHAP) authentication?
•Are you using a name service—Domain Name System (DNS) or Network
Information Service (NIS)?
•Have you obtained the necessary network addresses?
•Do you want to enable Simple Network Management Protocol (SNMP) for network
monitoring?
•Do you want dial-in only, dial-out only, or two-way communication on each port?
•What characteristics do you want to assign to the dial-out locations?
•How do you want to configure dial-in users?
•Do you want to use RADIUS or the internal user table on the PortMaster to
authenticate dial-in users?
•Do you want to use ChoiceNet to filter network traffic?
•Do you want to use the console port for administration functions, or do you want to
attach an external modem to the port?
1-2PortMaster 4 Configuration Guide
•For dial-in users, do you receive service on analog lines, ISDN Primary Rate
Interface (PRI), channelized T1, or E1?
Many other decisions must be made during the configuration process. This guide
discusses the various configuration options and their implications.
Setting the View
The PortMaster 4 operates via the modules and boards installed in its slots. The system
manager module installed in slot 4 provides overall (global) management for the entire
chassis.
To monitor and configure a particular module or board, you use the set view command
to set the view to the slot of the installed board or module. The default view is slot 4,
which is the manager view.
Because the Ethernet interfaces on a PortMaster 4 are numbered uniquely, you can
configure them from any view. However, you must reboot Ether0 and reset the
appropriate slot for the other Ethernet interfaces to activate configuration settings.
Except for the manager module, for which the command line prompt displays no
number, the prompt indicates the view you are in. For example:
Setting the View
Command> set view 3
View changed from 4 to 3
Command 3> set view 4
View changed from 3 to 4
Command>
The save all command saves all configuration information for all boards regardless of
what view is set.
Configuration Tips
PortMaster configuration can be confusing because settings can be configured for a port,
a user, or a remote location. Use Table 1-1 to determine how to configure your
PortMaster.
Table 1-1PortMaster Configuration Tips
If You Are Configuring . . .Then Configure Settings on . . .
A network hardwired port or
hardwired multiline load
balancing
One or more ports for dial-out
operation
The port
Dial-out locations using the location table
One or more ports for dial-in
operation
A callback network userThe callback location in the location table (refer
Introduction1-3
Dial-in users using the user table or RADIUS
to the location name in the user table)
Basic Configuration Steps
Basic Configuration Steps
The exact PortMaster configuration steps you follow depend upon the hardware you are
installing and your network configuration. However, the following general configuration
steps are the same for all PortMaster products:
1. Install the PortMaster hardware and assign an IP address and a password
as described in the PortMaster 4 Installation Guide.
2. Boot the system and log in with the administrative password.
You can configure the PortMaster from a terminal attached to the console port,
through an administrative Telnet session, or through a network connection.
Note – This configuration guide assumes that you have completed Step 1 and Step 2
✍
and does not give details on hardware installation, IP address assignment, or
administrative password assignment.
3. If you want to use PMVision software to configure your PortMaster, install
it on a workstation anywhere on your network.
PMVision is available via anonymous FTP at
ftp://ftp.livingston.com/pub/livingston/software/java/. See the PMVision
online help for information on using PMVision.
4. Configure the global settings.
PortMaster global settings are described in Chapter 2, “Configuring Global Settings.”
5. Configure the Ethernet settings, and configure the IP protocol settings for
your network.
PortMaster Ethernet settings are described in Chapter 4, “Configuring an Ethernet
Interface.”
6. Configure the synchronous ports.
PortMaster synchronous port settings are described in Chapter 6, “Configuring a
Synchronous WAN Port.”
7. Configure T1, E1, and ISDN PRI connections.
ISDN PRI connection configuration is described in Chapter 10, “Configuring T1, E1,
and ISDN PRI” and Chapter 11, “Configuring a T3 Mux Board.”
8. Configure dial-in users in the user table, or configure RADIUS.
The user table is described in Chapter 5, “Configuring Dial-In Users.” If you are
using RADIUS security instead of the user table, see the RADIUS for Windows NT Administrator’s Guide or RADIUS for UNIX Administrator’s Guide.
9. Configure ChoiceNet, if you are using it.
ChoiceNet is a traffic filtering mechanism for networks using dial-up remote access,
synchronous leased line, or Ethernet. Refer to the ChoiceNet Administrator’s Guide for
more information.
1-4PortMaster 4 Configuration Guide
Basic Configuration Steps
10. Configure dial-out locations in the location table.
The location table is described in Chapter 7, “Configuring Dial-Out Connections.”
11. Configure filters in the filter table.
Once the filters are created, they can be assigned as input or output filters for the
Ethernet interface, users, locations, or hardwired ports. Filters are described in
Chapter 8, “Configuring Filters.”
12. Configure the Layer 2 Tunneling Protocol (L2TP) if you are setting up an
L2TP tunnel to an L2TP-compatible router.
See the PortMaster 4 Command Line Reference for information on the L2TPcommands.
13. Configure OSPF, if you are using this protocol.
OSPF is described in the PortMaster Routing Guide.
14. Configure BGP, if you are using this protocol.
BGP is described in the PortMaster Routing Guide.
15. Troubleshoot your configuration, if necessary, and back it up.
See the troubleshooting information in this guide and the PortMaster Troubleshooting
Guide for instructions.
Once you have correctly configured all the settings necessary for your circumstances,
your PortMaster is ready to provide communication service and routing for your
network.
Introduction1-5
Basic Configuration Steps
1-6PortMaster 4 Configuration Guide
Configuring Global Settings 2
This chapter describes how to configure settings that the PortMaster 4 uses across all its
ports and interfaces.
This chapter discusses the following topics:
•“Setting the View” on page 2-2
•“Configuring Name Resolution” on page 2-2
•“Setting the Telnet Port” on page 2-3
•“Setting Management Application Connections” on page 2-4
•“Setting System Logging” on page 2-4
•“Setting Administrative Logins to Serial Ports” on page 2-6
•“Setting the Chassis” on page 2-6
•“Configuring Local IP Addresses” on page 2-6
•“Configuring an IP Address Pool” on page 2-8
•“Setting the Reported IP Address” on page 2-9
•“Configuring Named IP Pools” on page 2-9
•“Setting the Dynamic Host Control Protocol (DHCP) Server” on page 2-13
•“Displaying the Routing Table” on page 2-16
•“Setting Static Routes” on page 2-17
•“Setting Authentication for Dial-In Users” on page 2-21
•“Setting Call-Check Authentication” on page 2-21
•“Setting the ISDN Switch” on page 2-22
•“PortMaster Security Management” on page 2-22
See the PortMaster 4 Command Line Reference for more detailed command descriptions and
instructions.
You can also configure the PortMaster 4 using the PMVision application for Microsoft
Windows, UNIX, and other platforms supporting the Java Virtual Machine (JVM).
PMVision replaces the PMconsole interface to ComOS.
2-1
Setting the View
Setting the View
You configure global settings from the manager view. If you are not already in slot 4
(the default), use the following command to set the view to slot 4:
Command 3> set view 4
View changed form 3 to 4
Command>
Configuring Name Resolution
You can use either a network name service or the host table on the PortMaster 4 to map
hostnames to IP addresses.
Using the Host Table
Each host attached to an IP network is assigned a unique IP address. Every PortMaster
supports a local host table to map hostnames to IP addresses. If your network lacks a
computer that can perform hostname resolution, the PortMaster allows entries in a local
host table. Hostnames are used by the PortMaster only for your convenience when
using the command line interface, or if you require users to enter hostnames at the host
prompt.
To avoid confusion and reduce administrative overhead, Lucent recommends using the
Domain Name System (DNS) or Network Information Service (NIS) for hostname
resolution rather than the local host table. The PortMaster always checks the local host
table before using DNS or NIS. For information on setting the NIS or DNS name service,
refer to “Setting the Name Service.”
Setting the Name Service
The PortMaster can work with network name services such as the Network Information
Service (NIS) or the Domain Name System (DNS). Appendix A, “Networking Concepts,”
describes these name services. You must explicitly identify any name service used on
your network.
The PortMaster stores all information by address rather than name. As a result,
configuring the name server is useful only if you are using the command line interface
for administration or if you prompt a login user for a host. If you are not using either of
these features, you do not need to set the name service.
To set the name service, use the following command:
Command> setnamesvcdns|nis
Once the name service is set, you must set the address of your NIS or DNS name server
and enter the domain name of your network. See “Setting the Name Server” for
instructions.
2-2PortMaster 4 Configuration Guide
Setting the Name Server
The PortMaster supports RFC 1877, which allows remote hosts also supporting
RFC 1877 to learn a name server through PPP negotiation. You must provide the IP
address of the name server if you use a name service.
You must set a name service before you set a name server. See “Setting the Name
Service.” If you are not using a name service, you do not need a name server.
To set the name server, use the following command:
Command> setnameserverIpaddress
You can set an alternate name server with the following command:
Command> setnameserver2Ipaddress
You must set a domain name for your network after you set a name server. See “Setting
the Domain Name.”
You can disable the use of a name service by setting the name server’s IP address to
0.0.0.0.
Setting the Telnet Port
Setting the Domain Name
The domain name is used for hostname resolution. If you are using DNS or NIS, you
must set a domain name for your network.
To set the domain name of your network, use the following command:
Command> setdomainString
Setting the Telnet Port
The Telnet access port can be set to any number between 0 and 65535. The Telnet port
enables you to access and maintain the PortMaster using a Telnet connection to this TCP
port. If 0 (zero) is used, Telnet administration is disabled. The default value is 23. Ports
numbered 10000 through 10100 are reserved and should not be used for this function.
Up to four administrative Telnet sessions at a time can be active.
To set the Telnet access port to port number Tport, use the following command:
Command> settelnetTport
Using the Telnet Port as a Console Port
If the console port is set from a Telnet session, the current connection becomes the
console. This feature is useful for administrators who log in to a port using Telnet and
need to access the console for debugging purposes.
Note – Only one Telnet session can receive console messages at a time.
✍
Configuring Global Settings2-3
Setting Management Application Connections
To set the current Telnet access port as a console port, enter the following command:
Command> setconsole
Setting Management Application Connections
PMVision, ChoiceNet, and the ComOS utilities pmdial, pmcommand, pminstall,
pmreadconf, pmreadpass, and pmreset all use port 1643. For more than one of
these applications to connect at the same time, you must set the maximum number of
connections to two or more. The maximum is 10 connections.
If you use ChoiceNet to download filters dynamically, be sure to set the maximum
number of connections to 10.
To set the maximum number of concurrent connections for management applications
into the PortMaster, use the following command:
Command> setmaximumpmconsoleNumber
Setting System Logging
PortMaster products enable you to log authentication information to a system log file for
network accounting purposes.
Setting the Loghost
To set the IP address of the loghost—the host to which the PortMaster sends syslog
messages—use the following command:
Command> setloghostIpaddress
Note – Do not set a loghost at a location configured for on-demand connections,
✍
because doing so keeps the connection up or brings up the connection each time a
syslog message is queued for the syslog host.
Setting the loghost’s IP address to 0.0.0.0 disables syslog on the PortMaster. This change
requires a reboot to become effective.
RADIUS accounting provides a more complete method for logging usage information.
Refer to the RADIUS for Windows NT Administrator’s Guide and RADIUS for UNIX
Administrator’s Guide for more information on accounting.
Disabling and Redirecting Syslog Messages
By default, the PortMaster logs five types of events at the informational (info) priority
level using the authorization (auth) facility on the loghost. You can disable logging of
one or more types of events and change the facility and/or priority of log messages.
To disable logging of a type of event, use the following command:
Command> setsyslogLogtypedisabled
2-4PortMaster 4 Configuration Guide
Setting System Logging
Use the Logtype keyword described in Table 2-1 to identify the type of event you want to
disable—or enable again.
Table 2-1Logtype Keywords
Logtype
KeywordDescription
admin-logins!root and administrative logins.
user-loginsNonadministrative logins; you might want to disable this
logtype if you are using RADIUS accounting.
packet-filtersPackets that match rules with the log keyword.
commandsEvery command entered at the command line interface.
terminationMore detailed information on how user sessions terminate.
You can change the facility, the priority, or both, of log messages.
To change the facility or priority of log messages, use the following command. Be sure to
separate the Facility and Priority keywords with a period (.).
Command> setsyslogLogtypeFacility.Priority
The facility and priority can be set for each of the five types of logged events listed in
Table 2-1.
Table 2-2 and Table 2-3 show the keywords used to identify facilities and priorities.
Lucent recommends that you use the auth facility or the local0 through local7
facilities to receive syslog messages from PortMaster products, but all the facilities are
provided. See your operating system documentation for information on configuring
syslog on your host.
Table 2-2Syslog Facility Keywords
FacilityFacility NumberFacilityFacility Number
kern0cron15
user1local016
mail2local117
daemon3local218
auth4local319
syslog5local420
lpr6local521
news7local622
uucp8local723
Configuring Global Settings2-5
Setting Administrative Logins to Serial Ports
Table 2-3Syslog Priority Keywords
PriorityNumberTypically Used For
emerg0Messages indicating the system is
alert1Messages announcing action that must
crit2Critical messages
err3Error messages
warning4Warning messages
notice5Normal but significant messages
info6Informational messages
debug7Debug-level messages
To determine current syslog settings, enter the following command:
Command> show syslog
unusable
be taken immediately
Setting Administrative Logins to Serial Ports
When you log in using !root, administrative logins to the serial ports are enabled by
default. You can enable or disable administrative logins them by using the following
command
If administrative login is disabled, you can still use port C0 by setting the console
(bottom) DIP switch to the left (on) position.
:
Command> setserial-adminon|off
Setting the Chassis
When you use the PortMaster 4 as an AnyMedia™ MultiService Module (MSM), you
must specify the chassis type for PMVision to be able to display it. Use the following
command to set the PortMaster 4 as an MSM:
Command> set chassis msm-rac
Use the save all command to save changes to nonvolatile RAM. The chassis is identified
as a PortMaster 4 by default.
Configuring Local IP Addresses
The PortMaster 4 supports up to four internal routable IP addresses, which the
PortMaster advertises as host routes through RIP-2 and the Open Shortest Path First
(OSPF) routing protocol. When you configure a local IP address, it becomes the
PortMaster global address for network handles such as RADIUS, the Domain Name
System (DNS), SNMP, the intermachine trunk (IMT), and bootp. By referencing an IP
address instead of an interface, you do not lose the service if the interface goes down.
2-6PortMaster 4 Configuration Guide
Loading...
+ 161 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.