Jumat, 17 Juli 2015

Configure Fas2552 (first time)


Configure Fas2552 (first time)

1.    Set node management interface
Welcome to node setup.

You can enter the following commands at any time:
  "help" or "?" - if you want to have a question clarified,
  "back" - if you want to change previously answered questions, and
  "exit" or "quit" - if you want to quit the setup wizard.
     Any changes you made before quitting will be saved.

To accept a default or omit a question, do not enter a value.



This system will send event messages and weekly reports to NetApp Technical
Support.
To disable this feature, enter "autosupport modify -support disable" within 24
hours.
Enabling AutoSupport can significantly speed problem determination and
resolution should a problem occur on your system.
For further information on AutoSupport, see:
http://support.netapp.com/autosupport/

Type yes to confirm and continue {yes}: yes

Enter the node management interface port [e0c]: e0M
Enter the node management interface IP address: 172.16.254.100
Enter the node management interface netmask: 255.255.255.0
Enter the node management interface default gateway: 172.16.254.1
A node management interface on port e0M with IP address 172.16.254.100 has been created.


This node has its management address assigned and is ready for cluster setup.

To complete cluster setup after all nodes are ready, download and run the System Setup utility from the NetApp Support Site and use it to discover the configured nodes.

For System Setup, this node's management address is: 172.16.254.100.

Alternatively, you can use the "cluster setup" command to configure the cluster.



2.    Create Cluste (step.1)
login: admin
******************************************************
* This is a serial console session. Output from this *
* session is mirrored on the SP console session.     *
******************************************************
***********************
**  SYSTEM MESSAGES  **
***********************

The upgrade path cannot be determined. The upgrade process has exited. Contact
support personnel for the upgrade repair procedure. 
  
::>
::> cluster setup

Welcome to the cluster setup wizard.

You can enter the following commands at any time:
  "help" or "?" - if you want to have a question clarified,
  "back" - if you want to change previously answered questions, and
  "exit" or "quit" - if you want to quit the cluster setup wizard.
     Any changes you made before quitting will be saved.

You can return to cluster setup at any time by typing "cluster setup".
To accept a default or omit a question, do not enter a value.

Do you want to create a new cluster or join an existing cluster? {create, join}:create

Do you intend for this node to be used as a single node cluster? {yes, no} [no]:no
Will the cluster network be configured to use network switches? [yes]:no
Non-HA mode, Reboot node to activate HA

Warning: Ensure that the HA partner has started disk initialization before
         rebooting this node to enable HA.
         Do you want to reboot now to set storage failover (SFO) to HA mode?
         {yes, no} [yes]: yes

Rebooting now



3.    Create Cluste (step.2)
After Reboot.
::> cluster setup

Welcome to the cluster setup wizard.

You can enter the following commands at any time:
  "help" or "?" - if you want to have a question clarified,
  "back" - if you want to change previously answered questions, and
  "exit" or "quit" - if you want to quit the cluster setup wizard.
     Any changes you made before quitting will be saved.

You can return to cluster setup at any time by typing "cluster setup".
To accept a default or omit a question, do not enter a value.


Do you want to create a new cluster or join an existing cluster? {create, join}:create


Do you intend for this node to be used as a single node cluster? {yes, no} [no]:no
Will the cluster network be configured to use network switches? [no]: no

Existing cluster interface configuration found:

PortMTUIPNetmask
e0e9000169.254.99.224255.255.0.0
e0f9000169.254.155.105255.255.0.0

Do you want to use this configuration? {yes, no} [yes]: yes
Enter the cluster administrator's (username "admin") password:*********
Retype the password: *********

Step 1 of 5: Create a Cluster
You can type "back", "exit", or "help" at any question.

Enter the cluster name: bs-cluster
Enter the cluster base license key: *************AAAAAAAAAAAAA

Creating cluster bs-cluster                                                           
                                                                             
Network set up                                                                
Network set up .                                                              
Starting replication service                                                  
Starting replication service .                                                
Creating cluster                                                               
System start up                                                               
System start up .                                                             
Vserver Management                                                             
Starting cluster support services                                             
Cluster bs-cluster has been created.

Step 2 of 5: Add Feature License Keys
You can type "back", "exit", or "help" at any question.

Enter an additional license key []: *******AAAAAAAAAAAAAAAAAA

Step 3 of 5: Set Up a Vserver for Cluster Administration
You can type "back", "exit", or "help" at any question.


Enter the cluster management interface port [e0c]: e0a M
Enter the cluster management interface IP address []:172.16.254.103
Enter the cluster management interface netmask []:255.255.255.0
Enter the cluster management interface default gateway []:172.16.254.1

A cluster management interface on port e0M with IP address 172.16.254.103 has been created.  You can use this address to connect to and manage the cluster.

Enter the DNS domain names: body    thecompay.com
Enter the name server IP addresses: 192.168.0.111
DNS lookup for the admin Vserver will use the thecompay.com domain.

Step 4 of 5: Configure Storage Failover (SFO)
You can type "back", "exit", or "help" at any question.


SFO will be enabled when the partner joins the cluster.


Step 5 of 5: Set Up the Node
You can type "back", "exit", or "help" at any question.

Where is the controller located []: Gd. thecompay.com,
Enter the node management interface port [e0M]:
Enter the node management interface IP address []:172.16.254.100
Enter the node management interface netmask []:255.255.255.0
Enter the node management interface default gateway []:172.16.254.1

Cluster "bs-cluster" has been created.
To complete cluster setup, you must join each additional node to the cluster
by running "cluster setup" on each node.

Once all nodes have been joined to the cluster, see the Clustered Data ONTAP
Software Setup Guide for information about additional system configuration
tasks.  You can find the Software Setup Guide on the NetApp Support Site.

To complete system configuration, you can use either OnCommand System Manager
or the Data ONTAP command-line interface.

To access OnCommand System Manager, point your web browser to the cluster
management IP address (172.16.254.103).
To access the command-line interface, connect to the cluster management
IP address (for example, ssh admin@172.16.254.103).


4.    Cluster show
bs-cluster::> cluster show
Node                  Health  Eligibility
--------------------- ------- ------------
bs-cluster-01         true    true


5.    Joint Cluster (Step.1)
Welcome to the cluster setup wizard.
You can enter the following commands at any time:
  "help" or "?" - if you want to have a question clarified,
  "back" - if you want to change previously answered questions, and
  "exit" or "quit" - if you want to quit the cluster setup wizard.
     Any changes you made before quitting will be saved.
You can return to cluster setup at any time by typing "cluster setup".
To accept a default or omit a question, do not enter a value.
Do you want to create a new cluster or join an existing cluster? {create, join}:join
Non-HA mode, Reboot node to activate HA
Warning: Ensure that the HA partner has started disk initialization before
         rebooting this node to enable HA.
         Do you want to reboot now to set storage failover (SFO) to HA mode?
         {yes, no} [yes]: yes
Rebooting now



login: admin
******************************************
* This is a serial console session. Output from this *
* session is mirrored on the SP console session.     *
******************************************
**********************
**  SYSTEM MESSAGES  **
**********************
The upgrade path cannot be determined. The upgrade process has exited. Contact
support personnel for the upgrade repair procedure. 
 ::>                                                                               
'Rebooting to enable HA'                                                      
                                                                          
Terminated


6.    Joint Cluster (Step.2 –Set management interface)

Welcome to node setup.

You can enter the following commands at any time:
  "help" or "?" - if you want to have a question clarified,
  "back" - if you want to change previously answered questions, and
  "exit" or "quit" - if you want to quit the setup wizard.
     Any changes you made before quitting will be saved.

To accept a default or omit a question, do not enter a value.

Enter the node management interface port []: e0M
Enter the node management interface IP address []:172.16.254.101
Enter the node management interface netmask []:255.255.255.0
Enter the node management interface default gateway []:172.16.254.1

The node management interface has been modified to use port e0M with IP address 172.16.254.101.

This node has its management address assigned and is ready for cluster setup.

To complete cluster setup after all nodes are ready, download and run the System Setup utility from the NetApp Support Site and use it to discover the configured nodes.

For System Setup, this node's management address is: 172.16.254.101.

Alternatively, you can use the "cluster setup" command to configure the cluster.


Joint Cluster (Step.3)
login: admin
******************************************************
* This is a serial console session. Output from this *
* session is mirrored on the SP console session.     *
******************************************************
::> cluster setup

Welcome to the cluster setup wizard.

You can enter the following commands at any time:
  "help" or "?" - if you want to have a question clarified,
  "back" - if you want to change previously answered questions, and
  "exit" or "quit" - if you want to quit the cluster setup wizard.
     Any changes you made before quitting will be saved.

You can return to cluster setup at any time by typing "cluster setup".
To accept a default or omit a question, do not enter a value.


Do you want to create a new cluster or join an existing cluster? {create, join}:join
Existing cluster interface configuration found:
PortMTUIPNetmask
e0e9000169.254.35.70255.255.0.0
e0f9000169.254.68.96255.255.0.0
Do you want to use this configuration? {yes, no} [yes]: yes

Step 1 of 3: Join an Existing Cluster
You can type "back", "exit", or "help" at any question.

Enter the name of the cluster you would like to join [bs-cluster]:



Joining cluster bs-cluster                                                                      

.                                                                             
Network set up                                                                
Network set up .                                                               
Node check                                                                    
Node check .                                                                  
Joining cluster                                                               
Joining cluster .                                                             
System start up                                                               
System start up .                                                                             
Checking cluster applications                                                 
Checking cluster applications .                                               
Checking cluster applications ..                                                
Updating LIF Manager                                                          
Starting cluster support services                                              
Starting cluster support services .                                           
Starting cluster support services ..                                          

