Forum Discussion
10 Replies
Replies have been turned off for this discussion
- nelsonNovice I`purehost monitor` can help you identify the path but it sounds like you might already know which path is working and which is not. you've gone down the right path to figure out the root cause of the issue through that support case. not a lot you can do on your own without support
- jhunterNovice IYeah, I'm 99% sure I've got the configs on our MDS Switches correct, but nothing connected to this array is hitting this particular port for some reason
- purestorage_migNovice IDid you check fabric logins on the mds site? Did you double check you zoning, vsans, is this new setup, new server, were there any changes done on pure, mds etc...?
- jhunterNovice IThere are no flogi to that port's MAC. I have double checked zoning, vans, fcalias, etc... it all looks right... in the pure array GUI it even says some hosts are connected on that port but i don't see the paths in vCenter or in the flogi database on the MDS switch
- jhunterNovice Idid a little more digging and if i do a pureport list --intiator --raw --filter "'name ='CT1.FC9'", which is the port in question, i see a bunch of hosts logged in
- jhunterNovice Ii'm totally baffled
- nelsonNovice Ioh interesting, possibly zoning on the host ports that aren't logged in then?
- jhunterNovice Izoning on the mds ports you mean?
- jhunterNovice Ithe really odd thing is that even the hosts that say they're logged into that CT1.FC9 port on Pure Array side aren't getting any paths to it on the vCenter side (or in the flogi DB on the MDS side hitting the MAC of the Pure Array port)
- nelsonNovice Isorry yes the ports on the mds. and that is interesting