Quantcast
Channel: BladeSystem - General topics
Viewing all 901 articles
Browse latest View live

HP C7000 Blade connecting to power

$
0
0

Hey Guys
 
I have a HP C7000 enclosure with 16 X bl460 G6 blades. I bought all the power cable and I bought a 2 bar PDU and I need to know what is the type and model number of your Power Distribution Units.

I know I will need to bring an electrician over to add a breaker I think someone told me 40amp breaker and my c7000 will run N+N.

The input of all 6 power supply is 200-240v 50/60 hz max ac current is 13.7 A

Here in Canada we have 120 V outlets so I know I will to send somebody to add something to the fuse box or I will trip a breaker.

Can you guys tell me what gear you are using to power up your C7000 so I can order it also. I have been looking for about a month and I am going insane!!

Soon I will be running 2 C7000's so if you have 2 running of them please le me know the model number of the PDU's everything lol  from the outlet to the C7000 power supply connector. please help


3par with direct attached blade enclosure

request for quotation attach file

$
0
0

1- LICENSES, OPEX (Licenses - HPE 5 year post warranty Foundation Care Next Business Day Service (H7J32AC): 1) 3x - C7000 Blade Enclosure with IC Service: P/N - 686611-B21, S/N - CZ3324FXR6; P/N - 686611-B21, S/N - CZ3324FXDP; P/N - 681844-B21, S/N - CZ3341R04F 2) 1x - C7000 Blade Enclosure Service: P/N - 507015-B21, S/N - SGH314RHL6 3) 30x - ProLiant BL4xxc Service: P/N - 641016-B21, S/N - SGH314RKN0; P/N - 641016-B21, S/N - SGH314RKMW; P/N - 641016-B21, S/N - SGH314RR4T; P/N - 641016-B21, S/N - SGH314RR4S; P/N - 641016-B21, S/N - CZ3341R04V; P/N - 641016-B21, S/N - CZ3324FXRH; P/N - 641016-B21, S/N - CZ3324FXRJ; P/N - 641016-B21, S/N - CZ3324FXDW; P/N - 641016-B21, S/N - SGH314RR4P; P/N - 641016-B21, S/N - SGH314RR4R; P/N - 641016-B21, S/N - SGH314RKN5; P/N - 641016-B21, S/N - CZ3341R04X; P/N - 641016-B21, S/N - CZ3341R04M; P/N - 641016-B21, S/N - CZ3324FXRD; P/N - 641016-B21, S/N - CZ3324FXDX; P/N - 641016-B21, S/N - CZ3324FXDY; P/N - 641016-B21, S/N - CZ3324FXDV; P/N - 641016-B21, S/N - CZ3324FXRK; P/N - 666158-B21, S/N - CN731102GQ; P/N - 666158-B21, S/N - CN730805L2; P/N - 666158-B21, S/N - CN731102GT; P/N - 641016-B21, S/N - CZ3341R04P; P/N - 666158-B21, S/N - CZJ3410BV5; P/N - 666158-B21, S/N - CZJ3410BV6; P/N - 641016-B21, S/N - CZ3341R04S; P/N - 641016-B21, S/N - CZ3341R04K; P/N - 641016-B21, S/N - CZJ45103RD; P/N - 641016-B21, S/N - CZJ45103RC; P/N - 641016-B21, S/N - CZ3324FXRL; P/N - 641016-B21, S/N - CZ3324FXRF 4) 4x - ProLiant with DMR ProLiant BL6xxc Service: P/N - 727959-B21, S/N - CZJ45103N0; P/N - 727959-B21, S/N - CZJ45103MY; P/N - 727959-B21, S/N - CZJ45103MZ; P/N - 727959-B21, S/N - CZJ45103MX 5) 13x - B Series 4/24-12 c-Cls Switch Service: P/N - AJ821B, S/N - CN8320B009; P/N - AJ821B, S/N - CN8320B03J; P/N - AJ821B, S/N - CN8316B00E; P/N - AJ821B, S/N - CN8316B00K; P/N - AJ821B, S/N - CN8320B024; P/N - AJ821B, S/N - CN8320B02L; P/N - AJ820B, S/N - CN8305A03F; P/N - AJ820B, S/N - CN8305A031; P/N - AJ821B, S/N - CN8337B0EH; P/N - AJ821B, S/N - CN8337B0DZ; P/N - AJ821B, S/N - CN8451B0AT; P/N - AJ821B, S/N - CN8451B0B2; P/N - AJ821B, S/N - CN8451B0AU 6) 1x - MSA 2040 Storage Service: P/N - C8R14A, S/N - 2S6446B087 7)1x - MSA2000 G3 Array Service: P/N - AW567A, S/N - 2S6049C638 )  QTY-01

