Boot LUN

Similar Questions

• Move Vmware Boot LUN to another NetApp aggregate

  Hi all

  I have two Exsi 5.0 in a cluster and I need to move two LUNS two boot for another of the aggregates of NetApp. can someone please advise the steps I should follow to these migrations.

  Concerning

  Thank you JonathanKohler . I managed to finish, your answer is correct, however, the DataMotion is available in NetApp from Version 8 and as I have my controllers on 7.3.7, the feature wasn't available

  DataMotion is subject using flight move command that is unavailable in 7.3.7, but what I did to solve that is to use the command copy of flight, the main steps has been

  1. Create a new volume to act as the destination for your ESXi LUN boot volume in an another aggregate
  2. the volume must be equal to or greater than the space as well as the volume of the source
  3. the volume must be of the same style security
  4. Stop the VM
  5. Stop the ESXi
  6. the ESXi boot LUN offline
  7. new offline created the volume or to limit
  8. Start the copy process copy beginning old_volume new_volume flight
  9. in the old volume offline and online the new volume
  10. Make sure that the LUN is now available in the new path to the new total
  11. Add logical unit number to its initiator group so it is accessible by the ESXi Server
  12. Make sure the logic unit number is online and power on the ESXi
  13. Make sure you connect to your Vcenter server and rescan storage to add the LUN to start if you want

• B22 - M3 and boot from the San with W2008 R2 SP1

  I have a situation rather weired.

  With a tip of SAN service profile

  Associate a B22 - M3

  Boot lun visible

  W2008 R2 SP1 installation on a boot lun (storage HDS) works perfekt

  However, the startup fails! We see from Windows, and then it begins the loop again and again start

  Combining this Service profile even for a B200-M3 factory, Boot from SAN is ok

  Saw?

  Hey Wdey;

  I just wanted you to know that someone I've worked with that was running into the same question, and we found than problems problems was related to the defect below.

  The installation of windows 2008 R2 fails UCS 2.1.3a BIOS

  https://Tools.Cisco.com/bugsearch/bug/ CSCum84618

• install ESXi on UCS to boot from SAN

  Hello

  I have ucs and I need to boot from SAN

  I need to confirm something

  When I was installing WindowsServer the UCS to boot from SAN. I have attached the iso drivers for the HBA driver so that the blade can detect the boot LUN.

  Now, I'm going to install ESXi. Do you know if I need to use the iso as drivers for the HBA as with windows or ESXi detects this and will present me the boot LUN to start the installation?

  We will use the ESXi, VMware no custom of Cisco

  Thank you

  Hello

  A major difference:

  MSFT Windows has no drivers of enic fnic UCS preinstalled with the distribution of iso.

  ESXi has, but most likely not one who demands that the UCS support matrix.

  See http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

  Therefore you install ESXi ISO of the distribution, and then you update the drivers of the enic/fnic

  See http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/vic_driver...

• ID of the LUN duplicate when you use several bays

  I'll put up a new battery of VMware in a large company, where EMC and Netapp without are used.

  I asked a storage engineer to present a RDM on the Netapp SAN LUN. They have gave it a LUN ID 0. Unfortunately, my boot LUN on the EMC also has a LUN ID 0. This resulted in two LUNS tables separated with the ID 0. The targets are different and the paths are all.

  I've never had duplicate LUN like this before and I was wondering if there is a problem, and if it is commonly encountered in many situations of table. Maybe I need to be more specific with SAN engineers whose LUN ID they present at the same time, is this something the SAN engineer chooses their console?

  Do I need to worry about this at all? I screen dumped two LUNs.

  I can tell you that we have duplicated LUN that come from different tables in our environment as well (that I inherited from the previous engineer).  From what I remember the pain only treats that LUN comes easily what follow up dashboard, we have no technical/performance problem that arises from this.

  I make it a point to cut LUN with different identifiers now simply for ease of tracking.

  Hope that helps a little, and someone another chimes in!

• boot from san ESXi 4.1 on IBM Blade

  Hello community,

  I'm trying to BFS on a blade IBM HS22 blade.

  The SAN is a DS4700...

  Then, don't worry pour assign LUNS to the blade, I can mount ISO install ESXi4.1 and boot from it, do the deployment.

  But I can't boot from it at the next restart... Finally half I managed on a blade, and not another (her twin), each with well hidden and separate LUNS.

  Do you have an idea of how to set up the BIOS of the blade (and possibly of the QLogic card) pour booter from SAN?

  On the blade or it works, and ben is totally by chance, in fact...

  If you've done this, and BIOS the who HS22 blade, I'm interested to set up parameters pour un BFS correct!

  Thank you in advance.

  Hi Pilow,

  Activate the of there are BIOS of the HBA cards and tell them about what boot LUN. Take a look at this article for more info.

  A +.

  Franck

