Open Netvisor Linux - Pluribus Networks

Open Netvisor® Linux Getting Started Guide

January 2016

pluribusnetworks.com/dell 1

Table of Contents

Introduction 2Hardware Installation 3

Pluribus Networks Cloud Functions 4

Download Activation Keys for Offline Provisioning 6Locating the Service Tag 7

Software Installation 8

Offline Provisioning 9Post Installation Configuration 10

Submitting a Service Request 11

Appendix: Log Messages 12


Introduction Pluribus Networks advances software-defined networking (SDN) through Open Netvisor Linux (ONVL), the industry’s most programmable, open source-based network operating system. ONVL is based on a highly available, scalable, controller-less architecture to provide visibility, telemetry, security and dramatic operational simplification.

Pluribus ONVL combines the benefits of Linux with a controller-less fabric. The traditional CLI (Command Line Interface) is paired with fabric-wide programmability (via C API) and DevOps tools (e.g. Ansible) for agility and automation via a single point of management. Granular visibility and control is through a fabric-wide directory that contains endpoint information (vPorts) as well as allows for granular flow filtering and control (vFlow).

The Dell Open Networking (ON) Ethernet Switches, based on the latest generation chipsets from Broadcom, are designed to implement extremely cost effective, non-blocking, pay-as-you-grow leaf-spine architecture with predictable low-latency, thus dramatically improving workload management and network agility.

In combination with the Dell ON switching portfolio, ONVL provides best-in-class switching economics. The deployment flexibility is guaranteed by Pluribus ONVL full L2/L3 stack providing complete interoperability with the legacy networking infrastructure, allowing for easy insertion into brownfield deployments.

This document describes the steps needed to get ONVL installed on your Dell ON equipment and ready for further configuration. The procedures described in this guide provide general outlines and some specific details. For more detailed information, other documents are referenced.

The overall procedure follows steps shown here, details follow in this document:

1. Purchase Dell Open Networking hardware and Pluribus Networks Open Netvisor Linux software from the Dell Download Store: a. Dell sends an email confirmation of the purchase b. Pluribus Networks sends an email confirmation of the purchase, plus:

i. Pluribus Networks Cloud account information ii. Instructions to download ONVL ONIE (install) image

2. Receive Dell Open Networking switches and note the Dell service tag number for each switch 3. Connect to the Pluribus Networks Cloud website (cloud.pluribusnetworks.com) using account information:

a. Download ONVL ONIE image (file name: onie-installer) b. Activate device using Dell service tag identifier

i. If the device will have Internet access during installation, continue to step4 ii. If the device will not have Internet access during installation, download activation keys file

(file name: onvl-activation-keys) 4. Complete hardware installation. 5. Install ONVL ONIE image on Dell ON switches 6. Provisioning proceeds after ONVL installation

a. If the device has Internet access, provisioning is automatic (online provisioning) b. If the device does not have Internet access, provide Activation Keys downloaded earlier (offline provisioning)


Hardware Installation The hardware installation procedures are described in the Dell Open Networking Getting Started Guide. See references below. The steps described in this section prepare the hardware for ONVL installation.

The hardware installation procedures in the following Dell documentation include the steps necessary to complete the following tasks:

1. Understand safety considerations. 2. Unpacking the switch. 3. Rack mounting the switch. 4. Power up the switch.

Dell Networking S4048-ON & S6000-ON Getting Started Guide Use the following documentation to complete the hardware installation.

NOTE: The serial port settings needed to view messages on the console port: • - 115200Data bits - 8 • Stop bits - 1 • Parity - n

S4048-ON:

http://www.dell.com/support/manuals/us/en/19/Topic/force10-s4048-on/S4048_ON_GSG_Pub-v1/en-us/GUID-7E4C3BDC-BA59-47C8-B345-4BCA5428AB7A

S6000-ON:

http://downloads.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_networking/esuprt_net_fxd_prt_swtchs/force10-s6000-on_User%27s Guide_en-us.pdf


