Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

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:

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 to restart the FPC. 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:

If the VCP cannot ping the VFP, perform these tasks:

  1. Make sure that both the VCP and VFP have the network adapter connected to the internal bridge vSwitch (br-int).
  2. Verify that the MAC address of em1 on the VCP matches the MAC address shown in the Virtual Machine Properties.

    To determine the MAC address of the em1 interface:

  3. Verify that the MAC address of the interface on the VFP matches the MAC address shown in the Virtual Machine Properties.

    To determine the MAC address of the interface:

If the problem persists, contact the Juniper Networks Technical Assistance Center (JTAC).