Description

In a VC environment, due to management interface up, vme interface is down and causes duplicate IP in the monitoring tool.

Symptoms

VME is showing physically down.
Issue will be observed in devices which are in VC configuration.

Solution

Perform the following checks to make the vme interface UP:

> show interface vme terse (vme0 interface is showing as physically down)

{master:0}[edit]
root@SwitchA# run show interfaces me0 terse
Interface               Admin Link Proto    Local                 Remote
vme0                     up    down
vme0.0                   up    down   eth-switch


> The status won't change even when you disable /delete the interface and reconfigured it.

> We can delete the em interface and configure the vme interface as management to make vme interface up.

#delete interface em -------------> (To delete the management interface)
#set interfaces vme unit 0 family inet address < ip address > -------> (To configure vme interface)


The idea of the vme is that you use only one IP to manage the whole stack, so you basically can get to the vme's ip address from any of the physical management interfaces on each VC member always using the same IP.

> Perform the master switch over, the below command helps you with master switch over: 

> request chassis routing-engine master switch

> After the mastership exchange verify the vme interface status again.

Modification History

2024-01-09: Article modified.
2024-01-05 : Article Created

Related Information

https://community.juniper.net/discussion/virtual-chass-vme0-down-despite-em0-interface-up