04-24-2019 03:24 PM
We've pushed configs, changing interfaces from phone ports to access and 802.1q trunk ports, yet certain statements remain. Here is an example after going from phone to access:
voice vlan X
voice vlan dscp 46
classofservice trust untrusted
description 'VLAN X'
switchport mode access
switchport access vlan X
vlan pvid XX
vlan participation exclude 1
vlan participation include XX,YY
vlan tagging XX
poe detection 4ptdot3af+legacy
We've been able to remove the following with prepending "no" statements:
no voice vlan
no voice vlan dscp
no vlan pvid XX
no vlan tagging
We've not found a way to remove:
vlan participation exclude 1
vlan participation include XX,YY
Any suggestions?
07-03-2019 03:43 AM
Hi BJ,
You can use something like "vlan participation auto <vlan id>" to revert this setting to default. From example, the following is from my test:
"
(s3-stack) #show running-config interface 1/0/3
!Current Configuration:
!
interface 1/0/3
classofservice trust untrusted
description 'Default settings for the trunk port'
switchport mode trunk
vlan participation include 200,300
poe detection 4ptdot3af+legacy
exit
(s3-stack) #configure
(s3-stack) (Config)#interface 1/0/3
(s3-stack) (Interface 1/0/3)#vlan participation auto 200,300
(s3-stack) (Interface 1/0/3)#show running-config interface 1/0/3
!Current Configuration:
!
interface 1/0/3
classofservice trust untrusted
description 'Default settings for the trunk port'
switchport mode trunk
poe detection 4ptdot3af+legacy
exit
(s3-stack) (Interface 1/0/3)#
"
I've updated the case for this as well.
Paul
05-23-2019 12:37 PM
Of course, the case has been moved to our Tier 2 team, I've increased the priority on the case given how long it's been open, and I've messaged the Tier 2 manager to make sure the case gets more attention. Please don't hesitate to let me know if the case keeps stalling at this level and we'll get it up to our highest level of technicians for you.
05-23-2019 07:21 AM
Sam,
Can you help escalate case # 00271031 regarding this issue?
Thanks,
BJ
05-01-2019 06:34 PM
Thanks for your patience here, sorry for the long wait. The closest I've been able to get is to remove the VLAN from the database with:
(Enable) Vlan database
No vlan #
However that would remove any other VLAN settings as well. I spoke with our senior engineers and they weren't able to find the command either but they did suggest opening a case on this question so they can dig in to it further, if you're interested. If we do open a case, we'd want a screen shot of the no command failing, tech data from the switch for background info, and we'd want to make sure we were using the latest firmware version available, then we can get the case to our experts for you.