Linux BACS Installation: Broadcom NetXtreme II® Network Adapter User Guide
file:///C|/Users/Nalina_N_S/Documents/NetXtremeII/English/lnx_bacs.htm[9/5/2014 3:45:05 PM]
Back to Contents Page
Linux BACS Installation: Broadcom NetXtreme II
®
Network
Adapter User Guide
Overview
Installing WS-MAN or CIM-XML on Linux Server
Installing WS-MAN or CIM-XML on Linux Client
Installing the Broadcom Advanced Control Suite
Overview
The Broadcom Advanced Control Suite version 4 (BACS4) is a management application for configuring the NetXtreme II family
of adapters, also known as Converge Network Adapters (CNAs). BACS4 software operates on Windows and Linux server and
client operating systems. This chapter describes how to install the BACS4 management application.
This chapter describes how to install the BACS4 management application on Linux systems.
For Windows systems,
an installation program is provided which installs both the Windows drivers and the management applications, including
BACS4 (see
Windows Driver and Management Application Installation
for instructions).
There are two main components of the BACS4 utility: the provider component and the client software. A provider is installed
on a server, or "managed host", that contains one or more CNAs. The provider collects information on the CNAs and makes it
available for retrieval from a management PC on which the client software is installed. The client software enables viewing
information from the providers and configuring the CNAs.The BACS client software includes a graphical user interface (GUI)
and a command line interface (CLI).
Communication Protocols
A communication protocol enables exchanging information between provider and the client software. These are proprietary or
open-source implementations of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM)
standards from the Distributed Management Task Force (DMTF). Network administrators can choose the best option based on
the prevailing standard on their network.
The following table shows the available options based on the operating systems installed on the managed host and the client.
If the client uses:
And the managed host uses:
BACS can use these communication protocols:
Windows
Windows
WMI
WS-MAN (WinRM)
Windows
Linux
CIM-XML (OpenPegasus)
WS-MAN (OpenPegasus)
Linux
Windows
WS-MAN (WinRM)
Linux
Linux
CIM-XML (OpenPegasus)
WS-MAN (OpenPegasus)
WMI = Windows Management Instrumentation.
WS-MAN = Web Service-Management. WinRM is a Windows-based implementation and OpenPegasus is an open-
source implementation of the that operates on Linux.
CIM-XML = An XML-based version of OpenPegasus.
If your network includes a mix of Windows and Linux clients accessing Windows and Linux servers, then WS-MAN is a suitable
choice. If Linux is the only OS installed on the servers, then CIM-XML is an option. If the network includes only Windows
servers and clients, WMI is an option. WMI is very simple to configure but is supported only on the Windows OS. (See
Windows Driver and Management Application Installation
for instructions on installing and configuring the Windows protocols.)
BACS installation includes installing the provider component on the managed host and the client software on the management
station. The installation process differs based on the combination of operating systems installed on the client and managed
