Have a look at attachment,there is a 2950 24 port switch , which is connected to 8274 ibm core switch via ethernet.The 2950 has two fibre modules connected to 4507 switch with hsrp and etherchannel configured.
The 2950 switch ethernet link connected to 8274 ibm core switch is
fluctuating. at rare cases the ethernet led truns amber and link goes down for few seconds.
On observing the 2950 switch, it was found that there is no issue
with the hardware , It is a BPDU problem , where BPDU packets are
being generated by both data centre switch and IBM core switch. Any
one of the BPDU has to be blocked inorder to avoid the link failure.
The following commands were tested in the cisco 2950 switch .
1. Spanning-tree Port fast has been enabled.(for testing purpose)
2. Spanning-tree portfast bpdufilter default.
3. Making fastethernet 0/1 as trunklink.
4. Changing Spanningtree priority value.
5. Enabling Spanningtree gaurd root.
The Ethernet port of 8274 IBM core switch connecting 2950 switch has to be
made as trunk, since it is an uplink to 2950 switch..it is not yet checked as we dont have access to ibm switch.
it is sure that only configuration changes has to be done at 2950 side, since hardware has been replaced last before week and old conf is missing, earlier it was working setup.
i have pasted the error message,configuration details of 2950 switch.
1w3d: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk
1w3d: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking FastEthernet0/1 on VLAN0001.
stent port type.
1w3d: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking FastEthernet0/1 on
Error Message: SPANTREE-7-RECV-1Q-NON-TRUNK: Received 802.1Q BPDU on non trunk
Note: This message applies to Catalyst 3550, 2955, 2950, and 2940 switches.
Explanation: An SSTP bridge protocol data units (BPDU) was received on the listed interface, which is not an operational trunking interface. The first [chars] is the port name, and the second [chars] is the VLAN name.
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). When these parameters are consistent, spanning tree automatically unblocks the interface.
Looks like the IBM is sending DTP in which the fa0/1 becomes trunk and switch unblock the port and removes the inconsistency. Follow the recommendation above.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...