Enterprise Network Management System (NMS) Maintenance Release addresses the following issues:

Transcription

1 Contents 1) Release Summary...1 2) Enhancement Requests...6 3) Important Notes and Known Limitations...7 4) Platforms Supported...9 5) Installation Notes...9 6) Uninstallation Notes ) Release Summary Enterprise Network Management System (NMS) Maintenance Release addresses the following issues: Access Control Q A user with read-only access was able to modify Fault Summary preferences. Q Q Q Q Q With AccessControl On, a user cannot activate a seed unless the root user / Administrator has assigned the implicit view domain of the seed to the user. Appropriate warning and error messages were not displayed for this condition. A router was configured to use a static route as back-up for a number of on-demand circuits. The static route was being displayed in the Internet view as a separate entity. When the General > Comm Strings > All Database discovery preference was selected, an invalid character appeared in the toprt log file. On an ERS 8600, inexplicable MIB errors were encountered when dislink was run. Dual homed (DH) ERS 8600 nodes were displayed as brown, indicating a fault condition when one did not exist. Q Links between two OPEs or between an OPE and an ERS 8600 were not being discovered. Q Q Q Devices were placed in the wrong subnet folder. Subnets were not discovered using a routerless discovery. Subnets were not discovered or devices were placed in the wrong subnet folder. 1 of 11

2 Q Q Q Q Q Q A network was not discovered when a seed was defined with a specific IP address range. View domains created by a non-root user did not persist across sessions. When the VLAN folder view was changed to the physical layer, the VLAN folder appeared to be empty. A second discovery was required to discover new VLANs. When an ERS 8600, an ESU 1800, and an ESU 1850 were deployed in a Optical Ethernet configuration, an issue with the ViewDomain caused problems in a number of applications (InfoCenter, Device Inventory, Fault Summary) were observed. The broadcast address of an Ethernet Routing Switch 1424 was being used as the IP_label. Q The end nodes connected to a ERS 8600 version and a 8648 GTR card were not discovered. Device Integration Toolkit Device Integration Toolkit Device Integration Toolkit Q Q Q Q Q Q Q Q Q Newer agent versions were available on the Nortel site but they were not detected. (Related: Q , Q ) The Update component feature (Tool > Update component) did not always identify all the new DIT packages available from the Nortel site. Java Device failed to open when the user tried to launch it using the context (right-click) menu of the IP address of a switch. On a standalone client running Windows 2000 or 2003, a java error occurred when devices were exported to a.csv file. The wrong agent version was displayed for a CS 1000E Call Server. When the asset information for an ERS 8600 DH-ring was viewed, the serial number and HW Rev were missing. When the asset information for an ESU 1850 was viewed, information for port 1 was wrong and was missing for other ports. A Business Policy Switch (BPS) stack appeared as one device. The BPS stack is designed to appear as one device. An Ethernet Switch 470 stack appeared as one device. The ES 470 stack is designed to appear as one device. disdevice Q Users without appropriate access permissions were able to discover devices with disdevice. 2 of 11

3 dislink Q Dislink discovered devices outside the range of the assigned view domain. Expanded View Q The text shown in the blue bar at the bottom of the About Expanded View menu option did not fit the window and / or was difficult to read. Expanded View Q For an Ethernet Switch T PWR v3.6.2, when the Gigabit module (gbic) was installed and the link was up, only the shared copper port LEDs were on when the gbic was a fiber module. Expanded View Q For an Ethernet Switch T PWR v3.6.2, both fiber and copper shared ports were displayed as active when fiber ports were up. Fault Correlator Q The bsnconfigrationsavedtonvram v3 trap from BayStack devices was not converted to a fault. Fault Correlator Q OtmOpenxxxxx traps received from the Communication Server (rebranded from OTM) were not correlated into faults. Fault Script Q On VPN Routers (formerly Contivity Extranet Switches), scripts for some secure router faults did not execute. Fault Summary Q With an Ethernet Switch 470 v4.2 or an ES v4.4, the Mac address was not provided in the fault description. (Reference: Q ) Fault Summary Q On an ERS T/48T, the slot/port information of a link that goes up/down was shown incorrectly. Fault Summary Q Slot and port information was not displayed for a Link Up / Link Down fault. Fault Summary Q Traps from an ERS 8600 on a particular subnet were not reported. Fault Summary / Fault Script Fault Summary / Trap Server Fault Summary / Trap Server Q Q Q On an ERS 8600, the F_Generic_3_LINK_DOWN_RFC1573_2_3_new generic fault was not available as a menu option for fault scripts. Given that the trap-sending IP address of a device has been discovered, then all traps from that IP address are received and processed by Enterprise NMS, even if a specific interface is not within the seed range. When InfoCenter determined the appropriate fault color to assign to the device, all interfaces were considered. However, the faults from the specific interface did not appear in Event Browser because the view domain did not include the IP address of the specific interface. See also Q It appeared that traps were not being received from ESUs attached to an ERS 8600 DH-ring. See also Q of 11