• Botting SAN

  Hello!

  I have some doubts about an implememtation.

  The environment consists of a UCS 5100 chassis, Server Blade 4 B200M2 with M81KR and two fabric 6120XP cards. The fabric switch are connected to a switch Brocade fiber 200 c and 5000. Storage is 3160 of NetApp FAS.

  Want to define the profile of a boot server B200M2, which in fact San, we see ports fiber mode shows the 'F '. These ports are connected to the fabric 6120XP. The mode of operation in the fabric is 'ENd Host mode' and fiber ports are listed as "proxy_N." my question is, it is normal in the switches, Brocade, Fibre ports with connection fabric display mode "E"?

  The second question, it must first define a target boot in the profile of the blade of the UCS, or if you first map the LUN 0 to the vHBA (WWPN) in the storage device?

  Thanks in advance, greetings!

  Found as a Windows boot LUN ID of 1. Think any number would work? But 1 is a standard I know that most people use.

  You must have a startup profile aimed at the WWPN of one of more FC ports on your storage device. Example below. In some situations, I do port based zoning and mask just the LUNS to the storage device and others add WWPN zoning (Brocade) as well as base LUN masking.

  

  Craig

• Problem; ESX 5u1, initializing iSCSI on NetApp

  The problem that we see is;  VMware 5u1, even on 5 takes about 90% through the installation/copy of VMware on an 8 GB logical unit number (lun id 0)... .fails with the message "wait 2 start benches, found 0.

  HW configuration as follows;

  FIS 6248

  Blades B-200

  VIC M81KR Palo

  Configured "Device Ports" connection to NetApp 3240-10 GB e1a/e1b

  Firmware 2.0.2M

  Service profile

  assigned iSCSI (cdrom, iSCSI nic overlay) No. MAC startup strategy

  iSCSI boot vNIC, fabric a - no. failover, vLAN 550

  iSCSI_A vNIC, no failover, vLAN 550

  iSCSI_B vNIC, no failover, vLAN 551

  1 Mgmt vNIC fabric failover

  1 VMotion vNIC fabric failover

  VM - A vNIC, fabric failover

  VM - B vNIC, fabric failover

  NetApp 3240 DOT 8.0.2P6 7-mode

  10GB Ports connected to the FI 6248 "device Ports.

  E1A (vlan 550)

  E1B (vlan 551)

  It is a known problem with ESX 5.  At the end of installation to the iSCSI boot LUN, the Setup program tries to re - initialize the adapter iSCSI with a DHCP address.  This fails and kicks on the error you see.  Installation fine filled aura - restart just like you did.

  The VMFS LUNS not created on the start for ESX 5 LUN also is expected behavior.

  Kind regards

  Robert

• UCS connection to SAN switches

  I set up direct UCS in the SAN before, but not San switches to connect.  My understanding of the main differences between the two is as follows:

  (1) with SAN switches, you configure VSAN.  To do this, go to the SAN-> SAN Cloud tab and configure your vSAN ID here.  Then in your vHBA template, configure it to use the proper vSAN ID you configured under cloud of SAN.  Nothing else to do here?

  (2) whereas with direct-attached storage connect FI - A SPA and SPB and FI - B to SPA and SPB, with san switches will FI - A ' switch-1' and FI - B is going to "switch-2'."  Is this correct?  If so, anyone know why it should be that way?

  No problem, tbone-111

  As much as I know, that two vHBAs are supported at this time.  It is best to use 1 from the face and side b 1.

  The vHBAs that are used depend on which WWPN you zoned on your boot LUN.

  For the following example, assume the following group:

  1.) my vHBAs are named vHBA_A1, vHBA_B1, vHBA_A2, vHBA_B2 (A tissue face a and B for b-side)

  (2.) vHBA_A1 is the first HBA on my side, and vHBA_B1 is the first HBA on b-side

  AND

  3.) WWPN of the HBA is zoned properly my boot ports storage processor (SP) of the LUN on the FC switch

  AND

  4.) WWPN of the HBA is hidden correctly on my table LUN

  Those are logical, ANDS, they must ALL be true to prevent headaches later.

  5.) disk Array A0 and B1 SP ports are connected to my A fabric FC switch.  A1 and B0 are connected to my fabric B.

  6.) this example of strategy will start A fabric be the path of MBR

  Best practices - FYI, having at least 2 SAN political Boot (1-A-side, 1 for side b and distribute among your Service profiles).

  In my startup policy, I check the will to apply vHBA naming option and specify my names of vHBAs (sorry I have no screenshots available.  Everything started with a new company and do not yet have access lab).

  My primary SAN parameter can be: the main target: wwpn of A0 and secondary target: B1 wwpn

  My secondary SAN setting can be: the main target: wwpn of B0 and secondary target: A1 wwpn

  It would be a good idea to speak with the Admins of storage while you set up the first two servers to boot on each fabric for all troubleshooting.

  If the zoning and LUN masking are configured correctly, you should see WWPN listed during the boot sequence of UCS server to the point where the starting CF driver is loaded.

  Of course, download TAC Cisco on the line, if you encounter obstacles that you can not go beyond.

  I hope this helps,

  Trevor

  ======================================================================================

  If my answers were useful somehow, please note accordingly.  Thank you!

  Post edited by: Trevor Roberts Jr

