Trying to install APIC-EM v1.2 with 16 GBs of RAM for demo purposes. However, it fails trying to initialize the Grapevine services.
- The LAB version is shipping 1.2. It only requires 16G.. however:
we are about to change the release notes slightly.
- A lab version requires anything from 16-24G.
- If your disk performance is not good, you should opt for more RAM.
- Ideally you should use 24G, but there is a slight bug at present (1000^3 < 1024^3) so max you can use is 22G. See how you go with 22G.
- Just to be clear, this is not a different image, it is the same code, it just detects the limited RAM and boots in lab mode. all services work, but only 20 devices are supported.
you might find that does not work with 1.2.
There is a check with three thresholds:
Cisco APIC-EM will discover your host's available memory during the deployment process and will provide the following responses and options:
- When deploying the controller on a host with 64 GB or more of memory (meets the memory requirements), the configuration wizard will proceed with the installation.
- When deploying the controller on a host with 25 to 64 GB of memory, you are prompted to add another host or increase memory on the host to meet the requirements.
- When deploying the controller on a host with 16 to 25 GB or memory, you are prompted to install a low-memory, evaluation version of the controller.
- When deploying the controller on a host with less than 16 GB of memory, you are prompted to add more memory and cannot proceed with the installation.
Hi, when you say only 20 devices are supported, does this include the PnP cababilities. Will it stop pushing configurations out after it's provisioned 20 devices.
- Technically no. The only complication is that part of the PnP process is to add the device to the inventory.
- That is when you might have issues.
- The best option would be to delete the device from inventory once it has been provisioned by PnP.
- there is no "hard limit" on the number of PnP configurations you can make.
Do you know if the PnP capabilities might ever be siphoned off APIC-EM as a standalone product/service, as this is the only capability of the APIC that we need and it would be good to be able to run PnP separately on lower end hardware.
If you use Prime, you can also do PnP there. http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/user/guide/pi_ug/plugandplay.html
PI is moving towards using APIC-EM as the PnP engine. Today you can use PI standalone, but long term direction will be to have APIC-EM as the "universal PnP engine". It will be optimised...