Pluribus Networks Cloud Functions Instructions to access the Pluribus Networks Cloud (cloud.pluribusnetworks.com) are provided after the purchase of Dell ON equipment. A username and password are required to allow downloading of software and activation keys.

First, login to the Pluribus Networks Cloud website using the credentials provided.


Download ONVL ONIE Image The ONVL ONIE image is available from the current downloads page. Select “CURRENT” from the DOWNLOADS section of the sidebar menu.

Download the software to a local system. Release notes are also available for download. It is recommended that you download and review the release notes before you being the ONVL installation process.


Activate Device Activation begins with the generation of an activation key. Select “ACTIVATIONS” from the sidebar menu. Provide the Dell service tag from the device in the “empty” slot and press “Activate” to generate the activation keys. See the section “Locating the Service Tag” below for details about the Dell service tag. Multiple devices can be activated with a single authorization code (note: the “Auth code” is provided by Pluribus Networks, it is not user generated).

Download Activation Keys for Offline Provisioning Download the activation keys only if the device will not have Internet access during the installation process. If the device is connected to the Internet during the installation process, the activation keys are automatically downloaded.

After the activation key is generated, press the “ACTIVATION KEYS” download button. This will download a file to a local system. This file is named “onvl-activation-keys”. Note: If subsequent devices are activated a new version of the activation keys file will need to be downloaded. A single activation keys file can provide provisioning information for many devices.

Proprietary & Confidential9


Locating the Service Tag The Dell service tag is a seven character identifier that is unique to the device. It is very easy to find the service tag. It is shown on the label of the packaging for the device:

The service tag is also located on the device itself. This example shows the S6000-ON switch, the label is affixed to the top cover of the device:

The service tag can also be found on the order fulfillment paperwork for each of the devices in a given order.

Finally, if a network operating system is already installed on the switch it is possible to execute a command to report the service tag. The following example shows the onie-syseeprom command.

ONIE:/ # onie-syseeprom TlvInfo Header: Id String: TlvInfo Version: 1 Total Length: 150 TLV Name Code Len Value -------------------- ---- --- ----- Part Number 0x22 6 0M68YC *** output truncated *** Manufacturer 0x2B 5 28298 Country Code 0x2C 2 CN Service Tag 0x2F 7 8BRMX42 Vendor Extension 0xFD 6 0x36 0x37 0x34 0x2D 0x46 0x46 Product Name 0x21 8 S4000-ON Platform Name 0x28 26 x86_64-dell_s4000_c2338-r0 Loader Version 0x29 8 3.21.1.1 CRC-32 0xFE 4 0x56CCD005 Checksum is valid.


Software Installation There are two steps to the software installation process: ONVL installation and ONVL provisioning.

The Open Network Installation Environment (ONIE) supports several methods to install ONVL to the hardware. There are simple methods that are convenient for a small number of switches and there are more complicated procedures that provide automation for installation across many switches.

