Cisco Bug: CSCur15073 - Exhausted IP Pool affecting "hnbgw-service mci-hnbgw1" towards Iuh
Feb 21, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: Few days back we reported seen for cs-network cs1 some IP's from RTP IP Pool showing as 'Unassigned'. Configuration wise all matched to the number of PSC2 cards in the chassis. Nothing was discovered even though same configuration existed before and after seeing this problem. Back then, issue affected legacy Femto services. (Attached email discussion for reference) This time the issue is noted towards 'hnbgw-service mci-hnbgw1' which is bound to context mci-iuh from MCI Configuration. Status of several IP's was: 'Unassigned' state. This is the 2nd occurrence of this "Unassigned" trouble which leaves the HNB-GW blocking any CS Calls that happen to use or attempt to use an IP address that is "Unassigned". Eventually all IP's will end up in similar wrong state which is not acceptable. The RTP Pool configured on mci-iuh side has a complete /24 subnet even though we only need 96 IP's due to active # of PSC2 cards. We need your immediate attention to investigate why this happens as we have not found the apparent reason to this trouble and there seems no way to go out of this condition until ASR5000 chassis is restarted, which is not acceptable either. Some early CDET refer that this condition happens when a config of RTP pool parameters is applied or when binding new RTP pool to such entities. NO CONFIG happened or was manipulated when the issue happened. Conditions: 1. There seems no apparent condition for the issue to occur. 2. When the problem shows up, no CS Calls are possible for the attempts of using the IP address that appears under Unnasigned state. 3. When trying to find a workaround, the binding/unbinding sctp address to the hnbgw-service or unbinding/binding the rtp pool to that service, does not help at all. Problem escalates until all IP's available in the pool, show the same wrond state: 'Unassigned'!!!
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