Bug #1510475 “VLAN ID different than 0 doesn't work” : Bugs : Juniper Openstack

Maciej (maciej-grochowski) on 2015-11-17

information type:

Proprietary → Public

Ashish Ranjan (aranjan-n) on 2015-11-17

Changed in juniperopenstack:
assignee:	nobody → Hari Prasad Killi (haripk)

Revision history for this message

Hari Prasad Killi (haripk) wrote on 2015-11-18:

#1

In this case, a logical interface should be created on the router with the required vlan id and parent referring to the physical interface. Please confirm whether this was done or not.

tags:

added: vrouter

Revision history for this message

Nachi Ueno (nati-ueno) wrote on 2015-11-23:

#2

Yes. They did it, and it isn't working.

Revision history for this message

Maciej (maciej-grochowski) wrote on 2015-11-24:

#3

Download full text (3.9 KiB)

Hello Hari,
In case of device that has 2 logical ports, port-1 with vlan_id=0 and port-2 with vlan_id=3

using vif --list give me followed output:

Vrouter Interface Table

Flags: P=Policy, X=Cross Connect, S=Service Chain, Mr=Receive Mirror
       Mt=Transmit Mirror, Tc=Transmit Checksum Offload, L3=Layer 3, L2=Layer 2
       D=DHCP, Vp=Vhost Physical, Pr=Promiscuous, Vnt=Native Vlan Tagged
       Mnp=No MAC Proxy

vif0/0 OS: sproute0 (Speed 10, Duplex 1)
            Type:Physical HWaddr:00:00:00:00:00:00 IPaddr:0
            Vrf:0 Flags:L3L2Vp MTU:1514 Ref:3
            RX packets:299 bytes:109103 errors:0
            TX packets:683 bytes:498998 errors:0

vif0/1 OS: vhost0
            Type:Host HWaddr:08:00:27:01:02:03 IPaddr:0
            Vrf:0 Flags:L3L2 MTU:1514 Ref:3
            RX packets:679 bytes:508336 errors:0
            TX packets:299 bytes:109103 errors:0

vif0/2 OS: pkt0
            Type:Agent HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:65535 Flags:L3 MTU:1514 Ref:2
            RX packets:5 bytes:350 errors:0
            TX packets:1 bytes:70 errors:0

vif0/3 OS: veth_wan (Speed 10000, Duplex 1)
            Type:Physical HWaddr:aa:35:41:da:e0:59 IPaddr:0
            Vrf:0 Flags:TcL3L2Vnt MTU:1514 Ref:3
            RX packets:1 bytes:42 errors:0
            TX packets:1 bytes:42 errors:0

vif0/4 OS: port-1 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:58 IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/5 OS: port-2 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:59 IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/6 OS: port-3 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:5a IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:2
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/7 OS: port-4 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:5b IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:2
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/8 OS: NULL Vlan(o/i)(,S): 0/0 Bridge Index: 0 Parent:vif0/3
            Type:Virtual(Vlan) HWaddr:aa:35:41:da:e0:59 IPaddr:0
            Vrf:1 Flags:PL3L2Mnp MTU:1514 Ref:7
            RX packets:1 bytes:42 errors:0
            TX packets:1 bytes:42 errors:0

vif0/10 OS: NULL Vlan(o/i)(,S): 0/0 Bridge Index: 0 Parent:vif0/4
            Type:Virtual(Vlan) HWaddr:00:90:0b:3a:dc:58 IPaddr:0
            Vrf:2 Flags:PL3L2Mnp MTU:1514 Ref:1
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/12 OS: NULL Vlan(o/i)(,S): 3/3 Bridge Index: 0 Parent:vif0/5
            Type:Virtual(Vlan) HWaddr:00:90:0b:3a:dc:59 IPaddr:0
            Vrf:3 Flags:PL3L2Mnp MTU:1514 Ref:6
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/4350 OS: pkt3
Type:Stats HWaddr:00:00...

Hello Hari, 
In case of device that has 2 logical ports, port-1 with vlan_id=0 and port-2 with vlan_id=3

using vif --list give me followed output:

Vrouter Interface Table

Flags: P=Policy, X=Cross Connect, S=Service Chain, Mr=Receive Mirror
       Mt=Transmit Mirror, Tc=Transmit Checksum Offload, L3=Layer 3, L2=Layer 2
       D=DHCP, Vp=Vhost Physical, Pr=Promiscuous, Vnt=Native Vlan Tagged
       Mnp=No MAC Proxy

