Nortel V2.3 Instruction Manual

Magellan Vector OMS-V 2.3 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

2
Magellan Vector OMS-V 2.3 Release Notes
Revision Record
Issue Date Purpose
1.0 Jun 23, 1998 OMS-V 2.3 Beta release notes.
1.1 Jun 23, 1998 Change HPOV patch list.
Add a unresolved SR on multiple IP interfaces
1.2 Aug 11, 1998 OMS-V 2.3.2 GA Release Notes
1.3 Aug 19, 1998 Add 2.2 and 2.1 resolved SRs
Add unresolved SRs uni-directional links displayed for
multiple IP interface types
2.0 Sep 10, 1998 OMS-V 2.3 MR1 release notes
2.1 Sep 17, 1998 Document review modifications
2.2 Sep 24, 1998 Add unresolved SR

Table of Contents 3
Magellan Vector OMS-V 2.3 Release Notes
Table of Contents
Chapter 1 Introduction 7
Contents of these Release Notes 7
Configuration Supported 7
Functionality Supported 8
OMS-V Hardware 8
VSS 8
OMS-V 2.3 9
HP-OV 5.01 9
MDP 9
Documentation 9
Limitation 9
Exclusions 10
Chapter 2 Release Considerations 12
OMS-V 2.3 MR1 Installation Instructions 12
OMS-V 2.3 MR1 Release Introduction 13
Sun Microsystems Platform Considerations 13
Sun Solaris Installation 14
Hewlett Packard Platform Considerations 14
OMS-V Installation on Hewlett Packard 14
HP-Openview Considerations 14
VSM to OMS-V Upgrade Strategy Considerations 15
Upgrade VSM 1.1.x/2.0 or OMS-V 2.2.x to OMS-V 2.3 MR1 16
Chapter 3: Resolved Service Requests 17
OMS-V 2.3 Resolved Service Requests 17
10176058 Link Connection Between 2.3 and 2.3 Switches is shown as
Uni-Directional 17
10077699 It takes too long to reflect network changes on VSM Magellan
submap 17
10174616 Unable to Configure CDAS or AVR From The Front Panel View 17
Chapter 4 Unresolved Service Requests 18

4Table of Contents
Magellan Vector OMS-V 2.3 Release Notes
Unresolved Service Requests 18
Descriptions of Unresolved Service Requests 18
10131026 OMS-V 2.2.1 - No Colors Left 18
10092242 Trace PVC feature does not trace the complete VCC 18
10176700 Log Hosts utility does not launch from the Networks submap 19
10171439 conf vcc sh and con vpc sh give error on vmi from host 19
10131028 Front Panel Alarms Don’t Match Popup 19
Chapter 5 Trouble Shooting 21
After performing OMS-V upgrade, switches are not being discovered, Magellan
Network Submap remains empty. What is wrong? 21
The system is very slow, OR, the system seems to be doing something else
from time to time. 21
Chapter 6 Documentation 23
Addendum to NTP 241-9501-200, Software Installation and Commissioning for
Vector and Access Shelf 23

Table of Contents 5
Magellan Vector OMS-V 2.3 Release Notes
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

6Table of Contents
Magellan Vector OMS-V 2.3 Release Notes

7
Magellan Vector OMS-V 2.3 Release Notes
Chapter 1 Introduction
These release notes provide release information for the Vector system
managementcomponentOMS-V(OpenManagementSystem-Vector)release
2.3 MR1 (Maintenance Release 1). OMS-V replaces VSM (Vector System
Manager).
Contents of these Release Notes
• Chapter 1 provides an overview of this document and the product
functionality included and excluded for this release.
• Chapter 2 contains general release considerations.
• Chapter 3 lists Service Requests resolved in this release.
• Chapter 4 lists unresolved high priority Service Requests.
• Chapter 5 outlines common problems encountered with OMS-V and how
to resolve them.
• 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.
• Magellan Data Provider (MDP), a Magellan product billing component.
• Open Management System - Vector (OMS-V), a Vector network system
management component.
This release includes support for the following configurations:
• 2.5 or 5.0 Gbits Vector switches with the Vector Switching System (VSS)
versions VSS 1.1.x, VSS 2.0.x, VSS 2.2.x, and/or 2.3.x
• The Magellan Data Provider (MDP). Refer to the MDP release notes for
compatibility with Vector releases.
• The Open Management System - Vector (OMS-V) version OMS-V 2.3
MR1. (This was previously known as the Vector System Manager
component.)

