Académique Documents
Professionnel Documents
Culture Documents
x
Capas IEEE dentro del modelo OSI
IEEE
Nivel OSI Subcapa de Control de 802.2
ENLACE
Enlace Lógico (LLC)
7 Aplicación
Ethernet
Sesión Acceso al Medio (MAC)
5
4 Transporte
Subcapas de
FÍSICA
.
1 Física del medio 3
2
Capas del protocolo IEEE
802
El Comité IEEE 802 ha desarrollado una
arquitectura de protocolos, adoptada por otros.
Modelo de Referencia
Aplicación
IEEE 802
Presentación
Sesión Protocolos Puntos de
Acceso al
Transporte de la capas Servicio LLC
Red superiores (LSAP)
Control de Enlace
Enlace de Lógico-LLC
datos Control deAcceso Normas
al medio-MAC
IEEE802
Físico Físico
Medio de transmisión Medio de transmisión
3
Encapsulamiento del protocolo
LAN
Datos deAplicación
Cola de
Cabecera de trama Datos deAplicación
trama
4
Estándares IEEE 802
Ethernet
E (8) (6) (6) (2) (>46 <1500) (4)
7
El preámbulo es una cadena de 1s y 0s, que finaliza con 11 para indicar el comienzo del campo de dirección de
destino. Los campos que conformanla trama son:
DA (Destination Address - Dirección de destino): contiene 48 bits que representan la dirección MAC del host
destino.
SA (Source Address - Dirección de origen): contiene 48 bits que representan la dirección MAC del host que envía
la trama.
Type (tipo): contiene el número "Ethertype" que indica el protocolo de capa superior que es encapsulado en la
porción de datos de la trama. Ejemplos de números Ethertype son:
Data (datos): contiene la información del protocolo de la capa superior. Si la información es menor a 46 bytes, se
rellena para alcanzar el tamaño mínimo de trama de 64 bytes (encabezado más datos).
FCS (Frame Check Sequence - control de secuencia de trama): contiene los datos del CRC (Cyclic Redundancy
Check) para verificar errores en la recepción de la trama.
El tamaño mínimo de una trama es 64 bytes y el máximo 1518. Cuando se calcula el tamaño de una trama no se
incluye el preámbulo. El formato de la trama Versión 2, sigue las siguientes especificaciones:
El tamaño mínimo de una trama es 6+6+2+46+4= 64 bytes
El tamaño máximo de una trama es: 6+6+2+1500+4 = 1518 bytes
8
La IEEE desarolló su estandard Ethernet en junio de 1983. Cambiaron el campo type (tipo) por el
campo lenght (tamaño) y agregaron la capa LLC (Logical Link Control - Control de enlace lógico).
La figura muestra el formato de la trama IEEE 802.3.
Los campos de la trama son los siguientes:
Preámbulo: La IEEE lo definió como una cadena de 7 bytes de longitud compuesta por 1s y 0s.
Delimitador de inicio de la trama (SFD - Start Frame Delimiter): 10101011
DA: Dirección MAC destino.
SA: Dirección MAC origen.
Length (tamaño): contiene el tamaño del LLC más el campo de datos. Estos valores están
comprendidos en un rango desde 3 a 1500 bytes.
Data (datos): contiene la información del protocolo de capa superior, como en los otros formatos
de trama.
FCS: contiene el CRC.
9
Operación
Ethernet
Broadcast Ethernet
A B C D
Aplicacion Aplicacion Aplicacion Aplicacion
Presentacion Presentacion Presentacion
Presentacion
Sesion Sesion Sesion
Sesion
Transporte Transporte Transporte Transporte
Red Red Red Red
Enlace de Dato s Enlace de Datos Enlace de Dato s
Enlace de D atos
Fisica Fisica Fisica Fisica
10
Operación
Ethernet
A B C D
D
Aplicacion
Presentacion
Sesion
Transporte
Red
Enlace de Datos
Fisica
D ByC
Aplicacion Aplicacion
Presentaci on Presentacion
Sesion Sesion
Transporte Transporte
Red Red
Enlace de Datos Enlace de Datos
Fisica Fisica 11
Sending and receiving Ethernet frames on a bus
3333 1111
Hey, that’s
Nope me! Nope
1111 2222 3333 nnnn Abbreviated
MAC
Addresses
3333 1111
14
Sending and receiving Ethernet frames on a bus
Collision!
15
Access Methods
Hey, that’s
Nope
me! Nope Abbreviated
1111 2222 3333 nnnn MAC
Addresses
Notice the
location of
the DA!
3333 1111
17
• Sending and receiving Ethernet frames via a hub
3333 1111
1111
? 2222
• So, what does a
hub do when it
receives
information?
5555
• Remember, a hub
is nothing more
than a multiport
3333 4444
repeater. 22
• Sending and receiving Ethernet frames via a hub
Hub or
23
• Sending and receiving Ethernet frames via a hub
3333 1111
• The hub will flood it out all ports
1111 2222 except for the incoming port.
Nope • Hub is a layer 1 device.
• A hub does NOT look at layer 2
addresses, so it is fast in
transmitting data.
• Disadvantage with hubs: A hub
5555 or series of hubs is a single
Nope collision domain.
• A collision will occur if any two
or more devices transmit at the
same time within the collision
domain.
2222 1111
1111 2222
For me!
• Another disadvantage
with hubs is that is
take up unnecessary
bandwidth on other
links.
5555 Wasted
Nope
bandwidth
26
• Sending and receiving Ethernet frames via a switch
switch
1111 3333
1111 3333
• What happens when two devices
send to same destination?
Abbreviated
MAC • What if this was a hub?
addresses • Where is (are) the collision
2222 4444 domain(s) in this example?
• No Collisions in Switch, Buffering
switch
3333 4444
• Notice the
Source
Address Table
has multiple
entries for port
#1.
3333
3333
Collision Domain
3333
A B C D
Figura 1
A B C D
Figura 2
33
Confiabilidad
Ethernet
A B C D
Colisión
A B C D
34
Confiabilidad
Ethernet
A B C D
Colisión
A B C D
IEEE 802.1Q
Protocolo estándar de la IEEE, implementa el etiquetado de
tramas para identificar la VLAN, inserta un nuevo campo de
información en el encabezado de la trama.
Interconexión de vlan’s
También denominada ROAS Router On A Stick. Esto surge ya
que al implementar VLAN en una red conmutada de capa 2 se
generan múltiples dominios de broadcast generando multiples
redes virtuales que conviven sobre una misma infraestructura
física.
Simultáneamente como resultado de esta segmentación no
hay posibilidad de establecer conexión entre nodos que se
encuentran en diferentes VLAN’s de la red.
En consecuencia luego de segmentar la red utilizando VLAN,
para mejorar la performance y la seguridad, suele ser
necesario establecer comunicación entre nodos de diferentes
VLAN’s implementando dispositivos de capa 3.
Interconexión de vlan’s
Configuración básica de vlan
.
Creating VLANs
Default: dynamic desirable This link will become a trunking link unless one of the ports is
configured with as an access link, I.e. switchport mode access
10
.
MAC address Based VLANs
• Rarely implemented.
VTP “Vlan Trunking Protocol”
VTP
VTP
Benefits of VTP (VLAN Trunking Protocol)
Benefits
• VTP is a Cisco proprietary protocol that allows VLAN
configuration to be consistently maintained across a
common administrative domain.
• VTP minimizes the possible configuration inconsistencies
that arise when changes are made.
• Additionally, VTP reduces the complexity of
managing and monitoring VLAN networks.
VTP
• VTP (VLAN Trunking Protocol) is used to distribute and synchronize
information about VLANs that are configured throughout a switched
network.
• Switches transmit VTP messages only on 802.1Q and ISL trunks.
• Note: VTP is not required to configure trunking between switches, but is
used to simplify VLAN management.
• VTP Server
– This is the default VTP mode.
– VLANs can be created, modified, and deleted.
• VTP Client
– This behaves like a VTP server without the ability to create, change, or
delete VLANs.
• VTP Transparent
– Switches in the VTP Transparent mode do not participate in VTP.
VTP Operation
• VTP advertisements are sent as multicast frames.
• VTP servers and clients are synchronized to the latest revision number.
• VTP advertisements are sent every 5 minutes or when there is a change.
7
VTP Operation
Switch#config terminal
Switch(config)#vtp mode [client|server|transparent]
Switch#vlan database
Switch(vlan)#vtp [client|server|transparent]
14 RickGraziani
graziani@cab
VTP Configuration - Overview
16 RickGraziani
graziani@cab
Verifying VTP
status
• VLAN Tagging is used when a link needs to carry traffic for more than one VLAN.
• Trunk link: As packets are received by the switch from any attached end-station
device, a unique packet identifier is added within each header.
• This header information designates the VLAN membership of each packet.
Rick Graziani
graziani@cabrillo.edu 3
.
VLAN Tagging
• VLAN Tagging is used when a link needs to carry traffic for more than one VLAN.
– Trunk link: As packets are received by the switch from any attached end-
station device, a unique packet identifier is added within each header.
• This header information designates the VLAN membership of each packet.
• The packet is then forwarded to the appropriate switches or routers based on the
VLAN identifier and MAC address.
• Upon reaching the destination node (Switch) the VLAN ID is removed from the
packet by the adjacent switch and forwarded to the attached device.
• Packet tagging provides a mechanism for controlling the flow of broadcasts and
applications while not interfering with the network and applications..
.
VLAN Tagging
No VLAN Tagging
VLAN Tagging
• VLAN Tagging is used when a link needs to carry traffic for more than one
VLAN.
• Tagging is used so the receiving switch knows which ports in should flood
broadcast and unknown unicast traffic (only those ports belonging to the
same VLAN).
6
.
VLAN Tagging
802.10
• There are two major methods of frame tagging, Cisco proprietary Inter-
Switch Link (ISL) and IEEE 802.1Q.
• ISL used to be the most common, but is now being replaced by 802.1Q frame
tagging.
• Cisco recommends using 802.1Q.
• VLAN Tagging and Trunking will be discussed in the next chapter.
7
.
A Closer look at VLAN Tagging
ISL 802.1Q
Proprietary Nonproprietary
Encapsulated Tagged
8
VLAN Tagging
.
A Closer look at VLAN Tagging
ISL
Ethernet Frame
1500 bytes plus 18 byte header
(1518 bytes)
IEEE 802.1Q
SA and DASA and
802.1q
DA Type/Length Data (max 1500 New
CRC
MACs MACsTag Field bytes) CRC
10
ISL (Frame Encapsulation)
Ethernet Frame
1500 bytes plus 18 byte header
(1518 bytes)
11
VLAN Tagging
IEEE 802.1Q
NIC cards and networking devices can understand this “baby
giant” frame (1522 bytes). However, a Cisco switch must
remove this encapsulation before sending the frame out on an
access link.
or 802.1Q
14
VLAN Tagging
VLAN Tagging
VLAN Tagging
Configuring Trunking
Note: On switches
that support both
802.1Q and ISL, the
switchport trunk
encapsulation
command must be
done BEFORE the
switchport mode
trunk command.
• If SwitchA can only be a 802.1.Q trunk and SwitchB can only be an ISL trunk,
these two switches will not be able to form a trunk.
Configuring Trunking
802.1Q only Both ISL and 802.1Q
Trunk
• If SwitchA can only be a 802.1.Q trunk and SwitchB can be either ISL or
8021.Q trunk, configure SwitchB to be 802.1Q.
• On switches that support both 802.1Q and ISL, the switchport trunk
encapsulation command must be done BEFORE the switchport
mode trunk command.
Configuring Trunking
No VLAN Tagging
VLAN Tagging
Configuring Trunking
Configuring Trunking
Configuring Trunking
DTP
Dynamic Trunking Protocol
DTP Dynamic Trunking Protocol
DTP – Dynamic Trunking
Protocol
• Ethernet trunk interfaces support several different trunking modes.
– Access
– Dynamic desirable (default mode on Catalyst 2950 and 3550)
– Dynamic auto
– Trunk
– Non-negotiate
– dotq-tunnel (Not an option on the Catalyst 2950.)
• Using these different trunking modes, an interface can be set to trunking or
nontrunking or even able to negotiate trunking with the neighboring
interface.
• To automatically negotiate trunking, the interfaces must be in the same VTP
domain. (VTP is discussed in the next section.)
• Trunk negotiation is managed by the Dynamic Trunking Protocol (DTP), which
is a Cisco proprietary Point-to-Point Protocol.
• These various modes are configured using the switchport mode interface
command
DTP – Dynamic Trunking
Protocol
• These various modes are configured using the switchport mode interface
command.
• We have already discussed the two “non-dynamic” options:
Switch(config-if)switchport mode access
Switch(config-if)switchport mode trunk
• These options set the interface to non-trunking (access) or trunking (trunk)
DTP Dynamic Trunking Protocol
DTP
Dynamic Auto Dynamic Trunk Access
Desirable
Dynamic Access Trunk Trunk Access
Auto
Dynamic Trunk Trunk Trunk Access
Desirable
Trunk Trunk Trunk Trunk Not
recommended
Access Access Access Not Access
recommended
• Without the switchport mode access command, this interface will still
try to negotiate trunking.
Why the switchport mode access command?
Switch(config)#interface range fa 0/11 - 15
Switch(config-if-range)#switchport mode access
Then Destination MAC Address is that of the same device as the Destination IP Address.
Check ARP cache for entry of Destination IP Address and its MAC Address.
If no entry, ARP Request Destination IP Address asking for MAC Address.
VLAN 1
External Router VLAN 2
VLAN 3
VLANs 1, 2, 3
Router on a stick
Trunk
VLAN 1
VLAN 2
Multilayer Switch Or Trunk
VLAN 3
External Router
Router(config)# inter fa 0/1
Router(config-if) ip address 172.16.1.1 255.255.255.0
Router(config)# inter fa 0/2
Router(config-if) ip address 172.16.2.1 255.255.255.0
Router(config)# inter fa 0/3
Router(config-if) ip address 172.16.3.1 255.255.255.0
Inter-VLAN Routing
Inter-VLAN Routing
Inter-VLAN Routing
Configure Router On A Stick: 802.1Q Trunk Link
interface GigabitEthernet5/0
no shutdown ! Does not show in config
!
interface GigabitEthernet5/0.2
description VLAN 2
encapsulation dot1Q 2 native
ip address 172.16.1.2 255.255.255.0
!
interface GigabitEthernet5/0.10
172.16.10.100/ 172.16.20.100/
24 24
description VLAN 10
encapsulation dot1Q 10
ip address 172.16.10.1 255.255.255.0
!
interface GigabitEthernet1/1 interface GigabitEthernet5/0.20
switchport mode trunk description VLAN 20
encapsulation dot1Q 20
ip address 172.16.20.1 255.255.255.0
!
Router on a stick is very interface GigabitEthernet5/0.30
simple to implement. description VLAN 30
encapsulation dot1Q 30
ip address 172.16.30.1 255.255.255.0
!
interface GigabitEthernet5/0.40
description VLAN 40
encapsulation dot1Q 40
ip address 172.16.40.1 255.255.255.0
Inter-VLAN Routing
Example…
Spanning Tree Protocol
Redundancia
3
Redundant topologies
14
Three Steps of Initial STP
Convergence
STP Convergence
Step 1 Elect one Root Bridge
Step 2 Elect Root Ports
Step 3 Elect Designated Ports
15
Spanning Tree Protocol
Two Key Concepts: BID and
Path Cost
ALSwitch#
20
Step 1 Elect one Root Bridge
Root
Bridge
Cost=19 1/1 1/2 Cost=19
Cat-A
1/1 1/1
Cat-B Cat-C
1/2 1/2
Cost=19
21
Step 1 Elect one Root Bridge
Cat-A has the lowest Bridge MAC Address, so it wins the Root War!
All 3 switches have the same default Bridge Priority value of 32,768
22
Step 1 Elect one Root Bridge
• In a real network, you do not want the placement of the root bridge to
rely on the random placement of the switch with the lowest MAC address.
• A misplaced root bridge can have significant effects on your network
including less than optimum paths within the network.
23
Step 1 Elect one Root Bridge
2950#show spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32768
Address 0003.e334.6640
Cost 19
Port 23 (FastEthernet0/23)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
ALSwitch#
24
Spanning Tree Protocol
Spanning Tree Protocol
Three Steps of Initial STP
Convergence
STP Convergence
Step 1 Elect one Root Bridge
Step 2 Elect Root Ports
Step 3 Elect Designated Ports
27
Spanning Tree Protocol
Spanning Tree Protocol
Step 2 Elect Root Ports
Cost=19 1/1 1/2 Cost=19
Cat-A
1/1 1/1
Cat-B Cat-C
1/2 1/2
Cost=19
Cat-A
Our Sample Topology
1/1 1/1
Cat-B Cat-C
1/2 1/2
Cost=19
31
Root
BPDU BPDU
Cost=0+19=19 Cost=0+19=19
1/1 1/1
Cat-B Cat-C
1/2 1/2
Step 1 Cost=19
BPDU BPDU
Cost=19 Cost=19
1/1 1/1
Cat-B Cat-C
1/2 BPDU BPDU 1/2
BPDU Cost=19 Cost=19 BPDU
Cost=38 (19=19) Cost=38 (19=19)
Cost=19
Step 3
• Cat-B uses this value of 19 internally and sends BPDUs with a Root Path Cost
of 19 out Port 1/2.
Step 4
• Cat-C receives the BPDU from Cat-B, and increased the Root Path Cost to 38
33
(19+19). (Same with Cat-C sending to Cat-B.)
Root
Step 2 Bridge
Cat-A
1/2 Cost=19
Root BPDU
Cost=0
BPDU
Cost=0
Ports
BPDU BPDU
Cost=19 Cost=19
1/1 1/1 Root
Root Port
Port
Cat-B Cat-C
1/2 1/2
BPDU BPDU
Cost=38 (19=19) Cost=38 (19=19)
Cost=19
Step 5
• Cat-B calculates that it can reach the Root Bridge at a cost of 19 via Port 1/1 as
opposed to a cost of 38 via Port 1/2.
• Port 1/1 becomes the Root Port for Cat-B, the port closest to the Root Bridge.
• Cat-C goes through a similar calculation. Note: Both Cat-B:1/2 and Cat-C:1/2
save the best BPDU of 19 (its own).
34
2950#show spanning-tree
Step 2 Elect Root Ports
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32768
Address 0003.e334.6640
Cost 19
Port 23 (FastEthernet0/23)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
ALSwitch#
35
Spanning Tree Protocol
Spanning Tree Protocol
Three Steps of Initial STP
Convergence
STP Convergence
Step 1 Elect one Root Bridge
Step 2 Elect Root Ports
Step 3 Elect Designated Ports
38
Spanning Tree Protocol
Step 3 Elect
Designated
Ports
Segment 1 Segment 2
Cat-A
Step 3 Elect
Designated Ports
Cat-B Cat-C
1/2 1/2
Root Path Cost = 19 Root Path Cost = 19
Segment 3
Cost=19
• Segment 1: Cat-A:1/1 has a Root Path Cost = 0 (after all it has the Root Bridge) and
Cat-B:1/1 has a Root Path Cost = 19.
• Segment 2: Cat-A:1/2 has a Root Path Cost = 0 (after all it has the Root Bridge) and
Cat-C:1/1 has a Root Path Cost = 19.
• Segment 3: Cat-B:1/2 has a Root Path Cost = 19 and Cat-C:1/2 has a Root Path Cost =
19. It’s a tie!
41
Root
Root Path Cost = 0 Bridge Root Path Cost = 0
Cost=19 1/1 1/2 Cost=19
Segment 1 Segment 2
Cat-A
Step 3 Elect Designated Port Designated Port
Designated Ports
Cat-B Cat-C
1/2 1/2
Root Path Cost = 19 Root Path Cost = 19
Segment 3
Cost=19
Segment 1
• Because Cat-A:1/1 has the lower Root Path Cost it becomes the Designate
Port for Segment 1.
Segment 2
• Because Cat-A:1/2 has the lower Root Path Cost it becomes the Designate
Port for Segment 2.
42
Root
Root Path Cost = 0 Bridge Root Path Cost = 0
Cost=19 1/1 1/2 Cost=19
Segment 1 Segment 2
Cat-A
Designated Port Designated Port
Cat-B Cat-C
1/2 1/2
Root Path Cost = 19 Root Path Cost = 19
Segment 3
Cost=19
Segment 3
• Both Cat-B and Cat-C have a Root Path Cost of 19, a tie!
• When faced with a tie (or any other determination) STP always uses the four-step
decision process:
43
Root
Root Path Cost = 0 Bridge Root Path Cost = 0
Cost=19 1/1 1/2 Cost=19
Segment 1 Segment 2
Cat-A
Designated Port Designated Port
Segment 3 (continued)
• 1) All three switches agree that Cat-A is the Root Bridge, so this is a tie.
• 2) Root Path Cost for both is 19, also a tie.
• 3) The sender’s BID is lower on Cat-B, than Cat-C, so Cat-B:1/2 becomes the Designated
Port for Segment 3.
• Cat-C:1/2 therefore becomes the non-Designated Port for Segment 3.
44
Spanning Tree Protocol
Spanning Tree Protocol
Spanning Tree Protocol
Spanning Tree Protocol
Spanning Tree Protocol
Spanning Tree Protocol
Stages of spanning-tree port
states
51
PortFast
Powercycle a host and watch
link
lights…
How long
until switch
link light
turns green?
17 RickGraziani
graziani@cab
PortFast
I’m adding any
Powered addresses on this
On port to my MAC
Address Table.
DHCP Discovery
Timeout
IP Address = 169.x.x.x
DHCP Discovery
DHCP Offer
• The purpose of PortFast is to minimize the time that access ports wait for STP
to converge.
• When a port comes up, the port immediately moves into Forwarding state.
• The advantage of enabling PortFast is to prevent DHCP timeouts.
• Host sends DHCP Discovery
• Host can now can IP addressing information.
20
Configuring Portfast
Access2(config)#interface range fa 0/10 - 24
Access2(config-if-range)#switchport mode access
<Previously configured>
Access2(config-if-range)#spanning-tree portfast
OR
Access2(config)#spanning-tree portfast default
47 RickGraziani
graziani@cab
Rapid Spanning Tree Protocol
802.1D 802.1w
vs
• The Cisco Catalyst family of switches supports two types of link aggregation:
– Port Aggregation Protocol (PAgP) - Cisco proprietary
• Default when port channel is created (coming)
– Link Aggregation Control Protocol (LACP) - Industry standard 802.3ad-based
protocol
• EtherChannel provides redundancy.
– If one link fails traffic is automatically moved to an active link.
– Transparent to end user.
– LACP (coming) also allows for standby links (coming).
Fast Ethernet EtherChannel Fast Ethernet
Full duplex Full duplex
Dot1q auto Dot1q auto
Native = VLAN 2 Native = VLAN 2
VLANs 1 thru 100 VLANs 1 thru 100
6500 and 4500 switches also allow hash input to be based on:
dst-port (destination port)
src-dst-port (source and destination ports)
Dafaults for 29xx and 35xx (this may vary so check documentation)
Layer 2 switching (switched port) is src-mac (coming)
Layer 3 switching (routed port) is src-dst-ip (coming)
For non-IP traffic the switch will distribute frames based on MAC
addresses.
Multicasts and broadcasts sent over one link in the EtherChannel are not
sent back over other links in the EtherChannel.
Switch(config)# port-channel load-balance ?
Load dst-ip
dst-mac
src-dst-ip
Dst IP Addr
Dst Mac Addr
Src XOR Dst IP Addr
bits
bits
XOR
PAgP
LACP PAgP
LACP
Fa0/4
Fa0/4
Channel-group number: 1 – 64
Does not need to be the same on both switches but its
recommended that it usually is.
No PAgP or LACP negotiation
EtherChannel
on on
auto desirable
By default PAgP uses the silent submode for desirable and auto.
If you expect a switch to be on the other end you should use non-silent.
“Use the non-silent keyword when you connect to a device that transmits bridge protocol data units
(BPDUs) or other traffic.”
“Use the silent keyword when you connect to a silent partner (which is a device that does not generate
BPDUs or other traffic).”
Either will work between switches.
For more information on when to use silent or non-silent:
http://www.cisco.com/en/US/tech/tk389/tk213/technologies_configuration_example09186a0080094953.s
html
LACP modes
EtherChannel
active
active
passive
passive active
on on
auto
passive
Configuring PAgP
DLS1(config)# port-channel load-balance dst-ip
DLS1(config)# interface range fa 0/11 - 12
DLS1(config-if-range)# switchport trunk encapsulation dot1q
DLS1(config-if-range)# switchport mode trunk
DLS1(config-if-range)# channel-protocol pagp
DLS1(config-if-range)# channel-group 1 mode desirable
Notice:
Load balancing does not have to match but usually it does.
DTP on DLS2 is dyanmic auto (result is trunk with DLS1)
PAgP configured on both ends
VERIFING
DLS1#show run DLS2#show run
! !
port-channel load-balance dst-ip port-channel load-balance src-dst-ip
! !
interface Port-channel1 interface Port-channel1
switchport trunk encapsulation dot1q switchport trunk encapsulation dot1q
switchport mode trunk !
! !
interface FastEthernet0/1 interface FastEthernet0/1
! ... ! ...
interface FastEthernet0/11 interface FastEthernet0/11
switchport trunk encapsulation dot1q switchport trunk encapsulation dot1q
switchport mode trunk channel-group 1 mode auto
channel-group 1 mode desirable !
! !
interface FastEthernet0/12 interface FastEthernet0/12
switchport trunk encapsulation dot1q switchport trunk encapsulation dot1q
switchport mode trunk channel-group 1 mode auto
channel-group 1 mode desirable
Verifying
DLS1# show etherchannel protocol
Group: 1
----------
Protocol: PAgP
Partner's information:
Port: Fa0/12
------------
...
Configuring LACP
DLS1(config)# port-channel load-balance dst-ip
DLS1(config)# lacp system-priority 11111
Fa0/13-14 has a
DLS1(config)# interface range fa 0/11 - 12
DLS1(config-if-range)# switchport trunk encapsulation dot1q
higher port priority
DLS1(config-if-range)# switchport mode trunk so these will
DLS1(config-if-range)# channel-protocol lacp become the
DLS1(config-if-range)# channel-group 1 mode active standby links
DLS1(config-if-range)# lacp port-priority 99 should something
happen to any of
DLS1(config)# interface range fa 0/13 - 14
the active links.
DLS1(config-if-range)# switchport trunk encapsulation dot1q
DLS1(config-if-range)# switchport mode trunk
Default port-priority = 32,768
DLS1(config-if-range)# channel-protocol lacp
DLS1(config-if-range)# channel-group 1 mode active
Group: 1
----------
Protocol: LACP
DLS1#