- Community Home
- >
- Networking
- >
- Legacy
- >
- PCM
- >
- Re: AP 420, Procurve manager 2.1.5 firmware upgrad...
PCM
1752594
Members
3022
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2006 11:29 PM
тАО10-17-2006 11:29 PM
AP 420, Procurve manager 2.1.5 firmware upgrade
Hello, I recently upgraded two of our companys 420 accesspoints with the new 2.1.5 firmware via cli, and this worked fine.
Then, i decided to test it with the Procurve Manager, and that failed hard. This is what the eventlog says:
Event type:
Application Event
Trap type:
N/A
Received from:
Software Update
Date received:
Wed Oct 18 13:02:58 CEST 2006
Date acknowledged:
Event has not been acknowledged.
Severity:
Major
Event Description
10.xx.xx.xx Error
I knew from browsing the forums that i had to set the communication paramters in the device before, but now the accesspoints have done a factory reset and is running 2.0.43-temp2 firmware. The old firmware was 2.1.2 and it was running boot rom version 3.0.6.
What has happened? Did someone set up us the bomb? o_O
Then, i decided to test it with the Procurve Manager, and that failed hard. This is what the eventlog says:
Event type:
Application Event
Trap type:
N/A
Received from:
Software Update
Date received:
Wed Oct 18 13:02:58 CEST 2006
Date acknowledged:
Event has not been acknowledged.
Severity:
Major
Event Description
10.xx.xx.xx Error
I knew from browsing the forums that i had to set the communication paramters in the device before, but now the accesspoints have done a factory reset and is running 2.0.43-temp2 firmware. The old firmware was 2.1.2 and it was running boot rom version 3.0.6.
What has happened? Did someone set up us the bomb? o_O
- Tags:
- firmware update
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2006 08:27 AM
тАО10-26-2006 08:27 AM
Re: AP 420, Procurve manager 2.1.5 firmware upgrade
Hello Christian,
Is this something that you were able to duplicate more than once, or was this a result from one test? If the latter, then I would suggest opening a new call with ProCurve Support to report this issue (if you have not done so already). I have seen, on very rare occasions, what you have mentioned, and it is usually brought on by a corrupted image, or an upgrade that was prematurely stopped or lost connectivity to the network. Would need more detail though.
Thanks ... greg
Is this something that you were able to duplicate more than once, or was this a result from one test? If the latter, then I would suggest opening a new call with ProCurve Support to report this issue (if you have not done so already). I have seen, on very rare occasions, what you have mentioned, and it is usually brought on by a corrupted image, or an upgrade that was prematurely stopped or lost connectivity to the network. Would need more detail though.
Thanks ... greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2006 09:35 PM
тАО10-26-2006 09:35 PM
Re: AP 420, Procurve manager 2.1.5 firmware upgrade
i tried it two times with the same results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 08:46 PM
тАО12-04-2006 08:46 PM
Re: AP 420, Procurve manager 2.1.5 firmware upgrade
hi, did you have upgraded your PCM+?
http://66.35.221.171/WNDNames/software/standard_license_information.asp?fileName=http://www.hp.com/rnd/software/Download3_u8.htm
you can check this link, and upgrade your procurve manager plus.
http://66.35.221.171/WNDNames/software/standard_license_information.asp?fileName=http://www.hp.com/rnd/software/Download3_u8.htm
you can check this link, and upgrade your procurve manager plus.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP