0% found this document useful (0 votes)

82 views340 pages

Ml800-A4 Ge Miltilin

Uploaded by

Edmundo Muñoz

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

82 views340 pages

Ml800-A4 Ge Miltilin

Uploaded by

Edmundo Muñoz

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 340

GE

Digital Energy

Multilink ML800
Managed Edge Switch

Instruction Manual
Firmware Revision: 3.3x
Manual P/N: 1601-9107-A4 T
GIS ERE
RE

GE publication code: GEK-113571C

ISO9001:2000
EM I
G

U LT I L

GE Digital Energy's Quality

Management System is
registered to ISO9001:2000
QMI # 005094
*1601-9107-A4* UL # A3775
© 2015 GE Digital Energy Incorporated. All rights reserved.
GE Digital Energy Multilink ML800 instruction manual for revision 3.3x.
Multilink ML800 is a registered trademark of GE Multilin Inc.
NEBS is a trademark of Telcordia Technologies
The contents of this manual are the property of GE Digital Energy Inc. This documentation
is furnished on license and may not be reproduced in whole or in part without the
permission of GE Digital Energy. The content of this manual is for informational use only
and is subject to change without notice.
Part numbers contained in this manual are subject to change without notice, and should
therefore be verified by GE Digital Energy before ordering.
Part number: 1601-9107-A4 (September 2015)

For further assistance

For product support, contact the information and call center as follows:
GE Digital Energy
650 Markland Street
Markham, Ontario
Canada L6C 0M1
Worldwide telephone: +1 905 927 7070
Europe/Middle East/Africa telephone: +34 94 485 88 54
North America toll-free: 1 800 547 8629
Fax: +1 905 927 5098
Worldwide e-mail: multilin.tech@ge.com
Europe e-mail: multilin.tech.euro@ge.com
Website: http://www.gedigitalenergy.com/multilin
These instructions do not purport to cover all details or variations in equipment nor provide for every
possible contingency to be met in connection with installation, operation, or maintenance. Should further
information be desired or should particular problems arise which are not covered sufficiently for the
purchaser’s purpose, the matter should be referred to the General Electric Company.
To the extent required the products described herein meet applicable ANSI, IEEE, and NEMA standards; but
no such assurance is given with respect to local codes and ordinances because they vary greatly.

Federal Communications Commission

Radio Frequency Interference Statement
This equipment generates, uses and can radiate frequency energy and if not installed and used properly
in strict accordance with the manufacturer's instructions, may cause interference to radio
communication. It has been tested and found to comply with the limits for a Class A computing device in
accordance with the specifications in Subpart J of Part 15 of FCC rules, which are designed to provide
reasonable protection against such interference when operated in a commercial environment. Operation
of this equipment in a residential area is likely to cause interference, in which case the user, at their own
expense, will be required to take whatever measures may be required to correct the interference.
Canadian Emissions Statement
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment
Regulations.
Cet appareil respecte toutes les exigences du Réglement sur le matériel du Canada. Cet appareil est
Classe A..
Electrical Safety requirements:
1. This product is to be installed Only in Restricted Access Areas (Dedicated Equipment Rooms, Electrical
Closets, or the like).
2. 48 V DC products shall be installed with a readily accessible disconnect device in the building
installation supply circuit to the product.
3. This product shall be provided with a maximum 10 A DC Listed fuse or circuit breaker in the supply
circuit when connected to a 48 V centralized DC source.
4. The external power supply for DC units shall be a Listed, Direct Plug In power unit, marked Class 2, or
Listed ITE Power Supply, marked LP, which has suitably rated output voltage (i.e. 24 V DC or 48 V DC)
and suitable rated output current.
5. Product does not contain user replaceable fuses. Any internal fuses can ONLY be replaced by GE
Multilin.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL III

General Safety Precautions
Note

• Failure to observe and follow the instructions provided in the equipment manual(s)
could cause irreversible damage to the equipment and could lead to property
damage, personal injury and/or death.
• Before attempting to use the equipment, it is important that all danger and
caution indicators are reviewed.
• If the equipment is used in a manner not specified by the manufacturer or
functions abnormally, proceed with caution. Otherwise, the protection provided by
the equipment may be impaired and can result in Impaired operation and injury.
• Caution: Hazardous voltages can cause shock, burns or death.
• Installation/service personnel must be familiar with general device test practices,
electrical awareness and safety precautions must be followed.
• Before performing visual inspections, tests, or periodic maintenance on this device
or associated circuits, isolate or disconnect all hazardous live circuits and sources
of electric power.
• Failure to shut equipment off prior to removing the power connections could
expose you to dangerous voltages causing injury or death.
• All recommended equipment that should be grounded and must have a reliable
and un-compromised grounding path for safety purposes, protection against
electromagnetic interference and proper device operation.
• Equipment grounds should be bonded together and connected to the facility’s
main ground system for primary power.
• Keep all ground leads as short as possible.
• At all times, equipment ground terminal must be grounded during device
operation and service.
• In addition to the safety precautions mentioned all electrical connections made
must respect the applicable local jurisdiction electrical code.

IV MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

Safety Words and Definitions
The following symbols used in this document indicate the following conditions.

Indicates a hazardous situation which, if not avoided, will result in death or serious
Note

injury.

Indicates a hazardous situation which, if not avoided, could result in death or serious
Note

injury.

Indicates a hazardous situation which, if not avoided, could result in minor or

Note

moderate injury.

Indicates significant issues and practices that are not related to personal injury.
Note

Indicates general information and practices, including operational information and

Note

practices, that are not related to personal injury.

NOTE

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL V

BATTERY DISPOSAL

EN Battery Disposal batería. La batería se marca con este símbolo, que puede incluir siglas
This product contains a battery that cannot be disposed of as para indicar el cadmio (Cd), el plomo (Pb), o el mercurio (Hg ). Para el
reciclaje apropiado, devuelva este producto a su distribuidor ó
unsorted municipal waste in the European Union. See the product
deshágase de él en los puntos de reciclaje designados. Para mas
documentation for specific battery information. The battery is marked
with this symbol, which may include lettering to indicate cadmium información: wwwrecyclethis.info.
(Cd), lead (Pb), or mercury (Hg). For proper recycling return the battery ET Patareide kõrvaldamine
to your supplier or to a designated collection point. For more Käesolev toode sisaldab patareisid, mida Euroopa Liidus ei tohi
information see: www.recyclethis.info.
kõrvaldada sorteerimata olmejäätmetena. Andmeid patareide kohta
CS Nakládání s bateriemi vaadake toote dokumentatsioonist. Patareid on märgistatud
käesoleva sümboliga, millel võib olla kaadmiumi (Cd), pliid (Pb) või
Tento produkt obsahuje baterie, které nemohou být zneškodněny v
elavhõbedat (Hg) tähistavad tähed. Nõuetekohaseks ringlusse
Evropské unii jako netříděný komunální odpadu. Viz dokumentace k
produktu pro informace pro konkrétní baterie. Baterie je označena võtmiseks tagastage patarei tarnijale või kindlaksmääratud
vastuvõtupunkti. Lisainformatsiooni saab Internetist aadressil:
tímto symbolem, který může zahrnovat i uvedena písmena, kadmium
www.recyclethis.info.
(Cd), olovo (Pb), nebo rtuť (Hg). Pro správnou recyklaci baterií vraťte
svémudodavateli nebo na určeném sběrném místě. Pro více informací FI Paristoje ja akkujen hävittäminen
viz: www.recyclethis.info
Tuote sisältää pariston, jota ei saa hävittää Euroopan Unionin alueella
DA Batteri affald talousjätteen mukana. Tarkista tuoteselosteesta tuotteen tiedot.
Paristo on merkitty tällä symbolilla ja saattaa sisältää cadmiumia (Cd),
Dette produkt indeholder et batteri som ikke kan bortskaffes sammen
lyijyä (Pb) tai elohopeaa (Hg). Oikean kierrätystavan varmistamiseksi
med almindeligt husholdningsaffald i Europa. Se produktinformation
for specifikke informationer om batteriet. Batteriet er forsynet med palauta tuote paikalliselle jälleenmyyjälle tai palauta se paristojen
keräyspisteeseen. Lisätietoja sivuilla www.recyclethis.info.
indgraveret symboler for hvad batteriet indeholder: kadmium (Cd), bly
(Pb) og kviksølv (Hg). Europæiske brugere af elektrisk udstyr skal FR Élimination des piles
aflevere kasserede produkter til genbrug eller til leverandøren.
Ce produit contient une batterie qui ne peuvent être éliminés comme
Yderligere oplysninger findes på webstedet www.recyclethis.info.
déchets municipaux non triés dans l'Union européenne. Voir la
DE Entsorgung von Batterien documentation du produit au niveau des renseignements sur la pile.
La batterie est marqué de ce symbole, qui comprennent les
Dieses Produkt beinhaltet eine Batterie, die nicht als unsortierter
städtischer Abfall in der europäischen Union entsorgt werden darf. indications cadmium (Cd), plomb (Pb), ou mercure (Hg). Pour le
recyclage, retourner la batterie à votre fournisseur ou à un point de
Beachten Sie die spezifischen Batterie-informationen in der
collecte. Pour plus d'informations, voir: www.recyclethis.info.
Produktdokumentation. Die Batterie ist mit diesem Symbol
gekennzeichnet, welches auch Hinweise auf möglicherweise HU Akkumulátor hulladék kezelése
enthaltene Stoffe wie Kadmium (Cd), Blei (Pb) oder Quecksilber
Ezen termék akkumulátort tartalmaz, amely az Európai Unión belül
(Hektogramm) darstellt. Für die korrekte Wiederverwertung bringen csak a kijelölt módon és helyen dobható ki. A terméken illetve a
Sie diese Batterie zu Ihrem lokalen Lieferanten zurück oder entsorgen
mellékelt ismertetőn olvasható a kadmium (Cd), ólom (Pb) vagy higany
Sie das Produkt an den gekennzeichneten Sammelstellen. Weitere
(Hg) tartalomra utaló betűjelzés. A hulladék akkumulátor leadható a
Informationen hierzu finden Sie auf der folgenden Website: termék forgalmazójánál új akkumulátor vásárlásakor, vagy a kijelölt
www.recyclethis.info.
elektronikai hulladékudvarokban. További információ a
EL Απόρριψη μπαταριών www.recyclethis.info oldalon.
Αυτό το προϊόν περιέχει μια μπαταρία που δεν πρέπει να IT Smaltimento batterie
απορρίπτεται σε δημόσια συστήματα απόρριψης στην Ευρωπαϊκή Questo prodotto contiene una batteria che non può essere smaltita
Κοινότητα. ∆είτε την τεκμηρίωση του προϊόντος για συγκεκριμένες
nei comuni contenitori per lo smaltimento rifiuti, nell' Unione Europea.
πληροφορίες που αφορούν τη μπαταρία. Η μπαταρία είναι φέρει
Controllate la documentazione del prodotto per le informazioni
σήμανση με αυτό το σύμβολο, το οποίο μπορεί να περιλαμβάνει specifiche sulla batteria. La batteria è contrassegnata con questo
γράμματα για να δηλώσουν το κάδμιο (Cd), τον μόλυβδο (Pb), ή τον
simbolo e può includere alcuni caratteri ad indicare la presenza di
υδράργυρο (Hg). Για την κατάλληλη ανακύκλωση επιστρέψτε την
cadmio (Cd), piombo (Pb) oppure mercurio (Hg). Per il corretto
μπαταρία στον προμηθευτή σας ή σε καθορισμένο σημείο συλλογής. smaltimento, potete restituirli al vostro fornitore locale, oppure
Για περισσότερες πληροφορίες δείτε: www.recyclethis.info.
rivolgervi e consegnarli presso i centri di raccolta preposti. Per
ES Eliminacion de baterias maggiori informazioni vedere: ww.recyclethis.info.
Este producto contiene una batería que no se pueda eliminar como
basura normal sin clasificar en la Unión Europea. Examine la
documentación del producto para la información específica de la

VI MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

LT Baterijų šalinimas RU Утилизация батарей
Šios įrangos sudėtyje yra baterijų, kurias draudžiama šalinti Europos Согласно европейской директиве об отходах электрического и
Sąjungos viešose nerūšiuotų atliekų šalinimo sistemose. Informaciją электронного оборудования, продукты, содержащие батареи,
apie baterijas galite rasti įrangos techninėje dokumentacijoje. нельзя утилизировать как обычные отходы на территории ЕС.
Baterijos žymimos šiuo simboliu, papildomai gali būti nurodoma kad Более подробную информацию вы найдете в документации к
baterijų sudėtyje yra kadmio (Cd), švino (Pb) ar gyvsidabrio (Hg). продукту. На этом символе могут присутствовать буквы, которые
Eksploatavimui nebetinkamas baterijas pristatykite į tam skirtas означают, что батарея собержит кадмий (Cd), свинец (Pb) или ртуть
surinkimo vietas arba grąžinkite jas tiesioginiam tiekėjui, kad jos būtų (Hg). Для надлежащей утилизации по окончании срока
tinkamai utilizuotos. Daugiau informacijos rasite šioje interneto эксплуатации пользователь должен возвратить батареи
svetainėje: www.recyclethis.info. локальному поставщику или сдать в специальный пункт приема.
Подробности можно найти на веб-сайте: www.recyclethis.info.
LV Bateriju likvidēšana
SK Zaobchádzanie s batériami
Šis produkts satur bateriju vai akumulatoru, kuru nedrīkst izmest
Eiropas Savienībā esošajās sadzīves atkritumu sistēmās. Sk. produkta Tento produkt obsahuje batériu, s ktorou sa v Európskej únii nesmie
dokumentācijā, kur ir norādīta konkrēta informācija par bateriju vai nakladať ako s netriedeným komunálnym odpadom. Dokumentácia k
akumulatoru. Baterijas vai akumulatora marķējumā ir šis simbols, kas produktu obsahuje špecifické informácie o batérii. Batéria je
var ietvert burtus, kuri norāda kadmiju (Cd), svinu (Pb) vai dzīvsudrabu označená týmto symbolom, ktorý môže obsahovať písmená na
(Hg). Pēc ekspluatācijas laika beigām baterijas vai akumulatori označenie kadmia (Cd), olova (Pb), alebo ortuti (Hg). Na správnu
jānodod piegādātājam vai specializētā bateriju savākšanas vietā. recykláciu vráťte batériu vášmu lokálnemu dodávateľovi alebo na
Sīkāku informāciju var iegūt vietnē: www.recyclethis.info. určené zberné miesto. Pre viac informácii pozrite:
www.recyclethis.info.
NL Verwijderen van baterijen
Dit product bevat een batterij welke niet kan verwijdert worden via de SL Odlaganje baterij
gemeentelijke huisvuilscheiding in de Europese Gemeenschap. Ta izdelek vsebuje baterijo, ki je v Evropski uniji ni dovoljeno
Gelieve de product documentatie te controleren voor specifieke odstranjevati kot nesortiran komunalni odpadek. Za posebne
batterij informatie. De batterijen met deze label kunnen volgende informacije o bateriji glejte dokumentacijo izdelka. Baterija je
indictaies bevatten cadium (Cd), lood (Pb) of kwik (Hg). Voor correcte označena s tem simbolom, ki lahko vključuje napise, ki označujejo
vorm van kringloop, geef je de producten terug aan jou locale kadmij (Cd), svinec (Pb) ali živo srebro (Hg). Za ustrezno recikliranje
leverancier of geef het af aan een gespecialiseerde verzamelpunt. baterijo vrnite dobavitelju ali jo odstranite na določenem zbirališču. Za
Meer informatie vindt u op de volgende website: www.recyclethis.info. več informacij obiščite spletno stran: www.recyclethis.info.
NO Retur av batteri SV Kassering av batteri
Dette produkt inneholder et batteri som ikke kan kastes med usortert Denna produkt innehåller ett batteri som inte får kastas i allmänna
kommunalt søppel i den Europeiske Unionen. Se sophanteringssytem inom den europeiska unionen. Se
produktdokumentasjonen for spesifikk batteriinformasjon. Batteriet er produktdokumentationen för specifik batteriinformation. Batteriet är
merket med dette symbolet som kan inkludere symboler for å indikere märkt med denna symbol, vilket kan innebära att det innehåller
at kadmium (Cd), bly (Pb), eller kvikksølv (Hg) forekommer. Returner kadmium (Cd), bly (Pb) eller kvicksilver (Hg). För korrekt återvinning
batteriet til leverandøren din eller til et dedikert oppsamlingspunkt for skall batteriet returneras till leverantören eller till en därför avsedd
korrekt gjenvinning. For mer informasjon se: www.recyclethis.info. deponering. För mer information, se: www.recyclethis.info. TR Pil Geri
PL Pozbywanie się zużytych baterii Dönüşümü Bu ürün Avrupa Birliği genel atık sistemlerine atılmaması
gereken pil içermektedir. Daha detaylı pil bilgisi için ürünün
Ten produkt zawiera baterie, które w Unii Europejskiej mogą być kataloğunu inceleyiniz. Bu sembolle işaretlenmiş piller Kadmiyum(Cd),
usuwane tylko jako posegregowane odpady komunalne. Dokładne Kurşun(Pb) ya da Civa(Hg) içerebilir. Doğru geri dönüşüm için ürünü
informacje dotyczące użytych baterii znajdują się w dokumentacji yerel tedarikçinize geri veriniz ya da özel işaretlenmiş toplama
produktu. Baterie oznaczone tym symbolem mogą zawierać noktlarına atınız. Daha fazla bilgi için: www.recyclethis.info.
dodatkowe oznaczenia literowe wskazujące na zawartość kadmu
TR Pil Geri Dönüşümü
(Cd), ołowiu (Pb) lub rtęci (Hg). Dla zapewnienia właściwej utylizacji,
należy zwrócić baterie do dostawcy albo do wyznaczonego punktu Bu ürün Avrupa Birliği genel atık sistemlerine atılmaması gereken pil
zbiórki. Więcej informacji można znaleźć na stronie internetowej içermektedir. Daha detaylı pil bilgisi için ürünün kataloğunu inceleyiniz.
www.recyclethis.info. Bu sembolle işaretlenmiş piller Kadmiyum(Cd), Kurşun(Pb) ya da
PT Eliminação de Baterias Civa(Hg) içerebilir. Doğru geri dönüşüm için ürünü yerel tedarikçinize
geri veriniz ya da özel işaretlenmiş toplama noktlarına atınız. Daha
Este produto contêm uma bateria que não pode ser considerado lixo fazla bilgi için: www.recyclethis.info.
municipal na União Europeia. Consulte a documentação do produto
para obter informação específica da bateria. A bateria é identificada Global Contacts
por meio de este símbolo, que pode incluir a rotulação para indicar o
cádmio (Cd), chumbo (Pb), ou o mercúrio (hg). Para uma reciclagem North America 905-294-6222
apropriada envie a bateria para o seu fornecedor ou para um ponto
Latin America +55 11 3614 1700
de recolha designado. Para mais informação veja:
www.recyclethis.info. Europe, Middle East, Africa +(34) 94 485 88 00
Asia +86-21-2401-3208
India +91 80 41314617

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL VII

VIII MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL
TABLE OF CONTENTS

Table of Contents
1: INTRODUCTION GETTING STARTED ...............................................................................................................................1-1
INSPECTING THE PACKAGE AND PRODUCT ..........................................................................1-1
ORDER CODES .......................................................................................................................................1-2
SPECIFICATIONS ...................................................................................................................................1-3
COMMAND LINE INTERFACE FIRMWARE ...................................................................................1-7
CONSOLE CONNECTION .........................................................................................................1-7
CONSOLE SETUP ......................................................................................................................1-7
CONSOLE SCREEN ...................................................................................................................1-8
LOGGING IN FOR THE FIRST TIME .........................................................................................1-8
AUTOMATIC IP ADDRESS CONFIGURATION .........................................................................1-8
SETTING THE IP PARAMETERS USING CONSOLE PORT ......................................................1-9
PRIVILEGE LEVELS ....................................................................................................................1-11
USER MANAGEMENT ...............................................................................................................1-12
HELP ..........................................................................................................................................1-13
EXITING .....................................................................................................................................1-14
ENERVISTA SECURE WEB MANAGEMENT .................................................................................1-15
LOGGING IN FOR THE FIRST TIME .........................................................................................1-15
PRIVILEGE LEVELS ....................................................................................................................1-17
USER MANAGEMENT ...............................................................................................................1-17
MODIFYING THE PRIVILEGE LEVEL ........................................................................................1-21
HELP ..........................................................................................................................................1-21
EXITING .....................................................................................................................................1-22
ML800 FIRMWARE UPDATES ..........................................................................................................1-23
UPDATING MULTILINK ML800 FIRMWARE .........................................................................1-23
SELECTING THE PROPER VERSION ........................................................................................1-23
UPDATING THROUGH THE COMMAND LINE .........................................................................1-23
UPDATING THROUGH THE ENERVISTA SECURE WEB MANAGEMENT SOFTWARE ..........1-25

2: PRODUCT OVERVIEW ...............................................................................................................................................2-1

DESCRIPTION PACKET PRIORITIZATION, 802.1P QOS ...............................................................................2-2
FRAME BUFFERING AND FLOW CONTROL ...........................................................................2-2
MANAGED NETWORK SOFTWARE FOR ML800 .................................................................2-3
FEATURES AND BENEFITS ................................................................................................................2-4
APPLICATIONS .......................................................................................................................................2-6

3: INSTALLATION PREPARATION ........................................................................................................................................3-1

BEFORE INSTALLING ................................................................................................................3-1
LOCATING ML800 SWITCHES ..............................................................................................3-1
CONNECTING ETHERNET MEDIA ...................................................................................................3-3
CONNECTING TWISTED PAIR (CAT3, CAT5, UTP OR STP) .............................................3-3
CONNECTING TWISTED PAIR (CAT5E OR BETTER, UTP OR STP) ....................................3-4
CONNECTING SINGLE-MODE FIBER OPTIC ..........................................................................3-4
GIGABIT SFP (SMALL FORM-FACTOR PLUGGABLE) TRANSCEIVERS .................................3-4
CONNECTING FIBER OPTIC CABLE TO SFP TRANSCEIVERS ..............................................3-5
MECHANICAL INSTALLATION .........................................................................................................3-6
MOUNTING DIMENSIONS FOR ML800 WITH METAL BRACKETS .......................................3-6
ELECTRICAL INSTALLATION .............................................................................................................3-8
POWERING THE MULTILINK ML800 MANAGED EDGE SWITCH .....................................3-8

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL TOC–1

TABLE OF CONTENTS

ALARM CONTACTS FOR MONITORING INTERNAL POWER, AND SOFTWARE TRAPS .......3-8
CONNECTING THE CONSOLE TERMINAL TO MULTILINK ML800 ......................................3-9

4: OPERATION FUNCTIONALITY ....................................................................................................................................4-1

SWITCHING FUNCTIONALITY ..................................................................................................4-1
AUTO-CROSS (MDIX) AND AUTO-NEGOTIATION FOR RJ-45 PORTS ..............................4-2
FLOW-CONTROL, IEEE 802.3X STANDARD ........................................................................4-3
POWER BUDGET CALCULATIONS FOR ML800 MODULES WITH FIBER MEDIA ..............4-3
MULTILINK ML800 MANAGED EDGE SWITCH PORT MODULES ......................................4-4
ML800 MODULES ..................................................................................................................4-4
ML800 BASE UNIT LED DESIGNATIONS ............................................................................4-6
ML800-48PS, BASE UNIT W/POE POWER-PASS-THROUGH .........................................4-11
TROUBLESHOOTING ...........................................................................................................................4-12
BEFORE CALLING FOR ASSISTANCE ......................................................................................4-12

5: IP ADDRESSING IP ADDRESS AND SYSTEM INFORMATION .................................................................................5-1

OVERVIEW ................................................................................................................................5-1
IMPORTANCE OF AN IP ADDRESS .................................................................................................5-3
DHCP AND BOOTP .................................................................................................................5-3
BOOTP DATABASE ....................................................................................................................5-3
CONFIGURING DHCP/BOOTP/MANUAL/AUTO ................................................................5-3
USING TELNET .........................................................................................................................5-5
SETTING PARAMETERS ......................................................................................................................5-8
SETTING SERIAL PORT PARAMETERS ....................................................................................5-8
SYSTEM PARAMETERS .............................................................................................................5-8
DATE AND TIME .......................................................................................................................5-10
NETWORK TIME .......................................................................................................................5-10
SYSTEM CONFIGURATION ................................................................................................................5-14
SAVING AND LOADING – COMMAND LINE ..........................................................................5-14
CONFIG FILE .............................................................................................................................5-14
DISPLAYING CONFIGURATION ................................................................................................5-17
SAVING CONFIGURATION .......................................................................................................5-20
SCRIPT FILE ..............................................................................................................................5-22
SAVING AND LOADING – ENERVISTA SOFTWARE ...............................................................5-23
HOST NAMES ...........................................................................................................................5-25
ERASING CONFIGURATION .....................................................................................................5-27
IPV6 ............................................................................................................................................................5-31
INTRODUCTION TO IPV6 .........................................................................................................5-31
WHAT’S CHANGED IN IPV6? .................................................................................................5-31
IPV6 ADDRESSING ..................................................................................................................5-32
CONFIGURING IPV6 ................................................................................................................5-32
LIST OF COMMANDS IN THIS CHAPTER ..................................................................................5-34

6: ACCESS SECURING ACCESS ..............................................................................................................................6-1

CONSIDERATIONS DESCRIPTION ............................................................................................................................6-1
PASSWORDS .............................................................................................................................6-1
PORT SECURITY FEATURE .......................................................................................................6-2
CONFIGURING PORT SECURITY THROUGH THE COMMAND LINE INTERFACE .........6-3
COMMANDS ..............................................................................................................................6-3
ALLOWING MAC ADDRESSES ...............................................................................................6-4
SECURITY LOGS ........................................................................................................................6-8

TOC–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

TABLE OF CONTENTS

AUTHORIZED MANAGERS .......................................................................................................6-10

CONFIGURING PORT SECURITY WITH ENERVISTA SOFTWARE .......................................6-12
COMMANDS .............................................................................................................................. 6-12
LOGS .........................................................................................................................................6-15
AUTHORIZED MANAGERS .......................................................................................................6-16

7: ACCESS USING RADIUS INTRODUCTION TO 802.1X ..............................................................................................................7-1

DESCRIPTION ............................................................................................................................7-1
802.1X PROTOCOL .................................................................................................................7-1
CONFIGURING 802.1X THROUGH THE COMMAND LINE INTERFACE ...........................7-4
COMMANDS .............................................................................................................................. 7-4
EXAMPLE ...................................................................................................................................7-6
CONFIGURING 802.1X WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE 7-9
COMMANDS .............................................................................................................................. 7-9

8: ACCESS USING INTRODUCTION TO TACACS+ .........................................................................................................8-1

TACACS+ OVERVIEW ................................................................................................................................8-1
TACACS+ FLOW ....................................................................................................................8-2
TACACS+ PACKET .................................................................................................................8-2
CONFIGURING TACACS+ THROUGH THE COMMAND LINE INTERFACE ......................8-4
COMMANDS .............................................................................................................................. 8-4
EXAMPLE ...................................................................................................................................8-4
CONFIGURING TACACS+ WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE 8-6

9: PORT MIRRORING AND PORT MIRRORING ................................................................................................................................9-1

SETUP DESCRIPTION ............................................................................................................................9-1
PORT MIRRORING USING THE COMMAND LINE INTERFACE ............................................9-2
COMMANDS .............................................................................................................................. 9-2
PORT SETUP ...........................................................................................................................................9-3
COMMANDS .............................................................................................................................. 9-3
FLOW CONTROL ......................................................................................................................9-5
BACK PRESSURE ......................................................................................................................9-5
BROADCAST STORMS ..............................................................................................................9-7
LINK LOSS ALERT ....................................................................................................................9-9
PORT MIRRORING USING ENERVISTA SECURE WEB MANAGEMENT SOFTWARE ...9-11
COMMANDS .............................................................................................................................. 9-11
PORT SETUP .............................................................................................................................9-12
BROADCAST STORMS ..............................................................................................................9-15

10: VLAN VLAN DESCRIPTION ............................................................................................................................10-1

OVERVIEW ................................................................................................................................10-1
TAG VLAN VS. PORT VLAN .................................................................................................10-3
CONFIGURING PORT VLANS THROUGH THE COMMAND LINE INTERFACE ...............10-5
DESCRIPTION ............................................................................................................................10-5
COMMANDS .............................................................................................................................. 10-5
CONFIGURING PORT VLANS WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE
10-7
DESCRIPTION ............................................................................................................................10-7
CONFIGURING TAG VLANS THROUGH THE COMMAND LINE INTERFACE ..................10-12
DESCRIPTION ............................................................................................................................10-12

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL TOC–3

TABLE OF CONTENTS

COMMANDS ..............................................................................................................................10-12
EXAMPLE ...................................................................................................................................10-13
CONFIGURING TAG VLANS WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE
10-19
DESCRIPTION ............................................................................................................................10-19

11: VLAN REGISTRATION OVERVIEW ...............................................................................................................................................11-1

OVER GARP DESCRIPTION ............................................................................................................................11-1
GVRP CONCEPTS ....................................................................................................................11-1
GVRP OPERATIONS ................................................................................................................11-2
CONFIGURING GVRP THROUGH THE COMMAND LINE INTERFACE ..............................11-6
COMMANDS ..............................................................................................................................11-6
GVRP OPERATION NOTES .....................................................................................................11-6
CONFIGURING GVRP WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE 11-8
EXAMPLE ...................................................................................................................................11-8

12: SPANNING TREE OVERVIEW ...............................................................................................................................................12-1

PROTOCOL (STP) DESCRIPTION ............................................................................................................................12-1
FEATURES AND OPERATION ...................................................................................................12-1
CONFIGURING STP ..............................................................................................................................12-3

13: RAPID SPANNING OVERVIEW ...............................................................................................................................................13-1

TREE PROTOCOL DESCRIPTION ............................................................................................................................13-1
RSTP CONCEPTS .....................................................................................................................13-1
TRANSITION FROM STP TO RSTP .........................................................................................13-2
CONFIGURING RSTP THROUGH THE COMMAND LINE INTERFACE ...............................13-4
NORMAL RSTP ........................................................................................................................13-4
SMART RSTP (RING-ONLY MODE) THROUGH THE COMMAND LINE INTERFACE (CLI) .13-13
CONFIGURING STP/RSTP WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE
13-15
NORMAL RSTP ........................................................................................................................13-15
SMART RSTP (RING-ONLY MODE) WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE
13-19

14: QUALITY OF SERVICE QOS OVERVIEW ....................................................................................................................................14-1

DESCRIPTION ............................................................................................................................14-1
QOS CONCEPTS .......................................................................................................................14-1
DIFFSERV AND QOS ...............................................................................................................14-2
IP PRECEDENCE .......................................................................................................................14-2
CONFIGURING QOS THROUGH THE COMMAND LINE INTERFACE ................................14-4
COMMANDS ..............................................................................................................................14-4
EXAMPLE ...................................................................................................................................14-6
CONFIGURING QOS WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE ..14-9
DESCRIPTION ............................................................................................................................14-9

15: IGMP OVERVIEW ...............................................................................................................................................15-1

DESCRIPTION ............................................................................................................................15-1
IGMP CONCEPTS ....................................................................................................................15-1
IP MULTICAST FILTERS ...........................................................................................................15-4
RESERVED ADDRESSES EXCLUDED FROM IP MULTICAST (IGMP) FILTERING .................15-4

TOC–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

TABLE OF CONTENTS

IGMP SUPPORT .......................................................................................................................15-5

CONFIGURING IGMP THROUGH THE COMMAND LINE INTERFACE ...............................15-6
COMMANDS .............................................................................................................................. 15-6
EXAMPLE ...................................................................................................................................15-8
CONFIGURING IGMP WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE 15-11
EXAMPLE ...................................................................................................................................15-11

16: SNMP OVERVIEW ...............................................................................................................................................16-1

DESCRIPTION ............................................................................................................................16-1
SNMP CONCEPTS ...................................................................................................................16-1
TRAPS ........................................................................................................................................16-3
STANDARDS .............................................................................................................................. 16-3
CONFIGURING SNMP THROUGH THE COMMAND LINE INTERFACE .............................16-5
COMMANDS .............................................................................................................................. 16-5
EXAMPLE ...................................................................................................................................16-6
CONFIGURING SNMP WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE 16-11
EXAMPLE ...................................................................................................................................16-11
CONFIGURING RMON ........................................................................................................................16-15
DESCRIPTION ............................................................................................................................16-15
COMMANDS .............................................................................................................................. 16-15

17: MISCELLANEOUS E-MAIL .......................................................................................................................................................17-1

COMMANDS DESCRIPTION ............................................................................................................................17-1
COMMANDS .............................................................................................................................. 17-2
EXAMPLE ...................................................................................................................................17-3
STATISTICS ..............................................................................................................................................17-5
VIEWING PORT STATISTICS WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE 17-5
SERIAL CONNECTIVITY .......................................................................................................................17-7
DESCRIPTION ............................................................................................................................17-7
HISTORY ...................................................................................................................................................17-8
COMMANDS .............................................................................................................................. 17-8
PING ...........................................................................................................................................................17-9
PING THROUGH THE COMMAND LINE INTERFACE ..............................................................17-9
PING THROUGH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE ...........................17-9
PROMPT ....................................................................................................................................................17-10
CHANGING THE COMMAND LINE PROMPT ..........................................................................17-10
SYSTEM EVENTS ...................................................................................................................................17-11
DESCRIPTION ............................................................................................................................17-11
COMMAND LINE INTERFACE EXAMPLE .................................................................................17-11
ENERVISTA EXAMPLE ..............................................................................................................17-12
COMMAND REFERENCE ....................................................................................................................17-14
MAIN COMMANDS ...................................................................................................................17-14
CONFIGURATION COMMANDS ................................................................................................17-16

18: MODBUS PROTOCOL MODBUS CONFIGURATION .............................................................................................................18-1

OVERVIEW ................................................................................................................................18-1
COMMAND LINE INTERFACE SETTINGS .................................................................................18-1
ENERVISTA SETTINGS ..............................................................................................................18-3
MEMORY MAPPING .............................................................................................................................18-4
MODBUS MEMORY MAP ........................................................................................................18-4
FORMAT CODES .......................................................................................................................18-37

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL TOC–5

TABLE OF CONTENTS

A: REVISION HISTORY & REVISION HISTORY ..............................................................................................................................A-1

WARRANTY CHANGE NOTES .......................................................................................................................A-1
CHANGES TO THE MANUAL ....................................................................................................A-1
WARRANTY .............................................................................................................................................A-3
GE DIGITAL ENERGY WARRANTY STATEMENT ....................................................................A-3

B: DC POWER INPUT SPECIFICATIONS FOR MULTILINK ML800 SWITCHES, DC POWER AT 12, 24, –48, 125, AND
250 V DC POWER INPUT ...............................................................................B-1
12, 24, –48, 125, AND 250 V DC POWER, THEORY OF OPERATION ..............................B-3
APPLICATIONS FOR DC-POWERED ETHERNET SWITCHES ................................................B-4
ML800, 12, 24, –48, 125, AND 250 V DC INSTALLATION ...................................................B-5
UL REQUIREMENTS FOR DC-POWERED UNITS ...................................................................B-5
OPERATION .............................................................................................................................................B-6

C: INTERNAL DC DUAL- SPECIFICATIONS - FOR MULTILINK ML800 EDGE SWITCH ................................................C-1

SOURCE POWER MULTILINK ML800, WITH DC DUAL-SOURCE OPTION ........................................................C-3
INPUT OPTION DUAL-SOURCE OPTION, THEORY OF OPERATION .................................................................C-4
FEATURES AND BENEFITS OF THE DUAL-SOURCE DESIGN ..............................................C-5
INSTALLATION .......................................................................................................................................C-6

TOC–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 1: Introduction
Introduction

1.1 Getting Started

1.1.1 Inspecting the Package and Product

Examine the shipping container for obvious damage prior to installing this product; notify
the carrier of any damage that you believe occurred during shipment or delivery. Inspect
the contents of this package for any signs of damage and ensure that the items listed
below are included.
This package should contain:
1. ML800 Managed Edge Switch, base unit (configured with user-selected port
module options installed)
2. Set of two metal vertical mounting brackets, with screws to the case
3. ML800 Installation and User Guide (this manual).
Remove the items from the shipping container. Be sure to keep the shipping container
should you need to re-ship the unit at a later date.
In the event there are items missing or damaged, contact the party from whom you
purchased the product. If the unit needs to be returned, please use the original shipping
container if possible. Refer to Section 4.3, Troubleshooting, for specific return procedures.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–1

INTRODUCTION CHAPTER 1: INTRODUCTION

1.2 Order Codes

1–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.3 Specifications
PERFORMANCE
Filtering / Forwarding Rate:.. Ethernet (10Mb): 14,880 pps
Fast Ethernet (100Mb): 148,800 pps
Gigabit Ethernet (1000Mb): 1,488,000 pps
Switching Processing Type: .. Store and Forward with IEEE 802.3x full-duplex flow -control, non-
blocking
Data Rate:..................................... 10Mbps, 100Mbps and 1000Mbps
Address Table Capacity:......... 4K node, self-learning with address aging
Packet buffer size:..................... 240KB for 10/100 and 120KB for 1000Mb
Latency: ......................................... 5 μs + packet time (100 to 100Mbps)
15 μs + packet time (10 to 10 Mbps, and 10 to 100Mbps)
Throughput with 8 10/100 and 2Glink max: 4.17M pps (Transmit)
Back plane:................................... 2.66Gb/s per slot

NETWORK STANDARDS AND COMPLIANCE, HARDWARE

Ethernet V1.0/V2.0 IEEE 802.3:10BASE-T,
IEEE 802.3u:.................................. 100Base-TX, 100BASE-FX
IEEE 802.3z: .................................. 1000BASE-X Ethernet (Auto-negotiation)
IEEE 802.3ab:............................... 1000BASE-X Ethernet
IEEE 802.1p:.................................. Priority protocol
IEEE 802.1d:.................................. Spanning tree protocol
IEEE 802.1w:................................. Rapid Spanning tree protocol
IEEE 802.1q:.................................. VLAN Tagging
IEEE 802.3x: .................................. Flow Control
IEEE 802.3ad:............................... Link Aggregation (Trunking)
IEEE 802.1x: .................................. Port based Network access control
IEEE 802.3af: ................................ Power over Ethernet

MAXIMUM 10 MBPS ETHERNET SEGMENT LENGTHS

Unshielded twisted pair: ........ 100 m (328 ft)
Shielded twisted pair:.............. 150 m (492 ft)
10BASE-FL multi-mode fiber optic:2 km (6,562 ft)
10BASE-FL single-mode fiber optic:10 km (32,810 ft)

MAXIMUM STANDARD FAST ETHERNET SEGMENT LENGTHS

10BASE-T (CAT 3, 4, 5 UTP) .... 100 m (328 ft)
100BASE-TX (CAT 5 UTP)......... 100 m (328 ft)
Shielded twisted pair............... 150 m (492 ft)
100BASE-FX, half-duplex, multi-mode412 m (1350 ft)
100BASE-FX, full-duplex, multi-mode2.0 km (6,562 ft)
100BASE-FX, half-duplex, single-mode412 m (1350 ft)
100BASE-FX, full-duplex, single-mode20.0 km (66K ft)
100BASE-FX, full-duplex, Long Reach40.0 km (122K ft)

MAXIMUM STANDARD GIGABIT ETHERNET SEGMENT LENGTHS

1000BASE-T (CAT5e or higher is recommended:100m (328 ft)
1000BASE-SX, full-duplex, multi-mode (62.5μm cable):220m
1000BASE-SX, full-duplex, multi-mode (50μm cable):550m
1000BASE-LX, full-duplex, multi-mode (50, 62.5μm cable): 550m
1000BASE-LX, full-duplex, single-mode (9μm cable):5km
1000BASE-ZX, full duplex, single-mode (9μm cable): >70km

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–3

INTRODUCTION CHAPTER 1: INTRODUCTION

FIBER MULTI-MODE CONNECTOR TYPES SUPPORTED

Fiber Port, MTRJ-type (plug-in):SFF Fiber multi-mode 100BASE-FX
Fiber Port, LC-type (plug-in):. SFF Fiber multi-mode 100BASE-FX
Fiber Port, 1000BASE-SX, SFP modules

FIBER SINGLE-MODE CONNECTOR TYPES:

Fiber Port, LC-type Fiber SFF single-mode, 100BASE-FX
Fiber Port, 1000BASE-LX, SFP modules

LEDS PER PORT

One set at the port, one set on swivel top on right side
(See section 4.2.1 and 4.2.2 for detailed LED configurations)

OPERATING ENVIRONMENT
Ambient Temperature:............ -40° to 140° F (-40° to 60°C) for UL60950 and Component Parts
rating
-40° to 195° F (-40° to 85°C) for IEC 60068 Type Test short term
rating
Storage Temperature: ............. -60°to 210°F (-50°to 100°C)
Ambient Relative Humidity: .. 5% to 95% (non-condensing)
Altitude: .......................................... -200 to 13,000 ft. (-60 to 4000m)
Conformal Coating (humidity protection) optional:Request quote

ALARM RELAY CONTACTS

One NC indicating internal power, one NC software controllable

PACKAGING
Enclosure:...................................... High strength extruded aluminum
Dimensions:.................................. 6.85 in. H x 7.5 in. W x 2.0 in. D
17.4 cm H x 19.1 cm W x 5.08 cm D
Cooling method: ........................ Convection, fully-enclosed ribbed-surface aluminum case used as
a sink, designed for vertical mounting, no fans
Weight: ........................................... 3 lbs. (1.3 kg)

MANAGEMENT CONSOLE CONNECTOR

Serial DB-9, see details at sec. 3.6

DC POWER SUPPLY (INTERNAL, FLOATING GROUND DESIGN)

12 V DC Power Input nominal (range 8 to 18 V DC)
24 V DC Power Input nominal (range 18 to 36 V DC)
-48 V DC Power Input nominal (range 36 to 60 V DC)
125 V DC Power Input nominal (range 88 to 150 V DC)
250 V DC Power Input nominal (range 160 to 300 V DC)
Std. Terminal Block: .................. “ -, GND, + ”

AC POWER SUPPLY (INTERNAL)

AC Power Connector:............... IEC-type, male recessed
100-240 V AC Power Input, 47 to 63 Hz (auto-ranging)

POWER CONSUMPTION
20 watts max. (for a fully loaded fiber model with 2 Gb)
15 watts max. (for 8 port copper and 100Mb fiber model)

DUAL DC POWER INPUT (OPTIONAL)

A Dual-Source option is available for the 12 V DC, 24 V DC, –48 V DC, and 125 V DC and 250 V DC
models. This provides for continuity of operation when either of the DC input sources is
interrupted. See Appendices B and C.
The Dual-Source Terminal Block is marked :“ +A, -A, -B, +B ”

1–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

ML800 MOUNTING
Vertical mounting normal. Suitable for wall or DIN-Rail mounting (ML800)

TYPE TESTS

TEST REFERENCE STANDARD TEST LEVEL

Electrostatic Discharge EN61000-4-2 Level 4

RF immunity EN61000-4-3 Level 3
Fast Transient Disturbance EN61000-4-4 Level 3 & 4
Surge Immunity EN61000-4-5 Level 4
Conducted RF Immunity EN61000-4-6 Level 3
Power magnetic Immunity IEC61000-4-8 Level 2
0,40,70% dips,250/
Voltage Dip & interruption IEC61000-4-11
300cycle interrupts
Environmental (Cold) DNV 2.4 -25 C
Environmental (Dry heat) DNV 2.4 70 C
Relative Humidity Cyclic DNV 2.4 2 day
Radiated & Conducted
CISPR22/ IEC60255-25 Class A
Emissions
Radiated & Conducted
FCC Part 15 Subpart B Class A
Emissions
Safety EN60950-1 standard
Harmonics EN61000-3-2
Flicker EN61000-3-3
Ingress Protection IEC60529 IP20A
Sinusoidal Vibration DNV 2.4 1 to 4 G

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–5

INTRODUCTION CHAPTER 1: INTRODUCTION

APPROVALS

Applicable Council Directive According to

CE Compliance Low voltage directive EN60950-1
EMC Directive EN61000-6-2, EN61000-6-4

North America cULus UL60950-1

C22.2 No. 60950-1

Manufactured under a registered ISO9001

ISO
quality program

WARRANTY
Three years, per UL 60950 temperature ratingMade in USA

1–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.4 Command Line Interface Firmware

1.4.1 Console Connection

The connection to the console is accessed through the DB-9 RS232 connector on the
switch marked as the console port. This command line interface (or CLI) provides access to
the switch commands. It can be accessed by attaching a VT100 compatible terminal or a
PC running terminal emulation firmware to the console port.
USB-to-serial adapters are also available for computers that do not support native serial
ports but have access to USB ports.
The interface through the console or the console management interface (or CMI) enables
you to reconfigure the switch and to monitor switch status and performance.

Once the switch is configured with an IP address, the command line interface (or CLI) is
also accessible using telnet as well as the serial port. Access to the switch can be either
through the console interface or remotely over the network. Simultaneous access (that is,
through the console port as well as through the network) to the MultiLink ML800 Managed
Edge Switch switch is not permitted.
The Command Line Interface (CLI) enables local or remote unit installation and
maintenance. The MultiLink ML800 Managed Edge Switch provides a set of system
commands which allow effective monitoring, configuration and debugging of the devices
on the network.

1.4.2 Console Setup

Connect the console port on the switch to the serial port on the computer using the serial
cable listed above. The settings for the HyperTerminal firmware emulating a VT100 are
shown below. Make sure the serial parameters are set as shown (or bps = 38400, data bits
= 8, parity = none, stop bits = 1, flow control = none).

FIGURE 1–1: Serial Settings in HyperTerminal

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–7

INTRODUCTION CHAPTER 1: INTRODUCTION

1.4.3 Console Screen

Once the console cable is connected to the PC and the firmware configured, ML800 legal
disclaimers and other text scrolls by on the screen.
The line interface prompt appears displaying the switch model number (e.g. ML800>)
The switch has three modes of operation: operator (least privilege), manager, and
configuration. The prompts for the switches change as the switch changes modes from
operator to manager to configuration. The prompts are shown below with a brief
description.
• ML800>
Operator Level - for running operations queries
• ML800#
Manager Level - for setting and reviewing commands
• ML800##
Configuration Level - for changing the switch parameter values
For additional information on default users, user levels and more, refer to User
Management on page 1–12.

1.4.4 Logging In for the First Time

For the first time, use the default user name and passwords assigned by GE. They are:
• Username: manager
Password: manager
• Username: operator
Password: operator
We recommend you login as manager for the first time to set up the IP address as well as
change user passwords or create new users.

1.4.5 Automatic IP Address Configuration

The ML800 is operational immediately after it is powered up. The advanced management
and configuration capabilities of the ML800 allows you to easily configure, manage, and
secure your devices and network.
Before starting, ensure you have the following items:
• RJ45 Ethernet cable
• PC with an Ethernet port
• Microsoft Internet Explorer 6.0 or higher
• Macromedia Flash Player 5.0 or higher (available from http://
www.macromedia.com/shockwave/download/
download.cgi?P1_Prod_Version=ShockwaveFlash)
Ensure both firmware components are installed before proceeding.
The ML800 can search the network for commonly used services that can issue an IP
address. If the switch is connected to a network, the ML800 uses the following process to
find an IP address.

If the ML800 is not connected to a network, then proceed to Step 3 below. or use the
Note

default IP address.
NOTE

1–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

Step 1:
The ML800 will scan the network for a DHCP server. If the server responds, the ML800 will
acquire and set the assigned IP address. To manage the switch, determine the assigned IP
address and enter as follows in Internet Explorer:
https://<assigned_IP_address>
Ensure that https is entered, not http, and that there is connectivity (that is, you can ping
the switch).
Step 2:
If there is no response from a DCHP server, the ML800 will query for a BOOTP server. If the
server responds, the ML800 will acquire and set the assigned IP address. To manage the
switch, determine the assigned IP address and enter as follows in Internet Explorer:
https://<assigned_IP_address>
Ensure that https is entered, not http, and that there is connectivity (that is, you can ping
the switch).
Step 3:
If there is no response from either a DCHP or BOOTP server, or if the switch is not
connected to a network, the switch will assign itself an IP address. The ML800 will check to
see if IP address 192.168.1.2, with a network mask of 255.255.255.0, is free. If so, it will
assume these values. If this IP address is assigned to another device, the ML800 will repeat
steps 1 through 3 to find a DCHP or BOOTP server or wait for the 192.168.1.2 address to
become free.
Once connected, the browser will display a login prompt. The default login is:
• Username: manager
Password: manager

1.4.6 Setting the IP Parameters Using Console Port

To setup the switch, the IP address and other relevant TCP/IP parameters have to be
specified.
The IP address on the MultiLink ML800 Managed Edge Switch is set to 192.168.1.2 from the
factory. The switch is fully operational as a Layer 2 switch as a default. Setting a default IP
address can potentially cause duplicate IP address problem if multiple switches are
powered on and installed on the network. To manage the switch, an IP address has to be
programmed.
Before starting, please ensure that the IP address assigned to the switch is known or
contact your system/network administrator to get the IP address information. Follow the
steps listed below to configure the switch.
 Ensure the power is off.
 Follow the steps described above for connecting the console cable
and setting the console firmware.
 Power on the switch.
 Once the login prompt appears, login as manager using default
password (manager).
 Configure the IP address, network mask and default gateway as per
the IP addressing scheme for your network.
 Set the manager password (this step is recommended; refer to the
following section).

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–9

INTRODUCTION CHAPTER 1: INTRODUCTION

 Save the settings (without saving, the changes made will be lost).
 Power off the switch (or a firmware reboot as discussed below).
 Power on the switch - login with the new login name and password.
 From the PC (or from the switch) ping the IP address specified for the
switch to ensure connectivity.
 From the switch ping the default gateway specified (ensure you are
connected to the network to check for connectivity) to ensure
network connectivity.
Syntax:
ipconfig [ip=<ip-address>] [mask=<subnet-mask>] [dgw=<gateway>]
An example is shown below.
ML800# ipconfig ip=3.94.247.41 mask=255.255.252.0
dgw=3.94.244.41
ML800# save

This manual assumes the reader is familiar with IP addressing schemes as well as how net
Note

mask is used and how default gateways and routers are used in a network.
NOTE
Reboot gives an opportunity to save the configuration prior to shutdown. For a reboot,
simply type in the command reboot . Note that even though the passwords are not
changed, they can be changed later.
ML800# reboot
Proceed on rebooting the switch? ['Y' or 'N'] Y
Do you wish to save current configuration? ['Y' or 'N'] Y
ML800#
The ML800 forces an answer by prompting with a “Y” or a “N” to prevent accidental
keystroke errors and loss of work.
The parameters can be viewed at any time by using the show command. The show
command will be covered in more detail later in various sections throughout the
document.
The example below illustrates the basic setup parameters. You can use show setup or
show sysconfig commands to view setup parameters.

1–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

ML800# show setup

Version: ML800 build 2.1.0 Nov 12 2007 11:10:13
MAC Address: 00:20:06:27:0a:e0
IP Address: 3.94.247.41
Subnet Mask: 255.255.252.0
Gateway Address: 3.94.244.1
CLI Mode: Manager
System Name: ML800
System Description: 6 Port Modular Ethernet Switch
System Contact: multilin.tech@ge.com
System Location: Markham, Ontario
System ObjectId: 1.3.6.1.4.1.13248.12.7
ML800# show sysconfig
System Name: ML800
System Contact: multilin.tech@ge.com
System Location: Markham, Ontario
Boot Mode: manual
Inactivity Timeout(min): 120
Address Age Interval(min): 300
Inbound Telnet Enabled: Yes
Web Agent Enabled: Yes
Time Zone: GMT-05hours:00minutes
Day Light Time Rule: Canada
System UpTime: 0 Days 0 Hours 45 Mins 55 Secs
ML800#
Some of the parameters in the MultiLink ML800 Managed Edge Switch are shown above.
The list of parameters below indicates some of the key parameters on the switch and the
recommendations for changing them (or optionally keeping them the same).

1.4.7 Privilege Levels

Two privilege levels are available - manager and operator. Operator is at privilege level 1
and the manager is at privilege level 2 (the privilege increases with the levels). For example,
to set up a user for basic monitoring capabilities use lower number or operator level
privilege (level 1).
The Manager level provides all operator level privileges plus the ability to perform system-
level actions and configuration commands. To select this level, enter the enable <user-
name> command at the Operator level prompt and enter the Manager password, when
prompted.
enable <user-name>
For example, switching from an operator-level to manager-level, using the enable
command is shown below.
ML800> enable manager
Password: *******
ML800#
Note the prompt changes with the new privilege level.
Operator privileges allow views of the current configurations but do not allow changes to
the configuration. A “>” character delimits the operator-level prompt.
Manager privileges allow configuration changes. The changes can be done at the
manager prompt or for global configuration as well as specific configuration. A “#”
character delimits any manager prompt.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–11

INTRODUCTION CHAPTER 1: INTRODUCTION

1.4.8 User Management

A maximum of five users can be added per switch. Users can be added, deleted or
changed from a manager level account. There can be more than one manager account,
subject to the maximum number of users on the switch being restricted to five.
To add a user, use the add command as shown below. The user name has to be a unique
name. The password is recommended to be at least 8 characters long with a mix of upper
case, lower case, numbers and special characters.
add user=<name> level=<number>
The following example adds a user “peter” with manager-level privilege:
ML800# user
ML800(user)## add user=peter level=2
Enter User Password:******
Confirm New Password:******
ML800(user)##
To delete a user, use the delete command as shown below.
delete user=<name>
The following example deletes the user “peter”:
ML800(user)## delete user=peter
Confirm User Deletion(Y/N): Y
User successfully deleted
ML800(user)##
The syntax to modify a password is shown below:
passwd user=<name>
The following example changes the password for user “peter”.
ML800(user)## passwd user=peter
Enter New Password:******
Confirm New Password :******
Password has been modified successfully
ML800(user)##
The syntax to modify the privilege level for a specific user is shown below:
chlevel user=<name> level=<number>
The following example modifies the privilege level of user “peter” to Operator privileges.
ML800(user)## chlevel user=peter level=1
Access Permission Modified
ML800(user)##
The syntax to set the access privileges for telnet and Web services is shown below:
useraccess user=<name> service=<telnet|web> <enable|disable>
The following example sets the access privileges for telnet and Web services.
ML800(user)## useraccess user=peter service=telnet disable
Telnet Access Disabled.

1–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.4.9 Help
Typing the help command lists the commands you can execute at the current privilege
level. For example, typing help at the Operator level shows the following:
ML800> help
logout ping set
terminal telnet walkmib
Contextless Commands:
! ? clear
enable exit help
show whoami
alarm
ML800>
Help for any command that is available at the current context level can be viewed by
typing help followed by enough of the command string to identify the command. The
following syntax applies:
help <command string>
For example, to list the help for the set time command
ML800# help set time
set time : Sets the device Time
Usage
set time hour=<0-23> min=<0-59> sec=<0-59> [zone=GMT[+/-]hh:mm]
ML800#
The options for a specific command can be displayed by typing the command and
pressing enter. The following syntax applies:
command <Enter>
For example, the options for the show command are:
ML800# show <Enter>
Usage
show active-stp
show active-snmp
show active-vlan
show address-table
show age
show alarm
show arp
show auth <config|ports>
show backpressure
show bootmode
--more--
Other ways to display help, specifically, with reference to a command or a set of
commands, use the TAB key. The following syntax applies:
<TAB>
<Command string> <TAB>
<First character of the command> <TAB>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–13

INTRODUCTION CHAPTER 1: INTRODUCTION

For example, following the syntax listed above, the <TAB> key will list the available
commands in the particular privilege level:
ML800> <TAB>
?
alarm
clear
enable
exit
help
logout
ping
set
show
telnet
terminal
walkmib
whoami
ML800>
The following example lists commands starting with a specific string:
ML800> s <TAB>
set
show
ML800>
In the following example, the <TAB> key completes the command:
ML800> se<TAB>
password
timeout
vlan
ML800> set

1.4.10 Exiting
To exit from the CLI interface and terminate the console session use the logout
command. This command prompts to ensure that the logout was not mistakenly typed.
The following syntax applies:
logout
The following example illustrates logging out from a session:
ML800> logout
Logging out from the current session [’Y’ or ’N’] Y
Connection to the host lost

1–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.5 EnerVista Secure Web Management

1.5.1 Logging in for the First Time

Enter the following URL in the web browser to login to the EnerVista Secure Web
Management software.
https://<IP Address assigned to the switch>

Make sure you use HTTPS (secure HTTP) and not HTTP in the URL.
Note

In the example shown in the previous section, the URL is:

https://3.94.247.41
If your site uses name services, you can use a name instead of the IP address. Please make
sure that the name is resolved to the IP address assigned to the switch.
The secure site will issue the certificate check shown below.

FIGURE 1–2: Security certificate

Once you click Yes on the security certificate, the browser will prompt you to login.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–15

INTRODUCTION CHAPTER 1: INTRODUCTION

FIGURE 1–3: Login screen

For the first time,

 Login with the name manager and password manager.
 Click on Login.
After a successful login, the welcome screen is shown. Note the different information
provided on the screen and different areas. The menus are used to configure settings on
the switch. Users can click on a specific port to open the port configuration view.

FIGURE 1–4: Welcome screen

1–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.5.2 Privilege Levels

• Operator privilege users: operator privileges allow views of the current
configurations but do not allow changes to the configuration.
• Manager privilege users: manager privileges allow configuration changes. The
changes can be done at the manager prompt or for global configuration as well as
specific configuration.

1.5.3 User Management

A maximum of five users can be added per switch. Users can be added, deleted or
changed from a manager level account. There can be more than one manager account,
subject to the maximum number of users on the switch being restricted to five.
 Select the Administration > User Mgmt > User Accounts menu
item.
 To add a user, use the add button.
The username must be a unique name. The password is recommended to be at least 8
characters long with a mix of upper case, lower case, numbers and special characters.

In the following example below, the user peter was added with manager privilege after
clicking the add button.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–17

INTRODUCTION CHAPTER 1: INTRODUCTION

After successfully adding a user, the added user is displayed in the list of users as shown
below.

1–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

 To delete a user, click on the delete icon ( )as shown below.

The firmware will prompt to verify the delete command.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–19

INTRODUCTION CHAPTER 1: INTRODUCTION

 To modify the password, view the users as described above and click
on the edit icon ( ).

After clicking on the edit icon, the screen opens up for modifying the password.

In this example, the user ID peter was selected for modification. The password for peter
will be modified after the new password is entered.

1–20 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.5.4 Modifying the Privilege Level

Privilege levels cannot be changed from the EnerVista Secure Web Management (SWM)
firmware. This can only be done through the CLI interface, or alternately, by deleting the
user and adding the same user with the proper privilege level.

1.5.5 Help
Help for the EnerVista Secure Web Management software can be obtained by clicking on
the Help icon as shown below.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–21

INTRODUCTION CHAPTER 1: INTRODUCTION

1.5.6 Exiting
 To exit or logout, click on the logout button.

 Confirm the logout by selecting OK in the pop-up window.

1–22 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

1.6 ML800 Firmware Updates

1.6.1 Updating Multilink ML800 Firmware

This section describes the process for upgrading firmware on a ML800 Switch Module.
There are several ways of updating Firmware on a Multilink ML800: Serial using the
Multilink ML800’s Console port, tftp or through ftp.

1.6.2 Selecting the Proper Version

The latest version of the firmware is available as a download from the GE Digital Energy
web site.
To determine the version of firmware currently installed on your Switch, proceed as
follows:
 Using the EnerVista web interface, log into the Switch using the
procedure described earlier. The firmware version installed on the
switch will appear on the lower left corner of the screen.

Version #

1.6.3 Updating through the Command Line

Use the following procedure to install firmware to the ML800 via the serial port.
 Download the MultiLink Switch Software from the GE Digital Energy
web site.
 Use the null-modem cable to connect to the ML800 serial port.
 Login at the manager level with the proper password.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–23

INTRODUCTION CHAPTER 1: INTRODUCTION

 Save the existing configuration (refer to Saving Configuration on

page 5–20 for details).
 Enter the following command:
ML800# xmodem get type=app
Do you wish to upgrade the image? [Y or N] Y
Please start XModem file transfer now.
Refer to “Saving Configuration” on page 20 for details on the xmodem command.
Once the upgrade is started, the terminal emulation firmware will ask for the installation
file location.
 Indicate the file location to begin the file transfer.
 Make sure the Xmodem protocol is also selected in this file location
dialog window.

In some operating systems it maybe necessary to select the transfer option.

In this case,
 Return to the HyperTerminal window used in step 5.
 Select the Transfer > Send File menu item.
 As shown below, enter the location of the new firmware file.
 Select the Xmodem protocol.

 Select the Send button and to begin the file transfer.

1–24 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 1: INTRODUCTION INTRODUCTION

 Once the file transfer is completed reboot the switch with the
reboot command or by cycling power.
 Login to the switch and use the show version command to verify
and upload the configuration file (if necessary).

1.6.4 Updating through the EnerVista Secure Web Management software

Use the following procedure to install the EnerVista Secure Web Management software.
 Download the latest MultiLink ML800 Managed Edge Switch
firmware from the GE Digital Energy web site.
 Save this file on FTP or TFTP. Ensure the FTP or TFTP path is
configured. If using FTP, record the FTP login name and password.
 Select the switch to upgrade. Ensure you have system administration
privileges available on the switch.
 Open an EnerVista Secure Web Management software session with
the switch by typing in the following URL:
https://<IP address of the switch>
If using FTP, save the configuration before proceeding. GE Digital Energy recommends a
two-step update: first save the configuration to the ftp server, then load the new image
and restart the switch (refer to Saving Configuration on page 5–20 for details on saving the
configuration).
 Load the new firmware as shown below.

As the file is being loaded, the firmware will display the transfer in progress window.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 1–25

INTRODUCTION CHAPTER 1: INTRODUCTION

 Reboot the switch when the transfer is complete.

After reboot, the firmware is ready for use.
 If using TFTP, save the configuration before proceeding.
GE Digital Energy recommends a two-step update:
• first save the configuration to the TFTP server,
• then load the new image and restart the switch (refer to Saving
Configuration on page 5–20 for details on saving the
configuration).
 Load the new firmware as shown below.

As the file is being loaded, the firmware will display the transfer in progress window.

 Reboot the switch when the transfer is complete.

After reboot, the firmware is ready for use.

1–26 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 2: Product Description

Product Description

2.1 Overview
ML800 Managed Edge Switches provide configurability in an entry-level industrial-grade
package. The high performance ML800 base unit comes with four 10/100 copper ports
(which may be either regular or PoE). Up to 3 100Mb fiber ports or up to four more 10/100
copper ports or combinations, may also be configured. In addition, one or two Gb ports
may be configured as 10/100/1000 copper or SFP fiber in any ML800 base unit.
ML800s are ideal for building a switched, hardened Ethernet network infrastructure,
connecting edge devices such as PLCs and IEDs with upstream switches or routers.
Designed for use in industrial applications such as factory floors and control cabinets,
industrial video surveillance systems with PoE, power utility substations, tariffed carrier
field facilities, or transportation and oil and gas, the rugged ML800 handles stressful
workloads (mixes of bursty data traffic and priority streaming traffic) as well as harsh
environmental conditions.
Advanced thermal design techniques with ribbed–surface Aluminum cases for maximum
heat dissipation and a sealed case design enables the unit to operate in harsh Industrial
grade environments efficiently. Heavy duty Ethernet Switch jobs are readily
accommodated with an extended temperature rating of -40˚C to 60˚C by the UL
Component Parts method, or -40˚C to 85˚C by the IEC 60068 Type-Test method. With
options such as several popular DC power input types, AC power and DIN-Rail mounting,
the hardened ML800 is a “multi-purpose” Industrial Ethernet Switch.
The ML800 managed switches also provides a PoE option via power –inside PoE base unit
(ML800P-48VDC) on Slot A and allows the users to utilize up to 4-ports of PoE to support
802.3af Powered devices. See details for PoE base unit in sec 5.2. The Power Sourcing
Equipment (PSE) is fully compatible with Powered Devices (PD) (e.g wireless access points,
IP phones) that comply with the IEEE 802.3af PoE standard. The PoE switch ports have an
auto-sensing algorithm, so that they provide power only to 802.3af, PoE end devices. PoE
is managed by a multi-stage handshake to protect equipment from damage and to

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 2–1

PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION

manage power budgets .The PoE ports will discontinue supplying power when the PoE
powered devices are disconnected. This feature supports the 802.3af PoE PSE standard for
over-current protection, under-current detection, and fault protection.

High performance features include non-blocking unicast traffic speed on all ports and
802.1p QoS Traffic Prioritization. ML800 switches are “plug-and-play” and are designed for
use in connecting edge devices such as PLCs, IEDs and PoE video cameras with upstream
switches and routers where a mix of bursty data traffic and priority streaming traffic for
video surveillance and cell-tower applications are present.
ML800 Managed Edge Switches have heavy-duty aluminum cases and are readily
available with standard Industrial grade 24VDC power. Alternative internal DC power
options are available. Internal AC power and DC power input types may be 12V, 24V, 48V,
125V, 250V and dual source DC input is optional on the ML800.
Alarm Relay contacts provided on each ML800 Switch monitor the hardware and software
through traps, providing a record of any losses of power signals and other user- defined
software events. See Section 3.4.2 for details.

2.1.1 Packet Prioritization, 802.1p QOS

Quality of Service means providing consistent predictable data delivery to users from
datagram paths that go all across a network. As a LAN device, the ML800 can do its part
to prevent any QOS degradation while it is handling Ethernet traffic through its ports and
buffers.
The ML800 switching hardware supports the IEEE 802.1p standard and fulfills its role in
support of QOS, giving packet processing priority to priority tagged packets according to
the 802.1p standard. In addition to hardware support for QOS, the software supports two
priority queues that can be shared across the eight levels of defined packet priorities for
application-specific priority control by the user through software configuration settings.

2.1.2 Frame Buffering and Flow Control

ML800’s are store-and-forward switches. Each frame (or packet) is loaded into the
Switch’s memory and inspected before forwarding can occur. This technique ensures that
all forwarded frames are of a valid length and have the correct CRC, i.e., are good packets.
This eliminates the propagation of bad packets, enabling all of the available bandwidth to
be used for valid information.
While other switching technologies (such as "cut-through" or "express") impose minimal
frame latency, they will also permit bad frames to propagate out to the Ethernet segments
connected. The "cut-through" technique permits collision fragment frames (which are a
result of late collisions) to be forwarded which add to the network traffic. Since there is no
way to filter frames with a bad CRC (the entire frame must be present in order for CRC to
be calculated), the result of indiscriminate cut-through forwarding is greater traffic
congestion, especially at peak activity. Since collisions and bad packets are more likely
when traffic is heavy, the result of store-and-forward operation is that more bandwidth is
available for good packets when the traffic load is greatest.

2–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION

When the ML800 Switch detects that its free buffer queue space is low, the Switch sends
industry standard (full-duplex only) PAUSE packets out to the devices sending it packets to
cause “flow control”. This tells the sending devices to temporarily stop sending traffic,
which allows the traffic to catch-up without dropping packets. Then, normal packet
buffering and processing resumes. This flow-control sequence occurs in a small fraction of
a second and is transparent to an observer.
Another feature implemented in the ML800 Switches is a collision-based flow-control
mechanism (when operating at half-duplex only). When the Switch detects that its free
buffer queue space is low, the Switch prevents more frames from entering by forcing a
collision signal on all receiving half-duplex ports in order to stop incoming traffic.

2.1.3 Managed Network Software for ML800

ML800 comes with licensed network software which allows the user to configure the
ML800 as a Managed Switch and implements security features and other software
enabled features.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 2–3

PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION

2.2 Features and Benefits

• Managed switching for high performance Ethernet LANs
Multilink ML800 Switches provide unicast non-blocking (all ports can run at full speed
at once) performance with standard Managed Network Software. They are typically
used in LAN traffic centers with up to 8 100Mb +2 Gigabit ports for backbone
connections, where managed network services are desired.
• Switching services includes 802.1p QoS packet prioritization
The Multilink ML800 switching hardware supports QoS, giving packet processing
priority to priority tagged packets according to the IEEE 802.1p standard. For port-
and application-specific priorities of data, the QoS software may be configured.
• Fiber Ports Built-In
Multilink ML800 Managed Edge Switches are designed to naturally include fiber ports,
and support mixes of multi-mode, single-mode, 100Mb and 1000Mb speed; full-and
half-duplex; classic Small Form Factor (SFF) and Small Form Pluggable (SFP) fiber
connectors. RJ-45 10/100 ports can also be configured in the mix of port types.
• Relay Contacts for monitoring internal power and user-defined software events
Two Alarm Relay contacts monitor basic operations. One is for hardware, and will
signal loss of power internally. The other is software controlled and will signal user-
defined software events such as a security violation or an Ring-Only Mode fault
condition.
• Vertical mounting for efficient convection cooling, no fans, extended temperature
Mounting brackets for vertical mounting are included. DIN-Rail mounting hardware is
optional. Ethernet signal and power cables attach at the bottom. Two sets of status
LEDs are included, one set viewable at the port connector and one set viewable from
the front.
• All types of power input, 12, 24, 48, 125, 250 V DC and AC
The ML800 can be configured with the user’s choice of DC power supplies: 12V and
24 V for factory floor, 48 V for tariffed carrier field facilities and for PoE-powered
applications such as IP video surveillance, and 125 V or 250 V for substations. An
internal AC power supply may also be chosen, universal AC for use worldwide.
• Heavy-duty design for Industrial Ethernet and extended temperature operation
Fiber ports take more power than copper ports, but the Multilink ML800 design
provides for this with heavy-duty components. The ambient temperature dual-rating
is 60°C per UL methods, and 95°C per IEC type test methods.
• Multilink management software
Managed networks software, combined with a Multilink Switch, provides power and
efficiency in a managed Ethernet platform. A full range of industry-standard software
functions in the Multilink software product enables the versatile Multilink Switches to
perform efficiently in a wide range of managed LAN applications, including redundant
topologies.
• Ring-Only Mode for economical high availability using ring topology.
Ring-Only Mode feature provides reliable fast recovery of a fault in an economical ring
topology combining unmanaged and managed switches.

2–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION

• RSTP-2004 for rings and meshes, fastest fault recovery, interoperability.

RSTP-2004 provides reliable fast recovery from a fault in a redundant LAN, which may
include Multilink switches and routers as well as other vendors industry-standard-
RSTP products. Redundant topologies may include rings, dual-rings, and complex
meshes.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 2–5

PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION

2.3 Applications
ML800 Edge Switches offer high performance, modularity and availability. They provide
the flexibility of 100Mbps fiber and copper ports as well as single or dual Gigabit (1000Mb)
ports, with industry-standard LAN management software. Multilink ML800 Switches are
easily used in a variety of applications including client/server computing, secure VLAN-
performance upgrades to departmental networks, and stream traffic for VOIP and audio/
video applications. They can also be used in a much diversified combination of mixed
media in Industrial floor applications. The performance characteristics of the ML800
Switches enable them to inter-connect a series of subnets (one subnet per ML800 Switch
port) in a LAN traffic center. The subnet connections may be via fiber or twisted pair
cabling, 100Mbps or 10 Mbps speed, and full-or half-duplex.
The mixed-media modular capability is ideal for industrial applications where existing
Ethernet LAN network cabling must be accommodated. The fiber-built-in media capability
is ideal for integrating future-proof fiber cabling into the LAN structure.
Example 1: ML800 Switch for an Industrial Application
Equipped with lots of useful features including hardened enclosures, a wide spread of DC
power supply options, and extended temperature ratings qualifies the ML800 Managed
switch for any Industrial factory-floor, traffic control, transportation system, or power
utility application. The several ML800 software operated features qualifies this managed
switch to operate and perform securely and reliably in all critical applications. The addition
of Ring-Only Mode features allow this Managed switch to provide a very secure highly
available redundant network capability in any ring topology network.
The Managed ML800’s modularity along with the management software features
remarkably handle industrial environments (i.e. where the factory floors are networked
with Ethernet based mixed-media LANs equipped with PLCs, computers for taking
readings and data from Machines, Client/ Server databases, etc. and sending these
important data to the central office data warehouses) very securely and reliably. The DIN-
Rail Mounting options on the Multilink ML800 allow the factory floor’s industrial user to
mount the ML800 securely anywhere on their Network setup.
The option of setting the ports at 10 or 100Mb on copper and 100Mb on fiber media
provide widespread options to the users to mix and match their legacy and advance
network needs. The modularity of the ML800 Managed Edge Switches make them an
attractive choice for use in applications with LAN connections to an organization’s multiple
site offices and factory- floors. The different locations can be easily connected together

2–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION

with the Fiber ports supported by the ML800 Switch. A main NT-server in a secure area
protected from earthquake or fire hazards can be connected to the full duplex Gigabit
Fiber port.

Extended temperature ratings and a variety of options for AC/DC power supplies qualify
this managed ML800 switch for use in non-temperature controlled networks and many
other temperature sensitive critical Industrial applications where above normal room
temperatures occur while the network is in operation. Full-duplex future proof fiber media
can easily connect long distance subnets and provide a stable secure network to all
applications. The SNMP management capability of the ML800 Switch helps create a
database of all the network subnets to easily manage the network.
Example 2: A managed network is needed to provide a redundant ring topology for
maximum redundancy. In a network where any faulty cable, cable disconnection or power
failure can bring the whole thing down, a ring switch can be reconfigured and up and
running in milliseconds. The ring topology of the network consists of high speed LAN
segments supported by 100 Mbps full-duplex future-proof fiber media to provide a secure
long distance LAN connection. The entire network is sharing a higher bandwidth Gigabit-
enabled data-mining server for the vital database located in a separate secured building.
The copper ports are required for multiple subnets inside the power plant to check the
status of other Ethernet units. The entire spread network will be manageable to provide
easy, detectable, uninterrupted support through a viewable SNMP monitor.
The ML800 Managed Edge Switch equipped with a mix of copper and fiber ports provides
an economical and seamless solution to many requirements. The user-configurable
Multilink ML800 provides an extra boost to the network requirements by providing copper/

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 2–7

PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION

fiber media along with the higher bandwidth support of 10/100 and 1000Mb. The user can
utilize the SNMP feature equipped with VLAN, RMON, STP and other standard managed
LAN features to provide a secure and stable network.

The ML800 Managed Fiber with Ring-Only Mode features easily fulfill the redundant
requirement with a secure and fast reconfiguration time for cable breakup when set up in
a ring topology. The Gigabit port option boosts the bandwidth for high speed to support
the peak traffic and minimize congestion.
Example 3: In another application in an industrial environment, a 12 port Nebs compliant,
24VDC managed switch is required to meet the fiber and copper connections to cover the
wider area of video CCTV. The switch must be SNMP enabled and managed to easily
monitor the whole setup.
The managed edge switch easily qualifies for this requirement with the various features
and modularity it has. Loaded with management software, the edge switch provides a very
effective and economical solution for the video -vignette environment.
The security features (e.g. port-security, VLANs, SNMPv3, secure telnet, etc.) also boost the
managed switches to provide a very effective and reliable solution. The modularity feature
to support both copper and fiber at either 10/100/1000Mb speeds easily meets the various
speeds of legacy and future broadband requirements.
In a fast growing secure video environment, the ML800 is a reliable and secure solution.
The modular design of the ML800, provides a wide range of copper/fiber options to meet
requirements. The Gigabit uplink for storage or broadband uplink allows the telecom user
a very effective solution to store their sensitive data securely.

2–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 3: Installation
Installation

3.1 Preparation

3.1.1 Before Installing

Before installing the equipment, it is necessary to take the following precautions:
1. If the equipment is mounted in an enclosed or multiple rack assembly, the
steady-state long-term environmental temperature around the equipment
must be less than or equal to 600C.
2. If the equipment is mounted in an enclosed or multiple rack assembly,
adequate airflow must be maintained for proper and safe operation.
3. If the equipment is mounted in an enclosed or multiple rack system,
placement of the equipment must not overload or load unevenly the rack
system.
4. If the equipment is mounted in an enclosed or multiple rack assembly, verify
the equipment’s power requirements to prevent overloading of the building/s
electrical circuits.
5. If the equipment is mounted in an enclosed or multiple rack assembly verify
that the equipment has a reliable and uncompromised earthing path.

POTENTIAL ELECTRICAL EXPOSURE - The Multilink ML800 must be installed in an

electrical enclosure where any access to live electrical wiring is restricted only to
authorized service personnel.
This section describes installation of the Multilink ML800 Switches, as well as connection of
the various Ethernet media types.

3.1.2 Locating ML800 Switches

For vertical panel mounting and wall mounting, see Section 3.3

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 3–1

INSTALLATION CHAPTER 3: INSTALLATION

For vertical DIN-Rail mounting, see Section 3.3.1

For DC power input data, see Appendix B. For Dual Source, see Appendix C.
The rugged metal case of the ML800 will normally protect it from accidental damage in a
lab or workplace setting. Maintain an open view of the front to visually monitor the status
LEDs. Keep an open area around the unit so that cooling can occur from convection while
the unit is in operation. The ML800 has no fans, so it is silent when in operation. Internal
electronics use the case as a heat sink, so the unit may normally be quite warm to the
touch.

3–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 3: INSTALLATION INSTALLATION

3.2 Connecting Ethernet Media

The ML800 Switches are specifically designed to support standard Ethernet media types
within a single Switch unit. This is accomplished by using a two popular Fiber Connectors
which can be individually selected and configured.
(See Section 4.2 for a description of the Modules)
The various media types supported along with the corresponding IEEE 802.3, 802.3D,
802.3u, 802.3AB and 802.3z standards and connector types are as follows:

Media IEEE Standard Connector

Twisted Pair (CAT 3 or 5) 10BASE-T RJ-45

Twisted Pair (CAT 5) 100BASE-TX RJ-45

Twisted pair (CAT5E or CAT6 1000BASE-T RJ-45

Fiber (Multi-mode) 100BASE-FX MTRJ, LC

Fiber (Single-mode) 100BASE-FX LC

Fiber (Multi-mode) 1000BASE-SX LC (SFP)

Fiber (Multi-mode, Single-mode) 1000BASE-LX LC (SFP)

Fiber (Single-mode) 1000BASE-ZX LC (SFP)

3.2.1 Connecting Twisted Pair (CAT3, CAT5, UTP or STP)

The RJ-45 ports of the ML800 can be connected to the following two media types:
100BASE-TX and 10BASE-T. CAT 5 cables should be used when making 100BASE-TX
connections. When the ports are used as 10BASE-T ports, CAT 3 may be used. In either
case, the maximum distance for unshielded twisted pair cabling is 100 meters (328 ft).

It is recommended that high quality CAT. 5 cable be used whenever possible in order to
Note

provide flexibility in a mixed-speed network, since 10/100 copper switched ports are
NOTE auto-sensing for either 10 and 100Mb/s.
The following procedure describes how to connect a 10BASE-T or 100BASE-TX twisted pair
segment to the RJ-45 port. The procedure is the same for both unshielded and shielded
twisted pair cables.
1. Using standard twisted pair media, insert either end of the cable with an RJ-
45 plug into the RJ-45 connector of the port. Note that, even though the
connector is shielded, either unshielded or shielded cables and wiring may be
used.
2. Connect the other end of the cable to the corresponding device.
3. Use the LINK LED to ensure proper connectivity by noting that the LED will be
illuminated when the unit is powered and proper connection is established.

For Power Substations: In support of the IEEE 1613 Class 2 standard, GE Digital Energy
Note

advises that, for substation applications, the RJ-45 ports are intended for connectivity to
NOTE other communication equipment such as routers or telecommunication multiplexers

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 3–3

INSTALLATION CHAPTER 3: INSTALLATION

installed in close proximity (i.e., less than 2 meters or 6.5ft) to the ML800. It is not
recommended to use these ports in substation applications to interface to field devices
across distances which could produce high (greater than 2500V) levels of ground potential
rise (GPR) during line-to-ground fault conditions. The ML800 passes the 1613specifications
for zero packet loss with fiber ports & with RJ-45 ports used as indicated here.

3.2.2 Connecting Twisted Pair (CAT5e or better, UTP or STP)

The RJ-45 Gigabit ports of the ML800 can be connected to the media types, 1000BASE-T or
CAT 5E or better 100-ohm UTP or shielded twisted pair (STP) balanced cable. The CAT 5E or
better 100-ohm UTP or shielded twisted pair (STP) balanced cable is recommended to use
when making 1000BASE-TX connections. In either case, the max distance for unshielded
twisted pair cabling is 100 meters (328 ft).
The following procedure describes how to connect a 1000BASE-T twisted pair segment to
the RJ-45 port. The procedure is the same for both unshielded and shielded twisted pair
cables.
1. 1000BASE-T connections require that all four pairs or wires be connected.
Insert either end of the cable with an RJ-45 plug into the RJ-45 connector of
the port. Note that, even though the connector is shielded, either unshielded
or shielded cables and wiring may be used.
2. Connect the other end of the cable to the corresponding device
3. Use the LINK LED to ensure proper connectivity by noting that the LED will be
illuminated when the unit is powered and proper connection is established

3.2.3 Connecting Single-Mode Fiber Optic

When using single-mode fiber cable, be sure to use single-mode fiber port connectors.
Single-mode fiber cable has a smaller diameter than multi-mode fiber cable (9/125
microns for single-mode, 50/125 or 62.5/125 microns for multi-mode where xx/xx are the
diameters of the core and the core plus the cladding respectively). Single-mode fiber
allows full bandwidth at longer distances, about 70km with the single-mode LC.

3.2.4 Gigabit SFP (Small Form-factor Pluggable) Transceivers

The small form-factor pluggable (SFP) is a compact optical transceiver used in optical
communications for both telecommunication and data communications applications. Due
to its compact, hot pluggable characteristics, SFPs are becoming a very popular choice for
various applications. The small-chassis ML800 is designed for industry-standard Gb-SFPs
for user selection of the SFP gigabit media type as desired.
All SFPs used in ML800s are compliant with the industry standard Multi-Source Agreement
(MSA) ensuring compatibility with a wide range of networking kit (see Section 1.3 for the
SFP’s available for the ML800).

It is highly recommended to remove the fiber cable first before removing the SFP
transceiver for any reason. Not removing the fiber cable first can damage the fiber cable,
CAUTION
cable connector or optical interfaces. It is advised not to remove and insert a SFP
transceiver frequently as this may shorten its useful life.

Always use an ESD wrist strap while handling the SFP transceivers since the SFP modules
are static sensitive devices.
CAUTION

3–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 3: INSTALLATION INSTALLATION

The copper 1000BASE-T SFP transceiver port supports 1000Mb only. It is recommended to
Note

use a straight-through RJ-45 (4-twisted pair) connection while connecting to any Server/
NOTE workstation. While connecting with any Switch/repeater or other device, it is
recommended to use Crossover RJ-45 (4-twisted pair) category 5 or higher cabling. The
maximum length supported on copper 1000BASE-T is 100m (328 ft.).

3.2.5 Connecting Fiber Optic Cable to SFP Transceivers

1. Before connecting the fiber optic cable, remove the protective dust caps from
the tips of the connectors on the PM. Save these dust caps for future use.
2. Wipe clean the ends of the dual connectors with a soft cloth or lint-free lens
tissue dampened in alcohol. Make certain the connectors are clean before
connecting.

One strand of the duplex fiber optic cable is coded using color bands at regular intervals;
Note

you must use the color-coded strand on the associated ports at each end of the fiber optic
NOTE segment.
3. Find the Transmit (TX) and Receive (RX) markings on the SFP transceiver to
verify the top side of it. Some of the transceiver marks arrow sign for up.
4. Position the SFP transceiver correctly before insertion, and then insert the SFP
transceiver carefully, until the transceiver connector snap into the place in the
socket connector.
5. Connect the Transmit (TX) port on the Multilink PM to the Receive (RX) port of
the remote device. Connect the Receive (RX) port on the PM to the Transmit
(TX) port of the remote device.
The LINK LED on the front of the PM will illuminate and turn Green, when a proper
connection has been established at both ends (and when power is ON in the unit). If LINK is
not lit or OFF after cable connection, the normal cause is improper cable polarity. Swap
the fiber cables at the PM connector and also check the connectivity on the target device
to remedy this situation.
Reconfigure or reboot both of the devices if required.
If connected properly, you can check via software for verifying the validity of SFP Gigabit
ports.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 3–5

INSTALLATION CHAPTER 3: INSTALLATION

3.3 Mechanical Installation

3.3.1 Mounting Dimensions for ML800 with metal brackets

Each ML800 is supplied with metal mounting brackets and screws to mount the unit
securely on a panel or wall. It is recommended to mount the ML800 vertically, as shown on
following page, for proper cooling and long-life reliability. It is also advisable to mount the
unit with space for air movement around the top and the sides, typically a minimum of 1
inch.

The metal brackets supplied, hold the back of the ML800 unit out from the panel or wall
Note

behind it, creating a rear space of about ¼ inch or 1cm. This allows air circulation and
NOTE cooling of the rear part of the case.
For best cooling of the ML800, attach the metal brackets to metal (rather than wood or
plastic). Attaching to metal helps conduct heat away from the ML800 through the metal
brackets and into the metal support structure.

Since the ML800 has special internal thermal techniques (patent pending) to move the
Note

heat generated by the electronic components inside into the case, the case may be quite
NOTE warm to the touch during normal operation.

The unit is mounted using the brackets as shown in the illustration above. The spacing for
Note

the mounting screws into the supporting wall or panel is a rectangle 21.74 x 11.91 cm (8.56
NOTE x 4.69 inches) center-to-center.

FIGURE 3–1: ML800 Mounting Dimensions

The ML800 is designed for use in a “factory floor” industrial environment. It is available with
an optional DIN-Rail bracket to mount it securely in a metal factory floor enclosure,
maintained vertically for proper convection cooling of the unit. The Multilink ML800
requires one DIN-Rail bracket for secure mounting. This may be ordered as Model # DIN-
RAIL-ML800. See a ML800 viewed from the side, at the rear, with model DIN-RAIL-ML800 in
place on the unit.

3–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 3: INSTALLATION INSTALLATION

The DIN Rail bracket is mounted on one of three available positions at the rear of the
ML800 unit. Eight threaded holes are provided on the rear of ML800 for DIN-Rail mounting
purposes. The required four screws are included with the DIN-Rail bracket, and are no.4-
40 X 5/16 PHIL. PAN Head.
To install the ML800 with the DIN-Rail bracket installed, hold the ML800 in the side vertical
position with the bottom out, and with the top moved in toward the DIN-Rail. Position the
DIN bracket over the top of the DIN-Rail. Then, snap the bracket into holding position by
moving the bottom of the ML800 inwards to a vertical position. The DIN-Rail bracket is
heavy duty, and will hold the ML800 securely in position, even with cabling attached to the
unit.
To release the ML800 from the DIN-Rail mounting, press the top of the DIN-Rail bracket
slide DOWN to release the ML800 so that it can be dismounted by pulling the bottom out.
Once the bottom of the ML800 is rotated out, the DIN-Rail bracket is not engaged and the
ML800 can be moved up and out, free of the DIN-Rail mounting.
The DIN-Rail mounting bracket is optional and needs to be ordered as separate items, e.g
Model # DIN-RAIL-ML800.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 3–7

INSTALLATION CHAPTER 3: INSTALLATION

3.4 Electrical Installation

3.4.1 Powering the Multilink ML800 Managed Edge Switch

The DC internal power supply supports installation environments where the DC voltage is
from 10 to 300 volts depending on the model selected. The power consumption will range
from about 15 up to 20 watts, depending on the port quantity and types in the
configuration.. When connecting the Ethernet cabling, there is no need to power down the
unit. Individual cable segments can be connected or disconnected without concern for
power-related problems or damage to the unit.
Power input options are available to suit the ML800 Switches to special high-availability
communications and/or heavy industrial-grade applications, including:
• 12VDC, -48VDC, 24VDC, 125VDC and 250VDC with single DC input,
• 12VDC, -48VDC, 24VDC, 125VDC and 250VDC with dual-source DC input
• AC input with internal power supply
(See Section 1.2 for Ordering Information.)

3.4.2 Alarm Contacts for monitoring internal power, and Software Traps
The Alarm Contacts feature, standard on ML800’s, provides two Form C Normally Closed
(NC) contacts to which the user can attach two sets of status monitoring wires at the green
terminal block. When this option is present, the terminal block for Alarm Contacts is part of
the Power Input panel in the ML800 case. The DC power input connection is in the same
panel.
The first NC Alarm Contact (top position, switch vertically mounted) is a “Software Alarm”,
operated by user settings in the software. The user can disable the Software Alarm feature
with a software configuration command if desired. When the Software Alarm is enabled,
the Form C Normally Closed (NC) contact is held close during normal software operation. A
user-defined software malfunction, such as an SNMP Trap or a Software Security violation
or an Ring-Only Mode Fault, causes the contact to open and thus triggers an alarm in the
user’s monitoring system
The second NC Alarm Contact is held closed when there is power on the main board inside
of the Switch. This provides a “Hardware Alarm” because the NC contacts will open when
internal power is lost, either from an external power down condition or by the failure of the
power supply inside of the Switch.
Useful information about Alarm contacts:
1. There are four terminal blocks (1,2,3,4) provided next to the DC power supply
2. The left two pins (1,2) are hardware operated
3. The right two pins (3,4) are software operated
4. These are both NC (normally closed) relays
5. The switch’s software operation needs to be enabled and set to get the Alarm traps.
For detailed information about the Software Alarm and software control of SNMP
alarm traps, please reference Chapter 16.

3–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 3: INSTALLATION INSTALLATION

The Alarm Contacts are on the front left area (next to the DC power source) of the Multilink
ML800 unit and are green in color as shown in the picture.

FIGURE 3–2: Alarm Contacts: 1 & 2 (left) hardware operated; 3 & 4 (right) software operated

3.4.3 Connecting the Console Terminal to Multilink ML800

Use a (DB-9) “null modem” cable to connect the Multilink ML800 Console Port (the RS-232
port on the ML800 Switch) to your PC, so that your PC becomes the ML800 Console
Terminal.

The DB-9 cable is not included with the ML800 package.

Note

NOTE 3.4.3.1 RS-232 (DB-9) Console port (Serial port) pin assignments

FIGURE 3–3: DB9 Console Port Connector

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 3–9

INSTALLATION CHAPTER 3: INSTALLATION

Pin Signal Description

1 DCD Data Carrier Detect (Not Used)

2 RXD Receive Data

3 TXD Transmit Data

4 OPEN Not Used

5 GND Signal Ground

6 OPEN Not Used

7 RTS Request to Send

8 CTS Clear to Send

9 OPEN Not Used

The above provided information enables a managed station (a PC or Console terminal) to

connect directly to the switch using a straight through cable.

To use the Console port to configure the managed switch, a serial (Null-modem) female to
Note

female cable is required to communicate properly. The Null-Modem (DB-9) cable is optional
NOTE and can be ordered from the factory, along with the unit as:
CONSOLE CBL for serial port
CONSOLE USB for USB port

For Power Substations: In support of the IEEE 1613 Class 2 standard, GE Digital Energy
Note

advises that, for substation applications, the serial (DB-9) console ports are intended for
NOTE temporary connectivity to other equipment such as PCs. Since the console port
connection is temporary, it is excluded from IEEE 1613 packet-loss testing per the 1613
standard-defined test procedure.

3–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 4: Operation
Operation

4.1 Functionality

4.1.1 Switching Functionality

A Multilink ML800 provides switched connectivity at Ethernet wire-speed among all of its
ports. The Multilink ML800 supports10/100Mbs for copper media and 100Mb separate
traffic domains for fiber ports to maximize bandwidth utilization and network
performance. All ports can communicate to all other ports in a Multilink ML800, but local
traffic on a port will not consume any of the bandwidth on any other port.
The Multilink ML800 units are plug-and-play devices. There is no software configuring
necessary to be done for basic operation at installation or for maintenance. The only
hardware configuration settings are user options for an UP-LINK Switch (resides inside the
unit) on the ML8004-RJ-45. There is an optional Half / Full duplex mode and 10Mbps or
100Mbps selection for the switched ports which must be configured through ML800
software per unit as per the requirement. The internal functions of both are described
below.

4.1.1.1 Filtering and Forwarding

Each time a packet arrives on one of the switched ports, the decision is taken to either filter
or to forward the packet. Packets whose source and destination addresses are on the
same port segment will be filtered, constraining them to that one port and relieving the
rest of the network from having to process them. A packet whose destination address is on
another port segment will be forwarded to the appropriate port, and will not be sent to the
other ports where it is not needed. Traffic needed for maintaining the un-interrupted
operation of the network (such as occasional multi-cast packets) is forwarded to all ports.
The Multilink ML800 Switches operate in the store-and-forward switching mode, which
eliminates bad packets and enables peak performance to be achieved when there is
heavy traffic on the network.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 4–1

OPERATION CHAPTER 4: OPERATION

4.1.1.2 Address Learning

All Multilink ML800 units have address table capacities of 4K node addresses suitable for
use in larger networks. They are self-learning, so as nodes are added, removed or moved
from one segment to another, the ML800 Switch automatically keeps up with node
locations.
An address-aging algorithm causes least-used addresses to fall out in favor for frequently-
used addresses. To reset the address buffer, cycle power down-and-up.

4.1.2 Auto-Cross (MDIX) and Auto-negotiation for RJ-45 ports

The RJ-45 ports independently support auto-cross (MDI or MDIX) in auto-negotiation mode
and will work properly with all the other connected devices with RJ-45 ports whether they
support Auto-negotiation (e.g 10 Mb Hub, media converter) or fixed mode at 10 Mb or
100Mb Half/Full Duplex(managed switch) or not. No cross-over cable is required while
using the ML800’s copper port to other devices. Operation is according to the IEEE 802.3u
standard.
The Managed ML800’s Fast Ethernet copper ports can be set for either fixed 100Mb speed
or for 10/100 F/H N-way auto-negotiation per the IEEE802.3u standard. The selection is
made via MNS software. The factory default setting is for auto-negotiation. At 10Mb or
100Mb-fixed speed, the user may select half- or full-duplex mode by management
software for each RJ-45 port separately.
One frequently-used application for the Managed Multilink ML800 Switch copper ports is to
connect one of them using a fiber media converter to another Switch in the network
backbone, or to some other remote 100Mb device. In this case, it is desirable to operate
the fiber link at 100Mb speed, and at either half- or full duplex mode depending on the
capabilities of the remote device. Standard commercially available Fast Ethernet media
converters mostly do not support auto-negotiation properly, and require that the switched
port to which they are connected be at the 100Mb fixed speed. Attachments to a 10/100
auto-negotiation port typically will not work properly. The ML800 Switch’s RJ-45 ports
handle this situation by configuring the ports as per desired through management
software port settings and can check the port status of each port after the change.
When Multilink ML800 RJ-45 copper ports are set for auto-negotiation and are connected
to another auto-negotiating device, there are 4 different speed and F/H modes possible
depending on what the other device supports. These are: (1) 100Mb full-duplex, (2) 100Mb
half-duplex, (3) 10 Mb full-duplex and (4) 10 Mb half-duplex.
The auto-negotiation logic will attempt to operate in descending order and will normally
arrive at the highest order mode that both devices can support at that time. (Since auto-
negotiation is potentially an externally controlled process, the original “highest order
mode” result can change at any time depending on network changes that may occur). If
the device at the other end is not an auto-negotiating device, the ML800’s RJ-45 ports will
try to detect its idle signal to determine 10 or 100 speed, and will default to half-duplex at
that speed per the IEEE standard.

4.1.2.1 General information

Auto-negotiation per-port for 802.3u-compliant switches occurs when:

• the devices at both ends of the cable are capable of operation at either 10Mb or
100Mb speed and/or in full- or half-duplex mode, and can send/receive auto-
negotiation pulses, and . . .
• the second of the two connected devices is powered up*, i.e., when LINK is
established for a port, or

4–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 4: OPERATION OPERATION

• the LINK is re-established on a port after being lost temporarily.

Some NIC cards only auto-negotiate when the computer system that they are in is
Note

powered. These are exceptions to the “negotiate at LINK – enabled” rule above, but may
NOTE be occasionally encountered.
When operating in 100Mb half-duplex mode, cable distances and hop-counts may be
limited within that collision domain. The Path Delay Value (PDV) bit-times must account for
all devices and cable lengths within that domain. For Multilink ML800 Fast Ethernet
switched ports operating at 100Mb half-duplex, the bit time delay is 50BT.

4.1.3 Flow-control, IEEE 802.3x standard

Multilink ML800 Switches incorporate a flow-control mechanism for Full-Duplex mode. The
purpose of flow-control is to reduce the risk of data loss if a long burst of activity causes
the switch to save frames until its buffer memory is full. This is most likely to occur when
data is moving from a 100 Mb port to a 10 Mb port and the 10 Mb port is unable to keep up.
It can also occur when multiple 100Mb ports are attempting to transmit to one 100 Mb
port, and in other protracted heavy traffic situations.
Multilink ML800 Switches implement the 802.3x flow control (non-blocking) on Full-Duplex
ports, which provides for a “PAUSE” packet to be transmitted to the sender when the
packet buffer is nearly filled and there is danger of lost packets. The transmitting device is
commanded to stop transmitting into the ML800 Switch port for sufficient time to let the
Switch reduce the buffer space used. When the available free-buffer queue increases, the
Switch will send a “RESUME" packet to tell the transmitter to start sending the packets. Of
course, the transmitting device must also support the 802.3x flow control standard in order
to communicate properly during normal operation.

When in Half-Duplex mode, the ML800 Switch implements a back-pressure algorithm on

Note

10/100 Mb ports for flow control. That is, the switch prevents frames from entering the
NOTE device by forcing a collision indication on the half-duplex ports that are receiving. This
temporary “collision” delay allows the available buffer space to improve as the switch
catches up with the traffic flow.

4.1.4 Power Budget Calculations for ML800 Modules with Fiber Media
Receiver Sensitivity and Transmitter Power are the parameters necessary to compute the
power budget. To calculate the power budget of different fiber media installations using
Multilink products, the following equations should be used:
OPB (Optical Power Budget) = PT(min) - PR(min)
where PT = Transmitter Output Power, and PR = Receiver Sensitivity
Worst case OPB = OPB - 1dB(for LED aging) - 1dB(for insertion loss)
Worst case distance = {Worst case OPB, in dB} / [Cable Loss, in dB/Km]
where the “Cable Loss” for 62.5/125 and 50/125mm (M.m) is 2.8 dB/km,
and the “Cable Loss” for 100/140 (Multi-mode) is 3.3 dB/km,
and the “Cable Loss” for 9/125 (Single-mode) is 0.5 dB/km
and the “Cable Loss” for 9/125 (Single-mode) is 0.4 dB/km (LX25)
and the “Cable Loss” for 9/125 (Single-mode) is 0.25 dB/km (ZX40)
and the “Cable Loss” for 9/125 (Single-mode) is 0.2 dB/km (ZX70)

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 4–3

OPERATION CHAPTER 4: OPERATION

4.2 Multilink ML800 Managed Edge Switch Port Modules

4.2.1 ML800 Modules

An important feature of the Multilink ML800 is the use of Port Modules for flexible mixed-
media connectivity to RJ-45 copper and various fiber media. The first four ports (1,2,3 & 4)
of the Multilink ML800 Switches are fixed RJ-45 copper ports with dual-speed 10/100 Mbps
auto-negotiating capability. Additionally the switch can accept up to two Port Modules to
provide the user with up to 6 additional ports (10 total) providing a wide selection of
Ethernet copper and fiber media connections with 10, 100 and 1000Mbps capability and
up to 70 km.

The ML800 Port modules are not identical to the port modules used in other Multilink
Note

products such as the ML2400 and ML810. For information about other Multilink products,
NOTE please see the applicable manual. For a list of ML800 Port Modules, refer to Section 1.2
Order Codes.
Each ML800 Port Module (PM) is individually described in the following sections.

4.2.1.1 ML800 Module LED designations

RJ45 (Standard)
1 = ON (100 Mb), OFF (10 Mb)
2 = ON (Link)
3 = ON (Full Duplex), OFF (Half Duplex)
4 = BLINKING (Activity)

RJ45 (PoE)
1 = ON (100 Mb), OFF (10 Mb)
2 = ON (Link), BLINKING (Link/Activity)
3 = ON (Full Duplex), OFF (Half Duplex)
4 = ON (PoE device detected)

4–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 4: OPERATION OPERATION

MTRJ (Fiber)
1 = ON (Link)
2 = BLINKING (Activity)

LC (Fiber)
1 = ON (Link)
2 = BLINKING (Activity)

Gigabit (Copper / Fiber)

1 = ON (Full Dx), OFF (Half Dx)
2 = ON (Link)
3 = BLINKING (Activity)
4 = ON (1000 Mb) Not used for Fiber
5 = ON (100 Mb) Not used for Fiber
6 = ON (10 Mb) Not used for Fiber

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 4–5

OPERATION CHAPTER 4: OPERATION

4.2.2 ML800 Base Unit LED designations

4–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 4: OPERATION OPERATION

4.2.2.1 C1 Module: 4 x 10/100Mb RJ45 (Slot C)

The C1 Module 4-port Copper module, provides four 10/100Mb switched RJ-45 ports. The
10/100 Mb switched ports normally (as a default setting) are independently N-way auto-
negotiating and auto-crossover (MDIX) for operation at 10 or 100 Mb speed in full- or half-
duplex mode. (i.e., each independently selects a mode and speed to match the device at
the other end of the twisted pair cable).
For auto-negotiation and MDIX details, see Section 4.1.2.
On the model C1 module, there are four LEDs for each port, two integrated into the
connector, and two below the connector. The LK (Link) LED indicates “ready for operation”
on that port when lit. The blinking ACT (Activity) LED indicates receiving Activity on that port
when lit. The 10/100 LED indicates operation at 100 Mb speed when ON and at 10 Mb
speed when OFF (when auto-negotiation is not disabled). The FDX/HDX LED is ON to
indicate full-duplex operation and OFF to indicate the half-duplex mode. A twisted pair
cable must be connected into an RJ-45 port and the Link (LK) indicator for that port must
be ON (indicating there is a powered-up device at the other end of the cable) in order for a
LK LED to provide valid indications of operating conditions on that port.
Using the management software, the user may disable auto-negotiation and fix the
desired operation of each RJ-45 port. The user may select 10Mb or 100Mb speed and full-
or half-duplex mode per-port as per user requirements.

For Power Substations: In support of the IEEE 1613 Class 2 standard, GE Digital Energy
Note

advises that, for substation applications, the RJ-45 ports are intended for connectivity to
NOTE other communication equipment such as routers or telecommunication multiplexers
installed in close proximity (i.e., less than 2 meters or 6.5 ft) to the ML800. It is not
recommended to use these ports in substation applications to interface to field devices
across distances which could produce high (greater than 2500 V ) levels of ground
potential rise (GPR) during line-to-ground fault conditions. The ML800 passes the 1613
specifications for zero packet loss with fiber ports and with RJ-45 ports used as indicated
here.

4.2.2.2 CB Module: 1 x MTRJ / 3 x RJ45 (Slot C)

The CB Module, 4-port Fiber / Copper module, provides one 100 Mb Multimode MTRJ Fiber
port and three 10/100 Mb switched RJ-45 ports.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 4–7

OPERATION CHAPTER 4: OPERATION

The CB Module fiber port is a Small Form Factor (SFF) MTRJ Multimode connector. The
MTRJ’s small size and ease of connection make it a good choice for 100Mbps “fiber-to-the-
desktop” Ethernet connectivity. When installed in a Multilink ML800 Series Switch, it
supports fiber optic cable distances up to the IEEE-standard 100 Mbps distance limits, i.e.,
typically 2 km at full-duplex and 412 m at half-duplex.
Each port has an Activity (ACT) LED indicating packets being received and a Link (LK) LED
that indicates proper connectivity with the remote device when lit.
The CB Module copper ports support Ethernet twisted pair segments of any standard
length. It is equipped with a three-port RJ-45 connector, and offers 10/100 full / half-duplex
auto-negotiating capability on each port. The RJ-45 connector is shielded to minimize
emissions and will allow both unshielded twisted pair (UTP) and shielded twisted pair (STP)
cable connections. When installed in a Multilink ML800 Series Managed Switch, the copper
ports support the standard distance of 100 m on each port.

4.2.2.3 C3 Module: 2 x MTRJ / 2 x RJ45 (Slot C)

The C3 Module, 4-port Fiber / Copper module, provides two 100Mb Multimode MTRJ Fiber
ports and two 10/100 Mb switched RJ-45 ports.

4.2.2.4 CC Module: 3 x MTRJ / 1 x RJ45 (Slot A, Slot C)

The CC Module, 4-port Fiber / Copper module provides three 100Mb Multimode MTRJ Fiber
ports and one 10/100Mb switched RJ-45 port. This module option occupies parts of Slot
“A” and Slot “C”.

4.2.2.5 CD Module: 1 x LC / 3 x RJ45 (Slot C)

4–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 4: OPERATION OPERATION

The CD Module, 4-port Fiber / Copper module provides one 100Mb Multimode LC Fiber port
and three 10/100 Mb switched RJ-45 ports.
The CD Module fiber port is a Small Form Factor (SFF) LC Multimode connector used
primarily in 100 Mbps fiber-to-the-desktop links. When installed in a Multilink ML800 Series
Switch, it supports fiber optic cable distances up to the IEEE-standard 100 Mbps distance
limits, i.e., typically 2 km at full-duplex and 412 m at half-duplex.
The compact size of the LC Connector reduces the size of wiring panels in wiring closets
while providing the advantage of “future-proof” fiber optic technology.
The cable end is a “plug-in” connector with both fiber strands terminated in one housing
that cannot be improperly inserted. Each port has an Activity (ACT) LED indicating packets
being received and a Link (LK) LED indicating proper connectivity with the remote device
when lit.
The CD Module copper ports support Ethernet twisted pair segments of any standard
length. It is equipped with a three-port RJ-45 connector, and offers 10/100 full / half-duplex
auto-negotiating capability on each port. The RJ-45 connector is shielded to minimize
emissions and will allow both unshielded twisted pair (UTP) and shielded twisted pair (STP)
cable connections. When installed in a Multilink ML800 Series Managed Switch, the copper
ports support the standard distance of 100 m on each port.

4.2.2.6 C4 Module: 2 x LC / 2 x RJ45 (Slot C)

The C4 Module, 4-port Fiber / Copper module provides two 100Mb Multimode LC Fiber
ports and two 10/100Mb switched RJ-45 ports. (See Section 4.2.2.5 for more information.)

4.2.2.7 CE Module: 3 x LC / 1 x RJ45 (Slot A, Slot C)

The CE Module, 4-port Fiber / Copper module provides three 100 Mb Multimode LC Fiber
ports and one 10/100 Mb switched RJ-45 ports. This module option occupies parts of Slot
“A” and Slot “C”. (See Section 4.2.2.5 for more information.)

4.2.2.8 C5, CF, CG: LC Singlemode (15km) / RJ45 Module

The C5, CF, CG, 4-port Fiber / Copper modules provide 100Mb Singlemode LC Fiber ports,
supporting distances up to 15 km , and 10/100 Mb switched RJ45 ports. These modules
provide the same functions as the Multimode versions (see Sections 4.2.2.5 through 4.2.2.7
for more detail and panel configurations).

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 4–9

OPERATION CHAPTER 4: OPERATION

4.2.2.9 CH, CI, CJ: LC Singlemode (40km) / RJ45 Module

The CH, CI, CJ, 4-port Fiber / Copper modules provide 100Mb Singlemode LC Fiber ports,
supporting distances up to 40km , and 10/100 Mb switched RJ45 ports. These modules
provide the same functions as the Multimode versions (see Sections 4.2.2.5 through 4.2.2.7
for more detail and panel configurations).

4.2.2.10 Gigabit RJ45 Copper ports (Slot D)

The H7, 2-port Copper Gigabit module provides two fixed 10/100/1000 Mb RJ-45 ports.
Note

The Multilink ML800 offers a Gigabit option with multiple choices of Copper 10/100/
NOTE
1000 Mbps or Gigabit SFP Fiber transceivers for the modular slot. Up to two Gigabit ports
(maximum) can be configured in Slot D only.
There are six LEDs provided for each Gigabit port. Each Copper Gigabit port has LEDs that
indicate FH (Full or Half Duplex), LK (Link), ACT (Activity) and 10/100/1000 Mbps speed (set
to AUTO by default).

The HK, 1-port Copper Gigabit module provides one fixed 10/100/1000 Mb RJ-45 port.
Note

NOTE 4.2.2.11 Gigabit SFP Fiber ports (Slot D)

The H1, H2, H3, H4, H5, H6, 2-port Fiber Gigabit module provides two SFP open
Note

transceiver locations that can operate at 10/100/1000 Mbps speeds.

NOTE
Transceivers are available with both multi-mode 850 nm (550 m), 1310 nm (3 km), single-
mode 1310 nm (10 km and 25 km) and single-mode 1550 nm (40 km and 70 km) fiber
options.

4–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 4: OPERATION OPERATION

(See the Order Codes section of this manual for part numbers)
The 1000 Mb Gigabit SFP fiber-port modules on the Multilink ML800 are normally set
(factory default) to operate at AUTO mode for best fiber distance and performance.
LEDs are configured the same as the copper gigabit option. (See Section 4.2.2.10 above)

The HE, HF, HG, HH, HI, HJ, 1-port Fiber Gigabit module provides one SFP open
Note

transceiver location that can operate at 10/100/1000 Mbps speeds.

NOTE

4.2.3 ML800-48PS, Base Unit w/PoE Power-pass-through

The ML800 is available with the option of having PoE capabilities on the four fixed RJ45
ports in the base unit (ports 1, 2, 3 and 4).
The PoE (Power-over-Ethernet) RJ-45 ports are similar to regular RJ-45 ports, except they
have the capability of providing power on each port to power up attached PD devices, per
the IEEE802.3af PoE standard. The power-pass-through PoE ports are dependent upon the
-48VDC input power to supply the PD power for these RJ-45 (10/100) ports. Each port
supplies up to 15 watts to power attached PoE PD devices.
The LEDs on the PoE ports are slightly different compared to regular (non-PoE) RJ-45 ports.
When the PoE port is in use, the PoE LED is ON when connected properly to an IEEE 803.af
compliant PD device on that port. When non-PoE devices are connected, the PoE LED is
OFF. Operation of Ethernet data traffic is not affected by PoE. LINK and ACTIVITY LEDS are
combined on the PoE modules into one LED that is marked as LINK/ACT.
PoE LEDs Summary
• For PoE devices, each RJ-45 PoE port supports only 802.3af complaint devices. The
PoE LED is ON when the attached PD is drawing power from the port. The power is
supplied on the data pairs, per IEEE802.3af PoE standard.
• For non-PoE devices connected, the PoE port will act as a normal RJ-45 port and
the PoE LED is OFF. No power is sent out from the port.
• The PoE ports in Multilink 6K’s with 48 V DC power input act as a pass-through, so
the 48 V DC power input source to the Multilink ML800 must be strong enough to
provide power to the Multilink switch and to all 4-RJ-45 ports with PD devices
connected (up to 15 watts per PoE port).
• In the case where the 48 V DC power in not internally connected to the PoE port
pins and no power is coming to the PoE ports for some reason, all the PoE port
LEDs are ON simultaneously to indicate a trouble condition. The ports will still
operate properly for data traffic to non-PoE devices.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 4–11

OPERATION CHAPTER 4: OPERATION

4.3 Troubleshooting
All Multilink Ethernet products are designed to provide reliability and consistently high
performance in all network environments. The installation of a Multilink ML800 Switch is a
straight forward procedure. The operation is also straightforward and is discussed in
Section 4.1.
Should problems develop during installation or operation, this section is intended to help
locate, identify and correct these types of problems. Please follow the suggestions listed
below prior to contacting your supplier. However, if you are unsure of the procedures
described in this section or if the Multilink ML800 Switch is not performing as expected, do
not attempt to repair the unit; instead contact your supplier for assistance or contact GE
Digital Energy Customer Support.

4.3.1 Before Calling for Assistance

1. If difficulty is encountered when installing or operating the unit, refer back to
the Installation Section of the applicable chapter of this manual. Also check to
make sure that the various components of the network are interoperable.
2. Check the cables and connectors to ensure that they have been properly
connected and the cables/wires have not been crimped or in some way
impaired during installation. (About 90% of network downtime can be
attributed to wiring and connector problems.)
3. Make sure that DC power is properly attached to each Multilink ML800 Switch
unit. Use the PWR LEDs to verify each unit is receiving power.
4. If the problem is isolated to a network device other than the Multilink ML800
Switch product, it is recommended that the problem device be replaced with a
known good device. Verify whether or not the problem is corrected. If not, go
to Step 5 below. If the problem is corrected, the Multilink ML800 Switch and its
associated cables are functioning properly.
5. If the problem continues after completing Step 4 above, contact your supplier
of the Multilink ML800 Switch unit or if unknown, contact GE Digital Energy,
Inc. by fax, phone or email for assistance.

4–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 5: IP Addressing
IP Addressing

5.1 IP Address and System Information

5.1.1 Overview
It is assumed that the user has familiarity with IP addresses, classes of IP addresses and
related netmask schemas (for example, class A, B, and C addressing).
Without an IP address, the switch operates as a standalone Layer 2 switch. Without an IP
address, you cannot:
• Use the web interface to manage the switch
• Use telnet to access the CLI
• Use any SNMP Network Management software to manage the switch
• Use NTP protocol or an NTP server to synchronize the time on the switch
• Use TFTP or FTP to download the configurations or upload software updates
• Run ping tests to test connectivity
To set the IP address, please refer to section 1.4.6: Setting the IP Parameters. Once the IP
address is set, the CLI can be accessed via telnet as well as the console interface. From
now on, all commands discussed are accessible from the command line interface,
irrespective of access methods (i.e. serial port or in band using telnet).
To verify the IP address settings using the command line interface, the show ipconfig
command can be used as follows:
ML800> show ipconfig
IP Address: 3.94.247.41
Subnet Mask: 255.255.252.0
Default Gateway: 3.94.244.1
ML800>
To verify the IP address using the EnerVista Secure Web Management software,
 Select the Administration > System menu item to view.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–1

IP ADDRESSING CHAPTER 5: IP ADDRESSING

 Edit the IP address information.

Besides manually assigning IP addresses, there are other means to assign an IP address
automatically. The two most common procedures are using DHCP and bootp.

5–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

5.2 Importance of an IP Address

5.2.1 DHCP and bootp

DHCP is commonly used for setting up addresses for computers, users and other user
devices on the network. bootp is the older cousin of DHCP and is used for setting up IP
addresses of networking devices such as switches, routers, VoIP phones and more. Both of
them can work independent of each other. Both of them are widely used in the industry. It's
best to check with your network administrator as to what protocol to use and what the
related parameters are. DHCP and bootp require respective services on the network. DHCP
and bootp can automatically assign an IP address. It is assumed that the reader knows
how to setup the necessary bootp parameters (usually specified on Linux/UNIX systems in
the /etc/boopttab directory).

5.2.2 bootp Database

Bootp keeps a record of systems supported in a database - a simple text file. On most
systems, the bootp service is not started as a default and has to be enabled. A sample
entry by which the bootp software will look up the database and update the IP address
and subnet mask of the switch would be as follows:
ML800:\
ht=ether:\
ha=002006250065:\
ip=3.94.247.41:\
sm=255.255.252.0:\
gw=3.94.244.1:\
hn:\
vm=rfc1048
where:
• ML800 is a user-defined symbolic name for the switch.

• ht is the hardware type. For the MultiLink family of switches, set this to ether (for
Ethernet). This tag must precede the ha tag.
• ha is the hardware address. Use the switch's 12-digit MAC address.
• ip is the IP address to be assigned to the switch.
• sm is the subnet mask of the subnet in which the switch is installed.
Each switch should have a unique name and MAC address specified in the bootptab table
entry

5.2.3 Configuring DHCP/bootp/Manual/AUTO

By default, the switch is configured for auto IP configuration. DHCP/bootp/manual can be
enabled with the command line interface by using the set bootmode command with the
following syntax:
set bootmode=<dhcp|bootp|manual|auto> bootimg=<enable|disable>
bootcfg=<enable|disable>
The bootimg argument is only valid with the bootp type. This option allows the switch to
load the image file from the bootp server. This is useful when a new switch is placed on a
network and the IT policies are set to load a specific image which is supported and tested
by IT personnel.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–3

IP ADDRESSING CHAPTER 5: IP ADDRESSING

Likewise, the bootcfg argument is valid only with the bootp type. This option allows the
switch to load the configuration file from the bootp server. This is useful when a new
switch is put on a network and the specific configurations are loaded from a centralized
bootp server
The following example changes the boot mode of the switch:
ML800# set bootmode type=bootp bootimg=enable bootcfg=disable
Network application image download is enabled.
Network application config download is disabled.
Save Configuration and Restart System
ML800#
Alternatively, the DHCP/bootp/manual can be enabled through the EnerVista Secure Web
Management software as shown below.
 Select the Administration > System menu item.
 Click Edit.

 Alternatively, select items in the Administration > Set menu to

individually modify the boot mode, date and time, log size, etc.

5–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

 After the changes are completed for each section, click OK to

register the changes.
Note that if the IP address is changed, the http session has to be restarted with the new IP
address.

5.2.4 Using Telnet

The telnet client is enabled on the ML800. The ML800 supports five simultaneous sessions
on a switch: four telnet sessions and one console session. This allows many users to view,
discuss, or edit changes to the ML800. This is also useful when two remote users want to
view the switch settings. The telnet client can be disabled through the command line
interface by using the telnet disable command with the following syntax:
telnet <enable|disable>
Telnet can also be disabled for specific users with the useraccess command. Refer to
section 1.4.8: User Management, for details.
Multiple telnet sessions started from the CLI interface or the command line are serviced by
the ML800 in a round-robin fashion (that is, one session after another). If one telnet session
started from an ML800 is downloading a file, the other windows will not be serviced until
the file transfer is completed.
The following example changes the telnet access. In this case, the enable command was
repeated without any effect to the switch.
ML800# configure access
ML800(access)## telnet enable
Access to Telnet already enabled
ML800(access)## exit
ML800#

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–5

IP ADDRESSING CHAPTER 5: IP ADDRESSING

The show console command can show the status of the telnet client as well as other
console parameters. The following example reviews the console parameters with the show
console command. Note that telnet is enabled.
ML800# show console
Console/Serial Link
Inbound Telnet Enabled: Yes
Outbound Telnet Enabled: Yes
Web Console Enabled: Yes
SNMP Enabled: Yes
Terminal Type: VT100
Screen Refresh Interval (sec): 3
Baud Rate: 38400
Flow Control: None
Session Inactivity Time (min): 10
ML800#
Users can telnet to a remote host from the MultiLink family of switches using the following
syntax.
telnet <ipaddress> [port=<port number>]
The default port for telnet is 23.
To start a telnet session through the EnerVista Secure Web Management software,
 Select the Administration > Telnet menu item.

The default port for telnet is 23.

The ML800 will time out an idle telnet session. It may be useful to see who is currently
connected to the switch. It may also be useful for a person to remotely terminate a telnet
session. To facilitate this, the ML800 supports the following two commands:
show session
kill session id=<session>

5–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

For example:
ML800# user
ML800(user)## useraccess user=peter service=telnet enable
Telnet Access Enabled.
ML800(user)## exit
ML800# show session
Current Sessions:
SL# Sessn Id Connection User Name User Mode
1 1 163.10.10.14 manager Manager
2 2 163.11.11.1 peter Manager
3 3 163.12.12.16 operator Operator
ML800# kill session id=3
Session Terminated
ML800#
In the above example, the user with username “peter” is given telnet access. Then multiple
users telnet into the switch. This is shown using the show session command. The user
operator session is then terminated using the kill session command.

A maximum of four simultaneous telnet sessions are allowed at any time on the switch.
Note

The commands in these telnet windows are executed in a round robin fashion; that is, if
one window takes a long time to finish a command, the other windows may encounter a
delay before the command is completed. For example, if one window is executing a file
download, the other windows will not be able to execute the command before the file
transfer is completed. As well, if a outbound telnet session is started from the switch
(through a telnet window) then other windows will not be able to execute a command until
the telnet session is completed.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–7

IP ADDRESSING CHAPTER 5: IP ADDRESSING

5.3 Setting Parameters

5.3.1 Setting Serial Port Parameters

To be compliant with IT or other policies the console parameters can be changed from the
CLI interface. This is best done by setting the IP address and then telnet over to the switch.
Once connected using telnet, the serial parameters can be changed. If you are using the
serial port, remember to set the VT-100 emulation software properties to match the new
settings.
The serial port parameters are modified using the set serial command with the
following syntax:
set serial [baud=<rate>] [data=<5|6|7|8>] [parity=<none|odd|even>] [stop=<1|1.5|2>]
[flowctrl=<none|xonxoff>]
Where <rate> = standard supported baud rates.

Changing these parameters through the serial port will cause loss of connectivity. The
Note

terminal software parameters (e.g. HyperTerminal) will also have to be changed to match
NOTE the new settings.
To see the current settings of the serial port, use the show serial command to query the
serial port settings as illustrated below.
ML800# show serial
Baud Rate: 38400
Data: 8
Parity: No Parity
Stop: 1
Flow Control: None

5.3.2 System Parameters

The system parameters can be queried and changed. To query the system parameters,
two commands are frequently used: show sysconfig and show setup. Usage for both
commands is illustrated below.
The following example lists system parameters using the show setup command. Most
parameters here cannot be changed.
ML800# show setup
Version: ML800 build 3.3.0 March 19 2009 14:22:43
MAC Address: 00:20:06:27:0a:e0
IP Address: 3.94.247.41
Subnet Mask: 255.255.252.0
Gateway Address: 3.94.244.1
CLI Mode: Manager
System Name: ML800
System Description: 12 Port Modular Ethernet Switch

5–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

System Contact: multilin.tech@ge.com

System Location: Markham, Ontario
System ObjectId: 1.3.6.1.4.1.13248.12.7
ML800#
The following example lists system parameters using the show sysconfig command.
Most parameters here can be changed.
ML800# show sysconfig
System Name: ML800
System Contact: multilin.tech@ge.com
System Location: Markham, Ontario
Boot Mode: manual
Inactivity Timeout(min): 120
Address Age Interval(min): 300
Inbound Telnet Enabled: Yes
Web Agent Enabled: Yes
Time Zone: GMT-05hours:00minutes
Day Light Time Rule: Canada
System UpTime: 7 Days 12 Hours 30 Mins 46
Secs
ML800#
System variables can be changed. Below is a list of system variables which GE
recommends changing.
• System Name: Using a unique name helps you to identify individual devices in a
network.
• System Contact and System Information: This is helpful for identifying the
administrator responsible for the switch and for identifying the locations of
individual switches.
To set these variables, change the mode to be SNMP configuration mode from the
manager mode using the following syntax
snmp
setvar [sysname|syscontact|syslocation] =<string>
The following command sequence sets the system name, system location and system
contact information.
ML800# snmp
ML800(snmp)## setvar ?
setvar: Configures system name, contact or
location
Usage: setvar
[sysname|syscontact|syslocation]=<string>
ML800(snmp)## setvar syslocation=Fremont
System variable(s) set successfully
ML800(snmp)## exit
ML800#

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–9

IP ADDRESSING CHAPTER 5: IP ADDRESSING

5.3.3 Date and Time

It may be necessary to set the day, time or the time zone manually. This can be done by
using the set command with the necessary date and time options with the following
syntax:
set timezone GMT=[+ or -] hour=<0-14>
min=<0-59>
set date year=<2001-2035> month=<1-12> day=<1-31>
[format=<mmddyyyy|ddmmyyyy|yyyymmdd>]
set time hour=<0-23> min=<0-59> sec=<0-59> [zone=GMT[+/-]hh:mm]
To set the time to be 08:10 am in the -5 hours from GMT (Eastern Standard Time) and to set
the date as 11 May 2005, the following sequence of commands are used.
ML800# set time hour=8 min=10 sec=0 zone=GMT-5:00
Success in setting device time
ML800# show time
Time: 8:10:04
ML800# show timezone
Timezone: GMT-05hours:00minutes
ML800# set date year=2005 month=5 day=11
Success in setting device date
ML800# show date
System Date: Wednesday 15-11-2005 (in mm
-dd-yyyy format)
ML800#
The syntax for other date and time commands are:
set timeformat format=<12|24>
set daylight country=<country name>
The following command sequence sets the daylight location:
ML800# set daylight country=Canada
Success in setting daylight savings to the
given location/country Canada
ML800# show daylight
Daylight savings location name: Canada
ML800#
The date and time can only be set through the command line interface software.

5.3.4 Network Time

Many networks synchronize the time using a network time server. The network time server
provides time to the different machines using the Simple Network Time Protocol (SNTP). To
specify the SNTP server, one has to
1. Set the IP parameters on the switch
2. Define the SNTP parameters

5–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

To set the SNTP parameter with the command line software, enter the SNTP configuration
mode from the manager. The setsntp, sync, and sntp commands can then be used to
setup the time synchronization automatically from the SNTP server. Note it is not sufficient
to setup the SNTP variables. Make sure to setup the synchronization frequency as well as
enable SNTP. The syntax for the above commands is shown below.
setsntp server = <ipaddress> timeout = <1-10>
retry = <1-3>
sync [hour=<0-24>] [min=<0-59>] (default = 24
hours)
sntp [enable|disable]
To set the SNTP server to be 3.94.210.5 (with a time out of 3 seconds and a number of
retries set to 3 times); allowing the synchronization to be ever 5 hours, the following
sequence of commands are used
ML800# sntp
ML800(sntp)## setsntp server=3.94.210.5 timeout=3 retry=3
SNTP server is added to SNTP server
database
ML800(sntp)## sync hour=5
ML800(sntp)## sntp enable
SNTP is already enabled.
ML800(sntp)## exit
ML800(sntp)#
SNTP parameters can be configured through the EnerVista Secure Web Management
software with the Configuration > SNTP menu item. The SNTP menu allows the time zone
(hours from GMT) to be defined along with other appropriate parameters on setting the
time and synchronizing clocks on network devices.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–11

IP ADDRESSING CHAPTER 5: IP ADDRESSING

The edit button allows editing of the SNTP parameters as shown below. Adding or deleting
SNTP servers is accomplished by using the add and delete buttons. Clicking the edit button
allows the specific SNTP parameter settings to be modified.

After the proper SNTP values are entered, click OK to register the changes, or click Cancel
to back out from the changes made.
To add an SNTP server, click the add button on the Configuration > SNTP menu. The menu
prompts you to add IP address of an SNTP server, the time out in seconds and the number
of retries, before the time synchronization effort is aborted. The Sync Now button allows
synchronization as soon as the server information is added.

If your site has internet access, there are several SNTP servers available online. A quick
Note

search will yield information about these servers. You can use the IP address of these
NOTE servers; however, please ensure the server can be reached by using the ping command.
The ping command can also be launched from the EnerVista software.

5–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

The Time Out value is in seconds. Note the time server can be a NTP server available on
the Internet. Ensure the IP parameters are configured for the switch and the device can be
pinged by the switch. Once the server is added, it is listed with the other SNTP servers.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–13

IP ADDRESSING CHAPTER 5: IP ADDRESSING

5.4 System Configuration

5.4.1 Saving and Loading – Command Line

Place the Switch offline while transferring Setting Files to the Switch.
Note

When transferring Settings Files from one Switch to another, the IP address of the
NOTE originating Switch will also be transferred. The user must therefore reset the IP address on
the receiving Switch before connecting to the network.
Configuration changes are automatically registered but not saved; that is, the effect of the
change is immediate. However, if power fails, the changes are not restored unless they
saved using the save command. It is also a good practice to save the configuration on
another network server using the tftp or ftp protocols. Once the configuration is saved, it
can be loaded to restore the settings. At this time, the saved configuration parameters are
not in a human readable format. The commands for saving and loading configurations on
the network are:
saveconf mode=<serial|tftp|ftp>
<ipaddress> file=<name>
loadconf mode=<serial|tftp|ftp>
<ipaddress> file=<name>
Ensure the machine specified by the IP address has the necessary services running. For
serial connections, x-modem or other alternative methods can be used. In most situations,
the filename must be a unique, since overwriting files is not permitted by most ftp and tftp
servers (or services). Only alphanumeric characters are allowed in the filename.
The following example illustrated how to save the configuration on a tftp server
ML800# saveconf mode=tftp 3.94.240.9 file=ML800set
Do you wish to upload the configuration?
['Y' or 'N'] Y
The saveconf and loadconf commands are often used to update software. Before the
software is updated, it is advised to save the configurations. The re-loading of the
configuration is not usually necessary; however, in certain situations it maybe needed and
it is advised to save configurations before a software update. The loadconf command
requires a reboot for the new configuration to be active. Without a reboot the older
configuration is used by the MultiLink family of switches.
The saveconf and loadconf commands are often used to update software to the
ML800. These commands will be deprecated in the version 2.x and above, and replaced
with the ftp, tftp, or xmodem commands. It is advised to begin using these commands
instead of saveconf and loadconf.

5.4.2 Config file

Multilink software can now use the ftp or tftp (or xmodem if using the CLI) to upload and
download information to a server running the proper services. One useful capability
provided in Multilink software is export of the CLI commands used to configure the switch.
To do this, use Config Upload/Download.
Using Config Download, examination of the contents of the saved file would appear as
shown below:

5–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

<ML800 -conf-1.0>
################################################################
# Copyright (c) 2001-2005 GE Digital Energy, Inc All rights reserved.
# RESTRICTED RIGHTS
# ---------------------------------
# Use, duplication or disclosure is subject to U.S. Government
# restrictions as set forth in Sub-division (b)(3)(ii) of the
# rights in Technical Data and Computer Software clause at
# 52.227-7013.
#
# This file is provided as a sample template to create a backup
# of GE MultiLink switches. As such, this script
# provides insights into the configuration of GE MultiLink
# switches settings. GE Digital Energy, Inc. recommends that modifications of this
# file and the commands should be verified by the User in a
# test environment prior to use in a "live" production network.
# All modifications are made at the User's own risk and are
# subject to the limitations of the GE MultiLink software End User
# License Agreement (EULA). Incorrect usage may result in
# network shutdown. GE Digital Energy, Inc. is not liable for incidental or
# consequential damages due to improper use.
################################################################
***This is a Machine Generated File.
***Only the SYSTEM config block is editable.
***Editing any other block will result in error while loading.
##########################################################
# Hardware Configuration - This area shows the type of #
# hardware and modules installed. #
##########################################################
[HARDWARE]
type=ML800
slotB=8 Port TP Module
##########################################################
# System Manager - This area configures System related #
# information. #
##########################################################

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–15

IP ADDRESSING CHAPTER 5: IP ADDRESSING

[SYSTEM]
***Edit below this line only***

system_name=ML800
system_contact=support@gemultilin.com
system_location= Markham, Ontario
boot_mode=manual
system_ip=192.168.5.5
system_subnet=0.0.0.0
system_gateway=0.0.0.0
idle_timeout=10
telnet_access=enable
snmp_access=enable

web_access=enable

Edit above this line only

##########################################################
# User Accounts - This area configures user accounts for #
# accessing this system. #
##########################################################
...

FIGURE 5–1: Contents of a config file

1. A config file allows only certain portions of the file to be edited by a user. Changing
Note

any other part of the file will result in the system not allowing the file to be loaded, as
NOTE
the CRC computed and stored in the file would not be matched. Should you want to
edit, edit the System portion of the file only. GE Digital Energy, Inc. recommends
editing the “script” file (see below)
2. File names cannot have special characters such as *#!@$^&* space and control
characters.

5–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

5.4.3 Displaying configuration

Using SWM, the need to display specific CLI commands for configuring capabilities is not
needed. The menus are modular and are alphabetically sorted to display each necessary
component in a logical manner. This section is repeated from the CLI manual, should the
need arise to view the necessary commands. The best way to view these commands is to
telnet to the switch using the Telnet menu from the Administration menu.
To display the configuration or to view specific modules configured, the ‘show config’
command is used as described below.
Syntax show config [module=<module-name>]
Where module-name can be:

Name Areas affected

IP Configuration, Boot mode, Users settings (e.g. login
system
names, passwords)
event Event Log and Alarm settings
port Port settings, Broadcast Protection and QoS settings
bridge Age time setting
stp STP, RSTP and LLL settings
ps Port Security settings
mirror Port Mirror settings
sntp SNTP settings
llan VLAN settings
gvrp GVRP settings
snmp SNMP settings
web Web and SSL/TLS settings
tacacs TACACS+ settings
auth 802.1x Settings
igmp IGMP Settings
smtp SMTP settings

If the module name is not specified the whole configuration is displayed.

ML800# show config

[HARDWARE]
type= ML800
slotB=8 Port TP Module
##########################################################

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–17

IP ADDRESSING CHAPTER 5: IP ADDRESSING

# System Manager - This area configures System related #

# information. #
##########################################################
[SYSTEM]
***Edit below this line only****
system_name=Main
system_contact=someone@joe.com
system_location= Markham, Ontario
boot_mode=manual
system_ip=192.168.1.15
system_subnet=0.0.0.0
system_gateway=192.168.1.11
idle_timeout=10
telnet_access=enable
snmp_access=enable
web_access=enable

--more—
...

FIGURE 5–2: ’show config’ command output

5–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

ML800# show config module=snmp

[HARDWARE]
type= ML800
slotB=8 Port TP Module
##########################################################
# Network Management - This area configures the SNMPv3 #
# agent. #
##########################################################
[SNMP]
engineid=LE_v3Engine
defreadcomm=public
defwritecomm=private
deftrapcomm=public
authtrap=disable
com2sec_count=0
group_count=0
view_count=1
view1_name=all
view1_type=included
view1_subtree=.1
view1_mask=ff

--more—
...

FIGURE 5–3: Displaying specific modules using the ‘show config’ command

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–19

IP ADDRESSING CHAPTER 5: IP ADDRESSING

ML800# show config module=snmp,system

[HARDWARE]
type= ML800
slotB=8 Port TP Module
##########################################################
# System Manager - This area configures System related #
# information. #
##########################################################
[SYSTEM]
***Edit below this line only****
system_name=Main
system_contact=someone@joe.com
system_location= Markham, Ontario
boot_mode=manual
system_ip=192.168.1.15
system_subnet=0.0.0.0
system_gateway=192.168.1.11
idle_timeout=10
telnet_access=enable
snmp_access=enable
web_access=enable

--more—
...

FIGURE 5–4: Displaying configuration for different modules.

Note – multiple modules can be specified on the command line

5.4.4 Saving Configuration

It is advisable to save the configuration before updating the software, as it may be
necessary in certain situations. The loadconf command requires a reboot to activate the
new configuration. Without a reboot, the ML800 used the previous configuration. When
reboot is selected, the user is prompted as follows:
Reboot? ['Y' or 'N']
Select “Y”. The ML800 will prompt:
Save Current Configuration?
Select “N”.

5–20 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

With release 1.7 and higher, the configuration can be saved in the older format (binary
Note

object) or in a new format as an ASCII file. The new format is recommended by GE Digital
NOTE Energy. Use the old format only if there are multiple MultiLink switches on the network
running different versions of software. GE Digital Energy recommends upgrading all
switches to the most current software release.
To ease the process of uploading and executing a series of commands, the ML800 can
create a host (equivalent to creating a host table on many systems). The command for
creating a host is:
host <add|edit|del> name=<host-name> ip=<ipaddress> user=<user>
pass=<password>
The show host command displays the host table entries
ML800# access
ML800(access)## host add name=server ip=192.168.5.2
Host added successfully
ML800(access)## show host
No Host Name IP Address User Password
=========================================
1 server 192.168.5.2 -- ******
2 -- -- -- --
3 -- -- -- --
4 -- -- -- --
5 -- -- -- --
6 -- -- -- --
7 -- -- -- --
8 -- -- -- --
9 -- -- -- --
10 -- -- -- --
ML800(access)##

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–21

IP ADDRESSING CHAPTER 5: IP ADDRESSING

5.4.5 Script File

Script file is a file containing a set of CLI commands which are used to configure the
switch. CLI commands are repeated in the file for clarity, providing guidance to the user
editing the file as to what commands can be used for modifying variables used by MNS.
The script file does not have a check sum at the end and is used for configuring a large
number of switches easily. As with any configuration file that is uploaded, GE Digital
Energy, Inc. recommends that modifications of this file and the commands should be
verified by the user in a test environment prior to use in a "live" production network.
The script file will look familiar to people familiar with the CLI commands as all the
commands saved in the script file are described in the CLI User Guide. A sample of the
script file is shown below.

###############################################################
#
# Copyright (c) 2001-2005 GE Digital Energy, Inc All rights reserved.
# RESTRICTED RIGHTS
# ---------------------------------
# Use, duplication or disclosure is subject to U.S. Government
# restrictions as set forth in Sub-division (b)(3)(ii) of the
# rights in Technical Data and Computer Software clause at
# 52.227-7013.
#
# This file is provided as a sample template to create a backup
# of GE MultiLink switches configurations. As such,
# this script provides insights into the configuration of GE MultiLink switch's settings.
# GE Digital Energy, Inc. recommends that modifications of this
# file and the commands should be verified by the User in a
# test environment prior to use in a "live" production network.
# All modifications are made at the User's own risk and are
# subject to the limitations of the GE MultiLink MNS End User
# License Agreement (EULA). Incorrect usage may result in
# network shutdown. GE Digital Energy, Inc. is not liable for incidental or
# consequential damages due to improper use.
###############################################################
#

##########################################################
# System Manager - This area configures System related #
# information. #
##########################################################

set bootmode type=manual

ipconfig ip=192.168.5.5 mask=0.0.0.0 dgw=0.0.0.0
set timeout=10
access
telnet enable
snmp enable
web=enable
exit
##########################################################
# User Accounts - This area configures user accounts for #
# accessing this system. #
##########################################################

user
add user=manager level=2
passwd user=manager
manager
<additional lines deleted for succinct viewing>

5–22 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

In the above example, note that all the commands are CLI commands. This script provides
an insight into the configuration of GE MultiLink switches settings. GE Digital Energy, Inc.
recommends that modifications of this file and the commands should be verified by the
User in a test environment prior to use in a "live" production network
To ease the process of uploading the script files, use the Script Upload/Download
capability described above.

5.4.6 Saving and Loading – EnerVista Software

Place the Switch offline while transferring Setting Files to the Switch.
Note

Ensure the machine specified by the IP address has the necessary services running on it.
For serial connections, x-modem or other alternative methods can be used. Generally, the
filename name must be a unique filename, as over-writing files is not permitted by most
FTP and TFTP servers (or services).
The following figure illustrates saving the configuration on a TFTP server. Note that the
menu is similar to the FTP screen described earlier.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–23

IP ADDRESSING CHAPTER 5: IP ADDRESSING

This process can also be used to update new software to the managed MultiLink switches.
Before the software is updated, it is advised to save the configurations. Reloading of the
configuration is not usually necessary, but in certain situations it may be needed, and it is
recommended that you save configurations before a software update. Make sure to
reboot the switch after a new configuration is loaded.
The file transfer operations allowed are:
1. Image Download (or Image Upload): Copy the ML800 image from switch to the
server (or from the server to the switch). The “Image Upload” option is
commonly used to upgrade the ML800 image on the switch.
2. Config Download (or Config Upload): Save the configuration of the switch on
the server (or load the saved configuration from the server to the switch). This
option is used to save a backup of the ML800 configuration or restore the
configuration (in case of a disaster.)
3. Script Download (or Script Upload): Save the necessary CLI commands used
for configuration of the switch (or upload the necessary CLI commands
needed to configure the switch). This option is used to ease the repetitive task
of configuring multiple commands or reviewing all the commands needed to
configure the ML800.
4. Host Download (or Host Upload): Save the host information. The hosts are
created by the Configuration - Access - Host commands
5. Log Upload - Save the log file on the ftp/tftp server
To save any changes,
 Click on the save ( ) icon.
The software will ask again if the changes need to be saved or
ignored.
 If the changes need to be ignored, click on Cancel and reboot the
switch.

5–24 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

 If the changes need to be saved, click on OK.

The following figures illustrate saving changes made after adding an SNTP server. This is
done by clicking on the Save icon to save current configuration

5.4.7 Host Names

Instead of typing in IP addresses of commonly reached hosts, the ML800 allows hosts to be
created with the necessary host names, IP addresses, user names, and passwords.
 Use the Configuration > Access > Host menu to create host entries
as shown below.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–25

IP ADDRESSING CHAPTER 5: IP ADDRESSING

 To add a host, click the Add button.

 Fill in all the fields below to create the necessary host entries.

5–26 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

 To delete or edit the entries, use the delete or edit icons next to each
entry shown above.

5.4.8 Erasing Configuration

Kill Config option using SWM

To erase the configuration and reset the configurations to factory defaults, you can use
the kill config option from Administration tab by selecting kill config.

User also has the option to save one module from defaulting back to factory defaults by
Note

checking the module box before issuing kill Config command.

NOTE

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–27

IP ADDRESSING CHAPTER 5: IP ADDRESSING

In the example below “system” module box has been checked. In this case after kill Config
command is issued by pressing the OK button, the Switch will perform a factory dump
restoring all the Switch settings back to factory defaults except for the “System” settings
which will be retained.

When the OK button is pressed the Switch will issue the following warning messages; and
reboot the switch for it to revert back to the factory default settings with the exceptions of
modules opted not to be defaulted.

5–28 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

Here is a list of the modules and related settings that can be selected not to default back to
factory default settings.

Name Areas affected

System IP Configuration, Boot mode
User Users settings (e.g. login names, passwords)
Port settings, Broadcast Protection and QoS
Port
settings
STP/RSTP STP, RSTP settings
Port-Security Port Security settings
Port-Mirror Port Mirror settings
VLAN Port/Tag VLAN settings
ACCESS IP-Access and Host Table settings
IGMP IGMP Settings
LACP LACP settings

Kill Config option using CLI

This command is a “hidden command”; that is, the on-line help and other help functions
normally do not display this command. The syntax for this command is:
kill Config
or
kill config save=module command
The kill Config command will default all the Switch settings back to factory defaults, while
the kill config save=module will default all with the exception of module selected.
Available modules are: system, user, acces, port, vlan, ps, mirror, lacp, slp, and igmp.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–29

IP ADDRESSING CHAPTER 5: IP ADDRESSING

It is recommended to save the configuration (using saveconf command discussed above)

before using the kill config command. The following two examples illustrate how to erase
all the Switch’s configuration using the kill config command and the second example
illustrates how to erase all the Switch’s configuration with the exception of ‘system’
configuration.
ML800# kill config
Do you want to erase the configuration?
['Y' or 'N'] Y
Successfully erased configuration...Please reboot.
ML800# kill config save=system
Do you want to erase the configuration?
['Y' or 'N'] Y
Successfully erased configuration...Please reboot.
Once the configuration is erased, please reboot the switch for the changes to take effect.

5–30 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

5.5 IPv6
This section explains how to access the GE MultiLink switches using IPv6 instead of IPv4
addressing. IPv6 provides a much larger address space and its use is often required.

Assumptions
It is assumed here that the user is familiar with IP addressing schemes and has other
supplemental material on IPv6, configuration, routing, setup and other items related to
IPv6. This user guide does not discuss these details.

5.5.1 Introduction to IPv6

IPv6 is short for "Internet Protocol Version 6". IPv6 is the "next generation" protocol or IPng
and was recommended to the IETF to replace the current version Internet Protocol, IP
Version 4 ("IPv4"). IPv6 was recommended by the IPv6 (or IPng) Area Directors of the
Internet Engineering Task Force at the Toronto IETF meeting on July 25, 1994 in RFC 1752:
The Recommendation for the IP Next Generation Protocol. The recommendation in
question, was approved by the Internet Engineering Steering Group and a proposed
standard was created on November 17, 1994. The core set of IPv6 protocols was created
as an IETF draft standard on August 10, 1998.
IPv6 is a new version of IP, designed to be an evolutionary step from IPv4. It is a natural
increment to IPv4. It can be installed as a normal software upgrade in internet devices and
is interoperable with the current IPv4. Its deployment strategy is designed to have no
dependencies. IPv6 is designed to run well on high performance networks (e.g. Gigabit
Ethernet, OC-12, ATM, etc.) and at the same time still be efficient on low bandwidth
networks (e.g. wireless). In addition, it provides a platform for the new level of internet
functionality that will be required in the near future.
IPv6 includes a transition mechanism designed to allow users to adopt and deploy it in a
highly diffuse fashion, and to provide direct interoperability between IPv4 and IPv6 hosts.
The transition to a new version of the Internet Protocol is normally incremental, with few or
no critical interdependencies. Most of today's internet uses IPv4, which is now nearly
twenty years old. IPv4 has been remarkably resilient in spite of its age, but it is beginning
to have problems. Most importantly, there is a growing shortage of IPv4 addresses, which
are needed by all new machines added to the Internet.
IPv6 fixes a number of problems in IPv4, such as the limited number of available IPv4
addresses. It also adds many improvements to IPv4 in areas such as routing and network
auto configuration. IPv6 is expected to gradually replace IPv4, with the two coexisting for a
number of years during the transition period.

5.5.2 What’s changed in IPV6?

The changes from IPv4 to IPv6 fall primarily into the following categories:
• Expanded Routing and Addressing Capabilities – IPv6 increases the IP address size
from 32 bits to 128 bits, to support more levels of addressing hierarchy, a much
greater number of addressable nodes, and simpler auto-configuration of
addresses. The scalability of multicast routing is improved by adding a "scope"
field to multicast addresses.
• A new type of address called an "anycast address" is defined, that identifies sets of
nodes where a packet sent to an anycast address is delivered to one of these

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–31

IP ADDRESSING CHAPTER 5: IP ADDRESSING

nodes. The use of anycast addresses in the IPv6 source route allows nodes to
control the path along which their traffic flows.
• Header Format Simplification - Some IPv4 header fields have been dropped or
made optional, to reduce the common-case processing cost of packet handling
and to keep the bandwidth cost of the IPv6 header as low as possible despite the
increased size of the addresses. Even though the IPv6 addresses are four times
longer than the IPv4 addresses, the IPv6 header is only twice the size of the IPv4
header.
• Improved Support for Options - Changes in the way IP header options are encoded
allow more efficient forwarding, less stringent limits on the length of options, and
greater flexibility for introducing new options in the future.
• Quality-of-Service Capabilities - A new capability is added to enable the labeling of
packets belonging to particular traffic "flows" for which the sender requests
special handling, such as non-default quality of service or "real- time" service.
• Authentication and Privacy Capabilities - IPv6 includes the definition of extensions
which provide support for authentication, data integrity, and confidentiality. This is
included as a basic element of IPv6 and will be included in all implementations.

5.5.3 IPv6 Addressing

IPv6 addresses are 128-bits long and are identifiers for individual interfaces and sets of
interfaces. IPv6 addresses of all types are assigned to interfaces, not nodes. Since each
interface belongs to a single node, any of that node's interface’s unicast addresses may be
used as an identifier for the node. A single interface may be assigned multiple IPv6
addresses of any type.
There are three types of IPv6 addresses. These are unicast, anycast, and multicast. Unicast
addresses identify a single interface. Anycast addresses identify a set of interfaces such
that a packet sent to an anycast address will be delivered to one member of the set.
Multicast addresses identify a group of interfaces, such that a packet sent to a multicast
address is delivered to all the interfaces in the group. There are no broadcast addresses in
IPv6. This function has been replaced by multicast addresses.
IPv6 supports addresses which are four times the number of bits as IPv4 addresses (128 vs.
32). This is 4 Billion x 4 Billion x 4 Billion (296) times the size of the IPv4 address space (232).
This works out to be:
340,282,366,920,938,463,463,374,607,431,768,211,456
This is an extremely large address space. In a theoretical sense this is approximately
665,570,793,348,866,943,898,599 addresses per square meter of the surface of the planet
Earth (assuming the earth surface is 511,263,971,197,990 square meters). In the most
pessimistic estimate this would provide 1,564 addresses for each square meter of the
surface of Earth. The optimistic estimate would allow for 3,911,873,538,269,506,102
addresses for each square meter of the surface Earth. Approximately fifteen percent of
the address space is initially allocated. The remaining 85% is reserved for future use.
Details of the addressing are covered by numerous articles on the WWW as well as other
literature, and are not covered here.

5.5.4 Configuring IPv6

The commands used for IPv6 are the same as those used for IPv4. Some of the commands
will be discussed in more details later. The only exception is the ‘ping’ command where
there is a special command for IPv6. That commands is ‘ping6’ and the syntax is as

5–32 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 5: IP ADDRESSING IP ADDRESSING

Syntax ping6 <IPv6 address> - pings an IPv6 station.

There is also a special command to ping the status of IPv6. That command is
Syntax show ipv6 - displays the IPv6 information.
To configure IPv6, the following sequence of commands can be used:

ML800# ipconfig ?
ipconfig : Configures the system IP address, subnet mask and gateway
Usage
ipconfig [ip=<ipaddress>] [mask=<subnet-mask>] [dgw=<gateway>]

ML800# ipconfig ip=fe80::220:6ff:fe25:ed80 mask=ffff:ffff:ffff:ffff::

Action Parameter Missing. "add" assumed.
IPv6 Parameters Set.
ML800# show ipv6

IPv6 Address : fe80::220:6ff:fe25:ed80 mask : ffff:ffff:ffff:ffff::

ML800# show ipconfig

IP Address : 192.168.5.5
Subnet Mask: 255.255.255.0
Gateway Address: 192.168.5.1
IPv6 Address: fe80::220:6ff:fe25:ed80 mask : ffff:ffff:ffff:ffff::
IPv6 Gateway: ::

ML800#

FIGURE 5–5: Configuring IPv6

In addition to the commands listed above, the commands which support IPv6 addressing
are
Syntax ftp <IPv6 address> - ftp to an IPv6 station
Example – ftp fe80::220:6ff:fe25:ed80
Syntax telnet <IPv6 address> - telnet to an IPv6 station
Example – telnet fe80::220:6ff:fe25:ed80
Besides, if the end station supports IPv6 addressing (as most Linux and Windows systems
do), one can access the switch using the IPv6 addressing as shown in the example below
http://fe80::220:6ff:fe25:ed80

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 5–33

IP ADDRESSING CHAPTER 5: IP ADDRESSING

5.5.5 List of commands in this chapter

Syntax ipconfig [ip=<ip-address>] [mask=<subnet-mask>] [dgw=<gateway>] [add|del]
– configure an IPv6 address. The add/delete option can be used to add or delete IPv4/IPv6
addresses.
Syntax show ipconfig – display the IP configuration information – including IPv6 address
Syntax ping6 <IPv6 address> - pings an IPv6 station
Syntax show ipv6 - displays the IPv6 information
Syntax ftp <IPv6 address> - ftp to an IPv6 station
Syntax telnet <IPv6 address> - telnet to an IPv6 station.

5–34 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 6: Access Considerations

Access Considerations

6.1 Securing Access

6.1.1 Description
This section explains how the access to the MultiLink ML800 Managed Edge Switch can be
secured. Further security considerations are also covered such as securing access by IP
address or MAC address.

It is assumed here that the user is familiar with issues concerning security as well as
Note

securing access for users and computers on a network. Secure access on a network can
NOTE be provided by authenticating against an allowed MAC address as well as IP address.

6.1.2 Passwords
The MultiLink ML800 Managed Edge Switch has a factory default password for the
manager as well as the operator account. Passwords can be changed from the user ID by
using the set password command.
For example:
ML800# set password
Enter Current Password: *******
Enter New Password:*******
Confirm New Password:*******
Password has been modified successfully
ML800#

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–1

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

6.1.3 Port Security Feature

The port security feature can be used to block computers from accessing the network by
requiring the port to validate the MAC address against a known list of MAC addresses. This
port security feature is provided on an Ethernet, or Fast Ethernet, port. In case of a security
violation, the port can be configured to go into the disable mode or drop mode. The disable
mode disables the port, not allowing any traffic to pass through. The drop mode allows the
port to remain enabled during a security violation and drop only packets that are coming
in from insecure hosts. This is useful when there are other network devices connected to
the MultiLink ML800 Managed Edge Switch. If there is an insecure access on the secondary
device, the MultiLink ML800 Managed Edge Switch allows the authorized users to continue
to access the network; the unauthorized packets are dropped preventing access to the
network.

Network security hinges on the ability to allow or deny access to network resources. This
Note

aspect of secure network services involves allowing or disallowing traffic based on

NOTE information contained in packets, such as the IP address or MAC address. Planning for
access is a key architecture and design consideration. For example, which ports are
configured for port security? Normally rooms with public access (e.g. lobby, conference
rooms, etc.) should be configured with port security. Once that is decided, the next few
decisions are: Who are the authorized and unauthorized users? What action should be
taken against authorized as well as unauthorized users? How are the users identified as
authorized or unauthorized?

6–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

6.2 Configuring Port Security through the Command

Line Interface

6.2.1 Commands
To configure port security, login as a level 2 user or as a manager. Once logged in, get to
the port-security configuration level to setup and configure port security with the following
command syntax:
configure port-security
port-security
For example, using the configure port-security command:
ML800# configure port-security
ML800(port-security)##
Alternately, the port-security command can also be used to enter the port-security
configuration mode:
ML800# port-security
ML800#(port-security)##
From the port security configuration mode, the switch can be configured to:
1. Auto-learn the MAC addresses.
2. Specify individual MAC addresses to allow access to the network.
3. Validate or change the settings.
The command syntax for the above actions are:
allow mac=<address|list|range>
port=<num|list|range>
learn port=<number-list> <enable|disable>
show port-security
action port=<num|list|range>
<none|disable|drop>
signal port=<num|list|range>
<none|log|trap|logandtrap>
ps <enable|disable>
remove mac=<all|address|list|range>
port=<num|list|range>
signal port=<num|list|range>
<none|log|trap|logandtrap>
Where the following hold:
• allow mac - configures the switch to setup allowed MAC addresses on specific
ports
• learn port - configures the switch to learn the MAC addresses associated with
specific port or a group of ports
• show port-security - shows the information on port security programmed or
learnt
• action port - specifies the designated action to take in case of a non
authorized access
• ps - port security - allows port security to be enable or disabled

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–3

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

• remove mac - removes specific or all MAC addresses from port security lookup
• signal port=<num|list|range> - observe list of specified ports and notify if
there is a security breach on the list of port specified. The signal can be a log entry,
a trap to the trap receiver specified as part of the SNMP commands (where is that
specified) or both

There is a limitation of 200 MAC addresses per port and 500 MAC addresses per switch for
Note

port security.

All commands listed above must be executed under the port security configuration mode.
Note

NOTE
Let's look at a few examples. The following command allows specific MAC addresses on a
specified port. No spaces are allowed between specified MAC addresses.
ML800(port-security)## allow mac=00:c1:00:7f:ec:00,00:60:b0:88:9e:00
port=18
The following command sequence sets the port security to learn the MAC addresses. Note
that a maximum of 200 MAC addresses can be learned per port, to a maximum of 500 per
switch. Also, the action on the port must be set to none before the port learns the MAC
address information.
ML800(port-security)## action port=1, 2 none
ML800(port-security)## learn port=1, 2 enable
The following command sequence enables and disables port security
ML800(port-security)## ps enable
Port Security is already enabled
ML800(port-security)## ps disable
Port Security Disabled
ML800 ps enable
Port Security Enabled

6.2.2 Allowing MAC Addresses

The Port Security feature has to be used with the combination of commands shown below
in order for it to be implemented successfully.
To configure a port to allow only a certain MAC address (single or a list of max 200 MAC
addresses per port and 500 MAC addresses per ML800, as per manuals) we have to:
1. Verify that the port is in default port security status.
2. Use the following commands:
#port-security
(port-security)##ps enable
(port-security)##allow mac=<address,list,range> port=<num,list,range>
(port-security)##action port=<num,list,range>drop

All the above commands have to be configured in this sequence, otherwise the port will
Note

remain insecure.
NOTE

6–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

To deny a mac address, use the following:

#port-security
(port-security)##ps enable
(port-security)##deny mac=<address,list,range> port=<num,list,range>
(port-security)##action port=<num,list,range>drop
Example 6-1 views port security settings on a switch. Learning is enabled on port 1. This
port has 6 stations connected to it with the MAC addresses as shown. Other ports have
learning disabled and the MAC addresses are not configured on those ports.

Example 6-1: Viewing the port security settings

ML800# show port-security

PORT STATE SIGNAL ACTION LEARN COUNT MAC ADDRESS
---- ----- ------ ------ ----- ----- -----------
1 ENABLE LOG NONE ENABLE 6 00:e0:29:2a:f1:bd
00:01:03:e2:27:89
00:07:50:ef:31:40
00:e0:29:22:15:85
00:03:47:ca:ac:45
00:30:48:70:71:23
2 ENABLE NONE NONE DISABLE 0 Not Configured
3 ENABLE NONE NONE DISABLE 0 Not Configured
4 ENABLE NONE NONE DISABLE 0 Not Configured
5 ENABLE NONE NONE DISABLE 0 Not Configured
6 ENABLE NONE NONE DISABLE 0 Not Configured

ML800(port-security)##

Example 6-2: Enabling learning on a port

ML800(port-security)## learn port=3 enable

Port Learning Enabled on selected port(s)
ML800(port-security)## show port-security
PORT STATE SIGNAL ACTION LEARN COUNT MAC ADDRESS
---- ----- ------ ------ ----- ----- -----------
1 ENABLE LOG NONE ENABLE 6 00:e0:29:2a:f1:bd
00:01:03:e2:27:89
00:07:50:ef:31:40
00:e0:29:22:15:85
00:03:47:ca:ac:45
00:30:48:70:71:23
2 ENABLE NONE NONE DISABLE 0 Not Configured
3 ENABLE NONE NONE ENABLE 0 Not Configured
4 ENABLE NONE NONE DISABLE 0 Not Configured
5 ENABLE NONE NONE DISABLE 0 Not Configured
6 ENABLE NONE NONE DISABLE 0 Not Configured

ML800(port-security)##

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–5

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

Example 6-2 shows how to enable learning on a port. After the learning is enabled, the
port security can be queried to find the status of MAC addresses learnt. If there were
machines connected to this port, the MAC address would be shown on port 3 as they are
shown on port 1.
Example 6-3 shows how to allow specific MAC address on specific ports. After the MAC
address is specified, the port or specific ports or a range of ports can be queried as shown.
Example 6-4 shows how to remove a MAC address from port security
To set logging on a port, use the following command sequence:
ML800(port-security)## signal port=3 logandtrap
Port security Signal type set to Log and
Trap on selected port(s)
The examples provided illustrate the necessary commands to setup port security. The
recommended steps to setup security are:
 Set the ML800 software to allow port security commands (use the
port-security command).
 Enable port security (use the enable ps command).
 Enable learning on the required ports (for example, use the learn
port=3 enable command for port 3).
 Verify learning is enables and MAC addresses are being learnt on
required ports (use the show port-security port=3 command).
 Save the port-security configuration (use the save command).

Example 6-3: Allowing specific MAC addresses on specific ports

ML800(port-security)## allow mac=00:c1:00:7f:ec:00 port=1,3,5

Specified MAC address(es) allowed on selected port(s)
ML800(port-security)## show port-security port=1,3,5
PORT STATE SIGNAL ACTION LEARN COUNT MAC ADDRESS
---- ----- ------ ------ ----- ----- -----------
1 ENABLE LOG NONE ENABLE 6 00:e0:29:2a:f1:bd
00:01:03:e2:27:89
00:07:50:ef:31:40
00:e0:29:22:15:85
00:03:47:ca:ac:45
00:30:48:70:71:23
00:c1:00:7f:ec:00
3 ENABLE NONE NONE ENABLE 0 00:c1:00:7f:ec:00
5 ENABLE NONE NONE DISABLE 0 00:c1:00:7f:ec:00

Example 6-4: Removing MAC addresses from specific ports

ML800(port-security)## remove mac=00:c1:00:7f:ec:00 port=3

Specified MAC address(es) removedfrom selected
port(s)
ML800(port-security)## show port-security port=3
PORT STATE SIGNAL ACTION LEARN COUNT MAC ADDRESS
---- ----- ------ ------ ----- ----- -----------

6–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

 Disable learning on required ports (for example, use the learn

port=3,5 disable command).
 (Optional step) Add any specific MAC addresses, if needed, to allow
designated devices to access the network (use the add
mac=00:c1:00:7f:ec:00 port=3,5 command).
 Disable access to the network for unauthorized devices (Use action
port=3 <diable|drop> depending on whether the port should
be disabled or the packed dropped. Follow that with a show port-
security command to verify the setting).
 (Optional step) Set the notification to notify the management station
on security breach attempts (use the command signal port to
make a log entry or send a trap).

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–7

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

Example 6-5 illustrates these steps for setting up port security on a specific port:
Once port security is setup, it is important to manage the log and review the log often. If
the signals are sent to the trap receiver, the traps should also be reviewed for intrusion and
other infractions.

6.2.3 Security Logs

All events occurring on the MultiLink ML800 Managed Edge Switch are logged. The events
can be informational (e.g. login, STP synchronization etc.), debugging logs (for debugging
network and other values), critical (critical events), activity (traffic activity) and fatal events

Example 6-5: Configuring port security

ML800# port-security
ML800(port-security)## ps enable
Port Security is already enabled
ML800(port-security)## learn port=3 enable
Port Learning Enabled on selected port(s)
ML800(port-security)## show port-security
PORT STATE SIGNAL ACTION LEARN COUNT MAC ADDRESS
---- ----- ------ ------ ----- ----- -----------
1 ENABLE LOG NONE ENABLE 6 00:e0:29:2a:f1:bd
00:01:03:e2:27:89
00:07:50:ef:31:40
00:e0:29:22:15:85
00:03:47:ca:ac:45
00:30:48:70:71:23
2 ENABLE NONE NONE DISABLE 0 Not Configured
3 ENABLE NONE NONE ENABLE 0 00:c1:00:7f:ec:00
4 ENABLE NONE NONE DISABLE 0 Not Configured
5 ENABLE NONE NONE DISABLE 0 Not Configured
6 ENABLE NONE NONE DISABLE 0 Not Configured

ML800(port-security)## save
Saving current configuration
Configuration saved
ML800(port-security)## learn port=3 disable
Port Learning Disabled on selected port(s)
ML800(port-security)## action port=3 drop
Port security Action type set to Drop on selected
port(s)
ML800(port-security)## show port-security port=3
PORT STATE SIGNAL ACTION LEARN COUNT MAC ADDRESS
---- ----- ------ ------ ----- ----- -----------
3 ENABLE NONE DROP ENABLE 0 00:c1:00:7f:ec:00
ML800(port-security)## signal port=3 logandtrap
Port security Signal type set to Log and Trap on
selected port(s)

6–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

(such as unexpected behavior). The specific types of logs can be viewed and cleared. The
show log command displays the log information and the clear log command clears
the log entries. The syntax for these commands is shown below:
show log [1..5|informational|debug|fatal |critical|activity]
clear log [informational|debug|activity |critical|fatal]
The set logsize command set the number of lines to be collected in the log before the
oldest record is re-written. The syntax for this command is:
set logsize size=<1-1000>
Example 6-6 illustrates the show log and clear log commands. The show log
command indicates the type of log activity in the S column. I indicates informational
entries and A indicates activities which are a result of port-security setup. Notice the
clear log informational command clears the informational entries only.
The log shows the most recent intrusion at the top of the listing. If the log is filled when the
switch detects a new intrusion, the oldest entry is dropped off the listing.
As discussed in the prior section, any port can be set to monitor security as well as make a
log on the intrusions that take place. The logs for the intrusions are stored on the switch.
When the switch detects an intrusion on a port, it sets an “alert flag” for that port and
makes the intrusion information available.
The default log size is 50 rows. To change the log size, use the set logsize command.
When the switch detects an intrusion attempt on a port, it records the date and time
stamp, the MAC address, the port on which the access was attempted and the action
taken by ML800 software. The event log lists the most recently detected security violation
attempts. This provides a chronological entry of all intrusions attempted on a specific port.

Example 6-6: Security log commands

ML800# show log

S Date Time Log Description
- ---- ---- ---------------
I 12-07-2004 9:01:34 A.M CLI:manager console login
I 12-07-2004 5:54:23 P.M SNTP:Date and Time updated from SNTP server
I 12-08-2004 6:09:00 P.M SNTP:Date and Time updated from SNTP server
I 12-09-2004 1:48:56 P.M TELNET:Telnet Session Started
I 12-09-2004 1:49:23 P.M CLI:manager console login
I 12-09-2004 4:26:26 P.M TELNET:Telnet Session Started
I 12-09-2004 4:26:34 P.M CLI:manager console login
I 12-09-2004 6:23:37 P.M SNTP:Date and Time updated from SNTP server
I 12-10-2004 6:38:13 P.M SNTP:Date and Time updated from SNTP server
I 12-11-2004 10:16:24 A.M TELNET:Telnet Session Started
I 12-11-2004 6:52:49 P.M SNTP:Date and Time updated from SNTP server
I 12-12-2004 12:40:35 P.M TELNET:Telnet Session Started
I 12-12-2004 12:40:42 P.M CLI:manager console login
A 12-17-2004 12:05:52 P.M PS:INTRUDER 00:e0:29:6c:a4: fd@port11, packet dropped
A 12-17-2004 12:07:04 P.M PS:INTRUDER 00:50:0f:02:33: b6@port15, packet dropped
A 12-17-2004 12:07:16 P.M PS:INTRUDER 00:e0:29:2a:f0: 3a@port15, packet dropped
ML800# clear log informational
Clear Logged Events? ['Y' or 'N']
ML800# show log
S Date Time Log Description
- ---- ---- ---------------
A 12-17-2004 12:05:52 P.M PS:INTRUDER 00:e0:29:6c:a4: fd@port3, packet dropped

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–9

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

The event log records events as single-line entries listed in chronological order, and serves
as a tool for isolating problems. Each event log entry is composed of four fields
• Severity - the level of severity (see below).
• Date - date the event occurred on. See Date and Time on page 5–10 for
information on setting the date and time on the switch.
• Time - time the event occurred on. See Date and Time on page 5–10 for
information on setting the date and time on the switch
• Log Description - description of event as detected by the switch
Severity has one of the following values, and depending on the severity type, is assigned a
severity level.
• I (information, severity level 1) indicates routine events.
• A (activity, severity level 2) indicates the activity on the switch.
• D (debug, severity level 3) is reserved for GE Digital Energy internal diagnostic
information
• C (critical, severity level 4) indicates that a severe switch error has occurred.
• F (fatal, severity level 5) indicates that a service has behaved unexpectedly.

6.2.4 Authorized Managers

Just as port security allows and disallows specific MAC addresses from accessing a
network, the ML800 software can allow or block specific IP addresses or a range of IP
addresses to access the switch. The access command allows access to configuration
mode:
access
The allow ip command allows specified services for specified IP addresses. IP addresses
can be individual stations, a group of stations or subnets. The range is determined by the IP
address and netmask settings.
allow ip=<ipaddress> mask=<netmask> service=<name|list>
The deny ip command denies access to a specific IP address(es) or a subnet. IP
addresses can be individual stations, a group of stations or subnets. The range is
determined by the IP address and netmask settings.
deny ip=<ipaddress> mask=<netmask> service=<name|list>
The remove ip command removes specific IP address(es) or subnet by eliminating
specified entry from the authorized manager list.
remove ip=<ipaddress> mask=<netmask>
The removeall command removes all authorized managers.
removeall
The show ip-access command displays a list of authorized managers
show ip-access

It is assumed here that the user is familiar with IP addressing schemes (e.g. class A, B, C,
Note

etc.), subnet masking and masking issues such as how many stations are allowed for a
NOTE given subnet mask.

6–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

In Example 6-7, any computer on 3.94.245.10 network is allowed (note how the subnet
mask indicates this). Also, a specific station with IP address 3.94.245.25 is allowed (again
note how the subnet mask is used). An older station with IP address 3.94.245.15 is
removed.

Example 6-7: Allowing/blocking specific IP addresses

ML800# access
ML800(access)## allow ip=3.94.245.10 mask=255.255.255.0 service=tel
Service(s) allowed for specified address
ML800(access)## allow ip=3.94.245.25 mask=255.255.255.255 service=t
Service(s) allowed for specified address
ML800(access)## remove ip=3.94.245.15 mask=255.255.255.255
Access entry removed
ML800(access)## exit
ML800# show ip-access
============================================================
IP Address | Mask | Telnet | Web | SNMP |
============================================================
3.94.245.10 255.255.255.0 ALLOWED DENIED DENIED

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–11

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

6.3 Configuring Port Security with EnerVista Software

6.3.1 Commands
After enabling the EnerVista Secure Web Management software,
 Select the Configuration > Port > Security menu item to configure
port security as shown below.

From the menu shown above, each individual port can be configured for the proper action
on the port, auto learn MAC addresses and specify individual MAC addresses.
 To edit each port, click on the edit icon ( ).
 To enable or disable port security, use the Status drop down menu
as shown below.

6–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

Note that the screen also provides an overview of each port on the switch. Each port can
be individually configured for the proper port security action.
Each individual port can be configured by clicking on the edit icon ( ). Once the edit
screen is shown, the following actions can be taken for each port:
1. The port can be specified to create a log entry or send a trap, do both or do
nothing. This is done through the Signal Status drop down menu.
2. The port can be specified to drop the connection, disable the port or do
nothing. This is indicated by the Action Status drop down menu.
3. The port can be put in the learn mode or the learning can be disabled. This is
indicated by the Learn Status drop down menu.
Additionally, MAC addresses can be added or deleted from the table of allowed MAC
addresses.
 To delete a MAC address, click on the delete icon ( ).
 To add a MAC address, click on the Add button and fill in the MAC
address in the MAC address window.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–13

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

There is a limitation of 200 MAC addresses per port and 500 MAC addresses per switch for
port security.
After clicking on the Add button, the following screen appears, allowing the entry of a
specific MAC address

Once port security is setup, it is important to manage the log and review it often. If the
signals are sent to the trap receiver, the traps should also be reviewed for intrusion and
other infractions.

6–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

6.3.2 Logs
All events occurring on the Managed MultiLink ML800 Managed Edge Switch are logged.
The events can be informational (e.g. login, STP synchronization etc.), debugging logs (for
debugging network and other values), critical (critical events), activity (traffic activity) and
fatal events (such as unexpected behavior). The specific types of logs can be viewed and
cleared. To view the logs in the EnerVista Secure Web Management software, select the
Configuration > Logs menu item.

Note the different types of logs. Specific logs may be viewed by using the drop down menu
in the top right corner
As discussed in the previous section, any port can be set to monitor security as well as
make a log on the intrusions that take place. The logs for the intrusions are stored on the
switch. When the switch detects an intrusion on a port, it sets an “alert flag” for that port
and makes the intrusion information available.

The default log size is 50 rows. To change the log size, select the Configuration > Statistics
Note

> Log Statistics menu item.

NOTE
When the switch detects an intrusion attempt on a port, it records the date and time
stamp, the MAC address, the port on which the access was attempted and the action
taken by the MultiLink ML800 Managed Edge Switch. The event log lists the most recently
detected security violation attempts. This provides a chronological entry of all intrusions
attempted on a specific port.
The event log records events as single-line entries listed in chronological order, and serves
as a tool for isolating problems. Each event log entry is composed of four fields
• Severity - the level of severity (see below).
• Date - date the event occurred on. See Date and Time on page 5–10 for
information on setting the date and time on the switch.
• Time - time the event occurred on. See Date and Time on page 5–10 for
information on setting the date and time on the switch
• Log Description - description of event as detected by the switch

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–15

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

Severity has one of the following values, and depending on the severity type, is assigned a
severity level.
• I (information, severity level 1) indicates routine events.
• A (activity, severity level 2) indicates the activity on the switch.
• D (debug, severity level 3) is reserved for GE Digital Energy internal diagnostic
information
• C (critical, severity level 4) indicates that a severe switch error has occurred.
• F (fatal, severity level 5) indicates that a service has behaved unexpectedly.

6.3.3 Authorized Managers

Just as port security allows and disallows specific MAC addresses from accessing a
network, the EnerVista Secure Web Management software can allow or block specific IP
addresses or a range of IP addresses to access the switch.
 Access this functionality via the Configuration > Access > IP Access
menu item.

The window above show the authorized access list for managing the switch. Note specific
services can be authorized. Also note that individual stations or a group of stations with IP
addresses can be authorized.

It is assumed that users are familiar with IP addressing schemes (e.g. class A, B, C etc.),
Note

subnet masking and masking issues such as how many stations are allowed for a given
NOTE subnet mask.
In the following example, any computer on 10.10.10.0 sub network is allowed (note how
the subnet mask is used to indicate that). Also, a specific station with IP address
192.168.15.25 is allowed (again note how the subnet mask is used to allow only one
specific station in the network) and an older station with IP address 192.168.15.15 is
removed.

6–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 6–17

ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS

6–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 7: Access Using RADIUS

Access Using RADIUS

7.1 Introduction to 802.1x

7.1.1 Description
The TACACS+ protocol is the latest generation of TACACS. TACACS is a simple UDP (User
Datagram Protocol) based access control protocol originally developed by BBN for the
MILNET (Military Network). Later the enhancements were called TACACS+. TACACS+ is a TCP
(Transmission Control Protocol) based access control protocol. TCP offers a connection-
oriented transport, while UDP offers best-effort delivery making the access authentication
reliable.
Remote Authentication Dial-In User Service or RADIUS is a server that has been
traditionally used by many Internet Service Providers (ISP) as well as Enterprises to
authenticate dial in users. Today, many businesses use the RADIUS server for
authenticating users connecting into a network. For example, if a user connects PC into
the network, whether the PC should be allowed access or not provides the same issues as
to whether or not a dial in user should be allowed access into the network or not. A user
has to provide a user name and password for authenticated access. A RADIUS server is
well suited for controlling access into a network by managing the users who can access
the network on a RADIUS server. Interacting with the server and taking corrective action(s)
is not possible on all switches. This capability is provided on the MultiLink ML800 Managed
Edge Switch.
RADIUS servers and its uses are also described by one or more RFCs.

7.1.2 802.1x Protocol

There are three major components of 802.1x: - Supplicant, Authenticator and
Authentication Server (RADIUS Server). In the figure below, the PC acts as the supplicant.
The supplicant is an entity being authenticated and desiring access to the services. The
switch is the authenticator. The authenticator enforces authentication before allowing
access to services that are accessible via that port. The authenticator is responsible for
communication with the supplicant and for submitting the information received from the
supplicant to a suitable authentication server. This allows the verification of user

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–1

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

credentials to determine the consequent port authorization state. It is important to note

that the authenticator's functionality is independent of the actual authentication method.
It effectively acts as a pass-through for the authentication exchange.

FIGURE 7–1: 802.1x network components

The RADIUS server is the authentication server. The authentication server provides a
standard way of providing Authentication, Authorization, and Accounting services to a
network. Extensible Authentication Protocol (EAP) is an authentication framework which
supports multiple authentication methods. EAP typically runs directly over data link layers
such as PPP or IEEE 802, without requiring IP. EAP over LAN (EAPOL) encapsulates EAP
packets onto 802 frames with a few extensions to handle 802 characteristics. EAP over
RADIUS encapsulates EAP packets onto RADIUS packets for relaying to RADIUS
authentication servers.
The details of the 802.1x authentication are as follows.
1. The supplicant (host) is initially blocked from accessing the network. The
supplicant wanting to access these services starts with an EAPOL-Start frame.
2. The authenticator (MultiLink ML800 Managed Edge Switch), upon receiving an
EAPOL-start frame, sends a response with an EAP-Request/Identity frame
back to the supplicant. This will inform the supplicant to provide its identity.
3. The supplicant then sends back its own identification using an EAP-Response/
Identity frame to the authenticator (MultiLink ML800 Managed Edge Switch).
The authenticator then relays this to the authentication server by
encapsulating the EAP frame on a RADIUS-Access-Request packet.
4. The RADIUS server will then send the authenticator a RADIUS-Access-
Challenge packet.
5. The authenticator (MultiLink ML800 Managed Edge Switch) will relay this
challenge to the supplicant using an EAP-Request frame. This will request the
supplicant to pass its credentials for authentication.
6. The supplicant will send its credentials using an EAP-Response packet.
7. The authenticator will relay using a RADIUS-Access-Request packet.
8. If the supplicant's credentials are valid, RADIUS-Access-Accept packet is sent
to the authenticator.
9. The authenticator will then relay this on as an EAP-Success and provides
access to the network.
10. If the supplicant does not have the necessary credentials, a RADIUS-Access-
Deny packet is relayed to the supplicant as an EAP-Failure frame. The access
to the network continues to be blocked.

7–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS

FIGURE 7–2: 802.1x authentication details

The ML800 software implements the 802.1x authenticator. It fully conforms to the
standards as described in IEEE 802.1x, implementing all the state machines needed for
port-based authentication. The ML800 software authenticator supports both EAPOL and
EAP over RADIUS to communicate to a standard 802.1x supplicant and RADIUS
authentication server.
The ML800 software authenticator has the following characteristics:
• Allows control on ports using STP-based hardware functions. EAPOL frames are
Spanning Tree Protocol (STP) link Bridge PDUs (BPDU) with its own bridge multicast
address.
• Relays MD5 challenge (although not limited to) authentication protocol to RADIUS
server
• Limits the authentication of a single host per port
• The MultiLink ML800 Managed Edge Switch provides the IEEE 802.1x MIB for SNMP
management

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–3

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

7.2 Configuring 802.1x through the Command Line

Interface

7.2.1 Commands
On enabling 802.1x ports, make sure the port which connects to the RADIUS servers needs
to be manually authenticated. To authenticate the port, use the setport command. The
CLI commands to configure and perform authentication with a RADIUS server are
described below.
The auth command enters the configuration mode to configure the 802.1x parameters.
auth
The show auth command displays the 802.1x configuration or port status.
show auth <config|ports>
The authserver command define the RADIUS server. Use the UDP socket number if the
RADIUS authentication is on a port other than 1812.
authserver [ip=<ip-addr>] [udp=<num>] [secret=<string>]
The auth enable and auth disable commands enable or disable the 802.1x
authenticator function on the MultiLink ML800 Managed Edge Switch.
auth <enable|disable>
The setport command configures the port characteristics for an 802.1x network.
setport port=<num|list|range> [status=<enable|disable>]
[control=<auto|forceauth|forceunauth>] [initialize=<assert|deassert>]
The backend port command configure the parameters for EAP over RADIUS.
backend port=<num|list|range>
[supptimeout=<1-240>]
[servertimeout=<1-240] [maxreq=<1-10>]
The port argument is mandatory and represents the port(s) to be configured. The
supptimeout argument is optional and represents the timeout in seconds the
authenticator waits for the supplicant to respond back. The default value is 30 seconds
and values can range from 1 to 240 seconds. The servertimeout argument is optional
and represents the timeout in seconds the authenticator waits for the back-end RADIUS
server to respond. The default value is 30 seconds and can range from 1 to 240 seconds.
The maxreq argument is optional and represents the maximum number of times the
authenticator will retransmit an EAP request packet to the Supplicant before it times out
the authentication session. Its default value is 2 and can be set to any integer value from 1
to 10.
The portaccess command sets port access parameters for authenticating PCs or
supplicants.
portaccess port=<num|list|range>
[quiet=<0-65535>] [maxreauth=<0-10>] [transmit=<1-65535>]
The port argument is mandatory and identifies the ports to be configured. The quiet
argument is optional and represents the quiet period – the amount of time, in seconds, the
supplicant is held after an authentication failure before the authenticator retries the
supplicant for connection. The default value is 60 seconds and values can range from 0 to
65535 seconds. The maxreauth argument is optional and represents the number of re-
authentication attempts permitted before the port is unauthorized. The default value is 2
and integer values can range from 0 to 10. The transmit argument is optional and
represents the transmit period. This is the time in seconds the authenticator waits to
transmit another request for identification from the supplicant. The default value is 30 and
values range from 1 to 65535 seconds

7–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS

The reauth command determines how the authenticator (MultiLink ML800 Managed
Edge Switch) performs the re-authentication with the supplicant or PC.
reauth port=<num|list|range> [status=<enable|disable>]
[period=<10-86400>]
The port argument is mandatory and sets the ports to be configured. The status argument
is optional and enables/disables re-authentication. The period argument is optional and
represents the re-authentication period. This is the time in seconds the authenticator waits
before a re-authentication process will be performed again to the supplicant. The default
value is 3600 seconds (1 hour), and values range from 10 to 86400 seconds.
The show-stats command displays 802.1x related statistics.
show-stats port=<num>
The trigger-reauth command manually initiates a re-authentication of supplicant.
trigger-reauth port=<num|list|range>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–5

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

7.2.2 Example
Example 7-1 demonstrates how to secure the network using port access. Ensure there is
no 802.1x or RADIUS server defined. Only one RADIUS server can be defined for the entire
network.

Example 7-1: Setting port control parameters The RADIUS server is on port 2. This port is
authenticated manually. If the RADIUS server is
802.1X Authenticator Configuration several hops away, it may be necessary to
================================== authenticate the interconnection ports. Make sure
Status: Disabled the setport port=2 status=enable
RADIUS Authentication Server control=forceauth initialize=assert command
================================== is executed before the auth enable command.
IP Address: 0.0.0.0
UDP Port: 1812
Shared Secret:
ML800# auth
ML800(auth)## setport port=2 status=enable control=forceauth initialize=assert
Successfully set port control parameter(s) The auth disable command is not
necessary. However, it is shown for
ML800(auth)## auth disable completeness in case a RADIUS
802.1X Authenticator is disabled. server was defined with a previously
set authentication scheme.
ML800(auth)## authserver ip=3.204.240.1 secret=secret
Successfully set RADIUS Authentication Server parameter(s)
ML800(auth)## auth enable
802.1X Authenticator is enabled.
ML800(auth)## show auth ports
Port Status Control Initialize Current State
The RADIUS server is
======================================================
connected on port #2
1 Enabled Auto Deasserted Authorized
2 Enabled ForcedAuth Asserted Unauthorized
3 Enabled Auto Deasserted Authorized
4 Enabled Auto Deasserted Unauthorized
5 Enabled Auto Deasserted Unauthorized
6 Enabled Auto Deasserted Unauthorized
-- Port not available
ML800(auth)## show auth config
802.1X Authenticator Configuration
==================================
Status: Enabled
RADIUS Authentication Server
==================================
IP Address: 3.204.240.1
UDP Port: 1812
Shared Secret: secret

(continued on following page)

7–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS

Setting port control parameters (continued)

ML800(auth)## backend port=2 supptimeout=45 servertimeout=60 maxreq=5

Successfully set backend server authentication
parameter(s) This command sets timeout
characteristics and the number of
ML800(auth)## show-port backend requests before access is denied.
Port Supp Timeout Server Timeout Max Request
(sec.) (sec.)
=============================================== The authenticator waits for the supplicant
1 30 30 2 to respond back for 45 seconds; the
2 45 60 5 authenticator waits for 60 seconds for the
3 30 30 2 back-end RADIUS server to respond back
4 30 30 2 and the authenticator will retransmit an
5 30 30 2 EAP request packet 5 times to the
6 30 30 2 Supplicant before it times out the
authentication session.
ML800(auth)## portaccess port=2 quiet=120 maxreauth=7 transmit=120
Successfully set port access parameter(s)
ML800(auth)## show-port access
Port Quiet Period Max Reauth Tx Period
(sec.) (sec.)
=========================================
1 60 2 30
2 120 7 120
3 60 2 30
4 60 2 30
5 60 2 30
6 60 2 30
(continued on following page)
The time the supplicant is held after an
authentication failure before the authenticator
retries the supplicant for connection is changed to
120 seconds, the number of re-authentication
attempts permitted before the port becomes
Unauthorized is set to 7, and the time the
authenticator waits to transmit another request
for identification from the supplicant is changed
to 120 seconds. These values can be changed on
all ports depending on devices being
authenticated.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–7

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

Setting port control parameters (continued)

ML800(auth)## reauth port=1 status=enable period=300

This command forces the
Successfully set re-authentication parameter(s) authentication period on port #1
every 5 minutes; all other ports are
ML800(auth)## shoW-port reauth
force authenticated every hour as
Port Reauth Status Reauth Period (sec.) indicated by the show-port reauth
========================================= command below.
1 Enabled 300
2 Enabled 3600
3 Enabled 3600
4 Enabled 3600
5 Enabled 3600
6 Enabled 3600

ML800(auth)## show-stats port=3

Port 3 Authentication Counters
authEntersConnecting :3
authEapLogoffsWhileConnecting :0
authEntersAuthenticating :3
authAuthSuccessesWhileAuthenticating : 2
authAuthTimeoutsWhileAuthenticating : 0
authAuthFailWhileAuthenticating :0
authAuthReauthsWhileAuthenticating : 0
authAuthEapStartsWhileAuthenticating : 1
authAuthEapLogoffWhileAuthenticating : 0
authAuthReauthsWhileAuthenticated : 0
authAuthEapStartsWhileAuthenticated : 0
authAuthEapLogoffWhileAuthenticated : 0
backendResponses :5
backendAccessChallenges :2
backendOtherRequestsToSupplicant : 0
backendNonNakResponsesFromSupplicant : 2
backendAuthSuccesses :2
backendAuthFails :0
ML800(auth)## trigger-reauth port=3
Successfully triggered re-authentication
ML800(auth)##

7–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS

7.3 Configuring 802.1x with EnerVista Secure Web

Management software

7.3.1 Commands
To access the 802.1x configuration window, select the Configuration > Radius > Server
menu item.
First, select the server. Do not enable RADIUS capabilities until you have ensured that the
ports are configured properly. After the ports are configured, enable RADIUS. Also ensure
that the port connected to the RADIUS server, or the network where the RADIUS server is
connected to, is not an authenticated port.
The following window shows the configuration of a RADIUS Server. Initially, the RADIUS
Services are disabled and the server IP address is set to 0.0.0.0. Edit the server IP and
secret to add a RADIUS server.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–9

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

The following figure illustrates the editing of information for the RADIUS server. Note the
UDP port number can be left blank and the default port 1812 is used.

After configuring the server information, specific port information is configured.

 Select the Configuration > Radius > Port > Set menu item to
configure the RADIUS characteristics of each port.
 To edit the port settings, click on the edit icon ( ).

Ensure that the port which has the RADIUS server is force authorized and asserted. For
other ports (user ports), it is best to leave the Control on auto and Initialize on de-asserted.

7–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS

To change the port access characteristics when authenticating with a RADIUS server,
 Select the Configuration > Radius > Port > Access menu item.

The Quiet Period column represents the time, in seconds, the supplicant is held after an
authentication failure before the authenticator retries the supplicant for connection. The
value ranges from 0 to 65535 seconds, with a default of 60.
The Max Reauth column shows the permitted reauthentication attempts before the port
becomes unauthorized. Values are integers ranging from 0 to 10, with a default of 2.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–11

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

The Tx Period column represents the transmit period. This is the time (in seconds) the
authenticator waits to transmit another request for identification from the supplicant. The
values range from 1 to 65535 seconds, with a default of 30.
The backend or communication characteristics between the ML800 and the RADIUS Server
are defined through the Configuration > Radius > Port > Access > Backend menu item.

The Supp Timeout column represents the timeout the authenticator waits for the
supplicant to respond. The values range from 1 to 240 seconds, with a default of 30.
The Server Timeout column represents the timeout the authenticator waits for the
backend RADIUS server to respond. The values range from 1 to 240 seconds, with a default
of 30.
The Max Request column represents the maximum times the authenticator retransmits an
EAP request packet to the supplicant before it times out. Values are integers ranging from
1 to 10, with a default of 2.

7–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS

The port authentication characteristics define how the authenticator (ML800 switch) does
the re-authentication with the supplicant or PC. These are defined through the
Configuration > Radius > Port > Access > Reauth menu item.

The Reauth Period represents the time the authenticator waits before a re-authentication
process will be done again to the supplicant. Values range from 10 to 86400 seconds, with
a default of 3600 (1 hour).
The Configuration > Radius > Port > Stats menu item illustrates the radius statistics for
each port.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 7–13

ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS

After all the port characteristics are enabled,

 Do not forget to save the configuration using the save ( ) icon and
enabling RADIUS from the Configuration > Radius > Server menu.

7–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 8: Access using TACACS+

Access using TACACS+

8.1 Introduction to TACACS+

8.1.1 Overview
The TACACS+ protocol (short for Terminal Access Controller Access Control System)
provides access control for routers, network access servers and other networked
computing devices via one or more centralized servers. TACACS+ provides separate
authentication, authorization and accounting services.
TACACS allows a client to accept a username and password and send a query to a TACACS
authentication server, sometimes called a TACACS daemon (server) or simply TACACSD. This
server was normally a program running on a host. The host would determine whether to
accept or deny the request and sent a response back.
The TACACS+ protocol is the latest generation of TACACS. TACACS is a simple UDP based
access control protocol originally developed by BBN for the MILNET (Military Network).
XTACACS is now replaced by TACACS+. TACACS+ is a TCP based access control protocol.
TCP offers a reliable connection-oriented transport, while UDP offers best-effort delivery.
TACACS+ improves on TACACS and XTACACS by separating the functions of authentication,
authorization and accounting and by encrypting all traffic between the Network Access
Server (NAS) and the TACACS+ clients or services or daemon. It allows for arbitrary length
and content authentication exchanges, which allows any authentication mechanism to be
utilized with TACACS+ clients. The protocol allows the TACACS+ client to request very fine-
grained access control by responding to each component of a request.
The MultiLink ML800 Managed Edge Switch implements a TACACS+ client.
1. TACACS+ servers and daemons use TCP port 49 for listening to client requests.
Clients connect to this port to send authentication and authorization packets.
2. There can be more than one TACACS+ server on the network. The MultiLink
Switch Software supports a maximum of five TACACS+ servers.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 8–1

ACCESS USING TACACS+ CHAPTER 8: ACCESS USING TACACS+

8.1.2 TACACS+ Flow

TACACS works in conjunction with the local user list on the ML800 software (operating
system). The process of authentication as well as authorization is shown in the flow chart
below.

Start
Login as Operator

No Login

Yes User in Local

Is User Manager?
User List?

Yes

Logout TACACS+ Enabled?

Yes Yes
Authentication Connection failure
failure Connect to Additional
Logout Additional
TACACS server to Servers?
Servers?
authenticate

Authorized as Authenticated No
Operator or
Authorization failure Logout
TACACS+
Login as Operator
authorization

Authorized as
Manager

FIGURE 8–1: TACACS Authorization Flowchart

The above flow diagram shows the tight integration of TACACS+ authentication with the
local user-based authentication. There are two stages a user goes through in TACACS+. The
first stage is authentication where the user is verified against the network user database.
The second stage is authorization, where it is determined whether the user has operator
access or manager privileges.

8.1.3 TACACS+ Packet

Packet encryption is a supported and is a configurable option for the ML800 software.
When encrypted, all authentication and authorization TACACS+ packets are encrypted and
are not readable by protocol capture and sniffing devices such as EtherReal or others.
Packet data is hashed and shared using MD5 and secret string defined between the
MultiLink ML800 Managed Edge Switch and the TACACS+ server.

8–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+

32 bits wide
4 4 8 8 8 bits
Major Minor Packet type Sequence Flags
Version Version number
Session ID
Length
754717A1.CDR

FIGURE 8–2: TACACS packet format

The portions of the TACACS packet are defined as follows:

• Major Version: The major TACACS+ version number.
• Minor version: The minor TACACS+ version number. This is intended to allow
revisions to the TACACS+ protocol while maintaining backwards compatibility.
• Packet type: Possible values are:
• TAC_PLUS_AUTHEN:= 0x01 (authentication)
TAC_PLUS_AUTHOR:= 0x02 (authorization)
TAC_PLUS_ACCT:= 0x03 (accounting)
• Sequence number: The sequence number of the current packet for the current
session.
• Flags: This field contains various flags in the form of bitmaps. The flag values
signify whether the packet is encrypted.
• Session ID: The ID for this TACACS+ session.
• Length: The total length of the TACACS+ packet body (not including the header).

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 8–3

ACCESS USING TACACS+ CHAPTER 8: ACCESS USING TACACS+

8.2 Configuring TACACS+ through the Command Line

Interface

8.2.1 Commands
There are several commands to configure TACACS+.
The show tacplus command displays the status of TACACS or servers configured as
TACACS+ servers:
show tacplus <status|servers>
The tacplus enable and tacplus disable commands enable or disable TACACS
authentication:
tacplus <enable|disable>
The tacserver command creates a list of up to five TACACS+ servers:
tacserver <add|delete> id=<num>
[ip=<ip-addr>] [port=<tcp-port>] [encrypt=<enable|disable>] [key=<string>]
The <add|delete> argument is mandatory and specifies whether to add or delete a
TACACS+ server. The id argument is mandatory and sets the order to poll the TACACS+
servers for authentication. The ip argument is mandatory for adding and defines the IP
address of the TACACS+ server. The port argument is mandatory for deleting and defines
the TCP port number on which the server is listening. The encrypt argument enables or
disables packet encryption and is mandatory for deleting. The key argument requires the
secret shared key string must be supplied when encryption is enabled.

8.2.2 Example
Example 8-1 below, illustrates how to configure TACACS+.

8–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+

Example 8-1: Configuring TACACS+:

ML800# show tacplus servers

ID TACACS+ Server Port Encrypt Key
=======================================
1 10.21.1.170 1 Enabled secret
2 -- -- -- --
3 -- -- -- --
4 -- -- -- --
5 -- -- -- --
ML800# user
ML800(user)## show tacplus status
TACACS+ Status: Disabled
ML800(user)## tacplus enable
TACACS+ Tunneling is enabled.
ML800(user)## tacserver add id=2 ip=10.21.1.123 encrypt=enable key
TACACS+ server is added.
ML800(user)## show tacplus servers
ID TACACS+ Server Port Encrypt Key
=======================================
1 10.21.1.170 1 Enabled secret
2 10.21.1.123 1 Enabled some
3 -- -- -- --
4 -- -- -- --
5 -- -- -- --
ML800(user)## tacserver delete id=2
TACACS+ server is deleted.
ML800(user)## show tacplus servers
ID TACACS+ Server Port Encrypt Key
=======================================
1 10.21.1.170 1 Enabled secret
2 -- -- -- --
3 -- -- -- --
4 -- -- -- --
5 -- -- -- --
ML800(user)## tacplus disable

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 8–5

ACCESS USING TACACS+ CHAPTER 8: ACCESS USING TACACS+

8.3 Configuring TACACS+ with EnerVista Secure Web

Management software
 To access the TACACS servers, select the Administration > User
Mgmt > TACACS+ menu item.
By default, no TACACS servers are defined.

 To add a server, click on the Add button as shown below.

8–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+

Note that the TCP port field can be left blank – port 49 is used as a default port. Up to five
TACACS+ servers can be defined.
After the configuration is completed,
 Save the settings.
 Enable the TACACS+ services by using the Status drop down menu..

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 8–7

ACCESS USING TACACS+ CHAPTER 8: ACCESS USING TACACS+

8–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 9: Port Mirroring and

Port Mirroring and Setup

9.1 Port Mirroring

9.1.1 Description
This section explains how individual characteristics of a port on a MultiLink ML800
Managed Edge Switch is configured. For monitoring a specific port, the traffic on a port
can be mirrored on another port and viewed by protocol analyzers. Other setup includes
automatically setting up broadcast storm prevention thresholds.
An Ethernet switch sends traffic from one port to another port. Unlike a switch, a hub or a
shared network device, the traffic is “broadcast” on each and every port. Capturing traffic
for protocol analysis or intrusion analysis can be impossible on a switch unless all the
traffic from a specific port is “reflected” on another port, typically a monitoring port. The
MultiLink ML800 Managed Edge Switch can be instructed to repeat the traffic from one
port onto another port. This process - when traffic from one port is reflecting to another
port - is called port mirroring. The monitoring port is also called a “sniffing” port. Port
monitoring becomes critical for trouble shooting as well as for intrusion detection.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–1

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

9.2 Port Mirroring using the Command Line Interface

9.2.1 Commands
Monitoring a specific port can be done by port mirroring. Mirroring traffic from one port to
another port allows analysis of the traffic on that port.
The show port-mirror command displays the status of port mirroring:
show port-mirror
The port-mirror command enters the port mirror configuration mode.
port-mirror
The setport monitor command configures a port mirror.
setport monitor=<monitor port number> sniffer=<sniffer port number>
The prtmr command enables and disables port mirroring.
prtmr <enable|disable>
The sequence below illustrates how port 1 is mirrored on port 2. Any traffic on port 1 is also
sent on port 2.
ML800# show port-mirror
Sniffer Port: 0
Monitor Port: 0
Mirroring State: disabled
ML800# port-mirror
ML800(port-mirror)## setport monitor=1 sniffer=2
Port 1 set as Monitor Port
Port 2 set as Sniffer Port
ML800(port-mirror)## prtmr enable
Port Mirroring Enabled
ML800(port-mirror)## exit
ML800# show port-mirror
Sniffer Port: 2
Monitor Port: 1
Mirroring State: enabled
ML800#
Once port monitoring is completed, GE strongly recommends that the port mirroring be
disabled using the prtmr disable command for security reasons.
1. Only one port can be set to port mirror at a time.
2. Both the ports (monitored port and mirrored port) have to belong to the same
VLAN
3. The mirrored port shows both incoming as well as outgoing traffic

9–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

9.3 Port Setup

9.3.1 Commands
Each port on the MultiLink ML800 Managed Edge Switch can be setup specific port
characteristics. The commands for setting the port characteristics are shown below.
The device command enters the device configuration mode:
device
The setport command configures the port characteristics:
setport port=<port#|list|range> [name=<name>] [speed=<10|100>] [duplex=<half|full>]
[auto=<enable|disable>] [flow=<enable|disable>] [bp=<enable|disable>]
[status=<enable|disable>] [lla=<enable|disable>]
The arguments for the setport command are defined as follows:
• The device argument sets up the MultiLink ML800 Managed Edge Switch in the
device configuration mode.
• The name argument assigns a specific name to the port. This name is a designated
name for the port and can be a server name, user name or any other name.
• The speed argument sets the speed to be 10 or 100 Mbps. This works only with 10/
100 ports; the value is ignored and no error shown for 10 Mbps ports.
• The flow argument sets up flow control on the port.
• The bp argument enables back pressure signaling for traffic congestion
management.
• The status argument enabled/disables port operation
The show port command displays information about a specific port number.
show port[=<port number>]

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–3

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

In Example 9-1, ports 3 and 4 are given specific names. Ports 1 and 5 are active, as shown
by the link status. Port 5 is set to 100 Mbps, and all other ports are set to 10 Mbps. All ports
are set to auto sensing (speed).
The port speed and duplex (data transfer operation) settings are summarized below.
The speed setting defaults to auto and senses speed and negotiates with the port at the
other end of the link for data transfer operation (half-duplex or full-duplex). The “auto”
speed detection uses the IEEE 802.3u auto negotiation standard for 100Base-T networks. If
the other device does not comply with the 802.3u standard, then the port configuration on
the switch must be manually set to match the port configuration on the other device.
Possible port setting combinations for copper ports are:
• 10HDx: 10 Mbps, half-duplex
• 10FDx: 10 Mbps, full-duplex
• 100HDx: 100 Mbps, half-duplex
• 100FDx: 100 Mbps, full-duplex
Possible port settings for 100FX (fiber) ports are:
• 100FDx (default): 100 Mbps, full-duplex
• 100HDx: 100 Mbps, half-duplex

To change the port speed on a transceiver port, it is required to reboot the switch.
Note

NOTE

Example 9-1: Port setup

ML800# device
ML800(device)## setport port=3 name=JohnDoe
ML800(device)## setport port=4 name=JaneDoe
ML800(device)## show port
Keys: E = Enable D = Disable
H = Half Duplex F = Full Duplex
M = Multiple VLAN's NA = Not Applicable
LI = Listening LE = Learning
F = Forwarding B = Blocking
Port Name Control Dplx Media Link Speed Part Auto VlanID GVRP STP
-------------------------------------------------------------------------------
1 A1 E H 10Tx UP 10 No E 1 - -
2 A2 E H 10Tx DOWN 10 No E 1 - -
3 JohnDoe E H 10Tx DOWN 10 No E 1 - -
4 JaneDoe E H 10Tx DOWN 10 No E 1 - -
5 A5 E F 100Tx UP 100 No E 1 - -
6 A6 E H 10Tx DOWN 10 No E 1 - -
7 A7 E H 10Tx DOWN 10 No E 1 - -

9–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

9.3.2 Flow Control

The flow setting is disabled by default. In this case, the port will not generate flow control
packets and drops received flow control packets. If the flow setting is enabled, the port
uses 802.3x Link Layer Flow Control, generates flow control packets, and processes
received flow control packets.

With the port speed set to auto (the default) and flow control set to enabled; the switch
Note

negotiates flow control on the indicated port. If the port speed is not set to auto, or if flow
NOTE control is disabled on the port, then flow control is not used.
Use the flowcontrol command to set flow control:
flowcontrol xonlimit=<value> xofflimit=<value>
where xonlimit can be from 3 to 127 (default value is 4) and xofflimit ranges from 3 to
127 (default value is 6).

9.3.3 Back Pressure

The backpressure command disables/enables back pressure based flow control
mechanisms. The default state is disabled. When enabled, the port uses 802.3 Layer 2 back
off algorithms. Back pressure based congestion control is possible only on half-duplex, 10-
Mbps Ethernet ports. Other technologies are not supported on the MultiLink ML800
Managed Edge Switch.
backpressure rxthreshold=<value>
where the rxthreshold value can be from 4 to 30 (default is 28).
Back pressure and flow control are used in networks where all devices and switches can
participate in the flow control and back pressure recognition. In most networks, these
techniques are not used as not all devices can participate in the flow control methods and
notifications. Alternately, QoS and other techniques are widely used today.
In the example below, the MultiLink ML800 Managed Edge Switch is set up with flow
control and back pressure.

Example 9-2: Back pressure and flow control

ML800# device
ML800(device)## show flowcontrol
XOnLimit : 4
XOffLimit : 6
ML800(device)## flowcontrol xonlimit=10 xofflimit=15
XOn Limit set successfully
XOff Limit set successfully
ML800(device)## show flowcontrol
XOnLimit : 10
XOffLimit : 15
ML800(device)## show backpressure
Rx Buffer Threshold : 28

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–5

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

Back pressure and flow control (continued)

ML800(device)## backpressure rxthreshold=30

Rx Buffer Threshold set successfully
ML800(device)## show backpressure
Rx Buffer Threshold : 30
ML800(device)## show port
Keys: E = Enable D = Disable
H = Half Duplex F = Full Duplex
M = Multiple VLAN's NA = Not Applicable
LI = Listening LE = Learning
F = Forwarding B = Blocking
Port Name Control Dplx Media Link Speed Part Auto VlanID GVRP STP
-------------------------------------------------------------------------------
1 B1 E H 10Tx UP 10 No E 1 - -
2 B2 E H 10Tx DOWN 10 No E 1 - -
3 JohnDoe E H 10Tx DOWN 10 No E 1 - -
4 JaneDoe E H 10Tx DOWN 10 No E 1 - -
5 B5 E F 100Tx UP 100 No E 1 - -
6 B6 E H 10Tx DOWN 10 No E 1 - -

ML800(device)## show port=11

Configuration details of port 11
--------------------------------------------------
Port Name : JohnDoe
Port Link State : DOWN
Port Type : TP Port
Port Admin State : Enable
Port VLAN ID :1
Port Speed : 10Mbps
Port Duplex Mode : half-duplex
Port Auto-negotiation State : Enable
Port STP State : NO STP
Port GVRP State : No GVRP
Port Priority Type : None
Port Security : Enable
Port Flow Control : Disable
Port Back Pressure : Disable
Port Link Loss Alert : Enabled
ML800(device)## setport port=11 flow=enable bp=enable

(continued on next page)

9–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

Back pressure and flow control (continued)

ML800(device)## show port

Keys: E = Enable D = Disable
H = Half Duplex F = Full Duplex
M = Multiple VLAN's NA = Not Applicable
LI = Listening LE = Learning
F = Forwarding B = Blocking
Port Name Control Dplx Media Link Speed Part Auto VlanID GVRP STP
-------------------------------------------------------------------------------
1 B1 E H 10Tx UP 10 No E 1 - -
2 B2 E H 10Tx DOWN 10 No E 1 - -
3 JohnDoe E H 10Tx DOWN 10 No E 1 - -
4 JaneDoe E H 10Tx DOWN 10 No E 1 - -
5 B5 E F 100Tx UP 100 No E 1 - -
6 B6 E H 10Tx DOWN 10 No E 1 - -

ML800(device)## show port=11

Configuration details of port 11 Note that the flow control and back pressure is
-------------------------------------------------- shown as enabled for the specific port. The global
show port command does not provide this detail.
Port Name : JohnDoe
The back pressure and flow control parameters
Port Link State : DOWN
are global – i.e., the same for all ports.
Port Type : TP Port
Port Admin State : Enable
Port VLAN ID :1
Port Speed : 10Mbps
Port Duplex Mode : half-duplex
Port Auto-negotiation State : Enable
Port STP State : NO STP
Port GVRP State : No GVRP
Port Priority Type : None
Port Security : Enable
Port Flow Control : Enable

9.3.4 Broadcast Storms

One of the best features of the MultiLink ML800 Managed Edge Switch is its ability to keep
broadcast storms from spreading throughout a network. Network storms (or broadcast
storms) are characterized by an excessive number of broadcast packets being sent over
the network. These storms can occur if network equipment is configured incorrectly.
Storms can reduce network performance and cause bridges, routers, workstations, servers
and PCs to slow down or even crash.
The MultiLink ML800 Managed Edge Switch is capable of detecting and limiting storms on
each port. A network administrator can also set the maximum rate of broadcast packets
(frames) that are permitted from a particular interface. If the maximum number is
exceeded, a storm condition is declared. Once it is determined that a storm is occurring on
an interface, any additional broadcast packets received on that interface will be dropped
until the storm is determined to be over. The storm is determined to be over when a one-
second period elapses with no broadcast packets received.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–7

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

The braoadcast-protect command enables or disables the broadcast storm

protection capabilities.
broadcast-protect <enable|disable>
The rate-threshold command set the rate limit in frames per second.
rate-threshold port=<port|list|range> rate=<frames/sec>
The show broadcast-protect command displays the broadcast storm protection
settings
show broadcast-protect
In Example 9-3, the broadcast protection is turned on. The threshold for port 11 is then set
to a lower value of 3500 broadcast frames/second.

9–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

Example 9-3: Preventing broadcast storms

ML800# device
ML800(device)## show broadcast-protect
===================================================================
PORT | STATUS | THRESHOLD (frms/sec) | CURR RATE (frms/sec) | ACTIVE
===================================================================
1 Disabled 19531 0 NO
2 Disabled 19531 0 NO
3 Disabled 19531 0 NO
4 Disabled 19531 0 NO
5 Disabled 19531 0 NO
6 Disabled 19531 0 NO

ML800(device)## broadcast-protect enable

Broadcast Storm Protection enabled
ML800(device)## show broadcast-protect
===================================================================
PORT | STATUS | THRESHOLD (frms/sec) | CURR RATE (frms/sec) | ACTIVE
===================================================================
1 Enabled 19531 0 NO
2 Enabled 19531 0 NO
3 Enabled 19531 0 NO
4 Enabled 19531 0 NO
5 Enabled 19531 0 NO
6 Enabled 19531 0 NO

ML800(device)## rate-threshold port=11 rate=3500

Broadcast Rate Threshold set
ML800(device)## show broadcast-protect
===================================================================
PORT | STATUS | THRESHOLD (frms/sec) | CURR RATE (frms/sec) | ACTIVE
===================================================================
1 Enabled 19531 0 NO
2 Enabled 19531 0 NO
3 Enabled 3500 0 NO
4 Enabled 19531 0 NO
5 Enabled 19531 0 NO
6 Enabled 19531 0 NO

9.3.5 Link Loss Alert

The GE Digital Energy Universal Relay (UR) family and the F650 family of relays have
redundant Ethernet ports that allow for automatic switching to their secondary ports
when they detect the primary path is broken. The MultiLink ML800 Managed Edge Switch
can compensate for situations where only the switch receiver fiber cable is broken. Upon
detection of the broken receiver link, the ML800 will cease sending link pulses through the
relay’s receive fiber cable, thereby allowing the relay to switch to its secondary path.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–9

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

It is recommended to enable the Link Loss Alert (LLA) feature on ports that are connected
to end devices. LLA should be disabled for switch ports connected in a ring.
The Link Loss Alert feature is disabled by default on 100 MB Fiber Optic ports. It can be
enabled and disabled via the lla parameter in the setport command as follows:
setport port=<port#|list|range> [lla=<enable|disable>]
The following example illustrates how to enable the link loss alert feature.

9–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

9.4 Port Mirroring using EnerVista Secure Web

Management software

9.4.1 Commands
Monitoring a specific port can be done by port mirroring. Mirroring traffic from one port to
another port allows analysis of the traffic on that port.
To enable port mirroring as well as setting up the ports to be “sniffed”,
 Select the Configuration > Port > Mirroring menu item.

 Set the sniffer port and the port on which the traffic is reflected.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–11

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

 Make sure the Mirror Status is also set to enabled for mirroring:

For security reasons, GE Digital Energy recommends that the port mirroring be disabled
using the Edit button and setting the Mirror Status to off once port monitoring is
completed.
Note that:
1. Only one port can be set to port mirror at a time.
2. Both the ports (monitored port and mirrored port) have to belong to the same
VLAN.
3. The mirrored port shows both incoming as well as outgoing traffic.

9.4.2 Port Setup

With the ML800, the specific characteristics of each port can be individually programmed.

9–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

 Select a specific port by using the edit icon in the Configuration >
Port > Settings menu.

 Click the edit icon to open the following window.

In these windows:
• Port Number represents the port number on the switch.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–13

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

• Port Name assigns a specific name to the port. This name is a designated name
for the port and can be a server name, user name or any other name.
• Admin Status indicates whether the port can be administered remotely.
• Link indicates the link status. In the figure above the link is down, implying either
there is no connection or the system connected to the port is turned off.
• Auto-Neg sets auto negotiation for 100 Mbps and Gigabit copper ports. There is no
no auto negotiation for fiber ports as their speeds are fixed.
• The Port Speed sets the speed to be 10 or 100 Mbps. This settings works only with
10/100 ports; it is ignored for 10 Mbps ports.
• The Duplex setting selects full duplex or half duplex capabilities for 10/100 Mbps
ports.
• The Back Pressure displays the state of the back pressure setting on the port. This
value can be edited in this window.
• The Flow Control displays the state of the flow control setting on the port. This
value can be edited in this window.
• Priority displays the priority set for the port. This value cannot be edited in this
window.
• The VLAN ID displays the VLAN set for the port. This value cannot be edited in this
window.
• The STP State displays the STP settings for the port. This value cannot be edited in
this window.
• The Tagged State displays the Tag settings on the port. This value cannot be
edited in this window.
• The GVRP State displays the GVRP settings on the port. This value cannot be edited
in this window.
• The LLA indicates the state of the Link Loss Alert feature.
The “Auto” (default) value for the Port Speed senses the speed and negotiates with the port
at the other end of the link for data transfer operation (half-duplex or full-duplex). The
“Auto” value uses the IEEE 802.3u auto negotiation standard for 100Base-T networks. If the
other device does not comply with the 802.3u standard, then the port configuration on the
switch must be manually set to match the port configuration on the other device.
Possible port setting combinations for copper ports are:
• 10HDx: 10 Mbps, half-duplex
• 10FDx: 10 Mbps, full-duplex
• 100HDx: 100 Mbps, half-duplex
• 100FDx: 100 Mbps, full-duplex
Possible port settings for 100FX (fiber) ports are:
• 100FDx (default): 100 Mbps, full-duplex
• 100HDx: 100 Mbps, half-duplex
To change the port speed on a transceiver port, the switch must be rebooted

9–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP

9.4.3 Broadcast Storms

One of the best features of the MultiLink ML800 Managed Edge Switch is its ability to keep
broadcast storms from spreading throughout a network. Network storms (or broadcast
storms) are characterized by an excessive number of broadcast packets being sent over
the network. These storms can occur if network equipment is configured incorrectly or the
network software is not properly functioning or badly designed programs (including some
network games) are used. Storms can reduce network performance and cause bridges,
routers, workstations, servers and PCs to slow down or even crash.
The ML800 Switch is capable of detecting and limiting storms on each port. A network
administrator can also set the maximum rate of broadcast packets (frames) that are
permitted from a particular interface. If the maximum number is exceeded, a storm
condition is declared. Once it is determined that a storm is occurring on an interface, any
additional broadcast packets received on that interface will be dropped until the storm is
determined to be over. The storm is determined to be over when a one-second period
elapses with no broadcast packets received.
Broadcast storm protection can be configured through the Configuration > Port >
Broadcast Storm menu.

 To edit the threshold level, click on the edit icon as seen below.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 9–15

PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP

See details in Broadcast Storms on page 9–7 to determine the threshold level.

 After changes are made, do not forget to save the changes using
the save icon ( ).
If the switch is rebooted before the changes are made, the changes
will be lost.

9–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 10: VLAN

VLAN

10.1 VLAN Description

10.1.1 Overview
Short for virtual LAN (VLAN), a VLAN creates separate broadcast domains or network
segments that can span multiple MultiLink ML800 Managed Edge Switchs. A VLAN is a
group of ports designated by the switch as belonging to the same broadcast domain. The
IEEE 802.1Q specification establishes a standard method for inserting VLAN membership
information into Ethernet frames.
VLANs provide the capability of having two (or more) Ethernet segments co-exist on
common hardware. The reason for creating multiple segments in Ethernet is to isolate
broadcast domains. VLANs can isolate groups of users, or divide up traffic for security,
bandwidth management, etc. VLANs are widely used today and are here to stay. VLANs
need not be in one physical location. They can be spread across geography or topology.
VLAN membership information can be propagated across multiple MultiLink ML800
Managed Edge Switchs.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–1

VLAN CHAPTER 10: VLAN

The following figure illustrates a VLAN as two separate broadcast domains. The top part of
the figure shows two “traditional” Ethernet segments. Up to 32 VLANs can be defined per
switch.

SEGMENT 1 SEGMENT 2

CONSOLE

POWER

VLAN 1 VLAN 2
FIGURE 10–1: VLAN as two separate broadcast domains

A group of network users (ports) assigned to a VLAN form a broadcast domain. Packets are
forwarded only between ports that are designated for the same VLAN. Cross-domain
broadcast traffic in the switch is eliminated and bandwidth is saved by not allowing
packets to flood out on all ports. For many reasons a port may be configured to belong to
multiple VLANs.
As shown below, ports can belong to multiple VLANs. In this figure, a simplistic view is
presented where some ports belong to VLANs 1, 2 and other ports belong to VLANs 2,3.
Ports can belong to VLANs 1, 2 and 3. This is not shown in the figure.

SEGMENT 1 SEGMENT 3
SEGMENT 2

CONSOLE

POWER

VLAN 1 VLAN 2 VLAN 3

FIGURE 10–2: Ports assigned to multiple VLANs

By default, on the MultiLink ML800 Managed Edge Switch, VLAN support is enabled and all
ports on the switch belong to the default VLAN (DEFAULT-VLAN). This places all ports on the
switch into one physical broadcast domain.
If VLANs are entirely separate segments or traffic domains - how can the VLANs route
traffic (or “talk”) to each other? This can be done using routing technologies (e.g., a router
or a L3-switch). The routing function can be done internally to a L3-switch. One advantage

10–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

of an L3 switch is that the switch can also support multiple VLANs. The L3 switch can thus
route traffic across multiple VLANs easily and provides a cost effective solution if there are
many VLANs defined.
As shown below, routing between different VLANs is performed using a router or a Layer 3
switch (L3-switch)

SEGMENT 1 SEGMENT 2

ROUTER

ROUTER or L3 SWITCH

CONSOLE

POWER

VLAN 1 VLAN 2
FIGURE 10–3: VLAN routing

The Multilink ML800 supports up to 32 VLANs per switch

10.1.2 Tag VLAN vs. Port VLAN

What is the difference between tag and port VLAN? In a nutshell - port VLAN sets a specific
port or group of ports to belong to a VLAN. Port VLANs do not look for VLAN identifier (VID)
information nor does it manipulate the VID information. It thus works “transparently” and
propagates the VLAN information along.
In the tag VLAN, an identifier called the VLAN identifier (VID) is either inserted or
manipulated. This manipulated VLAN tag allows VLAN information to be propagated
across devices or switches, allowing VLAN information to span multiple switches.
As described earlier, VLAN is an administratively configured LAN or broadcast domain.
Instead of going to the wiring closet to move a cable to a different LAN segment, the same
task can be accomplished remotely by configuring a port on an 802.1Q-compliant switch
to belong to a different VLAN. The ability to move end stations to different broadcast
domains by setting membership profiles for each port on centrally managed switches is
one of the main advantages of 802.1Q VLANs.
802.1Q VLANs aren't limited to one switch. VLANs can span many switches. Sharing VLANs
between switches is achieved by inserting a tag with a VLAN identifier (VID) into each
frame. A VID must be assigned for each VLAN. By assigning the same VID to VLANs on
many switches, one or more VLAN (broadcast domain) can be extended across a large
network.
802.1Q-compliant switch ports, such as those on the MultiLink ML800 Managed Edge
Switch, can be configured to transmit tagged or untagged frames. A tag field containing
VLAN information can be inserted into an Ethernet frame. If a port has an 802.1Q-

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–3

VLAN CHAPTER 10: VLAN

compliant device attached (such as another switch), these tagged frames can carry VLAN
membership information between switches, thus letting a VLAN span multiple switches.
Normally connections between switches can carry multiple VLAN information and this is
called port trunking or 802.1Q trunks.
There is one important caveat: administrators must ensure ports with non-802.1Q-
compliant devices attached are configured to transmit untagged frames. Many network
interface cards such as those for PCs printers and other “dumb” switches are not 802.1Q-
compliant. If they receive a tagged frame, they will not understand the VLAN tag and will
drop the frame. In situations like these, its best to use port based VLANs for connecting to
these devices.
Sometimes a port may want to listen to broadcasts across different VLANs or propagate
the VLAN information on to other ports. This port must thus belong to multiple VLANs so
that the broadcast information reaches the port accurately. If the port also wants to send
broadcast traffic, the proper leave (sending out of information) and join rules (receiving
information) have to be configured on the MultiLink ML800 Managed Edge Switch.
It is recommended to use IEEE 802.1q tagged based VLANs over port based VLANs
because of there multi-vendor interoperability and capability of carrying the isolated
tagged VLAN information when more than one switch is involved.

10–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

10.2 Configuring Port VLANs through the Command Line

Interface

10.2.1 Description
Port VLANs are rarely used, and are not recommended, in networks which use VLANs
across multiple switches. Port VLANs are used when VLANs are setup up on a single switch
and connectivity between the system on different VLANs is needed however the
broadcasts and multicasts are isolated to the specific VLAN.
GE recommends using the set-port command for setting the port based VLAN as well.
The port-based VLAN feature supports a maximum of 1 VLAN per port. Any pre-existing
VLAN tags on traffic coming into the switch on a port-based VLAN port will be removed.
General steps for using port VLANs are
1. Plan your VLAN strategy and create a map of the logical topology that will
result from configuring VLANs. Include consideration for the interaction
between VLANs.
2. Configure at least one VLAN in addition to the default VLAN
3. Assign the desired ports to the VLANs
4. Decide on trunking strategy - how will the VLAN information be propagated
from one switch to another and also what VLAN information will be
propagated across
5. (Layer 3 consideration) check to see if the routing between the VLANs is
“working” by pinging stations on different VLANs

You can rename the default VLAN, but you cannot change its VID (1) or delete it from the
Note

switch
NOTE

Any ports not specifically assigned to another VLAN will remain assigned to the DEFAULT-
Note

VLAN
NOTE

Changing the number of VLANs supported on the switch requires the SAVE command to
Note

save the new VLAN information

NOTE

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–5

VLAN CHAPTER 10: VLAN

To save VLAN configuration:

save
To edit VLANs:
edit id=<vlan Id> [name=<vlan name>] port=<number|list|range>
To display the VLAN information:
show vlan type=<port|tag> [<id=vlanid>]
The following command sequence shows how to configure VLANs on a MultiLink ML800
Managed Edge Switch.
ML800# vlan type=port
ML800(port-vlan)## add id=2 name=test port=1-7
ML800(port-vlan)## start vlan=all
ML800(port-vlan)## save
Saving current configuration...
Configuration saved
To move Management Control on any VLAN:
add id=<vlan Id> [name=<vlan name>] port=<number|list|range>
[Forbid=<number|list|range>][<mgt|nomgt>]
To enable or disable Management Control on any VLAN:
edit id=<vlan Id>[name=<vlan name>][port=<number|list|range>[<mgt|nomgt>]

10–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

10.3 Configuring Port VLANs with EnerVista Secure Web

Management software

10.3.1 Description
Port VLANs are rarely used, and are not recommended, in networks which use VLANs
across multiple switches. Port VLANs are used when VLANs are setup up on a single switch
and connectivity between the systems on different VLANs is needed; however, the
broadcasts and multicasts are isolated to the specific VLAN.
Either port VLANs or Tag VLAN can be active at any given time on a switch. Only the default
VLAN (VLAN ID = 1) is active as a Tag VLAN as well as a port VLAN.
General steps for using port VLANs are
1. Plan your VLAN strategy and create a map of the logical topology that will
result from configuring VLANs. Include consideration for the interaction
between VLANs.
2. Configure at least one VLAN in addition to the default VLAN.
3. Assign the desired ports to the VLANs
4. Decide on trunking strategy – how will the VLAN information be propagated
from one switch to another and also what VLAN information will be
propagated across.
5. Layer 3 consideration – check to see if the routing between the VLANs is
“working” by pinging stations on different VLANs

You can rename the default VLAN, but you cannot change its VID =1 or delete it from the
Note

switch.
NOTE

Any ports not specifically assigned to another VLAN will remain assigned to the DEFAULT-
Note

VLAN (VID=1).
NOTE

Changing the number of VLANs supported on the switch requires the changes to be saved
Note

for future use. To eliminate the changes, reboot the switch without saving the changes.
NOTE

For VLAN configuration use Configuration > VLAN menu items as shown below. The Port
VLANs are active by default.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–7

VLAN CHAPTER 10: VLAN

The currently assigned Port VLANs are displayed as follows:

 Select the Configuration > VLAN > Port-Based menu item.

10–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

As discussed above, ports 1, 2, 3, 5, 6, 7, and 8 still belong to default VLAN. We will now add
another VLAN with VID=40 and VLAN name = Support.

 Add the ports.

 Define the VLAN.
 Click OK..

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–9

VLAN CHAPTER 10: VLAN

After adding the VLAN, the VLAN is not active. Activating the VLAN has to be done
manually.
 To activate the VLAN, click on the Status button.
 Select VLAN ID.
 Select VLAN Status: Start .

A specific VLAN can be activated or all VLANs can be activated (or disabled).
 Click OK to activate VLAN..

10–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

After activation, note that ports 1 to 3 belong to the new VLAN. The VLAN membership of
the ports assigned to VLAN 40 now indicates that they are only members of VLAN 40. The
default VLAN membership has been terminated on VLAN activation.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–11

VLAN CHAPTER 10: VLAN

10.4 Configuring Tag VLANs through the Command Line

Interface

10.4.1 Description
The VLAN information needs to be propagated on to other switches when multiple
switches are connected on a network. In these situations it is best to use tag-based VLANs.

10.4.2 Commands
The set-port command for setting Tag VLANs has the following parameters. The
default id parameter sets the default VLAN id (termed PVID in previous versions). The
default VLAN id is the VLAN id assigned to the untagged packets received on that port. For
the MultiLink ML800 Managed Edge Switch, the default VLAN id is 1
set-port port=<number|list|range>
default id=<number>
The filter parameter enables or disables the VLAN filtering function. When enabled, the
switch will drop the packets coming in through a port if the port is not a member of the
VLAN. For example, if port 1 is a member of VLANs 10, 20 and 30, if a packet with VLAN id
40 arrives at port 1 it will be dropped.
set-port port=<number|list|range>
filter status=<enable|disable>
The tagging id and status parameters define whether the outgoing packets from a port
will be tagged or untagged. This definition is on a per VLAN basis. For example, the
command set-port port=1 tagging id=10 status=tagged will instruct the
switch to tag all packets going out of port 1 to belong to VLAN 10.
set-port port=<number|list|range>
tagging id=<number> status=<tagged|untagged>
The join id parameter adds the specified port(s) to the specified VLAN id. This parameter
works with active or pending VLANs.
set-port port=<number|list|range>
join id=<number>
The leave id parameter releases a specific port from a VLAN. For example if port 1
belongs to VLAN 10, 20, 30, 40 the command set-port port=1 leave id=40 makes port 1
belong to VLAN 10, 20, 30, dropping VLAN 40.
set-port port=<number|list|range>
leave id=<number>
The show-port command lists all parameters related to tag VLAN for the list of ports. If
the port parameter is omitted, it will display all ports.
show-port [port=<port|list|range>]
To move Management Control on any VLAN:
add id=<vlan Id> [name=<vlan name>] port=<number|list|range>
[Forbid=<number|list|range>][<mgt|nomgt>]
To enable or disable Management Control on any VLAN:
edit id=<vlan Id>[name=<vlan name>][port=<number|list|range>[<mgt|nomgt>]

10–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

10.4.3 Example
In the following example, we start with Port VLAN and convert to TAG VLAN. We define
ports 3 through 5 to belong to VLANs 10, 20 and 30 and the rest of the ports belong to the
default VLAN (in this case, VLAN 1). Filtering is enabled on ports 3 to 5. The VLAN setup is
done before devices are plugged into ports 3 to 5 as a result the status of the ports show
the port status as DOWN.
1. A word of caution - when Tag VLAN filtering is enabled, there can be serious
connectivity repercussions - the only way to recover from that it is to reload
the switch without saving the configuration or by modifying the configuration
from the console (serial) port.
2. There can be either Tag VLAN or Port VLAN. Both VLANs cannot co-exit at the
same time.
3. There can only be one default VLAN for the switch. The default is set to VLAN 1
and can be changed to another VLAN. A word of caution on changing the
default VLAN as well - there can be repercussions on management as well as
multicast and other issues.
4. Tag VLAN support VLAN ids from 1 to 4096. VLAN ids more than 2048 are
reserved for specific purposes and it is recommended they not be used.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–13

VLAN CHAPTER 10: VLAN

10–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

Converting Port VLAN to Tag VLAN (continued)

VLAN ID: 1
Name : Default VLAN
Status : Active
-----------------------------------------------
PORT | MODE | STATUS
----------------------------------------------- Note that ports 3 to 5 are “DOWN” - the
1| UNTAGGED | UP VLAN configuration is preferably done
2| UNTAGGED | DOWN before devices are plugged in to avoid
3| UNTAGGED | DOWN connectivity repercussions.
4| UNTAGGED | DOWN
5| UNTAGGED | DOWN
6| UNTAGGED | DOWN
7| UNTAGGED | UP
ML800#vlan type=tag
ML800(tag-vlan)##add id=10 name=mkt port=3-5
Tag based vlan Added Successfully.
Vlan id :10
Vlan name : engineering
Ports :3-5
ML800(tag-vlan)##edit id=10 name=engineering port=3-5
Tag based vlan edited Successfully.
Vlan id : 10
Vlan name : engineering
Ports : 3-5
ML800(tag-vlan)##add id=20 name=sales port=3-5

Tag based vlan Added Successfully. Intentionally executed to

show the effect of adding a
Vlan id :20 duplicate VLAN.
Vlan name : sales
Ports :3-5
ML800(tag-vlan)##add id=20 name=marketing port=3-5
ERROR: Duplicate Vlan Id
ML800(tag-vlan)##add id=30 name=marketing port=3-5
Tag based vlan Added Successfully.
Vlan id :30
Vlan name : marketing
Ports :3-5
ML800(tag-vlan)##show vlan type=tag
(continued on next page)

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–15

VLAN CHAPTER 10: VLAN

Converting Port VLAN to Tag VLAN (continued)

10–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

Converting Port VLAN to Tag VLAN (continued)

VLAN ID: 20
Name : sales
Status : Active
-----------------------------------------------
PORT | MODE | STATUS
-----------------------------------------------
3| UNTAGGED | DOWN
4| UNTAGGED | DOWN
5| UNTAGGED | DOWN
VLAN ID: 30
Name : marketing
Status : Active
-----------------------------------------------
PORT | MODE | STATUS VLANs are now active. However, as the
----------------------------------------------- packet traverses VLANs, the packet should
3| UNTAGGED | DOWN be tagged. This is enabled next.
4| UNTAGGED | DOWN
5| UNTAGGED | DOWN
ML800(tag-vlan)##set-port port=3-5 tagging id=10 status=tagged
Port tagging enabled
ML800(tag-vlan)##set-port port=3-5 tagging id=20 status=tagged
Port tagging enabled
ML800(tag-vlan)##set-port port=3-5 tagging id=30 status=tagged
Port tagging enabled
ML800(tag-vlan)##show vlan type=tag
VLAN ID: 1
Name : Default VLAN
Status : Active

(continued on next page)

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–17

VLAN CHAPTER 10: VLAN

Converting Port VLAN to Tag VLAN (continued)

10–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

10.5 Configuring Tag VLANs with EnerVista Secure Web

Management software

10.5.1 Description
When multiple switches are on a network, the VLAN information needs to be propagated
on to other switches. In such situations, it is best to use tag based VLANs.
On the ML800, the port VLAN type is set to none. To use Tag VLANs, first enable Tag VLANs.
In the following example, we assign various ports as VLANs 10, 20 and 30 and the
remaining ports to the default VLAN (that is, VLAN 1).
The VLAN setup occurs before devices are connected to the ports. As such, the port status
is shown as DOWN.

There can be serious connectivity repercussions when Tag VLAN filtering is enabled. The
only way to recover from this it is to reload the switch without saving the configuration or
by modifying the configuration from the console (serial) port.
The ML800 can be configured for either Tag VLAN or Port VLAN. Both VLANs cannot co-exit
at the same time. There can only be one default VLAN for the switch. The default is set to
VLAN 1 and can be changed to another VLAN.

There can be repercussions on management as well as multicast and other issues when
changing the default VLAN.
Tag VLAN supports VLAN IDs from 1 to 4096. VLAN IDs greater than 2048 are reserved for
specific purposes. As such, it is recommended they not be used.
To use the Tag VLAN, first
 Set the VLAN type to Tag in the Configuration > VLAN > Set Type
menu.

The next step is to define the VLANs needed. To do that,

 Click On Configuration >vlan >tag-based Menu.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–19

VLAN CHAPTER 10: VLAN

 Click on the Add button..

 Now add the necessary VLANs.

In the example below, add the VLANs in the following manner
• VLAN 1, All ports - default VLAN
• VLAN 10, Engineering VLAN - ports 2, 3, 4
• VLAN 20, Support VLAN - ports 4, 5 (note that port 4 belongs to
VLAN 10, 20)
• VLAN 30, Marketing VLAN - ports 5, 6 (note that port 5 belongs to
VLAN 20, 30)

10–20 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

 After adding the ports and defining the VLAN, click OK.
 Click on Port Settings in the Configuration >VLAN >Tag-Based
menu and enable the tagging for each port..

 Repeat the last two steps for each of the ports and each of the
VLANs (click on port settings and enable the tag on the port.)
After all the ports are tagged, the tagged column should change to
“Yes” for all VLANs
To check the status of the tagging,

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–21

VLAN CHAPTER 10: VLAN

 Select the Configuration > VLAN > Tag-Based > Tagging menu.
.

To activate the VLAN,

 Click on the Status button under the Configuration >VLAN >Tag-
Based > Settings menu.
 Click OK.

10–22 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 10: VLAN VLAN

Tagged VLANs can be viewed from the Configuration > VLAN > Tag-Based > Tagging
menu.
To add or delete specific ports from a VLAN,
 Click on Join & Leave button from the Configuration > VLAN >. Tag-
Based > Settings menu and specify the action.
In the example below, we will take port 2 and assign it to leave VLAN
10. After the action is completed, note that port 2 will belong to VLAN
1 only.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 10–23

VLAN CHAPTER 10: VLAN

To enable the filter capability for each port, use the Configuration >VLAN >Tag-Based >
Settings menu as shown below.

Use the Configuration >VLAN >Tag-Based > Filter menu to view the filter information for
the ports.

10–24 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 11: VLAN Registration

VLAN Registration over GARP

11.1 Overview

11.1.1 Description
The Generic Attribute Registration Protocol (GARP) and VLAN registration over GARP is
called GVRP. GVRP is defined in the IEEE 802.1q and GARP in the IEEE 802.1p standards. To
utilize the capabilities of GVRP, GE Digital Energy recommends that the user become
familiar with the concepts and capabilities of IEEE 802.1q.

11.1.2 GVRP Concepts

GVRP makes it easy to propagate VLAN information across multiple switches. Without
GVRP, a network administrator has to go to each individual switch and enable the
necessary VLAN information or block specific VLANs so that the network integrity is
maintained. With GVRP, this process can be automated.
It is critical that all switches share a common VLAN. This VLAN typically is the default VLAN
(VID=1) on most switches and other devices. GVRP uses “GVRP Bridge Protocol Data Units”
(“GVRP BPDUs”) to “advertise” static VLANs. We refer to GVRP BPDU is as an
“advertisement”.
GVRP enables the MultiLink ML800 Managed Edge Switch to dynamically create 802.1q-
compliant VLANs on links with other devices running GVRP. This enables the switch to
automatically create VLAN links between GVRP-aware devices. A GVRP link can include
intermediate devices that are not GVRP-aware. This operation reduces the chances for
errors in VLAN configuration by automatically providing VLAN ID (VID) consistency across
the network. GVRP can thus be used to propagate VLANs to other GVRP-aware devices
instead of manually having to set up VLANs across the network. After the switch creates a
dynamic VLAN, GVRP can also be used to dynamically enable port membership in static
VLANs configured on a switch.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 11–1

VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP

There must be one common VLAN (that is, one common VID) connecting all of the GVRP-
Note

aware devices in the network to carry GVRP packets. GE Digital Energy recommends the
NOTE default VLAN (DEFAULT_VLAN; VID = 1), which is automatically enabled and configured as
untagged on every port of the MultiLink ML800 Managed Edge Switch. That is, on ports
used as GVRP links, leave the default VLAN set to untagged and configure other static
VLANs on the ports as either “Tagged or Forbid” (“Forbid” is discussed later in this chapter).

11.1.3 GVRP Operations

A GVRP-enabled port with a tagged or untagged static VLAN sends advertisements
(BPDUs, or Bridge Protocol Data Units) advertising the VLAN identification (VID) Another
GVRP-aware port receiving the advertisements over a link can dynamically join the
advertised VLAN. All dynamic VLANs operate as Tagged VLANs. Also, a GVRP-enabled port
can forward an advertisement for a VLAN it learned about from other ports on the same
switch. However, the forwarding port will not itself join that VLAN until an advertisement for
that VLAN is received on that specific port.

Switch 1 Switch 2 Switch 3 Static VLAN

GVRP On GVRP On GVRP On configured end
device (NIC or
switch) with
2 3 5 GVRP on
1 4 6

754721A1.CDR

FIGURE 11–1: GVRP operation

Switch 1 with static VLANs (VID= 1, 2, and 3). Port 2 is a member of VIDs 1, 2, and 3.
1. Port 2 advertises VIDs 1, 2, and 3.
2. On Switch 2 - Port 1 receives advertisement of VIDs 1, 2, and 3 AND becomes a
member of VIDs 1, 2, and 3.
3. As discussed above, a GVRP enabled port can forward advertisement for a
VLAN it learnt about. So port 3 advertises VIDs 1, 2, and 3, but port 3 is NOT a
member of VIDs 1, 2, and 3 at this point, nor will it join the VLAN until and
advertisement is received.
4. On Switch 3, port 4 receives advertisement of VIDs 1, 2, and 3 and becomes a
member of VIDs 1, 2, and 3.
5. Port 5 advertises VIDs 1, 2,and 3, but port 5 is NOT a member of VIDs 1, 2, and
3 at this point.
6. Port 6 on the end device is statically configured to be a member of VID 3. Port
6 advertises VID 3.
7. Port 5 receives advertisement.
8. Port 4 advertises VID 3.
9. Port 3 receives advertisement of VID 3 AND becomes a member of VID 3. (Still
not a member of VIDs 1 and 2 as it did not receive any advertisements for VID
1 or 2).
10. Port 1 advertises VID 3 of VID 3 AND becomes a member of VID 3. (Port 1 is still
not a member of VIDs 1 and 2).
11. Port 2 receives advertisement of VID 3. (Port 2 was already statically
configured for VIDs 1, 2, 3).

11–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 11: VLAN REGISTRATION OVER GARP VLAN REGISTRATION OVER GARP

If a static VLAN is configured on at least one port of a switch, and that port has established
Note

a link with another device, then all other ports of that switch will send advertisements for
NOTE that VLAN.
In the following figure, tagged VLAN ports on switch “A” and switch “C” advertise VLANs 22
and 33 to ports on other GVRP-enabled switches that can dynamically join the VLANs. A
port can learn of a dynamic VLAN through devices that are not aware of GVRP (Switch “B”).

Switch C
Switch C Port 5 dynamically joined VLAN 22
1 5 GVRP On Ports 11, 12 belong to Tagged VLAN 33
Switch A
GVRP On Tagged
VLAN 22
Tagged 11
2 Switch E
VLAN 22 Tagged 12 GVRP On
VLAN 33 Dynamic
VLAN 33

Switch D
Dynamic
GVRP On
Switch B VLAN 22
Dynamic 3
No GVRP 7
VLAN 33
Tagged Switch E
Dynamic 6
VLAN 22 Port 2 dynamically joined VLAN 33
VLAN 22 Ports 7 dynamically joined VLAN 33

Switch D
Port 3 dynamically joined VLAN 33
Ports 6 dynamically joined VLAN 33 754722A1.CDR

FIGURE 11–2: VLAN assignment in GVRP enabled switches

An “unknown VLAN” is a VLAN that the switch learns of by GVRP. For example, suppose that
port 1 on switch “A” is connected to port 5 on switch “C”. Because switch “A” has VLAN 22
statically configured, while switch “C” does not have this VLAN statically configured, VLAN
22 is handled as an “Unknown VLAN” on port 5 in switch “C”. Conversely, if VLAN 22 was
statically configured on switch C, but port 5 was not a member, port 5 would become a
member when advertisements for VLAN 22 were received from switch “A”. GVRP provides a
per-port join-request option which can be configured.
VLANs must be disabled in GVRP-unaware devices to allow tagged packets to pass
through. A GVRP-aware port receiving advertisements has these options:
• If there is no static VLAN with the advertised VID on the receiving port, then
dynamically create a VLAN with the same VID as in the advertisement, and allow
that VLAN's traffic
• If the switch already has a static VLAN with the same VID as in the advertisement,
and the port is configured to learn for that VLAN, then the port will dynamically join
the VLAN and allow that VLAN's traffic.
• Ignore the advertisement for that VID and drop all GVRP traffic with that VID
• Don't participate in that VLAN
• A port belonging to a tagged or untagged static VLAN has these configurable
options:
• Send VLAN advertisements, and also receive advertisements for VLANs on other
ports and dynamically join those VLANs
• Send VLAN advertisements, but ignore advertisements received from other ports
• Avoid GVRP participation by not sending advertisements and dropping any
advertisements received from other devices

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 11–3

VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP

Table 11–1: Port settings for GVRP operations

Unknown Operations
VLAN mode
Learn Enables the port to dynamically join any VLAN
for which it receives and advertisement, and
allows the port to forward the advertisement it
receives.
Block Prevents the port from dynamically joining a
VLAN that is not statically configured on the
switch. The port will still forward advertisements
that were received by the switch on other ports.
Block should typically be used on ports in
insecure networks where there is exposure to
attack - such as ports where intruders can
connect.
Disable Causes the port to ignore and drop all the
advertisements it receives from any source.

The show-vlan command displays a switch's current GVRP configuration, including the
unknown VLANs.
show-vlan
A port must be enabled and configured to learn for it to be assigned to the dynamic VLAN.
To send advertisements, one or more tagged or untagged static VLANs must be configured
on one (or more) switches with GVRP enabled. The ML800 software allows a dynamic VLAN
to be converted to a static VLAN with the static command.
static vlan=<VID>

The show vlan type=tag command will display VID in case the VID is not known.
Note

NOTE
Example 11-1 illustrates how to convert a dynamic VLAN into a static VLAN.
As the following table indicates, a port that has a tagged or untagged static VLAN has the
option for both generating advertisements and dynamically joining other VLANs.

Table 11–2: GVRP options

Per-port “unknown Per-port static VLAN options
VLAN” (GVRP)
configuration Tagged or untagged Auto Forbid

Learn Generate advertisements. Receive advertisements Do not allow the port to

Forward advertisements for and dynamically join become a member of
other VLANs. Receive any advertised VLAN this VLAN
advertisements and that has the same VID
dynamically join any as the static VLAN
advertised VLAN
Block Generate advertisements. Receive advertisements Do not allow the VLAN
Forward advertisements and dynamically join on this port
received from other ports to any advertised VLAN
other VLANs. Do not that has the same VID
dynamically join any
advertised VLAN
Disable Ignore GVRP and drop all GVRP Ignore GVRP and drop Do not allow the VLAN
advertisements all GVRP on this port
advertisements

11–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 11: VLAN REGISTRATION OVER GARP VLAN REGISTRATION OVER GARP

Example 11-1: Converting a dynamic VLAN to a static VLAN

The unknown VLAN parameters are configured on a per interface basis using the CLI. The
tagged, untagged, Auto, and Forbid options are configured in the VLAN context. Since
dynamic VLANs operate as tagged VLANs, and it is possible that a tagged port on one
device may not communicate with an untagged port on another device, GE Digital Energy
recommends that you use tagged VLANs for the static VLANs.
A dynamic VLAN continues to exist on a port for as long as the port continues to receive
advertisements of that VLAN from another device connected to that port or until you:
• Convert the VLAN to a static VLAN
• Reconfigure the port to Block or Disable
• Disable GVRP
• Reboot the switch
The time-to-live for dynamic VLANs is 10 seconds. That is, if a port has not received an
advertisement for an existing dynamic VLAN during the last 10 seconds, the port removes
itself from that dynamic VLAN.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 11–5

VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP

11.2 Configuring GVRP through the Command Line

Interface

11.2.1 Commands
The commands used for configuring GVRP are shown below.
The gvrp command enables or disables GVRP.
gvrp <enable|disable>
The show gvrp command displays whether GVRP is disabled, along with the current
settings for the maximum number of VLANs and the current primary VLAN.
show gvrp
The set-ports command set the state of the port to learn, block or disable for GVRP.
Note the default state is disable.
set-ports port=<port|list|range> state=<learn|block|disable>
The set-forbid command sets the forbid GVRP capability on the ports specified.
set-forbid vlan=<tag vlanid>
forbid=<port-number|list|range>
The show-forbid command displays the ports with GVRP forbid capabilities.
show-forbid
The following example illustrates how to configure GVRP using the commands shown in
this section.

11.2.2 GVRP Operation Notes

A dynamic VLAN must be converted to a static VLAN before it can have an IP address.
After converting a dynamic VLAN to a static VLAN use the “save” command to save the
changes made - on a reboot the changes can be lost without the save command.
Within the same broadcast domain, a dynamic VLAN can pass through a device that is not
GVRP-aware. This is because a hub or a switch that is not GVRP-aware will flood the GVRP
(multicast) advertisement packets out all ports.
GVRP assigns dynamic VLANs as tagged VLANs. To configure the VLAN as untagged, first
convert the tagged VLAN to a static VLAN.
Rebooting a switch on which a dynamic VLAN deletes that VLAN. However, the dynamic
VLAN re-appears after the reboot if GVRP is enabled and the switch again receives
advertisements for that VLAN through a port configured to add dynamic VLANs.
By receiving advertisements from other devices running GVRP, the switch learns of static
VLANs from those devices and dynamically (automatically) creates tagged VLANs on the
links to the advertising devices. Similarly, the switch advertises its static VLANs to other
GVRP-aware devices.
A GVRP-enabled switch does not advertise any GVRP-learned VLANs out of the port(s) on
which it originally learned of those VLANs.

11–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 11: VLAN REGISTRATION OVER GARP VLAN REGISTRATION OVER GARP

Example 11-2: Configuring GVRP

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 11–7

VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP

11.3 Configuring GVRP with EnerVista Secure Web

Management software

11.3.1 Example
To configure GVRP,
 Select the Configuration > VLAN > GVRP menu item.

From the GVRP menu screen, GVRP can be enabled or disabled using the drop down menu.
Each specific port can be put in the Learn, Disable or Enable state as shown in Table 11–2:
GVRP options on page 11–4.
The unknown VLAN parameters are configured on a per interface basis using the CLI. The
tagged, untagged, Auto, and Forbid options are configured in the VLAN context. Since
dynamic VLANs operate as tagged VLANs, and it is possible that a tagged port on one
device may not communicate with an untagged port on another device, GE Digital Energy
recommends that you use tagged VLANs for the static VLANs.
A dynamic VLAN continues to exist on a port for as long as the port continues to receive
advertisements of that VLAN from another device connected to that port or until you:
• Convert the VLAN to a static VLAN
• Reconfigure the port to Block or Disable
• Disable GVRP
• Save the configuration
• Reboot the switch
The time-to-live for dynamic VLANs is 10 seconds. That is, if a port has not received an
advertisement for an existing dynamic VLAN during the last 10 seconds, the port removes
itself from that dynamic VLAN.
Refer to GVRP Operation Notes on page 11–6 for additional information on using GVRP.

11–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 12: Spanning Tree

Spanning Tree Protocol (STP)

12.1 Overview

12.1.1 Description
The Spanning Tree Protocol was designed to avoid loops in an Ethernet network. An
Ethernet network using switches can have redundant paths, which may cause loops. To
prevent loops, the MultiLink Switch Software uses the spanning tree protocol (STP).
Controlling the span in which traffic traverses is necessary as a manager of the software. It
is also necessary to specify the parameters of STP. STP is available as the IEEE 802.1d
protocol and is a standard of the IEEE.

12.1.2 Features and Operation

The switch uses the IEEE 802.1d Spanning Tree Protocol (STP). When STP is enabled, it
ensures that only one path at a time is active between any two nodes on the network. In
networks where more than one physical path exists between two nodes, STP ensures only
a single path is active by blocking all redundant paths. Enabling STP is necessary to avoid
loops and duplicate messages. This duplication leads to a “broadcast storm” or other
erratic behavior that can bring down the network.
As recommended in the IEEE 802.1Q VLAN standard, the MultiLink ML800 Managed Edge
Switch uses single-instance STP. This means a single spanning tree is created to make sure
there are no network loops associated with any of the connections to the switch. This
works regardless of whether VLANs are configured on the switch. Thus, these switches do
not distinguish between VLANs when identifying redundant physical links.
The switch automatically senses port identity and type, and automatically defines port
cost and priority for each type. The software allows a manager to adjust the cost, priority,
the mode for each port as well as the global STP parameter values for the switch.
While allowing only one active path through a network at any time, STP retains any
redundant physical path to serve as a backup (blocked) path in case the existing active
path fails. Thus, if an active path fails, STP automatically activates (unblocks) an available
backup to serve as the new active path for as long as the original active path is down.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 12–1

SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP)

The table below lists the default values of the STP variables. Refer to the following section
for detailed explanation on the variables. By default, STP is disabled. To use STP, it has to be
manually enabled.

Table 12–1: STP default values

Variable or attribute Default value
STP capabilities Disabled
Reconfiguring general operation priority 32768
Bridge maximum age 20 seconds
Hello time 2 seconds
Forward delay 15 seconds
Reconfiguring per-port STP path cost 0
Priority 32768
Mode Normal
Monitoring of STP Not available
Root Port Not set

12–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP)

12.2 Configuring STP

The show stp command lists the switch's full STP configuration, including general
settings and port settings, regardless of whether STP is enabled or disabled (default).
show stp <config|ports>
Example 12-1 illustrates the show stp command with the config parameter.
The variables listed in this example are defined as follows
• Spanning Tree Enabled (Global): Indicates whether STP is enabled or disabled
globally; that is, if the values is YES, all ports have STP enabled. Otherwise, all ports
have STP disabled.
• Spanning Tree Enabled (Ports): Indicates which ports have STP enabled. In the
example, ports 9 through 16 have STP enabled, but STP functionality is not
enabled. As such, STP will not perform on these ports.
• Bridge Priority: Specifies the switch (bridge) priority value. This value is used along
with the switch MAC address to determine which switch in the network is the root
device. Lower values indicate higher priority, and values range from 0 to 65535
with a default value of 32768.
• Bridge Forward Delay: Indicates the duration the switch waits from listening to
learning states and from learning to forwarding states. The value ranges from 4 to
30 seconds, with a default of 15.
• Bridge Hello Time: When the switch is the root device, this is the time between
messages being transmitted. The value is from 1 to 10 seconds, with a default of 2.
• Bridge Max Age: This is the maximum time a message with STP information is
allowed by the switch before the switch discards the information and updates the
address table. Value range from 6 to 40 seconds with default value of 20.
• Root Port: Indicates the port number elected as the root port of the switch. A root
port of "0" indicates STP is disabled.
• Root Path Cost: A path cost is assigned to individual ports for the switch to
determine which ports are the forwarding points. A higher cost indicates more
loops, a lower cost indicates fewer loops. More loops equal more traffic and a tree
which requires a long time to converge - resulting in a slower system.
• Designated Root: Displays the MAC address of the bridge in the network elected or
designated as the root bridge. When STP is not enabled, the switch designates
itself as the root switch.
• Designated Root Priority: Shows the designated root bridge's priority. The default
value is 32768.
• Root Bridge Forward Delay: Indicates the designated root bridge forward delay.
This is the time the switch waits before switching from the listening to the

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 12–3

SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP)

forwarding state. The default is 15 seconds, with a range of 4 to 30 seconds.

• Root Bridge Hello Time: Indicates the designated root bridge's hello time. Hello
information is transmitted every 2 seconds.
• Root Bridge Max Age: Indicates the designated root bridge maximum age, after
which it discards the information as being old and receives new updates.
These variables can be changed using the “priority”, “cost”, “port” and “timers” commands
described later in this chapter.
Example 12-2 illustrates the show stp command with the ports parameter. The variables
listed in this example are defined as follows:
• Port#: indicates the port number. Value ranges from 01 to max number of ports in
the switch
• Type: indicates the type of port - TP indicates Twisted Pair

Example 12-1: Viewing STP configuration

ML800#show stp config

RSTP CONFIGURATION
-----------------
Rapid STP/STP Enabled(Global) : NO
RSTP/STP Enabled Ports : 1,2,3,4,5,6,7
Protocol : Normal RSTP
Bridge ID : 80:00:00:00:00:00:00:00
Bridge Priority : 32768
Bridge Forward Delay : 15
Bridge Hello Time : 02
Bridge Max Age : 20
Root Port :0
Root Path Cost :0
Designated Root : 80:00:00:00:00:00:00:00

Example 12-2: Viewing STP ports

ML800#show stp ports

STP Port Configuration

12–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP)

• Priority: STP uses this to determine which ports are used for forwarding. Lower the
number means higher priority. Value ranges from 0 to 255. Default is 128
• Path Cost: This is the assigned port cost value used for the switch to determine the
forwarding points. Values range from 1 to 65535
• State: indicates the STP state of individual ports. Values can be Listening, Learning,
Forwarding, Blocking and Disabled.
• Des. Bridge: This is the port's designated root bridge
• Des. Port: This is the port's designated root port
To enable or disable STP, enter the STP configuration mode via the stp command and use
the stp enable or stp disable command.
To stp command enters STP configuration mode:
stp
The enable and disable parameters start (enable) or stop (disable) STP.
stp <enable|disable>
The stp and rstp parameters set the spanning tree protocol to be IEEE 802.1d or 802.1w
(Rapid Spanning Tree Protocol).
set stp type=<stp|rstp>
The show active-stp command display which version of STP is currently active.
show active-stp

Incorrect STP settings can adversely affect network performance. GE recommends starting
Note

with the default STP settings. Changing the settings requires a detailed understanding of
NOTE STP. For more information on STP, please refer to the IEEE 802.1d standard.

It is always a good idea to check which mode of STP is active. If the proper mode is not
Note

active, the configuration command stp will not be understood. To set the proper mode,
NOTE use the set stp command.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 12–5

SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP)

Example 12-3 shows how to enable STP using the above commands.

Example 12-3: Enabling STP

ML800#show active-stp

Current Active Mode: RSTP.

RSTP is Disabled.

ML800#stp

ERROR: Invalid Command

ML800#set stp type=stp

STP Mode set to STP.

ML800#stp

ML800(stp)##stp enable
Successfully set the STP status

ML800(stp)##show stp config

STP CONFIGURATION
-----------------
Spanning Tree Enabled(Global) : YES
Spanning Tree Enabled(Ports) : YES, 1,2,3,4,5,6,7
Protocol : Normal STP
Bridge ID : 80:00:00:20:06:2b:e1:54
Bridge Priority : 32768
Bridge Forward Delay : 15
Bridge Hello Time : 2
Bridge Max Age : 20
Root Port : 0
Root Path Cost : 0
Designated Root : 80:00:00:20:06:2b:e1:54

12–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP)

The priority command specifies the port or switch level priority. When a port(s) are
specified the priority is associated with ports and their value is 0 to 255. If no ports are
specified, then the switch (bridge) priority is specified and its value is 0 to 65535. This value
is used along with the switch MAC address to determine which switch in the network is the
root device. Lower values mean higher priority. The default value is 32768.
priority [port=<number|list|range>]
value=<0-255 | 0-65535>
The cost command is port specific. A path cost is assigned to individual ports for the
switch to determine which ports are the forwarding points. A higher cost means the link is
“more expensive” to use and falls in the passive mode compared to the link with a lower
cost. Value ranges from 0 to 65535, with a default value of 32768.
cost port=<number|list|range>
value=<0-65535>
The port command assigns ports to STP. If you are unsure, let the software make the
decisions. The status parameter enables or disables a port from participating in STP
discovery. Its best to only allow trunk ports to participate in STP. End stations need not
participate in STP process.
port port=<number|list|range>
status=<enable|disable>
The timers command changes the STP forward delay, hello timer and aging timer values.
The forward-delay parameter indicates the time duration the switch will wait from
listening to learning states and from learning to forwarding states. The value ranges from
4 to 30 seconds with a default value of 15. When the switch is the root device, the hello
parameter represents the time between messages being transmitted. The value is from 1
to 10 seconds with a default value is 2. The age parameter is the maximum time a
message with STP information is allowed by the switch before the switch discards the
information and updates the address table again. Value ranges from 6 to 40 seconds with
default value of 20.
timers forward-delay=<4-30> hello=<1-10> age=<6-40>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 12–7

SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP)

Example 12-4: Configuring STP parameters

ML800(stp)##show stp config

STP CONFIGURATION
-----------------
Spanning Tree Enabled(Global) : NO
Spanning Tree Enabled(Ports) : YES, 1,2,3,4,5,6,7
Protocol : Normal STP
Bridge ID : 80:00:00:20:06:2b:e1:54
Bridge Priority : 32768
Bridge Forward Delay : 15
Bridge Hello Time : 2
Bridge Max Age : 20
Root Port : 0
Root Path Cost : 0
Designated Root : 80:00:00:20:06:2b:e1:54
Designated Root Priority : 32768
Root Bridge Forward Delay : 15
Root Bridge Hello Time : 2
Root Bridge Max Age : 20

ML800(stp)##show stp ports

STP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port

12–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP)

Configuring STP parameters (continued)

ML800(stp)##show stp ports

STP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 100 Forwarding 80:00:00:20:06:2b:e1:54 80:01
02 TP(10/100) 128 19 Forwarding 80:00:00:20:06:2b:e1:54 80:02
03 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:03
04 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:04
Ports that have connected devices
05 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:05 now participate in STP.
06 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:06
07 TP(10/100) 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:07

ML800(stp)##priority value=15535
Successfully set the bridge priority

ML800(stp)##show stp config

STP CONFIGURATION
-----------------
Spanning Tree Enabled(Global) : YES
Spanning Tree Enabled(Ports) : YES, 1,2,3,4,5,6,7
Protocol : Normal STP
STP is now enabled. Note the default
Bridge ID : 3c:af:00:20:06:2b:e1:54
values for the discussed variables.
Bridge Priority : 15535
Bridge Forward Delay : 15
Bridge Hello Time : 2
Bridge Max Age : 20
Root Port : 0
Root Path Cost : 0
Designated Root : 3c:af:00:20:06:2b:e1:54
Designated Root Priority : 15535
Root Bridge Forward Delay : 15
Root Bridge Hello Time : 2
Root Bridge Max Age : 20

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 12–9

SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP)

Configuring STP parameters (continued)

ML800(stp)##cost port=2 value=20

Setting cost for STP...Successfully set the path cost for port 2

ML800(stp)##show stp ports

STP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 100 Forwarding 80:00:00:20:06:2b:e1:54 80:01
02 TP(10/100) 20 20 Forwarding 80:00:00:20:06:2b:e1:54 80:02
03 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:03
04 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:04
05 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:05
06 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:06
07 TP(10/100) 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:07

ML800(stp)##port port=1 status=disable

Successfully set the STP status for port 1

ML800(stp)##show stp ports

STP Port Configuration Since port 9 does not participate in

STP, it is not listed here. Any changes
made to STP parameters on port 9 will
------------------------------------------------------------------------------- be ignored

Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 100 Forwarding 80:00:00:20:06:2b:e1:54 80:01
02 TP(10/100) 20 20 Forwarding 80:00:00:20:06:2b:e1:54 80:02
03 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:03
04 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:04
05 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:05
06 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:06
07 TP(10/100) 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:07

12–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP)

Configuring STP parameters (continued)

ML800(stp)##port port=1 status=enable

Successfully set the STP status for port 1

R-2S(stp)##show stp ports

STP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 100 Forwarding 80:00:00:20:06:2b:e1:54 80:01
02 TP(10/100) 20 20 Forwarding 80:00:00:20:06:2b:e1:54 80:02
03 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:03
04 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:04
05 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:05
06 100MB Fiber 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:06
07 TP(10/100) 128 100 Disabled 80:00:00:20:06:2b:e1:54 80:07

The age parameter is out of range as

ML800(stp)##show stp config per the IEEE 802.1d specifications.

STP CONFIGURATION
-----------------
Spanning Tree Enabled(Global) : YES
Spanning Tree Enabled(Ports) : YES, 1,2,3,4,5,6,7
Protocol : Normal STP
Bridge ID : 80:00:00:20:06:2b:e1:54
Bridge Priority : 15535
Bridge Forward Delay : 15
Bridge Hello Time : 2
Bridge Max Age : 20
Root Port : 0
Root Path Cost : 0
Designated Root : 80:00:00:20:06:2b:e1:54
Designated Root Priority : 15535
Root Bridge Forward Delay : 15

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 12–11

SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP)

Configuring STP parameters (continued)

ML800(stp)##show stp config

STP CONFIGURATION
-----------------
Spanning Tree Enabled(Global) : YES
Spanning Tree Enabled(Ports) : YES, 1,2,3,4,5,6,7
Protocol : Normal STP
Bridge ID : 80:00:00:20:06:2b:e1:54
Bridge Priority : 15535
Bridge Forward Delay : 20
Bridge Hello Time : 5
Bridge Max Age : 30
Root Port : 0
Root Path Cost : 0
Designated Root : 80:00:00:20:06:2b:e1:54

12–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 13: Rapid Spanning Tree

Rapid Spanning Tree Protocol

13.1 Overview

13.1.1 Description
The Rapid Spanning Tree Protocol (RTSP), like STP, was designed to avoid loops in an
Ethernet network. Rapid Spanning Tree Protocol (RSTP) (IEEE 802.1w) is an evolution of the
Spanning Tree Protocol (STP) (802.1d standard) and provides for faster spanning tree
convergence after a topology change.

13.1.2 RSTP concepts

The IEEE 802.1d Spanning Tree Protocol (STP) was developed to allow the construction of
robust networks that incorporate redundancy while pruning the active topology of the
network to prevent loops. While STP is effective, it requires that frame transfer must halt
after a link outage until all bridges in the network are sure to be aware of the new topology.
Using STP (IEEE 802.1d) recommended values, this period lasts 30 seconds.
The Rapid Spanning Tree Protocol (IEEE 802.1w) is a further evolution of the 802.1d
Spanning Tree Protocol. It replaces the settling period with an active handshake between
switches (bridges) that guarantees topology information to be rapidly propagated through
the network. RSTP converges in less than one second. RSTP also offers a number of other
significant innovations. These include
• Topology changes in STP must be passed to the root bridge before they can be
propagated to the network. Topology changes in RSTP can be originated from and
acted upon by any designated switch (bridge), leading to more rapid propagation
of address information
• STP recognizes one state - blocking for ports that should not forward any data or
information. RSTP explicitly recognizes two states or blocking roles - alternate and
backup port including them in computations of when to learn and forward and
when to block
• STP relays configuration messages received on the root port going out of its
designated ports. If an STP switch (bridge) fails to receive a message from its

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–1

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

neighbor it cannot be sure where along the path to the root a failure occurred.
RSTP switches (bridges) generate their own configuration messages, even if they
fail to receive one from the root bridge. This leads to quicker failure detection
• RSTP offers edge port recognition, allowing ports at the edge of the network to
forward frames immediately after activation while at the same time protecting
them against loops
• An improvement in RSTP allows configuration messages to age more quickly
preventing them from “going around in circles” in the event of a loop
RSTP has three states. They are discarding, learning and forwarding.
The discarding state is entered when the port is first taken into service. The port does not
learn addresses in this state and does not participate in frame transfer. The port looks for
STP traffic in order to determine its role in the network. When it is determined that the port
will play an active part in the network, the state will change to learning. The learning state
is entered when the port is preparing to play an active member of the network. The port
learns addresses in this state but does not participate in frame transfer. In a network of
RSTP switches (bridges) the time spent in this state is usually quite short. RSTP switches
(bridges) operating in STP compatibility mode will spend between 6 to 40 seconds in this
state. After 'learning' the bridge will place the port in the forwarding state. While in this
state the port both learns addresses and participates in frame transfer while in this state.
The result of these enhanced states is that the IEEE 802.1d version of spanning tree (STP)
can take a fairly long time to resolve all the possible paths and to select the most efficient
path through the network. The IEEE 802.1w Rapid reconfiguration of Spanning Tree
significantly reduces the amount of time it takes to establish the network path. The result is
reduced network downtime and improved network robustness. In addition to faster
network reconfiguration, RSTP also implements greater ranges for port path costs to
accommodate the higher connection speeds that are being implemented.
Proper implementations of RSTP (by switch vendors) is designed to be compatible with IEEE
802.1d STP. GE recommends that you employ RSTP or STP in your network.

13.1.3 Transition from STP to RSTP

IEEE 802.1w RSTP is designed to be compatible with IEEE 802.1D STP. Even if all the other
devices in your network are using STP, you can enable RSTP on the MultiLink ML800
Managed Edge Switch. The default configuration values of the RSTP available in ML800
software will ensure that your switch will inter-operate effectively with the existing STP
devices. RSTP automatically detects when the switch ports are connected to non-RSTP
devices using spanning tree and communicates with those devices using 802.1d STP BPDU
packets.
Even though RSTP inter-operates with STP, RSTP is more efficient at establishing the
network path and network convergence in case of a very fast failure. As such, GE
recommends that all network devices be updated to support RSTP. RSTP offers
convergence times typically less than one second. However, to make best use of RSTP and
achieve the fastest possible convergence times, there are some changes required to the
RSTP default configuration.
1. Under some circumstances, it is possible for the rapid state transitions
employed by RSTP to result in an increase in the rates of frame duplication
and the order in which the frames are sent and received. To allow RSTP
switches to support applications and protocols that may be sensitive to frame
duplication and out of sequence frames, RSTP may have to be explicitly set to
be compatible with STP. This requires setting the “Force Protocol Version”
parameter to be STP compatible. This parameter should be set to all ports on
a given switch.

13–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

2. As indicated above, one of the benefits of RSTP is the implementation of a

larger range of port path costs that accommodates higher network speeds.
New default values have been implemented for path costs associated with
the different network speeds. This may create incompatibility between
devices running the older implementations of STP a switch running RSTP.
3. At any given time, the software can support either STP or RSTP but not both.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–3

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

13.2 Configuring RSTP through the Command Line

Interface

13.2.1 Normal RSTP

The commands to setup and configure RSTP are as follows. The set stp command sets
the switch to support RSTP or STP. It is necessary to save and reboot the switch after this
command.
set stp type=<stp|rstp> -
The rstp command enters the RSTP configuration mode and enables/disabled RSTP. By
default, RSTP is disabled and has to be manually activated.
rstp
rstp <enable|disable>
The syntax for the port command on RSTP is shown below.
port port=<number|list|range> [status=<enable|disable>] [migration=<enable>]
[edge=<enable|disable>] [p2p=<on|off|auto>]
The p2p parameter sets the “point-to-point” value to off on all ports connected to shared
LAN segments (i.e. connections to hubs). The default value is auto. P2P ports would
typically be end stations or computers on the network.
The edge parameter enables/disables all ports connected to other hubs, bridges and
switches as edge ports.
The migration parameter is set for all ports connected to devices such as hubs, bridges
and switches known to support IEEE 802.1d STP services but not RSTP services
The show active-stp command displays whether STP or RSTP is running.
show active-stp
The show stp command display the RSTP or STP parameters.
show stp <config|ports>

Users may notice extended recovery time if there is a mix of firmware revisions in the Mesh
Note

or Ring
NOTE

13–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

The variables listed by the show stp config command are:

• Rapid Spanning Tree Enabled (Global): Indicates whether STP is enabled or disabled
globally i.e. if the values is YES, all ports have STP enabled, otherwise, all ports have
STP disabled.
• Rapid Spanning Tree Enabled Ports: Indicates which ports have RSTP enabled.
• Protocol: Indicates whether STP or RSTP is being used. It also indicates if RSTP is used
in Smart RSTP (ring-only mode) or normal mode.
• Bridge Priority: Specifies the switch (bridge) priority value. This value is used along
with the switch MAC address to determine which switch in the network is the root
device. Lower values mean higher priority. Values range from 0 to 65535 with a
default of 0.
• Bridge Forward Delay: Indicates the time duration the switch will wait from listening
to learning states and from learning to forwarding states. The value ranges from 4 to
30 seconds with a default of 15.
• Bridge Hello Time: When the switch is the root device, this is the time between
messages being transmitted. The value is from 1 to 10 seconds with a default of 2.
• Bridge Max Age: This is the maximum time a message with STP information is allowed
by the switch before the switch discards the information and updates the address
table again. Values range from 6 to 40 seconds with a default value of 20.

Example 13-1: Enabling RSTP and reviewing the RSTP variables

ML800#rstp

ML800(rstp)##show stp config

RSTP CONFIGURATION
-----------------
Rapid STP/STP Enabled(Global) : NO
RSTP/STP Enabled Ports : 1,2,3,4,5,6,7
Protocol : Normal RSTP
Bridge ID : 80:00:00:20:06:2b:e1:55
Bridge Priority : 32768
Bridge Forward Delay : 15
Bridge Hello Time : 02
Bridge Max Age : 20
Root Port :0
Root Path Cost :0
Designated Root : 80:00:00:20:06:2b:e1:55
Designated Root Priority : 32768
Root Bridge Forward Delay : 15
Root Bridge Hello Time : 02
Root Bridge Max Age : 20
Topology Change count :0
Time Since topology Chg : 16

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–5

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

• Root Port: Indicates the port number, which is elected as the root port of the switch. A
root port of "0" indicates STP is disabled.
• Root Path Cost: A path cost is assigned to individual ports for the switch to determine
which ports are the forwarding points. A higher cost means more loops; a lower cost
means fewer loops. More loops equal more traffic and a tree which takes a long time
to converge, resulting in a slower system.
• Designated Root: Shows the MAC address of the bridge in the network elected or
designated as the root bridge.
• Designated Root Priority: Shows the designated root bridge's priority. The default
value is 0.
• Root Bridge Forward Delay: Indicates the designated root bridge's forward delay.
This is the time the switch waits before it switches from the listening to the forwarding
state. This value can be set between 4 to 30 seconds, with a default of 15.
• Root Bridge Hello Time: Indicates the designated root bridge's hello time. Hello
information is sent out every 2 seconds.
• Root Bridge Max Age: Indicates the designated root bridge's maximum age, after
which it discards the information as being old and receives new updates.
• Topology Change Count: Since the last reboot, the number of times the topology has
changed. Use this in conjunction with "show uptime" to find the frequency of the
topology changes.
• Time Since topology Change: The number of seconds since the last topology change.
The variables listed by the show stp ports command are:
• Port#: Indicates the port number. The value ranges from 1 to the maximum number of
ports in the switch.
• Type: Indicates the type of port. TP indicates twisted pair.
• Priority: STP uses this to determine which ports are used for forwarding. Lower
numbers indicate higher priority. The values range from 0 to 255, with a default of 128.
• Path Cost: This is the assigned port cost value used for the switch to determine the
forwarding points. Values range from 1 to 2000000. Lower values indicate a lower
cost and hence the preferred route. The costs for different Ethernet speeds are
indicated below. The Path cost in STP is compared to the path cost in RSTP.

Example 13-2: Reviewing the RSTP port parameters

ML800(rstp)##show stp ports

RSTP Port Configuration

13–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

Example 13-3: RSTP information from a network with multiple switches

ML800(rstp)##show stp ports

RSTP Port Configuration

Table 13–1: Path cost as defined in IEEE 802.1d / 802.1w

Port type STP path cost RSTP path cost
10 Mbps 100 2000000
100 Mbps 19 200000
1 Gbps 4 20000
10 Gbps 2 2000

• State: Indicates the STP state of individual ports. Values can be Listening, Learning,
Forwarding, Blocking and Disabled.
• Des. Bridge: This is the port's designated root bridge
• Des. Port: This is the port's designated root port
Another example of the same command, from a larger network with several switches is
shown in Example 13-3. Note the show stp ports command can be executed from the
manager level prompt or from RSTP configuration state as shown in the screen captures
earlier

In this example, ports 9 and 10 have a path cost of 20000 and are the least cost paths.
These ports are connected to other switches and the ports are enabled as forwarding
ports. Ports 6 and 7 are also connected to other switches. From the state column, it
indicates that port 7 is in a standby state as that port is discarding all traffic.
More CLI commands associated with RSTP in the RSTP configuration mode are shown
below. The forceversion command sets the STP or RSTP compatibility mode.
forceversion <stp|rstp>
The show-forceversion command displays the current forced version.
show-forceversion
The show-timers command displays the values of the timers set for RSTP.
show-timers

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–7

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

The priority command specifies the switch (bridge) priority value. This value is used
along with the switch MAC address to determine which switch in the network is the root
device. Lower values mean higher priority. The value ranges from 0 to 65535 with a default
of 32768. When port are specified, the priority is associated with ports and their value is 0
to 255.
priority [port=<number|list|range>]
value=<0-255|0-65535>
A path cost is assigned to individual ports for the switch to determine which ports are the
forwarding points. A higher cost means the link is “more expensive” to use and falls in the
passive mode compared to the link with a lower cost. The value of the cost command
ranges from 0 to 65535, with a default of 32768.
cost port=<number|list|range>
value=<0-65535>
The port command assigns ports for RSTP. Note that specific ports may not need to
participate in RSTP process. These ports typically would be end-stations. If unsure, it is best
to let the software make the decisions.
port port=<number|list|range> status=<enable|disable>
The status parameter enables or disables a port from participating in RSTP discovery. Its
best to only allow trunk ports to participate in RSTP; end stations need not participate in
the RSTP process.
The timers command changes the STP forward delay, hello timer and aging timer values.
timers forward-delay=<4-30> hello=<1-10> age=<6-40>
The forward-delay parameter indicates the time duration the switch will wait from
listening to learning states and from learning to forwarding states. The value ranges from
4 to 30 seconds with a default of 15.
The hello parameter represents the time between messages being transmitted when the
switch is the root device. The value is 1 to 10 seconds, with a default of 2.
The age parameter is the maximum time a message with STP information is allowed by the
switch before the switch discards the information and updates the address table again.
Value ranges from 6 to 40 seconds with default value of 20.

13–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

Example 13-4: Configuring RSTP

ML800#rstp

Check the status of STP or RSTP. These

ML800(rstp)##show stp config commands show if STP or RSTP is
enabled.

ML800(rstp)##show active-stp

Current Active Mode: RSTP.

RSTP is Disabled.

ML800(rstp)##rstp enable
Successfully set the RSTP status

ML800(rstp)##show active-stp

Current Active Mode: RSTP.

RSTP is Enabled.

ML800(rstp)##show stp config

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–9

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

Configuring RSTP (continued)

RSTP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 2000000 Forwarding 80:00:00:20:06:2b:e1:55 00:01
02 TP(10/100) 128 200000 Forwarding 80:00:00:20:06:2b:e1:55 00:02
03 100MB Fiber 128 200000 Disabled 00:03
04 100MB Fiber 128 200000 Disabled 00:04
05 100MB Fiber 128 200000 Disabled 00:05 The forceversion capability can be
used for compatibility with STP
06 100MB Fiber 128 200000 Disabled 00:06 devices. In this example, the switch is
07 TP(10/100) 128 2000000 Disabled 00:07 forced to STP mode.

ML800(rstp)##forceversion rstp
Error: Force Version already set to Normal RSTP

ML800(rstp)##forceversion stp

ML800(rstp)##show-forceversion

Force Version : Force to STP only Using forceversion, the switch is now
operating using RSTP. Note the show
stp config command also indicates
ML800(rstp)##show stp config the switch protocol is RSTP.

RSTP CONFIGURATION
-----------------
Rapid STP/STP Enabled(Global) : YES
RSTP/STP Enabled Ports : 1,2,3,4,5,6,7
Protocol : Force to STP only
Bridge ID : 80:00:00:20:06:2b:e1:55
Bridge Priority : 32768
Bridge Forward Delay : 15
Bridge Hello Time : 02
Bridge Max Age : 20
Root Port :0
Root Path Cost :0

13–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

Configuring RSTP (continued)

RSTP CONFIGURATION
-----------------
Rapid STP/STP Enabled(Global) : YES
RSTP/STP Enabled Ports : 1,2,3,4,5,6,7
Protocol : Normal RSTP
Bridge ID : 80:00:00:20:06:2b:e1:55
Bridge Priority : 32768
Bridge Forward Delay : 15
Bridge Hello Time : 02
Bridge Max Age : 20
Root Port :0
Root Path Cost :0
Designated Root : 80:00:00:20:06:2b:e1:55
Designated Root Priority : 32768
Root Bridge Forward Delay : 15
Root Bridge Hello Time : 02
Root Bridge Max Age : 20
Topology Change count :0
Time Since topology Chg : 1371

ML800(rstp)##show-timers

Forward Delay Timer : 15 sec

Hello Timer : 2 sec
Max Age : 20 sec

ML800(rstp)##show stp ports

RSTP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 2000000 Forwarding 80:00:00:20:06:2b:e1:55 00:01
02 TP(10/100) 128 200000 Forwarding 80:00:00:20:06:2b:e1:55 00:02
03 100MB Fiber 128 200000 Disabled 00:03
04 100MB Fiber 128 200000 Disabled 00:04
05 100MB Fiber 128 200000 Disabled 00:05
06 100MB Fiber 128 200000 Disabled 00:06

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–11

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

Configuring RSTP (continued)

ML800(rstp)##show stp ports

RSTP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 2000000 Forwarding 80:00:00:20:06:2b:e1:55 00:01
02 TP(10/100) 100 250000 Forwarding 80:00:00:20:06:2b:e1:55 00:02
03 100MB Fiber 128 200000 Disabled 00:03
04 100MB Fiber 128 200000 Disabled 00:04
05 100MB Fiber 128 200000 Disabled 00:05
06 100MB Fiber 128 200000 Disabled 00:06
07 TP(10/100) 128 2000000 Disabled 00:07

ML800(rstp)##port port=1 status=disable

ML800(rstp)##show stp ports

RSTP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port
-------------------------------------------------------------------------------
01 TP(10/100) 128 2000000 NO STP 00:01
02 TP(10/100) 100 250000 Forwarding 80:00:00:20:06:2b:e1:55 00:02
03 100MB Fiber 128 200000 Disabled 00:03
04 100MB Fiber 128 200000 Disabled 00:04
05 100MB Fiber 128 200000 Disabled 00:05
06 100MB Fiber 128 200000 Disabled 00:06
07 TP(10/100) 128 2000000 Disabled 00:07

ML800(rstp)##port port=1 status=enable

ML800(rstp)##show stp ports

RSTP Port Configuration

-------------------------------------------------------------------------------
Port# Type Priority Path Cost State Des. Bridge Des. Port

13–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

Configuring RSTP (continued)

RSTP CONFIGURATION
-----------------
Rapid STP/STP Enabled(Global) : YES
RSTP/STP Enabled Ports : 1,2,3,4,5,6,7
Protocol : Normal RSTP
Bridge ID : 80:00:00:20:06:2b:e1:55
Bridge Priority : 32768
Bridge Forward Delay : 20
Bridge Hello Time : 05
Bridge Max Age : 30
Root Port :0
Root Path Cost :0
Designated Root : 80:00:00:20:06:2b:e1:55
Designated Root Priority : 32768

13.2.2 Smart RSTP (Ring-Only Mode) through the Command Line Interface (CLI)
A special case of a mesh structure is a ring. In many networks, network managers prefer to
create a ring structure for redundancy and simplicity of the topology. In a ring structure:
1. All switches in the network are GE Digital Energy switches.
2. RSTP is enabled on all the switches.
3. The topology is a ring.
4. All switches in the ring have been configured to use the Smart RSTP (ring only
mode) (as shown below).
5. All switches in the ring must use the same firmware revision.
The ring structure can demonstrate fast recovery times, typically faster than what RSTP
can recover from a single fault. In many situations RSTP will recover in seconds, whereas
smart RSTP (ring-only mode) will recover in milliseconds.
To configure Ring-Only mode, ensure the first three of the four situations described above
are met.
RSTP mode has to be enabled before any configuration to the ring-only mode.
The RSTP command enters the RSTP configuration mode and enables/disables RSTP. By
default, RSTP is disabled and has to be manually activated.
rstp
rstp <enable|disable>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–13

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

The syntax for the romode command on RSTP is shown below.

Example 13-5: Configuring smart RSTP, ring-only mode

ML800# rstp

ML800(rstp)##rstp enable
Successfully set the RSTP status

ML800(rstp)##romode show
RO-MODE status : Disabled
RO-MODE set on ports : NONE

ML800(rstp)##romode add port=1,2

Added Ports: 1,2

ML800(rstp)##romode enable
RSTP Ring Only Mode Enabled.

ML800(rstp)##romode show
RO-MODE status : Enabled
RO-MODE set on ports : 1,2

ML800(rstp)##romode disable
RSTP Ring Only Mode Disabled.

ML800(rstp)##romode show

13–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

13.3 Configuring STP/RSTP with EnerVista Secure Web

Management software

13.3.1 Normal RSTP

To setup and configure RSTP, select the Configure > RSTP menu items. In setting up RSTP
or STP, it is advised that the system defaults are used for weights and other parameters.
Only when specific ports are required to be the active link should the default values
change.
In the window below, RSTP or STP is disabled. The designated root is set to zero as RSTP is
disabled.

The RSTP bridge configuration parameters are defined below.

• Designated Root: Shows the MAC address of the bridge in the network elected or
designated as the root bridge. Normally, when STP is not enabled, the switch
designates itself as the root switch.
• Root Path Cost: A path cost is assigned to individual ports for the switch to determine
which ports are the forwarding points. A higher cost means more loops; a lower cost
fewer loops. More loops equal more traffic and a tree which takes a long time to
converge, resulting in a slower system
• Root Port: Indicates the port number, which is elected as the root port of the switch. A
root port of "0" indicates STP is disabled.
• Protocol: Indicates whether STP or RSTP is being used. It also indicates if RSTP is used
in Smart RSTP (ring-only mode) or normal mode.
• Bridge ID: Indicates the MAC address of the current bridge over which traffic will flow.
• Bridge Priority: Specifies the switch (bridge) priority value. This value is used along
with the switch MAC address to determine which switch in the network is the root
device. Lower values mean higher priority. The value ranges from 0 to 65535, with a
default of 32768
• Status: Indicates whether STP or RSTP is enabled.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–15

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

• Bridge Hello Time: When the switch is the root device, this is the time between
messages being transmitted. The value is from 1 to 10 seconds, with a default of 2.
• Bridge Forward Delay: Indicates the time duration the switch will wait from listening
to learning states and from learning to forwarding states. The value ranges from 4 to
30 seconds, with a default of 15.
• Bridge Max Age: This is the maximum time a message with STP information is allowed
by the switch before the switch discards the information and updates the address
table again. The value ranges from 6 to 40 seconds with a default 20.
• Hold Time: This is the minimum time period to elapse between the transmissions of
configuration BPDUs through a given LAN Port. At most one configuration BPDU shall
be transmitted in any hold time period. This parameter is a fixed parameter, with
values as specified in RSTP standard (3 seconds).
• Topology Change: A counter indicating the number of times topology has changed.
• Time since TC: Indicates time that has elapsed since the last topology change. Use
this in conjunction with uptime on the graphical display (screen shown after a
successful login) to find the frequency of the topology changes.
 Click on Edit to make any changes.
On this screen, you can select and enable STP or RSTP.

 Under protocol, select “Force to STP” if there are legacy or other third
party devices that do not support RSTP.
 Otherwise it is recommended to enable “Normal RSTP”.

13–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

Once again, if you are not familiar with the STP or RSTP parameter settings, is best to use
the default values.
 Simply enable RSTP (or STP) and let the system default values prevail.
After RSTP is enabled, the fields are updated.
 Note the Status, Time since TC, and Designated Root values.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–17

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

The port specific values for RSTP or STP are shown below.

 Click on the edit icon ( ) to edit the values for a specific port.
The columns in the above window are defined as follows:
• Port#: Indicates the port number. Value ranges from 1 to the maximum number of
ports in the switch.
• Port Type: Indicates the type of port and speed; TP indicates twisted-pair.
• Port State: Forwarding implies traffic is forwarded onto the next switch or device
connected the port. Disabled implies that the port may be turned off or the device
connected to it may be unplugged or turned off. Values can be Listening, Learning,
Forwarding, Blocking and Disabled.
• Path Cost: This is the assigned port cost value used for the switch to determine the
forwarding points. Values range from 1 to 2000000. The lower the value, the lower
the cost and hence the preferred route. The costs for different Ethernet speeds are
shown below. The STP path cost is compared to the RSTP path cost.
Table 13–2: Path cost defined in IEEE 802.1d and 802.1w
Port Type STP Path cost RSTP Path cost
10 Mbps 100 2 000 000
100 Mbps 19 200 000
1 Gbps 4 20 000
10 Gbps 2 2000

• Priority: STP uses this to determine which ports are used for forwarding. Lower the
number means higher priority. Value ranges from 0 to 255. Default is 128
• Edge Ports: RSTP offers edge port recognition, allowing ports at the edge of the
network to forward frames immediately after activation while at the same time
protecting them against loops.

13–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

• P2P Ports: set the "point-to-point" value to off on all ports that are connected to
shared LAN segments (i.e. connections to hubs). The default value is auto. P2P
ports would typically be end stations or computers on the network.
• Designated Root: MAC Address of the Root Bridge in the tree
• Status: status of STP/RSTP for the port.
The STP or RSTP values can be changed for each port as shown below.

Migration is enabled for all ports connected to other devices such as hubs, bridges and
switches known to support IEEE 802.1d STP services and cannot support RSTP services.
Status is normally enabled - in certain cases the Status can be set to disabled to turn off
RSTP or STP on that port.

13.3.2 Smart RSTP (Ring-Only Mode) with EnerVista Secure Web Management Software
A ring is a special case mesh structure. In many networks, network managers prefer to
create a ring structure for topological redundancy and simplicity. In a ring structure:
1. All switches in the network are GE Digital Energy switches.
2. RSTP is enabled on all the switches.
3. The topology is a ring.
4. All switches in the ring have been configured to use the ring-only mode (as
shown below).
5. All switches in the ring must use the same firmware revision.
The ring structure can demonstrate fast recovery times, typically faster than what RSTP
can recover from a single fault. In many situations RSTP will recover in seconds, whereas
smart RSTP (Ring-Only mode) will recover in milliseconds.
To configure ring-only mode, ensure the first three of the four situations described above
are met.
To enable ring-only mode, first

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–19

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

 Enable RSTP by setting the STP Type to RSTP in the Administration >
Set > STP Type menu:

 Select the Configuration > RSTP > Bridge RSTP menu as shown
below.

 Click the Edit button to configure RSTP.

 Once in Edit mode, change the Status to Enable.

13–20 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL

 Save Configuration.

...THEN SAVE

ENABLE STATUS...

To reset RSTP back to normal mode, select “Normal RSTP” for the Protocol setting. Save the
configuration by clicking on the icon.
 Select the Configuration > RSTP > RO Mode menu as shown below:

 Click the Edit button to configure RO Mode.

 Select the desired ports as shown below, then click OK to exit.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 13–21

RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL

Only 2 ports can be selected to Ring Only Mode.

Note

NOTE

 Select the Enabled option for the Status setting as shown below:

 Save the configuration by clicking on the icon.

13–22 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 14: Quality of Service

Quality of Service

14.1 QoS Overview

14.1.1 Description
Quality of Service (QoS) refers to the capability of a network to provide different priorities to
different types of traffic. Not all traffic in the network has the same priority. Being able to
differentiate different types of traffic and allowing this traffic to accelerate through the
network improves the overall performance of the network and provides the necessary
quality of service demanded by different users and devices. The primary goal of QoS is to
provide priority including dedicated bandwidth.

14.1.2 QoS Concepts

The MultiLink ML800 Managed Edge Switch supports QoS as specified in the IEEE 802.1p
and IEEE 802.1q standards. QoS is important in network environments where there are
time-critical applications, such as voice transmission or video conferencing, which can be
adversely effected by packet transfer delays or other latency in a network.
Most switches today implement buffers to queue incoming packets as well as outgoing
packets. In a queue mechanism, normally the packet which comes in first leaves first (FIFO)
and all the packets are serviced accordingly. Imagine, if each packet had a priority
assigned to it. If a packet with a higher priority than other packets were to arrive in a
queue, the packet would be given a precedence and moved to the head of the queue and
would go out as soon as possible. The packet is thus preempted from the queue and this
method is called preemptive queuing.
Preemptive queuing makes sense if there are several levels of priorities, normally more
than two. If there are too many levels, then the system has to spend a lot of time managing
the preemptive nature of queuing. IEEE 802.1p defines and uses eight levels of priorities.
The eight levels of priority are enumerated 0 to 7, with 0 the lowest priority and 7 the
highest.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 14–1

QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE

To make the preemptive queuing possible, most switches implement at least two queue
buffers. The MultiLink ML800 Managed Edge Switch has two priority queues, 1 (low) and 0
(high).When tagged packets enter a switch port, the switch responds by placing the packet
into one of the two queues, and depending on the precedence levels the queue could be
rearranged to meet the QoS requirements.

14.1.3 DiffServ and QoS

QoS refers to the level of preferential treatment a packet receives when it is being sent
through a network. QoS allows time sensitive packets such as voice and video, to be given
priority over time insensitive packets such as data. Differentiated Services (DiffServ or DS)
are a set of technologies defined by the IETF (Internet Engineering Task Force) to provide
quality of service for traffic on IP networks.
DiffServ is designed for use at the edge of an Enterprise where corporate traffic enters the
service provider environment. DiffServ is a layer-3 protocol and requires no specific layer-2
capability, allowing it to be used in the LAN, MAN, and WAN. DiffServ works by tagging
each packet (at the originating device or an intermediate switch) for the requested level of
service it requires across the network.

IP Header

DMAC SMAC Protocol ToS Data FCS

DiffservCode Points (DSCP) Unused

754725A1.CDR

FIGURE 14–1: ToS and DSCP

DiffServ inserts a 6-bit DiffServ code point (DSCP) in the Type of Service (ToS) field of the IP
header, as shown in the picture above. Information in the DSCP allows nodes to determine
the Per Hop Behavior (PHB), which is an observable forwarding behavior for each packet.
Per hop behaviors are defined according to:
• Resources required (e.g., bandwidth, buffer size)
• Priority (based on application or business requirements)
• Traffic characteristics (e.g., delay, jitter, packet loss)
Nodes implement PHBs through buffer management and packet scheduling mechanisms.
This hop-by-hop allocation of resources is the basis by which DiffServ provides quality of
service for different types of communications traffic.

14.1.4 IP Precedence
IP Precedence utilizes the three precedence bits in the IPv4 header's Type of Service (ToS)
field to specify class of service for each packet. You can partition traffic in up to eight
classes of service using IP precedence. The queuing technologies throughout the network
can then use this signal to provide the appropriate expedited handling.

14–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE

Data +FCS

ToS byte

3 bits

IP precedence 754726A1.CDR

FIGURE 14–2: IP Precedence ToS Field in an IP Packet Header

The three most significant bits (correlating to binary settings 32, 64, and 128) of the Type of
Service (ToS) field in the IP header constitute the bits used for IP precedence. These bits are
used to provide a priority from 0 to 7 for the IP packet.
Because only three bits of the ToS byte are used for IP precedence, you need to
differentiate these bits from the rest of the ToS byte.
The MultiLink ML800 Managed Edge Switch has the capability to provide QoS at Layer 2. At
Layer 2, the frame uses Type of Service (ToS) as specified in IEEE 802.1p. ToS uses 3 bits,
just like IP precedence, and maps well from Layer 2 to layer 3, and vice versa.
The switches have the capability to differentiate frames based on ToS settings. With two
queues present - high or low priority queues or buffers in MultiLink ML800 Managed Edge
Switch, frames can be placed in either queue and serviced via the weight set on all ports.
This placement of queues, added to the weight set plus the particular tag setting on a
packet allows each queue to have different service levels.
MultiLink ML800 Managed Edge Switch QoS implementations provide mapping of ToS (or IP
precedence) to Class of Service (CoS). A CoS setting in an Ethernet Frame is mapped to the
ToS byte of the IP packet, and vice versa. A ToS level of 1 equals a CoS level of 1. This
provides end-to-end priority for the traffic flow when MultiLink ML800 Managed Edge
Switchs are deployed in the network.

Not all packets received on a port have high priority. IGMP and BPDU packets have high
Note

priority by default.
NOTE
The MultiLink ML800 Managed Edge Switch has the capability to set the priorities based on
three different functions. They are
• Port QoS: assigns a high priority to all packets received on a port, regardless of the
type of packet.
• TAG QoS: if a packet contains a tag, the port on which the packet was received
then looks to see at which level that tag value is set. Regardless of the tag value, if
there is a tag, that packet is automatically assigned high priority (sent to the high
priority queue)
• ToS QoS: (Layer 3) when a port is set to ToS QoS, the most significant 6-bits of the
IPv4 packet (which has 64 bits) are used. If the 6 bits are set to ToS QoS for the
specific port number the packet went to, that packet is assigned high priority by
that port

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 14–3

QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE

14.2 Configuring QoS through the Command Line

Interface

14.2.1 Commands
The MultiLink ML800 Managed Edge Switch supports three types of QoS - Port based, Tag
based and ToS based.

QoS is disabled by default on the switch. QoS needs to be enabled and configured.
Note

NOTE
The qos command enters the QoS configuration mode.
qos
The usage of the setqos command varies depending on the type of QOS. For example, for
QOS type tag, the tag levels have to be set, and for QOS type ToS, the ToS levels have to be
set. If the priority field is not set, it then defaults to low priority. ToS has 64 levels and the
valid values are 0-63 and a tagged packet has 8 levels and the valid values are 0-7
setqos type=<port|tag|tos|none> port=<port|list|range> [priority=<high|low>] [tos=<0-
63|list|range>]
[tag=<0-7|list|range>]
Setting the type parameter to none will clear the QoS settings.
The set-weight command sets the port priority weight for All the ports. Once the weight
is set, all the ports will be the same weight across the switch. The valid value for weight is
0-7
set-weight weight=<0-7>
A weight is a number calculated from the IP precedence setting for a packet. This weight is
used in an algorithm to determine when the packet will be serviced
The show-portweight command displays the weight settings on a port.
show-portweight
As mentioned previously, the switch is capable of detecting higher-priority packets marked
with precedence by the IP forwarder and can schedule them faster, providing superior
response time for this traffic. The IP Precedence field has values between 0 (the default)
and 7. As the precedence value increases, the algorithm allocates more bandwidth to that
traffic to make sure that it is served more quickly when congestion occurs. The MultiLink
ML800 Managed Edge Switch can assign a weight to each flow, which determines the
transmit order for queued packets. In this scheme, lower weights (set on all ports) are
provided more service. IP precedence serves as a divisor to this weighting factor. For
instance, traffic with an IP Precedence field value of 7 gets a lower weight than traffic with
an IP Precedence field value of 3, and thus has priority in the transmit order.
Once the port weight is set, the hardware will interpret the weight setting for all ports as
outlined below (assuming the queues are sufficiently filled - if there are no packets, for
example, in the high priority queue, packets are serviced on a first come first served - FCFS
- basis from the low priority queue).

14–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE

Table 14–1: Port weight settings

Value Hardware traffic queue behavior
0 No priority - traffic is sent alternately from each
queue and packets are queued alternately in each
queue.
1 Two packets are sent from the HIGH priority queue
and one packet from LOW priority queue.
2 Four packets are sent from the HIGH priority queue
and one packet from LOW priority queue.
3 Six packets are sent from the HIGH priority queue
and one packet from LOW priority queue.
4 Eight packets are sent from the HIGH priority queue
and one packet from LOW priority queue.
5 Ten packets are sent from the HIGH priority queue
and one packet from LOW priority queue.
6 Twelve packets are sent from the HIGH priority queue
and one packet from LOW priority queue.
7 All packets are sent from the HIGH priority queue and
none are sent from LOW priority queue.

The show qos command displays the QoS settings

show qos [type=<port|tag|tos>] [port=<port|list|range>]
Sometimes it is necessary to change the priority of the packets going out of a switch. For
example, when a packet is received untagged and has to be transmitted with an addition
of the 802.1p priority tag, the tag can be assigned depending on the untag value set. For
example if the untag command is set to port=1 tag=2 priority=low, untagged packets
received on that port will be tagged with a priority low upon transmit.
The untag command defines the 802.1p user priority assigned to untagged received
packets to be transmitted as tagged from the priority queue.
set-untag port=<port|list|range> priority=<high|low> tag=<0-7>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 14–5

QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE

14.2.2 Example
The following example shows how to configure QoS.

Example 14-1: Configuring QoS

ML800#show port

Keys: E = Enable D = Disable

H = Half Duplex F = Full Duplex
M = Multiple VLAN's NA = Not Applicable
LI = Listening LE = Learning
F = Forwarding B = Blocking

Port Name Control Dplx Media Link Trunk Speed Part Auto VlanID GVRP STP
-----------------------------------------------------------------------------
1 A1 E H 10Tx DOWN No 10 No E 1 - -
2 A2 E H 10Tx DOWN No 10 No E 1 - -
3 A3 E F 100Fx DOWN No 100 No D 1 - -
4 A4 E F 100Fx DOWN No 100 No D 1 - -
5 A5 E F 100Fx DOWN No 100 No D 1 - -
6 A6 E F 100Fx DOWN No 100 No D 1 - -
All traffic on port 1 is sent to the
7 A7 E H 10Tx DOWN No 10 No E 1 - - high priority queue.

ML800#qos

ML800(qos)##setqos type=port port=1 priority=high

Successfully set QOS.

ML800(qos)##show qos type=port

14–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE

Configuring QoS (continued)

The queue behavior is set so that 8

ML800(qos)##setqos port=3 priority=high type=tag tag=5 high-priority packets and 1 low-priority
packet is sent out.

Successfully set QOS.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 14–7

QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE

Configuring QoS (continued)

Port priority Weight set to 1 High : 1 Low.

ML800(qos)##set-weight weight=4

ML800(qos)##show-portweight

Port priority Weight set to 8 High : 1 Low.

ML800(qos)##

14–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE

14.3 Configuring QoS with EnerVista Secure Web

Management software

14.3.1 Description
To access QoS settings,
 Select the Configuration > QoS menu items.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 14–9

QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE

 Select the Port and the type of QoS/ToS settings.

The following window illustrates the setting of port 1 for port-based
QoS with a high priority. Note the sections on Tag and TOS are
ignored for Port settings.

After the port QoS settings are completed, the changes are reflected on the QoS menu
screen. The port 1 QoS settings indicate high priority set.

14–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE

Next, a tag-based QoS is enabled on port 3. Note that only the menu area for the tag
setting is relevant.

After the Tag QoS settings are completed, the changes are reflected on the QoS menu
screen.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 14–11

QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE

In the following window, a ToS is enabled on Port 5. As before, only the ToS level settings
are relevant.

Note that the different settings are clear from the window below. Port 1 has port-based
QoS, port 3 has tag-based QoS, and port 5 is using ToS.

 After all changes are made, save the changes using the save icon
( ).

14–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 15: IGMP

IGMP

15.1 Overview

15.1.1 Description
Internet Group Management Protocol (IGMP) is defined in RFC 1112 as the standard for IP
multicasting in the Internet. It is used to establish host memberships in particular multicast
groups on a single network. The mechanisms of the protocol allows a host to inform its
local router, using Host Membership Reports that it wants to receive messages addressed
to a specific multicast group. All hosts conforming to level 2 of the IP multicasting
specification require IGMP.

15.1.2 IGMP Concepts

The ML800 supports IGMP L2 standards as defined by RFC 1112. IGMP is disabled by
default and needs to be enabled on the MultiLink ML800 Managed Edge Switch. IP
multicasting is defined as the transmission of an IP datagram to a “host group”, a set of
zero or more hosts identified by a single IP destination address. A multicast datagram is
delivered to all members of its destination host group with the same “best-efforts”
reliability as regular unicast IP datagrams, i.e. the datagram is not guaranteed to arrive at
all members of the destination group or in the same order relative to other datagrams.
The membership of a host group is dynamic; that is, hosts may join and leave groups at
any time. There is no restriction on the location or number of members in a host group, but
membership may be restricted to only those hosts possessing a private access key. A host
may be a member of more than one group at a time. A host need not be a member of a
group to send datagrams to it.
A host group may be permanent or transient. A permanent group has a well-known,
administratively assigned IP address. It is the address and not the membership that is
permanent – at any time, a permanent group may have any number of members, even
zero. On the other hand, a transient group is dynamically assigned an address when the
group is created, at the request of a host. A transient group ceases to exist, and its address
becomes eligible for reassignment, when its membership drops to zero.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 15–1

IGMP CHAPTER 15: IGMP

The creation of transient groups and the maintenance of group membership is the
responsibility of “multicast agents”, entities that reside in internet gateways or other
special-purpose hosts. There is at least one multicast agent directly attached to every IP
network or sub-network that supports IP multicasting. A host requests the creation of new
groups, and joins or leaves existing groups by exchanging messages with a neighboring
agent.
The Internet Group Management Protocol (IGMP) is an internal protocol of the Internet
Protocol (IP) suite. IP manages multicast traffic by using switches, multicast routers, and
hosts that support IGMP (in the MultiLink ML800 Managed Edge Switch implementation of
IGMP, a multicast router is not necessary as long as a switch is configured to support IGMP
with the querier feature enabled). A set of hosts, routers, and/or switches that send or
receive multicast data streams to or from the same source(s) is termed a multicast group,
and all devices in the group use the same multicast group address. The multicast group
running version 2 of IGMP uses three fundamental types of messages to communicate:
• Query: A message sent from the querier (multicast router or switch) asking for a
response from each host belonging to the multicast group. If a multicast router
supporting IGMP is not present, then the switch must assume this function in order
to elicit group membership information from the hosts on the network (if you need
to disable the querier feature, you can do so using the IGMP configuration MIB).
• Report: A message sent by a host to the querier to indicate that the host wants to
be or is a member of a given group indicated in the report message.
• Leave Group: A message sent by a host to the querier to indicate that the host has
ceased to be a member of a specific multicast group. Thus, IGMP identifies
members of a multicast group (within a subnet) and allows IGMP-configured hosts
(and routers) to join or leave multicast groups.
When IGMP is enabled on the MultiLink ML800 Managed Edge Switch, it examines the IGMP
packets it receives to:
• Learn which ports are linked to IGMP hosts and multicast routers/queriers
belonging to any multicast group.
• Become a querier if a multicast router/querier is not discovered on the network.
Once the switch learns the port location of the hosts belonging to any particular multicast
group, it can direct group traffic to only those ports, resulting in bandwidth savings on
ports where group members do not reside. The following example illustrates this operation.

15–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 15: IGMP IGMP

The figure below shows a network running IGMP.

FIGURE 15–1: Advantages of using IGMP

In the above diagram:

• PCs 1 and 4, switch 2, and all of the routers are members of an IP multicast group
(the routers operate as queriers).
• Switch 1 ignores IGMP traffic and does not distinguish between IP multicast group
members and non-members. Thus, sends large amounts of unwanted multicast
traffic to PCs 2 and 3.
• Switch 2 is recognizing IGMP traffic and learns that PC 4 is in the IP multicast group
receiving multicast data from the video server (PC X). Switch 2 then sends the
multicast data only to PC 4, thus avoiding unwanted multicast traffic on the ports
for PCs 5 and 6.
The next figure (below) shows a network running IP multicasting using IGMP without a
multicast router. In this case, the IGMP-configured switch runs as a querier. PCs 2, 5, and 6
are members of the same IP multicast group. IGMP is configured on switches 3 and 4.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 15–3

IGMP CHAPTER 15: IGMP

Either of these switches can operate as querier because a multicast router is not present
on the network. (If an IGMP switch does not detect a querier, it automatically assumes this
role, assuming the querier feature is enabled-the default-within IGMP.)

FIGURE 15–2: Isolating multicast traffic in a network

In the above figure, the multicast group traffic does not go to switch 1 and beyond. This is
because either the port on switch 3 that connects to switch 1 has been configured as
blocked or there are no hosts connected to switch 1 or switch 2 that belong to the
multicast group.
For PC 1 to become a member of the same multicast group without flooding IP multicast
traffic on all ports of switches 1 and 2, IGMP must be configured on both switches 1 and 2,
and the port on switch 3 that connects to switch 1 must be unblocked.

15.1.3 IP Multicast Filters

IP multicast addresses occur in the range from 224.0.0.0 through 239.255.255.255 (which
corresponds to the Ethernet multicast address range of 01005e-000000 through 01005e-
7fffff in hexadecimal.) Devices such as the MultiLink ML800 Managed Edge Switch having
static Traffic/Security filters configured with a “Multicast” filter type and a “Multicast
Address” in this range will continue in effect unless IGMP learns of a multicast group
destination in this range. In that case, IGMP takes over the filtering function for the
multicast destination address(es) for as long as the IGMP group is active. If the IGMP group
subsequently deactivates, the static filter resumes control over traffic to the multicast
address formerly controlled by IGMP.

15.1.4 Reserved Addresses Excluded from IP Multicast (IGMP) Filtering

Traffic to IP multicast groups in address range 224.0.0.0 to 224.0.0.255 will always be
flooded because addresses in this range are “well known” or “reserved”. Thus, if IP Multicast
is enabled and there is an IP multicast group within the reserved address range, traffic to
that group will be flooded instead of filtered by the switch.

15–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 15: IGMP IGMP

15.1.5 IGMP Support

The MultiLink ML800 Managed Edge Switch supports IGMP version 1 and version 2. The
switch can act either as a querier or a nonquerier. The querier router periodically sends
general query messages to solicit group membership information. Hosts on the network
that are members of a multicast group send report messages. When a host leaves a group,
it sends a leave group message. The difference between Version 1 and Version 2 is that
version 1 does not have a “Leave” mechanism for the host. The MultiLink ML800 Managed
Edge Switch does pruning when there is a leave message or a time expires on a port, we
prune the multicast group membership on that port.
1. The MultiLink ML800 Managed Edge Switch supports only the default VLAN. It
can be enabled within a port VLAN, tagged VLAN, or no VLAN. It can snoop up
to 256 multi-cast Groups.
2. IGMP is disabled as a default. It has to be enabled to leverage the benefits of
IGMP.
3. The MultiLink ML800 Managed Edge Switch supports only the default VLAN. It
can be enabled within a port VLAN, tagged VLAN, or no VLAN. It can snoop up
to 256 multi-cast Groups.
4. IGMP works only on default VLAN (DEFAULT_VLAN or VID = 1).

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 15–5

IGMP CHAPTER 15: IGMP

15.2 Configuring IGMP through the Command Line

Interface

15.2.1 Commands
The igmp command enters IGMP configuration mode and enables or disables IGMP on the
switch.
igmp
igmp <enable/disable>
The show igmp command displays the IGMP status.
show igmp
The following command sequence illustrates how to enable and query the status of IGMP.
ML800# igmp
ML800(igmp)## igmp enable
IGMP is enabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Enabled
Querier Interval : 125
Querier Response Interval : 10
Multicasting Unknown Streams : Enable
ML800(igmp)## igmp disable
IGMP is disabled
ML800(igmp)## show igmp
IGMP State : Disabled
ImmediateLeave : Disabled
Querier : Enabled
Querier Interval : 125
Querier Response Interval : 10
Multicasting Unknown Streams : Enable
ML800(igmp)##
The output of the show igmp command provides the following useful information:
• IGMP State shows if IGMP is turned on (Enable) or off (Disable).
• Immediate Leave provides a mechanism for a particular host that wants to leave
a multicast group. It disables the port (where the leave message is received) ability
to transmit multicast traffic.
• Querier shows where the switch is a querier or a non-querier. In our example, the
switch is the querier.
• Querier Interval shows the time period in seconds on which the switch sends
general host-query messages.
• Querier Response Interval specifies maximum amount of time in seconds that
can elapse between when the querier sends a host-query message and when it
receives a response from a host.

15–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 15: IGMP IGMP

• Multicasting Unknown Streams shows if the control of multicast streams is on

(Enabled) or off (Disabled).
The show-group command displays the multicast groups.
show-group
The following command sequence illustrates how to display IGMP groups:
ML800(igmp)## show-group
GroupIp PortNo Timer LeavePending
----------------------------------------
224.1.0.1 1 155 0
224.0.1.40 1 155 0
ML800(igmp)##
The output of the show-group command displays the following information:
• Group IP column shows the multicast groups.
• Port No shows the port where the multicast group is being detected.
• Timer shows the amount of time left in seconds before the group port will be
deleted (or will not be able to route multicast traffic) if the switch does not receive a
membership report.
• Leave Pending column shows the number of leave messages received from this
port
Every port can be individually set to three different IGMP modes - auto, block and forward.
• Auto - lets IGMP control whether the port should or should not participate sending
multicast traffic
• Block - manually configures the port to always block multicast traffic
• Forward - manually configures the port to always forward multicast traffic
To set the port characteristics, use the set-port command in the IGMP configuration
mode.
set-port port=< port|list|range> mode=<auto|forward|block>
The show-port command displays the port characteristics for IGMP.
show-port
The show-router command displays detected IGMP-enabled router ports.
show-router
The set-leave command enables or disables the switch to immediately process a host
sending a leave message rather that wait for the timer to expire.
set-leave <enable|disable>
The set-querier command enables or disables a switch as IGMP querier.
set-querier <enable|disable>
The set-qi command sets the IGMP querier router to periodically send general host-
query messages. These messages are sent to ask for group membership information. This
is sent to the all-system multicast group address, 224.0.0.1. The valid range can be from 60
to 127 seconds, with a default of 125.
set-qi interval=<value>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 15–7

IGMP CHAPTER 15: IGMP

The set-qri command sets the query response interval representing the maximum
amount of time that can elapse between when the querier router sends a host-query
message and when it receives a response from a host. The range can be from 2 to 270
seconds, with a default of 10. Restrictions apply to the maximum value because of an
internal calculation that is dependent on the value of the query interval.
set-qri interval=<value>

15.2.2 Example
The following example shows how to configure IGMP.

Example 15-1: Configuring IGMP

ML800(igmp)## set-port port=2-4 mode=forward

ML800(igmp)## show-router
RouterIp PortNo Timer
---------------------------------
10.21.1.250 1 25

(continued on next page)

15–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 15: IGMP IGMP

Configuring IGMP (continued)

ML800(igmp)## set-leave enable

IGMP immediate leave status is enabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Enabled
Querier : Enabled
Querier Interval : 125
Querier Response Interval : 10
Multicasting Unknown Streams : Enabled
ML800(igmp)## set-leave disable
IGMP immediate leave status is disabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Enabled
Querier Interval : 125
Querier Response Interval : 10
Multicasting Unknown Streams : Enabled
ML800(igmp)## set-querier enable
IGMP querier status is enabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Enabled
Querier Interval : 125
Querier Response Interval : 10
Multicasting Unknown Streams : Enabled
ML800(igmp)## set-querier disable
IGMP querier status is disabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Disabled
Querier Interval : 125
Querier Response Interval : 10
Multicasting Unknown Streams : Enabled
ML800(igmp)## set-qi interval=127
Query interval successfully set
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Disabled
Querier Interval : 127
Querier Response Interval : 10
Multicasting Unknown Streams : Enabled
ML800(igmp)## set-qri interval=11

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 15–9

IGMP CHAPTER 15: IGMP

Configuring IGMP (continued)

ML800(igmp)## show igmp

IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Disabled
Querier Interval : 127
Querier Response Interval : 11
Multicasting Unknown Streams : Enabled
ML800(igmp)## mcast disable
MCAST is disabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Disabled
Querier Interval : 127
Querier Response Interval : 11
Multicasting Unknown Streams : Disabled
ML800(igmp)## mcast enable
MCAST is enabled
ML800(igmp)## show igmp
IGMP State : Enabled
ImmediateLeave : Disabled
Querier : Disabled
Querier Interval : 127

15–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 15: IGMP IGMP

15.3 Configuring IGMP with EnerVista Secure Web

Management software

15.3.1 Example
For configuring IGMP,
 Select the Configuration > IGMP menu item.
The menu allows the IGMP parameters to be set and provides
information on IGMP groups and routers.

The menu allows the IGMP parameters described earlier to be set. It also provides the
necessary information of IGMP groups and routers.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 15–11

IGMP CHAPTER 15: IGMP

 Click on the Edit button to edit the IGMP parameters.

This screen also enables and disables IGMP.

Changes are reflected on the Configuration > IGMP > Information screen. The groups and
routers screen displays the IGMP Groups and IGMP Routers information. All edits to IGMP
are done through the Information screen.

15–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 16: SNMP

SNMP

16.1 Overview

16.1.1 Description
SImple Network Management Protocol (SNMP) enables management of the network. There
are many software packages which provide a graphical interface and a graphical view of
the network and its devices. These graphical interface and view would not be possible
without SNMP. SNMP is thus the building block for network management.

16.1.2 SNMP Concepts

SNMP provides the protocol to extract the necessary information from a networked device
and display the information. The information is defined and stored in a Management
Information Base (MIB). MIB is the “database” of the network management information.
SNMP has evolved over the years (since 1988) using the RFC process. Several RFCs define
the SNMP standards. The most common standards for SNMP are SNMP v1 (the original
version of SNMP); SNMP v2 and finally SNMP v3.
SNMP is a poll based mechanism. SNMP manager polls the managed device for
information and display the information retrieved in text or graphical manner. Some
definitions related to SNMP are
• Authentication - The process of ensuring message integrity and protection against
message replays. It includes both data integrity and data origin authentication
• Authoritative SNMP engine - One of the SNMP copies involved in network
communication designated to be the allowed SNMP engine which protects against
message replay, delay, and redirection. The security keys used for authenticating and
encrypting SNMPv3 packets are generated as a function of the authoritative SNMP
engine's engine ID and user passwords. When an SNMP message expects a response
(for example, get exact, get next, set request), the receiver of these messages is
authoritative. When an SNMP message does not expect a response, the sender is
authoritative
• Community string - A text string used to authenticate messages between a
management station and an SNMP v1/v2c engine

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–1

SNMP CHAPTER 16: SNMP

• Data integrity - A condition or state of data in which a message packet has not been
altered or destroyed in an unauthorized manner
• Data origin authentication - The ability to verify the identity of a user on whose
behalf the message is supposedly sent. This ability protects users against both
message capture and replay by a different SNMP engine, and against packets
received or sent to a particular user that use an incorrect password or security level
• Encryption - A method of hiding data from an unauthorized user by scrambling the
contents of an SNMP packet
• Group - A set of users belonging to a particular security model. A group defines the
access rights for all the users belonging to it. Access rights define what SNMP objects
can be read, written to, or created. In addition, the group defines what notifications a
user is allowed to receive
• Notification host - An SNMP entity to which notifications (traps and informs) are to be
sent
• Notify view - A view name (not to exceed 64 characters) for each group that defines
the list of notifications that can be sent to each user in the group
• Privacy - An encrypted state of the contents of an SNMP packet where they are
prevented from being disclosed on a network. Encryption is performed with an
algorithm called CBC-DES (DES-56)
• Read view - A view name (not to exceed 64 characters) for each group that defines
the list of object identifiers (OIDs) that are accessible for reading by users belonging to
the group
• Security level - A type of security algorithm performed on each SNMP packet. The
three levels are: noauth, auth, and priv. noauth authenticates a packet by a string
match of the user name. auth authenticates a packet by using either the HMAC MD5
algorithms. priv authenticates a packet by using either the HMAC MD5 algorithms and
encrypts the packet using the CBC-DES (DES-56) algorithm.
• Security model - The security strategy used by the SNMP agent. Currently, ML800
supports three security models: SNMPv1, SNMPv2c, and SNMPv3.
• Simple Network Management Protocol (SNMP) - A network management protocol
that provides a means to monitor and control network devices, and to manage
configurations, statistics collection, performance, and security.
• Simple Network Management Protocol Version 2c (SNMPv2c) - The second version
of SNMP, it supports centralized and distributed network management strategies, and
includes improvements in the Structure of Management Information (SMI), protocol
operations, management architecture, and security.
• SNMP engine - A copy of SNMP that can either reside on the local or remote device.
• SNMP group - A collection of SNMP users that belong to a common SNMP list that
defines an access policy, in which object identification numbers (OIDs) are both read-
accessible and write-accessible. Users belonging to a particular SNMP group inherit all
of these attributes defined by the group.
• SNMP user - A person for which an SNMP management operation is performed. The
user is the person on a remote SNMP engine who receives the information.
• SNMP view - A mapping between SNMP objects and the access rights available for
those objects. An object can have different access rights in each view. Access rights
indicate whether the object is accessible by either a community string or a user.
• Write view - A view name (not to exceed 64 characters) for each group that defines
the list of object identifiers (OIDs) that are able to be created or modified by users of
the group.

16–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

16.1.3 Traps
The traps supported by MNS are as follows:
SNMP Traps: Warm Start, Cold Start, Link Up, Link Down, Authentication Failure.
RMON Traps: Rising Alarm, Falling Alarm for RMON groups 1, 2, 3, and 9 (Statistics, Events,
Alarms, and History)
Enterprise Traps: Intruder

16.1.4 Standards
There are several RFC’s defining SNMP. MNS supports the following RFC’s and standards
SNMPv1 standards
• Security via configuration of SNMP communities
• Event reporting via SNMP
• Managing the switch with an SNMP network management tool Supported
Standard MIBs include:
• SNMP MIB-II (RFC 1213)
• Bridge MIB (RFC 1493) (ifGeneralGroup, ifRcvAddressGroup, ifStackGroup)
• RMON MIB (RFC 1757)
• RMON: groups 1, 2, 3, and 9 (Statistics, Events, Alarms, and History)
• Version 1 traps (Warm Start, Cold Start, Link Up, Link Down, Authentication Failure,
Rising Alarm, Falling Alarm)
RFC 1901-1908 – SNMPv2
• RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working Group
• RFC 1902, Structure of Management Information for Version 2 of the Simple
Network Management Protocol (SNMPv2). SNMPv2 Working Group
• RFC 1903, Textual Conventions for Version 2 of the Simple Network Management
Protocol (SNMPv2). SNMPv2 Working Group
• RFC 1904, Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2). SNMPv2 Working Group
• RFC 1905, Protocol Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2). SNMPv2 Working Group
• RFC 1906, Transport Mappings for Version 2 of the Simple Network Management
Protocol (SNMPv2)
• RFC 1907, Management Information Base for Version 2 of the Simple Network
Management Protocol (SNMPv2). SNMPv2 Working Group
• RFC 1908, Coexistence between Version 1 and Version 2 of the Internet-standard
Network Management Framework. SNMPv2 Working Group
RFC 2271-2275 – SNMPv3
• RFC 2104, Keyed Hashing for Message Authentication
• RFC 2271, An Architecture for Describing SNMP Management Frameworks
• RFC 2272, Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)
• RFC 2273, SNMPv3 Applications

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–3

SNMP CHAPTER 16: SNMP

• RFC 2274, User-Based Security Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)
• RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)

16–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

16.2 Configuring SNMP through the Command Line

Interface

16.2.1 Commands
There are several commands and variable which can be set for configuring SNMP. The
basic SNMP v1 parameters can be set by referring to the section on System Parameters.
Most commands here refer to SNMP v3 commands and how the variables for SNMP v3 can
be configured.
The snmp command enters the SNMP configuration mode.
snmp
The snmpv3 command enters the SNMP V3 configuration mode. It is still necessary to
enable SNMP V3 by using the set snmp command after entering configuration mode.
snmpv3
The set snmp command defines the SNMP version. The ML800 supports all versions (v1,
v2 and v3) or only v1. By default, SNMP v1only is enabled.
set snmp type=<v1|all>
The show snmp command displays the SNMP configuration information.
show snmp
The setvar command sets the system name, contact and location. All parameters are
optional but a user must supply at least one parameter.
setvar [sysname|syscontact|syslocation]=<string>
The quickcfg command automatically configures a default VACM (view-based access
control model). This allows any manager station to access the ML800 either via SNMP v1,
v2c or v3. The community name is “public”. This command is only intended for first time
users and values can be changed by administrators who want more strict access.
quickcfg
The engineid command allows the user to change the engine ID. Every agent has to
have an engineID (name) to be able to respond to SNMPv3 messages.
engineid string=<string>
The authtrap command enables or disables authentication traps generation.
authtrap <enable|disable>
The show-authtrap command displays the current value of authentication trap status.
show-authtrap
The deftrap command defines the default community string to be used when sending
traps. When user does not specify the trap community name when setting a trap station
using the trap command, the default trap community name is used.
deftrap community=<string>
The show-deftrap command displays the current value of default trap.
show-deftrap
The trap command defines the trap and inform manager stations. The station can receive
v1, v2 traps and/or inform notifications. An inform notification is an acknowledgments that
a trap has been received. A user can add up to 5 stations.
trap <add|delete> id=<id> [type=<v1|v2|inform>] [host=<host-ip>]
[community=<string>] [port=<1-65534>]

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–5

SNMP CHAPTER 16: SNMP

The show-trap command shows the configured trap stations in tabular format. The id
argument is optional and is the number corresponding to the trap entry number in the
table.
show-trap [id=<id#>]
The com2sec command specifies the mapping from a source/community pair to a
security name. Up to 10 entries can be specified. This part of the View based Access
Control Model (VACM) as defined in RFC 2275.
com2sec <add|delete> id=<id> [secname=<name>] [source=<source>]
[community=<community>]
The group command defines the mapping from sec model or a sec name to a group. A
sec model is one of v1, v2c, or usm. Up to 10 entries can be specified. This part of the View
based Access Control Model (VACM) as defined in RFC 2275.
group <add|delete> id=<id> [groupname=<name>] [model=<v1|v2c|usm>]
[com2secid=<com2sec-id>]
The show-group command displays all or specific group entries. The id argument is
optional and is the number corresponding to the group entry number in the table
show-group [id=<id>]
The view command defines a manager or group or manager stations what it can access
inside the MIB object tree. Up to 10 entries can be specified. This part of the View based
Access Control Model (VACM) as defined in RFC 2275
view <add|delete> id=<id> [viewname=<name>] [type=<included|excluded>]
[subtree=<oid>] [mask=<hex-string>]
The show-view command display all or specific view entries. The id argument is optional
and is the number corresponding to the view entry number in the table.
show-view [id=<id>]
The user command adds user entries. The ML800 allows up to 5 users to be added.
Currently, the ML800 agent only support noauth and auth-md5 for v3 authentication and
auth-des for priv authentication.
user <add|delete> id=<id> [username=<name>] [usertype=<readonly|readwrite>]
[authpass=<pass-phrase>]
[privpass=<pass-phrase>] [level=<noauth|auth|priv>] [subtree=<oid>]
The show-user command displays all or specific view entries. The id is optional and is the
number corresponding to the view entry number in the table.
show-user [id=<id>]

16.2.2 Example
The following example shows how to configure SNMP.

16–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

Example 16-1: Configuring SNMP

ML800# set snmp type=v1

SNMP version support is set to "v1"
ML800# show snmp
SNMP CONFIGURATION INFORMATION
------------------------------
SNMP Get Community Name : public
SNMP Set Community Name : private
SNMP Trap Community Name : public
AuthenTrapsEnableFlag : disabled
SNMP Access Status : enabled
SNMP MANAGERS INFO
------------------
SNMP TRAP STATIONS INFO
-----------------------
ML800# set snmp type=all
SNMP version support is set to "v1, v2c, v3"
ML800# show snmp
SNMP v3 Configuration Information
=============================
System Name : ML800
System Location : Markham, ON
System Contact : multilin.tech@ge.com
Authentication Trap : Disabled
Default Trap Comm. : public
V3 Engine ID : Multi_Switch_Engine
ML800# snmpv3
ML800(snmpv3)## setvar sysname=ML800 syscontact=admin syslocation=
ML800(snmpv3)# quickcfg
This will enable default VACM.
Do you wish to proceed? ['Y' or 'N' ] Y
Quick configuration done, default VACM enabled
ML800(snmpv3)## engineid string=Multi_1200
Engine ID is set successfully
ML800(snmpv3)## authtrap enable
Authentication trap status is set successfully
ML800(snmpv3)## show-authtrap
Authentication Trap Status: Enabled
ML800(snmpv3)## deftrap community=mysecret
Default trap community is set successfully
ML800(snmpv3)## show-deftrap

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–7

SNMP CHAPTER 16: SNMP

Configuring SNMP (continued)

ML800(snmpv3)## trap add id=1 type=v1 host=3.94.200.107

Entry is added successfully
ML800(snmpv3)## show-trap
ID Trap Type Host IP Community Port
================================================
1 v1 3.94.200.107 -- --
2 -- -- -- --
3 -- -- -- --
4 -- -- -- --
5 -- -- -- --
ML800(snmpv3)## show-trap id=1
Trap ID : 1
Trap Type : v1
Host IP : 3.94.200.107
Community : --
Auth. Type : --
ML800(snmpv3)## com2sec add id=1 secname=public source=default com
Entry is added successfully
ML800(snmpv3)## com2sec add id=2
ERROR: "secname" parameter is required for "add" directive
ML800(snmpv3)## com2sec add id=2 secname=BCM
Entry is added successfully
ML800(snmpv3)## show-com2sec
ID Sec. Name Source Community
=============================================
1 public default public
2 BCM default public
3 -- -- --
4 -- -- --
5 -- -- --
6 -- -- --
7 -- -- --
8 -- -- --
9 -- -- --
10 -- -- --
ML800(snmpv3)## show-com2sec id=2
Com2Sec ID : 2
Security Name : BCM
Source : default
Community : public
ML800(snmpv3)## group add id=1 groupname=v1 model=v1 com2secid=1
Entry is added successfully

(continued on next page)

16–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

Configuring SNMP (continued)

ML800(snmpv3)## show-group
ID Group Name Sec. Model Com2Sec ID
=============================================
1 v1 v1 1
2 public v2c 1
3 public usm 1
4 -- -- --
5 -- -- --
6 -- -- --
7 -- -- --
8 -- -- --
9 -- -- --
10 -- -- --
ML800(snmpv3)## show-group id=1
Group ID : 1
Group Name : v1
Model : v1
Com2Sec ID : 1
ML800(snmpv3)## view add id=1 viewname=all type=included subtree=.1
Entry is added successfully
ML800(snmpv3)## show-view
ID View Name Type Subtree Mask
===============================================
1 all included 1 ff
2 -- -- -- --
3 -- -- -- --
4 -- -- -- --
5 -- -- -- --
6 -- -- -- --
7 -- -- -- --
8 -- -- -- --
9 -- -- -- --
10 -- -- -- --
ML800(snmpv3)## show-view id=1
View ID : 1
View Name : all
Type : included
Subtree : .1
Mask : ff
ML800(snmpv3)## access add id=1 accessname=v1 model=v1 level=noauth read=1 writ
notify=none
Entry is added successfully

(continued on next page)

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–9

SNMP CHAPTER 16: SNMP

Configuring SNMP (continued)

ML800(snmpv3)## show-access
ID View Name Model Level R/View W/View N/View Context Prefix
=================================================================================
1 v1 v1 noauth 1 none none "" exact
2 -- -- -- -- -- -- -- --
3 -- -- -- -- -- -- -- --
4 -- -- -- -- -- -- -- --
5 -- -- -- -- -- -- -- --
6 -- -- -- -- -- -- -- --
7 -- -- -- -- -- -- -- --
8 -- -- -- -- -- -- -- --
9 -- -- -- -- -- -- -- --
10 -- -- -- -- -- -- -- --
ML800(snmpv3)## show-access id=1
Access ID : 1
Access Name : v1
Sec. Model : v1
Sec. Level : noauth
Read View ID : 1
Write View ID : none
Notify View ID : none
Context : ""
Prefix : exact
ML800(snmpv3)## user add id=1 username=jsmith usertype=readwrite authpass=something
Entry is added successfully
ML800(snmpv3)## show-user
ID User Name UType AuthPass PrivPass AType Level Subtree
=================================================================================
1 jsmith RW something -- MD5 auth --
2 -- -- -- -- -- -- --
3 -- -- -- -- -- -- --
4 -- -- -- -- -- -- --
5 -- -- -- -- -- -- --
ML800(snmpv3)## show-user id=2
ERROR: Entry is not active
ML800(snmpv3)## show-user id=1
User ID : 1
User Name : jsmith
User Type : read-write
Auth. Pass : something
Priv. Pass :
Auth. Type : MD5
Auth. Level : auth
Subtree :
ML800(snmpv3)## exit
ML800#

16–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

16.3 Configuring SNMP with EnerVista Secure Web

Management software

16.3.1 Example
Most SNMP v1 capabilities can be set using the EnerVista Secure Web Management
software. For SNMP v2 and v3 parameters, please refer to Configuring SNMP through the
Command Line Interface on page 16–5.
SNMP variables are used in conjunction with Alert definitions. Alert Definitions are covered
in the next chapter.
To configure SNMP,
 Select the Configuration > SNMP menu item.

 Use the Edit button to change the SNMP community parameters.

 Use the Add buttons to add the management and trap receivers.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–11

SNMP CHAPTER 16: SNMP

The following window illustrates changes to the SNMP community parameters. It is

recommended to change the community strings from the default values of public and
private to other values.

 When done changing the community strings, click OK.

Multiple managers can be added as shown below.
 When adding SNMP manager stations, click on the Add button on
the SNMP menu screen.
 Make sure that each station can be pinged from the switch by using
the Configuration > Ping menu.

16–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

 When done adding stations, click OK.

 When adding SNMP trap receivers, click on the Add button on the
SNMP menu screen.
 Make sure that each station can be pinged from the switch by using
the Administration > Ping menu.
 Determine which sorts of traps each station will receive, as shown
above. If not sure, select all three types.
 When done adding trap receivers, click OK.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–13

SNMP CHAPTER 16: SNMP

Note the different types of trap receivers added.

Stations can be deleted using the delete icon ( ). To change the stations characteristics
or IP addresses, it is recommended to delete the station and add a new one.
 After all changes are made, save the changes using the save icon
( ).

16–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 16: SNMP SNMP

16.4 Configuring RMON

16.4.1 Description
The switch supports RMON (Remote Monitoring) on all connected network segments. This
allows for troubleshooting and optimizing your network. The MultiLink ML800 Managed
Edge Switch provides hardware-based RMON counters. The switch manager or a network
management system can poll these counters periodically to collect the statistics in a
format that compiles with the RMON MIB definition.
The following RMON groups are supported:
• Ethernet statistics group - maintains utilization and error statistics for the switch
port being monitored.
• History group - gathers and stores periodic statistical samples from previous
statistics group.
• Alarm group - allows a network administrator to define alarm thresholds for any
MIB variable.
• Log and event group - allows a network administrator to define actions based on
alarms. SNMP traps are generated when RMON alarms are triggered.

16.4.2 Commands
The following RMON communities, when defined, enable the specific RMON group as show
above. The rmon command enter the RMON configuration mode to setup RMON groups
and communities.
rmon
The history command defines the RMON history group and the community string
associated with the group.
history def-owner=<string> def-comm=<string>
The statistics command defines the RMON statistics group and the community string
associated with the group.
statistics def-owner=<string>
def-comm=<string>
The alarm command defines the RMON alarm group and the community string
associated with the group.
alarm def-owner=<string> def-comm=<string>
The event command defines the RMON event group and the community string
associated with the group.
event def-owner=<string> def-comm=<string>
The show rom command lists the specific RMON data as defined by the group type.
show rmon <stats|hist|event|alarm>

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 16–15

SNMP CHAPTER 16: SNMP

The following command sequence illustrates how to configure RMON groups.

ML800(rmon)## rmon
ML800(rmon)## event def-owner=test def-comm=somestring
RMON Event Default Owner is set
RMON Event Default Community is set
ML800(rmon)## show rmon event
RMON Event Default Owner : test
RMON Event Default Community : somestring
ML800(rmon)## exit
ML800#

16–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 17: Miscellaneous

Miscellaneous commands

17.1 E-mail

17.1.1 Description
SMTP (RFC 821) is a TCP/IP protocol used in sending e-mail. However, since it's limited in its
ability to queue messages at the receiving end, it's usually used with one of two other
protocols, POP3 or Internet Message Access Protocol (IMAP) that lets the user save
messages in a server mailbox and download them as needed from the server. In other
words, users typically use a program that uses SMTP for sending e-mails (out going - e.g.
replying to an e-mail message) and either POP3 or IMAP for receiving messages that have
been arrived from the outside world. While SMTP (and its related protocols such as POP3,
IMAP etc.) are useful transports for sending and receiving e-mails, it is extremely beneficial
for a network administrator to receive e-mails in case of faults and alerts. The MultiLink
ML800 Managed Edge Switch can be setup to send and e-mail alert when a trap is
generated.
If this capability is used, please ensure that SPAM filters and other filters are not set to
delete these e-mails.
GE Digital Energy recommends that a rule be setup on the mail server so that all e-mails
indicating SNMP faults are automatically stored in a folder or redirected to the necessary
administrators.
The SNMP alerts can be configured using the MultiLink Switch Software for the following:
• Send e-mail alert according to the configuration rules when a specific event
category happens.
• Send e-mail alert according to the configuration rules when a specific trap SNMP
trap category happens.
• Provide configuration and customization commands for users to specify SMTP
server to connect to, TCP ports, user recipients and filters.
• The SMTP alerts provide the following capabilities:
• SMTP alerts can be enabled or disabled globally.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–1

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

• User can defined a global default SMTP server identified by its IP address, TCP port
and retry count.
• User can add up to five SMTP alert recipients. Each recipient is identified by an ID
and e-mail address. The e-mail address needs to be a valid address and can be an
alias setup for distribution to a larger audience.
• Filters are provided for each recipient to allow only certain categories of traps and
events be sent by e-mail.
• Each recipient can have its own SMTP server and TCP port number, if this is not
defined on a certain recipient, the default SMTP server and TCP port number is
used.

17.1.2 Commands
The smtp command configures the SNMP alerts to be sent via e-mail.
smtp
smtp <enable|disable>
The show smtp command displays the current SMTP global settings and recipients
displays the currently configured recipients of e-mail alerts.
show smtp <config|recipients>
The add command adds a specific id, where id represents the recipient identification and
ranges from 1 to 5. The software allows a maximum of 5 recipients
add id=<1-5> email=<email-addr> [traps=<all|none|S|R|E>]
[events=<all|none|I|A|C|F|D>] [ip=<ip-addr>] [port=<1-65535>] [domain=<domain>]
The add command has the following additional parameters:
• The email parameter is the e-mail address of the recipient.
• The optional traps parameter represents the trap filter. If value is all, all traps of
any type will be sent to this recipient. If value is none, no traps are sent to this
recipient. Value can also be a combination of 'S' (SNMP), 'R' (RMON) and 'E'
(enterprise). For example, trap=SR means that SNMP and RMON traps will be sent
via e-mail to the recipient. If this option is not defined, the recipient will have a
default value of “all”.
• The optional events parameter is the event filter. Value can be “all” - all event
severity types will be sent to recipient, “none” - no event will be sent to recipient or
a combination of 'I' (informational), 'A' (activity), 'C' (critical), 'F' (fatal) and 'D' (debug).
With “event=ACF” implies that events of severity types activity, critical and fatal will
be sent to recipients by e-mail. If this option is not defined, a value of “all” is taken.
• The optional ip parameter represents the SMTP server IP address. This is the SMTP
server to connect to for this particular user. If this option is not defined, the global/
default SMTP server is used.
• The optional port parameter specifies the TCP port of the SMTP server. If this is not
defined, the global default TCP port is used.
The optional domain parameter specifies the domain name of the SMTP server. If this
is not defined, the global default domain name is used.
The delete command deletes the specific id specified. The deleted id no longer receives
the traps via e-mail. The id is added using the add command
delete id=<1-5>

17–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

The sendmail command customizes (and also sends a test e-mail to check SMTP settings)
the e-mail delivered by specifying the e-mail subject field, server address, to field and the
body of the text. See the example in this section for details.
sendmail server=<ip-addr> to=<email-addr> from=<email-addr> subject=<string>
body=<string>
The server command configures the global SMTP server settings.
server ip=<ip-addr> [port=<1-65535>] [retry=<0-3>] [domain=<domain>]
For this command, ip represents the SMTP server IP address, port the TCP port to be used
for SMTP communications (default is 25), and retry specifies how many times to retry if an
error occurs when sending e-mail (from 0 to 3 with default of 0).
The optional domain parameter specifies the domain name of the SMTP server.

17.1.3 Example
The following example shows how to set SMTP to receive SNMP trap information via e-mail.

E-mail alerts can be forwarded to be received by other devices such as cellphones and
Note

pages. Most interfaces to SMTP are already provided by the service provider.
NOTE

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–3

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

Example 17-1: Configuring SMTP to receive SNMP trap information via e-mail

ML800#smtp
ML800(smtp)##server ip=3.94.210.25 port=25 retry=3 domain=ge.com
Successfully set global SMTP server configuration
ML800(smtp)##show smtp config
SMTP Global Configuration
========================================
Status : Disabled
SMTP Server Host : 3.94.210.25
SMTP Server Domain : ge.com
SMTP Server Port : 25
Retry Count : 3
ML800(smtp)##add id=1 email=jsmith@ge.com traps=s events=CF
Recipient successfully added
ML800(smtp)##add id=2 email=xyz@abc.com traps=all events=all ip=3.30.154.28 port=25
domain=abc.com
Recipient successfully added
ML800(smtp)##show smtp recipients
ID E-mail Address SMTP Server From Domain Port Traps Events
===================================================================
1 jsmith@ge.com 3.94.210.25 ge.com 25 S FC
2 xyz@abc.com 3.30.154.28 abc.com 25 All All
3 -- -- -- -- -- --
4 -- -- -- -- -- --
5 -- -- -- -- -- --
ML800(smtp)##delete id=2
Recipient successfully deleted
ML800(smtp)##show smtp recipients
ML800(smtp)##show smtp recipients
ID E-mail Address SMTP Server From Domain Port Traps Events
===================================================================
1 jsmith@ge.com 3.94.210.25 ge.com 25 S FC
2 -- -- -- -- -- --
3 -- -- -- -- -- --

17–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

17.2 Statistics

17.2.1 Viewing Port Statistics with EnerVista Secure Web Management software
The EnerVista Secure Web Management software allows for the display of several
statistics in a graphical format. These are described below.
To view statistics,
 Select the Configuration > Statistics menu item.
To view port-specific statistics,
 Select the Configuration > Statistics > Port Statistics menu item.

Each port can be viewed by clicking on the back or forward buttons. Each group
represents different statistics.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–5

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

The following figure displays the port statistics for group 2.

The following figure displays the port statistics for group 3.

17–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

17.3 Serial Connectivity

17.3.1 Description
When using the serial connectivity with applications such as HyperTerminal, it may be
necessary to optimize the character delays so that the FIFO buffer used in the MultiLink
ML800 Managed Edge Switch is not overrun. The important parameters to set for any
serial connectivity software is to set the line delay to be 500 ms and the character delay to
be 50 ms. For example, using HyperTerminal this can be set under File > Properties. When
the Properties window is open, click on the ASCII Setup button and in the Line Delay entry
box enter in 500 and in the Character Delay entry box enter in 50 as shown below.

754729A1.CDR

FIGURE 17–1: Optimizing serial connection in HyperTerminal

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–7

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

17.4 History

17.4.1 Commands
The commands below may be useful in repeating commands and obtaining history
information.
The !! command repeats the last command.
!!
The !1, !2,..., !n commands repeat the nth command (as indicated by a show history).
!<n>
The show history command displays the last 25 executed commands. If less than 25
commands were executed, only those commands executed are shown.
show history
The history is cleared if the user logs out or if the switch times out. The history count
restarts when the user logs in.
The show version command displays the current software version.
show version

17–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

17.5 Ping

17.5.1 Ping through the Command Line Interface

The ping command can be used to test connectivity to other devices as well as checking
to see if the IP address is setup correctly. The command syntax is:
ping <ipaddress> [count=<1-999>]
[timeout=<1-256>]
For example:
ML800# ping 3.94.248.61
3.94.248.61 is alive, count 1, time = 40ms
ML800# ping 3.94.248.61 count=3
3.94.248.61 is alive, count 1, time = 20ms
3.94.248.61 is alive, count 2, time = 20ms
3.94.248.61 is alive, count 3, time = 40ms
ML800#
Many devices do not respond to ping or block ping commands. Make sure that the target
device responds or the network allows the ping packets to propagate.

17.5.2 Ping through EnerVista Secure Web Management software

The ping command can be used from EnerVista Secure Web Management software to
test connectivity to other devices as well as checking to see if the IP address is correct.
Select the Administration > Ping menu item to use ping.

As mentioned earlier, many devices do not respond to ping commands. Make sure that
the target device responds or the network allows ping packets to propagate.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–9

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

17.6 Prompt

17.6.1 Changing the Command Line Prompt

Setting a meaningful host prompt can be useful when a network administrator is
managing multiple switches and has multiple telnet or console sessions. To facilitate this,
the ML800 allows administrators to define custom prompts. The command to set a prompt
is:
set prompt <prompt string>
The length of the prompt is limited to 60 characters.
There are predefined variables that can be used to set the prompt. These are:
• $n: system name
• $c: system contact
• $l: system location
• $i: system IP address
• $m: system MAC address
• $v: version
• $$: the “$” (dollar sign) character
• $r: new line
• $b: space
A few examples on how the system prompt can be setup are shown below.
ML800# snmp
ML800(snmp)## setvar sysname=Core
System variable(s) set successfully
ML800(snmp)## exit
ML800# set prompt $n
Core# set prompt $n$b$i
Core 192.168.5.5# set prompt $n$b$i$b
Core 192.168.5.5 # snmp
Core 192.168.5.5 (snmp)## setvar sysname=ML800
System variable(s) set successfully
Core 192.168.5.5 (snmp)## exit
Core 192.168.5.5 # set prompt $b$b$i$b
192.168.5.5 # set prompt $n$b$i$b
ML800 192.168.5.5 #
ML800 192.168.5.5 # set prompt Some$bthing$i
Some thing192.168.5.5# set prompt Some$bthing$b$i
Some thing 192.168.5.5#

17–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

17.7 System Events

17.7.1 Description
The event log records operating events as single-line entries listed in chronological order,
and are a useful tool for isolating problems. Each event log entry is composed of four fields
as shown below:
• Severity field: Indicates one of the following
• I (Information) indicates routine events; A (Activity) indicates activity on the switch;
D (Debug) is reserved for GE Digital Energy; C (Critical) indicates that a severe
switch error has occurred; and F (Fatal). indicates that a service has behaved
unexpectedly.
• Date field: the date in mm/dd/yy format (as per configured) that the entry was
placed in the log.
• Time field: is the time in hh:mm:ss format (as per configured) that the entry was
placed in the log.
• Description field: is a brief description of the event.
The event log holds up to 1000 lines in chronological order, from the oldest to the newest.
Each line consists of one complete event message. Once the log has received 1000 entries,
it discards the current oldest line (with information level severity only) each time a new line
is received. The event log window contains 22 log entry lines and can be positioned to any
location in the log.

17.7.2 Command Line Interface Example

The following example illustrates a typical event log.

Example 17-2: Typical system event log

ML800# show log

S DATE TIME Log Description
-- ---------- ------------ ---------------------------------------------------
I 03-02-2005 5:14:43 P.M SYSMGR:System Subnet Mask changed
I 01-01-2001 12:00:00 A.M SYSMGR:successfully registered with DB Manager
I 01-01-2001 12:00:00 A.M SYSMGR:successfully read from DB
A 01-01-2001 12:00:00 A.M VLAN:Vlan type set to Port VLAN
I 01-01-2001 12:00:00 A.M SYSMGR:system was reset by user using CLI command
I 01-01-2001 12:00:00 A.M SNTP:Date/Time set to 01-01-2001 12:00AM
I 01-01-2001 12:00:00 A.M SNTP:Client started
I 03-03-2005 4:32:48 A.M SNTP:Date and Time updated from SNTP server
I 03-03-2005 9:31:59 A.M TELNET:Telnet Session Started
I 03-03-2005 9:32:04 A.M CLI:manager console login|
A 03-03-2005 9:32:11 A.M IGMP:IGMP Snooping is enabled
A 03-03-2005 9:35:40 A.M IGMP:IGMP Snooping is disabled
A 03-03-2005 9:41:46 A.M IGMP:IGMP Snooping is enabled

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–11

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

Event logs can be exported to a ftp or a tftp server on the network for further analysis. The
CLI command is used to facilitate the export of the event log
exportlog mode=<serial|tftp|ftp> <ipaddress> file=<name> doctype=<raw|html>
Where mode is the mode of transfer, ipaddress is the IP address of the ftp or TFTP server,
file is the filename, and doctype indicates the log is saved as a text file (raw) or as an
HTML file.
Please ensure the proper extension is used for the file argument (for example, “html” for
an HTML file).
ML800# exportlog mode=tftp 192.168.5.2 file=eventlog
doctype=html
Do you wish to export the event logs? [ 'Y' or 'N'] Y
Successfully uploaded the event log file.
ML800# exportlog mode=tftp 192.168.5.2 file=eventlog.txt
doctype=raw
Do you wish to export the event logs? [ 'Y' or 'N'] Y
Successfully uploaded the event log file.

17.7.3 EnerVista Example

The EnerVista Secure Web Management software provides and overview of the type of
Logs by reviewing the statistics. Each specific log can be viewed by viewing the logs menu.
To view the log statistics,
 Select the Configuration > Statistics > Log Statistics menu item.

The Log Statistics window displays the logged events received – most logs are typically
informational and activity.
The log buffer size can be controlled through this menu.

17–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

For viewing each specific log,

 Select the Configuration > Logs menu item.

Each specific type of log can be viewed by using the drop down menu as shown below. In
this example only informational logs are displayed.

The Clear button clears all the logs. To prevent accidental erasures, you will be prompted
again if the logs should be deleted.
The Event Log records operating events as single-line entries listed in chronological order.
For details on event log records, refer to Description on page 17–11.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–13

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

17.8 Command Reference

17.8.1 Main Commands

The main commands can be categorized as show commands, set commands, and
context-less commands. The show commands are listed below.
• show active-snmp: displays currently active SNMP support
• show active-stp: displays currently active STP
• show active-vlan: displays currently active VLAN
• show address-table: displays address table parameters
• show age: displays the address table age limit
• show arp: displays the arp details
• show bootmode: displays the current bootmode value
• show broadcast-protect: displays broadcast storm protection parameters
• show config: displays the saved configuration as a whole or by module
• show console: displays console serial link settings
• show date: displays system date
• show daylight: displays the configured daylight savings settings
• show gateway: displays the gateway of the system
• show gvrp: displays the GVRP parameters
• show host: displays the host table for FTP users
• show igmp: displays the IGMP parameters
• show interfaces: display the interface information
• show ip: displays the system IP address
• show ip-access: displays the IP address access list
• show ipconfig: displays the IP configuration
• show lacp
• show lll: displays the Link-Loss-Learn parameters
• show log: displays log information
• show logsize: displays the current event log size
• show mac: displays the system MAC address
• show modbus: displays Modbus settings
• show modules: displays the module information
• show port: displays the port information
• show port-mirror: displays the port mirroring parameters
• show port-security: displays the port security configuration parameters
• show power : displays condition of power supplies, in redundant power supply
switches only
• show qos: displays the QOS settings
• show rmon: displays the rmon configuration parameters
• show setup: displays the setup parameters of the system

17–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

• show smtp: displays e-mail (SMTP) alert information

• show snmp: displays information related to SNMP
• show sntp: displays the configured SNTP servers details
• show stats: displays the port statistics
• show stp: displays Spanning Tree Bridge parameters
• show subnet: displays the Subnet Mask of the system
• show ssl
• show sysconfig: displays system configurable parameters
• show syscontact: displays the current system contact
• show syslocation: displays the current system location
• show sysname: displays the current system name
• show time: displays the system time
• show timeout: displays the system inactivity time out
• show timezone: displays the configured time zone of the device
• show uptime: displays up time of the system
• show users: displays all configured users
• show version: displays current version of the software
• show vlan: displays the VLAN parameters of a specified type
• show web
The set commands are listed below.
• set bootmode
• set date year
• set daylight country
• set prompt
• set logsize
• set password: sets the current user password
• set snmp
• set stp
• set time
• set timeformat
• set timeout: sets the system inactivity time out
• set timezone
• set vlan: sets the VLAN type
The context-less commands are listed below.
• clear : clears the event log, command history, or screen
• climode: to set the interactive CLI mode
• enable: allows to login as another user
• help
• host: to generate the host table for FTP users
• more: to set more pipe in screen outputs

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–15

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

• save
• whoami: display the user information
• reboot
• authorize
• degrade
• exportlog mode
• ftp
• help
• ipconfig
• kill
• kill session id
• logout: logs out from the current user
• ping: to send the ping requests
• tftp
• telnet: connects to the remote system through telnet
• terminal: to set the terminal size
• xmodem

17.8.2 Configuration commands

The access commands are shown below.
• allow: allows the IP address
• deny: denies the IP address
• dhcp: enables or disables the DHCP
• modbus: enables or disables access to Modbus map
• remove
• removeall
• snmp: enables or disables SNMP
• ssl
• telnet
• web
The alarm commands are shown below.
• add
• alarm
• del
• period
The authorization commands are shown below.
• auth
• authserver
• backend
• clear-stats

17–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

• portaccess
• reauth
• setport
• show-port
• show-stats
• trigger-reauth
The device commands are shown below.
• device
• backpressure
• broadcast-protect: enables or disables broadcast storm protection globally
• flowcontrol
• rate-threshold: sets the broadcast rate threshold (frames/sec)
• setage: sets the mgtagetime
• setport: sets the port configuration
The VLAN registration over GARP (GVRP) commands are shown below. Refer to VLAN
Registration over GARP on page 11–1 for details.
• gvrp
• help gvrp: configures GVRP parameters for dynamic VLAN
• set-forbid: sets forbidden ports for a tag-based VLAN
• show-ports: show ports current GVRP state
• show-forbid: show forbidden ports for tag-based VLAN
• set-ports: set GVRP port state usage
• show-vlan: shows dynamic/static tag-based VLANs
• static: convert dynamic VLAN to static VLAN
The IGMP commands are shown below. Refer to IGMP on page 15–1 for additional details.
• mcast
• set-leave: enables or disables IGMP immediate leave status
• set-port: sets the port mode
• set-qi: sets the query interval (60 to 127) for router ports
• set-qri
• set-querier : enables or disables switch as querier
• show-group: displays IGMP group list
• show-port: displays IGMP port mode
• show-router : displays IGMP router list
The Link Aggregation Control Protocol (LACP) commands are shown below.
• lacp
• add port
• del port
• edit port
The port mirroring commands are shown below. Refer to Port Mirroring and Setup on page
9–1 for additional details.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–17

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

• help port-mirror
• prtmr : enables/disables port mirroring functionality
• setport: defines the port mirroring ports
The port security commands are shown below. Refer to Securing Access on page 6–1 for
additional details.
• action: sets the action type of secured port
• allow: allows MAC addressing per port
• help port-security
• learn: enables/disables security for a single port or group of ports
• ps: enables/disables security in system
• remove: removes MAC addressing per port
• signal: sets the signal type of the secured port
The quality of service (QoS) commands are shown below. Refer to QoS Overview on page
14–1 for additional details.
• help qos
• setqos: configures QOS configuration usage
• set-untag
• set-weight: sets the port priority weights for all the ports in all the device
• show-portweight: displays the current port weight priority
The remote monitoring (RMON) commands are shown below. Refer to Configuring RMON
on page 16–15 for additional details.
• alarm: sets the owner for the alarm group
• event: sets the owner for the event group
• help rmon
• history: sets the owner for the history group
• statistics: sets the owner for the statistics group
The Rapid Spanning Tree Protocol (RSTP) commands are shown below. Refer to Rapid
Spanning Tree Protocol on page 13–1 for additional details.
• cost: sets the path cost of ports
• forceversion: set the force version of STP
• help rstp
• lll
• port: sets the RSTP administration status of ports
• priority: changes the priority of ports or bridge
• rstp: changes the RSTP administrative status of the bridge
• show-forceversion: shows the current force version of RSTP
• show-mode: shows the port mode status
• show-timers: shows the bridge time parameters
• timers: changes the bridge time parameters
The Simple Mail Transfer Protocol (SMTP) commands for e-mail are shown below. Refer to
E-mail on page 17–1 for additional details.
• add: adds a recipient

17–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS

• delete: deletes a recipient

• help smtp
• sendmail: sends e-mail
• server: sets the global SMTP server configuration
• smtp: enables/disables SMTP e-mail alert
The Simple Network Management Protocol (SNMP) commands are shown below. Refer to
SNMP on page 16–1 for additional details.
• authentraps: enable/disables the authentication traps
• community: configures SNMP community names
• help snmp
• mgrip: adds or deletes the SNMP manager IP
• setvar: configures system name, contact, or location
• traps: adds or deletes a trap receiver
The Simple Network Time Protocol (SNTP) commands are shown below. Refer to Network
Time on page 5–10 for additional details.
• delete: deletes the SNTP server from SNTP server database
• help sntp
• setsntp: adds SNTP server into the SNTP server database
• sntp: configures parameters for SNTP system
• sync: sets the interval for synchronization time with an NTP server
The Spanning Tree Protocol (STP) commands are shown below. Refer to Spanning Tree
Protocol (STP) on page 12–1 for additional details.
• cost
• lll
• port
• priority
• s-ring
• stp
• timers
The user commands are shown below.
• add: adds a new user
• chlevel: changes the user access permissions
• delete: deletes an existing user
• help user
• passwd: change the user password
• tacplus
• tacserver
• useraccess
The VLAN commands are shown below. Refer to VLAN on page 10–1 for additional details.
• add
• delete

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 17–19

MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS

• edit
• save
• set-egress
• set-ingress
• set-port
• show-egress
• show-ingress
• show-port
• start
• stop
• vlan

17–20 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Ethernet Communications Switch

Chapter 18: Modbus Protocol

Modbus Protocol

18.1 Modbus Configuration

18.1.1 Overview
Modicon programmable controllers as well as other PLCs can communicate with each
other and other devices over a variety of networks. The common language used by all
Modicon controllers is the Modbus protocol. This protocol defines a message structure that
controllers recognize and use regardless of the networks over which they communicate. It
describes the process a controller uses to request access to another device, how it will
respond to requests from the other devices, and how errors will be detected and reported.
It establishes a common format for the layout and contents of message fields. The Modbus
protocol thus operates at the layer 7 of the OSI 7 layer stack. Additional information on
Modbus can be found at http://www.modbus.org and other related sites.
RFC 1122 Requirements for Internet Hosts - Communication Layers defines how Modbus
packets can be carried over a TCP/IP transport and how Modicon controllers or other PLC
devices can communicate over a TCP/IP network. To facilitate this communications, the
MultiLink ML800 Managed Edge Switch allows Modbus connectivity.
As per this RFC, Modbus communications take place on TCP port 502. Please make sure the
network security devices do not block port 502. If port 502 is blocked, which is the normal
case with many firewall and other security devices, the communications between two
Modbus devices over a TCP/IP network will not succeed.

18.1.2 Command Line Interface Settings

The following command-line interface settings are available:
modbus <enable|disable>
modbus port=<port|default>
modbus device=<device|default>
show modbus
The commands enable the Modbus protocol and set the relevant Modbus slave address
and communication port values.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–1

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

For example,
ML800# show ipconfig
IP Address: 192.168.1.5
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.10
ML800# show modbus
Access to Modbus disabaled
Modbus is Using Port: 502
Modbus is Using Device: 5
ML800# access
ML800(access)## modbus enable
Enabling Access to Modbus
ML800(access)## show modbus
Access to Modbus enabled
Modbus is Using Port: 502
Modbus is Using Device: 5
ML800(access)## modbus port=602
Modbus Port is set
ML800(access)## show modbus
Access to Modbus enabled
Modbus is Using Port: 602
Modbus is Using Device: 5
ML800(access)## modbus port=default
Modbus Port Set to Default
ML800(access)## show modbus
Access to Modbus enabled
Modbus is Using Port :502
Modbus is Using Device :5

18–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

18.1.3 EnerVista Settings

To modify the Modbus settings through EnerVista Secure Web Management software,
 Select the Configuration > Access > Modbus menu item.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–3

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

18.2 Memory Mapping

18.2.1 Modbus Memory Map

The Modbus memory map is shown below. Refer to Format Codes on page 18–37 for
details on the items in the format column.
Table 18–1: Modbus memory map (Sheet 1 of 33)
Address Description Range Step Format Default
0000 System name (12 registers) - - String Varies
000C System contact (12 registers) - - String multilin.tech
@ge.com
0018 System location (12 registers) - - String Markham, Ontario
0024 Software version (6 registers) - - String Varies
002A IP address (byte 0) 1 to 254 1 F1 0
002B IP address (byte 1) 1 to 254 1 F1 0
002C IP address (byte 2) 1 to 254 1 F1 0
002D IP address (byte 3) 1 to 254 1 F1 0
002E Netmask (byte 0) 1 to 254 1 F1 0
002F Netmask (byte 1) 1 to 254 1 F1 0
0030 Netmask (byte 2) 1 to 254 1 F1 0
0031 Netmask (byte 3) 1 to 254 1 F1 0
0032 Gateway (byte 0) 1 to 254 1 F1 0
0033 Gateway (byte 1) 1 to 254 1 F1 0
0034 Gateway (byte 2) 1 to 254 1 F1 0
0035 Gateway (byte 3) 1 to 254 1 F1 0
0036 MAC address (3 registers) - - String Varies
0039 Order code (16 registers) - - String Varies
0049 Power alarm 1 0 to 1 1 F2 0
004A Power alarm 2 0 to 1 1 F2 0
004B Stp State 0 to 1 1 F3 0
004C Number of ports 1 to 32 1 F1 Varies
004E Port present map - - Bitmap Varies
0050 Port link map - - Bitmap 0
0052 Port stp state map - - Bitmap 0
0054 Port activity map - - Bitmap 0
0056 Port 1 type 0 to 6 1 F4 Varies
0057 Port 2 type 0 to 6 1 F4 Varies
0058 Port 3 type 0 to 6 1 F4 Varies
0059 Port 4 type 0 to 6 1 F4 Varies
005A Port 5 type 0 to 6 1 F4 Varies
005B Port 6 type 0 to 6 1 F4 Varies
005C Port 7 type 0 to 6 1 F4 Varies
005D Port 8 type 0 to 6 1 F4 Varies
005E Port 9 type 0 to 6 1 F4 Varies
005F Port 10 type 0 to 6 1 F4 Varies
0060 Port 11 type 0 to 6 1 F4 Varies
0061 Port 12 type 0 to 6 1 F4 Varies

18–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 2 of 33)

Address Description Range Step Format Default
0062 Port 13 type 0 to 6 1 F4 Varies
0063 Port 14 type 0 to 6 1 F4 Varies
0064 Port 15 type 0 to 6 1 F4 Varies
0065 Port 16 type 0 to 6 1 F4 Varies
0066 Port 17 type 0 to 6 1 F4 Varies
0067 Port 18 type 0 to 6 1 F4 Varies
0068 Port 19 type 0 to 6 1 F4 Varies
0069 Port 20 type 0 to 6 1 F4 Varies
006A Port 21 type 0 to 6 1 F4 Varies
006B Port 22 type 0 to 6 1 F4 Varies
006C Port 23 type 0 to 6 1 F4 Varies
006D Port 24 type 0 to 6 1 F4 Varies
006E Port 25 type 0 to 6 1 F4 Varies
006F Port 26 type 0 to 6 1 F4 Varies
0070 Port 27 type 0 to 6 1 F4 Varies
0071 Port 28 type 0 to 6 1 F4 Varies
0072 Port 29 type 0 to 6 1 F4 Varies
0073 Port 30 type 0 to 6 1 F4 Varies
0074 Port 31 type 0 to 6 1 F4 Varies
0075 Port 32 type 0 to 6 1 F4 Varies
0076 Port 1 link status 0 to 1 1 F3 0
0077 Port 2 link status 0 to 1 1 F3 0
0078 Port 3 link status 0 to 1 1 F3 0
0079 Port 4 link status 0 to 1 1 F3 0
007A Port 5 link status 0 to 1 1 F3 0
007B Port 6 link status 0 to 1 1 F3 0
007C Port 7 link status 0 to 1 1 F3 0
007D Port 8 link status 0 to 1 1 F3 0
007E Port 9 link status 0 to 1 1 F3 0
007F Port 10 link status 0 to 1 1 F3 0
0080 Port 11 link status 0 to 1 1 F3 0
0081 Port 12 link status 0 to 1 1 F3 0
0082 Port 13 link status 0 to 1 1 F3 0
0083 Port 14 link status 0 to 1 1 F3 0
0084 Port 15 link status 0 to 1 1 F3 0
0085 Port 16 link status 0 to 1 1 F3 0
0086 Port 17 link status 0 to 1 1 F3 0
0087 Port 18 link status 0 to 1 1 F3 0
0088 Port 19 link status 0 to 1 1 F3 0
0089 Port 20 link status 0 to 1 1 F3 0
008A Port 21 link status 0 to 1 1 F3 0
008B Port 22 link status 0 to 1 1 F3 0
008C Port 23 link status 0 to 1 1 F3 0
008D Port 24 link status 0 to 1 1 F3 0
008E Port 25 link status 0 to 1 1 F3 0
008F Port 26 link status 0 to 1 1 F3 0

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–5

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 3 of 33)

Address Description Range Step Format Default
0090 Port 27 link status 0 to 1 1 F3 0
0091 Port 28 link status 0 to 1 1 F3 0
0092 Port 29 link status 0 to 1 1 F3 0
0093 Port 30 link status 0 to 1 1 F3 0
0094 Port 31 link status 0 to 1 1 F3 0
0095 Port 32 link status 0 to 1 1 F3 0
0096 Port 1 STP state 0 to 1 1 F3 0
0097 Port 2 STP state 0 to 1 1 F3 0
0098 Port 3 STP state 0 to 1 1 F3 0
0099 Port 4 STP state 0 to 1 1 F3 0
009A Port 5 STP state 0 to 1 1 F3 0
009B Port 6 STP state 0 to 1 1 F3 0
009C Port 7 STP state 0 to 1 1 F3 0
009D Port 8 STP state 0 to 1 1 F3 0
009E Port 9 STP state 0 to 1 1 F3 0
009F Port 10 STP state 0 to 1 1 F3 0
00A0 Port 11 STP state 0 to 1 1 F3 0
00A1 Port 12 STP state 0 to 1 1 F3 0
00A2 Port 13 STP state 0 to 1 1 F3 0
00A3 Port 14 STP state 0 to 1 1 F3 0
00A4 Port 15 STP state 0 to 1 1 F3 0
00A5 Port 16 STP state 0 to 1 1 F3 0
00A6 Port 17 STP state 0 to 1 1 F3 0
00A7 Port 18 STP state 0 to 1 1 F3 0
00A8 Port 19 STP state 0 to 1 1 F3 0
00A9 Port 20 STP state 0 to 1 1 F3 0
00AA Port 21 STP state 0 to 1 1 F3 0
00AB Port 22 STP state 0 to 1 1 F3 0
00AC Port 23 STP state 0 to 1 1 F3 0
00AD Port 24 STP state 0 to 1 1 F3 0
00AE Port 25 STP state 0 to 1 1 F3 0
00AF Port 26 STP state 0 to 1 1 F3 0
00B0 Port 27 STP state 0 to 1 1 F3 0
00B1 Port 28 STP state 0 to 1 1 F3 0
00B2 Port 29 STP state 0 to 1 1 F3 0
00B3 Port 30 STP state 0 to 1 1 F3 0
00B4 Port 31 STP state 0 to 1 1 F3 0
00B5 Port 32 STP state 0 to 1 1 F3 0
00B6 Port 1 activity 0 to 1 1 F3 0
00B7 Port 2 activity 0 to 1 1 F3 0
00B8 Port 3 activity 0 to 1 1 F3 0
00B9 Port 4 activity 0 to 1 1 F3 0
00BA Port 5 activity 0 to 1 1 F3 0
00BB Port 6 activity 0 to 1 1 F3 0
00BC Port 7 activity 0 to 1 1 F3 0
00BD Port 8 activity 0 to 1 1 F3 0

18–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 4 of 33)

Address Description Range Step Format Default
00BE Port 9 activity 0 to 1 1 F3 0
00BF Port 10 activity 0 to 1 1 F3 0
00C0 Port 11 activity 0 to 1 1 F3 0
00C1 Port 12 activity 0 to 1 1 F3 0
00C2 Port 13 activity 0 to 1 1 F3 0
00C3 Port 14 activity 0 to 1 1 F3 0
00C4 Port 15 activity 0 to 1 1 F3 0
00C5 Port 16 activity 0 to 1 1 F3 0
00C6 Port 17 activity 0 to 1 1 F3 0
00C7 Port 18 activity 0 to 1 1 F3 0
00C8 Port 19 activity 0 to 1 1 F3 0
00C9 Port 20 activity 0 to 1 1 F3 0
00CA Port 21 activity 0 to 1 1 F3 0
00CB Port 22 activity 0 to 1 1 F3 0
00CC Port 23 activity 0 to 1 1 F3 0
00CD Port 24 activity 0 to 1 1 F3 0
00CE Port 25 activity 0 to 1 1 F3 0
00CF Port 26 activity 0 to 1 1 F3 0
00D0 Port 27 activity 0 to 1 1 F3 0
00D1 Port 28 activity 0 to 1 1 F3 0
00D2 Port 29 activity 0 to 1 1 F3 0
00D3 Port 30 activity 0 to 1 1 F3 0
00D4 Port 31 activity 0 to 1 1 F3 0
00D5 Port 32 activity 0 to 1 1 F3 0
00D6 Port 1: Number of bytes received 0 to 1 F9 0
4294967295
00D8 Port 1: Number of bytes sent 0 to 1 F9 0
4294967295
00DA Port 1: Number of frames received 0 to 1 F9 0
4294967295
00DC Port 1: Number of frames sent 0 to 1 F9 0
4294967295
00DE Port 1: Total bytes received 0 to 1 F9 0
4294967295
00E0 Port 1: Total frames received 0 to 1 F9 0
4294967295
00E2 Port 1: Number of broadcast frames 0 to 1 F9 0
received 4294967295
00E4 Port 1: Number of multicast frames 0 to 1 F9 0
received 4294967295
00E6 Port 1: Number of frames with CRC 0 to 1 F9 0
error 4294967295
00E8 Port 1: Number of oversized frames 0 to 1 F9 0
received 4294967295
00EA Port 1: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
00EC Port 1: Number of jabber frames 0 to 1 F9 0
received 4294967295
00EE Port 1: Number of collisions occurred 0 to 1 F9 0
4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–7

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 5 of 33)

Address Description Range Step Format Default
00F0 Port 1: Number of late collisions 0 to 1 F9 0
occurred 4294967295
00F2 Port 1: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
00F4 Port 1: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
00F6 Port 1: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
00F8 Port 1: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
00FA Port 1: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
00FC Port 1: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
00FE Port 1: Number of MAC error packets 0 to 1 F9 0
4294967295
0100 Port 1: Number of dropped received 0 to 1 F9 0
packets 4294967295
0102 Port 1: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0104 Port 1: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0106 Port 1: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0108 Port 2: Number of bytes received 0 to 1 F9 0
4294967295
010A Port 2: Number of bytes sent 0 to 1 F9 0
4294967295
010C Port 2: Number of frames received 0 to 1 F9 0
4294967295
010E Port 2: Number of frames sent 0 to 1 F9 0
4294967295
0110 Port 2: Total bytes received 0 to 1 F9 0
4294967295
0112 Port 2: Total frames received 0 to 1 F9 0
4294967295
0114 Port 2: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0116 Port 2: Number of multicast frames 0 to 1 F9 0
received 4294967295
0118 Port 2: Number of frames with CRC 0 to 1 F9 0
error 4294967295
011A Port 2: Number of oversized frames 0 to 1 F9 0
received 4294967295
011C Port 2: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
011E Port 2: Number of jabber frames 0 to 1 F9 0
received 4294967295
0120 Port 2: Number of collisions occurred 0 to 1 F9 0
4294967295
0122 Port 2: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0124 Port 2: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0126 Port 2: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295

18–8 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 6 of 33)

Address Description Range Step Format Default
0128 Port 2: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
012A Port 2: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
012C Port 2: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
012E Port 2: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0130 Port 2: Number of MAC error packets 0 to 1 F9 0
4294967295
0132 Port 2: Number of dropped received 0 to 1 F9 0
packets 4294967295
0134 Port 2: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0136 Port 2: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0138 Port 2: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
013A Port 3: Number of bytes received 0 to 1 F9 0
4294967295
013C Port 3: Number of bytes sent 0 to 1 F9 0
4294967295
013E Port 3: Number of frames received 0 to 1 F9 0
4294967295
0140 Port 3: Number of frames sent 0 to 1 F9 0
4294967295
0142 Port 3: Total bytes received 0 to 1 F9 0
4294967295
0144 Port 3: Total frames received 0 to 1 F9 0
4294967295
0146 Port 3: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0148 Port 3: Number of multicast frames 0 to 1 F9 0
received 4294967295
014A Port 3: Number of frames with CRC 0 to 1 F9 0
error 4294967295
014C Port 3: Number of oversized frames 0 to 1 F9 0
received 4294967295
014E Port 3: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0150 Port 3: Number of jabber frames 0 to 1 F9 0
received 4294967295
0152 Port 3: Number of collisions occurred 0 to 1 F9 0
4294967295
0154 Port 3: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0156 Port 3: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0158 Port 3: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
015A Port 3: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
015C Port 3: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
015E Port 3: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–9

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 7 of 33)

Address Description Range Step Format Default
0160 Port 3: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0162 Port 3: Number of MAC error packets 0 to 1 F9 0
4294967295
0164 Port 3: Number of dropped received 0 to 1 F9 0
packets 4294967295
0166 Port 3: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0168 Port 3: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
016A Port 3: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
016C Port 4: Number of bytes received 0 to 1 F9 0
4294967295
016E Port 4: Number of bytes sent 0 to 1 F9 0
4294967295
0170 Port 4: Number of frames received 0 to 1 F9 0
4294967295
0172 Port 4: Number of frames sent 0 to 1 F9 0
4294967295
0174 Port 4: Total bytes received 0 to 1 F9 0
4294967295
0176 Port 4: Total frames received 0 to 1 F9 0
4294967295
0178 Port 4: Number of broadcast frames 0 to 1 F9 0
received 4294967295
017A Port 4: Number of multicast frames 0 to 1 F9 0
received 4294967295
017C Port 4: Number of frames with CRC 0 to 1 F9 0
error 4294967295
017E Port 4: Number of oversized frames 0 to 1 F9 0
received 4294967295
0180 Port 4: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0182 Port 4: Number of jabber frames 0 to 1 F9 0
received 4294967295
0184 Port 4: Number of collisions occurred 0 to 1 F9 0
4294967295
0186 Port 4: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0188 Port 4: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
018A Port 4: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
018C Port 4: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
018E Port 4: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0190 Port 4: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0192 Port 4: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0194 Port 4: Number of MAC error packets 0 to 1 F9 0
4294967295
0196 Port 4: Number of dropped received 0 to 1 F9 0
packets 4294967295

18–10 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 8 of 33)

Address Description Range Step Format Default
0198 Port 4: Number of multicast frames 0 to 1 F9 0
sent 4294967295
019A Port 4: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
019C Port 4: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
019E Port 5: Number of bytes received 0 to 1 F9 0
4294967295
01A0 Port 5: Number of bytes sent 0 to 1 F9 0
4294967295
01A2 Port 5: Number of frames received 0 to 1 F9 0
4294967295
01A4 Port 5: Number of frames sent 0 to 1 F9 0
4294967295
01A6 Port 5: Total bytes received 0 to 1 F9 0
4294967295
01A8 Port 5: Total frames received 0 to 1 F9 0
4294967295
01AA Port 5: Number of broadcast frames 0 to 1 F9 0
received 4294967295
01AC Port 5: Number of multicast frames 0 to 1 F9 0
received 4294967295
01AE Port 5: Number of frames with CRC 0 to 1 F9 0
error 4294967295
01B0 Port 5: Number of oversized frames 0 to 1 F9 0
received 4294967295
01B2 Port 5: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
01B4 Port 5: Number of jabber frames 0 to 1 F9 0
received 4294967295
01B6 Port 5: Number of collisions occurred 0 to 1 F9 0
4294967295
01B8 Port 5: Number of late collisions 0 to 1 F9 0
occurred 4294967295
01BA Port 5: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
01BC Port 5: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
01BE Port 5: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
01C0 Port 5: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
01C2 Port 5: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
01C4 Port 5: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
01C6 Port 5: Number of MAC error packets 0 to 1 F9 0
4294967295
01C8 Port 5: Number of dropped received 0 to 1 F9 0
packets 4294967295
01CA Port 5: Number of multicast frames 0 to 1 F9 0
sent 4294967295
01CC Port 5: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
01CE Port 5: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–11

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 9 of 33)

Address Description Range Step Format Default
01D0 Port 6: Number of bytes received 0 to 1 F9 0
4294967295
01D2 Port 6: Number of bytes sent 0 to 1 F9 0
4294967295
01D4 Port 6: Number of frames received 0 to 1 F9 0
4294967295
01D6 Port 6: Number of frames sent 0 to 1 F9 0
4294967295
01D8 Port 6: Total bytes received 0 to 1 F9 0
4294967295
01DA Port 6: Total frames received 0 to 1 F9 0
4294967295
01DC Port 6: Number of broadcast frames 0 to 1 F9 0
received 4294967295
01DE Port 6: Number of multicast frames 0 to 1 F9 0
received 4294967295
01E0 Port 6: Number of frames with CRC 0 to 1 F9 0
error 4294967295
01E2 Port 6: Number of oversized frames 0 to 1 F9 0
received 4294967295
01E4 Port 6: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
01E6 Port 6: Number of jabber frames 0 to 1 F9 0
received 4294967295
01E8 Port 6: Number of collisions occurred 0 to 1 F9 0
4294967295
01EA Port 6: Number of late collisions 0 to 1 F9 0
occurred 4294967295
01EC Port 6: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
01EE Port 6: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
01F0 Port 6: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
01F2 Port 6: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
01F4 Port 6: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
01F6 Port 6: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
01F8 Port 6: Number of MAC error packets 0 to 1 F9 0
4294967295
01FA Port 6: Number of dropped received 0 to 1 F9 0
packets 4294967295
01FC Port 6: Number of multicast frames 0 to 1 F9 0
sent 4294967295
01FE Port 6: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0200 Port 6: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0202 Port 7: Number of bytes received 0 to 1 F9 0
4294967295
0204 Port 7: Number of bytes sent 0 to 1 F9 0
4294967295
0206 Port 7: Number of frames received 0 to 1 F9 0
4294967295

18–12 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 10 of 33)

Address Description Range Step Format Default
0208 Port 7: Number of frames sent 0 to 1 F9 0
4294967295
020A Port 7: Total bytes received 0 to 1 F9 0
4294967295
020C Port 7: Total frames received 0 to 1 F9 0
4294967295
020E Port 7: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0210 Port 7: Number of multicast frames 0 to 1 F9 0
received 4294967295
0212 Port 7: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0214 Port 7: Number of oversized frames 0 to 1 F9 0
received 4294967295
0216 Port 7: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0218 Port 7: Number of jabber frames 0 to 1 F9 0
received 4294967295
021A Port 7: Number of collisions occurred 0 to 1 F9 0
4294967295
021C Port 7: Number of late collisions 0 to 1 F9 0
occurred 4294967295
021E Port 7: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0220 Port 7: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0222 Port 7: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0224 Port 7: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0226 Port 7: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0228 Port 7: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
022A Port 7: Number of MAC error packets 0 to 1 F9 0
4294967295
022C Port 7: Number of dropped received 0 to 1 F9 0
packets 4294967295
022E Port 7: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0230 Port 7: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0232 Port 7: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0234 Port 8: Number of bytes received 0 to 1 F9 0
4294967295
0236 Port 8: Number of bytes sent 0 to 1 F9 0
4294967295
0238 Port 8: Number of frames received 0 to 1 F9 0
4294967295
023A Port 8: Number of frames sent 0 to 1 F9 0
4294967295
023C Port 8: Total bytes received 0 to 1 F9 0
4294967295
023E Port 8: Total frames received 0 to 1 F9 0
4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–13

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 11 of 33)

Address Description Range Step Format Default
0240 Port 8: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0242 Port 8: Number of multicast frames 0 to 1 F9 0
received 4294967295
0244 Port 8: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0246 Port 8: Number of oversized frames 0 to 1 F9 0
received 4294967295
0248 Port 8: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
024A Port 8: Number of jabber frames 0 to 1 F9 0
received 4294967295
024C Port 8: Number of collisions occurred 0 to 1 F9 0
4294967295
024E Port 8: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0250 Port 8: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0252 Port 8: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0254 Port 8: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0256 Port 8: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0258 Port 8: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
025A Port 8: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
025C Port 8: Number of MAC error packets 0 to 1 F9 0
4294967295
025E Port 8: Number of dropped received 0 to 1 F9 0
packets 4294967295
0260 Port 8: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0262 Port 8: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0264 Port 8: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0266 Port 9: Number of bytes received 0 to 1 F9 0
4294967295
0268 Port 9: Number of bytes sent 0 to 1 F9 0
4294967295
026A Port 9: Number of frames received 0 to 1 F9 0
4294967295
026C Port 9: Number of frames sent 0 to 1 F9 0
4294967295
026E Port 9: Total bytes received 0 to 1 F9 0
4294967295
0270 Port 9: Total frames received 0 to 1 F9 0
4294967295
0272 Port 9: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0274 Port 9: Number of multicast frames 0 to 1 F9 0
received 4294967295
0276 Port 9: Number of frames with CRC 0 to 1 F9 0
error 4294967295

18–14 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 12 of 33)

Address Description Range Step Format Default
0278 Port 9: Number of oversized frames 0 to 1 F9 0
received 4294967295
027A Port 9: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
027C Port 9: Number of jabber frames 0 to 1 F9 0
received 4294967295
027E Port 9: Number of collisions occurred 0 to 1 F9 0
4294967295
0280 Port 9: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0282 Port 9: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0284 Port 9: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0286 Port 9: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0288 Port 9: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
028A Port 9: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
028C Port 9: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
028E Port 9: Number of MAC error packets 0 to 1 F9 0
4294967295
0290 Port 9: Number of dropped received 0 to 1 F9 0
packets 4294967295
0292 Port 9: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0294 Port 9: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0296 Port 9: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0298 Port 10: Number of bytes received 0 to 1 F9 0
4294967295
029A Port 10: Number of bytes sent 0 to 1 F9 0
4294967295
029C Port 10: Number of frames received 0 to 1 F9 0
4294967295
029E Port 10: Number of frames sent 0 to 1 F9 0
4294967295
02A0 Port 10: Total bytes received 0 to 1 F9 0
4294967295
02A2 Port 10: Total frames received 0 to 1 F9 0
4294967295
02A4 Port 10: Number of broadcast frames 0 to 1 F9 0
received 4294967295
02A6 Port 10: Number of multicast frames 0 to 1 F9 0
received 4294967295
02A8 Port 10: Number of frames with CRC 0 to 1 F9 0
error 4294967295
02AA Port 10: Number of oversized frames 0 to 1 F9 0
received 4294967295
02AC Port 10: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
02AE Port 10: Number of jabber frames 0 to 1 F9 0
received 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–15

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 13 of 33)

Address Description Range Step Format Default
02B0 Port 10: Number of collisions occurred 0 to 1 F9 0
4294967295
02B2 Port 10: Number of late collisions 0 to 1 F9 0
occurred 4294967295
02B4 Port 10: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
02B6 Port 10: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
02B8 Port 10: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
02BA Port 10: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
02BC Port 10: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
02BE Port 10: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
02C0 Port 10: Number of MAC error packets 0 to 1 F9 0
4294967295
02C2 Port 10: Number of dropped received 0 to 1 F9 0
packets 4294967295
02C4 Port 10: Number of multicast frames 0 to 1 F9 0
sent 4294967295
02C6 Port 10: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
02C8 Port 10: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
02CA Port 11: Number of bytes received 0 to 1 F9 0
4294967295
02CC Port 11: Number of bytes sent 0 to 1 F9 0
4294967295
02CE Port 11: Number of frames received 0 to 1 F9 0
4294967295
02D0 Port 11: Number of frames sent 0 to 1 F9 0
4294967295
02D2 Port 11: Total bytes received 0 to 1 F9 0
4294967295
02D4 Port 11: Total frames received 0 to 1 F9 0
4294967295
02D6 Port 11: Number of broadcast frames 0 to 1 F9 0
received 4294967295
02D8 Port 11: Number of multicast frames 0 to 1 F9 0
received 4294967295
02DA Port 11: Number of frames with CRC 0 to 1 F9 0
error 4294967295
02DC Port 11: Number of oversized frames 0 to 1 F9 0
received 4294967295
02DE Port 11: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
02E0 Port 11: Number of jabber frames 0 to 1 F9 0
received 4294967295
02E2 Port 11: Number of collisions occurred 0 to 1 F9 0
4294967295
02E4 Port 11: Number of late collisions 0 to 1 F9 0
occurred 4294967295
02E6 Port 11: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295

18–16 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 14 of 33)

Address Description Range Step Format Default
02E8 Port 11: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
02EA Port 11: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
02EC Port 11: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
02EE Port 11: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
02F0 Port 11: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
02F2 Port 11: Number of MAC error packets 0 to 1 F9 0
4294967295
02F4 Port 11: Number of dropped received 0 to 1 F9 0
packets 4294967295
02F6 Port 11: Number of multicast frames 0 to 1 F9 0
sent 4294967295
02F8 Port 11: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
02FA Port 11: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
02FC Port 12: Number of bytes received 0 to 1 F9 0
4294967295
02FE Port 12: Number of bytes sent 0 to 1 F9 0
4294967295
0300 Port 12: Number of frames received 0 to 1 F9 0
4294967295
0302 Port 12: Number of frames sent 0 to 1 F9 0
4294967295
0304 Port 12: Total bytes received 0 to 1 F9 0
4294967295
0306 Port 12: Total frames received 0 to 1 F9 0
4294967295
0308 Port 12: Number of broadcast frames 0 to 1 F9 0
received 4294967295
030A Port 12: Number of multicast frames 0 to 1 F9 0
received 4294967295
030C Port 12: Number of frames with CRC 0 to 1 F9 0
error 4294967295
030E Port 12: Number of oversized frames 0 to 1 F9 0
received 4294967295
0310 Port 12: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0312 Port 12: Number of jabber frames 0 to 1 F9 0
received 4294967295
0314 Port 12: Number of collisions occurred 0 to 1 F9 0
4294967295
0316 Port 12: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0318 Port 12: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
031A Port 12: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
031C Port 12: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
031E Port 12: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–17

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 15 of 33)

Address Description Range Step Format Default
0320 Port 12: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0322 Port 12: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0324 Port 12: Number of MAC error packets 0 to 1 F9 0
4294967295
0326 Port 12: Number of dropped received 0 to 1 F9 0
packets 4294967295
0328 Port 12: Number of multicast frames 0 to 1 F9 0
sent 4294967295
032A Port 12: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
032C Port 12: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
032E Port 13: Number of bytes received 0 to 1 F9 0
4294967295
0330 Port 13: Number of bytes sent 0 to 1 F9 0
4294967295
0332 Port 13: Number of frames received 0 to 1 F9 0
4294967295
0334 Port 13: Number of frames sent 0 to 1 F9 0
4294967295
0336 Port 13: Total bytes received 0 to 1 F9 0
4294967295
0338 Port 13: Total frames received 0 to 1 F9 0
4294967295
033A Port 13: Number of broadcast frames 0 to 1 F9 0
received 4294967295
033C Port 13: Number of multicast frames 0 to 1 F9 0
received 4294967295
033E Port 13: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0340 Port 13: Number of oversized frames 0 to 1 F9 0
received 4294967295
0342 Port 13: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0344 Port 13: Number of jabber frames 0 to 1 F9 0
received 4294967295
0346 Port 13: Number of collisions occurred 0 to 1 F9 0
4294967295
0348 Port 13: Number of late collisions 0 to 1 F9 0
occurred 4294967295
034A Port 13: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
034C Port 13: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
034E Port 13: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0350 Port 13: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0352 Port 13: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0354 Port 13: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0356 Port 13: Number of MAC error packets 0 to 1 F9 0
4294967295

18–18 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 16 of 33)

Address Description Range Step Format Default
0358 Port 13: Number of dropped received 0 to 1 F9 0
packets 4294967295
035A Port 13: Number of multicast frames 0 to 1 F9 0
sent 4294967295
035C Port 13: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
035E Port 13: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0360 Port 14: Number of bytes received 0 to 1 F9 0
4294967295
0362 Port 14: Number of bytes sent 0 to 1 F9 0
4294967295
0364 Port 14: Number of frames received 0 to 1 F9 0
4294967295
0366 Port 14: Number of frames sent 0 to 1 F9 0
4294967295
0368 Port 14: Total bytes received 0 to 1 F9 0
4294967295
036A Port 14: Total frames received 0 to 1 F9 0
4294967295
036C Port 14: Number of broadcast frames 0 to 1 F9 0
received 4294967295
036E Port 14: Number of multicast frames 0 to 1 F9 0
received 4294967295
0370 Port 14: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0372 Port 14: Number of oversized frames 0 to 1 F9 0
received 4294967295
0374 Port 14: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0376 Port 14: Number of jabber frames 0 to 1 F9 0
received 4294967295
0378 Port 14: Number of collisions occurred 0 to 1 F9 0
4294967295
037A Port 14: Number of late collisions 0 to 1 F9 0
occurred 4294967295
037C Port 14: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
037E Port 14: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0380 Port 14: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0382 Port 14: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0384 Port 14: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0386 Port 14: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0388 Port 14: Number of MAC error packets 0 to 1 F9 0
4294967295
038A Port 14: Number of dropped received 0 to 1 F9 0
packets 4294967295
038C Port 14: Number of multicast frames 0 to 1 F9 0
sent 4294967295
038E Port 14: Number of broadcast frames 0 to 1 F9 0
sent 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–19

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 17 of 33)

Address Description Range Step Format Default
0390 Port 14: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0392 Port 15: Number of bytes received 0 to 1 F9 0
4294967295
0394 Port 15: Number of bytes sent 0 to 1 F9 0
4294967295
0396 Port 15: Number of frames received 0 to 1 F9 0
4294967295
0398 Port 15: Number of frames sent 0 to 1 F9 0
4294967295
039A Port 15: Total bytes received 0 to 1 F9 0
4294967295
039C Port 15: Total frames received 0 to 1 F9 0
4294967295
039E Port 15: Number of broadcast frames 0 to 1 F9 0
received 4294967295
03A0 Port 15: Number of multicast frames 0 to 1 F9 0
received 4294967295
03A2 Port 15: Number of frames with CRC 0 to 1 F9 0
error 4294967295
03A4 Port 15: Number of oversized frames 0 to 1 F9 0
received 4294967295
03A6 Port 15: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
03A8 Port 15: Number of jabber frames 0 to 1 F9 0
received 4294967295
03AA Port 15: Number of collisions occurred 0 to 1 F9 0
4294967295
03AC Port 15: Number of late collisions 0 to 1 F9 0
occurred 4294967295
03AE Port 15: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
03B0 Port 15: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
03B2 Port 15: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
03B4 Port 15: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
03B6 Port 15: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
03B8 Port 15: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
03BA Port 15: Number of MAC error packets 0 to 1 F9 0
4294967295
03BC Port 15: Number of dropped received 0 to 1 F9 0
packets 4294967295
03BE Port 15: Number of multicast frames 0 to 1 F9 0
sent 4294967295
03C0 Port 15: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
03C2 Port 15: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
03C4 Port 16: Number of bytes received 0 to 1 F9 0
4294967295
03C6 Port 16: Number of bytes sent 0 to 1 F9 0
4294967295

18–20 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 18 of 33)

Address Description Range Step Format Default
03C8 Port 16: Number of frames received 0 to 1 F9 0
4294967295
03CA Port 16: Number of frames sent 0 to 1 F9 0
4294967295
03CC Port 16: Total bytes received 0 to 1 F9 0
4294967295
03CE Port 16: Total frames received 0 to 1 F9 0
4294967295
03D0 Port 16: Number of broadcast frames 0 to 1 F9 0
received 4294967295
03D2 Port 16: Number of multicast frames 0 to 1 F9 0
received 4294967295
03D4 Port 16: Number of frames with CRC 0 to 1 F9 0
error 4294967295
03D6 Port 16: Number of oversized frames 0 to 1 F9 0
received 4294967295
03D8 Port 16: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
03DA Port 16: Number of jabber frames 0 to 1 F9 0
received 4294967295
03DC Port 16: Number of collisions occurred 0 to 1 F9 0
4294967295
03DE Port 16: Number of late collisions 0 to 1 F9 0
occurred 4294967295
03E0 Port 16: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
03E2 Port 16: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
03E4 Port 16: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
03E6 Port 16: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
03E8 Port 16: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
03EA Port 16: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
03EC Port 16: Number of MAC error packets 0 to 1 F9 0
4294967295
03EE Port 16: Number of dropped received 0 to 1 F9 0
packets 4294967295
03F0 Port 16: Number of multicast frames 0 to 1 F9 0
sent 4294967295
03F2 Port 16: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
03F4 Port 16: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
03F6 Port 17: Number of bytes received 0 to 1 F9 0
4294967295
03F8 Port 17: Number of bytes sent 0 to 1 F9 0
4294967295
03FA Port 17: Number of frames received 0 to 1 F9 0
4294967295
03FC Port 17: Number of frames sent 0 to 1 F9 0
4294967295
03FE Port 17: Total bytes received 0 to 1 F9 0
4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–21

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 19 of 33)

Address Description Range Step Format Default
0400 Port 17: Total frames received 0 to 1 F9 0
4294967295
0402 Port 17: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0404 Port 17: Number of multicast frames 0 to 1 F9 0
received 4294967295
0406 Port 17: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0408 Port 17: Number of oversized frames 0 to 1 F9 0
received 4294967295
040A Port 17: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
040C Port 17: Number of jabber frames 0 to 1 F9 0
received 4294967295
040E Port 17: Number of collisions occurred 0 to 1 F9 0
4294967295
0410 Port 17: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0412 Port 17: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0414 Port 17: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0416 Port 17: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0418 Port 17: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
041A Port 17: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
041C Port 17: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
041E Port 17: Number of MAC error packets 0 to 1 F9 0
4294967295
0420 Port 17: Number of dropped received 0 to 1 F9 0
packets 4294967295
0422 Port 17: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0424 Port 17: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0426 Port 17: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0428 Port 18: Number of bytes received 0 to 1 F9 0
4294967295
042A Port 18: Number of bytes sent 0 to 1 F9 0
4294967295
042C Port 18: Number of frames received 0 to 1 F9 0
4294967295
042E Port 18: Number of frames sent 0 to 1 F9 0
4294967295
0430 Port 18: Total bytes received 0 to 1 F9 0
4294967295
0432 Port 18: Total frames received 0 to 1 F9 0
4294967295
0434 Port 18: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0436 Port 18: Number of multicast frames 0 to 1 F9 0
received 4294967295

18–22 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 20 of 33)

Address Description Range Step Format Default
0438 Port 18: Number of frames with CRC 0 to 1 F9 0
error 4294967295
043A Port 18: Number of oversized frames 0 to 1 F9 0
received 4294967295
043C Port 18: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
043E Port 18: Number of jabber frames 0 to 1 F9 0
received 4294967295
0440 Port 18: Number of collisions occurred 0 to 1 F9 0
4294967295
0442 Port 18: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0444 Port 18: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0446 Port 18: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0448 Port 18: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
044A Port 18: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
044C Port 18: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
044E Port 18: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0450 Port 18: Number of MAC error packets 0 to 1 F9 0
4294967295
0452 Port 18: Number of dropped received 0 to 1 F9 0
packets 4294967295
0454 Port 18: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0456 Port 18: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0458 Port 18: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
045A Port 19: Number of bytes received 0 to 1 F9 0
4294967295
045C Port 19: Number of bytes sent 0 to 1 F9 0
4294967295
045E Port 19: Number of frames received 0 to 1 F9 0
4294967295
0460 Port 19: Number of frames sent 0 to 1 F9 0
4294967295
0462 Port 19: Total bytes received 0 to 1 F9 0
4294967295
0464 Port 19: Total frames received 0 to 1 F9 0
4294967295
0466 Port 19: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0468 Port 19: Number of multicast frames 0 to 1 F9 0
received 4294967295
046A Port 19: Number of frames with CRC 0 to 1 F9 0
error 4294967295
046C Port 19: Number of oversized frames 0 to 1 F9 0
received 4294967295
046E Port 19: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–23

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 21 of 33)

Address Description Range Step Format Default
0470 Port 19: Number of jabber frames 0 to 1 F9 0
received 4294967295
0472 Port 19: Number of collisions occurred 0 to 1 F9 0
4294967295
0474 Port 19: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0476 Port 19: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0478 Port 19: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
047A Port 19: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
047C Port 19: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
047E Port 19: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0480 Port 19: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0482 Port 19: Number of MAC error packets 0 to 1 F9 0
4294967295
0484 Port 19: Number of dropped received 0 to 1 F9 0
packets 4294967295
0486 Port 19: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0488 Port 19: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
048A Port 19: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
048C Port 20: Number of bytes received 0 to 1 F9 0
4294967295
048E Port 20: Number of bytes sent 0 to 1 F9 0
4294967295
0490 Port 20: Number of frames received 0 to 1 F9 0
4294967295
0492 Port 20: Number of frames sent 0 to 1 F9 0
4294967295
0494 Port 20: Total bytes received 0 to 1 F9 0
4294967295
0496 Port 20: Total frames received 0 to 1 F9 0
4294967295
0498 Port 20: Number of broadcast frames 0 to 1 F9 0
received 4294967295
049A Port 20: Number of multicast frames 0 to 1 F9 0
received 4294967295
049C Port 20: Number of frames with CRC 0 to 1 F9 0
error 4294967295
049E Port 20: Number of oversized frames 0 to 1 F9 0
received 4294967295
04A0 Port 20: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
04A2 Port 20: Number of jabber frames 0 to 1 F9 0
received 4294967295
04A4 Port 20: Number of collisions occurred 0 to 1 F9 0
4294967295
04A6 Port 20: Number of late collisions 0 to 1 F9 0
occurred 4294967295

18–24 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 22 of 33)

Address Description Range Step Format Default
04A8 Port 20: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
04AA Port 20: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
04AC Port 20: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
04AE Port 20: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
04B0 Port 20: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
04B2 Port 20: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
04B4 Port 20: Number of MAC error packets 0 to 1 F9 0
4294967295
04B6 Port 20: Number of dropped received 0 to 1 F9 0
packets 4294967295
04B8 Port 20: Number of multicast frames 0 to 1 F9 0
sent 4294967295
04BA Port 20: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
04BC Port 20: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
04BE Port 21: Number of bytes received 0 to 1 F9 0
4294967295
04C0 Port 21: Number of bytes sent 0 to 1 F9 0
4294967295
04C2 Port 21: Number of frames received 0 to 1 F9 0
4294967295
04C4 Port 21: Number of frames sent 0 to 1 F9 0
4294967295
04C6 Port 21: Total bytes received 0 to 1 F9 0
4294967295
04C8 Port 21: Total frames received 0 to 1 F9 0
4294967295
04CA Port 21: Number of broadcast frames 0 to 1 F9 0
received 4294967295
04CC Port 21: Number of multicast frames 0 to 1 F9 0
received 4294967295
04CE Port 21: Number of frames with CRC 0 to 1 F9 0
error 4294967295
04D0 Port 21: Number of oversized frames 0 to 1 F9 0
received 4294967295
04D2 Port 21: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
04D4 Port 21: Number of jabber frames 0 to 1 F9 0
received 4294967295
04D6 Port 21: Number of collisions occurred 0 to 1 F9 0
4294967295
04D8 Port 21: Number of late collisions 0 to 1 F9 0
occurred 4294967295
04DA Port 21: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
04DC Port 21: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
04DE Port 21: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–25

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 23 of 33)

Address Description Range Step Format Default
04E0 Port 21: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
04E2 Port 21: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
04E4 Port 21: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
04E6 Port 21: Number of MAC error packets 0 to 1 F9 0
4294967295
04E8 Port 21: Number of dropped received 0 to 1 F9 0
packets 4294967295
04EA Port 21: Number of multicast frames 0 to 1 F9 0
sent 4294967295
04EC Port 21: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
04EE Port 21: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
04F0 Port 22: Number of bytes received 0 to 1 F9 0
4294967295
04F2 Port 22: Number of bytes sent 0 to 1 F9 0
4294967295
04F4 Port 22: Number of frames received 0 to 1 F9 0
4294967295
04F6 Port 22: Number of frames sent 0 to 1 F9 0
4294967295
04F8 Port 22: Total bytes received 0 to 1 F9 0
4294967295
04FA Port 22: Total frames received 0 to 1 F9 0
4294967295
04FC Port 22: Number of broadcast frames 0 to 1 F9 0
received 4294967295
04FE Port 22: Number of multicast frames 0 to 1 F9 0
received 4294967295
0500 Port 22: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0502 Port 22: Number of oversized frames 0 to 1 F9 0
received 4294967295
0504 Port 22: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0506 Port 22: Number of jabber frames 0 to 1 F9 0
received 4294967295
0508 Port 22: Number of collisions occurred 0 to 1 F9 0
4294967295
050A Port 22: Number of late collisions 0 to 1 F9 0
occurred 4294967295
050C Port 22: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
050E Port 22: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0510 Port 22: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0512 Port 22: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0514 Port 22: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0516 Port 22: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295

18–26 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 24 of 33)

Address Description Range Step Format Default
0518 Port 22: Number of MAC error packets 0 to 1 F9 0
4294967295
051A Port 22: Number of dropped received 0 to 1 F9 0
packets 4294967295
051C Port 22: Number of multicast frames 0 to 1 F9 0
sent 4294967295
051E Port 22: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0520 Port 22: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0522 Port 23: Number of bytes received 0 to 1 F9 0
4294967295
0524 Port 23: Number of bytes sent 0 to 1 F9 0
4294967295
0526 Port 23: Number of frames received 0 to 1 F9 0
4294967295
0528 Port 23: Number of frames sent 0 to 1 F9 0
4294967295
052A Port 23: Total bytes received 0 to 1 F9 0
4294967295
052C Port 23: Total frames received 0 to 1 F9 0
4294967295
052E Port 23: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0530 Port 23: Number of multicast frames 0 to 1 F9 0
received 4294967295
0532 Port 23: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0534 Port 23: Number of oversized frames 0 to 1 F9 0
received 4294967295
0536 Port 23: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0538 Port 23: Number of jabber frames 0 to 1 F9 0
received 4294967295
053A Port 23: Number of collisions occurred 0 to 1 F9 0
4294967295
053C Port 23: Number of late collisions 0 to 1 F9 0
occurred 4294967295
053E Port 23: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0540 Port 23: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0542 Port 23: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0544 Port 23: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0546 Port 23: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0548 Port 23: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
054A Port 23: Number of MAC error packets 0 to 1 F9 0
4294967295
054C Port 23: Number of dropped received 0 to 1 F9 0
packets 4294967295
054E Port 23: Number of multicast frames 0 to 1 F9 0
sent 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–27

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 25 of 33)

Address Description Range Step Format Default
0550 Port 23: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0552 Port 23: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0554 Port 24: Number of bytes received 0 to 1 F9 0
4294967295
0556 Port 24: Number of bytes sent 0 to 1 F9 0
4294967295
0558 Port 24: Number of frames received 0 to 1 F9 0
4294967295
055A Port 24: Number of frames sent 0 to 1 F9 0
4294967295
055C Port 24: Total bytes received 0 to 1 F9 0
4294967295
055E Port 24: Total frames received 0 to 1 F9 0
4294967295
0560 Port 24: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0562 Port 24: Number of multicast frames 0 to 1 F9 0
received 4294967295
0564 Port 24: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0566 Port 24: Number of oversized frames 0 to 1 F9 0
received 4294967295
0568 Port 24: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
056A Port 24: Number of jabber frames 0 to 1 F9 0
received 4294967295
056C Port 24: Number of collisions occurred 0 to 1 F9 0
4294967295
056E Port 24: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0570 Port 24: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0572 Port 24: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0574 Port 24: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0576 Port 24: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0578 Port 24: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
057A Port 24: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
057C Port 24: Number of MAC error packets 0 to 1 F9 0
4294967295
057E Port 24: Number of dropped received 0 to 1 F9 0
packets 4294967295
0580 Port 24: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0582 Port 24: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0584 Port 24: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0586 Port 25: Number of bytes received 0 to 1 F9 0
4294967295

18–28 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 26 of 33)

Address Description Range Step Format Default
0588 Port 25: Number of bytes sent 0 to 1 F9 0
4294967295
058A Port 25: Number of frames received 0 to 1 F9 0
4294967295
058C Port 25: Number of frames sent 0 to 1 F9 0
4294967295
058E Port 25: Total bytes received 0 to 1 F9 0
4294967295
0590 Port 25: Total frames received 0 to 1 F9 0
4294967295
0592 Port 25: Number of broadcast frames 0 to 1 F9 0
received 4294967295
0594 Port 25: Number of multicast frames 0 to 1 F9 0
received 4294967295
0596 Port 25: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0598 Port 25: Number of oversized frames 0 to 1 F9 0
received 4294967295
059A Port 25: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
059C Port 25: Number of jabber frames 0 to 1 F9 0
received 4294967295
059E Port 25: Number of collisions occurred 0 to 1 F9 0
4294967295
05A0 Port 25: Number of late collisions 0 to 1 F9 0
occurred 4294967295
05A2 Port 25: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
05A4 Port 25: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
05A6 Port 25: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
05A8 Port 25: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
05AA Port 25: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
05AC Port 25: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
05AE Port 25: Number of MAC error packets 0 to 1 F9 0
4294967295
05B0 Port 25: Number of dropped received 0 to 1 F9 0
packets 4294967295
05B2 Port 25: Number of multicast frames 0 to 1 F9 0
sent 4294967295
05B4 Port 25: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
05B6 Port 25: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
05B8 Port 26: Number of bytes received 0 to 1 F9 0
4294967295
05BA Port 26: Number of bytes sent 0 to 1 F9 0
4294967295
05BC Port 26: Number of frames received 0 to 1 F9 0
4294967295
05BE Port 26: Number of frames sent 0 to 1 F9 0
4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–29

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 27 of 33)

Address Description Range Step Format Default
05C0 Port 26: Total bytes received 0 to 1 F9 0
4294967295
05C2 Port 26: Total frames received 0 to 1 F9 0
4294967295
05C4 Port 26: Number of broadcast frames 0 to 1 F9 0
received 4294967295
05C6 Port 26: Number of multicast frames 0 to 1 F9 0
received 4294967295
05C8 Port 26: Number of frames with CRC 0 to 1 F9 0
error 4294967295
05CA Port 26: Number of oversized frames 0 to 1 F9 0
received 4294967295
05CC Port 26: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
05CE Port 26: Number of jabber frames 0 to 1 F9 0
received 4294967295
05D0 Port 26: Number of collisions occurred 0 to 1 F9 0
4294967295
05D2 Port 26: Number of late collisions 0 to 1 F9 0
occurred 4294967295
05D4 Port 26: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
05D6 Port 26: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
05D8 Port 26: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
05DA Port 26: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
05DC Port 26: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
05DE Port 26: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
05E0 Port 26: Number of MAC error packets 0 to 1 F9 0
4294967295
05E2 Port 26: Number of dropped received 0 to 1 F9 0
packets 4294967295
05E4 Port 26: Number of multicast frames 0 to 1 F9 0
sent 4294967295
05E6 Port 26: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
05E8 Port 26: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
05EA Port 27: Number of bytes received 0 to 1 F9 0
4294967295
05EC Port 27: Number of bytes sent 0 to 1 F9 0
4294967295
05EE Port 27: Number of frames received 0 to 1 F9 0
4294967295
05F0 Port 27: Number of frames sent 0 to 1 F9 0
4294967295
05F2 Port 27: Total bytes received 0 to 1 F9 0
4294967295
05F4 Port 27: Total frames received 0 to 1 F9 0
4294967295
05F6 Port 27: Number of broadcast frames 0 to 1 F9 0
received 4294967295

18–30 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 28 of 33)

Address Description Range Step Format Default
05F8 Port 27: Number of multicast frames 0 to 1 F9 0
received 4294967295
05FA Port 27: Number of frames with CRC 0 to 1 F9 0
error 4294967295
05FC Port 27: Number of oversized frames 0 to 1 F9 0
received 4294967295
05FE Port 27: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0600 Port 27: Number of jabber frames 0 to 1 F9 0
received 4294967295
0602 Port 27: Number of collisions occurred 0 to 1 F9 0
4294967295
0604 Port 27: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0606 Port 27: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0608 Port 27: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
060A Port 27: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
060C Port 27: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
060E Port 27: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0610 Port 27: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0612 Port 27: Number of MAC error packets 0 to 1 F9 0
4294967295
0614 Port 27: Number of dropped received 0 to 1 F9 0
packets 4294967295
0616 Port 27: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0618 Port 27: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
061A Port 27: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
061C Port 28: Number of bytes received 0 to 1 F9 0
4294967295
061E Port 28: Number of bytes sent 0 to 1 F9 0
4294967295
0620 Port 28: Number of frames received 0 to 1 F9 0
4294967295
0622 Port 28: Number of frames sent 0 to 1 F9 0
4294967295
0624 Port 28: Total bytes received 0 to 1 F9 0
4294967295
0626 Port 28: Total frames received 0 to 1 F9 0
4294967295
0628 Port 28: Number of broadcast frames 0 to 1 F9 0
received 4294967295
062A Port 28: Number of multicast frames 0 to 1 F9 0
received 4294967295
062C Port 28: Number of frames with CRC 0 to 1 F9 0
error 4294967295
062E Port 28: Number of oversized frames 0 to 1 F9 0
received 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–31

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 29 of 33)

Address Description Range Step Format Default
0630 Port 28: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0632 Port 28: Number of jabber frames 0 to 1 F9 0
received 4294967295
0634 Port 28: Number of collisions occurred 0 to 1 F9 0
4294967295
0636 Port 28: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0638 Port 28: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
063A Port 28: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
063C Port 28: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
063E Port 28: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0640 Port 28: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0642 Port 28: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0644 Port 28: Number of MAC error packets 0 to 1 F9 0
4294967295
0646 Port 28: Number of dropped received 0 to 1 F9 0
packets 4294967295
0648 Port 28: Number of multicast frames 0 to 1 F9 0
sent 4294967295
064A Port 28: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
064C Port 28: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
064E Port 29: Number of bytes received 0 to 1 F9 0
4294967295
0650 Port 29: Number of bytes sent 0 to 1 F9 0
4294967295
0652 Port 29: Number of frames received 0 to 1 F9 0
4294967295
0654 Port 29: Number of frames sent 0 to 1 F9 0
4294967295
0656 Port 29: Total bytes received 0 to 1 F9 0
4294967295
0658 Port 29: Total frames received 0 to 1 F9 0
4294967295
065A Port 29: Number of broadcast frames 0 to 1 F9 0
received 4294967295
065C Port 29: Number of multicast frames 0 to 1 F9 0
received 4294967295
065E Port 29: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0660 Port 29: Number of oversized frames 0 to 1 F9 0
received 4294967295
0662 Port 29: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0664 Port 29: Number of jabber frames 0 to 1 F9 0
received 4294967295
0666 Port 29: Number of collisions occurred 0 to 1 F9 0
4294967295

18–32 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 30 of 33)

Address Description Range Step Format Default
0668 Port 29: Number of late collisions 0 to 1 F9 0
occurred 4294967295
066A Port 29: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
066C Port 29: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
066E Port 29: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0670 Port 29: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0672 Port 29: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
0674 Port 29: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
0676 Port 29: Number of MAC error packets 0 to 1 F9 0
4294967295
0678 Port 29: Number of dropped received 0 to 1 F9 0
packets 4294967295
067A Port 29: Number of multicast frames 0 to 1 F9 0
sent 4294967295
067C Port 29: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
067E Port 29: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0680 Port 30: Number of bytes received 0 to 1 F9 0
4294967295
0682 Port 30: Number of bytes sent 0 to 1 F9 0
4294967295
0684 Port 30: Number of frames received 0 to 1 F9 0
4294967295
0686 Port 30: Number of frames sent 0 to 1 F9 0
4294967295
0688 Port 30: Total bytes received 0 to 1 F9 0
4294967295
068A Port 30: Total frames received 0 to 1 F9 0
4294967295
068C Port 30: Number of broadcast frames 0 to 1 F9 0
received 4294967295
068E Port 30: Number of multicast frames 0 to 1 F9 0
received 4294967295
0690 Port 30: Number of frames with CRC 0 to 1 F9 0
error 4294967295
0692 Port 30: Number of oversized frames 0 to 1 F9 0
received 4294967295
0694 Port 30: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
0696 Port 30: Number of jabber frames 0 to 1 F9 0
received 4294967295
0698 Port 30: Number of collisions occurred 0 to 1 F9 0
4294967295
069A Port 30: Number of late collisions 0 to 1 F9 0
occurred 4294967295
069C Port 30: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
069E Port 30: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–33

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 31 of 33)

Address Description Range Step Format Default
06A0 Port 30: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
06A2 Port 30: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
06A4 Port 30: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
06A6 Port 30: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
06A8 Port 30: Number of MAC error packets 0 to 1 F9 0
4294967295
06AA Port 30: Number of dropped received 0 to 1 F9 0
packets 4294967295
06AC Port 30: Number of multicast frames 0 to 1 F9 0
sent 4294967295
06AE Port 30: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
06B0 Port 30: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
06B2 Port 31: Number of bytes received 0 to 1 F9 0
4294967295
06B4 Port 31: Number of bytes sent 0 to 1 F9 0
4294967295
06B6 Port 31: Number of frames received 0 to 1 F9 0
4294967295
06B8 Port 31: Number of frames sent 0 to 1 F9 0
4294967295
06BA Port 31: Total bytes received 0 to 1 F9 0
4294967295
06BC Port 31: Total frames received 0 to 1 F9 0
4294967295
06BE Port 31: Number of broadcast frames 0 to 1 F9 0
received 4294967295
06C0 Port 31: Number of multicast frames 0 to 1 F9 0
received 4294967295
06C2 Port 31: Number of frames with CRC 0 to 1 F9 0
error 4294967295
06C4 Port 31: Number of oversized frames 0 to 1 F9 0
received 4294967295
06C6 Port 31: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
06C8 Port 31: Number of jabber frames 0 to 1 F9 0
received 4294967295
06CA Port 31: Number of collisions occurred 0 to 1 F9 0
4294967295
06CC Port 31: Number of late collisions 0 to 1 F9 0
occurred 4294967295
06CE Port 31: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
06D0 Port 31: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
06D2 Port 31: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
06D4 Port 31: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
06D6 Port 31: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295

18–34 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 32 of 33)

Address Description Range Step Format Default
06D8 Port 31: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
06DA Port 31: Number of MAC error packets 0 to 1 F9 0
4294967295
06DC Port 31: Number of dropped received 0 to 1 F9 0
packets 4294967295
06DE Port 31: Number of multicast frames 0 to 1 F9 0
sent 4294967295
06E0 Port 31: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
06E2 Port 31: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
06E4 Port 32: Number of bytes received 0 to 1 F9 0
4294967295
06E6 Port 32: Number of bytes sent 0 to 1 F9 0
4294967295
06E8 Port 32: Number of frames received 0 to 1 F9 0
4294967295
06EA Port 32: Number of frames sent 0 to 1 F9 0
4294967295
06EC Port 32: Total bytes received 0 to 1 F9 0
4294967295
06EE Port 32: Total frames received 0 to 1 F9 0
4294967295
06F0 Port 32: Number of broadcast frames 0 to 1 F9 0
received 4294967295
06F2 Port 32: Number of multicast frames 0 to 1 F9 0
received 4294967295
06F4 Port 32: Number of frames with CRC 0 to 1 F9 0
error 4294967295
06F6 Port 32: Number of oversized frames 0 to 1 F9 0
received 4294967295
06F8 Port 32: Number of bad fragments 0 to 1 F9 0
received (<64 bytes) 4294967295
06FA Port 32: Number of jabber frames 0 to 1 F9 0
received 4294967295
06FC Port 32: Number of collisions occurred 0 to 1 F9 0
4294967295
06FE Port 32: Number of late collisions 0 to 1 F9 0
occurred 4294967295
0700 Port 32: Number of 64-byte frames 0 to 1 F9 0
received/sent 4294967295
0702 Port 32: Number of 65 to 127 byte 0 to 1 F9 0
frames received/sent 4294967295
0704 Port 32: Number of 128 to 255 byte 0 to 1 F9 0
frames received/sent 4294967295
0706 Port 32: Number of 256 to 511 byte 0 to 1 F9 0
frames received/sent 4294967295
0708 Port 32: Number of 512 to 1023 byte 0 to 1 F9 0
frames received/sent 4294967295
070A Port 32: Number of 1023 to maximum 0 to 1 F9 0
byte frames received/sent 4294967295
070C Port 32: Number of MAC error packets 0 to 1 F9 0
4294967295
070E Port 32: Number of dropped received 0 to 1 F9 0
packets 4294967295

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–35

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

Table 18–1: Modbus memory map (Sheet 33 of 33)

Address Description Range Step Format Default
0710 Port 32: Number of multicast frames 0 to 1 F9 0
sent 4294967295
0712 Port 32: Number of broadcast frames 0 to 1 F9 0
sent 4294967295
0714 Port 32: Number of <64 byte fragments 0 to 1 F9 0
with good CRC 4294967295
0716 Serial Number --- --- String Varies

18–36 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL

18.2.2 Format Codes

• Bitmap: 32-bit group of bits, packed into two registers. Encoded in big endian.
• F1: 16-bit unsigned integer
• F2: Enumeration - power alarm
0 = power supply good
1 = power supply fail
• F3: Enumeration - OFF/ON
0 = Off
1 = On
• F4: Enumeration: port type
0 = Giga - GBIC
1 = Copper - TP
2 = Fiber - 10
3 = Fiber - 100
4 = Giga - 10/100/1000 (triple speed)
5 = Giga - Copper 1000 TP
6 = Giga - SFP
• F9: 32-bit unsigned long
• String: A sequence of octets, packed 2 to one register in sequence.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL 18–37

MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL

18–38 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Appendix A: Revision History &

Warranty

Revision History & Warranty

A.1 Revision History

A.1.1 Change Notes

Table A–1: Revision history

Part Number Revision Release Date
1601-9107-A1 22 April 2009
1601-9107-A2 16 February 2010
1601-9107-A3 5 July 2012
1601-9107-A4 31 September 20125

A.1.2 Changes to the Manual

Table A–2: Updates for Manual Revision A4

Section Description
General New Manual A4
General Added and corrected section number references

Table A–3: Updates for Manual Revision A3

Section Description
General New Manual A3
General Insert new Safety definitions and icons

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL A–1

REVISION HISTORY & WARRANTY CHAPTER A: REVISION HISTORY & WARRANTY

Table A–4: Updates for Manual Revision A1

Section Description
General New Manual A1

A–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER A: REVISION HISTORY & WARRANTY REVISION HISTORY & WARRANTY

A.2 Warranty

A.2.1 GE Digital Energy Warranty Statement

General Electric Digital Energy Inc. (GE Digital Energy) warrants each switch it
manufactures to be free from defects in material and workmanship under normal use and
service for a period of 24 months from date of shipment from factory.
In the event of a failure covered by warranty, GE Digital Energy will undertake to repair or
replace the relay providing the warrantor determined that it is defective and it is returned
with all transportation charges prepaid to an authorized service centre or the factory.
Repairs or replacement under warranty will be made without charge.
Warranty shall not apply to any relay which has been subject to misuse, negligence,
accident, incorrect installation or use not in accordance with instructions nor any unit that
has been altered outside a GE Digital Energy authorized factory outlet.
GE Digital Energy is not liable for special, indirect or consequential damages or for loss of
profit or for expenses sustained as a result of a relay malfunction, incorrect application or
adjustment.
For complete text of Warranty (including limitations and disclaimers), refer to GE Digital
Energy Standard Conditions of Sale.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL A–3

REVISION HISTORY & WARRANTY CHAPTER A: REVISION HISTORY & WARRANTY

A–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Appendix B: DC Power Input

DC Power Input

B.1 Specifications for Multilink ML800 Switches, DC Power at 12, 24, –48, 125,
and 250 V DC Power input
Each Multilink Model ML800 Managed Switch requires DC power input, at 12, 24, 48, 125
and 250 V DC nominal. The wide range of DC power input types qualifies this product for
use in 12, 24, 48, 125 and 250 V DC applications in different industries.
DC Power Terminals: “+”, “-” are internally floating so that user may ground either.

GND: ground wire connection to the ML800 chassis screw.

FIGURE B–1: Location of Chassis Ground

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL B–1

DC POWER INPUT CHAPTER B: DC POWER INPUT

Power Consumption:
20 watts typical (for a fully loaded fiber model with 2Gb)
15 watts typical (for 8 ports, copper and 100Mb fiber)
12 V DC Power Input nominal (range 8 to 18VDC)

24 V DC Power Input nominal (range 18 to 36VDC)

-48 V DC Power Input nominal (range 36 to 60VDC)
125 V DC Power Input nominal (range 88 to 150VDC)
250 V DC Power Input nominal (range 160 to 300VDC)
Standard ML800 DC Power Input Terminal Block : “ -, GND, + ”
See also Section 1.3 - Technical Specifications, for the ML800 base unit

B–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER B: DC POWER INPUT DC POWER INPUT

B.2 12, 24, –48, 125, and 250 V DC Power, Theory of Operation

The 12, 24, -48VDC, 125, and 250 V DC power options are designed using diodes inside on
each DC power input line behind the two external power connection terminals, so that the
power from an external source can only flow into the hub. This allows the Switch to
operate only whenever DC power is correctly applied to the two inputs. It protects the
Switch from incorrect DC input connections. An incorrect polarity connection, for example,
will neither affect the Switch, its internal power supply, nor will it blow the fuse in the
internal power supply.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL B–3

DC POWER INPUT CHAPTER B: DC POWER INPUT

B.3 Applications for DC-Powered Ethernet Switches

Multilink ML800 Switches are easily installed in a variety of applications where 12, 24, -
48VDC, 125, and 250 V DC power is used as the primary power source. The DC power
configuration capability provides an Ethernet networking solution utilizing a special power
supply in switches with a proven track record.
The –48 V DC solution is particularly useful in the telecommunication industry, where it is
common for facilities to operate on -48 V DC power. Such companies include regular and
wireless telephone service providers, Internet Service Providers (ISPs) and other
communication companies. In addition, many high availability equipment services, such
as broadcasters, publishers, newspaper operations, brokerage firms and other facilities
often use a battery backup system to maintain operations in the event of a power failure. It
is also frequently used for computer system backup, management and operations
monitoring equipment.
The 24 V and 125 V DC options are particularly useful in the industrial environment, where
it is common for facilities to operate on 24 V DC or 125 V DC power. The 125 V DC options
are mainly used in power utilities, such as electrical substations, electrical generating
plants, etc. The 24 V DC applications are mainly in heavy duty industrial automation such
as factory floor, process plants, HVAC, military equipment, etc.

B–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER B: DC POWER INPUT DC POWER INPUT

B.4 ML800, 12, 24, –48, 125, and 250 V DC Installation

This section describes the proper connection of the 12, 24, –48, 125, and 250 V DC leads to
the DC power terminal block on the Multilink ML800 Switch. The DC terminal block on the
Multilink ML800 Managed Switch is located on the left front of the unit and is equipped with
four (4) screw-down lead posts. The power terminals are identified as positive (+) and
negative (-), and they are electrically floating inside the unit so that either may be grounded
by the user if desired. The chassis is “earth” or ground (GND).
The connection procedure is straightforward. Simply insert the DC leads to the Switch’s
power terminals, positive (+) and negative (-) screws. The use of Ground (GND) connects to
the Switch chassis screw provided under the DC terminal. Ensure that each lead is securely
tightened.

Always use a voltmeter to measure the voltage of the incoming power supply and figure
Note

out the +ve potential lead or -ve potential lead. The more +ve potential lead will connect to
NOTE
the post labeled “+ve” and the rest to the “-ve”. The GND can be hooked up at the last
When power is applied, the green PWR LED will illuminate.

The GND should be hooked up first. The ML800 unit has a floating ground, so the user may
Note

elect to Ground either + or - terminal to suit the customer’s use.

NOTE
Before connecting live power lines to the Terminal Block of –48 V DC, 12 V DC, 24 V DC, 125
V DC, or 250 V DC products, always use a digital voltmeter to measure the output voltage
of the power supply and determine the lead which is more “+ve potential”. The more “+ve”
voltage lead from 48 V or –48 V supply must be connected to the post labeled “+”.

B.4.1 UL Requirements for DC-powered units

48 V DC products must be installed with a readily accessible disconnect device in the

building installation supply circuit to the product.
Minimum 18 AWG cable for connection to a Centralized DC power source.
1. Minimum 14 AWG cable for connection to an earth wiring.
2. Use only with Listed 10 A circuit breaker provided in building installation.
3. “Complies with FDA radiation performance standards, 21 CFR subchapter J.”
or equivalent.
4. Fastening torque of the lugs on the terminal block: 9 inch-pound max.
5. To secure a centralized DC Power Source cable , use at least four cable ties to
secure the cable to the rack at least 4 inches apart, with the first one located
within 6 inches of the terminal block.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL B–5

DC POWER INPUT CHAPTER B: DC POWER INPUT

B.5 Operation
Operation of Multilink ML800 Switches with the optional -48 V DC, 12 V DC, 24 V DC,
125 V DC, or 250 V DC dual-source power input is identical to that of the standard single-
source DC-powered models.

B–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

GE
Digital Energy

Multilink ML800

Appendix C: Internal DC Dual-

Source Power Input
Option
Internal DC Dual-Source Power Input Option

C.1 Specifications - for Multilink ML800 Edge Switch

Power Supply (Internal, -48VDC Dual-Source)
DC Power Connector: First Source: “A+”, “A-“, 2nd Source “B-“, “B+”
GND: Ground wire connection to the hub chassis screw
Input: Two separate sources, each at 36 - 60 VDC
Power Supply (Internal, 12VDC Dual-Source, model # Dual-Src-12V)
DC Power Connector: First Source: “A+”, “A-“, 2nd Source “B-“, “B+”
GND: Ground wire connection to the hub chassis screw
Input: Two separate sources, each at 8-18 VDC
Power Supply (Internal, 24VDC Dual-Source, model # Dual-Src-24V)
DC Power Connector: First Source: “A+”, “A-“, 2nd Source “B-“, “B+”
GND: Ground wire connection to the hub chassis screw
Input: Two separate sources, each at 18 - 36 VDC
Power Supply (Internal, 125VDC Dual-Source, model # Dual-Src-125V)
DC Power Connector: First Source: “A+”, “A-“, 2nd Source “B-“, “B+”
GND: Ground wire connection to the hub chassis screw
Input: Two separate sources, each at 88 - 150 VDC
Power Supply (Internal, 250VDC Dual-Source, model # Dual-Src-250V)
DC Power Connector: First Source: “A+”, “A-“, 2nd Source “B-“, “B+”
GND: Ground wire connection to the hub chassis screw
Input: Two separate sources, each at 160 - 300 VDC

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL C–1

INTERNAL DC DUAL-SOURCE POWER INPUT OPTION CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION

With the exception of the dual DC input power connections and the power supply, all
specifications and configuration options for the Multilink ML800 -48VDC, 12VDC, 24VDC,
125VDC and 250VDC models with this Dual-Source option are identical to those listed in
the Multilink ML800 Edge Switches Installation and User Guide, including Appendix B
“Internal DC Power Supply Option”

C–2 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION INTERNAL DC DUAL-SOURCE POWER INPUT OPTION

C.2 MULTILINK ML800, with DC Dual-Source option

The ML800-Switch models with the internal -48 V DC, 12 V DC, 24 V DC, 125 V DC, and
250 V DC Dual-Source power supply are designed for installations where a battery plant is
the power source, and where two separate power sources are utilized in order to increase
operational uptime and to simplify maintenance.
The functionality of the Multilink ML800 Switch -48 V DC, 12 V DC, 24 V DC, 125 V DC, and
250 V DC Dual-Source Option units are identical to the AC-powered models.

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL C–3

INTERNAL DC DUAL-SOURCE POWER INPUT OPTION CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION

C.3 Dual-Source Option, Theory of Operation

The Dual-Source DC power option is designed using diodes inside of the chassis on each
DC power input line. A diode is placed in each of the four input lines (behind the four
external power connection terminals) so that power from an external source can only flow
into the unit. This allows the unit to operate whenever DC power is correctly applied to
either or both of the two inputs.

C–4 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION INTERNAL DC DUAL-SOURCE POWER INPUT OPTION

C.4 Features and Benefits of the Dual-Source Design

1. The Switch unit can receive power from either input, “A” or “B”. The hub will normally
draw its power from the DC source with the highest voltage at a given time.
2. The Switch unit will not allow power to flow from a higher voltage input to a lower
voltage input, i.e. the two DC power sources are not mixed together by the hub.
3. When one correct DC input is present, the Switch will receive power if the other DC
input is absent, or even if it is connected with reverse polarity or shorted or grounded.
4. Reverse polarity connections, if they should accidentally occur on either input, will not
damage the Switch or power supply internally (nor will it blow the fuse in the internal
power supply) because of the blocking action of the diodes. This is true even if one
input connection is reversed while the Switch is operating from the other source.
5. The Switch will not receive power (and will not work) when both inputs are
simultaneously absent or are both incorrectly connected.

FIGURE C–1: Dual Source Terminal Block

MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL C–5

INTERNAL DC DUAL-SOURCE POWER INPUT OPTION CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION

C.5 Installation
This section describes the proper connection of the -48 V DC, 12 V DC, 24 V DC, 125 V DC,
and 250 V DC dual source leads to the power terminal block on the Multilink ML800 Switch
(shown in Figure above)
The terminal block is located on the left front of the unit next to the Alarm terminal block
and is equipped with four (4) screw-down lead posts. The primary terminals are identified
as positive (A+), negative (A-), and the secondary power terminals as negative (B-), positive
(B+). The chassis is earth/ground (GND). The Dual Source terminal block for the 12, 24, 48,
125, and 250 V DC are the same.

The GND should be hooked up first. The ML800 unit has a floating ground, so the user may
Note

elect to Ground either + or - terminal to suit the customer’s use. Before connecting live
NOTE
power lines to the terminal block, always use a digital voltmeter to measure the output
voltage of the power supply and determine the lead which is more “+ve potential”. The
more “+ve” voltage lead from a +ve or –ve power supply must be connected to the post
labeled “+”.
The connection procedure is straightforward. Simply connect the DC leads to the Switch’s
power terminals, positive (+) and negative (-) screws. The use of Ground (GND) is optional; it
connects to the Switch chassis. Ensure that each lead is securely tightened.

C–6 MULTILINK ML800 MANAGED EDGE SWITCH – INSTRUCTION MANUAL

Manual B30
No ratings yet
Manual B30
336 pages
Manual TV
No ratings yet
Manual TV
64 pages
DDX 9121b Overflow Solutions
No ratings yet
DDX 9121b Overflow Solutions
2 pages
Sony Hcd-Shake33 Hcd-Shake77 Ver1.0 SM
100% (3)
Sony Hcd-Shake33 Hcd-Shake77 Ver1.0 SM
120 pages
Solis Manual 75 100K 5G USA V1,1
No ratings yet
Solis Manual 75 100K 5G USA V1,1
40 pages
Generator and Engine Generador y Motor Gerador e Motor: PCI2200 PCI2800 PCI5000
No ratings yet
Generator and Engine Generador y Motor Gerador e Motor: PCI2200 PCI2800 PCI5000
92 pages
REJ603 Um 1MDU07206-YN ENd
No ratings yet
REJ603 Um 1MDU07206-YN ENd
56 pages
Modulo Receptor Ge-Rcv1 - Instr
No ratings yet
Modulo Receptor Ge-Rcv1 - Instr
1 page
IOM979820 Rev00
No ratings yet
IOM979820 Rev00
142 pages
Form-6 Yard Mount Reclose Control - S280702 - 10000
No ratings yet
Form-6 Yard Mount Reclose Control - S280702 - 10000
48 pages
Vented Block Battery Catalogue - Nov 2017
No ratings yet
Vented Block Battery Catalogue - Nov 2017
16 pages
Catalogo Max Kohl A G
No ratings yet
Catalogo Max Kohl A G
74 pages
Zelio-Logic Relays: File 8501
No ratings yet
Zelio-Logic Relays: File 8501
16 pages
Relay Manual for Electrical Technicians
No ratings yet
Relay Manual for Electrical Technicians
59 pages
Ajustes Del Emcp Ii+ (Caterpillar Electronic Modular Control Panel Ii+)
No ratings yet
Ajustes Del Emcp Ii+ (Caterpillar Electronic Modular Control Panel Ii+)
4 pages
Split Piso Techo - 10SEER
No ratings yet
Split Piso Techo - 10SEER
4 pages
Manual CSI-4-5KTL1P-GI-FL
No ratings yet
Manual CSI-4-5KTL1P-GI-FL
28 pages
GEC-Motor Protection Relay - Protección Por Corriente Soplador PDF
No ratings yet
GEC-Motor Protection Relay - Protección Por Corriente Soplador PDF
4 pages
ATESS HPS User Manual - V3
No ratings yet
ATESS HPS User Manual - V3
23 pages
Multilin 889: Grid Solutions
No ratings yet
Multilin 889: Grid Solutions
16 pages
Xpower Blue II Service Manual en
No ratings yet
Xpower Blue II Service Manual en
42 pages
Manual Sa Akx95lm K
No ratings yet
Manual Sa Akx95lm K
150 pages
TV Service Manual for Technicians
No ratings yet
TV Service Manual for Technicians
30 pages
VW Passat B7 NMS - Maintenance Procedures
No ratings yet
VW Passat B7 NMS - Maintenance Procedures
10 pages
Intelligent Solar Controller Guide
No ratings yet
Intelligent Solar Controller Guide
17 pages
PWRcell TOU Guide
No ratings yet
PWRcell TOU Guide
10 pages
Beninca Brainy
100% (1)
Beninca Brainy
52 pages
PowerFlex AC Drives - Fault 77 (IR Volts Range)
No ratings yet
PowerFlex AC Drives - Fault 77 (IR Volts Range)
4 pages
D10S Assembly (Sales)
No ratings yet
D10S Assembly (Sales)
13 pages
EM619001EM619002-IVY Technical Data Sheet
No ratings yet
EM619001EM619002-IVY Technical Data Sheet
10 pages
PJ500M PDF
0% (1)
PJ500M PDF
92 pages
APC Smart-UPS RT: User Manual
No ratings yet
APC Smart-UPS RT: User Manual
23 pages
Cutler Hammer Panel
No ratings yet
Cutler Hammer Panel
44 pages
Inteliats 70 Global Guide 2023-04-27
No ratings yet
Inteliats 70 Global Guide 2023-04-27
444 pages
LG Wd1873rds Manual de Usuario
No ratings yet
LG Wd1873rds Manual de Usuario
76 pages
User Manual Auto-Reclosing Protector
No ratings yet
User Manual Auto-Reclosing Protector
8 pages
Iom 1202 082013
100% (3)
Iom 1202 082013
137 pages
Industrial Butterfly Valves Guide
No ratings yet
Industrial Butterfly Valves Guide
22 pages
RM2048A Rectifier Manual 1 0
0% (1)
RM2048A Rectifier Manual 1 0
13 pages
PM700 Manual
No ratings yet
PM700 Manual
192 pages
Operator'S Guide: THE Model SG - 3428B Loudspeaker Test Oscillator
No ratings yet
Operator'S Guide: THE Model SG - 3428B Loudspeaker Test Oscillator
21 pages
CS12N60F
No ratings yet
CS12N60F
10 pages
Singer 5802 C Sewing Machine Manual PDF
0% (1)
Singer 5802 C Sewing Machine Manual PDF
88 pages
IW4069UB IKSemiconductor
No ratings yet
IW4069UB IKSemiconductor
5 pages
Explanation of Digital and Analog Quantities
No ratings yet
Explanation of Digital and Analog Quantities
31 pages
Datasheet Batería OPzV 16OPzV2000
No ratings yet
Datasheet Batería OPzV 16OPzV2000
2 pages
31-51790 Ref Mini Manual
No ratings yet
31-51790 Ref Mini Manual
2 pages
Philips Mcd183
0% (1)
Philips Mcd183
29 pages
Iecen 62040 1 2
No ratings yet
Iecen 62040 1 2
11 pages
JVC HXD 77 UJ Service Manual
No ratings yet
JVC HXD 77 UJ Service Manual
51 pages
Jumpstart ps1100
67% (3)
Jumpstart ps1100
16 pages
Automatico Protector LCD
100% (1)
Automatico Protector LCD
10 pages
Eat On
No ratings yet
Eat On
160 pages
MANUAL TV LG 49UJ620T-DA - 1602 - 0102 - WebOS3.5
No ratings yet
MANUAL TV LG 49UJ620T-DA - 1602 - 0102 - WebOS3.5
67 pages
6SL3220 2yd26
No ratings yet
6SL3220 2yd26
3 pages
Multilink ML3000/ML3100 Ethernet Switch Series: Grid Solutions
No ratings yet
Multilink ML3000/ML3100 Ethernet Switch Series: Grid Solutions
382 pages
Manual GE MULTILINK ML1200
No ratings yet
Manual GE MULTILINK ML1200
344 pages
745to845 Retrofit A1
No ratings yet
745to845 Retrofit A1
44 pages
345QSG Ac
No ratings yet
345QSG Ac
94 pages
Manual Español Relevador 489
No ratings yet
Manual Español Relevador 489
40 pages
User Name and Password Are Same (Your Dise Code) : User Guide To Fill Online NMMS Application Form
No ratings yet
User Name and Password Are Same (Your Dise Code) : User Guide To Fill Online NMMS Application Form
4 pages
Avi 77 Installation Instructions Ahz 2020
No ratings yet
Avi 77 Installation Instructions Ahz 2020
8 pages
Polymer vs Bentonite: Shear Strength Effects
No ratings yet
Polymer vs Bentonite: Shear Strength Effects
12 pages
Syllabus - Sem 3 (Scheme 2024)
No ratings yet
Syllabus - Sem 3 (Scheme 2024)
26 pages
Generation Beta
100% (1)
Generation Beta
2 pages
MX-FXX2: 1. Unpacking
No ratings yet
MX-FXX2: 1. Unpacking
5 pages
PLM 09 v05
No ratings yet
PLM 09 v05
12 pages
Title: AI in Art and Music Generation
No ratings yet
Title: AI in Art and Music Generation
8 pages
Online Job Portal
No ratings yet
Online Job Portal
126 pages
Wa0040.
No ratings yet
Wa0040.
3 pages
Final
No ratings yet
Final
24 pages
Redspot History and Culture Past Paper - Google Search
9% (11)
Redspot History and Culture Past Paper - Google Search
1 page
FEUHS Pending Requirement Agreement Form S.Y. 22 23 - Grade 7 1
No ratings yet
FEUHS Pending Requirement Agreement Form S.Y. 22 23 - Grade 7 1
2 pages
PhiX Loading Concentrations
No ratings yet
PhiX Loading Concentrations
2 pages
3 - Software Engineering
No ratings yet
3 - Software Engineering
29 pages
TSQ-179 (V) (CGS) - Archived 1/2006
No ratings yet
TSQ-179 (V) (CGS) - Archived 1/2006
9 pages
Lindell 902 De-Esser Manual
No ratings yet
Lindell 902 De-Esser Manual
7 pages
EEE321 Mid Autumn 2022
No ratings yet
EEE321 Mid Autumn 2022
2 pages
R&S CMW500 R&S CMW280
No ratings yet
R&S CMW500 R&S CMW280
10 pages
Lab-6: Amplifiers: 1. Objective
No ratings yet
Lab-6: Amplifiers: 1. Objective
5 pages
SV2701 3401
No ratings yet
SV2701 3401
182 pages
RDBMS 12 Question Answer
No ratings yet
RDBMS 12 Question Answer
31 pages
PDCCH Optimization for LTE Performance
100% (1)
PDCCH Optimization for LTE Performance
1 page
IFIX Advanced
No ratings yet
IFIX Advanced
15 pages
Fiber To The Home (FTTH)
No ratings yet
Fiber To The Home (FTTH)
6 pages
Final Draft For Poster IC 2024
No ratings yet
Final Draft For Poster IC 2024
3 pages
Post-Quantum Cryptography: IT Security For Critical Infrastructures
No ratings yet
Post-Quantum Cryptography: IT Security For Critical Infrastructures
3 pages
Product Flyer UTi730E
No ratings yet
Product Flyer UTi730E
1 page
Azure Fundamentals Exam Prep
0% (1)
Azure Fundamentals Exam Prep
9 pages
Energy Efficiency in Pump Systems
No ratings yet
Energy Efficiency in Pump Systems
30 pages