My faith in symantec testing and the compatability lab (what ever they're
calling it these days) is severely shaken. This seems to be a straight
forward, testable senario.
Sorry, just had to vent. Some times stuff happens and we can't test
everything...
Cheers,
Rich
sent from my g1 mobile,
Hello again,
And thanks for replies everyone. Everyone who replied (Bryan, Mark, Rich) had
the same thing in mind: reinstalling ASM even though it's supposed to be
included in the default vvm5.0 installation. Well, that's what I did, and even
got a step forward.
Now I've got the correct array
Hi Jarkko,
Would it be possible to stop and start DMP somehow? I have no idea on
how to do this.
But sometimes, a reboot is the only thing that can fix things, and it
maybe the best, and fastest, option.
Greg.
-Original Message-
From: veritas-vx-boun...@mailman.eng.auburn.edu
Hi,
This issue of use_all_paths not distributing I/O all paths of an ALUA
array had been identified and fixed internally. The fix should be
available in the subsequent RPs on VRTSvxvm 5.0MP3
With regards
Hari
--
Message: 1
Hello,
Recently installed sol10 vvm5.0 mp3 on a Fujitsu-Siemens PP450 w/ 4 x cpu
16G memory, connected to an EVA8000 with 2 x qlogic 2300F HBAs.
There's something odd with the dmp: all SAN disks seem to use only 4 fc paths
in use instead of the 8 paths that are available; only the primary
