Description

This article describes a specific issue where a VC split causing connectivity issues after a Junos upgrade

Symptoms

  • this is a 2 member EX4650 virtual-chassis.
  • only member 1 was upgraded and the vcports stayed physically down after the upgrade was completed.
  • When a 100G transceiver is a fiber cable, then the port won't come up and when a 100G transceiver is DAC, then the port will come up as 40G instead of 100G.
  • The following logs may be seen when this issue is triggered:
Soft inserting pic/port: 0/54!!!
[Mon Oct 28 15:02:56.944 LOG: Notice] qsfp-0/0/54 plugged in
[Mon Oct 28 15:03:00.358 LOG: Info] PORTDEV: Optic state changed for VCP port: 0/0/54 - Presence: 1
[Mon Oct 28 15:03:00.371 LOG: Debug] CMLC_LOCAL: Sending 'PIC Port Status send' msg to Master
[Mon Oct 28 15:03:00.420 LOG: Debug] dcbcm_port_resource_multi_set_on_quad Entry 0 - port=127 | phy_port=-1 | speed=40000 | lanes=4 | encap=0
[Mon Oct 28 15:03:00.420 LOG: Debug] dcbcm_port_resource_multi_set_on_quad Entry 1 - port=127 | phy_port=125 | speed=40000 | lanes=4 | encap=3
 
  • The 'show virtual-chassis vc-port' output may look like this:

root@sw> show virtual-chassis vc-port
localre:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
0/54        Configured         -1    Down         40000
0/55        Configured         -1    Down         40000

Solution

Upon further research we found a PR matching this particular event:

Affected platforms:

QFX5120-48T:QFX5120-32C:QFX5120-48Y:QFX5110-48S:EX4650:EX4650-48Y-VC

> The issue experienced is resolved in the following Junos releases:

 

junos:22.1R3-S5 junos:22.2R3-S1 junos:22.2R3-S3 junos:22.3R2-S1 junos:22.3R3 junos:22.3R3-S2 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1 junos:23.3R2

Modification History

2024-12-06 : Article Created