Switching

Hello Guys,

I tried upgrading an ex4600 from 18.1R3-S8.3  to  21.4R3-S3.4 but after the update, the switch doesn't boot well (see print 1).

When I try to commit after seeing the error on print 1, the switch shows me the following error (see print 5).

The switch booted without the configuration on it, I don't why happen it and my solution was to rollback the version from 21.4R3-S3.4 to 18.1R3-S8.3.

Any suggestions?; pls?

Tks!

HI EDUARDO MENDEZ,

Firstly, take the backup config of EX-4600 with following command.
show | display set | no-more 

delete l3 interface irb.0 try commit of configuration.

We have observed the same issue in one of the client device.
Try this and let me know about it.

Hello Guys,

I tried upgrading an ex4600 from 18.1R3-S8.3  to  21.4R3-S3.4 but after the update, the switch doesn't boot well (see print 1).

When I try to commit after seeing the error on print 1, the switch shows me the following error (see print 5).

The switch booted without the configuration on it, I don't why happen it and my solution was to rollback the version from 21.4R3-S3.4 to 18.1R3-S8.3.

Any suggestions?; pls?

Tks!

Hi NAVEEN M,

I have been deleted that interface (irb.0) before the upgrade, the other interface that deleted was vme.

The switch still shows up issue upgrading 

HI EDUARDO MENDEZ,

Firstly, take the backup config of EX-4600 with following command.
show | display set | no-more 

delete l3 interface irb.0 try commit of configuration.

We have observed the same issue in one of the client device.
Try this and let me know about it.

Hello Guys,

I tried upgrading an ex4600 from 18.1R3-S8.3  to  21.4R3-S3.4 but after the update, the switch doesn't boot well (see print 1).

When I try to commit after seeing the error on print 1, the switch shows me the following error (see print 5).

The switch booted without the configuration on it, I don't why happen it and my solution was to rollback the version from 21.4R3-S3.4 to 18.1R3-S8.3.

Any suggestions?; pls?

Tks!

Hello Eduardo, 

You should check the configuration of mc-ae interface, did you define the redundancy-group ? 
here find a mc-ae config example : 
https://www.juniper.net/documentation/us/en/software/junos/mc-lag/topics/topic-map/examples-mc-lag.html

Can you share your configuration ? 

Your upgrade path don't respect the Juniper's recommandations .. no more than 3 release at each. 
When i got many jump to upgrade, i use the USB key process to format and reinstall Junos directly in the new release.  You need a physical access and it start with default config (so you need to manage it) but you start with a fresh and proper install of JunOS ! 

Regards, 
Théo 

Hi NAVEEN M,

I have been deleted that interface (irb.0) before the upgrade, the other interface that deleted was vme.

The switch still shows up issue upgrading 

HI EDUARDO MENDEZ,

Firstly, take the backup config of EX-4600 with following command.
show | display set | no-more 

delete l3 interface irb.0 try commit of configuration.

We have observed the same issue in one of the client device.
Try this and let me know about it.

Hello Guys,

I tried upgrading an ex4600 from 18.1R3-S8.3  to  21.4R3-S3.4 but after the update, the switch doesn't boot well (see print 1).

When I try to commit after seeing the error on print 1, the switch shows me the following error (see print 5).

The switch booted without the configuration on it, I don't why happen it and my solution was to rollback the version from 21.4R3-S3.4 to 18.1R3-S8.3.

Any suggestions?; pls?

Tks!

Hi THEO QUENNEHEN, 

Between  18.1R3-S8.3 to 21.4R3-S3.4, it has three releases, are you agree?

set interfaces ae4 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae5 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae6 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae8 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae9 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae10 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae11 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae12 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae13 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae16 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae17 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae18 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae19 aggregated-ether-options mc-ae chassis-id 0
#
#
#
#Specify a unique chassis ID on QFX2
#
set interfaces ae4 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae5 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae6 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae8 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae9 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae10 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae11 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae12 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae13 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae16 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae17 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae18 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae19 aggregated-ether-options mc-ae chassis-id 1
#

Hello Eduardo, 

You should check the configuration of mc-ae interface, did you define the redundancy-group ? 
here find a mc-ae config example : 
https://www.juniper.net/documentation/us/en/software/junos/mc-lag/topics/topic-map/examples-mc-lag.html

Can you share your configuration ? 

Your upgrade path don't respect the Juniper's recommandations .. no more than 3 release at each. 
When i got many jump to upgrade, i use the USB key process to format and reinstall Junos directly in the new release.  You need a physical access and it start with default config (so you need to manage it) but you start with a fresh and proper install of JunOS ! 

Regards, 
Théo 

Hi NAVEEN M,

I have been deleted that interface (irb.0) before the upgrade, the other interface that deleted was vme.

The switch still shows up issue upgrading 

HI EDUARDO MENDEZ,

Firstly, take the backup config of EX-4600 with following command.
show | display set | no-more 

delete l3 interface irb.0 try commit of configuration.

We have observed the same issue in one of the client device.
Try this and let me know about it.

Hello Guys,

I tried upgrading an ex4600 from 18.1R3-S8.3  to  21.4R3-S3.4 but after the update, the switch doesn't boot well (see print 1).

When I try to commit after seeing the error on print 1, the switch shows me the following error (see print 5).

The switch booted without the configuration on it, I don't why happen it and my solution was to rollback the version from 21.4R3-S3.4 to 18.1R3-S8.3.

Any suggestions?; pls?

Tks!

Hi Eduardo, 

Nope, many more ! 
Release are 18.1, 18.2, 18.3, 18.4, 19.1, 19.2, 20.2, 20.4, 21.1, 21.2, 21.3, 21.4 


Did you have redundancy-group defined on your mc-ae interfaces ? 
like this below for ae4 ?
set interfaces ae4 aggregated-ether-options mc-ae redundancy-group 1

Regards,
Théo 

Hi THEO QUENNEHEN, 

Between  18.1R3-S8.3 to 21.4R3-S3.4, it has three releases, are you agree?

set interfaces ae4 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae5 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae6 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae8 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae9 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae10 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae11 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae12 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae13 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae16 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae17 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae18 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae19 aggregated-ether-options mc-ae chassis-id 0
#
#
#
#Specify a unique chassis ID on QFX2
#
set interfaces ae4 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae5 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae6 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae8 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae9 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae10 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae11 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae12 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae13 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae16 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae17 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae18 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae19 aggregated-ether-options mc-ae chassis-id 1
#

Hello Eduardo, 

You should check the configuration of mc-ae interface, did you define the redundancy-group ? 
here find a mc-ae config example : 
https://www.juniper.net/documentation/us/en/software/junos/mc-lag/topics/topic-map/examples-mc-lag.html

Can you share your configuration ? 

Your upgrade path don't respect the Juniper's recommandations .. no more than 3 release at each. 
When i got many jump to upgrade, i use the USB key process to format and reinstall Junos directly in the new release.  You need a physical access and it start with default config (so you need to manage it) but you start with a fresh and proper install of JunOS ! 

Regards, 
Théo 

Hi NAVEEN M,

I have been deleted that interface (irb.0) before the upgrade, the other interface that deleted was vme.

The switch still shows up issue upgrading 

HI EDUARDO MENDEZ,

Firstly, take the backup config of EX-4600 with following command.
show | display set | no-more 

delete l3 interface irb.0 try commit of configuration.

We have observed the same issue in one of the client device.
Try this and let me know about it.

Hello Guys,

I tried upgrading an ex4600 from 18.1R3-S8.3  to  21.4R3-S3.4 but after the update, the switch doesn't boot well (see print 1).

When I try to commit after seeing the error on print 1, the switch shows me the following error (see print 5).

The switch booted without the configuration on it, I don't why happen it and my solution was to rollback the version from 21.4R3-S3.4 to 18.1R3-S8.3.

Any suggestions?; pls?

Tks!