Device packages are managed by third party vendors.
If the major version (the naming property of class
vnsMDev) changes, uploading the new device package will create a new package. For example, if the original Cisco ASA package distinguished
name was "uni/infra/mDev-CISCO-ASA-1.0" and the new package version changed to "2.0", then the new distinguished name will
When importing a device package with a major version change, old service graphs and old device clusters will continue to point
to the old package and will continue working. New service graphs and new device clusters can choose to use either the old
or new device package. However, switching an old service graph or device cluster to the new package will be disruptive.
Changing the minor version (a property called
minorversion in the MO called
DevScript) does not change the distinguished name of the device package or the
Uploading a new device package with a
minorversion change overwrites the existing device package. All graphs and device clusters pointing to the old device package start pointing
to the new package automatically. The upgrade is non-disruptive and there should be no impact for existing service graphs
or device clusters.
A minor version change is the default recommendation for partners for any new device package revisions.
When using a device package, a device cluster can be managed by only one device package at any time.
A node in a service graph can associate to only one device package at any time.
The node in the service graph and the associated device cluster should point to the same device package. That is, you cannot
have a node in a service graph that points to the old device package while the device cluster points to the new package.
The Application Policy Infrastructure Controller (APIC) treats the version field as an opaque string. A change from "1.0" to "2.0" as well as "1.0" to "1.1" both look the same
to the APIC and are considered to be a major version change.
The APIC images are backward compatible with old device packages.
If a device package is already uploaded and the APIC is upgraded, the old device package will continue to work without any disruption.
Newer device packages might not work on older versions. In such cases, the device package upload step will fail with an appropriate
Make sure that the device package is supported on the vendor device (hardware and software) and that the device package is
compatible with the Cisco Application Centric
Infrastructure (ACI) platform. For more information, see the L4-L7 Compatibility List Solution Overview document at the following location:
Understand the differences between major/minor version changes on the device package and the impact when upgrading a device
Understand the features to be configured through the APIC by way of the device package to the services appliance. For example, understand the features on the firewalls or load balancers
that the administrator wishes to configure versus the features that are supported by the device package.