1) Release Summary...1 2) Platforms Supported...3 3) Installation Notes...3 4) Important Notes and Known Limitations...5 5) Uninstallation Notes...

Transcription

1 Contents 1) Release Summary...1 2) Platforms Supported...3 3) Installation Notes...3 4) Important Notes and Known Limitations...5 5) Uninstallation Notes...6 1) Release Summary ONMS Maintenance Release addresses the following issues: Synopsis CR ID Description subnet links links not removed AP7215 links links not shown ERS , trapreceiver registration ERS8600s, topology discovery ERS8610co Omniview Q Q Q Q Q Q Q Autodiscovery using seed discovery discovered Access Points properly but a link from the subnet appeared for every AP in the network. In a large network, the network map became very cluttered. If the interface index of the transit link on one Access Point was modified, but the neighboring AP retained its previous interface number, rediscovery discovered a new link but the previous link was not removed. Discovery did not discover links of the AP7215 for the Wireless Mesh Network topology view. ONMS topology view did not show links between the AP@NAP and the NAP-R. Given an ERS8600 running version but without SNMPv3 configured, trapreg tried to register the ONMS server as trapreceiver but the operation failed. This was caused because the trapreceiver table OID changed in version of the ERS8600 software. Topology discovery sometimes stopped running with ERS8600s. Omniview would not run on an ERS8610co with 3.5.x agent version. ESU links not displayed Q Links between ESUs in rings were not displayed after discovery. ESU1850, Omniview Q Omniview stopped running when launched on an crashed ESU1850 v.210. ESU1800 trap registration Q Trap registration was unsuccessful on Windows and Solaris for ESU1800 v of 7

2 Synopsis CR ID Description BayRS router links not discovered Router failed but stayed green in Infocenter Baystack switch fan New device not added to discovery database Expanded View refresh times Transport Domain Continuity lock up tnsnames.ora file overwritten Resync of Device Inventory Viewer failed Q Q Q Q Q Q Q Q Links between BayRS routers and layer 2 devices were not discovered properly. Given a router with a default route that was directly upstream, when the router went down, the ICMP reply from the router and every device after the router returned "TTL expired in transit". Superping did not recognize this response as indication that the device was down, with the result that the device stayed green in the Infocenter map. When a trap was received from a baystack switch indicating that a fan had stopped working, the ONMS recorded the event as expected. However, when the same baystack sent the same trap type, indicating that the status had returned to normal, the second event was not correlated with the first. The first event remained active, and displayed as an unresolved fault condition. A new device did not get added to the database during subnet rediscovery using routerless discovery. The device was discovered when discovery was done from a seed. When using Expanded View, when the refresh time was changed to invalid values, the values appeared to be accepted. Also, when the refresh time was changed to values that were less than the actual refresh time, it gave the appearance that the application was not responding. The Transport Domain Continuity application stopped running when the refresh rate was changed from manual to 5 seconds. When ONMS was installed on a system with an existing oracle database, the tnsnames.ora file was overwritten. Instead, the file should have been backed up and the original appended with the nmsdb entry. After all assets were cleared from the Device Inventory Viewer, the crdivdb command was run as per the procedure in the documentation, and the optivity daemons were stopped and restarted. A discovery was then run but it was not possible to resync the Device Inventory Viewer because no seeds showed up to sync with. Subnets not found Q When a routerless discovery was performed on a clean smop database, seed discoveries that were done later did not find subnets. 2 of 7

3 Synopsis CR ID Description OmniView line graphing Q When data was highlighted in Omniview and line graphing was selected, the line graphing chart popped up but there were no lines in it because only one datapoint was being stored in memory. 2) Platforms Supported Solaris 2.8 3) Installation Notes ONMS Maintenance Release applies to both "Client-Server" and "Client-Only" installations of ONMS 10.3 and Maintenance Release Disk space requirements for Solaris under $LNMSHOME: Client-Server: 80 MB Client-Only: 7 MB Note 1: You cannot install ONMS 10.3 server plug-ins (for example the VOIP or VPLS plug-ins) after installing Maintenance Release Nortel recommends that you install all available server plug-ins before you install Maintenance Release You cannot install ONMS and the ONMS North Bound Interface (NBI). The NBI can only be installed with ONMS Note 2: The installation and uninstallation scripts for ONMS create the following log files in the <directory>/nmsadm/log directory: onms1032_preinstall.log onms1032_install.log onms1032_postinstall.log onms1032_preremove.log onms1032_uninstall.log onms1032_postremove.log To install ONMS Maintenance Release : 3.1) Download the ONMS Maintenance Release from the Nortel web site and copy the files to a file-system on the target ONMS 10.3 (10.3.1) machine or a server with network share capability. 3 of 7

