Overview
Introduction
1-3
1.1.1
Connectivity
The SmartSwitch modules connect to Ethernet networks or workstations through the RJ45 ports on
the front panel. These ports are IEEE 802.3 10BASE-T and IEEE 802.3u 100BASE-TX
compliant. The ports support Category 5 Unshielded Twisted Pair cables with an impedance
between 85 and 111 ohms at lengths up to 100 meters for both 10 Mbps and 100 Mbps Ethernet
connections. They also support Category 3 for 10 Mbps, but not 100 Mbps Ethernet connections.
The 6H252-17 has a slot for an optional HSIM or VHSIM to provide additional connectivity to
various networking technologies.
The 6H262-18 has 2 GPIM slots for optional GPIMs that can provide additional connectivity to
Gigabit Ethernet, operating in full duplex mode. One of the ports is active and the other is
redundant. Redundancy is triggered based on link activity. GPIM 1 is the active port by default.
1.1.2
Auto-Negotiation
The twisted pair ports on the front panel of the SmartSwitch modules have the ability to
auto-negotiate the type of connection required to provide a link to another device. During
Auto-Negotiation, two devices automatically exchange information “telling” each other what their
operating capabilities are. The Auto-Negotiation feature targets the maximum capabilities that can
be reached between the two devices. For example, the SmartSwitches adjust to 100 Mbps when the
device on the other end of the connection can also adjust between 10 Mbps or 100 Mbps. If the
device on the other end of the connection can only operate at 10 Mbps, then the SmartSwitches
adjust to 10 Mbps operation.
When Auto-Negotiation is supported at both ends of a link, the two devices dynamically adjust to
full or half duplex operation based on the maximum capability that can be reached between the
two devices. If the device connected to the SmartSwitch cannot auto-negotiate, the module
interface operates according to the capability of the other device.
1.1.3
Runtime IP Address Discovery
This feature enables the modules to automatically accept an IP address from a Boot Strap Protocol
(BootP) server on the network into NVRAM without requiring a user to enter an IP address
through Local Management.
When the modules are connected to the network and powered up, Runtime IP Address Discovery
(RAD) checks the modules for an IP address. If one has not yet been assigned (module and 6C105
chassis IP address set to 0.0.0.0), RAD checks to see if any of the module interfaces have a link. If
so, RAD sends out Reverse Address Resolution Protocol (RARP) and BootP requests to obtain an
IP address from a RARP or BootP server on the network.