This node has joined the cluster bs-cluster.

Step 2 of 3: Configure Storage Failover (SFO)
You can type "back", "exit", or "help" at any question.

SFO will be enabled when the partner joins the cluster.

Step 3 of 3: Set Up the Node
You can type "back", "exit", or "help" at any question.

Enter the node management interface port []:  e0M
Enter the node management interface IP address []:172.16.254.101

Enter the node management interface netmask []:255.255.255.0
Enter the node management interface default gateway []:172.16.254.1

The node management interface has been modified to use port e0M with IP address 172.16.254.111.

This node has been joined to cluster "bs-cluster".
To complete cluster setup, you must join each additional node to the cluster
by running "cluster setup" on each node.

Once all nodes have been joined to the cluster, see the Clustered Data ONTAP
Software Setup Guide for information about additional system configuration
tasks.  You can find the Software Setup Guide on the NetApp Support Site.

To complete system configuration, you can use either OnCommand System Manager
or the Data ONTAP command-line interface.

To access OnCommand System Manager, point your web browser to the cluster
management IP address (172.16.254.110).
To access the command-line interface, connect to the cluster management
IP address (for example, ssh admin@172.16.254.110).


7.    2nd Cluster show

bs-cluster::> cluster show
Node                  Health  Eligibility
--------------------- ------- ------------
bs-cluster-01         true    true
bs-cluster-02         true    true


8.       Configure Cluster HA  and storage failover
bs-cluster::> storage failover show
                              Takeover         
Node           Partner        Possible State Description 
-------------- -------------- -------- -------------------------------------
bs-cluster-01  bs-cluster-02  false    Connected to bs-cluster-02, Takeover
                                       is not possible: Storage failover is
                                       disabled
bs-cluster-02  bs-cluster-01  false    Connected to bs-cluster-01, Takeover
                                       is not possible: Storage failover is
                                       disabled
2 entries were displayed.
bs-cluster::> cluster ha show
High Availability Configured: false

Warning: Cluster HA has not been configured.  Cluster HA must be configured
         on a two-node cluster to ensure data access availability in the
         event of storage failover. Use the "cluster ha modify -configured
         true" command to configure cluster HA.

bs-cluster::> cluster ha modify -configured true

Warning: High Availability (HA) configuration for cluster services requires
         that both SFO storage failover and SFO auto-giveback be enabled. These
         actions will be performed if necessary.
Do you want to continue? {y|n}: y

Notice: HA is configured in management.

bs-cluster::> cluster ha show
High Availability Configured: true
bs-cluster::> storage failover show
                              Takeover         
Node           Partner        Possible State Description 
-------------- -------------- -------- -------------------------------------
bs-cluster-01  bs-cluster-02  true     Connected to bs-cluster-02
bs-cluster-02  bs-cluster-01  true     Connected to bs-cluster-01
2 entries were displayed.


Kamis, 16 Juli 2015

Upgrade Ontap 8.2 7-mode ke CDoT 8.3 di mesin Fas2552

Upgrade Ontap 8.2 7-mode ke CDoT 8.3 di mesin Fas2552

1.    Cek status cluster
bs-ctrl2> cf status
Controller Failover enabled, bs-ctrl1 is up.
VIA Interconnect is up (link up).

2.    Jika masih enable dirubah ke disable
bs-ctrl2> cf disable
bs-ctrl2> cf status
Controller Failover disabled.
VIA Interconnect is up (link up).

3.    Shutdown ke LOADER
bs-ctrl2> halt

4.    Run command :
a.      LOADER-B> set-defaults
b.     LOADER-B> setenv bootarg.init.boot_clustered true
c.      LOADER-B> setenv AUTOBOOT false
d.     LOADER-B> setenv AUTOBOOT false
e.      LOADER-B> boot_ontap

5.    Pilih menu ‘Install new software config’

**************************
*                                                     *
* Press Ctrl-C for Boot Menu. *
*                                                     *
************************** 
^CBoot Menu will be available.

Please choose one of the following:

