vmkernel log message says the creation of WWPN failed. I installed ESX, created VM with Storage as RDM, physical. i have a doubt whether i forgot some steps? i am not able to see the Virtual WWPN generated by ESX, in Brocade 5000 SAN switch. If you are using a BladeCenter or something like that it may differ slightly. I am using a 2U IBM server in my configurations for both of my ESX Servers. then you have to edit the vm.vmx configruation file and change the setting ffrom scsi0:0 Present = TRUE to scsi0:0 Present = FALSE. Also, if you reboot the VM and it will not let you start it up giving you an error that says in can't find scsi0:0. If you created the hard drive on the VM first as I did, you probably ended up with a RDM disk called scsi0:0 of 0MB, if so, delete this drive from your VM as it is obviously has no space to use.
#Brocade san switch concepts windows#
(you might have to rescan for disk in Windows if you don't see it) Now go to the VM and add the drive and pick the new LUN as the RDM disk. Once this is done then I had to rescan the Storage Adapters in VirtualCenter Server. I turned off the NPIV option and masked the LUN to the physical HBAs of the physical ESX Server(s). Click Finish to complete your virtual machine, or optionally perform additional configuration (see ). On the Ready to Complete New Virtual Machine page, review your selections. On the Specify Advanced Options page, you can change the virtual device node and click Next. Subsequent screens offer different options, depending on your choice. When you clone the disk, make a template out of it, or migrate it (if the migration involves copying the disk), the contents of the LUN are copied into a virtual disk (.vmdk) file. Virtual compatibility allows the LUN to behave as if it were a virtual disk, so you can use features like disk modes. Virtual compatibility mode allows the virtual machine to use VMware snapshots and other advanced functionality. However, a LUN configured for physical compatibility cannot be cloned, made into a template, or migrated if the migration involves copying the disk. Physical compatibility is useful if you are using SAN-aware applications in the virtual machine. Physical compatibility mode allows the guest operating system to access the hardware directly. Select a compatibility mode, either physical or virtual. Select a datastore onto which to map the LUN.
You cannot deploy a virtual machine from a template and store its data on a LUN you can only store its data in a virtual disk file.|įrom the Select a Disk page, select Mapped SAN LUN. vmdk extension, but the file contains only disk information describing the mapping to the LUN on the ESX Server system. Encapsulating disk information in a file allows VirtualCenter to lock the LUN so that only one virtual machine can write to it. When you map a LUN to a VMFS volume, VirtualCenter creates a file that points to the raw LUN. This is useful if you are running applications in your virtual machines that must know the physical characteristics of the storage device. Mapping a SAN LUN For virtual machines running on an ESX Server host, instead of storing virtual machine data in a virtual disk file, you can store the data directly on a SAN LUN. Well first of all, we need to go to the Web Management for our Brocade switch which is usually (change ip_address with your own IP, duh!) and login.You are heading down the right path - you will attach an RDM to your VM which will allow you to access a raw lun on the SAN - follow the below instructions. In my case, the other IDs are 115 and 116, so we will give this one another ID of 17 for example.
OK! So now that we have our physical connection in place, let’s go into the Brocade and configure those ports.Īnother very important step is to make sure the Switch ID is different from the others.
#Brocade san switch concepts Patch#
If you are using patch panels in the middle, make sure you are connecting to the correct ports. Switch A -> Port 15 to Switch B -> port 15 where again the modules are the same and the cables are the same. The physical connection would look like this: Usually we would connect the same port number on both switches, but that’s not required. If our switches are in different locations and the distance is over 400m or 1300ft or 0.2mi (yeah I love that distance conversion), we will need to use a LW (Long Wave) module, which in general has as blue latch, and to use SM cables (Single-Mode) for long distances. If the switches are close to one another, we can use a standard SW (Short Wave) module with a minimum of a OM3 (Blue) cable or Multi-Mode cable.