SRX

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
Expand all | Collapse all

SRX300 TFTP Method to upgrade and loader

  • 1.  SRX300 TFTP Method to upgrade and loader

    Posted 05-31-2023 15:30

    Hello All,

    I am looking for SRX300 upgrade U-Boot and Loader using TFTP method. But I do not have latest boot loader binaries. Anyone who knows it, please let me know.

    Appreciate your help!



    ------------------------------
    PRACHI GADEKAR
    ------------------------------


  • 2.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 06-01-2023 11:40

    Hi Prachi,

    BIOS files are included in Junos itself. There is no need to use external files. You can check which BIOS is installed and which is available to install with your current Junos release using the command "show system firmware". Newer Junos releases may be shipped with newer BIOS versions included, available to install.

    If a new BIOS is available, you can install it using "request system firmware upgrade re bios" and for the backup bios use "request system firmware upgrade re bios backup". Use "show system firmware" during upgrade to monitor if the upgrade went well.

    Regards,

    Casper



    ------------------------------
    Casper Rijnders
    ------------------------------



  • 3.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 06-01-2023 14:34

    Hi Casper,

    I appreciate your reply. At present I can access only U-boot and loader prompts, unable to access Shell.

    sharing SRX300 details after I use Install command is as below.

    Octeon srx_300_ram# reset

    SPI stage 1 bootloader (Build time: May  3 2016 - 23:48:30)
    early_board_init: Board type: SRX_300

    U-Boot 2013.07-JNPR-3.1 (Build time: May 03 2016 - 23:48:31)

    SRX_300 board revision major:1, minor:12, serial #: CV2918AF0150
    OCTEON CN7020-AAP pass 1.2, Core clock: 1200 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
    Base DRAM address used by u-boot: 0x10fc00000, size: 0x400000
    DRAM: 4 GiB
    Clearing DRAM...... done
    Using default environment

    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    Found valid SPI bootloader at offset: 0x90000, size: 1481840 bytes


    U-Boot 2013.07-JNPR-3.1 (Build time: May 03 2016 - 23:50:19)

    Using DRAM size from environment: 4096 MBytes
    checkboard siege
    SATA0: not available
    SATA1: not available
    SATA BIST STATUS = 0x0
    SRX_300 board revision major:1, minor:12, serial #: CV2918AF0150
    OCTEON CN7020-AAP pass 1.2, Core clock: 1200 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
    Base DRAM address used by u-boot: 0x10f000000, size: 0x1000000
    DRAM: 4 GiB
    Clearing DRAM...... done
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    PCIe: Port 0 link active, 1 lanes, speed gen2
    PCIe: Link timeout on port 1, probably the slot is empty
    PCIe: Port 2 not in PCIe mode, skipping
    Net:   octeth0
    Interface 0 has 1 ports (SGMII)
    Type the command 'usb start' to scan for USB storage devices.

    Boot Media: eUSB usb
    Found TPM SLB9660 TT 1.2 by Infineon
    TPM initialized
    Hit any key to stop autoboot:  0
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    SF: 1048576 bytes @ 0x200000 Read: OK
    ## Starting application at 0x8f0000a0 ...
    Consoles: U-Boot console
    Found compatible API, ver. 3.1
    USB1:
    Starting the controller
    USB XHCI 1.00
    scanning bus 1 for devices... 2 USB Device(s) found
    USB0:
    Starting the controller
    USB XHCI 1.00
    scanning bus 0 for devices... 1 USB Device(s) found
           scanning usb for storage devices... 1 Storage Device(s) found

    FreeBSD/MIPS U-Boot bootstrap loader, Revision 2.11
    (builder@monarth, Sun Jul 26 18:59:02 PDT 2020)
    Memory: 4096MB
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    [6]Booting from eUSB slice 3
    \
    can't load '/kernel'
    can't load '/kernel.old'
    Press Enter to stop auto bootsequencing and to enter loader prompt.


    Type '?' for a list of commands, 'help' for more detailed help.
    loader> install tftp://192.168.100.10/junos-srxsme-21.1R1.11.tgz
    Target device selected for installation: internal media
    BCM MDK initializing ...
    BCM MDK init done.
    octeth0: Up 1000 Mbps Full duplex (port  0) (SGMII)
    /kernel data=0x101599c+0x1d3e60 pkg_seek: negative file seek (-1266)

    lseek failed

    Kernel entry at 0x801000c0 ...
    init regular console
    Primary ICache: Sets 16 Size 128 Asso 39
    Primary DCache: Sets 8 Size 128 Asso 32
    Secondary DCache: Sets 1024 Size 128 Asso 4
    CIU_FUSE 0x3/0x3
    GDB: debug ports: uart
    GDB: current port: uart
    KDB: debugger backends: ddb gdb
    KDB: current backend: ddb
    kld_map_v: 0x8ff80000, kld_map_p: 0x0
    Running in PARTITIONED TLB MODE
    Copyright (c) 1996-2021, Juniper Networks, Inc.
    All rights reserved.
    Copyright (c) 1992-2007 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
            The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    JUNOS 21.1R1.11 #0: 2021-03-18 20:48:46 UTC
        builder@qnc-jre-emake1t.juniper.net:/volume/build/junos/21.1/release/21.1R1.11/obj/octeon/junos/bsd/kernels/JSRXNLE/kernel
    can't re-use a leaf (perf_mon)!
    can't re-use a leaf (threshold)!
    can't re-use a leaf (debug)!
    JUNOS 21.1R1.11 #0: 2021-03-18 20:48:46 UTC
        builder@qnc-jre-emake1t.juniper.net:/volume/build/junos/21.1/release/21.1R1.11/obj/octeon/junos/bsd/kernels/JSRXNLE/kernel
    real memory  = 4294967296 (4194304K bytes)
    avail memory = 3511005184 (3348MB)
    FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    Security policy loaded: Junos MAC/veriexec (mac_veriexec)
    Security policy loaded: JUNOS MAC/pcap (mac_pcap)
    Security policy loaded: JUNOS MAC/runasnonroot (mac_runasnonroot)
    MAC/veriexec fingerprint module loaded: SHA1
    MAC/veriexec fingerprint module loaded: SHA256
    netisr_init: forcing maxthreads from 4 to 2
    random: <Software, Yarrow> initialized
    cpu0 on motherboard
    : CAVIUM's OCTEON 70XX/71XX CPU Rev. 0.2 with no FPU implemented
            L1 Cache: I size 78kb(128 line), D size 32kb(128 line), thirty two way.
            L2 Cache: Size 512kb, 4 way
    obio0 on motherboard
    uart0: <Octeon-16550 channel 0> on obio0
    uart0: console (9600,n,8,1)
    twsi0 on obio0
    set clock 0x49
    xhci0: <Cavium Octeon 7xxx xHCI Host Driver> on obio0
    usb0: <USB bus for xHCI Controller> on xhci0
    usb0: USB revision 3.0
    uhub0: vendor 0x0000 XHCI root hub, class 9/0, rev 3.00/1.00, addr 1
    uhub0: 2 ports with 2 removable, self powered
    xhci1: <Cavium Octeon 7xxx xHCI Host Driver> on obio0
    usb1: <USB bus for xHCI Controller> on xhci1
    usb1: USB revision 3.0
    uhub1: vendor 0x0000 XHCI root hub, class 9/0, rev 3.00/1.00, addr 1
    uhub1: 2 ports with 2 removable, self powered
    cpld0 on obio0
    pcib0: <Cavium on-chip PCIe HOST bridge> on obio0
    Disabling Octeon big bar support
    pcib0: Initialized controller
    pci0: <PCI bus> on pcib0
    pci0: <network, ethernet> at device 0.0 (no driver attached)
    pci0: <network, ethernet> at device 0.1 (no driver attached)
    gblmem0 on obio0
    octpkt0: <Octeon RGMII> on obio0
    boot_bus0 on obio0
    cfi0: <Macronix MX25L64 - 8MB> on boot_bus0
    cfi1: <Macronix MX25L64 - 8MB> on boot_bus0
    umass0: ATP Electronics ATP CG eUSB, rev 2.00/11.00, addr 2
    octpkt_attach: Initializing octpkt0 interface
    Timecounter "mips" frequency 1200000000 Hz quality 0
    md0: Preloaded image </isofs-install-srxsme> 32843776 bytes at 0x812e97fc
    da0 at umass-sim0 bus 0 target 0 lun 0
    da0: <ATP ATP CG eUSB 1100> Fixed Direct Access SCSI-4 device
    da0: 40.000MB/s transfers
    da0: 7672MB (15712256 512 byte sectors: 255H 63S/T 978C)
    random: unblocking device.
    hwpmc: OCTEON/4/64/0x1ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA>
    Trying to mount root from cd9660:/dev/md0
    WARNING: preposterous time in file system
    WARNING: clock 13118 days greater than file system time
    tty: not found
    Starting JUNOS installation:
        Source Package: net0:/junos-srxsme-21.1R1.11.tgz
        Target Media  : internal
        Product       : srx300
    add default: gateway 192.168.1.2
    PING 192.168.100.10 (192.168.100.10): 56 data bytes
    64 bytes from 192.168.100.10: icmp_seq=0 ttl=128 time=1.618 ms

    --- 192.168.100.10 ping statistics ---
    1 packets transmitted, 1 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 1.618/1.618/1.618/0.000 ms
    Computing slice and partition sizes for /dev/da0 ...
    media 7672 root 600 var 5151 cfg 191 swap 1030 800
    Attempting to save existing configuration...
    Could not find any existing configuration.
    Formatting target media /dev/da0 ...
    Preparing to create slices on /dev/da0
    /dev/da0: 15712256 sectors [C:978 H:255 S:63 SS:512]
    Shrinking slice 1 by 8116 blocks for alignment
    Shrinking slice 2 by 7860 blocks for alignment
    Shrinking slice 3 by 151 blocks for alignment
    Shrinking slice 4 by 686 blocks for alignment
    1+0 records in
    1+0 records out
    512 bytes transferred in 0.000194 secs (2638186 bytes/sec)
    Creating slices:
    g c978 h255 s63
    p 1    0xA5 256 1220684
    p 2    0xA5 1220940 1220940
    p 3    0xA5 2441880 10940265
    p 4    0xA5 13382145 2329425
    a 1
    ******* Working on device /dev/da0 *******
    fdisk: WARNING: adjusting start offset of partition 1
        from 256 to 315, to fall on a head boundary
    fdisk: WARNING: adjusting size of partition 1 from 1220684 to 1220625
        to end on a cylinder boundary
    Computing layout of partitions in /dev/da0s1...
    Shrinking partition a by 15750 blocks for alignment
    Labeling /dev/da0s1:
    bsdlabel: write to disk label supressed - label was as follows:
    # /dev/da0s1:
    8 partitions:
    #        size   offset    fstype   [fsize bsize bps/cpg]
      a:  1204619      256    unused        0     0
      c:  1220625        0    unused        0     0         # "raw" part, don't edit
    Ignoring watchdog timeout during boot/reboot
    Ignoring watchdog timeout during boot/reboot
    xhci0: ERROR! xhci_timeout: transfer timeout, id 62.
    0x801778e4+0x124 (0xc75bd800,0xc760b1d0,0xd8e11f05,0x13c0301) ra 0x80178c10 sz 64
    0x80178b38+0xd8 (0xc75bd800,0xc760b1d0,0xd8e11f05,0x13c0301) ra 0x8017a760 sz 64
    0x8017a4c0+0x2a0 (0xc75bd800,0xc760b1d0,0xd8e11f05,0x13c0301) ra 0x80aa8dcc sz 32
    mips_handle_this_interrupt+0x8c (0xc75bd800,0xc760b1d0,0xd8e11f05,0x13c0301) ra 0x80aa8e58 sz 40
    mips_handle_interrupts+0x58 (0xc75bd800,0xc760b1d0,0xd8e11f05,0x13c0301) ra 0x80aa9304 sz 48
    mips_interrupt+0x2ac (0xc75bd800,0xc760b1d0,0xd8e11f05,0x13c0301) ra 0x80e3e964 sz 32
    MipsKernIntr+0x140 (0x80f70000,0x812a58e0,0xffff8010,0xffff8010) ra 0x80aa6da4 sz 368
    cpu_idle+0x10 (0x80f70000,0x812a58e0,0xffff8010,0xffff8010) ra 0x80205fa0 sz 24
    0x80205d94+0x20c (0x80f70000,0x812a58e0,0xffff8010,0xffff8010) ra 0x8020052c sz 48
    fork_exit+0x258 (0x80f70000,0x812a58e0,0xffff8010,0xffff8010) ra 0x80e3f660 sz 48
    MipsNMIException+0x30 (0x80f70000,0x812a58e0,0xffff8010,0xffff8010) ra 0 sz 0
    pid 25, process: idle: cpu0
    cpu:0-Trap cause = 3 (TLB miss (store) - kernel mode)
    badvaddr = 0x1010, pc = 0x80177a08, ra = 0x80178c10, sr = 0x508008a3
    [thread pid 25 tid 100022 ]
    Stopped at      register_ucomdev_methods+0x1480:        sw      zero,16(s0)
    db> continue
    panic: trap
    cpuid = 0
    KDB: stack backtrace:
    SP 0: not in kernel
    0+0x0 (0,0,0,0) ra 0 sz 0
    pid 25, process: idle: cpu0
    ###Entering boot mastership relinquish phase
    KDB: enter: panic
    [thread pid 25 tid 100022 ]
    Stopped at      kdb_enter+0x810:        lui     a0,0x80e6



    ------------------------------
    PRACHI GADEKAR
    ------------------------------



  • 4.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 06-02-2023 06:19

    Hi Prachi,

    The Junos install from TFTP starts correctly, but fails due to "xhci0: ERROR! xhci_timeout: transfer timeout, id 62".

    That is a USB related hardware failure.

    In case you have a USB stick inserted (doesn't look like it from the boot log), then you can remove it and try again. Otherwise, this is a hardware defect and I'd recommend to replace / RMA the device.



    ------------------------------
    Casper Rijnders
    ------------------------------



  • 5.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 06-05-2023 11:42

    Hi,

    Casper, you mentioned it is a USB related error, but while using TFTP , i do not plug USB to device. Also If I try separately to install using USB, it detects installable from USB. so not sure what is that error for.

    Secondly, RMA is not possible for me to go ahead for and hence I posted my problem on this community.

    let me know it any other work around is there.

    Thanks,

    Prachi 



    ------------------------------
    PRACHI GADEKAR
    ------------------------------



  • 6.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 10-06-2023 10:43

    Hello, did you manage to solve the problem in some way? I'm having the same problem and I can't boot neither from USB nor from tftp...



    ------------------------------
    FRANCESCO PASQUALETTI
    ------------------------------



  • 7.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 10-07-2023 16:03

    Hi Francesco,

    Unfortunately, my issue still not resolved.  It will be great if your issue resolves and you share the way to resolve the issue. I always get Kernel related error .



    ------------------------------
    PRACHI GADEKAR
    ------------------------------



  • 8.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 10-08-2023 20:11

    I have two possible suggestions.

    For the tftp install see if the additional parameter no-validate can be added to the install command to bypass and ignore errors.

    If you have a working device, create a bootable usb snapshot on this device. 

    Then to that usb add a copy of the full installer file in the var/tmp or other user directory.

    Boot the damaged device from the USB and install to the internal media from the usb using the format option to check and clean the internal disk in the process.



    ------------------------------
    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
    http://puluka.com/home
    ------------------------------



  • 9.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 10-09-2023 03:49

    When the device starts in octeon mode, it means hardware error most of the times. It visible from the log you attached, that the device is unable to find HDD.

    I don't know if you can replace the HDD but yourself, we usually RMA, or bin devices like this.



    ------------------------------
    BALAZS KISS
    ------------------------------



  • 10.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 11-21-2023 08:30

    since my problem was not resolved , we landed up getting new device.  New device works Fantastic. Let me know if is possible to correct old device by transferring image from new on eto old one, if yes , please let me know , how can we do it.



    ------------------------------
    PRACHI GADEKAR
    ------------------------------



  • 11.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 11-21-2023 08:49

    Hi,

    You can install junos from USB / from TFTP in u-boot and loader : https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/index.html

    Hopefully one of the methods will work, but as I mentioned to you earlier, when the device starts in Octeon mode it usually means hardware error.



    ------------------------------
    BALAZS KISS
    ------------------------------



  • 12.  RE: SRX300 TFTP Method to upgrade and loader

    Posted 11-21-2023 09:13

    If you have a working device of the same model you could do the following process.  If there is a hardware issue other than the internal disk format or damage it would still fail.

    Create a bootable USB on the working device by making a snapshot to the USB

    Copy an install file of the same version onto this created USB drive

    Insert this USB into the damaged device and boot to this image.

    Perform a format install of the version from the USB to the internal drive



    ------------------------------
    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
    http://puluka.com/home
    ------------------------------