1. Manuals
  2. Brands
  3. Fore Systems Manuals
  4. Switch
  5. forerunner series
  6. Configuration manual

Fore Systems forerunner series Configuration Manual

Atm switch
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
™
ForeRunner
ATM Switch
fs
Network Configuration Manual
MANU0148-04 - Rev. A - 5/14/98
Software Version 5.2.x
FORE Systems, Inc.
1000 FORE Drive
Warrendale, PA 15086-7502
Phone: 724-742-4444
FAX: 724-742-7742
http://www.fore.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the forerunner series and is the answer not in the manual?

Questions and answers

Related Manuals for Fore Systems forerunner series

Summary of Contents for Fore Systems forerunner series

  • Page 1 ™ ForeRunner ATM Switch Network Configuration Manual MANU0148-04 - Rev. A - 5/14/98 Software Version 5.2.x FORE Systems, Inc. 1000 FORE Drive Warrendale, PA 15086-7502 Phone: 724-742-4444 FAX: 724-742-7742 http://www.fore.com...

  • Page 2: Legal Notices

    This publication is provided by FORE Systems, Inc. “as-is” without warranty of any kind, either express or implied, includ- ing, but not limited to, the implied warranties or conditions of merchantability or fitness for a particular purpose. FORE Systems, Inc.
  • Page 3 VCCI CLASS 1 NOTICE This equipment is in the Class 1 category (Information Technology Equipment to be used in commercial and/or industrial areas) and conforms to the standards set by the Voluntary Control Council For Interference by Information Technology Equipment aimed at preventing radio interference in commercial and/or industrial areas.Consequently, when used in a residential area or in an adjacent area thereto, radio interference may be caused to radios and TV receivers, etc.
  • Page 4 The E1 (NM-6/E1C, NM-2/E1C, NM-8/E1D, and NM-4/E1D) and E3 (NM-4/E3C, NM-2/E3C, NM-4/E3D, and NM-2/ E3D) network modules that are described in this manual are approved for use in FORE Systems’ host systems providing that the instructions below are strictly observed. Failure to follow these instructions invalidates the approval.

  • Page 5: Safety Certifications

    Required User Guide Statements - UK Installation The network modules are designed for use only with FORE Systems ATM Switches. Use of the network modules in any product not listed in this manual may result in a hazard and will invalidate the regulatory approval. The network modules must be installed in accordance with the installation instructions provided.

  • Page 7: Table Of Contents

    Placement of a FORE Systems Product ........
  • Page 8 Table of Contents Traffic Types........... . . 1 - 35 Traffic Policing (Usage Parameter Control) .
  • Page 9 Table of Contents 3.3.2 Registration and Address Resolution ......3 - 7 3.3.3 Data Transfer ..........3 - 8 Distributed LAN Emulation .
  • Page 10 Table of Contents Upgrading an ELAN without Using DLE ....... 3 - 54 3.8.1 Deleting the Non Co-located Services .
  • Page 11 Table of Contents 5.1.4.1 Hierarchical Addressing....... 5 - 3 5.1.4.1.1 Switch Prefix.
  • Page 12 Table of Contents CHAPTER 7 Signalling VCI Allocation Range ..........7 - 1 7.1.1 Determining the VCI Allocation Range with ILMI Down .
  • Page 13 Table of Contents 8.1.2 AMI Command Privileges........8 - 9 8.1.2.1 Admin Privileges .
  • Page 14 Table of Contents APPENDIX B Configuring Circuit Emulation Services Configuring CES Connections........B - 2 B.1.1 Creating a New CES Connection .
  • Page 15 Table of Contents D.2.2.3 Configuring the CLP0EPD Threshold ....D - 7 D.2.2.4 Configuring the CLP1PPD Threshold ....D - 8 Profiles .

  • Page 16: Forerunner Atm Switch Network Configuration Manual

    Table of Contents ForeRunner ATM Switch Network Configuration Manual TOC - 10...

  • Page 17: List Of Figures

    List of Figures CHAPTER 1 Configuring PVCs Figure 1.1 The Cell ..........1 - 2 Figure 1.2 Virtual Channels in a Virtual Path.

  • Page 18: Forerunner Atm Switch Network Configuration Manual

    List of Figures Figure 3.6 Distributed LAN Emulation Model ..... . . 3 - 12 Figure 3.7 IP ARP Broadcast from LEC 1 to LEC 9 ....3 - 13 Figure 3.8 Re-distributing the Broadcast across DLE Peer Servers .
  • Page 19 List of Figures APPENDIX C Converting from FT-PNNI to PNNI Figure C.1 Invalid Configuration of ASX-1000 Split between Two FT-PNNI Peer Groups........C - 2 Figure C.2 Invalid Configuration of ASX-1000 Split between Two PNNI Peer Groups .

  • Page 20: Forerunner Atm Switch Network Configuration Manual

    List of Figures ForeRunner ATM Switch Network Configuration Manual LOF - 4...

  • Page 21: List Of Tables

    List of Tables CHAPTER 1 Configuring PVCs Table 1.1 Summary of Traffic Contract Variables and Policing Actions . . . 1 - 37 CHAPTER 3 Configuring an Emulated LAN Table 3.1 LECS Configuration File Parameters ..... 3 - 25 CHAPTER 7 Signalling Table 7.1...

  • Page 22: Forerunner Atm Switch Network Configuration Manual

    List of Tables ForeRunner ATM Switch Network Configuration Manual LOT - 2...

  • Page 23: Preface

    This document also provides general ATM information and general product information. This document was created for users with various levels of experience. If you have any questions or problems, please contact FORE Systems’ Technical Support. Chapter Summaries Chapter 1 - Configuring PVCs - Describes how to create PVCs on a switch through the ATM Management Interface (AMI).

  • Page 24: Technical Support

    Preface Technical Support In the U.S.A., customers can reach FORE Systems’ Technical Assistance Center (TAC) using any one of the following methods: Select the “Support” link from FORE’s World Wide Web page: http://www.fore.com/ Send questions, via e-mail, to: support@fore.com Telephone questions to “support” at: 800-671-FORE (3673) or 724-742-6999 FAX questions to “support”...

  • Page 25: Typographical Styles

    Preface Typographical Styles Throughout this manual, all specific commands meant to be entered by the user appear on a separate line in bold typeface. In addition, use of the Enter or Return key is represented as <ENTER>. The following example demonstrates this convention: cd /usr <ENTER>...

  • Page 26: Important Information Indicators

    To call your attention to safety and otherwise important information that must be reviewed to ensure correct and complete installation, as well as to avoid damage to the FORE Systems product or to your system, FORE Systems utilizes the following WARNING/CAUTION/NOTE indicators.

  • Page 27: Laser Radiation Notice

    Preface Laser Radiation Notice Class 1 Laser Product: This product conforms to applicable requirements of 21 CFR 1040 at the date of manufacture. Class 1 lasers are defined as products which do not permit human access to laser radiation in excess of the accessible limits of Class 1 for applicable wavelengths and durations.

  • Page 28: Safety Precautions

    Modifications to Equipment Do not make mechanical or electrical modifications to the equipment. FORE Systems, Inc., is not responsible for regulatory compliance of a modified FORE product. Placement of a FORE Systems Product...

  • Page 29: Power Cord Connection

    WARNING! with single-phase power systems having a grounded neutral conductor. To reduce the risk of electrical shock, do not plug FORE Systems products into any other type of power system. Contact your facilities manager or a qualified electrician if you are not sure what type of power is supplied to your building.
  • Page 30 Preface viii ForeRunner ATM Switch Network Configuration Manual...

  • Page 31: Configuring Pvcs

    CHAPTER 1 Configuring PVCs To establish a permanent communication link between two sites, it is necessary to establish permanent virtual circuits (PVCs) at each switch along the communications path. This chapter discusses the creation of PVCs through the ATM Management Interface (AMI), a command- line user interface to ForeRunner ATM switches.
  • Page 32 Configuring PVCs VPI: 1, VCI: 37 cell ForeRunner ATM ForeRunner ATM Switch C Switch B port B4 port D1 port B1 port C1 port A1 VPI: 2, VCI: 33 port A4 cell cell VPI: 1, VCI: 35 ForeRunner ATM ForeRunner ATM Switch A Switch D cell VPI: 0, VCI: 32...

  • Page 33: Virtual Paths

    Configuring PVCs 1.2 Virtual Paths Virtual paths, which are carried within a physical transit medium (e.g., DS1, E1, DS3, E3, OC3c, or OC12c link), are used to establish connections between two nodes in an ATM net- work. Many virtual paths can be transmitted within a single physical link. Two types of vir- tual paths exist: virtual path connections (VPCs), also known as through paths, and originating/terminating paths, also known as virtual path terminators (VPTs).

  • Page 34: Through Paths

    Configuring PVCs The VCI value of cells does not change as the cell is switched through the ATM network via a virtual path. Each virtual path must originate at a switch fabric, pass through zero or more switch fabrics and terminate at another switch fabric. The origination and termination points are referred to as originating and terminating paths.
  • Page 35 Configuring PVCs switch fabric cell cell VPI: 10 VPI: 20 VCI: X VCI: X Through Path A4|10 -> B4|20 Figure 1.5 - An Example of a Through Path By definition, through paths only switch cells in one direction; they are unidirectional. For example, switch fabric X is configured with the through path B1|20 ->...

  • Page 36: Originating And Terminating Paths

    Configuring PVCs 1.2.2 Originating and Terminating Paths As previously noted, originating and terminating paths (also called virtual path terminators) are points at which a virtual path originates and terminates. For example, if a virtual path exists from switch fabric A to switch fabric B, then there must be an originating path on switch fabric A and a terminating path on switch fabric B.

  • Page 37: Listing Virtual Paths

    Configuring PVCs 1.3 Listing Virtual Paths 1.3.1 Listing Through Paths By logging in to AMI (see Chapter 1 of the ATM Management Interface (AMI) Manual for infor- mation about logging into AMI), it is possible to display either all of the existing through paths on an individual switch fabric or all of the existing through paths on a specified port.
  • Page 38 Configuring PVCs To list advanced options about all of the existing virtual (through) paths, enter the following parameters: configuration vpc show advanced Input Output Port Port Shape ConType tran-tran-pmp tran-tran-pp The fields in the advanced display are defined as follows: Field Description Input Port...

  • Page 39: Listing Originating And Terminating Paths

    Configuring PVCs 1.3.2 Listing Originating and Terminating Paths By logging in to AMI, it is possible to display either all of the existing originating and termi- nating paths on an individual switch fabric or on a specified port. To list all of the originating and terminating paths on an individual switch fabric, enter the following parameters: configuration vpt show Input...
  • Page 40 Configuring PVCs To list all of the advanced options about all of the existing virtual path terminators, enter the following parameters: configuration vpt show advanced Input Output Port Port Shape VBROB BuffOB terminate terminate terminate terminate terminate 1CTL terminate originate port port originate...

  • Page 41: Virtual Channels

    Configuring PVCs 1.4 Virtual Channels Virtual channels “ride” inside of virtual paths. The combination of the two specifies a virtual connection. On a switch fabric, each virtual channel switches cells with a specific VPI and VCI received on a specific port to another port with a new VPI and a new VCI. Unlike through paths, which carry one or more VCCs, virtual channels describe a single virtual connection between two endpoints.
  • Page 42 Configuring PVCs switch fabric cell cell VPI: 1 VPI: 9 VCI: 20 VCI: 25 Virtual Channel C2|1|20 -> D2|9|25 Figure 1.9 - Example of a Virtual Channel In order to establish two-way communications between two ports on a switch fabric, two vir- tual channels are necessary because virtual channels are unidirectional.
  • Page 43 Configuring PVCs Switch or ForeRunner Host B ATM Switch Switch or Term. Orig. Host C C3|3|45 -> A3|9|100 Switch or C3|3|50 -> C2|3|98 Switch or Host A C3|3|80 -> A1|7|88 Host D C3|3|123 -> A1|3|123 Switch or Host E Figure 1.11 - Virtual Channels Created on Terminating Path C3|3 Similarly, before the virtual channels shown in Figure 1.12 can be created, the originating path C2|2 must exist.

  • Page 44: Smart Permanent Virtual Circuits

    Configuring PVCs 1.4.1 Smart Permanent Virtual Circuits Smart Permanent Virtual Circuits (SPVCs) are connections that go across multiple switch fab- rics. An SPVC looks like a PVC at the local and remote endpoints with an SVC (Switched Vir- tual Circuit) in the middle. SVCs are channels established on demand by network signalling. Similar to a dialed telephone call, SVCs transport information between two locations and last only for the duration of the transfer.

  • Page 45: Listing Virtual Channels

    Configuring PVCs 1.4.2 Listing Virtual Channels By logging in to AMI, you can display either all of the existing virtual channels on an individ- ual switch fabric or on a specified port. To list all of the virtual channels on an individual switch fabric, enter the following parameters: configuration vcc show Input...
  • Page 46 Configuring PVCs To list advanced information about all of the existing permanent virtual channels on a switch board, enter the following parameters: configuration vcc show advanced Input Output Port Port Protocol ConType 3CTL 3CTL spans 3CTL spans 3CTL tran-tran-pp 3CTL 3CTL spans 3CTL...

  • Page 47: Creating Pvcs And Spvcs

    Configuring PVCs 1.5 Creating PVCs and SPVCs FORE’s ATM network modules provide ATM transmission connectivity, while its intelligent network modules, such as the Circuit Emulation Services (CES) network module, provide adaptation for ports carrying one transmission format (e.g., TDM) to ATM cells. This section describes how to create the following from one ATM port to another: •...

  • Page 48: Creating A Through Path

    Configuring PVCs 1.5.1 Creating a Through Path To create a new through path, log in to AMI and enter the following parameters: conf vpc new <iport> <ivpi> <oport> <ovpi> [-upc <index> ] [-name <name> ] The optional parameters for call records and VP shaping (using Series C network modules) are as follows: [-inctype (orig | tran | term) -outctype (orig | tran | term) [pmp |mpp | mpmp]]\-shapeivpi <vpi>...
  • Page 49 Configuring PVCs Parameter Description -shapeivpi <vpi> The incoming VPI for this through path. When the traffic shaping port is not the port con- nected to the WAN, a through path must be created from the WAN port to the traffic shap- ing port.
  • Page 50 Configuring PVCs In the first line in the first pair, notice that the output port is 2E4. This is the intra-fabric port. The 2 means the connection is coming out of the switch board in slot 2 through the intra-fabric port.

  • Page 51: Creating An Originating Or Terminating Path

    Configuring PVCs 1.5.2 Creating an Originating or Terminating Path To create an originating or terminating path (virtual path terminator), log in to AMI and enter the following parameters: configuration vpt new <port> <vpi> (term | orig) [-reserved <Kbs>]\ [-minvci <vci> ] [-maxvci <vci> ] The -reserved, -minvci, and -maxvci parameters are optional for creating originating or terminating paths.
  • Page 52 Configuring PVCs Parameter Description shapeovpi The output path on a traffic shaping originating vpt. Setting this value configures traffic shaping on the originating path. Cells bound for the network leave the traffic shaping port with this VPI. When the traffic shaping port is the WAN port, this value equals the input VPI of the originating path.
  • Page 53 Configuring PVCs The following is an example of how to create a terminating path: myswitch::configuration vpt> new 3b3 99 term Would you like to create the originating side also [y]? y The following is an example of how to create a originating path: myswitch::configuration vpt>...

  • Page 54: Shaping Multiple Originating Paths On A Single Port

    Configuring PVCs 1.5.2.1 Shaping Multiple Originating Paths on a Single Port This feature allows you to shape several originating paths to be output on a single port. This feature is useful if you have several remote sites interconnected by a PVP mesh. If you only need to shape one originating path, you can simply use the conf port traffic d ratelimit command on a Series D network module.
  • Page 55 Configuring PVCs Switch B Switch A VP 3 WAN PVP Mesh shaping port VP 2 VP 0 VP 0 Switch C VP 1 VP 1 looping port (orig. and term. paths VP 0 and VP 1) Figure 1.15 - PVPs Coming in Port 1A1 from WAN and Looped through Port 1A2 Then, as shown in the example in Figure 1.15, the traffic that is coming in through path 2 on port 1A1 from the WAN gets looped back to terminating path 0 on on port 1A2.
  • Page 56 Configuring PVCs To configure the shaped originating paths as shown in the example in Figure 1.14 and Figure 1.15, perform the following steps: First, create the UPC contract to be used on the through paths that are going to be output on the shaping port on the Series D network module to the WAN.

  • Page 57: Terminating A Pvc At A Switch

    Configuring PVCs Create a PVP in the opposite direction and use -loopvpi to ensure that the cells on each through path get looped back the terminating paths on the looping port (1a2). myswitch::configuration vpc> new 1a1 2 1a2 2 -loopvpi 0 myswitch::configuration vpc>...

  • Page 58: Creating Atm Arp Entries

    Configuring PVCs 1.5.2.3 Creating ATM ARP Entries To create a FORE IP PVC ARP entry, log in to AMI. Data on this PVC is encapsulated using null encapsulation (also known as VC-based multiplexing) as specified in RFC-1483. Enter the following parameters: configuration atmarp newforeip <host>...

  • Page 59: Listing Atm Arp Entries

    Configuring PVCs 1.5.2.4 Listing ATM ARP Entries To verify that the ARP entries exist correctly for the outgoing PVC connection from the SCP to the host, display the ATM ARP cache by logging in to AMI and entering the following param- eters: configuration atmarp show IPaddress...

  • Page 60: Creating A Virtual Channel

    Configuring PVCs 1.5.3 Creating a Virtual Channel To create a new virtual channel, log in to AMI and enter the following parameters: configuration vcc new <iport> <ivpi> <ivci> <oport> <ovpi> <ovci> [-upc <index> ] [-name <name> ] The advanced options for call records are as follows: -inctype (orig | tran | term) -outctype (orig | tran | term) [pmp | mpp | mpmp]] These parameters are defined as follows:...
  • Page 61 Configuring PVCs Parameter Description mpmp Indicates this is a multipoint-to-multipoint channel. By indicating pmp, mpp, or mpmp, you are only assigning a label for record keeping purposes. The switch does not neces- sarily create the type of channel you have specified. If you assign a connection type, but do not assign a pmp, mpp, or mpmp label, the switch assigns a label of pp (point-to-point).

  • Page 62: Creating A Spans Spvc

    Configuring PVCs 1.5.4 Creating a SPANS SPVC To create a SPANS SPVC, you must configure both ends of the connection concurrently on the two switch fabrics. This means you must have an AMI session open on both the local switch fabric and the destination switch fabric.

  • Page 63: Displaying Spans Spvc Information

    Configuring PVCs To create a SPANS SPVC, you need to configure the two ends concurrently on the two switch fabrics. Therefore, you first need to open an AMI session to the destination switch fabric by using the SCP’s IP address, along with the SNMP read-write community string. The following example depicts how to create a bidirectional SPVC from the local switch fabric (myswitch) to a remote switch fabric (198.29.22.46 named fishtank).
  • Page 64 Configuring PVCs Field Description Local BW The amount of peak bandwidth allocated for this SPANS SPVC, specified in Kbps. Remote ID The unique number that the remote switch fabric’s SCP assigned to this SPANS SPVC when it was created. Remote Port The port number on the remote switch fabric.

  • Page 65: Traffic Types

    Configuring PVCs 1.6 Traffic Types following sections contain informal definitions of the concepts presented. For a NOTE detailed understanding of these issues, please see the ATM Forum’s UNI 3.1 and TM 4.0 Specifications. Quality of Service (QOS) Management is based on the bandwidth parameters associated with a virtual connection and the class of service and ATM Adaptation Layer (AAL) used for that connection.

  • Page 66: Traffic Policing (Usage Parameter Control)

    “tagged” or “dropped,” depending on what is defined in the contract. This ensures that the connections with reserved bandwidth are not exceeding their reservations. FORE Systems’ switches use a combination of “leaky bucket,” or Generic Cell Rate Algorithm (GCRA) hard- ware in the switch fabric and user-configurable parameters in AMI to perform these policing functions.

  • Page 67: Non-Conforming Cells: Tagging Vs. Dropping

    Configuring PVCs 1.7.2 Non-conforming Cells: Tagging vs. Dropping Second, it is important to understand the concept of tagging and dropping. Each ATM cell has a Cell Loss Priority (CLP) bit which indicates if the network can drop it under congested con- ditions.
  • Page 68 Configuring PVCs The specific combinations of these parameters that make up the ATM Forum contracts are defined as follows: cbr <pcr01> cbr0 <pcr0> <pcr01> [tag] vbr <pcr01> <scr01> <mbs01> vbr0 <pcr01> <scr0> <mbs0> [tag] abr <pcr01> <mcr> The cbr <pcr01> contract is for CBR traffic. It only uses the first leaky bucket to assess the conformance to PCR of the aggregate of the CLP=0 cells and the CLP=1 cells.

  • Page 69: Ami Upc Commands

    Configuring PVCs 1.7.4 AMI UPC Commands AMI allows you to create a UPC contract using these combinations of traffic parameters. To create a UPC contract in AMI, enter the following parameters: configuration upc new <index> ubr [aal5 [noPktDisc]] [ubrTagging] [AltCLP] [-name <name> ] configuration upc new <index>...
  • Page 70 Configuring PVCs Parameter Description mbs0 Indicates the maximum burst size for cells with CLP = 0. mbs01 Indicates the maximum burst size for all cells. tag means that non-conforming CLP = 0 cells are tagged. Otherwise, they are dropped. The default is that they are dropped. This option only applies to the PCR0 parameter of the CBR0 contract and to the SCR0 and MBS0 parameters of the VBR0 contract.
  • Page 71 Configuring PVCs Parameter Description -scheduling (roundrobin | Indicates the scheduling mode to be used for servicing traffic on the output side of a Series smoothed | guaranteed) D network module. roundrobin means that all service for these connections comes from one of the round-robin queues in the network module.
  • Page 72 Configuring PVCs The following is an example of how to create a UPC contract: myswitch::configuration upc> new 5 vbr0 500 200 250 -cdvt 1000 aal5 PPPol -name vbr0_upc This example specifies a contract named “vbr0_upc”, which is a VBR0 contract with an index of 5, a pcr01 of 500 cells/sec (or kbps), an scr0 of 200 cells/sec (or kbps), an mbs0 of 250 cells (or kilobits), a CDVT of 1,000 microseconds, and partial packet policing enabled.

  • Page 73: Configuring Classical Ip

    CHAPTER 2 Configuring Classical IP 2.1 Introduction This chapter describes how to design, configure, and maintain a Classical IP ATM network. The term classical indicates that the ATM network has the same properties as existing legacy LANs. That is, even though ATM technology allows for large, globally connected networks, for example, it is only used in the LAN environment as a direct replacement of existing LAN technology.

  • Page 74: Logical Ip Subnets

    Configuring Classical IP 2.1.1 Logical IP Subnets An important concept in Classical IP networks is that of a Logical IP Subnet (LIS). An LIS is a group of hosts configured as members of the same IP subnet (that is, they have the same IP network and subnetwork numbers).

  • Page 75: Spans Interface

    Configuring Classical IP 2.1.3 SPANS Interface While each of the Classical IP interfaces for a given physical interface is designed to support Classical IP using Q.2931 signalling, a SPANS interface also exists for each physical interface. The SPANS interface is asx0 in switch software and is fa0 in host adapter software. The SPANS interface supports FORE IP on top of SPANS signalling.

  • Page 76: Address Registration And Ilmi

    Configuring Classical IP 2.2 Address Registration and ILMI Before a host can establish connections over a physical interface, the host must know the NSAP address for that interface. The primary purpose of Interim Local Management Interface (ILMI) is to discover and register these NSAP addresses dynamically. 2.2.1 NSAP Addresses For private ATM networks, addresses uniquely identify ATM endpoints.

  • Page 77: Operating With Ilmi Support

    2.2.2 Operating with ILMI Support FORE Systems switches running ForeThought software provide support for ILMI. If ILMI is supported on all of the switches and hosts in a given network, when a switch boots up, ILMI enables the switch to discover all of the hosts attached to it and to send its ATM prefix associ- ated with the port to those hosts dynamically.

  • Page 78: Arp And Arp Servers

    Configuring Classical IP 2.3 ARP and ARP Servers 2.3.1 Theory In order for a host to establish a connection to another host, it must first determine the other host’s ATM address. ATM ARP (ATM address resolution protocol) is the procedure used to resolve an IP address into an ATM address.

  • Page 79: Configuring A Fore Switch To Be An Arp Server

    Configuring Classical IP 2.3.2 Configuring a FORE Switch to be an ARP Server FORE’s ATM switches also have the capability of being an ARP server. (FORE’s ATM adapters can not be configured as an ARP server.) To configure a ForeRunner ATM switch as an ARP server, perform the following steps on only one of the SCPs: On one of the SCPs, determine the ATM address of that SCP for the relevant inter- face (qaa0 ->...

  • Page 80: Classical Ip Operation

    Configuring Classical IP 2.3.3 Classical IP Operation Once a host knows its own ATM address and the ATM address of its ARP server it attempts to establish a connection to the ARP server, which is used to send ARP requests and receive ARP replies.

  • Page 81: Operational Issues

    Configuring Classical IP 2.3.4 Operational Issues Certain hosts in an LIS may not support Classical IP. It is still possible to communicate with these hosts (and for these hosts to communicate with one another) by using static ARP entries. If a host does not support Classical IP, its IP-to-ATM address mapping should be placed in its ARP server’s cache as a static entry.

  • Page 82: Classical Ip Pvcs

    Configuring Classical IP 2.4 Classical IP PVCs 2.4.1 Theory and Configuration Normally, ATM connections in a Classical IP environment are established dynamically using UNI 3.0 or UNI 3.1. ARP, ILMI, and UNI 3.0 or UNI 3.1 all work together as described previ- ously to set up an SVC.

  • Page 83: Configuring The Network

    Configuring Classical IP 2.5 Configuring the Network In an ATM network, before any connections can be made, the two parties must know each other’s ATM address in order to set up that connection. To allow those connections to work, the ideal scenario is for all hosts and switches in the net- work to have support for both ILMI and for RFC-1577 (Classical IP over ATM).

  • Page 84: Third-Party Host With No Ilmi And No Rfc-1577 Support

    Configuring Classical IP 2.5.1 Third-Party Host with No ILMI and No RFC-1577 Support To configure a network with a third-party vendor’s host (or an edge device) that supports nei- ther ILMI nor RFC-1577 (as shown in Figure 2.1), perform the following steps: FORE Switch FORE FORE Switch...

  • Page 85: Third-Party Switch With Ilmi And No Rfc-1577 Support

    Switch A Third-Party Switch ILMI, no RFC-1577 = FORE Systems host Figure 2.2 - Configuring a Third-Party Switch with ILMI Support and No RFC-1577 Be sure that ForeThought software has been installed on all of the hosts and that ILMI was set in the process. ILMI dynamically performs address registration for all of the hosts.

  • Page 86: Third-Party Switch With Rfc-1577 And No Ilmi Support

    Switch B Third-Party Switch RFC-1577, no ILMI = FORE Systems host Figure 2.3 - Configuring a Third-Party Switch with RFC-1577 and No ILMI Support Be sure that ForeThought software has been installed on all of the FORE hosts and that ILMI was set in the process. ILMI dynamically performs address registration for all of the FORE hosts and FORE switches.

  • Page 87: Configuring An Emulated Lan

    CHAPTER 3 Configuring an Emulated LAN 3.1 Introduction This chapter describes how to design, configure, and maintain an Emulated LAN (ELAN) over an ATM network. An ELAN provides communication of user data frames among all members of the ELAN, similar to a physical LAN. One or more ELANs may run simulta- neously (and independently) on the same ATM network.

  • Page 88: Elan Components

    Configuring an Emulated LAN 3.2 ELAN Components The components of an ELAN include LECs, and LAN Emulation services consisting of a LECS, a LES, and a BUS. Although the ATM Forum specification allows the LES and BUS to be located on different devices, more intelligent traffic handling is possible when they are located on the same device.

  • Page 89: Lan Emulation Client (Lec)

    Configuring an Emulated LAN 3.2.1 LAN Emulation Client (LEC) The LEC is the component in an end system that performs data forwarding, address resolution, and other control functions when communicating with other components within the ELAN. It also provides a MAC level emulated Ethernet or Token Ring interface and appears to higher level software as though a physical interface is present.

  • Page 90: Emulated Lan Operation

    Configuring an Emulated LAN 3.3 Emulated LAN Operation This section describes the operation of an ELAN and its components from the point of view of a LEC. The operation of an ELAN may be divided into three phases: Initialization Registration and Address Resolution Data Transfer ELAN components communicate with each other using ATM connections.
  • Page 91 Configuring an Emulated LAN LECS LEC1 CONFIGURATION - DIRECT CONTROL - DIRECT CONTROL - DISTRIBUTE MULTICAST - SEND MULTICAST - FORWARD DATA - DIRECT engineering LEC2 Figure 3.2 - ELAN Operation 3 - 5 ForeRunner ATM Switch Network Configuration Manual...

  • Page 92: Initialization

    Configuring an Emulated LAN 3.3.1 Initialization Upon initialization, LEC1 obtains its own ATM address via ILMI address registration. LEC1 obtains the address of the LECS in one of four ways: by querying the switch to which LEC1 is connected via ILMI, by connecting to the “well-known” address defined by the ATM Forum’s LANE standards (47.0079.00.000000.0000.0000.0000.00A03E000001.00), by using PVC (0,17), or by using an address that is locally configured on LEC1.

  • Page 93: Registration And Address Resolution

    Configuring an Emulated LAN 3.3.2 Registration and Address Resolution After obtaining the address of the LES, LEC1 establishes a control-direct connection to the LES. When using DLE, this address is a single, anycast address which allows the LEC to reach one of the NOTE other DLE peer servers for its ELAN if its local server goes down.

  • Page 94: Data Transfer

    Configuring an Emulated LAN 3.3.3 Data Transfer When LEC1 receives a network-layer packet from a higher layer protocol to transmit to some destination MAC address (for example, LEC2), LEC1 initially does not know the correspond- ing ATM address of the destination. Consequently, LEC1 transmits an LE_ARP request to the LES.

  • Page 95: Distributed Lan Emulation

    Configuring an Emulated LAN 3.4 Distributed LAN Emulation Distributed LAN Emulation (DLE) allows the LES and BUS functions that are provided to each ELAN to be distributed among multiple, interconnected server platforms. In this way, DLE provides these ELANs with resiliency and scalability. To understand DLE operation, it is useful to compare DLE to the current LANE service model, which uses a single LES and BUS for each ELAN.

  • Page 96: Using A Single Server

    Configuring an Emulated LAN 3.4.1.1 Using a Single Server When LEC 1 wants to contact LEC 3, several messages are exchanged. First, LEC 1 attempts to learn the MAC address of LEC 3 by broadcasting an IP-ARP request with LEC 3’s IP address. As Figure 3.4 shows, this ARP request is sent in two steps: as a point-to-point message from LEC 1 to the LANE BUS, then...

  • Page 97: Limitations Of A Single Server

    Configuring an Emulated LAN 3.4.1.2 Limitations of a Single Server Because the there is only one LES/BUS supporting the ELAN, the following limitations exist: • The number of LECs in a single ELAN is limited by the number of virtual circuits that the single LES/BUS can establish through their platform’s ATM port.

  • Page 98: Distributed Lan Emulation Model

    Configuring an Emulated LAN 3.4.2 Distributed LAN Emulation Model To address the limitations of the single server model, DLE distributes the LANE services load among a mesh of LES/BUS DLE peer servers, as shown in Figure 3.6. LES/BUS 1 LES/BUS 3 LES/BUS 2 Eng LEC 6 Eng LEC 1...

  • Page 99: Using Dle

    Configuring an Emulated LAN 3.4.2.1 Using DLE Figure 3.7 shows how a connection begins to be established through DLE peer servers. LEC 1 wants to communicate with LEC 9, which is in the same ELAN, but is locally attached to a dif- ferent DLE peer server.
  • Page 100 Configuring an Emulated LAN LEC 9 recognizes its IP address, and prepares an IP ARP response. As shown in Figure 3.9, it then sends an LE-ARP request to its local LES , asking for the ATM address that matches LEC 1’s MAC address. Since LEC 9’s local LES does not have an entry for LEC 1, the local LES passes the query along to all of its locally-attached proxy LECs (none are shown in this figure) and all of its DLE peer servers LES/BUS 1...

  • Page 101: Advantages Of Dle

    Configuring an Emulated LAN When the third DLE peer server receives the LE-ARP response, it passes it directly to LEC 9 (which sent the original query) . The third DLE peer server also caches the registration infor- mation for LEC 1 so that other local LECs do not have to go through the entire process again. However, this cache ages out over time.

  • Page 102: Single Server Elan

    Configuring an Emulated LAN 3.4.2.2.3.1 Single Server ELAN Figure 3.12 shows a single server ELAN composed of nine LECs attached to three different switches. The LECS and the LES/BUS are attached to a host connected to a single switch. The process for LEC 1 to connect to the LANE services takes several steps: LEC 1 asks the signalling software on its switch to open a connection to the “well- known”...
  • Page 103 Configuring an Emulated LAN ELAN Eng LES/BUS 1 LECS Switch 2 Switch 1 Switch 3 Eng LEC 1 Eng LEC 2 Eng LEC 3 Eng LEC 4 Eng LEC 5 Eng LEC 6 Eng LEC 7 Eng LEC 8 Eng LEC 9 Figure 3.13 - ELAN with Single Server and Remote Connection to Server Figure 3.14 shows the ELAN in operation after three LECs have gone through the registration process.

  • Page 104: Dle Elan

    Configuring an Emulated LAN 3.4.2.2.3.2 DLE ELAN As noted previously, having a single server supporting an ELAN has a potential problem because the server can be a single point of failure. However, DLE can address this problem. By attaching the ELAN LECs to multiple DLE peer servers which communicate with each other as described earlier, the number of LECs affected by a server failure is reduced, and a backup server is provided for affected LECs to use.
  • Page 105 Configuring an Emulated LAN ELAN Eng ELAN Eng LES/BUS 2 LES/BUS 1 LECS Switch 2 Switch 1 Switch 3 Eng LEC 1 Eng LEC 2 Eng LEC 3 Eng LEC 4 Eng LEC 5 Eng LEC 6 Eng LEC 7 Eng LEC 8 Eng LEC 9 Figure 3.16 - ELAN with Multiple Servers in Operation...
  • Page 106 Configuring an Emulated LAN The failure and recovery process occurs as follows: Eng LES/BUS 1 has lost power. All circuits connected to it are torn down. Low- level signalling traffic (e.g., SSCOP messages) stop, and Switch 1 removes the address of Eng LES/BUS 1 from its link tables. LECs 1 and 4 had been connected to Switch 1.

  • Page 107: Elan Access Control

    Configuring an Emulated LAN 3.5 ELAN Access Control Basic ATM Forum LAN Emulation Servers do not guard against unauthorized users learning an ELAN’s LES address and then joining the ELAN. However, a method of authorization checking is available in ForeThought 5.2.x. After a LEC obtains the address of its LES, the LEC sends a request to the LES to join the ELAN.

  • Page 108: Configuring An Elan

    Configuring an Emulated LAN 3.6 Configuring an ELAN There are different instructions for configuring an ELAN, depending on how your network is currently configured. Please read the following list to determine which set of instructions to use. • If you had previously configured LANE, you want to upgrade some or all of the clients to ForeThought 5.2.x, and you want to upgrade all the equipment that is running services to ForeThought 5.2.x using DLE, use the instructions found in Section 3.7.

  • Page 109: Configuring An Lecs Configuration Database File

    Configuring an Emulated LAN 3.6.1 Configuring an LECS Configuration Database File The LECS uses a text configuration file to contain the configuration information needed by LECs that wish to participate in an ELAN. The LECS configuration file may be built and edited using a text editor such as vi or emacs.

  • Page 110: Lecs Configuration File Syntax

    Configuring an Emulated LAN make changes LECS configuration file while the LECS process is NOTE running. The configuration file is reread periodically by the LECS process (the default period is ten minutes). Consequently, any changes that you make to the configuration file are not recognized until the file is reread.
  • Page 111 Configuring an Emulated LAN Table 3.1 defines the various key parameters that may be entered in the configuration file. The acceptable range of values and the default value for each parameter is also given. Table 3.1 - LECS Configuration File Parameters Parameter Definition Identifies the type of ELAN, either Ethernet/IEEE 802.3...
  • Page 112 Configuring an Emulated LAN Table 3.1 - LECS Configuration File Parameters (Continued) Parameter Definition Specifies the minimum time between switching BUS and .Path_Switching_Delay: 6 data paths, in seconds. The minimum is 1 and the maxi- mum is 8. The default value is 6 seconds. The segment ID of the emulated LAN for an IEEE 802.5 .Local_Segment_ID source routing bridge.
  • Page 113 Configuring an Emulated LAN Table 3.1 - LECS Configuration File Parameters (Continued) Parameter Definition Specifies the minimum amount of time to wait before re- .Resolution_Hold_Down_Time: 160 initiating an MPOA Resolution Request after a failed resolution attempt. This value is usually greater than the Resolution_Maximum_Retry_Time.
  • Page 114 Configuring an Emulated LAN Table 3.1 - LECS Configuration File Parameters (Continued) Parameter Definition Specifies the format for the IP addresses <dotted- <dotted-addr> addr> used above. The format is <octet>.<octet>. <octet>.<octet>. The range of each octet is from 0 to 255.
  • Page 115 Configuring an Emulated LAN Table 3.1 - LECS Configuration File Parameters (Continued) Parameter Definition Specifies the format for the number of seconds for the <frame-time> set-up and tear-down thresholds. The range is 0 through 65535. Specifies the parameters used in signalling a connection <qos>...

  • Page 116: Defining An Elan

    Configuring an Emulated LAN 3.6.1.3 Defining an ELAN Each ELAN is defined by an address statement whose value denotes the ATM address of the ELAN’s LES. For example: engineering.Address: c5.0005.80.ffe100.0000.f21a.01b9.0020480605b2.00 To configure DLE for an ELAN, use the anycast address in this statement. Be sure to use a NOTE distinct anycast address for each ELAN in the network.

  • Page 117: Defining A Client

    Configuring an Emulated LAN The last two forms of ATM-address matching elements are functionally the same. The latter is shorter but only allows for masks whose semi-octets are all ones or all zeros, while the former allows for arbitrary masks. A prospective-client address is “captured” by an ELAN name if the client’s address matches one of the Accept elements but not one of the Reject elements (if present).

  • Page 118: Lecs Control Parameters

    Configuring an Emulated LAN 3.6.1.5 LECS Control Parameters Specifying values for keys in the LECS group provides control over the operation of the LECS process. If you change the values of the LECS control parameters while the LECS process is running, NOTE the new values do not take effect until the LECS process is stopped, and then restarted.

  • Page 119: Lecs Mpoa Parameters

    Configuring an Emulated LAN 3.6.1.6 LECS MPOA Parameters MPOA requests use similar, and in many cases, the same database keys as LANE requests. However, there are some MPOA-specific keys that can be specified. LEC/MPC parameters can be specified for shortcuts. For example, the following group of parameters indicates that shortcuts should be established for IP flows, but only after a threshold of 10 frames per second is surpassed.
  • Page 120 Configuring an Emulated LAN For example, you could specify that telnet traffic to the Class C 202.19.88.0 subnet should be sent on a UBR VCC with a peak rate of 10,000 cells per second, but only after the traffic on that connection exceeds 20 frames per second.

  • Page 121: Sample Lecs Configuration File

    Configuring an Emulated LAN 3.6.2 Sample LECS Configuration File Do not attempt to edit an existing functional CAUTION LECS configuration file without first making a backup copy of the file. Incorrect modification of the configuration file could result in loss of communication between one or more members of a defined ELAN.
  • Page 122 Configuring an Emulated LAN # The search ordering of elan names Match.Ordering: default, engineering, marketing # the default configuration parameters .Control_TimeOut: 120 .Maximum_Unknown_Frame_Count: 1 .Maximum_Unknown_Frame_Time: 1 .VCC_TimeOut_Period: 1200 .Maximum_Retry_Count: 1 .Aging_Time: .Forward_Delay_Time: 15 .Expected_LE_ARP_Response_Time: 1 .Flush_TimeOut: 4 .Path_Switching_Delay: 6 .Multicast_Send_VCC_Type: Best Effort .Connection_Complete_Timer: 4 .LAN_Type: Ethernet/IEEE 802.3 .Maximum_Frame_Size: 1516...
  • Page 123 Configuring an Emulated LAN # Parameters for elan: engineering engineering.Address: 47.0005.80.ffe100.0000.f21a.01b9.0020480605b2.11 engineering.Accept: 002048080011 , 0020481020ef engineering.Maximum_Frame_Size: 4544 # Parameters for elan: marketing marketing.Address: 47.0005.80.ffe100.0000.f21a.01b9.0020480605b2.21 marketing.Accept: 002048080011 , 0020481020ef Figure 3.20 - Sample LECS Configuration File (Part Two of Two) 3 - 37 ForeRunner ATM Switch Network Configuration Manual...

  • Page 124: Starting The Lan Emulation Services

    Configuring an Emulated LAN 3.6.3 Starting the LAN Emulation Services LAN Emulation services include the LECS and the LES/BUS. Once the LECS configuration database file has been configured, these services must be started so that they are available for LECs to attempt to use. Using ForeThought 5.2, the LES/BUS services must run in the same device.
  • Page 125 Configuring an Emulated LAN Use the following AMI command to verify that the LECS has been started and is running: configuration lane lecs show Index AdminStatus OperStatus Selector Database 0x0c atm-forum lecs.cfg The OperStatus field shows up, meaning that the LECS is running. Now you must start the DLE peer servers as described in the next section.

  • Page 126: Starting The Dle Les/Bus Peer Servers

    Configuring an Emulated LAN 3.6.3.2 Starting the DLE LES/BUS Peer Servers The LES and BUS services must be started for the ELAN. This example assumes you are using DLE; therefore, you must enter a distinct anycast address (that is unique within the first 19 bytes) for the LECs to use to contact the LES, and the address of each of the DLE peer servers so that this server can communicate with its peers.
  • Page 127 Configuring an Emulated LAN You must enter the address of each of the DLE peer servers when you are starting DLE; e.g., if NOTE you want four peers, then all four must be configured with the addresses of the other three peers, as well as their own LES address, at the time that each LES/BUS is started.

  • Page 128: Starting The Lec(S) And Joining An Elan

    Configuring an Emulated LAN 3.6.4 Starting the LEC(s) and Joining an ELAN Now that the ELAN services have been started, you can have LECs join the ELAN that you have created. The switch software only allows you to create an instance of a LEC on a switch.
  • Page 129 Configuring an Emulated LAN If you want to use the manual mode, you must enter either a LECS address other than the well- NOTE known address or you must enter a LES address. If you enter a LES address, this means that the LEC bypasses the LECS and directly contacts the specified LES.

  • Page 130: Upgrading An Elan To Use Dle

    Configuring an Emulated LAN 3.7 Upgrading an ELAN to Use DLE This section describes how to upgrade your ELAN if you had previously configured LANE, you want to upgrade some or all of the clients from ForeThought 4.1.x to ForeThought 5.2.x, and you want to upgrade all the equipment that is running services to ForeThought 5.2.x using DLE.

  • Page 131: Edit The Lecs.cfg File

    Configuring an Emulated LAN 3.7.1 Edit the LECS.CFG File Before you edit the LECS.CFG file, you may wish to back it up to a host using the oper flash put NOTE command. If you are using TFTP as the transfer protocol (this is the default), the remote host to which the FLASH file will be sent must be running the TFTP server code and must have on...

  • Page 132: Delete The Les And Bus

    Configuring an Emulated LAN Give the anycast address of the DLE peer servers to the new ELAN. Also, replace the LES address of the old ELANs with this anycast address, except for the last of the |n failover ELANs (in this case, Mktg|1). Leave Mktg|1 with old LES address for now so the LECs can use it until they are all changed over.

  • Page 133: Upgrade The Switches Running Services

    Configuring an Emulated LAN Verify the LES has been deleted. myswitch::configuration lane les> show No LES information is available. The LES and BUS in this example were co-located. If yours are not co-located, you need NOTE to administer the BUS down using conf lane bus admin <...

  • Page 134: Transfer The Updated Lecs.cfg File

    Configuring an Emulated LAN Create a DLE peer server (LES/BUS pair) with the new ELAN name (in this case, Mktg) on each switch that is to become a DLE peer server. myswitch::configuration lane les> new 0x00 Mktg -anycast c5.0005.80.ffe100.0000.f21c.126b.0020481c126b.66 -peers 47.0005.80.ffe100.0000.f21a.24f9.0020481a24f9.00 47.0005.80.ffe100.0000.f21c.10bb.0020481c10bb.90 Use the show command to verify the information that you entered:...

  • Page 135: Restart The Lecs

    Configuring an Emulated LAN 3.7.6 Restart the LECS Administer the LECS down and back up again. This forces any active clients to re-establish their connection with the LECS and forces the LECS to read and use the new LECS.CFG file. myswitch::configuration lane lecs>...
  • Page 136 Configuring an Emulated LAN Use the following command to get the interface name from the IfName field as follows: myswitch::configuration lane lec> show advanced Admin Oper Index Status Status Mode MACaddress IfName ELAN 0x11 wellknown 0a20481a2c78 el17 Mktg|0 LECS:0x47.0079.00.000000.0000.0000.0000.00a03e000001.00 LES :c5000580ffe1000000f21c126b0020481c126b66 BUS : 47000580ffe1000000f21c126b0020481c126b66 LEC ID : 13057 Discovered ELAN name : Mktg|0...

  • Page 137: Create The Last Dle Peer

    Configuring an Emulated LAN Use the following command to verify that the LEC has joined the ELAN by looking at the OperStatus field as follows: myswitch::configuration> lane lec show advanced Admin Oper Index Status Status Mode MACaddress IfName ELAN 0x11 wellknown 0a20481a2c78 el17...

  • Page 138: Update The Lecs.cfg File

    Configuring an Emulated LAN 3.7.10 Update the LECS.CFG File After you add the last DLE peer, go back and delete the old remaining failover ELAN informa- tion from the LECS.CFG file. Transfer the file to a workstation for editing. myswitch::operation> flash put lecs.cfg 169.144.85.195:/tftpboot/lecs.cfg Transferred 2323 bytes of fs:/lecs.cfg On that workstation, use a text editor to delete all lines referring to any of the |n failover ELANs (in this case, Mktg|0 and Mktg|1).

  • Page 139: Restart The Lecs

    Configuring an Emulated LAN 3.7.12 Restart the LECS Administer the LECS down and back up again. This forces the active LECs to re-establish their connection with the LECS and forces the LECS to read and use the new LECS.CFG file. myswitch::configuration lane lecs>...

  • Page 140: Upgrading An Elan Without Using Dle

    Configuring an Emulated LAN 3.8 Upgrading an ELAN without Using DLE This section describes how to upgrade your ELAN if you had previously configured LANE, you want to leave the clients running ForeThought 4.1.x, and you want to upgrade all the equipment that is running services to ForeThought 5.2.x without using DLE.

  • Page 141: Deleting The Non Co-Located Services

    Configuring an Emulated LAN 3.8.1 Deleting the Non Co-located Services There are several steps involved in changing the non co-located services. 3.8.1.1 Administer Down the Services Administer down the LECS. myswitch::configuration lane> lecs admin <LECS index> down Administer down the LES and BUS. myswitch::configuration lane>...

  • Page 142: Upgrade The Switches Running Services

    Configuring an Emulated LAN Transfer the LECS.CFG file that is currently being used by the LECS to a workstation (other than the one to which you backed up the file) so you can edit the file. myswitch::operation> flash put lecs.cfg 169.144.85.195:/tftpboot/lecs.cfg Transferred 2323 bytes of fs:/lecs.cfg On the workstation that has the LECS.CFG file, use a text editor to delete any lines that refer to any non-colocated BUSs.

  • Page 143: Administer The Services Up

    Configuring an Emulated LAN 3.8.4 Administer the Services Up Administer up the LES/BUS pair and the LECS on the switch(es) running each of the services. myswitch::configuration lane> les admin <LES index> up myswitch::configuration lane> lecs admin <LECS index> up The transfer of your ELAN to ForeThought 5.2.x is now complete. 3 - 57 ForeRunner ATM Switch Network Configuration Manual...
  • Page 144 Configuring an Emulated LAN 3 - 58 ForeRunner ATM Switch Network Configuration Manual...

  • Page 145: Mpoa

    • the LAN Emulation Configuration Server (LECS) The LANE services may operate on a FORE Systems ATM switch, PowerHub 7000, or Solaris workstation. ForeThought also provides support for Distributed LAN Emulation (DLE) which provides load-sharing and improved fault-tolerance within an ELAN.

  • Page 146: Lane Primer

    MPC “hat,” the additional function of the LEC/MPC in an MPOA-aware network is to source and sink internetwork shortcuts. Runs on a Solaris workstation or a FORE Systems LAN Emulation Configuration Server (LECS) ATM switch. Maintains information about all ELANs within the administrative domain.

  • Page 147: An Example Lane Configuration

    MPOA Runs on a PowerHub 7000, a ForeRunner ATM switch, LAN Emulation Server (LES) or a Solaris workstation. Maintains information about the LEC/MPCs within a single ELAN and performs address resolution. The LES can be configured to support or disable MPOA operation in an ELAN.

  • Page 148: The Initialization Process

    MPOA Each PC runs a LEC/MPC ASX-200BX ASX-200BX Runs a LECS, Runs a LECS, SWITCH SWITCH LES/BUS, and LES/BUS, and PowerHub 7000 Runs a LEC/MPC Fast Ethernet FDDI Ethernet Figure 4.1 - An Example of an ELAN 4.2.2.1 The Initialization Process Each LEC/MPC goes through the following process when it starts up: The LEC/MPC obtains its own ATM address via address registration.

  • Page 149: The Connection Process

    MPOA The LEC/MPC requests the information needed to join a specified ELAN or the default ELAN. The LECS has information about available ELANs, what ELANs each LEC/MPC can join, and which ELAN the LEC/MPC should attempt to join first. If a LECS is not available, or if you choose not to use it, you can manually specify the information required to join a specific ELAN.

  • Page 150: Multiple Elans

    MPOA 4.2.2.5 Multiple ELANs It is possible to set up more than one ELAN in a FORE network. For each new ELAN, you must configure another LES/BUS instance for that LAN. On the access devices, bridge groups must be used to associate physical ports with ELANs on the ATM side. An end station in the ELAN with a ForeRunner adapter can connect to up to 16 ELANs simultaneously.

  • Page 151: An Introduction To Multi-Protocol Over Atm

    MPOA 4.3 An Introduction to Multi-Protocol Over ATM MPOA builds upon the foundation of LANE. 4.3.1 LANE Without MPOA ATM networks co-exist with and support network applications which may not be ATM- aware. Consequently, ATM protocols are needed to monitor legacy network protocol (IP, IPX, Appletalk, etc.) packets and perform translation into ATM cells and circuits.

  • Page 152: Why Mpoa

    MPOA In addition to LANE, protocols such as IP can operate over an ATM network via the IETF Internetworking Over NBMA Networks (ION) Working Group’s Next Hop Resolution Protocol (NHRP). NHRP allows the ATM network to be divided into Logical IP Subnets (LISs). Using NHRP, routers are still required to interconnect these subnets;...
  • Page 153 MPOA E LAN E LAN marketing R outer engineering ATM Cloud Figure 4.3 - LANE with MPOA 4 - 9 ForeRunner ATM Switch Network Configuration Manual...

  • Page 154: Mpoa Components

    MPOA 4.3.3 MPOA Components MPOA requires LANE services for both ELAN traffic handling and MPOA configuration. The LEC/MPC can wear two different “hats.” When LANE/MPOA Client (LEC/MPC) wearing its LEC “hat,” it simply communicates with other ELAN components (the LES and BUS) to resolve MAC addresses into ATM addresses.

  • Page 155: Mpoa Example

    MPOA 4.3.4 MPOA Example The following are the basic requirements for establishing a shortcut across an MPOA-enabled network: • There must be LEC/MPCs at each end of the network between which a shortcut is desired. • The local router interface at each end must be running an MPS. •...

  • Page 156: Mps Configuration

    MPOA 4.3.4.1 MPS Configuration The network administrator must configure each MPS with the site-specific IP address match- ing the gateway address being used by LEC/MPCs in its ELAN. The MPS on each PowerHub 7000 is configured as follows: For each LANE/MPOA virtual port, specify an ELAN name. The LECS configura- tion must also be updated to allow the MPS to join these ELANs.

  • Page 157: Flow Analysis

    MPOA 4.3.4.3 Flow Analysis On a LEC/MPC’s host or edge device, IP packets with destinations within the host’s subnet are sent using LANE 1.0 methods; i.e., the client puts on its LEC “hat” and works directly with its ELAN’s services to connect with local destinations. Packets destined for remote subnets cause the LEC/MPC to put on its MPC “hat.”...

  • Page 158: Shortcut Teardown

    MPOA When the ingress LEC/MPC receives the NHRP response containing the destina- tion’s ATM address, it first checks if a shortcut circuit to that ATM address already exists. If a shortcut circuit to that address already exists, it sends the packets via the existing shortcut circuit.

  • Page 159: Forethought Pnni

    Forum approved protocol which defines interoperability between private ATM switches. PNNI defines both the routing and signalling standards for inter-switch interoperability. This chapter provides an overview of FORE Systems’ pre-standard version of PNNI, ForeThought PNNI (FT-PNNI), and its use in a multiple-switch network. FT-PNNI is a scalable routing and signalling protocol used in networks containing multiple ForeRunner switches.

  • Page 160: Ft-Pnni Routing

    ForeThought PNNI 5.1 FT-PNNI Routing The FT-PNNI routing protocol serves to distribute topology and address reachability informa- tion between switches and groups of switches in a network. This topology and addressing information is used by switches to compute paths through the network. The functions of the FT-PNNI routing protocol include the following: •...

  • Page 161: Hierarchical Addressing

    ForeThought PNNI 5.1.4 Hierarchical Routing FT-PNNI operates in a hierarchical topology. The structure of the hierarchy is defined by the peer group ID in a routing domain. Address assignment in FT-PNNI, therefore, corresponds to this hierarchical topology, providing increased scalability. 104 bits Peer Group ID Switch Summary Prefix...

  • Page 162: Path Computation

    ForeThought PNNI 5.1.4.1.2 Switch Summary Prefix Each switch is configured with a switch mask (swmask) which gives the length of the switch summary prefix within the switch prefix. The swmask gives the number of most significant bits of the switch prefix that constitute the switch summary prefix. Since all end system addresses attached to a switch have the same switch summary prefix, their reachability information can be summarized by this prefix (i.e., by the switch summary prefix).

  • Page 163: The Physical Network

    ForeThought PNNI 5.2 The Physical Network In an ATM network, data is sent and received over virtual circuits, or circuits that only exist when needed. This communication over these virtual circuits is made possible by signalling that occurs between the switches in the network. In a network of ForeRunner switches, any new addition to the topology is recognized immedi- ately by all nodes (switches) having a direct connection to the new node.
  • Page 164 ForeThought PNNI Figure 5.2 - Private ATM Network with 21 Switches and 34 Bidirectional Links It is in these large, single-level networks that FT-PNNI is most useful, because it lets you sim- plify large network topologies by creating a two-level hierarchy. In this hierarchy, clusters of contiguous switches are grouped together and they are collectively summarized by a single, logical node.
  • Page 165 ForeThought PNNI Peer Group C Peer Group Peer Group D Border Switch Switch/Node Logical Link (loglink) Peer Group A Peer Group B Figure 5.3 - Example of FT-PNNI Hierarchy Showing Lowest-Level Peer Groups 5 - 7 ForeRunner ATM Switch Network Configuration Manual...

  • Page 166: Peer Groups

    ForeThought PNNI 5.2.1 Peer Groups The FT-PNNI hierarchy begins with a network of switches, organized into peer groups. A peer group is a collection of interconnected switches that are organized into a group. Peer group organization can be determined by a network administrator, but switches that are located close to one another are usually made into a peer group.

  • Page 167: Peer Group Summary Node

    ForeThought PNNI 5.2.4 Peer Group Summary Node (PGSN) A PGSN is a virtual (logical) or imaginary node that summarizes a peer group’s reachability information. The PGSN has the peer group ID of its peer group as its switch summary prefix. Each border switch in the peer group advertises a logical link (loglink) to the PGSN.
  • Page 168 ForeThought PNNI Backbone Link Peer Group Summary Node (PGSN) Figure 5.4 - View of the Network from Switches in Peer Group A 5 - 10 ForeRunner ATM Switch Network Configuration Manual...

  • Page 169: Atm Forum Pnni

    Through this re-organization, PNNI reduces the amount of topology information that those nodes must maintain. This chapter provides an overview of FORE Systems’ implementation of ATM Forum PNNI (hereafter referred to as PNNI), and its use in a multiple-switch network. To understand PNNI, it is important to first understand how PNNI’s routing and signalling protocols work.

  • Page 170: Database Exchange Protocol

    ATM Forum PNNI 6.1.2 Database Exchange Protocol When neighboring nodes determine that they are peers; i.e., that they belong to the same peer group and they are running compatible versions of the PNNI protocol, they begin a database exchange process. At regular intervals, each node tells the other what information it has in its topology database and requests similar information from the other neighboring nodes.

  • Page 171: Hierarchical Routing

    ATM Forum PNNI 6.1.5 Hierarchical Routing Hierarchical routing allows contiguous switches to be organized into peer groups. The switches within each peer group exchange detailed topology information about their own group that is not visible to switches outside the peer group. Similarly, switches within each peer group do not receive detailed topology information about switches outside of their peer group.

  • Page 172: Pnni Signalling Protocol

    ATM Forum PNNI 6.2 PNNI Signalling Protocol PNNI signalling is used to establish point-to-point and point-to-multipoint connections across the network. This protocol is based on ATM Forum UNI signalling with mechanisms added to support source routing and crankback. 6.2.1 Source Routing A DTL is a source route which specifies the preferred call routing path that the ForeThought PNNI or PNNI router should use when setting up an SVC.

  • Page 173: Internetworking Between Pnni And Ft-Pnni

    ATM Forum PNNI 6.3 Internetworking between PNNI and FT-PNNI When ATM Forum PNNI is deployed, some networks running FT-PNNI will be connected to networks running PNNI. To provide internetworking of these protocols, ForeThought 5.2.x allows reachability information to be leaked dynamically between FT-PNNI and PNNI peer groups.

  • Page 174: Dynamic Leaking Of Reachability Information

    ATM Forum PNNI 6.3.2 Dynamic Leaking of Reachability Information This feature allows dynamic leaking of reachability information between the single FT-PNNI node and the single PNNI node within a gateway switch. It may also be used to control the leaking of reachability information between two PNNI peer groups. Using split switches, it possible to connect and exchange reachability information between any number of PNNI peer groups.

  • Page 175: Peer Groups In Areas

    ATM Forum PNNI 6.3.2.1.1 Peer Groups in Areas Multiple peer groups can exist within an area. Peer groups within an area are connected to each other by border links as shown in Figure 6.3. Peer Group Border Link Peer Group D Switch/Node Horizontal Link Peer Group C...

  • Page 176: Levels

    ATM Forum PNNI 6.3.2.1.3 Levels Each areas has a level associated with it. Levels are used to control the flow of reachability information in a multi-level routing hierarchy (which is discussed in the next section). An N-level hierarchy has N discrete values of levels associated with it, namely, L ,..., L .

  • Page 177: Configuring Domains

    ATM Forum PNNI In Figure 6.4, the two nodes configured in switch S1 belong to different areas, and so they do not share the same link-state topology database. The same is true for the nodes configured in switch S4. Dynamic reachability leaking takes place among the nodes in switch S1, enabling end systems in Area A to reach other end systems in Area B, and vice versa within Domain 1.

  • Page 178: Propagation Of Reachability Information

    ATM Forum PNNI 6.3.2.3 Propagation of Reachability Information The leaking of reachability information between two areas is constrained by two things: policy and scope. 6.3.2.3.1 Policies ForeThought software lets you configure a policy as a flexible means of enforcing security across the network topology.

  • Page 179: The Process For Leaking Reachability

    ATM Forum PNNI When a leaked address is to be advertised or summarized, a node also determines the scope with which to advertise the address (or its summary). The scope denotes the highest level in the PNNI routing hierarchy at which an address can be advertised. Scoping ensures that reachability information does not loop.
  • Page 180 ATM Forum PNNI 6 - 12 ForeRunner ATM Switch Network Configuration Manual...

  • Page 181: Chapter 7 Signalling

    CHAPTER 7 Signalling This chapter contains information that pertains to the signalling portion of ForeThought soft- ware. This signalling information is described in the following sections: • Section 7.1 - VCI Allocation Range • Section 7.2 - Signalling Scope • Section 7.3 - Signalling Channel Auto Configuration Procedures •...

  • Page 182: Determining The Vci Allocation Range With Ilmi Down

    Signalling 7.1.1 Determining the VCI Allocation Range with ILMI Down If ILMI is not operational and if the VCI allocation range of the signalling channel is specified, then the range is determined as an intersection of the following: • the VCI-range of the path containing the signalling channel •...
  • Page 183 Signalling In another example, if there are VCIs already reserved on VP 65, as shown below in the MinVCI and MaxVCI fields: configuration vpt show Input Output Port Port ResBW CurBW MinVCI MaxVCI Protocol terminate 37.3K terminate 0.8K terminate 0.8K terminate 0.8K terminate...

  • Page 184: Determining The Vci Allocation Range With Ilmi Up

    Signalling 7.1.2 Determining the VCI Allocation Range with ILMI Up If ILMI is operational, then the peer switch’s VCI allocation range is obtained by reading its ILMI MIB variable atmfAtmLayerMaxVccs. The VCI allocation range of the signalling chan- nel is then determined as an intersection of the following: •...
  • Page 185 Signalling In another example, if the peer supports the range of 32 - 511, but there are VCIs already reserved on VP 65, as shown below in the MinVCI and MaxVCI fields: configuration vpt show Input Output Port Port ResBW CurBW MinVCI MaxVCI Protocol terminate...
  • Page 186 Signalling In a third example, if the peer only supports the range of 32 - 180, and VCIs 1 - 120 are already reserved on VP 65, and you enter the following: conf signalling new 1A3 65 -ilmi up -minvci 70 -maxvci 200 then the actual range is computed as an intersection based on the range you enter (70 - 200), the range available in that VP (1 - 120), and the range supported by the peer (32 - 180).

  • Page 187: Signalling Scope

    Signalling 7.2 Signalling Scope A signalling channel can be configured to control either VCs within its own VP (VP-scope, the default) or to control VCs in its own VP, in addition to controlling VCs in other VPs on the link (link-scope).

  • Page 188: Dynamic Paths

    Signalling 7.2.2 Dynamic Paths A link-scope signalling channel allocates new virtual channel connections based on the avail- ability of virtual channel connections within the VC-space of the link-scope signalling channel at that time. A link-scope signalling channel allocates connections in a new originating/termi- nating path (called a dynamic path, because signalling uses such a path on the fly) when its cur- rent VC-space is exhausted.

  • Page 189: Signalling Channel Auto Configuration Procedures

    Signalling 7.3 Signalling Channel Auto Configuration Procedures This section provides an overview of signalling channel auto configuration and describes some rules for configuring signalling interfaces. Auto configuration requires that ILMI is up on that signalling interface. 7.3.1 Overview of Signalling Channel Auto Configuration Signalling support for UNI 3.0, UNI 3.1, and UNI 4.0 is provided in ForeThought 5.2.x.
  • Page 190 Signalling The following two tables summarize the above information. Table 7.1 highlights the actions taken based on the configurations of the FORE switches on both sides of an interface. ForeThought versions prior to ForeThought 4.1.x always default to UNI 3.0. Both UNI 3.1 and UNI 4.0 use SSCOP version 31.
  • Page 191 Signalling An alternative way of looking at the auto configuration procedure is to look at the atmfAtmLayerUniVersion variable. Table 7.2 shows actions taken based on the atmfAtmLayerUniVersion variable supported by the peer switch. Table 7.2 - Action Taken Based on the Peer’s Supported MIB Variable Configured atmfAtmLayer Action Taken...

  • Page 192: Rules For Signalling Channel Auto Configuration

    Signalling 7.3.2 Rules for Signalling Channel Auto Configuration In ForeThought 5.0.x and greater, there are two rules for signalling channel auto configuration. The first deals with specifying the signalling interface type and signalling interface version. The second rule concerns specifying the signalling scope and mode. 7.3.2.1 Specifying the Type and Interface Version In AMI, the signalling interface type and signalling interface version are now treated as a pair.

  • Page 193: Examples Of Valid Configurations

    Signalling 7.3.2.1.1 Examples of Valid Configurations The following are examples of valid configurations to enter into AMI: conf sig new 1a1 0 conf sig new 1a1 0 -type privateUNI -version uni30 conf sig new 1a1 0 -type privateUNI -version uni31 conf sig new 1a1 0 -type privateUNI -version uni40 conf sig new 1a1 0 -type publicUNI conf sig new 1a1 0 -type publicUNI -version auto...

  • Page 194: Examples Of Invalid Configurations

    Signalling 7.3.2.1.2 Examples of Invalid Configurations Table 7.4 shows examples of invalid configurations to enter into AMI and the reasons why they are invalid. Table 7.4 - Invalid Type and Version Combinations Invalid Combination Reason conf sig new 1a1 0 -version uni30 The type is not entered (auto).

  • Page 195: Specifying The Scope And Mode

    Signalling 7.3.2.2 Specifying the Scope and Mode In AMI, the signalling scope (designated in AMI as -sig_alloc) and the signalling mode (designated in AMI as -sig_mode) are now treated as a pair. The pertinent portion of the AMI syntax is listed here for reference: myswitch::configuration signalling>...

  • Page 196: Examples Of Valid Configurations

    Signalling 7.3.2.2.1 Examples of Valid Configurations The following are examples of valid configurations to enter into AMI: conf sig new 1a1 0 conf sig new 1a1 0 -sig_alloc auto -sig_mode auto conf sig new 1a1 0 -sig_alloc vp -sig_mode vpAssoc conf sig new 1a1 0 -sig_alloc link -sig_mode nonAssoc The first example is the default that is most often used when configuring a signalling interface.
  • Page 197 Signalling There is a potential invalid configuration that can occur because the auto configuration of the operating scope and mode depend on whether a path is an elastic path or not. A non-elastic path has bandwidth reserved for it from the link bandwidth at the time that the path is created (when the -reserved option in conf vpt new is used.) An elastic path does not have reserved bandwidth at creation time.

  • Page 198: Allowable Combination Of Traffic Parameters

    Signalling 7.4 Allowable Combination of Traffic Parameters 7.4.1 PNNI 1.0/UNI 4.0 The following information applies to both signalled connections and to PNNI SPVCs. 7.4.1.1 Service Categories The ATM service categories assigned to connections in PNNI 1.0 and UNI 4.0 are defined in the ATM Traffic Management Specification, Version 4.0 (TM 4.0).

  • Page 199: Uni 3.X

    7.4.2 UNI 3.X FORE Systems supports a subset of traffic contracts which are specified in Table F.1 of the UNI 3.1 specification. These traffic contracts are enforced on both signalled connections as well on PNNI SPVCs. The following are the allowable contracts supported by FORE’s switch fabrics.
  • Page 200 Signalling Table 7.7 shows the subset of the UNI 3.1 allowable combination of traffic parameters sup- ported by ForeThought 5.2.x: Table 7.7 - UNI 3.1 Allowable Combination of Traffic Parameters in ForeThought 5.2.x Broadband Bearer Class Traffic Type & & &...

  • Page 201: Chapter 8 Security

    CHAPTER 8 Security ForeThought software (that is version 5.0.x or greater) provides various forms of switch secu- rity. Security can be implemented by creating userids. There are also security methods that prevent access to the switch, which include IP filtering and NSAP filtering. Each of these secu- rity methods is described in the following sections.
  • Page 202 Security If the administrator wants to change, add, or delete one or more userids and propagate these changes to the other switches, he or she should use the same method. First, make all of the modifications on one switch, back up the login file to a host, and restore the login file to each of the other switches.

  • Page 203: Login Authentication Method

    Security 8.1.1 Login Authentication Method The network administrator can configure two different forms of login authentication: local authentication and SecurID authentication. The administrator may employ either method for all users, or he or she may choose to employ the local method for some users and the SecurID method for other users.

  • Page 204: Securid Passcode

    Security 8.1.1.2.2 SecurID Passcode This authentication method provides a high level of security because the SecurID passcode that allows access to the protected switches is comprised of two parts: • a secret, memorized personal identification number (PIN) • the current code generated by the user’s assigned SecurID token 8.1.1.2.2.1 PIN Number The PIN is known only by the user.

  • Page 205: Data Encryption Between The Server And Switches

    Security 8.1.1.2.3.3 Data Encryption between the Server and Switches Messages sent between the server and the switches are encrypted either using the DES algo- rithm or Security Dynamics proprietary encryption algorithm. The server can use either method, but all switches must use the same algorithm as the one configured on the server. This data encryption method protects communications between the server and the switches because the first time the switch contacts the server, it receives a node secret file, which is a string of about 16 bytes.

  • Page 206: Editing The Server Configuration File

    Security Even though this information is stored in the FLASH, it cannot be accessed using any of the NOTE oper flash commands. The conf security login securid get, delete, and show commands must be used. If the configuration file is not found, if the wrong file was copied, or if the file is corrupted, the SecurID service does not work, an appropriate error message is logged to the console, and the user trying to log in is denied access.
  • Page 207 ADDRESSES: By name in host file or name service BAD PASSCODES: 3 RESPONSE DELAY: 2 TOKENS IN LICENSE: 25 LICENSE CONFIGURATION This license was created for: Fore Systems, Inc. 1000 FORE Drive Warrendale, PA 15086 These parameters are defined as follows: Parameter Description LICENSE CREATION The date the ACE/server license was created.

  • Page 208: An Example Login Using Securid

    Security Parameter Description ADDRESSES Indicates how network devices shall have the IP addresses resolved. BAD PASSCODES The number of failed login attempts with incorrect passcodes, after which the server puts the token associated with that userid into Next Token Mode. When the token is in this mode, the next time the same user tries to log in and gets the passcode correct, he or she is also prompted to enter the next token code;...

  • Page 209: Ami Command Privileges

    Security 8.1.2 AMI Command Privileges The network administrator can configure two different levels of AMI command privileges for userids: admin privileges and user privileges. Each method is described in the following sec- tions. 8.1.2.1 Admin Privileges A person whose userid is configured with admin privileges is allowed to access and use all of the AMI commands.

  • Page 210: Userid Password

    Security 8.1.4 Userid Password The network administrator may also assign a password to a userid using the conf security login password command. (This command replaces the old oper password command.) When a user logged in with user privileges wants to modify the password, he or she must correctly enter the old password first before typing the new password.

  • Page 211: Ip Filtering

    Security 8.2 IP Filtering The IP filtering feature lets the network administrator limit access to the control port of the switch to prevent unauthorized access to the switch. The switch performs filtering on incom- ing IP packets by determining if there is a match between the packet’s header source address and this table of authorized incoming IP addresses.

  • Page 212: Strict Source Routing Flag

    Security 8.2.2.1 Strict Source Routing Flag If the ssr flag is set to allow, all incoming IP packets that are strict source routed are accepted, provided that they match an IP address in the table of authorized addresses. If the ssr flag is set to disallow, all incoming IP packets that are strict source routed are rejected, even if they match an IP address in the table of authorized addresses.

  • Page 213: Nsap Filtering

    Security 8.3 NSAP Filtering This feature provides a mechanism for filtering calls based on a combination of the calling (source) and called (destination) addresses, as well as the incoming and outgoing UNIs. Each UNI may have one address filter for incoming call setups, and one for outgoing call set- ups.

  • Page 214: Nsap Filtering Lookup

    Security 8.3.2 NSAP Filtering Lookup A filter lookup mechanism is provided which allows you to enter components of a call setup message to test whether a call setup attempt with the supplied addresses and ports would be accepted or rejected by a specific filter. The switch returns an answer of accepted or rejected and the index number of the template that accepted or rejected the information entered.

  • Page 215: Configuring Timing

    CHAPTER 9 Configuring Timing This chapter describes how to set up timing on a ForeRunner ATM Switch. Topics covered include: • Section 9.1 - Overview • Section 9.2 - Timing Modes • Section 9.3 - Switchclock • Section 9.4 - Port Level Timing •...

  • Page 216: Switchclock

    Configuring Timing 9.3 Switchclock If a TCM is not installed in the switch, all of the ports within a fabric use the switchclock as their timing reference. The switchclock can be any port that is able to recover a clock (i.e., the network module supports distributed timing).

  • Page 217: Port Level Timing

    Configuring Timing 9.4 Port Level Timing In addition to the switchclock, there is also a configurable parameter for each port called a transmit clock (txclock). Each port’s txclock can be configured to use either the network clock or the internal clock. •...

  • Page 218: Timing Configuration Examples

    Configuring Timing 9.5 Timing Configuration Examples This section provides examples of how to set the switchclock on various types of switches. For more information about the specific timing commands, see the AMI Configuration Commands Reference Manual. If you have a TCM installed in your switch, see the CEC-Plus User’s Manual for information about configuring timing with a TCM.

  • Page 219: Configuring Timing On An Asx-1000 (Multiple Timing Domains)

    Configuring Timing 9.5.3 Configuring Timing on an ASX-1000 (Multiple Timing Domains) This example assumes that you are going to use 1C1 as your primary clock and 1D1 as your sec- ondary clock for fabrics 1 and 2 and that you are going to use 3A1 as your primary clock and 3B1 as your secondary clock for fabrics 3 and 4.
  • Page 220 Configuring Timing 9 - 6 ForeRunner ATM Switch Network Configuration Manual...

  • Page 221: Configuring Snmp

    APPENDIX A Configuring SNMP The switch control software for the ForeRunner ATM switches includes an SNMP agent. The SNMP agent enables the remote monitoring and configuration of these switches. A.1 SNMP Indexing There are two main SNMP indexing schemes used: software port indices and hardware port indices.
  • Page 222 Configuring SNMP Table A.1 - ASX-200WG/ASX-200BX Port Numbering Port Software Port Board-Netmod- Port Software Port Board-Netmod- Name Number Port Index Name Number Port Index 0.0.0 0.2.0 0.0.1 0.2.1 0.0.2 0.2.2 0.0.3 0.2.3 0.0.4 0.2.4 0.0.5 0.2.5 0.1.0 0.3.0 0.1.1 0.3.1 0.1.2 0.3.2 0.1.3...

  • Page 223: Snmp Traps

    Configuring SNMP A.2 SNMP Traps SNMP traps are used to update the state of the network automatically to remote network management hosts. The SNMP agent on the switch supports several SNMP traps. The traps generated by the switch’s SNMP agent can be sent to as many destinations as needed.
  • Page 224 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxPsInputDown This trap alerts that one ATM switch power supply failed due to failure in the input voltage. The power supply that failed is identified by the power supply index.
  • Page 225 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxSpansUp This trap alerts that the SPANS signalling on the link that is identified by the sigPathPort and sigPathVPI is asxTempSensorOverTemp This trap alerts that one of the temperature sensors indicates over temperature.
  • Page 226 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxSonetLineAISon This trap indicates that the specified SONET port is receiving a Line level Alarm Indication Signal from the far-end equipment. asxSonetLineAISoff This trap indicates that the Line AIS error condition signalled by the asxSonetLineAISon trap has been cleared.
  • Page 227 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxDS1YellowCleared This trap indicates that Yellow Alarm is cleared on the incoming signal. asxDS1AISDetected This trap indicates that AIS Alarm is detected on the incoming signal.
  • Page 228 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxE3AtmLCDCleared This trap indicates that the LCD failure identified by trap asxE3AtmLCDDetected has been cleared. An LCD failure is cleared when the LCD defect is absent for 10 +/- 0.5 seconds.
  • Page 229 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxE3AISDetected This trap indicates that the specified E3 port has detected incoming AIS Alarm. asxE3AISCleared This trap indicates that incoming AIS alarm has been cleared on the specified E3 port.
  • Page 230 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxDS3LOSCleared This trap indicates that the incoming LOS Alarm has been cleared on the specified DS3 port. asxSonetLOFDetected This trap indicates that the specified SONET port is experiencing Loss Of Frame (LOF) failure.
  • Page 231 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxSonetPathUNEQDetected This trap indicates that the specified SONET port is experiencing unequipped (UNEQ). A UNEQ failure is declared when the UNEQ defect persists for a period of 2.5 +/- 0.5 seconds.
  • Page 232 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxDS3AtmLCDCleared This trap indicates that the LCD failure identified by trap asxDS3AtmLCDDetected has been cleared. An LCD failure is cleared when the LCD defect is absent for 10 +/- 0.5 seconds.
  • Page 233 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number asxJ2HBERCleared This trap indicates that High Bit Error Rate (HBER) is cleared on the incoming signal. asxJ2PAISDetected This trap indicates that Payload Alarm Indication Sig- nal (PAIS) is detected on the incoming signal.
  • Page 234 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number 1028 q2931AVRejectTrap This trap is generated whenever any UNI3.x with AddressValidation enabled rejects a Setup Request call more than q2931AVRejectTrapThreshold times in any given q2931AVRejectTrapPeriod.
  • Page 235 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number 1038 asxVPAISCleared This trap indicates that the Alarm Indication Signal (AIS) has been removed from the incoming (terminat- ing) virtual path. This trap is generated once when the virtual path is declared to be in the inactive AIS state.
  • Page 236 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number 1068 asxPsCurrentDown This trap alerts that one ATM switch power supply had a current failure. The power supply that failed is identified by the power supply index. 1069 asxPsCurrentUp This trap alerts that one ATM switch power supply...
  • Page 237 Configuring SNMP Table A.2 - SNMP Traps Supported on the ForeRunner Switches (Continued) Trap Trap Name Description Number 2000 frf8PVCStatus This trap indicates when an interworking PVC has experienced an alarmed condition, either on the ATM network side or Frame Relay side. It is also generated when the PVC alarmed condition is cleared.
  • Page 238 Configuring SNMP Table A.3 defines the message types and the message requests for Trap 2003. Table A.3 - Message Type Encodings for Trap 2003 MessageType Message Request Configure network module Configure port Send egress Fdl Network module reset Port reset Configure a channel/service Request channel/service configuration Request port configuration...
  • Page 239 Configuring SNMP Table A.3 - Message Type Encodings for Trap 2003 (Continued) MessageType Message Request Request to enable/disable connection ingress rate enforcement Delete a connection Configure port to be timing source Table A.4 defines the error codes for Trap 2003 and their meanings. Table A.4 - Error Codes for Trap 2003 Error Code Error Code Meaning...
  • Page 240 Configuring SNMP Table A.4 - Error Codes for Trap 2003 (Continued) Error Code Error Code Meaning Invalid parameter Duplicate DLCI Memory allocation failure Service not created Connection does not exist Invalid Service Connection ID unavailable Invalid Connection ID Unexpected message Object already configured Operation failed Physical channel configuration failed...

  • Page 241: Adding Snmp Trap Destinations

    Configuring SNMP A.2.1 Adding SNMP Trap Destinations To create one or more SNMP trap destinations on a ForeRunner switch, log in to AMI and open a session on the switch. Enter the following parameters: configuration snmp trap destinations new <ipaddress> The <ipaddress>...

  • Page 242: Removing Snmp Trap Destinations

    Configuring SNMP A.2.3 Removing SNMP Trap Destinations To delete one or more SNMP trap destinations for a ForeRunner switch, log in to AMI and open a session on the switch. Prior to deleting any trap that may need to be recreated later, as a pre- caution, a recommended practice is to list all trap destinations using AMI and either copy the screen or write down the destinations.

  • Page 243: Appendix B Configuring Circuit Emulation Services

    APPENDIX B Configuring Circuit Emulation Services FORE Systems’ Circuit Emulation Services (CES) Network Modules (NMCE-6/DS1A and NMCE-6/E1A) provide adaptation from time-division multiplexed (TDM) equipment (i.e., PBXs, WAN multiplexers, channel banks, video codecs, etc.) and traffic to ATM. Both modules provide structured and unstructured services, with a maximum of 127 connections supported on each module.

  • Page 244: Configuring Ces Connections

    Configuring Circuit Emulation Services B.1 Configuring CES Connections The ces commands let you create and delete CES connections, as well as display the status of existing connections. You can display the list of available subcommands by typing ? at the ces level.
  • Page 245 Configuring Circuit Emulation Services SRTS only available unstructured connections, which are created by specifying all NOTE for the <timeslots> parameter. The -cas and -partialfill options are not applicable to unstructured mode. Structured mode is selected by indicating the exact timeslots to be used. For example, timeslots 1, 2, and 3 would be entered as 1-3, timeslots 2, 4, 6 would be entered...
  • Page 246 Configuring Circuit Emulation Services Parameter Description -reassCDVT <cdvt> The Cell Delay Variation Tolerance for cells being received by the segmentation and reas- sembly (SAR) engine. The range for this parameter is 100 to 24000 (in µs), and the default is 2000 (i.e., 2 ms). bufSize The amount of reassembly buffer space allocated for the connection.

  • Page 247: B.1.2 Displaying Ces Connections

    Configuring Circuit Emulation Services B.1.2 Displaying CES Connections To display the current CES connections, enter the following: myswitch::configuration ces> show Input Output Service State Port Timeslots VPI VCI Type Port TimeSlots VPI VCI down down spvc 1D3 down down spvc 1D3 The fields in this display are defined as follows Field Description...
  • Page 248 Configuring Circuit Emulation Services To display the advanced settings of the current CES connections, enter the following: myswitch::configuration ces> show advanced Service Clock Partial Integ. Service MapVPI MapVCI Type Mode Fill BufSize CDVT Period 2024 structured synch basic 0 2500 The fields in this display are defined as follows Field Description...

  • Page 249: Appendix C Converting From Ft-Pnni To Pnni

    APPENDIX C Converting from FT-PNNI to PNNI This appendix discusses the conversion of both non-hierarchical and hierarchical FT-PNNI networks to ATM Forum PNNI (hereafter referred to as PNNI) routing. It is assumed that you are familiar with the fundamentals of FT-PNNI and PNNI routing and familiar with FORE’s implementation of PNNI as described in Chapter 6 of this manual.

  • Page 250: Asx-1000 Routing Configuration Issues

    Converting from FT-PNNI to PNNI C.1 ASX-1000 Routing Configuration Issues This section discusses routing in hierarchical networks in which there are ASX-1000 switches present in your network. Because each one of the four fabrics appears as a single node in rout- ing and because you cannot take a two-hop path to go from one switch fabric to another switch fabric in the same ASX-1000, there are certain FT-PNNI and PNNI node configurations that should be avoided.

  • Page 251: Asx-1000S In Pnni Areas

    Converting from FT-PNNI to PNNI This problem can be avoided by not breaking up an ASX-1000 between multiple FT-PNNI peer groups. For example, in the network in Figure C.2, the entire ASX-1000 could have been made part of peer group B with only A.3, A.4, and A.5 in peer group A. A.3 and A.4 would be the border nodes in peer group A connected to A.1 and A.2 (re-numbered to have B as their peer group ID) in peer group B.

  • Page 252: Multiple Gateways In An Asx-1000

    Converting from FT-PNNI to PNNI C.1.3 Multiple Gateways in an ASX-1000 Another potential problem can occur when an ASX-1000 in a FT-PNNI area has gateways (split-switches with one FT-PNNI and one PNNI node) to a PNNI area. The ASX-1000 can only have, at most, one of its fabrics as a gateway between the FT-PNNI area and the PNNI area.

  • Page 253: Migration Of A Non-Hierarchical Ft-Pnni Network

    Converting from FT-PNNI to PNNI C.2 Migration of a Non-Hierarchical FT-PNNI Network This section discusses the conversion of a non-hierarchical FT-PNNI network to a non-hierar- chical (single peer group) PNNI network. It is assumed that all switches in your network are FORE switches.

  • Page 254: Detailed Migration Example

    Converting from FT-PNNI to PNNI C.2.2 Detailed Migration Example This section gives a detailed example of how to change the example non-hierarchical FT-PNNI network shown in Figure C.4 to a PNNI network. FT-PNNI node FT-PNNI link Figure C.4 - A Non-Hierarchical FT-PNNI Network This network has five switches named S1 through S5.
  • Page 255 Converting from FT-PNNI to PNNI PNNI peer group boundary PNNI node FT-PNNI peer group boundary FT-PNNI node FT-PNNI link Fore Area A4 Fore Level L4 Figure C.5 - S5 Changed to a Gateway Switch Convert S3 to a gateway switch by modifying the default protocol of the default domain in S3 to gateway using the following AMI command: conf atmroute domain modify <domain ID>...
  • Page 256 Converting from FT-PNNI to PNNI Convert S4 to a gateway switch by modifying the default protocol of the default domain in S4 to gateway using the following AMI command: conf atmroute domain modify <domain ID> gateway Reboot switch S4. Upon the reboot, S4 will come up with a FT-PNNI node in area 4 and a PNNI node in area 5.
  • Page 257 Converting from FT-PNNI to PNNI At this point, S3 no longer has any links attached to its FT-PNNI node, so it does not need to be a gateway switch anymore. Modify the default protocol of S3 to pnni using the following AMI command: conf atmroute domain modify <domain ID>...

  • Page 258: Migration Of A Hierarchical Ft-Pnni Network

    Converting from FT-PNNI to PNNI C.3 Migration of a Hierarchical FT-PNNI Network This section discusses the migration of a hierarchical FT-PNNI network to a FORE hierarchical PNNI network. It is assumed that all switches in your network are FORE switches. If your net- work contains a contiguous backbone, use the instructions found in Section C.3.1.

  • Page 259: Migration Overview

    Converting from FT-PNNI to PNNI C.3.1.1.1 Migration Overview The following basic steps are involved in the migration. Each of these steps is described in detail in the following sections. It is recommended that you read the entire section before attempting to change over your network. Upgrade each switch in the network to ForeThought 5.2x.
  • Page 260 Converting from FT-PNNI to PNNI Modify the default protocol of the default domain in C.1 to gateway using the fol- lowing AMI command: conf atmroute domain modify <domain ID> gateway Reboot switch C.1. Upon the reboot, C.1 will come up with two nodes: one FT-PNNI node and one PNNI node.
  • Page 261 Converting from FT-PNNI to PNNI B.1 will be the next switch to be converted to a gateway switch. Administer the node down. Change the peer group ID of its PNNI node to D, modify the level of its PNNI node to 2, modify the default protocol of the default domain in B.1 to gateway, then administer the node up using the following AMI commands: conf atmroute pnni node admin <index>...

  • Page 262: Convert The Individual Peer Groups

    Converting from FT-PNNI to PNNI C.2 is the final backbone switch to be converted to a gateway switch. Change the peer group ID of its PNNI node (currently down) to D, modify the level of its PNNI node to 2, and modify the default protocol of the default domain in C.2 to gateway using the following AMI commands: conf atmroute pnni node modify <index>...
  • Page 263 Converting from FT-PNNI to PNNI C.6 will be the first switch to be converted to a gateway between the existing FT-PNNI area and the PNNI area. This area should be at a lower level. The level of this peer group will be 6. Modify the level of the PNNI node (currently down) in C.6 to 2, change the area ID of its PNNI node to 6, and modify the default protocol of the default domain in C.6 to gateway using the following AMI commands:...
  • Page 264 Converting from FT-PNNI to PNNI Since C.3 is the last FT-PNNI switch, convert it directly to a PNNI switch by chang- ing the level of its PNNI node to 6, changing the area ID of C.3 to 6, and modifying the default protocol of the default domain in C.3 to pnni using the following AMI commands: conf atmroute pnni node modify <index>...
  • Page 265 Converting from FT-PNNI to PNNI Change the default protocol of the default domain in C.1 to pnni using the follow- ing AMI command: conf atmroute domain modify <domain ID> pnni Reboot switch C.1. Create a second PNNI node in C.1 with a node index of 2, the peer group ID set to C, area 6, and level 6 using the following AMI commands: conf atmroute pnni node modify 2 -pgid c -forelevel 6 -forearea 6 conf atmroute domain modify <domain ID>...
  • Page 266 Converting from FT-PNNI to PNNI 12. Upon reboot of C.1, C.3 and C.4 will no longer need to be gateway switches. So, modify the default protocol to PNNI using the following AMI command on each switch: conf atmroute domain modify <domain ID> pnni Reboot both C.3 and C.4.

  • Page 267: Migration Starting With The Peer Groups

    Converting from FT-PNNI to PNNI C.3.1.2 Migration Starting with the Peer Groups This section gives a detailed example of how to migrate a hierarchical FT-PNNI network with a contiguous backbone as shown in Figure C.9 to a PNNI network. In that figure, only the bor- der nodes are shown.
  • Page 268 Converting from FT-PNNI to PNNI PNNI peer group boundary PNNI node PNNI link FT-PNNI peer group boundary FT-PNNI node PG A FT-PNNI link PG C PG B Figure C.15 - C.6 as a Gateway Modify the default protocol of the default domain in C.5 to gateway using the fol- lowing AMI command: conf atmroute domain modify <domain ID>...
  • Page 269 Converting from FT-PNNI to PNNI At this point, C.5 does not have any more FT-PNNI links left. So, modify the default protocol of the default domain in C.5 to pnni using the following AMI command: conf atmroute domain modify <domain ID> pnni Reboot switch C.5.
  • Page 270 Converting from FT-PNNI to PNNI 10. C.2 is the last switch in the peer group to become a gateway. Modify the default protocol of the default domain in C.2 to gateway using the following AMI command: conf atmroute domain modify <domain ID> gateway Upon the reboot of C.2, the last FT-PNNI link (between C.2 and C.4) in the peer group becomes a PNNI link.

  • Page 271: Convert Peer Group A

    Converting from FT-PNNI to PNNI C.3.1.2.1.3 Convert Peer Group A Peer group A is chosen next to be migrated to PNNI. Step 7 from the conversion of peer group C is unnecessary in peer group A’s case because there is only one border node in this peer group, and, therefore, the peer group does not get partitioned during the migration.
  • Page 272 Converting from FT-PNNI to PNNI Create a second PNNI node in A.1 with a node index of 2, the peer group ID set to D, area 3, and level 2 using the following AMI commands: conf atmroute pnni node modify 2 -pgid d -forelevel 2 -forearea 3 conf atmroute domain modify <domain ID>...
  • Page 273 Converting from FT-PNNI to PNNI To quickly restore the connectivity, the rest of the backbone should be migrated to PNNI. Change the peer group ID to D, the level to 2, and area to 3 on the PNNI node in B.1, and change the default protocol of the default domain in B.1 to gateway using the following AMI commands: conf atmroute pnni node modify 1 -pgid d -forelevel 2 -forearea 3...

  • Page 274: Convert Peer Group B

    Converting from FT-PNNI to PNNI PNNI peer group boundary PNNI node PNNI link FT-PNNI peer group boundary FT-PNNI node PG A FT-PNNI link PG B PG C PG D Figure C.18 - A Migrated Backbone C.3.1.2.1.5 Convert Peer Group B Migrate all of the nodes in peer group B using the same method that was used to migrate peer group C in Section C.3.1.2.1.2.

  • Page 275: Migration Of A Hierarchical Ft-Pnni Network With A Non-Contiguous Backbone

    Converting from FT-PNNI to PNNI C.3.2 Migration of a Hierarchical FT-PNNI Network with a Non- Contiguous Backbone This section gives a detailed example of how to migrate a hierarchical FT-PNNI network with a non-contiguous backbone as shown in Figure C.19 to a PNNI network. In this figure, only the border nodes are shown.
  • Page 276 Converting from FT-PNNI to PNNI • The link between B.2 and C.2 in the FT-PNNI network can be placed in a new area (with peer group ID D), which is a higher level area connecting peer groups B and C and acts as a back door entry between the two peer groups. This provides the redundancy that this link offered in the original FT-PNNI network.

  • Page 277: Appendix D Configuring Frameplus Modules

    APPENDIX D Configuring FramePlus Modules FORE Systems’ FramePlus network modules (NMFR-4/DS1A and NMFR-4/E1A) are four- port interfaces that support interworking between ATM and Frame Relay, or ATM and Frame-based UNI (FUNI). All four ports of the DS1 FramePlus Network Module can support fractional DS1 services (n x 64 Kbps) where 1 to 24 contiguous or non-contiguous DS0 channels are mapped to a single ATM port.

  • Page 278: Frame Relay Overview

    Configuring FramePlus Modules D.1 Frame Relay Overview Serving as an interface between user and network equipment, Frame Relay provides a means for statistically multiplexing many logical data channels (or virtual circuits) over a single physical transmission link. Frame Relay is ideal for supporting multiple data streams because it provides flexible and efficient utilization of available bandwidth.

  • Page 279: Configuring The Module Level

    Configuring FramePlus Modules D.2 Configuring the Module Level Before configuring any services or PVCs, you should divide the buffer space between the high and low priority buffers because the PVCs are going to go through these buffers. Cells are read from the high priority buffer first.

  • Page 280: Setting The Thresholds

    Configuring FramePlus Modules D.2.2 Setting the Thresholds After the buffer space is configured, set the various discard thresholds under conf module fram. It is important that you follow the order shown in this section for configuring the thresholds. The NOTE calculation of each threshold is dependent on the previous one.

  • Page 281: Noting The Clp0Ppd Threshold

    Configuring FramePlus Modules D.2.2.1 Noting the CLP0PPD Threshold Each buffer has four different thresholds. The first is for Partial Packet Discard (PPD) on cells with CLP=0. This threshold is automatically set for you as 87.5% of the size of each buffer and cannot be changed.

  • Page 282: Configuring The Clp1Epd Threshold

    Configuring FramePlus Modules D.2.2.2 Configuring the CLP1EPD Threshold Next, calculate the CLP1EPD threshold for each buffer. You have four choices: 25, 37, 50, or 62 percent. For example, you could set the threshold to 50 percent of the remaining buffer size of each buffer, which is 14,336, as shown by the arrow in Figure D.3: 14,336 cells * 0.5 = 7,168 cells 16,384 cells...

  • Page 283: Configuring The Clp0Epd Threshold

    Configuring FramePlus Modules D.2.2.3 Configuring the CLP0EPD Threshold Now, calculate the CLP0EPD threshold for each buffer. You have four choices: 50, 62, 75, or 87 percent. For example, you could set the threshold to 50 percent of the remaining buffer size of each buffer, which is 7,168, as shown by the arrow in Figure D.4.

  • Page 284: Configuring The Clp1Ppd Threshold

    Configuring FramePlus Modules D.2.2.4 Configuring the CLP1PPD Threshold Finally, calculate the CLP1PPD threshold for each buffer. You have four choices: 50, 62, 75, or 87 percent. For example, you could set it to 50 percent of the remaining buffer size, which is 3,584, as shown by the arrow in Figure D.5.

  • Page 285: Profiles

    Configuring FramePlus Modules D.3 Profiles A profile lets you define a set of information that can be applied to a particular service or PVC using a single index number, much in the same way that you can define a set of traffic manage- ment information in a UPC contract and then apply it to a PVC using a single index number.

  • Page 286: Frame Relay Rate Profile

    Configuring FramePlus Modules D.3.3 Frame Relay Rate Profile The Frame Relay rate profile allows you to manage and define rate enforcement and rate adaptation characteristics that can be applied on a per-VC basis to a Frame Relay PVC using the -frrate <index> option under conf fratm pvc new. You can explicitly enable rate enforcement in both the ingress and the egress direction on a FramePlus network module.

  • Page 287: Lmi Profile

    Configuring FramePlus Modules D.3.4 LMI Profile The Link Management Interface (LMI) profile lets you define the version of LMI that is sup- ported by a particular Frame Relay service. The profile can be applied on a per-service basis using the -lmi <index> option under conf fratm new. If you do not want to use LMI, then enter the none option for -flavor under conf fratm new and use this profile when creat- ing your services.

  • Page 288: Configuring Frame Relay

    Configuring FramePlus Modules D.5 Configuring Frame Relay To configure Frame Relay on a FramePlus network module, these steps must be performed in the following order: Choose or create any profiles that you wish to use. Create each service that you need and associate the profile(s) with it. Create each PVC and associate the profile(s) and service(s) with it.

  • Page 289: Creating The Services For Frame Relay

    Configuring FramePlus Modules D.5.2 Creating the Services for Frame Relay Create any Frame Relay services that you want and apply the LMI and service profiles. For example: myswitch::configuration fratm> new <port> <timeslots> [-lmi <index> ] [-service <index> ] [-egress_re (enabled|disabled)] [-status (enabled|disabled)] [-name <name>...

  • Page 290: Creating Frame Relay Pvcs

    Configuring FramePlus Modules D.5.3 Creating Frame Relay PVCs Now that the profiles and services have been created, you can create your PVCs and apply the EPD/PPD, FRF.8, and FRRATE profiles to the PVCs. For example: myswitch::configuration fratm pvc> new <serviceid> <dlci> [-oport <oport> ] [-ovpi <ovpi>...

  • Page 291: Configuring Frame Relay Spvcs

    Configuring FramePlus Modules D.5.4 Configuring Frame Relay SPVCs You can also configure SPVCs (Smart Permanent Virtual Circuits) on a FramePlus network module. An SPVC is a connection that spans multiple switch fabrics and looks like a PVC at the local and remote endpoints with an SVC in the middle. If a link carrying an SPVC goes down and there is an alternate route, then the end switch fabrics of the SPVC automatically reroute the SPVC around the failed link.

  • Page 292: Creating A Frame Relay Pnni Spvc

    Configuring FramePlus Modules D.5.4.2 Creating a Frame Relay PNNI SPVC To create a Frame Relay PNNI SPVC, perform the following steps: Configure the ingress Frame Relay PVC without specifying the -oport, -ovpi, and -ovci parameters. For example: myswitch::configuration fratm pvc> new 4A1:00 100 -epdppd 1 -name spvc_a Display the Frame Relay PVC so you can see what Input Port, Input VPI, and Input VCI values were assigned to the PVC.

  • Page 293: Configuring Funi

    Configuring FramePlus Modules D.6 Configuring FUNI To configure FUNI on a FramePlus network module, these steps must be performed in the fol- lowing order: Change the application key, if necessary. Choose or create any profiles that you wish to use. Create each service that you need and associate the profile(s) with it.

  • Page 294: Creating The Profiles For Funi

    Configuring FramePlus Modules Now you can change the application. When you change the application, the switch deletes all existing services and PVCs that use a different application, and removes them from the CDB (i.e., if you are changing from Frame Relay to FUNI, the switch deletes existing Frame Relay information, and vice versa).

  • Page 295: Creating Funi Services

    Configuring FramePlus Modules D.6.3 Creating FUNI Services Create any FUNI services that you want and apply the FUNI and service profiles. For exam- ple: myswitch::configuration funi> new <port> <timeslots> [-funi <index> ] [-service <index> ] [-status (enabled|disabled)] [-name <name> ] myswitch::configuration funi>...

  • Page 296: D.6.4 Creating Funi Pvcs

    Configuring FramePlus Modules D.6.4 Creating FUNI PVCs Now that the profiles and services have been created, you can create your FUNI PVCs and apply the EPD/PPD profiles to the PVCs. For example: myswitch::configuration funi pvc> new <serviceid> <fvpi> <fvci> [-oport <oport> ] [-ovpi <ovpi>...

  • Page 297: Configuring Funi Spvcs

    Configuring FramePlus Modules D.6.5 Configuring FUNI SPVCs You can also configure SPVCs (Smart Permanent Virtual Circuits) on a FramePlus network module. An SPVC is a connection that spans multiple switch fabrics and looks like a PVC at the local and remote endpoints with an SVC in the middle. If a link carrying an SPVC goes down and there is an alternate route, then the end switch fabrics of the SPVC automatically reroute the SPVC around the failed link.

  • Page 298: Creating A Funi Pnni Spvc

    Configuring FramePlus Modules D.6.5.2 Creating a FUNI PNNI SPVC To create a FUNI PNNI SPVC, perform the following steps: Configure the ingress FUNI PVC without specifying the -oport, -ovpi, and -ovci parameters. For example: myswitch::configuration funi pvc> new 4A1:00 0 40 -epdppd 1 -name spvc_a Display the FUNI PVC so you can see what iport, ivpi, and ivci values were assigned to the PVC.

  • Page 299: Upgrading The Frameplus Network Module Software

    Configuring FramePlus Modules D.7 Upgrading the FramePlus Network Module Software Because the FramePlus network module has an on-board i960 processor, you can upgrade the the network module application software using TFTP. The method for upgrading the network module software is similar to that for upgrading the switch software. myswitch::configuration module fram>...
  • Page 300 Configuring FramePlus Modules D - 24 ForeRunner ATM Switch Network Configuration Manual...
  • Page 301 Acronyms The networking terms in the following list are defined in the Glossary of this manual. Glossary items are listed alphabetically according to the full term. ATM Adaptation Layer Available Bit Rate Address Complete Message Allowable Cell Rate Adaptive Differential Pulse Code Modulation ADPCM ATM-attached Host Functional Group AHFG...
  • Page 302 Acronyms Building Integrated Timing Supply BITS Bayonet-Neill-Concelman Bridge Protocol Data Unit BPDU Bits per Second Bipolar Violation Broadband Terminal Equipment B-TE Broadcast and Unknown Server Connection Admission Control Channel Associated Signaling Connectionless Broadband Data Service CBDS Constant Bit Rate International Telephone and Telegraph Consultative Committee CCITT Common Channel Signaling Cell Delay Variation...
  • Page 303 Acronyms Domain Naming System Digital Standard n (n=0, 1, 1C, 2, and 3) Data Set Ready Data Terminal Equipment Data Terminal Ready Electrically Erasable Programmable Read Only Memory EEPROM Explicit Forward Congestion Indication EFCI Exterior Gateway Protocol Electronics Industries Association Extended Industry Standard Architecture EISA Emulated Local Area Network...
  • Page 304 Acronyms Interface Data Unit Institute of Electrical and Electronics Engineers IEEE Internet Engineering Task Force IETF Interim Local Management Interface ILMI Internet Protocol Internetwork Packet Exchange Intermediate system Integrated Services Digital Network ISDN International Standards Organization International Telecommunication Union Telecommunication ITU-T Interworking Function Interexchange Carriers...
  • Page 305 Acronyms Most Significant Bit Maximum Transmission Unit Network Management Entity Network Management Layer Network Management Station Network-to-Network Interface or Network Node Interface Network Parameter Control Non Return to Zero Non Return to Zero Inverted NRZI Network Service Access Point NSAP National TV Standards Committee NTSC Operation and Maintenance Cell...
  • Page 306 Acronyms Routing Domain Requests For Comment RFCs Radio Frequency Interference Routing Information Protocol Reduced Instruction Set Computer RISC Request To Send Source Address Source MAC Address Service Access Point Segmentation And Reassembly Structured Cabling, or Structured Connectors, or Stick and Click Sustainable Cell Rate Small Computer Systems Interface SCSI...
  • Page 307 Acronyms Shielded Twisted Pair, Spanning Tree Protocol Synchronous Transport Signal Switched Virtual Circuit (or Channel) Switched Virtual Channel Connection SVCC Switched Virtual Path Connection SVPC Transparent Asynchronous Transmitter/Receiver Interface TAXI Transmission Convergence Transmission Control Protocol Transmission Control Protocol/Internet Protocol TCP/IP Tagged Cell Rate Transmission Convergence Sublayer Time Division Multiplexing...
  • Page 308 Acronyms Acronyms - 8 ForeRunner ATM Switch Network Configuration Manual...

  • Page 309: Glossary

    Glossary a 10 Mbps baseband Ethernet specification utilizing twisted-pair cabling (Category 10Base-T - 3, 4, or 5). 10BaseT, which is part of the IEEE 802.3 specification, has a distance limit of approx- imately 100 meters per segment. the IEEE standard for bridging; a MAC layer standard for 802.1d Spanning Tree Bridging - transparently connecting two or more LANs (often called subnetworks) that are running the same protocols and cabling.
  • Page 310 Glossary a method used to resolve higher level protocol addressing Address Resolution Protocol (ARP) - (such as IP) into the appropriate header data required for ATM; i.e., port, VPI, and VCI; also defines the AAL type to be used. a component of network- and desktop-management software, such as SNMP, that Agent - gathers information from MIBs.
  • Page 311 ATM Management Interface (AMI) - trol software (SCS). AMI lets users monitor and change various operating configurations of FORE Systems switches and network module hardware and software, IP connectivity, and SNMP network management. a virtual channel connection (VCC) or a virtual path connection ATM Peer-to-Peer Connection - (VPC) directly established, such as workstation-to-workstation.
  • Page 312 Glossary a FORE program that shows and manipulates ATM ARP entries maintained by the atmarp - given device driver. This is also used to establish PVC connections. The group of functions performed by an ATM- ATM-attached Host Functional Group (AHFG) - attached host that is participating in the MPOA service.
  • Page 313 Glossary an error event on a line in which the normal pattern of alternating Bipolar Violation (BPV) - high (one) and low (zero) signals is disrupted. A bipolar violation is noted when two high sig- nals occur without an intervening low signal, or vice versa. An ATM Forum defined specification for the interface B-ISDN Inter-Carrier Interface (B-ICI) - between public ATM networks to support user services across multiple public carriers.
  • Page 314 Glossary a common digital network suitable Broadband Integrated Services Digital Network (B-ISDN) - for voice, video, and high-speed data services running at rates beginning at 155 Mbps. A protocol used to establish, maintain and release Broadband ISDN User’s Part (B-ISUP) - broadband switched network connections across an SS7/ATM network.
  • Page 315 Glossary an ATM Layer protocol data unit (PDU). The basic unit of information transported in Cell - ATM technology, each 53-byte cell contains a 5-byte header and a 48-byte payload. a quantification of cell clumping for a connection. The cell clump- Cell Delay Variation (CDV) - ing CDV (yk) is defined as the difference between a cell's expected reference arrival time (ck) and its actual arrival time (ak).
  • Page 316 Glossary a form of circuit state signaling in which the circuit state Channel Associated Signaling (CAS) - is indicated by one or more bits of signaling status sent repetitively and associated with that specific circuit. A device that multiplexes many slow speed voice or data conversations onto Channel Bank - high speed link and controls the flow.
  • Page 317 Glossary An ITU-TSS standard for the message for- Common Management Interface Protocol (CMIP) - mats and procedures used to exchange management information in order to operate, adminis- ter maintain and provision a network. The connection of transmission channels similar to a chain. Concatenation - a communications device that offers the ability to concentrate many lower- Concentrator -...
  • Page 318 Glossary a FORE program that monitors and changes the state of ports on a ForeRunner switch cport - running asxd. a mapping between two channels or paths at a network device. Cross Connection - equipment that is on the customer side of the point of Customer Premise Equipment (CPE) - demarcation, as opposed to equipment that is on a carrier side.
  • Page 319 Glossary an RS232 modem interface control signal (sent from the DTE to Data Terminal Ready (DTR) - the modem on pin 20) which indicates that the DTE is ready for data transmission and which requests that the modem be connected to the telephone circuit. a packet of information used in a connectionless network service that is routed to Datagram - its destination using an address included in the datagram’s header.
  • Page 320 Glossary the distributed name and address mechanism used in the Domain Naming System (DNS) - Internet. Two way communication. Duplex - a generic phrase used in the full names of several protocols, all commonly used to allow DXI - a pair of DCE and DTE devices to share the implementation of a particular WAN protocol. The protocols define the packet formats used to transport data between DCE and DTE devices.
  • Page 321 Glossary a system where an ATM connection is terminated or initiated (an originat- End System (ES) - ing end system initiates the connection; a terminating end system terminates the connection). This identifier distinguishes multiple nodes at the same level in End System Identifier (ESI) - case the lower level peer group is partitioned.
  • Page 322 The way in which information is controlled in a network to prevent loss of data Flow Control - when the receiving buffer is near its capacity. a FORE Systems routing and signalling protocol that uses pri- ForeThought PNNI (FT-PNNI) - vate ATM (NSAP) addresses; a precursor to ATM Forum PNNI (see PNNI).
  • Page 323 Glossary a variable length group of data bits with a specific format containing flags at the Frame - beginning and end to provide demarcation. In bit-oriented protocols, a 16-bit field that contains transmis- Frame Check Sequence (FCS) - sion error checking information, usually appended to the end of the frame. a fast packet switching protocol based on the LAPD protocol of ISDN that per- Frame Relay - forms routing and transfer with less overhead processing than X.25.
  • Page 324 Glossary ANSI standard that extends the computer bus High Performance Parallel Interface (HIPPI) - over fairly short distances at speeds of 800 and 1600 Mbps. a serial communications connection that operates at speeds High-Speed Serial Interface (HSSI) - of up to 1.544 Mbps. In a network, the primary or controlling computer in a multiple computer installation.
  • Page 325 Glossary the standard that specifies the use of the Simple Interim Local Management Interface (ILMI) - Network Management Protocol (SNMP) and an ATM management information base (MIB) to provide network status and configuration information. a system that provides forwarding functions or relaying functions or Intermediate System (IS) - both for a specific ATM connection.
  • Page 326 Glossary Network mask values are used to identify the network portion and the host portion of the address. Default network masks are as follows: Class A - 255.0.0.0 Class B - 255.255.0.0 Class C - 255.255.255.0 Subnet masking is used when a portion of the host ID is used to identify a subnetwork. For example, if a portion of a Class B network address is used for a subnetwork, the mask could be set as 255.255.255.0.
  • Page 327 Glossary Wide-area digital transmission scheme used predominantly in Japan that carries data at a J2 - rate of 6.312 Mbps. analog communication line distortion caused by variations of a signal from its reference Jitter - timing position. An ISO Standards group that defines how to com- Joint Photographic Experts Group (JPEG) - press still pictures.
  • Page 328 Glossary the information transferred between corresponding entities on behalf of the Layer User Data - upper layer or layer management entities for which they are providing services. a FORE program that implements both the LAN Emulation Server (LES) and the Broad- le - cast/Unknown Server (BUS).
  • Page 329 Glossary protocol developed by the IEEE 802 committee for data-link-layer Logical Link Control (LLC) - transmission control; the upper sublayer of the IEEE Layer 2 (OSI) protocol that complements the MAC protocol; IEEE standard 802.2; includes end-system addressing and error checking. a troubleshooting technique that returns a transmitted signal to its source so that Loopback - the signal can be analyzed for errors.
  • Page 330 Glossary fiber optic connector that joins fiber to the FDDI controller. Media Interface Connector (MIC) - message identifier used to associate ATM cells that carry segments Message Identifier (MID) - from the same higher layer packet. an ATM Layer Management (LM) process that manages different types of sig- Metasignalling - nalling and possibly semipermanent virtual channels (VCs), including the assignment, removal, and checking of VCs.
  • Page 331 Glossary user access in which more than one terminal equipment (TE) is supported Multipoint Access - by a single network termination. a collection of associated ATM VC or VP links, and their Multipoint-to-Multipoint Connection - associated endpoint nodes, with the following properties: 1.
  • Page 332 Glossary Duplicated network equipment and/or data which can provide a Network Redundancy - backup in case of network failures. OSI generic standard for a network address consisting Network Service Access Point (NSAP) - of 20 octets. ATM has specified E.164 for public network addressing and the NSAP address structure for private network addresses.
  • Page 333 Glossary The optical counterpart of STS-n (the basic rate of 51.84 Mbps on Optical Carrier level-n (OC-n) - which SONET is based is referred to as OC-1 or STS-1). Part of RFC 1483. A three-octet field in the SubNet- Organizationally Unique Identifier (OUI) - work Attachment Point (SNAP) header, identifying an organization which administers the meaning of the following two octet Protocol Identifier (PID) field in the SNAP header.
  • Page 334 Glossary A Virtual Channel Connection (VCC) is an Permanent Virtual Channel Connection (PVCC) - ATM connection where switching is performed on the VPI/VCI fields of each cell. A Perma- nent VCC is one which is provisioned through some network management function and left up indefinitely.
  • Page 335 Glossary a collection of associated ATM VC or VP links, with associated Point-to-Multipoint Connection - endpoint nodes, with the following properties: 1. One ATM link, called the Root Link, serves as the root in a simple tree topology. When the Root node sends information, all of the remaining nodes on the connection, called Leaf nodes, receive copies of the information.
  • Page 336 Glossary the information exchanged between corresponding entities Protocol Control Information - using a lower layer connection to coordinate their joint operation. a unit of data specified in a layer protocol and consisting of protocol Protocol Data Unit (PDU) - control information and layer user data. the process in which one system acts for another system to answer protocol requests.
  • Page 337 Glossary an RS-232 modem interface signal (sent from the DTE to the modem Request To Send (RTS) - on pin 4) which indicates that the DTE has data to transmit. IETF documents suggesting protocols and policies of the Requests For Comment (RFCs) - Internet, inviting comments as to the quality and validity of those policies.
  • Page 338 Glossary a connection established via a service order or via network man- Semipermanent Connection - agement. A protocol used to run IP over serial lines, such as telephone circuits or Serial Line IP (SLIP) - RS-232 cables, interconnecting two systems. the point at which an entity of a layer provides services to its LM Service Access Point (SAP) - entity or to an entity of the next higher layer.
  • Page 339 Glossary FORE Systems’ proprietary signalling Simple Protocol for ATM Network Signalling (SPANS) - protocol used for establishing SVCs between FORE Systems equipment. Fiber optic cable in which the signal or light propagates in a single Single Mode Fiber (SMF) - mode or path.
  • Page 340 Glossary see Stick and Click. Structured Connectors (SC) - a logical subdivision of a layer. Sublayer - a specially reserved variant of IEEE 802.2 encoding SubNetwork Access Protocol (SNAP) - SNAP indicates to look further into the packet where it will fine a Type field. the interface between an SMDS end user’s CPE and the Subscriber Network Interface (SNI) - network directly serving the end user, supported by either a DS1 or DS3 access arrangement.
  • Page 341 Glossary the payload field plus a little overhead of a basic Synchronous Payload Envelope (SPE) - SONET signal. a transport and switching method that depends on infor- Synchronous Transfer Mode (STM) - mation occurring in regular, fixed patterns with respect to a reference such as a frame pattern. a SONET electrical signal rate.
  • Page 342 Glossary a program that displays the topology of a FORE Systems ATM network. An topology - updated topology can be periodically re-displayed by use of the interval command option. the calls being sent and received over a communications network. Also, the packets Traffic - that are sent on a data network.
  • Page 343 Glossary Layer Four of the OSI reference model that is responsible for maintaining Transport Layer - reliable end-to-end communications across the network. a program interrupt mechanism that automatically updates the state of the network to trap - remote network management hosts. The SNMP agent on the switch supports these SNMP traps.
  • Page 344 Glossary ITU-T standard describing a synchronous, physical layer protocol used for communica- V.35 - tions between a network access device and a packet network. V.35 is most commonly used in the United States and Europe, and is recommended for speeds up to 48 Kbps. a type of traffic that, when sent over a network, is tolerant of delays Variable Bit Rate (VBR) - and changes in the amount of bandwidth it is allocated (e.g., data applications).
  • Page 345 Glossary a private data communications network built on public Virtual Private Data Network (VPDN) - switching and transport facilities rather than dedicated leased facilities such as T1s. a private voice communications network built on public switch- Virtual Private Network (VPN) - ing and transport facilities rather than dedicated leased facilities such as T1s.
  • Page 346 Glossary Glossary - 38 ForeRunner ATM Switch Network Configuration Manual...
  • Page 347 Index BUS ....... . . 3 - 3 ABR ....... 1 - 35 address registration .
  • Page 348 Index data encryption ..... . 8 - 5 flooding protocol ..... 6 - 2 database exchange protocol .
  • Page 349 Index Interim Local Management Interface LES ....... . . 3 - 3 (ILMI) .
  • Page 350 Index peer group leader (PGL) ....6 - 3 node secret file ....8 - 5 permanent virtual channel passcode .
  • Page 351 Index terminating paths ..... 1 - 6 virtual path ......1 - 3 creating .
  • Page 352 Index Index - 6 ForeRunner ATM Switch Network Configuration Manual...

Table of Contents