Cisco Bug: CSCut08639 - GetNextAddress ignores client-class name
Feb 27, 2015
- Cisco Network Registrar
Known Affected Releases
Symptom: When using the web services REST interface and requesting a DHCP address using the action=getNextAddress action you receive an IP address from an unexpected Scope which doesn't have selection-tags configured which match the selection-criteria of the specified client-class. Conditions: You have client-classes which specify selection-criteria, and Scopes with selection-tags configured. You use the action=getNextAddress with clientClass=<some-client-class-name>.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases