netbotz appliance bot post login failed

DCIM_Support · ‎2020-07-04

DCE keeps event log keeps listing netbotz appliance bot post login failed

this from a 550. I have 6 other 550's and they all seem to work fine

Any ideas / setting I have missed?

DCIM_Support · ‎2020-07-04

Hi david.whitfield3,

Please, share some screenshots, where you can clearly see what you are reporting. This will help solve your problem faster and better.

With respect.

DCIM_Support · ‎2020-07-04

DCIM_Support · ‎2020-07-04

Hi david.whitfield3,

Ok, then double check the correctness of the NetBotz appliance settings with the IP-address 10.224.15.103 in the APC Advanced View software.

To do this, select the menu item Tools -> Advanced -> Advanced View POST-only mode... and in the Advanced View POST-only mode Configuration window check the validity of the authentication data for your DCE-server.

With respect.

DCIM_Support · ‎2020-07-04

Hello - Thanks for the response

checked that, it is the same as the other working bots - no entry. I added one anyway and fault remains

Looked at message log, I get this

DCIM_Support · ‎2020-07-04

With a similar problem, I already dealt with a long time ago (back in early 2014 😀. To begin with, please tell us whether your DCE-server reads information from the sensors that are connected to this problem NetBotz appliance (with IP 10.224.15.103)?

DCIM_Support · ‎2020-07-04

Also tell me the version of the DCE-server, the version of the problematic NetBotz appliance, and the version(s) of the other NetBotz appliance(s) (which have no problems).

With respect.

DCIM_Support · ‎2020-07-04

Hi. DCE is 7.4.3 bot 550 is 4.61. But you miss the point. I have multiple bots. It is only this one that has the error report

DCIM_Support · ‎2020-07-04

Hi david.whitfield3,

I also had a multiple bots, but the problem was with just one 😀.

Ok, to help you quickly, answer two questions:

whether your DCE-server reads information from the sensors that are connected to this problem NetBotz appliance (with IP 10.224.15.103)?

And messages "Netbotz Appliance Bot Post from IP address 10.224.15.103; login failed." still appear on the DCE-server with a periodicity of 10 minutes?

With respect.

DCIM_Support · ‎2020-07-04

DCE 7.4.3

DCE can see all device sensor values from bot

Netbotz 4.6.1 av_20170620-1609

all other bots are exactly the same version , but they do not report error

DCIM_Support · ‎2020-07-04

Hi david.whitfield3,

checked that, it is the same as the other working bots - no entry. I added one anyway and fault remains

First, delete the entry for the DCE-server that you added. I.e., the window Advanced View POST-only mode Configuration should be empty (as well as on other bots).

Secondly, in the APC Advanced View software, click the Configuration -> Periodic Reports button. In the Periodic Reports Configuration window that opens, check the Periodic HTTP Report (and also in the Periodic FTP Report) if there was mistakenly enabled reports sent to your DCE-server?

Third, try to reboot the problematic NetBotz and then check again: if there is a message appear every 10 minutes about the failed login from this NetBotz? Check again, not just the presence of sensors from this NetBotz in the DCE-server, but the fact that the sensor values are updated regularly with the frequency that is configured in the DCE-server by Device -> NetBotz Appliance Communication Settings -> NetBotz Appliance Polling...

With respect.

DCIM_Support · ‎2020-07-04

removed entry as soon as it did not fix it

no periodic reports are set for anything on this or any other bot

reboot it ! - Really ?

polling was first thing I checked - data collection at 1 minute, monitoring at 5 minute, so no correlation

DCIM_Support · ‎2020-07-04

reboot it ! - Really ?

Yes, if you are 100% sure, that all settings are correct, then rebooting NetBotz is one of the options for effective verification (this is from my experience). So you can check once again whether NetBotz makes an incorrect login attempt to your DCE server every 10 minutes. It's easy to check.

With respect.

DCIM_Support · ‎2020-07-04

Dear david.whitfield3,

Have you been able to solve this issue or not?

With respect.

DCIM_Support · ‎2020-07-04

Hello,

Thanks

No, the problem remains the same as per the original screen shot - bot post login failed - reported every 10 minutes by DCE. ISX polling is set at Data collection 1 minute, monitoring 5 minutes

Regards

DCIM_Support · ‎2020-07-04

Dear david.whitfield3,

Tell, please, have you tried to reboot or poweroff/poweron NetBotz appliance or not?

With respect.

DCIM_Support · ‎2020-07-04

Yes I have, with respect telling someone to reboot the appliance is hardly an innovate approach. I posted on here to get expert comments / advise from fellow expert users, not to be told switch it on / off again

DCIM_Support · ‎2020-07-04

And nevertheless, as you commented on in topic , in another case it helped for you:

...I powered off the Netbotz for 3 minutes then reconnected and all fine. you MUST leave them off for 3 minutes or it does not solve it

😉

DCIM_Support · ‎2020-07-04

You really are a sad little man.

I offered more than state "reboot it", explaining the rational behind it and more detail. But if that's the best you can do, just searching for an argument - I will leave the forum.

I have 10 years of working with Netbotz and its the forums loss to be left with the likes of you.

I hope you feel good about yourself.

Signing off

DCIM_Support · ‎2020-07-04

@David Whitfield

I'm having the same problem as the guy stated he is having. And I have tried all the steps you told him to. Can you help me please

DCIM_Support · ‎2020-07-04

I am also experiencing the same issue and tried all steps above.

Has there been any solution or workarounds?

Kind regards

DCIM_Support · ‎2020-07-04

Dear Jesse Hall and juice,

As I already reported above in this topic, for me it worked fine. That is, I found the cause of the above error messages in the DCE access logs and resolved it.

But if all these methods do not work for you at all (?why I don’t know?), then I can offer the last radical method: restore the NetBotz-4.x appliance to factory defaults. How to do this remotely without losing the IP configuration is well written in topic .

I personally used this method several times. Since, indeed, there are cases when this is the only way to solve a problem with a NetBotz-4.x appliance and not otherwise (see for example my resolved topic ).

Hope this helps you.

With respect.

DCIM_Support · ‎2020-07-04

Hi there david.whitfield3, have you manage to fix the issue ?

Kind regards

DCIM_Support · ‎2020-07-04

Dear david.whitfield3,

We are all here at HELP CENTER EcoStruxure IT, and I, among others, are interested in helping you solve the problem. Perhaps that's why you asked for help here. And since your problem is not solved, it means that there is not enough information to solve it. Therefore, if it's not difficult for you, please share for experts / fellow expert users here, are the screenshots of your problem NetBotz appliance like mine (where red, I highlighted information that is important).

About window (do not forget to hide serial and MAC addresses):

Configuration window:

Network Interfaces window:

Alert Action -> Send using HTTP POST -> Edit Alert Action window:

Latest DCE-server web-GUI Event Log window, as you did last time:

Next, for example, your steps to solve the problem can be as follows. We have three components: NetBotz appliance, DCE-server, network infrastructure with other network devices (this is also important). Using, for example, a router or similar external network device, make to capture network traffic with its subsequent analysis on the side of the NetBotz appliance and on the side of the DCE-server. Further, it all depends on the results of the analysis of network traffic.

If the NetBotz appliance is indeed the source above the specified network traffic to the DCE-server side (not vice versa), you first need to make a backup configuration of the NetBotz Appliance. Then this backup configuration must be sent to Schneider Electric employees for detailed analysis.
If the NetBotz appliance is not a source above the specified network traffic towards the DCE-server (not vice versa), but the DCE-server still registers failed login attempts (like you on the screenshot), it is necessary to find out which of the network devices in the your network does this.
In addition, if the above traffic does not exist at all, then to verify the correct functioning of the DCE-server, you can capture system logs from your DCE-server, according to topic . And again send these log files for detailed analysis to Schneider Electric employees. This can also facilitate or speed up the resolution of your problem.

In addition, if the problem is all the same in your NetBotz appliance, then experts / fellow expert users can ask you to do it:

Restart or turn off / turn on the NetBotz appliance.
Reset the NetBotz appliance settings to their factory defaults and then restore them from the backup configuration.
Update the NetBotz appliance firmware with all the default settings restored.
And the last option - it is replaced with another known good NetBotz appliance.

If you have any questions, please ask.

With respect.

DCIM_Support · ‎2020-07-04

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