installation guide and release notes - general datacomm

ProSphere NMS Version 5.3.4Installation Guide and Release Notes032R906-V534, Issue 1 - February 2010

Copyright©2010 General DataComm, Inc. ALL RIGHTS RESERVED.This publication and the software it describes contain proprietary and confidential information. No part of this document may be copied, photocopied, reproduced, translated or reduced to any electronic or machine-readable format without prior written permission of General DataComm, Inc. The information in this document is subject to change without notice. General DataComm assumes no responsibility for any damages arising from the use of this document, including but not limited to, lost revenue, lost data, claims by third parties, or other damages. If you have comments or suggestions concerning this manual, please contact:General DataComm, Inc. Technical Publications 6 Rubber Avenue, Naugatuck, Connecticut USA 06770Telephone: 1 203 729 0271

TrademarksAll brand or product names are trademarks or registered trademarks of their respective companies or organizations.

Documentation

Revision History: GDC P/N 032R906-V534

Related Publications

-REV is the hardware revision (-000 , -001 , etc.) -VREV is the most current software version (-V530, V620, V722, etc. ) In addition to the publications listed above, always read the Release Notes supplied with your products.

Issue Date Release Description

1 February 2010 Initial release of Software Version 5.3.3

Description Part Number

Xedge / ProSphere Quick Reference (for all Xedge systems) 032R299-000

Xedge 6000 Hardware Setup Guide (for all Xedge systems) 032R440-REV

Xedge 6000 Technical Reference Guide 032R310-REV

Xedge 6000 Version 6.2.0 Software Configuration GuideXedge 6000 Version 6.2.0 Diagnostics GuideXedge 6000 Version 6.2.x Release Notes and Cumulative Patch Notes

032R400-V620032R500-V620032R901-V62X

Xedge MSPx Version 7.2.x Software Configuration GuideXedge MSPx Version 7.2.x Release Notes and Cumulative Patch Notes

032R401-V72X032R901-V72X

ProSphere NMS Version 5.3 User Guide 032R610-V53X

ProSphere NMS Version 5.3.X Installation and Release Notes (CORE, AEM, GFM, SPM, RTM)ProSphere NMS Version 4.4.0 Installation and Release Notes (CORE, AEM, GFM, MVS)

032R906-V53X032R906-V440

ProSphere NMS Version 5.3.4 Publication No. 032R906-V534Issue 1 - February 2010

Installa for GD

TABLE OF CONTENTS

.. 1-5

.. 1-6

. 1-6

1-6

. 1-8

. 1-8

... 1-9

.. 1-9

-9

11

1-13

-13

-15

15

16

9

...19

...20

....22

.....23

....23

......24

...24

...24

....25

..

Chapter 1: ProSphere Operating Platform....................................1-51.0 Overview ......................................................................................................................1-5

1.1 Software Reference.........................................................................................

1.2 ProSphere Core Functions ..............................................................................

1.3 New in ProSphere Version 5.3.4 .....................................................................

1.4 Limitations Resolved in ProSphere Version 5.3.4............................................

2.0 Minimum Requirements - Hardware ...........................................................................

3.0 Minimum Requirements - Software ............................................................................

4.0 User Management ......................................................................................................

5.0 Windows Installation and Setup .................................................................................

5.1 Installing MySQL for Windows ....................................................................... 1

5.2 Installing Informix for Windows .................................................................... 1-

6.0 Solaris Installation and Setup .....................................................................................

6.1 Solaris Installation .......................................................................................... 1

6.2 Creating NMS Admin Account ...................................................................... 1

6.3 Installing MySQL for Solaris ......................................................................... 1-

6.4 Installing Informix for Solaris ........................................................................ 1-

Chapter 2: ProSphere Installation ................................................... 11.0 Overview.........................................................................................................................19

2.0 Installing ProSphere 5.X Applications ........................................................................

2.1 Slot 0 Security Options ....................................................................................

3.0 Uninstalling ProSphere 5.X ........................................................................................

4.0 Starting the ProSphere 5.X Servers ...........................................................................

5.0 Starting the ProSphere 5.X Client...............................................................................

6.0 ProSphere Database Management ............................................................................

6.1 ProSphere NMS Database Backup (Windows) ...............................................

6.2 ProSphere NMS Database Backup (Solaris) ...................................................

7.0 Operating Guidelines ..................................................................................................

8.0 Known Issues................................................................................................................26

tion & Release Notes C Part No. 032U656-C01

Publication No. 032R906-V534 ProSphere NMS Version 5.3.4Issue 1 - February 2010

Installation & Release Notesfor GDC Part No. 032U656-C01


Installafor GD

nodes itch arts

00 lated

. To t

d

oduct

d

Chapter 1: ProSphere Operating Platform

1.0 OverviewThis version of the ProSphere Network Management System (NMS) supports Xedge (Version 5.x and higher). ProSphere NMS may discover older versions of Xedge Swcode, with alarms and configurations screens functioning normally, however not all pof ProSphere NMS applications are known to work with those older versions.

This document is intended for qualified engineers who are familiar with the Xedge 60family of multiservice switches, Xedge network architecture and management, and reterminology. A thorough understanding of hardware/software requirements and a proficiency in the relevant operating environments are assumed.

This section provides the installation instructions for these workstation environmentsinstall the ProSphere software, refer to later sections of this document. For the latesinformation, contact your GDC representative or go to http://www.gdc.com .

1.1 Software ReferenceThis version of ProSphere NMS has been tested and is supported on Sun/Solaris anMicrosoft Windows platforms listed below. The following table describes software modules relevant to ProSphere NMS. In this document, short forms of the software prnames are used.

Note: IMPORTANT! This version of ProSphere NMS has been tested for installation on, anoperation with the Solaris Version 2.10 up to the May 2009 release.

Table 1: Software Reference

Software Components Part Number Version

ProSphere NMS Software Product 032U656-C01 Version 5.3.4

ProSphere InformixDatabase Software for Windows

-- Version 7.25

ProSphere Informix (Database Software for SUN/Solaris)

032U641-C01 Version 7.25

MySQL Enterprise Server Database Software (for Solaris or for Windows)

Ref: SUN website Version 5.0

Solaris Software Product Ref: SUN website Ver 2.9

Ver 2.10 (up to May ‘09)

Windows Operating System Ref: Microsoft website Windows XP Pro

Windows 2003 Server

Windows 2008 Server



ns

ords

ins .

, and o the

g a

tions.

TM.

etc.

also aved).

ame

1.2 ProSphere Core FunctionsProSphere NMS is comprised of the following core functions. Note that not all functiomay be required for your network environment.

• User Management provides for the addition/removal of users, changing passwfor existing users, and defining access privileges to users.

• Topology Management performs Auto-Discovery of the Xedge network, maintanetwork topology, and displays a map of nodes, cards, links and connections

• Alarm Management polls each discovered device for its current active alarmsreceives alarms from Xedge slot controllers configured to send SNMP traps tNetwork Management station.

• Configuration Management generates the Explorer tree or the shelf GUI thatrepresents the entire topology for the purpose of adding, deleting or modifyinnode, slot, link or connection in the network.

• Service Provisioning Management configures Pseudowires and ATM connec

• Routing Management generates deterministic routing tables for the Xedge A

• File Management provides backup/restoral of configuration, trap/alarm logs,

Note: Detailed operating information and procedures are provided in the ProSphere User Guide listed in the front of this document.

1.3 New in ProSphere Version 5.3.4• (MR10155) Allows user to change circuit desciption in manage circuit screen;

allows user to sort accending or decending in service set. (Sorted order not s

• (MR10155) Allows configure change trap to go up to active alarm even if the strap is already in the active alarm table.

• Move: Added initialize route in RTM Route Viewer tab

• Added send file (single files only) in RTM Route Viewer Tab

• Added Dialog box to Import [All] circuits option.

1.4 Limitations Resolved in ProSphere Version 5.3.4• (MR10170) Fixed shelf display for PCX2

• (MR10160, MR 10173) Fixed RTM file transfer status

• (MR10176) Fixed RTM file transfer to legacy controller using ssh

• (MR10121) Remove node that has no routes out of Manage Route Screen

• (MR10120) Fixed some issues with sending file from Route Viewer Tab

• (MR10174) Manage Route Table will not be regenerated on tabchanged.

• RTM: Fixed file progress bar which was not resetting.

• (MR10186) Failed downloads locked up ProSphere after SSH was enabled.



Installafor GD

gacy

hile

ile

r

• SSH did not return error when attempting remote command to non existing lecontroller.

• Added confirm message when user click import All circuits

• (MR10191) Fixed nodal transfer status not updated correctly, showed error wall slots show ok.

• (MR10193) Notify user of file tranfer failure in Routes Viewer screen.

• (MR10194) DS3 Lim missing in shelf view for PCX and PCL

• (MR10195) Fixed problem with initialize route.

• (MR10196, MR10197) Slot controllers indicate bin&ascii when only the ascii fis on the drive. Node level now shows neither bin nor ascii)

• (MR10200) Fixed progress bar in the Route Viewer stayed as failed.

• Fixed local storage of routing files.

• Fixed spvcId range of ids allowed for PCX from 5000 to 4000.

• Adjusted rate at which SPM writes connections to switches to compensate fosnmp issues.



r ce. quired.

ver

d for

2.0 Minimum Requirements - Hardware The following are minimum requirements for Windows and SUN workstations. Higheprocessor speed and more memory can significantly increase application performanWhen managing more than 30 nodes, a higher processor or more memory may be re

• Sun Blade 1000 Workstation: 600 MHz; 4 GB RAM; 80 GB disk space; CDROM/DVD Drive

• PC: Intel Pentium Processor, 1GHz; 2 GB RAM; 80 GB disk space; CDROM/DVD Drive

Note: Consult your authorized ProSphere/Xedge representative for advice on specific hardware/software requirements other than the ones mentioned above.

3.0 Minimum Requirements - SoftwareFor SUN Platforms:

1. Solaris OS Ver 2.9, or Solaris Ver. 2.10 (up to May ‘09)

2. Informix SE 7.25.UC1; Connect 2.40.UC1-3 for Solaris 2.9 or 2.10,or MySQL Version 5.0 Enterprise Server for Solaris

3. ProSphere NMS

For PC Windows Platforms with Informix”

1. Win XP Pro/Service Pack 2, Service Pack 3, Win 2003 Server or Win 2008 Ser

2. Informix SE 7.2.5 TC3X3 for Windows 2000/XP/2003 Server, or MySQL Version 5.0 Enterprise Server for Windows

3. ProSphere NMS

Note: The MySQL or Informix database server system is required for object persistence anRTM applications. The MySQL software is acquired by the user. Informix must be purchased with ProSphere NMS, for the Windows or Solaris platform.



Installafor GD

elow.

t

ted

s

“No rks.

m,

ver d.

4.0 User ManagementThe default usernames and passwords for ProSphere client applications are listed b

5.0 Windows Installation and SetupThe following installation instructions are for Windows Operating Systems. You musperform the following procedure in the order given.

Before you begin:

• Refer to the hardware specifications accompanying your PC to ensure that processor speed and memory capacity meet ProSphere requirements.

• Contact your System Administrator for loading Windows OS and the associaService Pack.

• The Informix Database Server for Windows or the MySQL Server for Windowmust be installed before the ProSphere software, as described below.

Note: You must provision your ProSphere environment with either MySQL or Informix. TheDatabase” option is for engineering use only and is not supported in customer netwo

5.1 Installing MySQL for WindowsThe following procedure installs the MySQL Server software on the Windows platforand includes setting the password for the root account.

1. Run the MySQL Server Setup Wizard. At the Welcome screen, click Next .

2. At the Setup Type screen, select Typical , then click Next .

3. At the Installation screen, click Install to begin the installation.

4. During the installation process, MySQL information screens are displayed. Click Next as necessary to proceed.

5. When the Wizard Completed screen appears, select the Configure MySQL Seroption, then click Finish to exit the wizard and launch the Configuration Wizar

6. At the Welcome screen, click Next to configure the MySQL Server instance.

7. At the first MySQL Server Instance screen, select Detailed Configuration , then click Next .

8. At the server type screen, select Server Machine , then click Next .

User Types and Privileges Default Username Default Password

Super User has all network management privi-leges, including user management.

ProAdmin manager

Administrator has all network management privileges, but cannot create/delete users.

nmsadmin nmsadmin

Operator has all alarm and circuit privileges. Cannot change configuration or topology.

nmsoper nmsoper

Monitor has read-only access to modules. prospher prospher



Page 1

nless

d cked,

9. At the database usage screen, select the Multifunctional Database option, then, click Next .

10. At the drive and directory screen, select the destination for the InnoDB datafile, uyou want to use the default settings. Click Next to continue.

11. At the current connections screen, select Decision Support (DSS)/OLAP to set the appropriate number of concurrent connections to the server. Click Next .

12. At the networking options screen, set the following options:

• Select Enable TCP/IP Networking

• In the port number field, type 3307

• Select Add firewall exception for this port

• Select Enable Strict Mode

13. Click Next to continue.

14. At the character set screen, select Standard Character Set, then click Next .

15. At the Windows options screen, set the following options:

• Select Install As Windows Service

• For the Service Name, select MySQL

• Select the option that will Launch the MySQL Server automatically

• Select Include Bin Directory in Windows PATH


17. At the security options screen, set the following options:

• Select Modify Security Settings

• Type the root password

• Retype the root password

• Select Enable root access from remote machines


19. At the execute screen, click Execute to start the configuration. Each task is markewith a check as the configuration sequence proceeds. When all four fields are checlick Finish to close the wizard.

20. MySQL installation on your Windows platform is complete. Proceed to Chapter 2: ProSphere Installation.

0 Installation & Release Notesfor GDC Part No. 032U656-C01


Installafor GD

m,

r .

tory:

.

.

e

.

5.2 Installing Informix for WindowsThe following procedures install the MySQL Server software on the Windows platforand includes setting the password for the root account.

Be sure to have your IBM Informix product materials at hand, including serial numbekeycard and CD-ROM accompanying your product. Both are required for installation

1. Insert the Informix CDROM in the CD Drive.

2. From Windows Explorer, navigate to the CD-ROM drive and open the Informix/Windows folder. Double-click on setup.exe to launch the Informix installer for Windows.

3. At the Welcome prompt, click Next . The Key Input Dialog screen appears.

4. Enter the serial number and key value supplied with your Informix product. Thisinformation is printed on the label of the installation CD. Click Next when finished.

5. At the Choose Destination Location window, select the default installation direc

c:\Program Files\Informix\IBM Informix SE

6. Click Next. At the Set up Type window, click Next to accept the Typical install.

7. In the Select Program Folder window, click Next to accept the existing folder nameInformix SE will now install on your PC.

8. Proceed to the next section to set up the Informix environment, server and host

