Edge ports and server links: You plan to connect a server on an access port and do not want STP delays on link-up. Which Cisco command should you use on that interface (safe edge behavior, not a global disable)?

Introduction / Context:
Servers and endpoints benefit from immediate forwarding on link-up. Waiting through STP listening/learning states delays DHCP and application startup. Cisco provides a safe edge optimization called PortFast for access ports that are not expected to form loops.

Given Data / Assumptions:

• The port connects to a single server (no switch behind it).
• We want to avoid the normal STP delay but not disable loop protection across the network.
• The correct solution is interface-level.

Concept / Approach:
spanning-tree portfast transitions the port quickly to forwarding while still allowing STP to protect against loops (BPDU Guard can be added for safety). Disabling STP entirely is dangerous and not recommended.

Step-by-Step Solution:

Verification / Alternative check:
Observe immediate forwarding on link-up and successful client DHCP without delay. If a switch is inadvertently connected, BPDU Guard will err-disable the port.

Why Other Options Are Wrong:

• Global or interface commands to “turn off” STP are unsafe and often invalid syntax.
• spanning-tree security is not a valid command.
• no spanning-tree vlan 1 disables STP for a VLAN globally—risky and not the intent.

Common Pitfalls:
Confusing PortFast with disabling STP; forgetting BPDU Guard on edge ports.

Final Answer:
spanning-tree portfast