Procedure to add CSM load Balancer in cisco works lms 3.0.1

[mkareemashraf]

Dear All,

We are using Ciscoworks lms 3.0.1 in our company.

we have CSM installed in our core switch .

CSM module is displayed in ciscoview but it is not displayed in RME Topology map.

what is the procedure to get CSM in RME CAmpus manager topology and where can i get the exact documentation for it.

please help me .

thanks

ashraf

[Joe Clarke]

RME doesn't have a topology map. Topology is part of Campus Manager which is completely separate from RME. The CSM is not supported by Campus Manager, and thus will not appear correctly on the Topology Map.

[mkareemashraf]

Dear sir,

we have seen CSM is Supported in topology map in list for supported devices.

please check the link below :

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.0.1/device_support/table/lms301sdt.html

or

check the attached file for your information.

please,i want to known if the device is not suported in topology map why it is mentioned in list.

[Joe Clarke]

What is the sysObjectID? Because the CSM with sysObjectID 1.3.6.1.4.1.9.1.524 is not supported by Campus Manager.

[mkareemashraf]

dear sir,

how can we get OID for CSM .

please help me to get it.

thanks

ashraf

[Marvin Rhoads]

One uses the snmpwalk tool to retrieve Object Identifiers (OIDs) from a given network entity.

snmpwalk is included with most *nix distributions and is included with the DFM component of CiscoWorks. From the DFM User Guide (http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.1/user/guide/dfmfaq.html), it is used thus:

Q. How can I collect Mibwalk for a device?

A. To collect the Mibwalk for a device, do the following:

Step 1 Go to NMSROOT/objects/smarts/bin

Step 2 Enter the following command for:

•Snmp v1 and snmp v2 devices:

-For Solaris: ./sm_snmpwalk --community= deviceIp

For eg: ./sm_snmpwalk --community=cisco 4.1.1.1

-For Windows: sm_snmpwalk --community= deviceIp

For eg: sm_snmpwalk --community=cisco 4.1.1.1

•Snmp v3 devices:

-For Solaris: ./sm_snmpwalk --snmp=3 --user=desuser --auth=MD5 --authPass=changeme --priv=DES --privPass=despass --authengine=8000000903000019563F8338 bq-gwhsrp.lss.emc.com

-For Windows: sm_snmpwalk --snmp=3 --user=desuser --auth=MD5 --authPass=changeme --priv=DES --privPass=despass --authengine=8000000903000019563F8338 bq-gwhsrp.lss.emc.com

The above command will generate three files, xxxxx.walk, xxxxx.mimic, and xxxxx.snap files [where xxxxx is the device IP] in the same location, that is inNMSROOT/objects/smarts/bin. You can zip the 3 generated files.

Hope this helps. Please rate this post if it does.

[Joe Clarke]

Go to Device Center, and launch the SNMP Walk tool. Use a starting OID value of "sysObjectID".

[mkareemashraf]

1) We ran a SAPRO (Snmpwalk) dump on the 6513 Switch hosting the CSM module, but we could not find the object-ID: 1.3.6.1.4.1.9.1.524

2) Are we supposed to take SNMP dumps of host switch or the module, as the module does not speak SNMP. We also checked the Cisco PRODUCTS-MIB file and it has only one OID for the CSM module (1.3.6.1.4.1.9.1.524), so if this OID is not supported in Campus Manager Topology then why it is listed in the Device Support Table Matrix?

3) We also ran the SNMP walk tool in DFM, however it only lists the object-id of the switch itself and not for any modules installed in it (FWSM,IDSM,CSM etc.) as seen below:

The following is a SNMP walk of device 10.X.XX.XX starting from sysObjectID

SNMP Walk Output

--------------------------------------------------------------------------------

sysObjectID

.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.9.1.400

The following is a SNMP walk of device 10.X.XX.XX starting from sysObjectID

SNMP Walk Output

--------------------------------------------------------------------------------

sysObjectID

RFC1213-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::ciscoWSC6513

[Joe Clarke]

If the CSM is not a separately manageable device, then it will never appear in Campus Manager as a device. Instead, the support mentioned is probably just that Campus will recognize the module in the switch (not really a big deal). The sysObjectIDs shown here are supported, and you should be seeing these switches in Campus.