Intel Ethernet Cmdlets for Microsoft Windows* for PowerShell* and Intel® Ethernet Network Adapter E810 Series

19814
8/9/2022

Introduction

Ethernet cmdlets for Microsoft* Windows* for PowerShell*

Available Downloads

  • Microsoft Windows*
  • Size: 242.4 KB
  • SHA1: C7882ABC0506726F56D64646068BBB40889FA41D

Detailed Description

Overview

This download contains Ethernet cmdlets for Microsoft* Windows* for PowerShell*, which allow you to get information, configure settings, or debug issues on supported Intel® Ethernet devices. Not all hardware and operating systems support all cmdlets.

- Ethernet cmdlets are supported on Intel® Ethernet 700 Series and newer devices. 

- Firmware logging is supported only on Intel® Ethernet 800 Series devices.

 

Firmware Logging

----------------

In Windows, you use PowerShell and Ethernet driver cmdlets to set the configuration for firmware logs and generate the logs.

Firmware logs are generated in a binary format and have to be decoded by Customer Support. Information collected is related only to firmware and hardware for debug purposes.

 

Prerequisites

=============

You must have the latest base driver and NVM installed.

 

Installation

============

For most Intel Ethernet devices:

1. Download the zip file with the Ethernet driver cmdlets from the Intel Download Center.

2. Save the zip file to the system you are trying to debug. 

3. Extract files from the zip file.

4. In the extracted files, double-click on Ethernet_Cmdlets.exe.

The cmdlets will automatically install to the current user's PowerShell module directory (for example, to C:\Users\Administrator\Documents\WindowsPowerShell\Modules\IntelEthernetCmdlets).

After installation, you can use the cmdlets without manually importing the module.

 

For more information please see the included readme.txt or download the Intel® Ethernet Adapter User Guide and the readme.txt

Product and Performance Information

1

Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.