Troubleshooting VFP and VCP Connection Establishment
Purpose
When the VCP and VFP connection is established, the show interfaces terse command in the VCP CLI displays the ge-0/0/x interfaces and the following messages appear in the
VFP syslog file:
RPIO: Accepted connection from 128.0.0.1:50896 <-> vPFE:3000 RPIO: Accepted connection from 128.0.0.1:56098 <-> vPFE:3000 HOSTIF: Accepted connection
If the VCP cannot connect to the VFP, the VFP syslog file does
not display the RPIO and HOSTIF messages.
Action
Run the request chassis fpc slot 0 restart command from the VCP CLI. If an FPC is in transition error message is displayed, then run restart chassis-control.
If these commands do not correct the problem, verify whether
the VCP can ping the VFP from the routing-instance __juniper_private1__. The three management interfaces (for the host, VCP VM, and VFP
VM) connected to the internal bridge should be able to reach each
other. For example:
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
If the VCP cannot ping the VFP, perform these tasks:
Use the
brctl showcommand to verify the bridge configuration and connected interfaces.Verify that the startup configuration file is correct.
Verify that the VFP and the VCP VMs are up and the correct IP addresses are assigned.
Restart the FPC from the VCP VM.
Restart the chassis management process from VCP VM.
Stop and start the VFP VM.
Stop and start the VCP VM.
Restart the host.
If the problem persists, contact the Juniper Networks Technical Assistance Center (JTAC).