Dear all,

I encountered IQ startup issue because of invalid hostid.

When I checked hostid using cpuinfo utility, I realized that hostid is a null like below.

[cpuinfo -v]

————————————————————————————————————————————————————————-

2014/10/15 13:35:39  Sybase Licensing API/2.2.0.9/2209/64bit/2/P/x86_64/Enterprise Linux/OPT/Thu May  3 09:00:42 2012

2014/10/15 13:35:39  FLEXnet Licensing API/v11.5.0.0 build 56285 amd64_re3

2014/10/15 13:35:39  Hostid [0x22230d0]:

2014/10/15 13:35:39  cpuinfo: Hostid = (null)

License hostid:

Detected 2 logical processor(s), 2 core(s), in 1 chip(s)

————————————————————————————————————————————————————————-

If ifconfig has no entry for eth0, license only looks for etho,

lmutil hostid reports: NIC card must be on eth0 for Linux, otherwise SySAM will see the hostid as null and not work.

After moving the NIC card to eth0 the license can now check out fine as the hostid is visible to SySAM.

Here are two workaround.

Workaround 1

============

– Change eth2 to eth0 in /etc/sysconfig/hwconf (make sure there’s no other eth0 defined)

– Rename eth2 scripts to eth0 in /etc/sysconfig/network-scripts

– Edit references to eth2 and change them to eth0

Workaround 2

============

It should be possible to use the ‘sysamcap’ host-ids with products using SyLAPI 2.2.0.9, such as ASE 15.7 ESD#2 and upcoming releases for other products. (CR 693195 provides a workaround in sysamcap and is delivered in SySAM/SyLAPI 2.2.0.9)

Thanks

Gi-Sung Jang

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. John Barton

    I Think this can happen if they clone a VM impropely and the MAC Address is duplicated and so the new instances eth0 will not come up because the MAC Address should be unique. I had this at one customer and they missed a step in the cloning process and that was what caused there to be no eth0 on the host and SYSAM did not like that.

    (0) 

Leave a Reply