Support and News Forum

The file hierarchy of vMX 16.1 and 17.1 is different. It does not include the qcow2 and img file in the tgz file.
Can anyone help to advise the procedure to import the vMX 16.1 JUNOS? thanks

http://eve-ng.net/index.php/documentati ... -16-x-17-x


root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls
ova upgrade
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7#
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls
ova upgrade
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls ova/
vcp_16.1R4.7.ova vfpc_16.1R4.7.ova
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls upgrade/
junos-vmx-x86-64-16.1R4.7.tgz
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7#

jackychu wrote: ↑

Mon Jul 31, 2017 6:05 am

The file hierarchy of vMX 16.1 and 17.1 is different. It does not include the qcow2 and img file in the tgz file.
Can anyone help to advise the procedure to import the vMX 16.1 JUNOS? thanks

http://eve-ng.net/index.php/documentati ... -16-x-17-x


root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls
ova upgrade
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7#
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls
ova upgrade
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls ova/
vcp_16.1R4.7.ova vfpc_16.1R4.7.ova
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7# ls upgrade/
junos-vmx-x86-64-16.1R4.7.tgz
root@eve-ng:~/tmp/vmx-esxi-16.1R4.7#

decompress the ova,and vmdk will shows up.
Then convert the vmdk to qcow2.
I think this will be ok,you can try it!

Could you please follow this HowTo
http://www.eve-ng.net/index.php/documen ... -16-x-17-x

here is exactly said which iage must me rnamed to which one and placed in which directory.
UD

Thanks ohsanpao19988 and Uldis.
It works now.

hello, i received several message from syslogd after the VCP has completely boot up. Do anyone have any ideas of following message?d

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 SCHED: Thread 63 (PFE Statistics) ran for 1020 ms without yielding

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Scheduler Oinker

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 0: sp = 0xd9d96968, pc = 0x8077c11

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 1: sp = 0xd9d969c8, pc = 0x8105cfb

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 2: sp = 0xd9d96a08, pc = 0x811c506

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 3: sp = 0xd9d96eb8, pc = 0x8161256

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 4: sp = 0xd9d96ff8, pc = 0x807d756

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 5: sp = 0xd75e0fd8, pc = 0x8074795

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 6: sp = 0xd75e0ff8, pc = 0x807d756

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 7: sp = 0xffcd1208, pc = 0x807649a

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 8: sp = 0xffcd1228, pc = 0x807cf45

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 9: sp = 0xffcd1248, pc = 0x8065813

Message from syslogd@vMX-VCP at Aug 1 03:01:54 ...
vMX-VCP fpc0 Frame 10: sp = 0xffcd1268, pc = 0x4f5459d3

Hi. Is everything working?

Pure guess this but that looks like messages related to the interfaces. Pretty sure this happens in some way on all Juniper V devices when the fpc loads and the interfaces show up.

If it's working not to worry

Cheers

These messages disappear after some time...

UD

Sipart wrote: ↑

Tue Aug 01, 2017 7:34 am

Hi. Is everything working?

Pure guess this but that looks like messages related to the interfaces. Pretty sure this happens in some way on all Juniper V devices when the fpc loads and the interfaces show up.

If it's working not to worry

Cheers

yes, it is working but it shows frequently that make the screen so messy...

You can ignore this error - it's nothing to worry about.
I talked with juniper - if you want to get rid of this, follow the Instructions on my Blog: https://jncie.eu/how-to-get-rid-of-sche ... er-on-cli/

thanks Chris.