2950 故障

偏执的太偏执、 2022-01-16 07:21 288阅读 0赞

故障如下：

交换机串接，上行线路断线，局域网内部正常。

处理无果，查看cisco交换机日志如下。

00:57:51: %SPANTREE-7-RECV\_1Q\_NON\_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/21 VLAN1.  
00:57:51: %SPANTREE-7-BLOCK\_PORT\_TYPE: Blocking FastEthernet0/21 on VLAN0001. Inconsistent port type.  
00:58:06: %SPANTREE-2-UNBLOCK\_CONSIST\_PORT: Unblocking FastEthernet0/21 on VLAN0001. Port consistency restored.$ON\_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/21 VLAN1.

配置：

\#interface FastEthernet0/24  
\#spanning-tree bpdufilter enable

===============================以下为摘录合集=================

网络接入一个思科3560交换机(不做配置),不过碰到一个很怪的问题,连到某个交换机,3560的相关端口不会变正常,因为没设备调试,后来就改用TRUNK可以互连.

交换机提示:  
01:48:44: %SPANTREE-7-RECV\_1Q\_NON\_TRUNK: Received 802.1Q BPDU on non trunk FastE  
thernet0/8 VLAN1.  
01:48:44: %SPANTREE-7-BLOCK\_PORT\_TYPE: Blocking FastEthernet0/8 on VLAN0001. Inc  
onsistent port type.

这几天来了个新的交换机(也是3560),在网络上试验,发现了一个有趣的现象  
1.连在AVAYA P882上,思科3560指示灯正常  
2.连在思科3750交换机(在网络中使用),思科3560指示灯正常  
3.连在AVAYA P334T-ML或AVAYA P330(在网络中使用),思科3560指示灯不正常,与上面的问题一样  
4.连在单独AVAYA P334T-ML(不与其他交换机连),思科3560指示灯正常

根据初步分析,交换机提示:01:48:44: %SPANTREE-7-RECV\_1Q\_NON\_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/8 VLAN1.可能是端口受到某些BPDU信息后自行关闭.  
后查了好多资料,其实只要开启BPDU端口信息过屡功能,就完全可以正常接入.不需要对上联交换机的端口做任何设置.

设置方法:

interface FastEthernet0/8  
spanning-tree bpdufilter enable

\-------------------------------------

引用:  
作者: edreamer2006  
在单位的网络接入一个思科3560交换机(不做配置),不过碰到一个很怪的问题,连到某个交换机,3560的相关端口不会变正常,因为没设备调试,后来就改用TRUNK可以互连.

你这样做会把SPANNING TREE 在上连端口DISABLE掉.. 这样真的是在解决问题还是为将来的SPANNING TREE LOOP埋下伏笔? 要么两端起ACCESS LINK, 要么两端起TRUNK LINK, 都可以搞定啊..

\----------------------------------------------

分析日志，应该是S8610发送生成树协议的BPDU数据包，而CISCO2950交换机认为此端口不是trunk端口，于是将此端口block，造成无法交换数据包。  
检查S8610相应的端口配置正常，端口为默认配置，默认为switchport mode access.

于是对2950增加如下命令

no spanning-tree vlan 4  
后问题解决。  
我想非Cisco设备与Cisco设备连接还是有兼容性问题。  
但为什么12.1(6)EA2c版本正常而12.1(22)EA13版本就不正常呢？其中有什么变化？我不知道，等有时间查一下。

0--------------------------------------------------------------------------------------------------------------------

1.Error Message SPANTREE-7-RECV\_1Q\_NON\_TRUNK: Received 802.1Q BPDU on non trunk \[chars\] \[chars\]

Explanation This message indicates that an SSTP BPDU was received on the listed interface, which is  
not an operational trunking interface. \[chars\] is the interface ID.

Recommended Action Verify that the configuration and operational state of the listed interface and  
that of the interface to which it is connected are in the same mode (access or trunk). If the mode  
is trunk, verify that both interfaces have the same encapsulation (none, ISL, or 802.1Q). Once these  
parameters are consistent, spanning tree automatically unblocks the interface as appropriate.

2.Error Message SPANTREE-2-RECV\_PVID\_ERR: Received BPDU with inconsistent peer vlan id \[dec\] on  
\[chars\] \[chars\]

Explanation This message indicates that the listed interface received an SSTP BPDU that is tagged  
with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This error occurs  
when the native VLAN is not consistently configured on both ends of an 802.1Q trunk. \[dec\] is the  
VLAN ID. \[chars\] is the interface ID.

Recommended Action Verify that the configuration of the native VLAN ID is consistent on the  
interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically  
unblocks the interfaces as appropriate.

3.Error Message SPANTREE-2-BLOCK\_PVID\_LOCAL: Blocking \[chars\] on \[chars\] Inconsistent local vlan

Explanation This message indicates that the spanning tree port associated with the listed spanning  
tree instance and interface will be held in spanning tree blocking state until the port VLAN ID  
(PVID) inconsistency is resolved. The listed spanning tree instance is the same one as the native  
VLAN ID on the listed interface. \[chars\] is the spanning tree port ID.

\-----------------------------------------------------------------------------------------------------

在连接ADSL MODEM的2950端口上作no span vlan 1后，问题解决

转载于:https://blog.51cto.com/engtt/262699