[Top] [Table Of Contents] [Prev] [Next] [Index]

About This Guide         

The PortMaster® Troubleshooting Guide can be used to identify and solve software and hardware problems in the Lucent Remote Access PortMaster family of products.


This guide is designed to be used by system administrators and network managers with knowledge of basic networking concepts.

PortMaster Documentation

The following manuals are available from Lucent Technologies. The hardware installation guides are included with most PortMaster products; other manuals 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.

This guide provides complete installation and configuration instructions for ChoiceNet server software.
This reference provides the complete description and syntax of each command in the ComOS® command set.
This guide provides a comprehensive overview of networking and configuration issues related to PortMaster products.
These guides contain complete hardware installation instructions. An installation guide is available for each PortMaster product line-IRX, Office Router, Communications Server, and Integrated Access Server.
This guide covers PMconsole Administration Software for Microsoft Windows, a graphical tool for configuring the PortMaster. The majority of the material in this guide also applies to the UNIX version of PMconsole.
Lucent recommends that you use the Java graphical user interface (GUI) PMVision rather than PMConsole to configure and manage a PortMaster.
This guide describes routing protocols supported by PortMaster products, and how to use them for a wide range of routing applications.
This guide provides complete installation and configuration instructions for Lucent Remote Authentication Dial-In User Service (RADIUS) software.

Additional References


Use any World Wide Web browser to find a Request for Comments (RFC) online.

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 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 1771, A Border Gateway Protocol 4 (BGP-4)

RFC 1812, Requirements for IP Version 4 Routers

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 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 2178, OSPF Version 2


Internetworking with TCP/IP, Volume 1: Principles, Protocols, and Architecture. Douglas Comer. Prentice Hall, Inc. 1995. (ISBN 0-13-216987-8 (v.1))

Routing in the Internet. Christian Huitema. Prentice Hall PTR, 1995.
(ISBN 0-13-132192-7)

TCP/IP Network Administration. Craig Hunt. O'Reilly & Associates, Inc. 1994.
(ISBN 0-937175-82-X)

TCP/IP Illustrated, Volume 1: The Protocols. W. Richard Stevens. Addison-Wesley Publishing Company. 1994. (ISBN 0-201-63346-9)

Internet Routing Architectures. Bassam Halabi. Cisco Press, 1997.


Document Conventions

The following conventions are used in this guide:




Bold font

Indicates a user entry-a command, menu option, button, or key-or the name of a file, directory, or utility, except in code samples.

Italic font

Identifies 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.

set syslog Logtype {[disabled] [Facility.Priority]}

Vertical bar (|)

Separates two or more possible options in command syntax.

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 results in equipment failure or loss of data.

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 authorized sales channel partner.

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.

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/index.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.

For North America, Latin America, and the Asia Pacific Region

Contact Lucent Remote Access Monday through Friday between the hours of 6 a.m.
and 6 p.m. (GMT -8).

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, click Services, and then click Training.

Subscribing to PortMaster Mailing Lists

Lucent maintains the following Internet mailing lists for PortMaster users:

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.
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.

[Top] [Table Of Contents] [Prev] [Next] [Index]

Copyright © 1998, Lucent Technologies. All rights reserved.