Software Archive
Read-only legacy content

MICs and VLANs

Panos_L_
Beginner
695 Views

We have a VLAN that needs to be accessed via VLAN Tagging.  This is enabled
on the compute hosts as eth2.3.  I've configured eth2 as a bridge (br1) and
included the mic cards (mic0, mic1) in this bridge.  Creating br1.3 works
to route on the vlan, but the MIC hosts don't seem to support this.


Are there any packages we may be missing for VLAN support?

0 Kudos
4 Replies
Frances_R_Intel
Employee
695 Views

I believe tagged VLAN is not enabled by default on the coprocessor. Have you tried doing a 'modprobe 8021q' to load the kernel module on the coprocessor? The cryptic name is from the IEEE VLAN standard.

0 Kudos
Panos_L_
Beginner
695 Views

Hi Frances,

Thank you for your reply. The 8021q module loads fine:

[root@n34-mic0 ~]# modprobe 8021q

[root@n34-mic0 ~]# dmesg | tail -n 2
[37348.264234] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[37348.264261] All bugs added by David S. Miller <davem@redhat.com>
[root@n34-mic0 ~]#

What is missing a utility like vconfig to create the tagged interface, but that can be compiled for the k1om architecture. My question had to do with how tagged packets propagate through mic0. Even though I was able to create tagged interface on the card, I could not get any traffic through.

 

 

0 Kudos
Frances_R_Intel
Employee
695 Views

There are additional VLAN files for the coprocessor in the MPSS release under the k1om directory. I don't know if that has the configuration file you are looking for or not. I will need to ask around for further information. Luckily in this case I think I know just who to ask.

0 Kudos
Erich_C_Intel1
Employee
695 Views

Have you tried the VLAN in Static pair configuration? I would recommend first to check the connectivity of the VLAN in Static pair configuration and then switch to a bridge configuration. 

To check that the connection works you could try running from the coprocessor the following command : 

$ arping -I mic0.66 10.23.5.1

Assuming that 66 is the value of your VLAN, you should see Unicast replies. 

Also you can try using tcpdump in the host to see the tagged packets with the following command.

$ sudo tcpdump -ni mic0 vlan 66

 

0 Kudos
Reply