Adaptec 5325301656 Administration Guide - Page 37

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

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

  • 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224

Configuring TCP/IP Settings
Chapter 2
Network Access to the Server
23
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.