Grey page while trying to edit options in VCM

September 5, 2017, 6:06 am

≪ Previous: Flex-10/10D: bay1-2 stacking links degraded

On my manager I cannot edit any option as everything becomes grey if I click on them. On this exemple, I am trying to add a Network to my erver profile and it just becomes completely grey. I can still go back to the menu and start over but it always stops at the same places. I can still connect and do certain things, but the moment I want to edit anything it just freezes like this.

If anyone as an idea why it does this and/or how to stop it from doing it would be great.

EDIT: I was able to continue working (somewhat) by using TAB. I was able to change some things and save them even though I could not do it with my mouse.

↧

NPAR NICs show as disconnected

September 20, 2017, 4:28 am

≫ Next: NPAR NIC Disconnected in ESXi 6.5

≪ Previous: Grey page while trying to edit options in VCM

Hi,

New to the forums and to Virtual Connect and already, on a completly new environment being built, I have an issue that I cannot find clarity on.

So, what we have is the following:

- C7000 Enclsoure

- Virtual Connect Swicthes in bays 1, 2 + 5 , 6

- BL460C Gen 9 with 1 x 536FLB (LOM) and 1 x 534M in Mez Slot 2 - both adapters are dual port

I'm looking to use NPAR to define a number of adapters that my ESXi 6.5 hosts will see as different vmnics, so for example:

LOM 1a = vmnic0

LOM 2a = vmnic1

MEZ 1a = vmnic2

MEZ 2a = vmnic3

LOM 1b = vmnic4

LOM 2b = vmnic5

MEZ 1b = vmnic6

MEZ 2b = vmnic7

From what I can tell, all firmware/drivers are current.

The problem comes after applying the Server Profile and rebooting, there are times that the ESXi host shows some of the NICs as disconnected. I found this link http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04942515 which describes our issue, but it is dated Jan 2016 and I have not been able to find anything newer to say that the issue has been resolved.

I guess others have seen this in the past, but is there an actual resolution to the problem as Jan 2016 seems a long time to go without a fix.

Thanks in advance

Nikrik

↧

NPAR NIC Disconnected in ESXi 6.5

September 20, 2017, 4:39 am

≫ Next: After firmware upgrade, VC-FC 8GB-20-port Module degraded

≪ Previous: NPAR NICs show as disconnected

Hi,

Not only am I new to the forums but I'm also new to Virtual Connect.

Currently I'm in the process of designing/deploying a new environment which consists of:

