• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Upgrading Switch IOS Error

Comblues

Member
Upgrading switch IOS error
Whilst trying to upgrade the IOS on my switch I receive a..

%Error opening tftp://141.101.98.26/c2950-i6q4l2-mz.121-22.EA14.bin (Socket error)

message does anybody know what I'm doing wrong?

==================

This error is commonly experienced when the device cannot reach the file it is trying to load - IOS or Config file for example.

Here's a reference from Cisco's Website:

http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a008020b19e.shtml


I believe the problem is more likely related to the situation whereby an IP Address has not yet been assigned to the switch.

The problem can be replicated and reproduced easily enough by removing an IP Address from the Switch and then trying to perform a tftp copy operation.

Also if the interface on management or other vlans is/are shutdown and there is no active IP Address on the device.

Quick fix, assign IP Address and turn up the interface then start the copy process again with successful results.

Comblues
 
Last edited:
Is there a question here? Socket error = first thing to check is accessibility. If the transfer started but ended with this error, it normally means tftp was blocked or dropping packets (it is UDP after all) and the Cisco recovery mechanism didn't work (like normal it seems.) Using something like ftp (or console xmodem etc) if available should succeed.

From this example I assume you are using the wrap cable?
 
It was a problem that was being experienced and I was asked to help resolve it.

A shut down vlan resulting in no ip address that was active caused the error in question. Easily resolved.

I thought others may find it useful.

Thanks for the offers of help.

Yes a console cable was used.

Comblues
 
I couldn't help notice your signature contains bunch of certs that you have.
Didn't realize there's a CCNP track called "BGP/QoS/MPLS "
 
Back
Top