starting with LMS 2.5 the 'unused up' and 'unused down' reports where introduced;
that means, UT stores information for all endhost ports in the DB, regardless if they have an endhost connected or not. So my question is if the following is correct for the initial FIRST major acquisition of UT (with prerequisite that for all devices successfull data collection was done and UT does not encounter any problems!)?
after this first major acquisition, the number of entries in the DB is (nearly) the number of available enduser ports of all devices managed by Campus Manager. Nearly, because there are (could be) ports with duplicate MACs (like IP phones with PC connected to them or some server ports). For these ports I can generate a report 'Ports with multiple MAC' to get the amount and a list of the entries.
And this is only true for the first acquisition because changing entries are not necessarily removed from the UT db (depending on the purge policy)
As a result, when estimating if one (1) installation of campus fits for the network (regarding capacity of UT which currently is 100 000 entries) he has to look at the total number of ports on all devices managed by campus to get an idea of this scenario and not only at the number of endusers on the devices because UT counts every port.
the documentation is talking of currently supporting 100 000 endhosts (250 000 endhosts in LMS 3.0) but I think they are talking of entries in the UT database (regardless if there are endhosts connected or not) and not 'real' endhosts. Is that correct or does anybody has other experiences or information on this?