********************************************************************************
*                                                                              *
*               INTEL CORPORATION PROPRIETARY INFORMATION                      *
*  This software is supplied under the terms of a license agreement or         *
*  nondisclosure agreement with Intel Corporation and may not be copied        *
*   or disclosed except in accordance with the terms of that agreement.        *
*    Copyright (c) 1999-2007 Intel Corporation. All Rights Reserved.           *
*                                                                              *
********************************************************************************

Intel PRO Alerting Suite, ASF Compliant Software Release Dragon Lake 13.0.1/Alpha Build 02
==================================================================================

SUMMARY
-------

    This document describes the known issues and the change history for this release 
    for the following Intel ASF PRO Alerting Suite components:
    
    - ASF AGENT INSTALL
    - ASF AGENT SERVICE EXECUTABLE
    - ASF AGENT SERVICE DLL
    - ASF AGENT WMI PROVIDER
    - ASF AGENT WMI SAMPLE APPLICATION                                                                                  
    - ASF DRIVERS

Known issues
------------

1. Scenario:   The EEPROM image of an ASF capable adapter was re-burned after ASF agent
   	       was installed and ASF2.0 security keys were set.
   Symptom:    May cause loss of functionality of ASF2.0 commands.
   Workaround: Reenter the existing security keys using the ASF agent user interface.

2. Scenario:   82573 Gigabit Ethernet Controller was configured to send watchdog 
	       expiration event in case boot hang occurs.
   Symptom:    No watchdog expiration event is being sent upon BIOS boot hang.
   Workaround: No workaround available.

3. Scenario:   82573 Gigabit Ethernet Controller was configured to send watchdog
               expiration event in case OS hang occurs.
               System was shut down via an RMCP command sent to the 
               82573 Gigabit Ethernet Controller.
   Symptom:    An OS-hung Watchdog will be sent. 
   Workaround: No workaround available.


4. Issue:      ASF Agent does not support more than one IP per ASF-capable adapter.
   Symptom:    When using ASF-capable adapter with multiple IP addresses, only the first 
	       IP address will be used by the ASF Agent in order to connect to the 
	       Management Console. If the first IP address is not on the same subnet as
	       the Management Console, a message “Management console cannot be reached” 
	       will appear and ASF Agent will enter Safe Mode.
   Workaround: No workaround available. Make sure that the first IP address of the ASF 
	       capable adapter is on the same subnet with the Management Console.



Limitations
-----------



1. Issue:      ASF and teaming do not work at the same time.
   Symptom:    One cannot configure teaming on a set of adapters when ASF is enabled on one of them. 
               There is one exception to this rule – if the team consists of the two ports of an 
               82571EB adapter, a team can be created even if ASF is enabled on one of the ports.


2. Scenario:   Using direct packets to wake up systems through a 10/100 NIC when ASF is enabled.
   Symptom:    You cannot wake up a machine using an 10/100 NIC with a direct packet while ASF is 
               enabled. This is intentional, so the machine won't wake from the ASF's MC pings.
   Workaround: Wake up the machine remotely using ASF remote control capabilities.






