1 of 13

Getting Started

This section provides information about how to install/upgrade the OPBNOS and information on the SONiC shell.

Licensing

Aviz OPB NOS supports 3 license types listed below

License

Features

Platforms

Basic

Layer 3/4 (IPv4 and IPv6) Filtering
Layer 2 (VLAN and Ethertype) Filtering
VLAN Actions (Ingress and Egress)
Redirection (Ports, Static LAG)
Hybrid Port for multiple lookups
Port and Flow Statistics Management: NTP, SSH, Timezone, SYSLOG, LLDP, TACACS+, ZTP, SNMPv1/v2 Get, Traps, ISCLI, REST API (HTTPs - selfsigned), sFlow, RADIUS
OPB Fabric Manager (FlowVision) Appliance

Broadcom (TD3, TD2X, TH)

EC5812, EC7712, EC7726, EC7816, EC7326, Celestica DS2000

DELL

S5248F-ON, S5232F-ON

Nvidia (Spectrum 1,2,3)

SN2010, SN2100, SN2201, SN2700, SN3420, SN3700, SN3800, SN4600C, SN4700

Advanced - DataCenter

(Includes Basic)

VXLAN Encap and Decap*
Generic Header Filtering (MPLS, L2GRE, VXLAN, IP-n-IP)*
User-Defined Offset Filtering*
Match-Expression Filtering*
VxLAN Stripping
Truncation

Nvidia (Spectrum 2,3)

SN3420, SN3700, SN3800, SN4600C, SN4700

Advanced - Telco

(Includes

Advanced DC)

GTP Parsing
Symmetric Load balancing based on Inner IP(v4/v6) header
GTP Filtering - Inner IP header, Tunnel IDs
GTP extension header support of type 0x85

Nvidia (Spectrum 2,3)

SN3420, SN3700, SN3800, SN4600C, SN4700

Trial (30 days)

All features (Basic, Advanced-DC, Advanced-5G)

All

*Features unique to Aviz OPB NOS

Limitations

ASIC Limitations:

Multiple flows can not have the same network port
In VLAN-aware mode, VLAN is a mandatory match qualifier for the flow rule for matching tagged packets
Pop-VLAN is supported on flow rules which have VAN id as a qualifier
Flow rule VLAN qualifier is not supported in VLAN-Unaware mode
For VxLAN, NVIDIA supports only one source VTEP per system but supports multiple destination VTEP
For VxLAN, multiple VNI cannot be mapped to the same Destination VTEP
GTP, UDF and Generic Header Filtering configurations and rules are not supported for the NVIDIA SN2100 switch
Ingress-VLAN is not supported on EC-AS7326 and EC-AS7726 platforms

Software Limitations:

Port-Channel can not be configured as a network port
A Maximum of 4 active SSH sessions are supported
Tunnel attributes cannot be updated and will require deleting the existing tunnel and reconfiguring
Override qualifiers are not supported for the VxLAN feature
GTP rule configuration is to be done using a string (i.e. double quotes)
GTP global configuration must be enabled before configuring the GTP rule
A proper license is required before configuring a feature
System reboot is required after port breakout configuration.
Before doing port breakout, make sure interface doesn't have any dependent configuration, best practice is to do port breakout with clean configuration.

SSH connection should be disconnected gracefully using the “quit” command once the usage is completed

Image Management

The switch image is the executable code running on the device. Aviz OPBNOS can be upgraded to the device

ONIE to OPBNOS
OPBNOS to OPBNOS

The typical upgrade process for the image consists of the following steps:

Load a new firmware image and boot image onto an SFTP, HTTP, SCP, or TFTP server on your network.
Transfer the new images to the switch
Specify the new image as the one to be loaded the next time a switch reload occurs
Reload the switch

Installing OPBNOS from ONIE

To install OPBNOS from ONIE, please follow the below steps:

Login using the console port and reboot the switch
Enter ONIE mode

Select 'ONIE: Uninstall OS' to clean up installed images

This step takes a few minutes and reboot the switch after cleanup is complete

The Switch will reboot and boot into 'ONIE: Install OS' mode, run the below command to stop auto-discovery

ONIE:/ # onie-discovery-stop

The 'onie-discovery-stop' command is deprecated and will be removed in 2019.02.

If you are using the latest version of ONIE, Use 'onie-stop' instead.

Assign 'eth0' with a management-IP to copy image from remote server

ONIE:/ # ifconfig eth0 <mgmt-ip> netmask <netmask> up
//Example - ifconfig eth0 10.4.4.72 netmask 255.255.254.0 up

If server is present on different network using below command to add a default route

ONIE:/ # route add default gw <gw-ip>
//Example - route add default gw 10.4.4.1

Image can be installed using HTTP or SCP:
- SCP -

//Copy image - 
ONIE:/ # scp <user>@<server-ip>:/<dir>/opb-nos.bin opbnos.bin
//Example - scp aviz@10.2.2.10:/images/opb/opb-nos.bin opbnos.bin 

//Install copied image -
ONIE:/ # onie-nos-install <image-name.bin>
//Example - onie-nos-install opbnos.bin

HTTP -
- start HTTP-server on image directory, on a linux server below command can be used to achieve this

aviz@10.2.2.10:/images/opb$ python3 -m http.server 8030

On the switch console use the below command to install the image using HTTP, This will download and install the OPBNOS

ONIE:/ # onie-nos-install http://<IP>:<port>/<opb-nos.bin>
//Example - onie-nos-install http://10.2.2.10:8030/opb-nos-20220714.2.1.1.bin

Installing OPBNOS from USB Drive

