05-01-2015 08:12 PM
If you can on that model, upgrade the HPs. There's a control to change what it gets cranky enough to log about in the newer software. It is mentioned in the release notes. IIRC you can either tune it, or just having the new software causes it to only log occasionally compared to the constant nagging.
05-21-2015 10:14 AM
Disabling the port-vlan tlv under the ap lldp profile in the controller fixed this problem for us.
ap lldp profile "default"
05-12-2016 11:55 PM
We were also running into this issue and found another workaround which seems to be made specifically to ignore these logs.
Following command on the HP switch should do the trick:
- lldp ignore-pvid-inconsistency
07-21-2016 03:06 PM
If you are running a newer verson of the Procurve/Provision/HPE Aruba OS on your switch you can use this handy command to filter out those pesky PVID mismatch errors, in your log.
logging filter PVID 1 ".VID unknown." deny
logging filter PVID default permit
logging filter PVID enable
I'm not sure when this command came into existance, but I know it is avaiable as Proview 15.16 and of course on the new version 16.x code.
Hope it works for you!
- John Maier
07-28-2016 08:02 AM
Using an lldp-profile as wgrandis said is a nice easy solution that does not
require fiddling with each switch.
Do note if you have a large AP group that does not have an enet profile applied and you
need to swap in a new enet profile to do so, this will cause a link-flap on all the APs,
which can among other things load the switch AAA mechanisms. So probably best to do so
But still, it is the best solution yet to this.
03-08-2017 02:24 AM
I know this a very old post but i do have a fix for this issue.
to recap the issue is caused by the pvid mismatch between the switch and ap.
Rather than configure all your switch ports to disable lldp you can configure your AP ethernet profile with the correct pvid.
All my access points are connected as untagged vlan 10. I created a new wired profile for vlan 10.
ap wired-ap-profile "vlan 10"
switchport access vlan 10
created a new lldp profile and disabled port vlan advertisments
ap lldp profile "vlan 10"
bound the two together
ap wired-port-profile "vlan 10"
wired-ap-profile "vlan 10"
lldp-profile "vlan 10"
added to the group
enet0-port-profile "vlan 10"
hey presto no logs filled with errors.
3 weeks ago
The MGMT VLAN of your AP group is VLAN 99 right?
Is it also configured in the AP group on the Aruba controller?
Default it is normally VLAN 1.