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.
UT is smart enough not to add entries for MAC addresses on trunk ports by default. However, in UT 5.0, you have the option of enable acquisition of users on all trunk ports or just selected trunk ports. If you have enabled this option, then what you're seeing is expected. If not, then UT should not be adding those entries. Check Campus Manager > Admin > User Tracking > Acquisition > Configure Trunk For End Hosts Discovery to see if this feature is enabled.
That said, if these gig ports are not really trunking (simply uplink ports), and CDP is not enabled on these ports (or the CDP neighbors are not being managed by Campus), then seeing users connected to those ports is expected, and there is nothing that can be done in UT to avoid it.
Ok, thanks Joe. I will check those Acquisition settings. Come to think of it, there are quite a few normal uplink ports. Would it help if I enable CDP then? From the reports it looks like UT will add a new record for a previous discovered MAC address if: the port changed or the VLAN changed.
If you enable CDP on those ports, you will also need to make sure the neighbors are managed on the Topology Map. Only then will UT ignore entries on those ports.
It depends on the UT DHCP setting as to how UT will resolve moving MACs and the duplicates they cause. If you have DHCP support enabled, only duplicate MACs with reachable IP addresses will be retained.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...