The Open Compute Project publishes a complete guide (https://github.com/opencomputeproject/onie/wiki/Quick-Start-Guide) detailing the installation methods. The following methods are described in the ONIE Quick Start Guide provided by the Open Compute Project:

1. Installing using a USB thumb drive 2. Installing over the network

a. Installing and configuring an HTTP Server b. Copying the ONVL ONIE Image and activation keys to the HTTP Server c. Testing the onvl-installer file download from the HTTP Server

3. Installing using a directly connected web server 4. Installing using an L2 connected web server 5. Installing using a DHCP server (L2 network)

a. Basic b. Domain Name Server

6. Installing using a DHCP server (L3 network)

Other advanced methods and troubleshooting procedures are described in the ONIE Quick Start Guide.

ONVL Installation The ONVL installation procedure is automatic assuming the software installation method chosen is working properly.

The following sample output assumes the ONIE ONVL image (onie-installer) and activation keys (onvl-activation-keys) files are stored on a USB drive that is inserted in the UBS port of the Dell ON switch.

NOTE: The ONVL install image file must be named: onie-installer

ONIE: Starting ONIE Service Discovery ONIE: Executing installer: file://dev/sdb/onie-installer Extracting image Netvisor Installer: platform: dell_s6000_s1220 The operation has completed successfully.


ONVL Provisioning The ONVL provisioning procedure is automatic assuming the ONVL installation procedure worked properly.

If the device has a working Internet connection the provisioning information can be retrieved from the Pluribus Networks update server automatically.

The provisioning process walks through a set of possible locations for the activation keys file (onvl-activation-keys). First, the automatic provisioning procedure tries to contact the Pluribus Networks update server over the Internet. If the device does not have a working Internet connection other local connections are attempted (shown below).

AUTO-PROVISION: looking for the update server... AUTO-PROVISION: [NOT FOUND] AUTO-PROVISION: looking for offline bundle... AUTO-PROVISION: onvl-discover: sftp discovery.... AUTO-PROVISION: onvl-discover: not found AUTO-PROVISION: onvl-discover: usb discovery.... AUTO-PROVISION: onvl-discover: not found AUTO-PROVISION: onvl-discover: dhcp discovery.... AUTO-PROVISION: [NOT FOUND]

Offline Provisioning If the device does not have a working Internet connection, the onvl-activation-keys file is required to complete the provisioning process.

In the following example, the onvl-activation-keys file was discovered on the USB drive that is inserted in the UBS port of the Dell ON switch.

AUTO-PROVISION: onvl-discover: onvl-activation-keys found: /dev/sdb1 AUTO-PROVISION: Extracting initial bundle. AUTO-PROVISION: Decrypting signed bundle. AUTO-PROVISION: Extracting signed bundle. AUTO-PROVISION: Verifying package signature. AUTO-PROVISION: Extracting packages. AUTO-PROVISION: pkgs ready AUTO-PROVISION: onvl-installer: checking for device installer - 8WWMX42/onvl-activation-keys... AUTO-PROVISION: onvl-installer: executing device installer - 8WWMX42/onvl-activation-keys... AUTO-PROVISION: [INSTALLED]

Running Acceptance Tests... test passed comment Total Memory: OK 7.78G Switch device: OK orion found

[GREEN] switch successfully initialized. serial number: 1550ST9100083 hostid: 900011c device id: 8WWMX42 Reboot required.

The device will reboot automatically after the provisioning process is complete as noted in the console messages above.


Post Installation Configuration After installation and activation are complete you can proceed to configure the switches for your network. The Pluribus Networks ONVL Validated Design Guide provides a practical guide to create validated leaf-spine architectures. The Pluribus Networks ONVL Configuration Guide provides an authoritative guide to the many features of ONVL. Basic knowledge of the management CLI is assumed; use the Configuration Guide to review CLI syntax and structure.

The overall procedure to configure ONVL based on the Validated Design Guide is as follows:

1. Review the topology and design considerations a. Redundancy requirements b. IP and VLAN scheme

2. Completing the initial switch setup a. Setup wizard runs automatically upon first login (default login/passwd: pluribus/test123) b. Set the timezone c. Other management interface parameters may need to be configured

3. Creating the ONVL Fabric a. fabric-create command or fabric-join command b. fabric-show command

4. Creating cluster objects between two switches for redundancy a. cluster-create command for spine layer b. cluster-create command for leaf layer

5. Creating virtual link aggregation groups (VLAGs) a. trunk-create command b. vlag-create command

6. Creating and assigning VLANs a. vlan-create command b. vlan-port-add command c. stp-port-modify command (as needed)

7. Creating the vRouters a. Configure virtual router redundancy protocol (VRRP)

i. vrouter-create command ii. vrouter-interface-add command

b. Create L3 interfaces. i. vrouter-interface-add command

c. Configure OSPF routing i. vrouter-ospf-add command ii. vrouter-modify command

Pluribus Networks integrated fabric-wide analytics capabilities are also described in the Validated Design Guide. The following analytics topics are covered:

1. Connection Flow Analytics a. connection-show command b. client-server-stats-show command

2. Packet Capture and Analysis 3. Offline Analysis of Analytics 4. Fabric-wide Interface Statistics 5. VM Visibility


Submitting a Service Request For ONVL software support, you can purchase optional support contracts from your partner, reseller, or Pluribus Networks. Purchasing a support contract from a local partner is sometimes preferred due to geographical or language requirements. Please contract your local partner to better understand the available service programs and pricing. If you purchased a Pluribus FreedomCare maintenance agreement, you can contact Pluribus Networks directly for support requirements.


Appendix: Log Messages The following are sample BIOS and boot messages that you may encounter during the processes described in this document.

BIOS (Dell Inc) Boot Selector S6000-ON (SI) 3.20.0.1 (32-port TE/FG) POST Configuration

CPU Signature 30669 CPU FamilyID=6, Model=36, SteppingId=9, Processor=0 Microcode Revision 10b

POST Control=0xea000303, Status=0xe6009f00 MSRs: Platform ID: f09885b04f

PMG_CST_CFG_CTL: 263006 BBL_CR_CTL3: 7e00010f Perf Ctrl & status: 63d, 63d104f06000648

Perf cnt (curr/fixed): 208c09bc/56cadad0 Clk Flex Max: 0 Misc EN: 60840080

Therm Status: 883c0000 (offset=0x0) MC0 Ctl: 0

MC0 Status: 0

BIOS initializations... POST: RTC Battery ok at last cold boot (0xb)

RTC date Sunday 12/11/2015 18:25:36 POST SPD test ............................... PASS POST Lower DRAM Memory test

SpeedStep enabled, Processor Bus Ratio=10, Vid=53 Short memory cell test Perf cnt (curr/fixed): 24e9e850/24eb4df0

POST Lower DRAM Memory test ................. PASS POST Lower DRAM ECC check ................... PASS || ||

DxE POST

POST Upper DRAM Memory test SpeedStep enabled, Processor Bus Ratio=10, Vid=53

Short memory cell test Perf cnt (curr/fixed): ba3a8c8/ba3abd8 POST Upper DRAM Memory test ................. PASS

POST Upper DRAM ECC check ................... PASS POST PCIe test .............................. PASS POST NVRAM check ............................ PASS

POST overall test results ................... PASS || ||

Version 2.15.1236. Copyright (C) 2012 American Megatrends, Inc.


BIOS Date: 07/09/2014 16:30:33 Ver: 0ACAH015 Press <DEL> or <F2> to enter setup.

|| ||

|| ||

GNU GRUB version 2.02~beta2+e4a1fe391

+----------------------------------------------------------------------------+ |*Netvisor - 2.3.1-203018322 | | ONIE | || || || || || || || || || || +----------------------------------------------------------------------------+

error: can't find command `hwmatch'. Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands

before booting or `c' for a command-line. The highlighted entry will be executed automatically in 0s. || ||

Booting `Netvisor - 2.3.1-203018322' [ * Stopping Send an event to indicate plymouth is up

* Starting Mount filesystems on boot * Starting Populate /dev filesystem * Starting Populate and link to /run filesystem

* Stopping Populate /dev filesystem * Stopping Populate and link to /run filesystem * Stopping Track if upstart is running in a container

* Starting cgroup management daemon * Starting Initialize or finalize resolvconf * Starting FUSE filesystem for LXC

* Stopping cgroup management proxy * Starting set console keymap * Starting Signal sysvinit that virtual filesystems are mounted

* Starting Signal sysvinit that virtual filesystems are mounted * Starting Bridge udev events into upstart * Starting Signal sysvinit that remote filesystems are mounted

2.446952] i8042: No controller found * Starting device node and kernel event manager * Starting FUSE filesystem for LXC

