Cabletron Systems EMME User Manual

EMME

SN

RESET

EMME

(ETHERNET MANAGEMENT

MODULE WITH ETHERNET)

USER’S GUIDE

BOK
STBYA
STBYB
RCVA
RCVB
RCVC
RCVD

ON PWR

ON PWR

ERR
STYBC
STBYD
CLNA
CLNB
CLNC
CLND

A
U

I

1

A
U

I

2

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, or software described in this manual is subject to change without notice.

IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY INCIDENTAL,
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 1995 by: Cabletron Systems, Inc., P.O. Box 5005, Rochester, NH 03866-5005

All Rights Reserved
Printed in the United States of America

Part Number: 9030514-04 November 1995

SPECTRUM, LANVIEW, Remote LANVIEW NCM-PCMMAC

trademarks and

MMAC-5FNB, MMAC-3FNB, CXRMIM, TPRMIM, FORMIM

Cabletron Systems, Inc.

All other product names mentioned in this manual may be trademarks or registered trademarks of
their respective companies.

Multi-Channel, Element Manager, EMME, EMME/LM, MMAC-8FNB

, and

, and

BRIM

are registered

EPIM

are trademarks of

,

EMME USER’S GUIDE i

Printed on

recycled paper.

NOTICE

FCC 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:

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 operator’s manual, may cause harmful interference to radio 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.

WARNING:

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

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

Changes or modifications made to this device which are not expressly approved by the

DOC 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 présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables
aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique
édicté par le ministère des Communications du Canada.

VCCI NOTICE