4 3.2) Uncompress the ONMS Maintenance Release files using the following command: zcat <ONMS1032-Solaris.tar.Z> tar xvf - 3.3) Stop all Optivity NMS server processes as well as client applications. Ensure that all topology processes ('toprt', 'topst', 'topdt','protur', 'protmr', 'protfr') and any other Optivity processes are stopped. Use AutoTopology Manager (topui) to stop the topology processes. Run "ps -ef grep lnms" to check for any Optivity processes that are running still. If any Optivity process is running still, run "kill <PID>" to stop all running Optivity process. 3.4) If ONMS is installed with platform software such as NetView or HP OpenView, stop all platform daemons. 3.5) Login in as user 'root'. If root is not configured to run optivity then run the following command: Bourne, k-shell:. /usr/lnms/bin/opt_kshrc C-shell: source /usr/lnms/bin/opt_cshrc 3.6) Change (cd) to the following directory: <directory>/hpux/cdrom/p1032/ Where <directory> is the directory to which you downloaded the maintenance release archive file. 3.7) Use the following command to run the script install program:./install Note: As the installation script runs, the following error messages may appear in the console window and also in the install log file: * Unable to connect to the Web server * ORA-00001: Unique constraint (APPCONTROLDB.UNQ_VIEW_SPEC) violated * Error while trying get Mib from MIBDB for esuagentcommunitylevel * SQLPLUS : SP2-0306: Invalid option. * Error in ctemplatedb :: vsetpeers - mib object esuagentcommunitylevel is not in MIBDB database. These messages can be ignored. 3.8) If ONMS is installed with platform software such as NetView or HP OpenView, restart all platform daemons as required. 4 of 7

5 3.9) Start all Optivity daemons using the "optivity_apps start" command. 3.10) Run the command "optstatus -fe" to ensure all Optivity daemons are running. 4) Important Notes and Known Limitations 4.1) If Maintenance Release is installed over Maintenance Release and you want to uninstall Maintenance Release , you must first uninstall the Maintenance Release ) install and uninstall scripts may stop running and exit with the following error message: "Some Optivity NMS processes are still running. Please stop all the applications and run install/uninstall again." Use the following command sequence to identify the Optivity NMS processes that are running and kill them: # ps -ef grep LNMS # kill -9 <pid> 4.3) If you delete any Optivity NMS databases (smop, fault, AppControlDB, evomni, mibdb or vogon) using "rm_appdb", or if you set the databases to factory defaults using the DB Admin Tool, then you MUST stop all Optivity NMS daemons first. Use the "optivity_apps stop" command to stop the daemons. Restart all Optivity NMS daemons using "optivity_apps start". 4.4) To reset a database to its factory defaults: a. Uninstall the Maintenance Release using either "uninstall1032" or "install -u" script commands in %LNMSHOME%/p1032. b. Insert the Optivity NMS Client/Server CD in the CD drive. c. Use the ONMS Database Admin Tool to reset the database. Choose Tools > Reset database d. Reinstall Maintenance Release according to the instructions in Section 3 of this document. 5 of 7

6 4.5) The following are known limitations: NAP-Router duplicate routers, Q If SNMP is enabled in the NAP-Router, duplicate routers show up after discovery. ESU1850 duplicate links, Q If OE Rings contain ESU1850 devices, duplicate links may be discovered. This limitation will be addressed in an upcoming release. ERS8600 ver boots with default configuration, Q Given an ERS8600 running version with SNMPv3 configured, when the ONMS was set as trapreceiver, the snmptargetaddrtimeout and snmptargetaddrretrycount values were set to 0. These zeros are invalid for the CLI configuring commands. As a result, when the ERS8600 booted, it could not interpret these values and so booted with the default configuration. This problem has been resolved in ONMS , but an upgrade to agent code v3.7.3 on the ERS8600 is required for complete resolution. (Refer also to Q , below.) ERS8600 ver 3.7.3, trapregistration resets values to 0, Q Given an ERS8600 running version with SNMPv3 configured, trapregistration set the snmptargetaddrtimeout and snmptargetaddrretrycount values to zero. These values were changed but when trapregistration queried the device, it reset them to zero. This problem has been resolved on ONMS , but an upgrade to agent code v3.7.3 on the ERS8600 is required for complete resolution. (Refer also to Q , above.) 5) Uninstallation Notes This procedure uninstalls Maintenance Release and the system reverts to the previouslyinstalled version of Optivity NMS (10.3 or ). Note: ONMS Maintenance Releases must be uninstalled prior to the uninstallation of the Optivity NMS To uninstall Maintenance Release : 5.1) Login in as user 'root'. 6 of 7

7 If root is not configured to run optivity then run the following command: Bourne, k-shell:. /usr/lnms/bin/opt_kshrc C-shell: source /usr/lnms/bin/opt_cshrc 5.2) Stop all ONMS applications. 5.3) Stop all NMS platform daemons (in a platform system only). 5.4) Change directory (cd) to $LNMSHOME/p ) Run the script "uninstall1032" or "install -u". 5.6) Restart all NMS platform daemons (in a platform system only). 5.7) Start all Optivity daemons, using the "optivity_apps start" command. 5.8) Run the command "optstatus -fe" to ensure all Optivity daemons are running Nortel Networks, Inc. All rights reserved. 7 of 7