- Bronze, 100 points or more
I wish to get a far more clearer understanding of UserTracking.(CM ver 5.1.1) Th userguide does not provide indepth information. I understand that it collects data from routers and switches For instance using the bridge-mib and getting data from the dot1dTpFdbTable OID. I can do this with snmpwalk as well.
But what is confusing, is the way UserTracking populates the collected data in the database. We see plenty duplicate MAC addresses. I see the same MAC address on Fast Ethernet ports and on Gig ports. I understand the MAC will appear in these Gig trunks, but is there a way to stop those from populating the database? Tracking a user to the port he is connected on surely makes more sense.
This question's history is related to investigation into the possibility of using a UT report for monthly billing purposes. One fee per port per user. Inevitably UT can provide prove a user has used a port, but overbilling must not happen due to duplicate MACs etc.
Thanks in advance.