[UFO2_DEVICESTAT :#] (IF-Node2) Required Device Status 2 Tag The ExDesc must start with the case sensitive string: [UFO2_DEVICESTAT:#] The number following the colon (:) must be the Failover ID for the interface running on IF-Node2 The pointsource must match the interfaces’ point source. Location1 must match the ID for the interfaces. A lower value is a better status and the interface with the lower status will attempt to become the primary interface. 0 – 99 / None Updated by the Interface on IFNode2 [UFO2_STATE:#] (IF-Node1) Optional State 1 Tag The ExDesc must start with the case sensitive string: [UFO2_STATE:#] The number following the colon (:) must be the Failover ID for the interface running on IFNode1 The failover state tag is recommended. The failover state tags are digital tags assigned to a digital state set with the following values. 0 = Off: The interface has been shut down. 1 = Backup No Data Source: The interface is running but cannot communicate with the data source. 2 = Backup No PI Connection: The interface is running and connected to the data source but has lost its communication to the PI Server. 3 = Backup: The interface is running and collecting data normally and is ready to take over as primary if the primary interface shuts down or experiences problems. 4 = Transition: The interface stays in this state for only a short period of time. The transition period prevents thrashing when more than one interface attempts to assume the role of primary interface. 5 = Primary: The interface is running, collecting data and sending the data to PI. 0 – 5 / None Normally updated by the Interface currently in the primary role.
[UFO2_STATE:#] (IF-Node2) Optional State 2 Tag The ExDesc must start with the case sensitive string: [UFO2_STATE:#] The number following the colon (:) must be the Failover ID for the interface running on IFNode2 The failover state tag is recommended. Normally updated by the Interface currently in the Primary state. Values range between 0 and 5. See description of State 1 tag.
Creating the UniInt Failover Control and Failover State Tags (Phase 2) The ICU can be used to create the UniInt Failover Control and State Tags. To use the ICU Failover page to create these tags simply right click any of the failover tags in the tag list and select the “Create all points (UFO Phase 2)” menu item. If this menu choice is grayed out it is because the UFO_State digital state set has not been created on the Server yet. There is a menu choice “Create UFO_State Digital Set on Server FRANTISEKPC…” which can be used to create that digital state set. Once this has been done then the “Create all points (UFO Phase2) should be available. Once the failover control and failover state tags have been created the Failover page of the ICU should look similar to the illustration below.
Meaning While in this state, the interface is in its primary role and sends data to the PI Server as it is received. This message also states that there is not a backup interface participating in failover. Message 10-May-12 16:37:21 PI-TXP 1> UniInt failover: Interface in the “Primary” state and actively sending data to PI. Backup interface available. Meaning While in this state, the interface sends data to the PI Server as it is received. This message also states that the other copy of the interface appears to be ready to take over the role of primary.
Microsoft Winsock Errors Unfortunately, there is currently no routine that translates Windows socket error numbers to text. Therefore, a partial table is included here for reference. Error Code Description Symbolic Name A blocking operation was interrupted by a call to WSACancelBlockingCall WSAEINTR An attempt was made to access a socket in a way forbidden by its access permissions WSAEACCES The system detected an invalid pointer address in attempting to use a pointer argument in a call WSAEFAULT An invalid argument was supplied WSAEINVAL Too many open sockets WSAEMFILE A non-blocking socket operation could not be completed immediately WSAEWOULDBLOCK A blocking operation is currently executing WSAEINPROGRESS An operation was attempted on a non-blocking socket that already had an operation in progress WSAEALREADY An operation was attempted on something that is not a socket WSAENOTSOCK A required address was omitted from an operation on a socket WSAEDESTADDRREQ A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself WSAEMSGSIZE A protocol was specified in the socket function call that does not support the semantics of the socket type requested WSAEPROTOTYPE An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call WSAENOPROTOOPT The requested protocol has not been configured into the system, or no implementation for it exists The support for the specified socket type does not exist in this address family The attempted operation is not supported for the type of object referenced WSAEOPNOTSUPP The protocol family has not been configured into the system or no implementation for it exists WSAEPFNOSUPPORT
Support may be provided in languages other than English in certain centers (listed above) based on availability of attendants. If you select a local language option, we will make best efforts to connect you with an available Technical Support Engineer (TSE) with that language skill. If no local language TSE is available to assist you, you will be routed to the first available attendant. If all available TSEs are busy assisting other customers when you call, you will be prompted to remain on the line to wait for the next available TSE or else leave a voicemail message. If you choose to leave a message, you will not lose your place in the queue. Your voicemail will be treated as a regular phone call and will be directed to the first TSE who becomes available. If you are calling about an ongoing case, be sure to reference your case number when you call so we can connect you to the engineer currently assigned to your case. If that engineer is not available, another engineer will attempt to assist you. Search Support From the OSIsoft Technical Support Web site, click Search Support. Quickly and easily search the OSIsoft Technical Support Web site’s Support Solutions, Documentation, and Support Bulletins using the advanced MS SharePoint search engine. Email-based Technical Support When contacting OSIsoft Technical Support by email, it is helpful to send the following information: Description of issue: Short description of issue, symptoms, informational or error messages, history of issue Log files: See the product documentation for information on obtaining logs pertinent to the situation. Online Technical Support From the OSIsoft Technical Support Web site, click Contact us > My Support > My Calls. Using OSIsoft’s Online Technical Support, you can: Enter a new call directly into OSIsoft’s database (monitored 24 hours a day) View or edit existing OSIsoft calls that you entered View any of the calls entered by your organization or site, if enabled See your licensed software and dates of your Service Reliance Program agreements