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