I'm about to setup 18/4 modules and plan on linking those to our DR site that is using 14/2 modules. Any issues connecting those (currently on 3.3.2 code)? And followup question to that assuming it's OK to run like that:
Prod site is Gen 2 supervisors and could move to 4.X code eventually. While DR site is Gen1 and thus staying on 3.X code. Any concern with FCIP tunnel between 3.X and 4.X code?
We ran into a bug on the 3.3.2 code on our FCIP links. We did an upgrade to the SAN core to resolve the issue. My case was with EMC so here is the information from them.
Problem: Host is unable to communicate with disks using IVR because the Host's PLOGI does not reach the disk and IVR sends a PLOGI reject back to the host.
Root Cause: Cisco bug tracking number CSCsu38135. Access to this bug requires access to Cisco's Bug toolkit.
Have the host logout or login to the fabric (e.g. by flapping the port) multiple times. If this is done every 2 minutes, then 1 in 3 tries should catch the appropriate window, and the host should be able to communicate.
Perform a FCNS refresh on the affected VSAN.
Perform an IVR refresh.
Permanent fix: Fixed in SAN OS 3.3(3) and NX OS 4.1(1b).
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...