• Storage groups

  Hello

  At the start of SAN in UCS, what is the best practice when creating the storage groups in the drive Bay?

  For example, VMware: is it best practice to have a storage group for each ESXi and add its own ESXi Boot LUN (id = 0) and the necessary VM LUN data store?

  Other environments (Linnux, Windows, Hyoer-V) have something special in these terms to support?

  Thank you

  It's a security issue.  Because the LUN ID can be changed easily on the host computer, you could continuously clobber the LUN hurt if your server administrator has incorrectly changed LUN ID.  In addition, once a host is started, it will be able to see & access each LUNS in the storage group independently LUN ID.  The importance of the impacts host LUN ID matches only a host trying to start SAN.

  The two main forms of security applied to the storage is zoning and masking.

  Zoning - on storage switch, acts as an ACL restricting the scope of what can see the members of the zone.  An area will normally contain only a single host and target WWN.  * Who I can see *.

  Masking - on the table limits of storage 'what' LUN a host has access to.  This is done in the form of storage groups.  * What can I access *.

  Either work around poses a great risk to corruption or destruction of data given that different operating systems can be read their native file systems.  E.g. If you had all your hosts in a storage group (ESX, Windows etc.) and tried to separate them only by a LUN ID, a simple change of 1 digit of the start ID LUN on the initiator target could lead a crowd to not read the file system and potentially right a new signature to the risk - replace your existing data.  Windows cannot read a linux partition and vice versa.

  Follow these best practices and your data will be much more safe & secure.

  Kind regards

  Robert

• Service profile of the CISCO UCS for ESXi

  Do you need multiple boot LUN on the storage array for each host that you want to apply the service profile to? I'm just confused, let's say I have 12 blades that I want to designate as boot SAN for ESXi, y aura-t 12 profiles of separate service for each of them, and will need me 12 different LUNS on our storage? I am new to this and I just want to make it as clean as possible! Any help is appreciated.

  Hi Justin,

  You can have the same LUN ID for multiple service profiles, as well as the same target ID. However, your initiators will be different and you will need to configure the zoning on your switch upstream if you use the end host mode.

  Here is a good guide, review the basics and how to put in place.

  http://jeffsaidso.com/2010/11/boot-from-San-101-with-Cisco-UCS/

  Also here is an excellent guide to troubleshooting;

  http://www.Cisco.com/c/en/us/support/docs/servers-unified-computing/UCS-...

  Kind regards

• SAN Multi-pathing recommended?

  Hello

  I have a few questions on multiple paths SAN using UCS.

  I will be detailed for each question.

  1. Since there is no option to switch to vHBA, should use the features underlying the o/s (e.g. ESX/ESXi) MPIO? I think that MPIO for ESX/ESXi is enabled by default but to Win2008, we will need to activate it?
  2. My Clariion Bay has 2 SPS (SP - A and SP - B). Each processor has 2 ports. I have these 2 ports cracks to two MDS with a MDS connection to a fabric of interconnection respectively. Should I create two SAN fabrics for these 2 lanes (2 different VSAN)?
  3. What is the convergence time the host to use a different path of failure? (a few seconds or a minute or two?) This is related to question 2, if, for example, the convergence time should take approximately 1 min +, then it makes no difference with 2 different fabrics of SAN compared to 1, because Let's experience downtime anyway.
  4. I have a LUN (0 logic unit number) of start-up and LUN 1 as the store of data LUNS for each host. Since then, my strategy of UCS start-up (for blade/host 1) aura vHBA1 (Primary-> SP-A/port-0, secondary-> SP-B/port-0) and vHBA2 (Primary-> SP-A/port-1, secondary-> SP-B/port-1), should I give to the property for all LUNS for host1 to SP - A?
     • Will I have problems if I put the boot logical unit number (LUN 0) in SP - A and the data store logic (LUN 1) in SP - B unit number? In this case, I don't know how the selection of the path as the path in writing is always on SP - A, and only in the event of failure of the path or the SP failures, it will use the secondary path. Would appreciate some advice on this

  Thank you.

  Answers online.  Others can chime in if they have any comments or suggestions.

  See you soon,.

  Robert

  steven.pw.lau wrote:
  Hi,
  I have a few questions on SAN Multi-pathing using UCS.
  I will itemized each questions.
  Since there's no failover option for vHBA, we would need to use the underlying MPIO features of the O/S (e.g. ESX/ESXi)? I believe MPIO for ESX/ESXi is enabled by default but for Win2008, we'll need to enable it?
  [Robert] - Correct.  There's a native multipathing pluging (NMP) in VMware, but for Windows you'll need additional config/software.
  2. My Clariion array has 2 Storage Processors (SP-A and SP-B). Each SP has 2 ports. I have these 2 ports meshed to two MDS with one MDS connecting to one Fabric Interconnect respectively. Should I be creating two SAN fabrics for these 2 paths (2 different VSANs)?
  
  [Robert] - Yes.  Connect one VSAN on each FI.  Your FC uplinks will each connect to an upstream MDS (assuming each MDS is not connected to each FI).  You will still have 4 storage paths available to each host using two vHBAs.  3.  What is the convergence time for the host to use another path when failure occurs? (few seconds or a minute or so?) This is related to  question 2 if for example, the convergence time were to take around 1 min+, then it makes no differences having 2 different SAN fabrics as compared to 1 because we'll be experiencing downtime anyway.
  
  [Robert] - Failover for FC traffic is handled by the host, not UCS.  It's up to the host OS to decide how & when to redirect traffic to the alternate path. Normally FC failover is pretty seamless.  FC traffic can't tolerate any lengthy of delays.  As soon as the SCSI command times out, it will jump to the other path. Again, this will vary from OS to OS, but generally its seamless to the application/OS.
  4. I'd like have one boot LUN (LUN 0) and LUN 1 as the datastore LUN for each host. Since, my boot policy in UCS (for blade/host 1) will have vHBA1 (Primary -> SP-A/port-0, Secondary -> SP-B/port-0) and vHBA2 (Primary -> SP-A/port-1, Secondary -> SP-B/port-1), should I give the ownership for all the LUNs for host1 to SP-A?
  
  [Robert]  Yes.  Your primary boot target must be the "owner" of the LUN (and should be the "default" owner for that matter).  Only when SPA fails, will the LUN tresspass to SP-B and the secondary boot path will succeed during server boot up.   Keep in mind, this is only for booting.  Once its up & running, the OS handles failover activities.  5. Will I have problems if I only put the boot LUN (LUN 0) in SP-A and the datastore LUN (LUN 1) in SP-B? For this case, I'm not sure how the path selection will work as the writeable path is always on SP-A and only if path failure occurs or SP failures, it will only use the secondary path. Would appreciate some advice on this
  [Robert] Boot policy & data path selection are two different things.  If your boot LUN is targeting SPA, it will likely maintain that path as the OS loads.  Once the OS loads you can manipulate the path for any LUN. If desired you could set the "Active" path of your Datastore LUN within vCenter to be the other SP (SPB in your case) by modifying the path selection policy and setting it to "Fixed" PSP.  The default Path Selection Policy is MRU (Most recently Used).  This is normally adequate, but if you want to manually load balance your traffic the Fixed PSP policy is the way to go.
  

  Thank you.

• Operation of ESXi installation failed

  Hi guys,.

  For a new installation of ESXi 5.1, the storage team gave a LUN to start 10 GB of our EMC symmetrix storage box. When I try to install the ESXi by selecting the LUN to 10 GB I get this error below.

  This program has encountered an error:

  (Use the arrows to schoo)

  Error (see the log for more information)

  vmkfstools failed with the message: create fs deviceName: "devices/vmfs / '.

  / disks/naa. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:8', fsShortName: 'vfat ',.

  FSName: '(null)'

  ' / vmfs/devices/drives/naa. "is not a valid absolute or relative path

  Could not resolve the path for device name

  / VMFS, Devices, Disks, NAA. XXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  Usage: vmkfstools - C [vmfs3 | vmfs5] / vmfs/devices/disks/vml... or,

  vmkfstools - C [vmfs3 | vmfs5] / vmfs/devices/disks/naa... or,

  ' vmkfstools - C [vmfs3 | vmfs5].

  /VMFS/devices/disks/MPX.vmhbaA:T:L:P

  Error: no such file or directory

  A doubt, is that the storage team gave ID LUN 1. I heard that the boot LUN must be 0. Will this be a problem? And they have already set up multiple paths to the storage array. Which will cause a problem?

  Sorry guys, the storage team forgot to bring the disks online. Its solved now. Thank you.

