We are currently running 10 UCS sites at various locations and recently fired up a syslog project to be able to collect all events but have halted along the way. The idea was to collect syslogs from each UCS system to the same syslog server. Our approach on how to seperate the sites was to have each system send data on different ports... However we're unable to configure custom ports.
The only way we can identify each system today (by design in UCS) is by its IP address, this does however not work very well since some of the sites are using the same IP addresses.
Is it possible to send syslog data to a custom UDP port?
Would it be possible (in future release) for the UCS to include the system name or similar in the event being sent to syslog server?
Currently you are not able to modify the syslog port. This is not on any roadmap in the near future either. There would need to be more demand for customized syslog ports, which we don't have other than this request to date.
It is something that is a known issue, and we are working on prioritizing it in an upcoming release. Feel free to reach out to me directly to discuss this further. My email is ericwill at cisco dot com.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...