The point is that a static LAG has no additional layer (or kind of an interface) on top of the pure network interface links - thats why switches do not show a status for the static LAG.
In fact, the R9000 (like all Netgear routers with static link aggregation support!) are providing a wrong proof. All these routers implement the LAG based on the Linux bonding driver. Initially, there was only dynamic LAG based on 802.3ad with LACP available. Here we have an additional negotiated layer between the LAG end points - that's why the routers have this status indication. When it comes to the static LAG, the indicator does only reflect that both links of the LAG are up - not that there is a properly configured LAG. Simple test? Unplug one of the router aggregation ports (while connected to the router using WiFi or another local LAN port of course), then connect any other Ethernet device (don't use the same computer!) to that LAN port - and you find the router showing "active" on the aggregation...
i still do understand why on the switch i do not get active. This is what Netgear say in the movie on the site.
maybe i make it to big and staring blindly at the video that Netgear make.
As I tried to proof with the test demonstration: There is no way to provide a reliable "LAG active" information on a static LAG, in fact on both ends (any switch, and the router). To my knowledge, no business class swiches with static LAG support have any indication on static LAG beyond of the pure link indication.
