Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
 

Related Documentation

 

Configuring the Unified Forwarding Table

To optimize the way your switch allocates memory for different types of addresses, you can choose a unified forwarding table profile. In addition to choosing this profile, you can also decide how you want memory allocated for longest prefix match (LPM) entries.

Configuring an Address-Storage Profile

On QFX5100 and EX4600 switches, you can control the allocation of memory available to store the following:

  • MAC addresses
  • Layer 3 host entries
  • Longest prefix match (LPM) table entries

You configure the mix that best meets your needs by choosing the appropriate profile. Table 1 lists the profiles you can choose and the maximum values for the MAC address and host table entries.

Table 1: Unified Forwarding Table Profiles

Profile NameMAC TableHost Table (unicast and multicast addresses)
 MAC AddressesIPv4 unicastIPv6 unicastIPv4 (*, G)IPv4 (S, G)IPv6 (*, G)IPv6 (S, G)

l2-profile-one

288K

16K

8K

8K

8K

4K

4K

l2-profile-two

224K

80K

40K

40K

40K

20K

20K

l2-profile-three (default)

160K

144K

72K

72K

72K

36K

36K

l3-profile

96K

208K

104K

104K

104K

52K

52K

lpm-profile*

32K

16K

8K

8K

8K

4K

4K

Note that if the host table stores the maximum number of entries for any given type, the entire table is full and is unable to accommodate any entries of any other type. For example, an IPv6 unicast address occupies twice as much memory as an IPv4 unicast address, and an IPv6 multicast address occupies four times as much memory as an IPv4 unicast address. For more information about valid combinations of table entries see Understanding the Unified Forwarding Table.

To configure the profile that you want, enter and commit the following statement:

[edit]
user@switch# set chassis forwarding-options profile-name

Note: When you configure and commit a profile, the PFE process restarts and all the data interfaces on the switch go down and come back up.

The settings for l2-profile-three are configured by default. That is, if you do not enter a set forwarding–options chassis profile-name statement, these settings are configured.

Configuring the LPM Allocation

In addition to choosing a profile, you can further optimize memory allocation for LPM table entries by configuring how many IPv6 prefixes in the range /65 through /127 you want the switch to store. The switch uses LPM entries during address lookup to match addresses to the most-specific (longest) applicable prefix. The procedures for configuring the LPM table are different depending on which version of Junos OS you are using.

Configuring the LPM Table With Junos OS 13.2X51-D10 and 13.2X52-D10

With Junos OS 13.2x51-D10 and 13.2X52-D10, the switch allocates memory for 16 IPv6 prefixes in the range /65 through /127 by default. If you want to use more than 16 IPv6 prefixes in this range, you must enter and commit the following statement:

user@switch# set chassis forwarding-options profile-name num-65-127-prefix [1-128]

Each increment adds support for 16 IPv6 prefixes between /65 and /127, for a maximum of 2048 such prefixes (16 x 128 = 2048). The system supports 16 of these prefixes by default, so to increase the number of supported prefixes, you must enter a value of 2 or greater. For example, if you enter 2, the system will support 32 IPv6 prefixes in the range /65 through /127.

Note: When you configure and commit the num-65-127-prefix value, all the data interfaces on the switch restart. The management interfaces are unaffected.

The LPM table is shared, and each increment that you add for IPv6 prefixes in the range /65 through /127 reduces the number of table entries that are available for IPv4 prefixes and IPv6 prefixes shorter than /65. Note that IPv6 prefixes /65 and longer consume twice as much memory as shorter IPv6 prefixes and four times as much memory as IPv4 prefixes. So, for example, entering the following statement

user@switch# set chassis forwarding-options l2-profile-one num-65-127-prefix 2

provides for 16 additional IPv6 prefixes /65 or longer (for a total of 32 such prefixes) and reduces the numbers of other prefixes that can be stored, as indicated:

  • 32 fewer IPv6 prefixes shorter than /65 (16 IPv6 prefixes /65 or longer consume the same amount of memory as 32 IPv6 prefixes shorter than /65), or
  • 64 fewer IPv4 prefixes (16 IPv6 prefixes /65 or longer consume the same amount of memory as 64 IPv4 prefixes)

Table 2 provides examples of valid combinations that the LPM table can store using the l2 and l3 profiles. Once again, each row in the table represents a case in which the table is full and cannot accommodate any more entries.

Table 2: Example LPM Table Combinations Using l2-and l3 Profiles With Junos OS 13.2X51-D10 and 13.2X52-D10

num-65-127-prefix ValueIPv4 EntriesIPv6 Entries (Prefix <= 64)IPv6 Entries (Prefix >= 65)

1 (default)

16K-16

0K

16

1 (default)

0K

8K-16

16

1 (default)

8K-16

4K

16

64

4K

4K

1K

64

2K

5K

1K

64

0K

6K

1K

128

4K

2K

2K

128

2K

3K

2K

128

0K

4K

2K

Note: With Junos OS 13.2X51-D10 and 13.2X52-D10, the lpm-profile does not support IPv6 prefixes. If you use this version of Junos OS and also use the lpm-profile, do not configure the num-65-127-prefix statement. That is, leave it at its default value of 1, which allows for as many as 128K IPv4 prefixes (the maximum possible).

Configuring the LPM Table With Junos OS 13.2x51-D15

With Junos OS 13.2X51-D15, you can configure the memory allocation for the LPM table for the lpm-profile profile independently of the other profiles. In addition, Junos OS 13.2x51-D15 offers twice as much storage for IPv6 prefixes /65 through /127 (4K instead of 2K) for the l2 and l3 profiles.

Configuring the l2 and l3 profiles With Junos OS 13.2x51-D15

With Junos OS 13.2x51-D15, you can configure the switch to support as many as 4K IPv6 prefixes /65 through /127 if you are using any profile other than the lpm-profile profile. To do so, enter and commit the following statement:

user@switch# set chassis forwarding-options profile-name num-65-127-prefix [0-4]

Each increment adds support for 1K IPv6 prefixes between /65 and /127, for a maximum of 4K such prefixes. The default value is 1, which allocates memory for 1K of IPv6 prefixes in this range. Each increment that you add for IPv6 prefixes in the range /65 through /127 reduces the number of table entries that are available for IPv6 prefixes shorter than /65 and IPv4 prefixes. Table 3 shows the numbers of entries that you can allocate by using the num-65-127-prefix statement with Junos OS 13.2X51-D15. Once again, each row represents a case in which the table is full and cannot accommodate any more entries.

Table 3: LPM Table Combinations for l2 andl3 profiles With Junos OS 13.2X51-D15

num-65-127-prefix ValueIPv4 EntriesIPv6 Entries (Prefix <= 64)IPv6 Entries (Prefix >= 65)

0

16K

8K

0K

1 (default)

12K

6K

1K

2

8K

4K

2K

3

4K

2K

3K

4

0K

0K

4K

Note: When you configure the num-65-127-prefix value, the PFE process restarts and all the data interfaces on the switch go down and come back up. The management interfaces are unaffected.

Configuring The lpm-profile With Junos OS 13.2x51-D15

If you use the lpm-profile profile with Junos OS 13.2x51-D15, you can control whether the switch allocates any memory for IPv6 prefixes /65 through /127. By default, the switch supports the following with this profile:

  • 128K IPv4 prefixes
  • 16K IPv6 prefixes (all lengths)

You can disable support for IPv6 prefixes /65 through /127 with the lpm-profile profile so that there is more memory for IPv6 prefixes shorter than /65. To do so, enter and commit the following statement:

user@switch# set chassis forwarding-options profile-name prefix-65-127-disable

If you enter this statement, the switch allocates memory for the following:

  • 128K IPv4 and IPv6 prefixes shorter than /65
  • 0K IPv6 prefixes /65 through /127

For example, if you use the prefix-65-127-disable statement, each of the following combinations are valid:

  • 100K IPv4 and 28K IPv6 /64 prefixes
  • 64K IPv4 and 64K IPv6 /64 prefixes
  • 128K IPv4 and 0K IPv6 /64 prefixes
  • 0K IPv4 and 128K IPv6 /64 prefixes
 

Related Documentation

 

Published: 2014-07-23

Supported Platforms

 

Related Documentation

 

Published: 2014-07-23