SG350XG - %SYSLOG-F-OSFATAL: caught segmentation fault - BONJOUR task

[carnyx.io]

Hello,

I havec several switches SG350XG-2F10.

Since i activated the "BONJOUR" protocol to connect switches to Cisco Business Dashboard, i regularly have emergency errors :    %SYSLOG-F-OSFATAL: caught segmentation fault exception 

%SYSLOG-F-OSFATAL: caught segmentation fault exception at address 0xaa4ff6f5 signal-num = 11 (SIGSEGV) signal-code = 2 (SEGV_ACCERR) reg[00] = 0xaa4fc3f3 reg[01] = 0xaa4fc356 reg[02] = 0x0 reg[03] = 0x9f reg[04] = 0x339f reg[05] = 0xaa4fc406 reg[06] = 0x50e688e4 reg[07] = 0x50e689dc reg[08] = 0x0 reg[09 ] = 0x50e688e3 reg[10] = 0x50e688dd FP = 0x0 IP = 0xf3 SP = 0x50e68798 LR = 0xc1d3ec PC = 0xc1a518 CPSR = 0xa0030010 Fault Address = 0xaa4ff6f5 Trap no = 0xe Err Code = 0x17 Old Mask = 0x0 ***** FATAL ERROR ***** Reporting Task: BNJR. Software Version: 2.5.9.54 (date Nov 29 2023 time 14:36:03) base_ad

My firmware is the last one i think : 2.5.9.54

What can i do to connect my switches to CBD without BONJOUR errors ?

Best regards

GE

[bigevilbeard]

Looks like a bug https://bst.cisco.com/quickview/bug/CSCvo48821 - but i dont see a fix?

[carnyx.io]

hello and thanks

My switches have 2.5.9.54 firmware and it's not a SNMP fault but BONJOUR protocol fault.

So it's not really similar

Best regards

[Mark Elsen]

  - @carnyx.io               It remains a bug , if you are on latest firmware involve cisco :
                                                                 https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

   M.

[Mark Elsen]

 - @carnyx.io  This bug report : https://bst.cisco.com/bugsearch/bug/CSCvo48821?rfs=qvlogin has  a Fixed status. But Known Fixed releases is empty. That means that developers have resolved the issue , but ir is not yet incorporated in a production release. Contact Cisco's TAC to ger an ETA on that , 

 M.

[carnyx.io]

Thanks Mark but this product has exceeded Last Day of Support date (2025-06-30). Apparently I can't contact support on this EOL range of switches...

Do you know, if i can connect my SG350XG switches to Cisco Business Dashboard without BONJOUR protocol ?

Perhaps with SNMP or CDP ?

Oh, how I miss Cisco Network Assistant on the old C2960G and C3560X switches. It worked better and with more features than CBD.. 

Best regards

GE

[Mark Elsen]

  - @carnyx.io      >....Do you know, if i can connect my SG350XG switches to Cisco Business Dashboard without BONJOUR protocol ?
                           That looks like a yes : Ref  https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/cisco-business-dashboard/admin-guide/b_Cisco_Business_Dashboard_Admin/b_CBD_chapter_00.html
                         >....In a direct managed network, you will need to connect the first device to the Cisco Business Dashboard manually. Then, this device reports information such as CDP, LLDP, and mDNS (aka Bonjour) to Dashboard. This information is used to identify additional devices in the network, 

  M.

[carnyx.io]

Indeed, I could connect only one switch per site, and let the others be discovered via CDP. This would undoubtedly limit the number of switches affected by crashes. But it's still a last resort...

I also tried activating the CBD probe on one of the switches, but the results weren't conclusive.

I'll dig a little deeper, but it's not very serious of Cisco to offer unfinished solutions.

They remove CNA, which was very good, and replace it with CBD, which is worthless.

I'm a long-time user, and I find that the quality of Cisco products has deteriorated significantly over time

Best regards

GE

[Mark Elsen]

  - @carnyx.io   I can agree with those observations but these devices are long EOL and now also past support:
                         https://www.cisco.com/c/en/us/products/collateral/switches/350x-series-stackable-managed-switches/eos-eol-notice-c51-743290.html  as you stated already.

                        Consider modernizing the infrastructure : https://www.cisco.com/c/en/us/solutions/small-business/selector-tool.html

  M.

[clarkwa]

I'm engineer from CBD team, actually, CBD support discovery SMB device through CDP, but for CDP discovery, you need to configure CDP's device ID format as MAC address, if you still have problem for discovery SMB device, please feel free to ask, and I will do my best to assist you.

[carnyx.io]

Hello clarkwa,

Thank you for your reply.

I had to disable the Bonjour protocol on my SMB switches because they were crashing regularly (segmentation fault) when this protocol was enabled 

I don't undrestand that a protocol can be implemented and not tested before production deployment !

On the SMB switches, the "device type ID" is set to "MAC Address" on "CDP Local Information" screen. Apparently, it's not possible to select anything else. So it' OK.

On CBD web site, I can still see my SMB switches even after disabling Bonjour. So discovery seems to work without Bonjour.

Good.

But I don't know if it's related or not, but the Topology feature is no longer working. On the screen, the message "Loading Topology" just keeps spinning indefinitely

I'm going to restart the VM to see if that helps.

This isn't a personal criticism, but really, CBD is inferior to CNA in terms of functionality and visibly more fragile... It feels like we're taking a step backward.

[clarkwa]

Hello 

We sincerely apologize for the Bonjour crash issue. However, the SG350 device has reached its End of Life (EOL), so the device team will no longer release new versions. If you’d like to have a better experience, we recommend replacing it with a newer switch model. These newer products have deeper integration with CBD.

Regarding your feedback that CBD is not as good as CNA, we also encourage you to share more suggestions, as we are continuously improving it to create more value for our customers.

However, it’s perfectly fine if you prefer to continue using the SG350. Next, please help collect the relevant information so that I can assist you in resolving the topology issue, so need you do follow steps in orderly to collect info:

1. Please go to the Network page and the Inventory page, and take two screenshots, as shown in the two example images below.

2. Go to CBD "System->Log Settings" page, and configure log setting as shown in pic below.

3. Then, go back to the topology web page and load the topology so that the relevant debug logs for the topology can be collected.

4. Finally, return to the Log Setting page and download the log file.