Help on LIF configuration

netappmagic · ‎2015-03-30

I have vserver: clu-nfs-2, then uder this vserver, two of data lif's are following:

data lif: clu-nfs-2-t-01

data lif: clu-nfs-2-t-02

My question is, how could I know clu-nfs-2-t would be the DNS name for flip-flop lif for clu-nfs-2-t-01 and clu-nfs-2-t-02

Thanks!

YIshikawa · ‎2015-03-30

This KB may help.
https://kb.netapp.com/support/index?page=content&id=1013801

netappmagic · ‎2015-03-31

Thanks for the link. But not sure I fully understand.

The following is the result. In it, " clu1-nfs-2-t-01" and " clu1-nfs-2-t-02" can get resolve by nslookup "clu1-nfs-2-t", I understant that DNS round-robinly pickup an IP. The client can use "clu1-nfs-2-t" for altinatively using " clu1-nfs-2-t-01( x.x.30.11)" or " clu1-nfs-2-t-02(x.x.30.12)". However, adversely, the client cannot use clu1-nfs-2, only clu1-nfs-2-01 or clu1-nfs-2-02 can get resolved.

So, how could I know I could assign clu1-nfs-2-t-01 to the client, and why in the other cases, I would have to use clu1-nfs-2-01 or clu1-nfs-2-02 individually?

clu1::> net int show -vserver clu1-nfs-2
(network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
clu1-nfs-2
            clu1-nfs-2-01 up/up    x.xx.23.11/24    clu1-01        a0a-314 true
            clu1-nfs-2-02 up/up    x.x.23.12/24    clu1-02        a0a-314 true
            clu1-nfs-2-admin
                         up/up    x.x.18.61/24    clu1-02        a0a-310 true
            clu1-nfs-2-t-01
                         up/up    x.x.30.11/24    clu1-01        a0a-308 true
            clu1-nfs-2-t-02
                         up/up    x.x.30.12/24    clu1-02        a0a-308 true
5 entries were displayed.

YIshikawa · ‎2015-03-31

It depends on whether your clients have an access to x.x.23 network or not, and role and protocols of these LIFs.
Please check network reachability first. And, can you post "net int show -vserver clu1-nfs-2"?

netappmagic · ‎2015-03-31

Again,

My main question is, if I did not set it up from scratch, then how could I know DNS name clu1-nfs-2-t would RR to either clu1-nfs-2-t-01 or clu1-nfs-2-t-02?

Then on the other side, there is no DNS pointer to the pair of clu1-nfs-2-01 and clu1-nfs-2-02.

The following is the requested output

> net int show -vserver clu1-nfs-2
(network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
clu1-nfs-2
            clu1-nfs-2-01 up/up    x.x.23.11/24    clu1-01        a0a-314 true
            clu1-nfs-2-02 up/up    x.x.23.12/24    clu1-02        a0a-314 true
            clu1-nfs-2-admin
                         up/up    x.x.18.61/24    clu1-02        a0a-310 true
            clu1-nfs-2-t-01
                         up/up    x.x.30.11/24    clu1-01        a0a-308 true
            clu1-nfs-2-t-02
                         up/up    x.x.30.12/24    clu1-02        a0a-308 true
5 entries were displayed.

YIshikawa · ‎2015-03-31

Easiest way is just checking by nslookup.
If you would like to know as per configuration, check records on external DNS server and "
net int show -vserver clu1-nfs-2 -instance"(sorry I missed this option).
KB ID 1013801 details related configurations and have links to external DNS setup procedure. Read then, determine which sort of RR DNS is used, and check LIF configuration.

netappmagic · ‎2015-04-01

OK. I am starting to recognize now you could not find the DNS load-balancing information among all LIF's from NetApp storage level if you just start to work on it, unless somebody who knows the environment told you so.

Now if you go back to my previous output, we have DNS load-balancing setup over clu1-nfs-2-g-01 and clu1-nfs-2-g-02. there is no DNS load-balancing points to clu1-nfs-2-01 and clu1-nfs-2-02, we could do so, by creating a DNS pointer, say the name could be clu1-nfs-2, for a type of application, or clients accesss. Correct