VMware Cloud Community
FMorales
Contributor
Contributor
Jump to solution

Problem when try to convert to a NFS server

Hello, I have a ESX 3.5 that mount a NFS server ( Debian 4 on a PIII/ 512M with a Intel Pro 1000 nic).

I cant make a cold converter with converter CD, because the connection with my NFS server is unstable when

converter start....

I try to cahge the nic to a 100M on the cold converter machine ... thinking that maybe is making a saturation of my server ..

but I have the same problems ... I try also change to a 100M the nic of nfs server ... but I have the same problems ...

The two machines are connected trought a new linksys 10/100/1000 24 port swith.

My NFS server work fine with others applications ....

I was thinking that maybe the problem is that the PIII at 900Mhz is slow with the TCP/IP nfs stack and maybe 100M or 1000M nic are saturation it.

But my server works fine with other applications .... I change the distro from debian 4 to fedora ...... but I have the same problem ...

Vmware converter ... fails because NFS server lost connection and ... after a time ... it reconnect. ....

Any idea?

Thanks a lot

Francisco Morales López de Gamarra Vmware VCP | LPI - CCNA
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Texiwill
Leadership
Leadership
Jump to solution

Hello,

I would suggest going gigE for the NFS server. Also, you will need to look at the /var/log/messages logfile on your NFS Server. Is the NFS Server on its own Datastore with a separate pNIC for it? You need to look at the logs to determine the issue.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

View solution in original post

0 Kudos
2 Replies
Texiwill
Leadership
Leadership
Jump to solution

Hello,

I would suggest going gigE for the NFS server. Also, you will need to look at the /var/log/messages logfile on your NFS Server. Is the NFS Server on its own Datastore with a separate pNIC for it? You need to look at the logs to determine the issue.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
FMorales
Contributor
Contributor
Jump to solution

Hello, I cant get NFS service stable with ESX 3.5.

ESX mount the NFS server fine, but when I try to use it with converter (with a high load) it fais randomly

I changed three times the NFS server machine thinking it would be the problem .... even the linux distribution, I try with debian etch / sarge / fedora,

and I get always the same problem .... ESX lost connection with NFS server .... and it make that the NFS server tcp/ip connection goes very very slow even

down ...

I changed the ethernet card too .... I try with Intel Pro 10/100 , Intel Pro 10/100/1000, 3com ...

I changed the switch where they are connected to a new Gigabit one

Wires are cat6

I note that sometime, on the Virtual Center (Configuration -> Storage) it appear like (Inactive) ... and it is not connected

This is my /etc/exports:

/var/nfs 192.168.18.40(rw,sync,no_root_squash) 192.168.18.21(rw,sync,no_root_squash)

And This is the ESX vmkernel log:

Jul 3 09:24:00 virtual1srv vmkernel: 12:18:14:24.739 cpu3:1036)NFS: 107: Command: (mount) Server: (192.168.18.40) IP: (192.168.18.40) Path: (/var/nfs) Label: (BACKUP) Options: (None)

Jul 3 09:24:30 virtual1srv vmkernel: 12:18:14:55.295 cpu3:1036)WARNING: NFS: 898: RPC error 13 (RPC was aborted due to timeout) trying to get port for Mount Program (100005) Version (3) Protocol (TCP) on Server (192.168.18.40)

Jul 3 09:25:35 virtual1srv vmkernel: 12:18:15:59.658 cpu0:1035)NFS: 107: Command: (mount) Server: (192.168.18.40) IP: (192.168.18.40) Path: (/var/nfs) Label: (BACKUP) Options: (None)

Jul 3 09:26:05 virtual1srv vmkernel: 12:18:16:30.368 cpu1:1035)WARNING: NFS: 898: RPC error 13 (RPC was aborted due to timeout) trying to get port for Mount Program (100005) Version (3) Protocol (TCP) on Server (192.168.18.40)

Jul 3 09:26:06 virtual1srv vmkernel: 12:18:16:30.475 cpu3:1036)NFS: 107: Command: (mount) Server: (192.168.18.15) IP: (192.168.18.15) Path: (/var/nfs) Label: (BACKUP) Options: (None)

Jul 3 09:26:36 virtual1srv vmkernel: 12:18:17:01.403 cpu3:1036)WARNING: NFS: 931: MOUNT RPC failed with RPC status 13 (RPC was aborted due to timeout) trying to mount Server (192.168.18.15) Path (/var/nfs)

Jul 3 09:26:58 virtual1srv vmkernel: 12:18:17:22.636 cpu0:1037)NFS: 107: Command: (mount) Server: (192.168.18.15) IP: (192.168.18.15) Path: (/var/nfs) Label: (BACKUP) Options: (None)

Jul 3 09:27:29 virtual1srv vmkernel: 12:18:17:53.449 cpu0:1037)WARNING: NFS: 931: MOUNT RPC failed with RPC status 13 (RPC was aborted due to timeout) trying to mount Server (192.168.18.15) Path (/var/nfs)

Jul 3 09:28:10 virtual1srv vmkernel: 12:18:18:35.041 cpu1:1037)NFS: 107: Command: (mount) Server: (192.168.18.15) IP: (192.168.18.15) Path: (/var/nfs) Label: (BACKUP) Options: (None)

Jul 3 09:45:31 virtual1srv vmkernel: 12:18:35:56.391 cpu0:1028)WARNING: NFS: 257: Mount: (BACKUP) Server (192.168.18.15) 192.168.18.15 Volume: (/var/nfs) not responding

