- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- Cisco UCS vNIC Adapter Policy
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
02-17-2014 12:22 PM
02-17-2014 12:22 PM
I've been setting up Server 2008 R2 bare metal installs using one vNIC for LAN traffic and two vNICs for iSCSI traffic (on separate VLANs), all there Ethernet adapters use the Cisco default "Windows" Eth Adapter Policy. Should I be creating a separate iSCSI one with different Transmit and Receive Queues? Or is the default Windows one acceptable?
Same question for VMware vSphere 5.1/5.5 and the vNICs that act as the uplinks for the iSCSI traffic, is the default VMware policy acceptable?
Thank you.
Jacob
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-20-2014 12:11 AM
02-20-2014 12:11 AM
Re: Cisco UCS vNIC Adapter Policy
Good question. I have used Windows policy for all my Windows vNIC (regular and iSCSI). Same on ESXi. Like to know if this could be improved by tuning the adapter policies for iSCSI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-16-2014 04:45 AM
04-16-2014 04:45 AM
Re: Cisco UCS vNIC Adapter Policy
Hi Jacob/Sammy
The default OS/default adapter looks to be the correct one for UCS. I have asked Nimble Support to investigate further and confirm - they will post a reply back here shortly.
Jason
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-22-2014 06:26 AM
04-22-2014 06:26 AM
SolutionHi Jacob/Sammy
Quick update: I contacted Nimble Support and they have confirmed that using the Windows adapter is best for Windows, and VMware for ESX. Nimble Support have also checked this with Cisco.
They added the following link from Cisco:
Operating System Specific Adapter Policies
By default, Cisco UCS provides a set of Ethernet adapter policies and Fibre Channel adapter policies. These policies include the recommended settings for each supported server operating system. Operating systems are sensitive to the settings in these policies. Storage vendors typically require non-default adapter settings. You can find the details of these required settings on the support list provided by those vendors.
Important:
We recommend that you use the values in these policies for the applicable operating system. Do not modify any of the values in the default policies unless directed to do so by Cisco Technical Support.
Jason
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP