User guide

3: Installing the Spider
SecureLinx Spider/SpiderDuo User Guide 31
Cable Connections for KVM and USB
Connections for KVM and USB are integrated into the Spider. Do not use extension cables. Plug
the Spider directly into the ports on the host server. If using the Spider serial port, plug the cable
into the COM port on the server.
The second Cascade Ethernet port can connect to the Spider to the target computer management
LAN port, or to a main LAN port, or to an Spider chain. When connecting the Ethernet ports,
straight through or crossover cables can be used, because the Spider has auto-polarity and auto-
crossover correction. Although the port marked Ethernet and the port marked Cascade are both
Ethernet interfaces, you must use the port marked Ethernet if using only one Ethernet interface.
Perform the following steps when daisy chaining Spider devices.
1. Plug the outside network cable into the left Ethernet port of the first Spider.
2. Connect the right Cascade port to the left port of the next Spider in the chain.
3. Repeat as necessary. The last Spider in the chain should have its right port unoccupied,
unless cabling in a loop for redundant connection.
Device Failure or Cable Break in the Daisy Chain
If a device fails or there is a cable break in the daisy chain, there could be a loss of network
connectivity for all devices downstream from the cable break or device failure. Avert this issue by
installing Spanning Tree in the switch or router to which the Spider chain attaches. Then, connect
the last Spider from its Cascade port to the same switch so that there is a redundant outside
connection.
Spanning Tree protocol implemented in the switch disables one of the two network connections
while the loop remains complete. Data flows in one direction only around the loop. If the loop
breaks, Spanning Tree activates both connections, so that data flows in both directions. All
devices in the Spider chain are accessible except the one immediately downstream from the cable
break or failed device. Do not try this workaround without Spanning Tree installed.
Client Server Setup
Two mechanisms provide the monitoring of client servers that are connected through the Spider:
platform-dependent management and platform-independent management.
 Platform-dependent management—Spider View is a standalone Windows XP or later
application that locates, manages, and accesses multiple Spider devices in an integrated
view. Spider View requires ActiveX controls enabled. Refer to the Spider View User Guide at
http://www.lantronix.com/support/documentation.html for instructions on installation and
operation of Spider View .
 Platform-independent management—Each Spider contains an embedded web server that
delivers web pages, a Java KVM Remote Console program, and a terminal program. To
access and manage the client server, a web browser is required. For example, use the latest
version of Internet Explorer, Netscape, FireFox, and Safari. To run the Remote Console
window and manage the target server, a Java plug-in (SUN JRE 1.4 or later) is required.
Network Environment
The connection between the client and Spider must be open to IP traffic and use TCP ports 80
(HTTP) and 443 (HTTPS). Firewalls and NAT devices should be configured to support this
configuration. The TCP ports can be changed by accessing Interfaces > Network.