- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: Loosing BAGG When assigning New VLAN 5900AF
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
тАО09-01-2017 01:06 AM
тАО09-01-2017 01:06 AM
Loosing BAGG When assigning New VLAN 5900AF
Hello,
I'am facing a very strange issue.
I have 2 IRF Stacks based on 2 paris of 5900AF Switchs.
Theses stacks are used for theVMware Datacenter connectivity.
To connect to my Backbone Switches i have created a BAGG composed of 4 ports.
Everything is working as needed but when i add a new VLAN in the Switch i loose the connectivity of the BAGG.
To reestablish the connectivity i have to unplugg all the BAGG cables ans reconnect them.
The remote Backbone Switch is a single HP Procurve 2910al.
How can you explain this behavior?
It seems to happen only when i assign an IP to the VLAN.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2017 04:04 AM - edited тАО09-01-2017 04:13 AM
тАО09-01-2017 04:04 AM - edited тАО09-01-2017 04:13 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
It's unclear.
You wrote you have a setup with two IRF Stacks, each one made of two 5900AF Switches (a total of four 5900AF Switches). That's OK.
Hope I've misunderstood your scenario...but you wrote that you have Backbone Switches (so plural) connected to both your IRF Stacks but you just cited one single remote Backbone Switch (an HP ProCurve 2910al)...that let me think you should have two separate Port Trunk Groups (using the HP ProCurve terminology) definded on the 2910al and each Port Trunk Group (made of aggregated interfaces) separately terminates on each IRF Stack...in other words...from what you wrote...it seems that each IRF Stack has a LAG (Link Aggregatation Group, Comware terminology) that terminates on the 2910al, exactly on each Port Trunk Group counterpart...a scenario that is totally understandeable.
If this is not the case it means that your scenario has instead a single Port Trunk on the 2910al side that is necessarily "distributed" against both two separate IRF Stacks...but I think that scenario is not supported (a Port Trunk splitted to two separate LAGs).
So:
- How is your exact network topology with regard to the HP ProCurve 2910al and two separate 2 members IRF Stacks?
- Where you "created a BAGG composed of 4 ports."?
- Where the above 4 ports BAGG terminates?
- Are the IRF Stacks directly interconnected together (other than being indirectly interconnected through the 2910al)?
- What is the VLANs status/configuration on IRF Stacks and on the 2910al?
- Have you more than one 2910al (the Backbone Switch)?
You then wrote "when i add VLAN in the Switch...", which one?
P.S.
The output of those CLI commands would help:
On ProVision based Switches (HP ProCurve): show trunks and/or show lacp
On Comware based Switches (5900AF): display link-aggregation verbose
Moving this whole threat to the Comware-based category would help (Web and Unmanaged doesn't fit well speaking about 2910al and 5900AF).
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2017 05:23 AM - edited тАО09-01-2017 05:26 AM
тАО09-01-2017 05:23 AM - edited тАО09-01-2017 05:26 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
Thanks for your quick reply Parnassus!
Sorry for my bad explanation. My 2 IRF Stacks are totaly seprated. I have two production sites with the same IRF topology on each site.
I have made a quick plan to explain you the topology (attached JPG).
Below you will find the results of the cli commands that answers the other questions.
I don't Know how to move this thread to the Comware-based Category. Sorry ;-)
Hope this helps to Understand my topology.
2910al Part
L32-Switch_02# show trunks
Load Balancing
Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- --------
13 | Trk-L32-SW01 100/1000T | Trk41 LACP
14 | Trk-L32-SW01 100/1000T | Trk41 LACP
15 | Trk-L32-SW01 100/1000T | Trk41 LACP
16 | Trk-L32-SW01 100/1000T | Trk41 LACP
17 | Trk-L32-SW03 100/1000T | Trk50 LACP
18 | Trk-L32-SW03 100/1000T | Trk50 LACP
19 | Trk-L32-SW03 100/1000T | Trk50 LACP
20 | Trk-L32-SW03 100/1000T | Trk50 LACP
21 | Trk-L21-SW01 100/1000T | Trk1 LACP
22 | Trk-L21-SW01 100/1000T | Trk1 LACP
23 | Trk-L21-SW01 100/1000T | Trk1 LACP
24 | Trk-L21-SW01 1000SX | Trk1 LACP
LACP
LACP Trunk Port LACP
Port Enabled Group Status Partner Status
---- ------- ------- ------- ------- -------
13 Active Trk41 Down No Success
14 Active Trk41 Down No Success
15 Active Trk41 Down No Success
16 Active Trk41 Down No Success
17 Active Trk50 Blocked Yes Failure
18 Active Trk50 Up Yes Success
19 Active Trk50 Up Yes Success
20 Active Trk50 Up Yes Success
21 Active Trk1 Blocked No Failure
22 Active Trk1 Up Yes Success
23 Active Trk1 Up Yes Success
24 Active Trk1 Up Yes Success
L32-Switch_02# show vlans
Status and Counters - VLAN Information
Maximum VLANs to support : 256
Primary VLAN : DEFAULT_VLAN
Management VLAN :
VLAN ID Name | Status Voice Jumbo
------- -------------------------------- + ---------- ----- -----
1 DEFAULT_VLAN | Port-based No No
100 NFS_LL_100 | Port-based No No
101 iSCSI_LL_101 | Port-based No No
200 vMotion_LL_200 | Port-based No No
300 WAN1_LL_300 | Port-based No No
301 WAN2_LL_301 | Port-based No No
400 Wifi-UN-LL_400 | Port-based No No
402 Wifi1-LL_402 | Port-based No No
500 Mgt-LL-500 | Port-based No No
700 Mach-LL_700 | Port-based No No
701 Femto-LL-701 | Port-based No No
702 Mobatime-LL-702 | Port-based No No
901 Redwood | Port-based No No
950 Video | Port-based No No
5900af Part
<L33-Switch-01>display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected,
I -- Individual, * -- Management port
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregate Interface: Bridge-Aggregation1
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/25 S 32768 2 {ACDEF}
XGE2/0/25 S 32768 2 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/25 5 0 1 0x1 , 02a0-98c4-9565 {ACDEF}
XGE2/0/25 6 0 1 0x1 , 02a0-98c4-9565 {ACDEF}
Aggregate Interface: Bridge-Aggregation2
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/27 S 32768 7 {ACDEF}
XGE2/0/27 S 32768 7 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/27 5 0 1 0x1 , 02a0-98c4-9aa3 {ACDEF}
XGE2/0/27 6 0 1 0x1 , 02a0-98c4-9aa3 {ACDEF}
Aggregate Interface: Bridge-Aggregation3
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/26 S 32768 3 {ACDEF}
XGE2/0/26 S 32768 3 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/26 1 0 1 0x1 , 02a0-98c4-9566 {ACDEF}
XGE2/0/26 3 0 1 0x1 , 02a0-98c4-9566 {ACDEF}
Aggregate Interface: Bridge-Aggregation4
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/28 S 32768 4 {ACDEF}
XGE2/0/28 S 32768 4 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/28 1 0 1 0x1 , 02a0-98c4-9aa4 {ACDEF}
XGE2/0/28 3 0 1 0x1 , 02a0-98c4-9aa4 {ACDEF}
Aggregate Interface: Bridge-Aggregation5
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/29 U 32768 8 {A}
XGE1/0/30 S 32768 8 {ACDEF}
XGE2/0/29 U 32768 8 {A}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/29 1 255 17 0xffff, 0011-3269-104f {ABCD}
XGE1/0/30 3 255 17 0xffff, 0011-3269-104f {ABCDEF}
XGE2/0/29 2 255 17 0xffff, 0011-3269-104f {ABCD}
Aggregate Interface: Bridge-Aggregation6
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/31 U 32768 6 {A}
XGE2/0/31 S 32768 6 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/31 1 255 33 0xffff, 0011-3269-1053 {ABCD}
XGE2/0/31 2 255 33 0xffff, 0011-3269-1053 {ABCDEF}
Aggregate Interface: Bridge-Aggregation50
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-1ef9
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/47 U 32768 1 {A}
XGE1/0/48 S 32768 1 {ACDEF}
XGE2/0/47 S 32768 1 {ACDEF}
XGE2/0/48 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/47 17 0 103 0xf840, 2c27-d77b-f840 {ACEF}
XGE1/0/48 20 0 103 0xf840, 2c27-d77b-f840 {ACDEF}
XGE2/0/47 18 0 103 0xf840, 2c27-d77b-f840 {ACDEF}
XGE2/0/48 19 0 103 0xf840, 2c27-d77b-f840 {ACDEF}
##################################################################################
Brief information about all VLANs:
Supported Minimum VLAN ID: 1
Supported Maximum VLAN ID: 4094
Default VLAN ID: 1
VLAN ID Name Port
1 Default-LL-1 BAGG1 BAGG2 BAGG3 BAGG4 BAGG5
BAGG6 BAGG50 FGE1/0/51 FGE1/0/52
FGE2/0/51 FGE2/0/52 XGE1/0/1
XGE1/0/2 XGE1/0/3 XGE1/0/4
XGE1/0/5 XGE1/0/6 XGE1/0/7
XGE1/0/8 XGE1/0/9 XGE1/0/10
XGE1/0/11 XGE1/0/12 XGE1/0/13
XGE1/0/14 XGE1/0/15 XGE1/0/16
XGE1/0/17 XGE1/0/18 XGE1/0/19
XGE1/0/20 XGE1/0/21 XGE1/0/22
XGE1/0/23 XGE1/0/24 XGE1/0/25
XGE1/0/26 XGE1/0/27 XGE1/0/28
XGE1/0/29 XGE1/0/30 XGE1/0/31
XGE1/0/32 XGE1/0/33 XGE1/0/34
XGE1/0/35 XGE1/0/36 XGE1/0/37
XGE1/0/38 XGE1/0/39 XGE1/0/40
XGE1/0/41 XGE1/0/42 XGE1/0/43
XGE1/0/44 XGE1/0/46 XGE1/0/47
XGE1/0/48 XGE2/0/1 XGE2/0/2
XGE2/0/3 XGE2/0/4 XGE2/0/5
XGE2/0/6 XGE2/0/7 XGE2/0/8
XGE2/0/9 XGE2/0/10 XGE2/0/11
XGE2/0/12 XGE2/0/13 XGE2/0/14
XGE2/0/15 XGE2/0/16 XGE2/0/17
XGE2/0/18 XGE2/0/19 XGE2/0/20
XGE2/0/21 XGE2/0/22 XGE2/0/23
XGE2/0/24 XGE2/0/25 XGE2/0/26
XGE2/0/27 XGE2/0/28 XGE2/0/29
XGE2/0/31 XGE2/0/32 XGE2/0/33
XGE2/0/34 XGE2/0/35 XGE2/0/36
XGE2/0/37 XGE2/0/38 XGE2/0/39
XGE2/0/41 XGE2/0/42 XGE2/0/43
XGE2/0/44 XGE2/0/46 XGE2/0/47
XGE2/0/48
100 NFS-LL-100 BAGG1 BAGG2 BAGG3 BAGG4 BAGG5
BAGG6 XGE1/0/1 XGE1/0/2 XGE1/0/3
XGE1/0/4 XGE1/0/5 XGE1/0/6
XGE1/0/7 XGE1/0/8 XGE1/0/9
XGE1/0/10 XGE1/0/11 XGE1/0/12
XGE1/0/13 XGE1/0/14 XGE1/0/15
XGE1/0/16 XGE1/0/17 XGE1/0/18
XGE1/0/19 XGE1/0/20 XGE1/0/21
XGE1/0/22 XGE1/0/23 XGE1/0/24
XGE1/0/25 XGE1/0/26 XGE1/0/27
XGE1/0/28 XGE1/0/30 XGE1/0/31
XGE1/0/45 XGE1/0/47 XGE2/0/1
XGE2/0/2 XGE2/0/3 XGE2/0/4
XGE2/0/5 XGE2/0/6 XGE2/0/7
XGE2/0/8 XGE2/0/9 XGE2/0/10
XGE2/0/11 XGE2/0/12 XGE2/0/13
XGE2/0/14 XGE2/0/15 XGE2/0/16
XGE2/0/17 XGE2/0/18 XGE2/0/19
XGE2/0/20 XGE2/0/21 XGE2/0/22
XGE2/0/23 XGE2/0/24 XGE2/0/25
XGE2/0/26 XGE2/0/27 XGE2/0/28
XGE2/0/30 XGE2/0/31 XGE2/0/32
XGE2/0/45
101 iSCSI-LL-101 BAGG1 BAGG2 BAGG3 BAGG4 BAGG5
BAGG6 XGE1/0/1 XGE1/0/2 XGE1/0/3
XGE1/0/4 XGE1/0/5 XGE1/0/6
XGE1/0/7 XGE1/0/8 XGE1/0/9
XGE1/0/10 XGE1/0/11 XGE1/0/12
XGE1/0/13 XGE1/0/14 XGE1/0/15
XGE1/0/16 XGE1/0/17 XGE1/0/18
XGE1/0/19 XGE1/0/20 XGE1/0/21
XGE1/0/22 XGE1/0/23 XGE1/0/24
XGE1/0/25 XGE1/0/26 XGE1/0/27
XGE1/0/28 XGE1/0/30 XGE1/0/31
XGE1/0/45 XGE1/0/47 XGE2/0/1
XGE2/0/2 XGE2/0/3 XGE2/0/4
XGE2/0/5 XGE2/0/6 XGE2/0/7
XGE2/0/8 XGE2/0/9 XGE2/0/10
XGE2/0/11 XGE2/0/12 XGE2/0/13
XGE2/0/14 XGE2/0/15 XGE2/0/16
XGE2/0/17 XGE2/0/18 XGE2/0/19
XGE2/0/20 XGE2/0/21 XGE2/0/22
XGE2/0/23 XGE2/0/24 XGE2/0/25
XGE2/0/26 XGE2/0/27 XGE2/0/28
XGE2/0/30 XGE2/0/31 XGE2/0/32
XGE2/0/45
200 vMotion-LL-200 XGE1/0/1 XGE1/0/2 XGE1/0/3
XGE1/0/4 XGE1/0/5 XGE1/0/6
XGE1/0/7 XGE1/0/8 XGE1/0/9
XGE1/0/10 XGE1/0/11 XGE1/0/12
XGE1/0/13 XGE1/0/14 XGE1/0/15
XGE1/0/16 XGE1/0/17 XGE1/0/18
XGE1/0/19 XGE1/0/20 XGE1/0/21
XGE1/0/22 XGE1/0/23 XGE1/0/24
XGE1/0/45 XGE1/0/47 XGE2/0/1
XGE2/0/2 XGE2/0/3 XGE2/0/4
XGE2/0/5 XGE2/0/6 XGE2/0/7
XGE2/0/8 XGE2/0/9 XGE2/0/10
XGE2/0/11 XGE2/0/12 XGE2/0/13
XGE2/0/14 XGE2/0/15 XGE2/0/16
XGE2/0/17 XGE2/0/18 XGE2/0/19
XGE2/0/20 XGE2/0/21 XGE2/0/22
XGE2/0/23 XGE2/0/24 XGE2/0/45
300 VLAN 0300 BAGG50 XGE1/0/40 XGE1/0/47
XGE1/0/48 XGE2/0/40 XGE2/0/47
XGE2/0/48
700 VLAN 0700 BAGG50 XGE1/0/1 XGE1/0/2
XGE1/0/3 XGE1/0/4 XGE1/0/5
XGE1/0/6 XGE1/0/7 XGE1/0/8
XGE1/0/9 XGE1/0/10 XGE1/0/11
XGE1/0/12 XGE1/0/13 XGE1/0/14
XGE1/0/15 XGE1/0/16 XGE1/0/17
XGE1/0/18 XGE1/0/19 XGE1/0/20
XGE1/0/21 XGE1/0/22 XGE1/0/23
XGE1/0/24 XGE1/0/45 XGE1/0/47
XGE1/0/48 XGE2/0/1 XGE2/0/2
XGE2/0/3 XGE2/0/4 XGE2/0/5
XGE2/0/6 XGE2/0/7 XGE2/0/8
XGE2/0/9 XGE2/0/10 XGE2/0/11
XGE2/0/12 XGE2/0/13 XGE2/0/14
XGE2/0/15 XGE2/0/16 XGE2/0/17
XGE2/0/18 XGE2/0/19 XGE2/0/20
XGE2/0/21 XGE2/0/22 XGE2/0/23
XGE2/0/24 XGE2/0/30 XGE2/0/45
XGE2/0/47 XGE2/0/48
701 VLAN 0701 BAGG50 XGE1/0/1 XGE1/0/2
XGE1/0/3 XGE1/0/4 XGE1/0/5
XGE1/0/6 XGE1/0/7 XGE1/0/8
XGE1/0/9 XGE1/0/10 XGE1/0/11
XGE1/0/12 XGE1/0/13 XGE1/0/14
XGE1/0/15 XGE1/0/16 XGE1/0/17
XGE1/0/18 XGE1/0/19 XGE1/0/20
XGE1/0/21 XGE1/0/22 XGE1/0/23
XGE1/0/24 XGE1/0/45 XGE1/0/47
XGE1/0/48 XGE2/0/1 XGE2/0/2
XGE2/0/3 XGE2/0/4 XGE2/0/5
XGE2/0/6 XGE2/0/7 XGE2/0/8
XGE2/0/9 XGE2/0/10 XGE2/0/11
XGE2/0/12 XGE2/0/13 XGE2/0/14
XGE2/0/15 XGE2/0/16 XGE2/0/17
XGE2/0/18 XGE2/0/19 XGE2/0/20
XGE2/0/21 XGE2/0/22 XGE2/0/23
XGE2/0/24 XGE2/0/45 XGE2/0/47
XGE2/0/48
702 VLAN 0702 BAGG50 XGE1/0/1 XGE1/0/2
XGE1/0/3 XGE1/0/4 XGE1/0/5
XGE1/0/6 XGE1/0/7 XGE1/0/8
XGE1/0/9 XGE1/0/10 XGE1/0/11
XGE1/0/12 XGE1/0/13 XGE1/0/14
XGE1/0/15 XGE1/0/16 XGE1/0/17
XGE1/0/18 XGE1/0/19 XGE1/0/20
XGE1/0/21 XGE1/0/22 XGE1/0/23
XGE1/0/24 XGE1/0/45 XGE1/0/47
XGE1/0/48 XGE2/0/1 XGE2/0/2
XGE2/0/3 XGE2/0/4 XGE2/0/5
XGE2/0/6 XGE2/0/7 XGE2/0/8
XGE2/0/9 XGE2/0/10 XGE2/0/11
XGE2/0/12 XGE2/0/13 XGE2/0/14
XGE2/0/15 XGE2/0/16 XGE2/0/17
XGE2/0/18 XGE2/0/19 XGE2/0/20
XGE2/0/21 XGE2/0/22 XGE2/0/23
XGE2/0/24 XGE2/0/45 XGE2/0/47
XGE2/0/48
901 Wifi-Redwood-901 BAGG50 XGE1/0/1 XGE1/0/2
XGE1/0/3 XGE1/0/4 XGE1/0/5
XGE1/0/6 XGE1/0/7 XGE1/0/8
XGE1/0/9 XGE1/0/10 XGE1/0/11
XGE1/0/12 XGE1/0/13 XGE1/0/14
XGE1/0/15 XGE1/0/16 XGE1/0/17
XGE1/0/18 XGE1/0/19 XGE1/0/20
XGE1/0/21 XGE1/0/22 XGE1/0/23
XGE1/0/24 XGE1/0/45 XGE1/0/47
XGE1/0/48 XGE2/0/1 XGE2/0/2
XGE2/0/3 XGE2/0/4 XGE2/0/5
XGE2/0/6 XGE2/0/7 XGE2/0/8
XGE2/0/9 XGE2/0/10 XGE2/0/11
XGE2/0/12 XGE2/0/13 XGE2/0/14
XGE2/0/15 XGE2/0/16 XGE2/0/17
XGE2/0/18 XGE2/0/19 XGE2/0/20
XGE2/0/21 XGE2/0/22 XGE2/0/23
XGE2/0/24 XGE2/0/45 XGE2/0/47
XGE2/0/48
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2017 06:41 AM - edited тАО09-01-2017 07:11 AM
тАО09-01-2017 06:41 AM - edited тАО09-01-2017 07:11 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
OK, better now.
A first thing that can be noticed looking at BAGG50 status on the IRF Stack:
Aggregate Interface: Bridge-Aggregation50 Aggregation Mode: Dynamic Loadsharing Type: Shar Management VLAN : None System ID: 0x8000, e8f7-2431-1ef9 Local: Port Status Priority Oper-Key Flag -------------------------------------------------------------------------------- XGE1/0/47 U 32768 1 {A} XGE1/0/48 S 32768 1 {ACDEF} XGE2/0/47 S 32768 1 {ACDEF} XGE2/0/48 S 32768 1 {ACDEF} Remote: Actor Partner Priority Oper-Key SystemID Flag -------------------------------------------------------------------------------- XGE1/0/47 17 0 103 0xf840, 2c27-d77b-f840 {ACEF} XGE1/0/48 20 0 103 0xf840, 2c27-d77b-f840 {ACDEF} XGE2/0/47 18 0 103 0xf840, 2c27-d77b-f840 {ACDEF} XGE2/0/48 19 0 103 0xf840, 2c27-d77b-f840 {ACDEF}
is that port XGE1/0/47 state is Unselected (U): this means that traffic coming from the Trk50 (2910al) on the same link (so from Port 17, see indeed Partner 17) will be dropped and this is not a good thing to start with.
This situation can be observed looking at the Trk50's Port 17 status as reported here:
LACP Trunk Port LACP Port Enabled Group Status Partner Status ---- ------- ------- ------- ------- ------- 13 Active Trk41 Down No Success 14 Active Trk41 Down No Success 15 Active Trk41 Down No Success 16 Active Trk41 Down No Success 17 Active Trk50 Blocked Yes Failure 18 Active Trk50 Up Yes Success 19 Active Trk50 Up Yes Success 20 Active Trk50 Up Yes Success 21 Active Trk1 Blocked No Failure 22 Active Trk1 Up Yes Success 23 Active Trk1 Up Yes Success 24 Active Trk1 Up Yes Success
So this is a thing that need, in my opinion, to be investigated further.
Then, and there could be a strict relationship with the BAGG50<-->Trk50 non good status reported above, another thing to notice is that VLAN IDs assignment on BAGG's member interfaces (not directly on BAGG itself) has an anomaly [**] exactly regarding the XGE1/0/47; looking at VLANs defined on the IRF Stack BAGG50 - and so its XGE1/0/47, XGE1/0/48, XGE2/0/47 and XGE2/0/48 member interfaces [*] - permits those tagged VLAN IDs: 300, 700, 701, 702 and 901 BUT Interface XGE1/0/47 - it very alone - is also tagged for VLAN IDs 100, 101 and 200 which is pretty strange since, being a member of BAGG50, it should have the same exact settings of other three member interfaces with regard to VLAN IDs tagging (this other than all other physical interface settings, which I presume already OK); interfaces XGE1/0/48, XGE2/0/47 and XGE2/0/48 aren't tagged on VLAN IDs 100, 101 and 200 exactly as it isn't the whole BAGG50 for those VLAN IDs.
See what I mean here:
Brief information about all VLANs: Supported Minimum VLAN ID: 1 Supported Maximum VLAN ID: 4094 Default VLAN ID: 1 VLAN ID Name Port ... 100 NFS-LL-100 BAGG1 BAGG2 BAGG3 BAGG4 BAGG5 BAGG6 XGE1/0/1 XGE1/0/2 XGE1/0/3 XGE1/0/4 XGE1/0/5 XGE1/0/6 XGE1/0/7 XGE1/0/8 XGE1/0/9 XGE1/0/10 XGE1/0/11 XGE1/0/12 XGE1/0/13 XGE1/0/14 XGE1/0/15 XGE1/0/16 XGE1/0/17 XGE1/0/18 XGE1/0/19 XGE1/0/20 XGE1/0/21 XGE1/0/22 XGE1/0/23 XGE1/0/24 XGE1/0/25 XGE1/0/26 XGE1/0/27 XGE1/0/28 XGE1/0/30 XGE1/0/31 XGE1/0/45 XGE1/0/47 XGE2/0/1 XGE2/0/2 XGE2/0/3 XGE2/0/4 XGE2/0/5 XGE2/0/6 XGE2/0/7 XGE2/0/8 XGE2/0/9 XGE2/0/10 XGE2/0/11 XGE2/0/12 XGE2/0/13 XGE2/0/14 XGE2/0/15 XGE2/0/16 XGE2/0/17 XGE2/0/18 XGE2/0/19 XGE2/0/20 XGE2/0/21 XGE2/0/22 XGE2/0/23 XGE2/0/24 XGE2/0/25 XGE2/0/26 XGE2/0/27 XGE2/0/28 XGE2/0/30 XGE2/0/31 XGE2/0/32 XGE2/0/45 101 iSCSI-LL-101 BAGG1 BAGG2 BAGG3 BAGG4 BAGG5 BAGG6 XGE1/0/1 XGE1/0/2 XGE1/0/3 XGE1/0/4 XGE1/0/5 XGE1/0/6 XGE1/0/7 XGE1/0/8 XGE1/0/9 XGE1/0/10 XGE1/0/11 XGE1/0/12 XGE1/0/13 XGE1/0/14 XGE1/0/15 XGE1/0/16 XGE1/0/17 XGE1/0/18 XGE1/0/19 XGE1/0/20 XGE1/0/21 XGE1/0/22 XGE1/0/23 XGE1/0/24 XGE1/0/25 XGE1/0/26 XGE1/0/27 XGE1/0/28 XGE1/0/30 XGE1/0/31 XGE1/0/45 XGE1/0/47 XGE2/0/1 XGE2/0/2 XGE2/0/3 XGE2/0/4 XGE2/0/5 XGE2/0/6 XGE2/0/7 XGE2/0/8 XGE2/0/9 XGE2/0/10 XGE2/0/11 XGE2/0/12 XGE2/0/13 XGE2/0/14 XGE2/0/15 XGE2/0/16 XGE2/0/17 XGE2/0/18 XGE2/0/19 XGE2/0/20 XGE2/0/21 XGE2/0/22 XGE2/0/23 XGE2/0/24 XGE2/0/25 XGE2/0/26 XGE2/0/27 XGE2/0/28 XGE2/0/30 XGE2/0/31 XGE2/0/32 XGE2/0/45 200 vMotion-LL-200 XGE1/0/1 XGE1/0/2 XGE1/0/3 XGE1/0/4 XGE1/0/5 XGE1/0/6 XGE1/0/7 XGE1/0/8 XGE1/0/9 XGE1/0/10 XGE1/0/11 XGE1/0/12 XGE1/0/13 XGE1/0/14 XGE1/0/15 XGE1/0/16 XGE1/0/17 XGE1/0/18 XGE1/0/19 XGE1/0/20 XGE1/0/21 XGE1/0/22 XGE1/0/23 XGE1/0/24 XGE1/0/45 XGE1/0/47 XGE2/0/1 XGE2/0/2 XGE2/0/3 XGE2/0/4 XGE2/0/5 XGE2/0/6 XGE2/0/7 XGE2/0/8 XGE2/0/9 XGE2/0/10 XGE2/0/11 XGE2/0/12 XGE2/0/13 XGE2/0/14 XGE2/0/15 XGE2/0/16 XGE2/0/17 XGE2/0/18 XGE2/0/19 XGE2/0/20 XGE2/0/21 XGE2/0/22 XGE2/0/23 XGE2/0/24 XGE2/0/45 ...
Removing XGE1/0/47's VLAN tagging on VLAN IDs 100, 101 and 200 would help in fixing things.
[*] indeed if BAGG50 is tagged on some VLAN IDs so are there its member interfaces.
[**] BAGG configuration on Comware requires to configure all at BAGG level (then configuration - VLAN IDs tagging included - are going to be propagated down to BAGG member interfaces automatically).
This just looking at IRF Stack <--> 2910al interconnection.
To check BAGG50 interface members' status on IRF Stack side, perform:
display interface brief | include 1/0/4[7-8]
display interface brief | include 2/0/4[7-8]
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-04-2017 01:24 AM
тАО09-04-2017 01:24 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
Hello Parnassus,
I have to correct this mistakes but i have to make that on site.
In the meantime i have checked my other site that have the same configuration and the same issue.
I don't have this mistakes (if i have understood well) on this config so it's not the source of the loosing BAGG.
Here are the config:
Procurve 2900al:
C11-Switch_05# show trunks
Load Balancing
Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- --------
37 | 100/1000T | Trk50 LACP
38 | 100/1000T | Trk50 LACP
39 | 100/1000T | Trk50 LACP
40 | 100/1000T | Trk50 LACP
41 | 100/1000T | Trk10 LACP
42 | 100/1000T | Trk11 LACP
43 | 100/1000T | Trk10 LACP
44 | 100/1000T | Trk11 LACP
45 | 100/1000T | Trk10 LACP
46 | 100/1000T | Trk11 LACP
47 | 1000SX | Trk10 LACP
48 | 1000SX | Trk11 LACP
C11-Switch_05# show lacp
LACP
LACP Trunk Port LACP
Port Enabled Group Status Partner Status
---- ------- ------- ------- ------- -------
37 Active Trk50 Up Yes Success
38 Active Trk50 Up Yes Success
39 Active Trk50 Up Yes Success
40 Active Trk50 Up Yes Success
41 Active Trk10 Up Yes Success
42 Active Trk11 Up Yes Success
43 Active Trk10 Up Yes Success
44 Active Trk11 Up Yes Success
45 Active Trk10 Up Yes Success
46 Active Trk11 Up Yes Success
47 Active Trk10 Up Yes Success
48 Active Trk11 Up Yes Success
ComWare 5900af:
<C13-Switch-01>display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected,
I -- Individual, * -- Management port
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregate Interface: Bridge-Aggregation1
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/25 S 32768 5 {ACDEF}
XGE2/0/25 S 32768 5 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/25 6 0 1 0x1 , 02a0-98c4-97cb {ACDEF}
XGE2/0/25 5 0 1 0x1 , 02a0-98c4-97cb {ACDEF}
Aggregate Interface: Bridge-Aggregation2
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/27 S 32768 1 {ACDEF}
XGE2/0/27 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/27 6 0 1 0x1 , 02a0-98c4-9fa9 {ACDEF}
XGE2/0/27 5 0 1 0x1 , 02a0-98c4-9fa9 {ACDEF}
Aggregate Interface: Bridge-Aggregation3
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/26 S 32768 2 {ACDEF}
XGE2/0/26 S 32768 2 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/26 1 0 1 0x1 , 02a0-98c4-9faa {ACDEF}
XGE2/0/26 3 0 1 0x1 , 02a0-98c4-9faa {ACDEF}
Aggregate Interface: Bridge-Aggregation4
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/28 S 32768 4 {ACDEF}
XGE2/0/28 S 32768 4 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/28 3 0 1 0x1 , 02a0-98c4-97cc {ACDEF}
XGE2/0/28 1 0 1 0x1 , 02a0-98c4-97cc {ACDEF}
Aggregate Interface: Bridge-Aggregation5
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/29 S 32768 8 {ACDEF}
XGE1/0/30 S 32768 8 {ACDEF}
XGE2/0/29 S 32768 8 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/29 1 255 17 0xffff, 0011-3262-3a61 {ABCDEF}
XGE1/0/30 3 255 17 0xffff, 0011-3262-3a61 {ABCDEF}
XGE2/0/29 2 255 17 0xffff, 0011-3262-3a61 {ABCDEF}
Aggregate Interface: Bridge-Aggregation6
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/31 S 32768 7 {ACDEF}
XGE2/0/31 S 32768 7 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/31 1 255 33 0xffff, 0011-3262-3a65 {ABCDEF}
XGE2/0/31 2 255 33 0xffff, 0011-3262-3a65 {ABCDEF}
Aggregate Interface: Bridge-Aggregation50
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-2431-165c
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/47 S 32768 3 {ACDEF}
XGE1/0/48 S 32768 3 {ACDEF}
XGE2/0/47 S 32768 3 {ACDEF}
XGE2/0/48 S 32768 3 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/47 37 0 103 0x5240, a0b3-cca7-5240 {ACDEF}
XGE1/0/48 39 0 103 0x5240, a0b3-cca7-5240 {ACDEF}
XGE2/0/47 38 0 103 0x5240, a0b3-cca7-5240 {ACDEF}
XGE2/0/48 40 0 103 0x5240, a0b3-cca7-5240 {ACDEF}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-04-2017 07:03 AM
тАО09-04-2017 07:03 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
Hi, I never wrote that what I found in your first site configuration you gave was the culprit of your issue...it's just a thing I noticed and a thing to investigate on further.
Glad your second site shows no issue on the BAGG link as the first site (even if it shows the same issue related to VLAN addition you reported the first site has).
At this point would be important to exactly explain what happen. You initially wrote:
idinfo wrote: Everything is working as needed but when i add a new VLAN in the Switch i loose the connectivity of the BAGG. To reestablish the connectivity i have to unplugg all the BAGG cables ans reconnect them.
but you still haven't described what you did (...when i add a new VLAN in the Switch...), on which switch(es) you did that and what logs were generated when you did that VLAN related configuration.
Are you using only Port based VLANs or are you also routing among (IP-based) VLANs? and, if so (so there are Protocol based VLANs too), which switch is actually performing the IP Routing task?
Perform a dispaly vlan vlanid on the IRF Stack for each vlanid (VLAN ID) you have definded on the IRF Stack, repeat the same on the Switch you use on the Backbone (something like show vlans vlanid), this to have a full idea of your VLANs configuration IRF Stack side and Backbone Switch side.
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2017 10:05 AM
тАО09-06-2017 10:05 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
Hi,
Sorry for my bad english, that's not my intention ;-)
This is the steps that lead to BAGG breaking:
- Adding the VLAN to the Backbone Switch (2910) => No Impact
- Tagging all the needed ports (including BAGG) with the new VLAN on the Backbone Switch (2910) => No Impact
- Adding an IP to the Backbone Switch (2910) => No Impact
- Adding the VLAN to the IRF Stack (5900AF) => No Impact
- Tagging all the needed ports (Include BAGG50) with the new VLAN on the Backbone Switch (5900AF) + Adding an IP to the Backbone Switch (5900AF) => BAGG Down
I have to check if it's "Assigning the VLAN" or "Setting the IP to the VLAN" that Pull Down the BAGG.
I will check that Friday when i will correct the mistakes that you have detected.
Sorry again and thanks for your precious help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2017 08:32 AM
тАО09-08-2017 08:32 AM
Re: Loosing BAGG When assigning New VLAN 5900AF
Hi,
Here is the results of the tests ans checks:
Are you using only Port based VLANs or are you also routing among (IP-based) VLANs? and, if so (so there are Protocol based VLANs too), which switch is actually performing the IP Routing task?
Only Port-Based VLANs. IP Routing is disable on all Switchs.
Perform a dispaly vlan vlanid on the IRF Stack for each vlanid (VLAN ID) you have definded on the IRF Stack, repeat the same on the Switch you use on the Backbone (something like show vlans vlanid), this to have a full idea of your VLANs configuration IRF Stack side and Backbone Switch side.
The two Sides seams to be correct for the VLANs.
I have corrected the port Tagging on port 47 and now i have all my trunks valid.
I have made my tests this morning and i was not be able to reproduce the issue.
The only difference was that i have made my changes directly connected to the IRF Stack (not remotely) and corrected the mistake of port 47.
Hope the issue is solved. I will try next time remotely and not remotls to check if it's the source of the issue but i dont mind it this.
Thans for your help