If the servers already have the agent installed, you need to move them to into the required group that is associated with the appropriate policy & rule modules! You can search their hostnames, select the server, then "modify group membership".
This question reminded me of a CSA implementation I worked on where the customer suggested a witty solution to a common problem.
Here was the situation:
60 servers and a limited maintenance window.
As you know to install CSA requires a reboot. In most cases this can only be done during a maintenance window.
Given that my client had limited knowledge of CSA, and a month between maintenance windows, they elected to install the agent on all 60 servers in a single maintenance window. Immediately after they rebooted the server they disabled the CSA agent. In this way they were able to enable the agent at their own pace, as they grew more familiar with the product. They also avoided the nightmare of watching 60 servers report to the Management Center at one time and all the possible configuration errors that newbies can so easily make upon first installing CSA. They also didn't have to keep scheduling downtime for server reboots.
Moral of the story: It pays to listen to your customer because you never know when they will suggest a very plausible solution.
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...