ProSBC in KVM LAN/WAN voip0 NIC showing down

7. Troubleshooting
1

Hi Support,

I’m currently trying to install ProSBC lab version 3.3.12.53 in a KVM env. I buy a virtual machine with 2 NICs, one is for mgmt, the other is for data/voip and role is LAN/WAN. ProSBC can identify 2 NICs initially, but once I restart the host, it shows voip0 is down.
I checked the result of ”lspci -vvv | grep -i Ether -A 25” it is showing the first ethernet card is using “Kernel driver in use: virtio-pci”, and the second card is using “Kernel driver in use: igb_uio“ which means it is managed by DPDK, and then I check the logs of tboam_app, it is showing:

25th, 08:15:32.326+0000 TBLV2 HCTL: [ip interface] "voip0" : Sending command /lib/tb/toolpack/pkg//3.3.12.53/scripts/network_resource.rb ip-interface --create --name voip0 --physdev voip0 --dhcp --onboot  
25th, 08:15:32.355+0000 TBMSG HCTL: ruby: voip0: error fetching interface information: Device not found 
25th, 08:15:32.356+0000 TBMSG HCTL: ruby: [FAIL]	 No MAC found /lib/tb/toolpack/pkg/3.3.12.53/scripts/host_ip_interface.rb:509:in `get_mac_from_ifconfig'/lib/tb/toolpack 
25th, 08:15:32.356+0000 TBMSG HCTL: ruby: /pkg/3.3.12.53/scripts/host_ip_interface.rb:520:in `get_available_mac'/lib/tb/toolpack/pkg/3.3.12.53/scripts/host_ip_interface.

and then i check the get_mac_from_ifconfig function in host_ip_interface.rb script, it is showing using cmd “cmdresult = ifconfig -a #{device}“, that maybe the reason why it fails.

My QUESTION: since the sencond card is managed by DPDK, why it is still using “cmdresult = ifconfig -a #{device} “ to get mac?

2

here is the result “lspci -vvv | grep -i Ether -A 25“

[root@prosbc3312 ~]# lspci -vvv | grep -i Ether -A 25
00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
        Subsystem: Red Hat, Inc. Device 0001
        Physical Slot: 3
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at fd018000 (64-bit, prefetchable) [size=16K]
        Region 2: Memory at fd000000 (64-bit, prefetchable) [size=32K]
        Region 4: Memory at fd01c000 (64-bit, prefetchable) [size=16K]
        Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
                Vector table: BAR=2 offset=00000000
                PBA: BAR=2 offset=00004000
        Capabilities: [b8] Vendor Specific Information: VirtIO: CommonCfg
                BAR=0 offset=00002f00 size=00000038
        Capabilities: [c8] Vendor Specific Information: VirtIO: Notify
                BAR=0 offset=00002ff0 size=00000004 multiplier=00000000
        Capabilities: [dc] Vendor Specific Information: VirtIO: ISR
                BAR=0 offset=00002f3c size=00000004
        Capabilities: [ec] Vendor Specific Information: VirtIO: DeviceCfg
                BAR=0 offset=00002f40 size=00000050
        Kernel driver in use: virtio-pci
        Kernel modules: virtio_pci

00:04.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
        Subsystem: Red Hat, Inc. Device 0008
        Physical Slot: 4
--
04:01.0 Ethernet controller: Red Hat, Inc. Virtio network device
        Subsystem: Red Hat, Inc. Device 0001
        Physical Slot: 1-4
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Region 0: Memory at fc808000 (64-bit, prefetchable) [size=16K]
        Region 2: Memory at fc800000 (64-bit, prefetchable) [size=32K]
        Region 4: Memory at fc80c000 (64-bit, prefetchable) [size=16K]
        Capabilities: [a0] MSI-X: Enable- Count=5 Masked-
                Vector table: BAR=2 offset=00000000
                PBA: BAR=2 offset=00004000
        Capabilities: [b8] Vendor Specific Information: VirtIO: CommonCfg
                BAR=0 offset=00002f00 size=00000038
        Capabilities: [c8] Vendor Specific Information: VirtIO: Notify
                BAR=0 offset=00002ff0 size=00000004 multiplier=00000000
        Capabilities: [dc] Vendor Specific Information: VirtIO: ISR
                BAR=0 offset=00002f3c size=00000004
        Capabilities: [ec] Vendor Specific Information: VirtIO: DeviceCfg
                BAR=0 offset=00002f40 size=00000050
        Kernel driver in use: igb_uio
        Kernel modules: virtio_pci
3

Hi julinpeng,

This is a very interesting technical catch. It appears there is a conflict between the DPDK initialization and the management scripts’ attempt to verify the MAC address via ifconfig.

Before we go deeper into the DPDK binding scripts, we would like to look at the full system state.

  1. Please provide a tbreport Could you please generate a tbreport and send it via wetransfer? Label the report with your username so we have context for the file.

  2. Temporary Workaround (e1000) While we investigate the VirtIO driver behavior in this specific build, you can likely get your lab environment stable by changing the Virtual NIC type in your KVM settings.

Shut down the VM.

Change the NIC model from virtio to e1000.

Restart the VM.

The e1000 driver uses a more standard kernel handshake that should allow the voip0 interface to initialize without the ‘Device not found’ error.

Once we have your tbreport, we can provide you with a more detailed answer.

-Support

4

Hi Dave,

Thanks for you repsonse. Basically this ProSBC version has not been tested on VM with virtual NIC based on VirtIO driver, right? I’m trying to install ProSBC into the VM which is in a pulic cloud infrastructure based on KVM. So, for the Temporary Workaround (e1000), I’m afraid it is not available for me to do so, I’ll try to get a tbreport.

5

Hi Dave

tbreport “report_1767173512_2025-12-31_00h00_2026-01-01_23h59.tar.gz“ has been sent. Please check it out. Waiting for your response, TIA.

6

Hi Julinpeng,

We have reviewed the recently provided logs in the TBreport, thank you.

Log Observations The logs reveal repeated errors concerning interface creation and MAC address identification. Specifically, the Virtual Infrastructure Manager (VIM) is failing to initialize the voip0 interface:

TBERR VIM: CTBOAMVim::OnHostIpInterfaceActionCompleted: Error in ip interface script (82000022) TBERR VIM: [ ip interface ] FAIL - action ‘create’ on ‘voip0’ completed with Result=0x02000000. Script exit code was 255. Script result was No MAC found

We have observed similar behaviors in this specific code version within certain virtualized environments. While some deployments function without issue, we are not yet 100% certain of the root cause in this specific KVM instance. To assist our investigation, please provide more detail on your environment:

Which public cloud provider is being used?
What flavor of KVM is being used?
Can you verify the MAC assignment on the virtualized platform for the 2nd NIC controller?

While we are investigating a potential test build for future evaluation, we cannot guarantee a timeline or specific results at this stage.

As a troubleshooting step, we recommend testing a downgrade to Toolpack version 3.1 or 3.2. These versions utilize a different driver handling profile for VirtIO that may be more compatible with your cloud’s MAC address assignment logic.

We are continuing to verify these findings and will provide updates as more data becomes available.

-Support

7

Hi Dave,

We’re using Huawei public cloud, and the flavor is 2vCPUs | 4GiB | ac9.large.2, and we tried many other flavors, all of them get the same error.

We already submitted a ticket the TS this issue. Their support guys told us, once the NIC controller is managed by DPDK, cloud infrastructure can do nothing for it, thus it wont get a MAC.

For the downgrade to Toolpack version 3.1 or 3.2, we’re newbies to ProSBC and at a investigating stage, can you pls share some links to do that? many thanks.

8

Hi,

I’m trying to understand the scenario better and see if I can help.

If you have urgency to put this ProSBC into production on KVM, I would suggest using version 3.1.145 (up to 3.1.147 should also work fine in this environment).

Please note that it is not possible to directly downgrade from 3.3.x to 3.1.x. To do that, you would need either:

  • A clean KVM image already running ProSBC 3.1.x, or

  • To manually install the 3.1.x installer via SSH and then manually adjust the active version in the toolpack configuration files.

While this manual procedure is relatively straightforward for TelcoBridges Support, it can be error-prone if you are not very familiar with the internal structure of the system. Because of that, I strongly recommend using a fresh 3.1.x KVM image, which avoids the need for support intervention and reduces risk.

Once you confirm that the NICs (LAN/WAN/VoIP) come up correctly on 3.1.x, you’ll have a solid baseline to validate whether the issue is related to the newer 3.3.x builds or to the KVM/driver configuration itself.

