Client Setup; Network Environment - Lantronix SecureLinx Spider User Manual

Cabling
Connections for video, USB, and keyboard/mouse are integrated into the Spider. Do not
use extension cables; plug the Spider directly into the appropriate ports on the host
system. If using the serial port, cable it to the appropriate COM port on the server. The
second Ethernet port (cascade) may be used to connect to the target computer's
management LAN port or main LAN port, or to chain Spiders. When connecting the
Ethernet ports, either straight through or crossover cables may be used, as the Spider
has both auto-polarity and auto-crossover correction.
When chaining Spiders, bring the outside network cable in to the left Ethernet port of
the first Spider.
Connect the right Cascade port to the left port of the next Spider in the chain.
Repeat as necessary. The last Spider in the chain will have its right port unoccupied,
unless cabling in a loop for redundant connection.
The downside to chaining Spiders is that a break in the cabling or device failure results in
a loss of network connectivity for all Spiders downstream of the fault. This can be averted
if the switch or router to which the Spider chain attaches supports Spanning Tree, and
has it activated. In that case, the last Spider can have its Cascade port tied back to the
same switch so that there is a redundant outside connection. The Spanning Tree protocol
implemented in the switch will disable one of the two network connections while the loop
remains complete; data will flow in only one direction around the loop. If the loop is
broken, it activates both connections, so that data can flow in both directions. All Spiders
will be accessible except the one immediately downstream from the break or down unit.
Do not try this without Spanning Tree in place.

Client Setup

Two mechanisms are provided for monitoring Spider-connected targets at client systems.
Spider View is a standalone Windows application that can locate, manage, and access
multiple Spiders from an integrated view. Spider View requires a client to be running
Windows XP or later and have ActiveX controls enabled. Please refer to the separate
Spider View User Guide for instructions on installation and operation of Spider View.
For platform-independent management, each Spider contains an embedded web server
that delivers web pages and Java applets. The client system must have a web browser
(Spider supports browsers such as Internet Explorer 6.0+, Netscape 5.0+, FireFox 1.0+,
and Safari 2.0+) in order to access and administer the Spider. To run the actual Remote
Console window and manage the target system, a Java plug-in is also required. The
Microsoft Java Runtime Environment version 1.1 or later is supported, but the Sun JRE
1.4 or later is preferred.

Network Environment

The connection between client and Spider must be open to IP traffic and have TCP ports
80 (HTTP) and 443 (HTTPS) open. Firewalls and NAT devices may need to be
configured to support this; consult your system administrator. The TCP ports used by the
Spider may be changed at Device Settings
When idle, the Spider generates minimal network traffic but when images are rapidly
changing on the host system and image quality is set to the maximum there can be
SecureLinx Spider User Guide
Network.
3: Installation
16