Die Foren-SW läuft ohne erkennbare Probleme. Sollte doch etwas nicht funktionieren, bitte gerne hier jederzeit melden und wir kümmern uns zeitnah darum. Danke!

Verbindungsabbrüche im 30 Minuten Takt

Hilfe bei Problemen mit Installation & Benutzung des VMware ESX Server 4/VMware vSphere 4.0.

Moderatoren: Dayworker, irix

Antworten
Member
Beiträge: 4
Registriert: 21.07.2010, 11:37

Verbindungsabbrüche im 30 Minuten Takt

Beitragvon night-liner » 21.07.2010, 12:00

Hallo @ all,

zuerst einmal: Ich habe noch einiges an Lernbedarf, was VMware angeht.
Versuche mich aber ständig weiterzubilden.

Nun stehe ich vor einem großen Rätsel:

Wir haben hier eine ESX-Farm mit 3 Physikalischen Maschinen (ESX01 - ESX03) und einigen virtuellen Servern. (Fast alles W2K3)
Seit gestern (20.07.2010) Nachmittag, kommt es ca. alle 30 Minuten zu kurzfristigen ausfällen der Netzwerkverbindung.
Alle virtuellen Server einer Maschine (z.B. ESX03) sind plötzlich nicht mehr zu erreichen,
die vServer auf den anderen Kisten (ESX01, ESX02) schon.
Ein paar Minuten später trifft es dann alle vServer auf ESX02, wobei alle vServer auf ESX01 und ESX03 erreichbar sind.
Das ganze dauert dann so ca. 1 Minute und dann ist alles wieder wie vorher.
Geändert wurde definitv nichts. Die Ereignis Logs der virtuellen Server sind clean.
Storage, SAN-Contrroller und SAN-Switch sind OK. Auch hier keine Meldungen im Log.

irgendwas legt uns quasi das ganze Netz lam.

Das VM-Log habe ich angehangen.

Vielen Dank für Euere Hilfe

Achja: Systeminfos: ESX4.0.0 / VSphere4
Nach oben
Experte
Beiträge: 1337
Registriert: 25.04.2009, 11:17
Wohnort: Thüringen

Beitragvon Supi » 21.07.2010, 12:11

Was ist mit dem LAN-Switch?
Was sagen die Logs der ESX Server? Die virtuellen Server werden ggf durch den Host abgefangen und melden möglicherweise nix.
Nach oben
Member
Beiträge: 4
Registriert: 21.07.2010, 11:37

Beitragvon night-liner » 21.07.2010, 13:44

Dem LAN-Switch geht es gut. Auch dessen Logfiles sind sauber.
Der Rest des Netzwerkes bleibt von dem Problem verschont.

Die logfiles eines ESX-Servers habe ich angefügt.
(nicht wundern die heißen bei uns ESX04 bis ESX06 - keiner weiss warum)
Werde daraus nicht wirklich schlau, meine aber fehler zu sehen.

Vielen Dank
Nach oben
Member
Beiträge: 4
Registriert: 21.07.2010, 11:37

Beitragvon night-liner » 21.07.2010, 13:51

irgendwie wollen die Anhänge nicht...

deshalb hier auszüge aus den Logfiles:

vmkernel

Code: Alles auswählen

