I have found that when you alias a WWn prior to the WWN logging in the name will not be correctly applied when the host does log in. What I do is save my alias commands and re-run them again. I do it from a windows host so if I have a lot of entries I just put the commands into a .bat file and run it that way.
I see the same result however I still have the same problem as the OP. When you view the WWN's form the FA perspective there is no name associated with it; in the list logins command output. There will be a name in the masking view.
The environment I work in now is almost completely boot from SAN so we see this all the time.
Like I said the environment is pretty much 100% boot from SAN so everything storage wise is done prior to the host coming up. We zone and create all the storage then its turned over to the engineering folks to load the O/S and APP's.
We have a work flow and contractors that do provisioning so there isnt a task for them to come back and update the alias data.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
1478
0
Posted January 2nd, 2014 11:00
for example: symaccess -sid 123 rename -wwn 500110a00085c630 -alias oracle01/h0