I have a small SAN Fabric composed of 2 NX5596 adn on NX5548 configured with FC Swiching.
Each Switch is connected with a pair of 2 FC 8Gbps with each other Switch configured as ISL Trunk.
Without San-Port-Channel configured configured everything is working fine, also in the case where only one link between 2 Switches FC is going down.
This failure is e.g. fully transparent with IOMETER and File Explorer.
Instead as I aggregate the pair of ISL Link bwetween 2 Swithces FC within a San-Port-Channel, a failure of Link in the channel issue a timeout with IOMETER for approx. 30-55 secondes and the File explorer may be (Not responding) for a few secondes.
I did the tests with and without IOD, but with almost the same result.
I also did the test with 2 LoadBalancing Type : srcId/DestId/OxId and srcId/DestID and also with almost the same result.
I always though the configuration WITH San-Port-Channel would have better behavior in failure condition as a configuration WITHOUT San-Port-Channel.
Is there something specific to configure within the San-Port-Channel to improve its performance?
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...