5.2.1 Set up Informix Environment/Server9. From Windows Explorer, go to the Informix bin directory (below) by traversing th

tree:

c:\Program Files\Informix\IBMInformix SE\bin

10. Double-click the setnet32.exe application. The Informix Setnet32 screen appears



Page 1

ow:

11. At the Environment tab, shown above, set up the following:

A. Scroll down the list of Informix Client /Server Environments and select:

INFORMIXSERVER

B. In the Edit Environment Variable field, type SE as shown in the example, then click Set to set the variable.

C. Click the checkbox to select the Use my settings , then click Apply .

12. Now click the Server Information tab. Enter server information as described bel

A. In the Informix Server field, type SE.

B. In the Hostname field, type the hostname of your computer.

C. In the Protocol Name field, select sesoctcp

D. In the Service Name field, type sqlexec

E. Leave the Options field blank.

F. Click the Apply button.

G. When prompted to “Define New Informix Server?”, click OK.

H. Click the Make Default Server button.

13. Now click the Host Information tab. Enter host information as described below:

A. In the Current Host field, type or select your hostname.

B. In the User Name field, type your PC Administrator (administrator) name.

C. For the Password Option, select Password .

D. In the Password field, type the PC Login Administrator’s password.

E. Click the Apply button.

F. When prompted to “Define New Host ?”, click OK.

14. Informix installation on your Windows platform is complete. Proceed to Chapter 2: ProSphere Installation.



Installafor GD

gin, ur

r

the

“No rks.

6.0 Solaris Installation and SetupThese procedures set up a stand-alone SUN workstation with Solaris. Before you beyou must have the following information available. If you need assistance, contact yosystem administrator.

• Name of the Workstation

• IP Address for the Workstation

• Correct IP Mask so that you can communicate with other workstations in youLAN.

• Name Service will be None (no DHCP or NIS will be used for this setup)

• Gateway IP Address

• The Informix Database Server or the MySQL Server must be installed beforeProSphere software, as described below.

Note: You must provision your ProSphere environment with either MySQL or Informix. TheDatabase” option is for engineering use only and is not supported in customer netwo

6.1 Solaris InstallationThe following installation instructions apply to networked stand-alone system type configurations only.

Note: CAUTION ! The following Solaris installation and setup procedures will completely remove all files currently on your workstation.

1. Login as root .

2. Insert Solaris CD into the CDROM drive.

3. Shut down the workstation by typing the following commands:

sync

halt

4. At the "OK" prompt type:

boot cdrom

5. Follow the on-screen instructions, as prompted.

6. Enter the following information as prompted:

Hostname ProNMS (example)Networked Yes

IP Address 200.200.200.5

7. In the Name Service dialog box, select None, then click Continue .

8. In the Subnets dialog box, select Yes or No, depending on your network configuration.

9. Enter the netmask in the Netmask dialog box, then click Continue .



Page 1

ne,

x.

heck

x

ady.

10. Specify the time zone in the Time Zone dialog box, the click Set . Otherwise, use Geographic Region dialog box to specify the region and time zothen click Continue .

11. Set Date and Time in the Date and Time dialog box, then click Continue .

12. In the Solaris Interactive Installation window, select initial or upgrade , then click Continue .

13. In the Allocate Client Services? window, click Continue .

14. In the Language dialog box, select the desired language, then click Continue .

15. In the Software dialog box, select End User System Support , then click Continue .

16. In the Disk dialog box, select disks , then click Continue .

17. In the Preserve Data dialog box, click Continue to overwrite.

18. In the Automatically Layout File Systems? dialog box, select Auto Layout

19. Select / and swap (ONLY) and then click Continue .

20. To change layout, press Customize in the File System and Disk Layout dialog bo

21. Depending on disk size, enter the size for / in the Customize Disks dialog box. Cthe free space and then enter the remaining space for swap. For example, for 2GB disks, delete every entry in the Customize Disks dialog boexcept for:

/ set to 1540 MB swapset to remaining MB

22. Select OK, then click Continue .

23. In the Mount Remote File System? dialog box, click Continue .

24. In the Profile dialog box, click Begin Installation and ignore warning.

25. Reboot the system, as prompted.

26. When the installation is complete, a prompt appears, indicating the system is re

27. Proceed to Section 6.2 Creating NMS Admin Account in this chapter.



Installafor GD

l to set

ctions

udes

6.2 Creating NMS Admin AccountIt is recommended that you create a separate, new user account (nmsadmin ) for ProSphere. Refer to your Solaris documentation and use the appropriate Solaris toothe following values:

• User name: nmsadmin

• Login Shell: C

• Password: Select Normal Password.... (This prompts for a password and confirmation of the password.)Type nmsadmin for password, then click OK.

• Select Create Home Directory button.

• Path: /export/home/nmsadmin

Once the NMS Admin Account has been successfully created, proceed to the next sein this chapter to install and set up the MySQL or Informix database software.

6.3 Installing MySQL for SolarisThe following procedure installs and sets up MySQL on the Solaris platform, and inclsetting the password for the root account.

