UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Observer mdzialak
Observer
1,093 Views
Registered: ‎04-24-2018

Vivado 2018.1 host interface name

Jump to solution

In Vivado 2014.4 Licence Manager there are recognized MAC adresses on both eth0 and eth1 interfaces
(View Host Information -> Network Interface Card (NIC) ID).
However in Vivado 2018.1 Licence Manager (installed on the same host) there is recognized only eth0 interface.

What interface name convention is obligatory in Vivado 2018.1?

0 Kudos
1 Solution

Accepted Solutions
Observer mdzialak
Observer
1,098 Views
Registered: ‎04-24-2018

Re: Vivado 2018.1 host interface name

Jump to solution

It turned out that Vivado 2018.1 environment requires physical Ethernet interface to be used in licence.

Interface name does not have to be in "ethX" format, though.

View solution in original post

0 Kudos
4 Replies
Moderator
Moderator
1,038 Views
Registered: ‎06-14-2010

Re: Vivado 2018.1 host interface name

Jump to solution

Hello @mdzialak,

 

In relation to your question: “What interface name convention is obligatory in Vivado 2018.1?”, the answer is: the traditional names, eth0, eth1, eth2, etc.

 

Please note that if you are using a new Ethernet port name format of your OS (fyi - typical port names used on many new Linux machines are em0, em1, eno1, enp0, etc ... instead of the traditional names, eth0, eth1, eth2, etc ...), this would not get recognized by the FlexLM tools then.

In VLM you’d then see 000000000000 of your MAC/Host ID, which would not match to what you have your licenses file generated for and a licensing issue will be seen then.

See AR#60510 https://www.xilinx.com/support/answers/60510.html for more details.

 

Therefore, if you are working with the Node-Locked licenses, then the only way to overcome this issue (i.e. Host ID = 000000000000) is to change the port name to the traditional names, eth0, eth1, eth2, etc., as indicated in the AR#60510.

 

Hope this helps.

Kind Regards,
Anatoli Curran,
Xilinx Technical Support
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Moderator
Moderator
1,035 Views
Registered: ‎06-14-2010

Re: Vivado 2018.1 host interface name

Jump to solution

Hello again @mdzialak,

 

I forgot to attach a screenshot where you can see that eth0 as well as eth1 are both getting detected in VLM as available NICs (in my case, the NIC numbers are identical, however all I want to show here is that eth0 as well as eth1 are both getting detected):

 

Forum_35.png

 

 

Kind Regards,
Anatoli Curran,
Xilinx Technical Support
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Observer mdzialak
Observer
1,001 Views
Registered: ‎04-24-2018

Re: Vivado 2018.1 host interface name

Jump to solution

Dear @anatoli,

 

thank You for the answer.
However, my experience does not confirm Your statement.

On the left - Vivado Licence Manager 2014.4, on the right - Vivado Licence Manager 2018.1.
Screenshot_2018-05-07_15-57-40.png

 

ifconfig:

Screenshot_2018-05-07_15-58-02.png

 

Vivado 2014.4 detects only ethX interfaces, that's right. But Vivado 2018.1 detects only ens3 (in that case) interface. Why is that?

0 Kudos
Observer mdzialak
Observer
1,099 Views
Registered: ‎04-24-2018

Re: Vivado 2018.1 host interface name

Jump to solution

It turned out that Vivado 2018.1 environment requires physical Ethernet interface to be used in licence.

Interface name does not have to be in "ethX" format, though.

View solution in original post

0 Kudos