• Best way to prevent storage being added to the PVDC in vCD 5.1

  Hello

  
  With vCloud Director 1.5 when I created a new provider vDC I was showed all storages available data presented to my vCenter and can choose exactly which ones I would include in the pVDC.

  
  I have now deployed vCloud Director 5.1 Although my ESXi hosts are still 5.0 and the option seems to have changed. Know you're just given the choice of * (Any) for storage profiles and each data store moves the pVDC.

  It is a problem for me because all my boot LUN be included wihin the pVDC as available storage, and clearly is not what they are.

  I know I can go in the tab manage and monitor, select data warehouse, and groups of the left and then manually disable each of my boot Lun, but it is not just that I have to include a logic unit number inside a pVDC and then turn it off.

  
  I do it the only way possible?

  
  Oh, by the way I forgot to mention that we do not use storage profiles and have no storage vendors set up in vCenter. It's because I have not loaded plug-ins of table to determine the types of disc.

  Well, storage profiles do the trick. Even if your storage array has no built-in storage capacity, you can define your own functions, add the ability to all stores of data type and functions to a profile of storage. You can then add clusters of storages of data/store data based on a profile for the provider vdc.

  Of course there are profiles of storage and the right edition of vSphere.

  It's only a short secription how to do, but the documentation for vmware is pretty good about this

• Reclassification of 5.0 to 5.1 issue with iSCSI

  I have a number of HP BL490c G7 SAN EMC e via flexible HP 10 virtual connect network.

  With esxi 5.0 U1, could see the LUN and boot from SAN, which was great.

  I used VUM 5.1 update after update vCenter.

  The update process failed leaving me with a black screen on the console startup esxi indicating the installation script failed, pressing enter just rebooted.

  I deleted and then re-created the boot LUN and I install from scratch, 5.1 when I boot from the ISO image, he is unable to see any external storage to install to, 5.0 U1 still shows any fine the LUN during the installation process, so I know the material is always good and esxi 5.0 U1 still works fine.

  If something has changed for the iSCSI HBA support between U1 5.0 and 5.1?

  Is that what I can do to get this working?

  Thanks in advance.

  OK, looks like the images are missing the driver necessary be2iscsi for iSCSI independent material, to ESXi vanilla as well as HP Custom ISO:

  ~ software # esxcli profile
  (Updated) HP-ESXi - 5.1.0 - standard-iso
  Name: (updated) HP-ESXi - 5.1.0 - standard-iso
  Seller: host01.local
  Creation date: 2012-09 - 17 T 05: 22:29
  Modification date: 2012-09 - 25 T 08: 57:20
  Loan without a State: false
  Description:

  2012 09-17 T 05: + 00:00 22:29.656115: are the following VIBs
  installed:
  epsec-mux 5.1.0 - 757363
  ----------
  2012 09-13 T 18: + 00:00 30:35.687583: are the following VIBs
  installed:
  VMware-fdm 5.1.0 - 799731
  ----------
  Profile of customized HP for ESXi 5.1.0 ISO Image

  [...]

  ~ List of the vib # esxcli software | grep be2net
  NET-be2net 4.1.255.11 - 1vmw.510.0.0.799733 VMware VMwareCertified 2012-09-12
  ~ List of the vib # esxcli software | grep be2iscsi

  [Nothing]

  Picture of HP information list nor a updated driver be2iscsi:

  http://h18004.www1.HP.com/products/servers/Software/VMware-ESXi/driver_version.html

  Image 5.0 has a SCSI-BE2. V00 file that contains the driver be2iscsi. I don't know why they failed in 5.1 ESXi.

  Try to manually add the be2iscsi driver to your image:

  https://my.VMware.com/Web/VMware/details?downloadGroup=DT-ESX50-Emulex-be2iscsi-413343&ProductID=229

  http://v-front.blogspot.de/p/ESXi-customizer.html

  And to your original question around change 5.1 to hardware iSCSI, they have added support for frames:

  http://cormachogan.com/2012/09/10/vSphere-5-1-storage-enhancements-part-5-storageprotocols/