Enable/Disable auto meta using Solution Enabler SYMCLI

Product:

Solutions Enabler SYMCLI 7.x, Enginuity: 5773, 5874,5875

Description:

Procedure to enable/disable auto meta using Solution Enabler SYMCLI and SMC.

Solution:

If you want to create a single regular device larger than the maximum size, Symmetrix will create a metadevice instead when auto meta feature is enabled. If auto meta is disabled (which is by default), creating device fails. Auto meta feature was introduced with Solutions Enabler V6.5.1 running Enginuity version 5773, which allows metadevices to be created in a single configuration change session.

For Enginuity 5874, the maximum device size in cylinders is 262668.
For Enginuity 5773 and earlier, the maximum device size in cylinders is 65520.

Auto meta can be enabled only if the other auto meta parameters min_auto_meta_size, auto_meta_config and auto_meta_member_size are set to valid values. The settings are Symmetrix-wide.

Min_auto_meta_size: Specifies the size threshold that triggers auto meta creation. When you try to create a device greater than min_auto_meta_size and auto_meta is enabled then a meta will be created. The min_auto_meta_size cannot be set less than the auto_meta_member_size, and needs to be less than or equal to the value in the table below.
Auto_meta_member_size: Specifies the default meta member size in cylinders when the auto_meta feature is enabled. Needs to be less than or equal to the value in the table below.
Auto_meta_config: Specifies the default meta config when the auto_meta feature is enabled. Possible values are CONCATENATED, STRIPED, or NONE.

Enginuity version	Max single device size (CYL)	Max single device size (GB)	Min_auto-meta_size (CYL)	Auto_meta_member_size (CYL)
5874	262668	240	262669	262668
5773	65520	59	65521	65520

To enable auto meta using Solution Enabler:

1. Run the following command to verify if auto meta is disabled: symcfg list -sid xxxx -v
2. If not, create a file 1.txt and add the following text: set Symmetrix auto_meta=enable, min_auto_meta_size=xxxx, auto_meta_member_size=xxxx, auto_meta_config=xxxx;
3. Run the following command: symconfigure -sid xxxx -f 1.txt commit -nop
4. Verify if auto meta is enabled.

To enable the auto meta using SMC:

1. Right-click the Symmetrix ID and select Symmetrix Admin, Set Symmetrix Attributes
2. Enable Auto Meta feature, and enter the Minimum Auto Meta Size, Auto Meta Member Size, Auto Meta Configuration.
3. Click Add to Configure Session List and Commit the change.

NOTE:

• Auto meta feature is not applicable for CKD devices.
• Internal device types DATA, SAVE, DRV cannot be metadevices, therefore, they can't be larger than maximum size.
• You can override the auto_meta_member_size and the auto_meta_config in the create device command line only if auto_meta is ENABLED and the total device size is greater than min_auto_meta_size.

Permanent Sparing Process

Permanent Sparing:

 

An automated, self healing process that runs on the service processor to permanently replace a failing drive with a spare drive through a configuration change. Permanent Sparing can also be thought of as a “permanent replacement.”

 

Direct Sparing:

An automated, self healing process that runs on the service processor that invokes a spare drive and adds it as another member of the RAID group. The failing drive is removed when the copy process is finished.

 

Spare drive:

A physical drive that is not user accessible and is reserved for use by Replacement sparing in the event of a drive failure

 

Permanent Sparing Process

When Symmetrix Enginuity detects that a drive is about to fail, the Permanent Sparing

process begins.It looks for a spare drive of the same block size, capacity, and speed

in a good location to permanently replace the failing drive by means of a configuration change. Permanent Sparing is used in:

Enginuity 5874

Enginuity 5875

Enginuity 5876 with RAID 6(14+2)

 

The Permanent Sparing process identifies a good spare location using the following

rules:

No RAID 1 mirror or RAID 5 group member on the same loop

No more than two members of the same RAID 6 group on the same loop

Note:

If the process cannot identify a spare in a good location, or if the Permanent Sparing process cannot begin for any reason, the system calls home to the EMC Customer Support Center to inform that immediate replacement is required. When a suitable spare is identified, the Permanent Sparing process loads a new configuration file in which all the logical volumes initially configured on the failing drive are now configured on the selected spare (new) drive. The configuration change typically takes a few seconds to complete, during which time the configuration is locked. Data is then rebuilt onto the new drive. The Symmetrix system continues to process host I/O requests at the highest priority to minimize any effects on performance. The configuration is not locked during the rebuild process. The failed drive becomes a Not Ready spare in the spare pool and can be replaced at a later date. Multiple spares are planned for each array to be available for subsequent drive failures. The Not Ready state prevents the drive from being introduced onto the back-end Fibre Channel loop in the event of system power cycle, system IML, or disk director IML. The Not Ready setting will be removed once the drive is physically

replaced, at which time it will again become an available spare.

 

EMC VMAX – Solutions Enabler Versions Required For Enginuity Levels

To confirm that your Solutions Enabler version is supported for the level of Enginuity running on your Symmetrix VMAX please reference the following Knowledge Base support.emc.com/kb/52982
The following table details the Minimum required Solutions Enabler version required:

Note: Check EMC Online Support for the latest Solutions Enabler version and release notes.

calculate free space in veritas volume.

# vxdg list
NAME         STATE                ID
ossctedbdg   enabled,cds          1313610087.29.ossdhcp01

Method 1:

# vxdg -g ossctedbdg free

DISK         DEVICE       TAG            OFFSET    LENGTH   FLAGS
ossctedbdg32 xp24k0_08d4 xp24k0_08d4      10401792  256      -
ossctedbdg33 xp24k0_08d5 xp24k0_08d5      10401792  256      -
ossctedbdg34 xp24k0_08d6 xp24k0_08d6      10401792  256      -
ossctedbdg35 xp24k0_08d7 xp24k0_08d7      10401792  256      -
ossctedbdg36 xp24k0_08d8 xp24k0_08d8      10401792  256      -
ossctedbdg43 xp24k0_08ba xp24k0_08ba      419346432 256      -
ossctedbdg213 xp24k0_0081  xp24k0_0081  104943872 942862992  -


