Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi all I have been trying to license the C93180YC-FX running 9.3.7 for the entire morning and I cannot make it to register to the on-Prem SSM. I am very familiar with IOS-XE smart licensing but Nexus seems to be a different beast. I have an on-prem S...
Hello all I appreciate this question has been raised before and it seems we don't have a solution yet. So I would like to see if anyone has found a solution. I have been tasked to "figure out" how to perform a (2 member) cat9300 stack upgrade with no...
HiIt seems that I am hitting a bug with pushing a very generic template for a C1111-8PLTEEAW* that is connected to WAN via wired interface Gi0/0/1. cEdge is running IOS-XE SDWAN version 16.12.3.0.3752. All controllers are running 19.2.2. The router h...
HiI am trying to attach a feature template to n an C1111-8PLTEEAWE running 16.12.03 IOS-XE SDWAN. Controllers are running version 19.2.2. I manually configured the cisco router and it has sucessfully built control connections to the controllers. Now,...
Hi allWe are experiencing the same issue after upgrading from 16.12.3a to 17.3.3 on 9300-24T + 9300-24P stacks. We are using on-prem CSSM and everything worked fine prior to the update. I've tried some of the suggestion from this thread with no luck....
HiI found a workaround and the template finally attached sucessfully. I did not upgrade however. What is going on is essentially is vManage trying to delete the default config from cEdge and router is just not liking it. What you need to do is to inc...
Hi ManuelNo, I am still looking ways to come around this. I will post a solution as soon as it's available. I have another C1111-4PLTEEA router running the same version 16.12.3.0.3752, however this one is connecting via LTE and had no issues attachin...
The issue was resolved. Resolution: be careful about values you put into the input fields when filling in the config template. There was a mistake in the values in one of the variables. vManage is doing some data validation on these config templates...
Just to follow up on the issue.I've managed to solve the problem with some help and it turned out to be a NAT problem.Communication from vManage --> vBond and vSmart --> vBond must be NAT-ed in a way to change the source IP of the vManage/vSmart into...
