Probably one of the reasons it wasn't made more
granular is because when you do a clear arp
it just sends a unicast arp request for any
entry that is currently in the table.
It doesn't actually flush and re-arp so
forwarding using that arp is unaffected as
long as the end station responds to the unicast
arp request.
Rodney
On Wed, Jan 12, 2005 at 02:01:12PM +0100, Sascha E. Pollok wrote:
Folks,
I recently had to debug some customer's ARP problem.
Due to this, I had to flush several of his MAC addresses
from our arp-cache more than once. I found, that the
"clear arp-cache" command supports giving the related
interface using "clear arp-cache interface FastEthernet..".
This is not bad but why doesn't IOS support FastEthernet
subinterface-numbers like "clear arp-cache interface FastEthernet0/1.15" ?
I am still able to clear the arp cache by shut-noshut the interface
but I am wondering why I can give the physical interface, only.
This is on a 12.3(6a).
Anyone?
Cheers
Sascha
P.S.: Yes, I searched Ciscos website - no luck.
5 messages in net.nether.puck.cisco-nsp[c-nsp] clear arp-cache interface on ...