2-  BLADE SYSTEM,BL460C,GEN10,HPE ( "HPE Server Equipment with listed below specification: 1) HPE ProLiant BL460c Gen10 v6 10/20Gb FlexibleLOM Configure-to-order Blade Server (P09524-B21) – 1 EA; 2) HPE BL460c Gen10 Intel Xeon-Gold 6248 (2.5GHz/20-core/150W) FIO Processor Kit (P06820-L21) – 1 EA; 3) HPE BL460c Gen10 Intel Xeon-Gold 6248 (2.5GHz/20-core/150W) Processor Kit (P06820-B21) – 1 EA; 4) HPE 64GB (1x64GB) Quad Rank x4 DDR4-2933 CAS-21-21-21 Load Reduced Smart Memory Kit (P00926-B21) – 12 EA; 5) HPE 400GB SAS 12G Mixed Use SFF (2.5in) SC 3yr Wty Digitally Signed Firmware SSD (P04525-B21) – 2 EA; 6) HPE 12W Smart Storage Battery (up to 3 Devices) for BladeSystem Server (P01363-B21) – 1 EA; 7) HPE Smart Array P204i-b SR Gen10 (4 Internal Lanes/1GB Cache) 12G SAS QMH2672 16Gb Fibre Channel Host Bus Adapter (710608-B21) – 1 EA; HPE Trusted Platform Module 2.0 Gen10 Option (864279-B21) – 1 EA; 9) License, HPE OneView for Blade Server including 3yr 24x7 Support FIO Bundle Physical 1-server LTU (F6Q89A) – 1 EA; 10) License, HPE Legacy FIO Mode Setting (758959-B22) – 1 EA; 11) License,HPE Gen10 TPM 1.2 FIO Setting (872108-B21) – 1 EA; 12) License, HPE BL460c Gen10 Support (H7J32A5#W4C) – 1 EA; 13) License, HPE One View w/Ilo Support (H7J32A5#SVN) – 1 EA. " ) QTY- 10

3- FLEX FABRIC ADAPTER,20Gb,700763-B21,HPE ( HPE FlexFabric 20Gb 2-port 650FLB Adapter (700763-B21)) QTY- 10

4- ULTRIUM CLEANING CARTRIDGE,C7978A,HPE ( HPE Ultrium Universal Cleaning Cartridge (C7978A))  QTY-20

5- CARTRIDGE,LTO-7,15TB,20PCK,C7977AH,HPE ( HPE LTO-7 Ultrium 15TB Eco Case Data Cartridge 20 Pack (C7977AH)) QTY-5

6- TAPE BARCODE,LABEL PACK,LTO-7,Q2014A,HPE ( HPE Q2014A Ultrium LTO-7 RW Tape Barcode Label Pack (Q2014A)) QTY- 1

