Problems for setting up Cache Node [MCC]

NOC Certto 0 Reputation points
2025-02-18T19:22:20.3433333+00:00

I followed the Microsoft Connected Cache for ISPs documentation for setting up MCC in a Ubuntu 22.04 LTS server (twice, 'cause I reinstalled everything, but no success).

Everything went fine, I see that there is content inside the cache folders, the command iotedge list results in a positive output (MCC, edgeAgent and edgeHub up and running). BGP peering with my router is up too, successfully imported the announced prefix into BIRD's routing table.

However, it seems it has no connection/communication with Azure Portal. The Cache Node status stuck in "Never Phoned Home". There is no Healthy/Unhealthy Nodes in monitoring. The Cache Node reports that it has never received a route, although BIRD learned the routes (and it is reachable).

As I've already said, I tried to reinstall completely, also deleted and created the Cache Node again. But there was no success.

Any help would be appreciated!

Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. NOC Certto 0 Reputation points
    2025-03-10T11:53:03.67+00:00

    It turns out, the problem solved without much interaction.

    The 1st installation, I waited for around 1-2 days and the status never changed. But in the 2nd time, a couple of hours were enough. Traffic is flowing correctly and it is listing a healthy node in Azure. Although, Bird shows the networks announced via BGP as unreachable, it's actually reaching and deploying the cache content to our selected customers.

    The documentation is indeed a little bit uninformative and lacks some in-depth troubleshooting methods. Anyways, everything is fine right now.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.