Re: Native VLAN question between HP 5412zl and Cisco 6506 (2920 Views)
Reply
Occasional Advisor
lagp
Posts: 7
Registered: ‎02-23-2013
Message 1 of 4 (2,945 Views)

Native VLAN question between HP 5412zl and Cisco 6506

I am attempting to move the "Native" (Cisco Term), Untagged (HP Term) from VLAN 1 to VLAN 700.

 

I have a Trunk "TRK1" on the HP aggregating 8 Gig Interfaces together connectng to an EtherChannel on the Cisco 6506 which is also aggregating 8 Gig Interfaces together.  Everything was working fine when I first stood everything up using VLAN 1 as the Untagged / NATIVE Vlan.  (Yes, I know, why did you change it - another story). 

 

I thought it would be very easy to change the NATIVE / Untagged VLAN but I am running into issues.

 

On the Cisco switch, I am receiving no events; but the HP 5412zl running verson K.15.10.0009, I am constantly receiving events.

 

Here is what I have configured on the Cisco Side....

 

!
interface Port-channel5
 description CO22ZNBCRK1SW1
 switchport
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 1,5,300,500
 switchport mode trunk
 switchport nonegotiate

!

CO22DCWCRK1SW1#sho int port-channel 5 trunk

Port                Mode         Encapsulation  Status        Native vlan
Po5                 on           802.1q         trunking      1

Port                Vlans allowed on trunk
Po5                 1,5,300,500

Port                Vlans allowed and active in management domain
Po5                 1,5,300,500

Port                Vlans in spanning tree forwarding state and not pruned
Po5                 1,5,300,500

 

Per this output, I am using VLAN 1; however, the HP thinks differently.

 

Here are the events I am recieving on the HP Switch...

 

I 05/21/13 18:19:40 00828 lldp: PVID mismatch on port F20(VID 1)with peer device port Gi4/8(VID 700)(363)
I 05/21/13 18:19:44 00828 lldp: PVID mismatch on port F18(VID 1)with peer device port Gi4/7(VID 700)(363)
I 05/21/13 18:19:44 00828 lldp: PVID mismatch on port F16(VID 1)with peer device port Gi4/6(VID 700)(363)
I 05/21/13 18:19:44 00828 lldp: PVID mismatch on port F10(VID 1)with peer device port Gi4/3(VID 700)(363)
I 05/21/13 18:19:45 00828 lldp: PVID mismatch on port F12(VID 1)with peer device port Gi4/4(VID 700)(363)
I 05/21/13 18:19:52 00828 lldp: PVID mismatch on port F6(VID 1)with peer device port Gi4/1(VID 700)(362)
I 05/21/13 18:19:57 00828 lldp: PVID mismatch on port F14(VID 1)with peer device port Gi4/5(VID 700)(362)
I 05/21/13 18:19:58 00828 lldp: PVID mismatch on port F8(VID 1)with peer device port Gi4/2(VID 700)(362)

 

Here is configuration snippets from the HP 5412zl

 

trunk F6,F8,F10,F12,F14,F16,F18,F20 trk1 trunk

 

VLAN ID : 1
  Name : DEFAULT_VLAN
  Status : Port-based
  Voice : No
  Jumbo : No

  Port Information Mode     Unknown VLAN Status
  ---------------- -------- ------------ ----------
  Trk1             Untagged Learn        Up

 

I tried calling HP Technical Support and was told I must use VLAN 1 as the Untagged VLAN.  I don't believe this is true because I am using VLAN 700 between an HP 2910 and the same HP 6506 and have no issues.  The only difference is there are no aggregating ports.

 

I am thinking I either need to reboot the HP Switch or make the changes on the HP end (Far Side) moving to VLAN 700 as the Untagged VLAN, shutting down the port channel on the Cisco Side, make the change on the Cisco side and bring up the port channel.

 

Does anyone have other suggestions?

 

Thanks in advance...

Esteemed Contributor
paulgear
Posts: 655
Registered: ‎04-03-2011
Message 2 of 4 (2,928 Views)

Re: Native VLAN question between HP 5412zl and Cisco 6506

Hi lagp,

 

If the messages are correct, you have changed the native VLAN on the HP end without changing it on the Cisco end.  (The Cisco config you've posted needs "switchport trunk native vlan 700".)

 

Are you actually seeing any poor performance or other faults on those ports?  Those messages are only from LLDP, and i'm not sure if the Cisco 6500s support this - some of their lower-end switches don't.  If you search these forums you should find a few posts indicating that they show up sometimes even if your configuration is correct.

 

You're absolutely right that you can change the native/untagged VLAN id from 1 to something else, and as long as you have checked that you have the correct tagging on both ends it is safe to ignore the LLDP PVID mismatch errors.  In my experience (on older firmware versions) rebooting won't solve anything.

Regards,
Paul
Esteemed Contributor
paulgear
Posts: 655
Registered: ‎04-03-2011
Message 3 of 4 (2,926 Views)

Re: Native VLAN question between HP 5412zl and Cisco 6506

Here's one of the previous discussions about it: http://h30499.www3.hp.com/t5/ProCurve-ProVision-Based/lldp-PVID-mismatch/td-p/5951527

In that case it looks like the message was correct and matching up the VLAN tagging fixed it.
Regards,
Paul
Trusted Contributor
Vince_Whirlwind
Posts: 401
Registered: ‎02-25-2013
Message 4 of 4 (2,920 Views)

Re: Native VLAN question between HP 5412zl and Cisco 6506

It looks like your Cisco switch is in a state. I would down all the ports, including the trunk port, then bring them back up. It shouldn't take a reboot.

 

That said, I think your idea of using VLAN700 as your native VLAN is fine. In fact, you should be encourage to eliminate VLAN1.

 

Here's something to remember:

Cisco *always* has a native VLAN on a .1q trunk. Unless it is specified, it will be VLAN1 by default.

Procurve can have a .1q trunk with *no* native (untagged) VLAN. It's optional. I prefer to not use one.

 

On a Cisco-Procurve trunk, you define your native VLAN on the Cisco side and match that to an untagged VLAN on the Procurve side.

 

If you've been mucking around with this and the switches are having an issue, the problem won't be your actual .1q config (which is pretty simple L2 frame-formatting), more likely the link aggregation (which is more complex). Delete the trunk ports and re-create them if disable/enable doesn't work.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.