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.
Hello everyone.I have got the same error and I am not able to access the vManage's GUI interface. So, I guess the neo4j database corrupted would be the cause.vManage# request nms configuration-db diagnosticsNMS configuration databaseChecking cluster ...
Hi everyone.I have one vManage (20.7.1) in standalone mode in my eve-ng. Yesterday I had an eletric power disruption at home and my vManage seems to have died. I can telnet to 8443 from my desktop. But I've tried to wget through vMware console and I ...
Hi everyoneI have tried to apply a template by vManage to a cEdge 8300 (20.6 version) but I received the following messsage. However, I could realize that the config has been applied. What could I do? Detach the cedge from vManage and repeat the acti...
Hi @ericgar I've got the admin tech as you mentioned. I am attaching the file if you (or someone else) could help me.If I could restore the templates from the old vManage, it will be very helpfull.Thanks in advance,
The key point here is about I don't have the root password to do. Sadly, it couldn't be used even analyze the log error like below cause I have only the admin credentials.
Hi @bigevilbeard, thanks for replying and so sorry about my delayed response.To make a comparison, I build up a new vManage using the same eve-ng image and I saw that the new one has the same log status regarding 'auplink'.Do know how can I fix the '...
Hi my friend.Coud you help me out?I have one vManage (20.7.1) in standalone mode in my eve-ng. Yesterday I had an eletric power disruption at home and my vManage seems to have died. I can telnet to 8443 from my desktop. But I've tried to wget throug...
Hi @bigevilbeard I have collected the logs as mentioned and catched some error messages as below. The entire file was attached as well.I am turned if you could have a light on this.Much appreciate that.Output:=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2023.08...
