Call Manager server 8.6 in LMS 4.1 discovery

Unanswered Question
Jul 31st, 2012

Hi Guys,

I setup one network where LMS is in subnet and CUCM is in subnet both are reachabe to each other and  both are also in different EVN/VRF.

when i try to discover the CUCM from LMS 4.1. It discover only routers and switches. I am unable to find any CUCM 8.6 server, i did the snmp read community setting in call manager under serviceability.

In addition, IP phones are appeared as END host not as IP Phones. (find attached image)

Need your help regarding this issue. Its bit urgent.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Vinod Arya Tue, 07/31/2012 - 03:45

Make sure the Call Manager is IP and SNMP reachable from LMS server. if so, try adding the CUCM manually via Inventory > Add/edit devices.

once added run the inventory, data collections and UT Aquisition. Call manager is mandatory  to be managed with LMS to show IP Phones, else we see the mac add as end-hosts.

You are facing expected behaviour.


Fazal E Rasool Khan Tue, 07/31/2012 - 05:06

Thanks for the reply Vinod.

Call Manager is reachable by Ping from LMS but when i run the snmpwalk i got the following result as attached.

I also add the device/cucm in inventory but when i discover its unreachable

did i use the right in the syntax.

Vinod Arya Tue, 07/31/2012 - 23:47


The output was also correct!! So if went fluidic!

You can close this thread if issue is resolved.



Fazal E Rasool Khan Wed, 08/01/2012 - 00:10

As the issue is solved, we can close the discussion.

Can you explain, what we have to look in snmpwalk output.



Vinod Arya Wed, 08/01/2012 - 00:29

Intenton was to check if dveice responds to snmp request from LMS server, which is vital for all that we're interested in.

When we use the snmpwalk utility, which is used by LMS for all snmp communication, we see the output as what we have asked if the device has responded appropriately or if there is any error.

In our case the CUCM replied properly. We used command ;

NMSROOT/Objects/jt/bin>snmpwalk -v 2c -c public .

Where the bold portion is question we asked CUCM, which is .

The reply from device contain some un-important stuff, which you'll notice whenever you query any device, and at last you'll see reply from device.

. stands for any device's system information, like make-model-image etc.

Reply which is not imp and useless :

Useful reply which should be seen @ last, based on what we asked from device ;

Once it was verified that the device is comminicating to LMS via snmp, it was expected that it would work fine.



This Discussion

Related Content