Revision 0605bbe3
Added by Ermal Luçi almost 17 years ago
usr/local/www/interfaces_lagg_edit.php | ||
---|---|---|
136 | 136 |
?> |
137 | 137 |
</select> |
138 | 138 |
<br/> |
139 |
<span class="vexpl">Remote lagg address endpoint. The subnet part is used for the determinig the network that is tunneled.</span></td> |
|
139 |
<span class="vexpl"> |
|
140 |
<ul> |
|
141 |
<li> |
|
142 |
<b>failover</b><br/> |
|
143 |
Sends and receives traffic only through the master port. If |
|
144 |
the master port becomes unavailable, the next active port is |
|
145 |
used. The first interface added is the master port; any |
|
146 |
interfaces added after that are used as failover devices. |
|
147 |
</li><li> |
|
148 |
<b>fec</b><br/> Supports Cisco EtherChannel. This is a static setup and |
|
149 |
does not negotiate aggregation with the peer or exchange |
|
150 |
frames to monitor the link. |
|
151 |
</li><li> |
|
152 |
<b>lacp</b><br/> Supports the IEEE 802.3ad Link Aggregation Control Protocol |
|
153 |
(LACP) and the Marker Protocol. LACP will negotiate a set |
|
154 |
of aggregable links with the peer in to one or more Link |
|
155 |
Aggregated Groups. Each LAG is composed of ports of the |
|
156 |
same speed, set to full-duplex operation. The traffic will |
|
157 |
be balanced across the ports in the LAG with the greatest |
|
158 |
total speed, in most cases there will only be one LAG which |
|
159 |
contains all ports. In the event of changes in physical |
|
160 |
connectivity, Link Aggregation will quickly converge to a |
|
161 |
new configuration. |
|
162 |
</li><li> |
|
163 |
<b>loadbalance</b><br/> Balances outgoing traffic across the active ports based on |
|
164 |
hashed protocol header information and accepts incoming |
|
165 |
traffic from any active port. This is a static setup and |
|
166 |
does not negotiate aggregation with the peer or exchange |
|
167 |
frames to monitor the link. The hash includes the Ethernet |
|
168 |
source and destination address, and, if available, the VLAN |
|
169 |
tag, and the IP source and destination address. |
|
170 |
</li><li> |
|
171 |
<b>roundrobin</b><br/> Distributes outgoing traffic using a round-robin scheduler |
|
172 |
through all active ports and accepts incoming traffic from |
|
173 |
any active port. |
|
174 |
</li><li> |
|
175 |
<b>none</b><br/> This protocol is intended to do nothing: it disables any |
|
176 |
traffic without disabling the lagg interface itself. |
|
177 |
</li> |
|
178 |
</ul> |
|
179 |
</span></td> |
|
140 | 180 |
</tr> |
141 | 181 |
<tr> |
142 | 182 |
<td width="22%" valign="top" class="vncell">Description</td> |
Also available in: Unified diff
Add text, from lagg(4) man page, that explains what the various protocols do. Add even a note to explain that only un-assigned interfaces can be part of a lagg(4) interface with suggestion from http://forum.pfsense.org/index.php/topic,11614.0.html.