Ran into this issue in 184.108.40.206. For reference,CSCvc13812. Unable to actually look at these bug IDs in detail. We click the links and it tells us that we have insufficient permissions to view these bugs. That goes for all bug IDs in the recent APIC-EM release notes. This was working fine with the same version and nothing has really be done while deploying a new rule successfully.
The initial bug was editing a single device rule and converting it to a stack.
Unable to add a single device rule since cannot accept the EULA, but a multiple device rule works with no issues. Using a 3650-24PS/ 3650-48PS. For example, can make a complete rule or can just put in the bare minimum information and no configuration. Both of these break with the "you must accept the EULA" error when attempting to add the rule. A stack works fine with the same configurations that was using for the single device rule.
The only way you can specify a license it to choose a stack.
All of the parameters in the red box are stacking parameters. If you select a licence, then that implies a stack. If you do not specify a member count then it defaults to 7.
Since you had been using the stack configuration section on all deployments, even single switches should use just a stack of 1. Since there was no "1" in the expected member count is needed, you have just been leaving that blank.
- When doing this in the latest version, it should tell you that you need to accept the EULA.Still may be nice to spit out a different error message if someone leaves the expected member count blank and fills out the license/EULA.
The current behaviour is to set member count to 7 if you leave it blank.
there are a couple of things here.
1) for switch stacks, if you have different licenses on the members, the stack will be split in two, so we need to have licence changes for stacks and stack members.
2) In order to do this for non-stack, we need to support all devices, routers, switches etc. Currently there are different mechanisms on routers for licensing and enforcement
3) For the 3850 and 3650 (common stacks) licensing is RTU, which makes it much simpler to change in the stack scenario.
looking at more general license integration in future.