I have a dual-hub mGRE network setup over an MPLS network. I am using EIGRP for routing and it generally seems to be working well as far as data and routing go. VoIP is another matter. We are seeing inconsistent reports on call quality. We have QoS setup with service provider and on mGRE tunnels. Since all traffic goes over MPLS we are not using IPSec. Utilization on the circuits is very low. Most circuit usually run only 20-40% utilization.
So I start digging around and found two things that seem odd:
1) When I do "sho ip nhrp" I notice most of the registrations have the NAT flag set. This I find out because there is no NATTing being done anywhere.
2) NHRP registration routinely counts down to 0:00 before re-registering. I was under the impression that a client will refresh its registration at 1/3 interval of nhrp holdtime but this doesn't seem to be working. I currently have holdtime set at 28800 because all IPs are static. I have tried other holdtime settings and also tried setting the ip nhrp registration timeout but registration still counts down to 0:00.
Should I be worried about this? Or should I keep looking for another problem?
1) "This setting is on NHRP mapping entries that are from NHRP registration packets. This indicates that the remote node (NHS client) supports the NHRP NAT extension type for supporting dynamic spoke-to-spoke tunnels to or from spokes behind a NAT router. This flag does not mean that the spoke (NHS client) is behind a NAT router. "
2) Usually NHRP registrations are refreshed at a 3rd of the holdtime as you said. That's what I see in my environment. You should have closer look here. Nevertheless, I wouldn't expect bad call quality caused by NHRP problems. If there was a problem, the calls would probably get interrupted.
The doc you reference on the NAT flag seems to be very clear. What bothers me is that it appears to be random. I have about 20 routers on the mGRE network. At any one time, "show ip nhrp" will show about half with the NAT flag. I would be happier if I could find some consistency on this but I guess I will have to live with it.
The sympton I get from spoke-to-spoke VoIP callers is that when they get a bad connection they immediately hang up and call again and the second call is clear. I thought this might have to do with the spoke initially being routed thru the hub and then switching to direct link with the other spoke after learning spoke NBMA address.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...