<head in shame> no, as it turns out, its called "read the fucking manual, you dolt". (im the dolt) I dont know If SAF words things odd, or if im full shortbus anymore
"The Integra-W link with out-band management implements two Ethernet connections – one for management traffic and the second for user traffic. Since user traffic and management circuits are parallel, an Ethernet loop will occur. To avoid the loop, management on WAN interfaces has to be disabled by entering this command in CLI “modem management 0”. Thereby management Link aggregation/bonding and load balancing with SAF products 31 traffic will only pass through the wireless link via the user traffic connection egressing the MNG port." Id like to blame them, but thats pretty straight forward right there, And I read it like 10 times, they even recommended trying that command, it just never registered... im off to go lick windows. On Mon, Mar 5, 2018 at 7:21 PM, Jaime Solorza <[email protected]> wrote: > It's called loopis destructus....turn off management port on far side and > see if that clears it up... > > Jaime Solorza > > On Mar 5, 2018 5:32 PM, "Steve Jones" <[email protected]> wrote: > >> scratch that. My powercode DHCP server is freaked out getting queries >> from both sides >> >> On Mon, Mar 5, 2018 at 5:44 PM, Steve Jones <[email protected]> >> wrote: >> >>> I may be helmet here, but am I correct in assuming that OOB managment >>> ports should not participate in bridging traffic across wireless links of >>> any kind? >>> this 2+0 has OOB on the radios, I have the management ports run into a >>> switch on each side. Loop protection is kicking the ports on and off. The >>> customer traffic is flowing over the wireless via LACP bonding in the same >>> switch, but isolated via VLAN. >>> >>> I should not, under any circumstances see MAC addresses from the other >>> side of a link via the management port should I? Im not only seeing the >>> remote switch, but every mac in the MAC table from the remote switch. both >>> sides have the OOB in ports 21 and 22, in the following, both switched have >>> port 22 blocked due to detected loop, but it flip flops back and forth >>> between 21 and 22 when the detection timer expires. I havent had calls of >>> any issues with customer traffic (both are independent DHCP subnets) >>> >>> A SIDE Switch MAC Address - 74:46:a0:e8:ed:00 >>> >>> A SIDE MAC Table >>> >>> 38:ea:a7:bc:24:40 21 Learned >>> >>> >>> >>> B SIDE Switch MAC Address - 38:ea:a7:bc:24:40 >>> >>> B SIDE MAC Table >>> >>> 74:46:a0:e8:ed:00 21 Learned >>> >>> >>
