HPE BladeServer BL460c FCoE on RedHat Linux

A quick procedural reference to configure HPE BL460c bladeserver with FlexFabric Virtual Connect. RedHat Linux doesn’t present the Fiber Channel FlexNIC as Fiber Channel ports. These ports (LOM1b and LOM2b) are presented as NIC ports with default MacAddresses. In order to configure the Fiber Channel ports, FCoE configuration needs to be enabled.

Two configuration changes are required from default configuration –

1. /etc/sysconfig/network-scripts/ifcfg-enoXX
2. /etc/fcoe/enoXX

In order to configure the correct network adapters need to figure out which adapters are configured for Ethernet and which are for Fiber Channel.

Look through the Virtual Connect to determine the configured Ethernet adapters –

From Virtual Connect Command Line Interface (CLI via SSH to Virtual Connect Manager) –
VC –> show profile C7000_Bay1
(Replace the C7000_Bay1 with the server profile)

Sample output:
Ethernet Network Connections
Port Network Status PXE/IP Boot MAC Address Allocated Name Order Speed (min-max)
1 Multiple OK UseBIOS/Auto 00-17-A4-73-00-30 3Gb-10Gb Network
2 Multiple OK UseBIOS/Auto 00-17-A4-73-00-32 3Gb-10Gb Network
3 Multiple OK UseBIOS/Auto 00-17-A4-73-00-34 3Gb-10Gb Network
4 Multiple OK UseBIOS/Auto 00-17-A4-73-00-36 3Gb-10Gb Network

FCoE Connections
Port Connected Name Type Status Allocated WWPN MAC Address To Bay Speed (min-max)
1 1 Fabric SAN OK 4Gb-8Gb 50:06:0B:00: 00-17-A4-75–A 00:C2:65:04 00-0E
2 2 Fabric SAN OK 4Gb-8Gb 50:06:0B:00: 00-17-A4-75–B 00:C2:65:06 00-0F

Not that FCoE connections have WWN as well as the MAC Addresses for each port. Note down the MAC Addresses and search for them in Linux –

On the RedHat server please ensure that FCoE util is loaded. Verify the install with following command –
# yum list | grep -i fcoe
fcoe-utils.x86_64 1.0.32-1.el7 @anaconda/7.5

If not install it using following command –
# yum install fcoe-utils.x86_64

Now, configure the FCoE on RedHat server

Sample RedHat Linux commands –
# ip addr
4: eno31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:17:a4:75:00:0e brd ff:ff:ff:ff:ff:ff
5: eno32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:17:a4:75:00:0f brd ff:ff:ff:ff:ff:ff

There will be many adapters but in this case eno31 and eno32 are matching the MAC Addresses with the one we noted down in Virutal Connect output.

Once identified, configure these two adapters.

1. Configure the two NIC adapters in /etc/sysconfig/network-scripts/

# TYPE=Ethernet
# IPV6INIT=yes
# IPV6_ADDR_GEN_MODE=stable-privacy
# NAME=eno31
Most importantly, ONBOOT=yes will ensure that adapter is set to FCoE adapters at each boot.

2. Configure both NICs in /etc/fcoe

## Type: yes/no
## Default: no
# Enable/Disable FCoE service at the Ethernet port
# Normally set to “yes”

## Type: yes/no
## Default: no
# Indicate if DCB service is required at the Ethernet port
# Normally set to “yes”

## Type: yes/no
## Default: no
# Indicate if VLAN discovery should be handled by fcoemon
# Normally set to “yes”

## Type: fabric/vn2vn
## Default: fabric
# Indicate the mode of the FCoE operation, either fabric or vn2vn
# Normally set to “fabric”

## Type: yes/no
## Default: no
# Indicate whether to run a FIP responder for VLAN discovery in vn2vn mode
Note that MODE=”fabric” and DCB_REQUIRED=”no” are the most important settings and the file name should be matching the one we set in /etc/sysconfig/network-scripts/ifcfg-eno31 and eno32 files.

That’s it, the FCoE adapters should be enabled and they should be logged in to SAN Switches.


Why HPE invested in Synergy, “The Composable Infrastructure”?

HPE is positioning Synergy “The Composable Infrastructure” to slowly phaseout c7000 “BladeSystem” that was announced in 2006 and remained unmatchable since then. Synergy introduces industry’s first Composable Infrastructure” that echos HPE’s modern IT slogan “Hybrid IT Transformation” and replaces traditional c7000. Recently, many of the c7000 customers are asking questions around HPE’s new product line announcement – Synergy BladeSystem – “Why do we need Synergy”?