To install OPBNOS from USB Drive, Please follow the below steps:

Login using the console port and reboot the switch
Enter ONIE mode

Select 'ONIE: Uninstall OS' to clean up installed images

The Switch will reboot and boot into 'ONIE: Install OS' mode, run the below command to stop auto-discovery

ONIE:/ # onie-discovery-stop

Enter the following command to create a USB mount location on the system

ONIE:/ # mkdir /mnt/media

Enter the following command to mount the USB. The vfat option is used for FAT32 formatted drives

ONIE:/ # mount -t vfat /mnt/media
Example - ONIE:/ # mount -t vfat /dev/sdb1 /mnt/media

Install the software from the USB drive, where /mnt/media specifies the path where the USB partition is mounted

ONIE:/ # onie-nos-install /mnt/media/opbnos.bin

Image Upgrade from OPBNOS

To upgrade image to a newer version from OPBNOS CLI, use the following command:

CLI Example:

pbnoscli# copy scp avizuser@10.2.2.10:/mnt/ws/images/opbnos/R2.8.0/nvidia/opb-nos-mellanox-20250215.2.8.0.bin opbnos-image
The authenticity of host '10.2.2.10 (10.2.2.10)' can't be established.
ECDSA key fingerprint is SHA256:+S2EmXkMAA6WYu6VKodKZtsha3HpVzLCnpG95yEqqlQ.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '10.2.2.10' (ECDSA) to the list of known hosts.
avizuser@10.2.2.10's password:
opb-nos-mellanox-20250215.2.8.0.bin                                                         100% 1467MB 109.8MB/s   00:13
New image will be installed, continue? [y/N]: y

//After installation is complete, perform a reboot
pbnoscli# reboot

To verify, Please run below command:

pbnoscli# show boot
Current: OPBNOS-master.0-dirty-20250213.013329
Next: OPBNOS-master.0-dirty-20250213.013329
Available:
OPBNOS-master.0-dirty-20250213.013329
OPBNOS-master.0-dirty-20250209.063638


pbnoscli# show version

Aviz OPB NOS Version: 2.8.0
Distribution: Debian 11.11
Kernel: 5.10.0-18-2-amd64

Platform: x86_64-mlnx_msn4600c-r0
HwSKU: ACS-MSN4600C
ASIC: mellanox
ASIC Count: 1
Serial Number: MT2040X05753
Model Number: MSN4600-CS2FC
Hardware Revision: A1
Uptime: 11:36:28 up 17:35,  3 users,  load average: 1.09, 1.03, 1.02
Date: Wed 19 Feb 2025 11:36:28

Docker images:
REPOSITORY                TAG                              IMAGE ID       SIZE
docker-syncd-mlnx         latest                           c530e940d41c   898MB
docker-syncd-mlnx         master.0-dirty-20250207.160956   c530e940d41c   898MB
docker-snmp               latest                           27018d6fc1c5   408MB
docker-snmp               master.0-dirty-20250207.160956   27018d6fc1c5   408MB
docker-platform-monitor   latest                           b48d9e8798f6   881MB
docker-platform-monitor   master.0-dirty-20250207.160956   b48d9e8798f6   881MB
docker-orchagent          latest                           83e221477668   396MB
docker-orchagent          master.0-dirty-20250207.160956   83e221477668   396MB
docker-lldp               latest                           b8dda16e3032   403MB
docker-lldp               master.0-dirty-20250207.160956   b8dda16e3032   403MB
docker-eventd             latest                           cfc31e8b5c59   361MB
docker-eventd             master.0-dirty-20250207.160956   cfc31e8b5c59   361MB
docker-database           latest                           7099928b9e6f   361MB
docker-database           master.0-dirty-20250207.160956   7099928b9e6f   361MB
docker-sflow              latest                           8f7d4b72342d   361MB
docker-sflow              master.0-dirty-20250207.160956   8f7d4b72342d   361MB
docker-nagr               latest                           2d4c3653029e   804MB
docker-nagr               master.0-dirty-20250207.160956   2d4c3653029e   804MB
fv                        latest                           a55f748c07a0   173MB

Selecting OPBNOS on next boot

To specify OPBNOS image on next reboot, use the following command:

Reference

Comment

List the available images using the following command:

pbnoscli# show boot

CLI Example

pbnoscli# show boot
Current: OPBNOS-master.0-dirty-20250213.013329
Next: OPBNOS-master.0-dirty-20250213.013329
Available:
OPBNOS-master.0-dirty-20250213.013329
OPBNOS-master.0-dirty-20250209.063638

Select image to boot on next reboot using below command:

pbnoscli# nextboot-image OPBNOS-master.0-dirty-20250209.063638

Removing available images

You can remove unused or old images from the device to optimize disk utilization using the "cleanup-images" and "remove-image" commands.

Reference

Command

remove-image < image_name>

Description

Remove specific image from the switch

Parameters

ImageName - Can be obtained from "show

boot"

Mode

EXEC

CLI Example

pbnoscli# remove-image <image-name>
//Example - remove-image SONiC-OS-2.1.1_RELEASE.0-dirty-20220718.065117

Reference

Command

cleanup-images

Description

Remove all available images from the switch

Parameters

ImageName - Can be obtained from "

Mode

EXEC

pbnoscli#cleanup-images

Rebooting the Switch

You can reload/reboot the switch using the below command:

pbnoscli# save   
  save                  Copy Running configuration to Startup configuration
pbnoscli# save 
Saving Configuration

pbnoscli# reboot 
Check if running config is saved
Do you want to reboot the device [y/n]: y