View NAS Cluster Information

You can view information about a NAS cluster, including the IP addresses of all nodes, the path to the StorNext file system, node status, VIPs assigned to the cluster, and NFS failover status.

Note: For a list of all the Appliance Controller commands, see the Command Index.

  1. Log in to the Appliance Controller CLI on the master node:
  2. Enter:

    3. nascluster show version

    Note: The nascluster show version command is an extension of the nascluster show command.

    The Appliance Controller version running on those nodes is shown in bold, green.

    > nascluster show version

    NAS Cluster IP: 10.65.182.246/eth0, Master: Yes, SNFS Root: /stornext/snfs1, Joined: Yes
									ID: 0cebcf74-fa79-11e9-a8ca-0050569b86b8
									Cluster Hostname: clustervip.testdomain
									DNS Enabled: No
									Load balancing: Proxy-Disabled
									NFS-HA(NFSv3): Enabled
									Cluster VIP: 10.65.165.116 (active) snt405406-vip.mdh.quantum.com
									Scale out VIP pool:
									VIP: 10.65.164.1 (active, node:1) snt405406-pool1.mdh.quantum.com
									VIP: 10.65.164.162 (active, node:1) snt405406-pool2.mdh.quantum.com
									Nodes: 2
									*1: 10.65.182.246 (Joined) snt405406-gw1.mdh.quantum.com | Quantum x86_64 Appliance Controller 3.0.0-10975
								2: 10.65.187.33 (Not-Ready) snt405406-gw2.mdh.quantum.com | Quantum x86_64 Appliance Controller 2.3.0-10800

    The Appliance Controller version running on node 1 (in bold, green), and status of node 2 (not running; in bold, red).

    > nascluster show version

    NAS Cluster IP: 10.65.182.246/eth0, Master: Yes, SNFS Root: /stornext/snfs1, Joined: Yes
									ID: 0cebcf74-fa79-11e9-a8ca-0050569b86b8
									Cluster Hostname: clustervip.testdomain
									DNS Enabled: No
									Load balancing: Proxy-Disabled
									NFS-HA(NFSv3): Enabled
									Cluster VIP: 10.65.165.116 (active) snt405406-vip.mdh.quantum.com
									Scale out VIP pool:
									VIP: 10.65.164.1 (active, node:1) snt405406-pool1.mdh.quantum.com
									VIP: 10.65.164.162 (active, node:1) snt405406-pool2.mdh.quantum.com
									Nodes: 2
									*1: 10.65.182.246 (Joined) snt405406-gw1.mdh.quantum.com | Quantum x86_64 Appliance Controller 3.0.0-109752: 10.65.187.33 (Not-Ready) snt405406-gw2.mdh.quantum.com | unknown
  1. Log in to the Appliance Controller CLI on the master node:
  2. Enter:

    3. nascluster show

    Note the following when you view the output:

    • The NFS-HA property displays the version of NFS that is supported when it is enabled.

    • The VIP pool is separate from the cluster VIP and master VIP.

    • The nodes list displays an asterisk (*) in front of the master node.

    > nascluster show

    NAS Cluster IP: 10.65.185.194/eth0, Master: No, SNFS Root: /stornext/snfs1, Joined: Yes

    ID: 1368c4f4-d4f1-11e9-8166-0050569ba56f

    Cluster Hostname: vsop-pool.mdh.quantum.com

    DNS Enabled: No

    Load balancing: Proxy-Disabled

    NFS-HA(NFSv3): Enabled

    Cluster VIP: 10.65.164.107 (active) vsop-nas.mdh.quantum.com

    Scale out VIP pool:

    VIP: 10.65.164.77 (active, node:1) vsop-pool.mdh.quantum.com

    VIP: 10.65.164.76 (active, node:2) vsop-pool.mdh.quantum.com

    Nodes: 2

    1: 10.65.185.194 (Joined) vsop-nas02a.mdh.quantum.com

    *2: 10.65.184.233 (Joined) vsop-nas02b.mdh.quantum.com

    > nascluster show

    NAS Cluster IP: 10.65.185.194/eth0, Master: No, SNFS Root: /stornext/snfs1, Joined: Yes

    ID: 1368c4f4-d4f1-11e9-8166-0050569ba56f

    Cluster Hostname: vsop-pool.mdh.quantum.com

    DNS Enabled: No

    Load balancing: Proxy-Disabled

    NFS-HA: Disabled

    Cluster VIP: 10.65.164.107 (active) vsop-nas.mdh.quantum.com

    Nodes: 2

    1: 10.65.185.194 (Joined) vsop-nas02a.mdh.quantum.com

    *2: 10.65.184.233 (Joined) vsop-nas02b.mdh.quantum.com

    > nascluster show

    NAS Cluster IP: 10.65.184.242/em3, Master: Yes, SNFS Root: /stornext/snfs1, Joined: No

    ID: 0d588738-e9f6-11e9-abb0-0050569ba92e

    Cluster Hostname:

    DNS Enabled: No

    Load balancing: leastconn

    NFS-HA: Disabled

    Nodes: 2

    *1: 10.65.184.242 (Enabled) vsop-xfe01.mdh.quantum.com

    2: 10.65.172.81 (Enabled) vsop-xfe02.mdh.quantum.com

    > nascluster show

    NAS Cluster IP: 10.65.184.242/em3, Master: Yes, SNFS Root: /stornext/snfs1, Joined: Yes

    ID: 0d588738-e9f6-11e9-abb0-0050569ba92e

    Cluster Hostname:

    DNS Enabled: No

    Load balancing: leastconn

    NFS-HA: Disabled

    Nodes: 2

    *1: 10.65.184.242 (Joined) vsop-xfe01.mdh.quantum.com

    2: 10.65.172.81 (Joined) vsop-xfe02.mdh.quantum.com

    > nascluster show

    NAS Cluster IP: 10.65.184.242/em3, Master: Yes, SNFS Root: /stornext/snfs1, Joined: Yes

    ID: 0d588738-e9f6-11e9-abb0-0050569ba92e

    Cluster Hostname:

    DNS Enabled: No

    Load balancing: leastconn

    NFS-HA: Disabled

    Cluster VIP: 10.65.164.107 (active) vsop-nas.mdh.quantum.com

    Nodes: 2

    *1: 10.65.184.242 (Joined) vsop-xfe01.mdh.quantum.com

    2: 10.65.172.81 (Joined) vsop-xfe02.mdh.quantum.com

    > nascluster show

    NAS Cluster IP: 10.65.184.242/em3, Master: Yes, SNFS Root: /stornext/snfs1, Joined: Yes

    ID: 0d588738-e9f6-11e9-abb0-0050569ba92e

    Cluster Hostname: vsop-pool.mdh.quantum.com

    DNS Enabled: No

    Load balancing: Proxy-Disabled

    NFS-HA(NFSv3): Enabled

    Cluster VIP: 10.65.164.107 (active) vsop-nas.mdh.quantum.com

    Scale out VIP pool:

    VIP: 10.65.164.77 (active, node:1) vsop-pool.mdh.quantum.com

    VIP: 10.65.164.76 (active, node:2) vsop-pool.mdh.quantum.com

    Nodes: 2

    *1: 10.65.184.242 (Joined) vsop-xfe01.mdh.quantum.com

    2: 10.65.172.81 (Joined) vsop-xfe02.mdh.quantum.com

    > nascluster show

    NAS Cluster IP: 10.65.184.242/em3, Master: Yes, SNFS Root: /stornext/snfs1, Joined: Yes

    ID: 0d588738-e9f6-11e9-abb0-0050569ba92e

    Cluster Hostname: vsop-pool.mdh.quantum.com

    DNS Enabled: No

    Load balancing: Proxy-Disabled

    NFS-HA(NFSv3): Enabled

    Cluster VIP: 10.65.164.107 (active) vsop-nas.mdh.quantum.com

    Scale out VIP pool:

    VIP: 10.65.164.77 (active, node:1) vsop-pool.mdh.quantum.com

    VIP: 10.65.164.76 (active, node:2) vsop-pool.mdh.quantum.com

    Controller management config:

    VIP: 192.168.16.200 (active on local device)

    1: 192.168.16.11/em1:1

    2: 192.168.16.12/em1:1

    Nodes: 2

    *1: 10.65.184.242 (Joined) vsop-xfe01.mdh.quantum.com

    2: 10.65.172.81 (Joined) vsop-xfe02.mdh.quantum.com

    Node States

    The following table presents the different states of nodes.

    State Description
    Enabled

    The node is ready to join the NAS cluster, but it is not actively ready to take client connections.
    Joined

    The node is ready to take client connections, or to become the master node in the event of a NAS failover.
    Not-Ready

    One of the following:

    • The node cannot be reached due to an issue with the node's Appliance Controller, network, or NAS cluster management processes.
    • The node has been removed from the cluster with the nascluster leave <ip_addr> command. It can still receive communications from other nodes in the NAS cluster, but it will not actively participate in the NAS cluster. Nodes will report this state when a system administrator has taken the node offline to perform maintenance.
    Disabled

    The node is still a member of the cluster, but it cannot receive NAS connections, be used as a NAS failover target, or receive configuration updates.

    Nodes typically report this state when a system administrator has taken a node offline to perform maintenance, or when the node has gone offline for some other reason.