StorageTek 6140 / CAM 6.1 newby, setup Qs

Question

Just got a M4000 with a 6140 connected via dual Fibre HBA. Confused what S/W is installed where. I installed the CAM s/w on the M4000 (Data Host?) but I just re-read a StorageTek Array Admin Gde that says the management s/w (CAM?) must be installed on a Sun workstation - .i.e. not on my M4000 is this true? A 2nd Sun system needs to be used to run the CAM application?
Lastly, if M4000 is running Solaris 10 is there any Data Host s/w (drivers, etc.) that I have to install or is it already included in pre-installed Solaris 10 O/S on my M4000 or do I have to find a Solaris 10 O/S CD that has extra array drivers that I need to install? I did enable Multipathing on Solaris 10 via the stmsboot.
Any guidance is greatly appreciated.
Dean

Answer 1

FYI - I answered my own Qs with a bunch of RTFM and trial-and-error.
I originally put the CAM S/W on the M4000 (is data host). Obtained a static IP # for network connection to 6140 Controller A and used laptop to connect to 6140 via seria cable (with proper serial-to-CAT-5 adaptor) to configure IP for controller. Then I could go to URL CAM S/W Install Gde said to use from my desktop and Register 6140 by supplying IP instead of searching network. Was able to register 6140 but network guys complained of "flapping" between M4000 and 6140 so I uninstallled CAM on M4000 and installed it on spare Ultra 25, re-registerd 6140 but network guys say I'm still "flapping".
As for S/W on M4000 to drive 6140 array - Solaris 10 includeds necessary drivers and no need to download SAN S/W from Sun. I did issue Solaris command to support Multipathing.
As for configuring the 6140 with 6-146GB,15KRPM FC-AL disks: I don't have any Premium Licenses as this M4000 will be the only data host to use the 6140... I have a Oracle 10 D/B to house on 6140 so starting with adding a storage pool that asks for a storage profile - I chose ORACLE_OLTP_HA. Then I created a Volume referencing the added storage pool so when I select all 6 disks I got Raid 1+0 and half the total disk space of the 6 disks. I finally created an initiator - the only unkown was when it wanted Unique Identifier (WWN) the Volume create screens listed a WWN of 32chars (WWN of 1st and 6th disk in my volume) but Create Initiator screen wouldn't take this - just had to give it the WWN of 1st disk of Volume and then used hostname of M4000 as only host associated with this initiator.
After a quick reboot of M4000 format finally saw a big 400GB+ disk!!!! The format tool showed the same 8 slices to configure as with individual disks. I zeroed-out all slices but slice 0 and mapped the entire Volume to this slice.
Now for a follow-up Q:
I got this big disk on the array created but I need more than 7 slices to carve it up. What's the best way to do it? A guy here that has older disk arrays has always used Volume Mgr S/W and created 1 big Concat over the entire array volume and chopped it up via soft partitions. Is this a good approach that will achieve good performance? Is there a way to chop up the disks within CAM so M4000 sees multiple logical disks that I can then use the 7 slices per each logical disk for my mount pts? I want to keep Raid 1+0 if possible.
Dean U.