Setting up a Brocade Switch.

  Setting up a Brocade Switch.

Step1: setting up the username and password

 The default username is admin and the default password of the brocade switch is password

Step 1: Name the switch by “switchName” cmd

Step2: Set the Domain ID.

To set the domain id you need to first disable the switch so when you disable the switch all the port which are showing the green light will turn to the amber light.

The cmd to disable the switch is “switchDisable”

And then enter the “configure”cmd to configure the switch.

When you enter the configure cmd you will be asked number of questions so you need to put “yes”  in “Fabric parameters” and rest set default and set domain id in domain id section like if you need to set the domain id as 1 then put 1 in front of the domain id section.

Step3: enable the switch with its new domin id.

Enter the “switchEnable” cmd after you did the configuring of the switch after you enter the switchEnable cmd the switch will reboot.

Then after reboot enter the “logout”cmd to logout from the switch.

How to create Zone in Brocade switch.

How to create Zone in Brocade switch.

Terminology

HBA - Host Bus Adapter, which in this case, refers to the Fibre Channel Card. In LAN networking, it’s analogous to an Ethernet card.
WWN - World Wide Name, a unique 8-byte number identifying the HBA. In Ethernet networking, it’s analogous to the MAC address.
FC Zone - Fibre Channel Zone, a partitioned subset of the fabric. Members of a zone are allowed to communicate with each other, but devices are not allowed to communicate across zones. An FC Zone is loosely analogous to a VLAN.

Steps to Zone Brocade Switch

1. Plug in the FC Connector into an open port on the switch.
2. Login to the server and verify the HBA connection. It should see the switch but not the storage device.
3. Login to the Brocade Switch GUI interface. You’ll need Java enabled on your browser.
4. Check the Brocade Switch Port.
1. On the visual depiction of the switch, click on the port where you plugged in the FC connector.
2. The Port Administration Services screen should pop up. You’ll need to enable the pop-up.
3. Verify that the Port Status is “Online”. Note the port number.
4. Close the Port Administration Services screen.
5. Find the WWN of your new device
1. Navigate back to the original GUI page.
2. Select Zone Admin, an icon on the bottom left of the screen. It looks like two squares and a rectangle.
3. Expand the Ports & Attaching Devices under the Member Selection List.
4. Expand the appropriate port number. Note the attached WWN.
6. Create a new alias for this device
1. Click New Alias button
2. Follow menu instructions
7. Add the appropriate WWN to the alias
1. Select your new device name from the Name drop down menu
2. Expand the WWNs under Member Selection List
3. Highlight the appropriate WWN
4. Select Add Member
8. Add the alias to the appropriate zone
1. Select the Zone tab
2. Select the appropriate zone from the Name drop down menu
3. Select the appropriate alias from the Member Selection List
4. Click Add Member
9. Ensure that the zone is in Zone Config in the Zone Config tab
10. Save your changes by selecting ZoningActions -> Enable Config
11. Login back in to the server to verify. It should now see the storage devices.

NetApp SnapVault

Snap vault

Snapvault is a heterogeneous disk –to-disk backup solutions for Netapp filers and systems with other OS (solaris, HP-UX, AIX, windows, and linux) . in event of data loss or corruption on a filer, backed up data can be restored from the snap vault secondary storage system with less downtime and less of the uncertainly associated with conventional tape backup and restore operations . snapshot technology is used for the snap vault operation.

Snap vault can be done beteween the two system either netapp filer to filer or from unix/win servers to netapp filer. While doing the snapvault from server to filer we need to install the snapvault agent on server.the snapvault agent name is ossv(open system snap vault).

Snapvault technology works on snap vault client and snapvault server model means the client is whose data is to be backedup and the snapvault server is where the client data will get backed up.

Snapvault works on snapshot technology first the baseline transfer will happen and then the incremental backup will happen. The snapshot of the data will get backedup and the retention of the backed data is also simple, we need to mount the backup volume via nfs or cifs and then copy the data.

Snapvault reguired two licenses one is for the primary site and one is for the secondary site.

Steps to configure the snapvault between the two netapp storage.

Step 1. Add the license on primary filer and secondary filer.

Filer1> license add xxxxxxx

Filer2> license add xxxxxxx

Step 2. Enable the snapvault on the primary filer and do the entry on the primary filer of secondary filer.

Filer1> options snapvault.enable on

Filer1> options snapvault.access host=filer2

Step 3. Enable the snapvault on the secondary filer and do the entry on the secondary filer of primary filer.

Filer2> options snapvault.enable on

Filer2> options snapvault.access host=filer1

Now let the destination volume name is vipuldest where all the backups are done on filer2 and the source volume name is vipulsource whose backup is to be taken on filer1  , so filer2> /vol/vipuldest and for the primary filer filer1>/vol/vipulsource/qtree1.

Step 4.  We need to disable the snapshot schedule on the destination volume. Snap vault will manage the destination snapshot schedule.

Filer2> snap sched vipuldest 0 0 0

Step 5.  Do the initial baseline backup

Filer2> snapvault start –S filer1:/vol/vipulsource/qtree1 filer2:/vol/vipuldest/qtree1

Step 6. Creating the schedule for the snapvault backup on source and destination filer

On source we will create less number of retention schedules and destination we can create more number of retention schedules.

On source we will create 2 hourly, 2daily, 2weekly and on destination we will create 6 hourly, 14daily, 6 weekly.