1. Login as root.

2. Execute groupadd mysql to add mysql group.

3. Execute useradd -g mysql mysql to add mysql user to mysql group.

4. Copy the appropriate file to local directory:

mysql-5.0. [xx] -solaris [yy] -hardware-bittype.pkg.gz

5. Execute gunzip filename.pkg.gz

6. Execute pkgadd ñd filename.pkg and use all default options. This will install mysql server to the /opt/mysql directory.

7. Go to /opt/mysql/mysql/scripts and run the following:

./mysql_install_db --user=mysql --ldata=/opt/mysql/mysql/data

8. Go to /opt/mysql/mysql/bin and run the following:

./mysqld_safe --datadir=/opt/mysql/mysql/data --user=root --port=3307 &

Note: This command can be added to startup script for automatic startup. (Auto detection and launch will be added to ProSphere NMS in a future release.)

9. To set the root password, eecute from /opt/mysql/mysql/bin the following:

./mysqladmin -u root --host= [hostname] --port=3307 password [root password]

10. To change the root password, execute the following: --p [oldpassword]11. MySQL installation on your Solaris platform is complete.

Proceed to Chapter 2: ProSphere Installation.



Page 1

ys.

. ion:

ris

iles

6.4 Installing Informix for SolarisThis section describes how to install Informix for Solaris via a customized script thatfacilitates the Informix Database Server. This procedure requires Informix license ke

1. Login as nmsadmin (not as root).

2. Open a terminal window and type: pwd to ensure you are in the $HOME directoryIt should show your $HOME directory, the full user account path for your applicat/export/home/nmsadmin

3. Insert the appropriate ProSphere Informix CD in the CDROM drive for your Solaenvironment.

4. At the prompt, enter the following:

tar -xf /cdrom/cdrom0/common.tar

5. A series of compressed files are copied into the $HOME directory. Wait until all fhave been copied from the ProSphere CD.

6. Become super-user by typing su and then enter your super-user password. Your prompt should become # .

7. Begin the installation of Informix by following the on-screen instructions of the installation script “ProSphere Toolkit”. A sample session is provided below. In the sample session:

• Text in bold is the user input or key presses.

• Three ellipses (...) represent text that will be displayed on the screen.

• Plain text denotes screen prompts; Italic text denotes helpful comments.

• Do not use the Informix License Keys shown in the sample session. Use the Key that came with your ProSphere 5.X distribution.

Note: In the sample session, there are several questions that you must answer. For most questions, the default will suffice. The Toolkit will run as the user nmsadmin . Although the script offers additional applications, you will only install the Informix software.

./install

The ProSphere Management Toolkit is about to be installed...

What user will the Toolkit run as? [nmsadmin] <Enter>What group will the Toolkit run as? [staff] <Enter>What permissions should directories default to? [0775] <Enter>What permissions should executable files default to? [0775] <Enter>What permissions should all other files default to? [0664] <Enter>What temporary directory shall I unpack the Acrobat Reader in? [/tmp] <Enter>ADOBE SYSTEMS INCORPORATED ...This will display a long Adobe License Message. Press Enter or Space Bar to go to the end of the message.Type "decline" to exit the Adobe installer. decline ...The INFORMIX database software is about to be installed. ...Ready to continue? - Type no to exit. [yes] <Enter> ...



Installafor GD

