Jump to content


13
[Offer]

Juniper vQFX



115 replies to this topic

#29 densma

densma

    Newbie

  • Members
  • Pip
  • 0 posts
  • 18 thanks

Posted 24 January 2017 - 01:32 AM

what's username /password?. nothing seem to work. tried root/no and root with no pw
trying on gns3

#30 000CCIE000

000CCIE000

    Member

  • Members
  • PipPip
  • 12 posts
  • 55 thanks

Posted 24 January 2017 - 01:38 AM

try  root/Juniper   , root/root

Thanked by 2 Members:
donahmed007 , densma

#31 densma

densma

    Newbie

  • Members
  • Pip
  • 0 posts
  • 18 thanks

Posted 24 January 2017 - 12:46 PM

that works thanks

#32 LstEDim

LstEDim

    Member

  • Members
  • PipPip
  • 10 posts
  • 7 thanks

Posted 24 January 2017 - 09:11 PM

it's really working. Thanks

#33 dzzz

dzzz

    Junior Member

  • Members
  • PipPip
  • 7 posts
  • 472 thanks

Posted 07 February 2017 - 06:34 AM

can anyone seed

#34 HermanToothrot

HermanToothrot

    Member

  • Members
  • PipPip
  • 32 posts
  • 17364 thanks
  • LocationMonkey Island

Posted 11 February 2017 - 03:00 AM

View Postdzzz, on 07 February 2017 - 06:34 AM, said:

can anyone seed

Can't seed, but I can upload either the .vmdk files, or the vagrant .box files somewhere for you. Not going to be Mega or Dropbox, though.

#35 HermanToothrot

HermanToothrot

    Member

  • Members
  • PipPip
  • 32 posts
  • 17364 thanks
  • LocationMonkey Island

Posted 14 February 2017 - 06:49 AM

View Postdzzz, on 07 February 2017 - 06:34 AM, said:

can anyone seed

Here are the .vmdk files:

Hidden Content
You'll be able to see the hidden content once you press the thanks button.

The .7z archive isn't password protected. You'll have to supply an email address to download it, so just use a burner account you don't care about (I use one for any vendors, especially Solarwinds, that require an email to download an eval).   I'll edit this post once the vagrant .box files are uploaded to the same file host.  I don't know if they've changed it, but the only real documentation for the vQFX pre-release has been for the vagrant files.  The login for the virtual RE is root/Juniper.


Here are the vagrant files:

Hidden Content
You'll be able to see the hidden content once you press the thanks button.

Edited by HermanToothrot, 14 February 2017 - 08:52 AM.


Thanked by 49 Members:

#36 kechik

kechik

    Advanced Member

  • Members
  • PipPipPip
  • 109 posts
  • 170 thanks

Posted 14 February 2017 - 09:22 AM

Hi all,

It works on GNS3 using .vmdk.
kechik, proud to be a member of IT Certification Forum since Dec 2008.

#37 HermanToothrot

HermanToothrot

    Member

  • Members
  • PipPip
  • 32 posts
  • 17364 thanks
  • LocationMonkey Island

Posted 14 February 2017 - 10:43 AM

View Postkechik, on 14 February 2017 - 09:22 AM, said:

Hi all,

It works on GNS3 using .vmdk.

Yup!  Don't even need to convert them to .qcow2 disk images, since they'll work as-is. One thing that i noticed, was that assigning more than 15 interfaces to the vRE doesn't give you more xe-0/0/x switchports (at least, not in version 1.5.3).

Here's what I mean:

virtual Routing Engine -

Eth0 - connect to OOB switch
Eth1 - connect to Eth1 of the virtual PFE
Eth2 - can't use for whatever reason
Eth3 - xe-0/0/0
Eth4 - xe-0/0/1
Eth5 - xe-0/0/2
...omitted...
Eth14 -  xe-0/0/11

If I tried to assign it something like, say, 24 NICs, Eth14 is still the last xe-0/0/x switchport. The interfaces beyond that are just em ports, like em15, em16, em17, etc...  

