Broadcom ASF Management Console for Windows =========================================== February 2004, Rob Swindell ASF Background -------------- The ASF (Alert Standard Format) defines methods for remote management and control of systems in OS-absent environments. The Remote Management and Control Protocol (RMCP), defined as part of the ASF 1.0 protocol specification, provided no security mechanisms to protect desktop systems from unauthorized remote management. An ASF 1.0 managed client (Network Adapter) listens for RMCP messages on UDP port 26Fh (623). The ASF 2.0 protocol specification introduced the RMCP Security-Extensions Protocol (RSP) to provide authentication and integrity services for remote management. The secure RMCP protocol defined in ASF 2.0 listens for secure RMCP messages on UDP port 298h (664). About ASF 2.0 ------------- There are 2 supported authenticated user "roles" for ASF 2.0 remote management: Operator and Administrator. The implication is that authenticated Administrators may have more "rights" than authenticated Operators, but that determination is actually made by the individual that configures the Security Policy of the managed client (Network Adapter). It's actually possible for an Administrator to have fewer rights than an Operator, if the Security Policy is configured as such. Most secure RMCP messages can be sent to an ASF 2.0 managed client using a "Bypass Session" which provides no authentication or integrity. However, the "Remote Control" commands (i.e. Reset, PowerUp, PowerDown, and PowerReset) may require an authenticated session with the proper "rights" to execute these commands depending on the configured "Remote Capabilities" for the managed client. ASF Management Console Background --------------------------------- This program is a replacement for the Broadcom AsfNetMon application and should be used for all future ASF testing and verification in the Broadcom network controller group. It supports all the features of AsfNetMon, has far fewer bugs, conforms more closely to the ASF specification, and supports ASF 2.0 (secure management). You Will Need ------------- ASF testing requires a minimum of two computers: 1. A managed client with an ASF-enabled Broadcom Ethernet Network Adapter. This PC should be tested in both OS-present and OS-absent states. 2. A management console with any Network Adapter, running ASF Management Console software (presumably the Broadcom ASF Management Console for Windows). Installation ------------ No "installation" of the Broadcom ASF Management Console is required other than running the AsfMgmtCon.exe file. If you have existing Windows Registry Keys with AsfNetMon settings, it will use those settings for the managed client IP address history and the default managed client IP address. Any changes to the appliction form's size or position, the ASF 2.0 security settings, most checkboxes, and the managed client's IP address (and IP history) are automatically saved to the Windows registry when the application is shutdown and automatically restored when the application is later run on the same system. Configuration ------------- The "Manage" tab has all the controls require for management of an ASF "managed client". Enter the IP address of the client you wish to manage in the "Managed Client (IP Address)" edit box or pick one from the IP address history drop down box. To add an IP address to the history, hit the ENTER key while editing the IP address. To remove an IP address, hit the DELETE key. To send a management (RMCP) command to the managed client, select the desired command from the "Management Command" combo box and click the "Send" button. To send the same command repeatedly to the client, check the "Repeat" checkbox and enter the repeat count, with an optional "Delay" (in milliseconds) between each command/response sequence. You may also turn off the logging and status/ cursor indications to increase the number of commands that may be sent over a period of time, attempting to saturate the client with commands. To quickly send a single management command to the managed client, use one of the toolbar icons for: Ping, Capabilities Request, System State Request, Reset, Power Up, Power Down, or Power Reset. In order to create an authenticated session with a client using ASF 2.0, you must enter the security parameters in the "Security" tab and either click the "Authenticate" button or send the Management "Authentication" command from the Manage tab (effectively the same thing). If you wish to monitor PET messages (e.g. Heartbeat messages and other "events" sent from ASF clients), you must be running a Windows NT based operating system and have Windows SNMP Services installed and running. /* End of File */Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.