Ethernet Switching
Ethernet Switching

EX2300 Virtual Chassis - NotPrsnt

[ Edited ]
3 weeks ago
Hello, I have Virtual Chassis with two members - master and backup. Yesterday the backup member stopped working - with status NotPrsnt. I tried to connect to the backup switch by console cable, but the console connection also didn't work, so I suppose that the switch is dead (but ports blink) The question is - if I poweroff/poweron the backup switch and it will add to virtual-chassis after reboot, will it disturb network on master switch? Bofh switches form a LAG interface ae0 to chassis cluster.
9 REPLIES 9
Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago
Hi Gabriel,

If you have "no split-detection" in place, then the Master should working fine and current in Master state. If that's the case, you're ok to bring up the backup without harm.

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/virtual-chassis-mx-serie...

Hope this helps.

Regards,
-r.

--------------------------------------------------

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago

Hi Gabriel

 

I believe that the backup switch is already in not-prsnt state so powering it off and powering it on should not have any further impact with respect to the master switch. The lag interface will still have the member from master fpc as part of the lag ae0. 

Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago

Thank you for your answers. I wonder if it's a common thing to get EX2300 crashed, as it happened just a couple of days after running into production..

Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago
Hi Gabriel,

If you see a crash file in /var/tmp/ then please have it checked on a JTAC case. In general, saw one other post discussing a specific issue but can’t generalize it as common 😊.
https://forums.juniper.net/t5/Junos/EX2300-48T-Stop-working-after-random-time-after-upgrade-to-19/td...

Please keep us posted if you resolved your query on this post, so others can refer to it if they have the same question.

Hope this helps.

Regards,
-r.

--------------------------------------------------

If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated Smiley Happy.
Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago

HI Gabriel

 

If the backup switch stopped working it could mostly be due to file system corrouption.

Once you poweroff/poweron the backup and if it comes back up then check in the console logs for any bad blocks etc... during the boot up of backup.

Also you can check for the logs /var/run/dmesg.detail file to confirm if there were bad blocks. Usually a power cycle will fix it and you may not see it.

 

Hope this helps

 

Thanks

Ethernet Switching
Solution
Accepted by topic author Gabriel-
2 weeks ago

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago

Your issue might be related to the following PR,

 

https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1442376




#####
Please mark my post as solution if it helped you
Kudos will also be appreciated
Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago

Hi Gabriel, 

 

The previous ECalderon's post might be the issue since you console to the device and not get any output, the switch could still forward traffic for sometime, but later might stop... What is your current  switch version?

 

Thank you, 
Franky

Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

3 weeks ago

Very interesting PR.

 

Nice finding skills. Kudos.

 

Benjamin

Ethernet Switching

Re: EX2300 Virtual Chassis - NotPrsnt

2 weeks ago

Thanks for help. After some digging, it really looks like the mentioned issue: https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1442376 and in the thread on forum - https://forums.juniper.net/t5/forums/v3_1/forumtopicpage/board-id/JUNOS/thread-id/14654/page/3

 

I rebooted the switch and it started to work again (probably temporarly), I'll try to make an upgrade soon to 18.2R3-S2 from 

 18.2R3.4