Software Management

Unanswered Question
Sep 15th, 2009

HI,

I have added the images from 6500 devices, inclusive from SXF

to SXI2. I have also stopped and restarted the daemon manager and

performed a inventory recollection of all 6500 devices. Upon trying the

Distribute by Devices, I got the same behavior such that:

Devices running SXH or SXI have options for upgrade to SXH or SXI.

Devices running SXF only have options for upgrading to SXF.

I started wondering about Recommendation preferences under View/Edit

Software Management Preferences. Currently I have all of the following

checked:

Recommendation

Include Cisco.com images for image recommendation.

Include General deployment images.

Include latest maintenance release (of each major release).

Include images higher than running image.

Include same image feature subset as running image.

What I have found after experimenting with disabling and enabling

different combinations of the recommendations, is that enabling the

following set of recommendations produces the above behavior for SXF

devices:

Include Cisco.com images for image recommendation.

Include images higher than running image.

Include same image feature subset as running image.

If I uncheck the Cisco.com images for image recommendation and just have

the following:

Include General deployment images.

Include latest maintenance release (of each major release).

Include images higher than running image.

Include same image feature subset as running image.

then I can chose SXI as an option to upgrade SXF devices.

Is this a bug of some sort or am I misunderstanding how the

recommendations should be checked off?

-Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Tue, 09/15/2009 - 07:41

This is an issue with how these options are documented. Essentially, many of these options should be treated as having an "Only" in front of them. I generally recommend people leave these options unchecked, and add desired images to the local repo. This step can be done out-of-band, and saves time when it comes down to the actual deployment phase.

Actions

This Discussion