8
Magellan Vector OMS-V 2.3 Release Notes
The following table outlines the configuration compatibility between the
OMS-V and Vector switching components.
Functionality Supported
OMS-V Hardware
For OMS-V 2.3 MR1, it is recommended that the OMS-V workstations be Sun
Microsystems’ or Hewlett Packard’s current product line that supports their
Solaris 2.6 or HP-UX 10.20 operating systems.
VSS VSS 2.3 MR1 release notes are covered in a separate document. Please refer
to the VSS 2.3 MR1 release notes for any on-switch related issues.
Table 1: Open Management System Vector (OMS-V) compatibility with Vector switching
components
Switching component
Network mgmt release / platform VSS
1.1.x VSS 2.0.x VSS 2.2.x VSS 2.3 MR1 AS 1.0
VSM 1.1 SunOS 3.4 & HP-OV 3.3 Y - - - -
HP-UX 9.05 & HP-OV 3.3 Y - - - -
VSM 2.0 SunOS 3.4 & HP-OV 3.3 Y Y - - -
HP-UX 9.05 & HP-OV 3.3 Y Y - - -
OMS-V 2.1 Solaris 2.5.1 & HP-OV 4.11 Y Y - - Y
HP-UX 10.20 & HP-OV 4.11 Y Y - - Y
OMS-P/V 2.1 Solaris 2.5.1 & HP-OV 4.11 Y Y - - Y
OMS-V 2.2.3 Solaris 2.5.1 & HP-OV 4.11 Y Y Y - Y
HP-UX 10.20 & HP-OV 4.11 Y Y Y - Y
OMS-V 2.3 GA Solaris 2.6 & HP-OV 5.01 Y Y Y Y Y
HP-UX 10.20 & HP-OV 5.01 YYYYY
OMS-V 2.3 MR1 Solaris 2.6 & HP-OV 5.01 Y Y Y Y Y
HP-UX 10.20 & HP-OV 5.01 YYYYY
Bold represents OMS-V 2.3 MR1 (Maintenance Release 1) Vector system management elements

9
Magellan Vector OMS-V 2.3 Release Notes
OMS-V 2.3
The OMS-V 2.3 MR1 release introduces no new functionality. Please see
OMS-V 2.3 GA Release Notes for new functionality introduced in OMS-V
2.3.
Further details are provided in the related NTP 241-9501-302, Open
Management System for Vector (OMS-V) Guide.
HP-OV 5.01
In HP-OV 5.01, Overlay Submap option is provided for controlling the
creation of map windows. The default option for Overlay Submap is to change
maps/submap without creating new windows, to have only one window visible
at a time. Double clicking on one enclosure in the network submap for
example, will not create a new connection submap, but transforms the network
submap into a connection submap. Further details are provided in the NTP
241-9501-302, Open Management System for Vector (OMS-V) Guide.
MDP Please see the release notes appropriate to MDP releases supporting VSS
components.
Documentation
• Release Notes
• NTP 241-9501-000, Vector List of Terms
• NTP 241-9501-010, Vector General Description
• 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
• NTP 241-9501-302, Open Management System for Vector (OMS-V) Guide
• NTP 241-9501-501, Vector Hardware Maintenance User Guide
• NTP 241-9501-503, Vector Management Interface (VMI) Commands
Reference Guide
Limitation The UNI traffic class and UBR policing features are managed via the OMS-V
Release 2.3 MR1 GUI starting from VSS version Release 2.2.3. Earlier
versions of VSS and OMS-V had a mismatch in the MIB OIDs associated with

