Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Managing Junos Node Slicing

Deleting Guest Network Functions

This procedure involves shutting down a GNF and then deleting it. In JDM, GNF VMs are called VNFs. Use the following steps to delete a VNF:

  1. Shut down a VNF by using the JDM CLI command request virtual-network-functions gnf-name stop all-servers. For example:

    root@test-jdm-server0> request virtual-network-functions test-gnf stop all-servers

  2. Delete the VNF configuration by applying the JDM CLI configuration statement delete virtual-network-functions gnf-name. See the following example:

    root@test-jdm-server0# delete virtual-network-functions test-gnf

    root@test-jdm-server0# commit synchronize

  3. Delete the VNF image repository by using the JDM CLI command request virtual-network-functions gnf-name delete-image all-servers. For example:

    root@test-jdm-server0> request virtual-network-functions test-gnf delete-image all-servers

    Note:

    • To delete a VNF completely, you must perform all the three steps.

    • If you want to delete a VNF management interface, you must stop and delete the VNF first.

Disabling Junos Node Slicing

To disable Junos node slicing, you must uninstall the following packages:

  • JDM package

  • Junos OS image for GNFs

Note:

Save the JDM configuration if you want to use it for reference.

Use the following steps to disable Junos node slicing (external server model):

  1. Delete the GNFs first by performing all the steps described in the section Deleting Guest Network Functions.
  2. Stop the JDM on each server by running the following command at the host Linux shell:

    root@Linux server0# jdm stop

    Stopping jdm: Domain jdm destroyed

  3. Uninstall the JDM on each server by running the following command at the host Linux shell.

    For the servers running RHEL, run the following command:

    For the servers running Ubuntu, run the following command:

  4. To revert the MX Series router from BSYS mode to standalone mode, apply the following configuration statements on the MX Series router:

    The router now operates in standalone mode.

To disable in-chassis Junos node slicing, you must:

  • Shut down and delete all GNFs. Also, delete the Junos OS image associated with the GNF.

  • Shut down JDM and then delete the JDM software package.

  • Delete the in-chassis BSYS mode configuration (set vmhost resize vjunos).

  • Reboot the Routing Engine.

Use the following steps to disable in-chassis Junos node slicing:

  1. Delete the GNFs first by performing all the steps described in the section Deleting Guest Network Functions.

  2. Stop the JDM on each Routing Engine by running the following command:

  3. Uninstall the JDM on each Routing Engine by running the following command.

  4. To revert the MX Series router from BSYS mode to standalone mode, apply the following configuration statements on the MX Series router:

  5. Reboot VM host.

    The router now operates in standalone mode.

    Note:

    All files in the /var/ location, including the log files (/var/log) and core files (/var/crash), are deleted when you reboot VM host after deleting the vmhost resize vjunos compact configuration. You must save any files currently in /var/log or /var/crash before deleting the vmhost resize vjunos compact configuration if you want to use them for reference.

Managing Sub Line Cards

For an overview of sub-linecards, see Sub Line Card Overview.

For configuring sub-linecards, please refer to Configuring Sub Line Cards and Assigning Them to GNFs.

To manage the sub line cards, you can use the same CLI operational commands that are used to manage full line cards.

You can operate on SLCs from both BSYS as well as their associated GNFs.

From the BSYS, you can see the status of all SLCs on all FPCs, and take actions on any SLC.

From a GNF, you can see the status of, and take actions on, only those SLCs that are assigned to that GNF.

When you run a show command at the BSYS for a sliced line card, the output shows values from BLC and all SLCs of that line card. The annotation fpc-slot:slc-id is used to indicate that an output field is from a sub line card. When the same show command is run at a GNF for that line card, the output shows the value only from the specific slice that has been assigned to that GNF.

When you need to take action on an SLC from the BSYS, you must use the new keyword slc, together with an SLC ID, to indicate the specific SLC of a specific FPC. When you need to take action on the SLC from its associated GNF, you only need to specify the FPC slot (the SLC ID is implicit).

Operational Commands on BSYS for Line Card Slices

The following are the sample command outputs on the BSYS, where FPC 1 has been sliced.

To view the status of a sliced line card at the BSYS, use the CLI command show chassis fpc, as shown below. The slot entries 1:1 and 1:2 indicate the outputs from SLC1 and SLC2 respectively. The slot entry ‘1’ indicates the output of the BLC.

The status of each SLC of a Line card is displayed using the fpc-slot-id:slc-id nomenclature as below along with the GNF assignment details:

To examine the operational values of the line card resources of a sliced line card, use the CLI command show chassis fpc pic-status. These operational values match the configured values of the line card resources.

To view the software version, uptime and the individual Packet Forwarding Engine assignments of the SLCs, use the CLI command show chassis fpc slot detail, as shown below.

To view the node-level assignments of line cards and sub line cards to different GNFs, use the CLI command show chassis network-slices fpcs at the BSYS, as shown below. In this example, GNF 1 has 2 line card slices, SLC1 of FPC1 and SLC1 of FPC9, and no full line cards. GNF 2 here has one full line card, FPC6, and 2 line card slices, SLC2 of FPC1 and SLC2 of FPC9.

You can take a sub line card offline, bring it online or restart it in the same way as you would with full line cards. You must use the additional keyword slc and an SLC ID to indicate the specific SLC. For example, to restart SLC1 of FPC1, use the CLI command request chassis fpc slot 1 slc 1.

On the BSYS, when you take a sliced FPC offline, and do not specify any SLC, the command is applied to all SLCs of that FPC, that is, all the SLCs will first be taken offline, followed by the FPC itself. Similarly, when you bring a sliced FPC online, the FPC will be first brought online, followed by all the SLCs.

Operational Commands on GNF for Line Card Slices

The operational commands used on a GNF are identical to those that are used on full line cards. When you specify an fpc-slot, which has a sliced FPC, the command implicitly operates only on the specific SLC of that FPC that has been assigned to that GNF, that is, the SLC ID is implied.

In the example below, the CLI command show chassis fpc 1 is entered on GNF A; so, it shows the status of only one SLC, SLC1, since that is the SLC of FPC1 associated with GNF A. It also shows the BLC status of that FPC. Note that this output does not show the status of SLC2 of FPC1, since SLC2 is associated with a different GNF (GNF B).

In the example below, the same CLI command show chassis fpc 1 is entered on GNF B; so, it shows only SLC2, which is the SLC of FPC1 associated with GNF B. It also shows the BLC status of that FPC. Note that this output does not show the status of SLC1 of FPC1, since SLC1 is associated with a different GNF (GNF A).

As another example, the following is the output of the CLI command show chassis fpc 5 detail from GNF A. Note that it shows only SLC1 information.

To take offline, bring online or restart an SLC from its associated GNF, specify only its FPC slot, as shown in the following example (the SLC ID is implied).

For a sample sub linecard configuration, please refer to Sample Configuration for Sub Line Cards.

Related Documentation