130kms is going to add some serious latency so you have to be doing asynchronous TC. Don't ever consider doing sync TC.
I believe B2B credits on a 9509 are allocated as required. You could keep an eye on what is happening and then set them statically if necessary. I think that by default, 250 B2B credits are available per port and thats enough for that distance. The rule of thumb is 1 B2B credit for a 2 Gpbs port so 130 km will only need 65 B2B credits but it never hurts to have more.
I tend to leave everything as is unless advised by the vendor. Get HDS in on this to stop any heartache when it goes pearshaped.
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...