These instructions do not purport to cover all details or variations in equipment nor provide
for every possible contingency to be met in connection with installation, operation, or
maintenance. Should further information be desired or should particular problems arise
which are not covered sufficiently for the purchaser’s purpose, the matter should be referred
to the General Electric Company.
To the extent required the products described herein meet applicable ANSI, IEEE, and NEMA
standards; but no such assurance is given with respect to local codes and ordinances
because they vary greatly.
GE Multilin Multilink ML2400 instruction manual for revision 3.x.
Multilink ML2400 is a registered trademark of GE Multilin Inc.
The contents of this manual are the property of GE Multilin Inc. This documentation is
furnished on license and may not be reproduced in whole or in part without the permission
of GE Multilin. The content of this manual is for informational use only and is subject to
change without notice.
Part numbers contained in this manual are subject to change without notice, and should
therefore be verified by GE Multilin before ordering.
Part number: 1601-0220-AB (June 2008)
TOCTABLE OF CONTENTS
Table of Contents
1: INTRODUCTIONGETTING STARTED ............................................................................................................... 1-1
Examine the shipping container for obvious damage prior to installing this product; notify
the carrier of any damage that you believe occurred during shipment or delivery. Inspect
the contents of this package for any signs of damage and ensure that the items listed
below are included.
This package should contain:
• MultiLink ML2400 Ethernet Switch, base unit (configured with user-selected port
module options installed)
• Set of metal “ears” for 19-inch rack mounting
• Installation and user guide (this manual)
Remove the items from the shipping container. Be sure to keep the shipping container
should you need to re-ship the unit at a later date. To validate the product warranty, please
complete and return the enclosed product registration card to GE Multilin as soon as
possible.
In the event there are items missing or damaged, contact the party from whom you
purchased the product. If the unit needs to be returned, please use the original shipping
container if possible. Refer to Troubleshooting on page 4–7, for specific return procedures.
IEEE 802.3x:.......................................................Flow control
MAXIMUM 10 MBPS ETHERNET SEGMENT LENGTHS
Unshielded twisted pair: .............................100 m (328 ft.)
Shielded twisted pair:...................................150 m (492 ft.)
10Base-FL multi-mode fiber optic: .......2 km (6562 ft .)
10Base-FL single-mode fiber optic: .....10 km (32810 ft.)
MAXIMUM STANDARD FAST ETHERNET SEGMENT LENGTHS
10Base-T (CAT 3, 4, 5 UTP): ........................100 m (328 ft.)
100Base-TX (CAT 5 UTP): .............................100 m (328 ft.)
Shielded twisted pair:...................................150 m (492 ft.)
100Base-FX, half-duplex, multi-mode: 412 m (1350 ft.)
100Base-FX, full-duplex, multi-mode: .2.0 km (6562 ft.)
100Base-FX, half-duplex, single-mode: 412 m (1350 ft .)
100Base-FX, full-duplex, long reach: ...40.0 km (122K ft.)
MAXIMUM STANDARD GIGABIT ETHERNET SEGMENT LENGTHS
1000Base-T (CAT5e or higher is recommended): 100 m (328 ft.)
1000Base-SX, full-duplex, multi-mode (62.5 μm cable): 220 m
1000Base-SX, full-duplex, multi-mode (50 μm cable): 550 m
FIBER MULTI-MODE CONNECTORS
Fiber port, ST (twist-lock): ..........................fiber multi-mode, 10 Mb 10Base-FL
100/10: ................................................................ON = 100 Mbps; OFF = 10 Mbps
ALARM RELAY CONTACTS
One NC indicating internal power, one NC firmware controllable
Maximum Voltage:.........................................up to 250 V AC, 220 V DC
Maximum Switching Power:......................60 W, 125 VA
Maximum Carrying Current:......................2 A @ 30 V DC
0.2 A @ 220 V DC
MANAGEMENT CONSOLE
Connector:.........................................................DB-9 for RS-232 “null-modem” cable (sometimes called
an X-modem cable)
POWER SUPPLY
Input voltage: ...................................................LOW RANGE (LO Power Supply)
Nominal DC Voltage: 48 V DC
Min/Max DC Voltage: 36/60 V DC
................................................................................HIGH RANGE (HI and AC Power Supply)
Nominal DC Voltage: 110 to 250 V DC
Min/Max DC Voltage: 88/300 V DC
Nominal AC Voltage: 100 to 240 V AC
Min/Max AC Voltage: 85/265 V AC
Input current (fiber): ......................................LO: 1.59 A maximum
HI: 1.8 A maximum for AC voltage
0.9 A maximum for DC voltage
AC: 1.8 A maximum
Standard terminal block: ...........................“–”, “+”, internally floating
Ground: ...............................................................Terminal for filter ground wire, external connection to the
ML2400 chassis
Power consumption:.....................................55 watts typical; 60 watts maximum for a fully loaded
fiber model; 35 watts maximum for a fully-loaded RJ45
model
Internal Fuse:.......................................... HI: Ceramic, axial SLO BLO, 3 A /350 V AC
Manufacturer: Conquer
Part Number: SCD-A 003
LO: Ceramic, axial SLO BLO, 5 A /350 V AC
Manufacturer: Conquer
Part Number: SCD-A 005
PER-PORT JUMPERS AND SWITCHES
The copper daughter board has on internal switch for selecting MDI-MDIX crossover on port # 1.
Other port-specific user settings (such as FDX or HDX, copper 10/100 speed) can be fixed using
firmware commands.
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 1
st
edition
CSA:.......................................................................Certified per C22.1 No. 60950-1 1
st
edition
WARRANTY
24 months from date of shipment
Manufactured in USA
GE Multilin reserves the right to change specifications, performance, characteristics, and/or model
• parameter 2 can be used optionally only if parameter 1 is specified
• parameter 3 is mandatory.
Whenever the word PC is used, it implies a UNIX, Linux, Windows, or any other operating
system based workstation, computer, personal computer, laptop, notebook or any other
computing device. Most of the manual uses Windows XP based examples. While effort has
been made to indicate other operating system interactions, it is best to use a Windows-XP
based machine when in doubt.
The documentation reflects features of MultiLink Switch Software version 1.7.x or later. If
your switch is not at the current version, GE Multilin recommends upgrade to version 1.7.x
or later. Please refer to the GE Multilin website for information on upgrading the MultiLink
Switch Software.
1.4.2EnerVista Software
Icons common to the EnerVista MultiLink Secure Web Management (SWM) firmware for
edit, delete, save and refresh are:
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.A female-female null modem cable.
2.A serial port . If your PC does not have a serial port, you may want to invest in
a USB-to-serial converter or USB-to-serial cable.
3.Terminal emulation firmware such as HyperTerminal or other equivalent
firmware. Ensure the firmware supports Xmodem protocol, as you may need
this in the future to update the MultiLink Switch Software.
4.Enough disk space to store and retrieve the configuration files as well as copy
firmware files. We recommend at least 15 MB of disk space for this purpose.
5.For access security - decide on a manager level account name and password
6.IP address, netmask, default gateway for the switch being configured.
As a default, the switch has no IP (Internet Protocol) address and subnet mask. For first
time use, the IP address has to be assigned. This can only be done by using the console
interface provided.
The same procedure can also be used for other configuration changes or updates (for
example, changing the IP address, VLAN assignments and more). Once the IP address is
assigned and a PC is networked to the switch, the switch's command line interface (CLI)
can be accessed via telnet. To manage the switch through in-band (networked) access
(e.g. telnet, or web browser Interface), you should configure the switch with an IP address
and subnet mask compatible with your network. Also, change the manager password to
control access privileges from the console.
Many other features such as optimizing the switch's performance, traffic engineering and
traffic prioritizing, VLAN configuration, and improving network security can be configured
through the switch's console interface as well as in-band (networked) access, once the IP
address is setup. Besides the IP address, setting up the SNMP parameters allows
configuration and monitoring through an SNMP network management station running a
network management program.
The connection to the console is accessed through the DB-9 RS232 connector on the
switch marked as the console port. This command line interface (or CLI) provides access to
the switch commands. It can be accessed by attaching a VT100 compatible terminal or a
PC running terminal emulation firmware to the console port.
USB-to-serial adapters are also available for computers that do not native serial ports but
have access to USB ports.
The interface through the console or the console management interface (or CMI) enables
you to reconfigure the switch and to monitor switch status and performance.
Once the switch is configured with an IP address, the command line interface (or CLI) is
also accessible using telnet as well as the serial port. Access to the switch can be either
through the console interface or remotely over the network. Simultaneous access (that is,
through the console port as well as through the network) to the MultiLink switch is not
permitted.
The Command Line Interface (CLI) enables local or remote unit installation and
maintenance. The MultiLink family of switches provides a set of system commands which
allow effective monitoring, configuration and debugging of the devices on the network.
1.5.2Console Setup
Connect the console port on the switch to the serial port on the computer using the serial
cable listed above. The settings for the HyperTerminal firmware emulating a VT100 are
shown below. Make sure the serial parameters are set as shown (or bps = 38400, data bits
= 8, parity = none, stop bits = 1, flow control = none).
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. The prompts are shown below with a brief
description.
• ML2400>
Operator Level - for running operations queries
• ML2400#
Manager Level - for setting and reviewing commands
• ML2400##
Configuration Level - for changing the switch parameter values
For additional information on default users, user levels and more, refer to User Management on page 1–14.
1.5.4Logging In for the First Time
For the first time, use the default user name and passwords assigned by GE. They are:
•Username: manager
Password: manager
•Username: operator
Password: operator
We recommend you login as manager for the first time to set up the IP address as well as
change user passwords or create new users.
1.5.5Automatic IP Address Configuration
The ML2400 is operational immediately after it is powered up. The advanced management
and configuration capabilities of the ML2400 allows you to easily configure, manage, and
secure your devices and network.
Before starting, ensure you have the following items:
• RJ45 Ethernet cable
•PC with an Ethernet port
• Microsoft Internet Explorer 6.0 or higher
• Macromedia Flash Player 5.0 or higher (available from http://
Ensure both firmware components are installed before proceeding.
The ML2400 can search the network for commonly used services that can issue an IP
address. If the switch is connected to a network, the ML2400 uses the following process to
find an IP address.
If the ML2400 is not connected to a network, then proceed to Step 3 below. or use the
default IP address.
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. To manage the switch, determine the
assigned IP address and enter as follows in Internet Explorer:
https://
<assigned_IP_address>
Ensure that https is entered, not http, and that there is connectivity (that is, you can ping
the switch).
Step 2:
If there is no response from a DCHP server, the ML2400 will query for a BOOTP server. If the
server responds, the ML2400 will acquire and set the assigned IP address. To manage the
switch, determine the assigned IP address and enter as follows in Internet Explorer:
https://
<assigned_IP_address>
Ensure that https is entered, not http, and that there is connectivity (that is, you can ping
the switch).
Step 3:
If there is no response from either a DCHP or BOOTP server, or if the switch is not
connected to a network, the switch will assign itself an IP address. The ML2400 will check
to see if IP address 192.168.1.2, with a network mask of 255.255.255.0, is free. If so, it will
assume these values. If this IP address is assigned to another device, the ML2400 will
repeat steps 1 through 3 to find a DCHP or BOOTP server or wait for the 192.168.1.2
address to become free.
Once connected, the browser will display a login prompt. The default login is:
•Username: manager
Password: manager
1.5.6Setting the IP Parameters
To setup the switch, the IP address and other relevant TCP/IP parameters have to be
specified.
The IP address on the MultiLink switch is set to 192.168.1.2 from the factory. The switch is
fully operational as a Layer 2 switch as a default. Setting a default IP address can
potentially cause duplicate IP address problem if multiple switches are powered on and
installed on the network. To manage the switch, an IP address has to be programmed.
Before starting, please ensure that the IP address assigned to the switch is known or
contact your system/network administrator to get the IP address information. Follow the
steps listed below to configure the switch.
Z Ensure the power is off.
Z Follow the steps described above for connecting the console cable
This manual assumes the reader is familiar with IP addressing schemes as well as how net
mask is used and how default gateways and routers are used in a network.
Reboot gives an opportunity to save the configuration prior to shutdown. For a reboot,
simply type in the command
reboot. Note that even though the passwords are not
changed, they can be changed later.
ML2400# reboot
Proceed on rebooting the switch? ['Y' or 'N'] Y
Do you wish to save current configuration? ['Y' or 'N'] Y
ML2400#
The ML2400 forces an answer by prompting with a “Y” or a “N” to prevent accidental
keystroke errors and loss of work.
The parameters can be viewed at any time by using the
show command. The show
command will be covered in more detail later in various sections throughout the
document.
The example below illustrates the basic setup parameters. You can use
show setup or
show sysconfig commands to view setup parameters.
ML2400# show setup
Version: ML2400 build 1.6.1 Apr 29 2005 11:10:13
MAC Address: 00:20:06:27:0a:e0
IP Address: 3.94.247.41
Subnet Mask: 255.255.252.0
Gateway Address: 3.94.244.1
CLI Mode: Manager
System Name: ML2400
System Description: 25 Port Modular Ethernet Switch
System Contact: multilin.tech@ge.com
System Location: Markham, Ontario
System ObjectId: 1.3.6.1.4.1.13248.12.7
ML2400# show sysconfig
System Name: ML2400
System Contact: multilin.tech@ge.com
System Location: Markham, Ontario
Boot Mode: manual
Inactivity Timeout(min): 120
Address Age Interval(min): 300
Inbound Telnet Enabled: Yes
Web Agent Enabled: Yes
Time Zone: GMT-05hours:00minutes
Day Light Time Rule: Canada
System UpTime: 0 Days 0 Hours 45 Mins 55 Secs
ML2400#
Some of the parameters in the MultiLink family of switches are shown above. The list of
parameters below indicates some of the key parameters on the switch and the
recommendations for changing them (or optionally keeping them the same).
1.5.7Privilege Levels
Two privilege levels are available - manager and operator. Operator is at privilege level 1
and the manager is at privilege level 2 (the privilege increases with the levels). For example,
to set up a user for basic monitoring capabilities use lower number or operator level
privilege (level 1).
The Manager level provides all operator level privileges plus the ability to perform systemlevel actions and configuration commands. To select this level, enter the
name>
prompted.
For example, switching from an operator-level to manager-level, using the
command is shown below.
Note the prompt changes with the new privilege level.
Operator privileges allow views of the current configurations but do not allow changes to
the configuration. A “>” character delimits the operator-level prompt.
Manager privileges allow configuration changes. The changes can be done at the
manager prompt or for global configuration as well as specific configuration. A “#”
character delimits any manager prompt.
enable <user-
command at the Operator level prompt and enter the Manager password, when
enable <user-name>
enable
ML2400> enable manager
Password: *******
ML2400#
1.5.8User Management
A maximum of five users can be added per switch. Users can be added, deleted or
changed from a manager level account. There can be more than one manager account,
subject to the maximum number of users on the switch being restricted to five.
To add a user, use the add command as shown below. The user name has to be a unique
name. The password is recommended to be at least 8 characters long with a mix of upper
case, lower case, numbers and special characters.
add user=<name> level=<number>
The following example adds a user “peter” with manager-level privilege:
ML2400# user
ML2400(user)##
Enter User Password:******
Confirm New Password:******
add user=peter level=2
ML2400(user)##
To delete a user, use the delete command as shown below.
delete user=<name>
The following example deletes the user “peter”:
ML2400(user)## delete user=peter
Confirm User Deletion(Y/N): Y
User successfully deleted
ML2400(user)##
The syntax to modify a password is shown below:
passwd user=<name>
The following example changes the password for user “peter”.
1.5.9Help
ML2400(user)## passwd user=peter
Enter New Password:******
Confirm New Password :******
Password has been modified successfully
ML2400(user)##
The syntax to modify the privilege level for a specific user is shown below:
chlevel user=<name> level=<number>
The following example modifies the privilege level of user “peter ” to Operator privileges.
ML2400(user)## chlevel user=peter level=1
Access Permission Modified
ML2400(user)##
The syntax to set the access privileges for telnet and Web services is shown below:
Help for any command that is available at the current context level can be viewed by
typing help followed by enough of the command string to identify the command. The
following syntax applies:
help <command string>
For example, to list the help for the
set time command
ML2400# help set time
set time : Sets the device Time
Usage
set time hour=<0-23> min=<0-59> sec=<0-59> [zone=GMT[+/-]hh:mm]
ML2400#
The options for a specific command can be displayed by typing the command and
pressing enter. The following syntax applies:
command <Enter>
For example, the options for the
show command are:
ML2400# show <Enter>
Usage
show active-stp
show active-snmp
show active-vlan
show address-table
show age
show alarm
show arp
show auth <config|ports>
show backpressure
show bootmode
--more--
Other ways to display help, specifically, with reference to a command or a set of
commands, use the TAB key. The following syntax applies:
<TAB>
<Command string> <TAB>
<First character of the command> <TAB>
For example, following the syntax listed above, the <TAB> key will list the available
commands in the particular privilege level:
The following example lists commands starting with a specific string:
ML2400> s <TAB>
set
show
ML2400>
In the following example, the <TAB> key completes the command:
ML2400> se<TAB>
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.
The following syntax applies:
logout
The following example illustrates logging out from a session:
ML2400> logout
Logging out from the current session [’Y’ or ’N’] Y
Enter the following URL in the web browser to login to the EnerVista Secure Web
Management software.
https://<IP Address assigned to the switch>
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. Please make
sure that the name is resolved to the IP address assigned to the switch.
The secure site will issue the certificate check shown below.
FIGURE 1–2: Security certificate
Once you click Yes on the security certificate, the browser will prompt you to login.
FIGURE 1–3: Login screen
For the first time,
Z Login with the name manager and password manager.
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.2Privilege Levels
• Operator privilege users: operator privileges allow views of the current
• Manager privilege users: manager privileges allow configuration changes. The
1.6.3User Management
A maximum of five users can be added per switch. Users can be added, deleted or
changed from a manager level account. There can be more than one manager account,
subject to the maximum number of users on the switch being restricted to five.
The username must be a unique name. The password is recommended to be at least 8
characters long with a mix of upper case, lower case, numbers and special characters.
configurations but do not allow changes to the conf iguration.
changes can be done at the manager prompt or for global configuration as well as
specific configuration.
Z Select the Administration > User Mgmt > User Accounts menu
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.4Modifying the Privilege Level
Privilege levels cannot be changed from the EnerVista Secure Web Management (SWM)
firmware. This can only be done through the CLI interface, or alternately, by deleting the
user and adding the same user with the proper privilege level.
1.6.5Help
Help for the EnerVista Secure Web Management software can be obtained by clicking on
the Help icon as shown below.
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.
For serial port updates directly through the serial/console port, the following items are
required.
1.A female-to-female null modem cable.
2.A USB-to-serial converter or cable if your PC does not have a serial port. A
cable is available from GE Multilin.
3.Terminal emulation firmware such as HyperTerminal (included with Windows)
or equivalent. Ensure that the firmware supports the Xmodem protocol
4.At least 15 MB of free disk space.
5.Manager level account name and password of the switch being upgraded.
6.An internet connection. Ensure the connection does not block ftp file transfers
1.7.2Selecting the Proper Version
Ensure that the proper version of the MultiLink Switch Software is installed. The latest
version of the firmware is available at http://www.GEmultilin.com
Z Connect to the ML2400 and login as manager.
Z Enter the
Z Download the latest version of MultiLink firmware from the GE
Multilin website.
1.7.3Updating through the Command Line
Use the following procedure to install firmware to the ML2400 via the serial port .
Z Download the MultiLink Switch Software from the GE Multilin web
site.
Z Use the null-modem cable to connect to the ML2400 serial port.
Z Login at the manager level with the proper password.
Z Save the existing configuration (refer to Saving Configuration on
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://<IP address of the switch>
If using FTP, save the configuration before proceeding. GE Multilin recommends a two-step
update: first save the configuration to the ftp server, then load the new image and restart
the switch (refer to Saving Configuration on page 5–19 for details on saving the
configuration).
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.
Z If using TFTP, save the configuration before proceeding.
GE Multilin recommends a two-step update:
• first save the configuration to the TFTP server,
• then load the new image and restart the switch (refer to Saving Configuration on page 5–19 for details on saving the
configuration).
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.1p QoS prioritization is included, providing high performance switching
services for both “smooth” streaming and “bursty” data traffic.
The MultiLink ML2400 Ethernet Switch has up to 25 ports capacity, all of which may be
configured as fiber ports, while offering a space-saving rack-mount chassis that is only 1 U
(1.70 inches or 4.32 cm) in height. The “mixed-media” capability allows user-selection of all
popular flavors of fiber port connectors and modes, including 10Mb fiber alongside Gigabit
ports. It also allows a mix of 10/100Mb RJ45 (copper) ports and a fiber Gigabit port in the
same unit. This flexibility is achieved via a family of communication modules for copper
and fiber, six-port modules for fiber and RJ45 combinations, and 1 Gb port module
selections using GBICs. These modules are factory configured in a base chassis unit (or
may be changed in the field by trained technicians) to adapt the unit to the user's
application and Ethernet cabling requirements. Evolving mixed-media requirements for
10 Mb and 100 Mb fiber and copper as well as Gigabit ports can be handled by the
ML2400.
The packaging and power-input options target the ML2400 at heavy-duty applications.
Rack widths accommodated include standard 19" RETMA, ETSI, and 23". Input power may
be 48 V DC for telecommunications environments or 125 V DC for industrial applications.
Redundant power supplies are optional on all models.
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.1p packet prioritization in hardware, and industry-standard
managed networks software functionality, all in convenient 1 U rack-mount packages.
The ML2400 is a 19" rack-mountable Ethernet switch with three eight-port slots (A, B, and
C) and one Gb-only slot (D). Slots A, B and C may be configured with a selection of fiber and
copper ports. Slot D may be configured with a Gb module that accepts GBICs. These
configurable ports allow the ML2400 to efficiently serve a large variety of applications. The
ML2400 modules are usually factory installed, but may be changed or added at a later
date in the field.
Status LEDs are part of each port module and are viewable when connecting the Ethernet
media. The port status data is also accessible through the MultiLink Switch Software.
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.CDR
FIGURE 2–1: Example two-Port 10Mb mm fiber ST module & two-Port 100Mb mm fiber ST module
The default setup on the 10 Mb fiber module is half-duplex, which allows the ML2400 to
connect to any 10 Mb hub, media converter, or almost any device with a 10 Mb fiber
Ethernet port. The default setting of the 100 Mb fiber modules is full-duplex. User mode
control per port through the software “port settings” is the same as the other modules.
Note
The status LED layout on a 10Mb fiber port pair is different from that on a 100 Mb fiber port
pair. Notice that on the above image, where the 2 x 10 Mb ST mm fiber poarts have three
LEDs next to each port, the 2 x 100 Mb ST mm fiber ports have 4 LEDs combined for the 2
ports, and under each port is a link LED. In both cases, the number of status LEDs is the
same for each port.
There are three LEDs per fiber port. The Link (LK) LED, when lit, indicates "ready for
operation" on that port, the F/H LED indicates operation in full-duplex mode when ON
(half-duplex when OFF), and the blinking ACT LED indicates receiving activity on the port. A
fiber cable must be connected to the port, and the link (LK) indicator for that port must be
ON (indicating there is a powered-up device at the other end of the cable) in order for a LK
LED to provide valid indications of operating conditions on that port. Color-coding on the
panel of the module shows which LEDs belong to which port.
The fiber ports support fiber cabling distances according to the 10Base-FL and 100BaseFX standards, i.e., 2 km distance for multi-mode fiber. A single-mode option for greater
distance may be available as a special order, contact GE Multilin.
The combo four-port modules are combinations of copper and fiber media, available as
two 10/100 switched RJ45 copper ports and two 100 Mb switched multi-mode fiber ST or
SC ports as shown below.
•AF module: 2 × 10 Mb ST mm fiber and 2 × 100 Mb ST mm fiber
•AG module: 2 × RJ45 10/100 Mb copper and 2 × 100 Mb SC sm fiber
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.
• A5 module: 2 × 10 Mb ST mm fiber and 4 × RJ45 10/100 Mb copper
• A6 module: 2 × 100 Mb ST mm fiber and 4 × RJ45 10/100 Mb copper
• A7 module: 2 × 100 Mb ST sm fiber and 4 × RJ45 10/100 Mb copper
• A8 module: 2 × 100 Mb SC sm fiber (20 km) and 4 × RJ45 10/100 Mb copper
• A9 module: 2 × 100 Mb SC sm fiber (40 km) and 4 × RJ45 10/100 Mb copper
For ports numbering, ports 1, 3, 5, and 7 are copper, ports 2 and 6 are fiber, while ports 4
and 8 are not present.
The four RJ45 ports operate just like the 8-port copper module, and the two fiber ports
operate at 100 Mbps full-duplex (default). User mode control per port through the ML2400
software is also the same.
On the six-port combo modules, there are four LEDs for each RJ45 port, which indicate
status the same as described in the previous section.
There are three LEDs per fiber port. The Link (LK) LED, when lit, indicates "ready for
operation" on that port, the F/H LED indicates operation in full-duplex mode when ON
(half-duplex when OFF), and the blinking ACT LED indicates receiving activity on the port . A
fiber cable must be connected to the port, and the link (LK) indicator for that port must be
ON (indicating there is a powered-up device at the other end of the cable) in order for a LK
LED to provide valid indications of operating conditions on that port . Color-coding on the
panel of the module shows which LEDs belong to which port.
The six-port modules are also available with four RJ45 10/100 copper and two 10 Mb fiber
mm ST ports. For detailed information about 10Mb mm ST fiber half of the module, refer to
the next section.
2.2.3Eight-port Modules
754703A1.CDR
FIGURE 2–2: Two 10 Mb ST fiber and four RJ45 10/100 Mb copper
The ML2400 8-port copper module (A4 module) provides eight 10/100 Mb switched RJ45
ports. The 10/100Mb switched ports normally (as a default setting) are independently n-
way auto-negotiating for operation at 10 or 100 Mb speed in full or half-duplex mode; that
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. The blinking ACT
(Activity) LED indicates receiving Activity on that port when lit. The 10/100 LED indicates
operation at 100 Mb speed when ON and at 10 Mb speed when OFF (when autonegotiation is not disabled). The F/H LED is ON to indicate full-duplex operation and OFF to
indicate half-duplex mode. A twisted pair cable must be connected into an RJ45 port and
the Link (LK) indicator for that port must be ON (indicating there is a powered-up device at
the other end of the cable) in order for a LK LED to provide valid indications of operating
conditions on that port.
Using the ML2400 management software, the user may disable auto-negotiation and fix
the desired operation of each RJ45 port. User may select the 10 or 100 Mb speed and full
or half-duplex mode per-port as per the user requirement.
The combo eight-port modules are combinations of copper and fiber media, available in
the configurations shown below.
•AA module: 4 × 100 Mb LC mm fiber (2 km) and 4 × RJ45 10/100 Mb copper
•AB module: 8 × 100 Mb LC mm fiber (2 km)
•AC module: 4 × 100 Mb LC sm fiber (15 km) and 4 × RJ45 10/100 Mb copper
•AD module: 8 × 100 Mb LC sm fiber (15 km)
•AE module: 2 × 100 Mb LC sm fiber (15 km) and 6 × RJ45 10/100 Mb copper
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.
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.1p standard and fulfills its role in
support of QoS, giving packet processing priority to priority tagged packets according to
the 802.1p standard. In addition to hardware support for QoS, the ML2400 software
supports two priority queues that can be shared across the eight levels of defined packet
priorities for application-specific priority control by the user through software
configuration settings.
2.3.2Frame Buffering and Flow Control
The ML2400 is a store-and-forward switch. Each frame (or packet) is loaded into the
switch's memory and inspected before forwarding can occur. This technique ensures that
all forwarded frames are of a valid length and have the correct CRC, i.e., are good packets.
This eliminates the propagation of bad packets, enabling all of the available bandwidth to
be used for valid information.
While other switching technologies (such as “cut-through” or “express”) impose minimal
frame latency, they will also permit bad frames to propagate out to the Ethernet segments
connected. The “cut-through” technique permits collision fragment frames (which are a
result of late collisions) to be forwarded which add to the network traffic. Since there is no
way to filter frames with a bad CRC (the entire frame must be present in order for CRC to
be calculated), the result of indiscriminate cut-through forwarding is greater traffic
congestion, especially at peak activity. Since collisions and bad packets are more likely
when traffic is heavy, the result of store-and-forward operation is that more bandwidth is
available for good packets when the traffic load is greatest .
When the ML2400 detects that its free buffer queue space is low, the switch sends industry
standard (full-duplex only) PAUSE packets out to the devices sending packets to cause
“flow control”. This tells the sending devices to temporarily stop sending traffic, which
allows a traffic catch-up to occur without dropping packets. Then, normal packet buffering
and processing resumes. This flow-control sequence occurs in a small fraction of a second
and is transparent to an observer.
Another feature implemented in the ML2400 is a collision-based flow-control mechanism
(when operating at half-duplex only). When the switch detects that its free buffer queue
space is low, it prevents more frames from entering by forcing a collision signal on all
receiving half-duplex ports in order to stop incoming traffic.
2.3.3MultiLink Switch Software
The ML2400 includes licensed software, allowing configuration of the ML2400 as a
managed switch.
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.4Redundant 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. the two power
sources are not mixed together by the switch).
When one power supply is present, the ML2400 will receive power even if the other power
supply is absent, or if it is connected with reverse polarity, shorted, or grounded.
If reverse polarity connections should accidentally occur on either input, they will not
damage the ML2400 or power supply (nor will it blow the fuse in the internal power supply)
because of the blocking action of the diodes. This is true even if one input connection is
reversed while the Switch is operating from the other source.
The ML2400 will not receive power (and will not work) when both inputs are simultaneously
absent.
The status of the power supplies can be queried with the
show power
Power supply 1 on the switch is power input A and power supply 2 on the switch is power
input B. For example,
ML2400# show power
Power Input A Good.
Power Input B Good.
The show power command is only available in switches with redundant power supplies.
2.3.5Additional Features and Benefits
• Managed switching for high performance Ethernet LANs: The ML2400 provides
non-blocking (all ports can run at full speed) performance with standard managed
networks software included.
• Switching services includes 802.1p QoS packet prioritization: The ML2400
switching hardware supports QoS, giving packet processing priority to priority
tagged packets according to the IEEE 802.1p standard. For port- and applicationspecific priorities of data, the QoS software may be configured.
• Features fiber-built-in: The ML2400 is designed to include fiber ports and
supports mixes of multi-mode and single-mode, 10/100/1000 Mb speed, full-and
half-duplex, and GBIC fiber connectors. The RJ45 10/100 ports can also be
configured with the mix of port types.
• Relay contacts for monitoring internal power and user-defined software events: Two alarm relay contacts monitor basic operations. One is for hardware
and will signal loss of power internally. The other is software controllable and will
signal user-defined software events such as a security violation.
• Modular design for port flexibility, in a 1U space-saving rack-mount package:
The 1U ML2400 chassis has four slots for port configuration. A family of 4, 6 or 8
port modules allows the user to select the desired mix of port types and speeds.
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. Test reports are available upon request.
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. The ML2400 switches are easily used in a variety of applications,
including MANs (metropolitan area networks) client/server computing, secure VLAN
performance upgrades to departmental networks, and LAN traffic centers requiring Gb
backbone services. The performance characteristic of the ML2400 switches enable them
to interconnect a series of subnets (one subnet per ML2400 port) in a LAN traffic center.
The subnet connections may be via fiber or twisted pair cabling, 100 or 10 Mbps speed,
and full-or half-duplex mode.
The mixed-media capability of the ML2400 is ideal for upgrading existing Ethernet LAN
networks where existing cabling must be accommodated. The fiber media capability is
ideal for integrating future-proof fiber cabling into the LAN structure.
2.4.2ML2400 Switch for a VLAN Application
The MultiLink ML2400 Ethernet Switch can handle VLAN applications and provide security
and performance in Ethernet network centers. A secure VLAN-enabled network is an
administratively configured broadcast domain. The network administrator determines
which ports and nodes belong to certain broadcast domains by setting membership
profiles. The ML2400 VLAN capability can be developed in several types of virtual LANs,
such as port-based or tag-based VLANs.
In an office environment where departments such as Finance, Engineering, R&D, and
Marketing require a secure LAN, the ML2400 VLAN feature will prevent traffic cross-over
among domains and keep sensitive data and information under control. The managed
ML2400 with VLANs capability is ideal for any application where a secure VLAN is required
for multiple departments.
The modularity of the ML2400 makes it an attractive choice for applications with LAN
connections to an multiple site offices. Disparate offices can be easily connected with the
Fiber ports supported by the ML2400 switch. A main NT-based server in a secure area,
protected from earthquake or fire hazards, can be connected to the full duplex Gigabit
fiber port.
Full-duplex future proof fiber media can easily connect long distance subnets and provide
a stable secure network to all applications. The SNMP management capability of the
ML2400 allows the creation of a database of all network 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. The entire network is sharing a higher bandwidth Gigabit-enabled datamining server for the vital database located in a separate secured building. The copper
ports are required for multiple subnets inside the building. The entire spread network will
be manageable to provide easy, detectable, uninterrupted support through a viewable
SNMP monitor.
The MultiLink ML2400 Ethernet Switch equipped with the mix of copper and fiber ports
provides an economical and seamless solution to the requirements. The user-configurable
ML2400 provides an extra boost to the network requirements by providing copper/fiber
media along with the higher bandwidth support of 10/100 and 1000 Mb. The user can
utilize the SNMP feature equipped with VLAN, RMON, SNTP and other standard managed
LAN features to provide a secure and stable network.
The ML2400 managed switch with mixed-media flexibility allows the users more than one
configuration alternative. The user has an advantage by fulfilling the present requirements
as well as benefiting from the multiple choices of modules to support future expansion as
the network evolves. The Gigabit port option boosts the bandwidth for high speed to
support the peak traffic and minimize congestion.
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.Placement of the equipment must not overload or unevenly load the rack
4.Verify the equipment's power requirements to prevent overloading of
5.Verify that the equipment has a reliable and uncompromised grounding path.
6.Equipment is to be installed by service personnel in a restricted operation
This chapter describes installation of the MultiLink ML2400 Ethernet Switch, as well as
connection of the various Ethernet media types.
3.1.2Locating the ML2400
For mounting instructions, refer to Mechanical Installation on page 3–6.
The location of a ML2400 switch is dependent on the physical layout of the network. The
ML2400 is typically placed in a central location where groups of network devices need to
communicate. These switches are typically rack mounted in a wiring closet see Section
3.3.2 below), but because they have rubber feet they can also be installed on a shelf or
table top unit. The compact size allows the ML2400 to be easily placed in an office or lab
area, and it can also be either shelf of wall-mounted (see Section 3.3.1 below).
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.
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 standardMedia typeDistance
100Base-FXmulti-mode fiber220 m
single-mode fiber 5 km
10Base-Ttwisted-pair100 m
100Base-TX100Base-FX100 m
3.2.2Connecting ST-type Fiber Optics (twist-lock)
The following procedure applies to installations using modules with ST-type fiber
connectors. These are type A1, A2, A4, A5, A6, and A7 modules.
Z Before connecting the fiber optic cable, remove the protective dust
caps from the tips of the connectors on the module.
Save these dust caps for future use.
Z Wipe clean the ends of the dual connectors with a soft cloth or lint-
free lens tissue dampened in alcohol.
Ensure the connectors are clean before proceeding.
Note
One strand of the duplex fiber optic cable is coded using color bands at regular intervals.
The color-coded strand must be used on the associated ports at each end of the fiber optic
segment.
Z Connect the transmit (TX) port on the module (light colored post) to
the receive (RX) port of the remote device.
Begin with the color-coded strand of the cable for this first TX-toRX connection.
Z Connect the receive (RX) port on the module (dark colored post) to
the transmit (TX) port of the remote device.
Use the non-color coded fiber strand.
The LINK LED on the module will illuminate when a connection has been
established at both ends (assuming power is ON). If LINK is not lit after cable
connection, the cause may be improper cable polarity. Swap the fiber cables at the
module connector to remedy this situation.
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.4Connecting Single-mode Fiber Optics
When using single-mode fiber cable, be sure to use single-mode fiber port connectors.
Single-mode fiber cable has a smaller diameter than multi-mode fiber cable (9/125
microns for single-mode versus 50/125 or 62.5/125 microns for multi-mode, where xx/xx
represent the core diameters and the core plus cladding, respectively). Single-mode fiber
allows full bandwidth at longer distances and may be used to connect 10 Mb nodes up to
10 km.
The same connection procedures for multi-mode fiber apply to single-mode fiber
connectors. Follow the steps listed Connecting ST-type Fiber Optics (twist-lock) on page 3–3.
3.2.5Connecting RJ45 Twisted Pair
The RJ45 ports of the ML2400 can be connected to the following two media types:
100Base-TX and 10Base-T. CAT Five cables should be used when making 100Base-TX
connections. When the ports are used as 10Base-T ports, CAT.3 may be used. In either
case, the maximum distance for unshielded twisted pair cabling is 100 m (328 ft.).
Note
It is recommended that high quality CAT. 5 cables (which work with 10 Mb and 100 Mb) be
used whenever possible to provide flexibility in a mixed-speed network, as dual-speed
ports are auto-sensing for 10 and 100 Mb/s.
The following procedure describes how to connect a 10Base-T or 100Base-TX twisted pair
segment to the RJ45 port. The procedure is the same for both unshielded and shielded
twisted pair cables.
Z Using standard twisted pair media, insert either end of the cable
with an RJ45 plug into the RJ45 connector of the port.
Even though the connector is shielded, either unshielded or
shielded cables may be used.
Z Connect the other end of the cable to the corresponding device.
Z Use the LINK LED to ensure connectivity by noting that the LED will
be illuminated when the unit is powered and connection is
established.
The ML2400 RJ45 Gigabit ports can be connected to 1000Base-T, CAT.5E (or better), 100 Ω
UTP, or shielded twisted-pair (STP) balanced cable media. The CAT.5E or shielded twisted
pair (STP) balanced cable is recommended when making 1000Base-TX connections. In
either case, the maximum distance for unshielded twisted pair cabling is 100 m (328 ft.).
Note
It is recommended that high quality CAT. 5E cables (which work at both 100 and 1000 Mb)
be used whenever possible to provide flexibility in a mixed-speed network.
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.
Z Connect the other end of the cable to the corresponding device.
Z Use the LINK LED to ensure connectivity by noting that the LED will
be illuminated when the unit is powered and connection is
established.
3.2.6Connecting Gigabit Media using GBICs
The Gigabit ports accept industry-standard GBICs for user selection of the gigabit media
type desired. A selection of fiber and copper GBICs are available.
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.2Rack 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. When properly installed, the front-mounted LED status
indicators should be in plain view and easy to read. Rack-mount installation requires
special 19-inch rack-mounted brackets and screws (included with the ML2400). These
brackets attach to the front sides of the switch, which is then typically fastened into a
standard 19" RETMA rack as shown below.
754733A1.CDR
FIGURE 3–1: Rack mounting
The 23-inch brackets and the ETSI (European metric, approximately 21") brackets are also
available for rack-mounting of the ML2400. These brackets are popular in the
telecommunications industry where they are a standard for central office rack-mounting
purposes. The 23-inch and the ETSI brackets are mainly used for larger equipment
assemblies in rack-mounting frames where the rack-mount equipment is typically
accessed in operation from both sides.
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.
The optional 23" brackets and the ETSI (21") brackets each come as a pair in a package,
along with the necessary screws for attaching the brackets to the sides of the ML2400.
They must be ordered as line items.
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. The power terminals are identified as positive (+), negative (–), and filter ground
( ) for DC power and as live L(+), neutral N(–), and for AC power. These terminals
are floating inside the unit so that either may be grounded by the user if desired. The
chassis or safety ground is the stud located beside the terminal block.
The connection procedure is straightforward. Simply insert DC leads to the ML2400 power
terminal positive (+), negative (–), and or AC leads to the live L(+), neutral N(–), and.
Please ensure the correct polarity. The should be connected to the safety ground,
except during dielectric testing. Ensure that each lead is securely tightened.
FIGURE 3–3: Power connection and alarm contacts
Note
Always use a voltmeter to measure the voltage of the incoming power supply and properly
determine the positive and negative leads.
Note
The GND should be hooked up first. The ML2400 has a floating ground, so the user may
elect to ground either the positive or negative terminal.
When power is applied, the green PWR LED will illuminate.
The ML2400 is available with a redundant power supply option. If the redundant power
supply is ordered, it should be wired as described above. The possible combinations of
redundant power supplies are: HI-HI, HI-LO, LO-HI, and LO-LO. The AC power supply cannot
be supplied with a redundant supply.
3.4.2UL Requirements for DC-Powered Units
1.Minimum 18 AWG cable for connection to a centralized DC power source.
2.Minimum 14 AWG cable for connection to a earthing wiring.
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.Centralized DC power source cable securing; use at least four cable ties to
secure the cable to the rack at least 4 inches apart, with the first one located
within 6 inches of the terminal block.
3.4.3Alarm Contacts
The alarm contacts feature provides two form-A normally closed (NC) contacts to which
the user can attach two sets of status monitoring wires at the green terminal block. When
this option is present, the terminal block for alarm contacts is part of the power input panel
in the ML2400 case. The DC power input connection is in the same panel. A manual on-off
switch for power to the unit is not available on ML2400 units with the alarm contacts
option, as these two features occupy the same space in the case.
The first NC alarm contact (top position) is a “software alarm”, operated by user settings in
the ML2400 software. The user can disable the software alarm feature with a software
configuration command if desired. When the software alarm is enabled, the form-A
normally closed (NC) contact is held close during normal software operation. A userdefined software malfunction, such as an SNMP trap or a software security violation,
causes the contact to open and thus trigger an alarm in the user’s monitoring system
The second (bottom position) NC alarm contact is held closed when there is power on the
main board inside of the ML2400. This provides a “hardware alarm” because the NC
contacts will open when internal power is lost, either from an external power down
condition or by the failure of the ML2400 power supply. For an ML2400 with the redundant
power supply option, the hardware alarm contact will change state if any one of the power
supplies fails.
Useful information about the alarm contacts:
• The four terminal block (1, 2, 3, and 4) is adjacent to the power supply.
• The top two pins (1 and 2) are software operated.
• The bottom two pins (3 and 4) are hardware operated.
• By default, the alarm contacts are NC (normally closed).
• Software operation must be enabled to get the alarm traps. Further information is
provided in this manual.
The green alarm contacts are on the front rear area (next to the power source) of the
ML2400 unit.
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.
3.5Connecting a Management Console Terminal to the ML2400
3.5.1Description
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.
Table 3–2: Console port pin assignment
PinSignalDescription
1CDCarrier detect (not used)
2RXDReceive data (input)
3TXDTransmit data (output)
4opennot used
5GNDSignal ground
6 to 9opennot used
This information enables a management station (PC or console terminal) to connect
directly to the switch console using a straight-through serial cable.
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. All ports can
communicate to other ports in a ML2400, but local traffic on a port will not consume any of
the bandwidth on any other port.
The ML2400 is a plug-and-play device. There is no software configuration necessary for
basic operation, installation, or maintenance. Optional half/full-duplex mode and 10 or
100 Mbps selection for the switched ports must be configured through software as per the
requirement. The internal functions of both are described below.
4.1.2Filtering and Forwarding
Each time a packet arrives on one of the switched ports, the decision is taken to either filter
or to forward the packet. Packets whose source and destination addresses are on the
same port segment will be filtered, constraining them to that one port and relieving the
rest of the network from having to process them. A packet whose destination address is on
another port segment will be forwarded to the appropriate port, and will not be sent to the
other ports where it is not needed. Traffic needed for maintaining the un-interrupted
operation of the network (such as occasional multi-cast packets) are forwarded to all
ports.
The ML2400 operates in the store-and-forward switching mode, which eliminates bad
packets and enables peak performance when there is heavy traffic on the network.
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.4Status LEDs
The following status LEDs are included:
• PWR: Power LED, ON when external power is applied to the unit.
• LK: Steady ON, link status for 10 Mbps and 100 Mbps operation.
• ACT: ON with port activity for 10 Mbps and 100 Mbps operation.
• F/H: Full/half-duplex LED, ON when the port is running full-duplex, OFF for halfduplex.
• 100/10: Speed LED, ON when the speed is 100 Mbps, OFF when the speed is
10 Mbps.
4.1.5Up-link Manual Switches (for RJ45 port only)
The module has a manual up-link switch, located on the inside of the board next to the 10/
100Mb (RJ45) port # 1 which it controls. It enables the port's cable to be cascaded (X) to a
10/100Mb repeater or switching hub in the network. The Up-link Switch position is
configured as (=) straight position by default from the factory settings on all the RJ45 ports,
either used for all copper module or combo module.
4.1.6Auto-Negotiation (for Fast Ethernet Copper Ports)
The managed ML2400 Fast Ethernet copper ports can be set for either fixed 100 Mb speed
or for 10/100 full/half-duplex n-way auto-negotiation per the IEEE802.3u standard. The
selection is made via the ML2400 software. The factory default setting is for autonegotiation. At 10 or 100 Mb fixed speed, the user may select half or full-duplex mode via
software for each RJ45 port.
A common application for the ML2400 copper ports is for connection via a fiber media
converter to another switch in the network backbone (or some other remote 100 Mb
device). In this case, it is desirable to operate the fiber link at 100 Mb, and at either half or
full-duplex mode depending on the capabilities of the remote device. Standard
commercially available Fast Ethernet media converters mostly do not support autonegotiation properly, and require that the switched port to which they are connected be at
100 Mb fixed speed. Attachment to 10/100 auto-negotiation ports typically will not work
properly. The ML2400 RJ45 ports handle this situation by configuring the ports as per the
software port settings and can check the port status of each port after the change.
When the ML2400 copper ports are set for auto-negotiation and are connected to an
auto-negotiating device, there are four speed and F/H modes available, depending on
what the other device supports. These are:
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). If
the device at the other end is not an auto-negotiating device, the ML2400 RJ45 ports will
try to detect its idle signal to determine 10 or 100 speed, and will default to half-duplex at
that speed per the IEEE standard.
Auto-negotiation per-port for 802.3u-compliant switches occurs when:
• Devices at both ends of the cable are capable of operation at 10 Mb or 100 Mb
and/or in full/half-duplex mode, and can send/receive auto-negotiation pulses,
and
• The second of the two connected devices is powered up (i.e., when LINK is
established for a port) or the LINK is re-established on a port after being lost
temporarily.
Note
Some NIC cards only auto-negotiate when the computer system that they are in is
powered up. These are exceptions to the “negotiate at LINK enabled” rule above, but may
be occasionally encountered.
When operating in 100 Mb half-duplex mode, cable distances and hop-counts may be
limited within that collision domain. The Path Delay Value (PDV) bit-times must account for
all devices and cable lengths within that domain. For MultiLink fast Ethernet switched ports
operating at 10 0Mb half-duplex, the bit time delay is 50BT.
4.1.7Flow Control (IEEE 802.3x)
The ML2400 incorporates a flow-control mechanism for full-duplex mode. Flow-control
reduces the risk of data loss if a long burst of activity causes the switch to save frames
until its buffer memory is full. This is most likely to occur when data is moving from a
100 Mb port to a 10 Mb port and the 10 Mb port is unable to keep up. It can also occur
when multiple 100 Mb ports are attempting to transmit to one 100 Mb port , and in other
protracted heavy traffic situations.
The ML2400 implements the 802.3x flow control (non-blocking) on full-duplex ports, which
provides for a “PAUSE” packet to be transmitted to the sender when the packet buffer is
nearly filled and there is danger of lost packets. The transmitting device is commanded to
stop transmitting into the ML2400 port for sufficient time to let the Switch reduce the
buffer space used. When the available free-buffer queue increases, the Switch will send a
“RESUME” packet to tell the transmitter to start sending the packets. Of course, the
transmitting device must also support the 802.3x flow control standard in order to
communicate properly during normal operation.
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.
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:
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:
1.The 100 Mb fiber segment must operate in full-duplex (FDX) mode (i.e. the fullduplex (factory default).
2.The worst-case OPB of the fiber link must be greater than the fiber cable's
passive attenuation, where attenuation is the sum of cable loss, LED aging
loss, insertion loss, and safety factor.
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. However, if you are unsure of the procedures
described in this section or if the ML2400 is not performing as expected, do not attempt to
repair the unit; instead contact your supplier for assistance or contact GE Multilin.
4.2.2Before Calling for Assistance
1.If difficulty is encountered when installing or operating the unit , refer to
chapter 2. Also ensure that the various components of the network are
interoperable.
2.Check the cables and connectors to ensure that they have been properly
connected and the cables/wires have not been crimped or in some way
impaired during installation (about 90% of network downtime can be
attributed to wiring and connector problems.)
3.If the problem is isolated to a network device other than the ML2400, it is
recommended that the problem device be replaced with a known good
device. Verify whether or not the problem is corrected. If not, go to the next
step. If the problem is corrected, the ML2400 and its associated cables are
functioning properly.
4.If the problem continues after completing the previous step, contact GE
Multilin.
4.2.3When Calling for Assistance
Please be prepared to provide the following information:
1.A complete description of the problem, including the following: the nature and
duration of the problem, situations when the problem occurs, the components
involved in the problem, and any particular application that appears to create
the problem.
2.An accurate list of GE product model(s) involved, with serial number(s). Include
the date(s) that you purchased the products from your supplier.
3.It is useful to include other network equipment models and related hardware,
including personal computers, workstations, terminals and printers; plus, the
various network media types being used.
4.A record of changes that have been made to your network configuration prior
to the occurrence of the problem. Any changes to system administration
procedures should all be noted in this record.
It is assumed that the user has familiarity with IP addresses, classes of IP addresses and
related netmask schemas (for example, class A, B, and C addressing).
Without an IP address, the switch operates as a standalone Layer 2 switch. Without an IP
address, you cannot:
• Use the web interface to manage the switch
• Use telnet to access the CLI
• Use any SNMP Network Management software to manage the switch
• Use NTP protocol or an NTP server to synchronize the time on the switch
• Use TFTP or FTP to download the configurations or upload software updates
• Run ping tests to test connectivity
To set the IP address, please refer to Setting the IP Parameters on page 1–12. Once the IP
address is set, the CLI can be accessed via telnet as well as the console interface. From
now on, all commands discussed are accessible from the command line interface,
irrespective of access methods (i.e. serial port or in band using telnet).
To verify the IP address settings using the command line interface, the
command can be used as follows:
ML2400> show ipconfig
IP Address:3.94.247.41
Subnet Mask:255.255.252.0
Default Gateway: 3.94.244.1
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.
DHCP is commonly used for setting up addresses for computers, users and other user
devices on the network. bootp is the older cousin of DHCP and is used for setting up IP
addresses of networking devices such as switches, routers, VoIP phones and more. Both of
them can work independent of each other. Both of them are widely used in the industry. It's
best to check with your network administrator as to what protocol to use and what the
related parameters are. DHCP and bootp require respective services on the network. DHCP
and bootp can automatically assign an IP address. It is assumed that the reader knows
how to setup the necessary bootp parameters (usually specified on Linux/UNIX systems in
the
/etc/boopttab directory).
5.2.2bootp Database
Bootp keeps a record of systems supported in a database - a simple text file. On most
systems, the
entry by which the
and subnet mask of the switch would be as follows:
bootp service is not started as a default and has to be enabled. A sample
bootp software will look up the database and update the IP address
ML2400 is a user-defined symbolic name for the switch.
•
•
ht is the hardware type. For the MultiLink family of switches, set this to ether (for
Ethernet). This tag must precede the
ha is the hardware address. Use the switch's 12-digit MAC address.
•
•
ip is the IP address to be assigned to the switch.
sm is the subnet mask of the subnet in which the switch is installed.
•
Each switch should have a unique name and MAC address specified in the
entry
5.2.3Configuring DHCP/bootp/Manual/AUTO
By default, the switch is configured for auto IP configuration. DHCP/bootp/manual can be
enabled with the command line interface by using the
following syntax:
set bootmode=<dhcp|bootp|manual|auto> bootimg=<enable|disable>
bootcfg=<enable|disable>
The bootimg argument is only valid with the bootp type. This option allows the switch to
load the image file from the bootp server. This is useful when a new switch is placed on a
network and the IT policies are set to load a specific image which is supported and tested
by IT personnel.
Likewise, the
bootcfg argument is valid only with the bootp type. This option allows the
switch to load the configuration file from the bootp server. This is useful when a new
switch is put on a network and the specific conf igurations are loaded from a centralized
bootp server
The following example changes the boot mode of the switch:
ML2400# set bootmode type=bootp bootimg=enable bootcfg=disable
Network application image download is enabled.
Network application config download is disabled.
Save Configuration and Restart System
ML2400#
Alternatively, the DHCP/bootp/manual can be enabled through the EnerVista Secure Web
Management software as shown below.
Z Select the Administration > System menu item.
Z Click Edit.
Z Alternatively, select items in the Administration > Set menu to
individually modify the boot mode, date and time, log size, etc.
Z After the changes are completed for each section, click OK to
register the changes.
5.2.4Using Telnet
Note that if the IP address is changed, the
http session has to be restarted with the new IP
address.
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. This is also useful when two remote users
want to view the switch settings. The telnet client can be disabled through the command
line interface by using the
telnet disable command with the following syntax:
telnet <enable|disable>
Telnet can also be disabled for specific users with the
useraccess command. Refer to
User Management on page 1–14 for details.
Multiple telnet sessions started from the CLI interface or the command line are serviced by
the ML2400 in a round-robin fashion (that is, one session after another). If one telnet
session started from an ML2400 is downloading a file, the other windows will not be
serviced until the file transfer is completed.
The following example changes the telnet access. In this case, the enable command was
repeated without any effect to the switch.
ML2400# configure access
ML2400(access)##
Access to Telnet already enabled
ML2400(access)## exit
ML2400#
telnet enable
The show console command can show the status of the telnet client as well as other
console parameters. The following example reviews the console parameters with the
Users can telnet to a remote host from the MultiLink family of switches using the following
syntax.
telnet <ipaddress> [port=<port number>]
The default port for telnet is 23.
To start a telnet session through the EnerVista Secure Web Management software,
Z Select the Administration > Telnet menu item.
The default port for telnet is 23.
The ML2400 will time out an idle telnet session. It may be useful to see who is currently
connected to the switch. It may also be useful for a person to remotely terminate a telnet
session. To facilitate this, the ML2400 supports the following two commands:
SL# Sessn Id ConnectionUser Name User Mode
11163.10.10.14 managerManager
22163.11.11.1peterManager
33163.12.12.16 operatorOperator
ML2400#
Session Terminated
ML2400#
kill session id=3
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
operator session is then terminated using the
show session command. The user
kill session command.
Note
A maximum of four simultaneous telnet sessions are allowed at any time on the switch.
The commands in these telnet windows are executed in a round robin fashion; that is, if
one window takes a long time to finish a command, the other windows may encounter a
delay before the command is completed. For example, if one window is executing a file
download, the other windows will not be able to execute the command before the file
transfer is completed. As well, if a outbound telnet session is started from the switch
(through a telnet window) then other windows will not be able to execute a command until
the telnet session is completed.
To be compliant with IT or other policies the console parameters can be changed from the
CLI interface. This is best done by setting the IP address and then telnet over to the switch.
Once connected using telnet, the serial parameters can be changed. If you are using the
serial port, remember to set the VT-100 emulation software properties to match the new
settings.
The serial port parameters are modified using the
set serial command with the
following syntax:
set serial [baud=<rate>] [data=<5|6|7|8>] [parity=<none|odd|even>]
[stop=<1|1.5|2>] [flowctrl=<none|xonxoff>]
Where <rate> = standard supported baud rates.
Note
Changing these parameters through the serial port will cause loss of connectivity. The
terminal software parameters (e.g. HyperTerminal) will also have to be changed to match
the new settings.
To see the current settings of the serial port, use the
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.com
System Location: Markham, Ontario
Boot Mode: manual
Inactivity Timeout(min): 120
Address Age Interval(min): 300
Inbound Telnet Enabled: Yes
Web Agent Enabled: Yes
Time Zone: GMT-05hours:00minutes
Day Light Time Rule: Canada
System UpTime: 7 Days 12 Hours 30 Mins 46
Secs
ML2400#
System variables can be changed. Below is a list of system variables which GE
recommends changing.
•
System Name: Using a unique name helps you to identify individual devices in a
network.
System Contact and System Information: This is helpful for identifying the
•
administrator responsible for the switch and for identifying the locations of
individual switches.
To set these variables, change the mode to be SNMP configuration mode from the
manager mode using the following syntax
The following command sequence sets the system name, system location and system
contact information.
5.3.3Date and Time
It may be necessary to set the day, time or the time zone manually. This can be done by
using the
syntax:
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.
ML2400# set time hour=8 min=10 sec=0 zone=GMT-5:00
Success in setting device time
ML2400# show time
Time: 8:10:04
ML2400# show timezone
Timezone: GMT-05hours:00minutes
ML2400# set date year=2005 month=5 day=11
Success in setting device date
ML2400# show date
System Date: Wednesday 15-11-2005 (in mm
-dd-yyyy format)
ML2400#
The syntax for other date and time commands are:
set timeformat format=<12|24>
set daylight country=<country name>
The following command sequence sets the daylight location:
ML2400# set daylight country=Canada
Success in setting daylight savings to the
given location/country Canada
ML2400# show daylight
Daylight savings location name: Canada
ML2400#
The date and time can only be set through the command line interface software.
5.3.4Network Time
Many networks synchronize the time using a network time server. The network time server
provides time to the different machines using the Simple Network Time Protocol (SNTP). To
specify the SNTP server, one has to
1.Set the IP parameters on the switch
2.Define the SNTP parameters
To set the SNTP parameter with the command line software, enter the SNTP configuration
mode from the manager. The
setup the time synchronization automatically from the SNTP server. Note it is not sufficient
to setup the SNTP variables. Make sure to setup the synchronization frequency as well as
enable SNTP. The syntax for the above commands is shown below.
setsntp, sync, and sntp commands can then be used to
CHAPTER 5: IP ADDRESSINGIP 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)##
SNTP server is added to SNTP server
database
setsntp server=3.94.210.5 timeout=3 retry=3
ML2400(sntp)## sync hour=5
ML2400(sntp)##
SNTP is already enabled.
sntp enable
ML2400(sntp)## exit
ML2400(sntp)#
SNTP parameters can be configured through the EnerVista Secure Web Management
software with the Configuration > SNTP menu item. The SNTP menu allows the time zone
(hours from GMT) to be defined along with other appropriate parameters on setting the
time and synchronizing clocks on network devices.
The edit button allows editing of the SNTP parameters as shown below. Adding or deleting
SNTP servers is accomplished by using the add and delete buttons. Clicking the edit button
allows the specific SNTP parameter settings to be modified.
After the proper SNTP values are entered, click OK to register the changes, or click Cancel
to back out from the changes made.
To add an SNTP server, click the add button on the Configuration > SNTP menu. The menu
prompts you to add IP address of an SNTP server, the time out in seconds and the number
of retries, before the time synchronization effort is aborted. The Sync Now button allows
synchronization as soon as the server information is added.
Note
If your site has internet access, there are several SNTP servers available online. A quick
search will yield information about these servers. You can use the IP address of these
servers; however, please ensure the server can be reached by using the
The
ping command can also be launched from the EnerVista software.
ping command.
The Time Out value is in seconds. Note the time server can be a NTP server available on
the Internet. Ensure the IP parameters are configured for the switch and the device can be
pinged by the switch. Once the server is added, it is listed with the other SNTP servers.
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.
Configuration changes are automatically registered but not saved; that is, the effect of the
change is immediate. However, if power fails, the changes are not restored unless they
saved using the
save command. It is also a good practice to save the configuration on
another network server using the tftp or ftp protocols. Once the configuration is saved, it
can be loaded to restore the settings. At this time, the saved configuration parameters are
not in a human readable format. The commands for saving and loading configurations on
the network are:
Ensure the machine specified by the IP address has the necessary services running. For
serial connections, x-modem or other alternative methods can be used. In most situations,
the filename must be a unique, since overwriting files is not permitted by most ftp and tftp
servers (or services). Only alphanumeric characters are allowed in the filename.
The following example illustrated how to save the configuration on a tftp server
Do you wish to upload the configuration?
['Y' or 'N'] Y
The saveconf and loadconf commands are often used to update software. Before the
software is updated, it is advised to save the configurations. The re-loading of the
configuration is not usually necessary; however, in certain situations it maybe needed and
it is advised to save configurations before a software update. The
loadconf command
requires a reboot for the new configuration to be active. Without a reboot the older
configuration is used by the MultiLink family of switches.
The
saveconf and loadconf commands are often used to update software to the
ML2400. These commands will be deprecated in the upcoming release and replaced with
the
ftp, tftp, or xmodem commands. It is advised to begin using these commands
instead of
saveconf and loadconf.
5.4.2Config file
MNS can now use the ftp or tftp (or xmodem if using the CLI) to upload and download
information to a server running the proper services. One useful capability provided in MNS
is export of the CLI commands used to configure the switch. To do this, use Config Upload/
Download.
Using Config Download, examination of the contents of the saved file would appear as
shown below:
<ML2400 -conf-1.0>
################################################################
# Copyright (c) 2001-2005 GE Multilin, Inc All rights reserved.
# RESTRICTED RIGHTS
# ---------------------------------
# Use, duplication or disclosure is subject to U.S. Government
# restrictions as set forth in Sub-division (b)(3)(ii) of the
# rights in Technical Data and Computer Software clause at
# 52.227-7013.
#
# This file is provided as a sample template to create a backup
# of GE MultiLink switches. As such, this script
# provides insights into the configuration of GE MultiLink
# switches settings. GE 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.
# All modifications are made at the User's own risk and are
# subject to the limitations of the GE MultiLink software End User
# License Agreement (EULA). Incorrect usage may result in
# network shutdown. GE Multilin, Inc. is not liable for incidental or
# consequential damages due to improper use.
################################################################
***This is a Machine Generated File.
***Only the SYSTEM config block is editable.
***Editing any other block will result in error while loading.
##########################################################
# Hardware Configuration - This area shows the type of #
# hardware and modules installed. #
##########################################################
[HARDWARE]
type=ML2400
slotB=8 Port TP Module
##########################################################
# System Manager - This area configures System related #
# information. #
##########################################################
1.A config file allows only certain portions of the file to be edited by a user. Changing
any other part of the file will result in the system not allowing the file to be loaded, as
the CRC computed and stored in the file would not be matched. Should you want to
edit, edit the System portion of the file only. GE Multilin, Inc. recommends editing the
“script” file (see below)
2.File names cannot have special characters such as *#!@$^&* space and control
characters.
Using SWM, the need to display specific CLI commands for configuring capabilities is not
needed. The menus are modular and are alphabetically sorted to display each necessary
component in a logical manner. This section is repeated from the CLI manual, should the
need arise to view the necessary commands. The best way to view these commands is to
telnet to the switch using the Telnet menu from the Administration menu.
To display the configuration or to view specific modules configured, the ‘show config’
command is used as described below.
Syntaxshow config [module=<module-name>]
Where module-name can be:
NameAreas affected
system
event Event Log and Alarm settings
port Port settings, Broadcast Protection and QoS settings
bridge Age time setting
stp STP, RSTP and LLL settings
ps Port Security settings
mirror Port Mirror settings
sntp SNTP settings
llan VLAN settings
gvrp GVRP settings
snmp SNMP settings
web Web and SSL/TLS settings
tacacs TACACS+ settings
auth 802.1x Settings
igmp IGMP Settings
smtp SMTP settings
IP Configuration, Boot mode, Users settings (e.g. login
names, passwords)
If the module name is not specified the whole configuration is displayed.
It is advisable to save the configuration before updating the software, as it may be
necessary in certain situations. The loadconf command requires a reboot to activate the
new configuration. Without a reboot, the ML2400 used the previous configuration. When
reboot is selected, the user is prompted as follows:
Reboot? ['Y' or 'N']
Select “Y”. The ML2400 will prompt:
Save Current Configuration?
Select “N”.
FIGURE 5–4: Displaying configuration for different modules.
Note – multiple modules can be specif ied on the command line
type:Specifies whether a log file or host file is uploaded or downloaded. This can also
perform the task of exporting a configuration file or uploading a new image to
the switch
host, ip, file, user, pass: These parameters are associated with ftp/tftp server
communications.
The user can save the configuration in old (v2 format) and new (v3 format). The v3 format
must be used to utilize the ASCII and CLI Script capability.
save [format=v2|v3]
Note
With release 1.7 and higher, the configuration can be saved in the older format (binary
object) or in a new format as an ASCII file. The new format is recommended by GE Multilin.
Use the old format only if there are multiple MultiLink switches on the network running
different versions of software. GE Multilin recommends upgrading all switches to the most
current software release.
To ease the process of uploading and executing a series of commands, the ML2400 can
create a host (equivalent to creating a host table on many systems). The command for
creating a host is:
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.
recommends that modifications of this file and the commands should be verified by the
user in a test environment prior to use in a "live" production network.
The script file will look familiar to people familiar with the CLI commands as all the
commands saved in the script file are described in the CLI User Guide. A sample of the
script file is shown below.
###############################################################
#
# Copyright (c) 2001-2005 GE Multilin, Inc All rights reserved.
# RESTRICTED RIGHTS
# ---------------------------------
# Use, duplication or disclosure is subject to U.S. Government
# restrictions as set forth in Sub-division (b)(3)(ii) of the
# rights in Technical Data and Computer Software clause at
# 52.227-7013.
#
# This file is provided as a sample template to create a backup
# of GE MultiLink switches configurations. As such,
# this script provides insights into the configuration of GE MultiLink switch's settings.
# GE 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.
# All modifications are made at the User's own risk and are
# subject to the limitations of the GE MultiLink MNS End User
# License Agreement (EULA). Incorrect usage may result in
# network shutdown. GE Multilin, Inc. is not liable for incidental or
# consequential damages due to improper use.
###############################################################
#
##########################################################
# System Manager - This area configures System related #
# information. #
##########################################################
set bootmode type=manual
ipconfig ip=192.168.5.5 mask=0.0.0.0 dgw=0.0.0.0
set timeout=10
access
telnet enable
snmp enable
web=enable
exit
##########################################################
# User Accounts - This area configures user accounts for #
# accessing this system. #
##########################################################
user
add user=manager level=2
passwd user=manager
manager
<additional lines deleted for succinct viewing>
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.6Saving and Loading – EnerVista Software
Note
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.
After configuration changes are made, all the changes are automatically saved. It is a
good practice to save the configuration on another server on the network using the
or
ftp protocols. Once the configuration is saved, the saved configuration can be reloaded
tftp
to restore the settings. At this time, the saved or loaded configuration parameters are not
in a human readable format.
The following figure illustrates the FTP window, which can be used to save the
configuration, as well as up load new images or reload a saved configuration.
Ensure the machine specified by the IP address has the necessary services running on it .
For serial connections, x-modem or other alternative methods can be used. Generally, the
filename name must be a unique filename, as over-writing files is not permitted by most
FTP and TFTP servers (or services).
The following figure illustrates saving the configuration on a TFTP server. Note that the
menu is similar to the FTP screen described earlier.
This process can also be used to update new software to the managed MultiLink switches.
Before the software is updated, it is advised to save the configurations. Reloading of the
configuration is not usually necessary, but in certain situations it may be needed, and it is
recommended that you save configurations before a software update. Make sure to
reboot the switch after a new configuration is loaded.
The file transfer operations allowed are:
1.Image Download (or Image Upload): Copy the ML2400 image from switch to
the server (or from the server to the switch). The “Image Upload” option is
commonly used to upgrade the ML2400 image on the switch.
2.Config Download (or Config Upload): Save the configuration of the switch on
the server (or load the saved configuration from the server to the switch). This
option is used to save a backup of the ML2400 configuration or restore the
configuration (in case of a disaster.)
3.Script Download (or Script Upload): Save the necessary CLI commands used
for configuration of the switch (or upload the necessary CLI commands
needed to configure the switch). This option is used to ease the repetitive task
of configuring multiple commands or reviewing all the commands needed to
configure the ML2400.
4.Host Download (or Host Upload): Save the host information. The hosts are
created by the Configuration - Access - Host commands
5.Log Upload - Save the log file on the ftp/tftp server
To save any changes,
Z Click on the save () icon.
The software will ask again if the changes need to be saved or
ignored.
Z If the changes need to be ignored, click on Cancel and reboot the
switch.
Z If the changes need to be saved, click on OK.
The following figures illustrate saving changes made after adding an SNTP server. This is
done by clicking on the Save icon to save current configuration
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.
Z To delete or edit the entries, use the delete or edit icons next to
each entry shown above.
5.4.8Erasing 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.
In the example below “system” module box has been checked. In this case after kill Config
command is issued by pressing the OK button, the Switch will perform a factory dump
restoring all the Switch settings back to factory defaults except for the “System” settings
which will be retained.
When the OK button is pressed the Switch will issue the following warning messages; and
reboot the switch for it to revert back to the factory default settings with the exceptions of
modules opted not to be defaulted.
This command is a “hidden command”; that is, the on-line help and other help functions
normally do not display this command. The syntax for this command is:
kill Config
or
kill config save=module command
The kill Config command will default all the Switch settings back to factory defaults, while
the kill config save=module will default all with the exception of module selected.
Available modules are: system, user, acces, port, vlan, ps, mirror, lacp, slp, and igmp.
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.
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.1Introduction to IPv6
IPv6 is short for "Internet Protocol Version 6". IPv6 is the "next generation" protocol or IPng
and was recommended to the IETF to replace the current version Internet Protocol, IP
Version 4 ("IPv4"). IPv6 was recommended by the IPv6 (or IPng) Area Directors of the
Internet Engineering Task Force at the Toronto IETF meeting on July 25, 1994 in RFC 1752:
The Recommendation for the IP Next Generation Protocol. The recommendation in
question, was approved by the Internet Engineering Steering Group and a proposed
standard was created on November 17, 1994. The core set of IPv6 protocols was created
as an IETF draft standard on August 10, 1998.
IPv6 is a new version of IP, designed to be an evolutionary step from IPv4. It is a natural
increment to IPv4. It can be installed as a normal software upgrade in internet devices and
is interoperable with the current IPv4. Its deployment strategy is designed to have no
dependencies. IPv6 is designed to run well on high performance networks (e.g. Gigabit
Ethernet, OC-12, ATM, etc.) and at the same time still be efficient on low bandwidth
networks (e.g. wireless). In addition, it provides a platform for the new level of internet
functionality that will be required in the near future.
IPv6 includes a transition mechanism designed to allow users to adopt and deploy it in a
highly diffuse fashion, and to provide direct interoperability between IPv4 and IPv6 hosts.
The transition to a new version of the Internet Protocol is normally incremental, with few or
no critical interdependencies. Most of today's internet uses IPv4, which is now nearly
twenty years old. IPv4 has been remarkably resilient in spite of its age, but it is beginning
to have problems. Most importantly, there is a growing shortage of IPv4 addresses, which
are needed by all new machines added to the Internet.
IPv6 fixes a number of problems in IPv4, such as the limited number of available IPv4
addresses. It also adds many improvements to IPv4 in areas such as routing and network
auto configuration. IPv6 is expected to gradually replace IPv4, with the two coexisting for a
number of years during the transition period.
5.5.2What’s changed in IPV6?
The changes from IPv4 to IPv6 fall primarily into the following categories:
• Expanded Routing and Addressing Capabilities – IPv6 increases the IP address size
from 32 bits to 128 bits, to support more levels of addressing hierarchy, a much
greater number of addressable nodes, and simpler auto-configuration of
addresses. The scalability of multicast routing is improved by adding a "scope"
field to multicast addresses.
• A new type of address called an "anycast address" is defined, that identifies sets of
nodes where a packet sent to an anycast address is delivered to one of these
nodes. The use of anycast addresses in the IPv6 source route allows nodes to
control the path along which their traffic flows.
• Header Format Simplification - Some IPv4 header fields have been dropped or
made optional, to reduce the common-case processing cost of packet handling
and to keep the bandwidth cost of the IPv6 header as low as possible despite the
increased size of the addresses. Even though the IPv6 addresses are four times
longer than the IPv4 addresses, the IPv6 header is only twice the size of the IPv4
header.
• Improved Support for Options - Changes in the way IP header options are encoded
allow more efficient forwarding, less stringent limits on the length of options, and
greater flexibility for introducing new options in the future.
• Quality-of-Service Capabilities - A new capability is added to enable the labeling of
packets belonging to particular traffic "flows" for which the sender requests
special handling, such as non-default quality of service or "real- time" service.
• Authentication and Privacy Capabilities - IPv6 includes the definition of extensions
which provide support for authentication, data integrity, and confidentiality. This is
included as a basic element of IPv6 and will be included in all implementations.
5.5.3IPv6 Addressing
IPv6 addresses are 128-bits long and are identifiers for individual interfaces and sets of
interfaces. IPv6 addresses of all types are assigned to interfaces, not nodes. Since each
interface belongs to a single node, any of that node's interface’s unicast addresses may be
used as an identifier for the node. A single interface may be assigned multiple IPv6
addresses of any type.
There are three types of IPv6 addresses. These are unicast, anycast, and multicast. Unicast
addresses identify a single interface. Anycast addresses identify a set of interfaces such
that a packet sent to an anycast address will be delivered to one member of the set.
Multicast addresses identify a group of interfaces, such that a packet sent to a multicast
address is delivered to all the interfaces in the group. There are no broadcast addresses in
IPv6. This function has been replaced by multicast addresses.
IPv6 supports addresses which are four times the number of bits as IPv4 addresses (128 vs.
32). This is 4 Billion x 4 Billion x 4 Billion (296) times the size of the IPv4 address space (232).
This works out to be:
This is an extremely large address space. In a theoretical sense this is approximately
665,570,793,348,866,943,898,599 addresses per square meter of the surface of the planet
Earth (assuming the earth surface is 511,263,971,197,990 square meters). In the most
pessimistic estimate this would provide 1,564 addresses for each square meter of the
surface of Earth. The optimistic estimate would allow for 3,911,873,538,269,506,102
addresses for each square meter of the surface Earth. Approximately fifteen percent of
the address space is initially allocated. The remaining 85% is reserved for future use.
Details of the addressing are covered by numerous articles on the WWW as well as other
literature, and are not covered here.
5.5.4Configuring 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
Syntaxping6 <IPv6 address> - pings an IPv6 station.
There is also a special command to ping the status of IPv6. That command is
Syntaxshow ipv6 - displays the IPv6 information.
To configure IPv6, the following sequence of commands can be used:
ML2400# ipconfig ?
ipconfig : Configures the system IP address, subnet mask and gateway
Syntaxtelnet <IPv6 address> - telnet to an IPv6 station
Example – telnet fe80::220:6ff:fe25:ed80
Besides, if the end station supports IPv6 addressing (as most Linux and Windows systems
do), one can access the switch using the IPv6 addressing as shown in the example below
http://fe80::220:6ff:fe25:ed80
5.5.5List of commands in this chapter
Syntax ipconfig [ip=<ip-address>] [mask=<subnet-mask>] [dgw=<gateway>] [add|del]
– configure an IPv6 address. The add/delete option can be used to add or delete IPv4/IPv6
addresses.
Syntax show ipconfig – display the IP configuration information – including IPv6 address
Syntax ping6 <IPv6 address> - pings an IPv6 station
Syntax show ipv6 - displays the IPv6 information
Syntax ftp <IPv6 address> - ftp to an IPv6 station
Syntax telnet <IPv6 address> - telnet to an IPv6 station.