Hi Folks,
Auto-provisioning will take effect only on a pre-provisioned virtual chassis knob is enabled in the box under virtual-chassis hierarchy.
virtual-chassis {
preprovisioned; <<<<
member 0 {
role routing-engine;
With auto-provisioning, there is no need to for network ports to be used as virtual chassis ports. Auto-provisioning will take effect, only on a pre-provisioned virtual chassis and when the following conditions are met:
For the auto-provisioning feature to take effect, all the devices that are connected over network ports must be pre-provisioned on the master.
The master should contain the serial number of all of the EX4200 devices, which are required to form a VC.
When pre-provisioning is completed on the master, the VCPs are automatically configured and the devices are added to the VC in the sequence that they are connected.
When pre-provisioning is configured, LLDP on each member will send out sentinel packets on each of the network ports and monitor if there is a response.
In this case , if the two uplink ports are somehow bridged on the switch, then LLDP on member 0/3 will detect each other and make the conversion of this ports into VCEP ports. This is due to LLDP using regular packets.
After the conversion is complete, the two ports will try to exchange VC-specific packets.
To avoid such outages, the following methods can be used:
- Disable pre-provisioning.
- Disable LLDP.
Other than the above methods, there is no command to disable the auto-provisioning feature. if LLDP is disabled for the interfaces or pre-provisioning is disabled, everything works normally.
{master:0}[edit]
root@ex4200.ats36# run show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Up 32000 1 vcp-1
vcp-1 Dedicated 1 Up 32000 2 vcp-0
0/19 Auto-Configured -1 Up 1000 2 vcp-255/0/18 < Ports become VCP ports
fpc1:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Up 32000 2 vcp-1
vcp-1 Dedicated 1 Up 32000 0 vcp-0
fpc2:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Up 32000 0 vcp-1
vcp-1 Dedicated 1 Up 32000 1 vcp-0
0/18 Auto-Configured -1 Up 1000 0 vcp-255/0/19 < Ports become VCP ports
Please refer the below KB,
Other References: