#1, check the /opt/emc/scaleio/gateway/webapps/ROOT/WEB-INF/classes/gatewayInternal.properties file and look for "gateway.token.no.activity.timeout.in.seconds=600". 10 minutes is the timeout by default (This is from 2.0.1.3 Gateway). I'm not sure if there is a tomcat timeout that might interfere with setting this higher, but you are welcome to try changing this and see if it makes a difference. Restart the gateway when changes are made.  #2, The only ESRS piece that looks like it will help here is "/api/types/Esrs/actions/checkConnction"  #3, ScaleIO isn't aware of the VMs on the OS. This will need to be a PowerCLI script or something similar to query that information.  #4, To check and see if RAM Read Cache is enabled is a little trickier, as there is no specific check, other than from the --query_all correlating rest api call (/api/instances). So in that case, you would have to make that call and then parse the output for whichever component you are interested in (Pool/SDS/Volume).  Hope that helps
Hi there,  I am trying to collect ScaleIO nodes related information via restAPI and was unable to find some information. Couple of questions: 1. On using restAPI to collect the information, the key generated on login is used to do any further posts. This key keeps expiring every 5 minutes or so. Is there any other way in restAPI to have a certificate or keys which lasts for days? 2. Where can I find whether ESRS is enabled or not using restAPI? 3. Is there a way to get information on VMs installed on SCaleIO nodes via restAPI? Atleast the names of these VMs sitting on ScaleIO nodes? 4. Where can I find ram cache information for the ScaleIO using restAPI? I see this info on executing command: scli --query_all  true   cached  Thank you, RItu
ScaleIO 2.0 version RestAPI