• Troubleshooting



    Information related to import operation problems

    Before you contact your service provider, use either Unisphere or the Unisphere CLI to access information about jobs that failed and alert information and check the target storage system's log files.

    Jobs and Alerts information

    Use Unisphere to get information about Jobs that fail. Under Events, select Jobs. Use Jobs to view information on all jobs, including those jobs that are active and those jobs that are complete or failed. To quickly determine the number of active jobs (those jobs that are queued or running) and view job progress, use the Jobs icon in the status bar. To view detailed information about the job, specifically the individual tasks included in the job and the status of these tasks, select the Details icon. If a task fails, select View Error for more information.

    To get information about Jobs that fail, use the Unisphere CLI. To find the job that failed, review the Jobs output. The following is an example:

    C:>uemcli -d -u Local/admin -p /sys/task/job show

                          74:   ID               = N-66
          Type             = Replication Service
          Title            = Create VNX remote system connection
          State            = Failed

    Once you have the Job ID, you can retrieve more detailed information about the failure. The following is an example:

    C:>uemcli -d -u Local/admin -p /sys/task/job/step -jobId N-66 show -detail

                          1:    Title                        = Register VNX remote system connection
          Status                       = Failed
          Execution result code        = 105906574
          Execution result description = An error occured while trying to communicate with the remote VNX system. The credentials used might be incorrect or there may be a network issue while connecting to the remote VNX system. (Error Code:0x650018e)
          Rollback result code         = 4106
          Rollback result description  =  Task was rolled back and marked as failed. This is because some tasks failed or SP rebooted during task execution. (Error Code:0x100a)

    Alerts provide you with information about the source of an event, the symptoms and cause, and actions that you can take to resolve it. Any actions that are taken to resolve an alert must be performed directly on the system on which the alert was reported.

    In Unisphere under Events, select Alerts. In addition to appearing on the Alerts page, each alert generates a pop-up alert bubble in Unisphere. The alert bubble provides information about the alert and may also contain a link to a help topic on how to resolve the problem.

    Use the Unisphere CLI commands /event/log show and /event/alert/hist show to display additional event attributes that provide more detailed event reports than what appear in Unisphere. For example:

    uemcli -d -u Local/joe -p MyPassword456! /event/log show - fromTime “2009-11-09 00:00:00.000” –to “2009-11-09 23:59:59.999”

    uemcli -d -u Local/joe -p MyPassword456! /event/alert/hist show

    For detailed information about Jobs and Alerts, refer to either the Unisphere Online Help or the Unisphere Command Line Interface User Guide.

    Log information

    One of the most useful logs for reviewing errors that are related to setting the file import connection or creating an import session, or any other file import task, is /EMC/CEM/log/cemtracer_migration.log.

    VNX system with two Control Stations

    For a VNX system with two Control Stations, ensure that the following exists before you set up a file-based import:

    • The home directory of a user with Administrator role exists on the primary Control Station of the VNX. The home directory is used when you configure the import connection.
    • When you configure other components for an import operation, the primary Control Station of the VNX that is used must be the same Control Station as in the previous bullet item.

    You can retrieve information about the primary Control Station of the VNX system using the VNX command line interface (CLI). The following CLI output is an example that includes SPA, SPB, and the primary Control Station.

    # naviseccli -User Local/joe -Password MyPassword456! -Scope 0 -h domain -list

                        Node: APM00153042305
    IP Address: (Master)
    Name: hop21130
    Port: 80
    Secure Port: 443
    IP Address:
    Name: hop21131
    Port: 80
    Secure Port: 443
    IP Address:
    Name: Unity_CS0_03
    Port: 80
    Secure Port: 443

    If the primary Control Station of the VNX does not have a user home directory, you can manually fail over the Control Station. The following is an example set up by logging on the primary Control Station through SSH.

    # /nas/sbin/cs_standby -failover

                        The system will reboot, do you wish to continue? [yes or no]: yes
    Failing over from Primary Control Station...

    For more information about this situation and how to resolve it, see Knowledge Based Article 000489181.