09-16-2025 04:50 AM
hi..
i'm getting the following error
%SWPORT-4-MAC_CONFLICT: Chassis 1 F0: cpp_cp_svr: Dynamic mac B827.EB64.23F0 from GigabitEthernet2 conflict with WlClient, please check the network topology and make sure there is no loop.QFP:0.0 Thread:000 TS:00000006079705458006
but the device is still able to connect to ssid, i'm using a virtual controller that has the AP's on the same vlan as the gi2
it's a simple setup, we have other catalyst controller in different version on different vlans where each vlan also has the ap's meant for that controller (it's a lap setup)
in recent catalyst versions 17.12+ we had to make additional flex configuration to make the devices join the ssid, and i'm not sure why that was needed.
! interface GigabitEthernet1 no switchport ip address 192.168.64.96 255.255.255.0 negotiation auto ! interface GigabitEthernet2 switchport access vlan 107 switchport mode access negotiation auto ! interface GigabitEthernet3 negotiation auto ! interface Vlan1 no ip address ! interface Vlan107 ip address 192.168.107.61 255.255.255.0 ! ip forward-protocol nd ip forward-protocol udp ip http server ip http authentication local ip http secure-server ! ip route 0.0.0.0 0.0.0.0 GigabitEthernet1 192.168.64.1 ip ssh bulk-mode 131072 ip ssh rsa keypair-name ssh-key ip scp server enable
wireless profile flex default-flex-profile
description "default flex profile"
ip http client proxy 0.0.0.0 0
native-vlan-id 107
vlan-name VLAN0107
vlan-id 107
09-16-2025 05:05 AM
Not sure you hitting with Bug, (since you are 17.12 that should fix the issue)
check some workaround, also try moving to different VLAN
https://bst.cisco.com/bugsearch/bug/CSCvt96686
still issue contact TAC for suggest.
09-16-2025 05:11 AM
my main question is why did we need to configure flex profile to have vlan translation from id to name and change the native vlan from 1 to vlan id ? (in the past we didn't need to)
09-16-2025 05:09 AM
This C1000 SW?
MHM
09-16-2025 05:10 AM
no , virtual cisco catalyst 9800 17.18.1
09-16-2025 05:46 AM
09-16-2025 05:48 AM
""If there is another wireless controller in the network running in parallel with 9800, shut it down. Messages should stop appearing.""
MHM
09-16-2025 06:35 AM
there are like 3 or 4 of those controllers but each one has their own ssid and their own vlan.
09-16-2025 06:43 AM
Their own Vlan, you meaning each wlc have it wmi in different vlan?
MHM
09-16-2025 07:04 AM
yes. i have 17.9.4 catalyst on vlan-70 , 17.18.1 on vlan-107 , another on vlan-108, each one's gi2 port is on an svi for that vlan
however their gi1 is all on the same vlan of 64 and they all have this.
ip route 0.0.0.0 0.0.0.0 GigabitEthernet1 192.168.64.1
09-16-2025 07:25 AM
Each WLC have it vlan but use same subnet ?
MHM
09-16-2025 07:31 AM
in our case a vlan is same as subnet meaning
WLC x has 2 interfaces
gi1 out of band, has static IP, is connected to vlan-64 , has static ip 192.168.64.1
gi2 WMI has an svi connected to either vlan107,vlan108,vlan70 (which would be 192.168.107.x,192.168.108.x,192.168.70.x) depending on the WLC and each of those vlans would have ap's which are meant only for that WLC, the reason i did it this way, is because i wanted to have quickest way to each ap to discover their respective WLC without resorting to IT requests to change something in the DHCP, we can drop and create those controllers to test each version.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide