Created attachment 632759 [details] Screenshot Version: si22 Scenario: I've created few thousands of non-vlan networks in a data center, it seems like only 1007 of them appear in webadmin=>Data Centers main tab=>Logical Networks sub tab. In addition, there are no prev/next buttons so I can't edit all the other networks.
Not sure if there is any relation to the fact they are not VLAN tagged, looks like scroll buffer limit or something. In the documentation we actually say that the limit per host is 4096 + number of NICs. Per cluster basically the same and data center may have multiple clusters where logical networks may not be the same. So the limit should be much higher. But I'm not sure that a huge scroll down is the solution to present these - we may need filter on this subtab.
(In reply to comment #1) > Not sure if there is any relation to the fact they are not VLAN tagged, > looks like scroll buffer limit or something. I've added also 4096 vlan networks to the same env and I still see only 1007 networks, so it's probably not related to vlan/non-vlan. > > In the documentation we actually say that the limit per host is 4096 + > number of NICs. Per cluster basically the same and data center may have Limit per host should be "4096 + number of NICs - 1" since in the worse case when you attach all 4096 vlan networks to the same nic in host with n nics, you left with n-1 nics to attach networks to. > multiple clusters where logical networks may not be the same. > > So the limit should be much higher. Theoretically, the limit should be number of supported clusters per data center times the max number of networks per cluster, but practically I think that this number should be limited to much lower limit - based of a max number of lines that the relevant database table can have withour making webadmin stuck on every query. > But I'm not sure that a huge scroll down is the solution to present these - > we may need filter on this subtab. filer/paging.
Moving for future version, no resources and currently low priority. In addition network main tab should give a work-around for the above.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.