Comments (1)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 AnthonyEnglish commented Permalink

It's hard to say, but I would look at look at the attributes of the adapter and the disk on both VIO servers. For example, if on VIO2 the disk has a different queue_depth or reserve_policy, then on VIO1 it may appear as a different disk name. I would also check the VIO error report on both VIO servers (as padmin you can run errlog -ls) and see if you're getting any errors there. And of course make sure the disk is correctly assigned from the SAN to the adapters. <div>&nbsp;</div> One other thing - remove the vscsi device no the VIO client and the VIO server which connects to the failing adapter. <div>&nbsp;</div> Perhaps a call to IBM Support would give the answer pretty quickly. Your approach is a good one of removing the failing path and trying to recreate it.