UNSOLVED

Tushar_Patel1

updated

12 years ago

1

4347

March 4th, 2015 13:00

What is the correct symconfigure verb for doing an unbind with SE 8?

We upgraded to UniVMAX v8 which required us to upgrade Solutions Enabler to v8 as well.  Using the symconfigure unbind verb with SE 8 generates message "The requested feature is not supported for this microcode or SYMAPI version".  What is the correct correct verb or method of performing an unbind with SE 8?

  • 1533

    0

    Posted March 4th, 2015 13:00

    Yes, we're using a VMAX 40K running 5876.268.174.  This is exactly what I was looking for. Thanks.

  • seancummins

    2 Intern

    •

    226 Posts

    1533

    1

    Posted March 4th, 2015 13:00

    Tushar,

    I'm assuming you're working with a VMAX 10k/20k/40k, right? The unbind operation was moved from symconfigure to the symdev/symdg/symsg/symcg commands.

    For example: symdev -sid 1234 -devs 100:101 unbind -Pool FCPool1

    Thanks,

    - Sean

  • Rasmmacias

    108 Posts

    1533

    1

    Posted March 5th, 2015 04:00

    Note: The symconfigure command is no longer used to perform bind, unbind,
    rebind,
    allocate, reclaim, and free operations on thin devices and thin pools.

    Unbinding thin devices

    An unbind action disassociates a thin device from a thin pool.

      For example, the following commands
    unbinds thin devices in device group
    MyDgfrom the thin pool Mythinpool:

    symdg -sid 234 -nop unbind -dg MyDg -pool Mythinpool

      The symsg and symcgcommands are the same as symdg command using -sg SgName and the -cg CgName, respectively.

      The following command unbinds thin devices 1078 - 1081 from the thin pool Mythinpool:

    symdev -sid 234-nop unbind -devs 1078:1081 -pool  Mythinpool

      Restrictions for unbinding thin devices

      The following are restrcitions for unbinding thin devices:

      ◆ Device cannot be mapped to a front-end port or in the Ready state

      ◆ Device cannot be masked

      ◆ Device cannot have active snap sessions

      ◆ Device cannot be held

      ◆ Device cannot be a source or target of a clone (src or tgt) session

      ◆ Device cannot be a metamember

      ◆ Device cannot be a part of an enabled SRDF CG group

      ◆ Device cannot be an SRDF device

      ◆ Device cannot be under FAST control