2
Magellan Vector 2.0 Release Note, Issue 1.9.1
Revision Record
Issue Date Purpose
1.2 97-04-21 Summarize the Vector 2.0.3 Release
1.3 97-05-28 Summarize the Vector 2.0.4 Release
1.4 97-07-15 Summarize the Maintenance Release for VSS2.0.5
1.5 97-09-30 Summarize the Maintenance Release for VSS2.0.6
1.6 97-11-10 Summarize the Maintenance Release for VSS2.0.7
1.7 97-12-04 Summarize the Maintenance Release for VSM 2.0.5
1.8 98-02-16 Summarize the Maintenance Release for VSM 2.0.6
and VSS 2.0.8
1.9 98-04-17 Summarize the Maintenance Release for VSM 2.0.7
and VSS 2.0.9
1.9.1 98-06-15 Change the upgrade and downgrade procedures for
VSS 2.0.9. Correct the Hardware Summary table.
3
Magellan Vector 2.0 Release Notes, Issue 1.9.1
Table of Contents
5 Revision Record 2
6 Table of Contents 3
7 Chapter 1 Introduction 5
Configuration Supported 5
Functionality Supported 5
New Hardware 5
VSS 6
VSM 6
MDP 7
Documentation 7
New contents in this release 7
Exclusions 7
8 Chapter 2
Release Considerations 8
9 Chapter 3
Service Requests11
Unresolved Service Requests 11
Descriptions of Unresolved Service Requests 11
Solved Service Requests 13
Descriptions of Solved Service Requests 13
10 Chapter 4
Vector documentation 15
NTPs available with this release 15
Installing NTPs online 16
Viewing NTPs 17
Addendum to NTP 241-9501-301 Vector Management Interface User Guide 17
Changes to NTP 241-9501-301 Vector Management Interface User Guide 19
Addendum to NTP 241-9501-301 Vector Management Interface
User Guide 20
Resetting the Network Module 20
Changes to NTP 241-9501- 501 Vector Switch Hardware Maintenance Guide 20
Selecting a MAC address 21
Removing and installing high-speed interconnect (HSI) cables 21
Addendum to NTP 241-9501-301 Vector Management Interface User Guide 24
Addendum to NTP 241-9501-501 Vector Switch Hardware Maintenance Guide 25
Replacing link modules 25
Replacing link select cards 27
5
Magellan Vector 2.0 Release Notes, Issue 1.9.1
Chapter 1
Introduction
These release notes highlight the functionality new to this Vector Maintenance
Release in the areas of Hardware, Vector Switching System (VSS) software,
Vector System Manager (VSM) software, and Magellan Data Provider (MDP)
software.This Maintenance Release provides bug fixes for the Vector Switch
Software (VSS) and the Vector System Manager (VSM) software. See chapter
3 for the list of resolved bug fixes.
Included in these release notes:
• Chapter 1 provides an overview of this document and the product
functionality included or excluded for this release.
• Chapter 2 contains general release considerations.
• Chapter 3 lists all the Service Requests that are resolved and high priority
unresolved Service Requests in this release
• Chapter 4 provides a list of the Vector Release 2.0.X Northern Telecom
Publications (NTPs), the procedure for accessing the Vector installation
document (NTP 241-9501-103), and last minute changes and additions to
the NTPs.
• Appendix A contains Vector Switching System software upgrade and
installation procedure for Release VSS2.0.8 Vector product.
• Appendix B is a summary of the available hardware.
Configuration Supported
• 2.5 or 5.0 Gbit/s Vector switches with the Vector Switching System (VSS)
software
• The Vector System Manager (VSM)
• The Magellan Data Provider (MDP)
Functionality Supported
New Hardware
• Link Module
• Link Selector
• Netmod Extender
• External Synchronization Interface (ESI)
• Back Plane
6
Magellan Vector 2.0 Release Note, Issue 1.9.1
• Power Module
• Fan Unit
• ASX-1000 air filter
• BIP II
VSS • Duplex operation (manual, fault-driven and forced SWACT)
• Vector 1.1 ER6 and Vector 2.0.4 functionality
• Hardware inventory
• ESI DS1 BITS
• ESI Line Timing for OC-3/STM-1, J2, DS3, E3, and OC-12/STM-4
Netmods
• Traps (new hardware and SWACT)
• VMI
• OAM cells for OC12, OC3, DS1, DS3, E1, E3, J2 interfaces
• Mixed i960HA SCP pair and i960CF SCP pair configuration support
• Called Address Screening
• Enhanced Traffic Management
• Enhanced Connection Admission Control (ECAC)
• SVC Failure Cause Counters and Traps
VSM • Vector 1.1 ER6 and Vector 2.0.4 functionality
• Discovery (new hardware)
• Equipment management (new hardware)
• Fault management (new hardware and SWACT)
• Manual and Forced SWACT
• ESI DS1 BITS
• ESI Line Timing for OC-3/STM-1, J2, DS3, E3, and OC-12/STM-4
Netmods
• OAM cells for OC12, OC3, DS1, DS3, E1, E3, J2 interfaces
• VSM-ForeView co-existence
• Called Address Screening
• Enhanced Traffic Management
7
Magellan Vector 2.0 Release Notes, Issue 1.9.1
• Enhanced CAC
• SVC Failure Cause Counters and Traps
MDP • Billing support for fabric redundancy
• Updated BDF formats
Documentation
• Release Notes
• NTPs
New contents in this release
• VSM and VSS bug fixes, see chapter 3.
Exclusions Excluded from this release:
• Thermal below 5OC and above 40OC
Excluded from the product:
• Fore IP and SPANS
• ARP server on switch
8
Magellan Vector 2.0 Release Note, Issue 1.9.1
Chapter 2
Release Considerations
The following table lists the latest compatible releases for the products shown:
Product Release Table
Use the following instructions to load the MDP patch:
1) Log on to the MDP server.
2) Download (copy or ftp) the MDP patch file (P096_01.tar) to the MDP
server.
3) Stop any MDP processing by typing:
/iws/mdp/mdpadm shutdown
4) As root user, extract the fix from the tar file:
tar -xvfp P096_01.tar
The new executables will be propagated to the correct directories.
5) Restart MDP processing by typing:
/iws/mdp/mdpadm restart
The MDP BDF output formats have changed in the MDP R9.6 release. See
the Vector Data Collection System User Guide (NTP-241-9501-320) for
details.
Product Release
VSS (on-switch) VSS2.0.9_130_98.tar
VSM (off-switch) VSM2.0.7_131_HP-UX.tar
VSM2.0.7_131_SunOS.tar
MDP (off-switch) mdp096pai_sp413.tar.01
Following MDP Patch is required:
P096_01.tar
9
Magellan Vector 2.0 Release Notes, Issue 1.9.1
The Vector Release 2.0.X switch does not support ARP Server functionality.
In cases where customers are running ARPSERVER on Vector Release 1.1,
they need to migrate their ARPSERVER configuration onto a host before or
during the upgrade to a Vector 2.0.X network.
Only one ESI module per switch is supported in this release.
The Partial Packet Policing function of the Enhanced Traffic Management
Feature requires the revision J fabric (PEC NTET51AD).
To support a mixed i960CF/HA SCP configuration, you must upgrade the
Vector Switching System (VSS) Software to at least Vector Release 2.0.2. In
the mixed i960CF/HA SCP configuration, each fabric pair must be
configured either with two i960CF SCPs or two i960HA SCPs. As shown in
following figure, the i960CF SCP cannot coexist on the same fabric pair as
the i960HA SCP.
Switch configuration with both i960CF and i960HA processors
The “configuration VCC modify” command is removed in Vector Release
2.0.4 and higher. In order to modify an UPC contract, you must delete the PVC
or PVP and then reprovision the PVC or the PVP with the new UPC contract.
Hot-Swapping (plugging IN and OUT on in-active fabric) the SCP CF
processor card (NTET11AA or ACCA0130-2001 SCP-ASXCF Rev. K/L/M)
can cause permanent damage to the board. The work-around is to remove the
fabric with the SCP card. This problem is resolved in the SCP HA processor
card (that is, NTET11AC).
The ESI card takes 125 seconds to sync to the source. Bellcore standards
indicate that a Stratum 3 clock must lock within 100 seconds.
OR
fabric 1
fabric 2
fabric 3
fabric 4
i960HA SCP
i960HA SCP i960CF SCP
i960CF SCP
active plane
inactive plane
fabric 1
fabric 2
fabric 3
fabric 4
i960CF SCP
i960CF SCP i960HA SCP
i960HA SCP
active plane
inactive plane
10
Magellan Vector 2.0 Release Note, Issue 1.9.1
Customers who are running 2.0.3, 2.0.4 or 2.0.7 and before with pmp or
backplane throughpaths configured must use the upgrade and installation
procedure described in Appendix A.
New firmware for the External Synchronization Card has been introduced
which improves the locking characteristics to the BITS timing source. A
version 9 listed under configuration esi show will be displayed for ESI cards
containing the new updated firmware.
Fast SPVC re-routing in the event of a cable failure has been introduced for
OC3 and J2 Netmods.
The reset command introduced in Vector Release VSS2.0.4 under operation
linkmod has been replaced in VSS2.0.8 with the command operation netmod
reset. This VMI command provides the ability re-initialize the specified
netmod. Note: Invoking this command causes service disruptions to all ports
on the affected netmod.
Users who wish to install or migrate to MDP version 10.3.1 should refer to the
Magellan Data Provider User Guide, NTP 241-6001-309 for installation and
operation instructions. MDP 10.3.1 (version MDP103Pax) requires the Solaris
operating system and application of patch 10.3-14.
11
Magellan Vector 2.0 Release Notes, Issue 1.9.1
Chapter 3
Service Requests
Unresolved Service Requests
The table below lists all unresolved high priority Service Requests (SRs)
found in Vector Release VSS2.0.8 and VSM2.0.6.
Descriptions of Unresolved Service Requests
10126103: pt to mpt connections spanning two or more ports with contract violated.
Violation of contract (exceeding available bandwidth) on point to multi-point
connections that span 2 or more physical ports on the same netmod will result
with traffic being block on outgoing netmod ports and dropping
synchronization (for switches that are in sync) or in-active fabric panic when
the sync command is invoked (for switches out-of-sync). Recovery is to bring
traffic in-line with the contract, reset the affected netmod (operation netmod
reset) and re-sync the switch.
10127209: Traffic did not swact onto the new active linkselect card.
During replacement of the Link Select Card, there is a possibility that the
system may loose connection to the netmod or the netmod may get locked up
resulting in stoppage of all traffic. The avoidance procedure is to use the new
Link Select replacement procedure described in Chapter 4 (Vector
Documentation) of these release notes. Recovery is to reset the netmod using
the VMI command operation netmod reset.
Unresolved Service Requests
SR Number Description
10126103 pt to mpt connections spanning two or more ports with contract
violated.
10127209 Traffic did not swact onto the new active linkselect card
10133471 Unable to modify port bandwidth consistently.
10137752 Switch panic after several hours of MDP connection failures
10139547 All PVCs lost if NM Reset followed immediately by SWACT or
SYNC
10132316 Classical IP connection problem during hardware upgrades
12
Magellan Vector 2.0 Release Note, Issue 1.9.1
10133471: Unable to modify port bandwidth consistently.
This problem is actively being investigated. We believe it is related to Flash
memory fragmentation. Suggested avoidance procedure is to perform an
operation flash free command on flash memory every 4 to 6 weeks. This
ensures large blocks of contiguous memory are available for write operations
into flash.
10137752:Switch panic after several hours of MDP connection failures
One instance of a switch panic due to the MDP being down or an invalid MDP
address specified has been reported from the field. On this occasion, error
messages were displayed on the serial port and SNMP traps generated
(expected) but after 9 hours a switch panic occurred. Addressing the MDP
connection failure will avoid this panic. If this is not possible (MDP
connection problem persists), network operators should disable call recording
until the MDP connection problem is resolved.
10139547: All PVCs lost if NM Reset followed immediately by SWACT or SYNC
There is a possibility that performing a sync or swact operation immediately
after a operation netmod reset or removing, inserting or re-seating a Netmod
may result with all connections that originate/terminate on that netmod being
destroyed. This may result with the active and inactive CDBs being corrupted
or sync failures when call recording is enabled.
Avoidance procedure is to drop sync prior to invoking operation netmod reset
or removing, inserting or re-seating a Netmod then wait 2 minutes before
syncing the switch.
There two recovery procedures available.
For systems with corrupted CDBs, the recovery procedure is to reset the CDB
on the active and inactive, perform a restore with the last valid CDB backup
on the active, then sync the switch.
For systems were there are no missing connections between the active and
inactive CDB’s but the switch will not sync (with call, recording enabled) the
recovery procedure is to disable call records, sync the switch, drop sync,
enable call recording, reboot the active SCP and sync the switch.
Please refer to the Gotcha describing this problem and recovery in more
details.
10132316: Classical IP connection problem during hardware upgrades
There is a possibility that SPANS may become unstable or go down on one or
more switches in the network as a result of upgrading or replacing a hardware
component (i.e. Fabric, Linkmod or Linkeselect). This results in classical IP
13
Magellan Vector 2.0 Release Notes, Issue 1.9.1
connections being intermittent or going down. There are several possible
recovery procedures available. If this problem occurs, please contact GTS for
the appropriate recovery procedure.
Solved Service Requests
The tables below lists solved Customer and Internal Service Requests (SRs)
for the Vector Switch Software (VSS) and the Vector System Manager (VSM).
Solved Service Requests - VSM
Descriptions of Solved Service Requests
10067327:setting date, difference from GMT is 00:00 (VSS)
This fix resolves the problem of not being able to set the timezone. A new
command configuration switch timezone has been added. Previously the date
command contained an offset which was used for this purpose but did not work
correctly.
The new VMI command is;
configuration switch timezone est | cst | mst | pst | akst
where est = eastern standard time, cst = central standard time, mst = mountain
standard time, pst = pacific standard time and alst = alaskan stand time.
The operation date command can still be used to display the current date and
time.
Solved Service Requests - VSS
SR Number Description
10067327 setting date, difference from GMT is 00:00
10136334 When UNI 3.0 signaling is down, it will not autonomously restore.
10139834 Vector SCP stuck in initialized state after loading connectionsdue
to CDB corruption
SR Number Description
10138835 Off switch VMI command conf ecac ecac always fails.
14
Magellan Vector 2.0 Release Note, Issue 1.9.1
10136334: When UNI 3.0 signaling is down, it will not autonomously restore (VSS)
This fix resolves the problem where a 3.0 UNI can be brought into the down
state by changing the mode on a DS3 netmod (i.e. hcs or plcp). When the
mode of the netmod was restored to its original state, the UNI did not restore
itself to the up state. This was because previous versions of VSS2.0 only
attempted to re-establish the UNI once. Network operators had to manually
restart the UNI in question in order to restore it to the up state. Occasionally,
this did not work requiring the UNI to be deleted and recreated to clear the
problem.
In VSS2.0.9, Vector now continuously attempts to re-establish the UNI if it
goes down and carrier is present.
10139834:Vector SCP stuck in initialized state after loading connection
due to CDB corruption (VSS)
This SR (originally included in VSS2.0.7 ER2) is being propagated into
VSS2.0.9. This fix resolves the possibility of CDB corruption when operation
sync is performed. This was observed with customers having very large CDBs.
10138835:Off switch VMI command conf ecac ecac always fails.(VSM)
A solution for this SR introduced in VSM2.0.6 had a problem with it. This
problem has been fixed in VSM2.0.7. This resolves a problem in the VMI with
the configuration ecac ecac commands. Execution of these commands in
previous releases always failed displaying the message “?ERROR: Invalid
command”
The configuration ecac ecac command has been replaced with
configuration ecac For example, what used to be configuration ecac ecac
enable is now configuration ecac enable.
15
Magellan Vector 2.0 Release Notes, Issue 1.9.1
Chapter 4
Vector documentation
This chapter contains information about the Northern Telecom Publications
(NTP) available with this Vector Release. The information in this chapter is
organized as follows:
• NTPs available with this release
• installing NTPs online
• addendums to NTP 241-9501-301, Vector Management Interface User
Guide
• changes to NTP 241-9501-301, Vector Management Interface User Guide
• changes to NTP 241-9501-501, Vector Switch Hardware Maintenance
Guide
Please note that NTP 241-9501-103, 241-9501-301 and 241-9501-501 are
updated for Release 2.0.3. To ensure you have the most recent version, you
can:
• obtain the NTP from the Vector 2.0 hardware shipment
• order the NTP via your usual channels
NTPs available with this release
• NTP 241-9501-010, Vector General Description Guide
• NTP 241-9501-501, Vector Switch Hardware Maintenance Guide
• NTP 241-9501-103, Vector Site Planning and Installation Guide
• NTP 241-9501-301, Vector Management Interface User Guide1
• NTP 241-9501-302, Vector System Manager User Guide
• NTP 241-9501-320, Vector Data Collection System User Guide2
• NTP 241-9501-306, Vector System Manager Error Messages
Note1: The NTP 241-9501-301, Vector Management Interface User Guide is
renamed to NTP 241-9501-301, VMI User Guide for Vector in the paper
version.
16
Magellan Vector 2.0 Release Note, Issue 1.9.1
Note2: The NTP 241-9501-320, Vector Data Collection System User Guide is
available in paper only (that is, not in UniHelp).
Installing NTPs online
1 Login as root on your workstation.
2 Select a UNIX xterm window.
3 Set the read/write permissions by entering the UNIX command
umask 022
4 Enter the cshell operation by entering
csh
5 Create a vector home directory by entering
mkdir -p /usr/nortel/magellan/vector
6 Select a temporary directory for extracting the UniHelp (NTP software)
cd /usr/tmp
7 From the VSM or VSS CD or tape supplied by Nortel, put the VSM or VSS
tar file into /usr/tmp
tar -xvf <device name>
where <device name> for HP platforms is typically /dev/dsk/c201d2s0 for
CD and /dev/rmt0m for tape, or for Sun platforms is typically /dev/sr0 for
CD and /dev/rst<n> for tape, where <n> is a number from 0 through 9.
8 Extract the installation document tar file to the vector home directory
cd /usr/nortel/magellan/vector
tar -xvf /usr/tmp/<tar file>
where <tar file> is sunosdoc.tar for Sun platforms and hpuxdoc.tar for HP
platforms.
17
Magellan Vector 2.0 Release Notes, Issue 1.9.1
Viewing NTPs
1 Change directory to the NTP directory
cd /usr/nortel/magellan/vector/instldoc
2 Run the viewer software by entering
instldoc.run*
The viewer software starts, with the NTP ready to view.
Addendum to NTP 241-9501-301
Vector Management Interface User
Guide
This section provides an addendum to NTP 241-9501-301, Vector
Management Interface User Guide, chapter 6, “VMI Configuration
Commands”, section, “Showing the configuration of the virtual path
connections (VPCs)”.
VMI command configuration vpc obshow displays the overbooking values
associated with permanent virtual paths (PVPs). This command is only
available through the Vector management interface (VMI). The only VSM
access to this command is through a telnet session to VMI.
The command configuration vpc obshow displays the overbooking values
used by the system to calculate the equivalent bandwidth for both originating/
terminating paths and through paths.
configuration vpc obshow [<port>] [<vpi>]
For example, to view the overbooking values of all PVPs, type:
localhost::> configuration vpc obshow
Input Output
Port VPI Port VPI VBROB BuffOB
4D2 0 terminate N/A N/A
18
Magellan Vector 2.0 Release Note, Issue 1.9.1
4E2 0 terminate N/A N/A
4E3 0 terminate N/A N/A
4E4 0 terminate N/A N/A
4CTL 0 terminate N/A N/A
originate 4D2 0 100 100
originate 4E2 0 100 100
originate 4E3 0 100 100
originate 4E4 0 100 100
originate 4CTL 0 100 100
4B1 33 4B2 33 200 100
4B2 33 4B1 33 400 100
Notice the two through paths (last two row entries in the example), which
report having VBR bandwidth overbooking (VBROB) values of 200 and 400
respectively and VBR output buffer overbooking (BuffOB) values of 100 and
100.
For a more concise report to display all through paths with an input port and a
virtual path identifier (VPI), for example, port 4B1 and VPI 33:
localhost::> configuration vpc obshow 4B1 33
Input Output
Port VPI Port VPI VBROB BuffOB
4B1 33 4B2 33 200 100
To display all through paths from an input port, for example, port 4B2:
localhost::> configuration vpc obshow 4B2
Input Output
Port VPI Port VPI VBROB BuffOB
4B2 33 4B1 33 400 100
19
Magellan Vector 2.0 Release Notes, Issue 1.9.1
Changes to NTP 241-9501-301
Vector Management Interface User
Guide
This section provides changes to the NTP 241-9501-301, Vector Management
Interface User Guide, chapter 4, “Connection admission control for SVCs”,
section, “Aggregate maximum bandwidth for all switched virtual circuits”,
page 82, must be read as follows:
For each Quality of Service (QoS) setting, bandwidth added to the aggregate
SVC maximum bandwidth is as follows:
• for a CBR SVC connection, its peak cell rate (PCR) is counted in this
parameter
• for a VBR SVC connection, its “equivalent bandwidth” is counted in this
parameter
• for a UBR SVC connection, its representative bandwidth is counted in this
parameter
• this aggregate bandwidth must be larger than the maximum bandwidth
parameter for each SVC
• the aggregate SVC maximum bandwidth can be provisioned a different
value for each of the users-to-network and network-to-user directions
• the pre-configured maximum aggregate bandwidth for all the SVCs is
compared against:
equivalent bandwidth of the connection to be
admitted (in case of a UBR connection, it will
equal the corresponding UBR representative
bandwidth) + Bandwidth currently consumed by all
SVC connections (in case of a UBR connection, each
SVC connection will consume 3 cells per second) +
number of active UBR connections on the fabric *
UBR representative bandwidth
If the maximum pre-configured aggregate bandwidth is reached or
exceeded no additional SVCs can be admitted.
20
Magellan Vector 2.0 Release Note, Issue 1.9.1
Addendum to NTP 241-9501-301 Vector Management Interface
User Guide This section provides information for a new feature that is not documented
in NTP 241-9501-301, Vector Management Interface User Guide,
Chapter 11, “VMI operation commands,” page 293.
Resetting the Network Module
Vector 2.0.8 and higher supports the ability to reset a network module.
Caution: Invoking this command causes service disruptions to all ports on
the affected netmod.
To reset the network module, enter the command netmod reset at the level
operation:
operation netmod reset <module>
where:
module is the link module (A to D) you want to reset.
For example:
localhost::> operation netmod reset B
resets and initializes netmod B.
Once the command is invoked, VMI displays the following message:
Resetting the network module will destroy all
existing connections which are already
configured on the network module.
Reset Network Module - B - [n]?
Enter y (yes) to reset the network module or enter n (no) or press
<Return> to cancel the reset. The default is no.
Changes to NTP 241-9501- 501
Vector Switch Hardware Maintenance
Guide
This section contains the following procedures: selecting a MAC address,
removing an HSI cable and installing an HSI cable.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/
