- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: TFTP Problems on 5300 Switch
Switches, Hubs, and Modems
1752681
Members
5607
Online
108789
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
тАО03-30-2006 07:54 PM
тАО03-30-2006 07:54 PM
TFTP Problems on 5300 Switch
We have some 5300 ProCurves,
one of them don't let me copy config.
When i try to scan this Device for running-config with ProCurve Manager 2, i get tftp timeouts. I had tried to do it via console, same error. I have tried another tftp server, same error. This issue is only on one device.
All 5300 are Firmware E09.22.
Some Idea?
one of them don't let me copy config.
When i try to scan this Device for running-config with ProCurve Manager 2, i get tftp timeouts. I had tried to do it via console, same error. I have tried another tftp server, same error. This issue is only on one device.
All 5300 are Firmware E09.22.
Some Idea?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2006 07:59 PM
тАО03-30-2006 07:59 PM
Re: TFTP Problems on 5300 Switch
Have you checked communication paramenter I had an issue lately with the new B range of switches were the username had to be entered with the password as the default blank username wasent picked up. New security feature I think, I was also getting these time outs.
ROn
ROn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-31-2006 01:47 PM
тАО03-31-2006 01:47 PM
Re: TFTP Problems on 5300 Switch
I have seen TFTP timeouts before when a switch was under heavier than normal load. You might try increasing the TFTP transfer timeout value.
You might want to check the switch log for any signs of any broadcast storms or other anomalies that might be causing an Ethernet communications problem.
You might want to check the switch log for any signs of any broadcast storms or other anomalies that might be causing an Ethernet communications problem.
---------------------------------------------
I work for HP, but my posts and replies are my own.
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2006 10:10 PM
тАО04-06-2006 10:10 PM
Re: TFTP Problems on 5300 Switch
Thanks for quick response!
But it takes me some time to check this problem.
I think it was a Windows Routing Problem and a PCM+ Problem, not a real 5300 Problem.
The PCM+ is in our central site, and is multihomed.
One NIC for the Management Server the other for the Client Connection / RDP.
Because we have a large environment.
(10 locations and ca. 20 smaller "outposts")
We have 5300 as Border Gateways between our locations with Transport Vlans.
All connections are build as star (at the moment) to the central 5300.
The TFTP from the PCM2.1+ runs on the wrong NIC (clientside).
The issue i don't understand at moment is why i had no Problems with other Devices in these locations.
I have changed the def. gateway on the clientside nic,
after i change this no more problems to get running-config from this device.
I hope in future PCM Updates it is possible to change the Portbindings.
Not just commIpAdrr.txt for Management or Clientside.
I think all Management Services should run on Management Device?
Or have i missunderstand something from the docs?
But it takes me some time to check this problem.
I think it was a Windows Routing Problem and a PCM+ Problem, not a real 5300 Problem.
The PCM+ is in our central site, and is multihomed.
One NIC for the Management Server the other for the Client Connection / RDP.
Because we have a large environment.
(10 locations and ca. 20 smaller "outposts")
We have 5300 as Border Gateways between our locations with Transport Vlans.
All connections are build as star (at the moment) to the central 5300.
The TFTP from the PCM2.1+ runs on the wrong NIC (clientside).
The issue i don't understand at moment is why i had no Problems with other Devices in these locations.
I have changed the def. gateway on the clientside nic,
after i change this no more problems to get running-config from this device.
I hope in future PCM Updates it is possible to change the Portbindings.
Not just commIpAdrr.txt for Management or Clientside.
I think all Management Services should run on Management Device?
Or have i missunderstand something from the docs?
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