os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Add new entities for IEEE, Cisco and EtherChannel.

Browse source 
- Use the new entities.
- A big clean up for the Link Aggregation and Failover chapter.

Reviewed by:	trhodes@
This commit is contained in:
Brad Davis 2009-01-05 21:30:43 +00:00
parent 3b1a41e67f
commit ab3da6f848
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=33654
2 changed files with 62 additions and 41 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

100
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -21,7 +21,7 @@
</listitem>
<listitem>
<para>How to set up IEEE 802.11 and &bluetooth; devices.</para>
<para>How to set up &ieee; 802.11 and &bluetooth; devices.</para>
</listitem>
<listitem>
@ -700,7 +700,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
<sect2>
<title>Wireless Networking Basics</title>
<para>Most wireless networks are based on the IEEE 802.11
<para>Most wireless networks are based on the &ieee; 802.11
standards. A basic wireless network consists of multiple
stations communicating with radios that broadcast in either
the 2.4GHz or 5GHz band (though this varies according to the
@ -720,7 +720,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
network</emphasis>.</para>
<para>802.11 networks were first deployed in the 2.4GHz band
using protocols defined by the IEEE 802.11 and 802.11b
using protocols defined by the &ieee; 802.11 and 802.11b
standard. These specifications include the operating
frequencies, MAC layer characteristics including framing and
transmission rates (communication can be done at various
@ -740,7 +740,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
to communicate. This scheme was shown to be easily broken and
is now rarely used except to discourage transient users from
joining networks. Current security practice is given by the
IEEE 802.11i specification that defines new cryptographic
&ieee; 802.11i specification that defines new cryptographic
ciphers and an additional protocol to authenticate stations to
an access point and exchange keys for doing data
communication. Further, cryptographic keys are periodically
@ -1378,7 +1378,7 @@ ath0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
</callout>
<callout arearefs="co-tls-proto">
<para>Here, we use RSN (IEEE 802.11i) protocol, i.e.,
<para>Here, we use RSN (&ieee; 802.11i) protocol, i.e.,
WPA2.</para>
</callout>
@ -3216,7 +3216,7 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
<variablelist>
<varlistentry><term>failover</term>
<varlistentry><term>Failover</term>
<listitem>
<para>Sends and receives traffic only through the master port. If the
@ -3226,15 +3226,15 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
</listitem>
</varlistentry>
<varlistentry><term>fec</term>
<varlistentry><term>&cisco; Fast &etherchannel;</term>
<listitem>
<para>Supports Cisco EtherChannel. This is a static setup and does not
<para>&cisco; Fast &etherchannel; (FEC), is a static setup and does not
negotiate aggregation with the peer or exchange frames to monitor the
link, if the switch supports LACP then that should be used
link. If the switch supports LACP then that should be used
instead.</para>
<para>Balances outgoing traffic across the active ports based on hashed
<para><acronym>FEC</acronym> balances outgoing traffic across the active ports based on hashed
protocol header information and accepts incoming traffic from any
active port. The hash includes the Ethernet source and destination
address, and, if available, the VLAN tag, and the IPv4/IPv6 source
@ -3242,20 +3242,20 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
</listitem>
</varlistentry>
<varlistentry><term>lacp</term>
<varlistentry><term>LACP</term>
<listitem>
<para>Supports the IEEE 802.3ad Link Aggregation Control Protocol
<para>The &ieee; 802.3ad Link Aggregation Control Protocol
(LACP) and the Marker Protocol. LACP will negotiate a set of
aggregable links with the peer in to one or more Link Aggregated
Groups. Each LAG is composed of ports of the same speed, set to
Groups (LAG). Each LAG is composed of ports of the same speed, set to
full-duplex operation. The traffic will be balanced across the ports
in the LAG with the greatest total speed, in most cases there will
only be one LAG which contains all ports. In the event of changes in
only be one LAG which contains all ports. In the event of changes in
physical connectivity, Link Aggregation will quickly converge to a
new configuration.</para>
<para>Balances outgoing traffic across the active ports based on hashed
<para><acronym>LACP</acronym> balances outgoing traffic across the active ports based on hashed
protocol header information and accepts incoming traffic from any
active port. The hash includes the Ethernet source and destination
address, and, if available, the VLAN tag, and the IPv4/IPv6 source
@ -3263,19 +3263,19 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
</listitem>
</varlistentry>
<varlistentry><term>loadbalance</term>
<varlistentry><term>Loadbalance</term>
<listitem>
<para>This is an alias of <emphasis>fec</emphasis> mode.</para>
<para>This is an alias of <emphasis>FEC</emphasis> mode.</para>
</listitem>
</varlistentry>
<varlistentry><term>roundrobin</term>
<varlistentry><term>Round-robin</term>
<listitem>
<para>Distributes outgoing traffic using a round-robin scheduler
through all active ports and accepts incoming traffic from any active
port. This mode will violate Ethernet frame ordering and should be
port. This mode violates Ethernet Frame ordering and should be
used with caution.</para>
</listitem>
</varlistentry>
@ -3286,7 +3286,7 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
<title>Examples</title>
<example id="networking-lacp-aggregation-cisco">
<title>LACP aggregation with a Cisco switch</title>
<title>LACP aggregation with a &cisco; Switch</title>
<para>This example connects two interfaces on a &os; machine to the
switch as a single load balanced and fault tolerant link. More interfaces
@ -3297,23 +3297,31 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
much information as it can to distinguish different traffic flows and
balance across the available interfaces.</para>
<para>On the Cisco switch add the interfaces to the channel group.</para>
<para>On the &cisco; switch add the
<replaceable>FastEthernet0/1</replaceable> and
<replaceable>FastEthernet0/2</replaceable> interfaces to the
channel-group <replaceable>1</replaceable>:</para>
<screen>interface FastEthernet0/1
channel-group 1 mode active
channel-protocol lacp
<screen><userinput>interface <replaceable>FastEthernet0/1</replaceable>
channel-group <replaceable>1</replaceable> mode active
channel-protocol lacp</userinput>
!
interface FastEthernet0/2
channel-group 1 mode active
channel-protocol lacp
!</screen>
<userinput>interface <replaceable>FastEthernet0/2</replaceable>
channel-group <replaceable>1</replaceable> mode active
channel-protocol lacp</userinput></screen>
<para>On the &os; machine create the lagg interface.</para>
<para>On the &os; machine create the &man.lagg.4; interface using
<replaceable>fxp0</replaceable> and
<replaceable>fxp1</replaceable>:</para>
<screen>&prompt.root; <userinput>ifconfig lagg0 create</userinput>
&prompt.root; <userinput>ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig <replaceable>lagg0</replaceable> create </userinput>
&prompt.root; <userinput>ifconfig <replaceable>lagg0</replaceable> up laggproto lacp laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable></userinput></screen>
<para>View the interface status from ifconfig; ports marked as
<para>View the interface status by running:</para>
<screen>&prompt.root; <userinput>ifconfig <replaceable>lagg0</replaceable></userinput></screen>
<para>Ports marked as
<emphasis>ACTIVE</emphasis> are part of the active aggregation group
that has been negotiated with the remote switch and traffic will be
transmitted and received. Use the verbose output of &man.ifconfig.8;
@ -3328,8 +3336,8 @@ interface FastEthernet0/2
laggport: fxp1 flags=1c&lt;ACTIVE,COLLECTING,DISTRIBUTING&gt;
laggport: fxp0 flags=1c&lt;ACTIVE,COLLECTING,DISTRIBUTING&gt;</screen>
<para>The switch will show which ports are active. For more detail use
<userinput>show lacp neighbor detail</userinput>.</para>
<para>To see the port status on the switch, use <userinput>show
lacp neighbor</userinput>:</para>
<screen>switch# show lacp neighbor
Flags: S - Device is requesting Slow LACPDUs
@ -3345,17 +3353,27 @@ Port Flags Priority Dev ID Age Key Number State
Fa0/1 SA 32768 0005.5d71.8db8 29s 0x146 0x3 0x3D
Fa0/2 SA 32768 0005.5d71.8db8 29s 0x146 0x4 0x3D</screen>
<para>For more detail use the <userinput>show lacp neighbor
detail</userinput> command.</para>
</example>
<example id="networking-lagg-failover">
<title>Failover mode</title>
<para>Failover mode can be used to switch over to another interface if
the link is lost on the master.</para>
<para>Failover mode can be used to switch over to a secondary interface if
the link is lost on the master interface. Create and configure the
<replaceable>lagg0</replaceable> interface, with
<replaceable>fxp0</replaceable> as the master interface and
<replaceable>fxp1</replaceable> as the secondary interface:</para>
<screen>&prompt.root; <userinput>ifconfig lagg0 create</userinput>
&prompt.root; <userinput>ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig <replaceable>lagg0</replaceable> create</userinput>
&prompt.root; <userinput>ifconfig <replaceable>lagg0</replaceable> up laggproto failover laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable></userinput></screen>
<screen>lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
<para>The interface will look something like this, the major
differences will be the <acronym>MAC</acronym> address and the
device names:</para>
<screen>&prompt.root; <userinput>ifconfig <replaceable>lagg0</replaceable></userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=8&lt;VLAN_MTU&gt;
ether 00:05:5d:71:8d:b8
media: Ethernet autoselect
@ -3365,8 +3383,8 @@ Fa0/2 SA 32768 0005.5d71.8db8 29s 0x146 0x4 0x3D</screen
laggport: fxp0 flags=5&lt;MASTER,ACTIVE&gt;</screen>
<para>Traffic will be transmitted and received on
<devicename>fxp0</devicename>. If the link is lost on
<devicename>fxp0</devicename> then <devicename>fxp1</devicename> will
<replaceable>fxp0</replaceable>. If the link is lost on
<replaceable>fxp0</replaceable> then <replaceable>fxp1</replaceable> will
become the active link. If the link is restored on the master
interface then it will once again become the active link.</para>
</example>

3
share/sgml/trademarks.ent
View file

@ -86,7 +86,9 @@
<!ENTITY tm-attrib.cisco "<para>Cisco, Catalyst, and IOS are
registered trademarks of Cisco Systems, Inc. and/or its affiliates
in the United States and certain other countries.</para>">
<!ENTITY cisco "<trademark class='registered'>Cisco</trademark>">
<!ENTITY catalyst "<trademark class='registered'>Catalyst</trademark>">
<!ENTITY etherchannel "<trademark class='registered'>EtherChannel</trademark>">
<!ENTITY ios "<trademark class='registered'>IOS</trademark>">
<!ENTITY tm-attrib.corel "<para>Corel and WordPerfect are trademarks
@ -151,6 +153,7 @@ Coverity, Inc.</para>">
<!ENTITY tm-attrib.ieee "<para>IEEE, POSIX, and 802 are registered
trademarks of Institute of Electrical and Electronics Engineers,
Inc. in the United States.</para>">
<!ENTITY ieee "<trademark class='registered'>IEEE</trademark>">
<!ENTITY posix "<trademark class='registered'>POSIX</trademark>">
<!-- http://www.intel.com/intel/legal/tmnouns2.htm -->