210 WBX Software Installation Guide

210 WBX Software Installation Guide
Release 5.1.2
3HE13484AAAB
November 01, 2017

CONTENTS
1 About this Document 2

1.1 Validity of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Overview 4
2.1 210 WBX Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1 210 WBX 32QSFP28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.2 210 WBX 48SFP28 6QSFP28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Nuage Software Installation 7

3.1 Setting Up NOS with ONIE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Initializing the System and Downloading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.2 Installing NOS From the SD Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.3 Installing NOS From the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Boot After the NOS Installation is Complete . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3 Automatic NOS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.3.1 Configuring OS From the SD Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.3.2 Configuring OS From the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.3.3 Cloud-init File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
nuage_wbx cloud-init Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.4 Example of SD Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
cloud-init.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3.5 Example of DHCP + HTTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . 13
3.4 Reinstalling OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.5 Uninstalling OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Getting Started with the Nuage 210 WBX 16

4.1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2 Linux Hypervisor on the Nuage 210 WBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.1 SROS VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.2 VSG/VSA and 210 WBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5 Nuage SROS for 210 WBX 23

5.1 Nuage SROS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2 Similarities of 210 WBX Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.1 BOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.2 VM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2.3 Identifying a 210 WBX in a Busy Data Center . . . . . . . . . . . . . . . . . . . . . . . . . 25
i
5.2.4 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.5 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.6 Forward Error Connection and Auto Negotiation . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.7 Tech Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Admin tech-support for the Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Admin tech-support for the SROS VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6 Configuration of the 210 WBX Models with Nuage Software 36

6.1 210 WBX - 32QSFP28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1.1 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1.2 Cards and MDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.1.3 Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1.4 LAG 97 and LAG 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.2 210 WBX - 48SFP28 6QSFP28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.2.1 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.2.2 Cards and MDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2.3 Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
25GE Capable Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
100GE Capable Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.2.4 LAG 97 and LAG 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7 Appendix 52
7.1 Installation Trace Example from the SD card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ii
210 WBX Software Installation Guide, Release 5.1.2
Release: 5.1.2
Issue: 1
Issue Date: November 01, 2017
Document Number: 3HE13484AAAB
NUAGE NETWORKS – PROPRIETARY & CONFIDENTIAL
This document contains proprietary/trade secret information which is the property of Nokia Corporation. Not to be
made available to, or copied or used by anyone who is not an employee of Nokia Corporation except when there is a
valid non-disclosure agreement in place which covers such information and contains appropriate non-disclosure and
limited use obligations.
This document is protected by copyright. Except as specifically permitted herein, no portion of the provided infor-
mation can be reproduced in any form, or by any means, without prior written permission from Nokia Corporation /
Nuage Networks.
Nuage Networks and the Nuage Networks logo are trademarks of the Nokia group of companies. Nokia is a registered
trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners.
The information presented is subject to change without notice.
Nokia Corporation / Nuage Networks assumes no responsibility for inaccuracies contained herein.
Copyright©2017 Nokia Corporation / Nuage Networks. All rights reserved.
Build Number: 75
CONTENTS 1
CHAPTER
ONE
ABOUT THIS DOCUMENT
• Validity of this Document (page 3)

• Audience (page 3)
• Technical Support (page 3)
• Required Documents (page 3)
2
For a complete list of applicable user documentation, see the Technical Publications section of the Release Notes for
your Nuage Networks software version.
1.1 Validity of this Document
Printed versions of this document may not be up to date. Only the Web version of this document is current.
1.2 Audience
This manual is intended for enterprise system administrators who are responsible for enterprise network configuration
and administrators for the Nuage VSP/VNS software.
1.3 Technical Support
If you purchased a service agreement for your Nuage Networks VSP/VNS solution and related products from a dis-
tributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you
purchased an Alcatel-Lucent or Nokia service agreement, contact your welcome center:
https://networks.nokia.com/support
Nokia Online Services (NOLCS) provides registered customers with access to technical support, software downloads,
training, documentation, literature, and other related assets for our products and solutions. For assistance with NOLCS,
including inability to access, contact us as follows:
• Inside the U.S. and Canada: 1-866-582-3688, prompt 7.
• Outside the U.S.: 1-630-224-9000
• Via email: NOLS.support@nokia.com
1.4 Required Documents
This guide complements the 210 WBX Chassis Installation Guide and the Nuage VSP User Guide, providing instruc-
tions about how to set up a 210 WBX once it has been physically installed. It includes information about:
• Software installation
• Hypervisor and SROS management and configuration
• SROS details
You are required to use the following documents in conjunction with this guide:
• Nuage VSP Release Notes
• 210 WBX Chassis Installation Guide
• Nuage VSP User Guide
Note: For all supported features, see the Nuage VSP User Guide.
1.1. Validity of this Document 3

CHAPTER
TWO
OVERVIEW
• 210 WBX Overview (page 4)

– 210 WBX 32QSFP28 (page 4)
– 210 WBX 48SFP28 6QSFP28 (page 5)
2.1 210 WBX Overview
The 210 WBX 32QSFP28 and 210 WBX 48SFP28 6QSFP28 are the next-generation leaf/spine switch for Data Center
and Enterprise networks deployments. 210 WBX offers high density QSFP28/QSFP+/SFP28/SFP+/SFP supporting
native 100GbE, 50GbE, 40GbE, 10GbE and 1GbE ports, and using splitter cables, the possibility to offer 4x25GbE,
2x50GbE, or 4x10GbE breakouts.
2.1.1 210 WBX 32QSFP28
The 210 WBX is a 1U rack-mount or desktop chassis. The following figure shows the front panel and the features of
the 32QSFP28 unit.
Fig. 2.1: 210 WBX 32QSFP28 Front Panel
4
Table 2.1: 210 WBX 32QSFP28

Front Panel Features
Key Description
A SD card slot
B Ethernet QSFP28 ports
C Console port
D Management port
E System LEDs
F USB port
G ESD grounding jack
H Reset button
The following figure shows the rear panel and the features of the 32QSFP28 unit.
Fig. 2.2: 210 WBX 32QSFP28 Rear Panel
Table 2.2: 210 WBX 32QSFP28 Rear

Panel Features
Key Description
A Chassis ground point
B Power tray for PEM
C PEM LED
D Chassis cooling fan modules
2.1.2 210 WBX 48SFP28 6QSFP28
The 210 WBX is a 1U rack-mount or desktop chassis. The following figure shows the front panel and the features of
the 48SFP28 6QSFP28 unit.
Fig. 2.3: 210 WBX 48SFP28 6QSFP28 Front Panel
2.1. 210 WBX Overview 5

Table 2.3: 210 WBX 48SFP28

6QSFP28 Front Panel Features
Key Description
A System power LED
B System Status LED
C System Fan LED
D Ethernet SFP28 ports
E Ethernet QSFP28 ports
F Management port
G Console port
The following figure shows the rear panel and the features of the 48SFP28 6QSFP28 unit.
Fig. 2.4: 210 WBX 48SFP28 6QSFP28 Rear Panel
Table 2.4: 210 WBX 48SFP28 6QSFP28 Rear

Panel Features
Key Description
A Chassis ground point
B Power tray for PEM
C PEM LED
D ESD grounding jack
E Reset button (reserved for future use)
F SD card slot
G USB port
H Chassis cooling fan modules
Note: You are required to use the 210 WBX Chassis Installation Guide to install the 210 WBX router and follow
the site preparation, installation, and other required sections before you can use this guide. This guide only provides
the Nuage software configuration of the 210 WBX after the router is installed and set up.
You are required to use the following documents in conjunction with this guide:
• Nuage VSP Release Notes
• 210 WBX Chassis Installation Guide
• Nuage VSP User Guide
2.1. 210 WBX Overview 6

CHAPTER
THREE
NUAGE SOFTWARE INSTALLATION
• Setting Up NOS with ONIE (page 7)

• Initializing the System and Downloading Software (page 8)
– Prerequisites (page 8)
– Installing NOS From the SD Card (page 8)
– Installing NOS From the Network (page 10)
* Boot After the NOS Installation is Complete (page 10)

• Automatic NOS Configuration (page 11)
– Configuring OS From the SD Card (page 11)
– Configuring OS From the Network (page 11)
– Cloud-init File Format (page 12)
* nuage_wbx cloud-init Module (page 12)

– Example of SD Card Configuration (page 13)
* cloud-init.cfg (page 13)

– Example of DHCP + HTTP Server Configuration (page 13)
• Reinstalling OS (page 14)
• Uninstalling OS (page 14)
3.1 Setting Up NOS with ONIE
Open Network Install Environment (ONIE) is an open source initiative part of the Open Compute Project. It enables
automatic installation of a Network Operating System (NOS) such as the Nuage 210 WBX software. It provides the
following services:
• Installing and reinstalling an OS
• Booting in “rescue” mode
• Formatting the system
ONIE provides the infrastructure to install NOS Nuage 210 WBX software on the internal 210 WBX disk.
7
3.2 Initializing the System and Downloading Software
3.2.1 Prerequisites
• Complete installation of the 210 WBX router using the information in the 210 WBX Chassis Installation
Guide including all site and safety requirements.
• 210 WBX software license 3HE12204AA OS (210 WBX Nuage R5.0 License)
Note: Nuage recommends using the latest released software, which might be different from the one installed in the
SD card. You must contact your Nuage representative to find out about the latest release and the process to download
the supported software image.
Once your system is ready for the software download, complete one of the following process to initialize the 210 WBX
router:
• Installing NOS from the SD card
• Installing NOS from the network to boot the device
3.2.2 Installing NOS From the SD Card
The 210 WBX comes with ONIE preinstalled. Ask your Nuage representative to get the recommendation of which
software to install and then complete the following steps:
Step 1 Download the latest software on the Nuage 210 WBX SD card.
Step 2 Connect to the console management port of the switch (C) marked by a red circle. Do not connect
to the Ethernet management port (D).
Fig. 3.1: 210 WBX Console Management Port
Step 3 Insert the SD card and power up the system. The system boots up from the internal disk following
the boot, with GRUB. The following screen is displayed when it boots from ONIE.
Note: Install OS option is the default.
3.2. Initializing the System and Downloading Software 8

Fig. 3.2: 210 WBX ONIE Bootup
If the auto boot is interrupted for some reason, select the highlighted Install OS option explicitly. If
there is no interruption, the auto-boot results in selecting this option automatically. The installation
begins after ONIE finds the onie-installer-x86_64 file that exists on the SD card. ONIE
auto-mounts the file system to find this file.
An installation trace example looks like the following:
Booting ÒNIE: Install OS'

Welcome to GRUB!
ONIE: OS Install Mode ...
Version : 2016.02
Build Date: 2017-02-08T17:09+0800
Info: Mounting kernel filesystems... done.
Info: Mounting ONIE-BOOT on /mnt/onie-boot ...
Installing for i386-pc platform.
Installation finrandom: mktemp urandom read with 19 bits of entropy
˓→available
<snip>
<snip>
Note: For the detailed trace example, go to the Appendix.
After installation is complete, the SD card is not needed by the system and may be removed.

