If you have another host connected to the box you are zoning and if you know the director/port of the box and the wwn of the host you can also use:
symmask -sid 123 -dir 4A -p 0 list logins
and search for a line in the output that shows your wwn .. please note that you must find that the line ends with a pair of "Yes" .. This means that the wwn is logged on the FA port and that the WWN is seen in the fabric.
That is because SYMCLI is a Symmetrix tool and zoning is performed on switches. In fact, you should not be able to see any switch configuration with any tool unless you have login/password for the switch.
The symmask command is a nice way to verify that the port has connected. Unfortunately there is no way to pull zoning information using SYMCLI commands if you are looking to check the actual zone definitions.
This isn't a tale .. but a very long time ago there was an "fzone" command that worked in pair with the "fpath" command. Both were used to manage the SAN. "fpath" was of great help in masking while "fzone" was used in zoning .. They nicely disappeared (almost) whithout notice. Nobody misses them (AFAIK) ..
The "symmask list hbas" command will show you a line for each VCMDB instance .. If your HBA can't see a VCMDB you will not see lines in its output. It's easier but may lead to misunderstanding
Did anyone notice that the latest Solutions Enabler has added a command called symsan which appears to pull some switch information?
I have not had a chance to install this anywhere yet - but looks like there may soon be a direct way to do this. Maybe this is the response to those of us that miss using the fzone commands
I always run "symmask -sid xxx list logins". This will show every wwn in the vcmdb and whether they're logged in. The outpur can also be used to count the number of active hosts per FA.
This is from the release notes - haven't had a chance to test this out, but looks like a single command where it would have taken multiple to put together this information before. Still not pulling "zone" information directly, but maybe the next release will work towards that.
"The symsan command lists ports visible from a given director and LUNs visible behind a given remote port."
EXAMPLES To list ports visible from a given local port:
xe2sdc
4 Operator
•
2.8K Posts
0
July 31st, 2007 02:00
symmask -sid 123 -dir 4A -p 0 list logins
and search for a line in the output that shows your wwn .. please note that you must find that the line ends with a pair of "Yes" .. This means that the wwn is logged on the FA port and that the WWN is seen in the fabric.
Hope it's usefull
DA
117 Posts
0
July 31st, 2007 04:00
bodnarg
2 Intern
•
385 Posts
0
July 31st, 2007 04:00
xe2sdc
4 Operator
•
2.8K Posts
0
July 31st, 2007 05:00
Both were used to manage the SAN. "fpath" was of great help in masking while "fzone" was used in zoning ..
They nicely disappeared (almost) whithout notice. Nobody misses them (AFAIK)
End of the story
treesk
26 Posts
0
September 6th, 2007 03:00
sun1:/ # symmask list hbas
Identifier Type Adapter Physical Device Path Dir:P
---------------- ----- ---------------- ------------------------ -----
210000e08b02f56b Fibre pci@8,700000/QL* /dev/rdsk/c7t1d0s2 01C:1
210000e08b02f46b Fibre pci@8,700000/QL* /dev/rdsk/c8t1d0s2 16C:0
So from above output you will see first HBA connect to dir 1c port 1 and 2nd hba connect to dir 16c port 0.
Note in case you connect more than one port per hba you will see mutiple line of Dir:P of each HBA.
Regards,
Kawin.
xe2sdc
4 Operator
•
2.8K Posts
0
September 6th, 2007 05:00
xe2sdc
4 Operator
•
2.8K Posts
0
September 21st, 2007 06:00
Unfortunatly I'm still unable to upgrade my hosts to SE 642 .. But I think that sooner or later ..
bodnarg
2 Intern
•
385 Posts
0
September 21st, 2007 06:00
I have not had a chance to install this anywhere yet - but looks like there may soon be a direct way to do this. Maybe this is the response to those of us that miss using the fzone commands
RRR
4 Operator
•
5.7K Posts
0
September 21st, 2007 06:00
bodnarg
2 Intern
•
385 Posts
0
September 21st, 2007 07:00
"The symsan command lists ports visible from a given director and LUNs visible behind a given remote port."
EXAMPLES To list ports visible from a given local port:
symsan list -sanports -sid 123 -dir 3B -port 0
To list the LUNs visible from behind a port:
symsan list -sanluns -sid 123 -dir 3B -port 0 -wwn 0123456789ABCDEF
dynamox
9 Legend
•
20.4K Posts
0
September 21st, 2007 07:00
HemantR
1 Message
0
September 13th, 2019 00:00
If you see it is not logged in to FA then what should be the next steps to fix this, could you please share It would be great help.