   Special Notes for Management Adapters


Management Adapter Feature Notes
================================

Note: the information in this file applies to management adapters 
only. Standard, non-management adapters do not have a 3-pin auxiliary 
power connector.

1. Wake on LAN*
     Description
     Computer Requirements
     Settings in Windows* 98
     Settings in the computer's BIOS
     Troubleshooting Wake on LAN

2. Boot Agent
     Description
     Operation
     Troubleshooting Boot Agent


Wake on LAN
===========

Description

The Wake on LAN (WOL) feature of the management adapter allows 
a WOL-enabled computer to be powered-on remotely by a network 
management program. In some operating systems, it can also wake the 
computer from suspend mode. This is accomplished by sending a special 
type of data packet containing the adapter's specific Ethernet address.

Some management adapters are supplied with a small cable with a
3-pin connector at each end. Some WOL-enabled computers require
this cable for the WOL function. In these computers, one end of 
the cable is attached to the adapter and the other end is attached to 
the 3-pin WOL connector on the WOL-enabled computer. When the computer
is powered off, the adapter continues to operate by using +5 volt
standby power through the 3-pin cable in the computer.

In WOL-enabled computers that do not require the 3-pin cable, the 
adapter operates from 3.3 volt standby power supplied through the PCI
bus.  When the computer is powered off, the adapter continues to operate
by using 3.3 volt standby power through the PCI bus.

As long as AC power is available to the power supply, the adapter will 
draw standby power when the machine is powered off, allowing it to 
"listen" to the network for a wake up packet.

NOTE: Early versions of the Management adapter are +5 volt only. These
models must have the 3-pin cable attached for the WOL function to work.
These adapters can be identified by the fact that they are equipped with
3 LEDs on the adapter bracket, whereas the PCI 2.2 compliant models have
2 LEDs on the adapter bracket.  These older, +5 volt model adapters are
not compliant to the PCI 2.2 specification and will not fit in a 3-volt
only PCI slot due to the slot being keyed differently.

Computer requirements
---------------------

Only a computer designed for Wake on LAN can use the Wake on LAN
function. If your computer uses a 3-pin connector for Wake on LAN, make
sure the connector matches the 3-pin cable that may have been supplied
with the management adapter. If the computer has a Wake on LAN connector
that does not fit the 3-pin cable, do not attempt to use it with this
adapter. An exception to this rule is some early IBM WOL-enabled
computers that use a 2 pin header. These computers can be used with the
Management adapter by utilizing a 2 to 3 pin adapter, available at extra
charge from Intel.

If your computer requires the 3-pin cable, then the +5 volt standby power 
supply must be capable of supplying at least 0.2 amps at +5 volts for each
management adapter installed (.6 amps for each of the older PCI 2.1
compliant management adapters). This value is usually listed on the power
supply label as +5SB, +5VSB or +5AUX.

If your WOL-enabled computer is compliant to PCI specification 2.2,
then it does not require the 3-pin cable for Wake on LAN. In these 
computers, the 3.3 volt standby supply must be capable of supplying at
least 0.2 amps for each management adapter installed. You may
need to contact your computer manufacturer to verify the standby current
rating.

WOL Settings in Microsoft Windows* 98
-------------------------------------

If the management adapter is installed in an original retail version of
Microsoft Windows 98, you will have an additional setting in the adapter
properties that is not available for other types of adapters. This setting
is titled "ACPI Wake On LAN" and by default is set to "Enabled". This option
enables or disables the Magic Packet* service for Wake On LAN when used
in Microsoft Windows 98 version 4.10.1998 without the Service Pack.
If you are using a later version of Windows 98, or have Service Pack 1
or later installed, this option will be ignored and you will be using
the ACPI Wake On LAN services.


Settings in the computer's BIOS
-------------------------------

Many Wake on LAN enabled computers have settings similar to the
following:

On Modem Ring       Stay Off
On LAN              Power-on
On PME              Stay Off

The setting "On LAN" refers to wake-up events received through the 3-pin 
WOL connector. The setting "On PME" refers to wake-up events received 
through a signal on the PCI bus defined as "Power Management Event". 
Management adapters are capable of using either of these methods. 
Which settings to use will vary with the computer and operating system. 
The following are suggestions only.

A. In computers running Windows 98, set the "On LAN" BIOS setting to
"Stay off" and the "On PME" BIOS setting to "Power-on". In other
operating systems set the BIOS setting "On LAN" to "Power-on" and the
BIOS setting "On PME" to "Stay Off".

B. If these settings do not work for you, try reversing them, or set 
   both to "Power-on".

Troubleshooting Wake on LAN
---------------------------

Note: The reception of a wake up packet will set the adapter to a 
special state. This condition must be reset before the adapter will 
accept another wake up packet and power-on the computer. The drivers for 
this adapter are written to reset this condition when they load. The 
only other way of resetting this condition is removing AC power from the 
computer for a short duration (~10 seconds). Once you have sent the 
computer a wake up packet and powered-on the computer, you must let a 
driver load or it will no longer accept any wake up packets. If this 
happens, you can remove the AC power cord for 10-15 seconds or load an 
adapter driver to reset the adapter and restore normal operation.

If the computer will not power-on when a wake up packet is sent, check 
the computer's BIOS for power settings (see "Settings in the computer's 
BIOS" above). 

