ESXI 6.0 HELP

[bobkalil]

Dear all,

I have a nas storage was configured with esxi 6.0 connected to 2 HP CURVE switches. Unfortunately, both switches were reset to default.  Now esxi can't connect to the datastore from the nas and all the vm installed in the nas server. Plaese help!

the first screenshot is the esxi and the secnd one is Nas storage.

[IRIX201110141]

Try a vmkping from the esxi command line to reach the NAS. You didnt have provide Details about the VMKs so its not clear if you have configured Jumbo frames or not. If you can ping the NAS try a Storage Rescan on ESXi otherwise you have to reboot the ESXi.  Iam not sure how ESX 6.0 reacts on PDL/APD with NFS.

Regards,
Joerg

[berndweyand]

do you have iscsi oder nfs storage ?

over which of the ip´s does the nas provide the storage ?

i am wondering that vswitch1/2 doesnt have uplinks

[bobkalil]

Hello,

here are the cnfigs for the nas ip's:

eth0      Link encap:Ethernet  HWaddr 00:30:48:35:d3:d2

          inet addr:192.168.1.8  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::230:48ff:fe35:d3d2/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:235323 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1168 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:23459212 (22.3 MiB)  TX bytes:117371 (114.6 KiB)

          Interrupt:18 Memory:d8120000-d8140000

eth2      Link encap:Ethernet  HWaddr 00:1b:21:0b:7a:e8

          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0

          inet6 addr: fe80::21b:21ff:fe0b:7ae8/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:234727 errors:0 dropped:0 overruns:0 frame:0

          TX packets:630 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:22465316 (21.4 MiB)  TX bytes:55796 (54.4 KiB)

eth3      Link encap:Ethernet  HWaddr 00:1b:21:0b:7a:e9

          inet addr:192.168.20.1  Bcast:192.168.20.255  Mask:255.255.255.0

          inet6 addr: fe80::21b:21ff:fe0b:7ae9/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:236296 errors:0 dropped:0 overruns:0 frame:0

          TX packets:950 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:22594901 (21.5 MiB)  TX bytes:69236 (67.6 KiB)

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:86 errors:0 dropped:0 overruns:0 frame:0

          TX packets:86 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:8360 (8.1 KiB)  TX bytes:8360 (8.1 KiB)

I'm trying to ping this ip's but no luck the problem is the I can ping the esxi ip 192.168.1.13 success pinging the nas ip success 192.168.1.8 but pinging from esxi 192.168.10.1 and 192.168.20.1 no luck, again the switch doesn't have and vlan and the ip for the switch is 10.11.111.200.

I'm trying to rescan database and reboot the esxi but no luck to mount again the datastore.

[bobkalil]

pinging from esxi to nas

[berndweyand]

but regardless of iscsi or nfs-storage - your vswitches 1 & 2 have no uplinks but have the vmkernel-ports 192.168.10(20).20. your storage has the ip´s 192.168.10(20).1 - so i assume your storage connection  goes over this ipaddresses.

but the uplinks are missing. your host seems to have more than 2 vmnics because i cant see vmnic 0 &1 - should these 2 nics are the missing uplinks to vswitch0/1?

[bobkalil]

from the nas

root@bam-san01:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sda: 11994.0 GB, 11993993969664 bytes

255 heads, 63 sectors/track, 1458186 cylinders, total 23425769472 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1               1  4294967295  2147483647+  ee  GPT

Disk /dev/mapper/main-root: 9999 MB, 9999220736 bytes

255 heads, 63 sectors/track, 1215 cylinders, total 19529728 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/main-root doesn't contain a valid partition table

Disk /dev/mapper/main-swap: 3997 MB, 3997171712 bytes

255 heads, 63 sectors/track, 485 cylinders, total 7806976 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/main-swap doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/mapper/main-vmhost01'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/mapper/main-vmhost01: 10.7 GB, 10737418240 bytes

255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x000cc976

                     Device Boot      Start         End      Blocks   Id  System

/dev/mapper/main-vmhost01p1               1    20971519    10485759+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/mapper/main-vmhost02'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/mapper/main-vmhost02: 10.7 GB, 10737418240 bytes

255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00075abc

                     Device Boot      Start         End      Blocks   Id  System

/dev/mapper/main-vmhost02p1               1    20971519    10485759+  ee  GPT

Disk /dev/mapper/main-iso: 53.7 GB, 53687091200 bytes

255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/main-iso doesn't contain a valid partition table

Disk /dev/mapper/main-nas2: 2147.5 GB, 2147483648000 bytes

255 heads, 63 sectors/track, 261083 cylinders, total 4194304000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x6513e1dc

                 Device Boot      Start         End      Blocks   Id  System

/dev/mapper/main-nas2p1              63  4194301951  2097150944+  42  SFS

Disk /dev/mapper/main-nas1: 2147.5 GB, 2147483648000 bytes

255 heads, 63 sectors/track, 261083 cylinders, total 4194304000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x6513e1d2

                 Device Boot      Start         End      Blocks   Id  System

/dev/mapper/main-nas1p1              63  4194301951  2097150944+  42  SFS

WARNING: GPT (GUID Partition Table) detected on '/dev/mapper/main-iscsi01'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/mapper/main-iscsi01: 7146.8 GB, 7146825580544 bytes

255 heads, 63 sectors/track, 868885 cylinders, total 13958643712 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

                    Device Boot      Start         End      Blocks   Id  System

/dev/mapper/main-iscsi01p1               1  4294967295  2147483647+  ee  GPT

root@bam-san01:~#

[bobkalil]

yes as I mention before the switch is not configured and I don't know how to configure it for this issue.

[berndweyand]

but it does not matters if your switch ist configured or not in the moment. the virtual switches have no uplink configured so you cant reach your storage (compare it to vswitch0 which has 2 uplinks vmnic2&3)

[bobkalil]

so how can I make it up?

[berndweyand]

open the properties of switch1, go to network adapters and add one - vmnic0 (or 1). the same for vswitch2: vmnic1 (or 0)

then check. if that doesn work change the 2 nics vice versa

[bobkalil]

Many thanks, I can mount the storages fron the NAS.

Thank you soo much!!

[berndweyand]

ok - the physical switch was not the reason

[bobkalil]

another advice if you can I want to format the nas because it has old Debian os and I want to make FreeNAS the storage for sharing and I want to install open LDAP.

What do you suggest as a workflow to set it up?