CA Client Automation

Filtering Network Adapters from CORA Registration (Slow Engine Collect of Computer Registrations)

  • 1.  Filtering Network Adapters from CORA Registration (Slow Engine Collect of Computer Registrations)

    Posted 07-22-2016 11:01 AM

    Client Automation Administrators,

     

    Check out TEC1945924 on the CA Support site...

    Filtering Network Adapters from CORA Registration (Slow Engine Collect of Computer Registrations)

     

    CORA is the Common Registration API, and is the interface used by Client Automation to share computer registration data with other CA products (i.e. CA Service Desk Manager).  Even if you're not integrating Client Automation with another CA product, the engines processing the collect task are still registering computers (and network adapters) with CORA during the processing of registration messages.

     

    When CORA performs a registration of a network adapter that is not unique, i.e. the Microsoft Tunnel Adapter "00:00:00:00:00:00:00:E0", it forces CORA to compare the registration details with all existing records reporting the same MAC address.  Depending on the number of network adapters already registered with this address, this comparison will delay the CORA registration, resulting in a delay of the engine to process registration messages or in the worst case, it may cause the engine process to crash.

     

    Check out the technical document, which provides queries to identify which network adapters (MAC Addresses) are being duplicated in your environment, and instructions on how to setup a filter for the engine, to prevent this problem and keep computer registrations (and Collect Tasks) running smoothly.

     

    -Brian Fontana, CA Support