LAN/WAN Interfaces Not Available

[bhoover]

I Installed FreeSBC on bare metal. I have 10 network interfaces. Before configuration I verified all the interfaces were available on the console (ifconfig). During the initial configuration wizard using the GUI, all 10 could be seen so I configured 2 as management and the other 8 as LAN/WAN. After the configuration completed I can now only see the 2 management interfaces on the console and in the web GUI all of the LAN/WAN interfaces (renamed voip0, voip1, etc) all show as being unavailable. The config fail log says 'Restore the IP interface on the system or stop using it in the configuration.'

[Admin]

You need to be sure the NICs in the server must be our supported NIC list. Please check the following link for supported NIC list

https://docs.telcobridges.com/tbwiki/Supported_NICs

If your NIcs are under supported NIC list an getting problem again please contact with support@telcobridges.com.

[bhoover]

All of the NICs are on the supported list:

1a:00.0 Ethernet controller: Intel Corporation Ethernet Connection X722 for 10GBASE-T (rev 09)
1a:00.1 Ethernet controller: Intel Corporation Ethernet Connection X722 for 10GBASE-T (rev 09)
5e:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
5e:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
af:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
af:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
d8:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)
d8:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)

I do see in my messages file that the tbrouter service is failing to start. Further investigations shows these errors in the tbrouter logs:

06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetCoresFromConfig: 'core' number out of range (64 > 63) for device '00:0a:cd:36:9e:14' (8200000E) CTBRouterAppDpdkInitializer.cpp:2204
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetPortRequiredMbufs: Error getting core count (8200000E) CTBRouterAppDpdkInitializer.cpp:2081
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetCoresFromConfig: 'core' number out of range (64 > 63) for device '00:0a:cd:36:9e:14' (8200000E) CTBRouterAppDpdkInitializer.cpp:2204
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetCoresFromConfig: 'core' number out of range (68 > 63) for device 'b4:96:91:3f:f6:90' (8200000E) CTBRouterAppDpdkInitializer.cpp:2204
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetPortRequiredMbufs: Error getting core count (8200000E) CTBRouterAppDpdkInitializer.cpp:2081
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetCoresFromConfig: 'core' number out of range (68 > 63) for device 'b4:96:91:3f:f6:90' (8200000E) CTBRouterAppDpdkInitializer.cpp:2204
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetCoresFromConfig: 'core' number out of range (68 > 63) for device 'b4:96:91:3f:f6:91' (8200000E) CTBRouterAppDpdkInitializer.cpp:2204
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetPortRequiredMbufs: Error getting core count (8200000E) CTBRouterAppDpdkInitializer.cpp:2081
06th, 01:10:32.320+0000 TBERR CTBRouterAppDpdkInitializer::GetCoresFromConfig: 'core' number out of range (68 > 63) for device 'b4:96:91:3f:f6:91' (8200000E) CTBRouterAppDpdkInitializer.cpp:2204
06th, 01:10:32.320+0000 TBERR Configuration file '/usr/lib/tb/toolpack/setup/12358/3.1/current_nic.json' is invalid: 00:0a:cd:36:9e:14 Error getting Required Mbufs from config00:0a:cd:36:9e:14 Error getting core count from configb4:96:91:3f:f6:90 Error getting Required Mbufs from configb4:96:91:3f:f6:90 Error getting core count from configb4:96:91:3f:f6:91 Error getting Required Mbufs from configb4:96:91:3f:f6:91 Error getting core count from config

[lmorissette]

I believe you have assigned to many interfaces to the system. The initial process will assign enough CPU cores to network interfaces to be able to withstand network attacks.
However, the number of 64 or 68 reserved cores surprises me, so maybe the system is allocating too many CPU cores for some network interfaces. Send a TB report to support so we can check (https://docs.telcobridges.com/tbwiki/TBReport).

Some questions:
. Is it necessary to have all these network interfaces? 10Gbps interfaces can transport 50,000 sessions of SIP. Please explain the justification of having so many interfaces.
. Have you configured "dedicated cores" for the network interfaces? If so, you may want to uncheck this for internal interfaces (the ones not facing the public network) when configuring the interfaces from the initial web portal configuration.

[bhoover]

I don't really need that many interfaces. The server was built by someone else and they installed 3 2-port NIC cards for some reason. I'm only actually using 3 of the interfaces in my configuration (plus the management). Is there a way to "delete" the additional interfaces or do I have to physically remove them from the server?

I emailed the TB Report to support.

Thanks for your help.

-Ben

[Sponsored content]