- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve and Cisco 3750 interoperability - inc...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2011 07:41 AM
тАО02-08-2011 07:41 AM
Procurve and Cisco 3750 interoperability - inconsistent peer vlan
I have an HP ProCurve 5308 connected to a Cisco 3750 stack and am having some issues. The two pieces of equipment are connected with an etherchannel(HP trunk) for redundancy. They have been connected for a couple of months with no issues. Until this week, only two vlans had been tagged on the connection from the 5308 to the 3750 - well, tagged is not exactly accurate - one was tagged (vlan 10) and the other untagged (vlan 1) in order to match the native vlan on the Cisco. This week, I needed to start adding some of the other vlans to the 3750 stack. The vlans exist already on both devices. I went into the 5308 and set it to start tagging vlans 3-5 and 75 on the link to the 3750 stack. When I did, I got several errors on the 3750 stack regarding vlans 3 and 4 and they both went into a blocking state on the connection. They have been in that state ever since.
From my syslog server:
1731: Jan 26 05:48:32: %SPANTREE-2-BLOCK_PVID_PEER: Blocking Port-channel1 on VLAN0003. Inconsistent peer vlan.
1731: Jan 26 05:48:32: %SPANTREE-2-BLOCK_PVID_PEER: Blocking Port-channel1 on VLAN0003. Inconsistent peer vlan.
1730: Jan 26 05:48:32: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 3 on Port-channel1 VLAN4.
1730: Jan 26 05:48:32: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 3 on Port-channel1 VLAN4.
Everything I've read so far regarding this type of error point to a difference in the native vlan setup for both sides, but that's not the case here, as both sides are set for native vlan 1 and have been working that way for several months now. After playing with it some more, it appears that the issue is with VLAN 4. If I stop tagging VLAN 4 on the 3508 side, VLAN 3 comes up on the 3750. If I start tagging again, both 3 and 4 go down.
Feb 1 11:41:32: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 3 on Port-channel1 VLAN4.
Feb 1 11:41:32: %SPANTREE-2-BLOCK_PVID_PEER: Blocking Port-channel1 on VLAN0003. Inconsistent peer vlan.
Feb 1 11:41:32: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking Port-channel1 on VLAN0004. Inconsistent local vlan.
Feb 1 11:41:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3, changed state to down
Feb 1 11:41:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan4, changed state to down
Somehow it seems that the 5308 is sending a BDPU with vlan id 3 on VLAN4....
Any ideas would be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 05:43 AM
тАО02-09-2011 05:43 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
Procurve will use MSTP, Cisco PVSTP
vlan 3 and 4 need to be part of the same MST instance.
did you change primary or default vlan on the procurve?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 06:17 AM
тАО02-09-2011 06:17 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 06:19 AM
тАО02-09-2011 06:19 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 06:56 AM
тАО02-09-2011 06:56 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
If STP is not active, the Procurve will not participate in STP calculation, but will still forward BPDU's as if it's a normal data-packet.
apearently the procurve is returning the BPDU's received from the Cisco, back to the Cisco!
please post configs of both switches.
also check no other link connects these switches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 07:09 AM
тАО02-09-2011 07:09 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 07:15 AM
тАО02-09-2011 07:15 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
Unless you're willing to migrate your Cisco over to MST and allow the ProCurve to participate using MST, your other option would be to simply enable BPDU filtering on the Cisco ports that are peered to the ProCurve. This will prevent BPDUs from being broadcast to the ProCurve.
The root of the issue is that in a Per VLAN STP environment, each VLAN acts as an independent STP domain. When you introduce another device that either doesn't understand PVST or is capable of flooding the BPDUs, the Cisco side will block VLANs to protect itself. From there which VLANs get blocked gets determined by priority and cost...
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 07:27 AM
тАО02-09-2011 07:27 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
(Cisco switch config attached)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 07:30 AM
тАО02-09-2011 07:30 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 07:40 AM
тАО02-09-2011 07:40 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
Note: A single connection could be a link aggregated port (802.3ad)
I work for HP, but my posts and replies are my own.