Cabletron Systems 04-0053-01 User Manual

SmartSwitch ATM Switch User Guide

35 Industrial Way
Rochester, NH 03866
USA
[phone]

Part Number 04-0053-01 Rev. A
Order Number 9033002

NOTICE

Cabletron Systems reserves the right to make changes in specifications and other information contained in this
document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any
such changes have been made. The hardware, firmware, and software described in this manual are subject to change
without notice.

IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY INCIDENT AL, INDIRECT, SPECIAL,
OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, LOST PROFITS)
ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF
CABLETRON SYSTEMS HAS BEEN ADVISED OF, KNOWN, OR SHOULD HAVE KNOWN, THE
POSSIBILITY OF SUCH DAMAGES.

Copyright 1998 - 99 by Cabletron Systems, Inc., P.O. Box 5005, Rochester, NH 03866-5005
All Rights Reserved

Printed in the United States of America
SmartSwitch ATM Switch User Guide
Part Number 04-0053-01 Rev. A
Order Number: 9033002
SmartSwitch, SPECTRUM, LANVIEW, MicroMMAC, and BRIM are registered trademarks and Element Manager,

EPIM, EPIMA, EPIM-F1, EPIM-F2, EPIM-F3, EPIM-T, EPIM-X, FOT-F, FOT-F3, HubSTACK, SEH, SEHI, and
TMS-3 are tradem arks of Cabletr on Systems, Inc . All other product names mentioned in this manual may be
trademarks or registered trademarks of their respective companies.

ii SmartSwitch ATM Switch User Guide

FCC CLASS A NOTICE

This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation.

Note This equipment has been tested and found to comply with the limits for a Class A

digital device, pursuant to Part 15 of the FCC rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment uses, generates, and can
radiate radio frequency energy and if not installed in accordance with the
appropriate Setup and Installation Guide, may cause harmful interference to rad io
communications. Operation of this equipment in a residential area is likely to
cause interference in which case the user will be required to correct the
interference at his own expense.

Caution Changes or modifications made to this device which are not expr essly approved

by the party responsible for compliance could void the user’s authority to
operate the equipment.

DOC CLASS A NOTICE

This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the
Radio Interference Regulations of the Canadian Department of Communications.

Le present appareil numerique n’emet pas de bruits radioelectriques depassant les limites applicables aux appareils
numeriques de la class A prescrites dans le Reglement sur le brou illage radioelectrique edicte par le ministere des
Communications du Canada.

SmartSwitch ATM Switch User Guide iii

DECLARATION OF CONFORMITY
ADDENDUM

Application of Council Directive(s):

89/336/EEC
73/23/EEC

Manufacturer’s Name:
Manufacturer’s Address:

Product Name:
European Representative Name:
European Representative Address:

Conformance to Directive(s)/Product Standards:

Equipment Type/Environment:

Cabletron Systems, Inc.
35 Industrial Way

P. O. Box 5005
Rochester, NH 03866

SmartSwitch ATM switches
Mr. J. Solari
Cabletron Systems, Limited

Nexus House, Newbury Business Park
London Road, Newbury
Berkshire RG13 2PZ, England

EC Directive 89/336/EEC
EC Directive 73/23/EEC
EN 55022
EN 50082-1
EN 60950

Networking Equipment, for use in a Commerci al or Light
Industrial Environment.

We the undersigned, hereby declare, under our sole respo nsi bility, that the equipment packa ged with this
notice conforms to the above directives.

Manufacturer:

Legal Repersentative in Europe:

iv SmartSwitch ATM Switch User Guide

Full Name:
Title:
Location:

Full Name:
Title:
Location:

Mr. Ronald Fotino
Principal Compliance Engineer
Rochester, NH. U.S.A.

Mr. J. Solari
Managing Director - E.M.E.A.
Newbury, Berkshire, England

SAFETY INFORMATION
CLASS 1 LASER TRANSCEIVERS

The connectors on I/O modules contai ning the part numbers IOM-29-4-MIX, I OM-29-4-IR, IOM-29-4-LR, IOM-39 -1
and IOM-39-1-LR use Class 1 Laser transceivers. Read the following safety information before installing or oper ating
one of these modules.

The Class 1 Laser transceivers use an optical feedback loop to main tain Class 1 operation limits. This control loop
eliminates the need for maintenance checks or adjustments. The output is factory set, and does not allow any user
adjustment. Class 1 Laser transceivers comply with the following safety standards:

• 21 CFR 1040.10 and 1040.11 U. S. Department of Health and Human Services (FDA).

• IEC Publication 825 (International Electrotechnical Commission).

• CENELEC EN 60825 (European Committee for Electrotechnical Standardization).

When operating within their performance limitations, laser transceiver output meets the Class 1 accessible emission
limit of all three standards. Class 1 levels of laser radiation are not considered hazardous.

LASER RADIATION AND CONNECTORS

