dplug

1. Всегда скопируй dplug файд иначе он исчезнет после того как ты его загрузишь:copy bootflash:<dplug_name> bootflash:dplug_temp
2. Загрузи dplug: load bootflash:dplug_temp
3. Что бы посмотреть PID процесса, например fcns: ps -ef | grep fcns
4. Чтобы убить и перезапустить процесс: kill -9 <PID>

Чтобы правильно выбрать dplug, надо проверить полностью имя image который установлен на свиче: 

trabzon# show ver | grep image

  kickstart image file is: bootflash:/m9500-sf2ek9-kickstart-mz.4.2.9.bin

  system image file is:    bootflash:/m9500-sf2ek9-mz.4.2.9.bin

trabzon# show ver | grep MDS

  cisco MDS 9506 (6 Slot) Chassis ("Supervisor/Fabric-2")

Нам нужен dplug который для версии 4.2.9 и имеет sf2ek9 в названии. Кроме того он должен быть для платформы 9500.

Чтобы найти нужный файл:

1. telnet people.cisco.com
2. Перейти в нужную директорию в зависимости от ОС версии:

   Release	Location
   3.x	/auto/androme/REL_3_1_y_z
   3.2	/auto/andau/REL_3_2_y_z
   3.3-4-5	/auto/andr33/REL_3_3_y_z
   4.x	/auto/andankara/REL_4_x_y_z
   5.0.x	/auto/andbogota/REL_5_0_x_y_z
   5.1.x	/auto/andcairo/REL_5_1_x_y_z
   5.2.x	/auto/anddelhi/REL_5_2_x_y_z
   6.0.x	/auto/andedinburgh/REL_6_0_x_y_z
   6.1.x	/auto/andedinburgh/REL_6_0_x_y_z
   6.2.x	/auto/andfreetown/REL_6_2_x_y_z

   
   
3. cd build/images/gdb
4. ls *dplug*
5. copy the dplug image to ftp.cisco.com

DCNM overview

SCSI LUN discovery

SCSI LUN discovery feature can be used to find all targets (Disks and Tapes) and their LUNs(Logical Unit NUmbers) connected the local switch and/or remote switches.

SCSI LUN discovery feature uses -FFFFFD FCID address as a source to perform SCSI INQUIRY, REPORT LUNS, READ CAPACITY commands on SCSI devices.

mds9124(config)# show scsi-target disk 
--------------------------------------------------------------------------------
VSAN    FCID        PWWN                      VENDOR    MODEL             REV
--------------------------------------------------------------------------------
mds9124(config)# discover scsi-target local os all
discovery started
mds9124(config)# discover scsi-target remote os all
discovery started
mds9124(config)# show scsi-target status
discovery completed
mds9124(config)# show scsi-target disk
--------------------------------------------------------------------------------
VSAN    FCID        PWWN                      VENDOR    MODEL             REV
--------------------------------------------------------------------------------
10      0x250000    50:0a:09:82:99:9b:48:e0   NETAPP    LUN               811a

DPVM = Dynamic VSAN Port Membership

If task states that server HBAs can be moved from one MDS to another - time to use DPVM!

Step1: create VSAN an assign server's port to it.
mds9124(config)# vsan database
mds9124(config-vsan-db)# vsan 20 name BLUE
mds9124(config-vsan-db)# vsan 20 interface fc1/3
Traffic on fc1/3 may be impacted. Do you want to continue? (y/n) [n] y
mds9124(config-vsan-db)# exit

Step2: Create DPVM database for the HBA(s):

mds9124(config)# dpvm enable ! tab does not work on this command. You should type it manually

mds9124(config)# dpvm database

mds9124(config-dpvm-db)# device-alias Initiator vsan 20

Error: Device-alias dpvm  member unsupported in device-alias basic mode

!need to have enchanced mode for device-alias

mds9124(config)# device-alias mode enhanced

mds9124(config)# device-alias commit

mds9124(config-dpvm-db)# device-alias Initiator vsan 20

Successful. Commit should follow for command to take effect.

mds9124(config)# dpvm commit

Commit operation initiated. Check dpvm session status

Step3: activate DPVM database with a force parameter (without force commit might fail)

mds9124(config)# dpvm activate force

Successful. Commit should follow for command to take effect.

mds9124(config)# dpvm commit

Commit operation initiated. Check dpvm session status

Step4: verify the results

mds9124(config)# show dpvm status