Lenth*512/(1024*1024) = value in MB

in this case :  942862992*512/1024*1024=460383

 
Method 2:

# vxassist -g ossctedbdg maxsize
Maximum volume size: 942864384 (460383Mb)

EMC VMAX Online TDEV (striped) Meta expansion (courtesey Brian)

The following took quite a bit of trial and error on my part, when EMC setup our environment, they turned the Autometa feature on, so when a DEV is created larger then 240gb, it automatically rounded up and created 100gb slices and forms striped METAs. In my understanding, striped meta volumes are not really benificial in a thin pooled environment, that EMC best practices call for concatenated METAs (as each concatenated slice is striped across the entire thin pool allready)

Unfortunatly we were already stuck in this config and hundreds of our META volumes were setup as striped. It is far easier to expand a concatenated META (concatenated METAs also dont have hyper size restrictions) I could find no easy document listing how to expand a striped meta that was a TDEV and the only other blog online I found mentioned expanding a standard Device and not a TDEV. So here you go!

         UPDATE: I've since learned from EMC that the advantage of having striped metas in a thin pool environment provides more I/O "hooks" (as our SE put it) on the front end to the host and can increase performance for high I/O intensive applications when compared to a standard TDEV or a concatenated meta.

1. For a protected (online) expansion, create a BCV+TDEV Meta the same size as the TDEV Meta you wish to expand, with the same size hypers.

· Use the "configure" command to create a copy of the original Meta's configuration (Members and hyper size and bind location which you will have to unbind from)

· symconfigure -cmd "configure 1 devices copying dev xxxx(orig meta) overriding config=BCV+TDEV;" prep

· Unbind from thin pool then bind fully allocated and with persistent flag on :::::IMPORTANT:::::

· symconfigure -cmd "unbind tdev xxxx(new BCV+TDEV meta head) from pool <thin_pool>;" prep

· symconfigure -cmd "bind tdev xxxx(new BCV+TDEV meta head) to pool <thin_pool> PREALLOCATE SIZE = ALL, allocate_type = persistent;" prep

· This will take some time (10 to 15 min depending on size) as it needs to pre-allocate all the space to the pool.  Wait for pre-allocation to complete before continuing 

Note: If you manually create the TDEV meta to be used as a BCV, you can use this to convert it: symconfigure -cmd "convert dev xxxx to BCV+TDEV;" prep

2. Create new Meta members for the original META, the same size as existing members (in cylinders), with the number to achieve amount needed for expansion (Leave them unbound)

· symconfigure -cmd "create dev count=4, size=xxxxxx,config=TDEV, emulation=fba;" commit

· Do not bind

3. Then finially run this command to expand the original META, using the BCV Meta created in step 1:

· symconfigure -cmd "add dev xxxx:xxxx to meta xxxx, protect_data=TRUE, bcv_meta_head=xxxx;" prep

It should run for quite some time, as it copies all data to the BCV, expands the original volume, then copies/re-stripes the data back, including on to the new Meta members. We have seen it bring our back end director utilization to over 80% during the entire expansion, so plan on doing it during a time of low utilization.

After the expansion completes the BCV+TDEV can be cleaned up and deleted


==========================================================================
 Convert all the existing  concatenated metas to striped metas.

Here are the steps to do a conversion:

1)    Create a new meta of the same size and number of members of the meta to be converted:   symconfigure –sid <x> -cmd “create dev count=1 size=<x> gb, emulation=FBA,         config=TDEV;” commit
2)    Bind the new meta to a pool:   symconfigure –sid <x> -cmd “bind tdev <x> to pool <pool name>;” commit
3)    Change the new meta to be a BCV:   symconfigure –sid <x> -cmd “convert dev <x> to bcv+tdev;” commit
4)    Preallocate the new BCV:  symconfigure -sid <x> -cmd "start allocate on tdev <x>, start_cyl=0 end_cyl=last_cyl allocate_type=persistent;" commit
5)    Run the conversion:  symconfigure -sid <x> -cmd "convert meta <x>, config=striped, protect_data=TRUE, bcv_meta_head=<BCV device>;" commit

The last step will take some time;  it took about 30 minutes to convert a 200GB two-member meta when I was testing. 

 

Difference between Fabric Switches and Directors

A director is a class of switch where everything is redundant. Two power supplies, two supervisors, redundant backplane, hot upgrades, etc. So that nothing should bring the director level switch down and cause outage

Port states in Brocade

Differences between port states, reported when execute the switchshow command (online, offline, no light, not sync, etc...). 
I noticed that sometimes a particular is disable and its state show "no light" and other time its state says "not sync". Why?

