Description

In Mixed VCP between QFX5100 or EX4600 and EX4300 environment, 10G DAC (740-030076) VCP may not come up after upgrading from 18.4 to 20.X.

Symptoms

After Virtual chassis devices come up, VCP may fail coming up.

root@switch> show virtual-chassis protocol adjacency
fpc0:
--------------------------------------------------------------------------
Interface             System         State        Hold (secs)
vcp-255/0/46.32768    c042.d013.86e0 Initializing        59       <<<<<<<<<<<<<<<<<<<<<<<<< Here!!
vcp-255/0/47.32768    c042.d013.dcc0 Up                  59

fpc1:
--------------------------------------------------------------------------
Interface             System         State        Hold (secs)
vcp-255/2/0.32768     c042.d013.dcc0 Up                  59
                                                                  <<<<<<<<<<<<<<<<<<<<<<<<< Missing vcp-255/2/1
fpc2:
--------------------------------------------------------------------------
Interface             System         State        Hold (secs)
vcp-255/2/0.32768     d007.ca58.54a0 Up                  58
vcp-255/2/1.32768     c042.d013.86e0 Up                  57

{master:0}
root@switch> show virtual-chassis

Virtual Chassis ID: e7f4.16a5.b235
Virtual Chassis Mode: Mixed
                                                Mstr           Mixed Route Neighbor List
Member ID  Status   Serial No    Model          prio  Role      Mode  Mode ID  Interface
0 (FPC 0)  Prsnt    TA37173XXXXX qfx5100-48s-6q 128   Master*      Y  VC   2  vcp-255/0/47
1 (FPC 1)  Prsnt    PD37170XXXXX ex4300-48p     128   Linecard     Y  VC   2  vcp-255/2/0
2 (FPC 2)  Prsnt    PD37170XXXXX ex4300-48p     128   Linecard     Y  VC   0  vcp-255/2/0
                                                                           1  vcp-255/2/1

Member ID for next new member: 3 (FPC 3)

{master:0}
root@switch> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
0/46        Configured         -1    Up           10000                               <<<<<<<<<<<<<<<<<<<<<<<<< No neighbor
0/47        Configured         -1    Up           10000        2   vcp-255/2/0

fpc1:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
2/0         Configured         -1    Up           10000        2   vcp-255/2/1
2/1         Configured         -1    Up           10000                               <<<<<<<<<<<<<<<<<<<<<<<<< No neighbor
1/3         Configured               Absent

fpc2:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
2/0         Configured         -1    Up           10000        0   vcp-255/0/47
2/1         Configured         -1    Up           10000        1   vcp-255/2/0
1/1         Configured               Absent
1/0         Configured               Absent
1/2         Configured               Absent
1/3         Configured               Absent

{master:0}
root@switch>

Solution

This has been fixed by PR1665250. Refer to the following link.
https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1665250

As a recovery way, delete and re-add EX or QFX device corresponding port from VCP as follows.
For example, assume that VCP 255/2/1 on member 1 failed coming up. Also, you may need to do the same on the opposite link as well.

root@switch> request virtual-chassis vc-port delete pic-slot 2 port 1 member 1
root@switch> request virtual-chassis vc-port set pic-slot 2 port 1 member 1

Modification History

2023-10-23 : First edition