spa508 not applying config from $MAU config file

Sage Major · ‎03-07-2013

I have several 508's that are doing this

They read and apply the 508g.cfg config file from profile rule, but dont apply profile rule b. After a reboot it will apply rule b. Reboot again and it will apply only profile rule

<Profile_Rule group="Provisioning/Configuration_Profile">tftp://xxx/spa508G.cfg</Profile_Rule>

<Profile_Rule_B group="Provisioning/Configuration_Profile">tftp://xxx/spa/508/$MAU.xml</Profile_Rule_B>

Also I have the downgrade limit set but the firmware keeps trying download to 7.5.2b, even though it has 7.5.4 applied

<Downgrade_Rev_Limit group="Provisioning/Firmware_Upgrade">7.5.3</Downgrade_Rev_Limit>,

<Upgrade_Rule group="Provisioning/Firmware_Upgrade">

tftp://xxxx/spa/firmware/50x/spa50x-30x-7-5-2b.bin

</Upgrade_Rule>

Sage Major · ‎03-07-2013

Brought up a syslog and found more info

curent firmware

7.4.9c

upgrade rule

http://xxxxxxxx/spa/firmware/50x/spa50x-30x-7-5-2b.bin

I get a message that I can't downgrade below 7.5.3 even though I am trying to upgrade to 7.5.2b from 7.4.9c

16:14:38 fu:1:0c30e, 6.8 7.13 1

16:14:38 fu:1:0c201, 4.71 1

16:14:38 [0]UnRegOK

16:14:38 request reboot type=1 reason=Provisioning(4)

16:14:38 fu:1:0c17e, 5.1.9 5.1.12 5.1.14 5.1.19 1

16:14:38 FMM >>>> Failed upgrade

16:14:38 SPA508G a4:4c:11:9e:27:91 -- Upgrade failed: 12. corrupt file

16:14:29 ** New magic: SkOsMo5 fIrMwArE. Old magic: SkOsMo5 fIrMwArE

16:14:29 fprv_upgrade_from_buffer_priv(manual:0, buf: SkOsMo5 fIrMwArE, file_len: 4194816)

16:14:29 content len (pld) =4194816

16:14:19 [0]RegOK. NextReg in 29 (1)

16:13:56 [0]RegOK. NextReg in 29 (1)

16:13:33 [0]RegOK. NextReg in 29 (1)

16:13:10 [0]RegOK. NextReg in 29 (1)

16:13:00 FMM >>>> Requesting upgrade

16:13:00 SPA508G a4:4c:11:9e:27:91 -- Requesting upgrade tftp://xxxxxxxxxx/spa/firmware/50x/spa50x-30x-7-5-4.bin

16:13:00 SPA508G a4:4c:11:9e:27:91 -- Requesting upgrade tftp://xxxxxxxxx/spa/firmware/50x/spa50x-30x-7-5-4.bin

fu:1:0bfc1, 5.1.9 1

FMM >>>> Failed upgrade

SPA508G a4:4c:11:9e:27:91 -- Upgrade failed: downgrade to revision earlier than 7.5.3 not allowed

** New magic: SkOsMo5 fIrMwArE. Old magic: SkOsMo5 fIrMwArE

fprv_upgrade_from_buffer_priv(manual:0, buf: SkOsMo5 fIrMwArE, file_len: 4147359)

content len (pld) =4147359

[0]RegOK. NextReg in 29 (1)

content len (hdr) =4147359

FMM >>>> Requesting upgrade

SPA508G a4:4c:11:9e:27:91 -- Requesting upgrade http://xxxxxxxxxx/spa/firmware/50x/spa50x-30x-7-5-2b.bin

Dan Miley · ‎03-11-2013

it seems your upgrade config is telling the device don't go below 7,5,3, but then install 7.5.2b??

I'd set this to 7.5.2b or make it empty...

<<

7.5.3,>>

Downgrade_Rev_Limit Enforces a lower limit on the acceptable

version number during a firmware upgrade or

downgrade. The device does not complete a

firmware upgrade operation unless the

firmware version is greater than or equal to this

parameter.

To upgrade phone to 7.52b before other upgrade, you need a conditional, to only upgrade if the software version is less than 7.52b..

<<

tftp://xxxx/spa/firmware/50x/spa50x-30x-7-5-2b.bin

>>

Syntax to tell if software version is less than 7.5.2b then (the ? ) do the tftp....

($SWVER lt 7.5.2b) ? http://10.41.22.99/spa50x-30x-7-5-2b.bin

or to get to the latest, this should work to do both stages from 7.4.9

($SWVER lt 7.5.2b) ? http://10.41.22.99/spa50x-30x-7-5-2b.bin | ($SWVER lt 7.5.4) ? http://10.41.22.99/spa50x-30x-7-5-4.bin

Test in your lab to make sure it works before rolling out to your customers...

The full provisioning guide is here

http://www.cisco.com/en/US/docs/voice_ip_comm/csbpvga/spa100-200/provisioning/guide/SPA100-200_PG_78-20952.pdf

all the syntax, and config is there.

Dan.