help HP dl380 g4!

Similar Questions

• Unknow Device for HP DL380 G7 using Windows Server 2003 32-bit

  I need help to identify the right Windows 2003 SP2 32-bit driver for an unknown device in the Device Manager on a HP DL380 G7 server.  I have attached a screenshot.  The only information than the other, is that the device can be a PCI ISA device.

  Any help is greatly appreciated, if I'm in the wrong forum, please send the correct forum.

  Thank you

  Robert Jung

  [email protected]

  I found the problem, it's actually in a HP ProLiant Pack driver called: cp010950.exe attached is the image of the named driver: HP NULL IPMI Controller Driver for Windows 2003 version 1.0.0.0

• Expansion / Upgrade ProLiant DL380 G5 and ProLiant DL360 G5

  Hi all, we have two servers, Proliant DL380 G5 with SmartArray 400 and Proliant DL360 G5 with SmartArray 200icontroller controller, expand us on the disks, memory and cards network, the problem is that after we see the documentation which is sometimes wrong and don't know not the limitations of each of the parties, the issues are:

  Proliant DL380 G5 SmartArray 400:
  - STORAGE: up to 8 SAS / SATA, not clear what size that can be used with this controller, we understand that up to 500 GB SATA 7200 RPM and maximum 2 TB SAS 7200 RPM, we currently use with 146 GB drives to 10,000 rpm, whose original documentation is the maximum allowed value.
  -MEMORY: Up to 64 GB modules of maximum memory up to 8 GB.
  - NETWORK: update with PCI Express, support cards that I can find are HP NC110T PCI Express and PCI-Express HP NC373 HP NC360T PCI-Express.

  Proliant DL360 G5 SmartArray 200i:

  - STORAGE: up to 4 SAS / SATA controller supports only 200i SmartArray four drives in RAID 0, 1, 1 + 0 if we wanted to expand to six bays that are available on the disk server, it would change the controller and memory. Yet, the size of disk maximum supported based on the documentation is 72 GB SAS and SATA drive 60 GB, but looking it seems as if you agree at least 300 Gb SAS disks at 10 000 rpm and up to 500 GB 7200 RPM.
  - MEMORY: up to 64 GB maximum memory modules up to 8 GB.
  - NETWORK: update with PCI Express, support cards that I can find are HP NC110T PCI Express and PCI-Express HP NC373 HP NC360T PCI-Express.

  This is what I have gathered and what interests me in the expansion and to say that the documentation I found to give the feeling of this conflict, is perhaps by the dates of their procedures, but before you make a payment would guarantee the purchase. Also getting information guides, manuals and forums, I have also consulted compatibiliy HP Proliant Server Guide, so I have consutlado with HP before purchasing, but have yet to receive an answer.

  A greeting and thank you very much

  Hello jranerosc. I think you'd have better luck trying Business Forums of HP. You should get more specific help.

  Have a great day!

• ProLiant DL380 Gen9 - grouping of NETWORK cards

  Hello community,

  for a week we have new servers DL380 Gen9. Now, we want to install a server Win 2008 R2, but we cannot create a collection of NETWORK adapters.

  If I install the HP NCO (Network Configuration Utility), cp023339.exe Version 10.90, I get

  "The bot software will be installed on the system because the required hardware is not present in the system or the software/firmware does not apply to the system"

  I updated the driver / firmware of the NETWORK adapter have sought new HP Network Configuration tool, nothing.

  NIC: Map 1 GB 331i 4 ports Ethernet HP

  Can anyone help?

  Thank you very much

  / Hugo

  Hello:

  You can also ask your question on the Business - servers DL HP Support Forum.

  http://h30499.www3.HP.com/T5/ProLiant-servers-ml-DL-SL/BD-p/ITRC-264#.VHM-jHktC9I

