Cisco Business Dashboard not finding switches

[KIT12]

Hi, I have a few cisco switches that will not show up in the business dashboard. One of the devices that cannot be seen is X.X.X.235.I looked at the probe.log and see it trying to communicate, and the only thing I can see related to one of these devices is the following:

22-07-05T15:15:50.801232-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Southbound[76fd700]: [XMLSysFunc::GetTimeZone] Get C0:64:E4:5D:57:7C timezone_id success!
2022-07-05T15:15:50.801290-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Southbound[76fd700]: HTTPTransport GetUrl url: https://x.x.x.235/wcd?{NameServerList}!
2022-07-05T15:15:50.801345-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: [WebHandleManager::GetWebHandle] https://x.x.x.235 GET
2022-07-05T15:15:50.801398-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: WebRequest get handle 0x7f4ad001a3b0
2022-07-05T15:15:50.801450-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: WebRequest get handle 0x7f4ad001a3b0 lock
2022-07-05T15:15:50.801542-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Other[76fd700]: [bool clp_utilities::string_con::IsDomainInUrl(const string&)] host: x.x.x.235 is not domain
2022-07-05T15:15:50.801602-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: END curl_multi_add_handle result_add
2022-07-05T15:15:50.801656-04:00 FLCISCOBD cbdprobe[2554]: INFO Webclient[76fd700]: addRequest https://x.x.x.235/wcd?{NameServerList}
2022-07-05T15:15:50.801719-04:00 FLCISCOBD cbdprobe[2554]: INFO Webclient[76fd700]: requests # 5
2022-07-05T15:15:50.801778-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: <addRequest>start threads by sending signal
2022-07-05T15:15:50.801913-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Other[76fd700]: [bool clp_utilities::string_con::IsDomainInUrl(const string&)] host: x.x.x.235 is not domain
2022-07-05T15:15:50.801977-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: [https://x.x.x.235/wcd?{NameServerList}]Start wait pthread_cond_timedwait_relative, timeout seconds[600]
2022-07-05T15:15:50.802047-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Other[76fd700]: [https://x.x.x.235/wcd?{NameServerList}]<wait> Get the lock.
2022-07-05T15:15:50.802111-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: 0x7f4b076fb900 WebRequest::wait https://x.x.x.235/wcd?{NameServerList}
2022-07-05T15:15:50.835587-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[fc6f7700]: Request completed: https://x.x.x.238/wcd?{DNSGlobalSetting}{DefaultDomainList}.
2022-07-05T15:15:50.835681-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[fc6f7700]: 0x7f4b09f00900 setComplete https://x.x.x.238/wcd?{DNSGlobalSetting}{DefaultDomainList}
2022-07-05T15:15:50.835743-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[9f02700]: [https://x.x.x.238/wcd?{DNSGlobalSetting}{DefaultDomainList}]Get the pthread_cond_timedwait result : 0, consumes 0 seconds
2022-07-05T15:15:50.835802-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[fc6f7700]: Request completed: https://x.x.x.235/wcd?{NameServerList}.
2022-07-05T15:15:50.835861-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[fc6f7700]: 0x7f4b076fb900 setComplete https://x.x.x.235/wcd?{NameServerList}
2022-07-05T15:15:50.835920-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[9f02700]: ~WebRequest handle 0x7f4acc011e00 unlock
2022-07-05T15:15:50.835980-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Southbound[9f02700]: [virtual bool findit_probe::sthbd::transport::XMLTransport::Get(const string&, std::string&, std::map<MsgCode, std::__cxx11::basic_string<char> >&)] IP[x.x.x.238], result: <?xml version="1.0" encoding="UTF-8" ?>#012<ResponseData>#012<DeviceConfiguration>#012<version>1.0</version>#012<DNSGlobalSetting type="section">#012<enbl>1</enbl>#012<domainNameQueryTimeout>2</domainNameQueryTimeout>#012<domainNameQueryRetries>1</domainNameQueryRetries>#012<domainNameQueryInterval>8</domainNameQueryInterval>#012<domainName>mydomain.com</domainName>#012<domainNameOwner>1</domainNameOwner>#012</DNSGlobalSetting>#012<DefaultDomainList type="section">#012<Entry>#012<sourceType>1</sourceType>#012<interfaceName></interfaceName>#012<preference>1</preference>#012<domainName>mydomain.com</domainName>#012</Entry>#012</DefaultDomainList>#012</DeviceConfiguration>#012<ActionStatus>#012<requestURL>DefaultDomainList</requestURL>#012<statusCode></statusCode>#012</ActionStatus>#012</ResponseData>
2022-07-05T15:15:50.836058-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: [https://x.x.x.235/wcd?{NameServerList}]Get the pthread_cond_timedwait result : 0, consumes 0 seconds
2022-07-05T15:15:50.836113-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Webclient[76fd700]: ~WebRequest handle 0x7f4ad001a3b0 unlock
2022-07-05T15:15:50.836185-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Southbound[76fd700]: [virtual bool findit_probe::sthbd::transport::XMLTransport::Get(const string&, std::string&, std::map<MsgCode, std::__cxx11::basic_string<char> >&)] IP[x.x.x.235], result: <?xml version="1.0" encoding="UTF-8" ?>#012<ResponseData>#012<DeviceConfiguration>#012<version>1.0</version>#012<NameServerList type="section">#012<Entry>#012<addrType>1</addrType>#012<IPAddr>x.x.x.27</IPAddr>#012<preference>1</preference>#012<owner>1</owner>#012</Entry>#012</NameServerList>#012</DeviceConfiguration>#012<ActionStatus>#012<requestURL>NameServerList</requestURL>#012<statusCode></statusCode>#012</ActionStatus>#012</ResponseData>
2022-07-05T15:15:50.836257-04:00 FLCISCOBD cbdprobe[2554]: INFO Inventory[76fd700]: [DeviceIsReachable] device[C0:64:E4:5D:57:7C] port[443] is reachable
2022-07-05T15:15:50.836316-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Southbound[76fd700]: [virtual bool findit_probe::sthbd::transport::XMLTransport::Get(const string&, std::string&, std::map<MsgCode, std::__cxx11::basic_string<char> >&)] IP[x.x.x.235] responseData: <?xml version="1.0" encoding="UTF-8" ?>#012<ResponseData>#012<DeviceConfiguration>#012<version>1.0</version>#012<NameServerList type="section">#012<Entry>#012<addrType>1</addrType>#012<IPAddr>x.x.x.27</IPAddr>#012<preference>1</preference>#012<owner>1</owner>#012</Entry>#012</NameServerList>#012</DeviceConfiguration>#012<ActionStatus>#012<requestURL>NameServerList</requestURL>#012<statusCode></statusCode>#012</ActionStatus>#012</ResponseData>
2022-07-05T15:15:50.836384-04:00 FLCISCOBD cbdprobe[2554]: DEBUG Southbound[76fd700]: [bool findit_probe::sthbd::transport::XMLTransport::ResponseParse(const string&, std::map<MsgCode, std::__cxx11::basic_string<char> >&)] response: <?xml version="1.0" encoding="UTF-8" ?>#012<ResponseData>#012<DeviceConfiguration>#012<version>1.0</version>#012<NameServerList type="section">#012<Entry>#012<addrType>1</addrType>#012<IPAddr>x.x.x.27</IPAddr>#012<preference>1</preference>#012<owner>1</owner>#012</Entry>#012</NameServerList>#012</DeviceConfiguration>#012<ActionStatus>#012<requestURL>NameServerList</requestURL>#012<statusCode></statusCode>#012</ActionStatus>#012</ResponseData>

Is there something I'm missing? I can only find 2 our of 6 switches. 

Thank you.

[marce1000]

 - Check if the switches are compatible according to this document : https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/cisco-business-dashboard/technical-reference/b_CBD_Device_Support_List.html

 M.

[KIT12]

I checked. They a combination of 48 port and 24 port switches.

Product ID is SG350-52MP-K9 V02

I'm assuming because it's the SG350 line its supported?

[marce1000]

               - Check (minimum) required firmware version(s) too.

 M.

[Georg Pauwen]

Hello,

odd indeed. I assume you have hit the 'Refresh' button (in order to rediscover the network and update the topology) ?

[KIT12]

Yes I have done that. It finds every other device on the network except for the cisco switches. I made sure their gateways, and subnets were correct (they are located on the same subnet/vlan as the CBD) I can ping the devices and access the GUI of these switches. I can ping the CBD from them.  I also ,have SNMP turned on with it set as the management. I'm at a loss here. Maybe I should try rebooting the switches? That's probably about the only thing I haven't tried yet.

[Georg Pauwen]

Hello,

odd indeed. A reboot might indeed help. If you start with rebooting one switch and it is discovered, you know that this is the solution...