DPDK: Vrouter with Bond on VF is not coming up Build 3.02.41

Bug #1584153 reported by Vinod Nair
256
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.0
Fix Committed
High
Vinod Nair
Trunk
Fix Committed
High
Vinod Nair

Bug Description

Vrouter doesn't start after provisioning on VF+Bond

2016-05-19 22:37:58:456594:
2016-05-19 22:37:58:456868: [root@10.87.141.2] sudo: service supervisor-vrouter status
2016-05-19 22:38:18:477362: [root@10.87.141.2] out: supervisor-vrouter stop/waiting
2016-05-19 22:38:18:515239: [root@10.87.141.2] out:
2016-05-19 22:38:18:515920:
2016-05-19 22:38:18:516303: Disconnecting from 10.87.141.2... done.
2016-05-19 22:38:38:548506: Service supervisor-vrouter not running.
2016-05-19 22:38:38:548711:

Testbed,config
=================
env.dpdk = {
    host2: { 'huge_pages' : '50', 'coremask' : '0xf'},
}

env.sriov = {
     host2 :[ {'interface' : 'p1p1', 'VF' : 7, 'physnets' : ['physnet1']},{'interface' : 'p1p2', 'VF' : 7, 'physnets' : ['physnet2']} ]
}

#OPTIONAL BONDING CONFIGURATION
#==============================
#Inferface Bonding
#OPTIONAL BONDING CONFIGURATION
#==============================
#Inferface Bonding
bond= {
         host1 : { 'name': 'bond0', 'member': ['p1p1','p1p2'], 'mode': '802.3ad', 'xmit_hash_policy': 'layer3+4' },
         host2 : { 'name': 'bond0', 'member': ['p1p1_4','p1p2_4'], 'mode': 'balance-rr'},
}

#OPTIONAL SEPARATION OF MANAGEMENT AND CONTROL + DATA
#====================================================
#Control Interface
control_data = {
    host1 : { 'ip': '13.1.0.1/24', 'gw' : '13.1.0.254', 'device':'bond0' },
    host2 : { 'ip': '13.1.0.2/24', 'gw' : '13.1.0.254', 'device':'bond0', 'vlan':141 },

}

Tags: dpdk
Revision history for this message
Vinod Nair (vinodnair) wrote :

workaround is to create a sriov,conf file in /etc/init .. example is as below

cat /etc/init/sriov.conf
description "SRIOV"

start on (starting networking)
stop on runlevel [016]
limit core unlimited unlimited
# For DPDK vRouter we need longer timeout to let KNI devices shut down
# gracefully
kill timeout 20

# Restart the process if it dies with a signal
# or exit code not given by the 'normal exit' stanza.
respawn

# Give up if restart occurs 10 times in 90 seconds.
respawn limit 10 90

pre-start script
    echo 7 > /sys/class/net/p1p1/device/sriov_numvfs
    echo 7 > /sys/class/net/p1p2/device/sriov_numvfs
end script

script
end script

post-start script
end script

pre-stop script
end script

post-stop script
end script

information type: Proprietary → Public
Revision history for this message
Raja Sivaramakrishnan (raja-u) wrote :

Fixed in https://bugs.launchpad.net/juniperopenstack/+bug/1573255. Please close if it looks ok.

Revision history for this message
Vinod Nair (vinodnair) wrote :

Verified with 3.0.2 Build 43 and is ok

tags: removed: blocker
Kayla Fromme (kf0216)
information type: Public → Public Security
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.