You are on page 1of 134

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 a working paper intended for limited circulation and discussion. No departmental or corporate approval or commitment is implied, unless such approval or commitment is expressly given in a covering document.

Copyright 2001 Nortel Networks All rights reserved

Release Notes for P7.0.11

Chapter 1

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

Chapter 2

Upgrading from previous releases . . . . . . . . . . . . . . . . . . . . . . . . 11


Required hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Passport 6400 mimimum hardware vintage . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 ATM IP cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Year 2000 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Century Compliant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Passports Century Compliance Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Changes to Passport Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Migration to a PCR release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 MPANL DLCI-0 Restart functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3

New features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 19


Summary of Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Quality levels for this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Release 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 List of new features and feature enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 22 Base features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Passport Vport Robustness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 NS Switch on Degrade Product Improvement . . . . . . . . . . . . . . . . . . . . . . . . . 22 FPGA Management System (PP804) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 CTR.4 E1C Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 CP Ethernet Local Connect (PP1081) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Display Banner Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 BTDS/HTDS features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 BTDS/HTDS on 8-port DS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4400 Interworking features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 25 MPANL DLCI-0 Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 IP features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 IP Configurable Route Preference (CD1220) . . . . . . . . . . . . . . . . . . . . . . . . . 28 LAN features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 BGP4 Enhancements (PP787) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Virtual Router Redundancy Protocol (VRRP) (PP901) . . . . . . . . . . . . . . . . . . 30 Passport CP Switchover for ILS WAN Services (PP225) . . . . . . . . . . . . . . . . 30 Passport IP Class of Service (CoS) (PP742, PP848) . . . . . . . . . . . . . . . . . . . 31 IP Multicast (PP855) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 SNA Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Mobile Interworking features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 32

Release Notes for P7.0.11

4 Voice features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 VNET Signalling Gateway Stage 1 (PP902) . . . . . . . . . . . . . . . . . . . . . . . . . . 32 MVPE G.729A Voice Encoding (PP868) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 MPVE V.17 Fax Relay at 14.4 and 12.0 kbit/s (PP868) . . . . . . . . . . . . . . . . . . 33 VNET Call Redirection (PP885) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Voice Networking Blind Digit Manipulation (PP1099) . . . . . . . . . . . . . . . . . . . 33 MPA Voice Accounting Interworking (PP1269) . . . . . . . . . . . . . . . . . . . . . . . . 33 MPANL SPO-mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 MVPe support for SG3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 ATM features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Passport ATM IP FP Introduction (PP504) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 ATM Virtual UNI (PP669) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 ATM Enhanced Statistics (PP796) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Product enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 HEC Error Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 NetBios/IPX Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 4

Release Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Guidelines for open issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 PM1 FPs memory engineering considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Memory usage rule for PM1s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Before migrating software levels on PM1 FPs . . . . . . . . . . . . . . . . . . . . . . . . . 42 Support Discontinued of 8 Mbyte CQC based ATM FPs (PDC1.0) . . . . . . . . . . . 43 Inter-LAN Switching (ILS) Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 RFC1490 Bridged Frame Routing Considerations . . . . . . . . . . . . . . . . . . . . . 44 Multiple Virtual Routers (MVR) Considerations . . . . . . . . . . . . . . . . . . . . . . . . 44 ILS on ATM FP CQC Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 ATM Multiprotocol Encapsulation (ATM MPE) Considerations . . . . . . . . . . . . . . . 44 IP Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 IPX Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 IP Multicast Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 OSPF Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 IP CoS Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Bridging Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 NetSentry Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 CP Crash: NetSentry clusterbridge filter configuration . . . . . . . . . . . . . . . . . . 55 BGP-4 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Base Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 BCS Broadcast Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 No check prov warning of TR/DS1V/E1V port reset . . . . . . . . . . . . . . . . . . . . 58 MPANL Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 MPANL SPO Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 PNNI on Passport release 7.0.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 PORS considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Configuring optional manual paths for a PLC . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 5

Release Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Release Notes for P7.0.11

5 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Helmsman-based CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Replacing CQC-Based ATM FPs with ATM IP FPs . . . . . . . . . . . . . . . . . . . . . . 64 Changing card type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Changes for Lp/n Arc Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Changes for Atmif ConnMap Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Changes for Atmif/x Ca Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Changes for Atmif/x Vcc Vcd and Atmif/x Vpc Vpd Components . . . . . . . . . . 65 Installation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 ILS startup introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Support Discontinued of 8 Mbyte CQC-based ATM FPs (PDC1.0) . . . . . . . . . 65 Component Administration System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Benign Recoverable Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Express Manager support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Preside Multiservice Data Manager (formerly known as NMS) support . . . . . . 67 Preside Multiservice Data Manager (formerly known as NMS) connectivity using IpiFr 67 SNMP agent considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 SNMP standard MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 SNMP Enterprise MIB considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 SNMP rolled up variable considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Multiple services per shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Maximum supported feature set per shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Multiple applications per function processor . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Function Processor sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Agent queue size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 PORS Mux mode directly connected to a first generation ATM FP . . . . . . . . . 75 PORS Map mode on ATM IP FP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 ATM IP FP - first generation ATM FP Interwork . . . . . . . . . . . . . . . . . . . . . . . . 76 PORS Degrade Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Frame Relay engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Frame Relay Trace engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 IpiVc and IpiFr coexistence engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Use of standby CP during software migration . . . . . . . . . . . . . . . . . . . . . . . . . 78 Spooled files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Base Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Unsupported card types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Hitless CP switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 CAS congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 CP crash caused by LCM,GCM and RemoteCallAgent using all msg block . . 80

Release Notes for P7.0.11

6 Manual Loopback Test on E1C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 V.54/PN127 Loopbacks on DS1C/E1C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Processor memory fragmentation issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Bus Clock Source status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Trunks, DPN gateways and networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Management Data Provider support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Loadsharing engineering considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 PORS LRC checking updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Full trunk statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 ATM port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 MCS considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Frame Relay migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 FRF.5 2K Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Rapid Start/Stop of DLCI loopback causes card reset . . . . . . . . . . . . . . . . . . . 83 Frame Relay Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 FR-ATM Gateway with Virtual Framer and LP sparing . . . . . . . . . . . . . . . . . . 84 FR-ATM now requires atmNetworking to be in Sw Avl avList . . . . . . . . . . . . . 84 FRF.5 and ATM traffic management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Data Loopback with Resiliency A bit condition . . . . . . . . . . . . . . . . . . . . . . . . 84 Frame Relay over EuroISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 ILS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 IP CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 IMA migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 IMA-specific enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 ATM processor operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Maximum ATM connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Maximum number of ATM test and loop components . . . . . . . . . . . . . . . . . . . 87 OC-3 Multi Mode Optic Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 ATM Trunk Utilization Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 8 port DS1/E1 ATM card independent and IMA links . . . . . . . . . . . . . . . . . . . . 88 Port Sparing of 4 ports or less on 8-port DS1/E1 IMA cards . . . . . . . . . . . . . . 89 ATM Resource Control (ARC) migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 ARU reporting section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Changes to the Atmif transmit queue limit defaults . . . . . . . . . . . . . . . . . . . . . 91 Queue Limit Software Errors in 7.0 against OC3MM-CQC . . . . . . . . . . . . . . . 91 3pDS/E1A to 8pDS/E1A card migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 3pE1A to 8pE1A Linetype migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 ATM Function Processor crashes after CPSO and LP switchover . . . . . . . . . 92 Virtual Path Termination (VPT) Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 ATM SPVC accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 ATM Cell Transfer display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Provisioning of subConnectionPool and lnnConnectionPool on ATM cards . . 94 ATM Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Release Notes for P7.0.11

7 Passport ILMI not UNI 3.0/3.1 compliant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Provisioning SPVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Reserved channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 SPVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Changes in the IEs for the service categories for all SPVC interfaces . . . . . . 96 ATM signalling channel failure on IMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 ATM accounting for N-PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Provisioning permanent VCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Private Network to Network Interface (PNNI) . . . . . . . . . . . . . . . . . . . . . . . . . 96 ILS on ATMIP FP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 AAL1 Circuit Emulation Service (CES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Changing the txQueueLimit with AAL1 CES connections active . . . . . . . . . . . 98 CES over PORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 New bandwidth limits for 4p E1 and DS1 AAL1 cards . . . . . . . . . . . . . . . . . . . 98 Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Voice Networking Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 MVPE G.729A Voice Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 MVPE V.17 Fax Relay at 14.4 and 12.0 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . 100 Provisioning Voice Networking - relay encoding minimum rate . . . . . . . . . . . 100 MCDN Anti-tromboning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

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

Appendix D Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132


NTP 241-6401-805 PP6400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Release Notes for P7.0.11

Release Notes for P7.0.11

Chapter 1 Introduction
This document provides essential information about the Passport 6400 software load 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 why


You should read this document if you are a planner, engineer or craftsperson responsible for accepting, testing or deploying the associated Passport 6400 software load. This document provides information about the content of the associated software load, the status of previously open software issues, and the installation requirements, if any. You should review the information to familiarize yourself with new features and functionality. Please ensure that you have read and understood the contents of the release notes and are aware of your devices specific capabilities prior to installing this software release to eliminate or minimize potential service interruption.

What you need to know


You must be familiar with Passport 6400 software installation procedures. Courses are available.

How this document is organized


This document is focused on the new content in the current release of Passport 6400 software. The document includes the following chapters: Chapter 2, Upgrading from previous releases, provides basic information about the R7.0.11 software level.

Release Notes for R7.0.11

10 Chapter 1 Introduction

Chapter 3, New features and enhancements, provides a summary new features and enhancements that are introduced in Release 7.0. Chapter 4, Release Considerations, provides information about unresolved issues and problems. Chapter 5, Release Planning provides information about planning deployment of R7.0.11

Appendices provide detailed information about the current release and previous releases: Appendix A: Known Limitations provides information about problems found in this release or previous releases which are not yet resolved. Appendix B: Resolved Limitations since last release lists the CRs that have been resolved since the last release. Appendix C: Items Resolved in Previous Releases lists the CRs that have been resolved in previous releases.

Related documents
A number of Nortel Network publications (NTPs) are available to support this release. For detailed information about the NTPs that apply to this release, see Documentation (page 63)

Release Notes for R7.0.11

Chapter 2 Upgrading from previous releases 11

Chapter 2 Upgrading from previous releases


This chapter provides basic information about the R7.0.11 (BG00SBB) software level. 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 hardware
Passport 6400 mimimum hardware vintage Table 1 provides information for minimum supported hardware for Passport 6400 FPs.
Table 1 Minimum supported hardware for Passport 6400 CP/FP Processor Type CP Card name long version Card name short version Minimum vintage level (PEC code)a NTFN33AA NTNN01AA NTNQ01AA NTFP61AA NTNN02AA NTNN53AA NTNQ53AA NTFP58CA NTFP30CA NTNN45AA NTNQ45AA NTNN51AA NTNQ51AA NTFP18EA NTNN46AA NTNQ46AA NTFP32CA NTNN52AA NTNQ52AA NTFP17EA Hardware information

Control processor

CP

PM2, SBIC, SCSI disk, 64 Mbyte PM2, SBIC, EIDE disk, 64 Mbyte PM2, SBIC, EIDE disk, 64 Mbyte PM2, SBIC, EIDE disk, 64 Mybte PM2, SBIC, EIDE disk, 64 Mybte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC 1.1, CQC, 16 Mbyte PDC 1.1, CQC, 16 Mbyte PDC 1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte

CFP1 ATM

Control and Function Processor 1 2-port JT2 ATM function processor 3-port DS1 ATM function processor 3-port DS3 ATM function processor 3-port E1 ATM function processor 3-port E3 ATM function processor

CFP1 2pJ6MAtm

ATM

3pDS1Atm

ATM

3pDS3Atm

ATM

3pE1Atm

ATM

3pE3Atm

Release Notes for R7.0.11

12 Chapter 2 Upgrading from previous releases Table 1 Minimum supported hardware for Passport 6400 (Continued) CP/FP Processor Type ATM Card name long version Card name short version Minimum vintage level (PEC code)a NTNN54AA NTNQ54AA NTFP16EA NTNN55AA NTNQ55AA NTFP38DA NTNN47AA NTNQ47AA NTFP80BA NTNN48AA NTNQ48AA NTFP82BA NTNQ49AA NTNN49AA NTFN14CA NTNN50AA NTNQ50AA NTFN16CA NTNQ65AA NTNN65AA NTJS07CA NTJS09CA NTNN66AA NTNQ66AA NTNN68AA NTNQ68AA NTJS13CA NTNQ67AA NTNN67AA NTJS11CA NTNN26AA NTNQ26AA NTFP67AA NtBP40AA NTNN16AA NTNQ16AA NTFN56AA NTFP56AA Hardware information

3-port OC-3 multimode ATM function processor 3-port OC-3 singlemode ATM function processor 4-port DS1 AAL1 function processor 4-port E1AAL1 function processor 8-port DS1 ATM function processor 8-port E1 ATM function processor 2-port OC-3 ATM IP function processor 2-port OC-3 ATM IP function processor 3-port DS3 ATM IP function processor 3-port E3 ATM IP function processor

3pOC3MmAtm

PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16Mbyte PDC1.1, CQC, 16 Mbyte PDC1.1, CQC, 16 Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC 1, AQM, 64 Mbyte PPC, PQC 2, AQM, 64 Mbyte PPC, PQC 2, AQM, 64 Mbyte PPC, PQC, AQM, 64Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC, AQM, 64 Mbyte PPC, PQC, AQM, 64 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM1, SBIC, 8Mbyte PM2, SBIC, 16Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8Mbyte

ATM

3pOC3SmAtm

ATM

4pDS1Aal1

ATM

4pE1Aal1

ATM

8pDS1Atm

ATM

8pE1Atm

ATM IP

2pOC3MmAtm2

ATM IP

2pOC3SmAtm2

ATM IP

3pDS3Atm2

ATM IP

3pE3Atm2

FR

1-port DS3C function 1pDS3C processor

FR

8-port DS1 function processor

8pDS1

Release Notes for R7.0.11

Chapter 2 Upgrading from previous releases 13 Table 1 Minimum supported hardware for Passport 6400 (Continued) CP/FP Processor Type FR Card name long version Card name short version Minimum vintage level (PEC code)a NTNN14AA NTNQ14AA NTFN47AA NTBP19DA NTNN17AA NTNN18AA NTNN19AA NTNQ19AA NTNQ17AA NTNQ18AA NTFN52AA NTFL04AA NTJS43AA NTBP88AB NTNN23AA NTNQ23AA NTNN24AA NTNQ24AA NTFN50AA NTFN71AA NTBP40AA NTNN15AA NTNQ15AA NTFN48AA NTBP21EA NTNQ20AA NTNN20AA NTNQ21AA NTNN21AA NTNQ22AA NTNN22AA NTFN57AA NTFK01AA NTJS46BA NTBP90AA NTNQ25AA NTNN25AA NTFN51AA NTBP71AB NTNQ27AA NTNN27AA NTFN58AA NTFP04AA Hardware information

4-port DS1 function processor

DS1 (4pDS1)

PM2, SBIC, 16Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 64 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 64 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 64 Mbyte PM1, SBIC, 8 Mybte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8 Mybte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8 Mybte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 64 Mbyte PM2, SBIC, 64 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 64 Mbyte PM1, SBIC, 8 Mybte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8 Mybte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8 Mbyte

FR

4-port DS1Ch function processor

DS1C (4pDS1Ch)

FR

1-port DS3 function processor

DS3 (1pDS3)

FR

4-port E1 function processor

E1 (4pE1)

FR

4-port E1Ch function processor

E1C (4pE1Ch)

FR

1- port E3 function processor

E3 (1pE3)

FR

1-port HSSI function processor

HSSI

Release Notes for R7.0.11

14 Chapter 2 Upgrading from previous releases Table 1 Minimum supported hardware for Passport 6400 (Continued) CP/FP Processor Type FR Card name long version Card name short version Minimum vintage level (PEC code)a NTNQ12AA NTNN12AA NTNQ13AA NTNN13AA NTFN45AA NTFN49AA NTBP38EA NTNQ10AA NTNN10AA NTNQ11AA NTNN11AA NTFN46AA NTFN73AA NTBP16DA NTJS02BA NTNN37AA NTNQ37AA NTNQ36AA NTNN36AA NTBP82CA NTFN59AA Hardware information

8-port V.11 function processor

V11 (8pV11)

PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM1, SBIC, 8Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM1, SBIC, 8 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte PM1, SBIC, 8 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM1, SBIC, 8 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM1, SBIC, 8 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM1, SBIC, 8 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, 32 Mbyte PM2, SBIC, MVP, 16 Mbyte PM2, SBIC, 16 Mbyte, Ecan PM2, SBIC, 16 Mbyte, Ecan PM2, SBIC, 16 Mbyte, Ecan PM1, SBIC, 6 DSP

FR

8-port V.35 function processor

V35 (8pV35)

ILS

2-port ethernet 100BaseT function processor 6-port ethernet 10BaseT function processor 1-port FDDI multimode function processor 1-port FDDI singlemode function processor 4-port Token Ring function processor ILS Forwarder function processor 1-port DS1 MVP function processor 1-port DS1 MVP-E function processor 1-port DS1 voice function processor

2pEth100BaseT

ILS

6pEth10BaseT

ILS

1pFddiMultiMode NTFN61AA NTFN39AA NTBP76EC 1pFddiSingleMode NTFN60AA NTNN40AA NTBP92EA 4pTokenRing NTFN42BA NTNN35AA NTBP78DA NTNQ38AA NTNN38AA NTFN18AB NTFN62AB NTNQ85AA NTNN85AA NTJS40BA NTFP41AB

ILS

ILS

ILS

IlsForwarder

Voice Voice

1pDS1Mvp 1pDS1Mvpe

Voice

1pDS1V

Release Notes for R7.0.11

Chapter 2 Upgrading from previous releases 15 Table 1 Minimum supported hardware for Passport 6400 (Continued) CP/FP Processor Type Voice Voice Card name long version Card name short version Minimum vintage level (PEC code)a NTFN20BA NTFN20CA NTNQ86AA NTNN86AA NTJS35BA NTFP43AB NTFN64AA NTNQ87AA NTNN87AA NTJS38BA Hardware information

1-port E1 MVP function processor 1-port E1MVP-E function processor 1-port E1 voice function processor 1-port TTC2M MVP function processor

1pE1Mvp 1pE1Mvpe

PM2, SBIC, 32 Mbyte PM2, SBIC, 16 Mbyte PM2, SBIC, 16 Mbyte, Ecan PM2, SBIC, 16 Mbyte, Ecan PM2, SBIC, 16 Mbyte, Ecan PM1, SBIC, 6 DSP PM2, SBIC, MVP, 16 Mbyte PM2, SBIC, 16 Mbyte, Ecan PM2, SBIC, 16 Mbyte, Ecan PM2, SBIC, 16 Mbyte, Ecan

Voice Voice Voice

1pE1V 1pTTC2mMvp

1-port TTC2M MVPE 1pTTC2mMvpe function processor

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

ATM IP cards Note: The "Required Hardware Release Levels" table for the newly introduced ATM IP cards, has been temporarily removed to update the card codes. For further information please contact your Nortel Networks Representative.

Upgrade overview
The 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 an unsupported level. Take note of specific feature related considerations documented in Release Planning (page 63). Software compatibility Table 2 (page 16) shows the minimum Preside Multiservice Data Manager (formerly known as NMS), MDP, Express Manager, DPN, and PP4400 software levels required for Passport compatibility.

Release Notes for R7.0.11

16 Chapter 2 Upgrading from previous releases Table 2 Preside Multiservice Data Manager (formerly known as NMS), MDP, Express Manager, DPN and PP4400 Software Compatibility
Passport Preside Multiservice Data Manager MDP Express Manager DPN-100 AM/RM PP4400 R7.0.11 (BG00SBB) MDM 13.4 Solaris MDP 13.4 Express Manager 4.2 G37.1.0 R4.0

Year 2000 Information


Century Compliance, as defined in the next paragraph, is Passports readiness for the Year 2000. Century Compliant Century Compliant means that the specified product functions until the end of its warranty period without any material, service affecting non-conformance to the applicable Nortel Networks product specification with respect to the operations performed by such product which are date dependent. This is true provided that the specified software load or release, if any, identified by Nortel Networks (including any associated hardware), has been installed with respect to such product; and further provided that the use of such product is in conformance with the associated user documentation. Do not interpret the statement that a product is Century Compliant as a commitment to support a product beyond its committed support window. As used in this document, Year 2000 Readiness, Year 2000 ready, and similar phrases mean that these products are Century Compliant as defined in the preceding paragraph. Passports Century Compliance Position Passport was conceived and designed as a Year 2000-ready product, to be able to properly process and display 4-digit years as part of a more important capability accurate date-processing before, during and after the Year 2000. Since its introduction, 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-week timekeeping

Readiness was integrated into the software for transition without hardware upgrade.

Release Notes for R7.0.11

Chapter 2 Upgrading from previous releases 17

Changes to Passport Interfaces Passport interfaces have not changed. Further Information For further information, please contact your Nortel Networks account representative.

Migration to a PCR release


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

MPANL DLCI-0 Restart functionality


To maintain MPANL DLCI-0 Restart functionality, it is required to migrate to a S/W load that supports the new feature (migration to S/W loads that do not support MPANL DLCI-0 Restart will result in loss of this functionality). At time of writing, this feature is planned for availability in the following loads/ SSUPs (please consult the release notes prior to migration): 7.0.11 PCR4.2.2 PCR5.2 CA load

Release Notes for R7.0.11

18 Chapter 2 Upgrading from previous releases

Release Notes for R7.0.11

Chapter 3 New features and enhancements 19

Chapter 3 New features and enhancements


This chapter provides information about features and enhancements that are introduced with Release R7.0.11 (BG00SBB). This chapter contains the following 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)

Release Notes for R7.0.11

20 Chapter 3 New features and enhancements


.

Summary of Features
Quality levels for this Release Different aspects of this release are available at different quality levels. These levels are defined as follows: Alpha - Software is still under development; not all functional tests have been completed; some unexpected behaviour can occur. This functionality is not supported. Beta - All functional testing has been completed, but stress, interoperability, and performance testing is still in progress. This functionality is supported for pre-authorized trials only. Contact your Nortel Networks representative. Controlled Release - All functional, stress, interoperability and performance testing has been completed. Functionality is available to a limited number of customer sites to provide expanded in-service testing prior to GA. This functionality is supported for pre-authorized customers only. Contact your Nortel Networks representative. General Availability (GA) - All internal and external (customer lab and network) testing has been completed; and feature load is generally deployable. This functionality is supported.

Release 7.0 The following table summarizes the features introduced within this Release:
Table 3 New Features in this Release Feature ATM IP FP Introduction (PP504) ATM VP Termination Phase 2 (PP604) ATM Virtual UNI (PP669) ATM Enhanced Statistics (PP796) FRF.8 NPVC Scalability (PP567) BGP4 Enhancements (PP787) CP Switchover for ILS WAN Services (PP225) CP Ethernet Local Connect (PP1081) Display Banner Message ATM VPT Management (PP793) FPGA Management (PP804) VNET SIgnalling Gateway Stage 1 (PP902) MVPE G.729A Voice Encoding (PP868) MVPE V.17 Fax Relay at 14.4 and 12 kbits/s (PP868) Voice Networking Blind Digit Manipulation (PP1099) Mpa Voice Accounting Interworking (PP1269) HotHaus DSP on MVPE (PP868) Release 7.0 GA GA GA N/A GA GA GA N/A N/A GA GA GA GA GA N/A N/A GA Release 7.0.10 GA GA GA Controlled Release GA GA GA GA GA GA GA GA GA GA GA GA GA Release 7.0.11 GA GA GA Controlled Release GA GA GA GA GA GA GA GA GA GA GA GA GA

Release Notes for R7.0.11

Chapter 3 New features and enhancements 21 Table 3 New Features in this Release (Continued) Feature Release 7.0 ATMMPE on ATM IP FP (IP, MVR, Netsentry) VRRP-100BaseT Ethernet/Token Ring (PP901) IP CoS (PP742, PP848) E1C CTR-4 ISDN Compliance (PP818) IP Multicast (PP855) PORS Adaptive Routing (PP520) ATMMPE on ATM IP FP (PP698) (IPX, Bridging) VNS over ATM Trunks on ATM IP FP (PP827) VNET Call Redirection (PP885) ATM IP Part 3 (ABR) (PP771) HEC Error Sensitivity NetBios/IPX Filtering MPANL SPO-mux Configurable Route Preference (CD1220) SNA Load Balancing BTDS/HTDS on 8 port DS1 MVPe support for SG3 MPANL DLCI-0 Restart GA GA Beta N/A N/A Alpha Alpha Alpha N/A Alpha N/A N/A N/A N/A N/A N/A N/A N/A

Release 7.0.10 GA GA GA GA GA Controlled Release GA GA GA Alpha GA GA GA Controlled Release GA Beta N/A N/A

Release 7.0.11 GA GA GA GA GA Controlled Release GA GA GA Alpha GA GA GA Controlled Release GA Beta GA GA

Release Notes for R7.0.11

22 Chapter 3 New features and enhancements

List of new features and feature enhancements


The 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 enhancements


