Remote Management Console Does Not Receive Any Heartbeat PET Events
Ensure that the physical network connection between the
destination computer and the Remote Management Console is functional.
Ensure that the Remote Console IP address setting in the Broadcom®
ASFConfig utility matches the Remote Console's IP address.
Ensure that the ASF Enable checkbox is selected/enabled in the
ASFConfig utility.
Ensure that the Heartbeat checkbox is selected/enabled in the
ASFConfig utility and the
Heartbeat Interval is set to a value other than 0.
Remote Management Console Does Not Receive
Any PET Events
Ensure that the physical network connection between the
destination computer and the Remote Management Console is functional.
Ensure that the Remote Management Console IP address setting in the
ASFConfig utility matches the Remote Console's IP address.
Ensure that the ASF Enable checkbox is selected/enabled in the
ASFConfig utility.
Cannot Wake Up the System Through ARP/RMCP
Ping Packets
Ensure that the physical network connection between the
destination computer and the Remote Management Console is functional.
Ensure that
the WoL option is enabled in the Windows NIC driver. This option can be enabled in
the NIC drivers Properties, Configure, Advanced tab
for the network interface.
Ensure that the Wol on ARP/RMCP checkbox is selected/enabled.
Why Do I See the Same Event More Than Once?
The events that are sent to the Remote
Console use the same packet format
used by the SNMP. It is a UDP-based network protocol, and by design, a UDP packet
may get lost in the network. To remedy this situation, the ASF Standard
states that each event must be re-transmitted three times to ensure successful delivery of the
event to the Remote Management Console.
This may be due to a situation in which a new IP address has been recently assigned by the DHCP
server. If the ASF IP Monitor (BASFIpM) utility is not running, it cannot update the ASF NIC with the new IP address. Check Windows
Service to ensure that BASFIpM is running.