Jul 21 13:20:00 esx05 vmkernel: 158:00:07:13.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.041 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.041 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.035 cpu5:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.035 cpu5:4196)WARNING: NMP: nmp_DeviceStartLoop: NMP Device "naa.600c0ff000d89e432949404c01000000" is blocked. Not starting I/O from device.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.035 cpu5:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 7 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.036 cpu5:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 2 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.036 cpu4:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 6 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.036 cpu6:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 32 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.037 cpu6:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 43 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.038 cpu6:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 43 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.039 cpu6:4196)ScsiDeviceIO: 747: Command 0x25 to device "naa.600c0ff000d89e432949404c01000000" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x2 0x4 0x3.
Jul 21 13:20:03 esx05 last message repeated 46 times
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu3:4114)WARNING: ScsiDeviceIO: 2355: READ CAPACITY on device "naa.600c0ff000d89e432949404c01000000" from Plugin "NMP" failed. Timeout
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu3:4114)FSS: 662: Failed to get object f530 28 1 4c404ceb a643f314 2400ab51 3a1f3ce8 0 0 0 0 0 0 0 :Timeout
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu3:4114)WARNING: Fil3: 1918: Failed to reserve volume f530 28 1 4c404ceb a643f314 2400ab51 3a1f3ce8 0 0 0 0 0 0 0
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu3:4114)FSS: 662: Failed to get object f530 28 2 4c404ceb a643f314 2400ab51 3a1f3ce8 4 1 0 0 0 0 0 :Timeout
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu0:4096)VMNIX: VMKFS: 3734: timed out
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.042 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.042 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.042 cpu7:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world restore device "naa.600c0ff000d89e432949404c01000000" - no more commands to retry
Jul 21 13:22:49 esx05 vmkernel: 158:00:10:02.406 cpu3:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:22:49 esx05 vmkernel: 158:00:10:02.406 cpu3:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.


vmkwarning

Code: Alles auswählen

