[j-nsp] trying to upgrade OS on M5, getting "not compatible" error

Tue Jul 10 20:46:34 EDT 2007

Hey Mickey,

These messages are somewhat common when you skip a few releases. When
wearing my **testing** hat I use the "force" option, and when available
the "no-validate" switch, to make things happen when I see such
messages. I generally have success with this, especially when upgrading.
Sometimes on a downgrade your config will not be committed due to
unsupported statements. In some cases the release notes will inform that
you have to upgrade/downgrade to some intermediate version, but in the
case of 7.6R4.3 I saw no such instructions.

Definitely do a "request system snapshot" before attempting any upgrade,
if you have not already done so, to enable a reboot to existing
environment off of disk, should is be desired.

I believe that the "validate" option is the default when moving between
releases, and the 5.6 release does not seem to offer no-validate as a
choice.

Being that I was waiting for a test to complete, I went ahead and staged
a 5.6R2.4 to 7.6R4.3 upgrade on an m5, and all seems OK. Unfortunatley
this machine had no console access so only before/after.  Even so, being
that you are in a production environment I suggest that you contact jtac
to see if they have any specific instructions.

HTHs

regress at wiggum> show version 
Hostname: wiggum
Model: m5
JUNOS Base OS boot [5.6R2.4]
JUNOS Base OS Software Suite [5.6R2.4]
JUNOS Kernel Software Suite [5.6R2.4]
JUNOS Packet Forwarding Engine Support (M5/M10) [5.6R2.4]
JUNOS Routing Software Suite [5.6R2.4]
JUNOS Online Documentation [5.6R2.4]
JUNOS Crypto Software Suite [5.6R2.4]
KERNEL 5.6R2.4 #0 built by builder on 2003-02-14 23:22:39 UTC
. . .

regress at wiggum> request system software add
jinstall-7.6R4.3-domestic-signed.tgz force reboot 
Installing package
'/var/home/regress/jinstall-7.6R4.3-domestic-signed.tgz' ...
Verified MD5 checksum of jinstall-7.6R4.3-domestic.tgz
Adding jinstall...

WARNING:     This package will load JUNOS 7.6R4.3 software.
WARNING:     It will save JUNOS configuration files, and SSH keys
WARNING:     (if configured), but erase all other files and information
WARNING:     stored on this machine.  It will attempt to preserve dumps
WARNING:     and log files, but this can not be guaranteed.  This is the
WARNING:     pre-installation stage and all the software is loaded when
WARNING:     you reboot the system.

Saving the config files ...
Installing the bootstrap installer ...

WARNING:     A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use
the
WARNING:     'request system reboot' command when software installation
is
WARNING:     complete. To abort the installation, do not reboot your
system,
WARNING:     instead use the 'request system software delete jinstall'
WARNING:     command as soon as this operation completes.

Saving package file in /var/sw/pkg/jinstall-7.6R4.3-domestic-signed.tgz
...
Saving state for rollback ...
Rebooting ...
Reboot consistency check bypassed - jinstall 7.6R4.3 will complete
installation upon reboot
shutdown: [pid 3081]
Shutdown NOW!

*** FINAL System shutdown message from root at wiggum ***

System going down IMMEDIATELY

regress at wiggum> 

. . . .

wiggum (ttyp0)

login: login: regress
Password:

--- JUNOS 7.6R4.3 built 2007-02-09 23:21:08 UTC
% dmesg
Copyright (c) 1996-2001, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2004 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.
JUNOS 7.6R4.3 #0: 2007-02-09 23:21:08 UTC

