Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configure NextGen Port Extender

Manual Configuration Process

SD Preparation

Use this manual process to create an NGPE network environment. Satellite devices participating in NGPE must have the Junos factory default configuration, or must be zeroized before satellite onboarding. You must have root access to all devices. All interfaces intended for NGPE must be cabled. We strongly recommend that you have console access to all devices during the initial setup process.

Note: QFX platforms may retain some LLDP configuration after a zerioze procedure. In this scenario, it is recommended that you delete the entire configuration and then set only the root password before continuing with the NGPE configuration process.
  1. You'll need to generate and capture the SSH key from each SD. This key is used by the AD to communicate with the SD. Each SD will have a unique SSH key.
    This sets the device as a satellite node and also generates its unique SSH key.
  2. You will need to copy the SSH key and apply it to the AD configuration in a later step. Use this command to display the key. Ensure you copy the entire key output.

Configure the AD

AD Step by Step Configuration

Follow these steps to create the baseline configuration required to initialize the NGPE topology with AD and SD connectivity.

  1. Configure the required parameters on the AD, under the port-extender stanza.
    Configure the management loopback address used by the AD. This loopback is for management traffic only and is a required parameter. We don't recommend changing this address after the initial configuration.
  2. Configure the data loopback address used by the AD. This is a required parameter and must be different from the management loopback. We don't recommend changing this address after the initial configuration.
    This address is for data traffic only.
  3. Enable the EVPN-VXLAN fabric.
  4. Define the satellite model for this SD instance. You can use any name you prefer for <satellite-name>.
  5. Add the interfaces which will become the cascade and uplink ports.
    Note the interfaces are differentiated in this example by the "ad" or "sd" identifier. This example includes 4 interfaces per device. You may configure between 1 and 4 interfaces, although we recommend at least 2 per device. Configure the necessary number of interfaces for your deployment.
  6. Add the SSH key generated during step 2 of SD Preparation.
  7. Enable the commit scripts used for auto-configuration.
    The full path for the ngpe_commit.py file is /var/db/scripts/commit/ngpe_commit.py, however it isn't needed since NGPE looks for the script only in that location.
  8. Commit the configuration from the AD.
    You can use "commit" if your device has a single routing engine.

Apply the SD Minimal Configuration

SD Minimal Configuration

You automatically generated a minimal configuration file during the NGPE initialization process. Now you can apply it to the target satellite device.

  1. You'll need to view and copy the configuration in this file, then apply it on the SD.
  2. Add the minimal configuration to the SD.
  3. Monitor the SD configuration progress from the console. You can use the "tail" command from the SDs console to view the jnud log.

Configure Additional Satellite Devices

Onboard Additional SDs

The process to onboard additional SDs is outlined in this section. These steps do not apply to the first SD configured within your NGPE topology.

  1. Configure the device as a satellite.

  2. Capture the SSH key output.

  3. Define the satellite model on the AD.

  4. Configure the cascade and uplink ports between the AD and the additional SD.

  5. Add the SSH key captured in step 2. Ensure the SSH key is surrounded by quotation marks.

  6. Commit the configuration.

  7. Follow the steps in Apply the SD Minimal Configuration to complete this process.

Verification

Verify the NGPE Configuration

Once the commit script has been started, the full configuration process may take up to 180 seconds to complete. You may seem some warnings about required licenses, and you can disregard those warnings.

Use the following commands to check the state of the NGPE deployment.

  • show chassis jnu role: displays whether a device is a controller or satellite.

  • show chassis jnu satellites: displays the status of a single satellite or all satellites.

  • show chassis port-extender: displays each virtual SD slot number, along with its IP address, MAC address, and cascade port number.

  • show interfaces terse: displays the up/down status of interfaces; useful for confirming the NGPE fabric is up.

  • show lacp interfaces: check the status of aex participating in LACP

  • show interfaces vtep: check the status of VTEP interfaces.

  • show l2-learning vxlan-tunnel-endpoint remote: check the status of remote VTEP interfaces

  • show bfd session device-list [satellite-name(s)]: check the status of BFD sessions

  • request jnu satellite sync: needed if the SD failed to initially sync, meaning the SD is configured and working, yet it isn't associated with the AD.

  • show configuration | display set: displays the active configuration on the device

  • show log jnud: use this command to either monitor the progress of a satellite onboarding, or use after onboarding to check for any errors.

Extended Port Speeds

Change the Speed of an Extended Port

You can change the speed of an EP port in one of two ways:

  • Use the default-speed setting at the edit services port-extender satellite <satellite-name> hierarchy.

  • Use the speed option at the edit services port-extender satellite <sat-name> hierarchy. This option allows multiple ports to be configured at once.

Saving the Configuration

Save User-Generated Configuration

Follow this process to save only the user-generated configuration. None of the NGPE generated configuration will be present in this save operation. This process should be performed when NGPE is in a maintenance window since the process requires disabling the NGPE fabric. We don't support loading configurations with NGPE elements into an active NGPE environment since this can have unexpected effects.

  1. Disable the NGPE fabric.

  2. Save the configuration.

  3. Restore the NGPE fabric.

Reload Existing Saved NGPE Configuration

As previously stated, we don't support loading an NGPE configuration onto an active NGPE environment. You may however load a saved NGPE configuration to a non-NGPE device which will act as the AD. The target AD must have either a baseline Junos configuration, or you must zeroize the device prior to following this process. Ensure that all necessary cabling has been completed in advance, and that any intended SDs are also running a base configuration. Please ensure you have console access to the intended AD.

  1. Load the saved configuration.

  2. Once the configuration has been loaded and committed, you'll need to activate the port-extender stanza.

  3. Enable an SD.

  4. Synchronize the satellite.

  5. Repeat steps 3 and 4 for each SD.