• vMotion works between HP DL380 G7 and the Gen9

  Hi all

  VMotion I would like to know how working with HP DL380 G7 HP DL380 Gen9?

  Can someone help me?

  vMotion between this two servers:

  HP DL380 G7:

  Intel Xeon E5649

  Embedded NIC 4x1GbE

  + NC364T PCI Express Gigabit QuadPort

  HP DL380 Gen9:

  Intel Xeon E5-2650v3

  Embedded NIC 4x1GbE

  + 10 GB 2-port 10GBASE-T 533FLR-t HP FlexFabric

  Can someone help me?

  I would be very grateful
  

  Ralf
  

  The G7 has a CPU of generation Westmere, the Gen9 has a generation of Haswell CPU.

  vMotion requires that you have the same subset of games of CPU instructions and common on the source and destination of the CPU and active features in the server BIOS.

  This means that in your case:

  You will be able to vMotion virtual machine that has been powered on the host of the G7 (VM runs with Westmere instructions) for the Gen9 and so (but only if you don't re - power cycled the VM on the host G9).

  But you will not be able to vMotion virtual machine that has been powered - we on the Gen9 host (VM runs with Haswell instructions) to the host of the G7 most old car is missing these more recent CPU instruction sets.

  VCA comes here. By activating EVC on the common cluster with the generation of CPU down (in your case Westmere), all guests will present only these instruction sets to virtual machines when they are powered - on, which makes possible dynamic migration through the different physical CPU generations.

  See the following articles for more information about CVS:

  VMware KB: Enhanced vMotion compatibility (EVC) support processor

  VMware KB: EVC and CPU compatibility FAQ

  Alternatively you could manually hide CPU instructions by VM - with advanced options if you don't have a source host and destination in the same cluster, but it is a tedious task and I would not recommend it.

• ESXi 6.0 installs but does not start HP DL380 G7

  Hello

  I have a HP DL380 G7 server, I have 4 disks, configure a RAID0 array and created a logical volume of the sum of the disk 4 (2.2 to)

  ESXi 6.0 correctly installed and asks to restart, when restarts the server tries a different boot devices (network, etc.)

  I have tried F11 during boot and select to boot from the local disk, but the problem persists.

  No idea how to fix?

  Thank you!

  Thanks for your help!

  It was my mistake, check the Configuration of the Array utility there is an option in the main 'select the boot Volume"menu, selected my logical volume and here!

• HP DL380 G6 ESXi 5.5 capable of detecting devices of storage but unable to create data warehouses

  I will say upfront I am newbie and in need of assistance.

  I have a HP DL380 G6 for which I installed iso customized for ESXi with the help of a CD-Rom, installed everything great, no errors, health status shows all green.

  I have 3 hard drives in bays, 500GB, 500GB and 1 TB.

  Sensors see the three connected but in ESXi under storage I cannot see one, could not create a data store.

  My goal is to have a hard disk for each operating system that you are separate, I don't really care about RAID that I think that maybe part of the problem.

  I have attached the photos if someone can help me here.

  Thank you!

  

  

  

  Hello

  first of all, I would like to check if the latest Proliant SPP (service pack) is installed, or at less the systems BIOS, firmware for the P410i, network cards and the HP ILO (if you have a) is up-to-date. Latest version of the firmware of the P410i is 3.30 (B) insofar as I see, you have 3.00.

  Then go into the P410i RAID configuration and check if everything is configured correctly, it. It looks like at least the 1 TB drive and probably one of the 500 GB drives are not configured in the settings of the controller. This is why there is no volume showing in VMWare.

  If you change the configuration in P410i referring to disk/RAID volumes you may need to reinstall VMWare.

  cykVM

• With the help of Manager Update to upgrade ESX 5.1 to 5.5 - conflicting ERROR VIBS

  
  Hello

  I hope someone can help. I have a number of 5.1 ESX host that I would spend 5.5 using the Update Manager which seems straight forward enough... right

  vCentre is 5.5

  Import the ESXi ISO to update manager

  Create a baseline

  Attach the base to the host to be upgraded

  Analyze and correct the

  .... Simple

  The problem I have is that use us the HP Custom image because they are all servers in HP, sense, right. I downloaded the HP 5.5 Custom ISO Image from the VMWare site and imported from the ISO to the Update Manager, created a base line, attached to a host of test (DL585 G5) and scan. IM presented then an incompatible warning and details show below

  

  I searched the net for a solution and found several contradictory entries on dealing with VIBs and creating custom ISOs, I also downloaded the ZIP of the Depot HP ESX file and created a custom ISO that does not work either.

  Here are the current Broadcom VIBs installed on my ESX host, test

  

  I can not also remove the contradictory VIBs because they are network card drivers and if I delete and restart the host does not have network cards (well Yes, I tried).

  Its been 2 days of pulling my hair and maybe I'm missing something simple.

  Anyone have any ideas?

  Thank you

  DCurrie,

  I'm in the same boat as you. I all hosts in HP DL380s I have migrated my hosts to test on my server to vCenter 5.5 U1 and went to perform the upgrade on the hosts of 5.1. I had everything first to apply the latest patches on the 5.1, which then allowed me to level 5.5.0 of the host. I then had another set of patches that I applied (assuming that I had to do before moving to 5.5.1). After the implementation of those, I still 5.5.1 an incompatible upgrade.

  The upgrade contains the following set of contradictory VIBs:

  Broadcom_bootbank_net - bnx2_2.2.5dv55.2 - 1OEM.550.0.0.1331820

  Remove the conflicting VIBs, or use the Image Generator...

  Then, I could at least make at 5.5.0, but not more than details. Both used 5.5.0 and 5.5.1 ISOs are ISOs of OEM HP.

  I have currently installed bnx2_2.2.4f.v55.3.

  HP has like downloadable bnx2_2.2.3t.v55.7 under the heading vSphere 5.5.

  VMware under the HCL has several versions, including my current version and the bnx2_2.2.5d.v55.2.

  Since this is test, I'll play with it some more and see what I can understand.

  ----------------------------------------

  Update: from U1b 5.5 Release Notes

  Update Manager reports the status of compliance as Incompatible when scanning or clean up ESXi 5.x hosts in a HA cluster

  When you perform an upgrade ESXi 5.x hosts belonging to a HA cluster analysis, Update Manager can report on the status of compliance of the incompatible host and might not allow the hosts to be remediated. Inconsistent compliance status is because of the way the agent of FDM (HA) is installed on ESXi 5.x hosts. From vSphere 5.0, the FDM agent is installed on the hosts ESXi as a VIB. When a VIB is installed or updated on an ESXi host, a flag is set to indicate that the bootbank on the host has been updated. Update Manager checks this flag while performing an analysis to level or sanitation and requires this flag to be cleared before the upgrade of a host. The flag can be cleared by restarting the host.

  Solution: restart guests reporting the State of compliance as Incompatible. Run the analysis of upgrading or rehabilitation after the host comes back online.

  Will try this and let you know how it goes.

• HP DL380-> find hardware serial number of HP DL380 Server 2008 R2 VM

  Hello

  I'm working on a VMWare ESXi configuration that requires to get the serial number of the equipment of a HP DL380 to the VMWare Guest.  The only problem I have is that the guest will not know the IP address of the VMWare host.

  Here's the Setup: HP DL380 (running VMWare ESXi 5.5)-> VMWare ESXi Guest VM (virtual machine must obtain the serial number of the DL380, but do not know the IP address of the host and can not reach the network.  It is possible in some other way?).

  Any help would be appreciated.

  Thank you

  Ryan

  Well... you will need to do so through a proxy...

  If you have access to the VM vCenter, you can watch a powercli for this script, it would be grep it...

  If that VM can not reach the host at all, then you need another 'computer' that can reach the ESX host and virtual machine, to ask for you and pick up the other "computer."

  If this isn't an option... then you must watch the invoice for the order...

• VM loses connectivity after a reboot... help!

  I'm lost on this one, I've NEVER seen this problem before.

  The server is an HP DL380 G5 with two 1 GB network adapters. Running ESXi 5.0 (with all updates) one comes from ISP and we're going on the local network (server is mail, NAT and much more).

  After a reboot, the NETWORK card that comes from the ISP, loses connectivity, more often. It will be the Web sites (I guess that's the port open on the firewall) but nothing else. No internet, no. DNS, I can't even ping an external site by its IP. The only thing that works is the Web sites that are currently running. We use this connection for Web sites and Internet for the site so using NAT gives him around our PC, it is important that it works.

  The ONLY way to recover is to remove TWO cards from the network card in Windows and let Windows find their new (drivers). I got this server and copied down to older hardware, and never, it has a problem after a reboot and works with a number. On ESXi 5, even after fixation by the removal of the NETWORK adapter cards, once it gets restarted, I have to start all over again.

  I need to pass to the virtual machine, but so far it has been nothing but a nightmare.

  It is material or ESX that causes this problem, I don't know it's not on Windows server 2003 that they run...

  Any ideas? Please help if you can.

  The problem seems to be what I was suspecting, a routing problem internal VM. I thought you lost the 0.0.0.0 route to the internet, but instead, you actually get an another 0.0.0.0 route that points to the local interface. The route print output:

  Work:

  0.0.0.0          0.0.0.0       < isp="" gateway="">      <   isp ="" ip="">     10

  Does not:

  0.0.0.0          0.0.0.0       < isp="" gateway="">      <   isp ="" ip="">     10

  0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.1 10

  192.168.0.1 is the local IP address of the internal NETWORK adapter in your virtual machine. This means that for some reason, sees itself as the default gateway and also not trying to access the internet through your ISP router.

  If you look at the text notworking ipconfig/all command, you will see that the 'card Ethernet Local Area Connection 4' with the 192.168.0.1 IP itself now has as a default gateway.

  The LAN4 configuration is static, so it's quite strange where the new default gateway information comes. A quick fix after a reboot is likely to open the TCP/IP settings and remove the new default gateway of the interal NIC

  You could also enter a new route persistent to the ISP router with the metric is lower, but I think that we should first try to find out why your Windows 2003 establishes a default gateway on the internal interface.

• ESXI 5 - DL380 G7 - DR - HA - vMotion - x 2 NIC (8 Ports) - LAN - WAN - subnets

  Dear VMware community

  Did someone a challenge?  Being totally new to VMware (3 weeks to read and watch videose etc) I hope that this will start a discussion on the best way install, configure, and deploy my new virtual environment in a phase of the 3 stage for phase 1 to move into the new year 2012, first quarter for Headquarters and then so on.  I'm reading VMware vSphere Design, Mastering VMware vSphere and VMware vSphere 5 technical clustering Deepdive 5.

  Little background on our remedies and knowledge: -.

  There are 2 IT guys, me (TD) and JP.  JP has been with the same company and in it for about 5 years to deal with printers, ADSL, workstations physical and Small Business SERVER 2003 servers on sites, I was in there for about 12 years covering the market of small businesses (10-100 users) mainly on printers, workstations, LAN and WAN, servers Microsoft SBS 2003 to 2010 database Server 2003 and 2008 R2, Exchange 2003 to 2010, Draytek, WiFi AP and switches routers unmanaged.

  Little background on the parameters of our society: -.

  We have 1 company but 3 separate sites...  Office of Chief of site 1, Site 2 Site 3 (as a franchise) so each site tracks than their own facilities on the chart of accounts, personnel etc. etc. but reports to Headquarters.

  Site 1 has 50 users with Server 2003 SBS, SQL Server, Intranet, Helpdesk and PC Reporting.

  SQL is only used by 10 users for an internal application.

  10/10 MB Internet in lead line

  Site 2 has 50 users with a SBS 2003 and Server 2003 std, AD, DC, DHCP server, DNS etc.

  Server 2003 std manages a small application by a third company which send a little info per week.

  10/10 MB Internet in lead line

  Site 3 has 30 users with Std 2003 server, AD, DHCP, DNS etc. and mail is pop collected on the net.

  2 x - BT 30 MB - D / 7MB - line Up Infinity Internet

  Each site has now a connection of 1 GB Draytek 2830n with site-to-site inactive using ipsec vpn about 20 MB speed and an average of 15ms ping (no traffic is sent over lines at the moment), x 3 24-port HP Procurve switches, unmanaged, therefore, each site has its own separate domain structure, AD DC, DNS, DHCP etc., and IP.  It's a real pain to manage and look after.

  Adding all sites operating systems, data, Mail etc etc I will use about 1.5 TB

  What I want to achieve a realistic budget for 130 users: -.

  Virtual (that's why I'm here.  LOL)

  Reasonable return without having to go to a full SAN environment blown for 3 sites

  vMotion - HA - DR - continuity - Easy Backup and restore - centralized management – storage centralized redundancy - a kind of failover (but), Site replication to the other and, ideally, no. SPOF.

  I just bought the following Kit to test and then use in the direct environment and buy the additional kit if it is the right path to follow.

  HP HP/3COM Couche3 routing V1910 - 16G Ethernet Switch 16 Port - x 2

  HP 633405-421 PROLIANT DL380 G7 E5649 2.53 6 C SFF P410I/256 460W - x 2

  http://h10010.www1.HP.com/wwpc/UK/en/SM/WF06b/15351-15351-3328412-241475-241475-4091412-5064836.html

  HP 500662-B21 30 GB of RAM per server (3 x 8 GB) - DDR3-1333/PC3 - x 6

  HP 605835-B21 HP 1 to 6 G SAS 7.2 K 2.5 in. MDL - x 6

  HP 581286-B21 HP 600 Gb 6 G SAS 10 K rpm SFF Dual Port - x 6

  HP 8 GB Secure Digital High Capacity CLASS 10 Ultimate - x 2

  HP 516914-B21 HP DL380 G7 8SFF CAGE KIT for 8 bays SFF - x 2

  HP 503296-B21 HOT PLUG REDUNDANT POWER 460W - x 2

  HP 593722-B21 HP NC365T Gigabit Ethernet Card - PCI Express x 16 - x 2

  HP 468406-B21 SAS Controller - Serial Attached SCSI (SAS) - PCI Express 2 - x 2

  8 TB of QNAP TS - 459 Pro 4-bay Turbo NAS - 1 x II (no second RAID controller)

  MS Datacenter 2008 R2 - x 6

  MS Exchange 2010 - x 1

  My thoughts for 130 users between the 3 sites are:-

  Put all of the Group 1 local domain with unique authentication and replication DFS R2 server 2008.

  Head Office hosts will have x 2 Server 2008 R2 domain controllers DC01 and DC02 (primary and secondary DC)

  1 IP and subnet within the group structure

  Site 1 - 192.168.0.X 255.255.0.0

  Site 2 - 192.168.1.X 255.255.0.0

  Site 3 - 192.168.2.X 255.255.0.0

  Have 1 exchange server at the Head Office of the group.  Server 2008 R2 - Exchange 2010 Std

  Have 1 Intranet server at the Head Office of the group.  Server 2008 R2

  Have 1 Helpdesk server at the Head Office of the group.  Server 2008 R2

  Have 1 DC server at the Head Office of the group.  Server 2008 R2

  Have 1 Intranet server at the Head Office of the group.  Server 2008 R2

  Having enough material on the site of 2^nd to make appear the VM headquarters is in a DR situation.

  Host 2 will be DC03 DC04 Vm

  3 host will have DC05 and DC06 Vm

  Acceleration of VMware Standard Kit with up to 8 cpu

  x 6 servers DL380 G7 (see specifications above) - x 2 servers on each site with 6 simple core cpu for each server

  With a 16-10 k 600 GB SAS or x 16 x 1 TB 7.2 k MDL SAS 6 GB

  x 2, 4 port NIC - edge - 4-port 4-port HP NC365T

  HP P4000 VSA across x 16 discs on both servers for vMotion and HA

  A kind of QNAP backup software

  x 2 QNAP 8TB NAS, x 1 at Headquarters, x 1 to Site2 to VM backup of (QNAP to QNAP allow replication to Site to Site)

  My budget is of approximately: -.

  Around £50 k / 60 k give or take a little.   Just brought 10 k worth of kit leaving 40 k / 50 k.

  My questions are:-

  (1) would this setup and kit look if he'd work with future expansion?

  (2) what recommendations and how I would go about setting up the structure/IP subnets and vswitches/pswitches/groups etc. to which physical ports?

  (3) are there other recommendations or suggestions for me to watch given the fact that I never touch before vmware, and I'm going to do the installation, configuration and deployment?

  I know that, don't tell me "I have my hands full" LOL any help would be great.

  Thanks to advanced

  Trevor

  Hello

  I'd be curious to see a detailed drawing of what you intend to look like in the end.

  I would say please download video to youtube or iTunes where a lot of best practice available. or you can dowonload of best practices of product psecific.

  _________
  Good luck!

• New to all this, should help understand what to try, to turn.

  I have a dl380 G3 and a Dell 2650 available.  Hardware Guide says that ESX3.5 U 5 is supported.  I think I read it correctly.  What I would like to have is a hypervisor, according to me, the os and VirtualHost combined into a single entity. I would like to install this on a cd.  I could download ESXi 3.5 U5 (I reg #).  Is it the same thing as U5 ESX3.5?  Uncertain as to the differences.  If not, how can I download ESX3.5?, as it is ESXi3.5 I have hangs during installation on the DL380.

  Perhaps reasking in another forum?  Maybe get some help with my existing ESXi installation?  Where should I go from here?

  ESX is not free.

  To have the old edition 3.5, you must buy the 4.x and then ask a downgrade of the license.

  André

• DL380 G3 ESX 3i Version 3.5.0 network drivers

  I am very new to VMWare and having a problem setting up of my first installation of comments.

  I have a DL380 G3 with ESX 3i Version 3.5.0 installed.  In VMware Infrastructure Client, I can see the following network card:

  NC7781 Gigabit (PCI - X, 10,100,1000-T) server adapter

  My first guest OS is Server 2008 Standard (32-bit).

  In the comments, I can't get a driver installed.

  That's what I tried:

  Drivers HP.  I am told that the intelligent installation is not supported in a virtual machine.  So I extracted the files and tried to install.  I am told that the drivers are incorrect.

  Broadcom drivers.  I can get windows install these, but same problem, drivers are incorrect, and they do not start.

  I am sure that the hardware is supported and is on the compatibility list.

  Help, please!

  Thank you.

  Hi Robrandon,

  Welcome to the forums.

  Never try to use a physical device driver in a virtual machine. Check that your virtual machine is configured with the information in the appropriate operating system and has a virtual NIC attached. Then install VMware tools. The network card must be running in your comments.

  Good luck.

  Concerning

  Franck

• Help with SCSi controller

  Hello

  I want to move a controller SCSI one of our machines in our VMware machine, but I can't find any confirmation that the controller is supported by VMware, so hopefully someone here can help me.

  VMware machine Info:

  HP Proliant DL380 G5

  Running VMware ESX3i 3.5.0,123629

  News of the controller:

  LSI Logic - LSI20320C-HP

  SP #: 403051-001

  HP to the Denmark couldn't answer my question, and I've not had a lock tries to use the VMware search engine to find the material in the compatibility list.

  Let me know if you need more information.

  Best regards

  Anders

  This thread may help: http://communities.vmware.com/thread/104956

• HP ProLiant DL380 G4 can not install Windows 2003 x 64 error «...» CPU is not compatible with x 64 mode... »

  I try to install a Win2003 64 bit VM on ESXi 4 but get the error that x 64 processor not supported. The server has Intel E7520 Chipset and Xeon 2 x 64-bit clocked at 3.6 GHz processors. It should be possible to run virtual machines with Win2003 x 64, right? Anyone know what I'm doing wrong?

  Thanks for any help.

  While ESXi 4 will install, DL380 G4 platform is not supported.  This generation of processor (Xeon 51xx) taken supported operating systems for 64-bit, but there is no VT extensions.  It's why he can't support 64-bit clients.