3.2.3 Installing NOS From the Network
ONIE supports a number of methods for locating a NOS installer image. See the details in the “Installing over the
Network” section of the ONIE user guide: https://opencomputeproject.github.io/onie/user-guide/index.html
Note: An SD card is not required to perform installation from the network.
As the prerequisite for the NOS configuration, ONIE requires a valid DHCP server and an HTTP server. The DHCP
server provides the IP, netmask, default gateway and so on to enable the auto-configuration of the Ethernet management
port.
Note: The 210 WBX has two RJ45 ports at the front panel: the Ethernet management port and the console port.
Step 1 Connect the Ethernet management port of the 210 WBX to the LAN network so that it can reach
the DHCP server.
Note: Connect to the Ethernet management port (D) of the switch marked by a red circle. Do not
connect to the console management port of the switch (C).
Fig. 3.3: 210 WBX Ethernet Management Port
Step 2 Copy the NOS Installer Image to the HTTP server.

Step 3 In the DHCP server configuration, in addition to the IP subnet, default netmask, default gateway,
and so on, add the default-url option that points to the Nuage installer file in the HTTP server.
option default-url "http://<webserver-address>/onie-installer-x86_64"
Note: For details, see the ONIE user guide: https://opencomputeproject.github.io/onie/user-guide/index.html
Boot After the NOS Installation is Complete
After the Nuage 210 WBX NOS is installed, the 210 WBX automatically boots from NOS software. The NOS
software boots automatically unless the boot menu is interrupted. The following display shows the boot menu from
the console after the NOS is installed.
Note: The sample output is only an example and the Nuage software may not match the output on your terminal.

Fig. 3.4: 210 WBX NOS Bootup
The boot menu content reflects the version of 210 WBX NOS image installed on the disk. The menu displayed
indicates that the NOS is successfully installed.
A separate ONIE option lets you reinstall the software.
3.3 Automatic NOS Configuration
The 210 WBX supports automated configuration of the system without the need to log in to the switch. This is done
using configuration files previously located on the SD card or on the HTTP server serving the ONIE installer. Note
that those files need to be created and added to the SD card.
The configuration file is cloud-init.cfg, a file in YAML format used to configure the Linux hypervisor with the
Cloud-Init software,
3.3.1 Configuring OS From the SD Card
In order to customize the switch from the SD card, edit the cloud-init.cfg in the root directory of the SD
card. Static IPv4 host configuration can be done using cloud-init.cfg commands or manually editing the IP Linux
configuration, applying the configuration to ifcfg-mgmt interface (see Getting Started for more information).
3.3.2 Configuring OS From the Network
When ONIE installation is performed via DHCP server, the default-url option is used to specify the URL of the
ONIE installer.
During NOS installation, the ONIE installer will query the HTTP server for a cloud-init.cfg file on the same
path as the ONIE installer.
3.3. Automatic NOS Configuration 11

For example, if the default-url option is set to option default-url

"http://<webserver>/switch001/onie-installer-x86_64", the installer will query the URL
http://<webserver>/switch001/cloud-init.cfg for a configuration file. If found, the configuration
will be automatically applied at first boot.
3.3.3 Cloud-init File Format
The cloud-init.cfg must start with the line #cloud-config.

At first boot, the Linux system is configured according to the cloud-init configuration. Upon reboot, the initial config-
uration persists and the cloud-init.cfg file is ignored. To apply the configuration again, an ONIE reinstall must
be performed.
The system can be configured with cloud-init modules.
In order to secure the WBX switch, a common usage is to disable password root login and inject public SSH keys:
#cloud-config
ssh_pwauth: false
disable_root: true
ssh_authorized_keys:
- ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAGEA3FSyQwBI6Z+nCSjUU ...
It is possible to execute custom commands at the time of first boot:

#cloud-config
bootcmd:
- echo "Cloud-init configuration in progress...."
- echo "Installing additional packages"
- yum -y install nfs-utils
It is also possible to configure the ifcfg-mgmt interface:

#cloud-config
runcmd:
- '\sed -i "s/BOOTPROTO=dhcp/BOOTPROTO=none\nDEFROUTE=yes\nIPADDR=10.31.135.
˓→121\nNETMASK=255.255.224.0\nGATEWAY=10.31.128.1/" /etc/sysconfig/network-scripts/
˓→ifcfg-mgmt'
- 'ifconfig mgmt 10.31.135.121 netmask 255.255.224.0 up'

- 'route add -net 0.0.0.0 gw 10.31.128.1'
Configuration management tools such as Puppet or Ansible can be applied via cloud-init, as well as remote syslog
configuration. A complete list of modules is documented in the cloud-init modules documentation.
nuage_wbx cloud-init Module
A custom nuage_wbx cloud-init module allows the datacenter administrator to configure the boot options of the
TiMOS VM without logging in to the machine with the bof YAML key.
This allows configuration of a remote FTP server for switch configuration. Such a configuration lets the operator
centralize the configuration of several switches in a single server, while keeping the ability to push configuration
changes with the admin save command:
#cloud-config
nuage_wbx:
bof: #boot option file
primary-config: "ftp://user:pass@<ftp-server>/./switch001/config.cfg"

By default, the 210 WBX switch is designed to persist the configuration when an ONIE reinstallation is performed,
by storing relevant configuration files in a persistent partition. Such behaviour is not desirable in the context of fully
automated remote configuration. The nuage_wbx cloud-init module provides the wipe_persistent_data key
to ensure the system is provisioned from a clean state:
#cloud-config
nuage_wbx:
wipe_persistent_data: true
It is also possible to set up the VM SROS’s IPv6 static IP address via cloud-init’s nuage_wbx setting. This updates the
BOF directly:
#cloud-config
nuage_wbx:
bof:
primary-config: ftp://guest:guest@135.227.177.113/./sros-cfg/dni-tomahawk2
address: cafe:2::8779:87e3:b40f:2020/64
Getting the configuration file (config.cfg) from an HTTP server is not currently supported.
3.3.4 Example of SD Card Configuration
cloud-init.cfg
#cloud-config
ssh_pwauth: false
disable_root: true
nuage_wbx:
3.3.5 Example of DHCP + HTTP Server Configuration
To automatically configure several switches in a datacenter, a recommended approach is to have a unique

default_url per switch in the DHCP server, i.e.:
host switch001 { hardware ethernet D0:99:D5:AB:CD:EF; fixed-address 10.10.10.1;
˓→option default-url "http://<webserver>/switch001/onie-installer-x86_64"; }
host switch002 { hardware ethernet D0:99:D5:AB:CD:E1; fixed-address 10.10.10.2;

˓→option default-url "http://<webserver>/switch002/onie-installer-x86_64"; }
The recommended HTTP server file structure is as follows:

[root@webserver ~]$ tree /var/www/html
.
+-- onie-installer-x86_64 -> onie-installer-x86_64-nuage-5.1.2-40
+-- onie-installer-x86_64-nuage-5.1.2-40
+-- switch001
+-- cloud-init.cfg
+-- onie-installer-x86_64 -> ../onie-installer-x86_64
+-- switch002
+-- cloud-init.cfg
+-- onie-installer-x86_64 -> ../onie-installer-x86_64

Example of cloud-init.cfg :
#cloud-config
ssh_pwauth: false
disable_root: true
nuage_wbx:
3.4 Reinstalling OS
At boot time, selecting the ONIE option launches the ONIE bootloader. It attempts to reinstall the switch by using the
same sources described earlier for installing NOS from the SD card or installing NOS from the network.
Warning: After selecting the ONIE option from the boot menu, you must proceed to reinstall. The system
partitions are lost after the reinstall.
By default, during ONIE reinstall, the switch configuration and management network configuration are persisted. Any
manual customization of the Linux OS is not persisted and is lost after reinstall.
3.5 Uninstalling OS
To uninstall NOS, interrupt the NOS auto-boot, select “ONIE” option followed by ONIE: Uninstall OS as shown in
the figure:
3.4. Reinstalling OS 14
Fig. 3.5: 210 WBX ONIE Uninstall OS
3.5. Uninstalling OS 15
CHAPTER
FOUR
GETTING STARTED WITH THE NUAGE 210 WBX
• Getting Started (page 16)

• Linux Hypervisor on the Nuage 210 WBX (page 19)
– SROS VM (page 19)
– VSG/VSA and 210 WBX (page 20)
4.1 Getting Started
After the software is installed from the console, the system shows the login prompt of the Linux hypervisor:
Nuage 210-WBX 5.0.2-28

localhost login:
Step 1 Login as root/UFXCr4733F

The WBX has a two components: a Linux host and an SROS VM. The WBX host component uses
static IP (manually configured or using cloud-init) or DHCP to get the IP address for Linux. The
SROS VM uses an IPv4 host address and/or a static-IPv6 for the SROS management interface if
IPv6 support is desired (configured directly in the BOF or using cloud-init). For more information,
see Automatic NOS Configuration and BOF.
Note: If the system was booted and there was a functional DHCP server, a dynamic IP address for the Ethernet
management port was configured as part of the process. Therefore, skip Step 2; otherwise complete Step 2 to configure
a static IP address for the Ethernet management port.
Note: If a static IPv4 address was configured using cloud-init (see Automatic NOS Configuration), skip Step 2;
otherwise complete Step 2 to configure a static IP address for the Ethernet management port.
Step 2 Configure the Ethernet management port using the ifcfg-mgmt file and modify to the desired
configuration. The following is an example (IPv6 configuration in the host is optional and not
shown in the example):
[root@localhost network-scripts]# more ifcfg-mgmt

TYPE=Bridge
NAME=mgmt
16
DEVICE=mgmt
ONBOOT=yes
IPADDR=178.227.223.73
NETMASK=255.255.255.128
GATEWAY=178.227.223.1
Step 3 Restart the network configuration by entering the command below or, if the IP address has been
manually configured, a manual reboot of the system is recommended.
systemctl restart network.service
Step 4 Enter the ifconfig command to display all available interfaces of the hypervisor:
[root@localhost ~]# ifconfig
xbcmh0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:a0:c9:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
xbcmh1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

ether 34:12:78:56:01:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
TX packets 0 bytes 0 (0.0 B)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 23880 bytes 2219206 (2.1 MiB)
TX packets 23880 bytes 2219206 (2.1 MiB)
mgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 178.227.223.73 netmask 255.255.255.128 broadcast 178.227.
˓→223.127
ether d0:99:d5:95:12:41 txqueuelen 1000 (Ethernet)

device memory 0xfbd00000-fbd7ffff
virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 169.254.1.1 netmask 255.255.255.0 broadcast 169.254.1.255
ether 52:54:00:9f:72:e2 txqueuelen 1000 (Ethernet)
RX packets 9062 bytes 982398 (959.3 KiB)
TX packets 10452 bytes 774295 (756.1 KiB)
virbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