10
Magellan Vector OMS-V 2.3 Release Notes
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. For all previously released versions of VSS, the on-switch VMI
must be used.
Table 2: OMS-V 2.3 MR1 Feature Limitations
Please note that these features are limited to on-switch VMI only for switches
with previous versions to VSS Release 2.2.3.
A defect exists on showing bi-directional links when qaa0 and non-qaa0 (ie0,
qaa1, qaa2,qaa3) IP interface types are up. This is expanded upon in Chapter
4, Unresolved Service Requests.
Exclusions
Excluded from this release:
• OMS-V inter-work with OMS-P, as documented in 10186505. This SR
stops deployment of OMS-V 2.3.3 MR1 with OMS-P.
• Management Console when OMS-V uses IP over ATM.
• Using Remote Front Panel command when OMS-V is managing switches
with either ie0, qaa1, qaa2, or qaa3 interfaces.
• Auto-discovery when OMS-V is managing switches with either ie0, qaa1,
qaa2, or qaa3 interfaces.
Note 1: Although OMS-V can manage Vector switches using one of the IP in-
terfaces: ie0, qaa0, qaa1, qaa2, or qaa3. Remote Front Panel command
and auto-discovery function can only be used with qaa0 interface. When
OMS-V discovery is not using the qaa0 interface, the user must specify
all the switches to be discovered.
Note 2: OMS-V inter-work with OMS-P is pending a forthcoming release of
OMS-P.
Excluded from the product:
• Simultaneously using more than one of the IP interfaces: ie0, qaa1, qaa2,
or qaa3, on OMS-V workstations. (Note: user must select one of the
OMS-V 2.3 MR1
Features VSS R2.2.1 VSS R2.2.2 VSS R2.2.3 VSS R2.3 MR1
UNI Traffic Class on-switch VMI only VMI & GUI
UBR Policing on-switch VMI only VMI & GUI

11
Magellan Vector OMS-V 2.3 Release Notes
interfaces and not change it without first reconfiguring, rediscovering, and
cleaning up HP-OV database.)

12
Magellan Vector OMS-V 2.3 Release Notes
Chapter 2 Release Considerations
The following table lists the latest software loads for the products shown:
Table 3: Product Release List
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. This continues in OMS-V 2.3 MR1. Installers of
OMS-V are no longer required to do extra UNIX steps.
The following set of files are now delivered for each release.
• the OMS-V HP-UX and Solaris tar files for the loads listed in the table
above
• the release notes (this document)
• NTP 241-9501-200, Vector Software Installation and Commissioning
• shareLib.sh (upgrade script)
• omsvupgrade (upgrade script)
The script, omsvupgrade, must be used to install OMS-V 2.3 MR1. At the
completion of the execution of the omsvupgrade script, you will be requested
to edit the vsm configuration file, and launch the daemons using ovstart. Full
installation instructions are included in the NTP 241-9501-200, Vector
Software Installation and Commissioning.
Note: Always be sure to use the version of the omsvupgrade script which you
receive with each release since omsvupgrade may change from one release to
another.
Product Software Load
VSS VSS2.3.2_300_98.tar
AS VSS1.1.0_AS10_210_97
OMS-V <to be determined>
MDP mdp10.6

13
Magellan Vector OMS-V 2.3 Release Notes
OMS-V 2.3 MR1 Release Introduction
Table 4: Third Party Product Patch List
Before installing OMS-V, the correct versions of the operating system and HP
OV must be installed. The choice of platform is either Sun MicroSystems or
Hewlett Packard workstations. The following components are required by
OMS-V 2.3 MR1.
• installation of Solaris 2.6 on a Sun workstation, or
• installation of 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
correctly.
• For all installations, the HP-OV installation MUST include patches as
noted in Table 4: on page 13.
Sun Microsystem Platform Considerations
On Sun MicroSystems an operating system upgrade is necessary if using
SunOS as Sun discontinued support for the SunOS operating system 2Q97.
The operating system now provided by Sun on new workstations is Solaris 2.6.
Sun has announced their intent to discontinue the Sparc line of workstations
and replace them with a new Ultra family. Previous Vector system
management releases (VSM 1.1 and VSM 2.0.x) are deployed on the Sparc
line of workstations. It is recommended that the new Ultra line be used for any
new installations due to the marked improvement in performance.
Third Party Product Patches Required Problem Resolved
Installing HP OpenView
5.01 on Solaris 2.6
PSOV-1984 (Date: 16/06/98)
PSOV_02029
Incorrect map display
Year 2000 Xnmgraph y-axis
problem
Upgrading HP OpenView
from 5.0 to 5.01
on Solaris 2.6
PSOV_01790
PSOV-1984 (Date: 16/06/98)
PSOV_02029
incorrect map display.
Installation aborts (ov.version
does not function), xnmgraph
font problem.
Year 2000 Xnmgraph y-axis
problem
Installing HP OpenView
5.01 on HP-UX 10.20
PHSS_15662
PHSS_15076
Year 2000 Xnmgraph y-axis
problem

