Installation and Administration Guide Version 5.1.4

NavisAccess DSL Installation and Administration Guide

Part Number: 7820-0387-006 For software version 5.1.4 May 2002 Copyright © 2002 Lucent Technologies Inc. All rights reserved. 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), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Lucent Technologies. For permission to reproduce or distribute, please email your request to [email protected].

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.

European Community (EC) RTTE compliance Hereby, Lucent Technologies, declares that the equipment documented in this publication is in compliance with the essential requirements and other relevant provisions of the Radio and Telecommunications Technical Equipment (RTTE) Directive 1999/5/EC. To view the official Declaration of Conformity certificate for this equipment, according to EN 45014, access the Lucent INS online documentation library at http://www.lucentdocs.com/ins.

Safety, compliance, and warranty Information Before handling any Lucent Access Networks hardware product, read the Edge Access Safety and Compliance Guide included in your product package. See that guide also to determine how products comply with the electromagnetic interference (EMI) and network compatibility requirements of your country. See the warranty card included in your product package for the limited warranty that Lucent Technologies provides for its products.

Security statement In rare instances, unauthorized individuals make connections to the telecommunications network through the use of access features.

Trademarks Lucent, the Lucent logo, and all Lucent brand and product names are trademarks or registered trademarks of Lucent Technologies Inc. Other brand and product names are trademarks of their respective holders.

Ordering Information You can order the most up-to-date product information and computer-based training online at http://www.lucentdocs.com/bookstore.

Feedback Lucent Technologies appreciates customer comments about this manual. Please send them to [email protected].

Lucent Technologies Customer Service

Product and service information, and software upgrades, are available 24 hours a day. Technical assistance options accommodate varying levels of urgency.

Finding information and software

To obtain software upgrades, release notes, and addenda for this product, log in to the Lucent Customer Support Service Center at http://www.lucent.com/support. The Lucent Customer Support Service Center also provides technical information, product information, and descriptions of available services. The center is open 24 hours a day, seven days a week. Log in and select a service.

Obtaining technical assistance

The Lucent Customer Support Service Center at http://www.lucent.com/support provides access to technical support. You can obtain technical assistance through email or the Internet, or by telephone. If you need 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 a live chat. Select one of these sites when you log in to http://www.lucent.com/support.

Calling the technical assistance center (TAC)

If you cannot find an answer through the tools and information or if you have a very urgent need, contact TAC. Access the Lucent Customer Support Service Center at http://www.lucent.com/support 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 1-800-272-3634 for a menu of Lucent services, or call +1 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.

NavisAccess DSL Installation and Administration Guide iii NavisAccess DSL Installation and Administration Guide iv Contents

Customer Service ...... iii What is in this guide...... xi Documentation conventions...... xi Documentation set...... xii Preparing for installation...... xiii Determining the License type ...... xiii Determining installation type...... xiii Using the devices defined in NavisAccess DSL...... xiv SNMP access to Lucent devices ...... xiv NavisAccess DSL UDP ports...... xv System requirements...... xv NavisAccess DSL server configuration recommendations ...... xv Patches Used ...... xvii

Chapter 1 Standalone Installation...... 1-1 Getting ready to install: Things to know...... 1-1 NavisAccess DSL installation step summary: Solaris standalone...... 1-3 NavisAccess DSL standalone installation...... 1-4 Starting NavisAccess DSL...... 1-7

Chapter 2 Distributed Installation ...... 2-1 Getting ready to install: Things to know...... 2-1 Prerequisites for distributed installation ...... 2-3 The Distribution Plan...... 2-3 Assessing the relative power rating ...... 2-3 NavisAccess DSL component distribution ...... 2-4 NavisAccess DSL installation step summary: Distributed installation ...... 2-6 Primary server installation and creation of Distribution Plan...... 2-8 Secondary server installation ...... 2-12 Workstation installation ...... 2-14 Additional Steps...... 2-15 Starting NavisAccess DSL...... 2-17 Modifying your distribution plan...... 2-18 Adding components ...... 2-18 Redistributing componenets ...... 2-22

Chapter 3 Upgrading your NavisAccess installation ...... 3-1 Getting ready to install: Things to know...... 3-1 What versions can be upgraded ...... 3-3 What is upgraded ...... 3-3 NavisAccess Installation table ...... 3-4

NavisAccess DSL Installation and Administration Guide v Contents

Installation types...... 3-4 Standalone Installation...... 3-5 NavisAccess installation summary ...... 3-5 Upgrading from a Live to a Live installation ...... 3-6 Upgrading from a Demo to a Live installation ...... 3-7 Upgrading from a Demo to a Demo installation...... 3-8 Additional steps ...... 3-9 Starting NavisAccess ...... 3-11 Distributed Installation...... 3-12 NavisAccess installation step summary...... 3-12 Upgrading from a Live to a Live installation ...... 3-13 Primary Server installation ...... 3-13 Secondary Server Installation...... 3-14 Workstation installation...... 3-15 Upgrading from a Demo to a Live installation ...... 3-16 Primary Server Installation...... 3-16 Secondary Server Installation...... 3-18 Workstation Installation ...... 3-20 Upgrading from a Demo to a Demo installation...... 3-21 Primary server installation...... 3-21 Secondary Server installation ...... 3-22 Workstation installation...... 3-23 Additional Steps...... 3-24 Starting NavisAccess ...... 3-26

Chapter 4 Preparing Lucent Devices for Use with NavisAccess DSL...... 4-1 Overview...... 4-2 Device TAOS Software Requirements ...... 4-2 About the Network Management Option ...... 4-2 Preparing Lucent Devices ...... 4-3 Stinger/Stinger LS Preparation ...... 4-3 Enabling SNMP v1and configuring SNMP parameters on the Stinger...... 4-4 Configuring SNMPv1 trap destinations for the Stinger...... 4-5 Enabling SNMP v3 and configuring SNMP parameters on the Stinger...... 4-8 Creating a SNMPv3 user profile for the Stinger...... 4-9 Creating a SNMPv3 trap notifications profile for the Stinger ...... 4-10 Creating a SNMPv3 target profile for the Stinger ...... 4-11 Configuring SNMP v3 trap destinations for the Stinger...... 4-12 Configuring a Soft IP address on the Stinger ...... 4-15 Configuring a Global IP address on the Stinger ...... 4-16 Enable call logging on the Stinger...... 4-16 Enable call-logging for evaluation purposes ...... 4-19 DSL TNT Preparation...... 4-19 Enabling SNMP, community strings on the DSLTNT ...... 4-20 Configuring SNMP Trap destinations for the DSLTNT ...... 4-22 Configuring a Global IP address on the DSLTNT ...... 4-24 DSLMAX and DSLTerminator Preparation...... 4-25 Setting SNMP community strings for the DSLMAX and DSLTerminator...... 4-25 Configuring trap destinations for the DSLMAX and DSLTerminator...... 4-27 Setting SNMP v3 for the DSLTerminator and DSLMAX ...... 4-28 Configuring SNMP Security on the DSLMAX and DSLTerminator...... 4-30 vi NavisAccess DSL Installation and Administration Guide Contents

Chapter 5 Security...... 5-1 Security in NavisAccess DSL ...... 5-2 Users and user groups ...... 5-2 Pre-defined users...... 5-2 Pre-defined user groups ...... 5-3 Working with access rights...... 5-4 Pre-defined user group access rights ...... 5-5 Pre-defined user group permissioned features and functions...... 5-6 Pre-defined user group permissioned operations...... 5-11 User Manager...... 5-12 Edit user ...... 5-13 Edit user: group membership...... 5-14 Define a new user ...... 5-15 Define user: group membership ...... 5-16 Edit an existing user group ...... 5-17 Edit user group: data access...... 5-18 Edit user group: Feature Access ...... 5-18 Define a new user group...... 5-19 Define user group: data access ...... 5-20 Define user group: feature access...... 5-21 Logging out of NavisAccess DSL ...... 5-21 Logging into NavisAccess DSL ...... 5-21 Change password ...... 5-22 The User Session Manager applet...... 5-22 Using the User Session Manager applet ...... 5-23 Audit Trails ...... 5-24 Using the Audit Trails applet...... 5-25

Chapter 6 Device Discovery ...... 6-1 Introduction to Device Discovery ...... 6-2 Visual indicators for Discovery ...... 6-2 Automatic Discovery of Network Resources...... 6-4 Manual Discovery...... 6-4 Manually adding new devices...... 6-4 Discovery via the Master List ...... 6-5 The Master List...... 6-5 Generating a Master List ...... 6-5 Discovery using SNMP exploration ...... 6-5 Running the Explorer...... 6-6 Troubleshooting/Restarting Discovery ...... 6-7 Why did Discovery fail? ...... 6-7 Identifying an unknown device...... 6-8 Discovered device is marked undiscovered...... 6-8 To restart Discovery of a device ...... 6-8 To restart Discovery of multiple devices...... 6-9

Chapter 7 Database Maintenance ...... 7-1 Database tools ...... 7-2 DBMaint ...... 7-2 Clear Map Flags...... 7-3

NavisAccess DSL Installation and Administration Guide vii Contents

Backing-up the database ...... 7-3 Restoring the database ...... 7-5 Generating a fresh database ...... 7-8 Repairing a database ...... 7-10 Moving DB files ...... 7-10 Workstation prerequisites for Restore and Move options ...... 7-13 Backing-up the database without DBMaint...... 7-15 The cfgdbcron.ksh utility - Scheduling a database backup ...... 7-15 The db_backup utility ...... 7-17 db_backup syntax ...... 7-17 Manual restoration of the database ...... 7-19

Chapter 8 The Master List...... 8-1 The Master List ...... 8-2 Devices and Groups...... 8-2 Users and User Groups ...... 8-2 Types of Master Lists ...... 8-2 Processing the Master List ...... 8-3 Master List format: Devices and Interfaces...... 8-3 Master List format: Users, User Groups, and User Group Memberships ...... 8-4 Validation of information in the Master List ...... 8-8 Device and Interface information ...... 8-8 User and User Group information ...... 8-8 Processing a partial Master List: Device and Interface information ...... 8-9 Rules for processing the Master List: Device and Interface information ...... 8-9 Rules for processing the Master List: User and User Group information ...... 8-10 Importing terminology...... 8-10 Importing options ...... 8-11 Logging the progress Information ...... 8-15 Circuit status ...... 8-15 Actions to be taken when circuit status changes ...... 8-16 Device and interface status relationship ...... 8-16 The Master List Configurator (MLConfig)...... 8-16 Starting MLConfig from the command line ...... 8-17 Importing the Master List...... 8-17 MLConfig Command Line Options - Import ...... 8-18 Exporting the NavisAccess DSL database ...... 8-19 MLConfig Command Line Options - Export ...... 8-20 Creating a Master List from scratch...... 8-21 Generating the Master List using the MLConfig Launch Options Dialog ...... 8-22 Exporting Devices...... 8-22 Importing Devices...... 8-23 Exporting Groups...... 8-23 Importing a Group ...... 8-24 Exporting Users ...... 8-24 Importing Users ...... 8-24 Exporting User Groups ...... 8-24 Importing User Groups ...... 8-25 Exporting Users and User Groups ...... 8-25 viii NavisAccess DSL Installation and Administration Guide Contents

Chapter 9 Navis Device License Manager (NDLM)...... 9-1 Introduction...... 9-2 What are device licences? ...... 9-2 How Device Licences are updated...... 9-3 Who should use NDLM? ...... 9-3 Directory Structure ...... 9-3 Launching the NDLM...... 9-4 Setting the Advanced options ...... 9-5 Generating a Device License request file ...... 9-6 Step 1 ...... 9-6 Forwarding the request file...... 9-9 Processing the response file ...... 9-9 Step 2 ...... 9-9 Receiving a response file...... 9-10 Applying the license response file ...... 9-10 Reprocessing a file ...... 9-14 Log file samples...... 9-15 The request log file ...... 9-15 The response log file...... 9-17 NDLM error messages...... 9-18 Response File...... 9-20

Chapter 10 Uninstalling NavisAccess ...... 10-1 Appendix A Trap Forwarding...... A-1 Configuring Trap Forwarding...... A-1 Forwarding traps/events to a third party application ...... A-2 Loading MIBs onto the third party application ...... A-2 Adding a trap ...... A-2

Appendix B Multiple Standalone Installations on the Same LAN ...... B-1 Appendix C File Maintenance Notes...... C-1 Appendix D Multiple Server Farms on the Same LAN (Distributed Server)...... D-1 Distributed Server ...... D-1

Appendix E Workstation Installation on a Separate Subnet...... E-1 Determining the OSAGENT port ...... E-1 Determining the Primary Server DBServer name ...... E-1

Appendix F Configuring Printing...... F-1 Configuring Solaris...... F-1 Configuring printing within NavisAccess DSL...... F-1 Distributed Servers ...... F-2

NavisAccess DSL Installation and Administration Guide ix Contents

Appendix G The nautil Utility...... G-1 Using the nautil utility ...... G-1 Using the nautil utility to shutdown NavisAccess in a Distributed environment...... G-2 Distributed environment: Overview ...... G-2 Shutting down NavisAccess ...... G-2 Troubleshooting NavisAccess server processes with nautil ...... G-3 Process executables and NavisAccess Server components ...... G-4

Appendix H The TFTP Server ...... H-1 Configuring the TFTP Server ...... H-1 TFTP Server Setup...... H-1 Log File...... H-3 Port configuration ...... H-4 Configuring TFTP to work with a Network Address Translator (NAT) in a distributed NavisAccess environment ...... H-5 How NavisAccess performs TFTP in a NAT environment...... H-5 Port settings for a NAT setup ...... H-6 Configure TFTP to work with NAT (Standalone)...... H-7 Configure TFTP to work with NAT (Distributed) ...... H-9 Configure TFTP to work with Multi-homed NAT (Standalone) ...... H-11 Configure TFTP to work with Multi-homed NAT (Distributed) ...... H-12

Appendix I Copying Device Templates and Files...... I-1 Reusing Provisioning templates...... I-1 Copying templates ...... I-1 Reusing Master List files ...... I-1 Copying Master List files ...... I-1 Reusing the Device Configuration files...... I-2 Copying Device Configuration files ...... I-2

Appendix J License agreement ...... J-1

x NavisAccess DSL Installation and Administration Guide About This Guide

What is in this guide

This guide gives you step-by- step installation and device configuration instructions for installing NavisAccess as a standalone or distributed installation.

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 mono- Represents characters that you enter exactly as shown (unless the characters are space text also in italics—see Italics, below). If you could enter the characters but are not specifically instructed to, they do not appear in boldface. Italics Represent variable information. Do not enter the words themselves in 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. [ ] Square brackets indicate an optional argument you might add to a command. To include such an argument, type only the information inside the brackets. Do not type the brackets unless they appear in bold type. | Separates command choices that are mutually exclusive. > Points to the next level in the path to a parameter or menu item. The item that follows the angle bracket is one of the options that appears when you select the item that precedes the angle bracket. Key1-Key2 Represents a combination keystroke. To enter a combination 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 Con- trol key and press the H key.) Press Enter Means press the Enter, or Return, key or its equivalent on your computer. Note: Introduces important additional information.

! Warns that a failure to follow the recommended procedure could result in loss Caution: of data or damage to equipment.

NavisAccess DSL Installation and Administration Guide xi About This Guide Documentation set

Convention Meaning

! Warns that a failure to take appropriate safety precautions could result in physi- Warning: cal injury.

Warns of danger of electric shock. Warning:

Documentation set

Guide Description NavisAccess DSL User’s This manual describes and explains all NavisAccess Guide options, utilities and functions, and how to use them

xii NavisAccess DSL Installation and Administration Guide Read Me First

Preparing for installation

To prepare for NavisAccess DSL installation: • Determine the type of license • Determine the type of installation: standalone or distributed. • Provide proper SNMP access for all NavisAccess servers and workstations. • Setup Simple Network Timing Protocol (SNTP) on all NavisAccess servers prior to installation. Refer to the man pages for your operating system for detailed instructions. • Start the Solaris RPC Bind and Keyserv daemons. These daemons must be running prior to installing NavisAccess DSL. The script that starts these daemons is /etc/rc2.d/S71rpc.

Determining the License type

License type Description Demo Expires in 90 days from the date of installation Comp Expires in 180 days from the date of stamping Live Permanent production software.

Note: For a live license, you will need a license key. If running a Standalone Installation, please refer to Chapter 1, “Standalone Installation.” If running a Distributed Installation, please refer to Chapter 2, “Distributed Installation.”

Determining installation type

Before installing NavisAccess DSL, you must determine the proper type of installation for your needs.

NavisAccess DSL can be installed as a Standalone or Distributed System. Components are divided into server-side and client-side. The server includes the database, reporting and call processing. The client-side provides the graphical user interface (GUI) to workstations, Telnet and/or Xterm sessions.

Note: If you are installing more than one standalone or distributed system on the same LAN, please refer to “Multiple Standalone Installations on the Same LAN” on page B-1. • Standalone installation In a standalone configuration, one machine provides both server and client functionality.

NavisAccess DSL Installation and Administration Guide xiii Read Me First Preparing for installation

All components are installed on a single machine.However, Xterm and Telnet sessions can be run off of a standalone installation. • Distributed installation In a distributed server installation, the server components are distributed across one or more machines. This provides a mechanism for distribution of server-side processing. One or more client workstations must also be installed, to distribute client-side processing. Multiple Telnet and/or Xterm sessions may log in to the workstations. If all distributed components are installed on one physical machine, the client processing must still take place on one or more separate machines (i.e. workstations). That is, if a distributed installation is chosen, you cannot run Xterm and Telnet sessions off the servers. There must be at least one workstation installed to provide GUI processing. Main Server In a distributed environment, the database server (DBserver) resides on the Primary Server. The database server, in turn, contains the Distribution Plan. The Distribution Plan assigns components to the other machines in the “server farm” (an environment consisting of several machines is referred to as a “farm”). For this reason, whichever machine you assign as the main server must be installed first. DBMaint is installed on the same server as the Scheduling server and is also installed on the workstations. For multiple server farms, however, the Scheduling server and the DBserver are installed on different servers. Given the above scenario, to allow DBMaint to access the database files to perform its operations, you must mount the NavisAccess database directory, from the primary server, and have the same write privileges. In order to mount the database directory (in the primary server) to the secondary server, the directory path on both servers must be the same. For example, if the directory path in the primary server is /export/navis/database/..., the directory path in the secondary server must also be /export/navis/database/.... – Secondary Servers In a distributed environment, any of the servers other than the Main server, are considered Secondary Servers. A separate secondary server license key must be purchased for each Secondary Server in the server farm. – Workstation In a distributed environment, a workstation provides a local GUI software which in turn logs in to the server. Workstation performance is superior to using Xterm or Telnet, though functionality is the same. A separate Workstation license key must be purchased for each Workstation in the server farm. Xterm and Telnet sessions must log into a workstation, not into a Server. A separate Workstation license must be purchased for each simultaneous Xterm and Telnet session.

Using the devices defined in NavisAccess DSL

To save the devices you defined in NavisAccess DSL, use MLConfig to create a Master List of the devices. Please refer to Chapter 8, “The Master List.”

SNMP access to Lucent devices

Every NavisAccess DSL server and workstation must have SNMP access to all devices that NavisAccess DSL will manage. Therefore, when setting SNMP address security on your xiv NavisAccess DSL Installation and Administration Guide Read Me First System requirements

network devices, you must ensure that each NavisAccess DSL machine is listed in the range of IP addresses the device will respond to. Alternately, you can turn SNMP address security off.

NavisAccess DSL UDP ports

In order for NavisAccess DSL to run successfully, you need to know which firewall holes need to be opened in the event of the use of a firewall. The following table lists these ports which NavisAccess DSL utilizes.

Note: We strongly recommend that you use the default ports listed below, unless otherwise noted.

Utility UDP Default Ports

TFTP 69 If you are running two TFTP servers on one machine, you can configure a second port (other than 69) for the additional TFTP server. Port configuration is edited in the /etc/services. See “Port configuration” on page H-4 for full details.

SNMP 161

SNMP - Trap 162

Trap 1010 Forwarding Please see “Trap Forwarding” on page A-1 for full details.

Call-Logging 1646 Please refer to the chapter entitled, “System Options” in the NavisAccess DSL User’s Guide.

OSAGENT 1492 port number If you are installing more than one installation on the same LAN, you need to configure a different OSAGENT port for the second installation. Please see “Multiple Standalone Installations on the Same LAN” on page B-1 for details.

System requirements

NavisAccess DSL server configuration recommendations

NavisAccess DSL requires Solaris 2.6/7 CDE. NavisAccess can be installed as a standalone or as a distributed server configuration. However, a distributed server configuration provides the following advantages: • Safety mechanisms in scenarios where failure of a NavisAccess DSL component on one machine will not bring down the whole system. • A scalable solution that takes care of a site’s growing needs. By using a distributed configuration, NavisAccess DSL can manage more devices and services as the network size increases.

NavisAccess DSL Installation and Administration Guide xv Read Me First System requirements

Notes: 1. Larger reporting requirements, such as long duration or trending reports (reports run for time spans greater than a couple of hours on a standard number of devices, services, etc.) should be scheduled, and not run in real time. If you intend to run them in real time, you will need a separate server for the reporting component.

2. Hard disk space requirements are for NavisAccess DSL only.

The table below describes the system requirements for NavisAccess DSL.

Table i. NavisAccess DSL System Requirements

Devices/Ports Configuration Notes

Note: Both of these Standalone (Ultra 60 or • Number of NavisAccess DSL Clients: conditions must be met. equivalent): Total number of X-termed sessions cannot be more than 3 without performance impact. • < 200 Stingers – Dual CPU (300 MHz or • Client performance will be impacted • < 35,000 Ports higher) –RAM: 2 GB significantly if reports that take a considerable – Hard Disk Space: 18 GB time to execute are generated and run. – DB Cache: 128 MB – Swap Space: 4 GB

Note: Both of these Standalone (E-450 or • Total number of clients is five conditions must be met. equivalent): (5)(workstations or Xterm sessions). • < 750 Stingers – Four CPU (400 MHz or • < 200,000 Ports higher) –RAM: 4 GB – Hard Disk Space: 25 GB – DB Cache: 256 MB – Swap Space: 4 GB Note: Both of these Distributed - Two Server Farm • Total number of clients is five (5). conditions must be met. Primary and Secondary • Total number of services supported are up to servers (E-450 or equivalent): • <1000 Stingers 9,000. • <500,000 Ports Primary Server (400 MHz or higher) –Four CPUs –4 GB RAM – Hard Disk Space: 80 GB – DB Cache: 1024 MB – Swap Space: 8 GB Components: Database Server, Reporting Server, GUI Server, DSL Service Management Unit, Call Logging Streamer, Data Management Server

xvi NavisAccess DSL Installation and Administration Guide Read Me First Patches Used

Table i. NavisAccess DSL System Requirements (continued)

Devices/Ports Configuration Notes

Distributed - Two Server Farm Primary and Secondary servers) - continued:

Secondary Server (400 MHz or higher) –Four CPUs –2 GB RAM – Hard Disk Space: 10 GB – Swap Space: 4 GB Components: Call Logging Receiver, Auto-Grouping Engine, DSL Service Management Unit, Scheduling Server Workstation (Ultra 60 or equivalent) (Each workstation can support five Xterm sessions) – Dual CPU (300 MHz or higher) –RAM: 2 GB – Hard Disk Space: 18 GB – Swap Space: 4 GB

Note: If you will be using more than 1000 Stingers or 500,000 ports, or if you need to have more han 5 clients, please consult with your Lucent Sales Representative for configuration guidelines.

Patches Used

Obtaining patches from the NavisAccess CD

The patches on the NavisAccess CD are available at: NavisAccess/sol-patches/.

For directions to install the patches, refer to the NavisAccess/sol-patches directory. Select the readme.txt file that corresponds to the operating system version on which you will be installing NavisAccess.

Obtaining patches from the Web Patches may be obtained from the Lucent support site: http://www.lucent.com/support

Click to download the patch that corresponds to the Operating system version on which you will be installing NavisAccess. Once downloaded, open the readme.txt file for directions on installing the patches.

NavisAccess DSL Installation and Administration Guide xvii

Standalone Installation 1

SERIAL NUMBER FILE NEEDED: Before installing NavisAccess DSL, you must acquire a serial number file and a license key from Lucent Technologies. The file is obtained through the Lucent internet site. See your NavisAccess DSL box insert for details. You will need the Authorization Code that is enclosed with your NavisAccess DSL software. There is a 24 hour turn-around time for licensed key requests.

Note: Neither a serial number file nor a licence key is required if you are installing a 90-day evaluation copy. However, do not install an evaluation copy of NavisAccess DSL on top of a “live” copy. If you do so, your current database will be deleted.

Getting ready to install: Things to know

Please read the following prerequisites and preparatory steps before beginning installation of NavisAccess DSL.

Before proceeding with this installation, please read the preliminary information found in “Read Me First” on page -xiii.

Important! The RPC Bind and Keyserv daemons must be running prior to installing NavisAccess DSL. The script that starts these daemons is /etc/rc2.d/S71rpc. • Installation can be run from an X terminal. • All NavisAccess DSL files are installed with owner and group of the user who installed it. The files are given 755 as mode. This permission setting allows a non-root user to run NavisAccess. • NavisAccess DSL must be installed by a super user. • Solaris Power Management must be turned off on the NavisAccess Primary Server. For further information, refer to the man power.conf. • In order to use the NavisAccess DSL TFTP server, you must comment out the tftp line in the /etc/inetd.conf file by entering a number sign (#) in front of the line. This line will look similar to the following: tftp dgram udp wait root /usr/lbin/tftpd tftpd/opt/ignite/var/opt/ignite

NavisAccess DSL Installation and Administration Guide 1-1 Standalone Installation Getting ready to install: Things to know

• For proper display of NavisAccess DSL windows, you must ensure that the CDE environment setting for “Allow Primary Windows On Top” is checked.

• All servers and workstations in a NavisAccess DSL installation must have proper SNMP access to the network devices being managed. This includes proper setting of SNMP community strings in NavisAccess DSL. • X term performance will be improved by enhancing the video card on the machine used to X term into NavisAccess DSL. • When X terming to the server or from a Windows NT machine to UNIX, the Windows NT machine must be set to a maximum of 256 colors. • X terming is supported only on connections of 256K or higher. • If you are using XSoftware, please do not use TrueColor. • In order to use the NavisAccess Browse functionality, all mounted drives must be mounted with the following parameters: mount -o vers=2 • If you are using ssh X forwarding to display NavisAccess, the following lines must be added to the sshd configuration file (usually found in /etc/sshd_config): X11Forwarding = yes X11DisplayOffset = 10 • When using Telnet or Rlogin to run NavisAccess DSL, you must either log in as root or, if not logging in as root, run the .navisaccessprofile. • For both local and X term sessions, you must verify if the Display variable is set properly. To do so, at the command line enter: #echo $DISPLAY

1-2 NavisAccess DSL Installation and Administration Guide Standalone Installation Getting ready to install: Things to know

The Display is properly set if you receive one of the following responses: – :0.0 –:0.0 –:0.0 where “machine” refers to the machine from which you entered the command. If you receive no response from the command, display is not set properly. To set the Display environment variable, enter the following: export DISPLAY = nnn.nnn.nnn.nnn:0.0 where nnn.nnn.nnn.nnn is the IP address of the machine you are using.

NavisAccess DSL installation step summary: Solaris standalone

Note: For a detailed description of hardware requirements and component distribution, please refer to “System requirements” on page -xv of the Read me First chapter.

Use this summary as a checklist to ensure you follow all the steps for proper installation.Failure to follow all the steps outlined below may lead to problems starting or using NavisAccess DSL. Detailed installation instructions follow this list.

Prerequisites to installation:

q Solaris Operating System must be installed.

q CDE must be installed.

q NavisAccess DSL must be installed by a super user.

q NavisAccess DSL should run under the ksh.

q Required Installation system patches must be applied. The text file solpatch.txt tells which patches must be applied. The file solpatch.txt is located at: ftp.ascend.com/pub/Software-Releases/NavisAccess/Documentation/SOLARIS/solpatch.txt

Installation Steps:

q Step 1: Installation from the CD

q Step 2: Reboot system

q Step 3: Check status of services

q Step 4: Compile MIBs

NavisAccess DSL Installation and Administration Guide 1-3 Standalone Installation NavisAccess DSL standalone installation

NavisAccess DSL standalone installation

q Step 1: Installation from the CD 1 Insert the installation CD into the drive. 2 Change to the directory where the CD is mounted (usually /cdrom). 3 Change to the NavisAccess DSL directory and run the installation file by entering: ./setup -n -o Note: If you are executing more than one installation on the same LAN, refer to “Multiple standalone installation on the same LAN” on page B-1. 4 The “NavisAccess - Welcome” screen displays, prompting you to click [Cancel] to exit from any active applications before continuing with setup. 5 Click [Next] to continue if no applications are running. 6 The “Full Installation / Service Pack” screen displays. Please specify the installation type: – Full Installation - A fresh installation will take place. You will be prompted to enter a license key. Note: The database will be updated only if the existing or fresh installation is live. – Service Pack - The existing installation will be upgraded. The Database will be upgraded. A license key is not required. Note: The evaluation time period (if any) will not be extended. The Database must be running to install the Service Pack. 7 If performing a Full Installation, you will be prompted to locate a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a serial number file. The file is named liblock.so.

Note: If you are reinstalling NavisAccess DSL, the following message displays: Do you want to upgrade your existing database? Choosing Yes upgrades your database and your data is retained, choosing No will cause you to lose the existing data in your database. 8 The “NavisAccess-User Information” screen displays. Enter a User Name and Company name here and click [Next] to continue.

Note: The [Next] button will not activate until you enter all information on the User Information screen. 9 The Installation Type screen displays. Select Standalone and click [Next]. 10 You will be prompted to enter a License Key. The license key must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a License Key.

Enter the license key and click [OK]. The license key is an 18-character letter/number combination. It is case sensitive.

1-4 NavisAccess DSL Installation and Administration Guide Standalone Installation NavisAccess DSL standalone installation

11 The Target Directory screen displays with the default directory /export/home/navis. You can install NavisAccess DSL in the default directory or enter a new target directory path if you wish. Make sure that: – the directory has enough space. – there are no files in the target directory that you need (NavisAccess DSL overwrites all files in the entire target directory during the installation process). If there are files, move them to another directory. – the directory name is in lowercase letters as specified by the program, and it is a full name path. 12 Enter the directory in which NavisAccess DSL is to be installed. The directory must be all lower case as specified by the program, and it must be a full path. For example: /export/home/target_directory

Caution: The software installs to the exact directory path you specify. Be aware that any ! files in that directory will be deleted. You should always specify a new sub-directory to which NavisAccess DSL should be installed because all files in the final directory will be overwritten.

13 Click [Finish] to complete the installation. The Copying Files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete. At the Copying Files screen you can click [Cancel] to terminate the installation procedure. The About NavisAccess Installation screen displays, informing you that “NavisAccess is not properly installed. Are you sure you want to quit?”

q Step 2: Reboot system

Once the completion of the above steps, the Setup Status screen displays. This screen informs you that the database components were successfully installed. • Click [Yes] in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen.

q Step 3: Check status of services

All NavisAccess DSL services will start upon reboot. A utility, nautil, is provided to check the status of services and to start and stop them when needed. You should check the status of your services before proceeding.

Syntax for using nautil follows:

nautil start Starts NavisAccess DSL services

Note: Only Root user has permission to start any NavisAccess services that use port 1024 or less. status Shows status of services shutdown Shuts down services.

NavisAccess DSL Installation and Administration Guide 1-5 Standalone Installation NavisAccess DSL standalone installation

stop Shuts down services one at a time, giving you the option to stop individual services. This option is used when select services must be stopped.

Note: Only Root user has permission to stop any NavisAccess services that use port 1024 or less.

To check if NavisAccess DSL services are running, at the command line enter:

nautil status

A series of messages similar to the following will appear. X Virtual Frame Buffer Service is running. (PID id 9570) Database server is running. (PID id 10304) WindU(tm) Registry is running. (PID id 9625) WindU(tm) Service is running. (PID id 9635) osagent is running. (PID id 9755) edispatcher is running. (PID id 10480) tftp server is running. (PID id 10574) SNMP server is running. (PID id 10510) IMC is running. (PID id 10493) NMD Domain Server is running. (PID id 10561) SRM server is running. (PID id 10587)

If any services are displayed as not running, at the command line enter:

nautil start

Recheck the status when the startup procedure has completed.

q Step 4: Compile MIBs

Before using NavisAccess DSL, the necessary MIBs must be compiled. You must complete this step, even if you have compiled MIBs using a previous version of NavisAccess DSL. 1 To compile MIBs, after making sure the NavisAccess DSL services are running, enter the following command to open the MIB Compiler: mibc 2 Click the [Compile] button. The compilation process will begin and will be displayed in the MIB compiler window. Compiling of a MIB will generate messages reading: “Processing File: .”

1-6 NavisAccess DSL Installation and Administration Guide Standalone Installation Starting NavisAccess DSL

3 Upon completion of the compiling process, the MIB Compiler will write a binary file and then build a Trap database. If the entire process is successful, a screen similar to the one below will be displayed.

You are now finished with the installation process, and may start NavisAccess DSL.

Starting NavisAccess DSL

To start NavisAccess DSL, the environment must be set and the server services must be started. The user application (GUI) can then be started.

To start NavisAccess DSL: 1 Make sure the NavisAcces services are running. At the command line enter: nautil status to check status of the services. (For full details on the nautil utility, see “Step 3: Check status of services” on page 1-5.) 2 After verifying that all services are running, enter the following: srm & The srm executable starts the NavisAccess DSL graphical user interface. 3 The first time you start NavisAccess DSL, the default User Name and password are Admin and Admin. Startup Tip If you are starting NavisAccess DSL via a Telnet session from another Solaris machine, make sure you have properly exported the display. Telnet into the NavisAccess DSL workstation from the local machine and at the command line enter: export DISPLAY=x.x.x.x:0.0 where x.x.x.x = the IP address of then local machine.

NavisAccess DSL Installation and Administration Guide 1-7 Standalone Installation Starting NavisAccess DSL

1-8 NavisAccess DSL Installation and Administration Guide Distributed Installation 2

SERIAL NUMBER FILE NEEDED: Before installing NavisAccess DSL, you must acquire a serial number file and license key from Lucent Technologies for each server and /or workstation you are installing. The file is obtained through the Lucent internet site. See your NavisAccess DSL box insert for details. You will need the Authorization Code that is enclosed with your NavisAccess DSL software. There is a 24 hour turn-around time for licensed key requests.

Getting ready to install: Things to know

Please read the following prerequisites and preparatory steps before beginning installation of NavisAccess DSL.

Before proceeding with this installation, please read the preliminary information found in “Read Me First” on page -xiii.

Important! The RPC Bind and Keyserv daemons must be running prior to installing NavisAccess DSL. The script that starts these daemons is /etc/rc2.d/S71rpc. • Installation can be run from an X terminal or a character terminal. • All NavisAccess DSL files are installed with owner and group of the user who installed it. The files are given 755 as mode. This permission setting allows a non-root user to run NavisAccess. • NavisAccess DSL must be installed by a super user. • Solaris Power Management must be turned off on the NavisAccess Primary Server. For further information, refer to the man power.conf. • In order to use the NavisAccess DSL TFTP server, you must comment out the tftp line in the /etc/inetd.conf file by entering a number sign (#) in front of the line. This line will look similar to the following: tftp dgram udp wait root /usr/lbin/tftpd tftpd/opt/ignite/var/opt/ignite

NavisAccess DSL Installation and Administration Guide 2-1 Distributed Installation Getting ready to install: Things to know

• For proper display of NavisAccess DSL windows, you must ensure that the CDE environment setting for “Allow Primary Windows On Top” is checked.

2-2 NavisAccess DSL Installation and Administration Guide Distributed Installation Getting ready to install: Things to know

where “machine” refers to the machine from which you entered the command. If you receive no response from the command, display is not set properly. To set the Display environment variable, enter the following: export DISPLAY = nnn.nnn.nnn.nnn:0.0 where nnn.nnn.nnn.nnn is the IP address of the machine you are using.

Prerequisites for distributed installation

Note: For a detailed description of hardware requirements and component distribution, please refer to “System requirements” on page -xv

A distributed installation consists of NavisAccess DSL components being installed on two or more machines. During the installation process, through the Distribution Plan, you will be prompted to enter information based on your knowledge of the machine environment at your site.

Note: All server components may be installed on a single machine. However, with a distributed installation, at least one separate workstation installation is required in order to run the client-side components.

The Distribution Plan

As part of the installation process, you must define the NavisAccess DSL Distribution Plan. The Distribution Plan consists of two steps. • Step 1: Defining the machines • Step 2: Distributing Components

The Distribution Plan is defined during installation on the first machine. NavisAccess DSL then stores the Distribution Plan in its database. Each subsequent machine installation reads the information from the Distribution Plan to determine proper components to install.

Assessing the relative power rating

You can use the power rating information you furnish as part of the criteria to balance component load distribution. By knowing the relative strength of each machine in relation to the other machines, you can distribute the component load accordingly.

The Relative Power Rating scale is 100-1000. Rate your machine in relation to each other using this scale. Your most powerful machine would have the highest relative rating in comparison to the least powerful machine in the farm.

Consider the number and speed of the CPUs, the speed of the hard drive, and the amount of RAM when deciding on a power rating for each machine.

Example

Suppose that your machine farm consists of three servers with the following specifications. Based on these specifications, you might give them the relative power rating displayed in column three, and distribute the components as displayed in column four.

NavisAccess DSL Installation and Administration Guide 2-3 Distributed Installation NavisAccess DSL component distribution

Server System Specifications Relative Power Possible Component Distribution Rating

A dual 400mhz 12GB RAID 0 900 DB Server, DSMSC, NavisAccess DSL 384MB Server, Reporting Server

B 400mhz 4GB 384 MB 800 Call Logging Receiver, Checkpoint Handler, Auto Group Engine, Gui Servers

C 400mhz 4GB 384 MB 800 Running Unit (PME, DSTC, etc), GuiSrv

Remember that relative power rating has interpretive value only when machines are rated in relation to one another.

In essence, you are ranking your machines hierarchically, based on certain criteria. The hierarchy is reflected in the relative power rating value.

! Caution: Because the Distribution Plan must be written to the NavisAccess DSL database, NavisAccess DSL forces the installation of the Database server component on the first machine you entered as one of the machines in the farm. Therefore, the machine that will be your primary server must be entered first. You cannot override this.

Distribution Planning, Step 2: Distribute your components

Manually distribute the NavisAccess DSL components among the machines defined by you (in the Distribution Planning, Step 1 screen), or to Modify the component distribution.

On this screen, you can Add, Modify or Delete information for a machine.

NavisAccess DSL component distribution

If you are installing a Distributed Server configuration, efficient distribution of the NavisAccess DSL components is paramount. This section lists and briefly describes each component and how it should be distributed.

The following table describes the NavisAccess DSL components and their relative resource needs in terms of CPU utilization, memory and disk space. You should allocate your hardware appropriately based on these considerations.

Some components can be distributed only on one server, others can be installed multiple times on different servers to distribute processing.

In the table below, the following relative utilization levels apply for CPU, Memory and Disk Space utilization.

2-4 NavisAccess DSL Installation and Administration Guide Distributed Installation NavisAccess DSL component distribution

Keep in mind that these are relative ratings, not absolute. They should be used as guidelines to determine which components get installed on which machines in your NavisAccess DSL farm.

Table 2-1. NavisAccess DSL components and their function

Component Name and Description Relative Ratings Relative ratings

Database Server Contains the Sybase Database Server. It also has the CPU usage = high Osagent which facilitates communication between Disk space = high different CORBA objects. Memory usage = high • This component can be installed only once

Scheduling Server The Scheduling Server is the background component of CPU usage = low the NavisAccess DSL GUI (user interface). It processes Disk space = low background scheduling and background auto discovery. Memory usage = medium • This component can be installed only once

Auto Grouping Engine This component triggers auto discovery and creates CPU usage = high Linegroups and Services based on call logging packets Disk space = low received from devices. Memory usage = low • This component can be installed only once

Call Logging Streamer Receives Call Logging packets in real-time and stores CPU usage = low them on disk. These files are later used by the reporting Disk space = high modules. Memory usage = low

The Call Logging Streamer database component (clrdata) should be on the same machine as the Reporting Server. If these two components are on separate servers, you need to mount the /clrdata directory so that data can be accessed by the Reporting Server. • This component can be installed only once

Data Management The Data Management Server contains the following: CPU usage = medium Server • Event Streamer: This stores the events in the Disk space = low database. Memory usage = low • Adaptive Performance Monitor: Processes DSL Service data that is periodically written to the database. It calculates weighted averages of that data and restores it to the database as a performance template for each service. This template is then usable for adaptive threshold monitoring. • Progress/Disconnect View Server: This is the back-end process that responds to user requests to view the Progress/Disconnect Viewer suite of applets. • This component can be installed only once.

NavisAccess DSL Installation and Administration Guide 2-5 Distributed Installation NavisAccess DSL component distribution

Table 2-1. NavisAccess DSL components and their function (continued)

Component Name and Description Relative Ratings Relative ratings

DSL Service Processes real-time DSLdevice traffic into per-service, CPU usage = high Management Unit per-interval averages. This data is then streamed to the Disk space = low database and is also available for applets such as DSL Memory usage = high

Watch. • This component can be installed multiple times.

Call Logging Receiver Receives call logging packets and routes them to all CPU usage = high interested processes such as the DSL Service. Disk space = low

• This component can be installed multiple times. Memory usage = medium

GUI Server This is the back-end process responsible for collecting and CPU usage = medium publishing data specific to the distributed GUI applets Disk space = low

such as Examiner, DSL Watch, Active Sessions, etc. If Memory usage = medium you will be running multiple workstations and/or Xterm sessions, it is advisable to install the GUI server on a separate machine. All workstations and Xterms should then log into that machine. • This component can be installed multiple times.

Reporting Server This processes front-end and back-end requests for CPU usage = low reports. It generates the report’s display data and publishes Disk space = low

it to the client for viewing. If you will be have multiple Memory usage = high workstations and/or Xterm sessions running reports, it is advisable to install the Reporting Server on a separate machine.

The Reporting Server component should be on the same machine as the Call Logging Streamer. If these two components are on separate servers, you need to mount the machines so that data can be accessed. • This component can be installed multiple times.

NavisAccess DSL installation step summary: Distributed installation

Use this SUMMARY as a checklist to ensure you follow all the steps for proper installation. Failure to follow all the steps outlined below may lead to problems starting or using NavisAccess DSL. Detailed installation instructions follow this list.

Prerequisites to installation

The following prerequisites apply to the primary server, secondary server(s) and the workstation. Prerequisites that apply to a specific device are noted as such.

q Solaris Operating System must be installed.

q CDE must be installed.

2-6 NavisAccess DSL Installation and Administration Guide Distributed Installation NavisAccess DSL component distribution

q NavisAccess DSL must be installed by a super user.

qRequired installation system patches must be applied. Important! Applicable for distributed installations on E450s and E420s only. Before installing NavisAccess, please make sure to install the right patches for solaris. Please use the solaris patches dated August 31st 2000. Please do not use any other solaris patches. The text file solpatch.txt tells which patches must be applied. The file solpatch.txt is located at: ftp.ascend.com/pub/Software-Releases/NavisAccess/Documentation/SOLARIS/solpatch.txt

q Primary Server: Have available the name and IP address of every machine designated for Distributed Server configuration.

q Secondary Server(s): primary server must be installed before secondary server configuration.

Note: Before installing any workstation ensure that all services are running.

q Workstation: Secondary server(s) must be installed before Workstation configuration

q Go to the Lucent NavisAccess website to get your Serial Number File and License Keys.

Note: You should access the website a full day before you intend to install NavisAccess DSL. There is a 24-hour turn-around between submitting your request and delivery of the key(s) and the serial number file.

Installation Steps

Primary Server installation and creation of Distribution Plan q Step 1: Installation of primary server from the CD q Step 2: Reboot system

Secondary server installation q Step 3: Installation of Secondary server(s) from CD q Step 4: Reboot Secondary server(s)

NavisAccess DSL Installation and Administration Guide 2-7 Distributed Installation Primary server installation and creation of Distribution Plan

Workstation installation q Step 5: Installation of Workstation(s) from CD q Step 6: Reboot workstation

Additional Steps q Step 7: Check status of services q Step 8: Compile MIBs on all Workstations

Primary server installation and creation of Distribution Plan

q Step 1: Installation of Primary server from the CD 1 Insert the installation CD into the drive. You must begin installation with the CD in the machine that will be used as the primary (database) server. 2 Change to the directory where the CD is mounted (usually /cdrom). 3 Change to the NavisAccess DSL directory and run the installation file by entering: ./setup -n -o

Note: If you have multiple NavisAccess DSL farms on the same LAN, please refer to Appendix D, “Multiple Server Farms on the Same LAN (Distributed Server).” 4 The “NavisAccess - Welcome” screen displays, prompting you to click Cancel to exit from any active applications before continuing with setup. 5 Click [Next] to continue if no applications are running. 6 The “Full Installation / Service Pack” screen displays. Please specify the installation type:

– Full Installation - A fresh installation will take place. You will be prompted to enter a license key. Note: The database will be updated only if the existing or fresh installation is live.

– Service Pack - The existing installation will be upgraded. The Database will be upgraded. A license key is not required. Note: The evaluation time period (if any) will not be extended. The Database must be running to install the Service Pack. 7 If performing a Full Installation, you will be prompted to locate a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a serial number file. The file is named liblock.so.

Note: If you are reinstalling NavisAccess DSL, the following message displays: Do you want to upgrade your existing database? If you click Yes, your database is upgraded and no data is lost. If you click No, you lose all your data in the database and you must rebuild it.

2-8 NavisAccess DSL Installation and Administration Guide Distributed Installation Primary server installation and creation of Distribution Plan

8 The “NavisAccess-User Information” screen displays. Enter a User Name and Company name here and click [Next] to continue.

Note: The [Next] button will not activate until you enter all information on the User Information screen. 9 The Installation Type screen displays. Select Distributed and click [Next]. The “Distribution Planning, Step 1” screen displays. This screen will be used to enter the names and IP addresses of all machines that will be part of the NavisAccess DSL server farm. NavisAccess DSL workstations do not need to be entered.

Note: Remember that NavisAccess DSL forces the installation of the database server component on the first machine (the main server) entered as one of the machines in the farm. You cannot override this. 10 Enter the name and IP address of the primary server. Note the following before proceeding:

– The IP address of the primary server is automatically filled in. You must be installing from the CD drive on the primary server.

– The first machine entered into the distribution plan must be the primary server, which will contain the NavisAccess DSL database, plus other selected components. Typically, this should be the most powerful machine in the server farm.

– The “Machine Name” field is used only by NavisAccess DSL. It does not need to match the actual system name of the machines. However, it is advisable to make the names match to eliminate a possible source of confusion.

The Primary Server is always listed first.

11 Enter the Primary Server license key in the “License Key” field.

Note: The Primary Server license must be obtained from Lucent Technologies. Make sure you are entering a Primary Server license key, and not a Secondary Server license key. Only one Primary Server key is needed per installation.

NavisAccess DSL Installation and Administration Guide 2-9 Distributed Installation Primary server installation and creation of Distribution Plan

12 Move the Relative Power Rating slide bar to reflect the relative performance status of the machine. This is only used as a guideline, it does not affect the installation process.

Modifying a machine entry All the machine entries are displayed in the table (at the bottom of the screen). You cannot edit the information in the table. To edit: 1 Highlight the row you want to modify in the table section of the screen. The machine information is displayed on the upper section of the screen, in the Machine Name and IP Address fields. 2 Edit the information as needed and press Modify.

Deleting a machine entry To delete information in the distribution plan: 1 Highlight the row you want to delete in the table section of the screen. 2 Click [Delete]. The machine entry is deleted.

Note: The Primary Server cannot be deleted.

3 Click [Next] when you have entered all the machines. The “Distribution Planning, Step 2” screen displays with the database server assigned. Use this screen to manually distribute the NavisAccess DSL components among the machines defined in the previous screen or to modify the component distribution. You can click the:

– “Component Name” field to display a pull-down menu listing all the available components.

– “Machine Name” field to display the defined machines. 4 Components are assigned one at a time. Certain components can only be installed once. Others can be installed multiple times across multiple machines. The following table lists the components and their distribution possibilities.

Component Name No. of times component can be distributed

Database Server One

Scheduling Server One

Auto Grouping Engine One

Checkpoint Handler One

Dial Service Totals Engine One

Call Logging Streamer One

2-10 NavisAccess DSL Installation and Administration Guide Distributed Installation Primary server installation and creation of Distribution Plan

Component Name No. of times component can be distributed

Data Management Server One

Dial Service Management Unit Multiple

Call Logging Receiver Multiple

GUI Server Multiple

Reporting Server Multiple

See the section “NavisAccess DSL component distribution” on page 2-4 for details on how to distribute the components. 5 To assign a component, click the component field. A list of the available components displays. Select the component you need. 6 Click the Machine Name field. Highlight the machine on which you want to install the component and click Add. Note the following regarding component distribution: – Single-instance components are removed from the “Component Name” field as they are assigned to machines. – Multiple-instance components are incremented by one each time they are assigned to a machine. The “Component Name” display will indicate the number of times the component has been assigned. For example, if two GUI servers were assigned, it would appear like this: [1]GUI Server 7 Repeat the above steps until all components are distributed. You must distribute all the available components among the machines. The [Next] button is activated only after you have done this. Once you have assigned all the components to the machines, the Setup Wizard writes this information to the NavisAccess DSL Database, and proceeds to install the appropriate components to each machine. 8 Click Next when the component distribution is complete. 9 The Target Directory screen displays with the default directory /export/home/navis. You can install in the default directory or enter a new target directory path if you wish. Make sure that: – the directory has enough space. – there are no files in the target directory that you need (NavisAccess DSL overwrites them during the installation process). If there are, move them to another directory. – the directory name is in lowercase letters as specified by the program, and it is a full name path. 10 Enter the directory in which NavisAccess DSL is to be installed and click [Next]. (If no such directory exists, it prompts you whether such directory should be created. Click YES if you wish to do so.) 11 The “Are You Sure?” screen displays, warning you that all files in the Installation Directory will be deleted.

NavisAccess DSL Installation and Administration Guide 2-11 Distributed Installation Secondary server installation

The software installs to the exact directory path you specify. Be aware that any files in that ! directory will be deleted. You should always specify a new sub-directory to which NavisAccess DSL should be installed because all files in the final directory will be overwritten. 12 Click [Finish] to complete the installation.

The Copying files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory.

Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

To quit installation:

At the Copying Files screen you can click [Cancel] to terminate the installation procedure. A screen displays, informing you that “NavisAccess is not properly installed. Are you sure you want to quit?”

You will then be prompted with “NavisAccess must be installed on the following servers:” It will list the servers that you have defined as part of the farm.

q Step 2: Reboot system

A message is displayed that says, “The following servers must be re-installed. . .” and then lists the servers.

Secondary server installation

q Step 3: Installation of Secondary server(s) from CD

Note: Your installed primary server must be up before proceeding with the secondary server(s) installation.

Note: If using the osagent port, you must use the same osagent port as the Primary Server.

At a terminal window command prompt. 1 Insert the installation CD into the drive of a secondary server machine. This machine must have been included in the distribution plan created in Step 1. 2 Change to the directory where the CD is mounted (usually /cdrom). 3 Change to the NavisAccess DSL directory and run the installation file by entering: ./setup -n -o Note: If you have multiple NavisAccess DSL farms on the same LAN, please refer to Appendix D, “Multiple Server Farms on the Same LAN (Distributed Server).”

2-12 NavisAccess DSL Installation and Administration Guide Distributed Installation Secondary server installation

4 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. 5 The “Full Installation / Service Pack” screen displays. Please specify the installation type: – Full Installation - A fresh installation will take place. You will be prompted to enter a license key. Note: The database will be updated only if the existing or fresh installation is live. – Service Pack - The existing installation will be upgraded. The Database will be upgraded. A license key is not required. Note: The evaluation time period (if any) will not be extended. The Database must be running to install the Service Pack. 6 If performing a Full Installation, you will be prompted to locate a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a serial number file. The file is named liblock.so. 7 The NavisAccess Assigned Components screen displays. The installation program reads the distribution plan in the database on the primary server to learn which components belong on each secondary server. The Component Name window of this screen displays the components that you assigned to this particular server. 8 Verify that Proceed is checked, and click Next. The Target Directory screen displays. Make sure that: – the chosen directory has enough space. – there are no files in the target directory that you need (NavisAccess DSL overwrites them during the installation process). If there are, move them to another directory. – the directory name is in lowercase letters as specified by the program, and it is a full name path. 9 Enter the directory in which NavisAccess DSL is to be installed. (If no such directory exists, it prompts you whether such directory should be created. Click Yes if you wish to create the directory.) 10 The “Are You Sure” screen displays, warning you that all files in the Installation Directory will be deleted. The software installs to the exact directory path you specify. Be aware that any files in that ! directory will be deleted. You should always specify a new sub-directory to which NavisAccess DSL should be installed because all files in the final directory will be overwritten. 11 Click Finish to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

q Step 4: Reboot system

A message is displayed saying, “The following servers must be re-installed . . .” and then lists the servers.

Once Steps 1 through 3 are completed, the Setup Status screen displays. This screen informs you that the database components were successfully installed.

NavisAccess DSL Installation and Administration Guide 2-13 Distributed Installation Workstation installation

• Click Yes in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen.

Workstation installation

q Step 5: Installation of Workstation(s) from CD

At a terminal window command prompt. 1 Insert the installation CD into the Workstation drive. 2 Change to the directory where the CD is mounted (usually /cdrom). 3 Change to the NavisAccess DSL directory and run the installation file by entering: ./setup -n -o Note: If you intend to install your workstation on a separate subnet, please refer to “Workstation Installation on a Separate Subnet” on page E-1.

Note: If you have multiple NavisAccess DSL farms on the same LAN, please refer to Appendix D, “Multiple Server Farms on the Same LAN (Distributed Server).” 4 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. 5 The “Full Installation / Service Pack” screen displays. Please specify the installation type: – Full Installation - A fresh installation will take place. You will be prompted to enter a license key. Note: The database will be updated only if the existing or fresh installation is live. – Service Pack - The existing installation will be upgraded. The Database will be upgraded. A license key is not required. Note: The evaluation time period (if any) will not be extended. The Database must be running to install the Service Pack. 6 If performing a Full Installation, you will be prompted to locate a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a serial number file. The file is named liblock.so. 7 The Workstation Installation screen displays, indicating that no server components are assigned to this machine. By default, the “Proceed” radio button is checked. Click [Next] to continue. The “Override” button will bring you to a server installation screen. 8 You will be prompted to enter a Workstation License Key. The license key must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a License Key.

Enter the license key and click [OK]. The license key is an 18-character letter/number combination. It is not case sensitive.

2-14 NavisAccess DSL Installation and Administration Guide Distributed Installation Workstation installation

9 The Target Directory screen displays with the default directory /export/home/navis. You can install in the default directory or enter a new target directory path. Make sure that: – the directory has enough space. – there are no files in the target directory that you need (NavisAccess DSL deletes all the files in the entire directory during the installation process). If there are files, move them to another directory. – the directory name is in lowercase letters as specified by the program, and it is a full name path 10 Enter the directory in which NavisAccess DSL is to be installed. (If no such directory exists, it prompts you whether such directory should be created. Click Yes if you wish to create the directory.) 11 The “Are You Sure” screen displays, warning you that all files in the Installation Directory will be deleted. The software installs to the exact directory path you specify. Be aware that any files in that ! directory will be deleted. You should always specify a new sub-directory to which NavisAccess DSL should be installed because all files in the final directory will be deleted. 12 Click [Finish] to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

q Step 6: Reboot system

Once the completion of the above steps, the Setup Status screen displays. This screen informs you that the database components were successfully installed. • Click Yes in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen.

Additional Steps q Step 7: Check status of services

NavisAccess DSL Installation and Administration Guide 2-15 Distributed Installation Workstation installation

Syntax for using nautil follows:

nautil start Starts NavisAccess DSL services Note: Only the Root user has permission to start any services that use port 1024 or less. status Shows status of services shutdown Shuts down all services. stop Shuts down services one at a time, giving you the option to stop individual services. This option is used when select services must be stopped.

Note: Only the Root user has permission to stop any services that use port 1024 or less.

To check if NavisAccess DSL services are running, at the command line enter:

nautil status

2-16 NavisAccess DSL Installation and Administration Guide Distributed Installation Starting NavisAccess DSL

If any services are displayed as not running, at the command line enter:

nautil start

Recheck the status when the startup procedure has completed. q Step 8: Compile MIBs on Workstations

Before using NavisAccess DSL, the necessary MIBs must be compiled on each workstation in the system. You must complete this step, even if you have compiled MIBs using a previous version of NavisAccess DSL. 1 To compile MIBs, after making sure the NavisAccess DSL services are running, enter the following command to open the MIB Compiler: mibc 2 Click the [Compile] button. The compilation process will begin and will be displayed in the MIB compiler window. Compiling of a MIB will generate messages reading: “Processing File: .” 3 Upon completion of the compiling process, the MIB Compiler will write a binary file and then build a Trap database. If the entire process is successful, a screen similar to the one below will be displayed.

You are now finished with the installation process, and may start NavisAccess DSL.

Starting NavisAccess DSL

To start NavisAccess DSL, the environment must be set and the server services must be started. The user application (client GUI) can then be started on any workstation logging in to the server.

NavisAccess DSL Installation and Administration Guide 2-17 Distributed Installation Modifying your distribution plan

To start NavisAccess DSL: 1 Make sure the NavisAccess DSL services are running. To check status of the services, at the command line enter: nautil status (For full details on the nautil utility, see “Step 7: Check status of services” on page 2-8.) 2 After verifying that all services are running, enter the following: srm & The srm executable starts the NavisAccess DSL graphical user interface. 3 The first time you start NavisAccess DSL, the default User Name and password are Admin and Admin.

Note: If you are starting NavisAccess DSL via a Telnet session from another Solaris machine, make sure you have properly exported the display. Telnet into the NavisAccess DSL workstation from the local machine and at the command line enter: export DISPLAY=x.x.x.x:0.0 where x.x.x.x = the IP address of the local machine.

Modifying your distribution plan

Adding components

Adding components to the existing NavisAccess Server requires you to install NavisAccess onto a new Server. During installation, choose the components that you wish to add.

Installation from CD

At a terminal window command prompt: 1 Insert the installation CD into the Workstation drive. 2 Change to the directory where the CD is mounted (usually /cdrom). 3 Change to the NavisAccess DSL directory and run the installation file by entering: ./setup -n Note: If you intend to install your workstation on a separate subnet, please refer to “Workstation Installation on a Separate Subnet” on page E-1.

2-18 NavisAccess DSL Installation and Administration Guide Distributed Installation Modifying your distribution plan

6 If performing a Full Installation, you will be prompted to locate a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a license file. The file is named liblock.so. 7 The Workstation Installation screen displays, indicating that no server components are assigned to this machine. Select the “Override” button. Click [Next] to continue. The Distributed Planning, Step 1 dialog appears:

8 Enter the Machine Name, IP Address and the License Key (if Applicable) 9 Click [Add]. The entry will appear in the Machine List. Click [Next].

NavisAccess DSL Installation and Administration Guide 2-19 Distributed Installation Modifying your distribution plan

The Distribution Plan, Step 2 dialog will appear:

Use this screen to add the NavisAccess DSL component to the machines defined in the previous screen. You can Click the: – “Component Name” field to display a pull-down menu listing all the available components. – “Machine Name” field to display the defined machines. 10 Components are assigned one at a time. Certain components can only be installed once. Others can be installed multiple times across multiple machines. The following table lists the components and their distribution possibilities.

Component Name No. of times component can be distributed

Database Server One

Scheduling Server One

Auto Grouping Engine One

Checkpoint Handler One

Call Logging Streamer One

Data Management Server One

DSL Service Management Unit Multiple

2-20 NavisAccess DSL Installation and Administration Guide Distributed Installation Modifying your distribution plan

Component Name No. of times component can be distributed

Call Logging Receiver Multiple

GUI Server Multiple

Reporting Server Multiple

See the section “NavisAccess DSL component distribution” on page 2-4 for details on how to distribute the components. 11 To assign a component, click the component field. A list of the available components displays. Select the component you need. 12 Click the Machine Name field. Highlight the machine on which you want to install the component and click Add. Note the following regarding component distribution: – Single-instance components are removed from the “Component Name” field as they are assigned to machines. – Multiple-instance components are incremented by one each time they are assigned to a machine. The “Component Name” display will indicate the number of times the component has been assigned. For example, if two GUI servers were assigned, it would appear like this: [1]GUI Server 13 Click Next when the component is added. 14 The Target Directory screen displays with the default directory /export/home/navis. You can install in the default directory or enter a new target directory path if you wish. Make sure that: – the directory has enough space. – there are no files in the target directory that you need (NavisAccess DSL overwrites them during the installation process). If there are, move them to another directory. – the directory name is in lowercase letters as specified by the program, and it is a full name path. 15 Enter the directory in which NavisAccess DSL is to be installed and click [Next]. (If no such directory exists, it prompts you whether such directory should be created. Click YES if you wish to do so.) 16 The “Are You Sure?” screen displays, warning you that all files in the Installation Directory will be deleted. The software installs to the exact directory path you specify. Be aware that any files in that ! directory will be deleted. You should always specify a new sub-directory to which NavisAccess DSL should be installed because all files in the final directory will be overwritten. 17 Click [Finish] to complete the installation.

The Copying files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory.

NavisAccess DSL Installation and Administration Guide 2-21 Distributed Installation Modifying your distribution plan

Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

Redistributing componenets

Redistributing components on the existing NavisAccess Server farm requires that you install NavisAccess onto a new Server. During installation, choose the components that you wish to redistribute - from an existing server to a newly installed server.

Note: If you have multiple NavisAccess DSL farms on the same LAN, please refer to Appendix D, “Multiple Server Farms on the Same LAN (Distributed Server).” 4 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. 5 The “Full Installation / Service Pack” screen displays. Please specify the installation type: – Full Installation - A fresh installation will take place. You will be prompted to enter a license key. Note: The database will be updated only if the existing or fresh installation is live. – Service Pack - The existing installation will be upgraded. The Database will be upgraded. A license key is not required. Note: The evaluation time period (if any) will not be extended. The Database must be running to install the Service Pack. 6 If performing a Full Installation, you will be prompted to locate a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess DSL on how to obtain a serial number file. The file is named liblock.so. 7 The Workstation Installation screen displays, indicating that no server components are assigned to this machine. Select the “Override” button. Click [Next] to continue.

2-22 NavisAccess DSL Installation and Administration Guide Distributed Installation Modifying your distribution plan

The Distributed Planning, Step 1 dialog appears:

8 Enter the Machine Name, IP Address and the License Key (if Applicable) 9 Click [Add]. The entry will appear in the Machine List. Click [Next]. The Distribution Plan, Step 2 dialog will appear:

NavisAccess DSL Installation and Administration Guide 2-23 Distributed Installation Modifying your distribution plan

– “Machine Name” field to display the defined machines. 10 Components are assigned one at a time. Certain components can only be installed once. Others can be installed multiple times across multiple machines. The following table lists the components and their distribution possibilities.

Component Name No. of times component can be distributed

Database Server One

Scheduling Server One

Auto Grouping Engine One

Checkpoint Handler One

Call Logging Streamer One

Data Management Server One

DSL Service Management Unit Multiple

Call Logging Receiver Multiple

GUI Server Multiple

Reporting Server Multiple

See the section “NavisAccess DSL component distribution” on page 2-4 for details on how to distribute the components. 11 To unassign a component, click the Machine Name from the list of machines/componenets. 12 Click [Remove]. The component will now be available. 13 To assign that component, click the component field. A list of the available components displays. Select the component you need. 14 Click the Machine Name field. Highlight the machine on which you want to install the component and click Add. Note the following regarding component distribution: – Single-instance components are removed from the “Component Name” field as they are assigned to machines. – Multiple-instance components are incremented by one each time they are assigned to a machine. The “Component Name” display will indicate the number of times the component has been assigned. For example, if two GUI servers were assigned, it would appear like this: [1]GUI Server 15 Click Next when the component is added. 16 The Target Directory screen displays with the default directory /export/home/navis. You can install in the default directory or enter a new target directory path if you wish.

2-24 NavisAccess DSL Installation and Administration Guide Distributed Installation Modifying your distribution plan

Make sure that: – the directory has enough space. – there are no files in the target directory that you need (NavisAccess DSL overwrites them during the installation process). If there are, move them to another directory. – the directory name is in lowercase letters as specified by the program, and it is a full name path. 17 Enter the directory in which NavisAccess DSL is to be installed and click [Next]. (If no such directory exists, it prompts you whether such directory should be created. Click YES if you wish to do so.) 18 The “Are You Sure?” screen displays, warning you that all files in the Installation Directory will be deleted. The software installs to the exact directory path you specify. Be aware that any files in that ! directory will be deleted. You should always specify a new sub-directory to which NavisAccess DSL should be installed because all files in the final directory will be overwritten. 19 Click [Finish] to complete the installation.

The Copying files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory.

If components have been removed from a machine, setup will remind you that you MUST reinstall NavisAccess on that machine.

Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

NavisAccess DSL Installation and Administration Guide 2-25 Distributed Installation Modifying your distribution plan

2-26 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation 3

IF INSTALLING A PRODUCTION VERSION (LIVE) FROM AN EXISTING EVALUATION VERSION (DEMO), A SERIAL NUMBER FILE IS NEEDED. Before installing NavisAccess DSL, you must acquire a serial number file and license key from Lucent Technologies for each server and workstation you are installing. The file is obtained through the Lucent internet site. See your NavisAccess DSL box insert for details. You will need the Authorization Code that is enclosed with your NavisAccess DSL software. There is a 24 hour turn-around time for licensed key requests.

Getting ready to install: Things to know

Please read the following prerequisites and preparatory steps before beginning the installation of NavisAccess DSL.

Before proceeding with this installation, please read the preliminary information found in “Read Me First” on page -xiii.

Important! The RPC Bind and Keyserv daemons must be running prior to installing NavisAccess DSL. The script that starts these daemons is /etc/rc2.d/S71rpc. • Installation can be run from an X terminal or a character terminal. • All NavisAccess DSL files are installed with owner and group of the user who installed it. The files are given 755 as mode. This permission setting allows a non-root user to run NavisAccess. • NavisAccess DSL must be installed by a super user. • Solaris Power Management must be turned off on the NavisAccess Primary Server. For further information, refer to the man power.conf. • In order to use the NavisAccess DSL TFTP server, you must comment out the tftp line in the /etc/inetd.conf file by entering a number sign (#) in front of the line. This line will look similar to the following: tftp dgram udp wait root /usr/lbin/tftpd tftpd/opt/ignite/var/opt/ignite

NavisAccess DSL Installation and Administration Guide 3-1 Upgrading your NavisAccess installation Getting ready to install: Things to know

• For proper display of NavisAccess DSL windows, you must ensure that the CDE environment setting for “Allow Primary Windows On Top” is checked.

3-2 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Getting ready to install: Things to know

What versions can be upgraded NavisAccess versions 5.1.x of can be updated to version 5.1.4

What is upgraded During the upgrade process the database will be upgraded. This will not effect any data in the current database. Therefore, APM Data, Call-logging data, Devices, Services, Groups made, etc. will all be retained.

NavisAccess DSL Installation and Administration Guide 3-3 Upgrading your NavisAccess installation Getting ready to install: Things to know

NavisAccess Installation table

The following table lists the NavisAccess installation scenarios. It defines: • Which NavisAccess versions can be upgraded to 5.1.4. • Whether a license file is required. • If data in the database will be retained.

Old New License File License Retains Installation Installation Expiration previous version data? NavisAccess NavisAccess No License file needed 90 Days from Yes v 5.1.x Demo v 5.1.4 Demo date of first installation.

NavisAccess NavisAccess License file needed. N/A User can choose v 5.1.x Demo v 5.1.4 Live during setup. For further information on obtaining a License file, refer to the document shipped with NavisAccess titled “Serial Number Information.” NavisAccess NavisAccess Use existing file N/A Yes v 5.1.x Live v 5.1.4 Live No previous NavisAccess License file needed. N/A N/A installation v 5.1.4 Live For further information on obtaining a License file, refer to the document shipped with NavisAccess titled “Serial Number Information.” No previous NavisAccess No License file needed 90 Days from N/A installation v 5.1.4 Demo date of first installation.

Installation types

Once the upgrade type has been determined, choose which installation type you wish to perform:

A standalone installation consists of NavisAccess DSL components being installed on one machine.

This chapter takes you step-by-step through each upgrade scenario within the two installation types.

3-4 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Standalone Installation

Standalone Installation

If performing a distributed installation, refer to “Distributed Installation” on page 3-12 in this chapter.

NavisAccess installation summary

Note: For a detailed description of hardware requirements and component distribution, please refer to “Systems Requirements” in the Read me First chapter in the NavisAccess Installation and Administration Guide.

Use this summary as a checklist to ensure you follow all the steps for proper installation. Failure to follow all the steps outlined below may lead to problems starting or using NavisAccess. Detailed installation instructions follow this list.

Prerequisites to installation

q Solaris Operating System must be installed.

q Required operating system patches must be applied.

q The required patches are located from where you downloaded NavisAccess.

q Common Desktop Environment (CDE) must be installed.

q NavisAccess must be installed by a Superuser (root).

q NavisAccess should run under the ksh.

q If performing a Demo to Live upgrade, get your License File and License Keys. Consult the “Serial Number Information” document included with NavisAccess on how to obtain a License file and License Keys.

q You should access the website a full day before you intend to install NavisAccess. There is a 24-hour turn-around between submitting your request, delivery of the key(s) and the License file.

Installation Steps

q Step 1: Installation

q Step 2: Reboot system

Additional steps

q Step 3: Check status of services

q Step 4: Compile MIBs

NavisAccess DSL Installation and Administration Guide 3-5 Upgrading your NavisAccess installation Standalone Installation

Upgrading from a Live to a Live installation

q Step 1: Installation 1 Change to the directory where the installation files are placed, and run the installation file by entering: ./setup -n Note: The name of the database server must match that which NavisAccess is currently using. – To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays, click [Next] to continue if no applications are running. 3 The Target Directory screen displays the NavisAccess home directory. The directory should not be modified. Make sure that the directory has enough space. 4 Click [Next] to continue. The “Are You Sure” screen displays. 5 Click [Finish] to complete the installation. The Copying Files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete.

q Step 2: Reboot system

Once the above steps are completed, the Setup Status screen displays. This screen informs you that the installation of the NavisAccess components are complete. • Click [Yes] in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen. Once the system has rebooted, refer to “Additional steps” on page 3-9.

3-6 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Standalone Installation

Upgrading from a Demo to a Live installation

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

Note: The [Next] button will not activate until you enter all information on the User Information screen. 6 The Installation Type screen displays. Select Standalone and click [Next]. You are prompted to enter a License Key. The license key must be obtained from Lucent Technologies prior to installing the software. Consult the “Serial Number Information” document included with NavisAccess on how to obtain a License Key. 7 Enter the license key and click [OK]. The license key is an 18-character letter/number combination. It is case sensitive.

NavisAccess DSL Installation and Administration Guide 3-7 Upgrading your NavisAccess installation Standalone Installation

8 The Target Directory screen displays with the NavisAccess home directory. This directory should not be modified. Make sure that the directory has enough space. 9 Click [Next] to continue. The “Are You Sure” screen displays. 10 Click [Finish] to complete the installation. The Copying Files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete.

q Step 2: Reboot system

Upgrading from a Demo to a Demo installation

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays, click [Next] to continue if no applications are running. 3 The Target Directory screen displays the NavisAccess home directory. The directory should not be modified. Make sure that the directory has enough space. 4 Click [Next] to continue. The “Are You Sure” screen displays. 5 Click [Finish] to complete the installation. The Copying Files screen displays as it automatically starts to copy the files.

3-8 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Standalone Installation

The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete.

q Step 2: Reboot system

Additional steps

q Step 3: Check status of services

All NavisAccess services will start upon reboot. The nautil utility is provided to check the status of services and to start and stop them when needed. You should check the status of your services before proceeding.

Syntax for using nautil follows:

nautil start Starts NavisAccess services

Note: Only the Superuser (root) has permission to start any services that use port 1024 or less. status Shows status of services shutdown Shuts down all services. stop Shuts down services one at a time, giving you the option to stop individual services. This option is used when select services must be stopped.

Note: Only the Superuser (root) has permission to stop any services that use port 1024 or less. dbmaint Shuts down all services except the following: • X Virtual Frame Buffer Service • Database server •WindU Registry • WindU Service • osagent • edispatcher

1 To check if NavisAccess services are running, at the command line enter: nautil status

NavisAccess DSL Installation and Administration Guide 3-9 Upgrading your NavisAccess installation Standalone Installation

Recheck the status when the startup procedure has completed.

q Step 4: Compile MIBs

Before using NavisAccess, the necessary MIBs must be compiled. You must complete this step, even if you have compiled MIBs using a previous version of NavisAccess. 1 To compile the MIBs, after making sure the NavisAccess services are running, enter the following command to open the MIB Compiler: mibc 2 Click the [Compile] button. The compilation process will begin and will be displayed in the MIB compiler window. Compilation of a MIB will generate messages reading: “Processing File: .” If the entire process is successful, a screen similar to the one below will be displayed.

You are now finished with the installation process, and may start NavisAccess.

3-10 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Standalone Installation

Starting NavisAccess

To start NavisAccess, the environment must be set and the server services must be started. The user application (GUI) can then be started.

To start NavisAccess: 1 Make sure the NavisAccess services are running. At the command line enter: nautil status to check status of the services. (For full details on the nautil utility, see “Step 3: Check status of services” on page 3-9.) 2 After verifying that all services are running, enter the following: srm & The srm executable starts the NavisAccess graphical user interface (GUI).

NavisAccess DSL Installation and Administration Guide 3-11 Upgrading your NavisAccess installation Distributed Installation

Distributed Installation

If performing a standalone installation, refer to “Standalone Installation” on page 3-5 in this chapter.

NavisAccess installation step summary

Use this summary as a checklist to ensure you follow all the steps for proper installation. Failure to follow all the steps outlined below may lead to problems starting or using NavisAccess. Detailed installation instructions follow this list.

Note: For further information on distribution planning and component distribution, refer to Chapter 2, “Distributed Installation,” in the NavisAccess Installation and Administration Guide.

Prerequisites to installation

The following prerequisites apply to the primary server, secondary server(s) and the workstation. Prerequisites that apply to a specific device are noted.

q Solaris Operating System must be installed.

q Required operating system patches must be applied.

q The required patches are located from where you downloaded NavisAccess.

q Common Desktop Environment (CDE) must be installed.

q NavisAccess must be installed by a Superuser (root).

q NavisAccess should run under the ksh.

NavisAccess will be installed on the following machines:

q Primary Server: The first machine on which NavisAccess DSL is installed in a Distributed Server installation. When installing the Primary Server you will designate the other machines in the NavisAccess farm. You must have available the name and IP address of every Secondary Server designated for Distributed Server configuration.

Note: The Primary Server must be running throughout the Distributed Installation process

q Secondary Server(s): Once the Primary Server installation is complete, the second machine(s) to install NavisAccess on is the Secondary Server(s).

q Workstation: After NavisAccess is installed on both the Primary and Secondary Server(s), it’s time to install NavisAccess on the Workstation(s).

Note: Before installing on any workstation ensure that all services are running.

3-12 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

Note: You should access the website a full day before you intend to install NavisAccess. There is a 24-hour turn-around between submitting your request, delivery of the key(s) and the License file.

Installation Steps

Primary Server installation and creation of Distribution Plan

q Step 1: Installation of Primary server

q Step 2: Reboot system

Secondary server installation

q Step 3: Installation of Secondary server(s)

q Step 4: Reboot Secondary server(s)

Workstation installation

q Step 5: Installation of Workstation(s)

q Step 6: Reboot Workstation

Additional Steps

q Step 7: Check status of services

q Step 8: Compile MIBs on all Workstations

Upgrading from a Live to a Live installation

Primary Server installation

q Step 1: Installation of Primary server 1 Change to the directory where the installation files are placed, and run the installation file by entering: ./setup -n Note: The name of the database server must match that which NavisAccess is currently using. – To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

NavisAccess DSL Installation and Administration Guide 3-13 Upgrading your NavisAccess installation Distributed Installation

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays, click [Next] to continue if no applications are running. The Target Directory screen displays the NavisAccess home directory. This directory should not be changed. Make sure that the directory has enough space. 3 Click [Next] to continue. The “Are You Sure?” screen displays. 4 Click [Finish] to complete the installation. The Copying files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete. A message displays that says, “The following servers must be re-installed...” and then lists the servers.

q Step 2: Reboot system

Note: Your installed primary server must be up before proceeding with the secondary server(s) installation.

Secondary Server Installation

q Step 3: Installation of Secondary server(s)

Note: The following steps must be repeated on all secondary server(s).

At a terminal window command prompt: 5 Change to the directory where the installation files are placed, and run the installation file by entering: ./setup -n This command should be identical to what was entered at the Primary server.

Note: The name of the database server must match that which NavisAccess is currently using. – To obtain the database server name, issue the following command:

3-14 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

grep “\-n” /etc/rc2.d/S97ascendDBeng

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 6 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. The Target Directory screen displays the NavisAccess home directory. The directory should not be modified. Make sure that the chosen directory has enough space. 7 Click [Next] to continue. The “Are You Sure” screen displays. 8 Click Finish to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete. A message displays saying, “The following servers must be re-installed . . .” and then lists the servers.

q Step 4: Reboot system

Note: Your installed secondary server(s) must be up before proceeding with the workstation(s) installation.

Workstation installation

q Step 5: Installation of Workstation(s)

Note: You may install workstations on a different subnet from where the servers are installed. For further information, refer to Appendix E, “Workstation Installation on a Separate Subnet”, of the NavisAccess Installation and Administration Guide.

At a terminal window command prompt:

NavisAccess DSL Installation and Administration Guide 3-15 Upgrading your NavisAccess installation Distributed Installation

1 Change to the directory where the installation files are placed, and run the installation file by entering: ./setup -n This command should be identical to what was entered at the Primary server.

Note: The name of the database server must match that which NavisAccess is currently using. – To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. The Target Directory screen displays the NavisAccess home directory. This directory should not be changed. Make sure that the directory has enough space. 3 Click [Next] to continue. The “Are You Sure” screen displays. 4 Click [Finish] to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete.

q Step 6: Reboot system

Once the above steps are completed, the Setup Status screen displays. This screen informs you that the installation of the NavisAccess components are complete. • Click Yes in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen. Once the system has rebooted, refer to “Additional Steps” on page 3-24. When the Additional Steps are completed, continue with the installation process.

Upgrading from a Demo to a Live installation

Primary Server Installation

q Step 1: Installation of Primary server 1 Change to the directory where the installation files are placed, and run the installation file by entering:

3-16 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

./setup -n Note: The name of the database server must match that which NavisAccess is currently using. – To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays, click [Next] to continue if no applications are running. You are prompted to locate a License file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the “Serial Number Information” document included with NavisAccess on how to obtain a License file. 3 Select the License file and click [OK]. 4 The following message displays: “Do you want to upgrade your existing database?” Click [Yes] to upgrade your database. If you click [No], you lose all database information. The NavisAccess Assigned Components screen displays. Two things happen at this point: – The distribution plan, which is located on the primary server, is read by setup to determine which components belong on each server. – Once setup determines the components, the Component Name window of this screen displays the components that you assigned to the Primary server. 5 Verify that Modify is selected, and click [Next]. The Installation Type screen displays. 6 Select Distributed and click [Next]. The “Distribution Planning, Step 1” screen displays. This screen will be used to enter the names and IP addresses of all Primary and secondary servers. Names and IP Addresses of NavisAccess workstations should not be entered. 7 Enter the Primary Server license key in the “License Key” field. 8 Enter the Secondary Server license key in the “License Key” field.

Note: The Primary Server and Secondary Server license keys must be obtained from Lucent Technologies. 9 Move the Relative Power Rating slide bar to reflect the relative performance status of the machine. This is only used as a guideline, it does not affect the installation process.

Modifying a machine entry All the machine entries are displayed in the table (at the bottom of the screen). You cannot directly edit the information in the table. To edit:

NavisAccess DSL Installation and Administration Guide 3-17 Upgrading your NavisAccess installation Distributed Installation

Modifying a machine entry • Select the row you want to modify in the table section of the screen. The machine information is displayed on the upper section of the screen, in the Machine Name and IP Address fields. • Enter the License Key, and press Modify.

Deleting a machine entry Deleting a machine is not supported.

10 Click [Next] when you have entered the licenses for all of the machines. The “Distribution Planning, Step 2” screen displays with the database server assigned. 11 Click [Next] if you are not modifying your distribution plan. If you wish to modify your distribution plan, refer to the section titled “Distributed Installation” in Chapter 2 of the NavisAccess Installation and Administration Guide. 12 The Target Directory screen displays with the NavisAccess home directory. This directory should not be modified. Make sure that the directory has enough space. 13 Click [Next] to continue. The “Are You Sure?” screen displays. 14 Click [Finish] to complete the installation. The Copying files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete. A message displays that says, “The following servers must be re-installed...” and then lists the servers.

q Step 2: Reboot system

Note: Your installed primary server must be up before proceeding with the secondary server(s) installation.

Secondary Server Installation

q Step 3: Installation of Secondary server(s)

Note: The following steps must be repeated on all secondary server(s).

At a terminal window command prompt: 1 Change to the directory where the installation files are placed, and run the installation file by entering: ./setup -n

3-18 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

This command should be identical to what was entered at the Primary server.

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. You are prompted to locate a License file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the “Serial Number Information” document included with NavisAccess on how to obtain a License file. 3 Select the License file and click [OK]. The NavisAccess Assigned Components screen displays. Two things happen at this point: – The distribution plan, which is located on the primary server, is read by setup to determine which components belong on each server. – Once setup determines the components, the Component Name window of this screen displays the components that you assigned to the Secondary server. 4 Verify that Proceed is checked, and click [Next]. The Target Directory screen displays with the NavisAccess home directory. This directory should not be modified. Make sure that the chosen directory has enough space. 5 Click [Next] to continue. The “Are You Sure” screen displays. 6 Click Finish to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time. You must allow enough time for the process to complete. A message displays saying, “The following servers must be re-installed...” and then lists the servers.

q Step 4: Reboot system

NavisAccess DSL Installation and Administration Guide 3-19 Upgrading your NavisAccess installation Distributed Installation

Once the system has rebooted, refer to “Additional Steps” on page 3-24. When the Additional Steps are completed, continue with the installation process.

Note: Your installed secondary server(s) must be up before proceeding with the workstation(s) installation.

Workstation Installation

q Step 5: Installation of Workstation(s)

At a terminal window command prompt: 1 Change to the directory where the installation files are placed, and run the installation file by entering: ./setup -n This command should be identical to what was entered at the Primary server.

Note: The name of the database server must match that which NavisAccess is currently using.

– To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

3-20 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

5 Enter the License key and click [OK]. The license key is an 18-character letter/number combination. It is case sensitive.

6 The Target Directory screen displays with the NavisAccess home directory. This directory should not be modified. Make sure that the directory has enough space. 7 Click [Next] to continue. The “Are You Sure” screen displays. 8 Click [Finish] to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

q Step 6: Reboot system

Upgrading from a Demo to a Demo installation

Primary server installation

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

NavisAccess DSL Installation and Administration Guide 3-21 Upgrading your NavisAccess installation Distributed Installation

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays, click [Next] to continue if no applications are running. The Target Directory screen displays the NavisAccess home directory. This directory should not be changed. Make sure that the directory has enough space. 3 Click [Next] to continue. The “Are You Sure?” screen displays. 4 Click [Finish] to complete the installation. The Copying files screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete. A message displays that says, “The following servers must be re-installed...” and then lists the servers.

q Step 2: Reboot system

Once the completion of the above steps, the Setup Status screen displays. This screen informs you that the installation of the NavisAccess components are complete. • Click [Yes] in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen. Once the system has rebooted, refer to “Additional Steps” on page 3-24. When the Additional Steps are completed, continue with the installation process.

Note: Your installed primary server must be up before proceeding with the secondary server(s) installation.

Secondary Server installation

q Step 3: Installation of Secondary server(s)

Note: The following steps must be repeated on all secondary server(s).

Note: The name of the database server must match that which NavisAccess is currently using.

– To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

3-22 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. 3 The Target Directory screen displays the NavisAccess home directory. This directory should not be changed. Make sure that the chosen directory has enough space. 4 Click [Next] to continue. The “Are You Sure” screen displays. 5 Click Finish to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete. A message displays saying, “The following servers must be re-installed...” and then lists the servers.

q Step 4: Reboot system

Once Steps 1 through 3 are completed, the Setup Status screen displays. This screen informs you that the installation of the NavisAccess components are complete. • Click Yes in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen. Once the system has rebooted, refer to “Additional Steps” on page 3-24. When the Additional Steps are completed, continue with the installation process.

Note: Your installed secondary server(s) must be up before proceeding with the workstation(s) installation.

Workstation installation

q Step 5: Installation of Workstation(s) Note: You may install workstations on a different subnet from where the servers are installed. For further information, refer to Appendix E, “Workstation Installation on a Separate Subnet”, of the NavisAccess Installation and Administration Guide.

Note: The name of the database server must match that which NavisAccess is currently using.

NavisAccess DSL Installation and Administration Guide 3-23 Upgrading your NavisAccess installation Distributed Installation

– To obtain the database server name, issue the following command: grep “\-n” /etc/rc2.d/S97ascendDBeng

Text similar to the following will display:

/usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/Ascend28213_output.log -os 102400 -n Ascend28213 $NAVIS_DIR/database/ascend.db >>/dev/null

The string following the “-n” flag is the name of the database server. In the above example, Ascend28213 is the name of the database server. 2 The “NavisAccess - Welcome” screen displays. Click [Next] to continue. 3 The Target Directory screen displays the NavisAccess home directory. This directory should not be changed. Make sure that the directory has enough space. 4 Click [Next] to continue. The “Are You Sure” screen displays. 5 Click [Finish] to complete the installation. The Copying Files-Please Wait screen displays as it automatically starts to copy the files. The sliding bar on this screen shows you the progress of the files being copied to the directory. Be aware that the file copying process can take a considerable amount of time, and you must allow enough time for the process to complete.

q Step 6: Reboot system

Once the above steps are completed, the Setup Status screen displays.This screen informs you that the installation of the NavisAccess components are complete. • Click [Yes] in response to the prompt, “Do you want to reboot the system?” in the Setup Status screen. Once the system has rebooted, refer to “Additional Steps” on page 3-24. When the Additional Steps are completed, continue with the installation process.

Additional Steps

q Step 7: Check status of services

3-24 NavisAccess DSL Installation and Administration Guide Upgrading your NavisAccess installation Distributed Installation

Syntax for using nautil follows:

nautil start Starts NavisAccess services Note: Only the Superuser (root) has permission to start any services that use port 1024 or less. status Shows status of services shutdown Shuts down all services. stop Shuts down services one at a time, giving you the option to stop individual services. This option is used when select services must be stopped.

1 To check if NavisAccess services are running, at the command line enter: nautil status

q Step 8: Compile MIBs on Workstations

NavisAccess DSL Installation and Administration Guide 3-25 Upgrading your NavisAccess installation Distributed Installation

Before using NavisAccess, the necessary MIBs must be compiled on each workstation in the system. You must complete this step, even if you have compiled MIBs using a previous version of NavisAccess. 1 To compile MIBs, after making sure the NavisAccess services are running, enter the following command to open the MIB Compiler: mibc 2 Click the [Compile] button. The compilation process will begin and will be displayed in the MIB compiler window. Compilation of a MIB will generate messages reading: “Processing File: .” If the entire process is successful, a screen similar to the one below will be displayed.

You are now finished with the installation process, and may start NavisAccess.

Starting NavisAccess

To start NavisAccess, the environment must be set and the server services must be started. The user application (client GUI) can then be started on any workstation logging in to the server.

To start NavisAccess: 1 Make sure the NavisAccess services are running. To check status of the services, at the command line enter: nautil status (For full details on the nautil utility, see “Step 7: Check status of services” on page 3-24.) 2 After verifying that all services are running, enter the following: srm & Note: The srm executable starts the NavisAccess graphical user interface (GUI).

3-26 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with 4 NavisAccess DSL

Overview ...... 4-2

Device TAOS Software Requirements...... 4-2 Preparing Lucent Devices ...... 4-3

Stinger/Stinger LS Preparation ...... 4-3

DSL TNT Preparation ...... 4-19

DSLMAX and DSLTerminator Preparation...... 4-25

NavisAccess DSL Installation and Administration Guide 4-1 Preparing Lucent Devices for Use with NavisAccess DSL Overview

Overview

Before NavisAccess DSL can be used with Lucent Stinger, DSLTerminator, DSLMAX, and DSLTNT devices, several preparatory steps must be made. These are outlined below. Please make note of the minimum software requirements.

Device TAOS Software Requirements

NavisAccess DSL requires certain levels of Lucent TAOS device software for full functionality. In addition, the NavisAccess DSL Software Option is required for each Lucent Stinger, DSLTerminator, DSLMAX, and DSLTNT device that NavisAccess DSL will manage.

The following table lists required device software levels:

Device TAOS Software Level Call-Logging support Stinger/Stinger LS 9.0 Yes DSLTerminator 8.0.3 No DSLMAX family 8.0.3 No DSLTNT 8.0.3 No

About the Network Management Option

Each Lucent Stinger, DSLTerminator, DSLMAX, and DSLTNT device requires the Network Management Option (Network Management Enable) in order to be managed using NavisAccess DSL.

How do I know if I have the Network Management Enable software option on my Stinger and TNT device?

Telnet into the device and using the CLI interface, type the following: Admin > get base

If the Network Management Enable option is installed, the output will read: Network-management-enable = yes

If it does not say this, the Network Management Enable software option needs to be obtained.

How do I know if I have the Network Management Enable software option on my MAX and Terminator device? 1 Telnet into the device and [Tab] to the System Options window. 2 Click the up/down arrow key until you reach the Net Mgmt option. If the Network Management Enable option is installed, the line will read: Net Mgmt Installed

The Software Option is sold on a per-device basis, based on the specific device. Contact Lucent Technologies for details on purchasing the Software Option.

4-2 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Preparing Lucent Devices

Preparing Lucent Devices

Information on preparing Lucent devices can be found on the following pages:

Device Page found

Stinger/Stinger LS page 4-3

DSLTNT page 4-19

DSLMAX page 4-25

DSLTerminator page 4-25

Stinger/Stinger LS Preparation

Note: The Soft IP address must be set in the Stinger so that all call-logging packets have one IP address. Failure to accomplish this may cause problems during Device Discovery.

Use the following as a checklist for enabling communication between the Stinger device and NavisAccess:

Check Preparation Step Page in Chapter

If using SNMP v1, configure the following:

Enabling SNMP v1 and configuring SNMP parameters on page 4-4 the Stinger

Configuring SNMP v1 trap destinations for the Stinger page 4-5

If using SNMP v3, configure the following:

Enabling SNMP v3 and configuring SNMP parameters on page 4-8 the Stinger

Creating a SNMP v3 user profile for the Stinger page 4-9

Creating a SNMP v3 trap notification profile for the page 4-10 Stinger

Creating a SNMP v3 target profile for the Stinger page 4-11

Configuring SNMP v3 trap destinations for the Stinger page 4-12

If using either SNMP v1 or SNMP v3, configure the following:

Configuring a Soft IP address on the Stinger page 4-15

NavisAccess DSL Installation and Administration Guide 4-3 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

Check Preparation Step Page in Chapter

Configuring a Global IP address on the Stinger page 4-16

Enable call logging on the Stinger page 4-16

Enable call-logging for evaluation purposes page 4-19

Enabling SNMP v1and configuring SNMP parameters on the Stinger

SNMP validates each message with a password-like mechanism called a Community String. SNMPv1 uses a Read and Read/Write community strings.

NavisAccess DSL supports both SNMPv1 and SNMPv3. If you are using SNMPv1, you must follow the steps described below to set SNMPv1 for the Stinger.

To enable SNMPv1 and set security on the device: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: read snmp This will return a “SNMP read” message, and a new command prompt. 4 At the command prompt, enter: list This will return the following parameter list: enabled = no read-community = public read-write-enabled = no read-write-community = write enforce-address-security = no contact = "NMD, Bohemia" location = "NMD, Bohemia" queue-depth = 0 csm-modem-diag = no snmp-message-type = v1-and-v3 security-level = none (This option only applies when enabling SNMP v3.) 5 Set the enabled parameter to Yes as follows: set enabled = yes If the enabled parameter in the SNMP profile is set to No (the default), the device cannot be accessed by NavisAccess DSL. 6 If necessary, set new read-community and read-write-community strings (up to 32 characters) as follows: set read-community = secret_string set read-write-community = unique_string

4-4 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

The read-community string permits read access to the device and the read-write string permits read/write access.

Note: The read and write Community Names used by NavisAccess DSL must match what is specified on the device. Otherwise, communication cannot be established with the device. 7 Set the enforce-address-security parameter as follows: set enforce-address-security = yes/no Note: Setting Enforce Address Security to Yes is not advisable in a distributed installation because each NavisAccess DSL installation needs SNMP connectivity to the Stinger device. If the enforce-address-security parameter is set to No (its default value), any SNMP manager that presents the right community name will be allowed access (if value is left at no, please continue to Step 10). If it is set to Yes, the device checks the source IP address of the SNMP manager and allows access only to those IP addresses listed in the read-access-host and write-access-host arrays. You can list up to five IP hosts that can access the MIB read-write access, and up to five hosts that can read traps and other information. If SNMP security access is used, all NavisAccess DSL machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess DSL via Telnet or Xterm to not have to have their IP addresses included.) 8 It is recommended that you set the contact and location parameters with the name and location of the person to contact if there is a problem with the unit (up to 84 characters). For example: set contact = Mary Smith set location = Green Bay office, 555-1212 9 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by an “SNMP written” message.

Configuring SNMPv1 trap destinations for the Stinger

The Lucent Stinger sends messages in the form of SNMP Traps. These Traps are sent to a management station (such as NavisAccess DSL) for logging and interpretation. If there is an existing Management Station in your network, the devices may be set up to pass all Traps to it. Contact the network administrator for this information.

To configure the trap destination: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: new trap This will return a TRAP/" " read message and a new command prompt. 4 At the command prompt, enter: list

NavisAccess DSL Installation and Administration Guide 4-5 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

This will return a parameter list that begins similar to the following. (Parameters may vary based on the level of software being used.) host-name* = "" active-enabled = yes community-name = "" host-address = 0.0.0.0 host-port = 162 inform-time-out = 1500 inform-retry-count = 4 notify-tag-list = default target-params-name = default alarm-enabled = yes security-enabled = no port-enabled = no slot-enabled = no coldstart-enabled = yes warmstart-enabled = yes linkdown-enabled = yes linkup-enabled = yes ascend-enabled = yes console-enabled = yes use-exceeded-enabled = yes password-enabled = yes fr-linkup-enabled = yes fr-linkdown-enabled = yes event-overwrite-enabled = yes radius-change-enabled = yes lan-modem-enabled = yes slot-profile-change-enabled = yes power-supply-enabled = yes authentication-enabled = yes config-change-enabled = yes sys-clock-drift-enabled = yes suspect-access-resource-enabled = yes watchdog-warning-enabled = yes controller-switchover-enabled = no call-log-serv-change-enabled = yes wan-line-state-change-enabled = yes call-log-dropped-pkt-enabled = yes lim-sparing-enabled = no interface-sparing-enabled = no secondary-controller-state-change-enabled = no pctfi-trunk-status-change-enabled = yes no-resource-available-enabled = yes dsl-thresh-trap-enabled = no

4-6 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

atm-pvc-failure-trap-enabled = no atm-ima-alarm-trap-enabled = no ascend-link-down-trap-enabled = no ascend-link-up-trap-enabled = no snmp-illegal-access-attempt = no Note: Consult your Stinger documentation for details on these parameters. 5 Enter a host-name (up to 16 characters), as follows: set host-name = my_host_name The host-name specifies the hostname of the NavisAccess DSL station. This is the host to which the device will send SNMP traps. If the host-address field contains an IP address, the specified name is not used to actually locate the host. 6 Enter a community-name (up to 31 characters), as follows: set community-name = my_community-name This specifies the SNMP community name associated with the SNMP PDU (Protocol Data Units). The string you specify becomes a password that the device sends to NavisAccess DSL when an SNMP trap event occurs. The password authenticates the sender identified by the host address. 7 Enter an IP address for the host-address. For example: set host-address = 10.2.3.4 The host-address is the same address as that of the NavisAccess DSL station. In a distributed NavisAccess DSL installation, traps must be sent to the IP address of the machine on which the Scheduling Server has been installed. 8 Enter the default type of trap notification you want reported to NavisAccess DSL. For example: set notify-tag-list = default 9 Enter the default target parameter for the traps to be sent. For example: set target-params-name = default 10 Specify that the Stinger should send its port status to the host as follows: set port-enabled = yes If enabled, the Boxmap will show updated port status in real-time. 11 Specify that the device can be automatically re-discovered when a slot’s status changes as follows: set slot-enabled = yes 12 Specify that when the controller switches-over that a trap will be sent to the identified host. For example: set controller-switchover-enabled = yes 13 Specify that the line interface module (LIM) sparing trap should to be sent to the identified host. For example: set lim-sparing-enabled = yes 14 Specify that the interface (port) redundancy trap should to be sent to the identified host. For example: set interface-sparing-enabled = yes

NavisAccess DSL Installation and Administration Guide 4-7 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

15 Specify that when the secondary controller changes states that a trap is sent to the identified host. For example: set secondary-controller-state-change-enabled = yes Consult the device documentation for further information on defining the parameters. 16 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a “TRAP/host-name written” message.

Enabling SNMP v3 and configuring SNMP parameters on the Stinger

SNMP validates each message with a password-like mechanism called a Community String. SNMPv3 uses a user name/password combination.

If you are using SNMPv3, you must follow the steps described below to set SNMPv3 for the Stinger.

To enable SNMPv3 and set security on the device: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: read snmp This will return a “SNMP read” message, and a new command prompt. 4 At the command prompt, enter: list This will return the following parameter list: enabled = no read-write-enabled = no enforce-address-security = no contact = "NMD, Bohemia" location = "NMD, Bohemia" snmp-message-type = v1-and-v3 security-level = none 5 Set the enabled parameter to Yes as follows: set enabled = yes If the enabled parameter in the SNMP profile is set to No (the default), the device cannot be accessed by NavisAccess DSL. 6 It is recommended that you set the contact and location parameters with the name and location of the person to contact if there is a problem with the unit (up to 84 characters). For example: set contact = Mary Smith set location = Green Bay office, 555-1212 7 Set the security-level to auth-nopriv. For Example:

4-8 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

set security-level = auth-nopriv Note: The security-level must be set to auth-nopriv. If this is not done, NavisAccess DSL will have difficulty in discovering the device. 8 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by an “SNMP written” message.

Creating a SNMPv3 user profile for the Stinger

NavisAccess DSL provides support for SNMP v3 user name/password authentication on the Stinger Device. The SNMP v3 user name and password must be set within NavisAccess DSL, and also configured on the device.

NOTE: SNMPv3 functionality is only available if the NavisAccess DSL Software Option is enabled on the device.

To configure SNMP v3 on the Stinger: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: read snmpv3-usm-user This will return a new command prompt. 4 If an SNMPv3 profile has never been created before, you may need to enter: new snmpv3-usm-user 5 At the command prompt, enter: list This will return a parameter list similar to the following: name = password = active-enabled = no read-write-access = no auth-protocol = md5-auth priv-protocol = no-priv auth-key = priv-key = 6 Create a name for the profile. For example: set name = navis_snmpv3 This user name must be matched within NavisAccess DSL. Do not set the password. 7 Enable the profile by entering: set active-enabled = yes 8 The read-write-access parameter specifies whether or not the user name has write- access to the device. Set to Yes to enable write-access, or No to disable. For example:

NavisAccess DSL Installation and Administration Guide 4-9 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

set read-write-access = yes 9 Set the auth-protocol parameter as follows: set auth-protocol=md5-auth MD5-Auth is the only protocol supported by NavisAccess DSL. The priv-protocol parameter is not supported by NavisAccess DSL. 10 Specify the authentication key that appears in external authentication configurations. For security reasons, the string is hidden when “auth-key” is displayed. Type the following to set the auth-key: snmpauthpass The password must be matched with NavisAccess DSL. The priv key is not supported. 11 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a “SNMPV3-USM-USER/profile_name written” message. You can type “list” again to view the newly set parameters, for example: name = navis_snmpv3 password = active-enabled = yes read-write-access = yes auth-protocol = md5-auth priv-protocol = no-priv auth-key = priv key =

Creating a SNMPv3 trap notifications profile for the Stinger

When configuring SNMP trap destinations for the Stinger, the SNMP v3 trap notification profile needs to be created before hand.

The trap notification profile will iterate the system to find trap profiles with matching tags and the parameters in the trap profiles will be used to send traps to the network.

To Create a trap notification profile: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: new SNMPV3-NOTIFICATION 4 Type list, and the following will appear: [in SNMPV3-NOTIFICATION/] name* = active-enabled = no tag = type = trap

4-10 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

5 Set active-enabled to yes if this profile is to be used when generating SNMP messages using this entry. For example: active-enabled = yes 6 Set tag to point to the trap profile (refer to page 4-12) by entering the trap profile name. For example, if the trap profile name is v3trapprofile, then: tag = v3trapprofile 7 Set type to trap or inform. Trap is an unconfirmed notification, and inform is a confirmed notification. For example: type = trap 8 Finish the configuration by writing the new parameters to the device, as follows: write

Creating a SNMPv3 target profile for the Stinger When configuring SNMP trap destinations for the Stinger, the SNMP v3 target profile needs to be created before hand. The SNMP v3 target profile defines where traps will be sent. Note: Before creating a SNMP v3 target profile, a SNMP v3 usm user must be created, which will be used in the security-model parameter of the target profile. This defines the security name which identifies on whose behalf SNMP messages will be generated. Refer to Creating a SNMP v3 user profile for the Stinger for further information. To create a target profile: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: new snmpv3-target-param/ 4 This will create a new profile with a default list of settings that can be displayed by typing: list The following will be displayed: [in snmpv3-target-param/] name* = active-enabled = yes msg-proc-model = v1 security-model = v1 security-name = security-level = none 5 Set active-enabled to yes if this profile is to be used for notification generation. active-enabled = yes 6 Change the msg-proc-model to equal to SNMP version 3, by typing: msg-proc-model = v3 7 Change security-model to equal SNMP version 3 User based security model, by typing:

NavisAccess DSL Installation and Administration Guide 4-11 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

security-model = v3-usm 8 Enter a security-name parameter. This is the name of the snmpv3-usm-user you defined in “Creating a SNMP v3 user profile for the Stinger”. security-name = 9 Change the security-level parameter to auth-nopriv. This defines the level of security to be used when generating messages to this entry: security-level = auth-nopriv 10 Finish the configuration by writing the new parameters to the device, as follows: write 11 Return to the trap profile, and enter the target parameter for the traps to be sent: target-params-name =

Configuring SNMP v3 trap destinations for the Stinger

The Lucent Stinger sends messages in the form of SNMP Traps. These traps are sent to a management station (such as NavisAccess DSL) for logging and interpretation.

NavisAccess DSL uses Device-oriented SNMP traps in order to keep the NavisAccess DSL database updated with any device changes (slot change, and so on). The NavisAccess DSL real-time interface status updates in Boxmap are also dependent on SNMP traps. It is highly recommended that devices managed by NavisAccess DSL are configured to point SNMP traps at the NavisAccess DSL installation. Device-specific configuration details are below.

If there is an existing Management Station in your network, the devices may be set up to pass all Traps to it. Contact the network administrator for this information.

To configure the device destination: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 At the command prompt, enter: new trap This will return a TRAP/" " read message and a new command prompt. 4 At the command prompt, enter: list This will return a parameter list that begins similar to the following. (Parameters may vary based on the level of software being used.) host-name* = "" active-enabled = yes community-name = "" host-address = 0.0.0.0 host-port = 162 inform-time-out = 1500 inform-retry-count = 4

4-12 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

notify-tag-list = default target-params-name = default alarm-enabled = yes security-enabled = no port-enabled = no slot-enabled = no coldstart-enabled = yes warmstart-enabled = yes linkdown-enabled = yes linkup-enabled = yes ascend-enabled = yes console-enabled = yes use-exceeded-enabled = yes password-enabled = yes fr-linkup-enabled = yes fr-linkdown-enabled = yes event-overwrite-enabled = yes radius-change-enabled = yes lan-modem-enabled = yes slot-profile-change-enabled = yes power-supply-enabled = yes authentication-enabled = yes config-change-enabled = yes sys-clock-drift-enabled = yes suspect-access-resource-enabled = yes watchdog-warning-enabled = yes controller-switchover-enabled = no call-log-serv-change-enabled = yes wan-line-state-change-enabled = yes call-log-dropped-pkt-enabled = yes lim-sparing-enabled = no interface-sparing-enabled = no secondary-controller-state-change-enabled = no pctfi-trunk-status-change-enabled = yes no-resource-available-enabled = yes dsl-thresh-trap-enabled = no atm-pvc-failure-trap-enabled = no

NavisAccess DSL Installation and Administration Guide 4-13 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

atm-ima-alarm-trap-enabled = no ascend-link-down-trap-enabled = no ascend-link-up-trap-enabled = no snmp-illegal-access-attempt = no Consult your Stinger documentation for details on these parameters. 5 Enter a host-name (up to 16 characters), as follows: set host-name = my_host_name The host-name specifies the hostname of the NavisAccess DSL station. This is the host to which the device will send SNMP traps. If the host-address field contains an IP address, the specified name is not used to actually locate the host. 6 Enter an IP address for the host-address. For example: set host-address = 10.2.3.4 The host-address is the same address as that of the NavisAccess DSL station. In a distributed NavisAccess DSL installation, traps must be sent to the IP address of the machine on which the Scheduling Server has been installed. 7 Enter the type of trap notification you want reported to NavisAccess DSL. When running SNMP version 3, you must create a Notification Profile (refer to “Creating a SNMP v3 trap notification profile on the Stinger”, for further information), which will iterate the system to find trap profiles with matching tags and the parameters in the trap profiles will be used to send traps to the network. 8 Once created, enter the tag values that are used to select target addresses for a particular operation: set notify-tag-list = v3trapprofile 9 Enter a target parameter for the traps to be sent. When running SNMP version 3, you must create a new SNMP target profile (refer to “Creating a SNMP v3 target profile for the Stinger”). 10 Enter the default target parameter for the traps to be sent. For example: set target-params-name = default 11 Specify that the Stinger should send its port status to the host as follows: set port-enabled = yes If enabled, the Boxmap will show updated port status in real-time. 12 Specify that the device can be automatically re-disovered when a slot’s staus changes as follows: set slot-enabled = yes 13 Specify that when the controller switches-over that a trap will be sent to the identified host. For example: set controller-switchover-enabled = 14 Specify that the line interface module (LIM) sparing trap should to be sent to the identified host. For example: set lim-sparing-enabled = yes 15 Specify that the interface (port) redundancy trap should to be sent to the identified host. For example: set interface-sparing-enabled = yes

4-14 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

16 Specify that when the secondary controller changes states that a trap is sent to the identified host. For example: set secondary-controller-state-change-enabled = yes Consult the device documentation for further information on defining the parameters. 17 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a “TRAP/host-name written” message.

Configuring a Soft IP address on the Stinger

The soft IP address is the ‘single’ IP address that could be used to reach the Stinger at all times, particularly after a redundancy switchover. When the system IP address (discussed in “Configuring a Global IP address on the Stinger”, immediatley following this section) is set to the soft IP address, NavisAccess DSL uses the soft IP address to discover and communicate with the device.

To configure a soft IP address on the Stinger: 1 Attach to the Stinger via Telnet or through the console port. 2 Log in with write access 3 At the command prompt, enter: read ip-interface {{any any 0}0} This will return an “IP-INTERFACE read” message and a new command prompt. 4 At the command prompt, enter: list This will return a list similar to the following: [in IP-INTERFACE/{ { any-shelf any-slot 0 } 0 }] interface-address* = { { any-shelf any-slot 0 } 0 } ip-address = 0.0.0.0/0 netmask = 0.0.0.0 proxy-mode = Off rip-mode = routing-off route-filter = "" rip2-use-multicast = yes directed-broadcast-allowed = yes management-only-interface = no 5 Set the IP-address parameter, or the soft IP address which will be discovered by NavisAccess DSL. For example: set ip-address = 10.2.3.4/24 6 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a "IP-INTERFACE written" message.

NavisAccess DSL Installation and Administration Guide 4-15 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

Configuring a Global IP address on the Stinger

The system IP address MUST also be set in the global IP address profile, and it should be the same address asthe soft IP to ensure the proper functionality of NavisAccess.

To configure a global IP address on the Stinger: 1 Attach to the Stinger via Telnet or through the console port. 2 Log in with write access 3 At the command prompt, enter: read ip-global This will return an “IP-GLOBAL read” message and a new command prompt. 4 At the command prompt, enter: list This will return a list similar to the following: [in IP-GLOBAL] domain-name = "" dns-primary-server = 0.0.0.0 dns-secondary-server = 0.0.0.0 dns-server-query-type = udp system-ip-addr = 10.2.3.6/24 5 Set the system-ip-address parameter to the same ip-address that was set in the Soft IP profile. For example: set system-ip-address = 10.2.3.4/24 6 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a "IP-GLOBAL written" message.

Enable call logging on the Stinger

In order for NavisAccess DSL to receive data from the Stinger, the Call Logging feature must be enabled and set to send data to NavisAccess DSL. The call-logging packet contains information about the device, such as the IP Address of the device sending the packet. NavisAccess uses this information for device discovery, as well as auto-creating DSL Line Groups and Services.

Note: Only Stingers loaded with TAOS versions of 9.0 or higher support call logging.

Note: When sending a call-logging packet, Stinger will determine which device IP Address to send in the following order: 1 If ip-global is set, Stinger sends the ip-global address in the packet.

4-16 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

2 If neither ip-global or the Soft IP is set, the Ethernet IP of the Primary Controller is sent by Stinger.

Note: Call-logging data will not be sent unless the NavisAccess DSL Software Option is enabled on the device. 30-day evaluations of call-logging are available. See “Enabling call-logging for evaluation purposes,” following this section, for details.

To configure Call Logging for use with NavisAccess DSL: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access 3 At the command prompt, enter: read call-logging This will return a "CALL-LOGGING read" message, and a new command prompt. 4 At the command prompt, enter: list This will return a parameter list similar to the following. call-log-enable = no call-log-host-1 = 0.0.0.0 call-log-host-2 = 0.0.0.0 call-log-host-3 = 0.0.0.0 call-log-port = 1646 call-log-key = "ascend" call-log-timeout = 0 call-log-id-base = acct-base-10 call-log-reset-time = 0 call-log-stop-only = yes call-log-limit-retry = 0 call-log-server-index = host-1 call-log-radius-compat = vendor-specific call-log-multi-packet = no call-log-evaluation-end-julian-time = 0 call-log-stream-period = 15 5 Set the call-log enable parameter to “yes” as follows: set call-log-enable = yes 6 The other parameters may or may not need to be set using the same syntax: set command-name = parameter-value Parameters are explained below, and shown with default values in place: call-log-host-1 = 0.0.0.0 call-log-host-2 = 0.0.0.0 call-log-host-3 = 0.0.0.0

NavisAccess DSL Installation and Administration Guide 4-17 Preparing Lucent Devices for Use with NavisAccess DSL Stinger/Stinger LS Preparation

These parameters point call logging information to the NavisAccess DSL. Each Host #n parameter can specify the IP address of one NavisAccess DSL standalone server or call-logging receiver (distributed installation). The device first tries to connect to machine #1 for call-logging. If it receives no response, it tries to connect to machine #2. If it receives no response from machine #2, it tries machine #3. In a distributed installation, call-logging must point at a machine on which the Call Logging Receiver is installed. There may be multiple machines with Call-Logging Receivers. call-log-port = 1646 The call-log-port parameter specifies the UDP destination port to use for call-logging requests. The default zero indicates any UDP port. If you specify a different number, the call log host (NavisAccess DSL) must specify the same port number (the numbers must match). By default, NavisAccess DSL uses port 1646. This is the recommended setting on Lucent devices. call-log-key = "ascend" Enter a Call Logging key. The installed default is “ascend”. It is recommended that the default value of “ascend” is used. If you prefer a different value, use the System Options Call-Logging tab to change the default value prior to turning on call-logging on the devices. The key allows the device to send data to NavisAccess DSL. The same Key entered on the device must also be entered in NavisAccess DSL. A default Call Logging Key can be entered in NavisAccess DSL using the Key field on the Call Logging Configuration tab found under Config > System Options. To enter a Key different from the default, open the device Boxmap, right-click on the Configuration icon and choose Configuration. Enter the new key in the Call Logging field. call-log-timeout =0 The number of seconds the device will wait for a response to a call-logging request. This value can be set from 1 to 10. 0 is the default, which disables the timer. 10 is recommended call-log-reset-time = 0 Indicates the number of seconds that must elapse before the device returns to using the primary call log host (call-log-host-1). The default zero disables the reset to the primary call log host. call-log-limit-retry = 2 If the NavisAccess DSL station does not acknowledge a Start or Stop packet within the number of seconds in call-log-timeout, the device tries again, re-sending the packet until the server responds or the packet is dropped because the queue is full. The call-log-limit-retry parameter sets the maximum number of retries for these packets. A value of 0 (the default) indicates an unlimited number of retries. There is minimum of 1 retry. For example, setting the parameter to 10 retries would make a total of 11 attempts: the original attempt plus 10 retries. Recommended values are 2 or 3.

Call-log-stream-period = 15 The Call-Log-Stream-period has a default of 15. This setting represents the number of minutes between snapshots for stream packets. The default setting of 15 indicates Navis will send call logging streaming packets every 15 minutes. This number should not be modified.

4-18 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSL TNT Preparation

7 Make the necessary setting changes to the parameters discussed in Step 6. Following is a sample setting of Call Logging parameters. Comments are shown in brackets [ ]. Set call-log-enable = yes [Must be set or Call Logging will not work] Set call-log-host-1 = 150.10.10.10 [NavisAccess DSL call logging receiver or standalone] Set call-log-host-2 = 150.10.10.12 [Alternate NavisAccess DSL machine] Set call-log-port = 1646 Set call-log-key = mysecretstring [Must match string entered via NavisAccess DSL. The default is ascend on NavisAccess DSL.] Set call-log-timeout = 2 Set call-log-id-base = acct-base-16 [This parameter must be set as shown.] Call-log-radius-compat = [This parameter must be set as shown] 16-bit-vendor-specific Set call-logging-multipacket = no [This parameter must be set as shown]

8 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a "CALL-LOGGING written" message.

Enable call-logging for evaluation purposes

If the NavisAccess DSL Software Option is not available on the device, call-logging can be turned on for 30 days using the following procedure.

Enable call-logging for evaluation purposes as follows: 1 Log on to the device with debug privileges. 2 Switch to debug mode and enter cleval This will start call-logging, which will run for 30 days. At the end of 30 days, call-logging data will no longer be sent. This can only be re-started if the device is rebooted. In other words, the cleval command works only one time per-device restart.

DSL TNT Preparation

Use the following as a checklist for enabling communication between the DSLTNT device and NavisAccess:

Check Preparation Step Page in Chapter

Enabling SNMP, community strings on the DSLTNT page 4-20

Configuring SNMP Trap destinations for the DSLTNT page 4-22

Configuring a Global IP address on the DSLTNT page 4-24

NavisAccess DSL Installation and Administration Guide 4-19 Preparing Lucent Devices for Use with NavisAccess DSL DSL TNT Preparation

Enabling SNMP, community strings on the DSLTNT

SNMP validates each message with a password-like mechanism called a Community String. SNMPv1 uses a Read and Read/Write community strings. SNMPv3 uses a user name/password combination.

NavisAccess DSL supports both SNMPv1 and SNMPv3. If you are using SNMPv3, you must also follow the steps described in Setting SNMPv3 for the Stinger.

To enable SNMP and set security on the device: 1 Attach to the device via Telnet or through the console port 2 Log in with write access. 3 At the command prompt, enter: read snmp This will return a “SNMP read” message, and a new command prompt. 4 At the command prompt, enter: list This will return the following parameter list:

enabled = yes read-community = public read-write-enabled = yes read-write-community = write enforce-address-security = no read-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0+ write-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 + contact = syscontact_before location = "" queue-depth = 0 csm-modem-diag = no engine-id = 80:00:02:11:03:00:c0:7b:a0:d0:28:00 engine-boots = 18 snmp-message-type = v1-and-v3 security-level = none enable-vacm = no notification-log-age-out = 1440 bit-strings-allowed = yes Admin> write

5 Set the enabled parameter to Yes as follows. set enabled = yes If the enabled parameter in the SNMP profile is set to No (the default), the device cannot be accessed by NavisAccess DSL.

4-20 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSL TNT Preparation

6 If necessary, set new read-community and read-write-community strings (up to 32 characters) as follows: set read-community = secret_string set read-write-community = unique_string The read-community string permits read access to the device and the read-write string permits read/write access.

Note: The read and write Community Names used by NavisAccess DSL must match what is specified on the device. Otherwise, communication cannot be established with the device. 7 Set the enforce-address-security parameter as follows: set enforce-address-security = yes/no If the enforce-address-security parameter is set to No (its default value), any SNMP manager that presents the right community name will be allowed access (if value is left at no, please continue to Step 10). If it is set to Yes, the device checks the source IP address of the SNMP manager and allows access only to those IP addresses listed in the read-access-host and write-access-host arrays. You can list up to five IP hosts that can access the MIB read-write access, and up to five hosts that can read traps and other information. If SNMP security access is used, all NavisAccess DSL machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess DSL via Telnet or Xterm to not have to have their IP addresses included.) 8 If desired, set IP addresses for up to five read-access-hosts. For example: set read-access-hosts 1 = 10.2.3.4 set read-access-hosts 2 = 10.2.3.5 set read-access-hosts 3 = 10.2.3.6 set read-access-hosts 4 = 10.2.50.123 set read-access-hosts 5 = 10.2.50.124 When this parameter is set, only NavisAccess DSL stations logging in from the set IP addresses will be granted read-access to the device. 9 If desired, set IP addresses for up to five write-access hosts. For example: set write-access-hosts 1 = 10.2.3.4 set write-access-hosts 2 = 10.2.3.5 set write-access-hosts 3 = 10.2.3.6 set write-access-hosts 4 = 10.2.50.123 set write-access-hosts 5 = 10.2.50.124 When this parameter is set, only NavisAccess DSL stations logging in from the set IP addresses will be granted write-access to the device. 10 It is recommended that you set the contact and location parameters with the name and location of the person to contact if there is a problem with the unit (up to 84 characters). For example: set contact = Mary Smith set location = Green Bay office, 555-1212

NavisAccess DSL Installation and Administration Guide 4-21 Preparing Lucent Devices for Use with NavisAccess DSL DSL TNT Preparation

11 Set the message type. NavisAccess DSL supports all three message types. Options are:

v1-only The SNMP agent discards SNMPv3 messages. v3-only The SNMP discards SNMPv1 messages

v1-and-v3 The SNMP agent supports both the SNMPv1 and SNMPv3 protocols. This is the default setting.

12 For example, to set the message type to v1-and-v3, enter: set snmp-message-type = v1-and-v3 13 SNMP v3 users: Set the security-level to auth-nopriv. For Example: set security-level = auth-nopriv

Note: The security-level must be set to auth-nopriv. If this is not done, NavisAccess DSL will have difficulty in discovering the device. 14 The settings for bit-strings-allowed can be left as the default: bit-strings-allowed = yes 15 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by an “SNMP written” message.

Configuring SNMP Trap destinations for the DSLTNT

The Lucent DSLTNT sends messages in the form of SNMP Traps. These Traps are sent to a management station (such as NavisAccess DSL) for logging and interpretation.

If there is an existing Management Station in your network, the devices may be set up to pass all Traps to it. Contact the network administrator for this information.

4-22 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSL TNT Preparation

host-name* = "" active-enabled = yes community-name = "" host-address = 0.0.0.0 alarm-enabled = yes security-enabled = no port-enabled = no slot-enabled = no coldstart-enabled = yes warmstart-enabled = yes linkdown-enabled = yes linkup-enabled = yes ascend-enabled = yes console-enabled = yes use-exceeded-enabled = yes password-enabled = yes fr-linkup-enabled = yes fr-linkdown-enabled = yes event-overwrite-enabled = yes radius-change-enabled = yes mcast-monitor-enabled = yes lan-modem-enabled = yes dirdo-enabled = yes slot-profile-change-enabled = yes power-supply-enabled = yes multishelf-enabled = yes authentication-enabled = yes config-change-enabled = yes sys-clock-drift-enabled = yes primary-sdtn-empty-enabled = yes secondary-sdtn-empty-enabled = yes suspect-access-rescource-enabled = yes watchdog-warning-enabled = yes controller-switchover-enabled = no call-log-serv-change-enabled = yes secondary-controller-state-change-enabled = no pctfi-trunk-status-change-enabled = yes no-resource-available-enabled = yes Consult your DSL TNT documentation for details on these parameters. 5 Enter a host-name (up to 16 characters), as follows: set host-name = my_host_name The host-name specifies the hostname of the NavisAccess DSL station. This is the host to which the device will send SNMP traps. If the host-address field contains an IP address, the specified name is not used to actually locate the host.

NavisAccess DSL Installation and Administration Guide 4-23 Preparing Lucent Devices for Use with NavisAccess DSL DSL TNT Preparation

6 Enter a community-name (up to 31 characters), as follows: set community-name = my_community-name This specifies the SNMP community name associated with the SNMP PDU (Protocol Data Units). The string you specify becomes a password that the device sends to NavisAccess DSL when an SNMP trap event occurs. The password authenticates the sender identified by the host address. 7 Enter an IP address for the host-address. For example: set host-address = 10.2.3.4 The host-address is the same address as that of the NavisAccess DSL station. In a distributed NavisAccess DSL installation, traps must be sent to the IP address of the machine on which the Scheduling Server has been installed. 8 Enter the default trap notification you want reported to NavisAccess DSL. For example: notify-tag-list = default SNMP v1 traps will be sent when default is entered. 9 Enter the default target parameter for the traps to be sent. For example: target-params-name = default default is the target parameter for SNMP v1 traps to be sent. 10 Enable any class of Traps you want reported to NavisAccess DSL. For example:

Note: Setting port-enabled and slot-enabled to yes, allows Boxmap to show port status correctly. set alarm-enabled = yes set security-enabled = yes set port-enabled = yes set slot-enabled = yes set multishelf-enabled = yes set config-change-enabled = yes Consult the device documentation for details on these trap definitions. 11 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a “TRAP/host-name written” message.

Configuring a Global IP address on the DSLTNT

To ensure that the DSLTNT devices properly report all needed data, such as call-logging packets, to NavisAccess DSL, a global IP address must be configured.

To configure a global IP address: 1 Attach to the DSLTNT via Telnet or through the console port. 2 Log in with write access 3 At the command prompt, enter: read ip-global This will return an "IP-GLOBAL read" message, and a new command prompt.

4-24 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

4 At the command prompt, enter: list This will return a parameter list similar to the following: domain-name=abc.com dns-primary-server=10.65.212.178 dns-secondary-server=0.0.0.0 system-ip-addr=0.0.0.0 soft-ip-interface-addr=0.0.0.0 5 Set the system-ip-addr parameter, which designates the source address for IP traffic originating from the device. For example: set system-ip-addr=10.2.3.4 6 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a "IP-GLOBAL written" message.

DSLMAX and DSLTerminator Preparation

Use the following as a checklist for enabling communication between the DSLMAX and DSL Terminator device and NavisAccess:

Check Preparation Step Page in Chapter

Setting SNMP community strings for the DSLMAX and page 4-25 DSLTerminator

Configuring trap destinations for the DSLMAX and page 4-27 DSLTerminator

Setting SNMPV3 for the DSLTerminator and DSLMAX page 4-28

Configuring SNMP Security on the DSLMAX and page 4-30 DSLTerminator

Setting SNMP community strings for the DSLMAX and DSLTerminator

SNMP validates each message with a password-like mechanism called a Community Name. SNMPv1 uses a Read and Read/Write community strings. SNMP v3 uses security levels.

Note: NavisAccess DSL supports both SNMPv1 and SNMPv3 on both the DSLMAX20 and DSL Terminator devices.

For SNMPv1, there are two communities defined on the DSLTerminator and DSLMAX: • Read Comm Enables an SNMP manager to perform read commands (GET and GET NEXT) to request specific information. The default Read Comm string is public.

NavisAccess DSL Installation and Administration Guide 4-25 Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

• R/W Comm Enables an SNMP manager to perform both read and write commands (GET, GET NEXT, and SET), which means the application can access management information, set alarm thresholds, and change some settings on the devices. The default R/W Comm string is write.

If there is an existing management station on your network, the community names may have been changed from the default values. Contact the network administrator for this information.

Note: The read and write Community Names used by NavisAccess DSL must match what is specified by (on) the device. Otherwise, communication cannot be established with the device.

Security Note: There is no way to turn off SNMP write, so you must change the default read-write string to secure the unit against unauthorized SNMP access.

To configure the SNMP community names: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 Open the Ethernet menu. 4 Open the Mod Config submenu. 5 Open the SNMP Options submenu. 6 Make sure SNMP is enabled by setting read/write enable to Yes: R/W Comm Enable=Yes 7 Enter up to 16 characters for the Read Comm parameter. For example: Read Comm=secret_string 8 Enter up to 16 characters for the R/W Comm parameter. For example: R/W Comm=unique_string 9 Set the message type. NavisAccess DSL supports all three message types on the Stinger device. Options are:

– V1-and-V3 The SNMP agent supports both the SNMPv1 and SNMPv3 protocols. This is the default setting.

– V1-only The SNMP agent discards SNMPv3 messages.

– V3-only The SNMP discards SNMPv1 messages. 10 SNMP v3 users: Set the Security Level parameter to auth-nopriv. For example: Security Level=auth-nopriv

Note: The security-level must be set to auth-nopriv. If this is not done, NavisAccess DSL will have difficulty in discovering the devic+e. 11 Save and close the Ethernet profile.

4-26 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

Configuring trap destinations for the DSLMAX and DSLTerminator

The Lucent DSLMAX and DSL Terminator devices send alarm messages in the form of SNMP Traps. These Traps are sent to a management station (such as NavisAccess DSL) for logging and interpretation. If there is an existing Management Station in your network, the devices may be set up to pass all Traps to it. Contact the network administrator for this information.

Configuring the trap destinations:

To configure the DSLMAX and DSL Terminator trap destination: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 Open the Ethernet menu. 4 Open the SNMP Traps menu. 5 Press [Enter] to open a profile.

6 Assign a name to the profile. For example: Name=Navis_Machine The name can be up to 31 characters. It is typically set to the destination of the Traps (for example, the machine running NavisAccess DSL). 7 Turn on traps for alarm events, port state changes, security events and OSPF events as needed. Alarm=Yes Port=Yes Security=Yes OSPF=Yes (Note:this parameter is DSLMAX specific) 8 Enter the SNMP community string. For example: Comm=secret_string

NavisAccess DSL Installation and Administration Guide 4-27 Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

The entered string must match the SNMP read/write or read “community name,” which becomes a password sent to the SNMP management station when an SNMP trap event occurs. It authenticates the sender who is identified by the source IP address. See “Setting SNMP community strings”.

Note: To turn off SNMP traps, delete the value for the Comm parameter and set the next parameter (Dest) to 0.0.0.0. 9 Specify the IP address of the NavisAccess DSL machine. For example: Dest=192.168.50.55 In a distributed NavisAccess DSL installation, traps must be sent to the IP address of the machine on which the Scheduling Server has been installed.

Note: To turn off SNMP traps, set Dest=0.0.0.0 and delete the value for Comm. 10 Open the “Enable traps...” profile to set specific trap to yes. The menu will appear similar to the following:

11 Select the traps you wish to have sent to NavisAccess DSL. Please consult the MAX documentation for explanations of available traps. 12 Save and close the SNMP Traps Profile.

Setting SNMP v3 for the DSLTerminator and DSLMAX

NavisAccess DSL v 5.1 provides support for SNMP v3 user name/password authentication. The SNMP v3 user name and password must be set within NavisAccess DSL, and also configured on the device. Note: SNMPv3 functionality is only available if the NavisAccess DSL Software Option is enabled on the device.

To configure SNMP v3 on the MAX, Terminator and/or DSL MAX20: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access.

4-28 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

3 Open the Ethernet menu. 4 Open the SNMPv3 USM Users menu.

5 Assign a name for the profile, for example: Name=SNMPv3_Profile This name must be matched within NavisAccess DSL. 6 Assign a password to the profile, for example: snmpauthpass This password must be matched within NavisAccess DSL. 7 Set the profile to Active=yes to turn on SNMPv3. The R/W Access parameter specifies whether or not the user name has write- access to the device. Set to Yes to enable write-access. 8 Set the Auth Protocol parameter as follows: Auth Protocol=md5-auth Note: MD5-Auth is the only protocol supported by NavisAccess DSL.

Note: The Priv Protocol parameter is not available at this time. 9 Save and close the profile.

NavisAccess DSL Installation and Administration Guide 4-29 Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

Configuring SNMP Security on the DSLMAX and DSLTerminator

The SNMP Security feature on the MAX, Terminator and DSL MAX20 restricts device access to only those management stations specifically entered on the device. If the Security feature is currently enabled on your devices, you need to update the settings to include the NavisAccess DSL station.

You can list up to five IP hosts that can access the MIB read-write access, and up to five hosts that can read traps and other information. If SNMP security access is used, all NavisAccess DSL machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess DSL via Telnet or Xterm to not have to have their IP addresses included.)

Following are details about specifying which hosts can access the MIB.

To configure SNMP manager access: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 Open the Ethernet menu. 4 Open the Mod Config submenu. 5 Open the SNMP Options submenu. 6 Set the Security parameter to Yes. Security=Yes This parameter specifies that the device compare the source IP address of packets containing SNMP commands against a list of qualified IP addresses. The unit checks the version and community strings before making source IP address comparisons. (The Security parameter does not affect those checks.) If Security is set to No, you do not need to enter the NavisAccess DSL machine address. 7 Specify the IP addresses of hosts that will have SNMP read permission. The NavisAccess DSL station must be included for NavisAccess DSL to manage the device. For example: RD Mgr1=10.1.2.3 RD Mgr2=10.1.2.4 RD Mgr3=10.1.2.5 RD Mgr4=10.1.2.6 RD Mgr5=10.1.2.7 If the Security parameter is set to Yes, only SNMP managers at those IP addresses will be allowed to execute the SNMP GET and GET-NEXT commands.

4-30 NavisAccess DSL Installation and Administration Guide Preparing Lucent Devices for Use with NavisAccess DSL DSLMAX and DSLTerminator Preparation

8 Specify the IP addresses of hosts that will have SNMP write permission. For example: WR Mgr1=10.1.2.3 WR Mgr2=10.1.2.4 WR Mgr3=10.1.2.5 WR Mgr4=10.1.2.6 WR Mgr5=10.1.2.7 If the Security parameter is set to Yes, only SNMP managers at those IP addresses will be allowed to execute the SNMP SET command. 9 Save and close the Ethernet profile.

NavisAccess DSL Installation and Administration Guide 4-31

Security 5

Security in NavisAccess DSL ...... 5-2

Users and user groups ...... 5-2 Working with access rights ...... 5-4

Pre-defined user group permissioned features and functions ...... 5-6

Pre-defined user group permissioned operations...... 5-11

User Manager...... 5-12

Define a new user...... 5-15

Define user: group membership...... 5-16

Define a new user group ...... 5-19

Define user group: feature access ...... 5-21

Logging out of NavisAccess DSL ...... 5-21

Logging into NavisAccess DSL...... 5-21

Change password ...... 5-22

The User Session Manager applet ...... 5-22

Audit Trails ...... 5-24

NavisAccess DSL Installation and Administration Guide 5-1 Security Security in NavisAccess DSL

Security in NavisAccess DSL

Security in NavisAccess DSL is maintained by an Administrator who gives the user access by assigning that user to a User Group, which maintains a set of rights.

User Groups are used to assign complex rights to groups of users. All members of a User Group are granted the access rights that are assigned to the User Group. Users may be assigned to multiple User Groups, thus obtaining combined access rights.

User Group types: • Feature Access Group - This type of User Group (i.e., Manager, Operator, CNM User) provides its members with access to NavisAccess DSL features and feature functions (i.e., Reports, User Manager, Examiner, etc.) not data. • Data Access Group - This type of User Group provides its members with data. Data, assigned by an Administrator User Group member, can then be edited, viewed, or reported on (depending on the feature access group you have membership in).

Access rights within User Groups are defined in the following ways: • Feature Access - A feature, or feature set, is a set of viewable components that the user can launch and view such as Examiner, DSL Watch, etc. • Feature Function Access - Feature functions are defined as the operations that a user may use within a feature. The Administrator has the ability to define what feature a user (or group user) can access as well as specific feature related functions. • Data Access - Data Access relates to the ability of a user to access actual data. Users may be permissioned to access data such as Services, Groups, Devices, Reports, etc. Data Access is used in conjunction with Feature Access and Feature Function Access to provide the flexibility to define complex rights. For example, the user Calvin may be permissioned to access the DSL Watch feature but only data that belongs to IPS1.

Users and user groups

Users in NavisAccess DSL obtain rights through the User Groups that they are a part of. Users can be assigned to one or more groups giving them the combined rights of all groups.

NavisAccess DSL has two pre-defined users, and four pre-defined user groups.

Pre-defined users

Table 5-1. Predefined Users

User Type Permissioned Access

Admin All features, feature functions, and data.

5-2 NavisAccess DSL Installation and Administration Guide Security Users and user groups

Table 5-1. Predefined Users (continued)

User Type Permissioned Access

CNM Admin Data Access can be assigned per customer. (Customer Network Management)

Pre-defined user groups

Table 5-2. Pre-defined User Groups

User Group Type Permissioned Access

Administrator (Data & All features, functions and data. Including adding and Feature Access) editing Users.

Managers All Manager User Group features and functions. (Feature Access) Data Access must be assigned to the user. This can be done by creating a “data access” user group with the desired data access and assigning the user to both the Managers Group and the Data Access Group.

Operators All Operator User Group features and functions. (Feature Access) Data Access must be assigned to the user. This can easily be done by creating a “data access” user group with the desired data access and assigning the user to both the Operators Group and the Data Access Group.

CNM User All CNM User Group features and functions. Data (Customer Network Access can be assigned per customer. Management) (Feature Access)

Using one of the pre-defined feature access User Groups above, along with a data access User Group (that you create) a user now has the desired features and data to access.

For example, at company ISP1 an Administrator creates the User Andrew. The Administrator wants to allow Andrew to help out in the operation of the database, to ensure that it runs smoothly. Feature wise, Andrew should have access to running reports, and viewing, so the Administrator assigns Andrew to the Operators User Group.

The Administrator now permissions Andrew specific data to view and run reports on, so the Administrator assigns Andrew to be a member of the ISP1 Data Access User Group (which the Administrator has already created). ISP1 Data Access members automatically receive all the access rights the data the Administrator desires.

NavisAccess DSL Installation and Administration Guide 5-3 Security Users and user groups

Now Andrew is a member of the following groups: • Operators (Feature Access) • ISP1 Data Access (Data Access)

Using the User Manager, an Administrator can add a new user and user groups can be added and maintained giving the user any number of features and access.

Working with access rights

When permissioning access to the NavisAccess DSL Database, an Administrator has several challenges: • To allow the user access to the features that they need, and no more. • To allow the user access to the data that they need, and no more. • To give the user enough autonomy where they feel they are responsible for their own data within NavisAccess DSL.

NavisAccess DSL comes with four pre-defined User Groups that have different access levels. Using these pre-defined User Groups, along with one or two specific “data access” user groups, will help the Administrator more easily keep track of access to the data within the database, while giving the user the independence they need when editing/viewing their customer's data.

Pre-defined groups permission users to view/edit specific parts of the NavisAccess DSL database by limiting their access to certain NavisAccess DSL functions. To see a complete list, refer to Pre-defined User Group permissioned features and functions. Once the user has access to the NavisAccess DSL function, the Administrator must then grant access rights to the data which the user will be viewing/editing.

This can be done by creating a “data access” user group. A Data Access User Group can be permissioned this access to the desired data, thus by assigning a member to an “Access Data User Group”, this member would now have the access rights to the desired data. Combining this with a membership to one of the pre-defined groups would give the user the right combination of feature and data access.

5-4 NavisAccess DSL Installation and Administration Guide Security Users and user groups

Pre-defined user group access rights scenario

Note: This scenario assumes that the Administrator as made the User a member of the appropriate Data Access User Group, giving the user desired data access rights.

In the diagram below: • Customer obtains Internet access via Small ISP, which leases Customer a service of 20 connections. • Big ISP leases Small ISP 1000 connections, which Small ISP uses to handle the growing demand of its customers.

Customer has a connection problem, it cannot get online. To remedy this problem, Customer calls Small ISP, which, given CNM User Group Access rights, can see that there is in fact a problem with 10 of the connections which Big ISP has leased them.

Small ISP contacts a Big ISP Operator User Group member, which looks at the service leased to Small ISP and determines that it is a device problem. The Operator User Group Member then contacts a Manager User Group member who fixes the problem.

This of course is a very simple scenario, and through preventative maintenance can easily be avoided, but it demonstrates how the Pre-defined User Group Access rights can be used.

In Preventing this type of problem, an Operator User Group member can scan the Services and Devices on a regular basis, to ensure that a problem does not occur.

Pre-defined user group access rights

NavisAccess DSL has four pre-defined User Groups, each of which having access to specific features that help to define the role of each member in that group. In the following table, every User Group is paired with a “Motivation”, or the purpose behind giving membership to a user in a pre-defined User Group. In your organization, each member of a User Group will have the permission to access certain features, the feature access should reflect the role in which you want that member to play.

Table 5-3. Pre-defined User Group Access Rights

User Group Motivation Feature Access

Admin To administer Users and User Groups. To All features, including User Manager to which assign data to all users, and have top-level only an Admin User Group member has access. control over the NavisAccess DSL Database.

NavisAccess DSL Installation and Administration Guide 5-5 Security Users and user groups

Table 5-3. Pre-defined User Group Access Rights (continued)

User Group Motivation Feature Access

Manager To manage that data the in the NavisAccess All features except User Manager. A Manager DSL Database which is permissioned by the User Group member does not have permission Admin User Group member. to create and edit Users and User Groups.

Operator To ensure the smooth operation of the An Operator User Group member does not have NavisAccess DSL database, by monitoring permission to change any of the data assigned the data which is assigned by the Admin User by the Admin User Group member, but he does group member. If an Operator detects a have the ability to run reports on the data, problem, a Manager User group member which helps to ensure a smooth operation. should be contacted to remedy the problem. Features include: Examiner, Reports Exec, Report Wizard.

CNM User As a service oriented User Group, a CNM A CNM User Group oversees those services User Group member oversees the assigned by the Admin User Group member. A service-related data assigned by the Admin member of this group does not have the ability User Group member. to run reports, although a member can view any report assigned by the Admin User Group member. (The report is updated by the Operator User group member). Features include: Examiner, Show Groups, Show Reports, Show Services.

Pre-defined user group permissioned features and functions

The pre-defined User Groups come with certain changeable permissions by default. Several operations’ security access rights are unchangeable. These are listed in Pre-defined User Group Operations.

The following table is a break-down of NavisAccess DSL related features and functions, and if they are accessible or not via each pre-defined User Group.

Note: The Administrator User Group has access rights to every feature and function.

Table 5-4. Pre-defined User Group features and functions

Feature Feature Function Manager Operator CNM User

ADSL Line Code YNN Bits/bin

Copper Loop Test Bridge Tap Detection and Location YNN (Bridged)

Copper Loop Test Bridge Tap Detection and Location YNN (Lookout)

Copper Loop Test CLT Results Y N N

5-6 NavisAccess DSL Installation and Administration Guide Security Users and user groups

Table 5-4. Pre-defined User Group features and functions (continued)

Feature Feature Function Manager Operator CNM User

Copper Loop Test Complete Line test (Bridged) Y N N

Copper Loop Test Complete Line test (Lookout) Y N N

Copper Loop Test Complete Line Test w/p DSL Dig YNN Svc Params (Bridged)

Copper Loop Test Complete Line Test w/p DSL Dig YNN Svc Params (Lookout)

Copper Loop Test DSL Measurements (Bridged) Y N N

Copper Loop Test DSL Measurements (Lookout) Y N N

Copper Loop Test Load Coil Detection (Bridged) Y N N

Copper Loop Test Load Coil Detection (Lookout) Y N N

Copper Loop Test Wideband Noise Measurements YNN (Bridged)

Copper Loop Test Wideband Noise Measurements YNN (Lookout)

DB Maintenance Y N N

Device Card Code YNN Manager

DS1/E1 Trunk DS1/E1 Config Y N N Monitors

DS1/E1 Trunk DS1/E1 Current Y N N Monitors

DS1/E1 Trunk DS1/E1 Help Y N N Monitors

DS1/E1 Trunk DS1/E1 Intervals Y N N Monitors

DS1/E1 Trunk DS1/E1 Totals Y N N Monitors

DS3/E3 Trunk DS3/E3 Config Y N N Monitors

DS3/E3 Trunk DS3/E3 Config Help Y N N Monitors

NavisAccess DSL Installation and Administration Guide 5-7 Security Users and user groups

Table 5-4. Pre-defined User Group features and functions (continued)

Feature Feature Function Manager Operator CNM User

DS3/E3 Trunk DS3/E3 Current Y N N Monitors

DS3/E3 Trunk DS3/E3 Current Help Y N N Monitors

DS3/E3 Trunk DS3/E3 Help Y N N Monitors

DS3/E3 Trunk DS3/E3 Intervals Y N N Monitors

DS3/E3 Trunk DS3/E3 Intervals Help Y N N Monitors

DS3/E3 Trunk DS3/E3 Totals Y N N Monitors

DS3/E3 Trunk DS3/E3 Totals Help Y N N Monitors

DSL Device Watch Y N N

DSL Line Y N N

DSL Line Details Y N N

DSL Resource YNN Overview

DSL Watch Y N N

Event Viewer Y N N

Examiner Show Connections Y Y N

Examiner Show Customers Y Y N

Examiner Show Devices Y Y N

Examiner Show Groups Y Y Y

Examiner Show Reports Y Y Y

Examiner Show Services Y Y Y

Global Ops Add Customer Y N N

Global Ops Add Device Y N N

Global Ops Add Group Y N N

5-8 NavisAccess DSL Installation and Administration Guide Security Users and user groups

Table 5-4. Pre-defined User Group features and functions (continued)

Feature Feature Function Manager Operator CNM User

Global Ops Add Service Y N N

Global Ops Delete Customer Y N N

Global Ops Delete Device Y N N

Global Ops Delete Group Y N N

Global Ops Delete Line Group Y N N

Global Ops Delete Profile Y N N

Global Ops Delete Report Y N N

Global Ops Delete Service Y N N

Global Ops Duplicate Profile Y N N

Global Ops Duplicate Report Y N N

Global Ops Remove Interface Y N N

Global Ops Rename Customer Y N N

Global Ops Rename Device Y N N

Global Ops Rename Group Y N N

Global Ops Rename Interface Y N N

Global Ops Rename Profile Y N N

Global Ops Rename Report Y N N

Global Ops Rename Service Y N N

Manage Sessions Y N N

ML Config Y N N

OAM Test All Tests on Device Y N N

OAM Test OAM Test Delete Y N N

OAM Test OAM Tests Launch Y N N

OAM Test OAM Test Status Y N N

Report Exec Device Chassis - Last Completed YNN Day

Report Exec DSL CLT Results - All Results Y N N

NavisAccess DSL Installation and Administration Guide 5-9 Security Users and user groups

Table 5-4. Pre-defined User Group features and functions (continued)

Feature Feature Function Manager Operator CNM User

Report Exec DSL Line Status - Last Completed YNN Day

Report Exec DSL Line Status - Last Completed YNN Hour

Report Exec DSL Resources - Last Completed YNN Month

Report Exec DSL Resources - Snapshot Y N N

Report Exec DSL Sparing Status - Sparing Info Y N N

Report Exec Events - Last Completed Day Y N N

Report Exec Events - Last Completed Hour Y N N

Report Exec Interface Util - Last Completed Day Y N N

Report Exec Interval - Current Day Y N N

Report Exec Interval - Last Completed Day Y N N

Report Exec Interval - Last Completed Week Y N N

Report Exec NW Capacity Leaders - Last YNN Completed Day

Report Exec Top-N Interval - All Days of past YNN week

Report Exec Top-N Interval - last Completed Day Y N N

Report Exec Report Exec Y Y N

Report Wizard Report Wizard Y Y N

SONET/SDH Trunk SONET Config Y N N Monitors

SONET/SDH Trunk SONET Config Help Y N N Monitors

SONET/SDH Trunk SONET Current Y N N Monitors

SONET/SDH Trunk SONET Current Help Y N N Monitors

SONET/SDH Trunk SONET Help Y N N Monitors

5-10 NavisAccess DSL Installation and Administration Guide Security Users and user groups

Table 5-4. Pre-defined User Group features and functions (continued)

Feature Feature Function Manager Operator CNM User

SONET/SDH Trunk SONET Intervals Y N N Monitors

SONET/SDH Trunk SONET Intervals Help Y N N Monitors

SONET/SDH Trunk SONET Totals Y N N Monitors

SONET/SDH Trunk SONET Totals Help Y N N Monitors

Pre-defined user group permissioned operations

Certain operations’ access rights are unchangeable. These operations are accessible by members of pre-defined User Groups. The following table is a break-down of NavisAccess DSL related operations, and if they are accessible or not via each pre-defined User Group.

Note: The Administrator User Group has access rights to every operation

Table 5-5. Pre-defined user group permissioned operations

Operation Manager Operator CNM User

Examiner:

Create Groups Y N N

Config Device:

Download Y N Y

Datababse Y Y N

Erase Y N N

Write Memory Y N N

Upload Y N N

Image file: Y N

Directory Y N N

Download Y N N

Erase Y N N

Upload Y N N

NavisAccess DSL Installation and Administration Guide 5-11 Security User Manager

Table 5-5. Pre-defined user group permissioned operations (continued)

Operation Manager Operator CNM User

Scheduler N N N

Path Finder Y Y N

Performance Applets Y Y N

Alarm Monitor Y Y N

Threshold Manager Y N N

IPMAP Y Y N

System Options Y N N

Audit Trail Y N N

User Manager

The User Manager dialog box is accessed in NavisAccess DSL by selecting Security>Manager from the menu.

The User Manager allows an Administrator (or a user with Administrator rights) to add and edit Users and User Groups in the NavisAccess DSL Database.

5-12 NavisAccess DSL Installation and Administration Guide Security User Manager

The following information is displayed in the User Manager window:

Column Definition

UserName Name of user

Description Description of user

Status Indicates whether the User is Active or Locked Out (De-activated).

Auth Indicates whether the user is authenticated via the NavisAccess DSL Database or via Radius.

The User Manager allows you to perform the following functions: • Edit an existing user • Edit an existing user group • Add a new user • Add a new user group • Delete an added user or user group • Deactivate/activate a user

Edit user

Once a user has been created, an Administrator can edit a user profile to permit more simultaneous logins, add or take away permissions, and change the access to specific data within the database.

Pre-defined Users and User Groups can also be edited with one exception, you cannot change access (Data, Feature, and Feature Function) rights to the Administrators User Group.

To open the Edit User window, click [Edit] in the User Manager.

The Edit User window allows you to change the following characteristics:

Description A brief statement describing the User. (limit 80 characters) Password Change an existing case-sensitive password. (limit 30 characters) Authentication Select whether the user will be authenticated locally or from a Radius server. Permit (#) Select the number of concurrent login instances that a user can Simultaneous maintain on the database. Selecting more than 1 allows the user to Legions login simultaneously to multiple NavisAccess DSL Clients. Selecting 0 will allow the user to login to any number of NavisAccess DSL clients, simultaneously. Password Never Click to specify that the password should never expire. Expires (not available in v5.1)

NavisAccess DSL Installation and Administration Guide 5-13 Security User Manager

Expires In (#) Days Select the number of days that the password will expire in. The default (not available in is 10 days v5.1) Start Prompting Specify the number of days (prior to password expiration) that the user is prompted to configure a new password. De-activate User Check to De-activate an active user. By default, the user is De-activated. (Setting will display in the Status column of the User Manager)

Once the settings have been properly configured, click [Next>] to edit the User’s Group Membership.

Edit user: group membership

This window is used to view and /or modify the Group(s) the user is a member of.

The use of User groups is very powerful in that it allows Administrators to assign rights to groups of users by assigning the rights to the User Group. All members of the User Group will be granted the access rights that are granted to the User Group itself. This eliminates the need to copy a user, or assign rights to a select group of users. This also allows the Administrator to skip the Data Access window and Feature Access window that would be required if the Administrator could not assign the user to pre-configured User Groups.

The Edit User: Group Membership window allows you to perform the following:

Add-> Add a User to the User Group (making the User a member of that group). When the [Add->] button is clicked, the highlighted User Group will move to the Members column. <-Remove Remove a User from the User group (revoking the User’s membership in that User Group). When the [<-Remove] button is clicked, the highlighted User Group will move to the Non Member column. Add All-> Moves all User Groups to the Member of column. Gives the user all permissions maintained by all User Groups. <-Remove All Moves all User Groups to the Non Member of column. Removes all permissions given to the user. Primary Group If a User adds data and/or features (Services, Devices, etc.) to the database, NavisAccess DSL will grant access rights for the new data and/or feature(s). NavisAccess DSL will grant the same access rights to the newly added data/feature(s) as maintained in the Primary Group.

Example:

User ISP1 ISP2

User Group CNM Users, CNM Users, ISP1 Data Access ISP2 Data Access

5-14 NavisAccess DSL Installation and Administration Guide Security User Manager

User ISP1 ISP2

Primary Group ISP1 Data Access ISP2 Data Access

ISP1 and ISP2 are both members of the CNM Users Group. However, ISP1’s data access rights are maintained through the ISP1 Data Access User Group, while ISP2’s data access rights are maintained through the ISP2 Data Access User Group.

If a member of the ISP1 team adds a new service, the Administrator wants only members of the ISP1 Data Access User Group to have access rights to that new service, not members of the CHM Users Group, because that would mean ISP2 members have access to ISP1’s service.

In this case ISP1’s Primary Group should be ISP1 Data Access User Group.

Once the membership to User Groups have been defined, click [Finish] to complete the editing process and return to the User Manager.

Define a new user

The Define User screen is the first screen out of two needed to create a new user in the NavisAccess DSL Database. In this screen, the Administrator will enter the User Name, Password, Authentication, the number of simultaneous logins and Password Age information.

To open the Define User window, click [New User] in the User Manager.

The Define User window allows you to add the following characteristics:

User Name Name of new user

Description A brief statement describing the User. (limit 80 characters)

Password Add a case-sensitive password. (limit 30 characters)

Authentication Select whether the user will be authenticated locally or from a Radius server.

Permit (#) Simultaneous Select the number of concurrent login instances that a Logins user can maintain on the database. Selecting more than 1 allows the user to login simultaneously to multiple NavisAccess DSL Clients. Selecting 0 will allow the user to login to any number of NavisAccess DSL clients, simultaneously.

Password Never Expires (not Click to specify that the password should never expire. available in v 5.1)

Expires In (#) Days (not Select the number of days that the password will expire available in v 5.1) in. The default is 10 days.

NavisAccess DSL Installation and Administration Guide 5-15 Security User Manager

User Name Name of new user

Start Prompting (not available Specify the number of days (prior to password expiration) in v 5.1) that the user is prompted to configure a new password.

De-activate User Check to De-activate an active user. By default, the user is De-activated. (Setting will display in the Status column of the User Manager)

Once the new user has been defined, click Next> to add the new user to a user group so he/she may gain access rights.

Define user: group membership

User Groups are very powerful in that they allow Administrators to assign rights to groups of users by assigning the rights to the User Group. All members of the User Group will be granted the access rights that are granted to the User Group itself. This eliminates the need to copy a user, or assign rights to a select group of users. This also allows the Administrator to skip the Data Access window and Feature Access window that would be required if the Administrator could not assign the user to pre-configured User Groups.

The Define User: Group Membership window allows you to perform the following:

Add-> Add a User to the User Group (making the User a member of that group). When the [Add->] button is clicked, the highlighted User Group will move to the Member of column. <-Remove Remove a User from the User group (revoking the User’s membership in that User Group). When the [<- Remove] button is clicked, the highlighted User Group will move to the Non Member of column. Add All-> Moves all User Groups to the Member of column. Gives the user all permissions maintained by all User Groups. <-Remove All Moves all User Groups to the Non Member of column. Removes all permissions given to the user. Primary Data If a User adds data and/or features (Services, Devices, etc.) to the database, Group NavisAccess DSL will grant access rights for the new data and/or feature(s). NavisAccess DSL will grant the same access rights to the newly added data/feature(s) as maintained in the Primary Data Group.

5-16 NavisAccess DSL Installation and Administration Guide Security User Manager

Example

User ISP1 ISP2

User Group CNM Users, CNM Users, ISP1 Data Access ISP2 Data Access

Primary Group ISP1 Data Access ISP2 Data Access

If a member of the ISP1 team adds a new service, the Administrator only wants members of the ISP1 Data Access User Group to have access rights to that new service, not members of the CNM Users Group, because that would mean ISP2 members have access to ISP1’s service!

In this case the Primary Data Group should be ISP1 Data Access User Group.

Edit an existing user group

NavisAccess DSL gives an Administrator the ability to add or take away access rights to data or features in User Groups that are pre-defined or have been created to serve a special need within your organization. Once rights are given or taken away from a User Group all members of that group will be able effected, that is, if you take away a User Group's access to specific data, all members of that group will not be able to access that data.

Pre-defined User Groups can also be edited with one exception, you cannot change access (Data, Feature, and Feature Function) rights to the Administrators User Group.

To open the Edit User Group window, highlight a User Group, and click [Edit] in the User Manager.

The Edit User Group window allows you to perform the following:

Description A brief statement describing the User Group. (limit 80 characters)

Add-> Add a User Group to the User Group (making the selected User Group a member of the edited User Group, giving all members of the edited User Group access to the data and features assigned to the selected User Group). When the [Add->] button is clicked, the highlighted User Group will move to the Members column.

<-Remove Remove a User Group from the User Group (revoking the edited User Group's membership in the selected User Group, denying access to data and features assigned to the selected User Group). When the [<-Remove] button is clicked, the highlighted User Group will move to the Non column.

Add All-> Moves all User Groups to the Member column. Gives the user all permissions maintained by all User Groups.

NavisAccess DSL Installation and Administration Guide 5-17 Security User Manager

Description A brief statement describing the User Group. (limit 80 characters)

<-Remove All Moves all User Groups to the Non Member column. Removes all permissions given (by other user groups) to the user.

Once the membership to User Groups have been defined, giving or revoking access rights to members of the edited User Group, click Next> to define Data Access rights for the User Group.

Edit user group: data access

The Data Access rights screen is used to assign data rights to a User Group. The data that has not been permissioned is displayed in an “Examiner-like” tree in the Not Managed column. The Left pane contains the data items that have been permissioned. (By default, Data will not be managed. The Administrator selects which data the User Group will have access to.)

The Edit User Group: Data Access window allows you to perform the following:

Manage All Grants access to all items (current and future). Clicking this disables the Managed tree, and lets NavisAccess DSL know that this User Group has access to all data. Grant-> Grants access to a selected item (Group, Device, Service, etc.). Select an item in the Not Managed column and click [Grant->, to move it to the Managed column. <-Revoke Revokes access to a selected item (Group, Device, Service, etc.). Select an item in the Managed column and click <-Revoke] to move it to the Non Managed column. <-Revoke All Revokes access to all managed items. Clicking [<-Revoke All] moves all items from the Managed column to the Non Managed column.

Once the User Group has been given access to the desired data, click Next> to edit Feature Access rights to the User Group.

Edit user group: Feature Access

Access rights to the right-click applications are permissioned using the Feature Access screen. Features and functions will appear in the popup menu only if they are permissioned to the User Group.

By default, features will not be managed. The Administrator selects which features the User Group will have access to.

5-18 NavisAccess DSL Installation and Administration Guide Security User Manager

The Edit User Group: Feature Access window allows you to perform the following:

Manage All Grants permission to all features (current and future). Clicking this disables the Permissioned tree, and lets NavisAccess DSL know that this User Group has permission to use to all features and feature functions Grant-> Grants permission to a selected feature or feature function. Select an item in the Not Permissioned column and click [Grant->] to move it to the Permissioned column. <-Revoke Revokes permission to a selected feature or feature function. Select an item in the Permissioned column and click [<-Revoke] to move it to the Not Permissioned column. <-Revoke All Revokes permission to all managed features and feature functions. Clicking [<-Revoke All ] moves all items from the Permissioned column to the Not Permissioned column.

Once the User Group has been permission to use features and feature functions, click [Finish] to complete the editing of the User Group and return to the User Manager. Define a new user group

An Administrator can add a new User Group to provide a set of features and/or data access rights to specific Users. Defining a new User Group starts by clicking the [New Group] button in the User Manager, opening the Define User Group window.

User Groups in NavisAccess DSL are very powerful in that they allow the Administrator to assign rights to groups of users by simply assigning the rights to the User Group. All members of the User Group will be granted the access rights that are granted to the User Group itself. As defined in Security, there are two types of User Groups: Feature Access User Groups, and Data Access User Groups. These two groups, used in conjunction with each other, provide its members with the desired mix of Features and Data.

Example

ISP Big leases services to ISP Small. ISP Big's Administrator creates an “ISP1 Data Access User Group,” the purpose of which is to provide its members with the Access Rights to view only the services that it leases from Big ISP.

The Define User Group window allows you to perform the following:

Add-> Add a User to the User Group (making the User a member of that group). When the [Add->] button is clicked, the highlighted User Group will move to the Member of column. <-Remove Remove a User from the User group (revoking the User's membership in that User Group). When the [<- Remove] button is clicked, the highlighted User Group will move to the Non Member of column. Add All-> Moves all User Groups to the Member column. Gives the user all permissions maintained by all User Groups. <-Remove All Moves all User Groups to the Non Member column. Removes all permissions given to the user. Once the new User Group has been defined, click Next> to add set the Data Access rights for the User Group.

NavisAccess DSL Installation and Administration Guide 5-19 Security User Manager

Define user group: data access

The Assign Data Access rights screen is used to assign data rights to a User Group. The data that has not been permissioned is displayed in an “Examiner-like” tree in the Not Managed column. The Left pane contains the data items that have been permissioned. (By default, Data will not be managed. The Administrator selects which data the User Group will have access to.)

The Define User Group: Data Access window allows you to perform the following:

Manage All Grants access to all items (current and future). Clicking this disables the Managed tree, and lets NavisAccess DSL know that this User Group has access to all data. Grant-> Grants access to a selected item (Group, Device, Service, etc.). Select an item in the Not Managed column and click [Grant->] to move it to the Managed column. <-Revoke Revokes access to a selected item (Group, Device, Service, etc.). Select an item in the Managed column and click [<-Revoke] to move it to the Not Managed column. <-Revoke All Revokes permission to all managed features and feature functions. Clicking [<-Revoke All ] moves all items from the Permissioned column to the Not Permissioned column.

Note: Before adding data to be managed by the User Group, define what data you want its members to have access to.

Using the same example used in Define a New User Group, the Administrator has already created the User Group “ISP1 Data Access User Group”, and now wants to allow the members of this group to manage two services leased to them, Service1 and Service2. From the Not Managed column, select Service1 and click [<-Grant]. Select Service2 and click [<-Grant]. The members now have access to the data they are being leased.

Once the new User Group has been given access to data, click Next> to add Feature Access rights to the User Group.

5-20 NavisAccess DSL Installation and Administration Guide Security User Manager

Define user group: feature access

Access rights to the right-click applications are permissioned using the Feature Access screen. Features and functions will appear in the popup menu only if they are permissioned to the User Group. By default, features will not be managed. The Administrator selects which features the User Group will have access to.

The Define User Group: Feature Access window allows you to perform the following:

Manage All Grants permission to all features (current and future). Clicking this disables the Permissioned tree, and lets NavisAccess DSL know that this User Group has permission to use to all features and feature functions. Grant-> Grants permission to a selected feature or feature function. Select an item in the Not Permissioned column and click [<-Grant] to move it to the Permissioned column. <-Grant Revoke Revokes permission to a selected feature or feature function. Select an item in the Permissioned column and click [<-Grant] to move it to the Not Permissioned column. <-Revoke All Revokes permission to all managed features and feature functions. Clicking [<-Revoke All ] moves all items from the Permissioned column to the Not Permissioned column.

Once the new User Group has been permission to use features and feature functions, click [Finish] to complete the making of the User Group, and return to the User Manager.

Logging out of NavisAccess DSL

To logout from NavisAccess DSL: 1 From the NavisAccess DSL main menu bar, select Security > Logout. The Logout window appears, prompting you to choose which NavisAccess DSL Database you wish to logout from. 2 Click [OK] to log out.

Logging into NavisAccess DSL

The following post-installation detail applies:

Upon first using NavisAccess DSL after installation, the default login User Name is “Admin”. The default password is also “Admin”. The Password is case sensitive.

Note: The Administrator should change the defaults to secure the workstation.

To log in to NavisAccess DSL: 1 From the NavisAccess DSL main menu bar, select Security > Login. The Login dialog box opens. 2 Enter a User Name and Password.

Note: You must log out before another user can log in to NavisAccess.

NavisAccess DSL Installation and Administration Guide 5-21 3 Select the domain that you will be logging into. If you are unsure of your Domain, contact your NavisAccess DSL Administrator. 4 Click [Ok] to log in.

Change password

To change a password: 1 From the NavisAccess DSL main menu bar, select Security > Change Password. The Change Password dialog box opens. 2 If your User Name is different from what appears in the User Name row, enter the correct name. 3 If your domain is different from what appears in the Domain selection box, scroll to select the desired domain. 4 Enter your Old Password as indicated. 5 Enter and Confirm a new password, as indicated. 6 Click OK.

Note: Any level user can access the Change Password dialog box when logged in. All users are allowed to change their own password. Only the Administrator can change the default Password “Admin” to secure the workstation initially.

The User Session Manager applet

Menu: Security > User Session Manager

The User Session Manager allows you to view and logout users who are logged into NavisAccess.

Note: You must be an Administrator user to logout a session.

Table 5-6. The User Session Manager Applet

Heading Description

Userlogin Name of the user who is logged in. The current session is indicated with an asterisk (*).

Note: The current session cannot be logged out.

Groups The group that the user belongs to. Security The User Session Manager applet

Table 5-6. The User Session Manager Applet

Heading Description

Workstation IP Address of the workstation the user is logging in from. IPAddress

Time of login The time of login. Time is indicated by: yyyy-mm-dd HH:MM:SS.

Using the User Session Manager applet

To start the User Session Manager applet: • From the main menu bar, select Security > User Session Manager. The User Session Manager window will open and display all users who are currently logged into NavisAccess.

To log out a user: 1 Highlight the user(s) you wish to logout, and right-click. To select multiple users, hold down the [Shift] button and right-click the desired user rows. The Logout menu item will appear. 2 Click Logout, and a window will display asking to confirming your decision. 3 Click [Yes] and the user will be logged out. A logout event will be sent to the Event Viewer as well as the Audit Trails applet.

Other buttons:

In addition to the global toolbar buttons on its left side, the User Session Manager applet has two specialized button functions:

Button Description

[Copy] buttonCopies data in window to the Clipboard.

[Export Data] buttonExports collected data to a comma separated variable file.

NavisAccess DSL Installation and Administration Guide 5-23 Security Audit Trails

Audit Trails

The Audit Trails applet displays actions taken by NavisAccess DSL users. Audit Trails only displays actions which involve changes to the system or to devices: for example, changing the NavisAccess DSL system configuration, or uploading a configuration file to a device. Audit Trails does not report monitoring actions, such as launching DSL Watch or running a real-time performance graph. See the Audit Configuration tab for full details on the kinds of actions that Audit Trails will report.

Audit Trails reports user actions in real time.

5-24 NavisAccess DSL Installation and Administration Guide Security Audit Trails

Audit Trail fields

The bottom pane of the Audit Trails applet gives detailed information about each event received.

The following information is displayed in the Audit Trails window:

Table 5-7. The Audit Trail window heading descriptions

Heading Description

Event Time The date and time the event was generated.

Item Name The name of the item which generated the event.

Event Type A short description of the type of event generated.

Interface The connection to the network (only available for interface alarms).

Event Summary Describes the error in more detail than the Event Type field described above.

Severity The classification of the severity (e.g. critical, informational etc.).

Family The family of the alarm (e.g. IP, AppleTalk etc.).

State The current state of the device after this event (e.g. Operational, Non-operational).

Device Type The brand of device which generated the error.

Address The IP Address of the device which generated the event.

Using the Audit Trails applet

To start the Audit Trails applet, from the main menu bar, select View > Audit Trails. The Audit Trails window will open and events will be reported in real-time based on the Audit Configuration settings.

NavisAccess DSL Installation and Administration Guide 5-25 Security Audit Trails

5-26 NavisAccess DSL Installation and Administration Guide Device Discovery 6

Introduction to Device Discovery ...... 6-2

Automatic Discovery of Network Resources...... 6-4 Manual Discovery ...... 6-4

Generating a Master List ...... 6-5

Discovery using SNMP exploration ...... 6-5

Troubleshooting/Restarting Discovery ...... 6-7

NavisAccess DSL Installation and Administration Guide 6-1 Device Discovery Introduction to Device Discovery

Introduction to Device Discovery

Device Discovery (Discovery) gathers SNMP information about the devices on your network and stores that information in a database that it creates. There are several ways to run Discovery: 1 Automatic: Discovers the entire network at one time using the Explorer applet. The Explorer can be started as needed, or scheduled to run at a preset time. 2 Call Logging: Discovers network resources via call logging packets being received by NavisAccess DSL. In order for Call Logging discovery to occur, Call Logging must be enabled on your Lucent DSL devices, such as Stinger.

Note: If two DSL call-logging packets with different IP addresses of the same device are received, then one device is marked undiscovered in Examiner. 3Manual: Discovers one particular device at a time (using the New Device applet). 4 Master List: Discovers resources based on an input list. The Master List enables you to specify all devices and the interfaces associated with each device.

Note: NavisAccess DSL does not support devices (Stingers) that have been defined with no-auth-no-priv and, therefore, cannot discover them. Authentication and privacy are necessary to maintain security for any packet.

All of these methods gather the following information for each device and store it in a database: • The sysObjId of the device. • The sysName, sysLocation and sysDescr of the device. • The available interfaces for the device. • The discovered protocols of the device. • Device specific information.

The information gathered is used by NavisAccess DSL to populate the Examiner.

After the initial population of the database, use Discovery to update the information in your database. This includes identifying an unknown device or re-establishing contact with an existing device which failed to be discovered during the previous Discovery attempt.

Visual indicators for Discovery

The Examiner window uses visual indicators to denote a device's state in the network. The following table describes each indicator:

6-2 NavisAccess DSL Installation and Administration Guide Device Discovery Introduction to Device Discovery

Table 6-1. Visual indicators for a device

Indicator Icon sysObjID Discovery Description Known Attempted

Question mark No No 1) Never attempted to discover the device. Therefore, its type is not known. 2) The SNMP agent on the device did not respond with valid information.

Device icon with Yes No Attempting to discover the device for the first yellow ’X time.

Question mark No No Attempting to discover the device for the first with yellow ’X time.

Question mark No Yes Attempted initial discovery, but the device failed with red ’X to respond. Device type remains unknown.

Device icon with Yes Yes The last attempt to discover has failed, or Call red ’X Logging has not been received for 30 Minutes.

Device icon Yes Yes The last attempt to discover the device was successful.

NavisAccess DSL Installation and Administration Guide 6-3 Device Discovery Automatic Discovery of Network Resources

Automatic Discovery of Network Resources

NavisAccess DSL automatically discovers all network resources via Call Logging packets it receives. No operator interception is required.

Notes: Call Logging must be enabled on your Lucent DSL devices, i.e., Stinger, APX 8000.

If two DSL packets with different IP addresses of the same device are received, then one device is marked undiscovered in Examiner.

Manual Discovery

Manually adding new devices

Menu Bar: File > New > Device

The New Device feature is used to manually discover devices on your network (that is, discover one device at a time) and populate the database. Once the database is populated, you can use Examiner to view your network.

To manually add a new device 1 Select New > Device from the File menu to open the New Device dialog box. 2 Enter a valid IP Address for the device in the IP Address field. 3 If SNMPv1 supported device: Enter an optional, valid, read-only community string for the SNMPv1-supported device in the SNMPv1 Read Community field. If no community string is specified, the default community string defined in NavisAccess DSL Configuration (Configure > System Options) is used. If SNMPv3 supported device: Enter an optional, valid, read-only user name and password for the SNMPv3-supported device in the SNMPv3 Read User Name and SNMPv3 Read Password fields. If no user name and password is specified, the default user name and password defined in NavisAccess DSL Configuration (Configure > System Options) is used. 4 Enter a Device Display Name. This is an optional name for the device that can be different than the device’s system name (which is set on the device itself). 5 Enter a comment. This can be any information you feel would be useful regarding this device. 6 Click the [OK] button to add the device to the database or click the [Cancel] button to abort. 7 No duplication of IP addresses is allowed throughout the database. If the device IP address is already in the database, an error message appears. As devices are added to the database, they are represented by an icon in Examiner.

6-4 NavisAccess DSL Installation and Administration Guide Device Discovery Discovery via the Master List

Discovery via the Master List

The Master List

Networks are becoming more complex and often change on a daily basis. This causes Administrators to constantly change network configuration. Monitoring these network changes is critical in keeping the network up and running.

NavisAccess DSL provides an easier way for the Network Administrator to monitor changes to the network by allowing the creation of a list that specifies all the devices in the network. Working with discovery, the Master List specifies all of the devices and the WAN Line interface on those devices, as well as their current status.

NavisAccess DSL, upon discovery, reads the Master List and attempts to discover all of the devices on the list. Once discovered, NavisAccess DSL updates the status of the devices and interfaces in the database as specified in the Master List.

Generating a Master List

You can create a Master List by: • Manually creating the list from scratch, or • Using the existing NavisAccess DSL database information and exporting it.

Creating a Master List from scratch for a small network can be quick and efficient, allowing you to customize the exact devices that you want discovered.

However, creating a Master List from scratch for a big network can be a daunting task. For this reason, NavisAccess DSL provides the ML Config Launch Options window which enables you to export the NavisAccess DSL database information to generate a Master List. The list can then be easily updated manually to incorporate and minor changes in the network.

Select Tools>ML Config Launcher to open the ML Config Launch Options window. The ML Configurator can also be run via the command line by typing mlconfig. The ML Configurator offers several Import and Export options via the GUI or command line. For further information, refer to Chapter 8, “The Master List.”

Note: Before running the ML Config Launcher, run NavisAccess DSL Discovery to populate the NavisAccess DSL database with device information.

Discovery using SNMP exploration

Menu Bar: Tools > Explorer

The Explorer is run to automatically discover your network and populate the database. Once the database is populated, you can use Examiner to view your network.

NavisAccess DSL Installation and Administration Guide 6-5 Device Discovery Discovery using SNMP exploration

Explorer can be run manually or at a preset time via an administrator-created schedule. If your network is frequently changing (new devices, moved devices, swapped cards, and so on), you may want to schedule the Explorer to run on a regular basis at off-hours.

Note: Before you run the Explorer, make sure you have properly configured your community strings for SNMP v1 supported devices, or Read-Only/Read-Write user name and password for SNMP v3 supported devices, by adding/editing the settings in the NavisAccess DSL Configuration window.

Running the Explorer 1 Select Explorer from the Tools menu to open the Explorer Configuration dialog box. 2 Configure the settings on the Discover All tab.

Seed Router User-provided “Seed Router” IP Address. The Seed Router is defined as the starting point for discovery of your network. Routing Table Discovery When selected, uses routing tables to discover network devices.

Note: Routers with very large routing tables (over 30,000 entries) may have problems when their routing tables are scanned. By de-selecting this option, NavisAccess DSL will not scan the routing table during the course of its discovery. Node Discovery When selected, NavisAccess DSL finds all system nodes. This option is not recommended for most networks. NT-Station Discovery When selected, NavisAccess DSL discovers all Windows®NT workstations and servers. This option is not recommended for most networks. To be successfully discovered, the Windows®NT machine must have SNMP Service enabled. Save as Default When enabled, causes Explorer to continue Discovery from the point at which it left off. Devices already discovered are not discovered again. This option is enabled by default and is recommended, particularly for large networks. Pass Establishes the number of passes (from 1 to 10) which auto discovery makes. Since many devices go down and up and at times are too busy to respond to SNMP requests, there is the distinct possibility that some may be missed by the Explorer if only one pass is selected. It is therefore recommended that you select at least two passes.

6-6 NavisAccess DSL Installation and Administration Guide Device Discovery Troubleshooting/Restarting Discovery

3 If you want to limit the networks which can be discovered, click the Scoping tab. In large networks, this can provide a more precise picture of a section of the network. If you are not using Scoping, skip to Step 6.

4 Each network that you want to discover requires a seed router. Enter an IP address for each router you wish to use during network discovery. To do this, click the [New] button to open the New Scoping dialog box:

The Network Number field is automatically filled in. Only devices from the added networks will be discovered. 5 Select Scoping Options. See Step 2 above for definitions. 6 When all the desired options are set, the [OK] button begins the auto detection process. Discovered components will populate Examiner. As devices are added to the database, they are represented by an icon in Examiner.

Troubleshooting/Restarting Discovery

Why did Discovery fail?

Discovery may fail for the following reasons: • The user entered an incorrect community string for SNMP v1 supported devices, or Read-Only/Read-Write user name and password for SNMP v3 supported devices (or the default in System Options is not correct for this device). • The DNIS Translation Table entries were not modified to conform to the 10 digit default requirement. • An incorrect or invalid IP address was entered for a device (or for the seed router in explorer). • SNMP MIB II is not enabled on the device. • A filter or firewall blocked communication.

NavisAccess DSL Installation and Administration Guide 6-7 Device Discovery Troubleshooting/Restarting Discovery

• The SNMP timeout setting needs to be increased. See the SNMP Tab under System Options for details. • NavisAccess DSL is not able to reach the device. • Stinger and DSLTNT SNMP v3 users: The security-level in the SNMP profile is not set to auth-nopriv. • Stinger and DSLTNT SNMP v3 users: The security-level in the SNMP v3 target profile (which determines where SNMP v3 traps will be sent) is not set to auth-nopriv. • DSL Max and DSL Terminator SNMP v3 users: When configuring SNMP community strings, the Security Level parameter is not set to auth-nopriv.

When Discovery fails for a device, it must be restarted for the device to be entered into the database properly.

Identifying an unknown device

If Discovery does not recognize a device, the device is considered unknown and the screen displays a question mark in place of an icon for the device.

A yellow question mark indicates that the device was never discovered.

A yellow question mark with a red X indicates that the device failed while it was being discovered.

Please see the Visual Indicators table “Visual indicators for Discovery” on page 6-2 for details on what a device display indicates.

Discovered device is marked undiscovered If two call-logging packets with different IP addresses of the same device are received, then one device is marked undiscovered in Examiner. One device is automatically deleted (when it polls either device address table MIB). The remaining device may be represented by an icon with a yellow “X” over it indicating it is undiscovered. The device must be discovered again to remove the yellow “X”. To avoid this problem in the future, you must set the System IP address in the Stinger so that all call-logging packets have one IP address. To restart Discovery of a device If a device fails to be discovered, you may need to change an IP address, community strings for SNMP v1 supported devices, or Read-Only/Read-Write user name and password for SNMP v3 supported devices. To restart Discovery for an unknown device: 1 Right-click the device icon and select Device Information. Note: You may also update the community strings for SNMP v1 supported devices, or Read-Only/Read-Write user name and password for SNMP v3 supported devices using the Configuration applet available via the Boxmap. 2 Enter the correct IP Address and Community String for SNMP v1 supported devices, or Read User Name and Password for SNMP v3 supported devices, then click [OK]. This automatically updates the device information in the database. 3 Right-click the question mark again and select Discover Device to restart Discovery.

6-8 NavisAccess DSL Installation and Administration Guide Device Discovery Troubleshooting/Restarting Discovery

To restart Discovery of multiple devices Menu Bar: Tools > Discover Devices 1 Select Discover Devices from the Tools menu. The Discover Device(s) dialog box displays:

2 Highlight the devices that you want to discover. The standard [SHIFT] and [CTRL] key selection methods apply. 3 Click [Discover]. The device Discovery process restarts. If the discovery process completes successfully, the device icon and background color are automatically updated.

NavisAccess DSL Installation and Administration Guide 6-9 Device Discovery Troubleshooting/Restarting Discovery

6-10 NavisAccess DSL Installation and Administration Guide Device Discovery Troubleshooting/Restarting Discovery

NavisAccess DSL Installation and Administration Guide 6-11

Database Maintenance 7

Database tools ...... 7-2

Clear Map Flags...... 7-3 Backing-up the database ...... 7-3

Restoring the database ...... 7-5

Generating a fresh database ...... 7-8

Repairing a database ...... 7-10

Moving DB files...... 7-10

Workstation prerequisites for Restore and Move options ...... 7-13

Backing-up the database without DBMaint...... 7-15

The cfgdbcron.ksh utility - Scheduling a database backup ...... 7-15

The db_backup utility ...... 7-17

Manual restoration of the database ...... 7-19

NavisAccess DSL Installation and Administration Guide 7-1 Database Maintenance Database tools

Database tools

NavisAccess DSL provides database tools that can be used for the following: • Database backup - Performs a live backup of the NavisAccess DSL database. • Database restore - Returns the database to a previous state using a backup file. • Database reinitializing - Deletes the current database and replaces it with the original, empty database. • Database repair - Repairs database tables. • Database file moving - Moves NavisAccess DSL databases to a different disc device. After moving a database, new data is written to the database at the new location. Database tools are run from the DBMaint application.

Note: To launch DBMaint, all services must be running. To run the services, use nautil start. For detailed information on the nautil utility, refer to the “The nautil Utility” on page G-1.

DBMaint

DBMaint is installed on the same server as the Scheduling server and is also installed on the workstations. For multiple server farms, however, the Scheduling server and the DBserver are installed on different servers.

Given the above scenario, to allow DBMaint to access the database files to perform its operations, you must mount the NavisAccess database directory, from the primary server, and have the same write privileges.

In order to mount the database directory (in the primary server) to the secondary server, the directory path on both servers must be the same. For example, if the directory path in the primary server is /export/navis/database/..., the directory path in the secondary server must also be /export/navis/database/....

! Caution: If the services are not running, erratic behavior may result, including multiple windu processes. Multiple windu processes will appear in ‘nautil status’ as windu services that have multiple PIDs. To resolve this problem once it has occurred,

1 Run nautil shutdown, 2 Run ps -ef | grep windu and terminate all windu processes that are found, 3 Run nautil start again.

7-2 NavisAccess DSL Installation and Administration Guide Database Maintenance Database tools

Once logged on to DBMaint, you can shut down services as instructed in the procedure steps.

Clear Map Flags

The Clear Map Flags button is provided as an additional support tool. This application is needed only in very rare and specific instances.

This tool should be used only when requested by Lucent technical support.

Backing-up the database

NavisAccess DSL allows you to backup and save multiple copies of the NavisAccess DSL database. Any of these copies can be used to restore the database to a previous state. You may also want to include the backup files in your server backup plans to store them on tape or other backup media.

Note: Please refer to “Workstation prerequisites for Restore and Move options” on page 7-13 for Workstation prerequisites.

To back up the database: 1 At the command line, enter dbmaint and press ENTER. 2 A login screen appears. Enter a NavisAccess DSL user name and password.

Note: Only users with Administrator rights are able to access the DBMaint application. The DBMaint screen appears:

NavisAccess DSL Installation and Administration Guide 7-3 Database Maintenance Database tools

3 Click the Backup DB button. The Backup Database files screen appears.

This screen displays the eight database files that NavisAccess DSL allows you to back up and restore. You may restore these files as many times as you wish. The File name, Size, Creation Date and Path are displayed for each file.

Database Description

Ascend.db A “pointer” file NavisAccess DSL uses to locate information. This database must always reside in the same disc drive as the NavisAccess DSL application files.

The following six database files are used for Adaptive Performance Monitoring. Serviceinterval Servicedata Ingressinterval Ingressdata Egressinterval Egressdata

Event.db Stores system event data

Related Buttons Description

Set Registers the information entered in the Modify file path field.

Close Closes the Restore database files screen.

Backup Starts the Backup process.

Note: With the benefit of backing up certain database files to different disc drives and directories, under different names, you must take care to keep track of where your latest back up file is backed up. 4 Highlight the database that you want to back-up. The path for the database is displayed in the Destination Path field.

7-4 NavisAccess DSL Installation and Administration Guide Database Maintenance Database tools

5 Click Set if you confirm the destination path. If not, modify the path and then click Set. Repeat this for every database you would like backed-up. 6 The Backup Status screen shows the progress of the backup. A message, “Database is successfully backed up!” is displayed when the backup is complete.

Note: If you see a dialog saying, "DBService Not Running. Start DBService and Try again!", this maybe an error, due to the .odbc.ini file emptying. To regenerate this file, enter the following at the command line: dbcli6

If the database name is not known, enter the following at the command line: cat /etc/rc2.d/S97 ascendDBeng

The following will appear: ...../usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/scott_e_output.log -os 102400 -n NavisAccessDB $NAVIS_DIR/database/ascend.....

The database name in the example above is after the -n, or NavisAccessDB

Restoring the database

In a distributed server environment, we recommend that you Restore database files using the main server. If this is not possible and you need to use a Workstation, please read the following before starting.

Important: Workstation Prerequisites: If you are using a Workstation to Restore database files, you must perform certain steps before executing the Restore option. Failure to do so, will generate an error message informing you that no database files could be found. Refer to “Workstation prerequisites for Restore and Move options” on page 7-13.

Note: Before restoring the database, you must exit NavisAccess DSL and shut down some of the NavisAccess DSL services.

To Shut down the services: 1 At the command line enter the nautil dbmaint command. This will stop the appropriate services.

Note: For detailed information of the nautil utility, refer to the “The nautil Utility” on page G-1.

Distributed Environment: – Run nautil dbmaint on the main server – Exit NavisAccess DSL and run nautil dbmaint on the machine from which you are running the dbmaint application. – On all other secondary servers and workstations, Exit NavisAccess DSL and run nautil shutdown. 2 Start the DBMaint application by typing dbmaint at the command line. 3 Shut down the database (on the main server in a distributed environment).

NavisAccess DSL Installation and Administration Guide 7-5 Database Maintenance Database tools

4 At the command line enter the dbstop command. 5 Click the [Restore DB] button. If your database is currently running, you will receive a message asking you to shut down the database.

Note: If you run a new instance of DBMaint, you must run it with dbrestore as user name and password, and then click Restore. The Restore database files screen appears:

This screen displays the eight database files that NavisAccess DSL allows you to restore. You may restore these files as many times as you wish. Ascend.db, must reside in the same disc drive as the NavisAccess DSL application files and, therefore, can only be

7-6 NavisAccess DSL Installation and Administration Guide Database Maintenance Database tools

restored to that directory. All other database files may reside on other disc drives and directories. The File name, Size, Creation Date and Path are displayed for each file.

Database Description

Ascend.db A “pointer” file NavisAccess DSL uses to locate information. This database must always reside in the same disc drive as the NavisAccess DSL application files.

The following six database files are used for Adaptive Performance Monitoring. Serviceinterval Servicedata Ingressinterval Ingressdata Egressinterval Egressdata

Event.db Stores system event data

Related Buttons Description

Set Registers the information entered in the Modify file path field.

Advanced Sets the destination path for a database file used in a distributed server environment.

Close Closes the Restore database files screen.

Restore Starts the Restore process.

Note: With the benefit of restoring certain database files to different disc drives and directories, under different names, you must take care to keep track of where your latest file is restored. 6 Click the browse button to select the Source path for the database file being restored, or rename it if you wish, and click Set.

Distributed server only • Click the Advanced tab if you are working in a distributed server environment. The Advanced tab allows you to specify the Destination Path for the database file. When you click on this tab, a message displays letting you know that choosing this option may have adverse results, such as specifying the wrong destination path for the file. Click OK in response to this message. • The Destination Path field opens up.

NavisAccess DSL Installation and Administration Guide 7-7 Database Maintenance Database tools

• Click Set when you have specified the Destination Path.

7 When done, click Restore. The Restore Status screen will display while the database is being restored. 8 Exit DBMaint. 9 Run nautil shutdown on all the machines in the farm. 10 Run nautil start on all machines in the following order: main server, secondary servers, workstations.

Note: Make sure all services are running in each category (main server, secondary servers, workstations) before moving to the next category.

Generating a fresh database

Important: Any time any modifications are made to the NavisAccess DSL farm (server, or workstation is added, components are redistributed, etc.), the DBGroomer background schedule must run before a DBMaint Reinitialize is performed; otherwise, Reinitialize will fail. If there is any doubt that a DBGroomer schedule has run since the last modifications were made to the farm, run the schedule before launching DBMaint.

NavisAccess DSL allows you to create a fresh, empty database through the Reinitialize Database application

Note: Reinitializing the database will destroy all data in the current database. It is advisable to backup a copy of your current database before starting the reinitialize application.

Refer to “Workstation prerequisites for Restore and Move options” on page 7-13 for details.

7-8 NavisAccess DSL Installation and Administration Guide Database Maintenance Database tools

To reinitialize the database:

Before reinitializing the database, you must exit NavisAccess DSL and shut down some of the NavisAccess DSL services. To Shut down the services: 1 At the command line enter nautil dbmaint and press ENTER. The appropriate services will be stopped.

Note: For detailed information of the nautil utility, refer to the “The nautil Utility” on page G-1.

Distributed environment: –Run nautil dbmaint on the main server. – Exit NavisAccess DSL and run nautil dbmaint on the machine from which you are running the DBMaint application. – On all other secondary servers and workstations, Exit NavisAccess DSL and run nautil shutdown. 2 Start the DBMaint application by typing dbmaint at the command line. 3 A login screen appears. Enter a NavisAccess DSL user name and password.

Note: Only users with Administrator rights will be able to access the DBMaint application.

The DBMaint screen appears:

4 Shut down the database (on main server in distributed environment): At the command line enter dbstop and press Enter. 5 Click the Reinitialize DB button. A warning message appears letting you know that all data in the database will be lost upon re-initialization. Click [OK] to proceed. 6 If your database is running, you will receive a message asking you to shut down the database. A status screen shows the progress of the re-initialization. 7 When finished, exit DBMaint. 8 At the command prompt, on the main server, type: runsql // recover.bin 9 Run nautil shutdown on all machines in the farm.

NavisAccess DSL Installation and Administration Guide 7-9 Database Maintenance Database tools

10 Run nautil start on all machines in the following order: main server, secondary server(s), workstation(s). Make sure all services are running in each category (main server, secondary server, workstation) before moving to the next category.

Repairing a database

NavisAccess DSL allows you to repair your database in the rare and specific instance that a “Corrupt database” message is received.

Note: The Repair Database application should only be used if a “corrupt database” message has been received. It is advisable to contact Lucent’s technical support before proceeding with this operation.

To repair the database: 1 At the command line, enter DBMaint and press ENTER. 2 A login screen appears. Enter a NavisAccess DSL user name and password.

Note: Only users with Administrator rights are able to access the DBMaint application. The DBMaint screen appears:

3 Click the Repair Database button. A warning message appears. Click [OK] to proceed. 4 Upon completion, a “Tables Restored” message will be received.

Moving DB files

NavisAccess DSL allows you to move certain database files to other drives and directories. The files are listed below. Keep in mind, though, that the Ascend.db database must reside on the same disc drive as the NavisAccess DSL application files.

In a distributed server environment, we recommend that you Move database files using the main server. If this is not possible and you need to use a Workstation, please read the following before starting.

Important: Workstation Prerequisites: If you are using a Workstation to Move database files, you must perform certain steps before executing the Move option. Failure to do so, will generate an error message informing you that no database files could be found. Please see, “Workstation prerequisites for Restore and Move options” on page 7-13.

Note: This is not a backup procedure. Once the file(s) is moved, new data is written to the database(s) at its new location.

7-10 NavisAccess DSL Installation and Administration Guide Database Maintenance Database tools

It is strongly advised that you backup your databases before moving a database file to another drive/directory.

To move DB files:

Before moving database files, you must exit NavisAccess DSL and shut down some NavisAccess DSL services as shown in the table below. To Shut down services: 1 At the command line enter nautil dbmaint and press ENTER.

Note: For detailed information of the nautil utility, refer to the “The nautil Utility” on page G-1.

To start DBMaint: 2 At the command line, type dbmaint and press ENTER. 3 A login screen appears. Enter a NavisAccess DSL user name and password.

Note: Only users with Administrator rights will be able to access the DBMaint application. The DBMaint screen appears:

4 Type dbstop to shut down the database (in a distributed environment, type: dbstop from the main server) 5 Click [Move DB files].

Note: If you did not stop your database, and you did not shut down the services, you will receive a message asking you to shut down the database and all NavisAccess DSL Services 6 At command line, type dbstop and press ENTER to stop all services.

NavisAccess DSL Installation and Administration Guide 7-11 Database Maintenance Database tools

7 The Move database files window displays.

This screen displays the eight database files that NavisAccess DSL allows you to move. You may move these files as many times as you wish. Event.db may reside on other disc drives and directories. Ascend.db, however, must reside in the same disc drive as the NavisAccess DSL application files and, therefore, can only reside in that directory. The File name, Size, Creation Date and Path are displayed for each file.

Database Description

Ascend.db A “pointer” file NavisAccess DSL uses to locate information. This database must always reside in the same disc drive as the NavisAccess DSL application files.

The following six database files are used for Adaptive Performance Monitoring. Serviceinterval Servicedata Ingressinterval Ingressdata Egressinterval Egressdata

Event.db Stores system event data

Related Buttons Description

Set Registers the information entered in the Modify file path field.

Advanced Sets the source path for a database file used in a distributed server environment.

Close Closes the Restore database files screen.

Move Starts the Move process.

Note: With the benefit of moving certain database files to different disc drives and directories, under different names, you must take care to keep track of where your latest file is restored.

7-12 NavisAccess DSL Installation and Administration Guide Database Maintenance Database tools

8 Check the box to the left of the database file name to select it. The Destination Path for the database is displayed in the Destination Path field.

To deselect a database, clear the checkbox: 9 Click Set to confirm the destination path. If not, modify the path by clicking on browse (to the right of the file) to view the directory tree and then click Set. Repeat this for every database you would like to move. 10 Select the path for the file and click Set.

Distributed server only • Click the Advanced tab if you are working in a distributed server environment. The Advanced tab allows you to specify the Source Path for the database file. • When you click on this tab, a message displays letting you know that choosing this option may have adverse results, such as specifying the wrong source path for the file. Click OK in response to this message. • The Source Path field opens up. • Click Set when you have specified the Source Path.

11 Click Move.

Note: A message displays, strongly advising you to backup your database before proceeding with the move. 12 Once the database file(s) is moved, the message 'Database successfully moved' displays. 13 Exit DBMaint 14 Start the services again (the database is automatically opened). 15 Run nautil start on main server. When everything is running, 16 Run nautil start on secondary servers. 17 When all are running, run nautil start on workstations

Workstation prerequisites for Restore and Move options

By default, the Restore, Move and Reinitialize and Backup operation will always use a local source and local destination. If you plan to restore files using a remote source or destination, you must first mount/share the directory.

For example, if you run the standard DBMaint Backup on a workstation, you would have the Database files on the workstation. If you launch DBMaint on the workstation, you would have to mount in order to restore. 1 Share the $AutoBahn/database directory by accessing the /etc/dfs/dfstab directory and adding the following on the main server: share/ -o rw /(path of NavisAccess installation directory)/database

NavisAccess DSL Installation and Administration Guide 7-13 Example share -o rw /export/home/navis/database This ensures that the directory is shared upon machine bootup, and that the proper mount daemons are started. 2 Reboot.

Note: This change is permanent. The directory will always be shared unless the user modifies the /etc/dfs/dfstab file and reboots. 3 Check workstations for an $AutoBahn/database subdirectory. If none exists, create one. 4 Mount the $AutoBahn/database directory on the Main Server to the $AutoBahn/database directory on the workstation. To do this, on the workstation type: mount (IP address of the Main Server):/path of NavisAccess directory on the Main Server)/database /(Path of NavisAccess directory on Workstation)/database Note: When Moving database files, the directory path for the Main Server and the Workstation must be the same.

Example mount 107.342.322.11:/export/home/navis/database /export/home/navis/database 5 Now you may proceed and complete all the steps to the Restore or Move options. Important: After the Restore, Move, Reinitialize or Backup operation is complete, you must unmount. If you do not unmount, you will not be able to access files in your own $AutoBahn/database directory. Database Maintenance Backing-up the database without DBMaint

Backing-up the database without DBMaint

The cfgdbcron.ksh utility - Scheduling a database backup

With cfgdbcron.ksh, you can schedule backing up the entire NavisAccess database.You can choose the days and the time to backup the database. For example, you can back-up the database on every Wednesday and Saturday at 9:30 A.M.

Note: You must be a root user to use this utility.

Note: All database files (to be backed-up) must be present in the $AutoBahn/database directory. 1 To back-up the database, from the command line of the NavisAccess Database Server enter:

cfgdbcron.ksh

A welcome screen will display with the following information:

This script Requires Root permissions.

Checking permissions... OK- you have permissions to run this script Note: At this point, if you already have a cron job running, the following message will displays:

The system has a cronjob configured for backing up the NavisAccess database. If you continue the current job will be removed!!! continue [c] or Quit [q] Continue lets you proceed with the new job entry. Quit keeps current job entry. The utility will then display: Enter the directory where the backup copies of the database will be stored, the ‘Default’ is [/Navis_dir/NavisDBBackup]: Where: Navis_dir is the directory where NavisAccess is installed, for example: export/home/navis/NavisDBBackup Note: The utility will create a directory (dbback-DDMMYY) under the directory you specified or under the default directory. 2 Enter the full path of the directory where you want to store the backup copies of the database. If the default is acceptable, press [Enter]. The following message will appear:

Enter the number of concurrent backup copies (1 - 5) to be maintained in [/Navis_dir/NavisDBBackup], the ‘Default’ is [2]:

Where: Navis_dir is the directory where NavisAccess is installed, for example: export/home/navis/NavisDBBackup:

NavisAccess DSL Installation and Administration Guide 7-15 Database Maintenance Backing-up the database without DBMaint

3 Enter the number of backup copies you wish to store, between 1 and 5. The default is 2. For example, if you select 3 copies, for example, when the database is backed up for the fourth time, the earliest copy of the 3 copies will be overwritten by the most recent backup. 4 Enter the days of the week you want the cron job to run.

The days are designated as follows:

0 = Sunday 4 = Thursday 1 = Monday 5 = Friday 2 = Tuesday 6 = Saturday 3 = Wednesday 7 = Daily You can only enter the value of one day at a time. If, for example, you want to backup the database on Wednesday and Saturday, at the prompt, you would enter 3 and press Enter. The prompt would redisplay, at which time you would enter the number 6. 5 When you have entered all the days necessary, press f.

The following message will appear:

Enter the time of the day in HH:MM format (e.g. 16:30) for the backup cronjob to start, the ‘Default’ is [23:59]

Note: The time you select applies to all days selected in Step 4. 6 Enter the time desired and press Enter.

The following message displays: ------CAUTION: You are about to update the crontab entry! Please read the information below carefully. ALL CHANGES WILL BE FINAL AFTER THIS POINT. ------

Summary of options you have selected ------

The directory where backups will be stored: “directory” Number of backup copies to be stored: 3 Day(s) of the week database will be backed up: Wednesday, Saturday Time of day backup will start for each occurrence: 9:30 hrs

The following entry will be added to the crontab: 30 9 * * 3, 6 [-* backup directory.db_backupscript.ksh ....

You can use the unix 'crontab' command to manage your crontab.

Continue [c] or quit [q] ? 7 Select c to continue the backup process. The following message displays: Exiting DB backup cron.

7-16 NavisAccess DSL Installation and Administration Guide Database Maintenance Backing-up the database without DBMaint

Configuration script cleaning of the temporary workspace. Done. Note: If you select q, the cronjob is terminated. The following message displays: Exiting without saving changes.

The db_backup utility

The db_backup utility allows you to backup files the moment you execute the db_backup command.

Note: Unlike cfgdbcron.ksh, you cannot schedule the backup.

The files that must be backed-up are listed below:

Ascend.db

serviceinterval.db

servicedata.db

ingressinterval.db

ingressdata.db

egressinterval.db

egressdata.db

event.db

dslserviceinterval.db db_backup syntax

Command Description db_backup [-?] Displays the usage information db_backup pathfile Backs up NavisAccess Databases as specified in pathfile. where: pathfile contains lines with the following format:

Example

db_backup /opt/navis/bkup.txt

where: bkup.txt contains the following.

Preparing db_backup to run

Before using db_backup, perform Steps 1-3:

NavisAccess DSL Installation and Administration Guide 7-17 Database Maintenance Backing-up the database without DBMaint

1 Create a file using an editor (for example, vi editor) that will contain the information needed for the backup. For example, backuptest 2 If you need to change the number of backup copies, you must enter the value on the first line. The default is 2 copies.

Note: By default db_backup will keep the two most current backup copies. If you increase this number, the number of backup copies will reflect the new default. For example, if you change the value to 3, the number of backup copies kept will be three. 3 Enter the file name, source directory and destination directory of the database files. For example, ascend.db /source directory (of the backup files) /destination directory (of the backup files):

Running db_backup

Once Steps 1-3 are completed, perform Step 4 to run db_backup: 4 Execute the following to perform db_backup: db_backup backuptest

The response will be:

Starting Backup. Please wait.

When db_backup has finished, the backup files will be saved to the following: (based on Step 3 above)

/space/dbback/backup_MMDDYY

Where: backup_MMDDYY is the backup file(s) with the specified month, day and year.

Note: The following applies to db_backup: – If the destination backup directory does not exist, it will be created. However, the parent of backup directory should always exist. – The backed up database files have the same name as the db file. For example, in the above example, backup for ascend.db is /export/home/navis/dbbackupdir/ascend.db. The user cannot change that destination file name. – db_backup generates a text file named backup.dat in the backup directory. This file indicates the source directory for each database file that has been backed up. This can be used for restoring the backed-up database files at a later point.

7-18 NavisAccess DSL Installation and Administration Guide Database Maintenance Manual restoration of the database

Manual restoration of the database

To restore the backed-up database files manually, perform the following steps: 1 Shutdown all NavisAccess services, by executing the following: nautil shutdown Note: If you are running a NavisAccess distributed farm you must shutdown the services on all servers and workstations. 2 From the backup directory, copy all database files (i.e., Ascend.db) to the NavisAccess database directory: /$AutoBahn/database For example, if files are backed-up to:

/space/dbback/backup_MMDDYY Copy all.db files to: /$AutoBahn/database

Note: Before continuing with Step 3, check for the existence of any ascend.log file in the database directory. If the file exists, remove it manually. Once this is done, you may continue with Step 3. Of course, if the file does not exist, you can continue directly with Step 3. 3 Go to the following directory: /$AutoBahn/database and execute the following command: dbsrv6 -f ascend.db The database will be recovered. 4 re-start all NavisAccess services, by executing the following command: nautil start

NavisAccess DSL Installation and Administration Guide 7-19 Database Maintenance Manual restoration of the database

7-20 NavisAccess DSL Installation and Administration Guide The Master List 8

The Master List ...... 8-2

Types of Master Lists...... 8-2 Processing the Master List ...... 8-3

Processing a partial Master List: Device and Interface information ...... 8-9

The Master List Configurator (MLConfig) ...... 8-16

Creating a Master List from scratch...... 8-21

NavisAccess DSL Installation and Administration Guide 8-1 The Master List The Master List

The Master List

Networks are growing faster and becoming more and more complex. Administrators need an easy way to configure these networks. NavisAccess DSL provides an easy-to-use solution: the Master List.

NavisAccess DSL Master List provides an easier way for the Network Administrator to monitor changes to the network, by allowing the creation of a list specifying all the devices, groups, and user information in the network.

Devices and Groups

The Master List Configurator allows the Network Administrator to create a list specifying all the devices in the network.

Additionally, with the Master List you can optionally import and export all groups of devices listed in the Examiner in the Groups folder. Exporting Groups is useful when reinstalling a NavisAccess farm. Along with restoring device information (found in the Master List), groups of devices information, including all subgroups within the group, can be also restored.

Working with discovery, the Master List specifies all of the devices and the interfaces on those devices, as well as their current status. NavisAccess DSL reads the Master List and attempts to discover all of the devices on the list. Once discovered, NavisAccess DSL updates the status of the devices and interfaces in the database as specified in the Master List.

After discovering the devices, NavisAccess DSL updates the status of the devices and interfaces in the NavisAccess DSL database as specified in the Master List. Any discrepancies from the list that are discovered, are flagged and reported as an error in a Log file “MLConfigmmddhhmm.log”.

Users and User Groups

Users and User Groups can be exported to The Master List, enabling you to import this information to another NavisAccess farm, and to more easily modify the security settings in your network. When reinstalling a NavisAccess farm, along with restoring User and User Group information (found in the Master List), user group membership, as well as permissioned feature access and data access to certain User Groups can also be restored.

Once imported, Users and User Groups will appear in the User Manager.

Note: For security purposes the NavisAccess “Administrator” user information will not be exported to the master list file.

Types of Master Lists

You can generate two types of Master lists: • Master List - encompasses the entire network • Partial Master (device and interface information only)- encompasses part of the network

8-2 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

Processing the Master List

Master List format: Devices and Interfaces

Use the following format to define the Devices and Interfaces in the Master List: ; A Comment - A semicolon (;) at the beginning of a line denotes a Comment in the Master List. If a line begins with “;” in the Master List, it is treated as a Comment. . . . D:"MgmtIP1":"DeviceName":"ReadCommunity":"WriteCommunity":"SNMPPort":"Dev iceStatus" I:"MgmtIP1":"Shelf-slot-item":"Circuit Id":"Description":"IntfStatus" (This line is repeated to specify all the interfaces on this device) . . . D:"MgmtIP2":"DeviceName":"ReadCommunity":"WriteCommunity":"SNMPPort":"Dev iceStatus" I:"MgmtIP2":"Shelf-slot-item":"Circuit Id":"Description":"IntfStatus" . . . The following table describes each field.

Table 8-1. Lists the device and interface fields used in a Master List and their descriptions

Field Description

D Denotes a device

I Denotes an interface

"MgmtIP1" The IP Address of the device. DeviceName is the name assigned to this device. [Length - 32 chars]

“ReadCommunity” The Community String used for reading SNMP information from the device.

“WriteCommunity” The Community String used for writing SNMP information in the MIB located on the device. [Length - 32 chars]

“SNMPPort” The port number on the device on which SNMP requests are handled. Note: The SNMPPort field is currently not used in the processing of the Master List.

“DeviceStatus” The current status of the device. The status values are defined in “Circuit status” .

NavisAccess DSL Installation and Administration Guide 8-3 The Master List Processing the Master List

Table 8-1. Lists the device and interface fields used in a Master List and their descriptions

Field Description

“Circuit-Id” The string that uniquely identifies a channeled interface on a device. Circuit-Ids are unique across the entire network that belongs to a carrier.

“Description” Descriptive text associated with the interface. [Length - 64 chars]

“IntfStatus” The current status of the interface. The status values are defined in “Circuit status” .

The first line in this format, starting with the identifier ’D:’, provides information specific to a device. Other lines with the same MgmtIP address, starting with the identifier I:, provide information about various interfaces present on that device. This paired information is repeated for all the devices in the network.

Example

Here is an example of interface entries in the Master List for a device with an IP address of 192.168.30.22:

; Information for device 192.168.30.22

D:"192.168.30.22":"TestDeviceName":"TestReadSecret":"TestWriteSecret":"200":"Operational" I:"192.168.30.22":"1-1-1":"Ckt001001":"Test Circuit 1":"Operational" I:"192.168.30.22":"1-1-2":"Ckt001002":"Test Circuit 2":"Operational" I:"192.168.30.22":"1-2-1":"Ckt002001":"Test Circuit 3":"Out-Of-Service-Test" I:"192.168.30.22":"1-2-1":"Ckt002002":"Test Circuit 4":"Out-Of-Service-Test"

The example shown above provides information about a device and four interfaces/circuits available on that device. The same format is used to provide information about more interfaces on this device or on other devices.

Master List format: Users, User Groups, and User Group Memberships

Users

Use the following format to define the Users in the Master List: ; A Comment - A semicolon (;) at the beginning of a line denotes a Comment in the Master List. If a line begins with “;” in the Master List, it is treated as a Comment. ;------U:"UserNickname":"LoginMask":"BlankPassword":"ActiveLogin":"CurrentLogin":"Pri maryDataGroup":"NumItems":"AuthFlag":"ConcurrentFlag":"PasswordExpiry":"Passwo rdExpiryPrompt":"UserName":"EncryptedPassword":"RootDirectory":"UserDescription" :"TimeStamp"

8-4 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

The following table describes each field.

Table 8-2. Lists the user fields used in a Master List and their descriptions

Field Description

U Denotes a user record.

"UserNickname" Denotes a user for membership into a user group.

"LoginMask" Login level the user is operating on. The login level for an operator is 0. Modifying of this field is not recommended.

"IgnorePassword" This feature is not supported.

"ActiveLogin" Denotes wether a user is active.

"CurrentLogin" This feature is not supported.

"PrimaryDataGroup" The Primary Data Group to which the user belongs.

"NumItems" This feature is not supported.

"AuthFlag" This feature is not supported.

"ConcurrentFlag" Denotes how many concurrent logins the user is allowed.

"PasswordExpiry" This feature is not supported.

"PasswordExpiryPrompt" This feature is not supported.

"UserName" Denotes the user name

"EncryptedPassword" The password, encrypted.

"RootDirectory" This feature is not supported.

"UserDescription" Description of the user. An Administrator can specify a description when creating a new user.

"TimeStamp" Denotes the time the user was created.

The first line in this format, starting with the identifier ’U:’, provides information specific to a user. This information is repeated for all the users in the network.

Example

Here is an example of entries in the Master List for a user with a name of Remote:

; User Remote ;------

U:"User1001":"1":"0":"1":"0":"2":"0":"1":"0":"0":"0":"Remote":"afa0c1c5b4":"Root":"Remo teUser":"2002-03-18 12:00:00.000000"

NavisAccess DSL Installation and Administration Guide 8-5 The Master List Processing the Master List

The example shown provides information about a user. The same format is used to provide information about more users.

User Groups

Use the following format to define the User Groups in the Master List: ; A Comment - A semicolon (;) at the beginning of a line denotes a Comment in the Master List. If a line begins with “;” in the Master List, it is treated as a Comment. ;------UG:"UserGroupNickname":"GroupLoginMask":"PrivateGroup":"GroupName":"GroupD escription" GF:"UserGroupNickname":"FeatureCode":"FeatureFunctionCode" GD:"UserGroupNickname":"DataType":"DataID":"PermissionCode"

The following table describes each field.

Table 8-3. Lists the user group fields used in a Master List and their descriptions

Field Description

UG Denotes a user group

"UserGroupNickname" Denotes a user group.

"GroupLoginMask" Login level the group is operating on.

"PrivateGroup" This feature is not supported.

"GroupName" Name of the group.

"GroupDescription" Description of the group.

GF Denotes a group function

"UserGroupNickname" This feature is not supported.

"FeatureCode" Code denoting specific feature

"FeatureFunctionCode" Code denoting a specific feature function

GD Denotes Group Data

"UserGroupNickname" This feature is not supported.

"DataType" Type of data, e.g., device, group, service, etc. "0" equals everything.

"DataID" Specific data entity, e.g. specified device or group.

"PermissionCode" Permission Code

The first line in this format, starting with the identifier 'UG:', provides information specific to a user group. Other lines that belong to the same User Group, start with the identifier GF: and

8-6 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

GD:. GF provides information about various group features assigned to that user group. GD provides information about various group data assigned to that user group. This information is repeated for all the user groups in the network.

Example

Here is an example of entries in the Master List for a user group with a name of RemoteUsers:

;Usergroup RemoteUsers: ;------UG:"Usergroup1":"2":"0":"RemoteUsers":"Grants Access to all appropriate features and data" GF:"Usergroup1":"0":"0" GD:"Usergroup1":"0":"0":"65407"

The example shown above provides information about a user group and the features and data assigned to that group by the Administrator. The Administrator then assigns users to be members of specific groups. These are denoted in the Master List as Usergroupmembers.

User Group Membership

Use the following format to define the User Group Memberships in the Master List: ; A Comment - A semicolon (;) at the beginning of a line denotes a Comment in the Master List. If a line begins with “;” in the Master List, it is treated as a Comment. ;------UGM:"UserGroupNickname":"UserGroupNickname"

The following table describes each field.

Table 8-4. Lists the user group memeber fields used in a Master List and their descriptions

Field Description

UGM Denotes a user group membership

"UserGroupNickname" Denotes a user for membership into a user group.

"UserGroupNickname" Denotes the nickname for the user group.

Example

Here is an example of entries in the Master List for a user group member with a name of Usergroupmember x:

;Usergroupmember x: ;------UGM:"User1001":"Usergroup1"

The example shown above indicates that user "User1001" (login: "Remote"), belongs to "Usergroup1" (groupname: "RemoteUsers").

The example also provides information about the user group membership of a specific user assigned by the Administrator. This information is repeated for all the user group memberships in the network.

NavisAccess DSL Installation and Administration Guide 8-7 The Master List Processing the Master List

Validation of information in the Master List

Device and Interface information

If some parameters are not specified in the Device or Interface definitions in the Master List, those parameters are ignored during the processing of the Master List.

For example, in the following interface definition:

I:"192.168.30.22":"1-1-2":"Ckt001002"::"Operational"

the Definition field is not specified. In this case, NavisAccess DSL leaves the corresponding field in the NavisAccess DSL database table as it is. If the NavisAccess DSL database already contains some description, that description value is used by NavisAccess DSL.

If quotes are specified without a parameter value, NavisAccess DSL blanks out the corresponding entry from the NavisAccess DSL database table. For example, in the following interface definition:

I:"192.168.30.22":"1-1-2":"Ckt001002":"":"Operational"

the value for Definition field is an empty string. In this case, NavisAccess DSL blanks out the corresponding field in the NavisAccess DSL database table. If all the required fields are not present in an entry, an error message is logged in a Log file.

For device and interface entries that are explicitly defined in the Master List, a default status is assigned if the status is not specified.

User and User Group information

If some parameters are not specified in the User and User Group definitions in the Master List, those parameters will be ignored during the processing of the Master List.

There are four exceptions to this rule: User name, user nickname, group name and group nickname. If any of these items are not included, the record will not be processed.

User name and user nickname

In the example below, the user name is denoted by "Remote". The user nickname is denoted by "User1001":

U:"User1001":"1":"0":"1":"0":"2":"0":"1":"0":"0":"0":"Remote":"afa0c1c5b4":"Root": "RemoteUser":"2002-03-18 12:00:00.000000"

User group name and user group nickname

In the example below, the group name is denoted by "RemoteUsers". The user nickname is denoted by "Usergroup1":

UG:"Usergroup1":"2":"0":"RemoteUsers":"Grants Access to all appropriate features and data"

8-8 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

Processing a partial Master List: Device and Interface information

A partial Master List means that the Master List only contains information about changes made to the network. The changes could mean: • addition of new devices • removal of some of the existing devices • change in the status of some devices or circuits • a combination of these

Partial Master List processing is implemented by using a command line argument.

Rules for processing the Master List: Device and Interface information

NavisAccess DSL provides support for processing device and interface information for both partial and complete Master Lists. NavisAccess DSL defines a set of rules to process the Master List. These rules are summarized below.

The first two columns in the table below indicate the status of the device and the interface on which the call is processed. The third column indicates whether the called DNIS number has been processed by NavisAccess DSL earlier. If the DNIS has been processed, there is a record for the DNIS in the NavisAccess DSL database.

Table 8-5. Summary of rules to process the Master List

Device Status Interface Status DNIS Actions

Operational Operational Present Hunt Group and Services are created, if required. Stats are reported in the Plant calculations.

Operational Operational Not Present Same as above

Operational Unknown Present Device is discovered again. Hunt Group and Services are created, if required. Stats are reported. A CRITICAL event is generated to report that “A call is processed on an interface that is not in Operational state. Current interface state = ”.

Unknown Unknown Present Hunt Group and Services are created, if required. Stats are reported. Out-of-Service Out-of-Service A CRITICAL event is generated to report that “A call is Out-of-Service- Out-of-Service- processed on a device that is not in Operational state. Test Test Current device state = ” A CRITICAL event is generated to report that “A call is processed on an interface that is not in Operational state. Current interface state = ”.

NavisAccess DSL Installation and Administration Guide 8-9 The Master List Processing the Master List

Table 8-5. Summary of rules to process the Master List (continued)

Device Status Interface Status DNIS Actions

Operational Unknown Not Present The call is ignored.

Unknown Unknown Hunt Group and Services are not created, and Stats are not reported for such calls. Out-of-Service Out-of-Service

Out-of-Service- Out-of-Service- Test Test

Rules for processing the Master List: User and User Group information

The data that is imported from a Master List of users and/or user groups into a destination system will vary, depending on duplicate users and/or user groups which may exist both on the source system (the system you exported from), and the destination system (the system you are importing to).

Importing terminology

The following terminology is used when defining what data types will be imported from the source system to the destination system:

Table 8-6. ML Config user/user groups importing terminology

Data Type Description

Old User A user who exists in the destination system, but not in the source system.

Old User Group A user group that exists in the destination system, but not in the source system.

New User A user who exists in the source system, but not in the destination system.

New User Group A user group that exists in the source system but not in the destination system.

Duplicate User A user who exists in the destination system as well as in the source system.

Duplicate Group A user group that exists in the destination system as well as in the source system.

8-10 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

Importing options

There are three ways to import Master List data into the destination system:

Abort

Only data that is not duplicated will be imported to the destination system.

If any duplicate users and/or user groups, as well as feature function access and data access belonging to the user groups are found between the source system and the destination system when importing the Master List, the import operation will be aborted. Records pertaining to the destination system will be kept.

Override

In general, the override feature will override data in the destination system with what is present in the source system.

If any duplicate users and/or user groups, as well as feature function access and data access belonging to the user groups are found between the source system and the destination system when importing the Master List, the user group membership records are then considered on a record-by-record basis. The table below defines the actions NavisAccess will take, depending on the record type:

Refer to “Importing terminology” on page 8-10 for details on the terms used in the table(s) below.

User Group Membership

Table 8-7. Actions performed on user group membership when overriding

User User Group Result

Old Old Keep the records in the destination system. If a user belonged to a group before importing, he will so after importing.

Old Duplicate Keep the records in the destination system. If a user belonged to a group before importing, he will so after importing.

New New Insert the new record into the destination system. If user belongs to a group in the source system, he will belong to the group in destination system after importing.

New Duplicate Insert the new record into the destination system. If user belongs to a group in the source system, he will belong to the group in destination system after importing.

Note: If the -nonewadmin flag is set when performing the command-line operation, the Administrator group will be kept in the destination system. All other groups will be inserted to the destination from the source system.

NavisAccess DSL Installation and Administration Guide 8-11 The Master List Processing the Master List

Table 8-7. Actions performed on user group membership when overriding

User User Group Result

Duplicate Old Keep the old records in the destination system.

Duplicate New Keep the old user and insert the new user group into the destination system. If user x belonged to a user group in the source system before importing, user x will belong to that same user group in the destination system.

Duplicate Duplicate Deletes the old record, inserts the new record into the destination system. If user x belonged to the duplicate user group in the source system before importing, user x will belong to that same duplicate user group in the destination system.

Feature Function Permissions

Table 8-8. Actions performed on feature function permissions when overriding

Group Result

Old Keep the records in the destination system. If group x had permission for a function before importing, group x will have permission for that function after importing.

Duplicate Deletes the old records, and inserts the new records into the destination system. Group x, in the destination system, will only have permissions for those functions set in the source system.

New Insert the new record into the destination system. If group x has permission for a function in the source system, group x will have permission for that function, after importing, in the destination system.

Data Access Permissions

Table 8-9. Actions performed on data access permissions when overriding

Group Result

Old Keep the records in the destination system. If group x had permission for a set of data before importing, group x will have permission for the data after importing.

Duplicate If this group had ManageAll permission in the source system, then importing will Delete Old records and the group will have ManageAll permissions after importing.

If this group did not have ManageAll permission in the source system, importing will have no effect on data access permissions of the group in the destination system.

8-12 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

Table 8-9. Actions performed on data access permissions when overriding

Group Result

New Insert the new record into the destination system. If group x has ManageAll permission for data in source system, group x will have ManageAll permission for data, after importing, in the destination system.

Retain

In general, the retain feature will retain data in the destination system, rather than replacing it with the data from the source system.

If any duplicate users and/or user groups, as well as feature function access and data access belonging to the user groups are found between the source system and the destination system when importing the Master List, the user group membership records are then considered on a record-by-record basis. The table below defines the actions NavisAccess will take, depending on the record type:

Refer to the “Importing terminology” on page 8-10 for details on the terms used in the table(s) below.

User Group Membership

Table 8-10. Actions performed on user group membership when retaining

User User Group Result

Old Old Keep the records in the destination system. If user x belongs to a group in the source system, he will belong to that group in destination system (after importing.)

Old Duplicate Keep the records in the destination system. If user x belongs to a group in the source system, he will belong to that group in destination system (after importing.)

New New Insert the new record into the destination system. If user x belongs to a group in the source system, he will belong to that group in destination system (after importing.)

New Duplicate Insert the new record into the destination system. If user x belongs to a group in the source system, he will belong to that group in destination system (after importing.)

Duplicate Old Keep the records in the destination system. If user x belonged to a group in the source system before importing, he will belong to that group in the destination system (after importing.)

Duplicate New Keep the old user and insert the new user group into the destination system. If user x belonged to a group in the source system, he will not belong to the new group in the destination system (after importing.)

NavisAccess DSL Installation and Administration Guide 8-13 The Master List Processing the Master List

Table 8-10. Actions performed on user group membership when retaining

User User Group Result

Duplicate Duplicate Deletes then old record, inserts the new record into the destination system. If user x belonged to a group in the source system, he will belong to the same group in the destination system (after importing.)

Feature Function Permissions

Table 8-11. Actions performed on feature function permissions when retaining

Feature Result

Old Keep the records in the destination system. If group x had permission for a function before importing, group x will have permission for that function after importing.

Duplicate Keep the records in the destination system. If group x had permission for a function before importing, group x will have permission for that function after importing. However, group x will not have permissions for any new functions.

Data Access Permissions

Table 8-12. Actions performed on data access permissions when retaining

Group Result

Old Keep the records in the destination system. If group x had permission for a set of data before importing, group x will have permission for the data after importing.

Duplicate Keep the records in the destination system. If group x had permission for a set of data before importing, group x will have permission for the data after importing.

New Insert the new records into the destination system. If group x has ManageAll permission for data in source system, group x will have ManageAll permission for data, after importing, in the destination system. If ManageAll permission is not set, data access permissions are not imported to the new group.

8-14 NavisAccess DSL Installation and Administration Guide The Master List Processing the Master List

Logging the progress Information

A log file, named “MLConfigmmddhhmm.log” is generated by MLConfig to provide information about the operations performed by it. Every time MLConfig is scheduled, it creates a new Log file by putting the 'Month-Day-Hour-Minute' information in the Log file name. For example, if MLConfig is scheduled to run on May 24 at 4:00 pm, the Log file name is 'MLConfig05241600.log'.

MLConfig logs different types of information. If MLConfig initiates discovery of any new devices that did not exist in the NavisAccess DSL database earlier, it logs messages indicating that “The device discovery is initiated”, and when the devices get discovered, it logs messages indicating the same along with their IP addresses. MLConfig also logs all the Warning and Exception conditions for which it also generate events. For example, if some devices are not discovered, MLConfig logs messages indicating these conditions in addition to generating events.

Circuit status

The following status values are defined for the channeled interfaces:

Table 8-13.Status values for the channeled interface

Circuit Status Description

“Operational” A circuit is in active operational mode, and is providing normal service to the customer. The circuit is available for handling customer calls in this mode.

“Out-of-Service” A circuit is configured but, for some reason has been taken Out-of-active-Service. The circuit is not providing any service to the customer in this state, and does not handle any calls.

“Out-of-Service-Test” A circuit has been taken Out-Of-Service to perform tests.

“Out-of-Service-Test-Loopback” A circuit has been taken Out-Of-Service-Test to perform the loopback tests.

Unknown The circuit status is not in one of the defined states.

A circuit that is taken out of service for maintenance purposes, may be assumed to be “Out-of-Service for Test”. Unless different actions are required for circuits in the Maintenance state, the Maintenance state may be treated the same as the "Out-of-Service-Test" state.

Default Status

While processing a Complete Master List, if the status value is not specified for a device or interface, a default status of “Unknown” is assigned to it. On the other hand, if a Partial Master

NavisAccess DSL Installation and Administration Guide 8-15 List is being processed, the status value is left unchanged for devices or interfaces not referenced in the Master List.

Note: In the NavisAccess DSL database, the Interface Table will be enhanced to include the Status field to indicate the status of the interface/circuit.

Similarly, the Device Table will be enhanced to include the Status field. The status for a Device can also have one of the values as described above for circuits.

Actions to be taken when circuit status changes

Whenever the circuit status changes, the following actions are taken: • Remove the circuit/interface from the Hunt Group of which it is a part. • Change the status in the interface table. • Log the change indicating old and new status values.

Device and interface status relationship

While processing the Master List, if it is found that the status of a device has changed, the status of its interfaces may also be affected. NavisAccess DSL will automatically modify the status of affected interfaces based on the rules described in the table Table 8-14.

Table 8-14. Correlation between device status changes and interface status changes

If device status changes Interfaces status changes to From To

Operational, or Out-of-Service-Test, or Out-of-Service Status of all the interfaces is changed to Unknown “Out-of-Service”.

Operational, or Out-of-Service, or Unknown Out-of-Service-Test Status of all the interfaces is changed to “Out-of-Service-Test”.

Operational, or Out-of-Service, or Unknown Status of all the interfaces is changed to Out-of-Service-Test “Unknown”.

Out-of-Service, or Out-of-Service-Test, or Operational No change. Interfaces status must be Unknown explicitly modified using the Master List.

The Master List Configurator (MLConfig)

You can create a Master List by: 1 Manually creating a list from scratch 2 Using the existing NavisAccess DSL database information and exporting it

Creating a Master List from scratch, for a small network can be quick and efficient, allowing you to customize the exact information that you want. However, creating a Master List from scratch for a big network can be a daunting task. For this reason, you can use MLConfig. The Master List The Master List Configurator (MLConfig)

The Master List Configurator application provides the functionality of synchronizing the information in the NavisAccess DSL database with that in the Master List. MLConfig enables you to export the NavisAccess DSL database information to generate a Master List. This list can then be easily updated manually to incorporate any minor changes in the network.

MLConfig can be accessed from the: • command line • Tools menu (Tools> MLConfig Launcher)

Note: To use MLConfig to generate a list of devices and interfaces, one should let NavisAccess DSL initially discover the network so that the NavisAccess DSL database gets populated with information about the devices that are available on the network. Once the NavisAccess DSL database is populated with the network information, MLConfig can be run to generate the device/interface section of the Master List.

MLConfig Launch Options provide the ability of synchronizing the information in the NavisAccess DSL database with that in the Master List. It allows you to export device/ interface information, groups of devices, and user/user group information from the NavisAccess DSL database to generate the Master List.

Starting MLConfig from the command line

You can invoke the MLConfig application from the command line using parameters. These parameters are described in the next section.

The default option is -import, so when importing the Master List into the NavisAccess DSL database, it is not necessary to enter -import.

Start MLConfig from the command line as follows: mlconfig [ . . .]

To import the Master List: mlconfig -import master_list_file_name where master_list_file_name is the input Master List that is processed by MLConfig.

To export the information from NavisAccess DSL database to generate the Master List: mlconfig -export master_list_file_name where master_list_file_name is the output Master List that is processed by MLConfig.

Importing the Master List • At the UNIX command line, enter: mlconfig -import [options] master_list_file_name

NavisAccess DSL Installation and Administration Guide 8-17 The Master List The Master List Configurator (MLConfig)

MLConfig Command Line Options - Import

The following options can be specified when MLConfig application is used to import the Master List from the command line.

Table 8-15.MLConfig Command Line Options - Import

Option Description

-nodiscovery If this option is specified, MLConfig will not try to discover any new devices that are specified in the Master List. Default: New devices are discovered.

-devstatus "" This option can be used to specify the default status for the devices for which no status value is specified in the Master List. – Unknown – The device status is not in one of the defined states. – Operational – The device is in active operational mode, and is providing normal service to the customer. The device is available for handling customer calls in this mode. – Out-Of-Service – The device is configured but for some reason has been taken out of service. The device is not providing any service to the customer in this state, and does not handle any calls. – Out-Of-Service-Test – The device has been taken out of service to perform some tests. – Out-Of-Service-Test-Loopback – The device has been taken out of service to perform loopback tests.

Note: If the status of the device has changed, the status of the interface may be effected as well. Default: The default status is “Unknown” if no status value is specified for a device.

-intfstatus "" This option can be used to specify the default status for the circuits for which no status value is specified in the Master List. – Unknown – The interface status is not in one of the defined states. – Operational – An interface is in active operational mode, and is providing normal service to the customer. The interface is available for handling customer calls in this mode. – Out-Of-Service – An interface is configured but for some reason has been taken out of service. The interface is not providing any service to the customer in this state, and does not handle any calls. – Out-Of-Service-Test - An interface has been taken out of service to perform some tests. – Out-Of-Service-Test-Loopback – The interface has been taken out of service to perform loopback tests. Default: The default status is “Unknown” if no status value is specified for a circuit.

8-18 NavisAccess DSL Installation and Administration Guide The Master List The Master List Configurator (MLConfig)

Table 8-15.MLConfig Command Line Options - Import (continued)

Option Description

-deldevinfo If this option is specified, MLConfig will delete Device and Interface records from the database for the devices that were discovered earlier, but no longer appear in the Master List. Default: Device/Interface records are not deleted.

-partiallist This option is specifies that the Master List is a Partial Master List. If both -partiallist and -deldevinfo are specified when invoking MLConfig, the -deldevinfo option is ignored. Default: By default, Master List is treated as a Complete Master List unless -partiallist is specified.

-timeout This option can be used to specify the timeout value that MLConfig uses to wait for a device to be discovered. Default: 30 minutes

-nolog If this option is specified, Log file is not created by MLConfig, i.e., no logging will be done. Default: Log file is created.

-log This option can be used to specify a Log file name in which MLConfig puts the log messages. Default: “MLConfigmmddhhmm.log” file is created by default.

-nonewadmin This option specifies that no new Administrator users be created when importing the Master List into the Destination system. Default: Administrator users can be created unless -nonewadmin is specified.

-user If this option is specified, user information will be imported to the Master List.

-password If this option is specified, user password information will be imported to the Master List.

-Help or -? or -h If this options is selected it will display information about the usage of mlconfig.

Exporting the NavisAccess DSL database

To export the NavisAccess DSL database into a Master List, at the UNIX command line: 1 Enter mlconfig -export test2 (test2 is the name of the Master file in this example.). The database is exported and is named test2. The file (test2) resides in the NavisAccess directory. 2 The Master List is automatically created. You can access the Master List file using any text editor. You can then modify any of the devices or interfaces and their parameters. 3 Enter: mlconfig test2 to import the Master List file into NavisAccess DSL database. Since import is the default, you do not have to enter it as part of the command.

NavisAccess DSL Installation and Administration Guide 8-19 The Master List The Master List Configurator (MLConfig)

Viewing the status of a device or interface

To view the status of the device or interface access the Wan Line Table. To do this: 4 Right-click on a device in the Examiner> Access Application>Wan Line Table.

Note: To save time when creating a Master List from scratch, you can specify the device without specifying the interfaces since all interfaces associated with the device will be discovered automatically. If specific interfaces are missing from the Master List which are present in the database, it will force a discovery of the device associated with the interface.

MLConfig Command Line Options - Export

Entering mlconfig -export test2 (test2 is the name of the Master file in this example) at the command line exports all device/interface and user/user group information by default.

If you wish to export only specific aspects to the Master List, the export options shown below will allow you to do just that. For example, if you wanted MLConfig to only export device information to the Master List, you would enter the following at the command line:

mlconfig -export test2 -devices

The following options can be specified when MLConfig application is used to export the Master List from the command line.

Table 8-16.MLConfig Command Line Options - Export

Option Description

-devices If this option is specified, MLConfig will export device information to the Master List. Default: Device information is exported to the Master List.

-dnistranslated The option is not supported in NavisAccess DSL.

-dnisshort The option is not supported in NavisAccess DSL.

-dnisall The option is not supported in NavisAccess DSL.

-group This option is specifies that MLConfig will export device group information to the Master List. Default: Device group information is exported to the Master List.

-users If this option is specified, MLConfig will export user information to the Master List. Default: User information is exported to the Master List.

-usergroups If this option is specified, MLConfig will export user group information to the Master List. Default: User group information is exported to the Master List.

-Help or -? or -h If this options is selected it will display information about the usage of mlconfig.

8-20 NavisAccess DSL Installation and Administration Guide The Master List Creating a Master List from scratch

Creating a Master List from scratch 1 Enter the device information using any text editor In the example below groups of devices are included.. For example: ;Device “192.168.30.22” D:"192.168.30.22":"TestDeviceName":"TestReadSecret":"TestWriteSecret":"200":"Oper ational" I:"192.168.30.22":"1-1-1":"Ckt001001":"Test Circuit 1":"Operational" I:"192.168.30.22":"1-1-2":"Ckt001002":"Test Circuit 2":"Operational" I:"192.168.30.22":"1-2-1":"Ckt002001":"Test Circuit 3":"Out-Of-Service-Test" I:"192.168.30.22":"1-2-1":"Ckt002002":"Test Circuit 4":"Out-Of-Service-Test" ;Device “46.1.1.1” D:”46.1.1.1”:”NMD-MAX1800”: “read” :”write”:”161”: “Unknown” I:”46.1.1.1”:”1-4-1”:” ”:” “ I:”46.1.1.1”:”1-1-8”:” ”:” “ I:”46.1.1.1”:”1-1-7”:” ”:” “

;Group def:

G:"Group1003":"def":"":"0":"0":"0":"0":"0" M:"Group1003":"192.168.30.22":"-1":"D"

;Group abc:

G:"Group1002":"abc":"":"0":"0":"0":"0":"0" M:"Group1002":"46.1.1.1":"-1":"D" 2 Save the file when you have entered all the devices and interfaces you want discovered. 3 Run mlconfig test1 (test1 is the name of the Master List in this example). NavisAccess DSL automatically reads the Master List and starts to discover the devices on the Master List by comparing it to its database. NavisAccess DSL Examiner displays each device (in the Devices folder) or groups of devices (in the Groups folder) as they are discovered.

Viewing the status of a device or interface

To view the status of the device or interface access the Wan Line Table. To do this: 4 Right-click on a device in the Examiner> Access Application>Wan Line Table.

NavisAccess DSL Installation and Administration Guide 8-21 The Master List Generating the Master List using the MLConfig Launch Options Dialog

Generating the Master List using the MLConfig Launch Options Dialog

To display the ML Config Launch Options dialog, from the NavisAccess DSL menu bar, select: Tools > MLConfig Launcher.

The MLConfig Launch Options screen displays.

Exporting Devices 1 From the NavisAccess DSL menu bar, select: Tools > MLConfig Launcher. 2 Select Export To Master List. 3 Select the Master List file to export device information to in the Export to MasterList field. You may use the Browser button to find the Master List file. 4 Select Devices. 5 Click [Launch].

Example:

;Device "100.110.58.18":

D:"100.110.58.18":"Rosebud":"public":"write":"161":"Operational"

I:"100.110.58.18":"1-9-32774":"":"":"Operational" I:"100.110.58.18":"1-9-32769":"":"":"Operational" I:"100.110.58.18":"1-9-32773":"":"":"Operational" I;Device "101.115.59.19":

D:"101.115.59.19":"Small ISP":"public":"write":"161":"Operational" I:"101.115.59.19":"1-4-48":"":"":"Operational" I:"101.115.59.19":"1-4-47":"":"":"Operational"

8-22 NavisAccess DSL Installation and Administration Guide The Master List Generating the Master List using the MLConfig Launch Options Dialog

I:"101.115.59.19":"1-4-46":"":"":"Operational" I:"101.115.59.19":"1-4-43":"":"":"Operational"

Importing Devices 1 In the Import Options section of the MLConfig Launch Options dialog box, enter the name of the Master List file, the log file name, and any other information you require. 2 Once all fields are filled out as desired, click [Launch].

Note: Table below describes each field.

Exporting Groups 1 From the NavisAccess DSL menu bar, select: Tools > MLConfig Launcher. 2 Select Export To Master List. 3 Enter the name of the Master List file to export device and group information to in the Export to MasterList field. You may use the Browser button to find the Master List file. 4 Select Groups. 5 Click [Launch].

The created Master List file containing the group(s) will reside in the NavisAccess directory. The group(s) information is displayed at the bottom of the Master List file.

Example:

;Device "100.110.58.18":

D:"100.110.58.18":"Rosebud":"public":"write":"161":"Operational"

I:"100.110.58.18":"1-9-32774":"":"":"Operational" I:"100.110.58.18":"1-9-32769":"":"":"Operational" I:"100.110.58.18":"1-9-32773":"":"":"Operational" I;Device "101.115.59.19":

D:"101.115.59.19":"Small ISP":"public":"write":"161":"Operational" I:"101.115.59.19":"1-4-48":"":"":"Operational" I:"101.115.59.19":"1-4-47":"":"":"Operational" I:"101.115.59.19":"1-4-46":"":"":"Operational" I:"101.115.59.19":"1-4-43":"":"":"Operational"

;Group def:

G:"Group1003":"def":"":"0":"0":"0":"0":"0" M:"Group1003":"100.110.58.18":"-1":"D"

;Group abc:

G:"Group1002":"abc":"":"0":"0":"0":"0":"0" M:"Group1002":"101.115.59.19":"-1":"D"

NavisAccess DSL Installation and Administration Guide 8-23 The Master List Generating the Master List using the MLConfig Launch Options Dialog

Importing a Group 1 In the Imports Options section of the MLConfig Launch Options dialog box, enter the name of the Master List file that you want to import. 2 Also enter any additional information that you require.

Note: Table 8-17 on page 8-26 describes each field. 3 Once all fields are filled out as desired, click [Launch]

The imported Group(s) will display in Examiner in the Groups folder.

Exporting Users 1 From the NavisAccess DSL menu bar, select: Tools > MLConfig Launcher. 2 Select Export To Master List. 3 Enter the name of the Master List file to export user information to, in the Export to MasterList field. You may use the Browser button to find the Master List file. 4 Select User information 5 Select Users only. 6 Click [Launch].

The created Master List file containing the users(s) will reside in the NavisAccess directory. The user(s) information is displayed at the bottom of the Master List file.

Example:

;User Remote:

;------

U:"User1001":"1":"0":"1":"0":"2":"0":"1":"0":"0":"0":"Remote":"afa0c1c5b4":"Root":"R emote User":"2002-03-18 12:00:00.000000"

Importing Users 1 In the Imports Options section of the MLConfig Launch Options dialog box, enter the name of the Master List file that you want to import. 2 Also enter any additional information that you require.

Note: Table 8-17 on page 8-26 describes each field. 3 Once all fields are filled out as desired, click [Launch]

The imported User(s) will display in User Manager.

Exporting User Groups 1 From the NavisAccess DSL menu bar, select: Tools > MLConfig Launcher. 2 Select Export To Master List.

8-24 NavisAccess DSL Installation and Administration Guide The Master List Generating the Master List using the MLConfig Launch Options Dialog

3 Enter the name of the Master List file to export user group information to in the Export to MasterList field. You may use the Browser button to find the Master List file. 4 Select User information 5 Select Usergroups only. 6 Click [Launch].

The created Master List file containing the user group(s) will reside in the NavisAccess directory. The user group(s) information is displayed at the bottom of the Master List file.

Example:

;Usergroup RemoteUsers:

;------

UG:"Usergroup1":"2":"0":"RemoteUsers":"Grants Access to all appropriate features and data"

GF:"Usergroup1":"0":"0"

GD:"Usergroup1":"0":"0":"65407"

Importing User Groups 1 In the Imports Options section of the MLConfig Launch Options dialog box, enter the name of the Master List file that you want to import. 2 Also enter any additional information that you require.

Note: Table 8-17 on page 8-26 describes each field. 3 Once all fields are filled out as desired, click [Launch]

The imported User Groups will display in User Manager.

Exporting Users and User Groups 1 From the NavisAccess DSL menu bar, select: Tools > MLConfig Launcher. 2 Select Export To Master List. 3 Enter the name of the Master List file to export user and user group information to in the Export to MasterList field. You may use the Browser button to find the Master List file. 4 Select User information 5 Select Users and Usergroups. 6 Click [Launch].

The created Master List file containing the user(s) and user group(s) will reside in the NavisAccess directory. The user(s) and user group(s) information is displayed at the bottom of the Master List file.

NavisAccess DSL Installation and Administration Guide 8-25 The Master List Generating the Master List using the MLConfig Launch Options Dialog

Example:

;User Remote:

;------

U:"User1001":"1":"0":"1":"0":"2":"0":"1":"0":"0":"0":"Remote":"afa0c1c5b4":"Root":"R emote User":"2002-03-18 12:00:00.000000"

. . .

;Usergroup RemoteUsers:

;------

UG:"Usergroup1":"2":"0":"RemoteUsers":"Grants Access to all appropriate features and data"

GF:"Usergroup1":"0":"0"

GD:"Usergroup1":"0":"0":"65407"

The imported User(s) and User Group(s) will display in User Manager.

Export and Import Options

Table 8-17. Master List export and import options field descriptions

Field Description

Export Options

Export to Master List Select this field to export all devices.

Export MasterList File Name Enter the name of the MasterList that you would like to export the devices to.

Devices Select this field to export devices with the MasterList.

Groups Select this field to export group(s) of devices with the MasterList.

Note: The group can only contain devices and sub-groups. If services are included in the group or in a subgroup, the group or subgroup will be ignored and will not be exported.

User Information Select to export user information.

Users Only Select to export only user data to the Master List.

User Groups only Select, to export only user group data to the Master List.

Users and User Groups Selected, to export both user and user group data to the Master List.

Import Options

8-26 NavisAccess DSL Installation and Administration Guide The Master List Generating the Master List using the MLConfig Launch Options Dialog

Table 8-17. Master List export and import options field descriptions (continued)

Field Description

Import Master List File Name Select the Master List file to import device and group information from. For further information on the Import process, refer to Importing the Master List.

Log File Name Specify a Log file in which MLConfig places log messages. The Default MLConfigmmddhhmm.log file is created by NavisAccess DSL. For further information about the logging process, refer to Logging process information.

No Log Check to have MLConfig not create a log file. If this is selected, no logging will be done.

Default Device Status Specify the default status for the devices for which no status value is specified in the Master List. If no status is specified for a device, the default is Unknown. Unknown The device status is not in one of the defined states. Operational The device is in active operational mode, and is providing normal service to the customer. The device is available for handling customer calls in this mode.

Out-Of-Service The device is configured but, for some reason has been taken out of service. The device is not providing any service to the customer in this state, and does not handle any calls.

Out-Of-Service-Test The device has been taken out of service to perform some tests

Out-Of-Service-Test-Loopback The device has been taken out of service to perform loopback tests.

Note: If the status of the device has changed, the status of the interface may be effected as well. For further information, refer to Device and Interface status relationship.

NavisAccess DSL Installation and Administration Guide 8-27 The Master List Generating the Master List using the MLConfig Launch Options Dialog

Table 8-17. Master List export and import options field descriptions (continued)

Field Description

Default Interface Status Specify default status for the interfaces for which no status value is specified in the Master List. If no status is specified for an interface, the default is Unknown.

Unknown The interface status is not in one of the defined states.

Operational An interface is in active operational mode and is providing normal service to the customer. The interface is available for handling customer calls in this mode.

Out-Of-Service An interface is configured but, for some reason has been taken out of service. The interface is not providing any service to the customer in this state, and does not handle any calls.

Out-Of-Service-Test An interface has been taken out of service to perform some tests. Out-Of-Service-Test-Loopback The interface has been taken out of service to perform loopback tests.

Time Out in Minutes Specify the amount of time MLConfig should wait for a device to be discovered before timing out.

No Discovery Check No Discovery to have MLConfig not discover any new devices that are specified in the Master List.

Delete Device Info Click to have MLConfig delete device and interface records from the database for the devices that were discovered earlier, but no longer appear in the Master List.

Partial List Partial Master List means that the Master List will not provide information about the entire network, but will contain only information on changes made to the network. The changes could be: addition of new devices, removal of some existing devices, or a change in the status of some devices or interfaces, or any combination thereof.

Abort Only new data (users, user groups, and feature function access and data access belonging to those user groups) will be imported to the destination system.

If any duplicate users and/or user groups are found between the source system and the destination system when importing the Master List, the import operation will be aborted. Records pertaining to the destination system will be kept.

Override Select to override data in the destination system with what is present in the source system. For a complete list of user groups, feature access, and data access, refer to “Rules for processing the Master List: User and User Group information” on page 8-10.

8-28 NavisAccess DSL Installation and Administration Guide The Master List Generating the Master List using the MLConfig Launch Options Dialog

Table 8-17. Master List export and import options field descriptions (continued)

Field Description

Retain Select to retain data in the destination system, rather than replacing it with the data from the source system. For a complete list of user groups, feature access, and data access, refer to “Rules for processing the Master List: User and User Group information” on page 8-10.

NavisAccess DSL Installation and Administration Guide 8-29 The Master List Generating the Master List using the MLConfig Launch Options Dialog

8-30 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) 9

Introduction ...... 9-2

What are device licences? ...... 9-2 Launching the NDLM ...... 9-4

Setting the Advanced options ...... 9-5

Generating a Device License request file ...... 9-6

Processing the response file ...... 9-9

Reprocessing a file ...... 9-14

Log file samples...... 9-15

NDLM error messages...... 9-18

NavisAccess DSL Installation and Administration Guide 9-1 Navis Device License Manager (NDLM) Introduction

Introduction

The Navis Device License Manager (NDLM) allows license and software options updates to any hardware purchased from Lucent running TAOS v9.0 or higher. NDLM provides an automatic way of applying license and software options to the devices at your site after they are installed or upgraded.

What are device licences?

The term device licences refers to software options and license options, and is used in this document to collectively refer to the license and software options information for a device. • License options are pieces of information bound to a serial number of a slot card for any Lucent slot cards. License options are used to enable certain functionality on a per card basis. License options are stored on the card. • Software options is a system-wide code that is stored and handled on a per system basis (for example, a Stinger). These codes are already in use and are provisional on a per system basis. Software options are stored on the system.

Please note that software options for a Stinger need to be applied to both controllers in the case of a multiple controller environment.

Software options “apply” to all cards in a system or “override” an individual license. For example, you can purchase provisioning support on a per-card basis with license options, or purchase a software option that enables the functionality on all applicable cards.

Note: License and Software options are ultimately added to the NavisAccess DSL Database. NavisAccess DSL adds the newly learned codes to the cards in the TAOS device in a secure manner.

The illustration below graphically depicts the procedure for providing license and/or software options information.

The illustration below graphically depicts the procedure for providing device license information.

9-2 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) What are device licences?

How Device Licences are updated

The Navis Device Licence Manager (NDLM) utility updates software and licence information for a device(s) using a 2-step process.

Step 1- NDLM retrieves the device licences and serial numbers to create a request file. It does this by gathering device information from the NavisAccess DSL database and storing that information locally in a request file in a predefined format. Please see “Generating a Device License request file” on page 9-6. • The file created in Step 1 is e-mailed to [email protected]. A response file will be sent to you with all the device license information you have requested. The file is sent as an email attachment, and may be optionally compressed. • Receive and place the response file in the NavisAccess DSL directory. See “Receiving a response file” on page 9-10.

Step 2 - The License information on the devices is updated using the response file. Please see “Applying the license response file” on page 9-10. • After the device licences information is updated on the devices, the updated devices may be manually rediscovered. The NavisAccess DSL discovery process retrieves the current Device Licence information from the devices and populates that information in the appropriate database tables.

Note: Some updates do not change the behavior of the device until they are rebooted. Please see “Setting the Advanced options” on page 9-5 for details.

If you have technical issues with NDLM, or do not receive a response within 24 hours, contact Network care for support.

Who should use NDLM?

This utility can be used only by users with Navis “Admin” level privileges. All other level users do not have the permissions necessary to use this functionality.

Directory Structure

NavisAccess DSL will have the following directory to support the functionality provided by the Navis Device License Manager. All NDLM files will be stored in this directory.

NavisAccess NavisAccess DSL installation directory (includes all NavisAccess DSL directories.) featurecode Directory under NavisAccess installation directory for NDLM files

NavisAccess DSL Installation and Administration Guide 9-3 Navis Device License Manager (NDLM) Launching the NDLM

logs Directory under featurecode directory for storing any log files. reprocess Directory under featurecode directory storing any reprocessing files request Directory under featurecode directory storing any request files response Directory under featurecode directory storing any response files with current license and software options information configured in the Customer database.

Launching the NDLM 1 Access the NDLM from the NavisAccess main menu: Tools >Device License Manager. The Login screen appears. Note: If you make a mistake while entering the user name or password, the NDLM allows you two more attempts (a total of three) to enter the correct information before locking you out.

2 Enter the User Name and Password.

Note: If you try to login to the NDLM while an active session exists, the following message displays: Application started by user Admin on Fri Oct 27 14:17:52 2000 is still alive. Do you want to clear the lock and proceed? (Y/N).

This message is designed to prevent two people from requesting license options at the same time for the same device.

Enter Yes to clear the lock. By clearing the lock, you are allowed to access the Navis Device License Manager and continue.

The Welcome to Navis Device License Manager screen appears.

9-4 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Setting the Advanced options

At this screen you have three selections: • Advanced Settings- This selection allows you to change SNMP options before using the Navis Device License Manager to create or set license or software options files. It also allows you to reboot a device after card/code changes have been made. This selection is optional, you need not select it. • Create License Request File -This selection allows you to request license/software options for device(s) and individual groups in the Device and in the Device or Groups folder in Examiner. This selection is required. You must select it first. • Apply License Response File- Allows you to set the license/software options for a device(s) by processing the file that contains the device licences information for the selected device(s). This selection is required. You must select it second (after creating a license request file).

Setting the Advanced options

With this optional selection, you can change SNMP options before using the NDLM to create or set device license files. Because the response time of your devices may vary according to the site and utilization of your network, you may wish to adjust the speed of the NDLM.

To change the SNMP options: 1 Click on the Advanced Options button in the Welcome to Navis Device License Manager screen.

The Advanced Settings screen opens.

2 Make any desired changes using the descriptions in the following table as a guide.

Table 9-1. SNMP Advanced options and their description

SNMP Advanced options Description

Time Out Sets a value, in milliseconds, before an SNMP packet is considered lost in the network.

NavisAccess DSL Installation and Administration Guide 9-5 Navis Device License Manager (NDLM) Generating a Device License request file

Table 9-1. SNMP Advanced options and their description (continued)

SNMP Advanced options Description

Retries You can set the number of times an SNMP operation will be retried before the file is considered lost.

Reboot Devices After Check this box to reboot the device after the update has Licenses Are Set taken place (licensing information requires this). Rebooting the device causes the changes that were made to be stored permanently.

Note: You can optionally set the Reboot Devices After Licensing Are Set before proceeding to create a license/software response file.

Use Default Settings Press this button to restore the default settings.

Generating a Device License request file

Step 1

In this step, you generate a device license request file and email that file to Lucent.

You can request license/software options for all, some, or one device defined in the NavisAccess database. You can also request license/software options for individual groups.

To create a license/software options request file from the Welcome to Navis Device License Manager screen: 1 Click the Create License Request File button and click Next. The Select Devices screen appears.

9-6 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Generating a Device License request file

The table below describes the buttons available for the Select Devices screen.

Button Function Add Allows you to add a device from the Available Devices window to the Selected Devices window. Remove Allows you to remove a device from the Selected Devices window to the Available Devices window. Add All Allows you to add all the devices from the Available Devices window to the Selected Devices window. Remove All Allows you to remove all devices from the Selected Devices window to the Available Devices window.

2 Highlight the device(s) you need from the Available Devices widow, and click the Add button to move the device(s) to the Selected Devices window. 3 Click Next.

The Retrieval Options screen appears.

At this screen you have two options. These are described in the table below.

Option Description Build license request file from Allows you to create the request file for all the devices and their cards that were existing database most recently discovered, based on the current status of the database. Recent changes to the network may not be reflected in the NavisAccess database.

Note: It is highly recommended that you build the request file from the existing database unless you know that it has been modified.

NavisAccess DSL Installation and Administration Guide 9-7 Navis Device License Manager (NDLM) Generating a Device License request file

Option Description Poll Devices and update database Allows you to update the database to include any changes (for example, card prior to building license request file additions/deletions) made since the last initialization. In case of doubt, update the database to include all items. Please note that polling the devices on a large network is a lengthy operation. Note: Devices that cannot be polled for the current license information will not be included in the request file. If this occurs, the IP addresses of these devices will be displayed at the end of the log file window, the log file itself in the NavisAccess directory.

The devices that could not be contacted, may be down or disconnected.

4 Click Build license request file from existing database. 5 Click Finish when ready. The Processing screen appears, displaying the request steps entailed for the device license request.

6 Click the Close button to exit the NDLM.

The request file that you have just created, will be in the $Autobahn/featurecode /request directory.

Request files are created using the following naming convention: cardcode-request-mmdd-hhmmss.XML Where: MM = month, DD = day, hh = hour, mm = minutes ss = seconds XML= the file extension If the request file did not process successfully, you need to refer to the log file. See “The request log file” on page 9-15 for a sample of this file.

9-8 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Processing the response file

Forwarding the request file

Once the request file has been created, you need to send it to Lucent, so that a response file may be created for you. 7 Locate the request file that you just created in the $Autobahn/featurecode/request directory. For example, the Processing screen in Step 1 displays the NavisAccess directory path to be: e:/navisaccess/featurecode/request/cardcode-request-1116 -173415.XML. 8 Create an email and attach the request file (cardcode-request-1116-173415.XML) to it. If you use email options, such as email signatures, use them in the body of the email; do not attach them to the email. Note: The NDLM only supports attachments that are either ‘base64’ or ‘clear text’ encoded. Refer to your email User’s guide or online help to set your text/attachments settings to ‘base64’ or ‘clear text.’ 9 Send the email to: [email protected] Note: Please note that the email and request file have a 1:1 ratio. You may include only 1 request file per email. It is strongly recommended that a large file be compressed. If you send a compressed request file, you will receive a compressed response file in the same file format in which it was sent. For example, a Zip compressed request is responded to with a Zip compressed response. The following file formats are used, and appear as the file extension: • gz: GNU-Zip compress • Z: Sun Solaris Unix compress • ZIP: Zip compression • XML|XML: uncompressed request

Note: A compressed response file, must be manually uncompressed before you can use it. Step 1 is now complete.

Processing the response file

Step 2

In this step, you receive the response file sent by Lucent and apply the device licenses using this file.

Note: A response file for a correctly formed request file should be received from the license server within 24 hours. If you do not receive a response file within 24 hours, please contact “Customer Service” .

NavisAccess DSL Installation and Administration Guide 9-9 Navis Device License Manager (NDLM) Processing the response file

Receiving a response file

You will receive a response file from Lucent as an attachment to an email. The email’s standard text is the following:

Please find attached response to your request. EmailProcessor response summary: EmailProcessor Build Number (Date): 001 (10/06/2000) Request email received from: [email protected] Request email subject: Lucent EmailProcessor, Re: 1 of CARDCODES_RESPONSE response subject(s) 1 of HASHCODES_RESPONSE response subject(s) ------2 request(s) processed

Please, don’t respond to this message since it has been generated by automated process. Thank you for using EmailProcessor!

P.S. If you sent multiple attachments please note that just the first one was processed. Please, resend all other attachments one by one in order to get the desired responses.

If the request file was sent compressed, the response file will also be compressed. You must manually uncompress the response file before you can use it.

Note: CARDCODES_RESPONSE response subject(s) and HASHCODES_RESPONSE response subject(s), in the body of the response email, refer to the license and software options respectively. 1 Place the response file(s) in the response folder in the NavisAccess directory. Using the directory example in Step 1, you would place the response file in: e:\navisaccess\featurecode\response\EP20001116_1002.XML.

You are ready to apply the device licenses now that you have placed your response file(s) in the NavisAccess directory.

Applying the license response file

The response file(s) contains the device license information for the devices in the request file that you sent to Lucent.

Note: To apply the license response file, you must have “Admin” level privileges.

You are now ready to use the NDLM to enable these device licenses for you. 2 Launch the NDLM from the NavisAccess main menu: Tools > Device License Manager. 3 Click on Apply License Response File in the Device License Manager screen. 4 Click Next.

9-10 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Processing the response file

The Apply Device Licenses screen appears.

The table below lists and describes the options, buttons, and windows displayed in the Apply Device Licenses screen.

Option/button/window Description Processing Information: is displayed after selecting and loading a file (Response File, Load Current File buttons. Current Response File Displays the Response file you have selected.

Note: You may change the name of a response file to suite naming conventions at your site. Current State Displays the file processing progress. For example, Applying Device Licenses...Done Total Licenses Displays the total number of device licenses that will be updated. Percent complete Displays the percentage of the total number of devices that have not been processed.

NavisAccess DSL Installation and Administration Guide 9-11 Navis Device License Manager (NDLM) Processing the response file

Option/button/window Description Response File Selection Response File Allows you to select a file to which you can set the device license options. The files were created with “Generating a Device License request file” on page 9-6. Reprocess File These files contain information about devices that encountered errors while trying to set the device licenses (devices that were successfully processed are not included). You can run a Reprocess File to complete applying device licenses to all devices. Response File Processing Load Current File Select this button to load the file you chose with the Response File button. Apply Licenses Set the licenses for the devices in the selected response file. File Contents window Displays the devices that will be updated by the current response file. Log Message Window Displays the information created while the selected response file is being processed.

At this screen: 5 Click on the Response File button to display the files available. The License File Select screen appears. 6 Select the appropriate file and click OK.

Note: If you have not placed the response file(s) in the appropriate NavisAccess directory, you will not see the response file(s) displayed on this screen.

Note: The Current Path field is fixed, you cannot change it.

The name of the file you have selected displays in the Apply Device Licenses screen in the Current Response File field (once the file is processed, the file name disappears from this field).

9-12 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Processing the response file

The creation date of the file displays (for example, 20001130 - November 30, 2000). Notice also that each file has a unique number (1000, 1001) to distinguish it from other response files. 7 Click on the Load Current File button, to load the file you have selected.

The devices to be updated will appear in the File Contents window. 8 Click on the Apply Licenses button.

The lower window displays the log file. The Apply Device Licenses screen now looks like this:

Notice that the other fields now display the following:

Current Response File Displays the name of the response file just processed.

Current State Describes the status of the response file. In the example above, the file has completed applying the software options.

Total Licenses Display the total number of licenses applied.

Percent Complete Displays the percentage of the license/software options successfully applied. In the example above, the percentage is 100%.

File Contents Number of devices selected are displayed in this window. You can click on a device and the tree will expand and display the cards along with any log messages associated with that card.

Log Messages Messages created while setting the license/software options are displayed in this window. You can double click on a row in the Log Messages window. This will bring up a message box displaying that particular message.

NavisAccess DSL Installation and Administration Guide 9-13 Navis Device License Manager (NDLM) Reprocessing a file

Note: If you chose to Reboot Devices After Licenses Are Set in the Advanced Options screen, the devices that were successfully processed will now reboot even if not all of the devices were processed. Note: If there were no problems while processing the contents of the file, the value for Percent Complete should be 100%. If the values are not 100%, you may need to reprocess some of the devices. Please refer to “Reprocessing a file” on page 9-14 for details. If an error occurs, the Apply License Results window appears displaying the error, the log file name and the Reprocess file name that needs to be run using the Reprocess button. For detailed error information, see “The response log file” on page 9-17. To reprocess a file see “Reprocessing a file” on page 9-14..

Once the file is processed successfully (no errors), the extension of the response file is automatically changed to .bak. This prevents the file from being unnecessarily processed again. Step 2 is now complete.

Reprocessing a file

If an error is encountered while setting the license/software options, a file containing the unprocessed device licenses is created. To access and run this file: 1 Select the Reprocessing button in the Apply Device Licenses screen.

The License File Select window displays, listing the available files.The log file, for the request file that was processed, indicates the name of the reprocess file. Look for that name on this screen.

9-14 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Log file samples

The format for the files is:

REDO = the prefix for the file.

UPD = Update the files are listed by ascending date.

1130 = the month and day the file was created (November 30)

195704 = the hour, minutes and seconds when the file was created.

XML = the file extension.

All files are listed by date in ascending order. For example, the window above displays files ranging in date from November 7 (1107) to November 30(1130). All files have XML as the extension. 2 Select the file that you need to reprocess, then click OK. 3 Click the Load Current File button, to load the file you have selected. 4 Click the Apply Licenses button.

The file is reprocessed to set the device licences, and once again goes through the process described in step 8 on page 1-13.

Log file samples

The following are examples of the request and response log files. If there are discrepancies while creating a device license file, or setting the device licenses, you can review the log file to discern the error in question.

The request log file

The following information is stored in the request log file: • the Group name (“All Devices” or the selected group's name) on which the request was launched • the device name (before the request starts to get the license or software options for the device) • the request status (whether the request was successful or unsuccessful getting the codes from a device)

The log files during this step are created using the following naming convention:

CCGET-MMDD-hhmmss.xml

Where:

MM = month, DD = day, hh = hour, mm = minute, ss = seconds

NavisAccess DSL Installation and Administration Guide 9-15 Navis Device License Manager (NDLM) Log file samples

These files are created in the Logs directory. To view the log file, access: \navisaccess\featurecode\logs.

Sample log file information

Note: The request file name is ancillary.xml.

e:\navisaccess\ featurecode\logs\CCGET-1107-143902.XML

Tue Nov 07 14:39:19 2000 Contacting database for card details - Tue Nov 07 14:39:19 2000 Creating File - Tue Nov 07 14:39:19 2000 Starting to Write request File - Tue Nov 07 14:39:19 2000 Writing software option request - Tue Nov 07 14:39:19 2000 Request for Unit-13282364 written + Request for Card-13285580 written Tue Nov 07 14:39:19 2000 Finished Writing File

These messages are repeated for each device. Any operation that results in an error, causes a corresponding error message to be logged. For example:

: Failed to send request to get Feature Codes for device : Timed out. Failed to receive response for getting Feature Codes from device : Error in writing Feature Codes information to the file.

9-16 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) Log file samples

The response log file

The following information is stored in the response log file: • the license option file name being used to update the feature codes on the devices • the device name (for each device) before it sends the request to update the license/software options to a device • the device status (whether the response was successful or unsuccessful in updating the codes in a device)

The log files during this step are created using the following naming convention:

CCUPD-MMDD-hhmmss.xml

Where:

MM = month, DD = day, hh = hour, mm = minute, ss = seconds

The time stamp used to create this file is the same as the one used in the previous step. This allows correlation of any information, if required, from the log files created during the entire process.

The response log files are also stored in the \navisaccess\featurecode\logs directory.

Note: The response file name is ancillary.xml.

Sample Log File Information

: Updating Feature Codes using for "All Devices". // "All Devices" or selected group’s name.

: Sending request to update Feature Codes for device .: Updated Feature Codes in device .

…

These messages are repeated for each device. Any operation that results in an error, causes a corresponding error message to be logged. For example:

: Failed to send request to update Feature Codes for device . : Timed out. Failed to receive response for updating Feature Codes from device : Feature Codes update failed on device .

...

NavisAccess DSL Installation and Administration Guide 9-17 Navis Device License Manager (NDLM) NDLM error messages

NDLM error messages

Request file

Table 9-2. Request file error messages

Request File Error Messages Description

SNMP messages

Sending SNMP request to device , This message occurs when an SNMP request is being sent to the . device. Example: Sending SNMP request to device Gobsheru-1, 111.111.22

SNMP request could not be sent to device This message displays when an SNMP request cannot be sent to , . the device because the device is down or disconnected. Example: SNMP request could not be sent to device Gobsheru-1 >, <111.111.22>

SNMP Timed out. Request failed for device The SNMP request failed for a particular device because the , . time allotted for the SNMP request has passed. Example: SNMP Timed out. Request failed for Device Gobsheru-1, 111.111.22

SNMP request failed for device . The device does not respond to an SNMP request. The device may be down, or disconnected. Example: SNMP request failed for device Gobsheru-1

SNMP Requests could not be sent - stopping All the SNMP requests have failed. This message would rarely process. be displayed since it is highly unlikely that all SNMP requests would fail.

Starting to retrieve data from device . for a device. Example: Starting to retrieve data from device 111.111.22

Finished retrieving data. This message displays at the end of a license/software retrieval for a device.

Retrieving Data for Device - This message displays while data is being retrieved for a Software/License Option - . device. The IP address, and the software/license option serial number are displayed. Example: Retrieving Data for Device Gobsheru-1 > Software/License Option - 2191965

SNMP operations end. This message displays after polling for all the devices has ended.

9-18 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) NDLM error messages

Table 9-2. Request file error messages (continued)

Request File Error Messages Description

SNMP failures. None of the devices responded. An SNMP request has failed because no response has been received from the devices. The devices could be down or disconnected. This message would rarely be displayed since it is highly unlikely that all devices did not respond.

Process completed. SNMP Requests failed for This message immediately displays after the message “SNMP all devices. License request file will not be failures. None of the devices responded.” Since SNMP requests generated. failed for all devices, the license request file will not be generated. This message would rarely be displayed since it is highly unlikely that all devices did not respond.

Database Messages

Updating Database. This message displays after data from devices has been received.

Contacting database for Software/License This message displays when the request file is generated from Option details. the database.

Database contains no data for the selected This message displays when data is being requested for a device devices. License request file is not generated. from a database that does not have information for that device. Since no information is received, the license request file cannot be generated.

File Operations

Creating License Request File. This message displays while the License request file is being created.

Created License Request File . This message displays when the License request file has been completed. Example: Created License Request File cardcode-request-1121-192421.XML

Starting to Write License Request File. This message displays at the start of a license request file update for a device.

Writing software option request - Serial This message displays when the software option request is in Number- . progress. The serial number will display. Example: Writing software option request - Serial number - 11007681.

Writing license option request- Serial Number- This message displays when the license option request is in . progress. The serial number will display. Example: Writing software option request - Serial number - 11007681.

NavisAccess DSL Installation and Administration Guide 9-19 Navis Device License Manager (NDLM) NDLM error messages

Table 9-2. Request file error messages (continued)

Request File Error Messages Description

Finished Writing License Request File. This message displays when a license request file has been completed.

Other

Operation cancelled by user. Stopping creation This message displays when the user has selected the Cancel of license request file. button to terminate the operation.

The following devices did not respond. This message will display when certain devices do not respond to the request file inquiry. You are prompted to check the Please check the devices and try creating a device(s) status and to generate a new request file for those license request file for them later; Device # - IP devices. Addr.

Warning: Some of the devices did not respond. This message displays when some of the devices did not They may be down or disconnected. Please respond. Possible reasons for failure to connect are given. You check the devices and try creating a request file are prompted to later create a request file for the devices that for them later. The list of devices which did not did not respond. You may check the log file for the names of the respond can be found at the end of the log file - devices that did not respond. filename.

Response File

Table 9-3. Response file error messages

Response File Error Messages Description

"Starting Licenses Update For Device ." update for a device. Example: "Starting Licenses Update For Device Gobsheru-1"

"Completed Processing Licenses On Device Occurs on the completion of card license updates for a device. Card ." Example: "Completed Processing Licenses On Device Gobsheru-1 Card 2191965"

"Completed Updating Licenses On Device Occurs on the completion of a card software update for a Serial Number# ." Example: "Completed Updating Licenses On Device Gobsheru-1 Serial Number# 5164694857"

"Completed Processing Feature Codes For Occurs at the end of a license/software options update for a Device ." device. Example: "Completed Processing Feature Codes For Device Gobsheru-1"

9-20 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) NDLM error messages

Table 9-3. Response file error messages (continued)

Response File Error Messages Description

"Device Licenses Update Occurs after a user has selected the cancel button. Canceled By The User. Terminating ..." Example: "Device Gobsheru-1 Licenses Update Canceled By The User. Terminating ..."

"Errors Occurred Processing License Options Displays when an error occurred while updating For Device ." software/license options for a device. Example: "Errors Occurred Processing License Options For Device Gobsheru-1 "

Verification messages

"License Has Been Disabled On Occurs when the NDLM detects that a License that was Device Card #." Example: "Verification Error: License NM-PROV Has Been Disabled On Device Gobsheru-1 Card #2191965"

"There Are Licenses Disabled On Device Occurs when the NDLM detects that a License that was That Were Not Included With previously enabled is no longer operational for a specific card. License Example: "Verification Error: There Are Licenses Disabled Update." On Device Gobsheru-1 That Were Not Included With Card 2191965 License Update."

" License Is Enabled On Occurs when the NDLM detects that a License is set on the Device Card # But Was Not Included With The option update. Current Transaction." Example: "Verification Error: License NM-PROV Is Enabled On Device Gobsheru-1 Card #2191965 But Was Not Included With The Current Transaction."

"There Are Licenses Enabled On Device Occurs when the NDLM detects that a License is set on the That Were Not Included With card, but the card was not part of the current license/software License option update. Update." Example: "Verification Error: There Are Licenses Enabled On Device Gobsheru-1 That Were Not Included With Card 2191965 License Update."

“License Option %d Has Not Occurs when a license/software update failed to be applied on Been Set On The Device Card a specific card. #." Example: "Verification Error: License NM-PROV Option 2 Has Not Been Set On The Device Gobsheru-1 Card #2191965."

NavisAccess DSL Installation and Administration Guide 9-21 Navis Device License Manager (NDLM) NDLM error messages

Table 9-3. Response file error messages (continued)

Response File Error Messages Description

"Error Updating License Options For Device Occurs when a license/software update failed on a specific #." Example: "Verification Error: Error Updating License Options For Device Gobsheru-1 Card #2191965."

" SECProm Error # Indicates that an error occurred setting the license and shows Occurred Checking License ()." Example: "Verification Error: SECProm Error #4 Occurred Checking License (u902eHlk’as> wt]">13 41]pot4 )."

"SECProm Error: # Indicates that an error occurred setting a license and shows the ." error string of the SECProm. Example: "Verification Error: SECProm Error: #4 The 1st argument to the command is invalid."

Database Messages

"Error Writing License Options To Database For Occurs when a database error prevents the writing of a Serial Number #." Card/Unit data to the database. Example: "Database Error: Error Writing License Options To Database For Serial Number #5164694899"

Process Messages

"There Are No Licenses For Occurs when the response file has no features for a specific #." serial number. Example: "Process Error: There Are No Licenses For Card #6314684832"

"SNMP Error On Device Occurs when an SNMP timeout error occurs on a device which # ... results in operations for that device being discontinued. Discontinuing License Updates On This Example: "Process Error: SNMP Error On Device Device." Gobsheru-1 Card #6314684832 ... Discontinuing License Updates On This Device",

"SNMP Timeout On Device ... When an SNMP timeout error occurs on a device, processing Skipping #." is halted for all cards. This appears for each card that is bypassed. Example: "Process Error: SNMP Timeout On Device Gobsheru-1... Skipping Card #6314683832"

9-22 NavisAccess DSL Installation and Administration Guide Navis Device License Manager (NDLM) NDLM error messages

Table 9-3. Response file error messages (continued)

Response File Error Messages Description

"Errors Occurred Processing Licenses On Occurs on any error that occurs on a card or unit. Device Card #." Licenses On Device Gobsheru-1 Card #6314634832"

"Error () Occurred Occurs after an SNMP error message occurs. This appears for Processing Licenses On Device Card ." Example: "Process Error: Error (6) Occurred Processing Licenses On Device Gobsheru-1 Card #6314634832"

SNMP messages

"Timed Out Setting License ()." appears during the license update Example: "SNMP TimeOut Error: Timed Out Setting License (u902eHlk’as> wt]">13 41]pot4 )."

" Timed Out Checking License ()." the licence update had been applied to the device Example: "SNMP TimeOut Error: Timed Out Checking License (u902eHlk’as> wt]">13 41]pot4 )."

" Timed Out Waiting For Verification of License An SNMP message appears when checking to see if the Update For #...Discontinuing Licenses Operations Example: "SNMP TimeOut Error: Timed Out Waiting For On This ." Verification of License Update For Card #6314634832...Discontinuing Licenses Operations On This Card",

": Occurred Issuing Reboot for Occurs when an SNMP message occurs during a reboot Device ." operation for a device Example: "SNMP Error: General Error: Occurred Issuing Reboot for Device Gobsheru-1"

Parser messages

"Parsing License File ." Occurs at the start of parsing the response file Example: "Parsing License File 1126200-response.XML"

"Parsing File at Position Occurs when a parsing the response file and an unexpected tag ." is read Example: "Parser Error: Parsing File 1126200-response.XML at Position 23456"

"File Not Valid Response File Type" Occurs on any response file parsing error Example: "Parser Error: File Not Valid Response File Type"

NavisAccess DSL Installation and Administration Guide 9-23 Navis Device License Manager (NDLM) NDLM error messages

Table 9-3. Response file error messages (continued)

Response File Error Messages Description

"Subject Submitted was ()." Occurs when parsing the response file and an unexpected subject string was encountered Example: "Parser Error: Subject Submitted was (WRONG_SUBJECT)"

"Subject Is Empty." Occurs if the response file subject tag is empty Example: "Parser Error: Subject Is Empty")

"Expected Start Tag but Occurs if an unexpected start tag was read in the response file. encountered ." Example: "Parser Error: Expected Start Tag but encountered "

"Expected End Tag but Occurs if an unexpected end tag was read in the response file. encountered ." Example: "Parser Error: Expected End Tag but encountered "

9-24 NavisAccess DSL Installation and Administration Guide Uninstalling NavisAccess 10

This appendix provides the step-by-step instructions for completely uninstalling NavisAccess. This procedure is helpful if you are moving NavisAccess from one machine to another or any situation where you want to completely remove all NavisAccess files from your machine.

To remove NavisAccess from your machine: 1 Open the file /etc/navisaccess to see the location of your $AutoBahn directory. You need this information because you will be deleting $AutoBahn later in this procedure. 2 Stop all NavisAccess services by issuing the following command: nautil shutdown You can ensure all services have stopped by running nautil status. If there are any services still running, re-run nautil shutdown. 3 Delete the following files in the directory /etc/rc0.d: – K8navisaccess –K9windu – K9ascendDBeng – K9xvfb4na – K9osagent – K99windu (NavisAccess 4.x file) – K99ascendDBeng (NavisAccess 4.x file)

Note: Depending on your installation type, some of these files may not be present. For example, if this is not a primary server in a distributed installation, K9ascendDBeng will not be present in this directory. 4 Delete the following files in the directory /etc/rc2.d: – S98navisaccess –S97windu – S97ascendDBeng – S96xvfb4na – S97osagent – S99windu (NavisAccess 4.x file) 5 Delete the following files in the directory /etc/init.d: – navisaccess –windu

NavisAccess DSL Installation and Administration Guide 10-1 Uninstalling NavisAccess

– ascendDBeng – xvfb4na –osagent 6 Delete the line “./$AutoBahn/.navisaccessprofile” from the /.profile file. 7 Delete /usr/X11R6 link as follows: a. cd /usr b. rm X11R6 8 Delete var/adm/windu. 9 Delete etc/navisaccess. 10 Delete your $AutoBahn directory. 11 Delete /odbc.ini and /asasrv.ini.

File removal is complete!

10-2 NavisAccess DSL Installation and Administration Guide Trap Forwarding

Configuring Trap Forwarding

NavisAccess DSL provides the ability to forward traps and NavisAccess DSL events to multiple destinations, for use with third party event management tools. Traps can include those received from Lucent network devices, while events are generated by NavisAccess DSL itself, as it monitors for threshold crossings, downed channels and modems, etc.

Following are configuration instructions for NavisAccess DSL trap forwarding.

Adding a trap

You can use the default destination port, port 162, for the traps or you can redirect the traps to another port. If a port is used that is not the default, you must specify it.

To add a trap destination, at the command line enter: imc -addtf [IP Address] -port [port number]

Example: imc -addtf 192.222.1.22 133 Note: You do not have to specify the port number if the port being used is port 162, which is the default port.

Viewing current trap destinations

To view a trap destination, at the command line enter: imc -showtf

This command will return information similar to the following: Address=192.168.10.10, Community string=public, Port=162

Removing a trap

To remove a trap destination, at the command line enter: imc -deltf [IP Address] -port [port number]

You must specify the port number if the port being used is not the default port (162).

NavisAccess Installation and Administration Guide A-1 Forwarding traps/events to a third party application

When using third party applications such as HP OpenView and NetCool to view NavisAccess events, there are several steps which need to be completed.

Loading MIBs onto the third party application

When running on a third party Network Management System, NavisAccess integtates with the third party eventing system. There are additional steps and considerations for MIBs on these systems.

When loading MIBs onto the third party application: 1 From the /mibs/ascend/ directory, select ascend.mib and load the MIB. This must be the first MIB you load. 2 From the /mibs/ascend/ directory, load the navisaccess-ov.mib, and the ascend_trap.mib 3 You may load any additional MIBs you wish to load, with the following consideration. You must load wan.mib before loading xdsl.mib, adslcap.mib and/or sdsl.mib.

Adding a trap

You can use the default destination port, port 162, for the traps or you can redirect the traps to another port. If a port is used that is not the default, you must specify it.

To add a trap destination, at the command line enter: imc -addtf [IP Address] -port [port number]

Example: imc -addtf 192.222.1.22 133 Note: You do not have to specify the port number if the port being used is port 162, which is the default port. Multiple Standalone Installations on the Same LAN

If you are installing more than one standalone installation on the same LAN, the following setup format is required for the second installation. setup -n navisyyyyxxx -o xxxxx where: yyy is a unique name xxxxx is an OSAGENT port in the range of 49152 - 65535.

For example, if NavisAccess DSL is being installed on machine 192.168.50.55,using OSAGENT port 49152, the setup parameters would be: setup -n navismysite55 -o 49152 Note: “-o” is the letter “O”, not a zero.

NavisAccess DSL Installation and Administration Guide B-1

File Maintenance Notes

NavisAccess DSL components write to log files in certain situations. Though there is a limit on the log file size, all the log files combined together could take up a lot of hard disk space. A periodic cleanup of log files is recommended.

Note: If a log file is very large, please contact Lucent Technical Support before erasing it. To view the log files: 1 Access the $AutoBahn directory on your machine (if it is farm, do this on every machine). 2 At the command line enter: ls-l *.log A list of all log files display. To delete a log file: 1 Execute nautil shutdown on your machine (if it is a farm, do this on every machine). 2 Access the $AutoBahn directory 3 Enter rm *.log. This will remove all your log files. To remove a selected log file(s) substitute the * in the command with the name of the log file. When you have finished cleaning up your log files: 4 Execute nautil start (if it is farm, do this on every machine). NavisAccess DSL creates files for the calls handled by it. Over a period of time, these files could consume a lot of hard disk space. These files will need to be backed up and removed periodically from the system that has “Call Logging Streamer” installed on it. For details on how to maintain these files, please refer to Chapter 7, “Database Maintenance” in this guide. NavisAccess DSL stores a large amount of data in the database. Over time, the database may grow considerably large. Periodic backup of the database and DB grooming must be done to ensure that enough hard disk space is available for running NavisAccess DSL. NavisAccess provides an automatic Database Groomer schedule, found in the Schedule Wizard (Configure > Schedules). The default values for number of days of data saved may be changed by editing the Database Groomer schedule. The database can be backed up while running by using the DBMaint application. To start DBMaint, run dbmaint at the command line. Only a NavisAccess DSL administrator can log into the DBmaint application. For detailed information, please refer to Chapter 7, “Database Maintenance” in this guide, and the Schedule Wizard chapter in the NavisAccess DSL User’s Guide. At least 2 GB of free hard disk space must be available at any time for running NavisAccess DSL. If the hard disk space is running lower than this limit, log files or DB cleanup must be done to ensure that enough hard disk space is available for NavisAccess DSL. Please refer to Chapter 7, “Database Maintenance” in this guide.

NavisAccess DSL Installation and Administration Guide C-1

Multiple Server Farms on the Same LAN (Distributed Server)

If you are installing more than one distributed server farm on the same LAN, the following setup format is required for the second server farm.

Distributed Server

Important! For multiple server farms on the same LAN, use OSAGENT ports from the range 49152 - 65535.

For the second server farm, use the following setup format: • Main Server setup -n naviseuroxxx -o xxxxx where: xxx is equal to the last byte of the IP address on which NavisAccess DSL is being installed. For example, if NavisAccess DSL is being installed on machine 192.168.50.55, then the setup parameters would be: setup -n naviseuro55 -o 49152 Note: “-o” is the letter “O”, not zero. • Secondary Servers setup -n naviseuroxxxx where naviseuroxxx is exactly the same as it was for the main server. For example, if the main server is installed with: setup -n naviseuro55 -o 49152 then all secondary server installations must begin with: setup -n naviseuro55 • Workstations setup -n naviseuroxxxx where: naviseuroxxx is exactly the same as it was for the main server. For example, if the main server is installed with: setup -n naviseuro55 -o 49152 then all workstation installations must begin with: setup -n naviseuro55

NavisAccess DSL Installation and Administration Guide D-1

Workstation Installation on a Separate Subnet

All servers in a NavisAccess DSL farm must be on the same subnet. However, Workstations may be installed on a separate subnet and may also be installed on a separate LAN across a WAN connection.

In both cases, the following parameters must be used on the Workstation machine when calling the NavisAccess DSL Installation Application:

./setup -n -o -ni -oi -a OSAGENT

Example: If the Primary Server is using a DBServer name of Navis123, an osagent port of 27123, and has an IP address of 34.34.3.23. The Installation Application would be called as follows:

./setup -n Navis123 -o 27123 -ni 34.34.3.23 -oi 34.34.3.23 -a OSAGENT

Determining the OSAGENT port

To determine the osagent port of the Primary Server, go to the machine and run:

echo $OSAGENT_PORT

The osangent port is displayed.

Note: The default osagent port is 1492 (this is used if no osagent port is specified when installing the Primary Server).

Determining the Primary Server DBServer name

To determine the DBServer name of the Primary Server, go to the machine and run:

more /.odbc.ini

The EngineName value is the DBServer name.

! Caution: NEVER modify the .odbc.ini file

Note: The default DBServer name is NavisAccessDB (this is used if no DBServer name is specified when installing the Primary Server).

NavisAccess DSL Installation and Administration Guide E-1

Configuring Printing

To print reports, program windows and so on from within NavisAccess DSL, you must properly configure the printing on Solaris and within NavisAccess DSL.

Configuring Solaris

The Solaris operating system must be properly configured for printing. If you have already done so, you may skip to the next section. 1 To configure printing, you must enter the printer name and IP address in the /etc/hosts file. The /etc/hosts files uses the following parameters: – IP address –Host Name – Alias For example: 192.168.10.1 Printer_1 P1

Note: Use a suitable UNIX editor to add the printer to this file. 2 Run the Solaris Admintool by entering the following at the command line: admintool& The Admintool window opens. 3 From the menu, select Browse > Printers. Displays any printers currently set up. 4 To add a printer, choose Edit > Add > Access to Printer. 5 Add the Printer Name and the Printer Server (as you defined it in the /etc/hosts file). You may also add a description and choose this printer as your default printer. 6 Click [OK]. The printer is now setup in Solaris.

Configuring printing within NavisAccess DSL 1 From within NavisAccess DSL, click any Print icon to bring up the Print window. 2 Click the [Properties] button to open the Printer Setup window. 3 Click the Printer Specific button in the Printer Setup window. 4 Click the [Install] button to open the Printer Installation window. 5 Click the [Add Printer] button to open the Add Printer window. 6 Click the [Define New Port] button to open the Ports window. 7 Click the [Spooler] button to create a port for the defined printer.

NavisAccess DSL Installation and Administration Guide F-1 Configuring Printing

8 Click [Dismiss] to save the information. 9 In the Add Printer window, select the type of printer from the Printer Devices column, and select the port from the Current Port Definitions column. Click [Add Selected]. 10 Click [Dismiss] to save the information. 11 Return to the Printer Installation window, and again click [Dismiss]. 12 Click Options, and select the printer you are using from the drop-down list. 13 In the Printer Setup window, click [Save]. The printer configuration is now saved. 14 To print your first report after saving the printer configuration, select the Printer button twice to print your first report. Thereafter, to print other reports, select the printer button once.

Distributed Servers

To configure printers under a distributed server environment: 1 Run naprinter on the machine where Schedule Server is installed. 2 Follow the entire configuration instructions sequence as described above.

F-2 NavisAccess DSL Installation and Administration Guide The nautil Utility

Note: nautil is available for Solaris versions only.

The nautil utility monitors and manages the background services of NavisAccess DSL.

These services run on every machine that NavisAccess DSL is installed on and will vary depending on which components of NavisAccess are present on the machine.

Using the nautil utility 1 Before starting any nautil option, shut down the NavisAccess DSL user application. 2 Open a terminal session and type: nautil A list of nautil options appears:

start Starts all NavisAccess DSL services.

status Displays the status of all services.

shutdown Shuts down every service and cleans the shared resources. Once started, this option should not be stopped.

stop Allows you to stop services manually. When run, nautil stop will list of all the services running, stopping at each, and then prompt you to stop the desired service. This option is particularly useful when only one or two services need to be stopped.

dbmaint Stops those processes not needed by dbmaint; everything except windu, edispatcher, xvfb, and dbsrv6. The database server (dbsrv6) is left running in order to log into dbmaint as Admin. Use this command when performing database operations in dbmaint that require the database server to be shutdown, such as restoring, moving or reinitializing a database.

3 To run the desired option, type: nautil [option] Where option can be start, status, shutdown, or stop.

Note: Non-root users can only run the status option. To use start, shutdown, or stop, you must be a root user.

NavisAccess DSL Installation and Administration Guide G-1 Using the nautil utility to shutdown NavisAccess in a Distributed environment

Distributed environment: Overview

In a distributed server environment, the server components are distributed across one or more machines. This provides a mechanism for distribution of server-side processing. One or more client workstations must also be installed, to distribute client-side processing. Multiple Telnet and/or Xterm sessions may log in to the workstations.

If all distributed components are installed on one physical machine, the client processing must still take place on one or more separate machines (i.e. workstations). That is, if a distributed installation is chosen, you cannot run Xterm and Telnet sessions off the servers. There must be at least one workstation installed to provide GUI processing. – Primary Server In a distributed environment, the database server (DBserver) resides on the Primary Server. The database server, in turn, contains the Distribution Plan. The Distribution Plan assigns components to the other machines in the “server farm” (an environment consisting of several machines is referred to as a “farm”). – Secondary Server(s) In a distributed environment, any of the servers other than the Primary server, are considered Secondary Servers. – Workstation(s) In a distributed environment, a workstation provides a local GUI software which in turn logs in to the server.

Shutting down NavisAccess

When shutting down NavisAccess in a distributed environment it is very important that you shut down the machines in the following order: 1 Workstations - in no particular order. 2 Secondary Servers - in no particular order. 3 Primary Server - The primary server must be shutdown last.

If any secondary or primary server in a distributed environment is shut down, be sure that you shut down all other machines in that distributed environment.

To perform the shutdown, at the desired machine type:

nautil shutdown The nautil Utility Troubleshooting NavisAccess server processes with nautil

Troubleshooting NavisAccess server processes with nautil

Server processes in NavisAccess provide the underlying structure for NavisAccess server components to communicate and gather data. In a distributed environment, when one of these processes goes down, one or more componenents in the farm may be affected.

NavisAccess provides nautil, which can be used to check the status of these processes on any component in the farm.

When troubleshooting NavisAccess server processes using nautil, the first step is obtaining the status of those processes by typing the following at the command line: nautil status

Typing this will display the status of all processes running on that server. For example: X Virtual Frame Buffer Service is running. (PID id 235) Database server is running. (PID id 468) WindU(tm) Registry is running. (PID id 307) WindU(tm) Service is running. (PID id 319) osagent is running. (PID id 288) edispatcher is running. (PID id 535) Adaptive Performance Monitor is running. (PID id 643) tftp server is running. (PID id 669) SNMP server is running. (PID id 574) IMC is running. (PID id 548) Event Streamer is running. (PID id 561) NMD Domain Server is running. (PID id 656) SRM server is running. (PID id 682) Component server is running. (PID id 587) Reporting Server is running. (PID id 600) GUI server is running. (PID id 613) Radius Streamer is running. (PID id 630) AutoGrouping engine is running. (PID id 697)

As you can see, nautil is displaying the logical name of the server process. These names correspond to a process executable. The process executable is the actual file that resides on the server.

NavisAccess DSL Installation and Administration Guide G-3 The nautil Utility Troubleshooting NavisAccess server processes with nautil

The following table provides the correlation between the logical process name (as shown by nautil status), and the actual file name on the server:

Table J-1. Process name to process executable correlation table

Process name Process executable

X Virtual Frame Buffer xvfb

Database server dbsrv6

WindU(tm) Registry windu_registryd43

WindU(tm) Service windu_serviced43

osagent osagent

edispatcher edispatcher

Adaptive Performance Monitor apmon

tftp server tftpsrv

SNMP server snmpsrv

IMC imc

Event Streamer eventstreamer

NMD Domain Server nmddomainserver

SRM server srmserver

Component server nmdserver

Reporting Server reportingserver

GUI server guiserver

Radius Streamer radiusstreamer

AutoGrouping engine autogroupingengine

Process executables and NavisAccess Server components

Each process executable runs on one or more NavisAccess component servers. When a process executable stops, it effects the NavisAccess component server on which the process is running.

For example, if the the dbsrv6 process executable stops running, the Database Server will stop, causing a communication failure between the various NavisAccess componenent servers.

Because each component server in the NavisAccess farm is responsible for a different task, NavisAccess will be affected differently, depending on which process executable has stopped.

G-4 NavisAccess DSL Installation and Administration Guide The nautil Utility Troubleshooting NavisAccess server processes with nautil

The following table lists the NavisAccess component servers, the process executables that run on that server, as well as the role that the componenent server plays in a distributed NavisAccess environment.

Table 10-2.NavisAccess server components and thier role in a distributed NavisAccess environment

NavisAccess server process executables Description component name which run on this component

Database Server dbsrv6 Contains the Sybase Database Server. It also has the Osagent which facilitates communication between nmddomainserver different CORBA objects. IMC osagent edispatcher

Scheduling Server srmserver The Scheduling Server is the background component of the NavisAccess DSL GUI (user interface). It processes tftpsrv background scheduling and background auto discovery. windu_registryd43 windu_serviced43 imc edispatcher snmpsrv

Auto Grouping Engine autogroupingengine This component triggers auto discovery and creates Linegroups and Services based on call logging packets received from devices.

Call Logging Streamer radiusstreamer Receives Call Logging packets in real-time and stores them on disk. These files are later used by the reporting nmdserver modules. imc The Call Logging Streamer database component (clrdata) edispatcher should be on the same machine as the Reporting Server. If eventstreamer these two components are on separate servers, you need to mount the /clrdata directory so that data can be accessed by the Reporting Server.

NavisAccess DSL Installation and Administration Guide G-5 The nautil Utility Troubleshooting NavisAccess server processes with nautil

Table 10-2.NavisAccess server components and thier role in a distributed NavisAccess environment

Data Management apmon The Data Management Server contains the following: Server nmdserver • Event Streamer: This stores the events in the database. imc • Adaptive Performance Monitor: Processes DSL edispatcher Service data that is periodically written to the eventstreamer database. It calculates weighted averages of that data and restores it to the database as a performance template for each service. This template is then usable for adaptive threshold monitoring. • Progress/Disconnect View Server: This is the back-end process that responds to user requests to view the Progress/Disconnect Viewer suite of applets.

DSL Service snmpsrv Processes real-time DSLdevice traffic into per-service, Management Unit per-interval averages. This data is then streamed to the nmdserver database and is also available for applets such as DSL

imc Watch. edispatcher

Call Logging Receiver nmdserver Receives call logging packets and routes them to all interested processes such as the DSL Service. imc edispatcher

GUI Server guiserver This is the back-end process responsible for collecting and publishing data specific to the distributed GUI applets, imc such as Examiner, DSL Watch, Active Sessions, etc. edispatcher The GUI Server and Reporting Server can be combined during the installation to reside on one server, called the Component Server.

To perform this installation type: • From the setup command line, type -m single. For example:

./setup -n -o -m single

G-6 NavisAccess DSL Installation and Administration Guide The nautil Utility Troubleshooting NavisAccess server processes with nautil

Table 10-2.NavisAccess server components and thier role in a distributed NavisAccess environment

Reporting Server reportingserver This processes front-end and back-end requests for reports. It generates the report’s display data and publishes imc it to the client for viewing. edispatcher The Reporting Server component should be on the same machine as the Call Logging Streamer. If these two components are on separate servers, you need to mount the machines so that data can be accessed.

The GUI Server and Reporting Server can be combined during the installation to reside on one server, called the Component Server.

To perform this installation type: • From the setup command line, type -m single. For example:

./setup -n -o -m single

NavisAccess DSL Installation and Administration Guide G-7 The nautil Utility Troubleshooting NavisAccess server processes with nautil

G-8 NavisAccess DSL Installation and Administration Guide The TFTP Server

The following sections describe how to use the TFTP Server to configure a port number and to configure TFTP to work with NAT (Network Address Translation). For a detailed description of TFTP, please refer to Chapter 15, “Device Management: Configuration Tools”, in the NavisAccess DSL User’s Guide.

The TFTP Server allows you to monitor the status of TFTP downloads and uploads, to view historical data about them, and to set parameters such as maximum retry, timeout, port number and security settings.

The TFTP Server is started automatically when NavisAccess DSL starts.

Configuring the TFTP Server

To configure the TFTP Server, open the reglocal.dat registry file in a text editor. The reglocal.dat file is located in the following directory:

/registry/reglocal.dat

The following section indicates specific TFTP server settings: ------[SOFTWARE\Lucent\NavisAccess\tftp] Accept Requests From Navis Only,REG_DWORD=0 Maximum Retries,REG_DWORD=5 Timeout In Seconds,REG_DWORD=3 Enable Session Audit,REG_DWORD=1 Enable Hourly Statistics Log,REG_DWORD=0 TFTP root directory,REG_SZ= Maximum Parallel Sessions,REG_DWORD=75 ------

For further information on the server settings, refer to “TFTP Server Setup” on page H-1.

TFTP Server Setup

The TFTP Server setup parameters in the reglocal.dat file allow you to configure the TFTP server.

Before modifying the TFTP registry settings, shut down the TFTP server:

NavisAccess DSL Installation and Administration Guide H-1 The TFTP Server

1 At the x-session, type: nautil status 2 Hit [Enter] until you are prompted to stop the TFTP server process. 3 Type "y" to stop the TFTP server.

To configure the TFTP Server, open the reglocal.dat registry file in a text editor. The reglocal.dat file is located in the following directory:

/registry/reglocal.dat

The following is a sample of the TFTP Server section:

------

[SOFTWARE\Lucent\NavisAccess\tftp]

Accept Requests From Navis Only,REG_DWORD=0

Maximum Retries,REG_DWORD=5

Timeout In Seconds,REG_DWORD=3

Enable Session Audit,REG_DWORD=1

Enable Hourly Statistics Log,REG_DWORD=0

TFTP root directory,REG_SZ=

Maximum Parallel Sessions,REG_DWORD=75

------

Parameters that can be set include:

Table 10-3. TFTP Server parameters

Parameter Description

Accept request from Set this option to "1" to only accept requests made by NavisAccess DSL only NavisAccess DSL; that no other requests will be honored. The default is off, or "0".

Example: REG_DWORD=1

Use this option to secure information sent to and received from NavisAccess DSL via the TFTP server.

Note: Whenever a TFTP request is rejected due to security issues, an appropriate message is logged into the log file.

Maximum Retries Sets the number of times the TFTP server will retry a transfer before failing. The default is 5.

Timeout In Seconds Sets the amount of time, in seconds, that a transfer will be attempted before failing and retrying. The default is 3.

H-2 NavisAccess DSL Installation and Administration Guide The TFTP Server

Table 10-3. TFTP Server parameters

Parameter Description

Enable Session Audit Set this option to "1" to enable logging of TFTP events to the log file. This option is enabled by default.

Enable Hourly Statistics Set this option to "1" to enable the logging of cumulative statistics. The default is off, or "0".

Example: REG_DWORD=1

Without cumulative statistics, the log file will record the following:· • Operation type • File name • Source IP address • Destination IP address • Start Date and time • Stop Data and time • Total Blocks

Cumulative statistics include information on the following: • Read Requests • Write Requests •Errors • Retries • Blocks Transmitted • Blocks Received

TFTP Root Directory Use this option to restrict the TFTP server to retrieve or write information to a specific directory.

Note: For UNIX users: When configuring the "TFTP Root Directory" feature, no NavisAccess DSL clients can be running. Shut down all NavisAccess DSL clients, including Xterm sessions, and then launch the Administer TFTP function from the TFTP icon.

Maximum Parallel Sets the maximum number of concurrent sessions. The default Sessions is 75.

Log File

The log file is saved as tftpaudit.txt and stored in the NavisAccess DSL home directory. You may delete the log file if it grows very large.

Every time the TFTP Server is restarted, the tftpaudit.txt file will be saved as tftpaudit.old. Only one backup will be maintained of the log file.

NavisAccess DSL Installation and Administration Guide H-3 The TFTP Server

Port configuration

NavisAccess allows you to configure which port (other than 69) that the NavisAccess TFTP Server should use. This enables another TFTP Server, besides the NavisAccess TFTP Server, to run at the same time on one machine.

Special Note Regarding TNT “Binary Image” applet: For TNTs with 7.x and earlier versions of firmware code, the new MIB variable required to support this feature is not yet available. Therefore, the “Binary Image Upload/TNT Flash Manager” applet in NavisAccess DSL and its accompanying schedule will not work if you change our (the NavisAccess) TFTP Server port to other than 69 with 7.x and earlier code running on the TNT. This limitation does not apply to the MAX/Pipeline. The “Binary Image Upload” applet will work with any code greater than 5.x.

To Configure a port other than 69: 1 You must define the NavisAccess DSL TFTPSERVER as a service with a unique udp port in your system services file. For UNIX, the “services” file usually resides in /etc/services. For Windows®NT, the “services” file is usually found in WINNT\system32\drivers\etc. 2 Add the following line to your “services” file: na_tftp /udp where is an available (unused) port For example, the following shows typical entries from a services file: bootp 67/udp tftp 69/udp na_tftp 99/udp

Verifying the Port Number

After changing the port number, you can verify the port that NavisAccess DSL will be using. To do this: 1 Right-mouse click on the TFTP/BOOTP server icon on your desktop and select Administer TFTP. 2 Select the setup tab and there will be a grayed out field that contains the port number that has been specified by you.

H-4 NavisAccess DSL Installation and Administration Guide The TFTP Server

Configuring TFTP to work with a Network Address Translator (NAT) in a distributed NavisAccess environment

The following topic contains information on configuring NavisAccess, so TFTP communication may work properly with a NAT setup in a distributed NavisAccess environment.

How NavisAccess performs TFTP in a NAT environment

When NavisAccess performs TFTP, the following steps take place: 1 NavisAccess performs a SNMP set operation to the device (for example, a TNT) specifying its own IP address and its own TFTP port for the TFTP session. In the case of a NAT setup, the IP address specified is actually the NAT’s IP address. The IP Address is specified as the NAT’s IP address because the IP address of the NavisAccess machine may not be visible to the external NAT network. 2 The TNT device starts the TFTP session with the specified IP address and TFTP port. 3 The NAT gets the TFTP start request. The NAT uses the static mappings to translate and forward the request to the appropriate Navis Access machine. 4 NavisAccess gets the TFTP request and TFTP proceeds.

Considering the previous steps, if there is more than one NavisAccess machine behind the NAT that wants to participate in TFTP, each NavisAccess machine must have its own unique TFTP port. If every NavisAccess machine was to use the same port, the NAT could not translate the incoming request to different NavisAccess machines.

NavisAccess DSL Installation and Administration Guide H-5 The diagram below shows an example of a NAT environment that allows for a successful TFTP operation between the NavisAccess machines and the devices (for example, TNT):

The srm.ini file (as seen in the diagram) is available in the $AutoBahn directory (NavisAccess home directory) of the scheduling server and workstations. The [system] section must be updated by adding Use Alt Lookup=1, and a new section, [IP Addr Translation] must be created. Under the [IP Addr Translation] section, you will need to make an entry for each device that will require address translation.

The srm.ini file must be updated on all of the NavisAccess machines on which it exists.

For further information, and step-by-step setup, refer to “Configure TFTP to work with NAT (Distributed),” and “Configure TFTP to work with Multi-Homed NAT (Distributed),” on page G-6 and G-10, respectively, in the NavisAccess Installation and Administration Guide.

Port settings for a NAT setup

Appropriate port settings must be configured when using a NAT in a distributed NavisAccess environment. In particular, the na_tftp port setting (TFTP port) for each of the machines in the NavisAccess farm must be unique.

When a packet is sent from a TNT (on the outside of the NAT network) that is destined for a particular port inside of the NAT network, the NAT requires you to set static mappings on the NAT router which map the port to an appropriate IP address. The TFTP Server

Configure TFTP to work with NAT (Standalone)

NavisAccess provides the ability to configure the TFTP Server to work when a proxy or NAT (network address translation) is being used between NavisAccess and the Lucent device being managed by NavisAccess.

For address translation to occur, it must be enabled. Edit the srm.ini file in the NavisAccess install directory to enable this feature. 1 Stop the NavisAccess services. 2 Add the following entry in the srm.ini file, under the section labeled [system]. “Use Alt Lookup=1” Now that address translation is enabled, the address translation entries must be added to the srm.ini file. 3 Create a section labeled [IP Addr Translation] in the srm.ini file. 4 Under this section you will need to make an entry for each device that will require address translation. The entries in this section should be formatted according to the following: = where = the IP address that NavisAccess is using to manage the device(Max/TNT) where = the dynamic IP address allocated to the NAT router by the Network Access Server For example, an excerpt from a functional “srm.ini” file: [system] MemDebug= PolyStop= DiscoveryTime=14400 BoxPollInterval=240 GenerateAlarmsToNMS=1 Show NO NAME=1 Show Other Type=1 DefaultStop=1 IPAddress= HelpConfig=C:\NavisAccess\inmhelp.cfg MenuConfig=C:\NavisAccess ProgName=NavisAccess ProgLogo=NCLOGO ProgIcon=ASCEND MaxGetreqCount=50 MaxConfigFileSize=800 EnableAlarmSound=0 LaunchFirstTime=0

NavisAccess DSL Installation and Administration Guide H-7 The TFTP Server

Use Alt Lookup=1

[IP Addr Translation] 10.2.230.140=147.23.98.10 25.1.100.123=147.23.98.10 25.1.100.113=147.23.98.10 152.148.1.1=147.23.98.10 In this case, 10.2.230.140 is the IP address of the device that will be managed by NavisAccess, and 147.23.98.10 is the IP address that is assigned to the NAT router from the Network Access Server. 5 Save this file. 6 On the NAT, configuration of the Navis TFTP-port to the Navis machine IP address translation is required. 7 Restart the NavisAccess services. You can verify that the IP translation is functioning correctly by performing a TFTP operation to a device that has been entered in the ’IP Addr Translation’ portion of the srm.ini file. One TFTP operation could be a Configuration Download initiated by the device whose configuration is to be sent. note: If you stop TFTPSRV to perform configuration changes, restart the TFTPSRV using NAUTIL from the root user.

H-8 NavisAccess DSL Installation and Administration Guide The TFTP Server

Configure TFTP to work with NAT (Distributed)

For a distributed NAT, two things must be done on each machine performing TFTP in the NAT for address translation to occur: • The port must be defined, and • Translation entries must be added to the SRM.INI file.

Define the port on each machine performing TFTP in the NAT 1 You must define the NavisAccess TFTPSERVER as a service with a unique udp port in your system services file. For UNIX, the "services" file usually resides in /etc/services. For Windows NT, the "services" file is usually found in WINNT\system32\drivers\etc. 2 Add the following line to your "services" file: na_tftp /udp where is an available (unused) port Example: the following shows typical entries from a services file: bootp 67/udp tftp 69/udp na_tftp 99/udp

Add translation entries to the SRM.INI file on each machine performing TFTP in the NAT

NavisAccess DSL Installation and Administration Guide H-9 The TFTP Server

For example, an excerpt from a functional “srm.ini” file: [system] MemDebug= PolyStop= DiscoveryTime=14400 BoxPollInterval=240 GenerateAlarmsToNMS=1 Show NO NAME=1 Show Other Type=1 DefaultStop=1 IPAddress= HelpConfig=C:\NavisAccess\inmhelp.cfg MenuConfig=C:\NavisAccess ProgName=NavisAccess ProgLogo=NCLOGO ProgIcon=ASCEND MaxGetreqCount=50 MaxConfigFileSize=800 EnableAlarmSound=0 LaunchFirstTime=0 Use Alt Lookup=1 [IP Addr Translation] 10.2.230.140=147.23.98.10 25.1.100.123=147.23.98.10 25.1.100.113=147.23.98.10 152.148.1.1=147.23.98.10 In this case, 10.2.230.140 is the IP address of the device that will be managed by NavisAccess, and 147.23.98.10 is the IP address that is assigned to the NAT router from the Network Access Server. 6 Save this file. 7 On the NAT, configuration of the Navis TFTP-port to the Navis machine IP address translation is required. 8 Restart the NavisAccess services. You can verify that the IP translation is functioning correctly by performing a TFTP operation to a device that has been entered in the 'IP Addr Translation' portion of the srm.ini file. One TFTP operation could be a Configuration Download initiated by the device whose configuration is to be sent.

H-10 NavisAccess DSL Installation and Administration Guide The TFTP Server

Configure TFTP to work with Multi-homed NAT (Standalone)

NavisAccess provides the ability to configure the TFTP Server to work when one or more proxy or NAT (network address translation) is being used between NavisAccess and the Lucent device being managed by NavisAccess.

For address translations to occur, they must be enabled. To do this, file mapping must be done to all NASes to their respective NAT address. Edit the srm.ini file in the NavisAccess install directory to enable this feature. 1 Stop the NavisAccess services. 2 Add the following entry in the srm.ini file, under the section labeled [system]. “Use Alt Lookup=1” Now that address translation is enabled, the address translation entries must be added to the srm.ini file. 3 Create a section labeled [IP Addr Translation] in the srm.ini file. 4 Under this section you will need to make an entry for each device that will require address translation and it’s corresponding NAT IP address. In the multi-homed NAT system, you will have multiple NATs (network address translation) being used between NavisAccess and the Lucent device being managed by NavisAccess. The entries in this section should be formatted according to the following: = where = the IP address that NavisAccess is using to manage the device(Max/TNT) where = the dynamic IP address allocated to the respective NAT router by the Network Access Server For example, an excerpt from a functional “srm.ini” file: [system] MemDebug= PolyStop= DiscoveryTime=14400 BoxPollInterval=240 GenerateAlarmsToNMS=1 Show NO NAME=1 Show Other Type=1 DefaultStop=1 IPAddress= HelpConfig=C:\NavisAccess\inmhelp.cfg MenuConfig=C:\NavisAccess ProgName=NavisAccess ProgLogo=NCLOGO ProgIcon=ASCEND MaxGetreqCount=50 MaxConfigFileSize=800

NavisAccess DSL Installation and Administration Guide H-11 The TFTP Server

EnableAlarmSound=0 LaunchFirstTime=0 Use Alt Lookup=1 [IP Addr Translation] 10.2.230.140=147.23.98.10 25.1.100.123=147.23.98.10 25.1.100.113=141.25.91.12 152.148.1.1=141.25.91.12 In this case, 10.2.230.140 is the IP address of device1that will be managed by NavisAccess, and 147.23.98.10 is the IP address that is assigned to the NAT1 router from the Network Access Server. 25.1.100.123 is the IP address of device2 that will be managed by NavisAccess, and 147.23.98.10 is the IP address that is assigned to the NAT1 router from the Network Access Server. 25.1.100.113 is the IP address of device X1, and 141.25.91.12 is the IP address that is assigned to the NAT2 router from the Network Access Server. And 152.148.1.1 is the IP Address of deviceX2, which is also connected to NAT2. 5 Save this file. 6 On the NAT, configuration of the Navis TFTP-port to the Navis machine IP address translation is required. 7 Restart the NavisAccess services. You can verify that the IP translation is functioning correctly by performing a TFTP operation to a device that has been entered in the ’IP Addr Translation’ portion of the srm.ini file. One TFTP operation could be a Configuration Download initiated by the device whose configuration is to be sent. note: If you stop TFTPSRV to perform configuration changes, restart the TFTPSRV using NAUTIL from the root user.

Configure TFTP to work with Multi-homed NAT (Distributed)

NavisAccess provides the ability to configure the TFTP Server to work when one or more proxy or NATs (network address translation) is being used between NavisAccess and the Lucent device being managed by NavisAccess.

For distributed NATs, two things must be done on each machine performing TFTP in each NAT for address translation to occur: • The port must be defined, and • Translation entries must be added to the SRM.INI file.

H-12 NavisAccess DSL Installation and Administration Guide The TFTP Server

Example: the following shows typical entries from a services file: bootp 67/udp tftp 69/udp na_tftp 99/udp

Add translation entries to the SRM.INI file on each machine performing TFTP in the NAT

For address translation to occur, it must be enabled. Edit the srm.ini file in the NavisAccess install directory to enable this feature. 3 Stop the NavisAccess services. 4 Add the following entry in the srm.ini file, under the section labeled [system]. “Use Alt Lookup=1” Now that address translation is enabled, the address translation entries must be added to the srm.ini file. 5 Create a section labeled [IP Addr Translation] in the srm.ini file. Under this section you will need to make an entry for each device that will require address translation. The entries in this section should be formatted according to the following: = where = the IP address that NavisAccess is using to manage the device(Max/TNT) where = the dynamic IP address allocated to the NAT router by the Network Access Server For example, an excerpt from a functional “srm.ini” file: [system] MemDebug= PolyStop= DiscoveryTime=14400 BoxPollInterval=240 GenerateAlarmsToNMS=1 Show NO NAME=1 Show Other Type=1 DefaultStop=1 IPAddress= HelpConfig=C:\NavisAccess\inmhelp.cfg MenuConfig=C:\NavisAccess ProgName=NavisAccess ProgLogo=NCLOGO ProgIcon=ASCEND MaxGetreqCount=50 MaxConfigFileSize=800

NavisAccess DSL Installation and Administration Guide H-13 The TFTP Server

EnableAlarmSound=0 LaunchFirstTime=0 Use Alt Lookup=1 [IP Addr Translation] 10.2.230.140=147.23.98.10 25.1.100.123=147.23.98.10 25.1.100.113=112.3.69.36 152.148.1.1=112.3.69.36 In this case, 10.2.230.140 is the IP address of the device that will be managed by NavisAccess, and 147.23.98.10 is the IP address that is assigned to the NAT router from the Network Access Server. 6 Save this file. 7 On the NAT, configuration of the Navis TFTP-port to the Navis machine IP address translation is required. 8 Restart the NavisAccess services. You can verify that the IP translation is functioning correctly by performing a TFTP operation to a device that has been entered in the ’IP Addr Translation’ portion of the srm.ini file. One TFTP operation could be a Configuration Download initiated by the device whose configuration is to be sent.

H-14 NavisAccess DSL Installation and Administration Guide Copying Device Templates and Files

The following section describes how to copy DSL Provisioning Templates, Master List files, and Device Configuration files. Thus, effectively recreating an existing NavisAccess farm on a new NavisAccess installation. The files/templates may be used in another installation of NavisAccess if they are copied into the same directory in the second NavisAccess installation.

Reusing Provisioning templates

All template files are stored in the $AutoBahn/dslmanagement directory with a .defaults extension. For example, the default SDSL templates are named sdsl.defaults.

Copying templates

To copy the templates from one machine to another: • Copy $AutoBahn/dslmanagement/*.defaults from the first machine to the $AutoBahn/dslmanagement directory on the second machine. Note: Copying templates with the same name from one machine to another will result in the original templates being overwritten. The overwritten templates will be lost.

Reusing Master List files

Master List files are stored in the directory chosen at the time of export. For further information, refer to Chapter 7, “The Master List” in the NavisAccess DSL Installation and Administration Guide.

Copying Master List files

To copy the Master List files from one machine to another: • Copy /*.* from the first machine to the directory on the second machine. Note: Copying Master List files with the same name from one machine to another will result in the original Master List files being overwritten. The overwritten Master List files will be lost.

NavisAccess DSL Installation and Administration Guide I-1 Copying Device Templates and Files Reusing the Device Configuration files

Reusing the Device Configuration files

The Device Configuration files are stored in the directory chosen at the time of export. For further information, refer to Chapter 14, “Device Management: Configuration Tools” in the NavisAccess DSL User’s Guide.

Copying Device Configuration files

To copy the Device Configuration files from one machine to another: • Copy /*.* from the first machine to the directory on the second machine.

Note: Copying Device Configuration files with the same name from one machine to another will result in the original Device Configuration files being overwritten. The overwritten Device Configuration files will be lost.

I-2 NavisAccess DSL Installation and Administration Guide License agreement

MINIMUM END USER LICENSE TERMS

License. The term "Software" includes all Lucent and third party ("Supplier") software provided to you with this Lucent product, and includes any accompanying documentation (the "Documentation"). The term "Software" also includes any updates of the Software provided to you by Lucent at its option. Subject to the terms of this Agreement, Lucent grants to you, and you accept, a personal, non-exclusive, and nontransferable (except as set forth below) license to use the object code version of the Software on a single computer. The Software is "in use" on a computer when it is loaded into the temporary memory (i.e. RAM) or installed into the permanent memory (e.g. hard drive, CD-ROM or other storage device) of that computer, except that a copy installed on a network server for the sole purpose of distribution to other computers is not "in use". If you permanently install the Software on the hard disk or other storage device of a computer (other than a network server) and you use that computer more than 80% of the time it is in use, then you may also use the Software on a portable or home computer. You may make a reasonable number of copies of the Software and Documentation for backup or archival purposes only, so long as Lucent’s and its licensors copyright notices are reproduced on such copies.

Limitations on Use. You may not copy, rent, lease, sell, sublicense, assign, loan, time-share or otherwise transfer or distribute copies of the Software or Documentation to others, except as set forth in this agreement. You may physically transfer the Software from one computer to another provided that you do not retain any copies of the Software, including any copies stored on a computer. You may permanently transfer this license to another user, but only if you transfer or destroy all copies of the Software and Documentation, and the recipient agrees in writing to be bound by all of the terms of this agreement.

You agree that you will not decompile, disassemble, or otherwise reverse engineer the Software, and you will use your best efforts to prevent your employees and contractors from doing so, except to the extent that such restriction is expressly prohibited by applicable law. You may not modify, adapt, create a derivative work, merge, or translate the Software or the Documentation without the prior written consent of Lucent.

Specific Suppliers may be identified in the Documentation. You agree to any additional terms and conditions specific to particular Suppliers or Products, as described in the Documentation, which are incorporated herein by reference.

NavisAccess DSL Installation and Administration Guide J-1 License agreement

Intellectual Property Rights. You acknowledge that Lucent or its Suppliers retain exclusive ownership of all copyrights, trademarks, patents and/or other intellectual property rights in the Software and the Documentation. You are not granted any rights in the Software or Documentation other than the license rights expressly set forth above.

Term and Termination. The term of this license is for the duration of any copyright in the Software. This license automatically terminates if you fail to comply with any of the terms and conditions of this agreement. You agree that, upon such termination, you will either destroy (or permanently erase) all copies of the Software and Documentation, or return the original Software and Documentation to Lucent. You may terminate this license at any time by destroying the Software and Documentation and any permitted copies.

Limited Warranty and Limited Remedy. Lucent warrants to the original end user purchaser only that the Software as delivered at the time of purchase will substantially conform to the Documentation, and that the original diskettes and Documentation are free from defects in material and workmanship under normal use, for a period of ninety (90) days from the original end user’s purchase thereof (the "Limited Warranty Period"), provided the Software is used with compatible computer hardware and operating systems. This limited warranty is void if failure of the Software has resulted from accident, abuse, or misapplication. Lucent’s entire liability, and your sole and exclusive remedy shall be, at Lucent’s option, either to (a) correct or help you work around or avoid a reproducible Error, (b) replace defective diskettes or Documentation or (c) authorize a refund, so long as the Software and Documentation are returned with a copy of your receipt within ninety (90) days of your date of purchase together with a brief written statement describing the alleged Error. An "Error" is a defect in the Software that causes it not to perform substantially in accordance with the limited warranty set forth above. Any replacement Software or Documentation will be warranted for the remainder of the original warranty period only.

No Liability of Suppliers. You acknowledge that your rights under this Agreement, in the nature of warranty or otherwise, are solely against Lucent. NO SUPPLIER MAKES ANY WARRANTY, ASSUMES ANY LIABILITY, OR UNDERTAKES TO FURNISH TO YOU ANY SUPPORT OR INFORMATION CONCERNING PRODUCTS OR ANY PORTION OF PRODUCTS. You hereby release all Suppliers from any claims, damages or losses arising from the use of Products, regardless of the form of action.

Disclaimer of Warranties. EXCEPT AS SPECIFICALLY PROVIDED ABOVE, THE SOFTWARE AND THE DOCUMENTATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. ALL OTHER WARRANTIES ARE DISCLAIMED, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT OR THAT THE SOFTWARE’S FUNCTIONS WILL MEET YOUR REQUIREMENTS OR THAT ITS OPERATION WILL BE UNINTERRUPTED OR ERROR FREE. EXCEPT AS SET FORTH IN THIS AGREEMENT, THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE AND THE DOCUMENTATION IS WITH YOU. IF THEY PROVE DEFECTIVE AFTER THEIR PURCHASE, YOU, AND NOT LUCENT OR ITS SUPPLIERS, ASSUME THE ENTIRE COST OF SERVICE OR

J-2 NavisAccess DSL Installation and Administration Guide License agreement

REPAIR. If a disclaimer of implied warranties is not permitted by law, the duration of any such implied warranty is limited to ninety (90) days from the date of purchase by the original end user purchaser. Some jurisdictions do not allow the exclusion of implied warranties or limitations on how long an implied warranty may last, so such limitations or exclusions may not apply to you. This limited warranty gives you specific legal rights, and you may also have other rights which vary from jurisdiction to jurisdiction.

Liability Exclusions and Limitations. IN NO EVENT SHALL LUCENT OR ANY SUPPLIER BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS, LOSS OF USE OR INTERRUPTION OF BUSINESS), OR FOR LEGAL FEES, ARISING OUT OF THE USE OF THE SOFTWARE OR THE DOCUMENTATION, REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT PRODUCT LIABILITY OR OTHERWISE, EVEN IF LUCENT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL LUCENT’S AGGREGATE LIABILITY FOR ANY CLAIM EXCEED THE LICENSE FEE PAID BY YOU. This limitation shall apply notwithstanding any failure or inability to provide the limited remedies set forth above. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation(s) or exclusion(s) may not apply to you.

Proprietary Rights-Contracts with Certain U.S. Government Agencies. If the Software is acquired under the terms of a Department of Defense or civilian agency contract, the Software is "commercial item" as that term is defined at 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation" as such terms are used in 48 C.F.R. 12.212 of the Federal Acquisition Regulations and its successors and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995) of the DoD FAR Supplement and its successors. All U.S. Government end users acquire the Software and the Documentation with only those rights set forth in this agreement.

Export Restrictions. You acknowledge that the laws and regulations of the United States restrict the export and re-export of certain commodities and technical data of United States origin, including the Software and the Documentation, in any medium. You agree that you will not knowingly, without prior authorization if required, export or re-export the Software or the Documentation in any medium without the appropriate United States and foreign government licenses.

Severability. You acknowledge and agree that each provision of this agreement that provides for a disclaimer of warranties or an exclusion or limitation of damages represents an express allocation of risk, and is part of the consideration of this agreement. Invalidity of any provision of this Agreement shall not affect the validity of the remaining provisions of this Agreement.

NavisAccess DSL Installation and Administration Guide J-3 License agreement

General. This Agreement is the entire agreement between you and Lucent relative to the Software and Documentation, and supersedes all prior written statements, proposals or agreements relative to its subject matter. It may be modified only by a writing executed by an authorized representative of Lucent. No Lucent dealer or sales representative is authorized to make any modifications, extensions or additions to this agreement. This Agreement is governed by the laws of the State of California as applied to transactions taking place wholly within California between California residents, without application of its conflicts of law principles. The United Nations Convention on Contracts for the International Sale of Goods is specifically excluded from application to this Agreement.

If you have any questions, write or call Lucent Technologies, 1701 Harbor Bay Parkway, Alameda, CA 94502.

J-4 NavisAccess DSL Installation and Administration Guide Index

A standalone 2-1, 3-1 steps 2-7, 3-13 Audit Trails Workstation 2-14, 3-23 overview 5-24 Workstations use of 5-24, 5-25 MIB compilation 2-17, 3-26

B E

Backing up the database 7-3 error messages, Navis Device License Manager 9-18

C G

Configuring Generating ports H-4 fresh database 7-8 Master List 8-16

D I Database maintenance 7-2 Clear Map Flags 7-3 Installation database back-up 7-3 Distributed database repairing 7-10 component description 2-5 database restoration 7-5 Distribution plan 2-3 fresh database 7-8 prerequisites 2-3 moving database files 7-10 steps 2-7, 3-13 Workstation MIB compilation 2-17, 3-26 workstation prerequisites 7-13 Distributed prerequisites 2-6, 3-12 Device discovery 6-2 standalone 1-1 automatic 6-5 prerequisites 1-1 generating Master List 6-5 system requirements 1-3, 3-5 manual 6-4 Installation Distributed Master List 6-5 prerequisites 2-1, 3-1 running Explorer 6-6 the Explorer 6-5 Installation types xiii visual indicators 6-2 device license request file generating 9-6 L device licenses, updating 9-3 license options 9-2 Distributed installation component description 2-5 distributing components 2-4 Distribution plan 2-3 M distribution plan 2-3 File maintenance notes C-1 Master 8-26 prerequisites 2-1, 2-3, 2-6, 3-1, 3-4, 3-12 Master List

NavisAccess Installation and Administration Guide Index-1 Index N

Circuit Status 8-15 software options 9-2 configurator 8-17 Standalone installation Entries 8-4, 8-5, 8-7 LAN B-1 format 8-3, 8-4, 8-6, 8-7 prerequisites 1-1 generation 8-16 system requirements 1-3, 3-5 importing options 8-18, 8-20 Starting processing rules 8-9, 8-10 Solaris standalone 1-7, 2-17, 3-11, 3-26 types of 8-2 Moving database files 7-10 Multiple server farms on same LAN D-1 T

Templates N reusing I-1 TFTP Navis Device License Manager configuration advanced options,setting 9-5 using a proxy H-7, H-11 Apply Device Licenses screen 9-11 Trap forwarding A-1 error messages 9-18 Types of installation xiii launching 9-4 response file error messages 9-20 Navis Device License Manager (NDLM) 9-2 U

User Groups P predefined 5-3 Users Partial Master List 8-9 predefined 5-2 Port configuration H-4

Repairing a database 7-10 response file error messages 9-20 Restoring the database 7-5

Security 5-2 adding a new user group 5-19 Administrator user group 5-11 Data Access 5-2, 5-19 rights 5-18 defining a user 5-15 group membership 5-16 edit user 5-13 group membership 5-14 editing group membership 5-13 user group 5-17 Feature Access 5-2 predefined user groups 5-3 predefined users 5-2 SNMP access xiv

Index-2 NavisAccess Installation and Administration Guide