Contents. 1) New Features and Enhancements. New feature: Fault Summary forced refresh

Transcription

1 Contents 1) New Features and Enhancements...1 New feature: Fault Summary forced refresh...1 New feature: Hiding InfoCenter folders...3 New device integration...4 Enhancements...5 2) Summary of Resolved Issues...6 3) Important Notes and Known Limitations...8 4) Supported Platforms and Browsers ) Installation Notes ) Uninstallation Notes ) New Features and Enhancements New feature: Fault Summary forced refresh Under normal operating conditions, the Oracle database establishes a temporary connection with Fault Summary when trap or fault conditions occurs. The connection provides Fault Summary with trap and fault notifications. Under intense trap traffic conditions, the database may not establish the connection with the result that Fault Summary does not display the latest trap and fault information. (You can view the time elapsed from the last notification in the status bar located at the bottom of each Fault Summary window.) The Fault Summary forced refresh feature allows you to set a refresh interval for trap and fault notification. If Fault Summary does not receive any notification within the refresh interval, then Fault Summary queries the database and updates all open views with the current data. Forced refresh is disabled by default. It is enabled at client workstations, allowing you to tailor each client station to the needs of the user or users of that station. To enable forced refresh: 1. At the client station where you want to enable forced refresh, launch Fault Summary. 1 of 14

2 2. On the toolbar, click the Enable Forced Refresh button (see the following figure). The Forced Refresh Interval dialog appears. 3. Enter a refresh interval in the Forced Refresh Interval dialog. Fault Summary updates all open views at the interval set in the Forced Refresh Interval dialog. The default value is 100 seconds. 2 of 14

3 4. To deactivate forced refresh at any time, click Disable Forced Refresh on the toolbar. If you disable forced refresh, the refresh interval is returned to automatic and notifications display as they arrive. New feature: Hiding InfoCenter folders You can now hide any folder in the InfoCenter Folder tree. Hiding a folder To hide a folder: 1. In the Folder tree, right-click on the folder that you want to hide. 2. From the right-click menu, select Properties. 3. From the Properties window, click the View tab. 4. Check Hide. 5. Click Apply or OK to save the setting. OR Click Cancel to discard the change if not already applied. The folder is not displayed in the folder tree but it still exists in the database. Displaying hidden folders To display hidden folders: 1. From the InfoCenter menu bar, navigate to Options > Set preferences > General. 2. From the General window, select the Folder Options tab. 3. Check Show hidden folders. 4. Click OK to save the setting and close the window. OR Click Cancel to discard the change and close the window. Hidden folders are shown in a dimmed state in the Folder tree. 3 of 14

4 New device integration The following table lists the new devices and agents supported in Enterprise Maintenance Release Device Agent version Device Application Switch 3408 v23.2 Secure Router 1002 v9.2 Business Communication Manager 222 v2.6.0 Secure Router 1002E v9.2 Business Communication Manager 252 v2.6.0 Secure Router 1004 v9.2 Business Secure Router 222 v2.6.0 Secure Router 1004E v9.2 Business Secure Router 252 v2.6.0 Secure Router 3120 v9.2 Agent version CSE 1000 Call Server v5.0 Secure Router 4134 v10.0 CSE 1000 Signaling Server v5.0 VPN Router 1010 v7.0.0 Ethernet Routing Switch 1612G v2.1.1 VPN Router 1050 v7.0.0 Ethernet Routing Switch 1624G v2.1.1 VPN Router 1100 v7.0.0 Ethernet Routing Switch 1648T v2.1.1 VPN Router 1600 v7.0.0 Ethernet Routing Switch 2526T v4.0.0 VPN Router 1700 v7.0.0 Ethernet Routing Switch 2526T v4.1 VPN Router 1740 v7.0.0 Ethernet Routing Switch 2526T-PWR v4.0.0 VPN Router 1750 v7.0.0 Ethernet Routing Switch 2526T-PWR v4.1 VPN Router 221 v2.5.0 Ethernet Routing Switch 2550T v4.0.0 VPN Router 251 v2.2.0 Ethernet Routing Switch 2550T v4.1 VPN Router 2600 v7.0.0 Ethernet Routing Switch 2550T-PWR v4.0.0 VPN Router 2700 v7.0.0 Ethernet Routing Switch 2550T-PWR v4.1 VPN Router 4600 v7.0.0 Ethernet Routing Switch 4524GT v5.1 VPN Router 5000 v7.0.0 Ethernet Routing Switch 4526FX v5.0.0 VPN Router 600 v7.0.0 Ethernet Routing Switch 4526FX v5.1 Wireless Access Point 7215 v2.3.0 Ethernet Routing Switch 4526GTX v5.1 Wireless Access Point 7215 v3.0.0 Ethernet Routing Switch 4526GTX-PWR v5.1 Wireless Access Point 7215 v3.0.1 Ethernet Routing Switch 4526T v5.1 Wireless Access Point 7215 v3.0.2 Ethernet Routing Switch 4526T-PWR v5.1 Wireless Access Point 7215 v3.1 Ethernet Routing Switch 4548GT v5.0.0 Wireless Access Point 7215Duo v3.1 Ethernet Routing Switch 4548GT v5.1 Wireless Access Point 7220 v2.3.0 Ethernet Routing Switch 4548GT-PWR v5.0.0 Wireless Access Point 7220 v3.0.0 Ethernet Routing Switch 4548GT-PWR v5.1 Wireless Access Point 7220 v3.0.1 Ethernet Routing Switch 4550T v5.0.0 Wireless Access Point 7220 v3.0.2 Ethernet Routing Switch 4550T v5.1 Wireless Access Point 7220 v3.1 Ethernet Routing Switch 4550T-PWR v5.0.0 Wireless Access Point 7220Duo v of 14

