Link Aggregation for GS308E

NerdBit 

Afraid, I don't understand why you start arguing about LACP LAGs with me here - I'm just yet another user, not Netgear in any aspect (beyond of getting the opportunity to beta test some Netgear hardware every now and then in my spare time.

All the GS305E and GS308E Data Sheet show "Number of Static Manual LAGs and # of members: GS305E N/A  GS308E N/A". 

All the GS305EP GS305EPP GS308EP GS308EPP GS316E GS316EPP Data Sheet does show "Number of Static Manual LAGs and # of members: GS305EP 2/4  GS305EPP 2/4  GS308EP 2/4  GS308EPP 2/4  GS316EP 8/8  GS316EPP 8/8"

All the GS305E and GS308E Data Sheet show "Number of Static Manual LAGs and # of members: GS305E N/A  GS308E N/A". 

This is what confused me, because I know from the chip set specs (as reflected in the GS305EPP and GS308WP/EPP) the five and eight port do support static LAG - and how ever, this is missing or went lost in the product spec and definition process. his is why I tried to bring some attention to NTGR

Slightly different is the situation on the WAX6xx, like the WAX630E. Technically equipped with a 2.5Gbps Power-over Ethernet and a 1Gbps Ethernet ports,  one additional 1GbE port for network redundancy or link aggregation to enhance reliability or throughput.

A short excursion to RT*M unveils (bold text for clarification)

Enable link aggregation for the LAN 2 port
You can set up a static link aggregation connection between the access point and a switch by doing the following:
1. On the switch, configure static link aggregation on the two Ethernet ports that you intend to use for the LAG connection to the access point.
CAUTION: To prevent a network loop, configure the switch ports before connecting them to the access point ports.
2. Connect the two Ethernet ports on the switch to the LAN 1 port and the LAN 2 port on the access point.

LACP link aggregation is neither a holy grail nor a necessity for such a configuration. Nice your security appliances have it, it does not help in this context. A basic static LAG support would be sufficient. 

Hint: Balance-XOR mode, where the bonding of slave interfaces are static and all slave interfaces are active for load balancing and fault tolerance purposes is the way to go.