Jul 3 09:45:31 virtual1srv vmkernel: 12:18:35:56.402 cpu2:1036)WARNING: NFS: 1735: Failed to get attributes (No connection)

Jul 3 09:45:31 virtual1srv vmkernel: 12:18:35:56.402 cpu2:1036)FSS: 390: Failed with status No connection for b00f 16 4 1 1000800 f4c01c 0 0 0 0 0 0 0 0

Jul 3 09:45:31 virtual1srv vmkernel: 12:18:35:56.402 cpu2:1036)WARNING: NFS: 1735: Failed to get attributes (No connection)

Jul 3 09:45:31 virtual1srv vmkernel: 12:18:35:56.402 cpu2:1036)FSS: 390: Failed with status No connection for b00f 16 4 1 1000800 f4c01c 0 0 0 0 0 0 0 0

Jul 3 09:45:35 virtual1srv vmkernel: 12:18:35:59.627 cpu1:1168)WARNING: NFS: 281: Mount: (BACKUP) Server (192.168.18.15) 192.168.18.15 Volume: (/var/nfs) OK

Jul 3 10:00:19 virtual1srv vmkernel: 12:18:50:44.186 cpu3:1167)VSCSI: 2803: Reset request on handle 8215 (0 outstanding commands)

Jul 3 10:00:19 virtual1srv vmkernel: 12:18:50:44.187 cpu1:1056)VSCSI: 3019: Resetting handle 8215 0/0

Jul 3 10:00:19 virtual1srv vmkernel: 12:18:50:44.187 cpu1:1056)VSCSI: 2871: Completing reset on handle 8215 (0 outstanding commands)

Jul 3 10:00:40 virtual1srv vmkernel: 12:18:51:05.287 cpu3:1168)VSCSI: 2803: Reset request on handle 8215 (0 outstanding commands)

Jul 3 10:00:40 virtual1srv vmkernel: 12:18:51:05.287 cpu1:1056)VSCSI: 3019: Resetting handle 8215 0/0

Jul 3 10:00:40 virtual1srv vmkernel: 12:18:51:05.287 cpu1:1056)VSCSI: 2871: Completing reset on handle 8215 (0 outstanding commands)

Others Ccommands:

esxcfg-vmknic -l

root@virtual1srv root# esxcfg-vmknic -l

Interface Port Group IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled

vmk0 VMkernel 10.0.0.5 255.255.255.0 10.0.0.255 00:50:56:74:ed:49 1500 40960 true

vmk1 VMkernel 2 10.0.1.5 255.255.255.0 10.0.1.255 00:50:56:7a:09:4d 1500 40960 true

vmk4 VMkernel 3 192.168.18.40 255.255.0.0 192.168.255.255 00:50:56:73:8f:be 1500 40960 true <<<<<<----


to the NFS server

vmk3 VMotion 172.16.0.1 255.255.255.0 172.16.0.255 00:50:56:74:52:58 1500 40960 true

esxcfg-vswitch -l

root@virtual1srv root# esxcfg-vswitch -l

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 64 4 64 1500 vmnic0

PortGroup Name VLAN ID Used Ports Uplinks

Service Console 0 1 vmnic0

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch1 64 5 64 1500 vmnic1

PortGroup Name VLAN ID Used Ports Uplinks

Service Console 2 0 1 vmnic1

VMkernel 0 1 vmnic1

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch2 64 5 64 1500 vmnic2

PortGroup Name VLAN ID Used Ports Uplinks

Service Console 3 0 1 vmnic2

VMkernel 2 0 1 vmnic2

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch3 64 4 64 1500 vmnic3

PortGroup Name VLAN ID Used Ports Uplinks

VMotion 0 1 vmnic3

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch4 64 6 64 1500 vmnic4

PortGroup Name VLAN ID Used Ports Uplinks

VM Network 0 3 vmnic4

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch5 64 4 64 1500 vmnic5

PortGroup Name VLAN ID Used Ports Uplinks

VMkernel 3 0 1 vmnic5

esxcfg-route

root@virtual1srv root# esxcfg-route

VMkernel default gateway is 0.0.0.0

rpcinfo -p 192.168.18.18

root@virtual1srv root# rpcinfo -p 192.168.18.15

program vers proto port

100000 2 tcp 111 portmapper

100000 2 udp 111 portmapper

100024 1 udp 32772 status

100024 1 tcp 34165 status

100003 2 udp 2049 nfs

100003 3 udp 2049 nfs

100003 4 udp 2049 nfs

100003 2 tcp 2049 nfs

100003 3 tcp 2049 nfs

100003 4 tcp 2049 nfs

100021 1 udp 32774 nlockmgr

100021 3 udp 32774 nlockmgr

100021 4 udp 32774 nlockmgr

100021 1 tcp 44782 nlockmgr

100021 3 tcp 44782 nlockmgr

100021 4 tcp 44782 nlockmgr

100005 1 udp 984 mountd

100005 1 tcp 987 mountd

100005 2 udp 984 mountd

100005 2 tcp 987 mountd

100005 3 udp 984 mountd

100005 3 tcp 987 mountd

vmkping -D

root@virtual1srv root# vmkping -D

PING 10.0.0.5 (10.0.0.5): 56 data bytes

64 bytes from 10.0.0.5: icmp_seq=0 ttl=64 time=0.062 ms

64 bytes from 10.0.0.5: icmp_seq=1 ttl=64 time=0.041 ms

Any Help will be greatly appreciated

Francisco Morales López de Gamarra Vmware VCP | LPI - CCNA
0 Kudos