Lucent MAX 6000, MAX, MAX 800, MAX 3000 Administration Manual

Download

MAX

™

Administration Guide

Part number 7820-0678-002

For software version 9.0

January 2001

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), exce pt in accordance with applicable agreeme nts, contracts, or lic ensing, without the express written consent of Lucent Technologies. For permission to reproduce or distri bute, please email yo ur request to techpubs@ascend.com.

Notice

Every effort was made to ensure that the information in this document was complete and accurate at the time of printing, but information is subject to change.

Safety, Compliance, and Warranty Information

Before handling any Lucent Acc ess Networks hard ware produc t, read the E dge Access Saf ety and Comp liance Gui de i nclu ded i n your p rodu ct p acka ge. See that guide also to de term in e how prod ucts c omp ly wi th t he el ec trom agne tic int erfer en ce (E MI) and ne tw ork co mp atib il ity r equ irem e nts of y our count ry. See the warranty card incl uded in your product packa ge for the limited warranty tha t Lucent Technologies provides for its produ ct s.

Security Statement

In rare instances, unauthorized individuals ma ke connections to the telecommunications ne twork through the use of acce ss features.

Trademarks

4ESS, 5ESS, A Network of Expertise, AnyMedia, APX 8000, AqueView, AUDIX, B-STDX 8000, B-STDX 9000, ...Beyond Compare, CaseView, Cajun, CajunDocs, CAJUNVIEW, Callma ster, CallVisor, CBX 500, CellPipe, ChoiceNet, ClearReach, ComOS, cvMAX, DACScan, Dacsmate, Datakit, DEFINITY, Definity One, DSLMAX, DSLTerminator, DSLPipe, DSLTNT, Elemedia, Elemedia Enhanced, EMMI, End to EndSolutions, EPAC, eSight, ESS, EVEREST, Gigabit-scaled campus networking, Globalview, GRF, GX 250, GX 550, HyperPATH, Inferno, InfernoSpaces, Intragy, IntragyAccess, IntragyCentral, Intuity, IP Navigator, IPWorX, LineReach, LinkReach, MAX, MAXENT, MAX TNT, Multiband, Multiband PLUS, Multiband RPM, MultiDSL, MultiVoice, MultiVPN, Navis, NavisAccess, NavisConnect, NavisCore, NavisRadius, NavisXtend, NetCare, NetLight, NetPartner, OneVision, Open Systems Innovations, OpenTrunk, P550, PacketStar, PathStar, Pinnacle, Pipeline, PMVision, PortMaster, SecureConnect, Selectools, Series56, SmoothConnect, Stinger, SYSTIMAX, True Access, WaveLAN, WaveMANAGER, WaveMODEM, WebXtend, and Where Network Solutions Never End are trademarks of Lucent Technologies Inc. Advanta ge Pak, Advantage Services, AnyMedi a, ...Beyond Compare, End to End Solutions, Inter.NetWorking, MAXENT, and NetWork Knowledge Solutions are service marks of Lucent Technologies Inc. Other trademarks, service marks, and trade names mentioned in this publication belong to their respective owners.

Copyrights for Third-Party Software Included in Lucent Access Networks Software Products

C++ Standard Template Library software copyright© 1994 Hewlett-Packard Company and copyright© 1997 Silicon Graphics. Permission to use, c opy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Neither Hewlet t-Packard nor Silicon Graphics makes any representations about the suitability of this software for any purpose. It is provided “as is” wit hout express or implied wa rra nt y.

Berkeley Software Distribution (BSD) UNIX software c opyright© 1982, 1986, 1988, 1993 The Regents of California. All rights reserved. Redistribution and use in source and binary form s, wit h or witho ut mod ific ation , are permitt ed prov ided t hat th e fol lowin g co nditi ons a re met: 1. Red ist ributions of source code must retain the abov e copyright notice, thi s li st of conditions, and the following disclaim er. 2. Redistri but ions in binary form must reproduce the abov e copyright notice, th is list of condition s, a nd the following di sclaimer in the doc umentation and/or other materials provided with the distribu tion. 3. All adverti sing materials mentionin g features or use of t hi s software must display the following acknowledgement: This prod uct includes software developed by th e University of California, Berk eley, and its contr ibutors. 4. Neit her th e name of th e Univ ersity nor the name s of its c ontrib utors ma y be used to endorse or pro mote products derived from this software without specific prior wri tt en perm i ssion.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INC LUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Ordering Information

Y ou can order the most up-to-date product information and computer-based training online at http://www.lucent.com/ins/bookstore.

Feedback

Lucent Technologies appreciates your comments, either positive or negative, about this manual. Please send them to techpubs@ascend.com.

Lucent Technologies

Customer Service

T o obtain pro duct and service information, software upgrades, and technical assistance, visit

the eSight™ Service Center at http://www.esight.com. The center is open 24 hours a day, seven days a week.

Finding information and software

The eSight Service Center at http://www.esight.com provides technical information, product information, and descriptions of available services. Log in and select a service. The eSight Service Center also provides software upgrades, release notes, an d adden da. Or you can visit the FTP site at ftp://ftp.ascend.com for this information.

Obtaining technical assistance

The eSight™ Service Center at http://www.esight.com provides access to technical support. You can obtain technical assistance through email or the Internet, or by telephone.

If you need to contact Lucent Technologies for assistance, make sure that you have the following information available:

• Active contract number, product name, model, and serial number

• Software version

• Software and hardware options

• If supplied by your carrier, service profile identifiers (SPIDs) associated with your line

• Your local telephone company’s switch type and operating mode, such as AT&T 5ESS Custom or Northern Telecom National ISDN-1

• Whether you are routing or bridging with your Lucent product

• Type of computer you are using

• Description of the problem

Obtaining assistance through email or the Internet

If your services agreement allows, you can communicate directly with a technical engineer through Email Technical Support or eSight Live chat. Select one of these sites when yo u log in to http://www.esight.com.

Calling the technical assistance center (TAC)

If you cannot find an an swer through the tools and in for mat io n o n eS i ght o r if you have a very urgent need, contact TAC. Access the eSight Service Center at http://www.esight.com and click Contact Us below the Lucent Technologies logo for a list of telephone numbers inside and outside the United States.

You can alternatively call (800) 272-3634 for a menu of Lucent services, or call (510) 769-6001 for an operator. If you do not have an active services agreement or contract, you will be charged for time and materials.

MAX Administration Guide iii

Customer Service ..................................................................................................................... iii

About This Guide............................................................................ xvii

What you should know ......................................................................................................... xvii

Documentation conventions .................................................................................................xviii

The MAX documentation set ..................................................................................................xix

Chapter 1 Administering MAX Hardware ....................................................... 1-1

Troubleshooting POST .......................................................................................................... 1-1

Interpreting indicator lights ....................................................................................................1-2

MAX 6000 ...................................................................................................................... 1-2

MAX 3000 ...................................................................................................................... 1-5

Troubleshooting the Fault indicator light .......................................................................1-7

MAX 800 ........................................................................................................................1-7

Troubleshooting the No Logical Link status ..........................................................................1-9

Troubleshooting the AIM port interface ................................................................................1-9

Testing the AIM port interface .....................................................................................1-10

Calls fail between AIM ports ........................................................................................1-10

Excessive data errors on calls to AIM ports ................................................................. 1-11

Troubleshooting a codec ......................................................................................................1-12

The codec indicates that there is no connection ........................................................... 1-12

The codec does not receive data ................................................................................... 1-12

The codec cannot establish a call ..................................................................................1-13

Calls initiated by control-lead toggling are cleared too soon .......................................1-13

The codec cannot clear a call ........................................................................................1-13

Troubleshooting cable issues ...............................................................................................1-14

Displaying interface statistics .............................................................................................. 1-14

Using modems to perform administrative tasks ...................................................................1-16

Booting from a FAT-formatted PCMCIA card ....................................................................1-17

Chapter 2 DO Commands and Administrative Tasks.................................... 2-1

Activating administrative permissions ...................................................................................2-1

Performing basic administration ............................................................................................ 2-3

Managing sessions ....................................... ....................................... ...... ......................2-3

Copying FXS profiles with the DO Commands ............................................................. 2-4

Managing calls .......................................................................................... ...... ................2-5

Testing and troubleshooting ...................................................................................................2-6

Using bit-error tests ........................................................................................................ 2-6

Using remote loopback ................................................................................................... 2-8

Using remote management ........................................................................................... 2-10

DO Command operations .............................................................................................2-11

MAX Administration Guide v

Contents

Chapter 3 Terminal-Server Administrative Tasks.......................................... 3-1

Enabling and configuring the interface ........................................... .......................................3-1

Configuring the interface ................................................................................................3-2

Configuring the Session Options profile ........................................................................3-3

Navigating to and from the interface ..................................................................................... 3-4

Testing the MAX unit ............................................................................................................ 3-4

Understanding test results ......................................................................................................3-6

Starting remote management sessions ................................................................................... 3-7

Disconnecting user Telnet connections ..................................................................................3-9

Using Set commands ..............................................................................................................3-9

Enable password mode ...........................................................................................................3-9

Using Show commands ........................................................................................................3-1 0

Displaying uptime and revision ........................................................................... ...... ...3-10

Displaying modem status .............................................................................................. 3-11

Displaying V.110 terminal adapter status .....................................................................3-12

Displaying call and user activity ................................................................................... 3-13

Displaying active sessions ............................................................................................3-13

Displaying Dialed Number Information Service activity ............................................. 3-15

Using the Show Filters command .................................................................................3-17

Displaying information related to virtual routing .........................................................3-21

Chapter 4 Changing System Software Versions ........................................... 4-1

Preparing to change system software ..................................................................................... 4-2

Enabling Field Service and Operations parameters ........................................................4-2

Staying with the same software build .............................................................................4-2

Alternative builds for a MAX 6000 unit ......................................................................... 4-2

Using TFTP to upgrade or downgrade ...................................................................................4-3

Creating redundant backup images for a MAX 6000 unit ..............................................4-3

Using TFTP to upgrade ...................................................................................................4-4

Using TFTP to downgrade ..............................................................................................4-5

Using the serial port to upgrade or downgrade ......................................................................4-6

Saving your current profiles ...........................................................................................4-6

Upgrading system software ............................................................................................4-7

After the upgrade .......................................................... ....................................... ...... .....4-8

Restoring correct RADIUS parameters ..................................................................................4-8

Notice of discontinuance of configurable RADIUS port and ID space .................................4-9

Chapter 5 Administering E1 and T1 Services................................................ 5-1

Troubleshooting a Red Alarm ................................................................................................5-2

Verifying enabled lines ................................................. ....................................... ...... .....5-2

Verifying Framing Mode settings ...................................................................................5-3

Resolving cabling issues ............................................... ....................................... ........... 5-3

Summary of Red Alarm causes and solutions ................................................................ 5-3

Troubleshooting a blinking Alarm .........................................................................................5-4

Integrated CSU for T1/PRI .............................................................................................5-4

Remedying D-channel issues ..........................................................................................5-5

Summary of blinking Alarm potential causes and possible solutions ............................5-7

Using Net/E1 and Net/T1 status windows .............................................................................5-7

Listing WAN interface features ......................................................................................5-7

Displaying errors ............................................................................................................. 5-8

vi MAX Administration Guide

Contents

Displaying link and channel status .................................................................................5-8

Displaying FDL statistics ..............................................................................................5-10

Fractional T1 services ......................................................... ..... .....................................5-12

Using line diagnostics ..........................................................................................................5-13

Clearing user error event and performance registers ....................................................5-13

Initiating a line loopback test ........................................................................................5-14

Swapping NFAS status .................................................................................................5-14

Testing the lines ............................................................................................................5-15

Remedying Trunk Down state .............................................................................................5-15

Using terminal-server commands ........................................................................................ 5-16

Resetting the unit and clearing calls ............................................................................. 5-16

Displaying the source of clocking ................................................................................5-16

Specifying channels for E1 and T1 ......................................................................................5-17

Verifying E1 and T1 parameter settings ..............................................................................5-17

E1-specific parameter settings ...................................................................................... 5-17

T1-specific parameter settings ...................................................................................... 5-18

Fractional T1-specific parameters ...................................... ..... .....................................5-19

T1/PRI-specific parameters .......................................................................................... 5-20

PBX-T1 specific parameters .........................................................................................5-21

Troubleshooting channels ....................................................................................................5-22

Chapter 6 Administering ISDN........................................................................ 6-1

Troubleshooting BRI interface problems ...............................................................................6-1

WAN calling errors in outbound Net/BRI calls ..............................................................6-1

Calls are not dialed or answered reliably ........................................................................6-2

The Net/BRI lines do not dial or answer calls ................................................................6-2

Displaying E1 ISDN call information ....................................................................................6-2

Displaying ISDN events .........................................................................................................6-3

Understanding ISDN cause codes .......................................................................................... 6-4

Chapter 7 Administering TCP/IP..................................................................... 7-1

Managing the Internet Protocol (IP) ...................................................................................... 7-2

IP-routing environment ...................................................................................................7-2

Displaying IP information ..............................................................................................7-2

Troubleshooting IP routing .............................................................................................7-3

Displaying IP route statistics ..........................................................................................7-7

Displaying IP statistics and addresses ............................................................................7-8

RIP updates and IP routes ...............................................................................................7-9

Displaying address pool status ......................................................................................7-10

Displaying DNS-related information ................................................................................... 7-10

Displaying the local DNS fallback table .......................................................................7-10

Editing the local DNS table .......................................................................................... 7-12

Displaying Multicast information ........................................................................................7-13

Displaying the multicast forwarding table ....................................................................7-13

Listing multicast clients ................................................................................................ 7-14

Displaying IP-multicast activity ...................................................................................7-15

Using VRouter-related terminal-server commands .............................................................7-15

Displaying UDP packet information ....................................................................................7-16

Managing the Address Resolution Protocol (ARP) .............................................................7-19

Displaying and clearing the ARP cache ............................................................................... 7-19

Managing the Internet Control Message Protocol (ICMP) .................................................. 7-20

MAX Administration Guide vii

Contents

Pinging remote IP hosts ................................................................................................7-21

Displaying ICMP information ......................................................................................7-22

Preventing ICMP security breaches .............................................................................. 7-22

Managing the Routing Information Protocol (RIP) .............................................................7-23

Verifying the transmission path to NetWare stations ................................................... 7-23

Displaying IPX packet statistics ................................................................................... 7-25

Displaying the IPX service table ..................................................................................7-25

Displaying the IPX routing table .................................................................................. 7-25

Managing the Open Shortest Path First (OSPF) protocol ....................................................7-26

Displaying OSPF information ......................................................................................7-26

Verifying OSPF-related parameter settings ..................................................................7-36

Working with the OSPF routing table ..........................................................................7-37

Multipath routing .......................................................................................................... 7-39

Third-party routing ....................................................................................................... 7-40

How OSPF adds RIP routes .......................................................................................... 7-40

Route preferences ......................................................................................................... 7-40

MD5 cryptographic authentication ..................................... ..... .....................................7-42

Enabling Finger support .............................................................................................. ...... ...7-42

Understanding the AppleTalk-routing environment ............................................................ 7-43

Chapter 8 Administering PAD, X.25, and Frame Relay ................................. 8-1

Administering X.25 ................................................................................................................8-1

Displaying information about X.25 ................................................................................ 8-2

X.25 clear cause codes .................................................................................................... 8-3

X.25 diagnostic field values ............................................................................................8-3

Administering PAD ................................................................................................................8-5

Displaying information about PAD sessions ..................................................................8-6

Verifying PAD-related settings .......................................... ..... ...... .................................8-6

Understanding PAD service signals ...............................................................................8-7

Administering Frame Relay ...................................................................................................8-8

Using the Set commands to configure Frame Relay ..............................................................8-9

Chapter 9 Using Traps to Monitor Performance............................................ 9-1

Establishing SNMP access security .......................................................................................9-1

Enabling SNMP Set commands ......................................................................................9-2

Setting community strings ..............................................................................................9-2

Setting up and enforcing address security ......................................................................9-2

Resetting the MAX and verifying reset ..........................................................................9-2

Specifying User-based security ......................................................................................9-3

Example of SNMP security configuration ......................................................................9-3

Using the SNMPv3 User-based Security Model ....................................................................9-4

Verifying Network Management is installed ...................................... ............................9-4

Required SNMP Options profile settings .......................................................................9-4

Required SNMPv3 USM Users profile settings .............................................................9-5

Using SNMP traps .................................................................................................................9-6

Understanding the SNMP trap parameters .....................................................................9-7

Example SNMP trap configuration .................................................................................9-7

Enable Traps profile settings ..........................................................................................9-8

Using OSPF-related SNMP traps .........................................................................................9-10

SNMP Trap profile settings ................................................ ..... .....................................9-10

Mod Config settings ...................................................................................................... 9-10

viii MAX Administration Guide

Contents

Enable Traps profile settings ........................................................................................9-11

Administering virtual interfaces ...................................................................................9-11

Administering nonvirtual interfaces .............................................................................9-12

Administering Link-State Advertisements ...................................................................9-13

Matching an OSPF trap to an SNMP trap ID in RFC 1850 ..........................................9-13

Alarm/Error and Security events ............................................................................ ..... ......... 9-14

Alarm/Error events ........................................................................ ..... ..........................9-14

Security events ..............................................................................................................9-15

Appendix A Understanding Syslog messages .................................................A-1

Verifying Syslog support ................................................................................. ...... ............... A-2

Understanding Message Log status window ......................................................................... A-2

Understanding Level 4 and Level 6 messages ...................................................................... A-3

Understanding Level 5 messages ..........................................................................................A-4

Gathering tunneling information ........................................................................................... A-4

Call ID values .................................................................................. ...... ................................A-5

ATMP-related disconnect codes ...........................................................................................A-5

Understanding disconnect codes and progress codes ........................................................... A-6

Disconnect codes and their meanings ...................................................................................A-7

Progress codes and their meanings ..................................................................................... A-10

Code combinations and their possible meanings ................................................................ A-12

Appendix B Diagnostic Parameters and Commands .......................................B-1

Using diagnostics-related VT100 commands ........................................................................B-1

Using administrator-only commands ..............................................................................B-1

Using BRI/LT-related commands ...................................................................................B-5

Using E1-related commands ...........................................................................................B-8

Using Host/Dual (Host/6) Port-related commands .........................................................B-9

Using Modem-related commands .................................................................................B-10

Using T1-related commands .........................................................................................B-12

Using diagnostics-related DO commands ............................................................................B-14

? .....................................................................................................................................B-14

ARPTable ......................................................................................................................B-15

Clocksource ..................................................................................................................B-16

Clr-History ....................................................................................................................B-17

CoreDump .....................................................................................................................B-17

Diag ...............................................................................................................................B-18

Diag ? ............................................................................................................................B-18

Diag AddrPool ..............................................................................................................B-20

Diag Callback ...............................................................................................................B-21

Diag IPXrip ...................................................................................................................B-21

Diag Modemdrv ............................................................................................................B-22

Diag Networki ...............................................................................................................B-25

Diag PPPFSM ...............................................................................................................B-25

Diag PPPIF ...................................................................................................................B-27

Diag PPTPData .............................................................................................................B-28

Diag RadAcct ................................................................................................................B-28

Diag RadIF ....................................................................................................................B-29

Diag Routmgr ...............................................................................................................B-30

Diag SNTP ....................................................................................................................B-30

Diag Telnet ...................................................................................................................B-31

MAX Administration Guide ix

Contents

Ether-Display ................................................................................................................B -31

Fatal-History .................................................................................................................B-32

FClear ............................................................................................................................B-36

FRestore ........................................................................................................................B-36

FSave ............................................................................................................................B-36

Heartbeat .......................................................................................................................B-36

Help ...............................................................................................................................B-37

Lanport Modem .................... ...... ........................................ ..... .....................................B-37

Lcstate ...........................................................................................................................B-38

MdbStr ..........................................................................................................................B-39

MDialout .......................................................................................................................B-40

ModemDiag ..................................................................................................................B-40

ModemDrvDump ..........................................................................................................B-42

NetRoute .......................................................................................................................B-42

NSLookup .....................................................................................................................B-42

NVRAMClear ...............................................................................................................B-43

PPPDump N ..................................................................................................................B-44

PPPInfo .........................................................................................................................B-44

PPTPCM .......................................................................................................................B-45

PPTPEC ........................................................................................................................B-45

PPTPSend .....................................................................................................................B-46

PRIDisplay ....................................................................................................................B-46

Quit ...............................................................................................................................B-47

RadStats ........................................................................................................................B-47

Reset ..............................................................................................................................B-48

Revision ........................................................................................................................B-48

T1coredisplay ................................................................................................................B-49

Tempdisplay ..................................................................................................................B-49

TLoadCode ...................................................................................................................B-49

TRestore ........................................................................................................................B-51

TSave ............................................................................................................................B-51

Update ...........................................................................................................................B-51

WANDisplay ................................................................................................................B-52

WANDSess ...................................................................................................................B-53

WANNext .....................................................................................................................B-53

WANOpening ...............................................................................................................B-54

WDDialout ....................................................................................................................B-54

Using diagnostics-related DO commands for the MAX 6000 unit’s PCMCIA card ...........B-54

FImageCopy ..................................................................................................................B-54

Fload .............................................................................................................................B-55

Format ...........................................................................................................................B-56

FVersionInfo .................................................................................................................B-56

Ls ..................................................................................................................................B-57

MkDir ............................................................................................................................B-57

Mv .................................................................................................................................B-57

Rm .................................................................................................................................B-58

TLoadCode ...................................................................................................................B-58

Understanding Diagnostic command output ........................................................................B-59

Breaking down the raw data .................................................................................................B-60

x MAX Administration Guide

Contents

Appendix C Machine Interface Format (MIF) .....................................................C-1

Accessing the interface ..........................................................................................................C-1

Using full and partial addresses .............................................................................................C-2

Using supported commands ...................................................................................................C-4

Understanding responses ................................................................................................C-4

Loading and saving entities ............................................................................................C-4

Getting an entity’s current value .....................................................................................C-5

Getting the address and value of the next entity .............................................................C-5

Modifying parameter values ...........................................................................................C-6

MIF traps and asynchronous reports ...............................................................................C-6

Understanding command-line basics .....................................................................................C-7

Modifying an entity in the edit area .......................................................................................C-8

Using supported types ..........................................................................................................C-10

Index...........................................................................................Index-1

MAX Administration Guide xi

Figures

Figure 1-1 MAX 6000 front panel....................................................................................... 1-2

Figure 1-2 Redundant MAX 6000 front panel.................................................................... 1-3

Figure 1-3 MAX 6000 back-panel indicator lights.............................................................. 1-4

Figure 1-4 MAX 3000 front panel....................................................................................... 1-5

Figure 1-5 MAX 3000 back-panel indicator lights.............................................................. 1-6

Figure 1-6 MAX 800 back panel......................................................................................... 1-9

Figure 7-1 Example IP-routed environment........................................................................ 7-2

Figure 7-2 Example AppleTalk-routed environment........................................................ 7-44

MAX Administration Guide Preliminary February 2, 2001 xiii

Tables

Table 1-1 MAX 6000 front-panel indicator lights............................................................. 1-2

Table 1-2 Redundant MAX 6000 front panel lights .......................................................... 1-3

Table 1-3 MAX 6000 back-panel indicator lights.............................................................. 1-4

Table 1-4 MAX 3000 front-panel indicator lights............................................................. 1-5

Table 1-5 MAX 3000 back-panel indicator lights.............................................................. 1-6

Table 1-6 MAX 800 front panel lights............................................................................... 1-7

