We have recently upgraded our distributed ACS deployment to v5.5 patch 4. We also added a new appliance (3495) to the deployment, this node was supposed to be configured to be a secondary node and the LogCollector. When the LogCollector function is moved to this new appliance (via the primary/administrative node), all of the "view-" services show the status "not monitored" when doing a "sh app stat acs". All other services are running.
When you try to open the "Monitoring and Reports" section, all you get is the warning: "The view database is not available. Try to reconnect ......etc."
Stopping and restarting the application or even rebooting the appliance has been done several times, no effect !!
Here's the kicker:
- When the LogCollector function is moved to another node in the deployment, this does not happen, all services are running .... !!
- When the 3495 is removed from the distributed deployment and runs in primary/standalone mode (therefore being LogCollector of its own deployment), all services run smoothly.
All of the four nodes run the same version, they even have the same patchlevel. The only thing that differs is the hardware:
The Appliance that won't start the services is a new 3495, the other nodes are either 1120 appliance (old, I know !! Plans exist to upgrade these to 3495 soon also), or VMWare ESX 5.5 virtual appliance .....
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...