Maintenance Release is an accumulative maintenance release. That is, all CRs fixed in previous releases are included.

Transcription

1 Contents 1) Release Summary...1 2) Platforms Supported...5 3) Installation Notes...5 4) Important Notes and Known Limitations...7 5) Uninstallation Notes ) Release Summary Maintenance Release is an accumulative maintenance release. That is, all CRs fixed in previous releases are included. ONMS Maintenance Release addresses the following issues: Tool and Topic CR ID # Description Manager and chains Manager and DHring Manager and ERS 5510 Manager and ERS 8600 Manager and ESU UNIs Manager and ESU UNIs Manager and ESUs Manager and seed modification Q Discovery of a daisy chain of devices appeared as a mesh. Q Incremental auto-discovery did not discover a DH-ring properly. Q With an Ethernet Routing Switch (ERS) 5510, devices not connected to a fiber port were not discovered. Q Traps were not being received from an ERS Q UNIs (User Network Interfaces) were not discovered on ESU 1800s and ESU 1850s. Q With ESUs configured in a DH-ring, UNIs were duplicated in the UNI list. Q With an ESU in a ring with another ESU, the Datalink Layer view showed two links to the next ESU and to the ERS 8600 it was connected to. Q Devices in a subnet folder that were discovered with the initial discovery were not discovered and were removed from the database when the range of the seed was extended. 1 of 12

2 Tool and Topic CR ID # Description Manager and spaces in path Manager and subnet folder Manager and VPN Routers Community Strings Editor and database import DB Admin Tool and export Device Inventory Viewer details and System 3000 hubs and ES 470 LEDs and ES 470 Logical View and ES 470 Retrieval Failed and ES 470 Retrieval Failed and ES 470 Retrieval Failed and ES 470 Retrieval Failed Q On a Windows 2000 machine with Service Pack 3, stopped responding because Oracle and Optivity were installed with a path that contains spaces. Q An out of range subnet folder was created during a discovery. Q Some subnets in VPN Router routing tables were not being discovered. Q Importing the community strings database failed under various import options. Q With Windows 2003, exporting a database caused the system to stop responding. Q Device Inventory Viewer did not provide enough hardware details for Ethernet Switches. Q did not work with System 3000 hubs. Q With an ES 470 and the gbic inserted, showed the corresponding cooper port LEDs as on, instead of the fiber LEDs. Q The gbic ports were missing from the ES 470 Logical View. Q With an ES 470, both fiber and cooper shared ports showed as active using a right click operation but when a port menu was selected, a Retrieval Failed error was returned. Q With an ES 470, a Retrieval Failed error was returned when any switch general menu option was selected using a right click operation. Q With an ES 470, a Retrieval Failed error was returned when any switch general menu option was selected using a right click operation. Q With the fiber ports active on an ES 470, both fiber and cooper shared ports showed as being active using a right click operation but if a port menu was selected, a Retrieval Failed error was returned. 2 of 12

3 Tool and Topic CR ID # Description and ESU 1850 and SNMPv3 Fault Correlator and ERS 8610 Fault Correlator and Link Down Fault Correlator and unmonitoring a fault Fault Summary and view domains Fault Summary port information Fault Summary slot/port information ERS 8600 object creation object creation pasted data seed creation Q The ESU 1850 MDAs dem-340t-4-port-1000base-t- Module and dem-340mg-4-port-mini-gbic-sfp Module were not recognized or displayed by Expanded View. Q indicated that it had retrieved data successfully from a device when it was not able to access data from the device. Q With an ERS 8610 v3.7, link up/down traps were not being correlated. Q The color of a link did not change to red when a Link Down fault occurred. Q When Unmonitor Faults was set on a device and the unmonitor time expired, monitoring did not resume and the unmonitored device color (default: green) did not change. Q Some faults were not displayed in Fault Summary because the IP of the device was not in the view domain IP range of the user. Q For Ethernet Routing Switches, Fault Summary showed logical port information, rather than physical port information. Q Fault Summary did not show slot and port information. Q When Device View / Interfaces was displayed for an ERS 8600, the IP address of the management interface was not included. Q When an object was created in a resource folder, InfoCenter generated a success message even though this operation is not allowed and the object was not created. Q When a new object was created in a custom folder with an address that was outside all view domains, the object was not being displayed. Q InfoCenter stopped responding when a custom folder with pasted data was saved. Q When a seed was created and saved via Apply, a critical alarm flashed briefly. 3 of 12

