vSphere 7 PetaSan Storage iSCSI adaptor path status not used
EungwangKim
1 Post
December 8, 2022, 3:00 amQuote from EungwangKim on December 8, 2022, 3:00 amvSphere 7 PetaSan Storage iSCSI adaptor path status not used
Currently, the iscsi setup is done in petasan and the iscsi initiator setup in DC to complete the drive installation. In order to be used as an iscsi storage device via vsphere 7, you have completed the separation of iscsi and nicks using other services through port binding with the isolation switch in vsphere.
I added iscsi adapter, set the network port binding, and designated it as a petasan address with Dynamic Discovery, but the path status does not use, so how should I solve it?
I'm a beginner, so I'm not good enough.
vSphere 7 PetaSan Storage iSCSI adaptor path status not used
Currently, the iscsi setup is done in petasan and the iscsi initiator setup in DC to complete the drive installation. In order to be used as an iscsi storage device via vsphere 7, you have completed the separation of iscsi and nicks using other services through port binding with the isolation switch in vsphere.
I added iscsi adapter, set the network port binding, and designated it as a petasan address with Dynamic Discovery, but the path status does not use, so how should I solve it?
I'm a beginner, so I'm not good enough.
Last edited on December 8, 2022, 3:11 am by EungwangKim · #1
admin
2,930 Posts
December 8, 2022, 11:23 amQuote from admin on December 8, 2022, 11:23 amWe have a vmware guide in our documentation page which should help.
make sure the PetaSAN iSCSI disk is started and displays its path ips, use any of the ips for dynamic discovery on the vmware side. make sure from vmware you can ping this ip as well as other ips for disk paths, if you cannot ping then check your network setup.
We have a vmware guide in our documentation page which should help.
make sure the PetaSAN iSCSI disk is started and displays its path ips, use any of the ips for dynamic discovery on the vmware side. make sure from vmware you can ping this ip as well as other ips for disk paths, if you cannot ping then check your network setup.
vSphere 7 PetaSan Storage iSCSI adaptor path status not used
EungwangKim
1 Post
Quote from EungwangKim on December 8, 2022, 3:00 amvSphere 7 PetaSan Storage iSCSI adaptor path status not used
Currently, the iscsi setup is done in petasan and the iscsi initiator setup in DC to complete the drive installation. In order to be used as an iscsi storage device via vsphere 7, you have completed the separation of iscsi and nicks using other services through port binding with the isolation switch in vsphere.
I added iscsi adapter, set the network port binding, and designated it as a petasan address with Dynamic Discovery, but the path status does not use, so how should I solve it?
I'm a beginner, so I'm not good enough.
vSphere 7 PetaSan Storage iSCSI adaptor path status not used
Currently, the iscsi setup is done in petasan and the iscsi initiator setup in DC to complete the drive installation. In order to be used as an iscsi storage device via vsphere 7, you have completed the separation of iscsi and nicks using other services through port binding with the isolation switch in vsphere.
I added iscsi adapter, set the network port binding, and designated it as a petasan address with Dynamic Discovery, but the path status does not use, so how should I solve it?
I'm a beginner, so I'm not good enough.
admin
2,930 Posts
Quote from admin on December 8, 2022, 11:23 amWe have a vmware guide in our documentation page which should help.
make sure the PetaSAN iSCSI disk is started and displays its path ips, use any of the ips for dynamic discovery on the vmware side. make sure from vmware you can ping this ip as well as other ips for disk paths, if you cannot ping then check your network setup.
We have a vmware guide in our documentation page which should help.
make sure the PetaSAN iSCSI disk is started and displays its path ips, use any of the ips for dynamic discovery on the vmware side. make sure from vmware you can ping this ip as well as other ips for disk paths, if you cannot ping then check your network setup.