Posted at December 25, 2024 by PCI-DB Team
Install Driver AutomaticallyDevice Name | Mellanox MCX454A-FCAT VPI Card Firmware 12.21.2010 |
---|---|
Category | Network Card |
Manufacturer | Mellanox |
File Size | 1.5 MB |
Supported OS | OS Independent |
- Query vPort Environments (Debug Counters): Debug counters are a group of counters that handle traffic performance issue related to firmware overhead in transport flow. The following are the additional counters added to this firmware version: current_q_under_processor_handle, total_q_under_processor_handle, qp_priority_update_flow
- Occasionally, when adding module info page for Bell 1G BaseT module to the mlxlink data, the information is not updated correctly.
Bug Fixes:
- Fixed an issue that caused QP connection timeout due to firmware not being able to handle duplicate packets with AckReq bit set. The fix stopped ignoring duplicate AckReq packets to avoid timeout on the sender side.
- MPFS load balance (DUP_MAC_ACTION==LOAD_BALANCE(1)) is not working as long as IB_ROUTING_MODE/SRIOV_IB_ROUTING_MODE is configured to LID.
- Fixed an issue that caused a SX engine deadlock (the SX engine handles software port/priority changes for a specific Send Queue) when more than a single SX engine handled the "prio diff" flow simultaneously, thus caused the hardware to get stuck. The issue happened as the firmware releases the SX engine and waits for various operation to complete. However, due to a race that allows a different transaction to get into the SX engine and cause the lock to be taken by it, the SX engine release is prevented.
- Fixed an issue that caused the system to hang while changing QPTS/QPDPM/ QPDP parameters during traffic.
- Fixed unfairness between senders in RoCE LAG while ECN is configured.
- Fixed an issue which displayed diagnostic counters only on the adapter that was initialized first, which is the counters’ owner. The owner received correct values, while the other adapter only received zeros.
- Fixed an issue that caused the rdma_cm traffic to fail on the 2nd port when more than 32 VFs were configured, when the RoCE Dual Port vHCA (a.k.a Multi-Port vHCA: MPV) feature was enabled.
- Service types not supported: SyncUMR, Mellanox transport, PTP, RAW IPv6, PTP (IEEE 1588)
- INT-A not supported for EQs only MSI-X
- PCI VPD write flow (RO flow supported)
- Streaming Receive Queue (STRQ) and collapsed CQ
- Precise clock synchronization over the network (IEEE 1588)
- SM is not supported on VFs
- DC is not supported in: Multi-Host, SR-IOV, and Ethernet (RoCE)
- RoCE LAG for VFs and Multi-Host/Socket-Direct are not supported in RoCE LAG
- QoS per VFs feature is supported up to 14 VFs per PF in dual port device with 8 VLs.
- Mutlihost Ethernet
- QUERY_MAD_DEMUX
- SET_MAD_DEMUX
- PAGE_FAULT_RESUME
- ACTIVATE_TRACER
- DEACTIVATE_TRACER
- ACCESS_REG_SPACE
- ACCESS_REG_SPACE_DWORD
- ACTIVATE/DEACTIVATE_TRACER
- QUERY/MODIFY_SCHED_QUEUE
- CREATE_RQ - MEMORY_RQ_RMP
- MODIFY_LAG_ASYNC_EVENT
- PXE Boot: Added ESC option as an abort key during PXE boot process.
- FlexBoot Link Aggregation Control Protocol (LACP): Enabled/disabled FlexBoot LACP support by editing the INI configuration.
- Serial Console: Removed Serial Console support in the ConnectX-4 adapter card.
- Upstream sync: Synced the source with iPXE (upstream sync)
- Pressing any of the arrow keys during boot might cause the boot process to be aborted
- Chain-loading "ipxe.pxe" and "undionly.kpxe" over InfiniBand is currently not supported when using DHCP client identification based on InfiniBand 32-bit Prefix+GUID (as with FlexBoot).
- Fixed an issue that prevented the first iSCSI target parameters to be reset to their default values.
When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.
However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.
Updating the adapter's drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.
To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don't forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.
Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don't miss a single new release.
It is highly recommended to always use the most recent driver version available.
Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.
Device Type: Network Card File Size: 42.2 MB Windows 2008
Install DriverDevice Type: Network Card File Size: 42.2 MB Windows Server 2012
Install DriverDevice Type: Network Card File Size: 42.2 MB Windows Server 2012
Install DriverDevice Type: Network Card File Size: 42.3 MB Windows 8.1 ,Windows 8.1 64 bit
Install DriverDevice Type: Network Card File Size: 42.1 MB
Install DriverDevice Type: Network Card File Size: 42.1 MB
Install DriverDevice Type: Network Card File Size: 42.3 MB Windows Server 2012
Install DriverDevice Type: Network Card File Size: 42.2 MB Windows 2008
Install DriverDevice Type: Network Card File Size: 42.2 MB Windows 7 ,Windows 7 64 bit
Install DriverDevice Type: Network Card File Size: 42.3 MB Windows Server 2012
Install DriverFind Missing Drivers
Recent Devices
Recent Drivers
© 2024 PCI-DB.com - PCI Database Replacement. All rights reserved.