In the VPLEX best practices it states that there should be be 2 or 4 (optimal) paths from the back end to a volume. If using 4 paths and one of them goes down then both Unisphere and vplexcli (various health check commands) indicate that there is no issue. It is not until just one path remains that either tool highlight a problem. At this time the number of paths is reduced from 4 to 1!
Has anyone come across this issue and a way to effectively monitor the back end for intial path failure?
Have written a little python script which monitors all FC Ports (FE , BE , WAN). It uses the REST API for getting the needed Infos. Let me know if you like to test it in your environment.
The vplexcli shows the status of the FC ports. What would be really useful is something similar to powermt display which shows summary counts of active and dead paths to devices.
You are right, but vplexcli is not as comfortable as it should be. You have to login to vplex ; start vplexcli and again give username and password. Not scriptable at all i think.
Crazy for one who knows symcli ;-)
For now the only solution of controlling / monitoring VPLEX from outside is using the REST API, isn't it?
What's powermt display ? Sounds like powerpath. Not using it for my Solaris Servers.
powermt is part of the powerpath suite. Example here shows Unix host attached to 56 Symmetrix devices and 2 VPLEX devices. (not a usual configuration as normally you would encapsulate all or nothing) All paths to all devices are ok.
HergenLange
4 Posts
3277
0
Posted March 13th, 2015 07:00
Have written a little python script which monitors all FC Ports (FE , BE , WAN). It uses the REST API for getting the needed Infos. Let me know if you like to test it in your environment.
Just don't know if i can upload it.
Send an email to hergen dot lange at olb dot de