Passport 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.048 Mb/s line speed capability to all the ports of a specified group; ports 1-4 or ports 5-7. Note: It is not recommended to provision the new speeds among old speeds within a group. NS Switch on Degrade Product Improvement Overview Passport provides a provisionable Network Clock Synchronization(NS) component for selecting the ports to be used as part of the network clocking scheme. Up to 3 reference sources can be provisioned (primaryReference, secondaryReference, and tertiaryReference). The NS Switch On Degrade Feature adds new attributes to govern the behavior of the NS component based on the port (physical layer) availability status. Current Implementation The common port management software normally interacts with the NS on the detection of major alarm conditions (los, lof, ais, rai, idle (ds3), mflof (e1), mfrai (e1), rfi (oc3) and port hw failure) and having detected such will inform the NS on the CP of the change in the port state and deregister itself. If the port is the currently active reference, then the NS on the CP will initiate a reference port switch. The primaryReference attribute will be considered first as a reference for the NS component. If this port fails due to a major alarm the NS component automatically initiates a change from the primary reference to the secondary or tertiary reference. When the primary reference errored condition has cleared then
Release Notes for R7.0.11

Chapter 3 New features and enhancements 23

the NS component will revert back to the reference port as specified by the primaryReference attribute. The Passport hardware has the ability to detect the errored condition AIS (blue alarm). The framer hardware having detected the AIS condition will trigger the generation of a minor alarm by the port management software. Along with the minor alarm, the port management software may also generate an availabilityStatus of degrade on the port (CAS> display Lp/x port/x availabilityStatus). Product Improvement The Passport NS AutoSwitch On Degrade Feature now adds the ability to perform a change in clock reference based on the availabilityStatus attribute of the port, of ATM cards, going to a degraded state. If this feature is enabled and having detected the degrade state, the port management software will now inform the NS process on the CP that it is going to deregister itself. As before, NS will then initiate a switch if the reporting port happens to be the currently active reference port. The following attributes now control the NS component :
set ns primaryReference lp/x port/x set ns secondaryReference lp/x port/x set ns tertiaryReference lp/x port/x set ns switchOnDegrade [ enabled | disabled ] // new set ns revertiveSwitch [ manual | auto ] // new set ns revertiveTime 5-120 // new - minutes

If the switchOnDegrade = disabled then the NS component will have the same behavior as described above (Current Implementation) and will not react to the port's degrade availability status. If the switchOnDegrade = enabled then the NS component will change reference due to the port's availability status going to a degrade condition. If the switchOnDegrade = enabled and the revertiveSwitch = manual, then operator intervention is required to switch the NS back to the primaryReference. This is accomplished by performing a lock and unlock of the primary reference port, provided that the degraded port condition has cleared. If the autoSwitch = enabled and the revertiveSwitch = auto, then reverting back to the primaryReference will happen automatically provided that the primaryReference degrade condition has cleared and remains stable for a period of time as specified by the revertiveTime attribute. A lock and unlock sequence on the primaryReference will bypass the revertive time and cause the reference switch over to happen immediately. The lock and unlock will disrupt any service that is currently running on the port. Target Cards The changes of this product improvement will target the Passport ATM (CQC Based) cards. This feature does not pertain to the frame based cards, LAN cards or features that generate an availability status of degrade at the application level. The frame and LAN based cards currently do not have the same behavior as the cell based cards. That is, the current implementation of the frame and LAN based hardware drivers do not generate a degrade availability state.

Release Notes for R7.0.11

24 Chapter 3 New features and enhancements

Provisioning Changes The following three new attributes are added to the NS component :
set ns switchOnDegrade [ enabled | disabled ] // default = disabled set ns revertiveSwitch [ manual | auto ] // default = manual set 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 with the hardware, customers no longer need to wait for an SSUP and can keep using existing software when the IM has changed. Interface Module (IM) Flash complements the Processor Module (PM) Flash by increasing the available Flash storage for future use Decreasing the number of FPGA file Decreasing the software downloading time

CTR.4 E1C Interface The CTR.4 E1C Interface feature extends the E1C capabilities to include CTR_4 compliance; thus, enabling the E1C to interface directly with ISDN networks. Previously, the E1C Functional Processor (FP) was available in standard and premium formats. Now, a new 64M channelized E1C card known as the CTR_4 compliant format is available and provides ETSI CTR 4 compliance, specifically for remote alarm indication (RAI). The premium E1C format is aimed for high capacity Frame Relay applications while the CTR_4 compliant format is primarily for connecting to ISDN networks in Europe. Features available on previous versions of the E1C will continue to be supported 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 indication (RAI) for ETS 300 011 compliance modification to provisionable attributes to selectively enable and disable hardware control of RAI.

CP Ethernet Local Connect (PP1081) This feature integrates the following capabilities with respect to the CP ethernet port on the Passport 6K. This feature is supported on the PP160, PP50, and PP30 with PM2 CP. 1 2 Support for telnet to the locally attached Passport node. Support for FTP file transfer to/from the locally attached Passport node.

Release Notes for R7.0.11

Chapter 3 New features and enhancements 25

Support for SNMP connectivity to the SNMP agent(s) on the locally attached Passport. Thisfeature will not support SNMP connectivity to remote passports through a Passport network.

This feature does not provide remote network management connectivity. Remote connectivity refers to the ability to manage other passport equipment through in band communication.
THIS FEATURE DOES NOT PROVIDE ANY PROTECTION AGAINST CONGESTION WHEN CONNECTED TO A LOCAL LAN.

Display Banner Message On 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 runs on a Passport switch, this implies that the banner message is composed on the NMS workstation. The composed message is then FTP'd to the /system/motd file on the Passport. If the /system/motd file does not exist, a banner is not displayed, so removal of the /system/motd file will remove the banner message from the system.

BTDS/HTDS features and enhancements


BTDS/HTDS on 8-port DS1 This feature provides BTDS and HTDS function on the 8-port DS1 FP. Currently, the BTDS and HTDS services are supported on the 4 port DS1 FP. From a service functionality perspective (BTDS/HTDS), there is no change from what was provided on the 4-port DS1 FP. The services behave the same way whether running on a 4-port or an 8-port card. The 8-port DS1 PM1 FPs (NTFP56xx) do not support this functionality. The 8port DS1 PM2 FPs (NTFN56xx) support up to 4 ports of BTDS/HTDS

4400 Interworking features and enhancements


MPANL DLCI-0 Restart The feature has been implemented with MPANL DLCI-0 Restart disabled/off as the default setting (current behaviour, no DLCI-0 Restart is sent by Passport 6400/Passport 7400) to ensure compatibility with existing networks (specifically PP4120/DPN networks, which are incompatible with the MPANL DLCI-0 Restart feature). If required, the feature is enabled by provisioning mpa/ 1 sig restartReqTimer with not zero value. MPANL DLCI-0 Restart, an optional procedure specified in Q.933, has been implemented to address interoperability issues between Passport 6400/Passport 7400 and Passport 4400. This procedure is different from restart on DLCI-16. Mpanl restart procedure on DLCI-16 affects only Mpanl SignalingMpanl component, Restart procedure on DLCI-0 affects only Mpanl Signaling. This restart procedure on DLCI-0 is not dependent on DLCI-16 Restart, as DLCI-16 restart is not dependent on DLCI-0 restart.

Release Notes for R7.0.11

26 Chapter 3 New features and enhancements

The restart procedure is used by an MPANL dte or dce to return the MPANL Signaling dte/dce interface to its default settings. The restart procedure is used by an MPANL dte or dce to recover from internal failure, after power-up, upon detection of DLCI-0 LAPF recovery, or after internal re-initialization. As a result of the execution of Restart procedure on DLCI-0, DLCI-0 returns to its default settings, meaning all SVCs are cleared. Restart Request Information Element

octet 1
1 0

Restart Request IE identifier


0 0 0 0 0 0

Figure: Restart Request Information Element

The Restart Request IE is composed of a single octet. The information element indicates 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

octet 1
1

Restart Acknowledgement IE identifier


0 0 0 0 0 0 1

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 dce in response to a restart request IE. The information carried in this IE has a per-interface context.

Release Notes for R7.0.11

Chapter 3 New features and enhancements 27

New Alarms
Alarm 7007 8100 Component Mpanl/<instance> Sig Severity minor Status message

Legend <instance> = a decimal value Details This alarm is generated at the Mpanl after two attempts to send a RESTART message to the adjacent Passport 4400 fail to result in a response with a RESTART ACKNOWLEDGE message. A restart request is sent out under certain conditions. This alarm is required for the interface to realize that attempts to synchronize the adjacent MPA have not been acknowledged. In compliance with procedures for restarts defined in the X.76 standard, the sender of the restart request can consider its interface available for use at this point. However, since no response indicates a possible lack of synchronization between the two passports, this warning is provided. Probable cause Type Remedial action Ensure that all switched DLCIs on the adjacent Passport 4400 are released.
Alarm 7007 8101 Component Mpanl/<instance> Sig Severity minor Status message

Legend <instance> = a decimal value Details This alarm is generated when the Mpanl is being requested to restart. Since a RESTART message can be received at any time, this alarm notifies the user that the Mpanl is being requested to restart by the adjacent MPA. Probable cause Type Remedial action No action required.

Release Notes for R7.0.11

28 Chapter 3 New features and enhancements

Alarm 7007 8102


Component Mpanl/<instance> Sig Severity minor Status message

Legend <instance> = a decimal value Details This alarm is generated when the Mpanl is being restarted. This alarm notifies the user that the Mpanl is being restarted after receiving a RESTART ACKNOWLEDGE message from the adjacent MPA, in response to its RESTART message. This alarm also indicates completion of the restart procedure. Probable cause Type Remedial action No action required.
Alarm 7007 8103 Component Mpanl/<instance> Sig Severity minor Status message

Legend <instance> = a decimal value Details This alarm is generated as a warning that the T317 timer has expired without the Mpanl receiving indication that the internal clearing has been completed. Timer T317 is started when the Mpanl receives a RESTART message from the adjacent MPA, and it enters the Restart state. The indication of the internal clearing prompts the Mpanl to stop the T317 timer and send a RESTART ACKNOWLEDGE message to the adjacent MPA, thereby completing the restart procedure. Probable cause Type Remedial action No action required.

IP features and enhancements


IP Configurable Route Preference (CD1220) This feature allows for the provisioning of the routing preference on a per routing protocol basis. In Passport each route is assigned a route preference. These values are currently hard coded (0 through 255) using defined constants per routing protocol. The preference is used by the routing manager as the first criteria of choosing which route to install from the routing table into the forwarding table.

Release Notes for R7.0.11

Chapter 3 New features and enhancements 29

For BGP, it also allows changing the routing preference on a per peer basis, by setting the corresponding Import policy's preference attributes to more preferred values. This could prove useful when the same routes (including default route) are learned through more than one peer. The default preference values used in this feature preserve the former hard coded ones(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 Protocols implementation. The feature does not check the sanity of the preference changing. This means that it should be done with caution and the knowledge of what effects it may have. The feature has been implemented for the following routing protocols: BGP, OSPF, RIP & Static Routing Protocol.

LAN features and enhancements


BGP4 Enhancements (PP787) This feature enhances the existing Passport BGP-4 functionality in the following ways: supports the Community Path attribute and acts accordingly as specified in RFC1997 selects a route based on the Path Attributes As Path and Communities under import 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 limitations Hardware There have been some issues noticed during the testing of BGP on the Passport 6000 which may affect customer network design. Primarily these have been around:
1 2 The amount of time required to bring up a BGP session with a peer. 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 number of BGP routes. Please plan your network designs accordingly. Special requirements This enhancement does not have any special requirements. This enhancement takes effect immediately after software load and does not require a system restart.

Release Notes for R7.0.11

30 Chapter 3 New features and enhancements

Release information This feature is introduced with Release 7.0. Virtual Router Redundancy Protocol (VRRP) (PP901) The Virtual Router Redundancy Protocol (VRRP) provides dynamic election of a VRRP virtual router (called Master) among a group of VRRP routers on a LAN. The elected Master is responsible for forwarding traffic for IP addresses controlled by the VRRP virtual router. If the elected Master router fails, VRRP will elect from the group a new Master to take over responsibility. VRRP eliminates the single point of failure inherent in the static default router environment. VRRP specifies an election protocol to provide the VRRP virtual router function. All protocol messaging is performed using IP multicast datagrams, allowing the protocol to operate over a multi-access LAN supporting IP multicast. Feature limitations Only supported on Token Ring and 100BaseT ethernet FPs. Hardware This feature has no hardware requirements. Special requirements This feature has no special requirements. VRRP takes effect immediately on software load and does not require a system restart. Release information This feature is introduced with Release 7.0. Passport CP Switchover for ILS WAN Services (PP225) The Passport CP Switchover for ILS WAN Services feature offers the following advantages: reduces the outage of ILS WAN services during a CP switchover (by the FP reload time) eliminates outage on WAN services that support hitless switchover provided all features on the card support it (otherwise an FP reset takes place) allows scheduled CP switchover with less impact

Feature limitations This feature has no specific feature limitations. Hardware All features loaded on cards must support hitless switchover to prevent WAN service outages. Special requirements This feature has no special requirements. This feature takes effect immediately on software load and does not require a system restart.

Release Notes for R7.0.11

Chapter 3 New features and enhancements 31

Release information This feature is introduced with Release 7.0. Passport IP Class of Service (CoS) (PP742, PP848) The Passport IP CoS with Release 7.0 feature provides the following benefits: 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 based media provides support for IP virtual private networks (VPN) by carrying CoS across Virtual Media and IP Tunnels classification of traffic at four different levels on a per protocol port interface or virtual router (VR) basis customer policy based class of service traffic prioritizing to define mission critical traffic supports ToS based interoperation with other devices including flexible setting of the ToS field, including the DiffServ Code Point

Feature limitations This feature has no specific feature limitations. Hardware This feature has no hardware requirements. Special requirements This enhancement does not have any special requirements. This enhancement takes effect immediately after software load and does not require a system restart. Release information This feature is introduced with Release 7.0. IP Multicast (PP855) Multicast provides the infrastructure for many new networking applications such as distance learning, software distribution and multimedia transmissions.IP Multicast on Passport uses Protocol Independent Multicast - Sparse Mode (PIMSM) to efficiently route multicast traffic to multiple individual host that may be sparsely distributed over a wide area. PIM-SM multicast routing protocol was
Release Notes for R7.0.11

32 Chapter 3 New features and enhancements

developed by an Internet Engineering Task Force working group and is defined in RFC 2362 . This feature is designed to restrict multicast traffic to only those routers with locally attached receivers or downstream routers interested in receiving this traffic, thereby minimizing the impact on network resources. The locally attached receivers can join a group to receive multicast traffic destined for that group. The receiver can also leave the group to stop receiving traffic destined for that group. SNA Load Balancing This feature provides a load balancing functionality across a Token Ring LAN where the multiple MAC addresses exist. The main benefit of this feature is that it provides an equal loading of the active link stations on a token ring LAN where there are multiple devices with the same MAC address. The load balancing has the capacity of finding all the routes to all the devices with the same MAC address. In order to do this the load balancing builds up its own table to keep all the routing information. This table is reconstructed periodically, in this way any malfunction is noticed and learned very fast. The functionality of this feature is based on the Local Device Monitoring (LDEV) which must be provisioned. The LDEV sends periodically "ping frames" to a given MAC address, the same MAC address on which Load Balancing should be applied. Based on the responses, the load balancing builds its own table identifying the MAC address and the routing information to reach that address. The limitation of this feature is that it can only provide load balancing functionality to one MAC address reachable via mulitple routes.

Mobile Interworking features and enhancements


There are no new Mobile Interworking features or enhancements in this release.

Voice features and enhancements


VNET 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 tandem PBXs Cost savings by eliminating redundant voice FPs. Since we no longer need links to gateway PBXs, the Passport 6400 hardware connected to the gateway 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 applications. MVPE G.729A Voice Encoding (PP868) This is a more efficient implementation of the G.729 voice encoding algorithm on MVPE

Release Notes for R7.0.11

Chapter 3 New features and enhancements 33

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 fax transmission while keeping bandwidth utilization low. VNET Call Redirection (PP885) VNET Call Redirection feature will allow VNET calls to be placed to alternate voice routes (Vroute(s)) regardless of the protocol being used (CAS, ETSI QSIG, MCDN etc..), in the case of load sharing, node failure, or original voice route failure. This feature will make Voice Networking more robust by allowing calls to route to a Hunt Group Server (HgS). A call to a Passport HgS DNA is sent to the HgS which chooses an eligible Hunt Group Member (HgM) DNA from the list available. If this eligible HgM DNA can accept the incoming call, the call will be connected. Otherwise, the next eligible DNA member of the list is chosen for hunting until the list has been exhausted. The choice of the HgM depends on the search mode and the HgM_s availability. To activate this feature provision a directory number in the VNCS to route to the HgS. The call will be presented to the hunt group server. The hunt group server will then select a destination HgM/ Vroute based on the algorithm selected and the HgM provisioned. Feature limitations The PP4400 will not work with this feature. The PP4400 cannot be a hunt group member for a given hunt group server. However the PP4400 can call a hunt group server 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. No manipulation is done to calling or connected numbers. Both en bloc and overlap dialing types are supported. The calling and connected numbers remain unchanged in order to ensure the reliability of the accounting records. Only a single message carries the digit information values (the SETUP for the calling number, and typically the CONNECT for the connected party number). Changing the calling or connected numbers makes accounting records unreliable, and makes billing inaccurate. MPA Voice Accounting Interworking (PP1269) The voice accounting on Passport interacts with peer voice services across the Passport network for single-ended or double-ended accounting record generation. The Passport Voice services that support a common subnetwork interface for accounting includes MPA voice accounting (MVA), legacy Passport Voice services, and Multipurpose Voice Platform (MVP). The functionality provided by this feature is: MVA source end accounting - When voice accounting is enabled on the MPA connected Passport switch then voice call accounting records are generated for calls originating from MPA.
Release Notes for R7.0.11

34 Chapter 3 New features and enhancements

MVA terminating end accounting - When voice accounting is enabled on the MPA connected Passport switch and the provisioned TerminatingEndRecords flag is enabled then voice call accounting records are generated for calls terminating at MPA. Double ended accounting - Exchange of voice call reference information exchanged between the MPA connected Passport switch and the peer voice switch allows correlation of accounting records generated at each end of a voice call when voice accounting is enabled.

MPANL SPO-mux This feature is an enhancement to the MPANL over PORS feature. MPANL SPO(Short Path Oriented) feature stabilizes the connection between Remote Server Agent (RSA) and Remote Server Interface (4400 and 6400) by splitting the negotiation of maxFrameSize for the Mpanl connection and for the MPANLPORS connection. This feature also corrects the issue with frame padding in PORS for Mpanl when SpoMux is needed. The end 4400 user has better control over the connection type used for MPANL voice calls. This leads to better quality of voice calls since voice quality is always better when using an SPO-mux mode connection. Prior to this feature, MPANL voice calls were always transported over either AAL5 mux or map mode connections. This feature allows MPANL voice calls to be transported over Spo mux as well . MPANL SPO connections are possible (specific to voice or video traffic) if a circuit of this type is properly provisioned. If not properly provisioned the system defaults 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 SG3 This change is to enable the completion of SG3 fax calls at the supported rates provided by V.17, V.29 and V.27ter (ie. 14.4 kbps and lower). This functionality does not support the V.34 standard but rather simply allows SG3 calls to downspeed to supported G3 rates. The downspeeding of SG3 fax calls to G3 rates is only supported in the faxRelay mode. The completion of SG3 fax calls at G3 rates is also supported in a 44006400 interworking scenario.

ATM features and enhancements


Passport ATM IP FP Introduction (PP504) ATM IP Functional Processors Four new Function Processors (FP) are supported by the feature: 2-Port OC3 SM 2-Port OC3 MM 3-Port DS3

Release Notes for R7.0.11

Chapter 3 New features and enhancements 35

3-Port E3

ATM IP Functional Processors are intended for use in the following environments: enterprise broadband networks using customer located or customer provided Passport switches full interworking with public carrier networks providing access services of all types, new and legacy, and trunking

ATM IP FPs are compatible with existing ATM systems. The new ATM IP Functional Processors provide: high performance adaptation for Frame Relay, IP and existing networking 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 introduction to existing networks a platform for ATM Forum traffic management phase 4 (TM4.0) and general TM improvements improved scalability for permanent connections, switched connections, and subconnections line rate frame forwarding (up to 155.520 Mbit/s per port on OC-3 FPs) on 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 FPs. (ConnMap is also removed for 8-port DS1 and E1 ATM FPs.) the entire VPI-VCI space is available for use removal of separation of the VPI-VCI space into regions reserved for VPCs 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 service mixtures
Release Notes for R7.0.11

36 Chapter 3 New features and enhancements

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 that provides a substantial performance increase (that is, a faster line rate for IP forwarding) standards compliant SONET 1+1 linear APS (line protection) that provides: unidirectional and bidirectional switching revertive and nonrevertive switching

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

Feature Limitations Not all the existing Passport software capabilities are supported in this release on the ATM IP FPs. 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 LANE ILS Tunneling

The capabilities that are not supported include:

Hardware The 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 37).

Release Notes for R7.0.11

Chapter 3 New features and enhancements 37 ATM IP OC-3 Single Mode FP & ATM IP OC-3 Multi-Mode FP hardware
backplane

APS switch port 0 Optical Line I/f SUNIDUAL AQM PQC ABC

CQM

CQM

MPC750 processor port 1 Optical Line I/f SDRAM

AQM

PQC

ABC

CQM

CQM

Special requirements

None ATM Virtual UNI (PP669) The Passport ATM Virtual UNI feature provides multiple virtual interfaces on one physical port. A virtual interface can be a User-to-Network Interface (UNI), an Interim Inter-switch Signalling Protocol (IISP), or a Private Network-toNetwork Interface (PNNI). Each virtual UNI, IISP, or PNNI is associated with a PVP, and has its own signalling channel which can set up SVCs within that PVP. In this way, the Passport ATM Virtual UNI feature provides SVC tunneling through a PVP network. ATM Enhanced Statistics (PP796) The ATM Spooled Statistics feature generates spooled statistics information for both ATM interfaces and Virtual Path Terminators(VPTs) on Passport. These statistics allow network engineers to gather data regarding the utilization of ATM resources within a Passport network.

Product enhancements
HEC Error Sensitivity
Introduction

Current implemetation of software allows for the possibility of excessive level of Header Error Count being received without shutting down the port. This situation has the potential to cause a degradation of service. The change will allow the operator to provision the delay timings between the receipt of 7 or more HEC errors and the raise of alarm to the minimum (1 ms). The changes will also allow

Release Notes for R7.0.11

38 Chapter 3 New features and enhancements

the operator to provision an HEC error threshold. If the accumulated HEC errors over provisionable intervals are greater or equal to the threshold, then the port will be shut down.
Current Implementation

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

The first part of the Product Improvement will enable an operator to provision the timing between OCD and LCD. If the timing between OCD to LCD and the timing between LCD to alarm are provisioned to the minimum, the sensitivity to the receipt of 7 or more consecutive HEC errors will be maximized. The new provisionable attribute lcdStateDelay will range approximately between 1 to 50 ms for DS1Atm and E1Atm cards (default 50 ms), 1 to 5 ms for DS3Atm and E1Atm cards (default 3 ms). In order to be able to provision the timing between the clearing of LCD anomaly (and uncorrectableHecErrors dropping down to half of provisioned hecErrorLimit, see below) and the port returning to service, an additional provisionable attribute clearDelay will be created. The attribute will range between 0 to 60 minutes (default 0). The second part of the solution will monitor the HEC error level, as defined by the existing operating attribute uncorrectableHecErrors for direct mapping. Once the uncorrectableHecErrors level is above hecErrorLimit (new provisionable attribute) over hecSampleInterval (new provisionable attribute) for consecutive hecErrorIntervalLimit , then the lcdAlarm will be issued and the port be brought down. This Product Improvement does not create any new message/alarm.
Recovery

After the port is down, the LCD condition is monitored continuously: 1 If there is no LCD asserted and if uncorrectableHecErrors drops below half of hecErrorLimit over hecSampleInterval seconds for the entire clearDelay period, then a clear alarm is to be issued and the port comes up. 2. 2.If LCD is asserted, then present LCD implementation (the implementation existing before this Product Improvement) will take precedence over the new hecErrorLimit/hecErrorSampleInterval/hecErrorIntervalLimit mechanism. This means uncorrectableHecErrors will not be monitored until LCD defect is cleared (uncorrectableHecErrors can not be monitored anyway because of H/W limitation). After LCD defect is cleared, if uncorrectableHecErrors is below

Release Notes for R7.0.11

Chapter 3 New features and enhancements 39

hecErrorLimit over hecSampleInterval seconds and there is no LCD defects for the entire clearDelay period, then a clear lcdAlarm is issued and the port comes up.
Target Cards

The changes of this product improvement will target all E1Atm, E3Atm, DS1Atm and DS3Atm cards. It will not target J6Matm cards. It will not target OC3Atm cards because the hardware used in these cards does not provide the capability to set the timing between OCD anomaly and LCD anomaly. Nor will the changes target AAL cards because such cards do not contain atmcell component.
CDL Changes

