Possible Cause | Possible Resolution |
---|---|
■ zASA instance or service is down (instance creation is in-progress) ■ zASA instance is powered off ■ zASA internal error | ■ Verify that the zASA instance is up and running. ■ Once a new VPG is created, a new zASA instance is created automatically again. ■ Terminate zASA and restart the ZVM. |