- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Virtual Connect, only sparse connectivity to s...
BladeSystem - General
1752354
Members
5789
Online
108787
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
12-27-2007 05:40 AM
12-27-2007 05:40 AM
Virtual Connect, only sparse connectivity to server with NCU generated VLAN
On VC i have an uplink (not "shared uplink set") carrying tagged packets of several VLANs from Procurve 2810-48G.
Several ESX3.5 servers have vSwitches connected to this uplink, and the VLANs are running fine at least for console and VI clients.
I connected a Windows 2003 server to the uplink network, using Network Configuration Utility to configure an interface for VLAN1. Now I can ping to and from the server, but most other sorts of traffic fails - AD logon, DNS, SMB...
Just tried to add a shared uplink set and network for the Windows server, and this works much better.
What can be wrong in the NCU configuration?
Ole Thomsen
Several ESX3.5 servers have vSwitches connected to this uplink, and the VLANs are running fine at least for console and VI clients.
I connected a Windows 2003 server to the uplink network, using Network Configuration Utility to configure an interface for VLAN1. Now I can ping to and from the server, but most other sorts of traffic fails - AD logon, DNS, SMB...
Just tried to add a shared uplink set and network for the Windows server, and this works much better.
What can be wrong in the NCU configuration?
Ole Thomsen
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2008 09:09 AM
01-02-2008 09:09 AM
Re: Virtual Connect, only sparse connectivity to server with NCU generated VLAN
make sure you are using NCU 8.80 at minimum as there are some VLAN fixes in 8.80.
Also, check for the NICs running TCP Offload Engine as there are some potential issues with that parameter. try disabling TCP Offload Engine and see if it resolves the issue.
Also, check for the NICs running TCP Offload Engine as there are some potential issues with that parameter. try disabling TCP Offload Engine and see if it resolves the issue.
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