Digital Energy Multilin MultiLink ML1200 Managed Field Switch Instruction Manual Firmware Revision 3.3x Manual P/N: 1601-9095-A1 Manual Order Code: GEK-113538 Copyright © 2009 GE Multilin Tel: (905) 294-6222 Fax: (905) 201-2098 Internet: http://www.GEmultilin.
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.
TOC TABLE OF CONTENTS Table of Contents 1: INTRODUCTION GETTING STARTED ............................................................................................................................. 1-1 INSPECTING THE PACKAGE AND PRODUCT ........................................................................ 1-1 ORDER CODES ..................................................................................................................................... 1-2 SPECIFICATIONS ..............................
TABLE OF CONTENTS ALARM CONTACTS FOR MONITORING INTERNAL POWER, AND SOFTWARE TRAPS ..... 3-8 ML1200 PORT MODULE (PM) INSTALLATION ................................................................. 3-9 CONNECTING A MANAGEMENT CONSOLE TERMINAL TO MULTILINK ML1200 (SERIAL-RJ-45 CONSOLE PORT) ........ 3-10 4: OPERATION FUNCTIONALITY ..................................................................................................................................4-1 SWITCHING FUNCTIONALITY ......................
TOC TABLE OF CONTENTS SECURITY LOGS ..................................................................................................................... 6-8 AUTHORIZED MANAGERS ..................................................................................................... 6-10 CONFIGURING PORT SECURITY WITH ENERVISTA SOFTWARE ..................................... 6-12 COMMANDS ...........................................................................................................................
TABLE OF CONTENTS WEB MANAGEMENT SOFTWARE ............................................................10-7 DESCRIPTION .......................................................................................................................... 10-7 CONFIGURING TAG VLANS THROUGH THE COMMAND LINE INTERFACE ................ 10-12 DESCRIPTION .......................................................................................................................... 10-12 COMMANDS ..................................
TOC TABLE OF CONTENTS DESCRIPTION .......................................................................................................................... 14-9 15: IGMP OVERVIEW ............................................................................................................................................. 15-1 DESCRIPTION .......................................................................................................................... 15-1 IGMP CONCEPTS ............................
TABLE OF CONTENTS MAIN COMMANDS ................................................................................................................. 17-14 CONFIGURATION COMMANDS .............................................................................................. 17-16 18: MODBUS PROTOCOL MODBUS CONFIGURATION ........................................................................................................... 18-1 OVERVIEW .......................................................................
Digital Energy Multilin Multilink ML1200 Managed Field 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.
INTRODUCTION 1.
CHAPTER 1: INTRODUCTION 1.3 INTRODUCTION 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: .....................................................................
INTRODUCTION CHAPTER 1: INTRODUCTION 1000BASE-SX, full-duplex, multi-mode(50μm cable):............ 550m 1000BASE-LX, full-duplex, single-mode(62.5μm cable): ...... 5Km FIBER MULTI-MODE CONNECTOR TYPES SUPPORTED: Fiber Port, ST-type (twist-lock): ........................................................ Fiber multi-mode, 10Mb 10BASE-FL Fiber Port, MTRJ-type (plug-in):........................................................ SFF Fiber multi-mode100BASE-FX Fiber Port, SC-type (snap-in): ......................
CHAPTER 1: INTRODUCTION INTRODUCTION POWER CONSUMPTION 35 watts worst case (for a fully loaded fiber model) 12 watts typical (for a small 4 port copper-only model) DUAL DC POWER INPUT (OPTIONAL) A Dual-Source option is available for the 12VDC, 24VDC, – 48VDC, and 125VDC models (not the 250VDC model). 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:..............................
INTRODUCTION CHAPTER 1: INTRODUCTION APPROVALS CE Compliance North America Applicable Council Directive According to Low voltage directive EN60950-1 EMC Directive EN61000-6-2, EN61000-6-4 cULus UL60950-1 C22.2 No. 60950-1 Manufactured under a registered ISO9001 quality program ISO WARRANTY Three years, per UL 60950 temperature rating.
CHAPTER 1: INTRODUCTION 1.4 INTRODUCTION 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.
INTRODUCTION 1.4.3 CHAPTER 1: INTRODUCTION Console Screen Once the console cable is connected to the PC and the firmware configured, ML1200 legal disclaimers and other text scrolls by on the screen. The line interface prompt appears displaying the switch model number (e.g. ML1200>) 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.
CHAPTER 1: INTRODUCTION INTRODUCTION If the ML1200 is not connected to a network, then proceed to Step 3 below. or use the default IP address. Note Step 1: The ML1200 will scan the network for a DHCP server. If the server responds, the ML1200 will acquire and set the assigned IP address.
INTRODUCTION CHAPTER 1: INTRODUCTION Z Follow the steps described above for connecting the console cable and setting the console firmware. Z Power on the switch. Z Once the login prompt appears, login as manager using default password (manager). Z Configure the IP address, network mask and default gateway as per the IP addressing scheme for your network. Z Set the manager password (this step is recommended; refer to the following section).
CHAPTER 1: INTRODUCTION INTRODUCTION ML1200# show setup Version: ML1200 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: ML1200 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 ML1200# show sysconfig System Name: ML1200 System Contact: multilin.tech@ge.
INTRODUCTION 1.4.8 CHAPTER 1: INTRODUCTION 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.
CHAPTER 1: INTRODUCTION 1.4.9 INTRODUCTION 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: ML1200> help logout terminal ping telnet set walkmib Contextless Commands: ! enable show alarm ? exit whoami clear help ML1200> 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.
INTRODUCTION CHAPTER 1: INTRODUCTION ? alarm clear enable exit help logout ping set show telnet terminal walkmib whoami ML1200> The following example lists commands starting with a specific string: ML1200> s set show ML1200> In the following example, the key completes the command: ML1200> se password timeout vlan ML1200> set 1.4.10 Exiting To exit from the CLI interface and terminate the console session use the logout command.
CHAPTER 1: INTRODUCTION 1.5 INTRODUCTION 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:// Note Make sure you use HTTPS (secure HTTP) and not HTTP in the URL. 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.
INTRODUCTION CHAPTER 1: INTRODUCTION FIGURE 1–3: Login screen For the first time, Z Login with the name manager and password manager. Z 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.
CHAPTER 1: INTRODUCTION INTRODUCTION FIGURE 1–4: Welcome screen 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.
INTRODUCTION CHAPTER 1: INTRODUCTION In the following example below, the user peter was added with manager privilege after clicking the add button.
CHAPTER 1: INTRODUCTION INTRODUCTION After successfully adding a user, the added user is displayed in the list of users as shown below. Z To delete a user, click on the delete icon ( MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL )as shown below.
INTRODUCTION CHAPTER 1: INTRODUCTION The firmware will prompt to verify the delete command. Z To modify the password, view the users as described above and click on the edit icon ( ).
CHAPTER 1: INTRODUCTION INTRODUCTION 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.5.4 Modifying the Privilege Level Privilege levels cannot be changed from the EnerVista Secure Web Management (SWM) firmware.
INTRODUCTION 1.5.5 CHAPTER 1: INTRODUCTION Help Help for the EnerVista Secure Web Management software can be obtained by clicking on the Help icon as shown below. 1.5.6 Exiting Z To exit or logout, click on the logout button.
CHAPTER 1: INTRODUCTION INTRODUCTION Z Confirm the logout by selecting OK in the pop-up window.
INTRODUCTION CHAPTER 1: INTRODUCTION 1.6 ML1200 Firmware Updates 1.6.1 Updating Multilink ML1200 Firmware This section describes the process for upgrading firmware on a ML1200 Switch Module. There are several ways of updating Firmware on a Multilink ML1200: Serial using the Multilink ML1200’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 Multilin web site.
CHAPTER 1: INTRODUCTION INTRODUCTION Z Save the existing configuration (refer to section 5.4.4 - Saving Configuration for details). Z Enter the following command: ML1200# 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.
INTRODUCTION CHAPTER 1: INTRODUCTION Z Once the file transfer is completed reboot the switch with the reboot command or by cycling power. Z 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. Z Download the latest MultiLink ML1200 Managed Field Switch firmware from the GE Multilin web site.
CHAPTER 1: INTRODUCTION INTRODUCTION Z Reboot the switch when the transfer is complete. After reboot, the firmware is ready for use. Z If using TFTP, save the configuration before proceeding. GE Multilin recommends a two-step update: • first save the configuration to the TFTP server, • then load the new image and restart the switch (refer to section 5.4.4 - Saving Configuration for details on saving the configuration). Z Load the new firmware as shown below.
INTRODUCTION 1–28 CHAPTER 1: INTRODUCTION MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 2: Product Description Product Description 2.1 Overview Multilink ML1200 Managed Field Switches provide maximum configurability in their class. The fiber-rich ML1200 can be configured with up to 12 100Mb fiber ports and two Gigabit ports. For 10/100 copper, regular or PoE-equipped 10/100 RJ-45 or 10/100/1000 copper ports may be configured to a maximum or 12 at 10/100 and 2 Gig ports.
PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION 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 manage power budgets .The PoE ports will discontinue supplying power when the PoE powered devices are disconnected. This feature supports the 802.
CHAPTER 2: PRODUCT DESCRIPTION 2.1.1 PRODUCT DESCRIPTION Four-port SFF fiber modules (CC Module, CD Module), 100Mb fiber In a four-port SFF (Small Form Factor) fiber port module, all of the fiber ports are of the same speed (100Mb), mode, and connector type. Small Form Factor (SFF) Fiber Ports come in multi-mode forms MT-RJ or LC-type connectors, and single-mode form LC-type connectors.
PRODUCT DESCRIPTION 2.1.2 CHAPTER 2: PRODUCT DESCRIPTION Four-Port Copper Module, C1 Module MDIX) The ML1200’s 4-port Copper module, the C1 Module, provides four 10/100Mb switched RJ45 ports. The 10/100Mb switched ports normally (as a default setting) are independently Nway auto-negotiating and auto-crossover (MDIX) for operation at 10 or 100Mb 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).
CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION The LEDs on C2 PoE modules are slightly different compared to regular (non-PoE) RJ-45 modules as shown in the figure below. When the PoE port is in use, the PoE LED is ON when connected properly to an 803.af compliant PD device on that port. When non-PoE devices are connected, the PoE LED is OFF. The operation of Ethernet data traffic is not affected by PoE.
PRODUCT DESCRIPTION 2.1.6 CHAPTER 2: PRODUCT DESCRIPTION SFP Gigabit (1000Mbps) port modules The Gigabit port options for the modular slot come in a few different configurations of Fiber SFP’s or RJ-45’s. The Multilink ML1200 offers only SFPs (Small Form Pluggable) for Gigabit speed. There are multiple choices of SFP Gigabit transceiver types to combine with RJ-45’s for the modular slot. Up to two Gigabit ports (max.) can be configured in the modular slot C only.
CHAPTER 2: PRODUCT DESCRIPTION 2.1.8 PRODUCT DESCRIPTION Frame Buffering and Flow Control Multilink ML1200’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.
PRODUCT DESCRIPTION 2.2 CHAPTER 2: PRODUCT DESCRIPTION Features and Benefits • Managed switching for high performance Ethernet LANs. Multilink ML1200 Switches provide unicast non-blocking (all ports can run at full speed at once) performance with standard Managed Network Software included. They are typically used in LAN traffic centers with up to 12 100Mb +2 Gigabit ports for backbone connections, where managed network services are desired. • Switching services includes 802.1p QoS packet prioritization.
CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION QoS, Port- and tag-based VLANs, GVRP, IGMP Snooping, SNMPc GUI support; Event Log; SNTP client for time-of-day; BootP and DHCP client for IP configuring, and password security and Secured Web interface.
PRODUCT DESCRIPTION 2.3 CHAPTER 2: PRODUCT DESCRIPTION Applications Multilink ML1200 Field 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.
CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION Extended temperature ratings and a variety of options for AC/DC power supplies qualify this managed ML1200 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.
PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION The ML1200 Managed Fiber with the Ring-Only Mode feature 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.
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 3: Installation Installation 3.1 Preparation Before installing the equipment, it is necessary to take the following precautions: 3.1.1 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.
INSTALLATION 3.2 CHAPTER 3: INSTALLATION Connecting Ethernet Media The Multilink ML1200 Switches are specifically designed to support all standard Ethernet media types within a single Switch unit. This is accomplished by using a family of different Fiber Connectors which can be individually selected and configured per-slot. See Section 2.2 for a description of the PMs. The various media types supported along with the corresponding IEEE 802.3, 802.3D, 802.3u, 802.3AB and 802.
CHAPTER 3: INSTALLATION INSTALLATION 3.2.0.2 Connecting Fiber Optic SC-type, "Snap-In" The following procedure applies to installations using a PM with SC-type fiber connectors, i.e., using C9 Module, CA Module single-mode: When connecting fiber media to SC connectors, simply snap on the two square male connectors into the SC female jacks of the PM, until it clicks and secures. 3.2.0.3 Connecting Single-Mode Fiber Optic When using single-mode fiber cable, be sure to use single-mode fiber port connectors.
INSTALLATION CHAPTER 3: INSTALLATION 3.2.0.5 Connecting Twisted Pair (CAT5e or better, Unshielded or Shielded) The RJ-45 Gigabit ports of the Multilink ML1200 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.
CHAPTER 3: INSTALLATION INSTALLATION Module Model# Gigabit Gb Modules, fixed ports--SFP H1 - H6 Module 2 SFP H7 Module 2 CU H8 - HD Module 1SFP, 1CU HE - HJ Module 1 SFP HK Module 1 CU 3.2.0.7 Connecting Fiber Optic Cable to SFP Transceivers Note 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.
INSTALLATION 3.3 CHAPTER 3: INSTALLATION Mechanical Installation 3.3.1 DIN-Rail Mounting the Multilink ML1200 The Multilink ML1200 is designed for use in a “factory floor” industrial environment. It is available with optional DIN-Rail brackets to mount it securely in a metal factory floor enclosure, maintained vertically for proper convection cooling of the unit. The Multilink ML1200 requires one DIN-Rail mounting clip or latch for secure mounting. These may be ordered as Model # DIN-RAIL-ML1200.
CHAPTER 3: INSTALLATION INSTALLATION For best cooling of the ML1200, attach the metal brackets to metal (rather than wood or plastic). Attaching to metal helps conduct heat away from the ML1200 through the metal brackets and into the metal support structure. Since the ML1200 has special internal thermal techniques (patent pending) to move the heat generated by the electronic components inside into the case, the case may be quite warm to the touch during normal operation.
INSTALLATION 3.4 CHAPTER 3: INSTALLATION Electrical Installation 3.4.1 Powering the Multilink ML1200 Managed Field Switch The DC internal power supply supports installation environments where the DC voltage is from 18 to 150 volts depending on the model selected. The power consumption will range from about 20 up to 35 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.
CHAPTER 3: INSTALLATION INSTALLATION The Alarm Contacts are on the front left area (next to the DC power source) of the Multilink ML1200 unit and are green in color as shown in the picture. 3.4.3 ML1200 Port Module (PM) Installation Multilink ML1200 Switches are normally received from the factory with all required Port Modules installed. Note There may be situations where the PMs need to be added or replaced. Any change in configuration of the modules can be done only via factory installation.
INSTALLATION 3.4.4 CHAPTER 3: INSTALLATION Connecting a Management Console Terminal to Multilink ML1200 (Serial-RJ-45 Console Port) The serial console port on the Multilink ML1200 is different from other Multilink family switches. The Serial RJ-45 port, as shown in the picture, requires an 8-pin RJ-45 male connector to have the proper communication. (Note - the serial RJ-45 console port on the Multilink ML1200 is compatible with Cisco-type RJ-45 console port cables).
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 4: Operation Operation This chapter describes the functions and operation of the Multilink ML1200 Switch. 4.1 Functionality 4.1.1 Switching Functionality A Multilink ML1200 provides switched connectivity at Ethernet wire-speed among all of its ports. The Multilink ML1200 supports10/100Mbs for copper media and 10 or 100Mb separate traffic domains for fiber ports to maximize bandwidth utilization and network performance.
OPERATION CHAPTER 4: OPERATION 4.1.1.2 Address Learning All Multilink ML1200 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 ML1200 Switch automatically keeps up with node locations. An address-aging algorithm causes least-used addresses to fall out in favor for frequentlyused addresses. To reset the address buffer, cycle power down-and-up. 4.1.
CHAPTER 4: OPERATION OPERATION 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 autonegotiation is potentially an externally controlled process, the original “highest order mode” result can change at any time depending on network changes that may occur).
OPERATION 4.1.5 CHAPTER 4: OPERATION Power Budget Calculations for ML1200 PM’s with Fiber Media Receiver Sensitivity and Transmitter Power are the parameters necessary to compute the power budget.
CHAPTER 4: OPERATION Note OPERATION H4, HH 1000 Mb FX Single-Mode 25 (Gigabit) 1310 9/125 -3.0 -21 16 40 18 45 H5, HI 1000 Mb FX Single-Mode 40 (Gigabit) 1550 9/125 -5.0 -22 15 60 17 68 H6, HJ 1000 Mb FX Single-Mode 70 (Gigabit) 1550 9/125 -2.0 -22 18 90 20 100 * The use of either multi-mode or single-mode fiber to operate at 100Mbps speed over long distances (i.e., in excess of approx.
OPERATION 4.2 CHAPTER 4: OPERATION Multilink ML1200 Managed Field Switch Port Modules This chapter describes each Port Module (PM), including appearance, functionality, and status displays. 4.2.1 Inspecting the Package and Product This section applies only to Port Modules shipped as separate items, i.e., ML1200 PMs that are not factory installed. Examine the shipping container for obvious damage prior to installing a ML1200 PM; notify the carrier of any damage you believe occurred during shipment.
CHAPTER 4: OPERATION OPERATION Multilink ML1200 Managed Switch, the copper port supports the standard distance 100m on each port and the fiber port supports fiber optic cable distances up the IEEE-standard 100Mbps distance limits, i.e., typically 2km at full-duplex and 412m at half-duplex. Each port has an Activity (ACT) LED indicating packets being received.
OPERATION CHAPTER 4: OPERATION 4.2.2.4 CB Module, 2 Ports @100Mbps single-mode FX-SC-type, Sgl.M The CB Module is also a Fiber module equipped with 2 Single-mode (Long Reach) SC-type connectors. It provides a long reach Fiber function in one module to the ML1200 Switches, supporting 100Mb single-mode (Long-Reach) fiber network segments. The CB Module, when installed in a Multilink ML1200 Switch, supports single-mode fiber cable lengths of as much as 40+ Km (see Power Budget, Section 4.5).
CHAPTER 4: OPERATION OPERATION Each port has an Activity (ACT) LED indicating packets being received, a Link (LK) LED that indicates proper connectivity with the remote device when lit, and a FDX/HDX LED to indicate full-duplex mode when lit (or half-duplex when off). The 10/100 LED indicates 100Mbps speed when lit and at 10Mbps speed when off. 4.2.2.
OPERATION CHAPTER 4: OPERATION 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, a Link (LK) LED indicating proper connectivity with the remote device when lit, and a FDX/HDX LED indicating full-duplex mode when lit (or half-duplex when off). 4.2.2.
CHAPTER 4: OPERATION OPERATION Each port has an Activity (ACT) LED indicating packets being received, a Link (LK) LED that indicates proper connectivity with the remote device when lit, a FDX/HDX LED to indicate full-duplex mode when lit (or half-duplex when off), and a “10/100” LED indicating 100Mb when lit (or 10 Mbps when off).
OPERATION CHAPTER 4: OPERATION • In the case where the 48VDC power in not internally connected 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. 4.2.2.12 SFPs, Gigabit (1000Mbps) port modules The Multilink ML1200 offers a Gigabit option with multiple choices of copper 10/100/ 1000Mbps or Gigabit SFP Fiber modules for the modular slot.
CHAPTER 4: OPERATION OPERATION described in this section or if the Multilink ML1200 Switch is not performing as expected, do not attempt to repair the unit; instead contact your supplier for assistance or contact GE Multilin Customer Support. 4.2.3 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.
OPERATION 4–14 CHAPTER 4: OPERATION MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field 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.
IP ADDRESSING CHAPTER 5: IP ADDRESSING Z 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.
CHAPTER 5: IP ADDRESSING 5.2 IP ADDRESSING 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.
IP ADDRESSING CHAPTER 5: IP ADDRESSING 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. 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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING Z 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 ML1200. The ML1200 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 ML1200.
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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING For example: ML1200# user ML1200(user)## useraccess user=peter service=telnet enable Telnet Access Enabled. ML1200(user)## exit ML1200# show session Current Sessions: SL# 1 2 3 Sessn Id 1 2 3 Connection 163.10.10.14 163.11.11.1 163.12.12.16 User Name manager peter operator User Mode Manager Manager Operator ML1200# kill session id=3 Session Terminated ML1200# In the above example, the user with username “peter” is given telnet access.
IP ADDRESSING 5.3 CHAPTER 5: IP ADDRESSING 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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING ML1200# show sysconfig System Name: ML1200 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 ML1200# System variables can be changed. Below is a list of system variables which GE recommends changing.
IP ADDRESSING CHAPTER 5: IP ADDRESSING 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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING 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 ML1200# sntp ML1200(sntp)## setsntp server=3.94.210.5 timeout=3 retry=3 SNTP server is added to SNTP server database ML1200(sntp)## sync hour=5 ML1200(sntp)## sntp enable SNTP is already enabled.
IP ADDRESSING CHAPTER 5: IP ADDRESSING 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.
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.
IP ADDRESSING 5.4 CHAPTER 5: IP ADDRESSING System Configuration 5.4.1 Saving and Loading – Command Line Place the Switch offline while transferring Setting Files to the Switch. When transferring Settings Files from one Switch to another, the IP address of the originating Switch will also be transferred. The user must therefore reset the IP address on the receiving Switch before connecting to the network.
CHAPTER 5: IP ADDRESSING IP ADDRESSING Using Config Download, examination of the contents of the saved file would appear as shown below: ################################################################ # Copyright (c) 2001-2005 GE Multilin, Inc All rights reserved. # RESTRICTED RIGHTS # --------------------------------# Use, duplication or disclosure is subject to U.S.
IP ADDRESSING CHAPTER 5: IP ADDRESSING [SYSTEM] ***Edit below this line only*** system_name=ML1200 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.
CHAPTER 5: IP ADDRESSING 5.4.3 IP ADDRESSING 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.
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— ...
CHAPTER 5: IP ADDRESSING IP ADDRESSING ML1200# show config module=snmp [HARDWARE] type= ML1200 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=.
IP ADDRESSING CHAPTER 5: IP ADDRESSING ML1200# show config module=snmp,system [HARDWARE] type= ML1200 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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING Additional capabilities have been added to save and load configurations.
IP ADDRESSING 5.4.5 CHAPTER 5: IP ADDRESSING 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 Multilin, Inc.
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 Multilin, 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.
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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING Z If the changes need to be ignored, click on Cancel and reboot the switch. Z 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 ML1200 allows hosts to be created with the necessary host names, IP addresses, user names, and passwords.
IP ADDRESSING CHAPTER 5: IP ADDRESSING Z To add a host, click the Add button. Z Fill in all the fields below to create the necessary host entries.
CHAPTER 5: IP ADDRESSING IP ADDRESSING Z 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. Note User also has the option to save one module from defaulting back to factory defaults by checking the module box before issuing kill Config command.
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.
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.
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. ML1200# kill config Do you want to erase the configuration? ['Y' or 'N'] Y Successfully erased configuration...
CHAPTER 5: IP ADDRESSING 5.5 IP ADDRESSING 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.
IP ADDRESSING CHAPTER 5: IP ADDRESSING 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 nodes. The use of anycast addresses in the IPv6 source route allows nodes to control the path along which their traffic flows.
CHAPTER 5: IP ADDRESSING IP ADDRESSING 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 Syntax ping6 - pings an IPv6 station.
IP ADDRESSING CHAPTER 5: IP ADDRESSING Syntax telnet - 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 5.5.5 List of commands in this chapter Syntax ipconfig [ip=] [mask=] [dgw=] [add|del] – configure an IPv6 address.
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 6: Access Considerations Access Considerations 6.1 Securing Access 6.1.1 Description This section explains how the access to the MultiLink ML1200 Managed Field 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 securing access for users and computers on a network.
ACCESS CONSIDERATIONS 6.1.3 CHAPTER 6: ACCESS CONSIDERATIONS 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.
CHAPTER 6: ACCESS CONSIDERATIONS 6.2 ACCESS CONSIDERATIONS 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.
ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS • remove mac - removes specific or all MAC addresses from port security lookup • signal port= - 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 port security.
CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS To deny a mac address, use the following: #port-security (port-security)##ps enable (port-security)##deny mac= port= (port-security)##action port=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.
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.
CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS Z Disable learning on required ports (for example, use the learn port=3,5 disable command). Z (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). Z Disable access to the network for unauthorized devices (Use action port=3 depending on whether the port should be disabled or the packed dropped.
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 ML1200 Managed Field Switch are logged. The events can be informational (e.g.
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..
ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS 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 ML1200 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.
CHAPTER 6: ACCESS CONSIDERATIONS Note ACCESS CONSIDERATIONS It is assumed here that the user is familiar with IP addressing schemes (e.g. class A, B, C, etc.), subnet masking and masking issues such as how many stations are allowed for a given subnet mask. 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.
ACCESS CONSIDERATIONS 6.3 CHAPTER 6: ACCESS CONSIDERATIONS Configuring Port Security with EnerVista Software 6.3.1 Commands After enabling the EnerVista Secure Web Management software, Z 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. Z To edit each port, click on the edit icon ( ).
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 ( screen is shown, the following actions can be taken for each port: ). Once the edit 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.
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.
CHAPTER 6: ACCESS CONSIDERATIONS 6.3.2 ACCESS CONSIDERATIONS Logs All events occurring on the Managed MultiLink ML1200 Managed Field 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.
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 Multilin internal diagnostic information • C (critical, severity level 4) indicates that a severe switch error has occurred.
CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS 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.
ACCESS CONSIDERATIONS 6–18 CHAPTER 6: ACCESS CONSIDERATIONS MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field 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.
ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS 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 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.
CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS 10. If the supplicant does not have the necessary credentials, a RADIUS-AccessDeny packet is relayed to the supplicant as an EAP-Failure frame. The access to the network continues to be blocked. FIGURE 7–2: 802.1x authentication details The ML1200 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.
ACCESS USING RADIUS 7.2 CHAPTER 7: ACCESS USING RADIUS 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.
CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS 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 The reauth command determines how the authenticator (MultiLink ML1200 Managed Field Switch) performs the re-authentication with the supplicant or PC.
ACCESS USING RADIUS 7.2.2 CHAPTER 7: ACCESS USING RADIUS 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. The RADIUS server is on port 2. This port is authenticated manually. If the RADIUS server is several hops away, it may be necessary to authenticate the interconnection ports.
CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS Setting port control parameters (continued) ML1200(auth)## backend port=2 supptimeout=45 servertimeout=60 maxreq=5 Successfully set backend server authentication parameter(s) ML1200(auth)## show-port backend This command sets timeout characteristics and the number of requests before access is denied. Port Supp Timeout Server Timeout Max Request (sec.) (sec.
ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS Setting port control parameters (continued) ML1200(auth)## reauth port=1 status=enable period=300 Successfully set re-authentication parameter(s) ML1200(auth)## shoW-port reauth Port Reauth Status Reauth Period (sec.
CHAPTER 7: ACCESS USING RADIUS 7.3 ACCESS USING RADIUS 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.
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. Z Select the Configuration > Radius > Port > Set menu item to configure the RADIUS characteristics of each port. Z To edit the port settings, click on the edit icon ( 7–10 ).
CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS 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. To change the port access characteristics when authenticating with a RADIUS server, Z Select the Configuration > Radius > Port > Access menu item.
ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS 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. 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.
CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS The port authentication characteristics define how the authenticator (ML1200 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).
ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS After all the port characteristics are enabled, Z Do not forget to save the configuration using the save ( ) icon and enabling RADIUS from the Configuration > Radius > Server menu.
Digital Energy Multilin Multilink ML1200 Managed Field 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.
ACCESS USING TACACS+ 8.1.2 CHAPTER 8: ACCESS USING TACACS+ TACACS+ Flow TACACS works in conjunction with the local user list on the ML1200 software (operating system). The process of authentication as well as authorization is shown in the flow chart below.
CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+ 4 Major Version 4 Minor Version 32 bits wide 8 8 Packet type Sequence number Session ID Length 8 bits Flags 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.
ACCESS USING TACACS+ 8.2 CHAPTER 8: ACCESS USING TACACS+ Configuring TACACS+ through the Command Line Interface 8.2.1 Commands There are several commands to configure TACACS+.
CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+ Example 8-1: Configuring TACACS+: ML1200# show tacplus servers ID TACACS+ Server Port Encrypt Key ======================================= 1 10.21.1.170 1 Enabled secret 2 ----3 ----4 ----5 ----- ML1200# user ML1200(user)## show tacplus status TACACS+ Status: Disabled ML1200(user)## tacplus enable TACACS+ Tunneling is enabled. ML1200(user)## tacserver add id=2 ip=10.21.1.123 encrypt=enable ke TACACS+ server is added.
ACCESS USING TACACS+ 8.3 CHAPTER 8: ACCESS USING TACACS+ Configuring TACACS+ with EnerVista Secure Web Management software Z To access the TACACS servers, select the Administration > User Mgmt > TACACS+ menu item. By default, no TACACS servers are defined. Z To add a server, click on the Add button as shown below. 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.
CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+ After the configuration is completed, Z Save the settings. Z Enable the TACACS+ services by using the Status drop down menu..
ACCESS USING TACACS+ 8–8 CHAPTER 8: ACCESS USING TACACS+ MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 9: Port Mirroring and Setup Port Mirroring and Setup 9.1 Port Mirroring 9.1.1 Description This section explains how individual characteristics of a port on a MultiLink ML1200 Managed Field 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.
PORT MIRRORING AND SETUP 9.2 CHAPTER 9: PORT MIRRORING AND SETUP 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.
CHAPTER 9: PORT MIRRORING AND SETUP 9.3 PORT MIRRORING AND SETUP Port Setup 9.3.1 Commands Each port on the MultiLink ML1200 Managed Field Switch can be setup specific port characteristics. The commands for setting the port characteristics are shown below.
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.
CHAPTER 9: PORT MIRRORING AND SETUP 9.3.2 PORT MIRRORING AND SETUP 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.
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP Back pressure and flow control (continued) ML1200(device)## backpressure rxthreshold=30 Rx Buffer Threshold set successfully ML1200(device)## show backpressure Rx Buffer Threshold : 30 ML1200(device)## show port Keys: E H M LI F = = = = = Enable Half Duplex Multiple VLAN's Listening Forwarding D F NA LE B = = = = = Disable Full Duplex Not Applicable Learning Blocking Port Name Control Dplx Media Link Speed Part Auto VlanID GVRP STP ----
CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP Back pressure and flow control (continued) ML1200(device)## show port Keys: E H M LI F = = = = = Enable Half Duplex Multiple VLAN's Listening Forwarding D F NA LE B = = = = = Disable Full Duplex Not Applicable Learning 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
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP The braoadcast-protect command enables or disables the broadcast storm protection capabilities. broadcast-protect The rate-threshold command set the rate limit in frames per second. rate-threshold port= rate= The show broadcast-protect command displays the broadcast storm protection settings show broadcast-protect In Example 9-3, the broadcast protection is turned on.
CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP Example 9-3: Preventing broadcast storms ML1200# device ML1200(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 ML1200(de
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.
CHAPTER 9: PORT MIRRORING AND SETUP 9.4 PORT MIRRORING AND SETUP 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”, Z Select the Configuration > Port > Mirroring menu item. Z Set the sniffer port and the port on which the traffic is reflected.
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP Z Make sure the Mirror Status is also set to enabled for mirroring: For security reasons, GE Multilin 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: 9.4.2 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.
CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP Z Select a specific port by using the edit icon in the Configuration > Port > Settings menu. Z Click the edit icon to open the following window. In these windows: • Port Number represents the port number on the switch.
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.
CHAPTER 9: PORT MIRRORING AND SETUP 9.4.3 PORT MIRRORING AND SETUP Broadcast Storms One of the best features of the MultiLink ML1200 Managed Field 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.
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP See details in Broadcast Storms on page 9–7 to determine the threshold level. Z 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.
Digital Energy Multilin Multilink ML1200 Managed Field 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 ML1200 Managed Field 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.
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.
CHAPTER 10: VLAN VLAN 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 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.
VLAN CHAPTER 10: VLAN 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.
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.
VLAN CHAPTER 10: VLAN start vlan= To save VLAN configuration: save To edit VLANs: edit id= [name=] port= To display the VLAN information: show vlan type= [] The following command sequence shows how to configure VLANs on a MultiLink ML1200 Managed Field Switch. ML1200# vlan type=port ML1200(port-vlan)## add id=2 name=test port=1-7 ML1200(port-vlan)## start vlan=all ML1200(port-vlan)## save Saving current configuration...
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.
VLAN CHAPTER 10: VLAN The currently assigned Port VLANs are displayed as follows: Z Select the Configuration > VLAN > Port-Based menu item.
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. Z Add the ports. Z Define the VLAN. Z Click OK..
VLAN CHAPTER 10: VLAN After adding the VLAN, the VLAN is not active. Activating the VLAN has to be done manually. Z To activate the VLAN, click on the Status button. Z Select VLAN ID. Z Select VLAN Status: Start . A specific VLAN can be activated or all VLANs can be activated (or disabled). Z Click OK to activate VLAN..
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.
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).
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.
VLAN CHAPTER 10: VLAN Example 10-1: Converting Port VLAN to Tag VLAN ML1200#vlan type=port ML1200(port-vlan)##show vlan type=port VLAN ID: 1 Name : Default VLAN Status : Active ======================== PORT | STATUS ======================== 5 | DOWN 6 | DOWN 7 | UP VLAN ID: 10 Name : engineering Status : Active ======================== PORT | STATUS ======================== 1 | DOWN VLAN ID: 20 Name : sales Status : Active ======================== PORT | STATUS ======================== 2 | DOWN VLAN ID: 3
CHAPTER 10: VLAN VLAN Converting Port VLAN to Tag VLAN (continued) VLAN ID: 1 Name : Default VLAN Status : Active ----------------------------------------------PORT | MODE | STATUS ----------------------------------------------1 | UNTAGGED | UP 2 | UNTAGGED | DOWN 3 | UNTAGGED | DOWN 4 | UNTAGGED | DOWN 5 | UNTAGGED | DOWN 6 | UNTAGGED | DOWN 7 | UNTAGGED | UP Note that ports 3 to 5 are “DOWN” - the VLAN configuration is preferably done before devices are plugged in to avoid connectivity repercussions.
VLAN CHAPTER 10: VLAN Converting Port VLAN to Tag VLAN (continued) VLAN ID: 1 Name : Default VLAN Status : Active ----------------------------------------------PORT | MODE | STATUS ----------------------------------------------1 | UNTAGGED | UP 2 | UNTAGGED | DOWN 3 | UNTAGGED | DOWN 4 | UNTAGGED | DOWN 5 | UNTAGGED | DOWN 6 | UNTAGGED | DOWN 7 | UNTAGGED | UP VLAN ID: 10 Name : engineering Status : Pending ----------------------------------------------PORT | MODE | STATUS --------------------------------
CHAPTER 10: VLAN VLAN Converting Port VLAN to Tag VLAN (continued) ----------------------------------------------PORT | MODE | STATUS ----------------------------------------------1 | UNTAGGED | UP 2 | UNTAGGED | DOWN 6 | UNTAGGED | DOWN 7 | UNTAGGED | UP VLAN ID: 10 Name : engineering Status : Active ----------------------------------------------PORT | MODE | STATUS ----------------------------------------------3 | UNTAGGED | DOWN 4 | UNTAGGED | DOWN 5 | UNTAGGED | DOWN VLAN ID: 20 Enable filtering on t
VLAN CHAPTER 10: VLAN Converting Port VLAN to Tag VLAN (continued) ----------------------------------------------PORT | MODE | STATUS ----------------------------------------------1 | UNTAGGED | UP 2 | UNTAGGED | DOWN 6 | UNTAGGED | DOWN 7 | UNTAGGED | UP VLAN ID: 10 Name : engineering Status : Active ----------------------------------------------PORT | MODE | STATUS ----------------------------------------------3 | TAGGED | DOWN 4 | TAGGED | DOWN 5 | TAGGED | DOWN VLAN ID: 20 Name : sales Status : Active
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 ML1200, 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).
VLAN CHAPTER 10: VLAN The next step is to define the VLANs needed. To do that, Z Click On Configuration >vlan >tag-based Menu. Z Click on the Add button.. Z Now add the necessary VLANs.
CHAPTER 10: VLAN VLAN • VLAN 30, Marketing VLAN - ports 5, 6 (note that port 5 belongs to VLAN 20, 30) Z After adding the ports and defining the VLAN, click OK. Z Click on Port Settings in the Configuration >VLAN >Tag-Based menu and enable the tagging for each port..
VLAN CHAPTER 10: VLAN Z 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, Z Select the Configuration > VLAN > Tag-Based > Tagging menu. .
CHAPTER 10: VLAN VLAN To activate the VLAN, Z Click on the Status button under the Configuration >VLAN >TagBased > Settings menu. Z Click OK. Tagged VLANs can be viewed from the Configuration > VLAN > Tag-Based > Tagging menu. To add or delete specific ports from a VLAN, Z Click on Join & Leave button from the Configuration > VLAN >. TagBased > Settings menu and specify the action. In the example below, we will take port 2 and assign it to leave VLAN 10.
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.
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 11: VLAN Registration over GARP 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 Multilin recommends that the user become familiar with the concepts and capabilities of IEEE 802.1q. 11.1.
VLAN REGISTRATION OVER GARP Note CHAPTER 11: VLAN REGISTRATION OVER GARP There must be one common VLAN (that is, one common VID) connecting all of the GVRPaware devices in the network to carry GVRP packets. GE Multilin recommends the default VLAN (DEFAULT_VLAN; VID = 1), which is automatically enabled and configured as untagged on every port of the MultiLink ML1200 Managed Field Switch.
CHAPTER 11: VLAN REGISTRATION OVER GARP VLAN REGISTRATION OVER GARP 11. Port 2 receives advertisement of VID 3. (Port 2 was already statically configured for VIDs 1, 2, 3). Note If a static VLAN is configured on at least one port of a switch, and that port has established a link with another device, then all other ports of that switch will send advertisements for that VLAN.
VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP • 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 Table 11–1: Port settings for GVRP operations Unknown VLAN mode Operations Learn Enables the port to dynamically join any VL
CHAPTER 11: VLAN REGISTRATION OVER GARP VLAN REGISTRATION OVER GARP Table 11–2: GVRP options Per-port “unknown VLAN” (GVRP) configuration Per-port static VLAN options Tagged or untagged Auto Forbid Learn Generate advertisements. Forward advertisements for other VLANs.
VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP 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.
CHAPTER 11: VLAN REGISTRATION OVER GARP 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 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.
VLAN REGISTRATION OVER GARP CHAPTER 11: VLAN REGISTRATION OVER GARP Example 11-2: Configuring GVRP ML1200# gvrp ML1200(gvrp)# show gvrp GVRP Status : Enabled ML1200(gvrp)## gvrp disable GVRP is now disabled ML1200(gvrp)## gvrp enable GVRP enabled ML1200(gvrp)## show-vlan ================================================= VLAN ID | NAME | VLAN | STATUS ================================================= 1 | Default VLAN | Static | Active 2 | Blue | Static | Active 6 | dyn6 | Dynamic | Active ML1200(gvrp)
CHAPTER 11: VLAN REGISTRATION OVER GARP VLAN REGISTRATION OVER GARP 11.3 Configuring GVRP with EnerVista Secure Web Management software 11.3.1 Example To configure GVRP, Z 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–5. The unknown VLAN parameters are configured on a per interface basis using the CLI.
VLAN REGISTRATION OVER GARP 11–10 CHAPTER 11: VLAN REGISTRATION OVER GARP MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 12: Spanning Tree Protocol (STP) 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.
SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP) 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. The table below lists the default values of the STP variables.
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 Example 12-1 illustrates the show stp command with the config parameter.
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.
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.
SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP) Example 12-3 shows how to enable STP using the above commands. 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.
CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP) priority [port=] 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.
SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP) Example 12-4: Configuring STP parameters ML1200(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:
CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP) Configuring STP parameters (continued) ML1200(stp)##show stp ports STP Port Configuration ------------------------------------------------------------------------------Port# Type Priority Path Cost State Des. Bridge Des.
SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP) Configuring STP parameters (continued) ML1200(stp)##cost port=2 value=20 Setting cost for STP...Successfully set the path cost for port 2 ML1200(stp)##show stp ports STP Port Configuration ------------------------------------------------------------------------------Port# Type Priority Path Cost State Des. Bridge Des.
CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP) Configuring STP parameters (continued) ML1200(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.
SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP) Configuring STP parameters (continued) ML1200(stp)##show stp config STP CONFIGURATION ----------------- 12–12 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:
Digital Energy Multilin Multilink ML1200 Managed Field Switch Chapter 13: Rapid Spanning Tree Protocol 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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL • 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 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL 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.
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= The rstp command enters the RSTP configuration mode and enables/disabled RSTP. By default, RSTP is disabled and has to be manually activated.
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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL • 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. • 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL Example 13-3: RSTP information from a network with multiple switches ML1200(rstp)##show stp ports RSTP Port Configuration ------------------------------------------------------------------------------Port# Type Priority Path Cost State Des. Bridge Des.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL The show-timers command displays the values of the timers set for RSTP. show-timers 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL Example 13-4: Configuring RSTP ML1200#rstp Check the status of STP or RSTP. These commands show if STP or RSTP is enabled.
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.
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
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL Configuring RSTP (continued) ML1200(rstp)##show stp ports RSTP Port Configuration ------------------------------------------------------------------------------Port# Type Priority Path Cost State Des. Bridge Des.
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 Root Bridge Forward
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL romode romode show The sequence of commands for enabling ring-only mode is shown in the following example: Example 13-5: Configuring smart RSTP, ring-only mode ML1200# rstp ML1200(rstp)##rstp enable Successfully set the RSTP status ML1200(rstp)##romode show RO-MODE status : Disabled RO-MODE set on ports : NONE ML1200(rstp)##romode add port=1,2 Added Ports: 1,2 ML1200(rstp)##romode enable RSTP Ring Only Mode Enable
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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL • Status: Indicates whether STP or RSTP is enabled. • 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.
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. Z Simply enable RSTP (or STP) and let the system default values prevail. After RSTP is enabled, the fields are updated. Z Note the Status, Time since TC, and Designated Root values.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL The port specific values for RSTP or STP are shown below. Z 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.
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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL To configure ring-only mode, ensure the first three of the four situations described above are met. To enable ring-only mode, first Z Enable RSTP by setting the STP Type to RSTP in the Administration > Set > STP Type menu: Z Select the Configuration > RSTP > Bridge RSTP menu as shown below. Z Click the Edit button to configure RSTP.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL Z Once in Edit mode, change the Status to Enable. Z 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. Z Select the Configuration > RSTP > RO Mode menu as shown below: Z Click the Edit button to configure RO Mode. Z Select the desired ports as shown below, then click OK to exit.
RAPID SPANNING TREE PROTOCOL Note CHAPTER 13: RAPID SPANNING TREE PROTOCOL Only 2 ports can be selected to Ring Only Mode. Z Select the Enabled option for the Status setting as shown below: Z Save the configuration by clicking on the 13–22 icon.
Digital Energy Multilin Multilink ML1200 Managed Field 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.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE To make the preemptive queuing possible, most switches implement at least two queue buffers. The MultiLink ML1200 Managed Field 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.
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.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE 14.2 Configuring QoS through the Command Line Interface 14.2.1 Commands The MultiLink ML1200 Managed Field Switch supports three types of QoS - Port based, Tag based and ToS based. Note QoS is disabled by default on the switch. QoS needs to be enabled and configured. The qos command enters the QoS configuration mode. qos The usage of the setqos command varies depending on the type of QOS.
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.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE 14.2.2 Example The following example shows how to configure QoS.
CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE Configuring QoS (continued) ML1200(qos)##show qos ======================================== PORT | QOS | STATUS ======================================== 1 | Port | DOWN 2 | Tag | DOWN 3 | None | DOWN 4 | None | DOWN 5 | None | DOWN 6 | None | DOWN 7 | None | DOWN ML1200(qos)##show qos type=tag ======================================== PORT | Tag | STATUS ======================================== 1 | 2 | | DOWN |
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE Configuring QoS (continued) Port priority Weight set to 1 High : 1 Low. ML1200(qos)##set-weight weight=4 ML1200(qos)##show-portweight Port priority Weight set to 8 High : 1 Low.
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, Z Select the Configuration > QoS menu items.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE Z 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.
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.
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. Z After all changes are made, save the changes using the save icon ( ).
Digital Energy Multilin Multilink ML1200 Managed Field 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.
IGMP CHAPTER 15: IGMP 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. 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.
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.
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.
CHAPTER 15: IGMP 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.1.
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 The show igmp command displays the IGMP status. show igmp The following command sequence illustrates how to enable and query the status of IGMP.
CHAPTER 15: IGMP IGMP show-group The following command sequence illustrates how to display IGMP groups: ML1200(igmp)## show-group GroupIp PortNo Timer LeavePending ---------------------------------------224.1.0.1 1 155 0 224.0.1.40 1 155 0 ML1200(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.
IGMP CHAPTER 15: IGMP 15.2.2 Example The following example shows how to configure IGMP. Example 15-1: Configuring IGMP ML1200(igmp)## set-port port=2-4 mode=forward Port mode is set. ML1200(igmp)## show-port --------------------Port | Mode --------------------1 | Auto 2 | Forwarding 3 | Forwarding 4 | Forwarding 5 | Auto 6 | Auto 7 | Auto ML1200(igmp)## show-router RouterIp PortNo Timer --------------------------------10.21.1.
CHAPTER 15: IGMP IGMP Configuring IGMP (continued) ML1200(igmp)## set-leave enable IGMP immediate leave status is enabled ML1200(igmp)## show igmp IGMP State ImmediateLeave Querier Querier Interval Querier Response Interval Multicasting Unknown Streams : : : : : : Enabled Enabled Enabled 125 10 Enabled ML1200(igmp)## set-leave disable IGMP immediate leave status is disabled ML1200(igmp)## show igmp IGMP State ImmediateLeave Querier Querier Interval Querier Response Interval Multicasting Unknown Strea
IGMP CHAPTER 15: IGMP Configuring IGMP (continued) ML1200(igmp)## show igmp IGMP State ImmediateLeave Querier Querier Interval Querier Response Interval Multicasting Unknown Streams : : : : : : Enabled Disabled Disabled 127 11 Enabled : : : : : : Enabled Disabled Disabled 127 11 Disabled : : : : : : Enabled Disabled Disabled 127 11 Enabled ML1200(igmp)## mcast disable MCAST is disabled ML1200(igmp)## show igmp IGMP State ImmediateLeave Querier Querier Interval Querier Response Interval Multicastin
CHAPTER 15: IGMP IGMP 15.3 Configuring IGMP with EnerVista Secure Web Management software 15.3.1 Example For configuring IGMP, Z 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.
IGMP CHAPTER 15: IGMP Z 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.
Digital Energy Multilin Multilink ML1200 Managed Field 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.
SNMP CHAPTER 16: SNMP authoritative. When an SNMP message does not expect a response, the sender is authoritative 16–2 • Community string - A text string used to authenticate messages between a management station and an SNMP v1/v2c engine • 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.
CHAPTER 16: SNMP SNMP • 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.
SNMP CHAPTER 16: SNMP • 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.
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.
SNMP CHAPTER 16: SNMP trap id= [type=] [host=] [community=] [port=<1-65534>] 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=] The com2sec command specifies the mapping from a source/community pair to a security name. Up to 10 entries can be specified.
CHAPTER 16: SNMP SNMP Example 16-1: Configuring SNMP ML1200# set snmp type=v1 SNMP version support is set to "v1" ML1200# 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 ----------------------- ML1200# set snmp type=all SNMP version support is set to "v1, v2c, v3
SNMP CHAPTER 16: SNMP Configuring SNMP (continued) ML1200(snmpv3)## trap add id=1 type=v1 host=3.94.200.107 Entry is added successfully ML1200(snmpv3)## show-trap ID Trap Type Host IP Community Port ================================================ 1 v1 3.94.200.107 --2 ----3 ----4 ----5 ----- ML1200(snmpv3)## show-trap id=1 Trap ID Trap Type Host IP Community Auth. Type : : : : : 1 v1 3.94.200.
CHAPTER 16: SNMP SNMP Configuring SNMP (continued) ML1200(snmpv3)## show-group ID Group Name Sec. Model Com2Sec ID ============================================= 1 2 3 4 5 6 7 8 9 10 v1 public public -------- v1 v2c usm -------- 1 1 1 -------- ML1200(snmpv3)## show-group id=1 Group ID Group Name Model Com2Sec ID : : : : 1 v1 v1 1 ML1200(snmpv3)## view add id=1 viewname=all type=included subtree=.
SNMP CHAPTER 16: SNMP Configuring SNMP (continued) ML1200(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 --------- ML1200(snmpv3)## show-access id=1 Access ID Access Name Sec. Model Sec.
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, Z Select the Configuration > SNMP menu item.
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. Z When done changing the community strings, click OK. Multiple managers can be added as shown below. Z When adding SNMP manager stations, click on the Add button on the SNMP menu screen. Z Make sure that each station can be pinged from the switch by using the Configuration > Ping menu.
CHAPTER 16: SNMP SNMP Z When done adding stations, click OK. Z When adding SNMP trap receivers, click on the Add button on the SNMP menu screen. Z Make sure that each station can be pinged from the switch by using the Administration > Ping menu. Z Determine which sorts of traps each station will receive, as shown above. If not sure, select all three types. Z When done adding trap receivers, click OK.
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. Z After all changes are made, save the changes using the save icon ( 16–14 ).
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 ML1200 Managed Field 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.
SNMP CHAPTER 16: SNMP ML1200(rmon)## show rmon event RMON Event Default Owner : test RMON Event Default Community : somestring ML1200(rmon)## exit ML1200# 16–16 MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field 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.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS • SMTP alerts can be enabled or disabled globally. • 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.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS 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> 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.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS Example 17-1: Configuring SMTP to receive SNMP trap information via e-mail ML1200#smtp ML1200(smtp)##server ip=3.94.210.25 port=25 retry=3 domain=ge.com Successfully set global SMTP server configuration ML1200(smtp)##show smtp config SMTP Global Configuration ======================================== Status : Disabled SMTP Server Host : 3.94.210.25 SMTP Server Domain : ge.
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, Z Select the Configuration > Statistics menu item. To view port-specific statistics, Z Select the Configuration > Statistics > Port Statistics menu item.
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.
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 ML1200 Managed Field 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.
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). ! The show history command displays the last 25 executed commands. If less than 25 commands were executed, only those commands executed are shown.
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 [count=<1-999>] [timeout=<1-256>] For example: ML1200# ping 3.94.248.61 3.94.248.61 is alive, count 1, time = 40ms ML1200# ping 3.94.248.61 count=3 3.94.248.61 is alive, count 1, time = 20ms 3.94.248.
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 ML1200 allows administrators to define custom prompts. The command to set a prompt is: set prompt The length of the prompt is limited to 60 characters.
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.
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= file= doctype= 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.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS For viewing each specific log, Z 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.
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.
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 syslocati
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.
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.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS The port mirroring commands are shown below. Refer to Chapter 9 - Port Mirroring and Setup for additional details. • help port-mirror • prtmr : enables/disables port mirroring functionality • setport: defines the port mirroring ports The port security commands are shown below. Refer to Chapter 6 - Securing Access for additional details.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS The Simple Mail Transfer Protocol (SMTP) commands for e-mail are shown below. Refer to Chapter 17 - E-mail for additional details. • add: adds a recipient • 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 Chapter 16 - SNMP for additional details.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS The VLAN commands are shown below. Refer to Chapter 10 - VLAN for additional details.
Digital Energy Multilin Multilink ML1200 Managed Field 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.
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL The commands enable the Modbus protocol and set the relevant Modbus slave address and communication port values. For example, ML1200# show ipconfig IP Address: 192.168.1.5 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.1.
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL 18.1.3 EnerVista Settings To modify the Modbus settings through EnerVista Secure Web Management software, Z Select the Configuration > Access > Modbus menu item.
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 18–4 Range Step Format 0000 System name (12 registers) Description - - String Default Varies 000C System contact (12 registers) - - String multilin.tech @ge.
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 2 of 33) Range Step Format Default 0062 Address Port 13 type Description 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
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 3 of 33) Address 18–6 Range Step Format Default 0090 Port 27 link status Description 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 Po
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 4 of 33) Range Step Format Default 00BE Address Port 9 activity Description 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
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 5 of 33) Address 18–8 Range Step Format Default 00F0 Port 1: Number of late collisions occurred Description 0 to 4294967295 1 F9 0 00F2 Port 1: Number of 64-byte frames received/sent 0 to 4294967295 1 F9 0 00F4 Port 1: Number of 65 to 127 byte frames received/sent 0 to 4294967295 1 F9 0 00F6 Port 1: Number of 128 to 255 byte frames received/sent 0 to 4294967295 1 F9 0 00F8 Port 1: Number of 256
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 6 of 33) Range Step Format Default 0128 Address Port 2: Number of 128 to 255 byte frames received/sent Description 0 to 4294967295 1 F9 0 012A Port 2: Number of 256 to 511 byte frames received/sent 0 to 4294967295 1 F9 0 012C Port 2: Number of 512 to 1023 byte frames received/sent 0 to 4294967295 1 F9 0 012E Port 2: Number of 1023 to maximum byte frames received/sent 0 to 4294967295 1 F9 0 0130
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 7 of 33) Address 18–10 Range Step Format Default 0160 Port 3: Number of 1023 to maximum byte frames received/sent Description 0 to 4294967295 1 F9 0 0162 Port 3: Number of MAC error packets 0 to 4294967295 1 F9 0 0164 Port 3: Number of dropped received packets 0 to 4294967295 1 F9 0 0166 Port 3: Number of multicast frames sent 0 to 4294967295 1 F9 0 0168 Port 3: Number of broadcast frames sent
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 8 of 33) Range Step Format Default 0198 Address Port 4: Number of multicast frames sent Description 0 to 4294967295 1 F9 0 019A Port 4: Number of broadcast frames sent 0 to 4294967295 1 F9 0 019C Port 4: Number of <64 byte fragments with good CRC 0 to 4294967295 1 F9 0 019E Port 5: Number of bytes received 0 to 4294967295 1 F9 0 01A0 Port 5: Number of bytes sent 0 to 4294967295 1 F9 0 01A2
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 9 of 33) Address 18–12 Range Step Format Default 01D0 Port 6: Number of bytes received Description 0 to 4294967295 1 F9 0 01D2 Port 6: Number of bytes sent 0 to 4294967295 1 F9 0 01D4 Port 6: Number of frames received 0 to 4294967295 1 F9 0 01D6 Port 6: Number of frames sent 0 to 4294967295 1 F9 0 01D8 Port 6: Total bytes received 0 to 4294967295 1 F9 0 01DA Port 6: Total frames received
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 10 of 33) Range Step Format Default 0208 Address Port 7: Number of frames sent Description 0 to 4294967295 1 F9 0 020A Port 7: Total bytes received 0 to 4294967295 1 F9 0 020C Port 7: Total frames received 0 to 4294967295 1 F9 0 020E Port 7: Number of broadcast frames received 0 to 4294967295 1 F9 0 0210 Port 7: Number of multicast frames received 0 to 4294967295 1 F9 0 0212 Port 7: Number
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 11 of 33) Address 18–14 Range Step Format Default 0240 Port 8: Number of broadcast frames received Description 0 to 4294967295 1 F9 0 0242 Port 8: Number of multicast frames received 0 to 4294967295 1 F9 0 0244 Port 8: Number of frames with CRC error 0 to 4294967295 1 F9 0 0246 Port 8: Number of oversized frames received 0 to 4294967295 1 F9 0 0248 Port 8: Number of bad fragments received (<64
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 12 of 33) Range Step Format Default 0278 Address Port 9: Number of oversized frames received Description 0 to 4294967295 1 F9 0 027A Port 9: Number of bad fragments received (<64 bytes) 0 to 4294967295 1 F9 0 027C Port 9: Number of jabber frames received 0 to 4294967295 1 F9 0 027E Port 9: Number of collisions occurred 0 to 4294967295 1 F9 0 0280 Port 9: Number of late collisions occurred 0 to
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 13 of 33) Address 18–16 Description Range Step Format Default 02B0 Port 10: Number of collisions occurred 0 to 4294967295 1 F9 0 02B2 Port 10: Number of late collisions occurred 0 to 4294967295 1 F9 0 02B4 Port 10: Number of 64-byte frames received/sent 0 to 4294967295 1 F9 0 02B6 Port 10: Number of 65 to 127 byte frames received/sent 0 to 4294967295 1 F9 0 02B8 Port 10: Number of 128 to 255 by
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 14 of 33) Range Step Format Default 02E8 Address Port 11: Number of 65 to 127 byte frames received/sent Description 0 to 4294967295 1 F9 0 02EA Port 11: Number of 128 to 255 byte frames received/sent 0 to 4294967295 1 F9 0 02EC Port 11: Number of 256 to 511 byte frames received/sent 0 to 4294967295 1 F9 0 02EE Port 11: Number of 512 to 1023 byte frames received/sent 0 to 4294967295 1 F9 0 02F0 P
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 15 of 33) Address 18–18 Range Step Format Default 0320 Port 12: Number of 512 to 1023 byte frames received/sent Description 0 to 4294967295 1 F9 0 0322 Port 12: Number of 1023 to maximum byte frames received/sent 0 to 4294967295 1 F9 0 0324 Port 12: Number of MAC error packets 0 to 4294967295 1 F9 0 0326 Port 12: Number of dropped received packets 0 to 4294967295 1 F9 0 0328 Port 12: Number of
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 16 of 33) Range Step Format Default 0358 Address Port 13: Number of dropped received packets Description 0 to 4294967295 1 F9 0 035A Port 13: Number of multicast frames sent 0 to 4294967295 1 F9 0 035C Port 13: Number of broadcast frames sent 0 to 4294967295 1 F9 0 035E Port 13: Number of <64 byte fragments with good CRC 0 to 4294967295 1 F9 0 0360 Port 14: Number of bytes received 0 to 4294967
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 17 of 33) Address 18–20 Description Range Step Format Default 0390 Port 14: Number of <64 byte fragments with good CRC 0 to 4294967295 1 F9 0 0392 Port 15: Number of bytes received 0 to 4294967295 1 F9 0 0394 Port 15: Number of bytes sent 0 to 4294967295 1 F9 0 0396 Port 15: Number of frames received 0 to 4294967295 1 F9 0 0398 Port 15: Number of frames sent 0 to 4294967295 1 F9 0 039A Po
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 18 of 33) Range Step Format Default 03C8 Address Port 16: Number of frames received Description 0 to 4294967295 1 F9 0 03CA Port 16: Number of frames sent 0 to 4294967295 1 F9 0 03CC Port 16: Total bytes received 0 to 4294967295 1 F9 0 03CE Port 16: Total frames received 0 to 4294967295 1 F9 0 03D0 Port 16: Number of broadcast frames received 0 to 4294967295 1 F9 0 03D2 Port 16: Number of
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 19 of 33) Address 18–22 Range Step Format Default 0400 Port 17: Total frames received Description 0 to 4294967295 1 F9 0 0402 Port 17: Number of broadcast frames received 0 to 4294967295 1 F9 0 0404 Port 17: Number of multicast frames received 0 to 4294967295 1 F9 0 0406 Port 17: Number of frames with CRC error 0 to 4294967295 1 F9 0 0408 Port 17: Number of oversized frames received 0 to 42949
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 20 of 33) Range Step Format Default 0438 Address Port 18: Number of frames with CRC error Description 0 to 4294967295 1 F9 0 043A Port 18: Number of oversized frames received 0 to 4294967295 1 F9 0 043C Port 18: Number of bad fragments received (<64 bytes) 0 to 4294967295 1 F9 0 043E Port 18: Number of jabber frames received 0 to 4294967295 1 F9 0 0440 Port 18: Number of collisions occurred 0 t
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 21 of 33) Address 18–24 Range Step Format Default 0470 Port 19: Number of jabber frames received Description 0 to 4294967295 1 F9 0 0472 Port 19: Number of collisions occurred 0 to 4294967295 1 F9 0 0474 Port 19: Number of late collisions occurred 0 to 4294967295 1 F9 0 0476 Port 19: Number of 64-byte frames received/sent 0 to 4294967295 1 F9 0 0478 Port 19: Number of 65 to 127 byte frames rece
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 22 of 33) Range Step Format Default 04A8 Address Port 20: Number of 64-byte frames received/sent Description 0 to 4294967295 1 F9 0 04AA Port 20: Number of 65 to 127 byte frames received/sent 0 to 4294967295 1 F9 0 04AC Port 20: Number of 128 to 255 byte frames received/sent 0 to 4294967295 1 F9 0 04AE Port 20: Number of 256 to 511 byte frames received/sent 0 to 4294967295 1 F9 0 04B0 Port 20: N
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 23 of 33) Address 18–26 Range Step Format Default 04E0 Port 21: Number of 256 to 511 byte frames received/sent Description 0 to 4294967295 1 F9 0 04E2 Port 21: Number of 512 to 1023 byte frames received/sent 0 to 4294967295 1 F9 0 04E4 Port 21: Number of 1023 to maximum byte frames received/sent 0 to 4294967295 1 F9 0 04E6 Port 21: Number of MAC error packets 0 to 4294967295 1 F9 0 04E8 Port 21
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 24 of 33) Range Step Format Default 0518 Address Port 22: Number of MAC error packets Description 0 to 4294967295 1 F9 0 051A Port 22: Number of dropped received packets 0 to 4294967295 1 F9 0 051C Port 22: Number of multicast frames sent 0 to 4294967295 1 F9 0 051E Port 22: Number of broadcast frames sent 0 to 4294967295 1 F9 0 0520 Port 22: Number of <64 byte fragments with good CRC 0 to 4294
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 25 of 33) Address 18–28 Range Step Format Default 0550 Port 23: Number of broadcast frames sent Description 0 to 4294967295 1 F9 0 0552 Port 23: Number of <64 byte fragments with good CRC 0 to 4294967295 1 F9 0 0554 Port 24: Number of bytes received 0 to 4294967295 1 F9 0 0556 Port 24: Number of bytes sent 0 to 4294967295 1 F9 0 0558 Port 24: Number of frames received 0 to 4294967295 1 F9 0
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 26 of 33) Range Step Format Default 0588 Address Port 25: Number of bytes sent Description 0 to 4294967295 1 F9 0 058A Port 25: Number of frames received 0 to 4294967295 1 F9 0 058C Port 25: Number of frames sent 0 to 4294967295 1 F9 0 058E Port 25: Total bytes received 0 to 4294967295 1 F9 0 0590 Port 25: Total frames received 0 to 4294967295 1 F9 0 0592 Port 25: Number of broadcast frame
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 27 of 33) Address 18–30 Range Step Format Default 05C0 Port 26: Total bytes received Description 0 to 4294967295 1 F9 0 05C2 Port 26: Total frames received 0 to 4294967295 1 F9 0 05C4 Port 26: Number of broadcast frames received 0 to 4294967295 1 F9 0 05C6 Port 26: Number of multicast frames received 0 to 4294967295 1 F9 0 05C8 Port 26: Number of frames with CRC error 0 to 4294967295 1 F9 0
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 28 of 33) Range Step Format Default 05F8 Address Port 27: Number of multicast frames received Description 0 to 4294967295 1 F9 0 05FA Port 27: Number of frames with CRC error 0 to 4294967295 1 F9 0 05FC Port 27: Number of oversized frames received 0 to 4294967295 1 F9 0 05FE Port 27: Number of bad fragments received (<64 bytes) 0 to 4294967295 1 F9 0 0600 Port 27: Number of jabber frames receive
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 29 of 33) Address 18–32 Range Step Format Default 0630 Port 28: Number of bad fragments received (<64 bytes) Description 0 to 4294967295 1 F9 0 0632 Port 28: Number of jabber frames received 0 to 4294967295 1 F9 0 0634 Port 28: Number of collisions occurred 0 to 4294967295 1 F9 0 0636 Port 28: Number of late collisions occurred 0 to 4294967295 1 F9 0 0638 Port 28: Number of 64-byte frames recei
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 30 of 33) Range Step Format Default 0668 Address Port 29: Number of late collisions occurred Description 0 to 4294967295 1 F9 0 066A Port 29: Number of 64-byte frames received/sent 0 to 4294967295 1 F9 0 066C Port 29: Number of 65 to 127 byte frames received/sent 0 to 4294967295 1 F9 0 066E Port 29: Number of 128 to 255 byte frames received/sent 0 to 4294967295 1 F9 0 0670 Port 29: Number of 256
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 31 of 33) Address 18–34 Range Step Format Default 06A0 Port 30: Number of 128 to 255 byte frames received/sent Description 0 to 4294967295 1 F9 0 06A2 Port 30: Number of 256 to 511 byte frames received/sent 0 to 4294967295 1 F9 0 06A4 Port 30: Number of 512 to 1023 byte frames received/sent 0 to 4294967295 1 F9 0 06A6 Port 30: Number of 1023 to maximum byte frames received/sent 0 to 4294967295 1 F
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 32 of 33) Range Step Format Default 06D8 Address Port 31: Number of 1023 to maximum byte frames received/sent Description 0 to 4294967295 1 F9 0 06DA Port 31: Number of MAC error packets 0 to 4294967295 1 F9 0 06DC Port 31: Number of dropped received packets 0 to 4294967295 1 F9 0 06DE Port 31: Number of multicast frames sent 0 to 4294967295 1 F9 0 06E0 Port 31: Number of broadcast frames sent
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 33 of 33) Address 18–36 Range Step Format Default 0710 Port 32: Number of multicast frames sent Description 0 to 4294967295 1 F9 0 0712 Port 32: Number of broadcast frames sent 0 to 4294967295 1 F9 0 0714 Port 32: Number of <64 byte fragments with good CRC 0 to 4294967295 1 F9 0 0716 Serial Number --- --- String Varies MULTILINK ML1200 MANAGED FIELD 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.
MODBUS PROTOCOL 18–38 CHAPTER 18: MODBUS PROTOCOL MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field Switch Appendix A Appendix A A.1 Revision History A.1.1 Change Notes Table A–1: Revision history Part Number 1601-9095-A1 A.1.2 Revision 3.3.0 Release Date 3 June, 2009 Changes to the Manual Table A–2: Updates for Manual Revision A1 Section Description General New Manual A1 General Firmware release 3.3.
APPENDIX A A.2 CHAPTER A: APPENDIX A Warranty A.2.1 GE Multilin Warranty Statement General Electric Multilin Inc. (GE Multilin) 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.
Digital Energy Multilin Multilink ML1200 Managed Field Switch Appendix B: DC Power Input DC Power Input MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL B–1
DC POWER INPUT CHAPTER B: DC POWER INPUT B.1 Specifications for Multilink ML1200 Switches, DC Power at 24 V and –48 V and 125 V DC Power input Each Multilink ML1200 Managed Switch requires DC power input, at either 24VDC, -48VDC or 125VDC nominal. The wide range of DC power input types qualifies this product for use in 24VDC, -48VDC as well as 125VDC applications in different industries.
CHAPTER B: DC POWER INPUT B.2 DC POWER INPUT -48 V DC, 24 V DC and 125 V DC Power, Theory of Operation The -48VDC, 24VDC and 125VDC 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.
DC POWER INPUT B.3 CHAPTER B: DC POWER INPUT Applications for DC Powered Ethernet Switches Multilink ML1200 Switches are easily installed in a variety of applications where -48VDC, 24, or 125VDC 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.
CHAPTER B: DC POWER INPUT B.4 DC POWER INPUT ML1200, -48 V, 24 V, 125 V DC Installation This section describes the proper connection of the -48VDC leads (or 24VDC / 125VDC leads) to the DC power terminal block on the Multilink ML1200 Switch. The DC terminal block on the Multilink ML1200 Managed Switch is located on the left front of the unit and is equipped with four (4) screw-down lead posts.
DC POWER INPUT B.5 CHAPTER B: DC POWER INPUT UL Requirements for DC-powered units 48VDC products shall be installed with a readily accessible disconnect device in the building installation supply circuit to the product. B–6 1. Minimum 18AWG cable for connection to a Centralized DC power source. 2. Minimum 14AWG cable for connection to a earth wiring. 3. Use only with Listed 10 A circuit breaker provided in building installation. 4.
CHAPTER B: DC POWER INPUT B.6 DC POWER INPUT Operation Operation of Multilink ML1200 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 singlesource DC-powered models.
DC POWER INPUT B–8 CHAPTER B: DC POWER INPUT MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL
Digital Energy Multilin Multilink ML1200 Managed Field Switch Appendix C: Internal DC DualSource Power Input Internal DC Dual-Source Power Input Option MULTILINK ML1200 MANAGED FIELD SWITCH – INSTRUCTION MANUAL C–1
INTERNAL DC DUAL-SOURCE POWER INPUT OPTION C.
CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION C.2 INTERNAL DC DUAL-SOURCE POWER INPUT OPTION Multilink ML1200 with -48 V DC, 24 V DC and 125 V DC Dual-Source option The ML1200-Switch models with the internal -48VDC, 12VDC, 24VDC, 125VDC and 250VDC 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.
INTERNAL DC DUAL-SOURCE POWER INPUT OPTION C.3 CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION 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.
CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION C.4 INTERNAL DC DUAL-SOURCE POWER INPUT OPTION Features and Benefits of the Dual-Source Design 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. 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.
INTERNAL DC DUAL-SOURCE POWER INPUT OPTION C.5 CHAPTER C: INTERNAL DC DUAL-SOURCE POWER INPUT OPTION Installation This section describes the proper connection of the -48VDC, 12VDC, 24VDC, 125VDC and 250VDC dual source leads to the power terminal block on the Multilink ML1200 Switch (shown in Figure to the 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.
