I setup one network where LMS is in subnet 192.168.5.0/24 and CUCM is in subnet 192.168.1.0/24. 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.
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.
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
The output was also correct!! So if went fluidic!
You can close this thread if issue is resolved.
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 10.10.10.1 .184.108.40.206.2.1.1
Where the bold portion is question we asked CUCM, which is .220.127.116.11.2.1.1.
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.
.18.104.22.168.2.1.1 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.