* Stopping FUSE filesystem for LXC * Starting load modules from /etc/modules * Starting cold plug devices

* Starting log initial device creation * Stopping set console keymap * Starting Signal sysvinit that the rootfs is mounted

* Stopping load modules from /etc/modules * Starting Clean /tmp directory * Stopping Clean /tmp directory

* Starting configure network device security * Starting Signal sysvinit that local filesystems are mounted


* Stopping Mount filesystems on boot * Starting flush early job output to logs

* Starting NFSv4 id <-> name mapper * Starting D-Bus system message bus * Stopping flush early job output to logs

* Starting SystemD login management service * Stopping rpcsec_gss daemon * Stopping Read required files in advance

* Starting configure network device security * Stopping cold plug devices * Starting Mount network filesystems

* Starting Upstart job to start rpcbind on boot only * Starting Failsafe Boot Delay * Stopping log initial device creation

* Stopping Upstart job to start rpcbind on boot only * Starting configure network device security * Starting configure network device

* Starting set console font * Stopping set console font * Starting userspace bootsplash

* Stopping userspace bootsplash * Starting Send an event to indicate plymouth is up * Stopping Mount network filesystems

* Stopping Send an event to indicate plymouth is up * Starting configure virtual network devices * Starting RPC portmapper replacement

* Stopping Failsafe Boot Delay * Starting NSM status monitor * Starting System V initialisation compatibility

