Unsolved
This post is more than 5 years old
42 Posts
0
1424
April 17th, 2012 04:00
Enabling V flag on VMAX port level
I have a HP-UX 11.31 host with devs already assigned from my VMAX. We've assigned a couple more devs, but the host is unable to recognize them. I've been reading about this and find out that the V flag is not set in the ports used by this host (a two node cluster actually). I could activate this at the IG, but cannot do it because is a cascaded initiator, I guess that I would have to delete the IG and recreate it with this flag before adding it to the parent IG for the cluster.
The thing is that we might have more systems with the same situation, so I preffer to activate the V flag on the port level. We have several more HP-UX (11.26) in this ports, and Linux hosts also. Question: Is there any risk on activating the V flag on the ports? any disruption or consideration to be taken before doing it? Any recommendation?
Thanks.
0 events found
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
April 17th, 2012 05:00
if you enable the V bit on the FA, you will cause issues for other open systems that do not use that flag (Linux, Windows, AIX ..etc), unless you disable that override that flag at the initiator level. I would figure out how to enable it at initiator level. I can always set the "D" flag on my cascaded initiator group for Linux. What happens when you try to set ig_flag on the cascaded group ?
jvtv
42 Posts
0
April 17th, 2012 06:00
We have ports 7F1_10F0 used for HP-UX and Linux production hosts (where I need the V flag enabled right now. We have another couple of ports, 7E0_9E1, used for development environments (also HP-UX and Linux) in which the V flag is enabled.
When I try to enable the flag at IG level I get this:
root:/tmp>symaccess -sid 1153 -name ESDC1SRP00016_pro_ig -type initiator set ig_flags on V -enable
Cannot set VSA for an initiator group that is cascaded (parent or child)