Support and News Forum

Why is it that interfaces are not showing up on VCP? I was able to run VCP and VFP successfully. Both are connected with their em1 interfaces.

Please see attached files.





root> show interfaces terse
Interface Admin Link Proto Local Remote
cbp0 up up
demux0 up up
dsc up up
em1 up up
em1.0 up up inet 10.0.0.4/8
128.0.0.1/2
128.0.0.4/2
inet6 fe80::5200:ff:fe0b:1/64
fec0:0:0:4/64
tnp 0x4
esi up up
fxp0 up up
gre up up
ipip up up
irb up up
jsrv up up
jsrv.1 up up inet 128.0.0.127/2
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lo0.16385 up up inet
lsi up up
mtun up up
pimd up up
pime up up
pip0 up up
pp0 up up
rbeb up up
tap up up
vtep up up

Wow, changing the settings to this solved the problem. Woohoo!!!

VCP CPUx1, 2G RAM
VFP CPUx3, 4G RAM

============================================================================
vMX-VCP

root> show interfaces terse
Interface Admin Link Proto Local Remote
ge-0/0/0 up up
lc-0/0/0 up up
lc-0/0/0.32769 up up vpls
pfe-0/0/0 up up
pfe-0/0/0.16383 up up inet
inet6
pfh-0/0/0 up up
pfh-0/0/0.16383 up up inet
pfh-0/0/0.16384 up up inet
ge-0/0/1 up up
ge-0/0/2 up up
ge-0/0/3 up up
ge-0/0/4 up up
ge-0/0/5 up up
ge-0/0/6 up up
ge-0/0/7 up up
ge-0/0/8 up up
ge-0/0/9 up up
cbp0 up up
demux0 up up
dsc up up
em1 up up
em1.0 up up inet 10.0.0.4/8
128.0.0.1/2
128.0.0.4/2
inet6 fe80::5200:ff:fe0b:1/64
fec0:0:0:4/64
tnp 0x4
esi up up
fxp0 up up
gre up up
ipip up up
irb up up
jsrv up up
jsrv.1 up up inet 128.0.0.127/2
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lo0.16385 up up inet
lsi up up
mtun up up
pimd up up
pime up up
pip0 up up
pp0 up up
rbeb up up
tap up up
vtep up up

root>

============================================================================

All is well until I get this message from my vMX-VCP, then it will be disconnected to vMX-VFP.

root>
Message from syslogd@ at Jun 29 22:32:32 ...
fpc0 CMT: Error initializing PFE asics

it is weak cpu issue, I saw such before.
try earlier version like vMX 16.1

Uldis (UD) wrote: ↑

Fri Jun 30, 2017 7:02 am

it is weak cpu issue, I saw such before.
try earlier version like vMX 16.1

Alright. Thanks.