5 Device Agent version Device Agent version Ethernet Routing Switch 4550T-PWR v5.1 Wireless Access Point 7220Duo v3.0.0 Ethernet Routing Switch T v5.1.0 Wireless Access Point 7220Duo v3.0.1 Ethernet Routing Switch T v5.1.0 Wireless Access Point 7220Duo v3.0.2 Ethernet Routing Switch T-PWR v5.1.0 Wireless Access Point 7220Duo v3.1 Ethernet Routing Switch T-PWR v5.1.0 Wireless Bridge 7230 v1.51 Ethernet Routing Switch TFD v5.1.0 Wireless Bridge 7230Ext v1.51 Ethernet Routing Switch 8306 v4.0.0 Wireless Gateway 7240 v3.0.0 Ethernet Routing Switch 8310 v4.0.0 Wireless Gateway 7250 v2.05 Ethernet Switch T-PWR v3.7.0 WLAN Security Switch 2350 v5.0.9 Ethernet Switch T v3.7.0 WLAN Security Switch 2350 v6.0.0 Ethernet Switch T-PWR v3.7.0 WLAN Security Switch 2360 v5.0.9 Ethernet Switch T v3.7.0 WLAN Security Switch 2360 v6.0.0 Ethernet Switch T-PWR v3.7.0 WLAN Security Switch 2380 v5.0.9 Secure Router 1001 v9.2 WLAN Security Switch 2380 v6.0.0 Secure Router 1001S v9.2 WLAN Security Switch 2382 v6.0.0 Enhancements Enterprise Network Management System (NMS) Maintenance Release includes the following enhancements: Tool CR ID Description ENMS Database Q The description for the cause of a fault in the ENMS database was limited to 128 characters. It is now 512 characters. Expanded View Q Wireless Gateway Redundancy, WMN 3.1 is now supported. Fault Script Fault Summary Fault Summary InfoCenter IP Services Manager Q Q Q Q Sysname (device name) is now available as a parameter when you configure a fault script. The fault message for the stacking of an ES470 was enhanced to indicate the physical slot and port information instead of the logical interface. When you have a fault panel open in Fault Summary, you now receive notification if no faults are correlated within a configurable timeframe. The default timeframe is 100 seconds. To change the timeframe, use the Forced Refresh Interval dialog described above under New feature: Fault Summary forced refresh. You can now hide InfoCenter folders. See above under New feature: Hiding InfoCenter folders. IP Services Manager now supports CS 1000 v of 14

