- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Link-aggregation and ESXi5 issues with A5120
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
Forums
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
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-07-2014 03:30 AM - last edited on 02-08-2014 11:44 PM by Lisa198503
02-07-2014 03:30 AM - last edited on 02-08-2014 11:44 PM by Lisa198503
Link-aggregation and ESXi5 issues with A5120
Hi, we have problems configuring ESXi with IRF stack.
Example:
- 4 A5120 in IRF stack
- ESXi 5.5 with 4 links with ip based hash algo
we want these 4 links are being used as the default VLAN for the connesisoni ESXi LAN segment, and for any other VLANs configured to separate the traffic at the Port Group ESXI (vMotion, etc.).
Starting from the default IRF configuration, the PVID to this VLAN is 1 (default). Aggregating 4 ports as described in the documents (port link-type trunk), leaving ESXi without VLAN configuration on the VM port group for the LAN do not works.
interface bridge-aggregation 21
description LAG esxi11 lan
port link-type trunk
port trunk permit vlan 1
stp disable
interface GigabitEthernet 1/0/39
port link-type trunk
port trunk permit vlan 1
port link-aggregation group 21
interface GigabitEthernet 4/0/39
port link-type trunk
port trunk permit vlan 1
port link-aggregation group 21
Instead we works by configuring as "port link-type access" and leaving everything not tagged
interface bridge-aggregation 21
description LAG esxi11 lan
interface GigabitEthernet 1/0/39
port link-aggregation group 21
interface GigabitEthernet 4/0/39
port link-aggregation group 21
interface Bridge-Aggregation 21
port link-type access
port access vlan 1
but we have 2 problems:
1. when a member of the IRF is disconnected, some VMs do not communicate on the network (probably port sense problems or unsupporte port-tyoe access mode issue...), all works again and "immediately" as soon as we attach power supply, also if member switch is only on in this phase.
2. Probably with this configuration, we can not use VLAN in port group
What is wrong in the configuration with link-type trunk ?
Thank you in advance
P.S. This post has been splitted off from other thread in Comware-Based, and edited its subject. - HP Forum Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2014 04:02 AM
02-07-2014 04:02 AM
Re: Link-aggregation and ESXi5 issues with A5120
Ok. We resolved trunk mode issue with this config:
interface bridge-aggregation 21
description LAG esxi11 lan
port link-type trunk
port trunk pvid vlan 1
port trunk permit vlan 1
Probbaly we erroneously assagned default VLAN to other than default VLAN 1...
So we resolved also issue 2 as we can add permitted VLAN on this trunk (ESXi vMotion, ...).
Can someone help on issue 1 ? could be related to the configuration with link-type access? not supported ?
Thank you