CiscoWorks LMS 2.5 and CMS devices

[alvaradof]

Hi all,

I have a newly installed Ciscoworks LMS 2.5 server on a Windows 2003

platform. We are having an issue with discovering switches that are

configured in a cluster via Cluster Management Suite. Because of the

ability to manage several switches via a single IP via the CMS

commander, non of the other switches have an IP, thus no DNS/RDNS for

Ciscoworks to resolve and discover. All switches have SNMP and CDP

configured and operational.

My question, is there a way to discover all the other switchs that are

managed by a CMS commander? will it be necesary to assign IP's to all

the switches that do not have IP's assigned, but are visible and

available via the CMS?

The switches in question are as follows:

CMS commander is a Catalyst 3550

CMS members are a variety of 2950's and 2900XL's

Thanks

Frank

[rmushtaq]

3500XL series is supported in IP Mode only. Clustered devices not assigned an IP address are not supported -> http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/camp_4x/cmgr_4_0/cm40sdt.htm#wp289914

[jedavis]

I am having the same issue. Rmushtaq, he is not using a 3500XL switch, he is using a 3550. I too have 3550 clusters. I have tried to add the clusters manually by going to Common Services -> Devices and Credentials -> Device Management and clicking add. From there I first create a device with a management type of "Standard" and a device type of "Cisco Cluster Management Suite", along with password and SNMP credentials. After doing this the cluster record appears in the device selector under CS@server\System Defined Groups\Network Management\Other Network Management Products\Cisco Cluster Management Suite. I then add the command switch with a management type of "Cluster Managed", select the cluster record that I just added and give it a member number of 0. The UI does not allow you to add any credentials while adding clustered devices. Presumably it gets these credentials from the cluster record. I then add the member switches and run Campus data collection from Campus Manager -> Administration. The result is that the command switch (the one with the IP address) is recognized, but none of the member switches are. Am I doing something wrong here? This procedure is described in the Readme for Common Services 3.0 Service Pack 1 at http://www.cisco.com/en/US/customer/products/sw/cscowork/ps3996/products_release_and_installation_notes09186a00803e8cd9.html#wp95254 in the section "Adding Standard Devices".

Thanks,

-Jeff

[itsadmin]

Jeff/Gang,

You are exactly right, you and I have the exact same issue at hand. I have searched high and low and have tried many different ways to try and use the CMS commander as the primary "entry" point for the rest of the cluster members with regards to management with LMS 2.5

So far, the only fix I have found is to bit the bullet and add IP's to all my switches and put them in a management VLAN. You can still use the CMS/CNA and manage the switches like you did in the past can now use LMS 2.5 for the same devices.

I did not want to assign any IP's to switches if I didn't have to, but see no way around this.

If I find something that works, I'll make sure to post it here.

Frank