Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

show ver indicates "Patching not available. . . "

I've followed a couple of threads where this message shows up and I'm confused about whether or not I should care. When  I type "dir" at the command line on the 6509-E I get "No files in directory" for disk0:/. The image is actually on sup_bootdisk:/.

I inherited this network and there is only one 6509-E configured this way. Will someone offer an explanation as to why the image is on the sup_bootdisk and whether or not there's some hidden consequence of leaving it there. Or whether I should simply copy the file to disk0:/. I ask because I am about to schedule a job with BCAN to upgrade the image.

Thanks,

Steve

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Silver

Re: show ver indicates "Patching not available. . . "

Hello Steve,

this message should be generated by the fact that the system is running a modular IOS image but without an install action performed.

it is just a warning and you should be fine.

Hope to help

Giuseppe

2 REPLIES
Hall of Fame Super Silver

Re: show ver indicates "Patching not available. . . "

Hello Steve,

this message should be generated by the fact that the system is running a modular IOS image but without an install action performed.

it is just a warning and you should be fine.

Hope to help

Giuseppe

New Member

Re: show ver indicates "Patching not available. . . "

Thanks for the response. After I opened the question I noticed that the image file name was different ( . . . WAN-M vs. . . . WAN-VM). So if I "install" the image to disk0:/ then . . . what, the image and file structure would be located on disk0:/ and not on the sup_bootdisk. That would seem to be the preferred mode, right? Or would you just leave it alone?

Thanks,
Steve

151
Views
0
Helpful
2
Replies
CreatePlease to create content