(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 7

This procedure is not supported for Non-Disruptive Upgrade on an HA pair.
The software will be installed to the alternate image, from which the node is
not currently running. Do you want to continue? {y|n} y

In order to download the package, a temporary network interface needs to be
configured.

Select the network port you want to use for the download (for example, 'e0a')
 e0M

The node needs to reboot for this setting to take effect.  Reboot now? {y|n}
(selecting yes will return you automatically to this install wizard) y



Rebooting...
Here are the permissions on /mroot directory:
drwxr-xr-x  3 root  wheel  512 Oct  8  2014 /mroot
/mroot directory doesn't exist or is it not writeable... aborting coverage dump
Terminated
.
Uptime: 1m46s
System rebooting...

6.    Copy image.tgz (ontap 8.3) via http

LOADER-B> boot_ontap
Loading X86_64/freebsd/image1/kernel:0x100000/9570440 0xa20888/4044560 Entry at 0x8016e330
Loading X86_64/freebsd/image1/platform.ko:0xdfc000/781096 0xf97750/720384 0xebab40/44936 0x1047550/49560 0xec5ac8/108679 0xee034f/80250 0xef3ce0/170336 0x10536e8/193800 0xf1d640/16 0xf1d650/2384 0x1082bf0/7152 0xf1e000/0 0xf1e000/344 0x10847e0/1032 0xf1e158/1944 0x1084be8/5832 0xf1e8f0/1648 0x10862b0/4944 0xf1ef60/240 0x1087600/720 0xf1f060/448 0xf5a8a0/14896 0xf97652/253 0xf5e2d0/135720 0xf7f4f8/98650
Starting program at 0x8016e330
NetApp Data ONTAP 8.2.2P1 Cluster-Mode
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Root mount waiting for: usbus0
Copyright (C) 1992-2014 NetApp.
All rights reserved.
md1.uzip: 39168 x 16384 blocks
md2.uzip: 15360 x 16384 blocks
*************************
*                                                     *
* Press Ctrl-C for Boot Menu. *
*                                                     *
************************** 
Proceeding with Install

In order to download the package, a temporary network interface needs to be
configured.

Enter the IP address for port e0M: 172.16.254.101
Enter the netmask for port e0M: 255.255.255.0
Enter IP address of default gateway: 172.16.254.1

What is the URL for the package? http://172.16.254.99/images/83P2_q_image.tgz
What is the user name on "172.16.254.99", if any?

Checking network link... -
Checking network link... /
 Checking network link... success.
Checking route to host "172.16.254.99"... success.
Attempting to reach 172.16.254.99... success.
Looking up URL "http://172.16.254.99/images/83P2_q_image.tgz"... success.
Downloading package...   0%
Downloading package...   1%
          …
Checking package contents... success.
Extracting install script from package... success.
Invoking script (validation phase).
INSTALL running in check-only mode: the image will be validated only
Mode of operation is COPY
Current image is image1
Alternate image is image2
Package MD5 checksums pass
Available space on boot device is 1560 MB
Required  space on boot device is 507 MB
Kernel binary matches install machine type
Terminated
Invoking script (install phase).  This may take up to 20 minutes.
Mode of operation is COPY
Current image is image1
Alternate image is image2
Package MD5 checksums pass
Available space on boot device is 1560 MB
Required  space on boot device is 507 MB
Kernel binary matches install machine type
Getting ready to install image
Syncing device...
Extracting to /cfcard/x86_64/freebsd/image2...
Installed MD5 checksums pass
Installing diagnostic and firmware files
Firmware MD5 checksums pass
Terminated
Installation complete.

Do you want to set the newly installed software as the default to be used for
subsequent reboots? {y|n} y

The node must be rebooted to start using the newly installed software. Do you
want to reboot now? {y|n} y


Rebooting...


7.    Install CDoT 8.3

*******************************
*                             *
* Press Ctrl-C for Boot Menu. *
*                             *
******************************* 
Running the upgrade system
bootarg.upgrade="true"
bootarg.from.version="8.2.2P1"
^CBoot Menu will be available.

Please choose one of the following:

(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 4
qla_init_hw: CRBinit running ok: 8c633f
NIC FW version in flash: 5.4.9
qla_init_hw: CRBinit running ok: 8c633f
NIC FW version bundled: 5.4.51
qla_init_hw: CRBinit running ok: 8c633f
NIC FW version in flash: 5.4.9
Jul 14 16:28:53 [localhost:cf.nm.nicTransitionDown:warning]: HA interconnect: Link down on NIC 0.
Jul 14 16:28:53 [localhost:cf.rv.notConnected:error]: HA interconnect: Connection for 'cfo_rv' failed.
qla_init_hw: CRBinit running ok: 8c633f
NIC FW version bundled: 5.4.51
Module Type 10GBase-SR
Jul 14 16:29:00 [localhost:sas.cable.error:debug]: Failed to retrieve info of cable attached to SAS port "0a".
WAFL CPLEDGER is enabled. Checklist = 0x7ff841ff
add host 127.0.10.1: gateway 127.0.20.1

Zero disks, reset config and install a new file system?: Jul 14 16:29:02 [localhost:raid.autoPart.disabled:notice]: Auto-partitioning is disabled on this system: the system needs a minimum of 4 usable internal hard disks.
y

This will erase all the data on the disks, are you sure?: y


Rebooting to finish wipeconfig request.
Skipped backing up /var file system to CF.
Terminated


8.    Restart dan configure