This is my oversimplified deployment strategy that I hope my fellow Net Pros will add to and comment upon.
I have found this methodology gives me the most control over the deployment.
To begin, the CSA Management Center needs a fully qualified domain name for CSA clients to be able to poll it. Set up the server and enter its name in your DNS. I then load a test mode kit on my laptop which I keep in the same room as the CSA-MC. If the kit downloaded to the laptop doesn't interfere with normal activities, then I download this kit to a PC that's in close proximity. During this time I keep a close eye on the events log of the Management Console and question each and every entry. You might be surprised at what your applications are doing, not to mention your end users. I create exceptions to rules where needed and fine tune the configuration while tightening up the rule set.
The point here is to create a test group that is near to your Management Center so that feedback on the deployment is rapid and can be undone if needed very quickly.
The other idea here is to carefully select the end users and try to achieve a cross section based on location, department, and function.
If you are going to deploy CSA on servers do it last after you get the hang of the implementation and moving the clients from test mode to live mode.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...