Adaptec 5325301656 Administration Guide - Page 37
Configuring TCP/IP Settings, Issues in TCP/IP Configuration
UPC - 753253016563
View all Adaptec 5325301656 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 37 highlights
Configuring TCP/IP Settings Configuring TCP/IP Settings TCP/IP settings are configured on the Network > TCP/IP screen of the Administration Tool. This screen defaults to the current settings for the primary Ethernet port (Ethernet1). Issues in TCP/IP Configuration Consider the following guidelines when connecting a Snap Server to the network. Cabling for Single-Subnet, Multihomed, or Network Bonding Configurations All GuardianOS Snap Servers ship with two Ethernet cables for connecting the server to the network. Note Exceptions to this are the Snap Server 110 and 210, which ship with a single Ethernet cable. • For a Single Subnet or Multihomed Configuration (Standalone) - Standalone treats each port as a separate interface. In a single-subnet configuration, only the primary port is connected to the switch. In a multihomed configuration, each port is cabled to a different switch and the network connections lead to separate subnets. Caution Do not connect both Ethernet ports to the same network segment in Standalone mode. This configuration is not supported and will lead to unexpected results. • For a Network Bonding Configuration (Load Balancing, Failover, Switch Trunking, or Link Aggregation) - Network bonding technology treats two or more ports as a single channel, with the network using one IP address for the server. Note This network bonding configuration is not applicable to Snap Server 110 or 210. To take advantage of network bonding, both ports must be physically connected to the network: • For load balancing, Switch Trunking, or Link Aggregation, connected to the same switch on the same subnet; or • For failover, connected to a different switch (in case one switch fails). Caution If you connect only one port, use the primary port (Ethernet1). If you use Ethernet2, some services may not function properly. Chapter 2 Network Access to the Server 23