Forwarding table management

1. A computer implemented method for representing a forwarding information base (FIB) in a database, comprising:

determining, by at least one processor, that a first routing prefix of a first forwarding entry in the FIB is a less specific routing prefix than a second routing prefix in a second forwarding entry in the FIB;

determining, by the at least one processor, a first next hop of the first routing prefix is equal to a second next hop of the second routing prefix;

removing, by the at least one processor, the second forwarding entry from the FIB based on the determination that the first next hop of the first routing prefix is equal to the second next hop of the second routing prefix; and

inserting, by the at least one processor, the first forwarding entry into a longest exact match (LEM) database or a longest prefix match (LPM) database based on a prefix length of the first routing prefix of the first forwarding entry.

2. The method of claim 1 , wherein the first next hop comprises a next hop address and an outgoing interface.

3. The method of claim 1 , wherein the inserting comprises inserting the first forwarding entry into the LPM database based on the prefix length of the first routing prefix of the first forwarding entry being different than 24 bits or 32 bits.

4. The method of claim 1 , wherein the inserting comprises inserting the first forwarding entry into the LEM database based on the prefix length of the first routing prefix of the first forwarding entry being 24 bits or 32 bits.

5. The method of claim 1 , wherein each of the LEM and LPM databases comprise ternary content-addressable memory (TCAM).

6. The method of claim 1 , further comprising:

generating a first sub routing prefix and a second sub routing prefix from a third routing prefix of a third forwarding entry in the FIB based on a prefix length of the third routing prefix being 23 bits.

7. The method of claim 6 , further comprising:

inserting the first sub routing prefix and the second sub routing prefix into the LEM database.

8. A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

determine that a first routing prefix of a first forwarding entry in a forwarding information base (FIB) is a less specific routing prefix than a second routing prefix in a second forwarding entry in the FIB;

determine a first next hop of the first routing prefix is equal to a second next hop of the second routing prefix;

remove the second forwarding entry from the FIB based on the determination that the first next hop of the first routing prefix is equal to the second next hop of the second routing prefix; and

insert the first forwarding entry into a database based on a prefix length of the first routing prefix of the first forwarding entry.

9. The system of claim 8 , wherein the first next hop comprises a next hop address and an outgoing interface.

10. The system of claim 8 , wherein to insert the first forwarding entry, the at least one processor is configured to insert the first forwarding entry into the database based on the prefix length of the first routing prefix of the first forwarding entry being different than 24 bits or 32 bits, wherein the database comprises a longest prefix match (LPM) database.

11. The system of claim 8 , wherein to insert the first forwarding entry, the at least one processor is configured to insert the first forwarding entry into the database based on the prefix length of the first routing prefix of the first forwarding entry being 24 bits or 32 bits, wherein the database comprises a longest exact match (LEM) database.

12. The system of claim 8 , wherein the database comprises ternary content-addressable memory (TCAM).

13. The system of claim 8 , wherein the at least one processor is further configured to generate a first sub routing prefix and a second sub routing prefix from a third routing prefix of a third forwarding entry in the FIB based on a prefix length of the third routing prefix being 23 bits.

14. The system of claim 13 , wherein the at least one processor is further configured to insert the first sub routing prefix and the second sub routing prefix into the database.

15. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

determining that a first routing prefix of a first forwarding entry in a forwarding information base (FIB) is a less specific routing prefix than a second routing prefix in a second forwarding entry in the FIB;

determining a first next hop of the first routing prefix is equal to a second next hop of the second routing prefix;

removing the second forwarding entry from the FIB based on the determination that the first next hop of the first routing prefix is equal to the second next hop of the second routing prefix; and

inserting the first forwarding entry into an exact match database based on a prefix length of the first routing prefix of the first forwarding entry being 24 bits or 32 bits.

16. The non-transitory computer-readable device of claim 15 , wherein the inserting comprises inserting a third forwarding entry into a longest prefix match (LPM) database based on a prefix length of a third routing prefix of the third forwarding entry being different than 24 bits or 32 bits.

17. The non-transitory computer-readable device of claim 15 , wherein the FIB is organized using a trie data structure.

18. The non-transitory computer-readable device of claim 16 , wherein each of the exact match and LPM databases comprise ternary content-addressable memory (TCAM).

19. The non-transitory computer-readable device of claim 15 , wherein the operations further comprise generating a first sub routing prefix and a second sub routing prefix from a third routing prefix of a third forwarding entry in the FIB based on a prefix length of the third routing prefix being 23 bits.

20. The non-transitory computer-readable device of claim 19 , wherein the operations further comprise inserting the first sub routing prefix and the second sub routing prefix into the exact match database.