Online/In_Sync
Normal operating port with a connected device / ISL to other switch. "Online" is the operating state, "In_Sync" the physical state of the receiver/transmitter. (to see the in_sync you have to issue a portshow, switchshow doesn't display it)
 
No_Module 

no gbic/sfp inserted

No_Light 

gbic/sfp inserted, maybe even cable connected, but receiving no light
Disabled/Offline

If you disable a port (via portdisable) its operating state goes to offline. Fabric OS doesn't check offline ports, this means the physical port state is nt display as whatever it was

 If there was a device previously connected it displays as disabled/in_sync, if there was none it displays as disabled/no_light (or no_module). This physical state is only updated when you enable the port again.
swFCPortPhyState: noCard(1), noGbic(2), laserFault(3), noLight(4), noSync(5), inSync(6), portFault(7), diagFault(8), lockRef(9)
swFCPortOpStatus: unknown(0), online(1), offline(2), testing(3), faulty(4)

Port State in switchshow Description

No_Card No interface card present
No_Module No module (SFP or other) present
No_Light Module not receiving light
No_Sync Module receiving light but out of sync
In_Sync Module receiving light and in sync
Laser_Flt Module signaling a laser fault
Port_Flt Port marked faulty
Diag_Flt Port failed diagnostics
Lock_Ref Locking to the reference signal
Testing Running diagnostics
Online Port is up and running

How to find the HOST WWN in BROCADE switch?

fcsw2:admin> nodefind 50:01:43:80:02:a3:00:16
Remote:
Type Pid    COS     PortName                NodeName
N    101501;2,3;50:01:43:80:02:a3:00:16;50:01:43:80:02:a3:00:17;
FC4s: FCP
NodeSymb: [41] "QMH2462 FW:v4.04.09 DVR:v8.02.01-k1-vmw43"
Fabric Port Name: 20:16:00:05:1e:04:0c:df
Permanent Port Name: 20:11:00:24:81:76:9a:62
Device type: NPIV Initiator

Port Index: 21 //same as 15 hex above

Share Area: No
Device Shared in Other AD: No
Redirect: No
Aliases: mat_esxs3 mat_esxs3

fcsw2:admin> fabricshow
Switch ID   Worldwide Name    Enet IP Addr    FC IP Addr      Name
-------------------------------------------------------------------------
4: fffc04 10:00:00:05:1e:34:7d:9b 16.53.144.100 0.0.0.0  >"fcsw2"
16:fffc10 10:00:00:05:1e:04:0c:df 16.53.146.146 0.0.0.0        "shishapangma" 

 FCID is 101501: Domain = 0x10(16), Area = 0x15(21), so we're looking for switch ID 0xfffc10, port 21.

Difference between WWN and WWPN?

A WWPN (world wide port name) is the unique identifier for a fibre channel port where a  WWN (world wide name) the unique identifier for the node itself.

A good example is a dual port HBA.  There will be two WWPN's (one for each port) and only a single WWN for the card itself.

It's actually the firt octet that is changing. For example the portName for my multiport Emulex card is 10000000c9592f6c. The NodeName is 2000000c9592f6c. The "1" is simply changed for "2". This is occuring for AIX Servers and Windows Servers. There is also a minor change between the portName and NodeName for my Clariion SP ports. For example portName shows 500601613021788f and NodeName for the same SP port shows 500601603021788f. The 61 changed to 60.

How to find zone directly from Host WWN in CISCO ?

pacdcmdsa3# show zone member ?
  fcalias  Alias Name
  fcid     FCID
  pwwn     WWN
 
 Example:

pacdcmdsa3# show zone member pwwn 21:00:00:1b:32:0e:32:b7
 pwwn 21:00:00:1b:32:0e:32:b7 vsan 1
  zone pacdcldom0014_clarion_spa0
  zone pacdcldom0014_clarion_spb0

How to Find Brocade switch Model?

pacdcbr5100a08_a:admin> switchshow
switchName: pacdcbr5100a08_a
switchType: 66.1
switchState: Online
switchMode: Native
switchRole: Subordinate

switch type output dispalys gives the model number  with 1.X for the brocade 1000 family,2.x for the
brocade 2800 family.The value x refers to motherboard Revision level
 
Switch Type Switch Name
1 Brocade 1000 Switches
2,6 Brocade 2800 Switch
3 Brocade 2100, 2400 Switches
4 Brocade 20x0, 2010, 2040, 2050 Switches
5 Brocade 22x0, 2210,2240, 2250 Switches
7 Brocade 2000 Switch
9 Brocade 3800 Switch
10 Brocade 12000 Director
12 Brocade 3900 Switch
16 Brocade 3200 Switch
17 Brocade 3800VL
18 Brocade 3000 Switch
21 Brocade 24000 Director
22 Brocade 3016 embedded Blade Switch
23 8Gbit 10-port embedded fabric switch
26 Brocade 3850 Switch
27 Brocade 3250 Switch
29 Brocade 4012 EmbeddedBlade Switch
32 Brocade 4100 Switch
33 Brocade 3014 Switch
34 Brocade 200E Switch
36 Brocade FR4-18i DirectorBlade
37 Brocade 4020 Embedded Blade Switch
38 Brocade 7420 SAN Router
40 Fibre Channel Routing (FCR) Front Domain
41 Fibre Channel Routing (FCR) Xlate Domain
42 Brocade 48000 Director
43 Brocade 4024 Embedded Blade Switch
44 Brocade 4900 Switch
45 Brocade 4016 Embedded Blade Switch
46 Brocade 7500 Switch
47 Brocade FC4-16IP Director Blade
50 Brocade 4GB FC Port Blade
51 Brocade 4018 Embedded Blade Switch
55 Brocade FA4-18i Extension Director Blade
55,2 Brocade 7600 Switch
58 Brocade 5000 Switch
62 Brocade DCX Backbone
63 Brocade 8Gb Backbone Core Fabric Switch
64 Brocade 5300 Switch
66 Brocade 5100 Switch
67 Brocade Encryption Switch
68 Brocade 8Gb 16 FC 2 GigE ports Director Encrypti
on Blade
69 Brocade 5410 Blade
70 Brocade 8GB 10 Port Embedded Fabric Switch
71 Brocade 300 Switch
72 Brocade 5480 Embedded Blade Switch
75 Brocade M5424 Embedded Blade Switch
76,6 Brocade 8000 FCoE Switch
77,3 Brocade DCX-4S
82 Brocade 8Gb 24-port Embedded Blade Switch
83 Brocade 16-FC port,
6-GE port, auto sensing 1, 2, 4 or 8Gbit Switch
86 Brocade 8Gbit 26-port embedded Switch
88 Brocade 10Gb 24 GigE ports DCE Blade
89 Brocade 8Gb 12 FC, 1Gb 10 GigE FCIP Blade, 10Gb
2 GigE ports FCR
***************************************************

TYPE SPEED IBM TYPE IBM MODEL NAME BROCADE MODEL NAME
 
2.x 1 Gbps 3534-1RU Brocade 2010
3.x 1 Gbps 2109-S08 Brocade 2400
6.x 1 Gbps 2109-S16 Brocade 2800
9.x 2 Gbps 2109-F16 Brocade 3800 (Cylon)
10.x 2 Gbps 2109-M12 Brocade 12000 (Ulysses)
12.x 2 Gbps 2109-F32 Brocade 3900 (Terminator)
16.x 2 Gbps 3534-F08 Brocade 3200 (Mojo)
21.x 2 Gbps 2109-M14 Brocade 24000 (Meteor)
22.x 2 Gbps IBM BladeCenter Module Brocade 3016 (Blazer)
26.x 2 Gbps 2005-H16 Brocade 3850 (Dazzler)
27.x 2 Gbps 2005-H08 Brocade 3250 (DazzlerJR)
32.x 4 Gbps 2005-B32 SAN32B-2 Brocade4100 (Pulsar)
34.x 4 Gbps 2005-B16 SAN16B-2 Brocade200E (Stealth)
37.x 4 Gbps IBM BladeCenter module Brocade 4020 (Blazer2)
38.x 2 Gbps 2109-A16 SAN16B-R BrocadeAP7420 (Mars)
42.x 4 Gbps 2109-M48 SAN256B Brocade48000 (Saturn)
43.x 4 Gbps HP BladeCenter Module Brocade 4024
44.x 4 Gbps 2005-B64 SAN64B-2 Brocade4900 (Viking)
46.x 4 Gbps 2005-R18 SAN18B-R Brocade7500 (Sprint)
46.x 4 Gbps 2005-R04 SAN04B-R Brocade7500E (Sprint)
58.x 4 Gbps 2005-B5K SAN32B-3 Brocade5000 (Pulsar2)
62.x 8 Gbps 2499-384 SAN768B BrocadeDCX
64.x 8 Gbps 2498-B80 SAN80B-4 Brocade5300
66.x 8 Gbps 2498-40E SAN40B-4 Express Brocade 5100
66.x 8 Gbps 2498-B40 SAN40B-4 Brocade5100
67.x 8 Gbps 2498-E32 Encryption Switch Brocade Encryption Switch
71.x 8 Gbps 2498-24E SAN24B-4 Express Brocade 300
71.x 8 Gbps 2498-B24 SAN24B-4 Brocade300
73.x 8 Gbps 10 port IBM BladeCenter moduleBrocade 5470 (Blazer3)
73.x 8 Gbps 20 port IBM BladeCenter moduleBrocade 5470 (Blazer3)
76.x CEE 3758-B32 IBM Converged Switch Brocade 8000
77.x 8 Gbps 2499-192 SAN384B BrocadeDCX-4S
83.x 8 Gbps 2498-R06 SAN06B-R Brocade7800
121.x 16 Gbps 2499-416 SAN384B-2 BrocadeDCX8510-4
120.x 16 Gbps 2499-816 SAN384B-4 BrocadeDCX8510-8
109.x 16 Gbps 2499-F48 SAN48B-5 Brocade6510

CISCO fabrics -MDS-3

CLI command modes :


Switch #

Exec mode :enables temporary changes to terminal settings ,perform basic tests,display system info.

Changes made in this mode are generally not saved across system resets.

Switch(config)#

configuration mode :enables configuration of features that affect the system as a whole .Chnages made on tis mode are saved acrosssystem resets.

To obtain a list of available commands use ?


NO form of commands :

Issue the no form of any commands to perform the following actions:

1.Undo wrongly issued command

2.Delete a created facility

 eg:delete a previouslt created zone.

eg: # no member pwwn 1:2:3:4:5
    # no zone name test vsan 1


 1. Turn the port on and give it a description:

SAN01# config t

Enter configuration commands, one per line.  End with CNTL/Z.

pacdcmdsa3(config)# interface fc4/30

pacdcmdsa3(config-if)# no shutdown

pacdcmdsa3(config-if)# switchport description deploy01

pacdcmdsa3(config-if)# exit

pacdcmdsa3(config)#

pacdcmdsa3# copy running startup

[########################################] 100%

2 .create VASN &Add the port to a vsan:

pacdcmdsa3# config t

Enter configuration commands, one per line.  End with CNTL/Z.

pacdcmdsa3(config)#vsan database

pacdcmdsa3(config-vsan-db)# vsan 10

pacdcmdsa3(config-vsan-db)# vsan 10 name test_vsan_10

pacdcmdsa3(config-vsan-db)#end

# show vsan 10




pacdcmdsa3# config t

Enter configuration commands, one per line.  End with CNTL/Z.

pacdcmdsa3(config)#vsan database

pacdcmdsa3(config-vsan-db)# vsan 10

pacdcmdsa3(config-vsan-db)# vsan 10 interface fc4/30

Traffic on fc4/30 may be impacted. Do you want to continue? (y/n) y

pacdcmdsa3(config-vsan-db)# exit

pacdcmdsa3(config)#

3 .Make pwwn alias:


pacdcmdsa3# config t

Enter configuration commands, one per line.  End with CNTL/Z.


pacdcmdsa3(config)# fcalias name deploy01 vsan 10


pacdcmdsa3(config-fcalias)# member pwwn 21:00:00:e0:8b:8f:e9:7e


pacdcmdsa3(config-fcalias)# exit

4 .Create the zone:

pacdcmdsa3# config t

Enter configuration commands, one per line.  End with CNTL/Z.


pacdcmdsa3(config)# zone name deploy01 vsan 10

pacdcmdsa3(config-zone)# member fcalias deploy01

pacdcmdsa3(config-zone)# member fcalias nsd05-r1

pacdcmdsa3(config-zone)# member fcalias nsd05-r2

pacdcmdsa3(config-zone)# exit

pacdcmdsa3(config)# exit

pacdcmdsa3#

View the zone:

pacdcmdsa3 # show zone name deploy01              

zone name deploy01 vsan 10
  fcalias name nsd05-r1 vsan 10
    pwwn 20:14:00:a0:b8:11:33:d0
 
  fcalias name nsd05-r2 vsan 10
    pwwn 20:24:00:a0:b8:11:33:d0
 
  fcalias name deploy01 vsan 10
    pwwn 21:00:00:e0:8b:8f:e9:7e


5 .Add the zone to a zoneset:

pacdcmdsa3# config t

Enter configuration commands, one per line.  End with CNTL/Z.

pacdcmdsa3(config)# zoneset name san01_prod10 vsan 10

pacdcmdsa3(config-zoneset)# member deploy01

pacdcmdsa3(config-zoneset)# exit

pacdcmdsa3(config)#

Check the zoneset name. Grab the name from the first line of output from:


pacdcmdsa3# show zoneset

zoneset name san01_prod10 vsan 10

6. Activate the zoneset


pacdcmdsa3# config t
Enter configuration commands, one per line.  End with CNTL/Z.

pacdcmdsa3(config)# zoneset activate name san01_prod10 vsan 10

Zoneset activation initiated. check zone status

pacdcmdsa3(config)# exit

pacdcmdsa3# copy running startup
[########################################] 100%

pacdcmdsa3#


7 .Add a user to the cisco mds with network-admin privileges.


pacdcmdsa3# config t

Enter configuration commands, one per line.  End with CNTL/Z.

pacdcmdsa3(config)# username username password password role network-admin

pacdcmdsa3(config)# snmp-server user username network-admin auth md5 password

pacdcmdsa3(config)# exit

pacdcmdsa3# copy running startup
[########################################] 100%

pacdcmdsa3#

8. When attaching symmetrix to your switches its best practice to hard set the ports to 4gb.


pacdcmdsa3(config-if)# int fc3/18

pacdcmdsa3(config-if)# switchport speed 4000

switchport speed auto

9. Rename Fibre Channel aliases using the fcalias rename command like this:

switch(config)# fcalias rename <old alias> <new alias> vsan 10

You can also rename zones:

switch(config)# zone rename <old zone name> <new zone name> vsan 10

And you can rename zonesets:

switch(config)# zoneset rename <old zoneset name> <new zoneset name> vsan 10

10. Search for  thread

switch# show zone | include server-name

pacdcmdsa3# show flogi database|include 21:00:00:24:ff:06:84:cb  (works like grep)

11. Set mode

mds-switch-1# conf t
Enter configuration commands, one per line. End with CNTL/Z.
mds-switch-1(config)# interface fc 1/1
mds-switch-1(config-if)# switchport mode E
mds-switch-1(config-if)# end

12. configure domain ID :

 Configure the switch in  vsan 10 to request a preffered domain 3 and accept any value assigned by the principal switch.


mds-switch-1(config)# fcdomain domain 3 preffered vsan 10

configure the switch in vsan 10 accept only a specific value and moves the local interfaces in vsan 10 to an isolated state if the requested id is not granted.

mds-switch-1(config)# fcdomain domain 3 static vsan 10

Valid domain IDs are numbers between 1-239


13.Configure priority 25 for the local switch in VSAN 10

mds-switch-1(config)# fcdomain priority 25 vsan 10


14 name server statistics

show fcns statistics

15. Rename switch

   # config t
   # switchname newname
   # exit
   # show switchname

16. set speed auto for 3 interfaces

   # config t
   # interface fc1/1 ,fc1/2,fc1/3
   # switchport speed auto
   # no shutdown
   # exit


Important commands :

show interface fc 1/11
show interface description
show interface brief
show logging info
show logging last 10
show running-config diff
show startup-config
show tech-support brief
show version
show zoneset
show running-config
show license usage
show vsan membership
show environment fan
show environment temperature

Data gathering : show tech-support

To move up one level from config mode or config sub mode type exit

To move up directly to the exec mode type end

How to find the HOST WWN in CISCO switch?

Assuming you know the pwwn of the HBA you are searching for, you can use the following steps to find the switch it is connected to:

 1) "show fcns database"  - find your pwwn in the output to detemine what FCID is assigned to the device, and note the VSAN.  Also, the first byte of the FCID will indicated the Domain ID of the switch the device is attached to.

 2) "show topology vsan <vsan number from step 1>" search for the switch with the domain id determined in step 1.

 The "show topology" output also includes the IP address of the mgmt port, so you can quickly ssh/telnet to the host switch and than verify that you've identified the right switch with the output of "show flogi database".

Difference between FCAlias & Device-Alias

FC aliases are used to associate 1 or more PWWNs to a user friendly name.  FCaliases are VSAN specific, so if a device is moved from VSAN 1 to VSAN 2, you should delete the FCalias in VSAN 1 and create a new one in VSAN 2.  FCalias will interoperate with some non-Cisco fibre channel switches.FCaliases are propagated via a zoneset  activate.

Device aliases associate 1 PWWN to a user friendly name.  They are not vsan sepcific, and can be used for other features beside zoning.  Device Aliases are configured manually in each switch, or can be propagated via Cisco Fabric Services.There is a Device Alias mode known as enhanced  mode, which is not enabled unless configured.  With enhanced mode device alias, if an HBA is associated with a device alias, and that device alias is placed into 20 zones, then that HBA fails and is replaced so the PWWN changes, you can edit the device alias database and that will push the new PWWN into the 20 zones automatically.


replace XXX with the appropriate VSAN number):

switch(config)# fcalias name stor-array-processor-a vsan XXX
switch(config-fcalias)# member pwwn AA:BB:CC:DD:EE:FF:00:11
switch(config-fclias)# exit
switch(config)#


To create a device alias, you’ll use the device-alias database command in global configuration mode. Once you are in database configuration mode, you can create device aliases using the device-alias command, like this:


mds(config)# device-alias database
mds(config-device-alias-db)# device-alias name <Friendly name> pwwn <Fibre Channel WWPN>
mds(config-device-alias-db)# exit
mds(config)# end

There is an additional step required after defining the device aliases. You must also commit the changes to the device alias database, like this:

mds(config)# device-alias commit


This commits the changes to the device alias database and makes the device aliases active in the switch.

Once a device alias is created, it applies to that WWPN regardless of VSAN. This means that you only have to define a single device alias for any given WWPN, whereas with the fcalias command a different alias needed to be defined for each VSAN.

Using device aliases also provides a couple other key benefits:

    Device aliases are automatically distributed to other Cisco-attached switches. For example, I defined the device aliases on a Cisco MDS 9134 that was attached to the Fibre Channel expansion port of a Cisco Nexus 5010 switch. The Nexus switch automatically picked up the device aliases. As best I can tell, this is controlled by the device-alias distribute global configuration command (or its reverse, the no device-alias distribute, which would disable device alias distribution).
    Once a device alias is defined for a WWPN, anytime the WWPN is displayed the device alias is also displayed. So in the output of various commands like show flogi database, show fcns database, or show zone you will see not only the WWPN, but also that WWPN’s associated device alias.

CISCO fabrics -MDS-2

Major commands to view the details:

show fcns database

show flogi database

show fdmi database

show fcs database

show fcns database  : Gives VASN number: FCID(8bit): Vendor : PWWN details  of all ports in the fabric.- Name server database :

The name server functionality maintains a database containing the attributes for all hosts and storage devices in each VSAN.The name server stores name entries for all hosts in the FCNS database.

show flogi database : Gives interface ,VSAN,fCID,PORT WWN,node wwn of that particular switch

In a Fibre Channel fabric, each host or disk requires an FC ID. Use the show flogi command to verify if a storage device is displayed in the Fabric login (FLOGI). If the required device is displayed in the FLOGI table, the fabric login is successful.

FDMI::

show fdmi database / show fdmi database detail :

Cisco MDS 9000 Family switches provide support for the Fabric-Device Management Interface (FDMI) functionality.FDMI enables management of devices such as Fibre Channel .Host Bus Adapters (HBAs) through in-band communications.Using the FDMI functionality, the SAN-OS software can extract the following management information about attached HBAs and host operating systems without installing proprietary host agents:

•Manufacturer, model, and serial number

•Node name and node symbolic name

•Hardware, driver, and firmware versions

•Host operating system (OS) name and version number

pacdcmdsa1#  show fdmi database

Registered HBA List for VSAN 1

  10:00:00:00:c9:5d:ee:ce

  10:00:00:00:c9:61:1f:05

  21:00:00:1b:32:13:64:ef

  21:00:00:1b:32:82:0e:f4

  21:00:00:1b:32:82:5b:f2

  21:00:00:1b:32:82:66:db

  21:00:00:1b:32:82:8d:f2

  21:00:00:1b:32:82:8f:f5

 pacdcmdsa1#  show fdmi database detail

Registered HBA List for VSAN 1

-------------------------------

HBA-ID: 10:00:00:00:c9:5d:ee:ce

-------------------------------

Node Name                      :20:00:00:00:c9:5d:ee:ce

Manufacturer                     :Emulex Corporation

Serial Num                        :BG65140697

Hardware Ver                    :2057706d

Driver Ver                         :6.10g

ROM Ver                          :1.50a8

Firmware Ver                     :2.50A6 (Z2D2.50A6)

OS Name/Ver                    :SunOS 5.10 Generic_127127-11

CT Payload Len                 :525980

Port-id: 10:00:00:00:c9       :5d:ee:ce
Supported FC4 types         :scsi-fcp fc-gs
Supported Speed                :1G

Current Speed                     :2G

Maximum Frame Size          :2048

OS Device Name                :lpfc

RSCN ::

The Registered State Change Notification (RSCN) is a Fibre Channel service that informs hosts about changes in the fabric. Hosts can receive this information by registering with the fabric controller (through SCR). These notifications provide a timely indication of one or more of the following events:

•Disks joining or leaving the fabric.

•A name server registration change.

•A new zone enforcement.

•IP address change.

•Any other similar event that affects the operation of the host.

switch# show rscn scr-table vsan 1

SCR table for VSAN: 1

---------------------------------------------

FC-ID         REGISTERED FOR

--------------------------------------------

0x1b0300      fabric detected rscns

Total number of entries = 1

FCS::

The Fabric Configuration Server (FCS) provides discovery of topology attributes and maintains a repository of configuration information of fabric elements. A management application is usually connected to the FCS on the switch through an N port. The FCS views the entire fabric

pacdcmdsa1# show fcs database

FCS Local Database in VSAN: 1

------------------------------

Switch WWN               : 20:01:00:0d:ec:2a:65:41

Switch Domain Id         : 0x33(51)

Switch Mgmt-Addresses    : snmp://24.40.61.82/eth-ip

                                            http://24.40.61.82/eth-ip

                                            snmp://24.40.61.82/eth-ip

                                            http://24.40.61.82/eth-ip

Fabric-Name              : 20:01:00:0d:ec:2a:65:41

Switch Logical-Name      : pacdcmdsa1

Switch Information List  : [Cisco Systems, Inc.*DS-C9509*3.1(2)*20:00:00:0d:ec:2a:65:40]

Switch Ports:

-------------------------------------------------------------------

Interface  fWWN                     Type     Attached-pWWNs

-------------------------------------------------------------------

fc1/1      20:01:00:0d:ec:2a:65:40  TE       20:01:00:0d:ec:2d:33:c0

fc1/2      20:02:00:0d:ec:2a:65:40  F        50:06:04:82:d5:2d:b8:86

fc1/3      20:03:00:0d:ec:2a:65:40  Unknown  None

fc1/4      20:04:00:0d:ec:2a:65:40  Unknown  None

fc1/5      20:05:00:0d:ec:2a:65:40  TE       20:05:00:0d:ec:2d:33:c0

fc1/6      20:06:00:0d:ec:2a:65:40  F        50:06:04:82:d5:2d:b8:97

fc1/7      20:07:00:0d:ec:2a:65:40  Unknown  None

fc1/8      20:08:00:0d:ec:2a:65:40  Unknown  None

fc1/9      20:09:00:0d:ec:2a:65:40  F        50:06:04:8a:d5:2d:b8:86

fc1/10     20:0a:00:0d:ec:2a:65:40  F        50:06:01:60:3b:20:10:06

fc1/11     20:0b:00:0d:ec:2a:65:40  Unknown  None

fc1/12     20:0c:00:0d:ec:2a:65:40  Unknown  None

fc1/13     20:0d:00:0d:ec:2a:65:40  F        50:06:04:8a:d5:2d:b8:97

fc1/14     20:0e:00:0d:ec:2a:65:40  TE       21:41:00:0d:ec:a2:40:00

fc1/15     20:0f:00:0d:ec:2a:65:40  TE       21:4d:00:0d:ec:a2:40:00

fc1/16     20:10:00:0d:ec:2a:65:40  F        50:03:08:c0:01:c4:60:68

fc2/1      20:41:00:0d:ec:2a:65:40  F        21:00:00:1b:32:0b:8e:19

fc2/2      20:42:00:0d:ec:2a:65:40  F        21:00:00:1b:32:14:10:f5

fc2/3      20:43:00:0d:ec:2a:65:40  F        50:01:43:80:00:c2:82:80

fc2/4      20:44:00:0d:ec:2a:65:40  F        50:01:43:80:00:c2:83:66

fc2/5      20:45:00:0d:ec:2a:65:40  F        50:01:43:80:00:c2:82:14

fc2/6      20:46:00:0d:ec:2a:65:40  F        50:01:43:80:00:c2:82:4e

CISCO fabrics -MDS-1

Important terms to understand.

Fabric Manger  is a  single tool used to configure ,monitor and manage an entire fabric of switches,directors .With in fabric manager,an overview of the fabric and its topology can be obtained.

Device manager  is used to manage an individual switch/director including the installed switching modules,the supervisor modules ,the status of each port within each module,the power supplies and the fan assemblies. While fabric manager tables show values for one more switches ,device manager just can show values for single switch.

VSAN

Physical topology is divided into logical fabrics called VSANs.Zoning is assigned per VSAN.Switch ports are assigned to only one VSAN.By default all switch ports are assigned to VSAN 1.(One physical switch to be carved into several virtual fabrics).Default VSAN;VSAN 1 cant be deleted however it can be suspended

.

Isolated VSAN:

VSAN 4096 is the isolated VSAN.All non trunking ports are transferred to this VSAN when the VSAN to which they belong to is deleted. This avoids an implicit transfer of posts to the default VSAN or to another configured VSAN.

Domain Parameters:

The fcdomain feature performs principal switch selection ,domain id distribution ,FCID allocation and fabric reconfiguration function as described in the FC-SW2 standards.The domains are configured on a per VSAN basis.When a switch boots up or joins a new fabric, it can request a specific domain ID or take any available domain ID.The configured domain ID can be preffered or static .Bydefault the configured domain is 0 and the configured type is preferred. If a domain ID is not configured, the local switch sends a random ID in its request. If the configured type is preferred, the local switch accepts the domain ID assigned by the principal switch and the assigned domain ID becomes the runtime domain ID.If the configured type is static ,the assigned domain ID is discarded, all local interfaces are isolated and the local switch assigns itself the configured domain ID which becomes the runtime domain ID.After obtaining the domain ID from the principal switch in the VSAN, the local switch assigns Fibre Channel Identifiers (FC IDs) to each end device as they log into the fabric. This process is known as FLOGI.Domain ID uniquely identify a switch in VSAN.A switch may have different domain IDs in different VSANs. The domain ID is part of over all FCID.

Set switch priority:

By default ,the configured priority is 128.The valid range is between 1 and 254.Priority 1 has the highest Priority. Value 255 is accepted from other switches but cannot be locally configured. Any new switch can become the principal switch when it joins a stable fabric. During  the principal switch selection phase, the switch with highest priority becomes the principal switch. If two switches have same configured priority, the switch with lowest WWN becomes the principal switch.

Name server:

The nameserver  functionality maintains a database containing  the attributes for all hosts and storage devices in each VSAN.

G_port or generic port on a switch can operate as an E_port or F_port. Found on Brocade, McData, and QLogic switches.

N_port is a port on the node (e.g. host or storage device) used with both FC-P2P or FC-SW topologies. Also known as node port.
E_port-The port can be either a trunking or non trunking port depending on the trunking mode port mode.E port is used when the port talks to another port of different switch forming an ISL.

Scanning for New LUNS and add it to Veritas Volume manager:Solaris

format

cfgadm -al (scanning controller)

devfsadm -Cv (scanning new disk)

format

format -d c3t50060E8005B20241d55

partition -p


print current table -p

2nd wud be the full disk

l -label

q
q

==================================================================================


# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
disk_0       auto:none       -            -            online invalid
disk_1       auto:none       -            -            online invalid
xp24k0_0003  auto:cdsdisk    -            -            online
xp24k0_0004  auto:cdsdisk    -            -            online
xp24k0_0212  auto:cdsdisk    xp24k0_0212  clds2bdg     online
xp24k0_0213  auto:cdsdisk    xp24k0_0213  clds2bdg     online
xp24k0_0800  auto:simple     -            -            online invalid
xp24k0_0801  auto:simple     -            -            online invalid

====================================================================================

# vxdiskunsetup xp24k0_0800
# vxdiskunsetup xp24k0_0801

=====================================================================================


# vxdctl enable
# vxdisksetup -if xp24k0_0800 format=cdsdisk
# vxdisksetup -if xp24k0_0801 format=cdsdisk
=====================================================================================
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
disk_0       auto:none       -            -            online invalid
disk_1       auto:none       -            -            online invalid
xp24k0_0003  auto:cdsdisk    -            -            online
xp24k0_0004  auto:cdsdisk    -            -            online
xp24k0_0212  auto:cdsdisk    xp24k0_0212  clds2bdg     online
xp24k0_0213  auto:cdsdisk    xp24k0_0213  clds2bdg     online
xp24k0_0800  auto:cdsdisk    -            -            online thin
xp24k0_0801  auto:cdsdisk    -            -            online thin
==================================================================================================
# vxdg -g clds2bdg adddisk xp24k0_0800=xp24k0_0800  (1. vgname 2.next available group name=disk name)
# vxdg -g clds2bdg adddisk xp24k0_0801=xp24k0_0801

=============================================================================================
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
disk_0       auto:none       -            -            online invalid
disk_1       auto:none       -            -            online invalid
xp24k0_0003  auto:cdsdisk    -            -            online
xp24k0_0004  auto:cdsdisk    -            -            online
xp24k0_0212  auto:cdsdisk    xp24k0_0212  clds2bdg     online
xp24k0_0213  auto:cdsdisk    xp24k0_0213  clds2bdg     online
xp24k0_0800  auto:cdsdisk    xp24k0_0800  clds2bdg     online thin
xp24k0_0801  auto:cdsdisk    xp24k0_0801  clds2bdg     online thin

=============================================================================
# vxdg -g clds2bdg free
DISK         DEVICE       TAG          OFFSET    LENGTH    FLAGS
xp24k0_0213  xp24k0_0213  xp24k0_0213  102844160 1929728   -
xp24k0_0800  xp24k0_0800  xp24k0_0800  0         104773888 -
xp24k0_0801  xp24k0_0801  xp24k0_0801  0         104773888 -       50GB

=============================================================================
# hostname
cldsapp-nb-8p.cable.comcast.com
#
#vxdg -g cho-oyudg free  in bytes---divide bye 2 ..........

=============================================================================


# /usr/lib/vxvm/bin/vxresize -g cho-oyudg datavol90 +30G

        vxresize -g t1-clrdg-dr clr2-data8-dg +50G

==============================================================================


# df -k

Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t0d0s0    8267957 3932739 4252539    49%    /
/devices                   0       0       0     0%    /devices
ctfs                       0       0       0     0%    /system/contract
proc                       0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
swap                 13431048    1544 13429504     1%    /etc/svc/volatile
objfs                      0       0       0     0%    /system/object
sharefs                    0       0       0     0%    /etc/dfs/sharetab
fd                         0       0       0     0%    /dev/fd
/dev/dsk/c0t0d0s4    13479123 2134137 11210195    16%    /var
swap                 18897080 5467576 13429504    29%    /tmp
swap                 13429576      72 13429504     1%    /var/run
/dev/dsk/c0t0d0s5    115081722 14689916 99240989    13%    /opt
/dev/vx/dsk/clds2bdg/vol01
                     103809024 78294764 23934633    77%    /u02
=============================================================================
# vxresize -g clds2bdg vol01 +100G
=============================================================================
# df -h
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c0t0d0s0      7.9G   3.8G   4.1G    49%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                    13G   1.5M    13G     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
fd                       0K     0K     0K     0%    /dev/fd
/dev/dsk/c0t0d0s4       13G   2.0G    11G    16%    /var
swap                    18G   5.2G    13G    29%    /tmp
swap                    13G    72K    13G     1%    /var/run
/dev/dsk/c0t0d0s5      110G    14G    95G    13%    /opt
/dev/vx/dsk/clds2bdg/vol01
                       199G    75G   117G    40%    /u02

===================================================================================

VMAX architecture

The Symmetrix V-Max family includes 2 options for scalability and growth. The V-Max series scales from 48 to 2,400 disks and provides 2 Peta bytes of usable protected capacity when configuring all 1TB SATA disks. The V-Max SE scales from 48 to 360 disks and is intended for smaller capacity needs that require Symmetrix performance, availability, and functionality.

The V-Max architecture is comprised of up to 8 engines. Each engine is a pair of directors. Each director is a 2-way quad-core Intel Xeon 5400 system with up to 64GB memory.It provides support for Fibre Channel, iSCSI, Gigabit Ethernet, and FICON connected hosts. Front-end and back-end connectivity has doubled over the DMX-4 with up to 128host ports and 128 disk channels. The V-Max also leverages 2.3 Gigahertz multi-core processors. The new Virtual Matrix provides the interconnect that enables resources to be shared across all V-Max engines to enable massive scale out

The Virtual Matrix Architecture replaces individual, function-specific directors with Symmetrix V-Max Engines, each containing a portion of Global Memory and two directors capable of managing front end, back end, and remote connections simultaneously.. Scalability has improved in all aspects: front-end connectivity, Global Memory, back-end connectivity, and usable capacity. The increased usable disk capacity is the result of an increase in Global Memory combined with a significant reduction in metadata overhead allowing 2400 devices to be configured with RAID types other than RAID 1 resulting in a dramatic increase in usable capacity. The Virtual Matrix is redundant and dual active and supports all Global Memory references, all messaging, and all management operations including internal discovery and initialization, path management, load balancing, fail over, and fault isolation within the array. The Symmetrix V-Max array is comprised of 1 to 8 V-Max Engines. Each V-Max Engine contains two integrated directors .Each director has two connections to the V-Max Matrix Interface Board Enclosure (MIBE) via the System Interface Board or SIB ports. Since every director has two separate physical paths to every other director via the Virtual Matrix, this is a highly available interconnect with no single point of failure

Each director also has 8 back-end 4Gb/s FC ports (comprised of quad-port HBAs) and various options for the front-end including 8 4Gb/s FC ports. In the full configuration of 128 4Gb/s FC ports on the front and back ends, the expectation is that this system could deliver 40GB/s if there a no bottlenecks in the system architecture.

V-Max Engine Architecture

The full VMax system comprises 11 racks!

The center rack is for the VMax engines, the other 10 are storage bays. Each storage bay can hold up to 240 drives. There are 160 disk array enclosures, 64 directly connected, and 96 daisy chained. There are 8 VMax engines, as denoted by each color. 

When configuring the Symmetrix, there are different types of Hyper devices that can be configured.For example:

Standard devices (STD) are configured for normal production operations

Business Continuance (BCV) devices are configured for TimeFinder/Mirror replication

Virtual Devices (VDEV) are configured for TimeFinder/SNAP local pointer-based replication

Dynamic Reallocation Volumes (DRV) devices are configured for Symmetrix Optimizer hyper re-location

TDEV devices are virtual cache-only devices that can grow in capacity

Save Devices are configured for Time Finder/SNAP and/or TDEV devices

R1 and R2 for remote replication

Virtual devices can reduce wasted disk space because the actual data is kept in a common pool ;only what is used is allocated in the common pool and the pool is shared by many TDEV devices. Eg: the host has a 100 GB Virtual TDEV device, the TDEV device uses no disk space, the Save pool contains the actual data, and only 20 GB is allocated until more space is required. The allocated capability is managed by EMC software