DCE sends a Netbotz devices critical comunication error message

[DCIM_Support]

Dear guys,

Our customer is worry because DCE is often sending a Netbotz devices critical comunication error message. The message in sent by email to the StruxureWare Data Center Expert administrators only.

The comunication error is auto solved after two or three seconds and the customer switch log is also reporting his problem. Actually it is happening with three devices, one 570, one 500 and one 355 devices. Also Netbotz devices hasn't any problem.

How can I know the cause of this problem and how and I solve it?

Best regards,

Enric

(CID:105466226)

[DCIM_Support]

Dear Enric,

Here are my suggestions:

• Please make sure that firewall settings or network issues do not block communication over port # 80 & Port # 443 between Struxureware DCE and Netbotz appliance
• Please check the Netbotz appliance polling settings in DCE, and see if the same behavior with increased Poll rate  

• I also would like to make sure that Netbotz appliance firmware and DCE version is the latest version
• Make sure that the network settings such as DNS IP addresses are correct

Were the netbotz appliances detected via Port # 80? 

Are the netbotz appliances on the same network? 

Do you have any Netbotz which is communicating with DCE without loss of communication on the same network or different network? This can help you to figure if its related to network issue. 

It is also a good idea to see from when these loss of communication alerts started for netbotz appliance from DCE. Do you have any sensors not communicating with the netbotz appliance? Was there any changes made to the netbotz appliance? 

regards,

Bala

(CID:105466243)

[DCIM_Support]

Dear Bala,

There are no issues with firewall and network with ports 80and 443.

The Netbotz Appliance Polling is set to 1 minute for data collection and 1 minute for monitoring. The customer wants this configuration and we cannot increase these values.

We have the latest version of Netbotz firmware and DCE.

All Netbotz appliance and DCE are in the same network and the customer has other Netbotz appliance in the same network wich doesn't loss communication.

When a communication is lost with a Netbotz, all sensors connected to this Netbotz also loss communication.

Maybe can help you an information. This morning I don a ping -t to some Netbotz and I've could see sometimes the response time was higher than 2500 ms. If you want I have the ping output in a text file.

Best regards,

Enric

(CID:105466981)

[DCIM_Support]

As far as I know, Network latency which you mentioned is very high. Since Polling is set to 1 minute and if the Netbotz appliance is not able to respond to DCE polling, then DCE will respond with loss of communication or timed out errors. I think one of the reasons could be the Network or network traffic related.

(CID:105466982)

[DCIM_Support]

Hi Bala, I understand your suggestions but this system has been running without any error for some months with the same transactions and now is getting these errors. The DCE version is 7.2.6, will be better to upgrade to 7.3.1?

(CID:105467380)

[DCIM_Support]

Dear Bala, I've increased the polling time and also upgraded the DCE version to the last version (7.3.1) The Netbotz is already with the latest version (4.5.1) and the problem hasn't solved. The customer network team has checked the network and all it's right but the problem is still happening. How can we avoid this problem? Best regards, Enric

(CID:105468843)

[DCIM_Support]

Hi guys!

I am having the some trouble with one of my costumers and I would like to know how Enric  solved is trouble, If its done could you help me solving the same trouble????

(CID:126182243)

[DCIM_Support]

Good Morning

some time ago I had the same problem and I was able to solve it by changing the MTU parameter in network settings, this parameter resizes the packages sent by netbotz.

(CID:129411361)

[DCIM_Support]

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