I just did some Google searches and turned off Loop Protection in the Devices/Configuration page. So far ok...
On Wed, Jan 25, 2017 at 7:12 PM, Josh Luthman <j...@imaginenetworksllc.com> wrote: > If you DEFINITELY don't have a bridge loop (like two backhauls going to > this tower, both of which go to the same collision domain) you can disable > port 2 from the STP. > > > Josh Luthman > Office: 937-552-2340 <(937)%20552-2340> > Direct: 937-552-2343 <(937)%20552-2343> > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Wed, Jan 25, 2017 at 7:09 PM, James Wilson <ja...@ridgecomms.com> > wrote: > >> I have a very straightforward flat network, no OSPF, etc. >> >> Tonight I started losing connection and traced it back to a Netonix >> switch. The connection is up for a minute then the Netonix switch turns off >> the AF5X's port. >> >> Below is what it's log is saying. I don't understand how the AF 5X >> that's connected to the port can cause a loop. Help! Thanks! :) >> >> >> Jan 25 17:39:37 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 17:42:39 Loop protection: re-enabling port 2 >> >> Jan 25 17:43:38 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 17:46:40 Loop protection: re-enabling port 2 >> >> Jan 25 18:03:04 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:06:05 Loop protection: re-enabling port 2 >> >> Jan 25 18:06:39 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:09:40 Loop protection: re-enabling port 2 >> >> Jan 25 18:15:17 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:18:18 Loop protection: re-enabling port 2 >> >> Jan 25 18:22:19 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:25:21 Loop protection: re-enabling port 2 >> >> Jan 25 18:25:38 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:28:40 Loop protection: re-enabling port 2 >> >> Jan 25 18:34:13 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:37:14 Loop protection: re-enabling port 2 >> >> Jan 25 18:37:22 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:40:24 Loop protection: re-enabling port 2 >> >> Jan 25 18:41:37 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:44:39 Loop protection: re-enabling port 2 >> >> Jan 25 18:45:37 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:48:39 Loop protection: re-enabling port 2 >> >> Jan 25 18:49:33 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:52:35 Loop protection: re-enabling port 2 >> >> Jan 25 18:53:39 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 18:56:41 Loop protection: re-enabling port 2 >> >> Jan 25 18:58:36 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> Jan 25 19:00:36 UI: Configuration changed by admin (172.19.3.6) >> >> Jan 25 19:00:36 UI: Port 2 STP: changed from 'Disabled' to 'Enabled' >> >> Jan 25 19:01:38 Loop protection: re-enabling port 2 >> >> Jan 25 19:02:38 Loop protection: detected loop from port 2 to port 2, >> disabling port 2 for 180 seconds >> >> _______________________________________________ >> Ubnt_users mailing list >> Ubnt_users@wispa.org >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> >> > > _______________________________________________ > Ubnt_users mailing list > Ubnt_users@wispa.org > http://lists.wispa.org/mailman/listinfo/ubnt_users > >
_______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org http://lists.wispa.org/mailman/listinfo/ubnt_users
