7.0.11

Passport 6400

Release Notes for P7.0.11

Software Release Name: P7.0.11

Software Version Name: BG00SBB

Software Release Date: March 28th, 2003

Distribution: General Availability

WARNING: The data herein are not to be used or disclosed without the consent of Nortel Networks. This note is aworking paper intended for limited circulation and discussion. No departmental or corporate approval or commitment isimplied, unless such approval or commitment is expressly given in a covering document.

Copyright © 2001 Nortel NetworksAll rights reserved

2


3

Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Who should read this document and why . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9What you need to know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2 Upgrading from previous releases . . . . . . . . . . . . . . . . . . . . . . . . 11Required hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Passport 6400 mimimum hardware vintage . . . . . . . . . . . . . . . . . . . . . . . . . . . 11ATM IP cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Year 2000 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Century Compliant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Passport’s Century Compliance Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Changes to Passport Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Migration to a PCR release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17MPANL DLCI-0 Restart functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 New features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 19Summary of Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Quality levels for this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

List of new features and feature enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 22Base features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Passport Vport Robustness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22NS Switch on Degrade Product Improvement . . . . . . . . . . . . . . . . . . . . . . . . . 22FPGA Management System (PP804) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24CTR.4 E1C Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24CP Ethernet Local Connect (PP1081) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Display Banner Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

BTDS/HTDS features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25BTDS/HTDS on 8-port DS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4400 Interworking features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 25MPANL DLCI-0 Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

IP features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28IP Configurable Route Preference (CD1220) . . . . . . . . . . . . . . . . . . . . . . . . . 28

LAN features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29BGP4 Enhancements (PP787) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Virtual Router Redundancy Protocol (VRRP) (PP901) . . . . . . . . . . . . . . . . . . 30Passport CP Switchover for ILS WAN Services (PP225) . . . . . . . . . . . . . . . . 30Passport IP Class of Service (CoS) (PP742, PP848) . . . . . . . . . . . . . . . . . . . 31IP Multicast (PP855) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31SNA Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Mobile Interworking features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 32


4

Voice features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32VNET Signalling Gateway Stage 1 (PP902) . . . . . . . . . . . . . . . . . . . . . . . . . . 32MVPE G.729A Voice Encoding (PP868) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32MPVE V.17 Fax Relay at 14.4 and 12.0 kbit/s (PP868) . . . . . . . . . . . . . . . . . . 33VNET Call Redirection (PP885) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Voice Networking Blind Digit Manipulation (PP1099) . . . . . . . . . . . . . . . . . . . 33MPA Voice Accounting Interworking (PP1269) . . . . . . . . . . . . . . . . . . . . . . . . 33MPANL SPO-mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34MVPe support for SG3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ATM features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Passport ATM IP FP Introduction (PP504) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34ATM Virtual UNI (PP669) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37ATM Enhanced Statistics (PP796) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Product enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37HEC Error Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37NetBios/IPX Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 4 Release Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Guidelines for open issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41PM1 FPs memory engineering considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Memory usage rule for PM1s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Before migrating software levels on PM1 FPs . . . . . . . . . . . . . . . . . . . . . . . . . 42

Support Discontinued of 8 Mbyte CQC based ATM FPs (PDC1.0) . . . . . . . . . . . 43Inter-LAN Switching (ILS) Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

RFC1490 Bridged Frame Routing Considerations . . . . . . . . . . . . . . . . . . . . . 44Multiple Virtual Routers (MVR) Considerations . . . . . . . . . . . . . . . . . . . . . . . . 44ILS on ATM FP CQC Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

ATM Multiprotocol Encapsulation (ATM MPE) Considerations . . . . . . . . . . . . . . . 44IP Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45IPX Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45IP Multicast Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45OSPF Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46IP CoS Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Bridging Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53NetSentry Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54CP Crash: NetSentry clusterbridge filter configuration . . . . . . . . . . . . . . . . . . 55

BGP-4 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Base Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

BCS Broadcast Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58No check prov warning of TR/DS1V/E1V port reset . . . . . . . . . . . . . . . . . . . . 58

MPANL Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59MPANL SPO Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59PNNI on Passport release 7.0.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

PORS considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Configuring optional manual paths for a PLC . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 5 Release Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63


5

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Helmsman-based CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Replacing CQC-Based ATM FP’s with ATM IP FP’s . . . . . . . . . . . . . . . . . . . . . . 64Changing card type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Changes for Lp/n Arc Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Changes for Atmif ConnMap Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Changes for Atmif/x Ca Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Changes for Atmif/x Vcc Vcd and Atmif/x Vpc Vpd Components . . . . . . . . . . 65

Installation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65ILS startup introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Support Discontinued of 8 Mbyte CQC-based ATM FPs (PDC1.0) . . . . . . . . . 65Component Administration System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Benign Recoverable Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Express Manager support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Preside Multiservice Data Manager (formerly known as NMS) support . . . . . . 67Preside Multiservice Data Manager (formerly known as NMS) connectivity using IpiFr

67SNMP agent considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67SNMP standard MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68SNMP Enterprise MIB considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68SNMP rolled up variable considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Multiple services per shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Maximum supported feature set per shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Multiple applications per function processor . . . . . . . . . . . . . . . . . . . . . . . . . . 73Function Processor sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Agent queue size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75PORS Mux mode directly connected to a first generation ATM FP . . . . . . . . . 75PORS Map mode on ATM IP FP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76ATM IP FP - first generation ATM FP Interwork . . . . . . . . . . . . . . . . . . . . . . . . 76PORS Degrade Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Frame Relay engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Frame Relay Trace engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77IpiVc and IpiFr coexistence engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Use of standby CP during software migration . . . . . . . . . . . . . . . . . . . . . . . . . 78Spooled files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Base Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Unsupported card types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Hitless CP switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79CAS congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80CP crash caused by LCM,GCM and RemoteCallAgent using all msg block . . 80


6

Manual Loopback Test on E1C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80V.54/PN127 Loopbacks on DS1C/E1C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Processor memory fragmentation issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Bus Clock Source status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Trunks, DPN gateways and networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Management Data Provider support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Loadsharing engineering considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81PORS LRC checking updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Full trunk statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81ATM port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82MCS considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Frame Relay migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83FRF.5 2K Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Rapid Start/Stop of DLCI loopback causes card reset . . . . . . . . . . . . . . . . . . . 83Frame Relay Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84FR-ATM Gateway with Virtual Framer and LP sparing . . . . . . . . . . . . . . . . . . 84FR-ATM now requires atmNetworking to be in Sw Avl avList . . . . . . . . . . . . . 84FRF.5 and ATM traffic management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Data Loopback with Resiliency ‘A bit’ condition . . . . . . . . . . . . . . . . . . . . . . . . 84Frame Relay over EuroISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

ILS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85IP CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86IMA migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86IMA-specific enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86ATM processor operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Maximum ATM connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Maximum number of ATM test and loop components . . . . . . . . . . . . . . . . . . . 87OC-3 Multi Mode Optic Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87ATM Trunk Utilization Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888 port DS1/E1 ATM card independent and IMA links . . . . . . . . . . . . . . . . . . . . 88Port Sparing of 4 ports or less on 8-port DS1/E1 IMA cards . . . . . . . . . . . . . . 89ATM Resource Control (ARC) migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90ARU reporting section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Changes to the Atmif transmit queue limit defaults . . . . . . . . . . . . . . . . . . . . . 91Queue Limit Software Errors in 7.0 against OC3MM-CQC . . . . . . . . . . . . . . . 913pDS/E1A to 8pDS/E1A card migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913pE1A to 8pE1A Linetype migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ATM Function Processor crashes after CPSO and LP switchover . . . . . . . . . 92Virtual Path Termination (VPT) Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93ATM SPVC accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93ATM Cell Transfer display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Provisioning of subConnectionPool and lnnConnectionPool on ATM cards . . 94

ATM Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94


7

Passport ILMI not UNI 3.0/3.1 compliant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Provisioning SPVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Reserved channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95SPVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Changes in the IEs for the service categories for all SPVC interfaces . . . . . . 96ATM signalling channel failure on IMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96ATM accounting for N-PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Provisioning permanent VCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Private Network to Network Interface (PNNI) . . . . . . . . . . . . . . . . . . . . . . . . . 96ILS on ATMIP FP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

AAL1 Circuit Emulation Service (CES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Changing the txQueueLimit with AAL1 CES connections active . . . . . . . . . . . 98CES over PORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98New bandwidth limits for 4p E1 and DS1 AAL1 cards . . . . . . . . . . . . . . . . . . . 98

Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Voice Networking Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99MVPE G.729A Voice Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100MVPE V.17 Fax Relay at 14.4 and 12.0 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . 100Provisioning Voice Networking - relay encoding minimum rate . . . . . . . . . . . 100MCDN Anti-tromboning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Appendix AKnown Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Appendix BResolved Limitations since last release. . . . . . . . . . . . . . . . . . . 104

Appendix CItems Resolved in Previous Releases . . . . . . . . . . . . . . . . . . . . 110Items Resolved in the P7.0 (BG00A) Release . . . . . . . . . . . . . . . . . . . . . . . . . . 110Items Resolved in the P7.0.1 (BG00S1A) Release . . . . . . . . . . . . . . . . . . . . . . 111Items Resolved in the P7.0.2 (BG00S2B) Release . . . . . . . . . . . . . . . . . . . . . . 115Items Resolved in the P7.0.3 (BG00S3A) Release . . . . . . . . . . . . . . . . . . . . . . 116Items Resolved in the P7.0.4 (BG00S4C) Release . . . . . . . . . . . . . . . . . . . . . . 118Items Resolved in the P7.0.5 (BG00S5A) Release . . . . . . . . . . . . . . . . . . . . . . 119Items Resolved in the P7.0.6 (BG00S6A) Release . . . . . . . . . . . . . . . . . . . . . . 120Items Resolved in the P7.0.7 (BG00S7B) Release . . . . . . . . . . . . . . . . . . . . . . 120Items Resolved in the P7.0.8 (BG00S8B) Release . . . . . . . . . . . . . . . . . . . . . . 123Items Resolved in the P7.0.9 (BG00S9A) Release . . . . . . . . . . . . . . . . . . . . . . 125Items Resolved in the P7.0.10 (BG00SAB) Release . . . . . . . . . . . . . . . . . . . . . 126

Appendix DDocumentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132NTP 241-6401-805 PP6400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134


8


9

ware

n0

are

lf

e notesare

port

on

Chapter 1Introduction

This document provides essential information about the Passport 6400 softload you have received.

The following topics are discussed in this section:

• “Who should read this document and why” (page 9)• “What you need to know” (page 9)• “How this document is organized” (page 9)• “Related documents” (page 10)

Who should read this document and whyYou should read this document if you are a planner, engineer or craftspersoresponsible for accepting, testing or deploying the associated Passport 640software load.

This document provides information about the content of the associated softwload, the status of previously open software issues, and the installationrequirements, if any. You should review the information to familiarize yoursewith new features and functionality.

Please ensure that you have read and understood the contents of the releasand are aware of your devices specific capabilities prior to installing this softwrelease to eliminate or minimize potential service interruption.

What you need to knowYou must be familiar with Passport 6400 software installation procedures.Courses are available.

How this document is organizedThis document is focused on the new content in the current release of Pass6400 software. The document includes the following chapters:

• Chapter 2, “Upgrading from previous releases”, provides basic informatiabout the R7.0.11 software level.

Release Notes for R7.0.11

10 Chapter 1 Introduction

lved

ious

ve

ave

issee

• Chapter 3, “New features and enhancements”, provides a summary newfeatures and enhancements that are introduced in Release 7.0.

• Chapter 4, “Release Considerations”, provides information about unresoissues and problems.

• Chapter 5, “Release Planning” provides information about planningdeployment of R7.0.11

Appendices provide detailed information about the current release and prevreleases:

• “Appendix A: Known Limitations” provides information about problemsfound in this release or previous releases which are not yet resolved.

• “Appendix B: Resolved Limitations since last release” lists the CRs that habeen resolved since the last release.

• “Appendix C: Items Resolved in Previous Releases” lists the CRs that hbeen resolved in previous releases.

Related documentsA number of Nortel Network publications (NTP’s) are available to support threlease. For detailed information about the NTP’s that apply to this release,“Documentation” (page 63)


Chapter 2 Upgrading from previous releases 11

are

Chapter 2Upgrading from previous releases

This chapter provides basic information about the R7.0.11 (BG00SBB) softwlevel. This chapter contains the following sections:

• “Required hardware” (page 11)

• “Upgrade overview” (page 15)

• “Year 2000 Information” (page 16)

• “Migration to a PCR release” (page 17)

Required hardwarePassport 6400 mimimum hardware vintage

Table 1 provides information for minimum supported hardware for Passport6400 FPs.

Table 1Minimum supported hardware for Passport 6400

CP/FPProcessorType

Card name longversion

Card nameshort version

Minimumvintagelevel (PECcode)a

Hardware information

CP Control processor CP NTFN33AANTNN01AANTNQ01AA

PM2, SBIC, SCSI disk, 64 MbytePM2, SBIC, EIDE disk, 64 MbytePM2, SBIC, EIDE disk, 64 Mbyte

CFP1 Control and FunctionProcessor 1

CFP1 NTFP61AANTNN02AA

PM2, SBIC, EIDE disk, 64 MybtePM2, SBIC, EIDE disk, 64 Mybte

ATM 2-port JT2 ATMfunction processor

2pJ6MAtm NTNN53AANTNQ53AANTFP58CA

PDC1.1, CQC, 16 MbytePDC1.1, CQC, 16 MbytePDC1.1, CQC, 16 Mbyte

ATM 3-port DS1 ATMfunction processor

3pDS1Atm NTFP30CANTNN45AANTNQ45AA

PDC 1.1, CQC, 16 MbytePDC 1.1, CQC, 16 MbytePDC 1.1, CQC, 16 Mbyte


3pDS3Atm NTNN51AANTNQ51AANTFP18EA


ATM 3-port E1 ATMfunction processor

3pE1Atm NTNN46AANTNQ46AANTFP32CA



3pE3Atm NTNN52AANTNQ52AANTFP17EA



12 Chapter 2 Upgrading from previous releases

ATM 3-port OC-3 multi-mode ATM functionprocessor

3pOC3MmAtm NTNN54AANTNQ54AANTFP16EA


ATM 3-port OC-3 single-mode ATM functionprocessor

3pOC3SmAtm NTNN55AANTNQ55AANTFP38DA

PDC1.1, CQC, 16MbytePDC1.1, CQC, 16 MbytePDC1.1, CQC, 16 Mbyte

ATM 4-port DS1 AAL1function processor

4pDS1Aal1 NTNN47AANTNQ47AANTFP80BA


ATM 4-port E1AAL1function processor

4pE1Aal1 NTNN48AANTNQ48AANTFP82BA



8pDS1Atm NTNQ49AANTNN49AANTFN14CA



8pE1Atm NTNN50AANTNQ50AANTFN16CA

PDC1.1, CQC, 16MbytePDC1.1, CQC, 16 MbytePDC1.1, CQC, 16 Mbyte

ATM IP 2-port OC-3 ATM IPfunction processor

2pOC3MmAtm2 NTNQ65AANTNN65AANTJS07CA

PPC, PQC, AQM, 64 MbytePPC, PQC, AQM, 64 MbytePPC, PQC, AQM, 64 Mbyte

ATM IP 2-port OC-3 ATM IPfunction processor

2pOC3SmAtm2 NTJS09CANTNN66AANTNQ66AA

PPC, PQC 1, AQM, 64 MbytePPC, PQC 2, AQM, 64 MbytePPC, PQC 2, AQM, 64 Mbyte

ATM IP 3-port DS3 ATM IPfunction processor

3pDS3Atm2 NTNN68AANTNQ68AANTJS13CA

PPC, PQC, AQM, 64MbytePPC, PQC, AQM, 64 MbytePPC, PQC, AQM, 64 Mbyte

ATM IP 3-port E3 ATM IPfunction processor

3pE3Atm2 NTNQ67AANTNN67AANTJS11CA

PPC, PQC, AQM, 64 MbytePPC, PQC, AQM, 64 MbytePPC, PQC, AQM, 64 Mbyte

FR 1-port DS3C functionprocessor

1pDS3C NTNN26AANTNQ26AANTFP67AANtBP40AA

PM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM1, SBIC, 8Mbyte

FR 8-port DS1 functionprocessor

8pDS1 NTNN16AANTNQ16AANTFN56AANTFP56AA

PM2, SBIC, 16MbytePM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8Mbyte

Table 1Minimum supported hardware for Passport 6400 (Continued)

CP/FPProcessorType








DS1 (4pDS1) NTNN14AANTNQ14AANTFN47AANTBP19DA

PM2, SBIC, 16MbytePM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8 Mbyte

FR 4-port DS1Chfunction processor

DS1C (4pDS1Ch) NTNN17AANTNN18AANTNN19AANTNQ19AANTNQ17AANTNQ18AANTFN52AANTFL04AANTJS43AANTBP88AB

PM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 64 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 64 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 64 MbytePM1, SBIC, 8 Mybte


DS3 (1pDS3) NTNN23AANTNQ23AANTNN24AANTNQ24AANTFN50AANTFN71AANTBP40AA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8 Mybte

FR 4-port E1 functionprocessor

E1 (4pE1) NTNN15AANTNQ15AANTFN48AANTBP21EA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8 Mybte

FR 4-port E1Ch functionprocessor

E1C (4pE1Ch) NTNQ20AANTNN20AANTNQ21AANTNN21AANTNQ22AANTNN22AANTFN57AANTFK01AANTJS46BANTBP90AA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM2, SBIC, 64 MbytePM2, SBIC, 64 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 64 MbytePM1, SBIC, 8 Mybte

FR 1- port E3 functionprocessor

E3 (1pE3) NTNQ25AANTNN25AANTFN51AANTBP71AB

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8 Mybte

FR 1-port HSSI functionprocessor

HSSI NTNQ27AANTNN27AANTFN58AANTFP04AA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8 Mbyte


CP/FPProcessorType







FR 8-port V.11 functionprocessor

V11 (8pV11) NTNQ12AANTNN12AANTNQ13AANTNN13AANTFN45AANTFN49AANTBP38EA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM1, SBIC, 8Mbyte

FR 8-port V.35 functionprocessor

V35 (8pV35) NTNQ10AANTNN10AANTNQ11AANTNN11AANTFN46AANTFN73AANTBP16DA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM2, SBIC, 32 MbytePM2, SBIC, 16 MbytePM2, SBIC, 32 MbytePM1, SBIC, 8 Mbyte

ILS 2-port ethernet100BaseT functionprocessor

2pEth100BaseT NTJS02BANTNN37AANTNQ37AA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM2, SBIC, 16 Mbyte

ILS 6-port ethernet10BaseT functionprocessor

6pEth10BaseT NTNQ36AANTNN36AANTBP82CANTFN59AA

PM2, SBIC, 16 MbytePM2, SBIC, 16 MbytePM1, SBIC, 8 MbytePM2, SBIC, 16 Mbyte

ILS 1-port FDDI multi-mode functionprocessor

1pFddiMultiMode NTFN61AANTFN39AANTBP76EC


ILS 1-port FDDI single-mode functionprocessor

1pFddiSingleModeNTFN60AANTNN40AANTBP92EA


ILS 4-port Token Ringfunction processor

4pTokenRing NTFN42BANTNN35AANTBP78DA


ILS ILS Forwarderfunction processor

IlsForwarder NTNQ38AANTNN38AANTFN18AB


Voice 1-port DS1 MVPfunction processor

1pDS1Mvp NTFN62AB PM2, SBIC, MVP, 16 Mbyte

Voice 1-port DS1 MVP-Efunction processor

1pDS1Mvpe NTNQ85AANTNN85AANTJS40BA

PM2, SBIC, 16 Mbyte, EcanPM2, SBIC, 16 Mbyte, EcanPM2, SBIC, 16 Mbyte, Ecan

Voice 1-port DS1 voicefunction processor

1pDS1V NTFP41AB PM1, SBIC, 6 DSP


CP/FPProcessorType







ard

e

are

R7.0 soft-

ATM IP cardsNote: The "Required Hardware Release Levels" table for the newlyintroduced ATM IP cards, has been temporarily removed to update the ccodes. For further information please contact your Nortel NetworksRepresentative.

Upgrade overviewThe releases from which an upgrade to Release R7.0.11 is supported are:

• all P7.0 releases

• all P5.1 releases

Consult with Nortel Networks Technical Support before upgrading from anunsupported level.

Take note of specific feature related considerations documented in “ReleasPlanning” (page 63).

Software compatibilityTable 2 (page 16) shows the minimum Preside Multiservice Data Manager(formerly known as NMS), MDP, Express Manager, DPN, and PP4400 softwlevels required for Passport compatibility.

Voice 1-port E1 MVPfunction processor

1pE1Mvp NTFN20BANTFN20CA

PM2, SBIC, 32 MbytePM2, SBIC, 16 Mbyte

Voice 1-port E1MVP-Efunction processor

1pE1Mvpe NTNQ86AANTNN86AANTJS35BA


Voice 1-port E1 voicefunction processor

1pE1V NTFP43AB PM1, SBIC, 6 DSP

Voice 1-port TTC2M MVPfunction processor

1pTTC2mMvp NTFN64AA PM2, SBIC, MVP, 16 Mbyte

Voice 1-port TTC2M MVPEfunction processor

1pTTC2mMvpe NTNQ87AANTNN87AANTJS38BA


a. NTNQ PEC codes are replacing older PEC codes. The hardware remains the same. Only the new FPs can be ordered.ware supports both the old and new PEC codes.


CP/FPProcessorType







ss for

ofto

etelct tonceaits

d in

ble toility

:

Year 2000 InformationCentury Compliance, as defined in the next paragraph, is Passport’s readinethe Year 2000.

Century Compliant“Century Compliant” means that the specified product functions until the endits warranty period without any material, service affecting non-conformancethe applicable Nortel Networks product specification with respect to theoperations performed by such product which are date dependent. This is truprovided that the specified software load or release, if any, identified by NorNetworks (including any associated hardware), has been installed with respesuch product; and further provided that the use of such product is in conformawith the associated user documentation. Do not interpret the statement thatproduct is Century Compliant as a commitment to support a product beyondcommitted support window.

As used in this document, “Year 2000 Readiness”, “Year 2000 ready”, andsimilar phrases mean that these products are “Century Compliant” as definethe preceding paragraph.

Passport’s Century Compliance PositionPassport was conceived and designed as a Year 2000-ready product, to be aproperly process and display 4-digit years as part of a more important capab– accurate date-processing before, during and after the Year 2000. Since itsintroduction, Passport has been able to fulfill key Year 2000 requirements in

• Managing dates in data manipulation

• Calculating and identifying leap years

• Managing Julian dates

• Computing intervals, scheduling events, and maintaining day-of-weektimekeeping

Readiness was integrated into the software for transition without hardwareupgrade.

Table 2Preside Multiservice Data Manager (formerly known as NMS), MDP, Express Manager, DPN andPP4400 Software Compatibility

Passport R7.0.11(BG00SBB)

Preside Multiservice Data Manager MDM 13.4 Solaris

MDP MDP 13.4

Express Manager Express Manager 4.2

DPN-100AM/RM

G37.1.0

PP4400 R4.0



se,PCRted

a

/

Changes to Passport InterfacesPassport interfaces have not changed.

Further InformationFor further information, please contact your Nortel Networks accountrepresentative.

Migration to a PCR releaseTo prevent any subsequent migration issues when migrating to a PCR releacustomers are advised to migrate their VCI numbers above the value of 32.streams discourage the use of VCI numbers below 32. Also, VCI 1 is restricin 7.0 as the meta-signaling protocol is not supported.

MPANL DLCI-0 Restart functionalityTo maintain MPANL DLCI-0 Restart functionality, it is required to migrate toS/W load that supports the new feature (migration to S/W loads that do notsupport MPANL DLCI-0 Restart will result in loss of this functionality).

At time of writing, this feature is planned for availability in the following loadsSSUPs (please consult the release notes prior to migration):

• 7.0.11• PCR4.2.2• PCR5.2 CA load


Chapter 3 New features and enhancements 19

re

Chapter 3New features and enhancements

This chapter provides information about features and enhancements that aintroduced with Release R7.0.11 (BG00SBB). This chapter contains thefollowing sections:

• “Summary of Features” (page 20)• “List of new features and feature enhancements” (page 22)• “Base features and enhancements” (page 22)• “4400 Interworking features and enhancements” (page 25)• “LAN features and enhancements” (page 29)• “Mobile Interworking features and enhancements” (page 32)• “Voice features and enhancements” (page 32)• “ATM features and enhancements” (page 34)• “IP features and enhancements” (page 28)• “BTDS/HTDS features and enhancements” (page 25)


20 Chapter 3 New features and enhancements

se

ity,

er of

:

.

Summary of FeaturesQuality levels for this Release

Different aspects of this release are available at different quality levels. Thelevels are defined as follows:

• Alpha - Software is still under development; not all functional tests havebeen completed; some unexpected behaviour can occur.This functionalityis not supported.

• Beta - All functional testing has been completed, but stress, interoperabiland performance testing is still in progress.This functionality is supportedfor pre-authorized trials only. Contact your Nortel Networksrepresentative.

• Controlled Release- All functional, stress, interoperability and performanctesting has been completed. Functionality is available to a limited numbecustomer sites to provide expanded in-service testing prior to GA.Thisfunctionality is supported for pre-authorized customers only. Contactyour Nortel Networks representative.

• General Availability (GA) - All internal and external (customer lab andnetwork) testing has been completed; and feature load is generallydeployable.This functionality is supported.

Release 7.0The following table summarizes the features introduced within this Release

Table 3 New Features in this ReleaseFeature Release 7.0 Release

7.0.10Release7.0.11

ATM IP FP Introduction (PP504) GA GA GAATM VP Termination Phase 2 (PP604) GA GA GAATM Virtual UNI (PP669) GA GA GAATM Enhanced Statistics (PP796) N/A Controlled

ReleaseControlled

ReleaseFRF.8 NPVC Scalability (PP567) GA GA GABGP4 Enhancements (PP787) GA GA GACP Switchover for ILS WAN Services(PP225)

GA GA GA

CP Ethernet Local Connect (PP1081) N/A GA GADisplay Banner Message N/A GA GAATM VPT Management (PP793) GA GA GAFPGA Management (PP804) GA GA GAVNET SIgnalling Gateway Stage 1(PP902)

GA GA GA

MVPE G.729A Voice Encoding (PP868) GA GA GAMVPE V.17 Fax Relay at 14.4 and 12kbits/s (PP868)

GA GA GA

Voice Networking Blind DigitManipulation (PP1099)

N/A GA GA

Mpa Voice Accounting Interworking(PP1269)

N/A GA GA

HotHaus DSP on MVPE (PP868) GA GA GA



ATMMPE on ATM IP FP(IP, MVR, Netsentry)

GA GA GA

VRRP-100BaseT Ethernet/Token Ring(PP901)

GA GA GA

IP CoS (PP742, PP848) Beta GA GAE1C CTR-4 ISDN Compliance (PP818) N/A GA GAIP Multicast (PP855) N/A GA GAPORS Adaptive Routing (PP520) Alpha Controlled

ReleaseControlled

ReleaseATMMPE on ATM IP FP (PP698)(IPX, Bridging)

Alpha GA GA

VNS over ATM Trunks on ATM IP FP(PP827)

Alpha GA GA

VNET Call Redirection (PP885) N/A GA GAATM IP Part 3 (ABR) (PP771) Alpha Alpha AlphaHEC Error Sensitivity N/A GA GANetBios/IPX Filtering N/A GA GAMPANL SPO-mux N/A GA GAConfigurable Route Preference(CD1220)

N/A ControlledRelease

ControlledRelease

SNA Load Balancing N/A GA GABTDS/HTDS on 8 port DS1 N/A Beta BetaMVPe support for SG3 N/A N/A GAMPANL DLCI-0 Restart N/A N/A GA

Table 3 New Features in this Release (Continued)Feature Release 7.0 Release

7.0.10Release7.0.11



-Mb/s-7.

eds

ased

theaiS

hertfor

y orthen

List of new features and feature enhancementsThe following features and enhancements are new in Release 7.0:

• “FPGA Management System (PP804)” (page 24)• “BGP4 Enhancements (PP787)” (page 29)• “Virtual Router Redundancy Protocol (VRRP) (PP901)” (page 30)• “Passport CP Switchover for ILS WAN Services (PP225)” (page 30)• “Passport IP Class of Service (CoS) (PP742, PP848)” (page 31)• “VNET Signalling Gateway Stage 1 (PP902)” (page 32)• “MVPE G.729A Voice Encoding (PP868)” (page 32)• “MPVE V.17 Fax Relay at 14.4 and 12.0 kbit/s (PP868)” (page 33)• “Passport ATM IP FP Introduction (PP504)” (page 34)• “MPA Voice Accounting Interworking (PP1269)” (page 33)• “MPANL SPO-mux” (page 34)• “MPANL DLCI-0 Restart” (page 25)• “MVPe support for SG3” (page 34)• “IP Configurable Route Preference (CD1220)” (page 28)• “SNA Load Balancing” (page 32)• “BTDS/HTDS on 8-port DS1” on page 25

Base features and enhancementsPassport Vport Robustness

The V35/V11 provides for an extended range of line speed but only for a predetermined set of values. This feature adds the new 1.024 Mb/s and 2.048line speed capability to all the ports of a specified group; ports 1-4 or ports 5

Note: It is not recommended to provision the new speeds among old spewithin a group.

NS Switch on Degrade Product ImprovementOverviewPassport provides a provisionable Network Clock Synchronization(NS)component for selecting the ports to be used as part of the network clockingscheme. Up to 3 reference sources can be provisioned (primaryReference,secondaryReference, and tertiaryReference). The NS Switch On DegradeFeature adds new attributes to govern the behavior of the NS component bon the port (physical layer) availability status.

Current ImplementationThe common port management software normally interacts with the NS ondetection of major alarm conditions (los, lof, ais, rai, idle (ds3), mflof (e1), mfr(e1), rfi (oc3) and port hw failure) and having detected such will inform the Non the CP of the change in the port state and deregister itself. If the port is tcurrently active reference, then the NS on the CP will initiate a reference poswitch. The primaryReference attribute will be considered first as a referencethe NS component. If this port fails due to a major alarm the NS componentautomatically initiates a change from the primary reference to the secondartertiary reference. When the primary reference errored condition has cleared



luehehe

e of

ingrt

methe

nce

ce.ce

ack

eriodncence

ice

Cards

evel.s thesed

the NS component will revert back to the reference port as specified by theprimaryReference attribute.The Passport hardware has the ability to detect the errored condition AIS (balarm). The framer hardware having detected the AIS condition will trigger tgeneration of a minor alarm by the port management software. Along with tminor alarm, the port management software may also generate anavailabilityStatus of degrade on the port (CAS> display Lp/x port/xavailabilityStatus).

Product ImprovementThe Passport NS AutoSwitch On Degrade Feature now adds the ability toperform a change in clock reference based on the availabilityStatus attributthe port, of ATM cards, going to a degraded state.If this feature is enabled and having detected the degrade state, the portmanagement software will now inform the NS process on the CP that it is goto deregister itself. As before, NS will then initiate a switch if the reporting pohappens to be the currently active reference port.The following attributes now control the NS component :set ns primaryReference lp/x port/xset ns secondaryReference lp/x port/xset ns tertiaryReference lp/x port/xset ns switchOnDegrade [ enabled | disabled ] // newset ns revertiveSwitch [ manual | auto ] // newset ns revertiveTime 5-120 // new - minutesIf the switchOnDegrade = disabled then the NS component will have the sabehavior as described above (Current Implementation) and will not react toport's degrade availability status.If the switchOnDegrade = enabled then the NS component will change referedue to the port's availability status going to a degrade condition.If the switchOnDegrade = enabled and the revertiveSwitch = manual, thenoperator intervention is required to switch the NS back to the primaryReferenThis is accomplished by performing a lock and unlock of the primary referenport, provided that the degraded port condition has cleared.If the autoSwitch = enabled and the revertiveSwitch = auto, then reverting bto the primaryReference will happen automatically provided that theprimaryReference degrade condition has cleared and remains stable for a pof time as specified by the revertiveTime attribute. A lock and unlock sequeon the primaryReference will bypass the revertive time and cause the refereswitch over to happen immediately. The lock and unlock will disrupt any servthat is currently running on the port.

Target CardsThe changes of this product improvement will target the Passport ATM (CQBased) cards. This feature does not pertain to the frame based cards, LAN cor features that generate an availability status of degrade at the application lThe frame and LAN based cards currently do not have the same behavior acell based cards. That is, the current implementation of the frame and LAN bahardware drivers do not generate a degrade availability state.



ithep

ash

R_4.d_4lly

nss

o be

n

rnetPP30

Provisioning ChangesThe following three new attributes are added to the NS component :set ns switchOnDegrade [ enabled | disabled ] // default = disabledset ns revertiveSwitch [ manual | auto ] // default = manualset ns revertiveTime 5-120 // default = 5 minutes)

FPGA Management System (PP804)Automated FPGA Download provides the following benefits:

• Improved FPGA management allows the latest FPGA files to be shipped wthe hardware, customers no longer need to wait for an SSUP and can keusing existing software when the IM has changed.

• Interface Module (IM) Flash complements the Processor Module (PM) Flby increasing the available Flash storage for future use

• Decreasing the number of FPGA file

• Decreasing the software downloading time

CTR.4 E1C InterfaceThe CTR.4 E1C Interface feature extends the E1C capabilities to include CTcompliance; thus, enabling the E1C to interface directly with ISDN networksPreviously, the E1C Functional Processor (FP) was available in standard anpremium formats. Now, a new 64M channelized E1C card known as the CTRcompliant format is available and provides ETSI CTR 4 compliance, specificafor remote alarm indication (RAI).

The premium E1C format is aimed for high capacity Frame Relay applicatiowhile the CTR_4 compliant format is primarily for connecting to ISDN networkin Europe. Features available on previous versions of the E1C will continue tsupported on this new FP.

In summary, this feature provides:

• a new 64M E1C FP

• new driver software to control the layer 1 hardware device

• changes to layer 1 alarm handling with respect to remote alarm indicatio(RAI) for ETS 300 011 compliance

• modification to provisionable attributes to selectively enable and disablehardware control of RAI.

CP Ethernet Local Connect (PP1081)This feature integrates the following capabilities with respect to the CP etheport on the Passport 6K. This feature is supported on the PP160, PP50, andwith PM2 CP.

1 Support for telnet to the locally attached Passport node.

2 Support for FTP file transfer to/from the locally attached Passport node.



ed

ote“in

s onNMSon

l of

tly,

omy

8-

f as

sL

4400.

onontI-0

3 Support for SNMP connectivity to the SNMP agent(s) on the locally attachPassport. Thisfeature will not support SNMP connectivity to remotepassports through a Passport network.

This feature does not provide remote network management connectivity. Remconnectivity refers to the ability to manage other passport equipment throughband” communication.

THIS FEATURE DOES NOT PROVIDE ANY PROTECTION AGAINST CONGESTIONWHEN CONNECTED TO A LOCAL LAN.

Display Banner MessageOn successful login (via a local session or telnet session) the contents of/system/motd will be displayed to the user. Since there is no editor that runa Passport switch, this implies that the banner message is composed on theworkstation. The composed message is then FTP'd to the /system/motd filethe Passport.

If the /system/motd file does not exist, a banner is not displayed, so removathe /system/motd file will remove the banner message from the system.

BTDS/HTDS features and enhancementsBTDS/HTDS on 8-port DS1

This feature provides BTDS and HTDS function on the 8-port DS1 FP. Currenthe BTDS and HTDS services are supported on the 4 port DS1 FP.

From a service functionality perspective (BTDS/HTDS), there is no change frwhat was provided on the 4-port DS1 FP. The services behave the same wawhether running on a 4-port or an 8-port card.

The 8-port DS1 PM1 FPs (NTFP56xx) do not support this functionality. Theport DS1 PM2 FPs (NTFN56xx) support up to 4 ports of BTDS/HTDS

4400 Interworking features and enhancementsMPANL DLCI-0 Restart

The feature has been implemented with MPANL DLCI-0 Restart disabled/ofthe default setting (current behaviour, no DLCI-0 Restart is sent byPassport 6400/Passport 7400) to ensure compatibility with existing network(specifically PP4120/DPN networks, which are incompatible with the MPANDLCI-0 Restart feature). If required, the feature is enabled by provisioningmpa/1 sig restartReqTimerwith not zero value. MPANL DLCI-0 Restart, anoptional procedure specified in Q.933, has been implemented to addressinteroperability issues between Passport 6400/Passport 7400 and Passport

This procedure is different from restart on DLCI-16. Mpanl restart procedureDLCI-16 affects only Mpanl SignalingMpanl component, Restart procedureDLCI-0 affects only Mpanl Signaling. This restart procedure on DLCI-0 is nodependent on DLCI-16 Restart, as DLCI-16 restart is not dependent on DLCrestart.



d by

ltlt

ent

.

in

The restart procedure is used by an MPANL dte or dce to return the MPANLSignaling dte/dce interface to its default settings. The restart procedure is usean MPANL dte or dce to recover from internal failure, after power-up, upondetection of DLCI-0 LAPF recovery, or after internal re-initialization. As a resuof the execution of Restart procedure on DLCI-0, DLCI-0 returns to its defausettings, meaning all SVCs are cleared.

Restart Request Information Element

Figure: Restart Request Information Element

The Restart Request IE is composed of a single octet. The information elemindicates that the sender wishes to initiate a restart on the interface.

This information element can be signaled from either the MPANL dte or dce

The information carried in this IE has a per-interface context.

Restart Acknowledgement Information Element

Figure: Restart Acknowledgement Information Element

The Restart Acknowledgment IE is composed of a single octet.

This information element can be signaled from either the MPANL dte or dceresponse to a restart request IE.

The information carried in this IE has a per-interface context.

8 7 6 5 4 3 2 1

Restart Request IE identifier

1 0 0 0 0 0 0 0

8 7 6 5 4 3 2 1

Restart Acknowledgement IE identifier

1 0 0 0 0 0 0 1

octet 1

octet 1



T

Inndernt.

d.

ce ar that

New AlarmsAlarm 7007 8100

Legend<instance> = a decimal value

Details

This alarm is generated at the Mpanl after two attempts to send a RESTARmessage to the adjacent Passport 4400 fail to result in a response with aRESTART ACKNOWLEDGE message. A restart request is sent out undercertain conditions. This alarm is required for the interface to realize thatattempts to synchronize the adjacent MPA have not been acknowledged.compliance with procedures for restarts defined in the X.76 standard, the seof the restart request can consider its interface available for use at this poiHowever, since no response indicates a possible lack of synchronizationbetween the two passports, this warning is provided.

Probable cause

Type

Remedial actionEnsure that all switched DLCIs on the adjacent Passport 4400 are release

Alarm 7007 8101


DetailsThis alarm is generated when the Mpanl is being requested to restart. SinRESTART message can be received at any time, this alarm notifies the usethe Mpanl is being requested to restart by the adjacent MPA.

Probable cause

Type

Remedial actionNo action required.

Component Severity StatusMpanl/<instance> Sig minor message




tifiesRTits

start

t themerthe

rnalRTthe

ingvaluesgofle.

Alarm 7007 8102


DetailsThis alarm is generated when the Mpanl is being restarted. This alarm nothe user that the Mpanl is being restarted after receiving a RESTAACKNOWLEDGE message from the adjacent MPA, in response toRESTART message. This alarm also indicates completion of the reprocedure.

Probable cause

Type


Alarm 7007 8103


DetailsThis alarm is generated as a warning that the T317 timer has expired withouMpanl receiving indication that the internal clearing has been completed. TiT317 is started when the Mpanl receives a RESTART message fromadjacent MPA, and it enters the Restart state. The indication of the inteclearing prompts the Mpanl to stop the T317 timer and send a RESTAACKNOWLEDGE message to the adjacent MPA, thereby completingrestart procedure.

Probable cause

Type


IP features and enhancementsIP Configurable Route Preference (CD1220)

This feature allows for the provisioning of the routing preference on a per routprotocol basis. In Passport each route is assigned a route preference. Theseare currently hard coded (0 through 255) using defined constants per routinprotocol. The preference is used by the routing manager as the first criteriachoosing which route to install from the routing table into the forwarding tab





, byrredte)

