Description

This article compares the CLI syntax of the most commonly used commands between NFX250 (nfx-2) and NFX250-NG (nfx-3) software.

Solution

Here is a table that lists the differences in CLI syntax between the nfx-2 (NFX250) software and the nfx-3 (NFX250-NG) software:

 

NFX2 software on NFX250

NextGen software on NFX250

Backplane/OVS vlans Config 
[edit host-os]
 vlans {
     <vlan-name> {
         vlan-id <vlan-id>;
     }
 }
 
[edit vmhost]
 vlans {
     <vlan-name> {
         vlan-id <vlan-id>;
     }
 }
[edit host-os]
 vlans {
     <vlan-name> {
         vlan-id-list [values];
     }
 }
 
[edit vmhost]
 vlans {
     <vlan-name> {
         vlan-id-list [values];
     }
 }
[edit host-os]
 vlans {
     <vlan-name> {
         vlan-id none;
     }
 }
 
[edit vmhost]
 vlans {
     <vlan-name> {
         vlan-id none;
     }
 }
[edit host-os]
 vlans {
     <vlan-name> {
         l3-interface <l3-interface>;
     }
 }
 
[edit vmhost]
 vlans {
     <vlan-name> {
         l3-interface <l3-interface>;
     }
 }
     
Internal liveliness subnet 
[edit host-os]
internal-ip-network <internal-ip-network>
 
[edit vmhost]
internal-ip-network <internal-ip-network>
     
Host interface config 
[edit host-os]
      interfaces {
          <interface-name> {
              unit 0 {
                  family inet {
                      address <source>;
                  }
              }
          }
      }
  }

Not Supported

Host Static Route 
[edit host-os]
      routing-options {
          static {
              route {
                  0.0.0.0/0 next-hop <next-hop>;
              }
          }
      }
  }

Not Supported

     
Analyzer 
[edit host-os]
 forwarding-options {
     analyzer <analyzer-name> {
         input {
             ingress | egress {
                 virtual-network-function <virtual-network-function> {
                     interface <interface-name>;
                 }
             }
         }
         output {
             virtual-network-function <virtual-network-function>;
             interface <interface-name>;
         }
     }
 }
 
[edit vmhost]
 forwarding-options {
     analyzer <analyzer-name> {
         input {
             ingress | egress {
                 virtual-network-function <virtual-network-function> {
                     interface <interface-name>;
                 }
             }
         }
         output {
             virtual-network-function <virtual-network-function>;
             interface <interface-name>;
         }
     }
 }
     
OVS cross connect 
[edit cross-connect]
 <cc-name> {
     physical-interface hsxe0|hsxe1
 }

Not Supported 

[edit cross-connect]
 <cc-name> {
     physical-interface hsxe0|hsxe1 {
         vlan-id <vlan-id> | none;
     }
 }

Not Supported 

[edit cross-connect]
  <cc-name> {
     virtual-network-function <vnf-name> {
         interface <interface>;
        }
 }
 
[edit vmhost]
 cross-connect {
     <cc-name> {
         virtual-network-function <vnf-name> {
             interface <interface>;
         }
     }
 }
[edit cross-connect]
  <cc-name> {
     virtual-network-function <vnf-name> {
         interface <interface>;
         vlan-id <vlan-id> | none;
     }
 }
 
[edit vmhost]
 cross-connect {
     <cc-name> {
         virtual-network-function <vnf-name> {
             interface <interface>;
             vlan-id <vlan-id> | none;
         }
     }
 }
     
Management Interfaces 
[edit interfaces]
 jmgmt0 {
       unit <interface-unit-number> {
         family inet {
             address <source>;
         }
         family inet6 {
             address <source>;
         }
     }
 }
 
[edit interfaces]
 fxp0 {
     unit <interface-unit-number> {
         family inet {
             address <source>;
 }
         family inet6 {
             address <source>;
         }
     }
 }
[edit interfaces]
 jsxe0 {
       unit <interface-unit-number> {
         family inet {
             address <source>;
         }
         family inet6 {
             address <source>;
         }
     }
 }
 
[edit interfaces]
 <interface-name> {
       unit <interface-unit-number> {
         family inet {
             address <source>;
         }
         family inet6 {
             address <source>;
         }
     }
 }
System VNF interfaces 
[edit virtual-network-functions ipsec-nm]
 interfaces heth1 | heth2 {
     description <description>;
     mapping {
         vlan {
             mode trunk | access;
             members <name>;
             native-vlan-id <native-vlan-id>;
         }
     }
 }

Not Supported 

[edit virtual-network-functions vjunos0]
 interfaces em1 {
     description <description>;
     mapping {
         vlan {
             mode trunk | access;
             members <name>;
             native-vlan-id <native-vlan-id>;
         }
     }
 }

Not Supported

     
Show Commands 
show chassis firmware
 
show system inventory firmware
show connections
 
show vmhost connections
show forwarding-options analyzer
 
show vmhost forwarding-options analyzer
show interfaces
 
show interfaces
show interfaces host-os

Not supported 

show interfaces host-os all

Not supported 

show log syslog
 
show log messages
show system core-dumps
 
show systemcore-dumps

show vmhost crash
show vlans
 
Show vlans

show vmhost vlans
show version
 
Show version

show vmhost version
     
Request commands 
request execute-command "jhost ovs-vsctl show"
 
show vmhost network nfv-back-plane
request execute-command "jhost uptime"
 
show vmhost uptime
request system reboot
 
request vmhost reboot
request system software add <package-name>
 
request vmhost software add <package-name>
request system power-off
 
request vmhost power-off
request setup jdm-auto-login <virtual-machine>

Not supported 

request genisoimage

Not supported

Modification History

  • 2021-09-29: Removed NFX150 and NFX350 from taxonomy, since the syntax list compares CLI on NFX250 between nfx-2 and nfx-3

  • 2021-09-29: Inserted show chassis firmware / show system inventory firmware to the table