Replies: 4 comments 5 replies
-
| 
         Thanks, I can see there is information about it on the containerlab website  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         I was able to start the container image with netlab. It takes quite some time for the container to be ready: FAILED - RETRYING: [r1 -> localhost]: Execute local ssh command to check vptx readiness (9 retries left).
FAILED - RETRYING: [r2 -> localhost]: Execute local ssh command to check vptx readiness (9 retries left).but eventually it works, until the initialisation.... [...]
TASK [Wait for et-0/0/0 interface] ***************************************************************************************************************************************************
included: /home/sa/code/quick-netlab-lab/netlab/netsim/ansible/tasks/readiness-check/vptx.yml for r2
TASK [Wait for et-0/0/0 to appear] ***************************************************************************************************************************************************
fatal: [r2]: FAILED! => changed=false
  msg: Could not open socket to clab-ml_4-r2:830
PLAY RECAP ***************************************************************************************************************************************************************************
r2                         : ok=9    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0
Error executing ansible-playbook /home/sa/code/quick-netlab-lab/netlab/netsim/ansible/initial-config.ansible -l r2:
  Command '['ansible-playbook', '/home/sa/code/quick-netlab-lab/netlab/netsim/ansible/initial-config.ansible', '-l', 'r2']' returned non-zero exit status 2.
[FATAL]   Executing Ansible playbook /home/sa/code/quick-netlab-lab/netlab/netsim/ansible/initial-config.ansible failedA quick AI chat to understand how the ansible playbook interact with junos pointed me to  And then it worked! ╰─❯ netlab initial -l r2
[WARNING]: Could not match supplied host pattern, ignoring: unprovisioned
PLAY [Deploy initial device configuration] *******************************************************************************************************************************************
TASK [Set variables that cannot be set with VARS] ************************************************************************************************************************************
ok: [r2]
TASK [Find device readiness script] **************************************************************************************************************************************************
ok: [r2]
TASK [Wait for device to become ready] ***********************************************************************************************************************************************
included: /home/sa/code/quick-netlab-lab/netlab/netsim/ansible/tasks/readiness-check/vptx-clab.yml for r2
TASK [Wait for SSH server] ***********************************************************************************************************************************************************
included: /home/sa/code/quick-netlab-lab/netlab/netsim/ansible/tasks/readiness-check/vm-clab-ssh-check.yml for r2
TASK [Check if 'sshpass' is installed] ***********************************************************************************************************************************************
ok: [r2 -> localhost]
TASK [Check for 'timeout' command] ***************************************************************************************************************************************************
ok: [r2 -> localhost]
TASK [Execute local ssh command to check vptx readiness] *****************************************************************************************************************************
ok: [r2 -> localhost]
TASK [Confirm r2 SSH server works] ***************************************************************************************************************************************************
ok: [r2] =>
  msg: Node r2 is ready.
TASK [Wait for et-0/0/0 interface] ***************************************************************************************************************************************************
included: /home/sa/code/quick-netlab-lab/netlab/netsim/ansible/tasks/readiness-check/vptx.yml for r2
TASK [Wait for et-0/0/0 to appear] ***************************************************************************************************************************************************
ok: [r2]
TASK [Normalize config on bridge-like devices] ***************************************************************************************************************************************
included: /home/sa/code/netsim-main-lab/venv/lib/python3.11/site-packages/netsim/ansible/tasks/deploy-module.yml for r2
[...]
PLAY RECAP ***************************************************************************************************************************************************************************
r2                         : ok=31   changed=2    unreachable=0    failed=0    skipped=17   rescued=0    ignored=0 | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         The only "visible" difference between cJunosEVO and vJunosEVO (the one we call vPTX) is the fact that it's shipped as container image, so you don't have to build a vrnetlab image. Since the functionality is the same between c- and v- imho it's not worth the effort, at least in my opinion. However, if you feel it could be useful for you, you can submit a PR for using it :)  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         [duplicate of #2503]  | 
  
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I just noticed Juniper/HPE made cJunosEvolved available through their vjunos-lab web page.
https://www.juniper.net/us/en/dm/vjunos-labs.html
I was wondering if anyone has tried it or might have any thoughts about it, in general and in netlab context specifically.
I took a peek inside the tarball and it seems it has two VMs wrapped inside of it.
System requirement seems to be the same as for VM version - 4 vCPU and 8G RAM.
Beta Was this translation helpful? Give feedback.
All reactions