Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

forwarding-options

 

Syntax

Chassis: EX4600 and QFX Series

Chassis: EX4600 and QFX Series

Chassis: EX4600 and QFX Series

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Hierarchy level [edit vlans vlan-name] introduced in Junos OS Release 13.2X50-D10 for EX Series switches.

Hierarchy level [edit bridge-domains bridge-domain-name] introduced in Junos OS Release 14.1 for MX Series routers.

custom-profile option introduced in Junos OS Release 15.1x53-D30 for QFX5200 Series switches only.

Description

Configure a unified forwarding table profile to allocate the amount of memory available for the following:

  • MAC addresses.

  • Layer 3 host entries.

  • Longest prefix match table entries.

This feature enables you to select a profile that optimizes the amount of memory available for various types of forwarding-table entries based on the needs of your network. For example, for a switch that handles a great deal of Layer 2 traffic, such as a virtualized network with many servers and virtualized machines, you would choose the l2-profile-one, which allocates the highest amount of memory to MAC addresses.

You configure the memory allocation for LPM table entries differently, depending on whether you using Junos OS Release 13.2X51-D10 or Junos OS Release 13.2X51-D15 and later. For more information about configuring memory allocation for LPM table entries, see Configuring the Unified Forwarding Table on Switches.

The num-65-127-prefix number statement is not supported on the custom-profile and the lpm-profile. The prefix-65-127-disable and unicast-in-lpm statements are supported only on the lpm-profile.

When you commit a configuration with a forwarding table profile change, in most cases the Packet Forwarding Engine restarts automatically to apply the new parameters, which brings the data interfaces down and then up again.

However, starting with Junos OS Releases 14.1X53-D40, 15.1R5, and 16.1R3, for a Virtual Chassis or Virtual Chassis Fabric (VCF) comprised of EX4600 or QFX5100 switches, the Packet Forwarding Engine in member switches does not automatically restart upon configuring and committing a unified forwarding table profile change. This behavior avoids having Virtual Chassis or VCF instability and a prolonged convergence period if a profile change is propagated to member switches and multiple Packet Forwarding Engines all restart at the same time. In this environment, instead of automatically restarting when you initially commit a profile configuration change, the message Reboot required for configuration to take effect is displayed at the primary switch CLI prompt, notifying you that the profile change does not take effect until the next time you restart the Virtual Chassis or VCF. The profile configuration change is propagated to member switches that support this feature, and a reminder that a reboot is required to apply this pending configuration change appears in the system log of the primary switch and applicable member switches. You then enable the profile change subsequently during a planned downtime period using the request system reboot command, which quickly establishes a stable Virtual Chassis or VCF with the new configuration.

Note

You should plan to make unified forwarding table profile changes only when you are ready to perform a Virtual Chassis or VCF system reboot immediately after committing the configuration update. Otherwise, in the intervening period between committing the configuration change and rebooting the Virtual Chassis or VCF, the system can become inconsistent if a member experiences a problem and restarts. In that case, the new configuration takes effect on the member that was restarted, while the change is not yet activated on all the other members.

The remaining statements are explained separately. See CLI Explorer.

Options

profile-namename of the profile to use for memory allocation in the unified forwarding table. Table 1 lists the profiles you can choose that have set values and the associated values for each type of entry.

On QFX5200 Series switches only, you can also select custom-profile. This profile enables you to allocate from one to four banks of shared hash memory to a specific type of forwarding-table entry. Each shared hash memory bank can store a maximum of the equivalent of 32,000 IPv4 unicast addresses.

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

* This profile supports only IPv4 in Junos OS Release13.2X51-D10. Starting in Junos OS Relase13.2X51-D15, the lpm-profile supports IPv4 and IPv6 entries.

Note

If the host 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 information about valid combinations of table entries see Understanding the Unified Forwarding Table.

l2-entries | l3-entries | lpm-entries(custom-profile only) Select a type of forwarding-table entry—Layer 2, Layer 3, or LPM—to allocate a specific number of shared memory banks. You configure the amount of memory to allocate for each type of entry separately.
num-banks number(custom-profile only) Specify the number of shared memory banks to allocate for a specific type of forwarding-table entry. Each shared memory bank stores the equivalent of 32,000 IPv4 unicast addresses.

Range: 0 through 4.

Note

There are four shared memory banks, which can be allocated flexibly among the three types of forwarding-table entries. To allocate no shared memory for a particular entry type, specify the number 0. When you commit the configuration, the system issues a commit check to ensure that you have not configured more than four memory banks. You do not have to configure all four shared memory banks. By default, each entry type is allocated the equivalent of 32,000 IPv4 unicast addresses in shared memory.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.