StruxureWare does not discover Netbotz 570

[DCIM_Support]

Hello! 

I've recently installed a StruxureWare VM and a Netbotz 570 in our datacenter. For some reason StruxureWare will not discover the 570, which is on the same subnet as the StruxureWare VM. I have other Netbotz devices at remote locations that are discovered with no problem. Any idea why the 570 would not show up? 

I can access the 570 with the NetBotz Advanced View software, so I assume it is functioning correctly. 

(CID:122094230)

[DCIM_Support]

Hi Sam,

There is no reason for DCE to be unable to discover a NetBotz 570. Things you need  to verify first however are things like:

• Are there enough node licenses available on DCE?
• Are you providing the correct admin user name and password during discovery?
• Are you using the correct protocol (ie HTTP / HTTPS VS SNMP)?
• Does your VM or router have specific firewall rules that could be blocking communications between the 2 systems?
• What version DCE? What version Botzware on the 570?

If this same server can discover devices in a remote network but not on it's own segment, it is likely something in the configuration as suggested in the above questions.

Thanks,

Steve

(CID:122094239)

[DCIM_Support]

Hi Steve, thanks for the reply! 

• We are good on licenses.
• Credentials are correct. As mentioned, I can log in from the Netbotz Advanced View software. 
• When creating the discovery, I used the "Netbotz Appliance" option. Should I use something else? 
• The VM does not have a firewall between it and the 570 appliance unless there is a firewall built into the VM that I'm not aware of. 
• DCE is version 7.4.3, Netbotz 570 is 4.5.4.

Agreed that it's most likely a configuration issue, I'm just not sure where. Any other ideas? 

(CID:122094698)

[DCIM_Support]

Hi Sam,

No, that's the correct discovery type. Some times people try adding a 570 using an SNMP discovery, I just wanted to verify you're not doing that. The 200 and 250 would use SNMP though (I know, may be confusing) but not the 3xx, 4xx, and 5xx series units.

You may also want to double-check the IP Filter applet on the NetBotz appliance. That's a firewall too.

If you've backed up the NetBotz appliance, you can also try resetting the config just to be sure there's nothing corrupt or wrong with the bot. To do this without changing the IP of the appliance (It will wipe out everything else...that's why you back it up) just go to the web page of the appliance and append /unconfig or http:///unconfig as per k-base FA158175.

The other thing you can try is to use the "Post-Only mode" option. This is on the NetBotz appliance under Tools -> Advanced.

What post only mode does is it causes the NetBotz to initiate communications instead of the DCE server. Much like when you're on the internet, an internet site can't start communications with your computer until your computer initiates that contact. If this works, then there's likely something blocking the DCE server from reaching out to the bot using HTTP or HTTPS. 

Steve

(CID:122094715)

[DCIM_Support]

Hey Steve, 

Sad to report that I've tried all options above and have still had no luck. Is it possible there is a problem with the 570? Do I need to open a ticket with support. 

The only other issue I can think of is that I haven't been able to register the 570 since it does not have a connection to the internet. Would that make any difference? 

(CID:122095220)

[DCIM_Support]

Hi Sam,

DCE communicates with the NetBotz using the same protocol used by advanced view and by the web. If you can access the appliance using those options, there is no reason on the appliance that it should not communicate with DCE. A hardware issue wouldn't cause this and still allow web and Advanced View.

I doubt it's a firmware issue but you may also want to try to re-flash the firmware and wipe out all data and potential corruption. K-base FA176133 can walk you through that procedure. Do not use the "keep" option and do not re-import any backups.

Registration of the appliance does not matter when it comes to communications, only for potential support and license key activation purposes. 

You can always open a ticket with your local support and they'll work through this type of troubleshooting with you. Maybe being on the phone at the time of troubleshooting will help. It's also possible that a remote session can be established and they can actually see and better understand what it happening. 

Steve

(CID:122095227)

[DCIM_Support]

Hi sam.killian,

Have you solved the problem or not? And if so, how?

With respect.

(CID:122096008)

[DCIM_Support]

I have not. I will contact support and report back but I've had other, more pressing issues come up, so I have not had a chance to speak to anyone. 

(CID:122096266)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.