I’m excited to finally have the opportunity to play with Juniper’s vMX! Since it was announced last year I’ve been eagerly waiting for release – a couple of client projects already have passed by where the vMX would have been a perfect fit. vMX already won an award earlier this year at Interop Tokyo 2015!
In this post I’ll be giving a bit of background on the vMX architecture and licensing, and then go on to walk through a lab based configuration of vMX.
The vMX is a virtual MX Series Router that is optimized to run as software on x86 servers. Like other MX routers, it runs Junos, and Trio has been compiled for x86! Yes, that means the sophisticated L2, L2.5 and L3 forwarding features we are used to on the MX are present on the vMX.
Architecture
vMX can be installed on server hardware of your choice, so long as it is x86 based and running Linux (although I’m sure a version to run on vmware won’t be too far away).
vMX itself actually consists of two separate VMs – a virtual forwarding plane (VFP) running the vTrio, and a virtual control plane (VCP) running Junos.
The Linux virtualisation solution KVM is what Juniper are using to spin up the virtual instances of the control and forwarding planes, and multiple instances of vMX can be run on the same hardware. To see Juniper using Linux and KVM is no surprise as this is what we are used to on Juniper’s other products such as the QFX.
The VMs are managed by a simple orchestration script which is used to create, stop and start the vMX instances. A simple configuration file defines parameters such as memory and vCPUs to allocate to the VCP and VFP.
A couple of Linux bridges are created by the orchestration script. Clearly VCP and VFP need to be able to communicate directly so an “internal” bridge is automatically created for each vMX instance to enable this communication. An “external” bridge is also created, this is used to enable the management interface on the Linux Physical host to be used for the virtual management interfaces on the VCP and VFP.
For data interfaces, there are a couple of techniques available for packet I/O depending on the required vMX throughput –
- Paravirtualisation using KVMs virtio drivers
- PCI passthrough using single root I/O virtualisation (SR-IOV), enabling packets to bypass the hypervisor and therefore increase I/O.
Juniper recommend virtio or SR-IOV up to 3Gbps, and SR-IOV over 3Gbps (using a minimum of 2 x 10GE interfaces).
Which you will choose will ultimately depend on your use case for the vMX.
Licensing
Now this is what I really like about vMX! Licensing is based on a combination of throughput and features, and the lowest available throughput license is 100Mbps! Yes – you don’t need to be shifting multi-Gigabits of traffic to start with vMX. You can start small and pay-as-you-grow with vMX.
Below 1Gbps there are only 3 options – 100Mbps, 250Mbps and 500Mbps. Full scale features are included! List price on the 100Mbps option is a very reasonable $750.
At 1Gbps and above, licences are a combination of features (Base, Advance, and Premium) and full duplex throughput (1G, 5G, 10G, 40G)
- Base – IP routing with 32,000 routes in the forwarding table. Basic Layer 2 functionality, Layer 2 bridging and switching.
- Advance – Features in the BASE application package IP routing with routes up to platform scale in the forwarding table. IP and MPLS switching for unicast and multicast applications. Layer 2 features include Layer 2 VPN, VPLS, EVPN, and Layer 2 Circuit
VXLAN. - Premium – Features in the BASE and ADVANCE application packages. Layer 3 VPN for IP and multicast
Setting up vMX on Ubuntu
Now I’m going to walk through setting up vMX on Ubuntu 14.04 LTS server (Juniper’s recommended flavour of Linux for vMX). Just for fun this is actually running as a nested Vmware VM on my Macbook Pro – fine for a lab, but don’t try this in production! 🙂 I have allocated 8GB RAM, 4 vCPUs and two vNICs to the Ubuntu VM. Also the VM is enabled to support hypervisor applications within the VM.
At this point Ubuntu Server has been freshly installed, and the option to install virtualisation was selected during setup.
First things first, let’s update all packages, install the prerequsite packages and restart the system
mdinham@ubuntu:~$ sudo apt-get upgrade <snip> mdinham@ubuntu:~$ sudo apt-get install bridge-utils qemu-kvm libvirt-bin python python-netifaces vnc4server libyaml-dev python-yaml numactl libparted0-dev libpciaccess-dev libnuma-dev libyajl-dev libxml2-dev libglib2.0-dev libnl-dev python-pip python-dev libxml2-dev libxslt-dev <snip> mdinham@ubuntu:~$ sudo reboot
Configuring vMX
As this is a lab based build, I will be using virtio for the virtual NIC. There are two options on the VFP – a “Lite” version PFE for labs and performance version for normal operation.
Note: Ubuntu 14.04 provides libvirt 1.2.2 which works for VFP lite version. However for the VFP performance version you must upgrade to libvirt 1.2.8.
Let’s extract the vMX application bundle and get going!
mdinham@ubuntu:~$ tar xzf vmx-14.1R5.4-1.tgz mdinham@ubuntu:~$ cd vmx-14.1R5.4-1/ mdinham@ubuntu:~/vmx-14.1R5.4-1$ ls config drivers env images scripts vmx.sh
First of all we need to setup the vmx config file, this is done by editing config/vmx.conf
First of all I set an instance name for vmx, and set the correct vmx images. I’m using vPFE-lite.
---
#Configuration on the host side - management interface, VM images etc.
HOST:
identifier : vmx1 # Maximum 4 characters
host-management-interface : eth0
routing-engine-image : "/home/mdinham/vmx-14.1R5.4-1/images/jinstall64-vmx-14.1R5.4-domestic.img"
routing-engine-hdd : "/home/mdinham/vmx-14.1R5.4-1/images/vmxhdd.img"
forwarding-engine-image : "/home/mdinham/vmx-14.1R5.4-1/images/vPFE-lite-20150707.img"
Now the parameters the control plane and forwarding plane.
I’ve allocated 1 vCPU to vRE and 3 vCPU to vPFE. 1GB RAM to the RE and 6GB to the forwarding plane, as per the defaults for 14.1
UPDATE: Feb 2016
For vMX on 15.1, allocate 1 vCPU to vRE and 3 vCPU to vPFE. 2GB RAM to the RE and 8GB to the forwarding plane.
I have also tried vMX with 2GB allocated to the vPFE and the forwarding plane loaded, which could be fine for lab purposes. I’d expect 1GB to be the minimum on the vRE. 3 x vCPU seems to be the minimum for the vPFE.
Note that device-type is set to “virtio” for the interfaces.
---
#External bridge configuration
BRIDGES:
- type : external
name : br-ext # Max 10 characters
---
#vRE VM parameters
CONTROL_PLANE:
vcpus : 1
memory-mb : 2048
console_port: 8601
interfaces :
- type : static
ipaddr : 10.102.144.94
macaddr : "0A:00:DD:C0:DE:0E"
---
#vPFE VM parameters
FORWARDING_PLANE:
memory-mb : 6144
vcpus : 3
console_port: 8602
device-type : virtio
interfaces :
- type : static
ipaddr : 10.102.144.98
macaddr : "0A:00:DD:C0:DE:10"
---
#Interfaces
JUNOS_DEVICES:
- interface : ge-0/0/0
mac-address : "02:06:0A:0E:FF:F0"
description : "ge-0/0/0 interface"
I will only be using one interface in this lab, but up to 10 can be configured. For SR-IOV, things are done slightly differently – see this vMX doc for reference.
I now need to deploy the vMX instance using the orchestration script. “-lv” provides verbose logging. My vMX instance will be created by the script and automatically started.
mdinham@ubuntu:~/vmx-14.1R5.4-1$ sudo ./vmx.sh -lv --install ================================================== Welcome to VMX ================================================== Date..............................................07/18/15 13:19:03 VMX Identifier....................................vmx1 Config file......................................./home/mdinham/vmx-14.1R5.4-1/config/vmx.conf Build Directory.................................../home/mdinham/vmx-14.1R5.4-1/build/vmx1 Environment file................................../home/mdinham/vmx-14.1R5.4-1/env/ubuntu_virtio.env Junos Device Type.................................virtio Initialize scripts................................[OK] Copy images to build directory....................[OK] ================================================== VMX Environment Setup Completed ================================================== ================================================== VMX Install & Start ================================================== Linux distribution................................ubuntu Check GRUB........................................[Disabled] Installation status of qemu-kvm...................[OK] Installation status of libvirt-bin................[OK] Installation status of bridge-utils...............[OK] Installation status of python.....................[OK] Installation status of libyaml-dev................[OK] Installation status of python-yaml................[OK] Installation status of numactl....................[OK] Installation status of libnuma-dev................[OK] Installation status of libparted0-dev.............[OK] Installation status of libpciaccess-dev...........[OK] Installation status of libyajl-dev................[OK] Installation status of libxml2-dev................[OK] Installation status of libglib2.0-dev.............[OK] Installation status of libnl-dev..................[OK] Check Kernel Version..............................[Disabled] Check Qemu Version................................[Disabled] Check libvirt Version.............................[Disabled] Check virsh connectivity..........................[OK] IXGBE Enabled.....................................[Disabled] ================================================== Pre-Install Checks Completed ================================================== Check for VM vcp-vmx1.............................[Not Running] Check for VM vfp-vmx1.............................[Not Running] Cleanup VM states.................................[OK] Check if bridge br-ext exists.....................[No] Cleanup VM bridge br-ext..........................[OK] Cleanup VM bridge br-int-vmx1.....................[OK] ================================================== VMX Stop Completed ================================================== Check VCP image...................................[OK] Check VFP image...................................[OK] VMX Model.........................................Lite Check VCP Config image............................[OK] Check management interface........................[OK] Setup huge pages to 8192..........................[OK] Attempt to kill libvirt...........................[OK] Attempt to start libvirt..........................[OK] Sleep 2 secs......................................[OK] Check libvirt support for hugepages...............[OK] ================================================== System Setup Completed ================================================== Get Management Address of eth0....................[OK] Generate libvirt files............................[OK] Sleep 2 secs......................................[OK] Find configured management interface..............eth0 Find existing management gateway..................eth0 Check if eth0 is already enslaved to br-ext.......[No] Gateway interface needs change....................[Yes] Create br-ext.....................................[OK] Get Management Gateway............................192.168.100.254 Flush eth0........................................[OK] Start br-ext......................................[OK] Bind eth0 to br-ext...............................[OK] Get Management MAC................................00:0c:29:76:a8:15 Assign Management MAC 00:0c:29:76:a8:15...........[OK] Add default gw 192.168.100.254....................[OK] Create br-int-vmx1................................[OK] Start br-int-vmx1.................................[OK] Check and start default bridge....................[OK] Define vcp-vmx1...................................[OK] Define vfp-vmx1...................................[OK] Wait 2 secs.......................................[OK] Start vcp-vmx1....................................[OK] Start vfp-vmx1....................................[OK] Wait 2 secs.......................................[OK] ================================================== VMX Bringup Completed ================================================== Check if br-ext is created........................[Created] Check if br-int-vmx1 is created...................[Created] Check if VM vcp-vmx1 is running...................[Running] Check if VM vfp-vmx1 is running...................[Running] Check if tap interface vcp_ext-vmx1 exists........[OK] Check if tap interface vcp_int-vmx1 exists........[OK] Check if tap interface vfp_ext-vmx1 exists........[OK] Check if tap interface vfp_int-vmx1 exists........[OK] ================================================== VMX Status Verification Completed. ================================================== Log file.......................................... /home/mdinham/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1437221943.log ================================================== Thankyou for using VMX ==================================================
Connecting to the console port on the VMs
We can now connect to the vMX control plane! This is done using the vmx.sh script again.
Specify vcp (control plane – Junos) or vcf (vPFE) and the instance name.
mdinham@ubuntu:~/vmx-14.1R5.4-1$ ./vmx.sh --console vcp vmx1 -- Login Console Port For vcp-vmx1 - 8601 Press Ctrl-] to exit anytime -- Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Amnesiac (ttyd0) login:
After a while, the FPC and interfaces will come online
root> show interfaces terse | match ge-0/0/0 ge-0/0/0 up up root> show chassis fpc Temp CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt DRAM (MB) Heap Buffer 0 Online Absent 100 0 512 14 0
I’ll go ahead and add an IP address to ge-0/0/0. Note: if I was using the management interface I could configure interface FXP0 also now. Remember FXP0 will be bridged to the host eth0 adapter (or an adapter you specify).
root# set interfaces ge-0/0/0.0 family inet address 192.168.100.5/24
Can I ping anything?
root> ping 192.168.100.5 PING 192.168.100.5 (192.168.100.5): 56 data bytes 64 bytes from 192.168.100.5: icmp_seq=0 ttl=64 time=0.059 ms ^C --- 192.168.100.5 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.059/0.059/0.059/0.000 ms root> ping 192.168.100.254 PING 192.168.100.254 (192.168.100.254): 56 data bytes ^C --- 192.168.100.254 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss
OK, so I can ping the interface but nothing else on the host. As I’m using virtio I need to create a device binding between the host physical NIC and the vMX interface.
Creating a virtio binding
This is done in the config file config/vmx-junosdev.conf.
virtio bindings are flexible and can be used to map multiple vMX instances to the same physical host interface, or to connect vMX instances together.
A new Linux bridge will be created between host interface eth1 and ge-0/0/0 on vmx1.
##############################################################
#
# vmx-junos-dev.conf
# - Config file for junos device bindings.
# - Uses YAML syntax.
# - Leave a space after ":" to specify the parameter value.
# - For physical NIC, set the 'type' as 'host_dev'
# - For junos devices, set the 'type' as 'junos_dev' and
# set the mandatory parameter 'vm-name' to the name of
# the vPFE where the device exists
# - For bridge devices, set the 'type' as 'bridge_dev'
#
##############################################################
interfaces :
- link_name : vmx_link
endpoint_1 :
- type : junos_dev
vm_name : vmx1
dev_name : ge-0/0/0
endpoint_2 :
- type : host_dev
dev_name : eth1
If eth1 is not already up on the Linux host, bring it up
sudo ifconfig eth1 up
Again the orchestration script vmx.sh is used to create the device bindings
mdinham@ubuntu:~/vmx-14.1R5.4-1$ sudo ./vmx.sh --bind-dev Bind Link vmx_link(ge-0.0.0-vmx1, eth1)...........[OK]
And we can see a new bridge has been created called “vmx_link” as referenced in the bindings configuration file
mdinham@ubuntu:~/vmx-14.1R5.4-1$ brctl show
bridge name bridge id STP enabled interfaces
br-ext 8000.000c2976a815 yes br-ext-nic
eth0
vcp_ext-vmx1
vfp_ext-vmx1
br-int-vmx1 8000.52540050c859 yes br-int-vmx1-nic
vcp_int-vmx1
vfp_int-vmx1
virbr0 8000.fe060a0efff1 yes ge-0.0.1-vmx1
ge-0.0.2-vmx1
ge-0.0.3-vmx1
vmx_link 8000.000c2976a81f no eth1
ge-0.0.0-vmx1
Now to retry that ping!
mdinham@ubuntu:~/vmx-14.1R5.4-1$ ./vmx.sh --console vcp vmx1 -- Login Console Port For vcp-vmx1 - 8601 Press Ctrl-] to exit anytime -- Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. root> ping 192.168.100.254 PING 192.168.100.254 (192.168.100.254): 56 data bytes 64 bytes from 192.168.100.254: icmp_seq=0 ttl=64 time=4.951 ms 64 bytes from 192.168.100.254: icmp_seq=1 ttl=64 time=2.081 ms ^C --- 192.168.100.254 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 2.081/3.516/4.951/1.435 ms
Success! At this point I’ve a working vMX with an interface mapped to a NIC on the Ubuntu host. What happens if I turn on OSPF and LDP?
root> show ospf neighbor Address Interface State ID Pri Dead 192.168.100.254 ge-0/0/0.0 Full 10.0.0.2 1 37 192.168.100.1 ge-0/0/0.0 Full 10.0.0.1 128 39 root> show ldp neighbor Address Interface Label space ID Hold time 192.168.100.254 ge-0/0/0.0 10.0.0.2:0 13
Excellent, now the fun can really begin, but I’ll save that for another time!
vPFE
One last thing – what does the VFP look like?
mdinham@ubuntu:~/vmx-14.1R5.4-1$ sudo ./vmx.sh --console vfp vmx1 -- Login Console Port For vfp-vmx1 - 8602 Press Ctrl-] to exit anytime -- Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Wind River Linux 6.0.0.12 localhost console localhost login: root Password: Last login: Sat Jul 18 12:20:49 UTC 2015 on console
The riot process is where all the magic happens!
top - 12:52:55 up 33 min, 1 user, load average: 0.38, 0.74, 0.62 Tasks: 102 total, 1 running, 101 sleeping, 0 stopped, 0 zombie Cpu(s): 0.5%us, 2.1%sy, 0.0%ni, 96.8%id, 0.0%wa, 0.0%hi, 0.6%si, 0.0%st Mem: 5824060k total, 4454308k used, 1369752k free, 12184k buffers Swap: 0k total, 0k used, 0k free, 44552k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1019 root 20 0 36.6g 37m 10m S 12 0.7 4:25.04 riot <snip>
Further reference
I hope you enjoyed this vMX post! For further reference on any of the above material please see the Juniper Release Notes for vMX
Bloody good post Matt, keep them coming!
Just what I was looking for. Thanks 🙂
Great article. Very well written and thorough!
Thanks for the post! I have played with vMX in Vbox (version R1.10) and found that QoS features do not work, can it be related to license absence?
Btw is there any demo or trial license ?
With no licence it can be trialled for 30 days with 1Mbps max throughput. I’ve not played with QoS features yet, but I believe supported QoS features are as per Intel DPDK QoS feature set (6 queues, 3 priorities). Thanks for reading the post 🙂
Really good article. I’d be interested in more stuff.
i try to install the vmx
when i run sudo ./vmx.sh -lv –install
i get this error
Traceback (most recent call last):
File “/root/vmx-14.1R5.4-1/scripts/common/vmx_configure.py”, line 592, in
if key.keys()[0] == “FORWARDING_PLANE”:
AttributeError: ‘NoneType’ object has no attribute ‘keys’
Log file……………………………………/root/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1440999853.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
are u know how to fix it t?
Hi David, thanks for reading the post. If you go to http://forums.juniper.net/t5/vMX/bd-p/vMX and start a new post, attach a copy of the log file and your vmx.conf, I’ll take a look for you.
Hello, thanks for the post. I completed setting up the vMX router..how do I access the router via cli or ssh. I don’t see how to login to the router instance.
Hi, are you using KVM or Vmware?
HI mdinham
thanks for your replay ,
but i try to found the problem
again great post keep the good work!!!
Thank you for this article. It`s very helpful.
Hi Mdinham,
Thanks a lot for your post it is very useful and I see for so many other.
I’m getting the following error during the installation process:
System Setup Completed
==================================================
.
.
.
Wait 2 secs…………………………………[OK]
Start vcp-vmx1………………………………[OK]
Start vfp-vmx1………………………………[Failed]
error: Failed to start domain vfp-vmx1
error: internal error: Process exited prior to exec: libvirt: error : internal error: Host kernel is not aware of NUMA.
Log file……………………………………/var/tmp/vmx-14.1R5.4-1/build/ vmx1/logs/vmx_1444746040.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
root@admin1-OptiPlex-790:/var/tmp/vmx-14.1R5.4-1#
Something that has to do with NUMA. Any idea what to do?
Hi, thanks for reading the post 🙂
Are you running 64-bit image of Ubuntu? Which version?
Thanks
Thank you for the quick reply 🙂
I found the following:
root@admin1-OptiPlex-790:/var/tmp/vmx-14.1R5.4-1/config# uname -a
Linux admin1-OptiPlex-790 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:10:15 UTC 2015 i686 i686 i686 GNU/Linux
Codename: trusty
root@admin1-OptiPlex-790:/var/tmp/vmx-14.1R5.4-1/config# lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Stepping: 7
CPU MHz: 3294.718
BogoMIPS: 6186.27
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
I think the problem is a 32-bit version of Ubuntu is installed?
Indeed. It’s a 32-bit. I guess I should install 64-bit and try again.
Hi mdinham, how are you?
After reinstalling Ubuntu to a 64-bit, I’m getting a new error as following:
Start br-int-vmx1……………………………[OK]
Check and start default bridge………………..[OK]
Define vcp-vmx1……………………………..[OK]
Define vfp-vmx1……………………………..[OK]
Wait 2 secs…………………………………[OK]
Start vcp-vmx1………………………………[OK]
Start vfp-vmx1………………………………[Failed]
error: Failed to start domain vfp-vmx1
error: internal error: early end of file from monitor: possible problem:
file_ram_alloc: can’t mmap RAM pages: Cannot allocate memory
Log file……………………………………/var/tmp/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1444915261.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
Any idea?
I’m good thanks 🙂 Can you tell me how much memory you have in the host? Also in vmx.conf, the memory settings for the VCP and VFP?
Sure 🙂 as following:
root@vMX:/var/tmp/vmx-14.1R5.4-1# cat /proc/meminfo
MemTotal: 5988208 kB
MemFree: 3782224 kB
MemAvailable: 4668600 kB
Buffers: 32176 kB
Cached: 1039780 kB
SwapCached: 364 kB
Active: 1000496 kB
Inactive: 1029008 kB
Active(anon): 909364 kB
Inactive(anon): 87140 kB
Active(file): 91132 kB
Inactive(file): 941868 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 6167548 kB
SwapFree: 6167152 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 957244 kB
Mapped: 89908 kB
Shmem: 38956 kB
Slab: 103004 kB
SReclaimable: 44620 kB
SUnreclaim: 58384 kB
KernelStack: 4304 kB
PageTables: 18068 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 9161652 kB
Committed_AS: 3127348 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 364832 kB
VmallocChunk: 34359299076 kB
HardwareCorrupted: 0 kB
AnonHugePages: 86016 kB
CmaTotal: 0 kB
CmaFree: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 101840 kB
DirectMap2M: 6068224 kB
root@vMX:/var/tmp/vmx-14.1R5.4-1#
———————————————————————————–
—
#vRE VM parameters
CONTROL_PLANE:
vcpus : 1
memory-mb : 2048
console_port: 8601
interfaces :
– type : static
ipaddr : 10.102.144.94
macaddr : “0A:00:DD:C0:DE:0E”
—
#vPFE VM parameters
FORWARDING_PLANE:
memory-mb : 6144
vcpus : 3
console_port: 8602
device-type : virtio
Thanks 🙂
It looks like your host has MemTotal: 5988208 kB – so around 6GB memory.
But we have 2GB allocated to vRE and 6GB to vPFE which won’t fit 🙂
Try changing vRE memory-mb to 1024 and vPFE to 2048.
6144 is the minimum officially supported for vPFE, but I have found that 2048 works ok for lab purposes. Good luck!
Indeed it make sense 🙂
I’ll try to increase the hard memory on this server and if impossible, re-allocate the memory as you’ve suggested.
I will update soon, thanks a lot again!
Hi mdinham 🙂
I’ve finally managed to install the vMX after increasing the memory on the host server. I made one vMX instance and it seems fine, however is it true that if the host server is reboot, the instance is gone and all it’s interfaces and bridges?
Should I run the installation script from the beginning?
Hi – glad you got it working 🙂 When you start vMX (./vmx.sh –start) it will create it’s own internal/external bridges for you, but not any of the vmx<->host_dev bridges. Just run ./vmx.sh –bind-check and then ./vmx.sh –bind-dev and you’ll be all set!
Thanks a lot mdinham! 🙂
Could you please write me those exacts commands you’ve mentioned so I’ll be able to run and then my instance will be permanent and survive server reboots?
Hello,
Could you help me with the launch of the script vmx.sh.
During the “Get Management Address of eth0”, the operation failed. No IP Address configuration for eth0.
Here come the logs:
[Command] brctl show br-ext | grep eth0
can’t get info No such device.
Thanks.
Hi, thanks for reading the post 🙂 I replied to your post at http://forums.juniper.net/t5/vMX/Error-Eth0/m-p/283331
Great post, very informative, thanks!
Decided to run this with KVM nested under ESXi 6.0.0, all the above instructions work with one slight modification which is enabling hardware assisted virtualization for the KVM guest.
For anyone else looking for information on this, you can tick this option if you are using the vSphere Web Client. If you are resource-cheap like myself you can edit the VMX file for the guest and add vhv.enable = “TRUE” at the end.
Identify the guest VM ID with vim-cmd vmsvc/getallvms | grep -i then reload it with vim-cmd vmsvc/reload
Power up the VM and off you go!
Hi,
Thanks for a great article!
I’m trying to figure out how to configure the interfaces by using ‘vmx-junosdev.conf’.
I’m able to create 1 link between two of my vMXes but what if I want to create more with more routers? I will for example want to create a full mesh with 4 vMXes, however, I’m not quite sure how to accomplish this :/.
I guess I need to use the bridge somehow, do I just add it?
Thankful for any help 🙂
Hi thanks for reading it – if you follow the same process and linking two up, just use a different name for the bridge and specify the ge on the vMX and you should be ok 🙂 shout if problems!
Matt, could you do me a favor and post the following for your setups (from both blog entries re: vMX)?
1. ifconfig -a (or ip addr)
2. netstat -rn
3. brctl show
4. show interfaces terse
I think having the full picture of what the underlying OS and the vMX setup is, would be very helpful. This is something I’ve noticed across several threads/blog entries/docs that is typically missing (even if the setup should be obvious).
Thank you in advance.
Very good article. Just wanted to point out that Juniper now offers a free 60-day trial of vMX without having to be an existing customer. You still have to register for a free account but do not have to have a product serial number tied to your account…
http://www.juniper.net/us/en/dm/free-vmx-trial/
-Justin
Great, easy to follow article. Does anyone know what happens once the 60 day trial expires. Does it just stop working?
Thanks for reading it 🙂 I believe it drops to a throughout of zero
I spent most of the day trying to get it running on vmplayer and then centos 7 :o( Will try using your instructions and ubuntu tomorrow. Is there an option to install virtualisation when you install ubuntu as a VM?
Yes – it’s easy enough 🙂
That’s correct. If you have a Juniper or partner SE, they can get you other lab/demo license.
When the 60 days trial passed, the vPFE stop forwarding packets.
Could you reapply a new trial licence for another 60 days? If not, I’ll have to ask the Juniper SE and hope he’s in a good mood :I) thanks for your quick response.
I believe you would have to create a new instance of the vMX (new S/N) to reset the timer. Juniper has created a pretty easy process for SEs to generate new trial/demo/lab licenses for vMX so it should not be too difficult to get your SE to generate it.
Guys, i’m running vMX on KVM on Ubuntu on vmplayer… i’ve followed the steps above, but cannot bind eth1 to ge-0/0/0. My ‘brctl show’ output looks the same as above. Is there another step i’m missing.
If I ‘monitor traffic interface’ or tcpdump, i dont see any traffic from the host or vMX.
To whom it may concern:
I’m running vMX on KVM on Ubuntu 14.04 LTS as well ( in a vmware v9 vm running on an ESXi 5.5 host). I’ve also faithfully followed the steps above and concerning the eth1 to ge-0/0/0 link, I cannot ping out to the next hop ip on the same subnet. Pinging to the interface ip inside of the junos router works. It seems that the junos ge-0/0/0 unit 0 intf ARP requests out and the request arrives at my physical switch outside of the ESXi host. There at the physical switch the arp table is valid with ge-0/0/0 unit 0 interface mac and a reply is generated (which I see via tcpdump -i eth1 on the Ubuntu host). (Also considered the cases where eth1 and vm port group are configured for promiscuous mode.) It’s a pickle, at least to me. (I’ve also tried building my Ubuntu VM with in one case E1000 interfaces and VMXNET3 in the other. ) It seems to be an issue somewhere between the linux bridge vmx_link and the logical interface ge-0/0/0 unit 0 at the VCP???
BTW great tutorial modulo this issue.
F. Santoro.
Is there a supported confirmed/tested configuration for vMX on Ubuntu 14.04.03(?) running in a vmware VM (which vmware-vmx version (8, 9, 10???))? I am also seeing the issue:
Thanks.
At the following location:
http://forums.juniper.net/t5/vMX/taskset-failed-to-parse-CPU-list/td-p/283829
Hello,
My VMX turn on VMware image with the last version of VMware Workstation or player.
Also, you have to installed at least 8Go of memory RAM. I’m not sure but for the VFP, your cpu needs the aes-ni option.
Hi Matt, great post, I have followed exactly the same steps (I am building it on VMware fusion running on my MAC pro). and I am stuck in below thing, I would really appreciate if you can please help…
Check and start default bridge………………..[OK]
Define vcp-vmx1……………………………..[OK]
Define vfp-vmx1……………………………..[OK]
Wait 2 secs…………………………………[OK]
Start vcp-vmx1………………………………[Failed]
error: Failed to start domain vcp-vmx1
error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
Log file……………………………………/var/tmp/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1450905842.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
regards,
Fahad
Hi – thanks for reading the post. It sounds like you are missing a setting on Fusion. On the VM settings – processors – advanced – and tick the box to enable hyper visor apps within the VM. That should do it – let me know!
Good evening,
Did you install the qemu-kvm ?
Do you have enabled thé option VT on your BIOS ?
I don’t know how if your Macintosh accept the VT processus.
pls, can you send link download vmx-14.1R5.4-1 to gmail. thanks you so much.
Here you go – http://www.juniper.net/us/en/dm/free-vmx-trial/
Wow!! It resolved the issue ….Thanks alot…!!!
But now when I try to bind the interfaces using ‘sudo ./vmx.sh –bind-dev’ after making changes in
interfaces :
– link_name : vmx_link
# mtu : 1500
endpoint_1 :
– type : junos_dev
vm_name : vmx1
dev_name : ge-0/0/0
endpoint_2 :
– type : host_dev
dev_name : eth1
# – link_name : vmx_link2
# mtu : 1500
# endpoint_1 :
# – type : junos_dev
# vm_name : vmx2
# dev_name : ge-0/0/0
# endpoint_2 :
# – type : bridge_dev
# dev_name : bridge1
#
I am getting this :(….
Traceback (most recent call last):
File “/var/tmp/vmx-14.1R5.4-1/scripts/junosdev-bind/vmx-junosdev-bind.py”, line 82, in
for key in vmx_configs:
File “/usr/lib/python2.7/dist-packages/yaml/__init__.py”, line 83, in load_all
yield loader.get_data()
File “/usr/lib/python2.7/dist-packages/yaml/constructor.py”, line 33, in get_data
return self.construct_document(self.get_node())
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 27, in get_node
return self.compose_document()
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 55, in compose_document
node = self.compose_node(None, None)
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 84, in compose_node
node = self.compose_mapping_node(anchor)
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 133, in compose_mapping_node
item_value = self.compose_node(node, item_key)
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 82, in compose_node
node = self.compose_sequence_node(anchor)
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 111, in compose_sequence_node
node.value.append(self.compose_node(node, index))
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 84, in compose_node
node = self.compose_mapping_node(anchor)
File “/usr/lib/python2.7/dist-packages/yaml/composer.py”, line 127, in compose_mapping_node
while not self.check_event(MappingEndEvent):
File “/usr/lib/python2.7/dist-packages/yaml/parser.py”, line 98, in check_event
self.current_event = self.state()
File “/usr/lib/python2.7/dist-packages/yaml/parser.py”, line 428, in parse_block_mapping_key
if self.check_token(KeyToken):
File “/usr/lib/python2.7/dist-packages/yaml/scanner.py”, line 116, in check_token
self.fetch_more_tokens()
File “/usr/lib/python2.7/dist-packages/yaml/scanner.py”, line 257, in fetch_more_tokens
% ch.encode(‘utf-8’), self.get_mark())
yaml.scanner.ScannerError: while scanning for the next token
found character ‘\t’ that cannot start any token
in “/var/tmp/vmx-14.1R5.4-1/config/vmx-junosdev.conf”, line 16, column 29
Could you please help again..
Hi Matt,
When I am binding vMX interface with the host, i am getting below errors
fahad@vmx:/var/tmp/vmx-14.1R5.4-1$ sudo ./vmx.sh –bind-dev
Bind Link vmx_link(ge-0.0.0-vmx1, eth0)………..[OK]
Numa node for eth0…………………………..-1
Cores servicing numa node -1………………….
Pid of vfp-vmx1……………………………..16357
Pin vhost-16357 (PID=16360) to cores ………….taskset: failed to parse CPU list:
[Failed]
Pin vhost-16357 (PID=16359) to cores ………….taskset: failed to parse CPU list:
[Failed]
Pin vhost-16357 (PID=16358) to cores ………….taskset: failed to parse CPU list:
[Failed]
Could you please help…
Thanks in advance.
fahad
Hi Matt, , I have followed exactly the same steps (I am building it on VMware fusion running on my lenovo T420 windows 7). and I am stuck in below thing, I would really appreciate if you can please help…
error: Failed to start domain vcp-vmx1
error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
Log file……………………………………
/home/masood/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1451471712.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
Hi – thanks for reading the post. Do you mean Fusion or Workstation? It sounds like you are missing a setting on Vmware. On the VM settings – processors – look for a setting to enable hyper visor apps within the VM. Also check you have VT-x enabled in the host BIOS, and the pre-requisite packages installed (qemu-kvm, libvirt, etc). Hope that helps!
Hello,
I had the same problem before.
My computer was not compatible with VT-D technologie. Did you enable this on your BIOS ?
hello team, previous error is removed. got new error below.. need your support
Start vfp-vmx1………………………………[Failed]
error: Failed to start domain vfp-vmx1
error: internal error: early end of file from monitor: possible problem:
file_ram_alloc: can’t mmap RAM pages: Cannot allocate memory
Log file……………………………………
/home/masood/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1451507727.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
Hi, I think this one is probably a simple on to fix. How much memory have you assigned to the VFP and how much memory does your KVM host have?
Hi ,
This is really nice article . By following this. i’m successfully installed the vMX but after login the router i could not see the interface ge-0/0/0 . is their any issue ?
Thanks for reading 🙂
It takes a while for the vMX VFP to load the forwarding plane but it sounds like it might be crashing on start up.
Start vMX and as soon as VFP loads get a console up and watch it boot. See if you get a kernel panic on boot.
Hi Matt,
Great post!
I have similar issue with Jahangir, the installation finished properly (console log: http://pastebin.com/UTuwHGUJ), but interface ge-0/0/0 doesn’t show up.
I checked that VFP bootup console and it says kernel panic (console log: http://pastebin.com/Un5FvcLy).
My implementation is like this:
– VMX on top of Ubuntu Guest
– Ubuntu 14.04 Guest on top of Ubuntu Host
– Ubuntu 14.04 Host on top of Physical Server
Any idea what should I check/research?
Thanks!
Thanks for reading it! Is there any reason you are running vMX within a Ubuntu guest rather than on the main Ubuntu Host? I would double check BIOS settings, I know of one person who had this issue and found a setting “AES-N”I in BIOS that fixed his issue. What Linux kernel are you using?
Hi Matt,
I also run Openstack+Contrail demo on top of the Ubuntu Host, hence I need to create another guest to prevent VMX messing with the Openstack Contrail configuration.
The kernel used on Ubuntu Guest is version 3.19.0-25-generic. The one on Ubuntu Host is 3.13.0-40-generic.
I checked that my physical server has its Intel AES-NI feature enabled.
Does anyone came across this error, while running the install script ?
Error! CPU needs AVX extensions to run Performance mode of VFP
–log–
VMX Stop Completed
==================================================
Check VCP image……………………………..[OK]
Check VFP image……………………………..[OK]
VMX Model…………………………………..Performance
Check CPU requirements……………………….[Failed]
Error! CPU needs AVX extensions to run Performance mode of VFP
Log file……………………………………
/home/ecode/vmx-14.1R5.4-1/build/vmx1/logs/vmx_1453809453.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
ecode@ubuntu1:~/vmx-14.1R5.4-1$
What type of CPU do you have?
Hi ,
Really a useful post.
Had my vMX setup using this. Small confusion . I tried binding one of the physical interface to vMX interfaces.
labuser@ubuntu:~/vmx-14.1R5.4-1$ brctl show
bridge name bridge id STP enabled interfaces
br-ext 8000.90b11c1715a5 yes br-ext-nic
em1
vcp_ext-vmx1
vfp_ext-vmx1
br-int-vmx1 8000.525400682721 yes br-int-vmx1-nic
vcp_int-vmx1
vfp_int-vmx1
bridge1 8000.000000000000 no
virbr0 8000.000000000000 yes
vmx_link1 8000.90b11c1715a6 no em2
ge-0.0.0-vmx1
vmx_link3 8000.fe060a0efff1 no ge-0.0.1-vmx1
vmx_link4 8000.fe060a0efff2 no ge-0.0.2-vmx1
this output shows the binding has taken place. But i couldn’t contact the ip assigned to ge-0/0/0.0 from the server . What can be the reason behind this ?
Really appreciate if you could help me out.
Thanks in advance.
Hi – thanks for reading the post, can you tell me where em2 on the server connects to? If a switch, is it placed in the same VLAN as the host management interface?
Thanks for replying .
Both are connected to switches which are in VC (virtual chassis) and placed in the same vlan.
Hi, all,
after Flush eth0 i lose managment access to my VM. How can i avoid it?
Hi Matt,
I am getting “Error starting domain:internal error:process exited while connecting to monitor: file_ram_alloc:can’t mmap RAM pages: Cannot allocate memory, when i tried to run my VFP-VMX
My VCP-VMX is working fine.
VCP – 1024 MB memory
VFP – 2048 MB memory
I have ubuntu 14.04 LTS with 8GB RAM.
Thanks,
TJ
Hi 🙂
Firstly, just bear in mind that although you might be able to get VFP to run with less than the recommended memory, on 14.1 recommended VFP memory is 6GB and on 15.1 it is 8GB.
How much free memory does the Ubuntu host have when you come to start vMX? The error message is saying you don’t have enough memory to start the VFP.
Also, is your system 32-bit or 64-bit and if 64-bit are you running the 64-bit version of Ubuntu?
M.
Hi Matt,
I was able to deploy VFP with just 2048MB memory but when I boot it, it just stuck on “Please wait: booting”
I log in to the console of VFP while booting and it is also stuck on “Waiting for RE to come up”
Any ideas?
I am using 64-bit of Ubuntu.
Hi – can you start a post on the juniper.net forums and post the boot logs there? There is a forum for vMX. I will look out for the post. Thanks 🙂
Make sure you are using the English language version of Ubuntu 14.04 LTS. Juniper’s scripts seem to be incompatible with Ubuntu Systems in a language other than english. Took me quite a while to get this figured out 😉
Hello,
I’m running VMX on my Ubuntu. VCP et VFP are running (cf below).
==================================================
Welcome to VMX
==================================================
Date……………………………………….07/18/16 09:32:32
VMX Identifier………………………………vmx1
Config file…………………………………/home/alex/VMX/VMX/config/vmx.conf
Build Directory……………………………../home/alex/VMX/VMX/build/vmx1
Environment file……………………………./home/alex/VMX/VMX/env/ubuntu_virtio.env
Junos Device Type……………………………virtio
Initialize scripts…………………………..[OK]
Copy images to build directory………………..[OK]
==================================================
VMX Environment Setup Completed
==================================================
==================================================
VMX Install & Start
==================================================
Linux distribution…………………………..ubuntu
Check GRUB………………………………….[Disabled]
Installation status of qemu-kvm……………….[OK]
Installation status of libvirt-bin…………….[OK]
Installation status of bridge-utils……………[OK]
Installation status of python…………………[OK]
Installation status of libyaml-dev…………….[OK]
Installation status of python-yaml…………….[OK]
Installation status of numactl………………..[OK]
Installation status of libnuma-dev…………….[OK]
Installation status of libparted0-dev………….[OK]
Installation status of libpciaccess-dev………..[OK]
Installation status of libyajl-dev…………….[OK]
Installation status of libxml2-dev…………….[OK]
Installation status of libglib2.0-dev………….[OK]
Installation status of libnl-dev………………[OK]
Check Kernel Version…………………………[Disabled]
Check Qemu Version…………………………..[Disabled]
Check libvirt Version………………………..[Disabled]
Check virsh connectivity……………………..[OK]
IXGBE Enabled……………………………….[Disabled]
==================================================
Pre-Install Checks Completed
==================================================
Check for VM vcp-vmx1………………………..[Not Running]
Check for VM vfp-vmx1………………………..[Not Running]
Cleanup VM states……………………………[OK]
Check if bridge br-ext exists…………………[No]
Cleanup VM bridge br-ext……………………..[OK]
Cleanup VM bridge br-int-vmx1…………………[OK]
==================================================
VMX Stop Completed
==================================================
Check VCP image……………………………..[OK]
Check VFP image……………………………..[OK]
VMX Model…………………………………..Lite
Check VCP Config image……………………….[OK]
Check management interface……………………[OK]
Setup huge pages to 8192……………………..[OK]
Attempt to kill libvirt………………………[OK]
Attempt to start libvirt……………………..[OK]
Sleep 2 secs………………………………..[OK]
Check libvirt support for hugepages……………[OK]
==================================================
System Setup Completed
==================================================
Get Management Address of eth0………………..[OK]
Generate libvirt files……………………….[OK]
Sleep 2 secs………………………………..[OK]
Find configured management interface…………..eth0
Find existing management gateway………………eth0
Check if eth0 is already enslaved to br-ext…….[No]
Gateway interface needs change………………..[Yes]
Create br-ext……………………………….[OK]
Get Management Gateway……………………….192.168.136.2
Flush eth0………………………………….[OK]
Start br-ext………………………………..[OK]
Bind eth0 to br-ext………………………….[OK]
Get Management MAC…………………………..00:0c:29:fa:91:3d
Assign Management MAC 00:0c:29:fa:91:3d………..[OK]
Add default gw 192.168.136.2………………….[OK]
Create br-int-vmx1…………………………..[OK]
Start br-int-vmx1……………………………[OK]
Check and start default bridge………………..[OK]
Define vcp-vmx1……………………………..[OK]
Define vfp-vmx1……………………………..[OK]
Wait 2 secs…………………………………[OK]
Start vcp-vmx1………………………………[OK]
Start vfp-vmx1………………………………[OK]
Wait 2 secs…………………………………[OK]
==================================================
VMX Bringup Completed
==================================================
Check if br-ext is created……………………[Created]
Check if br-int-vmx1 is created……………….[Created]
Check if VM vcp-vmx1 is running……………….[Running]
Check if VM vfp-vmx1 is running……………….[Running]
Check if tap interface vcp_ext-vmx1 exists……..[OK]
Check if tap interface vcp_int-vmx1 exists……..[OK]
Check if tap interface vfp_ext-vmx1 exists……..[OK]
Check if tap interface vfp_int-vmx1 exists……..[OK]
==================================================
VMX Status Verification Completed.
==================================================
Log file……………………………………/home/alex/VMX/VMX/build/vmx1/logs/vmx_1468827152.log
==================================================
Thankyou for using VMX
==================================================
The output command of ” show chassis fpc” is :
root>
Message from syslogd@ at Jul 18 07:48:02 …
i386_junos[2870]: fpc0 SCHED: Thread 45 (TNPC CM) ran for 1610 ms without yielding
root> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis VM5641FDAA3B VMX
Midplane
Routing Engine RE-VMX
CB 0 VMX SCB
FPC 0 Virtual FPC
CPU Rev. 1.0 RIOT 123XYZ987
root> show chassis fpc
Temp CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt DRAM (MB) Heap Buffer
0 Online
Theres is en errror during the reboot of the VMX. Do you have any idea (load module problem) ?
Additional routing options:kern.module_path: /boot//kernel;/boot/modules -> /boot/modules;/modules/peertype;/modules/ifpfe_drv;/modules/ifpfe_media;/modules/dev;/modules/platform;/modules;
kld netpfe media: ifpfem_ds0 ifpfem_ds1e1 ifpfem_ds3e3 ifpfem_imaLoading the IMA Link Media Layer; Attaching to media services layer
Loading the IMA Group Media Layer; Attaching to media services layer
ifpfem_otn ifpfem_sonetLoading the SONET Media Layer; Attaching to media services layer
kld netpfe drv: if_vcp ifpfed_atm ifpfed_chmicLoading the CHMIC module
ifpfed_controller ifpfed_ds0 ifpfed_ds1e1 ifpfed_ds3e3 ifpfed_eia530 ifpfed_esp ifpfed_ethinterface ifpfed_eth.1 already present in the KLD ‘kernel’!
kldload: Unsupported file type
kldload: can’t load /modules/ifpfe_drv/ifpfed_eth.ko: Exec format error
ifpfed_irb ifpfed_lt ifpfed_ml_cmn ifpfed_ml_ha ifpfed_posLoading POS driver
ifpfed_ppeer ifpfed_pppoe ifpfed_ps ifpfed_sa Loading Aggregate sonet driver
ifpfed_shared_uplink Loading shared uplink driver
ifpfed_svcs ifpfed_vtkld platform: bcm bcmxxx fdcsio1: configured irq 5 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio2: configured irq 3 not in bitmap of probed irqs 0
sio2: port may not be enabled
sio3: configured irq 7 not in bitmap of probed irqs 0
sio3: port may not be enabled
fileassoc gpbcLoading the Protobuf-C module
ixgbe mt_ifpfeLoading Multilink Services PICs module.
Loading the M&T Platform NETPFE module
kld platform devices: fchipkld peertype: peertype_asp peertype_asq peertype_ce peertype_esp peertype_fpc160 peertype_fpc40 peertype_gfpc peertype_iq2 peertype_iqecc peertype_lccre peertype_lsq peertype_msp peertype_ose peertype_rfeb peertype_rfpc peertype_scb peertype_sfm peertype_sfpc peertype_slavere peertype_xdpckld JAM core: jam_core_ifpfeLoading the JAM-Core module
pvid_db kld ipsec kld.
Doing additional network setup:.
Starting final network daemons:.
setting ldconfig path: /usr/lib /opt/lib
ldconfig: warning: /usr/lib /opt/lib: No such file or directory
starting standard daemons: cron.
Initial rc.amd64 initialization:.
kern.nmbgencfgblobs: 1000000 -> 2000000
Lock Manager
RDM Embedded 7 [04-Aug-2006] http://www.birdstep.com
Copyright (c) 1992-2006 Birdstep Technology, Inc. All Rights Reserved.
Hi All,
I have deploying vmx in ESXi. But still have problem can’t configure interface em1 and em2, I got this message ” em interface are not user configurable in vmx”
Thanks in advanced
Hi,
The data interfaces will show as ge-0/0/x on Junos, so if you are only seeing the em interfaces, then I guess the VFP has not started up correctly. What is the output of “show chassis fpc” ?
Can you start a new thread on J-net? http://forums.juniper.net/t5/vMX/bd-p/vMX
Thanks 🙂
Nice write-up. Thank you.
Two questions:
1) How do I set up the vMX as an SNMP agent?
2) How do I set up the vMX so that it can work with Py-EZ ? When I run py-ez on my vMX, using the example in https://www.juniper.net/techpubs/en_US/junos-pyez1.2/topics/task/program/junos-pyez-program-device-connecting.html and it is throwing a connection refused error on 127.0.0.1. http://www.juniper.net/techpubs/en_US/junos/topics/reference/configuration-statement/port-edit-system-services-netconf.html and RFC 4742 say to use port 830 . nmap says nothing is listening on port 830.
Hi man
i have different kind of numa-related error:
Start vfp-vmx1………………………………[Failed]
error: Failed to start domain vfp-vmx1
error: internal error: Process exited prior to exec: libvirt: error : unsupported configuration: NUMA node 0 is unavailable
I set up 32bit Ubuntu on cpu below:
root@ubuntu:~# lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 61
Stepping: 4
CPU MHz: 2394.459
BogoMIPS: 4788.91
Virtualization: VT-x
Hypervisor vendor: VMware
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 4096K
Ok. I finally won with 64 b version of bubntu & help of the different sources. So i’ll 10k them here too:
https://www.redhat.com/archives/libvir-list/2009-November/msg00482.html
finally 10x to all of u Guys.
Found this very userful