Reference for Passport 4400 and 6400/7400 Interworking

Part No. 209372-FNovember 2003

4555 Great America ParkwaySanta Clara, CA 95054

Reference for Passport 4400 and 6400/7400 Interworking

2

Copyright © 2003 Nortel Networks

All rights reserved. November 2003.

The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks Inc.

The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of that license. The software license agreement is included in this document.

Trademarks

Nortel Networks, the Nortel Networks logo, the Globemark, Unified Networks, Marathon, Passport, and Preside are trademarks of Nortel Networks.

Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.

Ethernet is a trademark of Xerox Corporation.

Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation

Pentium is a registered trademark of Intel Corporation.

SPARC and SPARCstation are trademarks or registered trademarks of Sparc International, Inc.

Java, Solaris, Sun, and Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc.

UNIX is a registered trademark of X/Open Company Limited.

All other trademarks and registered trademarks are the property of their respective owners.

The asterisk after a name denotes a trademarked item.

Restricted rights legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of conditions

In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the right to make changes to the products described in this document without notice.

Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission.

209372-F

3

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).

Nortel Networks Inc. software license agreement

This Software License Agreement (“License Agreement”) is between you, the end-user (“Customer”) and Nortel Networks Corporation and its subsidiaries and affiliates (“Nortel Networks”). PLEASE READ THE FOLLOWING CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT. If you do not accept these terms and conditions, return the Software, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price.

“Software” is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and is copyrighted and licensed, not sold. Software consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole or partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired the Software. You obtain no rights other than those granted to you under this License Agreement. You are responsible for the selection of the Software and for the installation of, use of, and results obtained from the Software.

1. Licensed Use of Software. Nortel Networks grants Customer a nonexclusive license to use a copy of the Software on only one machine at any one time or to the extent of the activation or authorized usage level, whichever is applicable. To the extent Software is furnished for use with designated hardware or Customer furnished equipment (“CFE”), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable. Software contains trade secrets and Customer agrees to treat Software as confidential information using the same care and discretion Customer uses with its own similar information that it does not wish to disclose, publish or disseminate. Customer will ensure that anyone who uses the Software does so only in compliance with the terms of this Agreement. Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly authorized; b) reverse assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneficiaries of this provision. Upon termination or breach of the license by Customer or in the event designated hardware or CFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction. Nortel Networks may audit by remote polling or other reasonable means to determine Customer’s Software activation or usage levels. If suppliers of third party software included in Software require Nortel Networks to include additional or different terms, Customer agrees to abide by such terms provided by Nortel Networks with respect to such third party software.

2. Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer, Software is provided “AS IS” without any warranties (conditions) of any kind. NORTEL NETWORKS DISCLAIMS ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligated to provide support of any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties, and, in such event, the above exclusions may not apply.

3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS OF, OR DAMAGE TO, CUSTOMER’S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN


4

ADVISED OF THEIR POSSIBILITY. The forgoing limitations of remedies also apply to any developer and/or supplier of the Software. Such developer and/or supplier is an intended beneficiary of this Section. Some jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply.

4. General

a) If Customer is the United States Government, the following paragraph shall apply: All Nortel Networks Software available under this License Agreement is commercial computer software and commercial computer software documentation and, in the event Software is licensed for or on behalf of the United States Government, the respective rights to the software and software documentation are governed by Nortel Networks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections 12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities).

b) Customer may terminate the license at any time. Nortel Networks may terminate the license if Customer fails to comply with the terms and conditions of this license. In either event, upon termination, Customer must either return the Software to Nortel Networks or certify its destruction.

c) Customer is responsible for payment of any taxes, including personal property taxes, resulting from Customer’s use of the Software. Customer agrees to comply with all applicable laws including all applicable export and import laws and regulations.

d) Neither party may bring an action, regardless of form, more than two years after the cause of the action arose.

e) The terms and conditions of this License Agreement form the complete and exclusive agreement between Customer and Nortel Networks.

f) This License Agreement is governed by the laws of the country in which Customer acquires the Software. If the Software is acquired in the United States, then this License Agreement is governed by the laws of the state of New York.

.

209372-F

5

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Passport 4400 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Passport 6400 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Passport 7400 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 1Introduction to Passport 4400 Interworking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Passport 4400 Series Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Introduction to PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Interworking Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Passport 4400 Features Not Supported by Passport 6400/7400 Equipment . . . . . . . . . . . . . . . 21

Chapter 2Primary PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

PANL Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Primary PANL Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Direct Primary PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Tunneled Primary PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Primary PANL Over ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

ISDN BRI Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Passport 4400 Switches Support Through ISDN TAs at Both Ends of the ISDN BRI

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Passport 4400 Unit Connects to the ISDN BRI or PRI Network Using an ISDN TA 30Passport 4400 Unit Connects Directly to the ISDN BRI Network . . . . . . . . . . . . . . . 31

Non-Cascading Passport 4400 Configuration: Logical View . . . . . . . . . . . . . . . . . . . . . . . . . . 32


6 Contents

Cascading Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Setting Up the PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Passport Network Prerequisites for the PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Loading Default Passport 4400 Unit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring the Passport 4400 Unit WAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring the WAN port for Direct Link or Frame Relay Tunneling . . . . . . . . . . . 37Configuring the WAN Port for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Considerations for High Data Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Defining PANL Signaling Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39DNA Prefix Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 3Backup PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Functional Overview of Backup PANLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Backup PANL for Non-Cascading Passport 4400 Units . . . . . . . . . . . . . . . . . . . . . . . . . . 42Backup PANL for Cascading Passport 4400 Units with Link Only Backup . . . . . . . . . . . 42Backup PANL for Cascading Passport 4400 Units with Full Node Backup . . . . . . . . . . . 43

Topology for Backup PANLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Cascading Passport 4400 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Cascaded Configuration with Link Only Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Cascaded Configuration with Full Node Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Analog PSTN Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Setting Up Backup PANLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 4Interworking for NMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

NMCR Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Software Distribution Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

NMCR Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Topology for NMS on Mission Critical User Data Networks . . . . . . . . . . . . . . . . . . . . . . 62

209372-F

Contents 7

Defining the Virtual Circuits to the NMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring IP for NMS Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Setting Up the SPVC to the NMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Setting Up the Static Route to the NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 5User Data LAN Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Core Router Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Topology for Connection to the UCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71LAN Interworking Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Internetworking Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74LAN Interworking Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Routed IP and IPX Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Bridged LAN Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Passport 4400 Unit Modes: Routing Versus Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Setting up VCs to the UCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Prerequisites for the Passport 4400 unit for UCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Prerequisites in the Passport Network for UCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configuring IP for User Data Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Configuring IPX for User Data Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Setting Up the SPVC to the UCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Setting Up LAN Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Prerequisites for the Passport 4400 unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Provisioning Routing for IP and IPX Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Provisioning IP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Provisioning Optional Routing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Provisioning Bridging for LAN Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Configuring the Passport 4400 Unit for Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90


8 Contents

Setting Up the SPVC to the UCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Defining Bridging Filtering Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Defining Bridging Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Virtual Router Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 6Frame Relay Access Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

FRAD Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95FRAD Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Payload Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Implementing Frame Relay Pass-Through for FRADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Configure the Frame Relay DCE Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Define the Frame Relay Switch Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Fine-Tune Transmission Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 7Voice Services Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Functional Overview of Voice Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Protocols Supported in Passport 4400 to 6400/7400 Voice Interworking . . . . . . . . . . . . 104

BRI and PRI Voice Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105MVP/MVP-E Function Processors Supporting Voice Interworking . . . . . . . . . . . . . . . . 108Audio Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Call Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110Call Progression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Network Addressing Used by Passport 4400 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Voice-Related Connections over the Passport 4400 to 6400/7400 Link . . . . . . . . . . . . . . . . . .112Functional Overview of Voice Interworking over ISDN BRI . . . . . . . . . . . . . . . . . . . . . . . . . .113

ISDN BRI to ISDN BRI Tie Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113ISDN BRI to PRI Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114PRI Tie Trunk Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

209372-F

Contents 9

Passport Network and PSTN Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115D-Channel Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Voice Interworking Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117ISDN BRI to ISDN BRI Tie Trunk Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119ISDN BRI to PRI Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Passport Network and PSTN Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Setting Up Voice Services Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Backwards Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Setting Up Voice Services on the Passport 4400 Units . . . . . . . . . . . . . . . . . . . . . . . . . . 128Populate the Voice Ingress and Egress Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Define Voice Profiles on the Passport 4400 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Comparison of Passport 4400 Unit and Voice Networking’s VoiceProfile Configurations 130Interaction Between Passport 4400 Unit and VoiceProfile Attributes . . . . . . . . . . . . . . . 130

Example of a Passport 6400/7400 VoiceProfile Configured for Voice Interworking 130Provisioning Voice Services for Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Provisioning Voice Networking for the Passport 4400 Units . . . . . . . . . . . . . . . . . . 132Setting Up the RSI on the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Configuring the ISDN BRI or PRI Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 8Traffic Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Overview of Traffic Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Emission Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Discard Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Transfer Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

DE-bit Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140BECN Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Passport Trunk Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Passport 6400/7400 PANL Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Passport 4400 PANL Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Packet Compared to Weighted Round-Robin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149


10 Contents

Multiple PVC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Transfer Priority Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Summary of Traffic Engineering Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Number of Voice Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Speech Activity Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Emission Queue for Voice Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Discard Priority for Voice Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Minimum Link Bandwidth for LAN Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Branches for NMS Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Voice over Tunneled PANL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Configurable Link-Level Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Additional Considerations for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Example Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Typical Configuration on Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155PANL in Tunneled Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Appendix ANetwork Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Call Redirection in a Passport 6400/7400 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Functional Overview of RID/MID Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Topology for RID/MID Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Setting Up RID/MID Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Provision the CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Provision RID/MID Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Interworking with Passport 6400/7400 Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Functional Overview of Interworking with Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . 164Topology for Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Setting Up Hunt Groups for Passport 4400 Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Prerequisites for the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Prerequisites in the Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

209372-F

11

About This Guide

This document provides example network topologies that illustrate the interworking between Passport* 4400 units and a Passport 6400/7400 network. Each chapter contains the following:

• Functional overview, that describes how the Passport 4400 unit interworks with the Passport 6400/7400 network

• Topology, that defines the scope of the interworking for the layer or service described in the chapter

• Prerequisites for the Passport 4400 unit and the Passport 6400/7400 network to establish interworking for the layer or service

• High-level summary of the provisioning steps and a discussion of the values you need to configure

The topologies described in “Primary PANL” on page 23 and “Backup PANL” on page 41 illustrate how the Passport 4400 unit connects to the Passport 6400/7400 network over frame relay and ISDN. This connection is essential, as all services use this link.

This document does not provide detailed provisioning steps. This information is in the Passport 4400 and 6400/7400 documentation suites and in Getting Started with Passport 4400 and 6400/7400 Interworking. See “Related Documents” on page 13 for a list of related documents and publications.

This document is intended for persons who are responsible for placing into operation Passport sub-networks which incorporate Passport 4400 units as access devices. These individuals may be responsible for any of the following tasks:

• Planning

• Engineering

• Installing and provisioning

• Operating and maintaining


12

You should have a good understanding of the following concepts:

• Passport 6400/7400 networking

• Frame relay connectivity

• Internetworking (IP, IPX, bridging, and routing)

• Passport 6400/7400 voice networking

Terminology

In the documentation, software, and MIBs for Passport 4400 and Passport 6400/7400 equipment, the terms PANL and MPANL are used interchangeably to refer to the Passport Access Network Link function. MPANL is the earlier term, but is still in common usage. MPANL is the term used within the Passport 6400/7400 command sets.

In this document, the term Passport 6400/7400 is used to refer interchangeably to either a Passport 6400 (all supported software versions) or a Passport 7400 (software version PCR4.2 and higher) system.

Conventions

The following list describes documentation conventions:

• nonproportional spaced plain type

Nonproportional spaced plain type represents system generated text or text that appears on your screen.

• nonproportional spaced bold type

Nonproportional spaced bold type represents words that you should type or that you should select on the screen.

• italics

Statements that appear in italics in a procedure explain the results of a particular step and appear immediately following the step.

209372-F 00

13

Words that appear in italics in text are for naming.

• [optional_parameter]

Words in square brackets represent optional parameters. The command can be entered with or without the words in the square brackets.

• <general_term>

Words in angle brackets represent variables which are to be replaced with specific values.

• UPPERCASE, lowercase

Passport commands are not case-sensitive and do not have to match commands and parameters exactly as shown in this document, with the exception of string options values (for example, file and directory names) and string attribute values.

• |

This symbol separates items from which you may select one; for example, ON|OFF indicates that you may specify ON or OFF.

• ...

Three dots in a command indicate that the parameter may be repeated more than once in succession.

Related Documents

This document uses commands and information found in the Passport 4400 and Passport 6400/7400 suite of documents. For additional information, consult the following documents:

Passport 4400 Documentation

The following documents are part of the Passport 4400 document library:

• Getting Started with Passport 4400 and 6400/7400 Interworking (209371)

• Reference for Passport 4400 and 6400/7400 Interworking (209372)

• Reference for Passport 4400 Command Line Interface (CLI) (214371)


14

• Configuring and Operating the Passport 4400 (214372)

• Implementing QSIG on Passport 4460 (214280)

The Passport 4400 product documentation is delivered on the product CD and is also available from Nortel Networks* Web site (www.nortelnetworks.com).

Refer to the release notes (Passport 4400 Release Notes for Release x.x) for a complete list of available manuals for the product release you are using.


• Passport 6400 Commands (241-6401-050)

• Passport 6400 Hardware Description (241-6401-200)

• Passport 6400 Preside Multiservice Data Manager Connectivity Guide (241-6401-275)

• Passport 6400 Security and Access Control Guide (241-6401-350)

• Passport 6400 Call Redirection Server Guide (241-6401-410)

• Passport 6400 Hunt Group Server Guide (241-6401-415)

• Passport 6400 Multiservice Passport Access Network Link Guide (241-6401-480)

• Passport 6400 Voice Networking Guide (241-6401-755)

• Passport 6400 Remote Server Agent Guide (241-6401-765)

• Passport 6400 Bridging Guide (241-6401-805)

• Passport 6400 Frame Relay DTE Access Guide (241-6401-810)

• Passport 6400 IP Routing Guide (241-6401-815)

• Passport 6400 IPX Routing Guide (241-6401-820)

• Passport 6400 Frame Relay UNI Guide (241-6401-900)

• Passport 6400 Frame Relay ISDN Switched Access Guide (241-6401-925)

• Passport 6400 Release Supplement

• Passport Networking Introduction (241-7501-310)

For a complete list and description of documentation in the Passport 6400 document library, see the Passport 6400 Documentation Guide (241-6401-001).

209372-F 00

http://www.nortelnetworks.com

15


• Passport 7400, 15000, 20000 Commands (241-5701-050)


• Passport 7400, 15000, 20000 Network Management Connectivity Guide (241-5701-271)

• Passport - MDM Network Security: Operations (NN10600-605)

• Passport - MDM Network Security: User Access Configuration (NN10600-606)

• Passport - MDM Network Security: Secure Communications Configuration (NN10600-607)

• Passport 7400, 15000, 20000 Call Redirection Server Guide (241-5701-410)

• Passport 7400, 15000, 20000 Hunt Group Server Guide (241-5701-415)




• Passport 7400, 15000, 20000 Frame Relay Fundamentals (241-5701-901)

• Passport 7400, 15000, 20000 Configuring Frame Relay (241-5701-902)

• Passport 7400, 15000, 20000 Understanding IP (241-5701-805)

• Passport 7400, 15000, 20000 Configuring IP (241-5701-810)

• Passport 7400, 15000, 20000 Frame Relay UNI Summary Card (241-5701-905)

• Passport 7400, 15000, 20000 Frame Relay Fundamentals (241-5701-901)

• Passport 7400, 15000, 20000 Configuring Frame Relay (241-5701-902)

• Passport 7400, 15000, 20000 Networking Overview (241-5701-400)

• Passport 7400, 15000, 20000 Overview (241-5701-030)

For a complete list and description of documentation in the Passport 7400 document library, see the Passport 7400, 15000, 20000 Documentation Guide (241-5701-001).


16

How to get help

If you purchased a service contract for your Nortel Networks* product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance.

If you purchased a Nortel Networks service program, contact one of the following Nortel Networks Technical Solutions Centers:

Additional information about the Nortel Networks Technical Solutions Centers is available from the www.nortelnetworks.com/help/contact/global URL.

An Express Routing Code (ERC) is available for many Nortel Networks products and services. When you use an ERC, your call is routed to a technical support person who specializes in supporting that product or service. To locate an ERC for your product or service, go to the http://www.nortelnetworks.com/help/contact/erc/index.html URL.

Technical Solutions Center Telephone

Europe, Middle East, and Africa +44 (0)20-8920-4618

North America (800) 4NORTEL or (800) 466-7835

Asia Pacific +61 2 8870 8800

China (800) 810-5000

209372-F 00

http://www.nortelnetworks.com/help/contact/global

http://www.nortelnetworks.com/help/contact/erc/index.html

http://www.nortelnetworks.com/help/contact/erc/index.html

17

Chapter 1Introduction to Passport 4400 Interworking

The Passport 4400 series of multiservice access units provides robust and flexible networking for all types of branch traffic. Passport 4400 units can carry voice, fax, video, LAN, and other data services, such as frame relay, SNA, SDLC, X.25, asynchronous, and HDLC over a choice of physical link options. These options provide efficient, reliable, and easily managed services for mission-critical, time-sensitive applications. The Passport 4400 series includes the Passport 4430, 4450, 4455, and 4460.

The Passport 4400 series of multiservice access units reduces networking costs, provides traffic consolidation, and extends the Passport internetworking solution to the branch office.

Passport 4400 Series Highlights

The Passport 4400 series allows network managers to:

• Reduce branch networking costs through traffic consolidation, bandwidth management, network link options, flexible equipment, and fully integrated networking and management.

• Simplify the use of new applications and services through powerful IP networking and a modular and flexible architecture.

• Benefit from end-to-end networking solutions with full service interworking and superior traffic management.

• Operate a scalable, manageable network through switched networking, with comprehensive and fully integrated management and networking services.

• Provide proven superior voice services by extending award-winning Passport voice features to the branch.


18 Chapter 1 Introduction to Passport 4400 Interworking

Introduction to PANL

The Passport 4400 series devices use the Passport access network link (PANL) protocol to access the WAN link to a Passport 6400/7400 series switch at a major site or backbone node. PANL is a Nortel Networks innovation that closely follows the standards for voice over frame relay (VoFR), FRF.11, and FRF.12 with extensions for switched virtual connections (SVC) and related signaling. These standards provide compression and framing, as well as fragmentation of large data frames for the insertion of voice frames to ensure acceptable levels of delay and delay variation (jitter).

Passport access networking for the Passport 4400 series products (Releases 2.0.3 through 2.0.11, 3.1.x, 4.x, and 5.x) works in a hierarchical model with regional backbone sites using Passport 6400/7400 series nodes. The backbone network provides:

• Switching and directory functions

• A robust, high-speed network to central headquarters and data-center locations

• Failure-recovery and traffic prioritization features

The challenges in providing access to the backbone network from many branch locations are:

• Operational costs

• Scalability

• Traffic management

The Nortel Networks PANL protocol solution addresses these challenges.

Nortel Networks PANL reduces operational costs by provisioning at connection end-points only. This approach reduces the provisioning and maintenance requirements since you do not need to define fixed paths through intermediate nodes from end-to-end. PANL addresses scalability needs associated with networking to hundreds or thousands of small branch locations, and provides effective traffic prioritization. Further, using various WAN link types with PANL enables you to implement the most cost-effective solution for each branch.

209372-F

Chapter 1 Introduction to Passport 4400 Interworking 19

Interworking Features

The following is a summary of the interworking features described in this document.

• Passport PANL interworking features

— PANL on dedicated lines

— PANL over frame relay (PANL tunneling) with ANSI, ITU and LMI

— Dial-up backup link over ISDN in case of primary link failure

— Emission priority queues for traffic management

— Discard prioritization on Passport 6400/7400 nodes (not supported on Passport 4400 unit)

— Support for switched virtual circuit (SVC) and soft permanent virtual circuit (SPVC) signaling

— Voice over frame relay (VoFr) and path-oriented routing system (PORS) for support of voice connections

— A-bit handling

— Support for Passport 4400 PANL-level backup or Passport 4400 node level backup through cascading and Passport call redirection features

• LAN interworking features (user data)

— Support for Passport inter-LAN services (ILS) as the user core router (UCR)

— LAN interworking (through frame relay PVC) with Passport ILS

— RFC 1490 bridge frame routing

— IP and IPX routing

— RIPv1 and RIPv1c, and RIPv2

— Passport 4400 IP prioritization is supported using Passport 4430, 4450, and 4455 Release 4.x units and Passport 4460 units with:

— Passport 6400 equipment at Release 7 or newer