4 Tool and Topic CR ID # Description unmanaged devices View Layer InfoCenter launch failure InfoCenter username Installation and Solaris OmniView and BPS 400 OmniView and Deltas per Second OmniView and ERS 8300 OmniView and ES 470 OmniView and private mibs OmniView and VLAN OmniView and VLANs Omniview and Zoom In OmniView date/time OmniView slot/port information OmniView,, TimeTicks Q Unmanaged devices were reset to managed devices when Optivity processes were stopped and restarted. Q InfoCenter stopped responding when the view was changed from the datalink layer to the physical layer. Q InfoCenter failed to launch and generated a folder error. Q It was not possible to log into InfoCenter using the username initial. Q There was an installation error on Solaris. Q OmniView did not display the port activity graph for a BPS 400. Q When the display was changed from the Totals Inactivity panel to the Deltas per Second panel, some ports were not shown. Q With an ERS 8300, OmniView did not display some panels. Q Some information was missing on some OmniView panels for an Ethernet Switch (ES) 470. Q When a new pane was added in OmniView, the private mibs were lost. Q Omniview became unreponsive when a VLAN object was launched. Q Sometimes OmniView stopped responding when 255 VLANs are configured on an ES 460 v3.6 or an ES 470 v3.6. Q Repeatedly zooming in caused OmniView to stop responding. Q OmniView displayed DateAndTime textual-convention type data in hex. Q OmniView did not show slot and port information. Q The TimeTicks value in a mib object was translated incorrectly in Omniview and. 4 of 12

5 Tool and Topic CR ID # Description Optivity Database and UNIs Transport Domain Continuity and test results Transport Domain Continuity refresh rate Trap Registration and ESU 1800 Wireless Mesh Network and fault reporting Q There were problems with QinQ support; standalone UNIs for ESUs not being available; and UNIs being mapped to the wrong node. Q TDC stopped responding when retrieving test results. Q With an ERS 8600, the TDC screen stopped responding when the TDC refresh rate was changed from Manual to 5 seconds. Q Trap registration did not work for an ESU 1800 v300. Q The yellow help text of a fault report did not display the MAC address of a quarantined device. 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, Maintenance Release , and Patches , , Disk space requirements for Solaris under $LNMSHOME: Client-Server: 250 MB Client-Only: 50 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: onms1033_preinstall.log onms1033_install.log 5 of 12

6 onms1033_postinstall.log onms1033_preremove.log onms1033_uninstall.log onms1033_postremove.log Note 3: Wireless Mesh Network customers only: It is recommended that you stay with ONMS Please refer to Section 4.5 below for details. To install ONMS Maintenance Release : 3.1) Download the ONMS Maintenance Release tar.Z archive file 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.2) Uncompress the ONMS Maintenance Release files using the following command: zcat <ONMS1033-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 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 IBM 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>/solaris/cdrom/p1033/ 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: 6 of 12

7 ./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) You are prompted: Do you want to install device templates? If you require the fix for CR Q , OmniView slot/port information, select yes. Note: Installing the device templates required approximately 2 hours. If you do not require a fix for Q , you can skip this step. 3.9) If ONMS is installed with platform software such as IBM NetView or HP OpenView, restart all platform daemons as required. 3.10) Start all Optivity daemons using the "optivity_apps start" command. 3.11) Run the command "optstatus -fe" to ensure all Optivity daemons are running. 4) Important Notes and Known Limitations 4.1) View Domain Use and Enterprise NMS (ENMS) SMOP Database Backup / Restore (Enterprise NMS is the rebranded name for Optivity NMS) An issue was discovered in the maintenance release of ENMS that has its origin in ENMS 10.3 (previously known as ONMS) the discovered issue relates to the use of View Domains. Issue Overview: When View Domains are configured and used, it is required that the View Domain be given a logical name. The issue manifests only when the given View Domain name is the same as the ENMS User Name. If you use View Domains and the View Domain name is different to the ENMS User Name, the issue does not manifest. Issue Symptom: In the event that the ENMS User Name is the same as the View Domain name, if an ENMS database backup is performed, ENMS creates an invalid SMOP database file no 7 of 12

