I have 2 hosts in a DRS HA cluster that have started reporting warnings in the VMKernel logs. I will really appreciate if you can point me in the right direction as to why these errors/warnings are coming on my hosts... Thank you so much.
Host 1
Feb 19 09:07:41 s15c250 vmkernel: 4:10:36:10.906 cpu1:4279)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x410001164f00) to NMP device "sym.019010278831343633" failed on physical path "vmhba0:C0:T0:L44" H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
Feb 19 09:07:41 s15c250 vmkernel: 4:10:36:10.906 cpu1:4279)ScsiDeviceIO: 747: Command 0x2a to device "sym.019010278831343633" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
Feb 19 09:10:32 s15c250 vmkernel: 4:10:39:02.545 cpu3:4281)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x41000107fdc0) to NMP device "sym.019010278831343633" failed on physical path "vmhba0:C0:T0:L44" H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
Feb 19 09:10:32 s15c250 vmkernel: 4:10:39:02.545 cpu3:4281)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "sym.019010278831343633" state in doubt; requested fast path state update...
Feb 19 09:10:32 s15c250 vmkernel: 4:10:39:02.545 cpu3:4281)ScsiDeviceIO: 747: Command 0x2a to device "sym.019010278831343633" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
Feb 19 09:20:47 s15c250 vmkernel: 4:10:49:16.747 cpu5:5045)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x41000104e7c0) to NMP device "sym.019010278831343633" failed on physical path "vmhba0:C0:T0:L44" H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
Feb 19 09:20:47 s15c250 vmkernel: 4:10:49:16.747 cpu5:5045)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "sym.019010278831343633" state in doubt; requested fast path state update...
Feb 19 09:20:47 s15c250 vmkernel: 4:10:49:16.747 cpu5:5045)ScsiDeviceIO: 747: Command 0x2a to device "sym.019010278831343633" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
Feb 19 09:21:59 s15c250 vmkernel: 4:10:50:29.194 cpu5:4297)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x410001267e40) to NMP device "sym.019010278831343633" failed on physical path "vmhba0:C0:T0:L44" H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
Feb 19 09:21:59 s15c250 vmkernel: 4:10:50:29.194 cpu5:4297)ScsiDeviceIO: 747: Command 0x2a to device "sym.019010278831343633" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
Feb 19 09:25:13 s15c250 vmkernel: 4:10:53:42.788 cpu1:4097)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4100010510c0) to NMP device "sym.019010278831343633" failed on physical path "vmhba0:C0:T0:L44" H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
Feb 19 09:25:13 s15c250 vmkernel: 4:10:53:42.788 cpu1:4097)ScsiDeviceIO: 747: Command 0x2a to device "sym.019010278831343633" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
Feb 19 09:27:34 s15c250 vmkernel: 4:10:56:03.935 cpu1:4097)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x410001104480) to NMP device "sym.019010278831343633" failed on physical path "vmhba0:C0:T0:L44" H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x44 0x0.
"vmkernel" 1169L, 244280C
Host 2
Feb 19 08:59:31 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 3506]on volume 'DASD'.
Feb 19 08:59:35 s15c251 vmkernel: 4:10:28:08.742 cpu8:4118)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50718720 v 654, hb offset 3571712
Feb 19 08:59:35 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 3506] is not free on volume 'DASD'
Feb 19 08:59:36 s15c251 vmkernel: 4:10:28:09.783 cpu8:4118)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50722816 v 656, hb offset 3571712
Feb 19 08:59:36 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 3516]on volume 'DASD'.
Feb 19 08:59:40 s15c251 vmkernel: 4:10:28:13.786 cpu8:4118)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50722816 v 656, hb offset 3571712
Feb 19 08:59:40 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 3516] is not free on volume 'DASD'
Feb 19 10:16:27 s15c251 vmkernel: 4:11:45:01.211 cpu6:4118)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50737152 v 667, hb offset 3571712
Feb 19 10:16:27 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4836]on volume 'DASD'.
Feb 19 10:16:31 s15c251 vmkernel: 4:11:45:05.212 cpu6:4118)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50737152 v 667, hb offset 3571712
Feb 19 10:16:31 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4836] is not free on volume 'DASD'
Feb 19 10:16:32 s15c251 vmkernel: 4:11:45:06.223 cpu15:4118)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50741248 v 735, hb offset 3571712
Feb 19 10:16:32 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4828]on volume 'DASD'.
Feb 19 10:16:36 s15c251 vmkernel: 4:11:45:10.224 cpu15:4118)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50741248 v 735, hb offset 3571712
Feb 19 10:16:36 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4828] is not free on volume 'DASD'
Feb 19 10:17:04 s15c251 vmkernel: 4:11:45:38.341 cpu4:4118)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50737152 v 667, hb offset 3571712
Feb 19 10:17:04 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4836]on volume 'DASD'.
Feb 19 10:17:08 s15c251 vmkernel: 4:11:45:42.342 cpu4:4118)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50737152 v 667, hb offset 3571712
Feb 19 10:17:08 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4836] is not free on volume 'DASD'
Feb 19 10:17:09 s15c251 vmkernel: 4:11:45:43.358 cpu12:4119)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50741248 v 735, hb offset 3571712
Feb 19 10:17:09 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4828]on volume 'DASD'.
Feb 19 10:17:13 s15c251 vmkernel: 4:11:45:47.360 cpu12:4119)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50741248 v 735, hb offset 3571712
Feb 19 10:17:13 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4828] is not free on volume 'DASD'
Feb 19 10:17:57 s15c251 vmkernel: 4:11:46:30.984 cpu12:4119)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50737152 v 667, hb offset 3571712
Feb 19 10:17:57 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4836]on volume 'DASD'.
Feb 19 10:18:01 s15c251 vmkernel: 4:11:46:34.986 cpu12:4119)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50737152 v 667, hb offset 3571712
Feb 19 10:18:01 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4836] is not free on volume 'DASD'
Feb 19 10:18:02 s15c251 vmkernel: 4:11:46:35.993 cpu12:4119)FS3: 2762: Requested mode: 1 Checking liveness of lock holders [type 10c00001 offset 50741248 v 735, hb offset 3571712
Feb 19 10:18:02 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4828]on volume 'DASD'.
Feb 19 10:18:06 s15c251 vmkernel: 4:11:46:39.994 cpu12:4119)FS3: 2854: Requested mode: 1 Lock [type 10c00001 offset 50741248 v 735, hb offset 3571712
Feb 19 10:18:06 s15c251 vmkernel: gen 431, mode 1, owner 4b78c065-357f130c-6481-001ec9e98efd mtime 4828] is not free on volume 'DASD'
Host 2 was logging this previously
Jan 28 01:38:47 s15c251 vmkernel: 22:14:25:28.785 cpu7:4204)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 01:38:47 s15c251 vmkernel: 22:14:25:28.834 cpu6:4205)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 01:38:47 s15c251 vmkernel: 22:14:25:28.851 cpu6:4205)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 04:38:35 s15c251 vmkernel: 22:17:25:16.242 cpu11:4203)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 04:38:35 s15c251 vmkernel: 22:17:25:16.244 cpu10:4196)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 04:38:35 s15c251 vmkernel: 22:17:25:16.294 cpu10:4198)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 04:38:35 s15c251 vmkernel: 22:17:25:16.311 cpu11:4198)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 07:38:23 s15c251 vmkernel: 22:20:25:03.721 cpu4:4199)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 07:38:23 s15c251 vmkernel: 22:20:25:03.724 cpu7:4209)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 07:38:23 s15c251 vmkernel: 22:20:25:03.774 cpu15:4208)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 07:38:23 s15c251 vmkernel: 22:20:25:03.791 cpu15:4208)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 10:12:50 s15c251 vmkernel: 22:22:59:29.858 cpu10:5138)<6>megasas_service_aen[8]: aen received
Jan 28 10:12:50 s15c251 vmkernel: 22:22:59:29.858 cpu15:4218)<6>megasas_hotplug_work[8]: event code 0x00a0
Jan 28 10:12:50 s15c251 vmkernel: 22:22:59:29.858 cpu15:4218)<6>megasas_hotplug_work[8]: aen registered
Jan 28 10:38:12 s15c251 vmkernel: 22:23:24:51.581 cpu13:4206)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 10:38:12 s15c251 vmkernel: 22:23:24:51.584 cpu15:4204)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 10:38:12 s15c251 vmkernel: 22:23:24:51.634 cpu10:4196)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 10:38:12 s15c251 vmkernel: 22:23:24:51.653 cpu10:4196)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 13:38:00 s15c251 vmkernel: 23:02:24:39.600 cpu4:4196)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 13:38:00 s15c251 vmkernel: 23:02:24:39.603 cpu7:4200)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 13:38:00 s15c251 vmkernel: 23:02:24:39.659 cpu14:4209)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 13:38:00 s15c251 vmkernel: 23:02:24:39.679 cpu14:4209)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 15:14:00 s15c251 vmkernel: 23:04:00:39.185 cpu13:10106)<6>megasas_service_aen[8]: aen received
Jan 28 15:14:00 s15c251 vmkernel: 23:04:00:39.186 cpu2:4215)<6>megasas_hotplug_work[8]: event code 0x009b
Jan 28 15:14:00 s15c251 vmkernel: 23:04:00:39.186 cpu2:4215)<6>megasas_hotplug_work[8]: aen registered
Jan 28 15:44:20 s15c251 vmkernel: 23:04:30:59.124 cpu4:10038)<6>megasas_service_aen[8]: aen received
Jan 28 15:44:20 s15c251 vmkernel: 23:04:30:59.124 cpu1:4220)<6>megasas_hotplug_work[8]: event code 0x0097
Jan 28 15:44:20 s15c251 vmkernel: 23:04:30:59.124 cpu1:4220)<6>megasas_hotplug_work[8]: aen registered
Jan 28 15:45:25 s15c251 vmkernel: 23:04:32:04.116 cpu4:4285)<6>megasas_service_aen[8]: aen received
Jan 28 15:45:25 s15c251 vmkernel: 23:04:32:04.116 cpu2:4221)<6>megasas_hotplug_work[8]: event code 0x0094
Jan 28 15:45:25 s15c251 vmkernel: 23:04:32:04.116 cpu2:4221)<6>megasas_hotplug_work[8]: aen registered
Jan 28 15:45:25 s15c251 vmkernel: 23:04:32:04.129 cpu4:10075)<6>megasas_service_aen[8]: aen received
Jan 28 15:45:25 s15c251 vmkernel: 23:04:32:04.129 cpu14:4228)<6>megasas_hotplug_work[8]: event code 0x0098
Jan 28 15:45:25 s15c251 vmkernel: 23:04:32:04.129 cpu14:4228)<6>megasas_hotplug_work[8]: aen registered
Jan 28 16:37:48 s15c251 vmkernel: 23:05:24:27.071 cpu7:4209)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 16:37:48 s15c251 vmkernel: 23:05:24:27.073 cpu7:4200)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 16:37:48 s15c251 vmkernel: 23:05:24:27.123 cpu10:4201)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Jan 28 16:37:48 s15c251 vmkernel: 23:05:24:27.140 cpu10:4201)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 17:01:25 s15c251 vmkernel: 23:05:48:03.944 cpu14:5138)<6>megasas_service_aen[8]: aen received
Jan 28 17:01:25 s15c251 vmkernel: 23:05:48:03.944 cpu4:4226)<6>megasas_hotplug_work[8]: event code 0x00a2
Jan 28 17:01:25 s15c251 vmkernel: 23:05:48:03.944 cpu4:4226)<6>megasas_hotplug_work[8]: aen registered
Jan 28 17:01:28 s15c251 vmkernel: 23:05:48:06.385 cpu14:5138)<6>megasas_service_aen[8]: aen received
Jan 28 17:01:28 s15c251 vmkernel: 23:05:48:06.385 cpu10:4222)<6>megasas_hotplug_work[8]: event code 0x00c3
Jan 28 17:01:28 s15c251 vmkernel: 23:05:48:06.385 cpu10:4222)<6>megasas_hotplug_work[8]: aen registered
Jan 28 17:01:28 s15c251 vmkernel: 23:05:48:06.385 cpu14:5138)<6>megasas_service_aen[8]: aen received
Jan 28 17:01:28 s15c251 vmkernel: 23:05:48:06.385 cpu15:4225)<6>megasas_hotplug_work[8]: event code 0x0036
Jan 28 17:01:28 s15c251 vmkernel: 23:05:48:06.385 cpu15:4225)<6>megasas_hotplug_work[8]: aen registered
Jan 28 17:33:10 s15c251 vmkernel: 23:06:19:48.875 cpu3:10092)<6>megasas_service_aen[8]: aen received
an 28 01:38:47 s15c251 vmkernel: 22:14:25:28.785 cpu7:4204)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Jan 28 01:38:47 s15c251 vmkernel: 22:14:25:28.834 cpu6:4205)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Host 3 is standalone and is reporting the following
Feb 18 04:26:07 s15c252 vmkernel: 3:05:57:11.827 cpu8:4207)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 04:26:07 s15c252 vmkernel: 3:05:57:11.830 cpu13:4202)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 04:26:07 s15c252 vmkernel: 3:05:57:11.876 cpu14:4198)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 04:26:07 s15c252 vmkernel: 3:05:57:11.884 cpu13:4206)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 07:25:54 s15c252 vmkernel: 3:08:56:59.137 cpu10:4201)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 07:25:54 s15c252 vmkernel: 3:08:56:59.139 cpu7:4207)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 07:25:54 s15c252 vmkernel: 3:08:56:59.187 cpu14:4198)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 07:25:54 s15c252 vmkernel: 3:08:56:59.194 cpu13:4209)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 10:25:42 s15c252 vmkernel: 3:11:56:46.557 cpu5:4203)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 10:25:42 s15c252 vmkernel: 3:11:56:46.559 cpu10:4195)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 10:25:42 s15c252 vmkernel: 3:11:56:46.605 cpu14:4206)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 10:25:42 s15c252 vmkernel: 3:11:56:46.613 cpu12:4207)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 13:25:30 s15c252 vmkernel: 3:14:56:34.237 cpu7:4208)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 13:25:30 s15c252 vmkernel: 3:14:56:34.239 cpu11:4196)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 13:25:30 s15c252 vmkernel: 3:14:56:34.285 cpu7:4199)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 13:25:30 s15c252 vmkernel: 3:14:56:34.293 cpu3:4195)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 16:25:17 s15c252 vmkernel: 3:17:56:21.557 cpu13:4206)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 16:25:17 s15c252 vmkernel: 3:17:56:21.559 cpu5:4199)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 16:25:17 s15c252 vmkernel: 3:17:56:21.604 cpu13:4202)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 16:25:17 s15c252 vmkernel: 3:17:56:21.612 cpu11:4197)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 19:25:04 s15c252 vmkernel: 3:20:56:08.866 cpu10:4206)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 19:25:04 s15c252 vmkernel: 3:20:56:08.869 cpu4:4209)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 19:25:04 s15c252 vmkernel: 3:20:56:08.916 cpu14:4197)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 19:25:04 s15c252 vmkernel: 3:20:56:08.924 cpu15:4199)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 22:24:51 s15c252 vmkernel: 3:23:55:56.176 cpu9:4195)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 22:24:51 s15c252 vmkernel: 3:23:55:56.179 cpu7:4204)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 18 22:24:52 s15c252 vmkernel: 3:23:55:56.225 cpu5:4198)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 18 22:24:52 s15c252 vmkernel: 3:23:55:56.233 cpu13:4207)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 01:24:39 s15c252 vmkernel: 4:02:55:43.516 cpu13:4203)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 01:24:39 s15c252 vmkernel: 4:02:55:43.518 cpu13:4209)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 01:24:39 s15c252 vmkernel: 4:02:55:43.564 cpu4:4197)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 01:24:39 s15c252 vmkernel: 4:02:55:43.572 cpu3:4196)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 04:24:26 s15c252 vmkernel: 4:05:55:31.016 cpu11:4204)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 04:24:26 s15c252 vmkernel: 4:05:55:31.018 cpu14:4195)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 04:24:26 s15c252 vmkernel: 4:05:55:31.064 cpu6:4203)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 04:24:26 s15c252 vmkernel: 4:05:55:31.072 cpu11:4208)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 07:24:14 s15c252 vmkernel: 4:08:55:18.327 cpu13:4200)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 07:24:14 s15c252 vmkernel: 4:08:55:18.329 cpu15:4210)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 07:24:14 s15c252 vmkernel: 4:08:55:18.376 cpu4:4197)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 07:24:14 s15c252 vmkernel: 4:08:55:18.383 cpu15:4207)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 10:24:01 s15c252 vmkernel: 4:11:55:05.656 cpu4:4208)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 10:24:01 s15c252 vmkernel: 4:11:55:05.658 cpu10:4198)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Feb 19 10:24:01 s15c252 vmkernel: 4:11:55:05.705 cpu4:4210)VMK_PCI: 728: device 018:00.0 capType 16 capIndex 76
Feb 19 10:24:01 s15c252 vmkernel: 4:11:55:05.713 cpu13:4209)VMK_PCI: 728: device 018:00.1 capType 16 capIndex 76
Any help will be much appreciated in making me understand whats really going on. Thanks a lot!