Guest

Preview Tool

Cisco Bug: CSCur06845 - NHRP control packets should be forwarded preferably on the same cloud

Last Modified

Aug 15, 2017

Products (109)

  • Cisco IOS
  • Cisco 886VAG 3G Integrated Services Router
  • Cisco 888W Integrated Services Router
  • Cisco 2951 Integrated Services Router
  • Cisco C892FSP Integrated Services Router
  • Cisco 898 Secure G.SHDSL EFM/ATM with Multi-Mode 4G LTE ISR Router
  • Cisco 819 Hardened Integrated Services Router
  • Cisco 861W Integrated Services Router
  • Cisco C897VA Integrated Services Router
  • Cisco ASR 901-6CZ-F-D Router
View all products in Bug Search Tool Login Required

Known Affected Releases

15.3(3)S 15.4(3)S 15.5(1)S 15.5(2)S 15.5(2)T

Description (partial)

Symptom:
Symptom1:Spoke-spoke tunnel doesn't come up with CTS enabled

Symptom2:H routes are created on spoke1 with next hop as Hub instead of spoke2
1.On B2MCBR I see H routes for co-located ISP1/ISP3,pointing to wrong next hop which is Hub border router(HMCBR).
 
B2MCBR:
  100.20.1.1/32 [250/1] via 53.1.0.1, 00:01:14, Tunnel30
                       [250/1] via 52.1.0.4, 00:01:49, Tunnel20
                       [250/1] via 51.1.0.1, 00:01:19, Tunnel10
B1MCBR:
H        100.30.1.1/32 [250/1] via 53.1.0.5, 00:02:44, Tunnel30
                       [250/1] via 51.1.0.5, 00:02:42, Tunnel10
2.After some time on B2MCBR , H route for Tunnel 30 is updated with correct nexthop 53.1.0.4(B1MCBR)
        100.20.1.1/32 [250/1] via 53.1.0.4, 00:01:37, Tunnel30
                       [250/1] via 52.1.0.4, 00:04:06, Tunnel20
                       [250/1] via 51.1.0.1, 00:01:40, Tunnel10
B1MCBR:
H        100.30.1.1/32 [250/1] via 53.1.0.5, 00:09:08, Tunnel30
                       [250/1] via 51.1.0.1, 00:04:06, Tunnel10

Conditions:
Symptom1:CTS inline tagging enabled
Symptom2:Hub border is connected to two ISPs.
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.