- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all,
We have newly installed Intel X710 NICs on Windows Server 2012 R2 connecting to a Juniper EX4500 with DCBX enabled. The Juniper DCBX information for the interfaces show enabled and everything looks good. The data center tab on the X710 shows the following:
Status: Non Operational
DCBx Version: IEEE 802.1Qaz
Priority Group: Operational
Priority Flow Control: Operational
iSCSI Status: Feature not present in peer TLV
Our other NICs we have are X520 and they show DCBX to be operational. All interface settings on the Juniper are identical.
To my knowledge the X710 devices have the latest drivers installed.
Has anyone seen something like this before or have any ideas?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've read a few links that stated LLDP was turned off somehow on the X710 cards. It states how to turn it back on for Linux systems but I don't see anything regarding Windows. I've pretty much run out of ideas on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Knightmese,
Thank you for posting your issue in Wired Ethernet Community.
Please help to run System support utility to capture details of your X710 adapter, kindly attach the log in the thread.
Sharing the link on where you can download the utility below.
https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility
regards,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the summary. Let me know if you were expecting more.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is a detailed view of one of the adapters:
AvailabilityRunning or Full PowerCaptionIntel(R) Ethernet Converged Network Adapter X710CoInstallersNicCo36.dll,NicCoInstallerEntryDefault IP GatewayNot AvailableDHCP EnabledNoDHCP Lease ExpiresNot AvailableDHCP Lease ObtainedNot AvailableDHCP ServerNot AvailableDriveri40ea64.sysDriver Date05/27/2016 12:00 AMDriver PathC:\Windows\system32\DRIVERS\i40ea64.sysDriver ProviderIntelDriver Version1.3.115.0ETrackID0x800024C6Index0017INFoem2.infINF SectionF1572Install DateNot AvailableInstalledYesIP AddressNot AvailableIP SubnetNot AvailableLast Error CodeNot AvailableLast Error Code DescriptionNot AvailableLast Reset10/05/2016 03:51 PMLocationPCI bus 3, device 0, function 1MAC Address3C:FD:FE:9C:E0:89ManufacturerIntelNet Connection IDphy 0 iscsi SC1 swb domain 1NetCfgInstanceId{39929CAC-5BF3-4478-9CB4-380D5EF95960}Number of VLANs1NVM Version5.4Part NumberH58362-003PNP Device IDPCI\VEN_8086&DEV_1572&SUBSYS_00008086&REV_01\4&38520966&0&0108Port1Power Management CapabilitiesNot AvailablePower Management SupportedNoProduct TypeIntel(R) Ethernet Converged Network Adapter X710Service Namei40eaStatusLink UpTeam NameNot in a teamTypeEthernet 802.3*EncapsulatedPacketTaskOffloadEncapsulated Task OffloadDisabled (0)*FlowControlFlow ControlRx & Tx Enabled (3)*InterruptModerationInterrupt ModerationEnabled (1)*IPChecksumOffloadIPv4IPv4 Checksum OffloadDisabled (0)*JumboPacketJumbo Packet9014 Bytes (9014)*LsoV2IPv4Large Send Offload V2 (IPv4)Disabled (0)*LsoV2IPv6Large Send Offload V2 (IPv6)Disabled (0)*MaxRssProcessorsMaximum Number of RSS Processors8 (8)*NumaNodeIdPreferred NUMA nodeSystem Default (65535)*NumRssQueuesMaximum Number of RSS Queues1 Queue (1)*PriorityVLANTagPacket Priority & VLANPacket Priority & VLAN Enabled (3)*QOSNDIS QOSEnabled (1)*ReceiveBuffersReceive Buffers1024 (1024)*RscIPv4Recv Segment Coalescing (IPv4)Enabled (1)*RscIPv6Recv Segment Coalescing (IPv6)Disabled (0)*RSSReceive Side ScalingEnabled (1)*RssBaseProcNumberRSS Base Processor Number0 (0)*RSSProfileRSS load balancing profileNUMAScaling (3)*SpeedDuplexSpeed & DuplexAuto Negotiation (0)*SRIOVSR-IOVDisabled (0)*TCPChecksumOffloadIPv4TCP Checksum Offload (IPv4)Disabled (0)*TCPChecksumOffloadIPv6TCP Checksum Offload (IPv6)Disabled (0)*TransmitBuffersTransmit Buffers1024 (1024)*UDPChecksumOffloadIPv4UDP Checksum Offload (IPv4)Disabled (0)*UDPChecksumOffloadIPv6UDP Checksum Offload (IPv6)Disabled (0)*VMQVirtual Machine QueuesDisabled (0)*VMQVlanFilteringVMQ VLAN FilteringEnabled (1)<t...- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Knightmese, Thank you for sharing the information, I'm currently checking your issue and will update this thread as soon as possible.
regards,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Knightmese, we'd like to confirm if the X520 were also connected to the same Juniper EX4500. Thanks.
regards,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Knightmese, kindly help to provide the additional information below for us to further investigate the issue.
1. Output of the following commands in your win2k12 system with X710 installed.
get-netqosdcbxsetting
get-netqostrafficclass
get-netqosflowcontrol
get-netqospolicy
get-netadapterqos
2. Logs in Juniper switch showing the DCB status of connected port.
regards,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Knightmese, we'd like to follow-up the requested information. Thanks.
regards,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In a nutshell it was because a native VLAN wasn't set on the Juniper ports connected to the X710 adapters which use different VLANs that only allow tagged traffic. LLDP packets on Juniper devices are untagged so you have to specify a native VLAN to received these packets. If you don't they just get dropped. Once we configured a native VLAN, DCBX came right up.
The X520 adapters didn't have this problem because they did not use tagged VLANs. We were migrating to a new storage system.
Regardless I appreciate the responses, Vince. Thank you. I hope this helps out if anyone else runs into this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Knightmese, Thanks For sharing this, i'll document your scenario and share if same issue encountered by other users.
regards,
Vince
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page