- Both PI & APIC-EM offer plug and play services as well as API programmability.
- why should I also invest in APIC-EM. Does APIC-EM provide capabilities that cannot be achieved using PI.
PI 3.0 is built upon APIC-EM in the sense that it uses the APIC-EM controller to facilitate its PnP service. Is this valid to say.. Also if this is true, what is the true difference between both and what is the value of APIC-EM if Prime Infrastructure somewhat covers the major scope of what the average network administrator desires..
It is true that PI now uses APIC-EM for PnP. In terms of differences, think of APIC-EM as a programmatic layer on top of the network (meaning you can extract things like topology, inventory, and network state programmatically). Today, it does PnP, IWAN provisioning, and flow-based path trace. All of these are also driven by a REST-based programmatic interface. Think of PI as a network management application in that it does element, config, and fault management.
What you'll see is that more and more network services will be exposed from APIC-EM that PI can take advantage of, so that PI becomes a set of applications on top of APIC-EM.
while you can use APIC-EM without PI to do PnP today, PI adds a layer of value on top of APIC-EM in that it manages the config templates and software images, and uses the APIC-EM REST interface to drive the provisioning of new devices. Without PI, you'd likely have to build your own application to do this management.
In terms of investment, APIC-EM is freely available. The IWAN feature, however, is cross-licensed with PI, so if you've invested in PI, then you have a license for the APIC-EM features as well.
- Is it true that the IWAN feature is no longer a part of APIC-EM. Is this a permanent or temporary change. If IWAN is not part of the APIC-EM solution, will there be another tool for IWAN automation.With APIC-EM 1.2.1 there is no longer a tab for IWAN and the release notes say that the upgrade will disable the IWAN feature.
That is temporary. 1.2.1 was a patch release. 1.3 the next major release is due in 4weelse and will restore IWAN. There was a bug in Iwan 1.2.1 that needed more time to be resolved. Rather than delaying the patch further and running up against the 1.3 release 1.2.1 patch was released without Iwan.
IWAN is part of APIC-EM. I did not mean to give the impression that it was not. It is, however, a separate license. You get this by default if you have Prime Infrastructure or a Cisco ONE software license.
- What is the interplay between discovery and inventory between the two. If I discover a router in APIC-EM does that information get ported to PI (and v.v.).
There is an API based integration today. PI uses APIC-EM credentials to get a list of network devices in APIC-EM and add them to the PI inventory. It will also create sites etc in APIC-EM too