tall?
Preparing to install the INFORMIX database; Are you ready to start the INFORMIX-Connect ins- Type no to exit. [ok] <Enter> ...Installing I-Connect as user "root"...Press RETURN to continue, or the interrupt key (usually CTRL-C or DEL) to abort. <Enter>
Enter your serial number (for example, INF#X999999 )Enter your serial number KEY (uppercase letters only)Press RETURN to continue, or the interrupt key (usually CTRL-C or DEL) to abort. <Enter> ...Preparing to load the INFORMIX-SE from the CD.Please have your INFORMIX License S/N and Key available.Extracting from CD... ...Are you ready to start the INFORMIX-SE install? - Type no to exit. [yes] <Enter>INFORMIX-SE Version 7.25.UC1Copyright (C) 1984-2000 Informix Software, Inc. ...Press RETURN to continue, or the interrupt key (usually CTRL-C or DEL) to abort. <Enter>

Enter your serial number (for example, INF#X999999 )Enter your serial number KEY (uppercase letters only) ...Press RETURN to continue, or the interrupt key (usually CTRL-C or DEL) to abort. <Enter> ...Installation of INFORMIX-SE complete.Installing and activating the necessary configuration files.If you do not want to specify a service number, use the default.What service number should sqlexec be using? [1525] <Enter> ...Installation of the INFORMIX database product is complete and activated.Do you wish to install the Installation Manager? [no] <Enter>Do you wish to run the Installation Manager? [no] noInstallation of the Toolkit is complete.

8. Installation of Informix is complete. Proceed to Chapter 2: ProSphere Installation.



Page 1


Installafor GD

w. ,

. lled.

or

ble

the IP

Chapter 2: ProSphere Installation7.0 Overview

This section describes the installation of all ProSphere Core applications, listed beloThese ProSphere applications allow for the management of users, topology, alarmsconfiguration, routing and file control.

• Services

• Global Fault Manager (GFM)

• ATM Element Manager (AEM)

• Service Provisioning Manager (SPM)

• Routing Manager (RTM)

Note: IMPORTANT! You must have a valid ProSphere serial number to install applicationsDepending on the serial number, the appropriate ProSphere applications will be insta

Note: IIMPORTANT! You must provision your ProSphere environment with either MySQL Informix. Return to Chapter 1: ProSphere Operating Platform for the appropriate installation and setup procedures for your platform.

8.0 Installing ProSphere 5.X ApplicationsProSphere applications are installed using GDCInstaller . The instructions given below are for reference only, please follow on-screen instructions.

1. Insert the ProSphere CDROM in the CD drive.

• For PC installation, if the installer does not start automatically from the CD, double-click installation file (SetupWin32.exe ) in D:, then follow instructions in Step 2.

• For Solaris installation, type cd /cdrom/cdrom0 then type./SetupSolaris and follow the instructions in Step 2.

2. When the Installer starts up, read the Welcome screen, then click Next .

3. Select one of the following Bundles:

• ProSphere Severs/Clients

• ProSphere Clients only

Note: If you are installing the Clients Only bundle, you must have installed the Servers on another workstation or PC, and you must have the IP Address of that machine availanow. You should also be able to ping that IP Address from your machine.

For each Client and Server machine, the hosts file must have an entry that refers to address and hostname of the opposite machine. For example: In the Server hosts file, add the following entry: [ client ipaddress] [ client hostname]In the Client hosts file, add the following entry: [ server ipaddress] [ server hostname]

Windows hosts file is found on c:\windows\system32\drivers\etc\hostsUNIX hosts file is found on /etc/hosts


Publication No. 032R906-V534 ProSphere NMS Version 5.3.4 Issue 1 - February 2010

Page 2

d

ress.

ing now.

then

fault

ust

CP),

switch. S.

S.

the

4. Enter your Serial Number, then click Next .

5. Select Choose Install Set to automatically select the Install set associatewith the Serial Number you entered. Click Next .

• If you selected ProSphere Clients Only, enter Your ProSphere Server IP Add• If you selected ProSphere Servers/Clients, continue to next step.

6. Select the Installation folder location (Default Recommended), then click Next .

7. Choose a Shortcut/Links Folder (Default recommended), then click Next .

8. If desired, enable Secure Shell access mode by selecting SSH, then click Next .

Note: IMPORTANT! You can only enable SSH during ProSphere installation. To avoid havto reinstall ProSphere later and restore your database and connections, enable SSH

9. (PC Only) Click to select the Windows Informix Configuration option to configureInformix for ProSphere.

10. Review the Pre-Installation Summary, then click Install to proceed.

11. The display will show a series of post-installation scripts running automatically, the installation will be complete. Click Done to finish the ProSphere installation.

12. Reboot the PC or SUN Workstation.

13. (PC Only) You must now create the ProSphere database as follows:

A. From Windows Explorer, navigate to the ProSphere Database directory (by deit is C:\Program Files\ProSphere5.3\data\database

B. Double-click on the createdb.bat batch file. A message window displays the progress as the database is being created.

C. When complete, close the message window.

14. You can now use the ProSphere applications. If you have enabled SSH, you mperform the SSH configuration procedures below.

8.1 Slot 0 Security OptionsThe ISG2 and PCX in slot 0 support the following security protocols: Secure Copy (SSecure Shell (SSH) and Internet Security (INET).

8.1.1 Secure Copy (SCP)SCP consists of an encrypted file transfer session between ProSphere NMS and the When a configuration change is made at the switch, a trap is sent to ProSphere NMProSphere then automatically initiates the SCP and gets the new config.cfg file from the switch’s slot-0 controller over an encrypted file transfer session. SCP is used only by the following ProSphere NMS functions:

• When ISDN.bin is being transferred from ProSphere NMS to the VSM for QSIG signaling only.

• When config.cfg file is being backed up from the switch to ProSphere NM

Note: As an alternative, operators can use a terminal SSH client (such as PuTTY) to openencrypted session.



Installafor GD

s, the client of the

users.

word

as

e

te key

8.1.2 Secure Shell (at Server Side)There is no SSH configuration required on ProSphere servers. When the client startprivate key is encrypted and sent from the ProSphere Client GUI to the server. The will verify SSH access to each existing node. If an existing node supports SSH, one following SSH status messages will be displayed at the bottom right corner of the ProSphere window:

SSH ActiveSSH Inactive

8.1.3 Configure Secure Shell (Client Side)Perform the following steps to configure the SSH IP address, password, key pairs and

1. Start the ProSphere Client as described in Section 11.0.

2. Add the IP address to the seed table.

3. Once the seed table is configured, select File->Setup SSH . The SSH Key Setup and Verification window appears.

4. Select Server in the “Create key for user” list.

5. Set up the key pair for the server by typing the ISG2 or PCX password in the Passfield.

6. Generate the private/public key pair and load the created key to existing nodes follows:

• For Solaris, select the key type (RSA or DSA), then click Create .

• For Windows, click Create , then enter the key type in the dialog box.

Note: IMPORTANT! While the system is generating the key pair, you must move the mouscontinuously over a blank area of the screen (Windows OS).

7. Repeat Step 4. through Step 6. for any authorized NMS users, as required.

8. This completes the configuration of Secure Shell for existing nodes and users.

• If nodes are to be added later to the topology, select Server in the “Create key for user” list, then click the Load button.

• To revoke access privileges for a user, select the desired user from the “Creafor user” list, then click the Remove button.

Note: As implemented in ProSphere NMS, the Secure Shell key size is fixed at 1024.



Page 2

ion ccess h are

the then

8.1.4 INET Security AccessFor the ISG2 and PCX only, INET is a firewall security protocol that works in conjunctwith SSH/SCP. When enabled, INET prevents unauthorized access by rejecting all aattempts except SNMP port 161, SNMP port 162 Traps, ICMP, and TCP Port 22, whicused by SSH/SCP.

1. To enable/disable INET Firewall in ISG2 or PCX:

• type ./inetaccess b eth0 (where b indicates blocking)

• type ./inetaccess u eth0 (where u indicates unblocking)

2. When logging into a craft port of a switch, after the password press Control-C.

3. At the root prompt, type the INET blocking string. (This only needs to be done the first time.)

9.0 Uninstalling ProSphere 5.XThe Uninstall program will intentionally leave certain files (log files, databases, etc.) onworkstation and will show a list of the files not deleted. If desired, back up these files,delete them manually.

To uninstall ProSphere from a PC:

1. Select Add/Remove Programs from the control panel.

2. Select the ProSphere application, then click Remove . This starts the Uninstall program.

3. When the uninstall process is complete, click Done . Reboot the PC.

To uninstall ProSphere from a SUN/Solaris workstation:

1. At the /export/home/nmsadmin directory, delete the ProSphere Installationdirectory by typing:

rm -rf ProSphere5.3

Note: By default, the path to the directory is /export/home/nmsadmin/ProSphere5.3

2. From the /var/tmp directory , delete the Log directories by typing:

rm -rf Pro*

3. When complete, reboot the workstation.



Installafor GD

you ddress

ick on

ow is

re

d.

10.0 Starting the ProSphere 5.X ServersBefore you start ProSphere servers and perform network discovery for the first time,must ensure that the your workstation has a route table that points to the external IP aof the node’s slot-0 controller. Consult your IT personnel as needed.

FROM A SOLARIS WORKSTATION

1. Open up a terminal window.

2. You must become a super user to start ProSphere user. Type su to change user to root, click Enter, then enter the root password.

3. From the /export/home/nmsadmin/ProSphere5.3/bin directory, type: ./StartServers

4. After the Servers have started, from the ProSphere Process Service window, clthe Explorer Icon.

5. Launch ProSphere Client Apps. The logon Screen will be displayed.

6. Log on using a default User ID and Password. The ProSphere Client Apps winddisplayed.

FROM A WINDOWS WORKSTATION

1. From Start>Programs, click on ProSphere 5.X Servers.

2. After the Servers have started, click on the Explorer Icon found on the ProSpheProcess Service window. The Logon Screen will be displayed.

3. Log on using a default User ID and Password. The Explorer window is displaye

11.0 Starting the ProSphere 5.X Client

FROM A SOLARIS WORKSTATION

1. Open up a terminal window.

2. From the /export/home/nmsadmin/ProSphere5.3/bin directory, type:

./ProClient

3. The Logon Screen will be displayed.

4. Log on using a default User ID and Password (see Section 4.0 User Managment). The ProSphere Client Apps window is displayed.



Page 2

al essary data ival e ).

ing:

:

at all

12.0 ProSphere Database ManagementProSphere NMS is designed around a centralized database which allow the individuProSphere, RTM and SPM applications to share common data. This includes the necdatabase files, registry files, executable binaries, libraries, and other files in one or twodirectories. It is strongly recommended to back up the entire data directories for archpurposes, or to save a copy to a backup machine. The procedure varies based on thplatform (Windows or Solaris) and the database software in use (Informix or MySQL

12.1 ProSphere NMS Database Backup (Windows)Backing up ProSphere on a Windows 2000 or XP machine simply involves copying the ProSphere 5.x data directory from the source machine to the destination machine as described below.

1. Halt the ProSphere process.

2. Browse to C:\Program Files\ProSphere5.x

3. Copy the entire data directory. This includes Informix database, RTM and SPM (see detail at right).

Note that if you are using the MySQL database software, you need to browse to C:\Program Files\MySQL\ and copy the entire data directory. This includes the gemdb, rtmdb and mysql directories.

4. Save the data directory to the destination machine.

12.2 ProSphere NMS Database Backup (Solaris)1. At the Solaris source machine, copy the directory

/export/home/nmsadmin/ProSphere5.x/data

into a new directory with a different directory name [cp -r] (example databu ).

Note that if you are using the MySQL database software, you need to browse to /opt/mysql/mysql/data/ and copy the entire data directory. This includes the gemdb , rtmdb and mysql directories.

2. As nmsadmin user, in the /export/home/nmsadmin/ProSphere5.x/ directory, tar the ProSphere data directory:

tar cvf data.tar data

3. The tar file permissions is changed. Change the permissions to the original sett

chmod 755 data.tar

4. At the target machine, rename the original installed data directory to:

dataoriginal

5. Copy the tar file to the target machine and un-tar in the ProSphere 5.x directory

tar xvf data.tar

6. The ProSphere 5.x database is now transferred to the backup machine. Note ththe properties definitions and registries have also been copied and transferred.

Data Directory (Windows)



Installafor GD

ing ress of

its

rder is ervers.

d for plit oller X,

ion re to

to e

y ings.

cease

restart

e ge

13.0 Operating Guidelines• When ISG2 or PCX is in slot0, TFTP communications from Windows Operat

System must be directed to the outside IP address (that is, the outside IP addthe Slot-0 controller).

• In the case of a Multicast, if the root circuit is killed after startup, the leaf circuwill also go down. In this situation, it may be necessary to stop the entire conference and restart it.

• Informix for Windows 2000 must have a continuous Ethernet connection in oto provide Object Persistence on discovered networks. If the Ethernet signal interrupted, you must re-establish the connection and restart the ProSphere s

• When a node has two ISG2/PCX slot controllers with IP addresses configurethe same Ethernet network, Discovery will work but Telnet could fail due to a sMOLN condition. To resolve this, change the IP address of the non-slot 0 contrto a different network, and configure a static route for the non-slot 0 ISG2/PCusing the interface of 40 .

• It may be necessary to maximize the ProSphere window to view all fields.

• (MR9679) By default, ProSphere NMS receives alarm traps when configurathas been changed and saved in the slot. The received trap causes ProSpheautomatically save the updated config.cfg file from the switch via TFTP. Be aware that if ProSphere Alarm ID #9 is masked (Mask Alarm =Yes), these traps are ignored and any configuration updates saved to the slot will not be savedProSphere. To save configuration changes without displaying every trap in thActive Alarms display, set Alarm ID #9 to Mask Alarm=No and AutoClear=Yes.

• Be aware that setting any alarm to AutoClear =Yes will cause the system to regularly poll for that alarm. This can result in excessive polling traffic and maoverflow the log file. As a general rule, alarms should remain at the default sett

• In the ProSphere/bin/ProClient.lax file, if the server hostname is longer than 15 characters, the name is truncated and Client<>Server updatesworking. To resolve this, edit the file to restore the truncated characters.An example ProClient.lax file is shown below:

lax.nl.java.option.additional=Dprosphere.server.host=localhos -Dprosphere.slot0ipbase=16 -Djava.rmi.server.hostname= h-hq-hub-hpov-nu

where a host name with more than 15 characters, h-hq-hub-hpov-nu , has been edited to restore the truncated characters. Once edited, save the file andProSphere.

• (MR10177) If intermittent authentication failure events are being logged in thXedge Events Log, check for a difference in the community name in the Xedswitches and in the XPM /data/properties/oidlist file. If a discrepancy is found, change the community definition in the XPM file.



Page 2

ent

the he

n as his ous

op

erface.

not

ice.

14.0 Known Issues• When the Network Timing Module is set to Line Timing (that is, no clock is

attached at the NTM “IN” connector), a NO NTM BITS CLOCK LINE INPUT trap will always be sent to the ProSphere Alarm window and to the Xedge EvLog. Timing is not adversely affected.

• The LIM1 or LIM2 associated with a PCX slot controller cannot be selected astiming source from the ProSphere NMS interface. To select LIM timing, use tcraft or Telnet interface.

• When a ISG2 slot controller is installed in an Xedge 6280 chassis (also knowthe IMX chassis), a trap reports that the “Secondary BITS Clock” isn’t good. Tchassis model doesn’t have a secondary BITS clock, hence, this is an erronereport. The ISG2 and the system timing is not adversely affected.

• AutoDiscovery may get stuck when discovering links. In this situation, this, stand restart Discovery via the F6 menu command.

• SPM does not perform validation checks for VPCI or Bandwidth parameters.

• (9915) For an OCN link, Scramble Cell Payload or Add Coset Poly cannot bechanged via ProSphere. These settings can only be changed via the craft int

• (9958) In a switch with a PCX or ISG2, Switched Fabric Redundancy is not supported via ProSphere. This application can only be enabled via the craft interface.

• (9698) In PCX applications with APS, the Group State Graphic (OC-N) does update with an APS switch.

• (9723) To get a read from the switch, the Read button needs to be clicked tw

• (9824) The Authentication Table cannot be modified for slot-0 controllers viaProSphere. It can only be modified via the craft interface.


installation guide and release notes - general datacomm

Documents