show ip cef summary (english translation)

merryllem · ‎07-10-2008

Greetings all,

Like the subject says I need an english translation of the following output. :) (Spefically the "load sharing elements" line)

ROUTER A OUTPUT

IP CEF with switching (Table Version 73), flags=0x0

23 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 1

5 instant recursive resolutions, 0 used background process

1 load sharing elements, 1 references

8 in-place/0 aborted modifications

26780 bytes allocated to the FIB table data structures

universal per-destination load sharing algorithm, id BA9D2B35

1(0) CEF resets

Resolution Timer: Exponential (currently 1s, peak 1s)

Tree summary:

8-8-8-8 stride pattern

short mask protection disabled

23 leaves, 20 nodes using 23084 bytes

Table epoch: 0 (23 entries at this epoch)

ROUTER B OUTPUT

IP CEF with switching (Table Version 71), flags=0x0

22 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 1

1 instant recursive resolution, 0 used background process

2 load sharing elements, 2 references

17 in-place/0 aborted modifications

27148 bytes allocated to the FIB table data structures

tunnel per-destination load sharing algorithm, id 818781A0

1(0) CEF resets

Resolution Timer: Exponential (currently 1s, peak 1s)

Tree summary:

8-8-8-8 stride pattern

short mask protection disabled

22 leaves, 20 nodes using 23056 bytes

Table epoch: 0 (22 entries at this epoch)

Thanks in advance

purohit_810 · ‎07-10-2008

Hi,

For this specific scenario, the hash function for the load-sharing algorithm is biased toward serial 0/0. You need to "reseed" the algorithm and to get balanced traffic mix across the two links, You can see more in detail " ip cef load-sharing algorithm universal "

Thanks,

Dharmesh Purohit

merryllem · ‎07-10-2008

Thanks Dharmesh for the reply. I was able to figure out why the outputs were different. Turns out I was missing some routes in the routing table. Therefore cef did not see the "other" adjancent path to the destination. Anyways the real reason why opened a topic is because some cef load-balancing im currently having. I will open new topic for that shortly. again Thanks.