vif0/0      OS: sproute0 (Speed 10, Duplex 1)
            Type:Physical HWaddr:00:00:00:00:00:00 IPaddr:0
            Vrf:0 Flags:L3L2Vp MTU:1514 Ref:3
            RX packets:299  bytes:109103 errors:0
            TX packets:683  bytes:498998 errors:0

vif0/1      OS: vhost0
            Type:Host HWaddr:08:00:27:01:02:03 IPaddr:0
            Vrf:0 Flags:L3L2 MTU:1514 Ref:3
            RX packets:679  bytes:508336 errors:0
            TX packets:299  bytes:109103 errors:0

vif0/2      OS: pkt0
            Type:Agent HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:65535 Flags:L3 MTU:1514 Ref:2
            RX packets:5  bytes:350 errors:0
            TX packets:1  bytes:70 errors:0

vif0/3      OS: veth_wan (Speed 10000, Duplex 1)
            Type:Physical HWaddr:aa:35:41:da:e0:59 IPaddr:0
            Vrf:0 Flags:TcL3L2Vnt MTU:1514 Ref:3
            RX packets:1  bytes:42 errors:0
            TX packets:1  bytes:42 errors:0

vif0/4      OS: port-1 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:58 IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/5      OS: port-2 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:59 IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/6      OS: port-3 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:5a IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:2
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/7      OS: port-4 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:5b IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:2
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/8      OS: NULL Vlan(o/i)(,S): 0/0 Bridge Index: 0 Parent:vif0/3
            Type:Virtual(Vlan) HWaddr:aa:35:41:da:e0:59 IPaddr:0
            Vrf:1 Flags:PL3L2Mnp MTU:1514 Ref:7
            RX packets:1  bytes:42 errors:0
            TX packets:1  bytes:42 errors:0

vif0/10     OS: NULL Vlan(o/i)(,S): 0/0 Bridge Index: 0 Parent:vif0/4
            Type:Virtual(Vlan) HWaddr:00:90:0b:3a:dc:58 IPaddr:0
            Vrf:2 Flags:PL3L2Mnp MTU:1514 Ref:1
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/12     OS: NULL Vlan(o/i)(,S): 3/3 Bridge Index: 0 Parent:vif0/5
            Type:Virtual(Vlan) HWaddr:00:90:0b:3a:dc:59 IPaddr:0
            Vrf:3 Flags:PL3L2Mnp MTU:1514 Ref:6
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/4350   OS: pkt3
            Type:Stats HWaddr:00:00:00:00:00:00 IPaddr:0
            Vrf:65535 Flags:L3L2 MTU:9136 Ref:1
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

vif0/4351   OS: pkt1
            Type:Stats HWaddr:00:00:00:00:00:00 IPaddr:0
            Vrf:65535 Flags:L3L2 MTU:9136 Ref:1
            RX packets:0  bytes:0 errors:0
            TX packets:0  bytes:0 errors:0

--------------------------------------

So that looks to 
vif0/12 is logic interface for vif0/5 (port-2) with vlan_id=3
vif0/10 is logic interface for vif0/4 (port-1) with vlan_id=0

next is that I can use vif0/10 with vlan_id=0 correctly (with no interface modification) because vlan_id=0, 
as  a second step I was created logical interface with wlan_id=3 eth0.3 and vconfig add eth0 3.
using this interface I am unable to get any IP address or even connectivity

Revision history for this message

Anand H. Krishnan (anandhk) wrote on 2015-11-30:

#4

A few questions:

What type of interfaces are port1, port2 and port3? Are these actual physical NICS? I see that speed and duplex values are invalid. I also see from the output you have given that the statistics are all 0.

Please run tcpdump on these interfaces to see what kind of packets are ingressing and egressing and let us know your observations

In the successful case, are you sure that you haven't connected your physical device to 'veth_wan' interface?

Thanks

Revision history for this message

Maciej (maciej-grochowski) wrote on 2015-11-30:

#5

Download full text (13.9 KiB)

Thank You for command, I will try to show as best as I can our device structure. After reading rest of this message please let me know if I can also show another additional command to help you.

Our hardware is lanner box http://www.lannerinc.com/download-center/Datasheets/x86-Network-Appliances/?download=1541. So we had 6 NIC-s

Few command to show structure of this hardware:

