Using the APIC-EM controller to stage a number of 3650 and 3850 stacks and standalone switches.Want to set the licensing on each switch (stack or standalone). It looks like the licensing is part of the stack configuration and even though we set it in the project file, the standalone switches did not take the licensing (as we defined it in the project file).
Here is an example of the project file e are using:
We are going to try putting a "1" in Stack Member Count on the next batch to see if it makes a difference.
|Serial Number/Mac Address(AP only)||Device Name*||Product ID*||Config Name||Bootstrap||Image Name||Device Certificate*||SUDI Required*||Stack Member Count||License Level||EULA Accepted|
There was another thread on this. Licences only apply in stacks.
The reason is that if the licences are different on stack members, the stack will break into groups, so we needed to fix it there.
Today, licensing is different on various platforms (routers, switches etc), so it is difficult to apply a general licensing scheme to all single member devices.
In future this will change.
Tired another batch with stack members set to 1. Licensing didn't take and the provisioning never completed (they are all stuck in "Deploying Image".
So don't use stack member = 1 to try to fake out the controller into applying the licensing
|2017-02-06 12:45:57 (Pacific Standard Time)||Device authentication status has changed to None|
|2017-02-06 12:32:42 (Pacific Standard Time)||Image upgrade was performed successfully|
|2017-02-06 12:08:59 (Pacific Standard Time)||UNCLAIMED|
|2017-02-06 12:08:48 (Pacific Standard Time)||Received new work request from Agent while expecting work response. Retrying operation RETRIEVING_IP_ADDRESSES_PRE_CONFIG|
|2017-02-06 12:08:14 (Pacific Standard Time)||Received new work request from Agent while expecting work response. Retrying operation FILESYSTEM_INFO_REQUESTED|
|2017-02-06 12:08:09 (Pacific Standard Time)||Device authentication status has changed to Authenticated|
|2017-02-06 12:07:36 (Pacific Standard Time)||Device first contact|
Please sign in to leave a comment.