cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2568
Views
0
Helpful
10
Replies

Trouble with 4305G firmware/kernel update

Tiberie Kirijas
Level 1
Level 1

Hi forum,

I've searched this forum for similar case, but could not find answer.

I have firmware and kernel update files for the DMP 4305G (5.2.0_FCS_4305.fwimg & DMPkernel_A2_4305.tivella) and tried every known way to me, to upgrade the DMP but without success.

We have DMS 5.2. I've tried upgrading through the DMM, DMM-DSM and even with IIS web server which i found as way to upgrade on this forum, but still no joy.

To be more specific, the try with the IIS web server, I uploaded the file to the root folder and used this example below:

(http://10.10.10.2:7777/set_param?mng.command=start+upgrade+kernel+http://10.10.10.10/DMPkernel_A1_4300.tivella) I only got an window to enter the username and password of the DMP and afterwards  nothing happend.

I have double checked that the DMP has the IP address of the DMM in Centralized Management, DMM-DSM Server timeout set to 300 sec, DMP Web account same as the user/pass in DMM, DMP Service account same user/pass and FTP enabled also.

The odd thing is that in DMM, it shows the 4305G as registered for a while, but after some time it registers out, and the status changes to red X . For this brief period i tired to upgrade the DMP from the Action drop-down menu though it did not do anything.

I know that the kernel should be aplied first and then the firmware. For sake of argument, I've upgraded the 4400G firmware through the DMM with no problem at all.

The exact model name is: DMP-4305G-5.1-K9

If you need me to upload and/or add additional info to this question, do tell.

Any input will be much appriciated!

Tiberie

1 Accepted Solution

Accepted Solutions

Ok, I tested a DMP-4305G here that was on 5.0. 

I upgraded for 5.0 to 5.1 first.  The upgrade was successful.

I then upgraded for 5.1 to 5.2.  The upgrade was successful.

You may need to capture a sniffer trace to see what is

going on.  And use the same steps and legends that i use

to verify everything in your setup.

T.

RECREATE NOTES:

===============


DMP        = 10.10.10.10

WEB Server = 20.20.20.20

      User = admin

  Password = default


Web Server = Apache (I do not use IIS)


5.1 Web Server Directory = Software/dms-images/DMP-images/5.1/

5.1 Firmware Kernel file = DMPkernel_A1_4305.tivella


5.2 Web Server Directory = Software/dms-images/DMP-images/5.2/FCS/5.2.0_FCS_4305/

5.2 Firmware Kernel file = DMPkernel_A2_4305.tivella

*** UPGRADE KERNEL FROM 5.0 to 5.1 ***

STEP#1

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (alexr@heritage) (gcc version 3.3.2) #1 Fri Oct 19 11:00:01 PDT 2007

STEP#2

http://admin:default@10.10.10.10:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F20.20.20.20%2FSoftware%2Fdms-images%2FDMP-images%2F5.1%2FDMPkernel_A1_4305.tivella

STEP#3

http://admin:default@10.10.10.10:7777/get_param?p=init.upg*

init.upg_context T_STRING Upgrade  (kernel) succeeded

init.upg_percent T_LONG 0

init.upg_status T_STRING Firmware upgrade not active

STEP#4

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (root@atiff-desktop) (gcc version 3.3.2) #1 Tue Nov 18 14:48:57 EST 2008

>> Success Kernel upgraded to 5.1 <<

*** UPGRADE KERNEL FROM 5.1 to 5.2 ***

STEP#1

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (root@atiff-desktop) (gcc version 3.3.2) #1 Tue Nov 18 14:48:57 EST 2008

STEP#2

http://admin:default@10.10.10.10:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F20.20.20.20%2FSoftware%2Fdms-images%2FDMP-images%2F5.2%2FFCS%2F5.2.0_FCS_4305%2FDMPkernel_A2_4305.tivella

STEP#3

http://admin:default@10.10.10.10:7777/get_param?p=init.upg*

init.upg_context T_STRING Upgrade  (kernel) succeeded

init.upg_percent T_LONG 0

init.upg_status T_STRING Firmware upgrade not active

STEP#4

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (compiler@compiler) (gcc version 3.3.2) #1 Wed Dec 9 22:10:26 PST 2009

>> Success Kernel upgraded to 5.2 <<

View solution in original post

10 Replies 10

Tomas de Leon
Cisco Employee
Cisco Employee

If you used the URL that is posted in the note, may not work since certain characters need

to be escaped.

The PREFERRED way to upgrade the kernel images is via

the Digital Media Manager(DMM) - Digital Signage Module(DSM).

Follow the Normal instructions for Upgrading DMP Firmware via

the DMM-DSM and Make sure to CHECK the "Is Kernel Upgrade?"

CheckBox.

Of Course, there may be some standalone or lab DMPs that may need

to upgrade the kernel images without access to a DMM.

To do this you can upgrade the Kernel via ALTERNATE METHOD:

1. HTTP Browser Commands

The Following Method are NOT the recommended method but is a way to upgrade

Kernel without a DMM.

-------------------------------

METHOD: HTTP Browser Commands

-------------------------------

* FTP or COPY the 5.1 KERNEL image to a REACHABLE WEB SERVER.  HTTP to the WEB SERVER location of the

  Kernel image to verify the image is there and accessible.  Record the IP ADDRESS of the Web Server,

  Location of the File on the Web Server, and the Kernel Image Filename.

  ie. http://web.server.com/DMPkernel_A1_4305.tivella

NOTE: The Image file is in the ROOT directory of Web Server.  If you have in a different

directory the "/" separators (or any Special Characters) will need to be ESCAPED.

* Open Browser and Send the Following HTTP REQUEST to DMP

  http://admin:default@a.b.c.d:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2Fweb.server.com%2F

%2FDMPkernel_A1_4305.tivella

  admin          = DMP Web Account Username

  default        = DMP Web Account Password

  a.b.c.d        = IP Address of DMP

  web.server.com = FQDN or IP Address of Web Server

* After the upgrade and DMP reboots use this command to check the status:

  http://admin:default@a.b.c.d:7777/get_param?p=init.upg*

Sample Response:

init.upg_context              T_STRING            Upgrade  (kernel) succeeded

If this answers your question, Please take time to mark this
discussion answered & rate the response.

Thank You!

T.

Hi Tomas,

I've tried again with the DMM - Digital Signage Module(DSM) and with the HTTP method but still no adequate response from the DMP 4305G.

I'm sending in attachment couple of screen shoots just to be more clear for what is going on while i try the procedure.

For the DMM-DSM case, you can see that the 4305G got registerd for a while and had green checkmark (DMP registerd.JPG) which in meantime i tried the procedure for upgrading the kernel. After some period it just lost status (DMP unregistered.JPG).

For the HTTP Web server method, I tried on IIS 6.0 (WebServer.JPG), I HTTP to the WEB SERVER location to verify (http.JPG), checked the status to see what's going on (see Upgrade status.JPG), but the 4305G did not restart at all. It just promt me for confirmation (see Confirmation dialog.JPG).

I tried also resetting to defaults the DMP, and tried it again through the http and got this output when checking update status (Upgrade status_2.JPG) bear in mind that this time the DMP was set to DHCP, hense it got ip address 10.0.10.129. It simply doesn kick start the upgrade process. I even tried with MIME type (plain/text) also for the .tivella extension.

This is the browser command i used:

http://admin:Passw0rd@10.0.1.19:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F10.0.10.50%2F

%2FD

MPkernel_A2_4305.tivella

Any ideas? Am I still missing something..

Thank you,

Tiberie

You used the browser command:

http://admin:Passw0rd@10.0.1.19:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F10.0.10.50%2F

%2FDMPkernel_A2_4305.tivella

Notice the

the

is the DIRECTORY that the file resides.  So replace with the directory name.

T.

Hi Tomas,

I tried now like this:

http://admin:Passw0rd@10.0.1.19:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F10.0.10.50%2FWebServer%2FDMPkernel_A2_4305.tivella

- *WebServer is the Home directory.

and like this:

http://admin:Passw0rd@10.0.1.19:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F10.0.10.50%2FDMPkernel_A2_4305.tivella

And when I checked the status did it upgrade, it still showed that the "Firmware upgrade has never been done". The DMP did not restart once. It's like it never got the update going.

I even tried this which i found from an earlier similar post: "Adding the MIME-type .tivella extension (as text/plain) in IIS to allow  the upgrade file to be served by the web server." Still no joy here.

Am I still doing it wrong, or there is something with the DMP or firmware image?

Thank you,

Tiberie

Ok, I tested a DMP-4305G here that was on 5.0. 

I upgraded for 5.0 to 5.1 first.  The upgrade was successful.

I then upgraded for 5.1 to 5.2.  The upgrade was successful.

You may need to capture a sniffer trace to see what is

going on.  And use the same steps and legends that i use

to verify everything in your setup.

T.

RECREATE NOTES:

===============


DMP        = 10.10.10.10

WEB Server = 20.20.20.20

      User = admin

  Password = default


Web Server = Apache (I do not use IIS)


5.1 Web Server Directory = Software/dms-images/DMP-images/5.1/

5.1 Firmware Kernel file = DMPkernel_A1_4305.tivella


5.2 Web Server Directory = Software/dms-images/DMP-images/5.2/FCS/5.2.0_FCS_4305/

5.2 Firmware Kernel file = DMPkernel_A2_4305.tivella

*** UPGRADE KERNEL FROM 5.0 to 5.1 ***

STEP#1

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (alexr@heritage) (gcc version 3.3.2) #1 Fri Oct 19 11:00:01 PDT 2007

STEP#2

http://admin:default@10.10.10.10:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F20.20.20.20%2FSoftware%2Fdms-images%2FDMP-images%2F5.1%2FDMPkernel_A1_4305.tivella

STEP#3

http://admin:default@10.10.10.10:7777/get_param?p=init.upg*

init.upg_context T_STRING Upgrade  (kernel) succeeded

init.upg_percent T_LONG 0

init.upg_status T_STRING Firmware upgrade not active

STEP#4

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (root@atiff-desktop) (gcc version 3.3.2) #1 Tue Nov 18 14:48:57 EST 2008

>> Success Kernel upgraded to 5.1 <<

*** UPGRADE KERNEL FROM 5.1 to 5.2 ***

STEP#1

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (root@atiff-desktop) (gcc version 3.3.2) #1 Tue Nov 18 14:48:57 EST 2008

STEP#2

http://admin:default@10.10.10.10:7777/set_param?mng.command=start+upgrade+kernel+http%3A%2F%2F20.20.20.20%2FSoftware%2Fdms-images%2FDMP-images%2F5.2%2FFCS%2F5.2.0_FCS_4305%2FDMPkernel_A2_4305.tivella

STEP#3

http://admin:default@10.10.10.10:7777/get_param?p=init.upg*

init.upg_context T_STRING Upgrade  (kernel) succeeded

init.upg_percent T_LONG 0

init.upg_status T_STRING Firmware upgrade not active

STEP#4

http://admin:default@10.10.10.10:7777/get_param?p=sinfo.version

sinfo.version T_STRING Linux version 2.4.22 (compiler@compiler) (gcc version 3.3.2) #1 Wed Dec 9 22:10:26 PST 2009

>> Success Kernel upgraded to 5.2 <<

Hi Tomas,

I've tried now with Apache server like you, run Wireshark , got TCP/IP handshake packets back and forth from the server and the DMP, but it did not start the upgrade process. I think there might be something missing(or restricting) from the configuration of the httpd.conf file of the Apache server to PUSH the kernel or maybe I should declare the .tivella type in the mime.types file!?

Can you please send me your httpd.conf file so I compare it and see if there is something different from mine config, if its not a problem?

Thanks a LOT for your continued interest to solve my problem, Tomas!

p.s.

This is what i get from step #1 from the 4305G DMP:

sinfo.version     T_STRING     Linux version 2.4.22 (root@atiff-desktop) (gcc version 3.3.2) #1 
Tue Nov 18 14:48:57 EST 2008

Step #3:

init.upg_context     T_STRING     Firmware upgrade has never been done
init.upg_percent     T_LONG     0
init.upg_status     T_STRING     Invalid product tag (act:"", exp:"D4305G").

Sincerely,

Tiberie

Tiberie,

post me your email and I will send you some additional

instructions to try. 

T.

also please issue this command and upload it"

https://admin:default@10.10.10.10:7777/get_param?p=*.*

Thanks

T.

Hi Tomas,

I've send you my e-mail via private message to you.

Meanwhile, here are mine findings:

I issued the command on the 4305G: https://admin:Passw0rd@10.0.10.129:7777/get_param?p=*.* and the DMP did not respond. That was strange, because before trying with the 4305G, I tried with the 4400 which works flawlessly. Then I removed the S from http(S) and it worked with the 4305G too.

Have in mind that the 4305G is factory reset, I've only changed the password, from default to Passw0rd.

I am sending in attach. the output from the 4400 just for sake of comparison.

Regards,

Tiberie

Please check your email.   I sent you additional information to try.

Please try and let me know how it goes.

T.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: