Error Log - Help-me pls !

[Maruo]

ESX 3.5

Server: PowerEdge 2950

Feb 7 09:31:51 ESX01 vmkernel: 0:00:00:03.492 cpu1:1041)WARNING: SCSI: 1249: LegacyMP Plugin could not claim path: vmhba0:264:0. Not supported

Feb 7 09:31:51 ESX01 vmkernel: 0:00:00:03.492 cpu1:1041)WARNING: ScsiPath: 3180: Plugin 'legacyMP' had an error (Not supported) while claiming path 'vmhba0:C0:T264:L0'.Skipping the path.

Feb 7 17:35:08 ESX01 vmkernel: TSC: 66213 cpu0:0)WARNING: Cpu: 1006: cpu supports 38 bit physical address, but system is configured to limit the MTRR mask to 36 bits

Feb 7 17:35:23 ESX01 vmkernel: 0:00:00:03.940 cpu3:1041)WARNING: SCSI: 279: SCSI device type 0xd is not supported. Cannot create target vmhba0:264:0

Feb 7 17:35:23 ESX01 vmkernel: 0:00:00:03.940 cpu3:1041)WARNING: SCSI: 1249: LegacyMP Plugin could not claim path: vmhba0:264:0. Not supported

Feb 7 17:35:23 ESX01 vmkernel: 0:00:00:03.940 cpu3:1041)WARNING: ScsiPath: 3180: Plugin 'legacyMP' had an error (Not supported) while claiming path 'vmhba0:C0:T264:L0'.Skipping the path.

Feb 7 18:39:14 ESX01 vmkernel: TSC: 65023 cpu0:0)WARNING: Cpu: 1006: cpu supports 38 bit physical address, but system is configured to limit the MTRR mask to 36 bits

Feb 7 18:39:29 ESX01 vmkernel: 0:00:00:03.936 cpu3:1041)WARNING: SCSI: 279: SCSI device type 0xd is not supported. Cannot create target vmhba0:264:0

Feb 7 18:39:29 ESX01 vmkernel: 0:00:00:03.936 cpu3:1041)WARNING: SCSI: 1249: LegacyMP Plugin could not claim path: vmhba0:264:0. Not supported

Feb 7 18:39:29 ESX01 vmkernel: 0:00:00:03.936 cpu3:1041)WARNING: ScsiPath: 3180: Plugin 'legacyMP' had an error (Not supported) while claiming path 'vmhba0:C0:T264:L0'.Skipping the path.

[FlorianLenz]

Hello Maruo,

I have the same error messages.

Platform: PowerEdge 2950 - ESX 3.5. QLE2462

FC does not really work. Access available but very slow. Partitioning/ Formatting of a VMFS not possible. I formatted the VMFS using iSCSI. Afterwards I could access the storage by FC at 33.6 modem speed. I opened a call at vmware as well as datacore (Storage). I also asked at Dell - without any response yet.

Do you have any updates or similar performance issues?

[Kent_Chalmers]

I am also receiving this exact same error on 2950s.

Cheers

Kent

[Kent_Chalmers]

I managed to fix this by placing a real ip address on the service console. Seamed to simple but it did fix it for me.

[Rumple]

Define real IP..

Did you not configure your service console with a valid network configuration before or did you change ot using a public ip on the service console.

[Kent_Chalmers]

Sorry, IP as in an IP that existed on our internal network. I used the term 'real' as a term for an ip that was usable. Apoligies for any confusion.

[FlorianLenz]

Due to Dell Support, the Error Message "Plugin 'legacyMP' had an error (Not supported) while claiming path 'vmhba0:C0:T264:L0'.Skipping the path" is "cosmetical" and not an error and belongs to Dells PercRaid Adapter.

My Problems (Slow FC-Performance) are now detected as propably a compatibility issue between ESX 3.5 and Brocade 200E Firmware 5.3.0a. We changed the FC-Switches to old 3200 with old Firmware and everything works fine (with 2GB)

[Bengyke]

I have the same error in the vmkernel log when scanning my LUNs: PE2950 with SAN NetApp.

2 x PE2950 (one year old) with SAN storage no problem

2 x new PE2950 (2 weeks old) problem with SAN Storage

Dell provides no solution till today ...

[FlorianLenz]

Sehr geehrte Kunden,

ich bin derzeit nicht im Büro erreichbar. Ihre Nachrichten kann ich erst wieder ab dem 11. März beantworten. In dringenden Fällen wenden Sie sich bitte an unser Servicedesk (support@she.net / +49 621 5200-210).

Ihre Nachrichten werden NICHT automatisch weitergeleitet.

Mit freundlichen Grüßen

Florian Lenz

[opbz]

On a san attached PE2950 you will get 2 types of disk related errors

Some are to do with the internal raid controller and are as listed on this page.

Others are along the lines of unable to read file table on certain luns.

Both these errors are normal. The first one is cosmetic the second one is caused because EMC CX are Active / PAssive SANs this means you can see a disk through both paths but only 1 path has full access to it

Also the newer HBA drivers included in ESX3.5 need the lattest bios for the HBA so ensure you have it fully updated.