Table of Contents
Related Manuals for Nortel V2.3
Summary of Contents for Nortel V2.3
-
Page 1: Release Notes
Magellan Vector OMS-V 2.3 MR1 Release Notes Software Release Date: September 17 1998 Issue: 2.2 1998 Northern Telecom All rights reserved *Magellan is a trademark of Northern Telecom Printed in Canada Magellan Vector OMS-V 2.3 Release Notes... -
Page 2: Revision Record
Revision Record Issue Date Jun 23, 1998 Jun 23, 1998 Aug 11, 1998 Aug 19, 1998 Sep 10, 1998 Sep 17, 1998 Sep 24, 1998 Magellan Vector OMS-V 2.3 Release Notes Purpose OMS-V 2.3 Beta release notes. Change HPOV patch list. Add a unresolved SR on multiple IP interfaces OMS-V 2.3.2 GA Release Notes Add 2.2 and 2.1 resolved SRs... -
Page 3: Table Of Contents
Table of Contents Chapter 1 Introduction Contents of these Release Notes Configuration Supported Functionality Supported OMS-V Hardware OMS-V 2.3 HP-OV 5.01 Documentation Limitation Exclusions Chapter 2 Release Considerations OMS-V 2.3 MR1 Installation Instructions OMS-V 2.3 MR1 Release Introduction Sun Microsystems Platform Considerations Sun Solaris Installation Hewlett Packard Platform Considerations OMS-V Installation on Hewlett Packard... - Page 4 The system is very slow, OR, the system seems to be doing something else from time to time. Chapter 6 Documentation Addendum to NTP 241-9501-200, Software Installation and Commissioning for Vector and Access Shelf Magellan Vector OMS-V 2.3 Release Notes...
-
Page 5: Table Of Contents
Tables and Figures Table 1: OMS-V compatibility with Vector switching components ...8 Table 2: OMS-V 2.3 MR1 Feature Limitations ...10 Table 3: Product Release List ...12 Table 4: Third Party Product Patch List...13 Figure 1: Upgrade OMS-V...16 Table 5: OMS-V 2.3 Resolved Service Requests ...17 Table 6: Unresolved Service Requests...18 Table of Contents 5... - Page 6 6 Table of Contents Magellan Vector OMS-V 2.3 Release Notes...
-
Page 7: Chapter 1 Introduction
• Chapter 6 provides a list of the changes and additions to NTP 241-9501- 200, Vector Software Installation and Commissioning. Configuration Supported The various components of a Vector network include: • Vector Switching System (VSS), a Vector switching component. -
Page 8: Functionality Supported
The following table outlines the configuration compatibility between the OMS-V and Vector switching components. Table 1: Open Management System Vector (OMS-V) compatibility with Vector switching components Network mgmt release / platform VSM 1.1 SunOS 3.4 & HP-OV 3.3 HP-UX 9.05 & HP-OV 3.3 VSM 2.0 SunOS 3.4 &... -
Page 9: Oms-V 2.3
• NTP 241-9501-103, Vector Site Requirements and Preparation Guide • NTP 241-9501-111, Vector Hardware Description • NTP 241-9501-200, Vector Software Installation and Commissioning • NTP 241-9501-205, Vector Hardware Installation and Upgrade User Guide • NTP 241-9501-301, Vector Operations and Maintenance Using VMI User Guide •... -
Page 10: Exclusions
UBR Policing and UNI traffic class. As a result, OMS-V was unable to obtain or assign the correct information on the switch. Since Release 2.2.3, the MIB OID has been updated to be consistent on both VSS and OMS-V. However, all previous switches still use the old MIB OID, the UNI traffic class can not be set via the OMS-V Release 2.2.3 GUI on any version of VSS previous to VSS Release 2.2.3. - Page 11 interfaces and not change it without first reconfiguring, rediscovering, and cleaning up HP-OV database.) Magellan Vector OMS-V 2.3 Release Notes...
-
Page 12: Chapter 2 Release Considerations
Chapter 2 Release Considerations The following table lists the latest software loads for the products shown: Product OMS-V OMS-V 2.3 MR1 Installation Instructions For OMS-V 2.2.2 and onward, installation was simplified by creating a single command to do both the removal of an old installation and adding the new installation in a single script. -
Page 13: Oms-V 2.3 Mr1 Release Introduction
HP-UX 10.20 on an Hewlett Packard workstation • installation of or upgrade to HP-OpenView 5.01 software on the Sun or HP platforms plus the HP OV patches as noted above. IMPORTANT NOTE: There is a set of installation “gotchas” covered in the following list that must be followed for OMS-V R2.3 MR1 to function... -
Page 14: Sun Solaris Installation
VMI. This problem is avoided by following the instructions provided in “Required font set for Solaris Installation in Chapter 3 of NTP 241-9501-200, Vector Software Installation and Commissioning. Hewlett Packard Platform Considerations Hewlett Packard discontinued support for the HP-UX 9.6 operating system as of 2Q97. -
Page 15: Vsm To Oms-V Upgrade Strategy Considerations
The data captured in the VSM/OMS-V database cannot be carried forward. Therefore, it will take a period of time to rediscover the network. If the current software on the workstation is a VSM release, the installation must be cleaned out by following the procedure for “Removing VSM software”... -
Page 16: Upgrade Vsm 1.1.X/2.0 Or Oms-V 2.2.X To Oms-V 2.3 Mr1
- install HP-OV 5.01 and appropriate patches. - install OMS-V 2.3 MR1 following the instructions in NTP 241-9501-200, Vector Software Installation and Commissioning. 3) Connect and start HP-OV 5.01 in network - OMS-V 2.3 MR1 manages VSS 1.1.x/2.0.x/2.2.x/2.3 MR1 switches. VSS2.3 MR1 switches will not be managed by earlier versions of VSM/OMS-V. -
Page 17: Chapter 3: Resolved Service Requests
From the Front Panel View, One UPC contract was configured. Trying to configure the second UPC, the following error message appeared: The switch is running a software version that does not support UPC Tables. This feature requires at least version 3.4.0. - Page 18 10174616 Unable to Configure CDAS or AVR From The Front Panel View When selecting configure CDA or AVR from the front panel view, the following message appeared whenever the hostname was displayed as an IP address, such as 5.1.1.1: Error:bad window path name “.cdasdlg5.1.1” Please report this error to Northern Telecom Magellan Technical Support Improvements were made to the CDAS and AVR windowing setup.
-
Page 19: Chapter 4 Unresolved Service Requests
Chapter 4 Unresolved Service Requests Unresolved Service Requests The table below lists all known unresolved high priority Service Requests Table 6: Unresolved Service Requests SR Number Description 10131026 OMS-V 2.2.1 - No Colors Left. 10092242 Trace PVC feature does not trace the complete VCC 10176700 Log Hosts utility does not launch from the Networks submap 10175312... - Page 20 10092242 Trace PVC feature does not trace the complete VCC Recovery • The trace feature can only be used to show the ingress port and the egress port on a single switch. This is planned to be fixed in a subsequent maintenance release.
- Page 21 10187107 Problem When Discovering Through Ethernet Impact • There is an inconsistency in the colour of connection links when discovering over ethernet with ie0, qaa0, and qaa1 up. An other workstation with qaa1up shows no problems. Prevention • Connection links need to be checked using VMI. Recovery •...
-
Page 22: Chapter 5 Trouble Shooting
/opt/OV/bin/ovstatus (verify the required processes are running) /opt/OV/bin/ovw & Allow 20 minutes for the switches to be discovered. If you still have problem, please contact Nortel Support. The system is very slow, OR, the system seems to be doing something else from time to time. - Page 23 To re-enable netmon, do the following: /opt/OV/bin/ovaddobj /etc/opt/OV/share/lrf/netmon.lrf ovstart netmon To prevent HP OpenView from displaying a dialog box stating that netmon is not running, you may turn off the polling of this process. Set the.netmonCheckFreq to 0 for XNmevents. Follow the instructions found in the /usr/openwin/lib/app-defaults/XNmevents file.
-
Page 24: Chapter 6 Documentation
Chapter 6 OMS-V Documentation Addendum to NTP 241-9501-302, Open Management System for Vector (OMS-V) Guide 1. Chapter 6, p. 122, Figure 26, Tachometer In Figure 26, the view remote command displays a qaa0 IP address interface type. In this figure for example, the qaa0 IP address is 5.1.1.1. To establish a connection, you need to use a qaa0 IP address interface type for the view remote command.