Karl,
> Stepping back to this email... Please note that I ran the commands on
> the secondary box.
How about this missing one
# echo "::rdc_uinfo -v" | mdb -k
An this one.
# truss -f sndradm -i
Jim
>
>
> Jim Dunham wrote:
>> A couple of comments about SNDR secondary data.
>>
>> Although the following command will display 'metadata' contained in
>> the 'dscfg' persistence storage on the local host, it may be listing
>> deleted, or otherwise stale metadata.
>>
>> # strings /etc/dscfg_local
>>
>> The correct commands to display all active 'dscfg' records are:
>>
>> # dscfg -l (include comments)
>> or
>> # dscfg -l | grep -v "^#" (excluding comments)
>>
>> =========================
> -bash-3.00$ dscfg -l | grep -v "^#"
> scm: 128 64 - - - - - - -
> setid: 2 -
> sndr: primary /dev/rdsk/c2t17d0s7 /dev/rdsk/c0t0d0s5 secondary
> /dev/md/rdsk/d20 /dev/rdsk/c1t1d0s7 ip async - - setid=1; -
> sndr: primary /dev/rdsk/c2t17d0s6 /dev/rdsk/c0t1d0s6 secondary
> /dev/md/rdsk/d50 /dev/rdsk/c1t1d0s6 ip async - - setid=2; -
> sv: /dev/md/rdsk/d20 - -
> sv: /dev/rdsk/c1t1d0s7 - -
> sv: /dev/md/rdsk/d50 - -
> sv: /dev/rdsk/c1t1d0s6 - -
> dsvol: /dev/md/rdsk/d20 - sndr
> dsvol: /dev/rdsk/c1t1d0s7 - sndr
> dsvol: /dev/md/rdsk/d50 - sndr
> dsvol: /dev/rdsk/c1t1d0s6 - sndr
>
>
>> Here are some SDNR sample configuration commands
>>
>> 1). Show that nothing is enabled
>>
>> # sndradm -p
>
> outputs nothing
> -bash-3.00$ sndradm -p
>
>>
>> 2). Enable SNDR on this node
>>
>> # sndradm -e nws-bur-24-204 /dev/zvol/rdsk/avs/primary_2
>> /dev/zvol/rdsk/avs/bitmap_2 nws-bur-24-206
>> /dev/zvol/rdsk/avs/primary_2 /dev/zvol/rdsk/avs/bitmap_2 ip async
>> Enable Remote Mirror? (Y/N) [N]: y
>>
>> Note:
>> When configuring a replica, the exact same SNDR enable command must
>> be
>> issued on both the SNDR primary and SNDR secondary nodes.
> Yes I made sure of that.
>
> -bash-3.00$ /usr/sbin/sndradm -e primary /dev/rdsk/c2t17d0s6
> /dev/rdsk/c0t1d0s6 secondary /dev/md/rdsk/d50 /dev/rdsk/c1t1d0s6 ip
> async
> Enable Remote Mirror? (Y/N) [N]: y
> sndradm: Error: bitmap /dev/rdsk/c1t1d0s6 is already in use by
> StorEdge
> Network Data Replicator
>
> -bash-3.00$ /usr/sbin/sndradm -e primary /dev/rdsk/c2t17d0s7
> /dev/rdsk/c0t0d0s5 secondary /dev/md/rdsk/d20 /dev/rdsk/c1t1d0s7 ip
> async
> Enable Remote Mirror? (Y/N) [N]: y
> sndradm: Error: bitmap /dev/rdsk/c1t1d0s7 is already in use by
> StorEdge
> Network Data Replicator
>
>
>> 7a). scm: 128 64 - - - - - - -
>>
>> Is the same as the following:
>>
>> # scmadm -C
>> nthreads : 128 /* number of threads */
>> cache_size : 64 /* total cache size */
>>
>> 7b. setid: 4 -
>>
>> Internal value equal to the highest numbered replica every created.
>> See the 'setid' value in the next record.
>>
>> 7c). sndr: nws-bur-24-204 /dev/zvol/rdsk/avs/primary_2
>> /dev/zvol/rdsk/avs/bitmap_2 nws-bur-24-206
>> /dev/zvol/rdsk/avs/primary_2 /dev/zvol/rdsk/avs/bitmap_2 ip async - -
>> setid=4; -
>>
>> Is the same as the following, minus the internal 'setid' value
>>
>> # sndradm -i
>> nws-bur-24-204 /dev/zvol/rdsk/avs/primary_2
>> /dev/zvol/rdsk/avs/bitmap_2 nws-bur-24-206
>> /dev/zvol/rdsk/avs/primary_2 /dev/zvol/rdsk/avs/bitmap_2 ip async
> command outputs nothing
>
>>
>> 7d). sv: /dev/zvol/rdsk/avs/primary_2 - -
>> sv: /dev/zvol/rdsk/avs/bitmap_2 - -
>>
>> The 'sv' device driver is the AVS "Storage Volume" driver, the means
>> in which AVS is interposed on SNDR replica, or II snapshot volumes.
>> Is the same as the following:
>>
>> # svadm
>> /dev/zvol/rdsk/avs/primary_2
>> /dev/zvol/rdsk/avs/bitmap_2
>>
>
> -bash-3.00$ /usr/sbin/svadm
> /dev/md/rdsk/d20
> /dev/rdsk/c1t1d0s7
> /dev/md/rdsk/d50
> /dev/rdsk/c1t1d0s6
>>
>> Use of the 'svadm' utility is no longer required, due to a 'feature'
>> called 'auto-SV'. 'Auto-SV' records are tagged with 'dsvol:'
>>
>> 7e). dsvol: /dev/zvol/rdsk/avs/primary_2 - sndr
>> dsvol: /dev/zvol/rdsk/avs/bitmap_2 - sndr
>>
>> Internal value equal to what volumes are 'SV' enabled. As shown above
>> these two volumes are 'SV' enabled for 'sndr'. If II was used for
>> snapshots, then this value will be listed for '"ii". If configured to
>> replicate a snapshot, or snapshot a replica, this value could also be
>> "sndr,ii", or "ii,sndr".
>>
>> 8). kstat -m sndr
>>
>> This should work is SNDR is enabled.
>>
>> 9). For those interested in looking at the Solaris Kernel MDB macros
>> for SNDR (rdc - its driver name)
>>
>> # echo "::rdc_uinfo -v" | mdb -k
>> ADDR FLAG STATE
>> ffffff072943a000 0000000000000a02 logging async
>>
>> primary: nws-bur-24-204 file: /dev/zvol/rdsk/avs/primary_2
>> bitmap: /dev/zvol/rdsk/avs/bitmap_2 netbuf:
>> 0xffffff072943a000
>> secondary: nws-bur-24-206 file: /dev/zvol/rdsk/avs/primary_2
>> bitmap: /dev/zvol/rdsk/avs/bitmap_2 netbuf:
>> 0xffffff072943a0d0
>> sflags: 0 bflags: 0 mflags: 0
>> index: 0 sync_pos: 0 vsize: 62914560
>> setid: 4 bits set: 983040 autosync: 0
>> maxqfbas: 16384 maxqitems: 4096
>> netconfig: 0
>> group: directIO:
>> diskqueue: diskqsize: 0
>> rdc_k_info: 0xffffff04e84b6000
>>
>>
>> 10). Finally the 'dsstat' data
>>
>> # dsstat -m sndr
>> name t s pct role kps tps svt
>> k/avs/primary_2 S L 100.00 net 0 0 0
>> sk/avs/bitmap_2 bmp 0 0 0
>>
>>
> Still no output
> -bash-3.00$ /usr/sbin/dsstat -m sndr
>
>>
>> - Jim
>>
>>
>>> For some reason, kstat -m sndr on the secondary does not output the
>>> configuration.
>>>
>>> Karl
>>>
>>> On 01/23/09, *Jim Dunham * <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>> Karl,
>>>>
>>>>> Thanks for taking the time to reply. I downloaded and compiled
>>>>> AVS from
>>>>> http://www.opensolaris.org/os/project/nws/
>>>>>
>>>>> I have previously installed AVS 4.0 and have seen dsstat
>>>>> (sndradm also)
>>>>> display nothing when the secondary is rebooted.
>>>>>
>>>>> I guess my next step will be to live upgrade the boxes to sxce
>>>>> b105 and
>>>>> see if the problem persists. I really wanted to avoid deploying
>>>>> sxce
>>>>> into production. I don't mean that to be a slight on opensolaris
>>>>> or
>>>> AVS.
>>>>>
>>>>> If the secondary is rebooted, do I need to run any commands before
>>>>> running dsstat in order to see the configuration?
>>>>
>>>> Please take a look at /var/adm/message and /var/adm/ds.log. There
>>>> has got to be some error messages and warnings.
>>>>
>>>> Jim
>>>>
>>>>>
>>>>>
>>>>> Karl
>>>>>
>>>>> Jim Dunham wrote:
>>>>>> Karl,
>>>>>>
>>>>>>> I have started testing openAVS again on Solaris 10 but this time
>>>> on u6.
>>>>>>>
>>>>>>> I rebooted the secondary and noticed that dsstat no longer
>>>>>>> displays
>>>>>>> anything.
>>>>>>>
>>>>>>> I'm wondering if this is a known bug and it's fixed on a
>>>>>>> specific
>>>>>>> opensolaris build.
>>>>>>
>>>>>> You seem to be a little confused on what software you are using.
>>>>>>
>>>>>> Solaris 10u6 or any update version of S10, requires AVS 4.0.
>>>>>> AVS 4.0
>>>>>> is an unbundled product that is purchased from Sun, including
>>>>>> Right-To-Use licensing. The software can all be obtained if you
>>>>>> signup
>>>>>> for the Try and Buy program.
>>>>>> http://www.sun.com/tryandbuy/specialoffers.jsp
>>>>>>
>>>>>> Various downloads of OpenSolaris
>>>>>> (http://www.opensolaris.org/os/downloads/)
>>>> <http://www.opensolaris.org/os/downloads/%29>, come with AVS
>>>> bundled.
>>>>>> Starting with OpenSolaris-2008.11, AVS is no longer avalable on
>>>>>> the
>>>>>> Live-CD, but is available as the follow four IPS packages:
>>>>>> SUNWscm,
>>>>>> SUNWspsv, SUNWrdc, SUNWii. The specific order of downloading the
>>>>>> software is required, as their is an IPS dependency defect,
>>>>>> that as of
>>>>>> the note, is unresolved:
>>>>>> http://defect.opensolaris.org/bz/show_bug.cgi?id=5115
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>>
>>>>>>> Thanks
>>>>>>> Karl
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> CONFIDENTIALITY NOTICE: This communication (including all
>>>>>>> attachments) is
>>>>>>> confidential and is intended for the use of the named
>>>>>>> addressee(s)
>>>>>>> only and
>>>>>>> may contain information that is private, confidential,
>>>> privileged, and
>>>>>>> exempt from disclosure under law. All rights to privilege are
>>>> expressly
>>>>>>> claimed and reserved and are not waived. Any use,
>>>>>>> dissemination,
>>>>>>> distribution, copying or disclosure of this message and any
>>>>>>> attachments, in
>>>>>>> whole or in part, by anyone other than the intended
>>>>>>> recipient(s) is
>>>>>>> strictly
>>>>>>> prohibited. If you have received this communication in error,
>>>>>>> please
>>>>>>> notify
>>>>>>> the sender immediately, delete this communication from all data
>>>> storage
>>>>>>> devices and destroy all hard copies.
>>>>>>> _______________________________________________
>>>>>>> storage-discuss mailing list
>>>>>>> [email protected]
>>>> <mailto:[email protected]>
>>>>>>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> CONFIDENTIALITY NOTICE: This communication (including all
>>>> attachments) is
>>>>> confidential and is intended for the use of the named addressee(s)
>>>> only and
>>>>> may contain information that is private, confidential,
>>>>> privileged, and
>>>>> exempt from disclosure under law. All rights to privilege are
>>>> expressly
>>>>> claimed and reserved and are not waived. Any use, dissemination,
>>>>> distribution, copying or disclosure of this message and any
>>>> attachments, in
>>>>> whole or in part, by anyone other than the intended recipient(s)
>>>>> is
>>>> strictly
>>>>> prohibited. If you have received this communication in error,
>>>> please notify
>>>>> the sender immediately, delete this communication from all data
>>>>> storage
>>>>> devices and destroy all hard copies.
>>>>> _______________________________________________
>>>>> storage-discuss mailing list
>>>>> [email protected]
>>>> <mailto:[email protected]>
>>>>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>>>>
>>>> Jim Dunham
>>>> Engineering Manager
>>>> Storage Platform Software Group
>>>> Sun Microsystems, Inc.
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> <
>>> dsstat
>>> .primary
>>> ><dsstat.secondary>_______________________________________________
>>> storage-discuss mailing list
>>> [email protected] <mailto:[email protected]
>>> >
>>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>>
>> Jim Dunham
>> Engineering Manager
>> Storage Platform Software Group
>> Sun Microsystems, Inc.
>>
>>
>
>
>
> CONFIDENTIALITY NOTICE: This communication (including all
> attachments) is
> confidential and is intended for the use of the named addressee(s)
> only and
> may contain information that is private, confidential, privileged, and
> exempt from disclosure under law. All rights to privilege are
> expressly
> claimed and reserved and are not waived. Any use, dissemination,
> distribution, copying or disclosure of this message and any
> attachments, in
> whole or in part, by anyone other than the intended recipient(s) is
> strictly
> prohibited. If you have received this communication in error,
> please notify
> the sender immediately, delete this communication from all data
> storage
> devices and destroy all hard copies.
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss