PAgP Silent/Non-silent Mode

PAgP模式解析
本文通过实验证明了PAgP(Port Aggregation Protocol)在默认情况下的运行模式:desirable模式为非静默模式,而auto模式为静默模式。这一发现纠正了官方文档中的错误,并解释了静默模式的作用及应用场景。

Time to bust another myth! Supposedly PAgP runs in silent mode by default
in both desirable and auto mode. So what does silent mode do?

“Use the silent mode when the switch is connected to a device that is not PAgP-capable
and seldom, if ever, sends packets. An example of a silent partner is a file server
or a packet analyzer that is not generating traffic. In this case, running PAgP on a
physical port connected to a silent partner prevents that switch port from ever becoming
operational. However, the silent setting allows PAgP to operate, to attach the port to a
channel group, and to use the port for transmission.”

So now for the myth itself. The first quote is from David Hucabys CCNP SWITCH 642-813
Official Certification Guide.

“By default, PAgP operates in silent submode with the desirable and auto modes, and
allows ports to be added to an EtherChannel even if the other end of the link is silent
and never transmits PAgP packets. This might seem to go against the idea of PAgP,
in which two endpoints are supposed to negotiate a channel. After all, how can two
switches negotiate anything if no PAgP packets are received?”

And then from the Cisco configuration guide for 3560 12.12(58)SE.

“If your switch is connected to a partner that is PAgP-capable, you can configure the
switch port for nonsilent operation by using the non-silent keyword. If you do not specify
non-silent with the auto or desirable mode, silent mode is assumed.”

So even Cisco themselves claim that both modes operate in silent mode. Surely Cisco
can’t be wrong?! Doesn’t it seem strange to operate in silent mode by default? The
most common use must be to connect to other switches?

To test this we setup two switches with two trunks between themselves. One side is
set to auto and one side is set to desirable. Then debug pagp all is run to check
what mode they are running in.

SW1(config)#int range f0/13 - 14
SW1(config-if-range)#sh
SW1(config-if-range)#channel-group 1 mode des
SW2(config)#int range f0/13 - 14
SW2(config-if-range)#sh
SW2(config-if-range)#channel-group 1 mode auto
PAgP: Fa0/13 enabling PAgP with mode desirable-nonsl
PAgP: set hello interval from 0 to 1000 for port Fa0/13 
PAgP: Fa0/14 enabling PAgP with mode desirable-nonsl
PAgP: set hello interval from 0 to 1000 for port Fa0/14 
PAgP: Fa0/13 enabling PAgP with mode auto-sl
PAgP: set hello interval from 0 to 1000 for port Fa0/13
PAgP: Fa0/14 enabling PAgP with mode auto-sl
PAgP: set hello interval from 0 to 1000 for port Fa0/14

Myth busted! Desirable runs in non silent mode but auto runs in silent mode.
So this myth exist book in official certification books and in Ciscos documents
which is bad. I’ll look into getting it update if I can. The point of forming
an etherchannel is to negotiate with the other side before forming it to make
sure that the links are not unidirectional and that they agree on all parameters.


http://lostintransit.se/2013/08/14/busting-myths-pagp-desirable-runs-in-silent-mode-by-default/


Building configuration... Current configuration : 1495 bytes ! version 15.0 no service timestamps log datetime msec no service timestamps debug datetime msec no service password-encryption ! hostname SW1 ! ! ! ! ! ! spanning-tree mode pvst spanning-tree extend system-id spanning-tree vlan 1 priority 24576 ! interface Port-channel1 switchport trunk allowed vlan 1,10,20,1002-1005 ! interface Port-channel2 switchport trunk allowed vlan 1,10,20,1002-1005 ! interface FastEthernet0/1 channel-group 1 mode active ! interface FastEthernet0/2 channel-group 1 mode active ! interface FastEthernet0/3 ! interface FastEthernet0/4 ! interface FastEthernet0/5 ! interface FastEthernet0/6 ! interface FastEthernet0/7 ! interface FastEthernet0/8 ! interface FastEthernet0/9 ! interface FastEthernet0/10 ! interface FastEthernet0/11 ! interface FastEthernet0/12 ! interface FastEthernet0/13 ! interface FastEthernet0/14 ! interface FastEthernet0/15 ! interface FastEthernet0/16 ! interface FastEthernet0/17 ! interface FastEthernet0/18 ! interface FastEthernet0/19 ! interface FastEthernet0/20 ! interface FastEthernet0/21 ! interface FastEthernet0/22 ! interface FastEthernet0/23 ! interface FastEthernet0/24 ! interface GigabitEthernet0/1 channel-group 2 mode active ! interface GigabitEthernet0/2 channel-group 2 mode active ! interface Vlan1 no ip address shutdown ! interface Vlan10 ip address 192.168.10.1 255.255.255.0 ! interface Vlan20 ip address 192.168.20.1 255.255.255.0 ! ! ! ! line con 0 ! line vty 0 4 login line vty 5 15 login ! ! ! ! end 配置了端口聚合,vlan也配置了ip,为什么ping不通?
最新发布
06-14
作业/作品类 题目: 端口聚合(又称为链路聚合),将交换机上的多个端口在物理上连接起来,在逻辑上捆绑在一起,形成一个拥有较大宽带的端口,可以实现负载分担,并提供冗余链路。 交换机的端口聚合配置 (一)任务准备 Cisio packet tracer:Switch_2960 2台;PC 4台;直连线 (二)实训操作 端口聚合使用的是EtherChannel特性,在交换机到交换机之间提供冗余的高速的连接方式。将两个设备之间多条FastEthernet或GigabitEthernet物理链路捆在一起组成一条设备间逻辑链路,从而增强带宽,提供冗余。 两台交换机到计算机的速率都是100M,SW1和SW2之间虽有两条100M的物理通道相连,可由于生成树的原因,只有100M可用,交换机之间的链路很容易形成瓶颈,使用端口聚合技术,把两个100M链路聚合成一个200M的逻辑链路,当一条链路出现故障,另一条链路会继续工作。 视图:全局配置模式下 命令: interface range interface_name1 to interface_name2 Switchport mode trunk channel-group 1 mode on 加入链路组1并开启 参数: interface_name1:聚合起始端口 interface_name2:聚合结束端口。 trunk表示端口可以转发所有Vlan包 将2个或多个物理端口组合在一起成为一条逻辑的路径 ,即链路channel-group,同时也形成了一个逻辑端口port-channel(一个整体) switchport mode access是直接接主机的,所属VLAN中的接口,都是access switchport mode trunk trunk mode 的接口可以同时传输多个VLAN信息的。 trunk mode 常用在两个SWITCH and  ROUTER , switch and switch 特权模式下 Switch#show etherchannel summary:显示相关汇聚端口组的信息; (三)成果展示 Switch0:具体操作 Switch> Switch#config t Switch(config)#interface range f0/1-2 Switch(config
04-17
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值