Home

PortMaster® 4 User Manual Addendum

1. 1 23 Primary Manager Module Failover 1 23 Troubleshooting Communication between Manager Modules 1 24 Replacing a Failed Manager 1 24 Upgrading a Replacement Manager Module to ComOS 4 2 1 25 RADIUS Improvements for L2TP New L2TP Command sa dade dd aa 2 1 New L20P Bearer sea ee ee ee eee es 2 1 New RADIUS Tunnel Attributes for L2TP 2 1 RADIUS Tunnel Attribute Tags 2 2 ComOS 4 2 Commands Redundant Manager Module Commands 3 1 RADIUS Commands 3 8 GOmmMand eee ay ar a ORS oo ee he RE Be oa rererere rere anni 3 12 Global Command ae amp 2 ru a a eae Bk Be Bae Be a 3 13 SS7 Commands 222322222 naar ge eee ae a eee ase 3 13 Cable Specifications Modem ee Sta Se 1 Console Cable ru sa u oe tk ER RD 2 RIJ 45 Gable bat ba bs bated 2 Ethernet Cable Specifications A 3 Index PortMaster4 User Manual Addendum About This Addendum Audience The PortMaster 4 User Manual Addendum from
2. Command Secondary gt set debug off Command Secondary gt reset console show bootlog This command shows the reboot information and stack traces of the boards and modules that are stored in a boot log file show bootlog Usage ComOS 4 2 supports the enhanced show bootlog command which now displays register and software version information in the output Use this command to capture reboot information without using a console The PortMaster 4 reserves a portion of its memory to store stack traces and the last process ID The boot log is stored in the nonvolatile RAM file system in a file named bootlog a circular buffer up to 64KB in length PortMaster 4 User Manual Addendum Redundant Manager Module Commands show smm backup When a board in the PortMaster 4 reboots it checks for information in the reserved area and sends it to the boot log and the console if configured This portion of memory is not overwritten at boot time so this information can be preserved To erase boot log information use the erase file bootlog command To translate the last process and stack trace data send the information to Lucent Netcare Technical support The information that is stored in the boot log consists of the following Time Stamp Time elapsed since the board was last rebooted Slot Slot where the reboot occurred Description Indicates if the unit was powered on soft booted or crashed If a crash occurred the stack trace is dis
3. 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 NetCare Technical Support The PortMaster 4 comes with a 1 year hardware warranty For all technical support requests record your PortMaster 4 ComOS version number and report it to the staff of NetCare Professional Services or your authorized sales channel partner New releases and upgrades of PortMaster software are available at http www livingston com forms one click dnload cgi or by anonymous FIP from ftp ftp livingston com pub le About This Addendum ix PortMaster Training Courses 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 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 sales channel partner in this region contact the Lucent NetCare EMEA Support Center Monday through Friday 24 hours a day By voice dial 33 4 92 38 33 33 By fax dial 33 4 92 38 31 88 By electronic mail email send mail to emeacallcenter lucent com For North America CALA and the Asia Pacific Region Contact Lu
4. 3 Third alternate gateway Ipaddress IP address of the alternate gateway Usage To use this command you must first select a slot for configuration using the set view command Use this command to configure the alternate gateways for each card To remove an alternate gateway set the IP address to 0 0 0 0 Each slot card first attempts to connect to the primary gateway If the attempt is unsuccessful the card retries in the following order 1 First alternate gateway 2 Second alternate gateway 3 Third alternate gateway 4 Primary gateway Only one SS7 gateway must be active at any given time When an alternate gateway is enabled after a line board detects that the primary gateway is unavailable a failover is accomplished within 30 seconds or less The PortMaster 4 retains calls between failovers and informs the new gateway about existing calls PortMaster 4 User Manual Addendum SS7 Commands set imt alt Note If multiple gateways are running at the same time a situation can occur in which the first connection attempt might succeed for an alternate gateway and the different slots become connected to different gateways When the primary gateway comes back online the alternate gateways must be shut down to allow the PortMaster 4 to switch back to the primary gateway See Also set imt parms ComOS 4 2 Commands 3 15 557 Commands set imt alt 3 16 PortMaster 4 User Manual Addendum Cable Specifications A Th
5. Lucent Technologies provides the following updates to the PortMaster 4 User Manual e Redundant Manager Modules Instructions for installing configuring and performing basic hardware troubleshooting on redundant manager modules in the PortMaster 4 e ComOS 4 2 Commands Descriptions of ComOS 4 2 command line interface commands e RADIUS Improvements for L2TP New RADIUS attributes and tunnel attribute tags to support the Layer 2 Tunneling Protocol L2TP on the PortMaster 4 Consult the PortMaster 4 User Manual for installation configuration and command information for the PortMaster 4 Integrated Access Concentrator For additional configuration maintenance and troubleshooting information common to all PortMaster products see PortMaster Documentation This addendum is designed to be used by qualified system administrators and network managers Knowledge of basic networking concepts is required PortMaster Documentation The following manuals are available from Lucent Technologies Unless otherwise noted 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 e ChoiceNet Administrator s Guide This guide provides complete installation and configuration instructions for Choi
6. Redundant Manager Module Events Alarm Description Slot 4 becoming primary manager This alarm reported by the primary manager is generated when a system manager module recognizes itself as the primary manager This event can take place after the bootup decision process or after a failover has occurred PortMaster 4 User Manual Addendum Using PMVison 1 8 with a Redundant System Manager Table 1 2 SNMP Alarms for Redundant Manager Module Events Alarm Description Slot 5 becoming This alarm reported by the secondary manager is secondary generated when a system manager module recognizes itself manager as the secondary manager Primary manager This alarm is generated by the secondary manager module in slot 4 after it fails to get a response to its hello messages for 5 failed seconds five hello messages are ignored by the primary manager module Secondary This alarm reported by the primary manager is generated manager in slot when the primary manager does not receive hello messages 5 failed from the secondary for 30 seconds Secondary This alarm is generated by the primary manager module manager when it detects a secondary manager module in slot 5 This detected in alarm conveys the same information as Slot 5 becoming slot 5 secondary manager except that it is reported by the primary module Can t hear This alarm is generated when the communication between manager in managers fail
7. address and MAC addresses for other devices in the system are software assigned from the address range based on the Ethernet card s MAC address The primary manager in slot 4 assigns MAC addresses immediately after bootup During failover system components retain the MAC address assigned by the primary manager in slot 4 Note The PROM of the Ethernet card attached to the manager module contains the en Follow these instructions to connect an Ethernet cable to the Ethernet 10 100BaseT interface Required Equipment One of the following Ll Category 5 twisted pair cable as specified by the EIA TIA 568 B wiring standard with an RJ 45 connector See RJ 45 Cable on page A 2 and Ethernet Cable Specifications on page A 3 for more information MII cable with an MII connector Installing and Working with the Redundant System Manager Module 1 11 Connecting an Ethernet Cable Procedure 1 Remove the cover from the cable guide if necessary 2 Run the cable through the cable guide duct until it is directly over the manager module 3 Pull the cable through the fingers of the cable guide duct as shown in Figure 1 10 4 Connect the cable to the RJ 45 or MII Ethernet 10 100BaseT interface see Figure 1 11 If both interfaces are connected the system uses the MII by default 5 If you have finished inserting modules and boards and connecting lines replace the cable guide cover by squeezing the duct fingers to
8. if the primary manager fails the secondary manager takes over Although all active calls are dropped during failover to the secondary manager power to the entire system is never interrupted and call traffic resumes as soon as the secondary manger takes over as primary and resets the individual line boards When operating the PortMaster 4 with a single manager module you must install the module in slot 4 You install the backup manager module in slot 5 When you boot the system for the first time the module in slot 4 starts up as the primary manager and the module in slot 5 starts up as the secondary See Primary Manager Module Selection at Startup on page 1 18 for details 1 1 Redundant System Manager Module Description Each system manager module consists of a manager board and an Ethernet 10 100Mbps board The manager board manages and administers the installed line boards The manager board communicates with installed line boards at 155Mbps speeds through an embedded Asynchronous Transfer Mode ATM cell switching network linked to the chassis passive backplane Manager modules communicate with each other via a 115Kb universal asynchronous receiver transmitter UART channel Physical Characteristics of a Manager Module Each manager module provides the following see Figure 1 1 CO port for a console connection with a null modem cable or for an asynchronous connection to an external modem The green LED on the CO por
9. in Figure 1 12 Figure 1 12 Pulling a Cable through the Cable Guide 1406_0009 4 Connect the cable to the Ethernet 10BaseT interface see Figure 1 13 Figure 1 13 Ethernet 10BaseT Interface on the Manager Module Ethernet 10BaseT Ether0 Dre 1406_0007 5 If you have finished inserting modules and boards and connecting lines replace the cable guide cover by squeezing the duct fingers together with one hand and sliding the cover over the duct fingers with the other 1 14 PortMaster 4 User Manual Addendum Configuring a Redundant System Manager Module Configuring a Redundant System Manager Module Before following the instructions in this section you must have installed a redundant system manager module in slot 5 of a fully configured functioning PortMaster 4 Use the following procedure to copy the PortMaster 4 system configuration to a redundant manager module 1 Review Installation and Configuration Requirements on page 1 3 to make sure you are ready to configure 2 Connect to the primary manager module in slot 4 via the console or an Ethernet port and enter the following command Command gt save all This command copies the system configuration from the primary manager module to the redundant secondary manager module s nonvolatile memory You can now configure the redundant manager s Ethernet interface Configuring the Ethernet In
10. in slot 5 Figure 1 4 Note The physical slots are numbered 0 through 9 from left to right Although a manager module is physically installed in slot 4 or slot 5 the Ethernet board of the module functioning as the primary manager is monitored through virtual slot 10 2 Insert the manager module in slot 5 gently guiding the module into the slot If you have trouble sliding the module into the card guide gently wiggle it back and forth to help it slide in Installing and Working with the Redundant System Manager Module 1 5 Installing a Redundant System Manager Module Figure 1 4 Installing the Redundant System Manager Module redundant system manager module slot 5 3 When the module is completely inserted in the slot close the top and bottom tabs so they are flush with the face of the chassis Closing the tabs causes the module to connect with the backplane DIP Switch Settings The DIP switches on each manager module are located between EtherO and Etherl see Figure 1 5 Each switch is off when turned to the left and on when turned to the right e DIP switch 1 turned to the left forces the CO port to transmit at 9600 baud 8 bits no parity and 1 stop bit for use as a console port When switch 1 is turned to the right CO can be configured as an asynchronous port e DIP switch 2 turned to the left sets the PortMaster 4 for netbooting When switch 2 is
11. it as the primary authentication server and sends it the authentication request from the next login attempt 4 Ifthe designated primary server does not respond after three attempts starts the failover process again The server currently designated as primary is marked with an asterisk in the output of the show global command To set the request interval use the set authentication interval command Example Command gt set authentication failover off Auth failover changed from on to off See Also set authentication interval page 3 9 set authentication interval This command sets the number of seconds that a PortMaster waits for a response from a RADIUS authentication server set authentication interval Seconds Seconds Value between 1 and 255 The number of seconds that must elapse between RADIUS access request retransmissions if the PortMaster receives no response from a RADIUS authentication server The default is 3 seconds and 0 resets the value to the default Usage The Seconds value determines how long the PortMaster waits before sending a subsequent request to the authentication server In addition the PortMaster waits two times this value to initiate failover For example if set authentication interval 6 is used failover occurs in 12 seconds Example Command gt set authentication interval 15 Auth retry interval changed from 5 to 15 sec ComOS 4 2 Commands 3 11 L2TP Command set 12tp id for host S
12. manager module Usage 4 2 supports the enhanced save command with the new keywords peer also and local only to allow the PortMaster 4 to save to the primary manager module or to both the primary and secondary manager modules See the save command description in the PortMaster 4 Command Line Reference for additional information See Also save set altname This command sets the prompt for the system manager module occupying slot 5 in the PortMaster 4 set altname Hostname Hostname Alternate hostname of up to 39 characters for the manager module occupying slot 5 See Also set host ComOS 4 2 Commands 3 5 Redundant Manager Module Commands set debug m2m 3 6 set debug m2m This command debugs the manager to manager protocol that runs between the primary and secondary manager modules set debug m2m Usage Use this command to see if the universal asynchronous receiver transmitter UART is functioning properly between the manager modules Example Command Secondary gt set console Setting CONSOLE to admin session Command Secondary gt set debug m2m Enabling Redundant Manager debugging Command Secondary gt MGR2MGR Pinging at 5830 Com 3999a8 silence 5 0 ping 18MGR2MGR Sending hello My state 3 his state 2 MGR2MGR Sending type 0x1 36 bytes seq 58 MGR2MGR Message type 0x81 length 36 sequence 58 MGR2MGR Received hello My state 3 his state 2 Hello says my state is 3 his state is 2
13. supplier Any repairs or alterations made by the user to this equipment or equipment malfunctions may give the telecommunications company cause to request the user to disconnect the equipment Users should ensure for their own protection that the electrical ground connections of the power utility telephone lines and internal metallic water pipe system if present are connected together This precaution may be particularly important in rural areas Caution Users should not attempt to make such connections themselves but should contact the appropriate electric inspection authority or electrician as appropriate European Terminal Marking 188 The PortMaster Communications Server carries the 188 approval marking in accordance with the CE Marking Directive 93 68 EEC This marking may be found on the base of the unit This equipment has been tested and is compliant with the following European Directives e 91 263 Telecommunications Terminal Equipment e 73 23 Low Voltage Directive e 89 336 EEC ElectroMagnetic Compatibility as amended by 92 31 EEC Pan European Approval BTZ the German Notified Body has issued Pan European Approval to the PortMaster in accordance with the TTE Directive 91 263 EEC This approval is valid throughout the European Economic Market This approval is valid in the following European Union Countries Belgium Denmark Finland France Germany Great Britain Greece Holland Icel
14. the primary manager console saves the configuration to nonvolatile memory on both manager modules Installing and Working with the Redundant System Manager Module 1 15 Configuring a Redundant System Manager Module 3 Use the commands in Table 1 1 as necessary to configure and operate the redundant manager module Refer to Chapter 3 ComOS 4 2 Commands for a detailed description of each command Note The redundant manager always displays Secondary in the prompt You can observe in the logs how the prompt shifts from one manager to the other when they change roles Table 1 1 Redundant Manager Module Configuration Commands Action Command Syntax Event Update the Command gt save all This command entered on the secondary manager with the current system configuration Save configuration information to the primary or secondary manager Configure an Ethernet address on the secondary manager Update ComOS on the secondary manager Copy a line card executable file to the redundant manager You can also copy configuration files View manager module status Name the redundant manager module Command gt save Keyword local only Command gt save Keyword peer also e Command gt set ether0 address Ipaddress Command Secondary gt tftp get Ipaddress Filename local only Command gt copy Subdirectory Filename source peer Subdirectory Filename destination Command g
15. Master 4 chassis PortMaster 4 User Manual Addendum Handling System Manager Module Failure 4 Insert a new manager module See Installing a Redundant System Manager Module on page 1 5 for instructions 5 Connect a console cable and EtherO and Ether lines See Connecting a Console on page 1 7 and Connecting an Ethernet Cable on page 1 10 6 Enter the following command to configure an Ethernet address for Ether0 Command gt set ether0 address Ipaddress See Configuring the Ethernet Interfaces on page 1 15 for more information 7 Enter the following commands to save changes to nonvolatile memory and activate the configuration Command gt save all Command gt reboot secondary Upgrading a Replacement Manager Module to ComOS 4 2 This section describes how to upgrade a spare system manager module to ComOS 4 2 or later from the command line You can also use PMVision 1 8 to upgrade the PortMaster 4 module Earlier versions of PMVision and the older programs pminstall PMconsole and PMconsole for Microsoft Windows do not recognize the redundant system manager module feature and view each manager module in the PortMaster 4 as a separate system Note Be sure to use PMVision 1 8 on a PortMaster 4 with a redundant system manager AN Follow this procedure to upgrade a spare system manager module to ComOS 4 2 or later 1 Make sure that you have the proper hardware and software and take the proper saf
16. PortMaster 4 User Manual Addendum Lucent Technologies 4464 Willow Road Pleasanton CA 94588 925 737 2100 800 458 9966 March 2000 7820 0963 001 Copyright and Trademarks 2000 Lucent Technologies All rights reserved PortMaster ComOS and ChoiceNet are registered trademarks of Lucent Technologies PMVision IRX and PortAuthority are trademarks of Lucent Technologies PolicyFlow is a service mark of Lucent Technologies All other marks are the property of their respective owners Disclaimer Lucent Technologies 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 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 FCC Class A Notice United States Computing devices and peripherals manufactured by Lucent Technologies generate use and can radiate radio frequency energy and if not installed and used in accordance with the instructions contained in this manual may cause interference to radio communications Such equipment has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of the FCC Rules which are designed to provide reasonable protection against radio interfe
17. and Ireland Italy Luxembourg Portugal Spain and Sweden European CE approvals are automatically recognized by Norway In addition to compliance with the ETSI based European standards I CTR 3 Net 3 Bridging Measures NET 3 and ETS 300 047 the PortMaster has been tested and complies with the following National Delta requirements e French delta requirements CSE 10 21 A e German delta requirements 223 ZV 25 Contents Contents About This Addendum Audience siti est be bbb bb Deb ee ec ohbbesocehebeso IRRE vii PortMaster Documentation 0 2 0 comes nennen ee eee ee vii REGS a viii Document Conventions ee eee viii Document AdvisOries Daun DEE SAAR WERE BRASS BY ix Contacting Lucent NetCare Technical Support ix For THE rise aan ie ale alien x For North America CALA and the Asia Pacific Region x PortMaster OULSCS nu ee eee eee ee eee eS x Subscribing to PortMaster Mailing Lists x 1 Installing and Working with the Redundant System Manager Module Redundant System Manager Module Description 1 1 Overview of Redundant Manager Operation 1 1 Physical Characteristics of Manager Module 1 2 Installation and Configuration R
18. anual Addendum Connecting an Ethernet Cable e Media independent interface MII used to connect other wiring types copper or fiber for example to the 10 100BaseT Ethernet Devices attached to the MII interface must be MII compliant Lucent strongly recommends that you configure and connect lines to both EtherO and Etherl interfaces on each manager module These interfaces must be on different Ethernet subnetworks However because Etherl interface on the redundant manager inherits its IP address from the primary manager be sure to connect the Etherl interface on the redundant manager to the same subnetwork as the Etherl interface on the primary manager module See Configuring the Ethernet Interfaces on page 1 15 Ethernet 10 100BaseT When using a PortMaster 4 with a redundant system manager module you must configure the Etherl interface on both manager modules The Etherl interface has the following characteristics and functions e Resides on the Ethernet board which receives power from the manager board The Ethernet board and the manager board make up the manager module e Communicates with the manager board over the PortMaster 4 passive ATM backplane e Contains CPU for inbound data and a CPU for outbound data e Remains active during low power or excessive heat conditions e 5 generally used to carry network traffic MAC address which is actually a MAC address range Conceptually the Ethernet card has the MAC
19. ble specifications for the PortMaster 4 Ethernet interface Table A 4 Ethernet Cable Specifications Ethernet Connector Transmission Type Type Cable Type Distance RJ 45 RJ 45 for 10BaseT Category 5 A Category 5 distributed cable that meets unshielded the ANSI EIA 568 A standard has a twisted pair maximum length of 328 feet 100 meters divided as follows RJ 45 RJ 45 for 100BaseT Category 5 nshielded 20 feet 6 meters between the hub and twisted pair the patch panel if used 295 feet 90 meters from the wiring closet to the wall outlet e 10 feet 3 meters from the wall outlet to the desktop device A maximum of four repeaters Ethernet cable must be grounded at both ends 1 For NEBS compliant installations Category 5 shielded twisted pair cable must be used Cable Specifications A 3 Ethernet Cable Specifications A 4 PortMaster 4 User Manual Addendum Index A accounting packets RADIUS 3 8 accounting packets setting intervals 3 9 accounting server RADIUS retry count 3 8 retry interval 3 9 alternate SS7 gateways setting 3 14 asynchronous ports 1 2 attributes for RADUS L2TP tunneling 2 1 authentication RADIUS failover 3 10 interval 3 11 B boot log erasing 3 7 1 8 1 1 8 cables console connecting 1 7 Ethernet connecting 1 10 Ethernet specifications A 3 modem connecting 1 9 RJ 45 A 3 cable specifications console cable A 2 Ethernet in
20. bug m2m Command gt set debug off Command gt reset console Entering this command is the only way you can reboot the primary manager from the secondary manager You can also reboot the secondary from the primary with the reset slot command These commands display the messages sent over the UART channel between the primary and secondary manager modules to the screen of your console session These commands turn debug mode off and redirect all debug output to null Primary Manager Module Selection at Startup The PortMaster 4 uses the following criteria for primary manager module selection when you turn on the unit 1 A manager module is primary if it does not encounter another manager module for 4 seconds during the boot up process 2 Iftwo manager modules boot at the same time the manager in slot 4 is primary and the manager in slot 5 is secondary After boot up the secondary manager sends hello messages at 1 second intervals to the primary manager and the primary manager responds See Handling System Manager Module Failure on page 1 23 for information about manager module failover and replacement SNMP Alarms Supporting Redundancy The SNMP alarms shown in Table 1 2 have been added for events related to the redundant system manager module feature These alarms are valid for either slot 4 or slot 5 When slot 5 is primary the slot numbers in the message are reversed Table 1 2 SNMP Alarms for
21. cable guide duct until it is directly over the manager module 3 Pull the cable through the fingers of the cable guide duct as shown in Figure 1 8 Figure 1 8 Pulling a Cable through the Cable Guide a 1406_0009 4 Attach the RJ 45 end of the cable to the CO port of the manager module see Figure 1 9 Installing and Working with the Redundant System Manager Module 1 9 Connecting an Ethernet Cable Figure 1 9 Console Port on the System Manager Module 1406_0007 If you have finished inserting modules and boards and connecting lines replace the cable guide cover by squeezing the duct fingers together with one hand and sliding the cover over the duct fingers with the other Ensure that DIP switch 1 is turned to the right Attach the RS 232 end of the cable to the external modem Refer to the documentation that came with your external modem for information on how to attach the RS 232 cable Connecting an Ethernet Cable The PortMaster 4 supports the following Ethernet connections on each manager module 10 100BaseT used as the primary uplink This Ether interface is located on the Ethernet board but powered from the manager board It is used for syslog traceroute Telnet RADIUS ChoiceNet the Domain Name System DNS and TFTP 10BaseT used for private network management This EtherO interface is physically located on the manager board PortMaster 4 User M
22. ceNet server software e PMVision User s Guide This guide provides instructions for installing configuring and using the PMVision monitoring and configuration application for PortMaster products This guide is not available in printed form e PortMaster 4 User Manual This collection of the following three standalone manuals provides instructions and commands for installing configuring and troubleshooting PortMaster 4 products Vil RFCs PortMaster 4 Installation Guide PortMaster 4 Configuration Guide PortMaster 4 Command Line Reference It also includes a comprehensive table of contents glossary and master indexes e PortMaster Routing Guide This guide describes routing protocols supported by PortMaster products and how to use them for a wide range of routing applications e PortMaster Troubleshooting Guide This guide can be used to identify and solve software and hardware problems in the PortMaster family of products e RADIUS for UNIX Administrator s Guide This guide provides complete installation and configuration instructions for Lucent Remote Authentication Dial In User Service RADIUS software on UNIX platforms RFCs To find a Request for Comments RFC online visit the website of the Internet Engineering Task Force IETF at http www ietf org 1157 A Simple Network Management Protocol SNMP RFC 1212 Concise MIB Definitions RFC 1213 Management Information Base fo
23. cent NetCare 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 and Latin America CALA or 1 925 737 2100 from elsewhere By email send mail as follows From North America and CALA to support livingston com From the Asia Pacific Region to asia support livingston com Using the World Wide Web see http www livingston com PortMaster Training Courses Lucent NetCare Professional Services offers hands on technical training courses on PortMaster products and their applications For course information schedules and pricing visit the Lucent NetCare website at http www netcaredata com 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 4 User Manual Addendum Subscribing to PortMaster Mailing Lists e portmaster modems a discussion of problems and solutions for PortMaster 4
24. condary manager when issued from either manager module Note Use the save all command to copy the current system configuration to the secondary manager module before rebooting it Usage 4 2 supports the enhanced reboot commands on the PortMaster 4 to support a redundant manager module Entering the reboot command without any arguments on the primary manager module reboots the entire PortMaster 4 Entering reboot from the secondary manager module reboots only the secondary manager module For additional information on redundant manager module failover see Primary Manager Module Failover on page 1 23 Examples Command gt reboot me Rebooting PortMaster Command Secondary gt lt system reboots gt Command gt reboot secondary Command gt See Also reboot ComOS 4 2 Commands 3 3 Redundant Manager Module Commands rename This command saves a copy of a file under another name to the local module s nonvolatile RAM rename Subdirectory Filename original Filename copy Subdirectory Path to the file Filename original Name of the file to be copied Filename copy Name of the file to save reset secondary This command shuts down and immediately restarts the secondary manager module reset secondary slotSlotnumber secondary Resets the secondary manager module when issued from either manager module This command performs the same function as the reboot secondary com
25. e Problems and Solutions on the Manager Module Continued LED Behavior Possible Cause Explanation or Possible Solution Network amber LED on an Ethernet interface is not lit An undefined problem occurred at startup but the cause cannot be determined from LED behavior If the PortMaster 4 is not receiving or sending traffic the network LED is not lit Refer to the solution column Verify that the network cabling is correct Try booting in console mode and observe the boot messages See Observing Boot Messages on page 4 3 of the PortMaster 4 Installation Guide If the boot messages do not suggest a solution record the information and contact Lucent NetCare technical support Handling System Manager Module Failure This section explains the failover process for the primary system manager module and provides instructions for troubleshooting communication between the manager modules replacing a failed manager module and upgrading a replacement manager Primary Manager Module Failover Primary manager module failover on the PortMaster 4 proceeds as follows 1 If the secondary manager module does not receive responses to five consecutive hello messages it listens for the heartbeat of the primary 2 If it detects a heartbeat the secondary does not take over as primary manager but generates a Can t hear manager in slot 4 SNMP alarm 3 Ifthe secondary manager does not detect a hea
26. e a redundant system manager module you must have the appropriate hardware and software and must take the proper safety precautions Verifying Hardware and Software for Redundant Operation Before installing and configuring the redundant manager module feature on your PortMaster 4 make sure of the following 1 Verify that your PortMaster 4 chassis has the Revision backplane Check the backplane for the revision letter C The revision letter is located behind slot 2 2 Make sure that both system manager modules are capable of redundancy Verify that the model number on each module ends in R Or check the label on the box that each module was shipped in for a manufacture date after July 1999 3 Verify that both system manager modules have ComOS 4 2 loaded Warning Use of a version earlier than 4 2 can damage PortMaster 4 hardware Installing and Working with the Redundant System Manager Module 1 3 Installation and Configuration Requirements Safety Precautions N AN Warning DC models only Before working on equipment that is connected to power lines remove jewelry such as rings necklaces and watches Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals If an electrical accident occurs turn off the emergency power switch for the room in which you are working cautiously unplug the system s power and get medical ass
27. econdary on 149 198 32 170 5 System Manager 4 2b5 9912031416 5 Primary on Configuring Manager Information You can set the IP address for the EtherO port of either manager by double clicking the desired manager module name and clicking the Ethernets button on the resulting display Lucent recommends that you issue a reboot command using the Command option after changing the IP address You can also set the system name for each module by selecting the Configure gt Global option Downloading an Image of ComOS The ComOS for both modules can be updated simultaneously In PMVision select Maintain gt Upgrade to perform the update Enter or browse to the location of the ComOS image and click the Update button Troubleshooting a Redundant System Manager Module When troubleshooting a redundant manager module system always verify that both manager modules are running ComOS 4 2 or later A possible indication of an incompatible ComOS on one of the modules is a solidly lit amber CO light Table 1 3 identifies manager module LED behavior possible causes of the behavior and explanation or possible solution Table 1 3 Hardware Problems and Solutions on the Manager Module LED Behavior Possible Cause Explanation or Possible Solution Green CO LED is lit Manager module is Normal behavior when a redundant primary manager module is installed Green CO LED off Manager module is Normal behavior when a redundant secondary manager module i
28. ed by an external device Terminal settings are incorrect or a connection or cable is inoperable There is no link integrity Heavy traffic can cause the network LED to blink so rapidly that it appears to be solidly lit However If packets cannot be passed you might have an incorrectly cabled network Remove the manager module from the PortMaster 4 chassis and verify the following The SIMM is firmly seated The nonvolatile RAM is firmly in place If all items have been verified and the problem is not fixed refer to Observing Boot Messages on page 4 3 in the PortMaster 4 Installation Guide and boot in console mode If the boot messages do not suggest a solution record the information and contact Lucent NetCare technical support If the LED stays solidly lit or does not light after you have removed all external devices contact Lucent NetCare technical support Verify terminal settings of 9600 baud 8 data bits 1 stop bit a parity of none and software control on XON XOFF Verify that DIP switch 1 is turned to the left Verify that you have a working console null modem cable and that it is properly connected at both ends For cable information see Console Cable on page A 2 Check the connection to the hub Verify that the network cabling is correct 1 22 PortMaster 4 User Manual Addendum Handling System Manager Module Failure Table 1 3 Hardwar
29. ee Also set authentication failover page 3 10 L2TP Command 3 12 4 2 introduces the following Layer 2 Tunneling Protocol L2TP command for the PortMaster 4 For a complete description of L2TP commands see Chapter 17 of the PortMaster 4 Command Line Reference set 12tp id for host This command sets an L2TP access concentrator LAC host to report itself using the RADIUS Tunnel Assignment ID value instead of its IP address or hostname during tunnel negotiations set 12tp id for host on off on Sets a LAC host to identify itself by its RADIUS Tunnel Assignment ID during L2TP negotiations off Sets a LAC host to identify itself using its IP address or hostname during L2TP negotiations This is the default Usage To use this command on a line board designated as a LAC you must first select a slot for configuration using the set view command By default a host identifies itself with an IP address during L2TP negotiations You can use this command to enable a host to identify itself with the Tunnel Assignment ID that you assign in RADIUS Example Command gt set view 3 view set to slot 3 Command 3 gt set 12tp id for host on OK PortMaster 4 User Manual Addendum Global Command set chapname Global Command set chapname This command sets a name that the entire PortMaster 4 uses to identify itself during Challenge Handshake Authentication Protocol CHAP negotiations set chapname Name Name Name of u
30. equirements 1 3 Verifying Hardware and Software for Redundant Operation 1 3 Safety Precautions 0 ie dee deda eee eee eens 1 4 Grounding Wrist Strap Instructions 1 4 Installing a Redundant System Manager Module 1 5 DIP Switeh Settings aww Aas Acie oe che ln le he a de Se as 1 6 Connecting a Console ss 2 daai GR Gad dW Rad an ee BE we Se 1 7 Optional Connecting an External Modem 1 9 Connecting an Ethernet Cable 1 10 Ethernet 707700 ts one cette eae He cha ee ee 1 11 Ethernet tOBasel ict testeta tet eet 1 13 Configuring a Redundant System Manager Module 1 15 Configuring the Ethernet Interfaces 1 15 vi Primary Manager Module Selection at Startup 1 18 SNMP Alarms Supporting Redundancy 1 18 Using PMVison 1 8 with a Redundant System Manager Module 1 19 Configuring Manager Information 1 20 Downloading an Image of ComOS 1 20 Troubleshooting a Redundant System Manager Module 1 20 Handling System Manager Module Failure
31. ety precautions a See Installation and Configuration Requirements on page 1 3 for instructions b Make sure that the manager module in slot 4 is running ComOS 4 2 If it is not upgrade this manager before going on to Step 2 2 Prepare the spare manager module for netbooting a Set DIP switch 2 to the left See DIP Switch Settings on page 1 6 for more information Installing and Working with the Redundant System Manager Module 1 25 Handling System Manager Module Failure 1 26 b Set up a directory structure to load ComOS 4 2 for netbooting to the manager s EtherO IP address Procedures for netbooting are located at http www livingston com tech technotes Scroll to PortMaster Troubleshooting click Netboot Procedures then select the procedure for your platform Insert the spare manager module in slot 5 See Installing a Redundant System Manager Module on page 1 5 for instructions Connect a console cable and EtherO and Ether lines See Connecting a Console on page 1 7 and Connecting an Ethernet Cable on page 1 10 Connect to the spare manager module If an IP address netmask and gateway address for the Ether0 interface are not provided by Dynamic Host Configuration Protocol DHCP services enter the following commands to configure them Command gt set ether0 address Ipaddress Command gt set netmask Netmask Command gt set gateway Ipaddress Command gt save all See Configur
32. f the cable guide duct as shown in Figure 1 6 Installing and Working with the Redundant System Manager Module 1 7 Connecting a Console Figure 1 6 Pulling a Cable through the Cable Guide 1406_0009 4 Attach the RJ 45 connector to the CO or C1 port of the manager module see Figure 1 7 Figure 1 7 Asynchronous Ports the System Manager Module or 1406_0007 5 Attach the RS 232 end of the cable to a dumb terminal or computer running terminal emulation software 6 If you have finished inserting modules and boards and connecting lines replace the cable guide cover by squeezing the duct fingers together with one hand and sliding the cover over the duct fingers with the other 7 Ensure that DIP switch 1 on the manager module is turned to the left 1 8 PortMaster 4 User Manual Addendum Optional Connecting an External Modem 8 Set the PC or terminal to 9600 baud 8 data bits 1 stop bit a parity of none and software flow control on KON XOFF Optional Connecting an External Modem Follow these instructions to connect an external modem for remote administration and troubleshooting Required Equipment RJ 45 to RS 232 modem cable See Modem Cable on page A 1 for more information LJ External modem Procedure 1 Remove the cover from the cable guide if necessary 2 Run the end of the cable with the RJ 45 connector through the
33. gether with one hand and sliding the cover over the duct fingers with the other Figure 1 10 Pulling a Cable through the Cable Guide 1406_0009 PortMaster 4 User Manual Addendum Connecting an Ethernet Cable Figure 1 11 Ethernet 10 100BaseT Interfaces on the Redundant Manager Module 4 or A 2 _ RJ 45 Ethernet 10 100BaseT Ether1 MII Ethernet 10 100BaseT alternative Ether1 1406_0007 Ethernet 10BaseT Because you communicate with the system manager modules over the network via the EtherO interfaces Lucent strongly recommends that you configure EtherO on both manager modules when operating the PortMaster 4 with a redundant system manager module Follow these instructions to connect an Ethernet cable to the Ethernet 10BaseT interface of the redundant manager module Required Equipment Category 5 unshielded twisted pair cable as specified by the EIA TIA 568 A wiring standard with an RJ 45 connector See RJ 45 Cable on page A 2 and Ethernet Cable Specifications on page A 3 for more information Procedure 1 Remove the cover from the cable guide if necessary 2 Run the cable through the cable guide duct until it is directly over the manager module Installing and Working with the Redundant System Manager Module 1 13 Connecting an Ethernet Cable 3 Pull the cable through the fingers of the cable guide duct as shown
34. her0 address command 1 16 1 25 1 26 set gateway command 1 26 set imt alt command 3 14 set imt reject cause command 3 13 set 12tp id for host command 2 1 3 12 set netmask command 1 26 setting DIP switches 1 6 show bootlog command 3 6 show smm backup command 1 16 3 7 specifications cable pinout A 1 Ethernet cable A 3 SS7 setting alternate gateways 3 14 SS7 commands 3 13 SS7 RADIUS rejects setting action to be taken 3 13 stack traces translating 3 6 syslog 1 10 T Telnet 1 10 PortMaster 4 User Manual Addendum 1 10 3 8 tftp get command 1 26 tftp get local only command 1 16 3 8 tftp get peer also command 3 8 traceroute 1 10 troubleshooting manager module 1 20 U upgrading ComOS a replacement manager module 1 25 using PMVision 1 26 with netboot 1 25 Index Index 3 Index Index 4 PortMaster 4 User Manual Addendum
35. ing the Ethernet Interfaces on page 1 15 for more information Upgrade ComOS on the spare manager module to ComOS 4 2 You can use the tftp get command to download ComOS by entering the command as follows from the spare manager module Command gt tftp get Ipaddress Filename Replace Ipaddress with the IP address of the TFIP server and Filename with the name of the ComOS image You can also use PMVision 1 8 or later to upgrade the manager Set DIP switch 2 to the right to turn off netbooting on the manager module PortMaster 4 User Manual Addendum RADIUS Improvements for L2TP 2 4 2 adds the new Layer 2 Tunneling Protocol L2TP set 121 id for host command and the new L2TP Bearer Type attribute and supports RADIUS enhancements for authorization authentication and accounting of L2TP users New L2TP Command You can set an L2TP access concentrator LAC to use the RADIUS Tunnel Assignment ID value instead of its IP address or hostname during L2TP tunnel negotiations with its peer the L2TP network server LNS This attribute allows for more precise tracking of tunnel usage for accounting To specify whether a LAC uses the RADIUS Tunnel Assignment ID value or its IP address or hostname during L2TP tunnel negotiations use the following command Command gt set 12tp id for host on off Setting id for host to on sets a LAC host to identify itself by its RADIUS Tunnel Assignment ID value Setting id for host to
36. internal digital modems and also the external modems that work with the PortMaster 4 To subscribe send email to majordomo livingston com with subscribe portmaster modems in the body of the message e 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 e 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 e tech bulletin livingston com a moderated push list featuring technical notes Web links and information about the latest code and beta releases sent on a weekly basis as well as periodic technical updates To subscribe complete the form at http www livingston com tech bulletin index html About This Addendum Subscribing to PortMaster Mailing Lists xii PortMaster 4 User Manual Addendum Installing and Working with the Redundant System Manager Module 1 This chapter provides the following in
37. ion on how to use these commands see the PortMaster 4 Configuration Guide the PortMaster Routing Guide and the PortMaster Troubleshooting Guide You can also configure the PortMaster 4 with the PMVision graphical user interface GUI for Microsoft Windows UNIX and other platforms supporting the Java Virtual Machine JVM Access PMVision online help for more information or see the PMVision User s Guide for additional information The See Also section in each command description refers to related commands in the PortMaster 4 Command Line Reference Redundant Manager Module Commands ComOS 4 2 introduces the following commands to configure and manage the redundant system manager module ComOS 4 2 also includes existing commands that have been modified to support the redundant manager module Chapter 1 Installing and Working with the Redundant Manager Module describes in detail how to use these commands to configure the redundant manager module for the PortMaster 4 3 1 Redundant Manager Module Commands peer copy peer This command copies a file between the system manager modules copy Subdirectory Filename source peer Subdirectory Filename destination Subdirectory Path to the file Filename source Name of the file to be copied Filenames and directory names cannot exceed 16 characters peer Manager module to copy the file to Filename Optional name to assign to the copied file in the new de
38. is appendix provides pinout and length information for the following cables used on the PortMaster 4 and specifications for cables used on PortMaster 4 Ethernet interfaces Modem Cable This cable is used to connect a data communication equipment DCE device modem to the CO or port See page 1 This cable is available from most computer equipment suppliers Console Cable Also known as a null modem cable this cable is used to connect a data terminal equipment DTE device terminal to the CO port See page A 2 This cable is available from most computer equipment suppliers RJ 45 Cable This cable is used to connect an Ethernet 10BaseT or 10 100BaseT line to an Ethernet port or to connect a Tl channelized T1 El channelized El or ISDN PRI line to a 1 or El port See page 2 Modem Cable Table A 1 gives pinout specifications for an RS 232 modem cable with RJ 45 and DB 25 connectors Table A 1 Modem Cable Pinouts PortMaster 4 Serial Port C1 PC or Terminal Serial Port RJ 45 Name Definition Direction nig Signal l RTS Request to Send Output 5 CTS 2 DTR Data Terminal Ready Output 8 DCD 3 TXD Transmit Data Output 3 RXD 4 GND Signal Ground NC 5 GND Signal Ground 7 GND 6 RXD Receive Data Input 2 TXD 7 DCD Data Carrier Detect Input 20 DTR 8 CTS Clear to Send Input 4 RTS NC Data Set Ready 6 DSR K Pins 8 and 6 in the DB 25 connectors are connected internally Not co
39. istance for any injured person Warning To avoid damaging the internal components of the PortMaster 4 follow antistatic precautions by wearing a grounding wrist strap Grounding Wrist Strap Instructions 1 4 When working with the internal components of the PortMaster 4 you must wear a grounding wrist strap Grounding wrist straps can be attached either at the front of the chassis behind the power bay door or at the back of chassis in the lower right and left corners Figure 1 2 shows the proper place to attach a grounding wrist strap at the front of the chassis Figure 1 2 Grounding Strap Attachment Front Panel grounding strap attachment 1406_0004 Figure 1 3 shows the proper places to attach a grounding wrist strap at the back of the chassis PortMaster 4 User Manual Addendum Installing a Redundant System Manager Module Figure 1 3 Grounding Strap Attachments Rear Panel om gt lt al OVDC A JUMPER OVDC B 48VDCB JUMPER 48 Oo Oo oO POWER O ALARM grounding strap attachments ae Installing a Redundant System Manager Module Procedure Follow these instructions to install the redundant manager module 1 Line up the edge of the module with the card guide
40. led SNMP alarm The primary does not check for the secondary s heartbeat If you receive these failure alarms on both manager modules wait and monitor the problem for several minutes If the problem persists for more than a minute or two reboot the secondary manager module from the secondary s console If the reboot fails to correct the problem turn power to the PortMaster 4 off and on If the manager modules are still not communicating reseat the secondary manager module by pulling it out and reinserting it into the slot See Safety Precautions on page 1 4 and Grounding Wrist Strap Instructions on page 1 4 before proceeding If reseating the secondary manager fails to correct the problem reseat the primary manager module If the communication problem persists contact Lucent NetCare technical support Replacing a Failed Manager Module Redundant manager modules are shipped with ComOS 4 2 installed When the active system manager module fails the secondary manager takes over as the primary manager To hot swap the failed manager module with a new one follow this procedure 1 Make sure that you have the proper hardware and software and take the proper safety precautions See Installation and Configuration Requirements on page 1 3 for instructions Disconnect lines to the failed manager module Open the top and bottom tabs on the failed manager module and remove it from the slot in the Port
41. mand Note Use the save all command to copy the current system configuration to the by secondary manager module before resetting it slotSlotnumber Resets a board in the specified slot physical or virtual Usage ComOS 4 2 supports the enhanced reset command to support the secondary manager module using the secondary keyword Entering reset slotSlotnumber from the secondary manager using the slot number of the primary manger is the only way to reboot the primary manager from the secondary For additional information about the reset command see the PortMaster 4 Command Line Reference No output is generated from this command See Also reset 3 4 PortMaster 4 User Manual Addendum Redundant Manager Module Commands save peer also local only save peer also local only This command saves configuration information to the nonvolatile memory of the primary manager module or of both the primary and secondary manager modules save Keyword local only peer also Keyword all global console filter host location netmask ports route snmp user ospf bgp For a complete description of these keywords see the PortMaster 4 Command Line Reference local only Saves to the nonvolatile memory of the manager module from which you enter the command peer also Saves to nonvolatile memory of both the primary and secondary manager modules This is the default The save peer also command cannot be issued from the secondary
42. nnected Console Cable Lucent recommends that the length of an RS 232 null modem cable does not exceed 50 feet 15 meters Console Cable Table A 2 gives pinout information for an RS 232 console null modem cable with RJ 45 and DB 25 connectors Table A 2 Console Cable Pinouts PortMaster 4 External Serial Port C1 Modem DB 25 RJ 45 Name Definition Direction DCE 1 RTS Request to Send Output 4 2 DTR Data Terminal Ready Output 20 3 TXD Transmit Data Output 2 4 GND Signal Ground NC 5 GND Signal Ground 7 6 RXD Receive Data Input 3 7 DCD Data Carrier Detect Input 8 8 CTS Clear to Send Input 5 _ Not connected Lucent recommends that the length of an RS 232 straight through console cable does not exceed 50 feet 15 meters RJ 45 Cable Table A 3 shows the pinout specifications for a Category 5 twisted pair cable as specified by the ANSI EIA 568 A wiring standard with an RJ 45 connector also known as RJ 48C connector Table 3 RJ 45 Cable Pinouts PortMaster 4 Ethernet 1 and El RJ 45 Ports Direction to or from the RJ 45 Signal Definition PortMaster 4 1 RXD Ring Receive Data Input 2 RXD Tip 4 TXD Ring Transmit Data Output 5 TXD Tip A 2 PortMaster 4 User Manual Addendum Ethernet Cable Specifications See Ethernet Cable Specifications on page A 3 for more information Ethernet Cable Specifications Table A 4 provides ca
43. number of times set with this command If no acknowledgment is sent from the primary accounting server in response to the last retry packet the PortMaster sends the packet to both the primary and alternate RADIUS accounting servers If an acknowledgment is received from the RADIUS accounting server the PortMaster no longer tries to resend the accounting packet To view the accounting count setting use the show global command Example Command gt set accounting count 45 Accounting retry count changed from 23 to 45 See Also set accounting interval page 3 9 set accounting interval This command sets the interval between accounting packet retransmissions to a RADIUS accounting server set accounting interval Seconds Seconds Number of seconds that elapse between RADIUS accounting packet retransmissions that are not acknowledged by an accounting server Integer between 1 and 255 The default is 30 seconds ComOS 4 2 Commands 3 9 RADIUS Commands set authentication failover 3 10 Usage When the PortMaster attempts to send a RADIUS accounting packet to the RADIUS accounting server and it does not receive an acknowledgment it retransmits the packet the number of times set with the set accounting count command Use the set accounting interval command to set the time interval between attempts to resend the RADIUS accounting packet If no acknowledgment is sent from the primary accounting server in response to the last
44. odule or on both the primary and secondary manager modules tftp get Ipaddress Filename 1 1 1 1 Ipaddress IP address of the TFIP server Filename Name of a file peer also Saves a file to the nonvolatile RAM on both the primary and secondary manager modules local only Saves a file to the nonvolatile RAM on the manager module from which you enter the command Usage ComOS 4 2 supports this modified tftp command to enable a system manager on the PortMaster 4 to save a file to the other manager module in addition to its own nonvolatile RAM RADIUS Commands 4 2 introduces the following RADIUS commands to configure the PortMaster 4 to use a RADIUS server For a complete list of RADIUS commands see Chapter 3 of the PortMaster 4 Command Line Reference set accounting count This command sets the number of times the PortMaster attempts to send a RADIUS accounting packet to a RADIUS accounting server 3 8 PortMaster 4 User Manual Addendum RADIUS Commands set accounting interval set accounting count Number Number Number of times the PortMaster attempts to send a RADIUS accounting packet to a RADIUS accounting server if it does not receive an acknowledgment from the server Integer between 1 and 99 The default is 5 Usage When the PortMaster attempts to send a RADIUS accounting packet to the RADIUS accounting server and it does not receive an acknowledgment it retransmits the packet the
45. of the PortMaster 4 Installation Guide Contact Lucent NetCare technical support if power is not present on the DC version Contact Lucent NetCare technical support Contact Lucent NetCare technical support If no boot server is available verify that DIP switch 2 is turned to the right and reboot otherwise see the network booting procedure in the PortMaster Troubleshooting Guide If nonvolatile RAM contents are corrupt follow the PortMaster Troubleshooting Guide procedure for network booting and rewriting the contents of nonvolatile RAM Installing and Working with the Redundant System Manager Module 1 21 Troubleshooting a Redundant System Manager Module Table 1 3 Hardware Problems and Solutions on the Manager Module Continued LED Behavior Possible Cause Explanation or Possible Solution Immediately after booting the DIAG LED on the manager module stays solidly lit or does not light This behavior does not refer to the boot sequence during which the DIAG LED is not lit for between 5 and 7 seconds During operation the DIAG LED on the manager module stays solidly lit or does not light No console login prompt is displayed Link green LED on an Ethernet interface is not lit when connected to an Ethernet hub Network amber LED on an Ethernet interface is solidly lit A component might have loosened during shipping A hardware problem might have been caus
46. off sets a LAC host to use its hostname or IP address during tunnel negotiations This is the default New L2TP Bearer Type Attribute The Bearer Type L2TP attribute identifies the type of calling device used in an L2TP connection as analog or digital The LAC sends this information to its L2TP peer the LNS The LNS then passes the information to the RADIUS accounting server in the NAS Port Type attribute New RADIUS Tunnel Attributes for L2TP The RADIUS Attributes for Tunnel Protocol Support Internet draft defines a set of RADIUS attributes to implement compulsory tunneling To provide this functionality ComOS 4 2 supports the following new RADIUS tunnel attributes for L2TP with Lucent RADIUS 2 1 or a RADIUS server with equivalent functionality e Tunnel Client Endpoint this attribute contains the address of the initiating end of the L2TP tunnel the LAC This attribute can be used to provide a globally unique way to identify a tunnel for accounting and auditing uses e Tunnel Password this attribute supports an encrypted password between a RADIUS server and a LAC e Tunnel Assignment ID this attribute enables RADIUS to inform the tunnel initiator the LAC about how to assign the session to a multiplexed tunnel or to a separate tunnel 2 1 New RADIUS Tunnel Attributes for L2TP e Tunnel Preference this attribute indicates the relative preference assigned to each tunnel if more than one set of tunneling attributes is ret
47. onsole 1 3 1 8 Ethernet 10 100BaseT 1 2 Ethernet 10BaseT 1 3 R RADIUS 1 10 accounting packets 3 8 authentication failover 3 10 interval between accounting packet transmissions 3 9 RADIUS commands 3 8 RADIUS L2TP attributes bearer type 2 1 tags 2 2 Tunnel Assignment ID 2 1 Tunnel Client Endpoint 2 1 Tunnel Password 2 1 Tunnel Preference 2 2 rebooting manager modules 3 3 reboot me command 1 17 3 3 reboot secondary command 1 25 3 3 reboot system command 1 17 3 3 redundant manager module displaying 3 7 rebooting 3 3 saving 3 5 redundant manager module commands 3 1 redundant system manager module compatibality 1 3 described 1 1 Index 2 installing 1 5 upgrading 1 25 rename command 3 4 reporting IP address LAC hosts 3 12 reset console command 1 18 reset secondary command 1 17 3 4 reset slot command 1 18 3 4 resetting secondary manager module 3 4 RJ 45 connector cable specifications A 2 Ethernet 10 100BaseT port 1 11 Ethernet 10BaseT port 1 13 pinout specifications A 2 S save all command 1 16 1 25 1 26 save local only command 3 5 save peer also command 1 16 3 5 saving 3 5 to nonvolatile RAM 3 8 to the peer server 3 8 set accounting count command 3 9 set accounting interval command 3 9 set altname command 3 5 set authentication failover command 3 10 set authentication interval command 3 11 set chapname command 3 13 set console command 1 18 set debug command 1 18 set debug m2m command 1 18 3 6 set et
48. p to 39 characters that the PortMaster 4 uses to identify itself during CHAP negotiations Usage This command enables multiple PortMaster 4 units to act like one system for CHAP operations if you set the same CHAP name on all of them Example No output is generated from this command Command gt set chapname buildingl SS7 Commands 4 2 introduces the following commands used to configure Signaling System 7 SS7 on the PortMaster 4 For a description of other commands related to SS7 configuration see Chapter 15 of the PortMaster 4 Command Line Reference set imt reject cause The command sets the cause code used when incoming calls are rejected by RADIUS when call checking is enabled for SS7 set imt reject cause Cause code Cause_code Value of the reject code an integer between 1 and 63 The default value is 1 Usage To use this command you must first select a slot for configuration using the set view command ComOS 4 2 Commands 3 13 SS7 Commands set set imt alt Use this command for telecommunications service providers that require a specific action to be taken when a RADIUS rejection occurs Example Command gt set view slot 3 Command 3 gt set imt reject code 63 Changed RADIUS reject code from 1 to 63 imt alt This command sets one or more alternate SS7 gateways for the line boards of the PortMaster 4 set imt alt 1 2 3 Ipaddress 1 First alternate gateway 2 Second alternate gateway
49. played If a softboot and crash occurred the last process is displayed Example In the following example the software version is ComOS 4 2b6 The register values are displayed after Regs Command gt show bootlog 000 00 01 21 65 SlotO Crash Boot 0 19 pm4gt10S 4 2b6 Crash type 3 Last Proc 0 0 IP 0x167768 Regs 00167760 001 7120 00245488 00000000 00210068 001 7154 00000000 00210D4C 1 4 7 8 216 1 7154 0 0 31 206 0 167768 245488 210d94 1e7120 1e7154 0 210dac 15b90b 2 15b4a2 245488 12418 ffff000 0 0 0 0 0 15b8dc 2 1fff28 800 210ddc 210448 12df8 ffff000 1 11 15 lbee 14e574 202498 0 0000 lled5d 1022b9 lbee 0 40 ffff000 ff540 ffff000 a 10272f 0000000 0 Press Return for More 10f0f4 0000000 0 fflel 0000000 0 0000000 0 show smm backup This command displays information about the primary and secondary manager modules if a redundant manager module is installed and operating in the PortMaster 4 show smm backup ComOS 4 2 Commands 3 7 RADIUS Commands tftp get peer also local only Example Command Secondary gt show smm backup System Manager Module Backup Information for slot 4 My state Secondary My protocol version 1 0 Peer state Primary Peer protocol version 1 0 Peer Management Address 149 198 32 171 Time since last hello 0 8 seconds tftp get peer also local only This command retrieves a file and saves to the nonvolatile memory on one system manager m
50. r Network Management of TCP IP based Internets MIB IT 1700 Assigned Numbers RFC 2138 Remote Authentication Dial In User Service RADIUS RFC 2139 RADIUS Accounting 2400 Internet Official Protocol Standards Document Conventions The following conventions are used in this addendum Convention Use Examples Bold font Indicates a user Enter version to display the version entry a number command menu option button or key or the name of a file directory or utility except in code samples e Press Enter Open the permit list file Vili PortMaster 4 User Manual Addendum Document Advisories Convention Use Examples Italic font Identifies a e set EtherO address Ipaddress command line placeholder Replace Area with the name of the Replace with a OSPF area real name or value Square brackets Enclose optional set nameserver 2 Ipaddress keywords and valuesig e set 50 destination Ipaddress command syntax Ipmask Curly braces Enclose a set syslog Logtype disabled required choice Facility Priority between keywords and or values in command syntax Vertical bar 1 Separates two or e set SO WI ospf on off more possible options in set SO host command syntax default prompt Ipaddress Document Advisories AN N Note means take note Notes contain information of importance or special interest Caution
51. rence when operated in a commercial environment Operation of this equipment in a residential area is likely to cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference Some components may not have been manufactured by Lucent Technologies If not Lucent Technologies has been advised by the manufacturer that the component has been tested and complies with the Class A computing device limits as described above IC CS03 Notice Canada The Industry Canada label identifies certified equipment This certification means that the equipment meets certain telecommunications network protective operational and safety requirements The Department does not guarantee the equipment will operate to the user s satisfaction Before installing this equipment users should ensure that it is permissible to be connected to the facilities of the local telecommunications company The equipment must also be installed using an acceptable method of connection In some cases the company s inside wiring associated with a single line individual service may be extended by means of a certified connector assembly telephone extension cord The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations Repairs to certified equipment should be made by an authorized Canadian maintenance facility designated by the
52. retry packet the PortMaster sends the packet to both the primary and alternate RADIUS accounting servers To view the accounting count and the accounting interval settings use the show global command Example Command gt set accounting interval 60 Accounting retry interval changed from 30 to 60 sec See Also set accounting count page 3 8 set authentication failover This command enables the PortMaster to dynamically switch primary and alternate RADIUS authentication servers based on their response to authentication requests set authentication failover on off on If the primary authentication server fails to respond to three consecutive requests the PortMaster sends seven requests to both the primary and secondary servers If the secondary server replies before the primary server it becomes the primary server off The PortMaster always tries the primary server first This is the default Usage This command enables the RADIUS authentication failover feature on the PortMaster When RADIUS authentication failover is enabled the PortMaster does the following 1 Sends three access request packets to the primary authentication server and awaits a response PortMaster 4 User Manual Addendum RADIUS Commands set authentication interval 2 Sends seven requests to both the primary and secondary authentication servers and awaits a response 3 If the secondary server responds first and failover is set to on designates
53. rtbeat from the primary it takes over and becomes primary 4 The new primary manager reboots the system All calls and network connections to the PortMaster are dropped and dynamic routing information is lost Heavy traffic on the primary manager can temporarily impede manager to manager communication This normal condition can create a failover like situation See Troubleshooting Communication between Manager Modules on page 1 24 for details Installing and Working with the Redundant System Manager Module 1 23 Handling System Manager Module Failure 1 24 Troubleshooting Communication between Manager Modules A burst of heavy traffic on the primary manager can cause temporary loss of communication over the 115Kb UART communications channel between the primary and the secondary manager modules This behavior can appear very much like a failover To troubleshoot the UART channel for possible failure follow this procedure 1 Check for the following two events which can indicate channel failure a The secondary manager does not detect a heartbeat from the primary and generates a Primary manager in slot 4 failed SNMP alarm If you can verify that the primary manager is functioning properly proceed to Step 5 If the secondary generates a Can t hear manager alarm proceed to Step 2 b The primary receives no communication from the secondary for 30 seconds and generates a Secondary manager in slot 5 fai
54. s The manager module in slot 5 determines slot 4 that the manager in slot 4 is still running because it can still detect a heartbeat Using PMVison 1 8 with a Redundant System Manager Module Note Be sure to use PMVision 1 8 on a PortMaster 4 with a redundant system manager module Earlier versions of PMVision and the older programs pminstall PMconsole and PMconsole for Microsoft Windows do not recognize the redundant system manager module feature and view each manager module in the PortMaster 4 as a separate system PMVision automatically handles both system manager modules transparently If you connect to a PortMaster 4 using the EtherO interface of the manager module in either slot 4 or slot 5 PMVision automatically contacts both managers and determines which is primary You can display information about both managers by selecting the Configure Boards option Figure 1 14 shows a display for a PortMaster 4 with a redundant manager module For more information about PMVision see the PMVision User s Guide Installing and Working with the Redundant System Manager Module 1 19 Troubleshooting a Redundant System Manager Module Figure 1 14 PMvVision Showing a Primary and Secondary Manager Device Model Comos 4 2b5 9912011209 PortMaster Configure Boards Device Board ID Board Type OS Version Serial Number Slot Manager Type Power PRI Switch Type 149 198 32 170 4 System Manager 4 2b5 9912011209 4 S
55. s installed 1 20 PortMaster 4 User Manual Addendum Troubleshooting a Redundant System Manager Module Table 1 3 Hardware Problems and Solutions on the Manager Module Continued LED Behavior Possible Cause Explanation or Possible Solution Green CO LED is flashing All LEDs fail to light Amber DIAG LED on the manager module does not light During startup the DIAG LED on the manager module fails to light stays lit or blinks three times per second continuously During startup the DIAG LED on the manager module blinks once per second for more than a minute Amber CO LED is flashing Manager module is booting and negotiating with the other manager to determine which is primary Peer to peer messages are traveling between manager modules Power is not present Board malfunction A hardware problem has occurred DIP switch 2 is turned to the left and no boot server is present Nonvolatile RAM contents are corrupt Normal behavior for a few seconds during bootup Persistent flashing indicates trouble in the communications path between the two manager modules See Troubleshooting Communication between Manager Modules on page 1 24 Normal behavior when a redundant manager module is installed Check the power switch power cable outlet and fuse For instructions on checking and changing the fuse in the AC version see Replacing a Fuse on page 4 10
56. stallation configuration troubleshooting and maintenance information for the redundant system manager module RSMM on the PortMaster 4 e Redundant System Manager Module Description on page 1 1 e Installation and Configuration Requirements on page 1 3 e Installing a Redundant System Manager Module on page 1 5 e Connecting a Console on page 1 7 e Optional Connecting an External Modem on page 1 9 e Connecting an Ethernet Cable on page 1 10 e Configuring a Redundant System Manager Module on page 1 15 e Primary Manager Module Selection at Startup on page 1 18 e SNMP Alarms Supporting Redundancy on page 1 18 e Using PMVison 1 8 with a Redundant System Manager Module on page 1 19 e Troubleshooting a Redundant System Manager Module on page 1 20 e Handling System Manager Module Failure on page 1 23 Redundant System Manager Module Description You can install a redundant system manager module in the PortMaster 4 chassis to provide system manager backup The manager modules must be installed in slots 4 and 5 and must be physically identical to each other One usually the module in slot 4 functions as the primary manager and the backup module is called the secondary manager Overview of Redundant Manager Operation By installing a redundant system manager module you can prevent PortMaster 4 downtime due to manager module failure With two manager modules installed
57. stination directory If no name is specified the PortMaster assigns the original filename Leave no space between peer and the path to the file and filename Usage ComOS 4 2 supports an enhanced copy command that allows a specific file to be copied from one manager module to another manager module using the peer keyword Each manager module has is own file system Use the show files command before and after using the copy command See the copy command description in the PortMaster 4 Command Line Reference for additional information Example Command gt copy shared m2c_ 2 4 peer Queued transfer of shared m2c_2 4 to shared m2c_2 4 on peer Starting transfer of shared m2c_2 4 to shared m2c_2 4 on peer Transfer complete 74204 bytes copied to shared m2c 2 4 on peer See Also copy 3 2 PortMaster 4 User Manual Addendum Redundant Manager Module Commands reboot me system secondary reboot secondary This command restarts the software on module of the PortMaster 4 or on the entire PortMaster 4 using the currently saved configuration reboot secondary Reboots the manager module receiving the command Caution Using the reboot me command on the primary manager module drops all calls and shifts primary responsibility to the secondary manager module system Reboots the entire PortMaster 4 when issued from either manager module secondary Reboots the se
58. t show smm backup Command gt set altname Hostname primary manager copies the system configuration to the secondary manager Using local only saves configuration information to the manager module you enter it from From the primary manager only peer also saves to both modules You cannot use this keyword from the secondary manager module This command activates the secondary manager module on the LAN This command downloads ComOS from the local server and saves it to nonvolatile memory on the secondary manager module With two managers the PortMaster 4 has two separate file systems Use the copy peer command to copy an executable file from the primary to the secondary manager For example copy shared quadt1 peer This command displays information about the primary and secondary manager modules This command sets the prompt for the manager module in slot 5 PortMaster 4 User Manual Addendum Configuring a Redundant System Manager Module Table 1 1 Redundant Manager Module Configuration Commands Continued Action Command Syntax Event Reboot the Command gt reboot system This command reboots the entire PortMaster 4 Reboot the secondary manager Reboot the current manager module Reboot the secondary manager Command gt reboot secondary Command gt reboot me Command Secondary gt reset secondary system You can enter this command from either manager This is
59. t is illuminated when the manager module is the primary manager and not illuminated when it is the secondary manager The green LED on the CO port blinks when the manager module has not yet determined if it is the primary or secondary manager The amber LED on the port is illuminated when it receives a message from the other manager module Cl port for an asynchronous connection to an external modem EtherO interface 10BaseT Ethernet interface for a private LAN connection DIP switch 1 bottom and 2 top to set CO function and the boot mode of the manager card Ether interface 10 100BaseT Ethernet interface for an upstream Ethernet connection Media independent interface MII connection alternative Etherl interface that accepts optional adapters for connection to copper or optical media DIAG LED lights when the module is booting and blinks off every 5 seconds during normal operation PWR LED remains solidly lit when the module is receiving power during normal operation PortMaster 4 User Manual Addendum Installation and Configuration Requirements Figure 1 1 System Manager Module gt CK L co C1 Bez EtherO 10BaseT DIP switches Ether1 10 100BaseT MII Interface to 10 100BaseT alternative Ether1 H DIAG LED PWR LED 1406_0007 Installation and Configuration Requirements To install and configur
60. terface A 3 modem cable A 1 RJ 45 2 cause codes for SS7 RADIUS rejections 3 13 Challenge Handshake Authentication Protocol 3 13 CHAP setting system name 3 13 ChoiceNet 1 10 console cable pinout specifications A 1 console port connecting a console 1 7 copying files 3 2 copy peer command 3 2 D debugging manager modules 3 6 reboot information 3 6 DIP switches 1 6 displaying secondary manager module information 3 7 downloading ComOS using PMVision 1 20 using tftp get 1 26 E erasing boot log 3 7 EtherO 1 13 Etherl 1 11 Ethernet cable connecting 10 100BaseT 1 11 10BaseT 1 13 specifications A 3 Ethernet connections 1 10 Ethernet interface specifications A 3 external modem 1 9 F failover enabling 3 10 G global commands 3 13 grounding wrist strap instructions 1 4 L L2TP command 3 12 LAC host identification during L2TP negotiations 3 12 M manager module debugging 3 6 installing 1 2 rebooting 3 3 sharing files 3 2 troubleshooting 1 20 media independent interface See MII connecting 1 11 description 1 2 Index 1 Index location 1 3 modem connecting to external modem 1 9 modem cable A 2 N NEBS Ethernet cable A 3 netboot preparing for 1 25 network connections Ethernet 10 100BaseT 1 11 Ethernet 10BaseT 1 13 MII 1 11 pinout specifications 1 PMVision upgrading ComOS with 1 26 using with redundant manager 1 19 port location asynchronous 1 6 c
61. terfaces When you install a redundant system manager module in a fully configured functioning PortMaster 4 you need to configure only the Ether0 interface on the redundant manager The redundant manager inherits its Etherl interface IP address from the Etherl interface of the primary manager during failover The IP address you assign to the EtherO interface on the redundant manager can be in the same subnet as the EtherO address on the primary manager but EtherO addresses for either manager module must be in a different subnet than the address of the 1 interface See Chapter 4 Configuring an Ethernet Interface in the PortMaster 4 Configuration Guide for a complete discussion of Ethernet interfaces Use the following procedure to assign an IP address to the redundant manager and activate the configuration 1 Connect to the secondary manager in slot 5 via the console port and use the following command to assign an IP address and netmask Command Secondary gt set EtherO address Ipaddress NM Ipmask To communicate with the redundant module on the network you must assign it an IP address 2 Enter the following commands to activate the configuration Command Secondary gt save all Command Secondary gt reboot secondary The save all command entered on the redundant manager saves the configuration to nonvolatile memory on the secondary manager When using a redundant manager entering the save all command on
62. the highest level reboot command This command reboots the secondary manager module and can be entered from either module Rebooting the secondary manager does not affect the current operating parameters of the system It just ensures that the secondary manager is running the current code and that its configuration is up to date If you enter this command on the primary manager it disconnects all calls and shifts the primary responsibility to the secondary If you enter this command on the secondary it reboots the secondary and has no effect on current PortMaster 4 operation To better understand the reboot commands note the defaults Entering reboot without an argument from the primary manager reboots the entire system just like the reboot system command Entering reboot without an argument from the secondary manager reboots only the secondary This command is an alternative way to reboot the secondary manager It has the same effect as the reboot secondary command Installing and Working with the Redundant System Manager Module 1 17 Primary Manager Module Selection at Startup Table 1 1 Redundant Manager Module Configuration Commands Continued Action Command Syntax Event connection between the primary and secondary manager modules Reboot the primary Command Secondary gt reset from the secondary slotSlotnumber Debug the Command gt set console Command gt set de
63. turned to the right the PortMaster 4 can boot normally Procedures for netbooting are located at http www livingston com tech technotes Scroll to PortMaster Troubleshooting click Netboot Procedures then select the procedure for your platform Figure 1 5 shows the location of the DIP switches on the manager module 1 6 PortMaster 4 User Manual Addendum Connecting a Console Figure 1 5 DIP Switches a H E R 0 0 switch 2 O 03 switch 1 10 100 Olt H E FA R 11 1406_0008 Connecting a Console Because the console port is your primary connection to the manager module Lucent strongly recommends that you connect a PC or terminal to the console port on both the primary and secondary manager modules Follow these instructions to connect a PC or terminal to a PortMaster 4 manager module for use as a console You can use the console connection on each manager module to configure and manage the PortMaster 4 Required Equipment I If you are using a a RJ 45 to DB 25 console cable with a 25 to 9 pin female adapter See Console Cable on page A 2 for more information I PC or terminal Procedure 1 Remove the cover from the cable guide if necessary 2 Run the end of the cable with the RJ 45 connector through the cable guide duct until it is directly over the manager module 3 Pull the end of the cable with the RJ 45 connector through the fingers o
64. urned by the RADIUS server For example if two different tunnel end points are included in the RADIUS attributes the tunnel end point with the lowest value specified in the value field is given preference If these attributes are not already in your RADIUS dictionary add them as follows ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE Tunnel Client Endpoint Tunnel Password Tunnel Assignment ID Tunnel Preference RADIUS Tunnel Attribute Tags 2 2 66 69 82 83 string string string integer In versions of RADIUS that support this feature you can now tag all RADIUS tunnel attributes so that ComOS can manage redundant tunnels more easily The tag field can assign the same ID to each attribute for a particular tunnel server end point to group the attributes and identify the tunnel more clearly Note Lucent RADIUS 2 1 does not currently support the tagging feature PortMaster 4 User Manual Addendum ComOS 4 2 Commands 3 This chapter describes the commands introduced ComOS 4 2 for the PortMaster 4 Command descriptions appear in the following sections e Redundant Manager Module Commands on page 3 1 e RADIUS Commands page 3 8 e L2TP Command on page 3 12 e Global Command on page 3 13 557 Commands on page 3 13 The complete set of commands used to configure monitor and debug the PortMaster 4 is described in the PortMaster 4 Command Line Reference For detailed informat

PortMaster® 4 User Manual Addendum

Contents

Download Pdf Manuals

Related Search

Related Contents

PortMaster&reg; 4 User Manual Addendum

Contents

Download Pdf Manuals

Related Search

Related Contents

PortMaster® 4 User Manual Addendum