Deployment of vMX with Dual REs and Multiple FPCs using EVE-NG

In this post, I will guide you through the process of deploying vMX with dual REs and multiple FPCs using EVE-NG.

To begin, you will need to download the vMX KVM bundle from the Juniper website. For this lab, we will be using Junos 21.4.

  1. Extract the vMX bundle:
    2. mkdir /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re0
mkdir /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re1
mkdir /opt/unetlab/addons/qemu/vmxvfp-21.4R3-S1.5-fpc0
mkdir /opt/unetlab/addons/qemu/vmxvfp-21.4R3-S1.5-fpc1
  2. Copy the images to their respective directories:
    3. ## RE0
cp /root/vmx/images/junos-vmx-x86-64-21.4R3-S1.5.qcow2 /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re0/virtioa.qcow2
cp /root/vmx/images/vmxhdd.img /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re0/virtiob.qcow2
cp /root/vmx/images/metadata-usb-re0.img /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re0/virtioc.qcow2

## RE1
cp /root/vmx/images/junos-vmx-x86-64-21.4R3-S1.5.qcow2 /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re1/virtioa.qcow2
cp /root/vmx/images/vmxhdd.img /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re1/virtiob.qcow2
cp /root/vmx/images/metadata-usb-re1.img /opt/unetlab/addons/qemu/vmxvcp-21.4R3-S1.5-re1/virtioc.qcow2

## FPC0
cp /root/vmx/images/vFPC-20220714.img /opt/unetlab/addons/qemu/vmxvfp-21.4R3-S1.5-fpc0/virtioa.qcow2
cp /root/vmx/images/metadata-usb-fpc0.img /opt/unetlab/addons/qemu/vmxvfp-21.4R3-S1.5-fpc0/virtiob.qcow2

## FPC1
cp /root/vmx/images/vFPC-20220714.img /opt/unetlab/addons/qemu/vmxvfp-21.4R3-S1.5-fpc1/virtioa.qcow2
cp /root/vmx/images/metadata-usb-fpc1.img /opt/unetlab/addons/qemu/vmxvfp-21.4R3-S1.5-fpc1/virtiob.qcow2
  3. Fix permissions:
    4. /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
  4. Add 4 new nodes in EVE-NG:
    • VCP-RE0
    • VCP-RE1
    • VFP-FPC0
    • VFP-FPC1
  5. Connect the em1 interfaces for all nodes to a bridge and start the nodes.
  6. After the REs boot up, you should now see that both REs are online and in Master/Backup state.
  7. Both FPCs should also be online.

While building your labs, you encountered a problem with interface connectivity. It appears that there might be a bug or an issue with the interface mapping between vFPC and EVE-NG. Specifically, when attempting to use ge-0/0/0 on the vMX device, you found that you had to connect ge-0/0/1 on EVE-NG instead.

Currently, you are investigating the problem in order to identify the root cause and find a solution. Nevertheless, you can continue building your lab and connecting interfaces without experiencing any other difficulties.

Comments

Post a Comment

Popular posts from this blog

Juniper EVPN-VXLAN Data Center Interconnection

Image
In this post, I will walk you through the deployment process of EVPN-VXLAN Data Center Interconnection. Data Centers are interconnected via WAN links and BGP has been enabled as both the Overlay and Underlay routing protocols. Each device within the IP fabric is assigned a unique Autonomous System Number (ASN) The underlay routing configuration ensures seamless reachability between all devices in the underlay the IP fabric. Overlay routing with VXLANs are reachable between VTEP across underlay IP fabric. EVPN-VXLAN configuration is established between DC1 and DC2 data centers, and Extended VLANs are configured to span between the two data centers, enhancing the scope and flexibility of the network. Here is the topology that I have designed and implemented: DC1-SW1 set interfaces ge-0/0/0 description TO-DC1-R1 set interfaces ge-0/0/0 unit 0 family inet address 192.168.253.2/30 set interfaces ge-0/0/1 description TO-DC1-SW2 set interfaces ge-0/0/1 unit 0 family inet ...
Read more

BNG Redundancy for DHCP Subscribers on Juniper MX

Image
Recently, I encountered a challenge while assisting a customer who sought a solution for deploying a redundant DHCP service to accommodate DHCP subscribers on two MX routers. Unfortunately, Juniper website currently lacks resources or examples specifically addressing the deployment of a redundant DHCP service for DHCP subscribers. Therefore, I took the initiative to set up a lab environment comprising two vMX routers functioning as BNG routers (BNG-1 and BNG-2), along with an additional MX router operating as the DHCP server. Here is the topology that I have designed and implemented:   BNG-1 set system host-name BNG-1 set system services subscriber-management enable set system services subscriber-management redundancy interface xe-0/0/3.1492 virtual-inet-address 172.16.0.129 set system services subscriber-management redundancy interface xe-0/0/4.1493 virtual-inet-address 172.16.0.1 set system services subscriber-management redundancy protocol vrrp set system servic...
Read more