- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Folks,
I need to upgrade my card to X722.
[root@esxi11:~] lspci | grep 722
0000:06:00.0 Ethernet controller: Intel(R) Ethernet Connection X722 for 10GbE SFP+
0000:06:00.1 Ethernet controller: Intel(R) Ethernet Connection X722 for 10GbE SFP+
The latest 700Series indicate it should contain a x722 bin file but it doesn't not.
All images for 710
ls -l | grep 710 | wc
107
ls -l | grep 722 | wc
0 0 0
I found a download that indicates BP ( zero explanation)
X722_NVMUpdate_v4.10_EFIx64
Image
X722_BNP_SFI_2x10G_P01_NCSI_4p10_80001A76.bin
CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.14.0
;Update
;For verification of NUP
;BNP SFP+
BEGIN DEVICE
DEVICENAME: X722
VENDOR: 8086
DEVICE: 37D0
NVM IMAGE: X722_BNP_SFI_2x10G_P01_NCSI_4p10_80001A76.bin
SKIP OROM: FALSE
EEPROM MAP: OCP_Configuration.txt
EEPID: 80001A76
REPLACES: 80000ACE 80000D07 80000D2F 80001573
RESET TYPE: REBOOT
END DEVICE
I copy nvmupdaten64e ( it for ESXi tool to a same dir) where the image is.
it detects x522 adapter but it doesn't detect x722
Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Connection 1.19(1.13) 15AD 00:003 Update not
X552/X557-AT 10GBASE-T available
Tool execution completed with the following status: Device not found.
Press any key to exit.
I also found this WFP_v4.10_X722_NVMUpdate_EFIx64 but no explanation as well.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafa,
Thank you for posting in our Intel® Ethernet Communities Page.
We are sorry to hear about the issue that you are experiencing with your network adapter.
So we would have a better understanding of your issue, please provide the following information:
1. Usually the error that you encounter happens if you update the firmware of a non-authentic Intel retail card. It could be an OEM card which is the reason why you are getting the error. To check this, please provide us pictures of the front, back, and all of the stickers on the actual unit.
2. Kindly provide us the results of this command: ethtool -i ethx where ethx is the Ethernet port.
3. The software only runs on Windows and Linux, so you may need to via the EFI shell.
We look forward to hearing from you. If we do not get your reply, we will follow up after 3 business days.
Best Regards,
Alfred S
Intel® Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Folks,
I validate this card with Intel back in Aug and send the Logo and provide a picture, all card original intel.
I can't run that command in ESXi since it doesn't detect the adapter at all. Please check the output I posted.
As I pointed out both Linux and Window see adapter, Both Update utils see adapter and
I update to the latest firmware.
ESXi latest tool doesn't see an adapter.
UEFI BIOS same.
Linux ( Please check careful everything is here)
06:00.1 Ethernet controller: Intel Corporation Ethernet Connection X722 for 10GbE SFP+ (rev 04)
Subsystem: Intel Corporation Ethernet Network Adapter X722-2
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 19
NUMA node: 0
Region 0: Memory at 92000000 (64-bit, prefetchable) [size=16M]
Region 3: Memory at 93808000 (64-bit, prefetchable) [size=32K]
Expansion ROM at fb280000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] MSI-X: Enable+ Count=129 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00001000
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 256 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range AB, TimeoutDis+, NROPrPrP-, LTR-
10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS-, TPHComp-, ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
AtomicOpsCtl: ReqEn-
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [e0] Vital Product Data
Product Name: Example VPD
Read-only fields:
[V0] Vendor specific:
[RV] Reserved: checksum good, 0 byte(s) reserved
End
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt+ UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [140 v1] Device Serial Number 0c-ca-79-ff-ff-1e-f2-f8
Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)
ARICap: MFVC- ACS-, Next Function: 0
ARICtl: MFVC- ACS-, Function Group: 0
Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)
IOVCap: Migration-, Interrupt Message Number: 000
IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy-
IOVSta: Migration-
Initial VFs: 64, Total VFs: 64, Number of VFs: 0, Function Dependency Link: 01
VF offset: 79, stride: 1, Device ID: 37cd
Supported Page Size: 00000553, System Page Size: 00000001
Region 0: Memory at 0000000093000000 (64-bit, prefetchable)
Region 3: Memory at 0000000093910000 (64-bit, prefetchable)
VF Migration: offset: 00000000, BIR: 0
Capabilities: [1a0 v1] Transaction Processing Hints
Device specific mode supported
No steering table available
Capabilities: [1b0 v1] Access Control Services
ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
Kernel driver in use: i40e
Kernel modules: i40e
Test
Intel(R) NVM Integrity Verification Tool
Nvmcheck version 1.35.42.07
QV SDK version 2.35.42.01
Copyright(C) 2012 - 2020 Intel Corporation.
NVM module: Option ROM.
NVM Integrity verification PASSED.
NVM module: PE image.
NVM Integrity verification PASSED.
NVM module: PHY PLL 0 Configuration.
NVM Integrity verification PASSED.
NVM module: PHY 0 Configuration.
NVM Integrity verification PASSED.
NVM module: PHY PLL 1 Configuration.
NVM Integrity verification PASSED.
NVM module: PHY 1 Configuration.
NVM Integrity verification PASSED.
NVM module: EMP image.
NVM Integrity verification PASSED
root@ubuntu:/cdrom/intel/25_4/APPS/NVMCHECK/Linux_x64# ./nvmcheck64e /HEADER /NIC=3
Intel(R) NVM Integrity Verification Tool
Nvmcheck version 1.35.42.07
QV SDK version 2.35.42.01
Copyright(C) 2012 - 2020 Intel Corporation.
NVM module: Option ROM.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x0004E000
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000000
-reserved 0x00000000
-lad_fw_entry_offset 0x0000014C
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000005 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
NVM module: PE image.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x0004E000
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000000
-reserved 0x00000000
-lad_fw_entry_offset 0x0000014C
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000002 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
NVM module: PHY PLL 0 Configuration.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x00000800
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000000
-reserved 0x00000000
-lad_fw_entry_offset 0x0000014C
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000006 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
NVM module: PHY 0 Configuration.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x00000800
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000000
-reserved 0x00000000
-lad_fw_entry_offset 0x0000014C
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
NVM module: PHY PLL 1 Configuration.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x00000800
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000000
-reserved 0x00000000
-lad_fw_entry_offset 0x0000014C
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000008 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
NVM module: PHY 1 Configuration.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x00000800
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000000
-reserved 0x00000000
-lad_fw_entry_offset 0x0000014C
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
NVM module: EMP image.
CSS Header:
-moduleType 0x00000006
-headerLen 0x000000A1
-headerVersion 0x00010000
-moduleID 0x00000000
-moduleVendor 0x00008086
-date 0x20130530
-size 0x0004E000
-keySize 0x00000040
-modulusSize 0x00000040
-exponentSize 0x00000001
-lad_srev 0x00000010
-reserved 0x00000000
-lad_fw_entry_offset 0x00133000
-lad_fl_dev_offset 0x00000000
-reserved:
0x00000000 0x00000001 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
[00:006:00:01]: Intel(R) Ethernet Network Adapter X722-2
Vendor : 8086
Device : 37D0
Subvendor : 8086
Subdevice : 0002
Revision : 4
LAN MAC : F8F21E79CA0D
Alt MAC : 000000000000
SAN MAC : FFFFFFFFFFFF
ETrackId : 8000265A
SerialNumber : 0CCA79FFFF1EF2F8
NVM Version : 5.16(5.10)
PBA : K20564-001
VPD status : Valid
VPD size : 25
NVM update : No config file entry
checksum : Valid
OROM update : No config file entry
CIVD : 1.2829.0
PXE : 1.1.18, checksum Not Relevant
ISCSI : 3.1.63, checksum Not Relevant
EFI : 4.4.12, checksum None
SMCLP : 3.1.21, checksum Valid
--------
VMware
Latest Native driver loaded
--- 1.10.9.0
Version: 1.10.9.0-1OEM.700.1.0.15525992
Build Type: release
License: Intel
Required name-spaces:
com.vmware.vmkapi#v2_6_0_0
Parameters:
EEE: array of int
Energy Efficient Ethernet feature (EEE): 0 = disable, 1 = enable, (default = 1)
MaxRdmaInts: int
Maximum RDMA Interrupts (default = 16)
RDMA: array of int
Enable RDMA support 0 = disable, 1 = enable, (default = 0)
LLDP: array of int
Link Layer Discovery Protocol (LLDP) agent: 0 = disable, 1 = enable, (default = 1)
TxITR: int
Default TX interrupt interval (0..0xFFF), in microseconds, (default = 100)
RxITR: int
Default RX interrupt interval (0..0xFFF), in microseconds (default = 50)
trust_all_vfs: array of int
Always set all VFs to trusted mode 0 = disable (default), other = enable
max_vfs: array of int
Maximum number of VFs to be enabled (0..128)
DRSS: array of int
Enable/disable the DefQueue RSS(default = 0 )
RSS: array of int
Enable/disable the NetQueue RSS( default = 1 )
VMDQ: array of int
Number of Virtual Machine Device Queues: 0/1 = disable, 2-16 enable (default =8)
The adapter does not detect so I can't even run eth tool nor any tools.
I only see a PCI devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafa,
Thank you providing those information.
Please allow us some time to check on this.
We will get back to you no later than 3 business days from now.
Best Regards,
Alfred S
Intel® Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafa,
Thank you for waiting for our update.
We are already beginning the preliminary checks on your issue, and we came up with these questions to help us with our investigation:
1. May we know the version of the VMWare ESXI software that you are using
2. Does the systems where these cards are integrated to all have an the same EFI version? You can see the version the moment you boot to the EFI shell?
We look forward to your reply. Should we not get your reply, we will follow up after three business days.
Best Regards,
Alfred S
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you please check the logs ?
All your questions in that log in the same thread.
You asked me for a picture I send you a picture and it has clearly seen in that pic it an Intel PCI card.
Please focus a bit.
Issue number one. ( Driver issue )
Again please check the Cross-check log.
For vSphere 7.0 Update 1 I test the latest driver posted in Oct 2020.
Version ESXi. 6.5 latest update doesn't detect the card. (used latest driver for i40en)
Version ESXI 6.7 latest update doesn't detect card. (used latest driver for i40en)
Version ESXi 7.0 latest update doesn't t detect the card. (used latest driver for i40en)
Issue two (NVupdate tool)
UEFI - doesn't detect the card. ( must be fixed)
ESXi - doesn't detect the card. ( must be fixed)
Linux - DOES detect card and firmware updated.
Win - DOES detect card and firmware updated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafab,
Thank you for providing that information.
We are humbly sorry if you felt that we are not checking the logs. We asked that question to confirm. Rest assured, we will closely look at your case and treat it with priority.
We will continue checking this and the information that provided is invaluable to us.
Please allow us some time to check on this. We hope for your understanding regarding this
We will get back to you no later than 3 business days from now.
Best Regards,
Alfred S
Intel® Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafab,
Thank you for waiting for our update.
We have already begun the initial stages of the investigation and our team would like to get specifics on some of the information that you have provided. Please answer the following questions:
1. May we know what specific driver version did you use for each ESXI version that you have tested?
2. Did you download the drivers from this page, https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=48643&vcl=true?
3. Did you get any errors when installing the driver?
4. We noticed that your account name on your profile shows VMWare. In line with this, is the card for business use or for personal use?
5. May we know how many cards are affected?
6. Kindly provide the PBA number of the Intel® Ethernet Network Adapter X722-DA2.
We look forward to your reply. Should we not get your reply, we will follow up after three business days.
7. What is the specific error that you are getting when you run the NVME tool?
We look forward to your reply. Should we not get your reply, we will follow up after three business days.
Best Regards,
Alfred S
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafab,
We are just following up.
It looks like you need more time to provide the information that we asked.
We will follow up again after 3 business days. Should we not hear from you, our system may automatically close the thread.
Best Regards,
Alfred S
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mustafab,
We need to close this thread since we have not gotten a response from you: maybe because you are busy or preoccupied at the moment. We know that this is important for you to get it resolved and it is also equally important for us to give you the right solution; as much as we would like to assist you, we need to close it to attend to other customers. We hope for your consideration and understanding on this one.
If you need any additional information, please submit a new question as this thread will no longer being monitored.
Thank you for contacting Intel® and have a great week!
Best Regards,
Alfred S
Intel® Customer Support
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page