[rancid] Cisco WAP VLAN packets/bytes not being filtered, triggering diff

[Sean]

Hi all,

New to the list, and more or less new to diggint into rancid deeper than the occasional device add. I recently moved to 3.2 and noticed that our Cisco WAPs started to report VLAN packet/byte counts on every configuration sync. Example:

- !VLAN:    0 packets, 0 bytes input
- !VLAN:    7944 packets, 3010776 bytes output
- !VLAN:         Other                                           0               79426
- !VLAN:    0 packets, 0 bytes input
- !VLAN:    7944 packets, 3010776 bytes output
- !VLAN:         Other                                           0               79426
- !VLAN:    7939 packets, 6224176 bytes input
- !VLAN:    63538 packets, 7157376 bytes output

I found this post (http://www.shrubbery.net/pipermail/rancid-discuss/2014-June/007703.html) that discusses the same issue, but for 3.1. I tried to apply the patch directly but it failed, presumably because of changes made between 3.1 and 3.2.

A manual application of the modified code did not work, either. $device is apparently undefined and throws an error in my rancid logs. Otherwise, it doesn't seem to have any effect.

Is there another update or patch available that might address this problem? Does the patch above still work, and I should re-apply it, stop being an idiot, and ignore the $device-related errors?

Any assistance would be appreciated.

Thanks!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20150429/8775fead/attachment.html>