I have the following port configuration
switchport access vlan 192
switchport mode access
switchport voice vlan 160
no logging event link-status
srr-queue bandwidth share 10 10 60 20
authentication control-direction in
authentication event no-response action authorize vlan 180
authentication host-mode multi-domain
authentication port-control auto
authentication violation protect
mls qos trust cos
no snmp trap link-status
snmp ifindex persist
auto qos voip trust
dot1x pae authenticator
dot1x timeout quiet-period 1
dot1x timeout tx-period 1
dot1x timeout supp-timeout 10
dot1x max-req 1
but somehow the line "switchport access vlan 192" changen to "switchport access vlan 0".
does anybody know why this happens? it needs to stay on 192 for Wake on Lan.
I think this wil answer your question. Thanks
Cisco IOS Software, C3750 Software (C3750-IPBASE-M), Version 12.2(50)SE3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 22-Jul-09 06:19 by prod_rel_team
Image text-base: 0x01000000, data-base: 0x02800000
ROM: Bootstrap program is C3750 boot loader
BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.2(44)SE5, RELEASE SOFTWARE (fc1)
vlan 0 is used internally, this is the reason why Yogesh asked you to provide information on switch model and IOS image running on it, probably to perfrom a bug search
Hope to help
we are moving from vmps to 802.1x.
so the answer is yes. it was dynamic
is it a known issue?
ps. it looks like alles the "switchport acces vlan" lines change to another vlan
Actually the bug I was looking at should already be fixed in the code
you are running. I was looking at your bootldr image, not your IOS.
Can you open a new TAC case for this? We need to look at this further.
thank you for your reply, just to be on the safe side I will upgrade my ios to a newer version.If the problem persists, my supplier will make a TAC case. I have no rights to do this.
I'll keep you informed.
I've updated to version 12.2(55)SE
it seems it has been solved. although I've just installed it yesterday. I'll update the information in about a week
after a couple of weeks, everything seems to work normale. so the update to 12.2.55 seems to have solved it. 12.2.50se4 didn't solve it.