This equipment is in the 1st Class Category (information 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 (VCCI) 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.

Read the instructions for correct handling.

ii EMME USER’S GUIDE

NOTICE

CABLETRON SYSTEMS, INC. PROGRAM LICENSE AGREEMENT

IMPORTANT:

This document is an agreement between you, the end user, and Cabletron Systems, Inc. (“Cabletron”)
that sets forth your rights and obligations with respect to the Cabletron software program (the
“Program”) contained in this package. The Program may be contained in firmware, chips or other
media. BY UTILIZING THE ENCLOSED PRODUCT, YOU ARE AGREEING TO BECOME
BOUND BY THE TERMS OF THIS AGREEMENT, WHICH INCLUDES THE LICENSE AND
THE LIMITATION OF WARRANTY AND DISCLAIMER OF LIABILITY. IF YOU DO NOT
AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED
PRODUCT TO THE PLACE OF PURCHASE FOR A FULL REFUND.

Before utilizing this product, carefully read this License Agreement.

CABLETRON SOFTWARE PROGRAM LICENSE

1. LICENSE.
package subject to the terms and conditions of this License Agreement.

You may not copy, reproduce or transmit any part of the Program except as permitted by the
Copyright Act of the United States or as authorized in writing by Cabletron.

2. OTHER RESTRICTIONS. You may not reverse engineer, decompile, or disassemble the
Program.

3. APPLICABLE LAW. This License Agreement shall be interpreted and governed under the
laws and in the state and federal courts of New Hampshire. You accept the personal jurisdiction
and venue of the New Hampshire courts.

You have the right to use only the one (1) copy of the Program provided in this

EXCLUSION OF WARRANTY AND DISCLAIMER OF LIABILITY

1. EXCLUSION OF WARRANTY.
writing, Cabletron makes no warranty, expressed or implied, concerning the Program (including
its documentation and media).

CABLETRON DISCLAIMS ALL WARRANTIES, OTHER THAN THOSE SUPPLIED TO
YOU BY CABLETRON IN WRITING, EITHER EXPRESSED OR IMPLIED, INCLUDING
BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE PROGRAM, THE
ACCOMPANYING WRITTEN MATERIALS, AND ANY A CCOMPANYING HARDW ARE.

2. NO LIABILITY FOR CONSEQUENTIAL DAMAGES
CABLETRON OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER
(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS,
PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, SPECIAL,
INCIDENTAL, CONSEQUENTIAL, OR RELIANCE DAMAGES, OR OTHER LOSS)
ARISING OUT OF THE USE OR INABILITY TO USE THIS CABLETRON PRODUCT,
EVEN IF CABLETRON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, OR
ON THE DURATION OR LIMITATION OF IMPLIED WARRANTEES IN SOME
INSTANCES THE ABOVE LIMITATIONS AND EXCLUSIONS MAY NOT APPLY TO
YOU.

Except as may be specifically provided by Cabletron in

. IN NO EVENT SHALL

EMME USER’S GUIDE iii

NOTICE

UNITED STATES GOVERNMENT RESTRICTED RIGHTS

The enclosed product (a) was developed solely at private expense; (b) contains “restricted computer
software” submitted with restricted rights in accordance with Section 52227-19 (a) through (d) of the
Commercial Computer Software - Restricted Rights Clause and its successors, and (c) in all respects
is proprietary data belonging to Cabletron and/or its suppliers.

For Department of Defense units, the product is licensed with “Restricted Rights” as defined in the
DoD Supplement to the Federal Acquisition Regulations, Section 52.227-7013 (c) (1) (ii) and its
successors, and use, duplication, disclosure by the Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at 252.227-

7013. Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03867.

iv EMME USER’S GUIDE

TABLE OF CONTENTS

CHAPTER 1 INTRODUCTION

1.1 USING THIS MANUAL................................................................1-1

1.2 ETHERNET MANAGEMENT MODULE OVERVIEW..................1-2

1.2.1 Multi Media Access Center with Flexible Network Bus... 1-4

1.2.2 Repeater Interface Controller Media Interface Modules. 1-5

1.2.3 Ethernet Channels A, B, C, and D.................................. 1-6

1.2.4 Local Management .........................................................1-8

1.2.5 MIB Navigation ...............................................................1-8

1.2.6 LANVIEW LEDs.............................................................. 1-8

1.2.7 LANVIEWSECURE......................................................... 1-8

1.3 REPEATER FUNCTIONALITY..................................................1-10

1.4 BRIDGING FUNCTIONALITY...................................................1-10

1.5 MORE ABOUT BRIDGES.........................................................1-11

1.5.1 Filtering and Forwarding............................................... 1-12

1.5.2 Spanning Tree Algorithm.............................................. 1-13

1.6 ROUTING FUNCTIONALITY ....................................................1-13

1.7 COMMUNITY NAMES...............................................................1-15

1.8 SNMP (SIMPLE NETWORK MANAGEMENT PROTOCOL)....1-15

1.8.1 Management Information Base (MIBs)......................... 1-16

1.9 IP ADDRESSING ...................................................................... 1-16

1.9.1 Network ID.................................................................... 1-17

1.9.2 Host ID.......................................................................... 1-17

1.9.3 Subnet Addresses ........................................................1-17

1.9.4 Subnet Masks............................................................... 1-18

1.10 DEFAULT GATEWAY...............................................................1-19

1.11 MAC ADDRESS........................................................................1-19

1.12 NETWORK MANAGEMENT CAPABILITIES............................1-19

1.13 UNINTERRUPTIBLE POWER SUPPLIES (UPS).....................1-20

1.14 EMME UPGRADES...................................................................1-20

1.15 GETTING HELP........................................................................1-22

1.16 RELATED MATERIAL...............................................................1-22

EMME USER'S GUIDE

v

TABLE OF CONTENTS

CHAPTER 2 NETWORK PLANNING AND CONFIGURATION

2.1 NETWORK REQUIREMENTS.....................................................2-1

2.2 EMME IN THE MULTI MEDIA ACCESS CENTER......................2-1

2.3 REPEATER MEDIA INTERFACE MODULES.............................2-2

2.3.1 Ethernet Port Interface Modules......................................2-4

2.4 SAMPLE NETWORK CONFIGURATIONS .................................2-5

2.4.1 Three Networks with a Single MMAC-FNB.....................2-6

2.4.2 Network with a Multi-port Router.....................................2-7

2.4.3 Configuring Additional Users to a Separate Segment.....2-8

2.4.4 Multiple Routed Sub-Networks......................................2-10

2.4.5 A Fault Tolerant Wiring Hierarchy.................................2-11

CHAPTER 3 INSTALLING THE EMME

3.1 UNPACKING THE EMME............................................................3-1

3.2 SETTING THE EMME MODE SWITCHES..................................3-2

3.3 INSTALLING THE EMME............................................................3-5

3.4 CONNECTING THE EMME TO THE NETWORK .......................3-7

CHAPTER 4 TESTING THE EMME

4.1 PRE-INSTALLATION TEST.........................................................4-1

4.2 INSTALLATION CHECK-OUT.....................................................4-3

CHAPTER 5 LOCAL MANAGEMENT

5.1 MANAGEMENT TERMINAL CONFIGURATION.........................5-2

5.1.1 Cable Configuration for the Management Terminal ........5-3

5.1.2 Cable Configuration for the UPS.....................................5-4

5.2 ESTABLISHING A TELNET CONNECTION ...............................5-4

5.3 LOCAL MANAGEMENT KEYBOARD CONVENTIONS..............5-5

5.4 ACCESSING LOCAL MANAGEMENT ........................................5-7

5.5 NAVIGATING LOCAL MANAGEMENT SCREENS.....................5-9

5.5.1 Selecting Local Management Menu Screen Items..........5-9

5.5.2 Exiting Local Management Screens..............................5-10

5.6 THE MAIN MENU SCREEN ......................................................5-11

5.7 SETUP MENU SCREEN ...........................................................5-12

vi

EMME USER'S GUIDE

TABLE OF CONTENTS

5.8 THE SYSTEM LEVEL SCREEN ............................................... 5-13

5.8.1 System Level Screen Fields .........................................5-13

5.8.2 Setting the System Date............................................... 5-15

5.8.3 Setting the System Time............................................... 5-15

5.8.4 Setting the IP Address.................................................. 5-16

5.8.5 Setting the Subnet Mask............................................... 5-17

5.8.6 Setting the Default Interface .........................................5-17

5.8.7 Setting the Default Gateway......................................... 5-18

5.8.8 Configuring Console and Modem Ports........................ 5-19

5.9 SNMP COMMUNITY NAMES SCREEN...................................5-21

5.9.1 Setting SNMP Community Names................................ 5-22

5.10 SNMP TRAPS SCREEN...........................................................5-23

5.10.1 Trap Table Screen Fields .............................................5-23

5.10.2 Setting SNMP Trap Destinations..................................5-24

5.11 STATUS MENU.........................................................................5-25

5.12 THE COMPONENT STATUS SCREEN....................................5-26

5.12.1 Component Status Screen Fields.................................5-26

5.13 THE DEVICE STATISTICS SCREEN.......................................5-27

5.13.1 Device Statistics Screen Fields ....................................5-27

5.13.2 Selecting an Update-Freq.............................................5-29

5.13.3 Selecting a Network/Slot/Port.......................................5-29

5.13.4 Enabling Ports ..............................................................5-30

5.13.5 Disabling Ports..............................................................5-30

CHAPTER 6 MIB NAVIGATOR

6.1 MANAGING DEVICE MIBs .........................................................6-1

6.2 ACCESSING THE MIB NAVIGATOR..........................................6-2

6.3 MIB NAVIGATOR COMMAND SET OVERVIEW........................6-3

6.3.1 Conventions for MIB Navigator Commands ...................6-3

6.3.2 Navigation Commands ...................................................6-5

6.3.3 Built-In Commands .......................................................6-11

6.3.4 Special Commands....................................................... 6-17

CHAPTER 7 TROUBLESHOOTING

7.1 INTERPRETING THE LANVIEW LEDs.......................................7-1

7.2 TROUBLESHOOTING CHECKLIST...........................................7-4

7.3 USING THE RESET BUTTON....................................................7-6

7.4 BEFORE CALLING TECHNICAL SUPPORT..............................7-6

EMME USER'S GUIDE

vii

TABLE OF CONTENTS

APPENDIX A IMAGE FILE DOWNLOAD USING OIDS

A.1 SETTING UP A UNIX WORKSTATION AS A TFTP SERVER... A-2

A.2 STANDARD LOCAL DOWNLOAD ............................................. A-3

APPENDIX B EMME OIDS

B.1 SPANNING TREE PROTOCOL .................................................B-1

B.2 PORT GROUP SECURITY......................................................... B-2

B.3 NETWORK AND CHANNEL LEVEL TRAPS.............................. B-5

B.4 BOARD LEVEL TRAPS.............................................................. B-6

B.5 PORT LEVEL TRAPS................................................................. B-7

B.6 BRIDGING .................................................................................. B-8

B.7 TRUNK PORT SECURITY .........................................................B-8

B.8 CHANNEL SELECTION .............................................................B-9

APPENDIX C EMME SPECIFICATIONS

C.1 BRIDGING FUNCTIONALITY.....................................................C-1

C.2 REPEATER FUNCTIONALITY...................................................C-2

C.3 CONSOLE PORT .......................................................................C-2

C.4 MODEM PORT ...........................................................................C-3

C.5 AUI PORTS.................................................................................C-3

C.6 ENVIRONMENTAL REQUIREMENTS.......................................C-4

C.7 FLASH EPROM ..........................................................................C-4

C.8 SAFETY......................................................................................C-4

C.9 SERVICE ....................................................................................C-4

C.10 PHYSICAL PROPERTIES..........................................................C-4

INDEX

viii

EMME USER'S GUIDE

CHAPTER 1

INTRODUCTION

Welcome to the Cabletron Systems

(EMME) User’s Guide

description of the EMME and the information needed to install and
operate it in a Cabletron Systems Multi Media Access Center with the
Flexible Network Bus (MMAC-FNB).

A general knowledge of Ethernet and IEEE 802.3 type data
communications networks and their physical layer components is helpful
when using the EMME.

. This manual provides the technical user with a

Ethernet Management Module

1.1 USING THIS MANUAL

Before installing or operating the EMME, read through this manual to
familiarize yourself with its content and to gain an understanding of the
features and capabilities of the EMME. This manual is organized as
follows:

Chapter 1,
provides an overview of its multichannel capability that supports up to
four separate Ethernet segments. This chapter also explains the EMME
repeater and bridge functionality, concluding with a list of related
manuals.

Introduction

, discusses the capabilities of the EMME and

Chapter 2,
requirements to consider before installing the EMME. This chapter also
includes sample configurations demonstrating various applications for the
EMME.

Chapter 3,
the EMME into an MMAC-FNB, set the EMME’s mode switches, and
connect segments to the EMME.

Chapter 4,
EMME before it is installed and again after connecting it to the network.

Chapter 5,
Local Management provides tools to manage the EMME and its attached
segments.

EMME USER’S GUIDE Page 1-1

Network Planning and Configuration

Installing the EMME

Testing the EMME

Local Management

, explains the network

, provides instructions on how to install

, provides procedures for testing the

, describes EMME Local Management.

CHAPTER 1

: INTRODUCTION

Chapter 6,

MIB Navigator

, describes MIB Navigator’s management and
control. The MIB Navigator manages EMME-related Management
Information Bases.

Chapter 7,

Troubleshooting

, details the Remote LANVIEW LEDs
incorporated into the EMME that enable you to quickly diagnose
problems that may occur with the module. This chapter also includes a
troubleshooting checklist, procedures for using the reset button, and
instructions for calling Technical Support if you need assistance.

Appendix A,

Image File Download Using OIDs

, provides instructions
for downloading an image file to the EMME by setting the MIB OID
strings.

Appendix B,

EMME OIDs

, contains selected OID strings which are

most often used.
Appendix C,

EMME Specifications

, contains location requirements and

operating specifications for the EMME.

1.2 ETHERNET MANAGEMENT MODULE OVERVIEW

The Cabletron Systems Ethernet Management Module with Ethernet
(EMME) is the heart of the Cabletron Systems Multi Media Access
Center. The EMME can provide four bridged and managed channels and
management for three separate Ethernet channels within a single MMAC.
This is accomplished by having channel A operate over the Power and
Management Bus, Cabletron’ s original Ethernet channel. Channels B and
C operate over the Flexible Network Bus (FNB). The EMME can also
bridge all three channels to a fourth externally connected channel (D,
usually a backbone connection), using one of the AUI ports on the
faceplate of the module.

The Cabletron Systems Ethernet non-repeater Media Interface Modules
use channel A on the MMAC backplane to communicate with the EMME
which performs the repeating function. MIMs provide a variety of
different media connections at one point within an MMAC. The EMME
incorporates an IEEE 802.3 repeater to provide repeater functionality for
these MIMs.

The EMME is fully compliant with IEEE 802.3 standards and provides
support for Spanning Tree IEEE 802.1d and DECnet.

Page 1-2 EMME USER’S GUIDE

ETHERNET MANAGEMENT MODULE OVERVIEW

The EMME operates in conjunction with Cabletron Systems’ Repeater
Interface Controller (RIC) Media Interface Modules (MIMs) by using the
MMAC’s FNB Ethernet channels B and C.

The EMME is SNMP compliant and can be controlled and monitored by
numerous SNMP Network Management packages both remotely and
locally. EMME firmware also supports Distributed LAN Monitor (DLM)
and Full Remote Monitoring (RMON) groups including: Alarms, Events,
History, Hosts, Hosts Top N, Statistics, Matrix, Captive and Filter.

The EMME also provides the following:

• i960 RISC based processor

• Four bridged/routed Ethernet networks

• IEEE 802.1 D Spanning Tree and DEC Spanning Tree support

• IEEE 802.3 compliance

• Flash download capability for easy firmware downloads

• Standard FTP download capability

• LANVIEW diagnostic LEDs

• Special Filtering Data Base

• Complete SNMP management capability

• IETF MIB support including bridge, RMON, and MIBII

• Complete packet and error breakdown for all four channels

• Cabletron Systems’ Distributed LAN Monitoring (DLM) reducing
management traffic between network devices and management
platform

• Cabletron Systems’ cable redundancy

EMME USER’S GUIDE Page 1-3

CHAPTER 1

: INTRODUCTION

1.2.1 Multi Media Access Center with Flexible Network
Bus

The Multi Media Access Center with Flexible Network Bus
(MMAC-FNB) pro vides the platform for the operation of the EMME. The
MMAC backplane provides three Ethernet buses designated as Ethernet
A, B, and C (See Figure 1-1). Cabletron Systems’ non-repeater MIMs
communicate over Ethernet A while Cabletron Systems’ repeater MIMs
use the Ethernet B and C buses. The EMME connects these buses to
provide bridging and management functionality.

There are two types of MMACs supporting Flexible Network Bus
architecture: shunting and non-shunting. Shunting supportive
MMAC-FNBs allow modules operating on either the Ethernet B or C bus
to continue communications with the EMME regardless of whether there
is an empty slot or an Ethernet A bus module between them in the chassis.

Power & Management Bus

Ethernet A Bus

Flexible Network Bus

Ethernet B Bus

Ethernet C Bus

Figure 1-1. MMAC Flexible Network Bus

051431

Page 1-4 EMME USER’S GUIDE

ETHERNET MANAGEMENT MODULE OVERVIEW

Table 1-1 provides a list of the MMAC-FNB chassis where shunting
capabilities are set at the factory.

Table 1-1. MMAC-FNB Chassis

MMAC-FNB Chassis Serial No.

MMAC-3FNB
MMAC-5FNB
MMAC-8FNB
MMAC-M3FNB ALL
MMAC-M5FNB ALL
MMAC-M8FNB

FC

000000000 or above

CC

000000000 or above

CG

000000000 or above

DK

000000000 or above

1.2.2 Repeater Interface Controller Media Interface
Modules

Cabletron Systems’ MultiChannel family of Media Interface Modules
(MIMs) includes the Repeater Interface Controller (RIC), which is an
IEEE 802.3 compliant multi-port repeater. You can configure these
modules to operate on either the Ethernet B or C bus, via hardware
jumpers or management software. Software management overrides any
hardware configuration setting.

RIC technology provides the MIM with an inter-RIC bus, allowing
multiple RIC MIMs communicating over the RIC bus to act as a single
logical repeater. For example, an Ethernet frame taking a path from one
RIC MIM, to the Inter-RIC bus, to another RIC MIM (the frame being
retimed and regenerated to all ports from the last RIC MIM) has a path
cost equivalent to only one repeater hop. Since Ethernet networks are
limited to four serially linked repeaters, using the RIC repeater offers a
significant advantage. By using cascading RIC MIMs, each of which
support at least 13 cable segments, you can build a much larger network
than you could with stand-alone repeaters.

EMME USER’S GUIDE Page 1-5

CHAPTER 1

: INTRODUCTION

1.2.3 Ethernet Channels A, B, C, and D

The EMME supports up to four Ethernet channels, provides management
for the four channels, and bridging between the ports. The four EMME
Ethernet channels access the same shared memory so that bridging
between the channels occurs concurrently.

TPMIM, FOMIM, and THNMIM

- The EMME provides repeater
functionality for these Cabletron Systems non-repeater Media Interface
Modules by using Ethernet channel A on the MMAC backplane to
transmit and receive data.

TPRMIM, FORMIM, and CXRMIM -

Ethernet channels B and C
transmit and receive pack ets o ver the Repeater Interface Controller (RIC)
management bus on the FNB to these Cabletron Systems RIC MIMs.
These MIMs can repeat packets autonomously without channeling them
through the EMME.

Third Party MIMs -

The EMME recognizes the third party MIMs listed
below and provides each module with support concerning the statistics on
the backplane and the control of channel selection for the entire module:

CSMIM2

•

- W ith supported connecti vity for channels A, B, or C in an

FNB chassis.

•

MODMIM -

With supported connectivity for channels A, B, or C in

an FNB chassis.

•

CRM-3E -

With supported connectivity for channels A, B, or C in an

FNB chassis.

•

PCMIM

- With supported connectivity for channel A in any MMAC

chassis.

•

SNACMIM-E

- With supported connectivity for channel A in any

MMAC chassis.

Page 1-6 EMME USER’S GUIDE

ETHERNET MANAGEMENT MODULE OVERVIEW

FDDI and Token Ring Modules

- The EMME recognizes the following
FDDI and Token Ring modules, but the EMME management does not
provide control or statistics.

CRM-3T

•

•

SNACMIM

•

TRMIM-32A

•

TRMIM-34A

•

TRRMIM-F2T

•

TRRMIM-F3T

With TRMMIM version 2.02 or greater, both Token Ring and Ethernet
modules can reside in the same chassis and support physical management
capabilities of the Token Ring MIMs using the TRMMIM as the token
ring management module. Without the TRMMIM, the EMME will only
recognize the Token Ring modules.

Ethernet Channel D -

Ethernet channel D is provided by one of the two
redundant AUI ports on the front panel of the EMME. With the correct
transceiver, the AUI ports provide the capability for cable redundancy and
a variety of Ethernet transmission media connections, including twisted
pair, fiber optic, and thick or thin Ethernet coaxial cable.

Either one of the AUI ports can act as the bridge port to the external
network. When the EMME is first powered up, the AUI 1 port acts as the
bridge port and the AUI 2 port is off. Using the EMME’s network
management capabilities, you can reverse this configuration to have the
AUI 2 port act as the primary bridge port.

TPXMIM -

The EMME also supports Cabletron’ s family of Twisted Pair
Switching Media Interface Modules (TPXMIMs). These modules provide
board or individual port connectivity to any MMAC-FNB Ethernet
Channel (A, B, or C) with full SNMP management including RMON. All
ports initially default to Channel B upon power up and require a
Management Information Base (MIB) change to access any other
channel.

EMME USER’S GUIDE Page 1-7

CHAPTER 1

: INTRODUCTION

1.2.4 Local Management

Built into the front panel of the EMME are two RJ45 ports. The Console
port allows access to Local Management by locally connecting a DEC VT
320 terminal, or a PC using VT320 emulation software. Refer to Chapter
5, Local Management.

1.2.5 MIB Navigation

EMME firmware supports a management tool through which you
navigate through Management Information Bases (MIBs). Refer to
Chapter 6, MIB Navigator.

1.2.6 LANVIEW LEDs

The EMME incorporates Cabletron Systems’ LANVIEW Status
Monitoring and Diagnostics System. Should a problem arise, such as a
power failure or a cable fault, the LANVIEW LEDs will help you to
diagnose it. The module includes the following LANVIEW LEDs:

• Board OK and Error LEDs for board status

• Standby, Receive, and Collision LEDs for Ethernet Channel Status

• On and Power LEDs for AUI Port Status

1.2.7 LANVIEW

SECURE

The EMME supports the LANVIEWSECURE suite of Ethernet MMAC
products. The LANVIEW

SECURE products support both inbound data,

“Intruder Prevention,” and outbound data, “Eavesdrop Prev ention.” These
products are identified by the words “LANVIEW

SECURE” printed on the

faceplate of the product.
Intruder prevention allo ws locking of ports when an intruder , based on the

expected MA C address assigned to that port, is seen on that port. A trap is
then generated and sent to the Network Management station to indicate an
intruder violation. When locking is enabled, the default configuration for
intruder prevention in LANVIEW

SECURE disables the port and sends a

trap to the management station. If the trap screen is configured
appropriately, through Local Management or setting OIDs, traps are sent
to the management station.

Page 1-8 EMME USER’S GUIDE

ETHERNET MANAGEMENT MODULE OVERVIEW

Eavesdrop prevention delivers a modified data portion (filled with a
random pattern of binary ones and zeros) of the Ethernet packet to all
ports except the port specified in the original packet’s destination MAC
address field. Effectively all ports, except the actual destination port,
receive meaningless information. There are two learned MAC addresses
per port.

Full security allows the network administrator to configure the ports, so
that “broadcast” and “multicast” packets have the data portion of the
packet modified with a random pattern of ones and zeroes. Therefore, the
ports set to this mode do not see these packet types. The default setting for
“Full security” is disabled. Enabling the “Full security” function modifies
the broadcast and multicast packets.

LANVIEW
addresses per LANVIEW

SECURE products support assignment of up to 32 MAC

SECURE chip. The addresses can be assigned to

one or divided among several ports on the chip.
For LANVIEWSECURE products, trunk ports are defined as 3 or more

MAC addresses but may not exceed 34 MAC addresses, on that port, in
order to secure it. A port with 35 or more addresses can never be secured.
Ports with 3 - 34 MAC addresses can be secured and will need the
addresses manually entered to secure the port. Non-LANVIEW

SECURE

ports can only be secured with 2 or less MAC addresses associated with
that port. Non-LANVIEW

SECURE ports with three or more addresses can

never be secured.
LANVIEWSECURE is enabled upon locking a channel, module, or port.

When enabled, the first two addresses that are learned become the
expected address associated with that port on any LANVIEW

SECURE

module.

EMME USER’S GUIDE Page 1-9

CHAPTER 1: INTRODUCTION

1.3 REPEATER FUNCTIONALITY

The EMME’s repeater functionality ensures that any problem segments
connected to any port on the MMAC-FNB will not affect any other
segments connected to the MMAC-FNB. For example, if 32 consecutive
collisions are detected on any segment, or if a collision detector is on for
more than 2.4 milliseconds, the EMME automatically partitions that
segment from the MMAC-FNB. The segment is automatically
reconnected to the MMAC-FNB when a good packet is transmitted onto
the segment.

For Cabletron Systems’ original non-repeater MIMs (i.e., TPMIM,
FOMIM) the EMME’s IEEE 802.3 compliant repeater provides the
MMAC-FNB with the ability to achieve maximum data paths on all
Ethernet transmission media, including 10BASE-T twisted pair, fiber
optic, and thick or thin Ethernet type cabling. To attain these maximum
data paths, the EMME retimes data packets and regenerates the preamble
of each data packet that enters the MMAC-FNB.

With the Cabletron Systems repeater modules (TPRMIM, CXRMIM, and
FORMIM), packets are repeated autonomously on the MIM and are not
channelled through the EMME. Module to module repeating is achieved
over the FNB backplane. The EMME provides management for these
modules and keeps Device, Network, Board, and Port Level performance
and error statistics.

1.4 BRIDGING FUNCTIONALITY

The EMME automatically configures itself as a bridge between channels
A, B, C, and D, for a four port bridge maximum. The EMME provides

802.1d compliant bridging capabilities to prevent unnecessary network
traffic from passing between segments.

Frames received by the EMME are forwarded to four megabytes of
buffering memory. The EMME’s processor accesses the frames from the
buffered memory and passes address information to the bridging
algorithm. Then, based on the bridging decision, the frames are filtered or
forwarded.

The EMME incorporates the Spanning Tree and DEC Spanning Tree
Algorithms that allow network architects to set up bridges in parallel
between segments as backup paths for fault tolerance. These bridges
remain in a standby condition until the primary parallel path fails.

Page 1-10 EMME USER’S GUIDE

MORE ABOUT BRIDGES

1.5 MORE ABOUT BRIDGES

A bridge is a device that can be added to a network to allow expansion
beyond the limitations of IEEE 802.3. If an Ethernet network has a
repeater hop (count) of four repeaters or a propagation delay near the

51.2-microsecond maximum, a bridge can be used to build an extended
network. Ethernet bridges read in packets and decide to filter or forward
them based on the destination address of the packet. The simple forward/
filter decision process allows a bridge to segment traffic between two
networks, keeping local traffic local. This process increases the
availability of each network while still allowing traffic destined for the
opposite side of the bridge to pass.

Bridges are also used to connect similar networks such as Ethernet, Token
Ring, and Fiber Distributed Data Interface (FDDI) together. Note that
similar networks means that the upper five layers of the OSI model (see
Figure 1-2) are the same but may have different Data Link and Physical
layers. The Bridge operates at the Data Link level of the OSI model. It
stores packets and based on the packet destination address, forwards or
filters the packets. Because bridges work at layer 2 of the OSI model,
bridges are protocol independent. Bridges are slower than repeaters
because a bridge must read the complete data frame, check for errors, and
make forward or filter decisions based on recognized addresses stored in
its source address table.

7. APPLICA TION

6. PRESENTATION

5. SESSION

4. TRANSPOR T

3. NETWORK

2. DATA LINK

1. PHYSICAL

7
6
5
4

BRIDGE

3
2
1

Figure 1-2. OSI Model

7
6
5
4
3
2
1

EMME USER’S GUIDE Page 1-11

CHAPTER 1: INTRODUCTION

The bridge is considered a node on the network and performs store and
forward functions for packets on each network. This contrasts with a
repeater which repeats the signal bit by bit from one side of the network
to the other. The bridge actually reads each packet, checks the packet for
accuracy, then decides whether the packet should be sent to the other
network based on the destination address. If the other network is busy, it
is the responsibility of the bridge to store the packet, for a reasonable
time, until the transmission can be made.

The bridge is also responsible for handling collisions. If a collision
happens as the bridge is transmitting onto the second network, the bridge
is responsible for the back off and retransmission process. The original
sending node is not made aware of the collision. It assumes the packet has
been sent correctly. If the bridge is unable to send the packet to its final
destination, the original sending station, expecting some response from
the device it was attempting to contact, will “time out” and depending on
the protocol attempt retransmission.

1.5.1 Filtering and Forwarding

The bridge decides whether to forward or filter a packet based on the
physical location of the destination device with respect to the source
device. A bridge dynamically learns the physical location of devices by
logging the source addresses of each packet and the bridge port the packet
was received on in a table called the Source Address Table (SAT).

The EMME supports the Special Filtering Database. This feature allows
the networks manager to define bridge filters above and beyond the
normal source and destination filters. The Special Filtering Database
allows filters to be configured for source, destination, type field, and a
flexible 64-byte offset to filter on information within the data portion of
the packet. A 64-byte window of data can search the data portion of the
packet to make filtering and forwarding decisions.

Page 1-12 EMME USER’S GUIDE

ROUTING FUNCTIONALITY

1.5.2 Spanning T ree Algorithm

The Spanning Tree Algorithm (STA) is used by bridges to detect data
loops (duplicate data paths). The bridges will then automatically break the
loop and use the now blocked path as a backup in case the primary path
fails.

When a bridge is powered up, it goes through a series of self tests to
check its internal operation. During this time the bridge is in a standby
condition and does not forward traffic. Also during this standby period,
the bridge sends out special bridge management packets called
configuration Bridge Protocol Data Packets (BPDU). Bridges use the
BPDUs as a way of communicating with each other. The purpose of the
configuration BDPU is to notify other bridges on all of the connected
networks of the current topology. Based on the bridge priority and
address, the other bridges will automatically detect loops and negotiate a
single path. The bridge or bridges involved in this primary data path will
then come on-line and the bridges with lower priority involved in the
backup path(s) will go into a blocking condition.

The other type of BPDU is the topology change BPDU. This BPDU is
made up of four bytes and notifies the other bridges that a change has
taken place. Upon receipt of the topology change BPDU the bridges will
re-arbitrate, or re-span, to form a legal topology.

1.6 ROUTING FUNCTIONALITY

For routing functionality in the EMME, the following is needed:

• Routing Services software for the EMME module. A license must be

purchased for each module upgrade.

• 8-MB memory upgrade to bring the Dynamic Random Access

Memory (DRAM) up to a total of 12 MB. For information about 8-MB
upgrade kits, refer to the EMME Upgrades section at the end of this
chapter.

EMME USER’S GUIDE Page 1-13

CHAPTER 1: INTRODUCTION

The Routing Services software provides the following additional
funtionality:

• Security via access lists

• Directed User Datagram Protocol (UDP) broadcast forwarding

• Support for multiple frame types:

- Internet Protocol (IP) and DECnet - Ethernet Type II and

SubNetwork Address Protocol (SNAP)

- Internet Packet Exchange (IPX) - Ethernet Type II, Novell, 802.2

and SNAP

• Statistics for host delivered and sourced packets

• Basic configuration via a local terminal

• Diagnostics via Telnet

• Flash download via Trivial File Transfer Protocol (TFTP)
With the Router Software loaded in the EMME, the EMME has the

options available for three network protocols. The user, through Local
Management, can select either IP, IPX, or DECnet Phase IV routing.

IP routing is the TCP/IP protocol that specifies how information is brok en
into packets, and how they are addressed to route over a network.

DECnet Phase IV specifies two forms of DECnet routing as follows:

• Phase IV or Level 1- For routing DECnet packets from one node to
another within a DECnet area.

• Area or Level 2 - For routing DECnet packets from one DECnet area
to another.

The DECnet Phase IV routing services are based on Digital Equipment
Corporation’s requirements for DECnet Phase IV, Level 1, and Area
routers.

Page 1-14 EMME USER’S GUIDE

COMMUNITY NAMES

1.7 COMMUNITY NAMES

When using Local or Remote management tools to access the EMME, it
is important that the network manager has the ability to maintain network
security. Community names provide some network security by serving as
passwords to the device and the software running it. The network
manager (super user) establishes three (3) passwords, each of which
controls varying levels of access to the hardware and software. The
Community names are set through the Local Management SNMP
Community Names Table. Once these are set by the network manager,
they can be maintained in confidence or limited to users who have a need
to manage the system.

The three levels of access are:

• Super-User - Allows full management privileges

• Read Write - Allows edit of device configuration parameters not

including changing Community names

• Read Only - Allows reading of device parameters not including

Community names

1.8 SNMP (SIMPLE NETWORK MANAGEMENT

PROTOCOL)

SNMP is a protocol within the TCP/IP protocol suite. Network
applications such as Local Management and MIB Navigator use SNMP to
manage device configurations and monitor operating conditions. SNMP
protocol defines methods for “GETs,” “SETs,” and “TRAPs,” either
remotely from any point along the TCP/IP network or locally. This allows
for control of the device from any point along the network. MIB
Navigator uses the Management Information Base (MIB), located on the
device to be managed, to access information (GET), change device
parameters (SET), and to notify preselected users that an event has
occurred (TRAP).

EMME USER’S GUIDE Page 1-15

CHAPTER 1: INTRODUCTION

1.8.1 Management Information Base (MIBs)

The MIBs are a database which are resident on the network device (i.e.,
EMME). Objects in the information base are uniquely identified by
administratively assigned identifiers (called object identifiers or OIDs)
and can be viewed, retrieved, or changed using an SNMP packet
exchange over the network or locally using MIB Navigator.

1.9 IP ADDRESSING

Each network interface or TCP/IP host is identified by a 32-bit binary
number called the IP address. This 32-bit number is divided into four
8-bit numbers called octets. Each octet is translated into its decimal
equiv alent and is represented using Dotted Decimal Notation (DDN). The
DDN format is XXX.XXX.XXX.XXX.

The IP address consists of two distinct parts, the Network ID and Host ID.
There are three classes of IP addressing: Class A, B, and C.

Tables 1-2 through 1-4 describe the classes.

Table 1-2. Class A

Range of Network IDs: 1 - 126.host.host.host

[1 octet for the Network ID (127
reserved)]

Binary translation:
(of first octet)

Range for the Host ID: net.1 - 254.1 - 254.1 - 254

Table 1-3. Class B

Range of Network
IDs:

Binary translation:
(of first octet)

128 -191.1 - 254.host.host
[2 octets for the Network ID]

1000000 - 10111111
[first bit is always 1 and second is always 0]

0000001 - 01111111
[first bit is always 0]

[3 octets for the Host ID - allows
16,777,214 hosts per network]

Range for the Host
ID:

Page 1-16 EMME USER’S GUIDE

net.net.1 - 254.1 - 254
[2 octets for the Host ID - allows 65,534 hosts
per network]

Table 1-4. Class C

IP ADDRESSING

Range of Network
IDs:

Binary translation:
(of first octet)

Range for the Host
ID:

192 - 223.1 - 254.1 - 254.host
[3 octets for the Network ID]

1100000 - 11011111
[first and second bits always 1 and third is
always 0]

net.net.net.1 - 254
[1 octet for the Host ID - allows 254 hosts per
network]

1.9.1 Network ID

The Internet Assigned Numbers Authority (IANA) assigns the Network
ID and uniquely identifies a network on the Global Internet. On private
internal networks, unofficial IP addresses can be used allowing the
network address to be unique only within that internal network. (This is
not recommended by Cabletron.) The size of the Network ID is
determined by the class of the IP address.

1.9.2 Host ID

Host IDs are assigned by the local administrator . Since all hosts within the
same network share the same Network ID, each host must have a unique
Host ID. This allows for the identification of each host within the netw ork
based on this portion of the IP address. The class of IP address used
determines the size of the Host ID.

1.9.3 Subnet Addresses

Subnet addresses are used to partition an IP network into multiple
subnetworks or subnets. The use of Subnet addresses adds an additional
layer of hierarchy to the IP addressing scheme. This additional addressing
layer facilitates isolation, control, and administration of users within the
network. This is done by grouping hosts into separate subnets. Use of
subnet addresses on the network means using a subnet mask in
conjunction with each IP address.

EMME USER’S GUIDE Page 1-17

CHAPTER 1: INTRODUCTION

1.9.4 Subnet Masks

The purpose of the subnet mask is to indicate the part of the Host ID that
is being used as a Subnet address. By default no part of the Host ID is
used, and therefore, the default or “Natural Mask” masks just the octets
that comprise the Network ID. Table 1-5 shows the default masks.

Table 1-5. Class and Default Masks

Network Class Length of Network ID Default Mask

Class A X. 255.0.0.0
Class B X.X. 255.255.0.0
Class C X.X.X. 255.255.255.0

The binary 1’s in the mask “mask-out” the Network ID and the 0’s show
where the Host ID is. When using part of the Host ID as a subnet address,
define a subnet mask that will mask-out the bits of the Host ID that are
being used as a subnet address. The calculations for the mask must be
done at the bit level since in some cases, al w ays in Class C addresses, the
last octet must be split into part Host ID and part Subnet address.

Table 1-6 shows how using the mask determines the subnet and Host
addresses that are available from the octet.

Table 1-6. Examples of Subnet Masks

Decimal

Mask

255 11111111 1 - 254 None
254 11111110 2 - 254 (Even numbers only) None
252 11111100 4 - 252 (Multiples of 4 only) 1 and 2
248 11111000 8 - 248 (Multiples of 8 only) 1 - 6
240 11110000 16 - 240 (Multiples of 16 only) 1 -14
224 11100000 32, 64, 96, 128, 192, 224 1 - 30
192 11000000 64 and 192 1 - 62

Binary

Equivalent

Available Subnet

Addresses

Available

Host IDs

Page 1-18 EMME USER’S GUIDE

DEFAULT GATEWAY

1.10 DEFAULT GATEWAY

The default gateway is the IP address of the network or host to which all
packets addressed to unknown network or host are sent. The default
gateway should be a perimeter or border de vice that connects the netw ork
with the rest of the world. The default gateway attempts to route the
packet to the correct destination. This gateway is often used by managers
to handle all traffic between pri v ate networks and the Internet. If a def ault
gateway is not defined the packets addressed to a netw ork or host address
not found in the forwarding table will be dropped.

1.11 MAC ADDRESS

The MAC address is a unique, 48-bit binary number, associated with a
specific physical connection to a network. MAC addresses are divided
into 6 octets, and represented in hexadecimal form such as the following:

00-00-1D-00-26-FB
The MAC addresses are administered by the IEEE and are generally

assigned at the time of manufacture, and cannot be changed. The first
three octets uniquely identify the manufacturer . Cabletron de vices all start
with: 00-00-1D.

1.12 NETWORK MANAGEMENT CAPABILITIES

The Cabletron Systems EMME can be controlled and managed by any
SNMP network management system. These include:

• Cabletron Systems SPECTRUM

• Cabletron Systems SPECTRUM Element Manager for Windows

• Third Party SNMP compliant Network Management Packages
The EMME’s network management capabilities provide the necessary

management tools for the EMME to operate at its full capacity. Your
ability to set up parameters with network management ensures optimal
performance of the EMME.

EMME USER’S GUIDE Page 1-19

CHAPTER 1: INTRODUCTION

For example, you can gather a large amount of statistical information
about the EMME, including the quantities of the following.

– Packets – Receive Collisions
– Transmit Collisions – Giant Packets
– Runt Packets – Misaligned Packets
– CRC Error – Out of Window Collisions
– Bytes Received

For further specific information, refer to the applicable Network
Management Package User’s Manual.

1.13 UNINTERRUPTIBLE POWER SUPPLIES (UPS)

The EMME can monitor and control American Power Conversion UPSs.
The EMME modem port is connected to the UPS via a DB9-to-RJ45
adapter (Cabletron Part Number 9372066).

This feature supports two methods for activating the UPS monitoring as
follows:

• Using the Local Management, System Level screen of the EMME via
a system connected to the EMME console port.

• Using SPECTRUM Element Manager for Windows, SPECTRUM
Portable Management Application (SPMA), or SPECTRUM. These
software packages provide Graphical User Interfaces (GUI) to
configure the UPS.

1.14 EMME UPGRADES

To take advantage of enhanced EMME features, a Dynamic Random
Access Memory (DRAM) upgrade is required. These are DRAM modules
that are only available through Cabletron Systems. The DRAM modules
provide additional memory required to support the following:

– Routing – Matrix
– RMON MIB Host – Captive
– Hosts Top N – Filter Groups

Page 1-20 EMME USER’S GUIDE

EMME UPGRADES

To determine the upgrade required for a specific EMME, the EMME
board revision le vel must be kno wn. The re vision le vel can be found using
one of the following:

• Local Management, where it is shown on the Password screen

• MIB Navigator, described in Chapter 6
The OID used to determine the EMME revision is eMMEHRev, which is:

1.6.1.4.1.52.1.6.2.9.2

This is a read only function.

NOTE

Table 1-7 lists the EMME board revisions along with the associated
DRAM Upgrade Kits and their part number.

Table 1-7. EMME Boards and Associated DRAM Upgrade Kit.

EMME Board

Revision

05 and 07 Static Column 8MB-SC-UGK60
06, 08, and 09 Fast Page Mode 8MB-FPM-UGK60

DRAM Upgrade Kit

Type

8-MB DRAM

Part No.

Revisions 04 and below do not support a SIMM socket.

NOTES

The EMME only supports Static Column and Fast Page
Mode DRAM from Cabletron Systems.

EMME USER’S GUIDE Page 1-21