spanning-tree portfast should be enabled only on access-ports that connect to workstations because enabling them on trunk ports could cause accidental STP loops. That being said there are situation in which you connect to end servers with a trunk port & you dont want that port to go through the usual 50 sec delay in STP state transistions. For such cases we can enable 'stp portfast trunk' on a trunk port which would cause the trunk to behave exactly as a access port connected to a workstation skipping the STP delay.
I would recommend removing the command from the interface if possible. You could run into some serious problems in the future using portfast on an uplink. More than likely someone put it there for faster convergence when/if the link went down.
I have to agree with Mark with an addition, if you want faster convergance in case of a primary uplink failure - then portfast it not the solution. You might want to consider running RPVST or enabling uplinkfast for fast convergance in a failure situation.
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...