Jul 21 13:19:44 esx05 vmkernel: 158:00:06:57.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:44 esx05 vmkernel: 158:00:06:57.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:44 esx05 vmkernel: 158:00:06:57.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:45 esx05 vmkernel: 158:00:06:58.041 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:45 esx05 vmkernel: 158:00:06:58.041 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:45 esx05 vmkernel: 158:00:06:58.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:45 esx05 vmkernel: 158:00:06:58.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:45 esx05 vmkernel: 158:00:06:58.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:46 esx05 vmkernel: 158:00:06:59.041 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:46 esx05 vmkernel: 158:00:06:59.042 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:46 esx05 vmkernel: 158:00:06:59.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:46 esx05 vmkernel: 158:00:06:59.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:46 esx05 vmkernel: 158:00:06:59.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:47 esx05 vmkernel: 158:00:07:00.041 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:47 esx05 vmkernel: 158:00:07:00.042 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:47 esx05 vmkernel: 158:00:07:00.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:47 esx05 vmkernel: 158:00:07:00.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:47 esx05 vmkernel: 158:00:07:00.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:48 esx05 vmkernel: 158:00:07:01.041 cpu5:36602)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:48 esx05 vmkernel: 158:00:07:01.041 cpu5:36602)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:48 esx05 vmkernel: 158:00:07:01.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:48 esx05 vmkernel: 158:00:07:01.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:48 esx05 vmkernel: 158:00:07:01.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:49 esx05 vmkernel: 158:00:07:02.041 cpu5:36587)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:49 esx05 vmkernel: 158:00:07:02.041 cpu5:36587)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:49 esx05 vmkernel: 158:00:07:02.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:49 esx05 vmkernel: 158:00:07:02.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:49 esx05 vmkernel: 158:00:07:02.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:50 esx05 vmkernel: 158:00:07:03.041 cpu6:36603)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:50 esx05 vmkernel: 158:00:07:03.041 cpu6:36603)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:50 esx05 vmkernel: 158:00:07:03.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:50 esx05 vmkernel: 158:00:07:03.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:50 esx05 vmkernel: 158:00:07:03.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:51 esx05 vmkernel: 158:00:07:04.040 cpu1:36598)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:51 esx05 vmkernel: 158:00:07:04.041 cpu1:36598)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:51 esx05 vmkernel: 158:00:07:04.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:51 esx05 vmkernel: 158:00:07:04.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:51 esx05 vmkernel: 158:00:07:04.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:52 esx05 vmkernel: 158:00:07:05.041 cpu5:36600)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:52 esx05 vmkernel: 158:00:07:05.041 cpu5:36600)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:52 esx05 vmkernel: 158:00:07:05.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:52 esx05 vmkernel: 158:00:07:05.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:52 esx05 vmkernel: 158:00:07:05.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:53 esx05 vmkernel: 158:00:07:06.041 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:53 esx05 vmkernel: 158:00:07:06.041 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:53 esx05 vmkernel: 158:00:07:06.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:53 esx05 vmkernel: 158:00:07:06.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:53 esx05 vmkernel: 158:00:07:06.041 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:54 esx05 vmkernel: 158:00:07:07.042 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:54 esx05 vmkernel: 158:00:07:07.042 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:54 esx05 vmkernel: 158:00:07:07.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:54 esx05 vmkernel: 158:00:07:07.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:54 esx05 vmkernel: 158:00:07:07.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:55 esx05 vmkernel: 158:00:07:08.041 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:55 esx05 vmkernel: 158:00:07:08.042 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:55 esx05 vmkernel: 158:00:07:08.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:55 esx05 vmkernel: 158:00:07:08.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:55 esx05 vmkernel: 158:00:07:08.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:56 esx05 vmkernel: 158:00:07:09.041 cpu5:36602)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:56 esx05 vmkernel: 158:00:07:09.042 cpu5:36602)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:56 esx05 vmkernel: 158:00:07:09.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:56 esx05 vmkernel: 158:00:07:09.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:56 esx05 vmkernel: 158:00:07:09.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:57 esx05 vmkernel: 158:00:07:10.041 cpu5:36587)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:57 esx05 vmkernel: 158:00:07:10.042 cpu5:36587)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:57 esx05 vmkernel: 158:00:07:10.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:57 esx05 vmkernel: 158:00:07:10.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:57 esx05 vmkernel: 158:00:07:10.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:58 esx05 vmkernel: 158:00:07:11.042 cpu6:36603)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:58 esx05 vmkernel: 158:00:07:11.042 cpu6:36603)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:58 esx05 vmkernel: 158:00:07:11.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:58 esx05 vmkernel: 158:00:07:11.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:58 esx05 vmkernel: 158:00:07:11.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:19:59 esx05 vmkernel: 158:00:07:12.041 cpu1:36598)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:59 esx05 vmkernel: 158:00:07:12.042 cpu1:36598)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:19:59 esx05 vmkernel: 158:00:07:12.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:19:59 esx05 vmkernel: 158:00:07:12.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:19:59 esx05 vmkernel: 158:00:07:12.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:00 esx05 vmkernel: 158:00:07:13.041 cpu5:36600)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:00 esx05 vmkernel: 158:00:07:13.041 cpu5:36600)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:00 esx05 vmkernel: 158:00:07:13.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:20:00 esx05 vmkernel: 158:00:07:13.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:20:00 esx05 vmkernel: 158:00:07:13.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.041 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu5:4172)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:20:01 esx05 vmkernel: 158:00:07:14.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.041 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu1:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - issuing command 0x4100062af000
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world failover device "naa.600c0ff000d89e432949404c01000000" - failed to issue command due to Not found (APD), try again...
Jul 21 13:20:02 esx05 vmkernel: 158:00:07:15.042 cpu4:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Logical device "naa.600c0ff000d89e432949404c01000000": awaiting fast path state update...
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.035 cpu5:4196)WARNING: NMP: nmp_DeviceStartLoop: NMP Device "naa.600c0ff000d89e432949404c01000000" is blocked. Not starting I/O from device.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu3:4114)WARNING: ScsiDeviceIO: 2355: READ CAPACITY on device "naa.600c0ff000d89e432949404c01000000" from Plugin "NMP" failed. Timeout
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.040 cpu3:4114)WARNING: Fil3: 1918: Failed to reserve volume f530 28 1 4c404ceb a643f314 2400ab51 3a1f3ce8 0 0 0 0 0 0 0
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.042 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.042 cpu1:36599)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:20:03 esx05 vmkernel: 158:00:07:16.042 cpu7:4207)WARNING: NMP: nmp_DeviceAttemptFailover: Retry world restore device "naa.600c0ff000d89e432949404c01000000" - no more commands to retry
Jul 21 13:22:49 esx05 vmkernel: 158:00:10:02.406 cpu3:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:22:49 esx05 vmkernel: 158:00:10:02.406 cpu3:36601)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:27:49 esx05 vmkernel: 158:00:15:02.406 cpu7:36587)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T3:L4" determined to be in unexpected NOT READY state when probed.
Jul 21 13:27:49 esx05 vmkernel: 158:00:15:02.406 cpu7:36587)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath: Path "vmhba1:C0:T2:L4" determined to be in unexpected NOT READY state when probed.


