cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
804
Views
13
Helpful
24
Replies

SWIM supports OS upgrade on 6513s or not 6509s

yjdabear
VIP Alumni
VIP Alumni

The hangup appears to be SWIM does not see the SUP module (and hence the bootdisk) on all the 6509s, but it sees them fine on all the 6513s. All the cat6ks are running CatOS 8.4(4). Is there any known issue between SWIM and cat6509?

SUPs on the 6509s:

4000-1000BaseX Supervisor 9 port WS-SUP32-GE-3B Rev. 4.5

1000-1000BaseX Supervisor 9 port WS-SUP32-GE-3B Rev. 4.1

2000-1000BaseX Supervisor 9 port WS-SUP32-GE-3B Rev. 4.1

SUPs on the 6513s:

SUPERVISOR32_6000

7-8 port 1000BaseX Supervisor module

1 Accepted Solution

Accepted Solutions

The patch affects inventory, so it would address SOME of the inconsistencies between the platforms. However, the will still be some differences due to the different MIBs being used.

View solution in original post

24 Replies 24

Joe Clarke
Cisco Employee
Cisco Employee

What version of RME is this? What version of the SharedSwimCAT package do you have?

RME 4.0.6. I see a SharedSwimCatSwitch at 1.0, but there's no device package update found when checking against cisco.com.

Upgradable one in the 6513s

MODULE : wssup32ge3b

MODEL : 8 port 1000BaseX Supervisor module

...

Image_Type : SUPERVISOR32_6000

SOURCE : bootdisk:

UPGRADETYPE : ACTIVE

The nonupgradable SUP in the 6509s, which translates to wssup32ge3b too, according to http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=moduleType

MODULE : EntityVendorOIDType(.1.3.6.1.4.1.9.5.1.3.1.1.2.509)

MODEL : 1000BaseX Supervisor 9 port WS-SUP32-GE-3B Rev. 4.1

The package should be SharedSwimCAT, and the latest version is 1.4, and the Sup32-GE-3B is supported in this version.

Found it. I do have SharedSwimCAT 1.4. I've updated my previous post to include more info: The problem from what I see is the same wssup32ge3b (.1.3.6.1.4.1.9.5.1.3.1.1.2.509) is recognized by SWIM in the 6513 (slot 7 or 8), but not in any 6509 (slot 5 or 6).

What do you mean by isn't recognized? Please post a screenshot showing the difference between the working 6513 and the non-working 6509. I want to be sure we're on the same page.

I find the 6504s in the same boat as 6509s as well.

could you check if the failing devices are listed in RME with a status other then 'normal' (i.e. 'alias' or 'conflicting',..)

I found the problem. The 6506, 6509, and 6504 are instrumented differently than the 6513 when it comes to inventory collection. RME uses the CISCO-STACK-MIB when collecting the inventory from the 6513, but uses the ENTITY-MIB for the other switches. The ENTITY-MIB code is missing the new Sup module mapping. The bug is CSCsq40165.

Is there a fix available? If not, can one be expected any time soon, with a TAC case opened?

The bug is scheduled to be fixed in RME 4.3. There is no patch right now. It may be possible for development to create one if you open a TAC service request.

Thanks! I have to ask for clarification though: Would development make the patch for LMS 2.6 (RME 4.0.6)?

They should. The change is trivial.

I'm also curious if the patch would address the RME reporting inconsistencies between 650Xs and 6513s, presumably due to the same instrumentation difference, or would it be a single-issue fix just for SWIM?

The patch affects inventory, so it would address SOME of the inconsistencies between the platforms. However, the will still be some differences due to the different MIBs being used.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: