The WAAS doesn't play nicely with old legacy mainframe LPR printing. I'm not mainframe guy, which is why I don't know the exact details to how the application was written. I was hoping this was resolved in 4.2.1 but we're still running into the same issue, work around is to bypass it completely. The problem is for every new print job it uses the same source port 721 or 722 and connects on port 515. You will have multiple syns that show up as either 721 or 722 continuously.
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...