8 error message is generated when this occurs. Any attempt to restore the SMOP database corrupts the database. If your environment meets the described condition that can cause the database to become corrupted, no attempt should be made to restore the SMOP database on any version of ENMS A patch will be provided to correct this issue and SMOP database restore should only be attempted from the stated patch fix please see the Solution section below. Solution: For ENMS 10.3.x users: It is advised that if you use View Domains and your View Domain configuration matches the symptom as described, that you delete any View Domains that share the ENMS User Name with the View Domain, and recreate the View Domain using a new name other than an ENMS User Name Users must upgrade to the latest maintenance release of ONMS ENMS A patch will be released for ENMS ( ) that will be a required patch for the system. This patch will implement a fix that will allow the ENMS database to be backed up and restored correctly For ENMS 10.4 users: This issue will be resolved in ENMS 10.4 and will not require a patch to be installed for ENMS 10.4 users. Upgrading to ENMS 10.4: The ENMS patch is mandatory for upgrading to ENMS In order for customers to upgrade to the next major release of ENMS (ENMS 10.4), it is required that the base ENMS version be ENMS Upgrades from any other release of ENMS 10.3.x to ENMS 10.4 will not be supported. 4.2) 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> 8 of 12

9 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 "uninstall1033" or "install -u" script commands in %LNMSHOME%/p1033. 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. 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. 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. 9 of 12

10 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.) ESU1800 ver 3.0 or above trapderegistration is not working, Q Use the command line interface to do trap deregistration. Slots and ports are not displayed until the daemons are restarted, Q At the completion of successful installation of the Maintenance Release, stop and start all daemons. This activates the slot/port display. Failed to receive the trap from the ESUs attached to the DH-ring, Q The ESUs attached to DH-ring do not show up in Device Inventory Viewer (DIV), Q The root cause of these issues is that the ENMS applications (DIV, Fault Summary) use the topology seed subnet ranges as the IP ranges for view domain without using the subnet mask. Hence, a device that has an IP address greater than the end subnet address is excluded in DIV and Fault Summary. In the discovery seed definition, either: a) enter the largest IP address to be discovered in place of the end subnet address; or b) enter the end subnet as x.x.x.255. for ESU1850 does not show proper port/led status, Q The "In Use LED" color scheme displayed in (EV) does not match the ESU 1850 panel "In Use LED" color. in use/link status in use LED up/up down/up up/down down/down ESU G G G G EV Y off off off Community Strings Editor accepts out of range entries and long strings cause database problems, Q Enter only the valid numbers 1-99 for the timeout values of community string. DIV synchronization is performed on all seeds even if user only specifies one, Q of 12

11 Optical ethernet (OE) slots/ports not viewable with double click of asset in DIV, Q Numerous shortcut keystrokes are either duplicated in menus or are not available, Q Subnet auto-discovery failed to discover a new device, Q Do the auto-discovery with Manager rather than using subnet auto-discovery. After rediscovery, User Network Interfaces (UNI) were not retrieved on ESUs, Q Retrieve the ESU UNI information from the ERS 8600 after the network rediscovery. The Transport Domain Continuity (TDC) test screen locked up when a periodic test was set with a refresh rate of 5 seconds, Q The TDC screen locked up when a TDC test was added or modified with a refresh rate of 5 seconds, Q Use manual refresh for TDC periodical test rather than auto-refresh. When using auto-discovery with a specific IP range entered, Manager sometimes failed to discover the network, Q When using auto-discovery with a specific IP range entered, Manager sometimes failed to discover subnets and devices, Q Run auto-discovery without specifying the IP range, and then use view domain to define the network. Links between AP 7220s cannot be discovered, Q Recommendation for Wireless Mesh Network customers: It is recommended that you stay with ONMS If you require ONMS , please contact your Global Network Product Support representative for a patch. 5) Uninstallation Notes This procedure uninstalls Maintenance Release and the system reverts to the previouslyinstalled version of Optivity NMS (10.3, , or ). 11 of 12

12 Note: If you want to uninstall one or more maintenance releases, you must perform the uninstalls in the reverse order of installation. To uninstall Maintenance Release : 5.1) 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 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 "uninstall1033" 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. 12 of 12