When the connector is in place, all laser radiation remains within the fiber. The maximum amount of radiant power
exiting the fiber (under normal conditions) is -12.6dBm or 55x10

Removing the optical connector from the transceiver a llows laser r adiation to emit d irectly f rom the o ptical po rt. Th e
maximum radiance from the optical port (under worst case conditions) is 0.8 W cm

Do not use optical instruments to view the laser output. The use of optical instruments to view laser output increases
eye hazard. When viewing the output optical port, you must remove power from the network adapter.

-6

watts.

-2

or 8x103 W m-2 sr-1.

SmartSwitch ATM Switch User Guide v

FIBER OPTIC PROTECTIVE CAPS

Warning READ BEFORE REMOVING FIBER OPTIC PROTECTIVE CAPS.

Cable assemblies and MMF/SMF ports are shipped with protective caps to prevent contamination. To avoid
contamination, replace port caps on all fiber optic devices when not in use.

Cable assemblies and MMF/SMF ports that become contaminated may experience signal loss or difficulty inserting
and removing cable assemblies from MMF/SMF ports.

Contamination can be removed from cable assemblies by:

1. Blowing surfaces with canned duster (Chemtronics p/n ES1270 or equivalent).

2. Using a fiber port cleaning swab (Alcoa Fujikura LTS p/n ACT-01 or equivalent) saturated with

optical-grade isopropyl alcohol, gently wipe the end surface of ferrules first; then wipe down the
sides of both ferrules.

3. Blow ferrule surfaces dry with canned duster.

Contamination can be removed from MMF/SMF ports by:

1. Using the extension tube supplied with canned duster, blow into the optical port, being careful not

to allow the extension tube to touch the bottom of the optical port.

2. R econnect cable and check f or proper mating. If pr oblems remain, gently wipe out optical port with

a DRY fiber port cleaning swab and repeat step 1.

Warning T o avoid contamination, replace port caps on all fiber optic devices when not

in use.

vi SmartSwitch ATM Switch User Guide

REGULATORY COMPLIANCE SUMMARY

SAFETY

SmartSwitch ATM switches meet the safety requirement s of UL 1950 , CSA C22.2 No. 950, EN 6095 0, IEC 950, and
73/23/EEC.

EMC

SmartSwitch ATM switches meet the EMC requiremen t s of F CC Part 15, EN 55022, CSA C108.8, VCCI V-3/93.01,
EN 50082-1, and 89/336/EEC.

SmartSwitch ATM Switch User Guide vii

REVISION HISTORY

Document Name: SmartSwitch ATM Switch User Guide
Document Part Number: 04-0053-01 Rev. A
Document Order Number: 9033002

Author: Bruce Jordan
Editor: Ayesha Maqsood
Illustrator: Mike Fornalski

Date Revision Description

>ÀV…Ê£™™™ " Initial release

viii SmartSwitch ATM Switch User Guide

Table of Contents

TABLE OF CONTENTS

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Contents of the User Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.2 SmartSwitch ATM Switch Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2 IP Over ATM and LANE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Creating an IP over ATM VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1.1 Default ATM Addressing for IP over ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.2 Creating an Emulated LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.2.1 ATM Addressing for LAN Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

2.2.2 ELANs Across Multiple Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

2.2.3 Switch Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.2.4 Distributed LANE Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.2.5 ELAN Join Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.2.6 LANE Over WAN Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

2.2.7 Using LNNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

3 PNNI Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 PNNI Node Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1.1 Default PNNI Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2 Multi-level PNNI Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.2.1 Connecting Multiple Peer Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.2.2 Physical Connections Between Peer Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3 Managing Parallel PNNI Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.3.1 Aggregation Tokens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

3.3.2 PNNI Link Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

4 Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Additional Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.2 IISP Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.2.1 IISP Routing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.2.2 IISP Link Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

4.3 UNI Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4.3.1 UNI Link Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

4.4 Route Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4.4.1 Administrative Weights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4.4.2 Creating Route Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4.5 IP Routing for Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

SmartSwitch ATM User Guide ix

Table of Contents

5 Virtual Ports and Static Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

5.1 PVC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

5.1.1 Point-to-Point PVCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

5.1.2 Point-to-Multipoint PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

5.1.3 Connecting to Local Switch Client Through a PVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

5.2 PVP Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

5.2.1 Connecting PVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7

5.3 Virtual Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7

5.3.1 Creating Virtual Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8

5.4 Soft PVC and PVP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11

5.4.1 Soft PVC and Soft PVP differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 1 1

5.4.2 Making Soft PVC and PVP Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12

5.4.3 Creating a soft PVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12

5.4.4 Creating a Soft PVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15

6 Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.1 Traffic Management Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.1.1 Traffic Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.1.2 Call Admission Control Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

6.1.3 Queue Buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

6.1.4 EFCI, EPD, and RM Cell Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

7 Firmware Upgrades and Bootline Commands . . . . . . . . . . . . . . . . . . . . . . .7-1

7.1 Update Firmware Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

7.2 Bootline Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

7.2.1 Accessing the Bootline Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

