Broadcom BACS for HP FlexFabric and StoreFabric Adapters User Guide
Abstract
This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the
servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
Part Number: 741900-003
April 2014
Edition: 3
© Copyright 2013, 2014 Hewlett-Packard Development Company, Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
AMD is a trademark of Advanced Micro Devices, Inc. Intel is a trademark of Intel Corporation in the U.S. and other countries.
Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.
Contents
Introduction .................................................................................................................................. 5
BACS overview ............................................................................................................................................ 5
Starting BACS .............................................................................................................................................. 5
BACS interface on Microsoft Windows operating systems ................................................................................ 5
Explorer View pane ............................................................................................................................ 5
Context View selector ......................................................................................................................... 6
Context View pane ............................................................................................................................. 6
Menu bar .......................................................................................................................................... 6
Description pane ................................................................................................................................ 7
Installation overview ...................................................................................................................... 8
Introduction ................................................................................................................................................. 8
Hardware requirements ................................................................................................................................ 8
Software requirements .................................................................................................................................. 8
Communication protocols .............................................................................................................................. 9
Installation summary ..................................................................................................................................... 9
Installation summary for Microsoft Windows operating systems ............................................................... 9
Installation summary for Linux operating systems .................................................................................. 10
Installing BACS components on Microsoft and Linux operating systems ............................................. 12
WinRM installation steps ............................................................................................................................. 12
Basic configuration ........................................................................................................................... 12
User configuration ............................................................................................................................ 12
Configuring HTTP ............................................................................................................................. 12
Configuring HTTPS ........................................................................................................................... 13
Generating a self-signed certificate for Microsoft and Linux servers ........................................................ 14
Installing the management application .......................................................................................... 18
Installation on Microsoft Windows OS ......................................................................................................... 18
Installing the BACS management client on a Microsoft Windows operating system ................................. 18
Configuring HTTP on Microsoft operating systems ................................................................................ 18
Configuring HTTPS on Microsoft operating systems .............................................................................. 19
Testing a client WinRM HTTPS/SSL connection.................................................................................... 19
Installation on Linux OS .............................................................................................................................. 19
Downloading and unpacking HP SoftPaq ........................................................................................... 20
Installing OpenSSL and OpenPegasus ................................................................................................ 20
Installing WS-MAN and CimXML on Linux OS .................................................................................... 21
Installing OpenPegasus from Inbox RPM for Red Hat ............................................................................ 21
Installing OpenPegasus from Source for Red Hat and SuSE .................................................................. 21
Launching the application ............................................................................................................ 29
Launching the GUI in Microsoft Windows OS ............................................................................................... 29
Launching the GUI in Linux OS .................................................................................................................... 29
Closing the GUI in Microsoft Windows OS ................................................................................................... 29
Launching the CLI from Microsoft Windows OS ............................................................................................. 29
Launching the CLI from Linux OS .................................................................................................................. 29
Closing the CLI ........................................................................................................................................... 29
Contents 3
Configuration ............................................................................................................................. 30
Configuring preferences .............................................................................................................................. 30
Enabling or disabling the BACS tray icon ........................................................................................... 30
Setting Explorer View refresh time ...................................................................................................... 30
Connecting to a host .................................................................................................................................. 30
Adding a local host .......................................................................................................................... 30
Adding a remote host ....................................................................................................................... 30
Managing the host ..................................................................................................................................... 31
Information tab ................................................................................................................................ 31
Configuration tab ............................................................................................................................. 31
Managing the network adaptor ................................................................................................................... 31
Viewing adapter information ............................................................................................................. 32
Viewing resource information ............................................................................................................ 32
Viewing hardware information .......................................................................................................... 32
Configuring adapter parameters ........................................................................................................ 33
Configuring multi-function parameters ................................................................................................. 33
Hardware and resource configuration wizard ..................................................................................... 33
Managing the Ethernet controller (port) ......................................................................................................... 33
Viewing port level information ........................................................................................................... 33
Viewing vital signs ........................................................................................................................... 34
Managing the LAN device .......................................................................................................................... 35
Viewing NDIS information ................................................................................................................. 35
Viewing resource information ...................................................................................................................... 36
Viewing statistics .............................................................................................................................. 36
Viewing resource reservations ........................................................................................................... 39
Changing the MTU size of iSCSI ports ................................................................................................ 39
Configuring the IP address for iSCSI offload ....................................................................................... 39
CLI commands ............................................................................................................................ 41
Configuring with the CLI utility ..................................................................................................................... 41
Support and other resources ........................................................................................................ 42
Before you contact HP ................................................................................................................................ 42
HP contact information ................................................................................................................................ 42
Acronyms and abbreviations ........................................................................................................ 43
Documentation feedback ............................................................................................................. 46
Index ......................................................................................................................................... 47
Contents 4
Introduction
BACS overview
BACS is an integrated utility that provides useful information about each network adapter installed in a
system. BACS provides views of property values and traffic statistics for network objects. BACS also enables
modification of property values. BASP functionality configures VLANs and runs within BACS systems that use
Starting BACS
at least one Broadcom-based network adapter.
From the Control Panel, click Broadcom Control Suite 4 to start the BACS. Or, click the BACS icon located in
the taskbar at the bottom of the Windows desktop.
BACS interface on Microsoft Windows operating systems
The BACS Microsoft Windows interface contains the following regions:
• Explorer View pane
• Context View selector
• Context View pane
• Menu bar
• Description pane
The default configuration docks and pins the Explorer View pane on the left side of the main window, the
Context View pane on the right, the Context View selector below the menu bar, and the Description pane
Explorer View pane
below the Context View pane. Drag the splitter between any two panes to vary the pane size.
Dock and pin the Explorer View pane on the left side, right side, top, or bottom of the main window.
The Explorer View pane lists the objects that you can view, analyze, test, or configure using BACS. When
you select an item from the Explorer View pane, the Context View pane displays the tabs with the information
and options available for the item.
The organization and design of this panel presents the manageable objects in the same hierarchical manner
as drivers and subcomponents. This simplifies the management of various elements of the adapters. The top
level of the hierarchy is the Host container, which lists all hosts managed by BACS. Below the hosts are the
installed network adapters, with the manageable elements such as physical port VBD, NDIS, FCoE, and
iSCSI, below the adapters.
Introduction 5
The icon next to each device in the Explorer View pane shows its status. An icon next to a device name that
appears normal means the device is connected and working.
• X appears on the device icon to indicate the device is currently not connected to the network.
• Greyed out device icons indicate the device is currently disabled.
Context View selector
The Context View selector appears below the menu bar and includes the filter and tab categories. Expand or
collapse the categories that appear on the tabs in the Context View pane. To display a category, select the
Filter view
box next to the category name.
A multiple-host environment that uses different adapters and contains multiple configurable elements can be
difficult to manage. Use the following view filters to increase device administration efficiency:
• All
• NDIS/L2NIC
• iSCSI
• FCoE
• iSCSI target
• FCoE target
Context View pane
The Context View pane displays all the parameters that you can view for the object selected in the Explorer
View pane. The parameters are grouped by tabs and categories, depending on the parameter type. The
available tabs are Information, Configuration, Diagnostics, and Statistics. Because the BACS interface is
context-sensitive, only the parameters that apply to the selected object can be viewed or configured in the
Context View pane.
Menu bar
The following options appear on the menu bar. Because the menu items are context-sensitive, not all items are
available at all times.
File menu
Action menu
• Add Host adds the selected host.
• Discover Hosts discovers hosts.
• Boot Configurations configures the iSCSI boot parameters.
• Remove Hosts removes the selected host.
• Remove All Hosts removes all the hosts.
• Refresh All refreshes all the hosts.
View menu
Introduction 6
• Explorer View displays and hides the Explorer View pane.
• Tool Bar displays and hides the tool bar.
• Status Bar displays and hides the status bar.
• Broadcom Logo displays and hides the logo on BACS to optimize the maximum viewable space.
Tools menu
Options configure BACS preferences.
iSCSI menu
• Discovery Wizard locates targets and helps to configure the HBA.
• Manage Targets Wizard manages targets.
• Manage iSNS Servers manages iSNS servers to allow discovery, management, and configuration of
iSCSI devices.
• Manage Discovery Portals manages iSCSI discovery portals.
Discovery Wizard
The Discovery Wizard is available from the iSCSI menu. Follow the prompts in the wizard to discover iSCSI
targets using the SendTargets method or the Internet iSNS server.
Manage iSNS Servers
The Manage iSNS Servers window is available from the iSCSI menu. Add or remove iSNS servers from this
window.
Manage Discovery Portals
The Manage Discovery Portals window is available from the iSCSI menu. Add or remove iSCSI discovery
portals from this window.
Boot Configuration Wizard
The Boot Configuration Wizard is available by right-clicking a port. Follow the prompts in the wizard to
configure the iSCSI boot parameters.
Hardware and Resource Configuration Wizard
Use the Hardware and Resource Configuration Wizard to configure properties for hardware resources.
Follow the prompts in the wizard to configure hardware resources. You can preview the configuration before
committing the changes.
Description pane
The Description pane provides information, configuration instructions, and options for the selected
parameter in the Context View pane.
Introduction 7
Installation overview
Introduction
BACS management can be installed on both Microsoft Windows and Linux platforms.
The BACS installer package for the Microsoft Windows OS is based on Microsoft MSI installation
technology. The Broadcom Windows CIM provides WS-MAN and WMI protocol support for client-server
connections.
The Broadcom Linux CIM provides WS-MAN protocol and CimXML protocol support for client-server
Hardware requirements
connections.
Systems that host BACS must meet the following hardware requirements:
• At least one of the following HP FlexFabric adapters:
o HP FlexFabric 10Gb 2-port 534M Adapter
o HP FlexFabric 10Gb 2-port 534FLR-SFP+ Adapter
o HP FlexFabric 10Gb 2-port 534FLB Adapter
o HP StoreFabric CN1100R 2-port CNA Adapter
o HP FlexFabric 20Gb 2-port 630FLB Adapter
o HP FlexFabric 20Gb 2-port 630M Adapter
• A single or multiprocessor HP ProLiant Gen8 system
• 128 MB of physical RAM to run the BACS4 GUI Management Application
HP recommends 256 MB because less memory can severely affect performance.
• A video card capable of handling 256K colors and screen resolution of 800 x 600
HP recommends 16K colors and 1024 x 768 resolution.
• At least 200 MB disk space
Software requirements
BACS is designed to run on the following Microsoft Windows platforms:
• Microsoft Windows Server 2012 64-bit, Intel 64, AMD 64
• Microsoft Windows Server 2008 32-bit, 64-bit Intel x86, Intel 64, AMD 64
• Microsoft Windows Server 2008 R2 64-bit, Intel 64, AMD 64
To use the SNMP management features, install the SNMP service. There is no other software requirement for
Microsoft Windows. All required software components are included in the BACS4 GUI installer package
and are installed as part of the installation process.
Installation overview 8
BACS is designed to run on the following Linux platforms:
• Red Hat Enterprise 5, 32-bit, 64-bit Intel x86, Intel 64, AMD 64
• Red Hat Enterprise 6, 32-bit, 64-bit Intel x86, Intel 64, AMD 64
• SuSE Enterprise, SLES, 10, 32-bit, 64-bit Intel x86, Intel 64, AMD 64
• SuSE Enterprise, SLES, 11, 32-bit, 64-bit Intel x86, Intel 64, AMD 64
The Linux OS requires specific software components. For more information, see "Installing BACS components
on Microsoft and Linux operating systems (on page 12)."
Communication protocols
Broadcom provides the following communication protocols that are used to connect server and client
systems:
• Microsoft Windows clients and servers can use WMI and WS-MAN/WinRM.
Linux systems that connect to Microsoft Windows servers can use the WS-MAN/WinRM protocol to
connect to the Microsoft Windows server.
• Linux clients and servers can use CimXML/Open Pegasus and WS-MAN/Open Pegasus.
Microsoft Windows clients that connect to Linux servers can use the CimXML/Open Pegasus and
WS-MAN/Open Pegasus protocols to connect to the Linux server.
• If Microsoft Windows and Linux clients both access Windows and Linux servers on a network, use the
WS-MAN protocol.
• If Linux is the only OS installed on the servers, use the CimXML protocol.
• If the network only has Microsoft Windows clients and servers, use the WMI protocol. WMI does not
require as much configuration as other protocols but is only supported on Microsoft Windows systems.
Installation summary
Installation summary for Microsoft Windows operating systems
Install BACS on either, or both, Microsoft Windows and Linux operating systems.
Microsoft Windows Server
Use the following items to install BACS on a Microsoft Windows Server. For the complete installation
instructions, see "Installing BACS components on Microsoft and Linux operating systems (on page 12)."
To install BACS on a Microsoft Windows server:
1. Install WinRM software component on the server.
2. Perform Basic configuration on the server.
3. Perform User configuration on the server.
4. Perform HTTP configuration on the server.
5. Perform HTTPS configuration on the server.
a. Generate a self-signed certificate for Microsoft Windows server.
b. Install a self-signed certificate on a Microsoft Windows server.
Installation overview 9
6.
Configure, and then test the WinRM listener on the server.
7. Perform additional configuration, if required, like firewall configuration on the server.
8. Install the BACS management application.
Microsoft Windows client
Use the following items to install BACS on a Microsoft Windows client. For the complete installation
instructions, see "Installing BACS components on Microsoft and Linux operating systems (on page 12)."
To install BACS on a Microsoft Windows client:
1. If you plan to use HTTP with WS-MAN, perform HTTP configuration on a client.
2. If you plan to use HTTPS with WS-MAN, perform HTTPS configuration on a client.
3. Configure WinRM listener on a client.
4. Install the BACS client application on client systems.
The WMI protocol is only supported on Microsoft Windows OS. CimXML is not supported on Microsoft
Windows OS.
BACS WMI on a Microsoft Windows server
Use the following items to install BACS WMI on a Microsoft Windows server. For the complete installation
instructions, see "Setting up namespace security using WMI control (on page 26)."
To install BACS WMI on a Microsoft Windows server:
1. Set namespace security using WMI control.
2. Grant DCOM remote launch, and then activate permission for a user or group.
3. Perform special configuration, if necessary.
4. Follow the standard Microsoft Windows client installation steps to use WMI on a Microsoft Windows
client.
Installation summary for Linux operating systems
Use the following items to install BACS on a Linux server. For the complete installation instructions, see
"Installing BACS components on Microsoft and Linux operating systems (on page 12)."
Install the following items in the following order:
1. OpenSSL
2. Pegasus
3. BRCM_CMPIProvider-x.x.x.rpm
4. BACS-x.x.x.rpm
There are two installation options available with OpenPegasus–Inbox RPM or from source. The Inbox
OpenPegasus is only available on Red Hat OS. For SLES11, the only available option is the source RPM.
WS-MAN is not supported with the Inbox RPM. To use WS-MAN, install OpenPegasus from source.
To install BACS on a Linux server:
1. Install OpenPegasus on server from source RPM.
2. Start CIM Server on the server.
3. Configure OpenPegasus on server.
4. Install Broadcom CIM provider.
Installation overview 10
5.
Perform additional configuration, if required, like firewall configuration.
6. Install the BACS client application on client systems, Microsoft Windows OS, or Linux.
Linux client
The following items are needed to install BACS on a Linux client. For the complete installation instructions, see
"Installing BACS components on Microsoft and Linux operating systems (on page 12)."
To install BACS on a Linux client:
1. Install the following:
a. OpenSSL
b. Pegasus
c. BRCM_CMPIProvider-x.x.x.rpm
d. BACS-x.x.x.rpm
2. To use HTTPS with WS-MAN, perform HTTPS configuration on client.
For HTTP, no special configuration is required on Linux client system. Only the BACS management
application is required.
3. Install the BACS client application on client system.
BACS CimXML on a Linux server
Use the following items to install BACS CimXML on a Linux server. For the complete installation instructions,
see "Installing BACS components on Microsoft and Linux operating systems (on page 12)." The installation
steps for Linux server are similar to WS-MAN.
There are two installation options available with OpenPegasus–Inbox RPM or from source. The Inbox
OpenPegasus is only available on Red Hat OS. For SLES11, the only available option is the source RPM.
WS-MAN is not supported with the Inbox RPM. To use WS-MAN, install OpenPegasus from source.
To install BACS on a Linux server:
1. Install OpenPegasus on the server from Inbox RPM or from source RPM.
2. Start CIM Server on the server.
3. Configure OpenPegasus on the server.
4. Install the Broadcom CIM provider.
5. Perform additional configuration, if required, like firewall configuration.
6. Install the sg3_utils package, which is available in the Linux Distribution Package Repository. The
package is required to query LUN information.
7. Install the BACS client application on client systems, Microsoft Windows OS, or Linux.
8. Follow the standard Linux client installation steps to use CimXML on a Linux client.
Installation overview 11
Installing BACS components on Microsoft and Linux operating systems
WinRM installation steps
WinRM 2.0 is pre-installed on Microsoft Windows 7 and Windows 2008 R2.
For Microsoft Windows 2008, install the Windows Management Framework Core that includes WinRM 2.0
and Windows Powershell 2.0. For more information, see the Microsoft website
Basic configuration
(http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11829).
The Microsoft Windows firewall must be enabled for WinRM to work properly.
To configure WinRM basic:
1. Configure the Microsoft Windows firewall.
For detailed information about firewall configuration, see "Modifying Microsoft Windows Firewall rules
(on page 16)."
2. Open a command prompt, and then run winrm quickconfig.
The winrm quickconfig command enables remote management on the Microsoft Windows server.
3. Obtain the configuration information of the client service:
winrm get winrm/config
The output of this command is RootSDDL =
O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD).
BA stands for BUILTIN\Administrators.
User configuration
A user account must be a member of the Microsoft Windows Administrators group on the local or remote
computer to connect to WinRM. User accounts must also be added to the WinRM allowed connect list.
Modify the root SDDL to include the user account or group. The SSDL ID for the account or group you want
to add is required.
To add a user, for example with an SDDL ID of S-1-5-21-1866529496-2433358402-1775838904-1021:
winrm set winrm/config/Service
@{RootSDDL="O:NSG:BAD:P(A;GA;;;BA)(A;;GA;;;S-1-5-21-1866529496-243335840
2-1775838904-1021)S:P(AU;FA;GA;;WD)(AU;SA;GWGX;;;WD)"}
Configuring HTTP
The default HTTP port for WinRM 2.0 is 5985.
Installing BACS components on Microsoft and Linux operating systems 12
Loading...