In the previous post we have discussed about fundamental of etherchannel and prerequisite details of etherchannel prior to its configuration. etherchannel simply means, its a technology which allows multiple physical links combines together to form one logical interface, from switch STP perspective this logical interface is treated as single link or port.
Today we will practically illustrating the etherchannel configuration, before that its important to bring here out for your knowledge that ether channel can configure through two different methods.
1. manual configuration
2. dynamic confirmation,
Manual configuration is very straight forward and no negotiation packets are used to form etherchannel. Hence etherchannel will never form if you configured one switch manually and other switch with dynamic configuration by using PAgP or LACP protocol. Config command is very simple.
SW1(config)#int range fas0/1 - 2
In the later case, dynamic configuration can be done through two different protocols,
1. PAgP -->cisco proprietary protocol and only support on cisco switches which is called Port Aggregation Protocol.And it is not compatible with LACP protocol. PAgP supports two mode.
Channel will never form if both switch channel mode is configured as Auto,Today we will practically illustrating the etherchannel configuration, before that its important to bring here out for your knowledge that ether channel can configure through two different methods.
1. manual configuration
2. dynamic confirmation,
Manual configuration is very straight forward and no negotiation packets are used to form etherchannel. Hence etherchannel will never form if you configured one switch manually and other switch with dynamic configuration by using PAgP or LACP protocol. Config command is very simple.
SW1(config)#int range fas0/1 - 2
SW1(config-if-range)#channel-group 1 mode on
SW1(config-if-range)#
SW2(config)#int range fas0/1 - 2
SW2(config-if-range)#channel-group 1 mode on
SW2(config-if-range)#
In the later case, dynamic configuration can be done through two different protocols,
1. PAgP -->cisco proprietary protocol and only support on cisco switches which is called Port Aggregation Protocol.And it is not compatible with LACP protocol. PAgP supports two mode.
- Desireable mode -- means actively sending nagotiation packets and attempt to form a channel.
- Auto mode --- Means actively waiting for remote or other switch to form a channel.
- desirable --- desirable both switch channel mode is configured as Desirable.
- desirable----auto one of switch channel mode is desirable and auto in other end..
- auto -- auto because auto means simply waiting for remote switch to form channel.
SW1(config)#int range fas0/1 - 2
SW1(config-if-range)#channel-protocol pagp
SW1(config-if-range)#channel-group 1 mode desirable
SW1(config-if-range)#
SW2(config)#int range fas0/1 - 2
SW2(config-if-range)#channel-protocol pagp
SW2(config-if-range)#channel-group 1 mode auto
SW2(config-if-range)#
2. LACP (802.3ad)--> Open standard aggregation protocol developed by IEEE, which is supported between multi-vendor switches and is called Link Aggregation Control Protocol. Its also operates on two different mode.
- Active mode --> in this mode, switch is actively sending negotiation packets and form a channel.
- Passive mode--> in this mode switch is simply waiting other switch to form a channel.
- active -- active both switch channel mode is configured as active.
- active -- passive one switch with channel mode active and passive on other switch.
- Passive -- passive in this mode, both switches waiting remote switch to form a channel.
SW1(config)#int range fas0/1 - 2
SW1(config-if-range)#channel-protocol lacp
SW1(config-if-range)#channel-group 1 mode active
SW1(config-if-range)#
SW2(config-if-range)#channel-protocol lacp
SW2(config-if-range)#channel-group 1 mode passive
SW2(config-if-range)#
Actual etherchannel configuration setup..
SW1 VLAN configuration..
interface FastEthernet0/3
switchport access vlan 50
switchport mode access
!
interface FastEthernet0/4
switchport access vlan 60
switchport mode access
interface Vlan50
ip address 10.10.10.1 255.255.255.0
!
interface Vlan60
ip address 20.20.20.1 255.255.255.0
switchport access vlan 50
switchport mode access
!
interface FastEthernet0/4
switchport access vlan 60
switchport mode access
interface Vlan50
ip address 10.10.10.1 255.255.255.0
!
interface Vlan60
ip address 20.20.20.1 255.255.255.0
etherchannel configuration! we have configured PAgP as aggregation protocol in this scenerio.
SW1(config-if-range)#channel-protocol pagp
SW1(config-if-range)#channel-group 1 mode desirable
SW1(config-if-range)#
Trunk configuration over etherchannel link. by default , dot1Q is used as encapsulation protocol.
SW1(config-if)#switchport mode trunk
SW1(config-if)#switchport trunk allowed vlan 50,60
SW2 vlan configuration.
interface FastEthernet0/3
switchport access vlan 50
switchport mode access
!
interface FastEthernet0/4
switchport access vlan 60
switchport mode access
interface Vlan50
ip address 10.10.10.100 255.255.255.0
!
interface Vlan60
ip address 20.20.20.100 255.255.255.0
etherchannel configuration! we have configured PAgP as aggregation protocol in this scenerio.
SW2(config-if-range)#channel-protocol pagp
SW2(config-if-range)#channel-group 1 mode desirable
SW2(config-if-range)#
Trunk configuration over etherchannel link. by default , dot1Q is used as encapsulation protocol.
SW2(config-if)#switchport mode trunk
SW2(config-if)#switchport trunk allowed vlan 50,60
If you wished to configure port-channel as a layer3 interface,then
SW1#int port-channel 1
SW1#no switch-port
SW1#ip add 192.168.0.1 255.255.255.0
To add port-channel in Vlan
SW1#vlan 200
SW1#int port-channel 1
SW1#switchport mode access
SW1# switchport access vlan 200
Both interface fas0/1 and fas0/2 are participating in etherchannel.
SW1#sh etherchannel port-channel
Channel-group listing:
----------------------
Group: 1
----------
Port-channels in the group:
---------------------------
Port-channel: Po1
------------
Age of the Port-channel = 00d:02h:19m:01s
Logical slot/port = 2/1 Number of ports = 2
GC = 0x00000000 HotStandBy port = null
Port state = Port-channel
Protocol = PAGP
Port Security = Disabled
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+------------------+-----------
0 00 Fa0/1 On 0
0 00 Fa0/2 On 0
Time since last port bundled: 00d:02h:02m:57s Fa0/2
Below etherchannel summary status , we came to know that etherchannel is properly formed, indicated by "P" letter.
SW1#sh etherchannel summary
Flags: D - down P - in port-channel
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+----------------------------------------------
1 Po1(SU) - Fa0/1(P) Fa0/2(P)
Trunk Link verification on both switches..
SW1#sh interfaces trunk
Port Mode Encapsulation Status Native vlan
Po1 on 802.1q trunking 1
Port Vlans allowed on trunk
Po1 50,60
Port Vlans allowed and active in management domain
Po1 50,60
Port Vlans in spanning tree forwarding state and not pruned
Po1 50,60
From above result, both VLAN 50 and 60 are allowed on trunk link and is in forwarding state.
STP on these two switches are currently operated in PVST.
connectivity verification,
pinging from PC1 to PC3, both are in same vlan but in different switch.
Reachbility from PC4 to PC2
PC4>ping 20.20.20.2
SW1#sh spanning-tree summary
Switch is in pvst mode
Root bridge for: default VLAN0050 VLAN0060
Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN0001 0 0 0 3 3
VLAN0050 0 1 0 4 5
VLAN0060 0 0 0 4 4
---------------------- -------- --------- -------- ---------- ----------
3 vlans 0 1 0 11 12.
connectivity verification,
pinging from PC1 to PC3, both are in same vlan but in different switch.
PC1>ping 10.10.10.101
Pinging 10.10.10.101 with 32 bytes of data:
Reply from 10.10.10.101: bytes=32 time=1ms TTL=128
Reply from 10.10.10.101: bytes=32 time=0ms TTL=128
Reply from 10.10.10.101: bytes=32 time=0ms TTL=128
Reply from 10.10.10.101: bytes=32 time=1ms TTL=128
Ping statistics for 10.10.10.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Reachbility from PC4 to PC2
PC4>ping 20.20.20.2
Pinging 20.20.20.2 with 32 bytes of data:
Reply from 20.20.20.2: bytes=32 time=1ms TTL=128
Reply from 20.20.20.2: bytes=32 time=1ms TTL=128
Reply from 20.20.20.2: bytes=32 time=0ms TTL=128
Reply from 20.20.20.2: bytes=32 time=0ms TTL=128
Ping statistics for 20.20.20.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
No comments:
Post a Comment