Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Windows Server: Common Issues in Broadcom Advanced Control Suite 4

Summary: This article contains information about common issues encountered in Broadcom Advanced Control Suite version 4 (BACS4) on Windows servers.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

This article provides information about common issues encountered in Broadcom Advanced Control Suite version 4 (BACS4) on Windows servers.


Cause

  See below.

Resolution

Table of Contents:

  1. "Control Suite" component is management client only
  2. Adapter teaming is not available

1. "Control Suite" component is management client only

The first issue concerns the installer. Notice that the Common Information Model (CIM) Provider is now a requirement for the Broadcom Advanced Server Program (BASP) driver and that there are no components beneath the Control Suite. This is a change from previous versions of the application. The Control Suite component is the management client, allowing you to manage the local server or a remote machine.

In order for a machine to be managed (locally or remotely) using BACS, it must have the CIM Provider component installed. It is often forgotten to install this component. Attempting to manage a machine that does not have the CIM Provider installed results in a "Cannot connect to host" error. This can be confusing when attempting to manage the local server. The solution is simple, install the CIM Provider component on the machine that you want to manage by starting the installation file again. Once installed, choose the CIM Provider and BASP (Figure 1 below (Only English).
  Customer Setup CIM Provider
Figure 1: BACS version 4 installation

Back to Top


2. Adapter teaming is not available

The second issue concerns network adapter teaming. As you can see in the image below, the Teams menu at the top is not available. This occurs if Broadcom Advanced Control Suite (BACS) is not launched with administrator privileges. If BACS is launched from the system tray, as is common practice, it runs without administrator privileges. In order to use the full functionality of BACS, it is necessary to right-click BACS in the Start menu, select Run as Administrator, and click Yes when prompted by User Account Control.

Network Adapter teaming
Figure 2: BACS version 4 - Adapter options

The Teams menu is still unavailable until you select TEAM VIEW from the Filter dropdown list as shown below:

Teams menu unavailable
Figure 3: BACS version 4 - Teaming View

Back to Top

Affected Products

Servers
Article Properties
Article Number: 000139638
Article Type: Solution
Last Modified: 23 Sep 2024
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.