New switch stack forms but VLAN tagging is inconsistent

Minimal guidance for messy support realities.

Scenario

After adding a switch to a stack, some ports land in the wrong VLAN or lose trunk configuration unexpectedly.

Recommended Resolution Path

  1. Audit the stack member role, startup config, and interface inheritance after the join.
  2. Compare running and startup configuration so you know whether the drift survives reboot.
  3. Test representative access and trunk ports before reconnecting every endpoint.
  4. Save and archive the corrected config once port behavior is consistent again.

Technician Notes

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.