Hi All, Thanks for your interest in vMX! We apologize for a couple of missing pieces as part of vMX 15.1F4 release that have caused issues on user end. First, vMX ESXi image was missing due to some backend script issues. Second, Getting Started Guide for VMWare for vMX was missing a reference to metadata_usb file which caused VFP VM launch issue. Both issues have been resolved. Please refer to Juniper’s website for the images and documentation.
If you’re seeing other issues, please use Juniper vMX forum http://forums.juniper.net/t5/vMX/bd-p/vMX for support. Regards, Juniper vMX Team On 1/7/16, 6:22 AM, "juniper-nsp on behalf of Robert Hass" <juniper-nsp-boun...@puck.nether.net on behalf of robh...@gmail.com> wrote: >On Thu, Jan 7, 2016 at 3:17 PM, Robert Hass <robh...@gmail.com> wrote: > >> It would seem that vMX is still in the quite early stages. When I looked >>> at it a few months ago, the documentation was lacking lots of details. In >>> the end, I just didn't feel like it was ready for production in the role >>> that I wanted to use it in. The lack of VMWare support at the time was one >>> of the main reasons as well >>> >> >> After short testing I can confirm same feelings. Got a lot of error >> messages like this: >> > >Just one funny bug to confirm our feelings about vMX maturity :) >'show chassis hardware' shows different Serial Number after reboot. Huh so >how assign license do my VM ? :) > >Chassis VMX77 VMX >Chassis VMX81 VMX >Chassis VMX11 VMX > >Cheers >Rob >_______________________________________________ >juniper-nsp mailing list juniper-nsp@puck.nether.net >https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
