RME config mgmt is set up to keep config for the last 30 days and the last 7 revisions. I just find out there're configs from as early as 2004 in /var/adm/CSCOpx/files/archive/config/###. I assume ### is the dbid of a device. There're as many as 224 (gasp!) running.cfg/slot1_running.cfg files in one directory. I think it's been suggested that it's not a good idea to delete CiscoWorks files from the UNIX CLI out right. But how could I otherwise clean up these stale configs "properly"? I have tried tuning down the level of config retention from 30 days to 15 days and 7 revs to 5 revs, respectively. That only seemed to make RME consume disk space faster, without deleting the real old configs.
Firs time I ran the Delete Change History (set to 31 days), it took two to three hours and MSIE returned a "this page cannot be displayed". I ran it again and got "None of the records in the database matches your filter criteria." within 10 mins. Does it mean it's safe for me to manually delete cfg files older than 30 days in /var/adm/CSCOpx/files/archive/config/###/?
Can I trigger a config purge right away by starting ConfigPurge under Server Config -> Admin -> Process Management -> Start Process? Crikey! Tried it anyway, it didn't do squat.
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 ...