Guest

Preview Tool

Cisco Bug: CSCuw56267 - DMVPN Phase3: Improve insufficient resources NHRP error - route conflict

Last Modified

Jan 10, 2016

Products (111)

  • Cisco IOS
  • Cisco 886VA-CUBE Integrated Services Router
  • Cisco 892W Integrated Services Router
  • Cisco C892FSP Integrated Services Router
  • Cisco VG204XM Analog Voice Gateway
  • Cisco 898 Secure G.SHDSL EFM/ATM with Multi-Mode 4G LTE ISR Router
  • Cisco 886VAG 3G Integrated Services Router
  • Cisco 819 Hardened Integrated Services Router
  • Cisco ASR 901-6CZ-FS-D Router
  • Cisco 861W Integrated Services Router
View all products in Bug Search Tool Login Required

Known Affected Releases

15.5(3)M 15.5(3)S

Description (partial)

Symptom:
When a spoke tries to build a tunnel with a remote spoke, NHRP resolution requests for the remote network [192.168.100.x/xx] may result in the following NHRP error while installing Next-Hop override routes for the remote network:

%DMVPN-3-NHRP_RESOLUTION_ERROR: Tunnel815: Received Resolution Reply Error indication for Resolution - insufficient resources(5) Src (Tunnel: 10.1.1.1 NBMA: 172.16.1.1) Dest (Tunnel: 192.168.100.1 NBMA: UNKNOWN)

this is not really an resolution reply error received from the peer spoke, instead is an error generated locally on the router while processing the resolution reply from the peer spoke for the given Network [192.168.100.x/xx].

What really happens here is, when the spoke receives resolution for a remote network, if the spoke already contains a route, in this case 192.168.100.0/24, and the resolution reply contains a prefix other than /24, the spoke throws NHRP_RESOLUTION_ERROR - Received Resolution Reply Error indication for Resolution - insufficient resources(5). Here this error has to be interpreted as one due to conflicting route and the spoke's inability to install Next-Hop override, instead of an actual NHRP error indication received from the peer spoke.

Conditions:
DMVPN Phase 3 deployment. 
IOS Spoke to Spoke to tunnel establishment is expected.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.