Name resolution latency on site converted from Frame-Relay to VPN
This is a bit hairy, so excuse my detailed explanation as if I were speaking to a child....
One of my customer's has a remote site in Canada on 256/64k Frame-Relay. They need at least 512k for bandwidth picky applications and have a scheduled plan for upgrade to 1Mb in a few months. They couldn't wait for the upgrade and had DSL installed as a temp fix. (NOTE...customer went with cheapest option/equipment available). They purchased a PIX 501 and already had a Cisco 2611 router with 2 ehternets. Then PIX 501 is currently tunneled to a customer VPN access point in to their network. One 2611 router ethernet is connected to the PIX and the other is connected to the site LAN (Cisco 2950s). Testing the VPN connection (without affecting the production Frame-Relay) with a couple laptops was successful with great response time, to include name resolution. Cutting the site over from Frame-relay to DSL wasn't as successful. I shut down the Frame-Relay sub-interface on the old router and moved the single cat5 LAN connection and plugged it in to the new 2611 router. We rebooted all network devices and started fresh. The first few PCs on the LAN worked with great response time. After 10 to 15 minutes any PC that logged on to the LAN would experience a large delay. I had onsite assistance that would run ping and trace tests for me on the PCs experiencing a delay. If pinging by address, the response was excellent (30 to 40ms). If pinging by name, the response was also excellent (30 to 40 ms), but it would take a long time for the results to be displayed on the screen. So any attempts at a device by name would experience latency, but no problems by address. Nothing was changed in DNS/DHCP/WINS, just the routing and network hardware was changed. The same symptoms were seen when running traceroutes. I ran ping to addresses and device names from the switches on the LAN, and didn't experience any latency. One other symptom.....After 15 to 20 minutes, the first few PCs on the network that didn't experience any latency just all of a sudden lost Internet access, but were still capable of accessing other network apps and mail.
Any assistance with this would be greatly appreciated.
Re: Name resolution latency on site converted from Frame-Relay t
To resolve name resolution failures, consult with your system administrator to confirm IP name resolution within the entire network, which includes local device IP configurations, network-based name resolution systems (such as DNS), and DHCP systems.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...