Switching

 View Only
last person joined: 23 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.  EX3400 upgrade failing with (/usr/sbin/clksyncd) dumped core.

    Posted 17 days ago

    Is there anyway to get more information about a validation failure during a code upgrade?  Maybe debug flags?

    We are in the process of upgrading our ex3400's from 18.2 to 23.4.  We've done multiple single switches with a jump from 21.4R3 to 23.4R2.  This same process with our VC stack has failed multiple times.  I've tried jumping 21.4R3 to lower code versions (22.1,22.3,22.4) all fail with the same apparent error (below).


    I can do a no-validate or a force but was hoping to find out why single switches work but the VC's fail.  The only thing in my VC config is preprovisioning.  I can't believe that is the failure point. 
    I doubt this is a space issue. we get partition to 40%, install the code on each VC member individually then schedule reboot the next morning.

    Thanks
    wes

    ---------Error during software add ----------------------------
    Hardware Database regeneration succeeded
    Validating against /config/juniper.conf.gz
    Ethernet Clock Synchronization Process: ../../../../../../src/junos/usr.sbin/clksyncd/clksyncd_atlas.c:clksyncd_atlas_get_cb_logical_slot_number:2396: insist '0' failed
    mgd: error: Check-out pass for Ethernet Clock Synchronization Process (/usr/sbin/clksyncd) dumped core (0x86)
    mgd: error: configuration check-out failed
    Validation failed
    Validating against /config/rescue.conf.gz
    Ethernet Clock Synchronization Process: ../../../../../../src/junos/usr.sbin/clksyncd/clksyncd_atlas.c:clksyncd_atlas_get_cb_logical_slot_number:2396: insist '0' failed
    mgd: error: Check-out pass for Ethernet Clock Synchronization Process (/usr/sbin/clksyncd) dumped core (0x86)
    mgd: error: configuration check-out failed
    Validation failed
    ERROR: Current configuration not compatible with junos-arm-32-23.4R2.13.tgz



    ------------------------------
    WES HALL
    ------------------------------


  • 2.  RE: EX3400 upgrade failing with (/usr/sbin/clksyncd) dumped core.

    Posted 17 days ago

    Hi Wes,

    You can use no-validate to skip checks for the configuration against "juniper.conf.gr" and "rescue.conf.gr." 

    These validation attempts fail due to errors with the "Ethernet Clock Synchronization Process." Since you have minimal configuration on your devices, configuration validation won't be necessary. If there is a PR on it, JTAC will be able to get that for you as it will require them to analyze clksyncd core dump. 

    Also, for pre-21.2 to post-21.2 upgrades, we recommend using no-validate because of FreeBSD changes. 21.2+ releases uses FreeBSD12 which uses system calls which do not exist on earlier freeBSDs. Please refer to the TSB: https://supportportal.juniper.net/s/article/Need-to-use-no-validate-option-when-upgrading-Junos-software-from-pre-Junos-21-2R1-to-Junos-version-21-2R1-or-later

    Thank you!



    ------------------------------
    Sougata Ray

    **Please note upgrade guidance might not be complete for all implementation/configurations. Before proceeding with an update please ensure you have tested in a lab environment and/or a backup copy of the original configuration. If urgent assistance is needed, please open a JTAC ticket (Only an option until July 1, 2023 for upgrading Junos 10-11-13).**
    ------------------------------

    Original Message