Depending on the OS and the cluster type, you will need to have FA port settings to support the environment. If you refer to the Fiber Bit Settings of the latest EMC Support Matrix, you will be able to determine to correct settings for your environment.
These settings can usually be set in ControlCenter, although most CE's aren't very happy about it. It's certainly not something that you should try while anything in production is attached to that particular FA port ....

Hope This Helps - regards......

Julianne

With SE 6.4 ..you can now set specific flags using your symmask command ..without affecting other systems on the same FA. Stefano educated me how to do that when i had to set SPC-2 flag for my Exchange 2007 cluster

Take a look at the latest solution enabler guide and look for "Setting the HBA port flags"

heheh ..i am always nice

you can can set specific flag on per hba basis versus on the FA bases. For example we were deploying Exchange 2007 that required that SPC-2 flag set on the FA. Since we had other systems sharing that FA and those systems could not handle SPC-2 flag ..we used Solution Enabler 6.4 new functionality that enables you to set FA port settings at HBA level. For example to enable SCSI3 flag and Common serial number for just one particular HBA:

symmask -sid 031 set hba_flags on C, SC3 -enable -wwn 210000e08b0995b7-dir 16A -p 0

My answer was in reference to the DMX FA port settings, not the HBA port settings.
Although it's reasonable that the HBA port settings are configurable by the symmask command, it doesn't seem likely that the FA port settings would be.

Correct me if I'm wrong (please be nice about it tho ), but my understanding was that the two types of port configuring commands were:
1.) Symmask - updates the symapi database
2.) Symconfigure - updates the bin file

Regards,
Julianne

to answer your question about clusters ..in a two node cluster ..you can have both nodes active as long as different resources are active on different nodes, that way you can utilize both nodes ..and not just have one box sitting there using power and cooling and not doing anything. For example you could have one node running your production database while your other node is running development. In event of cluster failover you need to make sure boxes are sized properly (memory,cpu ..etc) to be able to handle the load of the failed node. We have a 4-node exchange 2007 cluster that consists of 3 active and 1 standby nodes. Some great resources here:

http://www.microsoft.com/windowsserver2003/technologies/clustering/resources.mspx

Hmmmm Dynamox are you still using my own original example ??

I don't want credits !! I want points

Goodmorning

-s-

PS you are right .. We don't have box sn 031 here

i got it from SE config guide ..but i did give you credit for explaining this new feature in my first reply

not really ..i just updated my management box to SE 6.4.1 and started using the new functionality.

What do you emc'ers do with points, eh???
Give the points to me or dynamox, I say!

Okay - back to the question - isn't there a specific FA setting that is a prerequisite to using the 6.4 symmask setting you're talking about that allows an FA 'subseting' for a specific HBA?

I hope that question makes sense - it barely makes sense to me. Maybe I need more coffee ..... I love coffee ...

-julianne