Cisco Bug: CSCvt34512 - BNG Iedge delays causes wrong DHCP mode-class to be selected
Sep 02, 2020
- Cisco ASR 9000 Series Aggregation Services Routers
Known Affected Releases
Symptom: Iedge may stall on a new session creation, due to the new feature "subscriber database batch-control" which is set by default on 1000msec batch processing. When DHCP is waiting for session creation response from iedge, it receives another DISCOVER and while processing that packet default profile name is updated in the client structure and packet is dropped. Once iedge responds for session creation, DHCP will read the RADIUS parameters like class, match-mode-class, pool etc. from subdb. While selecting the profile based on match mode-class value, it looks for the base profile name from client structure. Since that value is already updated with default profile value, it is unable to get the base profile name and continue to use default profile and proceeds with session creation. Conditions: "subscriber database batch-control" set to default 1000msec, which exposes the problem in DHCP code when multiple DISCOVER are received from the same CPE.
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