DB is activated successfully, auto-learn is off, distribution is enabled,

Duplicated pwwn will be  Rejected.

mds9124(config)# show dpvm database

device-alias Initiator [21:00:00:e0:8b:0a:fc:6d] vsan 20

device-alias TestFcalias [50:0a:09:82:99:9b:48:e0] vsan 20

[Total 2 entries]

!In order to automatically copy DPVM configuraiton, on other switches you should do:
1. dpvm enable - on other switches
2. dpvm commit - on switch which has the configuration

Basic interface and VSAN configuation

mds9124(config)# interface fc1/5
mds9124(config-if)# switchport description Connection to Lancelot fc1/12
mds9124(config-if)# switchport speed 4000
mds9124(config-if)# switchport mode E

mds9124(config)# vsan database

mds9124(config-vsan-db)# vsan 10 name RED

mds9124(config-vsan-db)# vsan 10 interface fc1/3

Traffic on fc1/3 may be impacted. Do you want to continue? (y/n) [n] y

mds9124(config)# show vsan membership

vsan 1 interfaces:

    fc1/1             fc1/2             fc1/4             fc1/6

    fc1/8             fc1/9             fc1/10            fc1/11

    fc1/12            fc1/13            fc1/14            fc1/15

    fc1/16            fc1/17            fc1/18            fc1/19

    fc1/20            fc1/21            fc1/22            fc1/23

    fc1/24

vsan 10 interfaces:

    fc1/3           

mds9124(config)# show vsan

vsan 1 information

         name:VSAN0001  state:active

         interoperability mode:default

         loadbalancing:src-id/dst-id/oxid

         operational state:up

vsan 10 information

         name:RED  state:active

         interoperability mode:default

         loadbalancing:src-id/dst-id/oxid

         operational state:up

! VSAN configuration should me manually done on all switches
! VSAN should ALWAYS be configured in the VSAN alowed trunk list otherwise all configured VSANs wil use the trunk.

Fibre Channel Addressing - FCIDs

MDS Fabric Switch assigns a VSAN-wide unique FCID to each device (HBA Port or Disk Drive) during the FLOGI. Other vendor switches assign a banric-wide unique FCID to each device.

The 24-bit FCID consists of three 8-bit fields:
1st byte - Domain ID of a switch the device is connected to.
2nd byte - Area ID - for each N_Port and NL_Port, the switch will assign area field started at 0x00 and incrementing by one for each consecutive ogin
3rd byte - Device ID 

Well-known FCID addresses:

• 0xFFFFFA - Management Server
• 0xFFFFFB - Time Server
• 0xFFFFFC - Name Server/Directory Server (show fcns database)
• 0xFFFFFD - Fabric Controller (Used for communication between switches)
• 0xFFFFFE - Fabric F_Port (Used by N_Ports for Fabric Login)

Fibre Channel Addressing - WWNs

WWN (Worldwide Name) is a unique 64-bit value that is assigned to a device at the factory.

Each N_Port and NL_Port (HBA port or Starage Disk) has one nWWN and one or more pWWNs (port WWN):

canterbury# sho flogi database
---------------------------------------------------------------------------
INTERFACE  VSAN    FCID            PORT NAME               NODE NAME
---------------------------------------------------------------------------
fc1/5       1     0xef0000  50:0a:09:81:99:9b:48:e0  50:0a:09:80:89:9b:48:e0     [Netapp]
fc1/12     1     0xef0003  50:05:07:63:0e:00:08:f3  50:05:07:63:0e:fe:08:f3        [Panda]
fc1/16     1     0xef0004  10:00:00:00:c9:32:27:85  20:00:00:00:c9:32:27:85

Total number of flogi = 3.

Each F_Port (physical port on the switch) has one fWWWN (fabric WWN)

mds9506# show interface fc 1/1

fc1/1 is down (SFP not present)

    Hardware is Fibre Channel

    Port WWN is 20:01:00:05:30:00:9b:9d

Each Fabric Switch has one sWWN (switch WWN)

mds9506# show wwn switch

Switch WWN is 20:00:00:05:30:00:9b:9d

Each VSAN has its own VSAN sWWN.

mds9506# show fcdomain vsan 1

The local switch is the Principal Switch.

Local switch run time information:

        State: Stable

        Local switch WWN:    20:01:00:05:30:00:9b:9e

        Running fabric name: 20:01:00:05:30:00:9b:9e