When I try to delete a certain community from the list in "Communities" I get the following error (XXX stands for the filename):
Could not delete the Community XML file: XXX.xml
I have to cancel the window, otherwise I cannot quit it. What is strange to me: I can open this community, although something is worng with it... Any ideas? I'm using Cisco Network Assistant Version 5.7 (6).
I have the same problem and I'm on 5.8(5). The prduct was not connecting to one of my 3750's so I want to delete the community and do a new scan. I also rebooted my system to ensure no hidden second instance.
When I try to delete the community I get the same response as Leonardo.
Re: Cisco Network Assistant: error deleting community
i ran into this error as well. the CNA appears to be pulling a community list from the online profile somewhere as opposed to reading local config files. I am still chasing down how to prevent CNA from reloading previously deleted communities, but in the meantime here's how to fix your problem.
navigate to C:\Users\<User>\.networkassistant\communities. copy any of the XML files in this directory (you might even be able to use a totally blank file, i haven't tried that) and create a new xml file to match the community name you are having trouble deleting.
the problem comes when the CNA application attempts to delete a configuration file that doesn't exist in the communities directory. giving it a file to delete gets you past the failure you've posted.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...