Ops Manual

Passport 4400
Operators Manual
Part Number 800-1952-20, Rev. A
June 1998
Notice of Filing Declaration of CE Conformance (for International sales) A Declaration of CE Conformance is on file at the Nortel addresses shown below. The declaration lists the models described in this manual. If the unit carries the CE mark, this declaration certifies that it meets the specific EMC standards and safety (LVD) standards required for CE marking. If the product is a module, the module is CE-compliant only if it is placed in a CE-marked base unit. Nortel MICOM Communications Corp. 4100 Los Angeles Avenue Simi Valley, California 93063-3397 U.S.A. (805) 583-8600 Nortel MICOM Communications Corp. (Europe) Ltd. The Granary Tongham, Surrey GU10 1DW England, UK 44 1252 781 777
Any units not carrying the CE approval are not CE-compliant. Modules placed in these units may not meet emission standards for CE compliance.
Notice NORTEL CONFIDENTIAL: The information contained in this document is the property of Nortels Except as specifically authorized in writing by Nortel, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation, and maintenance purposes only.
Notice Specifications, tolerances, and design characteristics described in this manual are subject to change without notice.
ii
Contents
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix How This Manual is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Acronyms Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Overview 1
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Benefits of Passport 4400 Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Passport 4400 Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Magellan Passport Access Network Link (MPANL) Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 MPANL and Switched Permanent Virtual Circuits (SPVCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Passport 4400 Network Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Service Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Passport 4400 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample Passport 4400 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 1-6 1-6 1-7 1-7 1-9
iii
Getting Started 2
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Adding a Passport 4400 to a Passport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Step 1: Configure the MPANL Service on the Passport Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Step 2: Configure Core Router Functionality on the Passport Switch . . . . . . . . . . . . . . . . . . . . . . 2-3 Step 3: Provide Network Management Workstation Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Step 4: Install the Passport 4400 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Step 5: Load Factory Default Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Step 6: Provision Passport 4400 Node and MPANL Link Parameters . . . . . . . . . . . . . . . . . . . . . . 2-14 Step 7: Provision Passport 4400 ILS Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 Step 8: Provision User Subnets and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27 Provisioning a T1 or 56k CSU Primary WAN Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Network Administration 3
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Identifying the Passport 4400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Assigning User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Setting CLI Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Managing System Memory Banks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Using System Rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 Setting the System Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Enabling and Setting Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Taking a Port Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15 Monitoring Passport 4400 System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 Monitoring Passport 4400 Network Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
iv
System Utilities 4
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 TFTP Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Upgrading to Release 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 TELNET Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 System Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Reset Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Ping Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
LAN Services 5
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 LAN Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Provisioning LAN Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Provisioning Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Provisioning IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Provisioning IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Monitoring LAN Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Frame Relay Services 6

Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Provisioning Guidelines for Frame Relay Pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Provisioning Procedure for Frame Relay Pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Defining Multiple Frame Relay Switch Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Defining Optional Frame Relay PVC and SVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Defining Optional Frame Relay System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Defining Optional Frame Relay Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19 Defining Optional Frame Relay Virtual Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24 Frame Relay Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
HDLC Transparent Data Services 7

Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 HTDS provisioning procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
ISDN Services 8
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Passport 4400 Circuit Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 ISDN Provisioning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Provisioning ISDN as the Primary WAN Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Provisioning ISDN as the Backup WAN Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 Adding an Additional ISDN Backup Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 Optional ISDN Dial Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13 Optional ISDN Physical Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17 ISDN Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Managing Primary and Backup Links (GCM) 9

Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Passport 4400 Global Circuit Manager (GCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
GCM Default Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Provisioning Serial WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the WAN Port Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Primary or Backup Serial Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-Configuring a Serial Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 9-4 9-5 9-6 9-7
Primary and Backup Link Switching and Timing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Modifying GCM Switching Delay, Switching Type and Timer Status Settings . . . . . . . . . . . . . . 9-8 Modifying GCM Timer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
vi
Traffic Management 10
Whats In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 -1 Passport 4400 Traffic Management Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 -2 Viewing Traffic Management Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 -3 Defining Traffic Management Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 -7
Trap Messages A
System Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 MPANL Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 RSI Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 TFTP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 Bridging Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Frame Relay Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8 VNET (Voice 2.0) Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 T1/E1 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10 GCM Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13 ISDN Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
vii
viii
About This Manual

This manual describes how Passport 4400 access devices contribute to services provided by Passport networks and extend those services to small branch offices. It also explains how to set up the Passport 4400, download software from a TFTP server, and provision the Passport 4400 for network management services and user services. This manual is intended for anyone responsible for installing or upgrading the Passport 4400 or its software components, or requiring detailed information about provisioning and configuring the unit. It is assumed that the reader of this manual has a basic understanding of wide area networking, Passport systems, and the user services provided by the Passport 4400.
How This Manual is Organized

A summary of the content of each chapter of this manual is given below. Chapter 1, Overview, gives a brief description of the features, services and benefits that the Passport 4400 brings to an existing Passport network. The unique characteristics of the system architecture of the Passport 4400 are discussed. An example of a Passport 4400-based network is shown. Chapter 2, Getting Started, describes the tasks and procedures that are required to install and bring up a new Passport 4400 on a Passport network. Chapter 3, Network Administration, describes the monitoring and administrative functions that a network manager or administrator can perform using the Command Line Interface (CLI) of the Passport 4400. Topics include assigning user privileges and passwords, naming Passport 4400 units, configuring CLI port parameters, managing system memory banks, using system rollback, activating and assigning system traps, and taking a port offline. Chapter 4, System Utilities, explains the TFTP software download procedure for the Passport 4400. It also covers TELNET access, the system reset features of the unit, and the Ping utility. Chapter 5, LAN Services, describes the features, provisioning procedures and monitoring capabilities of the Passport 4400 in LAN environments. Chapter 6, Frame Relay Services, describes the features, provisioning procedures and monitoring capabilities of the Passport 4400 in frame relay networks.
ix
Passport 4400 Operators Manual
About This Manual
Chapter 7, HDLC Transparent Data Service, describes the features and provisioning procedures for applications involving the transfer of legacy data across a frame relay network. Chapter 8, ISDN Services, describes the use and configuration of ISDN as a primary or backup WAN link. Chapter 9, Managing Primary and backup Links (GCM), describes the backup options for the primary WAN link (Port 2) on the Passport 4400, and explains how the Global Circuit Manager controls the switchover from the primary port to the backup port and back to the primary port. Chapter 10, Traffic Management, describes the Passport 4400 traffic management methods, how to enable traffic management on the Passport 4400, and how the various traffic management parameters affect the flow of traffic out of the Passport 4400. Appendix A, Trap Messages, contains a list of Passport 4400 trap messages and their meanings.
Related documents
The following documents are relevant to Passport 4400 devices and Passport systems. If you are installing Passport 4400s for the first time, it is recommended that you refer to this set of documents in the order listed. 241-7501-500 241-7001-210 800-1951-20 800-1953-20 800-1952-20 241-7001-803 241-7001-804 241-7001-802 241-7001-300 800-1950-20 241-7001-410 241-7001-180 800-1943-20 800-1944-20 241-7001-340 Passport 4400 Interworking Description Magellan Passport Access Network Link User Guide Passport 4400 Hardware Installation Manual Passport 4400 Supplement for R2.0.0 (Release Notes) Passport 4400 Operators Manual Passport IP Routing Guide Passport IPX Routing Guide Passport Frame Relay DTE Access User Guide Passport Frame Relay UNI User Guide Passport 4400 CLI Command Reference Passport Voice Networking User Guide Passport Remote Server Agent User Guide Passport 4400 Analog Voice Modules User Guide Passport 4400 T1 and E1 Access Modules User Guide Passport Frame Relay ISDN Switched Access User Guide
About This Manual
Conventions
There are a number of documentation conventions you should know about. 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. 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. If you do not make a choice, a default ON is assumed.
...
Three dots in a command indicate that the parameter may be repeated more than once in succession.
The term absolute pathname refers to the full specification of a path starting from the root directory. Absolute pathnames always begin with the slash ( / ) symbol. A relative pathname takes the current directory as its starting point, and starts with any alphanumeric character (other than /).
xi
About This Manual
Acronyms Used in This Manual

ARP BRI CIR CLI CUG CVM DCE DLCI DNA DSP DTE EIR FP FRAD FRCM FRNNI FRS FRUNI GCM HDLC HTDS ICM IE ifIndex ILS IP IPX ISDN LAN LAPD LDM LMI MAC MIB MMTC MPA MPANL Address Resolution Protocol Basic Rate Interface Committed Information Rate Command Line Interface Closed User Group Clear Voice Module Data Circuit Equipment Data Link Connection Identifier Data Network Address Digital Signal Processor Data Terminal Equipment Excess Information Rate Function Processor Frame Relay Access Device Frame Relay Circuit Manager Frame Relay Network-to-Network Interface Frame Relay Service Frame Relay User-to-Network Interface Global Circuit Manager High-Level Data Link Control HDLC Transparent Data Services ISDN Circuit Manager Information Element Interface Index Inter-LAN Switching Internet Protocol Internetwork Packet Exchange Integrated Services Digital Network Local Area Network Link Access Procedure on the D-channel Legacy Data Module Local Management Interface Medium Access Control Management Information Base Multimedia Traffic Classes Magellan Passport Access Magellan Passport Access Network Link
xii
About This Manual
MSM NAC NMCR NMS NSP PAD PBX PORS PPA PRI PVC RFC RIP SIMM SNMP SPVC SPX SVC TFTP TP TUVM UCR UNI VPM VPN WAN
MPANL Switch Map Network Adapter Card Network Management Core Router Network Management System Network Service Provider Packet Assembler/Disassembler Private Branch Exchange Path Oriented Routing System Physical Point of Attachment Primary Rate Interface Permanent Virtual Circuit Request for Comments Routing Information Protocol Single In-line Memory Module Simple Network Management Protocol Switched Permanent Virtual Circuit Sequenced Packet Exchange Switched Virtual Circuit Trivial File Transfer Protocol Transfer Priority Turbo Universal Voice Module User Core Router User to Network Interface Virtual Path Maintenance Virtual Private Network Wide Area Network
xiii
About This Manual
xiv
Overview
Whats In This Chapter:
Description of Passport 4400 services Benefits of Passport 4400-based networks Description of Passport 4400 Interworking The Magellan Passport Access Network Link (MPANL) protocol Switched Permanent Virtual Circuits (SPVCs) Passport 4400 Network Layers The concept of inter-LAN switching Core Router functionality Some special features of Passport 4400 system architecture Global Circuit Manager Virtual Ports Interface Indices An example of a Passport 4400-based network
The Passport 4400 series of access devices provides low-cost multimedia and data transport services across Passport networks for small branch offices. Among the features and services available are the following: LAN services such as bridging and IP/IPX routing frame relay tunneling (encapsulation) for external FRADs with multiplexing at the Passport switch prioritization for multimedia (voice) traffic when it shares the link with application data use of ISDN as a primary link or backup link advanced interfaces supporting high-quality voice compressed to 8 kbps and fax demodulation legacy protocol support via a Legacy Data Module (LDM).
Note: Passport models 160, 50, 30 and 6000-7000 series are referred to as Passport switch in this document. A Passport network refers to a network containing at least one Passport switch.
1-1
Overview
Passport 4400 units act as end points in a star topology WAN supported by Passport switches, and must be logically connected to a core router on the Passport switch. These core routers are then interconnected to build larger networks. The benefits of Passport 4400 are achieved through the interworking of Passport 4400 units with their parent Passport switches. This arrangement allows small branch sites to consolidate high-quality voice and data services over a single low-speed link into the Passport network. The traffic is then passed through regional concentration sites where it can be carried more rapidly to its destination. A typical Passport 4400 network diagram is shown in Figure 1-3 at the end of this chapter.
Benefits of Passport 4400 Networks

Passport 4400-based networks economically extend Passport functionality into small branch offices. They accomplish this by obtaining optimum performance from a variety of low-speed communications links with Passport switches through the use of a proprietary link protocol providing access services that interoperate with Passport network services providing simplified provisioning and error-recovery features to reduce management costs permitting scalable solutions through the use of large quantities of smallscale Passport 4400 units, thus eliminating the need to rebuild networks in order to expand them.
Passport 4400 Interworking

Each Passport 4400 unit is physically connected to the Passport network by a single WAN link consisting of a leased line or other direct connection, an ISDN connection or a public frame relay service. This single physical link is used to carry all user traffic and network management traffic between the Passport 4400 and the Passport network. Virtual connections called switched permanent virtual circuits (SPVCs) are used to establish connections to a Passport inter-LAN Switching (ILS) service and to other Passport services. The higher-level protocols that provide routing and other services to the Passport 4400 are then established over these SPVCs.
1-2
Overview
Magellan Passport Access Network Link (MPANL) Protocol A proprietary frame relay link protocol, Magellan Passport Access Network Link (MPANL), is used to establish the physical link between the Passport 4400 and the Passport switch. MPANL is an internal Passport service based on FRF.11 and the ITU-T Q.922 and Q.933 specifications for frame mode bearer services. It operates at the data link and network layers (Layers 2 and 3) of the OSI model and provides the following services and functionality: accomodates the unique signaling and payload transport requirements of the Passport 4400 accomodates a variety of link types in order to scale link costs to the lowcost Passport 4400 prioritizes voice traffic to assure high-quality voice service on all link types when sharing bandwidth with application data supports frame relay multiplexing/demultiplexing (FrMux), enabling multiple Passport 4400 units to communicate through a single Passport function processor (FP) port provides the link management and control software that enables traffic management. Certain MPANL extensions of the frame relay protocol are signaled in DLCI-0; others are signaled in DLCI-16. The following are signaled in DLCI-0: call setup extensions using proprietary MPANL Information Elements (IEs) call setup extensions using switched permanent virtual circuit (SPVC) and CUG IEs A-bit signaling using the Q.933 STATUS message. The following MPANL extensions are signaled in DLCI-16: dynamic exchange of voice service profiles between the Passport 4400 and the Passport switch reliable out-of-band signaling after call establishment. The MPANL service designates the use of DLCI-16 exclusively for MPANL signaling. MPANLs adaptation of LAPF (Link Access Procedure for Frame-mode bearer services) is used to assure signaling reliability. For more information about the MPANL protocol, see Chapter 2 of document 241-7001-210, Magellan Passport Access Network Link User Guide.
1-3
Overview
MPANL and Switched Permanent Virtual Circuits (SPVCs) Passport networks employ virtual connections that have characteristics of both permanent virtual circuits (PVCs) and switched virtual circuits (SVCs). These connections are called switched permanent virtual circuits (SPVCs). Figure 1-1 shows a Passport MPANL service on the edge of a Passport frame relay cloud. (Note that the cloud represents a single Passport switch.) The MPANL service interconnects a Passport 4400 SPVC virtual port and a frame relay service (FRS) residing on a Passport function processor (FP). The Passport FRS can be a Frame Relay User-Network Interface (FRUNI), a Frame Relay Network-toNetwork Interface (FRNNI), or another MPANL. When a Passport 4400 establishes a connection to a Passport FRS, an SPVC virtual port is created on the Passport 4400. This virtual port must be provisioned with a remote DNA that corresponds to the FRS to which it is connecting and a remote DLCI that corresponds to the connection within the FRS to which it is connecting. SPVCs are provisioned to originate from each branch Passport 4400 unit and terminate on a Passport Frame Relay DCE (FRUNI) Data Link Connection Identifier (DLCI) resident on the Passport switch. Normally there are two SPVCs provisioned for each branch Passport 4400: one to handle user service traffic, and one to handle network management traffic. On the Passport side, the FRS function processor is provisioned with the DNA of the SPVC virtual port, a local DLCI and the DLCI of the Passport 4400s SPVC virtual port. A PVC call request message is sent to the MPANL, which handles it as an SPVC call.
Passport Switch Passport 4400 Passport FRUNI, FRNNI, or MPANL
SPVC Virtual Port
Passport MPANL
Calling DLCI: 16 Called DLCI: X
SVC
VC SPVC
Local DLCI: X Remote DLCI: 16
Figure 1-1. MPANL and SPVC Connectivity
1-4
Overview
Passport 4400 Network Layers

Provisioning a Passport 4400 unit involves creating multiple logical layers to operate over the physical layer. Each logical layer carries a different type of traffic, such as network management traffic, voice traffic, LAN traffic, or traffic supporting other user services. Each layer is supported by a switched virtual circuit (SVC) which may terminate on the same physical port of the Passport 4400. Figure 1-2 shows the logical layers of a Passport 4400 network link.
IP Layer Router Layers, Management, Voice

Passport 4400 Passport 4400 Remote LAN
NMS Station
Frame Relay User Service Layer

Passport 4400 Passport 4400
FRAD
FRAD
Physical Layer
Passport 4400 MPANL Connection Magellan Passport WAN
Figure 1-2. Passport 4400 Network Layers
1-5
Overview
Physical Layer A Passport 4400 may be physically connected to a Passport network via a direct link, an ISDN connection or a public frame relay network. The connection may be to a V.35, V.11, DS1, E1, DS1C or E1C Function Processor (FP) on the Passport switch. Port 2 on the Passport 4400 operates in DTE mode; the Passport FP operates in DCE mode and provides clocking for the Passport 4400. For information on the appropriate cables to use for this connection, consult document 800-1951-20, Passport 4400 Hardware Installation Manual. Management Layer When a Passport 4400 unit is physically connected to a Passport network, a primary logical link to a Passport function processor acting as a network management core router must be established before any user traffic can be carried. This link must be in place in order to ensure that network management traffic remains separate from user service traffic. Connectivity between the management station and branch Passport 4400 units is achieved via the combination of a physical connection to the MPANL service running on the Passport Function Processor (FP) to which the branch unit is connected, the SPVC to the Passport Frame Relay UNI service provided by the inter-LAN Switching Network Management Core Router (ILS NMCR), and the logical associations between these key elements. The following are major network management components of a Passport network containing Passport 4400 units: the Passport ILS network management core router (NMCR) functionality the MPANL connection, which allows Passport 4400 units to communicate with the Passport WAN. Passport ILS Core Router Functionality In a Passport 4400-based network, different Passport switches are used for user service traffic and network management traffic. For example, software downloads, branch configuration updates and SNMP traps generated by the Passport 4400 SNMP agent are routed to the NMS workstation through the Passport switch designated for network management traffic. Management traffic passing between Passport 4400 branch units and the network management core router has the same characteristics as IP LAN traffic, but needs to have higher data security. To ensure data integrity and to better utilize frame relay link bandwidth, management traffic is allocated its own virtual port and interface index number (IfIndex), and is assigned a higher traffic priority than LAN data. A core router can support a number of Passport 4400 branch units; the exact number will depend on the type and volume of user traffic.
1-6
Overview
MPANL Connection An MPANL connection is required between every Passport 4400 in the network and a Passport switch. The MPANL protocol, among other things, enables prioritization within the network of various traffic types within the multiplexed payloads of Q.922 frame relay frames. See Passport 4400 Interworking on page 1-2 for more information about MPANL. For detailed information, see document 241-7001-210, Magellan Passport Access Network Link User Guide. User Service Layers Once the management layer is in place, user services for LAN, voice and other applications can be provisioned. Each service layer carries specific traffic relating to an individual Passport 4400 service. For example, a user service subnet established for LAN traffic would carry end-user traffic between Passport 4400 branch units and the Passport switch designated as a User Core Router.
Passport 4400 System Architecture

A complete picture of Passport 4400 network deployment requires a discussion of the following components of the Passport 4400s system architecture: Global Circuit Manager (GCM) Virtual Ports Interface Indices Global Circuit Manager (GCM) The Passport 4400 supports two physical links (one primary and one backup) and several logical links to the Passport switch. These links can use either Frame Relay or ISDN protocol, with one physical link designated as primary and one as backup. To control the traffic flow during switch-over from primary link to backup and vice versa, a system of circuit managers is assigned to each protocol and major system function. These circuit managers are arranged in a hierarchical order, with the Global Circuit Manager (GCM) at the top. The GCM administers all logical links between the Passport 4400 and the Passport switch. The GCM is provisioned as to which link type (ISDN or serial) and which physical port will provide the primary and backup links. The GCM also monitors the links and determines when to switch from the primary to the backup link if the primary link fails, and when to switch from the backup link to the primary if the primary link is restored.
1-7
Overview
The GCM does not contain any protocol information or signaling information. To allow for the greatest flexibility, the GCM has been designed to be protocolindependent, with specific information for each protocol stored in separate circuit managers. For example, for ISDN, service-specific information such as dial phone numbers is stored in the ISDN Circuit Manager (ICM). Virtual Ports The Passport 4400 has been designed to allow all subnet traffic, both end-user traffic (such as voice, LAN and frame relay pass-through) and management traffic, to be transmitted back and forth between the Passport 4400 unit and the network over a single WAN link. In order to manage the numerous SVCs carrying this traffic, each type of service is associated with a virtual port and managed by an Interface Index (IfIndex). During network configuration, associations are made between the virtual ports and the IfIndices on each Passport 4400 unit. Virtual ports interface logically with the user applications and the underlying transport layers and services (such as Ethernet or frame relay). This arrangement allows numerous services to be multiplexed over a single physical link. When an IP address is given to a virtual port, that virtual port becomes logically linked to a physical port on the Passport 4400 unit. A single physical port can support several virtual ports. Interface Indices For management purposes, each Passport 4400 physical and virtual port is mapped to a specific interface index. An interface index (ifIndex) is a unique identifier that allows SNMP to read and write to a particular Physical Point of Attachment (PPA). These interface indices are used to establish logical links between physical or virtual ports and higher-level applications and protocol stacks. The configured and operational ifIndices are listed in ifIndex tables that are accessible through the Command Line Interface. The Passport 4400 can support up to 255 ifIndices. Some of these are hard-coded and cannot be changed; others are automatically reserved by the Passport 4400 operating system when the unit is powered on. The quantity of ifIndices automatically reserved is dependent on the type and arrangement of modules that are present in the unit. The hard-coded ifIndex numbers are listed and described in Monitoring Passport 4400 System Parameters in Chapter 3, Network Administration.
1-8
Overview
Sample Passport 4400 Network

The diagram on the following page is an example of a Passport 4400-based network illustrating many connection and service options. The following table describes the connections and services.
Table 1-1. Passport 4400 Network Connections and Services Site A Description External Links Devices Services
A small branch office with a Public Frame couple of telephones, a fax and Relay; backup a few LAN-based workstations. ISDN A large Passport 4400-only site. Legacy protocols are supported to the IBM host at Site C. (A typical bank branch arrangement.) A main site with both a Passport 4400 and a Passport switch. Perhaps a small bank headquarters office. A large branch office with a separate connection between the PBX and the service provider Passport. Public Frame Relay; backup ISDN
Passport 4400 Analog voice and fax LAN connected through a third-party router Passport 4400 Digital voice and fax LAN routing Legacy protocols (X.25 and Token Ring/SNA) via an LDM
Dedicated link to service provider; dedicated link to core router/NMS site
Passport 4400 LAN routing X.25 via LDM Passport switch Voice and fax via PBX Token Ring/Ethernet
Dedicated link Passport 4400 Voice and fax from PBX to Frame Relay DCE service provider; Large scale voice and fax dedicated link from PBX Passport 4400 to service provider Dedicated link to Site C; dedicated link to service provider Passport switch Voice and fax Frame Relay DCE to thirdparty router ILS core management and user router
A Passport-only site providing management and user core router services along with a network management workstation.
1-9
Overview
SITE A
Passport 4400
R
SITE B
3270 Cluster Passport 4400 X.25 PBX
SITE C
IBM Host PBX Passport Public FR WAN
Public Telephone Network
X.25 Passport 4400
SITE D
X.25
PBX
SITE E
Passport
Passport 4400
NMS Workstation
FR
FR
Legend:
R
= Third-party Router = IP LAN with attached stations
Figure 1-3. Typical Passport 4400 Connections
1-10
Getting Started
Steps required to add a Passport 4400 to a Passport network Provisioning procedures necessary to accomplish a standard setup Provisioning procedures for a T1 or 56k CSU primary WAN link
This chapter explains the steps necessary to add a Passport 4400 to an existing Passport network. The steps are given in summary form first; then they are broken down into specific instructions that include provisioning procedures and Command Line Interface (CLI) commands. It is assumed that the following prerequisite steps have been accomplished prior to the physical installation of the Passport 4400 unit: user service requirements have been determined for the branch LAN that will be attached to the Passport 4400 the link type that will connect the Passport 4400 to the Passport switch (direct connection, ISDN, or frame relay) has been determined the Passport switch that will provide network management (NMS) core router functionality for the new Passport 4400 has been selected.
Adding a Passport 4400 to a Passport Network

Step 1: Configure the MPANL Service on the Passport Switch Before the new Passport 4400 can be provisioned, the Passport Function Processor to which the new unit is being connected must be configured for the MPANL service. Step 2: Configure Core Router Functionality on the Passport Switch The Passport switch that will provide network management for the Passport 4400 must be configured as an inter-LAN Switching (ILS) core router. Step 3: Provide Network Management Workstation Connectivity The workstation that will be used to manage the Passport 4400 and configure it using SNMP must be identified and connected to the ILS core router via an IP LAN. If the Passport 4400 will support legacy traffic, you must also provide an X.25 connection to the network management workstation for communicating with the Legacy Data Module (LDM) or Legacy Expansion Module (LEM) on the Passport 4400.
2-1
Getting Started
Step 4: Install the Passport 4400 Unit Set up the Passport 4400, install the interface modules and connect the cables to the application devices and the Passport switch. Step 5: Load Factory Default Configuration Values When the Passport 4400 is powered on for the first time, the configuration memory banks are empty. It is recommended that you execute a reset procedure in order to ensure that the configuration banks contain the factory default configuration settings. Step 6: Provision Passport 4400 Node and MPANL Link Parameters Give the Passport 4400 a unique identity on the management subnet by provisioning its node ID and MPANL link to the Passport switch. Step 7: Provision Passport 4400 ILS Virtual Circuits This step establishes switched permanent virtual circuits (SPVCs) between the Passport 4400 and the Passport ILS core router in order to enable routing of both user service traffic and network management traffic. Step 8: Provision User Subnets and Services After all of the above steps have been completed, you are ready to provision the appropriate user services on the access ports of the Passport 4400.
Step 1: Configure the MPANL Service on the Passport Switch

What You Need to Know:
All Passport function processors (FPs) that will provide the MPANL service must be upgraded to PM2. The Passport network must be migrated to Passport Release 4.2.1 or greater in order to support MPANL and other elements necessary for Passport 4400 interworking. In addition to the MPANL service, the Frame Relay Multimedia Traffic Class service must also be configured on the Passport FP to which the Passport 4400 is to be connected. For information on which Passport FPs support the MPANL service, see document 241-7001-210, Magellan Passport Access Network Link User Guide. The type of physical link attaching the Passport FP to the Passport 4400 affects the specific commands used to configure the MPANL service. Refer to document 241-7001-210, Magellan Passport Access Network Link User Guide for specific configuration procedures.
2-2
Getting Started
Step 2: Configure Core Router Functionality on the Passport Switch

The Passport switch that is acting as the ILS Network Management Core Router (NMCR) must be equipped with function processors for Frame Relay User-Network Interface (FRUNI), Frame Relay DTE (FRDTE), and Ethernet IP services. A physical or virtual frame relay hairpin connection is required on the Passport ILS NMCR in order to associate the Passport ILS FRDTE interface with the FRUNI service that terminates the SPVC from the Passport 4400. Passport Release 4.2 and above creates a virtual hairpin within the function processor so that a physical hairpin connection is not required when using the Passport 4400. (See Figure 2-1.) A distinct IP subnet is required for the FRDTE interface. It is recommended that the Passport ILS FRDTE protocol port be configured for passive RIP with silence flag enabled. If LAN services will be implemented at the Passport 4400 site, another Passport switch must also be configured as a User Core Router (UCR). You need the following numbers to configure core router functionality: Logical Processor number or card number of the ILS function processor in both Passport switches (the one providing the Network Management Core Router and the one providing the User Core Router) DNA numbers for the Passport switches (one for the NMCR; one for the UCR) DLCI numbers for the Passport 4400 (one for network management traffic; one for user traffic) IP addresses for the Passport protocol ports (one for network management traffic; one for user traffic).
Notes: The Network Management Core Router and the User Core Router should be configured on different virtual routers in order to provide security for the network management traffic. This can be accomplished either by establishing virtual routers on two different Passport switches, or by using the Multiple Virtual Router facility available with Passport Release 4.2.3 or above. See document 241-7001-809, Passport Multiple Virtual Routers User Guide. For information regarding which features are needed on the Passport Logical Processor (LP), refer to the documention for your Passport switch.
2-3
Getting Started
Passport
Passport
Passport 4400
ILS
Bridge Router Port 1
SPVC VP DNA DLCI
VR V.35 Port Port 2
FRDTE
MPANL Network Link
MPANL
VC
FRUNI
SPVC
Figure 2-1. ILS Core Router Functionality
Configuring core router functionality on the Passport switch involves the following procedures: Configuring FRUNI on the Network Management Core Router (NMCR) Configuring FRDTE and a virtual router on the NMCR Configuring FRUNI on the User Core Router (UCR) Configuring FRDTE and a virtual router on the UCR. Configuring Passport ILS as a UCR is very similar to NMCR configuration, except that remote groups must be provisioned below the FRDTE component and associated with multiple protocol ports and IP subnets -- or IPX network numbers (one per branch Passport 4400). In other words, the number of IP subnets and/or IPX network numbers is equal to the number of Passport 4400s with interconnected LANs.
Note: In the following configuration example, the numbers 299 and 399 are used for unique ILS FRUNI numbers. The first digit represents the logical processor (lp) number or card number in the Passport switch that is running the ILS software; the 99 is a user-selected number that is high enough to not be associated with any physical port.
2-4
Getting Started
Configuring FRUNI on the NMCR The following commands must be executed on the Passport switch in order to add a FRUNI interface for the NMCR connection to a Passport 4400. A single FRUNI interface can be used for multiple Passport 4400s; however, each Passport 4400 requires its own individual SPVC connection to the NMCR FRUNI interface so that network management traffic can be exchanged. On the Passport switch, enter the following commands:
add fruni/299
(2=lp number; 99=user-selected number for ILS)

delete fruni/299 framer
(Deletes the framer component; a virtual framer is used instead.)

add fruni/299 virtualframer set fruni/299 virtualframer lp lp/2
(Assigns the FRUNI to the logical processor that supports ILS.)

set fruni/299 dna dna 3021811397299
(Passport DNA prefix=3021811397; 299=unique number for ILS FRUNI)

set fruni/299 lmi procedures ansi * add fruni/299 dlci/20
(Assigns a DLCI of 20 to the Passport 4400 for network management traffic. Each Passport 4400 must have a unique DLCI number for network management traffic.)
* set fruni/299 dlci/20 dc remotedlci 16
(The remote DLCI is the DLCI that the Passport switch uses to talk to the Passport 4400; it is always 16 for MPANL.)
* set fruni/299 dlci/20 dc remotedna 302181139810101
(remote DNA=MPANL DNA prefix of the Passport 4400 + 101 for NMS traffic)
Note: The 101 suffix used above is required by the Passport 4400 to indicate NMS traffic. set fruni/299 dlci/20 dc type permanentslave *
(Passport switch is always the Slave; Passport 4400 is the Master.)

Note: The steps marked by an asterisk (*) must be performed for each Passport 4400 that is to have NMCR access.
2-5
Getting Started
Configuring FRDTE and a Virtual Router on the NMCR The following commands must be executed on the Passport switch to add an FRDTE service and associated virtual router for a Passport 4400:
add frdte/299

delete frdte/299 framer

add frdte/299 virtualframer set frdte/299 virtualframer lp lp/2
(Assigns FRDTE to the logical processor that supports ILS.)

set frdte/299 lmi procedures ansi add frdte/299 rg/2
(All Passport 4400s are assigned to a single remote group; rg/1 is used for dynamic DLCIs set up by the Passport switch.)
* add frdte/299 stdlci/20
(Creates a static DLCI between the FRUNI service and the FRDTE.)
Note: This command must be repeated for each Passport 4400 in the network; each unit must have a unique DLCI. add vr/1
(Creates the virtual router.)

add vr/1 pp/NMS
(Assigns a protocol port (pp) for the routing of network management traffic; all Passport 4400s are assigned to the same pp.)
* set frdte/299 stdlci/20 linktoremotegroup frdte/299 rg/2
(Links the static DLCI to the remote group containing the Passport 4400.)
Note: This command must be repeated for each Passport 4400 in the network. set frdte/299 rg/2 linktoprotocolport vr/1 pp/NMS
(Links the remote group to the protocol port.)

add -s vr/1 pp/NMS ipp lo/100.100.1.1
(Configures the protocol port for the IP protocol and assigns an IP address to the protocol port; must be on the same subnet as ifIndex 4 on the Passport 4400.)
2-6
Getting Started
set vr/1 pp/NMS ipp lo/100.100.1.1 netmask 255.255.255.0 add vr/1 pp/NMS ipp lo/100.100.1.1 ripif add vr/1 ip add vr/1 ip rip
Configuring FRUNI on the UCR The following commands must be executed on the Passport switch in order to add a FRUNI interface for the UCR connection to a Passport 4400. A single FRUNI interface can be used for multiple Passport 4400s; however, each Passport 4400 requires its own individual SPVC connection to the UCR FRUNI interface so that user traffic can be exchanged. On the Passport switch, enter the following commands:
add fruni/399

delete fruni/399 framer

add fruni/399 virtualframer set fruni/399 virtualframer lp lp/3
(Assigns the FRUNI to the logical processor that supports ILS.)

set fruni/399 dna dna 3021811398399
(Passport DNA prefix=3021811398; 399=unique number for ILS FRUNI)

set fruni/399 lmi procedures ansi * add fruni/399 dlci/21
(Assigns DLCI of 21 to the Passport 4400 for user traffic. Each Passport 4400 must have a unique DLCI number for user traffic.)
* set fruni/399 dlci/21 dc remotedlci 16
(The remote DLCI is always 16 for MPANL.)

* set fruni/399 dlci/21 dc remotedna 302181139810100
(remote DNA=Passport 4400 MPANL DNA prefix + a 3-digit suffix indicating the type of traffic and the Point of Physical Attachment (PPA) on which the virtual port resides.)
* set fruni/399 dlci/21 dc type permanentslave
(Passport switch is always the Slave; Passport 4400 is the Master.)

Note: The steps marked with an asterisk (*) must be performed for each Passport 4400 that is to have UCR access.
2-7
Getting Started
Configuring FRDTE and a Virtual Router on the UCR The following commands must be executed on the Passport switch to add an FRDTE service and associated virtual router for a Passport 4400:
add frdte/399

delete frdte/399 framer

add frdte/399 virtualframer set frdte/399 virtualframer lp lp/3
(Assigns FRDTE to the logical processor that supports ILS.)

set frdte/399 lmi procedures ansi * add frdte/399 rg/12
(Each Passport 4400 in the network must be assigned to its own remote group; rg/1 is reserved for dynamic DLCIs set up by the Passport switch.)
* add frdte/399 stdlci/21
(Creates a static DLCI between the FRUNI service and the FRDTE; this must be a unique number for each Passport 4400 in the network.)
add vr/1
(Creates the virtual router.)

* add vr/1 pp/A1_1
(Assigns a protocol port for the routing of user traffic; each Passport 4400 requires its own protocol port.)
* set frdte/399 stdlci/21 linktoremotegroup frdte/399 rg/12
(Links the static DLCI to the remote group containing the Passport 4400.)
* set frdte/399 rg/12 linktoprotocolport vr/1 pp/A1_1
(Links the remote group to the protocol port; this command will be unique for each Passport 4400 unit.)
* add -s vr/1 pp/A1_1 ipp lo/100.102.1.1
(Configures the protocol port for IP routing and assigns an IP address to the protocol port. The IP address for each Passport 4400 must be unique and must be on the same subnet as ifIndex 2 for that unit.)
Notes: You may configure this port for IPX routing or for bridging. See Configuring the User Core Router for IPX Routing below. The steps marked by an asterisk (*) must be performed on each Passport 4400 that is connected to the User Core Router.
2-8
Getting Started
set vr/1 pp/A1_1 ipp lo/100.102.1.1 netmask 255.255.255.0 add vr/1 pp/A1_1 ipp lo/100.102.1.1 ripif add vr/1 ip add vr/1 ip rip
Configuring the User Core Router for IPX Routing
If you need to configure the Passport User Core Router for IPX routing, use the following commands:
add vr/1 ipx set vr/1 ipx netp 00-00-00-01
(Assigns netnumber 1 to the virtual router.)

add vr/1 pp/A1_1 ipx/link
(Configures the protocol port for IPX and specifies the link as frame relay rather than Ethernet.)
set vr/1 pp/A1_1 ipx/link networkNumber 00-00-00-02 set vr/1 pp/A1_1 ipx/link defaultType wanRip
(Turns RIP ON on the WAN.)
Step 3: Provide Network Management Workstation Connectivity

In this step you will set up a UNIX workstation to provide a TFTP server for software download and to provide TELNET connectivity for remote access to the Passport 4400 Command Line Interface (CLI). This workstation is also used as the site for installation of the Passport 4400 Network Management System (NMS).
While the Command Line Interface (CLI) is used for all configuration and software download functions described in this manual, NMS configuration and surveillance capabilities are supported in Passport 4400 Release 2.0. For a description of how to use the NMS to configure the Passport 4400, refer to NTP 241-6001-106, NMS Magellan Access Configuration Server Installation and Administration Guide. Although it is not mandatory to complete this Step 3 in order to install a new Passport 4400 in an existing Passport network and get it up and running, it is strongly recommended that you set up a network management workstation to provide software download capabilities and remote access to the CLI. An Ethernet interface on the Passport ILS Network Management Core Router, or elsewhere in the network, is either connected to the same management LAN segment as the NMS workstation, or is connected directly to an Ethernet interface
2-9
Getting Started
on the NMS workstation (see Figure 2-2). The management subnet must be distinct from the FRDTE subnet supporting the SPVC to the branch Passport 4400. The NMS workstation must have a static route configured in order to ensure that the IP address of the Passport 4400 network management traffic is associated with the correct workstation Ethernet port. To set up the NMS workstation as a TFTP server, perform the following steps:
1. Log in as root and edit the /etc/inetd.conf file. 2. Find the line starting with #tftp dgram and remove the comment character (#) from the
beginning of the line.

3. At the end of the tftp dgram line is a directory specifier that indicates where the TFTP
protocol will look for files to transfer. Add a subdirectory for the Passport 4400 software underneath the /tftpboot directory.
4. Save these changes and reboot the workstation. Notes: If the tftp dgram line is already uncommented, it means that the workstation is already serving as a TFTP server. If you use the directory already specified for this workstation as the directory for the Passport 4400 software, problems may occur if the files used by the other system conflict with the naming conventions for the Passport 4400 software. It is therefore recommended that the directory containing the Passport 4400 software contain no other files other than the software for download. It is recommended for security reasons that TFTPs secure mode be used for software download.
For instructions on how to download software from the NMS workstation to a Passport 4400, see Chapter 4, System Utilities.
Passport Passport 4400 NMS
Figure 2-2. Providing Network Management Workstation Connectivity
2-10
Getting Started
Step 4: Install the Passport 4400 Unit

Specific instructions for the physical installation and cable connections of the Passport 4400 are given in Chapters 2 and 3 of document 800-1951-20, Passport 4400 Hardware Installation Manual. Refer to that manual when performing this step. Be sure to connect either an asynchronous terminal or a PC with terminal emulation software to the management port on the base module of the Passport 4400. Power on the management device and set the communication parameters as follows: Data Rate: 9600 bps Data Bits: 8 Stop Bits: 1 Parity: None Power on the Passport 4400 unit according to the instructions given in Chapter 2 of the Passport 4400 Hardware Installation Manual. After the boot sequence has concluded, a login prompt will appear on the local management screen. If the login prompt does not appear, press Enter one or more times until it appears. Type CLI at this prompt and press Enter. At the password prompt, press Enter again. A welcome message will appear followed by the prompt CLI>. You are now logged into the Command Line Interface, the user interface for the Passport 4400. CLI Architecture The Command Line Interface (CLI) uses the SNMP protocol to locally provision, configure and monitor the Passport 4400. The CLI performs mapping between user commands and the SNMP Management Information Base (MIB) objects. The CLI interfaces with the SNMP client to communicate requests to the SNMP agent. The SNMP client collects the responses generated by the SNMP agent and passes them back to the CLI which then translates them into the display shown on the CLI screen. The CLI can be accessed locally by an asnychronous terminal device connected to the serial management port on the Passport 4400 base module; it can also be accessed remotely via TELNET. The workstation using TELNET must have IP connectivity via the NMS Core Router or else be directly connected to the Ethernet port on the Passport 4400. (For more information on TELNET access, see Chapter 4, System Utilities.) Only one CLI session can be active at a time on a Passport 4400 unit.
2-11
Getting Started
CLI Structure The CLI structure is a hierarchy consisting of a set of primary functions, most containing one or more levels of sub-commands followed by configurable parameters. To see the list of primary CLI functions, press Enter at the CLI> prompt. The following list will appear:
CLI> add confirm define delete debug download logout ping reset save set show
These functions are described in document 800-1950-20, Passport 4400 CLI Command Reference. Using the CLI When entering CLI commands, you can type the entire command, or just enough characters to make the command unique. For example, you could use the single letter a for the add command, but you must use def for the define command in order to distinguish it from the delete and debug commands.
Note: In this manual, CLI commands will be presented in their entirety for clarity.
To enter a command, type the command and press Enter. If the command syntax is correct and the appropriate hardware and software is installed, the command will be executed. For some commands, the message Command Successful will appear on the CLI screen. If the command syntax is incorrect, or the appropriate hardware and software is not installed, the system will respond with the message Invalid Command or Command Failed.
2-12
Getting Started
The following tips will help you in navigating the CLI: If you do not know the available options for a command, type the command and press Enter. The CLI will display the next level of options. To redisplay the last command you entered, press Ctrl-P. To exit the CLI without using the logout command, press Ctrl-D. Parameters displayed between angle brackets indicate variables you must provide. Ask your network administrator for the information. Display string values must be typed between double quotation characters. Some parameters provide entry and table options, allowing you to display values either individually or together in a group. If you want to access parameters as a group, use the table option; if you want to access parameters individually, use the entry option. Long display commands can be interrupted at the end of a screen of text by entering Q.
Step 5: Load Factory Default Configuration Values

Passport 4400 units shipped from the factory are pre-loaded with the latest release of boot code and application software. Factory default configuration values are included in the application software, but they are not pre-loaded into configuration Flash memory. When a new Passport 4400 is powered on for the first time, configuration Flash is empty. Before provisioning user services, the factory default configuration values should be loaded into the configuration memory. To ensure that configuration memory contains factory default values and only factory default values, execute the following command at the CLI prompt:
reset system default reset
This command clears the configuration memory banks of all data and loads the default values during the autoboot sequence.
2-13
Getting Started
Step 6: Provision Passport 4400 Node and MPANL Link Parameters

A node profile is required for each link established between the Passport 4400 and the Passport switch. You will need to obtain the following information from your network administrator: the DNA numbering plan required for your application (the supported DNA numbering plans are X121 and E164; the default is X121). the DNA number of the Passport 4400. This consists of the DNA number of the Passport switch providing the MPANL service plus a unique suffix identifying the Passport 4400 unit and distinguishing it from all other Passport 4400 units in the network. the node name and or node ID of the Passport 4400. your customer ID (and/or contact person and location, if desired). DTE and DCE maximum frame size for the Passport 4400-to-Passport connection. DTE and DCE receiver bandwidth for the Passport 4400-to-Passport connection. maximum DLCI value for the Passport 4400-to-Passport connection. When a Passport 4400 unit is brought onto a Passport network, the following information exchange takes place between the Passport 4400 and the Passport switch to which it is connected: The Passport 4400 sends its node profile information to the Passport switch. The Passport sends DCE profile information to the 4400. The 4400 registers its DNA prefix with the Passport. The 4400 sends its DTE bandwidth and frame size to the Passport. To complete the Passport 4400 node profile and link setup, perform the following procedures:
1. Set the DNA numbering plan, if required. Enter the following commands at the CLI
prompt.
show fr system configured
This displays several system parameters, the last of which is the current configured DNA numbering plan. The default setting is x121.
define fr system numberingplan e164
This command changes the DNA numbering plan from X121 to E164 when the change is saved and a system reset is performed.
2-14
Getting Started
2. Provision node profile information. Enter the following commands at the CLI prompt. define msm profile customerid <CustomerId> : INTEGER (0..65535)
The element msm signifies MPANL Switch Map. The customer ID is expressed as an integer between 0 and 65535. Type the number after a space following the customerid element. Do not type the angle brackets.
define msm profile dnaprefix <DNAPrefix> : String (1..30)
This command assigns a unique DNA number to the Passport 4400. The DNA number is a string of from 1 to 30 characters. The string must be enclosed in quotation marks. The string is composed of the DNA numbering plan type, the DNA number of the Passport switch, and a unique number for the Passport 4400. Several identifiers are usually combined to construct the DNA number, as shown by the following example: Example DNAPrefix: [x121]302181139710 [x121] 3021 81 13 97 10 = = = = = = DNA numbering plan DNIC (Data Network Identifier Code) RID (Routing Identifier for the Passport switch) MID (Module Identifier for the Passport switch) Passport switch Node ID unique number for the Passport 4400
Note: When defining the DNA number, it is not necessary to enter the type of numbering plan. The system automatically reads the operational numbering plan type from configuration memory. If you do include the [x121] or [e164] at the beginning of the DNA number, be sure that it is inside the quotation marks. set system administration nodename <NodeId> : String (1..50)
This command assigns a node name or system name to the Passport 4400. Be sure to enter the desired name within quotation marks. The node name will appear in the CLI prompt as soon as the command is executed. In addition to assigning a node name to each Passport 4400, it may be desirable for network management purposes to also assign a node ID to each unit. This is an optional command.
define msm profile nodeid <NodeId> : INTEGER (1..65535)
For the node ID, enter an integer between 1 and 65535.
2-15
Getting Started
3. Provision the link information for the Passport 4400-to-Passport connection. Enter the
following commands at the CLI prompt.

show msm dtelink table IfIndex : 155 (operational) : 155 (configured) : 63 (operational) : 63 (configured) : 64000 (operational) : 64000 (configured) : 64000 (operational) : 64000 (configured) : 80 (operational) : 80 (configured)
MaxSubChannelRange
DTEReceiverBW
DCEReceiverBW
DTEMaxFrameSize
DCEMaxFrameSize
: 80 (operational) : 80 (configured) ---------------------------------------------------------------
This command shows both the configured and currently active (operational) values for the Passport 4400-to-Passport link parameters. For a new Passport 4400, the two sets of values will be the same, and they will be the factory default values. Notice the value for the interface index (ifIndex) of the link. You will need to enter this number in the next command.
add msm dtelink <IfIndex> <DTEReceiverBW> <DCEReceiverBW> <DTEMaxFrameSize> <DCEMaxFrameSize> <RowStatus> :INTEGER :INTEGER :INTEGER :INTEGER :INTEGER :modify (1..255) (16000..2048000) (16000..2048000) (50..4100) (50..4100)
For IfIndex, enter the number displayed by the show command above. For DTEReceiverBW and DCEReceiverBW, enter the frame relay link speed in bits per second (bps). These values should be the same, and they should match the line speed of the Passport switch. The default setting is 64000 bps.
Note: When the Passport 4400 is operating as DTE for the MPANL service, the line speed configured on the Passport switch overrides the values provisioned here. If the Passport 4400 is operating as DCE for the MPANL service, the value provisioned here determines the physical line speed, and the Passport switch must be configured to match.
2-16
Getting Started
The DTEMaxFrameSize and DCEMaxFrameSize should be set in accordance with the physical link speed, or, if tunneling through a public frame relay network, the expected line speed of the public frame relay service. The default setting is 80 bytes, which is acceptable for a 64 kbps link. It is recommended that you increase the link frame size by 80 bytes for each 64 kbps increment of bandwidth on the link. Failure to set the frame size properly may cause poor throughput performance if set too small, or voice quality degradation if set too large. After you have entered values for each of these parameters, type modify and press Enter. The dteLink table will be updated with the new values. Following is an example of what the add msm dtelink command might look like in its entirety: add msm dtelink 155 128000 128000 160 160 modify
define msm dtelink maxsubchannelrange <IfIndex> <maxSubChannelRange> : INTEGER (1..255) : INTEGER (17..255)
For IfIndex, enter the number displayed via the show command at the beginning of this procedure step. The max subchannel range represents the highest DLCI number that can be used on this link. The maximum allowable DLCI for the Passport 4400-to-Passport link is 255. The default setting is 63.
define wan port baudrate <IfIndex> <BaudRate> : INTEGER (1..255) : INTEGER (9600..1920000)
For IfIndex, enter the number displayed via the show command at the beginning of this procedure step. For BaudRate, enter the physical line speed as determined either by the MPANL service on the Passport switch or by the DCEReceiverBW value that was set using the add msm dtelink command.
Note: The line speed provisioned with this command is the value that is used by the Passport 4400 to calculate the percentage of bandwidth utilization. Therefore, it is important that this parameter reflect the actual line speed so that false utilization percentages are not recorded and false trap messages generated.
2-17
Getting Started
4. Check the new configuration values and verify that they are correct. Use the following
commands.
show msm profile NodeId : 1 (operational) : 5 (configured) : 0 (operational) : 99 (configured)
CustomerId
DNAPrefix
: "[x121] (operational) : "[x121]3021811397" (configured) ------------------------------------------------------------
A node ID of 5, a customer ID of 99, and a DNA prefix of 3021811397 have been configured. Notice that the operational values have not changed because the Passport 4400 has not been reset.
show msm dtelink table IfIndex : 155 (operational) : 155 (configured) : 63 (operational) : 254 (configured) : 64000 (operational) : 128000 (configured) : 64000 (operational) : 128000 (configured) : 80 (operational) : 160 (configured)
MaxSubChannelRange
DTEReceiverBW
DCEReceiverBW
DTEMaxFrameSize
DCEMaxFrameSize
: 80 (operational) : 1500 (configured) ------------------------------------------------------------
A maximum DLCI of 254 has been provisioned for the frame relay link between the Passport 4400 and the Passport. The link speed has been set to 128 kbps, and the maximum frame size has been set to 160 bytes.
2-18
Getting Started
show msm dtelinkstatus table IfIndex LAPFStatus LocalComponentName RemoteComponentName : : : : 155 up "MPA/D1_1 MPANL/155" "EM/CONF2 Mpanl/600 SigMpanl"
This command shows the status of the frame relay MPANL link between the Passport 4400 and the Passport. The LocalComponentName and RemoteComponentName are automatically generated when the Passport 4400 and Passport switch first communicate with each other. The node name you set in procedure 2 of this step is contained within the LocalComponentName parameter. (If you have not defined a node name, this field will be empty.) The number associated with Mpanl in the RemoteComponentName is the number of the provisioned MPANL component on the Passport switch; the number associated with MPANL in the LocalComponentName is the ifIndex of the MPANL link on the Passport 4400.
5. To activate the configuration changes, save the new settings and reset the Passport 4400.
Use the following commands.

save configuration update reset system current reset
After the Passport 4400 completes the reset cycle, you may want to log back into the CLI and execute the show commands in procedure 4 again to verify that your new parameter values are now operational.
2-19
Getting Started
Step 7: Provision Passport 4400 ILS Virtual Circuits

In Step 2 you configured FRUNI and FRDTE components on the Passport switch to provide ILS core router functionality. Step 7 establishes ILS switched permanent virtual circuits (SPVCs) between the Passport 4400 and the ILS core router on the Passport switch.
IP addresses for LAN, WAN and network management traffic on the Passport 4400. IP address of the Passport protocol port for network management traffic (obtain from Step 2). IP address of the network management workstation (NMS). DLCI numbers for user service traffic and network management traffic on the Passport 4400. DNA numbers for the Passport Network Management Core Router FRUNI and the User Core Router FRUNI (obtain from Step 2). Number of hops from the NMS workstation to the Passport 4400 Provisioning ILS Virtual Circuits for IP Routing
1. Make sure that the Passport 4400 is configured for IP routing. define bridge global ipprotocol routed
The factory default setting for IPProtocol is bridged.

2. Assign IP addresses for the following ifIndices: ifIndex 1 (LAN traffic on Port 1),
ifIndex 2 (WAN user service traffic on Port 2), and ifIndex 4 (network management traffic on Port 2).
add ip address entry <IfIndex> <IPAddress> <NetMask> <BcastAddress> : : : : INTEGER (1..255) IPAddress Sub-NetMask IPAddress
You must execute this command three times: once for each ifIndex. The subnet mask will be either 255.255.255.0 or 255.255.0.0 or 255.0.0.0 depending on the class of the corresponding IP address. When the four variables have been correctly added to the add ip address entry command, the CLI will display a Command Successful message.
Note: You may wish to set a more restrictive subnet mask and broadcast address for ifIndex 4, since it is reserved for network management traffic only. See TFTP Software Download in Chapter 4, System Utilities for more information.
2-20
Getting Started
3. Set frame relay as the data link type on ifIndices 2 and 4. define ip base parameters datalinktype 2 fr define ip base parameters datalinktype 4 fr 4. Enable RIP on ifIndices 1 and 2 (RIP is disabled by default). define ip base parameters routeprotocoltype 1 rip define ip base parameters routeprotocoltype 2 rip 5. Turn RIP on for the Passport 4400 unit. define ip base rip on
Without RIP turned on for the unit, the individual commands to enable RIP on specific ifIndices will not be recognized.
6. Enable inverse ARP on ifIndices 2 and 4. define ip invarp 2 ip enabled define ip invarp 4 ip enabled 7. Create switched permanent virtual circuit (SPVC) links to the Passport switch for
ifIndices 2 and 4.
add fr port spvclandata <VirtualPortIfIndex> <RemoteNetDLCI> <SVCDNA> <ConnectType> : : : : INTEGER (1..255) INTEGER (16..991) Frame Relay DNA (quoted string)(3..30) slave | master
This command must be executed twice: use VirtualPortIfIndex = 2 for the first command; use 4 for the second command. For RemoteNetDLCI, enter the DLCI numbers assigned to the Passport 4400 for user traffic and for network management traffic. (In the example in Step 2, user traffic was assigned DLCI = 21; network management traffic was assigned DLCI = 20.) For SVCDNA for ifIndex 2, use the same DNA number you used in Step 2 when you configured FRUNI on the User Core Router. (In the example given in Step 2, the number was 3021811398399.) For ifIndex 4, use the same DNA number you used in Step 2 when you configured FRUNI on the Network Manager Core Router. (In the example given in Step 2, the number was 3021811397299.) For ConnectType, enter master.
Note: The choice of which device is the master and which device is the slave is by convention. It is recommended that in the Passport 4400-to-Passport switch connection, the Passport 4400 be designated the master for the purpose of speedier service recovery.
2-21
Getting Started
Using the data from Step 2, the add fr port spvclandata commands are as follows: add fr port spvclandata 2 21 3021811398399 master add fr port spvclandata 4 20 3021811397299 master
8. Save the configuration changes and reset the Passport 4400. save configuration update reset system current reset 9. Add a static route to the network management workstation. add ip route <DestAddress> <IfIndex> <Metric> <NextHop> <NetMask> : : : : : IPAddress INTEGER (1..255) INTEGER (2..15) IPAddress IPAddress
For DestAddress, enter the IP subnet address of the network management workstation. The IfIndex is 4 for network management traffic. The Metric is the number of hops from the NMS workstation to the Passport 4400. For NextHop, enter the IP address of the Passport protocol port used for network management traffic. Example: add ip route 192.168.15.0 4 2 100.100.1.1 255.255.255.0
10. Save the static route in non-volatile configuration memory. save configuration update
2-22
Getting Started
The following diagram shows a typical example of IP routing. The IP addresses shown correspond to those used in the provisioning procedures in this chapter, and are for illustrative puroposes only.
Passport Network
UCR
LAN Passport 4400
ex 2 ifInd .1.2 .102 100
Port 1 Port 2
100
ifInd ex 4 .10 0 .1 .2
ILS NMCR
NMS Station 192.168.15.15
Figure 2-3. Typical IP Network Provisioning
Provisioning ILS Virtual Circuits for IPX Routing If your application calls for IPX routing, you must execute the following additional commands.
define ipx system basic routerstatus 1 enabled add ipx circuit <SysInstance> <CircuitIndex> <OperState> <IfIndex> <CircuitName> <DataLinkType> <NetNumber> : INTEGER (1 only) : INTEGER (1..16) : down | up| sleeping : INTEGER (1..16) : "String" (0..48) : raw | snap | type2 | type8022 : NetNumber(0x01 - 0xFFFFFFFE)
This command must be entered twice: once for the IPX circuit coming into the Passport 4400 on Port 1, and once for the IPX circuit exiting the Passport 4400 on Port 2. See Figure 2-4 below.
2-23
Getting Started
For SysInstance, enter 1 for both commands. Enter a different circuit index number for each circuit. For OperState, enter up for both commands. The IfIndex for user traffic entering the Passport 4400 on Port 1 is 1; the IfIndex for user traffic exiting the Passport 4400 on Port 2 is 2. Enter circuit names in quotes that identify the user or the application or that are meaningful in your network environment. For DataLinkType, enter raw for the inbound IPX traffic on Port 1; enter type2 for the outbound IPX traffic on Port 2. Each IPX segment is identified by a different network number. In the diagram below, network number 5 represents the incoming segment to the Passport 4400; network number 2 represents the outbound segment from the Passport 4400 to the Passport network. Example: add ipx circuit 1 1 up 1 Store54 raw 0x05 add ipx circuit 1 2 up 2 network type2 0x02
Network 05 Network xx
Network 02 Passport 4400 Passport 4400 Passport Network Port 2 Client
Port 1
Client
Figure 2-4. IPX Network Provisioning
2-24
Getting Started
Verifying the Passport 4400 Provisioning To verify that you have correctly provisioned the Passport 4400 so far, enter the following show commands at the CLI prompt.
show bridge global IPProtocol : routed (operational) : routed (configured) : enabled (operational) : enabled (configured) : disabled (operational) : disabled (configured)
SpanningTree
ArpSpoofing
AgingTime
: 300 (operational) : 300 (configured) --------------------------------------------------------------
This display shows that the Passport 4400 has been provisioned for routing and that the unit has been reset. If you execute the show command prior to resetting the unit, the display will show a configured condition of routed, but an operational condition of bridged (the default).
show ip base rip Rip : on (operational) : on (configured) -------------------------------------------------------------
This display shows that RIP has been turned ON for the Passport 4400 unit.
show fr port spvclandata base spvc configured table VirtualPortIfIndex RemoteNetDLCI ConnectId SVCDNA ConnectType VirtualPortIfIndex RemoteNetDLCI ConnectId SVCDNA ConnectType : : : : : : : : : : 2 21 1 "[x121]3021811398399" master 4 20 2 "[x121]3021811397299" master
This display shows the DLCIs and DNA numbers used to create the SPVC links to the Passport switch for user traffic (ifIndex 2) and network management traffic (ifIndex 4).
2-25
Getting Started
show ip address configured table IfIndex IPAddress Mtu DataLinkType KeepAlive ForwardBcast IPNumber RouteProtocolType NetMask BcastAddress IfIndex IPAddress Mtu DataLinkType KeepAlive ForwardBcast IPNumber RouteProtocolType NetMask BcastAddress IfIndex IPAddress Mtu DataLinkType KeepAlive ForwardBcast IPNumber RouteProtocolType NetMask BcastAddress : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : 1 192.168.150.1 1500 ether on off numbered rip 255.255.255.0 255.255.255.255 2 100.102.1.2 1500 fr on off numbered rip 255.255.255.0 255.255.255.255 4 100.100.1.150 1500 fr on off numbered disable 255.255.255.0 255.255.255.255
This display allows you to check the IP address and data link type you assigned to each ifIndex.
2-26
Getting Started
Step 8: Provision User Subnets and Services

After all of the above steps have been completed, you are ready to provision the appropriate user services on the access ports of the Passport 4400. Provisioning instructions for user services are contained in the following chapters. LAN Services Frame Relay Services Chapter 5 Chapter 6
HDLC Transparent Data Services Chapter 7 ISDN Services Chapter 8
Provisioning a T1 or 56k CSU Primary WAN Link

The primary WAN link connecting the Passport 4400 to the Passport network often consists of a public frame relay service utilizing a serial V.35 physical connection. This is the link type that has been assumed throughout this chapter. Other options are available, however. The primary WAN link may be ISDN, or it may consist of a T1 or 56k CSU. For information on provisioning ISDN as the primary WAN link, see Chapter 8, ISDN Services. Instructions for provisioning a T1 CSU or a 56k CSU are given below.
The 56k CSU module is designed to be installed in the primary WAN port (Port 2) only. If it is installed in Port 3 by mistake (the backup WAN port), the other WAN ports in the Passport 4400 may cease to function until the 56k CSU module is removed.
Caution:
2-27
Getting Started
Provisioning a T1 CSU Interface The T1 CSU is defaulted to support 24 channels of 64 kbps each, which equals the maximum aggregate bandwidth available for user traffic (1.536 Mbps) on a T1 link. For applications that can support this arrangement, no additional provisioning is required for the T1 CSU interface module. If you have been allocated less than the full T1 bandwidth for your application, then you must specify which of the 24 channels you will be using. Enter the following command at the CLI prompt:
set csu t1 ds0connection <DS0Connection> : "String" (0..73)
The string that follows this command consists of a list or a range of DS0 channel numbers. The string may contain up to 73 characters. If the channel numbers are listed separately, they must be preceded by and separated by a comma; if the channel numbers are consecutive, they may be listed as a range by preceding the first and last channel number with a hyphen. Note the following examples. Example 1: Assigned DS0 channels are 1, 3, 5, 7, and 9. set csu t1 ds0connection 1,3,5,7,9 Example 2: Assigned DS0 channels are 5 through 10 and 15 through 20. set csu t1 ds0connection 5-10, 15-20 Optional T1 CSU Parameters Additional T1 CSU parameters are available via the set csu t1 command in the event it is necessary to fine-tune the T1 interface to meet your application requirements. These parameters, along with their factory default settings, are shown below.
b8zsStatus clkSource ds0BasicRate frameFormat framerLbkStatus Sets Zero Code suppression to enable or disable. Default = enable. Sets the T1 CSU line clocking source to internalClocking or externalClocking. Default = externalClocking. Sets the T1 CSU line speed to a multiple of either 64k or 56k bits per second. Default = 64k. Sets the T1 CSU frame format to d4FramingMode or esfFramingMode. Default = esfFramingMode. Enables or disables the T1 CSU framer loopback. Default = disable.
2-28
Getting Started
lineBuildOut
Selects the T1 CSU line buildout. Choices are: 0-133-feet | 133-266-feet | 266-399-feet | 399-533-feet | 533-655-feet | -7.5db | -15db | -22.5db Default = -7.5 db
localLbkStatus payLoadLbkStatus remoteLbkStatus txB7zsStatus
Enables or disables the T1 CSU local loopback. Default = disable. Enables or disables the T1 CSU payload loopback. Default = disable. Enables or disables the T1 CSU remote loopback. Default = disable. Sets Bit 7 zero suppression to enable or disable. If set to enable, Bit 7 is forced to 1 if 8 consecutive zeros occur. Default = disable. Selects the T1 CSU Idle Code. Valid values are integers between 0 and 255. Default = 127. Enables or disables the T1 CSU transmit loop down. Default = disable. Enables or disables the T1 CSU transmit loop up. Default = disable.
txIdleCode txLoopDownStatus txLoopUpStatus
For additional information on the optional T1 CSU configuration parameters, consult the Dallas Semiconductor Data Book, DS2151Q T1 Single-Chip Transceiver. Provisioning a 56k CSU Interface For most applications utilizing the 56k CSU interface module, no additional provisioning is required on the Passport 4400 beyond what has already been covered in this chapter in the Getting Started steps. Optional 56k CSU Parameters In the event it is necessary to fine-tune the 56k CSU to meet your application requirements, the following parameters are available via the set csu 56k command. These parameters, along with their factory default settings, are shown below.
clockingSource filterForce Sets the clocking source to externalClock or internalClock. Default = externalClock Sets filter forcing to enable or to normalTxCondition. Default = normalTxCondition.
2-29
Getting Started
filterForcingCntl loopback
Sets the filter gain if filter forcing is enabled. Valid values are from 0db to 90db in increments of 6db. Default = 0db. Used to force the CSU to be in loopback mode. Options are normalRxCondition or forceCSUtoLoopback. Default = normalRxCondition. Selects the 56k CSU operating mode. Choices are: 4Wire-Primary-56k-DDS 72k-SecondaryChannel-DDS 64k-ClearChannel 2Wire-Primary-56k-DDS Default = 4Wire-Primary-56k-DDS
operatingMode
txControlMode
Used to select transmission of the 56k CSU Control Mode Idle sequence. Options are normalTxCondition and idle. Default = normalTxCondition. Used to select transmission of the All Marks (or 1s) of the Data Mode Idle sequence for all modes. Options are normalTxCondition and txidle. Default = normalTxCondition. Used to select transmission of the Out Of Frame sequence for the DDS-PRI mode, or transmission of the Multiplexer Out Of Sync sequence for the DDS-SC mode. Options are normalTxCondition and outOfFrame. Default = normalTxCondition. Used to select transmission of the Out Of Service sequence for the DDS-PRI mode, or transmission of the Abnormal Station Code sequence for the DDS-SC mode. Options are normalTxCondition and outOfService. Default = normalTxCondition Enables or disables transmit zero suppression for DDS-PRI mode, or the transmission of all zeros for DDS-SC mode. Options are normalTxCondition and disable. Default = normalTxCondition.
txIdle
txOutOfFrame
txOutOfService
zeroSuppression
For additional information on the optional T1 CSU configuration parameters, consult the Level One Data Book, LXT441 Switched 56/DDS Integrated DSU/CSU.
2-30
Network Administration
Identifying the Passport 4400 Assigning User Privileges Setting CLI Port Parameters Managing System Memory Banks Using System Rollback Setting the System Clock Enabling and Setting Traps Taking a Port Offline Monitoring Passport 4400 System Parameters Monitoring Passport 4400 Network Link Parameters
The Passport 4400 is designed to allow network administration and monitoring to take place using a workstation and the Command Line Interface (CLI). The workstation can be either locally attached to the management port on the Passport 4400 base module or remotely connected via the Ethernet access port on the base module.
Note: During periods of heavy user traffic, the CLI may become unresponsive. This is normal, as user traffic by default has priority over CLI requests. Should this occur, the CLI will resume operation as soon as the user traffic load decreases.
Most system administration functions are accessed using the set system command. When this command is entered at the CLI prompt, the following options are displayed:
administration communityString consolePort firmware rollback timeOfDay traps
When parameters are configured using the set command, the values take effect immediately and remain in effect until the Passport 4400 is reset or power-cycled. If you want the configured values to remain in effect after a reset, you must execute the save configuration update command prior to cycling the power or performing a reset.
3-1
Identifying the Passport 4400

As system or network administrator, you may want to uniquely identify each Passport 4400 at your location or throughout your network. The CLI of each Passport 4400 allows you to assign it a node name, a contact name and a location name or identifier. Enter the following command at the CLI prompt:
set system administration contact location nodeName
For each of the variables above, you can enter a string of one to 50 characters in length. The strings must be entered within quotation marks. (The string micom is reserved and should not be used.) Each string is a separate command and takes effect immediately. When you set a new node name, the CLI prompt immediately changes to the new node name followed by >>. Execute the save configuration update command if you want the node information to remain in effect after the next reset. To view the identity of a Passport 4400, enter the following CLI command:
show system administration ConfigVersion ObjectID UpTime Contact NodeName Location Services : : : : : : : "Passport_4400_Rel_2.0.0 03/05/98 16:36:08" "1.3.6.1.4.1.335.1.4" 00Years 010Days 02:51:20 "MIS Department" "D1_1" "4th Floor" 4
Assigning User Privileges

The CLI software allows you to assign different users to different privilege levels which either allow or prevent access to specific CLI utilities and functions. These privilege levels are controlled using CLI community string groups, which are linked to the SMNP community string concept. Each user logs into the CLI with a password that is associated with a particular community string index. The password allows access only to those functions linked by their MIBs to that community string index. The CLI provides two different categories of user privileges, with three privilege levels in each category. The privilege levels are applied to individual MIB files, with read/write access to the MIB restricted to those users logging in with the appropriate password. The CLI software is shipped with default passwords which can be changed if required. See Changing Community String Passwords later in this chapter.
3-2
Community String Indexes and Group Passwords To view the community string indexes and default passwords, enter the following command at the CLI prompt:
show system communitystring table StringIndex nSP-Configurator nSP-Operator nSP-Monitor customer-Configurator customer-Operator customer-Monitor StringCommunity "private" "public" "proxy" "regional" "core" "nortel"
Network service provider (NSP) community strings access capabilities that are typically assigned to a network administrator in the service provider domain. Customer community strings (also called virtual private network or VPN community strings) access capabilities that are typically handled by a user at a network branch location. The tables below show the passwords and privilege levels associated with each community string index.
Table 3-1. Read/Write Privileges for Network Service Provider String Indexes Group Privilege String Index nSP-Configurator nSP-Operator nSP-Monitor Default Password private public proxy Network Configurator Read/write Read only Read only Network Operator Read/Write Read/Write Read only Network Monitor Read only Read only Read only
Table 3-2. Read/write Privileges for Customer String Indexes Group Privilege String Index Customer-Configurator Customer-Operator Customer-Monitor Default Password regional core nortel Cust. Configurator Read/write Read only Read only Cust. Operator Read/Write Read/Write Read only Cust. Monitor Read only Read only Read only
3-3
MIB Assignments Each MIB is associated with both a network service provider (NSP) community string and a customer community string. The table below shows how each MIB maps to these two community string groups.
Table 3-3. MIB Community String Assignments
Privilege Level by Group MIB

Traffic management WAN Code download RFC 1398 DNA Ethernet GCM ISDN (RFC 2127) ISDN Dial Control (RFC 2128) ISDN (proprietary) 56K LMI RSI IP Bridge Bridge debug parameters Voice service T1/E1 RFC 1493 IP/IPX filters System System community string IPX Frame relay Frame relay global group RFC 1315 Frame relay circuit table Frame relay error table RFC 1213 System group
Network Service
Configurator Configurator Configurator Monitor Monitor Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Configurator Monitor Monitor Monitor Operator Operator
Customer
Configurator Monitor None Monitor Monitor Configurator Monitor Monitor Monitor Configurator Configurator Monitor Monitor Configurator Configurator Configurator Configurator Configurator Configurator Configurator Monitor None Configurator Monitor Configurator Monitor Configurator Monitor Monitor Monitor
3-4
Using the Assignment Tables to Determine User Privileges To determine which password to assign to a user, first determine which MIBs the user needs to access and the type of access required (read/write, or read only). Use the information in Table 3-3 to determine the community string group (Network Service or Customer) and the privilege level (Configurator, Operator, or Monitor) associated with the required MIBs. Then check Table 3-1 and Table 3-2 to determine which login password will provide the necessary privilege level. In the example below, three different users require different access to a set of MIBs
.
User #1 (NSP user) User #2 (NSP user) User #3 (Customer)
requires read/write access to the Frame Relay MIB, read/write access to the RFC 1213 MIB, and read/write access to the IPX MIB. requires read only access to the Frame Relay MIB, read/write access to the RFC 1213 MIB, and read only access to the IPX MIB. requires read only access to the Frame Relay MIB, RFC 1213 MIB, and the IPX MIB.
By examining Table 3-3, we learn that each of the MIBs listed above are associated with the following community string groups:
Frame Relay MIB RFC 1213 MIB IPX MIB associated with the Configurator group for NSP users and the Display group for Customer users. associated with the Operator group for NSP users and the Operation group for Customer users. associated with the Configurator group for NSP users and the Configuration group for Customer users.
By cross-referencing this information with the data in Table 3-1 and Table 3-2, we can determine which password to assign to each user.
User #1:
This user requires read/write privileges to MIBs in both the Network configurator and Network operator groups. Table 3-1 shows that only the nSP-Configurator password provides the necessary access to both groups.
User #2
This user requires read only privileges to two MIBs in the Network configurator group, and read/write privileges to one MIB in the Network operator group. Table 3-1 shows that the nSP-Operator password provides the necessary access.
User #3
This user requires read only privileges to MIBs in the Customer configurator, Customer operator, and Customer monitor groups. Table 3-2 shows that only the Customer-Monitor password provides the necessary access.
3-5
Changing Community String Passwords If necessary, the passwords providing access to each of the community string indexes can be changed to any user-defined string of 25 characters or less. Both alphabetic and numeric characters can be used; however, do not use the space character (ASCI 0x20 Hex) as this character may cause a parsing error. To change a password, enter the following command at the CLI prompt:
set system communitystring <StringIndex> : nSP-Configurator | nSP-Operator | nSP-Monitor | customer-Configurator| customer-Operator| customer-Monitor : "String" (1..25)
<StringCommunity>
Complete the command by entering the string index whose password you wish to change, followed by the new password within quotation marks. Remember that the new password takes effect immediately, but is not saved automatically. If for any reason the CLI session is terminated, you will need the new password in order to access the privilege level whose password you changed. If you want the new password to remain in effect after a system reset, execute the save configuration update command.
Caution:
The string micom is a reserved string and should not be used as a password or in any CLI command that requires a quoted string.
To display the passwords for all six privilege levels, use the following command:
The passwords shown above are the default passwords. To verify the privilege level of the current CLI session, use the following command:
show system privilege LastCommunPrivLev : nSP-Configurator
3-6
Note: When a password is changed, all users requiring access to the associated community string group must be notified. Once the password has been changed, all users in that group will be unable to access the CLI without the new password. This is particularly important when changing the nSP-configurator password. Telnet and SNMP access via the Ethernet port will also be affected.
Setting CLI Port Parameters

You can set the baud rate, data bits, stop bits and parity for the serial management port that is used for local CLI access to the Passport 4400 unit. Enter the following command at the CLI prompt:
set system consoleport baudRate dataBits parity stopBits
Valid values for each of the parameters are shown below.

set system consoleport baudrate <BaudRate> : 2400bps | 4800bps | 9600bps | 19200bps| 38400bps
set system consoleport databits <DataBits> : INTEGER (5..8)
set system consoleport parity <Parity> : off | even| odd
set system consoleport stopbits <StopBits> : INTEGER (1..2)
The default values for the management or console port are as follows:
<BaudRate> <DataBits> <Parity> <StopBits> 9600 bps 8 off 1
3-7
Managing System Memory Banks

The Passport 4400 utilizes an 8 megabyte nonvolatile Flash SIMM to store the operating software, which includes two types of data: boot code, consisting of a loader program, power-on self tests, diagnostics and other start-up information application code, which contains the operating system modules for the user services. An additional 128 kilobytes of non-volatile memory on the Ethernet Base Module stores the configuration information, which consists of factory default parameter values plus those parameter values set or changed by the user. All non-volatile memory is logically divided into five memory banks: one bank for boot code (Bank 0), two for application code and two for configuration data. Bank 1 and Bank 2 each contain one application file; Bank 3 and Bank 4 each store one configuration file. Thus, it is possible for the Passport 4400 to store two different versions of application code and two different versions of configuration data. (Only one version of boot code can be stored in Bank 0.) When the Passport 4400 is shipped from the factory, memory banks 1 and 2 each contain a copy of the application code, including the factory default configuration data. Memory banks 3 and 4 are empty. When the unit is powered on for the first time, the application code in Bank 1 is copied into RAM for execution, and the factory default configuration settings are copied into configuration banks 3 and 4. Setting Memory Bank Status Application code and configuration memory banks can be set to either a committed state or an uncommitted state. When a memory bank is set to committed, it becomes write-protected and cannot be overwritten or erased during a software download or a save configuration update operation. The application code that is in the committed bank is loaded into RAM when a system reset occurs. The application code and configuration information that are in the uncommitted banks are overwritten during a TFTP software download. Only one application code bank and one configuration bank can be set to committed at a time. At initial startup, all four memory banks are in the uncommitted state. If Bank 1 is set to committed, Bank 2 remains in the uncommitted state and is the software download bank. If subsequently Bank 2 is set to committed, Bank 1 is automatically toggled to the uncommitted state at the next reset, and the application code in Bank 2 is then loaded into RAM for execution. Configuration banks can be set to either active or inactive as well as to the committed or uncommitted states. The Passport 4400 always reads the active configuration bank when a reset occurs, and saves configuration changes to the uncommitted bank.
3-8
At initial startup, configuration Bank 3 is the active bank and also the configuration save bank. This means that when you do your initial provisioning and you save your changes and reset the unit, the configuration changes will be saved to Bank 3, and Bank 3 will be read and loaded during the reset. If subsequently you make other configuration changes and you want to save the previous configuration as a backup, then you must do the following:
1. Set configuration Bank 3 to the committed state. set system firmware commitconfigbank bank3 reset system current reset
This write-protects configuration Bank 3 and changes the configuration save bank from Bank 3 to Bank 4. Note that you must reset the Passport 4400 in order for this change to take effect.
2. Make your configuration changes and save them to Bank 4. save configuration update Note: The configuration bank that is in the committed state is also the active bank, which is the bank that is read and loaded when the unit is reset. Since Bank 3 has been set to committed, it is also the active bank. 3. Before resetting the Passport 4400, set Bank 4 to the active state so that your new
configuration values will be loaded during the reset.

set system firmware activeconfigbank bank4 Note: Only one configuration bank can be in the active state. When a configuration bank is set to active, the other configuration bank is automatically toggled to the inactive state. 4. Reset the Passport 4400 and verify the new configuration. reset system current reset 5. If the new configuration is valid and you want it to now become write-protected instead
of Bank 3, set Bank 4 to the committed state and perform another reset.
set system firmware commitconfigbank bank4 reset system current reset
3-9
When a new version of application software is downloaded to a Passport 4400 unit, the old version can be kept as a backup until the new version is verified. Since the downloaded code is always stored in the uncommitted bank, you will want to set to committed the bank you wish to keep as backup. Enter the following command at the CLI prompt:
set system firmware commitcodebank <CommitCodeBank> : bank1 | bank2
Select and enter either bank1 or bank2. The bank that is NOT committed is the bank to which the next software download is stored. For information on performing a software download, see Chapter 4, System Utilities. To set a configuration bank to the active status, use the following command:
set system firmware activeConfigBank <ActiveConfigBank> : bank3 | bank4
Select and enter either bank3 or bank4. Viewing Memory Bank Status To check on memory bank usage, enter the following command at the CLI prompt:
show system firmware OperationType CommitConfigBank ConfigSaveBank ActiveConfigBank ConfigReadBank CodeReadBank CommitCodeBank CodeVersion ConfigVersion : : : : : : : : accessRouter none bank3 bank3 bank3 bank1 bank1 "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08"
Note in this display that both configuration banks are still in the uncommitted state. The configuration save bank is the same as the active bank, so any configuration changes that are saved will overwrite the active configuration.
Note: The configuration read bank is always the same as the active configuration bank; the application code read bank becomes the same as the application code committed bank after a reset is performed.
3-10
Using System Rollback

System rollback is a Passport 4400 feature that protects the unit from potentially damaging configuration and/or application code changes. When system rollback is enabled, a five-minute timer starts running each time a code or configuration bank status change is made and a system reset is performed. If a confirm rollback confirm command is not entered at the CLI prompt before the timer expires, the application software and/or configuration information automatically revert back to the previous versions that were in the committed state before the reset occurred. In effect, the committed/uncommitted states of the two pairs of memory banks are reversed. System rollback is initially set to disabled at the factory. This is because both application code banks initially contain the same version of software, and both configuration memory banks are initially empty; there is no previous configuration or application code to revert back to. It is recommended that you use the following procedure with a new Passport 4400 unit that has been received from the factory.
1. Ensure that both configuration memory banks contain factory default settings. reset system default reset
This command clears both configuration banks, then loads them with the factory default settings during the boot cycle.
2. Perform initial provisioning, save the configuration values and reset the Passport 4400. save configuration update reset system current reset 3. Check your configuration; verify that it is correct and that all applications are
functioning.
4. Set configuration Bank 3 to the committed state and reset the unit. set system firmware commitconfigbank bank3
Initially, Bank 3 is the configuration save bank, the configuration read bank and the active configuration bank, but neither configuration bank is committed. By setting Bank 3 to committed, Bank 4 becomes the save bank for the next configuration change that is saved.
5. Enable system rollback. set system rollback enable Note: System rollback cannot be enabled unless one of the configuration banks is committed.
3-11
6. When the next configuration change is made and saved, set Bank 4 to the active state
before executing the reset command.

set system firmware activeconfigbank bank4 save configuration update reset system current reset
When the autoboot sequence begins, the newly-saved configuration in Bank 4 will be read and loaded into DRAM, and the rollback timer will start.
7. Verify that the new configuration is correct and that all applications are functioning
properly.
8. If the configuration is acceptable, execute the following command to turn off the
rollback timer.
confirm rollback confirm 9. If you do not intend to make any more configuration changes, disable the system
rollback feature.
set system rollback disable Note: Once system rollback has been enabled, it will remain enabled even after a reset. To disable it, you must execute the set system rollback disable command.
If you plan to make configuration changes to the Passport 4400, it is recommended that you enable system rollback as a safety measure. During subsequent operation, it is best to have system rollback disabled so that if an inadvertent reset occurs, you do not have to execute the confirm rollback confirm command in order to keep the current configuration. To check the current state of the system rollback feature, enter the following command at the CLI prompt.
show system rollback Feature Status : disable : not-required
If rollback is disabled, the status will always indicate not-required. If rollback is enabled, the status will be one of the following: required - configuration changes have been made, the unit has been reset, and the confirm rollback confirm command has NOT been issued. not-required - the unit has been reset, but no configuration changes have been made; rollback is not required even though it is enabled. next-reset - configuration changes have been made, but the unit has not yet been reset.
3-12
Note: When the status is required and a confirm rollback confirm command is executed, the status will change to not-required. Subsequently, if further configuration changes are made, the status will change to next-reset until a reset command is issued.
Setting the System Clock

The Passport 4400 has an internal battery-backed calendar and clock. The system displays the date in mm/dd/yyyy format, the time and the day of the week. To view the current calendar and clock setting, enter the following command at the CLI prompt.
show system timeofday 03/31/1998 20:37:31 Tuesday
To set the clock, enter the following command at the CLI prompt.
set system timeofday date day hour minute month second year
Enter one at a time each element you wish to set. The system will prompt you with the valid values for the element you select.
Enabling and Setting Traps

The Passport 4400 can generate SNMP trap messages for a variety of events and alarm conditions. The trap messages can be directed to a single network management workstation (NMS) or to multiple destinations. The destinations may be password-protected if desired. To enable trap generation, enter the following command at the CLI prompt:
add system trapsubscription <IPAddress> <CommunityString> : IPAddress : "String" (0..25)
Enter the IP address of the NMS workstation or other destination that you want to use to collect the trap messages. For CommunityString, enter a sequence of up to 25 characters. Be sure to enclose the string within quotation marks. Do not use the space character in the string (ASCII 0x20 Hex).
3-13
Enter the add system trapsubscription command separately for each destination to which you wish to send trap messages. To turn off or disable trap generation, enter the following command at the CLI prompt:
delete system trapsubscription
Then enter the IP address of the destination that you want to disable from receiving traps. To display a table of the IP addresses and passwords of the specified trap collectors, enter the following command:
show system trap trapsubscription
If there are no IP addresses in the trap subscription table, trap messages will not be generated. Enabling the Authentication Trap The command set snmp authentraps enabled causes the Passport 4400 to produce a generic trap whenever any client tries to access a specified trap collector using a bad community string (incorrect password). The community string is part of the clients request data that allows the SNMP agent to authenticate the validity of the clients request for access. The authentication trap is defaulted to the enabled condition. To check the setting of this trap, enter the following command:
show snmp statistics.
The last entry at the bottom of the right-hand column of the table indicates whether the authentication trap is enabled or disabled. To disable the authentication trap, enter the following command:
set snmp authentraps disabled
This command takes effect immediately; it is not necessary to reset the Passport 4400. Setting System Trap Thresholds When trap generation is enabled, the Passport 4400 is defaulted to generate a trap message whenever bandwidth utilization, CPU utilization, or RAM utilization reaches 90% of capacity. To change the utilization thresholds that will trigger these trap messages, enter the following command at the CLI prompt.
set system traps bandwidthUtilThres cpuUtilThres ramUtilThres
3-14
For each of the options above, enter an integer from 1 to 100 representing the utilization percentage that will trigger a trap message to be sent. Traps are sent to the IP address or addresses provisioned by the add system trapSubscription command. To view the current utilization percentages, enter the following command:
show system statistics CPUUtilization : 1 InterRAMUtilization : 45 LinkTxBWUtilization : 14 LinkRxBWUtilization : 0
Note: The LinkTxBWUtilization and LinkRxBWUtilization percentages shown in this table are based on the line speed that is indicated by the show wan parameters port configured table command. The baud rate shown on this display may not equal the actual bandwidth of the link. If there is a discrepancy, set the correct line speed using the define wan port baudrate command. For more information, see procedure 3 of Step 6 in Chapter 2, Getting Started.
Taking a Port Offline

The Passport 4400 provides the capability of taking a port offline for testing purposes or in the event of a malfunction or for any other reason. Enter the following command at the CLI prompt.
set port adminstatus <IfIndex> <AdminStatus> : INTEGER (1..255) : up | down| testing
To complete the command, enter the ifIndex of the port you wish to take offline (or return to active status) followed by the desired status.
3-15
Monitoring Passport 4400 System Parameters

The show command in the CLI facility provides access to a wide range of system characteristics, data and statistics. When you enter show system at the CLI prompt, the following options are displayed.
administration card chassisStatus commitTrack communityString configUpdate consolePort firmware hardware ifIndex image interfaceExtension physicalCard privilege restartReason rollback statistics system timeOfDay traps
Following are sample displays and parameter descriptions for the show system command options. show system administration
ConfigVersion ObjectID UpTime Contact NodeName Location Services : "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : "1.3.6.1.4.1.335.1.4" : 00Years 010Days 02:51:20 : "MIS Department" : "D1_1" : "Simi Valley CA" : 4
3-16
ConfigVersion ObjectID UpTime Contact NodeName Location Services
The release number, revision number and date of the installed factory default configuration file. A unique number for this device; assigned by the factory. The time the system has been running since the last reset. Contact name for this unit. Provisioned using set system administration. Unique name for this unit. Provisioned using set system administration. Location name for this unit. Provisioned using set system administration. Shows the number of software services currently in operation on this device.
show system card This command allows you to view information about a single module in the Passport 4400 or to view a table of all of the modules in the Passport 4400. The modules are designated as follows: Base module - limA Data modules - lim1 through lim4 Voice modules - limB through limE. Following is a sample display in response to a request to view limA, the Ethernet Base Module.
show system card entry lima LogicalInterfModule ModuleName PcbPartNumber PcbReleaseString SerialNumber ManufactureDate : : : : : : limA "EBM" "NTAU01AA" " " "NNTM03Y6792K" "092297"
3-17
show system chassisStatus

NumberOfSlots Type PowerSupplyCnt : 5Slots : typeB : 5 CoolingFan Status Redundant : running : fault : yes
NumberOfSlots Type PowerSupplyCnt CoolingFan Status Redundant
Indicates whether the Passport 4400 is a 3-Slot or a 5-Slot unit. Specifies the type of power supply based on the type of voltage. Type A = DC voltage; Type B = AC voltage. Indicates how many power supplies are in the unit. Indicates the status of the cooling fan. Indicates the general status of the unit. Possible indications are normal and fault. Indicates whether or not the unit contains a redundant power supply.
show system commitTrack

Counter SrcIPAddrLastCommit CommunityLastCommit TimeLastCommit : : : : 19 192.168.150.1 "micom" 00Years 016Days 20:38:00
Counter SrcIPAddrLastCommit CommunityLastCommit
The number of commit commands executed since the last default reset (cold start). The IP address of the SNMP manager that issued the last successful SET operation. Contains the community string (password) of the user who was logged into the CLI the last time a code or configuration bank was committed, or a confirm rollback confirm command was executed. This field is cleared after any reset, and the system inserts micom. The elapsed time since a code or configuration bank was last committed. The default is all zeros.
TimeLastCommit
show system communityString This command displays the current password for a single community string index, or the passwords for all of the community string indexes. Following is the default community string table.
3-18
show system consolePort

BaudRate DataBits : 9600bps : 8 StopBits Parity : 1 : off
This command displays the current baud rate, data bits, stop bits and parity settings for the management port on the Ethernet Base Module. These parameter values are set using the set system consoleport command. Refer to Setting CLI Port Parameters earlier in this chapter for default values and more information. show system firmware
OperationType CommitConfigBank ConfigSaveBank ActiveConfigBank ConfigReadBank CodeReadBank CommitCodeBank CodeVersion ConfigVersion : : : : : : : : accessRouter none bank3 bank3 bank3 bank1 bank1 "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08"
For an explanation of the memory banks and their contents, see Managing System Memory Banks earlier in this chapter. The other items in this display are described below.
OperationType CodeVersion ConfigVersion This parameter is not currently implemented. The release number, revision number and date of the currentlyrunning application code. The release number, revision number and date the configuration file was provisioned.
3-19
show system hardware

ModelType RevisionLevel ManufactureRevDate SerialNumber ModuleID MACAddress : : : : : : "68040" 8 "092297" "M03Y6792K" 2 00:60:38:05:01:bd
ModelType RevisionLevel
The model number of the microprocessor on the Passport 4400 Ethernet Base Module. The hardware revision level of the Ethernet Base Module.
ManufactureRevDate The manufacture date of the board identified by serial number below. SerialNumber ModuleID MACAddress The serial number of the Ethernet Base Module of this unit. Factory information only. The MAC address of the Ethernet port on the base module.
show system ifIndex This command allows you to view either the configured or the operational ifIndex list. Each Passport 4400 physical and virtual port is mapped to a specific ifIndex, which is a unique identifier that allows SNMP to read and write to a particular Physical Point of Attachment (PPA). These interface indices are used to establish logical links between physical or virtual ports and higher-level applications and protocol stacks. The Passport 4400 can support up to 255 ifIndices. Some of these are hard-coded and cannot be changed; others are automatically reserved by the Passport 4400 operating system when the unit is powered on. The quantity of ifIndices automatically reserved is dependent on the type and arrangement of modules that are present in the unit. The following ifIndex numbers are hard-coded.
Table 3-4. Hard-Coded IfIndex Numbers IfIndex 1 2 3 4 Description Logical interface for frame relay SVCs associated with frame relay pass-through on serial Port 1. Virtual port for user LAN traffic (frame relay). Virtual port for bridging. Virtual port for network management traffic (frame relay).
3-20
The Passport 4400 supports up to 19 WAN ports: 3 on the base module, and 8 on each of two available Data Expansion Modules (DEMs). The WAN ports are assigned fixed ifIndex numbers as shown in the tables below.
Table 3-5. Fixed IfIndex Assignments - Base Module Port Number 1 2 3 IfIndex - Port 150 153 156 IfIndex - Connector 151 154 157 IfIndex - Frame Relay 152 155 158
Table 3-6. Fixed IfIndex Assignments - Data Expansion Module 1 Port Number 1 2 3 4 5 6 7 8 IfIndex - Port 159 162 165 168 171 174 177 180 IfIndex - Connector 160 163 166 169 172 175 178 181 IfIndex - Frame Relay 161 164 167 170 173 176 179 182
Table 3-7. Fixed IfIndex Assignments - Data Expansion Module 2 Port Number 1 2 3 4 5 6 7 8 IfIndex - Port 183 186 189 192 195 198 201 204 IfIndex - Connector 184 187 190 193 196 199 202 205 IfIndex - Frame Relay 185 188 191 194 197 200 203 206
3-21
Note: When the hardware is installed, the port and connector ifIndex values are assigned. The frame relay ifIndex number is only assigned when the port is configured with a protocol support type of frameRelayDTE or frameRelayDCE.
Following is a typical IfIndex Table for a Passport 4400 containing two Data Expansion Modules (DEMs), configured as lim1 and lim2, and an Analog Voice Module configured as limB.
Ifindex 1 2 3 4 7 8 150 151 152 153 154 155 159 160 161 162 163 164 165 166 168 169 183 184 186 187 189 190 192 193 IfExtType ethernetCsmacd propVirtual other propVirtual other other propMultiplexor other frameRelayService propMultiplexor v35 frameRelay propMultiplexor other frameRelayService propMultiplexor other frameRelayService propMultiplexor other propMultiplexor other propMultiplexor other propMultiplexor other propMultiplexor other propMultiplexor other PPA 0 0 0 1 0 0 1 1 1 2 2 2 1 1 1 2 2 2 3 3 4 4 1 1 2 2 3 3 4 4 Slot limA limA limA limA limB limB limA limA limA limA limA limA lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim2 lim2 lim2 lim2 lim2 lim2 lim2 lim2
3-22
PPA Number
The Point of Physical Attachment (PPA) is not a literal physical point of attachment, but is an internal identifier for the Passport 4400 code. Each application module has one or more PPAs associated with it, but the PPA numbers are unique only within the module; they are not unique across all devices or slots. For physical interfaces, the PPA number corresponds to the physical port number on the module. For logical or virtual interfaces, the number corresponds to a logical port or interface and is dependent on the interface module type. If a device does not support PPAs, the value -1 is used to indicate that the field is not used as an identifier. show system image This command displays information about the software associated with each operational ifIndex in the Passport 4400. The display can be quite lengthy for a fully loaded and configured Passport 4400. Below is a sample display for ifIndices 1 and 2 only.
Index Bank Software Filename Version Size CommitStatus BurnCount Index Bank Software Filename Version Size CommitStatus BurnCount : : : : : 1 bank0 boot "BT2_0_0.BOOT" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.21 02/23/98 20:42:50" : 218848 : committed : 0 : : : : : 2 bank1 code "PR2_0_0.CMP" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : 1430064 : committed : 2
The items in this display pertaining to each ifIndex are described in the table below.
3-23
Bank Software Filename Version Size CommitStatus BurnCount
The memory bank where the software module for this ifIndex is stored. The type of software: boot, code, or config. The filename of the software module running on this ifIndex. The release number and revision level of the software module. The size of the software module in bytes. Committed (write-protected) or uncommitted. The number of writes to Flash memory that have occurred since the last default reset (cold start).
show system interfaceExtension This command allows you to view extended information about a single configured or operational ifIndex, or to display the information for all configured or operational ifIndices. The example shown below is a portion of the display from the show system interfaceextension operational table command.
Ifindex IfExtName IfExtType LnkUpDownTrapEnable ConnectorPresent PersistenceType IfExtState PPA Slot Channel PPADevicesType Ifindex IfExtName IfExtType LnkUpDownTrapEnable ConnectorPresent PersistenceType IfExtState PPA Slot Channel PPADevicesType : : : : : : : : : : : : : : : : : : : : : : 1 "CARD/1 EN/1" ethernetCsmacd yes yes non-volatile configured 0 limA -1 ethDriver 2 0 propVirtual yes no non-volatile configured 0 limA -1 dataVP
3-24
IfExtName IfExtType LnkUpDownTrapEnable ConnectorPresent PersistenceType IfExtState PPA Slot
A pre-programmed interface name. If the interface does not have a name, a 0 is used. The type of interface. Indicates whether or not a trap will be generated when the link goes UP or DOWN. Yes if the interface is physical; No if the interface is logical or virtual. Indicates whether the Persistence Type is volatile or nonvolatile. Indicates whether or not this ifExt entry is configured. The PPA number of the interface. Assigned internally. See show system ifIndex for more information. The Logical Interface Module (LIM) name that the Passport 4400 uses to identify the interface. The Ethernet Base Module is always limA; data modules are named lim1 through lim4, and voice modules are named limB through limE. Used for serial data connections and for DSP voice channels. See explanation below. Indicates the PPA device type of this interface.
Channel PPADevicesType
Channel Number
The channel number is used along with the slot and PPA number to uniquely identify an interface within a device type; however, the channel number itself is not unique across all device types. For interfaces describing serial data connections (data ports), the channel number refers to the physical data channel. For interfaces describing DSP voice channels, the channel number refers to the corresponding voice channel number. For interface types that do not use channel number, the value of -1 is used. show system physicalCard This command displays either a single physical slot number and the name of the interface module in that slot, or it displays a table of all physical slot numbers and the names of the interface modules installed. Below is a sample display for a 5-Slot unit with two data modules and one voice module installed.
1 2 3 4 5 limA lim1 lim2 limB none
3-25
show system privilege

LastCommunPrivLev : nSP-Configurator
This command displays the community string privilege level you are currently logged in at on the CLI port. The nSP-Configurator level is the highest privilege level available. To view the complete list of privilege levels and the passwords required to reach each level, use the show system communitystring table command. show system restartReason
RestartReason : hwButtonCurrentReset
This command displays the type of reset (CPU, current, or default) that last occurred on the Passport 4400. If the last reset was initiated by the system, the display will indicate : Unknown for the restart reason. If the Passport 4400 is power-cycled for any reason, the display will indicate UnknownHardwareFault. Other possible RestartReason responses are the following:
cliCurrentReset hwButtonOrCLICPUReset hwButtonDefaultUnknownSWState
show system rollback

Feature Status : disable : not-required
This command shows whether system rollback is currently enabled or disabled. If rollback is disabled, the status will always indicate not-required. If rollback is enabled, the status will be one of the following: required - configuration changes have been made, the unit has been reset, and the confirm rollback confirm command has NOT been issued. not-required - the unit has been reset, but no configuration changes have been made; rollback is not required even though it is enabled. next-reset - configuration changes have been made, but the unit has not yet been reset.
Note: When the status is required and a confirm rollback confirm command is executed, the status will change to not-required. Subsequently, if further configuration changes are made, the status will change to next-reset until a reset command is issued.
3-26
show system statistics

CPUUtilization : 1 InterRAMUtilization : 45 LinkTxBWUtilization : 14 LinkRxBWUtilization : 0
This command displays the current utilization percentages for the Passport 4400 CPU, internal RAM, and link bandwidth.
Note: The LinkTxBWUtilization and LinkRxBWUtilization percentages shown in this table are based on the line speed that is indicated by the show wan parameters port configured table command. The baud rate shown on this display may not equal the actual bandwidth of the link. If there is a discrepancy, set the correct line speed using the define wan port baudrate command. For more information, see procedure 3 of Step 6 in Chapter 2, Getting Started.
show system system

CPUConfig PrimaryWANPort PriWANPortPhyMedia DCESerPortPhyMedia QUICCExpanModule1 QUICCExpanModule2 RTCBatteryStatus DRAMSize FlashMemorySize : : : : : : : : : companion040 present generalserial v35 notPresent notPresent batteryOK 8 Mbytes 8 Mbytes
This command displays hardware configuration information pertaining to the Passport 4400 unit as a whole. Parameters that may not be self-explanatory are dcescribed below.
CPUConfig PriWANPortPhyMedia The name of the CPU physically installed in the unit. The type of interface installed in Port 2 of the Base Module. Options are general serial, ISDN, 56K, T1, unknown, and none. The physical characteristics of the DCE serial port on the Base Module. Options are RS-232, V.35, V.36, X.21, unknown, and none.
DCESerPortPhyMedia
3-27
show system timeOfDay

03/31/1998 20:37:31 Tuesday
This command displays the system calendar and clock. The date is displayed in mm/dd/yyyy format. If the output is incorrect, you can update the clock using the set system timeofday command. show system traps The Passport 4400 system traps pertain to CPU utilization, bandwidth utilization, and internal RAM utilization. This command gives you the following two display choices.
trapSubscription threshold
The trapSubscription option allows you to view the IP addresses and community strings (passwords) of the workstations that have been configured to receive trap messages. You can select entry and enter a single IP address to check its password, or you can select table and view all of the IP addresses and their passwords. The threshold option displays the current utilization percentages that will trigger trap messages to be sent to the designated network management stations. The default threshold percentages are 90%.
3-28
Monitoring Passport 4400 Network Link Parameters

The following show commands provide general information about network parameters, operational characteristics and performance: show port show msm show snmp show traps Other show commands provide network information pertaining to specific user services such as LAN, frame relay, ISDN, and so forth. These commands and the information they provide are covered in the chapters dealing specifically with the user services. Show Port Command When you enter this command at the CLI prompt, the following options are displayed.
ifNumber parameters
The ifnumber option is not currently used. The parameters option allows you to view communications parameters for a single ifIndex or for all of the configured ifIndexes in the Passport 4400. Below is a sample display for ifIndex 4, the virtual port used for carrying network management traffic.
3-29
show port parameters entry 4 IfIndex Description IfType Mtu Speed PhysAddress AdminStatus OperStatus LastChange RxOctets RxUnicastPackets RxNonUnicastPackets RxDiscards RxErrors RxUnknownProtocols TxOctets TxUnicastPackets TxNonUnicastPackets TxDiscards TxErrors TxQueueLength Specific : : : : : : : : : : : : : : : : : : : : : : 4 "FrameRelay Virtual Port" other 0 0 up up 00Years 000Days 00:00:00 573240 2958 0 0 0 0 620 31 0 0 0 0 "0.0"
Description IfType
A textual string containing information about the interface. The type of interface, distinguished according to the physical or link protocol(s) immediately below the network layer in the protocol stack; for a virtual interface, the type is Other. Maximum Transfer Unit. The size in octets of the largest datagram that can be sent or received on this interface. An estimate of the current bandwidth of the interface in bits per second (bps). The address of the interface at the protocol layer immediately below the network layer in the protocol stack. For interfaces not having such an address, an octet string of zero length will be shown. Indicates whether the interface will be UP DOWN, or in the , Testing state when the next reset occurs. In the Testing state, no operational packets can be passed. The current operational state of the interface. The value of SysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last system reset, this field will contain a zero value. The number of octets received on this interface since the last reset of the counters, including framing characters.
Mtu Speed PhysAddress
AdminStatus
OperStatus LastChange
RxOctets
3-30
RxUnicastPackets RxNonUnicastPackets RxDiscards
The number of subnetwork-unicast packets delivered to a higher-layer protocol since the last reset of the counters. The number of subnetwork-broadcast or subnetwork-multicast packets delivered to a higher-layer protocol. The number of inbound packets on this interface that were discarded even though no errors were detected to prevent them from being deliverable to a higher-layer protocol. The number of inbound packets that contained errors, thus preventing them from being deliverable to a higher-layer protocol. The number of packets received on this interface that were discarded because of an unknown or unsupported protocol. The total number of octets transmitted out of this interface since the last reset of the counters, including framing characters. The total number of packets that higher-layer protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent. The total number of packets that higher-layer protocols requested be transmitted to a subnetwork-broadcast or subnetwork-multicast address, including those that were discarded or not sent. The number of outbound packets on this interface that were discarded even though no errors were detected to prevent them from being transmitted. The number of outbound packets on this interface that could not be transmitted because of errors. The number of bytes of memory in the transmit queue for this interface. A reference to MIB definitions specific to the particular media being used for this interface.
RxErrors
RxUnknownProtocols TxOctets TxUnicastPackets
TxNonUnicastPackets
TxDiscards
TxErrors TxQueueLength Specific
Show msm Command This command provides information about the MPANL link between the Passport 4400 and the Passport switch device. When you enter this command at the CLI prompt, the following options are displayed.
dteLink dteLinkStatus profile statistics
The information provided by each of the options above is shown in the examples below. The configured values may be different from the operational values if the configuration has been changed but the unit has not yet been reset.
3-31
show msm dteLink This command allows you to view DTE link information for either or both of the physical ifIndices used for the MPANL link between the Passport 4400 and the Passport switch. The sample display below is for the primary WAN link on ifIndex 155.
IfIndex : 155 (operational) : 155 (configured) : 63 (operational) : 63 (configured) : 64000 (operational) : 64000 (configured) : 64000 (operational) : 64000 (configured) : 80 (operational) : 80 (configured)
MaxSubChannelRange
DTEReceiverBW
DCEReceiverBW
DTEMaxFrameSize
DCEMaxFrameSize
: 80 (operational) : 80 (configured) ---------------------------------------------------------------
MaxSubChannelRange DTEReceiverBW DCEReceiverBW DTEMaxFrameSize DCEMaxFrameSize
The highest DLCI number that can be used on this link. The maximum allowable DLCI on the MPANL link is 255. The maximum throughput in bits per second that the MPANL DTE (normally the Passport 4400) is capable of receiving. The maximum throughput in bits per second that the MPANL DCE (normally the Passport FP) is capable of receiving. The maximum size in bytes of frames transmitted by the Passport 4400 to the Passport switch. The maximum size in bytes of frames received by the Passport 4400 from the Passport switch.
Note: The operational values of DTEReceiverBW and DCEReceiverBW shown in the table above correspond to the values that have been provisioned for the MPANL ifIndex on the Passport 4400. If the provisioned values do not match the values configured on the Passport switch, then this table will not indicate the actual line speed of the MPANL link, since the Passport switch, acting as DCE, controls the line speed. It is not possible to display the actual line speed via the CLI if the provisioned line speed does not match the actual line speed as determined by the Passport switch.
3-32
show msm dteLinkStatus This command allows you to view DTE link status for either or both of the physical ifIndices used for the MPANL link between the Passport 4400 and the Passport switch. The sample display below is for the primary WAN link on ifIndex 155.
IfIndex LAPFStatus LocalComponentName RemoteComponentName : : : : 155 up "MPA/D1_1 MPANL/155" "EM/CONF2 Mpanl/600 SigMpanl"
LAPFStatus LocalComponentName
The status (UP or DOWN) of the Link Access Procedure for Frame-mode bearer services on the MPANL link. MPA is a pre-programmed identifier for the Passport 4400; D1_1 is the configured node name; MPANL/155 is a system-generated identifier indicating the ifIndex number of the physical port providing the MPANL link.
RemoteComponentName Generated by the Passport 4400 software after the MPANL link has been established; CONF2 is the node name of the Passport switch.
show msm profile

NodeId : 1 (operational) : 1 (configured) : 0 (operational) : 0 (configured)
CustomerId
DNAPrefix
: "[x121]302181140160" (operational) : "[x121]302181140160" (configured) ---------------------------------------------------------------
NodeId
An integer from 1 to 65535 that uniquely identifies a Passport 4400 unit. Used as an index into the MSM Profile Table. Provisioned using define msm profile nodeid. An integer from 0 to 65535 that uniquely identifies the customer to which this Passport 4400 unit belongs; used in registering the Egress table. Provisioned using define msm profile customerid. The prefix of the Directory Network Address that uniquely identifies this Passport 4400 unit within the network topology.
CustomerId
DNAPrefix
3-33
show msm statistics This command allows you to view MPANL switch map connection statistics for either or both of the physical ifIndices used for the MPANL link between the Passport 4400 and the Passport switch. The sample display below is for the primary WAN link on ifIndex 155.
IfIndex 155 Reestablished 0 Established 1 Disconnects 0
This display shows the number of MPANL switch map links established, the number of disconnects that have occurred and the number of times the link has been reestablished. Show SNMP Command This command allows you to view statistics regarding SNMP communications. Note that some of the parameters in the display will be zero-valued in implementations that are optimized to support only those functions specific to either a management agent or a management station. Note also that the parameters in the display refer to an SNMP entity, of which there may be several residing on a managed node. To view the SNMP parameters, enter the command as shown below.
show snmp statistics RxPackets RxBadVersions RxBadCommunityUses RxTooBigs RxBadValues RxGeneralErrors RxValidSets RxGetNexts RxGetResponses TxTooBigs TxBadValues TxGetRequests TxSetRequests TxTraps : : : : : : : : : : : : : : 64 0 0 0 0 0 5 52 0 0 0 0 0 0 TxPackets RxBadCommuni RxASNParseErrors RxNoSuchNames RxReadOnlys RxValidGet/GetNexts RxGetRequests RxSetRequests RxTraps TxNoSuchNames TxGeneralErrors TxGetNexts TxGetResponses AuthenTraps : 63 : : : : : : : : : : : : 0 0 0 697 7 5 1039 0 0 0 63 enabled
RxPackets TxPackets RxBadVersions
The total number of SNMP messages delivered to the SNMP entity from the Passport 4400. The total number of SNMP messages passed from the SNMP entity to the Passport 4400. The total number of SNMP messages delivered to the SNMP entity which were for an unsupported SNMP version.
3-34
RxBadCommuni
The total number of SNMP messages delivered to the SNMP entity which used an SNMP community name not known to the entity.
RxBadCommunityUses The total number of SNMP messages delivered to the SNMP entity which represented an operation not allowed by the SNMP community named in the message. RxASNParseErrors RxTooBigs RxNoSuchNames RxBadValues RxReadOnlys The total number of ASN.1 or BER errors encountered by the SNMP entity when decoding received SNMP messages. The total number of SNMP PDUs delivered to the SNMP entity for which the value of the error-status field is tooBig. The total number of SNMP PDUs delivered to the SNMP entity for which the value of the error-status field is noSuchName. The total number of SNMP PDUs delivered to the SNMP entity for which the value of the error-status field is badValue. The total number of valid SNMP PDUs delivered to the SNMP entity for which the value of the error-status field is readOnly. Note: It is a protocol error to generate an SNMP PDU which contains readOnly in the error-status field. This object provides a means of detecting incorrect implementations of the SNMP. RxGeneralErrors RxValidGet/GetNexts The total number of SNMP PDUs delivered to the SNMP entity for which the value of the error-status field is genErr. The total number of MIB objects that have been received successfully by the SNMP entity as a result of valid Get-Request and Get-Next PDUs. The total number of MIB objects that have been altered successfully by the SNMP entity as a result of valid Set-Request PDUs. The total number of Get-Request PDUs that have been accepted and processed by the SNMP entity. The total number of Get-Next PDUs that have been accepted and processed by the SNMP entity. The total number of Set-Request PDUs that have been accepted and processed by the SNMP entity. The total number of Get-Response PDUs that have been accepted and processed by the SNMP entity. The total number of SNMP Trap PDUs that have been accepted and processed by the SNMP entity. The total number of SNMP PDUs generated by the SNMP entity for which the value of the error-status field is tooBig. The total number of SNMP PDUs generated by the SNMP entity for which the value of the error-status field is noSuchName.
RxValidSets
RxGetRequests RxGetNexts RxSetRequests RxGetResponses RxTraps TxTooBigs TxNoSuchNames
3-35
TxBadValues TxGeneralErrors TxGetRequests TxGetNexts TxSetRequests TxGetResponses TxTraps AuthenTraps
The total number of SNMP PDUs generated by the SNMP entity for which the value of the error-status field is badValue. The total number of SNMP PDUs generated by the SNMP entity for which the value of the error-status field is genErr. The total number of Get-Request PDUs generated by the SNMP entity. The total number of Get-Nextt PDUs generated by the SNMP entity. The total number of Set-Request PDUs generated by the SNMP entity. The total number of Get-Response PDUs generated by the SNMP entity. The total number of SNMP Trap PDUs generated by the SNMP entity. Indicates whether or not authentication traps have been enabled. The default setting is enabled.
Show Traps A list and explanation of all Passport 4400-generated traps is contained in Appendix A of this manual.
3-36
System Utilities
Software Download Procedures Upgrading to Release 2.0 Telnet Access System Reset Reset Counters Ping Utility
TFTP Software Download

Downloading system software is part of the Passport 4400 network management functionality, but can also be initiated from the CLI. Runtime TFTP software download requires TFTP configuration on the network management workstation and a properly configured Passport ILS Network Management Core Router (NMCR) to provide management IP connectivity to the branch Passport 4400. For information on setting up the network management workstation for TFTP download, see Chapter 2, Getting Started. To download a new version of software to a Passport 4400, you must perform two separate download procedures: download the file containing the boot code download the application code There are two methods that may be used to accomplish a TFTP download:
1 2 Set the source and target IP addresses and download filename before invoking the download command, then execute the download base code default command. Execute the download base code specific command and set the parameters one by one on the fly.
Each of these methods has its own advantages depending on your application environment. In the instructions below, we will download the boot code using the default download option; we will download the application code using the specific option.
Note: You can download software to only one Passport 4400 at a time.
4-1
System Utilities
Preliminary TFTP Download Provisioning If you are downloading software over a network, the Passport 4400 must have NMS connectivity and TFTP site access as described in Chapter 2, Getting Started. You should be able to ping the NMS workstation where the software download site has been installed. If you have already accomplished this setup, proceed to Default Download Procedure or Specific Download Procedure. If you have not already completed the steps in Getting Started, perform the steps below.
1. Configure the Passport 4400 for IP routing. define bridge global ip routed Note: Depending on where the NMS workstation is located in your network, this command may or may not be required. 2. Configure ifIndex 4 for passive RIP. define ip base parameter routeprotocoltype 4 passiverip
This setting is recommended in order to prevent the IP address for ifIndex 4 from being broadcast throughout the network. (Remember that ifIndex 4 is used for network management traffic only.)
3. Enable inverse ARP on ifIndex 4. define ip invarp 4 ip enabled 4. Enable RIP on the Passport 4400. define ip base rip on 5. If you have not already done so, enter the IP address of ifIndex 4 on the Passport 4400. add ip address entry 4 <IPAddress> <NetMask> <BcastAddress> : IPAddress : Sub-NetMask : IPAddress
For IPAddress, make sure that the address you enter is on the same subnet as the IP address of the NMCR protocol port. (In the example in Chapter 2, the IP address of the NMCR protocol port is 100.100.1.1; the IP address of ifIndex 4 on the Passport 4400 is 100.100.1.150.) For NetMask, enter 255.255.255.0 (or whatever is appropriate for your network). For BcastAddress, enter 255.255.255.255, or the address of the subnet with the subnetspecific address masked off.
4-2
System Utilities
6. Save the configuration and reboot the Passport 4400. save configuration update reset system current reset 7. If you have not already done so, establish a static route to the network containing the
TFTP server.
add ip route <DestAddress> <IfIndex> <Metric> <NextHop> <NetMask> : : : : : IPAddress INTEGER (1..255) INTEGER (2..15) IPAddress IPAddress
For DestAddress, enter the IP subnet address of the TFTP server. The IfIndex is 4 for network management traffic. The Metric is the number of hops from the TFTP server to the Passport 4400. For NextHop, enter the IP address of the Passport protocol port used for network management traffic. (The example below is from Chapter 2, Getting Started.) Example: add ip route 192.168.15.0 4 2 100.100.1.1 255.255.255.0
The diagram below shows a typical TFTP software download scenario using the IP addresses given as examples in Chapter 2 and in the provisioning steps above.
Frame Relay
100.100.1.1
Management Port
IfIndex 4 100.100.1.150 Passport UCR Passport NMCR NMS Workstation 192.168.15.30
PC
Figure 4-1. Typical TFTP Software Download Setup
4-3
System Utilities
Default Download Procedure

1. Enter the IP address of the UNIX workstation that has TFTP installed and that contains
the download code files.

set tftp serveripaddress <ServerIPAddress> 2. Enter the filename of the boot code file. set tftp remoteFileName <RemoteFileName>
Remember to enclose the filename within quotation marks. If you need to specify the path to where the file is located, include the path inside the quotation marks also. (An example of this is given in Step 1 of the Specific Download Procedure in this chapter.
3. Optional. The set tftp command provides options allowing you to set a timeout
value in seconds, and a retry count.

set tftp timeout <TimeOut> : INTEGER (0..900) secs
The TFTP download command will time out if it cannot locate the remote file and begin transferring it within this period of time. The default value is 10 seconds.
set tftp retransmissioncount <RetransmissionCount> : INTEGER (0..100)
The download command will automatically retry the download (if a failure is detected) as many times as is indicated by this parameter. The default value is 3.
4. Save the configuration and reset the Passport 4400. save configuration update reset system current reset 5. Display the TFTP parameters you have configured and verify that they are correct. (The
information displayed below is for the purpose of illustration only.)

show tftp parameters ServerIPAddress RemoteFileName TimeOut RetransmissionCount : : : : : : : : 192.168.15.30 (operational) 192.168.15.30 (configured) bt2000023.bld (operational) bt2000023.bld (configured) 10 (operational) 10 (configured) 3 (operational) 3 (configured)
4-4
System Utilities
show ip route table DestAddress 192.168.15.0 100.102.1.2 IfIndex 4 4 Metric 2 1 NextHop 100.100.1.1 100.100.1.150 Type local local NetMask 255.255.255.0 255.255.255.0
This table shows the static route that was set up in Chapter 2 (or in Step 7 above) to the network containing the TFTP server. The Metric is the number of hops from the TFTP server to the Passport 4400.
6. Enter the command to download the new code using the default option. download base code default
The Command Successful message will appear and the download will begin.
Note: The Command Successful message does not mean that the download was successful; it only means that the command was understood and accepted by the Passport 4400. 7. To monitor the status and progress of the download, use the following commands: show tftp state State : downloading
This command will display the state of the download operation at the time the command is executed. Possible states are idle and downloading.
show tftp error LastOperStatus ServerIPAddr FileName : retrieving-file : 192.168.15.30 : "bt2000023.bld"
Possible values for LastOperStatus are:

idle - download is not currently in progress retrieving-file - download is in progress timeout - download was attempted but timed out (perhaps due to an incorrect IP addrress server-error - download failed because of an error on the TFTP server download successful - download completed successfully
4-5
System Utilities
8. After the download is complete, verify that the new boot code is in Bank 0. show system image Index Bank Software Filename Version Size CommitStatus BurnCount : : : : : 1 bank0 boot "BT2_0_0.BOOT" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.23 02/23/98 20:42:50" : 218848 : committed : 0
The show system image command will display data for several ifIndices, but the only ifIndex of interest at this point is ifIndex 1. After the boot code has been successfully downloaded, you are ready to download the application code. For this procedure we will use the download base code specific command. Specific Download Procedure
1. Enter the command to download the new code using the specific option. download base code specific <ServerIPAddress> <RemoteFileName> : IPAddress : "String" (1..50)
Enter the IP address of the TFTP workstation followed by the filename of the application code enclosed in quotation marks:
download base code specific 192.168.15.30 "pr2000031.bld"
The Command Successful message will appear and the download will begin.
Notes: If the extended path of the download file has not been specified in the inetd.conf file on the TFTP server (see Step 3 in Chapter 2, Getting Started) you may include the path within the quotation marks in the download base code specific command. For example, if the download file is in a tftpboot subdirectory named pp4400, and you did not edit the inetd.conf file to specify this subdirectory, then you would include the subdirectory in the quoted string as follows: /pp4400/pr2000031.bld. The Command Successful message does not mean that the download was successful; it only means that the command was understood and accepted by the Passport 4400. Once this command is performed, the IP address, path and file name used become the default source used by the download base code default command.
4-6
System Utilities
2. To monitor the status and progress of the download, use the following commands: show tftp state State : downloading
This command will display the state of the download operation at the time the command is executed. Possible states are idle and downloading.
show tftp error LastOperStatus ServerIPAddr FileName : retrieving-file : 199.30.24.10 : "pr2000031.bld"
Possible values for LastOperStatus are idle, retrieving-file, timeout, server-error, and download successful.
3. After the download is complete, verify that the new application code image is in Flash
banks 1 or 2, and that there are new configuration files in banks 3 and/or 4.
show system image Index Bank Software Filename Version Size CommitStatus BurnCount Index Bank Software Filename Version Size CommitStatus BurnCount : : : : : 1 bank0 boot "BT2_0_0.BOOT" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.23 02/23/98 20:42:50" : 218848 : committed : 0 : : : : : 2 bank1 code "PR2_0_0.CMP" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.26 02/03/98 14:34:57" : 1427768 : committed : 20
4-7
System Utilities
[Q to Quit or Carriage Return to Continue] Index Bank Software Filename Version : : : : : 9 bank2 code "PR2_0_0.CMP" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : 1430064 : notCommitted : 1515870836
Size CommitStatus BurnCount . . . [Q to Quit or Carriage Return to Continue] Index Bank Software Filename Version Size CommitStatus BurnCount Index Bank Software Filename Version Size CommitStatus BurnCount : : : : :
16 bank3 config "PR2_0_0.CFG" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.23 02/03/98 14:34:57" : 65536 : committed : 0 : : : : : 17 bank4 config "PR2_0_0.CFG" "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : 65536 : notCommitted : 0
Notes: Notice from the display that the new application code was loaded into banks 2 and 4, (which had to be uncommitted in order to receive the download). This means that banks 1 and 3 were in the committed state when the download occurred. Had Bank 1 and/or Bank 3 not been in the committed state when the download took place, the new software would have been downloaded to those banks as well. To activate the new application code upon reset, you must change the status of Bank 2 to committed.
4-8
System Utilities
4. Set Bank 2 to committed; set Bank 4 to active if you want to load the default configu-
ration values for the new version of software.

set system firmware commitcodebank bank2 set system firmware activeconfigbank bank4 5. Reset the Passport 4400 to activate the new software. reset system current reset 6. Check to make sure the Passport 4400 booted up with the new software. show system firmware OperationType CommitConfigBank ConfigSaveBank ActiveConfigBank ConfigReadBank CodeReadBank CommitCodeBank CodeVersion ConfigVersion : : : : : : : : accessRouter bank4 bank3 bank4 bank4 bank2 bank2 "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08" : "Passport_4400_Rel_2.0.0_Rev_AX 0.0.31 03/05/98 16:36:08"
After a specific download is complete, if you enter the show tftp parameters command before executing a reset, you will notice that the server IP address and application code filename are displayed as operational but not configured.
show tftp parameters ServerIPAddress : 199.30.24.10 (operational) : 0.0.0.0 (configured) : "pr2000031.bld" (operational) : "" (configured) : 10 (operational) : 10 (configured)
RemoteFileName
TimeOut
RetransmissionCount : 3 (operational) : 3 (configured) -------------------------------------------------------------
If you enter the show tftp parameters command after resetting the Passport 4400, the server IP address and application code filename become configured as well as operational. These parameters are used the next time a default download procedure is executed.
4-9
System Utilities
Upgrading to Release 2.0

If you have received a new Passport 4400 that does not already contain Release 2.0 software, or if you wish to upgrade an existing Passport 4400 from an earlier version of software to Release 2.0, you can obtain the latest application code, boot code and MIB files on CD-ROM by ordering from your sales representative, or electronically through Magellan Access Global Technical Support (GTS) upon request. The files included in the Release 2.0 package are described below. Passport 4400 boot ROM code (bt20000xx.bld, where xx represents the latest build of the boot ROM code) Passport 4400 application code (pr20000yy.bld, where yy represents the latest build of the Release 2.0 software) Passport 4400 application code for MIBs (pr20000yy.tar) Passport 4400 Supplement for R2.0.0 (Release Notes: rs20000yy.ps) Passport 4400 configuration data from previous software releases is not forward-compatible with Release 2.0. As a result, when Release 2.0 boot code and application software is downloaded to the alternate Flash memory bank and set to the committed state, a cold reset is required. This type of reset restores the Passport 4400 to factory default settings, necessitating reconfiguration of the unit. To reconfigure the Passport 4400, it is recommended that you follow the steps in Chapter 2, Getting Started. Refer also to document 800-1953-20, Passport 4400 Supplement for R2.0.0 for information on performing a branch by branch cutover to Release 2.0 software.
4-10
System Utilities
TELNET Utility
The Passport 4400 allows remote access to the CLI via the TELNET protocol. You can run TELNET on a UNIX workstation or on a PC and access any Passport 4400 that is on the same IP subnet or that has a static route provisioned from the PC or workstation to the IP subnet of the Passport 4400. The diagram below shows several telnet possibilities.
Port 1 Passport 4400 #2 Frame Relay Telnet Workstation 2 192.168.37.1
Passport Switch 192.168.15.30 Passport 4400 #1
Port 2 200.202.38.1 Port 2 200.202.37.1
Port 1 192.168.38.1
192.168.37.10
Telnet Workstation 1
192.168.38.10
Figure 4-2. TELNET Access to the Passport 4400
Telnet Workstation 1 can access each of the Passport 4400s as follows: Passport 4400 #1 - telnet 192.168.38.1 Passport 4400 #2 - telnet 200.202.37.1 Telnet Workstation 2 can access each of the Passport 4400s as follows: Passport 4400 #1 - telnet 200.202.38.1 Passport 4400 #2 - telnet 192.168.37.1
4-11
System Utilities
System Reset
The Passport 4400 can be rebooted using CLI commands or by pressing a reset button on the rear panel of the Ethernet Base Module. Three levels of system reset are supported: CPU Reset - The CPU is restarted without diagnostics and without reloading the application code and configuration information into DRAM. Warm Start - The CPU is restarted, diagnostics are run, and the committed application code and configuration banks are loaded into DRAM. Cold Start - The CPU is restarted, diagnostics are run, the committed application code bank and the factory default configuration information is loaded into DRAM. To perform each of these resets using the CLI, enter the following commands: CPU Reset - reset system cpu reset Warm Start - reset system current reset Cold Start - reset system default reset
Reset Counters
The Passport 4400 enables you to reset statistical counters at any time without resetting the entire unit. When reset counters is entered at the CLI prompt, the following options appear:
bridge ethernet fr icmp ip ipx isdn msm rsi snmp tcp tm t1e1 udp voice wan
4-12
System Utilities
Most of the reset counters options allow you to zero out the counters in a corresponding statistics table that can be displayed using a corresponding show command. Other options allow you to zero out statistics for a specific port or ifIndex or circuit or DLCI. Brief descriptions of some of the reset counters options are given below. For further information, consult the chapter on utility verbs in document 800-1950-20, Passport 4400 CLI Command Reference.
reset counters bridge base port <IfIndex> <Action> : INTEGER (1..32) : clear
Resets the counters for the specified ifIndex for frames discarded due to excessive transit delay (DelayExDiscards) and excessive size (MtuExDiscards). These counters are displayed by executing the show bridge basic port entry command.
reset counters bridge spanningtree allPorts port
Resets the FwdTransitions counter associated with the show bridge spanningtree port command. You can reset the counter for a single port by selecting port and identifying its ifIndex number, or you can reset the counter for all spanning tree ports at once by selecting allPorts.
reset counters bridge transparent allPorts port
Resets the RxFrames, TxFrames and RxDiscards counters for a single port or for all ports. These statistics can be displayed by executing the show bridge transparent port command.
reset counters ethernet statistics <IfIndex> <Action> : INTEGER (1..255) : clear
Resets the counters for the specified ifIndex in the table displayed by executing the show ethernet statistics entry command.
4-13
System Utilities
reset counters fr line <IfIndex> <Action> : INTEGER (1..255) : clear
Resets the counters for the specified ifIndex for the statistics displayed when the following commands are executed:
show fr line network pvcsignalling operational entry show fr line user basedlcmi operational entry show fr line user mpanl statistics reset counters fr mpanl statistics <Action> : clear
Resets the numbers that are displayed for established calls, reestablished calls and disconnects when the show msm statistics table command is executed.
reset counters fr pvc <IfIndex> <DLCI> <Action> : INTEGER (1..255) : INTEGER (17..991) : clear
For the ifIndex and DLCI specified, resets the frame relay PVC statistics that are displayed when the show fr switch pvc operational entry command is executed.
reset counters fr svc <IfIndex> <DNA> <Action> : INTEGER (1..255) : Frame Relay DNA (as a quoted string)(3..30) : clear
For the ifIndex and DNA specified, resets the frame relay SVC statistics that are displayed when the following commands are executed:
show fr switch svc circuit table show fr port spvclandata svc circuit table show fr port svclandata circuit table reset counters fr system <Action> : clear
Resets the transmit and receive statistics that are displayed when the show fr
system operational command is executed.
4-14
System Utilities
reset counters icmp <Action> : clear
Resets the statistical counters for the parameters that are displayed when the show icmp statistics command is executed.
reset counters ip <Action> : clear
Resets the statistical counters for the parameters that are displayed when the show ip parameters command is executed.
reset counters ipx rip circuit system
Resets the IPX RIP counters for a specified circuit or for all circuits in the system. The TxPkts and RxPkts counters are displayed using the show ipx rip circuit command.
reset counters ipx sap circuit system
Resets the IPX SAP counters for a specified circuit or for all circuits in the system. The TxPkts and RxPkts counters are displayed using the show ipx sap circuit command.
reset counters ipx system advanced <SysInstance> <Action> : INTEGER (1..255) : clear
For the specified SysInstance, resets the counters for the parameters which are displayed using the show ipx system advanced table command.
reset counters isdn dialcontrol callactive <Index> <Action> : INTEGER (0..255) : clear
For the specified ISDN index, resets to zero the values of the gauges in the Dial Control Call Active table.
4-15
System Utilities
reset counters isdn dialcontrol callhistory <Action> : clear
Resets to zero the values of the gauges in the Dial Control Call History table.
reset counters isdn dialcontrol peer <Id> <Action> : INTEGER (1..2147483647) : clear
For the specified ID, resets to zero the values of the guages in the Dial Control Peer table.
reset counters isdn physicalif lapd <Index> <Action> : INTEGER (1..255) : clear
For the specified ISDN index, resets to zero the values in the table containing statistics for all D-channel data link interfaces.
reset counters isdn physicalif signaling <Index> <Action> : INTEGER (1..2147483647) : clear
For the specified ISDN index, resets to zero the values of the counters in the ISDN Signaling Statistics table.
reset counters msm <IfIndex> <Action> : INTEGER (1..255) : clear
For the specified ifIndex, resets the numbers that are displayed for established calls, reestablished calls and disconnects when the show msm statistics table command is executed.
reset counters rsi statistics <Action> : clear
Resets the counters for the parameters displayed by executing the show rsi statistics command.
reset counters snmp <Action> : clear
Resets the counters for the parameters displayed by executing the show snmp statistics command.
4-16
System Utilities
reset counters tcp <Action> : clear
Resets the counters for the parameters displayed by executing the show tcp parameters command.
reset counters t1e1 statistics <Action> : clear
Resets the counters for the statistics that are displayed when the show t1e1 statistics table command is executed.
reset counters udp <Action> : clear
Resets the transmit and receive statistics that are displayed when the show udp statistics command is executed.
reset counters voice statistics allChannels channel network
These command options allow you to reset voice statistics for a single voice channel, all voice channels simultaneously, or for the voice network. The affected statistics are displayed using the show voice statistics channel table command and the show voice statistics network command.
reset counters wan statistics port <IfIndex> <Action> : INTEGER (1..255) : clear
Resets the transmit and receive statistics for the specified ifIndex that are displayed when the show wan statistics port entry command is executed.
reset counters wan statistics trafficclass <IfIndex> <TrafficClass> <Action> : INTEGER (1..255) : INTEGER (0..3) : clear
Resets the counters that are displayed for the specified ifIndex and traffic class when the show wan statistics trafficclass entry command is executed.
4-17
System Utilities
reset counters wan statistics vofr <IfIndex> <Action> : INTEGER (1..255) : clear
Resets the counters that are displayed for the specified ifIndex when the show wan
statistics vofr entry command is executed.
Ping Utility
The Ping utility allows you to check to see if a connection has been established between two devices in a network. After you have provisioned the Passport 4400 for IP or IPX routing, you can enter the ping command followed by the IP address of the destination with which you wish to communicate. The Ping program tests the reachability of the destination by issuing an echo request and waiting for a reply.
4-18
LAN Services
Introduction to LAN services over a Passport network Provisioning LAN services Monitoring LAN services
When a Passport 4400 unit is added and physically linked to a Passport network, a primary logical link to a Passport switch acting as a core router must be established before any user traffic can be carried. The Passport 4400 can be used to interconnect LAN-based workstations at different branch sites, or at the core site, over the WAN cloud. As part of the Passport network, the Passport 4400 allows connectivity between workstations attached to its LAN with those attached to the Passport switch inter-LAN Switching (ILS) service. The Passport 4400 uses standard RFC1490 encapsulation for transporting LAN data over the WAN. This allows the Passport 4400 to interwork with any frame relay access device supporting RFC1490.
LAN Features
The following functions support LAN traffic in Passport 4400 units: bridging IP routing IPX routing. Each of these functions provides different options for carrying traffic across the Passport 4400s virtual ports. Bridging Bridging is used to connect LANs at the data link level (as opposed to the network level). The Passport 4400 supports transparent bridging, a process of relaying Media Access Control (MAC) frames between LANs in a manner that is invisible to the originating host. Transparent bridges permit the connection of separate Ethernet and other supported networks. Bridging on the Passport 4400 supports the IEEE Spanning Tree Protocol to prevent loops in bridged networks. The spanning tree protocol contains complex features that ensure traffic flow is maintained if bridged network topology
5-1
Passport 4400 Operations Manual
Frame Relay Services
changes. This spanning tree protocol is an IEEE 802.1d standard and is fully supported by a wide variety of third-party bridges.
LAN ifIndex 3 Passport 4400
ILS Core Router
Port 1 Port 2
ifIndex 2
Passport Network
Figure 5-1. Example of Passport 4400 Bridging
IP Routing TCP/IP is a suite of protocols that defines a common set of rules and conventions, allowing networks and hosts to communicate. The routed or network-layer protocol of TCP/IP is the Internet Protocol (IP). All router management applications, including TELNET, File Transfer Protocol (FTP), Trivial File Transfer Protocol (TFTP), and Simple Network Management Protocol (SNMP) are part of the TCP/IP architecture. Therefore, TCP/IP is usually supported in any internetwork regardless of the presence of TCP/IP end systems.
Passport Network ILS UCR

ifInd ex 2
LAN Passport 4400
ILS NMCR
ifInde x4
Port 1 Port 2
Figure 5-2. Example of Passport 4400 IP Routing
5-2
IPX Routing IPX is the basic routed protocol for Novell Corporation's NetWare internetworking software. IPX allows nodes to receive and transmit data by providing addressing and routing functions. Higher-level protocols are necessary to detect errors and resolve them with acknowledgment or retransmission messages.
Passport 4400
Passport Network Port 2
File Server
Port 1
Client
Figure 5-3. Example of Passport 4400 IPX Routing
Provisioning LAN Services

This section lists the specific provisioning procedures for setting up LAN service on the Passport 4400. It covers the following topics: Bridging (page 5-4) IP routing (page 5-8) IPX routing (page 5-12)
Prerequisites Before the Passport 4400 unit can support LAN services, the following conditions must exist: The appropriate LAN connections must be made to the Passport 4400 Ethernet Base Module, and the correct cables must be physically installed. Instructions for connecting the LAN port on Passport 4400 units may be found in document 800-1951-20, Passport 4400 Hardware Installation Manual. The Passport switch must be configured as an inter-LAN switching (ILS) core router. See Step 2 of chapter 2, Getting Started, for more information. A node profile must be established on the Passport 4400. The node profile allows the Passport 4400 to construct a link with the Passport switch. See Step 6 of chapter 2, Getting Started, for more information.
5-3
Command Line Interface (CLI) overview The commands described in this section are entered using the Passport 4400 Command Line Interface (CLI). The CLI can be accessed from a workstation attached to the Passport 4400 units management port, or remotely over a LAN connection. For more information about using the CLI, see Step 4 of Chapter 2, Getting Started.
Provisioning Bridging
The following commands are used to provision the Passport 4400 for bridging. More detailed information about bridging may be found in Passport Bridging User Guide, document 241-7001-801.
define bridge global ipprotocol bridged
Since the Passport 4400 is configured for bridging by default, the above command will not be necessary in most cases. If you are changing the Passport 4400 IP protocol from routed to bridged, use this command to select bridged mode.
add ip address entry 3 <IPAddress> <NetMask> <BcastAddress> : IPAddress : Sub-NetMask : IPAddress
This command assigns an IP address for ifIndex 3 (bridge traffic on Port 1). The subnet mask will be either 255.255.255.0 or 255.255.0.0 or 255.0.0.0 depending on the class of the corresponding IP address. When the variables have been correctly added to the add ip address entry 3 command, the CLI will display a Command Successful message.
define ip base parameters datalinktype 2 fr
This command sets frame relay as the data link type on ifIndex 2 (WAN user service traffic on Port 2). Since the Passport 4400 is configured for frame relay by default, the above command will not be necessary in most cases. If you are changing a port from ethernet to frame relay, use this command to select frame relay.
add fr port spvclandata 2 <RemoteNetDLCI> <SVCDNA> <ConnectType> : INTEGER (16..991) : Frame Relay DNA (quoted string)(3..30) : slave | master
This command creates a switched permanent virtual circuit (SPVC) link to the Passport for ifIndex 2. For RemoteNetDLCI, enter the DLCI numbers assigned to the Passport 4400 for user traffic. For SVCDNA, use the same DNA number used when you configured FRUNI on the User Core Router. For ConnectType, enter master.
5-4
Using the data from Step 2 of Chapter 2, Getting Started, the command is as follows: add fr port spvclandata 2 21 3021811398399 master
Provisioning Bridge Filtering Filtering may be used to reduce traffic and congestion in the Passport network. Information may be filtered by three separate criteria: Ethernet Type, MAC address, and SAP.
Activating bridge filters
set bridge spanningtree port status <IfIndex> <Status> : INTEGER (1..32) : enabled | disabled
The spanning tree protocol must be enabled before any filtering can take place. Set the status to enabled for all ifIndices used for bridging.
set bridge base port etypeFilter etypeFilterType macFilter macFilterType sapFilter sapFilterType
There are three varieties of filtering that may be applied to bridging. The Etype filter looks at the Ethernet type of the information. The MAC filter looks at the MAC address and the direction (source or destination) of the information. SAP filtering checks the SAP type of the information.
Note: The following CLI commands show activation of the Etype filter; to activate the MAC filter or SAP filter, substitute the appropriate command in the examples below. set bridge base port etypefilter <IfIndex> <EtypeFilter> : INTEGER (1..32) : enabled | disabled
The ifIndex number indicates which port is affected by the filter. All bridging filters are disabled by default; to use a particular type of filter, it must be enabled.
set bridge base port etypefiltertype
5-5
<IfIndex> <EtypeFilterType>
: INTEGER (1..32) : inclusive | exclusive
Setting the filter to inclusive will block any information that meets the filter requirements. Setting the filter to exclusive has the opposite effect the filter keeps information that meets the requirements, and blocks out everything else. The filter type is set to inclusive by default. For example, if a filter is designed to select information with an etype of 1600, an inclusive filter will refuse transmissions carrying an etype of 1600. An exclusive filter, however, will only accept transmissions with an etype of 1600, refusing all other etypes.
Entering bridge filters
Every filter has two basic requirements: the ifIndex number and the filter number. The ifIndex number indicates which port is affected by the filter. The filter number is an arbitrary ID number that must be assigned to each filter. Filter numbers are specific to each ifIndex; for instance, ifIndices 1 and 2 may each have a distinct filter assigned to filter number 1.
add bridge macfilter <IfIndex> <FilterNumber> <MACFilterAddr> <MACFilterDirection> : : : : INTEGER (1..32) INTEGER (1..32) MACADDRESS source | destination
MACFilterAddr is a hexadecimal string representing the MAC address of the transmission.

add bridge etypefilter range <IfIndex> <FilterNumber> <UpperRange> <LowerRange> : : : : INTEGER INTEGER INTEGER INTEGER (1..32) (1..32) (1536..65535) (1536..65535)
add bridge etypefilter singular <IfIndex> <FilterNumber> <Etype> : INTEGER (1..32) : INTEGER (1..32) : INTEGER (1536..65535)
Etype filters (and SAP filters, seen below) may be entered in two manners: as a range of etypes, or as a singular etype. A range filter will affect all etypes within a given range (for example, from 1600 to 64000). A singular filter will only affect one specific etype (for example, etype 4000).
add bridge sapfilter range <IfIndex> <FilterNumber> <UpperRange> <LowerRange> : : : : INTEGER INTEGER INTEGER INTEGER (1..32) (1..32) (1536..65535) (1536..65535)
5-6
add bridge sapfilter singular <IfIndex> <FilterNumber> <Etype> : INTEGER (1..32) : INTEGER (1..32) : INTEGER (1536..65535)
Optional Bridging Parameters The following commands offer further customization of bridging parameters.
define brigde global agingTime arpSpoofing ipProtocol spanningTree agingTime arpSpoofing The timeout period in seconds for aging out dynamically learned information. The default is 300 seconds. ARP spoofing intercepts WAN-based ARP requests, reducing WAN traffic. See Optional IP Routing Parameters below. The default is disabled. The IP networking protocol. This should be set to bridged, as shown in Provisioning Bridging above. The default is bridged. The spanning tree protocol detects a change in active topology and allows the root bridge to communicate these changes to all other bridges in the network. The default is enabled.
ipProtocol spanningTree
set bridge misc debugStatus spanDebugStatus spoofCacheAge spoofThreshold spoofThresholdAge debugStatus spanDebugStatus Sets the unit to debug the spanning tree algorithm. The default is disabled. Sets the unit to generate a controlled number of debugging messages to the CLI in order to debug bridge status. The default is disabled. The aging time for entries in the ARP spoofing cache specified by the cache timeout value. This is in order to make room for active entries. The default is 300 seconds. The number of consecutive outstanding ARP requests per test node when using ARP spoofing. The default is 15.
spoofCacheAge
spoofThreshold
spoofThresholdAge The aging time for the ARP spoofing cache threshold. The default is 5 seconds.
5-7
set bridge spanningtree parameters bridgeFwdDelay bridgeHelloTime bridgeMaxAge priority bridgeFwdDelay bridgeHelloTime bridgeMaxAge The value that all bridges use for forward delay when this unit is acting as root. The default is 1500 (15 seconds). The value that all bridges use for hello time when this unit is acting as root. The default is 200 (2 seconds). The maximum age of spanning tree protocol information learned from the network before it is discarded. The default is 2000 (20 seconds). Refers to the first two octets of the Bridge ID (priority followed by MAC address = Bridge ID). The default is 32768.
priority
set bridge spanningtree port pathCost priority status pathCost Value based on hop count. Used to compare various paths through the network environment. Path cost value is used by the routing protocols to determine the most favorable path to a particular destination. Path cost value is assigned by the system administrator. Value used to assign priority to the designated port. Priority based on packet size and interface type. Select enabled or disabled. This must be set to enabled before filters can be used (see Provisioning Bridge Filtering above).
priority status
Provisioning IP Routing
The procedure for provisioning IP routing on the Passport 4400 can be found in Step 7 of chapter 2, Getting Started. Provisioning IP Filtering There are two varieties of filtering that can be applied to IP routing IP forward filter and RIP filter. The IP forward filter is classified into system-based filters and port-based filters. System-based filters require you to specify both the source and destination networks. System-based filters are applied on packets received on all interfaces. Port-based filters require you to specify either the port or destination network, along with the interface to which the filter should be applied.
5-8
Routers in an IP network periodically update their routing information databases with information about networks and neighboring routers using Routing Information Protocol (RIP). RIP provides current information about router end stations and servers connected in the network, using a request and a response method as well as an informational broadcast method. The RIP filter is intended to perform the following: suppress routes from being advertised in routing updates suppress routes listed in updates from being processed suppress listening on routing updates from specific routers.
IP Forward filter
Select either port filtering or system filtering, depending upon your selection criteria.
add filters ip forward port (incoming/outgoing) <IfIndex> <FilterMask> <FilterAddress> <ProtocolType> <PortId> <Direction> <Action> : : : : : : : INTEGER (1..255) IPAddress IPAddress INTEGER (1..255) INTEGER (1..65535) source | destination forward | discard
Port filtering must be specified as either incoming or outgoing (select one). The filters Action determines the nature of the filter. Discard blocks transmissions as specified in the filter masks and addresses. Forward seeks out information with the specified masks and address, and then passes (forwards) the information to its destination, blocking all other information. This concept is essentially the same as Inclusive/Exclusive filtering for bridging (see page 5-5, Activating Bridge Filters).
add filters ip forward system <DestMask> <DestAddress> <SrcMask> <SrcAddress> <ProtocolType> <PortId> <Action> : : : : : : : IPAddress IPAddress IPAddress IPAddress INTEGER (1..255) INTEGER (1..65535) forward | discard
For system filtering, both the destination and source most be specficied.
RIP filter
add filters ip rip port (gateway/incoming/outgoing) <FilterMask> <FilterAddress> <Action> : IPAddress : IPAddress : forward | discard
5-9
RIP filtering must be specified as gateway, incoming, or outgoing (select one). The command and parameters are the same for each type of filtering. Optional IP Routing Parameters The following commands offer further customization of IP routing on the Passport 4400.
define fr port virtualPort mode <IfIndex> <Mode> : INTEGER (1..255) : basic | easyrouting
The procedures used to provision IP routing assume the existence of a core router with inter-LAN Switching (ILS) service. If your Passport network does not use an ILS core router, select the easyrouting option. This option is set to basic (no easyrouting) by default.
define brigde global arpSpoofing <ArpSpoofing> : enabled | disabled
ARP (Address Resolution Protocol) spoofing is a technique used to reduce WAN traffic. The ARP spoofing agent learns the addresses of local hosts and stores them in a table. This table is used to respond to ARP requests, in place of a WAN-based request. ARP spoofing is disabled by default.
define fr port spvcLANData svc txPriority <ConnectID> <TxPriority> : INTEGER (1..65535) : INTEGER (0..15)
The Passport 4400 allows you to change the transport priority of a specific virtual port. Transport priority can be assigned from 0-15, with higher numbers indicating higher priority. Default transport priority settings are as follows: LAN traffic: 0 NMS traffic: 6 voice traffic: 11 The Connect ID for a specific port may be found by using the following command: show fr port spvcLANData base svc operational table
define ip invArp <IfIndex> <Protocol> <Status> : INTEGER (1..255) : ip : enabled | disabled
Inverse ARP (InvARP), as specified in RFC1293, is an addition to standard ARP that allows a station to request an IP address corresponding to a given physical (hardware) address. Inverse ARP is disabled by default.
5-10
define ip base parameters bcastAddress dataLinkType ipAddress ipNumbered keepAlive mtu netMask routeProtocolType bcastAddress The IP broadcast address used for sending datagrams. This value applies to both the subnet and network broadcast addresses used on this interface. The link type, either frame relay (fr) or Ethernet (ether). The IP address of the Passport 4400. Select numbered or unNumbered to match your network configuration. This variable determines whether keepAlive messages are sent over this interface. Maximum Transmission Unit the size in octets of the largest datagram that can be sent or received. The subnet mask associated with the IP address of the Passport 4400.
dataLinkType ipAddress ipNumbered keepAlive mtu netMask
routeProtocolType The route protocol type is set to RIP in Step 7 of Chapter 2, Getting Started. Options are RIP Passive RIP, and disabled. Passive RIP , does not broadcast RIP information across the WAN. set ip parameters defaultTimeToLive
This command determines how long a packet is considered valid, measured in seconds.
set ip route metric netMask nextHop metric netMask nextHop The number of hops required to reach the destination IP address. The subnet mask associated with the IP address of this entry. The next hop (node) along the path to the destination IP address.
5-11
Provisioning IPX Routing

The procedure for provisioning IPX routing on the Passport 4400 can be found in Step 7 of Chapter 2, Getting Started. Optional IPX Routing Parameters The following commands offer further customization of IPX routing on the Passport 4400.
add ipx staticRoute <SysInstance> <CircuitIndex> <NetNumber> <Status> <Ticks> <HopCount> <NextHopNICAddress> : : : : : : : INTEGER (1 only) INTEGER (1..16) NetNumber (0x01 - 0xFFFFFFFE) off | on INTEGER (1..1000) ticks INTEGER (1..14) PhysAddress
CircuitIndex is an ID number for the route being added. NetNumber is the IPX network number associated with the route. Status should be set to on. Ticks and HopCount refer to the number of ticks and hops needed to reach the next NIC (MAC) address along the route.
define ipx circuit circuitName dataLinkType existState ifIndex netNumber operState circuitName dataLinkType existState ifIndex netNumber operState An arbitrary name assigned to a circuit. The link type of the circuit. This will depend on the direction of the IPX traffic over the circuit. Select on or off. The default is on. The ifIndex number associated with this circuit. The IPX network number associated with this circuit. The operation state of the IPX circuit. The default is up.
define ipx staticRoute hopCount nextHopNICAddress status ticks
5-12
hopCount nextHopNICAddress status ticks
The number of hops needed to reach the destination. The NIC (MAC) address of the next hop. The status of the route. This should be set to on. The delay, measured in ticks, to reach the destination.
define ipx system basic netNumber routerStatus spoofDataLinkType systemName wanOptimization netNumber routerStatus spoofDataLinkType systemName wanOptimization set ipx circuit staticStatus The network number portion of the IPX address of the system. The operational status of the router. The default is disabled. The link type to be spoofed. This will depend on the direction of the IPX traffic over the circuit. An arbitrary system name for the IPX network. WAN optimization is not currently supported.
This command compares current route and service information with information in permanent storage. Write will write the current information to storage; read will replace the information in storage with current information.
Monitoring LAN Services

The following commands allow the monitoring of parameters, settings, and results of LAN services. Many of these commands will allow you to confirm entries made with the add, define, and set commands. Others will track the performance of the Passport network.
Configured versus Operational
Many of the show commands used throughout this manual offer a choice between configured and operational settings, as in the following example:
show ip address configured operational
5-13
Configured refers to attributes that have been entered or selected from the CLI, but are not necessarily in use by the Passport 4400. Operational refers to attributes that are currently in use by the Passport 4400. The following example illustrates the difference between configured and operational settings.
show bridge global IPProtocol : bridged (operational) : bridged (configured)
Now switch the IPProtocol to routed mode.

define bridge global ipProtocol routed Command Successful show bridge global IPProtocol : bridged (operational) : routed (configured)
Though the IP protocol has now been configured as routed, the Passport 4400 is still operating as a bridge. Upon resetting, the Passport 4400 loads the configured option (routing) into its operational (active) settings.
reset system current reset show bridge global IPProtocol : routed (operational) : routed (configured)
Entry versus Table
Many of the show commands used throughout this manual offer two ways to display information: as a single entry, or as a complete table.
show ip route entry table
In this case, the entry option shows information about only the selected route. The table option displays information about all existing IP routes.
show ip route entry <DestAddress> : IPAddress
This indicates the variable used (destination address) to select an individual route.
show ip route entry 201.203.1.0 DestAddress 201.203.1.0 IfIndex Metric NextHop Type 2 1 201.203.1.77 local NetMask 255.255.255.0
5-14
show ip route table DestAddress 193.169.15.0 193.169.77.0 201.203.1.0 201.205.1.0 IfIndex 4 1 2 4 Metric 2 1 1 1 NextHop 201.205.1.1 193.169.77.1 201.203.1.77 201.205.1.77 Type netmgmt local local local NetMask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
Monitoring Bridging
show bridge base port configured (entry/table) IfIndex Type Status Priority PathCost MACFilter EtypeFilter SapFilter MACFilterType EtypeFilterType SapFilterType IfIndex Type Status Priority : : : : : : : : : : : 1 ethernet enabled 128 100 disabled disabled disabled inclusive inclusive inclusive
The ifIndex that is effected by the following filters. This is the selection criterion for an entry listing. The type of interface this port is attached to. Valid choices are ethernet, wan, frame relay, and internat. The status of the port: enabled or disabled The port priority, contained in the first octet of the Port ID. The Port ID, composed of the Priority and ifIndex of the port, is used in spanning tree information. The path cost added to any path that includes this port. These indicate the status of the three filters associated with bridging mode. The default is disabled.
PathCost MACFilter EtypeFilter SapFilter MACFilterType EtypeFilterType SapFilterType
These indicate the nature of the filter in question: inclusive (filter out the selected information), or exclusive (filter out everything BUT the selected information). See Provisioning Bridge Filtering above.
show bridge base port operational (entry/table) IfIndex ProtocolPointAccess Type MACFilter EtypeFilter : : : : : 1 0 ethernet disabled disabled
5-15
SapFilter MACFilterType EtypeFilterType SapFilterType IfIndex ProtocolPointAccess Type MACFilter EtypeFilter SapFilter MACFilterType EtypeFilterType SapFilterType
: : : :
disabled inclusive inclusive inclusive
The ifIndex that is effected by the following filters. This is the selection criterion for an entry listing. The Protocol Point of Access to which this ifIndex pertains. The type of interface this port is attached to. Valid choices are ethernet, wan, frame relay, and internat. These indicate the status of the three filters associated with bridging mode. The default is disabled.
These indicate the nature of the filter in question: inclusive (filter out the selected information), or exclusive (filter out everything BUT the selected information). See Provisioning Bridge Filtering above.
show bridge basic port (entry/table) Port IfIndex PortCircuit DelayExDiscards MtuExDiscards Port IfIndex PortCircuit DelayExDiscards MtuExDiscards : : : : : 1 1 0.0.0 0 0
The port number in question. The ifIndex associated with this port. A unique circuit name assigned to this port. The number of frames discarded due to excessive transit delay through the bridge. The number of frames discarded due to excessive size.
show bridge forwarding (entry/table) Address 00:60:38:05:01:b4 Address Port Status Port 1 Status self
The MAC address for which the Passport 4400 has forwarding and/ or filtering information. The port number that leads to the specified address. The status of this forwarding entry. Possible statuses include learned, self (address is located within the Passport 4400), mgmt (address included in static address table), invalid, and other.
5-16
show bridge global IPProtocol SpanningTree ArpSpoofing AgingTime : : : : : : : : bridged (operational) bridged (configured) enabled (operational) enabled (configured) disabled (operational) disabled (configured) 300 (operational) 300 (configured)
ipProtocol spanningTree
The IP networking protocol. This should be set to bridged, as shown in Provisioning Bridging above. The default is bridged. The spanning tree protocol detects a change in active topology and allows the root bridge to communicate these changes to all other bridges in the network. The default is enabled. ARP spoofing intercepts WAN-based ARP requests, reducing WAN traffic. See Optional IP Routing Parameters below. The default is disabled. The timeout period in seconds for aging out dynamically learned information. The default is 300 seconds.
arpSpoofing
agingTime
show bridge (etypeFilter/sapFilter) (configured/operational) (entry/table) IfIndex 1 1 IfIndex FilterNumber Status Etype UpperRange LowerRange FilterNumber Status Etype 1 range 0 2 singular 4400 UpperRange 50000 0 LowerRange 5000 0
The ifIndex to be filtered. This is the selection criterion for an entry listing. The ID number assigned to the filter. Range or singular. Singular acts upon a specific etype; range acts on all etypes within the specified range. For singular filters, this is the Ethernet type to be filtered. For range filters, these are the upper and lower boundaries of the Ethernet types to be filtered.
show bridge macFilter (configured/operational) (entry/table) IfIndex 1 IfIndex FilterNumber FilterNumber 1 MACFilterAddress 444444 MACFilterType source
The ifIndex to be filtered. This is the selection criterion for an entry listing. The ID number assigned to the filter.
5-17
MACFilterAddress MACFilterType
The MAC address to be filtered. The direction of the MAC-addressed information (source or destination).
show bridge misc DebugStatus SpanDebugStatus SpoofCacheAge SpoofThresholdAge SpoofThreshold : : : : : : : : : : disabled (operational) disabled (configured) disabled (operational) disabled (configured) 300 (operational) 300 (configured) 15 (operational) 15 (configured) 5 (operational) 5 (configured)
DebugStatus
Sets the unit to generate a controlled number of debugging messages to the CLI in order to debug the bridge status. The default is disabled. Sets the unit to generate a controlled number of debugging messages to the CLI in order to debug the spanning tree algorithm. The default is disabled. The aging time for entries in the ARP spoofing cache specified by the cache timeout value. This is in order to make room for active entries. The default is 300 seconds. The number of consecutive outstanding ARP requests per test node when using ARP spoofing. The default is 15. The aging time for the ARP spoofing cache threshold. The default is 5 seconds.
SpanDebugStatus
SpoofCacheAge
SpoofThreshold SpoofThresholdAge
show bridge parameters BridgeAddress NumOfPorts Type BridgeAddress NumOfPorts Type : 00:60:38:05:01:b4 : 2 : transparent_only The MAC address of the Passport 4400. The number of ports used for bridging. Typically, this number will be 2; one port for LAN traffic and one port for WAN traffic. The type of bridging used. The Passport 4400 supports only transparent bridging.
show bridge spanningTree parameters ProtocolSpec Priority : ieee8021d (operational) : 32768 (operational) : 32768 (configured)
5-18
TimeSinceTopChange TopologyChanges DesignatedRoot RootCost RootPort MaxAge HelloTime HoldTime ForwardDelay BridgeMaxAge BridgeHelloTime BridgeFwdDelay
: : : : : : : : : : : : : : :
00Years 000Days 00:01:29 (operational) 0 (operational) 80:00:00:60:38:05:01:b4 (operational) 128 (operational) 0 (operational) 2000 (operational) 200 (operational) 100 (operational) 1500 (operational) 2000 (operational) 2000 (configured) 200 (operational) 200 (configured) 1500 (operational) 1500 (configured)
ProtocolSpec Priority
The protocol used for bridging. Transparent bridging requires the IEEE 802.1d protocol. This number, an integer from 0 to 65535, forms the first two octets of the Bridge ID. Priority can affect the topology of the network; a bridge with a lower priority is more likely to be the designated root bridge.
TimeSinceTopChange The elapsed time since a topology change has occurred. TopologyChanges DesignatedRoot The number of changes in the topology of the network. This is the Bridge ID (priority plus MAC address) of the designated root bridge (determined by the spanning tree protocol). The cost of the path leading to the designated root bridge. The port that offers the lowest cost path to the designated root bridge. The length of time (in 1/100th of a second), that spanning tree information remains alive (before it is discarded). The interval (in 1/100th of a second) between transmission of spanning tree information. The interval (in 1/100th of a second) between transmission of two consecutive packets of spanning tree information. The length of time (in 1/100th of a second) that a bridge should wait before forwarding a topology change. If this bridge becomes the designated root bridge, then these values will be implemented throughout the network. See MaxAge, HelloTime, and ForwardDelay above.
RootCost RootPort MaxAge HelloTime HoldTime ForwardDelay BridgeMaxAge BridgeHelloTime BridgeFwdDelay
show bridge spanningTree port (entry/table)
5-19
IfIndex Priority State Status PathCost DesignatedRoot DesignatedCost DesignatedBridge DesignatedPort FwdTransitions IfIndex Priority
: : : : : : : : : : : : :
1 (operational) 128 (operational) 128 (configured) disabled (operational) enabled (operational) enabled (configured) 100 (operational) 100 (configured) 80:00:00:60:38:05:01:b4 (operational) 0 (operational) 80:00:00:60:38:05:01:b4 (operational) 0 (operational) 1 (operational)
The ifIndex of the port in question. The port priority, contained in the first octet of the Port ID. The Port ID, composed of the Priority and ifIndex of the port, is used in spanning tree information. The current state of the port, as defined by the spanning tree protocol. Possible states include blocking, listening, learning, forwarding, disabled, and broken. The status of the port: enabled or disabled The path cost added to any path that includes this port. The Bridge ID of the designated root, as determined by the spanning tree protocol. The path cost for the designated bridge (see below). The Bridge ID of the designated bridge. The designated bridge provides the lowest-cost path from the LAN to the designated root. The port of the designated bridge. The number of times this port has changed from the Learning state to the Forwarding state.
State
Status PathCost DesignatedRoot DesignatedCost DesignatedBridge
DesignatedPort FwdTransitions
show bridge transparent parameters LearnEntryDiscards AgingTime LearnEntryDiscards AgingTime : 0 : 300
The number of learned table entries that have been discarded. The timeout period in seconds for aging out dynamically learned information. The default is 300 seconds.
show bridge transparent port (entry/table) IfIndex 1 MaxInfo 1530 RxFrames 0 TxFrames 5 RxDiscards 0
5-20
IfIndex MaxInfo RxFrames TxFrames RxDiscards
The ifIndex of the port in question. The maximum size of the INFO field that this port will receive or transmit. The number of frames that this port has received. The number of frames that this port has transmitted. The number of valid frames that have been discarded (i.e., filtered) by the forwarding process.
Monitoring IP Routing
show ip address (configured/operational) (entry/table) IfIndex IPAddress Mtu DataLinkType KeepAlive ForwardBcast IPNumber RouteProtocolType IfIndex IPAddress Mtu DataLinkType KeepAlive ForwardBcast IPNumber RouteProtocolType : : : : : : : : 1 192.168.151.1 1500 ether on off numbered rip
The ifIndex associated with the IP address. The IP address to which this entrys addressing information pertains. Maximum Transmission Unit the size of the largest datagram that can be sent or received over the interface. frameRelay) or ether (Ethernet). This variable determines whether keepAlive messages are sent over this interface. The status of forward broadcasting on or off. The IP numbering method used numbered or unNumbered. The route protocol in use RIP, passive RIP, or disabled.
show ip base defaultRoute DefaultRoute : off (operational) : off (configured)
show ip base rip Rip : on (operational) : on (configured)
show ip invarp (entry/table)
5-21
IfIndex Protocol Status
: : : : : :
2 (operational) 2 (configured) ip (operational) ip (configured) enabled (operational) enabled (configured)
IfIndex Protocol Status
The ifIndex affected by the protocol and status registers. The routing protocol in use. Status of the protocol enabled or disabled.
show ip parameters Forwarding InputDatagrams InputAddrErrors RxUnknownProtocol InputDelivers OutputDiscards ReassembleTimeout ReassembleOK FragmentOK FragmentCreate Forwarding DefaultTimeToLive InputDatagrams InputHeaderErrors InputAddrErrors FwdDatagrams RxUnknownProtocol InputDiscards InputDelivers TxRequests : : : : : : : : : : on 224 0 0 224 0 60 0 0 0 DefaultTimeToLive InputHeaderErrors FwdDatagrams InputDiscards TxRequests OutputNumRoutes ReassembleNeed ReassembleFail FragmentFail RoutingDiscards : : : : : : : : : : 60 0 0 0 155 0 0 0 0 0
Determines whether the Passport 4400 is acting as an IP gateway (on) or an IP host (off). Indicates how long (in seconds) a packet is considered valid. The total number of datagrams received, including datagrams with errors. The number of inbound datagrams with an error in the IP header. The number of inbound datagrams with an invalid or unsupported IP address. The number of inbound datagrams for which the Passport 4400 is not the final destination. The number of inbound datagrams with an invalid or unsupported protocol. The number of inbound datagrams discarded due to lack of system resources (such as lack of buffer space). The number of inbound datagrams successfully delivered to IP user-protocols. The total number of IP datagrams supplied to the Passport 4400 in requests for transmission. This does not include datagrams counted in FwdDatagrams.
5-22
OutputDiscards OutputNumRoutes ReassembleTimeout ReassembleNeed ReassembleOK ReassembleFail FragmentOK FragmentFail
The number of outbound datagrams discarded due to lack of system resources (such as buffer space). The number of outbound datagrams discarded due to an invalid route. The maximum number of seconds which received fragments are held during reassembly. The number of inbound fragments which need reassembly. The number of datagrams successfully reassembled. The number of failures during reassembly. The number of datagrams successfully fragmented. The number of datagrams that require fragmentation but were unable to be fragmented (e.g., the Dont Fragment flag was set). The total number of datagram fragments that have been generated by the Passport 4400. The number of packets discarded due to lack of memory.
FragmentCreate RoutingDiscards
show ip route (entry/table) DestAddress 201.203.1.0 DestAddress IfIndex Metric NextHop Type IfIndex Metric NextHop Type 2 1 201.203.1.77 local The IP address of the destination of the route. The ifIndex associated with this route. The number of hops required to reach the destination. The IP address of the next hop along the route. The routing protocol or mechanism that supplied the Passport 4400 with this route. This does not mean that this route is restricted to only this type of traffic. The subnet mask associated with this route. NetMask 255.255.255.0
NetMask
Monitoring IPX Routing

show ipx circuit (entry/table) SysInstance CircuitIndex ExistState OperState IfIndex : : : : : : : : : 1 (operational) 1 (configured) 1 (operational) 1 (configured) on (operational) on (configured) up (operational) up (configured) 1 (operational)
5-23
CircuitName CircuitType DataLinkType LocalMaxPacketSize StaticStatus NetNumber StaticChanges InitFails Delays Throughput SysInstance CircuitIndex ExistState OperState IfIndex CircuitName CircuitType DataLinkType LocalMaxPacketSize StaticStatus
: : : : : : : : : : : : : : :
1 (configured) "A2_3" (operational) "A2_3" (configured) other (operational) raw (operational) raw (configured) 0 (operational) unknown (operational) unknown (configured) 00000015 (operational) 00000015 (configured) 0 (operational) 1 (operational) 1 (operational) 0 (operational)
This number is always 1. This is a unique number used to identify a circuit. The validity of this entry in the IPX system table. Setting this variable to off allows this entry to be removed. The operational state of the circuit up, down, or sleeping. The ifIndex of the interface used by this circuit. The IPX readable name for this circuit. The type of circuit other, broadcast, ptToPt, wanRIP , unnumberedRIP dynamic, or wanWS. , The data link (frame) type used by this circuit raw, snap, type2, or type8022. The maximum size (including header), in bytes, that the system supports locally on this circuit. Compares current route and service information with information in permanent storage. Write will write the current information to storage; read will replace the information in storage with current information. The network number of the destination. The number of times this circuit has changed state. The number of times that initialization of this circuit has failed. The period of time, in milliseconds, that it takes to transmit one byte of data. The amount of data, in bits per second, that may flow through the circuit if there is no other traffic.
NetNumber StaticChanges InitFails Delays Throughput
show ipx remoteservices (entry/table)
5-24
SysInstance NetNumber Node Socket Name Type ProtocolType HopCount SysInstance NetNumber Node Socket Name Type ProtocolType HopCount
: : : : : : : :
1 00000071 00:00:00:00:00:01 1105 "PP4400" 4 sap 2
This number is always 1. The network number of the node. The MAC address of the node. The socket number within the node. The name assigned to the node. This is the packet type, a code assigned to the various types of NetWare traffic. The protocol used to route NetWare traffic RIP or SAP . The number of hops required to reach the node.
show ipx (rip/sap) circuit (entry/table) SysInstance CircuitIndex State Pace Update AgeMul PktSize TxPkts RxPkts SysInstance CircuitIndex State Pace Update AgeMul PktSize : : : : : : : : : 1 1 auto-on 18 60 0 0 0 104
This number is always 1. This is a unique number used to identify a circuit. Indicates whether the router may send or receive RIP/SAP messages over this interface. The pace (packets per second) at which the router may send RIP/ SAP messages. The interval, in seconds, at which the router transmits RIP/SAP messages. This number, when multiplied with Update, shows how long the router keeps information received from RIP/SAP updates. The default RIP/SAP packet size.
5-25
TxPkts RxPkts
The number of RIP/SAP packets transmitted. The number of RIP/SAP packets received.
show ipx (rip/sap) system (entry/table) SysInstance 1 SysInstance State IncorrectPackets State on IncorrectPackets 0
This number is always 1. Indicates whether the router may send or receive RIP/SAP messages over this interface. The number of times that an incorrectly formatted RIP/SAP packet was received.
show ipx route (entry/table) SysInstance NetNumber Protocol Ticks HopCount CircuitIndex NextHop SysInstance NetNumber Protocol Ticks HopCount CircuitIndex NextHop : : : : : : : 1 00000001 rip 1 2 2 00:00:00:00:00:00
This number is always 1. The network number of the destination. The protocol used to route IPX traffic RIP or SAP . The length of time (in ticks) to reach the destination. The number of hops needed to reach the destination. This is a unique number used to identify a circuit. The MAC address of the next hop along this route.
show ipx services (entry/table) SysInstance ServiceType ServiceName ProtocolType NetNumber Node Socket HopCount SysInstance ServiceType : : : : : : : : 1 4 "PP4400" sap 00000071 00:00:00:00:00:01 1105 2
This number is always 1. The service type.
5-26
ServiceName ProtocolType NetNumber Node Socket HopCount
The service name. The protocol used to route IPX traffic RIP or SAP . The network number of the node in question. The MAC address of the node. The socket number within the node. The number of hops required to reach the node.
show ipx staticRoute (entry/table) SysInstance CircuitIndex NetNumber ExistState Ticks HopCount NextHopNICAddress SysInstance CircuitIndex NetNumber ExistState Ticks HopCount NextHopNICAddress : : : : : : : 1 (operational) 2 (operational) 00000012 (operational) on (operational) 18 (operational) 1 (operational) 00:00:00:00:00:00 (operational)
This number is always 1. This is a unique number used to identify a circuit. The network number of the destination. The validity of this entry in the IPX system table. Setting this variable to off allows this entry to be removed. The length of time (in ticks) to reach the destination. The number of hops required to reach the destination. The NIC (MAC) address of the next hop along this route.
show ipx system advanced (entry/table) SysInstance MaxPathSplits MaxHops RxTooManyHops RxFiltered NETBIOSPackets FwdPackets TxFiltered CircuitCount DestCount ServiceCount SysInstance MaxPathSplits MaxHops : : : : : : : : : : : 1 0 0 0 0 0 591440 0 2 6 3
This number is always 1. The maximum number of equal-cost paths allowed for a given destination and routing method. The maximum hop count allowed before a packet is discarded.
5-27
RxTooManyHops RxFiltered NETBIOSPackets FwdPackets TxFiltered CircuitCount DestCount ServiceCount
The number of incoming packets that have been discarded due to exceeding the maximum hop count. The number of incoming packets that have been filtered. The number of NetBIOS packets received. The number of incoming packets for which this interface was not the final destination. The number of outgoing packets that have been filtered. The number of circuits known to this instance of IPX. The number of currently reachable destinations known to this instance of IPX. The number of services known to this instance of IPX.
show ipx system basic (entry/table) SysInstance ExistState NetNumber Node SystemName RxPackets RxHeaderErrors RxUnknownSockets RxDiscards RxDelivers NoRoutes TxRequests TxDiscards TxPackets RouterStatus Spoofing SpoofDataLinkType WanOptimization : : : : : : : : : : : : : : : : : : : : : : : : : : 1 (operational) 1 (configured) on (operational) on (configured) 00000000 (operational) 00000000 (configured) 00:00:00:00:00:00 (operational) "mpa" (operational) "mpa" (configured) 595515 (operational) 0 (operational) 0 (operational) 0 (operational) 0 (operational) 8 (operational) 0 (operational) 0 (operational) 0 (operational) enabled (operational) enabled (configured) disabled (operational) disabled (configured) raw (operational) raw (configured) disabled (operational) disabled (configured)
SysInstance ExistState NetNumber
This number is always 1. The validity of this entry in the IPX system table. Setting this variable to off allows this entry to be removed. The network number of the Passport 4400 unit.
5-28
Node SystemName RxPackets RxHeaderErrors
The MAC address of the Passport 4400. The IPX readable name assigned to the Passport 4400. The total number of packets received, including those received in error. The number of IPX packets discarded due to errors in their headers, including any IPX packet with a size less than the minimum of 30 bytes.
RxUnknownSockets The number of IPX packets discarded because the destination socket was not open. RxDiscards RxDelivers NoRoutes TxRequests TxDiscards TxPackets RouterStatus Spoofing The number of IPX packets received and discarded (for reasons other than header errors and unknown sockets). The total number of IPX packets delivered locally, including packets from local applications. The number of times no route to a destination was found. The number of IPX packets supplied locally for transmission. The number of outgoing PIX packets discarded (for reasons other than filtering). The total number of IPX packets transmitted. The status of IPX routing. Can be enabled or disabled. The status of RIP/SAP spoofing over the network. Can be enabled or disabled.
SpoofDataLinkType The data link (frame) type to be spoofed raw, type2, type8022, and type8023. WanOptimization This feature is not currently implemented.
5-29
5-30


Overview of Passport 4400 Frame Relay Service Provisioning Guidelines and Procedures for Frame Relay Pass-through Defining Multiple Frame Relay Switch Maps Defining Optional Frame Relay PVC and SVC Parameters Defining Optional Frame Relay System, Line, and Virtual Port Parameters Frame Relay Monitoring
The Passport 4400 provides a frame relay pass-through service that allows collocated third-party FRADs and routers to be connected to a Passport WAN backbone. The third-party device is connected to the Passport 4400 via a permanent virtual circuit (PVC) connection to a Frame Relay DCE port. The frame relay pass-through service uses a switched permanent virtual circuit (SPVC) connection to communicate with another Frame Relay DCE port through the Passport network (see Figure 6-1 below). This enables a third-party FRAD on one Passport 4400 to communicate with another third-party FRAD that is connected to a remote Passport 4400 via a Frame Relay DCE port connected to a remote Passport 4400 LAN service connected to a Frame Relay UNI port on a Passport switch connected to a Passport switch inter-LAN (ILS) service. The diagram below shows two third-party FRADs communicating with each other over a Passport frame relay backbone.
FRAD
Passport 4400 MPANL
Passport 4400
FRAD
FRUNI PVC
MPANL
MPANL
FRUNI
SPVC
PVC
Figure 6-1. Frame Relay Pass-through Virtual Circuit Connections
6-1
The Passport 4400 allows data traffic originating from a FRAD to be combined with other traffic from the same site, such as voice and LAN, and carried to a Passport WAN over a single low speed link. The traffic can then be transported over the Passport WAN to a FRAD at a remote location which is also serviced by a Passport 4400 unit (see Figure 6-2 below). In effect, the Passport 4400 provides connectivity between FRADs and the Passport WAN. The Passport 4400 unit appears as a frame relay user-network interface (FR UNI) switch to the FRAD and provides the necessary buffering and flow control mechanisms to maintain delivery of user data between the attached devices. The frame relay pass-through service performs the following functions: generates the network LMI to the attached FRAD supports T.617 Annex D, Q.933 Annex A and LMI Revision 1 protocols propagates a connect status to the attached FRADs via active/inactive state changes (also known as A-bit signaling) propagates received flow control (FECN/BECN) and discard eligibility (DE) bits to the destination enforces inbound CIR and DE marking for the DCE side.
Site 1
FRAD
Site 2
FRAD
Passport 4400
Passport
Magellan Passport Frame Relay WAN
Passport
Passport 4400
PBX
LAN
Figure 6-2. Passport 4400 Frame Relay Pass-Through Traffic Flow
6-2
MPANL SPVC Overview The frame relay pass-through service uses an SPVC connection to attach two Passport 4400 Frame Relay DCE ports through the Passport network. An SPVC connection is also used to connect a Passport 4400 Frame Relay DCE and a Passport/DPN Frame Relay Service (FRS). Similar in concept to the ITU-T X.76 recommendation on SPVC, the MPANL SPVC feature dynamically sets up an SVC interface through an MPANL interface to connect two SPVC endpoints. Services and devices on the Passport 4400 using an SPVC respond to the SPVC as if it were a PVC. The primary advantage of the MPANL SPVC feature is the minimal provisioning required to bring up an SPVC between the interconnected services. A-bit Signaling An integral part of the MPANL SPVC feature is the development of the A-bit signaling mechanism. A-bit signaling is the exchange of availability status between the two end-points of a PVC. This exchange allows either end to know whether the other end is ready to receive data. In situations where the remote end is not yet ready to receive, data can be discarded at the ingress rather than wasting bandwidth transferring it across the network only to have it discarded at the egress side. The A-bit mechanism also detects any failure of the device at the other end, or of any component of the network across which the SPVC is established. As soon as the SPVC is established, the overall PVC service is defaulted to inactive in both directions. When a PVC endpoint interface detects that A-bit is active (both the physical layer and LMI are operational), the active status is signaled toward the other PVC endpoint. A Q.933 STATUS message is used to carry the A-bit information across the MPANL interface. The MPANL interface at the receiving portion of the network also propagates the A-bit status to the PVC endpoint interface.
Note: The Passport 4400 will not transmit data until the A-bit is signaled active by the remote end. Until this occurs, all data for the remote end will be discarded at ingress. If the local PVC endpoint on the 4400 unit is not operational, the 4400 unit will signal an A-bit inactive status and will discard any data received for the PVC endpoint.
6-3
Local Management Interface (LMI) The frame relay pass-through service supports PVC LMI across the User-Network Interface (UNI) with the device attached to the Frame Relay DCE port. Available DLCIs and their status are reported to the attached device. The following LMI protocols are supported: T1.617 Annex D (1994) Q.933 Annex A LMI Revision 1.
Provisioning Guidelines for Frame Relay Pass-through

The following general guidelines should be kept in mind when attaching a thirdparty FRAD to the Frame Relay DCE port (Port 1) on a Passport 4400 Base Module(see Figure 6-3 below): Port 2 on the Passport 4400 Base Module is the primary WAN link used to carry frame relay traffic between the Passport 4400 and the Passport switch. Port 3 is a serial WAN backup port. Port 1 is defaulted to DCE. The FRAD normally should be configured for DTE.
Note: Port 1 can usually be configured for DTE, if necessary. However, if there is a CSU/DSU installed in Port 3 on the Base Module, Port 1 cannot be configured for DTE.
Management port
Frame Relay DCE serial access port (Port 1)
Ethernet Access Ports 10BaseT AUI
Port 2
Port 3 Back panel Interface Modules
Figure 6-3. Serial Access Ports on the Passport 4400 Base Module (Rear View)
6-4
If Port 1 is DCE, the Passport 4400 generates clocking; if Port 1 is set to DTE, the Passport 4400 accepts the clock from the FRAD. The default line speed on Port 1 is 64 Kbps; the maximum line speed is 1.92 Mbps. Be sure that the Port 1 line speed is set to a lower value than the Port 2 line speed. The LMI on the Passport 4400 is defaulted to ANSI. Some routers are defaulted to CCITT. Make sure that the LMI settings of the FRAD and the Passport 4400 match. The local DLCI number must match the PVC DLCI as seen by the FRAD attached to the Frame Relay DCE port on the Passport 4400.
Provisioning Procedure for Frame Relay Pass-through

the WAN ifIndex for the Frame Relay DCE port to which the FRAD is attached (typically Port 1) the ifIndex for the Frame Relay DCE service on Port 1 of the local Passport 4400 the PVC DLCI number for the Frame Relay DCE port on the local Passport 4400 the PVC LMI settings for the FRAD attached to the Frame Relay DCE port the PVC DLCI numbers for all remote sites with which the unit is to exchange frame relay pass-through traffic the DNA prefix of the Passport 4400 unit and of all remote sites with which the unit is to exchange frame relay pass-through traffic. (This should have already been provisioned in Step 6 of Chapter 2, Getting Started. To provision the Passport 4400 for frame relay pass-through operation, perform the following procedures:
Notes: The following tasks must be performed on each Passport 4400 unit that is to support an attached FRAD. In the procedures below, the Frame Relay DCE port (to which a FRAD or third-party router is attached) is referred to as Port 1. This is the Frame Relay DCE port on the Passport 4400 Base Module. If Data Expansion Modules are installed in the Passport 4400, as many as 17 Frame Relay DCE ports can be supported.
6-5
1. Provision the Passport 4400 for SPVC service according to the procedures given in
Step 6 and Step 7 of Chapter 2, Getting Started.

2. Determine the ifIndices needed for the Frame Relay DCE port (Port 1on the Passport
4400 Base Module).

show system ifindex configured Ifindex 1 2 3 4 7 8 150 151 152 153 154 155 159 160 161 162 163 164 165 166 168 169 183 184 186 187 189 190 192 193 IfExtType ethernetCsmacd propVirtual other propVirtual other other propMultiplexor other frameRelayService propMultiplexor v35 frameRelay propMultiplexor other frameRelayService propMultiplexor other frameRelayService propMultiplexor other propMultiplexor other propMultiplexor other propMultiplexor other propMultiplexor other propMultiplexor other PPA 0 0 0 1 0 0 1 1 1 2 2 2 1 1 1 2 2 2 3 3 4 4 1 1 2 2 3 3 4 4 Slot limA limA limA limA limB limB limA limA limA limA limA limA lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim1 lim2 lim2 lim2 lim2 lim2 lim2 lim2 lim2
The example above is a typical IfIndex Table for a Passport 4400 containing two Data Expansion Modules (DEMs) and an Analog Voice Module. Note that WAN ports are given the IfExtType of propMultiplexor. The Passport 4400 Base Module is Slot limA, and the PPA numbers correspond to the port numbers for physical ports. Thus, the ifIndex numbers for the WAN ports on the Base Module of the example Passport 4400 above are as follows:
6-6
ifIndex 150 ifIndex 153
Port 1 (the Frame Relay DCE port attached to the FRAD) Port 2 (the Frame Relay DTE port providing the main link to the Passport network)
It can be seen that there is no WAN backup module installed in Port 3 of this Passport 4400, as there is no propMultiplexor IfExtType in Slot limA with a PPA number of 3. The Frame Relay DTE service is designated frameRelay in the IfIndex Table. Note that the ifIndex for Frame Relay DTE on Port 2 of the Base Module is 155.
3. Define the physical port parameters for the Frame Relay DCE port (Port 1) to match
those of the attached FRAD.

define wan port mode <IfIndex> <Mode> : INTEGER (1..255) : dce | dte
For IfIndex, enter 150 (the ifIndex of the physical WAN port). The mode you select will depend on the cable you are using to connect to the FRAD.
define wan port baudrate 150 <BaudRate> : INTEGER (9600..1920000)
The IfIndex is again 150. Be sure that the baud rates of the FRAD and Port 1 match. The default setting for Port 1 is 64000 bps.
4. Define frame relay DCE protocol support on the Frame Relay DCE port (Port 1). define wan port protocol 150 <ProtocolSupport> : none | frameRelayDCE| frameRelayDTE | htds
The IfIndex is still 150. For ProtocolSupport, enter frameRelayDCE. This command creates a new ifIndex for Port 1 that has an IfExtType of frameRelayService. Note that in the sample IfIndex Table shown above, the ifIndex for frameRelayService on Port 1 on the Base Module (limA) is 152, indicating that Port 1 was already provisioned for Frame Relay DCE protocol support when the show system ifindex command was executed.
6-7
Optional WAN Port Parameters

You may wish to configure other parameters on the Frame Relay DCE port using the define wan port command. These additional parameters are described below.
htdsCutThru ifType
Used for HDLC Transparent Data Service applications. See Chapter 7 of this manual for details. Specifies the signaling characteristics of the WAN interface. Options are RS-232, V.35, V.36, X.21, CSU/DSU, T1 CSU, ISDNBRI, and none. The default is V.35. The maximum frame size in bytes that will be received on this interface. The range is from 1 to 8192 bytes. The default value is 4000. Specifies the number of buffers that will be used for receive data. The range is from 20 to 255. The default is 100. The size in bytes of each receive buffer. The range is from 10 to 255 bytes. The default is 20. The size in bytes of each transmit buffer. The range is from 10 to 255 bytes. The default is 20.
maxRxFrameSize
numOfRxBuffers rxQueueSize txQueueSize
Note: If you are running voice traffic over the Frame Relay DCE port, the rxQueueSize parameter should be set to 2.5 or 3 bytes per voice channel in order to prevent lost speech frames. Thus, the default setting of 20 can be used with up to 8 voice channels; the queue size should be increased by the 2.5 or 3 multiplier per channel if you have more than 8 voice channels. If you are running a combination of voice and LAN traffic over the Frame Relay DCE port, the value of 50 optimizes LAN throughput and will accomodate up to 20 voice channels. If the queue size is increased above 50 to accomodate more than 20 voice channels, LAN throughput may be adversely affected. For most applications, the txQueueSize parameter can remain at the default setting regardless of the increase in the size of the receive queue. 5. Determine the ifIndex for the Frame Relay DCE service on Port 1. show system ifindex configured
To find the ifIndex for the Frame Relay DCE service on Port 1, look for the IfExtType of frameRelayService on Slot limA with a PPA number of 1. In the sample IfIndex Table shown in Step 2 above, the ifIndex number is 152.
6-8
6. Define the LMI protocol on Port 1 of the Passport 4400 to match the LMI protocol
configured on the attached FRAD.

define fr line network rfc1604service vcsignalprotocol <IfIndex> <VCSignalProtocol> : INTEGER (1..255) : none | lmi | ccittQ933A | ansiT1617D-1994
For IfIndex, using the example given in Step 2, enter 152. For VCSignalProtocol, enter the LMI protocol that matches the attached FRAD. The default for the Passport 4400 is ANSI T1.617D.
7. Find the DNA prefix of the Passport 4400 unit. (This has already been provisioned
according to Step 6 of Chapter 2, Getting Started.)

show msm profile NodeId : 1 (operational) : 5 (configured) : 0 (operational) : 99 (configured)
CustomerId
DNAPrefix
: "[x121] (operational) : "[x121]302181139710" (configured) ------------------------------------------------------------
In this example, a node ID of 5, a customer ID of 99, and a DNA prefix of 302181140042 have been previously configured. Notice that the operational values have not changed from the default values because the Passport 4400 has not been reset.
8. Determine the DLCI number for Port 1 on the Passport 4400. This must be obtained
from the FRAD configuration.

9. Repeat Steps 1 through 8 for the Passport 4400 at the remote site (Site 2 in this
example).
6-9
10. Define switch maps for both Passport 4400 units add fr switch map <LocalNetIfIndex> <LocalNetDLCI> <RemoteNetDLCI> <SVCDNA> <ConnectType> <SwitchType> : : : : : : INTEGER (1..255) INTEGER (16..991) INTEGER (16..991) Frame Relay DNA (as a quoted string)(3..30) slave | master frdce | htds
For each of the parameters above, enter the following, separating each entry with a space:
<LocalNetIfIndex> <LocalNetDLCI> <RemoteNetDLCI> <SVCDNA>
the frameRelayService ifIndex on Port 1 of Site 1 (152 in our example). the DLCI for Port 1 at Site 1 (obtained from Step 8 above).
the DLCI for Port 1 at the remote site (Site 2). the DNA prefix of the Passport 4400 at Site 2, followed by the number 3, followed by the Slot number and PPA number of Port 1 at Site 2 (inside quotation marks without any spaces). enter master for the site that will establish the connection; enter slave for the other site. enter frdce for both sites.
<ConnectType> <SwitchType>
Figure 6-4 shows two Passport 4400s provisioned for frame relay pass-through. Note how the switch maps are constructed from the ifIndices, DLCIs and DNA numbers.
SITE 1
Port 1 FRAD 100 Passport 4400 Port 2 Passport FR Network Port 2
SITE 2
Port 1 Passport 4400 200 FRAD
SITE 1: WAN if Index = 150 FR DCE ifIndex = 152 DNA Prefix = 302181139710 DLCI = 100
Connection created by frame relay switch map
SITE 2: WAN if Index = 150 FR DCE ifIndex = 152 DNA Prefix = 302181140042 DLCI = 200
Figure 6-4. Frame Relay Switch Map Construction
6-10
To provision the Passport 4400 switch map at Site 1 so that the unit at Site 1 establishes the connection with Site 2, enter the following command:
add fr switch map 152 100 200 302181140042311 master frdce
Note that the last two digits of the <SVCDNA> parameter are 11 because the Frame Relay DCE port on the unit at Site 2 is Port 1 (PPA = 1) on the Base Module (Slot = 1). To provision the Passport 4400 switch map at Site 2, enter the following command:
add fr switch map 152 200 100 302181139710311 slave frdce 11. Save the configurations of the two Passport 4400s and restart both units. save configuration update reset system current reset 12. Verify the following:
the frame relay ports on both Passport 4400 units are up the LMI protocol on both Passport 4400 units is up and running the frame relay switch maps on both Passport 4400 units are active.
Note: The commands shown below are for the Passport 4400 at Site 1 only. Repeat the commands on the Passport 4400 at Site 2. show port parameters entry 152 IfIndex Description IfType Mtu Speed PhysAddress AdminStatus OperStatus LastChange RxOctets RxUnicastPackets RxNonUnicastPackets RxDiscards RxErrors RxUnknownProtocols TxOctets TxUnicastPackets TxNonUnicastPackets TxDiscards TxErrors TxQueueLength Specific : : : : : : : : : : : : : : : : : : : : : : 152 "Frame Relay Physical DCE Line" other 1604 64000 up up 00Years 000Days 00:00:17 0 0 0 0 0 0 0 0 0 0 0 0 "0.0"
6-11
The OperStatus parameter should indicate up. A status of down indicates a physical layer problem on Port 1.
show fr line network proprietaryservice operational entry 152 IfIndex FlowControl Delta ConsecutiveFrames RateEnforcement MaxTxFrameSize MaxRxFrameSize TxBc RxBc TxBe RxBe TxThroughput RxThroughput PVCLMIStatus : : : : : : : : : : : : : : 152 disabled 1 10 enabled 1604 1604 0 0 0 0 0 0 up
The PVCLMIStatus parameter should indicate up. A status of down indicates an LMI mismatch between the Passport 4400 and the attached FRAD.
show fr switch map operational entry 152 100 LocalNetIfIndex LocalNetDLCI ConnectID RemoteNetDLCI SVCIfIndex SVCDNA SVCDLCI LocalPVCDLCIState SVCUserDLCIState ConnectType LastChange SwitchDisconnReason SwitchType : : : : : : : : : : : : : 152 100 1 200 0 "302181140042311" 17 active active master 00Years 001Days 02:53:59 no-reason frdce
The LocalPVCDLCIState and SVCUserDLCIState parameters should both indicate active. A state of inactive indicates a problem with the DNA number.
6-12
Defining Multiple Frame Relay Switch Maps

Consider Figure 6-5 below, in which the two-site network in Figure 6-4 has been expanded to four sites. Site 1 now has three DLCIs provisioned on Port 1, and Site 2 has two DLCIs provisioned on Port 1. Notice that Site 1 and Site 2 both have a DLCI of 100. This is acceptable because DLCI numbers have local significance only. At Site 3, the FRAD is not attached to Port 1 on the Passport 4400 Base Module; it is attached to Port 1 of lim1, which is the Data Expansion Module in Slot 2. At Site 4, the FRAD is attached to Port 2 of lim1. Notice that the ifIndices for the Frame Relay DCE service reflect these port locations.
SITE 1
FRAD 102 101 100 FR DCE ifI = 152 DNA = 302181139710 Passport 4400 Passport FR Network
SITE 2
Passport 4400 200 100 FR DCE ifI = 152 DNA = 302181140042 FRAD
SITE 4
Passport 4400
SITE 3
Passport 4400 202 201 FRAD
102 FR DCE ifI = 164 DNA = 302181144021 FR DCE ifI = 161 DNA = 302181142020
Figure 6-5. Defining Multiple Frame Relay Switch Maps
Switch Maps for Site 1 The switch maps for Site 1 are as follows: DLCI 100 to DLCI 100 at Site 2 DLCI 101 to DLCI 201 at Site 3 DLCI 102 to DLCI 102 at Site 4 Enter the following CLI commands:
add fr switch map 152 100 100 302181140042311 master frdce add fr switch map 152 101 201 302181142020321 master frdce add fr switch map 152 102 102 302181144021322 master frdce
6-13
Switch Maps for Site 2 The switch maps for Site 2 are as follows: DLCI 100 to DLCI 100 at Site 1 DLCI 200 to DLCI 202 at Site 3 Enter the following CLI commands:
add fr switch map 152 100 100 302181139710311 slave frdce add fr switch map 152 200 202 302181142020321 master frdce
Switch Maps for Site 3 The switch maps for Site 3 are as follows: DLCI 201 to DLCI 101 at Site 1 DLCI 202 to DLCI 200 at Site 2 Enter the following CLI commands:
add fr switch map 161 201 101 302181139710311 slave frdce add fr switch map 161 202 200 302181140042311 slave frdce
Switch Map for Site 4 The DLCI at Site 4 is mapped to DLCI 102 at Site 1. Enter the following CLI command to define this switch map:
add fr switch map 164 102 102 302181139710311 slave frdce
6-14
Defining Optional Frame Relay PVC and SVC Parameters

After the frame relay switch maps have been provisioned for each site in your network, you may wish to provision individual PVC and SVC parameters for some or all of your virtual circuits in order to customize your network to meet your application requirements. To provision frame relay PVC parameters, enter the following CLI command:
define fr switch pvc maxRxFrameSize maxTxFrameSize rxBe rxCIR txBe txCIR
For each of the above PVC parameters, you must specify the ifIndex of the FrameRelay DCE port on the Passport 4400 to which the FRAD is attached, and the DLCI of the particular PVC. Valid DLCI numbers for PVCs are from 16 to 991, inclusive. Notice the example below:
define fr switch pvc maxrxframesize <IfIndex> <DLCI> <MaxRxFrameSize> : INTEGER (1..255) : INTEGER (16..991) : INTEGER (0..4096)
For DLCI 100 at Site 1 in Figure 6-5, the command to set the maximum receive frame size at 1500 bytes would be as follows: define fr switch pvc 152 100 1500 The PVC parameters are described below.
maxRxFrameSize maxTxFrameSize rxBe The maximum frame size in bytes that will be accepted on this DLCI. The range is from 0 to 4096. The default value is 1600. The maximum frame size in bytes that will be transmitted on this DLCI. The range is from 0 to 4096. The default value is 1600. The maximum burst size (temporary data rate above the CIR) in bits per second (bps) that will be accepted on this DLCI. The range is from 0 to 2560000 bps. The default is 0. The data rate in bps that the network agrees to deliver on this DLCI. The range is from 0 to 2560000 bps. The default is 128000. The maximum burst size (temporary data rate above the CIR) in bits per second that will be transmitted on this DLCI. The range is from 0 to 2560000 bps. The default is 0. The estimated data rate in bps that the device on this DLCI will deliver to the network; the committed bandwidth to be allocated. The range is from 0 to 2560000 bps. The default is 128000.
rxCIR txBe
txCIR
6-15
To provision frame relay SVC parameters, use the following CLI command:
define fr switch svc discardPriority dna maxRxBurstSize maxRxSize maxTxBurstSize maxTxSize minRxThroughput minTxThroughput rxExcessBurstSize txExcessBurstSize txPriority
For each of the above SVC parameters, you must enter the ConnectID for the SVC. An example command is given below.
define fr switch svc dna <ConnectID> <DNA> : INTEGER (1..65535) : Frame Relay DNA (as a quoted string)(3..30)
Each frame relay switch map has a unique ConnectID that is assigned by the system when the switch maps are provisioned. To find the ConnectID for the SVC you are provisioning, use the following CLI command:
show fr switch map configured table LocalNetIfIndex LocalNetDLCI ConnectID RemoteNetDLCI SVCIfIndex SVCDNA SVCDLCI LocalPVCDLCIState SVCUserDLCIState ConnectType LastChange SwitchDisconnReason SwitchType : : : : : : : : : : : : : 152 100 2 100 155 "[x121]302181140042311" 25 active active master 00Years 000Days 16:33:09 no-reason frdce
The above display is a portion of the switch map table for Site 1 in Figure 6-5 containing DLCI 100. To define the DNA number for the SVC for DLCI 100 at Site 1, you would enter the following command: define fr switch svc dna 2 302181140042311 The remaining frame relay SVC parameters are defined below.
6-16
discardPriority
Indicates the likelyhood of frames on this SVC being discarded during periods of heavy congestion. The options are low, medium, and high-discard-level. The full SVCDNA number of the destination Passport 4400 for this SVC. The committed burst size (Bc) in bits per second (bps) in the ingress direction into the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The maximum frame size in bytes that will be received into the frame relay network from this SVC. The range is from 0 to 4096 frames. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The committed burst size (Bc) in bits per second (bps) in the egress direction out of the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The maximum frame size in bytes that will be transmitted out of the frame relay network by this SVC. The range is from 0 to 4096 frames. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of receive data during call setup. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of transmit data during call setup. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The excess burst size (Be) in bits per second in the ingress direction into the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The excess burst size (Be) in bits per second in the egress direction out of the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the value configured for the line is used for this SVC. The relative priority of the traffic on this SVC. The range is from 0 to 15, with higher numbers indicating higher priority. Voice traffic generally has a higher transport priority than data because it has a lower tolerance for delay. The default transport priority for frame relay traffic is 6.
dna maxRxBurstSize
maxRxSize
maxTxBurstSize
maxTxSize
minRxThroughput
minTxThroughput
rxExcessBurstSize
txExcessBurstSize
txPriority
6-17
After defining PVC and SVC parameters, you must execute the following commands in order to save the changes to configuration memory and cause them to take effect.
Defining Optional Frame Relay System Parameters

The Passport 4400 supports up to 255 DLCIs and 32 virtual ports. These numbers are user-configurable, however, using the define fr system command options. To change the values of the frame relay system parameters, use the following CLI commands.
define fr system maxdlciperline <MaxDLCIPerLine> : INTEGER (1..255)
The maximum number of DLCIs that will be permitted on a single Frame Relay DCE port. If you are only using Port 1 on the Base Module for frame relay pass-through, you can leave this parameter at the default setting of 255. If you have two Data Expansion Modules installed and you are using the maximum allowable 17 Frame Relay DCE ports, you may want to set this parameter to 15 to ensure you do not exceed the maximum total of 255 for the device.
define fr system maxnumberofdlci <MaxNumberOfDLCI> : INTEGER (1..255)
The maximum total number of DLCIs supported by the Passport 4400. The default value is 255.
define fr system maxvirtualport <MaxVirtualPort> : INTEGER (1..32)
The maximum number of virtual ports supported by the Passport 4400. The default value is 32.
define fr system numberingplan <NumberingPlan> : e164 | x121
The DNA numbering plan used by the Passport 4400. The default numbering plan is x121. To check the current values of the frame relay system parameters, enter the following CLI command:
show fr system configured MaxNumberOfDLCI MaxDLCIPerLine : 255 : 255 MaxVirtualPort NumberingPlan : 32 : x121
6-18
After defining frame relay system parameters, you must execute the following commands in order to save the changes to configuration memory and cause them to take effect.
Overriding the DNA Numbering Plan If you need to enter a DNA number using the numbering plan not currently configured, you can either change the numbering plan using the define fr system numberingplan command as described above, or you can override the current numbering plan by entering the other numbering plan type within square brackets [ ] in front of the DNA number. Below is an example of an override command.
add rsi server "[e164]3021811455000" <ServerName> <ServerType> : String (0..50) : primary | secondary
The ServerName is a name you assign to the local Passport 4400. The ServerType indicates whether the link from the Passport 4400 to the Remote Server Access (RSA) is a primary or secondary link. In the DNA string, characters entered after the first letter of the numbering plan type are treated as wildcards as long as they are contained inside the square brackets. As a result, the following command string would also change the numbering plan.
add rsi server "[e]3021811455000" <ServerName> <ServerType>
Defining Optional Frame Relay Line Parameters

Frame relay line parameters include LMI protocol parameters, PVC signaling parameters, and data rate and congestion control parameters for each logical frame relay connection. These parameters are divided into two groups: line network parameters and line user parameters. For most applications, the optional frame relay line parameters can be left at their default settings. For each configurable line parameter that you wish to change, you must first enter the ifIndex of the frame relay service for the port you are provisioning; then enter the desired value or setting for the parameter. The define frame relay line command options are given below, followed by brief definitions for each configurable parameter.
6-19
define fr line network proprietaryservice consecutiveFrames The number of consecutive frames that will be received with the BECN bit set before the transmit rate is reduced. The range is from 1 to 100 frames; default = 10. delta The number of seconds during which received frames are checked to see whether the FECN bit is set or cleared. The transmit rate is adjusted based on the number FECN bits set or cleared during this interval. The range is from 1 to 255 seconds; default = 1. Note: This setting is valid only if flow control is enabled. Determines whether or not frames exceeding the maximum allowable rate will be discarded during periods of heavy congestion. Default = disabled. The maximum frame size in bytes that will be accepted on this ifIndex. The range is from 1 to 4096. The default value is 1604. The maximum frame size in bytes that will be transmitted on this ifIndex. The range is from 1 to 4096. The default value is 1604. Determines whether or not rate enforcement will be imposed on this ifIndex for congestion management. Default = disabled. The maximum burst in bits per second (bps) that will be received on this ifIndex. The range is from 0 to 2560000 bps. The default is 0, which indicates that the network default value is used. Consult your frame relay service provider for this value. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of receive data during call setup. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the default value for the network is used for this ifIndex. The maximum burst in bits per second (bps) that will be transmitted on this ifIndex. The range is from 0 to 2560000 bps. The default is 0, which indicates that the network default value is used. Consult your frame relay service provider for this value. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of transmit data during call setup. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the default value for the network is used for this ifIndex.
flowControl
maxRxFrameSize maxTxFrameSize rateEnforcement rxBe
rxThroughput
txBe
txThroughput
define fr line network pvcsignalling netN392 netT392 Determines the user-side N392 error threshold value for this ifIndex. The range is from 1 to 10; default = 3. Indicates the time interval in seconds for the T392 Polling Verification timer. The range is from 5 to 30 seconds; default = 15.
6-20
define fr line user basedlcmi committedInfoRate The CIR in bits per second (bps) for the primary frame relay link between the Passport 4400 and the network. The range is from 0 to 2560000 bps; default = 64000.
consecutiveFrames The number of consecutive frames that will be received with the BECN bit set before the transmit rate is reduced. The range is from 1 to 100 frames; default = 10. infoRateAdjInterval The number of seconds during which received frames are checked to see whether the FECN bit is set or cleared. The transmit rate is adjusted based on the number FECN bits set or cleared during this interval. The range is from 1 to 255 seconds; default = 1. define fr line user basepvclmi bidirectional bidirectional lmiMode Indicates whether the PVC LMI will send both status inquiries and status reports. The default is false. Indicates whether the local PVC LMI is operating in DTE or DCE mode. The default setting is unidte.
define fr line user basesvclmi maxDLCI maxNumberOfCalls maxRxFrameSize The highest DLCI number allowed for an SVC on the Passport 4400. The range is from 17 to 991; default = 991. The maximum number of SVC connections allowed on the Passport 4400. The range is from 1 to 255; default = 255. The maximum frame size in bytes that will be accepted on the primary frame relay link between the Passport 4400 and the network. The range is from 0 to 4096. The default value is 0, which indicates that the maximum frame size is determined by the MPANL configuration (add msm dtelink command). Unless overwritten at connect time, this data rate in bits per second (bps) is used along with minRxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. If left at 0 (the default), the network will determine the data rate. The maximum frame size in bytes that will be transmitted on the primary frame relay link between the Passport 4400 and the network. The range is from 0 to 4096. The default value is 0, which indicates that the maximum frame size is determined by the MPANL configuration (add msm dtelink command).
maxRxThroughput
maxTxFrameSize
6-21
maxTxThroughput
Unless overwritten at connect time, this data rate in bits per second (bps) is used along with minTxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. If left at 0 (the default), the network will determine the data rate. The smallest DLCI number allowed for an SVC on the Passport 4400. The range is from 16 to 991; default = 16. Unless overwritten at connect time, this data rate in bits per second (bps) is used along with maxRxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. If left at 0 (the default), the network will determine the data rate. Unless overwritten at connect time, this data rate in bits per second (bps) is used along with maxTxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. If left at 0 (the default), the network will determine the data rate. The burst size (Bc) in bytes that the network is committed to receive. The range is from 0 to 2560000 bps. If left at 0 (the default), the network default will determine the receive burst size. The uncommitted receive burst size (Be) in bytes. The range is from 0 to 2560000 bps. If left at 0 (the default), the network default will determine the receive burst size. Determines how long the SVC LMI waits for a response from the network before transmitting the setup message. The range is from 1 to 255 seconds; default = 4 seconds. Determines how long the SVC LMI waits for a response from the network before transmitting a release message. The range is from 1 to 255 seconds; default = 30 seconds. The length of time in seconds that the SVC LMI will wait for a response from the network before retransmitting the release message. When the second release is transmitted, the local SVC LMI considers the corresponding SVC to have been released by the network even if no response has been received. The range is from 1 to 255 seconds; default = 4 seconds. The length of time in seconds that the SVC LMI will wait for a Connect message from the network, after receiving the Call Proceeding message, before sending a Release message. The range is from 1 to 255 seconds; default = 60 seconds. The burst size (Bc) in bytes that the network is committed to transmit. The range is from 0 to 2560000 bps. If left at 0 (the default), the network default will determine the transmit burst size. The uncommitted transmit burst size (Be) in bytes. The range is from 0 to 2560000 bps. If left at 0 (the default), the network default will determine the transmit burst size.
minDLCI minRxThroughput
minTxThroughput
rxBurstSize
rxExcessBurstSize
t303
t305
t308
t310
txBurstSize
txExcessBurstSize
6-22
define fr line user mpanllmi service cugAccess Determines the subscribed Closed User Group access rights. Options are noRight (the default), outgoingAccess, incomingAccess, and outAndinAccess. Options are noCUG (the default), SimpleCUG, and CUGSelection. A quoted string of up to 5 digits, determined at subscription time. Determines the CUG interloc code type. Options are national (the default) and international. A quoted string of up to 3 digits that identifies the MPANL service.100 = LAN service; 101 = NMS traffic; 200 = voice; 3XX = FRDCE/HTDS; and 500 = RSA/RSI.
cugFacility cugIC cugICType dnaSuffix
define fr line user pvclmi n391 The number of status enquiry intervals that pass before a full status enquiry message is sent. (Every nth status enquiry will be a full status enquiry.) The range is from 1 to 255; default = 6. The maximum number of unanswered status enquiries that will be accepted before the LMI is declared down. The range is from 1 to 10; default = 3. The number of seconds between successive status enquiry messages. The range is from 5 to 30 seconds; default = 10 seconds.
n392
t391
6-23
Defining Optional Frame Relay Virtual Port Parameters

The same SVC parameters that are provisioned for the frame relay switch maps can also be provisioned for the SPVCs that attach the Passport 4400 to the Passport ILS Core Router. These SPVCs are usually associated with ifIndices 2 and 4 on Port 2 of the Passport 4400. The CLI command is given below, followed by brief definitions for each configurable parameter.
define fr port spvclandata svc discardPriority Indicates the likelihood of frames on this SVC being discarded during periods of heavy congestion. The options are low, medium, and high-discard-level. The maximum frame size in bytes that will be received into the frame relay network from this SVC. The range is from 0 to 4096 frames. If this value is left at 0 (the default), the network default value is used for this SVC. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of receive data during call setup. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the network default value is used for this SVC. The maximum frame size in bytes that will be transmitted out of the frame relay network by this SVC. The range is from 0 to 4096 frames. If this value is left at 0 (the default), the network default value is used for this SVC. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of transmit data during call setup. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the network default value is used for this SVC. The minimum receive throughput in bits per second (bps); used with the maxRxThroughput value to negotiate with the remote. If this value is left at 0 (the default), the network default value is used for this SVC. The minimum transmit throughput in bits per second (bps); used with the maxTxThroughput value to negotiate with the remote. If this value is left at 0 (the default), the network default value is used for this SVC. The committed burst size (Bc) in bits per second (bps) in the ingress direction into the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the network default value is used for this SVC. The excess burst size (Be) in bits per second in the ingress direction into the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the network default value is used for this SVC.
maxRxSize
maxRxThroughput
maxTxSize
maxTxThroughput
minRxThroughput
minTxThroughput
rxBurstSize
rxExcessBurstSize
6-24
txBurstSize
The committed burst size (Bc) in bits per second (bps) in the egress direction out of the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the network default value is used for this SVC. The excess burst size (Be) in bits per second in the egress direction out of the frame relay network. The range is from 0 to 2560000 bps. If this value is left at 0 (the default), the network default value is used for this SVC. The relative priority of the traffic on this SVC. The range is from 0 to 15, with higher numbers indicating higher priority. Voice traffic generally has a higher transport priority than data because it has a lower tolerance for delay. The default transport priority for frame relay traffic is 6.
txExcessBurstSize
txPriority
Note: The define fr port svclandata CLI command is not used in Release 2.0 of the Passport 4400.
Frame Relay Monitoring

The Passport 4400 provides numerous displays that enable a network manager or individual Passport 4400 operator to view the status and performance of frame relay connections or check the values of configuration parameters. The statistical tables and status displays do not provide automatic real-time updates; they present static data as of the time of execution of the corresponding show command. Viewing Frame Relay System Parameters The following show commands may be used to view current operational and/or configured values for frame relay system parameters.
show fr system configured show fr system operational MaxNumberOfDLCI MaxDLCIPerLine : 255 : 255 MaxVirtualPort NumberingPlan : 32 : x121
The values shown above are the default values for the Passport 4400. The numbering plan can be set to e164 rather than x121, and the maximum number of DLCIs and virtual ports can be set to lesser values if desired. If you have multiple physical ports utilizing frame relay, you will probably want to set MaxDLCIPerLine to a smaller value so that the sum of all the DLCIs on all the lines does not exceed the value of MaxNumberOfDLCI.
6-25
Viewing Frame Relay Switch Maps The following commands allow you to view either configured or operational frame relay switch maps. By selecting entry, you can specify a single switch map; by selecting table, you can view all switch maps. The example below is the first switch map in an example table.
show fr switch map configured table show fr switch map operational table LocalNetIfIndex LocalNetDLCI ConnectID RemoteNetDLCI SVCIfIndex SVCDNA SVCDLCI LocalPVCDLCIState SVCUserDLCIState ConnectType LastChange SwitchDisconnReason SwitchType : : : : : : : : : : : : : 152 100 2 200 155 "[x121]302181140042321" 25 active active master 00Years 000Days 16:33:09 no-reason frdce
LocalNetIfIndex
When the switch type is FRDCE, this indicates the ifIndex of the local DCE interface. When the switch type is HTDS, this indicates the ifIndex of the local WAN interface. The DLCI value on the local DCE interface. This is always 16 if the switch type is HTDS. The Connect ID of this SPVC mapping. The DLCI value on the remote DCE interface. This value is carried in the user-to-user signaling of the SVC call setup to the remote 4400. The ifIndex of the local DTE interface on which this SVC is to be established with the remote 4400. The DNA of the remote node with which the SVC will be established. The DLCI value of the SVC, once the SVC has been established. Indicates whether the DCE sees the local PVC associated with this mapping as active or inactive. Indicates whether the DCE sees the SVC associated with this mapping as active or inactive. Whether this end of the SPVC segment initiated the SVC call (master) or not (slave).
LocalNetDLCI ConnectID RemoteNetDLCI
SVCIfIndex SVCDNA SVCDLCI LocalPVCDLCIState SVCUserDLCIState ConnectType
6-26
LastChange SwitchDisconnReason SwitchType
The time this PVC mapping entered its current operations state. The reason for SPVC inactivity in the case of a connection failure. The type of SPVC connection FRDCE (Frame Relay DCE) or HTDS.
Viewing Frame Relay Switch SVC Parameters The following commands allow you to view either configured or operational frame relay switch SVC parameters. By selecting entry, you can specify a single ConnectID; by selecting table, you can view all ConnectIDs. The example below is the first ConnectID in an example table.
show fr switch svc base configured table show fr switch svc base operational table ConnectID DNA DLCI MaxTxSize MaxRxSize TxThroughput RxThroughput MaxTxBurstSize MaxRxBurstSize TxExcessBurstSize RxExcessBurstSize TxPriority ReasonForDisconnect DiscardPriority Ifindex : : : : : : : : : : : : : : : 2 "[x121]302181140042321" 25 0 0 0 0 0 0 0 0 6 normal-condition medium-discard-level 155
ConnectID DNA DLCI MaxTxSize
The Connect ID of the SVC. The remote DNA to associate the SVC with the corresponding virtual port. The DLCI for the connected SVC. The maximum transmit frame size allowed to negotiate with the remote (in bytes). A value of 0 indicates the network default values are to be used. The maximum receive frame size allowed to negotiate with the remote (in bytes). A value of 0 indicates the network default values are to be used.
MaxRxSize
6-27
TxThroughput
The maximum transmit throughput allowed to negotiate with the remote (in bits/sec). A value of 0 indicates the network default values are to be used. The maximum receive throughput allowed to negotiate with the remote (in bits/sec). A value of 0 indicates the network default values are to be used. The maximum committed transmit burst size allowed to negotiate with the remote (in bytes). A value of 0 indicates the network default values are to be used. The maximum committed receive burst size allowed to negotiate with the remote (in bytes). A value of 0 indicates the network default values are to be used. The uncommitted (excess) transmit burst size allowed to negotiate with the remote (in bytes). A value of 0 indicates the network default values are to be used. The uncommitted (excess) receive burst size allowed to negotiate with the remote (in bytes). A value of 0 indicates the network default values are to be used. Transfer priority level for data on this SVC. All data on this SVC will be sent through the switches at the requested transfer priority level. The cause code describing the reason that the SVC was not established. The discard priority used for connection setup of this SVC map low, medium, or high. The ifIndex associated with this SVC DLCI.
RxThroughput
MaxTxBurstSize
MaxRxBurstSize
TxExcessBurstSize
RxExcessBurstSize
TxPriority
ReasonForDisconnect DiscardPriority IfIndex
Monitoring Frame Relay Switch SVC Performance The following commands allow you to monitor the frame relay traffic on each SVC circuit. By selecting entry, you can specify a single DLCI; by selecting table, you can view the traffic on all DLCIs. The example below is the first DLCI in a circuit table.
show fr switch svc circuit entry show fr switch svc circuit table IfIndex SVCDLCI Type DNA State RxFECNs RxBECNs TxFrames : : : : : : : : 155 19 switched "[x121]302181140042334" active 0 0 0
6-28
TxOctets RxFrames RxOctets CreationTime CallOriginator LastTimeChange Throughput NegMaxTxSize NegMaxRxSize NegTxThroughput NegRxThroughput NegTxBurstSize NegRxBurstSize NegTxExcessSize NegRxExcessSize TxDiscardCIRPolice TxPriority SVCIfIndex DiscardPriority
: : : : : : : : : : : : : : : : : : :
0 0 0 00Years 000Days 00:00:03 "" 00Years 000Days 00:00:03 0 4096 4096 1910000 1910000 63896 63896 0 0 0 6 155 medium-discard-level
IfIndex SVCDLCI Type DNA State RxFECNs RxBECNs TxFrames TxOctets RxFrames RxOctets CreationTime CallOriginator LastTimeChange
The ifIndex associated with this SVC. The local DLCI for this SVC, valid only when the connection has been established. The type of this SVC. Valid types include voice, switched or RFC1490. The DNA of the destination node associated with this SVC. The state of this SVC (active or inactive). The number of frames received from the network indicating forward congestion. The number of frames received from the network indicating backward congestion. The number of frames sent from this SVC since this counter was last reset. The number of octets sent from this SVC since this counter was last reset. The number of frames received over this SVC since this counter was last reset. The number of octets received over this SVC since this was counter was last reset. The time when connection of this SVC was established. The DNA of the SVC call originator. The time when the state of this SVC was last changed.
6-29
Throughput NegMaxTxSize NegMaxRxSize NegTxThroughput NegRxThroughput NegTxBurstSize NegRxBurstSize NegTxExcessSize NegRxExcessSize TxDiscardCIRPolice TxPriority SVCIfIndex DiscardPriority
The average number of 'Frame Relay Information Field' bits transferred per second across a physical frame relay interface. The negotiated maximum transmit size to be sent on this interface (in bytes). The negotiated maximum receive size to be sent on this interface (in bytes). The negotiated transmit throughput to be sent on this interface (in bits/sec). The negotiated receive throughput to be sent on this interface (in bits/sec). The negotiated transmit committed burst to be sent on this interface (in bits/sec). The negotiated receive committed burst to be sent on this interface (in bits/sec). The negotiated transmit excess burst to be sent on this interface (in bits/sec). The negotiated receive excess burst to be sent on this interface (in bits/sec). The number of packets that have been discarded due to policing of the CIR. The transfer priority used for connection setup of this SVC, ranging from 0 (lowest) to 15 (highest). The ifIndex associated with this SVC DLCI. The discard priority used for circuit connection setup of this SVC map low, medium, or high.
Monitoring Frame Relay Switch PVC Performance PVCs exist between the third-party FRADs attached to the serial port or ports of the Passport 4400. The following commands allow you to monitor the frame relay traffic on each PVC circuit. By selecting entry, you can specify a single ifIndex and DLCI; by selecting table, you can view the traffic on all DLCIs for all ifIndices. The example below shows the parameters for the first ifIndex and DLCI in a PVC operational table.
Note: The show fr switch pvc configured command options will display the first 10 parameters in the list below, with the exception of RxBc and TxBc.
6-30
show fr switch pvc operational entry show fr switch pvc operational table IfIndex DLCI MaxRxFrameSize RxBc RxBe RxCir MaxTxFrameSize TxBc TxBe TxCIR RxFrames TxFrames RxDEFrames RxExcessFrames TxExcessFrames RxDiscards RxOctets TxOctets IfIndex DLCI MaxRxFrameSize RxBc RxBe RxCIR MaxTxFrameSize TxBc TxBe TxCIR RxFrames : : : : : : : : : : : : : : : : : : 152 100 1600 0 0 0 1600 128 0 128 0 0 0 0 0 0 0 0
The ifIndex of the local DCE interface to this PVC. The value of this object is equal to the DLCI value for this PVC end-point. The largest frame relay information field (in octets) for endpoint data sent into the frame relay network for this PVC. The committed burst size (Bc) for end-point data sent into the frame relay network (in bits) for this PVC. The committed excess size (Be) for end-point data sent into the frame relay network (in bits) for this PVC. The committed information rate (CIR) for end-point data sent into the frame relay network (in bits/sec) for this PVC. The largest frame relay information field for end-point data received from the frame relay network (in octets) for this PVC. The committed burst size (Bc) for end-point data received from the frame relay network (in bits) for this PVC. The committed excess size (Be) for end-point data received from the frame relay network (in bits) for this PVC. The committed information rate (CIR) for end-point data received from the frame relay network (in bits/sec). The number of frames received by the network (ingress) for this PVC end-point. This includes any frames discarded by the network due to submitting more than Bc + Be data, or due to any network congestion recovery procedures.
6-31
TxFrames
The number of frames sent by the network (egress), regardless of whether they are Bc or Be frames for this PVC end-point. The number of frames received by the network (ingress) with the DE (discard eligibility) bit set to (1) for this PVC end-point. The number of frames received by the network (ingress) for this PVC end-point which were treated as excess traffic. The number of frames sent by the network (egress) for this PVC end-point which were treated as excess traffic. (The DE bit may be set to one.) The number of frames received by the network (ingress) that were discarded due to traffic enforcement for this PVC endpoint. The number of octets received by the network (ingress) for this PVC end-point. If the network supporting frame relay cannot count octets, then this count should be an approximation. The number of octets sent by the network (egress) for this PVC end-point. If the network supporting frame relay cannot count octets, then this count should be an approximation.
RxDEFrames RxExcessFrames TxExcessFrames
RxDiscards
RxOctets
TxOctets
Viewing WAN Parameters The commands listed in this section allow you to view configured and/or operational parameter values for all of the WAN interfaces in the Passport 4400. By selecting entry, you can specify a single ifIndex; by selecting table, you can view parameters for all ifIndices. The operational displays contain a few parameters not found in the configured displays. The operational tables shown below contain only the first ifIndex entry in the table.
show wan parameters port configured table show wan parameters port operational table IfIndex IfType Mode BaudRate MaxRxFrameSize ProtocolType NumOfRxBuffers RxQueueSize TxQueueSize FragmentSize IfLim IfChannel ProtocolSupport HTDSCutThrough HTDSFragSize : : : : : : : : : : : : : : : 153 v35 dte 1920000 4000 hdlc 200 20 10 80 limA 2 frameRelayDTE no 0
6-32
IfIndex IfType Mode
The ifIndex corresponding to a physical WAN port. The signaling characteristics of the port. Options are RS-232, V.35, X.21, CSU/DSU, ISDN-BRI, or none. The mode (connection type) used on this port: DCE or DTE. This determines whether the Passport 4400 receives or transmits clocking signals. The transmission rate of this port, in bits per second. For DCE ports, this variable controls the baud rate; for DTE ports, this variable must be set to match the baud rate of the other end (DCE). The maximum frame size that will be received on this interface (in bytes). The link protocol type. The number of buffers configured to receive data. The size of each receive buffer (in bytes). The size of each transmit buffer (in bytes). The number of bytes into which frames exceeding the maximum frame size will be fragmented. The LIM (slot location) of the module containing this port. The channel number of this port. The transmission protocol used on this port: none, Frame Relay DCE, Frame Relay DTE, or HTDS. Sets the HTDS Cut-Through state: yes (active) or no (inactive). The maximum fragment size created by HTDS Cut-Through.
BaudRate
MaxRxFrameSize ProtocolType NumOfRxBuffers RxQueueSize TxQueueSize FragmentSize IfLim IfChannel ProtocolSupport HTDSCutThrough HTDSFragSize
show wan parameters tunnelpvc configured table show wan parameters tunnelpvc operational table IfIndex 153 DLCI 16
This display shows that ifIndex 153, corresponding to physical Port 2 on the Passport 4400, is mapped to DLCI 16 on the Passport ILS Core Router, a PVC-based service on the Passport switch.
6-33
Monitoring WAN Statistics The commands listed in this section allow you to monitor WAN statistical information for all of the WAN interfaces in the Passport 4400. By selecting entry, you can specify a single ifIndex; by selecting table, you can view statistics for all ifIndices. The operational tables shown below contain only the first ifIndex entry in the table.
show wan statistics port table IfIndex RxBlockCount TxBlockCount TxLinkUnderRuns TxLinkOverflows RxBadPackets TxLinkErrors : : : : : : : 153 14098 13041 0 0 0 0
IfIndex RxBlockCount TxBlockCount TxLinkUnderRuns TxLinkOverflows RxBadPackets TxLinkErrors
The ifIndex corresponding to this WAN port. The number of frames received over this port. The number of frames transmitted over this port. The number of reported link underruns. An underrun occurs when data is not available for transmission. The number of reported link overflows. An overflow occurs when an outgoing packet is too large for transmission. The number of HDLC packets discarded. The number of times CTS (clear to send) went down while a packet was being transferred or a link underrun occured.
show wan statistics vofr entry show wan statistics vofr table IfIndex HiPriorityCount FragmentCount PackingCount RxFragmentCount LostFragmentCount ProtViolationCount : : : : : : : 153 0 0 0 0 0 0
IfIndex HiPriorityCount
The ifIndex of the port. The number of high-priority outbound frames which have been fragmented (when frame size exceeds Maximum Frame Size).
6-34
FragmentCount PackingCount RxFragmentCount LostFragmentCount ProtViolationCount
The number of fragmentation actions applied to outbound frames. The number of outbound fragments packaged with other frames or fragments The number of incoming fragments which were assembled into larger frames. The number of incoming lost fragments. The number of incoming protocol violations detected.
Viewing Frame Relay Line Network Characteristics The commands listed in this section display characteristics of the physical ports that are used for frame relay pass-through operation. When the show fr line network command is entered, the following options are displayed:
proprietaryService pvcSignalling rfc1604Service
For each of these options, you can view configured or operational parameters. By selecting entry, you can specify a single ifIndex; by selecting table, you can view the parameters for all ifIndices. The operational tables shown below contain only the first ifIndex entry in the table.
show fr line network proprietaryservice operational table IfIndex FlowControl InfoRateAdjInterval ConsecutiveFrames RateEnforcement MaxTxFrameSize MaxRxFrameSize TxBc RxBc TxBe RxBe TxThroughput RxThroughput PVCLMIStatus : : : : : : : : : : : : : : 161 disabled 1 10 disabled 1604 1604 0 0 0 0 0 0 up
IfIndex FlowControl
The ifIndex of the local physical interface. The flow control for outbound data enabled or disabled.
6-35
InfoRateAdjInterval
The time interval used to increase or decrease the transmission rate, depending on the number of frames received with the FECN (forward explicit congestion notification) bit either cleared (for increase) or set (for decrease). The number of consecutive frames received with the BECN (backward explicit congestion notification) bit set before reduction of the transmit rate. Sets the rate enforcement parameter for frame relay congestion management processing to enabled or disabled. The maximum transmission frame relay packet size (in bytes) for this logical port. The maximum receive frame relay packet size (in bytes) for this logical port. The transmission committed burst size (in bits/sec) for this logical port. The receive committed burst size (in bits/sec) for this logical port. The transmission excess burst size (in bits/sec) for this logical port. The receive excess burst size (in bits/sec) for this logical port. The transmission committed information rate (CIR) (in bits/ sec) for this logical port. The receive committed information rate (CIR) (in bits/sec) for this logical port. The status of the PVC local management interface (LMI) up or down.
ConsecutiveFrames
RateEnforcement MaxTxFrameSize MaxRxFrameSize TxBc RxBc TxBe RxBe TxThroughput RxThroughput PVCLMIStatus
show fr line network pvcsignalling operational table IfIndex Procedure NetN392 NetN393 NetT392 NetLinkRelErrors NetProtocolErrors NetChannelInactive : : : : : : : : 161 u2nnet 3 3 15 6 0 0
IfIndex Procedure
The ifIndex of the local frame relay DCE interface. The local in-channel signaling procedure that is used for this logical port. Valid values are u2nnet and bi-direct.
6-36
NetN392
The network-side N392 error threshold value for this logical port. This applies to Q.933 Annex A, T1.617 Annex D, and LMI. If this logical port is not performing network-side procedures, this field will display noSuchName. The network-side N393 monitored events count value for this logical port. This applies to Q.933 Annex A, T1.617 Annex D, and LMI. If this logical port is not performing network-side procedures, this field will display noSuchName. The network-side T392 polling verification timer value for this logical port. This applies to Q.933 Annex A, T1.617 Annex D, and LMI. If this logical port is not performing network-side procedures, this field will display noSuchName. The number of network-side local in-channel signaling link reliability errors for this logical port. These errors are indicated by non-receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element. If this logical port is not performing network-side procedures, this field will display noSuchName. The number of network-side local in-channel signaling protocol errors for this logical port. Types include protocol discriminator, message type, call reference, and mandatory information element errors. If this logical port is not performing network-side procedures, this field will display noSuchName. The number of times the network-side channel was declared inactive. If this logical port is not performing network-side procedures, this field will display noSuchName.
NetN393
NetT392
NetLinkRelErrors
NetProtocolErrors
NetChannelInactive
show fr line network rfc1604service operational table IfIndex NumberPlan PortType AddressLength VCSignalProtocol : : : : : 161 none uni twoOctets10Bits ansiT1617D-1994
IfIndex
The ifIndex of the local Frame Relay DCE interface. (ifIndex 161 corresponds to the local DCE interface for Port 1 of Data Expansion Module 1.) The network address numbering plan for this UNI logical port. Valid responses are x121, e164, other, and none. None implies that there is no ifPhysAddress for this interface. Other indicates that an address has been assigned to this interface, but the numbering plan is not enumerated here. The type of network interface (UNI or NNI) for this logical port.
NumberPlan
PortType
6-37
AddressLength VCSignalProtocol
The Q.922 address field length and DLCI length for this logical port. The local in-channel signaling protocol used for this logical port.
Viewing and Monitoring Frame Relay Line User Characteristics The commands listed in this section display LMI parameters, performance statistics and other characteristics of the connections between the Passport 4400 and the ILS Core Router service on the Passport switch. When the show fr line user command is entered, the following options are displayed:
baseDLCMI basePVCLMI baseSVCLMI dlcmiPVC mpanlLMI pvcLMI
For each of these options, you can view configured or operational parameters. By selecting entry, you can specify a single ifIndex; by selecting table, you can view the parameters for all ifIndices. The operational tables shown below contain only the first ifIndex entry in the table.
show fr line user basedlcmi operational table IfIndex Flow Control CommittedInfoRate InfoRateAdjInterval ConsecutiveFrames MTUSize ConnectTime TxLMI RxLMI HeaderErrorRx InvalidDLCIRx ShortFramesRx LongFramesRx IgnoredFramesRx XIDExpirationst TxExpirations PVCLMIStatus SVCLMIStatus : : : : : : : : : : : : : : : : : : 155 disabled 64000 1 10 1604 00Years 000Days 00:00:00 5196 5196 0 0 0 0 0 0 0 up up
6-38
IfIndex
The ifIndex of the local frame relay interface. (IfIndex 155 corresponds to the frame relay portion of the local DTE interface at Port 2 of the Ethernet Base Module.) Indicates whether or not rate enforcement will allow frames exceeding the CIR rate to be discarded during periods of heavy congestion. The default is disabled. The CIR in bits per second (bps) for the primary frame relay link between the Passport 4400 and the network. The range is from 0 to 2560000 bps. The default is 64000. The number of seconds during which received frames are checked to see whether the FECN bit is set or cleared. The transmit rate is adjusted based on the number FECN bits set or cleared during this interval. The range is from 1 to 255 seconds. The default is 1. The number of consecutive frames that will be received with the BECN bit set before the transmit rate is reduced. The range is from 1 to 100 frames. The default is 10. Maximum Transmission Unit Size: The maximum frame size that can be sent across the frame relay network. The value of sysUpTime when this port was created. The number of PVC LMI frames sent on this physical port (DLCI 0). The number of PVC LMI frames received on this physical port (DLCI 0). The number of frames received with an incomplete or missing address field. The number of frames received on an unassigned or invalid DLCI number. The number of short frames received. The number of frames that were received that were longer than the WAN MTU size. The number of frames received that were ignored (meaning they contained an unknown error). The number of XID TM21 timer expirations. (Valid only if MTU negotiation is enabled.) The status of PVC LMI (up or down). The status of SVC LMI (up or down).
FlowControl
CommittedInfoRate
InfoRateAdjInterval
ConsecutiveFrames
MTUSize ConnectTime TxLMI RxLMI HeaderErrorRx InvalidDLCIRx ShortFramesRx LongFramesRx IgnoredFramesRx XIDExpirations PVCLMIStatus SVCLMIStatus
show fr line user basepvclmi operational table IfIndex LMIMode Bidirectional : 155 : unidte : false
6-39
IfIndex
The ifIndex of the local frame relay DTE interface. IfIndex 155 corresponds to the frame relay port of the local DTE interface at Port 2 of the Ethernet Base Module. Indicates whether the local PVC LMI is operating in DTE or DCE mode. The default setting is unidte (unidirectional DTE). Indicates whether the PVC LMI will send both status inquiries and status reports. The default is false.
LMIMode Bidirectional
show fr line user basesvclmi operational table IfIndex Type T303 T305 T308 T310 MaxNumberOfCalls MaxTxFrameSize MaxRxFrameSize MinDLCI MaxDLCI MinTxThroughput MinRxThroughput MaxTxThroughput MaxRxThroughput TxBurstSize RxBurstSize TxExcessBurstSize RxExcessBurstSize : : : : : : : : : : : : : : : : : : : 155 q933svc 4 30 4 60 255 0 0 16 991 0 0 1920000 1920000 0 0 0 0
IfIndex
The ifIndex of the local frame relay interface. (ifIndex 155 corresponds to the local DTE interface for Port 2 of the Ethernet Base Module.) The type of SVC LMI protocol used on this interface. Determines how long the SVC LMI waits for a response from the network before retransmitting the setup message. The range is from 1 to 255 seconds. The default is 4 seconds. Determines how long the SVC LMI waits for a response from the network before retransmitting a disconnect message. The range is from 1 to 255 seconds. The default is 30 seconds.
Type T303
T305
6-40
T308
The length of time in seconds that the SVC LMI will wait for a response from the network before retransmitting the release message. When the second Release is transmitted, the local SVC LMI considers the corresponding SVC to have been released by the network even if no response has been received. The range is from 1 to 255 seconds. The default is 4 seconds. The length of time in seconds that the SVC LMI will wait for a Connect message from the network, after receiving the Call Proceeding message, before sending a release message. The range is from 1 to 255 seconds. The default is 60 seconds. The maximum number of SVC connections allowed on this link IfIndex. The range is from 1 to 255. The default is 255. The maximum frame size in bytes that will be transmitted on the primary frame relay link between the Passport 4400 and the network. The range is from 0 to 4096. The default value is 0, which indicates that the maximum frame size is determined by the MPANL configuration (add msm dtelink or the define msm dtelink) command. The maximum frame size in bytes that will be accepted on the primary frame relay link between the Passport 4400 and the network. The range is from 0 to 4096. The default value is 0, which indicates that the maximum frame size is determined by the MPANL configuration (add msm dtelink or the define msm dtelink) command. The smallest DLCI number allowed for an SVC on the Passport 4400. The range is from 16 to 991. The default is 16. The highest DLCI number allowed for an SVC on the Passport 4400. The range is from 17 to 991. The default is 991. Unless negotiated at connect time, this data rate in bits per second (bps) is used along with maxTxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. A value of 0 indicates that the network will determine the data rate. Unless negotiated at connect time, this data rate in bits per second (bps) is used along with maxRxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. A value of 0 indicates that the network will determine the data rate. Unless negotiated at connect time, this data rate in bits per second (bps) is used along with maxTxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. A value of 0 indicates that, the network will determine the data rate.
T310
MaxNumberOfCalls MaxTxFrameSize
MaxRxFrameSize
MinDLCI
MaxDLCI
MinTxThroughput
MinRxThroughput
MaxTxThroughput
6-41
MaxRxThroughput
Unless negotiated at connect time, this data rate in bits per second (bps) is used along with minRxThroughput to negotiate with the remote end during call setup. The range is from 0 to 2560000 bps. A value of 0 indicates that, the network will determine the data rate. The burst size (Bc) in bytes that the network is committed to transmit over the period of one second. The range is from 0 to 2560000 bps. A value of 0 indicates that the network default will determine the transmit burst size. The burst size (Bc) in bytes that the network is committed to receive over the period of one second. The range is from 0 to 2560000 bps. A value of 0 indicates that the network default will determine the receive burst size. The uncommitted transmit burst size (Be) in bytes. The range is from 0 to 2560000 bps. A value of 0 indicates that the network default will determine the excess burst size. The uncommitted receive burst size (Be) in bytes. The range is from 0 to 2560000 bps. A value of 0 indicates that the network default will determine the excess burst size.
TxBurstSize
RxBurstSize
TxExcessBurstSize
RxExcessBurstSize
show fr line user dlcmipvc operational table IfIndex LMIType AddressType AddressLength NumberOfPorts Multicast : : : : : : 155 noLMIConfigured q922Standard twoOctets 255 nonBroadcast
IfIndex
The ifIndex of the local frame relay interface. (ifIndex 155 corresponds to the frame relay portion of the local DTE interface at Port 2 of the Ethernet Base Module.) The type of PVC LMI active on this interface. The PVC LMI selected must be compatible with the active network PVC LMI. Valid values are lmi, itut933A (Q933 Annex A), ansiT1617D 1994 (ANSI T1.617a - 1994 Annex D), and noLmiConfigured. A value of noLmiConfigured indicates that no LMI is used. PVC and DLCIs can still be configured. Identifies which address format is in use on the frame relay interface. Valid values are q921 (13-bit DLCI), q922March90 (11-bit DLCI), q922November 90 (10-bit DLCI), and q922Standard. This value must match the address format used by the network. Identifies the Q.922 address field length and DLCI length for this UNI logical port. Value is given in octets.
LMIType
AddressType
AddressLength
6-42
NumberOfPorts Multicast
Maximum number of PVC DLCIs that may exist on this line IfIndex. Indicates whether or not the frame relay interface is using a multicast service. NonBroadcast indicates no multicast. Broadcast indicates multicast service is used.
show fr line user pvclmi operational table IfIndex T391 N391 N392 N393 : : : : : 155 10 6 3 3
IfIndex
The ifIndex of the local frame relay interface. (ifIndex 155 corresponds to the local frame relay portion of the DTE interface at Port 2 of the Ethernet Base Module.) The number of seconds between successive status inquiry messages. The range is from 5 to 30 seconds. The default is 10 seconds. The number of status inquiry intervals that pass before a full status inquiry message is sent. (Every nth status inquiry will be a full status inquiry.) The range is from 1 to 255. The default is 6. The maximum number of unanswered status enquiries that will be accepted before the LMI is declared down. The range is from 1 to 10. The default is 3. The number of status polling intervals over which the error threshold is counted. The default is 3.
T391
N391
N392
N393
Viewing and Monitoring MPANL Parameters and Statistics The following three show fr line user command options display MPANL information. The first two commands show service characteristics and parameters; the third command gives calling statistcs.
show fr line user mpanllmi parameters BaseType : nortel-DPN-4400 (operational) : nortel-DPN-4400 (configured) : "MLMIswRev1.00" (operational)
SoftwareRev
6-43
BaseType SoftwareRev
Indicates the type of Passport 4400 hardware used by the MPANL LMI protocol. Indicates the current revision level of the MPANL software running on the Passport 4400 hardware.
show fr line user mpanllmi service operational table ServiceIndex CUGFacility CUGAccess CUGICType CUGIC DNASuffix : : : : : : 1 noCUG noRight national "" "100"
ServiceIndex CUGFacility CUGAccess
An index number for the MPANL service designated by the DNA suffix field. Options are noCUG (the default), SimpleCUG, and CUGSelection. Determines the subscribed Closed User Group access rights. Options are noRight (the default), outgoingAccess, incomingAccess, and outAndinAccess. Determines the CUG interlock code type. Options are national (the default) and international. A quoted string of up to 5 digits, determined at subscription time. A quoted string of up to 3 digits that identifies the MPANL service. 100 = LAN traffic; 101 = NMS traffic; 200 = voice; 3XX = FRDCE/HTDS; 500 = RSA/RSI.
CUGICType CUGIC DNASuffix
show fr line user mpanllmi statistics ActiveVCs InitiatedCalls SucceededCalls DisconnectedCalls RejectedCUGs : : : : : 9 17 9 0 0 RequestedCalls FailedCalls ReleasedCalls AdmittedCUGs : : : : 22 0 0 0
ActiveVCs RequestedCalls InitiatedCalls
Number of active virtual circuits maintained by the MPANL LMI. The number of Connect requests received by the MPANL LMI from the upper layer applications on this Passport 4400. The number of calls this Passport 4400 has initiated.
6-44
FailedCalls SucceededCalls ReleasedCalls DisconnectedCalls AdmittedCUGs RejectedCUGs
The number of calls failed, either incoming or outgoing, for this Passport 4400. The number of calls succeeded, either incoming or outgoing, for this Passport 4400. The number of calls released by this Passport 4400 or by the network. The number of Disconnect requests received by the MPANL LMI from upper layer applications on this Passport 4400. The number of calls admitted whose setup messages had the correct CUG. The number of calls rejected whose setup messages had the wrong CUG.
Monitoring Frame Relay Virtual Port Parameters The Passport 4400 allows you to view the configurations and condition of the individual virtual port SPVCs and SVCs between the Passport 4400 and the ILS Core Router on the Passport switch. The displays are very similar to the show fr switch svc displays mentioned earlier in this chapter.
show fr port virtualport configured table show fr port virtualport operational table IfIndex 2 4 PhyPointOfAttach 0 1 Mode basic basic State up up ProtocolBinding ip-configured ip-configured
IfIndex
The IfIndex of the virtual port. The default virtual port for user LAN traffic over the WAN is 2. The virtual port for frame relay network management traffic is 4. The PPA number of the interface. This value is assigned internally. For an explanation of PPA number see the show system IfIndex command for more information. The mode of routing defined for the frame relay virtual port. Easyrouter is important when the Passport 4400 is used as a core user (NMS) router. In Easyrouter mode, LAN traffic is switched at the virtual port level, using the bridges MAC address/DLCI table to route the packet to another DLCI. Easyrouter mode also allows broadcasts to be generated to each DLCI on that virtual port. Basic mode is used when a third party router is connected to the core router. Exactly 1 DLCI will be supported in basic mode.
PhyPointOfAttach
Mode
6-45
State ProtocolBinding
The state of the virtual port. Possible states are up, down and uninitialized. Indicates the protocols bound to this virtual port.
show fr port spvclandata base spvc configured table show fr port spvclandata base spvc operational table VirtualPortIfIndex RemoteNetDLCI ConnectId SVCDNA SVCDLCI SVCIfIndex VirtualPortState SVCUserState ConnectType LastChange LastTimeDiscReason : : : : : : : : : : : 4 241 1 "[x121]3021811397299" 17 155 active active master 99 local-VP-is-down
VirtualPortIfIndex RemoteNetDLCI ConnectId
The IfIndex of the local virtual port. The DLCI value on the remote DCE interface. The connect ID of this SPVC mapping. Assigned internally by the Passport 4400. Unique for each SPVC generated on the Passport 4400 (frame relay DCE and LAN). The DNA for the remote node of this SPVC. The local DLCI for this SPVC. The ifIndex number for this SPVC connection. Indicates whether the local virtual port is active or inactive. Indicates whether the local DCE considers the SPVC associated with this mapping active (up) or inactive (down). Indicates whether this end of the SPVC segment initiated or received the SPVC call. Master indicates that this end will initiate the call; Slave indicates that this end will receive the call. The MIB II sysUpTime value in time ticks at the time this SPVC mapping entered its current operational state. Indicates the reason this SPVC is not currently active.
SVCDNA SVCDLCI SVCIfIndex VirtualPortState SVCUserState ConnectType
LastChange LastTimeDiscReason
6-46
show fr port spvclandata base svc operational table ConnectId SVCIfIndex DNA DLCI MaxTxSize MaxRxSize MinTxThroughput MinRxThroughput MaxTxThroughput MaxRxThroughput TxBurstSize RxBurstSize TxExcessBurstSize RxExcessBurstSize TxPriority ReasonForDisconnect DiscardPriority : : : : : : : : : : : : : : : : : 1 155 "[x121]3021811397299" 17 0 0 0 0 0 0 0 0 0 0 6 normal-condition medium-discard-level
ConnectID SVCIfIndex DNA DLCI MaxTxSize
The connect ID of this SPVC mapping. The IfIndex of the frame relay protocol associated with this DLCI. The DNA for the destination of the SPVC. The local DLCI for this SVC. The maximum frame size in bytes that will be transmitted out of the frame relay network by this SVC. The range is from 0 to 4096 frames. A value of 0 indicates that the network default value is used for this SVC. The maximum frame size in bytes that will be received into the frame relay network from this SVC. The range is from 0 to 4096 frames. A value of 0 indicates that the network default value is used for this SVC. The minimum transmit throughput in bits per second (bps); used with the maxTxThroughput value to negotiate with the remote. A value of 0 indicates that the network default value is used for this SVC. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of receive data during call setup. The range is from 0 to 2560000 bps. A value of 0 indicates that the network default value is used for this SVC. The Committed Information Rate (CIR) in bits per second (bps) used for negotiation of transmit data during call setup. The range is from 0 to 2560000 bps. A value of 0 indicates that the network default value is used for this SVC.
MaxRxSize
MinTxThroughput
MinRxThroughput
MaxTxThroughput
6-47
MaxRxThroughput
The minimum receive throughput in bits per second (bps); used with the maxRxThroughput value to negotiate with the remote. The network default value is used for this SVC. The committed burst size (Bc) in bits per second (bps) to the frame relay network. The range is from 0 to 2560000 bps. The network default value is used for this SVC. The committed burst size (Bc) in bits per second (bps) from the frame relay network. The range is from 0 to 2560000 bps. The network default value is used for this SVC. The excess burst size (Be) in bits per second to the frame relay network. The range is from 0 to 2560000 bps. The network default value is used for this SVC. The excess burst size (Be) in bits per second from the frame relay network. The range is from 0 to 2560000 bps. The network default value is used for this SVC. The relative priority of the traffic on this SVC. The range is from 0 to 15, with higher numbers indicating higher priority. Maps both as an emission priority out of the Passport 4400 and the Passport switch trunk through priority. Voice traffic generally has a higher transport priority than data because it has a lower tolerance for delay. The default transport priority for frame relay traffic is 0. Indicates the reason for the last SPVC disconnect. Indicates the probability of frames on this SVC being discarded by the Passport switch during periods of heavy congestion. The options are low, medium, and high-discardlevel.
TxBurstSize
RxBurstSize
TxExcessBurstSize
RxExcessBurstSize
TxPriority
ReasonForDisconnect DiscardPriority
show fr port spvclandata circuit table IfIndex SVCDLCI Type DNA State RxFECNs RxBECNs TxFrames TxOctets RxFrames RxOctets CreationTime CallOriginator LastTimeChange Throughput NegMaxTxSize NegMaxRxSize : : : : : : : : : : : : : : : : : 4 17 rfc1490Switched "[x121]3021811397299" active 0 0 7770 603783 8820 638704 00Years 000Days 00:00:03 "" 00Years 000Days 00:00:03 920 4096 4096
6-48
NegTxThroughput NegRxThroughput NegTxBurstSize NegRxBurstSize NegTxExcessSize NegRxExcessSize TxDiscardCIRPolice TxPriority SVCIfIndex DiscardPriority
: : : : : : : : : :
1917000 64000 63896 64000 0 0 0 6 155 medium-discard-level
IfIndex SVCDLCI Type DNA State RxFECNs RxBECNs TxFrames TxOctets RxFrames RxOctets CreationTime
The ifIndex associated with this SVC DLCI. The DLCI number associated with this SVC. The type of network interface for this logical port. Valid types are rfc 1490, voice, switched, and rfc1490 switched. The DNA of the destination node for this SVC. Indicates the current state of this SVC. May be active, inactive or invalid. The number of frame relay packets received on this DLCI with the FECN bit set since this counter was last reset. The number of frame relay packets received on this DLCI with the BECN bit set since this counter was last reset. The number of frame relay packets sent on this SVC since this counter was last reset. The number of octets sent on the corresponding SVC since this counter was last reset. The number of frames received over this SVC since it was created or the counter was last reset. The number of octets received over this SVC since it was created or the counter was last reset. The sysUpTime value when the SVC was created either at bootup time or when the SVC was set up through Q.933, whether by the Data Link Connection Management Interface or by a SetRequest. The DNA of the node originating the call that resulted in the establishment of the SVC. The value of sysUpTime when the state of the SVC last changed. (For SVCs established by the remote, the last time change should be equal to the SVC creation time.)
CallOriginator LastTimeChange
6-49
Throughput
The average number of frame relay information field bits transferred per second across a user network interface in one direction. This is measured over the measurement interval. The negotiated maximum frame size to be transmitted on this interface (in bytes). The negotiated maximum frame size to be received on this interface (in bytes). The negotiated throughput to be transmitted on this interface (in bits per second). The negotiated throughput to be received on this interface (in bits per second). The negotiated committed burst to be transmitted on this interface (in bits per second). The negotiated committed burst to be received on this interface (in bits per second). The negotiated excess burst to be transmitted on this interface (in bits per second). The negotiated Rx excess burst to be sent on this interface (in bits per second). The number of packets that have been discarded due to policing of the CIR. The relative priority of the traffic on this SVC. The range is from 0 to 15, with higher numbers indicating higher priority.APS both as emission priority out of the Passport 4400 and the Passport switch trunk through priority. Voice traffic generally has a higher transport priority than data because it has a lower tolerance for delay. The default transport priority for frame relay traffic is 0. The ifIndex of the frame relay protocol on the physical port. Indicates the probability of frames on this SVC being discarded by the Passport switch during periods of heavy congestion. The options are low- medium- and high-discardlevel.
NegMaxTxSize NegMaxRxSize NegTxThroughput NegRxThroughput NegTxBurstSize NegRxBurstSize NegTxExcessSize NegRxExcessSize TxDiscardCIRPolice TxPriority
SVCIfIndex DiscardPriority
6-50
HDLC Transparent Data Services

Introduction to HDLC transparent data services (HTDS) over a Passport network Provisioning procedures for HTDS.
HDLC and Frame Relay Pass-through The high-level data link control (HDLC) protocol is a set of ISO-defined procedures for carrying data over a link, usually with error detection and flow control. The HDLC Transparent Data Service (HTDS) provides end-to-end connectivity between applications (e.g. X.25 PAD) running over HDLC. This allows for a way of tunneling HDLC traffic over the frame relay backbone, thereby allowing networking of legacy protocols and equipment. With HTDS, the Passport 4400 unit provides a mechanism to tunnel legacy traffic over the WAN, which affords consolidation for existing co-located X.25 PAD devices. The applications (upper-layer protocols) are responsible for handling lost or aborted data.
HDLC port X.25 PAD
FRDTE port
Passport 4400 MPANL
FRUNI
MPANL
Figure 7-1. HDLC Tunneled over Frame Relay
7-1
Transfer modes There are two choices of providing the HTDS: cut-through store and forward The transfer modes are user-configurable.
Note: The HTDS must suppress idle flags, etc. Therefore it only forwards data frames across the WAN.
Cut-through transfer mode
The cut-through transfer mode does not wait for the entire frame to be received on the HDLC port before transferring the data over the frame relay WAN. Instead, it begins transferring a fixed number of incoming bytes as fragments. This mode allows the Passport 4400 unit to handle low speed traffic with large frames at low latency/delay. The source 4400 unit inserts a sequence number, unique within an HDLC frame, before transferring them across the WAN. The receiving 4400 unit uses this sequence number to order and re-assemble the frames before emission on the HDLC port. To prevent under-run on the HDLC port, the Passport 4400 maintains a jitter buffer. In cases of under-runs or out-of-sequence fragments, the destination 4400 unit aborts the frame on the port and tosses subsequent fragments belonging to the aborted frames. At the receiving end, the destination 4400 unit passes the fragments as they are received as frames on its HDLC port.
Store and forward transfer mode
The store and forward transfer mode buffers an entire frame received on its HDLC link before transferring it over the frame relay backbone. The destination Passport 4400 unit receives the entire HDLC frame before it begins to emit the HDLC data on its HDLC port.
7-2
HTDS provisioning procedures

What you need to know: On the Passport 4400 unit, the following parameters need to be provisioned for the port using the HTDS service: The DNA of the destination end. (This is signaled as the called party DNA.) The local and remote ports (ifIndices) used as end-points of the HTDS connection. The transfer mode (either cut-through or store and forward). Master or slave. Specify whether the switched permanent virtual circuit (SPVC) end-point is the master or slave.
Provisioning Guidelines for HTDS pass-through The following general guidelines should be kept in mind when attaching an HDLC device to the Frame Relay DCE port (Port 1) on a Passport 4400 Base Module (see Figure 6-3 below): Port 2 on the Passport 4400 Base Module is the primary WAN link used to carry frame relay traffic between the Passport 4400 and the Passport switch. Port 3 is a serial WAN backup port. Port 1 is defaulted to DCE. Port 1 can usually be configured for DTE, if necessary. However, if there is a CSU/DSU installed in Port 3 on the Base Module, Port 1 cannot be configured for DTE.
Frame Relay DCE serial access port (Port 1)
Ethernet Access Ports 10BaseT AUI
Management port
Port 2
Port 3 Back panel Interface Modules
Figure 7-2. Serial Access Ports on the Passport 4400 Ethernet Base Module (Rear View)
7-3
The default clocking on Port 1 is internal. If Port 1 is provisioned for DTE, set the clocking to external. The default line speed on Port 1 is 64 kbps; the maximum line speed is 1.92 Mbps. Be sure that the Port 1 line speed is set to a lower value than the Port 2 line speed. The LMI on the Passport 4400 is defaulted to ANSI. LMI must be disabled for HTDS pass-through. The local DLCI number must match the PVC DLCI as seen by the device attached to the Frame Relay DCE port on the Passport 4400.
Within the Passport 4400 network cloud, all connections are SVCs. If either end of a connection between FRADs established over a Passport 4400 network loses the PVC LMI, the SVC call between the Passport 4400 units will be dropped. 1. Provision the Passport 4400 for SPVC service according to the procedures given in Step 6 and Step 7 of Chapter 2, Getting Started.
Provisioning a 4400 unit to support frame relay pass-through services The following steps provision the switched permanent virtual circuit (SPVC) between the Passport 4400 and the ILS core router on the Passport switch. Before entering these commands, make sure that steps 1 and 2 of chapter 2, Getting Started, have been followed.
Note: This procedure is similar to the procedure Provisioning ILS Virtual Circuits for IP Routing listed in step 7 of chapter 2, Getting Started. IF your Passport network has already been properly provisioned for IP routing, please skip to the following procedure, Provisioning a Passport 4400 unit to support HTDS services.
The DNA numbers for the User Core Router FRUNI (obtain from Step 2 of Getting Started). IP addresses for LAN and WAN traffic and network management traffic on the Passport 4400. IP address of the Passport protocol port for network management traffic (obtain from Step 2). DLCI numbers for user service traffic on the Passport 4400.
1. Assign and configure IP addresses for the Passport 4400. add ip address entry <IfIndex> <IPAddress> <NetMask> <BcastAddress> : : : : INTEGER (1..255) IPAddress Sub-NetMask IPAddress
7-4
You must execute this command twice in order to assign an IP address for three interface indices: ifIndex 1 (LAN traffic on Port 1), and ifIndex 2 (WAN user service traffic on Port 2). The subnet mask will be either 255.255.255.0 or 255.255.0.0 or 255.0.0.0 depending on the class of the corresponding IP address. When the four variables have been correctly added to the add ip address entry command, the CLI will display a Command Successful message.
define ip base parameters datalinktype 2 fr
This command sets frame relay as the data link type on ifIndex 2.
define ip base parameters routeprotocoltype 1 rip define ip base parameters routeprotocoltype 2 rip
These commands enable RIP on ifIndices 1 and 2 (RIP is disabled by default).

define ip base rip on
Turns RIP on for the Passport 4400 as a whole. Without RIP turned on for the unit, the individual commands to enable RIP on specific ifIndices will not be recognized.
define ip invarp 2 ip enabled
Enables inverse ARP on ifIndex 2.

2. Set up the switched permanent virtual circuit (SPVC) between the Passport 4400 and the Passport switch. add fr port spvclandata <VirtualPortIfIndex> <RemoteNetDLCI> <SVCDNA> <ConnectType> : : : : INTEGER (1..255) INTEGER (16..991) Frame Relay DNA (quoted string)(3..30) slave | master
This command must be executed in order to create an SPVC link to the Passport switch for ifIndex 2. For RemoteNetDLCI, enter the DLCI number assigned to the Passport 4400 for user traffic. For SVCDNA, use the DNA number assigned to the FRUNI on the User Core Router. See chapter 2, Getting Started, for more information. For ConnectType, enter master.
3. Save the current configuration, and reset the Passport 4400. save configuration update reset system current reset
7-5
Provisioning a Passport 4400 unit to support HTDS services The following steps provision the connection between the HDLC device and Port 1 of the Passport 4400.
1. Find the ifIndex of the port that is connected to the HDLC device. show system ifindex configured Ifindex 1 2 3 4 150 151 153 154 155 IfExtType ethernetCsmacd propVirtual other propVirtual propMultiplexor other propMultiplexor v35 frameRelay PPA 0 0 0 1 1 1 2 2 2 Slot limA limA limA limA limA limA limA limA limA
In the above table, Physical Point of Attachment (PPA) and Slot indicate the physical location of each port. For example, PPA 1 and Slot limA refers to Port 1 on the Ethernet Base Module, slot A. Notice that each port may have several associated ifIndices. To select the proper ifIndex, look under the IfExtType column, and find the ifIndex associated with propMultiplexor. Using Port 1 on the Ethernet Base Module, the proper ifIndex would be 150. This is the ifIndex number that will be used in this procedure.
Note: Passport 4400 units equipped with one or more High-speed Data Modules (HDM) are not restricted to the use of Port 1 on the Ethernet Base Module. Additional ports will be listed in the show system ifindex configured table. Identify the desired port on the HDM by looking for the correct PPA and Slot numbers in the table, and select the appropriate ifIndex. 2. Add a frame relay switched permanent virtual circuit (SPVC) between the local and remote 4400. add fr port svcLANData <IfIndex> <DNA> : INTEGER (1..255) : Frame Relay DNA (in quotes) (3..30)
For IfIndex, enter 2, the ifIndex of the virtual WAN port. For the DNA address above, enter the DNA address of the 4400 unit at the remote site, preceded by the optional [x121] prefix (this entire value must be typed inside quotes).
3. Turn LMI off on the primary link (WAN link, Port 2 on the base module). define fr line user dlcmiPVC lmiType <IfIndex> <LMIType> : INTEGER (1..255) : noLMIConfigured | itut933A| ansiT1617D1994
7-6
For IfIndex, enter 155, the frame relay index for Port 2. The LMIType should be set to noLMIConfigured.
4. Define the bridge global IP protocol mode to bridged. (This is the default mode.) define bridge global ipProtocol <IPProtocol> : bridged | routed
Select bridged mode.

5. Write the configuration to nonvolatile RAM. save configuration update 6. Define the wan port protocol as HTDS. define wan port protocolSupport <IfIndex> <ProtocolSupport> : INTEGER (1..255) : none | frameRelayDCE| frameRelayDTE | htds
For IfIndex, enter 150, the ifIndex of Port 1 on the base module. Set the ProtocolSupport to htds.
7. Select the HTDS transfer mode: cut-through, or store and forward. define wan port htdsCutThru <IfIndex> <HTDSCutThrough> : INTEGER (1..255) : yes | no
Once again, we will use IfIndex 150 for Port 1. Select cut-through by setting this variable to yes, or select store and forward by choosing no.
8. Define the wan port mode as DCE. (This will provide the clock for Port 1.) define wan port mode <IfIndex> <Mode> : INTEGER (1..255) : dce | dte
The IfIndex is 150, and the mode should be set to dce.

9. Define the port baud rate. define wan port <IfIndex> <BaudRate> : INTEGER (1..255) : INTEGER (9600..1920000)
The IfIndex is 150. The baud rate will depend upon your HDLC device.
10. Write the configuration to nonvolatile RAM. save configuration update
7-7
Configuring the local Passport 4400 for HTDS

1. Add the local 4400 switch map entry for HTDS. add fr switch map <LocalNetIfIndex> <LocalNetDLCI> <RemoteNetDLCI> <SVCDNA> <ConnectType> <SwitchType> : : : : : : INTEGER (1..255) INTEGER (16..991) INTEGER (16..991) Frame Relay DNA (3..30) slave | master frdce | htds
The LocalNetIfIndex is 150, the same as the ifIndex used in the above procedures. The LocalNetDLCI and RemoteNetDLCI values must be set to 16 for HTDS. SVCDNA is the DNA prefix of the remote 4400, preceded by the optional [x121] prefix, followed by a 3, then the slot number and PPA number of the remote port. (This entire value must be typed inside quotes.) Set the ConnectType to master, and set the SwitchType to htds.
2. Write the configuration to nonvolatile RAM. save configuration update 3. Reset unit to activate changes. reset system current reset
7-8
Optional WAN Port Parameters You may wish to configure other parameters on the HTDS port using the define wan port command. These additional parameters are described below.
baudRate htdsCutThru ifType maxRxFrameSize mode numOfRxBuffers protocolSupport rxQueueSize txQueueSize
baudRate htdsCutThru ifType
The transmission rate of this port in bits per second. The range is 9600 to 1920000. When set to yes, HTDS cut-through is active. Specifies the signaling characteristics of the WAN interface. Options are RS-232, V.35, V.36, X.21, CSU/DSU, T1 CSU, ISDNBRI, and none. The default is V.35. The maximum frame size in bytes that will be received on this interface. The range is from 1 to 8192 bytes. The default value is 4100. The mode (connection type) used on this port: DCE or DTE. This determines whether the Passport 4400 receives or transmits clocking signals. Specifies the number of buffers that will be used for receive data. The range is from 20 to 255. The default is 100. Defines the type of transmission protocol used on this port. The choices are none, frameRelayDTE, frameRelayDCE, or htds. The size in bytes of each receive buffer. The range is from 10 to 255 bytes. The default is 20. The size in bytes of each transmit buffer. The range is from 10 to 255 bytes. The default is 20.
maxRxFrameSize
mode
numOfRxBuffers protocolSupport rxQueueSize txQueueSize
7-9
7-10
ISDN Services
Overview of ISDN Basic Rate Interface (BRI) Service Passport 4400 Circuit Managers ISDN Provisioning Guidelines Provisioning ISDN as the Primary WAN Link Provisioning ISDN as a Backup WAN Link Optional ISDN Provisioning ISDN Monitoring
The Passport 4400 supports the use of ISDN as an alternative to frame relay over a serial WAN link. An ISDN link can be either the primary WAN connection or can be provisioned as a backup link which becomes active only when the primary link fails. The Passport 4400 can also support two physical ISDN connections: one for the primary and one for the backup link. ISDN over leased line is also supported to provide additional connection options. The Passport 4400 can act only as a terminal end point for ISDN services. ISDN services for Passport 4400 units are physically supported by either an ISDN S/T or ISDN U hardware interface module. ISDN Basic Rate Interface (BRI) The Passport 4400 supports the ISDN Basic Rate Interface (BRI). BRI supports two 64 kbps Bearer (B) channels and one 16 kbps Data (D) channel. BRI is also referred to as 2B+D. The Primary Rate Interface (PRI) is not supported by the Passport 4400, although the Passport WAN to which the Passport 4400 unit is connected may require PRI ISDN. For more information about the ISDN requirements for the Passport WAN, see document 241-7001-210, Magellan Passport Access Network Link User Guide. The D-channel can be used to carry setup and user packet data across the network. For the Passport 4400, the D-channel will be reserved for ISDN-related call setup messages and other out-of-band signaling only. No user data is transmitted over the D-channel. Once the link to the WAN is established over the D-channel, user data traffic is carried over the B-channel. For Release 2.0, one 64 kbps B-channel is supported on each ISDN interface module.
8-1
ISDN Services
ISDN Protocols Supported Since different variants of ISDN are available in various international markets, Passport 4400 supports the following ISDN protocols: NET-3 (Euro-ISDN & UK) Vn 2/3 (France) FTZ 1TR6 (or BAPT 223 ZV 6-2 layer 2&3) Germany) INS64 (Japan) CoQ931 (National ISDN-1 Basic Rate, North America) CoQ931 with additions for AT&T 5ESS switch (North America) CoQ931 with additions for Nortel DMS-100 Switch (North America) At the link level, frame relay and Passport 4400 NetLink (VoFR) protocols are supported over the ISDN stream.
Passport 4400 Circuit Managers

To support ISDN as an alternative to frame relay, and to manage both protocols in the same unit, Passport 4400 software uses circuit managers to control the signal flow. A circuit manager activates or deactivates hardware interfaces and initiates the appropriate software. Circuit managers are also used to control the physical link and to generate control messages indicating the state of the link. To control the primary and backup WAN links, Passport 4400 uses a Global Circuit Manager (GCM), a Frame Relay Circuit Manager (FRCM) and an ISDN Circuit Manager (ICM). illustrates the relationship between the various circuit managers in the context of overall Passport 4400 software architecture. Global Circuit Manager (GCM) The GCM administers all logical links between the Passport 4400 and the Passport WAN. The GCM is provisioned as to which link type (ISDN or frame relay) and which physical port on the Base Module will provide the primary and backup links. (For Release 2.0, Port 2 should be provisioned as the primary link and Port 3 as the backup link.) The GCM also monitors the links and determines when to switch from the primary to the backup link if the primary link fails. The GCM does not contain any protocol information or signaling information. To allow for the greatest flexibility, the GCM has been designed to be protocolindependent, with specific information for each protocol (such as dial phone numbers for ISDN) stored in the circuit manager for the protocol. For ISDN, service-specific information is stored in the ICM.
8-2
ISDN Services
ISDN Circuit Manager (ICM) The ICM is the circuit manager responsible for controlling how ISDN links will be established and administered. The ICM stores specific information required to set up ISDN connections, responds to requests from the GCM and, when controlling an active link, passes configuration packets to the D-channel and user data traffic to the B-channel. The following user-defined variables are used by the ICM to set up and manage ISDN traffic: the ICM link table the ICM hardware table. Both these variables must be provisioned before ISDN services can be established. The ICM first receives initialization data when an ISDN card is provisioned for either the primary or backup WAN link. The ICM stores the information in the hardware table. One or more ICM links are then established for the hardware port with the information stored in the ICM link table. When the GCM sends a message to the ICM requesting a link to be activated, the ICM searches for the specified link in the link table, and, if the link cannot be found, an error message is sent to the GCM. If the link entry is found, the ICM activates the hardware port (if no link is currently active on that port). Once the port is activated, the ICM then activates the D-channel and begins to establish a connection to the Passport WAN. Once a connection is established over the D-channel, user data can then be passed over the links B-channel.
ISDN Provisioning Guidelines

Before Passport 4400 units can be provisioned to support ISDN services, the following conditions must exist: the appropriate ISDN hardware interface card or cards must be installed in the Passport 4400 Base Module and the correct cables must be physically connected. Instructions for installing ISDN interface cards are found in document 800-1951-20, Passport 4400 Hardware Installation Manual. the Passport 4400 unit must be provisioned to support MPANL (see Chapter 2, Getting Started, for information) and the appropriate values must be entered for the units Global Circuit Manager (GCM) table. the Passport switch to which you are connecting must be provisioned to support the ISDN variant you are using, and must be configured to support ISDN connections as described in document 241-7001-210, Magellan Passport Access Network Link User Guide All ISDN links, regardless of their intended function, must be provisioned with the appropriate peer numbers before any connection can be established. If you are provisioning ISDN connections over leased lines, the B-channel settings (channel 1, 2 or both) must be entered.
8-3
ISDN Services
The table below lists the tasks required to provision an ISDN connection (either primary or backup) and briefly describes each task.
Table 3-8. ISDN Provisioning Tasks Provisioning task Description
1. Ensure the Passport 4400 unit The ISDN interface cards must be physically installed in the and the Passport WAN are able to appropriate slots in the Base Module and the Passport WAN must support ISDN connections. be configured to support the variant of ISDN you require. 2. Indicate whether the CGM should use default or userdefined settings. If you plan to provision a primary ISDN WAN connection on Port 2, or if the primary link is a frame relay link on Port 2 and ISDN is providing a backup link through Port 3, use the default GCM settings. If any other configure is required, change the GCM settings to user-defined. Enter the variant of ISDN that you are using. Before establishing an ISDN connection, you must update the default peer numbers by entering the originate address and subaddress, and the calling address and sub-address. In leased line connections, the settings for the ISDN B-channel must be entered.
3. Define the ISDN protocol. 4. Enter the appropriate peer numbers. 5. For ISDN over leased line connections, enter the appropriate channel settings.
Provisioning ISDN as the Primary WAN Link

the correct ifIndices for the ISDN service the correct originate address and sub-address a complete list of all calling addresses and sub-addresses for leased line connections, the appropriate settings for the B-channels for leased line connections, be sure to inform your ISDN service provider of your power requirements. After installing the ISDN module in Port 2 of the Passport 4400 Base Module, and before beginning the actual provisioning of ISDN, enter the show system ifindex configured table command at the CLI prompt. This will display the ifIndices for ISDN on Port 2 (PPA 2). A typical IfIndex Table with ISDN installed in Port 2 is shown below.
8-4
ISDN Services
show system ifindex configured table Ifindex 1 2 3 4 5 6 7 8 9 150 151 153 154 155 156 157 158 IfExtType ethernetCsmacd propVirtual other propVirtual isdns ds0 ds0 lapd isdn propMultiplexor other propMultiplexor other frameRelay propMultiplexor other frameRelay PPA 0 0 0 1 2 2 2 2 2 1 1 2 2 2 3 3 3 Slot limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA
The following IfExtension types relate to ISDN: isdns - the physical interface type (S/T) of the ISDN circuit card; isdnu would designate a U-type circuit card. Ds0 - B-channel 1 or B-channel 2 of the ISDN BRI service. Each ISDN B-channel is represented by an ifEntry, even though the Passport 4400 currently supports only one B-channel. lapd - the LAPD interface. Each ISDN D-channel data link layer (LAPD) is represented by an ifEntry. isdn - the signaling D-channel of the ISDN service. propMultiplexor for PPA 2 - the ISDN B-channel protocol driver. frameRelay for PPA 2 - the frameRelay service running within the ISDN B-channel. To provision ISDN as the primary WAN link to the Passport network, complete the following procedures.
1. If you plan to use Port 3 on the Base Module as the primary WAN link (not
recommended), disable the default system settings by entering the following command. If you plan to use Port 2 for the primary WAN link, skip to Step 2.
define GCM global autoActStatus disabled
8-5
ISDN Services
2. Indicate that the values entered for this connection will be used for the primary WAN
link.
add gcm Link <Index> <Name> <SignalingType> <SignalingPCMIndex> <ProtocolType> <ProtocolPCMIndex> : INTEGER (1..255) : "String" (1..16) : unknown | isdn| unusedAlwaysUp : INTEGER (1..65535) : unknown | frameRelay : INTEGER (1..65535)
For <Index>, enter a number to identify the link. <Name> is an optional 1 to 16 character quoted string identifying the link. <SignalingPCMIndex> is a number identifying the signaling PCM. <ProtocolPCMIndex> is a number identifying the protocol PCM port (Port 2 or Port 3).
3. Enter the variant of ISDN to be used for the link. define isdn physicalIf signal protocol <Index> <Protocol> : INTEGER (1..2147483647) : other | dss1 | etsi | dass2 | ess4 | ess5 | dms100 | dms250 | ni1 | ni2 | ni3 | vn2 | vn3 | vn4 | vn6 | kdd | ins64 | ins1500 | itr6 | cornet | ts013 | ts014 | qsig | swissnet2| swissnet3
The <Index> identifies the physical ISDN interface as either primary or backup. Enter 1 for primary; 2 for backup.
8-6
ISDN Services
4. Enter the originate address for the ISDN peer. define isdn dialControl peer originateAddress <Id> <OriginateAddress> : INTEGER (1..2147483647) : "String" (0..131)
<Id> is a number between 1 and 2147483647 identifying the link. <IfIndex> is the IfIndex associated with the link. <OriginateAddress> is the originate address at which the peer will be called. This value must be entered in quotes.
5. Enter the originate subaddress for the ISDN peer. define isdn dialControl peer subAddress <Id> <SubAddress> : INTEGER (1..2147483647) : "String" (0..131)
where: <Id> is a number between 1 and 2147483647 identifying the link. <IfIndex> is the IfIndex associated with the link. <SubAddress> is the originate subaddress at which the peer will be called. This value must be entered in quotes.
6. Enter the ISDN address assigned to the signaling channel. define isdn physicalIf signal callingAddress <Index> <CallingAddress> : INTEGER (1..2147483647) : "String" (0..131)
where: <Index> is a value between 1 and 2147483647 identifying the entry. <CallingAddress> is the signaling channel address. This value must be entered in quotes.
7. Enter any supplementary information for the ISDN address assigned in step 6. define isdn physicalIf signal subAddress <Index> <SubAddress> : INTEGER (1..2147483647) : "String" (0..131)
where: <Index> is a value between 1 and 2147483647 identifying the entry. <SubAddress> is the supplementary ISDN address information. You can enter a character string of up to 131 characters. This value must be entered in quotes.
8-7
ISDN Services
Note: The remaining steps in this procedures apply only to leased line connections. 8. (For leased line connections only) Define how the ISDN B channel will carry traffic. define isdn dialControl peer BChannel <Id> <BChannel> : INTEGER (1..2147483647) : INTEGER (0..32)
<Id> is a number between 1 and 2147483647 identifying the ISDN link. <IfIndex> is the IfIndex associated with the ISDN link. <Bchannel> is a Bchannel number between 0 and 32.
Provisioning ISDN as the Backup WAN Link

To provision the ISDN service as the backup WAN link, you must: Configure or modify the Wan Port Configuration Table Modify the ISDN Dial Control Peer Table. Before you begin, you need to know the ifIndices that pertain to the ISDN hardware and software in Port 3 (PPA 3) of the Base Module. Following is a typical display of the IfIndex Table when the ISDN is a backup link installed in physical Port 3.
show system ifindex configured table Ifindex 1 2 3 4 5 6 7 8 9 150 151 153 154 155 156 157 IfExtType ethernetCsmacd propVirtual other propVirtual isdns ds0 ds0 lapd isdn propMultiplexor other propMultiplexor other frameRelay propMultiplexor other PPA 0 0 0 1 3 3 3 3 3 1 1 2 2 2 3 3 Slot limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA
The following IfExtension types relate to ISDN:
8-8
ISDN Services
isdns - the physical interface type (S/T) of the ISDN circuit card; isdnu would designate a U-type circuit card. Ds0 - B-channel 1 or B-channel 2 of the ISDN BRI service. Each ISDN B-channel is represented by an ifEntry, even though the Passport 4400 currently supports only one B-channel. lapd - the LAPD interface. Each ISDN D-channel data link layer (LAPD) is represented by an ifEntry. isdn - the signaling D-channel of the ISDN service. propMultiplexor for PPA 3 - the ISDN B-channel protocol driver. Modifying the Wan Port Configuration Table To modify the WAN port configuration table for ISDN backup, perform the following steps:
1. Define the interface type for the backup port as ISDN. define wan port ifType <IfIndex> <IfType> : INTEGER (1..255) : none | rs232 | v35 | x21 | v36 | csu-dsu| isdn-BRI | t1csu
For IfIndex, use the number in the IfIndex Table for propMultiplexer, PPA 3, Slot limA. In the example IfIndex Table above, the ifIndex is 156. For IfType, enter isdn-BRI.
2. Define the backup port mode as DTE. define wan port mode 156 dte 3. Define frame relay DTE protocol support for the backup port. CLI>define wan port protocolSupport 156 framerelaydte 4. Optional: Save the configuration changes and reset the Passport 4400. save configuration update reset system current reset
This step can be delayed until the ISDN configuration is complete; however, note the following change that takes place when the backup port configuration changes take effect.
Note: Following reconfiguration of the WAN driver, a new frame relay ifIndex (158) is created in the IfIndex Table. This entry may be used for additional configuration of the backup link.
8-9
ISDN Services
Modifying the ISDN Dial Control Peer Table Modifying an existing Dial Control Peer Table involves adding the destination address (OriginateAddress) and its subaddress. Perform the following steps:
1. Add the ISDN destination telephone number to the Dial Control Peer Table. define isdn dialcontrol peer originateaddress <Id> <IfIndex> <OriginateAddress> : INTEGER (1..2147483647) : INTEGER (1..255) : "String" (0..131)
The Id number identifies an existing row in the ISDN Dial Control Peer Table. This index number is used by the Global Circuit Manager (GCM) as a parameter in the GCM link. All ISDN-related peer information is stored in the ISDN Dial Control Peer Table and managed by the ISDN Circuit Manager (ICM). The GCM passes the index to the ICM only when the connection to the remote peer is to be established. The Id number is determined as follows:
a. If the hardware configuration is:
Port 2 = Serial Port 3 = ISDN, then the Id number for the ISDN in Port3 is 1.
b. If the hardware configuration is:
Port 2 = ISDN Port 3 = ISDN, then the Id number for the ISDN in Port 2 is 2; the Id number for the ISDN in Port 3 is 3. For IfIndex, use the number in the IfIndex Table for isdn (the signaling service), PPA 3, Slot limA. In the example IfIndex Table above, the ifIndex is 9. For OriginateAddress, enter the new destination telephone number inside quotation marks. For a Passport 4400 with a serial interface in Port 2, ISDN in Port 3 and a destination telephone number of 1-800-555-2345, the CLI command would be: define isdn dialcontrol peer originateaddress 1 9 18005552345
2. Add the subaddress of the ISDN destination telephone number to the Dial Control Peer
Table.
define isdn dialControl peer subAddress <Id> <IfIndex> <SubAddress> : INTEGER (1..2147483647) : INTEGER (1..255) : "String" (0..131)
For Id number and If index number, enter the same values as those of the define isdn dialcontrol peer originateaddress command above. For SubAddress, enter the subaddress of the new destination telephone.
8-10
ISDN Services
Adding an Additional ISDN Backup Link

The following procedure is used to add an additional ISDN backup link, or to modify the parameters of an existing ISDN backup link. The addition of a new ISDN backup link is performed in three steps: Add a new ISDN backup entry Create a new ISDN entry in the GCM Link Table Create a new ISDN entry in the GCM Backup Link Table
Note: You cannot add an additional ISDN backup link when the existing ISDN backup link is a leased line.
1. Add a New ISDN Backup Entry

add isdn peer <Id> <IfIndex> <BChannel> <OriginateAddress> <SubAddress> : : : : : INTEGER (1..2147483647) INTEGER (1..255) INTEGER (0..32) "String" (0..131) "String"
For Id, find the highest index number in the ISDN Peer Index Table by entering show isdn physicalif signalTable configured table at the CLI prompt; increment the highest index number by one (if dial-up line). For If Index number, use the number in the IfIndex Table for isdns or isdnu (depending on the physical interface type), PPA 3, Slot limA. In the example IfIndex Table above, the ifIndex is 5. For Bchannel, enter 1 or 2, as appropriate (leased line only). For OriginateAddress and SubAddress ,enter the new destination telephone number and its subaddress, as applicable.
8-11
ISDN Services
2. Create a New ISDN Entry in the GCM Link Table

CLI>add gcm link <Index> <Name> <SignalingType> <SignalingPCMIndex> <ProtocolType> <ProtocolPCMIndex> : : : : : : INTEGER (1..255) "String" (1..16) unknown | isdn| unusedAlwaysUp INTEGER (1..65535) unknown | frameRelay INTEGER (1..65535)
For Index, access the GCM Link Table by entering show gcm link configured table at the CLI prompt. Find the highest index number in the table and increment it by one. For Name, enter any quoted string from 1 to 16 digits. For SignalingType, enter isdn. For SignalingPCMIndex, enter the index of the new ISDN Peer entry created in Step 1. For ProtocolType, enter frameRelay. For ProtocolPCMIndex, enter 3 (the physical port of the backup link). 3. Create a New ISDN Entry in the GCM Backup Link Table
add gcm backup link
<Index>
<UnitIndex> <LinkIndex>
: INTEGER (1..255) : INTEGER (1..3) : INTEGER (1..255)
For Index, access the GCM Backup Table using the show gcm backuplink table command, find the last index entry and, if this is a new backup link, increment the highest number by 1. If you are modifying an existing backup link, copy the index number of the link you wish to modify. For unit index, enter 1 if a serial WAN link is primary, or 2 if the primary link is ISDN. For LinkIndex, enter: the index of the GCM link created in Step 2.
8-12
ISDN Services
Optional ISDN Dial Control Commands

The following commands can be used to change the values of dial control parameters if the default settings are not sufficient for your application. The dial control parameters are described in RFC 2128, Dial Control Management Information Base Using SMIv2.
define isdn dialControl callHistory <maxLength> : INTEGER (0..127)
This parameter defines the number of calls that will be stored in the Call History Table. When the table is full, the oldest entry is deleted when a new entry is created. A value of 0 prevents any calls from being retained. The default number of entries is 5.
define isdn dialControl configuration trapstatus <TrapStatus> : enabled | disabled
When enabled (the default setting), this parameter enables the system to generate SNMP trap messages upon detection of a dial control configuration alarm condition. The following command is used to modify configuration data for a single peer. A destination telephone number must be configured using the originateAddress parameter before any of the peer parameters can become active. The peer parameters are displayed when the following command is entered.
define isdn dialControl peer bChannel callRetries closedUserGroup failureDelay infoType lowerIf originateAddress permission retryDelay speed subAddress trapStatus define isdn dialControl peer bChannel <Id> <IfIndex> <BChannel> : INTEGER (1..2147483647) : INTEGER (1..255) : INTEGER (0..32)
This command applies to leased lines only. For Id and IfIndex, find the number in the ISDN Dial Base Peer table by entering the show isdn dial basePeer Table command.
8-13
ISDN Services
For Bchannel, enter 1 or 2, as applicable. This parameter is used only for leased lines, and is defined by the service provider. Not applicable to dial-up lines. For 128 kbps leased lines, set B-channel to 1.
define isdn dialControl peer callRetries <Id> <IfIndex> <CallRetries> : INTEGER (1..2147483647) : INTEGER (1..255) : INTEGER (0..2147483647)
For Id and IfIndex, find the numbers in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For CallRetries, enter an integer to specify the number of attempts for making a successful connection with the remote end.
define isdn dialControl peer closedUserGroup
This command is currently not used.

CLI>define isdn dialControl peer failureDelay <Id> <IfIndex> <FailureDelay> : INTEGER (1..2147483647) : INTEGER (1..255) : INTEGER (0..2147483647)
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For FailureDelay, enter an integer to specify a time delay in seconds. Following a configured number of unsuccessful call attempts, the system will pause for the specified number of seconds (failure delay) before attempting to call again.
For example, if the number of configured retries is 6, the retry delay is 8, and the failure delay is 15, the system will attempt to call 7 times in succession, with a delay of 8 seconds between calls. Following the 7th attempt, the system will pause for 15 seconds before resuming with the calls. If the failure delay is set to 0, the ICM will inform the GCM after the last unsuccessful call attempt, and the GCM will try to establish another backup link. If the failure delay is set to other than 0, call retries will be continuous, and the GCM will not be notified about the link failure, but will stay on the present link.
8-14
ISDN Services
define isdn dialControl peer infoType <Id> <IfIndex> <InfoType> : INTEGER (1..2147483647) : INTEGER (1..255) : other | speech | unrestrictedDigital | unrestrictedDigital56| restrictedDigital | audio31 | audio7 | video | packetSwitched | fax
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For InfoType, select unrestrictedDigital.
define isdn dialControl peer lowerIf <Id> <LowerIf> : INTEGER (1..2147483647) : INTEGER (0..255)
For Id, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For LowerIf, enter the ifIndex number of the D-channel. To find that number, enter show system ifindex operational, and read the entry next to isdn in the ifIndex table.
define isdn dialControl peer originateAddress <Id> <IfIndex> <OriginateAddress> : INTEGER (1..2147483647) : INTEGER (1..255) : "String" (0..131)
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For OriginateAddress, enter the destination telephone number.
define isdn dialControl peer permission <Id> <IfIndex> <Permission> : INTEGER (1..2147483647) : INTEGER (1..255) : originate | answer | bothOriginateAndAnswer | callback| none
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For Permission, select originate (only outgoing calls are permitted).
8-15
ISDN Services
define isdn dialControl peer retryDelay <Id> <IfIndex> <RetryDelay> : INTEGER (1..2147483647) : INTEGER (1..255) : INTEGER (0..2147483647)
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For RetryDelay, enter an integer (typically 1). This number, in seconds, specifies the delay between call retries when call attempts are unsuccessful.
define isdn dialControl peer speed <Id> <IfIndex> <Speed> : INTEGER (1..2147483647) : INTEGER (1..255) : INTEGER (0..2147483647)
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For Speed, enter either 56000 or 64000 (default) for dial-up lines; enter either 64000 (default) or 128000 for leased lines.
define isdn dialControl peer subAddress <Id> <IfIndex> <SubAddress> : INTEGER (1..2147483647) : INTEGER (1..255) : "String" (0..131)
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For SubAddress, enter the subaddress of the remote telephone number.
define isdn dialControl peer trapStatus <Id> <IfIndex> <TrapStatus> : INTEGER (1..2147483647) : INTEGER (1..255) : enabled | disabled
For Id and IfIndex, find the number in the ISDN Dial Peer Base Configured table. To view the table, enter the show isdn dialcontrol peer base configured table command. For TrapStatus, select enabled or disabled. When enabled, the system will generate SNMP trap messages upon detection of a dial control peer alarm condition.
8-16
ISDN Services
Optional ISDN Physical Interface Commands

The following commands can be used to change the values of the physical interface parameters if the default settings are not sufficient for your application. The commands in this section are applicable to the parameters described in RFC 2127, ISDN Management Information Base.
define isdn physicalif basic lineTopology <IfIndex> <LineTopology> : INTEGER (1..255) : pointToPoint | pointToMultipoint
For IfIndex, find the number by displaying the table using the show isdn
physicalif basicrate configured table command.
For Line Topology, select pointToMultipoint.

define isdn physicalif basic signalMode <IfIndex> <SignalMode> : INTEGER (1..255) : active | inactive
For IfIndex, find the number by displaying the table using the show isdn physicalif basicrate configured table command. For signalMode, select active for dial-up lines, inactive for leased lines.
define isdn physicalif endpoint serviceprofileid <Index> <ServiceProfileID> : INTEGER (1..2147483647) : "String" (0..131)
For Index, find the number by displaying the table using the show isdn physicalif endpoint configured table command. For ServiceProfileID, enter an integer ranging from 0 to 131. This is used only with selected U.S. switch types. Consult your ISDN service provider.
define isdn physicalif endpoint teitype <Index> <TEIType> : INTEGER (1..2147483647) : dynamic | static
For Index, find the number by displaying the table using the show isdn physicalif endpoint configured table command. For TEIType enter dynamic or static, as appropriate. If set to dynamic, the TEI (Terminal Endpoint Identifier) value for BRI interfaces will be assigned by the network. If set to static, you must assign the TEI value yourself.
8-17
ISDN Services
CLI>define isdn physicalif endpoint teivalue <Index> <TEIValue> : INTEGER (1..2147483647) : INTEGER (0..127)
For Index, find the number by displaying the table using the show isdn physicalif endpoint configured table command. The TEIValue depends on the setting of the TEIType setting (see above). If set to dynamic, the TEI value is set to 0 as long as no TEI has been assigned. Otherwise, the TEI value will be set by the network. If set to static, valid TEI values range from 0 to 63, with default set to 0.
define isdn physicalif signal callingaddress <Index> <CallingAddress> : INTEGER (1..2147483647) : "String" (0..131)
For Index, find the number by entering the show isdn physicalif signaltable configured table command. For CallingAddress, enter the local ISDN telephone number.
define isdn physicalif signal infotrapstatus <Index> <InfoTrapStatus> : INTEGER (1..2147483647) : enabled | disabled
For Index, find the number by entering the show isdn physicalif signaltable configured table command. For InfoTrapStatus, set to enabled if you want the system to generate SNMP trap messages upon detection of an ISDN physical signal alarm condition.
define isdn physicalif signal protocol <Index> <Protocol> : INTEGER (1..2147483647) : other | dss1 | etsi | dass2 | ess4 | ess5 | dms100 | dms250 | ni1 | ni2 | ni3 | vn2 | vn3 | vn4 | vn6 | kdd | ins64 | ins1500 | itr6 | cornet | ts013 | ts014 | qsig | swissnet2| swissnet3
8-18
ISDN Services
For Index, find the number by entering the show isdn physicalif signaltable configured table command. For Protocol, select one of the protocols shown in bold above, as applicable to your installation.
define isdn physicalif signal subaddress <Index> <SubAddress> : INTEGER (1..2147483647) : "String" (0..131)
For Index, find the number by entering the show isdn physicalif signaltable configured table command. For SubAddress, enter the subaddress of the local ISDN telephone number.
ISDN Monitoring
The Passport 4400 CLI contains the following three groups of show commands that can be used to display ISDN-related information: System If Index ISDN Dial Control - related to Dial Control MIB RFC 2128 ISDN Physical - related to ISDN MIB RFC 2127. These commands and their related displays are shown in the following sections.
8-19
ISDN Services
System ifIndex Display This command is used to display the ifIndex numbers for all Passport 4400 interfaces, including ISDN-related interfaces. A typical ifIndex table, with ISDN as the backup link, was shown in Provisioning ISDN as the Primary WAN Link earlier in this chapter. Another sample ifIndex table, with ISDN as both the primary and the backup link, is shown below. To obtain the display, enter the following command:
show system ifindex configured Ifindex 1 2 3 4 5 6 7 8 9 150 151 153 154 155 156 157 158 IfExtType ethernetCsmacd propVirtual other propVirtual isdns ds0 ds0 lapd isdn propMultiplexor other propMultiplexor other frameRelay propMultiplexor other frameRelay PPA 0 0 0 1 3 3 3 3 3 1 1 2 2 2 3 3 3 Slot limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA limA
The above table indicates that there is an ISDN card installed in the Primary Port (PPA=2) and the Backup Port (PPA=3), configured for dial-up lines (for leased lines there would be no lapd and isdn entries). Each ISDN basic rate hardware interface is represented by an ifEntry. The propMultiplexor interface type is the ISDN B-channel protocol driver; isdns represents the physical interface type (S/T) of the ISDN circuit card (isdnu would designate a U-type interface); isdn represents the signaling D-channel of the ISDN service; frameRelay designates the frameRelay protocol running within the ISDN; lapd represents the LAPD interface Each ISDN B-channel is represented by an ifEntry; ds0 = B channel 1 or B channel 2 of the ISDN BRI service. PPA = the physical port number within the Ethernet Base Module. Slot = the location of the ISDN card within the Passport 4400 unit; limA indicates that the ISDN card is a logical interface module in Slot A.
8-20
ISDN Services
ISDN Dial Control Displays The following commands display the current states of the parameters provisioned by the define isdn dialcontrol commands.
show isdn dialcontrol basepeer table Id 1 3 IfIndex 5 5 BChannel 1 1
This table shows which B-channel (1 or 2) is used for leased lines. For dial-up lines, this entry is ignored because the B-channel is assigned by the ISDN service.
show isdn dialcontrol callActive table SetupTime Index PeerAddress PeerSubAddress PeerId PeerIfIndex LogicalIfIndex ConnectTime CallState CallOrigin ChargedUnits InfoType TxPackets TxBytes RxPackets RxBytes : : : : : : : : : : : : : : : : 00Years 000Days 00:52:15 1 "384100" "" 2 18 19 00Years 000Days 00:52:15 active originate 0 unrestrictedDigital 72286 5606401 47798 3510473
SetUpTime Index PeerAddress PeerSubAddress PeerId PeerIfIndex LogicalIfIndex ConnectTime CallState
The time when the call was started. A chronological entry of calls started within the same 10 milliseconds of time. The telephone number to which this call is connected. The subaddress of the connected call. The index value of the Peer Table entry to which this call was made. The ifIndex number of the Peer Table entry to which this call was made. The ifIndex number of the B-channel through which this call was made. The time when the call was connected. Indicates whether or not the call is active.
8-21
ISDN Services
CallOrigin ChargedUnits InfoType
For active calls, this field will always indicate originate (for outgoing calls). The number of charged units for this connection. If charging information is not supplied by the switch, this field will be 0. The type of call. Options are speech, unrestrictedDigital, unrestrictedDigital56, restrictedDigital, audio7, audio31, video, packetSwitched, fax, and other. The number of packets transmitted during this call. The number of bytes transmitted during this call. The number of packets received during this call. The number of bytes transmitted during this call.
TxPackets TxBytes RxPackets RxBytes
show isdn dialcontrol callhistory configuration MaxLength RetainTimer : 0 (configured) : 5 (configured) : 0 (configured)
MaxLength RetainTimer
The size of the Call History buffer in number of calls. A value of 0 indicates that no call history is maintained. The minimum length of time, in minutes, that a call history entry will be maintained.
show isdn dialcontrol callhistory statistics table SetupTime: ActiveIndex PeerAddress PeerSubAddress PeerId PeerIfIndex LogicalIfIndex DisconnectCause DisconnectText ConnectTime DisconnectTime CallOrigin ChargedUnits InfoType TxPackets TxBytes RxPackets RxBytes : : : : : : : : : : : : : : : : the time when this call was started 1 "384100" "" 2 18 19 "111" "Protocol Error" 00Years 000Days 00:00:06 00Years 000Days 00:51:25 originate 0 unrestrictedDigital 39052 3028407 25083
8-22
ISDN Services
SetUpTime ActiveIndex PeerAddress PeerSubAddress PeerId PeerIfIndex LogicalIfIndex DisconnectCause
The time when the call was started. A chronological entry of calls started within the same 10 milliseconds of time. The telephone number to which this call is connected. The subaddress of the connected call. The index value of the Peer Table entry to which this call was made. The ifIndex number of the Peer Table entry to which this call was made. The ifIndex number of the B-channel through which this call was made. The encoded network cause value associated with this call. This value will depend on the interface type as well as on the protocol and protocol version being used on this interface. The ASCII text describing the reason for call termination. This field should be used only if a management station is unable to decode the value of dialCtlPeerStatsLastDisconnectCause. The time when the call was connected. The time when the call was disconnected. For active calls, this field will always indicate originate (for outgoing calls). The number of charged units for this connection. If charging information is not supplied by the switch, this field will be 0. The type of call. Options are speech, unrestrictedDigital, unrestrictedDigital56, restrictedDigital, audio7, audio31, video, packetSwitched, fax, and other. The number of packets transmitted during this call. The number of bytes transmitted during this call. The number of packets received during this call. The number of bytes transmitted during this call.
DisconnectText
ConnectTime DisconnectTime CallOrigin ChargedUnits InfoType
TxPackets TxBytes RxPackets RxBytes
8-23
ISDN Services
show isdn dialcontrol configuration AcceptMode TrapStatus : : : : acceptNone (operational) acceptNone (configured) enabled (configured) disabled (configured)
The Passport 4400 ISDN link will not accept incoming calls; therefore, AcceptMode must always be configured for acceptNone. TrapStatus will be configured as enabled or disabled. show isdn dialcontrol peer base configured table
Id IfIndex BChannel LowerIf OriginateAddress SubAddress ClosedUserGroup Speed InfoType Permission CallRetries RetryDelay FailureDelay TrapStatus : : : : : : : : : : : : : : 1 12 1 16 "384100" "" "" 64000 unrestrictedDigital originate 1 1 0 disabled
Id IfIndex BChannel LowerIf OriginateAddress SubAddress ClosedUserGroup Speed InfoType
Identifies a single peer. There may be multiple entries for one peer in order to support multilink as well as backup lines. The ifIndex number of the interface used for calling this peer. Indicates whether B-1 or B-2 is calling this peer. The ifIndex number of the D-channel on which the peer will be called. The telephone number on which the peer will be called. The subaddress of the telephone number on which the peer will be called. Not Applicable at this time. The line speed of the B-channel in bits per second. The information transfer capability to be used when calling this peer. Options are speech, unrestrictedDigital, unrestrictedDigital56, restrictedDigital, audio7, audio31, video, packetSwitched, fax, and other.
8-24
ISDN Services
Permission
Indicates whether or not callback is permitted for charging purposes. Note: The Passport 4400 does not support callback at this time. This field will always indicate originate (for outgoing calls). The number of calls that will be made to a non-responding address. A value of 0 indicates that there is no limit to the number of retries. The time, in seconds, between call retries. The time, in seconds, following a configured number of unsuccessful call attempts, before calling is resumed. A value of 0 indicates that calling will not be resumed. Indicates whether trap generation is enabled or disabled for this peer.
CallRetries
RetryDelay FailureDelay
TrapStatus
show isdn dialcontrol peer statistics table Id IfIndex ConnectTime ChargedUnit SucceededCalls FailedCalls AcceptedCalls RefusedCalls LastDisconnectCause LastDisconnectText LastSetupTime : : : : : : : : : : : 1 12 0 0 0 0 0 0 "0" "none" 00Years 000Days 00:00:00
Id IfIndex ConnectTime ChargedUnit
The index number of the peer. The ifIndex number of the signaling entity. The accumulated time since startup (in seconds) of all calls. The total number of charged units for this peer since startup. If charging information is not supplied by the switch, this field will be 0. The total number of calls completed to this peer. The total number of calls to this peer that have failed. The total number of calls accepted by this peer. The total number of calls refused by this peer. The encoded network cause value associated with this call. This value will depend on the interface type as well as on the protocol and protocol version being used on this interface.
SucceededCalls FailedCalls AcceptedCalls RefusedCalls LastDisconnectCause
8-25
ISDN Services
LastDisconnectText
The ASCII text describing the reason for call termination. This field should be used only if a management station is unable to decode the value of dialCtlPeerStatsLastDisconnectCause. The time in years, days, hours, minutes and seconds since the last call to this peer was started.
LastSetupTime
ISDN Physical Interface Displays The following commands display the current states of the parameters provisioned by the define isdn physicalif commands.
show isdn physicalif basicrate configured table IfIndex 18 12 IfType isdns isdns LineTopology pointToMultipoint pointToMultipoint IfMode te te SignalMode active active
IfIndex: the ifIndex number of the ISDN link. IfType: the physical interface of the ISDN link. It is either isdns (S/T interface) or isdnu (U interface). LineTopology: the network structure of the ISDN link. IfMode: is always te (terminal endpoint). SignalMode: active for dial-up lines; inactive for leased lines.
show isdn physicalif bearer table IfIndex ChannelType CurrentStatus ChannelNumber PeerAddress SubAddress CallOrigin InformationType MultiRate CallSetupTime CallConnectTime ChargedUnits : : : : : : : : : : : : 20 dialup idle 2 "" "" unknown Unknown false 00Years 000Days 00:52:15 00Years 000Days 00:52:16 0
IfIndex ChannelType ChannelStatus ChannelNumber
The ifIndex number of the B-channel. The type of ISDN link: dial-up or leased line. The current state of the B-channel: idle or active. The B-channel for which these table entries apply: B-1 or B-2.
8-26
ISDN Services
PeerAddress SubAddress CallOrigin InformationType
The ISDN address (telephone number) of the current or last call to which this B-channel was connected. The subaddress of the ISDN telephone number of the current or last call to which this B-channel was connected. The origin of the current or last call. If there has been no call on this interface since startup, the value will be unknown. The information transfer capability of the current or last call. Options are speech, unrestrictedDigital, unrestrictedDigital56, restrictedDigital, audio7, audio31, video, packetSwitched, fax, and other. Indicates whether or not the last call used multirate. Note: The Passport 4400 ISDN does not currently support multirate; therefore, this field will always indicate false. The time when call setup began for the current or last call. The time when the connect message was sent for the current or last call. The number of charged units for the current or last call. If charging information is not supplied by the switch, this field will be 0.
MultiRate
CallSetupTime CallConnectTime ChargedUnits
show isdn physicalif endpoint table Index IfIndex IfType TEIType TEIValue ServiceProfileID Status : : : : : : : 2 5 isdn dynamic 128 "2222" active
Index IfIndex IfType TEIType
A number that uniquely identifies an entry in this table. The ifIndex number of the interface associated with this Terminal Endpoint. The interface type for this Terminal Endpoint The type of Terminal Endpoint Identifier (dynamic or static) used for this Terminal Enpoint. If the value is dynamic, the TEI value is selected by the switch. If the value is static, a valid TEI value must be entered using the define isdn physicalif endpoint teivalue command. For Basic Rate interfaces, the default value is dynamic. For TEIType = static, valid values are from 0 to 63 (default = 0); for TEIType = dynamic, the value is assigned by the network, or 0 if not yet assigned.
TEIValue
8-27
ISDN Services
ServiceProfileID
The Service Profile Identifier (SPID) information for this Terminal Endpoint. The SPID contains from 9 to 20 numeric characters. This information is in addition to the local number for some switch protocol types, such as Bellcore NI-1 and NI-2. Indicates whether or not the entries in this table are active.
Status
show isdn physicalif signalstatistics table SignalingIndex IncomingCalls ConnIncomingCalls OutgoingCalls ConnOutgoingCalls ChargedUnits : : : : : : 2 0 0 0 0 0
SignalingIndex IncomingCalls ConnIncomingCalls OutgoingCalls ConnOutgoingCalls ChargedUnits
A number that uniquely identifies an entry in this table. Not applicable: The Passport 4400 does not support incoming calls. Not applicable: The Passport 4400 does not support incoming calls. The total number of outgoing calls attempted on this interface. The total number of connected outgoing calls on this interface. The total number of charged units for this interface. If charging information is not supplied by the switch, this field will be 0.
show isdn physicalif signaltable configured table Index IfIndex Protocol CallingAddress SubAddress BChannelCnt InfoTrapStatus Status : : : : : : : : 2 9 etsi "384000" "30" 2 disabled active
Index IfIndex Protocol
A number that uniquely identifies an entry in this table. The ifIndex number of the interface associated with this signaling channel. The protocol used by the associated ISDN switch.
8-28
ISDN Services
CallingAddress
The ISDN address assigned to this signaling channel. Specifically, the calling address element of the call setup message passed to the switch on outgoing calls. The subaddress of the ISDN address assigned to this signaling channel. The number of B-channels managed by this signaling channel. For BRI, this value is 2. Indicates whether Call Information traps will be generated for calls on this signaling channel. Indicates whether or not the entries in this table are active.
SubAddress BChannelCnt InfoTrapStatus Status
8-29
ISDN Services
8-30
Managing Primary and Backup Links (GCM)

Overview of the Global Circuit Manager (GCM) Default GCM Configurations Provisioning Serial WAN Links Primary and Backup Link Switching and Timing Options
Passport 4400 Global Circuit Manager (GCM)

The GCM manages two physical interfaces and all logical links between the Passport 4400 and the Passport WAN. The GCM is provisioned as to which link type (frame relay over serial line or frame relay over ISDN) and which physical port (Port 2 or Port 3) on the Passport 4400 Base Module will provide the primary and backup links. Typically, the primary link is provisioned as frame relay over serial link and the backup link is provisioned as frame relay over ISDN. See Figure 9-1 for an example of a typical primary and backup link configuration between the Passport 4400 and a Passport network.
Note: For Release 2.0, Port 2 should remain the primary link and Port 3 the backup link.
The GCM then monitors the links and determines when to switch from the primary to the backup link if the primary link fails. In the case of a primary link failure, the switch from primary to backup link is immediate. However, there are two switching types that can be configured for the GCM which determine how the GCM switches from backup to primary link once the primary link recovers from failure. The two switching types are discussed in Primary and Backup Link Switching and Timing Options later in this chapter. The GCM does not store any protocol information or signaling information. To allow for the greatest flexibility in terms of the type of cards that can be installed in the ports and in what combination, the GCM has been designed to be protocolindependent. Specific information for each protocol (such as dial phone numbers for ISDN) stored in the circuit manager for the protocol. For ISDN, service-specific information is stored in the ISDN Circuit Manager (ICM). Specific frame relay
9-1
information is stored in the Frame Relay Circuit Manager (FRCM). The GCM controls all communication between the circuit managers.
PP
Frame Relay
PP
Passport 4400
Port 2
k r y Lin Prima
PP
Serial ISDN
Port 3
Figure 9-1 Typical Passport 4400 Primary and Backup WAN Links
up ck Ba nk Li
ISDN
GCM Default Configurations

There are two default GCM configurations, Unit 1 and Unit 2. The Unit selected depends upon the hardware detected in Port 2 during a coldstart. If Port 2 is configured with a serial WAN card, Unit 1 is used as the default configuration. Unit 2 is the default configuration if Port 2 is configured with an ISDN card. The default configuration sets the parameters for the five MIB tables used by the GCM to set up and manage the Passport 4400 primary and backup WAN links: the GCM Unit table the GCM Link table the GCM Backup Link table the GCM Timer table the GCM Hardware table.
9-2
If Unit 1 is used, the GCM MIB tables have the configuration, depicted in Figure 9-2.
GCM Unit 1
switchType switchDelay Primary Link 1 Backup Remain
GCM Backup Table Index 1 2 Unit 1 1

BackupLink
2 3
GCM Link 1 Signaling Type: Protocol Type: FR, 2
GCM Link 3 Signaling Type: ISDN, 1 Protocol Type: FR, 3
unusedAlwaysUp
unusedAlwaysUp
ISDN Port 2
ISDN Port 3
FR Port 2
FR Port 3
GCM Hardware Table
Figure 9-2 GCM MIB Tables if the Default Configuration is Unit 1
If Unit 2 is used, the GCM MIB tables have the configuration depicted in Figure 9-3.
9-3
GCM Unit 2
switchType switchDelay Primary Link 4 Backup Remain
GCM Backup Table Index 3 4 Unit 1 1

BackupLink
5 6
unusedAlwaysUp
ISDN Port 2
ISDN Port 3
FR Port 2
FR Port 3
GCM Hardware Table
Figure 9-3 GCM MIB tables if the Default Configuration is Unit 2
Provisioning Serial WAN Links

Note: For all steps to provision ISDN WAN links, see ISDN Services on page 8-1 of this manual.
It is recommended that you do not change the designation of Port 2 as the Primary Link. However, depending on the type of connections you require, you can reconfigure the default GCM settings to change the link type. If you want to add a new backup link (i.e., a connection that has not existed before), use the add gcm.. CLI command. If you want to re-configure an existing primary or backup link, use the define gcm.. CLI command. Before You Begin Prior to re-configuring a link or adding a backup link, you should complete the following actions: Verify that any hardware, such as cables, required for the link type you are defining or adding is properly installed on the 4400. For information on 4400 hardware requirements, refer to document 800-1951-20 Passport 4400 Hardware Installation Manual. Familiarize yourself with the current link configurations by using one or more of the following CLI command to display configuration information from the various GCM MIB tables.
9-4
show show shoe show show show
gcm gcm gcm gcm gcm gcm
backupLink table global configuration table hwStatus table link table timer table unit table
Determine whether the WAN Port Configuration table needs to be modified by using the CLI command show wan parameter port configuration table. Check the information shown for the entry corresponding to the port to which you are adding a serial link or for which you are modifying a serial link. For serial links, Port 2 should be identified with the ifIndex number 153, and Port 3 should be identified with the ifIndex number 156. Modifying the WAN Port Configuration Table To modify the WAN port configuration table for a serial link, perform the following steps:
1. Define the signaling for the primary or backup port serial link. define wan port ifType <IfIndex> <IfType> : INTEGER (1..255) : none | rs232 | v35 | x21 | v36 | csu-dsu| isdn-BRI | t1csu |
For IfIndex, use the IfIndex Table number 153 if you are modifying the primary port (PPA 2) or 156 if you are modifying the backup port (PPA 3). For IfType, enter v35 or x21 as appropriate. The default setting for a serial interface module is v35.
2. Define the primary/backup port mode as DTE. define wan port mode 153 dte or define wan port mode 156 dte 3. Define frame relay DTE protocol support for the primary/backup port. define wan port protocolSupport 153 framerelaydte or define wan port protocolSupport 156 framerelaydte
9-5
4. If need be, define the baud rate (default is 64000) for the primary/backup port. define wan port baudrate 153 or define wan port baudrate 156
<BaudRate>
: INTEGER (9600..1920000)
5. Save the configuration changes and reset the Passport 4400. save configuration update reset system current reset
Adding a Primary or Backup Serial Link

1. If need be, modify the WAN Port Configuration table for the type of serial link you are adding. (See Modifying the WAN Port Configuration Table on page 9-5 to complete
this step.)
2. Create a new SL (serial link) entry in the GCM Link table. add gcm link <Index> <Name> <SignalingType> <SignalingPCMIndex> <ProtocolType> <ProtocolPCMIndex> : : : : : : INTEGER (1..255) "String" (1..16) unknown | isdn| unusedAlwaysUp INTEGER (1..65535) unknown | frameRelay INTEGER (1..65535)
For Index, access the GCM Link table by entering show gcm link configured table at the CLI prompt. Find the highest index number in the table and increment it by one. For Name, enter any quoted string from 1 to 16 digits. For SignalingType, enter unusedAlwaysUp. For SignalingPCMIndex, enter 0. For ProtocolType, enter frameRelay. For ProtocolPCMIndex, enter 2 (the physical port of the primary link) or 3 (the physical port of the backup link).
3. If the new link is to be a backup link, skip to Step 4. If the new link is a primary link,
create a new SL (serial link) entry in the GCM Unit table.

add gcm unit <Index> <Name> <backupRemainTime> : INTEGER (1..255) : "String" (1..16) : mins (byte)
9-6
<switchDelay> <switchType> <timerStatus>
: mins (byte) : fastSwitch | voiceSwitch : enabled | disabled
For Index, use the index number obtained in Step 1. For Name, enter any quoted string from 1 to 16 digits. For backupRemainTime, switchDelay, switchType, and timerStatus, see Modifying GCM Switching Delay, Switching Type and Timer Status Settings on page 9-8 for a description of how to set these parameters.
4. If the new link is to be a backup link, create a new SL (serial link) entry in the GCM
Backup Link table.

add gcm backupLink <Index> <UnitIndex> <LinkIndex> : INTEGER (1..255) : INTEGER (1..3) : INTEGER (1..255)
For Index, access the GCM Backup table using the show gcm backuplink table command. Find the last index entry and increment the highest number by one. For UnitIndex, enter 1 if a serial WAN link is primary, or 2 if the primary link is ISDN. For LinkIndex, enter the index of the GCM link created in Step 2. Re-Configuring a Serial Link
1. If need be, modify the WAN Port Configuration table to reflect any changes you are making to the serial link type. (See Modifying the WAN Port Configuration Table
on page 9-5 to complete this step.)

2. Determine the index number for the serial link (SL) you are modifying by accessing the GCM Link Table with the show gcm link configured table CLI command.
Note the index number for the SL you are modifying for use in Step 3.
3. Modify the settings for the SL (serial link) entry that you want to change in the GCM
Link table.
define gcm link Name SignalingType SignalingPCMIndex ProtocolType ProtocolPCMIndex : : : : : "String" (1..16) unknown | isdn| unusedAlwaysUp INTEGER (1..65535) unknown | frameRelay INTEGER (1..65535)
9-7
Name SignalingType SignalingPCMIndex ProtocolType ProtocolPCMIndex
Enter the index number obtained in Step 2 and any quoted string from 1 to 16 digits. Enter the index number obtained in Step 2 and unusedAlwaysUp. Enter the index number obtained in Step 2 and 0. Enter the index number obtained in Step 2 and frameRelay. Enter the index number obtained in Step 2 and either 2 (the physical port of the primary link) or 3 (the physical port of the backup link).
Primary and Backup Link Switching and Timing Options

The GCM determines when the Passport 4400 primary link has failed and immediately switches all traffic to the backup link. When the GCM determines the primary link has recovered from a failure, the length of time before it switches from backup to primary link depends on a number of GCM switching and timing settings. There are two switching types: FastSwitch: The BackupRemainTime is ignored. Voice links are dropped at Switchback. VoiceSwitch: Backup link transmission activity is dropped when either the BackupRemainTimer expires or there is no active voice call. With this setting, there can be overlap in link activity to allow voice transmissions to complete. After the primary link recovers, the GCM delays switching back to the primary link by the amount of time defined in the GCM Unit table switchDelay setting. The switchDelay setting applies to both fast-switch and voice-switch types. Modifying GCM Switching Delay, Switching Type and Timer Status Settings The following CLI commands can be used to modify the GCM unit switching settings and timing status.
define gcm unit backupRemainTime switchDelay switchType timerStatus : : : : mins (byte) mins (byte) fastSwitch | voiceSwitch enabled | disabled
9-8
backupRemainTime
The maximum number of minutes the backup link remains active after switching to the active primary link (i.e., overlap time in link activity). This setting is only used if switchType is set to voiceSwitch. The number of minutes delay, once the primary link is reestablished, before there is deactivation of the backup link and reactivation of the primary link. This determines whether backup-to-primary link switching is set to fast-switch (deactivates the backup link when the primary link is reestablished, regardless of backup link transmission activity) or voice-switch (deactivates the backup link after the primary link is reestablished and either the time set in backupRemainTime has passed or there is no active voice call). Enables or disables the GCM timer settings (see Modifying GCM Timer Settings on page 9-9).
switchDelay
switchType
timerStatus
Modifying GCM Timer Settings The following CLI commands can be used to modify the GCM timer settings.
define gcm timer unitIndex inactPeriodic inactStartHr inactStartMin inactDurationHr inactDurationMin inactMonday inactTuesday inactWednesday inactThursday inactFriday inactSaturday inactSunday : : : : : : : : : : : : : Index Index Index Index Index Index Index Index Index Index Index Index Index (byte), (byte), (byte), (byte), (byte), (byte), (byte), (byte), (byte), (byte), (byte), (byte), (byte), UnitID enabled/disabled (0..23) (0..59) (0..167) (0..59) enabled/disabled enabled/disabled enabled/disabled enabled/disabled enabled/disabled enabled/disabled enabled/disabled
unitIndex inactPeriodic inactStartHr
The index value that uniquely identifies an entry in the GCM Unit table. Enables or disables the functionality of the Periodic Timer inactivity administration. The hour designation to start link inactivity, or disconnection. When the system hour and minutes reach this setting and the inactStartMin setting, the link is automatically disconnected.
9-9
inactStartMin
The minute designation to start link inactivity, or disconnection. When the system hour and minutes reach the inactStartHr setting and this setting, the link is automatically disconnected. The hour designation for the duration of link inactivity, or disconnection. The minutes designation for the duration of link inactivity, or disconnection. Enables or disables the timer inactivity administration for the system day Monday. Enables or disables the timer inactivity administration for the system day Tuesday. Enables or disables the timer inactivity administration for the system day Wednesday. Enables or disables the timer inactivity administration for the system day Thursday. Enables or disables the timer inactivity administration for the system day Friday. Enables or disables the timer inactivity administration for the system day Saturday. Enables or disables the timer inactivity administration for the system day Sunday.
inactDurationHr inactDurationMin inactMonday inactTuesday inactWednesday inactThursday inactFriday inactSaturday inactSundays
9-10
Traffic Management
Overview of Passport 4400 Traffic Management Passport 4400 Traffic Management Parameters Viewing Traffic Management Parameter Settings Defining Traffic Management Parameters
10
The Passport 4400 performs traffic management solely based on the traffic being multiplexed withinnot on traffic on an incoming frame link. Its traffic management is designed to create an environment where small voice frames and large data frames can co-exist in the same box. Passport 4400 traffic management discards data frames when its emission queues are full; it does not base frame discard on whether the DE (Discard Eligibility) bit is set. First, the Passport 4400 sets the TP (Transfer Priority) for each traffic type. The priorities range from 0 to 15, with 15 being the highest priority. The following priorities are the default values for various traffic types when a ConnectID is first established: LAPF and LMI control traffic: TP15 Any voice links: TP11 HTDS traffic: TP6 FRDCE traffic: TP6 NMS traffic: TP6 LAN traffic: TP0
Note: While the default Transfer Priority can be changed, be careful not to starve certain traffic sources by giving a more starvation tolerant traffic type, such as a file transfer on the LAN, priority over one not so immune to delays, such as voice traffic.
Then, based on their TP, the traffic is loaded into the Passport 4400 emission queues. From the emission queues, traffic is allocated to fill the WAN links bandwidth according to its queue number (the WAN link is filled with the upper queues first), and, if traffic managment is enabled, according to certain traffic management parameter settings. For an illustration of how Passport 4400 TP fills emission queues (04) and how WAN link bandwidth is allocated, see Figure 10-1. The Passport 4400 does not currently base its traffic management on FECN (Forward Explicit Congestion Notification) and BECN (Backward Explicit Congestion Notification).
10-1
Transfer Priority
TP15 Reserved for LAPF and LMI traffic.
Ring of Connection Queues
Emission Queues
TP 10-14 Delay sensitive traffic
3 To W A N Link
TP 9
TP 3-8 HTDS, FRDCE, NMS
TP 0-2 LAN traffic
Figure 10-1 Passport 4400 allocation of traffic to WAN link bandwidth
Passport 4400 Traffic Management Parameters

There are three parameters on the Passport 4400 that control traffic management: Rate Enforcement: This parameter controls whether traffic management rules are enforced within the Passport 4400. If enabled, the other traffic management parameters are used to determine the flow of traffic in the Passport 4400. If disabled, the Passport 4400 combines traffic and sends it out without the use of any traffic management rules. Line Efficiency: This parameter determines whether your traffic can exceed your configured CIR (Committed Information Rate) values. If enabled, the passport 4400 allows traffic to transmit above a connections configured CIR value up to a maximum of the its link line speed, but only once all connections with data to transmit have met their CIR. If disabled,
10-2
the Passport 4400 keeps all traffic transmission to the configured CIR values, and excess burst (Be) settings are not applicable. Weighted Round Robin: This parameter controls whether the Passport 4400 uses Weighted Round Robin or Packet Round Robin to schedule the removal of data frames from its internal queueing structure. If enabled, Weighted Round Robin is used to fill the bandwidth by using a CIR formula to determine how much data to pull from one connection before moving on to the next one. If disabled, Packet Round Robin is used to fill the bandwidth based on number of packets, pulling one packet, regardless of size, from each connection in turn until the bandwidth is filled. The difference between these two methods of scheduling becomes important when a link is oversubscribed (i.e., the total committed and excess data rates exceeds the CIR plus the EIR of the DLCI). Since Weighted Round Robin ensures that each connection gets the same percentage of its requested bandwidth, it prevents a situation in which larger packets get a large, unfair percentage of the bandwidth. In addition, the TP and the CIR must be set for each ConnectID. Viewing Traffic Management Parameter Settings You can use the following CLI show commands to view current operational and/ or configured values for Passport 4400 traffic management parameters.
show tm global RateEnforcement : enabled (operational) : enabled (configured) : disabled (operational) : disabled (configured) : disabled (operational) : disabled (configured)
LineEfficiency
WeightedRoundRobin
RateEnforcement LineEfficiency
Rate enforcement must be enabled to allow traffic management. Line efficiency attempts to maximize throughput by filling otherwise unused outbound bandwidth with queued data. If enabled, this will allow bursts to the maximum line speed. Weighted Round Robin measures each traffic class by total number of bytes. If it is disabled, Packet Round Robin (measurement by total number of packets) is used instead.
WeightedRoundRobin
The following are examples of the information displayed when you enter the traffic management show commands. A table of parameters or statistics is displayed for each Connection ID.
10-3
show tm parameters entry show tm parameters table WANPhysicalPortNum FRDlciNum MPANLDlciNum Priority CommittedInfoRate ExcessInfoRate MaxBurstByteSz MaxBurstFrmSz AvgPacketSize MaxPacketSize DeltaTime ConsecutiveFrame : : : : : : : : : : : : 2 16 0 7 64000 0 8000 50 1000 1500 5 10
WANPhysicalPortNum FRDlciNum MPANLDlciNum Priority
The WAN physical port number. The DLCI of the tunneling PVC. The MPANL DLCI identifying the virtual connection. The Transfer Priority (TP) of this class, where class is the MPANL DLCI number, or emission queue, assigned upon creation of a frame relay pass-through service. The Committed Information Rate of this class (in bits/sec). The range is 0 to the maximum bandwidth of the link. The excess bandwidth (in bits/sec) required to accommodate momentary bursts of traffic for this class. The maximum burst allowed for this class (in bytes). The maximum burst allowed for this class (in frames). The average packet size that will be transmitted by this class (in bytes). The maximum packet size that will be transmitted by this class (in bytes). The delta time used for FECN bit management. The tally of frames received with the FECN bit set and cleared are maintained for this amount of time and are used to increase or decrease throughput rate, as per Q.922 Appendix I.(Note: this information is not processed by the Passport 4400, but is passed onto the network.) This variable, computed as per Q.922 Appendix I, section 1.2.2.1.1, holds the number of consecutive frames received with the BECN bit set which causes a transmit rate reduction. Any range may be specified by the LMI user at the time of the DLCI assignment. (Note: this information is not processed by the Passport 4400, but is passed onto the network.)
CommittedInfoRate ExcessInfoRate MaxBurstByteSz MaxBurstFrmSz AvgPacketSize MaxPacketSize DeltaTime
ConsecutiveFrame
10-4
show tm statistics entry show tm statistics table WANPhysicalPortNum FRDlciNum MPANLDlciNum TxTotalBytes TxTotalFrames TxTotalFrags RxTotalBytes RxTotalFrames RxTotalFrags PktsDiscQueFull PktsDiscQueOverflow EmissionQueueFail EmissionQueueFull RxTotalFecnClear RxTotalFecnSet RxTotalBecn : : : : : : : : : : : : : : : : 2 16 0 6544 801 801 1694 801 801 0 0 0 0 0 0 0
WANPhysicalPortNum FRDlciNum MPANLDlciNum TxTotalBytes
The WAN physical port number. The DLCI of the tunneling PVC. The MPANL DLCI identifying the virtual connection. The total number of bytes transmitted by this class, where class is the MPANL DLCI number, or emission queue, assigned upon creation of a frame relay pass-through service. The total number of frames transmitted by this class since this counter was last reset. The total number of fragments transmitted by this class since this counter was last reset. The total number of bytes received by this class since this counter was last reset. The total number of frames received by this class since this counter was last reset. The total number of fragments received by this class since this counter was last reset. The number of packets discarded because the traffic shaping queue was full. The number of packets discarded because of an overflow in the traffic shaping queue. The number of packets discarded because the packet submission to emission queue failed.
TxTotalFrames TxTotalFrags RxTotalBytes RxTotalFrames RxTotalFrags PktsDiscQueFull PktsDiscQueOverflow EmissionQueueFail
10-5
EmissionQueueFull
The number of times an attempt was made to submit a frame to emission queue, but the emission queue was found to be full. The total number of frames received with FECN bit off for this class. The total number of frames received with FECN bit set for this class. The total number of frames received with BECN bit set for this class.
RxTotalFecnClear RxTotalFecnSet RxTotalBecn
show tm status entry show tm status table WANPhysicalPortNum FRDlciNum MPANLDlciNum CurrentInfoRate MinInfoRate AvgTxRate BytesQueued FramesQueued : : : : : : : : 2 16 0 64000 0 0 0 0
WANPhysicalPortNum FRDlciNum MPANLDlciNum CurrentInfoRate
The WAN physical port number. The DLCI of the tunneling PVC. The MPANL DLCI identifying the virtual connection. The current Committed Information Rate (CIR) for this class, where class is the MPANL DLCI number, or emission queue, assigned upon creation of a frame relay pass-through service. The range is 0 to the maximum bandwidth of the link. The minimum value of CIR for this class. The average rate of data transmission (in bytes) on this class. The number of bytes in the transmit queue for this class. The number of frames in the transmit queue for this class.
MinInfoRate AvgTxRate BytesQueued FramesQueued
10-6
Defining Traffic Management Parameters Use the following CLI commands to set the Passport 4400 traffic management parameters:
define tm rateEnforcement enabled
The Rate Enforcement parameter must be set to enabled if you want traffic management to function.
define tm lineEfficiency <enabled/disabled> define tm weightedRoundRobin <enabled/disabled>
The next command is optional. As noted above, you should exercise caution in changing the Transfer Priority (TP). Each frame relay switch map has a unique ConnectID that is assigned by the system when the switch maps are provisioned. You will need to supply the ConnectID in the remaining traffic management commands. To determine all the assigned ConnectIDs, use the following CLI command:
show fr switch map configured table define fr sw svc txPriority ConnectID Transfer Priority : INTEGER (1..65535) : INTEGER (0..15)
This command must be repeated for each ConnectID you want to change.
define fr switch svc TxThroughput ConnectID Throughput : INTEGER (1..65535) : bps (0..2560000)
This is the one CIR value that must be set in order for Passport 4400 traffic management to function properly. Although there are other commands that reference CIR, only the above command affects traffic management. Perform this command to set the CIR for each ConnectID.
Note: Do not set the txThroughput to a value lower than your largest packet size; otherwise, you will experience a traffic deadlock on the associated DLCI. For example, if you set txThroughput to 9600 bps, and the Passport 4400 sees a 1500-byte (12,000 bits) packet in the Ring of Connection Queues, it determines the packet will not fit into the throughput and passes the DLCI, thus locking any information from being sent from that DLCI. Also, do not set the txThroughput to a value greater than the line speed for that connection. Doing so will automatically fail establishment of the link.
After setting traffic management parameters, you must execute the following CLI commands in order to save the changes to the configuration memory and cause them to take effect.
save config update reset system cpu reset
10-7
10-8
Trap Messages
The following tables describe the enterprise traps for the Passport 4400, Release 2.0. These enterprise traps contain information about events and alarms specific to the Passport 4400, detected and captured by the 4400 SNMP agents, and relayed to the network manager. In addition to the enterprise traps described in this appendix, the Passport 4400 also supports the SNMP standard set of generic traps. For a description of generic traps, refer to the RFC 1157 (IETF EFN of SNMP standards). Descriptions of the Passport 4400 enterprise traps are grouped into tables according to type, and then listed alphabetically within each table. The tables list variables which refer to the type of additional surveillance information generated by the associated trap. To see a description of additional information obtained with a traps variable(s), access the appropriate MIB module.
Note: Traps will be generated only if they are enabled by the Passport 4400 network manager.
Trap Type
System Traps (mcmSysxxx) MPANL Traps (mcmMpanlxxx) RSI Traps (mcmAlarmRsixxx) TFTP Traps (mcmTFTPxxx) Bridging Traps (newRoot or topologyChange) Frame Relay Traps (mcmFrxxx) Voice Traps (mcmVNETxxx) T1E1 Traps (mcm4400E1xxxx or mcm4400T1xxx) GCM Traps (mcmGCMxxx) ISDN Traps (dialxxx or isdnxxx)
Table Location
Page A-2 Page A-4 Page A-5 Page A-6 Page A-7 Page A-8 Page A-9 Page A-10 Page A-13 Page A-15
A-1
Trap Messages
System Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 unit.
Table A-1. Passport 4400 System Traps Name
mcmSysBandwidthUtilExceeded
Variable
mcmSysAsciiTimeofDay
Description
Indicates a Passport 4400 has exceeded its configured threshold value for bandwidth utilization. You can change the value by using the command set sys traps bandwidth 1-100. Indicates a Passport 4400 Battery Low condition. The battery supplies power to the Real Time Clock (RTC) for an accumulated power down of 10 years. Indicates a Passport 4400 chassis fan failure. Turn off the unit to prevent over-heating. Consult document 800-1951-20, Passport 4400 Hardware Installation Manual for information about the fan. Indicates a Passport 4400 configuration change that may have affected your applications. Indicates Passport 4400 CPU utilization has exceeded the configured threshold value. You can change the value by using the command set sys traps cpu 1-100. Indicates a power supply failure. The power supply jumper may not be set properly. Consult document 800-1951-20, Passport 4400 Hardware Installation Manual for information about the power supply jumper settings. Indicates Passport 4400 has exceeded its configured threshold value for RAM utilization. You can change the value by using the command set sys traps ram 1-100. Indicates the Passport 4400 Rollback feature is armed. This is a result of a user committing a new code/config bank for the next Passport 4400 reset. If this condition is not desired or needed, revert back to a previous configuration. Indicates the Passport 4400 Rollback feature is disarmed. This is a result of a user disarming a previously committed code/config bank before the next Passport 4400 reset. If this condition is not desired or needed, revert back to a previous configuration.
mcmSysBatteryLow
mcmSysChassisFanFailure
mcmSysConfigChanged
mcmSysCPUUtilExceeded
mcmSysMainPowerSupplyFailure
mcmSysRAMUtilExceeded
mcmSysRollbackArmed
mcmSysRollbackDisarmed
A-2
Trap Messages
Table A-1. Passport 4400 System Traps Name

mcmSysRollbackEnabled
Variable
Description
Indicates the Passport 4400 Rollback feature is enabled. If this feature is not desired, disable it. Indicates the Passport 4400 Rollback feature is being disabled. If this feature is required, enable it. A Passport 4400 system reset has occurred.
mcmSysRollbackDisabled
mcmSysSystemReset
A-3
Trap Messages
MPANL Traps
The traps in the following table are events and alarms pertaining to the Passport 4400 MPANL link.
Table A-2. MPNL Traps Name
mcmMpanlInterfaceLinkDown
Variable
mcmSysAsciiTimeofDay mcmMSMDTELLinkCfgIfIndex
Description
This trap is generated from the MPANL signaling module. It triggers once the MSM link goes down. Please check the Passport configuration. This trap is generated from the MPANL signaling module. It triggers once the MSM link goes up. The MSM link is now up. There is a Normal MSM Link establishment. This trap is generated from the MPANL signaling module. It will trigger if a DNA address is missing, i.e. has not been configured, for the module. Provision (configure) the DNA address of the Passport 4400. This trap will be generated from the MPANL signaling module. It will trigger once the profile is received from the Passport. This is a Normal condition.
mcmMpanlInterfaceLinkUp
mcmSysAsciiTimeofDay mcmMSMDTELLinkCfgIfIndex
mcmMpanlPrefixDNA hasNotBeenConfigured
mcmMSMProfileReceivedFrom- mcmSysAsciiTimeofDay mcmMSMDTELLinkCfgIfIndex Passport mcmMSMDTELinkStatsRemoteCompname
A-4
Trap Messages
RSI Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 RSI unit.
Table A-3. RSI Traps Name
mcmAlarmRsiFailedToLocateRSA
Variable
Description
This unit is unable to communicate with the RSI server; the server could not be reached. This could indicate a problem with the IP network, or that the server is temporarily out of service. Or, the 4400 might not be provisioned for the servers IP address. Try doing a ping to the server to determine its reachability over the IP network, and check the availability of the RSI server on the Passport. This unit is currently unable to communicate with a previously available server. This unit will periodically attempt to re-establish communication with the server. The problem could be with the IP network, or the server might be temporarily out of service. The unit cannot currently be used for address resolution. Try doing a ping to the server to help determine its leachability over the IP network. This unit is now able to communicate with a server with which it had lost communication. The unit can now be used for address resolution.
mcmAlarmRsiRSAIsDown
mcmAlarmRsiRSAIsUp
A-5
Trap Messages
TFTP Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 TFTP file transfer.
Table A-4. TFTP Traps Name
mcmTFTPDownloadFail
Variable
mcmSysAsciiTimeofDay mcmTFTPServerIpAddr mcmTFTPFileName mcmSysAsciiTimeofDay mcmTFTPServerIpAddr mcmTFTPFileName mcmSysAsciiTimeofDay mcmTFTPServerIpAddr mcmTFTPFileName
Description
A TFTP code download has failed between the Passport 4400 and the server. Check the network cables, and, providing the server is alive, retry the download. The TFTP code upload is not supported by the Passport 4400. A TFTP code download has succeeded between the Passport 4400 and the server. This is a Normal Status indicator.
mcmTFTPUploadFail
mcmTFTPDownloadSuccess
A-6
Trap Messages
Bridging Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 Bridging application.
Table A-5. Bridging Traps Name Variable Description
newRoot
Indicates the sending agent has become the new root of the Spanning Tree. This trap is sent by a bridge soon after its election as the new root. A topologyChange trap is sent by a bridge when any of its configured ports transition states. Sequences are from the Blocking state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a newRoot trap is sent for the same transition.
topologyChange
A-7
Trap Messages
Frame Relay Traps

The traps in the following table are events and alarms pertaining to the Passport 4400 Frame Relay service.
Table A-6. Frame Relay Traps Name
frDLCIStatusChange
Variable
frCircuitIfIndex frCircuitDlci frCircuitState mcmSysAsciiTimeofDay
Description
Indicates the specified Virtual Circuit has changed state. It has been created or invalidated, or has been toggled between the inactive and active states. This occurs when a PVC changes state and this trap is enabled (through frTrapState). Indicates the PVC LMI link is down. Check the cabling and MPANL link status, including the Passport MPANL status for that particular link. Indicates the PVC LMI link is up. This is a Normal Status indicator. Indicates WAN link is down. This is due to a loss of physical connection or is because the LMI is dropped. Check the physical connection, the MPANL LMI status, and provisioning on the Passport. Indicates the WAN link is up. This is a Normal Status indicator.
mcmFrPvcLmiLinkDown
mcmFrPvcLmiLinkUp mcmFrWanLinkDown
mcmSysAsciiTimeofDay mcmSysAsciiTimeofDay
mcmFrWanLinkUp
A-8
Trap Messages
VNET (Voice 2.0) Traps

The traps in the following table are events and alarms pertaining to a Passport 4400 Voice application.
Table A-7. VNET Traps Name
mcmVNETDownload Fail
Variable
mcmSysAsciiTimeofDay mcmVNETChCfgLimID mcmVNETChConfigChannelID mcmSysAsciiTimeofDay mcmVNETChCfgLimID mcmVNETChConfigChannelID mcmSysAsciiTimeofDay mcmVNETChCfgLimID mcmVNETChConfigChannelID mcmSysAsciiTimeofDay mcmSysAsciiTimeofDay
Description
Indicates a failure occurred while downloading the voice image. Retry the voice image download. Indicates the DSP is running, but is unable to sync up. A channel reset may be required. Reset the channel(s). Indicates recovery from the failure to sync up condition. Synchronization is acquired. This is a Normal Status indicator. Indicates the Passport 4400 built image does not contain CVM code. Indicates the Passport 4400 built image does not contain DVM code. Indicates the Passport 4400 built image does not contain TUVM code. Indicates the DSP is not running. A channel reset may be required. Reset the voice channel(s). Indicates recovery from the out of order condition. The DSP is running. This is a Normal Status indicator.
mcmVNETFailedToSyncUp
mcmVNETFailedToSyncUpRecovered mcmVNETNoCVMCodeImage mcmVNETNoDVMCodeImage
mcmVNETNoTUVMCodeImage mcmSysAsciiTimeofDay mcmVNETOutOfOrder mcmSysAsciiTimeofDay mcmVNETChCfgLimID mcmVNETChConfigChannelID mcmSysAsciiTimeofDay mcmVNETChCfgLimID mcmVNETChConfigChannelID
mcmVNETOutOfOrderRecovered
A-9
Trap Messages
T1/E1 Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 T1/E1 module.
Table A-8. T1/E1 Traps Name
mcm4400E1OOCMFAlarmClear
Variable
mcmSysAsciiTimeofDay mcm4400t1e1LineStatusLineIndex mcmSysAsciiTimeofDay mcm4400t1e1LineStatusLineIndex
Description
Indicates an E1 OOCMF Alarm has cleared. This is a Normal Status indicator. Indicates an E1 OOCMF Alarm is present. Framing error due to signal loss. Run the loopback tests, if possible, to determine the cause of the problem. Indicates an E1 OOSMF Alarm has cleared. This is a Normal Status indicator. Indicates an E1 OOSMF Alarm is present. This is caused by a framing error due to signal loss. Run the loopback tests, if possible, to determine the cause of the problem. Indicates an E1 AIS Alarm has cleared. This is a Normal Status indicator. Indicates an E1 AIS Alarm condition is present. Check physical link of the local E1 and the remote PBX. may be due to a framing error. Indicates a failure occurred during the E1 code download. Check the physicalconnection, and verify that the download is set up correctly and that the software is available on the server. Retry the download. Indicates the E1 is unable to sync up. It could indicate a protocol error. Check the physical connection, both local and remote, and attempt to run the loopback tests to determine the cause of the problem. Indicates recovery from the E1 failure to sync up condition. This is a Normal Status indicator. Indicates the built image does not contain E1 code. Load a new image that includes E1 code. Indicates the E1 is not responding. The management frame is out of order. Check for a framing error.
mcm4400E1OOCMFAlarmSet
mcm4400E1OOSMFAlarmClear
mcm4400E1OOSMFAlarmSet
mcm4400E1AISAlarmClear mcm4400E1AISAlarmSet
mcm4400E1DownloadFail
mcm4400E1FailToSyncUp
mcm4400E1FailToSyncUpRecover
mcm4400E1NoCodeImage
mcm4400E1OutOfOrder
A-10
Trap Messages

mcm4400E1OutOfOrderRecovered
Variable
Description
Indicates recovery from the E1 out of order condition. E1 is responding. This is a Normal Status indicator. Indicates an E1 red Alarm condition has cleared. This is a Normal Status indicator. Indicates an E1 Red Alarm condition is present. Check the physical connection to the remote. Indicates an E1 Remote A Bit Alarm has cleared. This is a Normal Status indicator. Indicates an E1 Remote A Bit Alarm is present. This may be due to a framing error. Run the loopback tests, if possible, to determine the cause of the problem. Indicates an E1 Remote Y Bit Alarm has cleared. This is a Normal Status indicator. Indicates an E1 Remote Y Bit Alarm is present. Run the loopback tests, if possible, to determine the cause of the problem. Indicates E1 TS16 AIS Alarm has cleared. This is a Normal Status indicator. Indicates an E1 TS16 AIS Alarm is present. The TX or RX side for the physical connection may be faulty. This may be due to a framing error. Run the Loopback tests, if possible, and determine the casue of the problem. Indicates a T1 AIS Alarm has cleared. This is a Normal Status indicator. Indicates a T1 AIS Alarm condition is present. Check the physical link of the local T1 and the remote PBX. This may be due to a framing error. Indicates a failure occurred during the T1 code download. Check the physical connections, and verify that the download is set up correctly and the software is available on the server. Retry the download.
mcm4400E1RedAlarmClear
mcmSysAsciiTimeofDay mcm4400t1e1LineStatusLineIndex
mcm4400E1RedAlarmSet
mcm4400E1RemoteABitAlarmClear
mcm4400E1RemoteABitAlarmSet
mcm4400E1RemoteYBitAlarmClear
mcm4400E1RemoteYBitAlarmSet
mcm4400E1TS16AISAlarmClear
mcm4400E1TS16AISAlarmSet
mcm4400T1AISAlarmClear mcm4400T1AISAlarmSet
mcm4400T1DownloadFail
A-11
Trap Messages

mcm4400T1FailToSyncUp
Variable
Description
Indicates the T1 is unable to sync up. Check the physical connection, both local and remote. Indicates recovery from the T1 failure to sync up condition. This is a Normal Status indicator. Indicates the built image does not contain T1 code. Load a new image that includes T1 code. Indicates the T1 is not responding. The management frame is out of order. Check for a framing error. Indicates recovery from the T1 out of order condition. T1 is responding. This is a Normal Status indicator. Indicates a T1 red Alarm condition has cleared. This is a Normal Status indicator. Indicates a T1 Red Alarm condition is present. Check the physical connection to the remote. Indicates a T1 Yellow Alarm condition has cleared. This is a Normal Status indicator. Indicates a T1 Yellow Alarm condition is present. The TX or RX side for the physical connection might be faulty. Possible framing error with the remote device. Run Loopback tests, if possible, to determine the cause of the problem.
mcm4400T1FailToSyncUpRecover
mcm4400T1NoCodeImage
mcm4400T1OutOfOrder
mcm4400T1OutOfOrderRecovered
mcm4400T1RedAlarmClear
mcm4400T1RedAlarmSet
mcm4400T1YellowAlarmClear
mcm4400T1YellowAlarmSet
A-12
Trap Messages
GCM Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 GCM logical link administrator.
Table A-9. GCM Traps Name
mcmGCMBakLinkDownCaused ByPhysicalConnection
Variable
mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex
Description
Indicates a GCM link state change from UP to DOWN. The GCM link is configured as the backup link. The disconnection is caused by loss of the physical connection. Check for a cabling problem, a possible signalling problem with the ISDN D-channel, or a Frame Relay protocol error. Indicates a GCM link state change from UP to DOWN. The GCM link is configured as backup link. The disconnection is caused by a GCM timer event. The GCM timer event (user activated) caused the link to go down. Wait until the timer kicks in. if it stays down, contact the appropriate field personnel. Indicates a GCM link state change from UP to DOWN. The GCM Link is configured as the backup link. The disconnections is caused by a loss of the physical connection. Check for a Frame Relay protocol error.
mcmGCMBakLinkDownCausedByGcmTimerEvent
mcmGCMBakLinkDownCausedByProtocolFailure
mcmGCMBakLinkDownCausedByUnknownSource
Indicates a GCM link state change from UP to DOWN. The GCM link is configured as the backup link. The disconnection is caused by the loss of an unknown event.
mcmGCMBaklinkEst
The connection between the 4400 and the Passport is established. The connection is built on both a physical and protocol level. Voice and LAN transfer is disabled for the backup link. This is the normal physical and protocol level connection, but the server is unreachable. Check the server connection. Indicates the connection is established, and Voice and LAN transfer is now activated on the backup link. This is a Normal Status indicator.
mcmGCMBakLinkUp
A-13
Trap Messages
Table A-9. GCM Traps Name

mcmGCMPriLinkDownCauseByPhysicalConnection
Variable
mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex
Description
Indicates a GCM link has changed its state from UP to DOWN. The GCM link is configured as primary link. The disconnection is caused by the loss of the primary links physical connection. Check for a cabling problem, a possible signaling problem with the ISDN D-channel, or a Frame Relay protocol error. If the problem persists, contact the appropriate system administrator or field personnel. Indicates a GCM link has changed its state from UP to DOWN. The GCM link is configured as the primary link. The disconnection is caused by a GCM timer event (user activated). Wait until the timer kicks in.
mcmGCMPriLinkDownCausedByGCMTimerEvent
mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex mcmSysAsciiTimeofDay mcmGCMLinkIndex mcmGCMLinkName mcmGCMLinkSigType mcmGCMLinkSigPcmIndex mcmGCMLinkProtoType mcmGCMLinkProtoPCMIndex
mcmGCMPriLinkDownCausedByProtocolFailure
Indicates a GCM link has changed its state from UP to DOWN. The GCM Link is configured as the primary link. The disconnection is caused by the loss of the protocol connection. This indicates a possible frame relay or ISDN D Channel signaling protocol error. Indicates a GCM link has changed its state from UP to DOWN. The GCM link is configured as the primary link. The disconnection is cause by the loss of an unknown event.
mcmGCMPriLinkDownCausedByUnknownSource
mcmGCMPriLinkEst
The connection between the 4400 and the Passport is established. The connection is built on both a physical and protocol level. Voice and LAN transfer is disabled for the primary link. This the normal physical and protocol level connection. Indicates the connection is established, and Voice and LAN transfer is now activated for the primary link. This is a Normal Status indicator.
mcmGCMPriLinkUp
A-14
Trap Messages
ISDN Traps
The traps in the following table are events and alarms pertaining to a Passport 4400 ISDN connection.
Table A-10. ISDN Traps Name

dialCtlPeerCallInformation
Variable
callHistoryPeerId callHistoryPeerIfIndex callHistoryLogicalIfIndex ifoperStatus callhistoryPeerAddress callhistoryPeerSubAddress callHistoryDisconnectCause callHistoryConnectTime CallHistoryDisconnectTime callHistoryInfoType callHistoryCallOrigin mcmSysAsciiTimeofDay callActivePeerId callActivePeerIfindex callActiveLogicalIfIndex ifoperStatus callActivePeerAddress callActivePeerSubAddress callActiveInfoType callActiveCallOrigin mcmSysAsciiTimeofDay
Description
This trap information is sent to the manager whenever a successful call clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, this information is sent after all retry attempts have filed. Only one such trap is sent in-between successful call attempts, and subsequent call attempts do not result in a trap. The ifOperStatus variable returns the operational status of the virtual interface associated with the peer to whom this call was made. This trap information is sent to the manager whenever a call setup message is received or sent. The variable ifOperStatus returns the operational status of the virtual interface associated with the peer to whom the call this call was made.
dialCtlPeerCallSetup
A-15
Trap Messages
Table A-10. ISDN Traps Name

isdnmibCallinformation
Variable
IfIndex isdnBearerOperStatus isdnBearerPeerAddress isdnBearerPeerSubAddress isdnBearerCallSetupTime isdnBearerInfoType isdnBearerCallOrigin mcmSysAsciiTimeofDay
Description
This trap information is sent to the manager under the following conditions:
Incoming calls rejected for policy reasons (e.g., unknown neighbor, or access violation). Outgoing calls determined to have ultimately failed, and, if retry is active, all retry attempts have failed. Calls that connect, in which case the variable isdnBearerCallConnectTime should be included in the trap.
Only one such trap is sent in-between successful or unsuccessful call attempts to or from a single neighbor. If the Dial Control MIB objects dialCtlNbrCfgId and dialCtlNbrrCfgIndex are known by the entity generating this trap, both objects should be included in the trap. The receipt of this trap with no dial neighbor information indicates that the manager must poll the callHistoryTable of the Dial Control MIB to see what changed.
A-16
Index A
Acronym definition table xii adding 9-6 Adding a 4400 to a Passport network 2-1 Agencies FCC ii ARP definition xii Authentication traps enabling 3-14 Circuit managers FRCM 9-1 GCM 9-1 ICM 9-1 CLI access via TELNET 4-11 architecture 2-11 definition xii LAN services provisioning 5-4 setting port parameters 3-7 structure 2-12 using 2-12 Committed Information Rate (CIR) defining 10 -7 Community strings changing passwords 3-6 indexes 3-3 passwords and privileges 3-3 Configuring (see also Provisioning) 4400 for HTDS 7-8 core router functionality 2-3 FRDTE on the NMCR 2-4, 2-6 FRDTE on the UCR 2-4, 2-8 FRUNI on the NMCR 2-4, 2-5 FRUNI on the UCR 2-4, 2-7 MPANL service 2-2 UCR for IPX routing 2-9 virtual router on the UCR 2-8 Connectivity management and branch 4400s 1-6 Core router functionality configuration 2-1, 2-3 CUG definition xii Customer community strings 3-3 Customer ID 2-14 Cut-through HTDS transfer mode 7-2
Index-1
B
Backup link switching and timing options 9-8 Bandwidth allocation 10 -2 emission queues 10 -1 Benefits of 4400 networks 1-2 BRI definition xii ISDN 8-1 Bridge filters activating 5-5 entering 5-6 provisioning 5-5 Bridging optional parameters 5-7 provisioning 5-4
C
CE Conformance ii Channel number 3-25 CIR definition xii Circuit manager ISDN support 8-2
CVM definition xii
D
DCE definition xii mode 1-6 Default passwords 3-3 DLCI definition xii value 2-14 DNA definition xii numbering 2-14 numbering plan 6-18 overriding the numbering plan 6-19 DNAPrefix example 2-15 DSP definition xii DTE definition xii mode 1-6 DTE/DCE maximum frame size 2-14 DTE/DCE receiver bandwidth 2-14
E
Easyrouter 6-45 Emission queues for bandwidth allocation 10 -1 Ethernet interface 2-9
F
Factory defaults loading configuration values 2-2, 2-13 FP definition xii FRAD definition xii Frame relay Defining multiple switch maps 6-13 defining optional line parameters 6-19 defining optional PVC & SVC parameters 6-15 defining optional system parameters 6-18 overriding the numbering plan 6-19 defining optional virtual port parameters 6-24 monitoring
Index-2
line user characteristics 6-38 MPANL parameters and statistics 6-43 virtual port parameters 6-45 WAN statistics 6-34 connection status and performance 6-25 switch PVC performance 6-30 switch SVC performance 6-28 viewing line network characteristics 6-35 line user characteristics 6-38 MPANL parameters and statistics 6-43 switch maps 6-26 switch SVC parameters 6-27 system parameters 6-25 WAN parameters 6-32 Frame relay pass-through functions 6-2 HDLC 7-1 LMI 6-4 MPANL SPVC feature 6-3 A-bit signaling 6-3 provisioning 6-4 provisioning 4400 support 7-4 provisioning procedure 6-5 optional WAN parameters 6-8 FRCM 9-2 definition xii relation to GCM and ICM 9-2 FRDTE configuring on the NMCR 2-4, 2-6 configuring on the UCR 2-4, 2-8 FRNNI definition xii FRS definition xii FRUNI configuring on the NMCR 2-4, 2-5 configuring on the UCR 2-4, 2-7 definition xii Function Processor (FP) 1-6
G
GCM 1-7, 9-1 default configuration 9-2 definition xii MIB tables 9-2
overview 9-1 protocol independence 9-1 relation to ICM and FRCM 9-2 Global Circuit Manager default configuration 9-2 MIB tables 9-2 overview 1-7 overview 9-1 protocol independence 9-1 relation to ICM and FRCM 9-2
H
HDLC definition xii frame relay pass-through 7-1 tunneled over frame relay 7-1 HTDS configuring a 4400 for 7-8 cut-through transfer mode 7-2 definition xii optional WAN port parameters 7-9 pass-through provisioning guidelines 7-3 provisioning procedures 7-3 store and forward transfer mode 7-2 transfer modes 7-2
provisioning 5-8 RIP 5-9 routing 2-20 optional parameters 5-10 provisioning 5-8 IPX definition xii routing 2-23 optional parameters 5-12 provisioning 5-12 routing through the UCR 2-9 ISDN adding an additional backup link 8-11 adding an ISDN entry to the GCM Backup table 8-12 adding an ISDN entry to the GCM Link table 8-12 BRI 8-1 circuit manager 8-3 definition xii Global Circuit Manager (GCM) 8-2 modifying the dial control peer table 8-10 protocols supported by the 4400 8-2 provisioning guidelines 8-3
L
LAN bridging 5-1 definition xii features 5-1 IP routing 5-2 IPX routing 5-3 provisioning 5-3 LAPD definition xii LDM definition xii Line Efficiency 10 -2 defining 10 -7 Line parameters frame relay 6-19 LMI definition xii Loading factory default configuration values 2-2,
I
ICM 9-2 definition xii relation to GCM and FRCM 9-2 Identifying the 4400 3-2 IE definition xii ifIndex assignment 3-20 definition xii overview 1-8 ILS core router functionality 1-6 definition xii Installing the 4400 unit 2-2, 2-11 Interworking 1-2 IP definition xii filtering forwardr 5-9
2-13
Logical links 1-7
Index-3
M
MAC definition xii Management and branch 4400 connectivity key elements 1-6 Management layer 1-6 Management subnet 2-10 Memory banks active and inactive settings 3-8 committing 3-8 managing 3-8 setting status 3-8 viewing status 3-10 MIB community string assignments 3-4 definition xii user privilege assignment table 3-5 MMTC definition xii modifying 9-5 Monitoring frame relay 6-25 line user characteristics 6-38 MPANL parameters & statistics 6-43 switch PVC performance 6-30 switch SVC performance 6-28 virtual port parameters 6-45 WAN statistics 6-34 network link parameters 3-29 system parameters 3-16 MPA definition xii MPANL configuration 2-1, 2-2 connection 1-7 definition xii extensions DLCI-0 1-3 DLCI-16 1-3 protocol 1-3, 1-7 MPANL and SPVC connectivity diagram 1-4 MPANL and SPVCs 1-4 MSM definition xii
N
NAC definition xiii Network layers 1-5 Network layers diagram 1-5 Network link parameters monitoring 3-29 Network management components 1-6 core router 1-6 Network management workstation connecting 2-1, 2-9 NMCR definition xiii NMS definition xiii Node name 2-14 NSP definition xiii
O
Optional WAN Port Parameters 6-8 Overview 4400 network benefits 1-2 4400 services 1-1 GCM
9-1
Global Circuit Manager 9-1 Global Circuit Manager (GCM) 1-7 ifIndex 1-8 ILS core router functionality 1-6 interface indices 1-8 interworking 1-2 management layer 1-6 MPANL and SPVCs 1-4 MPANL protocol 1-3 network layers 1-5 physical layer 1-6 system architecture 1-7 traffic management 10 -1 traffic management
10 -1
user service layers 1-7 virtual ports 1-8
Index-4
P
PAD definition xiii Passport switch model numbers 1-1 Passwords changing community strings 3-6 PBX definition xiii Physical connection options 1-6 Physical layer 1-6 Physical Point of Attachment 1-8 Ping utility 4-18 PORS definition xiii Port taking offline 3-15 PPA 1-8, 3-20 definition xiii, 3-23 PRI definition xiii Primary and backup physical links 1-7 Primary link switching and timing options 9-8 Primary logical link 1-6 Provisioning 4400 for frame relay pass-through 7-4 4400 ILS virtual circuits 2-2, 2-20 4400 node and MPANL link parameters 2-2,
optional parameters for frame relay 6-15
R
Rate Enforcement 10 -2 defining 10 -7 relation to GCM and FRCM 9-2 relation to GCM and ICM 9-2 Reset command 2-13 Resetting the system 4-12 RFC definition xiii RIP definition xiii IP filtering 5-9
S
Sample Passport 4400 network 1-9 Serial links 9-6 provisioning 9-4 re-configuriong 9-7 Services of the 4400 1-1 Set command system administration 3-2 Set system command 3-1 Show command system administration 3-2 system communitystring table 3-3 SIMM definition xiii SNMP definition xiii Software upgrade to Release 2.0 4-10 SPVC definition xiii SPX definition xiii Store and forward HTDS transfer mode 7-2 SVC definition xiii optional parameters for frame relay 6-15 Switch maps for frame relay 6-13 Switching options backup link 9-8 primary link 9-8 System architecture components 1-7
Index-5
2-14
bridge filtering 5-5 bridging 5-4 frame relay pass-through 6-4 HTDS 7-3 ILS virtual circuits for IP Routing 2-20 ILS virtual circuits for IPX routing 2-23 IP filtering 5-8 IP routing 5-8 IPX routing 5-12 ISDN 8-3 ISDN as primary WAN link 9-3 serial links 9-4 user subnets and services 2-2, 2-27 verification 2-25 PVC definition xiii
overview 1-7 System clock setting 3-13 System memory banks managing 3-8 System parameters monitoring 3-16 System reset 4-12 cold start 4-12 CPU 4-12 warm start 4-12 System rollback confirming 3-12 disabling 3-12 enabling 3-11 using 3-11 System traps setting 3-14
defining 10 -7 Transfer Priority (TP) 10 -1 default values 10 -1 defining 10 -7 Transport layers and services 1-8 Traps definitions A-1 enabling 3-13 setting 3-13 TUVM definition xiii
U
UCR configuring for IPX routing 2-9 definition xiii UNI definition xiii Upgrading to Release 2.0 4-10 User privileges assigning 3-2 categories 3-2 User service layers 1-7
T
TELNET providing connectivity 2-9 utility 4-11 TFTP default download procedure 4-4 definition xiii preliminary download provisioning 4-2 providing server 2-9 server setup 2-10 software download 4-1 specific download procedure 4-6 Timing options backup link 9-8 primary link 9-8 Traffic management 10 -1 Committed Information Rate (CIR) defining 10 -7 emission queues 10 -1 overview 10 -1 parameters 10 -2 defining settings 10 -7 Line Efficiency 10 -2 Rate Enforcement 10 -2 viewing settings 10 -3 Weighted Round Robin 10 -3 Transfer Priority (TP) 10 -1
V
Verifying 4400 provisioning 2-25 Viewing frame relay line network characteristics 6-35 line user characteristics 6-38 MPANL parameters & statistics6-43 switch maps 6-26 switch SVC parameters 6-27 system parameters 6-25 WAN parameters 6-32 Virtual port parameters frame relay 6-24 Virtual ports 1-8 subnet traffic 1-8 VPM definition xiii VPN community strings 3-3 definition xiii
Index-6
W
WAN definition xiii WAN Port Configuration Table 9-5 WAN port parameters for HTDS 7-9 WAN serial links 9-6 adding 9-6 provisioning 9-4 re-configuring 9-7 Weighted Round Robin 10 -3 defining 10 -7
Index-7
Index-8
Passport 4400
Operators Manual
Address comments to: Senior Manager, Technical Publications Northern Telcom MICOM Communications Corp. 4100 Los Angeles Ave. Simi Valley, CA 93063-3397 U.S.A 1-805-583-8600 1998 Northern Telecom All rights reserved Information subject to change without notice
Publication: 800-1952-20 Date: June 1998 Printed in Canada

Ops Manual

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ops Manual

Încărcat de

Drepturi de autor:

Formate disponibile

Passport 4400

Part Number 800-1952-20, Rev. A

Frame Relay Services 6

HDLC Transparent Data Services 7

Managing Primary and Backup Links (GCM) 9

About This Manual

How This Manual is Organized

Passport 4400 Operators Manual

About This Manual

About This Manual

Passport 4400 Operators Manual

Passport 4400 Operators Manual

About This Manual

Acronyms Used in This Manual

About This Manual

Passport 4400 Operators Manual

Passport 4400 Operators Manual

About This Manual

Passport 4400 Operators Manual

Benefits of Passport 4400 Networks

Passport 4400 Interworking

Passport 4400 Operators Manual

Passport 4400 Operators Manual

SPVC Virtual Port

Calling DLCI: 16 Called DLCI: X

Local DLCI: X Remote DLCI: 16

Figure 1-1. MPANL and SPVC Connectivity

Passport 4400 Operators Manual

Passport 4400 Network Layers

IP Layer Router Layers, Management, Voice

Frame Relay User Service Layer

Figure 1-2. Passport 4400 Network Layers

Passport 4400 Operators Manual

Passport 4400 Operators Manual

Passport 4400 System Architecture

Passport 4400 Operators Manual

Passport 4400 Operators Manual

Sample Passport 4400 Network

Dedicated link to service provider; dedicated link to core router/NMS site

Passport 4400 Operators Manual

Public Telephone Network

X.25 Passport 4400

= Third-party Router = IP LAN with attached stations

Figure 1-3. Typical Passport 4400 Connections

Adding a Passport 4400 to a Passport Network

Passport 4400 Operators Manual

Step 1: Configure the MPANL Service on the Passport Switch

Passport 4400 Operators Manual

Step 2: Configure Core Router Functionality on the Passport Switch

Passport 4400 Operators Manual

Bridge Router Port 1

SPVC VP DNA DLCI

VR V.35 Port Port 2

MPANL Network Link

Figure 2-1. ILS Core Router Functionality

Passport 4400 Operators Manual

(2=lp number; 99=user-selected number for ILS)

(Deletes the framer component; a virtual framer is used instead.)

(Assigns the FRUNI to the logical processor that supports ILS.)

(Passport DNA prefix=3021811397; 299=unique number for ILS FRUNI)

(Passport switch is always the Slave; Passport 4400 is the Master.)

Passport 4400 Operators Manual

(2=lp number; 99=user-selected number for ILS)