How does RHEV update multipath.conf

We are primarily a HDS shop and we have a /etc/multipath.conf that we have optimized and push out to our hosts via Satellite.  I recently spun up 2 nodes with RHEL 6.4 and then configured them to be RHEV Hypervisors, which replaced the multipath.conf.

This is the resulting output (which may actually be correct)

360060e801005dee0052fba9e0000002a dm-3 HITACHI,DF600F
size=50G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 3:0:0:1 sdc 8:32 active ready  running
`-+- policy='round-robin 0' prio=0 status=enabled
  `- 5:0:0:1 sde 8:64 active ready  running

excerpt from multipath.conf
devices {
device {
    vendor                  "HITACHI"
    product                 "DF.*"
    getuid_callout          "/sbin/scsi_id --whitelisted --replace-whitespace --device=/dev/%n"
}

***********************************************************

I was expecting to see something like (both active/ready)

ATLAS_0001 dm-3 HITACHI,DF600F
[size=200G][features=0][hwhandler=0][rw]
\_ round-robin 0 [prio=1][active]
 \_ 1:0:0:2 sdc 8:32  [active][ready]
 \_ 2:0:0:2 sdh 8:112 [active][ready]

excerpt from multipath.conf

        device {
                vendor "HITACHI"
                product "DF600F*"
                path_grouping_policy multibus
                path_checker readsector0
                getuid_callout "/opt/XXX/sysadmin/XXX_id -g -u -s /block/%n"
                }