Answer to the question lies in the question that HPE asked themselves before investing huge efforts in research and development of Synergy. Why HPE needed to come up with new product line when c7000 was keeping up with the development of new SAN, Network, SAS, Virtual Connect, Flex-Fabric technologies? Since its launch, c7000 BladeSystems adapted to most of the new technologies with a minor firmware code upgrade and delivered unprecedented performance and uptime to its customers. Still, HPE decided to invest in new product to deliver an unmatchable experience to the customers. Undoubtedly, HPE’s efforts paid off with Synergy that simplifies the environment for a quicker deployment Synergy poses several benefits to IT –

  • Industry demand is to move forward with Composable and Synergy is fully Composable.
  • Quicker to deploy with least components configuration.
  • It is Simple to deploy and manage.
  • Costs much less to upgrade than any other product in market.
  • Interconnected upgrade options are integrated as local resources with the introduction of re-timers in satellite fabric modules.

While developing the Synergy platform, HPE kept in mind that be it a traditional customer with simple applications (web hosting, fileshares, simple virtualized environment, database and home grown or legacy applications) or a customer with new breed of complex applications and services (DevOps, containers, managed services, hosting), HPE ensures that the “Composable Infrastructure” will be able to meet the requirements and demands of modern IT managers and administrators.

Composable infrastructure offers –
– Composable Frame
– Composable Management
– Composable Computer
– Composable Storage
– Composable Fabric

Composable Infrastructure benefits from its underlying components –
– Fluid Resource Pool
– Software-defined Intelligence
– Unified Programming Interface

HPE Synergy significantly reduces number of components on a purchase order and that is made possible with the introduction of new interconnect modules and compute nodes. With new generation compute modules, Synergy offers infrastructure to any size environment and makes it future proof with a promise to accommodate future technologies. While HPE is yet to release more information on its future product line it is a very good guess to assume that HPE’s latest undertaken projects will be first take option on Synergy, such as – Photonics, The Machine, Simplivity, More variants Storage and Fabric interconnect modules.

(More information can be found at http://www.hpe.com/info/synergy )
Posted in HPE

VMware Update Manager Installation with SQL Express (.Net framework3.5)

Installing VMware Update Manager (version 6.5) from the same installation ISO as vCenter there are two options; install on existing database (typical when VUM is installed on a vCenter server) or to install with embedded SQL Express. The Embedded SQL Express option is only available when Auto-run is selected from the installation ISO.

Graphic – Autoplay from ISO

2017-03-25 20.38.47

Graphic – Autorun from root folder

2017-03-25 20.40.29

If you run the VMware Update Manager installer (.exe or .msi) from the “Update Manager” directory, option for Embedded SQL Express is not there and a message is displayed like this –

Graphic – .EXE from the folder

2017-03-25 21.22.14

Graphic – VMware embedded db unavailable from autorun2017-03-25 20.52.41

Remeber, VUM uses 64-bit DSN that needs to be set if selected to use existing database. Once the database option is selected and passed the screen, VUM installs .NET framework 3.5 as pre-requisite. There are two problems encountered while installing the .NET framework 3.5. First, VUM installer tries to install the .NET framework 3.5 and the installation fails. If this happens you may try to enable the .NET framework 3.5 from the control panel –

Graphic – enable .NET framwork 3.5 from server manager console2017-03-25 21.29.38

or, another option is to use CLI command (with administrator privileges). DISM expample –

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

or (if you have source mounted as D:\ )

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:D:\sources\sxs /LimitAccess

Graphic – install-net35-disminstall-net35-dism

Troubleshooting: The .NET framework installation may fail if installation media is missing or Windows Server Update Services (WSUS) can’t be reached.

Feature installation gets error

Graphic – .NET framework installation error using server managerdotnet_feature_install_faial

DISM installation stuck at 66.5% and subsequently fails with error code 0x800F0906

Graphic – .NET framework installation error using DISMinstall-net35-dism-error

This error is because Windows host isn’t allowed to download online updates (this is separate from Windows Update). To solve this change the group policy settings to allow optional component installation to contact Windows update.

Run the gpedit.msc and navigate to

Computer Configuration > Administrative Templates > System > 

and open the “Specify settings for optional components and component repair” by double-click and then check the box “enable” and “Contact Windows update …”

Graphic – gpedit navigation2017-03-24 16.28.03

Graphic – enable windows update2017-03-25 21.14.46

All is well from here. Run the DISM CLI and .NET framework 3.5 will be installed online without requiring Windows source DVD.

First blog post

I am excited to start this blog to write about various infrastructure configurations that I come across. I am an IT consultant and deal with various configuration and issues, I will post most interesting facts that I encounter on typical configurations involving HPE, EMC, VMware, Veeam, Microsoft and Brocade.