Note: the snapshot name should be prefixed by “sv_”

Filer1> snapvault snap sched vipulsource sv_hourly 2@0-22

Filer1> snapvault snap sched vipulsource sv_hourly 2@23

Filer1> snapvault snap sched vipulsource sv_weekly 2@21@sun.

Step 7. Make the schedule on the destinations.

Filer2> snapvault snap sched vipuldest sv_hourly 6@0-22

Filer2> snapvault snap sched vipuldest sv_hourly 14@23@sun-fri

Filer2> snapvault snap sched vipuldest sv_weekly 6@23@sun.

To check the status use the snapvault status  cmd either on source or on destinations.

Brocade FOS Up gradation Steps

Brocade FOS Up gradation Steps.

1.       Backing up the existing switch configuration to the local server by cmd “configupload”.

For Example:

switch1:admin> configupload
Server Name or IP Address [host]: 1.2.3.4
User Name [user]: matty
File Name [config.txt]: switch1_config.txt
Protocol (RSHD or FTP) [rshd]: ftp
Password:
upload complete

For download put configdownload.

2.       Tag all the fiber cable and unplug it from the switch.

3.       Download the FOS version 6.1.0c from the brocade site.

4.       Take the putty of the switch.

5.       Enter the version cmd to check the current version.

6.       Enter the nsShow cmd to check the entire device directly connected to the switch.

7.       Enter the nsAllShow cmd to check the entire connected device to the fabric.

8.       Enter the fabricshow cmd to check all switches in the fabric

9.       Enter the Firmwareshow cmd to chek the primary and secondary partion.

10.   Enter the Firmwaredownload cmd to download the new version.

For example:

switch:admin> firmwaredownload 

Server Name or IP Address: 10.22.127.127

FTP User Name: JohnDoe

File Name:  /release.plist

FTP Password:

You can run firmwaredownloadstatus to get the status

of this command.

This command will cause the switch to reset and will

require that existing telnet, secure telnet or SSH

sessions be restarted.

Do you want to continue [Y]: y

11.   Enter the firmwaredownloadstatus cmd to check the current status of the upgrade process.

12.   Enter the firmwareshow cmd to check the primary and secondary partition version.

13.   Plugin all the fiber cable and check the connectivity.

14.   Enter the nsShow cmd to check the entire device directly connected to the switch.

15.   Enter the nsAllShow cmd to check the entire connected device to the fabric.

16.   Enter the fabricshow cmd to check all switches in the fabric.

Backing up Brocade switch configurations

Brocade switches have become one of the most widely deployed componets in most Storage Area Networks (SANs). One thing that has led to Brocade’s success is their robust CLI, which allow you to view and modify almost every aspect of their switch. This includes zoning configurations, SNMP attributes, domain ids, switch names and network addresses, etc. All of this configuration information is necessary for the switch to function properly, and should be periodically backed up to allow speedy recovery when disaster hits.

Each Brocade switch comes with the “configUpload” and “configDownload” commands to back up a switch configuration to a remote system, or to restore a configuration from a remote system. ConfigUplaod has two modes of oepration: interactive mode and automatic mode. To use the interactive mode to upload a config from a switch named switch1 to an ftp server with the IP address 1.2.3.4, configUpload can be run to walk you through backing up the configuration:

switch1:admin> configupload
Server Name or IP Address [host]: 1.2.3.4
User Name [user]: matty
File Name [config.txt]: switch1_config.txt
Protocol (RSHD or FTP) [rshd]: ftp
Password:
upload complete

After the configuration is uploaded, you will have a text file with you switches configuration on the remove server:

$ ls -l sw*

-rw-r--r--   1 matty    other       7342 Jul  7 09:15 switch1_config.txt

To restore a configuration, you can use the configDownload command. Both of these commands allow the paramters to be passed as arguments to the script, so they are ideal for automation (there is a backup script on the Brocade support site that can be used to automate configuration backups)

Testing and Restoring the Firmware version.

1.Enter the firmwaredownload –s cmd and set the auto commit options to “no”.

For example:

switch:admin> firmwaredownload -s

Server Name or IP Address: 10.32.220.100

FTP User Name: william

File Name:  /pub/v5.1.0/release.plist

FTP Password:

Do Auto-Commit after Reboot [Y]:  n

Reboot system after download [N]: y

Firmware is being downloaded to the switch. This step may take up to 30

minutes.

Checking system settings for firmwaredownload...

2. Restore back to the olderversion by “firmwareRestore” cmd.

3. Then enter the “firmwarecommit” to commit the olderversion.

Checking to be done after the upgradation activity on switch side.

firmwareShow Displays the current firmware level on the switch. For SilkWorm directors this

command displays the firmware loaded on both partitions (primary and

secondary) for both CPs. Brocade reco mmends that you maintain the same

firmware level on both partitions of  each CP within the SilkWorm director.

nsShow (Optional) Displays all devices directly connected to the switch that have logged

into the Name Server. Make sure the  number of attached devices after the

firmware download is exactly the same as  the number of attached devices prior to

the firmware download.

nsAllShow (Optional) Displays all connected devices to a fabric. Make sure the number of

attached devices after the firmware down load is exactly the same as the number

of attached devices prior to the firmware download.

fabricShow (Optional) Displays all switches in a fabric. Make sure the number of switches in

the fabric after the firmware download  is exactly the same as the number of

attached devices prior to the firmware download.