1. Real-time views of the meter in Vista show yellow boxes indicating a meter that is off-line
2. The device shows a site status of Connected in Management Console
3. Diagnostic Viewer (Communications Diagnostics > Site Overview) shows:
   1. Device status as offline.
   2. Good Responses counter is no longer increasing
   3. Bad Responses is slowly increasing.
   4. Last Attempt is usually the current time, but
   5. Last Response is some time in the past. (Normally, attempt time and response time are the same timestamp, or apart by a few seconds)
4. A netstat command shows that a connection is still established between ION Enterprise and the meter. At a command prompt, type

netstat an | find <ip address of meter>

Example output from netstat for meter at 10.168.80.148:

TCP 10.168.81.154:2694 10.168.80.148:7700 ESTABLISHED

5. To definitively confirm this problem, disconnect the affected meter using Management Console, and reconnect. Repeat step 4, and the netstat command will display more than one connection, including the old one in the state FIN_WAIT_1 (an orphaned connection)

TCP 10.168.81.154:2813 10.168.80.148:7700 ESTABLISHED

6. It may be possible that you cannot re-connect to the meter using this method. This usually occurs when all four connections to the meter are now used, often from multiple instances of ION Enterprise. In this case, there are two typical resolutions:
   1. Reset (power down/up) the meter to clear all connections. Site Server will reestablish the connection on restart.
   2. Reboot all ION Enterprise servers connected to the meter.

1. The meter has been continually connected to the server for a long period of time, and/or
2. A large volume of data has been sent FROM the PC to the meter. This is most typically the case with deployments that result in sustained high polling rates. Examples include, continuous real-time polling of all meters in a system for indefinite periods of time (i.e. leaving Vista diagrams open to meters for an extended period of time), or the use of custom meter frameworks that introduce rapid logging (causing the Log Inserter to continuously download records at a high rate)

Resolution
Firmware upgrades are required in order to eliminate this condition. Upgrades at or above the following version numbers will resolve the condition:

• ION7550/7650 V350 (V340 also resolved this problem)
• ION7550 RTU V222
• ION8600: V321
• ION8800: V331
• ION7500/7600 V254
• ION7500 RTU V122
• ION8300/8400/8500 A/B: V265(A), V281(B)
• Siemans9510/9610 V350 (V340 also resolved this problem)
• Siemans9510 ADR V222
• Siemans9500/9600 V254
• Siemans9500 ADR V122

Workaround
As described in symptoms, the meter connection can be re-established by disconnecting and reconnecting the meter in Management Console. This will leave an orphaned connection as described. If the customer is experiencing a large number of these orphaned connections, a third-party tool such as SysInternals TCPView tool can be used to identify these connections, and then close them.

Alternately, the resolutions described above can also be used:

1. Reset (power down/up) the meter to clear all connections. Site Server will reestablish the connection on restart.
2. Reboot all ION Enterprise servers connected to the meter.