Technical FAQs

Ask a Question

STBNIP2212 Advantys Non-RoHs Ethernet NIM Firmware Upgrade - Exec v.2.32

Release Notice

The purpose of this resolution is to inform STBNIP2212 users that the Exec., Kernel, and Web pages have been upgraded to the following:

    • Exec v.2.32
    • Kernel v. 2.04
    • Web page v.1.20.05

Goals and Symptoms

Exec file, nip2212_upgrade_[k]_v2.04.06_[fw]_v2.32_[web]_v1.20.05.exe, is now available and will automatically run the loader utility program when executed and prompt the user to enter the IP address of the Ethenet NIM. The Exec, Kernel, and web files will load sequentially and then reboot the NIM when completed.

Facts and Changes

The new Exec., Kernel and web versions are field upgradable and will work with any STBNIP2212 Ethernet NIM hardware whose firmware is version 2.70 or higher. This Exec cannot be loaded into NIMs that have an SV 2.30 or lower.

  • STBNIP2212's whose Exec versions are 2.3x or less are non-RoHs units. STBNIP2212's whose Exec versions are 2.7x or higher are RoHs units. The Execs between these units are not interchangeable.
    • RoHs is the acronym for Restriction of Hazardous Substances. RoHS, also known as Directive 2002/95/EC, originated in the European Union and restricts the use of specific hazardous materials found in electrical and electronic PRODUCTS. The substances banned under RoHS are lead (Pb), mercury (Hg), cadmium (Cd), hexavalent chromium (CrVI), polybrominated biphenyls (PBB) and polybrominated diphenyl ethers (PBDE).
  • Firmware for the RoHs and Non-RoHs Ethernet NIMs is available on Planet.

Causes and Fixes

The following issue has been resolved in this version:

  • Repeated swap overs of a Hot Standby system could cause an Advantys STB Island to go into a fallback condition.

    If a HSBY system is repeatedly swapped within a 2 minute time period, there is a possibility that some connections to the island may not close properly and 'hang' or remain open. A situation could occur where all 16 connections would hang, depending on the number of original connections and how fast the swaps occurred. Without the ability to receive Modbus messages, the island will fall into a fallback state, After the 2 minute timeout expired, new connections would then become available.

    Version 2.32 addresses this issue by adding TCP Keep Alives to Modbus connections to determine if the NIM has hanging connections. If so, the connection will close after a 30 second timeout instead of 2 minutes. In summary, v2.32 creates a situation where it is less likely that an Island will go into a fallback state due to repeated HSBY swap overs because the hanging connections are closed sooner and allows new connections to become available more quickly.

Was this helpful?
What can we do to improve the information ?