- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: comware and procurve bridge-aggregation vlan n...
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
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
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
03-16-2015 07:33 AM
03-16-2015 07:33 AM
Hi there. I probably missed a post with the answer when I searched for this but here I go.
Background, I am used to procurve and now made the move to a new comware based core.
My previous setup was a procruve connected to another procurve with LACP trunks with all vlan tagged on the trunk.
The new setup with which I am having an issue is a procurve and comware connected to another with LACP.
The trunk conf on procurve is straight forward:
trunk J1-J4 trk60 lacp
then this trk60 is tagged in each vlan of interest (1,99,100).
The bridge aggregation on comware is also ok:
interface Bridge-Aggregation10
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic
And the interfaces of interest are in the bagg accordingly
interface GigabitEthernet1/0/10
port link-mode bridge
port link-type trunk
port trunk permit vlan all
port link-aggregation group 10
You will note I am doing permit vlan all too.
On the procurve, my LACP looks good.
LACP Trunk Port LACP Admin Oper
Port Enabled Group Status Partner Status Key Key
---- ------- ------- ------- ------- ------- ------ ------
J1 Active Trk60 Up Yes Success 0 349
J2 Active Trk60 Up Yes Success 0 349
J3 Active Trk60 Up Yes Success 0 349
J4 Active Trk60 Up Yes Success 0 349
On the comware, my BAGG also looks good
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregation Interface: Bridge-Aggregation10
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, 7848-5952-8f88
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
GE1/0/10 S 32768 1 {ACDEF}
GE1/0/11 S 32768 1 {ACDEF}
GE2/0/10 S 32768 1 {ACDEF}
GE2/0/11 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE1/0/10 217 0 349 0xcf00, 0018-71ca-cf00 {ACDEF}
GE1/0/11 219 0 349 0xcf00, 0018-71ca-cf00 {ACDEF}
GE2/0/10 218 0 349 0xcf00, 0018-71ca-cf00 {ACDEF}
GE2/0/11 220 0 349 0xcf00, 0018-71ca-cf00 {ACDEF}
however...
While everything connected on my procurve untagged on vlan 99 and 100 is fine and reach the comware, what is untagged on vlan 1 doesn't.
now I perhaps lack comprehension of comware but here is what I think.
on comware, if I look at vlan 99 and 100 I see that the BAGG (and the member ports) is tagged.
>dis vlan 100
VLAN ID: 100
VLAN Type: static
Route Interface: not configured
Description: VLAN 0100
Name: 100-servers
Tagged Ports:
Bridge-Aggregation10
GigabitEthernet1/0/10 GigabitEthernet1/0/11 GigabitEthernet2/0/10
GigabitEthernet2/0/11
Ten-GigabitEthernet1/0/29
Ten-GigabitEthernet1/0/30
Ten-GigabitEthernet2/0/29
Ten-GigabitEthernet2/0/30
Untagged Ports: none
but on vlan 1 the BAGG is untagged.
>dis vlan 1
VLAN ID: 1
VLAN Type: static
Route Interface: not configured
Description: VLAN 0001
Name: leg-1-mgmt
Tagged Ports: none
Untagged Ports:
Bridge-Aggregation10
GigabitEthernet1/0/1 GigabitEthernet1/0/2 GigabitEthernet1/0/3
GigabitEthernet1/0/4 GigabitEthernet1/0/5 GigabitEthernet1/0/6
GigabitEthernet1/0/7 GigabitEthernet1/0/8 GigabitEthernet1/0/9
GigabitEthernet1/0/10 GigabitEthernet1/0/11 GigabitEthernet1/0/12
GigabitEthernet1/0/13 GigabitEthernet1/0/14 GigabitEthernet1/0/15
GigabitEthernet1/0/16 GigabitEthernet1/0/17 GigabitEthernet1/0/18
GigabitEthernet1/0/19 GigabitEthernet1/0/20 GigabitEthernet1/0/21
GigabitEthernet1/0/22 GigabitEthernet1/0/23 GigabitEthernet1/0/24
GigabitEthernet1/0/25 GigabitEthernet1/0/26 GigabitEthernet1/0/27
GigabitEthernet1/0/28 GigabitEthernet2/0/1 GigabitEthernet2/0/2
GigabitEthernet2/0/3 GigabitEthernet2/0/4 GigabitEthernet2/0/5
GigabitEthernet2/0/6 GigabitEthernet2/0/7 GigabitEthernet2/0/8
GigabitEthernet2/0/9 GigabitEthernet2/0/10 GigabitEthernet2/0/11
GigabitEthernet2/0/12 GigabitEthernet2/0/13 GigabitEthernet2/0/14
GigabitEthernet2/0/15 GigabitEthernet2/0/16 GigabitEthernet2/0/17
GigabitEthernet2/0/18 GigabitEthernet2/0/19 GigabitEthernet2/0/20
GigabitEthernet2/0/21 GigabitEthernet2/0/22 GigabitEthernet2/0/23
GigabitEthernet2/0/24 GigabitEthernet2/0/25 GigabitEthernet2/0/26
GigabitEthernet2/0/27 GigabitEthernet2/0/28
so here I go, the issue seem to be that I have a BAGG with port-link mode trunk that is untagged? hence not getting my vlan 1 traffic from the procurve? if so how do I "tagged" my BAGG on vlan1?
or perhaps I am mixing up the terms and miss something because when I had only procurve, this conf with the lacp trunk tagged on all vlans it did not require much more config.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2015 11:52 AM
03-16-2015 11:52 AM
SolutionHi Kitkatneko,
I think you need to explicitly set another pvid. Otherwise vlan1 will be pvid. (untagged)
so on your bagg do :
port trunk pvid <some vlan you do not use>
Then vlan 1 will not be untagged.
Regards
Region Midtjylland
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2015 12:48 AM
03-17-2015 12:48 AM
Re: comware and procurve bridge-aggregation vlan noobie question
I agree, native vlan/PVID is untagged in Comware 802.Q trunk ports.
You will need to set to another PVID if you want VLAN 1 to be tagged.
Daryl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2015 06:56 AM
03-18-2015 06:56 AM
Re: comware and procurve bridge-aggregation vlan noobie question
I indeed totaly missed the PVID part.
As mentioned I have changed the PVID of my BAGG and it automagically got tagged under the allowed vlan.
Thank you.