dokucama

• Create interfaces in KVM > VQFX-RE01 > They apper as emX ?
• Rebooting the vcp also reboots the VFP

The RE is used to connect to other network devices or hosts including the PFE. The initial port names are em0 to em14 but they are not used to communicate with other devices. The actual connectivity ports are xe-0/0/0 to xe-0/0/11. The port mappings of the RE are below:

em0 - management interface (fxp0)
em1 - internal link
em2 - unusable
em3 - xe-0/0/0
em4 - xe-0/0/1
em5 - xe-0/0/2
em6 - xe-0/0/3
em7 - xe-0/0/4
em8 - xe-0/0/5
em9 - xe-0/0/6
em10 - xe-0/0/7
em11 - xe-0/0/8
em12 - xe-0/0/9
em13 - xe-0/0/10
em14 - xe-0/0/11

• https://forums.juniper.net/t5/Ethernet-Switching/vQFX10k-15-1X53-D60-on-ESXi-Installation-and-Running-with-up-to/td-p/303493
• In the linux instances, interfaces are created but ifcfg files need to be written and network restarted
• in the vqfx, reassign macs (manually).
  • xe-0/0/1 is the 1st one to be used.

---

INSTALLATION:

• Preparations: host preparation
  • Importamnt: lag interfaces don't work with virtio, therefore linux servers need to be e1000 «<

show interface | display set   | no-more # delete all interfaces except xe-0/0/0-11
commit
set system scripts commit allow-transients
set system scripts commit file set-em-mac-to-xe-ae-vQFX.slax
commit

• Install: https://codingpackets.com/blog/juniper-vqfx-vagrant-libvirt-box-install
  • step by step guide Link
  • to configure the nodes (hosts and vqfx cli): nodes-config-example.docx
• Troubleshooting: troubleshooting-vqfx-vmx-install.docx

FULL DIR CONTENTS: vqfx-vagrant-ansible.tar.gz

# this is the bootstrap script (all components in daughter pages here)
#!/bin/bash
vagrant up 
./genhost.sh
./push-slax.sh
ansible-playbook --private-key=~/.vagrant.d/insecure_private_key -u vagrant -i ini/hosts -l VQFX playbook-housekeeping.yml
ansible-playbook --private-key=~/.vagrant.d/insecure_private_key -u vagrant -i ini/hosts -l VQFX playbook-vqfx.yml

---

TODO:

1. ansible to save all running configs in files