Table 1-7 PCMCIA card-related indicator lights............................................................... 1-8

Table 1-8 Output of the Show If Stats command............................................................. 1-15

Table 1-9 Show If command output................................................................................. 1-16

Table 1-10 Summary of PCMCIA file management commands....................................... 1-19

Table 2-1 DO menu commands for activating administrative permissions....................... 2-2

Table 2-2 DO menu commands for session management.................................................. 2-4

Table 2-3 DO menu commands for call management........................................................ 2-6

Table 2-4 DO menu commands for testing and troubleshooting ..................................... 2-10

Table 3-1 TServ Options parameters.................................................................................. 3-2

Table 3-2 Session Options parameters............................................................................... 3-3

Table 3-3 Returning to the VT100 interface...................................................................... 3-4

Table 3-4 Output of Show Modems command................................................................ 3-12

Table 3-5 Show calls output............................................................................................. 3-13

Table 3-6 Show Users command output.......................................................................... 3-14

Table 3-7 DO menu commands for specific protocols..................................................... 3-17

Table 5-1 Red Alarm potential causes and solutions......................................................... 5-3

Table 5-2 Blinking Alarm potential causes and possible solutions ................................... 5-7

Table 5-3 Link-status indicators......................................................................................... 5-9

Table 5-4 Channel-status indicators................................................................................. 5-10

Table 5-5 FDL performance registers.............................................................................. 5-11

Table 5-6 Net/T1 diagnostic commands .......................................................................... 5-15

Table 5-7 E1 parameters and settings............................................................................... 5-18

Table 5-8 T1-specific parameters..................................................................................... 5-19

Table 5-9 Fractional T1-specific parameters.................................................................... 5-19

Table 5-10 T1-PRI-specific parameters............................................................................. 5-20

Table 5-11 PBX-T1 parameters and settings ..................................................................... 5-21

Table 6-1 ISDN cause codes.............................................................................................. 6-4

Table 6-2 ISDN cause codes for 1TR6 switch type........................................................... 6-7

Table 7-1 Traceroute command syntax elements............................................................... 7-3

Table 7-2 Time field responses and annotations................................................................ 7-4

Table 7-3 IP routing table fields and definitions ............................................................... 7-6

Table 7-4 Output of the Show Dnstab command............................................................. 7-11

Table 7-5 Output of the Show IGMP Groups command ................................................. 7-13

Table 7-6 Output of the Show IGMP Clients command.................................................. 7-14

Table 7-7 VRouter-related terminal-server commands.................................................... 7-15

Table 7-8 VRouter-related terminal-server commands.................................................... 7-16

Table 7-9 Show commands, specified protocols, and network-specific information...... 7-17

MAX Administration Guide xv

Tables

Table 7-10 T1 channel status indicators............................................................................. 7-18

Table 7-11 OSPF routing table........................................................................................... 7-38

Table 7-12 MD5 Cryptographic parameters ............................. ..... ...... .............................. 7-42

Table 8-1 Clear cause codes............................................................................................... 8-3

Table 8-2 X.25 diagnostic field values............................................................................... 8-3

Table 8-3 PAD-specific parameters................................................................................... 8-6

Table 8-4 PAD service signal messages............................................................................. 8-8

Table 8-5 Set commands.................................................................................................... 8-9

Table 9-1 SNMPv3-related parameters.............................................................................. 9-6

Table 9-2 Trap-related parameters..................................................................................... 9-8

Table 9-3 Virtual interface-related OSPF traps................................................................ 9-11

Table 9-4 Nonvirtual interface-related OSPF traps.......................................................... 9-12

Table 9-5 LSA-related OSPF Traps parameters............................................................... 9-13

Table A-1 Summary of Syslog settings ............................................................................. A-2

Table A-2 Level 4 and Level 6 syslog messages............................................................... A-3

Table A-3 Level 5 Syslog messages .................................................................................. A-4

Table C-1 Syntax element descriptions .............................................................................. C-2

Table C-2 Command-line processing ................................................................................. C-7

Table C-3 Line-editing conventions ................................................................................... C-8

xvi MAX Administration Guide

About This Guide

The MAX™ Administration Guide is intended to help you as you measure, maintain, administer , and troublesh oot the performance of MAX 6000, MAX 3000, and MAX 800 units. A reference to a specific MAX model always accompanies information that applies only to that model. For example, if a desc ript ion i ndicates MAX 6000 , then that information applies only to MAX 6000 units. If a description indicates MAX, then that information applies to the MAX 6000, MAX 3000, or MAX 800 unit that is configured to support the feature being described.

To assure continuing satisfactory performance of a MAX unit make use of its indicator lights, the VT100 interface, the terminal-server command-line interface (CLI), DO commands, SNMP, and the Syslog.

Warning:

instructions in the Edge Access Safety and Compliance Guide. For information specific to your

unit, see the “Safety-Related Electrical, Physical, and Environmental Information ” appendix in your unit’s hardware installation guide.

Navigation and usage of all the user interfaces are described in the Hardware Installation and Basic Configuration Guide for your unit. You will continue to apply that information as you

use this guide.

The flexibility of the True Access™ Operating System (TAOS) software and hardware architecture of the MAX base unit allows you to introduce services as you need them. The MAX offers flash memory, slot cards, and software upgradable protocol support. You can upgrade the features that the MAX unit supports by changing the version of TAOS software running on the unit. The flexiblity of the system software and hardware architecture also results in support for over 15 WAN protocols. The MAX also supports several virtual private networking, several modem, and several bandwidth management protocols. Although the flexibility of the unit’s TAOS software and hardware architecture can make the tasks quite complicated, this guide intends to help you discern how best to assure satisfactory performance. Use this guide to gather information abou t the perform ance of the MAX un it and to eliminate problems that you may discover.

Note: This manual describes the full set of features for MAX 6000, MAX 3000, and MAX 800 units. Some features might not be available with earlier versions or specialty loads of the software.

Before installing or operating your MAX unit, be su re to read the safety

What you should know

This guide is for the pers on who configu res and ma intains MAX un its. To configure a unit, you need to understand the following:

• Internet or telecommuting concepts

MAX Administration Guide xvii

About This Guide

Documentation conventions

• WAN concepts

• LAN concepts, if applicable

Documentation conventions

Following are all the special characters and typographical conventions used in this manual:

Convention Meaning

Monospace text Represents text that appears on your computer’s screen, or that could

appear on your computer’s screen.

Boldface monospace text

Italics Represent variable information. Do not enter the words themselves in

[ ] Square brackets indicate an optional argument you might add to a

| Separates command choices that are mutually exclusive. > Points to the next level in the path to a parameter or menu item. The

Key1-Key2 Represents a combination keystroke. To enter a combination

Press Enter Means press the Enter, or Return, key or its equivalent on your

Note:

Represents characters that you enter exactly as shown (unless the characters are also in enter the characters but are not specifically instructed to, they do not appear in boldface.

the command. Enter the information they represent. In ordinary text, italics are used for titles of publications, for some terms that would otherwise be in quotation marks, and to show emphasis.

command. To include such an argument, type only the information inside the brackets. Do not type the brackets unless they appear in boldface.

item that follows the angle bracket is one of the options that appear when you select the item that precedes the angle bracket.

keystroke, press the first key and hold it down while you press one or more other keys. Release all the keys at the same time. (For example, Ctrl-H means hold down the Control key and press the H key.)

computer. Introduces important additional information.

italics

—see Italics, below). If you could

Caution:

Warning:

xviii MAX Administration Guide

W arns that a failure to follow the recom mended procedure could result in loss of data or damage to equipment.

Warns that a failure to take appropriate safety precautions could result in physical injury.

Warns of danger of electric shock.

The MAX documentation set

The MAX documentation set is available on the Documentation Library CD-ROM included with your MAX unit. You can order additional copies of the documentation on CD-ROM or paper from the online bookstore or you can view the documentation online. Go to http://www.lucent.com/ins/doclibrary for more information about these options.

The MAX documentation set consists of the following manuals:

•The Edge Access Safety and Compliance Guide

•The MAX Administration Guide (This volume)

•The Hardware Installation and Basic Con figuration Guide for your MAX 6000, MAX 3000, or MAX 800 unit

•The

•The MAX Reference

•The MAX Security Supplement

•The TAOS Glossary

•The TAOS RADIUS Guide and Reference

Network Configuration Guid e for your MAX 6000, MAX 3000, or MAX 800 unit

About This Guide

The MAX documentation set

MAX Administration Guide xix

Administering MAX Hardware

Troubleshooting POST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Interpreting indicator lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Troubleshooting the No Logical Link status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Troubleshooting the AIM port interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Troubleshooting a codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Troubleshooting cable issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Displaying interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Using modems to perform administrative tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Booting from a FAT-formatted PCMCIA card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

From the moment you turn on the power and the MAX unit initiates a power-on self test (POST), you can gather information that allows you to troubleshoot the MAX. Once the MAX is running, you can interpret the indicator lights that the unit includes on its front panel and back-panel. These indicator lights, combined with performance indicators, can lead you to discover hardware and other issues such as problems with the configuration, the Ascend Inverse Multiplexing (AIM) port, related Codec devices, and cables.

For E1, T1, and BRI interface-related information see Chapter 5, “Administering E1 and T1 Services” and Chapter 6, “Administering ISDN.”

Troubleshooting POST

A Power-on self test (POST) is a diagnostic test the MAX unit performs when it first starts up or after it completes a system reset. During a POST, the unit checks system memory, configuration, installed cards, compression hardware, and T1 connections.

If the start-up display indicates a failure in any part of the POST, an internal hardware failure has occurred with the unit.

If no data is displayed on the VT100 interface, verify that the unit completes all of the power-on self tests. Proceed as follows:

1 Verify that the MAX unit and your terminal are set at the same speed. 2 Locate the indicator light labeled Fault. 3 Switch on the MAX unit.

MAX Administration Guide 1-1

Administering MAX Hardware

Interpreting indicator lights

The MAX 6000, MAX 3000, and MAX 800 series each have a unique set of front panel indicator and back-panel indicator lights that display information about modems, power (including redundant power), fault-tolerance, data-link, and Alarm events.

MAX 6000

The MAX 6000 unit’s front-panel indicator lights indicate the status of the system, the PRI interface, and the data transfer in active sessions. Figure 1-1 shows the location of the indicator lights on the front panel of a MAX 6000 unit.

Figure 1-1. MAX 6000 front panel

Table 1-1 describes each indicator light located on the front panel of a MAX 6000 unit.

Table 1-1. MAX 6000 front-panel indicator lights

Light Description

Power On when the MAX 6000 unit’s power is on. Fault On in one of two cases:

• Hardware self-test in progress.

• Hardware failure. When a hardware self-test is in progress, the indicator light stays on. If any

type of hardware failure occurs, the indicator light flashes. If the failure is isolated to an expansion card, the MAX 60 00 unit might continue to fu nction without the expansion card.

Data On when calls are active.

1-2 MAX Administration Guide

Administering MAX Hardware

Interpreting indicator lights

Table 1-1. MAX 6000 front-panel indicator lights (continued)

Light Description

Alarm On indicates a WAN alarm or a trunk out of service (during line loopback

diagnostics, for example). WAN alarms include Loss of Sync, Red Alarm, Yellow Alarm, and All Ones (or AIS).

For more information about the Alarm indicator light, see“T roubleshooting a Red Alarm” on page 5-2 and “Troubleshooting a blinking Alarm” on page 5-4.

The MAX 6000 unit’s front panel indicator lights convey i nformatio n about th e power su pplies and the status of the unit’s fans. Figure 1-2 shows the location of the indicator lights on the front panel of a Redundant MAX 6000 unit.

Figure 1-2. Redundant MAX 6000 front panel

Table 1-2describes each indicator light on the front panel of a Redundant MAX 6000 unit.

Table 1-2. Redundant MAX 6000 front panel lights

Light Description

Power On when the Redundant MAX power supply is on. A Fail On only if one or more of the voltages from side A of the power supply

has failed (+12, +5, +3.3, -12, -5.)

MAX Administration Guide 1-3

Administering MAX Hardware

Interpreting indicator lights

Table 1-2. Redundant MAX 6000 front panel lights (continued)

Light Description

B Fail On only if one or more of the voltages from side B of the power supply

Fan On when the fans are functioning properly (if +12 Vdc from either A or

For more information, see “Troubleshooting a Red Alarm” on page 5-2 and “Troubleshooting a blinking Alarm” on page 5-4.

The MAX 6000 unit’ s back-panel indicator lights convey information about network traf fic on the unit’s Ethernet interface, packet collisions on the Ethernet network, full duplex operation on the Ethernet network, 100BaseT (or 10BaseT) status, and the functional status of the Ethernet interface. Figure 1-3 shows the MAX 6000 back -panel ind icator lights, which d isplay the status of the Ethernet interface.

Figure 1-3. MAX 6000 back-panel indicator lights

has failed (+12,+5, +3.3, -12, -5).

B is good). This indicator light goes off in the event of a fan failure.

Table 1-3 describes the MAX 6000 unit’s Ethernet interface indicator lights.

Table 1-3. MAX 6000 back-panel indicator lights

Light Description

ACT (Activity) On when the MAX is detecting activity (network traffic) on its Ether-

net interface. COL (Collisions) On when the MAX detects packet collisions on the Ethernet. FDX On indicates full duplex on the Ethernet. 100BT On indicates 100BaseT operation. Off indicates 10BaseT operation. LINK (Link integ-

rity)

1-4 MAX Administration Guide

On when the Ethernet interface is functional.

MAX 3000

Administering MAX Hardware

Interpreting indicator lights

The MAX 3000 unit’s front panel indicator lights indicate the power, status of the system self-tests, activity on the unit’s Ethernet interface, and Alarm events. Figure 1-4 shows the location of the indicator lights on the front panel of a MAX 30 00 unit.

Figure 1-4. MAX 3000 front panel

Table 1-4 describes each indicator light on the front panel of a MAX 3000 unit.

Table 1-4. MAX 3000 front-panel indicator lights

Light Description

Power On (green) when the MAX power is on. Fault On (yellow) in one of two cases:

• Hardware self-test is in progress.

• Hardware failure. When a hardware self-test is in progress, the light is on. If

any type of hardware failure occurs, the light flashes. If the failure is isolated to an expansion card, the MAX may continue functioning without the expansion card.

Data On (green) at power-up and thereafter if calls are active on

the Ethernet interface.

MAX Administration Guide 1-5

Administering MAX Hardware

LAN UTP

LNK COL

DPLX

100BT

WAN 1

Interpreting indicator lights

Table 1-4. MAX 3000 front-panel indicator lights (continued)

Light Description

Alarm On (amber) at power-up. Thereafter, on indicates a WAN

The MAX 3000 unit’s back-panel indicator lights convey information about the 10 Mbps operation, 100 Mpbs operation, transmitter activity, Full Duplex Mode, Half Duplex Mode, receiver activity, and collisions. Figure 1-5 shows the MAX 3000 back-panel indicator lights.

Figure 1-5. MAX 3000 back-panel indicator lights

alarm or a trunk out of service (for example, during line loopback diagnostics). WAN alarms include Loss of Sync, Red Alarm, Yellow Alarm, and All Ones (or AIS).

For more information regarding the Alarm indicator light, see “Troubleshooting a Red Alarm” on page 5-2 and “Troubleshooting a blinking Alarm” on page 5-4.

Table 1-5 describes the indicator lights on the MAX 3000 unit’s back panel.

Table 1-5. MAX 3000 back-panel indicator lights

Light Description

LNK During 10 Mbps operation, indicates Link Valid status. Dur-

ing 100 Mpbs operation, indicates scrambler lock and receipt

of valid Idle codes. The light is green when on. TX On (green) when transmitter is active. DPLX On (green) when the port is in Full Duplex Mode. When the

light is off, the port is in Half Duplex Mode.

1-6 MAX Administration Guide

Table 1-5. MAX 3000 back-panel indicator lights (continued)

Light Description

100BT On (green) when 100 Mbps operati on is selected for the UTP

port. RX On (green) when receiver is active. COL On (amber) when a collision occurs.

Troubleshooting the Fault indicator light

If the MAX 3000 or MAX 6000 unit’s Fault indicator light is off, the unit passed its power-on self tests and you cannot communicate with the VT100 interface, press Ctrl-L to refresh the screen. If you still do not see any data, check the cabling between the MAX unit and your terminal as follows:

1 Check the pin-out carefully on the 9-pin cable .

The control terminal plugs into the HHT-VT100 cable or the 9-pin connector labeled Control on the back of the unit. If you are connecting to an IBM PC-like 9-pin serial connector, a straight-through cable is appropriate. Otherwise, you might need a 9-to-25 pin conversion cable.

2 Check the flow control settings on your VT100 termin al.

If you are not communicating at all with the MAX unit, determine if you can establish communication after you have turned off all transmit and receive flow control at your terminal or terminal emulator.

3 Determine whether you need a null-modem cable converter.

Though generally not needed, occa sional ly a null-mo dem cable con verter is required for a few of the large numbers of different cable and terminal configurations that are available.

Administering MAX Hardware

Interpreting indicator lights

The Fault indicator light should remain off except during the power-on self tests. If you are using the VT100 interface, press Ctrl-L to refresh the screen.

If the Fault indicator light remains on longer than a minute, there is a MAX hardwar e failure. A blinking Fault indicator light also indicates a hardware failure.

Should these situations persist, contact Lucent Technologies technical support.

MAX 800

The MAX 800 unit’s front panel indicator lights convey information about the power supply, WAN activity, and install ed P CMCIA car ds. Table 1-6 describes the indictor light s on th e fron t panel of a MAX 800 unit.

Table 1-6. MAX 800 front panel lights

Light Description

Power light The green Power light indicates when the unit has been turned on

and is receiving power.

MAX Administration Guide 1-7

Administering MAX Hardware

Interpreting indicator lights

Table 1-6. MAX 800 front panel lights (continued)

Light Description

Traffic light The yellow Traffic light blinks to indicate that the unit has been

properly installed and is transmitting and receivin g data across the network.

PCMCIA cards

The activity of the MAX 800 unit’s indicator lights and how to interpret them depends on which type of card is in use. You can interpret them when a PCMCIA card ISDN adapter is inserted in the corresponding slot. Table 1-7 describes the PCMCIA card-related indicator lights for a MAX 800 unit.

Table 1-7. PCMCIA card-related indicator lights

Light Descriptions

ON Each of the ON indicator lights shows whether the corresponding

Each of the eight modem slots on the MAX 800 unit's back panel has four corresponding lights on the front panel. The lights are:

• ON—Power (green)

• CD—Carrier Detect (red)

• Rx—Receive data (yellow)

• Tx—Transmit data (yellow) These four lights provide status information that corresponds to

each of the eight PCMCIA cards optionally plugged into the unit.

modem is connected correctly and/or recognized by the MAX 800 unit. When this light is on, the modem is ready to recei ve da ta.

A flashing ON light means that the MAX 800 unit does not recognize the modem but is going to attempt to receive data through it anyway and interpret the data as Hayes-compatible modem commands. This happens only when the modem is not on the approved list or is malfunctioning. You can eject the questionable modem or let the MAX 800 unit attempt to receive data through it.

CD A CD light illu minates when an outside phone line connects to th e

corresponding modem. The light remains illuminated until the remote party disconnects from the line.

Rx An RX light flashes when data is being received over the phone line

through the associated modem.

Tx A TX light flashes when data is being transmitted over the phone

line through the associated modem.

The MAX 800 unit’s back panel includes a link-status light that identifies the status of the 10BaseT Ethernet connection. If the light is on, a working connection exists between the MAX

1-8 MAX Administration Guide

Administering MAX Hardware

Troubleshooting the No Logical Link status

10BaseT port and the Ethernet hub. Figure 1-6 shows the back panel of the MAX 800 unit, including the link status light.

Figure 1-6. MAX 800 back panel

If you need more information about any component, read the description in Table 1-6. Note: Figure 1-6 shows two PCMCIA card modems inserted in Slots 7 and 8. An ISDN

terminal adapter requires two slots.

Troubleshooting the No Logical Link status

In some countries outside the U.S., it is common for no logical lin k to exist before the MAX unit places a call. In the U.S., when you first plug a line into the unit or switch power on, the central office switch can take as long as 15 minutes to recognize that the line is now available. You might have to wait that long for the line state to change to Active (A). The physical link can exist without a logical link up on the line.

If you wait longer than 15 minutes and the line is still not available: 1 Determine whether all the telephone cables are wired straight through.

If you are running multipoint (passive bus) on your switch, all of the telephone cables must be wired straight through. If any of the cables are wired to cross over, you will not be able to place calls.

2 Verify that 100% termination is provided on each line. 3 Determine whether you have correctly specified the Service Profile Identifiers (SPIDs) in

the Line N profile for each line. If the SPIDs are not correctly specified, the line status might indicate No Logical Link. Check with your system manager or carrier representative to obtain the SPID or SPIDs for your line. To specify your SPIDs, use the Pri SPID and Sec SPID parameters in the Line N profile.

Troubleshooting the AIM port interface

You can connect a videoconferencing codec (coder/decoder) to a port supporting inverse multiplexing to communicate over a point-to-point link. The MAX supports two types of Inverse Multiplexing: Bandwidth ON Demand Interoperability Group (BONDING) and Ascend Inverse Multiplexing (A IM). Both types a re supported by the V.35, RS-449, or X.21 port on the MAX unit. T ypically, inverse-multiplexed calls are between video codecs and other devices that might need high bandwidth for serial data over the WA N.

MAX Administration Guide 1-9

Administering MAX Hardware

Troubleshooting the AIM port interface

Inverse multiplexing uses pins for controlling the data flow through the port. A device sends a signal through a pin and over the line to another device. The signal indicates the control-line state. For example, when a device sends a signal indicating that it has data to send, the control-line state is Request to Send (RTS). If the other device sends a sign al to indicate that it is ready to receive data, its control-line state is Data Transmit Ready (DTR). The process of sending these synchronization signals between Inverse Multiplexing ports is called handshaking. You can install two types of inverse multiplexing cards on a MAX unit: Host/AIM6 and Host/Dual. The Host/AIM6 card supports six ports and the Host/Dual card supports two ports. Both cards support of the same dialing protocols: AIM/Bonding, RS-366, V.25 bis, and X.21.

When you install a Host/AIM6 or Host/Dual card on the MAX unit, the card’s ports become the default route for inbound data calls, taking precedence over the bridge/router software. Make sure that your call-routing configuration accommodates calls destined for the local Ethernet network.

Note:

become the default route for inbound data calls and take precedence over the bridge/router software. Make sure that your call-routing configuration accommodates calls destined for the local Ethernet network. For more information about configuring a MAX unit to support a Host/AIM6 or a Host/Dual card, see the Network Configuration Guide for your unit.

When you install a Host/AIM6 or Host/Dual card on a MAX unit, the card’s ports

Testing the AIM port interface

Test the AIM port interface in one of two ways:

• A local loopback test

• Through true end-to-end communications Many COder/DECoder (codec) unit s or other AIM dev ices su ppo rt so me use o f loopback. For

example, when a MAX unit is in loopback mode and is connected to a codec, users see their own configuration through the codec. Likewise, most bridge/router devices recognize and report a diagnostic message when a packet is sent out and received by the same module. More often than not, the codec must be configured explicitly to accept the loopback from the communications device.

Local loopback testing is the best tool when troubleshooting the AIM port interface (the interface between the codec and the MAX unit). All of the symptoms and operations described in this section assume you are working from the local loopback diagnostics menu. Unless otherwise specified, the AIM port interfaces in this section can include the Remote Port Modules (RPMs).

