Hi, can anyone help me about i cant see my san storage in one of my esx?, i dont know what happen, only that the storage its ok and online, we didnt make any configuration, but we cant access, it doesnt appear in the esx....
You can take a look at page 134 of this document and the below thread. For some reason ESX is seeing the LUN as a replica of the original. Any changes made on the SAN? A LUN ID change could produce this.
http://www.vmware.com/pdf/vi3_301_201_san_cfg.pdf
http://www.vmware.com/community/message.jspa?messageID=364352#364352
The error in the console is:
cpu1:1034)LVM:4903:vmhba0:0:6:1 may be snapshot: disabling access. See reasignaturing section in SAN config Guide.
The disk that doesnt appear, when i go to add storage, it let me add it, but formatting it!
how can i do the reasignature??
thanks
Hi
issues with Displaying the Same LUN IDs Across Hosts
Normally, a LUN appears with the same LUN ID to all hosts that access the LUN. On
some arrays, however, it may not be possible to display the LUN with the same LUN
ID across hosts. As a result, the ESX Server system incorrectly detects the LUN as a
snapshot and places it offline.
Examples of storage arrays for which the same LUN ID may not be visible for a given
LUN across hosts are Clariion AX100 and few IBM TotalStorage Enterprise Storage
Systems (previously Shark Storage systems).
NOTE Any virtual machines on this new snapshot volume are not auto‐discovered. You
have to manually register the virtual machines.
SAN Configuration Guide
114 VMware, Inc.
To resolve issues with invisible LUNs on certain arrays
1 In the VI Client, select the host in the inventory panel.
2 Click the Configuration tab and click Advanced Settings.
3 Select LVM in the left panel and set LVM.DisallowSnapshotLUN to 0 in the right
panel.
4 Rescan all VMFS volumes.
After the rescan, all VMFS volumes are available.
Hope this helps
cpu1:1034)LVM:4903:vmhba0:0:6:1 may be snapshot: disabling access. See reasignaturing section in SAN config Guide.
http://www.vmware.com/pdf/vi3_esx_san_cfg.pdf - Page 113.
You can take a look at page 134 of this document and the below thread. For some reason ESX is seeing the LUN as a replica of the original. Any changes made on the SAN? A LUN ID change could produce this.
http://www.vmware.com/pdf/vi3_301_201_san_cfg.pdf
http://www.vmware.com/community/message.jspa?messageID=364352#364352
