Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
The purpose of this resolution is to inform users of STB Ethernet NIM's (Modbus TCP and Ethernet/IP) of a communication issue that may occur under a specific condition.
Goals and Symptoms
If an STBNIP2212 was powered on for 828 consecutive days, it would lose Modbus communications for 20 minutes, recover on its own and will not fault again with this behavior for another 828 days.
Facts and Changes
Causes and Fixes
CauseThe 828 consecutive days powered on relates to an internal clock value in the STBNIP2212. When this specific clock value is reached, an issue occurs with the ARP cache creating a 20 minute Modbus TCP communication loss. After this 20 minute period, the communications will recover on its own. ICMP service may or may not be immediately affected by this event but will recover at the same time as Modbus TCP communications.
How to Manage the Issue with Existing Firmware
If at any time, the NIP is power cycled, its clock count value resets to zero and starts a new 828 day operating period. This can be done during any scheduled maintenance period within the 828 day time frame to avoid this event.
New firmware for each of the 3 affected PRODUCTS will be posted to resolve this issue but a schedule for availability was not confirmed at the time of this posting.