I'm currently testing the ACS View 4.0 in a VMWare Environment.
I've added 2 ACS servers who are already in production thus generate enough syslog messages.
The problem is that the ACS Views requires a lot of mandatory attributes that are not generated by my ACS-servers. This results that the syslog messages are dropped by the ACS View Software and so the ACS View cannot make reports of it.
I can see that if I check the server status page. There I have the red cross on the logs which means "Mandatory Attributes Not Received".
For example: the "Bypass_Info" is mandatory, although it contains only info if MAC Auth Bypass is used. Otherwhise, the ACS does not send this attribute in the syslog (although it is configured to be sent so I would expect the ACS would send it with an empty value, like: Bypass_Info=)
Another example is the Athor_Failure_Code which never contains a value on my ACS logs (I can see it in the internal CVS logs that it's empty).
Indeed, I've found out that it isn't necessary to have all the "mandatory" attributes. The ACS View will use the syslogs if the aaa-server attribute is present. But several reports will not be able to view entirely (which seems normal).
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...