Software Archive
Read-only legacy content

Netmask for external bridge not set correctly

Andrey_Vladimirov
New Contributor III
640 Views

I am trying to connect Xeon Phi coprocessors to an external bridge with a wider than default netmask. My bridge br0 on the host has IP 10.33.1.2 with netmask 255.252.0.0 (the first 14 bits set). When I configure MPSS 3.2, I do this:

[bash]

[root@c001-n002 ~]# micctrl --addbridge=br0 --type=external --ip=10.33.1.2 --netbits=14
[root@c001-n002 ~]# micctrl --network=static --bridge=br0 --ip=10.33.1.22:10.33.1.42:10.33.1.62:10.33.1.82
          mic0: Changing network to static bridge br0 at 10.33.1.22
          mic1: Changing network to static bridge br0 at 10.33.1.42
          mic2: Changing network to static bridge br0 at 10.33.1.62
          mic3: Changing network to static bridge br0 at 10.33.1.82

[/bash]

Note that I do not have "netbits" in the second command, because if I put in "--netbits=14", micctrl responds "[Error] Adding an interface to a bridge will use the bridges netmask - ignoring netbits 14". The bridged configuration succeeds, however, on Xeon Phi, the interface mic0 is configured with a netmask of 255.255.255.0, which is incorrect.

[bash]

[root@c001-n002 ~]# service mpss start
Starting Intel(R) MPSS:                                    [  OK  ]
mic0: online (mode: linux image: /usr/share/mpss/boot/bzImage-knightscorner)
mic1: online (mode: linux image: /usr/share/mpss/boot/bzImage-knightscorner)
mic2: online (mode: linux image: /usr/share/mpss/boot/bzImage-knightscorner)
mic3: online (mode: linux image: /usr/share/mpss/boot/bzImage-knightscorner)
[root@c001-n002 ~]# ssh mic0 ifconfig mic0
mic0      Link encap:Ethernet  HWaddr 4C:79:BA:24:10:BA  
          inet addr:10.33.1.22  Bcast:10.33.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:143 errors:0 dropped:0 overruns:0 frame:0
          TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14910 (14.5 KiB)  TX bytes:10696 (10.4 KiB)

[/bash]

 

As a result, I cannot ping addresses outside of 10.33.1.22/255.255.255.0 from mic0 ("connect: Network is unreachable"). How do I convince micctrl to use a netmask of 255.252.0.0 for interface mic0 in uOS?

 

0 Kudos
5 Replies
Loc_N_Intel
Employee
640 Views

Hi Andrey,

There is a whitepaper discussing on how to configure the coprocessors in a cluster (link here http://software.intel.com/en-us/articles/configuring-intel-xeon-phi-coprocessors-inside-a-cluster ). Have you looked at this document yet? Thank you.

0 Kudos
Andrey_Vladimirov
New Contributor III
640 Views

I read this paper every morning (almost), but it is old in the sense that it uses MPSS Gold, and a lot of things have changed. What authors do there is they hack into the MIC filesystem tree to change the netmask in the interface configuration files. One should not have to resort to such inconvenient measures (and they are difficult to automate), especially when micctl has an argument to do it, and also because it claims that it will use the bridge's netmask.

The reason for my question is to verify that I am using micctrl correctly, and if I am doing it right, there is probably a bug in this tool.

 

0 Kudos
Loc_N_Intel
Employee
640 Views

Hi Andrey,

I get the same error when I try that command. Let me ask someone who know more about micctrl. Thank you.  

0 Kudos
Loc_N_Intel
Employee
640 Views

For your information, I generated a ticket in our system to track this defect (# 4868788). Thank you.

0 Kudos
Andrey_Vladimirov
New Contributor III
640 Views

Thank you very much, Loc!

0 Kudos
Reply