14
Magellan Vector OMS-V 2.3 Release Notes
Sun Solaris Installation
Some functions on OMS-V use fonts that are not part of the default Solaris
installation. This means that some GUI items in the OMS-V pull-down menus
will not work. (Example - Operation/Switch Control, which controls synching
and swacting of the Vectors). However, these operations can still be performed
through the text-based 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. The operating system now provided by HP and used by OMS-V
release 2.3 MR1 is HP-UX 10.20. If your current operating system is not HP-
UX 10.20, it must first be installed before installing OMS-V release 2.3 MR1.
OMS-V Installation on Hewlett Packard
WARNING! HP-UX 10.20 causes the installation script to abort if the xterm
window is resized during execution of the script. Therefore, please ensure the
xterm window is an appropriate size before invoking the installation script. It
isworthkeepinginmind that thisresizingproblem occurs duringtheexecution
of any shell script.
HP-Openview Considerations
OMS-Vusesthe HP-OpenViewNetworkNode Manager (NNM)fordiscovery
anddisplayof the VectorSwitching Systems inthenetwork.HewlettPackard’s
OpenView release, version HP-OV 5.01, is used by OMS-V 2.3 MR1 for
Vector system management. If your HP-OV version is not 5.01, an upgrade to
HP-OV 5.01 is necessary for OMS-V 2.3 MR1 deployment.
A list of patches, shown in Table4:on page 13,is required for HP OpenView
5.01 installation. Do not install extra patches unless it is advised by HP
OpenView technical personnel.
Further information about the patches, and the files to download can be found
on the World Wide Web at the following address:
http://ovweb.external.hp.com:80/cpe/patches/nnm/nnm.html
If the listed patches in Table 4 can not be obtained, use the latest HP OpenView
5.01 consolidated patches which contain the required patches.
Note: OMS-V 2.3 MR1 release was tested with the patches listed in Table 4.

15
Magellan Vector OMS-V 2.3 Release Notes
VSM to OMS-V Upgrade Strategy Considerations
When selecting workstations for the OMS-V upgrade, Solaris 2.6, HP-UX
10.20, and HP OV 5.01 vendor recommendations should be adhered to. If new
workstations are being utilized for the OMS-V installation, it is suggested that
the original VSM installation be left intact for the duration of the new OMS-V
installation. That way, network management is retained during the upgrade.
If the same workstation must be used, OMS-V upgrade will result in a loss of
management of the Vector switches for a period of time. This is a result of the
requirement to upgrade both the operating system and the HP OpenView
installation. 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”
described in NTP 241-9501-200, Vector Software Installation and
Commissioning. The new installation script, omsvupgrade, should be used to
install OMS-V R2.3 MR1. The omsvupgrade script will remove a previous
OMS-V (but not VSM) installation, provided its version is older than the one
tobeinstalled. PleaserefertoNTP 241-9501-200,Vector Software Installation
and Commissioning for complete details.
To downgrade OMS-V software, un-install OMS-V using the omsvupgrade
script provided with the OMS-V software that is currently installed. Then
Install the previous version of OMS-V software using the omsvupgrade script
that was provided with the previous version of the OMS-V software release.

16
Magellan Vector OMS-V 2.3 Release Notes
Upgrade VSM 1.1.x/2.0 or OMS-V 2.2.x to OMS-V 2.3 MR1
Figure 1 Upgrade OMS-V
1)Maintain at least one working and connected VSM/OMS-V workstation if you want
to continually manage the working network.
2)Identify and isolate a single workstation for upgrade.
- install or upgrade the appropriate operating system, Solaris 2.6 or HP-UX 10.20.
- 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.
4)Upgrade or replace the remaining VSM/OMS-V workstations with OMS-V 2.3 MR1.
Network Mgmt
WAN
VSS 1.1.x VSS 2.x.x
VSM 1.1.x/
1) 2)
3)
OMS-V 2.3 MR1
OS, HP-OV, and OMS-V upgrade
VSM 2.0/
Note: see Table 1 on page 8 for VSS/VSM/
OMS-V compatibilities
OMS-V 2.2.x