The first and most critical aspect of the AIM port interface is the cable or cables connecting the codec to the MAX unit. If you are unsure about the cabling required, contact Lucent Technologies technical support.

Calls fail between AIM ports

The following first-level diagnostic commands can help in troubleshooting calls between AIM ports:

• For a local loopback toward an application at its AIM port interface, use the Local LB command in the Port Diag menu.

1-10 MAX Administration Guide

• For a loopback toward an application at its remote-end AIM interface, use the DO Beg/End Rem LB command.

• For a channel-by-channel error measurement, use the DO Beg/End BERT command.

• To resynchronize a multichannel call, use the DO Resy nchronize command.

T o use a DO command, y ou must be in a prof ile or status window specific to an AIM por t with a call online.

Excessive data errors on calls to AIM ports

Circuit-quality problems sometimes encountered on PRI and BRI lines include excessive data errors or handshaking on calls to AIM ports and scrambling of inbound data during AIM Static calls.

If you encounter a problem in which the MAX reports excessive data errors on some calls to AIM ports, run a Byte Error Rate Test (BERT), which counts data errors that occur on each channel during a call to a AIM port. The BER T ch ecks the data integrity from the MAX unit at one end of the call to the MAX unit at the other end.

If you have verified that the MAX is correctly installed light and configured, and you have previously placed calls without excessive errors, use the DO Beg/End BERT command to run the BERT. Do not clear the call before running the BERT. Run a BERT only under the following conditions:

• A call is active.

• The Call Type parameter is set to

• The Call Mgm parameter is set to

AIM, FT1-B&O

Manual, Dynamic

Administering MAX Hardware

Troubleshooting the AIM port interface

FT1-AIM

, or

Delta

Set the Auto BERT parameter in the Call profile to run an automatic BERT. If the BERT indicates very high errors on some of the chann els, clear the call and redial. When re dialed, the call might take a different path, correcting the excessive error problem.

Excessive handshaking on calls to AIM ports

Handshaking is a normal and momen tary occurrence during call setup and when the MAX unit increases or decreases bandwidth. If there is trouble in the circuits that carry the call, frequent handshaking can occur. If the trouble is serious enough to degrade the quality of the call, the MAX unit disconnects. If handshaking is continuous for over a minute, the problem is probably not due to the quality of the line, an d you should call Lucent Technologies technical support.

Inbound data is scrambled during an AIM Static call

Because an AIM Static call does not have a management channel, it is possible for data scrambling to occur because of WAN slips, which are a type of timing error. Slips are a very infrequent occurrence. If you should encounter such a problem, clear the call and redial.

MAX Administration Guide 1-11

Administering MAX Hardware

Troubleshooting a codec

A COder/DECoder (codec) unit is a device that encodes analog data into a digital signal for transmission ov er a digital medium. Codecs are o ften used for videoconferencing.

A dual-port call is one in which a codec performs inverse multiplexing on two channels in order to achieve twice the bandwidth of a single channel. The codec provides two ports, one for each channel. T wo AIM ports on the MAX unit connect a dual-port call to the codec. These ports are the primary port and the secondary port. Because the unit places the two calls in tandem and clears the calls in tandem, it considers them a single call.

The codec indicates that there is no connection

The codec expects one or more of its control lines to be active. If no lines are active, toggle the various outputs available on the local loopb ack diagnostics menu. If there is still no connection, verify that you have installed the host cables correctly as described in the Hardware Installation and Basic Configuration Guide for your MAX unit.

If the cabling is installed correctly, examine the host interface cable pin-outs which are described in the Hardware Installation and Basic Co nfiguration Guide for your unit.

The codec does not receive data

If the codec does not receive data, proceed as follows: 1 Verify that the codec is configured to accept a loopback at the communications device.

Frequently, a codec requires certain control lines to be active during data transfer. Therefore, you might want to toggle the various host interface output lines, especially Data Set to Ready (DSR) and Carrier Detect (CD), to ensure that they are active.

2 Check the control line states.

If there is still no data transfer, your cable might not provide one or more control lines

required by the host. Refer to the unit’s Hardware Installation and Basic Configuration Guide for a description of the pins that it requires to be active. The following control lines

are generally the most important ones: – Carrier Detect (CD) – Clear To Send (CTS) – Data Set Ready (DSR)

3 Make sure the codec is configured for clocking.

If you are convinced that the control lines are in their correct states, but there is still no data transfer, you might have a clocking problem. The MAX unit provides both the transmit data clocks and the receive data clocks to your equipment through the host interface. The codec must be configured to accept the clocks from the unit.

4 Check your cable length.

If the cable length exceeds the recommended distances, you should be using terminal timing. Alternatively, you might need to install Remote Port Modules (RPM).

5 Check the data rate.

Adjust the data rate from the local loopback diagnostics menu by choosing the number of channels. Some applications cannot work above or below a certain data rate. For example,

1-12 MAX Administration Guide

some high performance codecs cannot operate at data rates of less than 384 Kbps. In such cases, adjust the number of channels of data being looped back.

The codec cannot establish a call

Y ou might notice that the Port profile is set to establish calls when Data Transmit Ready (DTR) is active, but the codec cannot establish a call. If the codec is going to originate the calls directly by using control-lead dialing, the call origination and clearing mechanisms must be configured for compatibility between the MAX unit and the codec. To verify a compatible configuration from the local loopback diagnostics menu:

1 Disable each of the MAX output control lines except DSR.

T o disable an output control line, toggle it to be Inactive (-). At this time, the codec should indicate that there is no connection.

2 Request an outgoing c all fr om yo ur equipment and monitor the Port Leads st atus menu of

the active ports in the call. One or more of the control line inputs should become active and remain active for some

period of time. If the DTR lead’s input does not change state, your cable is not properly configured. In this case, you must change the cable so that it routes the appropriate host output signal to the DTR input of the MAX. The MAX must use the DTR lead to establish outgoing calls.

Administering MAX Hardware

Troubleshooting a codec

3 Once you have made any changes required for verifyin g that the DTR lead becomes active

when the MAX requests the call, configure the Port profile to expect the DTR input. In the Port profile, set Dial Call to

DTR Active

Calls initiated by control-lead toggling are cleared too soon

If the MAX unit clears a call initiated by control-lead toggling before it completely establishes the call and the call is cleared almost immediately, the Port profile probably has a configuration error. To find the source of the problem, proceed as follows:

1 While monitoring the Port Leads status menu of the AIM ports used in the call, place an

outgoing call from the codec.

2 Watch the DTR input carefully while the MAX unit is establishing the call.

If the DTR input becomes Active (+) and thereafter returns to Inactive (-), the unit is using DTR as a pulse to place the call. Make sure that the Clear parameter in the Port profile is not set to maintains DTR positive during the call.)

3 While your equipment is still dialing the call, toggle the value of the CD output si gnal to

indicate to your equipment that the call completed. At this time, watch the control leads very carefully. Make certain that any control leads that toggle while the call is being established are not used in the Clear parameter to clear the call. This type of configuration error is the most likely cause of a call being cleared almost immediately.

DTR Inactive

. (Set Clear to

DTR Inactive

only when the application

The codec cannot clear a call

If a call cannot be cleared from the codec, the Port profile probably has a configuration error. To verify the source of the problem, proceed as follows:

MAX Administration Guide 1-13

Administering MAX Hardware

Troubleshooting cable issues

1 While monitoring the Port Leads status menu of the AIM ports used in the call, place an

outgoing call fro m your equipme nt.

2 Once the host has requested the outgoing call, toggle the CD output signal to Active (+).

The codec should recognize that the call is online.

3 Make a request to clear the call from the codec. 4 Watch the control leads very carefully as one or more of the input control lines to ggle.

Generally, either DTR or RTS is the line that toggles. Record whether the control lead input goes to Active (+) or Inactive (-) when the call is cleared.

5 Verify th at the value of the Clear parameter in the Port profile matches the action that the

codec takes when the call is cleared.

Troubleshooting cable issues

Data errors on all calls can indicate that you have installed faulty h ost interface cables or cables not suited to the application. Information on host interface cab ling requirements is found in the Hardware Installation and Basic Configuration Guide for your unit.

If you have purchased or buil t you r own cables, veri fy th at the pin -out i s the same as the MAX pin-out for compatibility. The Hardwar e Installation Guide and Basic Configuration Guide for your MAX unit lists the host interface pin-outs.

Frequently, a DB-25 breakout box is useful for monitoring control leads and for making quick changes to the cabling. However, because the host interface is running V.35 or RS-422 signal levels, you must verify that the breakout box is passive. That is, you must verify that the breakout box is not regenerating RS-232 level signals.

Displaying interface statistics

To display the supported interface-statistics commands, enter the Show IF command with a question mark. For example:

ascend% show if ? show if ? Display help information

show if statsDisplay Interface Statistics show if totalsDisplay Interface Total counts

1-14 MAX Administration Guide

Administering MAX Hardware

Displaying interface statistics

To display the status and packet count of each active WAN link and each local and loopback interface, enter the Show IF Stats command. For example:

ascend% show if stats Interface Name Status Type Speed MTU InPackets Outpacket

ie0 ethernet Up 6 10000000 1500 107385 85384 wan0 Down 1 0 1500 0 0 wan1 Down 1 0 1500 0 0 wan2 Down 1 0 1500 0 0 wanidle0 Up 6 10000000 1500 0 0 lo0 loopback Up 24 10000000 1500 0 0

Table 1-8 describes the output of the Show If Stats command.

Table 1-8. Output of the Show If Stats command

Field Description

Interface Interface name. For more information, see the Network Configura-

tion Guide for your MAX unit.

Name Name of the profile or a text name for the interface. Status

(the interface is functional) or

Down

(the interface is not

functional).

Type Type of application being used on the interface, as specified in RFC

1213 (MIB-2). For example, 23 indicates PPP and 28 indicates SLIP. Speed Data rate in bits per second. MTU The max i mum packet size allowed o n the interface. MTU stands f or

Maximum Transmission Unit. InPackets The number of packets the interface has received. OutPackets The number of packets the interface has transmitted.

T o display the packet count at each interface, broken down by type of packet, enter the Show If Totals command. For example:

ascend% show if totals Name --Octets----Ucast-- -NonUcast- Discard -Error- Unknown -Same IF-

ie0 i: 7813606 85121 22383 0 0 0 0 o: 101529978 85306 149 0 0 0 0 wan0 i: 0 0 0 0 0 0 0 o: 0 0 0 0 0 0 0 wan1 i: 0 0 0 0 0 0 0 o: 0 0 0 0 0 0 0 wan2 i: 0 0 0 0 0 0 0

MAX Administration Guide 1-15

Administering MAX Hardware

Using modems to perform administrative tasks

o: 0 0 0 0 0 0 0 wanidle0 i: 0 0 0 0 0 0 0 o: 0 0 0 0 0 0 0 lo0 i: 0 0 0 0 0 0 0 o: 0 0 0 0 0 0 0

Table 1-9 describes the output of the Show If command.

Table 1-9. Show If command output

Field Description

Name

Octets

Ucast

NonUcast

Discard

Error

Unknown

Same IF

Interface name. For more information, see the Network Configura-

tion Guide for your MAX unit.

Total number of bytes processed by the interface.

Packets with a unicast destination address.

Packets with a multicast address or a broadcast address.

Number of packets that the interface could not process.

Number of packets with CRC errors, header errors, or collisions.

Number of packets the MAX forwarded across all bridged interfaces

because of unknown or unlearned destinations.

Number of bridged packets whose destination is the same as the

source.

Using modems to perform administrative tasks

In order to isolate performance issues related to modems, you can disable specified digital modems and modem slots. A digital modem is an internal device in a MAX unit that enables it to communicate over a digital line with a station connected to an analog line. Incoming modem calls and incoming digital calls come over the same digital line. The MAX unit can accept an incoming call from the network either as a pure digital stream or as a digital stream encoded by Pulse Coded Modulation (PCM). A PCM-encoded digital stream contains a digitized version of the analog waveform sent by a device attached to a modem. The MAX unit can also convert outgoing data into analog waveforms, convert these waveforms to a PCM-encoded digital stream, and send them to the network over a digital line. The network presents the data to the receiving modem in analog form over an analog line. The data looks exactly as it would appear if it had been sent by an analog-based modem.

Quiescing or disabli ng a modem or modem sl ot does n ot resul t in ac tive calls being torn down. Instead, when the active call discontinues, that modem or modem slot is added to a disabled list and is unavailable for use. If all modems or modems slots are disabled, incoming callers receive a busy signal until the modems have been restored for service. A quiesced modem or modem slot is available for use approximately 20 seconds after it has been re-enabled.

1-16 MAX Administration Guide

Administering MAX Hardware

Booting from a FAT-formatted PCMCIA card

To disable a modem or a modem slot, access the V.90 S56 II Modem (or K56 Modem-16)> Mod Config menu.

To disable a particular modem, use the Modem #N parameter, where N is the modem number from 1 to 30. Set one of the following values:

Value Result

enable modem dis modem

dis modem+chan

To quiesce an entire modem slot, use the ModemSlot parameter. Set one of the following values:

Value Result

enable slot dis slot

dis slot+chan

Enables disabled modems. This is the default value. Places the modem on the disabled list. When an active connection

drops, the card becomes available for maintenance. Places the modem and an arbitrary B channel on disabled lists.

Enables disabled modems on the slot. This is the default value. Places all modems that are not active on the disabled list. When the

active connections drop, the card becomes available for maintenance. Disables all modems on the slot, along with an equal number of B

channels.

Booting from a FAT-formatted PCMCIA card

The Windows and DOS operating systems use a File Allocation Table (FAT) to keep track of the parts of files stored on devices such as hard disks and Personal Computer Memory Card International Association (PCMCIA) cards. If you administer more than one MAX 6000 unit, use a Windows or DOS operating system, and have access to a FA T-formatted PC card you can boot the units from the PCMCIA card. Only the MAX 6000 supports this feature.

In order to start one or more MAX 6000 units from a FAT-formatted PCMCIA card, you must obtain the TAOS software you want to use for booting, load it on the formatted PCMCIA card, and reset the unit. However, before you boot the MAX 6000 from a PCMCIA card, you must obtain the following two files from the Lucent Technologies FTP site. You need the fo llowing two file types :

• The TAOS executable file, which has the filename extension identify the specific file to place on the unit’s PC card, see /pub/Software-Releases/Max/Upgrade-Filenames.txt on the Lucent Technologies FTP site, ftp.ascend.com.)

• The bootstrap loader, also called a handler, in a file named m60handler.bin.

Place both files in the TFTP home directory of a TFTP server with network access to the MAX unit.

MAX Administration Guide 1-17

.m60

