NavisAccess Installation and Administration Guide
Part Number: 7820-0387-004 For software version 6.0 May 2001 Copyright © 2001 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.
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
4ESS, 5ESS, 7R/E, AnyMedia, APX 8000, AQueView, B-STDX 8000, B-STDX 9000, CaseView, CBX 500, CellPipe, ChoiceNet, ClearReach, ComOS, cvMAX, DACS, DACSmate, Datakit, DDM 2000FiberReach, DSLMAX, DSLPipe, DSL Terminator, DSLPipe, DSLTNT, elemedia, elemedia Enhanced, EMMI, GRF, GX 550, HyperPATH, Inferno, InfernoDesign, IntragyAccess, IntragyCentral, IP Navigator, IPWorX, LineReach, LinkReach, MAX, MAXENT, MAX TNT, Metropolis, MetroView, Multiband, MultiLink Protocol Plus, MultiVoice, MultiVPN, Navis, NavisRadius, NetCare, NetLight, NetPartner, NetworkCare, NX64000, OneVision, Open Systems Innovations, OpenTrunk, PacketStar, PathStar, Pinnacle, Pipeline, PortMaster, QVPN, QVPN Builder, SecureConnect, Series56, SmoothConnect, SpringTide, Stinger, SuperLine, SuperPipe, SYSTIMAX, True Access, WaveLAN, WaveMANAGER, WaveMODEM, and WebXtend are trademarks of Lucent Technologies Inc. eSight is a service mark of Lucent Technologies Inc. Other trademarks, service marks, and trade names mentioned in this publication belong to their respective owners.
Copyrights for Third-Party Software Included in Lucent Access Networks Software Products
C++ Standard Template Library software copyright© 1994 Hewlett-Packard Company and copyright© 1997 Silicon Graphics. Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Neither Hewlett-Packard nor Silicon Graphics makes any representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.
Berkeley Software Distribution (BSD) UNIX software copyright© 1982, 1986, 1988, 1993 The Regents of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer. 2. Redistributions in binary form must reproduce the above copy- right notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the Univer- sity of California, Berkeley, and its contributors. 4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Ordering Information
You can order the most up-to-date product information and computer-based training online at http://www.lucent.com/ins/bookstore.
Feedback
Lucent Technologies appreciates your comments, either positive or negative, about this manual. Please send them to [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 eSight™ Service Center at http://www.esight.com.
The eSight 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 eSight Service Center at http://www.esight.com provides access to technical support. You can obtain technical assistance through email or the Internet, or by telephone. If you need 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 an eSight Live chat. Select one of these sites when you log in to http://www.esight.com.
Calling the technical assistance center (TAC)
If you cannot find an answer through the tools and information on eSight or if you have a very urgent need, contact TAC. Access the eSight Service Center at http://www.esight.com and click Contact Us below the Lucent Technologies logo for a list of telephone numbers inside and outside the United States.
You can alternatively call 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 Installation and Administration Guide iii
Contents
Customer Service ...... iii
About This Guide...... xi About NavisAccess...... xi What is in this guide...... xi Documentation conventions...... xi Documentation set...... xii
Read Me First ...... xiii Preparing for installation...... xiii Determining your Installation type ...... xiii Upgrading NavisAccess from a version prior to 5.0 ...... xiv Upgrading NavisAccess from version 5.0.x...... xv Configuring a firewall in the NavisAccess network...... xv Protocols and ports to open on the firewall ...... xvi Client / Managed Devices communication...... xviii Server / Managed Devices communication ...... xix Providing SNMP access for all NavisAccess servers and workstations...... xx SNMP access to Lucent devices...... xx NavisAccess UDP ports...... xxi System requirements...... xxii Operating System Requirements ...... xxiii NavisAccess server and workstation configuration information ...... xxiv
Chapter 1 Stand-alone Installation...... 1-1 Getting ready to install: Things to know...... 1-1 System requirements...... 1-3 NavisAccess installation step summary: Solaris Stand-alone ...... 1-3 Installation Checklist for NavisAccess 6.0 on Solaris ...... 1-3 Part 1: Ready Solaris Machines...... 1-3 Part 2: Install NavisAccess & Configure NavisAccess System Settings...... 1-4 Part 3: Configure Lucent Remote Access Servers to work with NavisAccess...... 1-5 After installing NavisAccess 6.0 ...... 1-5 NavisAccess stand-alone installation...... 1-6 Before You Run NavisAccess for the first time ...... 1-9 Starting NavisAccess ...... 1-10
Chapter 2 Distributed Installation ...... 2-1 Getting ready to install: Things to know...... 2-1 System requirements...... 2-3 Prerequisites for distributed installation ...... 2-3 The Distribution Plan...... 2-3 Assessing the relative power rating ...... 2-3 NavisAccess component distribution...... 2-4 Installation Checklist for NavisAccess 6.0 on Solaris ...... 2-7 Part 1: Ready Solaris Machines...... 2-7 Part 2: Install NavisAccess and Configure System Settings...... 2-8 Part 3: Configure Lucent Remote Access Servers to work with NavisAccess...... 2-9 After installing NavisAccess 6.0 ...... 2-10 Primary server installation and creation of Distribution Plan...... 2-11
NavisAccess Installation and Administration Guide v Contents
Secondary server installation ...... 2-16 Workstation installation ...... 2-17 Additional Steps...... 2-19 Starting NavisAccess ...... 2-20 Starting NavisAccess as a non-root user ...... 2-21
Chapter 3 Preparing Lucent devices for use with NavisAccess...... 3-1 Preparing Lucent devices for use with NavisAccess (TAOS 8.x) ...... 3-1 The Network Management Enable software option ...... 3-1 Call-Logging and SNMPv3 restrictions in TAOS 8.x...... 3-1 MAX preparation ...... 3-2 Configuring SNMP Trap destinations for the MAX (TAOS 8.x) ...... 3-2 Setting SNMP community strings for the MAX (TAOS 8.x) ...... 3-3 Setting SNMP v3 for the MAX (TAOS 8.x) ...... 3-4 Enabling Call-Logging on the MAX (TAOS 8.x)...... 3-5 Configuring SNMP security on the MAX (TAOS 8.x)...... 3-7 Configure new NASportID (TAOS 8.x)...... 3-8 MAX TNT preparation ...... 3-9 Configuring SNMP Trap destinations for the TNT and APX 8000 (TAOS 8.x) ...... 3-9 Enabling SNMP, community strings on the TNT and APX 8000 (TAOS 8.x) .... 3-10 Setting SNMPv3 for the TNT and APX 8000 (TAOS 8.x)...... 3-12 Enabling Call Logging on the TNT and APX 8000 (TAOS 8.x) ...... 3-13 Configure NAS port ID format (TAOS 8.x)...... 3-16 Configuring a Global IP address on TNT and APX 8000 (TAOS 8.x)...... 3-16 Installing the hash codes...... 3-17 Preparing Lucent devices for use with NavisAccess (TAOS 9.0) ...... 3-18 About the NavisAccess Software Option ...... 3-18 Enabling SNMP v1 and configuring SNMP parameters on the TNT and APX8000 (TAOS 9.0)...... 3-19 Configuring SNMP v1 trap destinations for the TNT and APX8000 (TAOS 9.0) ...... 3-21 Enabling SNMP v3 and configuring SNMP parameters on the TNT and APX8000 (TAOS 9.0)...... 3-23 Creating an SNMP v3 user profile for the TNT and APX8000 (TAOS 9.0) ...... 3-25 Creating an SNMP v3 trap notifications profile for the TNT and APX8000 (TAOS 9.0)...... 3-26 Creating an SNMP v3 target profile for the TNT and APX8000 (TAOS 9.0)...... 3-27 Configuring SNMP v3 trap destinations for the TNT and APX8000 (TAOS 9.0) 3-28 Configuring a Soft IP address on the APX8000 (TAOS 9.0)...... 3-30 Enable call logging on the TNT and APX8000 (TAOS 9.0)...... 3-31 Enable call-logging for evaluation purposes (TAOS 9.0) ...... 3-34 Setting SNMP community strings for the MAX (TAOS 9.0) ...... 3-35 Enable Call-Logging on the MAX (TAOS 9.x) ...... 3-36 Configuring trap destinations for the MAX (TAOS 9.0) ...... 3-37 Setting SNMP v3 for the MAX (TAOS 9.0) ...... 3-39 Configuring SNMP Security on the MAX (TAOS 9.0) ...... 3-40 Configure New NASportID (TAOS 9.0)...... 3-41 Converting Call Logging files to comma-separated Variable (CSV) Files...... 3-41 CLD2CSV command-line utility...... 3-41 How CLD2CSV converts call-logging files...... 3-41 Modifying the cld2csv.ini file ...... 3-42 Output of the converted call-logging files...... 3-43 Converting your .cld files ...... 3-43 vi NavisAccess Installation and Administration Guide Contents
Chapter 4 Device Discovery ...... 4-1 Introduction to device Discovery...... 4-1 Visual indicators for Discovery ...... 4-2 Automatic Discovery of network resources...... 4-3 Networks that Do Not Support SNMP ...... 4-3 Using NavisAccess for the first time ...... 4-3 Configuring the DNIS Translation table...... 4-3 Using the DNIS Translation table ...... 4-4 Changing the DNIS default minimum length...... 4-5 Manual Discovery...... 4-5 Manually adding new devices...... 4-5 Discovery via the Master List ...... 4-6 The Master List...... 4-6 Generating a Master List ...... 4-6 ML Config Launch options ...... 4-7 Discovery using SNMP exploration ...... 4-8 Running the Explorer...... 4-8 Troubleshooting/restarting Discovery...... 4-10 Why did Discovery fail? ...... 4-10 Identifying an unknown device...... 4-10 To restart Discovery of a device ...... 4-10 To restart Discovery of multiple devices...... 4-11
Chapter 5 Security...... 5-1 Security in NavisAccess...... 5-1 Users and user groups ...... 5-2 Pre-defined users...... 5-2 Pre-defined user groups ...... 5-2 Working with access rights...... 5-3 Pre-defined user group access rights ...... 5-4 Pre-defined user group permissioned features and functions...... 5-5 Pre-defined user group permissioned operations...... 5-9 User Manager...... 5-11 Edit user ...... 5-11 Edit user: group membership...... 5-12 Define a new user ...... 5-13 Define user: group membership ...... 5-14 Edit an existing user group ...... 5-15 Edit user group: data access...... 5-15 Edit user group: Feature Access ...... 5-16 Define a new user group...... 5-17 Define user group: data access ...... 5-17 Define user group: feature access...... 5-18 Logging out of NavisAccess...... 5-19 Logging into NavisAccess ...... 5-19 Change password ...... 5-20 Audit Trails ...... 5-21 Using the Audit Trails applet...... 5-22 vii NavisAccess Installation and Administration Guide Contents
Chapter 6 Database Maintenance ...... 6-1 Database tools ...... 6-1 Clear Map Flags...... 6-2 Backing-up the database ...... 6-2 Restoring the database ...... 6-4 Generating a fresh database ...... 6-6 Repairing a database ...... 6-8 Moving DB files ...... 6-8 Workstation prerequisites for Restore and Move options ...... 6-11 Backing-up the database without DBMaint...... 6-12 The cfgdbcron.ksh utility - Scheduling a database backup ...... 6-12 The db_backup utility ...... 6-14 db_backup syntax ...... 6-15
Chapter 7 The Master List...... 7-1
Overview...... 7-1 Types of Master Lists ...... 7-1 Processing the Master List ...... 7-2 Master List format ...... 7-2 Validation of information in the Master List...... 7-3 Processing a partial Master List...... 7-4 Rules for processing the Master List ...... 7-4 Logging the progress Information ...... 7-5 Circuit status ...... 7-6 Actions to be taken when circuit status changes ...... 7-6 Device and interface status relationship ...... 7-7 The Master List Configurator (MLConfig)...... 7-7 Starting MLConfig from the command line ...... 7-8 Importing the Master List...... 7-8 MLConfig Command Line Options - Import ...... 7-8 Exporting the NavisAccess database...... 7-10 MLConfig Command Line Options - Export ...... 7-11 Creating a Master List from scratch...... 7-11 Generating the Master List using the MLConfig Launch Options Dialog ...... 7-12 Exporting the Master List ...... 7-12 Importing the Master List ...... 7-12 Import options...... 7-13
Chapter 8 Navis Device License Manager (NDLM)...... 8-1
Introduction...... 8-1 What are device licences? ...... 8-1 How Device Licences are updated...... 8-2 Who should use NDLM? ...... 8-3 Directory Structure ...... 8-3 Launching the NDLM...... 8-3 Setting the Advanced options ...... 8-5 Generating a Device License request file ...... 8-6 Step 1 ...... 8-6 Forwarding the request file...... 8-8 Processing the response file ...... 8-9 viii NavisAccess Installation and Administration Guide Contents
Step 2 ...... 8-9 Receiving a response file Customer Service ...... 8-9 Applying the license response file ...... 8-10 Reprocessing a file ...... 8-14 Log file samples...... 8-14 The request log file ...... 8-15 The response log file...... 8-16 NDLM Error Messages...... 8-17 Response File...... 8-20
Appendix A Configuring Trap Forwarding ...... A-1
Appendix B Multiple Standalone Installations on the Same LAN ...... B-1
Appendix C Workstation Installation on a Separate Subnet...... C-1
Determining the osangent port...... C-1 Determining the Primary Server DBServer name ...... C-1
Appendix D File Maintenance Notes...... D-1
Appendix E Uninstalling NavisAccess ...... E-1
Appendix F The nautil Utility...... F-1
Using the nautil utility ...... F-1 The nastatus utility...... F-2 Using the nastatus utility...... F-2
Appendix G The TFTP Server ...... G-1
NavisAccess TFTP Server Setup tab ...... G-2 Disabling the TFTP Server ...... G-3 Port configuration ...... G-3 Configure TFTP to work with NAT (Standalone)...... G-4 Configure TFTP to work with NAT (Distributed) ...... G-6 Configure TFTP to work with Multi-homed NAT (Standalone) ...... G-8 Configure TFTP to work with Multi-homed NAT (Distributed) ...... G-9
Appendix H Setting NavisAccess Database Cache Size...... H-1
Appendix I Changing Host Machine Identifying Parameters ...... I-1
Appendix J Configuring Printing...... J-1
Configuring Solaris...... J-1 Configuring printing within NavisAccess ...... J-1 Distributed Servers ...... J-2
Appendix K License agreement ...... K-1 ix NavisAccess Installation and Administration Guide
About This Guide
About NavisAccess
NavisAccess™ network management software is the next generation tool for managing carrier networks, Points of Presence (POPs) and enterprise networks. It is the only end-to-end, solution designed specifically for ISPs, carriers and corporations who need to support a variety of network access devices and services. Features such as discovery and mapping, configuration management, performance measurement and fault monitoring provide customized information about the network -- ranging from the “big picture” view of the enterprise to the details about the performance on a single modem port. Among the features of NavisAccess are: • AccessWatch, the first and only software solution that summarizes key remote access operating parameters for elements and groups of elements. • Enterprise-wide discovery and mapping. • Centralized, remote management of devices and device groups, including chassis, software and configuration file change control. • An extensive suite of performance management tools. Fault detection tools that continually monitor all aspects of the network.
For a complete discussion of NavisAccess features, consult the NavisAccess User Guide (available both online and in printed form) or the NavisAccess online help.
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 Represents characters that you enter exactly as shown (unless the characters are monospace 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.
NavisAccess Installation and Administration Guide xi About This Guide Documentation set
Convention Meaning 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 Control 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.
! Warns that a failure to take appropriate safety precautions could result in Warning: physical injury.
Warns of danger of electric shock. Warning:
Documentation set
Guide Description NavisAccess User’s Guide This manual describes and explains all NavisAccess options, utilities and functions, and how to use them NavisAccess Operations Guide This guide explains NavisAccess options from a operator’s point of view.
xii NavisAccess Installation and Administration Guide Read Me First
Preparing for installation
There are several factors to consider before installing NavisAccess version 6.0. They are: • Determining the type of installation: stand-alone or distributed. • Understanding the consequences of upgrading from a previous version of NavisAccess. • Configuring a firewall (if applicable) in the NavisAccess network. • Providing proper SNMP access for all NavisAccess servers and workstations.
Each of these topics is explained below.
Determining your Installation type
Before installing NavisAccess, you must determine the proper type of installation for your needs.
Installation types
NavisAccess can be installed as a stand-alone 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 stand-alone or distributed system on the same LAN, please refer to “Multiple Standalone Installations on the Same LAN” on page B-1. • Stand-alone installation In a stand-alone configuration, one machine provides both server and client functionality. All components are installed on a single machine. However, X-term, and Telnet sessions can be run off of a stand-alone 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 X-term 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
NavisAccess Installation and Administration Guide xiii Read Me First Preparing for installation
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. – 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.
Changing from stand-alone installation to a Distributed installation
NavisAccess provides the ability for you to use your stand-alone server as part of the Distributed installation as follows: • Using the stand-alone server as the Primary server - You can install NavisAccess on top of the stand-alone installation. In a Distributed installation, the Primary server contains the Database server component which already resides on the stand-alone server machine. • Using the stand-alone server as a Secondary server - You must completely uninstall NavisAccess from the stand-alone machine before beginning the Distributed installation if you are using the stand-alone machine as a Secondary server in the Distributed installation.
Upgrading NavisAccess from a version prior to 5.0
If you are upgrading NavisAccess from a version prior to 5.0, you must completely uninstall NavisAccess and then install NavisAccess 6.0. Please refer to Appendix E, “Uninstalling NavisAccess”. Please refer to the NavisAccess User’s Guide for version 4.3 for detailed un-install instructions for NavisAccess 4.3.
The database format of NavisAccess version 4.3 or earlier is not compatible with version 5.0 or later. Therefore, you cannot reuse any data collected by versions of NavisAccess prior to 5.0.
For this reason, you may want to maintain your NavisAccess 4.3 system for a time after installing 6.0 in order to have access to the historical data.
Note: If you decide to maintain your NavisAccess 4.3 system, you must maintain it on a different machine from NavisAccess 6.0.
xiv NavisAccess Installation and Administration Guide Read Me First Preparing for installation
Upgrading NavisAccess from version 5.0.x
When upgrading your system from version 5.0 to 6.0 it is highly recommended that you upgrade your system(s) to Solaris 2.8 as NavisAccess 6.0 has been fully qualified on the current Solaris platform which is 2.8. The upgrade procedure is as follows: 1 Back up your database. It is recommended that you backup your database locally and remotely - in case of unforeseen events. The backup partition should have at least 20GB.
Begin the upgrade to Solaris 2.8. Preserve the slices you wish and patch OS. This install/upgrade will erase your current Navis installation. You may obtain the patches at: http://www.esight.com/. Please refer to the Release Notes for the latest patch information. 2 Re-install your current version of Navis (5.0.x) 3 Upgrade to the service pack you had earlier. 4 Stop all services after service pack installation. 5 Reinstall the database, remembering to run ‘dbsrv6 -f $AutoBahn/databse/ ascend.db’command before restarting the database along with the rest of the farm. 6 Restart services, confirming the Database Server runs and verifying the old DB is properly in place via the client. 7 Upgrade to NavisAccess 6.0. Have the setup program upgrade your database. Confirm that your distribution plan is properly accessed by the setup program and that the distribution plan is the one you wish to proceed with.
Note: Do not upgrade from NavisAccess 5.1 to NavisAccess 6.0, because NavisAccess 5.1 is a DSL-only management system and NavisAccess 6.0 is a dial-only management system.
Configuring a firewall in the NavisAccess network
When configuring a firewall for use in your NavisAccess network, it is essential that you know the following: • How NavisAccess can be partitioned, and • What communicated protocols and ports must be used across the networked domains.
Partitioning NavisAccess
NavisAccess can be partitioned across the following domains:
Client Domain - The NavisAccess clients can be installed in its own domain. This domain can be separate from the server, or the devices that it manages. There may be more than one client domain in the network, each having connection to the NavisAccess server farm and the managed devices.
Server Domain - The NavisAccess server farm components must be installed in a single domain. There may be several server domains in the network. These domains can be separate from the NavisAccess clients, or managed devices.
Managed Resource Domain - The managed resources, or devices, may reside in one or more domains. These domains can be separate from the NavisAccess client or server domains.
NavisAccess Installation and Administration Guide xv Read Me First Preparing for installation
This implies communication across three types of networked domains, where the firewall is separating each domain: • Client Domain / Server Domain • Client Domain / Managed Resource Domain • Server Domain / Managed Resource Domain
Protocols and ports to open on the firewall
The following topics define what communicated protocols and ports must be open on the firewall to enable communication between NavisAccess Client/Server Domains and the Managed Devices Domain: • Client/Server communication • Client/Managed devices communication • Server/Managed devices communication
Client Domain / Server Domain Communication
The following table lists the communication protocols that must be defined, and what ports that must be opened on the firewall that exists between the Client and Server Domains (the client/server domain boundary).
Table 0-1. Client Domain / Server Domain Communication
Client Domain Communication Path Server Domain Description
Sybase Client (on Sybase Server (on Client) Primary Server)
TCP: Any 10 user TCP: 2638 (from Primary The firewall needs to open up all ports to Primary Clients) outgoing TCP and UDP ports, except the Server UDP: 2638 (from Primary IMC TCP:1010 port UDP: Any one user Clients) Note: These ports do not apply to port to Primary Server NavisAccess CNM, as it removes all features that require direct Sybase connectivity.
IMC (on Client) IMC (on Primary and Secondary Servers)
TCP: Any one user TCP:1010 (from other The IMC processes communicate with port per server server and client IMCs) each other using a bi-polar TCP protocol, TCP: 1010 (from TCP: Any one port (to where one end of the connection other server and client other server and client terminates on TCP: 1010 port and the IMCs) IMCs other on Any TCP port. Note: These ports do not apply to NavisAccess CNM, as IMC communication is not necessary between client and server.
SNMPSrv Client (on SNMPSrv Server (on Client) Primary Server)
xvi NavisAccess Installation and Administration Guide Read Me First Preparing for installation
Table 0-1. Client Domain / Server Domain Communication
Client Domain Communication Path Server Domain Description
UDP: Any one user UDP: 3000 (from This applies to the Single SNMP Server port to Primary Server SNMPSrv clients on other configuration. In this configuration, all servers and clients) SNMP traffic is directed through the Note: UDP 3000 is SNMPSrv process on the Primary Server. configurable If Single SNMP Server is not configured, then the SNMPSrv process will reside on all servers. Client and SNMP communication will take-place with the device directly.
OSAgent (On Client) OSAgent (on Primary Server)
UDP: UDP: OSAgent_PORT In an environment where the client is not OSAgent_PORT on the same subnet as the Primary Server, the OSAgent on the client is TCP: Any one user TCP: defined to cascade from the OSAgent on port to Primary Server OSA_CLHDLR_TCP the Primary Server (via the use of the UDP: Any two user UDP: agentaddr file on the client). ports to Primary OSA_CLHDLR_UDP The environment variables that Server determine the OSAgent Broadcast and cascading ports are: Cascading OSAgents Cascading OSAgents within a Client within a Server Domain OSAGENT_PORT – required and Domain configured by setup. OSA_CLHDLR_TCP, OSA_CLHDLR_UDP - not required and TCP: OSA_CLHDLR TCP: Any one user port not configured by setup. If these are not (from cascading per cascading OSAgent configured, the cascading receiver ports OSAgents) UPD: Any two user ports will be selected at random. UDP: to cascading OSAgents OSA_CHLDRL_UDP (from cascading OSAgents)
Corba (On Client) Corba (On GUI and Reporting Servers)
TCP: Any one user TCP: Any one user TCP The client communicates with the GUI TCP port per corba port per corba object and Reporting Servers via TCP/IIOP. object (activated on (activated on GUI and The firewall must either be open for: UI and Reporting Reporting Server) • all TCP ports to/from the GUI and Server) Reporting Servers, or • all TCP/IIOP to/from the GUI and Reporting Servers
NavisAccess Installation and Administration Guide xvii Read Me First Preparing for installation
Client / Managed Devices communication
The following table lists the communication protocols that must be defined, and what ports that must be opened on the firewall that exists between the Client and Server Domains (the client/server domain boundary)l.
Table 0-2. Client / Managed Devices communication
Client Domain Communication Path Managed Devices Domain Description
SNMPSrv (on Managed Devices Server)
UDP: 162 (SNMP UDP: 162 (SNMP Traps to Note: This does not apply to the Traps from Devices) client) Single SNMP Server configuration. UDP: Any port to UDP: 161 (to receive SNMP When the Single SNMP Server send SNMP to devices from the client) configuration is used, all SNMP traffic travels via the SNMPSrv on UDP: 3000 - used the Primary Server. locally by the NavisAccess client
TFTPSrv Server (on Managed Devices Client)
UDP: 69 (TFTP UDP: 69 (TFTP to/from TFTP The following applies to to/from device) server) non-scheduled TFTP processing. All Note: UDP 69 is scheduled TFTP activity is configurable. processed by the Scheduling Server.
Ports used by NT Ports used by NT client client ONLY ONLY
UDP: 67 UDP: 68 (BOOT?DHCP to BOOT/DHCP Server TFTP Server) UDP: 68 UDP: 67 BOOT/DHCP from BOOT/DHCP Client TFTP Server
Local port for TFTPSrv Server users to pass data to it
UDP: 3050 (local port for TFTPSrv users)
xviii NavisAccess Installation and Administration Guide Read Me First Preparing for installation
Server / Managed Devices communication
The following table lists the communication protocols that must be defined, and what ports that must be opened on the firewall that exists between the Client and Server Domains (the client/server domain boundary).
Table 0-3. Server / Managed Devices communication
Server Domain communication path Managed Devices Domain Description
SNMPSrv (on Managed Devices Server/Primary)
UDP: 162 (SNMP UDP: 162 (SNMP Traps to If the Single SNMP Server Traps from Devices) client) configuration is used, all SNMP UDP: Any port to UDP: 161 (to receive SNMP traffic should flow from the Primary send SNMP to devices from the client) Server. If this is configured, the TFTP server process on the UDP: 3000 - for scheduling server will use port UDP communication from 3000 to communicate with the SNMP clients such as SNMPSrv on the Primary Server to SRM and TFTPSrv. process the SNMP traffic.If the Single SNMP Server configuration is not configured, SNMP traffic may flow from all servers.
TFTPSrv Server (on Managed Devices Scheduling Server)
UDP: 69 (TFTP UDP: 69 (TFTP to/from TFTP This setting applies ONLY to the to/from device) server) Scheduling Server, where all Note: UDP 69 is scheduled TFTP activity is configurable. processed.
Ports used by NT Ports used by NT client If the Single SNMP Server client ONLY ONLY configuration is used, the TFTPSrv process will use the SNMPSrv UDP: 67 UDP: 68 (BOOT?DHCP to process on the Primary Server to BOOT/DHCP Server TFTP Server) perform the SNMP UDP: 68 UDP: 67 BOOT/DHCP from communications. BOOT/DHCP Client TFTP Server
Local ports for TFTPSrv Server users to pass data to it.
UDP: 3050 (local port for TFTPSrv users)
Call Log Protocol Managed Devices CLP (on CLR Server)
NavisAccess Installation and Administration Guide xix Read Me First Preparing for installation
Table 0-3. Server / Managed Devices communication
Server Domain communication path Managed Devices Domain Description
UDP: 1646 (Call log UDP: Any (Call Log data to The firewall has to be configured to data from device and CLR and ACK from CLR) open all UDP ports from the device. ACK back to device) Note: UDP 69 is configurable.
Trap Forwarding via IMC
The IMC supports a feature that allows it to forward SNMP Traps onto other machines that may have a Network Management application running (such as HP Openview or Netcool). The following table defines the ports used by the IMC for trap forwarding:
Table 0-4. Trap Forwarding via IMC
Client or Server Communication path Management Software Description Domain
IMC (on Client or Machine with Network Server) management software
UDP: Any one user UDP: 162 (Destination This setting applies only if IMC trap port to forward traps machine(s) for forwarded traps forwarding is enabled on the Network Management Software that is behind a firewall.
Providing SNMP access for all NavisAccess servers and workstations
SNMP access to Lucent devices
Every NavisAccess server and workstation must have SNMP access to all devices that NavisAccess will manage. Therefore, when setting SNMP address security on your network devices, you must ensure that each NavisAccess machine is listed in the range of IP addresses the device will respond to. Alternately, you can turn SNMP address security off.
See the chapter “Preparing Lucent devices for use with NavisAccess” for instructions on setting SNMP address security.
xx NavisAccess Installation and Administration Guide Read Me First Preparing for installation
NavisAccess UDP ports
In order for NavisAccess 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 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 G-3 for full details. SNMP 161 SNMP - Trap 162 Trap Forwarding 1010 Please see “Configuring Trap Forwarding” on page A-1 for full details. Call-Logging 1646 Please refer to the chapter entitled, “System Options” in the NavisAccess User’s Guide. Osagent port 1492 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.
NavisAccess Installation and Administration Guide xxi Read Me First System requirements
System requirements
NavisAccess can be installed as a stand-alone (all server services and the client (GUI) reside on one and only one machine), or as a distributed server configuration with multiple servers and workstations.
A stand-alone configuration is simple to install and administer and works quite well for networks of up to 67,200 ports and where there will be a maximum of three (3) simultaneous users (client GUIs) of the NavisAccess system.
A distributed server configuration provides a scalable solution that takes care of a site’s growing needs. By using a distributed server configuration, NavisAccess can manage more devices and services as the network size increases.
System performance is also dependent upon the database size (the quantity of devices and services you will be managing) and larger reporting requirements. Long duration or trending reports (reports run for time spans greater than a couple of hours on 50 or more devices, services etc.) should be scheduled, and not run in real time. If these types of reports need to be run regularly either on a real-time or scheduled basis, it is recommended that a separate server be installed for the reporting component (Reporting Server).
Definitions • NavisAccess Server - This is the Solaris machine where server side components of the NavisAccess system get installed and run. The primary NavisAccess server refers to the server on which the database resides and secondary NavisAccess sever refers to any other server. • NavisAccess Workstation - This is the Solaris machine where the actual client GUI software is installed and can be run for a user to actually view and manage their network. Users must be on the workstation or x-term into a workstation to view and manage their network with the NavisAccess software. • GUI Server - This is the name of a component that is installed on a NavisAccess server. This does not allow the user to run the NavisAccess front-end GUI to manage to network. It is a server process that a client GUI connects with in order to generate the front-end display. Users cannot X-term into the GUI Server to manage their network. • Client GUI - The client GUI actually allows the user to access the front-end software and manage their network. A NavisAccess workstation runs client GUI software. An X-term into a NavisAccess workstation also runs client GUI software. • NavisAccess Server Farm - A set of NavisAccess Servers and Workstations that together manage the network. They all share one common database and all of the servers in the farm must be up and the NavisAccess services running on them for the system to be monitoring the network. • Service - A logical entity representing a part of the overall network traffic.For example, one TNT which provides analog service via one dial number (555-1212) and ISDN which provides service via another dialed number (555-1213) will have four services in NavisAccess representing this TNT’s traffic. The services will be TNT ISDN, TNT modem, 555-1212 modem and 555-1213 ISDN. • Port - Number of DS0’s on the device. DS0 is a single 64 Kbps channel, which is the building block of a T1 transmission line. Designed for digital voice (PCM), 24 DS0 channels make up one T1 line. xxii NavisAccess Installation and Administration Guide Read Me First System requirements
Operating System Requirements • Solaris 2.7 /2.8 • CDE is installed on each Solaris server/workstation NavisAccess will be run on, and the CDE environment setting for Allow Primary Windows on Top must be set to ON • Α list of Solaris patches that are documented as required by NavisAccess may be found on page one of the Release Notes. To obtain the patches, go to: http://www.esight.com/. • NavisAccess must be installed by root, and needs to run under ksh
Statements • One (1) fully-loaded TNT = 672 ports; 1 fully loaded APX 8000 = 2688 ports • Call logging data files will use 3 GB of space each day per 100 calls per second. • Disk space recommendations are based upon typical usage with the assumption of storing: – Eight days of call logging data (this data resides on the machine on which the CLS component is installed) – Ten days of Historical Service (Interval) Data – Fourteen days of Event Database History
Note: Your disk space usage may vary. Some tasks that impact disk space are: exporting to HTML and CSV, scheduling reports, and SNMP polling for interfaces. • Each TNT will result in an average of ten services being created in NavisAccess. This is based upon a typical installation. • It is recommended that the back up database be copied to a separate partition with a minimum of 20GB RAM.
Performance Tuning Statements • If you have installed the GUI Server and Reporting Server components on the same NavisAccess server machine, your GUI client performance will be impacted when running reports that take a considerable time to generate. • On the NavisAccess server on which the database is installed (for distributed configurations this is the Primary Server), the NavisAccess installation program sets a default database cache of 48 MB for systems with up to 512 MB RAM and a default database cache of 100 MB for systems with greater than 512 MB RAM.
NavisAccess Installation and Administration Guide xxiii Read Me First NavisAccess server and workstation configuration information
NavisAccess server and workstation configuration information
NavisAccess Networks with: • < 67,200 Ports and • < 100 Devices and • < 1500 NavisAccess Services
Stand-alone Server Workstation Configuration Notes Configuration
• Dual CPU (400 MHz) Ultra 60 None – no workstations can be Use this configuration to support a or equivalent installed to connect to a maximum of up to three (3) simultaneous • RAM: 2 GB stand-alone configuration client GUIs - (X-term sessions and NavisAccess GUI running on the • Available disk space: 24 GB or stand-alone itself) is the maximum more allowed with this configuration. • Swap Space: 4 GB Additional client GUIs will impact performance.
For NavisAccess Networks with: • < 134,000 Ports and • < 200 Devices and • < 3000 NavisAccess Services
Stand-alone Server Configuration Workstation Configuration Notes
• Enterprise 450 4 CPUs 400-MHz None – no workstations can be installed • Three (3) simultaneous client UltraSPARC II or equivalent to connect to a stand-alone configuration GUIs - (X-term sessions and • RAM: 4 GB NavisAccess GUI running on the • Available disk space: 24 GB or workstation itself) is the maximum more allowed with this configuration. • Swap Space: 4 GB Any additional client GUIs will impact performance. • To install 10 simultaneous clients, use the Distributed Server Configuration on the following page.
xxiv NavisAccess Installation and Administration Guide Read Me First NavisAccess server and workstation configuration information
For NavisAccess Networks with: • <201,660 Ports and • < 300 Devices and • < 4500 NavisAccess Services
Distributed Server Configuration Workstation Configuration Notes
Primary Server: • Per Ultra 60, 2 CPU, 2 GB: Ten (10) simultaneous client GUIs - • Enterprise 450 4 CPUs 400-MHz Ten (10) simultaneous client GUIs is (X-term sessions and NavisAccess GUI UltraSPARC II or equivalent the maximum allowed with this running on the stand-alone itself) is the • RAM: 4 GB workstation configuration. Any maximum allowed with this • Available disk space: 24 GB or additional client GUIs into this configuration. Additional client GUIs more (RAID recommended) workstation will impact will impact performance. performance. • Swap Space: 4 GB You can add an additional U60 GUI Primary Server Components: • Per Ultra 10, 1 GB: Server (the secondary server has the • Database Server Three (3) simultaneous client GUIs GUI Server component installed on it in this configuration) with 2GB RAM to • Scheduling Server is the maximum allowed with this support up to a maximum of twenty • Checkpoint Handler workstation configuration. Any additional client GUIs into this (20) client GUIs (either X-term sessions • Call Logging Receiver workstation will impact or installed NA workstations). • Dial Service Totals Engine performance. • Dial Service Management Unit Better client GUI performance can be • Auto-Grouping Engine • Per Ultra 5, 512MB: achieved by installing the Reporting Two (2) simultaneous client GUIs is Server, Data Management Server and Secondary Server: the maximum allowed with this the Call Logging Server components on • Dual CPU (400 MHz) Ultra 60 or workstation configuration. Any a separate machine from the GUI equivalent additional client GUIs into this Server. This is most beneficial if reports • RAM: 2 GB workstation will impact that crunch a lot of data will be • Hard Disk: 24 GB or more performance. generated and run on a regular basis. • Swap Space: 4 GB Secondary Server Components: • GUI Server • Data Management Server • Reporting Server • Call Logging Streamer
NavisAccess Installation and Administration Guide xxv Read Me First NavisAccess server and workstation configuration information
For NavisAccess Networks with: • < 336,000 Ports and • < 500 Devices and • < 8000 NavisAccess Services
Distributed Server Configuration Workstation Configuration Notes
Primary Server: • Per Ultra 60, 2 CPU, 2 GB: Ten (10) simultaneous client GUIs • Enterprise 450 4 CPUs 400-MHz Ten (10) simultaneous client GUIs is (X-term sessions and NavisAccess GUI UltraSPARC II or equivalent the maximum allowed with this running on the stand-alone itself) is the • RAM: 4 GB workstation configuration. Any maximum allowed with this • Available disk space: 54GB Hard additional client GUIs into this configuration. Additional client GUIs Disc (RAID recommended) workstation will impact will impact performance. performance. • Swap Space: 8GB You can add an additional U60 GUI Primary Server Components: • Per Ultra 10, 1 GB: Server (the secondary server has the • Database Server Three (3) simultaneous X-term GUI Server component installed on it in this configuration) with 2GB RAM to • Scheduling Server sessions is the maximum allowed support up to a maximum of twenty • Checkpoint Handler with this workstation configuration. Any additional X-terms into this (20) client GUIs (either X-term sessions • Call Logging Receiver workstation will impact or installed NA workstations). • Auto-Grouping Engine performance. Secondary Server #1: • Per Ultra 5, 512MB: • Dual CPU (400 MHz) Ultra 60 or Two (2) simultaneous client GUIs is equivalent the maximum allowed with this • RAM: 2 GB workstation configuration. Any • Available disk space: 24 GB or additional client GUIs into this more workstation will impact • Swap Space: 4 GB performance. Secondary Server #1 Components: • Dial Service Management Unit • Dial Service Totals Engine
Secondary Server #2: • Dual CPU (400 MHz) Ultra 60 • RAM: 2 GB • Available disk space: 54 GB or more • Swap Space: 4 GB Secondary Server #2 Components: • GUI Server • Data Management Server • Reporting Server • Call Logging Streamer
Note: For networks larger than 336,000 ports or more than 500 TNTs to be managed by NavisAccess, please consult with your Lucent Sales Representative for configuration guidelines.
xxvi NavisAccess Installation and Administration Guide Stand-alone Installation 1
SERIAL NUMBER FILE NEEDED: Before installing NavisAccess, 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 box insert for details. You will need the Authorization Code that is enclosed with your NavisAccess software. There is a 24-hour turn-around time for license key requests.
Note: A serial number file is not required if you are installing a 30-day evaluation copy.
Getting ready to install: Things to know
Please read the following prerequisites and preparatory steps before beginning installation of NavisAccess.
Before proceeding with this installation, please read the preliminary information found in “Read Me First” on page -xiii. • Installation can be run from an X-terminal or a character terminal. • All NavisAccess files are installed with owner and group of the user who installed it. The files are given 755 as mode. • NavisAccess must be installed by a super user. • In order to use the NavisAccess 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 Installation and Administration Guide 1-1 Stand-alone Installation Getting ready to install: Things to know
• For proper display of NavisAccess windows, you must ensure that the CDE environment setting for “Allow Primary Windows On Top” is turned on.
• All servers and workstations in a NavisAccess installation must have proper SNMP access to the network devices being managed. This includes proper setting of SNMP community strings in NavisAccess. • X-term performance will be improved by enhancing the video card on the machine used to X-term into NavisAccess. • When X-terming from UNIX to a Windows NT machine, the NT machine must be set to a maximum of 256 colors. • X-terming is supported only on connections of 256K or higher. • When using Telnet or Rlogin to run NavisAccess, 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 If the command returns :0.0
or
or
1-2 NavisAccess Installation and Administration Guide Stand-alone Installation Installation Checklist for NavisAccess 6.0 on Solaris
System requirements
NavisAccess installation step summary: Solaris Stand-alone
Note: For a detailed description of hardware requirements and component distribution, please refer to “System requirements” on page -xxii 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. Detailed installation instructions follow this list.
Prerequisites to installation:
q Solaris Operating System must be installed.
q CDE must be installed.
q NavisAccess must be installed by a super user.
q NavisAccess should run under the ksh.
q Required Installation system patches must be applied. The patches are located at: ftp.ascend.com/pub/Software-Releases/NavisAccess/Documentation/SOLARIS
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.
Installation Checklist for NavisAccess 6.0 on Solaris
There are three parts, each containing several steps, to completing a NavisAccess 6.0 installation. These are the three parts and the order in which they should be done: (1) Ready Solaris machines for install; (2) Install/Configure NavisAccess Software; (3) Configure RASes (devices) to be managed by NavisAccess.
Part 1: Ready Solaris Machines
q Determine what type of NavisAccess install you want to do: Stand-alone= one Solaris box Distributed Server = at least 2 Solaris boxes, one for the server and one for the workstation
q Make sure your hardware meets the minimum system requirements specified.
NavisAccess Installation and Administration Guide 1-3 Stand-alone Installation Installation Checklist for NavisAccess 6.0 on Solaris
q Install Solaris 2.7/2.8 on all servers and workstations that will have NavisAccess software on them and get them configured to work on your network appropriately. – All must have IP, SNMP, and TFTP connectivity to the remote access devices you want NavisAccess to manage. – Make sure to configure appropriate swap space as indicated in the NavisAccess installation guide. – Comment out the default Solaris TFTP server in /etc./inetd.conf since NavisAccess has its own. – NavisAccess must be run under the ksh, so on your NavisAccess machines you might want to make ksh the default shell for root under /etc./passwd. – Optional: Define a printer on the Solaris servers and workstations for NavisAccess reports to print.
q Install CDE on all servers and workstations that will have NavisAccess software on them. CDE is part of the default Solaris install. Ensure the CDE environment setting for Allow Primary Windows on Top is turned ON.
q Install the Solaris patches as specified required by NavisAccess on all servers and workstations that will have NavisAccess software on them. The list of these required patches can be found on page one of the Release Notes. The patches may be obtained at: http://www.esight.com/.
Part 2: Install NavisAccess & Configure NavisAccess System Settings
q If installing a purchased / LIVE (not evaluation) copy of NavisAccess, obtain the necessary License Key(s) and Serial Number File needed to install NavisAccess from http://www.lucent-info.com/ins/navisaccesslicense/.
Note: There can be a 24 hour turnaround time.
q As root, install the NavisAccess software on all server(s) and workstation(s) required for your type of installation. See Chapter 1, “Stand-alone Installation” or Chapter 2, “Distributed Installation” depending on your installation type.
q Reboot all NavisAccess servers and workstations and let them come up. Start NavisAccess by typing srm at the command prompt.
– Choose the Configure >System Options > SNMP Security menu selection and add all of the SNMP read community strings and the SNMP write community strings that are assigned or that you will assign to the remote access devices NavisAccess will manage.
– Choose the Configure > System Options > AccessWatch menu selection and enter the Call Logging Key and Port. Both of these must match the device configuration. When changing the Call Logging Port, you must stop all NavisAccess services and restart them for this change to become effective.
Note: These settings are global to NavisAccess, you only need set them on one workstation.
1-4 NavisAccess Installation and Administration Guide Stand-alone Installation Installation Checklist for NavisAccess 6.0 on Solaris
Part 3: Configure Lucent Remote Access Servers to work with NavisAccess.
These settings apply to Lucent TNT, APX, and MAX hardware. Make sure the TAOS version on the hardware meets the minimum required by NavisAccess.
q Configure SNMP traps to be sent from the device to the NavisAccess server that has the Scheduling Server component installed on it. This will let NavisAccess show traps in the Event Viewer when a link goes down or up or someone telnets into a device etc.
q Configure the SNMP Community Strings on the device, if not done already. This goes back to what is set in NavisAccess in the Configure > System Options > SNMP Security screen. The strings set in NavisAccess must match what is set on the device(s) in order for SNMP communication to be allowed between the device and NavisAccess.
q Configure the NAS port ID format. The device must use the new style of NAS port encoding for NavisAccess to discover services and correctly figure where calls are being received (shelf/slot/line). For the TNT, this is the new-nas-port-id-format found in the SYSTEM profile.
q If a LIVE copy of NavisAccess is being installed, HASH CODES for the NavisAccess Software Option must be installed on the devices that NavisAccess will manage. This ‘gives’ NavisAccess permission to manage the device (open a BoxMap on it, and with TAOS version 8.0 it is necessary in order to be able to create a Call Logging Profile).
q The Call Logging Profile on the device must be configured to send Call Logging information to the NavisAccess Server which has the Call Logging Receiver component installed on it.
– If you have a purchased copy of NavisAccess and TAOS > 8.0 on the device, you need the NavisAccess Software Option Hash Code installed to create a Call Logging Profile.
– If you have evaluation copy of NavisAccess and TAOS > 8.0, and therefore do not have the NavisAccess Software Option hash code, you can temporarily create a Call Logging Profile to work by: logging onto the device with debug privileges, switching to debug mode, and entering cleval . This will let you enable Call Logging to be sent from the device, but after 30 days it will stop sending this data to NavisAccess.
After installing NavisAccess 6.0
What did we accomplish by going through this three-part installation process? • Part 1 made sure the Solaris hardware was ready for NavisAccess to be installed on it. • Part 2 actually installed NavisAccess and let you set up some minimal system settings in order for NavisAccess to communicate with the devices, once the devices were actually configured in Part 3 to send information to NavisAccess. • Now after Part 3 is done, and calls come into the devices, Call Logging Packets (start and stop) containing information about all calls taken by the device will automatically be sent to NavisAccess. NavisAccess will receive the packets, process them and automatically discover the devices and services on those devices.
NavisAccess Installation and Administration Guide 1-5 Stand-alone Installation NavisAccess stand-alone installation
However, there is one more thing to accomplish before using NavisAccess:
Make sure you are running the kornshell (.ksh). Start NavisAccess on the workstation (if you did a stand-alone install, the workstation and server are the same machine). Select the Tools > DNIS Translation menu selection and translate all partial DNISs to the minimum length (the default is ten digits). After that, calls that land on the translated DNIS will cause a DNIS-based service to be created automatically.
NavisAccess stand-alone 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 directory and run the installation file by entering: . /setup
Note: If you are executing more than one installation on the same LAN, refer to “Multiple stand-alone installation on the same LAN” on page B-1.
Note: If you have a device in your network that has multiple IP addresses, you can stop auto-discovery from occurring upon rebooting your system by adding -d agedisc to the./setup command. This will ensure that the device will not inadvertently be discovered twice when using MLConfig. Using this option will cause the Do not discover devices through Call logging packets checkbox on the MLConfig tab of the NavisAccess Configuration dialog (Configure>System Options) to be selected once NavisAccess starts. Example: ./setup -d agedisc Once NavisAccess starts, you can start discovery through call-logging packets by deselecting the Do not discover devices through Call logging packets checkbox on the NavisAccess Configuration dialog MLConfig tab (Configure>System Options). 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. You will then be prompted to enter a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess on how to obtain a serial number file. The file is named liblock.so.
6 Enter the full path to the file, including the file name. Click OK when done. The NavisAccess-User Information screen displays. 7 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. 8 Select Stand-alone at the Installation Type screen and click Next.
1-6 NavisAccess Installation and Administration Guide Stand-alone Installation NavisAccess stand-alone installation
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 on how to obtain a License Key.
9 Enter the license key and click OK. The license key is an 18-character letter/number combination. It is not case sensitive. 10 The Target Directory screen displays with the default directory /export/home/navis. You may install NavisAccess 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 deletes 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. 11 Enter the name and path of the directory in which NavisAccess is to be installed.
Note: 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 should be installed because all files in the final directory will be deleted.
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. 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?” Click Yes to quit. NavisAccess automatically erases any installation files that may have been copied to the directory.
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.
NavisAccess Installation and Administration Guide 1-7 Stand-alone Installation NavisAccess stand-alone installation
q Step 3: Check status of services
All NavisAccess services will start upon reboot. The nautil utility is provided to start, stop, and check the status of services. You should check the status of your services before proceeding.
Syntax for using nautil follows:
nautil start Starts NavisAccess services 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. dbmaint Shuts down the services necessary to run the DBMAINT utility. -9 Kills process. If this option is specified, nautil will not attempt to gracefully shutdown the process. Instead the processes will be terminated using ’kill -9’. This option should be used with care.
To check if NavisAccess 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.
1-8 NavisAccess Installation and Administration Guide Stand-alone Installation Before You Run NavisAccess for the first time
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 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. Compiling of a MIB will generate messages reading: “Processing File:
You are now finished with the installation process, and may start NavisAccess.
Before You Run NavisAccess for the first time
Please note the following items that must be in place before using NavisAccess: • Lucent MAX, TNT, and APX devices must be running appropriate device software. Consult the “NavisAccess Installation and Administration Guide” and the README file for the latest information. • Lucent MAX and TNT devices must have SNMP enabled. See Chapter 3, “Preparing Lucent devices for use with NavisAccess” for details. • To use the AccessWatch application, Lucent MAX, APX and TNT devices must have Call Logging enabled. See Chapter 3, “Preparing Lucent devices for use with NavisAccess” for details. • Device Read and Read/Write community strings for SNMP v1 supported devices, as well as Read-Only and Read-Write user names and passwords for SNMP v3 supported devices must be properly configured. See the following, as applicable: – SNMP Security in Chapter 16 of the NavisAccess User’s Guide.
– Chapter 3, “Preparing Lucent devices for use with NavisAccess” in this guide. • Any required MIBs should be compiled. See the MIB Compiler topic in Chapter 14 of the NavisAccess User’s Guide.
NavisAccess Installation and Administration Guide 1-9 Stand-alone Installation Starting NavisAccess
Starting NavisAccess
To start NavisAccess, the environment must be set and the services must be started. The user application (client GUI) can then be started.
Note: The following procedure must be run by ROOT.
If you did not update your .profile during installation, you will need to run the .NavisAccessProfile before starting NavisAccess.
Note: Before starting NavisAccess, all services must be running. To start the services, use nautil start. For detailed information on the nautil utility, refer to the “The nautil Utility” on page F-1.
! 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.
To start NavisAccess: 1 Make sure the NavisAccess services are running. At the command line enter: nautil status This checks the status of the services. (For full details on the nautil utility, see “Step 3: Check status of services” on page 1-8.) 2 After verifying that all services are running, enter the following: srm & The srm executable starts the NavisAccess graphical user interface. 3 The first time you start NavisAccess, use the following default User Name and password: User Name =Admin Password = Admin
Note: Every console user of NavisAccess must have their own account and should be logged in as such. Do not run multiple instances of NavisAccess from the same NavisAccess login ID.
A user who Xterms into the server machine must use a different NavisAccess login than other users currently logged in to that server machine.
Startup Tip If you are starting Navis via a Telnet session from another Solaris machine, make sure you have properly exported the display. Telnet into the NavisAccess server 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.
1-10 NavisAccess Installation and Administration Guide Stand-alone Installation Starting NavisAccess
Starting NavisAccess as a non-root user
By default, NavisAccess can only be started by a user with root privileges. To override this, enter the following at the command line:
chmod -fR 777 navis_install_directory
where navis_install_directory is the name of the directory in which NavisAccess is installed. This command gives proper permissions to the files so they can be started by a non-root user.
For example, if NavisAccess is installed in a directory named “navis5”, you would enter:
chmod -R 777 navis5
NavisAccess Installation and Administration Guide 1-11
Distributed Installation 2
SERIAL NUMBER FILE NEEDED: Before installing NavisAccess, 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 box insert for details. You will need the Authorization Code that is enclosed with your NavisAccess 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 30-day evaluation copy. However, do not install an evaluation copy of NavisAccess 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 before beginning installation of NavisAccess.
Before proceeding with this installation, please read the preliminary information found in “Read Me First” on page -xiii.
• Do not run the installation application as a background process. The installation application should not be run as a background process, for example, with an ampersand (&). If it is, the Primary Server installation will go to the background toward the end of the installation and then stop. To complete the installation, in this case, go to the parent terminal of Install App and type: fg. The installation will proceed. • When upgrading to NavisAccess 6.0, it can take an hour or two to upgrade the database on large farms (more than 10,000 services). • Installation can be run from an X terminal or a character terminal. • All NavisAccess files are installed with owner and group of the user who installed it. The files are given 755 as mode. • NavisAccess must be installed by a super user. In order to use the NavisAccess 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 Installation and Administration Guide 2-1 Distributed Installation Getting ready to install: Things to know
• For proper display of NavisAccess windows, you must ensure that the CDE environment setting for “Allow Primary Windows On Top” is turned on.
• All servers and workstations in a NavisAccess installation must have proper SNMP access to the network devices being managed. This includes proper setting of SNMP community strings in NavisAccess. • X term performance will be improved by enhancing the video card on the machine used to X term into NavisAccess. • When X terming from UNIX to a Window NT machine, the NT machine must be set to a maximum of 256 colors. • X terming is supported only on connections of 256K or higher. • When using Telnet or Rlogin to run NavisAccess, 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 If the command returns :0.0
or
or
2-2 NavisAccess Installation and Administration Guide Distributed Installation System requirements
• 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.
System requirements
Prerequisites for distributed installation
Note: For a detailed description of hardware requirements and component distribution, please refer to “System requirements” on page -xxii.
A distributed installation consists of NavisAccess 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 that 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 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 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.
NavisAccess Installation and Administration Guide 2-3 Distributed Installation NavisAccess component distribution
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.
Server System Specifications Relative Power Possible Component Distribution Rating A dual 400mhz 12GB RAID 0 900 DB Server, DSMSC, NavisAccess Server, 384MB 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 database, NavisAccess 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 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 component distribution
If you are installing a Distributed Server configuration, efficient distribution of the NavisAccess components is paramount. This section lists and briefly describes each component and how it should be distributed.
The following table describes the NavisAccess components and their relative resource needs in terms of CPU utilization, memory and disk space. You should allocate your hardware appropriately based upon these considerations.
Some components can be distributed only on one server, others can be installed multiple times on different servers to distribute processing.
2-4 NavisAccess Installation and Administration Guide Distributed Installation NavisAccess 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 farm.
Table 2-1. NavisAccess components and their function
Component Name and Description Relative Ratings Relative ratings
Database Server Contains the Sybase Database Server. It also has 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 It is the background component of the NavisAccess CPU usage = low GUI (user interface). It processes background Disk space = low 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 Huntgroups and Services based on call logging Disk space = low packets received from devices. Memory usage = low • This component can be installed only once
Checkpoint Handler This process keeps track of all devices that are part CPU usage = low of one or more services. It triggers the Session Disk space = low Snapshot Protocol on those devices in order to gain Memory usage = low an accurate state of active sessions. • This component can be installed only once
Dial Service Totals Keeps track of all devices that are part of one or CPU usage = low Engine more services. It polls those devices for plant DS0 Disk space = low and DSP totals. Memory usage = low • This component can be installed only once
Call Logging Streamer Receives Call Logging packets in real time and CPU usage = low stores them on disk. These files are later used by the Disk space = high reporting modules. Memory usage = low
The Call Logging Streamer component should be on the same machine as the Reporting Server. 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 only once
NavisAccess Installation and Administration Guide 2-5 Distributed Installation NavisAccess component distribution
Table 2-1. NavisAccess components and their function (continued)
Component Name and Description Relative Ratings Relative ratings
Data Management The Data Management Server contains the CPU usage = medium Server following: Disk space = low • Event Streamer: This stores the events in the Memory usage = low database. • Adaptive Performance Monitor: Processes Dial Service data that is periodically written to the database. It calculates weighted averages of that data and stores it back into 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.
Dial Service Processes real time dial device traffic into CPU usage = high Management Unit per-service, per-interval averages. This data is then Disk space = low streamed to the database and is also available for Memory usage = high
applets such as AccessWatch. • 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 Dial Service. Disk space = low
• This component can be installed multiple times. Memory usage = medium
GUI Server This is the back-end process responsible for CPU usage = medium collecting and publishing data specific to the Disk space = low
distributed GUI applets such as Examiner, Access Memory usage = medium Watch, Active Sessions, etc. If you will be running multiple workstations and/or X-term sessions, it is advisable to install the GUI server on a separate machine. All workstations and X-terms should then log into that machine. • This component can be installed multiple times.
2-6 NavisAccess Installation and Administration Guide Distributed Installation Installation Checklist for NavisAccess 6.0 on Solaris
Table 2-1. NavisAccess components and their function (continued)
Component Name and Description Relative Ratings Relative ratings
Reporting Server This processes front-end and back-end requests for CPU usage = low reports. It generates the report’s display data and Disk space = low
publishes it to the client for viewing. If you will be Memory usage = high have multiple workstations and/or X-term 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.
Installation Checklist for NavisAccess 6.0 on Solaris
There are three parts, each containing several steps, to NavisAccess V5.0 installation. The three parts are as follows. They are in the order in which they should be done: 1 Ready Solaris machines for install 2 Install/Configure NavisAccess Software 3 Configure RASes (devices) to be managed by NavisAccess.
Part 1: Ready Solaris Machines
q Determine what type of NavisAccess install you want to do: Stand-alone = one Solaris box Distributed = at least two Solaris boxes, one for the server and one for the workstation
q Make sure your hardware meets the minimum system requirements specified.
q Install Solaris 2.7/2.8 on all servers and workstations that will have NavisAccess software on them and get them configured to work on your network appropriately. – All must have IP, SNMP, and TFTP connectivity to the remote access devices you want NavisAccess to manage. – Make sure to configure appropriate swap space as indicated in the NavisAccess installation guide. – Comment out the default Solaris TFTP server in /etc/inetd.conf since NavisAccess has its own TFTP. – NavisAccess must be run under the ksh. It is advisable to make ksh the default shell for root under /etc/passwd on your NavisAccess machines. – Optional: Define a printer on the Solaris servers and workstations for NavisAccess reports to print.
NavisAccess Installation and Administration Guide 2-7 Distributed Installation Installation Checklist for NavisAccess 6.0 on Solaris
q Install CDE on all servers and workstations that will have NavisAccess software on them. CDE is part of the default Solaris install. Ensure the CDE environment setting for Allow Primary Windows on Top is turned ON.
q Install the Solaris patches as specified required by NavisAccess on all servers and workstations that will have NavisAccess software on them. The list of these required patches can be found on page one of the Release Notes. The patches may be obtained at: http://www.esight.com/.
Part 2: Install NavisAccess and Configure System Settings
q If installing a purchased / LIVE (not evaluation) copy of NavisAccess, obtain the necessary License Key(s) and Serial Number File needed to install NavisAccess from http://www.lucent.com/products/applications/navis_license.html
Note: There can be a 24 hour turn-around time.
q As root, install the NavisAccess software on all server(s) and workstation(s) required for your type of installation. See Chapter 1, “Stand-alone Installation” or Chapter 2, “Distributed Installation” depending on your installation type.
q Reboot all NavisAccess servers and workstations and let them come up. Start NavisAccess by typing sum at the command prompt. Note, these following steps go hand in hand with configuration that you need to do on your devices in Part 3, so you may have to go back and forth a bit between steps in Part 2 and steps in Part 3 of this checklist. – Choose the Configure >System Options > SNMP Security menu selection and add all of the SNMP read community strings and the SNMP write community strings that are assigned or that you will assign to the remote access devices NavisAccess will manage. – Choose the Configure > System Options > AccessWatch menu selection and enter the Call Logging Key and Port. Both of these must match the device configuration. When changing the Call Logging Port, you must stop all NavisAccess services and restart them for this change to become effective.
Note: These settings are global to NavisAccess, you only need set them on one workstation.
2-8 NavisAccess Installation and Administration Guide Distributed Installation Installation Checklist for NavisAccess 6.0 on Solaris
Part 3: Configure Lucent Remote Access Servers to work with NavisAccess.
These settings apply to Lucent TNT, APX, and MAX hardware. Make sure the TAOS version on the hardware meets the minimum required by NavisAccess.
q Configure SNMP traps to be sent from the device to the NavisAccess server that has the Scheduling Server component installed on it. This will let NavisAccess show traps in the Event Viewer when a link goes down or up or someone telnets into a device etc.
q Configure the SNMP Community Strings on the device, if not done already. This goes back to what is set in NavisAccess in the Configure > System Options > SNMP Security screen. The strings set in NavisAccess must match what is set on the device(s) in order for SNMP communication to be allowed between the device and NavisAccess.
q Configure the NAS port ID format. The device must use the new style of NAS port encoding for NavisAccess to discover services and correctly figure where calls are being received (shelf/slot/line). For the TNT, this is the new-nas-port-id-format found in the SYSTEM profile.
q If a LIVE copy of NavisAccess is being installed, HASH CODES for the NavisAccess Software Option must be installed on the devices that NavisAccess will manage. This ‘gives’ NavisAccess permission to manage the device (open a BoxMap on it, and with TAOS version 8.0 it is necessary in order to be able to create a Call Logging Profile).
q The Call Logging Profile on the device must be configured to send Call Logging information to the NavisAccess Server which has the Call Logging Receiver component installed on it. – If you have a purchased copy of NavisAccess and TAOS > 8.0 on the device, you need the NavisAccess Software Option Hash Code installed to create a Call Logging Profile. – If you have evaluation copy of NavisAccess and TAOS > 8.0 and therefore do not have the NavisAccess Software Option hash code, you can temporarily create a Call Logging Profile to work by: logging onto the device with debug privileges, switching to debug mode, and entering cleval. This will let you enable Call Logging to be sent from the device, but after 30 days it will stop sending this data to NavisAccess.
NavisAccess Installation and Administration Guide 2-9 Distributed Installation Installation Checklist for NavisAccess 6.0 on Solaris
After installing NavisAccess 6.0
What did we accomplish by going through this three-part installation process? • Part 1 made sure the Solaris hardware was ready for NavisAccess to be installed on it. • Part 2 actually installed NavisAccess and let you set up some minimal system settings in order for NavisAccess to communicate with the devices, once the devices were actually configured in Part 3 to send information to NavisAccess. • Now after Part 3 is done and calls come into the devices, Call Logging Packets (start and stop) containing information about all calls taken by the device will automatically be sent to NavisAccess. NavisAccess will receive the packets, process them and automatically discover the devices and services on those devices.
However, there is one more thing to accomplish before using NavisAccess:
Make sure you are running the kornshell (ksh). 1 Start NavisAccess on the workstation (if you did a Stand-alone install, the workstation and server are the same machine). 2 Select the Tools > DNIS Translation menu selection and translate all partial DNISs to the minimum length (the default is ten digits).
Then, calls that land on the translated DNIS will cause a DNIS-based service to be created automatically.
Installation Step Summary
Primary Server installation and creation of Distribution Plan qStep 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 Important! Do not install more than one secondary server at the same time. q Step 4: Reboot Secondary server(s)
Workstation installation q Step 5: Installation of Workstation(s) from CD q Step 6: Reboot workstation
Additional Steps qStep 7: Check status of services q Step 8: Compile MIBs on all Workstations
2-10 NavisAccess Installation and Administration Guide Distributed Installation Primary server installation and creation of Distribution Plan
Primary server installation and creation of Distribution Plan
Note: Do not run the installation application as a background process.
If the installation application is run as a background process, ((i.e. with an ampersand (&)), the Primary Server installation will go to the background toward the end of the installation and then stop. In order to complete the installation, in this event, go to the parent terminal of Install App and type: fg. The installation will then proceed.
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 directory and run the installation file by entering: ./setup
Note: If you have multiple NavisAccess farms on the same LAN, please refer to the section, “Multiple server farms on the same LAN” in this chapter. If you have a device in your network that has multiple IP addresses, you can stop auto-discovery from occurring upon rebooting your system by adding -d agedisc to the ./setup command. This will ensure that the device will not be inadvertently discovered twice when using MLConfig. Using this option will cause the Do not discover devices through Call logging packets checkbox on the MLConfig tab of the NavisAccess Configuration dialog (Configure>System Options) to be selected once NavisAccess starts. Example: ./setup -d agedisc Once NavisAccess starts, you can start discovery through call-logging packets by deselecting the Do not discover devices through Call logging packets checkbox on the NavisAccess Configuration dialog MLConfig tab (Configure>System Options). 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. You will be prompted to enter a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess on how to obtain a serial number file. The file is named liblock.so.
6 Enter the full path to the file, including the file name. Click OK when done. The “NavisAccess-User Information” screen displays. 7 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.
NavisAccess Installation and Administration Guide 2-11 Distributed Installation Primary server installation and creation of Distribution Plan
You will be prompted to enter a Primary Server License Key. The license key must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess on how to obtain a License Key.
8 Enter the license key and click OK. The license key is an 18-character letter/number combination. It is not case sensitive. 9 Select Distributed at the Installation Type screen display.
10 Select the Single SNMP Server Installation checkbox, if desired. Choosing this option will cause SNMP requests to originate at one central server. 11 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 server farm. NavisAccess workstations do not need to be entered.
Note: Remember that NavisAccess 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. 12 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 database, plus other selected components. Typically, this should be the most powerful machine in the server farm.
2-12 NavisAccess Installation and Administration Guide Distributed Installation Primary server installation and creation of Distribution Plan
– The “Machine Name” field is used only by NavisAccess. 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.
13 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. 14 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: a 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 MachineName and IP Address fields. b Edit the information as needed and press Modify.
Deleting a machine entry To delete information in the distribution plan: a Highlight the row you want to delete in the table section of the screen. b Click Delete. The machine entry is deleted.
15 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 components among the machines defined in the previous screen or to modify the component distribution.
NavisAccess Installation and Administration Guide 2-13 Distributed Installation Primary server installation and creation of Distribution Plan
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. 16 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 Number 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
Data Management Server One
Dial Service Management Unit Multiple
Call Logging Receiver Multiple
GUI Server Multiple
Reporting Server Multiple
See the section “NavisAccess component distribution” on page 2-4 for details on how to distribute the components. 17 To assign a component, click the component field. A list of the available components displays. Select the component you need. 18 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: [2]GUI Server
2-14 NavisAccess Installation and Administration Guide Distributed Installation Primary server installation and creation of Distribution Plan
19 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 Database, and proceeds to install the appropriate components to each machine. 20 Click Next when the component distribution is complete. 21 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 deletes 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. 22 Enter the directory in which NavisAccess 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.) 23 The “Are You Sure?” screen displays, warning 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 should be installed because all files in the final directory will be deleted. 24 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?” Click [Yes] to quit. NavisAccess automatically erases any installation files that may have been copied to the directory.
q Step 2: Reboot system
Once the above steps have been completed, 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.
NavisAccess Installation and Administration Guide 2-15 Distributed Installation Secondary server installation
Secondary server installation
Important! Do not install more than one secondary server at the same time.
Note: Do not run the installation application as a background process.
If the installation application is run as a background process, ((i.e. with an ampersand (&)), the Primary Server installation will go to the background toward the end of the installation and then stop. In order to complete the installation, in this event, go to the parent terminal of Install App and type: fg. The installation will then proceed.
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.
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 directory and run the installation file by entering: ./setup 4 The “NavisAccess - Welcome” screen displays. Click Next to continue. You will be prompted to enter a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess on how to obtain a serial number file. The file is named liblock.so.
5 Enter the full path to the file, including the file name. Click OK when done. 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. You will be prompted to enter a Secondary Server License Key. The license key must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess on how to obtain a License Key.
6 Enter the license key and click OK. The license key is an 18-character letter/number combination. It is not case sensitive. 7 Verify that Proceed is checked, and click Next.
2-16 NavisAccess Installation and Administration Guide Distributed Installation Workstation installation
8 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 deletes 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 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 should be installed because all files in the final directory will be deleted. 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; you must allow enough time for the process to complete.
q Step 4: 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.
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 directory and run the installation file by entering: ./setup
Note: If you intend to install your workstation on a separate subnet, please refer to “Workstation Installation on a Separate Subnet” on page C-1. 4 The “NavisAccess - Welcome” screen displays. Click Next to continue.
NavisAccess Installation and Administration Guide 2-17 Distributed Installation Workstation installation
You will be prompted to enter a Serial Number file. This file must be obtained from Lucent Technologies prior to installing the software. Consult the documentation included with NavisAccess on how to obtain a serial number file. The file is named liblock.so.
5 Enter the full path to the file, including the file name. Click OK when done. 6 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. 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 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 not case sensitive. 8 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 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 9 Enter the directory in which NavisAccess is to be installed. (If no such directory exists, you are prompted to create a directory. 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 should be installed because all files in the final directory will be deleted. 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.
2-18 NavisAccess Installation and Administration Guide Distributed Installation Workstation installation
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
All NavisAccess 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.
The Syntax for using nautil follows:
nautil start Starts NavisAccess services 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. dbmaint Shuts down the services necessary to run the DBMAINT utility. -9 Kills process. If this option is specified then nautil will not attempt to gracefully shutdown the process. Instead the processes will be terminated using 'kill -9'. Should be used with care.
To check if NavisAccess 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)
NavisAccess Installation and Administration Guide 2-19 Distributed Installation Starting NavisAccess
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, 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 Once the NavisAccess services are running, you may compile MIBs. Open the MIB compiler by entering 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:
You are now finished with the installation process, and may start NavisAccess.
Starting NavisAccess
Once the environment is set and the server services are started, you may start NavisAccess. Then start the user application (client GUI). This can be started on any workstation logging in to the server.
Note: The following procedure must be run by ROOT.
If you did not update your .profile during installation, you will need to run the .NavisAccessProfile before starting NavisAccess. Note: Before starting NavisAccess, all services must be running. To start the services, use nautil start. For detailed information on the nautil utility, refer to the “The nautil Utility” on page F-1.
2-20 NavisAccess Installation and Administration Guide Distributed Installation Starting NavisAccess
! 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.
Start NavisAccess using the steps below: 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 Appendix F, “The nautil Utility.”.) 2 After verifying that all services are running, enter the following: srm & The srm executable starts the NavisAccess graphical user interface. 3 The first time you start NavisAccess, use the default User Name and password: User Name = Admin Password = Admin.
Note: Every console user of NavisAccess must have their own account and should be logged in as such. Do not run multiple instances of NavisAccess from the same NavisAccess login ID. A user who X-terms into the server machine must use a different NavisAccess login than other users currently logged in to that server machine.
Note: If you are starting Navis via a Telnet session from another Solaris machine, make sure you have properly exported the display. Telnet into the NavisAccess server 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.
Starting NavisAccess as a non-root user
By default, NavisAccess can only be started by a user with root privileges. To override this, enter the following at the command line:
chmod -R 777 navis_install_directory
where navis_install_directory is the name of the directory in which NavisAccess is installed. This command gives proper permissions to the files so they can be started by a non-root user.
For example, if NavisAccess is installed in a directory named “navis5”, you would enter:
chmod -fR 777 navis5
NavisAccess Installation and Administration Guide 2-21
Preparing Lucent devices for use with 3 NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 8.x)
Before NavisAccess can be used with Lucent MAX, TNT, and APX 8000 devices, running TAOS 8.x, several preparatory steps must be made. These are outlined below. Please make note of the minimum software requirements.
The Network Management Enable software option
To find out if you need to use the Network Management Software option, 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.
Note: You can also check whether you need the Network Management Enable software option by clicking Devices in the Examiner. The Network Management Bit column in the right pane will display Enabled if you have the Network Management Enable software option or Not Enabled if you do not have it.
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.
Call-Logging and SNMPv3 restrictions in TAOS 8.x
As of TAOS 8.x, call-logging data is no longer sent if the NavisAccess Software Option is not enabled on the device. There is a mechanism to generate call-logging without the Option for a limited time, for use in product evaluations. See the sections on enabling call-logging in this chapter for more details.
The Software Option is installed on devices using a hash code mechanism. See“Installing the hash codes” on page 3-17 for specifics.
SNMPv3 functionality is not available unless the NavisAccess Software Option is enabled.
NavisAccess Installation and Administration Guide 3-1 Preparing Lucent devices for use with NavisAccess MAX preparation
MAX preparation
Configuring SNMP Trap destinations for the MAX (TAOS 8.x)
The Lucent MAX products send alarm messages in the form of SNMP Traps. These Traps are sent to a management station (such as NavisAccess) 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 MAX 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). 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
3-2 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX preparation
8 Enter the SNMP community string for the MAX or Pipeline. For example: Comm=secret_string 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” below. 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 machine. For example: Dest=192.168.50.55 In a distributed NavisAccess 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 types. The menu will appear similar to the following:
11 Select the traps you wish to have sent to NavisAccess. Please consult the MAX documentation for explanations of available traps. 12 Save and close the SNMP Traps Profile.
Setting SNMP community strings for the MAX (TAOS 8.x)
SNMP validates each message with a password-like mechanism called a Community Name. SNMPv1 uses a Read and Read/Write community strings. SNMPv3 uses a user name/password combination.
NavisAccess supports both SNMPv1 and SNMPv3. If you are using SNMPv3, you must also follow the steps described in “Setting SNMP v3 for the MAX (TAOS 8.x)” on page 3-4.
NavisAccess Installation and Administration Guide 3-3 Preparing Lucent devices for use with NavisAccess MAX preparation
For SNMPv1, there are two communities defined on the MAX. • 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. • 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 must match what is specified by (on) the device. Otherwise, communication cannot be established with the device.
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 supports all three message types. 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 Save and close the Ethernet profile.
Setting SNMP v3 for the MAX (TAOS 8.x)
NavisAccess provides support for SNMP v3 user name/password authentication. The SNMP v3 user name and password must be set within NavisAccess, and also configured on the device.
Note: SNMPv3 functionality is only available if the NavisAccess Software Option is enabled on the device.
3-4 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX preparation
To configure SNMP v3 on the MAX: 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 SNMPv3 USM Users menu.
5 Assign a name for the profile, for example: Name=SNMPv3_Profile This name must be matched within NavisAccess. 6 Assign a password to the profile, for example: Passwd=snmp_password This password must be matched within NavisAccess. 7 Set the profile to Active=yes to turn on SNMPv3. 8 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. 9 Set the Auth Protocol parameter as follows: Auth Protocol=md5-auth MD5-Auth is the only protocol supported by NavisAccess. 10 The Priv Protocol parameter is not available in TAOS versions that are earlier than 9.x. 11 Save and close the profile.
Enabling Call-Logging on the MAX (TAOS 8.x)
In order for NavisAccess to receive call data from the MAX, the Call-Logging feature must be enabled and set to send data to NavisAccess.
Note: Call-logging data will not be sent unless the NavisAccess Software Option is enabled on the device. 30-day evaluations of call-logging are available. See “Enabling Call-Logging for evaluation purposes (TAOS 8.x)” on page 3-7 for details.
To configure Call-Logging for use with Access Watch: 1 Attach to the device via Telnet or the console port and log in with write access. 2 Open the Ethernet menu. 3 Open the Mod Config menu.
NavisAccess Installation and Administration Guide 3-5 Preparing Lucent devices for use with NavisAccess MAX preparation
4 Open the Call Logging menu. (You may need to scroll down the menu list to see this entry.)
5 Set the Call Log field to Yes. To do so, move the cursor to the field and press Enter. 6 Enter up to three Host IP addresses. These are NavisAccess machines to which Call Logging will send information. For example: Host #1 = 10.1.2.3 Host #2 = 10.1.2.4 Host #3 = 10.1.30.10 Each Host #n parameter can specify the IP address of one NavisAccess stand-alone server or call-logging receiver (distributed installation). The MAX 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. 7 If necessary, change the Dst Port value. This is the destination port through which the device will send information. The default value of 1646 is recommended. 8 Set the Call Log Timeout period from 10 to 30 seconds.
Note: This can be a value between 1 and 60 seconds. In most networks a value ranging from 10 to 30 seconds is appropriate. However, based upon network characteristics the value can be lower or higher than the recommended values. The device sends a request to the first host on the list of hosts specified and waits for a response from the server for the number of seconds specified in the Call Log Timeout parameter. If the device does not receive a response within that time, it sends a second request to the same server and waits for the same amount of time. If the device does not receive a response within the specified time-out, it sends a request to the next host on the list and repeats the process. 9 Enter a Call Logging Key (up to 20 characters). The key allows the device to send data to NavisAccess. The same Key entered on the device must also be entered in NavisAccess. This is similar in function to the community string, but not the same. A default Call Logging Key can be entered in NavisAccess using the Call Logging Key field on the Access Watch 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 Secret field. (For details on the Boxmap, see the NavisAccess online help or User Guide.) 10 The Acct-ID Base parameter determines if data is sent in Base 10 (decimal) or Base 16 (hexadecimal) format. This value must be set to 10 for Call Logging to work properly.
3-6 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX preparation
11 Set a Reset Timeout period, from 0 to 86400 seconds. (86400 seconds = 1 day.) Indicates the number of seconds that must elapse before the device returns to using the primary call log host (Host #1). The default zero disables the reset to the primary call log host. 12 Set the Allow Stop Only parameter. The device typically sends Start and Stop packets to the host to record connections. Authentication is required to send a Start packet. There are situations that the device will send a Stop packet without having sent a Start packet. These Stop packets have no user name. The Allow Stop Only parameter specifies whether the device should send a Stop packet with no user name. The default value is Yes. You can set this parameter to No to prevent the unit from sending Stop packets with no user name. 13 Set the Max Retry parameter. If the NavisAccess 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 Max 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.
Note: Call-logging retries should not be set to unlimited. For network performance reasons, network devices should not have call-logging retries set to infinite (a retry setting of zero). Call-logging retries should be set to a specific number, such as 3 or 4. 14 Set the Compat Mode parameter to VSA, as follows: Compat Mode=VSA 15 Save and close the Call Logging profile.
Enabling Call-Logging for evaluation purposes (TAOS 8.x)
If the NavisAccess Software Option is not available on the device, call-logging can be turned on for 30 days using the following procedure. 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.
Configuring SNMP security on the MAX (TAOS 8.x)
The SNMP Security feature on the MAX 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 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 machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess via Telnet or Xterm to not have to have their IP addresses included.)
Following are details about specifying which hosts can access the MIB.
NavisAccess Installation and Administration Guide 3-7 Preparing Lucent devices for use with NavisAccess MAX preparation
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 machine address. 7 Specify the IP addresses of hosts that will have SNMP read permission. The NavisAccess station must be included for NavisAccess 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. 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.
Configure new NASportID (TAOS 8.x)
The NASportID setting must be set to “yes”.
To configure the NASportID: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 Open the System menu. 4 Open the Sys Config menu. 5 Set the New NASportID to yes, as follows: NEW NASportID = Yes 6 Save and close the profile.
3-8 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX TNT preparation
MAX TNT preparation
Configuring SNMP Trap destinations for the TNT and APX 8000 (TAOS 8.x)
The Lucent TNT and APX8000 send messages in the form of SNMP Traps. These Traps are sent to a management station (such as NavisAccess) 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 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* = "" 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 lan-modem-enabled = yes ... Consult your TNT and APX8000 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 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 Installation and Administration Guide 3-9 Preparing Lucent devices for use with NavisAccess MAX 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 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 station. In a distributed NavisAccess installation, traps must be sent to the IP address of the machine on which the Scheduling Server has been installed. 8 Enable any class of Traps you want reported to NavisAccess. For example: set alarm-enabled = yes set security-enabled = yes set port-enabled = yes Consult the device documentation for details on these traps definitions. 9 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, community strings on the TNT and APX 8000 (TAOS 8.x)
SNMP validates each message with a password-like mechanism called a Community Name. SNMPv1 uses a Read and Read/Write community strings. SNMPv3 uses a user name/password combination.
NavisAccess supports both SNMPv1 and SNMPv3. If you are using SNMPv3, you must also follow the steps described in “Setting SNMPv3 for the TNT and APX 8000 (TAOS 8.x)” on page 3-12.
To enable SNMP and set security on the device: 1 Attach to the device via Telnet or through the console port.S 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 ]
3-10 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX TNT preparation
write-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 ] contact = "NMD, Bohemia" location = "NMD, Bohemia" queue-depth = 0 csm-modem-diag = no 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. 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 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 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 machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess 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 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
NavisAccess Installation and Administration Guide 3-11 Preparing Lucent devices for use with NavisAccess MAX TNT preparation
set write-access-hosts 5 = 10.2.50.124 When this parameter is set, only NavisAccess 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 11 Set the message type. NavisAccess 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.
For example, to set the message type to V1-and-V3, enter: set snmp-message-type = v1-and-v3 12 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by an “SNMP written” message.
Setting SNMPv3 for the TNT and APX 8000 (TAOS 8.x)
NavisAccess provides support for SNMP v3 user name/password authentication. The SNMP v3 user name and password must be set within NavisAccess, and also configured on the device.
Note: SNMPv3 functionality is only available if the NavisAccess Software Option is enabled on the device.
To configure SNMP v3 on the TNT or APX8000: 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. If an SNMPv3 profile has never been created before, you may need to enter: new SNMPV3-USM-USER 4 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
3-12 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX TNT preparation
auth-protocol = md5-auth priv-protocol = no-priv 5 Create a name for the profile. For example: set name = navis_snmpv3 This user name must be matched within NavisAccess. 6 Assign a password to the profile, for example: set password=snmp_password This password must be matched within NavisAccess. 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: 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. 10 NavisAccess only supports the no-priv parameter at this time. 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 = snmp_password active-enabled = yes read-write-access = no auth-protocol = md5-auth priv-protocol = no-priv
Enabling Call Logging on the TNT and APX 8000 (TAOS 8.x)
In order for NavisAccess to receive data from the MAX TNT, the Call-Logging feature must be enabled and set to send data to the NavisAccess.
Note: Call-logging data will not be sent unless the NavisAccess Software Option is enabled on the device. 30-day evaluations of call-logging are available. See “Enabling call-logging for evaluation purposes (TAOS 8.x)” on page 3-16 for details.
To configure Call Logging for use with NavisAccess: 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 returns a "CALL-LOGGING read" message, and a new command prompt.
NavisAccess Installation and Administration Guide 3-13 Preparing Lucent devices for use with NavisAccess MAX TNT preparation
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 = 0 call-log-key = "" 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 = 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 This points call logging information to the NavisAccess. Each Host #n parameter can specify the IP address of one NavisAccess stand-alone 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 = 0 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) must specify the same port number (the numbers must match). By default, NavisAccess uses port 1646. This is the recommended setting on the TNT. call-log-key = " " Enter a Call Logging key. The key allows the device to send data to NavisAccess. The same Key entered on the device must also be entered in NavisAccess. A default Call Logging Key can be entered in NavisAccess using the Default Secret field on the Access Watch Configuration tab found under Config > System Options.
3-14 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX TNT preparation
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 Secret field. call-log-timeout =0 The number of seconds the device waits 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. call-log-id-base = acct-base-10 Specifies if data is sent in Base 10 (decimal) or Base-16 (hexadecimal) format. Parameter settings are acct-base-10 and acct-base-16, respectively. This value must be set to acct-base-10 for NavisAccess to function properly. 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-stop-only = yes The device typically sends Start and Stop packets to the host to record connections. Authentication is required to send a Start packet. There are situations that the device will send a Stop packet without having sent a Start packet. These Stop packets have no user name. The call-log-stop-only parameter specifies whether the device should send a Stop packet with no user name. The default value is Yes. You can set this parameter to No to prevent the unit from sending Stop packets with no user name. call-log-limit-retry = 0 If the NavisAccess 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. 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 call logging receiver or stand-alone] Set call-log-host-2 = 150.10.10.12 [Alternate NavisAccess machine] Set call-log-port = 1646 set call-log-key = [Must match string entered via mysecretstring NavisAccess.] set call-log-timeout = 2 set call-log-id-base = acct-base-10 [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.
NavisAccess Installation and Administration Guide 3-15 Preparing Lucent devices for use with NavisAccess MAX TNT preparation
Enabling call-logging for evaluation purposes (TAOS 8.x)
If the NavisAccess Software Option is not available on the device, call-logging can be turned on for 30 days using the following procedure. 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.
Configure NAS port ID format (TAOS 8.x)
The NAS port ID format setting must be set to “yes”.
To configure the NAS port ID: 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 system This will return an "SYSTEM 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: name = TNT2 system-rmt-mgmt = yes v110-subaddress = 0 use-trunk-groups = no num-digits-trunk-groups = 1 ... new-nas-port-id-format = yes 5 Make sure the “new-nas-port-id-format” parameter is set to “yes.” If not, set it to yes as follows: set new-nas-port-id-format = yes 6 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a "SYSTEM written" message.
Configuring a Global IP address on TNT and APX 8000 (TAOS 8.x)
To ensure that the MAX TNT properly reports all needed data, such as call-logging packets, to NavisAccess, a global IP address must be configured.
To configure a global IP address:
3-16 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess MAX TNT preparation
1 Attach to the MAX TNT via Telnet or through the console port. 2 Log in with write access 3 At the command prompt, enter: read ip-g This will return an "IP-GLOBAL read" message, and a new command prompt. 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 to the IP address of the MAX TNT. 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.
Installing the hash codes
Each Lucent MAX, MAX TNT, APX 8000, TNT, and Pipeline 220 device requires the NavisAccess Software Option in order to be managed using NavisAccess. In addition, APX 8000, MAX TNT, MAX 20xx and MAX 60xx devices require the NavisAccess Software Option for Voice over IP management if Voice over IP (VOIP) calls are going to be made using the devices. The VOIP Software Option is in addition to the general NavisAccess Software Option.
To purchase the Option and receive a hash code, contact your Lucent Technologies sales representative. A brief outline of the procedure is provided below.
To enter the hash code: 1 A hash code is received from Lucent Technologies. The code consists of several lines of text. 2 Connect to the device via Telnet or console. 3 Enter device debug mode. This brings up the > prompt. 4 Type the hash code and hit Return. Alternately, if you have the hash code in electronic format, cut and paste the codes onto the screen. 5 A confirmation message will display. 6 Reset the device to enable the Software Option.
NavisAccess Installation and Administration Guide 3-17 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
Before NavisAccess can be used with Lucent TNT, APX8000, and MAX devices, running TAOS v9.0, several preparatory steps must be made. These are outlined below. Please make note of the minimum software requirements.
About the NavisAccess Software Option
Each Lucent MAX, TNT, and APX8000 device requires the NavisAccess Software Option (Network Management Enable) in order to be managed using NavisAccess.
How do I know if I need the Network Management Enable software option? • 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.
Note: You can also check whether you need the Network Management Enable software option by clicking Devices in the Examiner. The Network Management Bit column in the right pane will display Enabled if you have the Network Management Enable software option or Not Enabled if you do not have it.
How do I know if I need the Network Management Enable software option on my MAX? • Telnet into the device, and
Using the arrow key, scroll to Net Mgmt. If installed, the row will read "Net Mgmt Installed", and will appear like the following:
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.
3-18 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
TNT and APX8000 Preparation
When preparing the TNT or APX8000 device for either SNMP v1 or SNMP v3 traps, and for call-logging, please be sure to complete the steps in the order they are presented. Note that SNMP v3 configuration is preferred.
Enabling SNMP v1 and configuring SNMP parameters on the TNT and APX8000 (TAOS 9.0)
SNMP validates each message with a password-like mechanism called a Community String. SNMPv1 uses a Read and Read/Write community strings.
NavisAccess supports both SNMPv1 and SNMPv3. If you are using SNMPv1, you must follow the steps described below to set SNMPv1 for the TNT and APX8000.
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 read-access-hosts = [ 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 ] contact = "NMD, Bohemia" location = "NMD, Bohemia" queue-depth = 0 csm-modem-diag = no snmp-message-type = v1 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.
NavisAccess Installation and Administration Guide 3-19 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
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 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 machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess via Telnet or X-term 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 stations logging in from the set IP addresses will be granted read-access to the device. 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 stations logging in from the set IP addresses will be granted write-access to the device. 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 Set the message type to V1, enter: set snmp-message-type = v1
3-20 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
10 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 v1 trap destinations for the TNT and APX8000 (TAOS 9.0)
The Lucent TNT and APX8000 sends messages in the form of SNMP Traps. These Traps are sent to a management station 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
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
NavisAccess Installation and Administration Guide 3-21 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
use-exceeded-enabled = yes password-enabled = yes fr-linkup-enabled = yes fr-linkdown-enabled = yes radius-change-enabled = yes lan-modem-enabled = yes slot-profile-change-enabled = yes power-supply-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 atm-pvc-failure-trap-enabled = no ...
Note: Consult your TNT or APX8000 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 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 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 station.
3-22 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
In a distributed NavisAccess 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. 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 device should send security-event traps to the host (specified by the host-address) as follows: set security-enabled = yes
Security events notify users of security problems and tracks access to the unit.
Note: Consult the device documentation for further information on defining the parameters. 11 Enable any class of Traps you want reported to NavisAccess. For example: set alarm-enabled = yes set security-enabled = yes set port-enabled = yes set lim-sparing-enabled = yes set interface-sparing-enabled = yes set secondary-controller-state-change-enabled = yes
Note: Consult the device documentation for details on these trap definitions. 12 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 TNT and APX8000 (TAOS 9.0)
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 TNT and APX8000.
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:
NavisAccess Installation and Administration Guide 3-23 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
enabled = no read-community = public read-write-enabled = no read-write-community = write contact = "NMD, Bohemia" location = "NMD, Bohemia" queue-depth = 0 csm-modem-diag = no snmp-message-type = 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. 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 must match what is specified on the device. Otherwise, communication cannot be established with the device. 7 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 8 Set the message type V3, enter: set snmp-message-type = v3 9 Set the security-level to auth-nopriv. For Example: set security-level = auth-nopriv
Note: The security-level must be set to auth-nopriv. Currently, NavisAccess only supports the auth-nopriv SNMPv3 setting. 10 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by an “SNMP written” message.
3-24 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
Creating an SNMP v3 user profile for the TNT and APX8000 (TAOS 9.0)
NavisAccess provides support for SNMP v3 user name/password authentication on the TNT and APX8000 Device. The SNMP v3 user name and password must be set within NavisAccess, and also configured on the device.
Note: SNMPv3 functionality is only available if the NavisAccess Software Option is enabled on the device.
To configure SNMP v3 on the TNT or APX8000: 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 = 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. 7 Enable the profile by entering: set active-enabled = yes The read-write-access parameter specifies whether or not the user name has write- access to the device. 8 Set to Yes to enable write-access, or No to disable. For example: 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. The priv-protocol parameter is not available at this time. 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
NavisAccess Installation and Administration Guide 3-25 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
The password must be matched with NavisAccess. The priv key is not supported at this time. 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 an SNMP v3 trap notifications profile for the TNT and APX8000 (TAOS 9.0)
When configuring SNMP trap destinations for the TNT or APX8000, 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.
Creating 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/
3-26 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
8 Finish the configuration by writing the new parameters to the device, as follows: write 9 Return to the trap profile, and enter the tag values that are used to select target addresses for a particular operation: notify-tag-list = v3trapprofile
Creating an SNMP v3 target profile for the TNT and APX8000 (TAOS 9.0)
When configuring SNMP trap destinations for the TNT or APX8000, 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.
Creating 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/
NavisAccess Installation and Administration Guide 3-27 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
security-level = auth-nopriv
Note: auth-nopriv is the only security level supported by NavisAccess. 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 TNT and APX8000 (TAOS 9.0)
The Lucent TNT and APX8000 sends messages in the form of SNMP Traps. These traps are sent to a management station 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 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 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
3-28 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
ascend-enabled = yes console-enabled = yes use-exceeded-enabled = yes password-enabled = yes fr-linkup-enabled = yes fr-linkdown-enabled = yes radius-change-enabled = yes lan-modem-enabled = yes slot-profile-change-enabled = yes power-supply-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 atm-pvc-failure-trap-enabled = no
Note: Consult your TNT or APX8000 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 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 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 station.
NavisAccess Installation and Administration Guide 3-29 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
In a distributed NavisAccess installation, traps must be sent to the IP address of the machine on which the Scheduling Server has been installed. 8 Enter the type of trap notification you want reported to NavisAccess. 9 When running SNMP version 3, you must create a Notification Profile (refer to Creating a SNMP v3 trap notification profile on the TNT and APX8000 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. Once created, enter the tag values that are used to select target addresses for a particular operation: set notify-tag-list = v3trapprofile 10 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 TNT and APX8000. Once created, enter the target parameter for the traps to be sent: set target-params-name =
Note: Consult the device documentation for further information on defining the parameters. 12 Enable any class of Traps you want reported to NavisAccess. For example: set alarm-enabled = yes set security-enabled = yes set port-enabled = yes
Note: Consult the device documentation for details on these trap definitions. 13 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 APX8000 (TAOS 9.0)
The soft IP address is the ‘single’ IP address that the device uses for call-logging, radius and other IP traffic after a redundancy switchover. NavisAccess uses the soft IP address to discover and communicate with the device.
To configure a soft IP address on the APX8000: 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 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
3-30 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
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. For example: set ip-address = 10.2.3.4/1 6 Set the proxy-mode to always. For example: set proxy-mode = always The Proxy-Mode specifies under what conditions the device responds to Address Resolution Protocol (ARP) requests with its own Media Access Control (MAC) address. ‘Always’ specifies that the device responds to an ARP request with its own MAC address if the request matches any IP address to which the device has a route. 7 Finish the configuration by writing the new parameters to the device, as follows: write This will be followed by a "IP-INTERFACE written" message.
Enable call logging on the TNT and APX8000 (TAOS 9.0)
In order for NavisAccess to receive data from the TNT and APX8000, the Call Logging feature must be enabled and set to send data to NavisAccess. 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 Line Groups and Services.
Note: When receiving a call-logging packet, NavisAccess will determine the device’s IP Address in the following order: • If the system-ip-addr parameter in ip-global is set, Navis will use this address in the packet. • If the system-ip-addr parameter in ip-global is not set, the Soft IP address will be used. • If neither the system-ip-addr parameter in ip-global or the Soft IP is set, the Ethernet IP will be used.
Note: Call-logging data will not be sent unless the NavisAccess Software Option is enabled on the device. 30-day evaluations of call-logging are available. See Enabling call-logging for evaluation purposes for details.
NavisAccess Installation and Administration Guide 3-31 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
To configure Call Logging for use with NavisAccess: 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 an "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 = 0 call-log-key = "" 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 5 Set the call-log enable parameter to “yes” as follows: set call-log-enable = yes 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 These parameters point call logging information to the NavisAccess. Each Host #n parameter can specify the IP address of one NavisAccess stand-alone 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 = 0
3-32 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
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) must specify the same port number (the numbers must match). By default, NavisAccess uses port 1646. This is the recommended setting on Lucent devices. call-log-key = " " Enter a Call Logging key. The installed default is “ascend”. The key allows the device to send data to NavisAccess. The same Key entered on the device must also be entered in NavisAccess. A default Call Logging Key can be entered in NavisAccess 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. call-log-id-base = acct-base-16 Specifies if data is sent in Base 10 (decimal) or Base-16 (hexadecimal) format. Parameter settings are acct-base-10 and acct-base-16, respectively. This value must be set to acct-base-16 for NavisAccess to function properly. 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-stop-only = yes The device typically sends Start and Stop packets to the host to record connections. Authentication is required to send a Start packet. There are situations that the device will send a Stop packet without having sent a Start packet. These Stop packets have no user name. The call-log-stop-only parameter specifies whether the device should send a Stop packet with no user name. The default value is No. You can set this parameter to No to prevent the unit from sending Stop packets with no user name. call-log-limit-retry = 0 Enter a call-log-limit-retry of 2 or 3. If the NavisAccess 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. call-log-server-index = host-1 The currently active call logging server index. The default setting is host-1. call-log-radius-compat = vendor-specific Enables or disables vendor-specific Attribute (VSA) compatibility mode when the TNT or APX8000 is using RADIUS for call-logging to NavisAccess. The setting must be vendor-specific.
NavisAccess Installation and Administration Guide 3-33 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
call-log-multi-packet = no Each call-logging packet sent contains a header and attributes. For each packet sent, the device also sends packet-related data, or “overhead” data across the network. All told, the device constantly sends data across the network tying up your valuable resources. The call-log-multi-packet parameter combines the headers, and consolidates the attributes of multiple packets so they exist in one packet. This not only saves the cost of the packets being sent, but also the “overhead”, or packet-related data sent by the device each time a packet is sent.
Note: When applied, multi-packets may cause the traffic pattern to shift. Where before you had packets sent at a steady rate, now you may notice that for a time traffic is less than normal, and at the interval, as the multi-packets are sent by the device, there may be a burst of traffic. 6 Set the call logging MultiPacket enable to yes or no. Yes is recommended. 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 call logging receiver or stand-alone]
Set call-log-host-2 = 150.10.10.12 [Alternate NavisAccess machine]
Set call-log-port = 1646
set call-log-key = mysecretstring [Must match string entered via NavisAccess.]
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] vendor-specific
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 (TAOS 9.0)
If the NavisAccess Software Option is not available on the device, call-logging can be turned on for 30 days using the following procedure. 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.
3-34 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
Setting SNMP community strings for the MAX (TAOS 9.0)
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 supports both SNMPv1 and SNMPv3 on the MAX devices.
For SNMPv1, there are two communities defined on the MAX. • 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. • 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 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 supports all three message types on the TNT and APX8000 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.
NavisAccess Installation and Administration Guide 3-35 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
SNMP v3 users: Set the Security Level parameter to auth-nopriv. For example: Security Level=auth-nopriv
Note: NOTE: The security-level must be set to auth-nopriv. If this is not done, NavisAccess will not discovering the device. NavisAccess only supports auth-nopriv. 10 Save and close the Ethernet profile.
Enable Call-Logging on the MAX (TAOS 9.x)
In order for NavisAccess to receive call data from the MAX, the Call-Logging feature must be enabled and set to send data to NavisAccess.
Note: Call-logging data will not be sent unless the NavisAccess Software Option is enabled on the device. 30-day evaluations of call-logging are available. See “Enable call-logging for evaluation purposes (TAOS 9.0)” on page 3-34 for details.
To configure Call-Logging for use with Access Watch: 1 Attach to the device via Telnet or the console port and log in with write access. 2 Open the Ethernet menu. 3 Open the Mod Config menu. 4 Open the Call Logging menu. (You may need to scroll down the menu list to see this entry.)
5 Set the Call Log field to Yes. To do so, move the cursor to the field and press [Enter]. 6 Enter up to three Host IP addresses. These are NavisAccess machines to which Call Logging will send information. For example: Host #1 = 10.1.2.3 Host #2 = 10.1.2.4 Host #3 = 10.1.30.10 Each Host #n parameter can specify the IP address of one NavisAccess stand-alone server or call-logging receiver (distributed installation). The MAX 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. 7 If necessary, change the Dst Port value. This is the destination port through which the device will send information. The default value of 1646 is recommended.
3-36 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
8 Set the Call Log Timeout period from 1 to 60 seconds. The device sends a request to the first host on the list of hosts specified and waits for a response from the server for the number of seconds specified in the Call Log Timeout parameter. If the device does not receive a response within that time, it sends a second request to the same server and waits for the same amount of time. If the device does not receive a response within the specified time-out, it sends a request to the next host on the list and repeats the process. 9 Enter a Call Logging Key (up to 20 characters). The key allows the device to send data to NavisAccess. The same Key entered on the device must also be entered in NavisAccess. This is similar in function to the community string, but not the same. A default Call Logging Key can be entered in NavisAccess using the Call Logging Key field on the Access Watch 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 Secret field. (For details on the Boxmap, see the NavisAccess online help or User Guide.) 10 The Acct-ID Base parameter determines if data is sent in Base 10 (decimal) or Base 16 (hexadecimal) format. This value must be set to 10 for Call Logging to work properly. 11 Set a Reset Timeout period, from 0 to 86400 seconds. (86400 seconds = 1 day.) Indicates the number of seconds that must elapse before the device returns to using the primary call log host (Host #1). The default zero disables the reset to the primary call log host. 12 Set the Allow Stop Only parameter. The device typically sends Start and Stop packets to the host to record connections. Authentication is required to send a Start packet. There are situations that the device will send a Stop packet without having sent a Start packet. These Stop packets have no user name. The Allow Stop Only parameter specifies whether the device should send a Stop packet with no user name. The default value is Yes. You can set this parameter to No to prevent the unit from sending Stop packets with no user name. 13 Set the Max Retry parameter. If the NavisAccess 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 Max 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.
Note: Call-logging retries should not be set to unlimited. For network performance reasons, network devices should not have call-logging retries set to infinite (a retry setting of zero). Call-logging retries should be set to a specific number, such as 3 or 4. 14 Set the Compat Mode parameter to VSA, as follows: Compat Mode=VSA 15 Save and close the Call Logging profile.
Configuring trap destinations for the MAX (TAOS 9.0)
The Lucent MAX devices send alarm messages in the form of SNMP Traps. These Traps are sent to a management station 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.
NavisAccess Installation and Administration Guide 3-37 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
To configure the MAX 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). 7 Turn on traps for alarm events, port state changes, security events and OSPF events as needed. Alarm=Yes Port=Yes Security=Yes Enter the SNMP community string. For example: Comm=secret_string 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” below.
Note: To turn off SNMP traps, delete the value for the Comm parameter and set the next parameter (Dest) to 0.0.0.0. 8 Specify the IP address of the NavisAccess machine. For example: Dest=192.168.50.55 In a distributed NavisAccess 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. 9 Open the “Enable traps...” profile to set specific trap to yes. The menu will appear similar to the following:
3-38 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
10 Select the traps you wish to have sent to NavisAccess. Please consult the MAX documentation for explanations of available traps. 11 Save and close the SNMP Traps Profile.
Setting SNMP v3 for the MAX (TAOS 9.0)
NavisAccess provides support for SNMP v3 user name/password authentication. The SNMP v3 user name and password must be set within NavisAccess, and also configured on the device.
Note: SNMPv3 functionality is only available if the NavisAccess Software Option is enabled on the device.
To configure SNMP v3 on the MAX: 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 SNMPv3 USM Users menu. 5 Assign a name for the profile, for example: Name=SNMPv3_Profile This name must be matched within NavisAccess.
NavisAccess Installation and Administration Guide 3-39 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
6 Assign a password to the profile, for example: Passwd=snmp_password This password must be matched within NavisAccess. 7 Set the profile to Active=yes to turn on SNMPv3. 8 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. 9 Set the Auth Protocol parameter as follows: Auth Protocol=md5-auth MD5-Auth is the only protocol supported by NavisAccess. 10 The Priv Protocol parameter is not available at this time. 11 Save and close the profile.
Configuring SNMP Security on the MAX (TAOS 9.0)
The SNMP Security feature on the MAX 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 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 machines must be included, including primary server, secondary servers and workstations. (Machines accessing NavisAccess via Telnet or X-term 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 machine address. 7 Specify the IP addresses of hosts that will have SNMP read permission. The NavisAccess station must be included for NavisAccess 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
3-40 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
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. 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.
Configure New NASportID (TAOS 9.0)
The NASportID setting must be set to “yes”.
To configure the NASportID: 1 Attach to the device via Telnet or through the console port. 2 Log in with write access. 3 Open the System menu. 4 Open the Sys Config menu. 5 Set the New NASportID to yes, as follows: NEW NASportID = Yes 6 Save and close the profile.
Converting Call Logging files to comma-separated Variable (CSV) Files
CLD2CSV command-line utility
CLD2CSV is a command line tool which allows a user to convert call-logging files (cld files) into csv files. Csv files are comma separated text files that can be imported into Excel.
This allows for the call-logging files to be converted into a more readable format, which enables you to use the files for customized reporting.
How CLD2CSV converts call-logging files
When converting call-logging files CLD2CSV uses a configuration file called cld2csv.ini. This file, which is created from the radius dictionary files, specifies what columns will be present in the output and in what order.
The configuration file contains one line for each attribute that need to be generated in the output. The following shows the default cld2csv.ini file, located in: \\
NavisAccess Installation and Administration Guide 3-41 Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
#(AttributeId, VendorId) NAS-Identifier, 0 Acct-Status-Type, 0 NAS-Port-Type, 0 Client-Port-DNIS, 0 Caller-Id, 0 Acct-Session-Id, 0 Acct-Session-Time, 0 Ascend-PreSession-Time, 529 Ascend-Connect-Progress, 529 Ascend-Disconnect-Cause, 529
This default file contains the most common Attributes used by NavisAccess.
This file can be modified to include Attributes of your choice for further customizing.
Modifying the cld2csv.ini file
The cld2csv.ini file contains two columns: Vendor ID’s, and Attribute ID’s.
These IDs are obtained through the radius files that ship with NavisAccess. These files are located in \\
Examples of these are: vendors.radius, dictionary.radius, and ascend.radius.
The vendors.radius file contains the Vendor ID #’s of the other radius files, for example: [vendors.radius] 0 dictionary.radius 529 ascend.radius ...
Where 0 and 529 are the Vendor ID #’s.
The dictionary.radius, and ascend.radius files contain the Attribute ID’s, for example:
NAS-Identifier Acct-Status-Type NAS-Port-Type ... Ascend-PreSession-Time Ascend-Connect-Progress ...
Select the Vendor and Attribute IDs you wish from the radius files supplied, and add them to the cld2csv.ini.
3-42 NavisAccess Installation and Administration Guide Preparing Lucent devices for use with NavisAccess Preparing Lucent devices for use with NavisAccess (TAOS 9.0)
Output of the converted call-logging files
The output file has Timestamp as the first column followed by all the columns that you specify in the cld2csv.ini file. An empty value is generated for the columns that are absent in the call logging packets. By default the first line of the output file is a header line showing what columns are present in the output.
An example of the output is shown below: Packet Timestamp,“NAS-Identifier [Attribute:4 Vendor:0]” “Fri Oct 11 2000 17:15:16”,”219.247.46.117” “Fri Oct 11 2000 17:15:16”,”219.247.46.57”
Converting your .cld files 1 If necessary, modify the cld2csv.ini file as described above. 2 From the command line, type: cld2csv 3 If desired, add a switch to the command in the following format: cld2csv [-c ] [-h] [-o
Switch Description
-c This is an optional parameter that specifies the config file to use when converting from .cld to .csv. If this option is not present, then the cld2csv.ini file present in the current directory is used. If no cld2csv.ini file is present in the current directory an error will be generated.
-h This option suppresses the header line in the output.
-o This option is used to specify the name of the output file. By default the tool generates the output on the terminal.
The cld2csv utility reads in the cld2csv.ini file, organizing your output on the terminal. If the -o switch is selected, the output will go to the file you have named.
NavisAccess Installation and Administration Guide 3-43
Device Discovery 4
Introduction to device Discovery
Discovery gathers SNMP information about the devices on your network and creates a database. There are four ways to run Discovery: • Automatic: Call Logging discovers network resources via call logging packets received by NavisAccess. In order for Call Logging discovery to occur, Call Logging must be enabled on your Lucent MAX and MAX TNT devices • Manual: discovers one particular device at a time (using the New Device applet). • 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. • Discovery using SNMP Exploration: 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.
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 to populate Examiner and to create the Internet Map. The Internet Map graphically depicts all devices (access servers, routers, switches) found, as well as the subnetworks linked to these devices and the actual connections. Any device can be managed from the Internet Map or 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.
NavisAccess Installation and Administration Guide 4-1 Device Discovery Introduction to device Discovery
Visual indicators for Discovery
The Examiner window uses visual indicators to denote a device’s state in the network. The following table summarizes the possibilities:
Table 4-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 No No Attempting to discover the device for yellow ’X the first time.
Question mark with Yes No Attempting to discover device for the yellow ’X first time.
Question mark with No Yes Attempted initial discovery, but the red ’X device failed to respond. Device type remains unknown.
Device icon with Yes Yes The device has been previously red ’X discovered However, the last attempt to discover the device has failed.
Device icon Yes Yes The last attempt to discover the device was successful.
4-2 NavisAccess Installation and Administration Guide Device Discovery Automatic Discovery of network resources
Automatic Discovery of network resources
NavisAccess automatically discovers all network resources via Call Logging packets it receives. No operator interception is required.
Note: In order for Call Logging discovery to occur, Call Logging must be enabled on your Lucent MAX and MAX TNT devices.
Networks that Do Not Support SNMP
To discover devices on networks that do not support SNMP, use a Master List and the MLConfig utility. For detailed information on using a Master List and the MLConfig utility to discover devices, please refer to Chapter 7, “The Master List.”
Using NavisAccess for the first time 1 Access the DNIS Translation table Tools > DNIS Translation Table to ensure that all DNISs conform to the default 10 digit length defined by NavisAccess. All incoming DNISs must be at least 10 digits in order for NavisAccess to create/discover devices and services from your incoming call logging packets. Refer to the section “Configuring the DNIS Translation table” on page 4-3 for full details. 2 Configure your system options. Configure > System Options > – SNMP Security tab - enter the read/write community strings, global user-names and passwords for read-write access on all devices. – Access Watch tab - Enter the Call Logging key and Port. Both must match the device(s) configuration. Refer to the NavisAccess User’s Guide, “Configuring System Options” chapter for full details.
Note: The settings for SNMP Security and Access Watch are global. The settings affect all workstations in a client/server setup.
Configuring the DNIS Translation table
The DNIS Translation table holds all the DNISs (the phone number the user calls to connect to a TNT) received and registered by NavisAccess.
By default, NavisAccess requires a 10 digit minimum DNIS length to ensure uniqueness for each DNIS. For example, if NavisAccess receives two 4 digit DNISs -- “1234” -- that are for two different services (516-1234, 338-1234), NavisAccess creates only one service called 1234 instead of two because NavisAccess does not recognize each one as being a unique number and, therefore, cannot distinguish one DNIS from the other. For this reason, we recommend a minimum 10 digit DNIS.
NavisAccess Installation and Administration Guide 4-3 Device Discovery Automatic Discovery of network resources
You must modify all DNISs which are 9 digits or less in the DNIS Translation table to be a minimum of ten digits for NavisAccess to recognize them as unique numbers. For example, in the United States the basic phone number consists of 7 digits, not counting the area code. To make it a ten digit number, add the area code as part of the number.
Note: For DNISs outside of the United States, the basic phone number may be 10 or more digits. If your basic number is a 10 digit number, you need to increase it by at least one digit to make each number unique.
Using the DNIS Translation table
To access the DNIS Translation table, Tools >DNIS Translation.
Below is an example of this table.
Notice that the table displays full and partial DNISs. All partial DNISs must be translated to full DNISs, in this case 10 digits. You can add digits to DNISs by editing the number.
To edit a partial DNIS: 1 Right-click on the DNIS that you would like to edit. 2 Click on the Edit Selected Items pop-up. The DNIS Translation dialog box displays, showing you the partial DNIS. Notice that the OK button is grayed out.
3 Enter the required digits to the DNIS in the Fully Populated Dnis field. The OK button is now activated.
4-4 NavisAccess Installation and Administration Guide Device Discovery Manual Discovery
4 Click OK when done. The change is immediate.
Note: Once you translate the partial DNIS to a full DNIS, you cannot delete the DNIS, you can only edit it.
Changing the DNIS default minimum length
Even though NavisAccess is configured with a ten digit DNIS default, you may change this default if a different minimum is required for your site.
Note: The new default only takes effect for new calls (calls that come in after the default has been changed).
To change the default, in a distributed environment, you must run setminimumdnisdigits from the NavisAccess Server that contains the Scheduling Server component.
If you are not sure which server that is, run nautil status on the servers. One of the Servers will output the status of srm server. That is the machine that contains the Scheduling Server component. 1 Access the command line, change to the NavisAccess installation directory and enter the following argument. setminimumdnisdigits n where n is the number of digits for the new DNIS default. The DNIS default may be from 4 to 24 digits. 2 Access the DNIS Translation table (Tools > DNIS Translation). 3 Right-click on any DNIS. The DNIS Translation pop-up displays. 4 Edit the DNIS to conform to the new default. For example, if the original DNIS minimum was 10 and the new minimum is 13, you must add 3 more digits to the DNIS. 5 Click OK.
All new incoming DNISs now require the new minimum DNIS default.
Manual Discovery
Manually adding new devices
Menu Bar: File > New > Device
The New Device feature is used to manually discover your network (that is, discover one device at a time) and populate the database. Once the database is populated, you can use Examiner and the Internet Map 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-related device in the SNMPv1 Read Community field. If no community
NavisAccess Installation and Administration Guide 4-5 Device Discovery Discovery via the Master List
string is specified, the default community string defined in NavisAccess Configuration (Configure > System Options) is used. If SNMPv3 supported device: Enter an optional, valid, read-only user name and password for the SNMPv3-related 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 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 and shown on a newly rendered Internet Map.
Discovery via the Master List
The Master List
With the ever-growing need to manage complex networks, the ways that Administrators monitor and configure these networks are changing frequently.
NavisAccess 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, upon discovery, reads the Master List and attempts to discover all of the devices on the list. Once discovered, NavisAccess 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 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. For further information on creating a Master List from scratch, refer to the NavisAccess User Guide.
However, creating a Master List from scratch for a big network can be a daunting task. For this reason, NavisAccess provides the ML Config Launch Options window which enables you to export the NavisAccess database information to generate a Master List. The list can then be easily updated manually to incorporate and minor changes in the network.
4-6 NavisAccess Installation and Administration Guide Device Discovery Discovery via the Master List
Select Tools>ML Config Launcher to open the ML Config Launch Options window. The ML Configurator can also be opened and run from the command line. For further information, refer to the NavisAccess User Guide.
Note: Before running the ML Config Launcher, NavisAccess should discover the network initially so that the database gets populated with information about devices available on the network.
ML Config Launch options
Menu: Tools>ML Config Launcher
The ML Config Launch Options dialog provides the ability of synchronizing the information in the NavisAccess database with that in the Master List. It allows you to export the device and interface information from the NavisAccess database to generate the Master List.
The ML Config Launch Options include Export and Import options: • Export options Export to Master List - Select the Master List file to export device information to. For further information on the Export process, refer to Exporting the Master List. • Import options Import Master List file name - Select the Master List file to import device information from. For further information on the Import process, refer to Importing the Master List. Log File Name - Specify a Log file in which ML Config places log messages. The Default MLConfigmmddhhmm.log file is created by NavisAccess. For further information about the logging process, refer to Logging process information. 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. 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.
NavisAccess Installation and Administration Guide 4-7 Device Discovery Discovery using SNMP exploration
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 ML Config should wait for a device to be discovered before timing out. No Discovery - Check No Discovery to have ML Config not discover any new devices that are specified in the Master List. Delete Device Info - Click to have ML Config 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 only will contain 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. No Log - Check to have ML Config not create a log file. If this is selected, no logging will be done.
Discovery using SNMP exploration
Menu Bar: Tools > Explorer
Explorer is run to automatically discover your network and populate the database. Once the database is populated, you can use Examiner and the Internet Map to view your network.
Explorer can be run manually, or a schedule can be created to run the Explorer at a pre-set time. If your network is frequently changing (new devices, moved devices, swapped cards, etc.), 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 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. Routing Table Discovery 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 will not scan the routing table during the course of its discovery. Seed Router Provide the IP Address for your “Seed Router.” This router is defined as the starting point for discovery of your network. Lucent MAX, MAX TNT and Pipeline devices may be selected as Seed Routers. Node Discovery Select to have NavisAccess find all system nodes. This option is not recommended for most networks.
4-8 NavisAccess Installation and Administration Guide Device Discovery Discovery using SNMP exploration
NT-Station Discovery Select to have NavisAccess discover all NT workstations and servers. This option is not recommended for most networks.
Note: To be successfully discovered, the NT machine must have SNMP Service enabled. Save as Default With this option enabled, when Explorer is run for a second time it will begin from the point at which it left off. That is, it will not rediscover devices already discovered. This option is selected by default and is recommended, particularly for large networks. Pass Establish the number of passes which auto discovery will make. The range for the number of passes is from 1 to 10. 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. 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 [Start] button begins the auto detection process. Discovered components will populate Examiner and they will also be used to generate the Internet Map. As devices are added to the database, they are represented by an icon in Examiner and shown on a newly rendered Internet Map.
NavisAccess Installation and Administration Guide 4-9 Device Discovery Troubleshooting/restarting Discovery
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. • The SNMP timeout setting needs to be increased. See the SNMP Tab under System Options for details. 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 for details on what a device display indicates.
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.
4-10 NavisAccess 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 rediscover. The standard [SHIFT] and [CTRL] key selection methods apply. 3 Click [Discover]. The device Discovery process restarts. If the discovery completes successfully, the device icon and background color are automatically updated.
NavisAccess Installation and Administration Guide 4-11
Security 5
Security in NavisAccess
Security in NavisAccess 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 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, AccessWatch, 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 AccessWatch feature but only data that belongs to IPS1.
Another example is the user may be permissioned to launch AccessWatch, but cannot view the feature function “Abnormally Terminated Calls”.
NavisAccess Installation and Administration Guide 5-1 Security Users and user groups
Users and user groups
Users in NavisAccess 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 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.
CNM Admin (Customer All CNM features and functions Navigation Management) Data Access can be assigned per customer.
Pre-defined user groups
Table 5-2. Pre-defined User Groups
User Group Type Permissioned Access
Administrator (Data & Feature All features, functions and data. Including adding Access) and 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 (Customer Navigation All CNM User Group features and functions. Data Management) (Feature Access) Access can be assigned per customer.
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.
5-2 NavisAccess Installation and Administration Guide Security Users and user groups
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. 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 access rights to the data the Administrator desires.
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 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.
NavisAccess 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 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 database by limiting their access to certain NavisAccess functions. To see a complete list, refer to Pre-defined User Group permissioned features and functions. Once the user has access to the NavisAccess function, the Administrator must then grant access rights to the data 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 to access the desired data. By assigning a member to an “Access Data User Group”, the member receives 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.
Pre-defined user group access rights scenario
Note: This scenario assumes that the Administrator has 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.
NavisAccess Installation and Administration Guide 5-3 Security Users and user groups
• 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 has four pre-defined User Groups, each 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 Database.
Manager To manage that data the in the NavisAccess All features except User Manager. A Manager Database which is permissioned by the Admin User Group member does not have permission to User Group member. create and edit Users and User Groups.
5-4 NavisAccess Installation and Administration Guide Security Users and user groups
Table 5-3. Pre-defined User Group Access Rights (continued)
User Group Motivation Feature Access
Operator To ensure the smooth operation of the An Operator User Group member does not have NavisAccess database by monitoring the data permission to change any of the data assigned by which is assigned by the Admin User group the Admin User Group member, but he does member. If an Operator detects a problem, a have the ability to run reports on the data, which Manager User group member should be helps to ensure a smooth operation. contacted to remedy the problem. Features include: Examine, Reports, AccessWatch, Viewer, Sessions Overview, Wan Line Table, Digital Line Configuration, Discovery, Event Viewer, System Log Monitor (Windows NT only), Event History.
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 to User Group member. 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: Examine, AccessWatch, Reports, Event Viewer.
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 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
AccessWatch AccessWatch Y Y Y
AccessWatch Expansion Y Y N
AccessWatch No Expansion Y N N
ActiveSessions ActiveSessions Y N N
Active Sessions Active Sessions Y N N
Active Sessions Disconnect Y Y Y
NavisAccess Installation and Administration Guide 5-5 Security Users and user groups
Table 5-4. Pre-defined User Group features and functions (continued)
Feature Feature Function Manager Operator CNM User
DB Maintenance DB Maintenance Y N N
Device Card Code Device Card Code YNN Manager Manager
Device Watch Device Watch Y N N
Device Watch No Expansion Y N N
Examiner Examiner Y Y Y
Examiner Show Connections Y Y N
Examiner Show Customers N N N
Examiner Show Devices Y Y Y
Examiner Show Groups Y Y N
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
Global Ops Add Service Y N N
Global Ops Add Trunk Group Y N N
Global Ops Delete Customer Y N N
Global Ops Delete Device Y N N
Global Ops Delete DNIS Y N N
Global Ops Delete Group Y N N
Global Ops Delete Hunt 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 Delete Trunk Group Y N N
5-6 NavisAccess 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 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 DNIS Y N N
Global Ops Rename Group Y N N
Global Ops Rename Hunt YNN Group
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
Global Ops Rename Trunk YNN Group
MLConfig MLConfig Y N N
PDV Device PDV Device YYN Summary Summary
PDV Interface PDV Interface YYN Summary Summary
PDV Service PDV Service YYY Summary Summary
Report Exec Report Exec Y Y Y
Account Disconnect Last Completed Day Y N N
Account Disconnect Last Completed YNN Hour
Account Disconnect Last Completed Day Y N N By Line
NavisAccess 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
Account Disconnect Last Completed YNN By Line Hour
Call Details Current Day Y N N
Call Details Last Completed Day Y N N
Call Details Last Completed YNN Week
Device Chassis Last Completed Day Y N N
Events Last Completed Day Y N N
Events Last Completed YNN Hour
Exceptions Last Completed Day Y N N
Exceptions Last Completed YNN Hour
FR NW Capacity Last Completed Day Y N N
FR NW Capacity Last Completed YNN Hour
FR VC Util Last Completed Day Y N N
Interface Util Last Completed Day Y N N
Interval Current Day Y N N
Interval Last Completed Day Y N N
Interval Last Completed YNN Week
NW Capacity Last Completed Day Y N N Leaders
Top-N Interval All Days of past YNN Week
Top-N Interval Last Completed Day Y N N
Top-N Trend All Days of past YNN Week
Top-N Trend Last Completed Day Y N N
5-8 NavisAccess 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
Report Wizard Report Wizard Y Y Y
Resource Detail Resource Detail Y N N
Resource Detail Disable Y N N
Resource Detail Enable Y N N
Resource Detail Zero Y N N
Resource Overview Resource Overview Y N N
Resource Overview Down Y N N
Resource Overview Remove Y N N
Resource Overview Up Y N N
Sessions Overview Sessions Overview Y Y Y
Wan Channel Table Wan Channel Table Y N N
Wan Line Table Wan Line Table Y N N
Wan Line Table Change Wan Line YNN States
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 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 Remote-enabled User
Group Wizard: Create YN NN Groups
NavisAccess Installation and Administration Guide 5-9 Security Users and user groups
Table 5-5. Pre-defined User Group permissioned operations (continued)
Operation Manager Operator CNM Remote-enabled User
Config Device: Y N N N Download Y N N Database Y N N Erase Y N N Write Memory Y N N Upload Y N N
Image file: Y N N N Directory Y Y N Download Y N N Erase Y N N Upload Y N N
Scheduler N N N N
Path Finder Y Y N N
Performance Applets Y Y N N
Alarm Monitor Y Y N N
Threshold Manager Y N N N
IPMAP Y Y N N
System Options Y N N N
Audit Trail Y N N N
Audit Trail History Y N N N
5-10 NavisAccess Installation and Administration Guide Security User Manager
User Manager
The User Manager dialog box is accessed in NavisAccess 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 Database.
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 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 maintain Simultaneous on the database. Selecting more than 1 allows the user to login Legions simultaneously to multiple NavisAccess Clients. Selecting 0 will allow the user to login to any number of NavisAccess clients, simultaneously.
NavisAccess Installation and Administration Guide 5-11 Security User Manager
Password Never Click to specify that the password should never expire. Expires (not available in 6.0) Expires In (#) Select the number of days that the password will expire in. The default is Days 10 days Start Prompting Specify the number of days (prior to password expiration) that the user is (not available in prompted to configure a new password. 6.0) 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) in which the user is a member.
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 will grant access rights for the new data and/or feature(s). NavisAccess 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-12 NavisAccess 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 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 (#) Select the number of concurrent login instances that a user can Simultaneous Logins maintain on the database. Selecting more than 1 allows the user to login simultaneously to multiple NavisAccess Clients. Selecting 0 will allow the user to login to any number of NavisAccess clients, simultaneously. Password Never Click to specify that the password should never expire. Expires Expires In (#) Days Select the number of days that the password will expire in. The default is 10 days. 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 new user has been defined, click Next to add the new user to a user group so he/she may gain access rights.
NavisAccess Installation and Administration Guide 5-13 Security User Manager
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 will grant access rights for the new data and/or feature(s). NavisAccess will grant the same access rights to the newly added data/feature(s) as maintained in the Primary Data Group.
Example:
User ISP1 ISP2 User Group CNM Users, CNM Users, ISP1 Data Access ISP2 Data Access 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 only wants 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 the Primary Data 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.
5-14 NavisAccess Installation and Administration Guide Security User Manager
Edit an existing user group
NavisAccess 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 an organization. Once rights are assigned or removed from a User Group, all members of that group will be able effected. For example, if you take away a User Group’s access to specific data, all members of that group will not have access that data.
Pre-defined User Groups can also be edited with one exception, that is 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. <-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 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.
NavisAccess Installation and Administration Guide 5-15 Security User Manager
<-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 features to which the User Group will have access.
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 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.
5-16 NavisAccess Installation and Administration Guide Security 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 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:
Group Name Name of the User Group Description A brief statement describing the User Group. (limit 80 characters) 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.
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.)
NavisAccess Installation and Administration Guide 5-17 Security User Manager
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 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 elements to be managed by the User Group, define the data elements to which you want its members to have access.
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.
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.
5-18 NavisAccess Installation and Administration Guide Security User Manager
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 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 permissioned to use features and feature functions, click [Finish] to complete the making of the User Group, and return to the User Manager. • Click Delete to remove an added User or User Group from the User Manager.
Note: You cannot delete the pre-defined User, Admin, or any pre-defined User Group. • Click Deactivate/Activate to activate/lock out a User. Activating a user allows them to log into the system. De-activating a user prevents them from logging into the system. The Status column displays the current setting.
Note: You cannot Deactivate the pre-defined User, Admin.
Logging out of NavisAccess
To logout from NavisAccess: 1 From the NavisAccess main menu bar, select Security > Logout. The Logout window appears, prompting you to choose which NavisAccess Database you wish to logout from. 2 Click OK to log out.
Logging into NavisAccess
The following post-installation detail applies:
Upon first using NavisAccess after installation, the default login is as follows: User Name = Admin Password = Admin Both User Name and Password are case sensitive. Note: The Administrator should change the defaults to secure the workstation.
NavisAccess Installation and Administration Guide 5-19 Security User Manager
To Log into NavisAccess: From the NavisAccess main menu bar, select Security > Login. The Login dialog box opens. 1 Enter a User Name and Password. Any level User can log in over any other User. A login can also be done by starting/restarting the program. 2 Select the domain that you will be logging into. If you are unsure of your Domain, contact your NavisAccess Administrator. 3 Click OK to log in.
Change password
To change a password: 1 From the NavisAccess 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.
5-20 NavisAccess Installation and Administration Guide Security Audit Trails
Audit Trails
The Audit Trails applet displays actions taken by NavisAccess users. Audit Trails only displays actions which involve changes to the system or to devices: for example, changing the NavisAccess system configuration, or uploading a configuration file to a device. Audit Trails does not report monitoring actions, such as launching AccessWatch 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.
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-6. 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.).
NavisAccess Installation and Administration Guide 5-21 Security Audit Trails
Table 5-6. The Audit Trail window heading descriptions
Heading Description
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.
Other buttons:
In addition to the global tool bar buttons on its left side, the Audit Trails applet has four specialized button functions:
Button Description [Export Data] button Exports collected data to a comma separated variable file. [Show/Hide Pie Displays the key to the color-coding in the pie charts. Legend] button [Show/Hide 3D Toggles the pie chart between a 2D and 3D image. Effect] buttons The [Show Toggle the pie charts between displaying information as a integer Values/Show Percent] value (e.g., 10 events reported) or as a percentage (e.g. 10% of all buttons events). Click on the pie chart to see the precise values.
5-22 NavisAccess Installation and Administration Guide Database Maintenance 6
Database tools
NavisAccess provides database tools that can be used for the following: • Database backup - Performs a live backup of the NavisAccess 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 databases to a different disc device. After moving a database, new data is written to the database at the new location.
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 F-1.
Database tools are run from the DBMaint application. 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.
Note: In a Distributed Server environment, DBMaint will run only from the server where the Scheduling Server is installed.
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.
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/...
NavisAccess Installation and Administration Guide 6-1 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 allows you to backup and save multiple copies of the NavisAccess 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: In a Distributed Server environment, DBMaint will run only from the server where the Scheduling Server is installed.
Note: Please refer to “Workstation prerequisites for Restore and Move options” on page 6-11 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 user name and password.
Note: Only users with Administrator rights are able to access the DBMaint application. The DBMaint screen appears:
6-2 NavisAccess Installation and Administration Guide 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 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 uses to locate information. This database must always reside in the same disc drive as the NavisAccess application files. Serviceinterval The following six database files are used for Adaptive Servicedata Performance monitoring. 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. 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.
NavisAccess Installation and Administration Guide 6-3 Database Maintenance Database tools
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.
Note: In case of a Sun machine crash, Database server crash or a Lock-out, type the following command in the command line before re-initializing the database: dbserv6 -f $AutoBahn/database/ascend.db
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 6-11.
Before restoring the database, you must exit NavisAccess and shut down some of the NavisAccess services. To Shut down the services:
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 F-1.
Distributed Environment: • Exit NavisAccess on the workstation • Run nautil shutdown on the workstations • Run nautil shutdown on the secondary servers • Run nautil dbmaint on the primary server 1 Start the DBMaint application by typing dbmaint at the command line. 2 A login screen appears. Enter a NavisAccess user name and password.
Note: Only users with Administrator rights will be able to access the DBMaint application. 3 Shut down the database on the main server in a distributed environment by entering the dbstop command. 4 Change directories to: /
6-4 NavisAccess Installation and Administration Guide Database Maintenance Database tools
The Restore database files screen appears:
This screen displays the eight database files that NavisAccess allows you to restore. You may restore these files as many times as you wish. Ascend.db, must reside in the same default location ($AutoBahn) as the NavisAccess application files and, therefore, can only be 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 uses to locate information. This database must always reside in the same default location ($AutoBahn) as the NavisAccess application files. serviceinterval The following six database files are used for Adaptive Performance servicedata monitoring. 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. 9 Click the browse button to select the Source path for the database file being restored, or rename it if you wish, and click Set.
NavisAccess Installation and Administration Guide 6-5 Database Maintenance Database tools
Distributed server only 1 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. 2 The Destination Path field opens up. 3 Click Set when you have specified the Destination Path.
4 When done click Restore. The Restore Status screen will display while the database is being restored. 5 Run /
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 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 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.
Note: In a Distributed Server environment, DBMaint will run only from the server where the Scheduling Server is installed.
Refer to “Workstation prerequisites for Restore and Move options” on page 6-11 for details.
To reinitialize the database:
Before reinitializing the database, you must exit NavisAccess and shut down the NavisAccess services. Depending on the type of install, to shut down the services:
6-6 NavisAccess Installation and Administration Guide Database Maintenance Database tools
Stand-alone • Exit NavisAccess and run the nautil dbmaint command. This will stop the appropriate services.
Distributed Environment, Primary Server: • Exit NavisAccess on the workstation • Run nautil shutdown on the workstations • Run nautil shutdown on the secondary servers • Run nautil dbmaint on the primary server 1 Start the DBMaint application by typing dbmaint at the command line. 2 A login screen appears. Enter a NavisAccess user name and password.
Note: Only users with Administrator rights will be able to access the DBMaint application. The DBMaint screen appears:
3 Shut down the database (on main server in distributed environment) by entering the dbstop command and press Enter. 4 Change directories to: /
NavisAccess Installation and Administration Guide 6-7 Database Maintenance Database tools
Repairing a database
NavisAccess 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 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 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 application files.
Note: In a distributed server environment, DBMaint will run only from the server where the Scheduling Server is installed.
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 6-11.
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.
It is strongly advised that you backup your databases before moving a database file to another drive/directory.
6-8 NavisAccess Installation and Administration Guide Database Maintenance Database tools
Before moving the database files, you must exit NavisAccess and shut down the NavisAccess services. Depending on the type of install, to shut down the services:
Stand-alone • Exit NavisAccess and run the nautil dbmaint command. This will stop the appropriate services.
Distributed Environment, Primary Server: • Exit NavisAccess on the workstation • Run nautil shutdown on the workstations • Run nautil shutdown on the secondary servers • Run nautil dbmaint on the primary server
To start DBMaint: 1 At the command line, type dbmaint and press ENTER. 2 A login screen appears. Enter a NavisAccess user name and password.
Note: Only users with Administrator rights will be able to access the DBMaint application. 3 Type dbstop to shut down the database (in a distributed environment, type: dbstop from the main server). 4 Click on 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 Services 5 At command line, type dbstop and press Enter to stop all services. The Move database files window displays.
This screen displays the eight database files that NavisAccess 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 default location ($AutoBahn) as the NavisAccess 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 uses to locate information. This database must always reside in the same default location ($AutoBahn) as the NavisAccess application files.
NavisAccess Installation and Administration Guide 6-9 Database Maintenance Database tools
Database Description serviceinterval The following six database files are used for Adaptive Performance servicedata monitoring. 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. 6 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. 7 To deselect a database, clear the checkbox. 8 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. 9 Select the path for the file and press 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.
6-10 NavisAccess Installation and Administration Guide Database Maintenance Database tools
10 Click Move
Note: A message displays, strongly advising you to backup your database before proceeding with the move. 11 Once the database file(s) is moved, the message ’Database successfully moved’ displays. 12 Exit DBMaint 13 Start the services again (the database is automatically opened). 14 Run nautil start on main server. When everything is running, 15 Run nautil start on secondary servers. 16 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.
Note: In a distributed server environment, DBMaint will run only from the server where the Scheduling Server is installed.
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
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.
NavisAccess Installation and Administration Guide 6-11 Database Maintenance Backing-up the database without DBMaint
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.168.32.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. To unmount, type: umount $AutoBahn/database
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.
6-12 NavisAccess Installation and Administration Guide Database Maintenance Backing-up the database without DBMaint
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: 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 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. ------
NavisAccess Installation and Administration Guide 6-13 Database Maintenance Backing-up the database without DBMaint
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. 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 can be backed-up are listed in the table below:
Table 6-1. NavisAccess database files available for back-up
NavisAcces Database files
ascend.db /opt/navis/database /opt/navis/dbbackupdir
serviceinterval.db /opt/navis/database /opt/navis/dbbackupdir
servicedata.db /opt/navis/database /opt/navis/dbbackupdir
ingressinterval.db /opt/navis/database /opt/navis/dbbackupdir
ingressdata.db /opt/navis/database /opt/navis/dbbackupdir
egressinterval.db /opt/navis/database /opt/navis/dbbackupdir
egressdata.db /opt/navis/database /opt/navis/dbbackupdir
event.db /opt/navis/database /opt/navis/dbbackupdir
6-14 NavisAccess Installation and Administration Guide Database Maintenance Backing-up the database without DBMaint 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 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 filename, 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.
NavisAccess Installation and Administration Guide 6-15 Database Maintenance Backing-up the database without DBMaint
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.
6-16 NavisAccess Installation and Administration Guide The Master List 7
Overview
Networks are growing faster and becoming more and more complex. Administrators need an easy way to configure these networks. NavisAccess provides an easy-to-use solution to this situation.
The NavisAccess Master List provides the administrator a way to easily and comprehensively configure and manage changes to a network. The Master List is a utility that enables you to specify all devices, the WAN Line Interfaces on those devices, and their current status. NavisAccess reads the Master List and tries to discover all the devices and the interfaces associated with each device that are specified in the list.
The Master List is used in conjunction with Device Discovery.
After discovering the devices, NavisAccess updates the status of the devices and interfaces in the NavisAccess 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”.
The Master list enables you to customize the list of devices that you want discovered. You can also use the Master List as a template to populate a new device’s database or refresh the database of an existing device.
Types of Master Lists
You can generate two types of Master lists: • Master List - encompasses the entire network • Partial Master - encompasses part of the network
NavisAccess Installation and Administration Guide 7-1 The Master List Processing the Master List
Processing the Master List
Master List format
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 7-1. Lists the 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” .
“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” .
7-2 NavisAccess Installation and Administration Guide The Master List Processing the Master List
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":"2 00":"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.
Validation of information in the Master List
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 leaves the corresponding field in the NavisAccess database table as it is. If the NavisAccess database already contains some description, that description value is used by NavisAccess.
If quotes are specified without a parameter value, NavisAccess blanks out the corresponding entry from the NavisAccess 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 blanks out the corresponding field in the NavisAccess 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.
NavisAccess Installation and Administration Guide 7-3 The Master List Processing the Master List
Processing a partial Master List
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
NavisAccess provides support for processing both partial and complete Master Lists. NavisAccess 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 earlier. If the DNIS has been processed, there is a record for the DNIS in the NavisAccess database.
Table 7-2. 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 =
7-4 NavisAccess Installation and Administration Guide The Master List Processing the Master List
Table 7-2. Summary of rules to process the Master List
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
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 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.
NavisAccess Installation and Administration Guide 7-5 The Master List Processing the Master List
Circuit status
The following status values are defined for the channeled interfaces:
Table 7-3. 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 List is being processed, the status value is left unchanged for devices or interfaces not referenced in the Master List.
Note: In the NavisAccess 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.
7-6 NavisAccess Installation and Administration Guide The Master List The Master List Configurator (MLConfig)
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 will automatically modify the status of affected interfaces based on the following rules:
Table 7-4. Describes correlation between device status changes and interface status changes
If device status changes Interfaces status changes to From To
Operational, or Out-of-Service Status of all the interfaces is changed Out-of-Service-Test, or to “Out-of-Service”. Unknown
Operational, or Out-of-Service-Test Status of all the interfaces is changed Out-of-Service, or to “Out-of-Service-Test”. Unknown
Operational, or Unknown Status of all the interfaces is changed Out-of-Service, or to “Unknown”. Out-of-Service-Test
Out-of-Service, or Operational No change. Interfaces status must be Out-of-Service-Test, or explicitly modified using the Master Unknown 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 database device 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, you can use MLConfig.
The Master List Configurator application provides the functionality of synchronizing the information in the NavisAccess database with that in the Master List. MLConfig enables you to export the NavisAccess 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 • the Tools menu (Tools> MLConfig Launcher) Note: To use MLConfig, one should let NavisAccess discover the network initially so that the NavisAccess database gets populated with information about the devices that are available on the network. Once the NavisAccess database is populated with the network information, MLConfig can be run to generate the Master List.
NavisAccess Installation and Administration Guide 7-7 The Master List The Master List Configurator (MLConfig)
MLConfig Launch Options provides the ability of synchronizing the information in the NavisAccess database with that in the Master List. It allows you to export the device and interface information from the NavisAccess database to generate the Master List.
Starting MLConfig from the command line
You can invoke the MLConfig application from the command line using optional parameters. These parameters are described in the next section.
The default option is import, so when importing the Master List into the NavisAccess 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 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
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 7-5. 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.
7-8 NavisAccess Installation and Administration Guide The Master List The Master List Configurator (MLConfig)
Table 7-5. MLConfig Command Line Options - Import (continued)
Option Description
-devstatus "
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 "
NavisAccess Installation and Administration Guide 7-9 The Master List The Master List Configurator (MLConfig)
Table 7-5. 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
-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
Exporting the NavisAccess database
To export the NavisAccess 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 device database is exported and is named test2. 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 database. Since import is the default, you do not have to enter it as part of the command.
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.
7-10 NavisAccess Installation and Administration Guide The Master List Creating a Master List from scratch
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
The following options can be specified when MLConfig application is used to export information from the Master List from the command line.
Table 7-6. MLConfig Command Line Options - Export
Option Description
-dnistranslated Exports all translated DNISs.
-dnisshort Exports all short DNISs.
-dnisall Exports all DNISs.
-customers Exports customer details from the NavisAccess database in the following format: C:”cust-name”:”cust-contact”:”cust-email”:”cust-phone#”
-devicesonly Exports only device information from the NavisAccess database. Does not export interface information.
Creating a Master List from scratch 1 Enter the device information using any text editor. 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”:” ”:” “ 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 automatically reads the Master List and starts to discover the devices on the Master List by comparing it to its database. NavisAccess Examiner displays each device as it is discovered.
NavisAccess Installation and Administration Guide 7-11 The Master List Generating the Master List using the MLConfig Launch Options Dialog
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: • Right-click on a device in the Examiner> Access Application>Wan Line Table.
Generating the Master List using the MLConfig Launch Options Dialog To display the ML Config Launch Options dialog, from the NavisAccess menu bar, select: Tools > MLConfig Launcher.
The MLConfig Launch Options screen displays.
Exporting the Master List 1 From the NavisAccess 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 Click Launch.
Importing the Master List 1 In the MLConfig Launch Options dialog, enter information for all the fields in the Import Options section. The table below describes each field. 2 Once all fields are filled out as desired, click Launch.
7-12 NavisAccess Installation and Administration Guide The Master List Generating the Master List using the MLConfig Launch Options Dialog
Import options
Table 7-7. Master List import options field descriptions
Field Description
Import Master List File Name Select the Master List file to import device 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. For further information about the logging process, refer to Logging process information.
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.
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.
NavisAccess Installation and Administration Guide 7-13 The Master List Generating the Master List using the MLConfig Launch Options Dialog
Table 7-7. Master List import options field descriptions (continued)
Field Description
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 only will contain 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.
No Log Check to have MLConfig not create a log file. If this is selected, no logging will be done.
7-14 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) 8
Introduction
The Navis Device License Manager (NDLM) allows license and software options updates to any hardware purchased from Lucent Technologies 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. These codes are already in use and are provisional on a per system basis. Software options are stored on the system.
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 Database. NavisAccess adds the newly learned codes to the cards in the TAOS device in a secure manner.
NavisAccess Installation and Administration Guide 8-1 Navis Device License Manager (NDLM) What are device licences?
The illustration below graphically depicts the procedure for providing device license information.
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 database and storing that information locally in a request file in a predefined format. Please see “Generating a Device License request file” on page 8-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 directory. See “Receiving a response file Customer Service” on page 8-9.
Step 2 - The License information on the devices is updated using the response file. Please see “Applying the license response file” on page 8-10. • After the device licences information is updated on the devices, the updated devices may be manually rediscovered. The NavisAccess 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 8-5 for details.
If you have technical issues with NDLM, or do not receive a response within 24 hours, contact Network care for support.
8-2 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Launching the NDLM
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 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 installation directory (includes all NavisAccess directories.) featurecode Directory under NavisAccess installation directory for NDLM files 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.
NavisAccess Installation and Administration Guide 8-3 Navis Device License Manager (NDLM) Launching the NDLM
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: “Device License Manager application was started by user
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.
There are three selections at this screen: 1 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. 2 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. However, if a request file was created in a previous session, you can proceed to “Apply License Response File.” 3 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).
8-4 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Setting the Advanced options
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 Settings 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 8-1. SNMP Advanced options and their description
SNMP Advanced options Description
Time Out Sets a value, in seconds, before an SNMP packet is considered lost in the network.
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.
NavisAccess Installation and Administration Guide 8-5 Navis Device License Manager (NDLM) Generating a Device License request file
Generating a Device License request file
Step 1
In the first step, you generate a device license request file and email that file to Lucent.
You may request license/software options for all, some, or one device defined in the NavisAccess database. You may 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.
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.
8-6 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Generating a Device License request file
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 the device has been modified. 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.
NavisAccess Installation and Administration Guide 8-7 Navis Device License Manager (NDLM) Generating a Device License request file
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 8-15 for a sample of this 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.’
8-8 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Processing the response file
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 step 2, 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.
Receiving a response file Customer Service
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 gen- erated by automated process.
NavisAccess Installation and Administration Guide 8-9 Navis Device License Manager (NDLM) Processing the response file
Thank you for using EmailProcessor!
P.S. If you sent multiple attachments please note that just the first one was processed. Please, re-send 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. 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. 10 Launch the NDLM from the NavisAccess main menu: Tools > Device License Manager. 11 Click on Apply License Response File in the Device License Manager screen. 12 Click Next. The Apply Device Licenses screen appears.
8-10 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Processing the response file
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. 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 8-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: 13 Click on the Response File button to display the files available. The License File Select screen appears.
NavisAccess Installation and Administration Guide 8-11 Navis Device License Manager (NDLM) Processing the response file
14 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, thus cannot be changed.
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).
The creation date of the file displays (for example, 20010630 - June 30, 2001). Notice also that each file has a unique number (1000, 1001) to distinguish it from other response files. 15 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. 16 Click on the Apply Licenses button. The lower window displays the log file. The Apply Device Licenses screen now looks like this:
8-12 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Processing the response file
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.
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 8-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 8-16. To reprocess a file see “Reprocessing a file” on page 8-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.
NavisAccess Installation and Administration Guide 8-13 Navis Device License Manager (NDLM) Reprocessing a file
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.
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 16 on page 1-12.
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.
8-14 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) Log file samples
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
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.
NavisAccess Installation and Administration Guide 8-15 Navis Device License Manager (NDLM) Log file samples
+
These messages are repeated for each device. Any operation that results in an error, causes a corresponding error message to be logged. For example:
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
8-16 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) NDLM Error Messages
…
These messages are repeated for each device. Any operation that results in an error, causes a corresponding error message to be logged. For example:
...
NDLM Error Messages
Request file
Table 8-2. Request file error messages
Request File Error Messages Description
SNMP messages
Sending SNMP request to device
SNMP request could not be sent to device This message displays when an SNMP request cannot be sent to
SNMP Timed out. Request failed for device The SNMP request failed for a particular device because the
SNMP request failed for device
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.
NavisAccess Installation and Administration Guide 8-17 Navis Device License Manager (NDLM) NDLM Error Messages
Table 8-2. Request file error messages (continued)
Request File Error Messages Description
Starting to retrieve data from device
Finished retrieving data. This message displays at the end of a license/software retrieval for a device.
Retrieving Data for Device -
SNMP operations end. This message displays after polling for all the devices has ended.
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.
8-18 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) NDLM Error Messages
Table 8-2. Request file error messages (continued)
Request File Error Messages Description
Created License Request File
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-
Writing license option request- Serial Number- This message displays when the license option request is in
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.
NavisAccess Installation and Administration Guide 8-19 Navis Device License Manager (NDLM) NDLM Error Messages
Response File
Table 8-3. Response file error messages
Response File Error Messages Description
"Starting Licenses Update For Device
"Completed Processing Licenses On Device Occurs on the completion of card license updates for a device.
"Completed Updating Licenses On Device Occurs on the completion of a card software update for a
"Completed Processing Feature Codes For Occurs at the end of a license/software options update for a Device
"Device
"Errors Occurred Processing License Options Displays when an error occurred while updating For Device
Verification messages
"License
"There Are Licenses Disabled On Device Occurs when the NDLM detects that a License that was
8-20 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) NDLM Error Messages
Table 8-3. Response file error messages (continued)
Response File Error Messages Description
" License
"There Are Licenses Enabled On Device Occurs when the NDLM detects that a License is set on the
“License
"Error Updating License Options For Device Occurs when a license/software update failed on a specific
"There Are Licenses Disabled On Device Occurs when the NDLM detects that a License that was
" SECProm Error #
"SECProm Error: #
NavisAccess Installation and Administration Guide 8-21 Navis Device License Manager (NDLM) NDLM Error Messages
Table 8-3. Response file error messages (continued)
Response File Error Messages Description
Database Messages
"Error Writing License Options To Database For Occurs when a database error prevents the writing of a Serial Number #
Process Messages
"There Are No Licenses For
"SNMP Error On Device
"SNMP Timeout On Device
"Errors Occurred Processing Licenses On Occurs on any error that occurs on a card or unit. Device
"Error (
SNMP messages
"Timed Out Setting License (
" Timed Out Checking License (
8-22 NavisAccess Installation and Administration Guide Navis Device License Manager (NDLM) NDLM Error Messages
Table 8-3. Response file error messages (continued)
Response File Error Messages Description
" Timed Out Waiting For Verification of License An SNMP message appears when checking to see if the Update For
"
parser messages
"Parsing License File
"Parsing File
"File Not Valid Response File Type" Occurs on any response file parsing error Example: "Parser Error: File Not Valid Response File Type"
"Subject Submitted was (
"Subject Is Empty." Occurs if the response file subject tag is empty Example: "Parser Error: Subject Is Empty")
"Expected Start Tag
"Expected End Tag
NavisAccess Installation and Administration Guide 8-23
Configuring Trap Forwarding A
NavisAccess provides the ability to forward traps and events to multiple destinations for use with third party event management tools. Traps can include those received from Lucent Technologies network devices, while events are generated by NavisAccess as it monitors for threshold crossings, downed channels and modems, etc.
Following are configuration instructions for NavisAccess 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).
Identifying which farm sent the trap
The identification parameter, ‘-idstr’ is an optional parameter that provides the name of the farm that sent the trap. Type the following to identify the trap:
imc –idstr [Identification string]
Example: imc –idstr [Bohemia]The –showtf parameter will display the following when this string is added: idstr=Bohemia
NavisAccess Installation and Administration Guide A-1
Multiple Standalone Installations on the B 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 27xxx where: yyy is a unique name xxx is equal to the last byte of the IP address of the machine on which Navis is being installed. For example, if NavisAccess is being installed on machine 192.168.50.55, the setup parameters would be: setup -n navismysite55 -o 2755 Note that “-o” is the letter “O”, not a zero.
Note: If you have a device in your network that has multiple IP addresses, you can stop auto-discovery from occurring upon rebooting your system by adding “-d agedisc” to the./setup command. This will ensure that the device will not inadvertently be discovered twice when using MLConfig. Using this option will cause the Do not discover devices through Call logging packets checkbox on the MLConfig tab of the NavisAccess Configuration dialog (Configure>System Options) to be selected once NavisAccess starts. Example: ./setup -d agedisc Once NavisAccess starts, you can start discovery through call-logging packets by deselecting the Do not discover devices through Call logging packets checkbox on the NavisAccess Configuration dialog MLConfig tab (Configure>System Options).
NavisAccess Installation and Administration Guide B-1
Workstation Installation on a Separate C Subnet
All servers in a NavisAccess 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 Installation Application: ./setup -n
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 osangent 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. 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 Installation and Administration Guide C-1
File Maintenance Notes D
NavisAccess 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 deleting your log files, 4 Execute nautil start (if it is farm, do this on every machine). NavisAccess 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 see the DBMaint chapter in this guide. NavisAccess 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. 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 administrator can log into the DBmaint application. For detailed information, please see the DBMaint chapter in this guide, and the Schedule Wizard chapter in the NavisAccess User’s Guide.
NavisAccess Installation and Administration Guide D-1 File Maintenance Notes
At least 2 GB of free hard disk space must be available at any time for running NavisAccess. 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. Please refer to the DBMaint chapter in this guide.
D-2 NavisAccess Installation and Administration Guide Uninstalling NavisAccess E
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 5.x file) – K99ascendDBeng (NavisAccess 5.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 5.x file) 5 Delete the following files in the directory /etc/init.d: – navisaccess – windu
NavisAccess Installation and Administration Guide E-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!
E-2 NavisAccess Installation and Administration Guide The nautil Utility F
Note: nautil is available for Solaris versions only.
The nautil utility monitors and manages the background services of NavisAccess.
These services run on every machine that NavisAccess 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 user application. 2 Open a terminal session, and type: nautil
A list of nautil options will appear:
start Starts all NavisAccess services. status Displays the status of all services, allowing one to view the status of (nastatus) multiple Navis processes running on one or more servers and workstations. 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 Installation and Administration Guide F-1 The nautil Utility The nastatus utility
Caution: Exercise caution when using the “nautil shutdown” command if non-NavisAccess applications are running on the server.
The “nautil shutdown” command utilizes the “ipcrm” command to clear system semaphores. This command clears all shared semaphores, and may cause unpredictable behavior in other applications. For example, if nautil is used to stop NavisAccess on a system running HP OpenView which is using semaphores, unexpected results can occur. This also applies to Sybase 11.
The nastatus utility
The nastatus utility allows you to view the status of multiple Navis processes running on one or more servers and workstations.
Using the nastatus utility From any machine on the farm, 1 open a terminal session, and type: nastatus telnet You will then be prompted for the password for the machines in the server farm.
Note: We recommend all your servers in the server farm share the same password. If your farm does not have a common password, you may be prompted again for subsequent passwords. 2 Enter your password(s). The status of each machine will be displayed, including the host name, services, and their status.
F-2 NavisAccess Installation and Administration Guide The TFTP Server G
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 the NavisAccess User’s Guide.
The TFTP Server applet 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 applet is started automatically when NavisAccess starts, and appears as a separate icon.
A Note for Solaris users: By default, the TFTP Server Applet on Solaris runs like a daemon, or in the background. (If you are running TFTP in the background, you can access the TFTP logfile (tftp.log) which is located in the NavisAccess installation directory.) If necessary, the TFTP front-end applet can be activated, by performing the following steps: 1 Shut down the daemon version of the TFTP server applet by obtaining the PID by typing nautil status at the x-session. 2 Type kill PID to shut down the Daemon applet. 3 Start the front-end applet by typing tftpsrv from the x-session.
To re-start the daemon version of the Applet: 1 Close the front-end applet. 2 Type nautil start to re-start the daemon applet.
Opening the TFTP Server
To open the TFTP Server applet, right-click on the TFTP Server icon and choose Administer TFTP. The TFTPSRV server should be launched using NAUTIL as the root user.
NavisAccess Installation and Administration Guide G-1 The TFTP Server
NavisAccess TFTP Server Setup tab
The TFTP Server Setup tab allows you to configure the TFTP server.
Fields that can be set from the Setup tab include:
Table 8-4. TFTP Server Setup tab field description
Field Description
Max Retries Sets the number of times the TFTP server will retry a transfer before failing.
Timeout Sets the amount of time, in seconds, that a transfer will be attempted before failing and retrying.
Port Number Displays the port number for the TFTP server. To change the port number see Port Configuration below.
Enable Logging Select this option to enable logging of TFTP events to the log file. To view the log file, click the [View Log File] button.
Verbose Mode Select this option to enable verbose mode logging. Verbose mode logging returns a block-by-block record of the file transfer. Without verbose mode, the log file will record the following: Start Date and time. Stop Data and time. File name. Source IP address. Destination IP address. Following is a sample, non-verbose log file entry: Thu Mar 20 14:21:26 1997 150.50.23.203 FSTART Transfer of Cfgup.log to Cfgup.log FSTART = start of file transfer. FEND =-end of file transfer.
G-2 NavisAccess Installation and Administration Guide The TFTP Server
Table 8-4. TFTP Server Setup tab field description (continued)
Field Description
Security Use this option to secure information sent to and received from NavisAccess via the TFTP server.
Note: Whenever a TFTP request is rejected due to security issues, an appropriate message is logged into the log file. Accept request from NavisAccess only Select this option to only accept requests made by NavisAccess; no other requests will be honored. Restrict operation to 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 “restrict operation” feature, no NavisAccess clients can be running. Shut down all NavisAccess clients, including Xterm sessions, and then launch the Administer TFTP function from the TFTP icon.
To view the log file, click the [View Log File] button. The log file is saved as LOGFILE.TXT and stored in the NavisAccess home directory (c:\NavisAccess by default). You may delete the log file if it grows very large. A new one will be automatically created.
Disabling the TFTP Server
To disable the TFTP Server, click on the TFTP Server Setup tab and click the [Disable Server] button. Doing so will terminate any ongoing sessions and prevent any new sessions from starting.
If you attempt a file transfer while the TFTP server is disabled, you will receive a “TFTP Operation Failed” error message.
If the TFTP Server is disabled, this is visually indicated by a change in the appearance of the TFTP Server icon.
Port configuration
NavisAccess allows you to configure which port (other than 69) 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 and it's 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.
NavisAccess Installation and Administration Guide G-3 The TFTP Server
To Configure a port other than 69: 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
To verify the port number: After changing the port number, you can verify the port that NavisAccess 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.
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:
G-4 NavisAccess Installation and Administration Guide The TFTP Server
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. 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.
NavisAccess Installation and Administration Guide G-5 The TFTP Server
Configure TFTP to work with NAT (Distributed)
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 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
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:
G-6 NavisAccess Installation and Administration Guide 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.
NavisAccess Installation and Administration Guide G-7 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:
G-8 NavisAccess Installation and Administration Guide 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.
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
NavisAccess Installation and Administration Guide G-9 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:
G-10 NavisAccess Installation and Administration Guide 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.
NavisAccess Installation and Administration Guide G-11
Setting NavisAccess Database Cache Size H
Setting the NavisAccess database cache size is accomplished by editing the start script in the ascendDBeng file.
Note: On Solaris the default database cache size is 48 MB (for Primary Server with up to 512 MB RAM) and 100 MB (for Primary Server with greater than 512 MB (up to 1.5 GB RAM)) and 200MB (for Primary Server with greater than 1.5GB RAM). On Windows NT, the default database cache size is 48 MB.
Table H-5. (Solaris default database cache sizes)
RAM Cache
0 - 512 48MB
512 - 1.5MB 100MB
1.5GB 200MB
As a general rule, it is recommended that cache of one-tenth of the total DB size be used, depending upon the total RAM size availability.
To set the NavisAccess database cache size: 1 Log in to your system as root. 2 Edit the following file: /etc/init.d/ascendDBeng You will see the start script in the file: if [ "$1" = "start" ] then /usr/bin/nohup $NAVIS_DIR/dbsrv6 -ud -gk all -m -c 48M -ti 0 -o $NAVIS_DIR/database/U601026_output.log -os 102400 -n U601026 $NAVIS_ DIR/database/ascend.db
3 To set the database cache size, you must edit the “-c” argument. As you can see, the database cache is set to 48M (48 Megabytes). The format for the cache size in xxxM, where xxx is the size and M represents Megabytes. 4 Set the database cache size. 5 Save the file. 6 Restart NavisAccess.
Note: The new database cache size will take effect when you restart NavisAccess.
NavisAccess Installation and Administration Guide H-1
Changing Host Machine Identifying I Parameters
If for any reason, the HostID, Hostname or IP address of a standalone machine or a machine in a distributed environment is changed, you must reinstall NavisAccess on the new machine in order for NavisAccess to run. Failure to do so, will result in a message informing you that you do not have a license key for NavisAccess when you try to launch it.
Below is the recommended procedure that must be implemented if changes are made to the identifying parameters on a Solaris machine installed with NavisAccess. Please follow the instructions that apply to your site.
– Most of the procedures involve reinstalling NavisAccess. If the machine has a NavisAccess 5.0 Service Pack (5.0.1, 5.0.2, etc), you must reinstall NavisAccess 5.0.0, and then reinstall the Service Pack.
– If you ever restore a database-backup that was made before any of the machine changes, the procedures listed below must be run again.
– The database can be kept in all cases (choose 'upgrade Database' at the appropriate prompt).
HostID change If the HostID is changed on a NavisAccess machine, perform the following according to machine type:
NavisAccess Standalone: 1 Run nautil shutdown on the machine. 2 Reinstall NavisAccess.
Note: If Step 1 is not performed, NavisAccess client may not be licensed after reinstall.
NavisAccess Distributed Server:
Servers (Primary and Secondary): • Reinstall NavisAccess.
Workstation: • Reinstall NavisAccess.
– Use the same license key that was used in the original installation.
– There will be a 'license key in use' error message during reinstall. Ignore this, selecting Yes to Proceed.
NavisAccess Installation and Administration Guide I-1 Changing Host Machine Identifying Parameters
Hostname Change If the machine hostname is changed after installing NavisAccess, you must reinstall NavisAccess (to run the NavisAccess GUI) and you must delete the old.windu.(hostname) file in $AutoBahn.
Once you reinstall NavisAccess, two .windu.(hostname) files will reside in $AutoBahn (for example, the old and new .windu files are: .windu.qa4, and.windu.qa5, respectively).
To delete the old .windu. file from $AutoBahn: 1 Cd into $AutoBahn. At the command prompt, type: 2 ls -al A list of the windu files will appear (in our example, .windu.qa4, .windu.qa5). To erase the old file, type: 3 rm .windu.qa4 4 Reboot.
IP Address Change Important!!!: Before any IP Address change is made to any NavisAccess machine(s), close all instances of NavisAccess and run nautil shutdown on all machines in farm. If the IP Address is changed on a NavisAccess machine, perform the following according to machine type: NavisAccess Standalone: 1 Run nautil shutdown on the machine. 2 Reinstall NavisAccess.
Note: If Step 1 is not performed, you will not be able to keep the database.
NavisAccess Distributed Server:
Primary Server: 1 Run nautil shutdown on the Primary Server. (If this is not done, you will not be able to keep the database.) 2 Reinstall NavisAccess on the Primary Server.
Note: Because the database server is not running upon installation, you will have to re-enter the distribution plan. 3 Reinstall NavisAccess on all Secondary Servers. 4 Reinstall NavisAccess on all Workstations.
Secondary Server: Reinstall NavisAccess on the machine with the IP address change, following these steps: 1 At the prompt to install Workstation, select Override. 2 Choose Distributed Server install type. 3 In Distribution Planning, Step 1, go to the Machine List at the bottom and highlight the machine with the old IP address.
I-2 NavisAccess Installation and Administration Guide Changing Host Machine Identifying Parameters
4 Modify this machine’s IP address field to the new IP address. 5 Finish the installation.
Workstation: No special steps are required if the IP address is modified on a Workstation machine. If nautil shutdown was run properly on the whole NavisAccess farm before the IP address change, the Workstation should continue to function.
NavisAccess Installation and Administration Guide I-3
Configuring Printing J
To print reports, program windows and so on from within NavisAccess, you must properly configure the printing on Solaris and within NavisAccess, as explained in the following procedures.
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.1Printer_1 P1 Use a suitable Unix editor to add the printer to this file. 2 Run the Solaris Admintool by enter the following at the command line: admintool& 3 The Admintool window will open. From the menu, select Browse > Printers. This will display any printers currently set up, if any. 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 1 From within NavisAccess, 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. 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.
NavisAccess Installation and Administration Guide J-1 Configuring Printing
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.
J-2 NavisAccess Installation and Administration Guide License agreement K
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 Installation and Administration Guide K-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
K-2 NavisAccess 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 Installation and Administration Guide K-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.
K-4 NavisAccess Installation and Administration Guide A
A visual indicators 4-2 Device license AccessWatch 1-4 generating request file 8-6 Allow Primary Windows On Top 1-2 updating 8-2 Audit Trails Disabling the TFTP Server G-3 overview 5-21 Display environment variable 1-2 use of 5-21, 5-22 Distributed Installation xiii component description 2-5 distributing components 2-4 B Distribution plan 2-3 File maintenance notes D-1 Backing up the database 6-2 prerequisites 2-1, 2-3 BOOT/DHCP stand-alone 2-1 Client xviii, xix steps 2-10 Server xviii, xix using a Stand-alone server xiv Workstations 2-17 MIB compilation 2-20 C DNIS Translation 1-6 Cache size, setting database cache size H-1 DNIS translation table 4-3 Call Logging and SNMPv3 restrictions in TAOS 8.0 3-1 modification of 4-5 Call logging packets 1-5, 1-6 use of 4-4 Cascading OSAgents xvii Client Domain xv E Server Domain Communication xvi Client GUI xxii Error messages, Navis Device License Manager 8-17 Compile MIBs 1-9, 2-20 Configure RAS 1-3 Configuring F ports G-3 trap destinations 3-2 File Maintenance Notes D-1 Firewall configuring in the NavisAccess network xv D
Database setting cache size H-1 G Database maintenance 6-1 Clear Map Flags 6-2 Generating database back-up 6-2 fresh database 6-6 database repairing 6-8 Master List 7-7 database restoration 6-4 GUI Server xxii fresh database 6-6 moving database files 6-8 workstation prerequisites 6-11 H Device discovery 4-1 automatic 4-8 Hash codes 3-17 automatic, manual, Master List 4-1 Host machine generating Master List 4-6 changing identifying parameters I-1 manual 4-5 changing IP address I-1 Master List 4-6 running Explorer 4-8 HostID, changing I-1 the Explorer 4-8 Hostname, changing I-1
NavisAccess Installation and Administration Guide Index-1 I
I advanced options,setting 8-5 Apply Device Licenses screen 8-11 IMC xx error messages 8-17 trap forwarding xx launching 8-3 Installation response file error messages 8-20 standalone 1-1 NavisAccess xiv prerequisites 1-1 Database system requirements 1-3 setting cache size H-1 types of xiii Server xxii Installing workstations on a separate subnet C-1 Server Farm xxii Workstation xxii NavisAccessProfile 1-10, 2-20 L liblock.so. 1-6 O License Agreement K-1 Operating System Requirements xxiii options 8-1 OSA_CLHDLR_TCP xvii OSA_CLHDLR_UDP xvii OSAgent xvii M OSAGENT_PORT xvii
Managed Resource Domain xv Master List P Circuit Status 7-6 configurator 7-7 Partial Master List 7-4 Entries 7-3 Pipeline format 7-2 configuring generation 7-7 community strings 3-3, 3-10 importing options 7-8 SNMP Trap destinations 3-2 processing rules 7-4 Port xxii types of 7-1 configuration G-3 MAX Primary Server xiii configuring using a stand-alone server xiv call logging 3-5, 3-36 community strings 3-3, 3-10 Printing J-1 SNMP Trap destinations 3-2 Protocols and ports to open on the firewall xvi MAX TNT configuring call logging 3-13 R Moving database files 6-8 Repairing a database 6-8 Response file error messages 8-20 N Restoring the database 6-4 Rlogin 1-2 NAS port ID 1-5 Nastatus F-1 utility F-2 S Nautil 2-19 start 1-8 Secondary Server xiv status 1-8 using a stand-alone server xiv utility 1-8, F-1 Security 5-1 Navis Device License Manager adding a new user group 5-17 (NDLM) 8-1 Administrator user group 5-9
Index-2 NavisAccess Installation and Administration Guide T
Data Access 5-1, 5-17 Setup tab G-2 rights 5-15 Solaris G-1 defining a user 5-13 TFTPSrv process xix group membership 5-14 Trap forwarding A-1 edit user 5-11 via IMC xx group membership 5-12 editing group membership 5-11 user group 5-15 U Feature Access 5-1 predefined UDP xvii, xx user groups 5-2 3000 xix users 5-2 Default Ports xxi OSA_CHLDRL xvii Server Domain xv OSAgent_PORT xvii Service xxii ports xvi, xx SNMP User Groups access xx predefined 5-2 address security xx Users Community Strings 1-5 predefined 5-2 Security 1-4 traps 1-5 SNMPSrv xviii, xix W SNMPSrv Client xvi SNMPSrv Server xvi Workstation xiv Software options 8-1 installation on a separate subnet C-1 Solaris default database cache sizes H-1 Stand-alone installation xiii (multiple) X on same LAN B-1 changing to a Distributed installation xiv X-term xiii, xxii, 1-2 prerequisites 1-1 Stand-alone server using in a Distributed installation xiv Starting Solaris as a non-root user 2-21 Solaris stand-alone 2-20 Solaris standalone 1-10 Sybase Client xvi Server xvi
T
TCP xvii xvi ports xvii Telnet xiii, 1-2 TFTP xxi activity xviii configuration using a proxy G-4, G-8 Server G-1 disabling G-3
NavisAccess Installation and Administration Guide Index-3