Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post, you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message.

Symptoms-  
All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received.

Affected CM releases
6.1.5 and later.

Resolution

In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps:

  1. Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management. The Certificate List window displays.
  2. You can use the Find controls in order to filter the certificate.
  3. Click on the ipsec.pem file and check the serial number of the certificate.
  4. Log on to CUCM OS Administration page of each node of the cluster. Choose Security > Certificate Management. The Certificate List window displays.
  5. You can use the Find controls in order to filter the certificate.
  6. Click on ipsec-trust.pem file with the file name of hostname of the publisher and check the serial number of the certificate.
  7. Certificate Serial Number should be same on all the nodes of the cluster. If Serial Number of any node is mismatched, complete these steps.
    1. Log on to CUCM OS Admin page of affected node.
    2. Choose Security > Certificate Management. The Certificate List window displays.
    3. You can use the Find controls in order to filter the certificate.
    4. Click on ipsec.pem file and download that certificate.
    5. Find the existing ipsec-trust with the filename of the hostname of the publisher,click on the file name and Delete.
    6. Upload the downloaded ipsec.pem file with the caption ipsec-trust.
    7. Restart the DRF Master Agent(MA)/DRF Local Agent (LA).
     
References.

      Comments

      Post a Comment

      Popular posts from this blog

      Understanding code yellow

      -
      Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
      Read more