7.2.2 Bootline Commands Explanations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

7.2.3 Upgrading Boot Load firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6

7.2.4 Upgrading POST Diagnostic firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7

7.2.5 Upgrading Switch Operating firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

8 ATM Filtering and Clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

8.1 Port ATM Address Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

8.1.1 Creating ATM Address Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

8.1.2 How ATM Address Filters Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

8.1.3 ATM Address Filter Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

8.1.4 Filter Considerations Regarding LANE and IP over ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

8.2 Port Clock Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

8.2.1 Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

9.1 Troubleshooting IP over ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

9.2 Troubleshooting LAN Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

9.3 Troubleshooting PNNI Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

9.3.1 Switches in Same Peer Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

9.3.2 Switches in Different Peer Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

x SmartSwit ch ATM User Gui de

Table of Contents

9.4 Troubleshooting Congestion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

9.4.1 Diagnosing Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

9.4.2 Global Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

9.4.3 Port Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

9.5 Events and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

9.5.1 Event Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

9.5.2 Viewing Events and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

9.5.3 Deleting Events and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

9.6 Saving Core Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

A Agent Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

A.1 MIB, SMI, MIB Files and Internet MIB Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

A.1.1 CSI ZeitNet Proprietary MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

A.1.2 Relation Between Object Identifier and the Represented Value . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

A.1.3 Supported protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4

A.1.4 Supported SMI Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4

A.1.5 CSI ZeitNet Proprietary MIB Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4

A.1.6 ATM SmartSwitch MIB Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-6

A.1.7 MIB Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-6

A.2 Managing an ATM SmartSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-7

A.2.1 Console Commands that Affect the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-7

A.2.2 Default Community Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-8

B Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

B.1 Telephone Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

B.2 FAX Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

B.3 Electronic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

B.4 Placing A Support Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

B.5 Hardware Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

B.6 Software Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

B.7 Repair Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1

SmartSwitch ATM User Guide xi

Table of Contents

xii SmartSwitch ATM User Guide

List of Figures

LIST OF FIGURES

Figure 2-1 Single PVP connection between clients and LANE services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Figure 2-2 Multiple PVP connection between clients and LANE services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Figure 2-3 LNNI Redundant LECSs on same network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Figure 2-4 LNNI call set up load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Figure 2-5 How LNNI handles ELAN join requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Figure 3-1 Physical connectivity for multi-peer group example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Figure 3-2 Logical representation of connectivity between groups A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

Figure 3-3 Adding a third PNNI node for next level connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Figure 3-4 Aggregation token values and parallel links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Figure 4-1 IISP route across PNNI domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Figure 4-2 Routes needed for a second IISP switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Figure 4-3 IP routing through SW1 for connectivity to the Ethernet network. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Figure 5-1 Terminating PVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Figure 5-2 Soft PVC across PNNI network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 -12

Figure 5-3 Soft PVC heals (is rerouted) to bypass broken link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Figure 7-1 Memory locations affected by the bootline commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Figure A-1 Internet MIB hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Figure A-2 CSI ZeitNet Private MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

Figure A-3 Cabletron ATM SmartSwitch object identifier example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4

SmartSwitch ATM User Guide xiii

List of Figures

xiv SmartSwitch ATM User Guide

List of Tables

LIST OF TABLES

Table 2-1 ELAN Join Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Table 6-1 Traffic descriptor type number explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Table 7-1 Bootline commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Table 9-1 Settings for Class of Service Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Table A-1 CSI Zeitnet proprietary MIB groupings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4

SmartSwitch ATM User Guide xv

List of Tables

xvi SmartSwitch ATM User Guide

1 INTRODUCTION

Welcome to the SmartSwitch ATM User Guide. This manual provides instructions and information about switch use,
maintenance, and problem solving for all SmartSwitch ATM switches. These include

• SmartSwitch 2500 Workgroup and Backbone ATM switches

• SmartSwitch 6A000 ATM switch modules

• SmartSwitch 9A100 ATM switch modules

• SmartSwitch 6500 ATM switch

Note For installation instructions and initial set up procedu res for your particular

SmartSwitch ATM switch, see the appropriate SmartSwitch ATM Switch
Installation and Setup Guide.

1.1 CONTENTS OF THE USER GUIDE

The SmartSwitch ATM User Guide provides instructions and examples on using the SmartSwitch ATM switch
features. By reading this manual you will learn how to perform the fol lowing operations:

• Creating and managing IP over ATM VLANs

• Creating and managing ELANS

• Using distributed LANE servers

• Configuring LNNI for LANE redundancy and load sharing through

• Creating and managing multi-level PNNI network topologies

• Adding routes (PNNI, IISP, UNI, and routes between ATM and Ethernet networks)

• Creating PVC and PVP connections

• Creating soft PVCs and soft PVPs

• Creating and using virtual ports

• Creating traffi c descript or s

• Managing bandwidth, switch traffic, and congestion

• Upgrading switch firmware

• Configuring ATM address filters

• Configuring network clocking

