[Netronome] Unable to resolve arp after vrouter comes up on bonded interface

Bug #1774084 reported by Vivek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.1
Invalid
High
Pieter Malan
R5.0
Invalid
High
Pieter Malan
Trunk
Invalid
High
Pieter Malan

Bug Description

/var/log/contrail.log
Tue May 29 15:47:31 PDT 2018: Creating vhost interface: vhost0.
Tue May 29 15:47:31 PDT 2018: Adding bond0 to vrouter
vRouter(Response): Operation not supported (95)
vRouter(Response): No such device (19)

root@5b8s4:~# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 00:15:4d:12:2a:cc
Active Aggregator Info:
 Aggregator ID: 1
 Number of ports: 2
 Actor Key: 17
 Partner Key: 3
 Partner Mac Address: 40:71:83:31:b2:40

Slave Interface: nfp_p1
MII Status: up
Speed: 40000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:15:4d:12:2a:cc
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: 00:15:4d:12:2a:cc
    port key: 17
    port priority: 255
    port number: 1
    port state: 61
details partner lacp pdu:
    system priority: 127
    system mac address: 40:71:83:31:b2:40
    oper key: 3
    port priority: 127
    port number: 19
    port state: 63

Slave Interface: nfp_p0
MII Status: up
Speed: 40000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:15:4d:12:2a:cb
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: 00:15:4d:12:2a:cc
    port key: 17
    port priority: 255
    port number: 2
    port state: 61
details partner lacp pdu:
    system priority: 127
    system mac address: 40:71:83:31:b2:40
    oper key: 3
    port priority: 127
    port number: 20
    port state: 63

root@5b8s4:~# contrail-status
== Contrail vRouter ==
contrail-vrouter-agent: initializing (XMPP:control-node:5.5.5.231, XMPP:control-node:5.5.5.233, XMPP:dns-server:5.5.5.232, XMPP:dns-server:5.5.5.233, Collector connection down, No Configuration for self)
contrail-vrouter-nodemgr: initializing (Collector connection down)

root@5b8s4:~# ping 5.5.5.254
PING 5.5.5.254 (5.5.5.254) 56(84) bytes of data.
From 5.5.5.237 icmp_seq=1 Destination Host Unreachable
From 5.5.5.237 icmp_seq=2 Destination Host Unreachable
From 5.5.5.237 icmp_seq=3 Destination Host Unreachable
^C
--- 5.5.5.254 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms

Jeba Paulaiyan (jebap)
tags: added: iconic smartnic vrouter
Vinod Nair (vinodnair)
information type: Proprietary → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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