Voice endpoints loop only on ports cloned from an older access template.
A VLAN migration completes and one voice subnet loops because inherited LLDP-MED still advertises the old VLAN
Switchport mode is correct, but phones keep learning the retired voice VLAN from an inherited policy profile.
Scenario
What to check first
- Identify the primary failure signal in the The Port Moved to the New Neighborhood and the Phone Kept Listening to the Old Welcome Speech scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Compare effective LLDP-MED policy before editing trunks.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field