LAG with two PTP wireless links on Netgear 5300-28G3

Hi Pedja21,

 

Welcome to the community! :) 

 

The configuration may or may not work with the M5300-28G3 switches.  I think this kind of network setup has not been tested yet.  However, since you have an existing online case with NETGEAR Support, it would be best to escalate your concern as feature request to the engineering team so that it would be supported or be compatible to work with the M5300-28G3 switches.  

 

 

Regards,

 

DaneA

NETGEAR Community Team

Hi Pedja21

 

I have reviewed Cambium ptp article from the link you provided, and it seems to me you shoud try to complete:

- the initial LAG configuration on NETGEAR M5300-28G3

- the MAC ACL configuration for redirecting in-band management packets to one port only in that LAG

 

What we are not going to achieve with M5300-28G3, is the link state monitoring feature for the LAG so that the switch can detect physical wireless link failure when heart‐beat loss happens in between each link port of the LAG. But this should be seamlessly handled by our LACP implementation; do you know if the PTP650 support LACP here?

 

So, creating LAG 1 (1/1/1) with port 7 (1/0/7) and port 8 (1/0/8) in it:

(Netgear Switch) #

(Netgear Switch) #config
(Netgear Switch) (Config)#interface 1/0/7
(Netgear Switch) (Interface 0/2)#addport 1/1/1
(Netgear Switch) (Interface 0/2)#exit
(Netgear Switch) (Config)#interface 1/0/8
(Netgear Switch) (Interface 0/3)#addport 1/1/1

(Netgear Switch) (Interface 0/3)#exit

Without further configuration, LAG 1 (1/1/1) is dynamic (LACP) and provides default hashing based on Source/Destination MAC, VLAN, EType and incoming port. This is the most common configuration that we should implement first.

 

When LAG is up, we should be able to redirect radio in-band management packets to each respective port using ACL (Access Command Lists), preventing LAG hashing from being used for such dedicated management traffic:

(Netgear Switch) #
(Netgear Switch) #config
(Netgear Switch) (Config)#mac access-list extended radio_inband
(Netgear Switch) (Config-mac-access-list)#permit any <radio1‐mac> / 00:00:00:00:00:00 redirect 1/0/8
(Netgear Switch) (Config-mac-access-list)#permit any <radio2‐mac> / 00:00:00:00:00:00 redirect 1/0/7
(Netgear Switch) (Config-mac-access-list)#permit any <radio3‐mac> / 00:00:00:00:00:00 redirect 1/0/8

(Netgear Switch) (Config-mac-access-list)#permit any <radio4‐mac> / 00:00:00:00:00:00 redirect 1/0/7

(Netgear Switch) (Config-mac-access-list)#exit

Then we can to apply this MAC ACL to both ports, as well as to the LAG:

(Netgear Switch) #
(Netgear Switch) #config

(Netgear Switch) (Config)#interface 1/0/7-1/0/8
(Netgear Switch) (Interface 1/0/7-1/0/8)#mac access-group radio_inband in

(Netgear Switch) (Interface 1/0/7-1/0/8)#exit

(Netgear Switch) (Config)#interface 1/1/1
(Netgear Switch) (Interface 1/1/1)#mac access-group radio_inband in

(Netgear Switch) (Interface 1/1/1)#exit

 

Please let us know your findings and provide your feedback to the community!

 

Regards,