6 2) Summary of Resolved Issues resolves the following issues: Tool CR ID Description Device Integration Toolkit Device Integration Toolkit Device Integration Toolkit Device Integration Toolkit Device Inventory Expanded View Expanded View Expanded View Expanded View Q Q Q Q Q Q Q Q Q The DIT Algorithm for finding multiple packages did not work properly. Installation of multiple DITs failed because all DITs were unzipped/untarred to the same directory and the attempt was made to install all at one time. By design, each DIT must be unzipped/untarred to a separate directory and installed one at a time. For WSS v6.0.0, some traps were not correlated into faults. In ENMS , Signaling Server v5.0 was not being discovered. For ERS 2500 devices, there was no information for the rear-ports in DIV when Stacking Mode was enabled. For ERS 2500 v4.0.0, ERS 4548GT, ERS 4548GT-PWR, ERS 4550T, ERS 4550T-PWR, and ERS 4526FX devices, Expanded View showed that a shared port was active when the port was deactivated. For ERS 2500 devices, information for the rear ports was not retrieved when Stacking mode was enabled. For ERS 2500 v4.1 devices, the chassis level pane stopped operating after being refreshed. Dynamic Frequency Selection Threshold Configuration allowed invalid values. Expanded View Q Invalid input values for integer type parameters were being accepted. Fault Correlator Q Trap correlation was delayed in some situations. Fault Correlator Fault Correlator Fault Summary Fault Summary Q Q Q Q On Solaris, the state recorder daemon failed unexpectedly when intense fault traffic was encountered. For ERS 5510 devices with SNMPv3 credentials, Telnet Authentication Traps were not correlating correctly. A junk character was appended to the device label when the label was edited in InfoCenter. Opening fault view on several different devices caused improper titling of the dynamic folders. Fault Summary Q With intense traffic, the auto-refresh stopped working. Fault Summary Q New traps were not inserted into the Trap view at the right position. Fault Summary Q Inefficient use of varbinds queries resulted in performance loss. Fault Summary Q The Trap View window went blank during intense trap activity. Fault Summary Q Fault View did not refresh properly when a new trap arrived. Fault Summary Fault Summary Q Q superping and staterecorder processes were failing because of the redundant processes on the server. Fault Summary failed to open because an ampersand ( & ) was used in the name for a custom folder. 6 of 14

7 Tool CR ID Description Fault Summary InfoCenter InfoCenter InfoCenter Q Q Q Q Some Property Filters (Fault Summary > Faults > Filters > New Filter) were not preserved after Fault Summary was closed and reopened. WLAN Security Switch 2350 v6.0.0 links cannot be discovered because there are no protocols that support discovery of link information. On Windows, logging in as Administrator was not case sensitive and it was possible to log in using administrator. The new slot/port conversion feature of ENMS 10.5 caused performance issues on some servers. InfoCenter Q ENMS 10.5 caused performance issues on some servers. InfoCenter Q The status of the L2 links in Infocenter was not updated. Notification Q All alarms were not propagated to InfoCenter. OmniView OmniView OmniView OmniView OmniView SuperPing Syslog Q Q Q Q Q Q Q For ERS 2500 devices, information for the rear ports was not retrieved when Stacking mode was enabled. For ERS 2500 devices in a stack configuration, some slot and port information was not displayed correctly. For ERS 2500 devices, panes that contained instances indexed by Slot/Port were not refreshed. For the ERS 4526 GTX, many MIB-II Interface panes did not display correctly. OmniView was resetting the counter for in or out octets at approximately 4,200,000,000. On Solaris, the superping daemon failed unexpectedly when intense fault traffic was encountered. For the Business Secure Router 222 and Business Secure Router 252, syslog registration was not working. Syslog Q For AP 7220 v3.1, syslog text messages were truncated. Topology Topology Topology Q Q Q For ERS 55xx v5.0, due to the new features (RIP, OSPF, and VRRP) implemented in the v5.0, the device was not discovered as a Layer 3 Switch. On Solaris, if a WLAN access points device was deleted from InfoCenter, it was not rediscovered. In ENMS , the data link layer showed the physical links instead of the MLT links. Topology Q For ERS55xx and ES45xx devices, MLT links were not discovered. Trap Registration Q For ERS1600 v2.1.0 devices, auto trap registration was not working. Trap Registration Q For the ERS 8300 v4.0.0, Auto Trap registration was not working. Trap Registration Trap Registration Trap Registration Trap Registration Q Q Q Q Trap Server failed when the management status of a device was changed. Deregistration failed in some instances when the management status of a device was changed to unmanaged. Reregistration failed when SNMPv1 credentials are changed to SNMPv3 credentials. Trapreg stopped working when the status of a large number of devices was changed to unmanaged. Trap Registration Q For ERS 1600 devices, traps were not being received. 7 of 14