cron

Code: Alles auswählen

Jul 21 10:15:01 esx05 crond[15125]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:20:01 esx05 crond[16021]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:25:01 esx05 crond[17046]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:30:01 esx05 crond[18006]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:35:01 esx05 crond[19047]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:40:01 esx05 crond[19954]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:45:01 esx05 crond[21040]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:50:01 esx05 crond[21936]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 10:55:01 esx05 crond[22961]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:00:01 esx05 crond[23920]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:01:01 esx05 crond[24170]: (root) CMD (run-parts /etc/cron.hourly)
Jul 21 11:05:01 esx05 crond[28578]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:10:01 esx05 crond[29478]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:15:01 esx05 crond[30555]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:20:01 esx05 crond[31456]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:25:01 esx05 crond[32483]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:30:01 esx05 crond[927]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:35:01 esx05 crond[2030]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:40:01 esx05 crond[2936]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:45:01 esx05 crond[3984]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:50:01 esx05 crond[4943]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 11:55:01 esx05 crond[5966]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:00:01 esx05 crond[6894]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:01:01 esx05 crond[7207]: (root) CMD (run-parts /etc/cron.hourly)
Jul 21 12:05:01 esx05 crond[8951]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:10:01 esx05 crond[9848]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:15:01 esx05 crond[10873]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:20:01 esx05 crond[11832]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:25:01 esx05 crond[12854]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:30:01 esx05 crond[13756]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:35:01 esx05 crond[14860]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:40:01 esx05 crond[17948]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:45:01 esx05 crond[18973]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:50:02 esx05 crond[19945]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 12:55:01 esx05 crond[20974]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 13:00:01 esx05 crond[21905]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 13:01:01 esx05 crond[22218]: (root) CMD (run-parts /etc/cron.hourly)
Jul 21 13:05:01 esx05 crond[24099]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 13:10:01 esx05 crond[24995]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 13:15:01 esx05 crond[26014]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 13:20:01 esx05 crond[26914]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Jul 21 13:25:01 esx05 crond[27950]: (root) CMD (/usr/lib/vmware/bin/memwatchdog.py > /dev/null 2>&1)
Nach oben
Experte
Beiträge: 1337
Registriert: 25.04.2009, 11:17
Wohnort: Thüringen

Beitragvon Supi » 21.07.2010, 14:11

http://forums.virtualizationtimes.com/n ... ated_links

hier gibts ähnliche Probleme und Lösungsansätze. (Remove Death Paths)
Nach oben
Member
Beiträge: 4
Registriert: 21.07.2010, 11:37

Beitragvon night-liner » 21.07.2010, 15:36

Danke für den Link.

Mittlerweile ist das Problem auch gelöst.

Der Fehler lag tatsächlich an einem toten Pfad.
Ich hatte auf unserm SAN ein ungenutztes Volume gelöscht und daraus zwei neue erstellt. Allerdings war diese Volume noch in VM eingebunden.
Das ganze ist seltsamerweise schon eine Woche her. In dieser Zeit ist nichts passiert.
Erst gestern begannen die Probleme.
Durch einen rescan hat er dann den Pfad aus der Config geschmissen und alles war wieder gut.
Nach oben
Antworten

Zurück zu „vSphere 4 / ESX 4“

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 11 Gäste