If you are connected to a hub or switch, the link LED on the back of the 
adapter should be on, even though computer power is off.  If the link 
LED it is not on, try powering the computer on. If the LED now lights, 
then the adapter is not receiving power in standby mode. If this is the 
case, check to make sure the 3 pin cable is properly plugged into a 
standard WOL 3 pin connector on systems that require it. Make sure that 
the power supply is capable of supplying the necessary current (see 
Computer Requirements above). Also, check with your computer vendor to be
sure that the computer is, in fact, capable of supporting Wake on LAN.

If the link LED does not come on when the computer is powered-on, you 
have not established link with your hub or switch. Check your cabling or 
substitute it with a cable that has been verified to work correctly.
Make sure your hub or switch is either 10baseT or 100baseTX and is
powered-on and fully functional.

If your computer will not power-on at all when the 3-pin cable is 
attached, but will power-on when the 3-pin cable is removed, your +5 
volt standby power supply is possibly insufficient. In systems that do 
not require the 3-pin cable, this symptom may be caused by an insufficient
3.3 volt standby power supply, especially if you are using multiple
management adapters (see Computer Requirements above). 

If everything listed above is correct and the computer will still not 
respond to a wake up packet, check with your computer vendor for an 
updated BIOS.

Boot Agent
==========

Description

The Boot Agent is a utility program that is stored in a flash memory
chip on the adapter, allowing the adapter to remotely boot the system
from the network using either of 2 methods. The default method is PXE, a
remote boot procedure defined by the "Wired for Management"
specifications and used by powerful network management programs, such as
Intel(R) LANDesk(R) Management suite. The alternate method is RPL, an
established industry standard historically utilized for remote booting
of diskless workstations from network operating systems such as NetWare*
and Windows NT* Server. 

Computers do not need to be Wake on LAN enabled to use this feature, and
the feature will work with or without the 3-pin auxiliary power
connector attached.

Configuration

When the computer is first powered-on, the Boot Agent will execute and
display a message similar to the following, with the current version number:

Initializing Boot Agent Version X.X
Press Ctrl+S to enter the Setup Program..

By default, this message will display for 2 seconds, then attempt to
boot from a local drive. If the attempt to boot from a local drive
fails, the agent will attempt to boot remotely. 

To change the configuration of the Boot Agent, press the "Ctrl" key and
"S" key simultaneously during the time that this message is displayed.
This will bring up the Boot Agent configuration screen.

There are 7 configurable parameters. Follow the on-screen instructions
to select, change and save the different parameters. The different
parameters are explained below, with the default parameter listed first.

Boot Protocol
Selections are PXE and RPL. Select PXE for use with Wired for Management
compliant network management programs, such as Intel LANDesk Management
Suite. Select RPL for legacy style remote booting.

PnP/BEV Boot
Selections are Disable and Enable. Select Disable to use the
Boot Agent for remote boot operation. Select Enable if your
computer BIOS has a BEV (Boot Entry Vector) capable remote boot program
built in and you wish to use that remote boot agent instead of the Intel
Boot Agent.

Default Boot
Selections are Local and Network. If Local is selected, the Boot Agent
will attempt to boot from a local drive first, then attempt to boot from
the network if local boot fails. If Network is selected, the Boot Agent
will attempt to boot from the network first.

Local Boot
Selections are Enable and Disable. If Enable is selected, the system
will be able to boot from a local drive (floppy drive or hard drive). If
disable is selected, the system will not be able to boot from a local
drive. This will be true regardless of the Default Boot setting.

Prompt Time
Selections are 2, 3, 5 and 8. The number represents the amount of time
in seconds the "Initializing Boot Agent Version 2.2 - Press Ctrl+S to
enter the Setup Program.." message is displayed every time the system is
booted.

Setup Message
Selections are Disable and Enable. If enabled, the message "Initializing
Boot Agent Version 2.2 - Press Ctrl+S to enter the Setup Program.." will
be displayed during boot up. If Disable is selected, only the message
"Initializing Boot Agent Version 2.2" will appear. However, you will still
be able to enter Ctrl+S to enter the setup program at that time.

Power Management
The selections are ACPI and APM. ACPI should work in most computers.

The APM selection will pre-enable the Wake-on-LAN function of the adapter.
Set this selection to APM if one of the following apply;

  1. You are having difficulty with remote wake up in computers that are
     compliant to the PCI 2.2 specification, you are not using the 3-pin
     header cable and are running an OS that is not ACPI (Advanced Control
     and Power Interface) aware.

  2. You are running an ACPI aware OS (such as Windows 98) on a none-ACPI
     computer and the link light goes out when you shut down the system,
     disabling Wake-on-LAN.


Troubleshooting Boot Agent
==========================

If you do not see a message similar to " Initializing Boot Agent Version
X.X" during the computer start-up, check the following:

In the computer setup, check for the boot device sequence. If "Intel 
UNDI, PXE" or "Network" is listed, move it ahead of the hard drive 
in the boot sequence.

Some computers require manual intervention to execute the Boot Agent. These
computers will normally display an informational note on the computer monitor
after power-on instructing you on how to execute a network boot. For example,
some computers will display the message "F12 Network Service Boot" on the
banner screen. In this example, you would press the F12 key to execute the
boot agent.

When using an RPL remote boot in computers that have a built-in network 
interface based on an Intel 82557, 82558 or 82559 LAN controller chip,
the boot agent may try to remote boot using the built-in interface 
instead of the management adapter. To avoid this, disable the
built-in interface in the computer BIOS settings.

See the Boot Agent User's Guide included on this CD (in the \BootAgent 
folder) for more complete instructions on using the Boot Agent.




* Other trademarks and brand names are the property of their owners.