8 Tool CR ID Description Trap Server Q For ERS 1600 devices, Trap Server failed when a trap was received. Trap Server Q SNMPv2 traps were not handled properly. Trending Q The Trending tool did not export data properly. Trending Q The Trending tool did not export data properly. 3) Important Notes and Known Limitations Process / Tool CR ID Description and Workaround (where applicable) Path Trace Q The enhanced Path Trace end node discovery algorithm identifies the network device to which an end node is connected more quickly. The algorithm does not provide expected results in the following situations: when there is a break in the path between the L3 switch and the L2 switch to which the end node is connected. when the default gateway of the end node subnet is a pure router. In this case, the ENMS database architecture does not provide a way to find the next L2 hop in the path to the end node. when there are special setups on the subnet gateway (for example, MLT or VLAN combined with MLT). These can affect the correlation between the MIBs and the indexes for the device agent. Data Migration to Maintenance Release CS1000 Telephony Manager Q , Q , Q , Q , Q , Q , Q Q , Q , Q Most database data and customizations from previous ENMS releases ( and lower) are preserved when ENMS maintenance release is installed. The following customizations are not preserved: InfoCenter resource folder customizations (Q ) InfoCenter folder backgrounds (Q ) InfoCenter preferences (Q ) AutoTopology Manager options and preferences (Q ) OmniView customizations (Q ) IPSM customizations (Q ) If ENMS maintenance release is uninstalled, the listed customizations from the previous release are restored. Enterprise NMS does not operate properly after the CS1000 Telephony Manager is installed; Telephony Manager does not operate properly after Enterprise NMS is installed or uninstalled The CS1000 Telephony Manager 3.0 cannot be installed on the same Windows server as Enterprise NMS because a library name is the same in both. An upgrade to CS1000 Telephony Manager 3.0 is required to resolve the problem. Do not install the two applications on the same server. Even if you uninstall Enterprise NMS, you must reinstall Telephony Manager. Database Q Do not reset the database. Resetting the database neutralizes any fixes or patches applied by a maintenance release. To reset the database, first uninstall all maintenance releases to return the software to its major release state (10.5), then you can reset the database. Reinstall the maintenance releases after the reset. 8 of 14

9 Process / Tool CR ID Description and Workaround (where applicable) Client / Server software compatibility not applicable A client running Enterprise NMS cannot be operated with a server that is running a lower Enterprise NMS Maintenance Release ( and below). If you upgrade a client to Enterprise NMS , you must also upgrade the server, and vice versa. View domain not applicable When running and you create a new discovery seed, Enterprise NMS creates and maintains a view domain for this seed automatically. The default IP range of this implicit view domain is to Faults, Traps Q , Q , Q DIT packages for applications: installation order CR Q To define a specific IP range for the implicit view domain, you can use AutoTopology Manager > Settings > Enter Seed Specification > Advanced. Alternatively, you can create a new view domain using AutoTopology Manager > Settings > Enter view domain specification. Traps and faults for all interfaces of a device are displayed when any interface of the device is in a view domain assigned to the user. DIT packages for applications establish a launch point within Enterprise NMS for device-specific management applications. Install new DIT packages for applications after installing Enterprise NMS Maintenance Release Note: All non-default application launch points (for examples: Java Device Manager, Enterprise Subscriber Manager) are deleted when is installed. Workaround A: the DIT package is not installed 1. Install Enterprise NMS Install (or Enterprise NMS Maintenance Release x and then Enterprise NMS Maintenance Release ) 3. Install the DIT package for the application. UMP integration and Fault Summary UMP integration and DIT packages Workaround B: the DIT package is installed before installation of Though the application launch points are deleted when Enterprise NMS Maintenance Release is installed, the DIT packages are not. Because a DIT package cannot be installed twice: 1. Create the application launch point manually. Q Fault Summary does not display alarms when it is launched from a device from an umbrella management platform (UMP). Reinstall the UMP after uninstalling ENMS Q DIT packages that are installed after ENMS 10.5 are not removed when ENMS 10.5 is uninstalled. Reinstall the UMP after uninstalling ENMS InfoCenter Q With WLAN Security Switch 2350 v6.0.0, the Access Point 2332 is discovered as an Access Point of 14