ether 52:54:00:a1:35:10 txqueuelen 1000 (Ethernet)
4.1. Getting Started 17


vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet6 fe80::fc54:ff:fee9:b148 prefixlen 64 scopeid 0x20<link>
ether fe:54:00:e9:b1:48 txqueuelen 1000 (Ethernet)
vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet6 fe80::fc54:ff:fe76:ae80 prefixlen 64 scopeid 0x20<link>
ether fe:54:00:76:ae:80 txqueuelen 1000 (Ethernet)
Step 5 Once the Ethernet management port is configured, access the hypervisor using SSH: ssh -p
893 root@ip.
As part of the installation process, the system automatically launches the SROS VM.
Note: Wait 5 minutes before accessing the VM console after a power cycle (cold reboot) or new installation.
The following example shows a WBX with a DHCP server in the ifcfg-mgmt interface:
# 'Management' bridge configuration for Nuage WBX systems

# The physical network interface of the system is made part of this bridge
DEVICE=mgmt
TYPE=Bridge
BOOTPROTO=dhcp
ONBOOT=yes
DELAY=0
The ifconfig command shows both IPv4 and IPv6 host addresses:
mgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet6 cafe:2::d299:d5ff:fe95:1111 prefixlen 128 scopeid 0x0<global>
inet6 fe80::d299:d5ff:fe95:3c41 prefixlen 64 scopeid 0x20<link>
ether b2:bb:6a:fc:36:df txqueuelen 1000 (Ethernet)
Note: cafe:2::d299:d5ff:fe95:1111 is the Linux host IPv6, not the SROS VM IPv6 address.
4.1. Getting Started 18

4.2 Linux Hypervisor on the Nuage 210 WBX
After the installation, there is access to the Linux hypervisor as a regular commercial Linux system. The host OS is
running Centos 7.3.
Hypervisor partition:
After the installation, the partitions should look like below
[root@localhost /]# gdisk -l /dev/sda

GPT fdisk (gdisk) version 0.8.6
Partition table scan:

MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.

Disk /dev/sda: 125045424 sectors, 59.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A9E8C47D-0666-420F-A8B8-655D61AA6B72
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 125045390
Partitions will be aligned on 2048-sector boundaries
Total free space is 3407 sectors (1.7 MiB)
Number Start (sector) End (sector) Size Code Name

1 2048 6143 2.0 MiB EF02 GRUB-BOOT
2 6144 268287 128.0 MiB FFFF ONIE-BOOT
3 268288 57936526 27.5 GiB 8300 VSGX-ROOT
4 57937920 125045390 32.0 GiB 8300 VSGX-DATA
VSGX-DATA is the persistent partition and all data to be preserved in an upgrade/reboot should be in this partition.
4.2.1 SROS VM
Step 1 To check that the SROS VM is running, enter the virsh command:
[root@localhost ~]# virsh list --all

Id Name State
----------------------------------------------------
1 vsgvm-wbx210-48s running
Step 2 To access and exit the SROS VM console using the Linux hypervisor, use command console
vsgvm to get to the VM console. This command enhances virsh console Id as the entire console life
output of the VM which is redirected to a specific file as shown in the following example:
[root@localhost ~]# console vsgvm