• Troubleshooting VLANs, ELANs, PNNI topologies, and traffic congestion problems

Note For detailed descriptions of individual SmartSwitch A T M console commands, see

the SmartSwitch ATM Reference Manual.

SmartSwitch ATM User Guide 1-1

SmartSwitch ATM Switch Differences Introduction

1.2 SMARTSWITCH ATM SWITCH DIFFERENCES

Not all features are supported on all SmartSwitch ATM switches. The SmartSwitch 6500 has capabilities that are not
supported by the other SmartSwitch ATM switches. The following is a list of capabilities supported by the
SmartSwitch 6500 only:

• PVPs

• Soft PVPs (all SmartSwitch ATM switches support soft PVCs)

• BUS logical multicasting

• Switch redundancy and automatic fail-over

• Network cloc king

Note It is clearly stated within the text of this User Guide whether a particular feature

is supported only by the SmartSwitch 6500.

1-2 SmartSwitch ATM User Guide

2 IP OVER ATM AND LANE

This chapter describes working with the SmartSwitch ATM switch IP over ATM VLAN and emulated LAN
capabilities. At the end of this chapter you will be able to use your SmartSwitch ATM switch to:

• Create an IP over ATM VLAN

• Create an emulated Ethernet LAN (LANE)

2.1 CREATING AN IP OVER ATM VLAN

This section describes implementing IP over ATM on your SmartSwitch ATM switch. The following assumptions are
made:

• The SmartSwitch ATM switch will have a client on the IP over ATM VLAN

• The ARP server will reside on the switch and co rrespond to the address of the switch client

• All end nodes (computers, edge devices, and so on) support Switched Virtual Circuits (SVCs)

1. Log into the switch, either through the terminal port or through the Ethernet interface by telnet.

2. Create a client on the switch and assign it as the ARP server for the VLAN.

SmartSwitch # add ipatmclient
ClientNumber(0) : 1
ServerType(NONE) : local
ServerAddress() :
IPAddress() : 90.1.1.1
NetMask(255.0.0.0) : 255.255.255.0
MTU(9180) :
SmartSwitch #

— the ARP server is assigned to the switch client

— IP address is for example only
— subnet mask is for example only

The example above creates a client on the switch, designates the client as the ARP server for the VLAN
(

ServerType = local), and assigns the client an IP address and subnet mask.

Note The command add ipatmclient always prompts you with a subnet mask that is

appropriate for the IP address. However, if necessary, you can change the subnet
mask to correspond to the strategy employed within your networks.

Caution Never create an IP over ATM VLAN (or an IP over A TM client) with the same

subnet as the ATM SmartSwitch Ethernet port.

SmartSwitch ATM User Guide 2-1

Creating an IP over ATM VLAN IP Over ATM and LANE

3. Enter the show client command to m a ke sure the client is operational and to obtain the 20-byte

ATM address of the ARP server. For instance, if you used the client number (client 1) from the
example in step 2, enter the following command:

SmartSwitch # show client 1
IP/ATM Client 1
============================================================================
Client State : Operational
Client Address : 39:00:00:00:00:00:00:00:00:00:14:41:80:00:00:5A:01:01:01:00
Server : is local
Server Connection : Established
MTU : 9180
IP Address : 90.1.1.1
IP NetMask : 255.255.255.0
SmartSwitch #

4. Physically connect your end nodes and edge devices to the ATM SmartSwitch ports.

Note Your end nodes do not need to be directly attached to the switch that co ntains th e

ARP server. For examp le, an end station is connected to an ATM SmartSwitch that
is connected through a route to the switch containing the ARP server. No special
configuration is needed for this end station to participate in the VLAN because the
end station automatically finds its path across the route to the ARP server and the
other VLAN members.

5. Configure the ATM interface or adapter for end nodes and edge devices. Typically, configuration

consists of designating IP over ATM as the connection type, assigning the device an IP address, and
specifying the 20-byte ATM address of the ARP server (the switch’s client address). For details on
the ATM SmartSwitch automatic addressing scheme for IP over ATM, see Section 2.1.1.

6. As your end devices are configured and started, they register with the ARP server. You can test

whether your IP over ATM VLAN is func tional by pinging from one e nd device to another.

T o make certain that all end devices are registered with the ARP server, you can inspect the switch’s ARP table using
the

show ipatmarp command. For example, if three end devices with IP addresses 90.1.1.2, 90.1.1.3, and 90.1.1.4 are

added to the VLAN, the following ARP table entries should exist:

SmartSwitch # show ipatmarp
ClientNumber(ALL) :
IP/ATM Server 2 ARP Table
IP Address ATM Address
============================================================================

90.1.1.2 39:00:00:00:00:00:00:00:00:00:14:41:80:00:00:5A:01:01:02:00
IP/ATM Server 3 ARP Table
IP Address ATM Address
============================================================================

90.1.1.3 39:00:00:00:00:00:00:00:00:00:14:41:80:00:00:5A:01:01:03:00
IP/ATM Server 4 ARP Table
IP Address ATM Address
============================================================================

90.1.1.4 39:00:00:00:00:00:00:00:00:00:14:41:80:00:00:5A:01:01:04:00
SmartSwitch #

2-2 SmartSwitch ATM User Guide

IP Over ATM and LANE Creating an IP over ATM VLAN

Note If configured devices fail to join the VLAN, see C hapter 4, "Routing." Section 4.3.

Also, see Chapter 9, "Troubleshooting."

2.1.1 Default ATM Addressing for IP over ATM

ATM SmartSwitches provide a default format for ATM addresses used by IP over ATM.

Note SmartSwitch 2500 family ATM switches and SmartSwitch 6500 switches use

different methods for producing the default netprefix.

Default Netprefix for SmartSwitch 2500 Family Switches

The default

netprefix

is constructed from

39 + nine zero bytes + last three bytes of CPU MAC address

For example, if the chassis MAC address =
Default netprefix =

39:00:00:00:00:00:00:00:00:00:14:41:80

00:20:D4:14:41:80

, then

Default Netprefix for SmartSwitch 6500

The default

netprefix

39 + nine zero bytes + last three bytes of chassis MAC address

For example, if the chassis MAC address =
Default netprefix =

is constructed from

00:00:1D:80:A3:34

39:00:00:00:00:00:00:00:00:00:80:A3:34

, then

Default IP Over ATM Local Client Address

The default

Local client

netprefix + two zero bytes + client IP address (in hexadecimal) + trailing zero byte

For example
netprefix =

39:00:00:00:00:00:00:00:00:00:A3:87:0B

address is constructed from

chassis MAC address =
client IP address =

00:00:1D:A3:87:0B

90.1.1.1 (5A.01.01.01 in hexadecimal)

then,
IP over ATM client address =

39:00:00:00:00:00:00:00:00:00:A3:87:0B:00:00:5A:01:01:01:00

SmartSwitch ATM User Guide 2-3

Creating an Emulated LAN IP Over ATM and LANE

2.2 CREATING AN EMULATED LAN

This section describes the steps for implementing an Emulated LAN (ELAN) on your SmartSwitch ATM switch.

Note If LANE services are to be reached through a virtual port on an ATM

SmartSwitch, this switch must be a SmartS witch 6500. Only the SmartSwitch
6500 supports logical multicasting. If LANE services are NOT reached through a
virtual port, LANE services can reside on any ATM SmartSwitch.

The following assumptions are made:

• The ATM SmartSwitch will contain a client on the ELAN

• All end nodes (computer s, edge devices, other switches, and so on) support the Well Known LECS

Address or the Anycast Address or can obtain the address of the LECS using ILMI

• All end nodes support Switched Virtual Circuits (SVCs)

Note An ELAN comes pre-configured on all SmartSwitch ATM switches. The ELAN

name is “ELAN000.” T o use this ELAN, start the LECS, configu re your end nodes
and edge devices to use ELAN name ELAN000, and then plug them into the ATM
SmartSwitch.

1. Enter the start lecs command to activate LANE server services on this ATM SmartSwitch.

SmartSwitch # start lecs
NOTICE - 'LECS' ***** LECS started *****
SmartSwitch #

— This assumes the LES/BUS is running (default)

2. Create an ELAN on your ATM SmartSwitch by executing the add elan command. The following

is an example.

SmartSwitch # add elan
ELANNumber(0) : 1
ELANName(ELAN001): Marketing
ConnectMethod(SVC):
ELANType(802.3)
Multipoint(YES) :
MTU(1516) :
ErrorLogEnable(NO) :
MinimumTDEnable(NO) :
Distribute(PROXY) :
SmartSwitch #

3. Use the add laneclient command to create a client for the switch on the ELAN:

SmartSwitch # add laneclient
ClientNumber(0) :1
LanName(ELAN001) : Marketing
ServerType(LECS) :
ServerAddress()
IPAddress() : 90.1.1.1
NetMask(255.0.0.0): 255.255.255.0
MTU(1516) :
SmartSwitch #

— 1 is used instead of the default, (0)
— ELAN is named Marketing instead of the default, (ELAN001)

—The default (Ethernet) is used

— Take the default
— Take the default

— One is used instead of the default, (0)
— ELAN name is Marketing, not the default, (ELAN001)

— No LANE server address is specified; see note below
— IP address and subnet mask are specified only as examples

2-4 SmartSwitch ATM User Guide

IP Over ATM and LANE Creating an Emulated LAN

Note When you create a client, it automatically finds the LECS address using ILMI.

Note The command add laneclient always prompts you with a subnet mask that is

appropriate for the IP address. However, if necessary, you can change the subnet
mask to correspond to the strategy employed within your networks.

As the local client joins the ELAN, the following messages are sent to the Event Log (see Chapter 9,
"Troubleshooting." Section 9.5):

NOTICE - 'ZLESSRV' LES Join 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:
14:41:82:00
NOTICE - 'ZLESSRV' BUS Connect 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:
14:41:82:00

Caution Never create an ELAN (or ELAN client) with the same subnet as the ATM

SmartSwitch’s Ethernet port.

4. Enter the show client command verify th at th e client is operational.

SmartSwitch # show client 1
LANE Client 1
============================================================================
Client State : Operational
Client Address : 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:81:00
LAN Name : Marketing
LECS Addr Source : ILMI
LECS Address : 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:80:01
LES Address : 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:82:02
LAN Type : 802.3
MTU : 1516
IP Address : 90.1.1.1
IP NetMask : 255.255.255.0
SmartSwitch #

Note While creating an ELAN client for the switch is not absolutely necessary, it does

provide management connect i v it y with the switch over its ATM ports (ins tead of
the Ethernet port). See Chapter 4, "Routing." Section 4.5 for information about
how to reach switches not directly connected to the Ethernet network.

5. Physically connect your end nodes and edge devices to the ATM SmartSwitch ports.

6. Configure the A TM interface or adapter for all end nodes and edge devices. T ypically, configuration

consists of specifying LAN Emulation as the connection type, assigning the device an IP address that
corresponds to the subnet of the switch’s client, and indicating that you want the device to either

SmartSwitch ATM User Guide 2-5

Creating an Emulated LAN IP Over ATM and LANE

acquire the LECS address through ILMI or use the Well Known Address as the address for the
LECS. For details on the ATM SmartSwitch automatic addr essing scheme for LANE, see
Section 2.2.1.

7. As each end device registers with the LES and BUS, messages are sent to the event log of the ATM

SmartSwitch containing the LECS. You can check connectivity by pinging between end nodes.

Note If configured devices fail to join the ELAN, see Chapter 4, "Routing." Section 4.3.

Also, see Chapter 9, "Troubleshooting."

Your ELAN is now operational. Additional ELANs can be created in the same way.

Note While it is possible for a single ELAN on an ATM SmartSwitch to support

multiple subnet s, in general, s witch performance i s best (and m anagement easiest)
when the “One-subnet-per-ELAN” rule is observed.

2.2.1 ATM Addressing for LAN Emulation

All ATM SmartSwitches prov ide default formats for ATM addresses used by LAN emulation entities (local client,
LECS, LES, and BUS). The SmartSwitch 2500 family of ATM switches and the SmartSwitch 6500 use different
methods for constructing these default addresses.

SmartSwitch 2500 Family Default LANE Addressing

The

netprefix

39 + nine zero bytes + last three bytes of CPU MAC address

For example, the chassis MAC address =
then
default netprefix =

The

local client

netprefix + CPU MAC address with last byte summed with the client number + zero selector byte

For example
netprefix =

is constructed from:

00:20:14:41:80

39:00:00:00:00:00:00:00:00:00:14:41:80

address is constructed from:

39:00:00:00:00:00:00:00:00:00:14:41:80

,

CPU MAC address =
client number =

00:20:D4:14:41:80

5

then,
client five’s default ATM address =

2-6 SmartSwitch ATM User Guide

,

39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:85:00

IP Over ATM and LANE Creating an Emulated LAN

The LECS address is constructed from:

netprefix + CPU MAC address + selector byte of 01

For example
netprefix =
chassis MAC address =

39:00:00:00:00:00:00:00:00:00:14:41:89

00:20:D4:14:41:80

then,
default LECS address =

39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:80:01

The LES and BUS have the same ATM address. LES and BUS addresses are constructed fr om:

netprefix + CPU MAC address with last byte summed with the ELAN number + numerical value two (2)

For example
netprefix =
CPU MAC address =
ELAN number =

39:00:00:00:00:00:00:00:00:00:A3:87:0B

00:20:D4:14:41:80

3

then,
default LES and BUS addresses =

39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:83:02

SmartSwitch 6500 Default LANE Addressing

The netprefix is constructed from:

39 + nine zero bytes + last three bytes of chassis MAC address

For example, the chassis MAC address =

00:00:1D:A3:87:0B

,
then
default netprefix =

39:00:00:00:00:00:00:00:00:00:A3:87:0B

The local client address is constructed from:

netprefix + CPU MAC address, with last byte summed with the client number + zero selector byte

For example
netprefix =
chassis MAC address =
CPU MAC address =
client number =

39:00:00:00:00:00:00:00:00:00:A3:87:0B

00:00:1D:A3:87:0B,

00:20:D4:14:41:80

,

5

then,
client five’s default ATM address =

39:00:00:00:00:00:00:00:00:00:A3:87:0B:00:20:D4:14:41:85:00

SmartSwitch ATM User Guide 2-7

Creating an Emulated LAN IP Over ATM and LANE

The LECS address is constructed from:

netprefix + chassis MAC address + selector byte of 01

For example
netprefix =
chassis MAC address =

