- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: PCM+ Getting switches to update
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
тАО05-13-2010 02:43 PM
тАО05-13-2010 02:43 PM
* Download request Received from 172.16.0.10
* tftp: connection to 129.82.133.x failed
The PCM server is dual-homed with both 172.16.0.10 and 129.82.133.x addresses. I've added both addresses in the server .\pnm\server\config\commIpAddr.txt and .\pnm\client\config\commIpAddr.txt with 172.16.0.10 taking prescidence.
Ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2010 05:02 PM
тАО05-13-2010 05:02 PM
Re: PCM+ Getting switches to update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2010 07:42 AM
тАО05-14-2010 07:42 AM
Re: PCM+ Getting switches to update
Something else I noticed that's odd is when I go into the switch and select downloading a tftp client it is set to 129.82.133.x.
When I did a port scan on the machine's normal IP I got the below ports none of which appear to be tftp related.
21/tcp
42/tcp
135/tcp
445/tcp
1027/tcp
1049/tcp
1068/tcp
3389/tcp
8009/tcp
9001/tcp
30000/tcp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2010 01:25 PM
тАО05-14-2010 01:25 PM
Re: PCM+ Getting switches to update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2010 02:13 PM
тАО05-14-2010 02:13 PM
Re: PCM+ Getting switches to update
This is the free 2 month trial as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2010 03:17 AM
тАО05-15-2010 03:17 AM
Re: PCM+ Getting switches to update
Here is one trick you can try:
a) Stop PCM server and Agent Services
b) Create a file "commIpAddr.txt" under "\pnm\pcm-agent\config" directory.
c) Add entry 172.16.0.10 in that file ( same as the one you added in .\pnm\server\config\commIpAddr.txt )
d) Restart PCM Server and Agent
Check using netstat or currports, to ensure both PCM Server and Agent are bound to same IP (amongst the dual IP's)
Now attempt your software update
Pl let know how this goes about
HTH
`Javed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 07:54 AM
тАО05-17-2010 07:54 AM
Re: PCM+ Getting switches to update
The 172.x.x.x is the scope that has only the switches - nothing else should ever be on that scope. This is also a non-routeable IP scope on a vlan that doesn't go to the router.
I wasn't sure what you meant by 'restart the agent' so I restarted the PCM services, deleted and re-discovered the device. with no increase in luck.
Using netstat I noticed that port 69 is bound to the 129.x.x.x address. Not sure that's relevent or not either.
UDP 172.16.0.10:67 *:*(Scvhost)
UDP 172.16.0.10:68 *:*(Scvhost)
UDP 129.82.133.x:67 *:*(Scvhost)
UDP 129.82.133.x:68 *:*(Scvhost)
UDP 129.82.133.x:69 *:*(javaw.exe*32) - PCM?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 07:58 AM
тАО05-17-2010 07:58 AM
Re: PCM+ Getting switches to update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 08:16 AM
тАО05-17-2010 08:16 AM
Re: PCM+ Getting switches to update
However my 172.16.x.x is my managment vlan - all of my switches have Ips on that scope and I have verified connectivity through it by hand. The onlything it's missing is layer 3 services as I don't control a router.
Or am I misunderstanding what you are suggesting?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 09:36 AM
тАО05-17-2010 09:36 AM