root@esehost:/rfshome/eseuser# lspci -tv
-[0000:00]-+-00.0 Intel Corporation Atom processor C2000 SoC Transaction Router
           +-01.0-[01]----00.0 Intel Corporation I210 Gigabit Network Connection
           +-02.0-[02]----00.0 Intel Corporation I210 Gigabit Network Connection
           +-03.0-[03]--
           +-04.0-[04]--
           +-0b.0 Intel Corporation Atom processor C2000 nCPM
           +-0e.0 Intel Corporation Atom processor C2000 RAS
           +-0f.0 Intel Corporation Atom processor C2000 RCEC
           +-13.0 Intel Corporation Atom processor C2000 SMBus 2.0
           +-14.0 Intel Corporation Ethernet Connection I354
           +-14.1 Intel Corporation Ethernet Connection I354
           +-14.2 Intel Corporation Ethernet Connection I354
           +-14.3 Intel Corporation Ethernet Connection I354
           +-16.0 Intel Corporation Atom processor C2000 USB Enhanced Host Controller
           +-17.0 Intel Corporation Atom processor C2000 AHCI SATA2 Controller
           +-18.0 Intel Corporation Atom processor C2000 AHCI SATA3 Controller
           +-1f.0 Intel Corporation Atom processor C2000 PCU
           \-1f.3 Intel Corporation Atom processor C2000 PCU SMBus

root@esehost:/rfshome/eseuser# lshw -class network
PCI (sysfs)
  *-network
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: port-1
       version: 03
       serial: 00:90:0b:3a:dc:58
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k firmware=3.20, 0x80000551 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:16 memory:dfd00000-dfd7ffff ioport:d000(size=32) memory:dfd80000-dfd83fff
  *-network
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: port-2
       version: 03
       serial: 00:90:0b:3a:dc:59
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k firmware=3.20, 0x80000551 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:17 memory:dfc00000-dfc7ffff ioport:c000(size=32) memory:dfc80000-dfc83fff
  *-network:0
       description: Ethernet interface
...

Thank You for command, I will try to show as best as I can our device structure. After reading rest of this message please let me know if I can also show another additional command to help you.

Our hardware is lanner box http://www.lannerinc.com/download-center/Datasheets/x86-Network-Appliances/?download=1541. So we had 6 NIC-s

Few command to show structure of this hardware:

root@esehost:/rfshome/eseuser# lspci -tv
-[0000:00]-+-00.0  Intel Corporation Atom processor C2000 SoC Transaction Router
           +-01.0-[01]----00.0  Intel Corporation I210 Gigabit Network Connection
           +-02.0-[02]----00.0  Intel Corporation I210 Gigabit Network Connection
           +-03.0-[03]--
           +-04.0-[04]--
           +-0b.0  Intel Corporation Atom processor C2000 nCPM
           +-0e.0  Intel Corporation Atom processor C2000 RAS
           +-0f.0  Intel Corporation Atom processor C2000 RCEC
           +-13.0  Intel Corporation Atom processor C2000 SMBus 2.0
           +-14.0  Intel Corporation Ethernet Connection I354
           +-14.1  Intel Corporation Ethernet Connection I354
           +-14.2  Intel Corporation Ethernet Connection I354
           +-14.3  Intel Corporation Ethernet Connection I354
           +-16.0  Intel Corporation Atom processor C2000 USB Enhanced Host Controller
           +-17.0  Intel Corporation Atom processor C2000 AHCI SATA2 Controller
           +-18.0  Intel Corporation Atom processor C2000 AHCI SATA3 Controller
           +-1f.0  Intel Corporation Atom processor C2000 PCU
           \-1f.3  Intel Corporation Atom processor C2000 PCU SMBus

root@esehost:/rfshome/eseuser# lshw -class network
PCI (sysfs)  
  *-network               
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: port-1
       version: 03
       serial: 00:90:0b:3a:dc:58
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k firmware=3.20, 0x80000551 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:16 memory:dfd00000-dfd7ffff ioport:d000(size=32) memory:dfd80000-dfd83fff
  *-network
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: port-2
       version: 03
       serial: 00:90:0b:3a:dc:59
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k firmware=3.20, 0x80000551 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:17 memory:dfc00000-dfc7ffff ioport:c000(size=32) memory:dfc80000-dfc83fff
  *-network:0
       description: Ethernet interface
       product: Ethernet Connection I354
       vendor: Intel Corporation
       physical id: 14
       bus info: pci@0000:00:14.0
       logical name: port-3
       version: 03
       serial: 00:90:0b:3a:dc:5a
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k firmware=0.0.0 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:20 memory:dfe60000-dfe7ffff ioport:e0c0(size=32) memory:dff2c000-dff2ffff
  *-network:1
       description: Ethernet interface
       product: Ethernet Connection I354
       vendor: Intel Corporation
       physical id: 14.1
       bus info: pci@0000:00:14.1
       logical name: port-4
       version: 03
       serial: 00:90:0b:3a:dc:5b
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k firmware=0.0.0 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:21 memory:dfe40000-dfe5ffff ioport:e0a0(size=32) memory:dff28000-dff2bfff
  *-network:2
       description: Ethernet interface
       product: Ethernet Connection I354
       vendor: Intel Corporation
       physical id: 14.2
       bus info: pci@0000:00:14.2
       logical name: eth0
       version: 03
       serial: 00:90:0b:3a:dc:5c
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k duplex=full firmware=0.0.0 ip=10.5.15.20 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:22 memory:dfe20000-dfe3ffff ioport:e080(size=32) memory:dff24000-dff27fff
  *-network:3
       description: Ethernet interface
       product: Ethernet Connection I354
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       logical name: mgmt
       version: 03
       serial: 00:90:0b:3a:dc:5d
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.0.5-k duplex=full firmware=0.0.0 ip=10.0.0.253 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:23 memory:dfe00000-dfe1ffff ioport:e060(size=32) memory:dff20000-dff23fff
  *-network:0
       description: Ethernet interface
       physical id: 1
       logical name: pkt0
       serial: a2:94:9c:af:16:8e
       size: 10Mbit/s
       capabilities: ethernet physical
       configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=yes multicast=yes port=twisted pair speed=10Mbit/s
  *-network:1
       description: Ethernet interface
       physical id: 2
       logical name: veth_wan
       serial: 86:ff:4d:bf:37:e5
       capabilities: ethernet physical
       configuration: autonegotiation=off broadcast=yes driver=veth driverversion=1.0 duplex=full link=yes multicast=yes port=twisted pair
  *-network:2
       description: Ethernet interface
       physical id: 3
       logical name: vhost0
       serial: 08:00:27:01:02:03
       capabilities: ethernet physical
       configuration: broadcast=yes driver=vrouter driverversion=N/A firmware=N/A ip=172.16.250.1 link=yes multicast=yes
  *-network:3
       description: Ethernet interface
       physical id: 4
       logical name: veth_wan_peer
       serial: a6:97:51:8e:47:35
       capabilities: ethernet physical
       configuration: autonegotiation=off broadcast=yes driver=veth driverversion=1.0 duplex=full ip=10.255.255.5 link=yes multicast=yes port=twisted pair

So it seems that we had interfaces connected to PCI: port-1:port-4 and eth0/mgmt.
Also, it can be good to show driver (for eth0 and ports1-4)

root@esehost:/rfshome/eseuser# ethtool -i eth0 
driver: igb
version: 5.0.5-k
firmware-version: 0.0.0
bus-info: 0000:00:14.2
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

root@esehost:/rfshome/eseuser# ethtool -i port-1
driver: igb
version: 5.0.5-k
firmware-version: 3.20, 0x80000551
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

igb driver info:

