Re: cam timer tuning

From: Naufal Jamal <naufalccie_at_yahoo.in>
Date: Sat, 29 Dec 2012 01:43:28 +0800 (SGT)

Hi Marko,

Nexus ----------------trunk----------4948
Arp timer:1500 secs
                Arp timer: 4 hours
Cam timer:1800 secs Cam
timer: 300 secs

I know cam timer should be greater than arp timer to avoid
flood. Should we try to make the cam timer in 4948 more than 1500 secs or make
the arp timer in nexus less than 300 (aging arp in 300 secs ?? ) Any inputs?
________________________________
 From: Marko Milivojevic
<markom_at_ipexpert.com>
To: Naufal Jamal <naufalccie_at_yahoo.in>
Cc:
"ccielab_at_groupstudy.com" <ccielab_at_groupstudy.com>
Sent: Friday, 28 December
2012 10:29 PM
Subject: Re: cam timer tuning
 
When I've seen this in the past,
it was usually discrepancy between
host ARP and switch MAC aging timers. Try
lowering timers on your
switches to be under/same as the ARP timers on hosts
and see if there
are any differences.

--
Marko Milivojevic - CCIE #18427 (SP
R&S)
Senior CCIE Instructor - IPexpert
On Fri, Dec 28, 2012 at 1:40 AM,
Naufal Jamal <naufalccie_at_yahoo.in> wrote:
> Hello,
>
> We have a pair of nexus
7K's (without vpc) running HSRP and MSTP.
> They are connected to access layer
switches 4948's. whenever we bring up a new
> trunk link between Nexus 7K and
4948 we see unicast flooding caused due to
> TCN's. I am wondering if it has
something to do with the difference in cam
> aging timer in both the
platforms. Nexus (1800 secs) and 4948 (300 secs). can
> anyone put some light
here please? I am thinking that changing the aging timer
> on nexus to 300
secs should help.. any thoughts?
>
> Naufal
>
>
> Blogs and organic groups at
http://www.ccie.net
>
>
Received on Sat Dec 29 2012 - 01:43:28 ART

This archive was generated by hypermail 2.2.0 : Tue Jan 01 2013 - 09:36:53 ART