Alcatel-Lucent OmniVista 2500 NMS Enterprise Network Management System Installation Guide
إعلان
إعلان
Installation Guide
for
OmniVista 2500 NMS Enterprise
Version 4.2.1.R01
September 2016
Part Number 060444-10
READ THIS DOCUMENT
ALE USA Inc.
26801 West Agoura Road
Calabasas, CA 91301
+1 (818) 880-3500
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Table of Contents
Upgrading from a Previous Version of OmniVista 2500 NMS ..........................................20
ii
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
This document details the OmniVista 2500 NMS Enterprise 4.2.1.R01 (OV 2500 NMS-E
4.2.1.R01) installation/upgrade process. For information on getting started with OmniVista 2500
NMS after installation (e.g., using the Web GUI, discovering network devices) see the Getting
Started Guide in the OmniVista 2500 NMS on-line help (accessed from Help link at the top of the main OmniVista 2500 NMS Screen).
Specific platform support and recommended system configuration information are available in the OmniVista 2500 NMS-E 4.2.1.R01 Release Notes.
Important Note:
This document details installing OV 2500 NMS-E 4.2.1.R01 as well as
upgrading from a previous version of OmniVista 2500 NMS .
If you are upgrading from a previous version, there are upgrade tasks that must be performed before installing
the new version of OmniVista. If you are upgrading, go to the upgrade section.
OV 2500 NMS-E 4.2.1.R01 is installed as a Virtual Appliance, and can be deployed on the following hypervisors: VMware ESXi, VirtualBox, Hyper-V:
• VMware ESXi: 5.5 and 6.0
• VirtualBox: 5.0.10
• MS Hyper-V: 2012 R2.
The sections below detail each of the steps required to deploy OV 2500 NMS-E 4.2.1.R01 as
Deploying the Virtual Appliance in VMware ESXi
Note that in the instructions below, vCenter is used for demonstration purposes.
1. Download and unzip the OVF package.
2. Log into vCenter and open the vSphere client.
3. Select the Host on which you want to install OV 2500 NMS-E 4.2.1.R01, click on File -
Deploy OVF Template. The Deploy OVF Template Wizard appears.
1
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
4. Click on the Browse button and locate the OV 2500 NMS-E 4.2.1.R01 Application file in the unzipped OVF folder (e.g., ovnmse-4.2.1.R01-65.0.ovf).
5. Select the file and click Open (or double click on the file). The file will appear in the “Deploy from a file or URL” field. Click Next. The OVF Template Details Screen appears.
2
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
6. Review the OVF details and click Next. The End User License Agreement Screen appears.
3
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
7. Review the License Agreement, click Accept, then click Next. The Name and Location
Screen appears.
8. Specify a Name and Inventory Location for the deployed template, then click Next.
9. If you have configured a Resource Pool, the Resource Pool Screen (below) appears. Select the host server and click Next.
4
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
If a host server only has storage configured, the Disk Format Screen will appear.
If you have multiple storage locations configured, the Storage Screen (below) appears. Select the destination storage where the template is to be deployed, then click Next. The Disk Format
Screen appears.
5
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
10. Select Thin Provision, then click Next. The Network Mapping Screen appears.
11. Select network that the deployed OVF template will use, then click Next. The Ready to
Complete Screen appears.
6
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
12. Review the configuration and click Finish. (You can select the “Power on after deployment” option to automatically power on the VA when deployment is complete.) A status window appears and displays the progress of the deployment. If you select the “Close this dialog when completed” option, the progress window will automatically close when the deployment is complete. If not, click Close at the completion of the deployment to close the window.
13. If the new Virtual Appliance was not powered on via the deployment wizard, power on the
VM now. Right-click on the VM in the Navigation Tree and select Power - Power On.
Once the Virtual Appliance is powered on, go to Completing the OmniVista 2500 NMS-E
4.2.1.R01 Installation to complete the installation.
Deploying the Virtual Appliance in VirtualBox
Note that in the instructions below, VirtualBox 5.0.10 in Windows 7 is used for demonstration purposes.
1. Download and unzip the OVF package.
2. Log into Windows 7 and open the Oracle VM VirtualBox tool.
7
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
3. Click File > Import Appliance.
4. Click browse icon then select the folder which you extracted at step 1 above, then click
Next.
8
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
5. Review the configuration and click Import.
6. The Software License Agreement window displays, click on Agree.
9
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
7. A status window appears and displays the progress of the deployment.
8. After the process is completed, right-click on the VM in the Navigation Panel and select Start
- Normal Start.
10
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
9. Configure the Network Adapter. Right-click on the VA and select Settings.
10. Select Network, then select the Network Adaptor that you created when you configured
VirtualBox.
11
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Once the Virtual Appliance is powered on, go to Completing the OmniVista 2500 NMS-E
4.2.1.R01 Installation to complete the installation.
Deploying the Virtual Appliance in Hyper-V
Note that in the instructions below, Hyper-V in Windows 2012 is used for demonstration purposes.
1. Download and unzip the OVF Hyper-V package.
2. Log into Windows 2012 and open the Hyper-V tool.
3. Select the Host on which you want to install OmniVista 2500 NMS, click on Actions > Import
Virtual Machine.
12
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
4. The Import Virtual Machine Wizard appears.
5. Click Next to go to the Locate Folder Screen, select the Folder that you extracted in Step 1, then click
Next.
13
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
6. Select the Virtual Machine to import (Default = OmniVista-2500 NMS-E-4.2.1.R01), then click Next.
7. Select the default Import Type: Copy the virtual machine (create a new unique ID), then click Next.
14
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
8. Specify folders to store the Virtual Machine files (or accept the default folders), then click
Next.
9. Choose folders to store the Virtual Hard Disks or accept the default location and click Next.
15
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
10. Review the import configuration and click Finish. (Click Previous to return to a screen and make changes.)
11. Configure the Network Adapter. Right-click on the VA and select Settings.
16
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
12. Select Network Adapter, then select the Virtual Switch that you created when you configured Hyper-V.
After the process is completed, right-click on the VM in the Navigation Panel and select Start.
Once the Virtual Appliance is powered on, go to Completing the OmniVista 2500 NMS-E
4.2.1.R01 Installation to complete the installation.
Completing the OmniVista 2500 NMS-E 4.2.1.R01 Installation
Follow the steps in the following sections to complete the OV 2500 NMS-E 4.2.1.R01 installation.
Launching the Console, Setting a Password and an IP Address
1. Launch the Console for the new VM. (In vCenter, this can be done by right-clicking on the VM in the Navigation Tree and selecting Open Console.) The password prompt appears.
17
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
2. Specify a new administrative password, then re-enter to confirm the new password. Press
Enter to configure System IP.
Note: The password should be an alpha-numeric string with a minimum of eight (8) characters and should not be based on dictionary words. Be sure to store the password in a secure place. Users will be prompted for the password at the end of the installation. Lost passwords cannot be retrieved.
3. Enter an IPv4 address.
4. Enter the IPv4 network mask.
5. Press y and Enter to confirm, then press Enter to continue.
6. The Memory Configuration Based on Network Size option is displayed.
Select the number of devices OV 2500 NMS-E 4.2.1.R01 will manage. To select a range, enter its corresponding number at the command prompt (e.g., enter 2 for Medium). Ranges include:
• Low (fewer than 500 devices)
• Medium (500 to 2,000 devices)
• High (2,000 to 5,000 devices)
• Very High (5,000 to 10,000 devices).
Press y and Enter to confirm, then press Enter to display the Configure the Virtual Appliance
Main Menu.
18
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
7. The Configure The Virtual Appliance Main Menu is displayed.
8. Enter 2 and press Enter to display the current configuration.
The current OV appliance configuration is displayed. You can go to the Configure The Virtual
Appliance Menu to configure additional settings (e.g., Default Gateway, Proxy, DNS) that may
be required to access OV 2500 NMS-E 4.2.1.R01 and perform upgrades. Please configure other settings as required.
19
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Note: OV 2500 NMS-E 4.2.1.R01 makes an HTTPS connection to the OmniVista 2500 NMS
External Repository for upgrade software, Application Visibility Signature Files, and
ProActive Lifecycle Management. If the OmniVista 2500 NMS Server has a direct connection to the Internet, a Proxy is not required. Otherwise, a Proxy should be configured to enable OV 2500 NMS-E 4.2.1.R01 to connect to the OmniVista 2500 NMS External
Repository.
9. Press Enter. The Virtual Appliance Menu is displayed again.
10. After completing all required settings (and after all services are running), enter
https://OVServerIPaddress in a supported browser to launch OV 2500 NMS-E 4.2.1.R01.
Upgrading from a Previous Version of OmniVista 2500 NMS
Follow the steps below to backup an existing OmniVista 2500 NMS Database and restore it to the new installation. The procedure is different depending on whether your existing installation is
Note: You cannot upgrade directly from OmniVista 2500 NMS 4.1.1 or 4.1.2R01/R02 to
4.2.1.R01. You must first upgrade from 4.1.1 or 4.1.2R01/R02 to 4.1.2.R03. See the applicable Installation Guide to upgrade from 4.1.1 or 4.1.2.R02/R03.
Upgrading from OmniVista 2500 NMS 3.5.7
Follow the steps below to upgrade from OmniVista 2500 NMS 3.5.7 to 4.2.1.R01.
1. On the existing installation of OmniVista 2500 NMS (3.5.7), change “admin” user's password to “switch”.
2. On the existing installation of OmniVista 2500 NMS, open the Server Backup Application and perform a backup. See the OmniVista 2500 NMS 3.5.7 Server Backup Application On-Line
Help for more information.
3. Perform a fresh deployment of OV 2500 NMS-E 4.2.1.R01 ( VMware ,
Note: If you have not shutdown the 3.5.7 installation, make sure that it is shutdown after performing the backup so there is no IP address conflict between the 3.5.7 installation and the 4.2.1.R01 installation.
4. Use an SFTP client to copy backup file generated in Step 2 above, to a fresh installation of
OV 2500 NMS-E 4.2.1.R01. Make sure the destination directory is “backups”.
•
SFTP User: cliadmin
• SFTP Password: <password when deploying VA>
• SFTP Port: 22
5. Login to OV 2500 NMS-E 4.2.1.R01 VA machine using cliadmin account.
Note: It is recommended that you take a VM Snapshot prior to the upgrade. (In vSphere you right-click on the VM and select Snapshot - Take Snapshot.)
6. Enter 4 and press Enter to choose the Upgrade/Restore VA option.
20
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
7. Enter 6 and press Enter to choose the Restore OV2500 NMS Data.
8. The list of backup files will display, choose a Backup File by selecting the number (e.g., 1) in the list and pressing Enter.
9. Press y at the confirmation prompt, and press Enter. Then press y at the warning confirmation prompt and press Enter.
10. Wait for all OV 2500 NMS-E 4.2.1.R01 Services start up. Use the “Display Status of All
Running Services” option of the Run Watchdog command in the Virtual Appliance Menu to view the status of services.
Note: After all Services start up, it is recommended that you take a VM snapshot. (In vSphere you right-click on the VM and select Snapshot - Take Snapshot.)
11. Once all services have started, enter https://OVServerIPaddress in a supported browser to launch OV 2500 NMS-E 4.2.1.R01.
12. After logging into OV 2500 NMS-E 4.2.1.R01, you will be required to enter the OV 2500
NMS-E 4.2.1.R01 Production License Key. Enter the Production License Key. For procedures
on generating an Evaluation License, see Appendix A .
13. You must now restart all services. Go to the Watchdog Screen in the OmniVista GUI
( Administrator - Control Panel – Watchdog) and click on the Restart All button to restart all services again. When all services restart, you will be able to log into OV 2500 NMS-E
4.2.1.R01.
21
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Note: It is recommended that you check the OmniVista Software Repository for any new patches/updates. On The Virtual Appliance Menu, select 4 – Upgrade/Restore VA, then select 2 – 4.2.1.R01 (Current Release).
Note: It may take up to one (1) hour for OV 2500 NMS-E 4.2.1.R01 to populate network data (e.g., VLANs information, Unified Access information).
Upgrading from OmniVista 2500 NMS 4.1.2.R03
The procedures below detail upgrading from a 4.1.2.R03 VA installation
or a 4.1.2.R03 Non-VA installation.
Upgrading from a VA Installation
Follow the steps below to upgrade from a VA installation of OmniVista 4.1.2.R03 to OV 2500
NMS-E 4.2.1.R01.
Important Note: By default, OV 2500 NMS-E 4.2.1.R01 is partitioned as follows:
HDD1:50GB and HDD2:256GB. If you are managing more than 500 devices it is recommended that you increase to provisioned hard disk using the Configure Network Size option in the Configure The Virtual Appliance Menu (Configure The Virtual Appliance Menu -
Configure Network Size (10) - Configure Data Partition (4)).
1. From OV 4.1.2.R03 VA system, open a Console on the VM to access the Virtual Appliance
Menu. Type 4 and press Enter to choose the Backup/Restore OmniVista 2500 NMS option.
2. Enter 1 and press Enter to choose Backup OmniVista 2500 NMS option from the
Backup/Restore OmniVista 2500 NMS menu.
3. Enter the Backup’s base name (default is “ov2500nms”), then press Enter. If no base name is specified, “ov2500nms” will be used as the default base name. The backup will begin.
22
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
After backup is finished, the output filename will be displayed: <base name>_<yyyy-MM-dd--
HH-mm>.bk (e.g., ov2500nms_2016-01-20- -16-15.bk). A backup includes OV2500 data backup (.osb), MongoDB data backup (.mgb) and license data backup (.lic).
4. FTP to the OmniVista 4.1.2.R03 Server to retrieve the backup file created above
(admin/admin, Port 8888).
5. Perform a fresh deployment of OV 2500 NMS-E 4.2.1.R01 ( VMware ,
6. Use an SFTP client to copy the backup file generated in Step 3 above, to the fresh installation of OV 2500 NMS-E 4.2.1.R01 VA. Make sure the destination directory is “backups”.
• SFTP User: cliadmin
•
SFTP Password: <password when deploying VA>
• SFTP Port: 22
The default Mongo Database passwords are the same for 4.1.2.R03 and 4.2.1.R01. If you are upgrading from 4.1.2.R03 and did not change the default Mongo password, steps 7 through 11 below are not required unless:
• You changed the default password in 4.1.2.R03, or
• You upgraded from 4.1.2.R01/R02 to R03 and are upgrading to 4.2.1.R01.
7. After the installation is completed, open a Console on the VA, and from the Virtual Appliance
Menu, enter 5 and press Enter to choose the Change Password option.
8. Enter 3 and press Enter to choose the Change Mongodb Database Password option.
23
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
9. Enter option 1 and enter the “old” Mongo Administrator password (this is the current
OmniVista 4.2.1.R01 password -ale2@!*passwd), then enter the “new” Mongo Administrator password (this is the 4.1.2.R03 Administrator password). Now Enter option 2 & enter old
Ngnms application user password (this is the current OmniVista 4.2.1.R01 password ale2@!*dbpasswd), then enter new Ngnms application password (this is the 4.1.2.R03 Ngnms app password). Remember, you are changing the OmniVista 4.2.1 passwords to the 4.1.2.R03 passwords.
10. After completing the password change, use the Run Watchdog command in the Virtual
Appliance Menu to restart all services.
11. Enter 3 and press Enter to choose the Run Watchdog Command option. At the prompt, enter 5 and press Enter to choose Restart All Services option. Wait until all services have restarted, then go to Step 12.
Note: It is recommended that you take a VM Snapshot prior to the upgrade (Step 12). (In vSphere you right-click on the VM and select Snapshot - Take Snapshot.)
24
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
12. From the Virtual Appliance Menu, enter 4, then press Enter to select the Upgrade/Restore
VA option.
13. Enter 6 and press Enter to choose Restore OmniVista 2500 NMS Data option from the
Upgrade VA menu.
14. Choose a Backup File by selecting the number (e.g., 1) in the list and pressing Enter.
15. Press y at the confirmation prompt, and press Enter. Then press y at the warning confirmation prompt and press Enter.
25
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
16. Wait for all OV 2500 NMS-E 4.2.1.R01 Services start up. Use the “Display Status of All
Running Services” option of the Run Watchdog command in the Virtual Appliance Menu to view the status of services.
Note: After all Services start up, it is recommended that you take a VM snapshot. (In vSphere you right-click on the VM and select Snapshot - Take Snapshot.)
17. Once all services have started, enter https://OVServerIPaddress in a supported browser to launch OV 2500 NMS-E 4.2.1.R01.
18. After logging into OV 2500 NMS-E 4.2.1.R01, you will be required to enter the OV 2500
NMS-E 4.2.1.R01 Production License Key. Enter the Production License Key (you may also use your existing 4.1.x Production License Key). For procedures on generating an Evaluation
19. You must now restart all services. Go to the Watchdog Screen in the OmniVista GUI
( Administrator - Control Panel – Watchdog) and click on the Restart All button to restart all services again. When all services restart, you will be able to log into OV 2500 NMS-E
4.2.1.R01.
Note: It is recommended that you check the OmniVista Software Repository for any new patches/updates. On The Virtual Appliance Menu, select 4 – Upgrade/Restore VA, then select 2 – 4.2.1.R01 (Current Release).
Note: It may take up to one (1) hour for OV 2500 NMS-E 4.2.1.R01 to populate network data (e.g., VLANs information, Unified Access information).
Upgrading from a Non-VA Installation
Follow the steps below to upgrade from a non-VA installation of 4.1.2.R03 (Windows/Linux) to
OV 2500 NMS-E 4.2.1.R01.
1. On the existing installation of OmniVista 2500 NMS (OmniVista 4.1.2.R03), change “admin” user's password to “switch”.
2. Perform a backup of the OmniVista 4.1.2.R03 installation and FTP it to a safe place outside
of the server. Detailed backup procedures are provided below .
3. Perform a fresh deployment of OV 2500 NMS-E 4.2.1.R01 (
4. Use an SFTP client to copy the backup file generated in Step 2 above, to the fresh installation of OmniVista 2500 NMS VA. Make sure the destination directory is “backups”.
•
SFTP User: cliadmin
• SFTP Password: <password when deploying VA>
•
SFTP Port: 22
The default Mongo Database passwords are the same in 4.1.2.R03 and 4.2.1.R01. If you are upgrading from 4.1.2.R03 and did not change the default Mongo password, steps
5 through 9 below are
not required unless:
• You changed the default password in 4.1.2.R03, or
• You upgraded from 4.1.2.R01/R02 to R03 and are upgrading to 4.2.1.R01.
5. After the installation is completed, open a Console on the VA, and from the Virtual Appliance
Menu, enter
5 and press Enter to choose the Change Password option.
26
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
6. Enter 3 and press Enter to choose the Change Mongodb Database Password option.
7. Enter option 1 and enter the “old” Mongo Administrator password (this is the current
OmniVista 4.2.1.R01 password -ale2@!*passwd), then enter the “new” Mongo Administrator password (this is the 4.1.2.R03 Administrator password). Now Enter option 2 & enter old
Ngnms application user password (this is the current OmniVista 4.2.1.R01 password ale2@!*dbpasswd), then enter new Ngnms application password (this is the 4.1.2.R03 Ngnms app password). Remember, you are changing the OmniVista 4.2.1 passwords to the 4.1.2.R03 passwords.
8. After completing the password change, use the Run Watchdog command in the Virtual
Appliance Menu to restart all services.
27
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
9. Enter 3 and press Enter to choose the Run Watchdog Command option. At the prompt, enter 5 and press Enter to choose Restart All Services option. Wait until all services have restarted, then go to Step 10.
Note: It is recommended that you take a VM Snapshot prior to the upgrade (Step 10). (In vSphere you right-click on the VM and select Snapshot - Take Snapshot.)
10. From the Virtual Appliance Menu, enter 4, then press Enter to select the Upgrade/Restore
VA option.
11. Enter 6 and press Enter to choose Restore OmniVista 2500 NMS Data option from the
Upgrade VA menu.
28
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
12. Choose a Backup File by selecting the number (e.g., 1) in the list and pressing Enter.
13. Press y at the confirmation prompt, and press Enter. Then press y at the warning confirmation prompt and press Enter.
14. Wait for all OV 2500 NMS-E 4.2.1.R01 Services start up. Use the “Display Status of All
Running Services” option of the Run Watchdog command in the Virtual Appliance Menu to view the status of services.
Note: After all Services start up, it is recommended that you take a VM snapshot. (In vSphere you right-click on the VM and select Snapshot - Take Snapshot.)
15. Once all services have started, enter https://OVServerIPaddress in a supported browser to launch OV 2500 NMS-E 4.2.1.R01.
16. After logging into OV 2500 NMS-E 4.2.1.R01, you will be required to enter the OV 2500
NMS-E 4.2.1.R01 Production License Key. Enter the Production License Key (you may also use your existing 4.1.x Production License Key). For procedures on generating an Evaluation
17. You must now restart all services. Go to the Watchdog Screen in the OmniVista GUI
( Administrator - Control Panel – Watchdog) and click on the Restart All button to restart all services again. When all services restart, you will be able to log into OV 2500 NMS-E
4.2.1.R01.
Note: It is recommended that you check the OmniVista Software Repository for any new patches/updates. On The Virtual Appliance Menu, select 4 – Upgrade/Restore VA, then select
2 – 4.2.1.R01 (Current Release).
Note: It may take up to one (1) hour for OV 2500 NMS-E 4.2.1.R01 to populate network data (e.g., VLANs information, Unified Access information).
Backup Procedures for OmniVista 2500 NMS 4.1.2.R03 Non-VA (Windows/Linux)
Follow the steps below to backup OmniVista 2500 NMS 4.1.2.R03 on Windows/Linux installations.
29
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
1. Go to the scripts directory of the OmniVista 2500 NMS installation folder and execute
“backup-ngnms.bat” (for Windows) or “backup-ngnms.sh” (for Linux).
You must run it with
Administrator privilege.
2. To perform an immediate backup, enter n, then press Enter at the "Schedule" prompt.
3. Enter the path of the Backup Directory (default is “C:\backup” on Windows and
“/root/Desktop/defaultbackupdir” on Linux), then press Enter.
4. Enter the Backup’s base name (default is “ov2500nms”), then press Enter.
A “Stopping services” message will appear as the services are automatically stopped. This may take some time to complete. When the services have been stopped, the backup will start. When the process is complete, a confirmation message will appear and the backup file will be stored in the configured backup directory under the name: <base name>_<yyyy-MM-dd--HH-mm>.bk.
Note: Old Backup Files are not automatically purged. Monitor and maintain the Backup
Directory to optimize disk space.
Using the Virtual Appliance Menu
To access the Main Virtual Appliance Menu for a VM, launch the Console. (In vCenter, this can be done by right-clicking on the VM in the Navigation Tree and selecting
Open Console.) The login prompt is displayed.
Note: You can also access the Virtual Appliance Menu by connecting via SSH using port
2222, user cliadmin, and password set when deploying VA (e.g., ssh [email protected] –p 2222).
1. Enter the login (cliadmin) and press Enter.
30
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
2. Enter the password and press Enter. The password is the one you created when you first
launched the VM Console at the beginning of the installation process. The Virtual Appliance
Menu is displayed.
The Virtual Appliance Menu provides the following options:
•
•
2 - Configure the Virtual Appliance
•
•
•
•
•
•
•
•
For information on these menu options, refer to the sections below.
Help
Enter 1 and press Enter to bring up help for the Virtual Appliance Menu.
Configure the Virtual Appliance
The “Configure the Virtual Appliance” menu provides the following options:
•
•
2 - Display Current Configuration
•
•
•
•
•
•
•
31
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
•
•
11 - Configure Keyboard Layout
•
•
•
•
•
Help
Enter 1 and press Enter to bring up help for the Configure The Virtual Appliance Menu.
Display Current Configuration
Enter 2 and press Enter to display the current VA configuration. Press Enter to return to the
Configure The Virtual Appliance Menu.
32
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Configure IP
1. If you want to re-configure the System IP, enter 3 and press Enter.
2. Enter an IPv4 IP address and subnet mask.
3. Enter y at the confirmation prompt and press Enter to confirm the settings. Press Enter to return to the Configure The Virtual Appliance Menu.
Configure Ports
1. Enter 4 and press Enter to configure System Ports.
33
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
2. At the prompt, enter an HTTP value and press Enter. Enter an HTTPS value and press
Enter.
• HTTP Port (Valid range: 1024 to 65535, Default = 80))
• HTTPS Port (Valid range: 1024 to 65535, Default = 443)
Note: You can press Enter to accept default values. New port values must be unique
(i.e., they must differ from any previously-configured ports).
3. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
After entering values and confirming, you must restart all services for the changes to take effect.
Use the Restart All Services option in the Run Watchdog command in the Virtual Appliance
Menu.
Configure Default Gateway
1. Enter 5 and press Enter to configure default gateway settings.
2. Enter an IPv4 default gateway.
3. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
34
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Configure Hostname
1. The default Hostname is omnivista. If you want to change the default Hostname, enter 6 and press Enter.
2. Enter a hostname.
3. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
Configure DNS Server
1. Enter 7 to specify whether the VM will use a DNS Server.
2. If the VM will use a DNS server, enter y, then press Enter. Enter the IPv4 address for Server
1 and Server 2, if applicable.
Note: If n (No) is selected, all DNS Servers will be disabled.
3. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
Configure Timezone
1. Enter 8 and press Enter to begin setting up the time zone; then confirm by typing y at the prompt.
2. Select the region for the VM by entering its corresponding numeric value (e.g., 10).
3. Select a country within the region by entering its corresponding numeric value (e.g., 25).
35
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
4. If prompted, enter the numeric value for the specific time zone within the country (e.g., 21).
5. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
Configure Route
1. If you want to add a static route from the VM to another network enter 9 and press Enter.
2. Add an IPv4 route by entering 3 at the command prompt.
36
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
3. Enter the subnet, netmask and gateway.
4. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
Configure Network Size
1. At the Main Menu prompt, enter 10 and press Enter to begin configuring a Network Size.
2. You can re-configure OV 2500 NMS-E 4.2.1.R01 memory settings by selecting option 2.
3. Configure Swap file by selecting option 3.
4. Configure Data Partition by selecting option 4.
By default, OV 2500 NMS-E 4.2.1.R01 is partitioned as follows: HDD1:50GB and HDD2:256GB.
If you are managing more than 500 devices it is recommended that you increase to provisioned hard disk using the Configure Network Size option in the Configure The Virtual Appliance Menu
(Configure The Virtual Appliance Menu - Configure Network Size (10) - Configure Data Partition
(4)).
Configure Keyboard Layout
1. Enter 11 and press Enter to specify a keyboard layout.
2. Press Enter to see the list of keyboard layouts.
3. Enter q and press Enter to quit the view mode. At the prompt, enter a keyboard layout then press Enter. Press y at the confirmation prompt.
The table below lists all supported keyboard layouts.
37
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
amiga-de atari-us sg-latin1 de-latin1-nodeadkeys cz-us-qwertz sk-prog-qwertz wangbe azerty fr-latin0 backspace euro2 unicode ttwin_cplk-UTF-8 ruwin_alt-KOI8-R nl2 by pt-latin9 ruwin_cplk-UTF-8 ruwin_ctrl-CP1251 mk-cp1251 se-fi-lat6 sk-prog-qwerty ru3 ro_std it-ibm emacs tralt cf ttwin_ctrl-UTF-8 cz-qwerty ruwin_ctrl-KOI8-R pl2 ru-cp1251 lt.l4 ru_win br-abnt2 is-latin1 et-nodeadkeys ruwin_ct_sh-UTF-8 lt.baltic bashkir
ANSI-dvorak mac-fr_CH-latin1 mac-es mac-fi-latin1 amiga-us atari-de hu fr_CH-latin1 sg-latin1-lk450 sk-qwertz wangbe2 fr fr-latin1 ctrl euro se-latin1 pt-latin1 no-latin1 mk uk sk-qwerty br-abnt ua ruwin_cplk-KOI8-R ruwin_ctrl-UTF-8 trq us ttwin_alt-UTF-8 il fi-latin1 defkeymap hu101 cz-lat2-prog ruwin_cplk-CP1251 ru-ms sv-latin1 ruwin_alt-CP1251 ua-utf emacs2 es is-latin1-us jp106 pt tr_q-latin5 no-dvorak dvorak-l mac-us mac-pl mac-template
38
atari-uk-falcon pt-olpc sg de-latin1 croat de fr-latin9 fr-pc tr_f-latin5 applkey euro1 cz-cp1250 ru4 pl1 es-cp850 pl se-lat6 la-latin1 dk kyrgyz ro fi-latin9 ruwin_ct_sh-KOI8-R trf by-cp1251 pc110 bg_pho-utf8 bg_pho-cp1251 br-latin1-us ttwin_ct_sh-UTF-8 no br-latin1-abnt2 ru bywin-cp1251 dk-latin1 pl4 il-phonetic lt se-fi-ir209 pl3 dvorak-r mac-euro mac-de-latin1 mac-se mac-dk-latin1 atari-se es-olpc fr_CH de_CH-latin1 slovene cz fr-old be-latin1 trf-fgGIod keypad windowkeys il-heb ruwin_ct_sh-CP1251 cz-lat2 bg-cp855 ua-cp1251 bg_bds-cp1251 sr-cy ru-yawerty defkeymap_V1.0 fi gr nl ruwin_alt-UTF-8 it bg_bds-utf8 ua-ws se-ir209 mk-utf ru1 us-acentos et it2 bg-cp1251 kazakh mk0 fi-old ru2 gr-pc ua-utf-ws dvorak mac-euro2 mac-be mac-dvorak mac-de-latin1-
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
mac-fr mac-de_CH sunt5-de-latin1 sunkeymap mac-pt-latin1 sunt4-no-latin1 sunt5-us-cz sunt4-es mac-uk sunt5-cz-us sunt5-es sunt5-ru sun-pl sunt5-fr-latin1 sunt5-fi-latin1
4. Press Enter to return to the Configure The Virtual Appliance Menu. nodeadkeys mac-it sundvorak sunt4-fi-latin1 sunt5-uk sun-pl-altgraph
Update SSL Certificate
To update the SSL Certificate, you must first generate a *.crt and *.key file and use an SFTP
Client to upload the files to the VA. Make sure the destination directory is “keys”.
• SFTP User: cliadmin
• SFTP Password: <password when deploying VA>
•
SFTP Port: 22
1. Enter 12 and press Enter.
2. Choose a file certificate file (.crt) and enter y and Enter. Choose a private key file (.key) and enter y and Enter. The Tomcat service will be restarted.
Configure NTP Client
1. Enter 13 and press Enter to configure an NTP Server.
2. Enter 2 and press Enter.
3. Enter the IP address of the NTP Server and press Enter.
39
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
4. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu. You can enable the server when you create it, or enabled it at a later time using option 5.
Configure Proxy
OV 2500 NMS-E 4.2.1.R01 makes an HTTPS connection to the OmniVista 2500 NMS External
Repository for upgrade software, Application Visibility Signature Files, and ProActive Lifecycle
Management. If the OV 2500 NMS-E 4.2.1.R01 Server has a direct connection to the Internet, a
Proxy is not required. Otherwise, a Proxy should be configured to enable OmniVista to connect to the OmniVista 2500 NMS External Repository.
1. Enter 14 and press Enter to specify whether the VM will use a Proxy Server. Enter 1 and press Enter to configure a Proxy Server.
2. If the VM will use a proxy server, enter the Proxy Server IP address, along with the port (e.g.,
8080).
Note: If n (No) is selected, all proxy servers will be disabled.
3. Enter y and press Enter to confirm the settings. Press Enter to return to the Configure The
Virtual Appliance Menu.
Import JRE CA Certificate
To import a JRE CA Certificate (e.g., *.pem), you must first use an SFTP Client to upload the files to the VA. Make sure the destination directory is “keys”.
• SFTP User: cliadmin
•
SFTP Password: <password when deploying VA>
• SFTP Port: 22
1. Enter 15 and press Enter to import a Private CA Certificate.
40
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
2. Enter the number for the certificate you want to import (e.g., 1) and press Enter.
3. Enter an alias for the certificate and press Enter. The certificate will be imported.
4. Enter y at the confirmation prompt and press Enter. Press Enter to return to the Configure
The Virtual Appliance Menu.
Exit
Enter 0 and press Enter to return to the Virtual Appliance Menu.
41
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Run Watchdog Command
The Watchdog command set is used to start and stop managed services used by OV 2500
NMS-E 4.2.1.R01. To access the Watchdog CLI Command Menu, enter 3 at the command prompt. The following displays:
Select number matching with action you want to perform and press
Enter.
Upgrade/Restore VA
To view information about the current version of the OV 2500 NMS-E 4.2.1.R01 VA, and to update the VM, enter 4 at the command prompt. Menu options include:
• Option 1: Get Help
• Option 2: Update to new OV build or release
• Option 3: Select the Repository which stores OV build/release
• Option 4: Configure Custom Repository
• Option 5: Check available updates
• Option 6: Restore old OV release (OV 3.5.7 or OV 4.1.2 R03)
• Option 0: Exit menu
1. Enter 2 to check current version:
2. Enter 5 to check available updates, then enter 2 to check immediately.
42
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
3. Enter 6 to Restore OV 2500 Data.
The sections below detail the backup /
restore steps for virtual appliance installations. Open a
Console on the VM to access the Virtual Appliance Menu. Enter 4 and press Enter to choose the Update/Restore VA option.
Note: To display backup file, you have to access the Virtual Appliance for sending backup files via SFTP:
• SFTP User: cliadmin
• SFTP Password: <password when deploying VA>
• SFTP Port: 22
Change Password
You can change the Virtual Appliance cliadmin password and/or mongo database password.
To change the VA cliadmin password, enter
2, then press Enter. At the prompts, enter the current password, then enter the new password.
To change the mongo database password, enter
3, then press Enter. You have two options when changing the mongo database password.
43
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Enter
1 to change the mongo administrator password. Enter 2 to change the application user password. At the prompts, enter the current password, then enter the new password.
Logging
You can view OV 2500 NMS-E 4.2.1.R01 Logs using the “Logging” option. Enter 6, then press
Enter.
Power Off
Before powering off the VM, you must stop all OV 2500 NMS-E 4.2.1.R01services using the
Stop All Services option in the Run Watchdog Command. After all the services are stopped, enter 7 at the command line to power off the VM. Confirm power off by entering y. The power off may take several minutes to complete.
Note: OV 2500 NMS-E 4.2.1.R01 functions stop running following power off. The VM must be powered back on via the VMware client software and you must log back into the VM via the console.
Reboot
Before rebooting the VM, you must stop all OV 2500 NMS-E 4.2.1.R01 services using the
Stop
All Services option in the Run Watchdog Command. After all services are stopped, enter 8 at the command line to reboot the VM. Confirm reboot by entering y. The reboot may take several minutes to complete. When rebooted, you will be prompted to log in through the cliadmin user and password prompts. Note that OV 2500 NMS-E 4.2.1.R01 functions continue following reboot.
Advanced Mode
Advanced Mode enables you to use read-only UNIX commands for troubleshooting. Enter
9, then press
Enter to bring up the CLI prompt. Enter exit and press Enter to return to the Virtual
Appliance Menu. The following commands are supported:
• /usr/bin/touch
• /usr/bin/mktemp
• /usr/bin/dig
• /usr/bin/cat
• /usr/bin/nslookup
44
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
• /usr/bin/which
• /usr/bin/less
• /usr/bin/tail
• /usr/bin/vi
• /usr/bin/tracepath
• /usr/bin/tty
• /usr/bin/systemctl
• /usr/bin/grep
• /usr/bin/egrep
• /usr/bin/fgrep
• /usr/bin/dirname
• /usr/bin/readlink
• /usr/bin/locale
• /usr/bin/ping
• /usr/bin/traceroute
•
/usr/bin/netstat
• /usr/bin/id
• /usr/bin/ls
• /usr/bin/mkdir
• /usr/sbin/ifconfig
• /usr/sbin/route
• /usr/sbin/blkid
• /usr/sbin/sshd-keygen
• /usr/sbin/consoletype
• /usr/sbin/ntpdate
• /usr/sbin/ntpq
• /usr/bin/ntpstat
• /usr/bin/abrt-cli
• /usr/sbin/init
• /usr/sbin/tcpdump
• /bin/mountpoint
Log Out
To log out of the VM and return to the cliadmin login prompt, enter 0 at the command line.
Confirm logout by entering y. Note that OV 2500 NMS-E 4.2.1.R01 functions continue following logout.
45
Part No. 060444-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
Appendix A – Generating an Evaluation License
An Evaluation License provides full OV 2500 NMS-E 4.2.1.R01feature functionality, but is valid only for 60 Days (starting from the date the license is generated). There are two (2) Evaluation
Licenses available. Both licenses can be generated at once or in sequence, depending on the configuration.
• NM (Node Management) – Device Management for Alcatel-Lucent Enterprise and supported Third-Party Devices. Licenses are available for 10 or 20 Nodes.
• VMM (Virtual Machine Manager) – (Optional) Features related to Virtual Machine
Manager. Licenses are only available in a single quantity – 200 virtual machines.
Note: A Node Management License is required to use the optional VMM License. Also, licenses cannot be cumulated at initial request or later on. This is different than a regular
Production licenses.
Follow the steps below to generate an Evaluation License Key.
1. Go to https://service.esd.alcatel-lucent.com/portal/page/portal/EService/LicenseGeneration .
2. Click on OmniVista 2500 NMS/VMM Releases 4.1.x & 4.2.1.
A-1
Part No. 033131-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
3. Enter the Customer ID and Order Number, then click Next.
• Customer ID – 99999
•
Order Number – evaluation
A-2
Part No. 033131-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
4. Select the License Type and the number of devices to be managed from the drop-down menu
(e.g., Evaluation NM License for 50 devices – EVAL-NM-EX-50-N_1), enter the Passcode
( alcatel), and click Submit Entry.
5. Complete all of the required fields on the License Registration Form and click Submit. A download prompt (shown below) will appear.
6. Click OK at the confirmation prompt to download the license key into Notepad. Notepad will open with the License Key displayed.
A-3
Part No. 033131-10, Rev. B
OmniVista 2500 NMS Enterprise 4.2.1.R01 Installation Guide
A confirmation e-mail will automatically be sent to the address entered on the Registration form that will include the License Key.
A-4
Part No. 033131-10, Rev. B
تنزيل
تم تحديث الرابط العام
رابط عام للمستند
إعلان