There will be four new provisionable attributes, all under the atmcell subcomponent (none of these attributes are applicable to J6MAtm, OC3Atm cards 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, depending on the type of card used) - new parameter that will determine the timing between entering OCD anomaly and moving to LCD anomaly. clearDelay (range 0-60 minutes, default 0 ms) - new parameter that will determine the minimum elapsed time before the port is allowed to return to active service after uncorrectableHecErrors is below half of hecErrorLimit and LCD anomaly absent continuously for the specified time. When the value is the default, the clearDelay time is actually 9.5 seconds 0.5 seconds. hecSampleInterval (range 0-25 seconds, default 0) When hecSampleInterval is 0, the mechanism of using uncorrectableHecErrors to bring down the port is turned off and hecErrorLimit will be ignored. When hecSampleInterval is n seconds (where 1 <= n <= 25) if the accumulative hecErrorLimit within n seconds is greater than the provisioned hecErrorLimit the sample interval is considered errored. If the number of consecutive errored intervals reaches hecErrorIntervalLimit an LCD alarm is declared and the port is disabled. hecErrorLimit (range 1-250000 uncorrectableHecErrors for DS3/E3, default 250000; range 1-10000 uncorrectableHecErrors for DS1/E1, default 10000) The default numbers represent roughly 25% error rate of the link capacity over 10 seconds (see the previous new provisionable attribute). The lower the provisioned value, the less uncorrectableHecErrors it would need to bring down the port. This attribute specifies the error threshold for a HEC error sampling interval. When the number of uncorrectableHeaderErrors in an interval of hecSampleInterval seconds is greater than or equal to hecErrorLimit, the sample interval is considered errored. If the number of consecutive errored intervals reaches hecErrorIntervalLimit an LCD alarm is declared and the port is disabled.

Release Notes for R7.0.11

40 Chapter 3 New features and enhancements

hecErrorIntervalLimit (range 1-25, default 1). This attribute specifies the limit on the number of consecutive errored HEC sampling intervals. When hecErrorIntervalLimit consecutive HEC error sampling intervals each have at least hecErrorLimit errors, an LCD alarm is declared and the port is disabled. NetBios/IPX Filtering This product enhancement allows the PP6400 IPX router to filter the IPX NetBIOS packets.

Release Notes for R7.0.11

Chapter 4 Release Considerations 41

Chapter 4 Release Considerations


This chapter provides information about unresolved issues and problems. This chapter contains the following sections: Guidelines for open issues (page 41) Inter-LAN Switching (ILS) Considerations (page 44) Base Considerations (page 58)

Guidelines for open issues


This section provides information that may help you work around some issues or problems related to identified but unresolved SRs. Workarounds are not available for all SRs. For more information, contact your Nortel Networks representative.

PM1 FPs memory engineering considerations


The PM1-based function processors (FPs) listed in Table 4 were Manufacture Discontinued in September 1998, and their hardware support ended in January 2002. However, software support for these FPs continues in R7.0.11, following the Passport Evergreen Software Policy, with the constraints listed in this release consideration.
Table 4 PEC codes for affected PM1 FPs
Unchannelized PM1FPs V.11 V.35 DS1 DS1 DS3 E1 E3 HSSI 8-port V11 8-port V35 4-port DS1 FR 8-port DS1 FR 1-port DS3 FR 4-port E1 FR 1-port E3 FR 1-port HSSI PEC code NTBP38xx NTBP16xx NTBP19xx NTFP56xx NTBP40xx NTFP21xx NTBP71xx NTFP04xx

Channelized PM1 FPs DS1C E1C 4-port DS1ch FR 1-port E1ch FR NTBP88xx NTBP90xx

Release Notes for R7.0.11

42 Chapter 4 Release Considerations

Memory usage rule for PM1s To 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 kbytes Channelized PM1 FPs: fastRam + normalRam + sharedRam = 14500 kbytes

FPs using more memory than this may load up and run, but are at risk of memory exhaustion when traffic bursts or other transient events occur, or if a patch or SSUP is loaded at a later date. So any PM1 FPs that exceed these limits should be reconfigured or replaced with a PM2 FP. PM2 FPs have 16 Mbyte or 32 Mbyte. In addition to more memory, PM2s have double the throughput of PM1s, Before migrating software levels on PM1 FPs Before migrating any nodes with PM1 FPs, consider whether the increased memory consumption of the target release level will push the PM1 FPs over the above limits. This can be easily forecast as shown below. It is critical to do this calculation long before the planned migration night, to allow time to order and deploy any required replacement FPs. Otherwise some PM1 FPs may fail to load after the migration, leaving end-users out of service. Note that the procedure below is based on the percent growth, release over release, for PM1 software packages as shown in Table 5.
Table 5 Percent memory growth on PM1 FPs
migration hop: % memory growth: R5.1 -> R7.0.11 10%

1) Display the current (before migrating) memory usage on the PM1 FP, using the command below. If there are many PM1 FPs in the network, an MDM script could 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

Release Notes for R7.0.11

Chapter 4 Release Considerations 43

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

Maximum memory usage allowed on PM1 at R5.1


Fast+Normal+Shared memory usage limit (in kbytes) from R5.1 to R7.0.11 PM1 FP type Unchannelized PM1 Channelized PM1 R5.1 7570 13551 R7.0.11 8100 14500

4) All PM1 FPs exceeding these limits should be reconfigured or replaced with PM2 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 provide reliable operation in R7.0.11. These FPs must be replaced either with the 16 Mbyte version of the same FP, or with an ATM IP FP prior to migrating to R7.0.11. These FPs are listed in the following table:
Table 7 8 Mbyte CQC-based ATM FPs (PDC1.0)
FP Type 3-port DS1 ATM function processor 8-port DS1 ATM function processor 3-port E1 ATM function processor 8-port E1 ATM function processor 3-port DS3 ATM function processor 3-port E3 ATM function processor 4-port DS1 AAL1 function processor 4-port E1 AAL1 function processor 2-port J2 ATM function processor 3-port OC-3 multi-mode ATM function processor 3-port OC-3 single-mode ATM function processor Unsupported PEC Range (8 Mbyte FPs) NTFP30AA - NTFP30BB NTFN14AA - NTFN14BB NTFP32AA - NTFP32BB NTFN16AA - NTFN16BB NTFP18AA - NTFP18DA NTFP17AA - NTFP17DA NTFP80AA - NTFP80AC NTFP82AA - NTFP82AC NTFP58AA - NTFP58BB NTFP16AA - NTFP16DB NTCP38AA - NTFP38CB Minimum 16 Mbyte Version NTFP30CA or NTNQ45AA NTFN14CA or NTNQ49AA NTFP32CA or NTNQ46AA NTFN16CA or NTNQ50AA NTFP18EA or NTNQ51AA NTFP17EA or NTNQ52AA NTFP80BA or NTNQ47AA NTFP82BA or NTNQ48AA NTFP58CA or NTNQ53AA NTFP16EA or NTNQ54AA NTFP38DA or NTNQ55AA

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

Release Notes for R7.0.11

44 Chapter 4 Release Considerations

Inter-LAN Switching (ILS) Considerations


RFC1490 Bridged Frame Routing Considerations A single DLCI for each IP COS value can be provisioned under a Remote Group provisioned with Bridged Frame Routing (BFR). Also, BFR cannot be provisioned under the default remote group (for example, no dynamic DLCIs). Finally, the bridging package is not required to be provisioned on the card running FrDte which results in a reduction in memory usage. Multiple Virtual Routers (MVR) Considerations All PM1 - based FPs currently in use, can still be used, provided only one Virtual Router is provisioned. When provisioning more than one VR, PM2 based ILS FPs and CP2s are required. The number of applications running under a Virtual Router, as well as the routing protocol type (static, RIP, EGP, OSPF Area Border Router, OSPF Internal Router, RIP, BGP4) and routing database size may have significant impact on the number of virtual routers that can be supported. Due to complex interaction between components, attention should be paid when more than 20 VRs are provisioned on a Passport. ILS on ATM FP CQC Considerations Migration Issue: VNS, SRES and NetSentry are not supported when this feature is enabled. If a Passport has any of these features configured, they must be removed before enabling ILS on CQC. Note: When commissioning a new shelf containing ILS, STARTUP procedures requires the ILS Forwarder Card. Interoperability Issue: Must not have VNS, SRES and NetSentry configured on the same shelf when this feature is enabled. This restriction applies if even one ATM MPE or LANE component has their ilsForwarder attribute set to blank. Note: VNS cannot be used on the same shelf, even if no ATM Logical Trunks are configured. Other issues: Performance will be significantly lower than what can be achieved using an ILS Forwarder Card. This feature is only supported for PDC1.1 based ATM FPs.

ATM Multiprotocol Encapsulation (ATM MPE) Considerations


To configure the ATM MPE feature, the ATM function processor as well as all function processors running ILS protocols must be configured with the ATM MPE software package. The ILS Forwarder card must be configured with the ATM MPE software package as well as the required ILS protocol software packages. Please see 241-6401-835 Passport LAN over ATM User Guide for more information.

Release Notes for R7.0.11

Chapter 4 Release Considerations 45

Sparing is supported for the ILS Forwarder card. It is recommended that the Vr Ip Arp autoRefresh attribute be set to disabled. If this attribute is set to enabled, it is possible that, under heavy ILS Forwarder congestion, ATM InverseArp Requests/Responses may be discarded resulting in a loss of IP connectivity across the ATM MPE link. In the event of a loss of IP connectivity due to ATM InverseArp Requests/ Responses getting discarded, a lock and unlock operation on the problem ATM MPE AC component will resolve the problem.

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

IP Considerations
A maximum of 2000 static routes can be configured in this release. This will be increased in a future Release. SNMP OSPF sets of operational attributes are not supported in this release. The maximum ping size allowed to be sent to a Passport virtual router protocol port is 30,600 bytes including headers. Due to buffer constraints, larger packets will cause the ping to fail. Care must be taken when clearing the ARP table to ensure ARP entries for ATM MPE are not cleared. These entries are established at call setup time and are not automatically replaced if deleted. If the entire ARP cache is intended to be cleared, lock/unlock of the ATM MPE component must be performed to re-establish the ARP table entries. To receive error free support for Remote Groups using IPX, both peers of a FrDte, X25Dte, and PPP circuit must be provisioned with the same preferred routing protocol (default type) and network number. If the connection is to a device that does not support the IW2 protocol, the Passport should be configured so that the default type attribute is configured as other.

IPX Considerations

IP Multicast Considerations
Provisioning a large number of static routes, hundreds for example, will result in a delay for the "Check Provisioning" command. Multicast statistics are not fully supported on Passport. Outgoing multicast packets will increment the ifOutUcastPkts statistic. Incoming multicast packets will increment the ifInUcastPkts statistic. This is true except in the case of ethernet media, where incoming multicast packets increment the ifInNuCastPkts and outgoing statistics increment the ifOutNuCastPkts. Also, if a static route is being used for multicast, the protocol port of the outgoing interface will see the ifOutNuCastPkts statistic incremented.

Release Notes for R7.0.11

46 Chapter 4 Release Considerations

OSPF Considerations
When there are 3 virtual routers configured in a meshed setup (e.g. A connects to B, B connects to C, C connects to A) a possible problem may occur. When all links are up and exporting routes into this OSPF domain is attempted, OSPF converges fine and the fastest path is used to reach the non-ospf routes. This can be seen in the RDB. For example, if the fastest path chosen to get to external routes off of A from C is through B and the physical port between C and B is locked, OSPF should re-converge to take the C to A path directly to get to the external networks. This however does not happen and the routes to these external networks are not propagated to the RDB. Hence, these networks become unreachable. If this occurs, the connection that is brought down is an atmmpe link. The work-around is to not lock the physical port to force OSPF to re-converge, but 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/x lock vr/n pp/x ipport lock atmmpe/n lock atmmpe/n ac/x

IP CoS Considerations
LogicalProcessorType Be sure to include ipCos in the feature list of all those LPTs associate with all ingress ports where ToS-based packet classification, Flow-based packet classification, Tos marking, Cos to EP mapping, and/or CoS to DP mapping are required. When only Layer 2 packet classification and CoS to VC mapping are required, ipCos is not required in the feature list. CosPolicyGroup A Policy Group associated an ingress protocol port serve to define ToS classification and Flow classification rules for packets entering the port. A CosPolicy Group associated an egress protocol port serve to define ToS marking and CoS to QoS rules for packets forwarded out that port. CosPolicyGroup It is highly recommended to leave the tosMask attribute under each CosTreatment component as its default value 0xFC in order to match to DSCP field for Differentiated Services. Policy When two ipAddrLayer4Flow components with the same protocol type having overlapping Layer 3 flow specifications are added under two different Policy components with different CoS under the same CosPolicyGroup, the CoS of the Policy containing the most precise Layer 3 flow specification (i.e. the one with the longest prefix length) takes precedence, regrardless of the Layer 4 flow specifications ( portRange ).
Release Notes for R7.0.11

Chapter 4 Release Considerations 47