builder at drakaina.juniper.net:/build/drakaina-c/7.6R4.3/obj-i386/sys/comp
ile/JUNIPER
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 331706894 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (331.71-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x66a  Stepping = 10

Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,MMX,FXSR>
real memory  = 268369920 (262080K bytes)
sio0: gdb debugging port
avail memory = 253669376 (247724K bytes)
Preloaded elf kernel "kernel" at 0xc06ea000.
DEVFS: ready for devices
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 14 entries at 0xc00fde70
DRAM Data Integrity Mode: Non-ECC
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> on motherboard
pci0: <PCI bus> on pcib0
isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 11
smb0: <Intel 82371AB SMB controller> port 0x5000-0x500f at device 7.3 on
pci0
pcic0: <TI PCI-1251B PCI-CardBus Bridge> mem 0xe6205000-0xe6205fff irq
15 at device 13.0 on pci0
pcic0: TI12XX PCI Config Reg: [pci only]
pccard0: <PC Card bus -- legacy version> on pcic0
pcic1: <TI PCI-1251B PCI-CardBus Bridge> mem 0xe6200000-0xe6200fff irq 7
at device 13.1 on pci0
pcic1: TI12XX PCI Config Reg: [pci only]
pccard1: <PC Card bus -- legacy version> on pcic1
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> port 0xd800-0xd83f mem
0xe6100000-0xe61fffff,0xe6204000-0xe6204fff irq 7 at device 16.0 on pci0
pcib1: <DEC 21150 PCI-PCI bridge> at device 17.0 on pci0
pci1: <PCI bus> on pcib1
fxp1: <Intel EtherExpress Pro 10/100B Ethernet> port 0xe000-0xe03f mem
0xe6000000-0xe60fffff,0xe6207000-0xe6207fff irq 10 at device 19.0 on
pci0
orm0: <Option ROMs> at iomem 0xc8000-0xc87ff,0xc9000-0xc97ff on isa0
ata2 at port 0x170-0x177,0x376 irq 15 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
vga0: <Generic ISA VGA> at port 0x3b0-0x3bb iomem 0xb0000-0xb7fff on
isa0
sc0: <System console> at flags 0x100 on isa0
sc0: MDA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0
sio0: type 16550A, console
sio1 at port 0x3e8-0x3ef irq 5 on isa0
sio1: type 16550A
sio2 at port 0x2f8-0x2ff irq 3 on isa0
sio2: type 16550A
sio3: configured irq 7 not in bitmap of probed irqs 0
fxp0: Ethernet address 00:a0:a5:12:25:b0
fxp1: Ethernet address 02:00:00:00:00:04
DEVFS: ready to run
ad0: 91MB <SanDisk SDCFB-96> [734/8/32] at ata0-master PIO1
ad1: 11513MB <IBM-DARA-212000> [23392/16/63] at ata0-slave UDMA33
Mounting root from ufs:/dev/ad0s1a
fxp1: link media UP 100Mb / full-duplex
TNP: version is changing to 1
TNP: adding neighbor 2 to interface fxp1.
fxp0: link media UP 100Mb / full-duplex
Microcode: Header revision 1, Date 5/5/1999, Platform Id 0x20
Microcode: updated from revision 0 to 11, date=05051999
mastership: routing engine 0 becoming master
TNP: adding neighbor 1 to interface fxp1.
cos_msg_red_drop_req_to_pfe: profile 0, err 0
rts_cos_red_drop_req_wait_and_reply red_drop_msg NULL to GETNEXT profile
0
setsockopt(RTS_ASYNC_NEED_RESYNC) ignored (pppd): client already active
%  cli
sho verregress at wiggum> show version 
Hostname: wiggum
Model: m5
JUNOS Base OS boot [7.6R4.3]
JUNOS Base OS Software Suite [7.6R4.3]
JUNOS Kernel Software Suite [7.6R4.3]
JUNOS Packet Forwarding Engine Support (M5/M10) [7.6R4.3]
JUNOS Routing Software Suite [7.6R4.3]
JUNOS Online Documentation [7.6R4.3]
JUNOS Crypto Software Suite [7.6R4.3]

regress at wiggum> 

regress at wiggum> show chassis alarms 
No alarms currently active

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Mickey Everts
> Sent: Tuesday, July 10, 2007 3:12 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] trying to upgrade OS on M5, getting "not 
> compatible" error
> 
> 
> I have an M5 which is running kind of an old version, JUNOS 5.6R2.4.  
> When I attempt to upgrade via this command:
> 
> request system software add validate reboot 
> /var/tmp/jinstall-7.6R4.3-domestic-signed.tgz
> 
> I received the following error...
> 
> WARNING: Current configuration not compatible with 
> /var/tmp/jinstall-7.6R4.3-domestic-signed.tgz
> 
> For the hell of it, I tried
> instead"jinstall-6.3R3.1-domestic-signed.tgz", but received 
> the same error. 
> 
> 
> What would be the best way to proceed?  We depend on this 
> router and need to keep downtime to a minimum.  The error 
> message is not exactly chock full of details.  What would 
> happen if I left off the "validate" 
> part of the command?
> 
> Thanks in advance for any help on this....
> 
> Mickey
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 