GE Consumer & Industrial Multilin MultiLink ML2400 Ethernet Communications Switch Instruction Manual Firmware Revision 3.x Manual P/N: 1601-0220-AB Manual Order Code: GEK-113042K Copyright © 2008 GE Multilin Canada L6E 1B3 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 ORDERING .............................................................................................................................1-2 ORDER CODES ..........................................................
TABLE OF CONTENTS MULTILINK SWITCH SOFTWARE ............................................................................................2-7 REDUNDANT POWER SUPPLY ................................................................................................2-8 ADDITIONAL FEATURES AND BENEFITS ................................................................................2-8 APPLICATIONS ......................................................................................................................
TOC TABLE OF CONTENTS SETTING SERIAL PORT PARAMETERS ....................................................................................5-8 SYSTEM PARAMETERS .............................................................................................................5-8 DATE AND TIME .......................................................................................................................5-9 NETWORK TIME ........................................................................................
TABLE OF CONTENTS CONFIGURING TACACS+ WITH ENERVISTA SECURE WEB MANAGEMENT SOFTWARE .............................................................................................8-6 9: PORT MIRRORING AND SETUP PORT MIRRORING ................................................................................................................9-1 DESCRIPTION ............................................................................................................................
TOC TABLE OF CONTENTS FEATURES AND OPERATION ...................................................................................................12-1 CONFIGURING STP ..............................................................................................................12-3 13: RAPID SPANNING TREE PROTOCOL OVERVIEW ..............................................................................................................................13-1 DESCRIPTION ............................................
TABLE OF CONTENTS CONFIGURING RMON .........................................................................................................16-13 DESCRIPTION ............................................................................................................................16-13 COMMANDS ..............................................................................................................................16-13 17: MISCELLANEOUS COMMANDS ALARM RELAYS .........................................
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 1: Introduction Introduction 1.1 Getting Started 1.1.1 Inspecting the Package and Product Examine the shipping container for obvious damage prior to installing this product; notify the carrier of any damage that you believe occurred during shipment or delivery. Inspect the contents of this package for any signs of damage and ensure that the items listed below are included.
INTRODUCTION 1.2 CHAPTER 1: INTRODUCTION Ordering 1.2.1 Order Codes The following table illustrates the order codes for the MultiLink ML2400 Ethernet Switch. The fiber optic LC ports are limited to a total of 12.
CHAPTER 1: INTRODUCTION 1.3 INTRODUCTION Specifications 1.3.1 Technical Specifications PERFORMANCE Ethernet (10 Mb)..............................................14880 pps Fast Ethernet (100 Mb):................................148,800 pps Gigabit Ethernet (1000 Mb): ......................1488000 pps Switching processing: ..................................Store and forward with IEEE 802.3x full-duplex flow control, non-blocking Data rate: ...........................................................
INTRODUCTION CHAPTER 1: INTRODUCTION FIBER SINGLE-MODE CONNECTORS Fiber port, SC-type:........................................Fiber optic single-mode, 100Base-FX Fiber port, 1000Base-FX:............................GBIC modules LEDS LK:..........................................................................steady ON when media link is operational ACT: .......................................................................ON with receiver port activity FDX/HDX:...........................................
CHAPTER 1: INTRODUCTION 1.3.2 INTRODUCTION Environmental Specifications OPERATING ENVIRONMENT Ambient temperature: .................................–40 to 185°F (–40 to 85°C) for IEC 60068-2-1, IEC 600682-2 for 16 hours Nominal ≤ 50°C Storage temperature:...................................–60 to 210°F (–50 to 100°C) Ambient relative humidity: ........................5% to 95% (non-condensing) Altitude:...............................................................2000 m 1.3.
INTRODUCTION CHAPTER 1: INTRODUCTION Standard Name Standard Number:Date code Severity levels Tested A-rated control power inputs IEEE 1613:2003 Test operation @85% to110% or rated - as per 5.1 and 5.
CHAPTER 1: INTRODUCTION INTRODUCTION IEC:.........................................................................IEC61850 EMC and operating conditions class C for power susbstations CE:..........................................................................EN 50082-1, EN 55022:1998, EN 60950 3rd Edition UL:..........................................................................UL listed/recognized (file E156407), UL 60950-1 1st edition CSA:.............................................................
INTRODUCTION 1.4 CHAPTER 1: INTRODUCTION Firmware Overview 1.4.1 Command Line Firmware Commands typed by the user will be shown in the following color and font. command The MultiLink Switch Software prompt will be shown in bold and fixed-width text, with a # or > character at the end.
CHAPTER 1: INTRODUCTION 1.4.3 INTRODUCTION Before Starting This section explains how to setup the GE MultiLink family of switches using the console port on the switch. Some of the functionality includes setting up the IP address of the switch, securing the switch with a user name and password, setting up VLANs and more. Before you start, it is recommended to acquire the hardware listed below and be ready with the items listed. For initial configuration through the serial/console port: 1.
INTRODUCTION 1.5 CHAPTER 1: INTRODUCTION Command Line Interface Firmware 1.5.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.
CHAPTER 1: INTRODUCTION 1.5.3 INTRODUCTION Console Screen Once the console cable is connected to the PC and the firmware configured, ML2400 legal disclaimers and other text scrolls by on the screen. The line interface prompt appears displaying the switch model number (e.g. ML2400>) 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.
INTRODUCTION CHAPTER 1: INTRODUCTION If the ML2400 is not connected to a network, then proceed to Step 3 below. or use the default IP address. Note Step 1: The ML2400 will scan the network for a DHCP server. If the server responds, the ML2400 will acquire and set the assigned IP address.
CHAPTER 1: INTRODUCTION INTRODUCTION 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). Z Save the settings (without saving, the changes made will be lost). Z Power off the switch (or a firmware reboot as discussed below).
INTRODUCTION CHAPTER 1: INTRODUCTION System System System System Description: 25 Port Modular Ethernet Switch Contact: multilin.tech@ge.com Location: Markham, Ontario ObjectId: 1.3.6.1.4.1.13248.12.7 ML2400# show sysconfig System Name: ML2400 System Contact: multilin.tech@ge.
CHAPTER 1: INTRODUCTION INTRODUCTION To add a user, use the add command as shown below. The user name has to be a unique name. The password is recommended to be at least 8 characters long with a mix of upper case, lower case, numbers and special characters.
INTRODUCTION CHAPTER 1: INTRODUCTION logout terminal ping telnet set walkmib Contextless Commands: ! enable show alarm ? exit whoami clear help ML2400> 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.
CHAPTER 1: INTRODUCTION INTRODUCTION ping set show telnet terminal walkmib whoami ML2400> The following example lists commands starting with a specific string: ML2400> s set show ML2400> In the following example, the key completes the command: ML2400> se password timeout vlan ML2400> set 1.5.10 Exiting To exit from the CLI interface and terminate the console session use the logout command. This command prompts to ensure that the logout was not mistakenly typed.
INTRODUCTION 1.6 CHAPTER 1: INTRODUCTION EnerVista Secure Web Management 1.6.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.
CHAPTER 1: INTRODUCTION INTRODUCTION 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. FIGURE 1–4: Welcome screen 1.6.2 Privilege Levels • Operator privilege users: operator privileges allow views of the current configurations but do not allow changes to the configuration.
INTRODUCTION CHAPTER 1: INTRODUCTION In the following example below, the user peter was added with manager privilege after clicking the add button. After successfully adding a user, the added user is displayed in the list of users as shown below.
CHAPTER 1: INTRODUCTION INTRODUCTION Z To delete a user, click on the delete icon ( )as shown below. 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 ( ).
INTRODUCTION CHAPTER 1: 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.6.4 Modifying the Privilege Level Privilege levels cannot be changed from the EnerVista Secure Web Management (SWM) firmware.
CHAPTER 1: INTRODUCTION 1.6.6 INTRODUCTION Exiting Z To exit or logout, click on the logout button. Z Confirm the logout by selecting OK in the pop-up window.
INTRODUCTION 1.7 CHAPTER 1: INTRODUCTION ML2400 Firmware Updates 1.7.1 Updating MultiLink Firmware This section describes how to upgrade the firmware on a Multilink switch, either locally at the console port or remotely over the network using FTP or TFTP. Depending on the update process (serial/console port or network), ensure the necessary tools listed below are available, tested and working before you begin.
CHAPTER 1: INTRODUCTION INTRODUCTION Refer to Saving Configuration on page 5–19 for details on the xmodem command. Once the upgrade is started, the terminal emulation firmware will ask for the installation file location. Z Indicate the file location to begin the file transfer. Z Make sure the Xmodem protocol is also selected in this file location dialog window. In some operating systems it maybe necessary to select the transfer option. In this case, Z Return to the HyperTerminal window used in step 5.
INTRODUCTION CHAPTER 1: INTRODUCTION Z Select the switch to upgrade. Ensure you have system administration privileges available on the switch. Z Open a EnerVista Secure Web Management software session with the switch by typing in the following URL: https:// If using FTP, save the configuration before proceeding.
CHAPTER 1: INTRODUCTION INTRODUCTION Z Load the new firmware as shown below. As the file is being loaded, the firmware will display the transfer in progress window. Z Reboot the switch when the transfer is complete. After reboot, the firmware is ready for use.
INTRODUCTION 1–28 CHAPTER 1: INTRODUCTION MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 2: Product Description Product Description 2.1 Overview 2.1.1 Introduction to the ML2400 The MultiLink ML2400 Ethernet Switch boosts the performance of large Ethernet LANs, typically serving as a “backbone” switch. It has the flexibility to handle a mix of both fiber and twisted-pair switched ports along with Gigabit backbone port options. Industrystandard IEEE 802.
PRODUCT DESCRIPTION 2.1.2 CHAPTER 2: PRODUCT DESCRIPTION Design Aspects Designed for use in network traffic centers, the MultiLink ML2400 Ethernet Switch is easy to install and use. Addresses of attached nodes are automatically learned, maintained, and aged out, adapting the switching services to network changes. LEDs provide status information on each port. The ML2400 provides high performance plug-and-play hardware operation, 802.
CHAPTER 2: PRODUCT DESCRIPTION 2.2 PRODUCT DESCRIPTION Communications Modules 2.2.1 Four-Port Modules The four-port fiber option for the modular slot comes in three configurations: • A1 module: 4 × 10 Mb – ST mm fiber • A2 module: 4 × 100 Mb – ST mm fiber • A3 module: 4 × 100 Mb – SC mm fiber 754701A2.
PRODUCT DESCRIPTION 2.2.2 CHAPTER 2: PRODUCT DESCRIPTION Six-port Modules The combo six-port modules are combinations of copper and fiber media, available as four 10/100 switched RJ45 copper ports and two 100 Mb switched multi-mode fiber ST or SC ports as shown below.
CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION is, each independently selects a mode and speed to match the device at the other end of the twisted pair cable (see Auto-Negotiation (for Fast Ethernet Copper Ports) on page 4–2 for additional details). 754702A1.CDR FIGURE 2–3: RJ45 10/100 Mb 8-port copper module On this module, there are four LEDs for each port, two in the connector and two separate. The LK (Link) LED indicates “ready for operation” on that port when lit.
PRODUCT DESCRIPTION 2.2.4 CHAPTER 2: PRODUCT DESCRIPTION Gigabit (1000 Mbps) Modules The 1000 Mb Gigabit fiber-port modules on the ML2400 are normally set (factory default) to operate in AUTO mode for best fiber distance and performance. The 1000 Mbps SC fiber-optic module on the Gigabit-SX and Gigabit-LX transceivers are compatible with the IEEE 802.3z Gigabit standards. 754730A1.
CHAPTER 2: PRODUCT DESCRIPTION 2.3 PRODUCT DESCRIPTION Features and Benefits 2.3.1 Packet Prioritization, 802.1p QoS Quality of Service (QoS) means providing consistent predictable data delivery to users from datagram paths that go all across a network. As a LAN device, the ML2400 can do its part to prevent any QoS degradation while it is handling Ethernet traffic through its ports and buffers. The ML2400 switching hardware supports the IEEE 802.
PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION All software information, including new releases and upgrades, can be accessed and download from the GE Multilin website at http://www.GEmultilin.com. 2.3.4 Redundant Power Supply With the redundant power supply, the ML2400 can receive power from either power supply 1 (A) or power supply 2 (B). The switch load is shared if both power supplies are available. The unit will not allow power to flow from a one input to another input (i.e.
CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION The port modules are normally factory installed and tested, but may be changed in the field. • Heavy-duty design for industrial Ethernet and extended temperature operation: Fiber ports take more power than copper ports, but the ML2400 design provides for this with heavy-duty components. The ambient temperature can be up to is 85°C. • NEBS and ETSI tested and certified: The ML2400 has been tested and certified for NEBS and ETSI.
PRODUCT DESCRIPTION 2.4 CHAPTER 2: PRODUCT DESCRIPTION Applications 2.4.1 Description The MultiLink ML2400 Ethernet Switch offers high performance and modularity. It provides the flexibility of 100 Mbps fiber, copper, and Gigabit ports, with industry-standard LAN management software.
CHAPTER 2: PRODUCT DESCRIPTION PRODUCT DESCRIPTION 754731A1.CDR FIGURE 2–5: VLAN application 2.4.3 Network with Multiple Subnets A managed switch is needed to provide an Ethernet backbone for a diversified network with multiple subnets. The backbone consists of high speed LAN segments supported by 100 Mbps full-duplex future-proof fiber media to provide secure long distance LAN connections.
PRODUCT DESCRIPTION CHAPTER 2: PRODUCT DESCRIPTION 754732A1.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 3: Installation Installation 3.1 Preparation 3.1.1 Precautions Before installing the equipment, it is necessary to take the following precautions if the equipment is mounted in an enclosed or multiple rack assembly: 1. Ensure the environmental temperature is less than or equal to 50°C. 2. Maintain adequate air flow for proper and safe operation. 3.
INSTALLATION CHAPTER 3: INSTALLATION Locate an power source within six feet (2 meters) of the intended ML2400 site. The rugged metal case of the will normally protect the switch from accidental damage in a lab or workplace setting. Maintain an open view of the front to visually monitor the status LEDs.
CHAPTER 3: INSTALLATION 3.2 INSTALLATION Connecting Ethernet Media 3.2.1 Description The ML2400 switches are specifically designed to support standard Ethernet media types within a single unit. This is accomplished by using a family of modules that are individually selected and configured. The supported media types with the corresponding IEEE 802.3, 802.3D, 802.3u, 802.3AB and 802.3z standards and connector types are as follows: Table 3–1: Ethernet media IEEE standard 100Base-FX 3.2.
INSTALLATION 3.2.3 CHAPTER 3: INSTALLATION Connecting SC-type Fiber Optics (snap-in) The following procedure applies to installations using modules with SC-type fiber connectors. These include the A3, A8, A9, and G2 modules. When connecting fiber media to SC connectors, simply snap on the two square male connectors into the SC female jacks of the module until it clicks and secures. 3.2.
CHAPTER 3: INSTALLATION INSTALLATION The following procedure describes how to connect a 1000Base-T twisted pair segment to the RJ45 port. The procedure is the same for both unshielded and shielded twisted pair cables. 1000Base-T connections require that all four pairs or wires be connected: Z Insert either end of the cable with an RJ45 plug into the RJ45 connector on the module. Although the connector is shielded, either unshielded or shielded cables may be used.
INSTALLATION 3.3 CHAPTER 3: INSTALLATION Mechanical Installation 3.3.1 Table-top or Shelf Mounting The MultiLink ML2400-AC Ethernet Switch can be mounted on a table-top or any suitable horizontal surface. It has four rubber feet to provide stability without scratching finished surfaces. 3.3.2 Rack Mounting Installation of a MultiLink ML2400 Ethernet Switch in a 19-inch rack is a simple procedure. The units are 1 U (1.70") high.
CHAPTER 3: INSTALLATION INSTALLATION 754734A1.CDR FIGURE 3–2: Mountings for ML2400 units rack-mounted in a frame The bracket mounting holes in the sides of the ML2400 permits it to be mounted in various ways. The same holes fit all three types (19", ETSI, 23") of brackets. The mounting for the 23" is illustrated above. The brackets may be attached flush with the front, or attached in the center for a set-back mounting which may reduce cabling torque.
INSTALLATION 3.4 CHAPTER 3: INSTALLATION Electrical Installation 3.4.1 Powering the ML2400 Units with the AC power supply option can be connected directly to 110/240 V AC with the supplied power cord. The standard high voltage (120/125 V AC/DC) or low-voltage (48 V DC) terminal block on the ML2400 is located on the rear of the unit and is equipped with three (3) screw-down lead posts.
CHAPTER 3: INSTALLATION 3.4.3 INSTALLATION 3. Use only with listed 10 A circuit breaker provided in building installation. 4. “Complies with FDA radiation performance standards, 21 CFR sub-chapter J” or equivalent. 5. Fastening torque of the lugs on the terminal block: 9 inch-pound maximum. 6. For AC and HI powered units, use only with listed 20A circuit breaker provided in building installation. Circuit breaker shall be provided in end system or building as disconnect device. 7.
INSTALLATION 3.4.4 CHAPTER 3: INSTALLATION Dielectric Strength (hi-pot) Testing The shorting link between the and safety ground must be removed prior to the dielectric strength test to protect the transient suppression circuitry of the power supply.
CHAPTER 3: INSTALLATION 3.5 INSTALLATION Connecting a Management Console Terminal to the ML2400 3.5.1 Description Use a DB-9 null-modem cable or a DB-9 to USB null-modem cable to connect the ML2400 console port (the RS232 port) to the a PC. Note Console cables may be purchased as a separate items. They are not included with the unit. 754736A1.CDR FIGURE 3–5: ML2400 console port The pin assignment for the console port are indicated in the following table.
INSTALLATION 3–12 CHAPTER 3: INSTALLATION MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 4: Operation Operation 4.1 Functionality 4.1.1 Switching Functionality The MultiLink ML2400 provides switched connectivity at Ethernet wire-speed. The ML2400 supports10/100 Mbps for copper media and 10 or 100 Mb separate traffic domains for fiber ports to maximize bandwidth utilization and network performance.
OPERATION 4.1.3 CHAPTER 4: OPERATION Address Learning All ML2400 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 ML2400 automatically keeps up with node locations. An address-aging algorithm causes least-used addresses to fall out in favor of frequentlyused addresses. To reset the address buffer, cycle power down-and-up. 4.1.
CHAPTER 4: OPERATION OPERATION • 100Mb half-duplex • 10 Mb full-duplex • 10 Mb half-duplex The auto-negotiation logic will attempt to operate in descending order and will normally arrive at the highest order mode that both devices can support at that time. (Since 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 Note 4–4 CHAPTER 4: OPERATION In half-duplex mode, the ML2400 implements a back-pressure algorithm on 10/100 Mb ports for flow control. That is, the switch prevents frames from entering the device by forcing a collision indication on the half-duplex ports that are receiving. This temporary “collision” delay allows the available buffer space to improve as the switch catches up with the traffic flow.
CHAPTER 4: OPERATION 4.1.8 OPERATION Power Budget Calculations with Fiber Media Receiver sensitivity and transmitter power are the parameters necessary to compute the power budget. To calculate the power budget of different fiber media installations using MultiLink products, the following equations should be used: OPB = P t ( min ) – P R ( min ) (EQ 4.
OPERATION CHAPTER 4: OPERATION The use of either multi-mode or single-mode fiber to operate at 100 Mbps speed over long distances (i.e., in excess of 400 m) can be achieved only if the following are applied: 4–6 1. The 100 Mb fiber segment must operate in full-duplex (FDX) mode (i.e. the fullduplex (factory default). 2.
CHAPTER 4: OPERATION 4.2 OPERATION Troubleshooting 4.2.1 Overview All MultiLink Ethernet products are designed to provide reliability and consistently high performance in all network environments. The installation of a ML2400 is a straightforward procedure (see chapter 2 for details) Should problems develop during installation or operation, this section is intended to help locate, identify and correct these types of problems. Please follow the suggestions listed below prior to contacting your supplier.
OPERATION 4–8 CHAPTER 4: OPERATION MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 5: IP Addressing IP Addressing 5.1 IP Address and System Information 5.1.1 Overview It is assumed that the user has familiarity with IP addresses, classes of IP addresses and related netmask schemas (for example, class A, B, and C addressing). Without an IP address, the switch operates as a standalone Layer 2 switch.
IP ADDRESSING CHAPTER 5: IP ADDRESSING To verify the IP address using the EnerVista Secure Web Management software, Z Select the Administration > System menu item to view. 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 ML2400. The ML2400 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 ML2400.
IP ADDRESSING CHAPTER 5: IP ADDRESSING Inbound Telnet Enabled: Yes Outbound Telnet Enabled: Yes Web Console Enabled: Yes SNMP Enabled: Yes Terminal Type: VT100 Screen Refresh Interval (sec): 3 Baud Rate: 38400 Flow Control: None Session Inactivity Time (min): 10 ML2400# Users can telnet to a remote host from the MultiLink family of switches using the following syntax. telnet [port=] The default port for telnet is 23.
CHAPTER 5: IP ADDRESSING IP ADDRESSING 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 ML2400# kill session id=3 Session Terminated ML2400# In the above example, the user with username “peter” is given telnet access. Then multiple users telnet into the switch. This is shown using the show session command. The user operator session is then terminated using the kill session command.
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 The following example lists system parameters using the show sysconfig command. Most parameters here can be changed. ML2400# show sysconfig System Name: ML2400 System Contact: multilin.tech@ge.
IP ADDRESSING CHAPTER 5: IP ADDRESSING set time hour=<0-23> min=<0-59> sec=<0-59> [zone=GMT[+/-]hh:mm] To set the time to be 08:10 am in the -5 hours from GMT (Eastern Standard Time) and to set the date as 11 May 2005, the following sequence of commands are used.
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 ML2400# sntp ML2400(sntp)## setsntp server=3.94.210.5 timeout=3 retry=3 SNTP server is added to SNTP server database ML2400(sntp)## sync hour=5 ML2400(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 5.4 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.
IP ADDRESSING CHAPTER 5: 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.
CHAPTER 5: IP ADDRESSING IP ADDRESSING [SYSTEM] ***Edit below this line only*** system_name=ML2400 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.
IP ADDRESSING 5.4.3 CHAPTER 5: 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.
CHAPTER 5: IP ADDRESSING 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— ...
IP ADDRESSING CHAPTER 5: IP ADDRESSING ML2400# show config module=snmp [HARDWARE] type= ML2400 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=.
CHAPTER 5: IP ADDRESSING IP ADDRESSING ML2400# show config module=snmp,system [HARDWARE] type= ML2400 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.
IP ADDRESSING CHAPTER 5: IP ADDRESSING Additional capabilities have been added to save and load configurations.
CHAPTER 5: IP ADDRESSING 5.4.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.
IP ADDRESSING CHAPTER 5: 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.
CHAPTER 5: IP ADDRESSING 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.
IP ADDRESSING 5.4.7 CHAPTER 5: IP ADDRESSING Host Names Instead of typing in IP addresses of commonly reached hosts, the ML2400 allows hosts to be created with the necessary host names, IP addresses, user names, and passwords. Z Use the Configuration > Access > Host menu to create host entries as shown below. 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. ML2400# 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.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 6: Access Considerations Access Considerations 6.1 Securing Access 6.1.1 Description This section explains how the access to the MultiLink family of switches 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, Fast Ethernet, or Gigabit 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.
CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS Example 6-1 views port security settings on a switch. Learning is enabled on port 9. This port has 6 stations connected to it with the MAC addresses as shown. Other ports have learning disabled and the MAC addresses are not configured on those ports. Example 6-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.
ACCESS CONSIDERATIONS CHAPTER 6: ACCESS CONSIDERATIONS 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 (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=11,15 command). Z Disable access to the network for unauthorized devices (Use action port=11 depending on whether the port should be disabled or the packed dropped. Follow that with a show port-security command to verify the setting).
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.2 Security Logs All events occurring on the MultiLink family of switches are logged. The events can be informational (e.g. login, STP synchronization etc.
CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS unexpected behavior). The specific types of logs can be viewed and cleared. The show log command displays the log information and the clear log command clears the log entries. The syntax for these commands is shown below: show log [1..5|informational|debug|fatal |critical|activity] clear log [informational|debug|activity |critical|fatal] The set logsize command set the number of lines to be collected in the log before the oldest record is re-written.
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 ML2400 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 1. The port can be specified to create a log entry or send a trap, do both or do nothing. This is done through the Signal Status drop down menu. 2. The port can be specified to drop the connection, disable the port or do nothing. This is indicated by the Action Status drop down menu. 3. The port can be put in the learn mode or the learning can be disabled. This is indicated by the Learn Status drop down menu.
ACCESS CONSIDERATIONS 6.3.2 CHAPTER 6: ACCESS CONSIDERATIONS Logs All events occurring on the Managed MultiLink 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.
CHAPTER 6: ACCESS CONSIDERATIONS ACCESS CONSIDERATIONS • F (fatal, severity level 5) indicates that a service has behaved unexpectedly. 6.3.3 Authorized Managers Just as port security allows and disallows specific MAC addresses from accessing a network, the EnerVista Secure Web Management software can allow or block specific IP addresses or a range of IP addresses to access the switch. Z Access this functionality via the Configuration > Access > IP Access menu item.
ACCESS CONSIDERATIONS 6–16 CHAPTER 6: ACCESS CONSIDERATIONS MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 7: Access Using RADIUS Access Using RADIUS 7.1 Introduction to 802.1x 7.1.1 Description The TACACS+ protocol is the latest generation of TACACS. TACACS is a simple UDP (User Datagram Protocol) based access control protocol originally developed by BBN for the MILNET (Military Network). Later the enhancements were called TACACS+. TACACS+ is a TCP (Transmission Control Protocol) based access control protocol.
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. EAPOL EAP over RADIUS 802.
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 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) ML2400(auth)## backend port=2 supptimeout=45 servertimeout=60 maxreq=5 Successfully set backend server authentication parameter(s) ML2400(auth)## show-port backend Supp Timeout Server Timeout Max Request (sec.) (sec.
ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS Setting port control parameters (continued) ML2400(auth)## reauth port=1 status=enable period=300 Successfully set re-authentication parameter(s) ML2400(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 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 ( ). 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.
CHAPTER 7: ACCESS USING RADIUS ACCESS USING RADIUS Z Select the Configuration > Radius > Port > Access menu item. The Quiet Period column represents the time, in seconds, the supplicant is held after an authentication failure before the authenticator retries the supplicant for connection. The value ranges from 0 to 65535 seconds, with a default of 60. The Max Reauth column shows the permitted reauthentication attempts before the port becomes unauthorized.
ACCESS USING RADIUS CHAPTER 7: ACCESS USING RADIUS The Max Request column represents the maximum times the authenticator retransmits an EAP request packet to the supplicant before it times out. Values are integers ranging from 1 to 10, with a default of 2. The port authentication characteristics define how the authenticator (ML2400 switch) does the re-authentication with the supplicant or PC. These are defined through the Configuration > Radius > Port > Access > Reauth menu item.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 8: Access using TACACS+ Access using TACACS+ 8.1 Introduction to TACACS+ 8.1.1 Overview The TACACS+ protocol (short for Terminal Access Controller Access Control System) provides access control for routers, network access servers and other networked computing devices via one or more centralized servers. TACACS+ provides separate authentication, authorization and accounting services.
ACCESS USING TACACS+ 8.1.2 CHAPTER 8: ACCESS USING TACACS+ TACACS+ Flow TACACS works in conjunction with the local user list on the ML2400 software (operating system). Please refer to User Management on page 1–14 for adding users on the MultiLink Switch Software. 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+: ML2400# show tacplus servers ID TACACS+ Server Port Encrypt Key ======================================= 1 10.21.1.170 49 Enabled secret 2 ----3 ----4 ----5 ----- ML2400# user ML2400(user)## show tacplus status TACACS+ Status: Disabled ML2400(user)## tacplus enable TACACS+ Tunneling is enabled. ML2400(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. After the configuration is completed, Z Save the settings.
CHAPTER 8: ACCESS USING TACACS+ ACCESS USING TACACS+ .
ACCESS USING TACACS+ 8–8 CHAPTER 8: ACCESS USING TACACS+ MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications 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 GE MultiLink 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 GE MultiLink family of switches 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 11 and 12 are given specific names. Ports 9 and 13 are active, as shown by the link status. Port 13 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 PORT MIRRORING AND SETUP To change the port speed on a transceiver port, it is required to reboot the switch. Note 9.3.2 Flow Control The flow setting is disabled by default. In this case, the port will not generate flow control packets and drops received flow control packets. If the flow setting is enabled, the port uses 802.3x Link Layer Flow Control, generates flow control packets, and processes received flow control packets.
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP Example 9-2: Back pressure and flow control ML2400# device ML2400(device)## show flowcontrol XOnLimit : 4 XOffLimit : 6 ML2400(device)## flowcontrol xonlimit=10 xofflimit=15 XOn Limit set successfully XOff Limit set successfully ML2400(device)## show flowcontrol XOnLimit : 10 XOffLimit : 15 ML2400(device)## show backpressure Rx Buffer Threshold : 28 (continued on next page) 9–6 MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION
CHAPTER 9: PORT MIRRORING AND SETUP PORT MIRRORING AND SETUP Back pressure and flow control (continued) ML2400(device)## backpressure rxthreshold=30 Rx Buffer Threshold set successfully ML2400(device)## show backpressure Rx Buffer Threshold : 30 ML2400(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 ----
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP Back pressure and flow control (continued) ML2400(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 ------------------------------------------------------------------------------9 B1 E H 10Tx UP 10 No E 1 10 B2 E H 10Tx DOWN 10 No E 1 11 JohnDoe E
CHAPTER 9: PORT MIRRORING AND SETUP 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.
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP Example 9-3: Preventing broadcast storms ML2400# device ML2400(device)## show broadcast-protect ====================================================================== PORT | STATUS | THRESHOLD (frms/sec) | CURR RATE (frms/sec) | ACTIVE ====================================================================== 9 Disabled 19531 0 NO 10 Disabled 19531 0 NO 11 Disabled 19531 0 NO 12 Disabled 19531 0 NO 13 Disabled 19531 0 NO 14 Disabled 19531 0 NO 15 Di
CHAPTER 9: PORT MIRRORING AND SETUP 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 enabled by default on 10 MB Fiber Optic ports, and disabled by default on 100 MB Fiber Optic ports.
PORT MIRRORING AND SETUP 9.4 CHAPTER 9: 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.
CHAPTER 9: PORT MIRRORING AND SETUP 9.4.2 PORT MIRRORING AND SETUP 2. Both the ports (monitored port and mirrored port) have to belong to the same VLAN. 3. The mirrored port shows both incoming as well as outgoing traffic. Port Setup With the ML2400, the specific characteristics of each port can be individually programmed. 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.
PORT MIRRORING AND SETUP CHAPTER 9: PORT MIRRORING AND SETUP • Auto-Neg sets auto negotiation for 100 Mbps and Gigabit copper ports. There is no no auto negotiation for fiber ports as their speeds are fixed. • The Port Speed sets the speed to be 10 or 100 Mbps. This settings works only with 10/100 ports; it is ignored for 10 Mbps ports. • The Duplex setting selects full duplex or half duplex capabilities for 10/100 Mbps ports.
CHAPTER 9: PORT MIRRORING AND SETUP 9.4.3 PORT MIRRORING AND SETUP Broadcast Storms One of the best features of the GE MultiLink 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 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.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 10: VLAN VLAN 10.1 VLAN Description 10.1.1 Overview Short for virtual LAN (VLAN), a VLAN creates separate collision domains or network segments that can span multiple MultiLink switches. 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 A group of network users (ports) assigned to a VLAN form a broadcast domain. Packets are forwarded only between ports that are designated for the same VLAN. Cross-domain broadcast traffic in the switch is eliminated and bandwidth is saved by not allowing packets to flood out on all ports. For many reasons a port may be configured to belong to multiple VLANs. As shown below, ports can belong to multiple VLANs.
CHAPTER 10: VLAN VLAN 10.1.2 Tag VLAN vs. Port VLAN What is the difference between tag and port VLAN? In a nutshell - port VLAN sets a specific port or group of ports to belong to a VLAN. Port VLANs do not look for VLAN identifier (VID) information nor does it manipulate the VID information. It thus works “transparently” and propagates the VLAN information along. In the tag VLAN, an identifier called the VLAN identifier (VID) is either inserted or manipulated.
VLAN CHAPTER 10: VLAN 10.2 Configuring Port VLANs through the Command Line Interface 10.2.1 Description Port VLANs are rarely used 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.
CHAPTER 10: VLAN VLAN 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 switch. ML2400# vlan type=port ML2400(port-vlan)## add id=2 name=test port=1-10 ML2400(port-vlan)## start vlan=all ML2400(port-vlan)## save Saving current configuration...
VLAN CHAPTER 10: VLAN Example 10-1: Adding three VLANs ML2400# set vlan type=port VLAN set to Port-based. ML2400# vlan type=port ML2400(port-vlan)## add id=10 name=engineering port=14 Vlan added successfully with Vlan id : 10 Vlan name : engineering Ports : 14 ML2400(port-vlan)## add id=20 name=engineering port=14 ERROR - Duplicate Vlan name ML2400(port-vlan)## add id=20 name=sales port=14 Each VLAN requires a unique name.
CHAPTER 10: VLAN VLAN Adding three VLANs (continued) ML2400(port-vlan)## show vlan type=port VLAN ID Name Status : 1 : Default VLAN : Active The added VLANs are not yet active. Each individual VLAN can be activated or all VLANs can be activated.
VLAN CHAPTER 10: VLAN Adding three VLANs (continued) VLAN ID : 10 Name : engineering Status : Active ======================== PORT | STATUS ======================== 14 | DOWN The pending VLAN is now active.
CHAPTER 10: VLAN VLAN 10.3 Configuring Port VLANs with EnerVista Secure Web Management Software 10.3.1 Description Port VLANs are rarely used 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. As discussed above, ports 9, 10, 11, 12, 13, 15, 16 still belong to default VLAN. We will now add another VLAN with VID=40 and VLAN name = Support.
CHAPTER 10: VLAN VLAN Z Add the ports. Z Define the VLAN. Z Click OK. . 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.. A specific VLAN can be activated or all VLANs can be activated (or disabled). Z Click OK to activate VLAN.
VLAN CHAPTER 10: VLAN . After activation, note that ports 9 to 13 belong to the new VLAN. Their membership in the default VLAN has been eliminated. Note 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. The ports can be added to VLAN 1 by using the edit button on VLAN 1 and assigning the ports to VLAN 1.
CHAPTER 10: VLAN 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. Note For versions 1.6.1 and below, the use of tag VLANs needed the set-ingress and setegress commands to set the flow of incoming and outgoing traffic. These commands are defunct as of MultiLink Switch Software version 1.6.1.
VLAN CHAPTER 10: VLAN To move Management Control on any VLAN: add id= [name=] port= [Forbid=][] To enable or disable Management Control on any VLAN: edit id=[name=][port=[] 10.4.3 Example In the following example, we start with Port VLAN and convert to TAG VLAN.
CHAPTER 10: VLAN VLAN Example 10-2: Converting Port VLAN to Tag VLAN ML2400# vlan type=port ML2400(port-vlan)## show vlan type=port VLAN ID Name Status : 1 : Default VLAN : Active ======================== PORT | STATUS ======================== 9 | UP 10 | DOWN 11 | DOWN 12 | DOWN 13 | UP 14 | DOWN 15 | DOWN 16 | DOWN VLAN ID Name Status : 10 : engineering : Active ======================== PORT | STATUS ======================== 14 | DOWN VLAN ID Name Status : 20 : sales : Active =====================
VLAN CHAPTER 10: VLAN Converting Port VLAN to Tag VLAN (continued) ML2400# show vlan type=tag VLAN ID Name Status : 1 : Default VLAN : Active ============================== PORT | MODE | STATUS ============================== 9 | UNTAGGED | UP 10 | UNTAGGED | DOWN 11 | UNTAGGED | DOWN 12 | UNTAGGED | DOWN 13 | UNTAGGED | UP 14 | UNTAGGED | DOWN 15 | UNTAGGED | DOWN 16 | UNTAGGED | DOWN Note that ports 14 to 16 are “DOWN” - the VLAN configuration is preferably done before devices are plugged in to avoid
CHAPTER 10: VLAN VLAN Converting Port VLAN to Tag VLAN (continued) ML2400(tag-vlan)## show vlan type=tag VLAN ID Name Status : 1 : Default VLAN : Active ============================== PORT | MODE | STATUS ============================== 9 | UNTAGGED | UP 10 | UNTAGGED | DOWN 11 | UNTAGGED | DOWN 12 | UNTAGGED | DOWN 13 | UNTAGGED | UP 14 | UNTAGGED | DOWN 15 | UNTAGGED | DOWN 16 | UNTAGGED | DOWN VLAN ID Name Status : 10 : engineering : Pending ============================== PORT | MODE | STATUS ======
VLAN CHAPTER 10: VLAN Converting Port VLAN to Tag VLAN (continued) ML2400(tag-vlan)## set-port port=14-16 filter status=enable WARNING: PVID does not match the port(15)'s VLAN ID(s). If you are using telnet session on this port,setting ingress might stop the session. Do you want to continue? ['Y' or 'N'] Y WARNING: PVID does not match the port(14)'s VLAN ID(s). If you are using telnet session on this port, setting ingress might stop the session.
CHAPTER 10: VLAN VLAN Converting Port VLAN to Tag VLAN (continued) ML2400(tag-vlan)## set-port port=14-16 tagging id=10 status=tagged Port tagging enabled ML2400(tag-vlan)## set-port port=14-16 tagging id=20 status=tagged Port tagging enabled ML2400(tag-vlan)## set-port port=14-16 tagging id=30 status=tagged Port tagging enabled ML2400(tag-vlan)## show vlan type=tag VLAN ID Name Status : 1 : Default VLAN : Active ============================== PORT | MODE | STATUS ============================== 9 | U
VLAN CHAPTER 10: 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 MultiLink ML2400 Ethernet Switch, the port VLAN type is set to none. To use Tag VLANs, first enable Tag VLANs.
CHAPTER 10: VLAN VLAN . Z Now add the necessary VLANs. In the example below, add the VLANs in the following manner • VLAN 1, All ports - default VLAN • VLAN 10, Engineering VLAN - ports 11, 12, 13 • VLAN 20, Support VLAN - ports 13, 14, 15 (note that port 13 belongs to VLAN 10, 20) • VLAN 30, Marketing VLAN -ports 15, 16 (note that port 15 belongs to VLAN 20, 30) Z After adding the ports and defining the VLAN, click OK.
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 >. Tag-Based > Settings menu and specify the action. In the example below, we will take port 11 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.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications 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 family of switches.
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 ML2400# gvrp ML2400(gvrp)# show gvrp GVRP Status : Enabled ML2400(gvrp)## gvrp disable GVRP is now disabled ML2400(gvrp)## gvrp enable GVRP enabled ML2400(gvrp)## show-vlan ================================================= VLAN ID | NAME | VLAN | STATUS ================================================= 1 | Default VLAN | Static | Active 2 | Blue | Static | Active 10 | dyn10 | Dynamic | Active ML2400(gvr
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 ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications 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).
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 ML2400(stp)## show stp config STP CONFIGURATION ----------------Spanning Tree Enabled(Global) Spanning Tree Enabled(Ports) Protocol Bridge ID Bridge Priority Bridge Forward Delay Bridge Hello Time Bridge Max Age Root Port Root Path Cost Designated Root Designated Root Priority Root Bridge Forward Delay Root Bridge Hello Time Root Bridge Max Age : : : : : : : : : : : : : : : NO YES, 9,10,11,12,1
CHAPTER 12: SPANNING TREE PROTOCOL (STP) SPANNING TREE PROTOCOL (STP) Configuring STP parameters (continued) ML2400(stp)## show stp config STP CONFIGURATION ----------------Spanning Tree Enabled(Global) Spanning Tree Enabled(Ports) Protocol Bridge ID Bridge Priority Bridge Forward Delay Bridge Hello Time Bridge Max Age Root Port Root Path Cost Designated Root Designated Root Priority Root Bridge Forward Delay Root Bridge Hello Time Root Bridge Max Age : : : : : : : : : : : : : : : YES YES, 9,10,11,12,13
SPANNING TREE PROTOCOL (STP) CHAPTER 12: SPANNING TREE PROTOCOL (STP) Configuring STP parameters (continued) RSTP CONFIGURATION ----------------Rapid STP/STP Enabled(Global) : NO ML2400(stp)## priority port=13 value=20 Successfully set the priority for port 13 ML2400(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) ML2400(stp)## port port=9 status=enable Successfully set the STP status for port 9 ML2400(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) ML2400(stp)## show stp config STP CONFIGURATION ----------------Spanning Tree Enabled(Global) Spanning Tree Enabled(Ports) Protocol Bridge ID Bridge Priority Bridge Forward Delay Bridge Hello Time Bridge Max Age Root Port Root Path Cost Designated Root Designated Root Priority Root Bridge Forward Delay Root Bridge Hello Time Root Bridge Max Age : : : : : : : : : : : : : : : YES YES, 9,10,11,12,13
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications 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.
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 Example 13-1: Enabling RSTP and reviewing the RSTP variables ML2400# rstp ML2400(rstp)## show stp config RSTP CONFIGURATION ----------------Rapid STP/STP Enabled(Global) : NO ML2400(rstp)## rstp enable Successfully set the RSTP status ML2400(rstp)## show active-stp Current Active Mode: RSTP. RSTP is Enabled.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL The variables listed by the show stp ports command are: • Port#: Indicates the port number. The value ranges from 1 to the maximum number of ports in the switch. • Type: Indicates the type of port. TP indicates twisted pair. • Priority: STP uses this to determine which ports are used for forwarding. Lower numbers indicate higher priority. The values range from 0 to 255, with a default of 128.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL Example 13-3: RSTP information from a network with multiple switches ML2400(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 The status parameter enables or disables a port from participating in RSTP discovery. Its best to only allow trunk ports to participate in RSTP; end stations need not participate in the RSTP process. The timers command changes the STP forward delay, hello timer and aging timer values.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL Example 13-4: Configuring RSTP ML2400# rstp ML2400(rstp)## show stp config Check the status of STP or RSTP. These commands show if STP or RSTP is enabled. RSTP CONFIGURATION -----------------Rapid STP/STP Enabled(Global) : NO ML2400(rstp)## show active-stp Current Active Mode: RSTP. RSTP is Disabled. ML2400(rstp)## rstp enable Successfully set the RSTP status ML2400(rstp)## show active-stp Current Active Mode: RSTP.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL Configuring RSTP (continued) ML2400(rstp)## forceversion stp ML2400(rstp)## show-forceversion Force Version : Force to STP only ML2400(rstp)## show stp config RSTP CONFIGURATION ----------------Rapid STP/STP Enabled(Global) RSTP/STP Enabled Ports Protocol Bridge ID Bridge Priority Bridge Forward Delay Bridge Hello Time Bridge Max Age Root Port Root Path Cost Designated Root Designated Root Priority Root Bridge Forward Delay Root Bridge
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL Configuring RSTP (continued) ML2400(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) ML2400(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 13.2.2 Smart RSTP (Ring-Only Mode) through the Command Line Interface A special case of a mesh structure is a ring. In many networks, network managers prefer to create a ring structure for redundancy and simplicity of the topology. In a ring structure: 1. All switches in the network are GE Multilin switches. 2. RSTP is enabled on all the switches. 3. The topology is a ring. 4.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL The sequence of commands for enabling ring-only mode is shown in the following example: Example 13-5: Configuring smart RSTP, ring-only mode ML2400# rstp ML2400(rstp)##rstp enable Successfully set the RSTP status ML2400(rstp)##romode show RO-MODE status : Disabled RO-MODE set on ports : NONE ML2400(rstp)##romode add port=1,2 Added Ports: 1,2 ML2400(rstp)##romode enable RSTP Ring Only Mode Enabled.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL 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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL 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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL 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.
RAPID SPANNING TREE PROTOCOL CHAPTER 13: RAPID SPANNING TREE PROTOCOL Z Click the Edit button to configure RSTP. 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.
CHAPTER 13: RAPID SPANNING TREE PROTOCOL RAPID SPANNING TREE PROTOCOL Z Click the Edit button to configure RO Mode. Z Select the desired ports as shown below, then click OK to exit. Note 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 MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL icon.
RAPID SPANNING TREE PROTOCOL 13–24 CHAPTER 13: RAPID SPANNING TREE PROTOCOL MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 14: Quality of Service Quality of Service 14.1 QoS Overview 14.1.1 Description Quality of Service (QoS) refers to the capability of a network to provide different priorities to different types of traffic. Not all traffic in the network has the same priority.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE To make the preemptive queuing possible, most switches implement at least two queue buffers. The MultiLink family of switches 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 MultiLink switches support 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) ML2400(qos)## show qos ============================== PORT | QOS | STATUS ============================== 9 | None | UP 10 | Port | DOWN 11 | Tag | DOWN 12 | None | DOWN 13 | None | UP 14 | None | DOWN 15 | None | DOWN 16 | None | DOWN ML2400(qos)## show qos type=tag ============================== PORT | QOS | STATUS ============================== 9 | | UP 10 | | DOWN 11 | 6 | DOWN 12 | | DOWN 13 | | UP 14 | | DOWN 15 | | DOWN 1
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE Configuring QoS (continued) ML2400(qos)## show qos ============================== PORT | QOS | STATUS ============================== 9 | None | UP 10 | Port | DOWN 11 | Tag | DOWN 12 | Tag | DOWN 13 | None | UP 14 | None | DOWN 15 | None | DOWN 16 | None | DOWN ML2400(qos)## 14–8 MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE 14.3 Configuring QoS with EnerVista Secure Web Management Software 14.3.1 Description To access QoS settings, Z Select the Configuration > QoS menu items. Z Select the Port and the type of QoS/ToS settings. The following window illustrates the setting of port 14 for portbased QoS with a high priority. Note the sections on Tag and TOS are ignored for Port settings.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE After the port QoS settings are completed, the changes are reflected on the QoS menu screen. The port 14 QoS settings indicate high priority set. Next, a tag-based QoS is enabled on port 17. Note that only the menu area for the tag setting is relevant.
CHAPTER 14: QUALITY OF SERVICE QUALITY OF SERVICE After the Tag QoS settings are completed, the changes are reflected on the QoS menu screen. In the following window, a ToS is enabled on Port 19. As before, only the ToS level settings are relevant.
QUALITY OF SERVICE CHAPTER 14: QUALITY OF SERVICE Note that the different settings are clear from the window below. Port 14 has port-based QoS, port 15 has tag-based QoS, and port 16 is using ToS. Z After all changes are made, save the changes using the save icon ( ).
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 15: IGMP IGMP 15.1 Overview 15.1.1 Description Internet Group Management Protocol (IGMP) is defined in RFC 1112 as the standard for IP multicasting in the Internet. It is used to establish host memberships in particular multicast groups on a single network.
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. 754727A1.CDR 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.) 754728A1.CDR 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: ML2400(igmp)## show-group GroupIp PortNo Timer LeavePending ---------------------------------------224.1.0.1 9 155 0 224.0.1.40 9 155 0 ML2400(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 ML2400(igmp)## set-port port=10-12 mode=forward Port mode is set. ML2400(igmp)## show-port --------------------Port | Mode --------------------09 | Auto 10 | Forwarding 11 | Forwarding 12 | Forwarding 13 | Auto 14 | Auto 15 | Auto 16 | Auto ML2400(igmp)## show-router RouterIp PortNo Timer --------------------------------10.21.1.
CHAPTER 15: IGMP IGMP Configuring IGMP (continued) ML2400(igmp)## set-leave enable IGMP immediate leave status is enabled ML2400(igmp)## show igmp IGMP State ImmediateLeave Querier Querier Interval Querier Response Interval Multicasting Unknown Streams : : : : : : Enabled Enabled Enabled 125 10 Enabled ML2400(igmp)## set-leave disable IGMP immediate leave status is disabled ML2400(igmp)## show igmp IGMP State ImmediateLeave Querier Querier Interval Querier Response Interval Multicasting Unknown Strea
IGMP CHAPTER 15: IGMP Configuring IGMP (continued) ML2400(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 ML2400(igmp)## mcast disable MCAST is disabled ML2400(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. Z Click on the Edit button to edit the IGMP parameters. This screen also enables and disables IGMP.
IGMP 15–12 CHAPTER 15: IGMP MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 16: SNMP SNMP 16.1 Overview 16.1.1 Description SImple Network Management Protocol (SNMP) enables management of the network. There are many software packages which provide a graphical interface and a graphical view of the network and its devices. These graphical interface and view would not be possible without SNMP. SNMP is thus the building block for network management. 16.1.
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 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.
CHAPTER 16: SNMP 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.
SNMP CHAPTER 16: SNMP Example 16-1: Configuring SNMP ML2400# set snmp type=v1 SNMP version support is set to "v1" ML2400# 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 ----------------------- ML2400# set snmp type=all SNMP version support is set to "v1, v2c, v3
CHAPTER 16: SNMP SNMP Configuring SNMP (continued) ML2400(snmpv3)## trap add id=1 type=v1 host=3.94.200.107 Entry is added successfully ML2400(snmpv3)## show-trap ID Trap Type Host IP Community Port ================================================ 1 v1 3.94.200.107 --2 ----3 ----4 ----5 ----- ML2400(snmpv3)## show-trap id=1 Trap ID Trap Type Host IP Community Auth. Type : : : : : 1 v1 3.94.200.
SNMP CHAPTER 16: SNMP Configuring SNMP (continued) ML2400(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 -------- ML2400(snmpv3)## show-group id=1 Group ID Group Name Model Com2Sec ID : : : : 1 v1 v1 1 ML2400(snmpv3)## view add id=1 viewname=all type=included subtree=.
CHAPTER 16: SNMP SNMP Configuring SNMP (continued) ML2400(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 --------- ML2400(snmpv3)## show-access id=1 Access ID Access Name Sec. Model Sec.
SNMP CHAPTER 16: 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–4. 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.
CHAPTER 16: SNMP 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.
SNMP CHAPTER 16: SNMP Z When done adding trap receivers, click OK. 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 ( ).
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 family of switches 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 ML2400(rmon)## show rmon event RMON Event Default Owner : test RMON Event Default Community : somestring ML2400(rmon)## exit ML2400# 16–14 MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 17: Miscellaneous Miscellaneous commands 17.1 Alarm Relays 17.1.1 Description In a wiring closet, it would be helpful if there were a visual indication for faults on components on the network. Normally, these would be performed by LEDs.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS Table 17–1: Pre-defined conditions for the relay Event ID Note Description Signal type 1 S-RING OPEN (see note below) SUSTAINED 2 Cold Start MOMENTARY 3 Warm Start MOMENTARY 4 Link Up MOMENTARY 5 Link Down MOMENTARY 6 Authentication Failure MOMENTARY 7 RMON Rising Alarm MOMENTARY 8 RMON Falling Alarm MOMENTARY 9 Intruder Alarm MOMENTARY 10 Link Loss Learn Triggered MOMENTARY 11 Broadcast Storm Detected MOMENTARY
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS Alarm relays (continued) ML2400(alarm)## add event=2 Alarm Event(s) Added: 2 ML2400(alarm)## show alarm Alarm Events Configuration -------------------------Alarm Status: DISABLED Relay Closure Time Period: 5 Seconds EventId Description Mode -----------------------------------------1 S-RING OPEN SUSTAINED 2 Cold Start MOMENTARY 3 Warm Start MOMENTARY 4 Link Up MOMENTARY 5 Link Down MOMENTARY 6 Authentication Failure MOMENTARY 7 RMON Raising Alarm M
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS Example 17-1: Alarm relays ML2400# alarm ML2400(alarm)## add event=2 Alarm Event(s) Added: 2 ML2400(alarm)## add event=1-5 Event 2 is Already Enabled. Alarm Event(s) Added: 1, 3, 4, 5 ML2400(alarm)## add event=6,8 Alarm Event(s) Added: 6, 8 ML2400(alarm)## add event=all Event 1 Event Event Event Event Event Event Alarm is Already Enabled. 2 is Already Enabled. 3 is Already Enabled. 4 is Already Enabled. 5 is Already Enabled.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS Alarm relays (continued) ML2400(alarm)## show alarm Alarm Events Configuration -------------------------Alarm Status: DISABLED Relay Closure Time Period: 5 Seconds EventId Description Mode -----------------------------------------1 S-RING OPEN NOT ENABLED 2 Cold Start MOMENTARY 3 Warm Start NOT ENABLED 4 Link Up MOMENTARY 5 Link Down NOT ENABLED 6 Authentication Failure MOMENTARY 7 RMON Raising Alarm NOT ENABLED 8 RMON Falling Alarm MOMENTARY 9 Int
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS 17.2 E-mail 17.2.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.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS The show smtp command displays the current SMTP global settings and recipients displays the currently configured recipients of e-mail alerts. show smtp The add command adds a specific id, where id represents the recipient identification and ranges from 1 to 5.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS 17.2.3 Example The following example shows how to set SMTP to receive SNMP trap information via e-mail. E-mail alerts can be forwarded to be received by other devices such as cellphones and pages. Most interfaces to SMTP are already provided by the service provider. Note Example 17-2: Configuring SMTP to receive SNMP trap information via e-mail ML2400#smtp ML2400(smtp)##server ip=3.94.210.25 port=25 retry=3 domain=ge.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS 17.3 Statistics 17.3.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 3.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS 17.4 Serial Connectivity 17.4.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 switches 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.5 History 17.5.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.6 Ping 17.6.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: ML2400# ping 3.94.248.61 3.94.248.61 is alive, count 1, time = 40ms ML2400# 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.7 Prompt 17.7.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 ML2400 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.8 System Events 17.8.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.9 Command Reference 17.9.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.9.2 Configuration commands The access commands are shown below.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS • clear-stats • 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 Port Mirroring on page 9–1 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 Securing Access on page 6–1 for additional details.
CHAPTER 17: MISCELLANEOUS COMMANDS MISCELLANEOUS COMMANDS The Simple Mail Transfer Protocol (SMTP) commands for e-mail are shown below. Refer to E-mail on page 17–6 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 SNMP on page 16–1 for additional details.
MISCELLANEOUS COMMANDS CHAPTER 17: MISCELLANEOUS COMMANDS • useraccess The VLAN commands are shown below. Refer to VLAN on page 10–1 for additional details.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 18: Modbus Protocol Modbus Protocol 18.1 Modbus Configuration 18.1.1 Overview Modicon programmable controllers as well as other PLCs can communicate with each other and other devices over a variety of networks. The common language used by all Modicon controllers is the Modbus protocol. This protocol defines a message structure that controllers recognize and use regardless of the networks over which they communicate.
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, ML2400# 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.2 Memory Mapping 18.2.1 Modbus Memory Map The Modbus memory map is shown below. Refer to Format Codes on page 18–36 for details on the items in the format column. Table 18–1: Modbus memory map (Sheet 1 of 33) Range Step Format 0000 Address System name (12 registers) Description - - String Default Varies 000C System contact (12 registers) - - String multilin.tech @ge.
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 2 of 33) Address 18–4 Range Step Format Default 0062 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 3 of 33) Range Step Format Default 0090 Address 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 Port 3 S
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 4 of 33) Address 18–6 Range Step Format Default 00BE 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 t
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 5 of 33) Range Step Format Default 00F0 Address 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 to 51
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 6 of 33) Address 18–8 Range Step Format Default 0128 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 7 of 33) Range Step Format Default 0160 Address 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 0 to 4
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 8 of 33) Address 18–10 Range Step Format Default 0198 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 9 of 33) Range Step Format Default 01D0 Address 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 0 to 4
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 10 of 33) Address 18–12 Range Step Format Default 0208 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:
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 11 of 33) Range Step Format Default 0240 Address 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 bytes)
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 12 of 33) Address 18–14 Range Step Format Default 0278 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 13 of 33) Description Range Step Format Default 02B0 Address 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 byte fram
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 14 of 33) Address 18–16 Range Step Format Default 02E8 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 15 of 33) Range Step Format Default 0320 Address 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 multica
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 16 of 33) Address 18–18 Range Step Format Default 0358 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 17 of 33) Description Range Step Format Default 0390 Address 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 Port 15:
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 18 of 33) Address 18–20 Range Step Format Default 03C8 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: Num
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 19 of 33) Range Step Format Default 0400 Address 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 4294967295
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 20 of 33) Address 18–22 Range Step Format Default 0438 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 occurr
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 21 of 33) Range Step Format Default 0470 Address 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 received/se
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 22 of 33) Address 18–24 Range Step Format Default 04A8 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 Por
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 23 of 33) Range Step Format Default 04E0 Address 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: Numbe
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 24 of 33) Address 18–26 Range Step Format Default 0518 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 25 of 33) Range Step Format Default 0550 Address 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 055A
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 26 of 33) Address 18–28 Range Step Format Default 0588 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 broadcas
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 27 of 33) Range Step Format Default 05C0 Address 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 05CA
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 28 of 33) Address 18–30 Range Step Format Default 05F8 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 29 of 33) Range Step Format Default 0630 Address 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 received/sen
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 30 of 33) Address 18–32 Range Step Format Default 0668 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 31 of 33) Range Step Format Default 06A0 Address 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 F9 0 0
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 32 of 33) Address 18–34 Range Step Format Default 06D8 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
CHAPTER 18: MODBUS PROTOCOL MODBUS PROTOCOL Table 18–1: Modbus memory map (Sheet 33 of 33) Range Step Format Default 0710 Address 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 ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL 18–35
MODBUS PROTOCOL CHAPTER 18: MODBUS PROTOCOL 18.2.2 Format Codes • Bitmap: 32-bit group of bits, packed into two registers. Encoded in big endian.
GE Consumer & Industrial Multilin Multilink ML2400 Ethernet Communications Switch Chapter 19: Appendix Appendix 19.1 Revision History 19.1.1 Change Notes Table 19–1: Revision history Part Number Revision Release Date ECO 1601-0220-A1 1.5.1 06 May 2005 --- 1601-0220-A2 1.5.1 19 May 2005 --- 1601-0220-A3 1.5.1 11 July 2005 --- 1601-0220-A4 1.5.1 16 September 2005 --- 1601-0220-A5 1.6.1 08 June 2006 --- 1601-0220-A6 1.7.x 18 August 2006 --- 1601-0220-A7 1.7.
APPENDIX CHAPTER 19: APPENDIX Table 19–3: Updates for Manual Revision AA Section Description General Manual revised to AA General Firmware release revised to 2.0.x 1.2.1 Order Code table revised 1.3.3 Added Type Tests section 5.5 IPv6 section added 5.4.2, 5.4.3, 5,4,4 Improved Configuration sections (3) added Table 4-2 Corrections to table Table 18-1 Add one new RAW to table - address 0716 Table 19–4: Updates for Manual Revision A9 Section Description 1.2.
CHAPTER 19: APPENDIX APPENDIX Table 19–6: Updates for 1601-0220-A6 Page (A5) Page (A6) Change Description Title Title Update Manual revision to A6 1-2 1-2 Update Updated Ordering section 1-3 1-3 Update Updated Power Supply specifications 9-7 9-7 Update Updated Link Loss Alert section Table 19–7: Updates for 1601-0220-A5 Page (A4) Page (A5) Change Description Title Title Update Manual revision to A5 1-2 1-2 Update Updated Ordering section 1-3 1-3 Update Updated Power Supp
APPENDIX CHAPTER 19: APPENDIX Table 19–8: Major updates for 1601-0220-A4 (Sheet 2 of 2) Page (A3) Page (A4) 1-3 1-3 Change Update Description Updated Power Supply specifications Table 19–9: Major updates for 1601-0220-A3 Page (A2) Page (A3) Change Description Title Title Update Manual revision to A3 1-3 1-3 Update Updated Power Supply specifications Table 19–10: Major updates for 1601-0220-A2 19–4 Page (A1) Page (A2) Change Description Title Title Update Manual revision to A2 1
CHAPTER 19: APPENDIX APPENDIX 19.2 Warranty 19.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.
APPENDIX 19–6 CHAPTER 19: APPENDIX MULTILINK ML2400 ETHERNET COMMUNICATIONS SWITCH – INSTRUCTION MANUAL
INDEX Index Numerics 802.1X ......................................................................................................... 7-1, 7-4 A ALARM CONTACT .............................................................................................. 3-9 ALARM RELAY ............................................................................................ 2-8, 17-1 specifications ................................................................................................... 1-4 APPLICATIONS ....
INDEX F FCC APPROVAL .................................................................................................. 1-6 FEATURES ........................................................................................................... 2-7 FILTERING ........................................................................................................... 4-1 FLOW CONTROL .................................................................................. 2-7, 4-3, 9-5 FORWARDING .......................
INDEX N NETWORK TIME ................................................................................................ 5-10 O ORDER CODES ................................................................................................... 1-2 P PACKET PRIORITIZATION ................................................................................. 2-7 PASSWORDS ...................................................................................................... 6-1 PING ....................................
INDEX SYSTEM PARAMETERS ....................................................................................... 5-8 T TACACS ............................................................................................................... 7-1 TACACS+ ............................................................................................................. 8-1 TAG VLAN ....................................................................................................... 10-13 TELNET .....................
