- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Trouble Trunking Ports (particularly with vSphere)
Switches, Hubs, and Modems
1748256
Members
3866
Online
108760
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
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
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
тАО07-08-2010 11:13 AM
тАО07-08-2010 11:13 AM
Trouble Trunking Ports (particularly with vSphere)
Hello all...
I have a strange problem I was wondering if anyone here would be kind enough to help me through.
First of all, let me say that this was all working until our stupid var came in to setup the new wireless controller card and screwed things up...
Anyway, a brief explanation. Our core is an 8212. Everything I am about to mention is connected to the core. Also, there are many vlans. The vlan I am in is vlan 90. Our vsphere environment is connected to the core, also in vlan 90. Our NetApp storage has a couple vifs, one in vlan 90, and one in vlan 101. vlan 101 is for NFS storage traffic. On the switch side, there WERE 10 trunks, each trunk containing 2 ports either from esx hosts or NetApp SAN. There are two trunks (4 NICs) for storage and four trunks (8 NICs)for each esx host (host a and b) = 10 trunks total.
Again, everything WAS working fine for over a month. NOW, there are 7 trunks.
The original 2 for storage are still there and still working... OK... Host A "magically" lost 3 of the 4 trunks. The only trunk remaining is the one that is the NFS storage NICs on the ESX side for host A...That's OK... Host B has 3 of it's 4 trunks remaining, yet NONE of them work...
As an example, Two NICs from ESX B are Teamed on the ESX side (IP Hash) and plugged into any two ports in vlan 90... I can ping the address... I now trunk the two ports on the switch side, again put the trunk in vlan 90... I get nothing.
I am at a loss here. I am not a networking guy, I am more storage and virtual guy, but I know enough to get by. Any suggestions are welcome as I need to fix this because our var is useless. Trunking is a very easy thing, I don't understand what is wrong. Also, I think the var said he accidentally put the wireless controller card in the wrong vlan and all our access points went down and it killed all our wireless. After this, everything went to hell in a handbasket. Any thoughts...
Thanks Chris
I have a strange problem I was wondering if anyone here would be kind enough to help me through.
First of all, let me say that this was all working until our stupid var came in to setup the new wireless controller card and screwed things up...
Anyway, a brief explanation. Our core is an 8212. Everything I am about to mention is connected to the core. Also, there are many vlans. The vlan I am in is vlan 90. Our vsphere environment is connected to the core, also in vlan 90. Our NetApp storage has a couple vifs, one in vlan 90, and one in vlan 101. vlan 101 is for NFS storage traffic. On the switch side, there WERE 10 trunks, each trunk containing 2 ports either from esx hosts or NetApp SAN. There are two trunks (4 NICs) for storage and four trunks (8 NICs)for each esx host (host a and b) = 10 trunks total.
Again, everything WAS working fine for over a month. NOW, there are 7 trunks.
The original 2 for storage are still there and still working... OK... Host A "magically" lost 3 of the 4 trunks. The only trunk remaining is the one that is the NFS storage NICs on the ESX side for host A...That's OK... Host B has 3 of it's 4 trunks remaining, yet NONE of them work...
As an example, Two NICs from ESX B are Teamed on the ESX side (IP Hash) and plugged into any two ports in vlan 90... I can ping the address... I now trunk the two ports on the switch side, again put the trunk in vlan 90... I get nothing.
I am at a loss here. I am not a networking guy, I am more storage and virtual guy, but I know enough to get by. Any suggestions are welcome as I need to fix this because our var is useless. Trunking is a very easy thing, I don't understand what is wrong. Also, I think the var said he accidentally put the wireless controller card in the wrong vlan and all our access points went down and it killed all our wireless. After this, everything went to hell in a handbasket. Any thoughts...
Thanks Chris
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2010 12:47 AM
тАО07-09-2010 12:47 AM
Re: Trouble Trunking Ports (particularly with vSphere)
Hi,
First off, what's a "var" ? :)
What type of trunks are you using (static or LACP)?
Could you post up the config on your 8212 as well?
First off, what's a "var" ? :)
What type of trunks are you using (static or LACP)?
Could you post up the config on your 8212 as well?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 10:26 AM
тАО08-02-2010 10:26 AM
Re: Trouble Trunking Ports (particularly with vSphere)
Thanks for responding. Sorry I got to this so late.
First, var stands for Value Added Resource. Basically, a consultant.
Secondly, they are static trunks.
Lastly, I was able to get this working by disabling all the ports I was trunking, deleting all the trunking info in the config, recreating it, and re-enabling the ports.
I'm not sure what happened, but it's fixed
First, var stands for Value Added Resource. Basically, a consultant.
Secondly, they are static trunks.
Lastly, I was able to get this working by disabling all the ports I was trunking, deleting all the trunking info in the config, recreating it, and re-enabling the ports.
I'm not sure what happened, but it's fixed
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