Rename Erases Configs on vMX routers
Posted: Wed Oct 21, 2020 7:38 pm
Hello,
I renamed my lab from Test to MPLS Core, and the routers all booted up minus their configs.
I see that a new directory looks to have been created as below, likely as a part of the renaming process:
root@eve-ng:/opt/unetlab/tmp# ls -al
total 280
drwxrwsr-x 4 root unl 4096 Oct 21 13:35 .
drwxr-xr-x 12 root root 4096 Oct 14 10:53 ..
drwxrwsr-x 3 root unl 4096 Oct 14 15:26 0
drwxrwsr-x 3 root unl 4096 Oct 21 13:35 1
-rw-rw-r-- 1 root unl 267264 Oct 14 14:24 index
root@eve-ng:/opt/unetlab/tmp#
There haven't been any other labs on this server, and the subdirectories are identical (7 vCp/vFP pairs for 14 separate nodes/subdirectories) so i believe that the original lab is there with a copy. I don't mind too much, it's just early stages, but the nodes in directory '0' don't seem to be accessible. At the very least I would like to clean it up, since it's a waste of space, at the most I would like to access it again so that I don't have to configure them with the base config all over again.
If this is expected behaviour, that would be all good, but again, the original directory for the router images is wasting space and is inaccessible by the application.
directory lists:
root@eve-ng:/opt/unetlab/tmp/0/e26d3faf-3290-4900-b9c3-c363beaf16aa# ls -al
total 64
drwxrwsr-x 16 root unl 4096 Oct 16 14:54 .
drwxrwsr-x 3 root unl 4096 Oct 14 15:26 ..
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 1
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 10
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 11
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 12
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 13
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 14
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 2
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 3
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 4
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 5
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 6
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 7
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 8
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 9
root@eve-ng:/opt/unetlab/tmp/0/e26d3faf-3290-4900-b9c3-c363beaf16aa# cd ../../1/e26d3faf-3290-4900-b9c3-c363beaf16aa/
root@eve-ng:/opt/unetlab/tmp/1/e26d3faf-3290-4900-b9c3-c363beaf16aa# ls -al
total 64
drwxrwsr-x 16 root unl 4096 Oct 21 13:35 .
drwxrwsr-x 3 root unl 4096 Oct 21 13:35 ..
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 1
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 10
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 11
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 12
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 13
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 14
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 2
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 3
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 4
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 5
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 6
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 7
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 8
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 9
root@eve-ng:/opt/unetlab/tmp/1/e26d3faf-3290-4900-b9c3-c363beaf16aa#
Any ideas?
edit: this is a brand new bare metal install, completed last week.
Thanks,
Ian.
I renamed my lab from Test to MPLS Core, and the routers all booted up minus their configs.
I see that a new directory looks to have been created as below, likely as a part of the renaming process:
root@eve-ng:/opt/unetlab/tmp# ls -al
total 280
drwxrwsr-x 4 root unl 4096 Oct 21 13:35 .
drwxr-xr-x 12 root root 4096 Oct 14 10:53 ..
drwxrwsr-x 3 root unl 4096 Oct 14 15:26 0
drwxrwsr-x 3 root unl 4096 Oct 21 13:35 1
-rw-rw-r-- 1 root unl 267264 Oct 14 14:24 index
root@eve-ng:/opt/unetlab/tmp#
There haven't been any other labs on this server, and the subdirectories are identical (7 vCp/vFP pairs for 14 separate nodes/subdirectories) so i believe that the original lab is there with a copy. I don't mind too much, it's just early stages, but the nodes in directory '0' don't seem to be accessible. At the very least I would like to clean it up, since it's a waste of space, at the most I would like to access it again so that I don't have to configure them with the base config all over again.
If this is expected behaviour, that would be all good, but again, the original directory for the router images is wasting space and is inaccessible by the application.
directory lists:
root@eve-ng:/opt/unetlab/tmp/0/e26d3faf-3290-4900-b9c3-c363beaf16aa# ls -al
total 64
drwxrwsr-x 16 root unl 4096 Oct 16 14:54 .
drwxrwsr-x 3 root unl 4096 Oct 14 15:26 ..
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 1
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 10
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 11
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 12
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 13
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 14
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 2
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 3
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 4
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 5
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 6
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 7
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 8
drwxrwsr-x 2 root unl 4096 Oct 21 13:33 9
root@eve-ng:/opt/unetlab/tmp/0/e26d3faf-3290-4900-b9c3-c363beaf16aa# cd ../../1/e26d3faf-3290-4900-b9c3-c363beaf16aa/
root@eve-ng:/opt/unetlab/tmp/1/e26d3faf-3290-4900-b9c3-c363beaf16aa# ls -al
total 64
drwxrwsr-x 16 root unl 4096 Oct 21 13:35 .
drwxrwsr-x 3 root unl 4096 Oct 21 13:35 ..
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 1
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 10
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 11
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 12
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 13
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 14
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 2
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 3
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 4
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 5
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 6
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 7
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 8
drwxrwsr-x 2 root unl 4096 Oct 21 15:02 9
root@eve-ng:/opt/unetlab/tmp/1/e26d3faf-3290-4900-b9c3-c363beaf16aa#
Any ideas?
edit: this is a brand new bare metal install, completed last week.
Thanks,
Ian.