It's also weird that "edit vlans" doesn't exist yet, but that's probably since it's still pre-release. The same was true with the pre-release versions of vMX.  The command is present in the production versions.  We can also use PFE shell commands on the vRE VM, to run diagnostics on the vPFE VM.      edit: I'm wrong, it DOES work.

Oh, and all the xe-0/0/x switchports are set to use DHCP by default, so you need to turn that off, if you want to assign those ports a static IP.

EDIT: It's cool that we can now hotlink running Qemu VMs in the beta versions of GNS3 2.0.  That means LACP and MC-LAG now failover properly, among other things. Before, the VMs would still think the links were present, even if deleted, and we don't have to shutdown and restart the VM to add a new device to a Qemu VM.

Edited by HermanToothrot, 14 February 2017 - 07:47 PM.


#38 kechik

kechik

    Advanced Member

  • Members
  • PipPipPip
  • 109 posts
  • 170 thanks

Posted 14 February 2017 - 01:07 PM

Hi Herman,


Yes. I'm think the limitation xe interface just to xe-0/0/11 only. "Edit Vlans" work properly.

{master:0}[edit vlans]
[email protected]#
kechik, proud to be a member of IT Certification Forum since Dec 2008.

#39 HermanToothrot

HermanToothrot

    Member

  • Members
  • PipPip
  • 32 posts
  • 17364 thanks
  • LocationMonkey Island

Posted 14 February 2017 - 02:24 PM

View Postkechik, on 14 February 2017 - 01:07 PM, said:

Hi Herman,


Yes. I'm think the limitation xe interface just to xe-0/0/11 only. "Edit Vlans" work properly.

{master:0}[edit vlans]
root[email protected]#

Huh.  When I tried it, I'd get an error. I'll have to give it another shot later tonight, or tomorrow.

EDIT: Weird. Now it works. Having a booger of a time getting the irb interfaces and bridge-domain stuff working right on a trunk port, but that's likely just due to me having a brain fart/operator error. Still new to Junos in general, and all that.

And yeah, you're likely correct about the VM limiting us to just 12 switchports. EXOS from Extreme Networks is the same (1 mgmt port, 12 switchports),  and with vEOS from Arista, ports beyond Eth19 or so, don't work correctly. There's a work around to get CumulusVX to support more ports, but I forget exactly what the procedure is.

Edited by HermanToothrot, 14 February 2017 - 07:54 PM.


#40 kechik

kechik

    Advanced Member

  • Members
  • PipPipPip
  • 109 posts
  • 170 thanks

Posted 21 February 2017 - 02:22 AM

Hi,

Anyone success setup VCF using this vQFX?


Thanks
kechik, proud to be a member of IT Certification Forum since Dec 2008.

#41 slimy_cat

slimy_cat

    Member

  • Members
  • PipPip
  • 35 posts
  • 4916 thanks

Posted 21 February 2017 - 03:58 PM

View Postkechik, on 14 February 2017 - 01:07 PM, said:

Hi Herman,
Yes. I'm think the limitation xe interface just to xe-0/0/11 only.
I think, it may be a QEMU-KVM limitation.
Previously KVM allowed to create only 8 virtual NICs. https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/595873

#42 HermanToothrot

HermanToothrot

    Member

  • Members
  • PipPip
  • 32 posts
  • 17364 thanks
  • LocationMonkey Island

Posted 21 February 2017 - 07:00 PM

View Postslimy_cat, on 21 February 2017 - 03:58 PM, said:

I think, it may be a QEMU-KVM limitation.
Previously KVM allowed to create only 8 virtual NICs. https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/595873

Yeah, someone ran into a similar issue with getting more interfaces to work, when using CumulusVX. I don't recall their workaround, but they had to launch it via qemu/kvm using some extra statements to get extra virtio-net-pci interfaces to come online.  This may or may not work with vQFX, though...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Organization

Community

Downloads

Test Providers

Site Info


Go to top