Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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:

    root@Linux server0# rpm -e jns-jdm

    For the servers running Ubuntu, run the following command:

    root@Linux server0# dpkg --remove jns-jdm
  4. To revert the MX Series router from BSYS mode to standalone mode, apply the following configuration statements on the MX Series router:
    root@router# delete chassis network-slices guest-network-functions
    root@router# commit

    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:
    root@router> request vmhost jdm stop
  3. Uninstall the JDM on each Routing Engine by running the following command.
    root@router> request vmhost jdm delete
  4. To revert the MX Series router from BSYS mode to standalone mode, apply the following configuration statements on the MX Series router:
    root@router# delete vmhost resize vjunos
    root@router# commit
  5. Reboot VM host.
    user@router> request vm host reboot (re0|re1)

    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.