* Starting configure network device * Starting Bridge socket events into upstart Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd

* Starting Bridge file events into upstart * Starting AppArmor profiles * Setting up X socket directories...

* Stopping System V initialisation compatibility * Starting System V runlevel compatibility * Starting CPU interrupts balancing daemon

* Starting regular background program processing daemon * Starting save kernel messages * Starting OpenSSH server

* Starting Automounter * Starting FUSE filesystem for LXC * Starting lxc network

* Stopping save kernel messages * Starting configure network device security * Starting FUSE filesystem for LXC

* Starting configure network device * Starting FUSE filesystem for LXC


* Starting FUSE filesystem for LXC * Starting FUSE filesystem for LXC

* Starting lxc * Starting FUSE filesystem for LXC * Starting FUSE filesystem for LXC

* Starting FUSE filesystem for LXC * Starting FUSE filesystem for LXC * Starting FUSE filesystem for LXC

* Starting FUSE filesystem for LXC * Stopping FUSE filesystem for LXC [ 10.874082] _alloc_mpool: _dma_vbase:ffff8800af000000 pbase:af000000

allocated:4000000 [ 10.874082] * Starting NTP server ntpd

* Restoring resolver state... 2015-12-11T18:26:04Z|00001|vlog|INFO|opened log file /var/nvOS/log/ovs-vswitchd.log 2015-12-11T18:26:04Z|00002|ovs_numa|INFO|Discovered 2 CPU cores on NUMA node 0

2015-12-11T18:26:04Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 2 CPU cores 2015-12-11T18:26:04Z|00004|reconnect|INFO|unix:/usr/local/var/run/openvswitch/ db.sock: connecting...

2015-12-11T18:26:04Z|00005|reconnect|INFO|unix:/usr/local/var/run/openvswitch/ db.sock: connected Dec11.10:26:04.[WARN]::hw_monitord.c:134:main /usr/sbin/nvOSd_hwmon: Debug level is 2

Dec11.10:26:04.[WARN]::nv_proc.c:47:nv_proc_connect connect: No such file or directory * Starting system logging daemon [ OK ] Dec11.10:26:06.:nvlogger_msgs_logger.c:142:nvlogger_smf_nvOSd_start SMF Service

starting nvOSd Dec11.10:26:06.[WARN]::nvOSd.c:5616:main /usr/sbin/nvOSd: Debug level is 2 /usr/sbin/nvOSd: Debug level is 2

Dec11.10:26:06.:nvOSd.c:5715:main /var/nvOS/etc: Config path = main Dec11.10:26:06.:nvOSd_platform.c:77:nvOS_init_platform_type platform_type: draco kernel.core_pattern = |usr/bin/core-compress.ksh /var/nvOS/log/cores/core %e %p

Dec11.10:26:06.:linux/nvOSd_linux_sys.c:1878:nvOS_os_set_core core set to /var/nvOS/ log/cores not implemented

failed: /usr/local/bin/ovs-vsctl get port eth0 tag failed: /usr/local/bin/ovs-vsctl get port eth0 tag nvOS_user_init: Using default user/password: network-admin/admin

Cannot open /nvOS/iso-images to import factory shipped ISOs resetting cfg_cache /var/nvOS/mirror needs to be updated from the publisher