17
Magellan Vector OMS-V 2.3 Release Notes
Chapter 3: Resolved Service Requests
OMS-V 2.3 Resolved Service Requests
The OMS-V R2.3 MR1 introduces solutions for the following major customer
impacting SRs.
Table 5: OMS-V 2.3 Resolved Service Requests
10174857 OMS_V was unable to create more than one UPC contract
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.
This problem has been corrected.
10176058 Link Connection Between 2.3 and 2.3 Switches is shown as Uni-
Directional
With using discovery overethernetor qaa1,with2 ormoreIP typesupon VSS,
the Magellan Networks submap displays a bi-directional connection as uni-
directional.
This is solved by using a SPANS address to discover a new link. SPANS signal
paths must be configured to discover new links.
10077699 It takes too long to reflect network changes on VSM Magellan
submap
Some changes in the status of switches or links took more than the configured
polling interval to update, when using default intervals. Improvements to the
discovery process have been made to enhance the speed to reflect network
changes.
SR Number Description
10174857 OMS_V was unable to create more than one UPC contract
10176058 Connection Between 2.3 and 2.3 Switches is shown as Unidirectional
10077699 It takes too long to reflect network changes on VSM Magellan submap.
10174616 Unable to Configure CDAS or AVR From The Front Panel View

18
Magellan Vector OMS-V 2.3 Release Notes
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.

19
Magellan Vector OMS-V 2.3 Release Notes
Chapter 4 Unresolved Service Requests
Unresolved Service Requests
The table below lists all known unresolved high priority Service Requests
Table 6: Unresolved Service Requests
Descriptions of 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 OMS-V Fails to Discover Links With non-qaa0 Up
10171439 conf vcc sh and con vpc sh give error on vmi from host
10131028 Front Panel Alarms Don’t Match Popup
10187107 Problem When Discovering Through Ethernet
10131026 OMS-V 2.2.1 - No Colors Left
Scenario •The problem occurs when opening a front panel display window (selecting a
vectorandopeningfrontpaneldisplay), the users receivesanerrorindicatingno
more colors available in the color map.
Impact •Unintended colours will be used by OMS-V.
Prevention •Minimize the usage of the available colours in the colour map.
Recovery •Reduce the number of applications running on the OMS-V workstation.
10092242 Trace PVC feature does not trace the complete VCC
Scenario •Trace connection feature does not trace the complete virtual connection. After a
virtual connection is established across a network, the trace only shows the
ingress port and the egress port on a single switch.
Impact •The virtual connection across the network is not represented by the trace
feature.
Prevention •None.

20
Magellan Vector OMS-V 2.3 Release Notes
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. A virtual connection across a network can be traced by repeatedly
displaying the connection on single switches.
10176700 Log Hosts utility does not launch from the Networks submap
Scenario •Theloghostsutilitywindowfails to raiseuponbeinglaunchedfromtheMagellan
Networks submap.
Impact •The log hosts utility cannot be launched from the Magellan Networks submap
Prevention •Do not launch the log hosts utility from the Magellan Networks submap. Instead,
launch this utility from the command line.
Recovery •This utility can be successfully launched from the command line. This will be
corrected in a subsequent maintenance release.
10171439 conf vcc sh and con vpc sh give error on vmi from host
Scenario •With many channels configured on the switch the commands “conf vcc sh” and
“conf vpc sh” yielded the error:
?ERROR: floating-point value too large to represent
Impact •This error was not easily recreatable.
Prevention •None.
Recovery •Use VMI on switch.
10131028 Front Panel Alarms Don’t Match Popup
Scenario •On the front panel view, the minor alarm bubble was active (yellow) as expected
indicating that one or more of the minor alarms were active. When the bubble
was clicked to determine which alarm is active in the Alarm control window, all
the alarms showed inactive.
•Clicking update had no effect.
•In VMI, fabric 2 indicated that two minor alarms are active (correct). Fabric 4
indicates no alarms are active (also correct)
Impact •Alarm control window is inconsistent with VMI.
Prevention •Alarms on the front panel need to be checked using the event browser or VMI.
Recovery •Use VMI or the event browser to check the alarms.
10187107 Problem When Discovering Through Ethernet
Scenario •Using discovery through ethernet with ie0, qaa0, and qaa1 up, links were
incorrectly showing red.
•On another workstation, with discovery thru qaa1, links were showing no
problems.
10092242 Trace PVC feature does not trace the complete VCC