- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Swicthes stopped updating PCM2.0+
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО01-16-2006 07:53 PM
тАО01-16-2006 07:53 PM
I have been running PCM2.0+ for a while now and it has been working fine.
All of a sudden, Some of the switches have stopped responding and i can no longer update the software on them from the management server.
There are 3 5308 switches, 1 4108 and 2 9308 switches that are experiencing this problem.
You can scan for configurations without any problems, As soon as you start the software update wizard it times out on the first part.
Anyone come across this before or have any ideas???
Cheers
Jonathan
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2006 03:21 AM
тАО01-17-2006 03:21 AM
Re: Swicthes stopped updating PCM2.0+
I have a long standing case (since Sept-Oct) with HP open about extremely high CPU Usage from Mysqld-max-nt.exe in PCM 2.0 (and 2.1)+ when performing some operations. Unfortunately, no resolution has come yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2006 08:33 AM
тАО01-17-2006 08:33 AM
Re: Swicthes stopped updating PCM2.0+
While I dig into this can you let me know if the switches in question successfully pass the "Test Communication Parameters" tests available via the right-click menu items and/or the toolbar for a specific device.
I'm wondering if perhaps the devices have too many telnet sessions left open or perhaps the communication parameters have changed (within PCM, the switch or both).
If you could run this test and let us know the results that would be very helpfull.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2006 09:49 PM
тАО01-17-2006 09:49 PM
Re: Swicthes stopped updating PCM2.0+
The process usagee is very low on the box, It stays at around 4% and occasionally spikes to 30% so i don't think that can be the problem.
I have about 48 switches currently being managed by the server, All of these will allow you to schedule a software update.
I have checked and double checked the Communication parameters in PCM. The comms parameter test is successful on all accounts.
I have upgraded to version 2.1 to see if this has any effect.
I hadn't thought of open telnet sessions etc. I will check this now...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2006 04:48 AM
тАО01-18-2006 04:48 AM
Re: Swicthes stopped updating PCM2.0+
I have since learned to always do a proper logoff from a telnet session and to not linger in a session too long.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2006 07:56 PM
тАО01-18-2006 07:56 PM
Re: Swicthes stopped updating PCM2.0+
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 12:08 PM
тАО01-19-2006 12:08 PM
SolutionThe engineers responsible for the software update tool in PCM have come back to me with a few clarifying questions:
1)When you say that the devices "stop responding" I assume you mean the are not responding to the first step of the software update wizard. Is that accurate and if not in what other ways do the switches stop responding?
2)Are all of your devices of the types you mentioned (5308,4108,9308) failing or are the ones you mentioned a subset of what's on your network. Just wondering if this is a class-wide problem (that is all 5300's you have deployed) or device specific (that is, 3 of your N 5300's).
3) Have you tried increasing the timeout value used by PCM for CLI and SNMP access? You can configure this by selecting the device and launching the "Comm. Parameters in PCM" tool. If the first step of the Software Update tool fails it is usually due to a timeout or mismatched communication parameters.
4) If possible, can you try rebooting one of the devices in question and letting us know if that changes anything. This will clear out any lingering telnet sessions but from your report that the communication test was successful I don't think this is likely to be the problem.
4)After restarting your management server can you please try the following steps:
- Rediscover one of the devices that is failing
- Test the communication parameters again to make sure everything is successful
- Try scanning the configuration on the device using the Configuration Manager "Scan" tool.
- Lastly, try running the software update wizard once again on the same device.
We are very interested in what you experience in each of these steps as something does seem to be amiss here. Once you have tried this can you let us know how it went and attach the file:
PNM\server\logs\FWU-server.log
This should give us a view into what is going wrong.
Sorry you're running into this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 10:30 PM
тАО01-19-2006 10:30 PM
Re: Swicthes stopped updating PCM2.0+
1)That is correct, they timeout on the first stage of the Software update wizard.
I can Still successfully scan for new configurations.
2)The devices that are failing are just a subset of what we have here.
4 out of 5 4108gl switches fail the update wizard.
4 out of 11 5300XL switches fail the update wizard
2 out of 4 9300 Switches fail.
3) I have tried, After you suggested it, increasing the timeout values configured in PCM. This has had no effect. I have checked and rechecked the communication settings and they are definately right.
4) I will try restarting one of the switches as soon as i can. Can't at the moment because all hell will break loose!
4)I have deleted one of the problem devices, Restarted the server and manually rediscovered the device. I reset the comms parameters and still no joy.
I have attached the requested log file.
Thanks for your help,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2006 04:39 PM
тАО01-20-2006 04:39 PM
Re: Swicthes stopped updating PCM2.0+
We can try this with the 5300 you have.
PNM\server\config\devconfig\sw5300.oid; open this file and change the variable that indicated something like the number of OS Image versions.
To be honest I am trying to do this from memory because I don├в t have access to one these files. It should have the number 2, change that to 1. You'll need to restart the PCM server.
See if the Wizard now moves to the next step.
If it doesn't timeout then you can bet that it was some sort of Telnet issue.
Again I must stress that you are doing this on your own risk, you should never mess with application files blah blah blah.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2006 01:14 AM
тАО01-22-2006 01:14 AM
Re: Swicthes stopped updating PCM2.0+
Looking at the log, you can see that the password for telnet is invalid, can you try and use the CLI wizard and see if that works? My guess it should also timeout.