root@esehost:/rfshome/eseuser# modinfo igb
filename:       /lib/modules/3.13.0-32-generic/kernel/drivers/net/ethernet/intel/igb/igb.ko
version:        5.0.5-k
license:        GPL
description:    Intel(R) Gigabit Ethernet Network Driver
author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>
srcversion:     1FB72FE8E4637A67EE1835D
alias:          pci:v00008086d000010D6sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A9sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E8sv*sd*bc*sc*i*
alias:          pci:v00008086d00001526sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Dsv*sd*bc*sc*i*
alias:          pci:v00008086d000010E7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E6sv*sd*bc*sc*i*
alias:          pci:v00008086d00001518sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Asv*sd*bc*sc*i*
alias:          pci:v00008086d000010C9sv*sd*bc*sc*i*
alias:          pci:v00008086d00000440sv*sd*bc*sc*i*
alias:          pci:v00008086d0000043Csv*sd*bc*sc*i*
alias:          pci:v00008086d0000043Asv*sd*bc*sc*i*
alias:          pci:v00008086d00000438sv*sd*bc*sc*i*
alias:          pci:v00008086d00001516sv*sd*bc*sc*i*
alias:          pci:v00008086d00001511sv*sd*bc*sc*i*
alias:          pci:v00008086d00001510sv*sd*bc*sc*i*
alias:          pci:v00008086d00001527sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Esv*sd*bc*sc*i*
alias:          pci:v00008086d00001524sv*sd*bc*sc*i*
alias:          pci:v00008086d00001523sv*sd*bc*sc*i*
alias:          pci:v00008086d00001522sv*sd*bc*sc*i*
alias:          pci:v00008086d00001521sv*sd*bc*sc*i*
alias:          pci:v00008086d0000157Csv*sd*bc*sc*i*
alias:          pci:v00008086d0000157Bsv*sd*bc*sc*i*
alias:          pci:v00008086d00001538sv*sd*bc*sc*i*
alias:          pci:v00008086d00001537sv*sd*bc*sc*i*
alias:          pci:v00008086d00001536sv*sd*bc*sc*i*
alias:          pci:v00008086d00001533sv*sd*bc*sc*i*
alias:          pci:v00008086d00001539sv*sd*bc*sc*i*
alias:          pci:v00008086d00001F45sv*sd*bc*sc*i*
alias:          pci:v00008086d00001F41sv*sd*bc*sc*i*
alias:          pci:v00008086d00001F40sv*sd*bc*sc*i*
depends:        ptp,dca,i2c-algo-bit
intree:         Y
vermagic:       3.13.0-32-generic SMP mod_unload modversions 
signer:         Magrathea: Glacier signing key
sig_key:        5E:3C:0F:9C:A6:E3:65:43:53:5F:A2:BB:5B:70:9E:84:F1:6D:A7:C7
sig_hashalgo:   sha512
parm:           max_vfs:Maximum number of virtual functions to allocate per physical function (uint)
parm:           debug:Debug level (0=none,...,16=all) (int)

"ip a" show a lot of interfaces because this device uses several virtualization techniques, but it also shows port-1:4 and eth0/mgmt

root@esehost:/rfshome/eseuser# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: port-3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:90:0b:3a:dc:5a brd ff:ff:ff:ff:ff:ff
3: port-4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:90:0b:3a:dc:5b brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:90:0b:3a:dc:5c brd ff:ff:ff:ff:ff:ff
    inet 10.5.15.20/23 brd 10.5.15.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::290:bff:fe3a:dc5c/64 scope link 
       valid_lft forever preferred_lft forever
5: mgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:90:0b:3a:dc:5d brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.253/24 brd 10.0.0.255 scope global mgmt
       valid_lft forever preferred_lft forever
    inet6 fe80::290:bff:fe3a:dc5d/64 scope link 
       valid_lft forever preferred_lft forever
6: port-1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:90:0b:3a:dc:58 brd ff:ff:ff:ff:ff:ff
7: port-2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:90:0b:3a:dc:59 brd ff:ff:ff:ff:ff:ff
8: sproute0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1300 qdisc mq state UNKNOWN group default qlen 10000
    link/none 
9: veth_wan_peer: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether a6:97:51:8e:47:35 brd ff:ff:ff:ff:ff:ff
    inet 10.255.255.5/24 brd 10.255.255.255 scope global veth_wan_peer
       valid_lft forever preferred_lft forever
    inet6 fe80::a497:51ff:fe8e:4735/64 scope link 
       valid_lft forever preferred_lft forever
10: veth_wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 86:ff:4d:bf:37:e5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::84ff:4dff:febf:37e5/64 scope link 
       valid_lft forever preferred_lft forever
11: pkt1: <> mtu 65535 qdisc noop state DOWN group default 
    link/void 7a:ea:06:51:4d:2a brd 00:00:00:00:00:00
12: pkt3: <> mtu 65535 qdisc noop state DOWN group default 
    link/void b6:1c:c1:e6:c7:40 brd 00:00:00:00:00:00
13: pkt2: <> mtu 65535 qdisc noop state DOWN group default 
    link/void 52:65:12:07:d5:72 brd 00:00:00:00:00:00
14: vhost0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1300 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 08:00:27:01:02:03 brd ff:ff:ff:ff:ff:ff
    inet 172.16.250.1/32 brd 172.16.250.1 scope global vhost0
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe01:203/64 scope link 
       valid_lft forever preferred_lft forever