39:00:00:00:00:00:00:00:00:00:A3:87:0B

00:00:1D:A3:87:0B

then,
default LECS address =

39:00:00:00:00:00:00:00:00:00:A3:87:0B:00:00:1D:A3:87:0B:01

The LES and BUS have the same ATM address. LES and BUS addresses are constructed fr om:

netprefix + chassis MAC address + ELAN number summed with the numerical value two (2)

For example
netprefix =
chassis MAC address =
ELAN number =

39:00:00:00:00:00:00:00:00:00:A3:87:0B

00:00:1D:A3:87:0B

3

then,
default LES and BUS addresses =

39:00:00:00:00:00:00:00:00:00:00:00:1D:A3:87:0B:05

2.2.2 ELANs Across Multiple Switches

ELANs can exist within a single switch, or they can span multiple switches. When an ELAN spans multiple switches,
it’s important that all switches within the group use the same LECS (see note, below). The general rule is: “Within an
administrative domain (a group of switches with related ELANs), there should be one and only one LECS.” For this
reason, never start the LECS on more than one switch within the administrative domain.

Note

The exception to the statement above is that if LNNI is enabled, multiple,
redundant LECS’ and LES/BUS’ can exist within the same administrative
domain. See Section 2.2.7 “Using LNNI.”

Note

If an uplink, end node, or other ATM switch does not support PNNI, or if its
version of ILMI is incompatible, it may be necessary to set up a static route
between the device and the rest of the ELAN. See Chapter 4, "Routing."

2-8 SmartSwitch ATM User Guide

IP Over ATM and LANE Creating an Emulated LAN

2.2.3 Switch Clients

It is important to understand the concept of ATM SmartSwitch client connections. A switch client connection is
actually a VLAN connection to the ATM SmartSwitch’s CPU (Here, we use the term VLAN to mean any type of
“virtual LAN,” whether LANE or IP over ATM.). This CPU connection appears as if the switch is an end station on
the virtual LAN. The ATM SmartSwitch uses local clients to connect itself to the VLANs that it supports.

This is analogous to a phone company that supports a communication system. Even though the phone company
maintains the circuits, a call to the phone company itself cannot be made unless the phone company has its own number
and connection on its own phone system. Similarly, VLAN membership (and the reachability) of an A TM SmartSwitch
on any particular VLAN depends upon whether the ATM SmartSwitch has a local client connection for that VLAN.

Clients are created using the command
For example, the following command adds a switch client to the ELAN

SmartSwitch# add laneclient
ClientNumber(0) : 1
LanName(ELAN001) : elan1
ServerType(LECS) :
ServerAddress() :
IPAddress() : 90.1.1.45 — Just for this example
NetMask(255.255.0.0) :255.255.255.0 — Just for this example
MTU(1516) :
SmartSwitch#

add laneclient for LAN emulation, and add ipatmclient for IP over A TM.

elan1:

Prior to creating this local client connection, end devices could communicate with each other through elan1, but they
could not communicate with the SmartSwitch ATM switch, itself.

2.2.4 Distributed LANE Services

LANE services (LECS, LES, and BUS) can reside on different ATM SmartSwitches. For example, the LECS can
reside on one ATM SmartSwitch, while the LES and BUS reside on another. Use the

add buselan to distribute LANE services among A TM SmartSwitches.

The following steps create an ELAN with the LECS on switch SW1 and the LES and BUS on switch SW2.

Use the add buselan command to create the BUS on switch SW2:

1.

SW2 # add buselan
ELANNumber(0) : 1 — We’ll use ELAN number = 1 throughout the example
ELANName(ELAN001) : mis1 — We’ll call the ELAN “mis1” throughout the example
ConnectMethod(SVC) :
ELANType(802.3) :
Multipoint(YES) :
MTU(1516) :
ErrorLogEnable(NO) :
MinimumTDEnable(NO) :

add lecselan, add leselan, and

SW2 #

SmartSwitch ATM User Guide 2-9

Creating an Emulated LAN IP Over ATM and LANE

2. Use the add leselan command to create an LES on switch SW2:

SW2 # add leselan
ELANNumber(0) : 1
ELANName(ELAN001) : mis1
ConnectMethod(SVC) :
ELANType(802.3) :
Multipoint(YES) :
MTU(1516) :
ErrorLogEnable(NO) :
MinimumTDEnable(NO) :
ForwardPeakCellRate(0) :
BackwardPeakCellRate(0) :
Distribute(PROXY) :
BUSATMAddress(39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:81:02):

SW2 #

— Created by

add buselan

3. Use the show leselan command on SW2 to obtain the ATM address of the LES:

SW2 # show leselan 1

ELAN : mis1

ELAN Number : 1
ELAN Name : mis1
ATM Address : 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:81
:02
Max Frame Size : 1516
Connection Method : SVC
Distribute VPI/VCI : 0/0
Distribute Method : PROXY
ELAN Type : 802.3
Multipoint : YES
Error Logging : NO
Min TD Negotiation : NO
BUS Address : 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:81
:02