The KVM Images for version 3.3 ( We assume you used this onde) and 3.1 ( no longer available on the license portal ) are below:

Version 3.3.12 (Latest KVM Image): https://download.telcobridges.com/Images/3.3.12.53/prosbc_kvm_3.3.12.53_368_c0f9c42.qcow2.tar.gz

Version 3.1.145 filename reference (maybe there is a 3.1.147 version also): freesbc_openstack_kvm_3.1.145.26_324_aff7baa.qcow2.tar.gz

You should ask Telcobridges support for the download link.

While we often exchange tips and general guidance here on the forum, if you need real, hands-on and customized assistance to move this forward more efficiently, I can also offer paid technical support.

Feel free to reach out to me directly if you’re interested. That way, we can look at your specific environment and constraints and provide more assertive and direct help, beyond what is usually feasible in a public forum discussion.

Best regards,

Allan

9

Thanks for your feedback, yeah, as i said, we’re in an investigation stage and just want to verify whether this SBC can fullfill our business requirement. So we can sure use a fresh 3.1.x KVM image. So Just wonder where can i download this fresh 3.1.x KVM image?

BR,

10

Hi Julinpeng,

Try using this link here: Software Release 3.1.147

Let us know your test results. If you give us more details on Ali Cloud, I’ll talk to the team about setting up a testing environment. Which service are you using? I noticed there are a few different versions available.

-Support

11

Hi Dave

We’re working on Huawei Cloud instead of Ali Cloud, we’re trying to integrate ProSBC into our CallCenter as a border firewal. We will use like B2BUA, and other ASBC and ISBC features. Is there an old KVM release available?

12

Hi Julinpeng,

Yes, did you see my link above? I sent you a this. Software Release 3.1.147 .

Please let me know if this link is giving any problems.

-Support

13

I thought it was a software installation package instead of KVM qcow2 images. Ok, let me check it out first. Thanks.

14

Hi Junpeng,

I am unable to access the internal link for the freesbc_kvm_3.1.117.3_269_283188.qcow2.tar.gz file. I have a meeting with the team in the morning and will send you the link tomorrow. I think it is still under our older FreeSBC link.

It is possible to downgrade, and I can send you instructions. Are you trying to preserve the existing configuration, or can you wipe it and start from the beginning? It depends on how much you have configured on the existing installation.

Let me know either way; I will help you test with the older version.

Please note we have a new build coming out that has addressed some of the errors we have seen in your TBReport logs, but we have not tested it in the Huawei Cloud. We are planning a 3.3.13 release in approximately two weeks, if our validation is successful.

-Support

15

Hi Dave,

Its ok, we can wipe the configuration and start from scrutch, and we did not do any other configuration since the voip0 is not up. thanks.

16

Hi Dave

I tried to down it from the page you share, the download link is https://tbsoftware.s3.amazonaws.com/3.1.147.16/TBToolPack-3.1.147.16-Linux-centos7-x86_64-Install , and it turns out a file with the name TBToolPack-3.1.147.16-Linux-centos7-x86_64-Install, without any extention, is it an exe file in linux or a KVM image? I tried to change the file name with an extention .tgz, and it does not work.

17

Hey Julinpeng,

Awesome, if we can start from scratch this makes the downgrade easy. The file I sent is an install file, but I belive you need this file freesbc_kvm_3.1.117.3_269_283188.qcow2.tar.gz I referenced above. I should be able to post this for you tomorrow after I meet with the team in the morning EST.

-Support

18

Alright, I’ll be waiting for the qcow2 file. TIA

19

Hello Julinpeng,

I have some news.

We no longer have the freesbc_kvm_3.1.117.3_269_283188.qcow2.tar.gz available for customers. Let me know if you can use an .iso file. If yes, I have posted a 3.1.x iso release file below.

I am also testing a work-around that may work with your current build. The team discussed opening an account for tesing on Huawei Cloud, but it is not decided yet, but we will keep you posted.

Let me know if you have any trouble with this link.

-Support

https://dfb5dtp2yq5y7.cloudfront.net/Images/FreeSBC/iso/freesbc_centos7_x86_64_3.1.145.26.320_1e78e9c.iso

20

OK, alright, I can try this iso image, and will share the result once I get it work