— Passport 7400 equipment at Release PCR4.2 or newer

• LAN interworking features (NMS connectivity)

— Support for Passport ILS as network management core router (NMCR)

• Frame relay service interworking

— Frame relay DCE access service (permanent virtual circuit (PVC) only) interworking with Passport frame relay UNI access service



— Rate adaptation and enforcement supported on Passport only

— Support for both NI-23 and NIS standards for frame relay ISDN switched access

— Use of intermediate Passport 6400/7400 nodes to route frame relay traffic to other nodes that can terminate Passport 4400 calls

• Voice interworking features

— Voice network channel associated signaling (CAS) on DS1 multipurpose voice platform (MVP), E1 MVP, and TTC2M MVP

— G.729 CS-ACELP compression

— Fax demodulation at 9600 bps

— Echo cancellation (per Passport 4400 unit, multipurpose voice platform)

— Speech activity detection (SAD)

— Interworking with Passport 4400 unit FXO, FXS, E&M

— CAS/wink start

— RSI/RSA for access to Passport VNCS voice profiles

— CUG validation for RSI/RSA

— Support for voice services over ISDN BRI

— Support for voice services over ISDN PRI (QSIG)

• Topology and addressing features

— Each Passport 4400 unit can have a maximum of one DNA prefix address

— Connection of either a single Passport 4400 unit per PANL link or a cascaded series of two or more Passport 4400 unit per PANL link

— True link and node backup through node cascading and RID/MID redirection

— Call redirection in Passport 6400/7400 networks when the destination is unreachable because of node or link failure along the designated connection

— Access to DPRS services through hunt groups

209372-F

Chapter 1 Introduction to Passport 4400 Interworking 21

For proper interworking with Passport 4400 units,:

• a Passport 6400 release level of Release 4.2 or later is required

• a Passport 7400 release level of Release PCR4.2 or later is required:

Passport 4400 Features Not Supported by Passport 6400/7400 Equipment

• Certain Passport 4400 Release 4.x channel types cannot be terminated on Passport 6400/7400 ports. These channels must be terminated on other Passport 4400 units. However, the connections between these channels can be switched through Passport 6400/7400 units. The Passport 4400 Release 4.x channel types that cannot terminate on Passport 6400/7400 units are:

— Voice Over IP (VoIP)

— X.25. However, you can use the Legacy Data Module (LDM) on Passport 4430, 4450, and 4455 units to allow interworking of X.25 channels with Passport 6400/7400 units.

— Async. However, you can use the Legacy Data Module (LDM) on Passport 4430, 4450, and 4455 units to allow interworking of async channels with Passport 6400/7400 units.

— SNA. However, if the Passport unit is equipped with SNA DLR using BAN encapsulation and Passport 6400 Release 5 or higher, SNA channels from Passport 4400 Release 4.x units can be supported.

• HTDS: the Passport 6400/7400 HTDS services do not interwork with the Passport 4400 HTDS service. Passport 4400 HTDS channels must be terminated on Passport 4400 units.

• Passport 6400/7400 BTDS services are the equivalent of Passport 4400 CBR services. BTDS does not interwork with CBR.

Note: Support for Passport 6400 Release 5.1 and all earlier releases is not available after December 31, 2002. For more information, contact your Certified Distributor or Account Manager.



209372-F

23

Chapter 2Primary PANL

This chapter describes the requirements for establishing the primary Passport access network link (PANL) between the Passport 4400 access unit and the Passport network. This chapter is organized around the following topics:

• “PANL Functional Overview” on page 23, provides a general description of how PANL works

• “Primary PANL Topologies” on page 25, provides a description of the physical and logical components involved in PANL

• “Cascading Topologies” on page 32, describes Passport 4400 units in a cascading topology

• “Setting Up the PANL” on page 35, provides the following information on installation and provisioning:

— Prerequisites that the Passport 4400 unit and the Passport network must have in place to support PANL

— Overview of the provisioning process

— Notes on requirements to achieve successful interworking

• “Further Information” on page 40, provides a list of related documents

For information on backup PANL configurations, see “Backup PANL” on page 41.

PANL Functional Overview

PANL is a frame relay interface that permits the Passport 4400 unit to establish a low-level connection to the Passport network. It is based on FRF.11 and FRF.12. This connection is the PANL and corresponds to the physical and data link layers of the OSI communications model.


24 Chapter 2 Primary PANL

The PANL consists of PANL interfaces at both the Passport 4400 unit and the Passport switch (the end points of the connection), where the interfaces support a permanent connection. This permanent connection in turn supports switched virtual circuits (SVCs) for dynamic voice calls across the network and soft permanent virtual connections (SPVCs) for data calls (network management and user data services) across the network.

When you have established the link, you can provision service interworking in which the Passport 4400 unit (a branch access) and the Passport network support user and network management traffic. To do this, PANL encapsulates voice and data in packets. PANL supports connectivity services to the Passport network, which require the Passport 4400 unit and the network to interwork effectively. Establishing the PANL is the first step in configuring the Passport 4400 unit for service interworking.

Three scenarios are described in “Primary PANL Topologies” on page 25:

• Direct connection over a dedicated facility

• Tunneled connection over a public frame relay network

• Dial-up or dedicated connection over a public ISDN network

The Passport 4400 unit supports the following physical media:

• V.35, V.11, RS-232, X.21

• DS1 and E1 CSU/DSUs

• DS1 channel and E1 channel

The Passport 4400 unit supports the following physical interfaces:

• V.35, V.11, RS-232, X.21

• 56 kbps CSU/DSU

• T1 and E1 CSU/DSUs

• ISDN BRI (Europe, Japan and North America)

209372-F

Chapter 2 Primary PANL 25

These topologies provide the same capabilities from the perspective of service interworking. Here is an illustration of the protocol layers for PANLs:

The tunneled frame relay encapsulation is always present in the packet for direct connections, tunneled connections, and ISDN connections. On direct links, PANL at both ends of the connection ignores this encapsulation.

Primary PANL Topologies

The primary PANL can be one of the following configurations:

• Direct connection over a dedicated facility (for example: T1, E1, V.35, and V.11)

• Connection through a public frame relay network

• Connection through a public ISDN network

The following sections describe each of these connections in non-cascading topologies. The figures in this section illustrate these configurations. (For clarity, figures do not show services.) Typically, one or more Passport 6400/7400 switches provide the PANL connections for multiple Passport 4400 units deployed around the edge of the Passport network.

For information on cascading topologies, see “Cascading Topologies” on page 32.

Direct Primary PANL

The direct primary PANL has the following characteristics:

• The link is a permanent connection.

• A Passport 4400 unit and a Passport 6400/7400 switch can be co-located or remote (from the network point of view, the switch is part of the network backbone).

FrameRelay PANL Data or Voice Services



• Services in the Passport network are accessible through other Passport 6400/7400 switches or third-party switches within the network.

Typically, the facility connects to the Passport 4400 unit through port 2 (a DTE/DCE serial access port). However, port 1 or 3 can also be the primary port. The type of port that you use on the Passport 4400 unit and on the Passport 6400/7400 switch depends on the network topology. For further information on assigning port type see the following documents:




Here is the topology for direct PANL:

PassportBackbone

Passport4400

(PANL)Passport

Connections to other Network Services

Passport(PANL)

PANLLink

PANL Link

Other Network Connection to Service

Connections to other Network Services

Passport 4400

Legend:

209372-F


Tunneled Primary PANL

The tunneled primary PANL supports the same traffic types as the direct link and has the following characteristics:

• The connections provided by the public network are frame relay PVCs.

• The facilities that support the direct PANL also support tunneled PANLs.

• The Passport 4400 unit and the Passport 6400/7400 switch are not co-located.

The service provider for the frame relay network provides hardware and facilities within the sphere of that network. Typically, you use this configuration to take advantage of connectivity over an existing public frame relay network. Using an existing frame relay network may be desirable where you have multiple Passport 4400 units and you want to take advantage of lower tariffs for public frame relay services.

Here is an example of a tunneled PANL through a public frame relay network:

Note: The service provider for the public frame relay network supplies all the equipment and facilities in the public network. These requirements are transparent to provisioning the tunneled link.

Passport 4400

Public FrameRelay Network

Passport4400

(PANL)

PANLLink

PassportNetwork

Passport(PANL +FRMUX)

Legend: PANL link Connection through Frame Relay Network



Primary PANL Over ISDN

The primary PANL over ISDN supports the same traffic types as both the direct link and the tunneled link and has the following characteristics:

• The connections provided by the public network are PVCs.

• The ISDN facility connects to an ISDN port on an ISDN BRI WAN module that is installed in the Passport 4400 unit (when this module is ordered with the unit or installed later as an upgrade). The Passport 4400 ISDN BRI WAN module supports basic rate interface (BRI) only.

• The ISDN facility connects to either a DS1C or E1C FP in channelized mode, which you configure for primary rate interface (PRI).

• The Passport 4400 unit and the Passport 6400/7400 switch are not co-located.

• Services in the Passport network are accessible through other Passport 6400/7400 switches or third-party switches within the network.

The Passport 4400 unit supports the following ISDN protocols:

• ETSI ETS300-102 (Europe) plus supplementary services (ETSI 300-xxx). Note that NET3 and NET5 define test procedures for ETS300-102 and have been replaced by I-CTR 3 and I-CTR 4.

• AT&T 5ESS (North America)

• Northern Telecom DMS100 (North America)

• NTT INS64 (Japan)

• Q.SIG

At the link level, the ISDN stream supports frame relay and Passport 4400 NetLink (VoFR) protocols.

209372-F


The following is an example of a PANL through a public ISDN network. You can replace the direct link with a tunneled link with no change in functionality or provisioning.

ISDN BRI Configurations

The configurations that follow can be used for both primary PANL and backup PANL applications.

• “Passport 4400 Switches Support Through ISDN TAs at Both Ends of the ISDN BRI Network” on page 30

• “Passport 4400 Unit Connects to the ISDN BRI or PRI Network Using an ISDN TA” on page 30

• “Passport 4400 Unit Connects Directly to the ISDN BRI Network” on page 31

Note: The above illustration also shows a backup PANL over the ISDN connection with the primary link over a direct connection.

Passport 4400

PassportNetwork

Passport4400

(PANL) Public ISDNNetwork

Passport(PANL)

PANLLink

Legend:Primary PANL LinkBackup PANL Link over Public ISDN Network



Passport 4400 Switches Support Through ISDN TAs at Both Ends of the ISDN BRI Network

PANL at the Passport 4400 unit is in a dedicated mode. You can set the PANL to operate at any speed up to the maximum speed to which ISDN TA is configured.

The Passport 4400 unit’s WAN port can be an ISDN TA module or the Serial WAN Interface Module, depending on the type of connection. ISDN can be used for the primary link as well as the backup link. There is only one primary link that is active all the time. The backup link is activated only when the primary link is out of service.

Passport 4400 Unit Connects to the ISDN BRI or PRI Network Using an ISDN TA

The Passport 6400/7400 unit is connected to the ISDN network using PRI or BRI, depending on the connection. If you use PRI, the connection must terminate on either a DS1C or E1C FP, depending on the country of operation. If you use BRI, an ISDN TA is required and the termination in the Passport 6400/7400 unit is to a V.35 FP. In this case, you must use a converter, since most ISDN TAs use a V.24 connector on the user side.

Passport 4400

V.35 FPrunning PANL

Passport 4400

Serial Interface

PANL

Passport6400/7400

BRI BRI

ISDN TA

ISDN TA

V.35ISDN

Passport 4400

V.35 FPrunning PANL

Passport 4400

Serial Interface

PANL

Passport6400/7400

PRI orBRI

PRI orBRI

ISDN TA

ISDN TA

V.35ISDN

209372-F


Connect the Passport 4400 unit’s Serial WAN Interface Module to an ISDN TA using a V.24 cable in most cases. Configure the PANL speed to either 64 Kb/s or 128 Kb/s. The ISDN TA will convert the Passport 4400’s output and place it on the ISDN network, based on either the U or S/T interface. The connection to the ISDN network can be either BRI or PRI, depending on the TA you use.

Passport 4400 Unit Connects Directly to the ISDN BRI Network

Connect the Passport 4400 unit’s ISDN module to the ISDN BRI network using either the U or S/T interface. Connect the Passport 6400/7400 unit to an ISDN TA using a V.35 FP.

Passport 4400

V.35 FPrunning PANL

Passport 4400

ISDN U or STInterface

Passport6400/7400

BRI BRI

ISDN TA

V.35ISDN



Non-Cascading Passport 4400 Configuration: Logical View

The illustration that follows shows the logical view of the connections described in “Direct Primary PANL” on page 25, “Tunneled Primary PANL” on page 27, and “Primary PANL Over ISDN” on page 28.

In the above illustration, note the assignment of PANL-DCE on the Passport network side of the PANL and of PANL-DTE on the Passport 4400 side of the PANL.

Cascading Topologies

Cascaded network configurations involve multiple Passport 4400 units that interconnect in a tree formation or hierarchy. Access from the cluster of Passport 4400 units to the Passport network is over a single primary PANL between the Passport 6400/7400 switch on the network edge and the top-level Passport 4400 unit in the cluster. This configuration offers reduced investment in equipment, since a number of Passport 4400 units can access the Passport network over a single PANL.

PANLPort 2

Passport 4400

PassportPANL

DTE

PrimaryPANLLink

DCE

Direct or Tunneled PANL Link

Refers to PANL-DTE

Refers to PANL-DCE

DTE

DCE

Legend:

209372-F


The technical characteristics of this primary PANL are identical to the links described in the preceding subsections. Further, the Passport 6400/7400 node at the network edge can register multiple DNA. As a result, the network can forward calls to all nodes in the cluster. Here is an example of cascaded Passport 4400 units and the arrangement of the primary PANLs:

Passport 6400/7400

PANL

Passport 6400/7400

PANL

Primary PANLLegend:

Passport 4400

Passport 4400

Passport 4400

Passport 4400

Passport 4400

Passport4400 D

(Subordinate)

Passport 4400Cluster

Passport4400 A

(Top LevelPassport

4400 Unit)

Passport4400 E

(Subordinate)

Passport4400 B

(Subordinate)

Passport4400 C

(Subordinate)

Passport 6400/7400

PANL

Passport6400/7400Backbone



Primary PANLs on each Passport 4400 unit in the cluster are usually configured on port 2 to support the correct PANL-DCE and PANL-DTE assignments at each PANL terminating point. Four- and eight-port high density modules (HDM) on Passport 4430/50/55 units also support the primary PANLs of units that are immediately subordinate in the cluster hierarchy (HDMs support DCEs). The 2-port and 6-port serial data expansion modules support PANL DCE on Passport 4460 units. Here is a logical view of this topology:

4400Passport PANL

4400Passport PANL

4400Passport PANL

Legend: Primary PANLDTE* Refers to PANL-DTEDCE* Refers to PANL-DCE

A

C

B

E

D

DTE*

DCE*

DTE*

DCE*

DTE*

DTE*

DTE*

DCE*

DCE*

4400Passport PANL

PANLOtherFPs

PANL(ISDN)

Passport (PANL)

PANLOtherFPs

Passport (PANL)

PANLOtherFPs

Passport (PANL)

4400Passport PANL

PANL(ISDN)

PANL(ISDN)

209372-F


Setting Up the PANL

Setting up the PANL involves the following provisioning processes on the Passport 4400 unit:

1 Load the default configurations for the Passport 4400 unit.

2 Configure the WAN port on the Passport 4400 unit.

3 Define the PANL profile on the Passport 4400 unit.

When you have completed provisioning (assuming that you have fulfilled all prerequisites on the Passport network side), the Passport 4400 unit and the Passport network establish the connection.

Prerequisites for the Passport 4400 Unit

The following prerequisites apply to both primary and backup PANLs:

• Install all Passport 4400 unit hardware and the facilities that connect the Passport 4400 unit to the Passport network.

• When you plan the cascaded Passport 4400 units, ensure that there are sufficient ports to support immediately subordinate units and that PANL-DCE and PANL-DTE assignments are correct.

• Identify all network addressing requirements for frame relay-based connections and ISDN-based connections.

Note: Prior to making connections and provisioning services, install and configure all hardware that you require to support all services planned for the Passport 4400 unit. This approach simplifies the process of setting up services.



Passport Network Prerequisites for the PANL

For further information on upgrading FPs, see the following documents:



These prerequisites insure that, when you have finished configuring the PANL on the Passport 4400 unit, the nodes can establish the connection.

Item Prerequisites

Passport switches terminating the PANL from a Passport 4400 unit

Ensure terminating function processors (FP) is processor module 2 (PM2).Provision PANL on FPs that terminate the PANL.

For the direct link and the tunneled frame relay link, provision terminating FPs for frame relay multimedia class traffic service. Your network may also require provisioning FRMUX.

For the ISDN link, provision terminating FPs for channelized mode.

Passport network • Migrate all Passport 6400 nodes in the network to Release 4.2 or higher.

• Migrate all Passport 7400 nodes in the network to Release PCR4.2 or higher.

Releases prior to this do not support PANL.

Note: There are other configuration requirements on the Passport network for frame relay pass-through, virtual circuits to the core routers, LAN interworking, voice services, Passport 4400 cascading, and DNA applications. See the appropriate chapter in this document.

209372-F


Loading Default Passport 4400 Unit Configuration

By loading the default configuration for the Passport 4400 unit, you ensure that you remove any existing provisioning that may conflict with the provisioning you are about to undertake. Default values are the factory settings. You need to load the default values to clear previously provisioned configurations. If the unit is new (that is, factory settings have not been altered), you can skip this procedure.

See Configuring and Operating the Passport 4400 for information on how to load default values.

Configuring the Passport 4400 Unit WAN Port

The primary WAN port can be either frame relay or ISDN.

Configuring the WAN port for Direct Link or Frame Relay Tunneling

Prior to provisioning the PANL profile for a direct link or tunneled link, you must provision the WAN port to support frame relay. The basic steps are:

1 Define the system parameters for frame relay.

2 Define the WAN port parameters.

Observe the following considerations when you define the values for provisioning:

• The numbering plan must be consistent with the plans used across the Passport network and other Passport 4400 units. Consult network engineering personnel for information on the numbering plan for the network.

• Use the primary port on the Passport 4400 unit for the PANL. This primary port is either port 1, 2, or 3, depending on the configuration of the Global Circuit Manager (GCM) and the hardware for the unit. See Configuring and Operating the Passport 4400 for more information.

• For most applications, set the mode to DTE (the Passport 6400/7400 switch or the public frame relay network defines the clock).



• For voice service interworking, link bandwidth must be large enough to accommodate the number of voice channels that the Passport 4400 unit supports and must also include bandwidth requirements for all data traffic. Also, the baud rates must be consistent. See Configuring and Operating the Passport 4400 for information on provisioning these values.

Configuring the WAN Port for ISDN

Prior to provisioning the PANL profile for a primary PANL over ISDN, you must provision the primary WAN port for ISDN connectivity. The basic steps are:

1 Define the port requirements.

2 Define ISDN peer and signaling addressing and subaddressing.

Observe the following considerations when you define the values for provisioning the primary link for ISDN:

• Make sure that you correctly configure the global circuit manager (GCM) on the Passport 4400 unit. The GCM identifies the port that supports the primary WAN link over ISDN.

• You must configure the same ISDN protocol on both the Passport 4400 unit and the FP on the Passport 6400/7400 switch.

• Make sure that you have correct addressing and subaddressing for both the ISDN peer and the signaling channel.

• If the connection uses a leased line through an external modem, define how the ISDN B-channel carries traffic.

Considerations for High Data Rates

On Passport 4460 units, the WAN link will not establish a connection through a serial port if the baud rate is above 134.4 Mb/s. When using a V.35 or V.36 interface, it is recommended that the Passport 6400/7400 use the “Transmit Signal Element Timing (DTE Source)” signal, especially at high data rates.

209372-F


However, the X.21 interface on the Passport 4460 does not currently support the “DTE Signal Element Timing” signal. In this case, use the following table to determine the appropriate maximum cable length for the desired data rate:

Defining PANL Signaling Management

PANL signaling management (MSM) includes the PANL profile and the link characteristics. The basic steps are:

1 Define the MSM profile.

2 Assign a node name to the Passport 4400 (optional).

3 Add the PANL-DTE link information.

When you define the values for provisioning, observe the following considerations:

• Structure the DNA prefix in any way that is meaningful to network requirements (that is, your address plan).

• The numbering plan can be either X121 or E164. The default is X121.

Data Rates

Cable Length (in feet) X.21 Terminated X.21 Unterminated

15 2,048,000.0000 1,024,000

25 2,048,000.0000 400,000

50 2,048,000.0000 200,000

100 1,523,229.2460 100,000

150 1,173,364.6230 70,000

200 954,198.4733 50,000

250 804,020.1005 45,000

300 694,685.6547 38,000

400 546,149.6450 28,000

500 449,943.7570 24,000



• The Passport 4400 unit also uses a DNA suffix that defines the service that is accessible through a specific virtual port. The chapters describing service interworking provide more information on each suffix.

DNA Prefix Numbers

DNA prefix numbers can be arbitrary in a stand alone network. However, in a Passport network, the Passport packet routing system requires that you follow a specific numbering scheme.

For example, the 12-digit DNA prefix 302211770302 can be broken down into the following components:

• 3022 - Data network identification code (DNIC). The ITU-T standards central authority assigns the DNIC to the network.

• 11 - Routing identifier (RID). The RID identifies the subnet of Passport 6400/7400 switches.

• 77 - Module identifier (MID). The MID identifies a Passport 6400/7400 switch in the subnet.

• 0302 - Unique identifier for the Passport 4400 unit. It is common practice to make these numbers meaningful in some way. For example, you can use the logical processor and port number of the physical connection, or Passport node id number.

Further Information

For further information on establishing the PANL between the Passport 4400 unit and the Passport network, see the following documents:





209372-F

41

Chapter 3Backup PANL

This chapter describes the requirements for establishing the backup Passport access network link (PANL) between the Passport 4400 unit and the Passport network. This chapter contains the following topics:

• “Functional Overview of Backup PANLs” on page 41, provides a brief overview of backup PANL configurations

• “Topology for Backup PANLs” on page 44, describes the physical and logical components

• “Setting Up Backup PANLs” on page 52, describes requirements for PANL and provides information on installation and provisioning


Functional Overview of Backup PANLs

Backup PANLs provide link or node redundancy in the event of node or facility failure for the primary PANL. The backup PANL can be any of the following:

• Leased line through external modem

• Public frame relay

• Public ISDN

The backup connection requires a dedicated port on the Passport 4400 unit. For more information on basic PANL function characteristics, see “PANL Functional Overview” on page 23.


42 Chapter 3 Backup PANL

Backup PANL for Non-Cascading Passport 4400 Units

For non-cascading Passport 4400 units, the backup PANL is any of the connection types defined in “PANL Functional Overview” on page 23.

In its simplest configuration, the PANL terminates at the Passport 6400/7400 node that terminates the primary PANL. If the primary PANL for any Passport 4400 unit goes out of service, the backup PANL takes over. The network does not require re-registration of the DNAs for affected Passport 4400 units. If the Passport node that terminates the primary PANL is unavailable for any reason, the Passport 4400 unit cannot send or receive calls over the Passport network.

A more robust configuration terminates the PANL on any other Passport 6400/7400 node that supports PANL. If RID/MID redirection is enabled in the Passport network, the backup PANL supports sending and receiving calls over the backup if the Passport node that terminates the primary PANL is unavailable for any reason.

For more information on RID/MID redirection, see “Network Applications” on page 157.

Backup PANL for Cascading Passport 4400 Units with Link Only Backup

A cascaded configuration with link only backup is the simplest topology and provides a link only backup.

If the primary PANL for any Passport 4400 unit goes out of service, the backup PANL takes over. The network does not require re-registration of the DNAs for affected Passport 4400 units.

If a Passport 4400 unit goes out of service, all subordinate units that depend on that unit for access to the Passport network are isolated and cannot accept or receive calls. The top-level Passport 4400 unit in the hierarchy de-registers the DNAs of the affected units.

209372-F

Chapter 3 Backup PANL 43

Backup PANL for Cascading Passport 4400 Units with Full Node Backup

A cascaded configuration with full node backup is the most reliable topology. This configuration provides both link and node backup and has the following characteristics:

• The primary PANLs follow the hierarchy of the Passport 4400 units (as with a cascaded configuration with link only backup). All primary links access the network over a single primary PANL between the top-level Passport 4400 unit in the hierarchy and the Passport PANL.

• The backup PANLs terminate on a PANL that is on any Passport 4400 unit, or on any Passport 6400/7400 node. The Passport 6400/7400 node can be the same node or any other node that supports PANL.

• RID/MID redirection may or may not be provisioned for the DNAs registered on the primary PANL.

• If a primary link or a node goes out of service, the top-level Passport 4400 unit signals the Passport PANL as to which subordinate Passport 4400 units are no longer available.

The backup PANLs for the unavailable units come into service and register DNAs (including multiple DNAs) on the terminating Passport PANL. If you have provisioned RID/MID redirection for DNAs over the primary PANL, the Passport network redirects calls destined for Passport 4400 end units to the Passport 6400/7400 nodes that terminate the backup PANLs. In this way, two-way call setup remains in service. If you have not provisioned RID/MID redirection, the Passport network cannot redirect calls. In this case, the affected Passport 4400 units can place calls but not receive them.

If a Passport 4400 unit goes out of service, that unit is unavailable and the primary PANLs for each subordinate unit are also unavailable. Each subordinate unit can re-register with the Passport 6400/7400 network over the backup PANL if available. Functionality that is available through RID/MID redirection as described in the preceding paragraph applies.

For more information on RID/MID redirection, see “Network Applications” on page 157.



Topology for Backup PANLs

The topology for backup PANL for a non-cascading Passport 4400 unit and for ISDN are similar to the topologies for the primary PANL. See “Primary PANL” on page 23 for more information.

The remainder of this chapter describes topologies for cascading configurations and for analog PSTN dial backup.

Cascading Passport 4400 Units

For both approaches to cascading, implementation of the Passport 4400 units has the following characteristics:

• Passport 4400 topologies permit cascading to four levels, where the Passport 6400/7400 unit that terminates the PANL is the first level and the top-level Passport 4400 unit is the second level. This arrangement leaves two additional levels for subordinate Passport 4400 units.

• All registered DNAs must be unique. Passport does not allow two DNAs where one is a subset of the other.

• Establish a PANL as described in “Primary PANL” on page 23 through a public switched telephone network (PSTN), an ISDN network, or a public frame relay network.

• Make sure you correctly assign PANL-DCE and PANL-DTE at the termination points of the PANLs.

Other characteristics and requirements for PANL apply. See “Primary PANL” on page 23 for information on interworking for PANL.

209372-F


Cascaded Configuration with Link Only Backup

Here is the topology for cascaded configuration with link only backup:

Passport 4400

Passport 4400

Passport 4400

Passport 4400

Passport 4400

Passport backbone

Legend: Primary PANL Backup PANL

Passport (PANL)

Passport (PANL)

Passport (PANL)

Passport4400 B

Passport4400 D

Passport4400 E

Passport4400 A

Passport4400 C



The implementation of cascaded Passport 4400 units for link backup has the following characteristics:

• Primary and backup PANLs are usually configured on IfIndex2 and IfIndex3 respectively to support the correct PANL-DCE and PANL-DTE assignments at each PANL terminating point.

• Four- and eight-port high density modules (HDM) also support the primary and backup PANLs of units lower in the hierarchy. HDMs support DCEs. However, for cascading requirements, use HDMs for topologies that support full node backup.

209372-F


Passport4400

PANL

PANL

PANL

A

C

B

E

D

DTE

DCE

DTE

DCE

DTE

DTE

DTE

DCE

DCE

Note: DTE and DCE refer to PANL DTE and DCE

DTE

DCE

PANL

PANLOtherFPs

Passport (PANL)

PANLOtherFPs

Passport (PANL)

PANLOtherFPs

PANL(ISDN)

PANL(ISDN)

PANL(ISDN)

Passport (PANL)

PANL


Passport network edge

Passport4400

Passport4400

Passport4400

Passport4400

Passport4400



Cascaded Configuration with Full Node Backup

Here is the topology for cascaded configuration with full node backup:

Passport 4400

Passport 4400

Passport 4400

Passport 4400

Passport 4400


Passport (PANL)

Passport (PANL)

Passport (PANL)

Passport backbone

Passport4400 B

Passport4400 D

Passport4400 E

Passport4400 A

Passport4400 C

209372-F


The implementation of cascaded Passport 4400 units for full node backup has the following characteristics:

• Backup PANLs terminate on Passport 6400/7400 nodes or on other Passport 4400 units.

• Primary PANLs are usually configured on port 2.

• Use four- and eight-port HDMs to support the primary and backup PANLs of subordinate units.

PANL

PANL

PANL

A

C

B

E

D

DTE

DCE

DTE

DCE

DCE

DCE

DTE

DTEDTE

DTE

DTE

DTE

DCE

DCE

DCE

Note: DTE and DCE refer to PANL DTE and DCE

DTE

DTE

DCE

DCE

PANL

PANLOtherFPs

Passport (PANL)

PANLOtherFPs

Passport (PANL)

PANLOtherFPs

PANL(ISDN)

PANL(ISDN)

PANL(ISDN)

Passport (PANL)

Passport4400

Passport4400

Passport4400

Passport4400

Passport4400

PANL

Legend: Primary Backup PANL

Passport network edge

DCE



Analog PSTN Dial Backup

Analog public switched telephone network (PSTN) dial backup is supported between a Passport 4400 unit and a Passport 6400/7400 unit, as well as between two Passport 4400 units. For this application, you use an analog modem between the Passport 4400 unit and the PSTN, and use a matching analog modem with any required converter at the Passport 6400/7400 side:

Information Concerning the Passport 4400 Unit

A Serial WAN Module is used in the Passport 4400 unit’s secondary WAN slot. Configure this port as a backup port to the primary link. You must take into consideration the prioritization of local traffic if the dial backup link operates at a lower link speed than the primary link. This insures that traffic composition can be maintained at the lower bandwidth. You should limit the number of calls (SVCs or SPVCs) that are carried by the backup link so there is sufficient bandwith for the services that you want to maintain during backup situations.

To limit the number of calls on any IfIndex, use the following CLI command:

CLI>define fr line user baseSVCLMI maxNumberOfCalls

Passport 4400

2-wire 2-wire

V.24Modem

V.35 to V.24Converter

Primary LinkOut of Service

V.35 FP

V.24Modem

PANL FP

Passport 4400

Serial WAN

Module

Passport6400/7400

V.35

Cable 1

Cable 2

Cable 3

PSTN

209372-F


<IfIndex> : INTEGER (1..255)<MaxNumberOfCalls> : INTEGER (1..255)

To change the transmit priority of an IfIndex, use the following CLI command:

CLI>define fr port spvcLANData svc txPriority

<ConnectId> : INTEGER (1..65535)<TxPriority> : INTEGER (0..15)

To find the ConnectId numbers, use the following CLI command:

CLI>show fr port spvcLANData base svc configured table

Typically, ConnectId 1 is an SPVC for LAN traffic and ConnectId 2 is for NMS traffic.

PANL is used over the dial backup link as well as the primary link. You can configure the link to operate between 16 Kb/s and 2 Mb/s. However, typical backup link speeds are between 14.4 Kb/s and 33.6 Kb/s. PANL will operate at speeds down to 9.6 Kb/s, but this speed might not be able to satisfactorily carry a voice channel.

Cable 1 in the illustration is typically a V.24 cable, such as the NTAU18AA V.24 to DCE cable.

Configure the modem connected to the Passport 4400 unit as follows:

• Set the modem to auto originate.

• Enter the remote end number into the modem’s memory.

• If the modem has the capability, you should program a secondary number, in case the first number does not answer the call.

• Make sure the modem is configured to start the dialing process as soon as the DTR lead goes high on the Passport 4400 unit’s Serial WAN Module.

• Make sure the modem terminates the call when the DTR lead goes low.

• Enter a DTE inactivity timeout value of about three minutes.

The modem connection to the PSTN is a standard telephone connection. The type of connection depends on the country where the modem is located.



Information Concerning the Passport 6400/7400 Unit

You should use the same manufacturer and model of modem at the Passport 6400/7400 side as used on the Passport 4400 side.

Cable 2 is a V.24 to V24 cable to connect the modem to the V.35 to V.24 converter. The converter is necessary, as the Passport 6400/7400 unit only supports a V.35 FP. The converter can be any third party V.35 to V.24 converter.

Cable 3 is a V.35 cable to connect the converter to the Passport 6400/7400 unit’s interface panel.

The Passport 6400/7400 V.35 FP must be a PM2 FP running PANL and used for the backup link connection. This same FP can also be used for the primary link. The V.35 FP must be used with the V.35 interface breakout panel, to provide a standard V.35 interface. The backup link must connect to the same Passport 6400/7400 unit as the primary link. Some points to consider:

• The Passport 6400/7400 dial backup port must be predefined and idle until the receiving modem answers the call. This condition normally creates alarms, because the port is active but there is no data being transferred. The alarms stop when a dial backup call is in operation.

• The dial backup call is always originated by the Passport 4400 unit.

• Make sure the modem connected to the Passport 6400/7400 unit is set to auto answer.

Setting Up Backup PANLs

Setting up cascading topologies on Passport 4400 units does not require installation or provisioning procedures in addition to those for PANLs to Passport 4400 units in non-cascading topologies.


See “Primary PANL” on page 23 for information on Passport 4400 unit prerequisites for setting up PANLs.

209372-F


Prerequisites in the Passport Network

See “Primary PANL” on page 23 for information on Passport 6400/7400 node prerequisites for setting up PANLs.

See “Network Applications” on page 157 for information on applications using Passport call redirection features.

Further Information

For further information on establishing the PANL between the Passport 4400 unit and the Passport network, see the following documents:






209372-F

55

Chapter 4Interworking for NMS

This chapter:

• Describes the requirements for establishing the virtual circuit between the Passport 4400 unit and the network management core router (NMCR).

• Provides information on setting up the virtual circuits to the NMCR.

• Includes information on establishing the static route to the network management system (NMS).

This chapter contains the following topics:

• “NMCR Functional Overview” on page 56, provides a description of how the virtual circuit to the NMCR works

• “NMCR Topology” on page 57, describes the physical and logical components involved in the virtual circuit to the NMCR

• “Defining the Virtual Circuits to the NMCR” on page 63, provides the following information on installation and provisioning:

— Prerequisites that the Passport 4400 unit and the Passport network must have in place to support connectivity to the NMCR



• “Security Issues” on page 67, provides guidelines for insuring network security for user data and network management


This chapter provides information on setting up the virtual circuits to the NMCR. This chapter also includes information on establishing the static route to the network management system (NMS).


56 Chapter 4 Interworking for NMS

Each virtual circuit can terminate on a single virtual router (with dedicated FRUNI and FRDTE) or a member of a group of multiple virtual routers (with shared FRUNI and FRDTE). The descriptions in this section apply to both network configurations.

NMCR Functional Overview

The virtual circuit to the NMCR corresponds to the network layer of the OSI communications model. Each virtual circuit is an encapsulated IP connection over frame relay from the Passport 4400 unit to the NMCR. The multi-service Passport access network link (PANL) terminates the virtual circuit on Passport frame relay. The NMCR permits the subnet associated with the Passport 4400 unit to route to the NMS subnet.

The virtual circuit to the NMCR supports IP connectivity for network monitoring using the simple network management protocol (SNMP). Typically, the NMS routes through one of the following:

• An IP subnet supported on a Passport 6400/7400 switch

• A frame relay connection supported on a Passport 6400/7400 switch

The NMCR requires one subnet for the FRDTE interface and all Passport 4400 units share a common management subnet on virtual port 4.

You provision the routing between end points for the services (LAN interworking, frame relay, and voice). You do not define the virtual circuit to the NMS (the end-point).

Software Distribution Capabilities

After you have established the virtual circuits to the NMCR and IP, you can set up a software distribution site to download software upgrades directly to the Passport 4400 unit. The software distribution site can be on any of the following:

• NMS workstation

• Any server that routes through the NMCR or a user core router (UCR)

209372-F

Chapter 4 Interworking for NMS 57

NMCR Topology

The virtual circuit consists of two parts. The first part is the PANL that connects the Passport 4400 unit to the network. This part includes the established connections between the Passport 6400/7400 switch with PANL and the Passport 6400/7400 switch that hosts the core router. The second part is the existing Passport network. You establish connectivity from the Passport 4400 unit to the NMCR by defining an SPVC that spans these parts of the connection.

The illustration that follows shows the topology for network management connectivity between the Passport 4400 unit, the NMCR, and the NMS. This high-level view shows that the network configuration is similar for both NMS connectivity over Passport inter-LAN services (ILS) and NMS connectivity over frame relay. The difference is the connection between the NMS and the NMCR. The NMS to NMCR connection is transparent from the perspective of the Passport 4400 unit and there are no special interworking considerations for Passport ILS or frame relay.



Passport 4400

Passport 4400

Passport 4400

PassportBackbone

Passport 4400(PANL)

Passport 4400(PANL)

IPSubnet

Subnet forPassport 4400 units

Legend: PANL Link SVPC to NMCR

Passport(PANL)

Passport(NMCR)

Passport(PANL)

Passport 4400(PANL)

Subnet for NMS

Ethernet orFrame Relay

209372-F


The following logical view shows the connectivity to the NMS over Passport ILS.

Passport (PANL)

Passport (UCR)

Passport 4400

Passport 4400 Subnet NMS Subnet

Virtual Frameror Physical Hairpin

NMSPANL

PANL FRUNI VR/RgPPort2

VR/RgPPort1

EthernetPANLLink

FRDTE

Legend:Virtual Circuit to protocol PortStatic RouteVirtual RouterRemote GroupProtocol Port

VRRg

PPort



The following logical view shows the connectivity to the NMS.

Because the SPVC between the Passport 4400 unit and the NMS supports a specific function, a discussion of provisioning for this connection is included in this chapter.

Passport (PANL)

Passport (NMCR)

Passport 4400

NMSPANL

PANL FRUNI FRUNI FRUNIVR/Rg

PPort1 PPort2

FrameRelay

IPPANL Link

FRDTEFRDTE

Legend:Virtual Circuit to protocol PortStatic RouteVirtual RouterRemote GroupProtocol PortVirtual framer

VRRg

PPort

209372-F


The connection between the Passport 4400 unit and the NMCR has the following characteristics:

• The connection between the Passport 4400 unit and the network is on the communication layer above PANL.

• The internal topology of the Passport network is transparent to the Passport 4400 unit.

• The Passport 4400 unit and the NMS have separate IP subnets.

• The NMS connects to the network through any Passport 6400/7400 switch that supports ILS-based services that are common to the NMCR.

• Each Passport 4400 unit connects to only one NMCR. However, an NMCR can connect to several Passport 4400 units.

• Connectivity to the NMS uses static routes.

In this example, the NMCR is in a separate subnet from the UCR for increased security between network management functions and user data.



Topology for NMS on Mission Critical User Data Networks

The following illustration shows a configuration that supports network management requirements for mission critical user data networks.

Legend:= OSPF

PassportBackbone

North/SouthAmericaAsia Europe

Passport(NMCR)

Passport(NMCR)

Passport(NMCR)

NMSNMSNMS

209372-F


Defining the Virtual Circuits to the NMCR

Defining the virtual circuits to the NMCR involves the following provisioning steps on the Passport 4400 unit:

1 Configuring IP for NMS traffic on the Passport 4400 unit.

2 Setting up an SPVC to the core router.

3 Setting up the static route to the NMS for network management purposes.


The following table summarizes the Passport 4400 unit requirements for supporting connectivity to core routers.

Note: Prior to making connections and provisioning, install and configure all hardware required to support services planned for the Passport 4400 unit. This approach simplifies the process of setting up services.

Item Prerequisite

Established PANLConfigured PANL signaling management (MSM)

• Established PANL. See “Primary PANL” on page 23 and “Backup PANL” on page 41.

• dnaPrefix is available.

Internetworking requirementsIP addressing for NMS traffic on the Passport 4400 unit

For most networks, you should provision NMS traffic and user data traffic on different subnets. This approach increases security.For the Passport 4400 subnet, you need the following addressing information:

• IP address• IP subnet mask

• IP broadcast address




The following table summarizes the Passport network configuration requirements to support connectivity to the NMCR.

Note: There are other configuration requirements on the Passport network for the PANL, frame relay pass-though, LAN interworking, voice services, Passport 4400 cascading, and DNA applications. See the appropriate chapter in this document.

Item Prerequisite

Core router configuration requirements

FRUNI and FRDTE • Configured on Passport 6400/7400 switches that function as core routers, provision FPs to support frame relay user-to-network interfaces (FRUNI) and frame relay data terminating equipment (FRDTE).

• Configure the virtual framer or hard wire the hairpin between the FRUNI and the FRDTE.

Addressing requirements • Determine the data network address (DNA) for the Passport 6400/7400 switch.

• Specify a unique DLCI for each core router connection on the Passport 6400/7400 switch.

• Determine the IP address, IP subnet mask, and IP broadcast address for the Passport protocol port to the NMS.

FP requirements Determine the logical processor (LP) number of the FP on which the SPVC terminates.

NMS requirements

IP addressing • IP address

• IP subnet mask

• IP broadcast address

209372-F


Configuring IP for NMS Traffic

Configuring IP on the Passport 4400 unit includes defining IP characteristics for NMS traffic. The basic steps are:

1 Define IP routing for NMS traffic on the Passport 4400 unit.

2 Define the data link connection type as frame relay.

3 Define routing protocols for each connection.


• The Passport 4400 unit supports each traffic type (NMS and user data) on a different virtual port.

• NMS connectivity does not depend on the mode.

• The IP address is restricted by the range defined by the network address and the subnet mask.

— The first address in the range is the subnet address. (You cannot use the first address for hosts.)

— The last address in the range is the broadcast address. (You cannot use the last address for hosts.)

— All remaining addresses are valid IP addresses for hosts.

• Enable routing information protocol (RIP) for each virtual port and enable RIP globally for the Passport 4400 unit.

• Enable passive RIP for the interface to the NMCR (enable RIP globally).

• Enable inverse address resolution protocol (ARP) for the virtual port that supports NMS traffic.

• For the remoteDna, use the dnaPrefix 101 for NMS traffic on the Passport 4400 unit.



Setting Up the SPVC to the NMCR

You must complete the following:

• Associate each virtual port with the DLCI of the Passport 4400 unit with the DNA of the NMCR.

• Define the frame relay port with a connection type of SPVC.


• Define the SPVC only after you have configured the Passport 6400/7400 unit that hosts the core router in the network.

• The virtual port IfIndex for the connection to the NMCR is always 4. (The virtual port IfIndex for the connection to the UCR is always 2.)

• The remoteNetDLCI is the DLCI on the Passport 6400/7400 switch, which identifies the connection from a Passport 4400 unit (each connection must have a unique DLCI). The Passport 6400/7400 switch always points to DLCI 16 for the connection from the switch to the Passport 4400 unit.

• The svcDNA is the DNA assigned to the core router. The value for svcDNA defines the end-point for the SPVC.

• When you define the frame relay port and an SPVC, define the connection type as master.

Setting Up the Static Route to the NMS


• Associate the virtual port with the IP address of the destination NMS workstation

• Define IP routing specifics for the IP connection

There are no special considerations to observe for provisioning values.

209372-F


Security Issues

For security purposes, assign a separate Passport virtual router for each NMCR and UCR. Virtual routers can be on the same Passport 6400/7400 switch. To ensure optimum security, follow these guidelines:

• On any Passport 4400 unit, the IfIndex for NMS traffic is different from the IfIndex for user data traffic.

• IfIndexes that carry NMS traffic on all Passport 4400 units are in the same subnet as the FRDTE on the NMCR.

• Each IfIndex that carries user data traffic on a Passport 4400 unit is in a unique subnet and do not overlap with the NMCR FRDTE subnet.

Further Information

For further information on establishing the connection between the Passport 4400 unit and the core routers, see Configuring and Operating the Passport 4400 (214372).

For information on Passport 6400 network requirements, see the following documents:



For information on Passport 7400 network requirements, see the following documents:








209372-F

69

Chapter 5User Data LAN Interworking

This chapter describes the requirements for establishing interworking between user data subnets on the Passport 4400 unit and subnets that are accessible through the Passport network.


• “Core Router Functional Overview” on page 70, describes the connection between the Passport 4400 unit and the user core router (UCR)

• “Topology for Connection to the UCR” on page 71, describes the physical and logical components

• “LAN Interworking Functional Overview” on page 73, explains LAN interworking

• “LAN Interworking Topologies” on page 75, describes the physical and logical components

• “Passport 4400 Unit Modes: Routing Versus Bridging” on page 82, covers issues related to selecting either the bridging or routing mode for the Passport 4400 unit

• “Setting up VCs to the UCR” on page 83, provides the following information on installation and provisioning:

— Prerequisites that the Passport 4400 unit and the Passport network must have in place to support LAN interworking

— Overview of the provisioning process for each interworking scenario


• “Setting Up LAN Interworking” on page 87, provides the following information on installation and provisioning:

— Prerequisites that the Passport 4400 unit and the Passport network must have in place to support LAN interworking

— Overview of the provisioning process for each interworking scenario


70 Chapter 5 User Data LAN Interworking



Core Router Functional Overview

The virtual circuits (VCs) to the core routers correspond to the network layer of the OSI communications model.

The VC connects the Passport 4400 unit to the core router. As the topology description in this chapter shows, each VC is an encapsulated IP connection over frame relay from the Passport 4400 unit to the UCR. PANL is the means through which the VC can terminate on Passport frame relay. The core router permits the subnet associated with the Passport 4400 unit to route to other subnets in the network. These other subnets can route through a Passport 4400 unit, a Passport 6400/7400 switch, or a third-party router.

The VC to the UCR supports user data traffic. The connection to the UCR makes LAN service interworking possible.

The UCR requires one subnet for each branch Passport 4400 unit that supports LAN services. The number of IP subnets is equal to the number of Passport 4400 units with interconnected LANs.

You provision routing between end points for the services (LAN interworking, frame relay, voice, and others). You do not define the VC to the end points, whether the end point is an NMS or a workstation on a user subnet.

209372-F

Chapter 5 User Data LAN Interworking 71

Topology for Connection to the UCR

The following illustration shows the topology for connectivity between the Passport 4400 unit and the UCR on a Passport 6400/7400 switch for branch LAN routing. SPVCs (Soft Permanent Virtual Circuits) support branch LAN services on Passport 4400 units: the end points are configured, but the connection route is selected automatically.

Both the NMCR and the UCR can reside on the same switch, either with separate FRUNI and FRDTE resources or with shared resources.

Legend:PANL LinkSPVC to UCREthernet

Passport(UCR)

Passport(UCR)

Passport(UCR)

Passport 4400

Passport 4400(PANL)

Passport 4400(PANL)

IP subnet

IP/IPX subnet

IP subnet

Passport 4400



Here is the logical view of the VC to the UCR:

Note: The logical view does not show complete connectivity to the user subnets. The SPVC between the Passport 4400 unit and the UCR can support several networking and interworking options. Also, a static route to the remote subnet may not be required.

Passport (PANL)

Passport (UCR)

Passport 4400


PANL

PANL FRUNI VR/RgPPort

User Subnet

PANLLink

FRDTE

Legend:Virtual Circuit to protocol PortVirtual Circuit to VCRVirtual RouterRouting Group

VRRg

Subnet

VR

Passport

209372-F


The connection between the Passport 4400 unit and the UCR has characteristics that are similar to those for the VC to the NMCR, with these differences:

• The user subnets connect to the network through any Passport 6400/7400 switch that has IP connectivity to the UCR.

• Each Passport 4400 unit can connect to only one UCR. However, a UCR can support SPVCs to several Passport 4400 units. A Passport network can include multiple UCRs.

• User subnets can route through a Passport 4400 unit, a Passport 6400/7400 switch, or third-party equipment (routers).

• Unlike connectivity to the NMCR (which requires a static route between the NMS and each Passport 4400 unit), connectivity between the Passport 4400 unit and the remote subnet can be static or dynamic.

LAN Interworking Functional Overview

In LAN interworking implementations, the Passport 4400 unit functions as either a router or a bridge. Through the port on the Ethernet base module, Passport 4430, 4450, and 4455 units support one LAN segment with IP and IPX. Passport 4460 units can be configured to support two LAN segments.

From the perspective of the Passport 4400 unit as a branch-level access unit, a typical service mix consists of the following:

• A user subnet or LAN segment connected to the Passport 4400 unit (IP and IPX)

• A subnet for NMS (under IP)

• Additional modules and facilities that support voice traffic

• Frame relay access devices (FRADs) that take advantage of frame relay pass-through

Note: The Passport 7400 switch does not support IPX.



The user subnet is the focus of LAN interworking. The Passport 4400 unit operates under one of the following modes:

• As a router, if the Passport 4400 unit supports a user data subnet

• As a bridge, if the Passport 4400 unit supports a LAN segment to an existing subnet

The subnet or LAN segment connects to the Passport network through the UCR. The UCR functions like any other Passport virtual router with these exceptions:

• You provision the UCR to support LAN traffic from Passport 4400 units.

• The associated protocol ports on the UCR are isolated from NMS traffic, if the network requires this level of security.

The Passport network may include one or more UCRs.

To support bridging on the Passport 4400 unit, you must also provision the UCR with bridge frame routing (BFR). BFR takes the bridged packets from the Passport 4400 unit and routes them to the correct destination.

Internetworking Protocols

For the Passport 6400/7400 switch that serves as the core router, you configure the protocol port that is associated with the subnet for IP and IPX. For connectivity to a Passport 4400 unit user data subnet or LAN segment, the protocol port must support the protocol of the subnet.

The Passport 6400/7400 switch handles routing between the Passport 4400 unit and the far end subnet. The subnet supported by the Passport 4400 unit appears like any other subnet supported by a Passport router or a third-party router.

209372-F


LAN Interworking Topologies

The illustration that follows shows the topology of LAN interworking for the following four scenarios:

• IP and IPX subnets through Passport 4400 units, in which subnets that are accessible through Passport 4400 units exchange datagrams

• IP and IPX subnets through Passport 6400 switches and IP subnets through Passport 7400 switches (virtual routers), in which a subnet that is accessible through a Passport 4400 unit exchanges datagrams with a subnet from a Passport 6400/7400 switch (Passport virtual router)

• IP and IPX subnets through third-party routers, in which a subnet supported by a Passport 4400 unit exchanges datagrams with a subnet that is accessible through a third-party router

• LAN segments bridged through Passport 4400 units, in which the Passport 4400 unit serves as a bridge to extend an existing subnet




The most common interworking scenarios are described in the following subsections:

• “Routed IP and IPX Subnets” on page 77

• “Bridged LAN Segments” on page 81

PassportBackbone

Passport(PANL)

Passport(PANL)

Passport(UCR)

Passport(VR)

IPSubnet

Legend: PANL Link Ethernet Connections

Passport4400

(Router)

Passport4400

(Router)

IPXSubnet

IP or IPXSubnet

IP or IPXSubnet

Router

Passport4400

(Bridge)

Passport 4400

Passport 4400

Passport 4400

209372-F


Routed IP and IPX Subnets

The following illustration shows the logical view of Passport 4400 units functioning as routers with access to either an IP host or an IPX server.

\

In this configuration, both remote subnets access the internetwork through the protocol port that you associate with each subnet, where each subnet has a unique protocol port. This topology is the basic internetworking connection for a remote subnet with access through the Passport 4400 unit.


Passport(PANL)