oded

e ofg

ing

in

nder

sport

of

entstart.

For BGP, it also allows changing the routing preference on a per peer basissetting the corresponding Import policy's preference attributes to more prefevalues. This could prove useful when the same routes (including default rouare learned through more than one peer.

The default preference values used in this feature preserve the former hard cones(see the attribute description below).

Benefit of the feature:

• Added flexibility in the network configuration

• More control over which protocol to use to run traffic

• Can be used to migrate from one routing protocol to another

The feature is based on the current Passport IP Routing Protocolsimplementation. The feature does not check the sanity of the preferencechanging. This means that it should be done with caution and the knowledgwhat effects it may have. The feature has been implemented for the followinrouting protocols: BGP, OSPF, RIP & Static Routing Protocol.

LAN features and enhancementsBGP4 Enhancements (PP787)

This feature enhances the existing Passport BGP-4 functionality in the followways:

• supports the Community Path attribute and acts accordingly as specifiedRFC1997

• selects a route based on the Path Attributes As Path and Communities uimport and export policy

• supports the Route Reflection function as specified in RFC1966

• alters the AS weight by inserting a dummy AS to the path attribute

Feature limitationsHardwareThere have been some issues noticed during the testing of BGP on the Pas6000 which may affect customer network design. Primarily these have beenaround:

1 The amount of time required to bring up a BGP session with a peer.

2 The amount of time required to exchange a routing table over this BGP session.

The BGP implementation on Passport 6000 is excellent for a small numberBGP routes. Please plan your network designs accordingly.

Special requirementsThis enhancement does not have any special requirements. This enhancemtakes effect immediately after software load and does not require a system re



ofN.

P

on.the

n

ng

FP

ded

N

tely

Release informationThis feature is introduced with Release 7.0.

Virtual Router Redundancy Protocol (VRRP) (PP901)The Virtual Router Redundancy Protocol (VRRP) provides dynamic electiona VRRP virtual router (called Master) among a group of VRRP routers on a LAThe elected Master is responsible for forwarding traffic for IP addressescontrolled by the VRRP virtual router. If the elected Master router fails, VRRwill elect from the group a new Master to take over responsibility. VRRPeliminates the single point of failure inherent in the static default routerenvironment.

VRRP specifies an election protocol to provide the VRRP virtual router functiAll protocol messaging is performed using IP multicast datagrams, allowingprotocol to operate over a multi-access LAN supporting IP multicast.

Feature limitationsOnly supported on Token Ring and 100BaseT ethernet FP’s.

HardwareThis feature has no hardware requirements.

Special requirementsThis feature has no special requirements. VRRP takes effect immediately osoftware load and does not require a system restart.


Passport CP Switchover for ILS WAN Services (PP225)The Passport CP Switchover for ILS WAN Services feature offers the followiadvantages:

• reduces the outage of ILS WAN services during a CP switchover (by thereload time)

• eliminates outage on WAN services that support hitless switchover proviall features on the card support it (otherwise an FP reset takes place)

• allows scheduled CP switchover with less impact

Feature limitationsThis feature has no specific feature limitations.

HardwareAll features loaded on cards must support hitless switchover to prevent WAservice outages.

Special requirementsThis feature has no special requirements. This feature takes effect immediaon software load and does not require a system restart.



its:

ed

ce

n

entstart.

ch

PIM-es


Passport IP Class of Service (CoS) (PP742, PP848)The Passport IP CoS with Release 7.0 feature provides the following benef

• provides IP CoS differentiation on the following media:

— Ethernet (10BaseT/100BaseT)

— Token Ring

— ATMMPE

— FRDTE

— PPP

— FDDI

• lets IP CoS operate within an ATM core network

• provides expedited forwarding of specified traffic over VC and non VC basmedia

• provides support for IP virtual private networks (VPN) by carrying CoSacross Virtual Media and IP Tunnels

• classification of traffic at four different levels on a per protocol port interfaor virtual router (VR) basis

• customer policy based class of service traffic prioritizing to define missiocritical traffic

• supports ToS based interoperation with other devices including flexiblesetting of the ToS field, including the DiffServ Code Point

Feature limitationsThis feature has no specific feature limitations.

HardwareThis feature has no hardware requirements.

Special requirementsThis enhancement does not have any special requirements. This enhancemtakes effect immediately after software load and does not require a system re


IP Multicast (PP855)Multicast provides the infrastructure for many new networking applications suas distance learning, software distribution and multimedia transmissions.IPMulticast on Passport uses Protocol Independent Multicast - Sparse Mode (SM) to efficiently route multicast traffic to multiple individual host that may bsparsely distributed over a wide area. PIM-SM multicast routing protocol wa



nedse

hefor

N

tivemeall

ing

d

uildsch

ase.

eed

s.

m

developed by an Internet Engineering Task Force working group and is defiin RFC 2362 . This feature is designed to restrict multicast traffic to only thorouters with locally attached receivers or downstream routers interested inreceiving this traffic, thereby minimizing the impact on network resources. Tlocally attached receivers can join a group to receive multicast traffic destinedthat group. The receiver can also leave the group to stop receiving trafficdestined for that group.

SNA Load BalancingThis feature provides a load balancing functionality across a Token Ring LAwhere the multiple MAC addresses exist.

The main benefit of this feature is that it provides an equal loading of the aclink stations on a token ring LAN where there are multiple devices with the saMAC address. The load balancing has the capacity of finding all the routes tothe devices with the same MAC address. In order to do this the load balancbuilds up its own table to keep all the routing information. This table isreconstructed periodically, in this way any malfunction is noticed and learnevery fast.

The functionality of this feature is based on the Local Device Monitoring(LDEV) which must be provisioned. The LDEV sends periodically "pingframes" to a given MAC address, the same MAC address on which LoadBalancing should be applied. Based on the responses, the load balancing bits own table identifying the MAC address and the routing information to reathat address. The limitation of this feature is that it can only provide loadbalancing functionality to one MAC address reachable via mulitple routes.

Mobile Interworking features and enhancementsThere are no new Mobile Interworking features or enhancements in this rele

Voice features and enhancementsVNET Signalling Gateway Stage 1 (PP902)

VNET Signalling provides the following benefits:

• Improves voice quality by eliminating tandem hops.

• Cost savings by eliminating the gateway PBX. Since no need for tandemPBX’s

• Cost savings by eliminating redundant voice FP’s. Since we no longer nlinks to gateway PBX’s, the Passport 6400 hardware connected to thegateway PBX can be re-assigned

• Ease of management, by making the network more simple

This feature is currently available for 6400-6400 and 6400-4400 application

MVPE G.729A Voice Encoding (PP868)This is a more efficient implementation of the G.729 voice encoding algorithon MVPE



eIG,

tegS

erthe

togM/

ouproup

rlap

he

tede.

the

kort

PAated

MPVE V.17 Fax Relay at 14.4 and 12.0 kbit/s (PP868)This feature allows customers to take full advantage of higher speed faxtransmission while keeping bandwidth utilization low.

VNET Call Redirection (PP885)VNET Call Redirection feature will allow VNET calls to be placed to alternatvoice routes (Vroute(s)) regardless of the protocol being used (CAS, ETSI QSMCDN etc..), in the case of load sharing, node failure, or original voice routefailure.

This feature will make Voice Networking more robust by allowing calls to routo a Hunt Group Server (HgS). A call to a Passport HgS DNA is sent to the Hwhich chooses an eligible Hunt Group Member (HgM) DNA from the listavailable. If this eligible HgM DNA can accept the incoming call, the call will bconnected. Otherwise, the next eligible DNA member of the list is chosen fohunting until the list has been exhausted. The choice of the HgM depends onsearch mode and the HgM_s availability. To activate this feature provision adirectory number in the VNCS to route to the HgS. The call will be presentedthe hunt group server. The hunt group server will then select a destination HVroute based on the algorithm selected and the HgM provisioned.

Feature limitationsThe PP4400 will not work with this feature. The PP4400 cannot be a hunt grmember for a given hunt group server. However the PP4400 can call a hunt gserver and a member will be selected for the call to complete on.

Voice Networking Blind Digit Manipulation (PP1099)This feature provides blind digit manipulation for the called number only. Nomanipulation is done to calling or connected numbers. Both en bloc and ovedialing types are supported.

The calling and connected numbers remain unchanged in order to ensure treliability of the accounting records. Only a single message carries the digitinformation values (the SETUP for the calling number, and typically theCONNECT for the connected party number). Changing the calling or connecnumbers makes accounting records unreliable, and makes billing inaccurat

MPA Voice Accounting Interworking (PP1269)The voice accounting on Passport interacts with peer voice services acrossPassport network for single-ended or double-ended accounting recordgeneration. The Passport Voice services that support a common subnetworinterface for accounting includes MPA voice accounting (MVA), legacy PasspVoice services, and Multipurpose Voice Platform (MVP).

The functionality provided by this feature is:

• MVA source end accounting - When voice accounting is enabled on the Mconnected Passport switch then voice call accounting records are generfor calls originating from MPA.



the

ds

oicef a

teingL-

n

NLays

ls

m

tesity

elay400-

• MVA terminating end accounting - When voice accounting is enabled onMPA connected Passport switch and the provisionedTerminatingEndRecords flag is enabled then voice call accounting recorare generated for calls terminating at MPA.

• Double ended accounting - Exchange of voice call reference informationexchanged between the MPA connected Passport switch and the peer vswitch allows correlation of accounting records generated at each end ovoice call when voice accounting is enabled.

MPANL SPO-muxThis feature is an enhancement to the MPANL over PORS feature. MPANLSPO(Short Path Oriented) feature stabilizes the connection between RemoServer Agent (RSA) and Remote Server Interface (4400 and 6400) by splittthe negotiation of maxFrameSize for the Mpanl connection and for the MPANPORS connection. This feature also corrects the issue with frame padding iPORS for Mpanl when SpoMux is needed.

The end 4400 user has better control over the connection type used for MPAvoice calls. This leads to better quality of voice calls since voice quality is alwbetter when using an SPO-mux mode connection.

Prior to this feature, MPANL voice calls were always transported over eitherAAL5 mux or map mode connections. This feature allows MPANL voice calto be transported over Spo mux as well .

MPANL SPO connections are possible (specific to voice or video traffic) if acircuit of this type is properly provisioned. If not properly provisioned the systedefaults to AAL5. The frame size for this virtual circuit will be 45 bytes,regardless of the frame size signaled by the MPA side.

Note: This feature allows better control of the quality of the voice call.

MVPe support for SG3This change is to enable the completion of SG3 fax calls at the supported raprovided by V.17, V.29 and V.27ter (ie. 14.4 kbps and lower). This functionaldoes not support the V.34 standard but rather simply allows SG3 calls todownspeed to supported G3 rates.

The downspeeding of SG3 fax calls to G3 rates is only supported in the faxRmode. The completion of SG3 fax calls at G3 rates is also supported in a 46400 interworking scenario.

ATM features and enhancementsPassport ATM IP FP Introduction (PP504)

ATM IP Functional ProcessorsFour new Function Processors (FP) are supported by the feature:

• 2-Port OC3 SM

• 2-Port OC3 MM

• 3-Port DS3



ided

all

g

n

ral

nd

on

so

vice

• 3-Port E3

ATM IP Functional Processors are intended for use in the followingenvironments:

• enterprise broadband networks using customer located or customer provPassport switches

• full interworking with public carrier networks providing access services oftypes, new and legacy, and trunking

ATM IP FP’s are compatible with existing ATM systems.

The new ATM IP Functional Processors provide:

• high performance adaptation for Frame Relay, IP and existing networkin

• superior traffic management capabilities

• high-density multi-service access for the carrier FR and ATM market

• full interworking with CQC based ATM FPs, allowing a smooth introductioto existing networks

• a platform for ATM Forum traffic management phase 4 (TM4.0) and geneTM improvements

• improved scalability for permanent connections, switched connections, asubconnections

• line rate frame forwarding (up to 155.520 Mbit/s per port on OC-3 FP’s)all ports for the following applications:

— Frame Relay (FRF.5 and FRF.8)

— DPRS-MCS (over ATM) end point

— PORS-Trunk Map Mode end point

• increased frame forwarding rates for the following applications:

— DPRS-MCS (over PORS) end point and Tandem forwarding

— DPRS-Trunk end point and Tandem forwarding

— PORS-Trunk AAL5 Mux Mode end point and Tandem forwarding

— PORS-Trunk AALSPO Mux Mode end point and Tandem forwarding

• connection mapping improvements:

— no ConnMap component is required for ATM IP FP’s. (ConnMap is alremoved for 8-port DS1 and E1 ATM FP’s.)

— the entire VPI-VCI space is available for use

— removal of separation of the VPI-VCI space into regions reserved forVPCs and regions reserved for VCCs

— support for the NNI cell header with full 12 bit VPI

• increased FP main memory, reducing memory related restrictions on sermixtures



r IP

es:

e on

:

37).

• support for the following interfaces:

— SONET (STS-3c)

— SDH (STM-1)

— DS3

— E3

• Virtual Path Termination of various forms

• ILS software support, assisted by an hardware forwarding engine thatprovides a substantial performance increase (that is, a faster line rate foforwarding)

• standards compliant SONET 1+1 linear APS (line protection) that provid

— unidirectional and bidirectional switching

— revertive and nonrevertive switching

• straight forward migration from first generation based ATM FP to ATM IPFP for most situations

Feature LimitationsNot all the existing Passport software capabilities are supported in this releasthe ATM IP FP’s. Supported capabilities include:

• ATM networking• DPRS networking• PORS networking• ATM Bearer Service, including Point-to-Multipoint SVCs• CES transport• FRF.8• FRF.5-MCS• VPT• VUNI• ILS Bridging• VNS• IPX

The capabilities that are not supported include:

• LANE• ILS Tunneling

HardwareThe ATM IP Functional Processor feature introduces the following hardware

• 2-Port OC3 SM• 2-Port OC3 MM• 3-Port DS3• 3-Port E3

For a block diagram of the new ATM IP OC-3 FP cards, see Table 3 (page



I),

aVP.

foreTM

l oftione

Clow

ATM IP OC-3 Single Mode FP & ATM IP OC-3 Multi-Mode FP hardware

Special requirementsNone

ATM Virtual UNI (PP669)The Passport ATM Virtual UNI feature provides multiple virtual interfaces onone physical port. A virtual interface can be a User-to-Network Interface (UNan Interim Inter-switch Signalling Protocol (IISP), or a Private Network-to-Network Interface (PNNI). Each virtual UNI, IISP, or PNNI is associated withPVP, and has its own signalling channel which can set up SVCs within that P

In this way, the Passport ATM Virtual UNI feature provides SVC tunnelingthrough a PVP network.

ATM Enhanced Statistics (PP796)The ATM Spooled Statistics feature generates spooled statistics informationboth ATM interfaces and Virtual Path Terminators(VPTs) on Passport. Thesstatistics allow network engineers to gather data regarding the utilization of Aresources within a Passport network.

Product enhancementsHEC Error Sensitivity

IntroductionCurrent implemetation of software allows for the possibility of excessive leveHeader Error Count being received without shutting down the port. This situahas the potential to cause a degradation of service. The change will allow thoperator to provision the delay timings between the receipt of 7 or more HEerrors and the raise of alarm to the minimum (1 ms). The changes will also al

backplane

port 0

port 1

APSswitch

SUNI-DUAL

AQM

MPC750processor

OpticalLine I/f

OpticalLine I/f

AQM

PQC

PQC

ABC

ABC

CQM

CQM CQM

CQMSDRAM



rorsort

DD

y is

leDad,ly,the

the

to

50d

aly

bynce

tiveht

alfay

tionew.isH/W

the operator to provision an HEC error threshold. If the accumulated HEC erover provisionable intervals are greater or equal to the threshold, then the pwill be shut down.

Current ImplementationRight now the receipt of 7 or more consecutive HEC errors results in an OCanomaly. It will take a minimum of 6 consecutive good cells to remove this OCanomaly. A LCD situation arises when the OCD state stays for the presetmilliseconds (Right now the delay between OCD anomaly and LCD anomalnot provisionable. It is preset to 50 ms for DS1Atm and E1Atm, 2.5 ms forDS3Atm and E3Atm). If the LCD situation stays for the currently provisionabdelay (attribute alarmActDelay range 0-2000ms, default 500ms), then an LCalarm is generated and the port is shut down. However, when link quality is bHEC errors could be received in patterns that will not result in an LCD anomabut will cause a degradation of service. After the LCD anomaly is disserted,port will return to service after about 9.5 seconds.

Proposed SolutionThe first part of the Product Improvement will enable an operator to provisiontiming between OCD and LCD. If the timing between OCD to LCD and thetiming between LCD to alarm are provisioned to the minimum, the sensitivitythe receipt of 7 or more consecutive HEC errors will be maximized. The newprovisionable attribute lcdStateDelay will range approximately between 1 toms for DS1Atm and E1Atm cards (default 50 ms), 1 to 5 ms for DS3Atm anE1Atm cards (default 3 ms).In order to be able to provision the timing between the clearing of LCD anom(and uncorrectableHecErrors dropping down to half of provisionedhecErrorLimit, see below) and the port returning to service, an additionalprovisionable attribute clearDelay will be created. The attribute will rangebetween 0 to 60 minutes (default 0).The second part of the solution will monitor the HEC error level, as definedthe existing operating attribute uncorrectableHecErrors for direct mapping. Othe uncorrectableHecErrors level is above hecErrorLimit (new provisionableattribute) over hecSampleInterval (new provisionable attribute) for consecuhecErrorIntervalLimit , then the lcdAlarm will be issued and the port be brougdown. This Product Improvement does not create any new message/alarm.

RecoveryAfter the port is down, the LCD condition is monitored continuously:1 If there is no LCD asserted and if uncorrectableHecErrors drops below h

of hecErrorLimit over hecSampleInterval seconds for the entire clearDelperiod, then a clear alarm is to be issued and the port comes up.

2. 2.If LCD is asserted, then present LCD implementation (the implementaexisting before this Product Improvement) will take precedence over the nhecErrorLimit/hecErrorSampleInterval/hecErrorIntervalLimit mechanism

This means uncorrectableHecErrors will not be monitored until LCD defectcleared (uncorrectableHecErrors can not be monitored anyway because oflimitation). After LCD defect is cleared, if uncorrectableHecErrors is below



formes

ttheill

dingeen

tive

l is 0,ned

The0

eedrrorrval

rt is

hecErrorLimit over hecSampleInterval seconds and there is no LCD defectsthe entire clearDelay period, then a clear lcdAlarm is issued and the port coup.

Target CardsThe changes of this product improvement will target all E1Atm, E3Atm,DS1Atm and DS3Atm cards. It will not target J6Matm cards. It will not targeOC3Atm cards because the hardware used in these cards does not providecapability to set the timing between OCD anomaly and LCD anomaly. Nor wthe changes target AAL cards because such cards do not contain atmcellcomponent.

CDL ChangesThere will be four new provisionable attributes, all under the atmcellsubcomponent (none of these attributes are applicable to J6MAtm, OC3Atmcards or any others cards). All OSI state information remains the same.

lcdStateDelay (range 1 to 50 ms or 1 to 5 ms, default 50 ms or 3 ms, depenon the type of card used) - new parameter that will determine the timing betwentering OCD anomaly and moving to LCD anomaly.

clearDelay (range 0-60 minutes, default 0 ms) - new parameter that willdetermine the minimum elapsed time before the port is allowed to return to acservice after uncorrectableHecErrors is below half of hecErrorLimit and LCDanomaly absent continuously for the specified time. When the value is thedefault, the clearDelay time is actually 9.5 seconds ± 0.5 seconds.

hecSampleInterval (range 0-25 seconds, default 0) When hecSampleIntervathe mechanism of using uncorrectableHecErrors to bring down the port is turoff and hecErrorLimit will be ignored. When hecSampleInterval is n seconds(where 1 <= n <= 25) if the accumulative hecErrorLimit within n seconds isgreater than the provisioned hecErrorLimit the sample interval is considerederrored. If the number of consecutive errored intervals reacheshecErrorIntervalLimit an LCD alarm is declared and the port is disabled.

hecErrorLimit (range 1-250000 uncorrectableHecErrors for DS3/E3, default250000; range 1-10000 uncorrectableHecErrors for DS1/E1, default 10000)default numbers represent roughly 25% error rate of the link capacity over 1seconds (see the previous new provisionable attribute).The lower the provisioned value, the less uncorrectableHecErrors it would nto bring down the port. This attribute specifies the error threshold for a HEC esampling interval. When the number of uncorrectableHeaderErrors in an inteof hecSampleInterval seconds is greater than or equal to hecErrorLimit, thesample interval is considered errored. If the number of consecutive erroredintervals reaches hecErrorIntervalLimit an LCD alarm is declared and the podisabled.



on

atd.

hecErrorIntervalLimit (range 1-25, default 1). This attribute specifies the limitthe number of consecutive errored HEC sampling intervals. WhenhecErrorIntervalLimit consecutive HEC error sampling intervals each haveleast hecErrorLimit errors, an LCD alarm is declared and the port is disable

NetBios/IPX FilteringThis product enhancement allows the PP6400 IPX router to filter the IPXNetBIOS packets.


Chapter 4 Release Considerations 41

his

s or

rearyingease

Chapter 4Release Considerations

This chapter provides information about unresolved issues and problems. Tchapter contains the following sections:

• “Guidelines for open issues” (page 41)

• “Inter-LAN Switching (ILS) Considerations” (page 44)

• “Base Considerations” (page 58)

Guidelines for open issuesThis section provides information that may help you work around some issueproblems related to identified but unresolved SR’s. Workarounds are notavailable for all SR’s. For more information, contact your Nortel Networksrepresentative.

PM1 FPs memory engineering considerationsThe PM1-based function processors (FPs) listed in Table 4 were ManufactuDiscontinued in September 1998, and their hardware support ended in Janu2002. However, software support for these FPs continues in R7.0.11, followthe Passport Evergreen Software Policy, with the constraints listed in this relconsideration.

Table 4PEC codes for affected PM1 FPs

Unchannelized PM1FPs PEC code

V.11 8-port V11 NTBP38xx

V.35 8-port V35 NTBP16xx

DS1 4-port DS1 FR NTBP19xx

DS1 8-port DS1 FR NTFP56xx

DS3 1-port DS3 FR NTBP40xx

E1 4-port E1 FR NTFP21xx

E3 1-port E3 FR NTBP71xx

HSSI 1-port HSSI NTFP04xx

Channelized PM1 FPs

DS1C 4-port DS1ch FR NTBP88xx

E1C 1-port E1ch FR NTBP90xx


42 Chapter 4 Release Considerations

oryrould

the

nnythe

ngript

Memory usage rule for PM1sTo determine if a PM1 FP is currently running a supported configuration:

1) Display the current memory usage on the PM1 FP, using the command:d lp/<n> memoryUsage

