Adding Virtual Volumes from Invista to Linux or Windows host, problems

Odd one here, We have 2 boxes one Red Hat, one Windows. On the Red Hat box, we have the box completely in Invista, I went to add a new virtual volume to the host, scanned and the scan died and now is a zombie process. We have had this before where a reboot will fix the issue, but I would think I would be able to add the drive without issues. See below:

qla2400 0000:22:00.0: LOOP DOWN detected (4 3 0).
qla2400 0000:22:00.0: LIP reset occured (f8f7).
qla2400 0000:22:00.0: LOOP UP detected (4 Gbps).
qla2400 0000:23:00.0: LOOP DOWN detected (4 3 0).
qla2400 0000:23:00.0: LIP reset occured (f8f7).
qla2400 0000:23:00.0: LOOP UP detected (4 Gbps).
qla2400 0000:22:00.0: LOOP DOWN detected (4 3 0).
qla2400 0000:22:00.0: LIP reset occured (f8f7).
qla2400 0000:22:00.0: LOOP UP detected (4 Gbps).
Vendor: EMC Model: Invista Rev: 2202
Type: Direct-Access ANSI SCSI revision: 04
qla2400 0000:22:00.0: scsi(1:0:0:10): Enabled tagged queuing, queue depth 32.
SCSI device sdw: 270336000 512-byte hdwr sectors (138412 MB)
SCSI device sdw: drive cache: write through
SCSI device sdw: 270336000 512-byte hdwr sectors (138412 MB)
SCSI device sdw: drive cache: write through
sdw:

Then on a Windows box, I have added a LUN, scanned for it but not mounted it as a drive. The box was rebooted and it hangs at the windows 2003 splash screen. If I removed the cirtual volume that I was going to add and reboot, the server comes up normal.

Has anyone seen this before?