Aruba & ProVision-based
1748244 Members
3727 Online
108760 Solutions
New Discussion

Re: Receiving PVID mismatch messages on all HP Pro-Curve switches

 
hashim100
New Member

Receiving PVID mismatch messages on all HP Pro-Curve switches

Hi 

2 Core Switch HP 5412zl  and  multiple Acces switches HP 3500YL are configured in a Network with Cisco IP Phone and Huawei Access Point. i am getting the Log messages PVID Mismatch  in all switches although configuration is Ok on all switches and applictaion are working fine but these messages are very annoying and facing network slowness. 

these messages are appearing on all switches. all switches are Pro-Curve 

Sample message on CORE-2 

I 08/18/17 00:55:33 00828 lldp: PVID mismatch on port B10(VID 1)with peer device
port 24(VID unknown)(197024)
I 08/18/17 00:55:33 00828 lldp: PVID mismatch on port B9(VID 1)with peer device
port 23(VID unknown)(197024)

Sample message on Access Switch

I 08/17/17 03:11:10 00828 lldp: PVID mismatch on port 24(VID 0)with peer device
port 34(VID 1)(37508)
I 08/17/17 03:11:10 00828 lldp: PVID mismatch on port 23(VID 0)with peer device
port 33(VID 1)(37508)

default vlan is vlan 1 and configured on all switches trunk as Untagged VLAN. but i am still receiving messages

CORE-2 Sample Config 

trunk B9-B10 trk17 trunk

vlan 1
name "NMS"
no untagged C1-C24,D1,D3-D12,D20,E13-E24
untagged B17-B24,D2,D13-D19,E5-E12,F3-F4,Trk1-Trk22,Trk51-Trk52
ip address 172.16.0.1 255.255.240.0
ip helper-address 172.30.10.5
vrrp vrid 1
owner
virtual-ip-address 172.16.0.1 255.255.240.0

show vlans ports Trk1 detail

Status and Counters - VLAN Information - for ports Trk17

VLAN ID Name | Status         Voice Jumbo    Mode
------- -------------------- + ---------- ----- ----- --------
1          NMS        | Port-based   No         No      Untagged
12        WLAN     | Port-based   No         No       Tagged
13       ADMIN     | Port-based   No         No       Tagged
14       VOIP         | Port-based  Yes        No       Tagged
15       CCTV        | Port-based  No         No       Tagged

Access Switch Sample Config

trunk 23-24 Trk1 Trunk

vlan 1
name "DEFAULT_VLAN"
untagged 4-5,8-12,15-22,A1-A4,Trk1
ip address 172.16.11.12 255.255.240.0
no untagged 1-3,6-7,13-14

VLAN ID   Name                     | Status     Voice     Jumbo     Mode
------- -------------------- + ---------- ----- ----- --------
1               DEFAULT_VLAN   | Port-based    No      No     Untagged
11                VLAN11                | Port-based    No      No       Tagged
12                WLAN                  | Port-based    No      No       Tagged
13              ADMIN                   | Port-based    No      No       Tagged
14               VoIP                      | Port-based     No     No       Tagged
15               CCTV                     | Port-based    No     No        Tagged

plese give me advice as switches configuration seems to me OK but receiving PVID Mismatch Log on all swicthes 

2 REPLIES 2
Vince-Whirlwind
Honored Contributor

Re: Receiving PVID mismatch messages on all HP Pro-Curve switches

It is best-practice to not have any of your real VLANs untagged on any switch to switch link.

I wonder if tagging VLAN1 would be better? 

It's best practice to not use VLAN1 as well though.

Richard Litchfield
Respected Contributor

Re: Receiving PVID mismatch messages on all HP Pro-Curve switches

You will get PVID mismatch log entries if the VLAN IDs for the untagged/native/PVID are not the same on each end. An untagged VLAN 1 connected to an untagged VLAN 24 will generate that message.

If the VLAN IDs cannot be matched for some reason (and they don't *have* to be - the messages are just annoying), you can disable the info being sent so the messages don't appear - see http://h22208.www2.hpe.com/eginfolib/networking/docs/switches/K-KA-KB/15-18/5998-8160_ssw_mcg/content/ch06s13.html

http://community.arubanetworks.com/t5/Wireless-Access/LLDP-Incorrect-VLAN-sent-out-ArubaOS-6-3/td-p/176932

dot1TlvEnable