forwarding-options (Unified Forwarding Table Profile)
Syntax
forwarding-options {
custom-profile {
exact-match-entries {
num-banks num-banks;
}
l2-entries {
num-banks num-banks;
}
l3-entries {
num-banks num-banks;
}
lpm-entries {
num-banks(0 | 2 | 4);
prefix-65-127-disable;
}
num-65-127-prefix num-65-127-prefix;
}
l2-profile-one {
num-65-127-prefix num-65-127-prefix;
}
l2-profile-three {
num-65-127-prefix num-65-127-prefix;
}
l2-profile-two {
num-65-127-prefix num-65-127-prefix;
}
l3-profile {
num-65-127-prefix num-65-127-prefix;
}
lpm-profile {
prefix-65-127-disable;
unicast-in-lpm;
}
vxlan-gbp-l2-profile;
vxlan-gbp-l3-profile;
vxlan-gbp-profile;
}Hierarchy Level
[edit chassis]
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.
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
| custom-profile |
On QFX5200 Series switches only, you can select
The the 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 |
( |
| num-banks number |
(
|
| profile-name |
Configure one of the following profiles to allocate memory:
Review Understanding the Unified Forwarding
Table to understand the memory allocation for your platform.
You can also use the user@host# set chassis forwarding-options ? Possible completions: + apply-groups Groups from which to inherit configuration data + apply-groups-except Don't inherit configuration data from these groups > l2-profile-one MAC: 288K L3-host: 16K LPM: 16K EM:0, needs reboot for VC; restarts PFE if standalone > l2-profile-three (default) MAC: 160K L3-host: 144K LPM: 16K, needs reboot for VC;restarts PFE if standalone > l2-profile-two MAC: 224K L3-host: 80K LPM: 16K EM:0, needs reboot for VC; restarts PFE if standalone > l3-profile MAC: 96K L3-host: 208K LPM: 16K EM:0, needs reboot for VC; restarts PFE if standalone > lpm-profile MAC: 32K L3-host: 16K LPM: 128K EM:0, needs reboot for VC; restarts PFE if standalone Requires reboot of the Virtual Chassis for profile change to take effect.
For standalone deployments, committing the profile configuration
restarts the PFE. You can use the user@host> show chassis forwarding-options localre: -------------------------------------------------------------------------- UFT Configuration: lpm-profile prefix-65-127 = enable --------------Bank details for various types of entries------------------ Entry type Dedicated Bank Size(K) Shared Bank Size(K) L2(mac) 32 32 * num shared banks L3(unicast & multicast) 16 32 * num shared banks Exact Match 0 16 * num shared banks Configure VXLAN GBP profiles and GBP policy filters with L4 matches on EX4400, EX4100, EX4650, and QFX5120 switches:
Review Micro and Macro Segmentation using Group Based Policy in a VXLAN for more details. You can also use the user@host# set chassis forwarding-options ? Possible completions: + apply-groups Groups from which to inherit configuration data + apply-groups-except Don't inherit configuration data from these groups > vxlan-gbp-l2-profile MAC: 160K L3-host: 48K LPM(IPv4): 32K EM: 48K.(restarts PFE if standalone system and requires reboot for VC systems) > vxlan-gbp-l3-profile MAC: 96K L3-host: 144K LPM(IPv4): 32K EM: 32K.(restarts PFE if standalone system and requires reboot for VC systems) > vxlan-gbp-profile MAC: 160K L3-host: 80K LPM(IPv4): 32K EM: 32K.(restarts PFE if standalone system and requires reboot for VC systems) |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.
custom-profile option introduced in Junos OS Release 15.1x53-D30 for
QFX5200 Series switches only.
VXLAN GBP profile options introduced in Junos OS Release 23.2R1 for EX4100, EX4400, EX4600, QFX5120-32C and QFX5120-48Y switches only.