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.
© 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.
Contents Introduction .................................................................................................................................. 5 BACS overview ............................................................................................................................................ 5 Starting BACS ..............................................................................................................................................
Configuration ............................................................................................................................. 30 Configuring preferences.............................................................................................................................. 30 Enabling or disabling the BACS tray icon ........................................................................................... 30 Setting Explorer View refresh time .............................................
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 at least one Broadcom-based network adapter. Starting BACS From the Control Panel, click Broadcom Control Suite 4 to start the BACS.
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.
• 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.
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 connections.
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).
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.
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.
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 (http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11829). Basic configuration The Microsoft Windows firewall must be enabled for WinRM to work properly.
To configure HTTP: 1. Select Start→Run, enter gpedit.msc, and then click OK. 2. Under Computer Configuration/Administrative Templates/Windows Components, select Windows Remote Management. 3. Under Windows Remote Management, select WinRm Client. 4. Under WinRM Client, double-click Trusted Hosts. 5. In the dialog, for TrustedHostsList, enter the hostnames of the clients. 6. If all clients are trusted, enter *, and then click OK. 7. Select WinRM Service. 8.
7. Select WinRM Service, and then enable Allow Basic Authentication. Generating a self-signed certificate for Microsoft and Linux servers Use Openssl to create a self-signed certificate. Openssl is available on both Microsoft Windows and Linux operating systems. To create a self-signed certificate on Microsoft Windows: 1. Generate a private key: openssl genrsa –des3 –out server.key 1024 2. Enter a passphrase at the prompt. Be sure to record the passphrase. 3.
Be sure to record the information to later import the certificate on a Microsoft Windows operating system. 3. Complete any additional steps as prompted. 4. Make a copy of server.crt, and then place the certificate file on the server where BACS is installed. To use a different computer to connect to the server running BACS, copy the same certificate to that computer. For a Linux server, create the certificate with the .pem extension. It is unnecessary to use the openssl command to convert from .crt to .
4. Select Computer Account. 5. Click Next, Finish, and then OK. 6. Expand Certificates (Local Computer). 7. Select the self-signed certificate from the personal store. If the certificate is created with a hostname, the hostname displays. 8. Double-click the hostname. 9. Select the Details tab. 10. Scroll down to, and then select, the Thumbprint field. 11. In the Details window select, and then copy, the thumbprint. 12.
7. If the server is in a workgroup, select all three options in the Profile Settings, and then click Next. 8. Enter a name for the rule, and then click Finish. The new rule appears and is enabled as indicated by a green check box.
Installing the management application Installation on Microsoft Windows OS Complete the following instructions to install BACS: • Installing the BACS management client on a Microsoft Windows operating system (on page 18) • Configuring HTTP on Microsoft operating systems (on page 18) • Configuring HTTPS on Microsoft operating systems (on page 19) • Testing a client WinRM HTTPS/SSL connection (on page 19) Installing the BACS management client on a Microsoft Windows operating system To install the BAC
3. Under Windows Remote Management, select WinRm Client. 4. Under WinRM Client, double-click Trusted Hosts. 5. In the dialog for TrustedHostsList, enter the hostnames of the clients. 6. If all clients are trusted, enter *. 7. Select WinRM Service. 8. Enable Allow Basic Authentication. 9.
• Installing OpenSSL and OpenPegasus (on page 20) • Installing WS-MAN and CimXML on Linux OS (on page 21) • Installing OpenPegasus from Inbox RPM for Red Hat (on page 21) • Installing OpenPegasus from Source for Red Hat and SuSE (on page 21) Downloading and unpacking HP SoftPaq 1. Download, and then unpack the HP SoftPaq to a directory on the target computer. The SoftPaq is a .tgz file named by the SoftPaq Number. 2. Extract the files from the .tgz file: tar -zxvf *.tgz 3.
16. Configure the Linux firewall. For more information, see "Configuring the Linux firewall (on page 24)." 17. Configure HTTPS. For more information, see "Configuring HTTPS on Linux systems (on page 25)." 18. 19. Install the BACS package: rpm –i BACS-x.x.x.rpm When installation is complete, a BACS icon appears on the desktop. For more information about launching BACS, see "Launching the application (on page 29).
Command Details $PATH:$PEGASUS_HOME/bin PATH PEGASUS_ENABLE_CMPI_P True ROVIDER_MANAGER CIM222 PEGASUS_CIM_SCHEMA PEGASUS_PLATFORM PEGASUS_HAS_SSL For Linux 32 bit system: LINUX_IX86_GNU For Linux 64 bit systems: LINUX_X86_64_GNU Optional Set to true for HTTPS support. PEGASUS_ENABLE_PROTOC Optional OL_WSMAN Set to true for WSMAN protocol support. OpenPegasus additional settings The following command are additional OpenPegasus settings: $PEGASUS_HOME needs to be set up in the shell environment.
Starting and stopping the CIM Server To start CIM Server, run cimserver from a command prompt. To stop the CIM Server, run cimserver –s from a command prompt. Check if OpenPegasus is installed properly: cimcli ei -n root/PG_Interop PG_ProviderModule If the OpenPegasus installation is compiled from source, open the PEGASUS_HOME directory to start CIM Server, or CIM Server does not load the repository properly. For ease of use, set PEGASUS_HOME in the .bash_profile file.
Enabling HTTP 1. Start the CIM Server if the CIM Server is not already started. For more information, see "Starting and stopping the CIM Server (on page 23)." 2. (Optional) To set the HTTP port, run the following command: cimconfig -s httpPort=5988 -p The property is not available for Inbox OpenPegasus. 3. 4. Enable an HTTP connection: cimconfig -s enableHttpConnection=true -p Stop and restart the CIM Server: cimserver –s and cimserver Enabling HTTPS 1.
5. Add the protocol in the Protocol field, for example, TCP or UDP. 6. Click Apply. SuSE To open ports in a SuSE firewall: 1. Select Computer→YaST. 2. On the left pane, select Security & Users. 3. On the right pane, double-click Firewall. 4. On the left pane of the firewall dialog box, select Custom Rules. 5. On the right pane, select Add. A dialog box appears. 6. Enter the following information: 7.
For more information, see "Generating a self-signed certificate for Microsoft and Linux servers (on page 14)." 2. Change directories to /etc/ssl/certs. 3. Create a hash value: openssl x509 -noout -hash -in hostname.pem The output looks like the following example: 100940db 4. Create a symbolic link to the hash value: ln -s hostname.pem 100940db.0 5. If the installed OpenSSL version is earlier than 1.0.0d, perform the following steps: a. Build OpenSSL. Be sure that everything is linked statically. b.
To configure namespace security: 1. Start the WMI Control from the command prompt: wmimgmt On Microsoft Windows 9x or NT4 systems that have WMI installed, enter the following command instead: wbemcntl.exe Or, to access the WMI Control and the Security tab, do one of the following: o Right-click on My Computer, and then click Manage. For Microsoft Windows 2008, the Server Manager utility opens. WMI control is located in the left pane.
c. In the Launch Permission dialog box, select any user and group. d. In the Allow column under the corresponding account permissions, select Remote Launch, Remote Activation, and then click OK. For more information, see the Microsoft website (http://msdn.microsoft.com/en-us/library/aa393266%28v=vs.85%29.aspx).
Launching the application Launching the GUI in Microsoft Windows OS To launch the BACS GUI, do one of the following: • From the Program Menu, select Start→All Programs→Broadcom→Broadcom Advanced Control Suite 4. • From the Control Panel, select Start→Control Panel, and then double-click Broadcom Control Suite 4. • From the system tray, click Broadcom Advanced Control Suite 4. BACS might not appear in the Microsoft Windows Server 2008 system tray.
Configuration Configuring preferences When the BACS program is installed, an icon in the Windows taskbar appears. Use the Options window to turn this icon on or off. Enabling or disabling the BACS tray icon 1. From the Tools menu, select Options. 2. Select or clear Enable BACSTray (enabled by default). 3. Click OK. Setting Explorer View refresh time 1. From the Tools menu, select Options. 2. Select Auto to set the Explorer View refresh time to 5 seconds.
6. Type the User name and Password. 7. Select Persist to save the information for this host. The host appears in the Explorer Pane the next time you open BACS, and you do not need to enter the host IP address or host name when connecting to the host. For security reasons, you must enter the User name and Password. 8. Click OK. Managing the host At the host level, you can view host information and configure parameters from the Information and Configuration tabs.
Viewing adapter information Select the network adapter in the Explorer View pane, and then select the Information tab to view adapter-level information. Viewing resource information You can view information about connections and other essential functions for the selected network adapter from the Resources section of the Information tab. The available information depends on the network adapter. • Bus Type is the type of input/output (I/O) interconnect used by the adapter.
• Management Firmware indicates the version installed on the system. • Vendor ID indicates the vendor ID. • Device ID indicates the adapter ID. • Subsystem Vendor ID indicates the subsystem vendor ID. • Subsystem ID indicates the subsystem ID. • External PHY Firmware Version indicates the external PHY firmware version. Configuring adapter parameters Select the network adapter in the Explorer View pane, and then select the Configuration tab to configure adapter-level parameters.
1. Select the Ethernet controller in the object explorer. 2. Select PortX (where X is either 0 or 1) below the adapter in the object explorer. Various components of the port are displayed below the port in the object explorer. 3. Click the plus sign icon next to the port to expand or collapse the tree below. 4. Select Information tab in the Context View Panel on the right side.
o LSO prevents an upper level protocol such as TCP from breaking a large data packet into a series of smaller packets with headers appended to them. o CO allows the TCP/IP/UDP checksums for send and receive traffic to be calculated by the adapter hardware rather than by the host CPU. • LiveLink IP Address is the network address of the LiveLink enabled adapter. • Local Connection identifies the module to which the blade server is attached. • o Chassis SW is the chassis switch module.
• MAC Address is the physical media access control address that is assigned to the adapter by the manufacturer. The physical address is never all 0s. • Permanent MAC Address is the unique hardware address assigned to the network adapter. • Offload Capabilities are capabilities supported by the adapter. This information is only available for certain adapters.
• Frames Rx OK is a count of the frames that were successfully received. This does not include frames received with frame-too-long, frame check sequence (FCS), length, or alignment errors, nor frames lost due to internal MAC sublayer errors. This counter is incremented when the receive status is reported as Receive OK. • Directed Frames Tx is a count of directed data frames that were successfully transmitted.
• Session format error is the number of sessions with errors due to inconsistent fields, reserved fields that are not 0, non-existent LUNs, and so forth. • Sessions failed is the number of failed sessions. Custom statistics Total Offload iSCSI Connections is the total number of offloaded iSCSI connections. Session Statistics The statistics in this area only pertain to the named session. • Session Name is the name used for the session between the initiator and the target.
• MAC Rx w/ no Pause Command enables MAC control frames with no pause command. • MAC Sent X-on indicates that MAC Transmit with X-on is on. • MAC Sent X-off indicates that MAC Transmit with X-on is off. • Large Send Offload Transmit Requests is the number of times the adapter was requested to transmit a packet performing TCP segmentation. • Total Offload TCP Connections is the total number of offloaded TCP connections. • SR-IOV Switch Statistics shows the statistics for SR-IOV switches.
To set the IP address of the iSCSI HBA for iSCSI offload: 1. Click the name of the iSCSI device in the SCSI controller section of the Explorer View pane. 2. To set the IP address, do one of the following: o For IPv4 DHCP and IPv6 DHCP protocols, select Enable to set the IP address dynamically using a DHCP server (not available for iSCSI booted adapters). o For other protocols, select Disable to set the IP address using a static IP address. 3.
CLI commands Configuring with the CLI utility An alternate method to BACS for configuring network adapters is BACSCLI, a utility that enables you to view information and configure network adapters using a console in either a non-interactive command line interface (CLI) mode or an interactive mode. BACSCLI provides information about each network adapter and enables modification of property values. For a complete list of commands and examples, see the BACSCLI ReadMe text file available with the installation.
Support and other resources Before you contact HP Be sure to have the following information available before you call HP: • Active Health System log (HP ProLiant Gen8 or later products) Download and have available an Active Health System log for 3 days before the failure was detected. For more information, see the HP iLO 4 User Guide or HP Intelligent Provisioning User Guide on the HP website (http://www.hp.com/go/ilo/docs).
Acronyms and abbreviations BACS Broadcom Advanced Control Suite BACSCLI Broadcom Advanced Control Suite command line interface BASP Broadcom Advanced Server Program CIM common information model CNA Converged Network Adaptor CO Checksum Offload.
HBA host bus adapter IQN iSCSI qualified name iSCSI Internet Small Computer System Interface iSNS Internet Storage Name Service LSO large send offload LUN logical unit number MAC Media Access Control MTU maximum transmission unit NDIS network driver interface specification PCI payment card industry PCIe Peripheral Component Interconnect Express PDU protocol data unit SDDL Security Descriptor Definition Language SLES SUSE Linux Enterprise Server Acronyms and abbreviations 44
SR-IOV Single root I/O Virtualization SSL Secure Sockets Layer TOE TCP/IP Offload Engine UDP User Datagram Protocol VF SR-IOV virtual function VF virtual bus driver VLAN virtual local-area network WinRM Windows Remote Management WMI Windows Management Interface WS-MAN Web Service Management Acronyms and abbreviations 45
Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index A D adapter settings 32, 33 additional configuration 16 DCOM, granting remote launch and activate permissions 27 destination site 7 DHCP server 34 discovery protocols 5, 6, 7, 30, 31, 33 drivers 35 B BACS communication protocols 8 BACS hardware requirements 8 BACS installation 8, 18 BACS installation procedure 12 BACS interface on Microsoft systems 5 BACS introduction 8, 9 BACS management application, installing 25 BACS management application, uninstalling 25 BACS software requirements 8 BACS, clo
menu bar 6 Microsoft iSCSI initiator software 31, 36 Microsoft Windows Firewall 16 Microsoft Windows Firewall, modifying 16 Microsoft Windows Server 2008 41 Microsoft Windows Server 2012 41 WMI, special configuration on other Microsoft systems 28 O OpenPegasus variables 21 OpenPegasus, additional settings 22 OpenPegasus, building and installing 22 OpenPegasus, configuring on a server 23 OpenPegasus, installing from Inbox RPM for Red Hat 21 OpenPegasus, installing from source for Red Hat and SuSE 21 OpenSS