7- LICENSES, CAPEX ( Perpetual license, HPE Brocade 8/16Gb Embedded FC Switch 12-port Upgrade E-LTU (T5517AAE) QTY-2

PLEASE QOUTE URGENTLY

 

Unable to access Active OnBoard Administrator (OA1)

$
0
0

I cannot access the OA interface which is active.
In my case it is OA1 which is active.
I have a C7000 enclosure with two redundant OAs (OA1 and OA2).
OA2 is accessible in GUI and SSH but not OA1.
Enclosure IP mode is activated so it is the IP address of OA1 which is always used when I put OA2 in active.
When OA2 becomes active, it is no longer accessible. It is OA1 in standby which becomes accessible.
The network settings are well configured.
The 2 OAs are in the same subnet.
How to reestablish the connection with the active OA?

QSFP28 socket compatible with QSFP transceiver

C7000 port mapping for interconnect bay 5&6 7&8 using Mezz slot2

$
0
0

if i have network switches in bays 5 and 6 and add 1gb pass thrus in 7 and 8 and  add a  1gb 4port nic 366m in mezz slot2 can ports 1 and 2 which are connected to bay 5 and 6 be disabled from the OA blade port mapping view checkbox?

 concern is disrupting network switches in bay 5 and 6 when installing passthrus for newly installed bl460's

Updating OS c7000 Chasis

$
0
0

I've just come into posession of an HPE blade system with a c7000 enclosure. System currently working with vmWare vSphere 5.0 on an old license. I've got a trial licence for 6.0 (max version of vSphere that will run on my individual blade). I'm trying to overwrite the OS with this new ISO image I have on CD, but can't seem to get my iLo environment to recognize the external DVD player I am using. 

Cuveballs which make this not a straight forward process:

- Running iLo 3, not the most recent 4

- am required to keep a full airgap with this device. No internet connection, and zero usb's to be used. I have this device networked to an isolated desktop that I am accessing the server through via iLo, however even the remote management console will not launch. 

 

I am suspecting this is likely firmware versions, and am working to establish a plan on updating this but wondered if anyone else has any hints to point me in the right direction and save me countless troubleshooting hours when I have such constraints. 

Cheers

c7000 Blade Chassis - Missing Virtual Connect Link

$
0
0

Hi,

We seem to be missing the link the for the Virtual Connect Manager..

I have been to Enclosure Settings/Enclosure IP Settings/IPV4/Interconnect Bays

Both Bay 1 and 2 have EBIPA address in there and they ping back ok.

They also have the tick in the enabled box.

 

The interconnect bays have "Cisco Catalyst Blade Switch 3020 for HP" in them and they all work ok.

 

Firmware :

OBA - 4.90 - Dec 11 2018

BladeSystem c7000 Onboard Administrator Tray 1.7
BladeSystem c7000 Insight Display 2.4.3

 

Is there something missing? 

Any help would be appreciated.

Thanks in advance.


C7000 OA upgrade path

$
0
0

Evening all.

I am creating a firmware baseline on 2 C7000 chassis at seperate datacentres and would like to check which firmware upgrade path I need to take for the secondary chassis.

I need to upgrade from OA version 4.22 to 4.60 and the VC in both Chassis is currentlly 4.20

All of the blades are BL460 G8 and have been upgraded to the 8.1 conveniance SPP including the 2019 bios.

Is there any VC outtage risk with this firmware upgrade? 

 

 

 

Updating ROM BIOS via iLO3 question

reconfiguring IP address for BL870c server - virtual connect change needed?

Migrate OA & Blade iLO interfaces to new VLAN

$
0
0
Hi,

I'm looking to move our enclosure and iLO management to it's own separate VLAN so it's away from the standard 'server' VLAN and am looking for direction in terms of the steps taken, and also whether there's anything else I need to consider.

My environment consists of 3 x c7000 (linked) enclosures, each with 2 x Flex10 Virtual Connect modules and 2 x OAs.

My thinking is as follows:

1) Configure new VLAN on switches and identify ports used for the OAs.
2) Log on to OAs and change IP addressing to new IPs associated with the new VLAN. At this point I lose connectivity (I'll be doing this remotely).
3) Change the switch ports that connect to each OA to be access ports in new VLAN. At this point I should regain access to the OAs on the new OA IP addresses.
4) Change the blade iLO IP addressing to the new VLAN.
5) Change the Flex10 IP addressing to the new VLAN.

Does that all sound correct?

Is this a disruptive task, as in, will it impact any production network traffic?

Thanks in advance.

HPE End of life and End of engineering support information for HPE products

$
0
0

Hi

Is there a consolidated document for HPE products End of life and end of support dates for DL/BL proliant servers, C7000 enclosures, Hp Ad525c  and other related enclosure products 

 

HPE C700 ENCLSOURE TRANNING VIDEOS

$
0
0

HPE C700 ENCLSOURE TRANNING VIDEOS

