•After upgrade to 2.0(1s), blades with UCS M81KR adapters will not show the error "initialize error 4" during FC boot.
CSCtt41541 - Upgrade to 2.0 is disruptive if customer has QoS policies.
•While upgrading to UCS 2.0 with QoS policies defined , QoS policies will not generate error messages and VIFs with QoS policies defined on them will remain up after upgrading the subordinate interconnect but before upgrading the primary interconnect.
For customers asking "which version of 2.0 should I upgrade to" - this would be it as of today. After the major release of 2.0, these minor patches only address bug fixes and do not introduce new major features. There is an upcoming Maintenance Release (MR1) will which include new functionality.
As always, if there are any issues please let us know.
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...