Question regarding DeltaV Reporter

I need to install DeltaV Reporter on a plant network computer.  That part is no problem.  However, my Guardian Support is lapsed.  Installing DeltaV Reporter itself, is no problem, but I need to know the port numbers firewall must forward from plant network, to control network Application Station so that I may properly configure it.

2 Replies

  • Frank, I'd be surprised if that wasn't in books on line. Regardless, you can use netstat in windows command line to see which ports are being requested by which applications. If a port is being blocked, you'll see a SYN_SENT status (among others) indicating the connection is not established. Furthermore, most firewall appliances have a monitoring feature that can list out what traffic has been blocked from which hosts. If you don't have access to these logs, request them from the department that does.
    However, many applications like opc clients (and perhaps reporter) make use of ephemeral ports, that span a dynamic range(usually high) rather than one individual port. In this case you'll need to either observe the range over multiple attempts, or just get an exception for your client in totality, but I wouldn't recommend that.
  • Frank, the communication in this case is based on OPC, and as mentioned by Youssef, you will need to manage the ephemeral port range since OPC uses DCOM. The Emerson Smart Firewall deals with DCOM natively, meaning that only a single port is actually configured/allowed to allow OPC communications to be established (the Emerson Smart Firewall will take care of the handshakes, etc.)

    Answering your question: with DCOM "friendly" firewalls all you need is TCP port 135, otherwise the full ephemeral port range - or - an OPC tunneler solution to reduce the amount of communication ports needed.

    I'm assuming you already have OPC Remote installed on your client node.