3.6.7.A 3002 Hardware client Update

[jbrennan]

I am trying to load 3.6.7.A on several 3002 hardware clients using Auto Update.

The first update works fine. I am upgrading from 3.6.7.Rel to 3.6.7.A. However once the 3002 has been upgraded to 3.6.7.A and reboots the new software the client again begins the upgrade process and reboots. In the local log file the 3002 after the VPN tunnel has been established says that the versions do not match.

Here is the log file.

42 02/24/2003 14:23:13.250 SEV=4 AUTOUPDATE/7 RPT=1

Updating firmware to 3.6.7.A from 3.6.7.A.

41 02/24/2003 14:23:13.250 SEV=4 AUTOUPDATE/6 RPT=1

Current version 3.6.7.A does not match 3.6.7.A.

Has anyone seen this happen with 3.6.7.A???

[gfullage]

Hmm, this looks like a problem. I just recreated it in my lab and saw the same thing. For the moment turn off the Client Update feature on the head-end concentrator and I'll get back to you with an answer as to what's going on.

[gfullage]

Yep, this is a bug, they've fixed it already and it'll be in 3.6.7.B. Unfortunately for the moment you'll have to turn off the auto-update feature, but when you're ready to load 3.6.7.B (should be out in a week or three) you should be OK.

[senthil.natarajan]

can you please provide me the documentation for autoupdate feature of 3002 hardware client. your help is appreciated.

Thanks

Senthil