A switch port in a blocking state can be caused by a few things.
The obvious one is a loop in the network has been prevented by spanning-tree. Do you have another uplink on that switch going back to the root bridge? This is likely your issue, or non-issue since spanning-tree is likely working properly.
I have also seen ports that were not set to access mode react when connected to interfaces that were bridging DLSW+ and other protocols. Take them out of dynamic trunking if they aren't supposed to be trunks.
You can also perform a "show interface status" to make sure the port isn't administratively down or in the error-disabled state.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...