4 InfoCenter Q Infocenter stopped functioning when you selected No for managing a device function. InfoCenter Q When a customer folder was created using the OE ring filter, the folder was not populated and appeared empty. InfoCenter Q On a Windows client, setting the Options > Set Preferences > Global > Display DNS Names did not seem to work. InfoCenter Q An ESU in a particular subnet was not discovered. OmniView Q Java exception errors occurred when OmniView statistics panes were refreshed automatically (as a result of a polling interval expiring). OmniView Q Beta-Delta > Second, Peak Delta > Second, Average Delta > Second panes were not working OmniView Q The Pane > Export function only exported total values, regardless of the values currently displayed. OmniView Q Graphs did not plot data correctly. OmniView Q With an ERS 8600, the defined panes for blade type did not match the blade hardware types. OmniView Q For 8672 ATM blades on ERS 8600 switches, no values are provided for ATM statistics under "Ports-by-Slot" for "ATM-PVC" and "ATM 1483 Elan". OmniView Q On an ERS 8600, the IP Routing > IP > Circuitless pane listed all IP addresses, not just the circuitless IP addresses. OmniView Q IPX addresses were displayed in decimal, not HEX. OmniView Q On BayRS routers, under Router > Table > Protocol IPX, the Route Table, SAP Table, and Interface Table panes were empty. OmniView Q When the SNTP Protocol pane was opened, the pane was empty and OmniView closed. OmniView Q On a Business Policy Switch 2000 v , the Port Details > VLAN ID pane used HEX format. OmniView Q On a Business Policy Switch 2000 v , the "Name", "Port Members", "Active Members", "Static Members" and "Not Allow To Join Members" values on the Vlan > Basic Vlan pane were displayed in HEX. OmniView Q On a Centillion 100 MCP v4.2.1, the fields on the Port-by-Slot > Slot 1 (ATM MCP) > Activity pane applied to Ethernet not ATM. No stats were displayed as the fields did not match the hardware type. (See also Q ) 4 of 11

5 OmniView Q See Q OmniView Q On a System 5000BH MCP v4.2.1, the "ELAN Name" values on the LANE Services > LAN Emulation Server > Profile pane were displayed in HEX. OmniView Q On an ES T v , the "VLAN ID" values on the Port Details > VLAN Information pane were displayed in HEX. OmniView Q On an ES T v , the "Name", "Port Members", "Active Members", "Static Members" and "Not Allow To Join Members" values on the Vlan > Basic Vlan pane were displayed in HEX. OmniView Q On an ES T v , the "VLAN ID" values on the Port Details > VLAN Port Information pane were displayed in HEX. OmniView Q On an ES T v , the "Unassigned Ports" values on the Spanning Tree > Spanning Tree Group Information pane were displayed in HEX. OmniView Q On an ES T v , when the Rapid Spanning Tree Protocol > Rapid Spanning Tree Extensions pane was opened, the pane was empty and OmniView closed. OmniView Q On an ES T v , when the Multiple Spanning Tree Protocol > Multiple Spanning Tree Group Information pane was opened, the pane was empty and OmniView closed. OmniView Q On an ES T v , when the SNTP Protocol > Configuration pane was opened, the message "No Data in Pane" was displayed. OmniView Q On an ES T v , when the SNTP Protocol > Status pane was opened, the message "No Data in Pane" was displayed and OmniView closed. OmniView Q On a BayRS router, when the Circuit Summary > Protocols > Protocol IP > Traffic Information pane was opened, the pane was empty. OmniView Q On a BayRS router, the Last Change value on the MIB2 > Interface > Status/Profile pane was incorrect. OmniView Q On a BayRS router, when the (VNR) Circuit Summary > Protocols > Bridge > Learning Bridge Info pane was opened, the pane was empty. OmniView Q On an ERS 5500, the Port activity pane did not show unit/port information. OmniView Q On an ESU 1800 and an ESU 1850, response was very slow for the QOS > 802.1p User Priority pane.. 5 of 11

