If it's of any benefit, MPIO, iSCSI and virtual volumes of many types are given abstract serial numbers because they don't have physical ones. I think that's the key to the problem. I believe I would have exactly that problem if the agent didn't crash first :-)
in SysInfo.log I get;
<Manufacturer: (Standard disk drives)>
<Caption: HP MSA2312sa Multi-Path Disk Device>
<Description: Disk drive>
<Name: //./PHYSICALDRIVE18>
<MediaType: Fixed hard disk media>
<Size: 15257>
<S/N:
....and then the agent crashes...
Looking at the same disk using wmic gives me the serial number of "00c0ff10eef70000a43e9e4d01000000" which decodes to;
char(0),char(192),char(255),char(16),char(238),char(247),char(0),char(0),char(19),char(230),char(139),S,char(1),char(0),char(0),char(0)
I doubt it would look very meaningful in XML but ,at least on the surface, it seems that the hex decode has harsher side-effects for some of my servers :-/
Hi again,
If it's of any benefit, MPIO, iSCSI and virtual volumes of many types are given abstract serial numbers because they don't have physical ones. I think that's the key to the problem. I believe I would have exactly that problem if the agent didn't crash first :-)
in SysInfo.log I get;
<Manufacturer: (Standard disk drives)> VE18>
<Caption: HP MSA2312sa Multi-Path Disk Device>
<Description: Disk drive>
<Name: //./PHYSICALDRI
<MediaType: Fixed hard disk media>
<Size: 15257>
<S/N:
....and then the agent crashes...
Looking at the same disk using wmic gives me the serial number of "00c0ff10eef700 00a43e9e4d01000 000" which decodes to; ,char(192) ,char(255) ,char(16) ,char(238) ,char(247) ,char(0) ,char(0) ,char(19) ,char(230) ,char(139) ,S,char( 1),char( 0),char( 0),char( 0)
char(0)
I doubt it would look very meaningful in XML but ,at least on the surface, it seems that the hex decode has harsher side-effects for some of my servers :-/
Regards,
Keith