Dell Broadcom NetXtreme Family of Adapters Manual
Wake-on-lan (wol) support on dell servers
Hide thumbs
Also See for Broadcom NetXtreme Family of Adapters:
- Installation manual (58 pages) ,
- User manual (178 pages) ,
- User manual (224 pages)
Related Manuals for Dell Broadcom NetXtreme Family of Adapters
Summary of Contents for Dell Broadcom NetXtreme Family of Adapters
- Page 1 Wake-on-LAN (WOL) Support on Dell™ Servers Dell White Paper By Ken Bignell ken_bignell@dell.com October 2007...
-
Page 2: Table Of Contents
Tools ..............................3 Dell Servers that Support Wake‐on‐LAN ..............3 Supported NICs (Network Adapters) ................... 4 Supported Operating Systems ......................5 Using WOL after A/C Power Disconnect or with no Operating System (OS) Installed (Out‐of‐Box, or D0uninitialized) ................... 6 Enabling WOL under Microsoft Windows NT 4.0............. 8 Enabling WOL under Microsoft Windows 2000 Server or Microsoft Server 2003 Family Operating Systems....................10 Enabling WOL under Red Hat Enterprise Linux® versions 4 and later and SUSE® Linux Enterprise Server versions 9 and later ..............12 Enabling WOL under Novell® NetWare® 5.x and 6.x ............ 14 October 2007 Page 2 Dell Enterprise Product Group... -
Page 3: Introduction
Wake‐On‐LAN allows a server to be remotely powered on. Wake‐On‐LAN technology resides in a server’s managed network interface card (NIC) and/or in a LAN‐on‐motherboard (LOM) integrated network connection. When a WOL enabled system is placed in a power saving mode (hibernate, standby, power off, etc...), the managed NIC or LOM uses the auxiliary power source to monitor the network and receive a wake‐up packet. When a wake‐up packet is received, the system powers up as normal. Prerequisites Tools The following tools are necessary to have on hand before using wake‐on‐LAN on a Dell server: 1. DOS bootable floppy disk, MS DOS version 6.0 or newer, FreeDOS or DRDOS (APM WOL only.) 2. IBAUTIL.EXE version 4.02.02.01 or newer for Intel network interface cards (NICs) or Intel‐based LANs on Motherboard (LOMs). 3. B57UTIL.EXE version 10.11 or newer or B57UDIAG.EXE version 6.04 or newer for Broadcom NICs or Broadcom‐based LOMs. 4. UXdiag.exe version 1.3.1 or newer for Broadcom NetXtreme II NICs or LOMs. 5. Ethtool 1.8.4 or better for Linux WOL (Dell Servers support Red Hat Enterprise Linux® and SUSE® Enterprise distributions of Linux.) 6. The latest BIOS for each system to use WOL. October 2007 Page 3 Dell Enterprise Product Group... -
Page 4: Dell Servers That Support Wake-On-Lan
Dell Servers that Support Wake-on-LAN The following are the Dell servers that support wake‐on‐LAN, and to what extent: • WOL is only supported on the LOM(s) (LAN on motherboard or integrated [embedded] NIC) PowerEdge™ 350 PowerEdge 1550 PowerEdge 6400 PowerEdge 6450 • WOL is supported on the LOM(s) and in all slots with a WOL‐supported PowerEdge 500 PowerEdge 600 PowerEdge 1400 PowerEdge 1600SC PowerEdge 1650 PowerEdge 1750 Broadcom NICs may cause the system to not boot if WOL is enabled for them in a slot in this system due to the larger amount of current drawn by them when in a WOL state. PowerEdge 2400 PowerEdge 2450 PowerEdge 2500 PowerEdge 2550 WOL is not supported on the Gigabit LOM PowerEdge 2600 PowerEdge 2650 PowerEdge 4400 PowerEdge 4600 PowerEdge 7150 •... -
Page 5: Supported Operating Systems
• No Operating System Installed • Microsoft® Windows NT® 4.0 Server Family The Microsoft Windows NT 4.0 Server family is not ACPI compliant; the driver must set up WOL. • Microsoft Windows Server® 2000 Family Microsoft Windows 2000 is ACPI (Advanced Configuration and Power Interface) compliant and supports WOL from Hibernate and Standby. Dell servers support the Hibernate mode and not the Standby mode, with the exception of the PowerEdge 350, which supports Standby and not Hibernate. • Microsoft Windows Server 2003 and 2008 (when available) Families Microsoft Windows Server 2003 is ACPI (Advanced Configuration and Power Interface) compliant and supports WOL from Hibernate and Standby. Dell servers support the Hibernate mode and not the Standby mode, with the exception of the PowerEdge 350, which supports Standby and not Hibernate. • Red Hat® Enterprise Linux® versions 4 and newer Linux is not currently ACPI compliant and WOL must be set up by the driver or another agent. • SUSE® Linux Enterprise Server versions 9 and newer Linux is not currently ACPI compliant and WOL must be set up by the driver or another agent. • Novell® NetWare® 5.x and 6.0 NetWare is not ACPI compliant and WOL must be set up by the driver. October 2007 Page 5 Dell Enterprise Product Group... -
Page 6: Using Wol After A/C Power Disconnect Or With No Operating System (Os) Installed (Out-Of-Box, Or D0Uninitialized)
DOS‐bootable floppy and copy the utility, listed in the Tools section above, specific to the WOL device to it from the Dell Open Management Server Assistant or download it from http://support.dell.com. Note: Broadcom B5700 and B5701 based NICs and LOMs do not support WOL in this way. The steps to enabling WOL after A/C power disconnect or with no operating system are as follows: 1. Boot the system using the DOS floppy, and run ‘IBAUTIL.EXE’, ‘UXDIAG.EXE –t ABCD’ or ‘B57UDIAG.EXE –t ABCD’. These programs will display the physically installed adapters and the status of each card’s WOL setting. UXDIAG.EXE is for NetXtreme II devices and B57UDIAG.EXE is for NetXtreme I devices. 2. Choose the NIC for WOL, record its MAC address, and note its number on the left hand side of the display. a. Enable Intel WOL by typing ‘ibautil –nic=X –wole’ where X is the number of the NIC in the display. b. Enable Broadcom NX1 WOL by typing ‘b57udiag –w 1 –c X’ where X is the number of the NIC in the display. Enable Broadcom NX2 WOL by typing ‘uxdiag –c X –wol 1’ where X is the number of the NIC in the display. October 2007 Page 6 Dell Enterprise Product Group... - Page 7 3. Unplug the system and send it to the remote site to be installed. The system must be removed from all A/C input for a period of at least 10 seconds to allow all capacitance to drain from the system so it resets to its default state. The system must not be powered on, just connected to A/C and the WOL enabled NIC connected to the active network. The system is now ready to be powered on via WOL when needed. 4. Send a ‘Magic Packet’ wake up signal to the MAC address of the WOL enabled NIC, and the system will boot. Out‐of‐Box WOL can only be accomplished via the ‘Magic Packet’ WOL signal. October 2007 Page 7 Dell Enterprise Product Group...
-
Page 8: Enabling Wol Under Microsoft Windows Nt 4.0
1. Boot the system using the DOS floppy, and run ‘IBAUTIL.EXE’, ‘UXDIAG.EXE –t ABCD’ or ‘B57UDIAG.EXE –t ABCD’. These programs will display the physically installed adapters and the status of each card’s WOL setting. UXDIAG.EXE is for NetXtreme II devices and B57UDIAG.EXE is for NetXtreme I devices. 2. Choose the NIC for WOL, record its MAC address, and note its number on the left hand side of the display. a. Enable Intel WOL by typing ‘ibautil –nic=X –wole’ where X is the number of the NIC in the display. b. Enable Broadcom NX1 WOL by typing ‘b57udiag –w 1 –c X’ where X is the number of the NIC in the display. Enable Broadcom NX2 WOL by typing ‘uxdiag –c X –wol 1’ where X is the number of the NIC in the display. 3. Reboot the system and login to Windows NT 4.0 with an account that has administrator privileges. If the most recent Dell‐provided drivers are not installed, install them. Dell strongly suggests updating to the newest versions of the network drivers available on the Dell support web site. 4. For Broadcom NICs and LOMs, or Intel Gigabit (1000 MBps) NICs or LOMs, skip to step 9. 5. For Intel FastEthernet (10/100 Mbps) NICs or LOMs, from the system tray or from the control panel, open PROSet II. Click on the NIC with WOL October 2007 Page 8 Dell Enterprise Product Group... - Page 9 6. Choose the Advanced Tab. In the settings frame, choose Enable PME and change the value to Enabled. 7. Click OK. Windows NT 4.0 will prompt for a reboot. Choose Yes. 8. After the system has restarted, if the NIC is not already connected to a switch or hub, connect it and shut the system down. 9. Shut the system off. The connection LED on the NIC and switch or hub will remain on indicating the NIC is monitoring the network for wake up packets directed to its MAC address. 10. Send a wake up signal to the MAC address of the WOL enabled NIC, and the system will boot. Note: If the system boot is interrupted before the OS and the NIC driver are loaded, the system will not be able to perform WOL again until the system is rebooted manually and the OS and driver are allowed to load and reset the NIC’s WOL registers. October 2007 Page 9 Dell Enterprise Product Group...
-
Page 10: Enabling Wol Under Microsoft Windows 2000 Server Or Microsoft Server 2003 Family Operating Systems
2003 operating systems are as follows: 1. Windows 2000 and Windows 2003 do not require that WOL be turned on in the NIC’s or LOM’s firmware, therefore the steps using DOS outlined in the Out‐of‐Box and Windows NT 4.0 procedures are not necessary and should be skipped. Enabling WOL with IBAUTIL.EXE, UXDIAG.EXE or B57UDIAG.EXE may be detrimental to WOL under Windows 2000 and Windows 2003. 2. Login to Windows 2000/2003 with an account that has administrator privileges. If the most recent Dell provided drivers for the NIC are not installed, install them. Open the properties for the NIC enabled for WOL and then click the ‘Configure’ button. Choose the Power Management Tab and enable the check box next to the line ‘Allow this device to bring the computer out of standby.’ Standby in this case refers to both Standby and Hibernate. Ensure that the check box next to the line ‘Allow the computer to turn off this device to save power’ is also checked. 3. Ensure Hibernate is enabled for the system by opening Power Options in the Control Panel, choosing the Hibernate Tab and checking ‘Enable hibernate support’. (See Note below if using a PowerEdge 350.) 4. Click OK. 5. If the NIC is not already connected to a switch or hub, connect it and set the system to hibernate by clicking Start/Shutdown and choosing Hibernate. October 2007 Page 10 Dell Enterprise Product Group... - Page 11 6. The system will shut off. The connection LED on the NIC and switch or hub will remain on indicating the NIC is monitoring the network for wake up packets directed to its MAC address. 7. Send a wake up signal to the MAC address of the WOL enabled NIC, and the system will boot. Note: If the system boot is interrupted before the operating system (OS) and the NIC driver are loaded, the system will not be able to perform WOL again until the system is rebooted manually and the OS and driver are allowed to load and reset the NIC’s WOL registers. PowerEdge 350 Note: The PowerEdge350 is the only Dell server that supports Standby and not Hibernate. The same procedures should be followed with the exception of the Hibernate enabling step and the shutdown to hibernate. Standby is enabled by default. Send the system in to standby by clicking Start/Shut Down then choosing Standby. October 2007 Page 11 Dell Enterprise Product Group...
-
Page 12: Enabling Wol Under Red Hat Enterprise Linux Versions 4 And Later And Suse Linux Enterprise Server Versions 9 And Later
The steps to Enabling WOL under Red Hat Enterprise Linux versions 4 and later and SUSE Linux Enterprise Server versions 9 and later are as follows: 1. Login to the BASH shell with root privileges. If the most recent Dell provided drivers are not installed, install them. Run ‘ethtool ethX’ where ‘ethX’ is the name and instance of the desired WOL network interface. The WOL capabilities and current default settings will be displayed in the output. a. The ethtool man pages have more information on settings and meanings of the settings. b. If the default settings show WOL disabled (as they will by default as shipped from Dell) then following steps 1 and 2 in the Out‐of‐Box WOL instruction section will change the default setting. Enabling WOL with ethtool when the default is disabled will not persist across reboots, meaning that shutting down and performing WOL once, then shutting down again and attempting WOL will not be successful without running ethtool again to enable WOL. The use of a startup script can enable WOL on each subsequent reboot if desired, or changing the default from the DOS based utilities. 2. Run ‘ethtool ethX –s wol g’ to enable Magic Packet WOL, where ethX is the name and instance of the desired WOL network interface. 3. Halt Linux and shut the system off. The connection LED on the NIC and switch or hub will remain on, indicating the NIC is monitoring the network for wake up packets directed to its MAC address. October 2007 Page 12 Dell Enterprise Product Group... - Page 13 To enable wake up types other than Magic Packet, check the ethtool man pages. 4. Send a Magic Packet wake up signal to the MAC address of the WOL enabled NIC, and the system will boot. Note: If the system boot is interrupted before the OS and the NIC driver are loaded, the system will not be able to perform WOL again until either the system is rebooted manually and the OS and driver are allowed to load and reset the NICs WOL registers, or A/C power to the system is removed for at least 30 seconds, resetting the NIC’s WOL registers. October 2007 Page 13 Dell Enterprise Product Group...
-
Page 14: Enabling Wol Under Novell® Netware® 5.X And 6.X
‘UXDIAG.EXE –t ABCD’ or ‘B57UDIAG.EXE –t ABCD’. These programs will display the physically installed adapters and the status of each card’s WOL setting. UXDIAG.EXE is for NetXtreme II devices and B57UDIAG.EXE is for NetXtreme I devices. 2. Choose the NIC for WOL, record its MAC address, and note its number on the left hand side of the display. a. Enable Intel WOL by typing ‘ibautil –nic=X –wole’ where X is the number of the NIC in the display. b. Enable Broadcom NX1 WOL by typing ‘b57udiag –w 1 –c X’ where X is the number of the NIC in the display. Enable Broadcom NX2 WOL by typing ‘uxdiag –c X –wol 1’ where X is the number of the NIC in the display. 3. Reboot the system and start the NetWare server. If the most recent Dell‐ provided drivers are not installed, install them. 4. For Intel based NICs or LOMs no modification is necessary, the driver is set up for WOL by default. To turn off WOL, use the ‘pmedisable=1’ key word in the load line. Set ‘pmedisable=0’ to re‐enable WOL 5. For Broadcom based NICs or LOMS, the keyword ‘magicp=1’ must be used to enable the driver for WOL. Setting ‘magicp=0’ disables WOL, disabled is the default. October 2007 Page 14 Dell Enterprise Product Group... - Page 15 6. Restart the server. After the server has restarted, if the NIC is not already connected to a switch or hub, connect it and shut the server down. 7. Shut the system off. The connection LED on the NIC and switch or hub will remain on indicating the NIC is monitoring the network for wake up packets directed to its MAC address. 8. Send a wake up signal to the MAC address of the WOL enabled NIC, and the system will boot. Note: If the system boot is interrupted before the OS and the NIC driver are loaded, the system will not be able to perform WOL again until the system is rebooted manually and the OS and driver are allowed to load and reset the NIC’s WOL registers. ©Copyright 2003‐2008 Dell Computer Corporation. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Computer Corporation is strictly forbidden. For more information, contact Dell. Dell cannot be responsible for errors in typography or photography. Trademarks used in this text: Dell, PowerEdge, and OpenManage are trademarks of Dell, Inc.; Microsoft, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft; Intel is a registered trademark of Intel Corporation.; Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc.; Novell and NetWare are registered trademarks of Novell, Inc.; SUSE is a registered trademark of SUSE Linux Products GmbH. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims any proprietary interest in trademarks and trade names other than its own. Information in this document is subject to change without notice. The content is provided as is, without express or implied warranties of any kind. October 2007 Page 15 Dell Enterprise Product Group...