 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Journey of a Network Engineer &#187; mn</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/network-engineering-journey/tag/mn/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/network-engineering-journey</link>
	<description></description>
	<lastBuildDate>Tue, 26 Feb 2013 11:05:07 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>GRE Tunnel ARP entry never times out! &#8211; part 2</title>
		<link>http://itknowledgeexchange.techtarget.com/network-engineering-journey/gre-tunnel-arp-entry-never-times-out-part-2/</link>
		<comments>http://itknowledgeexchange.techtarget.com/network-engineering-journey/gre-tunnel-arp-entry-never-times-out-part-2/#comments</comments>
		<pubDate>Mon, 30 May 2011 09:35:44 +0000</pubDate>
		<dc:creator>Sulaiman Syed</dc:creator>
				<category><![CDATA[6500]]></category>
		<category><![CDATA[AP]]></category>
		<category><![CDATA[ARP]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[GRE]]></category>
		<category><![CDATA[mn]]></category>
		<category><![CDATA[SUP720]]></category>
		<category><![CDATA[Tunnel]]></category>
		<category><![CDATA[wireless]]></category>
		<category><![CDATA[WLSM]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/network-engineering-journey/gre-tunnel-arp-entry-never-times-out-part-2/</guid>
		<description><![CDATA[I have been trying to figure out why the APR entries don&#8217;t timeout as they should do naturally from the tunnels. As it seems, the natural time of 4hr is not being applied here. For some uknown reason yet. We have opened up a TAC case with Cisco. Roger Nobel (CCIE WIreless#23679) is really helpful [...]]]></description>
				<content:encoded><![CDATA[<p>I have been trying to figure out why the <a title="GRE Tunnel ARP" href="http://itknowledgeexchange.techtarget.com/network-engineering-journey/gre-tunnel-arp-entry-never-times-out/">APR entries don&#8217;t timeout</a> as they should do naturally from the tunnels. As it seems, the natural time of 4hr is not being applied here. For some uknown reason yet. We have opened up a TAC case with Cisco. Roger Nobel (CCIE WIreless#23679) is really helpful and efficient.</p>
<p>So, in our troubleshooting so far, we tested how the MN is associated with AP, is the association with AP remains after MN is disconnected, does the SUP720 maintains a record for this MN. what we found so far is the following.</p>
<p>After the MN is disconnected from AP. The AP will clear the association in less than 1 min. and in another 5 mins this association will be cleared from the SUP720 as well. it can be seen from the following commands</p>
<blockquote><p>WLAN-CORE-1#show mobility mn ip 10.13.115.150<br />
MN Mac Address  MN IP Address  AP IP Address  Wireless Network-ID  Flags<br />
&#8212;&#8212;&#8212;&#8212;&#8211;  &#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;-  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-  &#8212;&#8211;<br />
b407.f9ea.a941  10.13.115.150  10.254.14.172  8                      F</p>
<p>Flags: D=Dynamic network ID, F=Fresh, G=Grace Period</p>
<p>WLAN-CORE-1#show mobility mn ip 10.13.115.150<br />
MN with ip 10.13.115.150 is not found in database</p></blockquote>
<p>Now naturally, the ARP entry should stay for 4 hrs (default Cisco). but in our case it says forever! we have ARP entries as old as 10 days without adding any configurations. The command does not even show any timer for timeout as it shows in other physical interfaces.</p>
<blockquote><p>WLAN-CORE-1#show int gig 5/1<br />
GigabitEthernet5/1 is up, line protocol is up (connected)<br />
Hardware is C6k 1000Mb 802.3, address is 0011.5cb4.c2a4 (bia 0011.5cb4.c2a4)<br />
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,<br />
reliability 255/255, txload 1/255, rxload 1/255<br />
Encapsulation ARPA, loopback not set<br />
Keepalive set (10 sec)<br />
Full-duplex, 1000Mb/s, media type is T<br />
input flow-control is off, output flow-control is off<br />
Clock mode is auto<br />
ARP type: ARPA, ARP Timeout 04:00:00</p></blockquote>
<p>here is how the tunnel interface looks like</p>
<blockquote><p>WLAN-CORE-1#show int tunnel 1<br />
Tunnel1 is up, line protocol is up<br />
Hardware is Tunnel<br />
Description:<br />
Internet address is X.X.X.253/20<br />
MTU 1514 bytes, BW 1000000 Kbit, DLY 500000 usec,<br />
reliability 255/255, txload 1/255, rxload 1/255<br />
Encapsulation TUNNEL, loopback not set<br />
Keepalive not set<br />
Tunnel source X.X.X.1 (Loopback1), fastswitch TTL 255<br />
Tunnel protocol/transport multi-GRE/IP, key disabled, sequencing disabled<br />
Checksumming of packets disabled, fast tunneling enabled<br />
Last input 00:00:00, output 00:00:01, output hang never<br />
Last clearing of &#8220;show interface&#8221; counters never<br />
Input queue: 0/75/125/37 (size/max/drops/flushes); Total output drops: 0<br />
Queueing strategy: fifo<br />
Output queue: 0/0 (size/max)<br />
5 minute input rate 318000 bits/sec, 226 packets/sec<br />
5 minute output rate 3458000 bits/sec, 355 packets/sec<br />
L2 Switched: ucast: 0 pkt, 0 bytes &#8211; mcast: 0 pkt, 0 bytes<br />
L3 in Switched: ucast: 0 pkt, 0 bytes &#8211; mcast: 0 pkt, 0 bytes mcast<br />
L3 out Switched: ucast: 0 pkt, 0 bytes mcast: 2989660 pkt, 922842977 bytes<br />
249194378 packets input, 54362827775 bytes, 0 no buffer<br />
Received 1308901 broadcasts (71327 IP multicasts)<br />
0 runts, 0 giants, 18 throttles<br />
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort<br />
327413145 packets output, 259801658657 bytes, 0 underruns<br />
0 output errors, 0 collisions, 0 interface resets<br />
0 output buffer failures, 0 output buffers swapped out</p></blockquote>
<p>I would wait for Mr. Roger to come back and see what possible thing is causing this.</p>
<p><span style="font-family: 'Arial','sans-serif';font-size: 10pt"><br />
</span></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/network-engineering-journey/gre-tunnel-arp-entry-never-times-out-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
