It would depends on how many devices you have. As a comparison, so you have some numbers, we have:
~80 Cisco 4235 IDS sensors
~70 Pix 525/535 Firewalls (11 clusters in Europe)
~3 Checkpoint Firewalls
~12 Cisco 3000 VPN Concentrators
All of these are spread across two PN-200 appliances. We have approximately 15 environments spread across these two boxes. The way we handle reporting and alerting for these environments is create reports that run daily, weekly, and monthly, analyzing only those devices tied to those environments. For example, we have:
Internation Web Page and Reservation (3 centers)
2 Firewalls, 5 IDS sensors per center
Employee Internet Access (2 domestic)
1 Checkpoint, 2 IDS sensors for each center
Business Partners (2 centers)
2 525's, 4 IDS for each center
SMTP/Mail (2 centers)
2 525s and 4 IDS for each center
Etc. Since we've logically separated the environments by hardware, we just make the reports with the pertinent hardware for each environment, and generate reports for those environments. it works just fine (albeit with everything we have, the PN-200's are both pretty slow when doing anything else).
If you have shared infrastructures across the same hardware appliances/devices, it may be tougher to accomplish. However, those environments should be separated across different networks, and in those reports, you could separate what is reported based on what network ranges you use for each environment.
Mutliple MARS appliances would obviously be better, all pointed at a GC, but for most, that's pretty cost prohibitive, especially considering the cost of the GC alone.
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...