[cisco-voip] device type mismatch from call manager..

[Wes Sisk]

Ed,

Approach appears good. 3 possibilities come to mind:

1. One thing i've observed but not been able to figure out is that 
sometimes 'run sql' appears case sensitive. If you try it your query as 
"run sql select name from device where name like '%11161EE' " does it 
find anything?
2. Database replication - device may be deleted on publisher but the 
delete may not be replicated down to subscriber.  Try the query on the 
publisher and on the server throwing the error. If different results 
then database replication is bad.
3. Change notification - In 6.x and later change notification to the 
running process (ccm) is generated AFTER database replication occurs. 
There is still possibility of losing change notification. If the device 
is not in database on the subscriber (again, assuming 6.x and later) but 
CM is throwing this message then ccm has definitely lost the change 
notification to delete the device.  Only recovery is restart the ccm 
service so the current config from database is loaded into memory.

/Wes



On Wednesday, August 04, 2010 12:58:43 PM, Ed Leatherman 
<ealeatherman at gmail.com> wrote:
> All,
>
> I'm getting a Device type mismatch syslog message about a specific
> device, which seems straight forward enough - but when I go hunting
> for the device in call manager to see what model it's configured as,
> it doesn't find the device. Is this normal? I expected to find a 7962
> that was configured as a 7961 by accident or something similar that I
> could correct.
> CM 7.1.5
>   	
> Aug  4 12:33:39 10.192.2.12 405102: Aug 04 16:33:39.265 UTC :
> %CCM_CALLMANAGER-CALLMANAGER-3-DeviceTypeMismatch: Device type
> mismatch. Name of device.:SEP0011211161EE Device type.:7 Database
> device type:255 App ID:Cisco CallManager Cluster ID:OWP-PUB-Cluster
> Node ID:owp-sub-a
> Aug  4 12:33:39 10.192.2.12 405101: Aug 04 16:33:39.251 UTC :
> %CCM_CALLMANAGER-CALLMANAGER-3-StationEventAlert: Station alert.
> Protocol:SCCP TCP ProcessID:2.100.9.389509 Device Text:6:
> Name=SEP0011211161EE Load=8.1(2.0)File Not Found Param1:2048
> Param2:-113854710 App ID:Cisco CallManager Cluster ID:OWP-PUB-Cluster
> Node ID:owp-sub-a
> Aug  4 12:33:39 10.192.2.12 405848: : ccm: 405053: Aug 04 16:33:39.251
> UTC :  %CCM_CALLMANAGER-CALLMANAGER-3-StationEventAlert: Station
> alert. Protocol:SCCP TCP ProcessID:2.100.9.389509 Device Text:6:
> Name=SEP0011211161EE Load=8.1(2.0)File Not Found Param1:2048
> Param2:-113854710 App ID:Cisco CallManager Cluster ID:OWP-PUB-Cluster
> Node ID:owp-sub-a
>
> I ran a sql query both on the publisher and the subscriber that is
> sending the error message, couldn't find anything in the device table
> for this one:
> admin:run sql select * from device where name="SEP0011211161EE"
> It just returns an empty set. How can there be a device type mismatch
> if there is nothing in the database for it?
>
>
>