Enterasys Networks 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 Enterasys
Networks 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 ENTERASYS NETWORKS 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 ENTERASYS NETWORKS HAS BEEN ADVISED OF, KNOWN, OR
SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES.
Virus Disclaimer
Enterasys has tested its software with current virus checking technologies. However, because no
anti-virus system is 100% reliable, we strongly caution you to write protect and then verify that the
Licensed Software, prior to installing it, is virus-free with an anti-virus system in which you have
confidence.
Enterasys Networks makes no representations or warranties to the effe ct that the Lice nsed Software is
virus-free.
Copyright 2000 by Enterasys Networks. All rights reserved.
Printed in the United States of America.
Order Number: 9032895-02 April 2000
Enterasys, NetSight, and Matrix E7 are tra demarks of Enterasys Networks.
SPECTRUM, MiniMMAC, FNB, Multi Media Access Center, and DNI are registered trademarks,
and Portable Management Application, IRM, IRM2, IRM3, IRBM, ETSMIM, EFDMIM, EMME,
ETWMIM, FDMMIM, FDCMIM, MRXI, MRXI-24, NB20E, NB25E, NB30, NB35E, SEHI, TRBMIM,
TRMM, TRMMIM, TRXI, Media Interface Module, MIM, and Flexible Network Bus are
trademarks of Cabletron Systems, Inc.
UNIX and OPENLOOK is a trademark of Unix System Laboratories, Inc. OSF/Motif and Motif are
trademarks of the Open Software Foundation, Inc. X W i ndow System is a trademark of Massachusetts
Institute of Technology. Ethernet and XNS are trademarks of Xerox Corporation. Apple and
AppleTalk are registered trademarks of Apple Computer, Inc. Banyan is a registered trademark of
Banyan Systems, Inc. DECnet is a registered trademark of Digital Equipment Corporation. Novell is a
registered trademark of Novell, Inc. CompuServe is a regis tered trademark of CompuServe. Sun Microsystems is a registered trademark, and Sun, SunNet, and Ope nWindows are trademarks of Sun
Microsystems, Inc.
i
Page 4
Restricted Rights Notice
(Applicable to licenses to the United States Government only.)
1.Use, duplication, or 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 DFARS
252.227-7013.
Enterasys Networks, 35 Industrial Way, Rochester, New Hampshire 03867.
2.(a) This computer software is submitted with restricted rights. It may not be used, reproduced, or
disclosed by the Government except as provided in paragraph (b) of this Notice or as otherwise
expressly stated in the contract.
(b) This computer software may be:
(1)Used or copied for use in or with the computer or computers for which it was acquired,
including use at any Government installation to which such computer or computers may
be transferred;
(2)Used or copied for use in a backup computer if any computer for which it w as acquired
is inoperative;
(3)Reproduced for safekeeping (archives) or backup purposes;
(4)Modified, adapted, or combined with other computer software, provided that the
modified, combined, or adapted portions of the derivative software incorporating
restricted computer software are made subject to the same restricted rights;
(5)Disclosed to and reproduced for use by support service contractors in accordance with
subparagraphs (b) (1) through (4) of this clause, provided the Government makes such
disclosure or reproduction subject to these restricted rights; and
(6)Used or copied for use in or transferred to a replacement computer.
(c) Notwithstanding the foregoing, if this computer software is published copyrighted computer
software, it is licensed to the Government, witho ut disclosure prohibitions, with the minimum
rights set forth in paragraph (b) of this clause.
(d) A ny other rights or limitations regarding the use, duplication, or disclosure of this computer
software are to be expressly stated in, or incorporated in, the contract.
(e) This Notice shall be marked on any reproduction of this computer software, in whole or in part.
ii
Page 5
Chapter 1Introduction
Using the MultiSwitch 700 Modules User’s Guide.................................................. 1-4
Related Manuals............................................................................................................ 1-6
Adding a New Connection...................................................................................6-4
Deleting a Connection...........................................................................................6-5
Chapter 7WAN Configuration
About the DELHW-UA............................................................................................ ....7-1
WAN Redundancy................................................................................................. 7-3
The WAN Logical View................................................................................................7-4
Changing WAN Logical Settings.........................................................................7-5
Index
vi
Page 9
Chapter 1
Introduction
About the MultiSwitch 700; how to use this guide; related guides; software conventions; getting help
Welcome to the MultiSwitch 700 Modules User’s Guide. We have designed this
guide to serve as a reference for using NetSight Element Manager for the
MultiSwitch 700 product, which encompasses the DLM6C-AA cha ssis and the
MultiSwitch 700 modules.
The MultiSwitch 700 product encompasses the DLM6C-AA chassis and the
MultiSwitch 700 modules. The DLM6C-AA hub is a stand-alone chassis that
offers five slots for interface modules; it also has two slots for dual redundant
power supplies (installed vertically to the right of the module slots), and a
removable fan tray (installed horizontally ac ross the botto m the chassis).
At the heart of the MultiSwitch 700 is its Frame Transfer Matrix (FTM) backplane
and distributed processing power. The FTM’s passive design provides a separate
independent backplane connection from each module in the chassis to every other
module installed in the chassis; each module contains its own active switching
components (so switching horsepower increases with module density), and each
module can be managed independently (via its Module Manager management
component) or — for devices which support distributed management — as part
of the chassis unit (via a sing le chassis IP/MAC address pair and the Chassis
Manager management component).
There are several varieties of MultiSwitch 700 modules currently available:
•The DLE22-MA and DLE23-MA modules each provide 24 fixed 10Base-T
switch ports (via RJ45 connectors on the DLE22-MA; RJ21 Telco connectors on
the DLE23-MA) and two slots for optional Fast Ethernet port interface
modules. Several Fast Ethernet port interface modules are available:
-the DELFX-UI, which provides one multi-mode fiber port via an SC
connector;
-the DELTX-UI, with one Category 5 UTP RJ45 connector;
-and the DELF3-UI, with one single-mode fiber port via an SC connector.
1-1
Page 10
Introduction
•The DLE32-MA and DLE33-MA modules each provide 24 fixed 10Base-T
switch ports (via RJ45 for the DLE32-MA and RJ21 for the DLE33-MA) and one
slot for an optional modular interface that can link the chassis to an FDDI,
ATM, WAN, or Gigabit Ethernet backbone. Each modular interface provides
frame translation between ATM, FDDI, WAN, Gigabit Ethernet, and Ethernet
through an on-board Intel i960 processor:
-The DELHF-UA is an FDDI/Ethernet Translator, which can act as a Sin gle
Attached Station (SAS) or Dual Attached Station (DAS) on an external
FDDI ring. FDDI Port Interface Modules provide a wide range of media
connectivity to the ring. The DELHF-UA also has full-duplex capability,
allowing for a 200 Mbps connection to another DELHF-UA.
-The DELHA-UA is an Asynchronous Transfer Mode (ATM) modular
interface, which provides an ATM uplink via two media-configurable
AT M Port Interface Modules. The dual port interface module design
allows for a redundant connection to the uplink, so that if the primary
interface fails, the secondary interface will automatica lly take over. The
DELHA-UA acts as an ATM Forum LAN Emulation Client (LEC) so that
it can transfer data between devices on an 802.x LAN supported by the
MultiSwitch 700 and ATM-connected end stations across a high speed
AT M Link. The DELHA-UA adheres to the ATM Forum-approved LAN
Emulation (LANE) standard, which defines how end users that rely on
existing data communications technology and protocols can oper ate o ver
an ATM network without penalty.
NOTE
-The DELHW-UA is a Wide Area Networking (WAN) modular interface,
which can provide uplinks to WAN backbones and allow you to perform
seamless LAN to WAN switching. The DELHW-UA supports IP and IPX
bridging or routing services, including IP RIP . Multiple W AN connectivity
options are supported, including Sync, T1, E1, D&I, ISDN S/T, DDS, and
HDSL interfaces, through the use of two configurable WAN port interface
modules. Connectivity is available for Po int to Point Protocol (PPP), as
well as Frame Relay and Leased Lines. Each WAN port interface module
can act independently, allowing simultaneous communication, or
configured to provide redundant channels if desired.
Unlike other modular interfaces designed for the MultiSwitch 700 boards, the
DELHW-UA module functions as an independent intelligent device with its own IP
address. As such, it must be managed separately from the MultiSwitch 700 chassis and
the board on which it is installed.
The DELHW-UA’s WAN functionality is accessed from the DELHW-UA’s Device View.
See The DELHW-UA Device View, on page 2-75 of Chapter 2, The MultiSwitch 700
Device View, for instructions on launching the DELHW-UA Device View. Other
DELHW-UA Device View functions, such as finding a source address and changing the
device time and date, are also described there.
Chapter 7, WAN Configuration, provides information on configuring and managing the
WAN capabilities of the various port modules available for the DELHW-UA.
1-2
Page 11
Introduction
-The DELHG-UA and DELHL-UA are Gigabit Ethernet modular
interfaces, each of which provide a single Gigabit E thernet connection that
fully conforms to the IEEE P802.3z (D3.1) Draft Standard. The
DELHG-UA provides a single 1000Base-SX (short-wave) multimode fiber
optic SC interface, allowing for link distances of up to 500 meters. The
DELHL-UA provides a single 1000Base-LX (long-wave) single
mode/multimode fiber optic SC interface, allowing for link distances of
up to 3 kilometers.
•The DLE28-MA module provides 24 fixed Ethernet multi-mode fiber por ts via
ST connectors, plus a single slot for a modular interface.
•The DLE49-MA module provides 48 switched Ethernet ports via four RJ21
Telco connectors and a single modular interface slot.
•The DLE02-MA and DLE52-MA modules are 10/100 Fast Ethernet modules.
The DLE02-MA provides 24 ports via RJ45 connections. The DLE52-MA
provides 16 ports via RJ45 connections as well as a next-generation modular
interface slot, which can accept any of the previously detailed modular
interfaces, or the new DELVM-UA Gigabit Ethernet modular interface:
-The DELVM-UA is a Gigabit Ethernet module which provides two slots
for Gigabit Ethernet port interface modules of various media to offer
integrated Gigabit Ethernet uplink capability . The DELVM-UA can accept
the DELG1-UA, which offers one SC connector for MMF 1000Base SX
Gigabit Ethernet connectivity, the DELG9-UA, which offers one SC
connector for MMF or SMF 1000Base LX connectivity, or the DELG4-UA,
which offers one ANSI Fibrechannel style-2 connector for 150 Ohm STP
1000Base CX connectivity.
•The DLEHF-MA carrier module provides two Fast Ethernet port interface
module slots and two modular interface slots.
Each of these modules provide key mission-criti c al features such as redundant
links for load sharing, alarm th resholdi ng, broadcast storm control, port
redirecting for traffic analysis, traffic priority configuration, and full error
breakdown. Per-port RMON support is also provided. By default, these modules
perform traditional switching (or bridging); each ca n also be configured to
perform prestandard IEEE 802.1Q VLAN switching (a.k.a “port-based VLAN”
switching).
The DLM6C-AA MultiSwitch 700 chassis itself offers the following features:
•Slots for up to 5 double-wide 2.4" interface modules, with chassis-wide
support of up to 130 users. Each interface module is individually driven and
managed by on-board processors, including an onboard ASIC processor for
switching, and Intel i960 Host microprocessors for dedicated module
management.
•A Frame Transfer Matrix (FTM) backplane design, that provides a separate
independent backplane connection from each module in the chassis to every
other module installed in the chassis. This allo ws a backplane bandwidth
capacity of up to 3.2 Gbps.
1-3
Page 12
Introduction
•Support for redundant, load-sharing power supplies to provide fault
tolerance.
•Diagnostic LEDs for quick visual diagnosis of interface and device
performance; a single removable fan tray; a 19" footprint for ease of installation
in rack mounts; and front panel accessibility to all chassis components for easy
maintenance.
•A distributed chassis management design, in which each module in the chassis
can be managed via a single chassis IP/MAC address pair that is associated
with the chassis as a whole. Each installed module will respond to
management queries to the “Chassis Manager” component that use the chassis
IP/MAC address pair and a chassis-level community string (e.g., “public”).
In addition to the “Chassis Manager” component for the hub as a w hole, each
installed module supports its own “Mo d ule Manager” management
component that responds to the same chas sis IP/MAC pair and a uniquely
indexed module-level community string (e.g., “public.1” for module 1;
“public.2” for module 2, etc.).
Using the MultiSwitch 700 Modules User’s Guide
Each chapter in this guide describes one major functionality or a collection of
several smaller functionalities of the MultiSwitch 700 modules and the chassis in
which they are installed. This guide contains information about software
functions which are accessed directly from the device icon.
Because the modules share much of their functionality, they will be collectively
referred to as the MultiSwitch 700 modules. Where there are dif ferences, h owever,
each device will be named separately, as necessary. The information displayed in
many of the windows will differ slightly depending upon which type of device is
being managed; however, only a single window will be shown unless significant
differences in functionality exist.
Chapter 1, Introduction, provides a list of related documentation, describes
certain software conventions, and shows yo u ho w to c o nt a c t t h e Gl ob a l Technical
Assistance Center. It also briefly describes the MultiSwitch 700 modules and
chassis.
Chapter 2, The MultiSwitch 700 Device View, describes the visual display of the
MultiSwitch 700 chassis as a whole and explains how to use the mouse within the
Device View. It details all chassis-level management fun ctions, including Port
Redirect, Advanced Priority Configuration, and pre-standard 802.1Q port-based
VLAN configuration at the chassis level. It documents chassis-specific
information, including MIB-II System Group information, chassis IP and MA C
addresses, chassis clock information and uptime, power supply configuration and
status, fan operational status, and backplane configuration.
The chapter also details how each module is displayed in the chassis, and
explains how to access management menus from the module display and change
port status information. It explains how to manage the individual module by
1-4Using the MultiSwitch 700 Modules User’s Guide
Page 13
Introduction
monitoring the module’s system resources, finding a source address on the
module, establishing module-level port priorities, setting up broadcast
suppression on the device, and configuring the module’s front panel COM port
and any attached Uninterruptable Power Supply (UPS).
Also described in this chapter is the Device View f unctionality associated with the
DELHW-UA modular interface. Unlike other modular interfaces designed for the
MultiSwitch 700 boards, the DELHW-UA module functions as an independent
intelligent device with its own IP address. As such, it must be managed separately
from the MultiSwitch 700 chassis an d the boa rd on which it is installed.
Chapter 3, Statistics, describes the two statistics views available at the interface
level: MIB-II Interface statistics and RMON Ethernet statistics.
Chapter 4, Alarm Configuration, provides instructions for using both the Basic
and Advanced alarm applications to configure alarms and the events that notify
you that an alarm condition has occurred. The ability to automatically initiate a
SET or a series of SETs in response to an alarm — functionality provided by the
proprietary Actions MIB — is also described.
Chapter 5, FDDI Management, describes the Configuration, Connection Policy,
Station List, Performance, FDDI Statistics, and Fra me Translation selections
available when a DELHF-UA module is installed.
Chapter 6, ATM Configuration, discusses the ATM Connections window which
will appear if you have a DELHA-UA module installed in your device.
Chapter 7, WAN Configuration, describes the physical configuration of the
DELHW-UA modular interface, including port interface module options, and
explains the WAN Logical View window and its functions.
The SmartSwitch and MultiSwitch Chassis User’s Guide discusses how to
NOTE
configure the Mu ltiSwit ch 700 chass is using the Chassis Se tup view. It gives an overview
of MultiSwitch 700 management views and general module information, and discusses
changing the current view as well as the default view.
Related Manuals
The MultiSwitch 700 Mo dules Use r’s Guide is only part of a complete document
set designed to provide comprehensive information about the features available
to you through NetSight Element Manager. Other guides which include
important information related to managing the MultiSwitch 700 include:
For more information about the capabilities of the MultiSwitch 700, consult the
appropriate hardware doc u mentation.
Software Conventions
NetSight Element Manager’s device user interface contains a number of elements
which are common to most windows and which operate the same regardless of
which window they appear in. A brief description of some of the most common
elements appears below; note that the information provided here is not repeated
in the descriptions of specific windows and/or functions.
Common Window Fields
Similar descriptive information is displayed in boxes at the top of most
device-specific windows in NetSight Element Manager, as illustrated in
Figure 1-1.
IP Address
Figure 1-1. Sample Window Showing Group Boxes
Device
Name
Location
MAC
Address
1-6Software Conventions
Page 15
Introduction
Device Name
Displays the user-defined name of the device. The device name can be changed
via the System Group window; see the Gener ic SNMP User’s Guide for details.
IP Address
Displays the device’s IP (Internet Protocol) Address. This will be one of two
addresses:
•The Network IP address assigned to the MultiSwitch 700 chassis (if a
network-level IP address has been assigned to the module).
•The individual module IP address (if IP addresses have been assigned on a
per-module basis).
Both of these IP address are assigned via Local Management to the Host interface
of each module in the MultiSwitch 700 chassis. The IP addresses cannot be
changed remotely via NetSight Element Manager. Note that altho ugh each
interface on the MultiSwitch 700 module has its own MAC, or physical, address,
only a single IP address is assigned to the module or cha ssis as a whole.
Location
Displays the user-defined location of the device or chassis. The location is entered
through the System Group window; see the Generic SNMP User’s Guide for
details.
MAC Address
Displays t he manufa cturer-set MAC address associated with the network IP
address of the MultiSwitch 700 chassis, or the module IP address of the currently
monitored Multi Switch 70 0 module. No te that MAC addr esses ar e factory -set and
cannot be altered through management.
Using the Mouse
This document assumes you are using a Windows-compatible mouse with two
buttons; if you are using a three button mouse, you should ignore the operation of
the middle button when following procedures in this document. Procedures
within the NetSight Element Manager document set refer to these buttons as
follows:
Software Conventions1-7
Page 16
Introduction
Left Mouse Button
Right Mouse Button
Figure 1-2. Mouse Buttons
For many mouse operations, this document assumes that the left (primary) mouse
button is to be used, and references to activating a menu or button will not
include instructions about which mouse button to use.
However, in instances in which right (secondary ) m ouse button functionality is
available, instructions will explic itly refer to right mouse button usage. Also, in
situations where you may be switching between mouse buttons in the same area
or window, instru ctions may also explicitly refer to both left and right mouse
buttons.
Instructions to perform a mouse operation include the following terms:
•Pointing means to position the mouse cursor over an area without pressing
either mouse button.
•Clicking means to position the mouse pointer over the indicated target, then
press and release the appropriate mouse button. This is most commonly used
to select or activate objects, such as menus or b uttons.
•Double-clicking means to position the mouse pointer over the indicated
target, then press and release the mouse button two times in rapid succession.
This is commonly used to activate an object’s default operation, such as
opening a window from an icon. Note that there is a distinction made between
“click twice” and “double-click,” since “click twice” implies a slower motion.
•Pressing means to position the mouse pointer over the indicated target, then
press and hold the mouse button until the de scribed action is completed. It is
often a pre-cursor to Drag operations.
•Dragging means to move the mouse pointer across the screen while holding
the mouse button down. It is often used for drag-and-drop operations to copy
information from one window of the screen into another, and to highlight
editable text.
1-8Software Conventions
Page 17
Using Buttons
Introduction
The Cancel button that appears at the bottom of most windows allows you to exit
a window and terminate any unsaved changes you have made. You may also
have to use this button to close a window after you have made any necessary
changes and set them by clicking on an OK, Set, or Apply button.
An OK, Set, or Apply button appears in windows that have configurable values;
it allows you to confirm and SET changes you have made to those values. In some
windows, you may have to use this button to confirm each individual set; in other
windows, you can set several values at once and confirm the sets with one click
on the button.
The Help button brings up a Help text box with informat ion specific to the
current window. For more information concerning Help buttons, see Getting
Help, on page 1-9.
The command buttons, for example Bridge, call up a menu listing the wind ows,
screens, or commands available for that topic.
Any menu topic followed by ... (three dots) — for example Statistics... — calls up
a window or screen associated with that topic.
Getting Help
This section describes three different methods of getting help for questions or
concerns you may have while using NetSight Element Manager.
Using On-line Help
You can use the Help buttons to obtain information specific to a particular
window . When you click on a Help button, a window will appear which contains
context-sensitive on-screen documentation that will ass ist you in the use of the
windows and their associated command and menu options. Note that if a Help
button is grayed out, on-line help has not yet been implemented for the associated
window.
From the Help menu accessed from the Device View window menu bar, you can
access on-line Help specific to the Device View window, as well as bring up the
Chassis Manager window for reference. Refer to Chapter 2, The MultiSwitch 700
Device View, for information on the Device View and Chassis Manager
windows.
All of the online help windows use the standard Microsoft Windows help facility. If you
NOTE
are unfamiliar with this feature of Windows, you can select H
Start menu, or H
Manager window.
elp from the Windows
elp —>How to Use Help from the primary NetSight Element
Getting Help1-9
Page 18
Introduction
Accessing On-line Documentation
The complete suite of documents available for NetSight Element Manager can be
accessed via a menu option available from the primary window menu bar: Help —> Online Documents. If you chose to install the documentation when you
installed NetSight Element Manager, this option will launch Adobe’s Acrobat
Reader and a menu file, which provides links to all available documents.
If you have not yet installed the do cumentation, th e Online Documents option will not
TIP
be able to access the menu file; in order to activate this option, you must run the setup.exe
again to install the documentation component. See your Installation Guide for details.
Getting Help from the Global Technical AssistanceCenter
If you need technical support related to NetSight Element Manager, contact the
Global Technical Assistance Center via one of the following meth ods:
By phone: (603) 332-9400
24 hours a day, 365 days a year
By fax:(603) 337-3075
By mail:Enterasys Networks
Technical Support
35 Industrial Way
Rochester, NH 03867
By e-mail mail:support@enterasys.com
FTP:ftp.ctron.com (134.141.197.25)
Loginanonymous
Passwordyour e-mail address
By BBS:(603) 335-3358
Modem Setting8N1: 8 data bits, 1 stop bit, No parity
Send your questions, comments, an d suggestions regarding NetSight
documentation to NetSight Technical Communications via the following address:
Netsight_docs@enterasys.com
To locate product specific information, refer to the Enterasys Web site at the
following address:
http://www.enterasys.com
1-10Getting Help
Page 19
NOTE
Introduction
For the highest firmware versions successfully tested with NetSight Element Manager
2.2.1, refer to the Readme file available from the NetSight Element Manager 2.2.1 program
group. If you have an earlier version of firmware and experience problems running
NetSight Element Manager, contact the Global Techncical Assistance Center for upgrade
information.
Getting Help1-11
Page 20
Introduction
1-12Getting Help
Page 21
Chapter 2
The MultiSwitch 700 Device View
Information displayed in the Device View window; the logical Device View; the Chassis Manager
window; hub management functions
The MultiSwitch 700 Device View window is the main screen that immediately
informs you of the current configuration of your chassis via a graphical display of
the chassis front panel. The default Logical View shows the modules installed in
your chassis according to the physical slots they occupy, and displays the
condition of individual interfaces on those modules. The Device View window
serves as a single point of access to all other MultiSwitch 700 windows and
screens, which are discussed at length in the following chapters.
To access the MultiSwitch 700 Device View window, use one of the following
options:
Figure 2-1. MultiSwitch Device Icon
1. In any map, list, or tree view, double-click MultiSwitch 700 icon you wish to
manage. The Management Selection window, Figure 2-2, opens.
or
1. In any map, list, or tree view, click the device you wish to manage, and select
Manage—>Node from the primary window menu bar, or select the Manage
Node toolbar button. The Management Selection window, Figure 2-2,
opens.
or
1. In any map, list, or tree view, click the right mouse button once to select the
device you wish to manage.
2-1
Page 22
The MultiSwitch 700 Device View
2. Select Manage from the resulting menu. The Management Selection window,
Figure 2-2, opens.
Figure 2-2. The Management Selection Window
3. In the Management Selection window, select Device View, and click the OK
button. The MultiSwitch 700 Device View window, Figure 2-3, opens.
Viewing Device Information
The MultiSwitch 700 Device View window (Figure 2-3) provides a graphic
representation of the MultiSwitch 700 hub and the currently modeled
MultiSwitch 700 modules, including a color-coded port display which
immediately informs you of the current configuration and status of all the port
The module displays in its corresponding physical slot in the MultiS witch 700.
Slots are numbered from 1–5, from left to right in the chassis. The Device View
also will provide you with environmental status information about the fan tray
and power supplies installed in the chassis.
2-2Viewing Device Information
Page 23
The MultiSwitch 700 Device View
Module
information
General device
information
Chassis-specific
information
Figure 2-3. The MultiSwitch 700 Device View Window
Up to 22 ports can be displayed simultaneously on a module. If a module has a higher port
NOTE
density than 22 ports, arrows displays at the top and bottom of the port stack so that you
can scroll through the remaining ports.
Viewing Device Information2-3
Page 24
The MultiSwitch 700 Device View
General Device Information
In addition to the main interface display, the Device View window provides the
following device information:
IP
The Device View window title displays the device’s IP (Internet Protocol)
Address; this will be the MultiSwitch 700 module IP address used to define the
device icon. The IP address is assigned to the MultiSwitch 700 module via the
Device Configuration portion of Local Management; it cannot be changed via
NetSight Element Manager. Note that although each interface in the MultiSwitch
700 module has its own MAC, or physical, a ddress, only a single IP address is
assigned to the device.
Connection Status
This color-coded area i ndicates the current state of communication between
NetSight Element Manager and the MultiSwitch 700 module.
•Green indicates the MultiSwitch 700 module is responding to device polls
(valid connection).
•Magenta indicates that the MultiSwitch 700 module is in a temporary stand-by
mode while it responds to a physical change in the hub (such as when a
module is inserted). Note that module and port menus are inactive during this
stand-by state.
•Blue indicates an unknown contact status; polling has not yet been established
with the MultiSwitch 700 module.
•Red indicates the MultiSwitch 700 module is not responding to device polls
(device is off line, or device polling has failed across the network for some
other reason).
Chassis Type
The model of chassis — MultiSwitch 700—þin which the monitored
MultiSwitch 700 module is installed.
Location
A descriptive field you can use to identify where the chassis is physically located.
You can edit this field through the device’s System Group window; refer to the
Generic SNMP User’s Guide for details.
UpTime
The amount of time, in a days hh/mm/ss format, that the MultiSwitch 700
module has been running since the last start-up. Note that when distributed
chassis management is available, this field will indicate the time that the longest
active module has been running since start-up.
2-4Viewing Device Information
Page 25
The MultiSwitch 700 Device View
Port Status
Indicates the port status display selection currently in effect. The default port
status view is bridge status; if you have not changed the port status selection since
launching the Device View window, this field will display Default. For more
information about changing the port status display, see Port Status Displays, on
page 2-12.
MAC
Displays the manufacturer-se t MAC, or physical , address associated with the I P
address used to define the device icon. This will be the MAC address assigned to
the first interface detected on the MultiSwitch 700 module (although each
interface in the MultiSwitch 700 module has its own MAC address). MAC
addresses are factory-set and cannot be altered.
Boot Prom
The revision of BOOT PROM installed in the MultiSwitch 700 module.
Firmware
The revision of device firmware stored in the MultiSwitch 700 module’s FLASH
PROMs.
NOTES
Time
The current time, in a 24-hour hh:mm:ss format, set in the MultiSwitch 700
module’s internal clock.
Date
The current date, in an mm/dd/yyyy format, set in the MultiSwitch 700 module’s
internal clock.
NetSight Element Manager displays and allows you to set all dates with four-digit year
values. You can set the date and time by using the Edit Device Date and Edit Device Time options on the Device menu; see Setting the Device Date and Time, on page 2-72,
for details.
Viewing Device Information2-5
Page 26
The MultiSwitch 700 Device View
DLM6C-AA Chassis-specific Information
The Device View provides the following information about the DLM6C-AA
chassis in which the MultiSwitch 700 module is installed. There are four
color-coded fields which provide status information for the operation of the
power supplies and fan tray installed in the DLM6C-AA chassis.
Power Redundancy
The DLM6C-AA supports two power supply modules. Each supports a separate
AC input connector, so that two separate power sources can be used for the
chassis. Additionally, with two power supplies installed, the total load presented
by the DLM6C-AA and its installed modules is split 5 0/50 between the supplies
(+/- 5%). The Power Redundancy field displays whether or not the chassis is
currently configured for load sharing and power redundancy. Possible values are:
•Available (Green) — Two HA-205-XX power supply modules are installed in
the DLM6C-AA chassis.
•Not Available (Yellow) — Only a single HA-205-XX power supply module is
installed in the DLM6C-AA chassis. Note that when only a single power
supply module is installed, it must always be in power slot 1 (PS1).
PS #1/#2 Status
Indicates the state of any power supplies insta lled in the DLM6C-AA Chassis.
Possible states returned are:
•Not Available (Yellow) — No response has been returned from the device
regarding the power supplies.
•Normal (Gr een) — A power supply is installed and operatin g in the associated
power slot.
•Fault (Red) — The power supply in the associated power slot is not
operational.
•Not Installed (Blue) — The indicated power slot is not occupied by a power
supply.
Fan Tray Status
The DLM6C-AA supports a single, removable fan tray that has four fans. The tray
is hot swappable, so it can be removed without powering do wn the chassis. This
field indicates the status of the DLM6C-AA’s Fan Tray:
•Not Available (Yellow) — No response has been returned regard ing the fan
tray.
•Normal (Green) — A fan tray is installed and operational.
•Fault (Red) — One or more fans in the tray have failed.
•Not Installed (Blue) — The fan tray slot is not occupied. The chassis is in
danger of overheating if it continues to run without the fan tray installed.
2-6Viewing Device Information
Page 27
Menu Structure
By clicking on various areas of the MultiSwitch 700 Device View display, you can
access menus with device-, module-, and port-level options, as well as utility
applications which apply to the device. The following illustration display s the
menu structure and indicates how to use the mouse to access the various menus:
The MultiSwitch 700 Device View
For the Device menu:
• The FDDIStatistics option
displays if you have a
DELHF-UA module installed.
• The ATMConnections option
displays if you have a
DELHA-UA module installed.
• The VLAN option displays if
your device has been
configured to operate in
802.1Q mode.
• The PriorityConfiguration
option displays if your device
suppor ts 802. 1P Dynamic
Multicast Filtering/Priority
Queuing.
• The UPS option will only
appear if your COM port has
been configured for use with
an Uninterruptable Pow er
Supply.
Figure 2-4. MultiSwitch 700 Device View Menu Structure
Viewing Device Information2-7
Page 28
The MultiSwitch 700 Device View
The Device Menu
From the Device Menu, you can access the following selections:
evice Type displays a window containing a description of the device being
•D
modeled. See Device Type, on page 2-20, for details.
evice Find Source Address enables you to determine through which
•D
interface a specified MAC address is communicating by searching the repeater
Source Address Table (SAT) and the 802.1d bridge Filtering database. If the
specified MAC address is located, a list of interface(s) through which the given
address is communicating will be displayed. See Using Device Find Source
Address, on page 2-27.
•Edit Device T
ime and Edit Device Date allow you to set the MultiSwitch 700
module’s internal clock; see Setting the Device Date and Time, on page 2-72.
ystem Group allows you to manage the MultiSw itch 700 via SNMP MIB II.
•S
Refer to the Generic SNMP Management Guide for further information.
/F Summary lets you view statistics (displayed both graphically a nd
•I
numerically) for the traffic processed by each network interface on your
device. See Viewing I/F Summary Info rmation, on page 2-22, for details.
LAN option displays in the Device menu if your module is co nf igured to
•V
operate in 802.1Q mode. The windows launched via the V
LAN option allow
you to configure and operate port-based VLANs on the module. See 802.1Q
VLANs, on page 2-60, for details.
TM Connections option displaysif you have a DELHA-UA installed in your
•A
module. This launches a window which lets you configure Permanent Virtual
Circuits (PVCs) for the module. See Cha pter 6, ATM Configuration, for more
information.
•Port R
edirector launches a window that allows you to mirror — or r edir ect —
traffic received or transmitted at one port on your module to one or more other
ports, so that you can unobtrusively at tach network analyzers to ascertain
problems or trends in your data flow. For more information about using the
Port Redirector window, see Redirecting Traffic on the MultiSwitch 700
Module, on page 2-46.
•System
Resources displays information about the processor used on the
monitored MultiSwitch 700 module, as well as the amount of installed and
currently available FLASH memory, DRAM, and NVRAM. See The System
Resources Window, on page 2-57.
riority Configuration allows you to establish priority packet forwarding. For
•P
more information, see Priority Configuration, on page 2-48.
The Priority Configuration menu option only displays for modules that respond to any
NOTE
of NetSight Element Manager’s queries to the following OIDs:
ctPriorityExtPortStatus, ctPriorityExtMaxNumMACEntries, or
ctPriorityExtNumPktTypeEntries.
2-8Viewing Device Information
Page 29
The MultiSwitch 700 Device View
•Com Port Configuration allows you to configure the settings of the COM ports
on the MultiSwitch 700 module; see Configuring the COM Port, on page 2-29.
roadcast Suppression allows you to set a threshold on the number of
•B
broadcast packets issued from each port on the MultiSwitch 700 module when
it is operating in traditional switch (bridge) mode. See Broadcast Suppression,
on page 2-55.
•FDDI
•U
•Ex
The View Menu
The View menu lets you switch the front panel display between two graphic
representations of the device:
•The L
•The B
The Port Status Menu
The Port Status menu allows you to select the status information that will be
displayed in the port text boxes in the Device View window:
Statistics option displays if you have a DELHF-UA installed in your
module. This launches a window which displays tra ffic-related statistics for
each Station Management (SMT) entity present on an installed DELHF-UA.
See Chapter 5, FDDI Management, for more information.
PS brings up a window that allows you to configure an Uninterruptable
Power Supply attached to your MultiSwitch 700 Module’s COM port. See
Using an Uninterruptable Power Supply (UPS), on page 2-43, for details.
it closes the MultiSwitch 700 Device View window.
ogical view provides the logical front panel display of the MultiSwitch
700 module and its interfaces.
ackPlane Config view displays the backplane connections between the
MultiSwitch 700 module and other modules installed in the DLM6C-AA
chassis.
tatus allows yo u to select one of four status type displays: Bridge, Bridge
•S
Mapping, Ad
oad will display the portion of network load processed per polling interval
•L
by each interface, expressed as a percentage of its theoretical maximum load
(10, 100, 155.5, 800, or 1000 Mbps).
rrors allows you to display the number of errors detected per polling interval
•E
by each interface, expressed as a percentage of the total number of valid
packets processed by the interface.
•I/F M
•I/F Sp
•I/F T
apping will display the interface ifIndex associated with each port on
your MultiSwitch 700 module.
eed will display the port’s bandwidth: 10M (megabits) for Ethernet;
100M for Fast Ethern et; 1.00 G for Gigabit Ethernet; 15 5.5M for A TM; and 8 00M
for the backplane interfaces.
ype will display the port type of each port on your MultiSwitch 700
module, e.g., Eth (ethernet-csmacd), ATM, or FDDI.
min, or Operator.
Viewing Device Information2-9
Page 30
The MultiSwitch 700 Device View
For more information on the port display options available via this menu, see
Selecting a Port Status View, on page 2-12.
DDI Menu
The F
If your MultiSwitch 700 has an installed DELHF-UA, the FDDI men u displays on
the Device View menu bar, with the following options:
•Configuration
•Connection Policy
•Station List
•Performance
•Frame Translation
Refer to Chapter 5, FDDI Management, for information on these menu selections.
The Utilities Menu
The Utilities Menu provides the following options:
•MIB Tools, which provides direct access to the MultiSwitch 700 module’s MIB
information; refer to the Tools Guide for more information.
•RMON utility, a remote monitoring feature that is supported on a per-port
basis when at least one Ethernet or Fast Ethernet module is installed in the
chassis; refer to the RMON User’s Guide for more information.
These selections are also available from the Tools menu at the top of the primary
NetSight Element Manager window.
The Help Menu
The Help Menu has the following three selections:
IBs Supported brings up the Chassis Manager window. See The Chassis
•M
Manager Window, on page 2-18.
hassis Manager Help brings up a help window with information specifically
•C
related to using the Chassis Manager and Device View windows.
bout Chassis Manager brings up a version window for the Chassis Manager
•A
application in use.
The Module Menu
The Module menu for the MultiSwitch 700 module provides mostly
bridging-related selections, many of which are also available from the Bridge
Status window:
odule Information opens a Module Information wi ndow that provides
•M
firmware and manufacturing informatio n which may be useful when
troubleshooting any problems that you are having with the module. For more
information, refer to The Module Information Window, on page 2-19.
•Module Type brings up a window containing a description of the selected
module; see Viewing Hardware Types, on page 2-20.
2-10Viewing Device Information
Page 31
The MultiSwitch 700 Device View
•Bridge Status opens a window that provides an overview of bridging
information for each port, and allows you to access all other bridge-rel ated
options. Refer to the Bridging chapter in the Tools Guide for more information.
roadcast Suppression allows you to set a threshold on the number of
•B
broadcast packets issued from each port on the MultiSwitch 700 module when
it is operating in traditional switch (bridge) mode.
•Device Find Source Address enables you to determine through which
interface a specified MAC address is communicating by searching the repeater
Source Address Table (SAT) and the 802.1d bridge Filtering database. If the
specified MAC address is located, a list of interface(s) through which the given
address is communicating will be displayed. See Using Device Find Source
Address, on page 2-27
•Performance Graph visually displays the combined performance of all
bridging interfaces installed in the MultiSwitch 700 module; refer to the
Bridging chapter in the Tools Guide for more information.
•Spanning Tree allows you to set bridge parameters when it is operating using
the Spanning Tree Algorithm (STA) — the method that bridges use to decide
the controlling (root) bridge when two or m ore bridges are in para llel. Refer to
the Bridging chapter in the Tools Guide for more information.
•SmartTrunk invokes the SmartTrunk Configuration and Status Screen, which
enables you to group interfaces logically to achieve greater bandwidth
between devices, if both devices support the SmartTrunk feature. There is no
limit to the number of ports that can be included in a single “trunk,” nor is
there a limit to the number of trunked “instances” that can be supported. Refer
to the Bridging chapter in the Tools Guide for more information.
•Filtering Database lets you see and configur e the contents of the 802.1d bridge
Static and Filtering Databases. Refer to the Bridging ch apter in the Tools Guide
for more information.
•Duplex Modes allows you to set Duplex Mode operation for standard
Ethernet interfaces.
•Enable/Disable Bridge enables or disables bridging across every interface
installed in the MultiSwitch 700 module.
The Port Menus
Each port menu offers the following selections:
•Connection Type displays a text description of the connection type of the
selected interface. This menu option appears if the device supports the
ctIfConnectionType OID. See Viewing Hardware Types, page 2-20, for details.
•Description displays a text description of the selected port. See Viewing
Hardware Types, on page 2-20, for details.
Viewing Device Information2-11
Page 32
The MultiSwitch 700 Device View
•Performance Graph brings up windows that visually display bridging
performance at the selected interface; r efer to the Bridging chapter in the Tools Guide for more information.
•Source Addressing allows you to view the source MAC addresses
communicating through the currently selected interface.
•I/F Statistics launches a window that displays MIB-II interface statistics for the
selected interface. See Chapter 3, Statistics, for more info rmation.
•Configuration allows you to configure Ethernet ports for Standard or Full
Duplex Mode, or configure operational parameters for Fast Ethernet ports,
depending on the type of interface selected.
•Alarm Configuration la unches the RMON- based Basic and A dvanced Alarm
applications; see Chapter 4, Alarm Conf iguration, for details. This selection is
available for all bridge port interfaces — even those (like ATM) that do not
specifically support RMON functionality — as long as at least one Ethernet or
Fast Ethernet port is on the module.
•Statistics launches the highest level of statistics currently available for the
selected port. For standard Ethernet and Fast Ethernet ports, RMON sta tistics
will be displayed if the RMON Default MIB component is active; if it has been
disabled, MIB-II interface statistics will display. See Chapter 3, Statistics, for
more information.
•Enable/Disable Port activates or disables bridging for the selected port,
respectively; refer to the Bridging chapter in the Tools Guide, and Enabling
and Disabling Ports, on page 2-74, for more information.
Port Status Displays
When you open the Logical View of the chassis, each port will display its current
bridging state (defined below) by default; to change this status display, select one
of the options on the Port Status menu, as described in the following sections.
Selecting a Port Status View
To change the status view of your ports:
1. Click on P
menu opens.
2. Drag down (and to the right, if necessary) to select the status information you
want to display. The port text boxes will display the appropriate status
information.
ortStatus on the menu bar at the top of the Device View window; a
2-12Viewing Device Information
Page 33
The MultiSwitch 700 Device View
Port status view options are:
tatus
S
You can view four port status categories, as follows:
ridge — FWD, DIS, LRN, LIS, BLK, or BRK
•B
•Bridge Mapping — the instance of the physical interface associated with a
bridge port
•Ad
•O
If you have selected the Bridge status mode, a port is considered:
•FWD (Forwarding) if the port is on-line and ready to forward packets across
•DIS (Disabled) if bridging at the port has been disabled by management; no
min — ON or OFF
perator — ON or OFF
the MultiSwitch 700 from one network segment to another. Note that this is
also the default display for ports which are administratively enabled but not
connected.
traffic can be received or forwarded on this port, including configuration
information for the bridged topology.
•LIS (Listening) if the port is not adding inf ormation to the filtering database. It
is monitoring Bridge Protocol Data Unit (BPDU) traffic while preparing to
move to the forwarding state.
•LRN (Learning) if the Forwarding database is being created, or the Spanning
Tree Algorithm is being executed because of a network topology change. The
port is monitoring network traffic, and learning network addresses.
•BLK (Blocking) if the port is on-line, but filtering traffic from going across the
MultiSwitch 700 from one network segment to another. Bridge topology
information will be forwarded by the port.
•BRK (Broken) if the physical interface has malfunctioned.
If you have selected the Bridge Mapping status mode, the port display will alter
to show the dot1dBasePortIfIndex, which is the va lue of the instance of the in terface
index (the MIB II ifIndex) that corresponds to each bridge/switch port on the
device. For a MultiSwitch 700 module, the dot1dBasePortIfIndex of the bridge
interfaces will map directly to the ifIndex.
If you have selected the Admin status mode, a port is considered:
•ON if the port is enabled by management.
•OFF if it has not been enabled or if it has been disabled through management
action.
The Admin state reflects the state requested by management; depending on the
circumstances, this may or may not match the current Operator status, described
below.
Viewing Device Information2-13
Page 34
The MultiSwitch 700 Device View
If you have selected the Operator status mode, a port is considered:
•ON if the port is currently forwarding packets.
•OFF if the port is not currently forwarding packets.
Note that the Operator status provides the actual status of the port; depending on
the circumstances, this may or may not reflect the Admin state currently requested
by management. For example, ports which are administratively ON but not yet
connected would display an Operator status of OFF, since no packets are being
forwarded.
oad
L
If you choose Load, the interface text boxes will display the percentage of
network load processed by each port during the last polling interval. This
percentage reflects the network load generated per polling interval by devices
connected to the port compared to the theoretical maximum load (10, 100, 155.5,
800, or 1000 Mbps) of the connected network.
rrors
E
If you choose the Errors mode, the interface boxes will display the percentage of
the total number of valid packets processed by each port during the last polling
interval that were error packets. This percentage reflects the number of errors
generated during the last polling interval by devices connected to that port
compared to the total number of valid packets processed by the port.
NOTE
The polling interval is set using the Device Management page of the Options window,
accessed via the T
ools —> Options selection from the main menu bar. Refer to the
User’s Guide for information on setting node polling intervals.
apping
I/F M
If you choose the I/F Mapping mode, the interface boxes will display the interface
number (ifIndex) associated with each port on the MultiSwitch 700 module.
eed
I/F Sp
If you choose the I/F Speed mode, the interface boxes will display the bandwidth
of each individual port on the MultiSwitch 700 module: 10M (megabits) for
standard Ethernet; 100M for Fast Ethernet, 155.5 M for ATM, 800M for a
backplane interface, and 1.00 G for Gigabit Ethernet.
ype
I/F T
If you choose the I/F Type mode, the interface boxes will display the network
type supported by each interface on the MultiSwitch 700 module, e.g., Eth
(ethernet-csmacd), ATM, or FDDI. Note that there is no type distinction between
standard Ethernet, Fast Ethernet, and Gigabit Ethernet.
2-14Viewing Device Information
Page 35
Port Status Color Codes
Three of the Port Status display options — Bridge, Admin, and Operator —
incorporate their own color coding schemes: for the Bridge option, green = FWD,
blue = DIS, magenta = LIS or LRN, orange = BLK, and red = BRK; for Admin and
Operator, green = ON, red = OFF, and blue = N/A (not available).
For all other Port Status selections — Bridge Mapping, Load, Errors,
I/F Mapping, I/F Speed, and I/F Type — color codes will continue to reflect the
most recently selected mode which incorporates its own color coding scheme.
The Chassis Backplane View
By default, the Device Vi ew window displays the Logical View of the DLM6C-AA
Chassis and an installed MultiSwitch 700 module. The Logical View provides port
status information and access to device-, module-, and port-level menus, as
described above. You can also display the Chassis Backplane View. The Chassis
Backplane View of the hub indicates the five point-to-point backplane
connections between the monitored MultiSwitch 700 module and other modules
in the chassis. The Backplane View also lets you disable those backplane
connections.
The MultiSwitch 700 Device View
The Chassis Backplane View, Figure 2-5, indicates the operational status of the
five point-to-point backplane connections between the monitored MultiSwitch
700 module and other modules in th e chassis slots. It also lets you enable or
disable the backplane connections to other modules in the chassis.
To access the Chassis Backplane View:
1. Click on V
2. Select B
iew in the menu bar to access the View menu.
ackPlane Config. The Chassis Backplane View, Figure 2-5, opens.
Viewing Device Information2-15
Page 36
The MultiSwitch 700 Device View
From the Backplane View you can display
the device interfaces
with respect to their
bridging status or
their MIB II Interface
status. The currently
selected Port Display
Form is shown in the
label above the
interfaces.
Below the Port
Display Form label,
the interfaces appear
according to the
currently selected
Display Form. In the
Bridge display form,
you can access
management options
for the individual
interfaces.
To change the display form
between Bridge and
Interface, click on the label
and select the desired
display form from the
resulting menu. Bridge is
the default display form.
When the disp lay form is i n Brid ge mode,
clicking on an interface will result in a
menu, offering various options applicable
to the selected backplane interface. For
information on enabling or disabling the
interface using the Enable... or Disable...
options, see Enabling or Disabling a
Backplane Interface, on page 2-18. For
details on the remaining menu options,
refer to their entries in The Port Menus,
on page 2-11.
Figure 2-5. The MultiSwitch 700 Module Backplane Device View
2-16Viewing Device Information
Page 37
The MultiSwitch 700 Device View
The backplane connections are indexed 1–5, where 1 indicates the connection to
first slot in the chassis and 5 indicates the connection to the last slot.
Backplane View Bridge Display Form
When the Backplane View display form is in the default Bridge mode, each
connection is represented by a color-coded text field as follows:
FWD (Green) The interface is on-line and ready to forward packets
across the MultiSwitch 700 from one module to another.
DIS (Blue) Bridging at the interface has been disabled by
management; no traffic can be received or forwarded on
this interface, including configuration information for
the bridged topology.
LIS (Magenta) The interface is not adding information to the filtering
database. It is monitoring Bridge Protocol Data Unit
(BPDU) traffic while preparing to move to the
forwarding state.
LRN (Magenta) The Forwarding database is being created, or the
Spanning Tree Algorithm is being executed because of a
network topology change. The interface is monitoring
network traffic, and learning network addresses.
BLK (Orange) The interface is on-line, but filtering traffic from going
across the MultiSwitch 700 from one module to another.
Bridge topology information will be forwarded by the
interface.
BRK (Red)The interface has malfunctioned.
Backplane View Interface Display Form
When the Backplane V i ew is in Interfa ce m ode, each co nnection is r e pr esen ted by
a color-coded text field that indicates a combination of the interface’s
Administrative status, Operational status, and Link status.
The following status conditions are supported:
UNK (Gray)NetSight Element Manager cannot determine the
backplane interface’s Administrative, Operational, or
Link status.
ON (Green)The backplane interface is operational (up) and
administratively enabled. Link status is linked, or not
applicable to the interface.
Viewing Device Information2-17
Page 38
The MultiSwitch 700 Device View
ON (Yellow)The backplane interface is operational (up) and
OFF (Blue)The interface is not operational, and prior to going down
OFF (Red)The interface is not operational, but prior to going down
TEST (Magenta)The interface is in some test operational state.
--- (Gray)The backplane interface is that associated with the slot in
Enabling or Disabling a Backplane Interface
You can enable or disable a backplane interface as follows:
1. With the display form in Bridge mode, click on the backplane interface which
you wish to enable or disable. A menu opens.
administratively enabled; however, the interface link
status is Not Linked (NLK).
it was also administratively disabled.
it was in an administratively enabled state.
which the currently monitored MultiSwitch 700 module
is installed.
2. Select Enable or Disable, as desired.
The MultiSwitch 700 firmware will not allow you to disable the oper ati onal status of an
TIP
interface supporting your active network connection. This applies to both backplane and
front panel interfaces. If you attempt to disable the backplane interface to the module that
is supporting your active network connection, you will receive a SET FAILED message.
The Chassis Manager Window
The MultiSwitch 700 modules draws its f unctionality from a collection of
proprietary MIBs and IETF RFCs, and organizes the MIB data into a series of
components. A MIB component is a logical grouping of MIB data, and each group
controls a defined set of objects. For example, MultiSwitch 700 module bridging
information is organized into its own component; Local Management (LIM) and
RMON are also contained in separate components. There is no one-to-one
correspondence between MIBs and MIB components; a single MIB component
might contain objects from several different proprietary MIBs and RFCs.
The Chassis Manager window, Figure 2-6, is a read-only window that displays the
MIBs and the MIB components — and, therefore, the functionality — supported
by the currently monitored device.
To view the Cha ssis Manager window:
1. Select Help—>MIBs Supported. The Chassis Manager window opens.
2-18Viewing Device Information
Page 39
The MIBs which provide
the MultiSwitch 700’s
functionality — both
proprietary MIBs and
IETF RFCs — are listed
here.
MIB Components are
listed here; remember,
there’s no one-to-one
correspondence between
MIBs and MIB
Components.
Figure 2-6. The Chassis Manager Window
The Module Information Window
The MultiSwitch 700 Device View
The Module Information window (Figure 2-7) displays system information, as
well as data provided by the PIC chip (Product Information Chip). The PIC chip,
which is updated each time a module is redesigned, maintains the manufacturing
data for the module and stores certain information such as the MAC addresses of
various components. Some devices will not return all the data displayed in the
Module Information window; these fields will remain blank.
To view the Module Information window:
1. Click on the desired module index. The Module menu displays.
2. Select M
opens.
odule Information. The Module Information window, Figure 2-7,
Figure 2-7. The Module Information Window
Viewing Device Information2-19
Page 40
The MultiSwitch 700 Device View
Firmware Version
The system description of the module, including its firmware revision number.
Boot Prom
The revision of boot PROM firmware in the module, including major version
number and minor revision number. The boot PROM provides power-on
diagnostics and download capability which enables the module’s system image
(which provides its runtime functionality) to be downloaded over the network.
Top Level Serial Number
The top level serial number of the module associated with this PIC chip which
provides encoded manufacturing date, location, serial number, and top level
revision number which can be used for troubleshooting information.
Base MAC Address
The base MAC address (in Ethernet format) assigned to the module.
SMB 1 Prom Version
This field is not applicable to the MultiSwitch 700 module. It will be blank.
Viewing Hardware Types
In addition to the graphical displays described above, menu options available at
the device and module levels provide specific information about the physical
characteristics of the MultiSwitch 700 hub and its in stalled modules.
Device T ype
Choosing the D
describes the management device being modeled.
Figure 2-8. Sample Device Type Window
Module Type
From the Module menus on the MultiSwitch 700 Device View window, you can
view a description of the Module types installed in your chassis.
evice Type option on the Device menu brings up a win dow that
1. Click on the desired module index. The Module menu displays.
2-20Viewing Device Information
Page 41
Connection Type
The MultiSwitch 700 Device View
2. Select Module T ype. A Module Type text box (similar to the example shown in
Figure 2-9) opens, describing the module type.
Figure 2-9. Sample Module Type Text Box
If your MultiSwitch 700 supports the ctIfConnectionT ype OID, its Port menus will
contain the Connection Type option. Selecting this option will display a window
that describes the selected interface’s connection type.
Figure 2-10. Sample Connection Type Windows
Interface Description
Choosing the Description option from the Port menu brin gs up a window that
describes the selected interface.
Figure 2-11. Sample Interface Description Windows
Viewing Device Information2-21
Page 42
The MultiSwitch 700 Device View
Viewing I/F Summary Information
The I/F Summary menu option available from the Device menu lets you view
statistics for the traffic processed by each network interface on your device. The
window also provides access to a detailed statistics window that breaks down
Transmit and Receive traffic for each interface.
To access the I/F Summary window:
1. From the Device View, click on the Device option from the menu bar.
2. Click ag ain to select I/F Summary. The I/F Summary window, Figure 2-12,
opens.
Figure 2-12. The I/F Summary Window
The I/F Summary window provides a variety of descriptive information about
each interface on your device, as well as statistics which display each interface’s
performance.
The following descriptive information is provided for each interface:
Index
The index value assigned to each interface on the device.
Type
The type of the interface, distinguished by the physical /lin k protoc ol( s) runni ng
immediately below the network layer. Possible values are fddi (for an installed
DELHF-UA), ethernet-csmacd (for standard, Fast Ethernet, and Gigabit Ethernet
front panel interfaces, as well as the backplane interfaces to the chassis), atm (for
an installed DELHA-UA), and Software LoopBack for the i960 Host Data port.
2-22Viewing Device Information
Page 43
Description
A text description of the interface: e.g., Ethernet Frontpanel (for the standard
Ethernet front panel interfaces), Fast Ethernet (for front panel Fast Ethernet
interfaces), FTM Backplane (for the backplane interfaces to the chassis), Host or Host Data Port for the on-board i960 Host interface, and ATM, or FDDI, for an
installed modular interface.
Physical Status
Displays the current physical status — or operational state — of the interface:
Online or Offline.
Logical Status
Displays the current logical status — or administrative state — of the interface:
Up or Down.
Interface Performance Statistics/Bar Graphs
The statistical values (and, where available, the accompanying bar graphs) to the
right of the interface description fields provide a quick summary of interface
performance. Y ou can select the statistical value you want to display and the units
in which you want those values displayed by using the two menu fields directly
above the interface display area, as follows:
The MultiSwitch 700 Device View
NOTE
1. In the right-most menu field, click on the down arrow and select the unit in
which you wish to display the selected statistic: Load, Raw Counts, or Rate.
Bar graphs are only available when Load is the selected base unit; if you select Raw
Counts or Rate, the Bar Graph column will be removed from the interface display.
2. Once you have selected the base unit, click on the down arrow in the left-most
field to specify the statistic you’d like to display. Note that the options available
from this menu will vary depending on the base unit you have selected.
After you select a new display mode, the statistics (and graphs, where applicable)
will refresh to reflect the current choice, as described below.
Raw Counts
The total count of network traffic received or transmitted on the indicated
interface since device counters were last reset. Raw counts are provided for the
following parameters:
In OctetsOctets received on the interface, including framing
characters.
In PacketsPackets (both unicast and non-unicast) received by the
device interface and delivered to a higher-layer protocol.
Viewing Device Information2-23
Page 44
The MultiSwitch 700 Device View
In DiscardsPackets received by the device interface that were
In ErrorsPackets received by the device interface that contained
In UnknownPackets received by the device interface that were
Out OctetsOctets transmitted by the interface, including framing
Out PacketsPackets transmitted, at the request of a higher level
Out DiscardsOutbound packets that were discarded by the device
discarded even though no errors prevented them from
being delivered to a higher layer protocol (e.g., to free up
buffer space in the device).
errors that prevented them from being delivered to a
higher-layer protocol.
discarded because of an unknown or unsupported
protocol.
characters.
protocol, by the device interface to a subnetwork address
(both unicast and non-unicas t ).
interface even though no errors were detected that
would prevent them from being transmitted. A possible
reason for discard would be to fr ee up buff er space in the
device.
Out ErrorsOutbound packets that could not be transmitted by the
device interface because they contained errors.
Load
The number of bytes processed by the indicated interface during the last poll
interval in comparison to the theoretical maximum load for that interface type
(10 Mbps for standard Ethernet; 100 Mbps for Fast Ethernet or FDDI; 155.5 Mbps
for ATM; 800 Mbps for a backplane port; 1000 Mbps for Gigabit Ethernet). Load is
further defined by the following parameters:
In OctetsThe number of bytes received by this interface, expressed
as a percentage of the theoretical maximum load.
Out OctetsThe number of bytes transmitted by this interface,
expressed as a percentage of the theoretical maximum
load.
When you select this option, a Bar Graph field will be added to the interface
display area; this field is only available when Load is the selected base unit.
Rate
The count for the selected statistic during the last poll interval. The available
parameters are the same as those provided for Raw Counts. Refer to the Raw
Counts section, page 2-23, for a complete description of each parameter.
2-24Viewing Device Information
Page 45
Viewing Interface Detail
The Interface Statistics window (Figure 2-13) provides detailed MIB-II interface
statistical information — including counts for both transmit and receive packets,
and error and buffering information — for each individual port interface.
Color-coded pie charts also let you graphically view statistics for both received
and transmitted Unicast, Multicast, Discarded, and Error packets.
To open the Interface Statistics window:
1. In the I/F Summary window, click to select the interface for which you’d like to
2. Click on Detail. The appropriate I/F Statistics window, Figure 2-13, opens.
The MultiSwitch 700 Device View
view more detailed statistics.
Figure 2-13. Detail Interface Statistics
You can also access this information via the I/F Statistics option available on the
TIP
individual port menus; see Chapter 3, Statistics, for more information.
Three informational fields appear in the upper portion of the window:
Description
Displays the interface description for the currently selected interface (e.g., Enet
Port, Fast Enet Port, FDDI, ATM, or Backplane Port).
Address
Displays the MAC (physical) address of the selected interface.
Viewing Device Information2-25
Page 46
The MultiSwitch 700 Device View
Type
Displays the interface type of the selected port: ethernet-csmacd, fddi, or atm.
The lower portion of the window provides the following transmit and receive
statistics; note that the first four statistics are also graphically displayed in the pie
charts.
Unicast
Displays the number of packets transmitted to or received from this interface tha t
had a single, unique destination address. These statistics are displayed in the pie
chart, color-coded green.
Non-Unicast
Displays the number of packets transmitted to or received from this interface tha t
had a destination address that is recognized by more than one device on the
network segment. The multicast field includes a count of broadcast packets —
those that are recognized by all devices on a segment. These statistics are
displayed in the pie chart, color-coded dark blue.
Discarded
Displays the number of packets which were discarded even though they
contained no errors that would prevent transmission. Good packets are typically
discarded to free up buffer space when the network becomes very busy; if this is
occurring routinely, it usually m eans that network traffic is overwhelming the
device. To solve this problem, you may need to re-configure your bridging
parameters, or perhaps re-configure your network to add additional bridges or
switches.
These statistics are displayed in the pie chart, color-coded magenta.
Error
Displays the number of packets received or transmitted that contained errors.
These statistics are displayed in the pie chart, color-coded red.
Unknown Protocol
Displays the number of packets received which were discarded because they were
created under an unknown or unsupported protocol.
Packets Received
Displays the number of packets received by the selected interface.
Transmit Queue Size
Displays the number of packets currently queued for transmission from this
interface. The amount of device memory devoted to buffer space, and the traffic
level on the target network, determine how large the output packet queue can
grow before the MultiSwitch 700 module will begin to discard packets.
Packets Transmitted
Displays the number of packets transmitted by this interface.
(Received only)
(Received only)
(Transmit only)
(Transmit only)
2-26Viewing Device Information
Page 47
The MultiSwitch 700 Device View
Making Sense of Detail Statistics
The statistics available in this window can give you an idea of how an interface is
performing; by using the statistics in a few simple calculations, it’s also possible to
get a sense of an interface’s activity level:
To calculate the percentage of input errors:
Received Errors /Packets Received
To calculate the percentage of output errors:
Transmitted Errors /Packets Transmitted
To calculate the total number of inbound and outbound discards:
Received Discards + Transmitted Discards
To calculate the percentage of inbound packets that were discarded:
Received Discards /Packets Received
To calculate the percentage of outbound packets that were discarded:
Transmit Discards /Packets Transmitted
The Interface Statistics window does not offer Disable or Test options. These options are
NOTE
available in the Interface Group window, which can be accessed via the System Group
window (select SUser’s Guide for information on the System Group and Interface Group windows.
ystem Group from the Device menu). Refer to your Generic SNMP
Using Device Find Source Address
When you select the Device Find Source Address option, the device’s 802.1D
Filtering database is searched for the specified MAC address. If it is found, the
Component field will display the value “Bridge” indicating that the address was
found on a bridging interface, and the Port Instance field will display the index
number assigned to the bridge port on which the address was located.
You may receive an error message stating “Can’t Display Source Address” if a Port
NOTE
Instance of “0” or “0.0” is reported. This value indicates that the MAC address is
communicating through the backplane instead of through a front panel interface.
Viewing Device Information2-27
Page 48
The MultiSwitch 700 Device View
The Device Find Source Address window can be accessed from the Chassis View
menu or the Module Index:
From the Chassis View:
1. Select Device—>Device Find Source Address.
From the Module Index:
1. Click on a module index to display the Module menu and select Device Find
Source Address.
The Device Find Source Address window, as shown in Figure 2-14, opens.
Figure 2-14. Device Find Source Address Window
The Device Find Source Address window displays the following information:
Component
Displays the type of interface through which the specified MAC address is
communicating. This field will report Bridge.
Port Instance
Displays the bridge port index number on which the specified MAC address was
found.
To use the Device Find Source Address window:
1. In the Address Mode field, select the format of the Source Address you wish
to find, either MAC or Canonical.
2. In the Enter Address text box, enter the Source Address you wish to find in
the appropriate XX-XX-XX-XX-XX-XX format.
2-28Viewing Device Information
Page 49
NOTE
NOTE
The MultiSwitch 700 Device View
If you enter the MAC format of a specified address, and then click on Canonical,
NetSight Element Manager will do the address conversion for you, from the Ethernet
hexadecimal format to the Token Ring Canonical format. The same is also true if you enter
the Canonical format of a speci fied address and then select MAC .
3. Click on the Find It! button. A “Processing Request” message displays in the
status bar at the bottom of the window.
If the specified MAC address is located, a list of the interface(s) through which the
given address is communicating displays in the lis t box. A status message at the
bottom of the window will displaythe number of interfaces through which the
given MAC address is communicating.
If the specified MAC address cannot be found, a “Source Address not found”
message displays.
If the MAC address is entered in an incorrect format, an “Invalid MAC Address.
Enter Valid MAC Address” message displays. Enter the address in the correct
XX-XX-XX-XX-XX-XX hexadecimal format.
Managing the Module
In addition to the performance and configuration information described in the
preceding sections, the Device View also provides you with the tools you need to
configure your MultiSwitch 700 module and keep it operating properly. Hub
management functions include setting operating parameters for Ethernet, FDDI,
Fast Ethernet, Gigabit Ethernet, and COM ports; managing an attached UPS;
redirecting traffic from one module interface to another; setting port priority
parameters; configuring transmission thresholds for broadcast packets; viewing
and configuring system resources; setting device date and time; and enabling and
disabling bridging at specific port interfaces.
Configuring Ports
The Configuration options available for FDDI, Ethernet, Fast Ethernet, Gigabit
Ethernet and COM ports allow you to configure operating parameters specific to
each port type: for FDDI and standard Ethernet ports, you can set the Duplex
Mode; for Fast Ethernet ports on first generation module s, you can set a variety of
duplex mode and negotiation parameters; for Fast Ethernet and Gigabit Ethernet
ports on second generation modules you can set speed, duplex mode, and flow
control parameters; and for COM ports, you can select the operation you wish the
port to perform, and set any associated speed parameters. FDDI, Ethernet, Fast
Managing the Module2-29
Page 50
The MultiSwitch 700 Device View
Ethernet and Gigabit Ethernet Port Configuration windows ar e available fr om the
Device View Port m enus; the COM Port option is available fro m the Device menu.
Note that no configuration option currently exists for ATM ports.
Configuring Standard Ethernet and FDDI Ports
The Port Configuration window available for both standard Ethernet and FDDI
ports allows you to set an interface to either Standard or Full Duplex Mode. Full
Duplex mode effectively doubles the available wire speed by allowing the
interface to both receive and transmit simultaneously. This window will also
display the mode currently in effect on the selected interface.
To access the Port Configuration Window:
1. Select the port you wish to configure. The Port Menu will display.
2. Click Configuration. The Port Configuration window, Figure 2-15, opens.
Figure 2-15. The Port Configuration Window
If you select the Configuration option available for a Fast Ethernet interface, an entirely
TIP
different window displays; see Configuring Fast E thernet Ports on First Generati on
Modules, on page 2-31, or Configuring Ethernet Ports on Second Gener ati on
Modules, on page page 2-36, for information on configuring these ports.
2-30Managing the Module
Page 51
WARNING
The MultiSwitch 700 Device View
For standard Ethernet interfaces, Full Duplex should only be enabled on an interface that
has a connection to a single destination address at the other end of the connection (i.e., it is
not a segment with an attached repeater cascading the connection to multiple destination
addresses).
Full Duplex mode disables the collision detection circuitry at the interface, so that both
Transmit and Receive wires can be used simultaneously. With a single destination address
at the other end of the connection (for example, if the connection was to a full duplex
interface on another switching module, or if a single file server was connected to the full
duplex switch port), this essentially doubles the available bandwidth from 10 Mbit/ sec to
20 Mbit/sec. The inter face at the other end of the conne ction must also have Full Dup l ex
enabled at the attached interface.
Full Duplex mode must be disabled if the interface is communicating with multiple
destinations simultaneous ly (i.e., if a repeater is cascaded from the interface), sinc e
Ethernet relies on Collision Sense for proper operation.
Similarly, an FDDI Full Duplex connection must also only be run point-to-point between
two supporting FDDI interfaces (e.g., another DELHF-UA), since the dual bandwidth is
attained by running data on both primary and secondary paths simultaneously. Since
Full Duplex overrides standard FDDI protocol (and eliminates ring redundancy), it will
not operate in a “ring” configuration, but only as a point-to-point high speed data trunk
between hubs. You must use Local Management to configure your DELHF- UA for Full
Duplex operation prior to making physical connections. Refer to your Local Management
Guide for more information.
Use the options in this window to select the desired mode:
Standard Mode
In Standard Mode, an interface can only either transmit or receive at any given
time, and must wait for one activity to be completed before switching to the next
activity (receive or transmit). In this mode, standard wire speeds (10 Mbps for
Ethernet, 100 Mbps for FDDI) are avail able.
Full Duplex
In Full Duplex Mode, an interface can both receive and transmit packets at the
same time, effectively doubling the available wir e speed to 20 Mbps (for Ethernet)
or 200 Mbps (for FDDI).
Be sure to click on Apply to set your changes; note that the interface’s current
mode can be determined by the field selected in the window.
Configuring Fast Ethernet Ports on First Generation Modules
The Port Configuration window available for Fast Ethernet ports on first
generation modules (e.g., a DELF3-UI, DELFX-UI, or DELTX-UI port interface
module) allows you to both view and set those ports’ available modes. All
100Base-TX Fast Ethernet ports can be configured to operate in either standard
Ethernet (10 Mbps) or Fast Ethernet (100 Mbps) mode, and in each mode can be
Managing the Module2-31
Page 52
The MultiSwitch 700 Device View
configured to operate in Full Duplex, effectively doubling the available wire
speed (from 10 to 20 Mbps in standard Ethernet mode, o r fr om 10 0 to 200 Mbps in
Fast Ethernet mode); 100Base-FX (fiber) ports ca n be configur ed to oper ate in their
standard 100 Mbps mode, or in Full Duplex mode. This window also displays the
mode currently in effect on the selected interface, and provides some information
(where it is available) about the interface’s link partner.
To access the Port Configuration Window:
1. Select the port you wish to configure; the Port Menu will display.
2. Click Configuration. The Fast Ethernet Port Configuration window,
Figure 2-16, opens.
Figure 2-16. The Fast Ethernet Port Configuration Window
Auto-Negotiation is not suppo rted by the DELFX-UI Fast Ethernet port interface
NOTE
module. If you launch the window for a port module slot which has no port interface
module installed, the Port Type will display as Unknown, the Link State will display No
Link, and the rest of the fields will be blank and/or grayed out.
2-32Managing the Module
Page 53
TIP
The MultiSwitch 700 Device View
If you select the Configuration option available for a standard Ethernet or FDDI interface
or for a Fast Ethernet port on a second generation module, an entirely different window
displays; see Configuring Standard Ethernet and FDDI Ports, on page 2-30, or
Configuring Ethernet Ports on Second Generation Modules, on page 2-36, for
information on configuring these ports.
From this window you can manually set the operational mode of the port, or —
for 100Base-TX interfaces — set the port to Auto-Negotiation so that the
appropriate operational mode can be determined automatically. The mode you
set will determine the speed of the port and whether it uses Full Duplex or
Standard Mode bridging.
The window displays the following information about the selected Fast Ethernet
port:
Port Type
Displays the port’s type: 100Base-TX RJ-45 (for built-in Fast Ethernet ports and
the DELTX-UI Fast Ethernet port interface module), 100Base-FX MMF SC
Connector (for the DELFX-UI Fast Ethernet port interface module), or Unknown
(for a port slot wi t h no mod u le in s talled).
Link State
Displays the current connection status of the selected port: Link or No Link.
Current Operational Mode
Indicates which of the available operational modes is curr ently in ef fect: 10Base-T,
10Base-T Full Duplex, 100Base-TX, 100Base-TX Full Duplex, 100Base-FX, or
100Base-FX Full Duplex. If the port is still initializing, not linked, or if there is no
port module installed in the slot, this field will remain blank.
Desired Operational Mode
Displays the operational mode that you have selected for this port, and allows
you to change that selection. The following op erational modes are available for
each port:
100Base-TXAuto-Negotiation, 10Base-T, 10BASE-T Full Duplex, 100Base-TX,
and 100Base-TX Full Duplex.
100Base-FX100Base-FX and 100Base-FX Full Duplex
Managing the Module2-33
Page 54
The MultiSwitch 700 Device View
If you choose to select a specific mode of operation (rather than auto-negotiation), you
!
CAUTION
should be sure that the link par tner supports the same mode. Otherwise, no link wi ll be
achieved.
If you select a Full Du plex mod e and t he link part ner supp orts th e same w ir e spee d but not
Full Duplex, a link will be achieved, but it will be unstable and will behave erratically.
If you select Auto-Negotiation, the local node will try to match the mode of the link
partner, even if the link partner is not set to auto-negotiate, and even if the local node
must use a mode which it is not currently advertising .
If Auto-Negotiation is the selected mode, the Current Operational Mode field
will indicate which mode was selected by the link partner. See Setting the
Desired Operational Mode, on page 2-35, for more information.
Advertised Abilities
For 100Base-TX ports which have been configured to ope rate in Auto-Negotiation
mode, this field allows you to select which of the operational modes available to
the port can be selected by the negotiating link partners.
NOTE
During Auto-Negotiation, each of the link partners will advertise all selected
modes in descending bandwidth order: 100Base-TX Full Duplex, 100Base-TX,
10Base-T Full Duplex, and 10Base-T. Of the selected abilities, the highest mode
mutually available will automatically be used. If there is no mode mutually
advertised, no link will be achieved.
If you have selected a specific operational mode for your 100Base-TX port, the
Advertised Abilities do not apply; the sel ect ed Advertised Abilities also do not
restrict the local node’s ability to set up a link with a partner who is not currently
Auto-Negotiating.
Auto-Negotiation is not currently supported for 100Base-FX ports.
Remote Capabilities
When the local node is set to Auto-Negotiation, this field will display the
advertised abilities of the remote link — even if the remote link is not currently set
to auto-negotiate. Possible values for this field are:
•100Base-TX Full Duplex
•100Base-TX
•10Base-T Full Duplex
•10Base-T
2-34Managing the Module
Page 55
NOTE
The MultiSwitch 700 Device View
•Link Partner does not support Auto-Negotiation — Auto-Negotiation is either
not supported by or is not currently selected on the remote port.
•Unknown — the link partner’s capabilities could not be determined.
When the local node is not set to Auto-Negotiation, this field will be grayed out,
even if the link partner is set to Auto-Negotiation and is advertising abilities.
If both link partners are set to Auto-Negotiation, but there is no mutually-advertised
operational mode, no link will be achieved, and both nodes may display the message “Link
Partner does not support Auto-Negotiation.” To resolve this situation, be sure both link
partners advertise all their abilities, or be sure they advertise at least one
mutually-available mode.
Setting the Desired Operational Mode
For any 100Base-TX port, you can specifically choose any one of the four available
operational modes, or you can select Auto-Negotiation mode, which allows the
port to negotiate with its link partner to find the highest mutually available
bandwidth. If you select Auto-Negotiation mode, you must also choose which of
the port’s bandwidth capabilities you wish to advertise to the link partner.
TIP
If you select Auto-Negotiation at both ends of a link, be sure at least one
mutually-advertised operational mode is available.
For a 100Base-FX port, the selection process is somewhat simpler;
Auto-Negotiation for these ports is not supported at this time, so you need only
choose between 100Base-FX standard mode and 100Base-FX Full Duplex.
However, you must still be sure that both link partners are set to the same
operational mode, or the link will be unstable.
To set your desired operational mode:
1. Click on the Desired Operational Mode combo box to display the menu of
available options; drag down to select the operational mode you wish to set.
For 100Base-TX ports, the available options are:
Auto Negotiation — the operational mode will be dynamically set based on
the modes selected in the Advertised Abilities field (where both link partners
are auto-negotiating) and the speeds and modes supported by the attached
device
10Base-T — 10 Mbps connection, Standard Mode
10Base-T Full Duplex — 10 Mbps connection, Duplex Mode
100Base-TX — 100 Mbps connection, Standard Mode
Managing the Module2-35
Page 56
The MultiSwitch 700 Device View
100Base-TX Full Duplex — 100 Mbps connection, Duplex Mode
For 100Base-FX ports, options are:
100Base-FX — 100 Mbps connection, Standard Mode
100Base-FX Full Duplex — 100 Mbps connection, Duplex Mode
2. If you have selected Auto-Negotiation (for 100Base-TX ports only), use the
Advertised Abilities field to select the operational capabilities you wish to
advertise to the port’s link partner. If both link partners will be
auto-negotiating, be sure there is at least one mutually-advertised operational
mode, or no link will be achieved.
The selected Advertised Abilities only come into play when both link partners are
TIP
auto-negotiating; if only one link partner is set to auto-negotiate, that node will establish a
link at whatever mode its partner is set to, even if that mode is not currently being
advertised.
3. Click Apply to save your changes. Click Refresh to display the new settings.
It may take a few minutes for mode changes to be completely initialized,
particularly if the link partners must negotiate or re-negotiate the mode; you
may need to refresh the window a few times before current operational data is
displayed.
Configuring Ethernet Ports on Second Generation Modules
The Ethernet Configuration window available for Fast Ethernet and Gigabit
Ethernet ports on second generation modules (e.g., DLE49- MA and DLE52-MA)
allows you to both view and set those ports’ available speed, modes, and flow
control. All second generation modules support the ctEthernetParameters MIB.
All Ethernet ports that return at least one instance for a query of the
ctEtherSupportedDuplex OID will use the Ethernet Configuration window as
shown in Figure 2-17.
All 100Base-TX Fast Ethernet ports can be configured to operate in either standard
Ethernet (10 Mbps) or Fast Ethernet (100 Mb ps) mode, and each mode can be
configured to operate in Full Duplex effectively doubling the available wir e speed
(from 10 to 20 Mbps in standard Ethernet mode, or from 100 to 200 Mbps in Fast
Ethernet mode). 100Base-FX (fiber) ports can be configured to operate in their
standard 100 Mbps mode, or in Full Duplex mode. 1000Base-SX/LX/CX Gigabit
Ethernet ports are always configured to operate in 1000 Mbps, Full Duplex mode.
This window displays the mode currently in effect on the selected interface, and
provides some information (where it is available) about the interface’s link
partner.
2-36Managing the Module
Page 57
The MultiSwitch 700 Device View
To access the Ethernet Configuration Window:
1. Select the port you wish to configure; the Port Menu will display.
2. Click Configuration. The Ethernet Configuration window, Figure2-16, opens.
Figure 2-17. The Ethernet Configuration Window
If you select the Configuration option available for a standard Ethernet or FDDI interface,
TIP
or for a Fast Ethernet port on a first generation module, an entirely different window
displays; see Configuring Standard Ethernet and FDDI Ports, page 2-30, or
Configuring Fast Ethernet Ports on First Generation Modules, page 2-31, for
information on configuring these ports.
From this window you can manually set the operational mode of the port, or —
for 100Base-TX and 1000Base-SX/LX/CX interfaces — set the port to Auto
Negotiate so that the appropriate operational mode can be determined
automatically. The mode you set will determine the port’s speed, duplex mode,
and flow control.
Managing the Module2-37
Page 58
The MultiSwitch 700 Device View
The window displays the following information about the selected Ethernet port:
Port Type
Displays the port’s type: 100Base-TX RJ-45or RJ71 (fo r built-in Fast Ethernet ports
and the FE-100TX Fast Ethernet port module), 100Base-FX MMF SC Connector
(for the FE-100FX Fast Ethernet port module), 1000Base-SX/LX/CX (for the
VHSIM-G6 Gigabit Ethernet port module), or Unknown (for a port slot with no
module installed).
Link State
Displays the current connection status of the selected port: Link or No Link.
Remote Auto Signal
Indicates whether the operating mode at the remote end of the link is set to Auto
Negotiate.
Auto Negotiate Config
Indicates whether Auto Negotiate signalling is in progress or has completed.
Possible values for this field are: configuring, complete, disabled, parallel detect
failed, or other.
!
CAUTION
Auto Negotiate Mode
Use this field to enable or disable Auto Negotiate for the port. If Auto Negotiate is
disabled, the port will use the speed, duplex mode, and flow control settings
specified in the Operational Mode fields. Note that 100-BaseFX ports do not
support Auto Negotiation; they must use the control settings specified in the
Operational Mode fields.
Operational Mode Fields
If the port is not set to Auto Negotiate then the settings in the Operational Mode
fields are used.
If you choose to select a specific mode of operation (rather than auto negotiation), you
should be sure that the link par tner supports the same mode. Otherwise, no link wi ll be
achieved.
For example, if you select Full Duplex mode and the li nk partner supports the sam e wire
speed but not Full Duplex, a link will be achieved, but it will be unstable and will behave
erratically.
If you select Auto-Negotiation, the local node will try to match the mode of the link
partner, even if the link partner is not set to auto-negotiate, and even if the local node
must use a mode which it is not currently advertising .
2-38Managing the Module
Page 59
The MultiSwitch 700 Device View
The Current Operational Mode settings indicate which of the available
operational modes is currently in effect. If Auto Negotiate is the selected mode,
the Current Operational Mode fields will indicate which mode was selected by
the link partner.
The Desired Operational Mode settings display the operational mode that is
currently selected for this port, and allows you to change the selection.
The following operational modes can be specified:
Speed
This field specifies a port speed of 10MB, 100MB, or 1000MB.
Duplex
This field specifies Half Duplex or Full Duplex mode for the port.
Flow Control
Flow control allows Ethernet devices to notify attached devices that congestion is
occurring and that the sending device should stop transmitting until the
congestion can be cleared. There are two commonly used methods of flow control:
Frame-based (operates on Full Duplex links) and Backpressure (operates on Half
Duplex links).
Ports set to Full Duplex mode have frame-based flow control, using pause
control frames. Frame-based flow control options are:
SymmetricThe port is able to both receive and transmit pause control
frames.
Asymmetric RX This option appears only for Gigabit Ethernet ports. The port
will receive pause control frames, but will not transmit its own.
Asymmetric TX This option appears only for Gigabit Ethernet ports. The port is
capable of sending pause control frames, but will not
acknowledge received pause co ntrol frames.
Disabled Disables flow control on the port.
Auto Negotiat e Ports configured to operate in auto negotiation mode will only
use pause control frames if the negotiation process determines
that the link partner supports them. Both ends of the link must
support auto negotiation and a common mode of operation.
Ports set to Half Duplex mode use Backpressure flow control. Backpressure flow
control simply asserts the carrier sense signal out the port causing the device
transmitting to detect a collision, stop trans mitting data, and send the jam signal.
Backpressure flow control options are enabled or disabled.
Managing the Module2-39
Page 60
The MultiSwitch 700 Device View
Setting the Desired Operational Mode
For any 100Base-TX port, you can configure operational modes, or yo u can select
Auto Negotiate mode, which allows the port to negotiate with its link partner to
find the highest mutually available bandwidth a nd flow control. If you select
Auto Negotiate mode, you must also choose which of the port’s bandwidth and
flow control capabilities you wish to advertise to the link partner (refer to Auto
Negotiation Technologies , page 2-40).
100Base-FX ports do not support auto negotiation for bandwidth or flow control
capability, so you must choose between 100Base-FX Half Duplex and 100Base-FX
Full Duplex mode, and set the flow control option. However, you must still be
sure that both link partners are set to the same operational mode, or the link will
be unstable.
For 1000Base-SX/LX/CX ports the speed and duplex modes are always
configured at 1000MB Full Duplex. However, you can select Auto Negotiate
mode, which allows the port to negotiate with its link partner to find the highest
mutually available bandwidt h and flow control. If you select Auto Negotiate
mode, you must also choose which of the port’s bandwidth and flow control
capabilities you wish to advertise to the link partner (refer to Auto Negotiation
Technologies, page 2-40).
NOTE
To set your desired operational mode:
1. Click on the Speed, Duplex, or Flow Control list box to display the menu of
available options; click to select the operational mode you wish to set.
If the port you are configuring does not support Flow Control, the Current Mode field will
display “not supported” and the Desired Mode list box will be disabled.
2. Click on the Apply button to save your changes.
Auto Negotiation Technologies
For ports which have been configured to operate in Auto Negotiate mode, this list
box allows you to select which of the operational modes available to the port will
be advertised to the negotiating link partner.
During Auto Negotiation, each of the link partners will advertise all selected
modes. Of the selected modes, the highest mode mutually available will
automatically be used. If there is no mode mutually advertised, no link wil l be
achieved.
2-40Managing the Module
Page 61
TIP
The MultiSwitch 700 Device View
If you select Auto-Negotiation at both ends of a link, be sure at least one
mutually-advertised operational mode is available.
If you have man ua l ly c on f i g ured specific operation al modes for your 100Base-TX
port or if you are configuring a 100Base-FX port, the Auto Negotiation
Technologies list box does not apply.
The Auto Negotiation Technologies list box has the following column heading s:
Advertised
This column specifies whether the operational mode listed in the far right column
of the list box will be advertised to the link partner. Only those operational modes
supported by the local port (those with a “yes” listed in the Local column) can be
advertised. Valid values are Enabled (the mode is supported and will be
advertised), Disabled (the mode is supported but will not be advertised), and
“---” (the mode is not supported).
Local
Indicates whether the operational mode listed in the far right column of the list
box is supported by the local port.
Remote
Indicates whether the operational mode listed in the far right column of the list
box is supported by the remote port.
Auto Negotiate Technology
This column lists possible opera tional modes.
Setting Advertised Abilities for Auto Negotiation
You can determine which operational mode supported by the local port will be
advertised to the negotiating link partner. Of the advertised modes, the highest
mode mutually available will automatically be used.
To advertise an operational mode:
1. In the list box, click on the operational mode of choice.
If the Advertised column had a value of Enabled, it will change to Disabled; a
value of Disabled will change to Enabled. If the Advertised column has a value
of “---”, then the value is not changed.
2. Click Apply to save your changes. Click Refresh to display the new settings.
It may take a few minutes for mode changes to be completely initialized,
particularly if the link partners must negotiate or re-negotiate the mode; you
may need to refresh the window a few times before current operational data is
displayed.
Managing the Module2-41
Page 62
The MultiSwitch 700 Device View
Configuring the COM Port
You can use the COM Port Configuration window (Figure 2-18) to specify the
functions that will be performed by the RS232 COM port on the fr o nt panel o f the
monitored MultiSwitch 700 module.
1. Click on D
2. Click on C
Port Configuration window, Figure 2-18, opens.
Figure 2-18. The COM Port Configuration Window
You can use the COM Port Configuration window to set th e fo llowing operating
parameters:
evice in the Device View menu bar to display the Device menu.
OM Port Configuration and then right to select Port 1. The COM
COM Port Admin
Use this field to administratively enable or disable the COM port.
COM Port Function
Use this field to select the function for which you wish to use the COM port:
LMLocal Management: select this option if you wish to connect a
terminal to the COM port from which to run Local Management.
UPSSelect this option if you wish to conn ect an uninterruptable
power supp l y (UPS) to the COM Port. N ot e t hat if you select this
option, an additional option — UPS — displays on the D evice
menu when you exit and re-enter device management; use the
resulting window to configure specific UPS settings.
SLIPSelect this option to use the COM port as a SLIP connection for
out-of-band SNMP management via direct connection to a serial
port on your network management workstation. Note that when
you configure the port as a SLIP connection, you must select the
desired baud rate in the Speed Selection field described below.
2-42Managing the Module
Page 63
NOTE
TIP
The MultiSwitch 700 Device View
PPPSelect this option to use the COM port as a PPP connection for
out-of-band SNMP management via direct connection to a serial
port on your network management workstation. Note that when
you configure the port as a PPP connection, you must select the
desired baud rate in the Speed Selection field described below.
Current MultiSwitch 700 firmware versions support only Local Managem ent and UPS
via the COM ports; future versions will add SLIP and PPP support. You will receive a
SET failed message if you attempt to configure the COM port for SLIP or PPP support.
Speed Selection
If you have configured the selected port as a SLIP or PPP connection, you must
select the appropriate baud rate: 2400, 4800, 9600, or 19,200. Note that this field
will default to Auto-Baud and become unselectable when the COM Port Function
is set to LM or UPS.
If the COM port you wish to configure is currently set to LM or UPS, the Speed
Selection field will be unavailable until the COM Port Function is set to SLIP or PPP
and that change is applied. Once available, the Speed Selection field will default to the last
known speed setting; use the down arrow to change this setting if necessary, then click the
Apply button again to complete the configuration.
To change the configuration of the selected COM port:
1. Click on to the right of each field, and select the desired setting.
2. Click on the Apply button to save your changes.
Using an Uninterruptable Power Supply (UPS)
Your MultiSwitch 700 supports the use of a UPS (uninterruptable power supply)
through its COM port (if configured through local management). (For more
information on the use of a UPS with the MultiSwitch 700, consult the
MultiSwitch 700 Installation Manual that was included when you purchased the
unit.) You can view or change the status of the UPS connected to your
MultiSwitch 700 at the UPS window.
Please note that the UPS window will on ly be active if you currently have a UPS
attached to your MultiSwitch 700 through the COM port, and you have correctly
set the Set UPS ID field.
Do not set the Set UPS ID field unless you have a UPS attached to the MultiSwitch 700,
WARNING
or you will disrupt your use of NetSight Element Manager.
Managing the Module2-43
Page 64
The MultiSwitch 700 Device View
Accessing the UPS Window
At the UPS window, you can configure the UPS ID model type for the
uninterruptable power supply you have attached to the COM port on your
device.
You can also view information concerning the UPS connected to your
MultiSwitch 700 including:
•The amount of time that your UPS has been running since the last start-up
•The line voltage and battery output
•The actual battery capacity of the UPS (dynamic bar graph)
You can also use a button at the bottom of the window to disconnect your UPS, or
you can use the Test option to initiate a self test of the un it.
To access the UPS window:
1. Click on D
2. Select U
evice in the menu bar to access the Device menu.
PS. The UPS window, Figure 2-19, opens.
Figure 2-19. The UPS Window
2-44Managing the Module
Page 65
The MultiSwitch 700 Device View
UPS ID
Displays the manufacturer and model typecode of the UPS attached to the COM
port of the MultiSwitch 700. You must assign this typecode for the UPS window
to be active. (See Setting the UPS ID, on page 2-46, for instructions for setting the
typecode for your UPS.) The valid typecodes are:
•Model 370
•Model 400
•Model 600
•Model 900
•Model 1250
•Model 2000
•Matrix 3000
•Matrix 5000
•SU 700
•SU 1400
•SU 2000XL
•Other
UPS Uptime
Displays the number of hours that the UPS has been operating since the last time
it was started up.
Line Voltage
Displays the voltage coming through the line attached to the MultiSwitch 700.
Battery Output
Displays the amount of battery output voltage.
Battery Capacity
Displays the percentage of remaining battery capacity (100% indicates a fully
charged battery).
Test Results
Displays the result of the last self-test performed by the UPS. The possible test
results are:
Unit OKThe UPS unit is in working order.
Unit FailedThe UPS unit has failed the self-test. Check the
unit for damage or consult your UPS User’s
Manual.
Bad BatteryThe UPS unit battery is bad.
No recent test No UPS self-test has been performed in the last
five minutes.
Unit in test...The UPS is currently in test mode.
Please standby
Managing the Module2-45
Page 66
The MultiSwitch 700 Device View
Setting the UPS ID
You need to set the UPS ID typecode that indicates the manufacturer and model
of the UPS.
To set the UPS ID:
1. Click on next to the SET UPS ID text box. A Model number menu displays.
Scroll to highlight the appropriate UPS ID. (Consult the manual that was
included when you purchased your UPS for the correct Model ID number.)
2. Click on the OK button. The UPS ID you have chosen displays in the text box,
and the UPS window will be active.
If your UPS unit does not function after you have set this ID, check the manual
you received with the UPS to ensure that you have chosen the correct UPS ID. If
you need to change the ID, follow the directions given above.
Using the Test Option
You can use the test option to activate a self-test cycle for your unit. This self-test
will check the viability of your unit and its battery.
To activate the test:
1. Click on the Test button. The unit will begin its self-test. The results of the test
displays in the Test Result text box next to the Test button.
Using the Disconnect Option
You can disc onnect the UPS attached to your MultiSw itch 700 through its COM
port, as follows:
1. Click on the Disconnect button near the bottom of the UPS window. Your
UPS will now be disconnected.
To reconnect, click OK button, or close, then re-open the UPS window.
Redirecting Traffic on the MultiSwitch 700 Module
The Port Redirector window (Figure 2-20) allows you to redirect traffic from one
or more interfaces directly to another interface — essentially mirroring the traffic
at the “redirect” interface. This feature is useful in that it allows you to use an
external analyzer on the “redirect” port to analyze data, without disturbing the
normal switching operations at the original source ports. The Port Redirector
window displays the interface remap table and allows you to add new entries to
and delete existing entries from this table. When you set a source port to redirect
to a destination port, the destination port will transmit out all packets received or
transmitted on the source port.
2-46Managing the Module
Page 67
To access the Port Redirector Menu:
The MultiSwitch 700 Device View
1. Click on D
2. Select Port R
evice in the Device View menu bar to display the Device menu.
edirector. The Port Redirector window, Figure 2-20, opens.
Figure 2-20. The Port Redirector Window
The current port mappings will be listed in this window. You may add entries to
or delete entries from this window.
To add an entry:
1. Next to the Source Module display box click on and select the desired
source module (Module X) from the drop down list.
2. Next to the Source Port display box click on and select the desired source
port (Port X) from the drop down list.
3. Next to the Destination Module display box click on and select the desired
destination module (Module X) from the drop down list.
4. Next to the Destination Port display box click on and select the desired
destination port (Port X) from the drop down list.
Managing the Module2-47
Page 68
The MultiSwitch 700 Device View
5. Click Add to add the redirect pair you have just configured to the list. The new
entry will now be displayed in the Current Active Entries list in this window and
the port traffic will begin to be redirected.
To delete an entry:
1. Click to highlight the entry line in the Current Active Entries list that you wish
to delete.
2. Click Delete to remove the redirect pair you have highlighted from the Current
Active Entries list. The entry will be deleted from the Current Active Entries list
and the traffic from the source port will not be redirected to the destination
port any longer.
Priority Configuration
The MultiSwitch 700 modules support priority packet forwarding. Priority packet
forwarding lets you designate certain packets to be of higher importance than
others, thereby allowing for the forwarding of these packets before packets of
lower priority. This function ality is essential for time-critical applications — such
as real-time video — on shared networks.
NOTE
The Priority Configuration me nu option will only appear in the Device menu for
modules that respond to any of NetSight Element Manager’s queries to the following
OIDs: ctPriorityExtPortStatus, ctPriorityExtMaxNumMACEntries, or
ctPriorityExtNumPktTypeEntries. If your module’s firmware does not respond to
these queries, contact the Global Call Center for firmware upgrade information.
Frame priority is enabled by the “tagging” of MAC frames so that they are given a
priority designation when they are forwarded by the MultiSwitch 700 module —
which is a tag-aware switch (i.e., one that adheres to the IEEE P802.1p and IEEE
P802.1q Draft Standards). Tagging a frame is accomplished by adding a Tag
Header to a frame immediately f ollowing its original Destination and Source
MAC address fields (and any r outing fields, if pre sent), and then r ecomputing the
Frame Check Sequence (FCS) appropriately. On receiving such a frame, a
tag-aware switch will read the priority from the tagged portion of the frame,
remove the Tag Header, recompute the FCS, and then direct it to its appropriate
transmission queue.
There are eight priority levels — indicated 0 through 7— available to designate
user priority. Frames tagged with a 0 represent the lowest priority level (or
normal) traffic, and frames tagged with a 7 indicate the highest priority level
traffic.
The MultiSwitch 700 module itself suppo rts two transmission queues: one that is
for 0 or normal priority traffic (o r any non-tagged traf fic), and a second queue that
is reserved for frames that have been tagged with a priority level of 1 or higher.
On receiving any priority-tagged frames, the Mult iSwitch 700 will forward them
out of the high priority queue before forwarding any frames in the normal
2-48Managing the Module
Page 69
The MultiSwitch 700 Device View
priority queue. However, the MultiSwitch 700 will tag outgoing frames with the
full range of eight priority levels, so that upon reception, a device that supports
the entire range of priority queuing will forward the frame appropriately.
You can use NetSight Element Manager to configure the criteria that determine
the priority in which frames will be queued for transmission by your MultiSwitch
700 module. Several different criteria can be used to determine a frame’s
transmission queue order:
•The module and port at which the frame was received.
•The destination and/or source MAC address associated with the frame.
•A combination of destination and/or source MAC address and the frame’s
protocol type.
•The frame’s protocol type.
When you configure the transmission queue for a specific frame, an entry is made
in one of three priority tables maintained by the MultiSwitch 700 module. These
tables are used to determine which transmit queue to use — normal priority or
high priority — when forwarding frames.
•The ctPriorityExtPortTable maintains priority entries based on a frame’s receive
port.
•The ctPriorityExtMACT able maintains priority entries based on a frame’s
MAC-layer information.
•The ctPriorityExtPktTypeTable maintains priority entries based on the frame’s
protocol type.
The following sections discuss how to use the Port Priority Configuration
window, the MAC Based Priority Configuration window, and the Frame Priority
Configuration window to make entries in these transmit priority tables.
Configuring Priority Queuing Based on Receive Port
You can use the Port Priority Configuration window, Figure 2-21, to determine
packet queuing based solely upon the port at which the packet was received. This
allows you to ensure that a connected user or LAN segment will have priority
when frames that were received on that port are queued for transmission.
Managing the Module2-49
Page 70
The MultiSwitch 700 Device View
Highlight a module/port, then
use the drop-down list box to
select a priority (Normal–7).
Click Apply to set the priority
at the device. Any priority of 1
or higher will allow packets
received at the chosen port to
be forwarded from the higher
priority transmission queue.
Figure 2-21. The Port Priority Configuration Window
NOTES
In the event that an incoming packet received on a designated port already has a priority
associated with it, you can use the ctPriorityExtPortFwdInboundPriority OID to
determine whether the incoming priority should remain intact, or be replaced with the
priority that you have set for the receiving port.
Use the MIB T ools utility suite to set the ctPriorityExtPortFwdInboundPriority OID
to 1 (for the appropriate port instance) if you want the incoming packet to retain its
originally set priority when received by the port; set the OID to 2 if you want the packet to
take the default priority set for the receiving port. Refer to the NetSight Element ManagerTools Guide for information on using the MIB Tools suite .
To access the Port Priority Configuration window:
1. Click on D
2. Click on P
menu. The Port Priority Configuration window opens.
The Port Priority Configuration window displays the contents of the
ctPriorityExtPortTable. It has a list box that displays the front panel interfaces
supported by the MultiSwitch 700 module, along with the slot number occupied
by the module, and any transmit priority that has been assigned to those
interfaces.
To assign a transmit priority to a port:
evice to access the Device menu.
riority Configuration and then right to select Port Based from the
1. Click to highlight the port interface of interest in the Po rt # column. Each
interface is identified by its MIBII IfIndex.
2-50Managing the Module
Page 71
2. Click on the Transmit Priority drop-down list box, and scroll to select the
desired priority level (Normal–7) for forwarding packets received on the
selected port.
Remember, since the MultiSwitch 700 module has two transmit queues, a priority of
NOTE
Configuring Priority Queuing Based on MAC-layer Information
Normal will cause packets received on that port to be forwarded through the lower priority
queue, and any priority of 1 through 7 will cause the packets to be forwarded through the
higher priority queue. However, other tag-aware switches may use the full range of eight
priority queues — so the priority that you assign ma y have bearing on how the frame is
forwarded when it is received by another device.
3. Click the Apply button. The defined priority displays next to the port in the
Transmit Priority column.
You can use the MAC Based Priority Configuration window, Figure 2-22, to
determine packet queuing based upon the packet’s Source and/or Destination
MAC address, as well as the packet’s frame T ype. These priority entries, based on
the frame’s MAC-layer information, are maintained in the ctPriorityExtMACTable.
You can create up to 1024 priority entries for queuing frames based upon on
MAC-layer information.
The MultiSwitch 700 Device View
Click Add to enter a
Select whether you want
the address type to be
destination, source, or
either type.
Determine whether to apply the
priority to all frames with the given
address and SA/DA type, or only
to frames of a specific type.
MAC Address to which
you want to assign a
higher priority
transmission queue.
Finally, select a priority level,
and click Apply.
Figure 2-22. The MAC Based Priority Configuration Window
Managing the Module2-51
Page 72
The MultiSwitch 700 Device View
To access the MAC Based Priority Configuration window:
1. Click D
2. Click P
menu. The MAC Based Priority Configuration window opens.
The MAC Based Priority Configuration window contains the following
information.
Current Priority Entries
The Current Priority Entries list box displays any MAC-based priority entries that
have been configured for the MultiSwitch 700 module. It has four columns:
•MAC Address, which identifies the physical address for which a frame
transmit priority entry has been configured.
•Address Type, which identifies whether the address of interest is in the sour ce
or destination field, or in both fields, of the frame.
•Frame Type, which indicates whether all frames with the given address will
have a transmit priority, or whether a specified frame Type will be used in
combination with the address.
•Priority, which displays the current transmit priority assigned to the entry.
Below the Current Priority Entries list box, several text fields and command
buttons allow you to configure or edit MAC-based priority entries:
evice to access the Device menu.
riority Configuration, and then right to select MAC Based from the
MAC Address
This text field allows you to enter a new MAC address that will h ave a transmit
priority associated with it.
Address Type
This drop-down list box allows you to select whether the given MAC address
must be in the source address portion of the frame (SA), the destination address
portion (DA), or in either portion (SA/DA).
Frame Type
This option button/text box combination allows you to choose whether All frame
Types wit h the given address will be given priority, or whether frames of a
Specific type (as defined in the associated text box) will be given priority.
Priority
Priority, which indicates the transmit priority level assigned to the configured
entry.
2-52Managing the Module
Page 73
The MultiSwitch 700 Device View
To assign a transmit priority based on MAC-layer information:
1. Click on the Add button. The entry fields will be activated.
2. Click in the MAC Address text box, and type in the physical address in
XX-XX-XX-XX-XX-XX format, where X is a valid hexadecimal value (A-F or
0-9), for which you want to configure a transmit priority.
3. Click on the Address Type drop-down list box, and select whether you want
the specified address to be in the Source Address portion of the frame (SA),
the Destination Address portion (DA), or in either portion (SA/DA).
4. Specify a Frame Type that you want associated with the frame:
a. Click on the appropriate Frame Type option button: Specific if you want a
certain Frame Type associated with the given MAC address, or All if you
do not care about the Frame Type.
b. If you select Specific, click in the associated text box and type in the
two-byte hexadecimal value for that protocol type (e.g., 0BAD for Banyan
frames).
NOTE
NOTE
When creating priority entries, you can specify up to four Frame T ypes for the same MAC
Address value.
5. Click on the Priority drop-down list box, and scroll to select the desired
priority level — Normal (0)–7 — for forwarding packets received with the
specified MAC-layer information.
Since the MultiSwitch 700 module has two transmit queues, a priority of Normal will
cause packets to be forwarded through the lower priority queue, and any priority of 1
through 7 will cause the packets to be forwarded through the higher pr iority queue.
6. Click Apply. The Current Priority Entries list box will be updated with the
newly created entry.
You can edit an existing address entry by changing the priority currently
associated with the entry. To do so:
1. Highlight the desired entry in the Current Priority Entries list box, and click on
the Edit button. The Priority drop-down list box will be activated. (All other
parameters will remain grayed-out, since they cannot be edited once they are
initially configured).
Managing the Module2-53
Page 74
The MultiSwitch 700 Device View
2. Click on the Priority drop-down list box, and scroll to select the new priority
level (Normal–7) for forwarding packets received with the specified MAC-layer
information.
3. Click Apply. The Current Priority Entries list box will be updated with the
newly ed ited entry.
To clear a priority entry from the ctPriorityExtMACTable:
1. Highlight the desired entry in the Current Priority Entries list box, and click
Delete. The entry fields will be cleared from the table.
Configuring Priority Queuing Based on Packet Type
You can use the Frame Priority Configuration window, Figure 2-23, to determine
packet queuing based solely upon its Type field data. Frame type entries are
maintained in the ctPriorityExtPktTypeTable. You can configure up to 15 frame
Type priority entries for the device.
Click Add to activate the Frame
Type field, then type in the 2
byte hexadecimal frame Type.
Use the drop-down list box to
select a priority (Normal–7)
associated with that frame Type
Click Apply to set the priority at
the device. Any priority of 1 or
higher will allow packets
received at the chosen port to
be forwarded from the higher
priority transmission queue.
Figure 2-23. Frame Priority Configuration Window
To assign a transmit priority based on frame Type information:
1. Click on the Add button. The entry fields will be activated.
2. Click in the Frame Type text box, and type in the 2-byte frame Type in XXXX
format, where X is a valid hexadecimal value (A-F or 0-9), for which you want
to configure a transmit priority (e.g., 8137 for Novell Type 1 frames).
3. Click on the Priority drop-down list box, and scroll to select the desired
priority level (Normal–7) for forwarding packets received with the specified
Type field information.
2-54Managing the Module
Page 75
NOTE
The MultiSwitch 700 Device View
Since the MultiSwitch 700 module has two transmit queues, a priority of Normal will
cause packets to be forwarded through the lower priority queue, and any priority of 1
through 7 will cause the packets to be forwarded through the higher
priority queue.
4. Click Apply. The Frame Type Entries list box will be updated with the newly
created entry.
You can edit an existing frame Type entry by changing its previously assigned
priority.
1. Highlight the desired entry in the Current Priority Entries list box, and click on
the Edit button. The Priorities drop-down list box will be activated (the Frame
Type cannot be edited once it is initially configured).
2. Click on the Priority drop-down list box, and select the desired priority level
(Normal–7) for forwarding packets received with the specified frame Type
information.
3. Click Apply. The F rame Type Priorities Entries list box will be updated with the
newly ed ited entry.
To clear a priority entry from the ctPriorityExtPktTypeTable:
1. Highlight the desired entry in the Frame Type Priorities Entries list box, and
click Delete. The entry fields will be cleared from the table.
Broadcast Suppression
From the Broadcast Statistics and Suppression window, you can monitor
broadcast peak statistics, and suppress the amount of broadcast frames received
on each interface on your MultiSwitch 700 module (thereby protecting your
network from broadcas t storms). Specifically, y ou can monitor the number of
frames each interface is receiving, and set limits on how many of those broadcast
frames will be forwarded to the other interfaces. Once a threshold has been
reached on an interface, broadcast frames will be dropped. From the Broadcast
Statistics and Suppression window, you can set a unique threshold for each
interface on a frames per second basis.
To access the Broadcast Statistics and Suppression window:
1. Click on the module index of the module of interest to display the Module
menu.
2. Select B
window, Figure 2-24, opens.
roadcast Suppression. The Broadcast Statistics and Suppression
Managing the Module2-55
Page 76
The MultiSwitch 700 Device View
Figure 2-24. The Broadcast Statistics and Suppression Window
Port #
This read-only field indicates the number assigned to each interface on the device.
Total RX
Displays the total number of broadcast frames received on the interface since the
device was last initialized.
Peak Rate
The peak rate of broadcast fram es (in frames per seco nd) r eceived on the interface
since the device was last initialized or the peak value was administratively reset
through this window.
Time Since Peak
The time (in a days HH:MM:SS format) since the peak broadcast rate occurred;
that is, the current MIB-II system uptime minus the system uptime when the peak
occurred (as recorded by the ctBroadcastPeakBroadcastRateTime OID). This value
will be reset to 0 days 00:00:00 when the device is re-initialized or when you
administratively reset the peak values.
2-56Managing the Module
Page 77
The MultiSwitch 700 Device View
To reset the Peak Rate and Time Since Peak values:
1. Shift- or Control-click to select one or more interfaces for which you want to
reset the values.
2. Click on the Reset Peak Rate and Peak Time on Selected Ports: drop-do wn
list box, and select YES.
3. Click Apply. The Peak Rate and Time Since Peak values will be reset for the
selected interfaces.
Threshold
The maximum number of received broadcast frames per second that may be
forwarded by this interface to other interfaces on the device. Any number of
broadcast frames received over this threshold will be dropped. The default value
for the interface is near the theoretical maximum frames per second for the
interface, i.e., 14,880 for 10Mb Ethernet interface, 148,880 for 100Mb Ethernet or
1,488,800 for Gigabit Ethernet.
To change the Receive Broadcast Threshold:
1. Shift- or Control-click to select one or more interfaces for which you want to
change the broadcast packet threshold.
2. Highlight the value currently in the Receive Broadcast Threshold on
Selected Ports: field and type in a new broadcast threshold value. Allowable
values begin at 10 and proceed in multiples of ten.
When you enter a value less than 10, the threshold will default to a value of 0. If you enter
NOTE
a value that is not a multiple of 10 it will default to the last multiple of 10, i.e., if you enter
15 as the new threshold value, the threshold value will be set to 10; if you enter 49 as the
new threshold value, the threshold value will be set to 40.
3. Click Apply. The new threshold will be applied to the selected interfaces. Any
broadcast frames received by the interface exceeding the set threshold will be
dropped.
The System Resources Window
The System Resources window displays attrib utes of the MultiSwitch 700
module’s CPU (including CPU type, and installed and available memory), as well
as the current and peak utilization of the CPU for switching. It also lets you
reserve the desired amount of CPU pro cessing used for switching or management
purposes, as well as reset the peak switch utilization information.
Managing the Module2-57
Page 78
The MultiSwitch 700 Device View
To display the System Resources window:
1. Click D
2. Select System
opens.
evice in the Device View menu bar to display the Device menu.
Figure 2-25. The System Resources Window
Resources. The System Resou r ces window, Figure 2-25,
CPU Type
Displays the type and speed (in megahertz) of the CPU (processor) used by the
system.
Flash Memory Installed:
Displays the total amount of installed flash memory (in Mbytes). Flash memory is
the reprogrammable memory used to store the device’s image code.
Flash Memory Available:
Displays (in Kbytes) the current amount of flash memory that is currently free
and not currently being used for code and data.
DRAM Installed:
Displays the total installed Dyna mic Random Access Memory (DRAM) in
Mbytes. DRAM is volatile memory used to temporarily store data via capacitors
and transistors, which must be constantly recharged to retain data. Access time to
read data stored on DRAM is slower than reading data stored on Static Random
Access Memory (SRAM) — since the processor cannot read DRAM while the
capacitors are being recharg e d. A DRAM chip, however, can store about four
times more data than a comparable SRAM chip, and is less expensive to
manufacture.
2-58Managing the Module
Page 79
The MultiSwitch 700 Device View
DRAM Available:
Displays (in Kbytes) the amount of free DRAM that is not currently being used for
data storage.
SRAM Installed:
Displays the total amount of SRAM (Static Random Access Memory) tha t is
installed (in Mbytes). SRAM retains data as long as the CPU is powered up. Since
it does not need the constant recharging of DRAM memory, its data can be
accessed much faster. SRAM is often used to temporarily cache — or store —
frequently accessed data or instructions commonly used by the processor. SRAM
can store less data than DRAM, however, and is more expensive to manufacture.
SRAM Available:
Displays (in Kbytes) the amount of free SRAM that is not currently being used for
data storage.
NVRAM Installed:
Displays (in Kbytes) the total insta lled Non-volatile Random Access Memory
(NVRAM). NVRAM retains data when the device is powered down, such as the
device IP address, community table information, and so forth.
NVRAM Available:
Displays (in Bytes) the amount of free NVRAM that is not currently being used
for data storage.
Current Switch Utilization:
Displays the current load on the switch, which is based on a percentage of
maximum switching capacity of 100%.
Peak Switch Utilization:
Displays the peak percentage of switch load (based on a maximum of 100%) that
has occurred on the switch, since power-up or last reset, along with the time and
date that it occurred. This field can be administratively refreshed, as described
below.
Reset Peak Switch Utilization:
This option allows you to clear the Peak Switch Utilization field.The Peak Switch
Utilization field will refresh to display the current switch utilization, date, and
time as the new peak values (until a new peak is experienced).
1. Click on next to the Reset Peak Switch Utilization field and select Yes from
the drop down list. (The default value is No.)
2. Click Apply to reset the displayed peak switch utilization. When the window
refreshes the value in this field will return to No.
The peak switch utilization values — including percentage, date, and time —
will be refreshed to display the current values. These values will change once
a new peak is experienced (or at the next peak reset).
Managing the Module2-59
Page 80
The MultiSwitch 700 Device View
The default setting for this field is No. While No is selected the peak switch utilization
NOTE
Reserving CPU Bandwidth
value will not be reset when you click on the Apply button. You must choose Yes for a
reset to take place.
CPU Management Reservation:
Displays the desired amount of CPU bandwidth reserved for management
purposes: None, Limited, or Full. Bandwidth that is not reserved for management
will be devoted to switching.
Depending on your needs and the main function of your MultiSwitch 700
module, you may wish to change the amount of CPU bandwidth that is currently
reserved for management purposes. The three possible allocations of CPU
bandwidth on your MultiSwitch 7 00 for manageme nt are:
•None — the MultiSwitch 700 will reserve all bandwidth for switching,
therefore management frames may be dropped under heavy loads.
802.1Q VLANs
•Limited — the management of the MultiSwitch 700 may be slow while the
device is experiencing heavy switching loads.
•Full — management of the MultiSwitch 700 is always possible and
management frames will take priority over switched data if full CPU
bandwidth is required (switched frames may be dropped).
To configure the CPU Management Reservation:
1. Next to the CPU Management Reservation field, click on and select
None, Full, or Limited from the drop down list.
2. Click on the Apply button to set the new CPU management reservation. A
window opens stating the set was succes sful.
This section introduces and describes pre-standard IEEE 802.1Q port-based
Virtual Local Area Network (VLAN) technology and the windows used to
configure 802.1Q VLAN-capable devices.
Current versions of MultiSwitch 700 firmware support the pre-standard IEEE
802.1Q draft specification for port-based VLANs.
2-60Managing the Module
Page 81
NOTES
NOTE
What Is A VLAN?
The MultiSwitch 700 Device View
For older versions of MultiSwitch 700 firmware, if 802.1Q is to be utilized it is required
that all modules in the chassis be configured to operate in 802.1Q mode. Distributed
Chassis Management ma y not be supported for MultiSwitch 700 modules oper ating in
802.1Q mode. In such cases, it is recommended that all modules installed in the
MultiSwitch 700 chassis be configured via Local Managem ent to operate in Standalone
mode. Contact the Global Technical Assistance Center for firmware upgrade information.
For current versions of MultiSwitch 700 firmware, DELHF-UA modules cannot be
installed in a MultiSwitch 700 that is operating in 802.1Q mode. This will be corrected in
a future version of firmware.
A Virtual Local Area Network (VLAN) is a logical group of devices that function
as a single Local Area Network segment (broadcast domain). Devices comprising
a VLAN may be (physically) widely separated, allowing users located in separate
areas or connected to separate ports to belong to a single VLAN group. Users
assigned to a VLAN can send and receive broadcast and multicast traffic as
though they were all physically connected to a single network segment.
VLAN-capable switches isolate broadcast and multica st tra ffic received from
VLAN groups, and contain broadcasts and multicasts from members of a VLAN
within that group.
What Is An 802.1Q Port-Based VLAN?
Switches that support the pre-standard IEEE 802.1Q draft specification for
port-based VLANs act by classifying frames into VLAN membership. Usually,
VLAN classification is based on tag headers (VLAN tags) in the headers o f data
frames. The tag header is inserted into the frame directly after the Source MAC
address field. A four-byte field in the tag header is used as the VLAN identifier.
These VLAN tags are added to data frames by the switch as the frames are
transmitted and/or received by certain ports, and are later used to make
forwarding decisions by the switch and other 802.1Q switches. In the absence of a
VLAN tag, a frame is assigned VLAN membership according to the VLAN
configuration of the switch port that receives the frame.
About 802.1Q VLAN Configuration and Operation
An 802.1Q VLAN is defined by assigning it a uniqu e identif ica tion number (the
VLAN ID) and an optional name. The VLAN ID is used to identify data frames
that originate from, and are intended for, the ports assigned to the VLAN. Up to
64 VLANs may be created, with VLAN IDs ranging from 2-4094. VLAN ID 1 is
reserved for the Default VLAN.
Managing the Module2-61
Page 82
The MultiSwitch 700 Device View
Ports on 802.1Q switches are assigned membership in a VLAN by ass ociating a
VLAN ID with each port on the switch. The VLAN ID is combined with the port’s
identification (e.g., module X port X) to form the Port VLAN ID (PVID).
When 802.1Q mode is initially activated on a device, all ports are associated with the
NOTE
Default VLAN (VLAN ID 1). If a VLAN ID has not been assigned to a particular port
on an 802.1Q switch, any frames received from that port will be classified as belonging to
the Default VLAN.
When 802.1Q is implemented for a MultiSwitch 700 that has a DELHA-UA
installed, each LEC will be represented as an individual port which can be easily
assigned membership in a VLAN.
For current versions of MultiSwitch 700 firmware, the number of LECs supported by the
NOTE
DELHA-UA in 802.1Q mode is limited to 32.
Once VLANs have been configured and activated, all frames with unknown
destination addresses (including broadcast, unknown multicast, and unknown
unicast frames) will be contained within the VLAN of their origin. The switch’s
Filtering Database tracks the associations between MAC addresses, VLAN
eligibilities, and port numbers, and is used to make forwarding decision s f or
frames. All VLANs share a single Spanning Tree.
Ingress List Operation
A port’s ingress list specifies the VLAN with which received frames will be
associated. The switch’s Filtering Database tracks the associations between VLAN
eligibilities, MAC addresses, and port numbers.
Untagged frames received by an 802.1Q switch port are classif ied accor ding to the
VLAN membership of the port that receives the frame.
Tagged frames received by an 802.1Q switch port are classified according to the
VLAN indicated in their tag header. A port may receive a tagged frame that
specifies a VLAN other than the one assigned to the port.
Egress List Operation
Each port’s egress list specifies which VLANs are associated with the port, and
specifies what type of frame (tagged or untagged) to transmit for each particular
VLAN on a port. This information may be statically defined by the user, or
dynamically learned and maintained by the switch’s Filtering Database.
2-62Managing the Module
Page 83
The MultiSwitch 700 Device View
If a port receives a tagged frame that specifies a VLAN other than the one
assigned to the port, the switch will dynamically associate that frame’s source
address and VLAN with the port (i.e., add that frame’s VLAN to the receiving
port’s egress list). Dynamically learned VLANs are subject to the same aging rules
as source addresses (e.g., if a tagged frame belonging to a dynamically learned
VLAN is not received by the port within the switch’s aging time, the transmitting
station’s source address and VLAN will be aged out for that port; no unknown
destination frames belonging to the station’s VLA N will be transmitted through
the port until the VLAN is dynamically learned once again). Only tagged frames
can cause the switch to dynamically change a port’s egress list.
802.1Q Port Types
Each 802.1Q switch port is assigned a mode of opera tion. Port types include:
1Q Trunk
If VLAN membership is to apply to users across several switches, ports used to
connect 802.1Q-aware devices ar e configured to use 1Q Trunk mode. In this mode,
all frames (except BPDUs) are transmitted with a tag header included in the
frame, allowing VLAN frames to maintain their VLAN ID across multiple
switches. Any untagged frames received by the port ar e dropped. 1Q Trunk ports
are configured to be members of all VLANs.
1d Trunk
This mode allows a port to transmit to a traditional (802.1d) switch fabric . These
ports transmit only untagged frames, and the switch expects to receive only
untagged traffic through the port. 1d T runk ports are configured to be members of
all VLANs. This mode can be used to share a connection among multiple VLANs
(e.g., sharing a server between two or more separate VLANs).
Hybrid
Hybrid mode (enabled by default) allows a port to receive and transmit both
tagged and untagged frames. In this mode, the port will be a member of its
statically assigned VLAN, as well as any dynamically learned VLANs (remember ,
dynamically learned VLANs are subject to the same aging rules as source
addresses).
Configuring Your 802.1Q VLANS
Before you can define and configure 802.1Q port-based VLANs on your device,
you must activate the device’s 802.1Q operational mode; this operation can be
performed using Local Management or the Mib Tools application. Using Mib
Tools, 802.1Q mode can be activated through the Container Mib’s Logical Entry
Table (cont LogicalEntryTable). When the 802.1Q component is activated, the device
will automatically reset, and begin operatin g in 802.1Q mode.
Managing the Module2-63
Page 84
The MultiSwitch 700 Device View
For older versions of MultiSwitch 700 firmware, if 802.1Q is to be utilized it may be
!
CAUTION
required that all modules in the chassis be configured to operate in 802.1Q mode. If you
attempt to activate a MultiSwitch 700 module’s 802.1Q component via the Mib Tools
application, you may lose contact with the rest of the chassis once the device resets. For
this reason, we recommend that Local Management be used to activate 802.1Q mode for
MultiSwitch 700 modules.
Refer to your device’s Local Management documentation for instructions on
activating a device’s 802.1Q operational mode via Local Management. For details
on the Mib Tools application, refer to your Tools Guide.
To set up your 802.1Q port-based VLANs using NetSight Element Manager, you
must first define the desired VLANs using the VLAN Config window
(Figure 2-26), wh ich allows you to assign VLAN IDs an d o ptional VLAN names,
and enable or disable VLANs.
After your VLANs are defined, you may configure the ingress and egress lists for
each port using the VLAN Port Config window (Figure 2-27) and the VLAN
Egress Port Config window (Figure 2-28), respectively.
Setting VLAN Parameters and Operational Modes
802.1Q VLANs are defined using the VLAN Config window, which is accessed
from the D
1. Click on D
2. Click on 802.1Q V
VLAN Config window, Figure 2-26, opens.
evice menu in your switch’s Device View. To launch the window:
evice in the Device View menu bar to display the Device menu.
LAN and then right to select 802.1Q VLAN Config. The
2-64Managing the Module
Page 85
The MultiSwitch 700 Device View
Figure 2-26. The VLAN Config Window
The Configured VLANS list box and fields allow you to view, create, modify,
delete, enable, and disable 802.1Q port-based VLANs. The list box displays the
following information about your defined VLANs:
VLAN ID
The VLAN ID is used to identify data frames that originate from, and are
intended for, the ports assigned to the VLAN. Up to 64 VLANs may be created,
with VLAN IDs ranging from 2-4094. The VLAN ID is combined with the port’s
identification (e.g., module X port X) to form the Port VLAN ID (PVID). VLAN ID
1 is reserved for the Default VLAN.
VLAN Name
An optional 32-character VLAN name may be assigned to a created VLAN. The
Default VLAN is assigned the name DEFAULT VLAN, which cannot be changed
or deleted.
Admin Status
This field indicates whether the VLAN is enabled or disabled. Unless Enable is
selected when port-based VLANs are initially defined, they are disabled by
default. The Default VLAN cannot be disabled.
Managing the Module2-65
Page 86
The MultiSwitch 700 Device View
Creating and Modifying VLANs
The fields immediately below the Configured VLANS list box are used to create
and modify your port-based VLANs. To create a new VLAN:
1. In the VLAN ID field, enter a unique value between 2-4094. VLAN ID 1 is
reserved for the Default VLAN, and cannot be used.
2. If desired, enter a name for the VLAN in the VLAN Name field. VLAN names
must be 32 characters or less.
Unless Enable is selected when a port-based VLAN is initially defined, it will be disabled
NOTE
by default. A new VLAN that is left in a Disabled state will remain disabled until a port
is assigned to it, at which time it will be automatically enabled. If you are changing a
VLAN’s port assignment, the VLAN should be disabled before changing the port
configuration. See Enabling and Disabling VLANs, on page 2-67, for instructions on
disabling VLANs. See Performing Ingress List Configuration, on page 2-67, for
details on completing your VLAN port configuration.
3. Click the Apply button. The new VLAN will be added to the Configured
VLANS list box.
Once a VLAN has been created, its VLAN ID cannot be modified. If you wish to
change a VLAN’s ID, you’ll have to delete the VLAN and create a new entry. See
Deleting VLANs, below, for instructions on deleting a VLAN. Attempting to
change a VLAN’s ID will result in the creation of a new VLAN with the same
VLAN name.
To modify an existing VLAN’s name, select its entry in the Configured VLANS
list box. The selected VLAN’s name will be displayed in the VLAN Name field.
Modify the displayed name as outlined in Steps 2-3, above.
Deleting VLANs
The VLAN Config window also allows you to delete VLANs (except for the
Default VLAN, which cannot be deleted). When a VLAN is deleted, any ports
assigned to that VLAN will automatically become members of the Default VLAN.
To delete a VLAN from your 802.1Q switch:
1. Click to select the desired VLAN entry in the Configured VLANS list box.
2. Click the Delete button. The selected VLAN will be removed from the list box.
2-66Managing the Module
Page 87
NOTE
The MultiSwitch 700 Device View
Enabling and Disabling VLANs
Unless Enable is selected when a VLAN is initially defined, it is disabled by default. A
new VLAN that is left in a Disabled state will remain disabled until a port is assigned to
it, at which time it will be automatically enabled. If you are changing a VLAN’s port
assignment, the VLAN should be disabled before changing the port configuration. See
Performing Ingress List Configuration, on page 2-67, for details on completing your
VLAN port configuration.
To enable or disable VLANs:
1. Select the desired VLAN entry in the Configured VLANS list box.
2. In the VLAN Admin field, click to selec t Enable or Disable.
3. Click the Apply button. The selected VLAN will be enabled or disabled,
depending on your selection.
Updating VLAN Config Window Information
Clicking the Refresh button will update the information displayed in the
Configured VLANs list without closing the wind ow.
Performing Ingress List Configuration
802.1Q VLAN port assignment and ingress list configuration operations are
performed using the VLAN Port Config window, which is accessed from the
evice menu in your switch’s Device View. See Ingress List Operation, on
D
page 2-62 for details on ingress lists. To l aun ch the window:
1. Click on D
evice in the Device View menu bar to display the Device menu.
2. Click on 802.1QV
The VLAN Port Config window, Figure 2-27, opens.
LAN and then right to select 802.1Q VLAN Port Config.
Managing the Module2-67
Page 88
The MultiSwitch 700 Device View
Figure 2-27. The VLAN Port Config Window
The 802.1Q VLAN Port Assignment list box in this window displays the
following information about ports on your 802.1Q switch:
Slot/Port
These fields display the slot and port index for each port on your 802.1Q s witch.
VLAN ID
This field displays the VLAN ID of the VLAN to which the port is currently
assigned.
Mode
This field displays the port’s current mode of operation. Port operational modes
include:
•Dot1DTrunk mode, which is used for ports that are to connect to a traditional
(802.1D) switch fabric. These ports transmit only untagged frames. 1d Trunk
ports are configured to be members of all VLANs.
•Dot1QTrunk mode, which is used for ports used to connect 802.1Q-aware
devices if VLAN membership is to apply to users across several switches.
These ports transmit only tagged frames. 1Q Tr unk ports are con figured to be
members of all VLANs.
2-68Managing the Module
Page 89
The MultiSwitch 700 Device View
•Hybrid mode, which allows a port to receive and transmit both tagged and
untagged frames. In this mode, the port will be a member of its statically
assigned VLAN, as well as any dynamically learned VLANs. Hybrid mode is
enabled by default.
For more information on 802.1Q port operational modes, see 802.1Q Port Types,
on page 2-63.
Discard
This field displays the port’s current frame discard format (discardTagged,
discardUntagged, or noDiscard).
The VLAN ID, Port Operational Mode, and Port Discard fields, below the list
box, allow you to configure your ports as foll ows:
VLAN ID
This field allows you to associate a selected port with an existing VLAN. See
Assigning VLAN Membership to Ports, on page 2-69, for details on performing
this operation.
Port Operational Mode
This field allows you to assign a mode of operation to a selected port. See Setting
Port Operational Modes, on page 2-70, for details on using this field.
NOTE
Port Discard
This field allows you to specify the frame discard format (discardTagged,
discardUntagged, or noDiscard) for a selected port. See Setting Port Frame
Discard Formats, on page 2-70, for details on using this field.
Assigning VLAN Membership to Ports
To assign a port on your 802.1Q switch to any of your defined VLANs:
1. In the list box, click to select a port that you wish to assign to a VLAN. The
port’s current VLAN configuration information, including its VLAN ID, will be
displayed in the fields below the list box.
2. In the VLAN ID field, click to select the VLAN ID of the VLAN to which you
wish to assign the selected port.
3. Click the Apply button. The new VLAN assignment will be reflected in the
VLAN Port Config window’s list box for the selected port.
If you assign a port to a VLAN that is in a Disabled state, the VLAN will automatically
be Enabled once the port assignment operation has been completed.
Managing the Module2-69
Page 90
The MultiSwitch 700 Device View
Setting Port Operational Modes
T o assign a port operational mode (dot1dTrunk, dot1QTrunk, or hybrid) to a port
on your 802.1Q switch:
1. In the VLAN Port Config window’s list box, click to select a port to which you
wish to assign a port operational mode.
2. In the Port Operational Mode field, click to select the desired operational
mode.
3. Click the Apply button. The selected mode will be reflected in the list box for
the selected port.
Setting Port Frame Discard Formats
To assign a frame discard format (discardTagged, discardUntagged, or
noDiscard) to a port on your 802.1Q switch:
1. In the VLAN Port Config window’s list box, click to select a port to which you
wish to assign a frame discard format.
2. In the Port Discard field, click to select the desired frame discard format.
3. Click the Apply button. The selected mode will be reflected in the list box for
the selected port.
Updating VLAN Port Config Window Information
Clicking the Refresh button will update the information displayed in the 802.1Q
VLAN Port Assignment list without closing the window.
Performing Egress List Configuration
802.1Q VLAN switching allows each port on a switch to transmit traffic for any or
all defined VLANs on your network. During egress list configuration, you
determine which VLANs are on each port’s egress list. See Egress List Ope ration,
on page 2-62 for details on egress lists.
Egress list configuration operations are performed using the VLAN Egress Port
Config window. To launch t he window:
1. Click on D
2. Click on 802.1QV
Config. The VLAN Egress Port Config window, Figure 2-28, opens.
evice in the Device View menu bar to display the Device menu.
LAN and then right to select 802.1Q VLAN Egress Port
2-70Managing the Module
Page 91
The MultiSwitch 700 Device View
Figure 2-28. The VLAN Egress Port Config Window
The list box at the top of this window is used to select a configured VLAN for
association with your swit ch’s ports. Clicking on a VLAN will display its
currently associated ports in the lower portion of this window. The list box
displays the following information:
Slot Number
This field displays the slot index for the module being configured.
VID
This field lists the VLAN IDs of the currently configured VLANs on your switch.
Name
This field lists the VLAN names assigned to the currently configured VLANs on
your switch.
Managing the Module2-71
Page 92
The MultiSwitch 700 Device View
Under the list box there are two groups of check boxes that display the ports on
the switch. A checkmark in the port’s check box indicates that the VLAN selected
in the list box is in the port’s egress list. The two groups are:
Egress Ports
Use these check boxes to add or remove the selected VLAN fr o m the egr e ss list of
one or more ports.
Egress Untagged List
Use these check boxes to allow the ports to transmit untagged frames from the
selected VLAN.
Building an Egress List
To build egress lists for your 80 2.1Q switch:
1. In the list box at the top of the window, click to select a configured VLAN. The
ports that contain the selected VLAN in their egress lists will be displayed in
the lower portions of this window with checkmarks in their check boxes.
2. To add or remove the selected VLAN from the egress list of one or more ports,
click on the appropriate check box in the Egress Po rts group . A checkmark in
a port’s check box indicates that the selected VLAN is in the port’s egress list.
3. To add or remove the ability for a port to transmit both tagged and untagged
frames from the selected VLAN, click to put a checkmark in the appropriate
check box in the Egress Untagged List group. Note that a port check box in
this group will be grayed out until it has been selected in the Egress Ports
group.
4. To apply any changes, click on the Apply button at the bottom of the window.
Setting the Device Date and Time
The Device menu provides the options that allow you to change the date and
time stored in the device’s internal clock: Edit Device Time and Edit Device
Date.
To edit the device time:
1. Click on D
2. Select Edit Device T
opens.
evice on the Device View menu bar to access the Device menu.
ime. The Device Time change window, Figure 2-29,
2-72Managing the Module
Page 93
The MultiSwitch 700 Device View
Figure 2-29. The Device Time Window
3. Enter the new time in a 24-hour hh:mm:ss format, either by highlighting the
field you wish to change and using the up and down arrow buttons, or by
entering the new value in the appropriate field.
4. Click OK to save your changes, or Cancel to exit without saving changes.
To edit the device date:
1. Click on D
1. Select E
opens.
2. Enter the new date in a mm/dd/yyyy format, either by highlighting the field you
wish to change and using the up and down arrow buttons, or by entering the
new value in the appropriate field.
3. Click OK to save your changes, or Cancel to exit without saving changes.
evice on the Device View menu bar to access the Device menu.
dit Device Date. The Device Date change window, Figure 2-30,
Figure 2-30. The Device Date Window
Managing the Module2-73
Page 94
The MultiSwitch 700 Device View
Enabling and Disabling Ports
When you disable bridging at a port interface, you disconnect that port’s network
from the bridge entirely. The port does not forward any packets, nor does it
participate in Spanning Tree operations. Nodes connected to the network can still
communicate with each other, but they can’t communicate with the bridge or
with other networks connected to the bridge. When you enable bridging for the
interface, the port moves from the Disabled state through the Listening and
Learning states to the Forwarding state; bridge port state color codes will ch ange
accordingly.
You cannot disable a backplane interface from the Device Logical View — since the
NOTE
backplane interfaces do not appear in the port stack. You must use the Device BackPlane
Config View to disable the interfaces to the DLM6C-AA backplane.
To enable or disable bridging for an individual interface:
1. Click on the appropriate port display box to display the port menu.
NOTE
2. Select Enable to enable bridging at the interface, or Disable to disable
bridging. Bridging will now be enabled or disabled across the selected port, as
desired.
To enable or disable bridging for all interfaces installed on the monitored
MultiSwitch 700 module:
1. Click on the module index of interest to display the Module menu.
2. Select Enable Bridge to enable bridging at all installed interfaces, or Disable Bridge to disable bridging across all interfaces. Bridging will now be enabled
or disabled across the installed interfaces, as desired.
For more information about bridging functions and how to determine the current state of
each bridge port, see the Bridging chapter in the Tools Guide.
2-74Managing the Module
Page 95
The DELHW-UA Device View
Unlike other modular interfaces designed for the MultiSwitch 700 boards, the
DELHW-UA module functions as an independent intelligent device with its own
IP address. As such, it must be managed separately from the MultiSwitch 700
chassis and the board on which it is installed. This section provides information
on launching the DELHW-UA Device View and using its associated functions. For
information on configuring and ma naging the WAN capabilities of the various
port modules available for the DELHW-UA, see Chapter 7.
QuickSET for the DELHW-UA was shipped with your device. This program is designed
NOTE
for point-and-click installation and set-up of DELHW-UA devices. If you launch Chassis
Manager for a DELHW-UA and have QuickSET installed, your Utilities menu will
display a menu pick for launching QuickSET. See your QuickSET for the DELHW-UA
documentation for more information.
Port interface modules available for the DELHW-UA include:
DELDS-UIDDS is Digital Data Services , a digital network that
supports data rates of 56Kbps or 64Kbps. The DDS
service provides users with dedicated, two-way
simultaneous transmission capabilities operating at
transfer rates up to 64 Kbps. This port module comes
with a built-in CSU/DSU.
The MultiSwitch 700 Device View
DELDI-UIThe DI (Drop-and-Insert) port interface module pro vides
a T1 interface through a front-panel RJ45 port and
includes a built-in CSU/DSU for direct connection to a
T1 line. The DELDI-UI provides Full T1 or Fractional T1
using 56 or 64 Kbps Time Slots. It also provides a second
Drop-and-Insert interface that allows more than one
device, such as a PBX, to share a single T1 connection.
DELE1-UIThis port interface module provides an E1 interface
through a front-panel RJ- 45 port and includes a built-in
CSU/DSU for direct connection to an E1 line. It provides
Full E1 or Fractional E1 using 56 or 64 Kbps Time Slots
with a total throughput of up to 2 Mbps. Time Division
Multiplexing (TDM) allows fo r the channelization of up
to 31 links of a single physica l interface.
The DELHW-UA Device View2-75
Page 96
The MultiSwitch 700 Device View
DELST-UI This port interface module provides an ISDN 128 Kbps
DELSY-UIProvides a synchronous serial connection of up to 2.048
Basic Rate Interface (BRI) and is designed for an ISDN
back-up link for a frame relay or leased line. In the
United States and Canada, Network Terminator
equipment (NT1) is required to provide an interface
between the DELST-UI and the ISDN line.
Mbps to external communications equipment (an
external CSU/DSU is required). An external CSU/DSU
is required; the following electrical interfaces are
supported (consult your hardware documentation for
cable pinout information):
EIA-RS449
V.3 5
EIA-RS232D
X.21
EIA-RS530
EIA-530A
RS530 ALT A
RS530A ALT A
NOTE
DELT1-UIProvides a T1 interface through a front-panel RJ45 port
and includes a built-in CSU/DSU for direct connection to
a T1 line. The DELT1-UI provides both Full T1 or
Fractional T1 using 56 or 64 Kbps Time Slots, with a total
throughput of up to 1.544 Mbps. Time Division
Multiplexing (TDM) allows for channelization of up to 24
links over a single physical T1/FT1 interface.
DELTD-UIThis port interface module provides both a T1 and DDS
interface that allows you to easily switch between the
two interfaces by changing the physical cabling and
reconfiguring the desired interface with either QuickSET
for the DELHW-UA or NetSight Element Manager.
For more information on these port modules, consult the appropriate hardware
documentation or your QuickSET for the DELHW-UA documentation.
To configure the DELDI-UI and DELE1-UI, use the QuickSET application that was
shipped with your device. See your QuickSET for the DELHW-UA documentation for
more information.
2-76The DELHW-UA Device View
Page 97
The MultiSwitch 700 Device View
Launching the DELHW-UA Device View Window
The DELHW-UA Device View window is the main screen that immediately
informs you of the current condition of individual ports on your switch via a
graphical display . The Device V iew window also serves as a single point of access
to all other DELHW-UA windows and screens, which are discussed throughout
this manual.
To access the DELHW-UA Device View window, use one of the following options:
1. In any map, list, or tree view, double-click on the DELHW-UA you wish to
manage.
or
1. In any map, list, or tree view, select the DELHW-UA you wish to manage.
2. Select Manage—>Node from the primary window menu bar, or select the
Manage Node toolbar button.
or
1. In any map, list, or tree view, click the right mouse button once to select the
DELHW-UA you wish to manage and on the resulting menu, select Manage.
Viewing Device Information
The desired DELHW -UA Device View window (Figure 2-31) provides a graphical
representation of the device, including a color-coded port display which
immediately informs you of the current configuration and status of the switch
and its ports.
The DELHW-UA Device View2-77
Page 98
The MultiSwitch 700 Device View
NOTES
TIP
Figure 2-31. The DELHW-UA Device View Window
The Device View windows will only display the bridge ports on a DELHW-UA. See your
QuickSET for the DELHW-UA documentation for information on managing your
Ethernet ports.
By clicking in designated areas of the chassis graphical display (as detailed later
in this chapter), or by using the menu bar at the top of the Device View window,
you can access all of the menus that lead to more detailed device- and port-level
windows.
When you move the mouse cursor over a management “hot spot” the cursor icon will
change into a “hand” to indicate that clicking in the current location will bring up a
management option.
2-78The DELHW-UA Device View
Page 99
Front Panel Information
The areas surrounding the main chassis area provide the following device
information:
IP
The Internet Protocol address assigned to the DELHW-UA appears in the title bar
of the Device View window. IP addresses are assigned via Local Management.
Connection Status
This color-coded area i ndicates the current state of communication between
NetSight Element Manager and the DELHW-UA.
•Green indicates the DELHW-UA is responding to device polls (valid
•Magenta indicates that the DELHW-UA is in a temporary stand-by mode
•Blue indicates an unknown contact status — polling has not yet been
The MultiSwitch 700 Device View
connection).
while it responds to a physical change in the switch; note that board and port
menus are inactive during this stand-by state.
established with the DELHW-UA.
•Red indicates the DELHW-UA is not responding to device polls (device is off
line, or device polling has failed across the network for some other reason).
UpTime
The amount of time, in a X day(s) hh:mm:ss format, that the DELHW-UA has
been running since the last start-up.
Port Status
If management for your device supports a variable port display (detailed in The
DELHW-UA Port Status Displays, on page 2-83), this field will show the display
currently in effect. If only a single port display is available — or if the default view
is in effect — this field will state Default.
MAC
Displays the physical layer address assigned to the interface associated with the
IP Address used to define the device icon when it was added to NetSight Eleme nt
Manager. MAC addresses are hard-coded in the device, and are not configurable.
Boot Prom
The revision of BOOT PROM installed in the DELHW-UA.
Firmware
The revision of device firmware stored in the DELHW-UA’s FLASH PROMs.
Time
The current time, in a 24-hour hh:mm:ss format, set in the DELHW-UA’s internal
clock.
The DELHW-UA Device View2-79
Page 100
The MultiSwitch 700 Device View
Date
The current date, in an mm/dd/yyyy format, set in the DELHW-UA’s internal
clock.
Menu Structure
By clicking on various areas of the DELHW-UA Device View display, you can
access menus with device- and port-level options, as well as utility applications
which apply to the device. The following illustration displays the menu structure
and indicates how to use the mouse to access the various menus:
If QuickSET is installed
on your workstation, it
will also appear in the
Utilities menu.
Clicking on the
module index will
bring up the Bridge
menu, described in
the Bridging
chapter of the
Tools Guide
.
Figure 2-32. DELHW-UA Device View Menu Structure
The Device Menu
From the Device Menu at the Device View window menu bar, you can access the
following selections:
evice T ype displays a d escription of the device being modeled. See Viewing
•D
Hardware Types, on page 2-20.
evice Find Source Address allows you to conduct a search to discover which
•D
interface(s) a specified source MAC addres s is communicating through. See
Viewing I/F Summary Information, on page 2-22.
2-80The DELHW-UA Device View
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.