Fix me Adding switch id (150995230) to logical switch AUTO-PROVISION: looking for the update server...

/etc/rc2.d/S99svc-nvOS-iptables: 54: /etc/rc2.d/S99svc-nvOS-iptables: cannot open / var/nvOS/etc/Local/iptables.conf: No such file start: Failed to restore rules: Return code:

Dec11.10:27:09.[WARN]::nvOS_mon.c:1873:main /usr/sbin/nvOS_mon: Debug level is 2 * Stopping System V runlevel compatibility [ OK ]


Pluribus Networks ONVL OS (DEMO VERSION) draco06 ttyS0 draco06 login: root

Password: Last login: Fri Dec 11 10:24:28 PST 2015 from 10.97.1.22 on pts/0 Welcome to Pluribus Networks Open Netvisor Linux (ONVL) OS - Version: 2.3.1-203018495

(GNU/Linux 3.16.0-34-generic x86_64) * Documentation: http://www.pluribusnetworks.com/support/documentation ***** Reserved by thomas.remahl until Dec. 13, 2015, 11:59 p.m. *****

root@draco06:~# root@draco06:~# AUTO-PROVISION: looking for the update server... uptime

13:26:48 up 3:00, 2 users, load average: 0.43, 0.44, 0.39 AUTO-PROVISION: looking for the update server... AUTO-PROVISION: [NOT FOUND]

AUTO-PROVISION: looking for offline bundle... AUTO-PROVISION: onvl-discover: sftp discovery.... AUTO-PROVISION: onvl-discover: not found

AUTO-PROVISION: onvl-discover: usb discovery.... AUTO-PROVISION: onvl-discover: not found AUTO-PROVISION: onvl-discover: dhcp discovery....

AUTO-PROVISION: [NOT FOUND] [14243.758551] sd 2:0:0:0: [sdb] No Caching mode page found [14243.763910] sd 2:0:0:0: [sdb] Assuming drive cache: write through

AUTO-PROVISION: looking for the update server... AUTO-PROVISION: [NOT FOUND] AUTO-PROVISION: looking for offline bundle...

AUTO-PROVISION: onvl-discover: sftp discovery.... AUTO-PROVISION: onvl-discover: not found AUTO-PROVISION: onvl-discover: usb discovery....

AUTO-PROVISION: onvl-discover: onvl-installer found: /dev/sdb1 AUTO-PROVISION: Extracting initial bundle. AUTO-PROVISION: Decrypting signed bundle.

AUTO-PROVISION: Extracting signed bundle. AUTO-PROVISION: Verifying package signature. AUTO-PROVISION: Extracting packages.

AUTO-PROVISION: pkgs ready AUTO-PROVISION: onvl-installer: checking for device installer - 8WWMX42/onvl- installer...

AUTO-PROVISION: onvl-installer: executing device installer - 8WWMX42/onvl-installer... AUTO-PROVISION: [INSTALLED] Running Acceptance Tests...

test Total Memory: Switch device:

Initializing. Make sure switch is connected to the update server. [GREEN] switch successfully initialized. serial number: 1550ST9100113

hostid: 900011f device id: 8WWMX42


Reboot required. [14279.020406] reboot: Restarting system

passed comment OK 7.78G OK orion found

BIOS (Dell Inc) Boot Selector S6000-ON (SI) 3.20.0.1 (32-port TE/FG) POST Configuration

CPU Signature 30669 CPU FamilyID=6, Model=36, SteppingId=9, Processor=0 Microcode Revision 10b

POST Control=0xea000303, Status=0xe6009f00 MSRs: Platform ID: f09885b04f

PMG_CST_CFG_CTL: 263006 BBL_CR_CTL3: 7e00010f Perf Ctrl & status: 63d, 63d104f06000648

Perf cnt (curr/fixed): 209f0dc6/56fd9040 Clk Flex Max: 0 Misc EN: 60840080

Therm Status: 883b0000 (offset=0x0) MC0 Ctl: 0

MC0 Status: 0

