Hi, I'm in the process of trying to migrate the core of our network from an HP ProCurve 5308 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. 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. I had a similar issue with vlans 6 and 8 between these two devices when I first went to this setup and it would shut down the interfaces instead of just the vlans. I wound up having to move those two to separate connections exclusive to the vlans to get them to work (that's probably a whole other issue). Any ideas would be appreciated. SWHQCORE#sh spanning-tree inc Name Interface Inconsistency Number of inconsistent ports (segments) in the system : 2 Hi Please here few explanations on HPE vlan tagging rules : https://techhub.hpe.com/eginfolib/networking/docs/switches/WB/15-18/5998-8156_wb_2926_atmg/content/ch01s02.html#s_VLAN_tagging_rules To my understanding, "tagged" means that the port is configured as trunk and 801.Q tagged frames are accepted against vlans number matching the port config. "Untagged" means that 801.Q trunking is not applied. So, frames do not use vlan marking and are accepted to the vlan associated with the port. "No untagged" means that this vlan is not usable as untagged traffic on port. I think that is a way to disable non tagged traffic on the port. On Cisco Catalyst, it is equivalent to disable the native vlan. So, if we look at your HP configuration, Cisco equivalent for few ports would be (using equivalent port number on one Catalyst access switch) : ! port 1 - tagged on vlan 2-4 but no untagged on vlan 1 int git1/0/1 ! vlan 1 is not allowed so, as it is default native vlan, non tagged traffic will be dropped as HP config expect. ! port 3 - tagged on vlan 3 but no untagged on vlan 1 int git1/0/3 ! vlan 1 is not allowed so, as it is default native vlan, non tagged traffic will be dropped as HP config expect. switchport trunk allowed vlan 3 ! port 5 - untagged vlan 4 (and no untagged vlan 1) int git1/0/5 ! port 6 - tagged on vlan 2-4 but untagged on vlan 1 int git1/0/6 ! vlan 1 is allowed so, as it is default native vlan, non tagged traffic will be accepted as HP config
expect. ! next command is optionnal as vlan 1 is native per default ! switchport trunk native vlan 1 Moreover, you might add next commands depending your needs : * on older Catalyst switches, set the type of trunking : switchport trunk encapsulation dot1q * disable DTP to avoid port negociate its trunking state : switchport nonegotiate * on a port facing a direct host, activate STP portfast to avoid convergence timers : spanning-tree portfast or spanning-tree portfast trunk (for tagged ports) I'm not HP expert, so I hope to not be wrong. Regards Jérôme |
2 hp procurve gleiches vlan
zusammenhängende Posts
Urheberrechte © © 2024 WIKIFI Inc.
