Skip to main content

How to present a iscsi lun to a linux machine for creating file system

 

On the linux machine :

1)Find out the iscsi name of the host:

cat /etc/iscsi/initiatorname.iscsi

note:in RHEL install "yum install iscsi-initiator-utils" if initiatorname.iscsi not found

2)discover the target storage array using iscsi target IP:

iscsiadm -m discovery -t st -p <target IP>

this output will be having iqn number about the storage target


3)make an iscsi I-T session on the host:

iscsiadm -m node -T <IQN of target>  -p <target IP> --login


4)verify the IT connection session by:

iscsiadm -m session


5)present a LUN from array and export to the host using IQN of the host


6)After LUN presented do a rescan of iscsi device by:

rescan-scsi-bus.sh

7)Create a new file sytstem on the new device and mount

mkfs /dev/sdb 

mkdir /mount1

mount /dev/sdb /mount1



Comments

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported