We are having a problem with our WISP and I can’t figure out why it’s failing.
We have 5 ePMP3000 APs connected to a cnMatrix EX1028-P switch. When the problem occurs, all the devices (APs + Switch) remain offline without connection/management
To solve it we do the following:
The technician goes to the site and disconnects and connects everything again. First connect the switch being ok. Then he starts putting the APs
Progressively, connect one, wait 10 minutes and connect the next one. When you connect the conflicting AP, all the equipment stop responding and
they are left unmanaged. They disconnect the AP that is in conflict and it responds all over again.
Once the conflicting AP is identified, all clients are filtered to deny their connection. In this scenario, the AP remains online and does not generate a conflict in the network.
Clients are allowed one by one and when the client that generates the failure is allowed, the entire network goes down as at the beginning.
Said client is left filtered and the network is normalized.
It has already happened on 3 different occasions, with different clients. No errors are seen in the APs and switch logs.
Both APs and SM are in bridge mode.
These are the software versions:
ePMP3000 SW Version 4.6.2
Switch EX1028-P SW Version 4.4-r3
Subscriber
Force190 SW Version 4.6.2
Force200 SW Version 4.6.2
Force 300-25 SW Version 4.6.2
I have seen similar issues when SM is in bridge mode and a client plugs into the LAN port of the router instead of the WAN port. Most of my SMs are in NAT mode to prevent this from happening.
Sounds like som sort of IP conflict but could be sometign else. Always enable client isolation in the AP’s and enable DHCP snooping on the ports that face the client APs, if the switch is capable of doing that. Is it just one AP that affects the whole network? if so what is unique about that one AP? thats why I suggested to check for an IP conflict. If that one AP has an ip say 192.168.1.20 unplug it and see if you can still ping 192.168.1.20 if you can then there is your answer as that tells you there is something else on your network with the same IP as the AP.
Check the confilicting AP’s IP address and make sure it is correct and that nothing else responds to that IP when the AP is not connected.
Without more information about how you have your network built, it is really hard to provide any good advice. If you need more help and dont want to post the information publicly, PM me directly and I can help you.
Some clients connect their own Wi-Fi router and in other clients we provide the Wi-Fi router but we do not have management over them.
I am going to NAT mode to all the clients to see if the network stabilizes.
The strange thing is these messages that I see in the switch log, there seems to be a layer2 problem
<134>Jan 26 17:57:08 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:4d:bb:27 from the port 5 to the port :6
<134>Jan 26 17:57:46 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:bd:03:69 from the port 4 to the port :6
<134>Jan 26 17:58:03 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 17:58:03 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 17:58:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 17:58:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 17:58:27 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 17:58:27 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 17:58:32 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 17:58:32 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 17:58:44 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 17:58:44 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 17:58:49 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:4d:bb:27 from the port 6 to the port :5
<134>Jan 26 17:59:08 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :5
<134>Jan 26 17:59:08 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 5 to the port :25
<134>Jan 26 17:59:08 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 5 to the port :25
<134>Jan 26 17:59:09 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :5
<134>Jan 26 17:59:09 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 5 to the port :25
<134>Jan 26 17:59:11 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 5 to the port :25
<134>Jan 26 17:59:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :5
<134>Jan 26 17:59:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 5 to the port :25
<134>Jan 26 17:59:48 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 17:59:48 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 18:00:48 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:4d:bb:27 from the port 5 to the port :6
<134>Jan 26 18:01:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:b1:4f:bb from the port 25 to the port :3
<134>Jan 26 18:01:23 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:4d:bb:27 from the port 6 to the port :5
<134>Jan 26 18:01:41 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:bd:03:69 from the port 6 to the port :4
<134>Jan 26 18:01:55 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address 58:c1:7a:bd:03:69 from the port 4 to the port :6
<134>Jan 26 18:02:05 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 18:02:05 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 18:02:38 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 18:02:38 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 18:02:42 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 18:02:42 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 18:03:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 18:03:12 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 18:03:18 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
<134>Jan 26 18:03:18 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 4 to the port :25
<134>Jan 26 18:03:44 ISS VLAN: VLAN: Source relearning has Occurred for Mac Address d8:18:d3:65:c1:40 from the port 25 to the port :4
Thank you @accelwireless !!
I am going to NAT mode to all the clients to see if the network stabilizes.
The strange thing is these messages that I see in the switch log, there seems to be a layer2 problem.
it is not a layer 2 issue, its informing you that the same mac address is moving between ports on the switch. This is indicative of a loop or a spanning tree issue.