Recovery installation on EX9200
The recovery installation is used to restore the factory default installation in case the device software gets corrupted.
Once the software gets restored, the device will have the default configuration and it will be needed to either recreate manually the configuration that was running on the device prior the software corruption or to use a configuration backup.
For recovery installation, there are two steps required:
- Creating a bootable USB stick(the emergency boot device)
- Boot from USB stick and install the software
These are the steps required to create the bootable USB stick that will be used to boot the EX9200 from:
- Download the install media for the Junos release you want to install
- Plug in the blank USB and verify the mount point
- Copy the install media file to the USB stick using this command(this is applicable to Linux hosts, so you will need to adapt the command to the type of OS where the bootable USB is created):
dd if=install-media64-ex92xx-14.2R7.5-domestic of=/dev/sdb bs=16k
And you are set with the first step.
For the second step, just plug in the USB stick in the EX9200 RE and reboot the RE.
You just need to watch the console and let the device boot and install from USB.
This is how a boot and installation from USB looks like on console along with some key messages showing the stage of the USB boot and install process:
WARNING: History shows a reset caused by ,JXX, JNX reboot, Bit set: 2 ,JXX, JNX reboot, Bit set: 3 reset. Will try to boot from USB Flash Drive Compact Flash Solid State Drive 1 Solid State Drive 2 Network Trying to boot from USB Flash Drive C CD Loader 1.00 /builder@orE: is disk2 ] Building the boot loader arguments 8172 3629 4411 Relocating the loader and the BTX Starting the BTX loader Booting [/kernel]... platform_early_bootinit: M/T/EX Series Early Boot Initialization GDB: debug ports: sio GDB: current port: sio KDB: debugger backends: ddb gdb KDB: current backend: ddb 13369344K of memory above 4GB ignored Copyright (c) 1996-2016, 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 14.2R7.5 #0: 2016-08-07 00:18:13 UTC builder@orth.juniper.net:/volume/build/junos/14.2/release/14.2R7.5/obj/i386/junos/bsd/kernels/MFS/kernel link_elf: symbol ipv6_linklocal_hint undefined KLD file if_em.ko - could not finalize loading module_register: module pci/sfccb already exists! Module pci/sfccb failed to register: 17 module_register: module pci/sngcb already exists! Module pci/sngcb failed to register: 17 module_register: module pci/hdkcb_fabsw already exists! Module pci/hdkcb_fabsw failed to register: 17 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU C5518 @ 1.73GHz (1729.11-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106e4 Stepping = 4 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x9ce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT> AMD Features=0x28100000<NX,RDTSCP,LM> AMD Features2=0x1<LAHF> Cores per package: 8 Logical CPUs per core: 2 real memory = 17179869184 (16384 MB) avail memory = 3388334080 (3231 MB) Initializing M/T/EX platform properties .. cpu0 on motherboard pcib0: <Host to PCI bridge> pcibus 0 on motherboard pci0: <PCI bus> on pcib0 pcib1: <PCI-PCI bridge> mem 0xfb900000-0xfb90ffff irq 11 at device 3.0 on pci0 pci3: <PCI bus> on pcib1 pci3: <network, ethernet> at device 0.0 (no driver attached) pcib2: <PCI-PCI bridge> irq 11 at device 4.0 on pci0 pci4: <PCI bus> on pcib2 pci4: <network, ethernet> at device 0.0 (no driver attached) pcib3: <PCI-PCI bridge> irq 11 at device 5.0 on pci0 pci5: <PCI bus> on pcib3 pci5: <network, ethernet> at device 0.0 (no driver attached) pcib4: <PCI-PCI bridge> irq 11 at device 6.0 on pci0 pci6: <PCI bus> on pcib4 pcib5: <PCI-PCI bridge> irq 11 at device 0.0 on pci6 pci7: <PCI bus> on pcib5 acb0: <Atlas Enhanced Control Subsystem> mem 0xfba10000-0xfba103ff irq 11 at device 13.0 on pci7 acb0: acb: softc at 0xc7874040, fpga regs at 0xf949b000 spi: zl30143 clock initialized to 19.44 MHz spi: zl30130 clock module initialized besw0: <Broadcom BCM56680 GigE Switch> mem 0xfba00000-0xfba0ffff irq 11 at device 14.0 on pci7 pci0: <base peripheral> at device 8.0 (no driver attached) pci0: <base peripheral> at device 8.1 (no driver attached) pci0: <base peripheral> at device 8.2 (no driver attached) pci0: <base peripheral> at device 8.3 (no driver attached) pci0: <base peripheral> at device 9.0 (no driver attached) pci0: <base peripheral> at device 10.0 (no driver attached) pci0: <base peripheral> at device 10.1 (no driver attached) pci0: <base peripheral> at device 10.2 (no driver attached) pci0: <base peripheral> at device 10.3 (no driver attached) pci0: <base peripheral> at device 10.4 (no driver attached) pci0: <base peripheral> at device 10.5 (no driver attached) pci0: <base peripheral> at device 10.6 (no driver attached) pci0: <base peripheral> at device 10.7 (no driver attached) pci0: <base peripheral, interrupt controller> at device 11.0 (no driver attached) pci0: <base peripheral> at device 16.0 (no driver attached) pci0: <base peripheral> at device 16.1 (no driver attached) pci0: <base peripheral> at device 17.0 (no driver attached) ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfbe21000-0xfbe213ff irq 11 at device 29.0 on pci0 usb0: waiting for BIOS to give up control usb0: EHCI version 1.0 usb0: <EHCI (generic) USB 2.0 controller> on ehci0 usb0: USB revision 2.0 uhub0: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub0: 1 port with 1 removable, self powered uhub1: vendor 0x8087 product 0x0020, class 9/0, rev 2.00/0.00, addr 2 uhub1: single transaction translator uhub1: 8 ports with 8 removable, self powered umass0: Unigen Corporation PQS4000B8-JN28, rev 2.00/11.00, addr 3 pcib6: <PCI-PCI bridge> at device 30.0 on pci0 pci25: <PCI bus> on pcib6 gpio0: <GPIO controller> at device 31.0 on pci0 gpio_lpc_dev_init, Found bios device: 0x3b148086 atapci0: <GENERIC ATA controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5090-0x509f,0x5080-0x508f irq 11 at device 31.2 on pci0 ata0: <ATA channel 0> on atapci0 ata1: <ATA channel 1> on atapci0 ichsmb0: <Intel PCH SMBus controller> port 0x5000-0x501f mem 0xfbe20000-0xfbe200ff irq 11 at device 31.3on pci0 atapci1: <GENERIC ATA controller> port 0x5070-0x5077,0x5060-0x5063,0x5050-0x5057,0x5040-0x5043,0x5030-0x503f,0x5020-0x502f irq 11 at device 31.5 on pci0 ata2: <ATA channel 0> on atapci1 ata3: <ATA channel 1> on atapci1 isa0: <ISA bus> on motherboard orm0: <ISA Option ROMs> at iomem 0xc0000-0xc0fff,0xc1000-0xc1fff on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A sio3: configured irq 9 not in bitmap of probed irqs 0x80 sio3: port may not be enabled sio3 at port 0x2e8-0x2ef irq 9 on isa0 sio3: type 16550A virtual chassis member-id = 255 virtual chassis mode = 0 Initializing product: 149 .. acb: acb_late_attach: Initializing silabs clocks to drive 8727 external phy md0: Preloaded image </mdimg> 8730624 bytes at 0xc0c521a8 Timecounter "TSC" frequency 1729113936 Hz quality 800 ###PCB Group initialized for udppcbgroup ###PCB Group initialized for tcppcbgroup ad1: 30533MB <UGB94BPH32H0S1 KCI 2030> at ata0-master UDMA33 ad0: 3896MB <VRFCF14096DIHK1 091110stray irq7 > at ata0-slave UDMA33 Loading JUNOS chassis module chassis_init_hw_chassis_startup_time: chassis startup time 0.000000 Keda0 at umass-sim0 bus 0 target 0 lun 0 da0: <Unigen PQS4000 1100> Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 3824MB (7831552 512 byte sectors: 255H 63S/T 487C) rnel thread "wkupdaemon" (pid 41) exited prematurelTrying to mount root from cd9660:/dev/md0 y. ^@Disabling watchdog =================== Bootstrap installer starting =================== Initialized the environment Routing engine model is RE-S-EX9200-1800X4 HW model is Intel(R) Xeon(R) CPU C5518 @ 1.73GHz Discovered that flash disk = ad0 , hard disk = ad1 ** /dev/ad0s1a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3138 files, 298291 used, 1467501 free (117 frags, 183423 blocks, 0.0% fragmentation) ** /dev/ad0s1e ** Last Mounted on /config ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 11 files, 23 used, 196274 free (26 frags, 24531 blocks, 0.0% fragmentation) ** /dev/ad1s1a ** Last Mounted on /tmp/.snp3282/mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3117 files, 298267 used, 1467777 free (113 frags, 183458 blocks, 0.0% fragmentation) ** /dev/ad1s1e ** Last Mounted on /mnt/config ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3 files, 3 used, 196546 free (26 frags, 24565 blocks, 0.0% fragmentation) ** /dev/ad1s1f ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 998 files, 999796 used, 8293338 free (818 frags, 1036565 blocks, 0.0% fragmentation) Disk to install is ad0 ad1 mfs: available=6554560 hw.physmem: 3473809408 hw.usermem: 3445252096 hw.realmem: 3473809408 Using 6291456 for /tmp WARNING: The installation will erase the contents of your disks. Do you wish to continue (y/n)? y Setting ospackage=jboot-14.2R7.5.tgz, configpackage= Setting packlist=jbundle64-ex92xx-14.2R7.5-domestic.tgz Packages mounted from the install media Partitioning ad0 ... ******* Working on device /dev/ad0 ******* Installing disk label on ad0s1 Running newfs on ad0s1a...
The installation goes on and this is what you need to see just before the EX9200 goes for a reboot to finish the installation from USB:
Adding jroute... Unmounted /mnt/packages/mnt/jbase machdep.bootsuccess: 0 -> 1 machdep.nextbootdev: usb -> compact-flash Eject the installation media and hit [Enter] to reboot? Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `vnlru_mem' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...0 0 done syncing disks... All buffers synced. Uptime: 8m15s Normal shutdown (no dump device defined) Rebooting...
When the reboot is complete, the EX9200 should be functional:
root> show version Model: ex9204 Junos: 14.2R7.5 JUNOS Base OS boot [14.2R7.5]
And this is everything that you need to know about the recovery installation on EX9200.
I hope you found this information useful.
The following two tabs change content below.
Paris ARAU
Paris ARAU is a networking professional with strong background on routing and switching technologies. He is a holder of CCIE R&S and dual JNCIE(SP and ENT). The day to day work allows him to dive deeply in networking technologies. Part of the continuously training, he is focusing on Software Defined Network and cloud computing.
Latest posts by Paris ARAU (see all)
- Junos Fusion – Part IV – Satellite policies and uplink failure detection - 30 July 2018
- Junos Fusion – Part III – Satellite commands and traffic forwarding - 16 July 2018
- Junos Fusion – Part II – Configuration, Administration and Operation - 16 July 2018
- Junos Fusion – Part I – Overview, Components, Ports and Software - 11 July 2018
- Vagrant – Part IV – Network topology using Juniper and Cumulus - 26 April 2018
Comments
So empty here ... leave a comment!