- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- GbE2 Reports Packet Errors when Activating XConnec...
BladeSystem - General
1752782
Members
6433
Online
108789
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
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
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
06-06-2007 04:51 AM
06-06-2007 04:51 AM
GbE2 Reports Packet Errors when Activating XConnect
Hi all.
I have an issue with a enclosure with 2 GbE2. Basically what happens is that when i activate the XConnect Ports (17 & 18) Blade Servers loose the connection and packet errors are reported.
I believe this is a trunk issue but, beside activating the trunk and enabling SIP and DIP as protocol, do I have to make ports 17 and 18 member of all the Vlans that transverse that link?
Can someone please give me a working example of a environmentlike this?
Another quick question: is there a number maximum of Vlans that can transverse a trunk in GbE2 or is it unlimited? I have 7 or 8 Different Vlans.
This is the actual configuration:
/c/l2/vlan 1
name "Default"
def 1 2 5 6 13 14 17 18 24
/c/l2/vlan 200
ena
name "HeartBeat"
def 3 7 15 20
/c/l2/vlan 300
ena
name "Gest"
def 19
/c/l2/vlan 400
ena
name "ServerFarm"
def 4 16 19 23
/c/l2/vlan 500
ena
name "CRM_LoadBalancer"
def 8 11 19
/c/l2/vlan 600
ena
name "DMZ_FrontEnd"
def 10 12 21 22
/c/l2/vlan 700
ena
name "DMZ_BackEnd"
def 9 21 22
This is the configuration i believe will solve this issue:
Trunk Group 1
Protocol - Static
Current settings: enabled
ports: 17, 18
Current IP Trunk Hash IP trunk hash settings:
sip dip
/c/l2/trunk/1/add/17-18
/c/l2/thash/sip/enable
/c/l2/thash/dip/enable
/c/l2/vlan 1
name "Default"
def 1 2 5 6 13 14 17 18 24
/c/l2/vlan 200
ena
name "HeartBeat"
def 3 7 15 17 18 20
/c/l2/vlan 300
ena
name "Gest"
def 17 18 19
/c/l2/vlan 400
ena
name "ServerFarm"
def 4 16 17 18 19 23
/c/l2/vlan 500
ena
name "LoadBalancer"
def 8 11 17 18 19
/c/l2/vlan 600
ena
name "DMZ_FrontEnd"
def 10 12 17 18 21 22
/c/l2/vlan 700
ena
name "DMZ_BackEnd"
def 9 17 18 21 22
Thanks a lot for your reply.
I have an issue with a enclosure with 2 GbE2. Basically what happens is that when i activate the XConnect Ports (17 & 18) Blade Servers loose the connection and packet errors are reported.
I believe this is a trunk issue but, beside activating the trunk and enabling SIP and DIP as protocol, do I have to make ports 17 and 18 member of all the Vlans that transverse that link?
Can someone please give me a working example of a environmentlike this?
Another quick question: is there a number maximum of Vlans that can transverse a trunk in GbE2 or is it unlimited? I have 7 or 8 Different Vlans.
This is the actual configuration:
/c/l2/vlan 1
name "Default"
def 1 2 5 6 13 14 17 18 24
/c/l2/vlan 200
ena
name "HeartBeat"
def 3 7 15 20
/c/l2/vlan 300
ena
name "Gest"
def 19
/c/l2/vlan 400
ena
name "ServerFarm"
def 4 16 19 23
/c/l2/vlan 500
ena
name "CRM_LoadBalancer"
def 8 11 19
/c/l2/vlan 600
ena
name "DMZ_FrontEnd"
def 10 12 21 22
/c/l2/vlan 700
ena
name "DMZ_BackEnd"
def 9 21 22
This is the configuration i believe will solve this issue:
Trunk Group 1
Protocol - Static
Current settings: enabled
ports: 17, 18
Current IP Trunk Hash IP trunk hash settings:
sip dip
/c/l2/trunk/1/add/17-18
/c/l2/thash/sip/enable
/c/l2/thash/dip/enable
/c/l2/vlan 1
name "Default"
def 1 2 5 6 13 14 17 18 24
/c/l2/vlan 200
ena
name "HeartBeat"
def 3 7 15 17 18 20
/c/l2/vlan 300
ena
name "Gest"
def 17 18 19
/c/l2/vlan 400
ena
name "ServerFarm"
def 4 16 17 18 19 23
/c/l2/vlan 500
ena
name "LoadBalancer"
def 8 11 17 18 19
/c/l2/vlan 600
ena
name "DMZ_FrontEnd"
def 10 12 17 18 21 22
/c/l2/vlan 700
ena
name "DMZ_BackEnd"
def 9 17 18 21 22
Thanks a lot for your reply.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2007 10:08 AM
06-11-2007 10:08 AM
Re: GbE2 Reports Packet Errors when Activating XConnect
p-Class or c-Class?
p-Class:
ports 17 and 18 (XConnects) on a GBE2p are enabled default and are configured as trunk 1 (aka a port channel). Ports 17 and 18 are only in vlan 1 by default (i.e. access ports in Vlan 1)
c-Class:
ports 17 and 18 are disabled by default. If you enable them they are automatically configured as trunk 1 and are in VLAN 1 by default.
You are correct. In order for the XConnects to work like dot1q trunks (carry all VLANs), ports 17 and 18 need to be tagged and be added as members of the desired VLANs. The config for ports 17 and 18 on both gbe2 switches in a pair must be identical.
Your proposed config looks good as long as you tag ports 17 and 18.
And the trunk hashing algorithm doesn't need to be modified in order for this to work. I think the default is sip dip anyway.
I believe the GBE2 switches support up to 256 VLANs and there is no limitation to the number of VLANs a port (like 17 and 18) can be a member of.
p-Class:
ports 17 and 18 (XConnects) on a GBE2p are enabled default and are configured as trunk 1 (aka a port channel). Ports 17 and 18 are only in vlan 1 by default (i.e. access ports in Vlan 1)
c-Class:
ports 17 and 18 are disabled by default. If you enable them they are automatically configured as trunk 1 and are in VLAN 1 by default.
You are correct. In order for the XConnects to work like dot1q trunks (carry all VLANs), ports 17 and 18 need to be tagged and be added as members of the desired VLANs. The config for ports 17 and 18 on both gbe2 switches in a pair must be identical.
Your proposed config looks good as long as you tag ports 17 and 18.
And the trunk hashing algorithm doesn't need to be modified in order for this to work. I think the default is sip dip anyway.
I believe the GBE2 switches support up to 256 VLANs and there is no limitation to the number of VLANs a port (like 17 and 18) can be a member of.
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