6 OmniView Q When panes were opened and the Display Label (Options->Display Label) was changed from Display Default Name to Display Sys Name, some operations and displays did not work properly. OmniView Q The Belongs to option remained active for a device even after the command was executed on the device and its subnetwork was displayed. OmniView / InfoCenter Q For an ESU 1800 and an ESU 1850, some port numbers were unreadable in OmniView; for an ERS 8600, a port number was unreadable in the VLAN folder. Syslog Q Syslog registration was not supported on VPN Router 221 and VPN Router 251. Syslog Q Syslog messages from Access Point 7220s were not displayed. Transport Domain Continuity Q Some columns displayed information in the wrong (HEX) format. Trap Registration Q On an ERS 8600 v3.7.11, the Enterprise NMS server was unable to register as trapreceiver. Trap Registration Q Auto trap registration did not work on an ERS 1600 v Trap Registration Q AutoTrap Registration failed with ESU 1850 v3.0.0 or later. Trap registration / Management state Q An Ethernet Services Unit (ESU) 1800 could not be placed in the Unmanaged state and trap registration could not be de-selected. Username Q The username initial caused problems with some Enterprise NMS applications. 2) Enhancement Requests Enterprise NMS Maintenance Release addresses the following enhancement requests: Tool CR ID Enhancement Fault Summary / Fault Script Q You can create fault scripts on the Ethernet Switch 470. InfoCenter Q If you access the Enterprise NMS server through a web browser, you can launch an application from within InfoCenter without reentering your user name and password. InfoCenter Q You can use a dot in a user name. For example: john.buck 6 of 11

7 Tool CR ID Enhancement InfoCenter Q If you access the Enterprise NMS server through a web browser, you can launch an application from within InfoCenter without reentering your user name and password. OmniView Q Device counters are zeroed when they are cleared. OmniView Q Resized windows maintain their new size after a new polling interval starts. OmniView Q A Removed Entity item has been added to the Menu > File options. This option allows you to remove an entity from the Navigation pane. 3) Important Notes and Known Limitations 3.1) Enterprise NMS 10.4 must be installed prior to installing the Enterprise NMS Maintenance Release ) CR: Q , CR: Q One or more blank command lines can be inserted in the Modify Application Launch window when Enterprise NMS Maintenance Release is installed. The blank lines can overwrite existing launch definitions with the result that the corresponding applications are no longer available on the right-click menu. Workaround: 1. Start Application Launch (InfoCenter: Admin > Application Launch). 2. Locate the blank command line in the Application List of the Modify Application Launch window. 3. Delete the blank line. 4. Reenter the original command line. 3.3) Fault Summary on a client running Enterprise NMS 10.4 does not operate in conjunction with a server that is running Enterprise NMS Maintenance Release The converse is also true. Nortel recommends that you update both server and client machines. 3.4) CRs: Q , Q , Q For any device, all traps and faults (for all interfaces) are displayed when any interface of the device is in the view domain assigned to the user. 3.5) CRs: Q , Q , Q , Q , Q , Q , Q , Q , Q , Q The fixes for these CRs can cause installation time to increase by up to one hour. An option to skip these fixes is provided during installation. 7 of 11

8 3.6) Enterprise NMS Maintenance Release includes several new agents that are installed using the Device Integration Toolkit. Install the new agents before installing Enterprise NMS Maintenance Release to avoid overwriting enhancements provided by the Enterprise NMS Maintenance Release ) When you create a new discovery seed, Enterprise NMS creates and maintains a view domain for this seed automatically. In Enterprise NMS Maintenance Release , the default IP range of this view domain is to To define a specific IP range for this view domain, use > Settings > Enter Seed Specification > Advanced. Alternatively, you can create a new view domain using > Settings > Enter view domain specification. 3.8) CR: Q If a discovery is stopped manually ( > Discovery > Stop Discovery) and is closed before the stop notification is received, the seed is not removed from the discovery queue and the discovery continues. Workaround: If a discovery is stopped, wait for the stop notification before closing. 3.9) CR: Q If a view domain is created when Access Control is off, the range of the view domain changes when Access Contol is turned on. To reestablish the view domain: 1. Ensure that Access Control is on. 2. Launch. 3. Navigate to Settings > Enter Seed Specification. 4. Select a seed. 5. Click Apply. 6. Repeat for all seeds. Workaround: Only create view domains when Access Control is on. 3.10) CR: Q When a view domain is created by the Administrator and assigned to a user and that user opens Fault Summary, the Fault Summary report can have many blank lines between faults. This causes the report to paginate poorly: a large blank space does not indicate the end of the report. Workaround: Ensure that you have scanned to the end of the report. 8 of 11

9 4) Platforms Supported Server: Windows 2000; Windows 2000 Advanced Server with Service Pack 4; Windows 2003 Enterprise Server with Service Pack 1 Client: Windows XP Professional with Service Pack 2; Windows 2000 Professional with Service Pack 4 5) Installation Notes Enterprise NMS Maintenance Release applies to both "Client-Server" and Client-Only installations of Enterprise NMS Disk space requirements: Client-Server: 50 MB Client-Only: 5 MB To install Enterprise NMS Maintenance Release : 5.1) Login in as user Administrator. 5.2) Download the enms1041_win.zip archive file from the Nortel web site to a directory on the target Enterprise NMS 10.4 server, or to a server with network share capability. Download path: > Support & Training menu > Technical Support item > Software Downloads item > Browse product support tab > Products A-Z tab > E > Enterprise Network Management System entry > Software link. 5.3) Extract the files to the directory to which the files were downloaded. If you are using WinZip: verify that the all files and use folder names options are selected verify that the permissions for the extracted files are set to read, write, and execute before extracting the files, enter the path to the directory to which the files were downloaded. 5.4) Stop all topology processes ('toprt', 'topst', 'topdt', 'protur', 'protmr', 'protfr'). To stop the processes, use: > Discovery > Stop Discovery 5.5) Exit/Close all ENMS client applications (examples: InfoCenter, Fault Summary, Expanded View). 9 of 11

10 5.6) Use Task to check for any Enterprise NMS processes that are running and End Task any that are. 5.7) If Enterprise NMS is integrated with an umbrella management platform (UMP) such as IBM Tivoli NetView or HP OpenView Network Node, Nortel recommends that you stop all UMP daemons. 5.8) Change directory (cd) to: <directory>/mswin32/cdrom/p1041/ where <directory> is the directory to which the Enterprise NMS Maintenance Release files were downloaded and extracted. 5.9) To install Enterprise NMS Maintenance Release , enter: install1041.bat 5.10) When installation is complete and Enterprise NMS is installed with a UMP, start all UMP daemons if they were stopped previously. 5.11) When installation is complete or the UMP daemons have restarted, generate a list of the Enterprise NMS services that are running. Enter: optstatus fe The optstatus fe command generates a message if a service fails to start. Use Service Control to start the service. 6) Uninstallation Notes This procedure uninstalls Enterprise NMS Maintenance Release and the system reverts to Enterprise NMS To uninstall Enterprise NMS Maintenance Release : 6.1) Login in as user Administrator. 6.2) Stop all topology processes ('toprt', 'topst', 'topdt', 'protur', 'protmr', 'protfr'). To stop the processes, use: > Discovery > Stop Discovery 6.3) Exit/Close all ENMS client applications (examples: InfoCenter, Fault Summary, Expanded View). 10 of 11

11 6.4) Use Task to check for any Enterprise NMS processes that are running and End Task 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, Nortel recommends that you stop all UMP daemons. 6.6) Change directory (cd) to: %LNMSHOME%\p ) Enter: uninstall1041.bat or install1041.bat -u 6.8) When installation is complete and Enterprise NMS is installed with a UMP, start all UMP daemons if they were stopped previously. 6.9) When installation is complete or the UMP daemons have restarted, generate a list of the Enterprise NMS services that are running. Enter: optstatus fe The optstatus fe command generates a message if a service fails to start. Use Service Control to start the service Nortel Networks, Inc. All rights reserved. 11 of 11