. (If you need help to

Administering MAX Hardware

Booting from a FAT-formatted PCMCIA card

Loading the software on the PCMCIA card

Use TFTP to load the TAOS executable file and the handler file on the PCMCIA card. When

you load software using the MAX 6000 unit’s TFTP functionality, the unit saves its configuration during the process.

Note: Your Security profile must permit use of Diagn os t ics mo de o r you must log in with t he Full Access profile.

To place software on the PC card, proceed as follows: 1 Enter Diagnostics mode by pressing Ctrl-D to display the DO menu and selecting D for

Diagnostics. The > prompt appears.

2 Format the PC card for booting the MAX 6000 unit by entering the following command:

> format -b

The -b option reserves space for the handler file.

3 The FAT file system now includes a location for the handler file, which contains a routine

that later invokes the TAOS executable file. To load the handler software from your TFTP server directory enter the following

command:

> tloadcode -b

where

-b

–

specifies that the

reserved for the handler file on the PC card.

tftp-server-IPadr

–

loaded the unit’s binary files.

m60handler.bin

–

4 Create a boot directory named Current as follows:

> mkdir /current

5 Load a TAOS executable file for the unit into the boot directory as follows:

> fload

where –

–

tftp-server-IPadr TAOSfilem60.bin

tftp-server-IPadr

stored the MAX 6000 binary file.

TAOSfilem60.bin

loaded on the PC card. The name may be as long as 64 characters, but the filename extension must be .bin and the file must be put into the default /current directory, as in the example.

tftp-server-IPadr

tloadcode

is the IP address of the TFTP server on which you have

is the name of the handler file.

is the IP address of the TFTP server on which you have

is the name of the executable file for the MAX 6000 unit when

command load the software into the space

m60handler.bin

To boot the unit from the TAOS executable file stored on the PC card, enter the Reset command to disconnect all active connections and restart the unit:

> reset

This completes the process of loading the software on the PC card.

1-18 MAX Administration Guide

Managing files on the PC card

TAOS includes file management commands that you use on the FAT file system. Table 1-10 summarizes the PC card file management commands.

Table 1-10. Summary of PCMCIA file management comma nds

Task Command and syntax

Administering MAX Hardware

Booting from a FAT-formatted PCMCIA card

Format a PC card with the FAT file system. Copy the handler file or TAOS executable

file from the TFTP server to the PC card. Copy a file from the TFTP server to the PC

card. Copy an image between the PC card and

internal flash memory. Create a directory. Remove a file or an empty directory. Move a file or directory. Report the code version stored on the card.

Lists the files and directories on the card’s file system.

format [ -o -e -b ] [

tloadcode [

options

device

]

tftp_server_IPadr filename

fload [

FImageCopy [-i | -p ]

mkdir

fVersionInfo -p

tftp_server_IPadr path1

path2

]

path

path1 path

path

]

MAX Administration Guide 1-19

DO Commands and Administrative Tasks

Activating administrative permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Performing basic administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Testing and troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

The MAX unit’s user interface is a menu-driven interface accessed through a VT100 terminal or VT100 emulation software running on a PC or workstation. Most of the tasks you perform in order to configure the unit can be done by using parameters in that menu-driven interface. However, one of the first tasks that you perform as an administrator, activating administrative commands, can be performed by using DO commands. Also, use DO commands to perform other administrati v e t asks. DO menu commands provide ways to manage MAX units. In some cases, they duplicate functions that are accessible through other methods, such as VT100 interface menu items. The availability of a particular command depends on your location in the VT100 interface and on the Security profile in effect.

This chapter describes how to use DO commands to activate administrative permissions. This chapter also reacquaints you with the basics of using the DO commands. The last section of this chapter introduces you to testing and troubleshooting the MAX by using DO commands.

Note: Under most circumstances, diagnostic commands are not required for correct op eration

of the MAX unit, and in some circumstances might produce undesirable results. However, if you require information about diagnostics DO commands, see “Diagnostic Parameters and Commands” o n page B-1.

For an overview of how to access and use the VT100 interface and CLI interfaces, including DO commands, refer to the Hardware Installation and Basic Configuration Guide for your unit. For information about Terminal Server DO commands, see Chapter 3, “Terminal-Server Administrat i ve Tasks.”

Activating administrative permissions

The DO menu is a context-sensitive list of commands that appears when you press Ctrl-D from any location in the VT100 interface. The commands in the DO menu vary, depending on the context in which you invoke it. For example, if you press Ctrl-D in a Connection profile, the DO menu looks similar to the followin g:

DO… >0=ESC

1=Dial P=Password

MAX Administration Guide 2-1

DO Commands and Administrative Tasks

Activating administrative permissions

S=Save E=Termserv D=Diagnostics

To execute a DO command, press and release the Ctrl-D combination (or the DO key on the palmtop), and then press and release the next k e y in the sequen ce (such as 1 to in vok e the Dial command). On a VT100 terminal, the PF1 function key is equivalent to Ctrl-D.

Before you use the administrative commands and profiles, you must log in as a superuser by activating a Security profile that has sufficient permissions (for example, the Full Access profile.) Proceed as follows:

1 Press Ctrl-D. The DO menu appears:

00-300 Security DO

…

>0=ESC

P=Password

2 Press P (or select

P=Password

3 In the list of Security profiles that opens, select Full Access.

The MAX unit prompts you for the Full Access password:

00-300 Security Enter Password:

[]

Press > to accept

4 Type the password assigned to the profile, and press Enter. The default password for the

Full Access login is

Ascend

When you enter the correct password, the MAX unit displays a message informing you that the password was accepted and that the unit is using the new security level:

Message #119 Password accepted. Using new security level.

If the password you enter is incorrect, the MAX unit prompts you again for the password.

Note: The first task you should perform after logging in as the superuser is to assign a new password to the Full Access profile.

The commands summarized in Table 2-1 are tools for managing security of MAX units.

Table 2-1. DO menu commands for activating administrative permissions

DO menu command Function

ESC (DO 0) Abort and exit the DO menu. Password (DO P) The DO Password command enables you to log into the

MAX unit.

2-2 MAX Administration Guide

Performing basic administration

The availability of a particular DO command depends on your location in the VT100 interface and the Security profile in effect. DO commands are used for session management, call management, and testing and troubleshooting. Commands for these functions are summarized in Table 2-2 on page 2-4, Table 2-3 on page 2-6, and Table 2-4 on page 2-10.

Managing sessions

Besides aborting and exiting sessions (ESC DO 0 command), DO commands load parameter values in the current profile, save the VT100 interface menu layout, log in or log out of the unit, save the parameter values in a specified profile, and close an active Telnet session on the unit.

Using the DO Load command

The DO Load command loads a saved or edited profile and overwrites the values of the current profile. For example, suppose you have saved a profile named Memphis in the Directory location 21-102 and your screen currently displays the foll owing lines:

21-100 Directory

21-1 Factory 21-101 Tucson >21-102 Memphis

DO Commands and Administrative Tasks

Performing basic administration

If you execute DO Load, the following display appears:

Load profile...?

0=Esc (Don’t load) 1=Load profile 102

If you choose the first option by pressing 0 (zero), the MAX unit aborts the load operation. If you choose the second option by pressing 1, the following status window appears:

Status #116

profile loaded as current profile

The Directory menu shows the results of the load operation:

21-100 Directory

21-1** Memphis 21-101 Tucson >21-102 Memphis

Saving the VT100 layout

The DO Menu Save command saves the entire current VT100 interface layout. The current layout replaces the default layout.

Keep in mind the following additional information:

• The DO Menu Save command appears only if the cursor is in front of th e Sys Config menu.

MAX Administration Guide 2-3

DO Commands and Administrative Tasks

Performing basic administration

• The command always places Sys Config in the default Edit display. (To change the default Edit display, you must configure the Edit parameter in the Sys Config profile after using the DO Menu Save command.)

• Menu Save does not apply to palmtop controllers, nor does it apply when your VT100 is plugged into an Remote Port Module (RPM) or palmtop port.

Saving the profile

The DO Save command saves the current parameter values in a specified profile.

Keep in mind the following additional information:

• If a profile is protected by a Security profile, you might not be able to overwrite it.

• The Save option does not appear if you are not logged in with operational privileges.

Closing a Telnet session

The DO Close T elnet command closes the current Telnet session. You must be running a T elnet session from a MAX unit's terminal-server interface.

The commands summarized in Table 2-2 are tools for managing sessions with MAX units.

Table 2-2. DO menu commands for session management

DO menu command Function

ESC (DO 0) Abort and exit the DO menu. Load (DO L) Load parameter values into the current profile. Menu Save (DO M) 8 Save the VT100 interface menu layout. Save (DO S) Save parameter values in the specified profile. Close TELNET (DO C) Close the current Telnet session.

Copying FXS profiles with the DO Commands

The MAXPOTS FXS™ slot card provides Plain Old Telephone Service (POTS) functionality to MAX 6000 units that support T1/E1 and to MAX 3000 units that support T1/E1/BRI. The Foreign Exchange Station (FXS) designation indicates that the POTS ports provide subscriber loop functionality, including loop current, supervision, and signaling, similar to that provided by the telephone company’s Central Office.

The MAXPOTS FXS slot card enables users to place calls between POTS ports and T1 trunks (inband signaling or PRI ), POTS ports and E1 trun ks (PR I or R 2), or betw een tw o POTS ports. Up to four MAXPOTS FXS slot cards can be installed i n a MAX 6000 T1 or a MAX 6000 E1. The MAXPOTS FXS card is also available on the MAX 3000 T1, E1 and BRI.

For more information about the MAXPOTS FXS slot card, see the Network Configuration Guide for your unit.

2-4 MAX Administration Guide

DO Commands and Administrative Tasks

Performing basic administration

There are five possible slot profiles for each MAXPOTS slot card. The first profile listed in the

slot’s menu is always the active profile. Initially the alternative configurations in the other four profiles.

To copy the active profile to one of the alternative profiles, proceed as follows: 1 From Analog FXS > FXS Config, select the active profile.

The active profile appears.

2 Press Ctrl-D to access the DO menu.

The DO menu appears.

3 Select S (Save). 4 Select the alternative profile by using the Up Arrow and, Down Arrow keys, and press

Enter. The active profile is saved to the specified alternative profile.

To activate one of the alternative profiles, copy any alternative profile to the active profile, proceed as follows:

1 From Analog FXS > FXS Config, s elect the alternat ive (101, 102, 103, or 104 ) profile you

want to activate. The alternative profile appears.

2 Press Ctrl-D to access the DO menu.

The DO menu appears.

3 Select L (Load).

default

profile is active. You can save

4 The alternative profile becomes the active profile.

Managing calls

Use DO commands to manage calls on a MAX unit. Since the availability of a particular DO command depends on your location in the VT100 interface, the Connection pr ofile for the call must be open or selected in the list of profiles.

To manually place a call, proceed as follows.

1 Open the Connection profile for the destination you want to call. 2 Press Ctrl-D.

3 Press 1 (or select 1=Dial) to invoke the Dial command. 4 Watch the information in the Sessions status window. You should see the called number,

Note: The Load option does not appear when you are in the active profile.

The DO menu appears. For example:

DO…

>0=ESC

1=Dial P=Password S=Save E=Termserv D=Diagnostics

followed by a message that the network session is up.

MAX Administration Guide 2-5

DO Commands and Administrative Tasks

Testing and troubleshooting

To manually clear a call, proceed as follows. 1 Open the Connection profile or tab to the status window that displays the information

about active session you want to clear.

2 Press Ctrl-D.

The DO menu for the active session appears. For example:

10-200 1234567890 DO

…

>0=ESC

2=Hang Up P=Password S=Save E=Termserv D=Diagnostics

3 Press 2 (or select

The status window displays changes when the call is terminated.

Clear a call by opening the Connection profile for the active connection or tab to the status window in which that connection is listed, as described in the Hardware Installation and Basic Configuration Guide for your unit.

The DO commands summarized in Table 2-3 are for call management.

Table 2-3. DO menu commands for call management

Command Description

Answer (DO 3) Answer an incoming call. Contract BW (DO 5) Decrease bandwidth. Dial (DO 1) Dial the selected or current profile. Extend BW (DO 4) Increase bandwidth. Hang Up (DO 2) Hang up from a call in progress. Resynchronize (DO R) Resynchronize a call in progress.

2=Hang Up

) to invoke the Hang Up command.

Testing and troubleshooting

Use DO commands to perform testing and troubleshooting tasks: measure bit-error rate test (BERT), measure performance with a remote loopback test, and perform remote management tasks. Use the DO commands discussed in the following sections when you need to analyze the performance of a MAX unit, the network, or remote units.

Using bit-error tests

A bit-error rate (BER) is the ratio of error bits to the total number of bits transmitted. A MAX unit can perform a bit-error rate test (BERT) by sending a known pattern of bits and counting

2-6 MAX Administration Guide

DO Commands and Administrative Tasks

Testing and troubleshooting

any errors received. The BER is one measure of the unit’s, the network’s and the remote unit’ s data transmission quality.

The DO Beg/End BERT command starts and stops a channel-by-channel BERT. The test runs over the currently called circuits from end-to-end. I t reports the total number of incorrect bytes found, and breaks the errors down according to DS0 channel. The results are displayed in the Session Err window.

When you select DO Beg/End BERT, the following events occur:

1 The local device sends a known data pattern over the network. 2 The responding end goes into a DS0-by-DS0 loopback mode of operation.

The signal at the remote end of the test is looped back at the application to a MAX unit interface, rather than at the network to unit interface.

3 By monitoring the data being received against the transmitted pattern, the local device

counts the errors it receives on each individual DS0 channel. If a single byte has two or more errors, it is recorded as a single error.

The call status letter T , for test, appears in the upper right-hand corn er of the display of both the local and the remote MAX unit to indicate that a BERT is in progress. To resume normal operation, end the BERT by entering Ctrl-D 7 (DO 7 on the palmtop controller).

Keep in mind the following additional information:

• A BERT suspends any transfer of user data in either directions.

• All commands that affect the call are disabled, except the command that ends the BERT.

• You must be in a port-specific edit menu or status window to execute the DO Beg/End BERT command.

• It is possible to run the BERT in only one direction at a time. That is, only one side can be the requester.

• To allow a MAX unit time to complete handshaking, you must wait at least 20 seconds between toggling the BERT on and off.

• The DO Beg/End BERT command does not appear if you are not logged in with operational privileges.

The statistics window and bit-error test

Ascend Inverse Multiplexing (AIM) manages the connection of two remotely located MAX units. A Statistics window is an AIM-port-specific window that provides information about line utilization and synchronization delay while a call is up. A Statistics window exists for each AIM port. For example, a Statistics window with the following contents would apply to the first port of an AIM card installed in slot 7:

71-300 Albuquerqu+ O Qual Good 01:23:44 MAX Rel Delay 10 CLU 80% ALU 77%

The first line of a Statistics window shows the status window number. This number includes the host port's number, the name of the current Call profile, and the call-status character.

MAX Administration Guide 2-7

DO Commands and Administrative Tasks

Testing and troubleshooting

The second line lists the quality of the call and the call duration. When a call lasts more than 96 hours, the window displays the call duration in number of days. The call quality, or Qual, can

Good, Fair, Marg

Good

•

Fractional T1-Backup and Overflow (FT1-B&O) is a type of call that provides automatic protection of nailed-up circuits. For FT1-B&O calls, the s econd line of the Statistics window might not show the call duration. When an FT1-B&O call h as no bad channels, the call duration appears as usu al. But if it does, the number o f of fl ine nai led-u p channels appears after the call quality. The following screen shows the Statistics window of an FT1-B&O call with two channels offline:

21-300 Albuquerqu+ O Qual Good 00:04:01 MAX Rel Delay 10 CLU 80% ALU 77%

—No errors have been detected during the transmission of the call.

Fair

—Some errors have been detected in transmission.

Marg

—A significant number of errors have been detected. In this case, reliable

transmission is not guaranteed and resynchronization is recommended.

Poor

—A MAX unit might drop individual channels from the call, or clear the call

automatically.

(marginal), or

Poor

. The meaning of each value is as follows:

(Specify FT1-B&O with the Call Type parameter. For more information about the Call Type parameter, see the MAX Reference.)

The third line displays the Max Rel Delay value. During a call, di fferent channels can take different paths through the WAN and can arrive at the destination at different times. This difference is known as a relative delay. The Max Rel Delay value indicates the largest amount of delay between any two channels in the call. The delay is calculated and reported in multiples of 125 microseconds and cannot exceed 3000.

The last line displays the following values:

CLU

•

CLU Type=FT1-AIM or FT1-B&O in the Call profile.

(For related information, see the Call Mgm, Call Type, Dyn Alg, and Sec History parameters in the MAX Reference.)

—Current line utilization. The percentage of bandwidth currently being used by the

call for transmitted data, divided by the total amount of band width that is available.

ALU

—Average line utilization. The average amount of available bandwidth used by the call for transmitted data during the current history period as specified by the Sec History and Dyn Alg parameters.

ALU

and

apply only to calls for which

Using remote loopback

Call Mgm=Dynamic

and

Call

A remote loopback is a type of diagnostic test in which the MAX unit transmits a signal that is returned to the sending unit after passing through the network. This allows you to compare the returned signal and get a sense of any problems on the remote unit, the network, and the local unit. Loopbacks are often done by excluding one piece of equipment after another.

2-8 MAX Administration Guide

DO Commands and Administrative Tasks

Testing and troubleshooting

The DO Begin/End Rem LB command begins and ends a loopback at the serial ho st port at the remote end of the call.

To begin a remote loopback, select DO Beg/End Rem LB. The call status character L appears in the upper right-hand corner of the screen at both the local and the remote device. A remote loopback tests the entire connection from host interface to host interface. The following events occur:

1 The serial host interface of the local MAX unit begins the remote loopback test. 2 The data loops at the serial host interface of the remote MAX unit and comes back to the

local unit.

This loopback is also known as a remote data loopback, because the loopback occurs at the DTE/DCE interface. To end a remote loopback, press Ctrl-D 6 (DO 6 on the palmtop controller).

Unplugging the palmtop controller also terminates a remote loopback.

Keep in mind the following additional information:

• A remote loopback disables data flow from the remote host, but the call remains online.

• A remote loopback disables Dynamic Bandwidth Allocation (DBA).

• Only switched and nailed-up channels active during the current call are looped back.

• Drop-and-Insert channels are not looped back.

• You must be in a port-specific edit menu or status window to use the DO Beg/End LB command.

• To allow the MAX unit time to complete handshaking, you must wait at least 20 seconds between toggling the remote loopback on or off.

• When the remote device is a not a Lucent Technologies inverse multiplexer, you cannot set up a remote loopback if the network connection occu rs ov er an ISDN line an d the Call profile include s any of the following settings:

– Call Type is set to – Call Type is set to

• If the remote device is an ISDN Terminal Adapter (TA), the MAX unit cannot usually perform a remote loopback. ISDN TAs cannot recognize the loopback signal. However, most switching Channel Service Units/Data Service Units (CSU/DSUs) recognize the remote loopback signal that the MAX unit sends, and remote loopbacks are usually possible with such equipment.

• The MAX unit uses a proprietary loopback message when the AIM management subchannel is present (Call Mgm is set to Manual, Dynamic, or Delta in a Call profile).

• The MAX unit uses the CC ITT V.54 loopback pattern when no management subchannel is present (Call Type is set to 1 Chnl or 2 Chnl and Call Mgm=Static in a Call profile).

1 Chnl AIM

2 Chnl

BONDING

and Call Mgm is set to

Static

Mode 1

• If the MAX unit fails to set up a remote loopback, it establishes a loopback at the local host interface that tried to establish the call.

• The DO Beg/End LB command does not appear if you are not logged in with operational privileges.

MAX Administration Guide 2-9

DO Commands and Administrative Tasks

Testing and troubleshooting

Using remote management

You can use remote management DO commands to begin and end a remote management session on the MAX unit.

The DO Beg/End Rem Mgm command begins and ends remote management of the device at the remote end of an Ascend Inverse Multiplexing (A IM) call. When you enter the command, the VT100 interface displays the following message at the top of its screen:

REMOTE MANAGEMENT VIA

specifies the serial host port t hrough which you are conducting remote man agemen t . To

port

end an AIM remote management session, en ter Ctrl-D 8 (DO 8 o n the palmtop contr oller). You cannot exit remote management from a port other than the port from which you began remote management. When the message at the top of the VT100 screen disappears, the screens associated with the local MAX unit appear.

Note: Use only the VT100 interface to perform remote management. The palmtop controller provides no indication as to whether you are in remote management or local management.

Keep in mind the following additional information:

• During an AIM call, remote management adds 20 Kbps to the 0.2% overhead of the call, and to that small extent reduces the bandwidth provided to serial host devices using the connection.

• The DO Beg/End Rem Mgm command is available for connections if the Call profile's Call Type parameter is set to

Static

• An error message of Remote Mgmt Denied indicates that you have tried to control a MAX unit that is not configured to allow remote management. You cannot remotely manage a device for which Remote Mgmt parameter, in the Sys Config profile, is set to No.

port

FT1-AIM, FT1-B&O

, or

AIM

(but not if Call Mgm is set to

• You cannot begin remote management if you do not have a call on line to the remote device. Furthermore, you mus t sel ect the DO Beg / End R em Mgm comm and from a menu specific to that call.

• The DO Beg/End Rem Mgm command does not appear if you are not logged in with operational privileges.

The DO commands summarized in Table 2-4 are tools for testing and troubleshooting MAX units.

Table 2-4. DO menu commands for testing and troubleshooting

DO menu command Function

Beg/End BERT (DO 7) Starts and stops BERT, a bit error rate test. Beg/End Rem LB (DO 6) Starts and stops a remote loopback. Beg/End Rem Mgm (DO 8) Starts a remote management session.

2-10 MAX Administration Guide

DO Command operations

When the list of DO commands appears, many operations might not be not available if the right profile has not been selected. Because the MAX unit can manage a number of calls simultaneously, you might need to select a specific Connection profile, Port profile, or Call profile in order to see certain DO commands. For example, to dial from a Call profile or a Connection profile, you must move to the Call profile (Host/6 > Port N Menu > Directory) or the Connection p rofile and press Ctrl-D 1.

You cannot dial if the Operations parameter is set to No for the con trol p ort. If a call is alread y active, DO 2 (Hang Up) appears instead of DO 1 (Dial). If the T1 or E1 line is not available, Trunk Down appears in the message log and you cannot dial.

In earlier versions of the software, the MAX unit downloaded the required code and immediately commenced with AT POST (which sends the string AT to each modem and waits for the modem to respond with OK). With the current software, the unit downloads the modem code, waits for the modems to checksum the downloaded code, and then verifies that the checksum matches before continuing. If the checksum does not match, the unit downloads the code again, up to two more times. If the checksum still does not match after three download attempts, the unit fails the entire slot card.

DO Commands and Administrative Tasks

Testing and troubleshooting

This feature helps to reduce the POST failure rates for a particular modem module. The unit’s modem modules boots every time the unit power-cycles, and requires boot-up configuration data from the unit. If the first boot-up fails, the unit makes two further attempt s to download the code for the unit’s modem modules.

MAX Administration Guide 2-11

Terminal-Server Administrative Tasks

Enabling and configuring the interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Navigating to and from the interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Testing the MAX unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Starting remote management sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Disconnecting user Telnet connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Using Set commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Enable password mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Using Show commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

You can enable and configure the terminal-server command-line interface from a MAX unit’s VT100 interface. You access the terminal-server command-line interface through the DO command menu, the same interface that you use to specify administrative permissions, described in “Activating adminis trative p e rmi ssions” on page 2-1. Use the terminal-server command-line interface to test the MAX unit, initiate remote management sessions, disconnect user Telnet connections, administer passwords, and display information about the unit’s configuration and performance.

For introductory information about navigation and MAX user interfaces, including the terminal-server command-line interface, see the Hardware Installation and Basic Configuration Gu ide for your MAX unit.

Enabling and configuring the interface

The TSEnabled parameter, in the TServ Options profile, enables or disables terminal services. Terminal services must be enabled to support incoming calls from analog modems or V.120 terminal adapters. If you are unable to access the terminal-server command-line interface, you must verify that the TSEnabled parameter is set to Yes. For example:

90-900 Mod Config

TServ Options

>TS Enabled=Yes

Passwd=*SECURE* Banner=** Pipeline Terminal Server** Login Prompt=Login: Passwd Prompt=Password: Prompt=ascend%

MAX Administration Guide 3-1

…

Terminal-Server Administrative Tasks

Enabling and configuri ng the int er fac e

Prompt Format=No Term Type=vt100 Host #1 Service = Telnet Host #2 Service = Rlogin Host #3 Service = Telnet Host #4 Service = Telnet Host #1 Port = 50 Host #2 Port = 51 Host #3 Port = 52 Host #4 Port = 53 Host #1 User = Rangie Host #2 User = Disco Host #3 User = D90 Host #4 User = SII

Configuring the interface

Once you have enabled the terminal-server command-line interface, configure the interface with the Banner, Login Prompt, Prompt, Prompt format, and Term Type parameters in the TServ Options profile, in the Mod Config menu. By using these parameters, you control the appearance of the terminal-server command-line inter face. For examp le, the users of the MAX

unit’s terminal-server command-line interface may have unique terminology that it would be helpful for you to use. Use these parameters to welcome the user to a part of your organization’s network that serves a particular function, cue the user that the command-line interface serves a particular group in your organization, or that the command-line interface serves a particular class of user outside of your organization.

The terminal-server menu provides the user with the options of beginning a Telnet, PPP, Rlogin, or Raw TCP session. You can specify the PPP option anywhere in the menu. For Telnet, Raw TCP, and Rlogin, the host authenticates the session. For PPP, the MAX unit authenticates the session.

Table 3-1 summarizes the TServ Options parameters that enable you to configure the terminal-server command-line interface.

Table 3-1. TS erv Options parameters

Parameter Description

Banner Specifies the text to be used as the terminal-server login

banner. Enter up to 84 alphanumeric characters, as in the following example:

Banner=Welcome to Your Organization

Following is an example of the default banner setting:

** Pipeline Terminal Server **

3-2 MAX Administration Guide

Terminal-Server Administrative Tasks

Enabling and configuring the interface

Table 3-1. TS erv Options parameters (continued)

Parameter Description

authentication is in use and an interactive user initiates a connection. If the Prompt Format parameter is set to include multiple lines in the login prompt by including carriage-return/line-feed (\n) and tab (\t) characters. To include an actual backslash character, you must another backslash. For example, you enter the string:

Welcome to\n\t\\\Ascend Remote Server\\\nEnter your user name:

to display the following text as a login prompt:

Welcome to \\Ascend Remote Server\\ Enter your user name:

Prompt Specifies the prompt the MAX unit displays during a termi-

nal-server session. Specify a string containing up to 15 characters. The default is

ascend%

escape

Yes

it with

Prompt Format Determines whether you are able to use the multiline format

for the terminal-server login prompt.

Term Type Specifies the default terminal type for Telnet and Rlogin

sessions. Enter up to 15 characters. The default is

Configuring the Session Options profile

Connections that are idle but continue to be connected present a potential point of entry for

unauthorized use of your network’s resources. Administer terminal-server idle-time limits by specifying the settings of the parameters shown in Table 3-2, in the Session Options profile, which is included in the Connections profile. Specifying these parameters allows you to assure that resources are allocated to user connections that are currently active and not to those that are inactive, which helps maintain the security of the unit.

Table 3-2 summarizes the Session Options parameters that yo u use to configure idle-time parameters in the Session Options profile.

Table 3-2. Session Options parameters

Parameter Description

TS Idle Specifies the number of seconds that a terminal-server con-

nection must be idle before the MAX unit disconnects the session.

vt100

TS Idle Mode Specifies whether the MAX unit uses the terminal-server

idle-timer and, if so , whether both th e user and host must be idle before the unit disconnects the session.

MAX Administration Guide 3-3

Terminal-Server Administrative Tasks

Navigating to and from the interface

Start a terminal-server command-line interface session if you have administrative privileges.

(For more information, see “Activating administrative permissions” on page 2-1.) Start a session using one of the following meth ods:

• From the main VT100 interface menu, select System > Sys Diag > Term Serv, and press Enter.

• In the Main Edit Menu, press Ctrl-D to open the DO menu, and select

• Enter the following keystroke sequence (Escape key, left bracket, Escape key, zero) in rapid succession:

Esc [ Esc 0

If you have sufficient privileges to invoke the command line, the MAX unit displays a command-line prompt. For example:

** Pipeline Terminal Server ** ascend%

Note: If y ou have a MAX unit running Multiband simulation, the following terminal-server commands are disabled: Close, Ipxping, Open, Resume, Rlogin, Telnet.

The commands in Table 3-3 close the terminal-server command-line interface and return the cursor to the VT100 interface.

Table 3-3. Returning to the VT100 interface

Command Description

Quit Closes the terminal-server command-line interface

session.

Hangup Closes terminal-server command-line interface ses-

sion.

E=Termserv

Local Go to Local mode, a data-transfer mode for calls on

an X.25/T3POS network. In Local mode, error recovery is performed locally. The MAX unit does not send supervisory frames (ACKs and NAKs) across the X.25 network. The T3POS PAD is responsible for sending supervisory frames to the T3POS Data Terminal Equipment (DTE).

Testing the MAX unit

Test the MAX unit through the terminal-server command-line interface by using the Test command. Using the Test command open channels to run a test (sometimes called a self-test) in which the unit calls itself. The unit places the call on one channel and receives it on another channel. Here is a simple example of entering the Test command:

ascend% test 555-1212

3-4 MAX Administration Guide

Terminal-Server Administrative Tasks

Testing the MAX unit

Press Ctrl-C at any time to terminate the test. While the test is running, the MAX unit displays the status. For example:

calling...answering...testing...end 200 packets sent, 200 packets received

The Test command has the following format:

test phonenumber [frame-count] [optional fields]

The table below summarizes the one required and the one optional argument that you can include in your Test command

Argument Specifies

phonenumber

[Frame-count]

There are four optional fields that you may specify in addition to the arguments above. If you do not specify a value, the default value is that specified by the corresponding parameter in the Connection profile. For a information about valid settings for the parameters in the Connection profile, see the MAX Reference. The table below summarizes the four optional fields that you can include in your Test command:

Optional field Specifies

[data-svc=

[call-by-call=

data-svc

]

T1-PRI-service

The telephone number of the channel receiving the test call. This can include the numbers 0 through 9 and the characters ()[]-, but cannot include spaces.

The optional frame-count argument is a number from 1 to 65535 and specifies the number of frames to send during the test. The default is

100

A data service identical to any of the values available for the Data Svc parameter.

A data service is provided over a WAN line and is characterized by the unit measure of its bandwidth. A data service can transmit either data or digitized voice. In a Connection profile, Data Svc specifies the type of data service the link uses.

Note: Because FT1 calls do not include switched services, the Data Svc parameter lists only

Call Type=FT1

how much bandwidth the unit routes to the host for each channel in the connection. When Call Type=FT1-AIM, the Data Svc parameter refers to the switched channels.

] Any value available to the Call by Call parameter.

In a connection profile, Call-by-Call specifies the PRI service to use when placing a call using that profile.

56KR

; in this context, the Data Svc setting indicates

Call Type=FT1-B&O

and

64K

when

MAX Administration Guide 3-5

Terminal-Server Administrative Tasks

Understanding test results

Optional field Specifies

[primary-number-type=

[transit-number=

AT&T-switch

ECI

]

Any value available to the PRI # Type parameter. The PRI # Type parameter specifies a switch type.

PRI # Type is used for outbound calls made by the MAX on PRI lines so that the switch can properly interpret the phone number dialed. Ask your PRI provider for details on when to use each of the following settings. This parameter specifies the TypeOfNumber field in the called party’s information element.

Note: The value you specify for PRI # Type in the Dial Plan profile overrides the value of PRI # Type in the Call profile and Connection profile if you have enabled the unit’s Dial Plan profiles.

Any value available to the Transit # parameter. Specifies a string for use in the transit network IE for PRI calling

when going through an Interexchange Carrier (IEC). The default (null) causes the MAX to use any available IEC for long-distance calls.

Note: The Transit # value in the Dial Plan profile overrides the Transit # value in the Call profile or the Connection profile. This parameter does not apply to nailed connections.

Understanding test results

MAX 6000 and MAX 3000 units that su ppo rt T1 ( or E1 ) us e the f i rst available T1 (or E1) line unless you enable the Use Trunk Grps parameter in the Sys Config menu.

If you enable the Use T r unk Grps param eter in t he Sys Confi g menu, sp ecify the outgo ing lines to be used in the test. The Use Trunk Grps parameter specifies the use of trunk groups for all network lines. When trunk groups are in use, channels must be assigned trunk group numbers to be available for outbound calls. In turn, when this parameter is set to configurations must specify trunk-group assignments. For more information about each of these parameters, see the MAX Reference.

The unit generates an error message for any condition that causes the test to terminate before sending the full number of packets. The following error messages can appear:

Message Explanation

bad digits in phone number

call failed The unit did not answer the outgoing call. Can indicate a

Yes

, channel

The telephone number you specified contained a character other than the numbers 0 through 9 and the characters

()[]-.

wrong telephone numb er or a busy telepho ne numb er. Use the Show ISDN command to determine the nature of the failure.

3-6 MAX Administration Guide

Message Explanation

call terminated packets sent received

cannot handshake

frame-count must be in the range 1-65535

no phone number

test aborted unit busy

unknown items on command-line

unknown option

unknown value

wrong phone number

packets

option

value

This message indicates the number of packets sent (N1) and received (N2).

The MAX answered the outgoing call, but the two sides did not properly identify themselves. Can indicate that the call was routed to t h e wron g MAX m odu l e or t hat t he te lephone number was incorrect.

The number of frames requested exceeded 65535.

You did not specify a telephone number on the command line.

The test was terminated (Ctrl-C). You attempted to start another test when one was already

in progress. Run only one self-test at a time. The command line contained unknown items. Inserting

one or more spaces in the telephone number can generate this error.

The command-line contained the option specified by option, which is invalid.

The command-line contained the value specified by value, which is invalid.

A device other than the MAX answered the call. Therefore, the telephone number you specified was incorrect.

Terminal-Server Administrative Tasks

Starting remote management sessions

Multilink Protocol Plus (MP+) uses Point-to-Point Protocol (PPP) encapsulation with Lucent-specific extensions, as described in RFC 1 934, to extend the capabilities of Multilink Protocol (MP). MP+ supports session and bandwidth management, enabling the MAX unit to connect to another unit by means of multiple channels. After an MP+ conn ection has been established with a remote station (for example, by using the DO Dial command), start a remote management session with that station by entering the Remote command in the following format:

remote

For example:

ascend% remote lab17gw

During the remote management session, the user interface of the remote device replaces your local user interface, as if you had opened a Telnet connection to the device. Enter Ctrl-\ at any time to terminate the remote session. Either end of an MP+ link can terminate the ses sio n by hanging up all channels of the connection.

station

MAX Administration Guide 3-7

Terminal-Server Administrative Tasks

Starting remote management sessions

The argument to the Remote command is the name of the remote station. It must match the value of a Station parameter in a Connection profile that allows outgoing MP+ calls or the

user-id

Note: A remote management session can time out because the traffic it generates does not reset the idle-timer. Therefore, the Idle parameter in the Connection profile at both the calling and answering ends of the connection should be di sabled dur ing a remo te manage ment sessio n and restored just before exiting. Remote management works best at higher terminal speeds.

At the beginning of a remote management session, you have privileges set by the default Security profile at the remote end of the connection. To activate administrative privileges on the remote station, activate the appropriate remote Security profile by using the DO Password

command (as described in “Activating administrative permissions” on page 2-1). The MAX unit generates an error message for any condition that causes the test to terminate

before sending the full number of packets. The following error messages can appear:

Message Explanation

not authorized

cannot find profile for <station>

profile for <station> does not specify MPP

cannot establish connection for <station>

<station> did not negotiate MPP

far end does not support remote management

management session failed

far end rejected session

at the start of a RADIUS profile set up for outgoing calls.

Y ou r current security privileges are insuff icient for beginning a r emote management session. To assign yourself the required privileges, log in with the DO Password command to a Security profile whose Edit System parameter is set to

The MAX could not locate a local Connection profile containing a S tation parameter whose value matched <station>.

The local Connection profile containing a Station value equal to <station> did not contain

The MAX located a local Connection profile containing the proper Station and Encaps settings, but it could not complete the connection to the remote station.

The remote station did not negotiate an MP+ connection. This error occurs most often when the remote station does not support MP+, but does support PPP.

The remote station is running a version of MP+ that does not support remote management.

A temporary condition, such as premature termination of the connection, caused the management session to fail.

The remote station was configured to reject remote management; its Remote Mgmt parameter was set to No in the System profile.

Yes

Encaps=MPP

3-8 MAX Administration Guide

Terminal-Server Administrative Tasks

Disconnecting user Telnet connections

To disconnect a specified user’s Telnet connection use the terminal-server command-line interface. Disconnect the user by specifying the session ID. The resulting disconnect code is identical to the RADIUS disconnect code, allowing you to track all administrative disconnects. To terminate a Telnet session, enter the command as follows:

kill session ID

where

session ID

the preceding section. The reported disconnect cause is DIS_LOCAL_ADMIN. The active Security profile must have Edit All Calls set to message appears when you enter the Kill command:

Insufficient security level for that operation.

When the session is properly terminated, a message similar to the following appears:

Session 216747095 killed.

When the session is not terminated, a caution similar to the following appears:

Unable to kill session 216747095.

is the session ID as displayed by the Show Users comman d described in

Yes

Edit All Calls=No

. If

, the following

Using Set commands

The MAX unit supports administrative Set commands such as Set All, Set Term, and Set Password. To display all of the Set commands, enter the Set ? (command with a question mark), as in the following example:

ascend% set ?

Use the Set All command to display the current settings. For example:

ascend% set all term = vt100

dynamic password serving = disabled

Enable password mode

The Set Password command puts the terminal-server in password mode, in which a Security Dynamics ACE/Server or Enigma Logic SafeWord server at a secure site can display password challenges dynamically in the terminal-server command-line interface.

Dynamics ACE/Servers use ACE authentication, a form of token-card authen tication in which RADIUS forwards a connection request to a Security Dynamics ACE/Server. The ACE/Server sends an Access-Challenge packet back through the RADIUS server and the MAX unit to the user who is dialing in. The user sees the challenge message, obtains the current token from the card, and enters the token. A token is a type of password that travels back through the MAX unit and the RADIUS server to the ACE/Server. The ACE/Server sends a response to the RADIUS server specifying whether the user has entered the pro per user name an d token. If the user enters an incorrect token, the ACE/Server returns another challenge, and the user can again attempt to enter the correct token. The server sends up to three challenges. After three

MAX Administration Guide 3-9

Terminal-Server Administrative Tasks

Using Show commands

incorrect tries, the MAX terminates the call. (ACE authentication is also known as SecurID authentication.)

Enigma Logic SafeWord servers use SafeWord authentication, a form of token-card authentication in which RADIUS forwards a connection request to an Enigma Logic SafeWord server. The ser ver sends an Access-Challenge p acket back throu gh the R ADIUS server an d the MAX unit to the user dialing in. The user sees the challenge message, obtains the current password from his or her token card, and enters th e current password (also called a token ). The token travels back through the MAX unit and the RADIUS server to the SafeWord server. The SafeWord server sends a response to the RADIUS server, specifying whether the user has entered the proper user name and token. If the user enters an incorrect token, the SafeWord server returns another challenge, and the user can again attemp t to enter the correct to ken. The server sends up to three challenges. After three incorrect entries, the MAX unit terminates the call.

When the terminal-server is in password mode, it passively waits for password challenges from a remote Security Dynamics ACE/Server or Enigma Logic SafeWord server. The Set Password command applies only when the MAX unit uses security card authentication. Enter the command as follows:

ascend% set password Entering Password Mode...

[^C to exit] Password Mode>

Press Ctrl-C to return to normal terminal-server command-line in terface operations and disable Password Mode.

Each channel of a connection to a secure site requires a separate password challenge, so for multichannel connections to a secure site, you must leave the terminal-server command-line interface in password mode until all channels have been established.

The Ascend Password Protocol (APP) Server utility provides an alternative way to allow users to respond to dynamic password challenges obtained from hand-held security cards. The APP Server utility also enables a user to respond to password challenges received from an external authentication server, such as an ACE/Server or SafeWord server. To allow a user to supply a password from a host on the local network, you must configure the MAX unit to co mmun i cate with the APP Server utility on that host.

Using Show commands

Use Show commands to see uptime and revision information, modem and V.110 card status, Dialed Number Information Service (DNIS) activity, and information about filters.

Displaying uptime and revision

To see how long the MAX unit has been running, enter the Show Uptime command. For example:

ascend% show uptime system uptime: up 2 days, 4 hours, 38 minutes, 43 seconds

3-10 MAX Administration Guide

If the MAX unit stays up for 1000 consecutive days with no power cycles, the number of days displayed resets to zero and begins to increment again.

The Show Revision command displays the software load and version number currently running on the MAX unit. For example:

ascend% show revision MAX-6000-L1 system revision: tck.m60 8.0.0

Displaying modem status

Use the Show Modems command, in the terminal-server command-line interface, to display modem status on a MAX 6000 or MAX 3000. You use this information to determine which modems and V.110 terminal adaptors are online or o ff line. This can help when troubleshoo ting the unit.

In the Main Edit menu, you see modems that are installed in the MAX 6000 unit, as in the following example:

Main Edit Menu

00-000 System 10-000 Net/T1 20-000 Net/T1

>30-000 K56 Modem-16

Terminal-Server Administrative Tasks

Using Show commands

Enter the Show Modems command to display modem activity. For example, the following output is from a unit with a V.90 K56 II modem card in slot 7:

ascend% show modems slot:item modem status

7: 1 1 online 7: 2 2 online 7: 3 3 online 7: 4 4 idle 7: 5 5 idle 7: 6 6 idle ... ... 7: 23 23 idle 7: 24 24 idle

For 12-MOD K56Flex modem slot cards, the numbering is not sequential, but the numbering does not affect functionality. As another example, if you have a 12-MOD modem card in Slot 8 in a MAX unit, the Show Modems command in the terminal-server command-line interface displays the following output:

ascend% show modems slot:item modem status

8:0 1 idle 8:1 2 idle 8:2 3 idle 8:3 4 idle 8:4 5 idle 8:5 6 idle

MAX Administration Guide 3-11

Terminal-Server Administrative Tasks

Using Show commands

8:6 7 idle 8:7 8 idle 8:8 9 idle 8:9 10 idle 8:12 11 idle 8:13 12 idle

Though there are several supported types of modems, all modems respond using the same fields of information. For example, the MAX 3000 unit supports V.90 S56 III Modem-30 and V.90 S56 III Modem-24 modems. The output of the show modems command is much the same as in the preceding example. However there are more modems and slots to display.

Table 3-4 describes each field and its output means.

Table 3-4. Output of Show Modems command

Field Description

slot item

modem

status

The slot and port number of the modem. For example, 8:1 indicates the first port on the digital modem card installed in slot 8.

The SNMP interface number of each modem. Modem status , which can be one of the following strings:

idle

—The modem is not in use.

awaiting DCD

(DCD). DCD is a signal sent from a modem to a host, indicating that the modem is online.

awaiting codes

nal or modem is waiting for modem result codes.

online initializing

—The call is up. The modem can now send and receive data.

—The call is up and waiting for Data Carrier Detect

—The modem is being reset.

Displaying V.110 terminal adapter status

Use the Show V.100 command, using the terminal-server command-line interface, to display V.110 terminal adapter status on a MAX 6000 or MAX 3000, if you installed any V.110 terminal adapters on the unit. V.110 is a rate-adaptive standard based on fixed frames, that subdivides an ISDN channel so that it can carry one lower-speed data channel. V.110 terminal adapters make asynchronous calls with CCITT V.110 encapsulation. These calls require V.110 modem processing.

—The DCD signal has been sent, and the termi-

An asynchronous device, such as an ISDN terminal adapter, encapsulates its data in V.110. A V.110 card provides eight V.110 modems that each enable the MAX unit to communicate with an asynchronous device over synchronous digital lines.

To display the status of the MAX unit’s V.110 terminal adapters, enter the Show V.110 command, as follows:

ascend% show v.110s slot:item v.110s status

3-12 MAX Administration Guide

4:1 1 in use 4:2 2 in use 4:3 3 in use 4:4 4 open issued 4:5 5 carrier detected 4:6 6 session closed 4:7 7 idle 4:8 8 in use

V.110 terminal adapters make asynchronous calls with CCITT V.110 encapsulation. These calls require V.110 modem processing. A V.110 card provides eight V.110 modems that each enable the MAX unit to communicate with an asynchronous device over synchronous digital lines. An asynchronous device such as an ISDN modem encapsulates its data in V.110. The V.110 module in the MAX 3000 unit (only) removes the encapsulation and enables an asynchronous session (a type of terminal-server session).

Displaying call and user activity

Use the terminal-server command-line interface to display call and user activity on the MAX unit. The Show Calls command displays information about active calls on a German 1TR6 (a German ISDN switch standard) or Japanese NTT (Nippon Telephone and Telegraph) switch type. For example:

ascend% show calls Call ID Called Party ID Calling Party ID InOctets OutOctets 3 5104563434 4191234567 0 0

4 4197654321 5108888888 888888 99999

Terminal-Server Administrative Tasks

Using Show commands

Table 3-5 describes the output included in each of the fields of output.

Table 3-5. Show calls output

Field Description

CallID

CalledPartyID

CallingPartyID

InOctets The total number of octets received by the user from the moment the call begins

OutOctets The total number of octets sent by the user from the moment the call begins until

An identifier for the call. The telephone number of the answering device (that is, this u nit). This ID is

obtained from La yer 3 protocol m essages during call setup. The telephone number of the caller. This ID is obtained from layer 3 protocol

messages during call setup.

until it is cleared.

it is cleared.

Displaying active sessions

Displaying active sessions al lows you to gather in format ion about active sess ions on the MAX unit. Use the Show Users command, in the terminal-server command-line interface, to see

MAX Administration Guide 3-13

Terminal-Server Administrative Tasks

Using Show commands

information about the performance of incoming and outgoing calls. Use the command to display the identification of the line, slot , rates, se rvice ty pe, host information, and user.

Display the active sessions by entering the Show Users command as in the following example:

ascend% show users I Session Line: Slot: Tx Rx Service Host User

O ID Chan Port Data Rate Type[mpID] Address Name O 231849873 1:1 9:1 56K 56K MPP[1] 10.10.68.2 jdoe I 231849874 1:3 3:1 28800 33600 Termsrv N/A Modem 3:1 O 214933581 1:2 9:2 56K 56K MPP[1] 10.10.4.9 arwp50 O 214933582 1:6 9:3 56K 56K MPP[1] MPP Bundle arwp50

Table 3-6 summarizes the output of the Show Users command.

Table 3-6. Show Users command output

Field Content

Session ID

Line:Chan

Slot: Port

Tx Data

Rx Rate

Service Type

I for an incoming call or O for an outgoing call. Unique session-ID. This is the same as Acct-Session-ID in

RADIUS. Line and channel on which the session is established. Slot and port of the service being used by the session. Can indicate

the number of a slot containing a modem card, and the modem on

that card. Or can indicate the virtual slot of the MAX unit’s bridge/router, in which case the port indicator shows the virtual interfaces to bridge/router starting with 1 for the first session of a multichannel session.

Transmit data rate in bits per second. Receive data rate in bits per second. Type of session, which can be

col name

For MP and

MPP (MPT

), shows the bundle ID shared by the calls in

terminal-server

a multichannel session. The special values document the progress of a session.

Initial

identifies sessions

or a

and

proto-

that do not yet have a protocol assigned. Login identifies sessions during the login process.

Host Address Network address of the host originatin g the session.

For some sessions this field is N/A. For outgoing MPP sessions only, the first connection has a valid network address associated with it. All other connections in the bundle have the network address listed as MPP Bundle.

3-14 MAX Administration Guide

Terminal-Server Administrative Tasks

Table 3-6. Show Users command output (continued)

Field Content

Using Show commands

User Name

The station name associated with the session. Initially, the value is

Answer

host. For terminal-server command-line interface sessions User Name is the login name. Before completion of login, the field contains the string respectively, of the modem servicing the session.

, which is usually replaced with the name of the remote

modem x:y

where x and y are the slot and port,

Displaying Dialed Number Information Service activity

To display Dialed Number Information Service (DNIS) activity on the MAX unit, use the terminal-server command-line interface. DNIS is a telephone company service that provides information about the called number, such as the name and location of the target user or unit. To display active DNIS sessions, enter the Show DNIS Session command:

ascend% show dnis session

GLOBAL MODEM HDLC V110

DNIS# Used/Max Used/Max Used/Max Used/Max

0. Unspecified 0/999 0/1 0/0 0/0

1. 68149 0/123 0/456 0/1 0/0

2. 8867764 0/1 0/1 0/1 0/1

3. 45566778800 0/0 0/0 0/0 0/0

4. 0/0 0/0 0/0 0/0

5. 0/0 0/0 0/0 0/0

6. 0/0 0/0 0/0 0/0

7. 0/0 0/0 0/0 0/0

8. 0/0 0/0 0/0 0/0

9. 0/0 0/0 0/0 0/0

10. 0/0 0/0 0/0 0/0

11. 0/0 0/0 0/0 0/0

12. 0/0 0/0 0/0 0/0

13. 0/0 0/0 0/0 0/0

14. 0/0 0/0 0/0 0/0

15. 0/0 0/0 0/0 0/0

16. 0/0 0/0 0/0 0/0

In the output:

• DNIS#—Displays up to eleven digits of the DNIS number. In the case that the DNIS number contains more than eleven digits, the table displays the last eleven digits.

• Used—Indicates the number of active sessions to the specified DNIS number.

• Max—Indicates the value specified in the Ethernet > Mod Config > DNIS options submenu.

If Ethernet > Mod Config > DNIS options > DNIS Limitation=No, and you enter the Show DNIS Sessions command, the MAX unit displays the following message:

DNIS Inactive

MAX Administration Guide 3-15

Terminal-Server Administrative Tasks

Using Show commands

To display DNIS session statistics, enter the Show DNIS Statistics com m a nd:

ascend% show dnis statistics

DNIS# Tot/Accept Tot/Accept Tot/Accept Tot/Accept

0. Unspecified 10/9 0/0 0/0 0/0

1. 68149 0/0 8/8 4/4 0/0

2. 8867764 0/0 0/0 0/0 0/0

3. 45566778800 0/0 0/0 0/0 0/0

4. 0/0 0/0 0/0 0/0

5. 0/0 0/0 0/0 0/0

6. 0/0 0/0 0/0 0/0

7. 0/0 0/0 0/0 0/0

8. 0/0 0/0 0/0 0/0

9. 0/0 0/0 0/0 0/0

10. 0/0 0/0 0/0 0/0

11. 0/0 0/0 0/0 0/0

12. 0/0 0/0 0/0 0/0

13. 0/0 0/0 0/0 0/0

14. 0/0 0/0 0/0 0/0

15. 0/0 0/0 0/0 0/0

16. 0/0 0/0 0/0 0/0

GLOBAL MODEM HDLC V110

In the output:

• Global—Incoming calls using unspecified resources.

• Modem—In coming calls using modem resources.

• HDLC—Incoming calls using an High level Data Link Control (HDLC) resource.

• V110—Incoming calls using a V110 resource.

DNIS#

•

Note: A counter resets when it reaches 10,000, or when you enter the Clear DNIS Statistics command.

If Ethernet > Mod Config > DNIS options > Show DNIS Statistics command, the MAX unit displays the followin g message:

DNIS Inactive

To clear DNIS session statistics, enter the Clear DNIS Statistics command. The MAX unit displays the following message:

Clearing all DNIS Statistics...

—Displays up to eleven digits of the DNIS number.

Tot

—indicates the number of calls received by the specified DNIS number.

—Specifies the total number of calls accepted by the specified DNIS number.

DNIS Limitation=No

, and you enter the

3-16 MAX Administration Guide

Terminal-Server Administrative Tasks

Using Show commands

The commands summarized in Table 3-7 are tools for managing DNIS sessions with MAX units.

Table 3-7. DO menu commands for specific protocols

Command Description

show dnis session

show dnis statistics

Using the Show Filters command

From the terminal server, enter the Show Filters command to display a list of the filters in use by sessions active on the MAX unit and display details about individual filters. For information about configuring filters, see the Network C on figuration Guide for your unit.

Listing the filters in use

From the terminal-server, enter the Show Filters command to display a list of the filters in use by sessions active on the MAX unit. Sessions authenticated by local profiles appear with their associated filter numbers as specified in their Connection profiles. Externally authenticated sessions, such as RADIUS sessions, have no associated filter names or numbers, so they appear with blank fields (indicated by hyphens). For example:

** Example Terminal Server Banner ** ascend% show filters ID Username Src Data-Filter Call-Filter Ipx-Filter TOS-Filter

----------------------------------------------------------------------

000 tnt2max1 loc 0 0 0 0 001 tnt2max2 loc 1 3 1 0 002 edmax ext - - - - 003 tnt2max4 loc 0 0 0 0 ascend%

Display active DNIS sessions. Display DNIS statistics.

The first three columns in the output provide the following information:

Column Information

ID Indicates an identification number for the active user. Username Name for the active user. Src Indicates the source of the profile, that is, whether it is downloaded through

RADIUS (ext) or is a local profile (loc).

MAX Administration Guide 3-17

Terminal-Server Administrative Tasks

Using Show commands

The filter numbers appear in the last four columns, each of which is for a particular type of filter, as follows:

Column Type of filter

Data-Filter Packet filter that defines which packets the MAX unit can transm it

on a connection.

Call-Filter Packet filter that defines which packets can bring up a connection or reset the

idle-timer for an established link.

IPX-Filter S ervice Advertising Protocol (SAP) filter. Determines which SAP advertise-

ments the MAX unit forwards or drops.

TOS-Filter Type-of-Service filter. Enables you to specify many of the same values as an

IP filter, and also to specify a precedence and TOS value.

Displaying filter details

To display the filter details for a particular session, include the filter ID in the Show Filters command:

show filters

where

is the number shown in the ID column above. For example:

ascend% show filters

Hostname: tnt2max1 ********************************************** Data Filter Direction: In

-----------------------------

Forward = yes Type = Generic Filter offset = 0 len = 8 more = no comp-neq = yes dummyForPadding = 0 mask = ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00 value = 12:31:23:12:30:00:00:00:00:00:00:00 ********************************************** Data Filter Direction: Out

-----------------------------

Forward = yes Type = Generic Filter offset = 0 len = 0 more = no comp-neq = no dummyForPadding = 0 mask = 00:00:00:00:00:00:00:00:00:00:00:00 value = 00:00:00:00:00:00:00:00:00:00:00:00 **********************************************

000

3-18 MAX Administration Guide

Terminal-Server Administrative Tasks

Using Show commands

Call Filter Direction: In

-----------------------------

Forward = no Type = Generic Filter offset = 0 len = 0 more = no comp-neq = no dummyForPadding = 0 mask = 00:00:00:00:00:00:00:00:00:00:00:00 value = 00:00:00:00:00:00:00:00:00:00:00:00 ********************************************** Call Filter Direction: Out

-----------------------------

Forward = no Type = Generic Filter offset = 12 len = 8 more = yes comp-neq = no dummyForPadding = 0 mask = 00:00:ff:ff:ff:00:00:00:ff:ff:00:00 value = 00:00:aa:aa:03:00:00:00:80:9b:00:00

-----------------------------

Forward = no Type = Generic Filter offset = 32 len = 3 more = no comp-neq = no dummyForPadding = 0 mask = ff:ff:ff:00:00:00:00:00:00:00:00:00

value = 04:04:04:00:00:00:00:00:00:00:00:00

-----------------------------

Forward = no Type = Generic Filter offset = 12 len = 2 more = yes comp-neq = no dummyForPadding = 0 mask = ff:ff:00:00:00:00:00:00:00:00:00:00 value = 80:9b:00:00:00:00:00:00:00:00:00:00

-----------------------------

Forward = no Type = Generic Filter offset = 24 len = 3 more = no comp-neq = no

MAX Administration Guide 3-19

Terminal-Server Administrative Tasks

Using Show commands

dummyForPadding = 0 mask = ff:ff:ff:00:00:00:00:00:00:00:00:00 value = 04:04:04:00:00:00:00:00:00:00:00:00

-----------------------------

Type-filter: exclude Server Type: 2123 Server Name: doom

-----------------------------

Type-filter: exclude Server Type: 1116 Server Name: zyst

-----------------------------

Type-filter: include Server Type: 9320 Server Name: abcde ********************************************** Ipx Sap Filter Direction: Out

-----------------------------

Type-filter: include Server Type: 1112 Server Name: nowhere

In the previous example, using the Show Filters 000 command dis plays Data-Filter #000, Call-Filter #3, Ipx-Filter #1, and no TOS filters. The Filters submenu, in the Ethernet menu, can include up to twelve filter profiles. When you go into the individual Filter profile, assign any combination of input or output filters up to twelve. In this example, Data-Filter #1 includes an input and an output filter. Call-Filter #3 includes one input filter and several output filters. Ipx-Filter #1 includes three input filters and one output filter.

3-20 MAX Administration Guide

Terminal-Server Administrative Tasks

Displaying information related to virtual routing

The following Show commands suppo rt virtual rou t ing. If you do not specify a VRouter name on the terminal server command line, the MAX unit displays global VRouter information. If you specify a VRouter name, the unit displays infor mat i on abou t th e specifi ed VRou ter.

Command Syntax with optional VRouter argument s

IPRoutes IPStats IPaddress ICMP UDP

TCP

Pools

show iproutes [-r vrouterName] [dest] show ip stats [[-r] vrouterName] show ip address [[-r] vrouterName] [all] show icmp [[-r] vrouterName] show udp stats [[-r] vrouterName] show udp listen [[-r] vrouterName]

show tcp stats [[-r] vrouterName] show tcp connection [[-r] vrouterName]

show pools [[-r] vrouterName]

Using Show commands

For more information about administering virtual routing, see “Using VRouter-related terminal-server commands” on page 7-15.

MAX Administration Guide 3-21

Changing System Software Versions

Preparing to change system software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Using TFTP to upgrade or downgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Using the serial port to upgrade or downgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Restoring correct RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Notice of discontinuance of configurable RADIUS port and ID space. . . . . . . . . . . . . 4-9

Caution: When you upgrade a MAX unit’s version of TAOS, the newer version might use a

configuration file format that is incompatible with the version that preceded it. The upgrade process automatically converts the unit’s configuration file to the newer format. You need a backup copy of the configuration file in the older format in case it ever becomes necessary to revert back to a previous version of TAOS. If you fail to create and save a backup copy of the configuration before your change a MAX unit’s version of TAOS, you might lose all configuration informat i on.

Caution: If possible use TFTP to change a MAX unit’s version of TAOS. TFTP is the most reliable way to obtain, store, and then change the version of TAOS.

Caution:

memory available to the MAX 6000 unit only by way of an external PCMCIA flash card. (This does not apply to MAX 3000 and MAX 800 units.)

Before you begin to change a MAX unit’s system software, you must enable the unit’s Field Service and Operations parameters. You must also verify that you are staying with the same build of the software. In addition to knowing th e VT100 inter face, you must be p repared to use the DO Command menu, as described in Chapter 2, “DO Commands and Administrative Tasks,” to access the diagnostics commands that you use to upgrade or downgrade the unit’s system software.

Note: Changing the system software is an exceptional situatio n in this regard. Under most circumstances, diagnostics commands are not required for correct operation of the MAX unit.

The standard software files you use to upgrade to TAOS 9.0 require additional flash

Trivial File Transfer Protocol (TFTP) provides a more reliable way to obtain, store, and install the system software to your unit than is the alternative, which is throu gh the serial port of the unit.

MAX Administration Guide 4-1

Changing System Software Versions

Preparing to change system software

As you prepare to change the system software on a MAX unit, you must verify that Field Service and Operations are enabled on the unit. When upgrading, try to stay with the same build. But you can use an alternative build to avoid having to add memory. You can use the memory provided by a MAX 6000 unit’s external PCMCIA card as you change system

software. No additional memory is required on a MAX 3000 or MAX 800 units.

Enabling Field Service and Operations parameters

The Field Service paramet er, in the Security profile, enables or di s abl es perm i ssi on to perform Lucent-specific field service operations, such as changing the operating system software on a MAX unit. The Field Service parameter is not applicable if the Operations parameter, also in the Security profile, is set to No. Before you begin the process of changing the unit’s version of T AOS, make sure that both parameters are set to Yes in the administrating Security profile. For example, the following Full Access security profile of a MAX 800 unit is corr ectly conf igur ed to support a change of operating system software:

00-300 Security

00-303 Full Access >Name=Full Access

Passwd=*SECURE* Operations=Yes Edit Security=Yes Edit System=Yes Field Service=Yes

Staying with the same software build

When a particular build of the system software is updated, it retains the same filename. If possible, you should always stay with the same build when you upgrade or downgrade. If you install a different build, your unit can lose its configuration. If this happens, you might need to manually restore your configuration. There can be no automated way to restore configuration data from a backup when changing builds since, if the file formats between the builds are incompatible, no suitable backup exists. For example, your MAX unit might have a T1 interface. If you are attempting to transfer a build that is appropriate for an E1 interface, the unit can display the following message:

This load appears not to support your network interface. Download aborted. Use

If this happens, verify that you have selected the correct build. If the build is intended for another type of unit, that you forcing the download is not recommended.

tloadcode -f

Alternative builds for a MAX 6000 unit

With two exceptions, the builds you can use to upgrade to TAOS 9.0 require additional flash memory, which is available to the MAX 6000 unit only, by way of an external PCMCIA flash card. (The builds for MAX 3000 and MAX 800 units do not require any additional flash

to force.

4-2 MAX Administration Guide

Changing System Software Versions

Using TFTP to upgrade or downgrade

memory .) To avoid using a PCMCIA flash card, you can upgrad e a MAX 6000 unit with one of the following two recommended builds:

• eik.m60 (an ultrathin load for E1 environments)

• tik.m60 (an ultrathin load for T1 environments)

In future releases, these ultrathin builds might not be available, and use of the MAX 6000 unit’s external flash memory will become a requirement. The current release includes a new feature to prevent a build that is too large fro m being placed in the unit’ s internal flash memo ry. If a build is too large, the unit aborts the download and displays the following message :

tftp download aborted due to flash write error

The MAX unit then restarts with its previous TAOS version and configuration intact. In releases before to TAOS 9.0, the process appeared to complete successfully although TAOS was corrupted and the configuration unusable.

The eik.m60 and tik.m60 builds do not include support for the following features:

•AppleTalk

•BRI

•IPX

•PHS

•POTS

•X.25

For the names of all the software builds and the features they provide, see

/pub/Software-Releases/Max/Upgrade-Filenames.txt

Technologies FTP server.

on the Lucent

Using TFTP to upgrade or downgrade

If possible, use TFTP to change a MAX unit’s version of TAOS. TFTP is a more reliable way to obtain, store, and then change the version of TAOS than is the alternative. Using TFTP, you can use a MAX 6000 unit’s external memory to create redundant backup images, as well as to upgrade the unit’s version of TAOS.

Creating redundant backup images for a MAX 6000 unit

MAX 6000 units now support two redundant copies of TAOS code on the PCMCIA flash memory card. If the first version of code becomes corrupt, the unit boots up the second version.

To create the redundant backup image, proceed as follows: Note: The order of these two steps is not important, but the unit will be unable to recover

from a failure in the primary code image until both steps have been executed. 1 Create a backup copy of the currently running binary on the PCMCIA flash card by using

the fBackupImage debug command:

> fBackupImage

MAX Administration Guide 4-3

Changing System Software Versions

Using TFTP to upgrade or downgrade

Preparing for image copy... This load contains an IOP part Copying 1797281 bytes from PCMCIA flash to PCMCIA... <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Image copied to high PCMCIA flash successfully. >

2 Load the lvs.m60 image into internal flash using the tload -i debug monitor

command to support the backup image:

> tload -i saving config to flash

loading code from 204.253.164.44:69 file lvs.m60...

tftp download complete. Verifying image... Downloaded image is OK.

Using TFTP to upgrade

To upgrade with TFTP, you must enter the commands in the correct sequence. If you do not enter them in the correct sequence, you could lose the MAX unit’s configuration.

To use TFTP to upgrade system software, proceed as follows: 1 Locate the following and place them in the TFTP server home directory:

– The configuration that is compatible with the version of TAOS to which you will

upgrade.

– The build of the system software version to which you will upgrade.

2 From the unit’s VT100 interface, press Ctrl-D to invoke the DO menu, then select

D=Diagnostics.

3 At the > prompt, use the Tsave-m command to save your curr ent con figuration in a way

that allows you to match it with the version of sy stem software with which it is compatible. For example, the following command saves the configuration named config800.cfg from the TFTP home directory of the server named tftp-server:

tsave

-m tftp-server config800.cfg

tftp-server

lvs.m60

4-4 MAX Administration Guide

Changing System Software Versions

Using TFTP to upgrade or downgrade

Caution:

assure that the configuration you save is as small as possible. You must retain the saved configuration file permanently. You will need this file if it ever becomes necessary to revert back to the earlier version after you upgrade the unit to TAOS 9.0. The file you save with the Tsave command contains all the passwords in clear text. Move this file from the TFTP directory to a secure location after the upgrade procedure is complete.

4 Enter the following command

5 Enter the following command to save your configuration to flash memory:

6 Enter the following command:

This completes the upgrade to TAOS 9.0.

A MAX unit’s internal flash storage is limited. Use the tsave -m command to

tloadcode

where name of the system software on the server (relative to the TFTP home directory).

For example, the command

tloadcode tftp-server ebixk.m60

loads ebixk.m60 into flash memory from the machine named tftp-server.

> fsave Use the command immediately after executing the tloadcode command.

> nvramclear

After the unit clears NVRAM memory, the unit automatically resets itself two times.

hostname filename

hostname

is the name or IP address of your TFTP server, and

filename

is the

After installing TAOS 9.0 you will have a smaller amount of available memory than you had with the previous TAOS release. The software files stored on the flash card hav e go tten bigg er and therefore require more memory. As new features are added to TAOS, the amount of memory used by the operating system grows. Therefore, the units running later versions of TAOS report less available memory. The reduced available memory is not a cause for concern.

Using TFTP to downgrade

To downgrade system software, you must follow the same steps as for upgrading TAOS, with one exception. Instead of using the fsave command, as descri bed in step 5 in “Using TFTP to upgrade,” enter the following command to restore the compatible configuration to flash memory:

trestore -f

where

hostname

compatible configuration on the server (relative to the TF T P home directory). For example, the command

trestore -f tftp-server Config803

hostname savedConfig

is the name or IP address of your TFTP server, and

savedConfig

is the

MAX Administration Guide 4-5

Changing System Software Versions

Using the serial port to upgrade or downgrade

retrieves Config803, a configuration compatible with TAOS 8.0.3, from the unit named tftp-server.

Note:

causes trestore to place the configuration in binary format into NVRAM, rendering the configuration unusable to the MAX un it.

The -f argument is necessary when downgrading. Failure to use the -f argument

Using the serial port to upgrade or downgrade

Caution:

Save your current profiles settings to your hard disk before you begin upgrading system software. After the upgrade, restore your profiles from the backup file you created. For security reasons, password information is not stored in backup files. If you have many passwords, you should consider using TFTP to upgrade your software. (For instructions, see

“Using TFTP to upgrade or downgrade” on page 4-3.)

Before upgrading your system through the serial port, make sure you have the following equipment and software:

• An IBM-compatible PC or Macintosh system with a serial port capable of connecting to

• A straight-through serial cable.

• Data communications software for your system, with terminal emulation (for example,

Upgrading system software through the serial cons ole deletes all existing profiles.

the MAX unit’s Console port.

Procomm Plus, HyperTerminal for the PC, or ZTerm for the Macintosh). Verify that the line-width settings of the communications software are set to at least 80 characters.

Saving your current profiles

Caution:

HyperTerminal, disable any screen savers or other programs that could interrupt the file transfer. Failure to do so might cause the file transfer to halt and can render the MAX unit unusable.

Verify that your terminal emulation program has a disk capture feature. Disk capture allows your emulator to capture to disk the ASCII characters it receives at its serial port. You should also verify that the data rate of your terminal emulation program is set to the same rate as the Term Rate parameter in the System menu’s Sys Config profile. You can cancel the backup process at any time by pressing Ctrl- C.

To save the MAX unit’s configuration (except passwords) to disk:

1 Open the Sys Diag menu. 2 Select Save Config, and press Enter.

3 Turn on the Capture feature of your communications program, and supply a filename for

4 Press any key to start saving your configured profiles.

If you use a Windows-based terminal emulator, such as Windows Terminal or

The following message appears:

Ready to download - type any key to start....

the saved profiles. (Consult the documentation for your communications program if you have any questions about how to turn on the Capture feature.)

4-6 MAX Administration Guide

5 Turn off the Capture feature of your communications program. 6 Print a copy of your configured profile and examine the saved configuration file.

Upgrading system software

To upgrade the software through the MAX unit’s serial port:

1 T yp e the following fou r - key sequ ence in rapid succession (press each key in the sequence

shown, one after the other, as quickly as possible):

Esc [ Esc -

(Press the Esc key , the Left Brack et key, the key, and the Minus key, in that order, in rapid succession.) The following string of Xmodem control characters appears:

CKCKCKCK

If you do not see these characters, you probably did not press the four-key sequence quickly enough. Try again. Most peopl e u se bot h hand s and keep one finger on the escap e key.

2 Use the Xmodem file-transfer protocol to send the system file to the unit .

Your communication s program no rmally tak es anywhere from 5 t o 15 minutes to send the file to the unit. The time displayed on the screen does not represent real time. Do no t worry if your communication program displays several “bad batch” messages. This is normal.

3 From the MAX unit’ s VT10 0 interf ace, access the diagno stics moni tor b y pr essing Ctrl-D

to invoke the DO menu, and select D=Diagnostics.

4 At the > prompt, enter the Fclear command:

Changing System Software Versions

Using the serial port to upgrade or downgrade

> fclear

5 At the > prompt, enter the NVRAMClear command:

> nvramclear

This causes the system to reset. When it comes back up, proceed with restoring your configuration.

6 Enter quit to exit the Diagnostic interface. 7 Open the Sys Diag menu. 8 Select Restore Cfg, and press Enter.

The following message appears:

Waiting for upload data...

Use the Send ASCII File feature of the communications software to send the configuration file to the unit.

Note: If you are upgrading, the configuration you restore in this step is the one that you saved by following the steps in “Saving your current profiles” on page 4-6. If you are downgrading then the configuration you saved in “Sav ing your current profiles” i s not t h e correct configuration to restore at this time. If you are do wngrad ing then you must restore the configuration file you saved before you upgraded to the current version of TAOS.

If you have any questi ons abo ut ho w to send an ASCII file, consult t he do cumen t ation for your communications program.

9 When the restore has been completed, the following message appears:

Restore complete - type any key to return to menu

MAX Administration Guide 4-7

Changing System Software Versions

Restoring correct RADIUS parameters

Press any key to return to the configuration menus.

10 Reset the unit by selecting System > Sys Diag > Sys Reset and conf irmin g it.

Restoring passwords

Edit your configuration file and enter the word *SECURE* in each instance of a password and save it as a text-only file. When you use the restore config command, the unit’s

configuration file and the passwords are restored to the unit.

Note: If you do not save the configuration as a text-only file, you will not be able to transfer it into the MAX unit.

If you restored a complete configuration, one without the modifications described above, then all the passwords used in your Security profiles have been wiped o ut. To reset them:

1 Press Ctrl-D to invoke the DO menu, select Password, and choose the Full Access

profile.

2 When you are prompted to enter the password, pr ess Enter (the null password). After you have restored you r privileg es by entering t he null password , you should i mmediately

open the Connection profiles, Security profiles, and Ethernet profile (Mod Config menu), and reset the passwords to their previous values.

After the upgrade

Restoring correct RADIU S parameters

On earlier RADIUS servers, the RADIUS Server submenu consisted of three clients (specific host addresses) and one Server Key for all three clients. If a MAX unit supports the new

RADIUS Server, restoration of the unit’s configuration causes a problem because the new RADIUS Server allows up to nine addresses (host or net) and a Server Key for each address. When you restore configurations with the old Client Address list, the subnet mask assigned to the clients will be the default subnet mask of the address typ e given (for example, 128.50.1.1 will get a subnet mask of 16) and not the previous 32-bit (single host) address. In addition, the Server Key will not automatically be set. You must set the Server Key manually for each client in the RADIUS Server submenu.

If you cannot communicate with the MAX unit t hrough the VT100 cont rol terminal, you mi ght have a problem with terminal configuration, the control port cable, or the MAX hardware.

4-8 MAX Administration Guide

Changing System Software Versions

Notice of discontinuance of configurable RADIUS port and ID space

In earlier versions of the system software, the default settings for User Datagram Prot ocol (UDP) source ports and ID spaces for communication with a RADIUS server specified the use of a unique source port for each card and a distinct ID space for both authentication and accounting requests. However, the MAX unit could be configured to use a single source port and ID space systemwide, in order to accommodate certain RADIUS server daemons that had a system-unique requirement.

Because no known RADUIS servers continue to maintain this requirement, and because increased port density makes the use of a single port and ID space undesirable, MAX units now always use port-unique source ports and always send RADIUS authentication and accounting requests with distinct RADIUS IDs. The following parameters are therefore no longer supported and have been removed from the External-Auth profile:

[EXTERNAL-AUTH] rad-id-space = distinct rad-id-source-unique = port-unique

The rad-ip-space and rad-id-source-unique parameters no longer appear in the External-Auth profile. If you downgrade the unit to an earlier release, the parameters revert to their default values for that release.

MAX Administration Guide 4-9

Administering E1 and T1 Services

Troubleshooting a Red Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Troubleshooting a blinking Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Using Net/E1 and Net/T1 status windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Using line diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Remedying Trunk Down state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Using terminal-server commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Specifying channels for E1 and T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Verifying E1 and T1 parameter settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Troubleshooting channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

A T1 line supports 24 64-Kbps channels, each of which can transmit and receive data or digitized voice. The line uses framing and signaling to achieve synchronous and reliable transmission. The most common configurations for T1 lines are ISDN Primary Rate Interface (T1 PRI) and unchann elized T1, incl uding f racti onal T1. The MAX unit supp orts u p to four T1 lines for up to 96 concurrent sessions.

An E1 Primary Rate Interface (E1/PRI) line consists of 32 64-Kbps channels. E1/PRI uses 30 B channels for user data, one 64-Kbps D channel for ISDN D-channel signaling, and one framing channel. The B channels can be all switched, all nailed up, or a combination of switched and nailed up. The E1/PRI line is a standard in Europe and Asia called CEPT G.703.

A T1 Primary Rate Interface (T1/PRI) line has a total bandwidth of 1.544 Mbps. T1/PRI uses 23 B channels for user data, and one 64-Kbps D channel for ISDN D-channel signaling. The B channels can be all switched, all nailed up, or a combination of switched and nailed up. The T1/PRI line is a standard in North America, Japan, and Korea. Connect this type of line to standard voice, Switched-56, Switched-64, Switched-384, Switched-1536, and MultiRate data services. Using a feature called PRI-to-TI conversion, the MAX can share the bandwidth of a T1/PRI line with a PBX.

Use the MAX unit’s indicator lights to begin troubleshooting and diagnosing E1 or T1 problems. Use line diagnostics to perform tests on the unit and see the information that is displayed in the unit’s status windows to determine whether or not E1 or T1 performance is meeting your standards. By verifying telephone numbers and using one VT100 interface parameter, remedy a Trunk Down state on the unit. Use the terminal-server command line interface (CLI) to test lines, reset the unit, clear calls, and display clock source. Verify

MAX Administration Guide 5-1

Administering E1 and T1 Services

Troubleshooting a Red Alarm

parameters in the VT 100 interface that are E1-specific, T1-specific, T1/PRI-specific, and PBX-T1-specific.

The MAX 6000 and MAX 3000 units also support unchannelized T1 services and fractional T1 services. An unchannelized T1 service uses the entire bandwidth of a T1/PRI line (1.544 Mbps) or an T1/PRI line (2.048 Mbps). Use an unchannelized line for a nailed-up connection, such as the link to a Frame Relay network. The MAX unit treats the line as though it were a single connection at a fixed speed, without individual channels. For more information, see

Chapter 8, “Administering PAD, X.25, and Frame Relay.”

Troubleshooting a Red Alarm

Without using any of the MAX 6000 or the MAX 3000 unit’s available interfaces, the indicator lights help you begin to gather information about the performance of the unit. For example, if the Alarm indicator light indicates that the line is in a Red Alarm state, the MAX unit cannot establish proper synchronization an d frame alignment with the WAN. Synchronization is a method of ensuring that the receiving end of a WAN connection can recognize characters in the order in which the transmitting end sent them, and can kn ow wher e on e chara c ter end s and the next begins. Without synchronization, the receiving end perceives data simply as a series of binary digits with no relation to one another. Frame alignment is a method of ensuring that the sending end of a WAN connection can recognize characters in the order in which the receiving end returns them, and can know where one character ends and the next begins.

After you plug an E1 or T1 line into the unit or change the settings that affect framing and synchronization, allow 30 seconds for the Red Alarm state to end.

Verifying enabled lines

The MAX 6000 or MAX 3000 unit that supports E1 or T1 can accommodate up to two line profiles in each of its Net/E1 or Net/T1 interfaces. If you are not using one of the MAX unit’s lines and it is enabled in the Line Config menu’s Line N profile, the unit is in a Red Alarm state. You must verify that the unused line is disabled in the Line Config menu’s Line N profile. In the following example, the 2nd Line is unused and, therefore, disabled:

10-1** Factory

Name=Factory

>2nd Line=Disabled

x Line 1... x Line 2...

Conversely, if you have a line that is set to Enabled and the T1/PRI services have been temporarily discontinued by the carrier, the unit is in a Red Alarm state. This could occur if you enable the integrated Channel Service Unit (CSU) on a T1/PRI port and connect the port directly to the metallic interface of the WAN without contacting your carrier for approval. To avoid harming the WAN, you must contact your carrier for approval before instal la ti on. If you disconnect or turn off the unit without prior notification, the carrier might temporarily discontinue your T1/PRI service. Verify that the port’s integrated CSU in the Front End parameter is set to CSU, in the Line Config menu’s Line N profile, then contact your T1/PRI carrier.

5-2 MAX Administration Guide

For more informati on about th e CSU and tr oubleshoot ing indicat or light s, see “Integrated CSU

for T1/PRI” on page 5-4.

Verifying Framing Mode settings

You must contact your E1 or T1 service carrier to determine the correct setting to specify for the Framing Mode parameter, which is located in the Line Config menu’s Line N profile. The Framing Mode parameter specifies the framing mode in use on the physical links of a T1 o r E1 line.

For a T1 line, the carrier can require you to specify one of the following values:

•

For an E1 line, the carrier can require you to specify the following values:

•

—Specifies the superframe format, which consists of 12 consecutive frames, separated

by framing bits. Do not use this setting with ISDN D-channel signaling (when

Signaling-Mode=ISDN ESF

—Specifies the Extended Superframe Format, which consists of 24 consecutive frames, separated by framing bits. The ISDN specification advises that you use ESF with ISDN D-channel signaling (when

G703

—Specifies that the trunk interface uses CRC-4.

2DS

—Specifies that the trunk interface does not use CRC-4.

Signaling-Mode=ISDN

Administering E1 and T1 Services

Troubleshooting a Red Alarm

Resolving cabling issues

If the MAX unit is connected through bantam con nector plugs, reverse the transmit an d receive plugs. Then allow the unit to attempt to establish s ync hronization for 30 seconds. The MAX unit uses bantam connector plugs to connect with digital circuits and digital crossover (DSX) patch panels .

Perform a line loopback test on a RJ48C connector-plug, connect: pin 1 to pin 5 and pin 2 to pin 4. When you plug this connector into the T1/PRI WAN port, the port should come out of Red Alarm state on the MAX unit, no matter what Encoding or Framing Mode settings you have specified. You should see line active (LA) in the corresponding line status window.

For more information about cables and cable specifications, see the Hardwa r e Ins tal lat ion an d Basic Configuration Guide for your unit.

Summary of Red Alarm causes and solutions

T able 5-1 summarizes potential causes for a Red Alarm and the solutions that may end the Red Alarm state.

Table 5-1. Red Alarm potential causes and solutions

Cause Solution

Unused T1 or T1 line is enabled

If the one of the T1 or T1 lines is unused, verify that it is disabled in the Line Config menu’s Line N profile.

MAX Administration Guide 5-3

Administering E1 and T1 Services

Troubleshooting a blinking Alarm

Table 5-1. Red Alarm potential causes and solutions (continued)

Cause Solution

Framing Mode parameter specifies incorrect value

Cabling problems Y ou might have a cross over cable install ed when a straight-t hrough cable is requ ired,

Check the specified value of the Framing Mode parameter in the Line Config menu’s Line N profile.

or vice versa.

Troubleshooting a blinking Alarm

Without using any of the MAX 6000 or the MAX 3000 unit’s available interfaces, a blinking Alarm helps you begin to gather information about the performance of the unit. For example, the indicator lights can indicate that a secondary E1/PRI or T1/PRI line is disabled.

A blinking Alarm indicator light indicates that the physical configuration of the E1/PRI or T1 line is correct but the D channel is not communicating with the WAN. A D channel carries WAN synchronization and signaling information on a T1 or T1 line. Synchronization over the D channel helps assure that data traveling over the network does not get lost or become jumbled. Signaling enables connections over telephone lines to be gracefully built and then torn down. Remedy D-channel issues by verifying information with your PRI service carrier, specifying values for several parameter settings in the Line Config profile, and verifying whether or not the unit is equipped with an integrated Channel Service Unit (CSU).

Integrated CSU for T1/PRI

If the WAN interface or the MAX unit is not equipped with an integrated CSU, the Alarm indicator light blinks. A CSU is a component of Data Circuit-terminating Equipment (DCE). A CSU connects a digital telephone line to a customer's network-access equipment. It can be built into the network interface of the network-access equipment, or it can be a separate device. The CSU terminates the connection at the user's end and processes digital signals. For information about displaying WAN interface features, such as the integrated CSU, see “Listing WAN interface features” on page 5-7.

Specify whether or not the MAX unit uses the integrated CSU by enabling or disabling the Front End parameter in the Line Config menu’s Line N profile. In the following example, the Front End parameter specifies the front-end type of the T1 transceiver. For a T1 line, specify CSU or DSX. The CSU setting specifies a Channel Service Unit, a device that ensures that only clean signals go out on the line. For example:

10-103

Line 1...

Example profile

Sig Mode=Inband NFAS ID num=N/A Rob Ctl=Wink-Start Switch Type=N/A Framing Mode=D4

Front End=CSU

Encoding=AMI FDL=N/A Length=

5-4 MAX Administration Guide

Administering E1 and T1 Services

Troubleshooting a blinking Alarm

Buildout=0 dB Clock Source=Yes Collect DNIS/ANI=No Pbx Type=N/A Delete Digits=N/A Add Number=N/A Front-End-Type

In the preceding example, the Front En d parameter is set to CSU. However, for T1/PRI there is one other valid setting and for T1/PRI there are two other settings. The digital crossover interfaces for connecting DS1 and DS3 signals. The specifies that there should be no such limitation.

If you enable the internal CSU on a T1/PRI port, connect the port directly to the metallic interface of the WAN. T o avoid har ming the WAN, you must contact your carrier for approval before installation. Once you install the MAX unit, you must no tify the carrier before disconnecting the unit from the WAN. If you disconnect or turn off the unit without prior

notification, the carrier might temporarily discontinue your T1/PRI service.The MAX unit’s internal CSUs are compatible with dry-loop T1/PRI lines, and with span-powered or wet-loop powered T1/PRI lines.

DSX

setting specifies

Short-Haul

setting

If you intend to use the MAX unit on T1 service lines, the unit must be o ne that is equipped with a CSU, otherwise the Alarm indicator light blinks. For example, MAX 6000 and the MAX 3000 units that support T1 have an integrated CSU.

During loss or power, or any other time a MAX 3000 unit resets, a relay closure connects WAN 1 to WAN 3. This feature protects the MAX 3000 unit’s drop-and-insert port (WAN 3) from power interruptions.

If you enable DSX on a T1/PRI port, you cannot connect directly to the WAN. You must connect the port to other equipment that provides the interface to the WAN (for example, an external CSU). Your carrier determines the correct value for the line buildout setting of the CSU, and you specify the value during installation.

If you specify settings for an E1/PRI line,

Long-Haul

setting specifies that th e uni t uses120-ohm termination only.

Remedying D-channel issues

With your PRI service carrier, you verify that the D channel is in service. This is especially important if no equipment has been plugg ed in to the line for some time. Next, your E1/PRI or T1/PRI service carrier can verify the setting that they are using for the line is appropriate for your MAX unit. For examp le, a MAX unit that supports T1 requires a D channel setting of 16. Finally, the T1 services carrier can verify the type of line encoding to specify in the Line Config profile’s Encoding parameter.

Long-Haul

Short-Haul

are valid. The

In the MAX unit’s Line Config profile, verify that you have specified values that support the type of E1/PRI or T1 services required by the unit. The Encoding parameter specifies the type of T1 line encoding that the MAX unit uses. Your carrier can tell you which type of encoding you require.

There are three possible settings. AMI, the default setting, specifies that the unit uses Alternate Mark Inversion encoding. AMI is an encoding method in which alternating positive and

MAX Administration Guide 5-5

Administering E1 and T1 Services

Troubleshooting a blinking Alarm

negative voltage represents a 1, and zero voltage represents a zero. AMI includes density enforcemnt, which dictates that you cannot transmit 16 consecutive zeroes. The specifies that AMI is used without applying density enforcement. encoding is Bipolar with 8-Zero Substitution. This is often required for ISDN lines. The B8ZS encoding method uses alternating positive and negative voltage to represent a 1, zero voltage represents a zero, and at least one bit out of every eight bits must be a 1.

After you have determined the correct setting, specify the setting by using the Encoding parameter. In the following example the PRI carrier has specified that setting:

10-103

Line 1...

Example profile

Sig Mode=Inband NFAS ID num=N/A Rob Ctl=Wink-Start Switch Type=N/A Framing Mode=D4 Front End=CSU

Encoding=AMI

FDL=N/A

Length= 1-133 ft. Buildout=0 dB

Clock Source=Yes Collect DNIS/ANI=No Pbx Type=N/A Delete Digits=N/A Add Number=N/A Front-End-Type

B8ZS

specifies that the

AMI

is the correct

None

setting

In the preceding example T1 line profile, the Length param eter specifies the cable length of the line from the CSU or other network interface unit to the MAX unit. The setting you indicate must reflect the longest line length you expect to encounter in your installation. The blinking Alarm state continues until you specify a value that is correct for your installation.

The Buildout parameter specifies the line buildout value for T1 lines connected to an internal CSU (Channel Service Unit). The buildout value is the amou nt of attenuation the unit should apply to the line’s network interface. The amount, if any, depends on the length of the MAX unit and the repeater from which it receives the signal. If the MAX unit is too close to a repeater, you might need to specify some attenuation, to reduce the strength of the signal. Check with your carrier to determine the correct value for this parameter. This parameter is not applicable if the T1 line does not have an integrated CSU to connect to the local digital telephone system.

For more information about the integrated CSU, see “Integrated CSU for T1/PRI” on page 5-4.

5-6 MAX Administration Guide

Administering E1 and T1 Services

Using Net/E1 and Net/T1 status windows

Summary of blinking Alarm potential causes and possible solutions

Table 5-2 summarizes potential causes and solutions for the blinking Alarm indicator.

Table 5-2. Blinking Alarm potential causes and possible solutions

Cause Solution

MAX unit is not equipped with a CSU

D channel is out of service

D channel setting is incorrect

Encoding parameter setting is incorrect

Determine whether your WAN interface or the MAX T1 unit is equipped with a CSU.

If no equipment has been plugged into the line for a short period of time (five to ten minutes), the D channel is taken out of service. Y ou might need to ask your carrier to put the D channel back into service.

Verify with your carrier representative that the D channel is channel 16 (E1) or 24 (T1).

If the carrier’s D channel number is correct, check the value of the Line Encoding parameter in the Line profile. When B8ZS encoding is in use, a noninverted D ch annel is establ ished. I f AMI encodin g is selected, an inverted D channel is established. Check the line translations provided by your carrier representative and set the li ne encoding to match the inversion requirements.

Using Net/E1 and Net/T1 status windows

MAX 3000 and MAX 6000 units that support E1 provide you with Net/E1 status windows. The units that support T1 provide you with Net/T1 status windows. The status windows are

branches of the Main Status window, in the unit’s VT100 interface. Use the status windows to display WAN interface features, error and performance information, line status, and Facility Data Line (FDL) Extended Superframe (ESF) performance.

For general information about navigating status windows in the VT100 interface, see the Hardware Installation and Basic Configuration Guide for your unit.

Listing WAN interface features

The Net Options window lists the WAN interface features installed on the MAX unit that supports T1 (or E1). To display the Net Options window, tab to a status window, then use the arrow keys to access the Net Options window.

The following example shows the Net Options window on a MAX unit that supports T1/PRI:

Net Options >T1/PRI Network I/F 2 Network I/F(s) Type: CSU/CSU

MAX Administration Guide 5-7

Administering E1 and T1 Services

Using Net/E1 and Net/T1 status windows

In the preceding example, the first line shows that the type of physical interface to the WAN is a T1/PRI Network I/F. The second line shows the number of network interfaces associated with the module. The third line shows whether internal CSU s are installed for the T1 lines.

Displaying errors

The Line Errors status window shows errors recorded on all current channels, in a channel-by-channel, line-by-line list. This is the case even if the interface is disabled in the Line N profile.

To display the Line Errors window, tab to a status window, then use the arrow keys to select a menu item representing a slot configuration (this section assumes a slot configured for T1 lines). After selecting that item, select the Line Errors window:

10-000 Net/T1

10-100 Line 1 Stat 10-200 Line 2 Stat

>10-300 Line Errors

Then, when you press Enter or the Right Arrow key, the T1 Line Errors window displays the channel-by-channel errors accumulated during all current calls. The window is divided into three columns. For example:

10-300 Errors 1: 0 2: 33 3: 33 -

The first column displays the T1 channel number followed by a colon (:). For a BRI line, it lists the line numbers (1 through 8).

The second column indicates the number of byte errors the MAX has detected on the channel in Line 1 during the current call. The third column displays the number of byte errors the MAX has detected on the channel in Line 2 during the current call.

If a channel is not associated with a current call, a hyphen (-) ap pears instead of a number. Any channel that would not have a number in either is omitted from the display.

Displaying link and channel status

The Line Stat windows (Line 1 Stat and Line 2 Stat) show the dynamic status of each WAN line, the condition of its electrical link to the carrier, and the status of its individual channels. T o display the line status window, tab to a status window, then use the arrow keys to access the Line N Stat window, in the Net/T1 (or Net/E1) menu. For example:

10-100 1234567890 L1/LA ----------

12345678901234

-------------s

5-8 MAX Administration Guide

Administering E1 and T1 Services

Using Net/E1 and Net/T1 status windows

In the preceding example, the first line of the Line Stat window shows the window number followed by columns for channels 1 through 10. The second line begins with the line number, followed by the link status, which is indicated by one of the two-character abbreviations listed in Table 5-3. Following the link status is a single-character that indicates channel status. (Table 5-4 lists the channel-status indicators.) The third line has column headers for the remaining channels. The fourth line continues where the second line left off, showing the status of the remaining channels.

Note: If the MAX 3000 unit is configu red for Drop-an d-Insert functi onality, and a Red Alarm (RA) or Loss of Synch condition is detected, the failure is conveyed to the device by sending an all ones (A1S) over Line 2. The Red Alarm indicates the line is not connected, improperly configured, experiencing a very high error rate, or is not supplying adequate WAN synchronization. The Alarm indicator light illuminates when the line is in this state. During the time this failure is active, devices connected to Line 2 cannot place calls.

Table 5-3 summarizes the link-status indicators that appear in the Line Stats window.

Table 5-3. Lin k -status indicators

Link status Mnemonic Description

LA Link active The line is active and physically connected. RA Red Alarm/Loss

of Sync

YA Yellow Alarm The MAX unit is receiving a Yellow Alarm pat-

DF D-channel fail-

ure

1S Keep alive (all

ones). Also known as Blue Alarm.

DS Disabled link The line is physically connected, but you have dis-

The line is not connected or is improperly configured, experiencing a very high error rate, or is not supplying adequate synchronization. The Alarm indicator light illuminates when the line is in this state.

tern. The Y ellow Alarm pattern is sent to the unit to indicate that the other end of the line cannot recognize the signals the unit is transmitting. The Alarm indicator light illuminates when the line is in this state.

The D channel for a PRI line is not currently communicating.

A signal is being sent from th e T1 (or E1) network to the MAX unit to indicate that the T1 line is currently inoperative. The Alarm light illuminates when the line is in this state.

abled the line in the Line N profile.

MAX Administration Guide 5-9

Administering E1 and T1 Services

Using Net/E1 and Net/T1 status windows

A single character represents the status of each channel in the line, as described in Table 5-4.

Table 5-4. Channel-status indicators

Channel status

. Not available The channel is not available because the line is disabled,

* Current The channel is connected in a current call.

- Idle The channel is currently idle (but in service). d Dialing The unit is dialing from this channel for an outgoing call. r Ringing The channel is ringing for an incoming call. m Maintenance The channel is in maintenance/backup (ISDN only). n Nailed The channel is marked Nailed in the Line N profile. x Drop-and-Insert The channel is configured for Drop- and-Ins ert fo r a DASS

o Out of Service The channel is out of service (ISDN only). s ISDN D channel The channel is an active D channel (ISDN only).

Mnemonic Description

has no physical link, or does not exist, or because is set to

Unused

2 E1 line or DPNSS E1/PRI line.

in the Line N profile.

b Backup ISDN D

channel

Displaying FDL statistics

A Facilities Data Link (FDL) is a 4-Kbps digital link between a sender and the telephone company’s monitors. The FDL uses Extended Superframe (ESF) framing, a framing format that consists of 24 cons ecutive frames, separ ated by framin g bits . The tel ephone co mpany u ses an FDL to check on the quality and performance of T1 lines. It provides information at regular intervals to your carrier’s maintenance devices. The MAX unit continues to accumulate ESF performance statistics in the FDL Stats windows, even if you do not choose an FDL protocol. Your carrier can tell you which FDL protocol to specify.

The FDL Stats windows are the fourth and fifth options listed in the VT100 interface’s status window Net/T1 window:

10-000 Net/T1 10-300 Line Errors ^ 10-400 FDL1 Stats >10-500 FDL2 Stats 10-600 Net Options

The channel is the backup D channel (ISDN only).

5-10 MAX Administration Guide

Administering E1 and T1 Services

Using Net/E1 and Net/T1 status windows

The following display shows the contents of the FDL2 Stats window:

10-500 FDL2 Stats >Error Events... Current Period... Last 24 Hours... 00:00... v

Note: Pressing the Down Arrow key displays additional statistics.

Display the statistics accumulated during the current 15-minute period (Current Period), the summed performance data accumulated during the past 24 hours, or the statistics for any

15-minute period in the previous 24 hours. If you select Last 24 Hours, get any past period’s registers, select an hour from the window, (03:00, for example), and then select any 15-minute period within that hour. Select any hour within the last 24.

Note: If your T1 service has a D4 (SF) interface, no carrier performance data is recorded. The D4 format consists of 12 consecutive frames, each one separated by framing bits. T1 lines that do not use ISDN D-channel signaling use the D4 format.

The performance registers contain both user and carrier Extended Superframe Format (ESF) statistics. The user performance-registers appear in the middle column after the register names, and the carrier performance-registers appear in the last column:

10-500 FDL2 Stats 03:45

ES:000005 000005 US:000000 000000 SS:000000 000000 BS 000000 000000 LF:000000 000000 CS:000000 000000

user registers

carrier registers

You can use the Clr Perf N parameters in the Line Diag menu to reset the user performance registers, but only the carrier can reset the carrier registers. All performance registers are reset upon power-up or software reset.

Table 5-5 describes the FDL performance registers.

Table 5-5. FDL performance registers

EE Displays the number of error events accumulated since the last time

this register was reset. An ESF error event is counted when the CRC-6 calculations at the receiving end of the T1 span do not match the CRC-6 calculations at the sending end. A mismatch indicates that the frame had at least one data error. Error events have no meaning for D4 lines. Only ESF lines carry the CRC-6 signature used to check the quality of the PRI line as a whole.

MAX Administration Guide 5-11

Administering E1 and T1 Services

Using Net/E1 and Net/T1 status windows

Table 5-5. FDL performance registers (continued)

ES Specifies errored seconds. For ESF lines, this register displays the

US Indicates unavailable seconds—the number of seconds in the

SS Displays severely errored seconds—the number of seconds, during

number of seconds in the 15-minute period in which there was at least one error event, or in which two or more framing errors were detected within a 3 ms interval. For D4 lines, this register display s the number of seconds in which one or more framing bit errors (FE) were detected or in which a controlled slip (CS) occurred.

15-minute period preceded by at least 10 consecutive severely errored seconds (SS).

the 15-minute period, in which there were at least 320 CRC-6 errors as detected by the MAX unit, or in which the T1 line was out of frame. For D4 lines, this register displays the number of one-second intervals containing eight or more framing bit errors (FEs) or one or more SEFs.

BS Specifies bursty errored seconds—the number of secon ds, during the

LF Indicates loss of frame seconds— the number of seconds in the

CS Displays controlled slip seconds—the nu mber of seconds in the

Fractional T1 services

Set the Call Type parameter to specify several fractional T1 settings. One of the settings, FT1-B&O, affects the information that the MAX unit displays in the Statistics window.

Fractional T1 is a nailed-up T1 line with bandwidth that might be only a fraction of the full T1 bandwidth. A nailed-up line is one that is rented from the telep hone company for exclusive use, 24 hours per day, seven days per week. It is possible to lease one channel on a line from the telephone company for exclusive use, 24 hours per day, seven days per week. The connection exists between two predet ermined poin ts and cannot be switched t o other locations. A nailed-up line is also called a leased line.

21-300 Albuquerqu+ O Qual Good 00:04:01

15-minute period, in which there were at least 2, but not more than 319, CRC-6 errors as detected by the MAX unit.

15-minute period in which the T1 line was out of frame.

15-minute period in which a frame was either replicated or deleted.

5-12 MAX Administration Guide

MAX Rel Delay 10 CLU 80% ALU 77%

Using line diagnostics

MAX 3000 and MAX 6000 units that support E1 or T1 provide you with a set of diagnostic

command parameters, in the Line Diag menu, to test the performance of the units’ lines. Initiate a line loopback test, swap the status of Non-Facility Associated Signaling (NFAS) D-channels on applicable lines, clear each line’s user error event registers, and clear all performance registers for each line using the options in the Line Diag menu.

A MAX 6000 unit that supports E1 or T1 lines has two slots, each of which supports two lines. Each of the unit’s two Line Diag menus provide line loopback, clear event registers, and clear all performance registers parameters for two lines, as in the following example of a MAX 600 0 that supports T1:

10-000 Net/T1

10-200 Line Diag

>10-201 Line LB1

10-202 Line LB2 10-203 Switch D chan 10-204 Clr Err1 10-205 Clr Perf1 10-206 Clr Err2 10-207 Clr Perf2

Administering E1 and T1 Services

Using line diagnostics

A MAX 3000 unit that supports E1 or T1 lines has one slot that supports two lines. However, the MAX 3000 unit can also include one drop-and-insert (North America integrated CSU) T1 line. The unit’s one Lin e Diag menu p rovides line loopb ack, clear ev ent registers, and clear all performance registers parameters for three lines, as in the following example of a MAX 3000 that supports E1:

10-000 Net/E1

10-200 Line Diag

>10-201 Line LB1

10-202 Line LB2 10-203 Line LB3 10-204 Switch D chan 10-205 Clr Err1 10-206 Clr Err2 10-207 Clr Err3 10-208 Clr Perf1 10-208 Clr Perf2 10-209 Clr Perf3

Clearing user error event and performance registers

The Clr Err1 command clears the user error event register of Line 1, the Clr Err2 command clears the user error event register of Line 2, and the Clr Err3 command clears the user error

MAX Administration Guide 5-13

Administering E1 and T1 Services

Using line diagnostics

event register of the MAX 3000 unit’s drop-and-insert Line 3. However, the Clr ErrN commands do not clear the performance registers for the line. The Clr PerfN command clears all performance registers for Line N, restarts the current time period, and begins accumulating new performance data.

Note: Error events have no meaning for D4-framed lines. A D4 line uses the Superframe format to frame data at the physical layer. This format consists of 12 consecutive frames separated from one another by fr aming bits.

Initiating a line loopback test

Note: Do not activate a line loopback test when a call is active on the line because the test

disrupts data flow between the codecs connected to either end of the network line.

Line LB1 is a Line LoopBack (LLB) command for Line 1 in a T1 slot, Line LB2 is a Line LoopBack command for Line 2 in a T1 slot, and so on. When you start the line loopback test for a T1 line, a remote device can test the T1 line and the MAX unit’s interface to the T1 line. All signals received by the MAX unit are looped back toward the remote unit. The remote unit can determine the quality of the T1 line by comparing the sent signal to the received signal.

The LLB occurs behind the unit’s Channel Service Unit (CSU) repeater, which boosts the signal on a T1 line, or Digital System Cross-con nect (DSX) signal-condit ioning module, whic h amplifies signals. Drop-and-Insert channels, which enable a single T1 line to carry both data and voice traffic, are also looped back.

Note: Do not activate LLB when a call is active on the line; doing so disrupts the data flow between the codecs connected to either end of the network line.

The unit responds to both the inband LLB signal and the Facility Data Link (FDL) LLB message. A management device can put the unit into LLB. A management device is a unit, on a T1 line, that measures the line’s performance and can send management signals to other devices on the line.

To initiate a loopback test on the first T1 line, highlight Line LB1 and press Enter. After prompting for confirmation, the unit starts the loopback test and the Alarm LED lights up. When you exit the menu option, th e unit automatically deactivates the loopback.

Swapping NFAS status

The Switched D Chan parameter, in the Line Diag menu, swaps the status of the primary and secondary Non-Facility Associated Signalin g (NFAS) Dchannels. It applies only to T1 lines using NFAS signaling.

NF AS is a form of out-of-band sig naling that maximizes the number of PRI lines supported by the signaling of one external Dchannel. NFAS is a special case of ISDN signaling in which two or more T1 lines use the same D-channel, and add a backup Dchannel. NFAS is required for the Switched-1536 data service. Because all 24 channels of the T1 line carry user data, the Dchannel must be on anothe r line.

5-14 MAX Administration Guide

Administering E1 and T1 Services

Remedying Trunk Down state

Table 5-6 summarizes Net/T1 diagnostic commands available in the Line Diag menu.

Table 5-6. Net/T1 diagnostic commands

Command Purpose

Line LB1 Line LB2 Line LB3

Switch D Chan

Clr Err1 Clr Err2 Clr Err3

Clr Perf1 Clr Perf2 Clr Perf3

Testing the lines

Test Line 1, Line 2, or Line 3 (MAX 3000 only) in a T1 slot, places a call from the MAX unit to itself over the WAN to determine the unit’s ability to initiate and receive calls and to diagnose the soundness of the digital access line and WAN.

Do not initiate these commands when a call is active on the line because they disrupt data flow between the codecs connected to either end of the network line.

Swaps status of the primary and secondary Non-Facility Associated Signaling (NFAS) D channels on T1 lines that use NFAS signaling.

Clears the user error event register of Line 1, Line 2, or Line3 (MAX 3000 only).

Clears all performance registers for Line 1, Line 2, or Line 3 (MAX 3000 only), restarts the current time period, and begins accumulating new performance data.

The MAX unit can run a test (sometimes called a self-test) that uses two op en channels to place a call on one open channel and receive the call on another open channel. Use the Test

command, in the unit’s terminal-server CLI, to perform this test.

Before you begin you must check one setting in the Sys Config profile and two settings in the Line N profile. Verify that you have not enabled the Use Trunk Grps parameter in the Sys Config profile. The Call-by-Call parameter, in the Line Config menu’s Line N profile, specifies the PRI service that the MAX uses when placing a call that is part of the test. Finally, verify that the unit has two available channels. Warning 180 is caused by a missing channel on a T1/PRI line. For example:

ERROR_CHAN_DISPLAY_STUCK 181 ERROR_NEW_CALL_NO_DISC_REQ 182

Remedying Trunk Down state

When the list of DO commands appears, many operations might not be not available if the right profile is not selected. Because the MAX unit can manage a number of calls simultaneously, you might need to select a specific Connection profile, Port profile, or Call profile in order to see certain DO commands. For example, to dial from a Call profile or a

MAX Administration Guide 5-15

Administering E1 and T1 Services

Using terminal-server commands

Connection profile, you must move to the Call profile (Host/6 > Port N Menu > Directory) or the Connection p rofile and press Ctrl-D 1.

Y o u cannot dial if 2 (Hang Up) appears instead of DO 1 (Dial). If the T1 or E1 line is not available, Trunk Down appears in the message log and you cannot dial.

To verify that the profile is correctly configured:

1 Make certain that you have entered the correct telephone number to dial. 2 Verify that the Data Svc parameter specifies a WAN service available on your line.

If you request a WAN service that is not available on your line, the WAN rejects your request to place a call.

3 Check whether the channels using the requested W AN service are busy.

If these channels are busy, an outgoing call might be routed to chan nels for which y ou d id not request the specified WAN service. Check the Data Svc, Call-by-Call, and PRI # Type parameter values in the profile.

4 Determine whether you have co rrectly set th e paramete rs contr olling Dy namic Ba ndwidth

Allocation. For detailed information, see the Network Configuratio n Guide for your unit.

Operations

is set to No for the control port. If a call is already active, DO

Using terminal-server commands

T erminal-server CLI commands can display information directly related to, or temporarily

affecting, the performance of the unit’s the E1/PRI and T1/PRI interfaces. Use the terminal-server command-line interface to test and reset the MAX unit. Verify clock source settings the MAX unit.

For more information about how to use the terminal-server command-line interface, see Chapter 3, “Terminal-Server Administrative Tasks.”

Resetting the unit and clearing calls

The Sys Reset command restarts the MAX unit and clears all calls without disconnecting the device from its power source. The unit logs out all users and returns user security to its default state. In addition, the unit performs diagnostic power-on self tests (POSTs) when it restarts. A system reset of a MAX unit causes momentary loss of T1 framing (that is, the data-encapsulation format), and the T1 line might shut down. In any event, the feedback from the MAX unit to the switch is incorrect until T1 framing is reestablished, usually within 30 seconds. If you have enabled the integrated CSU on the MAX unit that you are testing, you must notify your E1/PRI or T1/PRI carrier before you turn the unit off. For more information, see “Integrated CSU for T1/PRI” on page 5-4.

Displaying the source of clocking

The Clocksource command displays the source of clocking for the MAX unit. Clock slips can cause connectivity problems, particularly for analog users. If you have used the Clock Source parameter , i n t he Li n e C onf ig menu’s Li ne N profile, use the clocksource command to validate your changes.

5-16 MAX Administration Guide

Administering E1 and T1 Services

Specifying channels for E1 and T1

In the following example, the clock sour ce is taken f rom the first T1/PRI line, designated

0. Dsl#

on Net/T1 slot cards. This MAX has three T1/PRI lines configured, so there are three possible external sources for the clock. from clock source. For example:

MAX> clocksource Clock source is dsl 0 Dsl# 01234567890123456789012345678901234567890123456789 LstSel a????????????????????????????????????????????????? Now 222-----------------------------------------------

You must reset the MAX unit to enable any changes to the Clock Source parameter. Also, if more than one line has Clock Source set to derived from the first line with which the unit synchronizes. If you want to ensure that a particular line is the source, make sure it has Clock Source set to have Clock Source set to No.

indicates the maximum number of possible sources for the clock. The source can be

Dsl#0

. After

LstSel

Now

, a 2 indicates that Layer 2 is up for that line and is available as the

is further validation that the clock is being derived

Yes

, remember that the clock source will be

Specifying channels for E1 and T1

The telephone numbers that you specify in the Line N profile are the numbers local to your unit. Do not enter the telephone numbers of the MAX unit you are calling. Enter those numbers in the Call profile, Destination profile, or Con nection profile.

Yes

and that all other lines

dsl

In addition, when you are using E1 or T1 lines, any telephone numbers you specify must correspond to those channels within the circuit that are available for data transmission. For example, if channels 13 through 21 are allocated to a particular slot, you must specify the telephone numbers for ch annels 13 t hrough 21 i n the Line N profil e. Switched data channels do not have to be contiguous with in the circuit.

Verifying E1 and T1 parameter settings

Verify parameter settings in the MAX unit’s VT 100 interface that are E1-specific, T1-specific, T1/PRI-specific, and PBX-T1-specific. Determine if the configuration of the unit is correct for your T1 or E1 services environment. In some cases, you may need to contact your E1 or T1 service carrier for information about the correct settings you are required to specify.

E1-specific parameter settings

The VT100 interface of the MAX unit includes a NET/E1 menu. Specify E1 settings by using one E1-specific parameter in the Line Config profile and four E1-specific parameters in the Line N subprofiles in the Line Config profile. You must evaluate the settings of E1 parameters as you verify the proper configuration of the unit. In some cases, the correct setting that you must specify is determined by your E1 services carrier.

MAX Administration Guide 5-17

Administering E1 and T1 Services

Verifying E1 and T1 parameter settings

Table 5-7 summarizes the E1-specific parameters that are available.

Table 5-7. E1 parameters and settings

Parameter Description

Back-to-back Enables you to set up DASS-2 and DPNSS lines in a back-to-back con-

L2 End Specifies CCITT Layer 2, which is used to determine the address to

L3 End Specifies whether or not the MAX unit supports Layer2 Tunneling

nection. A crossover cable connects an E1 port of one MAX unit to an E1 port of another unit. No switch is required, and the connection is entirely local. One unit should be set up for DTE operation, and the other for DCE operation. This parameter applies only to E1 lines whose signaling mode is DPNSS. DPNSS is a standard that defines how different Private Branch Exchange (PBX) systems can operate together to produce a single virtual PBX.

send when two PBX devices are connected back-to-back. In that case, one side must act as a PBX and the other side must act as an ET.

Protocol (L2TP) and, if it does, whether the unit functions as an L2TP Access Concentrator (LAC), an L2TP Network Server (LNS), or both.

LoopAvoidance Specifies the number of transit PBX devices through which a call may

be routed.

NL Value Specifies the number of retransmission s to send on this line. The

default value is required when the line connects to a DPNSS or DASS2 switch. It must be set to its default value when the line connects to a DPNSS or DASS2 switch. The default is 64.

T1-specific parameter settings

The VT100 interface of the MAX unit includes a NET/T1 menu. Specify T1 settings by using three T1-specific parameters in the Line N subprofiles in the Line Config profile. You must evaluate the settings of T1 parameters as you verify the prop er confi guration of the unit.

5-18 MAX Administration Guide

Administering E1 and T1 Services

Verifying E1 and T1 parameter settings

Table 5-8 summarizes the T1-specific parameters that are available, the location of the parameter in the VT100 interface, and whether or not the setting you specify is determined by your E1 services carrier.

Table 5-8. T1-specific parameters

Parameter Description

Buildout Specifies the line buildout v alue for T1 lines with an internal CSU

(Channel Service Unit). The buildout value is the amount of attenuation the MAX unit should apply to the line's network interface in order to match the cable length from the unit to the next repeater.

Attenuation is a measure of the power lost on a transmission line or on a portion of that line. When you specify a build-out value, the MAX unit applies an attenuator to the T1 line, causing the line to lose power when the received signal is too strong. Repeaters boost the signal on a T1 line. If the MAX unit is too close to a repeater, you need to add some attenuation.

FDL Specifies the FDL (Facilities Data Link) protocol that the MAX unit

uses. FDL is a protocol used by the telephone company to monitor the quality and performance of T1 lines. This parameter does not apply to D4-framed T1 lines.

Hunt-n (

=1-3

)

These parameters indicate the hunt group numbers associated with the T1 line in a specific Line N profile. An SNMP manager can retrieve these numbers from Lucent Technologies devices and store them in a table that includes the devi ces from whic h informat ion is retr ieved and the hunt group numbers in their WAN Line Profiles. The numbers entered in th e Hun t-N # parameters must be the same as the numbers that are assigned to T1 channels, creating the hunt group.

Fractional T1-specific parameters

The VT100 interface of the MAX unit that supports Host/Dual (or Host/6) modules includes a Host/Dual (or a Host/6) menu. Specify fractional T1 settings by using five fractional T1-specific parameter in the Port N menu’s Directory profile. Evalua te the settings of

fractional T1 parameters as you verify the proper configuration of the unit intended to support fractional T1 services.

Table 5-9 summarizes fractional T1-specific parameters.

Table 5-9. Fra c tional T1-specific parameters

Parameter Description

FT1 Caller Specifies whether the MAX unit initiates an FT1-AIM, FT1-B&O, or

Nailed/MPP call or whether it waits for the remote end to initiate these types of calls. If the remote end has FT1 Caller set to No, set it to Yes on the local MAX unit; by the same token, if the remote end has FT1 Caller set to Yes, set it to No on the local MAX unit.

MAX Administration Guide 5-19

Administering E1 and T1 Services

Verifying E1 and T1 parameter settings

Table 5-9. Fra c tional T1-specific parameters (continued)

Parameter Description

Idle In a Port profile, this parameter is not applicab le when the port’s current

Call profile is configured for FT1 calls. If the MAX unit uses a port for FT1-AIM or FT1-B&O calls and Idle is set to Call in the Port profile, you must set Dial to FT1-B&O calls, and Idle is set to

DTR

Dial to tion of these parameters. Further, if you set Idle to

DTR

minal Ready) active for the MAX unit to connect the switched channels.

. Both the local and remote ends must use the same combina-

, the hosts at both ends of the connection must make DTR (Data Ter-

Terminal

; if the unit uses a port for FT1-AIM or

None

in the Port profile, you must set

None

and Dial to

Inc Ch Count This parameter does not apply if all channels if the call type is

B&O Restore Specifies how many seconds the MAX unit waits before restoring a

Call Mgm Specifies the way that the MAX unit manages calls at an AIM port when

T1/PRI-specific parameters

The VT100 interface of the MAX unit includes a NET/T1 menu. Specify T1/PRI settings by using four T1/PRI-specific parameters in the Line N subprofiles in the Line Config profile. You must evaluate the settings of T1/PR I parameters as you verify the proper configuration of the unit. The correct settings for the T1/PRI-specific parameters are determined by your T1/PRI service carrier.

Table 5-10 summarizes T1/PRI-specific parameters.

Nailed

In a Call profile, this parameter applies only if the call type is

FT1-AIM, FT1-B&O

Manual, Dynamic

nailed-up channel to an FT1-B&O call-that is, a call for which

Call Type=FT1-B&O

AIM, FT1- AIM, FT1-B&O

Type parameter. For these types of calls, call management consists of remote management, online error monitoring, remote loopbacks, and online bandwidth control between codecs.

BONDING

, or

Mode 2

BONDING

, or

and the Call Mgm parameter is set

is the value for the Call

AIM

Table 5-10. T1-PRI-specific parameters

Parameter Description

Call-by-Call In a T1 Line profile, specifies the call-by-call signaling value to set for

routing calls from a local device through the MAX unit to the netw ork. When it is set in another profile, it specifies the PRI service to use when placing a call using that profile.

Encoding Specifies the type of T1 PRI line encoding that the MAX unit uses.

5-20 MAX Administration Guide

Table 5-10. T1-PRI-specific parameters (continued)

Parameter Description

Administering E1 and T1 Services

Verifying E1 and T1 parameter settings

T1-PRI:PRI # Type

T1-PRI:NumPlanID

T1-PRI:PRI # Type is used for outbound calls made by the MAX unit on PRI lines so that the switch can properly interpret the telephone number dialed. Ask your PRI provider for details on when to use each of settings. This parameter specifies the TypeOfNumber field in the called party’s information element.

The value you specify for PRI # Type in the Dial Plan profile overrides the value of T1-PRI:PRI # Type in the Line N profile if you have enabled the unit’s Dial Plan profiles.

This parameter applies only to calls placed by devices terminating the inband T1 lines provided by the MAX unit in a T1-PRI conversion configuration.

T1-PRI:NumPlanID is used for outbound calls made by the MAX on PRI lines so that the switch can properly interpret the telephone number dialed. Ask your PRI provider for details on when to use each of the settings. This parameter specifies NumberPlanID field in the called party’s information element.

This parameter applies only to calls placed by devices terminating the inband T1 lines provided by the MAX unit in a T1-PRI conversion configuration.

The value you specify for NumPlanID in the Dial Plan pro file overrides the value of T1-PRI:NumPlanID in the Line N profile if you have enabled the unit’s Dial Plan profiles.

PBX-T1 specific parameters

The VT100 interface of the MAX unit includes a NET/T1 menu. Specify T1 settings by using five T1-specific parameters in the Line N subprofiles in the Line Config profile. You must evaluate the settings of T1 parameters as you verify the prop er confi guration of the unit.

Table 5-11 summarizes the T1-specific parameters that are available if the MAX unit is functioning in a PBX-T1 network environment.

Table 5-11. PBX-T1 parameters and settings

Parameter Specifies

Add Number Specifies a series of digits to add to the beginning of the dial-out tele-

phone number after removin g the digits specified by Delete Digits. The device connected to Line 2 (typ ically a PBX) dials this telepho ne nu mber. This parameter applies only to T1 lines using PBX-T1 conversion. Specify any digit str ing t h at the PRI switch requires. Cont act yo ur PR I switch provider for more information about requirem ents.

MAX Administration Guide 5-21

Administering E1 and T1 Services

Troubleshooting channels

Table 5-11. PBX-T1 parameters and settings (continued)

Parameter Specifies

Ans # Specifies a telephone number to be used for routing calls received on

Ans Service Specifies that the MAX unit routes an incoming call from Line 1 to

Delete Digits Specifies the number of digits deleted from the beginning of the tele-

the first T1 line to the second line. Th is may be an add -on number. This parameter applies only to T1 lines using PBX-T1 conversion.

Line 2 (the PBX) if the data service of the call matches the data service specified by Ans Service. It provides an alternative way to indicate which calls received on Line 1 should be forwarded to Line 2. If you set both Ans # and Ans Service t o incoming calls to Line 2.

If you set on Line 1 to Line 2 only if its data service type matches the data service specified by the Ans Service parameter, and only if its telephone number matches the telephone number specified by the Ans # parameter.

phone number dialed by the device connected to Line 2. Typically, a PBX (Private Branch Exchange) is connected to Line 2. A PBX is an internal telephone network in which one incoming number directs calls to various extensions and from one office to another.

Use this parameter when the PBX used to be connected to a switch that supplied a T1 line, is now connected to the MAX unit. The PBX has to change the numbers it dials. The Delete Digits parameter converts the number the PBX dials to the number presented to the WAN switch. This parameter applies only to T1 lines using PBX-T1 conversion.

PBX Type=Data

null

, the MAX unit does not route

, the MAX unit switches an incoming call

Input Sample Count

Allows the PRI-T1 conversion process to use one or two sets of Goertzel samples to do the DTMF tone detection. By default, the MAX unit uses only one sample to decode signals from robbed-bit PBXs, because come PBX devices have a tone duration less than 50ms, which does not provide enough time to compute two sets of Goertzel samples. The PRI- T1 conversion process is more accurate when the unit can use two samples. Using two samp les is recommended when the tone duration is longer than 70ms. This parameter applies o nly to T1 lines using PBX-T1 conversion.

Troubleshooting channels

You might encounter a problem in which the Line Status menu shows that the MAX unit is calling multiple channels simultaneously, but only some of the channels connect. In this case, an international MAX unit placed the call, or the call was from the U.S. to another country. In some countries, setting the Parallel Dial parameter in the Sys Config prof ile to a value higher than 1 or 2 violates certain dialing rules, an d only some of th e channels can connect du ring call setup. Try redu ci ng t he Pa rall el Di al par amet er v al ue to 2. If the problem persists , try reducing it to 1.

5-22 MAX Administration Guide

Administering E1 and T1 Services

Troubleshooting ch anne ls

You might notice that the data appears to be corrupted on single or multichannel calls dialed from the U.S. to another country. On some international calls, the data service per channel is not conveyed by the WAN to the MAX unit answering the call. You mu st therefore set

Yes

64-Kbps channels. You might encounter a problem in which the first channel of an inverse multiplexing or MP+

call connects, but the call then clears or does not connect on the remain ing channels. Th e most common error in defining Line N profiles is specifying incorrect telephone numbers. The MAX unit cannot successfully build inverse multiplexing or MP+ calls if the telephone numbers in the Line N profile of the called unit are incorrect. The numbers that you specify in the Line N profile are the numbers local to your uni t. Do not en ter the teleph one numbers of the MAX unit you are calling. Enter those numbers in the Call profile, Destinatio n profile, or Connection profile.

in the Call profile. If you do not, the MAX unit incorrectly thinks that the call uses

Force

If the error message No Channel Avail appears in the message log display when the MAX unit tries to place a call, check the Line N profile configuration. This message can also indicate that

the lines’ cables have been disconnected or were installed incorrectly.

MAX Administration Guide 5-23

Administering ISDN

Troubleshooting BRI interface problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Displaying E1 ISDN call information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Displaying ISDN events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Understanding ISDN cause codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

In addition to observing a MAX unit’s indicator lights to gather information about the performance of the unit’s ISDN adapters and links, you can display information to resolve WAN calling errors that occur in outbound Net/BRI calls and to troubleshoot BRI interface problems. You can also display ISDN (including E1 ISD N ) call informatio n and use ISDN Cause codes to troubleshoot the performance of a MAX unit.

Troubleshooting BRI interface problems

Problems sometimes encountered with BRI interfaces include calls not dialed or answered reliably, Net/BRI lines not dialing or answering calls, apparent logical-link failures, and WAN calling errors in netbound Net/BRI calls.

WAN calling errors in outbound Net/BRI calls

Should you encounter a problem in which the Call Status window immediately indicates a WAN calling error when the MAX places a call on a Net/BRI module. Proceed as follows:

1 Check the value of the Data Svc parameter in the Call or Connection profile.

Try both the solves the problem.

2 Verify that you are using the correct dialing plan.

Depending on how the BRI l ines are configu red, you might need t o type f our , seven , or ten digits to communicate with the remote end.

Four-digit dial ing invo lves th e last four dig its of you r phone nu mber. For example, if your phone number is (415) 555-9015, four-digit dialing requires that you enter only the last four digits: 9015. Seven-digit dialing specifies that you dial the digits 5559015, and ten-digit dialing requires 4155559015.

If you are sending the incorrect number of digits, the MAX cannot route the call. Ask your carrier representative for the correct dialing plan, or simply try all of the possibiliti es.

3 Ask your carrier representative to verify explicitly that the line is capable of supporting

the call types you are requesting.

MAX Administration Guide 6-1

64K

and

56K

options for Data Svc, to see whether using a different value

Lucent MAX 6000, MAX, MAX 800, MAX 3000 Administration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Customer Service

Finding information and software

Obtaining technical assistance

Obtaining assistance through email or the Internet

Calling the technical assistance center (TAC)

Table of Contents

About This Guide

What you should know

Documentation conventions

The MAX documentation set

Administering MAX Hardware

Troubleshooting POST

Interpreting indicator lights

MAX 6000

MAX 3000

Troubleshooting the Fault indicator light

MAX 800

Troubleshooting the No Logical Link status

Troubleshooting the AIM port interface

Testing the AIM port interface

Calls fail between AIM ports

Excessive data errors on calls to AIM ports

Excessive handshaking on calls to AIM ports

Inbound data is scrambled during an AIM Static call

Troubleshooting a codec

The codec indicates that there is no connection

The codec does not receive data

The codec cannot establish a call

Calls initiated by control-lead toggling are cleared too soon

The codec cannot clear a call

Troubleshooting cable issues

Displaying interface statistics

Using modems to perform administrative tasks

Booting from a FAT-formatted PCMCIA card

Loading the software on the PCMCIA card

Managing files on the PC card

DO Commands and Administrative Tasks

Activating administrative permissions

Performing basic administration

Managing sessions

Using the DO Load command

Saving the VT100 layout

Saving the profile

Closing a Telnet session

Copying FXS profiles with the DO Commands

Managing calls

Testing and troubleshooting

Using bit-error tests

The statistics window and bit-error test

Using remote loopback

Using remote management

DO Command operations

Terminal-Server Administrative Tasks

Enabling and configuring the interface

Configuring the interface

Configuring the Session Options profile

Navigating to and from the interface

Testing the MAX unit

Understanding test results

Starting remote management sessions

Disconnecting user Telnet connections

Using Set commands

Enable password mode

Using Show commands

Displaying uptime and revision

Displaying modem status

Displaying V.110 terminal adapter status

Displaying call and user activity

Displaying active sessions

Displaying Dialed Number Information Service activity

Using the Show Filters command

Listing the filters in use

Displaying filter details

Displaying information related to virtual routing

Changing System Software Versions

Preparing to change system software