2) Add the displayed RAM values (all in kbytes) for fastRam + normalRam +sharedRam

3) In order to be supported, the sum must be under these limits:Unchannelized PM1 FPs: fastRam + normalRam + sharedRam = 8100 kbytesChannelized PM1 FPs: fastRam + normalRam + sharedRam = 14500 kbytes

FPs using more memory than this may load up and run, but are at risk of memexhaustion when traffic bursts or other transient events occur, or if a patch oSSUP is loaded at a later date. So any PM1 FPs that exceed these limits shbe reconfigured or replaced with a PM2 FP. PM2 FPs have 16 Mbyte or 32Mbyte.

In addition to more memory, PM2s have double the throughput of PM1s,

Before migrating software levels on PM1 FPsBefore migrating any nodes with PM1 FPs, consider whether the increasedmemory consumption of the target release level will push the PM1 FPs overabove limits.

This can be easily forecast as shown below. It is critical to do this calculatiolong before the planned migration night, to allow time to order and deploy arequired replacement FPs. Otherwise some PM1 FPs may fail to load aftermigration, leaving end-users out of service.

Note that the procedure below is based on the percent growth, release overrelease, for PM1 software packages as shown in Table 5.

1) Display the current (before migrating) memory usage on the PM1 FP, usithe command below. If there are many PM1 FPs in the network, an MDM sccould be used to repeat the command for every one.d lp/<n> memoryUsage

2) Add the displayed RAM values (all in kbytes) for fastRam + normalRam +sharedRam

Table 5Percent memory growth on PM1 FPs

migration hop: R5.1 -> R7.0.11

% memory growth: 10%



as

ith

6

nd

3) Compare the sum to the limit for your current (before migrating) release,shown in Table 6

4) All PM1 FPs exceeding these limits should be reconfigured or replaced wPM2 FPs before migrating.

Support Discontinued of 8 Mbyte CQC based ATM FPs (PDC1.0)There is insufficient memory on all 8 Mbyte CQC based ATM FPs to providereliable operation in R7.0.11. These FPs must be replaced either with the 1Mbyte version of the same FP, or with an ATM IP FP prior to migrating toR7.0.11.

These FPs are listed in the following table:

Note:8 Mbyte CQC FPs were Manufacture Discontinued in May 1998, ahardware supported ended in January 2002.

Table 6Maximum memory usage allowed on PM1 at R5.1

Fast+Normal+Shared memory usage limit (in kbytes) fromR5.1 to R7.0.11

PM1 FP type R5.1 R7.0.11

Unchannelized PM1 7570 8100

Channelized PM1 13551 14500

Table 78 Mbyte CQC-based ATM FPs (PDC1.0)

FP Type Unsupported PEC Range(8 Mbyte FPs)

Minimum 16 Mbyte Version

3-port DS1 ATM function processor NTFP30AA - NTFP30BB NTFP30CA or NTNQ45AA

8-port DS1 ATM function processor NTFN14AA - NTFN14BB NTFN14CA or NTNQ49AA

3-port E1 ATM function processor NTFP32AA - NTFP32BB NTFP32CA or NTNQ46AA

8-port E1 ATM function processor NTFN16AA - NTFN16BB NTFN16CA or NTNQ50AA

3-port DS3 ATM function processor NTFP18AA - NTFP18DA NTFP18EA or NTNQ51AA

3-port E3 ATM function processor NTFP17AA - NTFP17DA NTFP17EA or NTNQ52AA

4-port DS1 AAL1 function processor NTFP80AA - NTFP80AC NTFP80BA or NTNQ47AA

4-port E1 AAL1 function processor NTFP82AA - NTFP82AC NTFP82BA or NTNQ48AA

2-port J2 ATM function processor NTFP58AA - NTFP58BB NTFP58CA or NTNQ53AA

3-port OC-3 multi-mode ATM functionprocessor

NTFP16AA - NTFP16DB NTFP16EA or NTNQ54AA

3-port OC-3 single-mode ATM functionprocessor

NTCP38AA - NTFP38CB NTFP38DA or NTNQ55AA



oup

s).

ualS

tinguter,

ber

d on

If are

this

ks

ILS.

se

see

Inter-LAN Switching (ILS) ConsiderationsRFC1490 Bridged Frame Routing Considerations

