1 Reply Latest reply on Apr 16, 2019 9:02 AM by andrews_j@subway.com

    Creating external nodes with different DNS names, but same IP (MS Azure PaaS)

    andrews_j@subway.com

      Creating external nodes with different DNS names, but same IP (MS Azure PaaS)

      Howdy Community!

      We are working towards figuring out the best method to monitor our Azure PaaS instances (SQL, Analysis Services, Web). I realize that the DPA product will provide some support for SQL PaaS, but not all.  We started by creating External Nodes utilizing the DNS name of the various PaaS instances, however while we were frontloading them, we ran into a hiccup...SW will not allow eternal nodes with different DNS names that resolve to the same IP to be configured on the same poller.  We don't have enough pollers to account for the variety of PaaS systems that may share the same IP.  PaaS systems rely on DNS and not IP to operate due to the high chance of the IP-behind to be changed without notice.

       

      How can I bypass this particular technical limitation, or, is there a more elegant solution that I am missing?

       

      Thanks All!

      Jimmy

       

      Orion Platform 2018.4 HF3, WPM 2.2.3, IPAM 4.8.1 HF1, NPM 12.4, DPAIM 11.1.1, NTA 4.5.0, SAM 6.8.0, NetPath 1.1.4

        • Re: Creating external nodes with different DNS names, but same IP (MS Azure PaaS)
          andrews_j@subway.com

          So I have tentatively found a workaround.  We also utilize SW IPAM, so we created a private supernet that is not being used onsite, 172.17.0.0/16, and broke that up into 4 /18 subnets, and labeled them "External_Node_Block1-4".  This subnet is NOT integrated with DNS and only exists within the IPAM environment.

           

          Upon PaaS node creation, we set it up as an external node, name it the FQDN of the PaaS instance.  This will create the record with the resolved DNS IP of the instance.  From here, I then log into my IPAM IP reservation request service, reserve one of the IPs, and put in the FQDN of the PaaS instance as the host name.  After the IP is reserved, I then go back into the external node and change the IP to one of those that were reserved through IPAM. NOTE: any IPAM will do, we just happen to be using SW's.

           

          From there, I can create a variety of different checks, most of them parameterized powershell scripts.  I can pass the PaaS instance DNS name just the same, and it still resolves to the publicly available IP.