Greetings. I am a newbie to HP C7K. I have the following configuration:

1. Single HP C7K. With six BL460c blades. In bay 1-3 and bay 9-11.

2. VC Flex-10/10D in bay 1 & 2. VC1 has 2 ports in LAG to switch 1 and VC2 has 2 in LAG to switch 2.

I sometimes see that "Domain Status" indicates that "Stacking Links" degraded. Trying to narrow it down. I have three probable candidates:

1. When I power on bays in particular order? Or change server profile config without un-assigning (only powered off: that's allowed right?)

2. When the OS bonding config is not complete/correct.

3. VC detecting a loop in my configuration?

Am I even making sense? Where can I read more about how the internal stacking links work? The X11-X14 are essentially uplink ports, right? In one LAG to the next bay peer, in my case?

->show stackinglink                 

Connection Status : Failed
Redundancy Status : Degraded

Stacking Mode : Full

No stacking links to display

Earlier:

->show stackinglink 

Connection Status : OK
Redundancy Status : OK

Stacking Mode : Full

===========================================
Link  Speed  Connected From  Connected To  
===========================================
1     10Gb   enc0:1:X11      enc0:2:X11    
2     10Gb   enc0:1:X12      enc0:2:X12    
3     10Gb   enc0:1:X13      enc0:2:X13    
4     10Gb   enc0:1:X14      enc0:2:X14    

I am not sure, but I think--amongst the things I have tried--VC reset fixes this.

Thanks in advance

Hi,

we have following setup:

OAs: FW 4.70 / VCs: 4.50

each VirtualConnect w/ 2 uplinks (x1/x2) - tunneled to ESX hosts and 1 uplink (x3), where the networks are tagged within VC. All uplinks are trunks with all available VLANs (i.e. 300-399, 400-499).

Tunneling (x1/x2 LACP) to ESX and tagging at dvSwitch works perfect. Networks created in VC using trunk of x3 have been working well for years, however now we found that some 4xx VLANs are not able to communicate with host outside C7000. Within C7000, host are able to communicate with each other over the 'faulty' VLAN.

We checked the network part already without any issue. We rebooted both VCs already without any success.

We have 12 identical C7000s with similar setup and only one has issues.

Any idea???

/br

Albert

Is it possible to achieve up to 4-HBA in a BL460c Gen8 with FlexFabric? The 554FLB provides two ports but I'm looking at wanting an additional 2 ports. If I add another 554FLB card will it use the FlexFabric modules in the BAY 1 & 2 or will I have to add additional FlexFabric modules to Bay 3 & 4?

Hi,

I have a HP c7000 blade enclosure with couple of BL460c Gen8 blades, and two HP VC Flex-10/10D interconnect modules. In the blades I have OpenStack Pike installed with latest CentOS 7 as host operating system and neutron is configured to use linux bridge to connect VMs (virtual machines) to the external world. The flow is like below:

external switch<-->HP virtual connect<-->[eno1 bridge tap]<-->[eth0 cirrosVM]

The eno1 is the first physical interface CentOS 7 sees in the BL460c blades, and the bridge is used to connect the cirrosVM to the outside network. The tap interface is used by the neutron to bridge toghether the eth0 interface in the cirrosVM and the eno1 interface in the CentOS.

The problem is the following:

When the cirrosVM wants to access any IP address in the external network, an arp request is sent out on the eth0 interface, and enters the linux bridge on the tap interface. In its forwarding table, the bridge assigns the eth0 mac address to the tap interface, and sends the arp request out on the eno1 interface. Now, some device on the left side of the bridge (I am sure the HP virtual connect does that), broadcasts that arp requests back, therefore the same arp request enters back the bridge on the eno1 interface, and the bridge assigns the source mac address of the arp request (which is still the eth0 mac address) to the eno1 port in the forwarding table. This behaivious, with the eth0 mac address wrongly assigned to the eno1 port in the bridge (while it should be assigned to the tap interface), causes all IP communication to stop working for that IP address.

So the question is: why does the HP virtual connect sends back the arp request broadcast? Is there a feature in the HP virtual connect that could disable this behaiviour? Or is this a bug in the HP virtual connect?

In the flow above, the external switch (HP ProCurve 2848) is used as a router as well, therefore the layer 2 broadcast domain is terminated in that switch. I am sure the external switch does not cause this behaiviour, since I have used port monitoring to trace, and I see the arp request arriving, but not going out again.

However, if I use tcpdump and trace on the eno1 interface, I see the arp request going out and comming back in. If I use the bridge monitor command, I can see the bridge assigning the eth0 mac address to the tap interface first (when the arp request goes out), then to the eno1 interface when the arp request comes back in.

Initially instead of the eno1 interface, I have bonded eno1 and eno2 toghether, therefore both Flex-10/10D switch modules where in use. I thought this arp request behaiviour might be caused by some loop in the Virtual Connect, however even now, when only eno1 is in use (therefore no loop), the same issue happens.

The workaround I have found is to convert the bridge to a hub, by setting ageing to 0 (brctl setageing br-name 0). In this way, the bridge floods all packets on all attached bridge interfaces (eno1 and tap interface), and everything starts working. However, this is not a long term solution.

I am wondering if anybody else has seen this issue, and if there is any solution for it.

Many thanks in advance,

Adrian

Please join us for the HPE Servers Expert Day on January 30 and 31.

More detailed information is available here:  http://hpe.to/6003DHgE9 

I have a small but annoying issue with a BladeSystem c7000, OA version is 4.01.

In the enclosure are ProLiant BL460c Gen8 blades with HP FlexFabric 10Gb 2-port 554FLB Adapters.

In the properties of each NIC, I see that 3 LOMs have been defined, one NIC, one FCoE HBA & one iSCSI NIC.

My issue is that I must enable software iSCSI in Vmware 5.5 and would like to disable both FCoE & iSCSI. To do this, I should use the Virtual Connect Manager tab of the OA, but the link is missing. 

If I check using VCSU, I don't get an IP for VC, only for OA & the 6120XG blade switch.

Any idea on how to reconfigure the LOM to be NIC only ?

Thanks in advance,

Eric

Hello community.

I have a VMware ESXi cluster running on multipl e vlade servers. These are all configured similarly.

lom1:a and lom2:a vm network

lom1:c and lom2:c mgmt/vmotion

lom1:d and lom2:d iscsi

lom1:b and lom2:b Assigned to FCoE , however we will repurpose these into another shared uplink set and this will configure similar to lom1:a and lom2:a

My concern is that once I power down the blades and remove the definition for lom1:b and lom2:b the vmnics presented to the ESXi hosts may becone reordered and jack the configuration. For example lom1:b and lom2:b may be assigned to the mgmt/vmotion network where lom1:c and lom2:c currently are. This concern was raised because on a test blade when I unhide the unused flexnics I get the warning in the screen shot about possible reordering.

Can anyone confirm. If I am not clear I can elaborate. I did not setup the FCoE unused definition so stating that this was a bad practice is not lost on me.. but will not hep me at this time,

Hello,

Try to pool out VC mac tables and save to doc via ssh
command show interconnect-mac-table  enc0:1 won't work

Any suggestion which one should I use?

Thanks

Hi Folks,

I have 2 hp C7000 enclosures that contain each 2 fc modules "HP 8/24c SAN switch pwr pk+ bladesystem c-Class"

enclosure 1 is working fine with this module

but enclosure 2 seems to not be able to use the fc moduls, because a lot of FC options are missing

. it's the first time I try to use it so I'm certainly missing something.

When I go to the "servers profiles" on enclosure 2, I don't have an "FC HBA Connections" section, like we can see on the "capture1" (coming from  enclosure 1)

and even on the start page of the VC web interface, a lot of FC options are missing (see capture 2 coming from enclosure 1, and capture 3 coming from enclosure 2)

For the moment I didn't plug any FC in the module of the enclosure 2, not sure if this is the reason...

the status of fc modules on enclosure 2 seems good (all is green), and I already try to restart them.

Thx a lot in advance

Hello,

We try to add new VLANs via cli to a Server Profile. Is this even possible?
Via gui we make this by Connections -> Server Profiles -> Ethernet Adapter Connections -> Multiple Networks... Edit -> and drag and drop the new vlan.
Is this also possible via an ssh Connection? And how is the right command to do that?
We have the VLANs for two Bays with the same VLAN ID.
We have two entries with the Name Multiple Networks in Ethernet Adapter connections, so we can't distinguish the Networks by Name.

In the Forums we found something like this
vcemcli -add server-port-map -profilename TestProfile -portnumber 3 -network Backup-VLAN-2003A -vlanid 2003 
But we are not sure if this makes what we want.

We tried this documentation https://support.hpe.com/hpsc/doc/public/display?docId=c04731372  on page 103 and found the following command
->add server-port-map-range MyProfile:1 UplinkSet=MyUplinkSet1 VLanIds=101-124,214
Adds multiple networks to a server-port-map

We hope our explanation is understandable

Some help would be gladly appreciated

Hello,

I bought two VC 10/10D refurbished modules. Put them into 1 and 2 bays. When I try to connect to 1 bay module - I have a wizard. But when I trying to connect to 2 bay - I have "The active Virtual Connect Manager is not at this IP address currently. We will continue to check every 30 seconds. If you expect the active Virtual Connect Manager at this IP address, please wait."

When I tried to connect throught console I get "Virtual Connect Manager not found at this IP address. The location of Virtual Connect Manager has not yet been established, please wait for initialization to complete."

When I tried to connect throught ssh I get "Virtual Connect Manager not found at this IP address. The location of Virtual Connect Manager has not yet been established, please wait for initialization to complete."

I tried move them to another bays but it didn't helped.

Can anybody help me?

I've noticed an issue with some of my virtual machines running on a particular host after that host was fully patched on Windows and HPE drivers/firmware from the 8.1 HPE service pack.

What would happen is VM's would get stuck in a stopping state for some reason. The host would all of a sudden try to move all the VM's from it but majority of them would get completely stuck which results in my having to hard reboot the server.

At first I thought this may have been a Windows update issue with a bad patch, but after looking closer I think this is an issue with the 554FLB adapter we are using:

2/12/2018:

The network interface "Emulex OneConnect 554FLB, Ethernet NDIS Miniport Driver" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets.
Reason: The network driver did not respond to an OID request in a timely fashion.
This network interface has reset 1 time(s) since it was last initialized.

2/1/2018:

The network interface "Emulex OneConnect 554FLB, Ethernet NDIS Miniport Driver" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets.
Reason: The network driver did not respond to an OID request in a timely fashion.
This network interface has reset 4 time(s) since it was last initialized.

According to the event viewer, Hyper-V was running fine with no issues until this warning occurred. When this warning occurred it followed with an error for each VM on the host:

A component on the server did not respond in a timely fashion. This caused the cluster resource 'SCVMM ********************' (resource type 'Virtual Machine', DLL 'vmclusres.dll') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.

The firmware for the 554FLB is 11.1.183.23 and the driver on Server 2016 Datacenter is 11.1.196.4

Note: This is the only node in the cluster that is up to date with HPE drivers/firmware and Windows patches so we could test it first. This is also the only node having this issue.

Hello guys,

I'm new to HPE world and want to know what a Virtual Connect is.

Is it a switch?  A pass thru?

Do I necessarily need Top of rack switch if I want my blade servers to communicate with the external LAN through the virtual connect.

Thank you very much for your answer.

Hi there,

I got two HP Virtual Connect 8Gb 24-Port FC Modules which seam to have a config / password on them diffrent then the default settings printed on them. So I research how to reset them but it seams that you can only reset the Enet Modules since the SAN Modules are non-intelligent. But on the Virtual Connect Manager I can not do anything with the modules as you can see here: 
I tried to press the reset button on the modules for 10 seconds. Does not reset them. Also vcsu tells me it can not communicate with them: 
I also tried the brocade way to reset them. Serial connection thru SSH on the Onboard Administrator. It works. I can get into it. Can even run the /usr/bin/passwordsdefault but since it is VC i guess the VC layer is on top of the brocade stuff...

Any Ideas?

Thanks a lot guys,

Regards,
Yves

Hi,

We have a C7000 chassis with a couple of HP VC Flex-10/10D Modules happily linked up to the corporate network via fibre using a couple of 10GB SFP-SR connections.

As we do with 5 other identical chassis.

We have 16 blades (BL460c G9) running ESXi 5.5 but the networking on each blade comes up as disconnected.

When I look in Virtual Connect Manager -> Chassis Name -> Interconnect Bays -> VC Flex-10/10D -> Server Ports the status of every single port is "Administrativley Disabled"

I have searched the internet for answers on this but there isn't much. I have firmware upgraded and downgraded the C7000, VC-Flex cards and even an individual blade but they status remains the same.

Picture attached.

Anyone have any ideas?

Thanks,

Dave

I have: HPE BladeSystem Enclosure C7000 with Interconnect Bay port 1 connected to SAN1 and port 2 connected to SAN2.

Is it possible to connect HPE ProLiant BL460c Gen9 Server Blade to both SAN Fabrics: SAN1 and SAN2 with one Mezzanine Card? If not, how I could do it?

We recently deployed a G3 c7000 enclosure with VC FlexFabric-20/40 F8 modules in Interconnect Bays 1 & 2; the OA modules and VC modules are at the latest firmware release.  We've got 10GbE DACs connecting Port X1 in either module to Cisco Nexus 5672UP-16G switches for network and 8Gb FC SFP+ connecting Port X8 to 8Gb FC ports via OM3 in the same Nexus switches.

We've got network connectivity in either module, but the FC ports are showing a status of "NOT-LOGGED-IN".  The documentation indicates that "External FC Port Type should be configured as Node port s (N_Port), 2Gb, 4Gb or 8Gb auto- negotiating SFP ports".

I haven't yet run ISL connections between the Nexus switches and our SAN switches, so it might just be that, but thought I would check with the folks in the field if they've configured similarly.  Thank you.

Hello,

I am new on Virtual Connect Technology and I turn around a trouble without find the solution...

I have added a new blade, BL 460c gen9 (same models we have already) with HP FlexFabric 10Gb 2-port 536FLB Adapter.
I have created a server profile on Virtual Connect but the status stay "not logged" without any uplink port.
I have downgraded the firmware & drivers of the fiber card like another Blade which is OK... but same result...

I had not make the zoning on Brocade, I did'nt see the new devices, (and yes NPIV is enabled).
On esx I see the 2 fcoe nic but without all informations :

vmhba32
Source MAC: d0:67:26:ac:d4:71
FCF MAC: 00:00:00:00:00:00
VNPort MAC: 00:00:00:00:00:00
Physical NIC: vmnic2
User Priority: 3
VLAN id: 0
VN2VN Mode Enabled: true

vmhba33
Source MAC: d0:67:26:ac:d4:79
FCF MAC: 00:00:00:00:00:00
VNPort MAC: 00:00:00:00:00:00
Physical NIC: vmnic3
User Priority: 3
VLAN id: 0
VN2VN Mode Enabled: true

If someone could help me ?? 

Thank in advance,

Best regards

We are working on a plan to resolve the Spectre/Meltdown issue throughout our environment and the question has been asked about the impact on Virtual Connect when we start updating the servers. Does anyone have any information regarding this? 

Thank you.

We have 2 x c7000 Enclourses, just bought 2 flex-10/10d virtual connects for each enclousre.

We have EMC VNX SAN with no switches, controllers only.

Need to connect each virtual connect to each controller directly.

How to? kindly explain.

Thanks