10 Process / Tool CR ID Description and Workaround (where applicable) InfoCenter Q When two seeds are created under the same default view domain, " ", the first seed cannot be removed from the view. Select all seeds created under the default View Domain and then execute Remove View Domain from the View command. Trending Q The Trending Tool does not work with the CSE1000. Firewall Q Addresses listed in the $LNMSHOME/conf/restrictedIP.conf file (UNIX) or the %LNMSHOME%\conf\restrictedIP.conf file (WIndows) are not allowed access through the ENMS firewall. That is, the trusted IP address feature for the ENMS firewall does not work. Disable the firewall. Expanded View Q For members of the AP 72xx family, Expanded View does not provide any data when launched from a browser. InfoCenter Q Accelar 1050 v1.3.6 devices appear in duplicate in resource folders. InfoCenter Q The image of a resource folder in graphical view cannot be saved as a png file (File menu, Save as Image). Save as jpg or other supported format. dislink Q When a link is (re)discovered with dislink, the link does not appear in the resource folder. Manually refresh the view by pressing the "Refresh" button. Security of AutoTopology Manager DIT package for AP 7215, 7220, and 7220 Duo devices Q Q An ENMS user with read-only rights for AutoTopology Manager (TOPUI_ACCESS = Read Only) can modify all AutoTopology Manager options (AutoTopology Manager > Settings > Options). The DIT package provided by AP 7215, 7220, and 7220 Duo devices does not support Autotrap registration. Manually add the IP address of the ENMS server to the trap receiver table at the device. Expanded View Q For an ERS 2500, Expanded View stops working when the chassis level panes are refreshed. DIT Admin Q If you login to a remote ENMS server from a local ENMS server and launch DIT Admin, DIT Admin launches on the local host, not the remote host. InfoCenter Q If you activate a seed with AutoTopology Manager but do not start a discovery, you cannot age-out a device in InfoCenter. Start and then stop the discovery process. InfoCenter Q A VPN tunnel displays as two VPN tunnels in InfoCenter. Database Admin Tool Q The Database Admin Tool is not working properly; import, export, and delete actions cannot be performed. Call View Q Call View is not supported on IPv6 servers. TDContinuity Q TDContinuity is not supported on IPv6 servers. Access Control Q Note for Windows users: ENMS usernames are case sensitive. 10 of 14

11 Process / Tool CR ID Description and Workaround (where applicable) Services on Windows AutoTopology Manager Q Q On Windows servers with ENMS , you can start more than one copy of any ENMS service. ENMS is designed so that if InfoCenter is launched and the ENMS database is empty, AutoTopology Manager (ATM) launches automatically. On Windows servers, if the ENMS firewall is running, ATM does not launch automatically. Workaround Disable the firewall. Browser Login Q For Windows servers, when connected to InfoCenter through a browser session from a client machine, you must reenter login credentials when you launch other ENMS applications. IP telephony Q With a CS1K, the ftp authentication on the Signaling Server (user/password) must be the same as specified in the telnet section for the Signaling Server in the ENMS Community Strings Editor. Otherwise, the CS1K is not discovered as a VoIP system and only the Call Server is displayed. Configure the FTP server on the Signaling Server to accept connections using the same user/password as for a telnet session. 4) Supported Platforms and Browsers Server: Windows 2003 Standard Server with Service Pack 1; Windows 2003 Enterprise Server with Service Pack 1 Client: Windows XP Professional with Service Pack 2 Browsers: Microsoft Internet Explorer 6.0 Mozilla 1.7 Mozilla FireFox 2.0 and 3.0 5) Installation Notes applies to both "Client-Server" and Client-Only installations of Enterprise NMS Enterprise NMS installation supports the English language set and English operating system. Disk space requirements: Client-Server: 1500 MB Client-Only: 100 MB Required upgrade path: Install Enterprise NMS x before installing. cannot be installed over ENMS x. To install : 5.1) Login in as user Administrator. 11 of 14