[Enter `Êc?' for help]
Login:
Password:
A:NS1712T0021#
4.2. Linux Hypervisor on the Nuage 210 WBX 19

Note: As in regular SROS, the default user and password is admin/admin.
Step 3 To exit the VM console session, type Êc. - Ctrl-E (followed by) c (followed by) . -
Note: The complete console output is redirected to the file /var/log/conserver.vsgvm.log
Once in the Nuage SROS VM, the unit behaves like a regular system.
4.2.2 VSG/VSA and 210 WBX
There are certain differences when comparing a BOF on a VSG/VSA and on a 210 WBX. The system runs on a VM
and therefore, the VM has an internal IP address, netmask, dns, and static route that points to the hypervisor as the
default gateway. This configuration is common to all 210 WBX VMs. The BOF also shows the Ethernet management
IP information, because that is the external point to access the SROS VM (in the example, previously in this user guide
the ifcfg-mgmt file has been configured with IPADDR=178.227.223.73).
A:# show bof
===============================================================================
BOF (Memory)
===============================================================================
primary-image cf2:\timos\both.tim
primary-config cf1:\config.cfg
address 169.254.1.2/24 active
primary-dns 169.254.1.1
static-route 0.0.0.0/0 next-hop 169.254.1.1
no auto-boot
autonegotiate
duplex full
speed 100
wait 3
persist off
no li-local-save
no li-separate
console-speed 115200
===============================================================================
Host Information
===============================================================================
linuxhost-ipv4-address 178.227.223.73 netmask 255.255.255.128
linuxhost-ipv6-address-1 Not available
linuxhost-ipv6-address-2 Not available
===============================================================================
Note: Although IPv6 can be configured in the Ethernet management port and is displayed as part of the BOF, SROS
VM can only use IPv4 to communicate with the external world. The hypervisor can be accessible with applications
using port 893 (See the ssh example earlier), otherwise applications default to the SROS VM.
The BOF (or files referenced in the BOF like config) does not exist as an individual file, it is contained within the user
disk vsgvm-wbx210-*.usrdisk.raw. The user disk is saved in the following folder:
[root@localhost ~]# cd /vsgx-data
[root@localhost vsgx-data]# ls -la
total 216904

drwxr-xr-x 3 root root 4096 Jul 11 20:51 .

dr-xr-xr-x. 20 root root 4096 Jul 11 21:17 ..
drwx------ 2 root root 16384 Apr 26 2000 lost+found
-rw-r--r-- 1 qemu qemu 222082560 Jul 12 22:33 vsgvm-wbx210-32q.usrdisk.raw
It is possible to list the content of the user disk:

[root@localhost ~]#mdir -i vsgvm-wbx210-32q.usrdisk.raw@@32256 ::/
Volume in drive : is SROS VM
Volume Serial Number is 77BB-4E50
Directory for ::/
bof cfg 307 2017-08-21 19:17 bof.cfg

config cfg 0 2017-08-21 19:17 config.cfg
BOOTLOG TXT 2621 2017-08-23 21:45 bootlog.txt
N~999990 INF 320 2017-08-23 21:46 nvsys.info
B~999988 TXT 2627 2017-08-22 17:58 bootlog_prev.txt
5 files 5 875 bytes
221 798 400 bytes free
It is also possible to save a file from the user disk locally in the persistent partition /vsgx-data (example bof.cfg):
[root@localhost ~]#mcopy -i vsgvm-wbx210-32q.usrdisk.raw@@32256 ::/config.cfg .
[root@localhost vsgx-data]# ls
config.cfg lost+found vsgvm-wbx210-32q.usrdisk.raw
However for easiness, recommendation is that whenever possible, VM files to be saved externally using an ftp:
*A:210-WBX# show bof

===============================================================================
BOF (Memory)
===============================================================================
primary-config ftp://*:*@172.203.15.48/./configs/tor10.cfg
After the installation, the Nuage software is saved under /usr/nuage/

[root@localhost ~]# cd /usr/nuage/
[root@localhost nuage]# ls -la
total 354604
drwxr-xr-x 4 root root 4096 Jul 11 21:17 .
drwxr-xr-x 14 root root 4096 Jul 6 00:35 ..
-rw-r--r-- 1 root root 2823 Jul 6 00:26 i2c_lock_functions
-rw-r--r-- 1 root root 884 Jul 11 21:16 last-vm-shut-trace.txt
-rwxr-xr-x 1 root root 17237683 Jul 5 23:11 nuagerpcd
-rw-r--r-- 1 root root 98703360 Jul 6 00:25 nuage-vsgx-imgdisk.raw
-rw-r--r-- 1 root root 222082560 Jul 6 00:30 nuage-vsgx-usrdisk.raw
-rwxr-xr-x 1 root root 919240 Jul 6 00:30 onie-syseeprom
-rw-r--r-- 1 root root 809 Jul 6 00:26 parser.awk
-rwxr-xr-x 1 root root 24076200 Jul 6 00:29 qemu-kvm
-rwxr-xr-x 1 root root 2210 Jul 6 00:26 qemu-vsgvm-emulator
lrwxrwxrwx 1 root root 41 Jul 11 21:17 read-env -> /usr/nuage/wbx210-32q/read-
˓→env-wbx210-32q
-rwxr-xr-x 1 root root 279 Jul 6 00:26 read-if.sh

-rw-r--r-- 1 root root 344 Jul 6 00:26 README
lrwxrwxrwx 1 root root 46 Jul 11 21:17 set-fan-speed -> /usr/nuage/wbx210-32q/
˓→set-fan-speed-wbx210-32q
lrwxrwxrwx 1 root root 40 Jul 11 21:17 set-led -> /usr/nuage/wbx210-32q/set-

˓→led-wbx210-32q

lrwxrwxrwx 1 root root 40 Jul 11 21:17 sfp_i2c -> /usr/nuage/wbx210-32q/sfp_

˓→i2c_wbx210-32q
-rw-r--r-- 1 root root 257 Jul 6 00:26 vsg-net-mgmt.xml

-rw-r--r-- 1 root root 256 Jul 6 00:26 vsg-net-rpc.xml
-rwxr-xr-x 1 root root 13593 Jul 6 00:26 vsgvm
-rw-r--r-- 1 root root 12938 Jul 6 00:26 vsgvm_functions
-rwxr-xr-x 1 root root 2326 Jul 6 00:26 vsgx-bootmsg.sh
drwxr-xr-x 2 root root 4096 Jul 6 00:36 wbx210-32q
drwxr-xr-x 3 root root 4096 Jul 6 00:36 wbx210-48s
You must follow the README file and not modify or delete the contents (add, remove, change, etc) from this directory.
Any accidental change can break the software installation and the only solution is to reinstall the software again.
[root@localhost nuage]# more README
NOTICE
======
This directory (and subdirectories within this) accomodates all executables,

configuation and others that are needed for Nuage software to run.
Any changes to the contents of this directory that are made without Nuage being
aware may make the platform inoperable.
DO NOT MODIFY OR DELETE CONTENTS OF THIS DIRECTORY HIERARCHY

CHAPTER
FIVE
NUAGE SROS FOR 210 WBX
• Nuage SROS (page 23)

• Similarities of 210 WBX Models (page 23)
– BOF (page 23)
– VM Information (page 24)
– Identifying a 210 WBX in a Busy Data Center (page 25)
– Power Supplies (page 25)
– Quality of Service (page 26)
– Forward Error Connection and Auto Negotiation (page 32)
– Tech Support (page 33)
* Admin tech-support for the Hypervisor (page 33)

* Admin tech-support for the SROS VM (page 34)
5.1 Nuage SROS
The 210 WBX reuses the same Nuage SROS used on the 7850 VSG. The main difference is the 210 WBX runs the
SROS on a virtual machine and uses an x86 platform running Linux. Also it uses a different silicon 100GE capable
chip set. However, for a user that logs into the system directly in the VM, there are no major differences between the
two products, other than the differences about the use of different interfaces, and some related features. The 210 WBX
supports 100GE, 50G and 25G, which are new compared to a 7850 VSG.
5.2 Similarities of 210 WBX Models
5.2.1 BOF
As shown in the Linux Hypervisor on the Nuage 210 WBX section of this document, the BOF has been modified to
reflect the VM, and points to the hypervisor as a default gateway for out-of-band management for IPv4. However,
for IPv6 management, the address must be manually configured in the BOF or added using cloud-init (see Automatic
NOS Configuration for more information). The IPv6 BOF address is accessible directly from the network (IPv6 host
address is optional).
23
The Ethernet management of the hypervisor has been added to the BOF display to show the IP address that is actually
being used for out-of-band management.
In the following example, note that the IP Host Information is different from the IP address of the VM, for both IPv4
and IPv6.
*A:210-WBX-32Q# show bof

===============================================================================
BOF (Memory)
===============================================================================
primary-image cf2:\timos\both.tim
primary-config cf1:\config.cfg
address 169.254.1.2/24 active
address cafe:2::d299:d5ff:fe95:2222/64 active
primary-dns 169.254.1.1
static-route 0.0.0.0/0 next-hop 169.254.1.1
no auto-boot
autonegotiate
duplex full
speed 100
wait 3
persist off
no li-local-save
no li-separate
no fips-140-2
console-speed 115200
===============================================================================
Host Information
===============================================================================
linuxhost-ipv4-address 10.31.137.47 netmask 255.255.224.0
linuxhost-ipv6-address-1 cafe:2::d299:d5ff:fe95:1111 prefixlen 128 0x0
˓→<global>
linuxhost-ipv6-address-2 cafe:2::b0bb:6aff:fefc:36df prefixlen 64 0x0

˓→<global>
===============================================================================
5.2.2 VM Information
The VM is accessible using the Host Information IPv4 or BOF IPv6 (example, from SSH):
ROL:~ $ ssh admin@178.227.223.74

TiMOS-DC-B-5.0.2-28 both/x86 NUAGE 210 Copyright (c) 2000-2017 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Jul 5 20:29:23 PDT 2017 [080cc4] by builder in /rel5.0-DC/release/panos/
˓→main
admin@178.227.223.74's password:
ROL:~ $ ssh -6 admin@cafe:2::d299:d5ff:fe95:2222

TiMOS-DC-B-5.0.2-28 both/x86 NUAGE 210 Copyright (c) 2000-2017 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Jul 5 20:29:23 PDT 2017 [080cc4] by builder in /rel5.0-DC/release/panos/
˓→main
admin@cafe:2::d299:d5ff:fe95:2222's password:
5.2. Similarities of 210 WBX Models 24

5.2.3 Identifying a 210 WBX in a Busy Data Center
To identify a particular 210 WBX in a busy data center, enter the enable-uid-beacon command to trigger an “all lights
on LED” amber blink. All LEDs flash in amber and a technician on site can find the switch in question.
*A:#configure system [no] enable-uid-beacon
5.2.4 Power Supplies
To verify the state of the power supplies (up or failed), enter the show chassis power-supply command.
Note: By default, the power supplies displayed in the show chassis command shows DC power supplies and appear
as up, irrespective of the number of power supplies fed or if being AC or DC.
*A:# show chassis power-supply
===============================================================================
Chassis Information
===============================================================================
Power Supply Information
Number of power supplies : 2
Power supply number : 1

Defaulted power supply type : dc
Status : up

Status : up
===============================================================================
To configure the Power supplies, enter the configure system power-supply command:
*A: >config>system# power-supply

- power-supply <power-supply-id> <type>
<power-supply-id> : [1..2]. Specifies power supply 1 or 2

<type> : keywords - dc|ac {single|multiple}|default|none. Specifies DC
˓→or AC
<single|multiple> : keywords
*A:# configure system power-supply 1 ac single

*A:# configure system power-supply 2 ac single
After the changes, the system shows the real status of the power supplies. Status failed is displayed if the power supply
has any problem or it has not been supplied with power.
*A:# show chassis power-supply
===============================================================================
Chassis Information
===============================================================================


Configured power supply type : ac single
Status : up
AC power : within range
DC power : within range
Over temp : within range

Configured power supply type : ac single
Status : failed
AC power : out of range
DC power : out of range
Over temp : within range
Note: The multiple keyword is not supported in the following output example:
*A:# configure system power-supply 1 ac multiple

MINOR: CHMGR #1001 Invalid - Unsupported power supply type ac multiple
5.2.5 Quality of Service
The 7850 VSG and the 210 WBX are slightly different in terms of Egress QoS and Queue hierarchy.
• The 7850 VSG has one scheduler and then 8 queues which are scheduled based on the config (strict and wrr
queues).
• The 210 WBX has one scheduler per forwarding class (FC) per port. So the wrr-weight is configured per FC
and not within the queue.
210 WBX Egress QoS model has one scheduler per port per FC available to be configured. This makes a total of
8 schedulers per port. Each of these schedulers have one multicast and one unicast queue feeding them. Default
configuration sets FC-8 to FC-5 in strict priority, and FC-4 to FC-1 to operate in weighted-round-robin (FC, from
high priority to low priority are NC, H1, EF, H2, L1, AF, and BE). However, the CLI allows for more schedulers
to be brought into weighted-round-robin by appropriately configuring the wrr-queues <from-fc> to <to-fc>. Once
the schedulers are not assigned from the strict priority and are provisioned as wrr, they are available for weight
configuration under fc <> sched-wrr-weight <weight>, where weight ranges from 1 to 100.
The sample output shows the default QOS policy on the 210 WBX:
A:# configure qos egress 1
A:as5712>config>qos>egress# info detail
----------------------------------------------
description "Default egress QoS policy."
no remarking
dot1p-remarking
wrr-queues 4 to 1
no policy-name
queue 1 create
adaptation-rule pir closest cir closest
rate max cir 0
mbs default
exit
queue 2 create
rate max cir 0

mbs default
exit
queue 3 create
rate max cir 0
mbs default
exit
queue 4 create
rate max cir 0
mbs default
exit
queue 5 create
rate max cir 0
mbs default
exit
queue 6 create
rate max cir 0
mbs default
exit
queue 7 create
rate max cir 0
mbs default
exit
queue 8 create
rate max cir 0
mbs default
exit
queue 11 multipoint create
rate max cir 0
mbs default
exit
rate max cir 0
mbs default
exit
rate max cir 0
mbs default
exit
rate max cir 0
mbs default
exit
rate max cir 0
mbs default
exit


rate max cir 0
mbs default
exit
rate max cir 0
mbs default
exit
rate max cir 0
mbs default
exit
fc af create
queue 3
multipoint-queue 13
dot1p-in-profile 2
dot1p-out-profile 2
no de-mark
dscp-in-profile af11
dscp-out-profile af12
sched-wrr-weight 1
exit
fc be create
queue 1
multipoint-queue 11
dot1p-in-profile 0
dot1p-out-profile 0
no de-mark
dscp-in-profile be
dscp-out-profile be
sched-wrr-weight 1
exit
fc ef create
queue 6
multipoint-queue 16
dot1p-in-profile 5
dot1p-out-profile 5
no de-mark
dscp-in-profile ef
dscp-out-profile ef
no sched-wrr-weight
exit
fc h1 create
queue 7
multipoint-queue 17
dot1p-in-profile 6
dot1p-out-profile 6
no de-mark
dscp-in-profile nc1
dscp-out-profile nc1
no sched-wrr-weight
exit
fc h2 create
queue 5
multipoint-queue 15
dot1p-in-profile 4

dot1p-out-profile 4
no de-mark
no sched-wrr-weight
exit
fc l1 create
queue 4
multipoint-queue 14
dot1p-in-profile 3
dot1p-out-profile 3
no de-mark
sched-wrr-weight 1
exit
fc l2 create
queue 2
multipoint-queue 12
dot1p-in-profile 1
dot1p-out-profile 1
no de-mark
dscp-in-profile cs1
dscp-out-profile cs1
sched-wrr-weight 1
exit
fc nc create
queue 8
multipoint-queue 18
dot1p-in-profile 7
dot1p-out-profile 7
no de-mark
dscp-in-profile nc2
no sched-wrr-weight
exit
----------------------------------------------
For ease of comparison, the following output example shows the default QOS policy for the 7850 VSG:
*A:>config>qos>egress$ info detail

----------------------------------------------
no description
no remarking
no dot1p-remarking
wrr-queues 4 to 1
no policy-name
queue 1 create
rate max cir 0
mbs default
wrr-weight 1
exit
queue 2 create
rate max cir 0
mbs default
wrr-weight 1

exit
queue 3 create
rate max cir 0
mbs default
wrr-weight 1
exit
queue 4 create
rate max cir 0
mbs default
wrr-weight 1
exit
queue 5 create
rate max cir 0
mbs default
no wrr-weight
exit
queue 6 create
rate max cir 0
mbs default
no wrr-weight
exit
queue 7 create
rate max cir 0
mbs default
no wrr-weight
exit
queue 8 create
rate max cir 0
mbs default
no wrr-weight
exit
rate max cir 0
mbs default
wrr-weight 1
exit
rate max cir 0
mbs default
wrr-weight 1
exit
rate max cir 0
mbs default
wrr-weight 1
exit
rate max cir 0

mbs default
wrr-weight 1
exit
rate max cir 0
mbs default
no wrr-weight
exit
rate max cir 0
mbs default
no wrr-weight
exit
rate max cir 0
mbs default
no wrr-weight
exit
rate max cir 0
mbs default
no wrr-weight
exit
fc af create
queue 3
multipoint-queue 13
dot1p-in-profile 2
dot1p-out-profile 2
no de-mark
exit
fc be create
queue 1
multipoint-queue 11
dot1p-in-profile 0
dot1p-out-profile 0
no de-mark
dscp-in-profile be
dscp-out-profile be
exit
fc ef create
queue 6
multipoint-queue 16
dot1p-in-profile 5
dot1p-out-profile 5
no de-mark
dscp-in-profile ef
dscp-out-profile ef
exit
fc h1 create
queue 7
multipoint-queue 17
dot1p-in-profile 6

dot1p-out-profile 6
no de-mark
dscp-in-profile nc1
exit
fc h2 create
queue 5
multipoint-queue 15
dot1p-in-profile 4
dot1p-out-profile 4
no de-mark
exit
fc l1 create
queue 4
multipoint-queue 14
dot1p-in-profile 3
dot1p-out-profile 3
no de-mark
exit
fc l2 create
queue 2
multipoint-queue 12
dot1p-in-profile 1
dot1p-out-profile 1
no de-mark
dscp-in-profile cs1
dscp-out-profile cs1
exit
fc nc create
queue 8
multipoint-queue 18
dot1p-in-profile 7
dot1p-out-profile 7
no de-mark
dscp-in-profile nc2
exit
5.2.6 Forward Error Connection and Auto Negotiation
Forward error connection (FEC) is applicable to 25GE ports (clause 74) and 100G ports (clause 91). FEC is disabled
for interoperability with Nokia 7X50 portfolio (note that this might not be the case in platforms belonging to other
vendors where FEC might be enabled by default).
# configure port ethernet [no] forward-error-correction
Auto Negotiate (AN) is applicable to 25G and 100G ports with copper interfaces. AN is enabled by default and only
is applied when a port is operating at 25G or 100G and a copper SFP has been detected.
# configure port ethernet [no] autonegotiate

Note: 210 WBX does have a limitation for AN and 100G FEC. Although it supports AN and supports 100G FEC,
it does not support negotiating 100GE FEC. If the peer sets its negotiation to support and require FEC, the link does
not come up with the default settings. If the peer sets its negotiation to support FEC, the link comes up, but without
FEC. You must either disable AN on both the 210 WBX and the peer to get the link to come up with FEC, or disable
FEC on the peer to get AN to bring the link up without FEC. Within 210 WBX and 7850 the link comes up with AN
enabled and FEC disabled (default values). In general the link comes up as long as the FEC setting is the same on both
ends and auto negotiate is enabled on both ends. FEC is negotiated correctly on 25G ports.
5.2.7 Tech Support
Similar to the admin tech-support command available on SROS to gather the necessary logs and configuration files
for technical support purposes, the 210 WBX models have a similar utility.
Two admin tech-supports are needed:
1. Admin tech-support for the hypervisor
2. Admin tech-support for the VM (same as a hardware VSG or 7750)
Admin tech-support for the Hypervisor
For the hypervisor, the utility is /usr/nuage/support/tech-support and it executes commands listed in
/usr/nuage/support_commands, and other contents that exist in /usr/nuage/logs and /var/log.
The result is archived and stored in /run/nuage-support/.
The following display shows an example output:
[root@localhost support]# ./tech-support

Running command: cat /etc/issue
Running command: uname -a
Running command: rpm -qa | egrep "kernel|vsg|nuage"
Running command: /usr/nuage/onie-syseeprom
Running command: cat /var/run/oniepfenv.json
Running command: dmidecode
Running command: cat /etc/sysconfig/network-scripts/ifcfg-mgmt
Running command: ifconfig -a
Running command: ip link show
Running command: netstat -r
Running command: cat /etc/resolv.conf
Running command: firewall-cmd --list-all
Running command: iptables -L
Running command: blkid
Running command: lsblk
Running command: df -hT
Running command: mount
Running command: cat /proc/mounts
Running command: virsh list --all
Running command: systemctl status -l vsgvm.service
Running command: systemctl status -l nuage-rpc.service
Running command: dmesg
Running command: mpstat -P ALL 5 1
Running command: top -n 1 -b
Running command: sleep 3
Running command: top -n 1 -b

Running command: lspci -k

Running command: cat /etc/udev/rules.d/80-nuage-net-names.rules
Running command: find /usr/nuage -exec \ls -ls {} \;
Running command: ls -ls /vsgx-data
Running command: ls -ls /vsgx-sd
Running command: /usr/nuage/support/dump-virsh-info
Copying logs...
============================================================================
Tech support file is at:
/run/nuage-support/tech-support-Fri_Aug_11_185112_EDT_2017.tgz
The file is kept with the system for only 2 hours.
Upload this file soon to technical support for analysis.
============================================================================
Admin tech-support for the SROS VM
For the SROS VM, tech-support is executed as normal (saved to a local file, or to an ftp server). For more info about
how to copy a file from the VM to the hypervisor host, see the VSG/VSA and 210 WBX section.
A:# admin tech-support

- tech-support <file-url>
<file-url> : <local-url>|<remote-url>
local-url - [<cflash-id>/][<file-path>]
200 chars max, including cflash-id
directory length 99 chars max each
remote-url - [{ftp://|tftp://}<login>:<pswd>@
<remote-locn>/][<file-path>]
255 chars max
directory length 99 chars max each
remote-locn - [ <hostname> | <ipv4-address> | <ipv6-
˓→address> ]
ipv4-address - a.b.c.d
ipv6-address - x:x:x:x:x:x:x:x[-interface]
x:x:x:x:x:x:d.d.d.d[-interface]
x - [0..FFFF]H
d - [0..255]D
interface - 32 chars max, for link local
˓→addresses
cflash-id - cf1:|cf1-A:|cf1-B:|cf2:|cf2-A:|cf2-B:
A:WBX-LEAF2# admin tech-support cf1:/techlog

Processing CPM...
Second Pass
Processing CPM...
Processing IOM in Slot 1...
Processing MDA in 1/1...
Done...
A:# file dir
Volume in drive cf1 on slot A is SROS VM.

Volume in drive cf1 on slot A is formatted as FAT32
Directory of cf1:\
07/05/2017 09:25p 307bof.cfg

08/23/2017 09:56p 2637bootlog.txt
08/11/2017 09:53p 2637bootlog_prev.txt
04/19/2017 09:52a 10413config.cfg
04/19/2017 09:43a 9746config.cfg.1
04/19/2017 08:51a 8888config.cfg.2
07/05/2017 09:25p 0config.cfg.3
08/23/2017 09:56p 319nvsys.info
08/22/2017 11:29p 167836tech
08/24/2017 12:05a 167764techlog
10 File(s) 370547 bytes.
0 Dir(s) 221425664 bytes free.

CHAPTER
SIX
CONFIGURATION OF THE 210 WBX MODELS WITH NUAGE

SOFTWARE
• 210 WBX - 32QSFP28 (page 36)

– Chassis (page 36)
– Cards and MDAs (page 38)
– Port Configuration (page 41)
– LAG 97 and LAG 98 (page 42)
• 210 WBX - 48SFP28 6QSFP28 (page 43)
– Chassis (page 43)
– Cards and MDAs (page 44)
– Port Configuration (page 48)
* 25GE Capable Ports (page 48)

* 100GE Capable Ports (page 49)
– LAG 97 and LAG 98 (page 50)
The 210 WBX models have many specific and common configuration steps when running with the Nuage software.
The details are provided in the individual sections.
• 210 WBX - 32QSFP28
• 210 WBX - 48SFP28 6QSFP28
6.1 210 WBX - 32QSFP28
6.1.1 Chassis
210 WBX chassis requires a new personality (personality is also used for management from VSD and VSAP).
To get the details of the chassis,enter the show chassis command. The sample output shows the Type of a 210 WBX
32QSFP28, shows the environment info (five fans) and the power supply info.
*A:210-WBX-32Q# show chassis
===============================================================================
36
Chassis Information
===============================================================================
Name : 210-WBX-32Q
Type : Nuage Networks 210 WBX-32Q
Location :
Coordinates :
CLLI code :
Number of slots : 2
Number of ports : 128
Major LED state : Off
Minor LED state : Off
Over Temperature state : OK
Base MAC address : d0:99:d5:93:0e:41
Virtual Chassis(VC) mode : Disabled
Hardware Data
Part number : Sim Part#
CLEI code : Sim CLEI
Serial number : NS1711T0016
Manufacture date : 01012003
Manufacturing deviations : Sim MfgDeviation wbx210-32q
Manufacturing assembly number : 01-2345-67
Time of last boot : 2017/07/12 01:18:13
Current alarm state : alarm cleared
-------------------------------------------------------------------------------
Environment Information
Number of fan trays : 5

Number of fans : 10
Fan tray number : 1

Speed : half speed
Status : up
Fan tray number : 2

Speed : half speed
Status : up
Fan tray number : 3

Speed : half speed
Status : up
Fan tray number : 4

Speed : half speed
Status : up
Fan tray number : 5

Speed : half speed
Status : up
-------------------------------------------------------------------------------

Status : up

6.1. 210 WBX - 32QSFP28 37

Status : up
===============================================================================
6.1.2 Cards and MDAs
Note: The cards and MDAs in a 210 WBX are different compared to a 7850 VSG.
The 210 WBX 32QSFP28 system has an iom-32-100g (that indicates that it is a 32p 100GE) and an sfm-210-WBX.
*A:210-WBX-32Q# show card
===============================================================================
Card Summary
===============================================================================
Slot Provisioned Type Admin Operational Comments
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 iom-32-100g up up
A sfm-210-WBX up up/active
===============================================================================
The system shows that there are two MDAs, and each MDA has 16 ports 100GE QSFP28
*A:210-WBX-32Q# show mda
===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
-------------------------------------------------------------------------------
1 1 m16-100g-qsfp28 up up
2 m16-100g-qsfp28 up up
===============================================================================
Physically, the numbering of the ports is from left to right, up and down (1 to 32). However, the physical number does
not match the software port numbering. As the Nuage 210 WBX reuses the 7850 VSG Nuage SROS, the software has
been adapted to expand each 100GE physical port into four different ports (a single 100GE can break out into four
different ports), maintaining the concept of IOM cards and MDAs used on VSG.
6.1. 210 WBX - 32QSFP28 38

Fig. 6.1: **210 WBX 32QSFP28 MDAs and Port Numbering*
• Physical port number 1 (upper left in the figure), corresponds to port 1/1/1 (card 1/mda1/port number). If
expanded by configuration with a breakout to 4x25G, or 4x10GE, then ports 1/1/2, 1/1/3, and 1/1/4 become
visible. If expanded by configuration with a breakout of 2x50GE, then only port 1/1/3 becomes visible.
• Physical port number 32 (lower right in the figure), corresponds to port 1/2/61 (card 1/mda1/port number) . If
To see the available ports, enter the show port command. The following example output shows the 32 ports available
(not using breakout configuration):
*A:210-WBX-32Q# show port
===============================================================================
Ports on Slot 1
===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
1/1/1 Up Yes Up 9212 9212 - hybr dotq lgige 40GBASE-CR4
1/1/9 Down No Down 9212 9212 - hybr null cgige
6.1. 210 WBX - 32QSFP28 39


===============================================================================
Ports on Slot A
===============================================================================
-------------------------------------------------------------------------------
A/1 Up Yes Up 1514 1514 - netw null faste MDI
===============================================================================
To verify the front port mapping in SROS, enter the tools dump front-port-to-timos-port command:
*A:210-WBX-32Q# tools dump front-port-to-timos-port

-----------------------------------
Front panel port | TiMOS port
-----------------------------------
1 | 1/1/1
2 | 1/1/5
3 | 1/1/9
4 | 1/1/13
5 | 1/1/17
6 | 1/1/21
7 | 1/1/25
8 | 1/1/29
9 | 1/1/33
10 | 1/1/37
11 | 1/1/41
12 | 1/1/45
13 | 1/1/49
14 | 1/1/53
15 | 1/1/57
16 | 1/1/61
17 | 1/2/1
18 | 1/2/5
19 | 1/2/9
20 | 1/2/13
21 | 1/2/17
22 | 1/2/21
23 | 1/2/25
24 | 1/2/29
25 | 1/2/33
26 | 1/2/37
27 | 1/2/41
28 | 1/2/45
29 | 1/2/49
30 | 1/2/53
6.1. 210 WBX - 32QSFP28 40

31 | 1/2/57
32 | 1/2/61
6.1.3 Port Configuration
The 210 WBX 32QSFP28 supports 32 ports QSFP28/QSFP+, and each port is individually configurable as 100GE,
50GE, 40GE, 2x50GE, 4x25GE or 4x10GE. The media-mode keyword defines port-type. The default is 100G.
*A:210-WBX-32Q#configure port ethernet media-mode

- media-mode {4x10G|4x25G|40G|50G|2x50G|100G}
- no media-mode
<4x10G|4x25G|40G|5*> : 4x10G|4x25G|40G|50G|2x50G|100G
When you enter the show port command to check the Port Type, depending on the media-mode, the Port Type
automatically changes to show the following:
• 100 GE = cgige
• 50 GE = lgige
• 40 GE = xlgige
• 25 GE = xxvge
• 10 GE = xgige
Each port has 4 LEDs, one per port and show the port configuration and speed based on the color.
Fig. 6.2: **210 WBX 32QSFP28 LEDs per Port*
6.1. 210 WBX - 32QSFP28 41

Table 6.1: 210 WBX 32QSFP28 LED Status Descriptions

LEDs Status Descriptions
LED 1
• Green - 100G operation
• Amber - 40G operation
• White - 50G operation
• Blue - 25G operation
• Purple - 10G operation
• Off - No Link
LED 2 - Working in breakout only

• Blue 25G operation
• Purple 10G operation
• Off 40G/100G operation (Assuming LED 1 is il-
luminated) or No Link

• White - 50G operation
• Blue - 25G operation
• Purple - 10G operation
• Off - 40G/100G operation (Assuming LED 1 is
illuminated) or No Link

• Blue 25G operation
• Purple 10G operation
Note: No link: Off / Linkup: Solid, LED / Traffic: Flashing
6.1.4 LAG 97 and LAG 98
LAG 97 and LAG 98 are configured by default in any VSG or 210 WBX.
• LAG 97 is used for the internal loop used when the system is configured as an L3 HW VTEP
• LAG 98 is used for the inter chassis (IC) connectivity when configuring MC-LAG
Note: For more info about MC-LAG, see the “Multichassis Link Aggregation Group” section in the Nuage VSP User
Guide.
LAG 97 (L3 loop) has no ports configured by default.
*A:210-WBX-32Q# configure lag 97

*A:210-WBX-32Q>config>lag# info
----------------------------------------------
description "System Loopback LAG"
encap-type dot1q
no shutdown
----------------------------------------------
6.1. 210 WBX - 32QSFP28 42

However, any port could be provisioned in the LAG 97. No real loop is needed (no external cables), loop is internal
but port cannot be used for anything else.
By default, LAG 98 (IC) has no ports configured either.
*A:210-WBX-32Q>config# lag 98
*A:210-WBX-32Q>config>lag# info
----------------------------------------------
description "Multichassis interconnect LAG"
encap-type dot1q
lacp active administrative-key 36864
no shutdown
----------------------------------------------
However, any port can be provisioned in the LAG 98. Note that in this case, cables are needed to interconnect both
MC-LAG nodes.
6.2 210 WBX - 48SFP28 6QSFP28
6.2.1 Chassis
210 WBX chassis requires a new personality (personality is also used for management from VSD and VSAP).
To get the details of the chassis, enter the **show chassis ** command. The following output shows the Type of a 210
WBX 48SFP28 6QSFP28, shows the environment info (four fans) and the power supply information.
*A:210-WBX-48S# show chassis
===============================================================================
Chassis Information
===============================================================================
Name : 210-WBX-48S
Type : Nuage Networks 210 WBX-48S
Location :
Coordinates :
CLLI code :
Number of slots : 2
Number of ports : 86
Major LED state : Off
Minor LED state : Off
Over Temperature state : OK
Base MAC address : d0:99:d5:95:12:41
Virtual Chassis(VC) mode : Disabled
Hardware Data
Part number : Sim Part#
CLEI code : Sim CLEI
Serial number : NS1712T0021
Manufacture date : 01012003
Manufacturing deviations : Sim MfgDeviation wbx210-48s
Manufacturing assembly number : 01-2345-67
Time of last boot : 2017/02/09 10:50:04
Current alarm state : alarm cleared
-------------------------------------------------------------------------------
Environment Information
Number of fan trays : 4
6.2. 210 WBX - 48SFP28 6QSFP28 43

Number of fans : 8
Fan tray number : 1

Speed : half speed
Status : up
Fan tray number : 2

Speed : half speed
Status : up
Fan tray number : 3

Speed : half speed
Status : up
Fan tray number : 4

Speed : half speed
Status : up
-------------------------------------------------------------------------------

Status : up

Status : up
===============================================================================
6.2.2 Cards and MDAs
Note: The cards and MDAs in a 210 WBX are different compared to a 7850 VSG.
The 210 WBX 48SFP28 6QSFP28 system has an iom-48-25g+6-100g (that indicates that it is a 48 ports 25GE and 6
ports 100GE) and an sfm-210-WBX2.
*A:210-WBX-48S# show card
===============================================================================
Card Summary
===============================================================================
Slot Provisioned Type Admin Operational Comments
-------------------------------------------------------------------------------
1 iom-48-25g+6-100g up up
A sfm-210-WBX2 up up/active
===============================================================================
The system shows there are three MDAs. The first MDA contains the 48 ports 25GE SFP28, the second MDA contains
the 6 ports 100GE QSFP28, and in the third MDA there are the 14 internal 100GE ports (to be used in LAG97)
*A:210-WBX-48S# show mda
6.2. 210 WBX - 48SFP28 6QSFP28 44

===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
-------------------------------------------------------------------------------
1 1 m48-25g-sfp28 up up
2 m6-100g-qsfp28 up up
3 m14-100g-internal up up
================================================================================
Physically, the numbering of the ports is from left to right, up and down (1 to 54). However, the physical number does
not match the software port numbering. As the Nuage 210 WBX reuses the 7850 VSG Nuage SROS, the software has
been adapted to expand each 100GE physical port into four different ports (a single 100GE can break out into four
different ports), maintaining the concept of IOM cards and MDAs used on VSG.
Fig. 6.3: **210 WBX 48SFP28 6QSFP28 MDAs and Port Numbering*
• Any SFP port numbers from 1 to 48, corresponding to 1/1/[1..48] (card1, mda1/port number).
• Physical port number 49 (first 100GE capable port), corresponds to port 1/2/1 (card 1/mda2/port number) . If
• Physical port number 54 (lower right in the drawing and last 100GE capable port), corresponds to port 1/2/21
(card 1/mda2/port number) . If expanded by configuration with a breakout to 4x25G, or 4x10GE, then ports
1/2/22, 1/2/23, and 1/2/24 become visible. If expanded by configuration with a breakout of 2x50GE, then only
port 1/2/23 becomes visible.
To see the available ports, enter the show ports command. The following example output shows the 54 available ports
(not using breakout configuration) split in MDA1 and MDA2. MDA3 corresponds to LAG 97 (read LAG97 section
for more details).
*A:210-WBX-48S# show port
===============================================================================
Ports on Slot 1
===============================================================================
6.2. 210 WBX - 48SFP28 6QSFP28 45


-------------------------------------------------------------------------------
1/1/1 Up Yes Up 9212 9212 - hybr dotq xgige GIGE-CX
1/1/2 Down No Down 9212 9212 - hybr null xgige
1/1/5 Down No Down 9212 9212 - hybr null xxvgige
1/2/5 Up Yes Up 9212 9212 - hybr dotq xlgige 40GBASE-CR4
1/3/1 Up Yes Up 9212 9212 97 hybr dotq cgige
6.2. 210 WBX - 48SFP28 6QSFP28 46


===============================================================================
Ports on Slot A
===============================================================================
-------------------------------------------------------------------------------
A/1 Up Yes Up 1514 1514 - netw null faste MDI
===============================================================================
To verify the front port mapping in SROS, enter the tools dump front-port-to-timos-port command:
*A:210-WBX-48S# tools dump front-port-to-timos-port

-----------------------------------
Front panel port | TiMOS port
-----------------------------------
1 | 1/1/1
2 | 1/1/2
3 | 1/1/3
4 | 1/1/4
5 | 1/1/5
6 | 1/1/6
7 | 1/1/7
8 | 1/1/8
9 | 1/1/9
10 | 1/1/10
11 | 1/1/11
12 | 1/1/12
13 | 1/1/13
14 | 1/1/14
15 | 1/1/15
16 | 1/1/16
17 | 1/1/17
18 | 1/1/18
19 | 1/1/19
20 | 1/1/20
21 | 1/1/21
22 | 1/1/22
23 | 1/1/23
24 | 1/1/24
25 | 1/1/25
26 | 1/1/26
27 | 1/1/27
28 | 1/1/28
29 | 1/1/29
30 | 1/1/30
6.2. 210 WBX - 48SFP28 6QSFP28 47

31 | 1/1/31
32 | 1/1/32
33 | 1/1/33
34 | 1/1/34
35 | 1/1/35
36 | 1/1/36
37 | 1/1/37
38 | 1/1/38
39 | 1/1/39
40 | 1/1/40
41 | 1/1/41
42 | 1/1/42
43 | 1/1/43
44 | 1/1/44
45 | 1/1/45
46 | 1/1/46
47 | 1/1/47
48 | 1/1/48
49 | 1/2/1
50 | 1/2/2
51 | 1/2/3
52 | 1/2/4
53 | 1/2/5
54 | 1/2/6
55 | 1/2/7
56 | 1/2/8
57 | 1/2/9
58 | 1/2/10
59 | 1/2/11
60 | 1/2/12
61 | 1/2/13
62 | 1/2/14
63 | 1/2/15
64 | 1/2/16
6.2.3 Port Configuration
The 210 WBX 48SFP28 6QSFP28 supports:

• 48 ports SFP28, SFP+, or SFP, and each port is individually configurable as 25GE, 10GE, or 1GE.
• 6 ports QSFP28 or QSFP+, and each port is individually configurable as 100GE, 50GE, 40GE, or 2x50GE,
4x25GE and 4x10GE if breakout configuration. The media-mode keyword defines port-type.
25GE Capable Ports
The default is 4x25GE capable ports. The physical ports 1-48 by default are 25GE.
The media-mode defines port-type: default 4x25G The speed defines port-speed: default 25000
*A:210-WBX-48S#configure port ethernet media-mode

- no media-mode
<4x10G|4x25G|40G|5*> : 4x10G|4x25G|40G|50G|2x50G|100G
6.2. 210 WBX - 48SFP28 6QSFP28 48

Ports can be configured as 25GE (default) or 10GE using media-mode. However, ports are gathered by banks of
four ports. To change the port speed per bank of four to 10GE, the first significant port should be configured to be
media-mode 4x10GE:
*A:210-WBX-48S#config port ethernet media-mode 4x10G
Then the corresponding four ports are converted as 10GE ports.

Both 25GE and 10GE ports can be individually provisioned as 1GE configuring speed-media 1000:
*A:210-WBX-48S#config port ethernet speed

- speed {1000|10000|25000}
<1000|10000|25000> : keywords
100GE Capable Ports
The physical ports 49-54 by default are 100GE media-mode defines port-type: default 100G
*A:210-WBX-48S#configure port ethernet media-mode

- no media-mode
<4x10G|4x25G|40G|5*> : 4x10G|4x25G|40G|50G|2x50G|100G
When you enter the show port command to check the Port Type, depending on the media-mode, the Port Type
automatically changes to show the following:
• 100 GE = cgige
• 50 GE = lgige
• 40 GE = xlgige
• 25 GE = xxvge
• 1 GE = xgige
6.2. 210 WBX - 48SFP28 6QSFP28 49

Table 6.2: 210 WBX 48SFP28 6QSFP28 LED Status Descriptions

LEDs Status Descriptions
LED 1
• Off - No Link

• Green 25G operation
• Amber 10G operation

• Off - 40G/100G operation (Assuming LED 1 is
illuminated) or No Link

• Green 25G operation
• Amber 10G operation
Note: No link: Off / Linkup: Solid, LED / Traffic: Flashing
6.2.4 LAG 97 and LAG 98
LAG 97 and LAG 98 are configured by default in any VSG or 210 WBX.
• LAG 97 is used for the internal loop used when the system is configured as an L3 HW VTEP
• LAG 98 is used for the inter chassis (IC) connectivity when configuring MC-LAG
Note: For more info about MC-LAG, see the “Multichassis Link Aggregation Group” section in the Nuage VSP User
Guide.
LAG 97 (L3 loop) has all MDA3 ports configured by default.
*A:210-WBX-48S# configure lag 97

*A:210-WBX-48S>config>lag# info
----------------------------------------------
description "System Loopback LAG"
encap-type dot1q
port 1/3/1
port 1/3/2
port 1/3/3
6.2. 210 WBX - 48SFP28 6QSFP28 50

port 1/3/4
port 1/3/5
port 1/3/6
port 1/3/7
port 1/3/8
port 1/3/9
port 1/3/10
port 1/3/11
port 1/3/12
port 1/3/13
port 1/3/14
no shutdown
----------------------------------------------
No real loop is needed (no external cables), loop is internal but ports cannot be used for anything else.
By default, LAG 98 (IC) has no ports configured either.
*A:210-WBX-48S>config# lag 98
*A:210-WBX-48S>config>lag# info
----------------------------------------------
description "Multichassis interconnect LAG"
encap-type dot1q
lacp active administrative-key 36864
no shutdown
----------------------------------------------
However, any port can be provisioned in the LAG 98. Note that in this case, cables are needed to interconnect both
MC-LAG nodes.
6.2. 210 WBX - 48SFP28 6QSFP28 51

CHAPTER
SEVEN
APPENDIX
• Installation Trace Example from the SD card (page 52)
7.1 Installation Trace Example from the SD card
Note: The following output is an example and should be used only as a reference because the output may vary based
on the Nuage 210 WBX software release.
Booting ÒNIE: Install OS'

Welcome to GRUB!
ONIE: OS Install Mode ...
Version : 2016.02
Build Date: 2017-02-08T17:09+0800
Info: Mounting kernel filesystems... done.
Info: Mounting ONIE-BOOT on /mnt/onie-boot ...
Installing for i386-pc platform.
Installation finrandom: mktemp urandom read with 19 bits of entropy available
ished. No error reported.
Info: Using eth0 MAC address: d0:99:d5:95:12:41
Info: eth0: Checking link... scsi 6:0:0:0: Direct-Access Generic STORAGE DEVICE
˓→ 0903 PQ: 0 ANSI: 6
sd 6:0:0:0: [sdb] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or
˓→FUA
sd 6:0:0:0: [sdb] Attached SCSI removable disk

down.
ONIE: eth0: link down. Skipping configuration.
ONIE: Failed to configure eth0 interface
Starting: dropbear ssh daemon... done.
Starting: telnetd... done.
discover: installer mode detected. Running installer.
Starting: discover... done.
Please press Enter to activate this console. Info: eth0: Checking link... down.
ONIE: eth0: link down. Skipping configuration.
ONIE: Failed to configure eth0 interface
52
ONIE: Starting ONIE Service Discovery

EXT2-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
random: nonblocking pool is initialized
EXT2-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
ONIE: Executing installer: file://dev/sdb1/onie-installer-x86_64
*** Nuage 210-WBX Installer script 5.0.2_28 ***
Setting eth0 MAC from syseeprom: D0:99:D5:95:12:41 - Change MAC Done
Found 2 devices: sda sdb
sdb Non-Internal Storage detected
Install Device set to /dev/sda
Install Device /dev/sda is of 125045424 sectors, size 59.6 GiB
Last installed partition detected = 2
Removing any non-ONIE/non-VSGX partitions
Partition ONIE-BOOT is either ONIE or VSGX
Partition GRUB-BOOT is either ONIE or VSGX
No existing Root Partion found for vsgx; Creating ROOT partition
Found last partition: INSTALL_LAST_PART="2"
Last partition set to="2"
Creating new partion VSGX-ROOT on /dev/sda3
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
No exisiting persistant data partition foud, creating new data partition
Creating new partion VSGX-DATA on /dev/sda4
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: done
Filesystem label=VSGX-DATA
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2097152 inodes, 8388433 blocks
419421 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
256 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624
Allocating group tables: done

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Extracting image. This will take some time...

0+292768 records in
0+292768 records out
2056224768 bytes (1.9GB) copied, 69.974810 seconds, 28.0MB/s
Image extraction complete. Running fsck to prepare for filesystem resizing...
fsck 1.42.8 (20-Jun-2013)
e2fsck 1.42.8 (20-Jun-2013)
Superblock last mount time (Thu Jul 6 04:32:03 2017,
7.1. Installation Trace Example from the SD card 53

now = Thu Feb 9 10:03:53 2017) is in the future.

Fix? yes
Superblock last write time (Thu Jul 6 04:40:48 2017,

now = Thu Feb 9 10:03:53 2017) is in the future.
Fix? yes
Pass 1: Checking inodes, blocks, and sizes
[ 5.135001] i8042: No controller found

[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
[ OK ] Found device M.2__S42__3ME2 VSGX-ROOTFS.
Starting File System Check on /dev/sda3...
[ OK ] Started File System Check on /dev/sda3.
[ OK ] Started dracut initqueue hook.
Starting dracut pre-mount hook...
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[ OK ] Started dracut pre-mount hook.
Mounting /sysroot...
[ OK ] Mounted /sysroot.
[ OK ] Reached target Initrd Root File System.
Starting Reload Configuration from the Real Root...
[ OK ] Started Reload Configuration from the Real Root.
[ OK ] Reached target Initrd File Systems.
[ OK ] Reached target Initrd Default Target.
Starting dracut pre-pivot and cleanup hook...
[ OK ] Started dracut pre-pivot and cleanup hook.
Starting Cleaning Up and Shutting Down Daemons...
Starting Plymouth switch root service...
[ OK ] Stopped target Timers.
[ OK ] Stopped Cleaning Up and Shutting Down Daemons.
[ OK ] Stopped dracut pre-pivot and cleanup hook.
Stopping dracut pre-pivot and cleanup hook...
[ OK ] Stopped target Initrd Default Target.
[ OK ] Stopped dracut pre-mount hook.
Stopping dracut pre-mount hook...
[ OK ] Stopped target Remote File Systems.
[ OK ] Stopped target Remote File Systems (Pre).
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Slices.
[ OK ] Stopped target Paths.
[ OK ] Stopped target Sockets.
[ OK ] Closed Open-iSCSI iscsiuio Socket.
[ OK ] Stopped target System Initialization.
[ OK ] Stopped target Local File Systems.
[ OK ] Stopped Apply Kernel Variables.
Stopping Apply Kernel Variables...
[ OK ] Stopped target Swap.
[ OK ] Stopped target Encrypted Volumes.
[ OK ] Stopped dracut initqueue hook.
Stopping dracut initqueue hook...
[ OK ] Stopped udev Coldplug all Devices.
Stopping udev Coldplug all Devices...

[ OK ] Stopped dracut pre-trigger hook.

Stopping dracut pre-trigger hook...
Stopping udev Kernel Device Manager...
Stopping Open-iSCSI...
[ OK ] Stopped udev Kernel Device Manager.
[ OK ] Stopped dracut pre-udev hook.
Stopping dracut pre-udev hook...
[ OK ] Stopped
Welcome to CentOS Linux 7 (Core)!
[ OK ] Stopped Switch Root.

[ OK ] Listening on udev Control Socket.
[ OK ] Reached target Swap.
[ OK ] Created slice User and Session Slice.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on LVM2 poll daemon socket.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Listening on Device-mapper event daemon FIFOs.
Mounting Huge Pages File System...
[ OK ] Set up automount Arbitrary Executab...ats File System Automount Point.
[ OK ] Reached target Slices.
[ OK ] Reached target Encrypted Volumes.
Mounting POSIX Message Queue File System...
[ OK ] Listening on LVM2 metadata daemon socket.
Starting Monitoring of LVM2 mirrors... dmeventd or progress polling...
[ OK ] Stopped Journal Service.
Starting Journal Service...
Mounting NFSD configuration filesystem...
Starting Create list of required st... nodes for the current kernel...
[ OK ] Listening on Delayed Shutdown Socket.
Mounting Debug File System...
Starting Collect Read-Ahead Data...
[ OK ] Created slice system-getty.slice.
[ OK ] Stopped target Switch Root.
[ OK ] Stopped target Initrd Root File System.
[ OK ] Stopped target Initrd File Systems.
[ OK ] Started Collect Read-Ahead Data.
Starting Remount Root and Kernel File Systems...
Starting Load Kernel Modules...
[ OK ] Started Create list of required sta...ce nodes for the current kernel.
Starting Create Static Device Nodes in /dev...
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Huge Pages File System.
[ OK ] Mounted Debug File System.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Journal Service.
Starting Load/Save Random Seed...
Starting Configure read-only root support...
Starting Flush Journal to Persistent Storage...
Starting Rebuild Hardware Database...
[ OK ] Started LVM2 metadata daemon.
Starting LVM2 metadata daemon...
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Load Kernel Modules.
Starting Apply Kernel Variables...
[ OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...

[ OK ] Started Flush Journal to Persistent Storage.

[ OK ] Mounted NFSD configuration filesystem.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Configure read-only root support.
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Rebuild Hardware Database.
Starting udev Coldplug all Devices...
[ OK ] Started udev Coldplug all Devices.
[ OK ] Found device /dev/ttyS0.
[ OK ] Found device M.2__S42__3ME2 VSGX-DATA.
[ OK ] Found device M.2__S42__3ME2 ONIE-BOOT.
[ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress polling.
[ OK ] Reached target Local File Systems (Pre).
Mounting /vsgx-data...
Mounting /onie-boot...
[ OK ] Mounted /onie-boot.
[ OK ] Mounted /vsgx-data.
[ OK ] Reached target Local File Systems.
Starting Mark the need to relabel after reboot...
Starting Preprocess NFS configuration...
Starting Tell Plymouth To Write Out Runtime Data...
Starting Rebuild Journal Catalog...
Starting Import network configuration from initramfs...
[ OK ] Started Mark the need to relabel after reboot.
[ OK ] Started Preprocess NFS configuration.
[ OK ] Started Rebuild Journal Catalog.
Starting Update is Completed...
[ OK ] Started Update is Completed.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Import network configuration from initramfs.
Starting Create Volatile Files and Directories...
[ OK ] Started Create Volatile Files and Directories.
Starting Security Auditing Service...
[ OK ] Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Listening on Virtual machine log manager socket.
[ OK ] Listening on Virtual machine lock manager socket.
[ OK ] Reached target Paths.
[ OK ] Reached target Timers.
[ OK ] Listening on Open-iSCSI iscsiuio Socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ OK ] Listening on Open-iSCSI iscsid Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting OpenSSH Server Key Generation...
Starting NTP client/server...
Starting Initial cloud-init job (pre-networking)...
[ OK ] Started Nuage VSG-X Boot Message.
Starting Nuage VSG-X Boot Message...
Starting GSSAPI Proxy Daemon...
[ OK ] Started irqbalance daemon.
Starting irqbalance daemon...
Starting Dump dmesg to /var/log/dmesg...
[ OK ] Started ABRT Automated Bug Reporting Tool.
Starting ABRT Automated Bug Reporting Tool...

Starting Install ABRT coredump hook...

[ OK ] Started ABRT kernel log watcher.
Starting ABRT kernel log watcher...
Starting Kernel Samepage Merging...
Starting Load CPU microcode update...
Starting Resets System Activity Logs...
Starting Authorization Manager...
[ OK ] Started D-Bus System Message Bus.
Starting D-Bus System Message Bus...
Starting Login Service...
[ OK ] Started GSSAPI Proxy Daemon.
[ OK ] Started Dump dmesg to /var/log/dmesg.
[ OK ] Started Kernel Samepage Merging.
[ OK ] Started Load CPU microcode update.
[ OK ] Started Resets System Activity Logs.
Starting Kernel Samepage Merging (KSM) Tuning Daemon...
[ OK ] Reached target NFS client services.
[ OK ] Started NTP client/server.
[ OK ] Started Kernel Samepage Merging (KSM) Tuning Daemon.
[ OK ] Started Login Service.
[ OK ] Started Install ABRT coredump hook.
[ OK ] Started Authorization Manager.
Starting firewalld - dynamic firewall daemon...
[ OK ] Started OpenSSH Server Key Generation.
[ 9.057137] cloud-init[800]: Cloud-init v. 0.7.5 running 'init-local' at Thu, 09
˓→Feb 2017 10:04:31 +0000. Up 9.02 seconds.
[ OK ] Started Initial cloud-init job (pre-networking).

[ OK ] Started firewalld - dynamic firewall daemon.
Starting Network Manager...
[ OK ] Started Network Manager.
Starting Network Manager Wait Online...
Starting Network Manager Script Dispatcher Service...
[ OK ] Started Network Manager Script Dispatcher Service.
Starting Hostname Service...
[ OK ] Started Hostname Service.
[ 15.926440] cloud-init[1142]: Cloud-init v. 0.7.5 running 'init' at Thu, 09 Feb
˓→2017 10:04:38 +0000. Up 15.88 seconds.
[ 15.967788] cloud-init[1142]: ci-info: ++++++++++++++++++++++++Net device

˓→info+++++++++++++++++++++++++
[ 15.968092] cloud-init[1142]: ci-info: +-----------+------+-----------+-----------

˓→+-------------------+
[ 15.968301] cloud-init[1142]: ci-info: | Device | Up | Address | Mask

˓→| Hw-Address |
˓→+-------------------+
[ 15.968705] cloud-init[1142]: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0

˓→| . |
[ 15.968896] cloud-init[1142]: ci-info: | enp5s0f0: | True | . | .
˓→| 00:a0:c9:00:00:00 |
[ 15.969094] cloud-init[1142]: ci-info: | ens1: | True | . | .

˓→| d0:99:d5:95:12:41 |
[ 15.969284] cloud-init[1142]: ci-info: | enp5s0f1: | True | . | .

˓→| 34:12:78:56:01:00 |

˓→+-------------------+
[ 15.969685] cloud-init[1142]: ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info

˓→failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Nuage 210-WBX 5.0.2-28

localhost login: [ 16.971194] cloud-init[1522]: Cloud-init v. 0.7.5 running
˓→'modules:config' at Thu, 09 Feb 2017 10:04:39 +0000. Up 16.91 seconds.
[ 17.287023] cloud-init[1573]: Cloud-init v. 0.7.5 running 'modules:final' at Thu,

˓→09 Feb 2017 10:04:39 +0000. Up 17.22 seconds.
ci-info: no authorized ssh keys fingerprints found for user centos.

[ 17.316134] cloud-init[1573]: ci-info: no authorized ssh keys fingerprints found
˓→for user centos.
ec2:
ec2: #############################################################
ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
ec2: 256 3a:d6:ac:51:b5:95:31:0c:01:f9:9b:05:6d:b2:62:1f (ECDSA)
ec2: 256 85:f2:46:ca:69:94:12:0a:c0:34:9f:7f:b1:73:c8:c6 (ED25519)
ec2: 2048 60:9c:59:50:89:64:56:c2:93:09:70:95:76:df:4e:9f (RSA)
ec2: -----END SSH HOST KEY FINGERPRINTS-----
ec2: #############################################################
-----BEGIN SSH HOST KEY KEYS-----
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBD7rN/
˓→FD4PJIqfpnfaMLrL/ToHD35gcz+3Ufsq3PCEQcomuD0wtJwLRXooXykmMt1bffp/R9A+3UCU/Q0RFasdI=
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOqL3mnHx/IkQb36Gv60epPGyy6u7YdwHKqVn9v2VQme
ssh-rsa
˓→AAAAB3NzaC1yc2EAAAADAQABAAABAQC3IMOOe+2vl9FfMYeulY6TpaNSfmimlcZ341cI4HzzY1UZfPIuSkiBEPgCg1MI0yxHMnr
v8/F/
˓→AzjhYCBIcCggHhrn9EkJdFbaQPWu39pmyQTi6BW1RaN9GIbqn4bcqt9WFtLgZdKTDb+BQq99+oE4mG99NGJd/
˓→FcnWCZiuUU79QDvz7LLGgu3jCD+bYnFu2QdCBWgprz7F7ENdkAsH7JZS2A3ANmR0EXBX1GNbCGeHjnRfKNR86xoYx9srfT
kIeeTHVyfQmd
-----END SSH HOST KEY KEYS-----
[ 17.345404] cloud-init[1573]: Cloud-init v. 0.7.5 finished at Thu, 09 Feb 2017 10:
˓→04:39 +0000. Datasource DataSourceNone. Up 17.34 seconds
Nuage 210-WBX 5.0.2-28

localhost login:

210 WBX Software Installation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

210 WBX Software Installation Guide

Uploaded by

Copyright:

Available Formats

210 WBX Software Installation Guide

November 01, 2017

1 About this Document 2

3 Nuage Software Installation 7

4 Getting Started with the Nuage 210 WBX 16

5 Nuage SROS for 210 WBX 23

6 Configuration of the 210 WBX Models with Nuage Software 36

NUAGE NETWORKS – PROPRIETARY & CONFIDENTIAL

Copyright©2017 Nokia Corporation / Nuage Networks. All rights reserved.

ABOUT THIS DOCUMENT

• Validity of this Document (page 3)

1.1 Validity of this Document

1.3 Technical Support

1.4 Required Documents

1.1. Validity of this Document 3

• 210 WBX Overview (page 4)

2.1 210 WBX Overview

2.1.1 210 WBX 32QSFP28

Fig. 2.1: 210 WBX 32QSFP28 Front Panel

Table 2.1: 210 WBX 32QSFP28

Fig. 2.2: 210 WBX 32QSFP28 Rear Panel

Table 2.2: 210 WBX 32QSFP28 Rear

2.1.2 210 WBX 48SFP28 6QSFP28

Fig. 2.3: 210 WBX 48SFP28 6QSFP28 Front Panel

2.1. 210 WBX Overview 5

Table 2.3: 210 WBX 48SFP28

Fig. 2.4: 210 WBX 48SFP28 6QSFP28 Rear Panel

Table 2.4: 210 WBX 48SFP28 6QSFP28 Rear

2.1. 210 WBX Overview 6

NUAGE SOFTWARE INSTALLATION

• Setting Up NOS with ONIE (page 7)

* Boot After the NOS Installation is Complete (page 10)

* nuage_wbx cloud-init Module (page 12)

* cloud-init.cfg (page 13)

3.1 Setting Up NOS with ONIE

3.2 Initializing the System and Downloading Software

3.2.2 Installing NOS From the SD Card

Fig. 3.1: 210 WBX Console Management Port

Note: Install OS option is the default.

3.2. Initializing the System and Downloading Software 8

Fig. 3.2: 210 WBX ONIE Bootup

Booting `ONIE: Install OS'

Note: For the detailed trace example, go to the Appendix.

3.2. Initializing the System and Downloading Software 9

3.2.3 Installing NOS From the Network

Note: An SD card is not required to perform installation from the network.

Fig. 3.3: 210 WBX Ethernet Management Port

Step 2 Copy the NOS Installer Image to the HTTP server.

option default-url "http://<webserver-address>/onie-installer-x86_64"

Note: For details, see the ONIE user guide: https://opencomputeproject.github.io/onie/user-guide/index.html

Boot After the NOS Installation is Complete

3.2. Initializing the System and Downloading Software 10

Fig. 3.4: 210 WBX NOS Bootup

3.3 Automatic NOS Configuration

3.3.1 Configuring OS From the SD Card

3.3.2 Configuring OS From the Network

3.3. Automatic NOS Configuration 11

For example, if the default-url option is set to option default-url

3.3.3 Cloud-init File Format

The cloud-init.cfg must start with the line #cloud-config.

It is possible to execute custom commands at the time of first boot:

It is also possible to configure the ifcfg-mgmt interface:

- 'ifconfig mgmt 10.31.135.121 netmask 255.255.224.0 up'

nuage_wbx cloud-init Module