Passport(UCR #1)

Passport 4400 "A"

Passport 4400 "B"Virtual Framer

or Physical Hairpin

PANL

PANL

IP or IPX Subnet

IP or IPX Subnet

PANL FRUNI PassPort

User Subnets

FRDTE

Legend:PANL Linkvirtual circuit to protocol portethernet

Passport

IPX Server

Server Farm

IP Host



In a typical network, the end-points in the remote subnet access an IP host or IPX server that is reachable through the Passport network. That is, the exchange of data occurs primarily between the remote subnet and the host or server. Data exchange between two remote subnets, with access through separate Passport 4400 units, is less common but is still a viable implementation that supports applications with low traffic demands.

Here is the logical view of Passport 4400 units functioning as routers with access to subnets supported by Passport 6400/7400 switches:

Passport(PANL)

Passport(UCR #1)

Passport 4400 "A"


PANL

IP or IPX Subnet

IP or IPX SubnetPANL FRUNI Pass

Port

User Subnets

FRDTE

Legend:PANL Linkvirtual circuit to protocol portethernet

Passport

IP or IPXSubnet

Server Farm

209372-F


Here is the logical view of Passport 4400 units functioning as routers for connection to LAN subnets through third-party routers:

Passport(PANL) Passport

Passport 4400 "A"

PANL

IP or IPX Subnet

IP or IPX SubnetPANL FRUNI

User SubnetsLegend:

PANL Linkvirtual circuit to protocol portethernet

Passport

IP or IPXSubnet

Server Farm

RFC 1490

Bay



Interworking with subnets off Passport 6400/7400 switches or third party routers is very similar to IP and IPX subnets through Passport 4400 units. See “Routed IP and IPX Subnets” on page 77. These implementations have the following characteristics:

• The Passport 4400 unit subnet can exchange data with any other subnet that is accessible through the Passport network.

• Where interworking occurs between the Passport 4400 unit subnet and the rest of the network, connections best support low traffic demands.

• Applications with high traffic demands may cause congestion on the PANL.

• For increased data security, NMS traffic is placed in a separate subnet.

• For subnets that connect to the network solely through third-party routers, the network does not require a UCR on a Passport 6400/7400 switch. You must configure the third-party routers to provide the function of the UCR.

• For subnets that include a mix of Passport 6400/7400 switches as routers and third-party routers, you can provision the UCR on a Passport 6400/7400 switch.

• If the third-party router is configured for RIP 2.0, configure the Passport 4400 unit to RIP1compatible.

209372-F


Bridged LAN Segments

The following illustration shows the logical view of Passport 4400 units in bridged mode.

Passport (PANL)

Passport 4400

PANL

Bridged IP or IPXLAN Segment

PANL

Legend:PANL Linkvirtual circuit to protocol port

Passport (UCR)

FRUNI PassPort

(BFR)

FRDTE

Passport (PANL)

Passport 4400

PANL

Bridged IP or IPXLAN Segment

PANL



Deploying the Passport 4400 unit in this configuration is useful for topologies that include LAN segments at remote locations, and in LANs that require a flat addressing plan.

The Passport 4400 unit forwards non-local and broadcast traffic on the local LAN segment to the frame relay port on the Passport network using RFC 1490 BFR. The protocol port must be configured for BFR. PANL encapsulates LAN traffic (either IP or IPX) according to RFC 1490 and packets arrive at the Passport node as bridged encapsulated frames.

Even though the packets that arrive at a BFR port are bridged encapsulated, they cannot bridge to the destination. BFR does not bridge the packet but instead sends the packet directly to the routing layer on the UCR for forwarding over Passport virtual networking system (VNS). Other than provisioning the BFR feature on the protocol port, this process is transparent.

Bridging on the Passport 4400 unit supports the IEEE spanning tree protocol, which prevents loops in networks that include bridged LAN segments. The protocol maintains traffic flow if the topology associated with the bridged segment changes. This protocol is an IEEE 802.1d standard and a wide variety of third-party bridges support this standard.

Passport 4400 Unit Modes: Routing Versus Bridging

Early in the planning phase, you must decide which mode to apply to the Passport 4400 unit. The mode is a global setting that defines the Passport 4400 unit as either a router or a bridge. The default mode is bridged. You determine the mode as a function of the LAN topology for user data traffic.

The mode that you select affects, and is affected by, the following LAN considerations:

• IP numbering plan, including conservation and assignment of IP addressing space

• Level of complexity that network administration can incur weighed against network requirements

• Subnet isolation requirements

• Traffic management

209372-F


Changing the mode at a later date in the evolution of the network incurs planning and administration overhead for reassigning IP address space and reprovisioning IP for all nodes associated with the affected Passport 4400 unit.

Setting up VCs to the UCR

Setting up VCs to the UCR involves the following provisioning steps on the Passport 4400 unit:

1 Configuring IP for user data traffic on the Passport 4400 unit.

2 Configuring IPX for user data traffic on the Passport 4400 unit.

3 Setting up an SPVC to each UCR.

Prerequisites for the Passport 4400 unit for UCR

The following table summarizes the Passport 4400 unit requirements to support connectivity to the core routers.

Note: Prior to making connections and provisioning, install and configure all hardware needed to support services planned for the Passport 4400 unit. This approach simplifies the process of setting up services.

Item Prerequisite

Established PANL

Configured PANL signaling management (MSM)

• Established PANL. See “Primary PANL” on page 23 and “Backup PANL” on page 41.

• dnaPrefix is available

Internetworking requirements



Prerequisites in the Passport Network for UCR

The following table summarizes the Passport network configuration requirements to support connectivity to the UCR. Because of the different topologies, connectivity to user subnets lies in the realm of LAN interworking.

IP addressing for user data traffic on the Passport 4400 unit

In most networks, you provision NMS traffic and user data traffic on different subnets. This approach increases security.

For the Passport 4400 user data subnet, you need the following addressing information:

• IP address

• IP subnet mask• IP broadcast address

IPX segment characteristics • Circuit names

• Network numbers

Note: There are other configuration requirements on the Passport network for the PANL, frame relay pass-though, LAN interworking, voice services, Passport 4400 unit cascading, and DNA applications. See the appropriate chapter in this document.

Item Prerequisite


FRUNI and FRDTE • On Passport 6400/7400 switches that function as UCRs, provision FPs to support frame relay user-to-network interfaces (FRUNI) and frame relay data terminating equipment (FRDTE).

• Provision the virtual framer or hard wire the hairpin between the FRUNI and the FRDTE.

Item Prerequisite

209372-F


Configuring IP for User Data Traffic

Configuring IP on the Passport 4400 unit includes defining IP characteristics for user data traffic. The basic steps are:

1 Define IP routing for user data traffic on the Passport 4400 unit.

2 Define the data link connection type as frame relay.

3 Define routing protocols for each connection.

When you define the values for provisioning, observe the following conditions:

• The Passport 4400 unit supports each traffic type (user data and NMS) on a different virtual port.

• The mode under which the Passport 4400 unit operates, either bridging or routing, supports the requirements for user data traffic.

• IP address is restricted by the range defined by the network address and the subnet mask.

— The first address in the range is the subnet address. You cannot use the first address for hosts.

— The last address in the range is the broadcast address. You cannot use the last address for hosts.

Addressing requirements • Determine the data network address (DNA) for the Passport 6400/7400 switch.

• Assign a unique DLCI for each core router connection on the Passport 6400/7400 switch.

• There are no addressing requirements at this time. (Each user LAN has a different subnet - see the user subnet requirements at the end of this table.)

FP requirements Determine the logical processor (LP) number of the FP on which the SPVC terminates.

Protocol requirements No protocol requirements at this time.

Item Prerequisite



— All remaining addresses are valid IP addresses for hosts.

• Enable router information protocol (RIP) for each virtual port and enable RIP globally for the Passport 4400 unit.

• For the remoteDna, use the dnaPrefix 100 to indicate user data traffic on the Passport 4400 unit.

• IP Prioritization: when you set up multiple SPVCs to a Passport 6400/7400 unit, select a priority of 9 or less. If you set the priority to 10 or more, the Passport 4400 unit can transmit frames that are only 128 bytes in length.

Configuring IPX for User Data Traffic

If IPX is bridged, there are no additional considerations for establishing an IPX subnet through a Passport 4400 unit. If IPX is routed, there are additional configuration requirements. See Configuring and Operating the Passport 4400 (214372).

Setting Up the SPVC to the UCR


• Associating each virtual port with the DLCI and the DNA of the corresponding core router

• Defining the frame relay port with a connection type of SPVC


209372-F



• Define the SPVC only after you have configured the Passport 6400/7400 unit that hosts the UCR in the network.

• The virtual port IfIndex for the connection to the UCR is always 2. The virtual port IfIndex for the connection to the NMCR is always 4.

• The remoteNetDLCI is the DLCI on the Passport 6400/7400 switch, which identifies the connection from the Passport 4400 unit (each connection must have a unique DLCI). The Passport 6400/7400 switch always points to DLCI 16 for the connection from the switch to the Passport 4400 unit.

• The svcDNA is the DNA assigned to the core router. The value for svcDNA defines the end point for the SPVC.

• When you define the frame relay port and SPVC, define the connection type as master.

Setting Up LAN Interworking

Setting up LAN interworking requires one or both of the following:

• Provisioning routing for IP and IPX subnets

• Provisioning bridging for LAN segments



Prerequisites for the Passport 4400 unit

The following table summarizes the Passport 4400 unit requirements for LAN interworking.


Item Prerequisite

Established PANL

Configured PANL signaling management (MSM)

• An established PANL. See “Primary PANL” on page 23.

• dnaPrefix is available.

Routed IP and IPX subnets

For each subnet, set up the connection to the core router, as described in “Setting up VCs to the UCR” on page 83.

Bridging LAN segments

IP addressing for user data traffic on the Passport 4400 unit

For each LAN segment off a Passport 4400 unit, you need the following addressing information for the IfIndex:• IP address

• IP subnet mask for the subnet to which the LAN segment belongs

• IP broadcast address for the subnet to which the LAN segment belongs

DLCI for user traffic across the bridge

Unique DLCI assigned to the LAN segment.

209372-F



The following table summarizes the Passport network configuration requirements for supporting LAN interworking.

Provisioning Routing for IP and IPX Subnets

Primary provisioning for routing IP and IPX subnets involves establishing connectivity to the core router. See “Setting up VCs to the UCR” on page 83 for information.

Additional provisioning requirements consist of the following:

• Provisioning IP filtering

• Provisioning optional routing parameters

The following sub-sections identify special considerations for these procedures.

Note: There are other configuration requirements on the Passport network for the PANL, frame relay pass-through, virtual circuits to the core routers, voice services, Passport 4400 cascading, and DNA applications. See the appropriate chapter in this document.

Item Prerequisite


Import and export policies (if needed)

If needed:• Provision RIP for the interface associated

with a Passport 4400 unit subnet.

• Provision OSPF, if needed, for interfaces to subnets within the Passport network.

Bridge frame routing Provisioning BFR on the Passport switch that supports the protocol port.



Prerequisites

See “Prerequisites for the Passport 4400 unit” on page 88 and “Prerequisites in the Passport Network” on page 89.

Provisioning IP Filtering

To reduce traffic over PANL, enable RIP filtering on the Passport 4400 unit.

Provisioning Optional Routing Parameters

For routing to both IP and IPX subnets, set Inverse ARP to match the Inverse ARP setting on the core router. Typically, you enable Inverse ARP.

Provisioning Bridging for LAN Segments

Setting up a bridged LAN segment involves the following provisioning steps on the Passport 4400 unit:

1 Configure the Passport 4400 unit for bridging, including the IP addresses and WAN port mode.

2 Set up the SPVC between the Passport 4400 unit and the UCR.

3 Define optional filtering requirements.

4 Define optional bridging parameters.

Prerequisites

See “Prerequisites for the Passport 4400 unit” on page 88 and “Prerequisites in the Passport Network” on page 89.

Configuring the Passport 4400 Unit for Bridging

Configuring the Passport 4400 unit for bridging consists of defining the IP addresses and the WAN port mode. The basic steps are:

1 Set up the SPVC to the UCR.

2 Define bridging filtering requirements.

209372-F


3 Define bridging parameters.

Setting Up the SPVC to the UCR

For information on special considerations for setting up the SPVC to the UCR, see “Setting Up the SPVC to the UCR” on page 86.

Defining Bridging Filtering Requirements

Defining bridging filtering requirements requires no special considerations over and above good network engineering. You must weigh the traffic loads incurred without filtering against the processing load incurred with filtering.

Defining Bridging Parameters

Defining bridging parameters requires no special considerations over and above good network engineering.

Security Issues

For information on security issues, see “Interworking for NMS” on page 55.

Virtual Router Applications

How you configure virtual routers is a network design and resource consideration. You can define virtual routers in the following configurations:

• As a single virtual router (with dedicated FRUNI and FRDTE)

• As a member of a group of multiple virtual routers (with shared FRUNI and FRDTE)



From the perspective of the Passport 4400 unit, virtual routers in both configurations look identical and there are no differences in setup on the Passport 4400 unit.

When you design networks that involve multiple virtual routers for network management, follow these guidelines:

• Configure only IP on each customer virtual router

• Configure IP on carrier virtual routers

• The carrier virtual router supports both SNMP standard MIBs and enterprise MIBs

• Passport 6400/7400 nodes that you configured with multiple virtual routers connected through frame relay are not in network time sync with the host

Further Information

For further information on LAN interworking between the Passport 4400 unit and the Passport network, see Configuring and Operating the Passport 4400 (214372).

For further information on LAN interworking between the Passport 4400 unit and the Passport 6400 network, see the following documents:

• Passport 6400 Bridging Guide (241-6401-805)


• Passport 6400 IPX Routing Guide (241-6401-820)


Single virtual router Multiple virtual routers

Dedicated FRUNI and FRDTE Shared FRUNI and FRDTE within the router group.

Single protocol port associated with the FRUNI and FRDTE

Up to 512 protocol ports associated with the FRUNI and FRDTE.

Supports IP, IPX, and BFR Carrier router supports IP, and one instance each of IPX and BFR.Customer virtual routers support IP only.

209372-F


For further information on LAN interworking between the Passport 4400 unit and the Passport 7400 network, see the following documents:








209372-F

95

Chapter 6Frame Relay Access Devices

This chapter describes the requirements for supporting frame relay access devices (FRAD) on the Passport 4400 unit. A FRAD is a device with a frame relay network link (such as a branch router, or a DPN-100 device). FRADs use frame relay pass-through service for point-to-point access. This chapter contains the following topics:

• “FRAD Functional Overview” on page 95, describes how FRADs use the frame relay pass-through feature

• “FRAD Topology” on page 97, describes the physical and logical components that create frame relay pass-through for FRADs

• “Implementing Frame Relay Pass-Through for FRADs” on page 100, provides the following information on installation and provisioning:

— Prerequisites that the Passport 4400 unit and the Passport network must have in place to support frame relay pass-through



FRAD Functional Overview

A FRAD can be any device from a third-party vendor that permits access to a remote end-point through a frame relay network. A FRAD can be a terminal server for a group of dumb terminals or a router. An Ethernet router is the typical function of a FRAD.


96 Chapter 6 Frame Relay Access Devices

Connectivity involving FRADs includes the following configurations:

• A device that you connect to the FRDCE port of a remote Passport 4400 unit

• A device that you connect to a frame relay UNI port on a Passport 6400/7400 switch

In the first configuration, FRADs at both the source and destination points are co-located with the Passport 4400 unit. Note that Passport 4430/50/55 units can support up to17 FRADs, and Passport 4460 units can support up to 13 FRADs.

In the second configuration, the destination FRAD connects directly to the Passport 6400/7400 switch (the FRAD may even be another Passport 4400 unit). This configuration typically occurs where frame relay is the only access type required for the branch of the network that the destination FRAD supports.

The FRAD uses the Passport 4400 unit to traverse the Passport network. The connection is a frame relay tunnel from the FRAD at the source to the FRAD at the destination. The FRAD at the destination port is identified by a DNA with a connection to an end-user device that is identified using a data link connection identifier (DLCI).

The FRADs see the connection as a permanent virtual circuit (PVC). That is, the FRAD and the Passport 4400 unit exchange protocol information according to link management interface (LMI) format. The Passport 4400 unit functions as a switch and the FRAD functions as customer premise equipment. In the frame relay context, the Passport 4400 unit functions as the DCE and the FRAD as the DTE.

The connection between the FRAD and the Passport 4400 unit is a PVC. Both ends of the PVC use link management interface (LMI) processes to establish and maintain the connection. The connection from the source to the destination relies on a frame relay switch map that defines the end points of the connection as well as which end initiates transmission. The actual connection across the network (switch to switch) is a Passport switched virtual circuit (SVC).

209372-F

Chapter 6 Frame Relay Access Devices 97

FRAD Topology

The following illustration shows the topology for a typical network that includes FRADs connected through Passport 4400 units.

In this illustration, two of the FRADs connect to Passport 4400 units that in turn connect to separate Passport 6400/7400 switches.

Passport 4400

Passport 4400Passport 4400

PANLLink

PANLLink

Passport4400

FRAD C(Passport

4400)

Passport Passport

Passport

FRAD B

Legend:PANL LinkOther Connections to Network ServicesPVC

Passport4400

LANand EndSystem

PANLLink

Passport4400

FRADA

LANand EndSystem

Passport 4400



The implementation of FRADs in the network has the following characteristics:

• PANL can be direct, tunneled (transparent to the connection), or over an ISDN line.

• The connection between the FRAD and the Passport 4400 unit is a PVC.

• The connection between the Passport 6400/7400 switch at the source and the switch at the destination is an SVC.

From the perspective of the FRAD, the connection from the network side of the source FRAD to the user side of the destination FRAD is a PVC. The FRAD continues to send information as long as it perceives that the connection is up (the destination FRAD is receiving).

Payload Encapsulation

Encapsulation occurs as the original datagram passes through each stage of the path to the destination. Encapsulation toward the switching fabric proceeds as follows:

• End-system transmits IP datagram to the FRAD.

• FRAD encapsulates the IP packet in a frame relay packet.

• PANL inserts the PANL header.

• The Passport 6400/7400 switch replaces the PANL header with a VC header and adds the Passport trunking header according to the protocols in place for the switching fabric.

As the network passes the original datagram to the destination, each stage of the connection removes or replaces the encapsulation until the FRAD at the destination end passes the unencapsulated datagram to the end system.

209372-F


Here is the progression of encapsulation:

FrameRelay

Header

FrameRelayFooter

Passport 4400

Passport 4400

(Includes header,footer, and payload)

FrameRelay

Header

FrameRelayFooter

FrameRelay

HeaderVC

Header

FrameRelay

HeaderVC

Header

FrameRelay

HeaderPANL

Header

IP

IP

WorkStation

WorkStation

FRAD

FRAD

Passport4400(PANL)

Passport4400(PANL)

Passport

Passport

Networkedge

Networkedge

FrameRelay

HeaderPANL

Header

FRHdr

PANLHdr IPFR

hdrFRftr

IPFRhdr

FRftr

FRHdr

PANLHdr IPFR

hdrFRftr

IPFRhdr

FRftr

IP

IPFR header(RFC 1490)



Implementing Frame Relay Pass-Through for FRADs

Implementing frame relay pass-through for FRADs involves the following provisioning steps on the Passport 4400 unit:

1 Configure the appropriate port to the FRAD for frame relay DCE.

2 Define the frame relay switch map for each Passport 4400 unit on each end of the connection.

3 Fine-tune transmission parameters on the Passport 4400 unit.

When configuring FRDCE service with frame relay switch map between a Passport 4400 unit and a Passport 6400/7400 unit, you must set the Passport 4400 unit to master and the Passport 6400/7400 to slave. Traffic Management with rate enforcement enabled allows for correct operation of the configured CIR bandwidth.

The following subsections describe specific considerations when provisioning FRADs over frame relay pass-through.


• Establish the PANL between the Passport 4400 unit and the Passport network. See “Primary PANL” on page 23.

• Connect the FRAD to the appropriate port on the Passport 4400 unit.

• Connect any additional FRADs to the ports on the expansion modules.


Ensure that you have connectivity between the Passport 6400/7400 switch and the Passport 4400 unit over the PANL. See “Primary PANL” on page 23. The switching fabric of the Passport network must also be in place.


209372-F


There are no additional prerequisites specific to implementing FRADs over frame relay pass-through.

Configure the Frame Relay DCE Port

Configuring the appropriate port on the Passport 4400 unit involves setting up required and optional parameters that ensure optimal communication with the FRAD. You configure all Passport 4400 units that connect to FRADs prior to setting up the switch maps.


• Choice of mode depends on customer requirements for the FRAD, as well as other cabling and interfaces on the Passport 4400 unit.

— If you configure ISDN on Port 3 for PANL, the port connected to the FRAD must be provisioned as DCE and the FRAD as DTE.

— If you provision the FRAD in DTE mode, the Passport 4400 unit must be DCE.

• Match the baud rate of the FRAD with the baud rate for the FRDCE port.

Define the Frame Relay Switch Maps

You define the switch map by provisioning DNA and DLCI information on the Passport 4400 unit at each end of the connection. The DNA of the remote Passport 4400 unit defines the destination of the SPVC through the Passport network. The DLCI associated with Port 1 on the Passport 4400 unit defines the FRAD to which packets are routed.

Note: There are other configuration requirements on the Passport network for the PANL, virtual circuits to the core routers, LAN interworking, voice services, Passport 4400 unit cascading, and DNA applications. See the appropriate chapter in this document.



When you define values for provisioning, observe the following considerations:

• The DLCI for port 1 on any Passport 4400 unit must be unique. However, each Passport 4400 unit can use the same DLCIs used on any other Passport 4400 unit. DLCIs have local significance only.

• The DNA is composed of the following values:<dnaPrefix> + <service_suffix> + <slot> + <port>

where:<dnaPrefix> is the DNA assigned to the Passport 4400 unit<service_suffix> is 3 (indicating frame relay)<slot> is the slot for the expansion card (2 or 3 for the 3-slot unit or 2 to 5 for the 5-slot unit<port> is the port on the card

For example:30210414554311

where:<dnaPrefix> is 30210414554<service_suffix> is 3<slot> is 1<port> is 1

Fine-Tune Transmission Parameters

You can fine-tune the parameters related to LMI, which are generic to frame relay on the Passport 4400 unit. Modify these parameters only if you have experience with frame relay network engineering.

Further Information

For further information about establishing FRADS, see Configuring and Operating the Passport 4400 (214372).

209372-F

103

Chapter 7Voice Services Interworking

This chapter describes the interworking of Passport 4400 and 6400/7400 voice services. Voice interworking extends Passport voice access and networking services to branches with network access through one or multiple Passport 4400 units.


• “Functional Overview of Voice Interworking” on page 103

• “Functional Overview of Voice Interworking over ISDN BRI” on page 113

• “Voice Interworking Topologies” on page 117

• “Setting Up Voice Services Interworking” on page 126

• “Further Information” on page 134

Functional Overview of Voice Interworking

Voice services interworking, like other interworking features, takes place over a PANL link between the Passport 4400 and 6400/7400 units. Voice interworking provides the following benefits:

• Dynamic routing, on a per-connection basis, for optimal transport of voice, fax, or data traffic through the network by way of:

— Path Oriented Routing System (PORS) for SVC setup, when data is delay sensitive as is voice data

— Dynamic Packet Routing System (DPRS) for DNA-based addressing


104 Chapter 7 Voice Services Interworking

• Full integration of all voice access platforms

— One common routing table, centrally manageable

— Generic tracing facilities

• Access to a Passport network by means of multipurpose voice platform (MVP) and MVP-enhanced (MVP-E) echo cancellation function processors

• Flexible control over the quality of service for voice & voice band data traffic by means of voice profiles

• Per-call assurance of the source and destination compatibility

• Remote server agent (RSA) and remote server interface (RSI) for access to Passport voice networking call server (VNCS) voice profiles

• CUG validation for RSI/RSA

For details, see the following sections:

• “Protocols Supported in Passport 4400 to 6400/7400 Voice Interworking” on page 104

• “MVP/MVP-E Function Processors Supporting Voice Interworking” on page 108

• “Audio Features” on page 108

• “Call Features” on page 110

• “Call Progression” on page 110

• “Network Addressing Used by Passport 4400 Units” on page 111

• “Voice-Related Connections over the Passport 4400 to 6400/7400 Link” on page 112

Protocols Supported in Passport 4400 to 6400/7400 Voice Interworking

Voice interworking requires both protocol interworking and protocol gateways between the Passport 4400 and 6400/7400 units. The following table lists the protocol-to-protocol arrangements supported by Passport 4400 and 6400/7400 voice interworking.

209372-F

Chapter 7 Voice Services Interworking 105

For more details on protocols supported by MVP/MVP-E FPs, see the following documents:

• Passport 6400 Voice Networking Guide (241-6401-755).


For more details on signaling protocols and interfaces supported by Passport 4400 units, see Configuring and Operating the Passport 4400.

BRI and PRI Voice Compatibility

Passport 4430/4450/4455 Release 3.1.6 (and higher) and Passport 4460 Release 4.1.2 (and higher) contain the Passport 6400/7400 call associated GF table. This allows Passport 4400 units to pass call associated facilities to a Passport 6400/7400 node. (Refer to the Release Notes accompanying future Passport 4400 releases to determine whether there are any updates to the Passport 6400/7400 call associated GF table support.)

Beginning with release 5.0, the Passport 4460 supports ETSI and ISO QSIG protocols on ISDN-PRI interfaces (implemented over T1 or E1 lines) including Basic call, GF call associated messages, and several Supplementary Services consistent with the Passport 6400/7400 features. Primary Rate digital voice support of QSIG implementation supports interoperability with Passport 6400/7400 T1 and E1 MVPe Function Processors as well as the BRI interfaces on the Passport 4400.

Passport 6400/7400 protocols

Passport 4400 series protocols/interfaces E1 CAS

ETSI QSIG

DS1 CAS NIS

ETSI ISDN MCDN

Analog interfaces including FXS, FXO, 2- or 4-wire E&M

X X X X X

Digital CAS interfaces, including T1 and E1

X X X X X

ISDN BRI and PRI ETSI QSIG

X

ETSI ISDN X

X = protocol-to-protocol arrangement supported.



The supported BRI and PRI call associated GF table facilities between the Passport 4400 units (release 5.1 and higher) and the Passport 6400/7400 units include the following:

QSIG Service Name ETSI or EN Standard

QSIG Basic Call ETS 300 172, 3rd Edition

Generic Function (GF) Procedures ETS 300 239, 3rd Edition

Transport of manufacturer specific information ETS 300 239, 2nd Edition

Name Identification ETS 300 238, 2nd Edition

Call Diversion ETS 300 257, 2nd Edition

Path Replacement ETS 300 259, 2nd Edition

QSIG Transit Counter EN 301 301 047/048

Call Offer (CO) ETS 300 361/362

Call Completion ETS 300 365/366

QSIG Segmentation and Reassembly ETS 300 172, Annex ZA (1995)

QSIG Calling/connected name identification restriction

ETS 300 237

QSIG message waiting indicator EN 301 260/255

QSIG centralized voice mail ETS 300 257, ETS 300 239, ETS 301 255 (2nd Edition)

QSIG configurable cause codes

209372-F


The following table shows the BRI and PRI Call Associated GF table compatibility between Passport 4400 releases and the Passport 6400/7400 units.

BRI interface - Passport 44xx Releases 3.1.5, 4.0.1, 4.1.1 and earlier

BRI interface - Passport 44xx Releases 3.1.6, 4.1.2, and later

PRI interface - Passport 4460 Release 5.0 and later

PRI interface - Passport 6400 Releases 4.2, 5.1, and 7.0

PRI interface - Passport 7400 Releases PCR4.2 and later

BRI interface - Passport 44xx Releases 3.1.5, 4.0.1, 4.1.1 and earlier

No No No No No

BRI interface - Passport 44xx Releases 3.1.6, 4.1.2, and later

No Yes Yes Yes Yes

PRI interface - Passport 4460 Release 5.0 and later

No Yes Yes Yes Yes

PRI interface - Passport 6400 Releases 4.2, 5.1, and 7.0

No Yes Yes Yes Yes

PRI interface - Passport 7400 Releases PCR4.2 and later

No Yes Yes Yes Yes

Yes means the voice and call associated facilities will be passed successfully between these products.No means the voice will pass successfully, but the call associated facilities will not pass between these products.



MVP/MVP-E Function Processors Supporting Voice Interworking

Passport 6400/7400 units provide support for voice interworking on the following MVP/MVP-E function processors (FPs):

• 1pDS1Mvp/Mvpe. Provides one DS1 port, capable of processing up to 24 channels. Supports DS1 CAS and ETSI Q.SIG protocols.

• 1pE1Mvp/Mvpe. Provides one E1 port, capable of processing up to 30 channels. Supports E1 CAS and ETSI Q.SIG protocols.

• 1pTTC2mMvp/Mvpe. Provides one TTC2M port, capable of processing up to 30 channels.

For a description of the FPs, see the following documents:



Audio Features

The following table lists the audio features supported by Passport 4400 and 6400/7400 voice interworking. You configure these features under the VoiceProfile and VoiceRoute components on Passport 6400/7400 nodes (on MVP/MVP-E FPs only).

Feature Name Passport 4400 <-> MVP/MVP-E

G.729 CSA-CELP Supported frame size is 20 bytes.

Fax/modem Supported only with Passport 4460 units and:

• Passport 6400 MVP-E FPs at Release 7 or newer.

• Passport 7400 MVP-E FPs at Release PCR4.2 or newer

209372-F


G.729 voice interworking is supported between Passport 4460 Release 4.1 and Passport 6400 releases as follows:

G.729 voice interworking is supported between Passport 4460 Release 4.1 and Passport 7400 Releases PCR4.2 and later (to Passport MVP and MVPe).

Fax demodulation (fax relay) Fax relay supports the following standards and rates with Group 3 fax devices:

• ITU V.27ter, 2.4 Kb/s

• ITU V.27ter, 4.8 Kb/s• ITU V.29, 7.2 Kb/s

• ITU V.29, 9.6 Kb/s

Fax relay is also compatible with Group 3 fax devices operating at “Super G3” rates: 14.4 Kb/s (ITU 4.17) and 33.6 Kb/s (ITU V.34). In this case, the fax data are transmitted at one of the lower rates listed above.

Speech Activity Detection (SAD) Supported.

Echo cancellation Passport 4400 series at 16 msec.

MVP/MVP-E at 32 msec.

Tandem pass through (TPT) Not supported in Passport 4400 and 6400/7400 interworking. TPT must be terminated by the same device at both ends (either Passport 4400 units or MVP/Es). Set TPT to disabled (the default) on ingress and egress of Passport 6400/7400 nodes, and to enabled on intermediate tandem Passport 6400/7400 nodes.

To Passport 6400 MVP To Passport 6400 MVPe

Release 5.11 Release 7.0 Release 5.11 Release 7.0

Yes Yes No Yes

1Tested with 5.1.20 (SSUP #20-BEO1SKB)

Feature Name Passport 4400 <-> MVP/MVP-E



Call Features

The following table lists the call features supported by Passport 4400 and 6400/7400 voice interworking.

Call Progression

Call progression occurs as follows:

1 The Passport 4400 unit accepts the dialed number.

2 Local calls (between stations connected to the local Passport 4400 unit) do not require address resolution through the RSA. The system resolves the dialed number through the egress table.

Feature Name 4400 series <--> MVP/MVP-E

Enbloc Dialing Supported.

Overlap Dialing MVP/MVP-E converts overlap to enbloc before sending to 4400 series units.

Over-ride Directory Number Only available on MVP/MVP-E originated calls. Over-ride Directory Number ignores the dialed digits and routes a call based on a provisioned number. The provisioned number is only used for routing the call and is not sent to the external equipment or the far-end of the connection.

Auto Call Only available on 4400 series unit-originated calls. Auto Call provides streamlined access to a provisioned number - similar to a hot line.

Call Restrictions Ignored. Call Restrictions limits access into the network.

DNA Address Plans X.121 and E.164 are supported.

Accounting Accounting is supported on both ends (for Passport 6400 and Passport 7400) but on the PANL end it is time-based, only. There is no voice accounting on the Passport 4400.

Dynamic Path Update Only supported on MVP/MVP-E end of call.

VNCS DNA-based Dialing Plan Supported.

209372-F


3 For calls to remote stations, the Passport 4400 unit resolves the address as follows:

• The Passport 4400 unit looks up the dialed number in the ingress table for possible out-going numbers.

• If the dialed number is not in the ingress table, the Passport 4400 unit looks in cache for a match against the dialed number.

• If the number is not in cache, the Passport 4400 unit queries the RSA. The RSA looks up the number in the VNCS and returns the destination DNA and the voice profile. The RSA completes CUG validation.

• The Passport 4400 unit stores the DNA for resolved addresses in the RSI cache.

4 When the Passport 4400 unit obtains a DNA against the dialed number, it sets up the call with the remote Passport 4400 or 6400/7400 unit.

5 If the remote end is a Passport 4400 unit, the unit looks up the number in its egress table to ensure that the dialed number is reachable. If the remote unit is a Passport 6400/7400 node, the Passport 4400 unit sends the call to the voice route (Vro) that the DNA addresses in the VNCS of the RSA or in the cache of the Passport 4400 unit.

6 For a call through a remote Passport 4400 unit, if the local Passport 4400 unit cannot obtain address resolution, or if the remote Passport 4400 unit fails to find a match in its egress table, the call fails. For a call through a remote Passport 6400/7400 node, if the voice subroute of the Vro is out of service, the call fails.

Network Addressing Used by Passport 4400 Units

Passport 4400 units use Data Network Addresses (DNAs). Dialed numbers for voice calls are mapped to DNAs using the VNCS database.

To minimize the number of DNAs on a Passport 4400 units (and hence the network), all voice services on a Passport 4400 unit share the same DNA suffix. This DNA suffix is for voice services only and is different from the DNA suffix used for other types of traffic (for example, frame relay).



Voice-Related Connections over the Passport 4400 to 6400/7400 Link

On the network link between the Passport 4400 and 6400/7400 units, the following connections are important to voice interworking:

• DLCI-0 and DLCI-16

— DLCI-0 carries the Q.933 call setups/clears.

— DLCI-16 carries proprietary information between a Passport 4400 unit and a network node. Specifically, for voice applications, DLCI-16 provides the transport layer that carries the end-to-end call messages between a Passport 4400 unit and PANL. These end-to-end call messages are carried as DLCI-16, SAP-X messages, where ‘X’ identifies the voice DLCI instance number.

• DLCI to RSA (VNCS). This is a frame relay call that allows access to VNCS through Remote Server Agent (RSA). For details about the RSA, see Passport 6400 Remote Server Agent Guide (241-6401-765) or Passport 7400 Remote Server Agent Guide (241-7401-765). This DLCI allows queries to the dialing plan database based on the dialed number. If a query is successful, then the following four pieces of information are returned:

— Destination side DNA

— Network parameters

— PORS parameters

— Voice parameters

• DLCIs for voice calls. These DLCIs are dynamic and exist only for the duration of a call. These DLCIs are responsible for carrying the compressed voice and any in-band control signals.

209372-F


Here is the Passport 4400 and 6400/7400 link-voice interworking perspective:

Functional Overview of Voice Interworking over ISDN BRI

PBXs can connect to the ISDN BRI voice module to support the following applications:

• “ISDN BRI to ISDN BRI Tie Trunk” on page 113

• “ISDN BRI to PRI Application” on page 114

• “PRI Tie Trunk Application” on page 115

• “Passport Network and PSTN Application” on page 115

• “D-Channel Signaling” on page 116

ISDN BRI to ISDN BRI Tie Trunk

Passport 4400 units support the ISDN BRI to ISDN BRI tie trunk application. In this configuration, the network sets up calls between ISDN devices that connect to separate PBXs, which in turn connect to Passport 4400 units over ISDN BRI. Both the source and the destination points have this access configuration.

Passport4400unit

PANL

DLCI - 0

DLCIs for voice calls

DLCI - 16

DLCI to RSA (VNCS)



Passport 4400 units provide call setup, recognize the dialed digits to determine the route the call takes, and then route the voice data through the network. When the end-station requests call take down, the associated Passport 4400 unit terminates the call. The Passport 4400 unit transparently passes ISDN D-channel signaling between both end-stations, as both devices are ISDN compatible. This application of D-channel signaling allows support for advanced signaling features at both ends.

ISDN BRI to PRI Application

In this application, the network sets up calls between ISDN devices at the source and destination. This application involves RSI/RSA interworking and Passport 4460 unit/Passport 6400/7400 node interworking (for ETSI QSIG and ETSI ISDN only). The Passport 4400 ISDN BRI ETSI QSIG, or a Passport 4460 unit provisioned for PRI QSIG, interoperates with the Passport 6400/7400 MVP/MVP-E module with ISDN PRI ETSI Q.SIG.

Either the Passport 4400 or 6400/7400 unit:

• Provides call setup

• Recognizes the dialed digits to determine the route the call takes

• Routes the voice data through the network

When the end-station requests call take down, either the Passport 4400 or 6400/7400 unit terminates the call.

Passport 4400 units transparently pass ISDN D-channel signaling between both end-stations since both devices are ISDN compatible. This application of D-channel signaling allows support for advanced signaling features at both ends.

209372-F


PRI Tie Trunk Application

The trunk side of each PBX is physically connected to a Passport 4460 PRI interface. Communication between the two Passport 4460 units is by switched connection over the Passport cloud.

As an example, assume that a telephone user attached to the PBX station at Node 1, intends to call PBX station 1234 at Node 2. To do that, the caller first dials trunk access code 6, and waits for a second dial tone from its PRI module. Next, the caller dials a string of digits that uniquely identify the Passport 4400 unit at Node 2, followed by 1234. Connection is established when the user at station 1234 goes off-hook.

If the call-initiating PBX is connected to a Passport PRI interface, then the destination PBX can be connected to:

• a Passport 4460 unit that has PRI module provisioned as QSIG

• a Passport 4460 or 4430/50/55 unit that has BRI module provisioned either as QSIG or Euro-ISDN

• a Passport 6400/7400 unit that has a PRI module provisioned

Passport Network and PSTN Application

You can combine ISDN BRI to BRI tie trunk applications and ISDN BRI to PRI applications to form a hybrid voice network that supports access to branch office PBXs over ISDN BRI, with access to a central office PBX over Passport 6400/7400 PRI. This application involves RSI/RSA interworking and Passport 4400 unit/Passport 6400/7400 node interworking.

PBX Node 1

PRI PRIPassport

4460

Node 2

4460

PBX



In this application, Passport 4400 units provide call setup, recognize dialed digits to determine the route the call takes, and route voice data through the network. Most calls route to the central office, but calls can also route to end-stations that are either local or on remote Passport 4400 units. Further, the local branches can go off-net to the ISDN PSTN and connect to each other or to facilities outside of the Passport network.

The Passport 4400 unit and the Passport 6400/7400 node at the central office transparently pass ISDN D-channel signaling between end-stations since all devices are ISDN compatible. This application of D-channel signaling allows support for advanced signaling features at both ends.

Passport 4400 units support a dialed digit signaling scheme referred to as enbloc signaling. In this signaling scheme, all dialed digits for a call are in the call setup message. This signaling scheme contrasts with the overlap signaling scheme, which attempts to route calls using a minimum number of digits (for example, two or three digits).

When a Passport 4400 unit receives calls that have been routed by overlap signaling, it converts the calls to enbloc signaling if the unit has voice modules other than only ISDN BRI voice modules (for example, an ISDN BRI voice module and an FXS or T1/E1 voice module installed). If a Passport 4400 unit has only ISDN BRI voice modules, the unit can support overlap and enbloc dialing, depending on how the unit is configured.

D-Channel Signaling

D-channel signaling supports dialed digits only for call setup and tear down, call acceptance, and call transmission. Call setup consists of recognizing that the phone is off-hook and accepting the dialed digits to determine where to route the call. In the case where the source and destination are both ISDN-attached PBXs or ISDN devices, the network transparently passes the remaining D-channel information between the source and destination. The Passport 4400 unit supports ETSI QSIG and Euro-ISDN (ETSI ETS 300 102-1) D-channel signaling for BRI. For PRI, D-Channel signaling can be only QSIG.

209372-F


Voice Interworking Topologies

The following illustrations shows the topology for voice service interworking over T1 and E1 modules:

Passport(PANL)

PassportNetwork

Passport4400

(RSI + PANL)

Passport(RSA + VNCS)

Passport(PANL)

PANL Link

Lines to phone sets, faxs, and PBXs

Passport 4400

Legend:

PBX withPhone sets

and fax

Passport4400(RSI + PANL)

PBX withPhone sets

and fax

Passport 4400



Passport4400

PANLRSIingress/egress

Passport4400

PBX, key systems,sets, or fax

PBX, key systems,sets, or fax

Passport(PANL)

PANL Link

Trunking interfaces andfacilities (network cloud)

Legend:

Passport Passport

PBX

trunks


PANL

MVP/MVP-E

RSAVNCS

209372-F


ISDN BRI to ISDN BRI Tie Trunk Applications

This application has the following characteristics:

• All Passport 4400 units have similar ingress/egress table and RSI requirements.

• PBXs connected over ISDN BRI need an ISDN BRI voice module in the associated Passport 4400 unit.

• Passport 6400/7400 network requirements for VNCS and RSA are the same as those for non-ISDN voice services based on Passport 4400 units.


Passport4400

Passport(PANL)

Passport(PANL)

PANL link

T1/E1 or Serial (V.11 or V.35) link

Lines to phones, faxs, and PBXs

Passport 4400

Legend:

PBX

Passport4400

PBX

ISDNBRI

ISDNBRI

Passport 4400



Passport 4400

RSI PANLingress/egress

RSI PANLingress/egress

Passport 4400

Passport(PANL)

PANL

Trunk interfaces and facilities (network cloud)

Connections to PBXs, end-stations, sets, and faxes

Legend:

Passport

ISDN setsor fax

ISDN BRI

Passport(PANL)

ISDN setsor fax

ISDN BRI

PBX

PBX

PANL

RSAVNCS

PANL

209372-F


ISDN BRI to PRI Application


• The Passport 4400 unit has similar ingress/egress table and RSI requirements.

• The PBX connected over ISDN BRI needs an ISDN BRI voice module in the Passport 4400 unit.

• Passport 6400/7400 network requirements for VNCS and RSA are the same as those for non-ISDN voice services.

Passport(MVP/MVP-E)

ETSI QSIGPassport

(RSA + VNCS)Passport(PANL)

PANL link

Lines to telephones,fax machines, and PBXs

Passport 4400

Legend:

PBX withtelephones

and faxmachines

PBX withtelephonesand fax machines

ISDNBRI

PassportNetwork



Passport 4400

Passport(PANL)

PANL Link

Trunk interfaces and facilities (network cloud)

Connections to PBXs, end-stations, sets, and faxes

Legend:

Passport

ISDN setsor fax

ISDN BRI

PBX

Passport

ISDN setsor fax

ISDN

PRI


PANL

RSAVNCSMVP/MVP-E

PBX

209372-F


Passport Network and PSTN Application


• All Passport 4400 units have similar ingress/egress table and RSI requirements.

• PBXs connected over ISDN BRI need an ISDN BRI voice module in the associated Passport 4400 unit.

• Analog and non-ISDN digital devices connect to the Passport 4400 unit.

• Passport 6400/7400 network requirements for VNCS and RSA are the same as those for non-ISDN voice services based on Passport 4400 units.

• Connection to the PSTN is direct from the PBX.



Passport(MVP/MVP-E)


PBX

ISDNBRI

PBX

ISDNPRI

Passport4400

Passport(PANL)

Passport(PANL)

PANL

Passport 4400

Legend:

PBX

ISDNPSTN

Passport4400

ISDNBRI

Passport 4400

209372-F


Passport 4400

Passport 4400

Passport(PANL)

PANLLegend:

Trunks

Passport(PANL)

ISDN BRI

ISDN BRI

PSTN

ISDNsetsor fax

PANL

Passport

RSAVNCS

PBX

PBX

PBX

PANL

Passport

MVP/MVP-E

ISDNsetsor fax

ISDNsetsor fax

ISDN BRIWAN

module

ingress/egress

PANL

ISDN BRIWAN

module

RSI

ingress/egress

ISDN BRIVoice

module

ISDN BRIWAN

module

PANL

RSI



Setting Up Voice Services Interworking

This section describes some of the issues and required procedures for setting up voice interworking.


• You must establish the PANL between the Passport 4400 unit and then network. See “Primary PANL” on page 23.

• You must provision the VNCS RSI/RSA services prior to establishing a call across the network.

• Fax: if you are using Passport 6400 Release 5.1 or later, or Passport 7400 Release PCR4.2 or later, use the following configuration for optimum completion rate: PBX -> MVP 6400/7400 PANL -> Passport 4460 -> PBX.

On the Passport 4400 unit, there are some protocol issues related to FXO to FXO interworking and connection to a Meridian 1 PBX. See the Release Notes included with your Passport 4400 units for additional information. Note that FXO requirements do not apply to voices services over ISDN BRI.

Note: There are other configuration requirements on the Passport network for PANL, frame relay pass-through, virtual circuits to the core routers, LAN interworking, Passport 4400 unit cascading, and DNA applications. See the appropriate chapter in this document.


209372-F



The following table summarizes the requirements for the Passport network configuration to support voice services interworking.

Item Prerequisite

Remote server agent (RSA) • Must be co-located with VNCS.

• Must have a dedicated DNA to which all Passport 4400 units point.

• Redundancy is recommended.

VNCS • Must have routing plan entries to resolve all anticipated address queries against it from the Passport 4400 unit.

VoiceProfile component The VoiceProfile component of the Passport 6400/7400 unit includes the following parameter values for numbers associated with the Passport 4400 unit:

• voiceEncodingChoice: g729Only for the first choice, none for the second and third choices

• silenceSuppression: on

• modemFaxEncodingChoice: relay for the first choice, none for the second and third choices. Even if you do not plan to process modem and fax traffic, you must configure the first, second, and third choices of the modemFaxEncodingChoice attribute; otherwise, voice services do not function.

• modemFaxRates: for relay encoding, change the default maximum rate to either 7.2 or 9.6 Kb/s. Only MVP-E FPs support V.17 fax calls at the default maximum rate of 14.4 Kb/s. Passport 4400 units only support V.29 fax relay calls up to 9.6 Kb/s.

See “Example of a Passport 6400/7400 VoiceProfile Configured for Voice Interworking” on page 130.

VoiceRoute component Set the following VoiceRoute Interface attributes:

• echoCancellation: on

• tandemPassThrough: disabled



Backwards Compatibility

Passport 4400 units are not compatible with versions of voice networking that do not provide DNA support. Ensure that all references to destination node and component IDs (from earlier versions of voice networking) are removed from the VNCS database.

Setting Up Voice Services on the Passport 4400 Units

Defining voice services involves the following provisioning procedures on the Passport 4400 units:

1 Populate the voice ingress and egress tables.

2 Define voice profiles.

3 Assign voice profiles to channels.

4 Define voice switching parameter profiles.

5 Assign voice switching parameter profiles to channels.

6 Set up the RSI.

The detailed requirements for provisioning differ between analog and digital voice services, but the basic procedures that you follow are the same.

In addition to the above procedures, in order to define PBX voice services over ISDN BRI, you must configure the ISDN BRI connection.

Populate the Voice Ingress and Egress Tables

The voice ingress table can include up to 32 entries (60 entries for Passport 4460 units) for remote numbers that are reachable through the local Passport 4400 unit (that is, for numbers for calls through the network). Entries correspond to the requirements defined in the network numbering plan.

The voice egress table can include up to 32 entries (60 entries for Passport 4460 units) for local numbers that are reachable through the local Passport 4400 unit (that is, numbers that are local to the Passport 4400 unit). Entries correspond to the requirements defined in the network numbering plan.

209372-F


The VNCS must be able to resolve the digits it receives from the Passport 4400 unit so that it can return a correct destination address to the originating Passport 4400 unit. Ensure that the VNCS includes an entry for the received digits.

Define Voice Profiles on the Passport 4400 Units

Voice profiles are important if the Passport 4400 unit supports dialed numbers for either voice only or voice/fax. Voice profiles ensure that the dialed number receives calls with predictable characteristics and requirements. You can define up to 32 voice profiles (60 voice profiles for Passport 4460 units), which you can then assign to each voice channel. Voice profiles on the Passport 4400 unit are different from those on the Passport 6400/7400 switches.

There are 16 voice profile options, accessible through CLI subcommands. The following parameters are mandatory:

• Set bandwidth to continuous.

• Set echo cancel to on.

• Use the default setting for DTMF detection.

For dialed numbers that terminate on fax machines, set the faxDigitizingRate to the correct value (default is 7.2 Kb/s).

If voice quality problems arise, fine-tune the following parameters:

• Jitter

• Echo

• Auto gain control

• Input level gain

• Output attenuation

• Fax and voice digitization rates

• Background

• Compander format

Fine-tuning the settings for these options requires experience in voice networking engineering. Consult network engineering personnel for more information.



Comparison of Passport 4400 Unit and Voice Networking’s VoiceProfile Configurations

A voice networking VoiceProfile is configured within VNCS on a network node and is dynamic on a call-by-call basis.

By comparison, a Passport 4400 unit is configured through SNMP and is static for all voice calls. All voice calls on the specified interface have the same configuration, regardless of the dialed number. However, during end-to-end voice networking call negotiation with a network node, the Passport 4400 unit recognizes and uses attribute values within the VoiceProfile’s LogicalConnectionOptions group.

Interaction Between Passport 4400 Unit and VoiceProfile Attributes

The VoiceProfile associated with a dialed number is defined by two groups of provisionable attributes: LogicalConnectionOptions and FramerOptions. The attributes in the LogicalConnectionOptions group describe and set up a switched logical connection. A unit uses these attributes whenever a call is initiated (regardless of whether it or a Passport 6400/7400 node initiates the call). The FramerOptions group of attributes defines how audio data is carried across a network. When a Passport 4400 unit initiates a voice call to a Passport 6400/7400 node, it ignores the FramerOptions group of provisionable attributes and instead uses its internal configuration.

However, for voice calls from a Passport 6400/7400 node to a Passport 4400 unit, two provisionable attributes belonging to the FramerOptions group (voiceEncodingChoice and modemFaxEncodingChoice) must be set to g729Only and relay, respectively. Otherwise, calls made to a Passport 4400 unit could fail, as initial bandwidth reservation calculations depend on these settings.

Example of a Passport 6400/7400 VoiceProfile Configured for Voice Interworking

Vncs/1 Vp/1setupPriority = 2holdingPriority = 2bumpPreference = bumpWhenNecessaryrequiredTrafficType = voice

209372-F


permittedTrunkTypes = terrestrial satellite tt1 tt2 tt3 ~tt4 ~tt5 ~tt6

requiredSecurity = 4requiredCustomerParm = 4pathAttributeToMinimize = costmaximumAcceptableCost = 1280maximumAcceptableDelay = 100000 msecemissionPriority = 0discardPriority = 1pathFailureAction = reRoutePathoptimization = enabledvoiceRates = rate

encoding min maxg728Only 16.0 kbit/s 16.0 kbit/sg729Only 8.0 kbit/s 8.0 kbit/s

voiceEncodingChoice = first: g729Onlysecond: nonethird: none

silenceSuppression = onsilenceSuppressionFactor = 40%dtmfRegeneration = offdataCallsAccepted = yesmodemFaxRates = rate

encoding min maxrelay 0.0 kbit/s 7.2 (or 9.6) kbit/s

modemFaxEncodingChoice = first: relaysecond: nonethird: none

v17EncodedAsG711G726 = nofaxIdleSuppressionG711G726 = offinsertedOutputDelay = 22 msec

Provisioning Voice Services for Interworking

To establish a call between a Passport 6400/7400 node and a Passport 4400 unit, voice networking provides a Passport 4400 unit with the values provisioned under the following Vncs DirectoryNumber component attributes of the destination:

• voiceProfileNumber

• numberingPlanIndicator

• dataNetworkAddress



The Remote Server Agent (RSA) provides access to the Vncs component from the Passport 4400 unit. For details on the RSA, see Passport 6400 Remote Server Agent Guide (241-6401-765) or Passport 7400 Remote Server Agent Guide (241-7401-765). For PANL provisioning information, see Passport 6400 Multiservice Passport Access Network Link Guide (241-6401-480) or Passport 7400 Multiservice Passport Access Network Link Guide (241-7401-480).

Provisioning Voice Networking for the Passport 4400 Units

Provision the Vncs Dn attributes for each prefix required by the Passport 4400 units.

set Vncs/1 DP/0 Dn/1234567 voiceProfileNumber 1 set Vncs/1 DP/0 Dn/1234567 numberingPlanIndicator x121set Vncs/1 DP/0 Dn/1234567 dataNetworkAddress 30216608410200

Setting Up the RSI on the Passport 4400 Unit

You may define the RSI with a primary RSA and an alternate RSA. If the primary fails, the RSI can query the alternate. In this configuration, each RSA is associated with a unique, co-located VNCS. As a result, both VNCS must have identical entries in their lookup tables for those portions of the tables which support call routing through the network for dialed numbers that Passport 4400 units support.

Note: The destinationNodeId and destinationComponentId attributes are not used by the Passport 4400 units, but they are required by voice networking if DNA addressing is not used.

The dataNetworkAddress attribute contains a prefix and a three-digit suffix. The prefix portion is configured on the Passport 4400 unit. For all calls made to a Passport 4400 unit, the dataNetworkAddress attribute must end with a suffix of 200.

209372-F


The terminating DNA is the DNA that the network plan assigns to the RSA. The originating DNA is the DNA that the network plan assigns to the Passport 4400 unit, plus the suffix “500”, which uniquely identifies the originating point as an RSI.

See “Configuring the Passport 4400 Unit WAN Port” on page 37 for information on settings for the PANL to support voice services.

Configuring the ISDN BRI or PRI Connection

The main requirement for setting up the connections is ensuring that each end of a physical link between the two pieces of equipment is properly configured as either network termination (NT) or terminating equipment (TE). The requirements for clock synchronization determine how you define each end of a physical link.

If the PBX does not connect to a PSTN, the Passport 4400 unit provides the clock source. Define the Passport 4400 unit as the NT and the PBX as the TE, as follows:

Note: You do not populate the RSI as in past releases. When you enable the RSI cache, the RSI automatically populates its cache as it queries the RSA and the RSA returns resolved addresses.

TE(Slave Clock)

ToPassportNetwork

Passport 4400

NT(Master Clock)



If the PBX does connect to a PSTN, the PBX must provide the clock source. This application requires the Passport 4400 unit to operate in TE mode. Check the Release Notes included with your Passport 4400 units to determine if TE mode is supported.

Lastly, configure the protocol on the ISDN BRI interface (ETSI QSIG or ETSI ISDN) or the PRI interface (QSIG). Ensure that the ETSI protocol on the Passport 4400 unit matches the protocol in the Passport 6400/7400 network.

Further Information

For further information about establishing voice services between the Passport 4400 units and the Passport network, see the following documents:


• Reference for Passport 4400 Command Line Interface (CLI) (214371)


• Implementing QSIG on Passport 4460 (214280)

For further information about establishing voice services between the Passport 4400 units and the Passport 6400 network, see the following documents:




NT(Master Clock)

ToPassportNetwork

Passport 4400

TE(Slave Clock)

PSTN

209372-F


For further information about establishing voice services between the Passport 4400 units and the Passport 7400 network, see the following documents:






209372-F

137

Chapter 8Traffic Management

This chapter describes traffic management as it applies to interworking between Passport 4400 units and the Passport 6400/7400 network. This chaptercontains the following topics:

• “Overview of Traffic Management Issues” on page 137, provides a brief overview of traffic management for Passport 4400 interworking

• “Passport Trunk Traffic Management” on page 141, describes traffic management for Passport trunks within the Passport network

• “Passport 6400/7400 PANL Traffic Management” on page 144, describes traffic management requirements for the PANL from the perspective of the Passport network

• “Passport 4400 PANL Traffic Management” on page 146, provides a description of traffic management requirements for the PANL from the perspective of the Passport 4400 unit

• “Transfer Priority Mappings” on page 150, provides a table of how to map transfer priority between Passport 6400/7400 nodes and Passport 4400 units

• “Summary of Traffic Engineering Rules” on page 151

• “Example Configurations” on page 154

Overview of Traffic Management Issues

Traffic may originate at devices supported by Passport 4400 units, or at an access service supported by a Passport 6400/7400 switch. Different traffic management mechanisms apply as data packets travel to or from a Passport 4400 unit, across the PANL, and across the Passport 6400/7400 trunk backbone.


138 Chapter 8 Traffic Management

The following illustration shows the points at which traffic management considerations affect how you should provision services and facilities, both on the Passport 4400 unit and within the Passport 6400/7400 network.

For a full discussion of each of the bubble diagrams, see the appropriate topic:

• “Passport Trunk Traffic Management” on page 141

• “Passport 6400/7400 PANL Traffic Management” on page 144

• “Passport 4400 PANL Traffic Management” on page 146

Traffic management mechanisms are located at the following points:

• In the Passport 4400 unit

• In the PANL service on the Passport 6400/7400 unit

• Within the Passport 6400/7400 trunking system

Passport4400

Passport 4400Passport 4400

Passport4400

Passport6400/7400

Passport6400/7400Passport

6400/7400

Passport6400/

7400 network

Passport4400

PANL trafficmanagement

Passport 6400/7400PANL trafficmanagement

Passport6400/7400trunk traffic

management

209372-F

Chapter 8 Traffic Management 139

In those portions of the network that incorporate Passport 4400 units, traffic management requires the following:

• Careful management of traffic-related priorities. Assign traffic-related priorities as a part of access service provisioning and respect those priorities within transport services.

• Proper sharing of bandwidth on common facilities. Provision committed rates for access services and then respect the committed rates on shared facilities.

Priorities

You provision priorities for traffic at specific points along a connection. You use different priorities for different applications, and you configure those priorities to support customer requirements for delay and importance of data. Three priority types are provisionable:

• “Emission Priority” on page 139

• “Discard Priority” on page 139

• “Transfer Priority” on page 140

Emission Priority

Emission priority determines the order in which an interface transmits a packet onto the link when two or more connections are competing for link bandwidth.

If customer requirements determine that a call must have low delay and low delay variation, provision the connection for a high emission priority. Different emission priorities are implemented by placing the data onto different queues, and using a scheduler to take data from the highest emission priority queue first, then from the next highest queue, and so on.

Passport 4400 units map transfer priorities to emission priorities.

Discard Priority

Discard priority determines the importance of a packet, and the order in which the switch must discard packets when congestion occurs. PANL discards packets from all queues when congestion occurs on any queue. Packet discard is part of the process of clearing congestion on the switch.



On the Passport 4460, if customer requirements determine that packets must not be discarded, provision the connection for high discard priority. If some loss of data is acceptable, then provision the interface with a middle or low discard priority.

Transfer Priority

Transfer priority determines the emission priority queue that the switch uses for a packet. It also determines the routing class of service (RCOS) for a call. You provision transfer priority on a per call basis.

You may want to adjust the txPriority on the Passport 4400 unit for NMS and LAN traffic. The range of values is 0 to 15, where higher values indicate higher priority traffic. You must not change the value for voice services. The default values are:

• LAN = 0

• NMS = 6

• Voice = 11

DE-bit Settings

The Passport 4400 unit sets the discard eligibility bit (DE-bit) in the PANL header on all frames queued for transmission that exceed the CIR (txthroughput) under the following conditions:

• Traffic management is enabled on Passport 4400 unit (rateEnforcement = enabled)

• Traffic management is set not to limit traffic to the CIR (lineEfficiency = enabled)

The traffic manager sets the DE-bit on all frames under its control when these frames exceed the CIR. Because each voice channel has enough allocated bandwidth, the traffic manager does not set the DE-bit for voice traffic. The traffic manager then encapsulates frames in VoFR superframes such that the DE-bit is not visible to the WAN connection. The DE-bit is significant only at the terminating end of the PANL at the Passport 6400/7400 node. DE-bits are transparent to the Passport 4400 unit. Lastly, no provisioning is required for DE-bit handling on the Passport 4400 unit.

209372-F


BECN Response

In conformance with ITU-Q.922, a public frame relay network node sends a backward explicit congestion notification (BECN) when congestion occurs. The BECN indicates that the source of the traffic must reduce its traffic rate.

Upon receiving N frames with BECN = 1 (where N is the parameter consecutiveFrames under fr line network proprietaryService) the Passport 4400 unit reduces its traffic rate by one step. The defined steps are:

• 0.675 times throughput



After receiving N/2 consecutive frames, where BECN = 0, the Passport 4400 unit increases the traffic rate by 0.125 times the throughput.

When the N parameter is the default value of 10, throughput equals the configured CIR and the Passport 4400 unit responds to BECNs on all Netlinks (that is, PANL and RFC 1490 links). Also, there is a configurable lower limit for the rate reduction. If the lower limit is equal to or greater than the configured CIR, then the BECN response flow control is disabled.

Passport Trunk Traffic Management

Passport trunk traffic management refers to Passport trunking features that control traffic flow through the Passport network.

The traffic management mechanisms that you configure on both the Passport 4400 unit and the PANL do not interwork directly with traffic management mechanisms for Passport trunks. The network sees traffic from the Passport 4400 unit as it sees traffic from all access points. Therefore, Passport trunk traffic management must take into consideration the requirements of traffic from all access points.



Here is an overview of the features that provide congestion handling, priority-based queuing, and traffic scheduling:

The switch services the queues according to emission priority and aggregate discard level (that is, the Passport multi-priority system). The aggregate discard level is the highest level in any of the three queues. For example, if the high emission priority queue reaches discard level 2, then the other two queues are also at this discard level.

High emissionpriority

Priorityscheduler

Trash

Discardpackets

InputCompare

Aggregatecurrentdiscard

level

Current three-queue model forPassport 6400/7400

Interrupting emissionpriority

Output

Normal emissionpriority

PORSbandwidthallocation

StarvationMonitor

0

21

Packet discardpriority

209372-F


Passport 6400/7400 trunk traffic management has the following characteristics:

• The starvation monitor only operates on the interrupting queue and only when the link is congested with interrupting traffic. This condition usually does not occur.

• The discard levels for each queue are based on the size of the queue and are at the same percentage in each respective queue.

• For PORS calls, the Passport 6400/7400 switch allocates bandwidth on Passport trunks but does not monitor bandwidth allocation.

• Forward congestion indication (FCI) tagging of frames occurs at the first congestion threshold.

• The amount of memory used for buffers varies with Passport trunk speed.

• For voice calls, the Passport 6400/7400 switch determines the discard priority through a setting on the voice networking call server (VNCS).

• For voice calls, the Passport 6400/7400 switch determines the emission priority through a setting on the VNCS. The PANL transfer priority determines the appropriate emission priority setting.

• The Passport 6400/7400 switch determines the VNCS attributes through the voice profile of the destination address.

• For data calls, the Passport 6400/7400 switch determines discard priority through the signaled discard priority assigned to the call (Normal = 2, High = 1).

• For data calls, the Passport 6400/7400 switch determines emission priority through the signaled transfer priority assigned to the call.

• Network control traffic has a discard priority of 0.

For more information on Passport trunk traffic management, see the following documents:

• Passport Networking Introduction (241-7501-310).

• Passport 7400, 15000, 20000 Networking Overview (241-5701-400)

• Passport 7400, 15000, 20000 Overview (241-5701-030)



Passport 6400/7400 PANL Traffic Management

Passport 6400/7400 PANL traffic management refers to PANL features on Passport 6400/7400 nodes that manage voice and data traffic. Traffic originates from or is destined for Passport 4400 units. The following illustration shows the general process of priority handling, fragmentation, and voice over frame relay (VoFR) multiplexing.

The Passport 6400/7400 switch categorizes incoming traffic by emission priority and queues traffic accordingly. The priority scheduler draws from the priority-based emission queues on a round-robin basis, always giving attention to higher emission priority traffic first. Fragmentation of large data packets reduces delay variation of voice traffic.

High emissionpriority

Priorityscheduler

Fragmentation

ToPassport

4400

Trash

Discardpackets

InputCompare

VoFR MUX

Low emissionpriority

0

1

2

3

Discardpriority

Current four-queue model for Passport 6400/7400

0 1 2 3

Aggregatecurrentdiscard

level

209372-F


When congestion occurs, the Passport 6400/7400 switch discards frames by assessing the discard priority of the incoming frames. The aggregate current discard level represents an overall discard threshold which, when exceeded, discards all traffic with a lower discard priority.

PANL traffic management on the Passport 6400/7400 switch has the following characteristics:

• Passport services queues according to emission priority. The Passport 6400/7400 switch transmits high-emission priority queue frames onto the link first.

• The amount of memory available for transmit buffers depends on the link speed.

• The Passport 6400/7400 switch determines voice discard priority through the VNCS setting.

• Voice traffic is set at emission priority 3.

• For data calls, the Passport 6400/7400 switch determines the discard priority through the signaled value (Normal = 2, High = 1).

• For data calls, the Passport 6400/7400 switch determines the emission priority through the signaled transfer priority. The Passport 6400/7400 switch does not permit data traffic in the emission priority 3 queue, except when the Passport 4400 unit assigns transfer priority 11 to a data stream.

• PANL signaling traffic has a hard-coded discard priority of 0. PANL signaling traffic bypasses the discard priority check at the Passport 6400/7400 switch.

• PANL signaling traffic has a hard-coded emission priority of 2 on emission queue 4.

For more information on PANL requirements, see the following documents:





Passport 4400 PANL Traffic Management

Traffic management on the Passport 4400 unit PANL refers to operational features on PANL on the Passport 4400 unit. Traffic management involves provisioning service access connections to support user service requirements. High quality voice, for example, requires not only the provisioning of voice services, but the allocation of voice traffic to a sufficiently high priority emission queue to minimize transmission delays. The following illustration shows the general arrangement of PANL features on the Passport 4400 unit.

Connectionqueues

Bandwidthshapers

Emissionpriorityqueues

highest=4

Inputtrafficfromappli-

cations

4

2

3

1

0

Classschedulers

Priorityscheduler

Fragmentation

VoFR assembly

queue ToPassport

PANL

Trash

Discardexcesstraffic Bandwidth

allocation

VoiceCAC

Current five-emission-priority modelfor Passport 4400

209372-F


Each connection has its own input queue and an allocated committed information rate (CIR). Bandwidth shapers provide data to any class scheduler based on the class of traffic that is currently in any of the connection queues. “Class” refers to the type of traffic, such as voice or LAN. The highest emission priority queue services the class schedulers until the bandwidth shaper is out of data. Then the next highest emission priority services its class scheduler, and so on. Class is based on emission queue.

On the outgoing side, the priority scheduler drains the emission priority queues. The link fragmentation queues drive the priority scheduler, which is interrupt-driven. An interrupt occurs when more link data is required. An idle link leaves new incoming frames to trigger the whole process. The VoFR assembly queue creates link frames by assembling fragments from the priority queues.

The voice connection admission control (CAC) determines the number of voice calls on the link. CAC reserves bandwidth for each voice call until calls consume the maximum amount of reserved bandwidth. You can provision the maximum reserved bandwidth.



PANL traffic management on the Passport 4400 unit has the following characteristics:

• For software map only, each connection (identified by a DLCI) has its own queue and allocated bandwidth CIR.

• The frame relay equivalent committed burst over 1 second determines the connection queue size.

• The class schedulers process queued packets for the highest emission priority first. The schedulers process queues by packet or weighted round robin modes within a class until the bandwidth shaper either stops (is out of tokens) or is out of data. Then the schedulers process for the next emission priority. This process continues through all emission priorities. The Passport 4400 unit allocates tokens to the shapers based on CIR and outgoing bandwidth every 16 msec (essentially token buckets).

• The Passport 4400 unit can send excess traffic for a given class when all higher priority queues are out of data. This characteristic is provisionable.

• The Passport 4400 unit services excess traffic first by emission priority to all traffic in the given emission priority then by the next lowest priority.

• The priority queues have a maximum of 10 frames ready for emission.

• The link VoFR assembly queue runs priority scheduler, which is interrupt-driven. The assembly queue triggers the schedule for the next fragment.

• If the link is idle, a new frame triggers the transmit process.

• Voice without speech activity detection continuously uses approximately 11 Kb/s per connection.

• The voice channel profile transfer priority determines the voice emission priority.

• PANL signaling traffic from the Passport 4400 unit has a hard-coded emission priority of 4.

• The Passport 4400 unit configures transfer priority for data and voice traffic using a transfer priority of 0 to 11. Voice must have transfer priority = 11. Data traffic must never have a transfer priority = 11 if the unit must also support voice service.

• You can choose the signaled data priority (discard priority) through appropriate provisioning in the VNCS.

• The Passport 4400 unit does not apply a discard priority to outgoing traffic.

• Voice CAC and bandwidth allocation prevent starvation for data by limiting

209372-F


the number of voice calls on the link.

Packet Compared to Weighted Round-Robin

The class schedulers operate in either packet round robin or weighted round robin modes. In packet mode, the scheduler takes a complete packet from a connection queue, then takes a complete packet from the next connection queue, and so on until all queues are empty. In weighted mode, the scheduler uses the CIR value for each connection within a class to determine how to process bytes in a queue.

Multiple PVC Support

Multiple netlinks (PVCs) can be active on a Passport 4400 WAN port, so that both PANL and RFC 1490 can be active on the same physical port. There is no priority of RFC 1490 frames over PANL frames. When you set up this configuration, ensure that you minimize the effects of delay on the quality of voice services.

For multiple PANL connections, the traffic manager sorts the connections by priority. The distribution of connections, either all on the same netlink or all on different netlinks, does not affect the traffic manager. When the total bandwidth that a connection needs is greater than the available bandwidth, the traffic manager sends the higher priority frames in preference to lower priority frames. Within a particular priority, the traffic manager allocates bandwidth in proportion to the requested bandwidth (weighted round robin) on a byte basis. Otherwise, each connection can send a single packet in turn (packet round robin).

Frames on a RFC 1490 connection are not fragmented. Therefore, the maximum transmittable unit (MTU) size of an RFC 1490 link must be small enough so that RFC 1490 frames on a shared physical port do not create delays for voice frames. The default MTU size for an RFC 1490 connection on the Passport 4400 unit is 300 bytes. Ensure that you correctly set a corresponding MTU size at the destination router.



Transfer Priority Mappings

Here is a summary of the transfer priority mapping between Passport 6400/7400 switches in the network and Passport 4400 units:

When a call originates from a service on either the Passport 6400/7400 switch or the Passport 4400 unit, the transfer priority sets the characteristics of the call, as shown in the table above. Passport PANL uses the same mapping for transfer priorities as the Passport FRUNI. For the PANL, voice calls must always use a transfer priority of 11, so that voice traffic has the correct delay characteristics.

You can differentiate traffic streams in terms of delay characteristics and importance, that is, discardability of packets, by arranging streams of traffic with different transfer priorities.

Signaled transfer priority in call setup

Passport trunk queue

Routing metricPassport PANL emission queue

Passport 4400 unit priority queue

not signaled (LAPF traffic) n/a n/a 2 4

11-15 Interrupting Delay 3 3

10 High Delay 3 3

9 High Delay 2 2

6-8 High Delay 1 1

3-5 Normal Throughput 1 1

0-2 Normal Throughput 0 0

209372-F


Summary of Traffic Engineering Rules

Follow these engineering rules when you configure applications that require interworking between the Passport 6400/7400 switch and the Passport 4400 unit:

• “Number of Voice Calls” on page 151

• “Speech Activity Detection” on page 151

• “Emission Queue for Voice Calls” on page 152

• “Discard Priority for Voice Calls” on page 152

• “Minimum Link Bandwidth for LAN Traffic” on page 152

• “Branches for NMS Connectivity” on page 152

• “Voice over Tunneled PANL” on page 153

• “Configurable Link-Level Frame Size” on page 153

• “Additional Considerations for the Passport 4400 Unit” on page 154

Number of Voice Calls

The maximum number of voice calls on a link must not exceed five for each 64 Kb/s increment of link bandwidth. You cannot reconfigure this limit. If SAD is on, the maximum number of calls is still five. However, data traffic may obtain a larger amount of link bandwidth, depending on the amount of speech activity detection that occurs.

Speech Activity Detection

On the Passport 4400 unit, the default setting for speech activity detection (SAD) is enabled (bandwidth = voiceActivated). If you set SAD to disabled (bandwidth = continuous), voice services between two Passport 4400 units incur additional link and CPU overhead.

A single Passport 4430/50/55 unit, with SAD enabled, supports up to 30 combined simultaneous digital and analog voice calls. A Passport 4460 unit, with SAD enabled, supports up to 60 combined simultaneous digital and analog voice calls. If SAD is disabled, the number of simultaneous calls the Passport units can support will be less than 30 for Passport 4430/50/55 units and less than 60 for Passport 4460 units.



Emission Queue for Voice Calls

Only voice calls use the highest emission priority queue on the Passport PANL service. This approach is recommended in a mixed service environment. This implies that voice calls must always use transfer priority 11, which the Passport PANL service maps to the highest emission priority transmit queue. Data calls must always use a transfer priority of less than 11.

The Passport PANL service maps the transfer priority to one of the lower emission priority transmit queues. For information on mapping transfer priority to PANL emission priority, see the following documents:

• Passport 6400 Frame Relay UNI Guide (241-6401-900)

• Passport 7400, 15000, 20000 Frame Relay UNI Summary Card (241-5701-905)

Discard Priority for Voice Calls

Voice calls can have a lower discard priority than data calls on the PANL for traffic in the direction of the Passport 6400/7400 node to the Passport 4400 unit.

Minimum Link Bandwidth for LAN Traffic

You must allocate a minimum amount of link bandwidth for user LAN traffic. Allocating less than this amount for user LAN traffic can result in connection time outs.

In general, the minimum value is approximately 10 Kb/s. Depending on the TCP/IP stack software used for the user LAN application, the minimum value can be greater than 10 Kb/s or less than 10 Kb/s.

Branches for NMS Connectivity

Several factors determine the number of branches that the network management core router (NMCR) supports. These factors include the service mix on the Passport inter-LAN services (ILS) NMCR function processor that runs the FRUNI service and whether the FP is PM1 or PM2.

209372-F


Voice over Tunneled PANL

When operating in a tunneled configuration, the voice quality from the Passport 4400 unit can degrade if the link level traffic information rate (TIR) is less than the physical link speed.

For example, consider the following configuration:

• Link speed is 2 Mb/s

• One voice call is up

• One frame relay DCE call is up, using a CIR of 64 Kb/s

• The link level TIR is 64 Kb/s

If the frame relay DCE port sends a full 64 Kb/s to the link, it transmits at the line rate (that is, at 2 Mb/s) in one burst lasting approximately 31 msec. These transmission characteristics block voice samples from transmission over the link. These characteristics also cause samples to queue until one second has passed and the TIR mechanism allows more transmission to occur. To prevent degradation of voice quality from occurring, set the link level TIR to the same value as the link physical speed when operating the Passport 4400 unit in tunneled mode.

When you configure the Passport PANL in non-tunneled mode, this problem does not occur. There is no requirement to set the Passport PANL TIR to a value that is the same as the link speed.

Configurable Link-Level Frame Size

The link-level frame size is configurable on the Passport 4400 unit. The frame size must take into account the physical link speed, or, if tunneling through a public frame relay, the TIR of the Passport PANL service. The default value on the Passport 4400 unit is 80 bytes. This value is acceptable for a 64 Kb/s link.

A simple rule to follow is to increase the link frame size by 80 bytes for each 64 Kb/s increment of bandwidth on the link. For example, use 160 bytes for a 128 Kb/s link speed, 240 bytes for a 192 Kb/s link speed, and so on. Failure to set the frame size properly causes poor throughput performance (if set too small) or voice quality degradation (if set too large).



Additional Considerations for the Passport 4400 Unit

On the Passport 4400 unit, you can configure the transfer priority for each of the following connection types:

• LAN overlay connection (for LAN data from one Passport 4400 unit to another Passport 4400 unit)

• LAN interworking connection (for LAN data from one Passport 4400 unit to Passport ILS)

• Frame relay (or HTDS) connection for a FRDTE connected to an FRDCE port on a Passport 4400 unit that sets up a call to an FRDCE port on a second Passport 4400 unit

You can configure the discard priority that the Passport 4400 unit signals in the call setup packet to the Passport PANL through the CLI on the Passport 4400 unit. A voice connection is the exception. The voice profile in the Passport 4400 unit sets the discard and transfer priority of a voice connection.

The voice connection admission control (CAC) on the Passport 4400 unit controls the total number of voice calls on a link. CAC reserves bandwidth for each voice call until the maximum amount of bandwidth reserved is exhausted. You determine the maximum reserved bandwidth through provisioning.

Refer to the Configuring and Operating the Passport 4400 (214372) for information on configuring priorities for the various types of connections.

Example Configurations

This section contains two example configurations involving the Passport 4400 unit:

• “Typical Configuration on Passport 4400 Unit” on page 155

• “PANL in Tunneled Mode Operation” on page 156

209372-F


Typical Configuration on Passport 4400 Unit

The following illustration provides an example of services supported on a typical Passport 4400 unit:

In this example, one telephone connects to the Passport 4400 unit. Therefore, you must allocate 11 Kb/s of bandwidth in the voice CAC. The FRDCE supports three calls in progress. Each call uses a different emission priority queue, which you define through provisioning. The LAN traffic has the lowest importance (for example, nightly file transfers) and has the lowest emission priority.

For details on which operator commands to use to set the transfer priorities for a given application on the Passport 4400 unit, see Configuring and Operating the Passport 4400 (214372).

BandwidthShapers and

Class Schedulers

Priority Queues(high emission

priority = 4)

Link toPassport Backbone

DLCI "A"(TP 9)

DLCI "C"(TP 0)

DLCI "B"(TP 6)

Workstation

FRAD

Telephone Voice

Frame RelayDCE

LAN VirtualPort

4

3

2

1

0



PANL in Tunneled Mode Operation

In this example, each Passport 4400 unit connects to the public frame relay network through a 64 Kb/s link. The Passport 6400/7400 switch connects to the network through a 256 Kb/s link. To match the transmission rate at the Passport 6400/7400 switch to the speed of the link to the Passport 4400 unit, the TIR that the Passport 4400 unit signals as part of the staging process must be equal to the link speed of 64 Kb/s.

If the signaled TIR value is greater than the speed of the link to the Passport 4400 unit, the public frame relay network can potentially discard packets because of buffer exhaustion in the public network. With a signaled TIR of 64 Kb/s, the PANL on the Passport 6400/7400 switch applies traffic shaping to limit transmission speed to no higher than 64 Kb/s.

Passport4400 "A"

Link speed = 64 Kb/s

Link speed = 256 Kb/s

Passport 4400

Legend:

PublicFrame Relay

Network

Passport4400 "B"

Passport 4400

Passport4400 "C"

Passport 4400

Passport4400 "D"

Passport 4400

PassportPANL FP

PANL A

PANL D

PANL C

PANL B

209372-F

157

Appendix ANetwork Applications

This appendix describes network applications using data network addresses for Passport 4400 units interworking with Passport 6400/7400 networks. This appendix contains the following topics:

• “Call Redirection in a Passport 6400/7400 Network” on page 157, describes considerations and requirements for using Passport 6400/7400 call redirection services

• “Interworking with Passport 6400/7400 Hunt Groups” on page 163, describes considerations for interworking Passport 4400 units with Passport 6400/7400 nodes in hunt groups

• “Further Information” on page 169, a list of related documents

Call Redirection in a Passport 6400/7400 Network

The call redirection feature in Passport 6400/7400 networks provides call redirection for dynamic packet routing system (DPRS) services. The call redirection server increases the chances that a destination application, such as frame relay or SNA, will be available, by redirecting a call attempt that would otherwise fail because the destination is unavailable or unreachable. The Passport 6400/7400 network supports three types of call redirection:

• Address redirection

• RID/MID redirection

• RID redirection


158 Appendix A Network Applications

For Passport 4400 units interworking with Passport 6400/7400 networks, RID/MID redirection is the key feature. RID/MID redirection permits node-level backup of Passport 4400 units in cascading and non-cascading topologies. Address redirection and RID redirection do not have interworking implications, since these redirection features do not function the same between Passport 6400/7400 nodes and Passport 4400 units. You can apply call redirection to Passport 4400 units in a Passport-only network.

The following subsections describe those aspects of RID/MID redirection that you must consider for interworking configurations. For a complete description of call redirection in Passport 6400/7400 networks, refer to the following documents:



Functional Overview of RID/MID Redirection

RID/MID redirection permits mapping of the primary destination address or address prefix to a RID/MID pair. Redirection lets you establish the primary PANL to one Passport 6400/7400 node and the backup PANL to a second Passport 6400/7400 node. On the call redirection server (CRS) in the Passport 6400/7400 network, you provision the redirection mapping to the RID/MID of the second Passport node. You can use RID/MID redirection with cascading Passport 4400 units in a full node backup topology.

If the destination Passport 6400/7400 node or primary PANL is out of service, the CRS forwards the call to the node with the secondary RID/MID. For redirection to work correctly, the Passport 4400 unit must have registered its address with the final destination call server (FDCR) on the Passport 6400/7400 node identified in the RID/MID redirection. This configuration provides a high level of resilience to node or PANL unavailability.

RID/MID redirection supports calls that originate on a Passport 4400 unit. These calls, once accepted by the Passport 6400/7400 node at the other end of the PANL link, have access to call redirection. On the other hand, a Passport 4400 unit does not provide call redirection locally. Once the Passport 6400/7400 network delivers a call to the destination Passport 4400 unit, further redirection attempts do not take place, even if the final destination is not reachable.

209372-F

Appendix A Network Applications 159

Topology for RID/MID Redirection

Here is a simple network that incorporates RID/MID redirection:

Passport4400

Subnet

Passport 4400

PassportBackbone

Passport4400

Passport(CRS)

Passport(RID1/MID1)

Passport(RID0/MID1)

PANL

Backup PANL

Call Redirection Server

Passport 4400

Legend:

CRS

Passport(RID0/MID2)

RID 0

RID 1

SubnetA B



This example shows the secondary Passport 6400/7400 node in a different RID. Typically, the Passport 6400/7400 node that terminates the backup PANL is in close proximity to the node that terminates the primary PANL. Usually, these nodes are configured within the same RID. However, in some topologies, Passport 6400/7400 nodes in different RIDs may be appropriate, provided requirements for close physical proximity are fulfilled. In this regard, the Passport implementation of RID/MID redirection is flexible. Location of the secondary node determines the length of facilities and number of intermediary nodes.

209372-F


Here is a logical view of RID/MID redirection:

XPANL link

Virtual circuit across the out of service Passport 6400/7400

Connections to access devices

Passport 6400/7400(RID0/MID2)

OtherFPs

PANL

PANL(ISDN)


OtherFPs

PANL

PANL(ISDN)


OtherFPs

PANL

PANL(ISDN)

Out of Service

Passport6400/7400

(CRS)

Passport 4400A

Passport 4400B

Legend:

Passportnetwork

edge

PANL

PANL



Because the node at RID0/MID2 is unavailable, the call request goes to the CRS. The CRS determines if there is a RID/MID mapped to the primary address, and if so, redirects the call. If the node or PANL at RID1/MID1 is also unavailable, or the Passport 4400 DNA is not registered, then the call fails.

Setting Up RID/MID Redirection

Setting up RID/MID redirection involves the following provisioning processes on the Passport 4400 unit:

1 Provision the CRS.

2 Provision the CRS to map the Passport 4400 unit DNA to a secondary RID/MID.

There are no interactions between RID/MID redirection and hunt groups for DPRS services.


Configure the primary and secondary PANLs to terminate on Passport nodes that are appropriate, given the network topology. Keep physical distances between the Passport 6400/7400 nodes and the Passport 4400 unit as short as possible.


Migrate all Passport 6400 nodes in the network to Release 5.1 or higher (releases prior to 4.2 do not support PANL, and releases prior to 5.1 do not support address redirection).

Migrate all Passport 7400 nodes in the network to Release PCR4.2 or higher (releases prior to PCR4.2 do not support PANL).

Note: There are other configuration requirements on Passport 4400 units for frame relay pass-through, virtual circuits to the core routers, LAN interworking, voice services, and Passport 4400 unit cascading. See the appropriate chapter in this document.

209372-F


Otherwise, there are no prerequisites that are specific to RID/MID redirection.

Provision the CRS

For information on determining the number and placement of CRS in the Passport network, refer to the following documents:



Provision RID/MID Redirection

When you provision RID/MID redirection, observe the following considerations:

• DPRS services based on the Passport 4400 unit cannot subscribe to DNA redirection. Address redirection is not available for the destination Passport 4400 unit.

• When you implement this feature, configure the entire Passport 4400 unit for PANL backup through RID/MID redirection.

Interworking with Passport 6400/7400 Hunt Groups

A hunt group in a Passport 6400/7400 network is a single data network address (DNA) that represents a group of service DNAs. A Passport 4400 unit can originate calls to a hunt group DNA or directly to a service DNA that is part of a hunt group. However, a Passport 4400 unit cannot be a member of a hunt group, since it cannot negotiate a call setup failure with the hunt group server.

Note: There are other configuration requirements on the Passport network for frame relay pass-through, virtual circuits to the core routers, LAN interworking, voice services, and Passport 4400 unit cascading. See the appropriate chapter in this document.



For more information on hunt groups in a Passport 6400/7400 network, see the foillowing documents:



Functional Overview of Interworking with Hunt Groups

When a call that originates from a Passport 4400 unit goes to a hunt group DNA, the hunt group server forwards the call to an eligible hunt group member. A member can be any of the following:

• Frame relay service

• SNA DLR

• SNA APPN

If no eligible member of the hunt group is available to take the call, the network sends the call for redirection. Call redirection can be to any other DNA in the Passport 6400/7400 network, including another hunt group.

DPRS services based on Passport 4400 units cannot be members of a hunt group.

209372-F


Topology for Hunt Groups

The following illustration shows a Passport 6400/7400 network with a hunt group. Observe how the network does not route the call through the HGS. The network can route the call to the HGS, but not to the hunt group DNA.



Passport4400

Passport 4400

Passport 6400/7400

Passport6400/7400BackbonePassport 4400

Primary PANL

Direct connection to destination DNA

Hunt Group Server

Hunt Group Member

Legend:

EndPoints

EndPoints

EndPoints

EndPoints

Passport 4400

Subnet

Passport 6400/7400

(PANL)

Passport6400/7400

(HGM)

Passport6400/7400

(HGM)

Passport 6400/7400

(HGS)

Subnet

Passport6400/7400

(HGM)

Passport6400/7400

(HGM)

HGS

HGM

209372-F


Here is a logical view of a Passport 6400/7400 network with a hunt group:

PANL link

Logical connections within the hunt group

Direct connection bypassing the hunt group DNA

Passport6400/7400

(PANL)

OtherFPs

PANL

PANL(ISDN)

Passport 6400/7400(HGM)

OtherFPs

PANL

PANL(ISDN)

Out of ServicePassport

6400/7400(HGS)

Legend:

Passportnetwork

edge

Passport 6400/7400

(CRS/HGM)

Passport(HGM)

EndPoints

Passport 4400

PANL

Passport 4400

PANL

End points



Setting Up Hunt Groups for Passport 4400 Access

When you configure Passport 4400 units and hunt groups in a Passport 6400/7400 network for interworking, observe the following requirements:

• A Passport 4400 unit cannot be a member of a hunt group.

• A Passport 4400 unit can be accessed through a hunt group member, as long as the access is not through the hunt group’s DNA.


There are no prerequisites that are specific to interworking with hunt groups.


Migrate all Passport 6400 nodes in the network to Release 5.1 or higher (releases prior to 4.2 do not support PANL and releases prior to 5.1 do not support hunt groups and address redirection).

Migrate all Passport 7400 nodes in the network to Release PCR4.2 or higher (releases prior to PCR4.2 do not support PANL).

Otherwise, there are no prerequisites that are specific to hunt groups in a Passport 6400/7400 network.

Note: There are other configuration requirements on Passport 4400 units for frame relay pass-through, virtual circuits to the core routers, LAN interworking, voice services, and Passport 4400 unit cascading. See the appropriate chapter in this document.

209372-F


Further Information

For further information on call redirection and hunt groups, see the following documents:







209372-F

171

Index

Aaggregate discard level

Passport trunk TM characteristics 142

Bbandwidth allocation

voice services 129

BFR, see bridged frame routingbridged frame routing 82

bridging filtering 91

bridging modecriteria for using 82

Ccustomer support 16

DDCE mode 37

DNA suffix 40core routers connectivity 65, 86

dnaPrefix 65, 86defining 39

DTE mode 37

Eecho cancellation

voice services 129

encapsulationFRAD over frame relay pass-through 98

FFRAD

and frame relay pass-throughconnection characteristics 96, 98definition 95frame relay DCE port 101network connection configurations 96transmission parameters 102

frame relay access device, see FRADframe relay DCE port

FRAD 101

Frame Relay multimedia class trafficupgrade requirements for PANL 36

frame relay pass-through

Gglobal circuit manager

WAN port for ISDN 38

IifIndex

support for different ILS traffic types 65, 85

interworking featuressummary 19–21

invARP 65

IP addressingaddress calculations 65, 85

ISDN addressingWAN port for ISDN 38

ISDN BRI voice servicessee voice services, ISDN BRI


172 Index

ISDN BRI, D-channel signaling 116

ISDN protocolsWAN port for ISDN 38

ISDN, ISDN BRI to ISDN BRI tie trunk applications 119

ISDN, ISDN BRI to PRI application 121

ISND, Passport network and PSTN application 123

LLAN interworking

optional parameters for IP/IPX subnets 90Passport 4400 modes 74protocols 74typical user LAN configuration 78

Mmode

bridging or routing support user LAN traffic 85

NNetwork addressing 111

network addressing 111

network securityconnectivity to core routers 67, 91NMS subnets 67user LAN subnets 67

NMS subnetsnetwork security 67

numbering planPassport network 37

PPANL

benefits 18characteristics over ISDN 28–29configurations 25description 23–24direct link 25–26

general description 18over ISDN 28–29standards 23tunnelled link characteristics 27

PANL backupcascading Passport 4400 units (full node) 43cascading Passport 4400 units (link only) 42non-cascading Passport 4400 units 42overview 41topologies 44

cascading Passport 4400 units 44

PANL interface 23

passive RIP 65

Passport 4400 unitbenefits 17physical communication levels 24physical interfaces 24

Passport networknumbering plan 37

PM2upgrade requirements for PANL 36

portsPANL 37

PRI tie trunk application 115

product support 16

RremoteNetDLCI

core router connectivity 66, 87

RIP 65, 86, 90

routing modecriteria for using 82

RSAterminating DNA 133

RSIprimary and alternate 132

Ssecurity, see network security

209372-F

Index 173

servicestypical service mix 73

SPVCcore router

virtual ports 66, 87core router connectivity 66, 87core routers

when to configure 66, 87

subnet overlapcore router connectivity 67

subnetsfor NMCR 56for UCR 70

support, Nortel Networks 16

svcDNAcore router connectivity 66, 87

Ttechnical support 16

traffic managementapplication points 138discard priorities 139emission priorities 139general requirements 139Passport 4400 PANL TM characteristics 148

class schedulers 149Passport 4400 PANL TM overview 146Passport PANL TM characteristics 145Passport PANL TM overview 144Passport trunk TM characteristics 143

aggregate discard level 142Passport trunk TM overview 141transfer priorities 140

transfer priorityvoice services 140

UUCR, see user core router 74user core router

characteristics 74

user LAN subnetsnetwork security 67

Vvirtual circuit

consists of 2 parts 57NMCR 56

voice egress tablevoice services 128

voice ingress tablevoice services 128

voice interworking, functional overview 103

voice interworking, protocol-to-protocol interworking 104

voice quality problems 129

voice service interworkingPANL link configuration 38

voice servicesbandwidth allocation 129call progression 110DTMF detection 129echo cancellation 129resource considerations

disabling cache 111transfer priority 140voice egress table 128voice ingress table 128voice quality problems 129

voice services, audio features 108

voice services, backwards compatibility 128

voice services, call features 110

voice services, call progression 110

voice services, Defining voice profiles on the Passport 4400 129

voice services, DLCI connections 112

voice services, ISDN BRIconfigure ISDN BRI connection 133set up 128


174 Index

voice services, Passport 4400 and VoiceProfile attributes 130

voice services, populating the voice ingress and egress tables 128

voice services, setting up on the Passport 4400 128

209372-F


Address comments to:

Manager, Technical Publications

Nortel Networks

4401 Great America Parkway

Santa Clara, CA 95054 U.S.A.

U.S.A.

© 2003 Nortel Networks

All rights reserved

Information subject to change without notice

Publication: 209372-F

Date: November 2003