MacTrack - v2.4 Released

[TheWitness]

All,

MacTrack 2.4 has been released. This release is a significant change from version 1.1. The ChangeLog is extensive and included below.

bug: 0001546: mactrack_view_devices does not display the proper page numbers
bug: 0001545: mactrack_scanner does not complete successfully for some hosts
bug: 0001547: mactrack_view_sites does not show page numbers
bug: 0001548: mactrack_view_macs various issues
bug: IEEE Database import runs out of memory
bug: Correct uninitialized error in mactrack_hp.php
bug: Resolved issue where Vendor Mac was lost during resolver process
bug: fix syntax of cacti_snmp_* calls
feature: 0001638: Allow Interface Data to Be "Scaned" on Demand from the WebUI Similar to Scanner
feature: 0001637: Enable Site Level Scanning Through the UI and Using Ajax
feature: Adding support for ArpWatch
feature: Adding Juniper Support
feature: Support Foundry Dual Mode Ports
feature: Implement MacWatch in code. E-Mailing now.
feature: Adding significant content to the mac_track_interfaces table
feature: Implement MacAuth functionality and periodic reports
feature: Implement Interfaces tab to MacTrack
feature: Aggregated ports patch from Gthe!
feature: Linux and DLink Scanners from Gthe!
feature: add all device SNMP options to mac_track_devices
feature: add full SNMP V3 support
feature: deprecate readstrings; maintain "SNMP Option Sets" in favour of them
feature: some Enterasys scanning functions (N7, C2, C3)
feature: import cacti devices into mac_track_devices
(new action hook for host.php)
feature: optionally sync SNMP settings of mac_track_devices and cacti device, governed by a config setting (defaulting to "none") to allow either
- mactrack -> host (when scanning) or
- host -> mactrack updates (when manually updating the host)
feature: allow for "connecting" existing mactrack devices to cacti devices
(via hostname, new action for mactrack_devices.php)
feature: copy snmp settings from cacti devices to mactrack devices
(via host_id connection, new action for mactrack_devices.php)
feature: Allow mapping of Cacti graphs to MacTrack
feature: Add columns for AutoNegotiation - Implementation TBD

My special thanks to all those who tested this release and contributed scanning functions. I do anticipate a v3.0 to be released with a new "Remote" plugin in the next few months.

Please submit your bug reports to http://bugs.cacti.net I also hope to have some documentation on this plugin shortly.

You may download the plugin here: http://docs.cacti.net/plugin:mactrack#mactrack

TheWitness

[JorisFRST]

Thank you very much for this.

I'll download it right away, is it the same as the latest svn ?
As i'd be happy to keep testing.

Joris.

[TheWitness]

There are two new columns in mac_track_interfaces, but they are unused. Otherwise, it's identical.

When you goto the Doc's site, you will notice that the Etherchannel issue is still open. I want to be able to handle it generically, so it was not included as is. We should continue the discussion in the MacTrack section of the forum relative to handling this generically.

TheWitness

[toe_cutter]

Thanks!
Cant wait for the AutoNegotiation feature
Ill be keeping an eye on the SVN heh

[torstentfk]

change log seems to be really cool
but one question at the beginning:
It is supported to have trunk -ports (ports with more than one VLAN) in the table? Old mactrack assumed these ports as non.user ports and discarded them.

Torsten

[TheWitness]

change log seems to be really cool
but one question at the beginning:
It is supported to have trunk -ports (ports with more than one VLAN) in the table? Old mactrack assumed these ports as non.user ports and discarded them.

Torsten

It should still behave this way.

[blugger]

Hi,

I already used 1.1 in the past. I stopped using it, because I was not able to gather information from the Cisco ASA.

Is it possible now?

BR
B.

[TheWitness]

Not sure. What specifically were you looking for it to collect. Please provide a specification.

[TheWitness]

MacTrack 2.5 will be out addressing a few minor issues with the initial 2.4 release. Please be patient. This is OSS after all.

TheWitness

[toe_cutter]

A quick question (before i bug report )
The "Last Change" column in the Interfaces tab. Is it supposed to show when the last time a port was used?
Im asking because i just disconnected a computer and rescanned the interface (green ring next to the interface) and while MT showed the port as down (had to refresh the page before that showed) the "Last change" column was unchanged as "Since restart", actually every port we have, has "Since restart", atm around 2000 ports scanned :S

I could suggest a change/tweak of that column, change its name to "Idle days" and have a counter count how many days since it was last active (port up/mac on port/traffic).
That would help in finding unused ports to re-use or if you're to clear out a switch.

[TheWitness]

A quick question (before i bug report )
The "Last Change" column in the Interfaces tab. Is it supposed to show when the last time a port was used?
Im asking because i just disconnected a computer and rescanned the interface (green ring next to the interface) and while MT showed the port as down (had to refresh the page before that showed) the "Last change" column was unchanged as "Since restart", actually every port we have, has "Since restart", atm around 2000 ports scanned :S

I could suggest a change/tweak of that column, change its name to "Idle days" and have a counter count how many days since it was last active (port up/mac on port/traffic).
That would help in finding unused ports to re-use or if you're to clear out a switch.

Can you please do me a favor and run a scan of the OID with the port active, then unplug and run it again, reconnect and run it again and PM me the output. Thought that this was working.

TheWitness

[toe_cutter]

Can you please do me a favor and run a scan of the OID with the port active, then unplug and run it again, reconnect and run it again and PM me the output. Thought that this was working.

TheWitness

Surething, i never knew there existed a ifLastChange OID

Edit: forgot you wanted it as a PM. Its sent now.

Edit2:
Another Q, the Ignore ports in Settings, is that list only applied to the Interface tab or is it "global"?
Im getting my desktops MAC on two different switches trunk-ports that are ignored according to this list.
Or should i add the trunk-ports to each device separately? If yes, can we have a global setting for this?

//David

[TheWitness]

Another Q, the Ignore ports in Settings, is that list only applied to the Interface tab or is it "global"?

This is for interfaces only at this point

I'm getting my desktops MAC on two different switches trunk-ports that are ignored according to this list.

Yes, if the trunks are not "detected" by the scanning function, you need to exclude them.

Or should i add the trunk-ports to each device separately? If yes, can we have a global setting for this?

It's at a device type basis, I'm pretty sure (maybe it's by device). Either way it needs some improvement (more flexibility).

TheWitness

[toe_cutter]

Yes, if the trunks are not "detected" by the scanning function, you need to exclude them.

Hm, okay.
Maybe i missed something, but trunk-macs are leaking into the mac-db.
Cant give any more details other than the vlan_trunk/vlan_trunk_status columns in the mac_track_interfaces table for an interface are set to 0 and that the scanning function does seem to find the trunks, else the db would fill up fast id suppose.

Anyway, need to work now.

//David

[zgamer]

Feature request: If more than "x"(a variable integer that is configurable) number of MAC address are detected per port to ignore that port. Basically adds some auto-detection of uplink ports and to auto-ignore them.