VC3.evolveip.net
- TRM Servers live which are Resource Management Servers for Builds/Reboots etc.. There is only one for the entire DaaS Platform. If there are numerous customers/people rebooting or building VM’s etc., you will likely see processes hang or error out until the load calms down.
- EC01/02 – Servers are the Connection Managers. They each have one main IP and a backend IP (169.x.x.x) so they can communicate to the service center etc.. The primary (01) will have Virtual IP associated to it in vSphere
- AP01 Virtual Server – Access point containing the external IP for the tenant portal (ex: svp.evolvedaas.com). Provides access to the portal
VC4.evolveip.net (Vegas Version of VC3)
VC5.evolveip.net
TROUBLESHOOTING TIPS:
- Service Center URL: https://svp.evolvedaas.com/index.action
- Local Desktop Logins (.\PC) (Pass: (Revol***)
- If the client cannot access the portal
- Could be Network related in general
- Log onto a Tenant Server on vc3 and try and access the portal (https://svp.evolvedaas.com/index.action). If this is accessible, there may be an issue with the Access Point (AP01) Server. If this is not accessible, then look into networking issues.
- Desktops cannot be launched
- SSH onto the primary Service Center Server and then to the Primary EC0? Server.
- tail -f /var/log/desktone/desktone.log – Check for errors
- tail -f /var/log/slony – Check for errors
- If errors are found relating to service interruptions, then first attempt you can complete the following:
- power both EC Servers down and wait for service center to show them both red then power one on (01) and wait until it is up then the 2nd - takes ~15). They will show up green in Service Center
- If the above does not fix the issue, complete the following KB article.. executing on both servers.. enter line on 01 server.. then enter line on 02 server and so on.
- http://ckb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2074777