Skip to content

Troubleshooting

Check the issues below for common problems and suggested ways of handling them.

Activities not Collected by the Activity Monitor

If activities are not collected by the Activity Monitor, we need to track the status of the components, starting from the data mover to the Activity Monitor service.

Log in to the data mover with your administrative user, and follow the suggestions below:

  • Verify the CEPA facility status on the data mover.

    Use the command:

    server_cepp <data mover> -service –status Output: server_2 : CEPP Started

  • If the CEPA isn't listed as "Started":

    Start it with the following command:

    server_cepp <data mover> -service –start

  • Display information about the CEPA service.

    Use the following command:

    server_2 : CEPP Started server_cepp <data mover> -pool -info Output: server_2 : pool_name = sepapool server_required = yes access_checks_ignored = 0 req_timeout = 5000 ms retry_timeout = 25000 ms pre_events = post_events =
    OpenFileRead,CreateFile,FileWrite,FileRead,CreateDir,DeleteFile,DeleteDir,CloseModified,RenameFile,enameDir,SetAclFile,SetAclDir,SetSecFile,SetSecDir post_err_events = CEPP Servers: ip = [ip address of the CEE server], state = ONLINE, status = ONLINE

  • Make sure the post events correspond to the definitions described in the prerequisites section.

  • If the state and status are not both ONLINE:

    • There might be a problem with the connection to the CEE service, or with the connection between the CEE service and the Activity Monitor service.

    • The CEPA facility is delicate to communication errors and in some cases the CEE does not recover from a communication failure.

  • Make sure all the prerequisites were set.

  • Make sure the CEE service is running with a domain user who is an administrator on the CEE service server.

  • Make sure the CEE service and the physical data mover CIFS server are joined to the same active directory domain.

  • Make sure the CEPA ip address listed in the output of the command above matches the IP address of the server running the CEE service.

  • Make sure there is no firewall between the data mover and the server running the CEE service.

  • Make sure the windows firewall is off on the server running the CEE service.

  • Try restarting the services.

    • Stop the CEPA facility with the following command:

    Server_cepp <data mover> -service -stop

    • Stop the EMC CEE service on the CEE server and the Activity Monitor service..

    • Start the CEPA facility.

    • Start the EMC CEE service, wait for 60 seconds.

    • Start the Activity Monitor service.

    • Wait for 60 seconds, and issue the command server_cepp <data mover> -pool –info again.

State and Status ONLINE, but no Events are Shown

If the state and status are both ONLINE, but no events are shown, check the event counters, in the data mover, using the following command:

server_cepp <data mover> -pool –stats Output: server_2 : pool_name = pool1 Event Name Requests Min(us) Max(us) Average(us) OpenFileWrite 2 659 758 709 CloseModified 2 604 635 620 Total Requests = 4 Min(us) = 604 Max(us) = 758 Average(us) = 664

Look at the count of the different events.

Issue the command a few more times and verify that the counters increase.

Those counters represent the total number of requests for all the CIFS server in all the virtual data movers. If the counters do not increase, it might be that no users are working on the CIFS server at the moment.

Counters Increase but No Events are Collected

If the counters increase, but no events are collected:

  1. Check the statistics log file of the Activity Monitor to verify whether events are received by the Activity Monitor.

  2. If no events are received by the Activity Monitor, validate the Application configuration:

    • Make sure the CIFS server name is properly configured in the Application filer name field.

      This value must be the actual name of the CIFS server name, and not the FQDN or one of the aliases.

    • If the CIFS server has aliases defined to it (validate that in the EMC management), make sure these aliases are defined under the aliases in the Application configuration.