Setting up IP addresses for loop of multiple ArmorStart

[dvanovec]

Hi guys, so I'm using BOOTP/DHCP tool in my virtual machine for setting up an IP addresses for basically everything.
My only issue is always with ArmorStarts, we have lets say 20 ArmorStarts in one loop and when I open BOOTP it find all MAC Addresses, but after setting up IP addresses and disabling BOOTP/DHCP for 2 ArmorStarts the next I want to set up and disable BOOTP/DHCP will just ignore me and show me some message, I need to manually cycle power and wait for awhile until I can set up next armorstart, I need to repeat this every 2 ArmorStarts I set up which is quite annoying and it is slowing down the process.

Do you have any idea what could cause this or have similiar problem?
btw. all ArmorStarts in loop are same models (294E-FD1P5Z-G3), note that this problem does not occur in case of ArmorBlocks/PowerFlex/Kinetix ...

Thanks for your :site:help!

 

[Contr_Conn]

..show me some message..

Can you get the exact message?

Based on your description, looks like the Armorstart stops sending BOOTP requests after a few unsuccessful attempts, taking a some Auto-IP address.

While this is not a desired behavior, I saw some devices doing that. The only way I know to re-trigger the requests is to cycle power. Also, some devices reduce the request rates after a few attempts, sending them once a minute or even slower.

You can probably run a Wireshark trace to verify Armorstart behavior.

 

[dvanovec]

Can you get the exact message?

Based on your description, looks like the Armorstart stops sending BOOTP requests after a few unsuccessful attempts, taking a some Auto-IP address.

While this is not a desired behavior, I saw some devices doing that. The only way I know to re-trigger the requests is to cycle power. Also, some devices reduce the request rates after a few attempts, sending them once a minute or even slower.

You can probably run a Wireshark trace to verify Armorstart behavior.

I'm currently not on-site so I can't tell you exactly what message did it show.
I can set up IP address on them and later can ping them without any issue, just can't disable DHCP on them, so maybe, as you mentioned, they stop sending DHCP request because they were sending it for too long without any response, while I set up different armorstart because I try to follow the loop sequence.

Once I'm back on-site I will try to run Wireshark and get back to this topic.

Thank you!

 

[Contr_Conn]

I can set up IP address on them and later can ping them without any issue, just can't disable DHCP on them...

Hard to guess without having any details. Need to have the exact fault message and even better to get a Wireshark.
My guess is that module established the connection to the controller and this state prevents any changes.
You may try to inhibit all devices in IO configuration before assigning addresses or assign addresses on the isolated network.
Again, this is just a guess, maybe other reasons.