Junos OS

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about Junos OS.
  • 1.  Electrical Reboot with Configuration Loss ACX2200

    Posted 07-18-2024 04:34

    Hello

    We faced electrical shutdown on 2 ACX2200 wich caused a reboot of both of the equipments.

    During this reboot, the configuration automaticaly loaded by the equipement was and old and osbolete configuration and Junos software.

    you will have a log 

    root@rie-gp-police-r01> show chassis alarms no-forwarding
     
     
     
    2 alarms currently active
     
    Alarm time               Class  Description
     
    2024-07-15 05:36:12 UTC  Minor  Host 0 Boot from backup root***********************
     
    2024-07-15 05:36:12 UTC  Major  Host 0 fxp0 : Ethernet Link Down
     
     
     
     
     
    ********************************************
     
    ==
     
     
     
     
     
    root@rie-gp-police-r01> show system commit
     
     
     
    0   2024-04-19 02:14:12 UTC by apierre via cli
     
        upgrade RIE GP -dino n°808417
     
    1   2023-06-07 09:15:31 UTC by jguillou via cli
     
    2   2023-06-07 09:14:59 UTC by jguillou via cli commit confirmed, rollback in 10mins==>  dernière commit
     
    3   2022-11-17 22:09:44 UTC by apierre via cli
     
     
     
    ******************************************************
     
     
     
     
     
    root@rie-gp-police-r01> show chassis routing-engine no-forwarding
     
     
     
    Routing Engine status:
     
        Temperature                 44 degrees C / 111 degrees F
     
        DRAM                      1536 MB (2048 MB installed)
     
        Memory utilization          41 percent
     
        5 sec CPU utilization:
     
          User                      24 percent
     
          Background                 0 percent
     
          Kernel                    32 percent
     
          Interrupt                  1 percent
     
          Idle                      44 percent
     
        1 min CPU utilization:
     
          User                       2 percent
     
          Background                 0 percent
     
          Kernel                     4 percent
     
          Interrupt                  0 percent
     
          Idle                      93 percent
     
        5 min CPU utilization:
     
          User                       1 percent
     
          Background                 0 percent
     
          Kernel                     2 percent
     
          Interrupt                  0 percent
     
          Idle                      96 percent
     
        15 min CPU utilization:
     
          User                       1 percent
     
          Background                 0 percent
     
          Kernel                     2 percent
     
          Interrupt                  0 percent
     
          Idle                      96 percent
     
        Model                          RE-ACX-2200
     
        Serial ID                      PX0220220007
     
        Start time                     2024-07-15 05:32:26 UTC
     
        Uptime                         15 hours, 15 minutes, 30 seconds
     
        Last reboot reason             Router rebooted after a normal shutdown.*************
     
        Load averages:                 1 minute   5 minute  15 minute
     
                                           0.08       0.04       0.01
     
     
     
     
     
     
     
    ===============================
     
     
     
     
     
    root@rie-gp-police-r01> show system uptime no-forwarding
     
     
     
    Current time: 2024-07-15 20:47:55 UTC
     
    Time Source:  LOCAL CLOCK
     
    System booted: 2024-07-15 05:32:26 UTC (15:15:29 ago)
     
    Protocols started: 2024-07-15 05:36:08 UTC (15:11:47 ago)
     
    Last configured: 2024-04-19 02:14:12 UTC (12w3d 18:33 ago) by apierre==è
     
     
     
    8:47PM  up 15:15, 1 user, load averages: 0.08, 0.04, 0.01

    please how i can resolve the problem fo ACX2200

    regards 

    Regards 



    ------------------------------
    Dhikra Marghli
    ------------------------------


  • 2.  RE: Electrical Reboot with Configuration Loss ACX2200

    Posted 07-18-2024 04:38

    Hello

    i wait a reply

    regards



    ------------------------------
    Dhikra Marghli
    ------------------------------



  • 3.  RE: Electrical Reboot with Configuration Loss ACX2200

    Posted 07-18-2024 07:58

    also  i add :

    root@rie-gp-police-r02> show system boot-messages  no-forwarding
     
    platform_early_bootinit: MX-PPC Series Early Boot Initialization
    mxppc_set_re_type: hw.board.type is ACX-2200
    WDOG initialized
    Copyright (c) 1996-2018, 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 17.4R2.4 #0: 2018-08-17 01:01:28 UTC
        builder@landvaettur:/volume/build/junos/17.4/release/17.4R2.4/obj/powerpc/junos/bsd/kernels/JUNIPER-PPC/kernel
    WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
    Timecounter "decrementer" frequency 62500000 Hz quality 0
    cpu0: Freescale e500v2 core revision 5.1
    cpu0: HID0 80004000<EMCP,TBEN>
    real memory  = 1580204032 (1507 MB)
    avail memory = 1548742656 (1476 MB)
    Security policy loaded: JUNOS MAC/pcap (mac_pcap)
    Security policy loaded: JUNOS MAC/runasnonroot (mac_runasnonroot)
    Security policy loaded: Junos MAC/veriexec (mac_veriexec)
    MAC/veriexec fingerprint module loaded: SHA1
    MAC/veriexec fingerprint module loaded: SHA256
    netisr_init: forcing maxthreads from 4 to 1
    ETHERNET SOCKET BRIDGE initialising
    random: <Software, Yarrow> initialized
    Initializing M/T/EX platform properties ..
    nexus0: <Powerpc Nexus device>
    ocpbus0: <on-chip peripheral bus> on nexus0
    openpic0: <OpenPIC in on-chip peripheral bus> iomem 0xf7f40000-0xf7f600b3 on ocpbus0
    uart0: <16550 or compatible> iomem 0xf7f04500-0xf7f0450f irq 58 on ocpbus0
    uart0: console (9600,n,8,1)
    uart1: <16550 or compatible> iomem 0xf7f04600-0xf7f0460f irq 58 on ocpbus0
    lbc0: <Freescale Local Bus Controller> iomem 0xf7f05000-0xf7f05fff,0xf8000000-0xffffffff irq 17,16 on ocpbus0
    cfi0: <AMD/Fujitsu - 8MB> iomem 0xffc00000-0xffffffff on lbc0
    fsyspld0 iomem 0xfef00000-0xfef00fff on lbc0
    ramdev0 iomem 0xfee1f000-0xfee1ffff on lbc0
    i2c0: <MPC85XX OnChip i2c Controller> iomem 0xf7f03000-0xf7f03014 irq 59 on ocpbus0
    8564 rtc0: <8564 RTC> on i2c0
    USB2513i usb hub0: <USB2513Bi usb hub> on i2c0
    tsec0: <eTSEC ethernet controller> iomem 0xf7f24000-0xf7f24fff irq 45,46,50 on ocpbus0
    tsec0: hardware MAC address 50:c7:09:88:de:7f
    miibus0: <MII bus> on tsec0
    brgphy0: <BCM54610 10/100/1000baseTX PHY> on miibus0
    brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
    tsec1: <eTSEC ethernet controller> iomem 0xf7f25000-0xf7f25fff irq 51,52,56 on ocpbus0
    tsec1: hardware MAC address 50:c7:09:88:de:7e
    miibus1: <MII bus> on tsec1
    gentbi0: <Generic ten-bit interface> on miibus1
    gentbi0:  1000baseSX-FDX, 1000baseT-FDX, auto
    ehci0: <Frescale Integrated USB 2.0 controller> iomem 0xf7f22000-0xf7f22503 irq 44 on ocpbus0
    usb0: EHCI version 1.0
    usb0 on ehci0
    usb0: USB revision 2.0
    uhub0: Freescale EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
    uhub0: 1 port with 1 removable, self powered
    uhub1: SMSC USB2513Bi, class 9/0, rev 2.00/b.a0, addr 2
    uhub1: multiple transaction translators
    uhub1: 3 ports with 3 removable, self powered
    ehci_activate_qh: unexpected next ptr
    QH(0xcdb8ed80) at 0x5d86cd80:
      sqtd=0xcdb8fde0 inactivesqtd=0xcdb8fcc0
      link=0x5d87bba2<QH>
      endp=0x80012102
        addr=0x02 inact=0 endpt=1 eps=2 dtc=0 hrecl=0
        mpl=0x1 ctl=0 nrl=8
      endphub=0x40811c01
        smask=0x01 cmask=0x1c huba=0x01 port=1 mult=1
      curqtd=0x00000001<T>
    Overlay qTD:
      next=0x5d86bcc0<> altnext=0x00000001<T>
      status=0x00000000: toggle=0 bytes=0x0 ioc=0 c_page=0x0
        cerr=0 pid=0 stat=0x0
      buffer[0]=0x00000000
      buffer[1]=0x00000000
      buffer[2]=0x00000000
      buffer[3]=0x00000000
      buffer[4]=0x00000000
    QTD(0xcdb8fde0) at 0x5d86bde0:
      next=0x5d86bcc0<> altnext=0x5d86bcc0<>
      status=0x00208d00: toggle=0 bytes=0x20 ioc=1 c_page=0x0
        cerr=3 pid=1 stat=0x0
      buffer[0]=0x002fc75c
      buffer[1]=0x00000000
      buffer[2]=0x00000000
      buffer[3]=0x00000000
      buffer[4]=0x00000000
    QTD(0xcdb8fcc0) at 0x5d86bcc0:
      next=0x00000001<T> altnext=0x00000001<T>
      status=0x00000000: toggle=0 bytes=0x0 ioc=0 c_page=0x0
        cerr=0 pid=0 stat=0x0
      buffer[0]=0x00000000
      buffer[1]=0x00000000
      buffer[2]=0x00000000
      buffer[3]=0x00000000
      buffer[4]=0x00000000
    umass0: vendor 0x13fe USB DISK 2.0, rev 2.00/1.00, addr 3
    umass0: SCSI over Bulk-Only; quirks = 0x0000
    umass0:0:0:-1: Attached to scbus0
    Initializing product: 154 ..
    Setting up M/T interface operations and attributes
    Initializing MX-PPC platform mastership..
    Registering tcp_platform_dependent = tcp_handle_special_ports
    da0 at umass-sim0 bus 0 target 0 lun 0
    da0: < USB DISK 2.0 PMAP> Removable Direct Access SCSI-6 device
    da0: 40.000MB/s transfers
    da0: 7644MB (15654912 512 byte sectors: 255H 63S/T 974C)
    random: unblocking device.
    Kernel thread "wkupdaemon" (pid 53) exited prematurely.
    Trying to mount root from ufs:/dev/da0s1a

    =====>  i want a solution that i can resolve this problem of lost of configuration and version 



    ------------------------------
    Dhikra Marghli
    ------------------------------



  • 4.  RE: Electrical Reboot with Configuration Loss ACX2200

    Posted 07-18-2024 19:38

    This problem occurs when the power loss boot/reboot corrupts the running primary disk partition and boot is not longer possible.

    As a result the device boots from the backup disk partition.

    The backup partition must be kept in sync with the primary partition using the Junos snapshot command or adding configuration to auto generate a snapshot when configuration changes occur.  The basic command from the operational prompt on ACX is

    request system snapshot slice alternate

    ACX snapshot documentation is here.

    https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/topics/topic-map/configure-root-partitions-acx.html



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