So, this is embarrassing 
.
I edited the GUI access restrictions and put the wrong IP address in there. Now I've locked myself out. What do I do?
1 ACCEPTED SOLUTION
Accepted Solutions
Whoops!
Yep - if you go to System->Security->Access Restriction and put a non-existent IP address (1.1.1.1 or something) for the access restriction list, you won't be able to log in. You'll be locked out of the GUI (including SOAP, REST and CLI), and if you are using the virtual appliance, you’ll be locked out from SSH access as well:
Don't do this....
Get a console on the system (ssh if possible, or direct console access through your hypervisor). Edit the config file $ZEUSHOME/zxtm/conf/security and remove the line beginning ‘access’.
The traffic manager should pick up that the file has changed and apply the change, and reconfigure the SSH access restrictions in the case of the virtual appliance.
Note that you can also configure a traffic manager to have restricted access to a cluster; the GUI, CLI and APIs are disabled and the traffic manager is not allowed to make configuration updates to the cluster. In this case, refer to the article What to do if you need to access a restricted Stingray Traffic Manager
Whoops!
Yep - if you go to System->Security->Access Restriction and put a non-existent IP address (1.1.1.1 or something) for the access restriction list, you won't be able to log in. You'll be locked out of the GUI (including SOAP, REST and CLI), and if you are using the virtual appliance, you’ll be locked out from SSH access as well:
Don't do this....
Get a console on the system (ssh if possible, or direct console access through your hypervisor). Edit the config file $ZEUSHOME/zxtm/conf/security and remove the line beginning ‘access’.
The traffic manager should pick up that the file has changed and apply the change, and reconfigure the SSH access restrictions in the case of the virtual appliance.
Note that you can also configure a traffic manager to have restricted access to a cluster; the GUI, CLI and APIs are disabled and the traffic manager is not allowed to make configuration updates to the cluster. In this case, refer to the article What to do if you need to access a restricted Stingray Traffic Manager
