vscsi0 or vscsi1

[hfaix]

I know you can set priorities on which virtual client scsi adapter to use, however changing priorities is done at the hdisk level and requires a reboot.

Is vscsi0 always the default, even though both have a priority of 1 by default?

Thanks again,

 

[p5wizard]

What happens if you discover the disks from vscsi1 first?

Q: What is your goal?


HTH,

p5wizard

 

[jprabaker]

You can use the chpath command to set the priority, 1 being the highest and the default setting for both paths. Do 'chpath -l hdisk0 -p vscsi0 -a priority=2'. This will set vscsi0 to be the lowest priority path and the server will use vscsi1. This requires a reboot!

'lspath -AHE -l hdisk0 -p vscsi0' will show you what its set to.

 

[hfaix]

My goals is to get all the disks in one client with a primary path of vscsi0 and a backup path of vscsi1. This would make it cleaner from a documentation stand point. I'm currently starting with two client lpars so each should get their primary scsi from one vio. I'm trying to avoid one over used path and one under used path.

I can control vscsi0 and vscsi1 (in terms of which vio it comes from) pretty easily by being caution when defining and building the client lpar.

thanks

 

[p5wizard]

I have all virtual SCSI traffic active over 1st VIOS and failover to 2nd VIOS - by taking care how/when the disks are discovered.
All virtual LAN traffic is active over 2nd VIOS and failover to 1st VIOS (with SEA-failover)

Apparently it is better that way because of interrupt handling. Interrupt activity is different for vSCSI versus vLAN - I read something to that effect in a redbook / redpiece / redpaper.


HTH,

p5wizard