Back to Contents Page
Connecting Network Devices
Connecting for Management
The switch is designed to interconnect multiple segments (or collision domains). The Gigabit Ethernet uplink ports on the switch's bracket can be connected to Gigabit Ethernet or 10/100 Fast Ethernet switches, network interface cards (NICs), or routers. For network applications that require routing (such as when interconnecting dissimilar network types or distinct VLANs), you should attach the switch directly to a router or Layer 3 switch.
To connect to an uplink port, use Category 5 unshielded twisted-pair (UTP) cable with RJ-45 connectors at both ends. The RJ-45 ports on the switch support automatic Media-Dependent Interface / Media-Dependent Interface, with internal crossover wiring (MDI/MDI-X) operation under auto-negotiation mode, so you can use standard straight-through twisted-pair cables to connect to any other network device (systems, servers, switches or routers) that supports auto-negotiation.
If the uplink ports are configured in forced mode, reference the following table for cabling with NICs or switches.
MDI port of the link partner
(Uplink port of a 3rd party switch, or NIC )
MDI-X port of the link partner
(Normal port of a 3rd party switch)
|Uplink port of the switch||X||=|
|NOTE: "X" denotes crossover cable; "=" represents straight-through cable.|
See Pin Assignments for further information on cabling.
|CAUTION: Do not plug a phone jack connector into an RJ-45 port. This will damage the switch. Use only twisted-pair cables with RJ-45 connectors that conform to FCC standards.|
For advanced management capability, the onboard management agent provides a command line configuration interface. This program can be accessed by a direct connection to the RJ-11 console port on the switch or the DB-9 console port on the remote access module (i.e., management card), or remotely by a Telnet connection over the network.
|NOTE: The IP address for this switch is assigned via Dynamic Host Configuration Protocol (DHCP) by default. To set this address, see Setting an IP Address.|
The management agent is based on Simple Network Management Protocol (SNMP). This SNMP agent permits the switch to be managed from any system in the network using SNMP-based systems management software.
The management agent also includes an embedded Hypertext Transfer Protocol (HTTP) Web agent. This Web agent can be accessed using a standard Web browser from any computer attached to the network.
The system configuration program and the SNMP agent support management functions such as:
There are two options for Console Port connections. One is through the remote access module in the chassis. The other is via the on-board RJ-11 port of the integrated switch. The default option is for the console port on the remote access module. However, this can be changed via the jumper configuration. Remove the switch from the chassis. Locate a three-pin jumper named JP6 which is located betweem two heat sinks. Set this jumper to Pins 1 and 2 (i.e., the left two pins) to select the console port on the remote access module, or to Pins 2 and 3 (i.e., the right two pins) to select the the console port on the switch. By default, the jumper is connected to Pins 1 and 2 to select the console port on the remote access module.
Refer to the the remote access module's user manual for information on connecting to this port.
The switch provides an RJ-11 port that enables a connection to a system or terminal for monitoring and configuring the switch. A DB-9-to-RJ-11 cable is provided with the switch. Use these items to attach a VT100 compatible terminal, or a system running a terminal emulation program to the switch. You can use the cable provided with this package, or use a cable that complies with the wiring assignments shown in RJ-11 Console Port.
To connect a terminal to the console port, complete the following steps:
|NOTE: When using HyperTerminal with Microsoft® Windows® 2000, make sure that you have Windows 2000 Service Pack 2 or later installed. Windows 2000 Service Pack 2 fixes the problem of arrow keys not functioning in HyperTerminals VT100 emulation. See www.microsoft.com for information on Windows 2000 service packs.|
|NOTE: Refer to Line Commands for a complete description of console configuration options.|
4. Once you have set up the terminal correctly, the console login screen will be displayed.
For a description of how to use the Command Line Interface (CLI), see Using the CLI. For information on CLI commands used for common tasks, see Using the Switch. For a list of all the CLI commands and detailed information on using the CLI, refer to the Command Line Reference.
Prior to accessing the switchs onboard agent via a network connection, you must first configure it with a valid IP address, subnet mask, and default gateway using a console connection, DHCP or Boot Protocol (BOOTP) protocol.
|NOTE: The IP address for this switch is assigned via DHCP by default. To manually configure this address or enable dynamic address assignment via DHCP or BOOTP, see Setting an IP Address.|
|NOTE: This switch supports four concurrent Telnet sessions.|
NOTE: Do not connect the Ethernet port on the remote management module, i.e., management card and the integrated switch's uplink ports to the same external switch or to the same subnet, otherwise a bridged loop may be formed, overloading the network. If you connect both port types to the same device or subnet, then you must enable Spanning Tree Protocol on the integrated switch. However, the Spanning Tree Protocol may disable one of the these ports to avoid a loop, and the management card's Ethernet port will probably be disabled because the Spanning Tree Protocol gives priority to higher speed ports.
After configuring the switchs IP parameters, you can access the onboard configuration program from anywhere within the attached network. The onboard configuration program can be accessed using Telnet from any computer attached to the network. The switch can also be managed by any computer using a Web browser (Internet Explorer 5.0 or above, or Netscape Navigator 6.2 or above), or from a network computer using SNMP-based systems management software.
|NOTE: The onboard program only provides access to basic configuration functions. To access the full range of SNMP management functions, you must use SNMP-based systems management software.|
The switch contains three firmware components: Loader, Diagnostics, and Runtime operation code. The firmware can be upgraded via a standard serial console port, via a network connection to a Trivial File Transfer Protocol (TFTP) server, or using SNMP management software.
You can upgrade all three firmware components by connecting your computer to the serial (COM) port on the switch and using a console interface package that supports the XModem protocol. (See Required Connections.)
Download the required firmware type.
|NOTE: The download file must be a PowerEdge 1655MC binary software file from Dell.|
|NOTE: You can only store two runtime code files on the switch. Use the dir command to check the contents of the switch file system, and use the delete command to remove all but one runtime code file from the system before continuing.|
When using Windows HyperTerminal, click the "Transfer" button,
click "Send File...," select the required file from your system,
select XModem Protocol, and then click "Send." The "Xmodem
send file for COM port" will display the progress of the download procedure.
After the file has been downloaded, the following screen text will display:
Image downloaded to buffer..........OK
[L]oader (Warning: you sure what you are doing?)
Update Image File:
TFTP can only upgrade the runtime code or configuration file. (See Switch/Firmware Page.) To download other firmware types (including diagnostics or loader) use the command line interface or SNMP.
|NOTE: Downloading runtime code via TFTP is much faster than downloading via the switch's serial port.|
Back to Contents Page