BIOS initializations... POST: RTC Battery ok at last cold boot (0xb)

RTC date Sunday 12/11/2015 22:23:53 POST SPD test ............................... PASS POST Lower DRAM Memory test

SpeedStep enabled, Processor Bus Ratio=10, Vid=53 Short memory cell test Perf cnt (curr/fixed): 24e91b60/24ea8100

POST Lower DRAM Memory test ................. PASS POST Lower DRAM ECC check ................... PASS || ||

DxE POST

POST Upper DRAM Memory test SpeedStep enabled, Processor Bus Ratio=10, Vid=53

Short memory cell test Perf cnt (curr/fixed): ba38a10/ba38b68 POST Upper DRAM Memory test ................. PASS

POST Upper DRAM ECC check ................... PASS POST PCIe test .............................. PASS POST NVRAM check ............................ PASS

POST overall test results ................... PASS || ||


Version 2.15.1236. Copyright (C) 2012 American Megatrends, Inc. BIOS Date: 07/09/2014 16:30:33 Ver: 0ACAH015

Press <DEL> or <F2> to enter setup. || ||

|| ||

GNU GRUB version 2.02~beta2+e4a1fe391 +----------------------------------------------------------------------------+ |*Netvisor - 2.3.1-203018322 | | ONIE | || || || || || || || || || || +-----------------------------

-----------------------------------------------+