Can anyone help me to learn C7000 enclosure training videos.

Apprecaite for your quick response.

C7000 - VC - OA - ILO - Compatiblity

$
0
0

Hey guys,

I'm looking for an document, where I can see which OA Version is compatible to the VC Version and which ILO Version is required for this version. After my opinion the VC Version depend on the OA Version, what is with ILO for Blades? Are they independent from the rest?

I didn't found any documents in support.hpe.com.

Background:

We have a lot of serverchassis with different version of VC/OA/ILO on Blade and I would like to to update these different version to the same version datacenterwide.

Thx


Frequently Searched and Consumed Technical Content on HPE Portal

$
0
0

2 x C7000 stop recognize BL680 G5 and BL460 G1 after OA Upgrade

$
0
0

Dear Community Members,

I have two decent 9 years old C7000 chassis with OA version 3.30. One chassis is equipped with 8 x BL460 G1 blades, second chassis is equipped with 8 x BL680 G5 respectibely. VC connect version is 3.50 is on both chassis.

Both chassis have:

2x HP 1/10GB VC-ENET Enet Modules P/N 399593-B22

2 x HP 1/10Gb VC-Enet Module 2x10Gb 8x1Gb P/N 399593-B22

After update of OA to version 3.71, then to 4.01 and ending on 4.23 version, as last version compatible with BL460 G1 and BL680 G5 respectively, blades started to be not recognizable by noth chassis after next power cycle. They do not respond on power cycle button and indicating red flash light. From OA point of view blades are displayed as blank slots in chassis overview with unidentified hardware with no chance to control them. All blades were updated to last supported iLo and ROM versions using appropriate packages for both models.

As result I have all 8 x 680 G5 not recognized in first chassis with blinking flash lights, 5 out of 8 BL460 G1 not recognized on second Chassis. 3 BL460 G1 still running, because I did not reboot them yet.

To migitate the issue I tried the following on first Chassis with BL680 G5:

1. Extract and insert all 8 Blades and OAs.

2. Mixing the slots for Blades

3. Downgrade of OA to previous versions

4. Executing E-FUSE reset to all 8 Blades from SSH CLI.

5. Complete power down of Chassis and Powering On.

6. Inserting OA module with version 3.50 from foreign chassis and upgrading to different 3.X and 4.X versions.

To migitate the issue I tried the following on second Chassis with BL460 G1:

1. Extract and insert all 5 Blades and OAs

2. Mixing the slots for Blades

3. Downgrade of OA to previous versions

4. Executing E-FUSE reset to 5 Blades from SSH CLI. 

5. Setting Pin 6 on MB on reset position and inserting blades back to Chassis.

Can You kindly advise how to bring back to life these systems?

Thank you in advance.

 

 

 

Smart array fw update

$
0
0
Hi All
I want update smart array firmware on hp blade on enclosure c7000 running solaris 10 on it. Kindly guide me complete procedure to update.
Thanks

Smart array firmware upgrade

$
0
0
Smart array fw update

Hi All
I want update smart array firmware on hp blade gen 8 on enclosure c7000 running solaris 10 on it. Kindly guide me complete procedure to update.
Thanks

Virtual Connect - How to Make Virtual Network Assigned in the Same LOM 1-A and 1-B ?

$
0
0

We have C7000 blade, with two node installed. In network side, one virtual connect (VC) was installed. 

We already created some virtual network in VC Manager to integrate with network environment. Then we want assign these virtual network in Server Profile. As we know network configuration port in VC has something like this:

LOM 1-A, 1-B, 1-C, 1-D.

What we want to do is assigning these virtual network (virtual network 10, 20, 30 for example) to LOM 1-A and LOM 1-B in the same time. Then we click Apply but can not save, with this error:

These connections are configured with duplicate networks (picture was attached) 

VCM Error.JPG

we also try to force this configuration by checking this option:

Force the same vlan mappings as in the shared uplink set

force the same vlan mapping.jpg

But still can not save such configuration.

Is it possible to do such configuration in HPE Virtual Connect system? if it is not possible what is the best option available? Please share 

We install VMware ESXi on its node so we need to do it to support multi vlan in the system.  

 

Viewing all 901 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>