- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve and Cisco 3750 interoperability - inc...
Switches, Hubs, and Modems
1753894
Members
7607
Online
108809
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-09-2011 07:52 AM
тАО02-09-2011 07:52 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
So if I really want to get to the root of the problem, I have to figure out how vlan 3 BPDU's are getting onto VLAN 4, correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 08:01 AM
тАО02-09-2011 08:01 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
trunk D15-D16 Trk1 LACP
interface D15
no lacp
exit
interface D16
no lacp
exit
you are using both "no lacp" and "lacp"
Are you sure this works as planned?
try a "show trunks" to see if the link is really operating as trunk.
same on the cisco side you are mixing commands on the trunk/etherchannel interface with commands on individual member-ports of the trunk/etherchannel.
>>>
interface Port-channel1
description Redundant Trunk to Core 5308
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-5,7,9-99
switchport mode trunk
interface GigabitEthernet2/0/24
description Uplink - 5308 D15
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-5,7,9-99
switchport mode trunk
channel-group 1 mode active
!
!
interface GigabitEthernet3/0/24
description Uplink - 5308 D16
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-5,7,9-99
switchport mode trunk
channel-group 1 mode active
<<<
=> remove redundant commands from individual ports and only apply them to the trunk/etherchannel.
interface D15
no lacp
exit
interface D16
no lacp
exit
you are using both "no lacp" and "lacp"
Are you sure this works as planned?
try a "show trunks" to see if the link is really operating as trunk.
same on the cisco side you are mixing commands on the trunk/etherchannel interface with commands on individual member-ports of the trunk/etherchannel.
>>>
interface Port-channel1
description Redundant Trunk to Core 5308
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-5,7,9-99
switchport mode trunk
interface GigabitEthernet2/0/24
description Uplink - 5308 D15
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-5,7,9-99
switchport mode trunk
channel-group 1 mode active
!
!
interface GigabitEthernet3/0/24
description Uplink - 5308 D16
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-5,7,9-99
switchport mode trunk
channel-group 1 mode active
<<<
=> remove redundant commands from individual ports and only apply them to the trunk/etherchannel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2011 08:32 AM
тАО02-09-2011 08:32 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
With STP turned off on the ProCurve, it will simply flood the BPDUs it recieves. I'm not sure how it will treat a BPDU without a VLAN ID in it's header when flooded to a port with both native (untagged) and tagged VLANs, but this may be a contributing factor.
I think all native and untagged VLANs will get BPDUs from all other VLANs including the Dot1Q "tagged" VLANs...
I think all native and untagged VLANs will get BPDUs from all other VLANs including the Dot1Q "tagged" VLANs...
---------------------------------------------
I work for HP, but my posts and replies are my own.
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 08:36 AM
тАО02-09-2011 08:36 AM
Re: Procurve and Cisco 3750 interoperability - inconsistent peer vlan
Buckeye-5308xl-Core# sh trunks
Load Balancing
Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- -----
D15 | 100/1000T | Trk1 LACP
D16 | 100/1000T | Trk1 LACP
From everything I've read, that's the way it works. You turn it of for the individual ports involved in the trunk and have it turned on for the trunk itself.
It's working fine, though I can see why the individual cisco ports don't need those commands - I think they get ignored anyway, but yes, I should probably pull them out.
Load Balancing
Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- -----
D15 | 100/1000T | Trk1 LACP
D16 | 100/1000T | Trk1 LACP
From everything I've read, that's the way it works. You turn it of for the individual ports involved in the trunk and have it turned on for the trunk itself.
It's working fine, though I can see why the individual cisco ports don't need those commands - I think they get ignored anyway, but yes, I should probably pull them out.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP