Hello  I cannot see anything wrong with the order that you are creating the views in.  The only thing I can think of (I acknowledge this is behaviour from Windows) is that when you change the protocol by adding the flags a host reboot (or at least HBA reset) may be necessary.  Seeing as the ESX kernel is essentially Linux you may need to do as Dynamox does and add the D bit to your overrides.  Sam Claret Technical Support Engineer III  Worldwide Technical Support – OSAPI Windows Office Hours: Rotating shift, 7AM – 4PM GMT Office #: +353 21 494 5981 Email: Sam.Claret[NAME].com Please let us know what you think of the level of service provided by sending an email to my manager, Clare Murphy (Claire.Murphy[NAME].com ). referencing the Service Request number [URL]
Dear friends,  has anyone ever encountered this before?  I'm on a VMAX with a new ESX cluster and after seting up everything on the storage side the ESX guys complain that they don't see the LUNs we provided.  When I ran a "symaccess -sid xxx show clustername -type init -detail" I can see that the override flags are set as they shoiuld be, but the strange thing is that when I set "symaccess -sid xxx -name clustername -type init set ig_flags on SC3,SPC2,OS2007 -enable" again just seconds after the command ran the ESX guys say they noiw can see the LUNs. From my point of view nothing changed, so I was wondering what is happening here. It happened before and each time running the script again helps.  I'm thinking whether or not this is due to the order we run the commands. Can the wwpns be put in the init group before I run the port flag command or should this be done the other way around or does this have nothing to do with the order I run the commands?  The order in which I run the commands for the is:  Can anyone tell me what's going on and why the ESX hosts didn't see the LUNs in the first place and after running the port flag command once again they did see the LUNs?
port flag settings sometimes don't seem to work on VMAX with VMware