When the two flow specifications have the same effective Layer 3 flow specification (i.e. they both have the same prefix length, and they both have same prefix up to the prefix length), then one of the follow two cases may occur: the two flow specifications have non-overlapping Layer 4 flow specifications (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 ranges when they have the same effective Layer 3 flow specification, so rather than provisioning:
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 50 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 = 10 15 which would lead to a semantic check error, one would provision: 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 9 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 = 10 15 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 = 11 50

FrDTE If CoS to QoS mapping is to be supported on FrDte then a different static DLCI and corresponding Fruni must be provisioned for each QoS. All virtual connections in the set must terminate at the same remote node. The QoS parameters 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 FrDte is provisioned with more than one static DLCI to the same next hop (for CoS-based selection of virtual circuit for forwarding refinement), it is recommend that the IfType attribute on the IpPort component is NOT set to pointToPoint. After provisioning static DLCIs with different CoS under an FrDte component and activating, lock and unlock the IpPort of the FrDte s linked protocol port. Note: Also see the section on Dynamica IP ARP Entries below.

Release Notes for R7.0.11

48 Chapter 4 Release Considerations

AtmMpe If CoS to QoS mapping is to be supported on AtmMpe then a different VCC and corresponding atmConnection must be provisioned for each QoS. All VCCs in the set must terminate at the same remote node. The QoS paramters of the ATM VCC must be set to reflect the required level of service. When the OSPF routing protocol is to be used on protocol ports where AtmMpe is provisioned with more than one atmConnection to the same next hop (for CoSbased selection of virtual circuit for forwarding refinement), it is recommend that the IfType attribute on the IpPort component is NOT set to pointToPoint. After provisioning atmConnections with different CoS under an AtmMpe component and activating, lock and unlock the IpPort of the AtmMpes linked protocol port. Note: Also see the section on Dynamica IP ARP Entries below. Dynamic IP ARP Entries Avoid clearing dynamic IP ARP entries learned by an AtmMpe protocol port if IP CoS is required. However, if it is necessary to clear IP ARP entries, note the following: If clearing any of the IP ARP entries of the same IP address, lock and unlock the IpPort of the AtmMpes linked protocol port. Static IP ARP Entries When a static arp entry is provisioned for an FRDTE or ATM MPE it replaces all of the dynamic arp entries, if any, for the IP address specified. When the static entry is later deleted, the dynamic entries entries do not automatically re-appear. The protocol port must be locked and unlocked to get the dynamic arp entries to re-appear. IP TUNNEL Interworking IP Cos with IP Tunnel is not presently supported. Virtual Media Unicast packets are not classified according to the assignedQos attribute on the protocol port (i.e by the Layer 2 classification method) at ingress to a virtual router, but multicast packts are. NMS PPMM The valid values that can be entered for provisioning the discardPriority attribute under the CosTreatment component are : unchanged,0,1,2,3; however the pulldown menu for this attribute displays unchanged only. Migration from Release 5.1 When migrating from a release 5.1 load (BE01*) to a R7.0 load (BG00*) certain migration steps which require manual intervention may be required to ensure a smooth migration without a loss of functionality.

Release Notes for R7.0.11

Chapter 4 Release Considerations 49

wanEmissionPriority Attribute Migration The wanEmissionPriority attribute in the QualityofServiceProfile component that exists in Release 5.1 is obsoleted by the new R7.0 emissionPriority attribute in the CosTreatment component. This change was done to provide more flexibility to the user when assigning an emission priority to outgoing packets under the CoS to QoS Mapping over single DLCI or PPP capability. With the attribute under the QualityofServiceProfile component, a specific emission priority was assigned to all packets of a particular class of service leaving the same virtual router. With the new attribute location under the CosTreatment component, an emission priority can be assigned for all packets of a particular class of service, but for all packets leaving a particular protocol port. Therefore the user would be able to provision different emission priorities for separate protocol ports for the same class of service. Unfortunately, since the new attribute is in the CosTreatment component (which requires ipCos to be provisioned in the featureList of the appropriate LogicalProcessorType component), some manual provisioning may be required to ensure there is no loss of functionality during the migration. Please follow the following steps to determine the provisioning steps that may be required before performing the migration to a R7.0 load.

Check to see if you are utilizing the CoS to QoS Mapping over single DLCI or PPP functionality based on the values of the wanEmissionPriority attributes in your current provisioning view for each defined VirtualRouter component, display the wanEmissionPriority attribute values under each QualityofServiceProfile 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|

Release Notes for R7.0.11

50 Chapter 4 Release Considerations

|4 |4

| |

2| 1| 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, then migration is required, if all the values are ep column are set to a value of 2, then NO migration is required, since the value of 2 is the default value of the obsoleted attribute wanEmissionPriority and the new attribute EmissionPriority.

If migration is still required (i.e. a wanEmissionPriority attribute was found with a value set to 1), then in order to prepare for the migration we need to ensure the proper CosPolicyGroup components exist in order for the migration to occur. During the migration, for each QualityofServiceProfile (QosP) component of each existing VirtualRouter (Vr), if the wanEmissionPriority attribute value is set to 1, then the EmissionPriority attribute of the CosTreatment component whose index matches the index of the QualityofServiceProfile component will be set to 1 for all CosPolicyGroup (pg) components defined under the same VirtualRouter. Pseudo-code example:
FOR x = {Vr[1st instance] TO Vr[number of Vr]} FOR y = {QosP[0] TO QosP[number of QosP]} IN Vr[x] IF Vr[x] QosP[y] wanEmissionPriority == 1 THEN FOR z = {Pg[0] TO Pg[number of Pg]} IN Vr[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 have CosPolicyGroup components existing to preserve the wanEmissionPriority attribute value during the migration. The following are the different steps that should be considered to preserve the value. for complete equivalence in functionality, for each VirtualRouter that has a wanEmissionPriority attribute value set to 1 (as checked in step 1), at least one CosPolicyGroup component should exist under the Ip component of the VirtualRouter, and one CosPolicyGroup should be linked to the VirtualRouter Ip

Release Notes for R7.0.11

Chapter 4 Release Considerations 51

component though the linkToPolicyUsers attribute (in other words, have a policy group linked to the VR). (In the first example Vr/3 and Vr/4 were the only VRs with an emission priority 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 operational subcomponents of the requested type. (In our example, the check for Vr/3 is OK as we have a policy group linked to the VR, but the check is not OK for Vr/4 as there are no policy groups provisioned) since the wanEmissionPriority attribute is only supported for FrDte and PPP media, actually only the FrDte and PPP media ProtocolPorts need to be ensured they are linked to a CosPolicyGroup, either directly through provisioning or instead inherits the CosPolicyGroup linked to the VirtualRouter as the default CosPolicyGroup. To check the CosPolicyGroup used by a ProtocolPort, look at the IpPort operational attribute operCosPolicyAssignment 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 +====================+-------------------Release Notes for R7.0.11

52 Chapter 4 Release Considerations

| Pp |operCosPolicyAssignm | | ent +====================+-------------------|ETH92 |! |PPP50 |! (In our example, the check for Vr/3 is OK as we have the policy group linked to the VR being used by our FrDte protocol port, but the check for Vr/4 is not OK as expected since we dont have any policy groups provisioned on Vr/4) 3 If there are any FrDte or PPP media ProtocolPort components that still need a CosPolicyGroup linked to it in order to migrate the wanEmissionPriority value of 1 into the new emissionPriority attribute, follow the following provisioning steps to add a CosPolicyGroup. in order to provision a CosPolicyGroup component, the ipCos feature must be provisioned in the featureList of the appropriate LogicalProcessorType component. if you do need to add CosPolicyGroup components and add the ipCos feature, then it is only required to be added to the featureList of the LogicalProcessorType components for WAN functional processors, as this functionality is only supported on FrDte and PPP media
(The following is an example as if we didnt have the ipCos feature previously provisioned) 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

Release Notes for R7.0.11

Chapter 4 Release Considerations 53 | | |frameRelayDte |atmmpe

(From displaying the features in the LPTs in our example, we see that only the V35 LPT requires the ipCos feature added since it is the only LPT that has PPP or FrDte running) 7> start prov Prov ok The edit view is identical to the current view. 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 to provision the CosPolicyGroup component)

provision a CosPolicyGroup component under each VirtualRouter that still requires a CosPolicyGroup assigned to it
12> start prov Prov ok The edit view is identical to the current view. 2000-xx-xx nn:nn:nn.nn

PROV 13> add vr/4 ip pg/VR4 (Weve created a CosPolicyGroup (pg) under vr/4 and appropriately named it VR4)

link the new CosPolicyGroup to either all the FrDte and PPP ProtocolPorts or to the VirtualRouter. It may be found more useful to link it to the VirtualRouter as any newly created FrDte and PPP ProtocolPorts will automatically use the CosPolicyGroup (and its provisioned CoS to QoS functionality) linked to the VirtualRouter.
PROV 14> set vr/4 ip cosPolicyAssignment vr/4 ip pg/VR4 PROV 15> check prov PROV 16> act prov PROV 17> end prov

Now the provisioning view is readyand can be migrated to a R7.0 load. After the load has completed migration, and if all the steps above were performed, you should see that the emission priority values properly stored as expected. Provisioning changes made to the discardPriority attribute under the CosTreatment component at R7.0 will not be preserved when migrating back to R5.1.

Bridging Considerations Fragmentation on Cluster Bridge is not supported. To avoid fragmentation, 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 to statistics.

Release Notes for R7.0.11

54 Chapter 4 Release Considerations

NetSentry filters applied on transparent bridge ports at incoming or outgoing do not function when they are first applied. The filter will be applied if the protocol port is locked then unlocked or if a different filter is applied to the filter point. When moving a station connected to one interface to another interface, the initial interface must be locked then unlocked to clear the entry in the forwarding table. Connectivity problems may result if the preserve domain attribute is set to on for 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 for a 802.3 frame over PPP media when going through a bridge. This feature is not supported over ATM-IP cards and is not reflected on this release, meaning that although the bConfigTinygram attribute under ppp/42 ncp component may indicate that the tinygram compression feature is enabled, it is actually not 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 is not in the feature list, the Function Processor will reset. Configuring NetSentry filters can significantly reduce throughput capacity. Careful filter design is required. Please refer to your Nortel Technical Support representative for assistance. Also, please see 241-6401-350 Passport Security and Access Control User Guide. Compilation of a filter file will fail if a single filter causes byte code to be produced which is greater than 32K. This is due to a 32K byte restriction of the PEV messaging system. Deleting a file under the vr/<vr_name> ns file/* subcomponent will not cause the filters contained in that file to be deleted. In order to delete filters it is necessary to delete the vr/<vr_name> ns subcomponent. However, filters can still be modified and updated correctly by placing the modified filter file in /provisioning/netsentry/prov and /provisioning/netsentry/oper directories and issuing the command reload vr/<vr_name> ns file/<file_name>.

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

Release Notes for R7.0.11

Chapter 4 Release Considerations 55

Bridging, frameRelayDte, etc.). However, the problem does not come from NetSentry itself, but rather from the ils media applications that do not act upon this NetSentry command.
Action priority Minimum spelling none Subcomponents priority

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

CP Crash: NetSentry clusterbridge filter configuration Applying a log_to action in the clusterbridge media will cause the CP to crash. A typical configuration might look something like:
filter BR_ETHER # Copy all ICMP packets ip_protocol in (1) alarm 1 log_to 208.42.18.185 35402 break; end

The packets generated by the filtering process are in turn processed by the filter generating more packets. The result is an infinite loop which consumes all available CPU and causes the CP to crash. The simplest workaround is to add a filter clause that checks the packet is not a log_to packet. The revised filter would look like this:
filter BR_ETHER # Do not relog the log_to packets udp_dp in (35402) break; # Copy all ICMP packets ip_protocol in (1) alarm 1 log_to 208.42.18.185 35402 break; end

This consideration applies equally to copy_to and route_to actions and has been documented in the 5.0 NetSentry 241-6401-350 Passport Security and Access Control User Guide.

BGP-4 Considerations
Memory limitation Assume:

Release Notes for R7.0.11

56 Chapter 4 Release Considerations

This assumption is based on the measurements made with live internet route feeds. The values below are approximate due to that BGP routes have a variable size data structure due to the variable size of the path attributes and the number of nlris sharing the same path attributes. Each First Indb routes uses 230 bytes of memory. Each successive Indb routes uses 105 bytes of memory. Each First Outdb (External peer or first Internal peer) routes uses 85 bytes. Each Second Outdb (internal peer) routes uses 70 bytes. Assume is a single VR configuration. Assume 5000 OSPF routes. Assume before any BGP connection is established, there is only 30 Mbytes free memory left. Assume 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 database F is the maximum number of routes supported. 230 x F + 105 x F + 85 x F = 470 x F = 34000000 - 4000000 = 30000000 420 x F = 30000000 F = 71428.571 Under this configuration, based on all the above assumptions, we can support maximum 71000 routes. More routes can be supported if fewer BGP route tables are required (i.e. network is not a transit AS). Reference Configurations Supported: The following reference configuration will still be supported: EBGP IBGP EBGP E1 ----------------- PP1-----------------PP2------------------ E2 Where E1 and E2 are BGP-4 speakers connected to Passports via External BGP (EBGP) peerings. PP1 and PP2 are Passport BGP-4 speakers connected to each other via an Internal BGP (IBPG) peering. The two passports are assumed to be in a single autonomous system. This topology only shows 2 Passports connected via IBGP. This simple topology is used only for describing the supported configurations. There could be as many as 32 BGP-4 speakers connected via IBGP. Configuration 1: EBGP IBGP EBGP E1 ----------------- PP1-----------------PP2------------------ E2 (default)--------->(default)--------------> <----------------(default)<---------(default)

Release Notes for R7.0.11

Chapter 4 Release Considerations 57

In this configuration, E1 advertises a default route to PP1 which in turn advertises it to all IBGP peers. E2 also advertises a default route to PP2 which in turn advertises it to all IBGP peers. The default routes are prioritized such that externally learned default routes take precedence over internally learned default routes. Configuration 2: EBGP IBGP EBGP E1 ----------------- PP1-----------------PP2------------------ E2 (Internet)--------->(DADR)----------------> <-----------------(DADR)<---------(Internet) In this configuration, E1 advertises the full Internet routing database to PP1 which compiles a Dynamic Agregate Default Route (DADR) from the Internet table which points to E1. PP1 then sends the DADR to all of its IBGP peers. E2 and PP2 behave the same as E1 and PP1. Configuration 3: EBGP IBGP EBGP E1 ----------------- PP1-----------------PP2------------------ E2 (Internet)------>(Internet)---------------> <---------------(Internet)<---------(Internet) We support configuration 3 with the limitation that we can only propogate the full Internet table to one IBGP or EBGP peer. Note: all the above configurations will subject to the memory limitation. RIP and BGP Interaction In version R7.0.11, RIP and BGP can be active simultaneously. However there is an issue with how the export policy to RIP operates (pulling information every 30 seconds) only the following configurations have been tested with sucessful operation: 1) 3000 BGP routes exported to RIP (per Passport Shelf) 2) Full Internet BGP routes with no export policy to RIP

Release Notes for R7.0.11

58 Chapter 4 Release Considerations

Base Considerations
BCS Broadcast Mechanism In Release 7.0, the BCS broadcast mechanism was disabled for FPs and nonactive CPs. Since no applications on the said cards use the broadcasting functionality of BCS, service is not affected. In the process of disabling the broadcast queue at startup, two types of SWERRs may be generated:
Shelf Card/1 BusTap/x; 2000-04-27 23:45:34.39 MSG indeterminate processing softwareError 00009000 ADMIN: unlocked OPER: enabled USAGE: active AVAIL: PROC: CNTRL: ALARM: STBY: notSet UNKNW: false Id: 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 AND PQC cards. This denotes that the broadcast queue is being disabled on the CQC/ PQC card.
Shelf Card/0 BusTap/x; 2000-04-27 23:45:34.39 MSG indeterminate processing softwareError 00009000 ADMIN: unlocked OPER: enabled USAGE: active AVAIL: PROC: CNTRL: ALARM: STBY: notSet UNKNW: false Id: 01000001 Rel: Com: Backplane broadcast data found. 0c0cc00000000c0/7/3 2 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 octetabove software error is The 1

generated during a CP reload. It denotes that the broadcast queue is being purged. These software errors are not service affecting in any way and normally happen once when cards on the shelf are rebooting. Any other occurrance of these software errors signals irregular use of the BCS broadcast mechanism. No check prov warning of TR/DS1V/E1V port reset At 7.0, provisioning changes to vendor, commentText and defaultTraceLevel attributes of any lp/x tr/y component will pass check prov without a warning, but will cause the port to reset upon activation. Provisioning changes to other attributes of the lp/x tr/y component will result in the following check prov warning. PROV 70> ch pr Prov
Release Notes for R7.0.11

Chapter 4 Release Considerations 59

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 after the initial deployment of the Token Ring FP. Adding an appropriate warning octet 1 message during a check prov is not possible as this would cause the warning to appear for all other port types that do not reset under these conditions. Refer to SR 10408605 for more information. Also affected are 1pDS1V and 1pE1V FPs. Since these are 1-port FPs, changes to vendor and commentText attributes of lp/x ds1/x (or lp/x e1/y) will cause the FP to reset.

MPANL Consideration
MPANL SPO Enhancement In order to enable the MPANL SPO feature after migration from 5.1 to 7.0, the following steps are to be followed: 1. Upgrade the switch to R7.0.11 (BG00SBB) 2. Change the MPANL VOICE USESPO to YES
SET MPANL/<n> VOICE USESPO YES

3. Lock and unlock all mpanls


LOCK -F MPANL/<n> UNLOCK MPANL/<n>

Note: SPO could be either SPO-MUX or SPO-MAP, depending on the ATM connection mode: MUX or MAP. PNNI on Passport release 7.0.11 The Passport Release 7.0.11 supports exactly the same PNNI capabilities as Passport Release 5.1. There were no enhancements made between the two releases. This means that the following enhancements to PNNI are NOT supported. This is not an exhaustive list, but is meant to highlight the key features that 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 Enterprise stream. 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

Release Notes for R7.0.11

60 Chapter 4 Release Considerations

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

PORS considerations
Configuring optional manual paths for a PLC Configure a manual path, which consists of a sequence of hops, identified by node name and egress trunk for transparent data services (TDS). Services linked to a manual path can also override the manual path setting through the manualPath or porsManualPath attribute associated with connections for that service. Note: If you change the configuration of an existing manual path to specify a different route, the services that use that ManualPath component automatically switch to the new route. You do not need to lock or disable the service. Procedure 1 At the source node, add the btds instance
add btds/<instance>

2. Set the interface name


set 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 name


set btds/<instance> plc remoteName <switch>

5. Define the first hop in the route by specifying the originating node and the
path 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 hop is assigned index 0, the seconds assigned index 1 and so on. 6. At the destination node, repeat steps 1 and 2. Variable definitions Table 8 contains definitions of the attribute values in Configuring optional manual paths for a PLC.
Table 8 Variable Definitions
Variable <index> Value This value is a decimal from 0 to 19 that indicates the position of the hop in the route. The first hop is assigned index 0, the second is assigned index 1, and so on.

Release Notes for R7.0.11

Chapter 4 Release Considerations 61 Table 8 Variable Definitions


Variable <n> <switch> <trunk> Value This value is a decimal of 1 to 255 that identifies the PORS manual path. There is no default value. 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 ( ).

For more information, please contact your Nortel Networks Representative.

Release Notes for R7.0.11

62 Chapter 4 Release Considerations

Release Notes for R7.0.11

Chapter 5 Release Planning 63

Chapter 5 Release 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 FPs with ATM IP FPs (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)

Documentation
For details on the changes to the NTPs, including feature impacts, fixed service requests, and removed documents, see 241-6401-000 Passport 6400 Whats New in the Documentation Suite. As of R7.0.10, there are changes to the way that the Passport technical documentation is made available to you. The UniHelp interfaces and the eDocs web site have been decommissioned. The rest of this section describes the current delivery methods: - Internet on page 63 - Intranet on page 63 - Helmsman-based CD-ROM on page 64 - Paper on page 64 Internet Over the Internet, you can use Helmsman Express on the Nortel Networks web site to view, do a suite-wide search, or download documents in PDF format. To register for access to Passport documents on Helmsman Express, contact your Nortel Networks account representative. Intranet You can install the Passport documents on a server in your own intranet to provide access to the documentation using the Helmsman software. Install the documents and Helmsman from the Helmsman-based CD-ROM (page 40).

Release Notes for R7.0.11

64 Chapter 5 Release Planning

Helmsman-based CD-ROM The Helmsman-based CD-ROM contains the current release of Passport documentation in PDF format, viewable with the Helmsman software. The CDROMincludes the Helmsman software as well as installation software for the PC, Unix (Sun and HP) and Macintosh platforms. Helmsman provides suite-wide search capabilities. Installation instructions are provided on the CD-ROM. Your Nortel Networks account representative needs to place an order for you to receive the CD-ROMs. Depending on which Performance Pack support package you have, you receive either one copy or up to five copies of the Helmsmanbased CD-ROM. Paper You can purchase sets of Passport documentation in hardcopy format in binders, at extra cost. For more information or to purchase hard copies, contact your Nortel Networks account representative.

Replacing CQC-Based ATM FPs with ATM IP FPs


To take advantage of new functionality on the new PQC-based ATM FP, you can upgrade your hardware from a CQC-based ATM FP to a PQC-based ATM FP. Changes in provisioning are required to replace a CQC-based FP with a PQCbased FP. If these mandatory provisioning changes are not made, semantic check errors will result when the card type is changed. The changes described here represent a minimal set required to make a PQC-based FP work and do not leverage 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 is the card type. Those with a customized configuration for either the Arc, ConnMap, or Ca components, must follow the instruction/semantic errors for those components. Changing card type The Shelf Card/n cardtype must be changed since the CQC-based FP and PQCbased FP have different card types. If the interface type of the card is also changed, the port subcomponents underneath the LP/x component must be replaced. If the number of interfaces is reduced on the new card type, the components relating to the additional interfaces must be deleted (for example, ATMIF). Changes for Lp/n Arc Component If the Lp/n Arc Cqc Override component exists, it must be deleted Adding the Lp/n Arc Aqm/x Override component is optional.
Release Notes for R7.0.11

Chapter 5 Release Planning 65

Changes for Atmif ConnMap Component If the Atmif ConnMap component exists, it must be deleted Changes for Atmif/x Ca Component For PQC-based FPs, if a service category has traffic shaping enabled, then the unshapedTransmitQueueing attribute must be set to autoConfigure. Common queueing and traffic shaping are not supported simultaneously for the same service category. Changes for Atmif/x Vcc Vcd and Atmif/x Vpc Vpd Components For PQC-based FPs, the unshapedTransmitQueueing attribute can only be set to a value of sameAsServiceCategory. The method of transmit queueing (perVc or common) can only be chosen per service category and not per connection.

Installation Planning
Installation procedures provided in NTP 241-6401-605 Passport 6400 Operations and Maintenance Guide apply to this release. ILS startup introduction You have the option of setting up IP communication using ILS IP capabilities between a newly commissioned Passport switch and one of the following: a software download site (Preside Multiservice Data Manager (formerly known 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-270 Passport 6400 StartUp Guide.

Migration planning
This section provides information needed to plan the migration from an earlier software 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) on page 43 for details. Component Administration System Due to a limitation in CAS, you must manually delete the obsolete AtmCr component during software migration from level 4.2 to level 7.0. Benign Recoverable Errors You may see the following benign recoverable error within the first four minutes after a shelf has been migrated from R4.2 to R7.0 (or a roll-back from R7.0 to P4.2) and there are frame relay connections terminating on the shelf:
Recoverable Software error at line 93 in file dmeLocalFrameS.cc Release Notes for R7.0.11

66 Chapter 5 Release Planning --- 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 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 CPU utilization: 45 percent busy CPU: i960 CF (E-step) No Traceback when at interrupt level Application level information at time of exception: Date: 1998-05-24 Time: 13:45:07 Card type: 3pDS3Atm Committed File : N/A Current view file: N/A Software version: BE00C CAS Information: COMPLETED: fpAct Synchronization begins. Synchronization ends.

This recoverable error does not indicate any problem. Instead, it indicates that stale frame relay data traffic from the other end of the frame relay connections, that was set up before the software migration, has been properly discarded. The reason that the discarding is causing the generation of this recoverable error in R7.0 is due to a format change of the internal data structure. As such, the benign recoverable errors should only be observed within the period of 4 minutes after 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 using the normal procedure for handling recoverable errors as detailed in the Troubleshooting section of NTP 241-6401-605 Passport 6400 Operations and Maintenance Guide.

Network management
This section provides information needed when performing network planning and management during software migration. This section contains the following subsections: Express Manager support (page 67) Preside Multiservice Data Manager (formerly known as NMS) support (page 67) Preside Multiservice Data Manager (formerly known as NMS) connectivity using 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)

Release Notes for R7.0.11

Chapter 5 Release Planning 67

Express Manager support Express Manager 4.2 will support Passport 6400 Release 7.0 (with custom templates), on Windows NT and 2000 operating systems. Express Manager 4.2 does not support Passport 7400 modules and the PCR stream. Express Manager 4.2 is the last release and the product will be supported only for the life of the Passport 6400 Release 7.0 stream. All prior releases of Express Manager are service discontinued as of December 31, 2002. Preside Multiservice Data Manager (formerly known as NMS) support Preside Multiservice Data Manager (formerly known as NMS) Release 12.5 (or higher) with Solaris is required to support Passport networks running this Passport release. Preside Multiservice Data Manager (formerly known as NMS) connectivity using IpiFr Ipifr DefaultRoute (DR) has been obsoleted since P4.2. It is replaced by Ipifr StaticRoute (SR) /0.0.0.0, which performs the same functions. During software migration, the new component of Ipifr SR/0.0.0.0 is created and its attribute ipiGtyIpAddress is set to the value of the IpiFrs DR. After the Passport is fully activated, 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 IP DefaultRoute, look at the IpiFr StaticRoute/0.0.0.0 component. The remoteIpAddress attribute of the IpiFr Lcn component is introduced with this release. The attribute provides a Static Address Resolution implementation (for example, mapping IP addresses to the link layer or, in this case, DNA addresses). In previous releases, address resolution was performed by inspecting the source IP address of the first IP packet sent over the LCN. If the remoteIpAddress attribute is not set, address resolution continues to depend on the source ID address. IpiFr configurations which use a router on a non-default route must implement non-standard router configurations in order to ensure that the correct address is resolved by the Passport. You should set the remoteIpAddress attribute for any configurations which have a router interfacing with the Passport network using IP over frame relay (for example, ipiFr). Set the remoteIpAddress to the routers IP address in order to take advantage of the router. Add an IpiFr StaticRoute to route to the network/ subnetwork/host IP address containing the management workstations. SNMP agent considerations The Passport SNMP agent supports SET on all components. You should be aware of the following SNMP considerations.

Release Notes for R7.0.11

68 Chapter 5 Release Planning

Full semantic checks (as per check prov) are performed when provisioned data is changed with an SNMP SET. The checks may take a long time, depending on the kind and extent of the provisioned data changes. Since the SNMP agent is unable to process other SNMP GET or SET requests until checks are finished, SNMP surveillance applications may be locked out temporarily. Change provisioned data using SNMP SET sparingly. Make only simple provisioning 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 yet been completed. (The first semantic check after a software upgrade is a complete check of all provisioned data and may take a long time.) Once a check prov has been done from the console, telnet session, or fmip session, SNMP SETs are accepted.

SNMP standard MIB Support for RFC 1657 Border Gateway Protocol Version 4 is introduced in this release. For a complete list of standard MIBs supported by SNMP refer to NTP 241-6401-300 Passport SNMP User Guide. SNMP Enterprise MIB considerations You can view all operational and provisionable attributes using SNMP. To take advantage of SNMP for surveillance purposes, you must have a workstation equipped with a standard SNMP package such as HP OpenView. You must configure Nortel Networkss SNMP Enterprise MIB, which is provided with the software. For further information, see: the README file in the MIBs directory on the software distribution site NTP 241-6401-300 Passport 6400 SNMP Guide

SNMP Enterprise MIB changes The Passport Enterprise MIBs are Nortel Networks proprietary MIBs for managing Passport. This section identifies the Passport Enterprise MIBs that are new in this release, the MIBs which have been modified, and the MIBs that have not been modified. A modified MIB indicates that the existing contents are modified or that additional informational elements are added. New MIBs nortelPP-bgpV1_BG00SBB.mib
Release Notes for R7.0.11

Chapter 5 Release Planning 69

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
Release Notes for R7.0.11

70 Chapter 5 Release Planning

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
Release Notes for R7.0.11

Chapter 5 Release Planning 71

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 considerations This section lists the component classes which are supported in the Passport State Summary Table. The OSI state and status of each component class is tracked in the form of rolled up state variables. An SNMP management application can optimize the polling of state values with the use of the Passport State Summary Table.
Table 9 SNMP Rolled Up Variables Supported Component Classes Supported Component Classes LogicalProcessor LogicalProcessor Ethernet LogicalProcessor Fddi LogicalProcessor DS3 LogicalProcessor E3 LogicalProcessor DS1 LogicalProcessor E1 LogicalProcessor V35 LogicalProcessor X21 LogicalProcessor TokenRing LogicalProcessor Sonet LogicalProcessor Sdh LogicalProcessor JT2 LogicalProcessor Hssi LogicalProcessor IlsForwarder LogicalProcessor Eth100Bt LogicalProcessor InverseMultiplexerAtm Shelf Card FileSystem FrameRelayNni FrameRelayUni FrameRelayAtm Release Supported P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0 P7.0

Release Notes for R7.0.11

72 Chapter 5 Release Planning Table 9 (Continued) SNMP Rolled Up Variables Supported Component Classes Supported Component Classes AtmInterface Release Supported P7.0

Engineering
This section provides information about engineering considerations. This section contains 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 shelf A Passport can be configured to operate with many different combinations of Function Processors and services on each shelf. As the number of services combined on a single shelf increases, make sure that there is sufficient trunk capacity and that proper priority is placed on the various service types to ensure correct congestion handling. Contact your Nortel Networks Networks Technical Support representative for additional information. Maximum supported feature set per shelf Certain service mixes, combined with a large number of defined components, consume a large quantity of memory. Ensure that Control Processor memory monitoring 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 be less than 22 Mbytes on a CP1. For CP2 and CFP1, the sum should be less than 57 Mbytes. If you have any questions regarding the memory consumption of different service mixes, contact your Nortel Networks Networks Technical Support representative.
Release Notes for R7.0.11

Chapter 5 Release Planning 73

Multiple applications per function processor Function Processors can support multiple services. Performance and engineering complexity increases with the number of services configured. Consult your Nortel Networks Networks Technical Support representative for engineering assistance. Use the following guidelines for high level planning: The order in which services are entered in the SW LPT/xx featureList associated with a given FP is important. Services are loaded in the Fast RAM of an PM1 FP based on the order in which you enter them in the associated SW LPT/xx featureList. Not all the services and their prerequisites will be placed in Fast RAM in situations where memory runs low. Additional services and prerequisites may be loaded in Normal RAM, adversely affecting performance.
Note: Second Generation Function Processors do not use fast RAM. Therefore the order of entry does not matter on Second Generation hardware.

If you configure a VNS service to carry ILS traffic over Passport frame-cell trunks, you must configure all ILS function processors, and all function processors carrying ILS traffic, with VNS. If you configure ATM MPE to carry ILS traffic over ATM facilities, you must configure all ILS function processors, and all function processors carrying ILS traffic, with ATM MPE. You can configure a Function Processor with both Frame Relay UNI and ILS Frame Relay DTE services, with DTE and DCE port interfaces connected by rolled cables or through the use of a virtual framer. In addition, you should limit the number of frame relay PVCs to ILS Service connections only. In this case, 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 when planning the introduction of new products. Do not use this solution when performance is a consideration.

Do not use multiple application combinations when high performance of a specific application is required. If you use multiple application combinations you should split the multiple application combination to take optimum advantage of the FPs memory and performance capabilities. The following two tables list applications and services supported on each FP. This does not imply that all the applications/services shown can operate concurrently on an FP. For details on the application/service combinations supported on individual FPs, see the Performance Specification Reference Guide NTP 241-6401-100. Note: For the all the tables in the Engineering Consideration section, an application is defined as a generic type, such as Frame Relay (FR). Each application is composed of individual services, such as FR UNI, FR NNI, FR SVC, and FR Trace in the case of Frame Relay.
Release Notes for R7.0.11

74 Chapter 5 Release Planning

Please contact your Nortel Networks Technical Support representative for further assistance.
Table 10 Applications/services supported by processor cards
Processor cards DS1 ATM (3-port) DS1 ATM (8-port) Ethernet (100 M) E1 ATM (8-port) E1 ATM (3 port) Ethernet (10 M) ILS forwarder

12m Vsp Aa1 x x

2p DS3c Aa1 x x

DS1 (4-port)

DS1 (8-port)

Token Ring

DS1 AAL1

DS3 ATM

JT2 ATM

Applications /Services V.11 V.35

Trunks: Routing systems for Passport Frame / Cell Trunks: DPRS x x PORS x x VNS see Note 2: x x Routing systems for Passport ATM Logical Trunks: DPRS PORS VNS see Note 2: DPN Gateway: over UTP x x over FR x x Frame Relay: FR UNI x x FR NNI x x FR SVC x x FR Trace x x FR-ATM interworking x x FR ISDN PANL see Note 5 Dedicated mode x x Tunnelled mode x x ISDN access VTDS: HDLC Transparent Data x x Bit Transparent Data x x Voice Access ILS: IP x x IPX x x Transparent Bridging x x SRB x x SRES x x SNA Data Link Routing NetSentry x x PPP x x FR DTE x x X.25 DTE x x GeneralVcIf LANE Client ATM: AAL1 CES ATM Bearer Service ATM networking (UNI,IISP,PNNI) ATM MPE x x ATM IMA Packet Voice Gateway over ATM Packet Voice Gateway PVG: Over Atm

x x x

x x x

x x x

x x x

x x x

x x x

x x x x x x x x x x x x x x x x x x x x x x x x x x x

x x x x x x x

x x x x x x x x x x x x x x x x x

x x x x x x x x x x x x x x x x x

x x x x x x x x x x x x x x x x

x x x x x

x x x x

x x

x x

x x

x x x x x

x x

x x

x x x x x x x x x

x x x x x x x x x

x x x x x x x x

x x x x x x x x

x x x x x x x x x

x x x x x x x x

x x x x x x x x

x x x x x x x x

x x x x x x x x

x x x

x x x

x x x

x x x x x x x

x x x x x x

x x x x x x x x x x

x x

x x

x x

x x x

x x x

x x

x x x

x x x

x x x

x x x x

x x x x x x

Note 1: An x shown in a column indicates that a service (listed by row) is supported on a function processor (displayed in columns). Note 2: VNS includes transport of all LAN Upper Layer Protocol (ULP). Note 3: When ATM MPE operates on CFP1, it is assumed that an ATM FP and an ILS Forwarder FP will run beside it. Note 4: For FR-ATM interworking and FrDTE, both logical and physical connections on the same FP are supported. Note 5: Supported on PM2 only.

Release Notes for R7.0.11

32p E1 Aa1

OC-3 ATM

E1 AAL1

E3 ATM

DS1C

DS3C

CFP1

HSSI

FDDI

DS3

E1C

E1

E3

Chapter 5 Release Planning 75 Table 11 Voice and bit transparent data services applications/services supported by function processorsApplication combinations
Applications/Services 1pDS1V x x 1pE1V x x J2MV 1pDS1Mvp 1pE1Mvp x x x x x x x TTC2MMvp x x

Bit Trans. Data Voice Service (VS) DCME Voice Networking (VNET)
EQSig NISig casSig

x 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 description for further information.

Function Processor sparing With the introduction of Second Generation Function Processors (for example, PM2 based FPs), it is very important that you use only like-generation FPs to spare active FPs. A First Generation FP should be spared by another First Generation FP, a Standard Second Generation FP should be spared by another Standard Second Generation FP, and a Premium Second Generation FP should be spared by another Premium Second Generation FP. Agent queue size In order to engineer the number accounting agent queue size, the amount of memory available on the FP is enough to hold two accounting records for every connection, up to the number of connections supported on the FP. For example, if a DS1C PM2 premium FP supports up to 5000 Frame Relay connections, then the agent queue size can be set to 5000 * 2 = 10000 without risk of memory exhaustion. For a DS1C PM1 FP, the maximum supported number of connections is 1000, and the maximum recommended accounting agent queue size is 2000. Increasing the size of the accounting agent queue beyond two times the supported number of connections may cause memory exhaustion on the FP. For more information on engineering call management, see 241-6401-600 Passport 6400 Operations and Maintenance Fundamentals. PORS Mux mode directly connected to a first generation ATM FP When a PORS trunk running Mux mode connections on a new ATM IP FP is directly connected to a first generation ATM FP that does not have the minimum required software level active, then on average three out of every four PORS connections that are setup are software forwarded. If running either AAL5 Mux mode or SPO Mux mode in these scenarios, the remote node should either be
Release Notes for R7.0.11

76 Chapter 5 Release Planning

upgraded to the appropriate level of software (as indicated below) or additional processor overhead for these connections should be factored into the engineering of the ATM IP FP. Release 5.1: BE01S4F (SSUP 5.1.4) Release 7.0: All loads. PORS Map mode on ATM IP FP Any node in the network that is performing frame-to-cell conversion for connections that traverse PORS trunk running Map mode on a new ATM IP FP also require a minimum software level to be active. Otherwise, on average, only three out of every four PORS connections that originated from these nodes are setup to be software forwarded. If running either AAL5 or SPO Map mode in these scenarios, the network nodes should either be upgraded to the appropriate level of software or additional processor overhead for these connections should be 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 networks for PORS to fully enable H/W forwarding on ATM IP FP based cards (6K/7K/ 15K): Release 5.1: BE01S4F (SSUP 5.1.4) Release 7.0: BG00SBB (R7.0.11) ATM IP FP - first generation ATM FP Interwork Three new attributes have been added to the ca: maxAutoSelectedVpi, maxAutoSelectedVciForVpiZero and maxAutoSelectedVciForNonZeroVpi. These attributes limit the maximum value that msb will autoSelect when establishing switched connections. This is required to allow ATM IP FP cards to sucessfully interwork with first generation ATM FP cards. The following conditions apply to these attributes (and are enforced by 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

Release Notes for R7.0.11

Chapter 5 Release Planning 77

means they apply to both first generation ATM FP and ATM IP FP cards. On a ATM IP FP card the programmable vcc space is only limited to 65535 (that is, max 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 connmap. So the maxAutoselected values must be less than their equivalent connmap settings. PORS Degrade Alarm If PORS trunks stage when there are a large number of features in the feature list, PORS services may use normal memory rather than high speed memory. When this happens, a MSG alarm (7018 0003) is issued. The remedial action is to reduce the value of maxLc for each Path Administrator on the card. For more information, refer to 241-6401-435 Passport 6400 Path-Oriented Routing System Guide. Frame Relay engineering With the increase in feature content and service combinations on Passport switches, the maximum DLCI limits per Function Processor have changed. Refer to Frame Relay and Performance documentation for information about engineering the network. FR MMTC traffic may starve lower Emission Queue traffic if too much MMTC traffic is sent. This causes the FrUni Lmi to go down since control traffic goes through Emission Queue 2. In some networks, you may be able to implement Frame Relay configurations that exceed the documented Nortel Networks deployment recommendations. Before doing so, consider the risks of not being able to operate the same configurations under future software releases. For more information, contact your Nortel Networks Networks representative. Frame Relay Trace engineering The following recommendations apply to Frame Relay Trace: One trace session per FP is recommended if the traced port has a frame throughput greater than 500 frames per second. You can trace all ports of an FP simultaneously if the frame throughput of each port does not exceed 100 frames per second. Traced frames should be truncated and filtered by DLCI, if possible, to reduce the load on the network to transport the traced frames to the receiver. Always truncate frames larger than 256 bytes. Do not trace an FP which is running at a CPU utilization greater than 75% if the port to be traced has a throughput greater than 500 frames per second.
Release Notes for R7.0.11

78 Chapter 5 Release Planning

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

IpiVc and IpiFr coexistence engineering The total number of connections should not exceed 24 (the existing engineering number) during migration. Use of standby CP during software migration In order to reduce the service outage during a software upgrade, the standby CP is 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 can not be commited because the version of software that saved the data originally is not the same version of software that will be running once the migration is complete. You must issue copy prov and check prov commands before commiting the provisioning data. Spooled files The maximumNumberOfFiles attribute of the Spooler component now allows the 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 run the risk of losing spooled information. Leave enough spare in the maximum number of files allowed to allow your off-switch entity to retrieve the files from the switch. If you use the unlimited setting you run the risk of filling the disk with spooled files, at which point all spooling stops and the disks lose synchronization. When using the unlimited setting, ensure that the offswitch entity retrieving the files is able to keep up with the file generation rate of the switch. If you were using the unlimited setting, then there will be a large number of files on disk. Changing the attribute to a non-unlimited setting (for example, 1-200) will cause the switch to erase all files from the disk that are in excess of the new maximum. The oldest files are removed first.

Release Notes for R7.0.11

Chapter 5 Release Planning 79

Base Considerations
Unsupported card types The card types listed in Application and service combinations supported by ATM PDC 1.0 and PDC 1.1 function processors appear when you issue the Passport command:
> help shelf card cardtype

Cards defined for future use are not supported. Cards listed as obsolete are retained in the CAS help function for reference by customers who still use these card types (athough you can no longer order the cards).
Table 12 Unsupported Card Types
Card Type DEV1 DEV2 CFP2 4pEthAui Notes Future use Future use Future use Obsolete

Hitless CP switchover The behavior of APPN services (SNA), LAN services (IP, IPX, Bridging), LAN media (Ethernet, Token Ring, FDDI), VNS, WAN services (Frame Relay DTE, X25 DTE, PPP) and ATM FPs supporting ATM MPE are unchanged by this feature. These services and configurations do not support Hitless CP Switchover. When you issue a switchover Lp/0 command, the command fails if the current or edit view differs from the committed view. You can use the -force option to force the CP switchover, but then you lose all unsaved provisioning data in the current or edit view. Also, to run the committed view, the FP running uncommitted provisioning data goes down. Passport starts a 10 minute timer after the Hitless CP switchover recovery is complete. If the newly active CP fails within that 10 minutes, Passport initiates a full shelf reset. This mechanism protects against faulty CPs that would continually request CP switchovers. At this time, the timer also handles manual switchovers triggered using one of the following commands:
reset lp/0 restart lp/0 reset sh ca/<active_cp> restart sh ca/<active_cp>

Release Notes for R7.0.11

80 Chapter 5 Release Planning

The use of any of these commands while the timer is active results in a full shelf reset. Switchover triggered with the command switchover lp/0 while the timer is active results in a Hitless CP Switchover and is subject to the limitations and conditions described in 241-6401-600 Passport Operations and Maintenance Description. CAS congestion When responding to a command requiring a large number of responses, CAS may appear to be temporarily unavailable to other requests. While you may not see an immediate response to CAS commands, CAS still receives the commands and responds in due time. If you continue to input the same command repeatedly, you are adding to the load on CAS. CP crash caused by LCM,GCM and RemoteCallAgent using all msg block When there is a protocol port going down and that protocol port is provisioned with transparent bridge protocol (TB), there is a chance that CP's message system will be congested when the CP tries to flush out all cache entries that learn from that port to all FPs. For example, if there are 600 cache entries learned from port A, and if port A goes down, 50 messages (say 600 cache entries packed into 50 messages) are sent to each FP. If there are 14 FPs configured (50*14) 700 messages are sent in a very short period of time. In some cases, if there are enough cache entries, the congestion can be very heavy and the CP will crash. Manual Loopback Test on E1C If the external loopback is applied to an E1C port after the manual loopback test has started, incoming frames to the port under test may not be acknowledged. If the external loopback is established before the manual loopback is started, the test will run properly. V.54/PN127 Loopbacks on DS1C/E1C Only one V.54 or PN127 Remote Loopback test per DS1 (V.54 only) or E1 port is permitted. This means a total of four concurrent tests are permitted per DS1C or E1C card. Processor memory fragmentation issues As software features are deleted and added through provisioning and activation cycles, the processor memory may become fragmented. Fragmentation means that large blocks of contiguous memory are no longer available to load new software modules. Once a certain level of fragmentation has occurred, it may not be possible to load new software, and in the worst case processor card resets may occur. It may be necessary to reset the Function Processor or examine the load order of features to ensure the optimal use of Function Processor Memory. Consult your Nortel Networks Networks Technical Support representative for further information and assistance.

Release Notes for R7.0.11

Chapter 5 Release Planning 81

Bus Clock Source status By default, the provisionable attribute Shelf Test automaticBusClockTest is disabled. To check the current setting of the attribute, issue the following command:
display -p shelf test automaticBusClockTest

It is more likely that the value for clockSourceStatus, under the Shelf Bus/X (or Y) component, is set to unknown after a relevant condition changes (for example, an LP state goes down). When the Passport Shelf is in dual bus mode, you can start a bus clock source test manually by issuing the following command:
run shelf test

After the test has been completed, observe the results by issuing the following command:
display shelf test

Observe the statuses of the Active CP and the Alternate Bus Clock Source by issuing the following command:
display sh bus/x (bus/y)

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

Trunks, DPN gateways and networking


Management Data Provider support Management Data Provider Release 13.4 (or higher) with Solaris is required to support Passport Networks running this 7.0 release. Loadsharing engineering considerations Before you deploy the Loadsharing feature, review and consider the Nortel Networks Networks Passport Loadsharing Engineering Guidelines document. You can obtain these guidelines from your Nortel Networks Networks Field Service representative. Loadsharing fast is a new algorithm on ATM IP PORS LRC checking updated LRC checking has been set to on for all message types. LRC is set when messages are sent and checked when messages are received. This update assists in detecting errors. Full trunk statistics The addition of a new spooled record for each Trunk AtmAccess component has the impact of adding extra records to the DCS spooling queues. You may need to increase the DCS agentQueueSize.
Release Notes for R7.0.11

82 Chapter 5 Release Planning

Note: DCS also has important changes in regards to spooling in P5.1. The agentQueueSize for spooled statistics should follow the P5.1 engineering guidelines. The old statistics being kept in the operational view do not exactly match previous statistics. Specifically, the DPRS statistic is always counted in its appropriate emission priority because of the multimedia bit being introduced in the Passport DPRS Multimedia RCDS feature. This is opposed to having the dispatcher using the higher interrupting queues to determine interrupting statistics. Some of the older attributes are now being replaced by newer attributes. Note that customers will be allowed time to update any operation procedures (manual or automated) in order to use the new attributes, before the old ones are removed. ATM port statistics As part of the ATM Spooled Port Statistics feature, two new operational attributes are added to the AtmIf component. txLinkUtilization and rxLinkUtilization display the average AtmIf link utilization during the most recent minute, expressed as a percentage. MCS considerations A customer wishing to use DPRS MCS may perform the following procedure during migration to avoid a possible disruption of service at a later time. This applies to the provisioning of the dprsMcsEp and dprsMcsAgent features on PM1 FPs. In order for the DPRS MCS Agent and DPRS MCS EP LPs to get the fast memory they require, they must be provisioned first on the feature list of their respective SW LPTs. To ensure they get the fast memory they require, you must bring up the FP with these features during initial loading. If you provision these features on their respective FPs through incremental loading, there is no guarantee that they will acquire the fast memory they require and performance may be degraded until the FP is reset. To prevent this type of service disruption, you may wish to perform the following steps during the software upgrade: 1 2 3 4 Determine on which LPs the DPRS MCS Agent feature is required. Provision the DPRS MCS Agent feature as the first feature on the feature list of the SW LPTs of the identified LPs. Determine on which LPs the DPRS MCS EP feature is required. If you are going to provision both features on the same LP, provision the DPRS MCS Agent feature as the first feature and the DPRS MCS EP feature as the second feature for the feature list of SWLPTs for the identified LPs. Proceed with the software upgrade.

Release Notes for R7.0.11

Chapter 5 Release Planning 83

You can skip this procedure if an adequate maintenance window exists in which the LP can be provisioned and reset without service disruption. Note: There is no guarantee, regardless of the provisioned order of the feature list, that the DPRS MCS agent and the DPRS MCS EP will acquire the fast memory they require if the porsTrunks feature is also provisioned on the PM1 FP. The MCS manager should reside on a processor card where adequate resources (memory/CPU) exist and where it does not introduce a new single point of failure. Following, in order of preference, are the processor choices: 1 2 3 4 transport (trunk) FP, especially if all of the MCS connections go through that FP access (Frame Relay) FP, especially if all MCS connections terminate on that FP other FP
Note: This introduces a new single point of failure.

CP2, note that CP1 is not supported. On dual CP nodes, the active CP will reset, and the MCS manager will be out of commission until the standby CP takes over. single CP node or CFP1 node. Note: There are the limitations on MCS combinations by card type. See Performance NTPs for more information.

Frame Relay
Frame Relay migration When migrating a set of FRF.5 nodes from 4.2 to 7.0 (or a later release), ensure that 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 node running release 7.0 and another node running a software version of 4.2.6 or earlier. Refer to Use of standby CP during software migration (page 78). Also refer to NTP 241-6401-900 Passport 6400 Frame Relay UNI Guide. FRF.5 2K Scalability The MCSMgr can support up to 128 endpoints with 2000 DLCIs when provisioned on a PM2 Premium or Standard card. However, the MCSMgr can only support 32 endpoints with 2000 DLCIs when provisioned (as candidate lp) on an ATM card. Rapid Start/Stop of DLCI loopback causes card reset An FP containing a DLCI will eventually restart if you apply the following continuous pattern of data loopback commands on a PVC while the PVC is running traffic:
Release Notes for R7.0.11

84 Chapter 5 Release Planning

<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 issued in this pattern is less than four seconds apart. Frame Relay Trace When you use this capability with the Nexustrace software (developed by Nexus Telecom AG), you may experience lock-ups of the trace session under congestion in a Unix SUN OS environment. When this occurs, restart the trace session. If you use the Nexustrace tool to capture and analyze the information from the Passport Frame Relay trace capability, it is recommended that you use Nexustrace version 3.2 or higher. Contact Nexus directly for further details. FR-ATM Gateway with Virtual Framer and LP sparing The components of a FR-ATM Gateway (either a FrUni or a FrNni, and a FrAtm) can be provisioned on separate LPs logically linked by a virtual framer. When one or both of the LPs are configured for LP Sparing, failure of the primary LP results in an outage of the frame relay service significantly longer than if the gateway had been co-located on the same card. FR-ATM now requires atmNetworking to be in Sw Avl avList The atmNetworking application is required for existing users of Fratm services. This is now the case because the FrAtm package now has a dependency on the atmNetworking feature. No change in the Sw Lpt/x featureList is required but the atmNetworking application must be present in the Sw Avl avList. If the feature is not present, the semantic check required by the migration process fails and notifies you about the actions necessary to rectify the situation. No impact on service results from this migration issue but the migration process may be delayed while the feature is added. FRF.5 and ATM traffic management The establishment of an FRF.5 ATM SPVC is subject to the same rules and limitations as one originating from an AtmIf Vcc Src component. In particular, if the SPVC is to route through a Passport ATM interface on which Usage Parameter Control (UPC) is enabled, the derived ATM traffic parameters must respect the hardware limitations described in 241-6401-700 Passport 6400 ATM Overview, chapter 2, under section UPC provisioning restrictions. These considerations apply to Frame Relay connections using traffic policies 3, 4 and 5 only. Data Loopback with Resiliency A bit condition There is an A-bit condition that occurs when data loopback is used with PVC resiliency (backup). While data loopback is active on the PVC primary slave, the PVC is redirected to the backup slave (perhaps due to some link failure), and then
Release Notes for R7.0.11

Chapter 5 Release Planning 85

redirected back to the primary slave when the failure is resolved. This is proper functionality. However, at this point, the DLCI on the master end indicates that the 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-established to the primary slave. Once the PVC is re-established on the primary slave, you can start loopback again. If the PVC is already re-established to the primary slave, and the A-bit condition is active, you can remove this condition by issuing a lock then unlock on the DLCI of the primary slave. Frame Relay over EuroISDN
Non-Zero Codeset Use

Passports Frame Relay over ISDN feature supports only codeset 0 information elements (IE). Incoming ISDN calls to Passport containing non-zero codeset IEs in the SETUP message are released if they are encoded as comprehension required.

ILS
IP CoS The Passport IP CoS feature provides the following: support for Layer 2 based ingress packet classification. VC based for Frame Relay DTE, VC-based ingress packet classification on ATM MPE, and port based for all other media capable of bearing IP packets on Passport. support on LAN and non-ATM WAN media for ToS based ingress packet classification (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 packet classification (where CoS is determined by IP Address, protocol, and L4 port information). CoS to egress QoS mapping on Frame Relay DTE using multiple DLCIs and using a single DLCI. CoS to egress QoS mapping on ATM MPE using multiple VCCs (max. 4) and a single VCC.

Limitations Unsupported 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 (and 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 without the ILS Forwarder card) is not supported.

Release Notes for R7.0.11

86 Chapter 5 Release Planning

Note: You can assign groups of policies either to a Virtual Routers Protocol Port (Vr Pp) or to a Virtual Routers IP component. Policy groups assigned to a Vr Ip are applied to all protocol ports under that virtual router that dont have policy groups assigned directly to them. If a policy group is assigned directly to a Vr Pp then the policies in that group completely replace any policiey groups assigned to the Vr Ip. For more details, please see NTP 241-6401-815 Passport IP Routing User Guide

ATM
This section provides information about ATM. This section contains the following 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 92) 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 cards (page 94)

IMA migration For information regarding the migration from the Proprietary Protocol to the ATM Forum Protocol, use the IMA migration procedure provided in NTP 241-6401-730 Passport 6400 Inverse Multiplexing for ATM Guide. IMA-specific enhancements Any new IMA-specific enhancements are expected to be implemented only for the ATM Forum protocol. The proprietary protocol is intended to be used solely for backwards compatibility with previous implementations of IMA on Passport, and will eventually be phased out.

Release Notes for R7.0.11

Chapter 5 Release Planning 87

ATM processor operation If the ingress side is over-engineered with frame traffic (that is, too much link bandwidth allocated to trunk applications), the Passport ATM card will experience receive queue congestion and traffic will be discarded. If trunks with different ATM Service categories (for example, rtVBR and nrtVBR) are used on the same ATM interface and there are a large amount of frames on the rtVBR trunk, the ATM FP could spend 100% of the time servicing the higher priority queues (for example, rtVBR) causing the low priority queues (for example, nrtVBR) to build up and discard. These lower priority trunks will go down if the high priority trunks sustain this CPU usage. These considerations apply equally when the higher priority traffic originates from ATM Bearer Service or PORS services. You must use proper engineering guidelines to avoid ingress frame queue starvation. Maximum ATM connections Enhancements to Passport software and the introduction of Function Processors with larger memories have increased the total number of ATM connection points supported by each Function Processor. For details on the number of connection points of a given type supported on a Function Processor, see NTP 241-6401-100 Passport Performance Specifications Reference Guide. Maximum number of ATM test and loop components The ATM connection verification capabilities provided by the Test and Loop components are intended for use in validating the correct operation of new ATM interfaces and connections. Since these capabilities are usually required infrequently, these components have not been optimized with respect to memory utilization. As a result, provisioning large numbers of Test or Loop components on an ATM FP could lead to memory exhaustion problems. These problems can be avoided by adhering to the following recommendations. Do not configure more than 30 Loop components on an ATM FP. An alternative, which uses a Nrp component linked to itself, has no such restriction. The number of Test components running on an ATM FP should not exceed three.

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

Release Notes for R7.0.11

88 Chapter 5 Release Planning

mode transmitter and the multi mode receiver if this type of connection must be made. The following rules must be observed when interconnecting single mode and multi mode OC-3 ATM FPs: The fiber that is connected to the single mode transmitter must be single mode up to the attenuator. The fiber between the attenuator and the multi mode receiver may be either single mode or multi mode. The fiber that is connected between the multi mode transmitter and the single mode receiver must be multi mode. The multi mode transmitter will not couple 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 fiber circuit requires the use of a multi-mode to single-mode converter device. ATM Trunk Utilization Alarm For the ATM Trk Util Alarm, the utilization calculation is only provided for the AAL5 VCC. It does not account for the traffic received by VCCs that is managed directly by Trk PA. Be aware that the traffic on the companion VCCs in SPO Mux mode and Map mode trunks is not considered by the utilization alarm. Set the alarm thresholds v according to the amount of DPRS, VNS, and PORS AAL5 Mux 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 known as NMS) will mark the trunk as being Out Of Service. The trunk itself will still be up but nearing saturation if the threshold is set correctly. If this may be an issue for you, disable the critical alarm by setting the threshold to 200%. 8 port DS1/E1 ATM card independent and IMA links Independent links and IMA link groups may be used simultaneously on the same FP provided they have unique instance numbers. When traffic shaping and perVc queueing is disabled on the 8-Port DS1/E1 ATM FPs, up to 8 independent links or IMA groups are supported. However, when traffic shaping or per-Vc queueing is enabled for any number of ports on the FP via the perVcQueueInterfaces attribute of the Arc component, only 4 independent links or IMA groups are supported regardless of whether or not traffic shaping is enabled or per-Vc queueing is used on the associated AtmIf components. In the latter case only independent link instances 0-3 or IMA instances 0-3 are supported. To take best advantage of the full service suite now available on the 8 port ATM FP, 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 connections can be supported.

Release Notes for R7.0.11

Chapter 5 Release Planning 89

Those DS1/E1 port tests which generate test patterns (card, manual, remoteLoop) are permitted only when the port is bound to an AtmIf component. Thus, these port test types are supported only on independent links. This restriction does not apply to the other test types (externalLoop, payloadLoop) which may be used even 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 cards was provisioned through the connectionPoolCapacity for port 0. The Arc component attribute totalConnectionPoolCapacity (values 0.10752, default 3072) supersedes the use of the connectionPoolCapacity attribute. The Arc will be modified automatically during the migration process, if the Arc exists. Also, the default Arc supports the use of totalConnectionPoolCapacity. The connectionPoolCapacity attribute must now be set to 0 for these cards.The connectionPoolCapacity attribute may still be used for cards other than 8-Port DS1/E1 ATM FPs if the desired distribution of connections across ports cannot be achieved using the totalConnectionPoolCapacity attribute. This totalConnectionPoolCapacity indicates the maximum number of connections (both VCC and VPC) that are available across all independent links and IMA groups on the logical processor. Increasing the value of totalConnectionPoolCapacity decreases the number of frame and cell buffers available on the FP. When using the new totalConnectionPoolCapacity attribute of the Arc component, port 0 and port 1 of three port cards are limited to 2560 connections. The 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 perVc queueing on the logical processor. For more information on which instances of independent links or Ima groups support shaping or per-Vc queueing based on the value of the perVcQueueInterfaces attribute, see NTP 241-6401-700 Passport 6400 ATM Overview. The default for the perVcQueueInterfaces attribute is 0 which means that no independent port or IMA group supports shaping or per-Vc queueing. When no Arc component exists the system uses the default value. Port instances or IMA instances are used to determine which interface supports traffic shaping and per-Vc queueing. Based on the value of the perVcQueueInterfaces attribute the port instances that support traffic shaping and per-Vc queueing are (0), (0,1), (0,1,2,3). Port Sparing of 4 ports or less on 8-port DS1/E1 IMA cards Sparing/Fanout of 4 ports or less is supported using a single termination panel. In this case the provisioned ports should be in the range of 0-3 (or 4-7) and ports outside this range should not be provisioned without a corresponding sparing

Release Notes for R7.0.11

90 Chapter 5 Release Planning

panel connected. Failure to connect a sparing panel when a port has been provisioned causes the FP to poll looking for it and causes a click in the panel serving the other bank of ports. ATM Resource Control (ARC) migration The following are the actions taken for Arc components that already exist. Migration of connectionPoolCapacity attribute: The connectionPoolCapacity attribute is kept as is and the totalConnectionPoolCapacity is set to 0. For 8 Port DS1/E1 ATM Card, the value of connectionPoolCapacity for port 0 is migrated to the totalConnectionPoolCapacity attribute. The connectionPoolCapacity is set to 0. The shapingStackAllocation attribute is migrated to the perVcQueueInterfaces attribute. Note that this migration preserves the system capabilities.

The following are situations where you must add an Arc to ensure backward compatibility: If there is no Arc component and shaping is in use by an AtmIf component bound to port 0 of the Lp: an Arc component will be created with the perVcQueueInterfaces attribute set to 1 (all other attributes are set to their default values). the unshapedTransmitQueueing attribute of the AtmIf is set to common. If there is no Arc component, the Lp is a 3 port card type and the Connmap Space for any atmIf linked to a port of this Lp is between 1025 and 1536: an Arc component will be created with the totalConnectionPoolCapacity attribute is set to 4608 (all other attributes are set to their default values). Otherwise, the Arc is not created and no independent link or Ima group will support shaping or per-Vc queueing on the logical processor. This can be considered to be a degradation of the system capabilities as port 0 did support shaping or per-Vc queueing by default before the migration. To preserve port 0 ability to support shaping or per-Vc over migration, you should explicitly add an Arc component before the migration and set perVcQueueInterfaces to 1. ARU reporting section The default values for the tx and rx frame memory allocation of 50% and 80% respectively, are now measured in cells. This corresponds to partitioning of 44% and 76% respectively in bytes. The minimum amount of buffer space reserved for cells and frames is the same. However, as both quantities are reported in cells the value for the minimum frame buffer memory appears larger.

Release Notes for R7.0.11

Chapter 5 Release Planning 91

Changes to the Atmif transmit queue limit defaults The effective default values of the transmit queue limits remain unchanged from previous Passport releases. The value reported in the operational view has been changed 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 attribute (txQueueLimit), under a particular ATM interface, indicates that the default for the card type will be used. For more information, see NTP 241-6401-700 Passport 6400 ATM Overview for details on the default values for the transmit queue limits. Queue Limit Software Errors in 7.0 against OC3MM-CQC The following SWERR (software error) occured when running the Qlimit Traffic Management test suite against 0C3MM-CQC FP's in the BG00S4C and BG00S5A software loads. This has also been seen against other CQC FP's.... 8pE1Atm, 8pDS1Atm, 3pDS3Atm, 3pE3Atm. Some connections may experience 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__20AtmNailedupConnPointRC20AtmTrafficP rovStruct _software__FPCcT0iT0RUi Int: 3/1/2/7205; atmNailedupConnPoint.cc; 318; p7.0d.35

3pDS/E1A to 8pDS/E1A card migration If you provision a three port DS1 or E1 ATM card with an Arc that has values in the connectionPoolCapacity vectors, perform the following steps during the 3pDS/E1A to 8pDS/E1A migration process: 1 2 3 Enter provisioning mode. Change the card type under Shelf Card/x set Shelf Card/x cardtype 8pDS1Atm If the Lp/x Arc is present: Set the totalConnectionPoolCapacity to three times the highest connectionPoolCapacity value. This will ensure that semantic checks will pass. set Lp/x Arc totalConnectionPoolCapacity <value> Set all the connectionPoolCapacity vectors to zero.

Release Notes for R7.0.11

92 Chapter 5 Release Planning

set Lp/x Arc connectionPoolCapacity 0 0 1 0 2 0 4 Check and activate the provisioning. For more information, see NTP 241-6401-700 Passport 6400 ATM Overview. 3pE1A to 8pE1A Linetype migration The 3-port E1 ATM FP (3pE1A) supports a lineType of either cas or ccs, with cas being the default. Since the 3pE1A uses a non-ATM specific framer chip it can support signalling multiframe framing, and therefore can use lineType cas. The 8-port E1 ATM FP (8pE1A) supports only a lineType of ccs, since it uses an ATM-specific framer chip that does not allow access to the timeslot 16 bits. As the usefulness of signalling multiframing is questionable on unchannelized interfaces, this is not normally a problem. Connecting an E1 with lineType cas to an E1 with lineType ccs results in Signalling MultiFrame Loss Of Frame (SMFLOF) alarms on the cas E1, since the ccs E1 is not transmitting the signalling multiframe alignment bit in timeslot 16. E1 channel associated signalling (cas) involves the use of 4-bit signals (ABCD bits) transmitted in timeslot 16 of the interface, with one set of ABCD bits per timeslot. Also contained in timeslot 16 is the signalling multiframe alignment bit and the Signalling MultiFrame Remote Alarm Indication (SMFRAI) bit, which is set to 1 on transmit when a SMFLOF is detected. E1 common channel signalling (ccs) involves the transmission of layer 2/3 messages in timeslot 16, for instance by an ISDN protocol stack which uses timeslot 16 as its D-channel. These messages refer to the channels (timeslots) carried by the interface. Since both cas and ccs signalling types are only applicable to channelized interfaces (for example, those whose total payload bandwidth is divided up into timeslots), and ATM interfaces are not channelized, cas and ccs signalling do not apply to ATM interfaces. Passport E1 components have an attribute lineType, which may be either cas or ccs. In the case of unchannelized interfaces, the effect of this choice is really to enable signalling multiframe framing in timeslot 16 (cas) or to ignore timeslot 16 completely (ccs). When migrating an FP from a 3pE1A to an 8pE1A, if the 3pE1As ports were provisioned with lineType cas, then their lineType will need to be reprovisioned to ccs on the 8pE1A as well as on the interface at the remote end. ATM Function Processor crashes after CPSO and LP switchover Customers may observe that an ATM Function Processor crashes after a CP switchover if a LP switchover is performed soon after the CPSO. The card will, however, return to full service after the CP switchover. Therefore, it is not advisable to do a LP switchover immediately following a CPSO, especially if there is traffic arriving at the LP.

Release Notes for R7.0.11

Chapter 5 Release Planning 93

At the time of a switchover or card reset, there is a brief time window where the actual interrupt handlers for CQC interrupts are not yet bound in. If traffic arrives at this time, a defaultHandler gets invoked. Since the default handler doesnt handle specific interrupts it is possible to get a watch dog timeout due to interrupts that remain continuously asserted. Once the actual handler gets bound in, the offending interrupt is handled properly. Changes have been introduced into the defaultHandler to minimize the probability of a time out but since it is not the intent of this handler to handle specific interrupts no further changes are intended for the defaultHandler routine. Virtual Path Termination (VPT) Phase 1 The considerations for the deployment of VPT Phase 1 are listed below.
Reserved Vci values

When a VPT is provisioned on a given VPI, VCI values 3 and 4 within that VPI can not be used. For example, if Vpc/3 is provisioned as a VPT, this means that Vcc/3.3 and Vcc/3.4 must not be provisioned. In Phase 1 of VPT, there are no safeguards in place to prevent those Vccs from being provisioned. However, if these Vccs are used, the ATM FP will eventually crash.
Minimum value required for ConnMap numVccsPerNonZeroVpi

Before you can successfully create and use a VPT VPC, the ConnMap attribute numVccsPerNonZeroVpi must have a value of 8 or greater. There are currently no safeguards in place to prevent you from using a value less than this minimum.
No elastic connections permitted

At this time, VPT does not fully support bandwidth elastic connections. Therefore, they should not be provisioned in conjunction with a VPT. For example, if there is VPT provisioned with VPI=3, all Vccs in the VPI=3 range must be provisioned as bandwidth non-elastic connections. ATM SPVC accounting You can provision an ATM SPVC (Soft Permanent Virtual Circuit) to generate accounting records in two different ways. The first method involves enabling UNI/IISP accounting at the ATM interface used by the SPVC. The second method involves enabling PVC accounting at the ATM interface, then provisioning a correlation tag for the SPVC. If you use both methods simultaneously, the SPVC generates two distinct sets of accounting records. To prevent this duplication of accounting information, provision a correlation tag for a SPVC only if UNI/IISP accounting is not enabled on the ATM interface. ATM Cell Transfer display Currently, Cell Transfer display is supported only on SPVP and SPVC connections with segment switch-side loopbacks provisioned.

Release Notes for R7.0.11

94 Chapter 5 Release Planning

Provisioning of subConnectionPool and lnnConnectionPool on ATM cards The number of sub-connections and logical network number (LNN) resources may now be changed on the ATM card (subConnectionPoolCapacity and InnConnectionPoolCapacity attributes under the LP ARC component). A sub-connection is used for interworking the ATM services with the frame oriented services such as Frame Relay, and Path Oriented Routing System (PORS). When a frame is received at a sub-connection, the frame header is modified to be compatible with service to which it is forwarded. Due to limited resources, not all of the provisioned number of sub-connections may be allocated. The actual number of sub-connections allocated is indicated in the sum of LP Aru subConnectionPoolAvailable and Lp Aru SubConnectionPoolUsage attributes. When the sub-connection pool is exhausted, no more connections are accepted from the services that use this pool. A logical network is a subset of passport modules together with a subset of trunks that interconnect those modules. It carries the traffic for a defined set of network protocols. A LNN is used to identify a logical network. The connectionless services which use the logical networks require some processing at the intermediate nodes. This pool is allocated at the intermediate nodes to sustain these connectionless services. Due to limited resources, not all of the provisioned number of LAN connection resource records may be allocated. The actual number of records allocated is indicated by the sum of Lp Aru ConnectionPoolAvailable and Lp Aru lnnConnectionPoolUsage attributes.

ATM Networking
Migration When migrating from R5.0 to R7.0, the AtmCr component will be migrated to the ARtg component. You must delete the AtmCr component once the node had been upgraded to R7.0. If the AtmCr and ARtg components are both provisioned, the check prov will give the following error message: AtmCr component is obsolete, please delete it. Passport ILMI not UNI 3.0/3.1 compliant It may take significant time to enable ILMI between a Passport and a nonMagellan switch after cable is disconnected and reconnected. The problem is caused by Passport ILMI 3.0/3.1 implementation which is not fully compliant with the UNI 3.0/UNI3.1 standard.

Release Notes for R7.0.11

Chapter 5 Release Planning 95

Passport ILMI 3.0/3.1 implementation does not support SNMP queries of ATM management information across the UNI as defined in Chapter 4 of the UNI 3.0/ 3.1 specification. Perform the following steps to increase the speed of the ILMI recovery: 1 2 3 Disable address registration on Passport. > Set atmif/x uni ilmi operatingMode addressRegDisabled Check and activate provisioning. At this point the ILMI comes up and a signalling VCC is created. Enable address registration on Passport. > Set atmif/x uni ilmi operatingMode addressRegEnabled 4 Check and activate Prov. Provisioning SPVCs Max CTD The provisionable range of the attribute maxCtd under the atmlf/Ca/Cbr and atmlf/Ca/rtVbr components is 0 to 2147483647. Provisioning 16777215 or higher means that a SPVC passing through this interface will incur a cell transfer delay equal to this value. The SPVC will fail because the maximum or do not care value in the fwdQosParameters under the VCD component of the SPVC is equal to 16777215. CLR The valid range for the CLR in the fwdQosParameters or bwdQosParameters under the VCD is 0 to 15 or 255 for the do not care value. In future releases, a semantic check will fail an invalid entry. Reserved channels Reserved channels for signalling on an ATM interface are given priority over PVCs, SPVCs, and SVCs when the system checks to see if Ca/maxVcc is reached. However, on FP resets, this priority is not maintained; the software admits PVCs and SPVCs first. This admits a maximum of maxVcc PVCs and SPVCs and fails to set up the reserved channel. SPVCs SPVCs do not support different values in the txPacketwiseDiscard and rxPacketwiseDiscard attributes under the Vcd component. You must set both attributes either to INDICATED or NOTINDICATED. The result is PPD is either ON or OFF in both directions. This limitation does not apply to PVCs and SVCs.

Release Notes for R7.0.11

96 Chapter 5 Release Planning

Changes in the IEs for the service categories for all SPVC interfaces Changes were made with the encoding of IEs for all the service categories for all SPVC interfaces. The encodings for P5.1 SPVCs are summarized in Serial interface combinations with WAN transport of LAN supported on CFP1 in NTP 241-6401-100 Passport Performance Specifications Reference Guide.
Table 13 P5.1 IE encodings for the service categories for all SPVC interfaces Service Category CBR VBR-rt VBR-nrt UBR Bearer Class X X X X Traffic Type CBR VBR VBR VBR Timing Required end-to-end end-to-end No No Yes Best Effort

ATM signalling channel failure on IMA A problem can exist when a signalling channel is created in the rtVBR bandwidth pool by using dynamic bandwidth control to create VCCs in the IMA feature. If there is bandwidth reduction and the signalling channel goes down, the signalling cannot come up because the elasticity of the connection will have claimed all of the available bandwidth. ATM accounting for N-PVCs Documentation for this feature is available in NTPs 241-6401-650 Passport 6400 Accounting Reference, 241-6401-700 Passport 6400 ATM Overview, and 241-6401-030 Passport 6400 Overview. Provisioning permanent VCC Provisioning a permanent VCC (with Nrp, Nep, Test, and Loop subcomponents) using the same VPI.VCI as a dynamic VCC with a Dst subcomponent causes a software error. The correct behavior is the permanent VCC clears the dynamic VCC and uses its VPI.VCI designation. Practice careful connection space usage to avoid provisioning permanent connections above the minAutoSelectedVciForVpiZero or minAutoSelectedVciForNonZeroVpi values under the AtmIf Ca component. Private Network to Network Interface (PNNI) PNNI is a complex standard and it is important that you understand it completely before modifying default values for the various timers that the protocol uses. Poorly chosen values can result in unexpected behavior that could impact network functionality. You should not modify timers without consulting Nortel Networks Data Network Engineering personnel. Currently PNNI does not support operation when the database is in overload state.

Release Notes for R7.0.11

Chapter 5 Release Planning 97 Random path sharing

When routing to a node, if there are multiple paths with the best optimization metric, then the PNNI routing algorithm randomly chooses one of them. This method of choosing the routing paths also provides a mechanism of load sharing on equal parallel links (see definitions below).
Definitions

1 2

Two links are considered parallel if they connect the same nodes. Two links are considered equal if they have the same value for the optimization metric.

Omitting links from the route computation process

If a link has the value for the optimization metric (that is, AW, CTD, CDV) equal to 0, then it is omitted from the route computation. For example, if the optimization metric is AW and a link has the administrative weight set to 0, then it is not considered in the route computation. ILS on ATMIP FP The Passport ILS on ATMIP FP feature provides: Improved performance (relative to ILS on CQC FP) for processing IP traffic. Elimination of the need to have an ILS Forward Card when processing IP traffic over the ILS on ATMIP FP. This allows the card slot occupied by the ILS Forwarder Card to be freed up. The architecture is more scalable; each ILS on ATMIP card does its own forwarding., rather than sharing the resources of an ILS Forwarder Card. In addition, bus utilization is reduced. Increased memory capacity of the ATMIP FP allows more feature combinations than do previous FPs.

Limitations The 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 used as an ingress module into VNS network. This problem is tracked by SR number 10375439. The data transferred from port 1 of the 100 BaseT card doesn't follow the VFF (very fast forwarding) hardware assisted data path, while port 0 can use it in the same test environment. The problem may be caused by some hardware differences between port 0 and port 1, which prohibits the data transferred from port 1 to become CAM eligible. As a result, the data from port 1 uses the software forwarding scheme and has a lower throughput compared with port 0.

Release Notes for R7.0.11

98 Chapter 5 Release Planning

AAL1 Circuit Emulation Service (CES)


Migration When migrating from to R7.0 with existing unstructured AAL1 service to ensure that 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 282 (a previous 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 active Changing the transmit queue limit (txQueueLimit) is a critical change that causes the ATM interface to be reset. As a result, enabled AAL1 CES calls on a particular interface are dropped if changes are made to the transmit queue limit while such AAL1 CES connections are active. This applies for any application running over an ATMIF exhibiting the txQueueLimit critical change. CES over PORS In a Passport network where the backbone nodes are running pre-P4.1 software and the nodes at the edges are running P4.2, the AAL1 CES cells will not be carried across the backbone over PORS because Dynamic NSAP addressing (a new P4.2 feature) does not exist in pre-P4.2 nodes. New bandwidth limits for 4p E1 and DS1 AAL1 cards Because there are limitations on the number of timeslots that can be used for structured services without exceeding the bandwidth of the card, a semantic check has been introduced in 5.1 (SR 10209545) to ensure that AAL1 FPs running structured services are not provisioned with more timeslots than they can handle. Some AAL1 configurations which have been up and running in some release levels of 4.2 and/or 5.0 may fail the first semantic check after upgrading to 5.1.

Release Notes for R7.0.11

Chapter 5 Release Planning 99

The new bandwidth limits which have been implemented for 4 port E1 and DS1 AAL1 cards are as follows. (There are no bandwidth limits when only unstructured services are present on a card). The Partial Fill level is taken into account for the bandwidth calculation such that the actual bandwidth for each service on a card is: ((provisioned ts * maximum partial fill level) + (provisioned partial fill level - 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 E1 and DS1 AAL1 cards are listed in the tables below. The bandwidth calculations for each service are rounded down to the nearest integer prior to being tallied together and displayed in the following tables:
Table 14 Bandwidth limitation for E1 Card Effective size of largest service on card 1-12 13-18 19-24 25-30 Table 15 Bandwidth limitation for DS1 Card Effective size of largest service on card 1-12 13-18 19-24

CAS 72 65 62 60

no CAS 106 98 94 92

CAS 88 77 72

no CAS 96 96 96

Voice
Voice Networking Gateways New Gateway Pairs - In Release 7.0, it is possible to place voice, modem and Facsimile calls between the following PP6400 CCS and CAS protocal pairs:
Table 16- PP6400 CCS and PP6400 CAS Pairs PP6400 CCS E1 ETSI QSig DS1 ETSI QSig E1 MCDN DS1 MCDN DS1 NIS PP 6400 CAS DS1CAS DS1CAS, E1 CAS DS1CAS, E1 CAS DS1CAS, E1 CAS DS1CAS, E1CAS

Release Notes for R7.0.11

100 Chapter 5 Release Planning Table 17- PP6400 CCS and PP4400 CAS Pairs PP 6400 CCS PP4400 CAS E1 ETSI QSig DS1 ETSI QSig E1 MCDN DS1 MCDN DS1 NIS DS1CAS, E1 CAS, Analog DS1CAS, E1 CAS, Analog DS1CAS, E1 CAS, Analog DS1CAS, E1 CAS, Analog DS1CAS, E1 CAS, Analog

These pairs are in addition to the existing E1 ETSI QSig to E1 CAS pair that is already available. Note that the Gateway feature does not yet support CCS to CCS protocol gateways. Data Calls - data calls between E1 and DS1 are not currently supported in any combination of protocols. MVPE G.729A Voice Encoding In Release 7.0, the G.729A voice encoding algorithm is supported on the E1Mvpe, DS1Mvpe and TTC2mMvpe FP's. It is twice as efficient as G.729 and interworks fully with G.729 on MVP and MVPE FP's on earlier releases of software MVPE V.17 Fax Relay at 14.4 and 12.0 kbit/s Without V.17 fax relay, there are two alternatives for handling a call between two fax 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 traffic through 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 or G.726 at 32 kbit/s

There are disadvantages to both of these alternatives. The first alternative does not allow the fax machines to transmit at their highest possible speed. The second alternative uses a lot of bandwidth through the Passport subnet. With the introduction of V.17 fax relay, a third alternative is available: allow the fax machines to transmit at their highest possible speed and encode the traffic through the Passport subnet using V.17 fax relay

This alternative is the best possible case. The fax machines are allowed to transmit at their highest possible speed, while bandwidth usage in the Passport subnet is kept as low as possible. V.17 fax relay is available for both Voice Transport and Voice Networking on MVPE FPs Provisioning Voice Networking - relay encoding minimum rate In Release 7.0 Voice Networking, ensure that you set the Vncs/n Vp/x modemFaxRates encoding relay rate min to 0. Otherwise, a warning will be issued explaining that the min relay rate is irrelevant.

Release Notes for R7.0.11

Chapter 5 Release Planning 101

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-tromboning MCDN feature Anti-tromboning will fail to activate between R7.0.11 and previous releases of 7.0 and 5.1. For the Anti-tromboning feature to work correctly it must terminate and orginate on the same voice route, signalling channel, voice subroute, switch voice service, and node id. If a call originates through a HgS there is no guarantee that the call will be terminating on the same node or same vroute.

Release Notes for R7.0.11

102 Chapter 5 Release Planning

Release Notes for R7.0.11

103

Appendix A Known Limitations


Table 18 contains a list of Change Requests (CR) which document problems found in this load or previous loads which are not yet resolved. These problems will be fixed in this load with patches, or in a subsequent load. Fixed CRs are moved to Appendix B Resolved Limitations since last release (page 104) in the release notes for the load in which the problem is fixed, and then moved to Appendix C Items Resolved in Previous Releases (page 110) for subsequent releases. The table is followed by details regarding the service request..
Table 18 Service requests Item CR ID CustRefNumber Platform Module Title

Note: There are no "known issues" for this release.

Release Notes for P7.0.11

104 Appendix B Resolved Limitations since last release

Appendix B Resolved Limitations since last release


The following table is a list of SRs that have been resolved since P7.0.10.
Table 19 Limitations resolved since last release # 1 2 3 4 5 6 7 8 9 10 11 12 CR ID Q00305898-01 Q00306108-10 Q00306147-06 Q00306222-07 Q00306266-15 Q00307432-05 Q00307625-04 Q00308034-02 Q00312799-01 Q00312979-01 Q00313012-04 Q00313061-12 020411-11221 020418-18235 020503-37153 020513-45956 020624-93155 020708-07723 020807-41362 020904-71853 030213-49908 010918-4905 010515-3865 CustRefNumber (ID Number) Title GVT/PP/MVPe: High BER during lp/x e1/0 test when using type card Attempting to autoselect the last available VPI hangs FP Crash: Cfra4 NMI has occurred at interrupt level memAudit tool is broken for PQC based cards False report of congestion condition on 4pOC3 FP PROP: Check prov fails after activation - VR duplicate vpi found .pd files are deleted from passport disk after sw dld PORS: Manual Path with Forced BW is broken (BTDS calls cannot stage) Prop: 4pMVPe:StdUipeCodec.cc and UipeDchanMaint.cc swerrs on loopback,add ch31 FUNC: txQosParameters:ctd value not displaying correct default value Software error in vnetUipeDchanMaint.cc; 1358, incomplete info NST: No more local msg blks LMB on 1pE1Mvp card

13 14 15 16 17 18 19

Q00314937 Q00315368 Q00315483 Q00315527 Q00315528 Q00315531 Q00315545 010822-3954 011126-57034 020916-85239 010918-4500 011025-24210

100BaseT: 100BaseT Ethernet card crahes when IfState changed VRRP alarms: memory overwrite, wrong NTP indexes, etc. PtoMP SVCs are not properly released on 2pOC3MmAtm2 card Crash.Reason:Module Data For Virtual Circuits not available (Pointer is NULL) 9000 Alarm: ifEntryFp.cc; 641; p7.0d.30 Unacked Trunk pa maxReservableBwOut Problem 011025-24210: 100BaseT card crash

Release Notes for P7.0.11

Appendix B Resolved Limitations since last release 105 Table 19 Limitations resolved since last release # 20 21 22 23 24 25 CR ID Q00315546 Q00315560 Q00315613 Q00315927-01 Q00315928-01 Q00319716 020214-45456 020305-66460 020523-58367 021009-13706 021024-31425 030220-57788 020404-02005 021111-51851 021112-53412 030211-46801 011127-58882 021008-12251 021030-39393 030205-40726 030213-49964 020222-54526 020314-78294 020724-25815 CustRefNumber (ID Number) 011004-13095 Title Crashes on FP cards running mpanl protocol PROP: Ipport Ingresspacket trace filtering enhancement LinkDestination Address of PPP connection is in RDB but not in FWD table TB Bridging: Bridge port remain in disable state after unloc ATMIP: Bridge traffic getting dropped after card reset Passport Allow 2 Vr to have management access when provision through MDM.

26

Q00336691

Traffic delay during CP switchover is better with CP1s than with CP2s

27

Q00365022-08

IMA link imbalance

28 29 30 31 32 33 34 35 36 37 38 39 40

Q00385377 Q00390178-01 Q00412517-04 Q00415413 Q00418956-06 Q00422483 Q00422811 Q00428330 Q00429612 Q00430209 Q00453541 Q00456071 Q00456684-08

Card reboot when HTDS plc "local address" changed. 1pMVpe Card crash when PBX card re-install

020607-75305

Prop: Anti-Tromboning fails on first attempt, then intermittently during traffic pp6k SWERR during Prov for OSPF Export ripInterface inwIpRtmOspfAreaTbl.cc UNI signalling remains disabled after VCC goes down and then up

020429-31476 020430-32200 020711-12562 020411-11115

Typo in .fdc file for load 7.x tProf top command causes card to Crash 1pDS1V NMI crash in BG0046A - UIPE_L3 (0x0253970) was near address 0xd003a804 MDM13.2: Customer has proxy alarms raised as a result of a clr alarm. pp6k, fruni ch pr passed, when side is network, pvcconfig is yes and dlci >300

020528-62907 020530-66629

100BT vrrp with instant 255, master doesn;t reply to ping request Q931 signalling compatibility issue Traffic loss between Atmif vcc and Fratm dlci

Release Notes for P7.0.11

106 Appendix B Resolved Limitations since last release Table 19 Limitations resolved since last release # 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 CR ID Q00461459 Q00464703-02 Q00472733 Q00474928 Q00475063 Q00477276 Q00482647 Q00483893 Q00491469-02 Q00491623 Q00492550 Q00493468 Q00496567 Q00500955 Q00501847-01 Q00502692-04 Q00503257-05 Q00503342 Q00513087 Q00514029-05 Q00514844 Q00515653-01 Q00519242 Q00520513 Q00520854 Q00524095-02 Q00524099 020506-37917 020909-77326 020904-72688 020807-41581 021105-45151 020327-93085 020717-18856 020726-29439 020717-18772 020729-30231 020712-13168 020709-09054 020620-90364 020610-77674 CustRefNumber (ID Number) 020604-70962 020306-68139 020624-93672 Title 7.0.9 ATMIP cards resetting with no traceback at CPSO Prop: No more message block on 1pE1Mvp card 7.0 ATMIP FP needs reset/re-seat after node reset/power-cycle pp6k, sddetoclpmapping in fratm siwf and niwf is not working properly in spvc Netsentry filter not working properly under tbp pp6k: fratm ca nddetoclpmapping value always1 is not working correctly. PP7K Passport is Switching Between CPs About Every Hour E1C card crashes with config as PP4400 ISDN backup 1pMVPE: DSP SW version not properly retrieved from permanent DSP signature RelayBC cause rxFrameMemoryUsage go up; frames are dropped after it reach thresh 7.0.10 Swerr during ch pr when LA not connected to LP Port. P7.0.10: MAC addresses switch following sw migration from P5.x ABC/Pp6k E1C PPP session up/down caused 2pATMIP card autoreset 09000 alarm raised when DPNGateway went down 020708-07084: CBOS12 Card/11 crash IP cache entry stuck in "pending" state on Fast Ethernet FP (100baseT) SBIC Addresses needing to be included for firmware fix (32 addresses total) Static route NH in FWD table is broadcast address of another protocol port Bandwidth allocation MPANL-MVP interworking CR to have IPD timer value of 1s to be submitted into mainstream OS Debug trace is always on, when IP policy group is configured for layer 2 4p GW: Vnet MCDN to Vnet NIS call protocol error Frames lost in network incrementing when using Cas on Rel 7.0.10 Adjust the solution for a previous submission in p7.0d.51 CTPE8 Lp/4 and Lp/9 crashing - MCS MGR PROP to 7.0.10B -- IE not forwarded transparently ATMIW: Software error at line 336 in file sbqGeneral.cc during interrupt 236

Release Notes for P7.0.11

Appendix B Resolved Limitations since last release 107 Table 19 Limitations resolved since last release # 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 CR ID Q00524572 Q00524780-01 Q00525136-01 Q00530480 Q00531351 Q00531560 Q00533669 Q00534794-02 Q00538464 Q00548254-05 Q00549882 Q00550060 Q00552139 Q00552257 Q00553114 Q00554724 Q00556943-02 Q00558853 Q00560635 Q00562609 Q00562792-02 Q00563486 Q00566642 Q00570243 021024-32028 021110-51761 030107-07333 021028-36485 011219-86005 021009-13706 021106-48059 021114-56762 021031-41404 021104-43759 021015-20317 021024-32129 021025-33816 020927-00219 021002-05173 020926-98716 CustRefNumber (ID Number) 020618-87470 020710-09987 Title SPVC active at 4460, but no SPVC at 6400 PROP: 00009000 Software Error - Invalid Data in CHID Software DLD Process does not allow patch download from PC based SDS. SWERR occurs after activate prov MPANL bug. Debug printf statement not removed from code. Attribute ""tableVersion"" under VR IP BGP is always 0 V35 ports osiUsage will become idle during port lock/unlock or when remote equip 100% CPU utilization on FP due to incorrect calculation of free CAM entries atmmpe ac inunknownprotos attribute incrementing permanently on shelf 021024-32129: crash in HE_check_segment_ie FUNC: Cannot telnet to ethernet port after re-activation 6400 does not implement a restart procedure for DLCI-0 Software error (9000 alarm) after deleting and adding a VR running bridging (TB) Ingress packet tracing for IP not working on ATM IP FPs for HW forwarded packets one static route missing from rdb after lock/unlock vr/x pp/x TR SNA DLR crashes with NMI (local bus error) Remote end Negotiation Cause Poor voice quality OSPF route(s) not in RDB on 7.0.10. SW Fault: BG00SAB when receiving RIP updates Proxy alarm on MDM after lock/unlock of E3 port. Clear not sent oper state disab DAT/GVT/PP: Fax collect calls are not being possible from LDA to MGA. VR: correct the behavior of the managemet VR PP6K: R7.0.9: 2pOC3Mm: Trunks do not restage after card reset with APS configure PP6K: V.35 port down disabled, linestate all up(rfs dsr dcd rts), remote port up

Release Notes for P7.0.11

108 Appendix B Resolved Limitations since last release Table 19 Limitations resolved since last release # 92 93 94 95 96 97 98 99 CR ID Q00570846 Q00570888 Q00571073 Q00571410 Q00571427 Q00575461 Q00575465 Q00584867-01 020327-93133 020927-99848 " CustRefNumber (ID Number) Title PP6K: CasPlaneResponseErrorInternal Swerr appears on CP switchover/reload FSM_BAD_MESSAGE after reloadcp PP6K: Q931Sig FramerIf -- Invalid msg sigChanLockedToFramer Swerr NSSA ABR advertising default route when not connected to backbone OSPF: NSSA: Type 7 to 5 conversion not taken over on ABR port failure. "Incorrect logic in method ""getIpPort"" for returning VRRP associated IP port VNS topology change causes TB bridging to reclaculate spanning tree (STP) 4P-E1MVPE FP does not detect and suppress the idle code. PP6400(7.0.9): Mpanl Framer record has a wrong value Implementing Debug commands used for Q00502184 PROP: Global Support Tool Release 2 (GST R2) 030104-04329 010406-6927 020204-31819 020307-69891 020613-81963 021126-71046 020809-44496 021216-91362 030116-17346 030212-48840 030305-73860 021121-65377 030119-20259 030119-20340 021003-07661 020909-77297 030213-49528 030301-69218 030212-48374 030220-58068 Vnet, Euro-isdn, second call setup fails "requested channel not available" COT TEST 2010HZ TONE DETECTED AS 2100HZ TONE BY ECAN USING 3C37H 1 PORTCODE

100 Q00586645 101 Q00588203 102 Q00588391 103 Q00588759 104 Q00589516-01

105 Q00591698 106 Q00593467 107 Q00594268-06

PP6k v7.0.10B - incomplete Long Distance FAXs Memory exhaustion by SNA on TR FP does not cause card to crash MvpDspif::memoryDumpFrameHandler_v - Bad Access Protection Fault 0x200

108 Q00596340-04

MPANL crash on SBIC due to corrupted Free list

109 Q00600300 110 Q00611998 111 Q00612226-01 112 Q00614023 113 Q00617511

7.0.10B: memory leak due to removing entries in apply table PP:6K: Problem with Fax/Modem service after migration to R7.0.10 After modem/fax call is released, the passport remains in mofax mode and is send QSIG Status message is not processed properly by Passport netbios broadcast results in high normal memory, high smb, token ring fp reset

Release Notes for P7.0.11

Appendix B Resolved Limitations since last release 109 Table 19 Limitations resolved since last release # CR ID CustRefNumber (ID Number) Title Deleting VRRP instances causes CP crash 030227-65852 Passport 7000-ve3l card 7 restart 70120101 CRAN PCR 4.2

114 Q00619678-01 115 Q00621443-03

Release Notes for P7.0.11

110 Appendix C Items Resolved in Previous Releases

Appendix C Items Resolved in Previous Releases


Items Resolved in the P7.0 (BG00A) Release
The following Service Request list details the updates that were included in P7.0 (BG00A).
Table 20 Items resolved in P7.0 Title Fix for mid loss problem Eap Bcst, Rtg dpn cs/scr comp missing SNA DLR fixes for problems found during IT-Austria live test SNA DLR traffic stops towards BNN connection HotHaus 3c24 build Call Completion Ratio drops to 77% if SAD=ON on PVC CAS Bad PNNI RCC component status on NMS & pnni swerrs Ingress and Egress frame free list failures VRRP related, gating SRs Atmif link Utilization, txQueue threshold SRs CP crash at vrCbs on call to saveFtoUpdate 10baseT eth card continous reboot after upgrade to BE01SFA 10BaseT cards crashes on intialization with traffic V11 (PM2) crash after reset: Free block list is exhausted Chan Restart Fails R7.0 Packaging Problem: Voice TDS APPN deletion of DLCI causing FP failure DS1 CAS VSR SVS useage causing SWERR under traffic load SWERR caused by tpt under traffic load. Change required in DCS Collector registration to support SNMP MVR IpRtm provisioning memory leak SWERR: AtmMpe semantic check for unrelated Lp provisioned Hardware Forwarding Fails During Route Flaps BGP external route wont export to ospf PVG: No TEST component under Shelf Card for the 32E1AAL card Ethernet Dynamic ARP entries cannot be cleared Inconsistent load distribution for IP equal cost multi-path SR Number 10290855 10319953 10324290 10323511 10311193 10319967 10304762 10302493 10314599 10288704 30140323 10310624 30123035 10323516 10320418 10316058 10299165 10323873 10317997 10198436 10317835 10311802 10322908 10307891 10318194 10309941

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 111 Table 20 (Continued) Items resolved in P7.0 Title No CAS response when a ping is issued on down PPP interface CATL4 | 3 CP crashes with same NMI error Missing accounting records/Dlcis stop reporting accounting ATM-IP FP: Inconsistent CLP bit setting for Egress traffic GateWay: Invalid "callingNumber" identified in vsr/x svs/y Multiple arp entries with same ipCos value Tos byte should not be used in sending VRRP advertisement 10BaseT continuously reboot TB flooding on CQC card does not work for atmMpe Fp crash during switch over CP switchover causing inVrCp swerr tTcmBGP2 _tcmTask running at 94% QSIG:PP answers to RESTART_ACK with RESTART_ACK Policies With Multiple Port Ranges May Not Work Properly Policies do not take effect after ipCos feature is added LanIdTable entries not aged out (SRB) Tb via 100baseT/ AtmMpe drops traffic PP520:attributes values cannot be set in NMS prov tool PP high CPU , shared message block exhaustion 7013 0011 ATM-IP FP:IP forwarded stats can be misleading No alarm raised when cable is pulled for 10BT port. IPX/100baseT interworking ATM-IP FP: ARP over MPE not working R7.0 Packaging Problem : rmsTandem "ping -rtd" command issue from a PP running 4.2 to a PP runn SR Number 10288360 10314496 10313428 10309939 10317679 10321152 10326658 10323765 10302724 10320588 10317787 10326181 30316362 10319627 10321188 10326669 10323114 10315784 10287492 10326844 10325285 10326667 10294126 10320414 10327427

Items Resolved in the P7.0.1 (BG00S1A) Release


The following is a list of SRs that have been resolved in BG00S1A.
Table 21 Items resolved in P7.0.1 Title Changing Startup to allow the customer to input a VR name Bicc syntax error SR# 10266391 10270677

Release Notes for P7.0.11

112 Appendix C Items Resolved in Previous Releases Table 21 Items resolved in P7.0.1 (Continued) Releasing allocated memory to prevent a shelf crash Error in shown amount of service disrupted after Check Prov CAS Check Prov unjustified error: spooling and agentQueueSiz Invalid Fairness Policy Behaviour for ABR OAM Performance: Unexpected Rxdiscard on CQC when OAM cells ON Early statistic records (Timestamp in MDP statistics) RxLinkUtilization and TxLinkUtilization not Reporting Correctly CAS plane response error PQC2 Introduction on Passport 6400 - running PQC2 as PQC2 ATM-IP FP: Exceeding defaulted totcappool causes SWERR Criticality is not being held through card reset Virtual Link Vpt Check Prov Failure Causing Abort/SWERR Local Session corruption causes swerr with every command VCC VCD TM - Altering TM to ABR values causes SWERRS Enhancement: need txUtilization attribute under AtmIf Vpt Ports stay down on new E1C card after provisioning ATM OAM: VPC segLinkSideLoopbackState Bridge crash with no traceback Sw fault/task EE30-antCr type mismatch/ internal mmy write protect fault VR IPX not showing stats Enhancements for Virtual Link VPT DS3/E3 ATM - IP crashing ABR MCR fairness and support for ATMMPE over ABR MSB SAL Throttling GFC bits not reset to zero when a cell with non zero GFC is received ATM-IP FP: Bridging: failed assertion in mySalIntHandler10_v Unresolved symbol list for baseMsbDs3E3FpSp_BG0018Cd.o in VxSim IPCos Links bad after Copy Prov DE frames are not mapped to cell of CLP=1 10304708 10316668 10319305 10336186 30130005 10309826 10332783; 10314599 10316915 10337464; 10321094 10328758 10330790 10331672 10310169 10313390 10316612 10326957; 10326958 10333533 10336656; 10316291 10301945 10314086 10321572 10335139; 10325823 10339091; 10339086 10341764; 10342387 10344386 10327538 10343998 10345177 10297097

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 113 Table 21 Items resolved in P7.0.1 (Continued) 100BaseT: 100BT Ethernet card crashes when IfState changed ATM-IP FP: VR0's are not created for Token Ring IP_TUN: IPX failed to pass thru over Tunnel using GreIp encapusulation SWERR doing OSPF provisioning while VR is locked CP crashes when deleting BGP export policy RIPv2 updates missing provisioned static routes ATM-IP FP: Changing from llc to ipxVc Encap causing crash ATM-IP FP: MOP counter not reset to 0 with IP and TB traffic EP/DP not managed properly in non-cos datapath Forwarding address used from inactive OSPF interface by NSSA RP router sends incorrect interface address in register stop ATMMPE: AtmMpe remains down after AC prov changes IP CoS feature for ATMIP Fp and other fixes 10333480 10341736 10264491 10301629; 10298703 10348765 10300643 10320346 10341605 10320733 10329809 10332280 10332306 10335018; 10332867; 10335020; 10335082 10335804 10321108 10332267 10332867 10335159 10336547 10338773 10303191 10333476 10333872 10335512 10340093 10341203 10341505 10332782 10340430; 10341836 10340475 10341985 Release Notes for P7.0.11

CP2 crashes after IPX/Filter activation Extend functionality of netSentry debug tool Multicast routers don't fwd packet224.0.1.0-224.255.255.255 IPCoS: inwIpFeh swerr when IPCoS added to FrDte sw lpt ARP Table Not Displayed Properly CDL changes & data member ppforwardingData ATM-IP FP:Bridging hardw. dpath cause Bridging VNS to break Congestion Causing ARP Problem ATMMPE: AtmMpe's are disabled after shelf reset FP Crash during get port address BGP reset shelf "l vr/1 ip bgp" VNS: IP traffic over VNS does NOT work from CQC to PQC BGP-matching mechanism enhancement Unresolved symbol in package cmsCommonS when ip is not provisioned Deleting IP off VR and activating view with IP causes rtgProcList SWERR Deletion of IP without IpMcast does not work properly SRB frames with double RIF in case of SRES-SRB-PB-TB path ATM-IP: SGAF card crash due to a null pointer

114 Appendix C Items Resolved in Previous Releases Table 21 Items resolved in P7.0.1 (Continued) IP_MCAST: RP failed to send SPT join when LHR joins RPT ATMMPE: InwArp swerr on SGAF AtmmMpe Multiple ICMP ATM-IP FP: Crash when trying to uninstallBrPort MCAST traffic rate dropped unexpectedly ATM-IP: atmmpe feat won't load on SGAF card BGP Policy Enhancements - Exclusion Routes ATMIP: LP reset on br flood after lck & unlck vr/1 br CacheStats alarm Id incorrect and 2pOC3SmAtm2 IPX support LHR on Broadcast network fail to forward Multicast packets ATM-IP: SGAF card crash during FWD between VNS and ATMMPE A field was misdefined MPANL Causes Card Crash Node Stuck in Staging causes PP Mid table not to be updated More than 18,000 Alarms 70090404 in around 10 seconds ETSI ISDN Protocol Error for MPANL Link ppath and ping does not work in 5.1.20 when Rid Substitution is needed Signalling Vcd Component Defaults Fail Check Prov Fax Relay fails to train at V.27 Fax Relay power levels vary as data rate changes Fax Relay fails to train at 2400 bps SNA DLR - FR BAN fails to work with Bay Router Ethernet SNA DLR: Activating new provisioning view will not complete APPN performance degradation TRK PA report a bad maxReservedBwOut ATM TRK SWERR: tpaAtmHook.cc sweers after deleting Trk PA co Call failed with QSIG to QSIGGF PBX Network Failure sending DTMF authorization codes Invalid IE in NOTIFY message identifying undefined Display MVP: FAX CanonE-600 can not send DIS frame to remote FAX PP4460 - PP6400 Interworking for G.711 10343632 10344405 10233486 10338062 10312656 10330461 10337872 10341984 10345238 10346024 10346326 10346691 60315008 10328000 10328001 10326705 10334924 10325360 10341384 10341385 10341386 10333033 10327731 10253264 10304233 10336296 10335147 10322321 10339004 10324703 10338063; 10340466; 10341067 10343768 10296570

G.711 w/ 40 Byte Frames Causes DSP Reload C function call from ASM in wrong page mode Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 115 Table 21 Items resolved in P7.0.1 (Continued) Comfort Noise Generation does not get reset between calls TPT does not switch to operating mode comfortNoiseCap value of -65 dBm0 not provisionable Initialize silence condition in SAD 10318503 10315757; 10337890 10339903 60317013

Items Resolved in the P7.0.2 (BG00S2B) Release


The following is a list of SRs that have been resolved in BG00S2B.
Table 22 Items resolved in P7.0.2 Title 2pOc3 SGAF APS does not switch properly SWERR: Wrong reported 'actualLineSpeed' of V.11-Ports EHOU2 DS3 ATM card crash File System sw error at dcsSpooler.cc;1354; and sfsCasIfGlob Problems in the SDD files_propagation_from_p5.0_to_present FP crash when bridge traffic going over domain bridging IMA Sparing Issue IMA Interoperability Issue Unrecoverable SWERR in rpcLib.c during task "EE0-stdEe" V.35 DCE port does not report proper status VL Vpt Causing Inaccuracies in AQM Shaper AtmIf TxCell Count problem with ABR over VL ATMIF Stats Manager not collecting dynamic VCC stats for PORS on CQC ATM-IP FP: Missing Bridge Forwarding Entries on CP ATM-IP: IP/VNS over CQC to PQC performance degradation ATM-IP: Frame Corruption on Egress causing LP crashes ATM-IP: Fail Assertion: isAllocated (vriId) ATM-IP: I-PQC FFL crashes with Bridging over AtmMpe link ATM-IP: Ingress SGAF card crashes when flooding to 4 or more other interface ATM-IP: IPFrag causing SGAF card to crash ATM-IP FP: failedAssertion deallocate__6MsbVri ATM-IP: SGAF card crash due to IPcoS isValidOnCard() missing assert for incorrect card number SR# 10277051 10327606 10292605 10319569 10327806 10350424 10353456 10294561 10337919 10307134 10317969 10320510 10327249 10333599 10334273 10342771 10351395 10350086 10339260 10341991 10348800 10349064 10350166 10334461

Release Notes for P7.0.11

116 Appendix C Items Resolved in Previous Releases Table 22 (Continued) Items resolved in P7.0.2 MsbAtmPortClassIterator not working The memory allocated to the LcmProcess was not released Token Ring Ipfrag LRC problem Tuples dropped from IPX srvc list Reset Shelf Causes IPX SWERR CIP : Potential Memory leak areaLsaCksumSum for router's in same area should be the same VRX/EMHT entries are not removed when PPP protocol port is locked No semantic check when linking ATM IP AtmMpe to IlsFwdr FP Migration escapes for R5.1 to R7.0 Crash in BGP export policy RIP packet processing and flush timer problem 10346845; 10337636 10314938 10316748 10323830 10353989 10294593 10130775 10211814 10335039 10336354 10340378 10348764 10349158 10349161 10349164 10315988 10326956 10321919 10318517; 10343126 10349836 10346367 10354815;10 356136

Frame UnderRuns incrementing while in tpt mode PORS Route Selection Overflows at DS3 Speed and Above CSRM not re-learned if the connected Passport node isolated FR-ATM SIWF InATMARP translation incompatible with RFC222 APPN migration issue from 4.2 to 5.1 - attributes CP crash when setting interfacename Br traffic go SW & ingress enet card reset when SGAF reset

Items Resolved in the P7.0.3 (BG00S3A) Release


The following is a list of SRs that have been resolved in BG00S3A.
Table 23 Items resolved in P7.0.3 Title Wrong management of C and I signals after view activation Wrong include file in dmePqcSystemFlash.cc AAL1 CES port must be locked and unlocked to clear user data CAS Prov: Corrupted Data error msg when migrated to BG0015D VL Shaping Fix Phase 2 SR# 10290854 10283899 10306718 10318208 10320510

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 117 Table 23 (Continued) Items resolved in P7.0.3 LRC Errors PQC Egress when Fowarding Mutiple MAC's ATMIF Stats Manager not collecting dynamic VCC stats for PORS on CQC ATM-IP: Fails to pass traffic on VPC/256 ATM-IP FP: Can not do a dmeTrace without loading strap ATM-IP: DME support for empty local frame head block ATM-IP: SGAF VNS to PPP causes bridge frames to discarded Software Error in pms subsystem, pmsCommonSemanticChecker.cc;260 Ipx SGAF fwding to VNS, tb outNuCastPkts count CP crash when issuing a certain command sequence MSB Frame Corruption Workaround MSB Iterators causing Memory corruption DME copy fix V35 cards must be reset after upgrade from 4.2.13 IMA lifts after lock/unlock - protocol error V11 - Localloop test failed V11 card crashes IP broadcast storms will affect other services Ospf Not Returning Proper info from Neighbour SNMP Queries Type 7 LSAs not generated for RIP Routes in a NSSA area IP CoS not respected when entering IP Tunnel ARP frames not using the best available discard priority FP crashed (during traffic flow) when provisioning mcast Filter reload does not work Ospf does not Re_converge when Primary DS# link fails Problem with GvcIf device monitoring 10332976 10333599 10334226 10338155 10348850 10358435 10342168 10356166 10343774 10346367 10346045 10349076 10352814 10357198 10358563 10360747 10317809 10354360 60324582 10354596 10330148 10301358 10348603 10344152 10347690 10346213 10348261 10357907 10357957 10353288 10353019 10360871 10326966 60315008 10328449 10344453 Release Notes for P7.0.11

pim domain provisioning error Delete CBSR does not change locally & IGMP query time wrong frmFromIf and octetFromIf reset during manual test V35 reboot: Fault is diagnosed as a bad access @ 0x2bf protection fault Switched data not working on a voice service MVPE:displaying Lp E1 or DS1 Audio component crashes card

118 Appendix C Items Resolved in Previous Releases Table 23 (Continued) Items resolved in P7.0.3 Voice Networking Call Hunting pcmcapture feature for dcme link vs crashes card Software Error generated when running traffic to PP4400 Card crashes after 3 dsp reloads 10344792 10346706 10355892 10357763

Items Resolved in the P7.0.4 (BG00S4C) Release


The following is a list of SRs that have been resolved in BG00S4C.
Table 24 Items resolved in P7.0.4 Title Multiple time servers will not synchronized after migration LineSpeed value rounds down instead of rounding up PP high CPU , shared message block exhaustion 7013 0011 Traffic using VPI >= 256 not working on SGAF DS3/E3 cards OC3 SGAF card crashes at file dmePqcDispatcher.cc Passport MIB-II contain ifPhysAddress with value ....01.00 txLinkUtilization & rxLinkUtilization incorrect for CQC Cards with VPCs OAM Cell causing a Sys Recoverable error FP Shared Memory not released after sh card test JT2A Port Test Failures Adding a VPC to an ATMIF on an IMA card constantly crashes Fragment from PP6000 and PP7000 PEC code split FS (MD-1999.0751-01.01) maxVPT initialized to maxVPC on Migration Command list doesn't work as expected for some components PRI ISDN does not restart if the FP cable is removed Long Pump Message for MPANL V35 crash with netSentry ATM-IP FP:Severe exception 252 on VRI 1 with IP traffic StartUp ATMMPE on ATM IP FP OSPF over multiple ATM VCC s and IPCoS Chk Prov allows broadcast IP to be the same as PP logIf IP NMI: Local Bus Error at InwIpxSap::serverOnThisPor Alarm 0000 9000 (VR/1 subcomponent) IP multicast affects IP unicast performance on ILS forwarder SR# 10326297 10356746 10356815 10359622 10359988 10362165 10363001 10363200 10330413 10368363 10374319 10369699 10369224 10351184 10365530 10368915 60320439 10343594 10332638 30324593 10341603 10080718 10357365 10081095 10365964

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 119 Table 24 (Continued) Items resolved in P7.0.4 Passport fails to forward multicast datagrams out PQC card Probes not sent from first hop router FHR when oif list is null SRES table not updated Netsentry filter problem with broadcast IP address (255) Ospf routes did not list if cost associated with > 65535 Passport 7.0 corrupted 802.3 Length field for Netbios frames VMAC address sent out by TR VRRP is rejected by w/s FR DTE LMI procedure IPX over FDDI fails after migration to r5.1 due to wrong MAC address Configuring RIP timers Router hangs when activate static routes with over 2 oifs Master VRRP router doesn't go down when it is no longer the primary IP owner Trace printf shows a mangled source address PORS trunk doesnt update the trunkcost attribute configured PORS: Software error "WINDOW Window Full" CSM stuck Vsr/x SVS/y back in service by channel TPT takes 30 secs to come back after 2100Hz tone is removed DSP memory dump occured during traffic re-routing DetGen/SAD causes double digits Passport dropped out of fax Relay mode when signal level low Transmit CAS yellow is activated if one VS path is removed PVC negotiation robustness Beep Tone heard over voice channel with E1 MVP-E FPs 10374361 10367013 10329812 10357629 30117735 10368374 10368367 10348329 10354034 10361458 10357888 10362214 10363924 10366450 10339159 10352213 10318461 10319230 10344376 10319625 10356631 10359949 10360643 10364633 60324479

Items Resolved in the P7.0.5 (BG00S5A) Release


The following is a list of SRs that have been resolved in BG00S5A.
Table 25 Items resolved in P7.0.5 Title E3A crashes when the ILS FWDR is added CP boot time more than 40 mins with 1493NetSentry apply table entries Add new Group to FRDTE out of Service Blur 7K node - not respond to any command & generate unknown SR# 10352439 10370674 10372970 10374939

Release Notes for P7.0.11

120 Appendix C Items Resolved in Previous Releases Table 25 (Continued) Items resolved in P7.0.5 Multicast: Packet replication on PQC fails ATM IP FP Crash after migration from 7.0.2 to 7.0.3 Gvcif on CFP1 discards frames when packet splitting NS Source does not switch on degraded reference ATMIP FP OC3S card disabled Node red in NMS as result of changing single attribute on PP CP crash when changing prov of ingress/egress gain Speech break up on MVPE cards when raising level of voice 10378571 10367646 10368387 10374964 10367360 10374137 10377155 60331471

Items Resolved in the P7.0.6 (BG00S6A) Release


The following is a list of SRs that have been resolved in BG00S6A.
Table 26 Items resolved in P7.0.6 Title rtcManualSetTime bug Non-standard date and time of day interface illegal CPU utilization in new PDC card. illegal CPU utilization in new PDC card. problem related to 8pds1 ima card ( cpu 200% utilization ) SR# 10140304 10170454 10386024 10386721 10386722 10389383

Items Resolved in the P7.0.7 (BG00S7B) Release


The following is a list of SRs that have been resolved in BG00S7B.
Table 27 Limitations Resolved in P7.0.7 Title Incorrect date and time of day format Prop: Flood of 70182001 causes 100% cpuutil - No info in alarm VNET Accounting: vnetFlags_faxRelayDownspeed not working CP Crashed and switched over to spare CP PROP: Failure of Correlation Tag in FR-ATM Accounting Prop: Memory utilization increase on PP running P5 and PNNI Prop: Issue with indb: lock/unlock brings the inLocaldb attrib Failure of IMA link causes slow response V35 card Crashes with BG0026Ad debug load SRNumber 10170491 10288468 10322043 10328014 10330700 10331527 10345749 10351390 10357223 CustRefNumber

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 121 Table 27 (Continued) Limitations Resolved in P7.0.7 Title Prop: Equipment Failures on Shelf card/1 on Passport GNHE02 Unresolved Symbol in porsAccFPs_BG0029Ad.o Issue with Operator Camp-On to remote extensions on Voice Networking Performance are not very stable with Bridging over VNS Prop: DS1C crash : NMI is diagnosed as a watchdog timeout BCS software swear on BG0032A CP crash, no more local message blocks CP Crash:Unrecoverable Software error at line 264 in file pcsUtils.cc Prop: A trunk doesnt come up after a migration from 4.2 to 5.1 in AAL1 card externalloop feature failure..... Multicast: debug statements should be removed from library. SRNumber 10358386 10365947 10367282 10368251 10370185 10370439 10371697 10373080 10374198 10377933 10379203 CustRefNumber

ISDN signaling channel hangs after cable disconnect and reconnect within 10379792 1 sec Prop: bgp running in a loop Prop: ATM UNI ILMI Failure Prop: DLR service interrupting if lock/inlock issued on VR Prop: AAL5 protocol error after FRF.8 (CPI Common part indicator w Prop: MSG 90000 Big Pev Message C=0x68006 CC=4 Prop: FDCR: Alarm 9000 when you try to set a dna to a fruni Watchdog timeout (interrupt 155) token ring card crashing FSD doesn't work properly. NetBIOS problem under ATMIP FP using ATMMPE s/w upgrade failure (5.1.30 to 7.0.4) 10381213 10381497 10382422 10383885 10384621 10385176 10385190 10386559 10387033 10387779

Passport 6400 MVP QSIG/CAS GATEWAY doesn't send ALERTING for 10387804 call to pp4400. Unable to unlock j2mv port (diagnostics failed). Prop: NTP 241-7501-210 Vol 3 error Echo cancellation is not operational on E1 or DS1 MVP Prop: Problem in the Media Registration for an atmmpe protocol port SWERRS gerenrated/BCS error occured during migration FDDI:LCM: Crash in preDeleteScan FDDI:LCM: crash in changeInPortToPpId V35: LCM: Crashes in preDeleteScan. CNYC22 isolated from network/routing topology 10388017 10388297 10389251 10389507 10392657 10392962 10392967 10392974 10393003 Release Notes for P7.0.11

122 Appendix C Items Resolved in Previous Releases Table 27 (Continued) Limitations Resolved in P7.0.7 Title MCDN calls with more than 12 digits in calling line ID are r Prop: No IP connectivity via X25 DTE 100BT Master VRRP reply with its physical MAC address after being unlocked MCDN / Auto attendant interaction PP-Virtual Media IP-address not exported into OSPF as stated in NTPs Unexpected CTD values Prop: Unable to get interworking between Passport DLR an ARN an P2 Prop: IMA card crashing continously BDM NIS: Call handle set to release, call still attmpted with no digits. Prop: E1 AAL1 FPs in 5.1.20: lock/unlock channel issue CAC b/w allocation leak S-PVC/P get "no route to destination" after trunk going down Standby CP crashed during migration from pcr2.1(CB0036A) to Prop: Memory leak - Network Timing Synchronization Startup facility causes crash on ATM IP FP Subcomponents not displayed when listing the lp DLR: PUs are not able to reconnect to host after IPL Prop: Passport crash StartUp ATMMPE on ATM IP FP. Start Up facility doesn't support VNS over ATM IP FP Virtual router unable to move up the component instance tree netbios/ipx packet causes atm/ip DS3 card to reset 802.3 length corrupted with ethernet 100mb card causing novel failed dd SRNumber 10393120 10395494 10396077 10398392 10398984 10398995 10399044 10401401 10402990 10406654 10410391 10410405 10411320 10411339 10420647 10421368 10421386 10421466 30324593 30335056 30337963 30340076 30343415 010212-6086 010212-6858 010212-6695 CustRefNumber

MCDN changes Facility codes causing problems when mapping to DPNSS 30348197 Prop: OAM AIS insertion dose not work on VPT VCC or VPC nrp Test component will disappear after lp/0 switchover. 60322573 60335975

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 123

Items Resolved in the P7.0.8 (BG00S8B) Release


The following is a list of SRs that have been resolved in BG00S8B
Table 28 Limitations resolved P7.0.8 Title Prop: Port 1 on 100BT card always not working when ATM-MPE present CA shows incorrect poolAdmittedConnections Clearing ARP results in inability to ping between the end stations Echo cancellation is not operational on E1 or DS1 MVP Prop: FSM msg alarm (msgCode=1966089 portIndex=8) Provisioning SAD slownandcongested causes software Errors Prop: FP Crash, NMI at Interupt 164, current task 164 in Call handle set to release, call still attmpted with no digits. Prop: PP15K OC3 FPs crash when DS3 FP with PQC2.0 is added to shel Overflow condition in connPoolUsage attribute under Standard Vpt types PROP: Cisco routers and fratm do not handshake after bootup Prop: Crash: CBRU1 CARD/0 - Offending task PNNI Hello Interval not respected. IP-Tunnel: check prov fails with 32 bit netmask 1pE1V card resets when change CID value Physical line interrupt: no PtoMP SVCs ; SwitchedMultiCastB Corrupted Facility IE in MCDN Set-up Messages Passport 6400 ATM IP card problem SRES double RIF fix prevents arp to 4120 or 4400 ping with small packets won't work when we using FrDte conne DSP asserts and recentinglinesamp 0000 SPVC connection issue in PCR2.0.2. Loader bug with respect to patch removal Entering d lp/0 cpeth crashes the CFP1 E1C Card connot be loaded with software 7.0.6 Prop: Changing the perserve domain parameter requires the fast eth TRACE feature on LP/x TR/x create SWERR and not able to turn OFF, once turn ON DS1MVP VNET CAS MCA DATA CALLS ARE CAUSING DSP ERRORS ATM IP (2POC3SMATM) card reboots after issuing l atmif/40 vcc/0.40 tm Prop: Support for FRF.8.1 not included in 5.1 or 7.0 SRNumber 10332907 10374182 10375170 10389251 10390185 10396007 10399019 10402990 10404114 10405908 10406137 10407007 10410662 10411740 10411885 10413717 10414058 10415139 10416623 10417554 10419539 10420354 10421057 10421123 10421353 10421543 10421745 10421751 10422354 10422573 010418-1282 010314-1807 010319-3636 010305-7156 010211-4760 010211-5084 CustRefNumber

Release Notes for P7.0.11

124 Appendix C Items Resolved in Previous Releases Table 28 (Continued) Limitations resolved P7.0.8 Title PP jumping to wrong state during call progress Repeating FTT (failure to train) using faxRelay Prop: HTDS stats error: Rx frame/sec - Rx kbits/sec PROP: Cannot IP ping w/ less than 510bytes-FRrouter to ATMrouter t "blockSnapSave" Crashes SBIC Card With Watchdog NMI softwareError : Caused by NCAS sessions not being torn down. E1C Card connot be loaded with software 7.0.7 CP local ethernet connect doesn't work from STARTUP Crash and VRcbs suspended for InwArp problem. 8port E1ATM (IMA) atmif ca Bandwidth allocation pr elapsedTime=0 if set Mpanl/<n> voice acct ao ster even the call is answere Startup AtmMpe doesn't work on E1 CQC Cards IP traffic delayed with traffic shaping enabled in 7.0.7 VRRP check sum error Prop: Problem with BGP aggregation policy in 5.1.27 HEC Error: Add numberOfIntervals for HEC error detection SRNumber 10423320 10423357 10423546 10423948 10424687 10425389 10425604 10425643 10426284 10426960 10427893 10428672 10430252 10430914 10431355 10432490 10432918 010528-6595 010528-6531 010508-9840 CustRefNumber

Locking and resetting Lp/5 Eth100/0 produced loss of service in Lp/5 Eth100/1 10434586 Prop: VR problem after resetting the Passport Kernel should pick IP address from EPROM if cpEthernetConfig file missing DSP asserts due to incorrect media frame size PROP: Failure of Correlation Tag in FR-ATM Accounting Problem in the Media Registration for an atmmpe protocol port TPT causes DSP Assert from 4pmvpe add : 3c34 BTDS Idle Suppression not working properly on MVPE EOC silence timer triggers too quickly on MVPE Mofax upspeed & downspeed fails on MVPE E1qsig MVP Card Crash during voice traffic Card crash after vnet component lock and unlock several time Prop: Variance DPRS strange behaviour Prop: CP crash when setting up >40 OSPF interfaces per VR Prop: MSG 0000 9000 nmiDcsHandler.cc, line 296; p7.0d.37 Prop: TR card crash with unrecoverable software error generated 10436217 10436568 10437180 10437894 10439375 10439718 10439842 10439847 10439851 10440515 10440683 10442002 10442008 10442103 10443590

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 125 Table 28 (Continued) Limitations resolved P7.0.8 Title Prop: CP crash with ARP operation DSP: FaxRelay Assert no DCS component Prop: Propagate a default route through VR Crash: CBOM1 LP/13 V35 SBIC QCSRAM Parity Error FRATM - Failed to activate provisioning data of FrAtm Crashes on 3pOC3Sm card 100BaseT card loses connectivity when port deleted SRNumber 10443909 10444792 10445764 10446367 10446413 10447745 10449355 10450657 CustRefNumber

TMuxOper : Trk/12 reports congestion state under the TRM Lg Lk while it isn't 10451137 Prop: Static Routes won't go into RDB if there is an OSPF external route Prop: OC12 FP Crash: Intrpt 162 at task DmeResumeDisp_t/Execute In PROP: ARP entries are display continuously in loop mode after migr SNA DLR calls dropped if two ports are in the same TR and one of them is discon. Prop: 3pE3A (CQC) crash : Unrecov. SWERR at line 278 in file pcsUtils.cc Domain number don't change on operational data in Lte component DS3Atm2 FP crash. excDumpTrace are display continuously under OS mode 10454965 10455437 10455905 30005839 30130765 30324467 30342025

Items Resolved in the P7.0.9 (BG00S9A) Release


The following is a list of SRs that have been resolved in BG00S9A.
Table 29 Limitations resolved in P7.0.9 Title PROP: Variance DPRS strange behaviour Lan-Wan-Lan Bridging performances aren't symetrical (Bad on port 1) PROP: OSPF checks N-bit in option field when receiving DD Packet. clockSourceStatus unknown when automaticBusClockTest is enabled AntiTromboning SWERR when picking up parked call Correct reporting of DSP Asserts Cannot IP ping w/ less than 510bytes-FRrouter to ATMrouter through Fratm Gwy SRNumber 10442002 10444767 10449718 10450429 10451186 10456568 10458064 CustRefNumber

Release Notes for P7.0.11

126 Appendix C Items Resolved in Previous Releases

Items Resolved in the P7.0.10 (BG00SAB) Release


The following is a list of CRs that have been resolved in BG00SAB
Table 30 Limitations resolved since last release # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 CR ID Q00098485 Q00305998-05 Q00306117-06 Q00306148-06 Q00306178-06 Q00306179-07 Q00306185-05 Q00306188-07 Q00306202 Q00306206-07 Q00306239 Q00306257-07 Q00306258 Q00306918-04 Q00306999-04 Q00307211 Q00307343-04 Q00307419 Q00307492-04 Q00307557-05 Q00307562 Q00307569-04 Q00307602 Q00307659-04 Q00307676 10457199 10434429 10470238 10444597 10456006 10476416 10450046 10452762 10452934 10459545 10456780 010827-0569 10820-1389 10479220 10474720 10469150 10480424 10460411 010919-6742 10461011 10483820 10458393 020610-7745 10482240 SR # 10476319 CustRefNumber Title Packaging of the Global Support Tool (GST) PROP: Crash: NMIS Local Session's kill Timer Corrupt aqm constant and maxMBS calculations incorrect IP cross-VPN traffic on Eth100Bt because CAM not enable for Port 1 Code-Red virus affecting Passport IP nodes PROP: 100% CPUUtil when CP reload with 2000 static arp entries Prop: VpiEv value corrupted. PROP: OSPF Adjacencies status stay in INIT DSP assert with 6ea3 occurring during fax call NCAS (NON CAll Associated sessions) not being torn down EURO ISDN DOES NOT RESPOND TO RESTART PROP: PP7K: 3.0: Local message block congestion Fratm on PP6400 doesn't understand 1490ProtocolHeader = 0300800000000806 ILMI registration proces of ATM address problem PMP AddPartyRequests queue up causes memory exhaustion BTDS Service does not recover after trunk failures. PP15k uni signaling channel disappears when vcd add/ del MVP-E interworking to 4400 Lost DTMF Digits FRDTE ifadminstatus has no effect after lp or shelf reset PROP: PGR: migration: High CPUtil on OC3 cards. PP6K: SW 5.1.31: 00009000 COL/STATS sw error Fratm - ATM correlation tag problem MVPE ignores DTMF control messages from PP4400 prior to answer supervision PROP: RIP v1Compatible updates not send out of FrDte rg with nbma VNCS attributes have incorrect range in CDL

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 127 Table 30 Limitations resolved since last release # 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 CR ID Q00307676 Q00307725-04 Q00307991-08 Q00308056 Q00308821 Q00312072-01 Q00312281-05 Q00312469-01 Q00312575-04 Q00312708-01 Q00315404 Q00315413 Q00315414 Q00315490 Q00315507 Q00315510 Q00315512 Q00315514 Q00315525 Q00315526 Q00315532 Q00315533 Q00315535 Q00315536 Q00315537 10412590 10420772 10420825 10451982 10458230 10459828 10460304 10460625 10465297 10465307 10469476 10469622 10470143 10470834 10471076 011130-6358 020514-4790 011030-2801 011018-1533 011001-9476 020405-0446 010309-9615 SR # 10456780 10464300 10476053 10475580 10470291 011114-4591 CustRefNumber Title VNCS attributes have incorrect range in CDL PROP:CPU utilisation on a V11 is at 100% -> can't r Unrecoverable Software error in file mvpCompProcess.cc Propagation of the Global Support Tool (GST) NMI occured at interrupt level due to local bus error PROP Errors in CD0118A when a call is forwarded or parked CP0 not reloading when IP 7K node is reset after testing IP. Prop: CC01S1B:callPark produces SWERR Prop: 4pDS1MVpe: vnetUipeDchanMaint swerr Prop:4pMVPE:-Crash due to memory protect violation 4p E1 AAL1 CRC4mode does not work When VC's MBS is set lower ECR goes up rather then down Cannot migrate from BE01SVA to BG00S7A Passport 6400 icmp redirect problem set Vroute/n Interface sends alarm on all switch components 2pOc3MmAtm2 card crashes when migrating to 7.0.8 Prop: Unrecoverable Software error at line 658 in file pqcIn Statistics between E1V and MVPe are different in VS framer CAM not repopulated even though traffic running for 30 min After node reboot FTE appearing on VR/0 when traffic on VR/1 FTE not flushed when bridge port is deregistering Configurable Route Preference Prop of CD1220 into p7.0 SNMP walk of 100.3.5.2.2 causes SWERR FP Crash: E3 is rebooting after sw upgrade to 7.0.9 The real traffic doesn't flow over 92% of ASR with DS3A(PQC).

Release Notes for P7.0.11

128 Appendix C Items Resolved in Previous Releases Table 30 Limitations resolved since last release # 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 CR ID Q00315548 Q00315553 Q00315554 Q00315556 Q00315557 Q00315562 Q00315562 Q00315566 Q00315567 Q00315568 Q00315571 Q00315574 Q00315575 Q00315577 Q00315579 Q00315583 Q00315586 Q00315589 Q00315607 Q00315611 Q00315842 Q00315843 Q00315844 Q00315846 Q00315847 SR # 10474318 10474588 10474594 10474783 10475133 10477589 10477589 10479106 10479145 10479353 10479558 10479779 10479780 10479810 10480520 10481281 10481726 10482078 10484342 10484364 10482559 10482040 10479096 10474102 10473116 011130-6527 020219-4990 020314-7861 020228-6225 020213-4409 020522-5689 011225-9119 020131-2907 011210-7469 020611-7883 020129-2485 011107-3777 020131-2968 010702-8623 011115-4814 020205-3332 010804-6565 020405-0345 011106-3649 020208-3858 020426-2977 020208-3858 020426-2977 CustRefNumber Title D2V MAC Address Issue on PP7480 Shelf 7.0.9: Entries in RDB not in FWD table PP6480 - IMA Grp must be bumped to restore connectivity Traffic Delay After CP Switchover XPL: IP Card crash after using ""get"" command Too many DSP reloads cause unrecoverable software error crash Regression failure on DSP reloads reporting 1pE1MVPe: Card crashes due to No more local msg blks IP stop forwarding if LEQ component is provisioned under PPP Acct subcomponent under vroute/x will not list operationally Memory leak on CP when VRRP is enabled on some VRs Load Balancing Feature, ARE filter feature Arp tracing on by default when entering OS Tracing ILP exception handling on PQC required in 7.0 Passport:6480:7.0.010BaseT card(2 & 7) crash Call Back (CCBS) QSIG supplemenatry feature does not work in 7.0.7/9 Reporting of DSP asserts NMI acces exception - BATMAN crash MCDN blind transfer with CLID IE with more than 12 digits calls fail One way speech/no egress messages from DSP PP6K: 7.0.9: NMI Offending task ""EE19-vrCbs"" Fed optimization - improve system recovery time CRS Function problem after CP Switchover or Reset Only vrrp master should use VMAC in ARP requests/ replies CP crash at task ""SftpSrvE1"" and ""EE16-Ntpd""

Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 129 Table 30 Limitations resolved since last release # 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 CR ID Q00315848 Q00315848 Q00315849 Q00315850 Q00315851 Q00315852 Q00315853 Q00315853 Q00315855 Q00315862 Q00315955-01 Q00315962-01 Q00315984 Q00316223-01 Q00316431-01 Q00316458 Q00316460-01 Q00318778 Q00336944 Q00361573-01 Q00363679 Q00366585 Q00384380 Q00386597 020402-9873 SR # 10472539 10472539 10468087 10466397 10463599 10463166 10459448 10459448 10450343 10430243 10375437 10375432 10328088 10448684 10464508 10479740 10482241 020314-7877 020402-9933 010809-2560 010212-5749 010702-8623 011115-4814 010619-7684 020514-4835 CustRefNumber 011212- 7876 011212-7876 011001-8221 020123-1692 011107-3777 011107-3811 011022-1919 Title CP Crashes at boot time due to LMB exaustion CP Crashes on boot memory issues relating to NetSentry V35 ports dropping for short period of time after RTS comes TB over ethernet connected to Cisco NMI crash PQC Frame FreeList is not sane on ingress VNS multicast ping fails - Linkgroup tables out of sync ATM trunks break ping -trace -all rtg vns node commands ATM IP trunks break ping -trace -all rtg vns node commands PP4450 voice traffic is running over the data VCC of SPO-mux trunk list vr/x pp/y sna circuit/**** doesn't show all the sessions established FP crashing when receving corrupted frames Bridging: AtmMpe Pp TBP InFrames stats not incrementing during flooding Extra digits within the ARP tables in 5.1/7.0 loads CP crash at tq_summary DLR account records dont contain description about information transferred Enhance existing load balancing feature to make it provisionable MSA32 : Cannot Establish rt-VBR SPVC Connections to FrAtm NSSA ABR missing default route from other ABR in rdb and fwd table to NSSA area FP restarted to clear SDL problem Prop: MCDN Break-in not working SWERR generated when changing snmpAdminStatus for bgp comp. 100BT debug tool .o file is not downloaded with other ILS software pp6k - FRATM Swerr (fedType.cc, fedT1v.cc, etc...) when Prov'ing Siwf Sd Checksum Errors in Uplink PTSEs Release Notes for P7.0.11

130 Appendix C Items Resolved in Previous Releases Table 30 Limitations resolved since last release # CR ID SR # CustRefNumber Title 6400 PANL does not support over 4096 Byte Packet Length Prop:MCDN SigChan PNI 020103-9532 CP Crash at P7.0.9 while handling NetIP Frame. Back Prop: Vnet StdUipe Codec.cc swerr when calls running and reload performed MDM conflicts with wireless comp/attrib in ENTERPRISE loads Prop: 4p Vnet MCDN - Conference call release causes card crash 020313-7690 Duplicate ospf external route in rdb pp6k, sddetoclpmapping in fratm siwf and niwf is not working properly in spvc pp6k sdfecntoefci mapping on fratm dlci siwf spvc is not working correctly 020429-3135 020424-2559 020405-0439 020315-8040 VRRP on Token-Ring uses Phys-Mac Address 2nd ECMP route is not in rdb PP6K:Passport 6K and 4K interworking (Problem with Auth code entry) MVP crashes (FP restarted to clear ADL problem) pp6k - Swerr when configuring atmPnni : antPnniRAGroups.cc; 351 on Cqc Prop: antitromboning swerr Prop: PP7K PCR 2.3.3 NCAS sessions not torn down and facility msgs are rejected Prop: PP7K PCR 2.3.3 software error generated when timer expired STAB: Unrecoverable error in ldrStartFirmware.cc on CP pp6k - Every 2nd conn NOT getting connected for SPVC/SPVP/SVC from UNI int. pp6k - 8pDS1 FP Crash when testing Btds connections - with valid/invalid config MPANL-MVP interworking over AALSPO trunk Voice debug DSP code needed STAB: Unrecoverable Software error - SBIC boot tests failed with code 3005 Eap Broadcast optimization

100 Q00410344 101 Q00412494-01 102 Q00412643 103 Q00416647-01 104 Q00417977 105 Q00420298-01 106 Q004215842 107 Q00421640 108 Q00421643 109 Q00422450 110 Q00426054 111 Q00426929 112 Q00429304 113 Q00429941 114 Q00431526-01 115 Q00456952-01 116 Q00457494-04 117 Q00457640-07 118 Q00458118 119 Q00458137 120 Q00462485 121 Q00463761 122 Q00469103-08 123 Q00469222 Release Notes for P7.0.11

Appendix C Items Resolved in Previous Releases 131 Table 30 Limitations resolved since last release # CR ID SR # CustRefNumber Title Crash on FDDI FP while testing ILS Sanity 020723-2469 020724-2586 020805-3831 2pEth100BaseT FP resetting after upgrade to 7.10 due to ICMP Error (TTL=0)

124 Q00471485 125 Q00490874

Release Notes for P7.0.11

132 Appendix D Documentation Updates

Appendix D Documentation Updates


V.11 function processor
NTP 241-6401-610 Passport 6400 FP Configuration and Testing Guide SR # 30345930 V.11 FP configuration parameters When configuring a V.11 FP, use the following values to help you set component attributes: Card type <cardtype>: V11 Ports <port>: X21 Port numbers <m>: 07 Line speeds and link modes The 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 robustness speeds for ports on the same function processor, there may be conflicts for the following speeds: 768000 640000 512000 384000 320000 256000 128000 64000 Configuration of ports for lines speeds and link mode must follow these rules: all ports within a group (ports 0 to 3 for group 1 and and ports 4 to 7 for group 2) are configured as either DCE (that is, DCE is supplying the line clock) or DTE through the linkMode attribute; one group can be DCE and the other DTE, or both groups can be of the same link mode if the ports in a group are DTE, you can configure any common or robustness line speed with no conflicts occuring

Release Notes for P7.0.11

Appendix D Documentation Updates 133

if the ports in a group are DCE, the ports can be any speed except one of the conflicting speeds noted above If you do not follow these configuration rules, the check prov fails and the system lists the conflicting speeds.

V.35 function processor


NTP 241-6401-610 Passport 6400 FP Configuration and Testing Guide SR # 30345930 V.35 FP configuration parameters When configuring a V.35 FP, use the following values to help you set component attributes: Card type <cardtype>: V35 Ports <port>: V35 Port numbers <m>: 07 Line speeds and link modes The 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 robustness speeds for ports on the same function processor, there may be conflicts for the following speeds: 768000 640000 512000 384000 320000 256000 128000 64000 Configuration of ports for lines speeds and link mode must follow these rules: all ports within a group (ports 0 to 3 for group 1 and and ports 4 to 7 for group 2) are configured as either DCE (that is, DCE is supplying the line clock) or DTE through the linkMode attribute; one group can be DCE and the other DTE, or both groups can be of the same link mode if the ports in a group are DTE, you can configure any common or robustness line speed with no conflicts occuring
Release Notes for P7.0.11

134 Appendix D Documentation Updates

if the ports in a group are DCE, the ports can be any speed except one of the conflicting speeds noted above If you do not follow these configuration rules, the check prov fails and the system lists the conflicting speeds.

NTP 241-6401-805 PP6400


There was a mistake in documentation in NTP 241-6401-805 PP6400. Please see below for details. ----------------------------------------------Passport 6400 Bridging Guide Publication: 241-6401-805 Document status: Standard Document version: 7.0S2 Document date: August 2000 ----------------------------------------------p. 139 --> bottom of page
Procedure 16

Provisioning transparent bridging example 1. Enter provisioning mode.


start Prov

2. Define the base and feature software by specifying the application version
list (AVL). set sw avl base_<software_level> bridge_<software_level> inWBase_<software_level> <---------module should be "inwBase"

Release Notes for P7.0.11

You might also like