G350 SW image not updated

[f0netech]

My office is in the process of updating our branch office G350 in preparation for migrating our primary server.

Have had no issue with the majority, but there is one that is not playing nice. Copied the updated firmware to not active boot bank. Verified that copy completes, no fault messages. Set the boot bank to point to the updated copy, reset gateway and BOOM, every time the gateway boots to the older version.

Have tried various steps, copied the file again to assure no corruption, it is also the same file that was copied to multiple others during this process. Verified with show ima ver command that the corrected image is on the not active bank. Used show boot bank and it states that the non active bank is the boot bank. Reset using various method both in SA and putty. copy run start performed, but again every time the gateway is restarted, it comes up with the older software version.

Not sure what else to do, any suggestions?

 

[kyle555]

md5 checksum on the image vs what you're pushing to the 350?

Maybe try going through an intermediate firmware level first? If you're loading latest to boot bank B, try newest minus 2 to boot bank B and see if it'll boot that and put latest on A after?

 

[AvayaTier3]

what is the FW version you are upgrading to?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[f0netech]

Upgrading from 30.24.0 to 30.27.1

 

[AvayaTier3]

Hardware Platform for CM and CM software version / SP


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AvayaTier3]

Date: September 9, 2013
Target Board:  G350 Media Gateway
Firmware Vintage: V30.27.1 (5.2.1)


GENERAL:
Customer impacting gateway issues will be addressed in new firmware versions wit
hin each supported gateway firmware series (e.g., 30.xx.xx is considered a firmw
are series). This ensures customer impacting fixes will be delivered and availab
le within each supported gateway firmware series until end of manufacturer suppo
rt. The latest gateway firmware version within a given firmware series should be
 used since it will have all of the latest fixes. New gateway features and funct
ionality will not be supported in configurations running newer series of gateway
 firmware with older Communication Manager releases.

To help ensure the highest quality solutions for our customers, Avaya recommends
 use of like gateway firmware version series and Communication Manager releases.
 This means the latest version within the GW Firmware Series are recommended wit
h the following Communication Manager software releases:

GW Firmware series        Communication Manager Release
=========================================================
25.xx.xx                  3.x.x
26.xx.xx                  4.x.x
27.xx.xx                  5.0.x
28.xx.xx                  5.0.x or 5.1.x
29.xx.xx                  5.2.0
30.xx.xx                  5.2.1

Newer gateway firmware versions running with older Communication Manager softwar
e releases are still supported. For example, running gateway firmware version se
ries 30.xx.xx with Communication Manager 4.x.x is still supported. However, prol
onged running in this type of mixed configuration is not recommended. Avaya reco
mmends running in a mixed configuration only as long as necessary to support gat
eway upgrades prior to upgrading Communication Manager software. Newer Communica
tion Manager software releases running with older gateway firmware versions are
not supported.

Gateway firmware support follows the Communication Manager software end of manuf
acturer support model. This means that as soon as a Communication Manager releas
e goes end of manufacturer support, new gateway firmware will no longer be suppo
rted with that particular Communication Manager release. For example, when Commu
nication Manager 3.x.x goes end of manufacturer support, gateway firmware series
 25.xx.xx will no longer be supported, and any new versions of gateway firmware
in the latest series (e.g., 30.xx.xx) will not be supported with Communication M
anager 3.x.x releases.

CONTENTS:
        1) Statement of Applicability
        2) Pre Install Instructions
        3) File Download Instructions
        4) Known Problems
        5) Change History


++++++++++++++++++++++++++++
1) Statement of Applicability
++++++++++++++++++++++++++++

This version of firmware is only applicable for G350 Media Gateway Processor.


See details in "General" Section above.


++++++++++++++++++++++++++++
2) Pre Install Instructions
++++++++++++++++++++++++++++

Required:
    - Avaya Communication Manager must be running at least version 2.0
      for G350 to operate.

    - G350 Media Gateway hardware version 1 or greater

    - Browser Access to the Customer Support Web site ([URL unfurl="true"]http://support.avaya.com)[/URL]
,
      or another way to get the Target File.

    - FTP and TFTP applications on your PC or Local Computer.

    - Target Board: G350 Media Gateway hardware version 1 or greater

    - Inads, dadmin, craft or a customer login that has been enabled
      for system maintenance.


++++++++++++++++++++++++++++
3) File Download Instructions
++++++++++++++++++++++++++++

Before attempting a download, please read the section in the Installation
documentation titled "Upgrading / Downloading Software / Firmware".

PLEASE NOTE: To ensure a successful download, from the system access terminal
(SAT) or ASA, issue the command 'busyout board v#' before issuing 'copy tftp'
command.  Upon completion, from the SAT or ASA issue the command 'release board
v#'.


++++++++++++++++++++++++++++
4) Known Problems
++++++++++++++++++++++++++++

None.

++++++++++++++++++++++++++++
5) Change History
++++++++++++++++++++++++++++

The following issues were fixed in 30.27.1 since the previous 30.24.0 release:

Gateway will not register to CM after S8300 is rebooted.

MM710B doesn't get updated when Restore operation in performed.

Increase the uptime duration displayed by the "show system" CLI command so that
it only rollsover once every 497 days.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]