error: can't find command `hwmatch'. [ [ [

Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line.

The highlighted entry will be executed automatically in 0s. || ||

Booting `Netvisor - 2.3.1-203018322'

2.459101] i8042: No controller found 4.657776] sd 0:0:0:0: [sdb] No Caching mode page found 4.663190] sd 0:0:0:0: [sdb] Assuming drive cache: write through

* Stopping Send an event to indicate plymouth is up * Starting Mount filesystems on boot * Stopping Track if upstart is running in a container

* Starting cgroup management daemon * Starting Initialize or finalize resolvconf * Starting FUSE filesystem for LXC

* Starting set console keymap * Starting Signal sysvinit that virtual filesystems are mounted * Starting Signal sysvinit that virtual filesystems are mounted

* Starting Bridge udev events into upstart * Starting Signal sysvinit that remote filesystems are mounted * Starting device node and kernel event manager

* Starting FUSE filesystem for LXC * Stopping FUSE filesystem for LXC * Starting load modules from /etc/modules

* Starting cold plug devices * Starting log initial device creation * Stopping cgroup management proxy

* Stopping set console keymap * Starting Signal sysvinit that the rootfs is mounted * Stopping load modules from /etc/modules

* Starting Clean /tmp directory * Stopping Clean /tmp directory * Starting Signal sysvinit that local filesystems are mounted

* Starting configure network device security


* Stopping Mount filesystems on boot * Starting flush early job output to logs

* Starting D-Bus system message bus * Stopping flush early job output to logs * Starting NFSv4 id <-> name mapper

* Starting SystemD login management service * Stopping rpcsec_gss daemon * Stopping Read required files in advance

* Starting configure network device security * Stopping cold plug devices * Stopping log initial device creation

* Starting configure network device * Starting Mount network filesystems * Starting configure network device security

* Starting save udev log and update rules * Starting set console font * Stopping save udev log and update rules

* Stopping set console font * Starting userspace bootsplash * Starting Upstart job to start rpcbind on boot only

* Starting Failsafe Boot Delay * Stopping Upstart job to start rpcbind on boot only * Stopping userspace bootsplash

* Starting Send an event to indicate plymouth is up * Stopping Mount network filesystems * Starting configure virtual network devices

* Stopping Send an event to indicate plymouth is up * Starting RPC portmapper replacement * Stopping Failsafe Boot Delay

* Starting System V initialisation compatibility * Starting NSM status monitor * Starting configure network device

* Starting Bridge socket events into upstart * Starting Bridge file events into upstart Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd

* Starting AppArmor profiles * Setting up X socket directories... * Stopping System V initialisation compatibility

* Starting System V runlevel compatibility * Starting CPU interrupts balancing daemon * Starting OpenSSH server

* Starting regular background program processing daemon * Starting save kernel messages * Starting Automounter

* Starting FUSE filesystem for LXC * Stopping save kernel messages * Starting configure network device security

* Starting lxc network * Starting configure network device


* Starting FUSE filesystem for LXC * Starting FUSE filesystem for LXC

* Starting FUSE filesystem for LXC * Starting FUSE filesystem for LXC * Starting lxc



* Stopping FUSE filesystem for LXC [ 12.312084] _alloc_mpool: _dma_vbase:ffff8800af400000 pbase:af400000 allocated:4000000

[ 12.312084] * Starting NTP server ntpd * Restoring resolver state...

* Starting system logging daemon 2015-12-11T22:24:24Z|00001|vlog|INFO|opened log file /var/nvOS/log/ovs-vswitchd.log 2015-12-11T22:24:24Z|00002|ovs_numa|INFO|Discovered 2 CPU cores on NUMA node 0

2015-12-11T22:24:24Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 2 CPU cores 2015-12-11T22:24:24Z|00004|reconnect|INFO|unix:/usr/local/var/run/openvswitch/ db.sock: connecting...

2015-12-11T22:24:24Z|00005|reconnect|INFO|unix:/usr/local/var/run/openvswitch/ db.sock: connected Dec11.14:24:24.[WARN]::hw_monitord.c:134:main /usr/sbin/nvOSd_hwmon: Debug level is 2

Dec11.14:24:24.[WARN]::nv_proc.c:47:nv_proc_connect connect: No such file or directory Dec11.14:24:27.:nvlogger_msgs_logger.c:142:nvlogger_smf_nvOSd_start SMF Service starting nvOSd

Dec11.14:24:27.[WARN]::nvOSd.c:5616:main /usr/sbin/nvOSd: Debug level is 2 Dec11.14:24:27.:nvOSd.c:5715:main /var/nvOS/etc: Config path = main Dec11.14:24:27.:nvOSd_platform.c:77:nvOS_init_platform_type platform_type: draco

kernel.core_pattern = |usr/bin/core-compress.ksh /var/nvOS/log/cores/core %e %p Dec11.14:24:27.:linux/nvOSd_linux_sys.c:1878:nvOS_os_set_core core set to /var/nvOS/ log/cores

* Starting configure network device security * Starting configure network device * Starting configure network device security

* Starting configure network device security * Starting configure network device security * Starting configure network device

* Stopping OpenSSH server * Starting OpenSSH server * Stopping OpenSSH server

* Starting configure network device * Starting Mount network filesystems * Stopping Mount network filesystems

* Starting OpenSSH server * Starting configure network device


* Starting Mount network filesystems * Stopping Mount network filesystems

Dec11.14:24:56.[WARN]::nvOS_mon.c:1873:main /usr/sbin/nvOS_mon: Debug level is 2 * Stopping System V runlevel compatibility [ OK ] Pluribus Networks ONVL OS (DEMO VERSION) draco06 ttyS0

draco06 login: root Password: Last login: Fri Dec 11 14:45:12 PST 2015 from 10.97.1.42 on pts/2

Welcome to Pluribus Networks Open Netvisor Linux (ONVL) OS - Version: 2.3.1-203018495 (GNU/Linux 3.16.0-34-generic x86_64)

About Pluribus Networks Pluribus Networks provides data center solutions that allow your business to run unconstrained. Our software-defined, open networking, fabric-based solutions transform existing network infrastructures into flexible and strategic assets fully aligned with today’s digital business needs. Our Virtualization-Centric Fabric (VCF™) architecture provides unprecedented insight, agility and security to customers seeking to simplify operations, run more cost effectively and bring new applications online faster.

Learn more at http://www.pluribusnetworks.com/dell and @pluribusnet.

Pluribus Networks, Inc. 2455 Faber Place, Suite 100, Palo Alto, CA 94303 1-855-GET-VNET / +1 650-289-4717

Copyright© 2016 Pluribus Networks, Inc. All rights reserved.

January 2016

Documents

Open Netvisor Linux - Pluribus Networks