Switching

 View Only
last person joined: 9 hours ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 05-27-2023 16:34

    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!





    ------------------------------
    EDUARDO MENDEZ
    ------------------------------


  • 2.  RE: EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 05-29-2023 06:22

    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.



    ------------------------------
    NAVEEN M
    ------------------------------



  • 3.  RE: EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 05-29-2023 08:51

    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 



    ------------------------------
    EDUARDO MENDEZ
    ------------------------------



  • 4.  RE: EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 05-30-2023 04:04

    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 



    ------------------------------
    THEO QUENNEHEN
    ------------------------------



  • 5.  RE: EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 05-31-2023 09:14

    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
    #



    ------------------------------
    EDUARDO MENDEZ
    ------------------------------



  • 6.  RE: EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 05-31-2023 09:36

    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 



    ------------------------------
    THEO QUENNEHEN
    ------------------------------



  • 7.  RE: EX4600 issue upgrade (18.1R3-S8.3 to 21.4R3-S3.4)

    Posted 06-01-2023 16:55

    Hi THEO QUENNEHEN

    Nope, I didnt do it.

    I only have been configured

    Configure the redundancy groups for ICCP on EX4600-1
    #
    set protocols iccp peer "IP PEER EX4600-2" redundancy-group-id-list 1

    Configure the redundancy groups for ICCP  on QFX2
    #
    set protocols iccp peer "IP  PEER  EX4600-1" redundancy-group-id-list 1
    #

    I thought that it was optional and It isnt necessary.

    In my case the configuration will be, is that correct?

    On both EX4600-1 / EX4600-2

    set interfaces ae4 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae5 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae6 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae8 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae9 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae10 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae11 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae12 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae13 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae16 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae17 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae18 aggregated-ether-options mc-ae redundancy-group 1
    set interfaces ae19 aggregated-ether-options mc-ae redundancy-group 1

    tks!



    ------------------------------
    EDUARDO MENDEZ
    ------------------------------