DX Infrastructure Manager

Expand all | Collapse all

Cluster installation conectivity problems

  • 1.  Cluster installation conectivity problems

    Posted 05-06-2013 11:14 AM
      |   view attached

    Hi,

     

    Anyone with Nms installed in cluster can confirm me if in the IM both IPs are shown as in the picture?

     

    10.130.70.19 Cluster IP

    10.130.70.4 - Node 1 IP (now this node is the owner of the cluster)

     

    The failover works fine, Nimsoft "works" but I am having terrible performance issues when IM is loged into the main server hub. I have IM installed in one client, not in the main server. If I log into another hub, it runs smooth. Also distrv is having many conectivity problems with the hubs. It seems something related with Virtual IP.

     

    Also I modified Hosts file because Nms didnt recognized Virtual Ip as a Local IP. I added a line like.

    10.130.70.10 - Node1 hostname

     

     

    Thanks.



  • 2.  Re: Cluster installation conectivity problems

    Posted 05-06-2013 11:42 PM

    Yes.  we have mixed binding of IPs on clustered hub as well.   

     

    What we've done was in the controller config...

    - Force hostname of cluster to something like NMSCluster

    - Force the IP to be VIP of the cluster

     

    if robot version is >= 5.11

    added the following line to the <controller> section of your robot.cfg: 


    local_ip_validation = no

     

    so it stops trying "fix" IP

     

    The hub config should also show the VIP as IP address near the license.

     

    I have had to have people re-login or click advance button on IM and reselect the cluster to login but for most part it fails over if they are already logged in



  • 3.  Re: Cluster installation conectivity problems

    Posted 05-09-2013 01:51 PM

    Hi,

     

    Changed in controller name to Nmscluster, and hub name too.


    Loval_validation_ip is off

    In Hub.cfg I dont see the VIP and in IM the hub probe has the Node IP instead of VIP.

    Now controller is activated with VIP and hub is using Node1 IP and the rest of probes are deactivated with the red-lock icon due to license


    I specified hubip = 10.130.70.19 in the hub.cfg but still not working. It is detecting the node IP for hub probe.,

     

    When I change back hub name to Node1 name and robotname to Node1 name as installed at the begining, all works fine again.

    Robot is 5.70.

    Many thanks !!