Cisco Bug: CSCsy87929 - Memory leak on BGP Acceptor and BGP Open
Jan 28, 2017
- Cisco IOS
Known Affected Releases
12.2(33)SB 12.2(33)SRD4 12.2(33)XND1 12.2REC
Symptom: The router allocates memory, but does not free it. This is shown in the output of the 'show memory debug leak' which shows memory allocated to the name BGP Open and/or BGP Accepter but never freed. Typical output of 'show mem debug leak' would include: Address Size Alloc_pc PID Alloc-Proc Name XXXXXX XXX XXXXX 0 *Dead* BGP Open or Address Size Alloc_pc PID Alloc-Proc Name XXXXXX XXX XXXX 0 *Dead* BGP Accepter Conditions: This problem is only seen if the following all happen: 1. BGP is configured, and there is at least one configured active neighbor, as in: router bgp <asn> neighbor x.x.x.x <otherasn> neighbor x.x.x.x activate 2. A nonzero terminal length is configured, as in: line con 0 length 25 3. The command <cmdBold>show ip bgp neighbors<noCmdBold> is issued, and displays material longer than the terminal length 4. The person viewing the output of the 'show ip bgp neighbors' presses a key other than space, enter, or question mark during the display of information about a particular BGP neighbor prior to the display of detailed TCP connection information 5. Subsequent to step four, an event happens causing the data structures associated with the session to the neighbor in step 4 to be destroyed happens. Configuring 'no router bgp <asn>' is the most easily reproduced example of this, though under load, a link flap with the neighbor can also cause it. This problem is only seen in 12.2(33)SB and later.
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