Looking for FC-AL ID of va7410 controller

[Simon Galton]

I'm documenting our setup and can not find a reference to the FC-AL ID of the va7410 controller. I assume that it is "7", but can someone validate or correct this?

Thanks!

[Vincent Fleming]

Uh, it's not 7. In fact, it would have up to 4 FC/AL loopids.

Run armdsp -a on the unit.

Look for entries like this: (there will be 2 of them, one for M/C1 and one for M/C2)

Controller At M/C1:
Status:_______________________________Good
Serial Number:________________________00PR00400628
Vendor ID:____________________________HP
Product ID:___________________________A6188A
Product Revision:_____________________HP13
Firmware Revision:____________________38370HP13P0912011411
Manufacturing Product Code:___________IJMTU00008
Controller Type:______________________HP StorageWorks Virtual Array 7100
Battery Charger Firmware Revision:____4.0
Front Port At M/C1.H1:
Status:_____________________________Good
Port Instance:______________________0
Hard Address:_______________________110
Link State:_________________________Link Up
Node WWN:___________________________50060b00000972f0
Port WWN:___________________________50060b00000938d5
Topology:___________________________Private Loop
Data Rate:__________________________1 GBit/sec
Port ID:____________________________110



In the above example, "port id" is what you're looking for (this is from a va7100). There will be a total of 4 ports, and hence 4 port ids.


The ports will be M/C1.H1, M/C1.H2, M/C2.H1 and M/C2.H2.

This is assuming, of course, that you're not in Fabric mode - where there is no loop id...

Good luck, and please post back if you require any further assistance.

Vince

[Eugeny Brychkov · Accepted solution]

Simon,
do not mix SCSI Id 7 with loop-id and al-pa.
First of all, if you're using fibre channel switch you only need to setup VA ports into fabric mode ('armmgr -y' or from vfp - serial interface at the back of each controller). In fabric mode loop-id does not play a role.
But if you use hub or direct connect to the host then you need to setup VA unique loop-id in 1-125 range ('vfpmgr -L' from vfp). If there will be loop-id conflict within ONE loop then controller will be assigned 'soft' loop-id which is not good because on next reboot it may change and thus device files will change and server may crash. If you use one VA then do not worry - bu default all front end FC ports have different loop-ids.
Of course recommended way is to use FC switches, not private loop
Eugeny

[Eugeny Brychkov]

Vincent,
where did you find this VA7100 with ancient HP13 and 4.0 battery firmwares? Looks like a lot of work for HP CE upgrading to HP18 and 4.3 ;o)
Eugeny

[Simon Galton]

OK, I'm braindead. Here I was examining the DS2400 shelves and noting their FC-AL ids and assuming the va74xx devices had a fixed id.

In fabric mode, which, naturally, the controller running in being connected to a switch and several hosts, this is irrelevant.

Noting the firmware comment -- I guess I better not tell anyone that we're still at HP14 on our va7400... :)

Thanks all.

[Eugeny Brychkov]

As soon as you already told it ;o)
Please call your local HP and schedule firmware upgrade. New HP18 firmware is pretty good and since HP14 has a lot of improvements
Eugeny

[Vincent Fleming]

Eugeny,

I just searched the forums for an example - I haven't a VA within reach to run armdsp on.

You always pick up those little details, don't you??? ;-} Picky, picky.

;-} ;-}

-Vince

[Eugeny Brychkov]

Simply I know where to look at. Like Sherlock Holmes - details will tell you all you need...
Eugeny