A single DLCI for each IP COS value can be provisioned under a Remote Grprovisioned with Bridged Frame Routing (BFR). Also, BFR cannot beprovisioned under the default remote group (for example, no dynamic DLCIFinally, the bridging package is not required to be provisioned on the cardrunning FrDte which results in a reduction in memory usage.

Multiple Virtual Routers (MVR) ConsiderationsAll PM1 - based FP’s currently in use, can still be used, provided only one VirtRouter is provisioned. When provisioning more than one VR, PM2 based ILFP’s and CP2s are required.

The number of applications running under a Virtual Router, as well as the rouprotocol type (static, RIP, EGP, OSPF Area Border Router, OSPF Internal RoRIP, BGP4) and routing database size may have significant impact on the numof virtual routers that can be supported. Due to complex interaction betweencomponents, attention should be paid when more than 20 VRs are provisionea Passport.

ILS on ATM FP CQC ConsiderationsMigration Issue:VNS, SRES and NetSentry are not supported when this feature is enabled.Passport has any of these features configured, they must be removed befoenabling ILS on CQC.

Note: When commissioning a new shelf containing ILS, STARTUPprocedures requires the ILS Forwarder Card.

Interoperability Issue:Must not have VNS, SRES and NetSentry configured on the same shelf whenfeature is enabled. This restriction applies if even one ATM MPE or LANEcomponent has their ilsForwarder attribute set to blank.

Note:VNS cannot be used on the same shelf, even if no ATM Logical Trunare configured.

Other issues:Performance will be significantly lower than what can be achieved using anForwarder Card. This feature is only supported for PDC1.1 based ATM FP’s

ATM Multiprotocol Encapsulation (ATM MPE) Considerations• To configure the ATM MPE feature, the ATM function processor as well a

all function processors running ILS protocols must be configured with thATM MPE software package.

• The ILS Forwarder card must be configured with the ATM MPE softwarepackage as well as the required ILS protocol software packages. Please241-6401-835Passport LAN over ATM User Guidefor more information.



led.

In

m

ds

ill

ase.

s,

forand

dedd

f arred

lt inlly

eretics

ast,tic

• Sparing is supported for the ILS Forwarder card.

• It is recommended that the Vr Ip Arp autoRefresh attribute be set to disabIf this attribute is set to enabled, it is possible that, under heavy ILSForwarder congestion, ATM InverseArp Requests/Responses may bediscarded resulting in a loss of IP connectivity across the ATM MPE link.the event of a loss of IP connectivity due to ATM InverseArp Requests/Responses getting discarded, a lock and unlock operation on the probleATM MPE AC component will resolve the problem.

ATM MPE is not supported on 2pJ6MAtm cardType, so all the 2pJ6Atm carhave to be pulled out of the switch before the user try to run Startup with theAtmMpe.

IP Considerations• A maximum of 2000 static routes can be configured in this release. This w

be increased in a future Release.

• SNMP OSPF sets of operational attributes are not supported in this rele

• The maximum ping size allowed to be sent to a Passport virtual routerprotocol port is 30,600 bytes including headers. Due to buffer constraintlarger packets will cause the ping to fail.

• Care must be taken when clearing the ARP table to ensure ARP entriesATM MPE are not cleared. These entries are established at call setup timeare not automatically replaced if deleted. If the entire ARP cache is intento be cleared, lock/unlock of the ATM MPE component must be performeto re-establish the ARP table entries.

IPX Considerations• To receive error free support for Remote Groups using IPX, both peers o

FrDte, X25Dte, and PPP circuit must be provisioned with the same preferouting protocol (default type) andnetwork number. If the connection is to adevice that does not support the IW2 protocol, the Passport should beconfigured so that thedefault typeattribute is configured asother.

IP Multicast ConsiderationsProvisioning a large number of static routes, hundreds for example, will resua delay for the "Check Provisioning" command. Multicast statistics are not fusupported on Passport. Outgoing multicast packets will increment theifOutUcastPkts statistic. Incoming multicast packets will increment theifInUcastPkts statistic. This is true except in the case of ethernet media, whincoming multicast packets increment the ifInNuCastPkts and outgoing statisincrement the ifOutNuCastPkts. Also, if a static route is being used for multicthe protocol port of the outgoing interface will see the ifOutNuCastPkts statisincremented.



ts toallFis canal

eternal

pe

ge,

arere

CP

ng

f theith

OSPF ConsiderationsWhen there are 3 virtual routers configured in a meshed setup (e.g. A connecB, B connects to C, C connects to A) a possible problem may occur. Whenlinks are up and exporting routes into this OSPF domain is attempted, OSPconverges fine and the fastest path is used to reach the non-ospf routes. Thbe seen in the RDB. For example, if the fastest path chosen to get to externroutes off of A from C is through B and the physical port between C and B islocked, OSPF should re-converge to take the C to A path directly to get to thexternal networks. This however does not happen and the routes to these exnetworks are not propagated to the RDB. Hence, these networks becomeunreachable. If this occurs, the connection that is brought down is an atmmlink.

The work-around is to not lock the physical port to force OSPF to re-converbut to lock any of the other components mentioned below.

• Instead of doing a lock lp/n ds3/x, you can do any of the following:lock vr/n pp/xlock vr/n pp/x ipportlock atmmpe/nlock atmmpe/n ac/x

IP CoS ConsiderationsLogicalProcessorTypeBe sure to includeipCosin the feature list of all those LPTs associate with allingress ports where ToS-based packet classification, Flow-based packetclassification, Tos marking, Cos to EP mapping, and/or CoS to DP mappingrequired. When only Layer 2 packet classification and CoS to VC mapping arequired,ipCosis not required in the feature list.

CosPolicyGroupA Policy Group associated an ingress protocol port serve to define ToSclassification and Flow classification rules for packets entering the port.

A CosPolicy Group associated an egress protocol port serve to define ToSmarking and CoS to QoS rules for packets forwarded out that port.

CosPolicyGroupIt is highly recommended to leave the tosMask attribute under eachCosTreatment component as its default value 0xFC in order to match to DSfield for Differentiated Services.

PolicyWhen two ipAddrLayer4Flow components with the same protocol type havioverlapping Layer 3 flow specifications are added under two different Policycomponents with different CoS under the same CosPolicyGroup, the CoS oPolicy containing the most precise Layer 3 flow specification (i.e. the one wthe longest prefix length) takes precedence, regrardless of the Layer 4 flowspecifications ( portRange ).



ame

ns

50

0

9

0

50

CI

e issede

tt.

When the two flow specifications have the same effective Layer 3 flowspecification (i.e. they both have the same prefix length, and they both have sprefix up to the prefix length), then one of the follow two cases may occur:

• the two flow specifications have non-overlapping Layer 4 flow specificatio(portRange) and both are accepted

• the two flow specifications have overlapping Layer 4 flow specifications(portRange) and a neither are accepted.

The ipAddrLayer4Flow components must not have overlapping port rangeswhen they have the same effective Layer 3 flow specification, so rather thanprovisioning:

vr/<vrName> ip pg/<pgName> pol/<1st pol> IpAddrLayer4Flow prefix = <IPaddr>vr/<vrName> ip pg/<pgName> pol/<1st pol> IpAddrLayer4Flow prefixlen = <len>vr/<vrName> ip pg/<pgName> pol/<1st pol> IpAddrLayer4Flow portnumberRange = 3

vr/<vrName> ip pg/<pgName> pol/<2nd pol> IpAddrLayer4Flow prefix = <IPaddr>vr/<vrName> ip pg/<pgName> pol/<2nd pol> IpAddrLayer4Flow prefixlen = <len>vr/<vrName> ip pg/<pgName> pol/<2nd pol> IpAddrLayer4Flow portnumberRange = 115

which would lead to a semantic check error, one would provision:


vr/<vrName> ip pg/<pgName> pol/<2nd pol> IpAddrLayer4Flow prefix = <IPaddr>vr/<vrName> ip pg/<pgName> pol/<2nd pol> IpAddrLayer4Flow prefixlen = <len>vr/<vrName> ip pg/<pgName> pol/<2nd pol> IpAddrLayer4Flow portnumberRange = 115


FrDTEIf CoS to QoS mapping is to be supported on FrDte then a different static DLand corresponding Fruni must be provisioned for each QoS. All virtualconnections in the set must terminate at the same remote node. The QoSparameters of the Fruni must be set to reflect the required level of service.

When the OSPF routing protocol is to be used on protocol ports where FrDtprovisioned with more than one static DLCI to the same next hop (for CoS-baselection of virtual circuit for forwarding refinement), it is recommend that thIfType attribute on the IpPort component is NOT set to pointToPoint.

After provisioning static DLCIs with different CoS under an FrDte componenand activating, lock and unlock the IpPort of the FrDte ’s linked protocol por

Note: Also see the section on Dynamica IP ARP Entries below.



ndinATM

peoS-

hat

d

ifthe

the

staticear.s to

the

utepull-

ainre a

AtmMpeIf CoS to QoS mapping is to be supported on AtmMpe then a different VCC acorresponding atmConnection must be provisioned for each QoS. All VCCsthe set must terminate at the same remote node. The QoS paramters of theVCC must be set to reflect the required level of service.

When the OSPF routing protocol is to be used on protocol ports where AtmMis provisioned with more than one atmConnection to the same next hop (for Cbased selection of virtual circuit for forwarding refinement), it is recommend tthe IfType attribute on the IpPort component is NOT set to pointToPoint.

After provisioning atmConnections with different CoS under an AtmMpecomponent and activating, lock and unlock the IpPort of the AtmMpe’s linkeprotocol port.

Note: Also see the section on Dynamica IP ARP Entries below.

Dynamic IP ARP EntriesAvoid clearing dynamic IP ARP entries learned by an AtmMpe protocol portIP CoS is required. However, if it is necessary to clear IP ARP entries, notefollowing:

If clearing any of the IP ARP entries of the same IP address, lock and unlockIpPort of the AtmMpe’s linked protocol port.

Static IP ARP EntriesWhen a static arp entry is provisioned for an FRDTE or ATM MPE it replaceall of the dynamic arp entries, if any, for the IP address specified. When the sentry is later deleted, the dynamic entries entries do not automatically re-appThe protocol port must be locked and unlocked to get the dynamic arp entriere-appear.

IP TUNNELInterworking IP Cos with IP Tunnel is not presently supported.

Virtual MediaUnicastpackets are not classified according to the assignedQos attribute onprotocol port (i.e by the Layer 2 classification method) at ingress to a virtualrouter, butmulticastpackts are.

NMS PPMMThe valid values that can be entered for provisioning the discardPriority attribunder the CosTreatment component are : unchanged,0,1,2,3; however thedown menu for this attribute displays “unchanged” only.

Migration from Release 5.1When migrating from a release 5.1 load (BE01*) to a R7.0 load (BG00*) certmigration steps which require manual intervention may be required to ensusmooth migration without a loss of functionality.



ingver

to.

e

yn.

t

CI

• wanEmissionPriority Attribute Migration

ThewanEmissionPriorityattribute in theQualityofServiceProfile componentthat exists in Release 5.1 is obsoleted by the new R7.0emissionPriorityattribute in theCosTreatmentcomponent.

This change was done to provide more flexibility to the user when assignan emission priority to outgoing packets under the CoS to QoS Mapping osingle DLCI or PPP capability. With the attribute under theQualityofServiceProfilecomponent, a specific emission priority was assignedall packets of a particular class of service leaving the same virtual routerWith the new attribute location under theCosTreatmentcomponent, anemission priority can be assigned for all packets of a particular class ofservice, but for all packets leaving a particular protocol port. Therefore thuser would be able to provision different emission priorities for separateprotocol ports for the same class of service.

Unfortunately, since the new attribute is in theCosTreatmentcomponent(which requires“ipCos” to be provisioned in thefeatureListof theappropriateLogicalProcessorTypecomponent), some manual provisioning mabe required to ensure there is no loss of functionality during the migratio

Please follow the following steps to determine the provisioning steps thamay be required before performing the migration to a R7.0 load.

1 Check to see if you are utilizing the CoS to QoS Mapping over single DLor PPP functionality based on the values of the wanEmissionPriorityattributes in your current provisioning view

• for each definedVirtualRouter component, display thewanEmissionPriorityattribute values under eachQualityofServiceProfile component

1> d vr/* qosp/* ep

Vr/* QosP/*+========+===+--+----------------------------------------| Vr |Qos|ep|Response| | P | |+========+===+--+----------------------------------------|1 | 0| 2||2 | 0| 2||2 | 1| 2||2 | 2| 2||2 | 3| 2||3 | 0| 2||3 | 1| 2||3 | 2| 1||3 | 3| 1||4 | 0| 2||4 | 1| 2|



ofe

to

ave

hat

st

|4 | 2| 1||4 | 3| 1|

(In this example, only VRs 3 & 4 are using non-default emission priorities)

• if any of the values under the “ep” column is set to a value of “1”, thenmigration is required, if all the values are “ep” column are set to a value“2”, then NO migration is required, since the value of “2” is the default valuof the obsoleted attributewanEmissionPriorityand the new attributeEmissionPriority.

2 If migration is still required (i.e. awanEmissionPriorityattribute was foundwith a value set to “1”), then in order to prepare for the migration we needensure the properCosPolicyGroupcomponents exist in order for the migrationto occur.

During the migration, for eachQualityofServiceProfile (QosP)component ofeach existingVirtualRouter (Vr) , if thewanEmissionPriorityattribute value isset to “1”, then theEmissionPriorityattribute of theCosTreatmentcomponentwhose index matches the index of theQualityofServiceProfile component willbe set to “1” for allCosPolicyGroup (pg)components defined under the sameVirtualRouter .

Pseudo-code example:

FORx = {Vr[1st instance] TOVr[number of Vr]}FORy = {QosP[0] TO QosP[number of QosP]} INVr[x]

IF Vr[x] QosP[y] wanEmissionPriority== 1THEN

FORz= {Pg[0] TO Pg[number of Pg]} INVr[x] Ip

Vr[x] Ip Pg[z]CosTreatment[y] emissionPriority= 1

As you can see from the pseudo-code example above it is important to hCosPolicyGroupcomponents existing to preserve thewanEmissionPriorityattribute value during the migration. The following are the different steps tshould be considered to preserve the value.

• for complete equivalence in functionality, for eachVirtualRouter that has awanEmissionPriorityattribute value set to “1” (as checked in step 1), at leaoneCosPolicyGroupcomponent should exist under theIp component of theVirtualRouter , and oneCosPolicyGroupshould be linked to theVirtualRouter Ip



d

P

component though thelinkToPolicyUsersattribute (in other words, have apolicy group linked to the VR).

(In the first example Vr/3 and Vr/4 were the only VRs with an emissionpriority equal to 1)

2> d vr/3 ip pg/*

Vr/3 Ip Pg/* users+====================+---------------------| Pg | users+====================+---------------------|1 |Vr/3 Ip|2 |Vr/3 Pp/ETH91| | IpPort

3> d vr/4 ip pg/*

Vr/1 Ip

Component has no provisioned or operationalsubcomponents of the requested type.

(In our example, the check for Vr/3 is OK as we have a policy group linketo the VR, but the check is not OK for Vr/4 as there are no policy groupsprovisioned)

• since thewanEmissionPriorityattribute is only supported for FrDte and PPmedia, actually only the FrDte and PPP mediaProtocolPortsneed to beensured they are linked to aCosPolicyGroup, either directly throughprovisioning or instead inherits theCosPolicyGroup linked to theVirtualRouteras the defaultCosPolicyGroup. To check theCosPolicyGroupused by aProtocolPort, look at theIpPort operational attributeoperCosPolicyAssignment

4> d vr/3 pp/* ipp operCosPolicyAssignment

Vr/3 Pp/* IpPort+====================+--------------------| Pp |operCosPolicyAssignm| | ent+====================+--------------------|ETH91 |Vr/VPN4A Ip Pg/2|FRDTE312 |Vr/VPN4A Ip Pg/1

5> d vr/4 pp/* ipp operCosPolicyAssignment

Vr/4 Pp/* IpPort+====================+--------------------



edotr/4)

ed)

| Pp |operCosPolicyAssignm| | ent+====================+--------------------|ETH92 |!|PPP50 |!

(In our example, the check for Vr/3 is OK as we have the policy group linkto the VR being used by our FrDte protocol port, but the check for Vr/4 is nOK as expected since we don’t have any policy groups provisioned on V

3 If there are any FrDte or PPP mediaProtocolPort components that still need aCosPolicyGrouplinked to it in order to migrate thewanEmissionPriorityvalueof 1 into the newemissionPriorityattribute, follow the followingprovisioning steps to add aCosPolicyGroup.

• in order to provision aCosPolicyGroupcomponent, the“ipCos” feature mustbe provisioned in thefeatureListof the appropriateLogicalProcessorTypecomponent.

• if you do need to addCosPolicyGroupcomponents and add the“ipCos”feature, then it is only required to be added to thefeatureListof theLogicalProcessorTypecomponents for WAN functional processors, as thisfunctionality is only supported on FrDte and PPP media

(The following is an example as if we didn’t have the ipCos feature previously provision

6> d sw lpt/* feat

Sw Lpt/*+====================+---------------------| Lpt | fl+====================+---------------------|ATM |atmUni| |atmIisp| |atmbearerservice| |atmtrunks| |atmmpe| |vns|CP |ipifr| |dpnrouting| |callserver| |mvr| |bgp| |oamenet| |ip|ILS |ip| |vns| |atmMpe|LAN |ip| |vns| |atmmpe|V35 |ppp| |ip



)

e

ftered,ted.

ack

n,

| |frameRelayDte| |atmmpe

(From displaying the features in the LPTs in our example, we see that only the V35 LPTrequires the ipCos feature added since it is the only LPT that has PPP or FrDte running

7> start provProv

The edit view is identical to the current view.ok 2000-xx-xx nn:nn:nn.nn

PROV 8> set sw lpt/V35 feat ipCos

PROV 9> check prov

PROV 10> act prov

PROV 11> end prov

(After activating the ipCos feature provisioning addition, the user will now be able toprovision the CosPolicyGroup component)

• provision aCosPolicyGroupcomponent under eachVirtualRouter that stillrequires aCosPolicyGroupassigned to it

12> start provProv

The edit view is identical to the current view.ok 2000-xx-xx nn:nn:nn.nn

PROV 13> add vr/4 ip pg/VR4

(We’ve created a CosPolicyGroup (pg) under vr/4 and appropriately named it VR4)

• link the newCosPolicyGroupto either all the FrDte and PPPProtocolPortsor totheVirtualRouter . It may be found more useful to link it to theVirtualRouter asany newly created FrDte and PPPProtocolPortswill automatically use theCosPolicyGroup (and it’s provisioned CoS to QoS functionality) linked to thVirtualRouter .

PROV 14> set vr/4 ip cosPolicyAssignment vr/4 ip pg/VR4

PROV 15> check prov

PROV 16> act prov

PROV 17> end prov

4 Now the provisioning view is readyand can be migrated to a R7.0 load. Athe load has completed migration, and if all the steps above were performyou should see that the emission priority values properly stored as expecProvisioning changes made to the discardPriority attribute under theCosTreatment component at R7.0 will not be preserved when migrating bto R5.1.

Bridging Considerations• Fragmentation on Cluster Bridge is not supported. To avoid fragmentatio

set the MTU of the Cluster Bridge on all links to be the same.

• Frames discarded during times of heavy activity may not get added tostatistics.



ing

e

the

r anot

ngntally

not

y.ort

of

s ittersleies

• NetSentry filters applied on transparent bridge ports at incoming or outgodo not function when they are first applied. The filter will be applied if theprotocol port is locked then unlocked or if a different filter is applied to thfilter point.

• When moving a station connected to one interface to another interface,initial interface must be locked then unlocked to clear the entry in theforwarding table.

• Connectivity problems may result if thepreserve domainattribute is set toonfor an access FDDI Encapsulated port.

• The only ILS media that can be used to perform Source Route Bridging(SRB) are:

— tokenRing (FP port or LAN port of CFP1)

— vns trunks

— frameRelayDte

— PPP

— Non-ATM IP FP ports

• The TinyGram compression feature is used to remove the trailling zero fo802.3 frame over PPP media when going through a bridge. This feature issupported over ATM-IP cards and is not reflected on this release, meanithat although the bConfigTinygram attribute under ppp/42 ncp componemay indicate that the tinygram compression feature is enabled, it is actunot working if the inegress traffic is from an ATM-IP card.

NetSentry Considerations• To configure the NetSentry feature, all Function Processors running ILS

protocols must be configured with the NetSentry package. If NetSentry isin the feature list, the Function Processor will reset.

• Configuring NetSentry filters can significantly reduce throughput capacitCareful filter design is required. Please refer to your Nortel Technical Supprepresentative for assistance. Also, please see 241-6401-350PassportSecurity and Access Control User Guide.

• Compilation of a filter file will fail if a single filter causes byte code to beproduced which is greater than 32K. This is due to a 32K byte restrictionthe PEV messaging system.

• Deleting a file under the “vr/<vr_name> ns file/*” subcomponent will notcause the filters contained in that file to be deleted. In order to delete filteris necessary to delete the “vr/<vr_name> ns” subcomponent. However, filcan still be modified and updated correctly by placing the modified filter fiin /provisioning/netsentry/prov and /provisioning/netsentry/oper directorand issuing the command “reload vr/<vr_name> ns file/<file_name>”.

The following NetSentry action, found in 241-6401-350Passport Security andAccess Control User Guideis not true. A NetSentry filter containing an action“priority” does not change the queueing priority on any ILS media (IP, IPX



on

edo arface.

. A

filter

ot a

been

Bridging, frameRelayDte, etc.). However, the problem does not come fromNetSentry itself, but rather from the ils media applications that do not act upthis NetSentry command.

This action changes the priority of a packet destined for a LAN or WAN interface. The allowrange is 0 (lowest priority) to 3 (highest priority). Note that a low priority packet that is sent tlittle-used interface can be forwarded before a high priority packet is sent to a congested inte

CP Crash: NetSentry clusterbridge filter configurationApplying a log_to action in the clusterbridge media will cause the CP to crashtypical configuration might look something like:

filter BR_ETHER

# Copy all ICMP packetsip_protocol in (1)alarm 1log_to 208.42.18.185 35402 break;

end

The packets generated by the filtering process are in turn processed by thegenerating more packets. The result is an infinite loop which consumes allavailable CPU and causes the CP to crash.

The simplest workaround is to add a filter clause that checks the packet is nlog_to packet. The revised filter would look like this:

filter BR_ETHER# Do not relog the log_to packetsudp_dp in (35402) break;# Copy all ICMP packetsip_protocol in (1)alarm 1log_to 208.42.18.185 35402 break;

end

This consideration applies equally to copy_to and route_to actions and hasdocumented in the 5.0 NetSentry 241-6401-350Passport Security and AccessControl User Guide.

BGP-4 ConsiderationsMemory limitationAssume:

Action Minimumspelling

Subcomponents

priority none priority



teiableber

uteseer)tes.

foreft.

ortbles

l BGPo eachto bected

ia

This assumption is based on the measurements made with live internet roufeeds. The values below are approximate due to that BGP routes have a varsize data structure due to the variable size of the path attributes and the numof nlris sharing the same path attributes.

Each First Indb routes uses 230 bytes of memory. Each successive Indb rouses 105 bytes of memory. Each First Outdb (External peer or first Internal proutes uses 85 bytes. Each Second Outdb (internal peer) routes uses 70 by

Assume is a single VR configuration. Assume 5000 OSPF routes. Assume beany BGP connection is established, there is only 30 Mbytes free memory leAssume a requirement of 4 Mbytes memory remains for dynamic usage.

Maximum Configuration supported:

1 EBGP(in) 1 IBGP(in and out) -> 3 set of full routing databaseF is the maximum number of routes supported.230 x F + 105 x F + 85 x F = 470 x F = 34000000 - 4000000 = 30000000420 x F = 30000000F = 71428.571

Under this configuration, based on all the above assumptions, we can suppmaximum 71000 routes. More routes can be supported if fewer BGP route taare required (i.e. network is not a transit AS).

Reference Configurations Supported:The following reference configuration will still be supported:

EBGP IBGP EBGPE1 ----------------- PP1-----------------PP2------------------ E2

Where E1 and E2 are BGP-4 speakers connected to Passports via Externa(EBGP) peerings. PP1 and PP2 are Passport BGP-4 speakers connected tother via an Internal BGP (IBPG) peering. The two passports are assumedin a single autonomous system. This topology only shows 2 Passports connevia IBGP. This simple topology is used only for describing the supportedconfigurations. There could be as many as 32 BGP-4 speakers connected vIBGP.

Configuration 1:

EBGP IBGP EBGPE1 ----------------- PP1-----------------PP2------------------ E2(default)--------->(default)-------------->

<----------------(default)<---------(default)



ises

fault

etE2

ull

re isryful

In this configuration, E1 advertises a default route to PP1 which in turn advertit to all IBGP peers. E2 also advertises a default route to PP2 which in turnadvertises it to all IBGP peers. The default routes are prioritized such thatexternally learned default routes take precedence over internally learned deroutes.

Configuration 2:

EBGP IBGP EBGPE1 ----------------- PP1-----------------PP2------------------ E2(Internet)--------->(DADR)---------------->

<-----------------(DADR)<---------(Internet)

In this configuration, E1 advertises the full Internet routing database to PP1which compiles a Dynamic Agregate Default Route (DADR) from the Interntable which points to E1. PP1 then sends the DADR to all of its IBGP peers.and PP2 behave the same as E1 and PP1.

Configuration 3:

EBGP IBGP EBGPE1 ----------------- PP1-----------------PP2------------------ E2(Internet)------>(Internet)--------------->

<---------------(Internet)<---------(Internet)

We support configuration 3 with the limitation that we can only propogate the fInternet table to one IBGP or EBGP peer.

Note: all the above configurations will subject to the memory limitation.

RIP and BGP InteractionIn version R7.0.11, RIP and BGP can be active simultaneously. However thean issue with how the export policy to RIP operates (pulling information eve30 seconds) only the following configurations have been tested with sucessoperation:

1) 3000 BGP routes exported to RIP (per Passport Shelf)

2) Full Internet BGP routes with no export policy to RIP



on-

NDCQC/

he

pen

lut

t in

Base ConsiderationsBCS Broadcast Mechanism

In Release 7.0, the BCS broadcast mechanism was disabled for FPs and nactive CPs. Since no applications on the said cards use the broadcastingfunctionality of BCS, service is not affected. In the process of disabling thebroadcast queue at startup, two types of SWERRs may be generated:

Shelf Card/1 BusTap/x; 2000-04-27 23:45:34.39MSG indeterminate processing softwareError 00009000

ADMIN: unlocked OPER: enabled USAGE: activeAVAIL: PROC: CNTRL:ALARM: STBY: notSet UNKNW: falseId: 01000001 Rel:Com: 0x0

Stack trace: _startDispatching_v__16EeDispatcherBaseUc_queryBusStatus_v__16Bcs_BusModeAgent_checkBcastQueues__11Bcs_PrimaryPci_checkBcastQueues__16Bcs_TxChannelSetPci _software__FPCcT0iUi_software__FPCcT0iT0RUi

Int: 1/1/2/25106; bcsTxChannelSetExt.cqc.cc; 118; p7.0d.19

The above software error is generated normally during the startup of CQC APQC cards. This denotes that the broadcast queue is being disabled on thePQC card.

Shelf Card/0 BusTap/x; 2000-04-27 23:45:34.39MSG indeterminate processing softwareError 00009000

ADMIN: unlocked OPER: enabled USAGE: activeAVAIL: PROC: CNTRL:ALARM: STBY: notSet UNKNW: falseId: 01000001 Rel:Com: Backplane broadcast data found.

0c0cc00000000c0/7/32 blocks purged in 3

Stack trace: _startDispatching_v__16EeDispatcherBaseUc_queryBusStatus_v__16Bcs_BusModeAgent _software__FPCcT0iT0RUi

Int: 0/0/2/7454; bcsBusModeAgent.cc; 227; p7.0d.19

The above software error is generated during a CP reload. It denotes that tbroadcast queue is being purged.

These software errors are not service affecting in any way and normally haponce when cards on the shelf are rebooting. Any other occurrance of thesesoftware errors signals irregular use of the BCS broadcast mechanism.

No check prov warning of TR/DS1V/E1V port resetAt 7.0, provisioning changes to vendor, commentText and defaultTraceLeveattributes of any lp/x tr/y component will pass check prov without a warning, bwill cause the port to reset upon activation.

Provisioning changes to other attributes of the lp/x tr/y component will resulthe following check prov warning.

PROV 70> ch prProv

octet 1



r the

g toer to

ngeshe

e

M

so

ures

e

Activation will disrupt service for the following component(s):Lp/2 Tr/0

ok 2001-07-12 12:17:03.19

The vendor, commentText and defaultTraceLevel attributes were added afteinitial deployment of the Token Ring FP. Adding an appropriate warningmessage during a check prov is not possible as this would cause the warninappear for all other port types that do not reset under these conditions. RefSR 10408605 for more information.

Also affected are 1pDS1V and 1pE1V FPs. Since these are 1-port FPs, chato vendor and commentText attributes of lp/x ds1/x (or lp/x e1/y) will cause tFP to reset.

MPANL ConsiderationMPANL SPO Enhancement

In order to enable the MPANL SPO feature after migration from 5.1 to 7.0, thfollowing steps are to be followed:

1. Upgrade the switch to R7.0.11 (BG00SBB)

2. Change the MPANL VOICE USESPO to YESSET MPANL/<n> VOICE USESPO YES

3. Lock and unlock all mpanlsLOCK -F MPANL/<n>UNLOCK MPANL/<n>

Note:SPO could be either SPO-MUX or SPO-MAP, depending on the ATconnection mode: MUX or MAP.

PNNI on Passport release 7.0.11The Passport Release 7.0.11 supports exactly the same PNNI capabilities aPassport Release 5.1. There were no enhancements made between the twreleases. This means that the following enhancements to PNNI are NOTsupported. This is not an exhaustive list, but is meant to highlight the key featthat are not in the Enterprise stream of software.

• EBR Phase 1 and Phase 2• H-PNNI• Provisionable Route Diversity• Specified Paths• Load Balancing using AvCR• External Link PNNI Crankback• PNNI Path and Connection Trace

As well, many of the PNNI scalability improvements are not in the Enterprisstream. The following limits will apply to the 6K network.

• Maximum number of PTSEs: 800• Maximum number of PNNI neighbors on any given PNNI node: 5

octet 1



ployn

yinked

at

y a

the

e

is

It is recommended that customers move to the PCR stream if they wish to dePNNI. The PCR stream has considerably more enhancements and has beeproven out in more networks than the R 7.0 software.

PORS considerationsConfiguring optional manual paths for a PLC

Configure a manual path, which consists of a sequence of hops, identified bnode name and egress trunk for transparent data services (TDS). Services lto a manual path can also override the manual path setting through themanualPath or porsManualPath attribute associated with connections for thservice.

Note: If you change the configuration of an existing manual path to specifdifferent route, the services that use that ManualPath componentautomatically switch to the new route. You do not need to lock or disableservice.

Procedure1 At the source node, add the btds instance

add btds/<instance>

2. Set the interface nameset btds/<instance> framer intefaceName Lp/<instance>x21/<instance>

3. Set the path type to manual.set btds/<instance> plc pathType manual

4. Set the remote nameset btds/<instance> plc remoteName “<switch>”

5. Define the first hop in the route by specifying the originating node and thpath to be taken in order to exit the node.set btds/<instance> plc manual path 0 “<switch><trunk>”

Note: 0 is the decimal that indicates the position of the hop. the first hopassigned index 0, the seconds assigned index 1 and so on.

6. At the destination node, repeat steps 1 and 2.Variable definitionsTable 8 contains definitions of the attribute values in Configuring optionalmanual paths for a PLC.

Table 8Variable Definitions

Variable Value

<index> This value is a decimal from 0 to 19 that indicates the position of the hop inthe route. The first hop is assigned index 0, the second is assigned index1, and so on.



For more information, please contact your Nortel Networks Representative.

<n> This value is a decimal of 1 to 255 that identifies the PORS manual path.There is no default value.

“<switch> <trunk>” An ASCII string of up to 40 characters that defines the

originating node in the path and the trunk used to leave the

node. The string must be enclosed in double quotation

marks (“ “).

Table 8Variable Definitions

Variable Value


Chapter 5 Release Planning 63

vice

ocsurrent

web

t your

the).

Chapter 5Release Planning

This chapter provides information about planning deployment of R7.0.11(BG00SBB). This chapter contains the following sections:

• “Documentation” (page 63)• “Replacing CQC-Based ATM FP’s with ATM IP FP’s” (page 64)• “Migration planning” (page 65)• “Network management” (page 66)• “Engineering” (page 72)• “Base Considerations” (page 79)• “Trunks, DPN gateways and networking” (page 81)• “Frame Relay” (page 83)• “ATM” (page 86)• “ATM Networking” (page 94)• “AAL1 Circuit Emulation Service (CES)” (page 98)• “Voice” (page 99)

DocumentationFor details on the changes to the NTPs, including feature impacts, fixed serrequests, and removed documents, see 241-6401-000Passport 6400 What’s Newin the Documentation Suite.

As of R7.0.10, there are changes to the way that the Passport technicaldocumentation is made available to you. The UniHelp interfaces and the eDweb site have been decommissioned. The rest of this section describes the cdelivery methods:

- “Internet” on page 63- “Intranet” on page 63- “Helmsman-based CD-ROM” on page 64- “Paper” on page 64

InternetOver the Internet, you can use Helmsman Express on the Nortel Networkssite to view, do a suite-wide search, or download documents in PDF format.

To register for access to Passport documents on Helmsman Express, contacNortel Networks account representative.

IntranetYou can install the Passport documents on a server in your own intranet toprovide access to the documentation using the Helmsman software. Installdocuments and Helmsman from the “Helmsman-based CD-ROM” (page 40


64 Chapter 5 Release Planning

D-PC,e

u tokage-

ders,

canP.

C-checkret

s theap,

PQC-

s

Helmsman-based CD-ROMThe Helmsman-based CD-ROM contains the current release of Passportdocumentation in PDF format, viewable with the Helmsman software. The CROMincludes the Helmsman software as well as installation software for theUnix (Sun and HP) and Macintosh platforms. Helmsman provides suite-widsearch capabilities.

Installation instructions are provided on the CD-ROM.

Your Nortel Networks account representative needs to place an order for yoreceive the CD-ROMs. Depending on which Performance Pack support pacyou have, you receive either one copy or up to five copies of the Helmsmanbased CD-ROM.

PaperYou can purchase sets of Passport documentation in hardcopy format in binat extra cost. For more information or to purchase hard copies, contact yourNortel Networks account representative.

Replacing CQC-Based ATM FP’s with ATM IP FP’sTo take advantage of new functionality on the new PQC-based ATM FP, youupgrade your hardware from a CQC-based ATM FP to a PQC-based ATM F

Changes in provisioning are required to replace a CQC-based FP with a PQbased FP. If these mandatory provisioning changes are not made, semanticerrors will result when the card type is changed. The changes described herepresent a minimal set required to make a PQC-based FP work and do noleverage the full feature and flexibility provided by the PQC-based FP.

If the CQC-based ATM FP is currently operating with the DEFAULT Arc,ConnMap, and Ca components, then the only required provisioning change icard type. Those with a customized configuration for either the Arc, ConnMor Ca components, must follow the instruction/semantic errors for thosecomponents.

Changing card typeThe Shelf Card/n cardtype must be changed since the CQC-based FP andbased FP have different card types.

If the interface type of the card is also changed, the port subcomponentsunderneath the LP/x component must be replaced.

If the number of interfaces is reduced on the new card type, the componentrelating to the additional interfaces must be deleted (for example, ATMIF).

Changes for Lp/n Arc ComponentIf the Lp/n Arc Cqc Override component exists, it must be deleted

Adding the Lp/n Arc Aqm/x Override component is optional.



theon

set toc or

s

0

ier

testo

Changes for Atmif ConnMap ComponentIf the Atmif ConnMap component exists, it must be deleted

Changes for Atmif/x Ca ComponentFor PQC-based FPs, if a service category has traffic shaping enabled, thenunshapedTransmitQueueing attribute must be set to autoConfigure. Commqueueing and traffic shaping are not supported simultaneously for the sameservice category.

Changes for Atmif/x Vcc Vcd and Atmif/x Vpc Vpd ComponentsFor PQC-based FPs, the unshapedTransmitQueueing attribute can only bea value of sameAsServiceCategory. The method of transmit queueing (perVcommon) can only be chosen per service category and not per connection.

Installation PlanningInstallation procedures provided in NTP 241-6401-605Passport 6400Operations and Maintenance Guideapply to this release.

ILS startup introductionYou have the option of setting up IP communication using ILS IP capabilitiebetween a newly commissioned Passport switch and one of the following:

• a software download site (Preside Multiservice Data Manager (formerlyknown as NMS) workstation)

• another Passport switch or router in an IP network

You can establish IP communication over various ILS media such as FrDte,VNS, ATM MPE and Ethernet. For more information, see NTP 241-6401-27Passport 6400 StartUp Guide.

Migration planningThis section provides information needed to plan the migration from an earlsoftware release to Release R7.0.11 (BG00SBB).

Support Discontinued of 8 Mbyte CQC-based ATM FPs (PDC1.0)8 Mbyte CQC-based ATM FPs are not supported in P7.0.11.

See “Support Discontinued of 8 Mbyte CQC based ATM FPs (PDC1.0)” onpage 43 for details.

Component Administration SystemDue to a limitation in CAS, you must manually delete the obsolete AtmCrcomponent during software migration from level 4.2 to level 7.0.

Benign Recoverable ErrorsYou may see the following benign recoverable error within the first four minuafter a shelf has been migrated from R4.2 to R7.0 (or a roll-back from R7.0P4.2) and there are frame relay connections terminating on the shelf:

Recoverable Software error at line 93 in file dmeLocalFrameS.cc



hatns,.

error

utes.

sing

ging

ity

--- Reason ---Attempted to send to an EntityId of 0x940044 with a bad type.Frame contents (100 byte max) is:41 2 22 c 31 8 44 0 94 c0 49 9f 55 55 5555 55 55 55 55 55 55 55 55 55 55 55 55 55 55 5555 55 55 55 55 55 55 55 55 55 55 55 55CPU utilization: 45 percent busy CPU: i960 CF (E-step)No Traceback when at interrupt levelApplication level information at time of exception:Date: 1998-05-24 Time: 13:45:07Card type: 3pDS3AtmCommitted File : N/ACurrent view file: N/ASoftware version: BE00CCAS Information: COMPLETED: fpActSynchronization begins.Synchronization ends.

This recoverable error does not indicate any problem. Instead, it indicates tstale frame relay data traffic from the other end of the frame relay connectiothat was set up before the software migration, has been properly discarded

The reason that the discarding is causing the generation of this recoverablein R7.0 is due to a format change of the internal data structure. As such, thebenign recoverable errors should only be observed within the period of 4 minafter a software migration involving pre-P5.0 to post-P5.0 software releases

If the recoverable error is observed at any other time, it should be dealt with uthe normal procedure for handling recoverable errors as detailed in theTroubleshooting section of NTP 241-6401-605Passport 6400 Operations andMaintenance Guide.

Network managementThis section provides information needed when performing network planninand management during software migration. This section contains the followsubsections:

• “Express Manager support” (page 67)

• “Preside Multiservice Data Manager (formerly known as NMS) support”(page 67)

• “Preside Multiservice Data Manager (formerly known as NMS) connectivusing IpiFr” (page 67)

• “SNMP agent considerations” (page 67)

• “SNMP standard MIB” (page 68)

• “SNMP Enterprise MIB considerations” (page 68)

• “SNMP rolled up variable considerations” (page 71)



r 4.2

ly forss

(or

rare

lly

thtion

ecting

n ar to

(forr toork/

ware

Express Manager supportExpress Manager 4.2 will support Passport 6400 Release 7.0 (with customtemplates), on Windows NT and 2000 operating systems. Express Managedoes not support Passport 7400 modules and the PCR stream.

Express Manager 4.2 is the last release and the product will be supported onthe life of the Passport 6400 Release 7.0 stream. All prior releases of ExpreManager are service discontinued as of December 31, 2002.

Preside Multiservice Data Manager (formerly known as NMS) supportPreside Multiservice Data Manager (formerly known as NMS) Release 12.5higher) with Solaris is required to support Passport networks running thisPassport release.

Preside Multiservice Data Manager (formerly known as NMS) connectivityusing IpiFr

Ipifr DefaultRoute (DR) has been obsoleted since P4.2. It is replaced by IpifStaticRoute (SR) /0.0.0.0, which performs the same functions. During softwmigration, the new component of Ipifr SR/0.0.0.0 is created and its attributeipiGtyIpAddress is set to the value of the IpiFr’s DR. After the Passport is fuactivated, all functions of Ipifr DR are performed by Ipifr SR/0.0.0.0.

Ipifr DR is not available after migration. To view the definition of the IPDefaultRoute, look at the ‘IpiFr StaticRoute/0.0.0.0’ component.

The ‘remoteIpAddress’ attribute of the ‘IpiFr Lcn’ component is introduced withis release. The attribute provides a Static Address Resolution implementa(for example, mapping IP addresses to the link layer or, in this case, DNAaddresses). In previous releases, address resolution was performed by inspthe source IP address of the first IP packet sent over the LCN.

If the ‘remoteIpAddress’ attribute is not set, address resolution continues todepend on the source ID address. IpiFr configurations which use a router onon-default route must implement non-standard router configurations in ordeensure that the correct address is resolved by the Passport.

You should set the ‘remoteIpAddress’ attribute for any configurations whichhave a router interfacing with the Passport network using IP over frame relayexample, ipiFr). Set the ‘remoteIpAddress’ to the router’s IP address in ordetake advantage of the router. Add an ‘IpiFr StaticRoute’ to route to the netwsubnetwork/host IP address containing the management workstations.

SNMP agent considerationsThe Passport SNMP agent supports SET on all components. You should be aof the following SNMP considerations.



sn theableP

beenlete

ETs

his

ke

e

ase,ed.

Full semantic checks (as percheck prov) are performed when provisioned data ichanged with an SNMP SET. The checks may take a long time, depending okind and extent of the provisioned data changes. Since the SNMP agent is unto process other SNMP GET or SET requests until checks are finished, SNMsurveillance applications may be locked out temporarily.

Change provisioned data using SNMP SET sparingly. Make only simpleprovisioning changes in order to limit the time needed for semantic checks.

SNMP SET is rejected with a return code of 'genErr' if:

• the edit view is different from the current view

• another user is in 'provisioning mode'

• a software upgrade has been done, and a full semantic check has not yetcompleted. (The first semantic check after a software upgrade is a compcheck of all provisioned data and may take a long time.) Once acheck provhas been done from the console, telnet session, or fmip session, SNMP Sare accepted.

SNMP standard MIBSupport for RFC 1657 “Border Gateway Protocol Version 4” is introduced in trelease.

For a complete list of standard MIBs supported by SNMP refer to NTP241-6401-300Passport SNMP User Guide.

SNMP Enterprise MIB considerationsYou can view all operational and provisionable attributes using SNMP. To taadvantage of SNMP for surveillance purposes, you must have a workstationequipped with a standard SNMP package such as HP OpenView. You mustconfigure Nortel Networks’s SNMP Enterprise MIB, which is provided with thsoftware.

For further information, see:

• the README file in the MIBs directory on the software distribution site

• NTP 241-6401-300Passport 6400 SNMP Guide

SNMP Enterprise MIB changesThe Passport Enterprise MIBs are Nortel Networks’ proprietary MIBs formanaging Passport.

This section identifies the Passport Enterprise MIBs that are new in this relethe MIBs which have been modified, and the MIBs that have not been modifi

A modified MIB indicates that the existing contents are modified or thatadditional informational elements are added.

New MIBs• nortelPP-bgpV1_BG00SBB.mib



• nortelPP-callRedirectionV1_BG00SBB.mib• nortelPP-frTraceRcvrV1_BG00SBB.mib• nortelPP-huntGroupEngV1_BG00SBB.mib• nortelPP-huntGroupV1_BG00SBB.mib• nortelPP-modAtmQosV1_BG00SBB.mib• nortelPP-modDprsQosV1_BG00SBB.mib• nortelPP-pcusaV1_BG00SBB.mib• nortelPP-tdmalwfV1_BG00SBB.mib• nortelPP-virtualMediaV1_BG00SBB.mib• nortelPP-vnetEurolsdnV1_BG00SBB.mib• nortelPP-vnetMcdnSigV1_BG00SBB.mib

Modified MIBS• nortelPP-appnV1_BG00SBB.mib• nortelPP-atmNetworkingV1_BG00SBB.mib• nortelPP-atmTrunksV1_BG00SBB.mib• nortelPP-bitTransparentV1_BG00SBB.mib• nortelPP-bridgeV1_BG00SBB.mib• nortelPP-casTestV1_BG00SBB.mib• nortelPP-dcmeV1_BG00SBB.mib• nortelPP-dpnRoutingV1_BG00SBB.mib• nortelPP-dpnTrunksV1_BG00SBB.mib• nortelPP-dprsMcsEpV1_BG00SBB.mib• nortelPP-frameRelayAtmV1_BG00SBB.mib• nortelPP-frameRelayNniV1_BG00SBB.mib• nortelPP-frameRelayUniV1_BG00SBB.mib• nortelPP-generalVcInterfaceV1_BG00SBB.mib• nortelPP-gsmIwfV1_BG00SBB.mib• nortelPP-ipV1_BG00SBB.mib• nortelPP-ipiFRV1_BG00SBB.mib• nortelPP-ipiVcV1_BG00SBB.mib• nortelPP-ipxV1_BG00SBB.mib• nortelPP-lanDriversV1_BG00SBB.mib• nortelPP-logicalProcessorV1_BG00SBB.mib• nortelPP-mgmtInterfacesV1_BG00SBB.mib• nortelPP-modCommonV1_BG00SBB.mib• nortelPP-mpaNetworkLinkV1_BG00SBB.mib• nortelPP-nstaV1_BG00SBB.mib• nortelPP-serverAccessRsaV1_BG00SBB.mib• nortelPP-snaV1_BG00SBB.mib• nortelPP-softwareV1_BG00SBB.mib• nortelPP-timeV1_BG00SBB.mib• nortelPP-traceBaseV1_BG00SBB.mib• nortelPP-vcTesterV1_BG00SBB.mib• nortelPP-voiceNetworkingV1_BG00SBB.mib• nortelPP-virtualRouterV1_BG00SBB.mib• nortelPP-vnetEtsiQsigV1_BG00SBB.mib• nortelPP-vnetNisSigV1_BG00SBB.mib• nortelPP-vncsCallServerV1_BG00SBB.mib• nortelPP-voiceV1_BG00SBB.mib



• nortelPP-x25TraceRcvrV1_BG00SBB.mib

Unchanged MIBs• nortelPP-alarmV1_BG00SBB.mib• nortelPP-atmBaseV1_BG00SBB.mib• nortelPP-atmBearerServiceV1_BG00SBB.mib• nortelPP-atmCoreV1_BG00SBB.mib• nortelPP-atmIispV1_BG00SBB.mib• nortelPP-atmMpeV1_BG00SBB.mib• nortelPP-atmPnniV1_BG00SBB.mib• nortelPP-atmUniV1_BG00SBB.mib• nortelPP-baseRoutingV1_BG00SBB.mib• nortelPP-baseSnmpV1_BG00SBB.mib• nortelPP-callServerV1_BG00SBB.mib• nortelPP-circuitEmulationServiceV1_BG00SBB.mib• nortelPP-dataCollectionV1_BG00SBB.mib• nortelPP-dataIsdnV1_BG00SBB.mib• nortelPP-disdnETSIV1_BG00SBB.mib• nortelPP-disdnJapanInsV1_BG00SBB.mib• nortelPP-disdnNI2V1_BG00SBB.mib• nortelPP-disdnNISV1_BG00SBB.mib• nortelPP-disdnTS014V1_BG00SBB.mib• nortelPP-extensionsV1_BG00SBB.mib• nortelPP-fileSystemV1_BG00SBB.mib• nortelPP-fraDpnTrunksV1_BG00SBB.mib• nortelPP-frameRelayDteV1_BG00SBB.mib• nortelPP-frameRelayEngV1_BG00SBB.mib• nortelPP-frameRelayIsdnV1_BG00SBB.mib• nortelPP-frameRelayMuxV1_BG00SBB.mib• nortelPP-frameRelayNniTraceV1_BG00SBB.mib• nortelPP-frameRelayNniV1_BG00SBB.mib• nortelPP-frameRelayUniTraceV1_BG00SBB.mib• nortelPP-frf5EpV1_BG00SBB.mib• nortelPP-hdlcTransparentV1_BG00SBB.mib• nortelPP-imaV1_BG00SBB.mib• nortelPP-kurtNetV1_BG00SBB.mib• nortelPP-laneClientV1_BG00SBB.mib• nortelPP-mcsMgrV1_BG00SBB.mib• nortelPP-netSentryV1_BG00SBB.mib• nortelPP-porsAtmTrunksV1_BG00SBB.mib• nortelPP-porsTrunksV1_BG00SBB.mib• nortelPP-porsVcV1_BG00SBB.mib• nortelPP-pppV1_BG00SBB.mib• nortelPP-provisioningV1_BG00SBB.mib• nortelPP-ruvStateSummV1_BG00SBB.mib• nortelPP-shelfV1_BG00SBB.mib• nortelPP-sourceRouteEndStationV1_BG00SBB.mib• nortelPP-standardTextualConventionsV1_BG00SBB.mib• nortelPP-subnetInterfaceV1_BG00SBB.mib• nortelPP-textualConventionsV1_BG00SBB.mib



Stateed in

nary

• nortelPP-trunksV1_BG00SBB.mib• nortelPP-unackTrunksV1_BG00SBB.mib• nortelPP-usefulDefinitionsV1_BG00SBB.mib• nortelPP-utpDpnTrunksV1_BG00SBB.mib• nortelPP-vnsV1_BG00SBB.mib• nortelPP-x25DteV1_BG00SBB.mib

SNMP rolled up variable considerationsThis section lists the component classes which are supported in the PassportSummary Table. The OSI state and status of each component class is trackthe form of rolled up state variables. An SNMP management application caoptimize the polling of state values with the use of the Passport State SummTable.

Table 9SNMP Rolled Up Variables Supported Component Classes

Supported Component Classes ReleaseSupported

LogicalProcessor P7.0

LogicalProcessor Ethernet P7.0

LogicalProcessor Fddi P7.0

LogicalProcessor DS3 P7.0

LogicalProcessor E3 P7.0

LogicalProcessor DS1 P7.0

LogicalProcessor E1 P7.0

LogicalProcessor V35 P7.0

LogicalProcessor X21 P7.0

LogicalProcessor TokenRing P7.0

LogicalProcessor Sonet P7.0

LogicalProcessor Sdh P7.0

LogicalProcessor JT2 P7.0

LogicalProcessor Hssi P7.0

LogicalProcessor IlsForwarder P7.0

LogicalProcessor Eth100Bt P7.0

LogicalProcessor InverseMultiplexerAtm P7.0

Shelf Card P7.0

FileSystem P7.0

FrameRelayNni P7.0

FrameRelayUni P7.0

FrameRelayAtm P7.0



tion

f

ksure

r

ts,ry

less57

vice

EngineeringThis section provides information about engineering considerations. This seccontains the following subsections:

• “Multiple services per shelf” (page 72)• “Maximum supported feature set per shelf” (page 72)• “Multiple applications per function processor” (page 73)• “Function Processor sparing” (page 75)• “Agent queue size” (page 75)• “PORS Mux mode directly connected to a first generation ATM FP”

(page 75)• “PORS Map mode on ATM IP FP” (page 76)• “ATM IP FP - first generation ATM FP Interwork” (page 76)• “PORS Degrade Alarm” (page 77)• “Frame Relay engineering” (page 77)• “Frame Relay Trace engineering” (page 77)• “IpiVc and IpiFr coexistence engineering” (page 78)• “Use of standby CP during software migration” (page 78)• “Spooled files” (page 78)

Multiple services per shelfA Passport can be configured to operate with many different combinations oFunction Processors and services on each shelf. As the number of servicescombined on a single shelf increases, make sure that there is sufficient truncapacity and that proper priority is placed on the various service types to encorrect congestion handling.

Contact your Nortel Networks Networks Technical Support representative foadditional information.

Maximum supported feature set per shelfCertain service mixes, combined with a large number of defined componenconsume a large quantity of memory. Ensure that Control Processor memomonitoring is part of the regularly scheduled network monitoring activities.

To configure Control Processor memory monitoring, use the “d LP/0” command.The sum of normalRam and sharedRam under memoryUsageAvg should bethan 22 Mbytes on a CP1. For CP2 and CFP1, the sum should be less thanMbytes.

If you have any questions regarding the memory consumption of different sermixes, contact your Nortel Networks Networks Technical Supportrepresentative.

AtmInterface P7.0

Table 9 (Continued)SNMP Rolled Up Variables Supported Component Classes

Supported Component Classes ReleaseSupported



ering

r:

AMted

er of

ell

g

ILSby

ldis

ns

.

Ps,

Multiple applications per function processorFunction Processors can support multiple services. Performance and enginecomplexity increases with the number of services configured.

Consult your Nortel Networks Networks Technical Support representative foengineering assistance. Use the following guidelines for high level planning

• Theorder in which services are entered in the ‘SW LPT/xx’ featureListassociated with a given FP is important. Services are loaded in the Fast Rof an PM1 FP based on the order in which you enter them in the associa‘SW LPT/xx’ featureList. Not all the services and their prerequisites will beplaced in Fast RAM in situations where memory runs low. Additionalservices and prerequisites may be loaded in Normal RAM, adverselyaffecting performance.

Note: Second Generation Function Processors do not use fast RAM. Therefore the ordentry does not matter on Second Generation hardware.

• If you configure a VNS service to carry ILS traffic over Passport frame-ctrunks, you must configure all ILS function processors, and all functionprocessors carrying ILS traffic, with VNS.

• If you configure ATM MPE to carry ILS traffic over ATM facilities, you mustconfigure all ILS function processors, and all function processors carryinILS traffic, with ATM MPE.

• You can configure a Function Processor with both Frame Relay UNI andFrame Relay DTE services, with DTE and DCE port interfaces connectedrolled cables or through the use of a virtual framer. In addition, you shoulimit the number of frame relay PVCs to ILS Service connections only. In thcase, Accounting, Bridging and Frame Relay SVC are not supported.

• Use Function Processor multiple application combinations only if fanout(port connectivity) is of concern and cost reduction is of interest whenplanning the introduction of new products. Do not use this solution whenperformance is a consideration.

•Do not use multiple application combinations when high performance of aspecific application is required. If you use multiple application combinatioyou should split the multiple application combination to take optimumadvantage of the FP’s memory and performance capabilities.

The following two tables list applications and services supported on each FPThis does not imply that all the applications/services shown can operateconcurrentlyon an FP.

For details on the application/service combinations supported on individual Fsee thePerformance Specification Reference GuideNTP 241-6401-100.

Note: For the all the tables in the Engineering Consideration section, anapplicationis defined as a generic type, such as Frame Relay (FR). Eachapplication is composed of individualservices, such as FR UNI, FR NNI, FRSVC, and FR Trace in the case of Frame Relay.



ther

Appli

TrunkRouti

DPV

RoutiDPV

DPNoo

FramFFFFFF

PANLDTIS

VTDSHBV

ILS:IPIPTSSSNPFXGL

ATM:AAAAAP

PackO

Note

Note

Note

Note

Note

Please contact your Nortel Networks Technical Support representative for furassistance.

Table 10Applications/services supported by processor cards

cations /Services

Processor cards

V.1

1

V.3

5

DS

1(4

-por

t)

E1

DS

3

E3

DS

1(8

-por

t)

HS

SI

DS

1C

E1C

DS

3C

Eth

erne

t(10

M)

Eth

erne

t(10

0M

)

FD

DI

Tok

enR

ing

ILS

forw

arde

r

CF

P1

DS

1A

TM

(3-p

ort)

E1

AT

M(3

port

)

JT2

AT

M

DS

3A

TM

E3

AT

M

OC

-3A

TM

DS

1A

AL1

E1

AA

L1

DS

1A

TM

(8-p

ort)

E1

AT

M(8

-por

t)

12m

Vsp

Aa1

2pD

S3c

Aa1

32p

E1

Aa1

s:ng systems for Passport Frame / Cell Trunks:PRS x x x x x x x x xORS x x x x x x x x xNS see Note 2: x x x x x x x x xng systems for Passport ATM Logical Trunks:PRS x x x x x x x xORS x x x x x x x xNS see Note 2: x x x x x x x xGateway:ver UTP x x x x x x x xver FR x x x x x xe Relay:R UNI x x x x x x x x x x x xR NNI x x x x x x x x x x x xR SVC x x x x x x x x x x x xR Trace x x x x x x x x x x xR-ATM interworking x x x x x x x x x x x xR ISDN x x

see Note 5edicated mode x x x x x x x xunnelled mode x x x x x x x xDN access x x x:DLC Transparent Data x x x x x x x xit Transparent Data x x x x xoice Access

x x x x x x x x x x x x x x x x xX x x x x x x x x x x x x x x x x x

ransparent Bridging x x x x x x x x x x x x x x x x xRB x x x x x x x x x x x x x xRES x x x x x x x x x x x x x xNA Data Link Routing x xetSentry x x x x x x x x x x x x x x x x xPP x x x x x x x x x x x xR DTE x x x x x x x x x x x x.25 DTE x x x x xeneralVcIf x xANE Client x x x x x x x x x x

AL1 CES x xTM Bearer Service x x x x x x x xTM networking (UNI,IISP,PNNI) x x x x x x x xTM MPE x x x x x x x x x x x x x x x x x x x x x x x xTM IMA x xacket Voice Gateway over ATM x x xet Voice Gateway PVG:ver Atm x x x

1: An “x” shown in a column indicates that a service (listed by row) is supported on a function processor (displayed in columns).

2: VNS includes transport of all LAN Upper Layer Protocol (ULP).

3: When ATM MPE operates on CFP1, it is assumed that an ATM FP and an ILS Forwarder FP will run beside it.

4: For FR-ATM interworking and FrDTE, both logical and physical connections on the same FP are supported.

5: Supported on PM2 only.



le,to

theruld be

fery

00,

orted

umSuxbe

Table 11Voice and bit transparent data services applications/services supported byfunction processorsApplication combinations

Function Processor sparingWith the introduction of Second Generation Function Processors (for exampPM2 based FPs), it is very important that you use only like-generation FPsspare active FPs. A First Generation FP should be spared by another FirstGeneration FP, a Standard Second Generation FP should be spared by anoStandard Second Generation FP, and a Premium Second Generation FP shospared by another Premium Second Generation FP.

Agent queue sizeIn order to engineer the number accounting agent queue size, the amount omemory available on the FP is enough to hold two accounting records for evconnection, up to the number of connections supported on the FP.

For example, if a DS1C PM2 premium FP supports up to 5000 Frame Relayconnections, then the agent queue size can be set to 5000 * 2 = 10000 withoutrisk of memory exhaustion.

For a DS1C PM1 FP, the maximum supported number of connections is 10and the maximum recommended accounting agent queue size is 2000.

Increasing the size of the accounting agent queue beyond two times the suppnumber of connections may cause memory exhaustion on the FP.

For more information on engineering call management, see 241-6401-600Passport 6400 Operations and Maintenance Fundamentals.

PORS Mux mode directly connected to a first generation ATM FPWhen a PORS trunk running Mux mode connections on a new ATM IP FP isdirectly connected to a first generation ATM FP that does not have the minimrequired software level active, then on average three out of every four PORconnections that are setup are software forwarded. If running either AAL5 Mmode or SPO Mux mode in these scenarios, the remote node should either

Applications/Services 1pDS1V 1pE1V J2MV 1pDS1Mvp 1pE1Mvp TTC2MMvp

Bit Trans. Data x x x x x x

Voice Service (VS) x x x x x x

DCME x

Voice Networking (VNET)

EQSig x x

NISig x x

casSig x x x

Note 1: The above services are typically completed by specific audio capabilities such as: ECAN, SAD,CSAHELP, LD-HELP, ADPCM, PCM, alternate fax, fax relay, TPT. Please refer to the specific service descriptionfor further information.



nalering

FPonlyare

priateould

for/

s to

upgraded to the appropriate level of software (as indicated below) or additioprocessor overhead for these connections should be factored into the engineof the ATM IP FP.

Release 5.1: BE01S4F (SSUP 5.1.4)Release 7.0: All loads.

PORS Map mode on ATM IP FPAny node in the network that is performing frame-to-cell conversion forconnections that traverse PORS trunk running Map mode on a new ATM IPalso require a minimum software level to be active. Otherwise, on average,three out of every four PORS connections that originated from these nodessetup to be software forwarded. If running either AAL5 or SPO Map mode inthese scenarios, the network nodes should either be upgraded to the approlevel of software or additional processor overhead for these connections shbe factored into the engineering of the ATM IP FP.

Instances of frame-to-cell conversion are:

• VOICE, BTDS or HTDS plc services going to a Map mode trunk

• Mux mode trunk going to a Map mode trunk

• Frame-based trunk going to a Map mode trunk

• Switch VOICE services going to a Map mode trunk

• MCS going to a Map mode trunk

Note 1: CES and Map mode trunk perform cell-to-cell relay.

Note 2: Minimum required software releases must be active in networksPORS to fully enable H/W forwarding on ATM IP FP based cards (6K/7K15K):

— Release 5.1: BE01S4F (SSUP 5.1.4)

— Release 7.0: BG00SBB (R7.0.11)

ATM IP FP - first generation ATM FP InterworkThree new attributes have been added to the ca:maxAutoSelectedVpi,maxAutoSelectedVciForVpiZeroandmaxAutoSelectedVciForNonZeroVpi.These attributes limit the maximum value that msb will autoSelect whenestablishing switched connections. This is required to allow ATM IP FP cardsucessfully interwork with first generation ATM FP cards.

The following conditions apply to these attributes (and are enforcedby semantic checks):

• The Max value must be greater than or equal to the minimum value.

• The MaxVpi must fit inside the defined vpi bit range (8 or 12 bit vpi)

These attributes form a subset of the "programmable" vcc space, which



as,

ap.

e list,hen

efer

s

nss.

t

f

iver.

ifnd.

means they apply to both first generation ATM FP and ATM IP FP cards. OnATM IP FP card the programmable vcc space is only limited to 65535 (that imax int).

• On a Non-Connmap card:

— MaxAutoselectedVci must be less than 65535

• On a Connmap Based Card:

— The maximum values must fit inside the range defined by the connm

— So the maxAutoselected values must be less than their equivalentconnmap settings.

PORS Degrade AlarmIf PORS trunks stage when there are a large number of features in the featurPORS services may use normal memory rather than high speed memory. Wthis happens, a MSG alarm (7018 0003) is issued. The remedial action is toreduce the value ofmaxLcfor each Path Administrator on the card. For moreinformation, refer to 241-6401-435Passport 6400 Path-Oriented RoutingSystem Guide.

Frame Relay engineeringWith the increase in feature content and service combinations on Passportswitches, the maximum DLCI limits per Function Processor have changed. Rto Frame Relay and Performance documentation for information aboutengineering the network.

FR MMTC traffic may starve lower Emission Queue traffic if too much MMTCtraffic is sent. This causes the FrUni Lmi to go down since control traffic goethrough Emission Queue 2.

In some networks, you may be able to implement Frame Relay configuratiothat exceed the documented Nortel Networks deployment recommendationBefore doing so, consider the risks of not being able to operate the sameconfigurations under future software releases. For more information, contacyour Nortel Networks Networks representative.

Frame Relay Trace engineeringThe following recommendations apply to Frame Relay Trace:

• One trace session per FP is recommended if the traced port has a framethroughput greater than 500 frames per second.

• You can trace all ports of an FP simultaneously if the frame throughput oeach port does not exceed 100 frames per second.

• Traced frames should be truncated and filtered by DLCI, if possible, toreduce the load on the network to transport the traced frames to the rece

• Always truncate frames larger than 256 bytes.

• Do not trace an FP which is running at a CPU utilization greater than 75%the port to be traced has a throughput greater than 500 frames per seco



ring

y CP

an

e

e

ws

n

ur

te

ofle,ess

• Do not trace an FP which is consistently using more than 300 Kbytes ofshared message blocks out of a 512K byte maximum.

IpiVc and IpiFr coexistence engineeringThe total number of connections should not exceed 24 (the existing engineenumber) during migration.

Use of standby CP during software migrationIn order to reduce the service outage during a software upgrade, the standbis now used in the following manner:

• Standby reboots with the new software (no change from P5.x).

• Standby loads the provisioning data (no change from P5.x).

• Standby saves the data in commit format.

• Switchover occurs, and commit-style activation is performed.

Note: Even though the data save in step (3) is in commit format, that file cnot be commited because the version of software that saved the dataoriginally is not the same version of software that will be running once thmigration is complete.

You must issue ‘copy prov’ and ‘check prov’ commands before commiting thprovisioning data.

Spooled filesThe ‘maximumNumberOfFiles’ attribute of the Spooler component now allothe following values to be configured:

1-200:maximum number of files is 1-200

0: no maximum

Be aware of the following considerations when setting this parameter:

• If you end up with the maximum number of files allowed on the disk, you ruthe risk of losing spooled information.

• Leave enough spare in the maximum number of files allowed to allow yooff-switch entity to retrieve the files from the switch.

• If you use the ‘unlimited’ setting you run the risk of filling the disk withspooled files, at which point all spooling stops and the disks losesynchronization. When using the ‘unlimited’ setting, ensure that the off-switch entity retrieving the files is able to keep up with the file generation raof the switch.

• If you were using the ‘unlimited’ setting, then there will be a large numberfiles on disk. Changing the attribute to a non-unlimited setting (for examp1-200) will cause the switch to erase all files from the disk that are in excof the new maximum. The oldest files are removed first.



ese

E,

over.

t orcerent

ss a

ual

Base ConsiderationsUnsupported card types

The card types listed in “Application and service combinations supported byATM PDC 1.0 and PDC 1.1 function processors” appear when you issue thePassport command:

> help shelf card cardtype

Cards defined for future use are not supported. Cards listed as obsolete areretained in the CAS help function for reference by customers who still use thcard types (athough you can no longer order the cards).

Hitless CP switchoverThe behavior of APPN services (SNA), LAN services (IP, IPX, Bridging), LANmedia (Ethernet, Token Ring, FDDI), VNS, WAN services (Frame Relay DTX25 DTE, PPP) and ATM FPs supporting ATM MPE are unchanged by thisfeature. These services and configurations do not support Hitless CP Switch

When you issue a switchover Lp/0 command, the command fails if the currenedit view differs from the committed view. You can use the -force option to forthe CP switchover, but then you lose all unsaved provisioning data in the curor edit view. Also, to run the committed view, the FP running uncommittedprovisioning data goes down.

Passport starts a 10 minute timer after the Hitless CP switchover recovery icomplete. If the newly active CP fails within that 10 minutes, Passport initiatefull shelf reset. This mechanism protects against faulty CPs that wouldcontinually request CP switchovers. At this time, the timer also handles manswitchovers triggered using one of the following commands:

• reset lp/0

• restart lp/0

• reset sh ca/<active_cp>

• restart sh ca/<active_cp>

Table 12Unsupported Card Types

Card Type Notes

DEV1 Future use

DEV2 Future use

CFP2 Future use

4pEthAui Obsolete



helf

d

Snotandsedly,

edstem

romporto 50

sh.

testd. Ifthe

ortS1C

tionans

loady beres to

and

The use of any of these commands while the timer is active results in a full sreset. Switchover triggered with the command ‘switchover lp/0’ while the timer isactive results in a Hitless CP Switchover and is subject to the limitations anconditions described in 241-6401-600Passport Operations and MaintenanceDescription.

CAS congestionWhen responding to a command requiring a large number of responses, CAmay appear to be temporarily unavailable to other requests. While you maysee an immediate response to CAS commands, CAS still receives the command responds in due time. If you continue to input the same command repeatyou are adding to the load on CAS.

CP crash caused by LCM,GCM and RemoteCallAgent using all msg blockWhen there is a protocol port going down and that protocol port is provisionwith transparent bridge protocol (TB), there is a chance that CP's message sywill be congested when the CP tries to flush out all cache entries that learn fthat port to all FPs. For example, if there are 600 cache entries learned fromA, and if port A goes down, 50 messages (say 600 cache entries packed intmessages) are sent to each FP. If there are 14 FPs configured (50*14) 700messages are sent in a very short period of time. In some cases, if there areenough cache entries, the congestion can be very heavy and the CP will cra

Manual Loopback Test on E1CIf the external loopback is applied to an E1C port after the manual loopbackhas started, incoming frames to the port under test may not be acknowledgethe external loopback is established before the manual loopback is started,test will run properly.

V.54/PN127 Loopbacks on DS1C/E1COnly one V.54 or PN127 Remote Loopback test per DS1 (V.54 only) or E1 pis permitted. This means a total of four concurrent tests are permitted per Dor E1C card.

Processor memory fragmentation issuesAs software features are deleted and added through provisioning and activacycles, the processor memory may become fragmented. Fragmentation methat large blocks of contiguous memory are no longer available to load newsoftware modules.

Once a certain level of fragmentation has occurred, it may not be possible tonew software, and in the worst case processor card resets may occur. It manecessary to reset the Function Processor or examine the load order of featuensure the optimal use of Function Processor Memory. Consult your NortelNetworks Networks Technical Support representative for further informationassistance.



(or

e test

ing

by

d to

nt.

ists

hasd to

Bus Clock Source statusBy default, the provisionable attribute Shelf Test automaticBusClockTest isdisabled. To check the current setting of the attribute, issue the followingcommand:

display -p shelf test automaticBusClockTest

It is more likely that the value for clockSourceStatus, under the Shelf Bus/XY) component, is set to ‘unknown’ after a relevant condition changes (forexample, an LP state goes down).

When the Passport Shelf is in dual bus mode, you can start a bus clock sourcmanually by issuing the following command:

run shelf test

After the test has been completed, observe the results by issuing the followcommand:

display shelf test

Observe the statuses of the Active CP and the Alternate Bus Clock Sourceissuing the following command:

display sh bus/x (bus/y)

For further information, refer to 241-6401-605Passport 6400 Operations andMaintenance Guide.

Trunks, DPN gateways and networkingManagement Data Provider support

Management Data Provider Release 13.4 (or higher) with Solaris is requiresupport Passport Networks running this 7.0 release.

Loadsharing engineering considerationsBefore you deploy the Loadsharing feature, review and consider the NortelNetworks Networks Passport Loadsharing Engineering Guidelines documeYou can obtain these guidelines from your Nortel Networks Networks FieldService representative. Loadsharing fast is a new algorithm on ATM IP

PORS LRC checking updatedLRC checking has been set to ‘on’ for all message types. LRC issetwhenmessages are sent andcheckedwhen messages are received. This update assin detecting errors.

Full trunk statisticsThe addition of a new spooled record for each Trunk AtmAccess componentthe impact of adding extra records to the DCS spooling queues. You may neeincrease the DCS agentQueueSize.



heg

inthe

thatl orved.

esM1

irust

se

ce

ng

list

tures.

Note: DCS also has important changes in regards to spooling in P5.1. TagentQueueSize for spooled statistics should follow the P5.1 engineeringuidelines.

The old statistics being kept in the operational view do not exactly matchprevious statistics. Specifically, the DPRS statistic is always counted in itsappropriate emission priority because of the multimedia bit being introducedthe “Passport DPRS Multimedia RCDS” feature. This is opposed to havingdispatcher using the higher interrupting queues to determine interruptingstatistics.

Some of the older attributes are now being replaced by newer attributes. Notecustomers will be allowed time to update any operation procedures (manuaautomated) in order to use the new attributes, before the old ones are remo

ATM port statisticsAs part of the ATM Spooled Port Statistics feature, two new operationalattributes are added to the AtmIf component. “txLinkUtilization” and“rxLinkUtilization” display the average AtmIf link utilization during the mostrecent minute, expressed as a percentage.

MCS considerationsA customer wishing to use DPRS MCS may perform the following procedurduring migration to avoid a possible disruption of service at a later time. Thiapplies to the provisioning of the dprsMcsEp and dprsMcsAgent features on PFPs.

In order for the DPRS MCS Agent and DPRS MCS EP LPs to get the fastmemory they require, they must be provisioned first on the feature list of therespective SW LPTs. To ensure they get the fast memory they require, you mbring up the FP with these features during initial loading. If you provision thefeatures on their respective FPs through incremental loading, there is noguarantee that they will acquire the fast memory they require and performanmay be degraded until the FP is reset.

To prevent this type of service disruption, you may wish to perform the followisteps during the software upgrade:

1 Determine on which LPs the DPRS MCS Agent feature is required.

2 Provision the DPRS MCS Agent feature as the first feature on the featureof the SW LPTs of the identified LPs.

3 Determine on which LPs the DPRS MCS EP feature is required.

4 If you are going to provision both features on the same LP, provision theDPRS MCS Agent feature as the first feature and the DPRS MCS EP feaas the second feature for the feature list of SWLPTs for the identified LP

5 Proceed with the software upgrade.



hich

tureastM1

urces

hat

that

illCP

sure

er

to

nlp)

You can skip this procedure if an adequate maintenance window exists in wthe LP can be provisioned and reset without service disruption.

Note: There is no guarantee, regardless of the provisioned order of the fealist, that the DPRS MCS agent and the DPRS MCS EP will acquire the fmemory they require if the porsTrunks feature is also provisioned on the PFP.

The MCS manager should reside on a processor card where adequate reso(memory/CPU) exist and where it does not introduce a new single point offailure. Following, in order of preference, are the processor choices:

1 transport (trunk) FP, especially if all of the MCS connections go through tFP

2 access (Frame Relay) FP, especially if all MCS connections terminate onFP

3 other FP

Note: This introduces a new single point of failure.

4 CP2, note that CP1 is not supported. On dual CP nodes, the active CP wreset, and the MCS manager will be out of commission until the standbytakes over.

5 single CP node or CFP1 node.

Note: There are the limitations on MCS combinations by card type. SeePerformance NTP’s for more information.

Frame Relay

Frame Relay migrationWhen migrating a set of FRF.5 nodes from 4.2 to 7.0 (or a later release), enthat the software version running before the migration starts is at least 4.2.7(BD02S7G). It is impossible to establish FRF.5 connections between a nodrunning release 7.0 and another node running a software version of 4.2.6 oearlier.

Refer to “Use of standby CP during software migration” (page 78). Also referNTP 241-6401-900Passport 6400 Frame Relay UNI Guide.

FRF.5 2K ScalabilityThe MCSMgr can support up to 128 endpoints with 2000 DLCIs whenprovisioned on a PM2 Premium or Standard card. However, the MCSMgr caonly support 32 endpoints with 2000 DLCIs when provisioned (as candidateon an ATM card.

Rapid Start/Stop of DLCI loopback causes card resetAn FP containing a DLCI will eventually restart if you apply the followingcontinuous pattern of data loopback commands on a PVC while the PVC isrunning traffic:



ued

stion.

m)nP

es.n thethe

cess

may

if

st

s 3,

thethen

<start data loopback on this PVC><stop data loopback on this PVC><start data loopback on this PVC>

This condition can only occur if the frequency of the loopback commands issin this pattern is less than four seconds apart.

Frame Relay TraceWhen you use this capability with theNexustracesoftware (developed by NexusTelecom AG), you may experience lock-ups of the trace session under congein a Unix SUN OS environment. When this occurs, restart the trace session

If you use theNexustracetool to capture and analyze the information from thePassport Frame Relay trace capability, it is recommended that you useNexustraceversion 3.2 or higher. Contact Nexus directly for further details.

FR-ATM Gateway with Virtual Framer and LP sparingThe components of a FR-ATM Gateway (either a FrUni or a FrNni, and a FrAtcan be provisioned on separate LPs logically linked by a virtual framer. Wheone or both of the LPs are configured for LP Sparing, failure of the primary Lresults in an outage of the frame relay service significantly longer than if thegateway had been co-located on the same card.

FR-ATM now requires atmNetworking to be in Sw Avl avListThe atmNetworking application is required for existing users of Fratm servicThis is now the case because the FrAtm package now has a dependency oatmNetworking feature. No change in the Sw Lpt/x featureList is required butatmNetworking application must be present in the Sw Avl avList.

If the feature is not present, the semantic check required by the migration profails and notifies you about the actions necessary to rectify the situation. Noimpact on service results from this migration issue but the migration processbe delayed while the feature is added.

FRF.5 and ATM traffic managementThe establishment of an FRF.5 ATM SPVC is subject to the same rules andlimitations as one originating from an AtmIf Vcc Src component. In particular,the SPVC is to route through a Passport ATM interface on which UsageParameter Control (UPC) is enabled, the derived ATM traffic parameters murespect the hardware limitations described in 241-6401-700Passport 6400 ATMOverview, chapter 2, under section ‘UPC provisioning restrictions’.

These considerations apply to Frame Relay connections using traffic policie4 and 5 only.

Data Loopback with Resiliency ‘A bit’ conditionThere is an A-bit condition that occurs when data loopback is used with PVCresiliency (backup). While data loopback is active on the PVC primary slave,PVC is redirected to the backup slave (perhaps due to some link failure), and



perat

d tocan

ve,ck

tiont IEsn

ameort

t

ort

and

nd

and

ut

redirected back to the primary slave when the failure is resolved. This is profunctionality. However, at this point, the DLCI on the master end indicates ththe PVC is down by way of the A-bit status, and discards all ingress traffic.

You can stop loopback on the primary slave before the PVC is re-establishethe primary slave. Once the PVC is re-established on the primary slave, youstart loopback again. If the PVC is already re-established to the primary slaand the A-bit condition is active, you can remove this condition by issuing a lothen unlock on the DLCI of the primary slave.

Frame Relay over EuroISDNNon-Zero Codeset UsePassport’s ‘Frame Relay over ISDN’ feature supports only codeset 0 informaelements (IE). Incoming ISDN calls to Passport containing non-zero codesein the SETUP message are released if they are encoded as “comprehensiorequired”.

ILSIP CoS

The Passport IP CoS feature provides the following:

• support for Layer 2 based ingress packet classification. VC based for FrRelay DTE, VC-based ingress packet classification on ATM MPE, and pbased for all other media capable of bearing IP packets on Passport.

• support on LAN and non-ATM WAN media for ToS based ingress packeclassification (where CoS is determined by any bits within the ToS octet,including the DiffServ Code Point)

• support on LAN and non-ATM media for Flow based ingress packetclassification (where CoS is determined by IP Address, protocol, and L4 pinformation).

• CoS to egress QoS mapping on Frame Relay DTE using multiple DLCIsusing a single DLCI.

• CoS to egress QoS mapping on ATM MPE using multiple VCCs (max. 4) aa single VCC.

LimitationsUnsupported interworkings include:

• IP CoS with NetSentry

• IP CoS with NHRP

• IP CoS with LANE

ToS based and Flow based ingress packet classification on the ATM IP FP (CQC FP with and without the ILS Forwarder card) is not supported.

ToS marking of ingress packets on ATMIP FPs (and CQC FP with and withothe ILS Forwarder card) is not supported.



colto

d

92)

s”

forelyrt,

Note: You can assign groups of policies either to a Virtual Router’s ProtoPort (Vr Pp) or to a Virtual Router’s IP component. Policy groups assigneda Vr Ip are applied to all protocol ports under that virtual router that don’thave policy groups assigned directly to them. If a policy group is assignedirectly to a Vr Pp then the policies in that group completely replace anypoliciey groups assigned to the Vr Ip.

For more details, please see NTP 241-6401-815Passport IP Routing User Guide

ATMThis section provides information about ATM. This section contains thefollowing subsections:

• “IMA migration” (page 86)• “IMA-specific enhancements” (page 86)• “ATM processor operation” (page 87)• “Maximum ATM connections” (page 87)• “Maximum number of ATM test and loop components” (page 87)• “OC-3 Multi Mode Optic Source” (page 87)• “ATM Trunk Utilization Alarm” (page 88)• “8 port DS1/E1 ATM card independent and IMA links” (page 88)• “Port Sparing of 4 ports or less on 8-port DS1/E1 IMA cards” (page 89)• “ATM Resource Control (ARC) migration” (page 90)• “ARU reporting section” (page 90)• “Changes to the Atmif transmit queue limit defaults” (page 91)• “Queue Limit Software Errors in 7.0 against OC3MM-CQC” (page 91)• “3pDS/E1A to 8pDS/E1A card migration” (page 91)• “3pE1A to 8pE1A Linetype migration” (page 92)• “ATM Function Processor crashes after CPSO and LP switchover” (page• “Virtual Path Termination (VPT) Phase 1” (page 93)• “ATM SPVC accounting” (page 93)• “ATM Cell Transfer display” (page 93)• “Provisioning of subConnectionPool and lnnConnectionPool on ATM card

(page 94)

IMA migrationFor information regarding the migration from the Proprietary Protocol to theATM Forum Protocol, use the IMA migration procedure provided in NTP241-6401-730Passport 6400 Inverse Multiplexing for ATM Guide.

IMA-specific enhancementsAny new IMA-specific enhancements are expected to be implemented onlythe ATM Forum protocol. The proprietary protocol is intended to be used solfor backwards compatibility with previous implementations of IMA on Passpoand will eventually be phased out.



k

ithonRy

e

s

ssorsintsction-100

TM

oryntscan

ed

ver,af

ATM processor operationIf the ingress side is over-engineered with frame traffic (that is, too much linbandwidth allocated to trunk applications), the Passport ATM card willexperience receive queue congestion and traffic will be discarded. If trunks wdifferent ATM Service categories (for example, rtVBR and nrtVBR) are usedthe same ATM interface and there are a large amount of frames on the rtVBtrunk, the ATM FP could spend 100% of the time servicing the higher prioritqueues (for example, rtVBR) causing the low priority queues (for example,nrtVBR) to build up and discard. These lower priority trunks will go down if thhigh priority trunks sustain this CPU usage.

These considerations apply equally when the higher priority traffic originatefrom ATM Bearer Service or PORS services.

You must use proper engineering guidelines to avoid ingress frame queuestarvation.

Maximum ATM connectionsEnhancements to Passport software and the introduction of Function Procewith larger memories have increased the total number of ATM connection posupported by each Function Processor. For details on the number of connepoints of a given type supported on a Function Processor, see NTP 241-6401Passport Performance Specifications Reference Guide.

Maximum number of ATM test and loop componentsThe ATM connection verification capabilities provided by the Test and Loopcomponents are intended for use in validating the correct operation of new Ainterfaces and connections. Since these capabilities are usually requiredinfrequently, these components have not been optimized with respect to memutilization. As a result, provisioning large numbers of Test or Loop componeon an ATM FP could lead to memory exhaustion problems. These problemsbe avoided by adhering to the following recommendations.

• Do not configure more than 30 Loop components on an ATM FP. Analternative, which uses a Nrp component linked to itself, has no suchrestriction.

• The number of Test components running on an ATM FP should not excethree.

OC-3 Multi Mode Optic SourceSingle mode and multi mode ATM OC-3 FPs may be interconnected. Howethe OC-3 multi mode ATM FP receivers may be over-driven if connected tosingle mode OC3 ATM transmitter. In lab or short haul circuits, a minimum o5db of optical attenuation must be provided in the circuit between the single



t beode

lti

ngle

er

eduxhe5

nlsue

ameper-nt

inks

the

TM

can

mode transmitter and the multi mode receiver if this type of connection musmade. The following rules must be observed when interconnecting single mand multi mode OC-3 ATM FPs:

• The fiber that is connected to the single mode transmitter must be singlemode up to the attenuator. The fiber between the attenuator and the mumode receiver may be either single mode or multi mode.

• The fiber that is connected between the multi mode transmitter and the simode receiver must be multi mode. The multi mode transmitter will notcouple optical energy into single mode fiber.

• The total multi mode circuit length must not exceed 2 km.

• The multi mode circuit attenuation must not exceed 10 dB.

Interconnection of a multi mode OC-3 ATM FP to a long haul single mode fibcircuit requires the use of a multi-mode to single-mode converter device.

ATM Trunk Utilization AlarmFor the ATM Trk Util Alarm, the utilization calculation is only provided for theAAL5 VCC. It does not account for the traffic received by VCCs that is managdirectly by Trk PA. Be aware that the traffic on the companion VCCs in SPO Mmode and Map mode trunks is not considered by the utilization alarm. Set talarm thresholds v according to the amount of DPRS, VNS, and PORS AALMux traffic that the link is likely to carry.

When the Critical alarm is received by Preside Multiservice Data Manager(formerly known as NMS), Preside Multiservice Data Manager (formerly knowas NMS) will mark the trunk as being Out Of Service. The trunk itself will stilbe up but nearing saturation if the threshold is set correctly. If this may be an isfor you, disable the critical alarm by setting the threshold to 200%.

8 port DS1/E1 ATM card independent and IMA linksIndependent links and IMA link groups may be used simultaneously on the sFP provided they have unique instance numbers. When traffic shaping andVc queueing is disabled on the 8-Port DS1/E1 ATM FPs, up to 8 independelinks or IMA groups are supported. However, when traffic shaping or per-Vcqueueing is enabled for any number of ports on the FP via theperVcQueueInterfaces attribute of the Arc component, only 4 independent lor IMA groups are supported regardless of whether or not traffic shaping isenabled or per-Vc queueing is used on the associated AtmIf components. Inlatter case only independent link instances 0-3 or IMA instances 0-3 aresupported.

To take best advantage of the full service suite now available on the 8 port AFP, the minimum vintage must be 'CA' (8pDS1A --> NTFN14CA, 8pE1A -->NTFN16CA). For previous vintage cards, if ATM UNI and/or networking(IISP) is defined on the majority of the ports, a maximum of 400 connectionsbe supported.



oop)senotd

ds

willo,

Theortnot

links

rs

ons.

er-cesd on

no

orts

and

el. Inrtsg

Those DS1/E1 port tests which generate test patterns (card, manual, remoteLare permitted only when the port is bound to an AtmIf component. Thus, theport test types are supported only on independent links. This restriction doesapply to the other test types (externalLoop, payloadLoop) which may be useeven if the port is configured as part of an IMA link group.

In Release P4.1, the number of connections for the 8-port DS1/E1 ATM carwas provisioned through the connectionPoolCapacity for port 0. The Arccomponent attribute totalConnectionPoolCapacity (values 0.10752, default3072) supersedes the use of the connectionPoolCapacity attribute. The Arcbe modified automatically during the migration process, if the Arc exists. Alsthe default Arc supports the use of totalConnectionPoolCapacity.

The connectionPoolCapacity attribute must now be set to 0 for these cards.connectionPoolCapacity attribute may still be used for cards other than 8-PDS1/E1 ATM FPs if the desired distribution of connections across ports canbe achieved using the totalConnectionPoolCapacity attribute.

This totalConnectionPoolCapacity indicates the maximum number ofconnections (both VCC and VPC) that are available across all independentand IMA groups on the logical processor. Increasing the value oftotalConnectionPoolCapacity decreases the number of frame and cell buffeavailable on the FP.

When using the new totalConnectionPoolCapacity attribute of the Arccomponent, port 0 and port 1 of three port cards are limited to 2560 connectiThe connectionPoolCapacity attribute can be used to bypass this limitation.

The Arc component attribute perVcQueueInterfaces (values 0.4, default 0)indicates how many independent links or IMA groups support shaping and pVc queueing on the logical processor. For more information on which instanof independent links or Ima groups support shaping or per-Vc queueing basethe value of the perVcQueueInterfaces attribute, see NTP 241-6401-700Passport 6400 ATM Overview.

The default for the perVcQueueInterfaces attribute is 0 which means that noindependent port or IMA group supports shaping or per-Vc queueing. WhenArc component exists the system uses the default value.

Port instances or IMA instances are used to determine which interface supptraffic shaping and per-Vc queueing. Based on the value of theperVcQueueInterfaces attribute the port instances that support traffic shapingper-Vc queueing are (0), (0,1), (0,1,2,3).

Port Sparing of 4 ports or less on 8-port DS1/E1 IMA cardsSparing/Fanout of 4 ports or less is supported using a single termination panthis case the provisioned ports should be in the range of 0-3 (or 4-7) and pooutside this range should not be provisioned without a corresponding sparin



nel

ort

nt

on.

ap:

ityes).

ortrt 0an

%4%

me.me

panel connected. Failure to connect a sparing panel when a port has beenprovisioned causes the FP to poll looking for it and causes a “click” in the paserving the other bank of ports.

ATM Resource Control (ARC) migrationThe following are the actions taken for Arc components that already exist.

Migration of connectionPoolCapacity attribute:

• The connectionPoolCapacity attribute is kept as is and thetotalConnectionPoolCapacity is set to 0.

• For 8 Port DS1/E1 ATM Card, the value of connectionPoolCapacity for p0 is migrated to the totalConnectionPoolCapacity attribute. TheconnectionPoolCapacity is set to 0.

• The shapingStackAllocation attribute is migrated to theperVcQueueInterfaces attribute. Note that this migration preserves thesystem capabilities.

The following are situations where you must add an Arc to ensure backwardcompatibility:

• If there is no Arc component and shaping is in use by an AtmIf componebound to port 0 of the Lp:

— an Arc component will be created with the perVcQueueInterfacesattribute set to 1 (all other attributes are set to their default values).

— the unshapedTransmitQueueing attribute of the AtmIf is set to comm

• If there is no Arc component, the Lp is a 3 port card type and the ConnmSpace for any atmIf linked to a port of this Lp is between 1025 and 1536

— an Arc component will be created with the totalConnectionPoolCapacattribute is set to 4608 (all other attributes are set to their default valu

Otherwise, the Arc is not created and no independent link or Ima group willsupport shaping or per-Vc queueing on the logical processor. This can beconsidered to be a degradation of the system capabilities as port 0 did suppshaping or per-Vc queueing by default before the migration. To preserve poability to support shaping or per-Vc over migration, you should explicitly addArc component before the migration and set perVcQueueInterfaces to 1.

ARU reporting sectionThe default values for the tx and rx frame memory allocation of 50% and 80respectively, are now measured in cells. This corresponds to partitioning of 4and 76% respectively in bytes.

The minimum amount of buffer space reserved for cells and frames is the saHowever, as both quantities are reported in cells the value for the minimum frabuffer memory appears larger.



rombeen

uteor

ic

....

in

will

Changes to the Atmif transmit queue limit defaultsThe effective default values of the transmit queue limits remain unchanged fprevious Passport releases. The value reported in the operational view haschanged to reflect the value that is actually being used by the hardware.

It is important to note that a value of zero (0) for the transmit queue limit attrib(txQueueLimit), under a particular ATM interface, indicates that the default fthe card type will be used.

For more information, see NTP 241-6401-700Passport 6400 ATM Overviewfordetails on the default values for the transmit queue limits.

Queue Limit Software Errors in 7.0 against OC3MM-CQCThe following SWERR (software error) occured when running the Qlimit TraffManagement test suite against 0C3MM-CQC FP's in the BG00S4C andBG00S5A software loads. This has also been seen against other CQC FP's8pE1Atm, 8pDS1Atm, 3pDS3Atm, 3pE3Atm. Some connections mayexperience unexplained traffic loss.

EM/NODERA9; 2000-12-03 12:29:39.60

MSG indeterminate processing softwareError 00009000

ADMIN: unlocked OPER: enabled USAGE: active

AVAIL: PROC: CNTRL: ALARM: STBY: notSet UNKNW: false Id:03000006 Rel: Com: Stack trace:_startDispatching_v__16EeDispatcherBaseUc_handleCasRequest_v__17AtmBaseCasHandlerR13AtmCasRequest_handleCasRequest_v__17AtmCompCasHandlerR13AtmCasRequest_changeConfiguration_v__20AtmNailedupConnPointRC20AtmTrafficProvStruct _software__FPCcT0iT0RUi Int: 3/1/2/7205;atmNailedupConnPoint.cc; 318; p7.0d.35

3pDS/E1A to 8pDS/E1A card migrationIf you provision a three port DS1 or E1 ATM card with an Arc that has valuesthe connectionPoolCapacity vectors, perform the following steps during the3pDS/E1A to 8pDS/E1A migration process:

1 Enter provisioning mode.

2 Change the card type under Shelf Card/x

set Shelf Card/x cardtype 8pDS1Atm

3 If the Lp/x Arc is present:

— Set the totalConnectionPoolCapacity to three times the highestconnectionPoolCapacity value. This will ensure that semantic checkspass.

— set Lp/x Arc totalConnectionPoolCapacity <value>

— Set all the connectionPoolCapacity vectors to zero.



casanhe

As

s to

CDrbith

ots)

intonot

casallylot

ed

Pill,

f

— set Lp/x Arc connectionPoolCapacity 0 0 1 0 2 0

4 Check and activate the provisioning.

For more information, see NTP 241-6401-700Passport 6400 ATM Overview.

3pE1A to 8pE1A Linetype migrationThe 3-port E1 ATM FP (3pE1A) supports a lineType of either cas or ccs, withbeing the default. Since the 3pE1A uses a non-ATM specific framer chip it csupport signalling multiframe framing, and therefore can use lineType cas. T8-port E1 ATM FP (8pE1A) supports only a lineType of ccs, since it uses anATM-specific framer chip that does not allow access to the timeslot 16 bits.the usefulness of signalling multiframing is questionable on unchannelizedinterfaces, this is not normally a problem. Connecting an E1 with lineType caan E1 with lineType ccs results in Signalling MultiFrame Loss Of Frame(SMFLOF) alarms on the cas E1, since the ccs E1 is not transmitting thesignalling multiframe alignment bit in timeslot 16.

E1 channel associated signalling (cas) involves the use of 4-bit signals (ABbits) transmitted in timeslot 16 of the interface, with one set of ABCD bits petimeslot. Also contained in timeslot 16 is the signalling multiframe alignmentand the Signalling MultiFrame Remote Alarm Indication (SMFRAI) bit, whicis set to 1 on transmit when a SMFLOF is detected.

E1 common channel signalling (ccs) involves the transmission of layer 2/3messages in timeslot 16, for instance by an ISDN protocol stack which usestimeslot 16 as its D-channel. These messages refer to the channels (timeslcarried by the interface.

Since both cas and ccs signalling types are only applicable to channelizedinterfaces (for example, those whose total payload bandwidth is divided uptimeslots), and ATM interfaces are not channelized, cas and ccs signalling doapply to ATM interfaces.

Passport E1 components have an attribute “lineType”, which may be eitheror ccs. In the case of unchannelized interfaces, the effect of this choice is reto enable signalling multiframe framing in timeslot 16 (cas) or to ignore times16 completely (ccs).

When migrating an FP from a 3pE1A to an 8pE1A, if the 3pE1A’s ports wereprovisioned with lineType ‘cas’, then their lineType will need to be reprovisionto ‘ccs’ on the 8pE1A as well as on the interface at the remote end.

ATM Function Processor crashes after CPSO and LP switchoverCustomers may observe that an ATM Function Processor crashes after a Cswitchover if a LP switchover is performed soon after the CPSO. The card whowever, return to full service after the CP switchover. Therefore, it is notadvisable to do a LP switchover immediately following a CPSO, especially ithere is traffic arriving at the LP.



thees’t

ound

tine.

PIthatnor, if

butentlyum.

te

.

tag.

At the time of a switchover or card reset, there is a brief time window whereactual interrupt handlers for CQC interrupts are not yet bound in. If traffic arrivat this time, a defaultHandler gets invoked. Since the default handler doesnhandle specific interrupts it is possible to get a watch dog timeout due tointerrupts that remain continuously asserted. Once the actual handler gets bin, the offending interrupt is handled properly.

Changes have been introduced into the defaultHandler to minimize theprobability of a time out but since it is not the intent of this handler to handlespecific interrupts no further changes are intended for the defaultHandler rou

Virtual Path Termination (VPT) Phase 1The considerations for the deployment of VPT Phase 1 are listed below.

Reserved Vci valuesWhen a VPT is provisioned on a given VPI, VCI values 3 and 4 within that Vcan not be used. For example, if Vpc/3 is provisioned as a VPT, this meansVcc/3.3 and Vcc/3.4 must not be provisioned. In Phase 1 of VPT, there aresafeguards in place to prevent those Vccs from being provisioned. Howevethese Vccs are used, the ATM FP will eventually crash.

Minimum value required for ConnMap numVccsPerNonZeroVpiBefore you can successfully create and use a VPT VPC, the ConnMap attrinumVccsPerNonZeroVpi must have a value of 8 or greater. There are curreno safeguards in place to prevent you from using a value less than this minim

No elastic connections permittedAt this time, VPT does not fully support bandwidth elastic connections.Therefore, they should not be provisioned in conjunction with a VPT. Forexample, if there is VPT provisioned with VPI=3, all Vccs in the VPI=3 rangemust be provisioned as bandwidth non-elastic connections.

ATM SPVC accountingYou can provision an ATM SPVC (Soft Permanent Virtual Circuit) to generaaccounting records in two different ways. The first method involves enablingUNI/IISP accounting at the ATM interface used by the SPVC. The secondmethod involves enabling PVC accounting at the ATM interface, thenprovisioning a correlation tag for the SPVC. If you use both methodssimultaneously, the SPVC generates two distinct sets of accounting records

To prevent this duplication of accounting information, provision a correlationfor a SPVC only if UNI/IISP accounting is not enabled on the ATM interface

ATM Cell Transfer displayCurrently, Cell Transfer display is supported only on SPVP and SPVCconnections with segment switch-side loopbacks provisioned.



es

nsed in

pted

nksork

less

onis

ohad

lllete

ist

Provisioning of subConnectionPool and lnnConnectionPool on ATM cardsThe number of sub-connections and logical network number (LNN) resourcmay now be changed on the ATM card (subConnectionPoolCapacity andInnConnectionPoolCapacity attributes under the LP ARC component).

A sub-connection is used for interworking the ATM services with the frameoriented services such as Frame Relay, and Path Oriented Routing System(PORS). When a frame is received at a sub-connection, the frame header ismodified to be compatible with service to which it is forwarded.

Due to limited resources, not all of the provisioned number of sub-connectiomay be allocated. The actual number of sub-connections allocated is indicatthe sum of LP Aru subConnectionPoolAvailable and Lp AruSubConnectionPoolUsage attributes.

When the sub-connection pool is exhausted, no more connections are accefrom the services that use this pool.

A logical network is a subset of passport modules together with a subset of truthat interconnect those modules. It carries the traffic for a defined set of netwprotocols. A LNN is used to identify a logical network. The connectionlessservices which use the logical networks require some processing at theintermediate nodes.

This pool is allocated at the intermediate nodes to sustain these connectionservices.

Due to limited resources, not all of the provisioned number of LAN connectiresource records may be allocated. The actual number of records allocatedindicated by the sum of Lp Aru ConnectionPoolAvailable and Lp ArulnnConnectionPoolUsage attributes.

ATM NetworkingMigration

When migrating from R5.0 to R7.0, the AtmCr component will be migrated tthe ARtg component. You must delete the AtmCr component once the nodebeen upgraded to R7.0.

If the AtmCr and ARtg components are both provisioned, the check prov wigive the following error message: “AtmCr component is obsolete, please deit.”

Passport ILMI not UNI 3.0/3.1 compliantIt may take significant time to enable ILMI between a Passport and a non-Magellan switch after cable is disconnected and reconnected. The problemcaused by Passport ILMI 3.0/3.1 implementation which is not fully complianwith the UNI 3.0/UNI3.1 standard.



M3.0/

sfer

C is

rs

r

d

thr

Cs.

Passport ILMI 3.0/3.1 implementation does not support SNMP queries of ATmanagement information across the UNI as defined in Chapter 4 of the UNI3.1 specification.

Perform the following steps to increase the speed of the ILMI recovery:

1 Disable address registration on Passport.

> Set atmif/x uni ilmi operatingMode addressRegDisabled

2 Check and activate provisioning. At this point the ILMI comes up and asignalling VCC is created.

3 Enable address registration on Passport.

> Set atmif/x uni ilmi operatingMode addressRegEnabled

4 Check and activate Prov.

Provisioning SPVCsMax CTDThe provisionable range of the attribute maxCtd under the atmlf/Ca/Cbr andatmlf/Ca/rtVbr components is 0 to 2147483647. Provisioning 16777215 orhigher means that a SPVC passing through this interface will incur a cell trandelay equal to this value. The SPVC will fail because the maximum ordo notcarevalue in the fwdQosParameters under the VCD component of the SPVequal to 16777215.

CLRThe valid range for the CLR in the fwdQosParameters or bwdQosParameteunder the VCD is 0 to 15 or 255 for thedo not carevalue. In future releases, asemantic check will fail an invalid entry.

Reserved channelsReserved channels for signalling on an ATM interface are given priority ovePVCs, SPVCs, and SVCs when the system checks to see if Ca/maxVcc isreached. However, on FP resets, this priority is not maintained; the softwareadmits PVCs and SPVCs first. This admits a maximum of maxVcc PVCs anSPVCs and fails to set up the reserved channel.

SPVCsSPVCs do not support different values in the txPacketwiseDiscard andrxPacketwiseDiscard attributes under the Vcd component. You must set boattributes either to INDICATED or NOTINDICATED. The result is PPD is eitheON or OFF in both directions. This limitation does not apply to PVCs and SV



r alllP

idthIfllingll of

nts)s aic

sage

es

tely.

l

d

Changes in the IEs for the service categories for all SPVC interfacesChanges were made with the encoding of IEs for all the service categories foSPVC interfaces. The encodings for P5.1 SPVCs are summarized in “Seriainterface combinations with WAN transport of LAN supported on CFP1” in NT241-6401-100Passport Performance Specifications Reference Guide.

ATM signalling channel failure on IMAA problem can exist when a signalling channel is created in the rtVBR bandwpool by using dynamic bandwidth control to create VCCs in the IMA feature.there is bandwidth reduction and the signalling channel goes down, the signacannot come up because the elasticity of the connection will have claimed athe available bandwidth.

ATM accounting for N-PVCsDocumentation for this feature is available in NTPs 241-6401-650Passport 6400Accounting Reference, 241-6401-700Passport 6400 ATM Overview, and241-6401-030Passport 6400 Overview.

Provisioning permanent VCCProvisioning a permanent VCC (with Nrp, Nep, Test, and Loop subcomponeusing the same VPI.VCI as a dynamic VCC with a Dst subcomponent causesoftware error. The correct behavior is the permanent VCC clears the dynamVCC and uses its VPI.VCI designation. Practice careful connection space uto avoid provisioning permanent connections above theminAutoSelectedVciForVpiZero or minAutoSelectedVciForNonZeroVpi valuunder the AtmIf Ca component.

Private Network to Network Interface (PNNI)PNNI is a complex standard and it is important that you understand it complebefore modifying default values for the various timers that the protocol usesPoorly chosen values can result in unexpected behavior that could impactnetwork functionality. You should not modify timers without consulting NorteNetworks Data Network Engineering personnel.

Currently PNNI does not support operation when the database is in overloastate.

Table 13P5.1 IE encodings for the service categories for all SPVC interfaces

ServiceCategory

BearerClass

TrafficType

TimingRequired

BestEffort

CBR X CBR end-to-end

VBR-rt X VBR end-to-end

VBR-nrt X VBR No

UBR X VBR No Yes



nsring

en

fic.

Pe

ach

d.

ed

euse

m

Random path sharingWhen routing to a node, if there are multiple paths with the best optimizatiometric, then the PNNI routing algorithm randomly chooses one of them. Thimethod of choosing the routing paths also provides a mechanism of load shaon equal parallel links (see definitions below).

Definitions1 Two links are consideredparallel if they connect the same nodes.

2 Two links are consideredequal if they have the same value for theoptimization metric.

Omitting links from the route computation processIf a link has the value for the optimization metric (that is, AW, CTD, CDV)equalto 0, then it isomitted from the route computation. For example, if theoptimization metric is AW and a link has the administrative weight set to 0, thit is not considered in the route computation.

ILS on ATMIP FPThe Passport ILS on ATMIP FP feature provides:

• Improved performance (relative to ILS on CQC FP) for processing IP traf

• Elimination of the need to have an ILS Forward Card when processing Itraffic over the ILS on ATMIP FP. This allows the card slot occupied by thILS Forwarder Card to be freed up. The architecture is more scalable; eILS on ATMIP card does its own forwarding., rather than sharing theresources of an ILS Forwarder Card. In addition, bus utilization is reduce

• Increased memory capacity of the ATMIP FP allows more featurecombinations than do previous FPs.

LimitationsThe following limitations apply:

• LANE media processing is not supported on ATM IP FP.

• IP Tunneling is not supported on ATM IP FP.

• Loadsharing is not supported on ATM IP FP.

• VNS load spreading on ATM IP FP does not work when ATM IP FP is usas an ingress module into VNS network. This problem is tracked by SRnumber 10375439.

• The data transferred from port 1 of the 100 BaseT card doesn't follow thVFF (very fast forwarding) hardware assisted data path, while port 0 canit in the same test environment. The problem may be caused by somehardware differences between port 0 and port 1, which prohibits the datatransferred from port 1 to become CAM eligible. As a result, the data froport 1 uses the software forwarding scheme and has a lower throughputcompared with port 0.



re

2 (a

ses

limiton

wareeg” (a

orc

can

e.1.

AAL1 Circuit Emulation Service (CES)Migration

When migrating from to R7.0 with existing unstructured AAL1 service to ensuthat you perform the following steps:

• The new Sw Av for aal1Ces must be downloaded:

set sw dld avListToDownload ! aal1Ces_BG00SBB

start sw dld

• The new sw LPT for aal1Ces must be added and the LP set to use it:

set sw lpt/AAL1FP featureList ! aal1Ces

set lp/x logicalProcessorType sw lpt/AAL1FP

Check, activate, confirm, save and commit the provisioning changes.

• Ensure that existing aal1Ces services have a minimum bufferSize of 28previous default value was 240):

display aal1Ces/* bufferSize

If not, use the set command to change them.

set aa1Ces/x bufferSize <bufferSize>

Check, activate, confirm, save and commit the changes.

Changing the txQueueLimit with AAL1 CES connections activeChanging the transmit queue limit (txQueueLimit) is a critical change that cauthe ATM interface to be reset. As a result, enabled AAL1 CES calls on aparticular interface are dropped if changes are made to the transmit queuewhile such AAL1 CES connections are active. This applies for any applicatirunning over an ATMIF exhibiting the “txQueueLimit” critical change.

CES over PORSIn a Passport network where the backbone nodes are running pre-P4.1 softand the nodes at the edges are running P4.2, the AAL1 CES cells will not bcarried across the backbone over PORS because “Dynamic NSAP addressinnew P4.2 feature) does not exist in pre-P4.2 nodes.

New bandwidth limits for 4p E1 and DS1 AAL1 cardsBecause there are limitations on the number of timeslots that can be used fstructured services without exceeding the bandwidth of the card, a semanticheck has been introduced in 5.1 (SR 10209545) to ensure that AAL1 FPsrunning structured services are not provisioned with more timeslots than theyhandle.

Some AAL1 configurations which have been up and running in some releaslevels of 4.2 and/or 5.0 may fail the first semantic check after upgrading to 5



S1

ntoh

l

1onsd

d

The new bandwidth limits which have been implemented for 4 port E1 and DAAL1 cards are as follows. (There are no bandwidth limits when onlyunstructured services are present on a card). The Partial Fill level is taken iaccount for the bandwidth calculation such that the actual bandwidth for eacservice on a card is:

((provisioned ts * maximum partial fill level) + (provisioned partial fill leve- 1)) / provisioned partial fill level

Maximum partial fill level is a constant which is equalled to 47.

The Bandwidth limitation for the maximum provisioned timeslots on 4 port Eand DS1 AAL1 cards are listed in the tables below. The bandwidth calculatifor each service are rounded down to the nearest integer prior to being tallietogether and displayed in the following tables:

Table 14Bandwidth limitation for E1 Card

Table 15Bandwidth limitation for DS1 Card

VoiceVoice Networking Gateways

New Gateway Pairs- In Release 7.0, it is possible to place voice, modem anFacsimile calls between the following PP6400 CCS and CAS protocal pairs:

Effective size of largest service on card CAS no CAS

1-12 72 106

13-18 65 98

19-24 62 94

25-30 60 92

Effective size of largest service on card CAS no CAS

1-12 88 96

13-18 77 96

19-24 72 96

Table 16- PP6400 CCS and PP6400 CAS Pairs

PP6400 CCS PP 6400 CAS

E1 ETSI QSig DS1CAS

DS1 ETSI QSig DS1CAS, E1 CAS

E1 MCDN DS1CAS, E1 CAS

DS1 MCDN DS1CAS, E1 CAS

DS1 NIS DS1CAS, E1CAS



t isto

ny

nd

wo

r

oescond

code

port

Table 17- PP6400 CCS and PP4400 CAS Pairs

These pairs are in addition to the existing E1 ETSI QSig to E1 CAS pair thaalready available. Note that the Gateway feature does not yet support CCSCCS protocol gateways.

Data Calls - data calls between E1 and DS1 are not currently supported in acombination of protocols.

MVPE G.729A Voice EncodingIn Release 7.0, the G.729A voice encoding algorithm is supported on theE1Mvpe, DS1Mvpe and TTC2mMvpe FP's. It is twice as efficient as G.729 ainterworks fully with G.729 on MVP and MVPE FP's on earlier releases ofsoftware

MVPE V.17 Fax Relay at 14.4 and 12.0 kbit/sWithout V.17 fax relay, there are two alternatives for handling a call between tfax machines that support V.17 in a Passport subnet with MVPE cards:

• force the fax machines to downspeed to 9.6 kbit/s and encode the trafficthrough the Passport subnet using V.29 fax relay at 9.6 kbit/s

• encode the traffic through the Passport subnet using G.711 at 64 kbit/s oG.726 at 32 kbit/s

There are disadvantages to both of these alternatives. The first alternative dnot allow the fax machines to transmit at their highest possible speed. The sealternative uses a lot of bandwidth through the Passport subnet. With theintroduction of V.17 fax relay, a third alternative is available:

• allow the fax machines to transmit at their highest possible speed and enthe traffic through the Passport subnet using V.17 fax relay

This alternative is the best possible case. The fax machines are allowed totransmit at their highest possible speed, while bandwidth usage in the Passsubnet is kept as low as possible. V.17 fax relay is available for both VoiceTransport and Voice Networking on MVPE FP’s

Provisioning Voice Networking - relay encoding minimum rateIn Release 7.0 Voice Networking, ensure that you set the Vncs/n Vp/xmodemFaxRates encoding relay rate min to 0. Otherwise, a warning will beissued explaining that the min relay rate is irrelevant.

PP 6400 CCS PP4400 CAS

E1 ETSI QSig DS1CAS, E1 CAS, Analog

DS1 ETSI QSig DS1CAS, E1 CAS, Analog

E1 MCDN DS1CAS, E1 CAS, Analog

DS1 MCDN DS1CAS, E1 CAS, Analog

DS1 NIS DS1CAS, E1 CAS, Analog



tesame

e.g.

PROV 6> ch pr

Vncs/2 Vp/1

Warning:

Attribute: modemFaxRates

Reason: The minimum relay rate is not relevant. Set the minimum relay

rate to 0 kbit/s to avoid this warning.

Prov

ok 2000-04-03 10:33:08.29

MCDN Anti-tromboningMCDN feature Anti-tromboning will fail to activate between R7.0.11 andprevious releases of 7.0 and 5.1. For the Anti-tromboning feature to workcorrectly it must terminate and orginate on the same voice route, signallingchannel, voice subroute, switch voice service, and node id. If a call originathrough a HgS there is no guarantee that the call will be terminating on the snode or same vroute.


103

sms

e”d) for

Appendix AKnown Limitations

Table 18 contains a list of Change Requests (CR) which document problemfound in this load or previous loads which are not yet resolved. These problewill be fixed in this load with patches, or in a subsequent load.

Fixed CRs are moved to Appendix B “Resolved Limitations since last releas(page 104) in the release notes for the load in which the problem is fixed, anthen moved to Appendix C “Items Resolved in Previous Releases” (page 110subsequent releases.

The table is followed by details regarding the service request..

Note: There are no "known issues" for this release.

Table 18 Service requests

Item CR ID CustRefNumber Platform Module Title


104 Appendix B Resolved Limitations since last release

d

n

lue

er

Appendix BResolved Limitations since last release

The following table is a list of SRs that have been resolved since P7.0.10.

Table 19Limitations resolved since last release

# CR ID CustRefNumber(ID Number)

Title

1 Q00305898-01 GVT/PP/MVPe: High BER during lp/x e1/0 test when using type car

2 Q00306108-10 Attempting to autoselect the last available VPI hangs FP

3 Q00306147-06 010515-3865 Crash: Cfra4 NMI has occurred at interrupt level

4 Q00306222-07 memAudit tool is broken for PQC based cards

5 Q00306266-15 False report of congestion condition on 4pOC3 FP

6 Q00307432-05 PROP: Check prov fails after activation - VR duplicate vpi found

7 Q00307625-04 010918-4905 .pd files are deleted from passport disk after sw dld

8 Q00308034-02 PORS: Manual Path with Forced BW is broken (BTDS calls cannotstage)

9 Q00312799-01 Prop: 4pMVPe:StdUipeCodec.cc and UipeDchanMaint.cc swerrs oloopback,add ch31

10 Q00312979-01 FUNC: txQosParameters:ctd value not displaying correct default va

11 Q00313012-04 Software error in vnetUipeDchanMaint.cc; 1358, incomplete info

12 Q00313061-12 020411-11221020418-18235020503-37153020513-45956020624-93155020708-07723020807-41362020904-71853030213-49908

NST: No more local msg blks LMB on 1pE1Mvp card

13 Q00314937 100BaseT: 100BaseT Ethernet card crahes when IfState changed

14 Q00315368 VRRP alarms: memory overwrite, wrong NTP indexes, etc.

15 Q00315483 PtoMP SVCs are not properly released on 2pOC3MmAtm2 card

16 Q00315527 010822-3954 Crash.Reason:Module Data For Virtual Circuits not available (Pointis NULL)

17 Q00315528 011126-57034020916-85239

9000 Alarm: ifEntryFp.cc; 641; p7.0d.30

18 Q00315531 010918-4500 Unacked Trunk pa maxReservableBwOut Problem

19 Q00315545 011025-24210 011025-24210: 100BaseT card crash


Appendix B Resolved Limitations since last release 105

s

m.

d

20 Q00315546 011004-13095 Crashes on FP cards running mpanl protocol

21 Q00315560 PROP: Ipport Ingresspacket trace filtering enhancement

22 Q00315613 020314-78294020724-25815

LinkDestination Address of PPP connection is in RDB but not in FWDtable

23 Q00315927-01 TB Bridging: Bridge port remain in disable state after unloc

24 Q00315928-01 ATMIP: Bridge traffic getting dropped after card reset

25 Q00319716 020214-45456020305-66460020523-58367021009-13706021024-31425030220-57788

Passport Allow 2 Vr to have management access when provisionthrough MDM.

26 Q00336691 020404-02005021111-51851021112-53412030211-46801

Traffic delay during CP switchover is better with CP1s than with CP2

27 Q00365022-08 011127-58882021008-12251021030-39393030205-40726030213-49964

IMA link imbalance

28 Q00385377 020222-54526 Card reboot when HTDS plc "local address" changed.

29 Q00390178-01 1pMVpe Card crash when PBX card re-install

30 Q00412517-04 020607-75305 Prop: Anti-Tromboning fails on first attempt, then intermittently duringtraffic

31 Q00415413 pp6k SWERR during Prov for OSPF Export ripInterfaceinwIpRtmOspfAreaTbl.cc

32 Q00418956-06 UNI signalling remains disabled after VCC goes down and then up

33 Q00422483 020429-31476 Typo in .fdc file for load 7.x

34 Q00422811 020430-32200 tProf top command causes card to Crash

35 Q00428330 020711-12562 1pDS1V NMI crash in BG0046A - UIPE_L3 (0x0253970) was nearaddress 0xd003a804

36 Q00429612 020411-11115 MDM13.2: Customer has proxy alarms raised as a result of a clr alar

37 Q00430209 pp6k, fruni ch pr passed, when side is network, pvcconfig is yes andlci >300

38 Q00453541 020528-62907 100BT vrrp with instant 255, master doesn;t reply to ping request

39 Q00456071 020530-66629 Q931 signalling compatibility issue

40 Q00456684-08 Traffic loss between Atmif vcc and Fratm dlci



Title



fter

set

eT)

es

ol

r

41 Q00461459 020604-70962 7.0.9 ATMIP cards resetting with no traceback at CPSO

42 Q00464703-02 020306-68139 Prop: No more message block on 1pE1Mvp card

43 Q00472733 020624-93672 7.0 ATMIP FP needs reset/re-seat after node reset/power-cycle

44 Q00474928 pp6k, sddetoclpmapping in fratm siwf and niwf is not working properlyin spvc

45 Q00475063 020610-77674 Netsentry filter not working properly under tbp

46 Q00477276 pp6k: fratm ca nddetoclpmapping value always1 is not workingcorrectly.

47 Q00482647 020709-09054 PP7K Passport is Switching Between CPs About Every Hour

48 Q00483893 020620-90364 E1C card crashes with config as PP4400 ISDN backup

49 Q00491469-02 1pMVPE: DSP SW version not properly retrieved from permanentDSP signature

50 Q00491623 020717-18856 RelayBC cause rxFrameMemoryUsage go up; frames are dropped ait reach thresh

51 Q00492550 020726-29439 7.0.10 Swerr during ch pr when LA not connected to LP Port.

52 Q00493468 020717-18772 P7.0.10: MAC addresses switch following sw migration from P5.x

53 Q00496567 020729-30231 ABC/Pp6k E1C PPP session up/down caused 2pATMIP card autore

54 Q00500955 020712-13168 09000 alarm raised when DPNGateway went down

55 Q00501847-01 020708-07084: CBOS12 Card/11 crash

56 Q00502692-04 020327-93085 IP cache entry stuck in "pending" state on Fast Ethernet FP (100bas

57 Q00503257-05 SBIC Addresses needing to be included for firmware fix (32 addresstotal)

58 Q00503342 020807-41581021105-45151

Static route NH in FWD table is broadcast address of another protocport

59 Q00513087 Bandwidth allocation MPANL-MVP interworking

60 Q00514029-05 CR to have IPD timer value of 1s to be submitted into mainstream

61 Q00514844 020904-72688 OS Debug trace is always on, when IP policy group is configured folayer 2

62 Q00515653-01 4p GW: Vnet MCDN to Vnet NIS call protocol error

63 Q00519242 020909-77326 Frames lost in network incrementing when using Cas on Rel 7.0.10

64 Q00520513 Adjust the solution for a previous submission in p7.0d.51

65 Q00520854 020506-37917 CTPE8 Lp/4 and Lp/9 crashing - MCS MGR

66 Q00524095-02 PROP to 7.0.10B -- IE not forwarded transparently

67 Q00524099 ATMIW: Software error at line 336 in file sbqGeneral.cc duringinterrupt 236



Title



ed

r

ith

te

68 Q00524572 020618-87470 SPVC active at 4460, but no SPVC at 6400

69 Q00524780-01 020710-09987 PROP: 00009000 Software Error - Invalid Data in CHID

70 Q00525136-01 Software DLD Process does not allow patch download from PC basSDS.

71 Q00530480 020926-98716 SWERR occurs after activate prov

72 Q00531351 MPANL bug. Debug printf statement not removed from code.

73 Q00531560 020927-00219 Attribute ""tableVersion"" under VR IP BGP is always 0

74 Q00533669 021002-05173 V35 ports osiUsage will become idle during port lock/unlock or whenremote equip

75 Q00534794-02 100% CPU utilization on FP due to incorrect calculation of free CAMentries

76 Q00538464 021015-20317 atmmpe ac inunknownprotos attribute incrementing permanently onshelf

77 Q00548254-05 021024-32129021025-33816

021024-32129: crash in HE_check_segment_ie

78 Q00549882 FUNC: Cannot telnet to ethernet port after re-activation

79 Q00550060 6400 does not implement a restart procedure for DLCI-0

80 Q00552139 Software error (9000 alarm) after deleting and adding a VR runningbridging (TB)

81 Q00552257 Ingress packet tracing for IP not working on ATM IP FPs for HWforwarded packets

82 Q00553114 021031-41404 one static route missing from rdb after lock/unlock vr/x pp/x

83 Q00554724 021104-43759 TR SNA DLR crashes with NMI (local bus error)

84 Q00556943-02 Remote end Negotiation Cause Poor voice quality

85 Q00558853 021024-32028 OSPF route(s) not in RDB on 7.0.10.

86 Q00560635 021110-51761030107-07333

SW Fault: BG00SAB when receiving RIP updates

87 Q00562609 021028-36485 Proxy alarm on MDM after lock/unlock of E3 port. Clear not sent opestate disab

88 Q00562792-02 011219-86005 DAT/GVT/PP: Fax collect calls are not being possible from LDA toMGA.

89 Q00563486 021009-13706 VR: correct the behavior of the managemet VR

90 Q00566642 021106-48059 PP6K: R7.0.9: 2pOC3Mm: Trunks do not restage after card reset wAPS configure

91 Q00570243 021114-56762 PP6K: V.35 port down disabled, linestate all up(rfs dsr dcd rts), remoport up



Title



ne

d

ee

de

ng

92 Q00570846 PP6K: CasPlaneResponseErrorInternal Swerr appears on CPswitchover/reload

93 Q00570888 FSM_BAD_MESSAGE after reloadcp

94 Q00571073 PP6K: Q931Sig FramerIf -- Invalid msg sigChanLockedToFramerSwerr

95 Q00571410 NSSA ABR advertising default route when not connected to backbo

96 Q00571427 OSPF: NSSA: Type 7 to 5 conversion not taken over on ABR portfailure.

97 Q00575461 " "Incorrect logic in method ""getIpPort"" for returning VRRP associateIP port

98 Q00575465 VNS topology change causes TB bridging to reclaculate spanning tr(STP)

99 Q00584867-01 020327-93133 4P-E1MVPE FP does not detect and suppress the idle code.

100 Q00586645 020927-99848 PP6400(7.0.9): Mpanl Framer record has a wrong value

101 Q00588203 Implementing Debug commands used for Q00502184

102 Q00588391 PROP: Global Support Tool Release 2 (GST R2)

103 Q00588759 030104-04329 Vnet, Euro-isdn, second call setup fails "requested channel notavailable"

104 Q00589516-01 010406-6927020204-31819020307-69891020613-81963

COT TEST 2010HZ TONE DETECTED AS 2100HZ TONE BYECAN USING 3C37H 1 PORTCODE

105 Q00591698 021126-71046 PP6k v7.0.10B - incomplete Long Distance FAXs

106 Q00593467 020809-44496 Memory exhaustion by SNA on TR FP does not cause card to crash

107 Q00594268-06 021216-91362030116-17346030212-48840030305-73860

MvpDspif::memoryDumpFrameHandler_v - Bad Access ProtectionFault 0x200

108 Q00596340-04 021121-65377030119-20259030119-20340

MPANL crash on SBIC due to corrupted Free list

109 Q00600300 021003-07661 7.0.10B: memory leak due to removing entries in apply table

110 Q00611998 020909-77297 PP:6K: Problem with Fax/Modem service after migration to R7.0.10

111 Q00612226-01 030213-49528030301-69218

After modem/fax call is released, the passport remains in mofax moand is send

112 Q00614023 030212-48374 QSIG Status message is not processed properly by Passport

113 Q00617511 030220-58068 netbios broadcast results in high normal memory, high smb, token rifp reset



Title



114 Q00619678-01 Deleting VRRP instances causes CP crash

115 Q00621443-03 030227-65852 Passport 7000-ve3l card 7 restart 70120101 CRAN PCR 4.2



Title


110 Appendix C Items Resolved in Previous Releases

Appendix CItems Resolved in Previous Releases

Items Resolved in the P7.0 (BG00A) ReleaseThe following Service Request list details the updates that were included in P7.0(BG00A).

Table 20Items resolved in P7.0

Title SR Number

Fix for mid loss problem Eap Bcst, Rtg dpn cs/scr comp missing 10290855

SNA DLR fixes for problems found during IT-Austria live test 10319953

SNA DLR traffic stops towards BNN connection 10324290

HotHaus 3c24 build 10323511

Call Completion Ratio drops to 77% if SAD=ON on PVC CAS 10311193

Bad PNNI RCC component status on NMS & pnni swerrs 10319967

Ingress and Egress frame free list failures 10304762

VRRP related, gating SRs 10302493

Atmif link Utilization, txQueue threshold SRs 10314599

CP crash at vrCbs on call to saveFtoUpdate 10288704

10baseT eth card continous reboot after upgrade to BE01SFA 30140323

10BaseT cards crashes on intialization with traffic 10310624

V11 (PM2) crash after reset: Free block list is exhausted 30123035

Chan Restart Fails 10323516

R7.0 Packaging Problem: Voice TDS 10320418

APPN deletion of DLCI causing FP failure 10316058

DS1 CAS VSR SVS useage causing SWERR under traffic load 10299165

SWERR caused by tpt under traffic load. 10323873

Change required in DCS Collector registration to support SNMP MVR 10317997

IpRtm provisioning memory leak 10198436

SWERR: AtmMpe semantic check for unrelated Lp provisioned 10317835

Hardware Forwarding Fails During Route Flaps 10311802

BGP external route won’t export to ospf 10322908

PVG: No TEST component under Shelf Card for the 32E1AAL card 10307891

Ethernet Dynamic ARP entries cannot be cleared 10318194

Inconsistent load distribution for IP equal cost multi-path 10309941


Appendix C Items Resolved in Previous Releases 111

Items Resolved in the P7.0.1 (BG00S1A) ReleaseThe following is a list of SRs that have been resolved in BG00S1A.

No CAS response when a ping is issued on down PPP interface 10288360

CATL4 | 3 CP crashes with same NMI error 10314496

Missing accounting records/Dlcis stop reporting accounting 10313428

ATM-IP FP: Inconsistent CLP bit setting for Egress traffic 10309939

GateWay: Invalid "callingNumber" identified in vsr/x svs/y 10317679

Multiple arp entries with same ipCos value 10321152

Tos byte should not be used in sending VRRP advertisement 10326658

10BaseT continuously reboot 10323765

TB flooding on CQC card does not work for atmMpe 10302724

Fp crash during switch over 10320588

CP switchover causing inVrCp swerr 10317787

tTcmBGP2 _tcmTask running at 94% 10326181

QSIG:PP answers to RESTART_ACK with RESTART_ACK 30316362

Policies With Multiple Port Ranges May Not Work Properly 10319627

Policies do not take effect after ipCos feature is added 10321188

LanIdTable entries not aged out (SRB) 10326669

Tb via 100baseT/ AtmMpe drops traffic 10323114

PP520:attributes values cannot be set in NMS prov tool 10315784

PP high CPU , shared message block exhaustion 7013 0011 10287492

ATM-IP FP:IP forwarded stats can be misleading 10326844

No alarm raised when cable is pulled for 10BT port. 10325285

IPX/100baseT interworking 10326667

ATM-IP FP: ARP over MPE not working 10294126

R7.0 Packaging Problem : rmsTandem 10320414

"ping -rtd" command issue from a PP running 4.2 to a PP runn 10327427

Table 21Items resolved in P7.0.1

Title SR#

Changing Startup to allow the customer to input a VR name 10266391

Bicc syntax error 10270677

Table 20 (Continued)Items resolved in P7.0

Title SR Number



Releasing allocated memory to prevent a shelf crash 10304708

Error in shown amount of service disrupted after Check Prov 10316668

CAS Check Prov unjustified error: spooling and agentQueueSiz 10319305

Invalid Fairness Policy Behaviour for ABR 10336186

OAM Performance: Unexpected Rxdiscard on CQC when OAM cells ON 30130005

Early statistic records (Timestamp in MDP statistics) 10309826

RxLinkUtilization and TxLinkUtilization not Reporting Correctly 10332783;10314599

CAS plane response error 10316915

PQC2 Introduction on Passport 6400 - running PQC2 as PQC2 10337464;10321094

ATM-IP FP: Exceeding defaulted totcappool causes SWERR 10328758

Criticality is not being held through card reset 10330790

Virtual Link Vpt Check Prov Failure Causing Abort/SWERR 10331672

Local Session corruption causes swerr with every command 10310169

VCC VCD TM - Altering TM to ABR values causes SWERRS 10313390

Enhancement: need txUtilization attribute under AtmIf Vpt 10316612

Ports stay down on new E1C card after provisioning 10326957;10326958

ATM OAM: VPC segLinkSideLoopbackState 10333533

Bridge crash with no traceback 10336656;10316291

Sw fault/task EE30-antCr type mismatch/ internal mmy write protect fault 10301945

VR IPX not showing stats 10314086

Enhancements for Virtual Link VPT 10321572

DS3/E3 ATM - IP crashing 10335139;10325823

ABR MCR fairness and support for ATMMPE over ABR 10339091;10339086

MSB SAL Throttling 10341764;10342387

GFC bits not reset to zero when a cell with non zero GFC is received 10344386

ATM-IP FP: Bridging: failed assertion in mySalIntHandler10_v 10327538

Unresolved symbol list for baseMsbDs3E3FpSp_BG0018Cd.o in VxSim 10343998

IPCos Links bad after Copy Prov 10345177

DE frames are not mapped to cell of CLP=1 10297097

Table 21Items resolved in P7.0.1 (Continued)



100BaseT: 100BT Ethernet card crashes when IfState changed 10333480

ATM-IP FP: VR0's are not created for Token Ring 10341736

IP_TUN: IPX failed to pass thru over Tunnel using GreIp encapusulation 10264491

SWERR doing OSPF provisioning while VR is locked 10301629;10298703

CP crashes when deleting BGP export policy 10348765

RIPv2 updates missing provisioned static routes 10300643

ATM-IP FP: Changing from llc to ipxVc Encap causing crash 10320346

ATM-IP FP: MOP counter not reset to 0 with IP and TB traffic 10341605

EP/DP not managed properly in non-cos datapath 10320733

Forwarding address used from inactive OSPF interface by NSSA 10329809

RP router sends incorrect interface address in register stop 10332280

ATMMPE: AtmMpe remains down after AC prov changes 10332306

IP CoS feature for ATMIP Fp and other fixes 10335018;10332867;10335020;10335082

CP2 crashes after IPX/Filter activation 10335804

Extend functionality of netSentry debug tool 10321108

Multicast routers don't fwd packet224.0.1.0-224.255.255.255 10332267

IPCoS: inwIpFeh swerr when IPCoS added to FrDte sw lpt 10332867

ARP Table Not Displayed Properly 10335159

CDL changes & data member ppforwardingData 10336547

ATM-IP FP:Bridging hardw. dpath cause Bridging VNS to break 10338773

Congestion Causing ARP Problem 10303191

ATMMPE: AtmMpe's are disabled after shelf reset 10333476

FP Crash during get port address 10333872

BGP reset shelf "l vr/1 ip bgp" 10335512

VNS: IP traffic over VNS does NOT work from CQC to PQC 10340093

BGP-matching mechanism enhancement 10341203

Unresolved symbol in package cmsCommonS when ip is not provisioned 10341505

Deleting IP off VR and activating view with IP causes rtgProcList SWERR 10332782

Deletion of IP without IpMcast does not work properly 10340430;10341836

SRB frames with double RIF in case of SRES-SRB-PB-TB path 10340475

ATM-IP: SGAF card crash due to a null pointer 10341985




IP_MCAST: RP failed to send SPT join when LHR joins RPT 10343632

ATMMPE: InwArp swerr on SGAF AtmmMpe 10344405

Multiple ICMP 10233486

ATM-IP FP: Crash when trying to uninstallBrPort 10338062

MCAST traffic rate dropped unexpectedly 10312656

ATM-IP: atmmpe feat won't load on SGAF card 10330461

BGP Policy Enhancements - Exclusion Routes 10337872

ATMIP: LP reset on br flood after lck & unlck vr/1 br 10341984

CacheStats alarm Id incorrect and 2pOC3SmAtm2 IPX support 10345238

LHR on Broadcast network fail to forward Multicast packets 10346024

ATM-IP: SGAF card crash during FWD between VNS and ATMMPE 10346326

A field was misdefined 10346691

MPANL Causes Card Crash 60315008

Node Stuck in Staging causes PP Mid table not to be updated 10328000

More than 18,000 Alarms 70090404 in around 10 seconds 10328001

ETSI ISDN Protocol Error for MPANL Link 10326705

ppath and ping does not work in 5.1.20 when Rid Substitution is needed 10334924

Signalling Vcd Component Defaults Fail Check Prov 10325360

Fax Relay fails to train at V.27 10341384

Fax Relay power levels vary as data rate changes 10341385

Fax Relay fails to train at 2400 bps 10341386

SNA DLR - FR BAN fails to work with Bay Router Ethernet 10333033

SNA DLR: Activating new provisioning view will not complete 10327731

APPN performance degradation 10253264

TRK PA report a bad maxReservedBwOut 10304233

ATM TRK SWERR: tpaAtmHook.cc sweers after deleting Trk PA co 10336296

Call failed with QSIG to QSIGGF PBX Network 10335147

Failure sending DTMF authorization codes 10322321

Invalid IE in NOTIFY message identifying undefined Display 10339004

MVP: FAX CanonE-600 can not send DIS frame to remote FAX 10324703

PP4460 - PP6400 Interworking for G.711 10338063;10340466;10341067

G.711 w/ 40 Byte Frames Causes DSP Reload 10343768

C function call from ASM in wrong page mode 10296570




Items Resolved in the P7.0.2 (BG00S2B) ReleaseThe following is a list of SRs that have been resolved in BG00S2B.

Comfort Noise Generation does not get reset between calls 10318503

TPT does not switch to operating mode 10315757;10337890

comfortNoiseCap value of -65 dBm0 not provisionable 10339903

Initialize silence condition in SAD 60317013


Title SR#

2pOc3 SGAF APS does not switch properly 10277051

SWERR: Wrong reported 'actualLineSpeed' of V.11-Ports 1032760610292605

EHOU2 DS3 ATM card crash 10319569

File System sw error at dcsSpooler.cc;1354; and sfsCasIfGlob 10327806

Problems in the SDD files_propagation_from_p5.0_to_present 10350424

FP crash when bridge traffic going over domain bridging 10353456

IMA Sparing Issue 10294561

IMA Interoperability Issue 10337919

Unrecoverable SWERR in rpcLib.c during task "EE0-stdEe" 10307134

V.35 DCE port does not report proper status 10317969

VL Vpt Causing Inaccuracies in AQM Shaper 10320510

AtmIf TxCell Count problem with ABR over VL 10327249

ATMIF Stats Manager not collecting dynamic VCC stats for PORS on CQC 10333599

ATM-IP FP: Missing Bridge Forwarding Entries on CP 10334273

ATM-IP: IP/VNS over CQC to PQC performance degradation 10342771

ATM-IP: Frame Corruption on Egress causing LP crashes 10351395

ATM-IP: Fail Assertion: isAllocated (vriId) 10350086

ATM-IP: I-PQC FFL crashes with Bridging over AtmMpe link 10339260

ATM-IP: Ingress SGAF card crashes when flooding to 4 or more other interface 10341991

ATM-IP: IPFrag causing SGAF card to crash 10348800

ATM-IP FP: failedAssertion deallocate__6MsbVri 10349064

ATM-IP: SGAF card crash due to IPcoS 10350166

isValidOnCard() missing assert for incorrect card number 10334461





MsbAtmPortClassIterator not working 10346845;10337636

The memory allocated to the LcmProcess was not released 10314938

Token Ring Ipfrag LRC problem 1031674810323830

Tuples dropped from IPX srvc list 10353989

Reset Shelf Causes IPX SWERR 10294593

CIP : Potential Memory leak 10130775

areaLsaCksumSum for router's in same area should be the same 10211814

VRX/EMHT entries are not removed when PPP protocol port is locked 10335039

No semantic check when linking ATM IP AtmMpe to IlsFwdr FP 10336354

Migration escapes for R5.1 to R7.0 10340378

Crash in BGP export policy 10348764

RIP packet processing and flush timer problem 103491581034916110349164

Frame UnderRuns incrementing while in tpt mode 10315988

PORS Route Selection Overflows at DS3 Speed and Above 10326956

CSRM not re-learned if the connected Passport node isolated 10321919

FR-ATM SIWF InATMARP translation incompatible with RFC222 10318517;10343126

APPN migration issue from 4.2 to 5.1 - attributes 10349836

CP crash when setting interfacename 10346367

Br traffic go SW & ingress enet card reset when SGAF reset 10354815;10356136


Title SR#

Wrong management of C and I signals after view activation 10290854

Wrong include file in dmePqcSystemFlash.cc 10283899

AAL1 CES port must be locked and unlocked to clear user data 10306718

CAS Prov: Corrupted Data error msg when migrated to BG0015D 10318208

VL Shaping Fix Phase 2 10320510

Table 22 (Continued)Items resolved in P7.0.2



LRC Errors PQC Egress when Fowarding Mutiple MAC's 10332976

ATMIF Stats Manager not collecting dynamic VCC stats for PORS on CQC 10333599

ATM-IP: Fails to pass traffic on VPC/256 10334226

ATM-IP FP: Can not do a dmeTrace without loading strap 10338155

ATM-IP: DME support for empty local frame head block 10348850

ATM-IP: SGAF VNS to PPP causes bridge frames to discarded 10358435

Software Error in pms subsystem, pmsCommonSemanticChecker.cc;260 10342168

Ipx SGAF fwding to VNS, tb outNuCastPkts count 1035616610343774

CP crash when issuing a certain command sequence 1034636710346045

MSB Frame Corruption Workaround 10349076

MSB Iterators causing Memory corruption 10352814

DME copy fix 10357198

V35 cards must be reset after upgrade from 4.2.13 10358563

IMA lifts after lock/unlock - protocol error 10360747

V11 - Localloop test failed 10317809

V11 card crashes 10354360

IP broadcast storms will affect other services 60324582

Ospf Not Returning Proper info from Neighbour SNMP Queries 10354596

Type 7 LSAs not generated for RIP Routes in a NSSA area 10330148

IP CoS not respected when entering IP Tunnel 10301358

ARP frames not using the best available discard priority 10348603

FP crashed (during traffic flow) when provisioning mcast 10344152

Filter reload does not work 1034769010346213

Ospf does not Re_converge when Primary DS# link fails 10348261

Problem with GvcIf device monitoring 103579071035795710353288

pim domain provisioning error 10353019

Delete CBSR does not change locally & IGMP query time wrong 10360871

frmFromIf and octetFromIf reset during manual test 10326966

V35 reboot: Fault is diagnosed as a bad access @ 0x2bf protection fault 60315008

Switched data not working on a voice service 10328449

MVPE:displaying Lp E1 or DS1 Audio component crashes card 10344453




Items Resolved in the P7.0.4 (BG00S4C) ReleaseThe following is a list of SRs that have been resolved in BG00S4C.

Voice Networking Call Hunting 10344792

pcmcapture feature for dcme link vs crashes card 10346706

Software Error generated when running traffic to PP4400 10355892

Card crashes after 3 dsp reloads 10357763


Title SR#

Multiple time servers will not synchronized after migration 10326297

LineSpeed value rounds down instead of rounding up 10356746

PP high CPU , shared message block exhaustion 7013 0011 10356815

Traffic using VPI >= 256 not working on SGAF DS3/E3 cards 10359622

OC3 SGAF card crashes at file dmePqcDispatcher.cc 10359988

Passport MIB-II contain ifPhysAddress with value ....01.00 10362165

txLinkUtilization & rxLinkUtilization incorrect for CQC Cards with VPCs 10363001

OAM Cell causing a Sys Recoverable error 10363200

FP Shared Memory not released after sh card test 10330413

JT2A Port Test Failures 10368363

Adding a VPC to an ATMIF on an IMA card constantly crashes 10374319

Fragment from PP6000 and PP7000 PEC code split FS (MD-1999.0751-01.01) 1036969910369224

maxVPT initialized to maxVPC on Migration 10351184

Command list doesn't work as expected for some components 10365530

PRI ISDN does not restart if the FP cable is removed 10368915

Long Pump Message for MPANL 60320439

V35 crash with netSentry 10343594

ATM-IP FP:Severe exception 252 on VRI 1 with IP traffic 10332638

StartUp ATMMPE on ATM IP FP 30324593

OSPF over multiple ATM VCC s and IPCoS 10341603

Chk Prov allows broadcast IP to be the same as PP logIf IP 10080718

NMI: Local Bus Error at InwIpxSap::serverOnThisPor 10357365

Alarm 0000 9000 (VR/1 subcomponent) 10081095

IP multicast affects IP unicast performance on ILS forwarder 10365964





Passport fails to forward multicast datagrams out PQC card 10374361

Probes not sent from first hop router FHR when oif list is null 10367013

SRES table not updated 10329812

Netsentry filter problem with broadcast IP address (255) 10357629

Ospf routes did not list if cost associated with > 65535 30117735

Passport 7.0 corrupted 802.3 Length field for Netbios frames 1036837410368367

VMAC address sent out by TR VRRP is rejected by w/s 10348329

FR DTE LMI procedure 10354034

IPX over FDDI fails after migration to r5.1 due to wrong MAC address 10361458

Configuring RIP timers 10357888

Router hangs when activate static routes with over 2 oifs 10362214

Master VRRP router doesn't go down when it is no longer the primary IP owner 10363924

Trace printf shows a mangled source address 10366450

PORS trunk doesn´t update the trunkcost attribute configured 10339159

PORS: Software error "WINDOW Window Full" CSM stuck 10352213

Vsr/x SVS/y back in service by channel 10318461

TPT takes 30 secs to come back after 2100Hz tone is removed 1031923010344376

DSP memory dump occured during traffic re-routing 10319625

DetGen/SAD causes double digits 10356631

Passport dropped out of fax Relay mode when signal level low 10359949

Transmit CAS yellow is activated if one VS path is removed 10360643

PVC negotiation robustness 10364633

Beep Tone heard over voice channel with E1 MVP-E FPs 60324479


Title SR#

E3A crashes when the ILS FWDR is added 10352439

CP boot time more than 40 mins with 1493NetSentry apply table entries 10370674

Add new Group to FRDTE out of Service 10372970

Blur 7K node - not respond to any command & generate unknown 10374939





Items Resolved in the P7.0.7 (BG00S7B) ReleaseThe following is a list of SRs that have been resolved in BG00S7B.

Multicast: Packet replication on PQC fails 10378571

ATM IP FP Crash after migration from 7.0.2 to 7.0.3 10367646

Gvcif on CFP1 discards frames when packet splitting 10368387

NS Source does not switch on degraded reference 10374964

ATMIP FP OC3S card disabled 10367360

Node red in NMS as result of changing single attribute on PP 10374137

CP crash when changing prov of ingress/egress gain 10377155

Speech break up on MVPE cards when raising level of voice 60331471


Title SR#

rtcManualSetTime bug 10140304

Non-standard date and time of day interface 10170454

illegal CPU utilization in new PDC card. 10386024

illegal CPU utilization in new PDC card. 1038672110386722

problem related to 8pds1 ima card ( cpu 200% utilization ) 10389383

Table 27Limitations Resolved in P7.0.7

Title SRNumber CustRefNumber

Incorrect date and time of day format 10170491

Prop: Flood of 70182001 causes 100% cpuutil - No info in alarm 10288468

VNET Accounting: vnetFlags_faxRelayDownspeed not working 10322043

CP Crashed and switched over to spare CP 10328014

PROP: Failure of Correlation Tag in FR-ATM Accounting 10330700

Prop: Memory utilization increase on PP running P5 and PNNI 10331527

Prop: Issue with indb: lock/unlock brings the inLocaldb attrib 10345749

Failure of IMA link causes slow response 10351390

V35 card Crashes with BG0026Ad debug load 10357223




Prop: Equipment Failures on Shelf card/1 on Passport GNHE02 10358386

Unresolved Symbol in porsAccFPs_BG0029Ad.o 10365947

Issue with Operator Camp-On to remote extensions on Voice Networking10367282

Performance are not very stable with Bridging over VNS 10368251

Prop: DS1C crash : NMI is diagnosed as a watchdog timeout 10370185

BCS software swear on BG0032A 10370439

CP crash, no more local message blocks 10371697

CP Crash:Unrecoverable Software error at line 264 in file pcsUtils.cc 10373080

Prop: A trunk doesnt come up after a migration from 4.2 to 5.1 in 10374198

AAL1 card externalloop feature failure..... 10377933

Multicast: debug statements should be removed from library. 10379203

ISDN signaling channel hangs after cable disconnect and reconnect within1 sec

10379792

Prop: bgp running in a loop 10381213

Prop: ATM UNI ILMI Failure 10381497

Prop: DLR service interrupting if lock/inlock issued on VR 10382422

Prop: AAL5 protocol error after FRF.8 (CPI Common part indicator w 10383885

Prop: MSG 90000 Big Pev Message C=0x68006 CC=4 10384621

Prop: FDCR: Alarm 9000 when you try to set a dna to a fruni 10385176

Watchdog timeout (interrupt 155) token ring card crashing 10385190

FSD doesn't work properly. 10386559

NetBIOS problem under ATMIP FP using ATMMPE 10387033

s/w upgrade failure (5.1.30 to 7.0.4) 10387779

Passport 6400 MVP QSIG/CAS GATEWAY doesn't send ALERTING forcall to pp4400.

10387804

Unable to unlock j2mv port (diagnostics failed). 10388017

Prop: NTP 241-7501-210 Vol 3 error 10388297

Echo cancellation is not operational on E1 or DS1 MVP 10389251

Prop: Problem in the Media Registration for an atmmpe protocol port 10389507

SWERRS gerenrated/BCS error occured during migration 10392657

FDDI:LCM: Crash in preDeleteScan 10392962

FDDI:LCM: crash in changeInPortToPpId 10392967

V35: LCM: Crashes in preDeleteScan. 10392974

CNYC22 isolated from network/routing topology 10393003

Table 27 (Continued)Limitations Resolved in P7.0.7




MCDN calls with more than 12 digits in calling line ID are r 10393120

Prop: No IP connectivity via X25 DTE 10395494

100BT Master VRRP reply with its physical MAC address after beingunlocked

10396077

MCDN / Auto attendant interaction 10398392

PP-Virtual Media IP-address not exported into OSPF as stated in NTPs10398984

Unexpected CTD values 10398995 010212-6695

Prop: Unable to get interworking between Passport DLR an ARN an P210399044

Prop: IMA card crashing continously 10401401

BDM NIS: Call handle set to release, call still attmpted with no digits. 10402990

Prop: E1 AAL1 FPs in 5.1.20: lock/unlock channel issue 10406654 010212-6858

CAC b/w allocation leak 10410391

S-PVC/P get "no route to destination" after trunk going down 10410405

Standby CP crashed during migration from pcr2.1(CB0036A) to 10411320

Prop: Memory leak - Network Timing Synchronization 10411339

Startup facility causes crash on ATM IP FP 10420647

Subcomponents not displayed when listing the lp 10421368

DLR: PUs are not able to reconnect to host after IPL 10421386

Prop: Passport crash 10421466

StartUp ATMMPE on ATM IP FP. 30324593

Start Up facility doesn't support VNS over ATM IP FP 30335056 010212-6086

Virtual router unable to move up the component instance tree 30337963

netbios/ipx packet causes atm/ip DS3 card to reset 30340076

802.3 length corrupted with ethernet 100mb card causing novel failed dd30343415

MCDN changes Facility codes causing problems when mapping to DPNSS30348197

Prop: OAM AIS insertion dose not work on VPT VCC or VPC nrp 60322573

Test component will disappear after lp/0 switchover. 60335975

Table 27 (Continued)Limitations Resolved in P7.0.7




Items Resolved in the P7.0.8 (BG00S8B) ReleaseThe following is a list of SRs that have been resolved in BG00S8B

Table 28Limitations resolved P7.0.8


Prop: Port 1 on 100BT card always not working when ATM-MPE present 10332907

CA shows incorrect poolAdmittedConnections 10374182 010211-4760

Clearing ARP results in inability to ping between the end stations 10375170 010211-5084

Echo cancellation is not operational on E1 or DS1 MVP 10389251

Prop: FSM msg alarm (msgCode=1966089 portIndex=8) 10390185

Provisioning SAD slownandcongested causes software Errors 10396007

Prop: FP Crash, NMI at Interupt 164, current task 164 in 10399019

Call handle set to release, call still attmpted with no digits. 10402990

Prop: PP15K OC3 FPs crash when DS3 FP with PQC2.0 is added to shel 10404114

Overflow condition in connPoolUsage attribute under Standard Vpt types 10405908

PROP: Cisco routers and fratm do not handshake after bootup 10406137

Prop: Crash: CBRU1 CARD/0 - Offending task 10407007

PNNI Hello Interval not respected. 10410662

IP-Tunnel: check prov fails with 32 bit netmask 10411740 010305-7156

1pE1V card resets when change CID value 10411885

Physical line interrupt: no PtoMP SVCs ; SwitchedMultiCastB 10413717

Corrupted Facility IE in MCDN Set-up Messages 10414058

Passport 6400 ATM IP card problem 10415139 010314-1807

SRES double RIF fix prevents arp to 4120 or 4400 10416623 010319-3636

ping with small packets won't work when we using FrDte conne 10417554

DSP asserts and recentinglinesamp 0000 10419539

SPVC connection issue in PCR2.0.2. 10420354

Loader bug with respect to patch removal 10421057

Entering d lp/0 cpeth crashes the CFP1 10421123 010418-1282

E1C Card connot be loaded with software 7.0.6 10421353

Prop: Changing the perserve domain parameter requires the fast eth 10421543

TRACE feature on LP/x TR/x create SWERR and not able to turn OFF, onceturn ON

10421745

DS1MVP VNET CAS MCA DATA CALLS ARE CAUSING DSP ERRORS 10421751

ATM IP (2POC3SMATM) card reboots after issuing l atmif/40 vcc/0.40 tm 10422354

Prop: Support for FRF.8.1 not included in 5.1 or 7.0 10422573



PP jumping to wrong state during call progress 10423320

Repeating FTT (failure to train) using faxRelay 10423357

Prop: HTDS stats error: Rx frame/sec - Rx kbits/sec 10423546

PROP: Cannot IP ping w/ less than 510bytes-FRrouter to ATMrouter t 10423948

"blockSnapSave" Crashes SBIC Card With Watchdog NMI 10424687

softwareError : Caused by 10425389 010508-9840

NCAS sessions not being torn down. 10425604

E1C Card connot be loaded with software 7.0.7 10425643

CP local ethernet connect doesn't work from STARTUP 10426284

Crash and VRcbs suspended for InwArp problem. 10426960

8port E1ATM (IMA) atmif ca Bandwidth allocation pr 10427893

elapsedTime=0 if set Mpanl/<n> voice acct ao ster even the call is answere10428672

Startup AtmMpe doesn't work on E1 CQC Cards 10430252 010528-6595

IP traffic delayed with traffic shaping enabled in 7.0.7 10430914 010528-6531

VRRP check sum error 10431355

Prop: Problem with BGP aggregation policy in 5.1.27 10432490

HEC Error: Add numberOfIntervals for HEC error detection 10432918

Locking and resetting Lp/5 Eth100/0 produced loss of service in Lp/5 Eth100/110434586

Prop: VR problem after resetting the Passport 10436217

Kernel should pick IP address from EPROM if cpEthernetConfig file missing10436568

DSP asserts due to incorrect media frame size 10437180

PROP: Failure of Correlation Tag in FR-ATM Accounting 10437894

Problem in the Media Registration for an atmmpe protocol port 10439375

TPT causes DSP Assert from 4pmvpe add : 3c34 10439718

BTDS Idle Suppression not working properly on MVPE 10439842

EOC silence timer triggers too quickly on MVPE 10439847

Mofax upspeed & downspeed fails on MVPE 10439851

E1qsig MVP Card Crash during voice traffic 10440515

Card crash after vnet component lock and unlock several time 10440683

Prop: Variance DPRS strange behaviour 10442002

Prop: CP crash when setting up >40 OSPF interfaces per VR 10442008

Prop: MSG 0000 9000 nmiDcsHandler.cc, line 296; p7.0d.37 10442103

Prop: TR card crash with unrecoverable software error generated 10443590

Table 28 (Continued)Limitations resolved P7.0.8





Prop: CP crash with ARP operation 10443909

DSP: FaxRelay Assert no DCS component 10444792

Prop: Propagate a default route through VR 10445764

Crash: CBOM1 LP/13 V35 10446367

SBIC QCSRAM Parity Error 10446413

FRATM - Failed to activate provisioning data of FrAtm 10447745

Crashes on 3pOC3Sm card 10449355

100BaseT card loses connectivity when port deleted 10450657

TMuxOper : Trk/12 reports congestion state under the TRM Lg Lk while it isn't10451137

Prop: Static Routes won't go into RDB if there is an OSPF external route 10454965

Prop: OC12 FP Crash: Intrpt 162 at task DmeResumeDisp_t/Execute In 10455437

PROP: ARP entries are display continuously in loop mode after migr 10455905

SNA DLR calls dropped if two ports are in the same TR and one of them isdiscon.

30005839

Prop: 3pE3A (CQC) crash : Unrecov. SWERR at line 278 in file pcsUtils.cc30130765

Domain number don't change on operational data in Lte component 30324467

DS3Atm2 FP crash. excDumpTrace are display continuously under OS mode30342025

Table 29Limitations resolved in P7.0.9


PROP: Variance DPRS strange behaviour 10442002

Lan-Wan-Lan Bridging performances aren't symetrical (Bad on port 1) 10444767

PROP: OSPF checks N-bit in option field when receiving DD Packet. 10449718

clockSourceStatus unknown when automaticBusClockTest is enabled 10450429

AntiTromboning SWERR when picking up parked call 10451186

Correct reporting of DSP Asserts 10456568

Cannot IP ping w/ less than 510bytes-FRrouter to ATMrouter through FratmGwy

10458064

Table 28 (Continued)Limitations resolved P7.0.8




t

d/

t

te

Items Resolved in the P7.0.10 (BG00SAB) ReleaseThe following is a list of CRs that have been resolved in BG00SAB


# CR ID SR # CustRefNumber Title

1 Q00098485 10476319 Packaging of the Global Support Tool (GST)

2 Q00305998-05 PROP: Crash: NMIS Local Session's kill Timer Corrup

3 Q00306117-06 10482240 aqm constant and maxMBS calculations incorrect

4 Q00306148-06 IP cross-VPN traffic on Eth100Bt because CAM notenable for Port 1

5 Q00306178-06 10461011 Code-Red virus affecting Passport IP nodes

6 Q00306179-07 10483820 PROP: 100% CPUUtil when CP reload with 2000 staticarp entries

7 Q00306185-05 10458393 Prop: VpiEv value corrupted.

8 Q00306188-07 020610-7745 PROP: OSPF Adjacencies status stay in INIT

9 Q00306202 10479220 DSP assert with 6ea3 occurring during fax call

10 Q00306206-07 10474720 NCAS (NON CAll Associated sessions) not being torndown

11 Q00306239 10469150 EURO ISDN DOES NOT RESPOND TO RESTART

12 Q00306257-07 10480424 PROP: PP7K: 3.0: Local message block congestion

13 Q00306258 10460411 010919-6742 Fratm on PP6400 doesn't understand1490ProtocolHeader = 0300800000000806

14 Q00306918-04 ILMI registration proces of ATM address problem

15 Q00306999-04 10457199 PMP AddPartyRequests queue up causes memoryexhaustion

16 Q00307211 10434429 BTDS Service does not recover after trunk failures.

17 Q00307343-04 10470238 PP15k uni signaling channel disappears when vcd addel

18 Q00307419 10444597 MVP-E interworking to 4400 Lost DTMF Digits

19 Q00307492-04 10456006 FRDTE ifadminstatus has no effect after lp or shelf rese

20 Q00307557-05 10476416 010827-0569 PROP: PGR: migration: High CPUtil on OC3 cards.

21 Q00307562 10450046 10820-1389 PP6K: SW 5.1.31: 00009000 COL/STATS sw error

22 Q00307569-04 10452762 Fratm - ATM correlation tag problem

23 Q00307602 10452934 MVPE ignores DTMF control messages from PP4400prior to answer supervision

24 Q00307659-04 10459545 PROP: RIP v1Compatible updates not send out of FrDrg with nbma

25 Q00307676 10456780 VNCS attributes have incorrect range in CDL



g

n

26 Q00307676 10456780 VNCS attributes have incorrect range in CDL

27 Q00307725-04 10464300 PROP:CPU utilisation on a V11 is at 100% -> can't r

28 Q00307991-08 10476053 Unrecoverable Software error in filemvpCompProcess.cc

29 Q00308056 10475580 Propagation of the Global Support Tool (GST)

30 Q00308821 10470291 011114-4591 NMI occured at interrupt level due to local bus error

31 Q00312072-01 PROP Errors in CD0118A when a call is forwarded orparked

32 Q00312281-05 CP0 not reloading when IP 7K node is reset after testinIP.

33 Q00312469-01 Prop: CC01S1B:callPark produces SWERR

34 Q00312575-04 Prop: 4pDS1MVpe: vnetUipeDchanMaint swerr

35 Q00312708-01 Prop:4pMVPE:-Crash due to memory protect violation

36 Q00315404 10412590 010309-9615 4p E1 AAL1 CRC4mode does not work

37 Q00315413 10420772 When VC's MBS is set lower ECR goes up rather thedown

38 Q00315414 10420825 Cannot migrate from BE01SVA to BG00S7A

39 Q00315490 10451982 Passport 6400 icmp redirect problem

40 Q00315507 10458230 set Vroute/n Interface sends alarm on all switchcomponents

41 Q00315510 10459828 011018-1533 2pOc3MmAtm2 card crashes when migrating to 7.0.8

42 Q00315512 10460304 011001-9476020405-0446

Prop: Unrecoverable Software error at line 658 in filepqcIn

43 Q00315514 10460625 Statistics between E1V and MVPe are different in VSframer

44 Q00315525 10465297 CAM not repopulated even though traffic running for 30min

45 Q00315526 10465307 After node reboot FTE appearing on VR/0 when trafficon VR/1

46 Q00315532 10469476 FTE not flushed when bridge port is deregistering

47 Q00315533 10469622 Configurable Route Preference Prop of CD1220 intop7.0

48 Q00315535 10470143 SNMP walk of 100.3.5.2.2 causes SWERR

49 Q00315536 10470834 011130-6358020514-4790

FP Crash: E3 is rebooting after sw upgrade to 7.0.9

50 Q00315537 10471076 011030-2801 The real traffic doesn't flow over 92% of ASR withDS3A(PQC).





0

51 Q00315548 10474318 D2V MAC Address Issue on PP7480 Shelf

52 Q00315553 10474588 7.0.9: Entries in RDB not in FWD table

53 Q00315554 10474594 PP6480 - IMA Grp must be bumped to restoreconnectivity

54 Q00315556 10474783 010804-6565020405-0345

Traffic Delay After CP Switchover

55 Q00315557 10475133 011106-3649 XPL: IP Card crash after using ""get"" command

56 Q00315562 10477589 020208-3858020426-2977

Too many DSP reloads cause unrecoverable softwareerror crash

57 Q00315562 10477589 020208-3858020426-2977

Regression failure on DSP reloads reporting

58 Q00315566 10479106 1pE1MVPe: Card crashes due to No more local msgblks

59 Q00315567 10479145 020129-2485 IP stop forwarding if LEQ component is provisionedunder PPP

60 Q00315568 10479353 011107-3777 Acct subcomponent under vroute/x will not listoperationally

61 Q00315571 10479558 020131-2968 Memory leak on CP when VRRP is enabled on someVRs

62 Q00315574 10479779 010702-8623011115-4814

Load Balancing Feature, ARE filter feature

63 Q00315575 10479780 020205-3332 Arp tracing on by default when entering OS

64 Q00315577 10479810 Tracing ILP exception handling on PQC required in 7.

65 Q00315579 10480520 020131-2907 Passport:6480:7.0.010BaseT card(2 & 7) crash

66 Q00315583 10481281 011210-7469020611-7883

Call Back (CCBS) QSIG supplemenatry feature doesnot work in 7.0.7/9

67 Q00315586 10481726 Reporting of DSP asserts

68 Q00315589 10482078 020219-4990 NMI acces exception - BATMAN crash

69 Q00315607 10484342 020314-7861 MCDN blind transfer with CLID IE with more than 12digits calls fail

70 Q00315611 10484364 020228-6225 One way speech/no egress messages from DSP

71 Q00315842 10482559 020213-4409 PP6K: 7.0.9: NMI Offending task ""EE19-vrCbs""

72 Q00315843 10482040 020522-5689 Fed optimization - improve system recovery time

73 Q00315844 10479096 011225-9119 CRS Function problem after CP Switchover or Reset

74 Q00315846 10474102 Only vrrp master should use VMAC in ARP requests/replies

75 Q00315847 10473116 011130-6527 CP crash at task ""SftpSrvE1"" and ""EE16-Ntpd""





76 Q00315848 10472539 011212- 7876 CP Crashes at boot time due to LMB exaustion

77 Q00315848 10472539 011212-7876 CP Crashes on boot memory issues relating toNetSentry

78 Q00315849 10468087 011001-8221020123-1692

V35 ports dropping for short period of time after RTScomes

79 Q00315850 10466397 011107-3777 TB over ethernet connected to Cisco NMI crash

80 Q00315851 10463599 011107-3811 PQC Frame FreeList is not sane on ingress

81 Q00315852 10463166 011022-1919 VNS multicast ping fails - Linkgroup tables out of sync

82 Q00315853 10459448 ATM trunks break ping -trace -all rtg vns nodecommands

83 Q00315853 10459448 ATM IP trunks break ping -trace -all rtg vns nodecommands

84 Q00315855 10450343 010619-7684020514-4835

PP4450 voice traffic is running over the data VCC ofSPO-mux trunk

85 Q00315862 10430243 list vr/x pp/y sna circuit/**** doesn't show all thesessions established

86 Q00315955-01 10375437 FP crashing when receving corrupted frames

87 Q00315962-01 10375432 Bridging: AtmMpe Pp TBP InFrames stats notincrementing during flooding

88 Q00315984 10328088 Extra digits within the ARP tables in 5.1/7.0 loads

89 Q00316223-01 10448684 010809-2560 CP crash at tq_summary

90 Q00316431-01 10464508 010212-5749 DLR account records dont contain description aboutinformation transferred

91 Q00316458 10479740 010702-8623011115-4814

Enhance existing load balancing feature to make itprovisionable

92 Q00316460-01 10482241 MSA32 : Cannot Establish rt-VBR SPVC Connectionsto FrAtm

93 Q00318778 020314-7877 NSSA ABR missing default route from other ABR inrdb and fwd table to NSSA area

94 Q00336944 020402-9933 FP restarted to clear SDL problem

95 Q00361573-01 Prop: MCDN Break-in not working

96 Q00363679 SWERR generated when changing snmpAdminStatusfor bgp comp.

97 Q00366585 100BT debug tool .o file is not downloaded with otherILS software

98 Q00384380 pp6k - FRATM Swerr (fedType.cc, fedT1v.cc, etc...)when Prov'ing Siwf Sd

99 Q00386597 020402-9873 Checksum Errors in Uplink PTSEs





s

s

100 Q00410344 6400 PANL does not support over 4096 Byte PacketLength

101 Q00412494-01 Prop:MCDN SigChan PNI

102 Q00412643 020103-9532 CP Crash at P7.0.9 while handling NetIP Frame.

103 Q00416647-01 Back Prop: Vnet StdUipe Codec.cc swerr when callsrunning and reload performed

104 Q00417977 MDM conflicts with wireless comp/attrib inENTERPRISE loads

105 Q00420298-01 Prop: 4p Vnet MCDN - Conference call release causecard crash

106 Q004215842 020313-7690 Duplicate ospf external route in rdb

107 Q00421640 pp6k, sddetoclpmapping in fratm siwf and niwf is notworking properly in spvc

108 Q00421643 pp6k sdfecntoefci mapping on fratm dlci siwf spvc isnot working correctly

109 Q00422450 020429-3135 VRRP on Token-Ring uses Phys-Mac Address

110 Q00426054 020424-2559 2nd ECMP route is not in rdb

111 Q00426929 020405-0439 PP6K:Passport 6K and 4K interworking (Problem withAuth code entry)

112 Q00429304 020315-8040 MVP crashes (FP restarted to clear ADL problem)

113 Q00429941 pp6k - Swerr when configuring atmPnni :antPnniRAGroups.cc; 351 on Cqc

114 Q00431526-01 Prop: antitromboning swerr

115 Q00456952-01 Prop: PP7K PCR 2.3.3 NCAS sessions not torn downand facility msgs are rejected

116 Q00457494-04 Prop: PP7K PCR 2.3.3 software error generated whentimer expired

117 Q00457640-07 STAB: Unrecoverable error in ldrStartFirmware.cc onCP

118 Q00458118 pp6k - Every 2nd conn NOT getting connected forSPVC/SPVP/SVC from UNI int.

119 Q00458137 pp6k - 8pDS1 FP Crash when testing Btds connection- with valid/invalid config

120 Q00462485 MPANL-MVP interworking over AALSPO trunk

121 Q00463761 Voice debug DSP code needed

122 Q00469103-08 STAB: Unrecoverable Software error - SBIC boot testsfailed with code 3005

123 Q00469222 Eap Broadcast optimization





e

124 Q00471485 Crash on FDDI FP while testing ILS Sanity

125 Q00490874 020723-2469020724-2586020805-3831

2pEth100BaseT FP resetting after upgrade to 7.10 duto ICMP Error (TTL=0)




132 Appendix D Documentation Updates

ent

ssthe

s:

upTEth

ess

Appendix DDocumentation Updates

V.11 function processorNTP 241-6401-610Passport 6400 FP Configuration and Testing GuideSR # 30345930

V.11 FP configuration parametersWhen configuring a V.11 FP, use the following values to help you set componattributes:

• Card type <cardtype>: V11

• Ports <port>: X21

• Port numbers <m>: 0–7

Line speeds and link modesThe V.11 function processor supports two sets of line speeds in Mbits/s:

• a common speed, which is any value within the configurable range

• V-port robustness speeds: 1024000 and 2048000

In some configurations where common speeds are combined with robustnespeeds for ports on the same function processor, there may be conflicts forfollowing speeds:

• 768000• 640000• 512000• 384000• 320000• 256000• 128000• 64000

Configuration of ports for lines speeds and link mode must follow these rule

• all ports within a group (ports 0 to 3 for group 1 and and ports 4 to 7 for gro2) are configured as either DCE (that is, DCE is supplying the line clock) or Dthrough thelinkModeattribute; one group can be DCE and the other DTE, or bogroups can be of the same link mode

• if the ports in a group are DTE, you can configure any common or robustnline speed with no conflicts occuring


Appendix D Documentation Updates 133

the

em

ent

ssthe

s:

upTEth

ess

• if the ports in a group are DCE, the ports can be any speed except one ofconflicting speeds noted above

If you do not follow these configuration rules, the check prov fails and the systlists the conflicting speeds.

V.35 function processorNTP 241-6401-610Passport 6400 FP Configuration and Testing GuideSR # 30345930

V.35 FP configuration parametersWhen configuring a V.35 FP, use the following values to help you set componattributes:

• Card type <cardtype>: V35

• Ports <port>: V35

• Port numbers <m>: 0–7

Line speeds and link modesThe V.35 function processor supports two sets of line speeds in Mbits/s:

• a common speed, which is any value within the configurable range

• V-port robustness speeds: 1024000 and 2048000

In some configurations where common speeds are combined with robustnespeeds for ports on the same function processor, there may be conflicts forfollowing speeds:

• 768000• 640000• 512000• 384000• 320000• 256000• 128000• 64000

Configuration of ports for lines speeds and link mode must follow these rule

• all ports within a group (ports 0 to 3 for group 1 and and ports 4 to 7 for gro2) are configured as either DCE (that is, DCE is supplying the line clock) or Dthrough thelinkModeattribute; one group can be DCE and the other DTE, or bogroups can be of the same link mode

• if the ports in a group are DTE, you can configure any common or robustnline speed with no conflicts occuring


134 Appendix D Documentation Updates

the

em

e see

on

se"

• if the ports in a group are DCE, the ports can be any speed except one ofconflicting speeds noted above

If you do not follow these configuration rules, the check prov fails and the systlists the conflicting speeds.

NTP 241-6401-805 PP6400There was a mistake in documentation in NTP 241-6401-805 PP6400. Pleasbelow for details.

-----------------------------------------------Passport 6400Bridging GuidePublication: 241-6401-805Document status: StandardDocument version: 7.0S2Document date: August 2000-----------------------------------------------

p. 139 --> bottom of page

Procedure 16Provisioning transparent bridging example

1. Enter provisioning mode.

start Prov

2. Define the base and feature software by specifying the application versi

list (AVL).set sw avl base_<software_level>bridge_<software_level> inWBase_<software_level> <---------module should be "inwBa


7.0.11

Documents