12 5.2) Download all ENMS archive files from the Nortel web site to a directory on the target Enterprise NMS 10.5 server, or to a server with network share capability that has at least 8 GB free space. The download path is: > Support & Training > Software Downloads > Browse product support > Products A-Z > E > Enterprise Network Management System > Software The complete file set is: ENMS archive files - o enms1052_win_zip.001 o enms1052_win_zip.002 o enms1052_win_zip.003 Concatenation script - o create_enms1052_archives.bat CAUTION: Some browsers insert extra characters (examples: [1] or, ) into the filename of a downloaded file. This causes concatenation to fail. Also, Windows 2003 can rename the ENMS archive files from enms1052_win_zip.00x to enms1052_win_zip.zip. Compare the filenames of the downloaded files with the filenames listed above. Correct as required. 5.3) Verify the integrity of the downloaded ENMS archive files. (This step is optional.) 1. Select one of the ENMS archive files. 2. Generate the md5 checksum for the file. If you do not have a tool that does this, you can download one from: 3. Compare the generated checksum with the checksum listed on the Nortel site, on the same page from which you downloaded the files, below the archive. 4. Repeat for the other two ENMS archive files. 5.4) Extract and concatenate the ENMS archive files. You can do this using one of two methods: 1. You can use the downloaded create_enms1052_archives.bat. In this case, go to step You can extract and concatenate the files manually. In this case, go to step ) Run: create_enms1052_archives.bat The archives are created. Go to step of 14

13 5.6) Enter: copy /b enms1052_win_zip.001+enms1052_win_zip.002+enms1052_win_zip.003 enms1052_win.zip This is one command line. There are spaces between: copy and / b and enms 003 and enms 5.7) Unzip the archive using your favorite zip program. If required,you can download one from: 5.8) Stop all topology processes ('toprt', 'topst', 'topdt', 'protur', 'protmr', 'protfr'). To stop the processes, use: AutoTopology Manager > Discovery > Stop Discovery 5.9) Exit/Close all ENMS client applications (examples: InfoCenter, Fault Summary, Expanded View). 5.10) Use Task Manager to check for any Enterprise NMS processes that are still running and execute an End Task for any that are. 5.11) If Enterprise NMS is integrated with an umbrella management platform (UMP) such as IBM Tivoli NetView or HP OpenView Network Node Manager, Nortel recommends that you stop all UMP daemons. 5.12) Change directory (cd) to: <directory>\mswin32\p1052\ where <directory> is the directory to which the Enterprise NMS Maintenance Release files were extracted. 5.13) To install, open a command line window and enter: install1052.bat 5.14) When installation is complete and Enterprise NMS is installed with a UMP, start all UMP daemons if they were stopped previously. 5.15) When installation is complete or the UMP daemons have restarted, generate a list of the Enterprise NMS services that are running. Enter: optstatus fe If any Enterprise NMS services are not running, use Service Control Manager to start them. 13 of 14

14 6) Uninstallation Notes This procedure uninstalls and the system reverts to the previous version of Enterprise NMS (either Enterprise NMS 10.5 or Enterprise NMS Maintenance Release x). To uninstall : 6.1) Login in as user Administrator. 6.2) Stop all topology processes ('toprt', 'topst', 'topdt', 'protur', 'protmr', 'protfr'). To stop the processes, use: AutoTopology Manager > Discovery > Stop Discovery 6.3) Exit/Close all ENMS client applications (examples: InfoCenter, Fault Summary, Expanded View). 6.4) Use Task Manager to check for any Enterprise NMS processes that are still running and execute an End Task for any that are. 6.5) If Enterprise NMS is integrated with an umbrella management platform (UMP) such as IBM Tivoli NetView or HP OpenView Network Node Manager, Nortel recommends that you stop all UMP daemons. 6.6) Change directory (cd) to: %LNMSHOME%/p ) Enter:./uninstall1052.bat or./install1052.bat -u 6.8) When the uninstall is complete and Enterprise NMS is installed with a UMP, start all UMP daemons if they were stopped previously. 6.9) When the uninstall is complete or the UMP daemons have restarted, run: optstatus fe Uninstall is successful when the output of the command indicates that no Enterprise NMS services are running Nortel Networks, Inc. All rights reserved. 14 of 14