vMX
vMX

vMX FPC empty

‎09-19-2017 08:14 AM

Hello World,

 

So I got pretty motivated about Juniper SP (tired of the same ol' Cisco rhetoric about upward mobility in the workplace, etc ---- figured I'd pursue something I'm a bit more passionate about) ... 

 

At any rate, I started down the path of building out a generic Juniper SP topology in ESXi 5.5U3 - after obtaining the latest vMX images from Juniper site. In my case, I beleive 17.3R1. 

 

They made it easy of course, consolidating everything to two OVA files, one for VCP and VFP. Imported them no problem, however when issuing "show chassis fpc" or "show interfaces terse" ... I see nothing. It's as if they don't exist. I've been careful to allocate recommended resources, following multiple sources for requirements, but still no joy. 

 

What gives???

 

 FPC_MISSING.PNG



Jesse W.
Sr. Systems/Network Engineer
CCNA, CCNP R&S, JNCIA, JNCIS-SEC

11 REPLIES 11
vMX

Re: vMX FPC empty

‎09-23-2017 10:24 PM

Hello,

 

Looks like communication issues between vCP and vFP.

Can you try steps given in the link below?

 

https://www.juniper.net/documentation/en_US/vmx16.1/topics/task/verification/vmx-vm-connection-troub...

 

Regards,

 

Rushi

 

 

vMX

Re: vMX FPC empty

‎09-26-2017 01:08 PM

Hi Rushi,

      I did perform those steps and I am able to ping 128.0.0.6 routing-instance __juniper_private1__ but I am still not having any physical ports showing up. When I do show chassis fpc I get 
0 present 

1...11 false

and when I do show chassis fpc pic-status i get:

slot 0 present virtual FPC

vMX

Re: vMX FPC empty

‎09-27-2017 01:06 AM

Hi Bhoomi

 

Please can you confirm the resources that you have allocated to VCP and VFP, and that the FPC is configured as Lite mode (if this is a lab)

 

Thanks

Matt Dinham
Juniper Networks Ambassador

Twitter: @mattdinham
Blog: http://matt.dinham.net

If this worked for you please flag my post as an 'Accepted Solution' so others can benefit. A kudo would be cool if you think I earned it.
vMX

Re: vMX FPC empty

‎09-27-2017 08:51 PM

Matt,

 

I am having the exact same issue as Bhoomi. I used the ping syntax on the link you provided and ping was good....

 

root> ping 128.0.0.16 routing-instance __juniper_private1__
PING 128.0.0.16 (128.0.0.16): 56 data bytes
64 bytes from 128.0.0.16: icmp_seq=0 ttl=64 time=0.273 ms
64 bytes from 128.0.0.16: icmp_seq=1 ttl=64 time=0.606 ms


 However, I also cannot see the ge- interfaces. I tried lite-mode, but that didn't work either. I have plenty of resources, I'm running on a Dell Blade Chassis, the Dell m1000e series blade. In my case I've allocated no less than 4 x CPUs and at least 8-10 GB of memory ---- but still cannot see interfaces. 

 

I just don't get it. This is really bothering me because I desparately want to incorporate vMX into my Service Provider lab topology. 

 

no_interfaces.PNG

 

Somebody help me figure this out ... if you do ... I'll call you the coolest engineer in the world for 10 more years ---- em hem --- if I remember in 10 years that is :-)



Jesse W.
Sr. Systems/Network Engineer
CCNA, CCNP R&S, JNCIA, JNCIS-SEC

vMX

Re: vMX FPC empty

‎09-28-2017 01:54 AM

Hi,

 

Please can you post details on how you have the vSwitches/vNICs configured for VCP and VFP (but as you have a working ping from VCP I'm assuming they are OK).

 

If you login to the VFP console are you seeing any errors, also see /var/log

 

Thanks

Matt Dinham
Juniper Networks Ambassador

Twitter: @mattdinham
Blog: http://matt.dinham.net

If this worked for you please flag my post as an 'Accepted Solution' so others can benefit. A kudo would be cool if you think I earned it.
vMX

Re: vMX FPC empty

[ Edited ]
‎09-28-2017 09:40 AM

Matt,

 

I'm both a systems/network engineer, so pretty savvy on the Virtual side as well. To answer your question, I used the default number of vNICs automatically assigned, I believe two on each VM, and made sure 100% sure to trunk the vSwitch, set it to promiscuous, and put the 2nd vNIC on same VLAN. I've tried destroying VMs, and re-importing over and over ---- never seems to work. Seems like others have the same issue when I Google-Fu. 

Is there an absolutely functional combination of ESXi/vMX that you're aware of? For example ESXi 5.5U3 and vMX 14.1, etc?

 

I feel like everything is there, just some minor detail is snagging me here. Sheesh :/



Jesse W.
Sr. Systems/Network Engineer
CCNA, CCNP R&S, JNCIA, JNCIS-SEC

vMX
Solution
Accepted by topic author jesse.worst@kisinc.net
‎10-04-2017 11:42 AM

Re: vMX FPC empty

‎09-28-2017 10:26 AM

Hi Jesse,

 

You need to have two vNICs on the VCP and VFP as follows

vNIC1 - management (fxp0)

vNIC2 - internal (used for VCP-VFP comms)

 

Subsequent NICs on the VFP are data interfaces

vNIC3 - ge-0/0/0

vNIC4 - ge-0/0/1

etc

 

Usually the NIC1 would either map to your management network, or create a new vSwitch for management and assign the NICs to that.

 

The NIC2 (internal network) should map to a dedicated vSwitch that links NIC2 on the VCP to NIC2 on the VFP only (one required per vMX instance).

 

Now if you have not assigned a 3rd NIC to the VFP, then it does not have a data interface so the virtual VFP will not start all the required processes and you will not see the ge-0/0/* in Junos.

 

Hope that helps

 

 

 

 

Matt Dinham
Juniper Networks Ambassador

Twitter: @mattdinham
Blog: http://matt.dinham.net

If this worked for you please flag my post as an 'Accepted Solution' so others can benefit. A kudo would be cool if you think I earned it.
vMX

Re: vMX FPC empty

‎10-04-2017 11:48 AM

Giving you credit for solution --- lol --- although I figured out before seeing your post. 

 

My issue wasn't entirely related to NIC allocation, so much as it was just waiting a while for FPC to come up. 

 

Interesting behavior in that when you first boot and run  > sho interfaces terse ... you don't see any ge- interfaces, however after about 2-4 more minutes, I checked again and boom! they are present. 

 

At any rate. I now have created 6 healthy instances of vMX 17.x on ESXi 5.5 with no problem (for those inquisitive minds wondering if there are compatibility issues with the above - nope, they play nice together.)

 

I now have an awesome hetergeneous CCIE-SP/JNCIE-SP lab, with the ability to emulate many topologies. Onwards to MP-BGP! Later.

 

Capture.PNG

 

 



Jesse W.
Sr. Systems/Network Engineer
CCNA, CCNP R&S, JNCIA, JNCIS-SEC

vMX

Re: vMX FPC empty

‎10-04-2017 12:41 PM
Cool, glad it’s sorted, and nice lab Smiley Happy

Yeah it takes a few minutes for the VFP to spin everything up. On boot the VFP syncs the virtualised TRIO forwarding plane (RIOT) binaries/code from the VCP and then it all must load up.
Matt Dinham
Juniper Networks Ambassador

Twitter: @mattdinham
Blog: http://matt.dinham.net

If this worked for you please flag my post as an 'Accepted Solution' so others can benefit. A kudo would be cool if you think I earned it.
vMX

Re: vMX FPC empty

2 weeks ago

Hello,

 

I am also facing the similar problem like you faced earlier. It seems the connection between VCP and VFP is absolutely fine however still I am unable to see ge-0/0/* interfaces.

 

root@PE1> ping 128.0.0.1 routing-instance __juniper_private1_
ping: invalid routing instance `__juniper_private1_'

root@PE1> ping 128.0.0.1 routing-instance __juniper_private1__
PING 128.0.0.1 (128.0.0.1): 56 data bytes
64 bytes from 128.0.0.1: icmp_seq=0 ttl=64 time=0.252 ms
64 bytes from 128.0.0.1: icmp_seq=1 ttl=64 time=0.055 ms
64 bytes from 128.0.0.1: icmp_seq=2 ttl=64 time=0.165 ms
64 bytes from 128.0.0.1: icmp_seq=3 ttl=64 time=0.150 ms
64 bytes from 128.0.0.1: icmp_seq=4 ttl=64 time=0.553 ms
64 bytes from 128.0.0.1: icmp_seq=5 ttl=64 time=0.166 ms
^C
--- 128.0.0.1 ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.055/0.224/0.553/0.158 ms

 

 

root@PE1> show interfaces terse | match ge-

 

 

Apprecaite any help on this matter...

 

I m using laptop with 32GB RAM and Corei7 Vpro 8th Gen.

 

Regards,

Raju

CCNA,JNCIP-SP, SRA

vMX

Re: vMX FPC empty

2 weeks ago

Hi Raju

What is the Junos version and the adapter type which you are using?