- C7000 enclosures
- Virtual COnnect swicthes in bays 1, 2 + 5, 6
- BL460c Gen 9 Blades with 1 x 536FLB (LOM) and 1 x 534M in Mez slot 2 (both dual port
- All firmware/drivers deployed from the latest support packs

I define the following NPARs in the server profile:

LOM 1a - vmnic0
LOM 2a - vminc1
MEZ 1a - vmnic2
MEZ 2a - vmnic3
LOM 1b - vmnic4
LOM 2b - vminc5
MEZ 1b - vmnic6
MEZ 2b - vmnic7

That works and the ESXi 6.5 hosts see all the nic's that Virtual Connect is presenting to the blade. The problem is that more often than not, a number of the nic's show as disconnected in ESXi. We did find this link from Jan 2016 http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04942515 (describes our issue perfectly) but I have not been able to find anything since that states the issue has been resolved.

Is anyone else seeing this with newly deployed kit??? Is there something I'm not thinking about when defining the NPAR NICs???

Thanks in advance

nikrik

↧

After firmware upgrade, VC-FC 8GB-20-port Module degraded

October 2, 2017, 9:49 am

≫ Next: Two C7000 chassis stacking pro's/cons

≪ Previous: NPAR NIC Disconnected in ESXi 6.5

Hi everyone.

Over the weekend, I upgraded the firmware on our HP OA, including the VC firmware. When it was completed, only one of the two VC-FC modules had been upgraded. The other shows as incompatible and nothing I've tried will get it to accept the newest firmware. I couldn't find any older versions on HP's web site, and I've tried upgrading from OA, VCSU and HPSUM.

As an added note, even though I fed VCSU an account with all privilleges, it said I didn't have firmware upgrade permissions. I even tried the Administrator account with the same results.

Any idea how I can get this module up and running again?

Thanks in advance for any suggestions.

Derek

↧

Two C7000 chassis stacking pro's/cons

October 5, 2017, 8:31 am

≫ Next: HPE BladeSystem c-Class Virtual Connect Firmware 4.61 - where are the Release Notes?

≪ Previous: After firmware upgrade, VC-FC 8GB-20-port Module degraded

Hi all,

We have two c7000 chassis with a pair of 10/10D modules and a pair 16gb 24port Fc modules in each chassis all fully populated with SFP's to used for VMware ESXi.

For the 10/10D modules is there any advantage of me using the VC domain stacking (apart from centralised management) and is there a limit on the number of stacking cables I can run (could I run 4 per module between the chassis' and the remaining 6 to uplink) or am I best running all the connections as uplinks to the core switches for throughput?

Any replies appreciated, thanks in advance!

↧

HPE BladeSystem c-Class Virtual Connect Firmware 4.61 - where are the Release Notes?

October 5, 2017, 1:33 pm

≫ Next: c7000/virtual connect Net. connect issue - only getting ip to one server in my bladecenter

≪ Previous: Two C7000 chassis stacking pro's/cons

On September 12, version 4.61 of the Virtual Connect firmware was released, it can be downloaded here:

https://h20566.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=7271228&swItemId=MTX_83557b0e132046f7811a51a8d1&swEnvOid=4183#tab4

The Release Notes tab advises that "The 4.61 version of HPE Virtual Connect Release Notes can be found in the following URL: http://www.hpe.com/info/vc/manuals

but when I navigate to the URL I am redirected to the Hewlett Packard Enterprise Information Library here:

http://h17007.www1.hpe.com/us/en/enterprise/servers/solutions/info-library/index.aspx?cat=bladesystem&subcat=vc

and there is absolutely nothing there related to version 4.61. There is documentation for the 4.60 release in July 2017, but nothing so far as I can see for 4.61. Does anyone know where I can view the VC 4.61 release notes?

↧

c7000/virtual connect Net. connect issue - only getting ip to one server in my bladecenter

October 6, 2017, 1:24 am

≫ Next: VC switch Power redundancy

≪ Previous: HPE BladeSystem c-Class Virtual Connect Firmware 4.61 - where are the Release Notes?

Setup:

1 - HP Bladecenter C7000

9 - bl465 g7 and bl685 g7 blades w/ standard dual emulex 10gb flexnics

1 - HP 1/10gb VC-Enet Module

I am running this enclosure from my home. So I am using a cablemodem/router from my cable company with a small netgear gigbit unmanaged switch in between. I have network cables plugged into the first 2 ports on the Interconnect card.

ive set up virtual connect manager to the best of my knowledge. I am able to get an ip just fine on my first blade that is running windows server 2016. My second blade running a linux live cd w/ correct nic drivers installed just wont pull an IPv4 address. I just show 100% dropped Rx packets uder ifconfig.

Ultimately What I am wanting set up is a fully populated blade center. The first server will house a hard drive and a pxe server and I want to network boot a live cd to ram (diskless) for the other 15 servers.

Any help would be greatly appreciated, I have been fighting with this for several days and I need to get this setup. I am not sure if maybe I need a better switch or router?

Thanks in advance

↧

VC switch Power redundancy

October 4, 2017, 5:49 am

≫ Next: Flex-10 VC Ethernet snmp v3

≪ Previous: c7000/virtual connect Net. connect issue - only getting ip to one server in my bladecenter

There are two VC switch.

My VC-SW-1 is connect to HP-sw-1 and VC-SW-2 is connect to HP-sw-2.

Now when I poweroff the one of the VC-sw from OnBoard Administrator GUI my blades become unreachable.

I have enabled smart links for Ethernet Network as well as Associated Network of Shared Uplinks.

Kindly, share your expirence, if there is something I missed to enable to make the VC-Switches redundant.

↧

Flex-10 VC Ethernet snmp v3

October 6, 2017, 7:15 am

≫ Next: Gen9 blades and VC Mgr Major error 6030 - Profile Pending

≪ Previous: VC switch Power redundancy

I have two flex-10 VC switches in a c7000. I have a snmp v3 user set up on them. On 20 September, I was able to run an snmp query and see the status of the external ports. Today, when I try, I get "invalid user." I've logged back in and checked. The setup looks correct. Any ideas on why it is not responding to a valid snmp query it did just a short time ago? Any suggestions on how to troubleshoot?

↧

Gen9 blades and VC Mgr Major error 6030 - Profile Pending

October 9, 2017, 1:34 pm

≫ Next: Is it possible to disable ssh login in HPE Virtual connect FlexFabric 10G/24 Module

≪ Previous: Flex-10 VC Ethernet snmp v3

Can anyone share knowledge of the root cause(s) of the VC Manager Major error 6030 - "Profile could not be assigned to powered up server". I got bit by this recently while doing Virtual Connect firmware upgrades (HP VC Flex-10/10D Module - firmware 4.45 to 4.50) and several servers dropped off the network after the interconnect modules reset. Reviewing the VC Manager system log shows 6030 Major error - while the VCSU log doesn't indicate any issues with the firmware upgrade itself. Power-cycling the affected servers brings them back on the network, but a firmware upgrade on the interconnect modules should be non-impacting to the servers if the server profiles provide redundant network ports and the server O/S properly handles the temporary link loss on each port.

-----------------------------------------------------------------------
Record    : 3136
Date/Time : 2017-10-06 01:04:26-04:00
Info      : PRO:ServerProfileBay10:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 10
-----------------------------------------------------------------------
Record    : 3137
Date/Time : 2017-10-06 01:04:29-04:00
Info      : PRO:ServerProfileBay11:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 11
-----------------------------------------------------------------------
Record    : 3138
Date/Time : 2017-10-06 01:04:32-04:00
Info      : PRO:ServerProfileBay12:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 12
-----------------------------------------------------------------------
Record    : 3139
Date/Time : 2017-10-06 01:04:34-04:00
Info      : PRO:ServerProfileBay15:6030:Major
Message   : Profile could not be assigned to powered up server : Bay 15
-----------------------------------------------------------------------

↧

Is it possible to disable ssh login in HPE Virtual connect FlexFabric 10G/24 Module

October 14, 2017, 9:39 pm

≫ Next: how to fix SSL Certificate Signed Using Weak Hashing Algorithm in Virtual connect Flexfabric 10G/24

≪ Previous: Gen9 blades and VC Mgr Major error 6030 - Profile Pending

Hi All,

i have 4 HPE Virtual connect FlexFabric 10G/24 Module's in my environment , i have patched the latest VC firmware 4.60 to fix SSH Server CBC Mode Ciphers Enabled but it fixes only 3des-cbc,blowfish-cbc and rest of the things are not fixed
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-cbc@lysator.liu.se
cast128-cbc
Here is my questions
1. is there any ssh configuration file in VC to disable the above encryption algorithms
2. if there is no ssh configuration file in VC is it possible to disable ssh login in VC
It would be highly appreciated if you could help me on this.
Thanks and Regards
Vinothsaran

↧

how to fix SSL Certificate Signed Using Weak Hashing Algorithm in Virtual connect Flexfabric 10G/24

October 14, 2017, 9:46 pm

≫ Next: HP Virtual Connect 4Gb FC Module (409513-B22) "No communication" error - Enclosure degraded status

≪ Previous: Is it possible to disable ssh login in HPE Virtual connect FlexFabric 10G/24 Module

Hi All,

Here is my question regarding SSL certificate in VC flex fabric 10g/24 module

1. is it possible to create self signed cerificate for VC

2. if it possible to create the self signed certificate with strong hashing algorithm

3. what are the steps to be done before and after importing the self signed certificate in VC

Thanks in advacnce for your help

Regards

Vinoth

↧

HP Virtual Connect 4Gb FC Module (409513-B22) "No communication" error - Enclosure degraded status

October 16, 2017, 7:28 am

≫ Next: Flash update breaks IE when accessing VC

≪ Previous: how to fix SSL Certificate Signed Using Weak Hashing Algorithm in Virtual connect Flexfabric 10G/24

Hello All,

First (Bay 3) HP Virtual Connect 4Gb FC Module (409513-B22) lost communication with Onboard Administrator (No IP assignment) and as a result the Enclosure got degraded status. The general VC FC module status was still OK (see below)

Status Status OK Thermal Status OK Powered On

Diagnostic Information Device Identification Data OK Temperature OK Overheat Check OK I/O Configuration OK Power Allocation Request OK

A couple of reset, power off/power on operations did not change the situation. We decided to replace suspicious VC FC module by using the same module model from another HPE Blade Enclosure. Unfortunately there is still "No communication" error and additionally used Uplink ports have "NOT-LOGGED-IN" connector status. For the sake of completeness the firmware version is the same on both VC FC modules.

It seems that simple replacement of VC 4Gb FC Module is unsuccessful. Could someone explain what can be a reason of "No communication" error and whether any additional steps are needed in case we replace VC FC module?

Is there any special procedure in order to add new VC FC module to the existing VC domain? We use HP Virtual Connect Enterprise Manager.

Regards

↧

Flash update breaks IE when accessing VC

October 24, 2017, 7:45 am

≫ Next: Miss match WWN of virtual connect server profile hba vs ESXi vmhba

≪ Previous: HP Virtual Connect 4Gb FC Module (409513-B22) "No communication" error - Enclosure degraded status

Hi,

Was looking to see if anyone else ran into an issue recently with the last Flash update, 27.0.0.170 for Active X.

We have customers that are still on Windows 10 and use IE 11, while testing the new version of Flash I noticed that when you open Virtual Connect the Left Hand menu loads to 100% then the browser locks up and crashes. Throught testing I see this on 32 and 64bit machines and can confirm it's the 27.0.0.170 update.

We were on VC 4.40 Firmware and upgraded to 4.61 to test and found the same issue.

Can anyone one else confirm they are seeing the same thing?

↧

Miss match WWN of virtual connect server profile hba vs ESXi vmhba

November 9, 2017, 8:11 pm

≫ Next: Retrieve PN

≪ Previous: Flash update breaks IE when accessing VC

Finding solution for WWN mis-match between FC SAN_1B & vmhba2 Fibre Channel ESXi storage adapter.

NPIV is enabled.

BL460c Gen8 vSphere ESXi 5.5

Tried:

1. Server profile FC connections to unassigned and back

2. Reseat the blade

3. Firmware are same with others that have no issues

sample:

FC SAN_1B
10:00:00:90:FA:#E:#7:#9

vmhba2
Fibre Channel
51:06:0b:00:00:c#:6#:## {this is also the same WWN seen on SAN switch and zoned)

↧

Retrieve PN

November 22, 2017, 12:38 am

≫ Next: Virtual Connect Management IP Change

≪ Previous: Miss match WWN of virtual connect server profile hba vs ESXi vmhba

Hi all,

Is it possible to retrieve the SFP's part number installed in Virtual Connect ?

I've looked in "show all" and in the web interfaces without success.

Have you any idea ?

Thanls

↧

Virtual Connect Management IP Change

November 23, 2017, 4:54 am

≫ Next: Moving blades to a different rack

≪ Previous: Retrieve PN

I have to change Virtual Connect Management IP address.
I already searched Onboard Administrator User Guide.
It mentioned that after changed VirtualConnect Management, Each VirtualConnect module must have to reset.
Is it true?
I searched web
When it comes to change VirtualConnect IP address, there's no any mention related to
VC module reset
I don't know what should I do
plz help

↧

Moving blades to a different rack

November 27, 2017, 11:44 am

≫ Next: Not Linked | Loop Detected

≪ Previous: Virtual Connect Management IP Change

I'm fairly knew to configuring switches/chassis/blades, so please excuse me if something doesn't sound right.

So we have a total of 5 chassis, and I manage these via HPE BladeSystem Onboard/Virtual Connect. I am being tasked with moving 2 blades in one chassis to our virtual connect chassis. Is there a document to follow? What is the time frame normally for this task?

Side question, I have 5 Chassis (1 not being used yet), just because I have 5 chassis does not mean that all of them are virtual connect? Maybe I'm not understanding what virtual connect really is, but I'm thinking Virtual San, so there are some that are physically needed, and the others are virtual. Any help to get me a firm foundation and good direction would help.

Thanks

↧

Not Linked | Loop Detected

December 4, 2017, 1:19 am

≫ Next: VC flex 10/10 D Module X1 X2 port unpopulated

≪ Previous: Moving blades to a different rack

Guys !

Need help on this particular issue.

Randomly (have happened twice already in last week ) we see the following error message -

"Not lInked / Loop Detected "

The above is shown on Virtual Connect GUI, resulting in all NIC's at ESX showing disconnected.

We fixed this by resetting the server port loop option from the Virtual Connect GUI.

As per VMWARE support case , ESXi host would not create any loop for the HP Virtual Connect uplinks - so it needs to be checked with HP and probably get more details (Mac address, NIC) where the loop was detected.

Can someone point out where to start this troubleshooting ?

As I read somewhere - it is by design that Flex10D would disconnect/disable downlink ports to servers if it finds a loop in its uplink connections ? Am I getting this right ? which means that there is a loop getting generated on TOR/Cisco switches propagating down here ?

↧