1 Reply Latest reply on Mar 17, 2014 3:37 PM by RichardLetts

    NPM:  Additional polling engine in a DMZ


      I have a sub-component in my agency that wants to piggy-back on our main NPM system and use it for monitoring of their specific systems.  Their systems are logically in a DMZ (not public facing, but they house sensitive information, requiring the 'seperation') behind a firewall using NAT.  Thier address space is using a range completely different from the rest of our environment, and is not routeable from the rest of the NPM installation we have.  We plan to use static NATs on the edge firewall for required traffic through the firewall.  Can we add an additional polling engine in their network, using a static NAT?