> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/troubleshooting-and-support/troubleshooting-tips-and-actions/how-to-get-rid-of-sub-optimal-warning.md).

# How to Get Rid of Sub Optimal Warning

## "Sub optimal" Waning

```
Gateway -> Routes
```

<figure><img src="/files/gM0SFyWxrD2CAeHtFfvq" alt=""><figcaption></figcaption></figure>

## Reason for the Waning

The reason for this is that some Nics (Azure, vmxnet3, e1000, ixgbe vf) report a RETA size of 0 while reporting multiple rx queues, meaning they can not support multiple CPUs. However TBRouter is not aware of this limit on those Nics then initiate the Cores on the Nics

### Solutions

We have ticket 23762 to improve the tbrouter to support RSS when we have a RETA table of 0. You will experience this warning before the fix. You can: 1-Just simply ignore the warning. 2- Change the nic.json to remove the section with the extra cores (so those cores can be used for something else) by following the below steps.

### Steps to Get Rid of The Warning

1\. ssh to the SBC host and do shell command:

locate nic.json Output: /usr/lib/tb/toolpack/setup/12358/3.0/dynamic\_nic.json /usr/lib/tb/toolpack/setup/12358/3.0/nic.json /usr/lib/tb/toolpack/setup/12358/3.0/validated\_nic.json /usr/lib/tb/toolpack/setup/12358/3.1/current\_nic.json /usr/lib/tb/toolpack/setup/12358/3.1/dynamic\_nic.json /usr/lib/tb/toolpack/setup/12358/3.1/nic.json /usr/lib/tb/toolpack/setup/12358/3.1/validated\_nic.json /usr/lib/tb/toolpack/tbrouter/current\_nic.json

2\. Do a copy of the existing nic.json (only need to operate the version your SBC is running)

e.g. cp /usr/lib/tb/toolpack/setup/12358/3.1/nic.json /usr/lib/tb/toolpack/setup/12358/3.1/nic\_bak.json

<br>

3\. Edit nic.json

e.g. vim /usr/lib/tb/toolpack/setup/12358/3.1/nic.json

4\. Remove the section with the extra cores

e.g. below is the section for one Nic with 2 cores, simply remove the section of "core": 2,

```
       "00:50:56:95:ba:0e": {
           "cores": [
               {
                   "core": 1,
                   "rx_nb_queues": 2
               },
               {
                   "core": 2,
                   "rx_nb_queues": 2
               }
           ],
```

Make it simply like this:

```
       "00:50:56:95:ba:0e": {
           "cores": [
               {
                   "core": 1,
                   "rx_nb_queues": 2
               }
           ],
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/troubleshooting-and-support/troubleshooting-tips-and-actions/how-to-get-rid-of-sub-optimal-warning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.