New iSCSI drive in vCenter showing up as "Not Consumed"
bill gottlieb
26 Posts
May 4, 2023, 4:31 pmQuote from bill gottlieb on May 4, 2023, 4:31 pmI have a vCenter running vSphere 6.7.0.40000 with several hosts (m610, m620, r720XD) running ESXi 6.0.0, 13635687.
We have an existing PetaSAN 2.3.1 cluster which has been running for several years on seven (7) Dell c2100 servers. This works fine.
I tried adding a new PetaSAN cluster running 3.1.0 using four (4) Dell R720XD servers using the same iSCSI 1 and 2 VLANs and subnets, but different IP ranges in the same subnet and different IQNs. When I try adding the newly created iSCSI disk to the ESXi hosts, the dynamic discovery works, all of the paths are established, the correct capacity is displayed but the datastore lists "Not Consumed" rather than the name of the disk, and it does not show up as a datastore in the lists.
I thought maybe this was an issue with v3.1.0, so I rebuilt the cluster using the 2.3.1 version we are currently using, but still get the same results.
Wondering if anyone has run into this same situation previously (I searched the forum but did not find anything...) or could possibly provide pointers.
Thanking in advance....
I have a vCenter running vSphere 6.7.0.40000 with several hosts (m610, m620, r720XD) running ESXi 6.0.0, 13635687.
We have an existing PetaSAN 2.3.1 cluster which has been running for several years on seven (7) Dell c2100 servers. This works fine.
I tried adding a new PetaSAN cluster running 3.1.0 using four (4) Dell R720XD servers using the same iSCSI 1 and 2 VLANs and subnets, but different IP ranges in the same subnet and different IQNs. When I try adding the newly created iSCSI disk to the ESXi hosts, the dynamic discovery works, all of the paths are established, the correct capacity is displayed but the datastore lists "Not Consumed" rather than the name of the disk, and it does not show up as a datastore in the lists.
I thought maybe this was an issue with v3.1.0, so I rebuilt the cluster using the 2.3.1 version we are currently using, but still get the same results.
Wondering if anyone has run into this same situation previously (I searched the forum but did not find anything...) or could possibly provide pointers.
Thanking in advance....
admin
2,930 Posts
May 4, 2023, 7:38 pmQuote from admin on May 4, 2023, 7:38 pmFrom ESXi, can you ping both ip paths on both subnets ? can you ping the other way around from PetaSAN to both ips on the ESXi ?
From ESXi, can you ping both ip paths on both subnets ? can you ping the other way around from PetaSAN to both ips on the ESXi ?
bill gottlieb
26 Posts
May 5, 2023, 1:05 amQuote from bill gottlieb on May 5, 2023, 1:05 amYes.
From ESXi:
[root@m620-43g-2015:~] ping 10.0.2.30
PING 10.0.2.30 (10.0.2.30): 56 data bytes
64 bytes from 10.0.2.30: icmp_seq=0 ttl=64 time=0.148 ms
64 bytes from 10.0.2.30: icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from 10.0.2.30: icmp_seq=2 ttl=64 time=0.081 ms
--- 10.0.2.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.076/0.102/0.148 ms
[root@m620-43g-2015:~] ping 10.0.3.30
PING 10.0.3.30 (10.0.3.30): 56 data bytes
64 bytes from 10.0.3.30: icmp_seq=0 ttl=64 time=0.167 ms
64 bytes from 10.0.3.30: icmp_seq=1 ttl=64 time=0.068 ms
64 bytes from 10.0.3.30: icmp_seq=2 ttl=64 time=0.070 ms
--- 10.0.3.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.068/0.102/0.167 ms
From PetaSAN:
root@petasan-12:~# ping 10.0.2.215
PING 10.0.2.215 (10.0.2.215) 56(84) bytes of data.
64 bytes from 10.0.2.215: icmp_seq=1 ttl=64 time=0.116 ms
64 bytes from 10.0.2.215: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 10.0.2.215: icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from 10.0.2.215: icmp_seq=4 ttl=64 time=0.063 ms
^C
--- 10.0.2.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3070ms
rtt min/avg/max/mdev = 0.050/0.071/0.116/0.027 ms
root@petasan-12:~# ping 10.0.3.215
PING 10.0.3.215 (10.0.3.215) 56(84) bytes of data.
64 bytes from 10.0.3.215: icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from 10.0.3.215: icmp_seq=2 ttl=64 time=0.063 ms
64 bytes from 10.0.3.215: icmp_seq=3 ttl=64 time=0.053 ms
64 bytes from 10.0.3.215: icmp_seq=4 ttl=64 time=0.053 ms
^C
--- 10.0.3.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3050ms
rtt min/avg/max/mdev = 0.053/0.059/0.070/0.011 ms
root@petasan-12:~#
Yes.
From ESXi:
[root@m620-43g-2015:~] ping 10.0.2.30
PING 10.0.2.30 (10.0.2.30): 56 data bytes
64 bytes from 10.0.2.30: icmp_seq=0 ttl=64 time=0.148 ms
64 bytes from 10.0.2.30: icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from 10.0.2.30: icmp_seq=2 ttl=64 time=0.081 ms
--- 10.0.2.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.076/0.102/0.148 ms
[root@m620-43g-2015:~] ping 10.0.3.30
PING 10.0.3.30 (10.0.3.30): 56 data bytes
64 bytes from 10.0.3.30: icmp_seq=0 ttl=64 time=0.167 ms
64 bytes from 10.0.3.30: icmp_seq=1 ttl=64 time=0.068 ms
64 bytes from 10.0.3.30: icmp_seq=2 ttl=64 time=0.070 ms
--- 10.0.3.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.068/0.102/0.167 ms
From PetaSAN:
root@petasan-12:~# ping 10.0.2.215
PING 10.0.2.215 (10.0.2.215) 56(84) bytes of data.
64 bytes from 10.0.2.215: icmp_seq=1 ttl=64 time=0.116 ms
64 bytes from 10.0.2.215: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 10.0.2.215: icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from 10.0.2.215: icmp_seq=4 ttl=64 time=0.063 ms
^C
--- 10.0.2.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3070ms
rtt min/avg/max/mdev = 0.050/0.071/0.116/0.027 ms
root@petasan-12:~# ping 10.0.3.215
PING 10.0.3.215 (10.0.3.215) 56(84) bytes of data.
64 bytes from 10.0.3.215: icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from 10.0.3.215: icmp_seq=2 ttl=64 time=0.063 ms
64 bytes from 10.0.3.215: icmp_seq=3 ttl=64 time=0.053 ms
64 bytes from 10.0.3.215: icmp_seq=4 ttl=64 time=0.053 ms
^C
--- 10.0.3.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3050ms
rtt min/avg/max/mdev = 0.053/0.059/0.070/0.011 ms
root@petasan-12:~#
bill gottlieb
26 Posts
May 9, 2023, 12:03 pmQuote from bill gottlieb on May 9, 2023, 12:03 pmHello..
Is there anything else you would suggest looking at?
Hello..
Is there anything else you would suggest looking at?
admin
2,930 Posts
May 9, 2023, 10:51 pmQuote from admin on May 9, 2023, 10:51 pmFrom what i understand: 2 PetaSAN clusters of the same version connected to the same ESXi client, one works but not the other. It is ost probably configuration problem. Can you try to access the other cluster from a different client environment ?
From what i understand: 2 PetaSAN clusters of the same version connected to the same ESXi client, one works but not the other. It is ost probably configuration problem. Can you try to access the other cluster from a different client environment ?
bill gottlieb
26 Posts
May 9, 2023, 11:37 pmQuote from bill gottlieb on May 9, 2023, 11:37 pmUnfortunately, I have only the single vSphere environment.
Unfortunately, I have only the single vSphere environment.
admin
2,930 Posts
May 10, 2023, 10:32 amQuote from admin on May 10, 2023, 10:32 amMaybe change the configuratoin: ip subnet/range, iqn base string..it must be a config issue.
Maybe change the configuratoin: ip subnet/range, iqn base string..it must be a config issue.
bill gottlieb
26 Posts
May 10, 2023, 11:54 amQuote from bill gottlieb on May 10, 2023, 11:54 amI cannot change the IP subnet, as I would have to change the iSCSI adapter networking, which would break the existing PetaSAN connections.
I have modified the IP ranges to a different range in the same subnet and changed the iqn base string. Detached and re-attached the iSCSI drive. Still have the same issue.
Can I provide any specific logs or capture a pcap to send?
I cannot change the IP subnet, as I would have to change the iSCSI adapter networking, which would break the existing PetaSAN connections.
I have modified the IP ranges to a different range in the same subnet and changed the iqn base string. Detached and re-attached the iSCSI drive. Still have the same issue.
Can I provide any specific logs or capture a pcap to send?
bill gottlieb
26 Posts
May 10, 2023, 5:03 pmQuote from bill gottlieb on May 10, 2023, 5:03 pmAs you stated, we had a datastore misconfiguration issue, We have resolved this and are now able to mount the datastore properly. Thank you for your help and advice!
As you stated, we had a datastore misconfiguration issue, We have resolved this and are now able to mount the datastore properly. Thank you for your help and advice!
admin
2,930 Posts
May 11, 2023, 10:33 amQuote from admin on May 11, 2023, 10:33 amGood to hear..thanks for the feedback.
Good to hear..thanks for the feedback.
New iSCSI drive in vCenter showing up as "Not Consumed"
bill gottlieb
26 Posts
Quote from bill gottlieb on May 4, 2023, 4:31 pmI have a vCenter running vSphere 6.7.0.40000 with several hosts (m610, m620, r720XD) running ESXi 6.0.0, 13635687.
We have an existing PetaSAN 2.3.1 cluster which has been running for several years on seven (7) Dell c2100 servers. This works fine.
I tried adding a new PetaSAN cluster running 3.1.0 using four (4) Dell R720XD servers using the same iSCSI 1 and 2 VLANs and subnets, but different IP ranges in the same subnet and different IQNs. When I try adding the newly created iSCSI disk to the ESXi hosts, the dynamic discovery works, all of the paths are established, the correct capacity is displayed but the datastore lists "Not Consumed" rather than the name of the disk, and it does not show up as a datastore in the lists.
I thought maybe this was an issue with v3.1.0, so I rebuilt the cluster using the 2.3.1 version we are currently using, but still get the same results.
Wondering if anyone has run into this same situation previously (I searched the forum but did not find anything...) or could possibly provide pointers.
Thanking in advance....
I have a vCenter running vSphere 6.7.0.40000 with several hosts (m610, m620, r720XD) running ESXi 6.0.0, 13635687.
We have an existing PetaSAN 2.3.1 cluster which has been running for several years on seven (7) Dell c2100 servers. This works fine.
I tried adding a new PetaSAN cluster running 3.1.0 using four (4) Dell R720XD servers using the same iSCSI 1 and 2 VLANs and subnets, but different IP ranges in the same subnet and different IQNs. When I try adding the newly created iSCSI disk to the ESXi hosts, the dynamic discovery works, all of the paths are established, the correct capacity is displayed but the datastore lists "Not Consumed" rather than the name of the disk, and it does not show up as a datastore in the lists.
I thought maybe this was an issue with v3.1.0, so I rebuilt the cluster using the 2.3.1 version we are currently using, but still get the same results.
Wondering if anyone has run into this same situation previously (I searched the forum but did not find anything...) or could possibly provide pointers.
Thanking in advance....
admin
2,930 Posts
Quote from admin on May 4, 2023, 7:38 pmFrom ESXi, can you ping both ip paths on both subnets ? can you ping the other way around from PetaSAN to both ips on the ESXi ?
From ESXi, can you ping both ip paths on both subnets ? can you ping the other way around from PetaSAN to both ips on the ESXi ?
bill gottlieb
26 Posts
Quote from bill gottlieb on May 5, 2023, 1:05 amYes.
From ESXi:
[root@m620-43g-2015:~] ping 10.0.2.30
PING 10.0.2.30 (10.0.2.30): 56 data bytes
64 bytes from 10.0.2.30: icmp_seq=0 ttl=64 time=0.148 ms
64 bytes from 10.0.2.30: icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from 10.0.2.30: icmp_seq=2 ttl=64 time=0.081 ms--- 10.0.2.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.076/0.102/0.148 ms
[root@m620-43g-2015:~] ping 10.0.3.30
PING 10.0.3.30 (10.0.3.30): 56 data bytes
64 bytes from 10.0.3.30: icmp_seq=0 ttl=64 time=0.167 ms
64 bytes from 10.0.3.30: icmp_seq=1 ttl=64 time=0.068 ms
64 bytes from 10.0.3.30: icmp_seq=2 ttl=64 time=0.070 ms--- 10.0.3.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.068/0.102/0.167 ms
From PetaSAN:root@petasan-12:~# ping 10.0.2.215
PING 10.0.2.215 (10.0.2.215) 56(84) bytes of data.
64 bytes from 10.0.2.215: icmp_seq=1 ttl=64 time=0.116 ms
64 bytes from 10.0.2.215: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 10.0.2.215: icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from 10.0.2.215: icmp_seq=4 ttl=64 time=0.063 ms
^C
--- 10.0.2.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3070ms
rtt min/avg/max/mdev = 0.050/0.071/0.116/0.027 ms
root@petasan-12:~# ping 10.0.3.215
PING 10.0.3.215 (10.0.3.215) 56(84) bytes of data.
64 bytes from 10.0.3.215: icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from 10.0.3.215: icmp_seq=2 ttl=64 time=0.063 ms
64 bytes from 10.0.3.215: icmp_seq=3 ttl=64 time=0.053 ms
64 bytes from 10.0.3.215: icmp_seq=4 ttl=64 time=0.053 ms
^C
--- 10.0.3.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3050ms
rtt min/avg/max/mdev = 0.053/0.059/0.070/0.011 ms
root@petasan-12:~#
Yes.
From ESXi:
[root@m620-43g-2015:~] ping 10.0.2.30
PING 10.0.2.30 (10.0.2.30): 56 data bytes
64 bytes from 10.0.2.30: icmp_seq=0 ttl=64 time=0.148 ms
64 bytes from 10.0.2.30: icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from 10.0.2.30: icmp_seq=2 ttl=64 time=0.081 ms
--- 10.0.2.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.076/0.102/0.148 ms
[root@m620-43g-2015:~] ping 10.0.3.30
PING 10.0.3.30 (10.0.3.30): 56 data bytes
64 bytes from 10.0.3.30: icmp_seq=0 ttl=64 time=0.167 ms
64 bytes from 10.0.3.30: icmp_seq=1 ttl=64 time=0.068 ms
64 bytes from 10.0.3.30: icmp_seq=2 ttl=64 time=0.070 ms
--- 10.0.3.30 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.068/0.102/0.167 ms
From PetaSAN:
root@petasan-12:~# ping 10.0.2.215
PING 10.0.2.215 (10.0.2.215) 56(84) bytes of data.
64 bytes from 10.0.2.215: icmp_seq=1 ttl=64 time=0.116 ms
64 bytes from 10.0.2.215: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 10.0.2.215: icmp_seq=3 ttl=64 time=0.050 ms
64 bytes from 10.0.2.215: icmp_seq=4 ttl=64 time=0.063 ms
^C
--- 10.0.2.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3070ms
rtt min/avg/max/mdev = 0.050/0.071/0.116/0.027 ms
root@petasan-12:~# ping 10.0.3.215
PING 10.0.3.215 (10.0.3.215) 56(84) bytes of data.
64 bytes from 10.0.3.215: icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from 10.0.3.215: icmp_seq=2 ttl=64 time=0.063 ms
64 bytes from 10.0.3.215: icmp_seq=3 ttl=64 time=0.053 ms
64 bytes from 10.0.3.215: icmp_seq=4 ttl=64 time=0.053 ms
^C
--- 10.0.3.215 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3050ms
rtt min/avg/max/mdev = 0.053/0.059/0.070/0.011 ms
root@petasan-12:~#
bill gottlieb
26 Posts
Quote from bill gottlieb on May 9, 2023, 12:03 pmHello..
Is there anything else you would suggest looking at?
Hello..
Is there anything else you would suggest looking at?
admin
2,930 Posts
Quote from admin on May 9, 2023, 10:51 pmFrom what i understand: 2 PetaSAN clusters of the same version connected to the same ESXi client, one works but not the other. It is ost probably configuration problem. Can you try to access the other cluster from a different client environment ?
From what i understand: 2 PetaSAN clusters of the same version connected to the same ESXi client, one works but not the other. It is ost probably configuration problem. Can you try to access the other cluster from a different client environment ?
bill gottlieb
26 Posts
Quote from bill gottlieb on May 9, 2023, 11:37 pmUnfortunately, I have only the single vSphere environment.
Unfortunately, I have only the single vSphere environment.
admin
2,930 Posts
Quote from admin on May 10, 2023, 10:32 amMaybe change the configuratoin: ip subnet/range, iqn base string..it must be a config issue.
Maybe change the configuratoin: ip subnet/range, iqn base string..it must be a config issue.
bill gottlieb
26 Posts
Quote from bill gottlieb on May 10, 2023, 11:54 amI cannot change the IP subnet, as I would have to change the iSCSI adapter networking, which would break the existing PetaSAN connections.
I have modified the IP ranges to a different range in the same subnet and changed the iqn base string. Detached and re-attached the iSCSI drive. Still have the same issue.Can I provide any specific logs or capture a pcap to send?
I cannot change the IP subnet, as I would have to change the iSCSI adapter networking, which would break the existing PetaSAN connections.
I have modified the IP ranges to a different range in the same subnet and changed the iqn base string. Detached and re-attached the iSCSI drive. Still have the same issue.
Can I provide any specific logs or capture a pcap to send?
bill gottlieb
26 Posts
Quote from bill gottlieb on May 10, 2023, 5:03 pmAs you stated, we had a datastore misconfiguration issue, We have resolved this and are now able to mount the datastore properly. Thank you for your help and advice!
As you stated, we had a datastore misconfiguration issue, We have resolved this and are now able to mount the datastore properly. Thank you for your help and advice!
admin
2,930 Posts
Quote from admin on May 11, 2023, 10:33 amGood to hear..thanks for the feedback.
Good to hear..thanks for the feedback.