Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

hw-db-profile

Syntax

Syntax (ACX7024)

Hierarchy Level

Description

Use this configuration to configure various database profiles to allocate tables with different sizes in the hardware. PFE restarts automatically once you change the configuration and commit. Profiles under this configuration support the below databases:

  • Large Exact Match (LEM)—This table stores Mac table entries, LSR entries, and IPv4 host entries
  • Longest Prefix Match (LPM)—This table stores IPv4 and IPv6 route entries

Options

lean-edge Configures lean-edge profile for Border Network Gateways (BNGs).
bng

Selects BNG DB profile and restarts PFE
carrier-ethernet

Selects carrier Ethernet high scale MAC DB profile and restarts PFE. Allocation for LPM is less and LEM is more in carrier-ethernet profile.
cloud-metro

Selects Cloud-Metro DB profile, restarts PFE
Default profile lean-edge.

Please find the change in profile naming and default as follows:

New MDB Profile Corresponding old profile
lean-edge (default) l3-xl
cloud-metro balanced (default)
carrier-ethernet l2-xl
bng balanced-exem
Note:

For features such as EVPN-VXLAN, if there is a requirement for a higher Layer 2 MAC scale, then it is recommended to migrate to “cloud-metro” profile.

ACX7024 devices support lean-edge and cloud-metro options only.

Note:

ACX7100-32C, ACX7100-48L, and ACX7509 support FIB compression by default. ACX7024 platform does not support FIB compression.

Usage scenarios for modular database (MDB) profile

Below are the recommended steps to retain an MDB profile which corresponds to the older MDB profile.

Example 1:

To retain the existing default old profile: “balanced” after upgrading to the new software image:

  • After the image upgrade to the new software the new default MDB profile is changed to “lean-edge” which corresponds to the old profile l3-xl.
    • Explicitly configure the “cloud-metro” MDB profile by executing the below command:

Example 2: To retain the corresponding MDB profile after upgrading to the newer software:

  • The older configured MDB profile, if configured on any network device, is considered and after the upgrade, the corresponding new MDB profile gets activated.
    • If you have configured old profile "balanced-exem", after the upgrade, the corresponding new MDB profile, “bng” is activated.
    • It is recommended that the user explicitly configures the new MDB profile and deletes the older configuration. Use the following commands:

Upgrade and Downgrade Scenarios

The below table summarises the expected behaviour during the upgrade and downgrade scenarios with Junos Evolved release 23.4R1.

Scenario Behaviour

Upgrade to new software when there are no explicit MDB profile configurations present then the default profile is used.

The upgrade will be successful. Default profile will be configured to "lean-edge".

Upgrade to new software when there are existing profile configurations.

MDB profiles are mapped internally with the corresponding new profile.
Downgrade/ rollback to older image from new image if new CLI is present

Downgrade to the older image displays error if new commands are present and upgrade is not completed. In order to successfully downgrade to older version, the new MDB configurations must be removed.

If there are no explicit new MDB profile configurations, downgrade to older software is successful. The system runs with the old default profile: "balanced" .
LPM distribution configuration If lpm-distribution option was configured in the older version software using set system packet-forwarding-options hw-db-profile lpm-distribution (1|2|3|4|200) command, upgrade to new software is successful, but LPM distribution configuration is not applied.

Release Information

Statement introduced in Junos OS Evolved Release 23.4R1 for ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, and ACX7908 routers.