Quality of Service (QoS)

# QoS WMI Provider 1.0 and
Intel® PRO QoS (PRO 10/100 Adapters Only)

- Overview

- System Requirements

- Installation

- Uninstall Procedure

- Usage with Applications

- Supported Standards

- Known Issues

## Overview

The Intel® PRO Quality of Service (QoS) Windows Management Instrumentation (WMI) Provider is a set of software modules that allow WMI-based management applications to manage the QoS capabilities of Intel® PRO network adapters. QoS WMI Provider uses WMI, a kernel-level instrumentation technology for the Microsoft Windows platform.

WMI is the middleware layer that allows measurement and instrumentation information to be collected from kernel mode data providers. This information is then provided to local or remote user-mode data consumers through the use of a common set of interfaces (Web-based Enterprise Management called WBEM). WMI is a data-independent pipeline between the data consumer and the data provider that makes no assumptions about the format of the data.

The QoS WMI Provider lets WMI-aware management applications set up priority filters to process high priority network traffic before normal traffic. By prioritizing traffic at the host or entry point of the network, network devices can base forwarding decisions on priority information defined in the packet.

WMI-aware management applications using QoS WMI Provider functionality can configure priority filters on the target system to do the following:

- Tag packets with priority levels for forwarding behaviors.

- Drop incoming packets that match certain criteria.

- Obtain statistics such as number of packets or number of bytes that were tagged with a particular priority.

## System Requirements

- Any Intel® PRO/100 Adapter and its related driver software.

- Microsoft* WMI Core.

- Windows* NT4 (SP4), Windows 98 (SP1 and later), Windows Millennium, Windows 2000, Windows XP, Windows Server 2003.

- For Adapter Teaming features (AFT and ALB support), the latest NDIS drivers on the Intel® CD or downloaded from http://support.intel.com.

The WMI Core components are part of the operating system. These pieces are required for a WMI-enabled application to work.

The QoS WMI Provider supports all Intel PCI PRO 10/100 adapters except for 82557 based adapters.

The QoS WMI Provider does not support any PRO 1000 adapters.

## Installation

To install QoS WMI Provider, double-click on the setup program found in the "\APPS\WBEM\WMI\QOS" directory on the Intel CD. WMI Core components must be installed before QoS WMI Provider is installed. If QoS WMI Provider does not find the WMI Core component's registry keys, installation fails. If Microsoft WMI Core is not installed, install it and restart the QoS WMI Provider installer.

The most recently released version of Microsoft WMI Core can be downloaded from: http://www.microsoft.com

## Uninstall Procedure

To Uninstall QoS WMI Provider:

- From the Control Panel, double click on the Add/Remove Programs icon.

- On the Install/Uninstall tab, select "Intel® PRO Quality of Service (QoS) WMI Provider (Build 1.0)".

- Click the "Add/Remove..." button.

# Usage with Applications

WMI-based management applications such as WBEM CIM studio and WBEM Object browser in the WMI SDK can be used to access QoS WMI Provider functionality both locally and remotely. This applies to Windows NT 4.0 (SP4 and later), 2000, XP and Windows Server 2003.

On Windows 95, Windows 98 or Windows Millennium operating systems however, you must carefully configure client systems to allow remote access of QoS WMI Provider functionality.

To do this, you will need to edit the Windows 95, Windows 98 or Windows Millennium system registry to remotely access QoS WMI Provider functionality.

| CAUTION: Editing the system's registry incorrectly can cause serious problems that may require you to reinstall your operating system. Be very careful when editing the following registry entries. Back up any important data before beginning this process. Be aware that enabling DCOM applications to connect anonymously to your Windows9x or Millennium system may violate your network's security policies. Consult with your system administrator before making these changes.

- Open regedit (Start-Run-regedit) on the Windows 95, Windows 98 system, and ensure that the following values are set correctly.

  - HKLM\software\microsoft\OLE\EnableDCOM should be set to its default of "Y".

  - HKLM\software\microsoft\OLE\EnableRemoteConnect should be changed to "Y".

  - HKLM\software\microsoft\wbem\cimom\AutostartWin9x should be changed to "2".

  - HKLM\software\microsoft\wbem\cimom\EnableAnonConnections should be changed to "1".

  - Exit the registry editor and restart the Windows 95, Windows 98 or Millennium system.

- Log onto the Windows 95, 98 or Millennium system remotely from Windows NT 4.0, 2000, XP or Windows Server 2003 using WBEM CIM Studio from the WMI SDK.

  - Enter the UNC name of the Windows 95, Windows 98 or Millennium system in the "Machine name" box and click "Connect."

  - In the WBEM CIM Studio login window, choose "Options" to see the full set of login choices.

  - Leave "Login as current user" checked.

  - Leave "impersonation level" set to impersonate.

  - For "authentication level", choose "None." Click OK.

This should allow you to connect to your Windows 95, 98 or Millennium system remotely.

## Supported Standards

The QoS WMI Provider implements the CIM specification that was submitted to DMTF for adoption into CIM 2.4 specification.

## Known Issues

- Under some circumstances, the process winmngt.exe may not start on a Windows 95, 98 or Millennium system. This results in a browsing machine being unable to connect to the Windows machine. The browser (CIM Studio or other) may show an error "the RPC server is unavailable". If pview95.exe shows that winmngt.exe is not executing, double click the file to begin execution. This may be fixed permanently by upgrading to a newer version of the WBEM core.

- All WBEM classes share the same access. There is currently no method to define per-class security. Therefore, it is not possible to restrict access to the QoS provider without restricting access to all WBEM classes. Consult Microsoft's WBEM/WMI documentation for information on setting appropriate security.

- It is possible to create filters that conflict. For example, adding the same filter with two different names will cause one filter to be ignored. Ensure that any filters added will not conflict with existing filters.

`Last modified on 1/23/03 8:38a Revision 6`