Configure CX Cloud Agent

[joaobraga]

My client was configuring the CX Cloud Agent on the VM and a screen appeared to configure the K3S Cluster. This is the first time I've seen this, does anyone have any idea how to proceed? Would it be better to go with the default configuration option?

[vkukatla]

Hi @joaobraga ,

If your network does not include any devices within the 172.16.x.x subnet, you can leave the custom subnet field blank and proceed by clicking “Continue.”

[pavelkedron]

Hello @vkukatla why it is there? What it means? I do not see anything about it in documentation....

[vkukatla]

Based on the CX Cloud agent VM IP address you provided in Initial IP configuration screen, the screen shows that the VM is utilizing the 172.16.x.x subnet for the internal Kubernetes network for internal communication within the VM.
Additionally, the screenshot clearly indicates that if this subnet overlaps with or is part of your organization’s or domain’s network, you will need to provide an alternative subnet to configure Kubernetes for internal communication within the VM.

[pavelkedron]

is it possible provide us with up to date documentation?

[jofrumki]

Hello @pavelkedron 

The documentation is being updated as we speak and will be available from the following link.

https://www.cisco.com/c/en/us/support/docs/cx/cx-cloud/cx222210-cx-cloud-agent-overview-v2-4.html

[pavelkedron]

Hello @jofrumki it has been two weeks and nothing is written in documentaion about K3S Cluster.

It is really strange that Cisco impelement something new and there are no information available on Web about it, especially since it is a part of installation process.

Still waiting to have more info about it.

Regards,

Pavel

[jofrumki]

Hello @pavelkedron 
Thank you for reaching out, I've asked the responsible team for an update. While we are waiting for this, are there any doubts about the requirement or purpose of this configuration? We want to ensure this process is not stressful in anyway.

Regards

[pavelkedron]

Hello  

It would be great to know purpose of this cluster or feature.

I am not sure if it can somehow interrupt integration process of CX Agent with DNAC, because right now, our customer is trying

To connect CX Agent version 2.4 with DNAC and it is still failing, but communication is allowed.

Thank you,

Regards,

Pavel

[jofrumki]

Hi @pavelkedron 

The best solution if issues arise with DNAC integration is to open a case with the CX Cloud/Agent Support team. The case creation can be done directly from CX Cloud itself.

As for the purpose of the feature to allow customers to customize the Kubernetes subnets is to prevent an overlap with existing devices/subnets in the customer's network that could pose issues with reachability to those same devices/subnets from the CX Agent. 

Thanks