..

HMP 4.1 ipmedia start failure

..

Developer Group

Developer Group
Connect with thousands of other developers to brainstorm ideas, share best practices and tips - or just chat about the latest emerging technologies making noise in the field. And of course, get the most up-to-date service and support news from Dialogic.
Dialogic PowerMedia HMP GlobalCall and R4 API

HMP 4.1 ipmedia start failure

  • Hi all,

    I have a strange behaviour with a new HMP 4.1 installation (SU 272). Installation completed successfully, and ipmedia starts with the standard demo license. Anyway with a permanent purchased license, ipmedia fails to start, although the license would be deployed correctly.

    This is not my first HMP installation, and I never met this kind of error before.

    The only difference concern with the server network interfaces. In this installation I have the following network IF:

    PrivateTeam: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
    RX packets 1941 bytes 1276418 (1.2 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1294 bytes 222434 (217.2 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    PublicTeam: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
    RX packets 2420 bytes 1052997 (1.0 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 733 bytes 2122667 (2.0 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    brPrivate: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast a.b.c.d
    inet6 fe80::9d28:5f2:537e:3124 prefixlen 64 scopeid 0x20<link>
    ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
    RX packets 1658 bytes 1094433 (1.0 MiB)
    RX errors 0 dropped 684 overruns 0 frame 0
    TX packets 352 bytes 31422 (30.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    brPublic: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet yyy.yyy.yyy.yyy netmask 255.255.255.224 broadcast e.f.g.h
    inet6 fe80::9095:1467:ef3d:bdcf prefixlen 64 scopeid 0x20<link>
    ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
    RX packets 2324 bytes 1028122 (1004.0 KiB)
    RX errors 0 dropped 684 overruns 0 frame 0
    TX packets 733 bytes 2122667 (2.0 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp3s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
    RX packets 1981 bytes 1311698 (1.2 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1293 bytes 227523 (222.1 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp3s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
    RX packets 2417 bytes 1094855 (1.0 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1914 bytes 2194436 (2.0 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp4s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
    RX packets 1470 bytes 1107668 (1.0 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp4s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
    RX packets 1189 bytes 1003375 (979.8 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    ens2f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether 00:26:55:db:2d:4e txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 44 memory 0xfbfe0000-fc000000

    ens2f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether 00:26:55:db:2d:4f txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 46 memory 0xfbfa0000-fbfc0000

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1 (Local Loopback)
    RX packets 802 bytes 78384 (76.5 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 802 bytes 78384 (76.5 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
    ether 52:54:00:d7:43:c4 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
    ether 52:54:00:d7:43:c4 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet6 fe80::fc54:ff:fe70:aa62 prefixlen 64 scopeid 0x20<link>
    ether fe:54:00:70:aa:62 txqueuelen 1000 (Ethernet)
    RX packets 1221 bytes 207182 (202.3 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1941 bytes 1242639 (1.1 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    My license has been generated with the MAC 98:4b:e1:05:fa:d2.

    Do you know guys about problem with bonding and or bridge IF (the server has KVM installed also)?

    Any help/suggest will be appreciated.

    Thanks.

    Roberto

  • From q quick look there is a requirement from the FlexLm (licensing) level that NIC must be named EthX (where x is a number) for license activation to work correctly. I see that since this is a VM, you will need to make sure that requirement is met.

    Jeff

  • Hi Jeff,

    The problem can't be this one, because on some other VMs I have ensXX interfaces and the system works.

    Roberto.

  • I am not sure about Linux, but I know on windows HMP side the same flex version does not support teaming. So the NIC has to be on a NIC that is not part of the team. You can then use any other adapter set afterwards for the actual streaming of RTP. It could be the Linux side has the same restrictions, but I have not tried that in the past.

    Just speculation.

    Are the other systems configured the same way? What is the license bond to in that case, which NIC?

    Jeff