— ATM address of LES

SW2 #

4. On switch SW1, use the command add lecselan to create the LECS:

SW1 # add lecselan
ELANNumber(0) : 1
ELANName(ELAN001) : mis1
LESAddress(39:00:00:00:00:00:00:00:00:00:A3:87:0B:00:00:1D:A3:87:0B:03):39:00:00:00:00:00:00:00:0

0:00:14:41:80:00:20:d4:14:41:81:02

ELANType(802.3) :
MTU(1516) :
TLVSet() :

SW1 #

— Specify the LES address on SW2

5. Use the add laneclient command on SW1 to add a client to the ELAN:

SW1 # add laneclient
ClientNumber(0) : 1
LanName(ELAN001) : mis1
ServerType(LECS) :
ServerAddress() :
IPAddress() : 90.1.1.22
NetMask(255.0.0.0) : 255.255.255.0
MTU(1516) :

SW1 #

— This IP address is for example only
— This subnet mask is for example only

2-10 SmartSwitch ATM User Guide

IP Over ATM and LANE Creating an Emulated LAN

6. Use the show client command on SW1 to see that the client has reached all the distributed LANE

services and has successfully joined ELAN

SW1 # show client
ClientNumber(ALL) :

Client Type IP Address Server Type Server Conn Status
==============================================================================
1 LANE 90.1.1.22 LECS Established Operational

SW1 #

mis1.

Notice in the example above that creating an ELAN with distributed services is a process of building fr om the botto m
up: First, the BUS is created so that its address can be specified to the LES. Next, the LES is created so that its address
can be specified to the LECS. Finally, the LECS is created.

If needed, all three ELAN services can exist on separate switches. For example, the BUS can exist on one switch (use

add buselan

the

command), the LES can exist on another switch (use the

exist on another switch (use the

Note If LNNI is enabled, each associated LES an d BUS must reside on the same switch.

add lecselan command).

add leselan

command), and the LECS can

See Section 2.2.7, “Using LNNI” for details.

2.2.5 ELAN Join Policies

ATM SmartSwitches provide control over the assigning of clients to ELANs. Control is accomplished by ELAN join
policies. By default, ATM SmartSwitches have a single ELAN join policy defined —
attempts to join LANE services, the ATM SmartSwitch uses information provided by the client to performs the

Best Effort. When a client

Best

Effort ELAN join test.

Note Additional security can be achieved through the use of ATM address filtering. See

Section 8.1 for information regarding ATM address filtering.

Best Effort Elan Join Test

The following describe the Best Effort test.

1. Does the client specify the n am e of the ELAN it wants to join?

- If yes, check whether an ELAN exists by that name. If an ELAN exists by that name, assign the

client to the ELAN. If no ELAN exists by that name, assign the client to the default ELAN
(ELAN 0).

- If no, check the client against the configuration information stored by the add lecselanlec

command (see The LECSELANLEC Table, on page -13). If an entry exists that corresponds to
the client, assign the client to the ELAN indicated. If the client does not correspond to an entry,
assign it to the default ELAN (ELAN 0).

SmartSwitch ATM User Guide 2-11

Creating an Emulated LAN IP Over ATM and LANE

Note If the default ELAN (ELAN 0) has been deleted, the client is dropped.

By using ELAN join policies, clients attempting to join LANE services can be assigned to specific ELANs. Table 2-1
lists the ELAN join policies that can be configured on an ATM SmartSwitch.

Table 2-1 ELAN Join Policies

Policy No. ELAN Join Policy Information Source Checked

1 Best Effort Default ELAN policy. Checks configuration information stored by the add

lecselanlec

command and during ELAN creation (add elan command).
2 By ATM Address Checks configu ration info rmation stored b y th e
3 By MAC Address Checks configuration information stored by the
4 By Route Descript or Checks configuration information st ored b y th e
5 By LAN Type Checks configuration information stored during ELAN creation (

add lecselanlec command.
add lecselanlec command.
add lecselanlec command.

add elan

command).
6 By Packet Size Checks configuration information from the
7 By ELAN Name Checks configuration information stored by the

add lecspacketsize command.

add lecselannametable

command.

Note For detailed information on each of the commands that ELAN join policies

interacts with, see the command descriptions in the SmartSwitch ATM Reference
Manual.

You can give each ELAN join policy a priority value to determine its hierarchy among other ELAN join policies. If
you define several ELAN join policies, the policy with the greatest priority value is tried first. If that policy fails, the
policy with the next greatest priority value is attempted, and so on. ELAN join policies with the same priority value
are ANDed together. For example, if three join policies are create, each with the same priority value, a client requesting
LANE services must meet the criteria of all three policies to be assigned an ELAN. If the client fails to meet the
requirements of all three policies, the policy with the next lowest priority value will attempt to assign the client to an
ELAN.

2-12 SmartSwitch ATM User Guide