Youssef, >> The TCAM is based on routing information, it doesn't learn in the same >> way. It is built from all of your RIP routes for instance and will not >> dynamically change depending on source / destination traffic. > step 1 : TCAM empty > $> show cam ip 3/12 > Slot Index IP_Address MAC Age VLAN Out Port > step 2 : a ping from a machine that is connected behind port 3/12 to a > some prefix (lets say 192.168.9.3) > step 3 : the TCAM get filled with a route to the 192.168.9.0/24 > $> show cam ip 3/12 192.168.9.0 255.255.255.255 > Slot Index IP_Address MAC Age VLAN Out Port > 3 10348 192.168.9.0/24 001b.ed24. 5 0 128 mgmt
Ok, so this device is removing prefixes from TCAM after a certain period of time to save space at the expense of 1st packet lookups (as you mentioned). Note: It will only ever do that for routes in the routing table. > M1 : 192.168.1.3/24 is in building A (with a default gateway on B) > M2 : 192.168.2.3/24 is in building A (with a default gateway on B) > M3 : 192.168.3.4/24 is in building A (with a default gateway on A) > M4 : 192.168.3.3/24 is in building A I'm assuming you have dot1q between A and B? Do you not have a L3 interface on A in 192.168.1/24? > machine 1 -> A(L3) -> B(L3) -> A(L2) -> machine 2 is very very slow. > machine 1 -> A(L3) -> machine 2 is fast > machine 1 -> A(L3) -> B(L3) -> machine 2 is fast Where is machine 2 physically located - building A or building B? Is the 50Mb/s pushing close to 100% on some port? Why is it only at 50Mb/s? _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
