UNSOLVED

GarethR1

updated

13 years ago

G

GarethR1

1 Rookie

•

7 Posts

0

1366

October 21st, 2013 08:00

VNX DHSM Connection Logging

Hi,

I'm got a set of VNX with CTA and ATMOS.

We use the DHSM connection facility of VNX to tier data to ATMOS via CTA. When defining a connection between VNX and CTA it is established per file system. The command indicate a log file is produced.

Two questions.

How do I read that log file - where is it?

How can I find out what files are being requested via DHSM connection as the CTA logging only indicates the ATMOS file ID?

I'm not after the DHSM server log file. I want the CLIENT logs.

Regards,

Gareth

  • umichklewis

    4 Apprentice

    •

    1190 Posts

    586

    0

    Posted October 21st, 2013 12:00

    The DHSM logs are written into the ./etc of the filesystem being migrated.  dhsm.log will have the data you're after.  Basically, you're looking at things like this:

    122125131*: SET_OFFLINE: 1.10000007e.8163e07.52c7c2d6, pe_id: NONE, offline_path

    : \\fma.home.org\fmroot\HPF\1MK88CH3AUO4Qe3L31RUCIQ426PG416NTNFGRV089IGQH7TIQ2S2N ... Sat Mar 10 09:04:42 2012

    122125132*: SET_OFFLINE: 1.10000007e.8164283.52c7c834, pe_id: NONE, offline_path

    : \\fma.home.org\fmroot\HPF\7SNL7PSR5UVSOe2VQ128LIH1PQSG416NTNFGKR0942IQI1N71BOCN ... Sat Mar 10 09:04:42 2012

    122125133*: SET_OFFLINE: 1.10000007e.8163f7e.52c7c491, pe_id: NONE, offline_path

    : \\fma.home.org\fmroot\HPF\4VHP3LQP8FGM6e8S0MLVJ99TGAQG416NTNFGKU059OCB998M1LD6V ... Sat Mar 10 09:04:42 2012

    122125134*: SET_OFFLINE: 1.10000007e.8163eb3.52c7c3a4, pe_id: NONE, offline_path

    : \\fma.home.org\fmroot\HPF\4EKCU02AI9TR7eAP2DC2HJKVNNCG416NTNFG8I0B7C57P240P8222 ... Sat Mar 10 09:04:42 2012

    You can find more information in the VNX guide, Using Filemover on VNX.

    One thing to keep in mind with using ATMOS on the backend, is that CTA communicates with ATMOS via the REST API and requests objects, not files.  If you want to see files being written to ATMOS, you'll only see filenames on the NAS side, in the dhsm logs.

    Let us know if that helps!

    Karl