3 Replies Latest reply: Mar 30, 2013 5:12 PM by adaikkap RSS

OCUM v5.1 autoselects 'wrong' cluster IP address

hoffman NetApp Employee Cyclist
Currently Being Moderated

Hi all,

I have a customer who’s trying to add a cluster to OCUM v5.1.  This cluster has 3 different cluster management LIFs, only one of which is routable to / from the OCUM Core server.  When we add the cluster to OCUM by specifying the routable interface (172.26.128.xx), the cluster and all elements are discovered, but then OCUM flips the 'Cluster IP' it is using to one of the non-routable cluster management LIFs (172.28.128.xx) and we lose connectivity to the cluster.  How does OCUM Core select the cluster IP it uses?  Is there a way to force it to use a specific IP for a cluster?  Does OCUM have any built-in affinity to a LIF on the sam esubnet (the OCUM server has multiple IPs, one of which is on a private subnet that is totally separate from the subnet the 2nd cluster management interface is on)?


Here are the cluster's cluster management LIFs...we want to use xxxxxCLU01_MGMT, but it keeps flipping to xxxxxVSE01_SCRIPT_ACCESS:


GTCNACLU01::> net int show
  (network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
                         up/up   xxxxxCLU01-01 e0a-4052
                         up/up   xxxxxCLU01-02 e1b-2070
                         up/up     xxxxxCLU01-01 e1b-4093


More Like This

  • Retrieving data ...


  • Correct Answers - 10 points
  • Helpful Answers - 5 points