15: pkt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500
    link/ether a2:94:9c:af:16:8e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a094:9cff:feaf:168e/64 scope link 
       valid_lft forever preferred_lft forever

Revision history for this message

Maciej (maciej-grochowski) wrote on 2015-11-30:

#6

Also, I will try to debug ports with tcpdump, and share my observations. But I think that hardware structure (last message) from my device also can be helpful for you.

According to point:
"In the successful case, are you sure that you haven't connected your physical device to 'veth_wan' interface?"
Could You explain a little bit more about this? How can I check this? (In previous message I send you output of 'ip a' command, is possible to make sure that we didn't do this)

Revision history for this message

Anand H. Krishnan (anandhk) wrote on 2015-11-30:

#7

From the output you sent me, it looks like none of the port-X interfaces have link up.

Revision history for this message

Maciej (maciej-grochowski) wrote on 2015-11-30:

#8

Download full text (5.3 KiB)

Yes, that is correct, I was trying to show You how the structure looks like with these port-1:4 interfaces because they are physical.
Please let me know which commands will be good to see with link-up.

I connected to port-1 end point device (with VLAN_ID=0) and using tcpdump I didn't see anything that could be troubling, at this point.
Maybe you would like to see VLAN_ID=2 or 3? Please let me know because there are many things that can be examinate, but I don't know which of them will be helpful for you.

Again vif --list show similar output. (port-1 link-up vlan-id=0)

root@9a093ec1-1b1b-47b4-ad51-ec267dfe1ceb:/# vif --list
Vrouter Interface Table

Flags: P=Policy, X=Cross Connect, S=Service Chain, Mr=Receive Mirror
       Mt=Transmit Mirror, Tc=Transmit Checksum Offload, L3=Layer 3, L2=Layer 2
       D=DHCP, Vp=Vhost Physical, Pr=Promiscuous, Vnt=Native Vlan Tagged
       Mnp=No MAC Proxy

vif0/0 OS: sproute0 (Speed 10, Duplex 1)
            Type:Physical HWaddr:00:00:00:00:00:00 IPaddr:0
            Vrf:0 Flags:L3L2Vp MTU:1514 Ref:6
            RX packets:83391 bytes:85923228 errors:0
            TX packets:57096 bytes:30768463 errors:0

vif0/1 OS: vhost0
            Type:Host HWaddr:08:00:27:01:02:03 IPaddr:0
            Vrf:0 Flags:L3L2 MTU:1514 Ref:3
            RX packets:55501 bytes:31033287 errors:0
            TX packets:81968 bytes:85636463 errors:0

vif0/2 OS: pkt0
            Type:Agent HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:65535 Flags:L3 MTU:1514 Ref:2
            RX packets:239 bytes:40429 errors:0
            TX packets:1330 bytes:153385 errors:0

vif0/3 OS: veth_wan (Speed 10000, Duplex 1)
            Type:Physical HWaddr:86:ff:4d:bf:37:e5 IPaddr:0
            Vrf:0 Flags:TcL3L2Vnt MTU:1514 Ref:3
            RX packets:34 bytes:1750 errors:0
            TX packets:31 bytes:1314 errors:0

vif0/4 OS: port-1 (Speed 1000, Duplex 1)
            Type:Physical HWaddr:00:90:0b:3a:dc:58 IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:1779 bytes:165773 errors:512
            TX packets:31 bytes:5931 errors:0

vif0/5 OS: port-2 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:59 IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/6 OS: port-3 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:5a IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:3
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/7 OS: port-4 (Speed 65535, Duplex 255)
            Type:Physical HWaddr:00:90:0b:3a:dc:5b IPaddr:0
            Vrf:0 Flags:L3L2Vnt MTU:1514 Ref:2
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/11 OS: NULL Vlan(o/i)(,S): 3/3 Bridge Index: 0 Parent:vif0/5
            Type:Virtual(Vlan) HWaddr:00:90:0b:3a:dc:59 IPaddr:0
            Vrf:1 Flags:PL3L2Mnp MTU:1514 Ref:6
            RX packets:0 bytes:0 errors:0
            TX packets:0 bytes:0 errors:0

vif0/12 OS: NULL Vlan(o/i)(,S): 0/0 Bridge Index: 0 Parent:vif0/...

Juniper Openstack

VLAN ID different than 0 doesn't work

Bug Description

Other bug subscribers

Remote bug watches