Please login or register. December 14, 2017, 04:53:10 PM

Author Topic: NPIV and dynamic Tracking Virtual FC  (Read 12162 times)

0 Members and 1 Guest are viewing this topic.

ronaldm

  • Jr. Member
  • **
  • Posts: 9
  • Karma: +0/-0
NPIV and dynamic Tracking Virtual FC
« on: December 16, 2011, 09:52:30 AM »
Hi,

I want to change the dynamic tracking to "no" on a system with virtual Fc adapters.
How can i do this? it is not possible to use the chdev command.
The default is "yes", so i can not remove the fc adapter and run cfgmgr.

thanks,

Ronald

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +0/-0
Re: NPIV and dynamic Tracking Virtual FC
« Reply #1 on: December 16, 2011, 11:14:34 PM »
To make changes to a device there are two methods:

bring the device to a "defined" state, and make the changes using chdev -l devname -a attrname=newvalue

If a device cannot be brought to a defined state (e.g., (virtual) disk adapter for rootvg) then a change to ODM only, followed by a reboot, will effect the change. The chdev command is the same as for dynamic except the argument -P is added.

Hopes this helps!

ronaldm

  • Jr. Member
  • **
  • Posts: 9
  • Karma: +0/-0
Re: NPIV and dynamic Tracking Virtual FC
« Reply #2 on: December 19, 2011, 07:30:31 AM »
That does'nt work:

fscsi0         Defined   C7-T1-01    FC SCSI I/O Controller Protocol Device
fscsi1         Available C8-T1-01    FC SCSI I/O Controller Protocol Device

# chdev -l fscsi0 -a dyntrk=no
Method error (/usr/lib/methods/chggen):
        0514-018 The values specified for the following attributes
                 are not valid:
     dyntrk     Dynamic Tracking of FC Devices

# chdev -l fscsi0 -a dyntrk=no -P
Method error (/usr/lib/methods/chggen):
        0514-018 The values specified for the following attributes
                 are not valid:
     dyntrk     Dynamic Tracking of FC Devices

# lsattr -El fscsi0
attach       switch    How this adapter is CONNECTED         False
dyntrk       yes       Dynamic Tracking of FC Devices        True
fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy True
scsi_id      0x31609   Adapter SCSI ID                       False
sw_fc_class  3         FC Class for Fabric                   True


Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +0/-0
Re: NPIV and dynamic Tracking Virtual FC
« Reply #3 on: December 19, 2011, 01:15:25 PM »
Fingers crossed! Lets look for default settings and values:

# odmget -q name=fscsi0 CuDv

CuDv:
        name = "fscsi0"
        status = 1
        chgstatus = 2
        ddins = "efscsidd"
        location = "07-08-02"
        parent = "fcs0"
        connwhere = "2"
        PdDvLn = "driver/iocb/efscsi"


From this I get the PdDvLn values I use for the next command:
# lsattr -D -c driver -s iocb -t efscsi   
attach       none         How this adapter is CONNECTED         False
dyntrk       no           Dynamic Tracking of FC Devices        True
fc_err_recov delayed_fail FC Fabric Event Error RECOVERY Policy True
scsi_id                   Adapter SCSI ID                       False
sw_fc_class  3            FC Class for Fabric                   True


So, there are the defaults. But what are the values for dyntrk?
# lsattr -R -c driver -s iocb -t efscsi -a dyntrk
yes
no


As your statements seem to be correct I would try deleting the fscsi0 device with rmdev -dl fscsi0.
If that fails you may need to add -R to recursively delete the devices.

On my system (with hardware fcs, but no SAN attached):
root@x101:[/home/padmin]odmget -q "name=fscsi0 AND attribute=dyntrk" CuAt

root@x101:[/home/padmin]chdev -l fscsi0 -a dyntrk=yes
Method error (/usr/lib/methods/chggen):
        0514-029 Cannot perform the requested function because a
                 child device of the specified device is not in a correct state.

root@x101:[/home/padmin]chdev -l fscsi0 -a dyntrk=yes -P
fscsi0 changed

root@x101:[/home/padmin odmget -q "name=fscsi0 AND attribute=dyntrk" CuAt

CuAt:
        name = "fscsi0"
        attribute = "dyntrk"
        value = "yes"
        type = "R"
        generic = "DU"
        rep = "sl"
        nls_index = 15



What you may need is this:
root@x101:[/home/padmin]rmdev -R -l fcs0                                 
fcnet0 Defined
sfwcomm0 Defined
fscsi0 Defined
fcs0 Defined
root@x101:[/home/padmin]chdev -l fscsi0 -a dyntrk=yes                   
fscsi0 changed
root@x101:[/home/padmin]


As a last resort you could use a odmdelete command to remove the single entry in CuAt

Before:
root@x101:[/home/padmin]lsattr -El fscsi0
attach       al           How this adapter is CONNECTED         False
dyntrk       yes          Dynamic Tracking of FC Devices        True
fc_err_recov delayed_fail FC Fabric Event Error RECOVERY Policy True
scsi_id      0x1          Adapter SCSI ID                       False
sw_fc_class  3            FC Class for Fabric                   True


verify record affected using odmget
root@x101:[/home/padmin]odmget -q "name=fscsi0 AND attribute=dyntrk" CuAt

CuAt:
        name = "fscsi0"
        attribute = "dyntrk"
        value = "yes"
        type = "R"
        generic = "DU"
        rep = "sl"
        nls_index = 15

An remove using odmdelete
root@x101:[/home/padmin]odmdelete -o CuAt -q "name=fscsi0 AND attribute=dyn>
0518-307 odmdelete: 1 objects deleted.

After:
root@x101:[/home/padmin]lsattr -El fscsi0                                   
attach       al           How this adapter is CONNECTED         False
dyntrk       no           Dynamic Tracking of FC Devices        True
fc_err_recov delayed_fail FC Fabric Event Error RECOVERY Policy True
scsi_id      0x1          Adapter SCSI ID                       False
sw_fc_class  3            FC Class for Fabric                   True


And we see dyntrk is back to default. Above is an "emergency" chdev -P operation, and a reboot is needed for the change to actually become effective.

ronaldm

  • Jr. Member
  • **
  • Posts: 9
  • Karma: +0/-0
Re: NPIV and dynamic Tracking Virtual FC
« Reply #4 on: December 19, 2011, 01:57:21 PM »
Micheal,

Ther is a different between FSCSI and Virtual fscsi. The default for fscsi dyntrk=no, the default for Virtual fscsi dyntrk=yes. Today i have a call logged by IBM. The had the following answer:

by design, the only option for "dyntrk" is "yes"  on virtual FC adapters on the NPIV client partitions. Neither the dyntrk nor the fc_err_recov can be disabled on the virtual FC adapters.

So , i have a problem because the compellent storage needed an incative Dynamic tracking. hope they have a solution for me.


thanks ,

Ronald

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +0/-0
Re: NPIV and dynamic Tracking Virtual FC
« Reply #5 on: December 23, 2011, 09:21:59 AM »
Thanks for the info on differences between the physical and virtual fscsi interfaces. I do not have easy access to NPIV for personal testing, unfortunately.

Again, note the lsdev -P command for getting the default settings, and lsdev -R for the ranges of values for attributes.

Finally, you can use the odmchange command to set dyntrk to an unsupported (by IBM) value and see if that solves your problem.
If that seems to work, both you and the storage VAR could begin by requesting a design change. (Maybe, if you are lucky, the virtual driver does not check the value/ignores it. I suspect the virtual dyntrk is only affected by what happens at the VIOS level rather than at the F-port value (hope I got that right, I get SAN terminology wrong on occasion).

Michael