Traffic only going through controller A on 6140

Question

We have two seperate StorageTek 6140 arrays both with dual FC controllers and acting in a similar way, so I'm not sure if this is normal or whether its our site config.
Controller B on each array doesnt seem to be getting utilised at all when looking at the performance monitoring. It says the controller is up and our disk volumes are distributed accross both controllers as the preffered controllers. We have multipathing on Solaris 10 using traffic manager (assuming configured and working correctly).
Is this normal to only see traffic on controller A and not on controller B? I believe traffic manager is configured for round-robin load balancing but as far as I can tell this isn't what i'm seeing taking place. Where would I look to change it so the traffic load is balanced across controllers?
Forgive me, I'm new to these devices so I'm still learning how they are configured. Thanks!

Answer 1

Hi Nik
Thanks for replying. Here is the output of a disk:
root@myhost# luxadm display /dev/rdsk/c5t600A0B800026AD9000000D3F4CA11187d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c5t600A0B800026AD9000000D3F4CA11187d0s2
Vendor: SUN
Product ID: CSM200_R
Revision: 0660
Serial Num: +(removed for privacy)+
Unformatted capacity: 102400.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x3
Maximum prefetch: 0x3
Device Type: Disk device
Path(s):
/dev/rdsk/c5t600A0B800026AD9000000D3F4CA11187d0s2
/devices/scsi_vhci/ssd@g600a0b800026ad9000000d3f4ca11187:c,raw
Controller /devices/pci@1e,600000/SUNW,qlc@3/fp@0,0
Device Address 200600a0b8290184,bb
Host controller port WWN 210000e08b921406
Class secondary
State STANDBY
Controller /devices/pci@1e,600000/SUNW,qlc@2/fp@0,0
Device Address 200700a0b8290184,bb
Host controller port WWN 210000e08b924106
Class primary
State ONLINE
After learning some more about how the 6140 works (I believe it is called an asymmetric array, at any one time a single volume will be owned by one controller, and all I/O to that volume will be via the path to that controller and not via round-robin), I believe it to be a software/firmware bug.
We have no problems communicating to volumes on preferred controller B and there are no alarms, so i can only conclude trafic must be going through that controller. But a volume on controller B will have no performance stats showing in CAM unless it is moved to controller A (stats subsequently go away again when moved back to controller B). Its not affecting the operation of the array, we just can't get volume performance stats on anything using controller B :(
CAM is 6.6 and IOM is 98D0 (latest is 98D3).