If you have the remote clients pointing to a publicly available CSAMC, then they can get configuration changes. Basically you just have to set the agent to poll every minute or so in the agent kit. When the agent polls, it contacts the management center and asks if its config has changed. If the config is different, it downloads the changes and updates itself.
Right. The CSAMC can still be a local server, you just need a public IP address NATed to the private IP address.
One problem you will face is resolving the MC server. The agents try to connect to the server's Hostname. So what you will want to do to make this work is add a static record on your internal DNS server so the full hostname resolves to the local IP. Then register a public record with your ISP so the public IP also resolves to your Hostname (and the NAT will take care of the rest).
There is 1 caveat though - if you're using an internal domain suffix that is non-conformative to public dns suffixes, then you'll have to rename your server. For example, my MC might be "csa1.domain.local", so I can't register that with my ISP. So I will have to rename it to something like "csa1.mysitename.com". Then I can register that with my ISP, and I can still add a static record on my local dns server that points that hostname to the private IP address.
Now... if your mobile uses almost NEVER come back to the local network, then you could just add an entry in their HOSTS file after you set up the NAT. Then you wouldn't have to deal with dns and renaming the mc.
If he can't register a public record for his internal hostname, then his only option is to rename the MC. But I suppose I left the most important part out - you're not just changing the name. You'd have to reinstall the MC and redeploy all the agents too.
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...