Asf 2.0 Example And Use Case - HP dc5100 - Microtower PC Configuration Manual

The Softpaq that supports Broadcom also includes two utilities that allow easy deployment of ASF in an
enterprise environment, as follows:
Broadcom ASF Remote Configuration Program: Command line application that allows IT Administrators
to remotely configure Broadcom adapter ASF support. This application requires the Microsoft WMI and
Broadcom CIM provider on the host system to connect and configure. Full details are available in the
Release.txt file at \ASF\RConfig within the Softpaq. You can install the Broadcom CIM provider using
the \MgmtApps folder in the Softpaq.
Broadcom ASF Silent Configuration Program for Windows and Linux: Command line utility for use in
place of Broadcom's ASF Configuration utility. More information is available at \ASF\SConfig in the
softpaq.

ASF 2.0 example and use case

The following example details how you could use ASF with supplied SDKs from Broadcom and Intel,
assuming the Management Console vendor fully implemented ASF 2.0. The Management Console config-
ures the ASF client utilizing WMI, configuring the timers and security keys to their desired settings. For this
example, assume that ASF is deployed and configured correctly.
Example
The Management Console needs to deploy a new software update to all clients to correct an intermittent
computer lockup coming out of low power states. Clients A and B are not reachable, but both clients have
not reported that any Watchdog timers have expired, and both are still sending heartbeats to the Con-
sole. The Management Console performs the following steps:
1. The Console attempts to retrieve client status from ASF. The Console first authenticates both clients and
establishes session IDs.
2. The Console then sends capability requests to the clients to determine remote capabilities. Both clients
report back that they are capable of all RMCP events, and the Console populates remote control
options for those clients for Administrator use.
3. The Console now needs to determine the state of the clients and sends System State requests. Both cli-
ents report back that they are currently in S4 (Hibernate).
4. The Console now knows it needs to wake the systems to update the software, so it sends RMCP Power
Up commands to the clients, and both clients respond that they received the request (RMCP ACK).
5. At this point, the Console waits for the Console's Agent Utility to report in and connect to the console
for the software update.
• Client A successfully loads the operating system, loads the console agent, and receives the
software update.
• Client B is not successful and sends the console an operating system Watchdog expire event,
as the system had the computer lockup error that the desired software update should correct.
The Console now knows that something happened between POST and operating system load that
prevented Windows from loading properly.
6. The Console then sends Client B an RMCP Power Reset command, hence Client B powers off and
powers back on five seconds later. Client B now loads the operating system properly, and its console
agent connects successfully and receives the software update.
This is just one example of how ASF can reduce desk-side visits and can repair problems remotely.
6