Adaptec 5325301638 Administration Guide - Page 29

Configuring TCP/IP Settings, Issues in TCP/IP Configuration

Get Adaptec 5325301638 - Snap Server 4500 NAS PDF manuals and user guides
UPC - 753253016389
View all Adaptec 5325301638 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 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. • For a Single Subnet or Multihomed Configuration (Standalone) - Standalone treats each port as a separate interface. In a single-subnet configuration, the primary port (only) 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 or Failover) - Network bonding technology treats two ports as a single channel, with the network using one IP address for the server. To take advantage of network bonding, both ports must be physically connected to the network; and (a) for load balancing, connected to the same switch on the same subnet; or (b) for failover, connected to different switch (in case one switch fails). Caution If you connect only one port, use the primary port (Ethernet1). If you use Ethernet2, a number of services will not function properly. Connect the Snap Server to the Network via a Switch While it is possible to connect a Snap Server to the network via a hub, this configuration unduly restricts the performance of the server for the following reasons: • Hubs do not support full-duplex. You can employ full-duplex only when the Snap Server is connected to a switch. • Hubs do not support Gigabit speeds. Attempting to force a Gigabit setting when the Snap Server is cabled to a hub will produce unintended consequences. The best performance possible when connected to a hub is 100 Mps/half duplex. Chapter 2 Network Access to the Server 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
Configuring TCP/IP Settings
Chapter 2
Network Access to the Server
15
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.
•
For a Single Subnet or Multihomed Configuration (Standalone) —
Standalone
treats each port as a separate interface. In a single-subnet configuration, the
primary port (only) 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 or Failover) —
Network
bonding technology treats two ports as a single channel, with the network using
one IP address for the server. To take advantage of network bonding, both ports
must be physically connected to the network; and (a) for load balancing,
connected to the same switch on the same subnet; or (b) for failover, connected to
different switch (in case one switch fails).
Caution
If you connect only one port, use the primary port (Ethernet1). If you use
Ethernet2, a number of services will not function properly.
Connect the Snap Server to the Network via a Switch
While it is possible to connect a Snap Server to the network via a hub, this
configuration unduly restricts the performance of the server for the following
reasons:
•
Hubs do not support full-duplex. You can employ full-duplex only when the
Snap Server is connected to a switch.
•
Hubs do not support Gigabit speeds. Attempting to force a Gigabit setting when
the Snap Server is cabled to a hub will produce unintended consequences.
The best performance possible when connected to a hub is 100 Mps/half duplex.