Recovering a Disconnected Leaf Errors on ACI

[O.K.]

Hello Everyone, 

We have had some errors on the APIC GUI. Basically errors were interface errors, but the leave has been removed from the fabric and errors are persisted, and it was not possible to remove them on the GUI. 

After a quick search, I've found this and here is documented (down below "Recovering a Disconnected Leaf Using the REST API")

how you can delete them via REST API. 

I've sent the following .json request via Ansible and it worked. 

- name: Send desired req. to node 2509 - json
      ansible.builtin.aci_rest:
        hostname: "{{ inventory_hostname }}"
        username: "{{ username }}"
        password: "{{ password }}"
        validate_certs: false
        path: "/api/policymgr/mo/.json"
        method: post
        content: {"fabricRsOosPath":{"attributes": {"dn":"uni/fabric/outofsvc/rsoosPath-[topology/pod-5/paths-2509/pathep-[eth1/{{int_id}}]]","status":"deleted"}}}
      loop: "{{ range(1,53) | list }}"
      loop_control:
        loop_var: int_id

So my question here is, we have the error types F1299 and F1209, which are from different classes but the leaves doesn't exist anymore. When I try to delete them with the same method (with the correct class of course), nothing happens. Does anyone have any idea?

For example an F1299 looks like:

uni/fabric/nodecfgcont/node-2509/rsnodePolGroup-[uni/fabric/funcprof/lenodepgrp-ALL]/source-[uni/fabric/leprof-ALL/leaves-ALL-typ-range]

Fault delegate: Switch profile configuration has not been deployed on node 2509 because: Node Not Leaf For Fabric Policies
Config
configuration-failed

and I have used the following play:

- name: Send desired req.
      ansible.builtin.aci_rest:
        hostname: "{{ inventory_hostname }}"
        username: "{{ username }}"
        password: "{{ password }}"
        validate_certs: false
        path: "/api/mo/.json"
        method: post
        content: {"fabricCreatedBy":{"attributes": {"dn":"uni/fabric/nodecfgcont/node-2509/rsnodePolGroup-[uni/fabric/funcprof/lenodepgrp-ALL]/source-[uni/fabric/leprof-ALL/leaves-ALL-typ-range]","status":"deleted"}}}

Thanks!

Regards.

[AshSe]

---

So my question here is, we have the error types F1299 and F1209, which are from different classes but the leaves doesn't exist anymore. When I try to delete them with the same method (with the correct class of course), nothing happens. Does anyone have any idea?

---

Sorry your question is not clear. Can you just brief your question again?

PFB, a detailed explanation of both the fault types:

Error Code F1299: Description: This error code generally indicates a fault related to the fabric node. It could be due to a variety of reasons such as connectivity issues, configuration errors, or hardware problems. Common Causes: Connectivity issues between APIC and fabric nodes. Misconfiguration in the fabric settings. Hardware failures or issues in the fabric nodes. Troubleshooting Steps: Check Connectivity: Ensure that the APIC can communicate with all fabric nodes. Verify the physical and logical connections. Review Configuration: Check the configuration settings on the APIC and fabric nodes to ensure they are correct and consistent. Inspect Hardware: Look for any hardware issues or alerts on the fabric nodes. Replace or repair any faulty hardware components. Logs and Documentation: Review the APIC logs and Cisco documentation for more detailed information on the specific fault and recommended actions.

Error Code F1209: Description: This error code typically indicates a fault related to the APIC itself. It could be due to software issues, configuration errors, or resource constraints. Common Causes: Software bugs or issues in the APIC firmware. Misconfiguration in the APIC settings. Resource constraints such as CPU, memory, or storage limitations. Troubleshooting Steps: Update Firmware: Ensure that the APIC is running the latest firmware version. Apply any available patches or updates. Review Configuration: Check the APIC configuration settings for any errors or inconsistencies. Monitor Resources: Monitor the APIC's resource usage (CPU, memory, storage) to identify any constraints or bottlenecks. Logs and Documentation: Review the APIC logs and Cisco documentation for more detailed information on the specific fault and recommended actions.

[O.K.]

Hello @AshSe ,
Thank you for your reply!

Basically, my question is how to get rid of these error messages? I can't delete them from the APIC GUI or via API, because the nodes are deleted (decommissioned) from the fabric and doesn't exist anymore.  

[AshSe]

Hello @O.K.  

To address the F1299 and F1209 error messages in Cisco APIC when the nodes have already been decommissioned and no longer exist in the fabric, you can follow these steps:

1. Clear Faults via CLI: Sometimes, clearing the faults directly from the APIC CLI can help. You can use the following commands to clear the faults:

This will list the faults. To clear them, you can use:

2. Use the REST API to Clear Faults: If you prefer using the API, you can send a DELETE request to the fault instance. Here’s an example using curl:

Replace <APIC_IP> with the IP address of your APIC and admin:password with your APIC credentials.

3. Check for Residual Configuration: Ensure there are no residual configurations or references to the decommissioned nodes. Sometimes, stale configurations can cause persistent faults. You can check for any remaining references using the following:

 

If you find any references to the decommissioned nodes, you can delete them using:

4. APIC Reboot: As a last resort, if the faults persist and you have confirmed that there are no residual configurations, you might consider rebooting the APIC controllers. This can sometimes clear out stale faults.

Note: Rebooting the APIC controllers should be done during a maintenance window as it will temporarily disrupt the management plane.

[njgpeck]

Can you post the code of the curl command? The screenshot gets cut off. 

Thanks!

[kinemasterpro]

It sounds like you're looking for the complete curl command. If you can share the context of what you're trying to achieve, I might be able to help. In the meantime, if you're editing video content with KineMaster, remember to keep your workflow efficient—consider using screen recordings to capture commands or outputs as you work through code. This way, you can refer back to them easily while editing! source website