Solved: cm 5.0 ip phone aquisition

clark.ford · ‎07-16-2008

I have cwlms 3.0 this is configured to integrate with ACS 4.1

All of our managed switches and routers are tacacs enabled apart from our ccm servers (ccm3.2)

RME is correctly flagging the servers up as NON ACS.

CM is discovering the servers but is unable to carry out a data collection from them as was previously done in lms 2.6 via an snmp session.

How can I talk to the non tacacs enabled ccm servers via cm 5.0?

Joe Clarke · ‎07-16-2008

Campus only uses SNMP to talk to the CCM, so TACACS+ doesn't come into play. However, since LMS is integrated with ACS, these CCMs MUST be AAA clients of this ACS server (even if they are not actually using AAA). LMS will only manage devices that are ACS clients.

If the CCMs are ACS clients, start up a sniffer trace filtering on SNMP traffic to one of the CCMs. Then start a new Data Collection, and see if any traffic is going to the CCMs.

View solution in original post

Joe Clarke · ‎07-16-2008

Campus only uses SNMP to talk to the CCM, so TACACS+ doesn't come into play. However, since LMS is integrated with ACS, these CCMs MUST be AAA clients of this ACS server (even if they are not actually using AAA). LMS will only manage devices that are ACS clients.

If the CCMs are ACS clients, start up a sniffer trace filtering on SNMP traffic to one of the CCMs. Then start a new Data Collection, and see if any traffic is going to the CCMs.

clark.ford · ‎07-21-2008

Thank you for help

the solution as you suggested was to add the the CCM servers as AAA clients( even though they are not using AAA).

Thanks again much appreciated