CallMgr Troubleshooting Day Three

CallMgr Troubleshooting Day Three - Tracing Change...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Tracing Change Notification In 5.x and 6.x database change notification is a critical process to understand and it has several steps: 1. Update is done on the web page 2. Information written to tables in IDS database 3. Db change message is inserted into DBLCnQueue in Dbmon application 4. Dbmon sends the change to all subscribed applications through tcp connection on port 8001 (step 4 can be over the network in 5.x but is always local in 6.x) Tracing Change Notification 5. The DbNotify process inside CallManager sends the update message to the appropriate internal processes inside the CallManager application. 6. The Db internal process inside CallManager may do a fresh database query and then send messages to other CallManager internal processes so they update their tables accordingly. Tracing Change Notification Tracing Change Notification Tracing Change Notification Example of setting CFA on a dn in 6.0(1) CallManager. These are the steps we will look at: 1. CFA changed on web page for dn 2010 from no setting to true setting and destination of 3010. 2. This database change is traced in the Dbmon traces 3. This database change is traced in the CallManager Dbnotify traces under Cisco Database Notification Service and the ccm folder 4. This database change is seen in the CallManager sdi and sdl traces Tracing Change Notificatoin 1. Here is the Dbmon trace generated by the web page update (this trace is in XML): filename = dbmon00000016.txt.. We see that the change is to the callforwarddynamic table and the action is an update (U) and the information changed is the cfadestination which was NULL and now is 3010. 08/26/2008 15:32:53 . 106 DbMon | < msg ><type> DBL </type>< table>callforwarddynamic</table ><tableid>434</tabl eid ><action>U</action ><time>1219782773</time> <old> <cdrserver>0</cdrserve r><cdrtime>1211387466</cdrtime ><pkid>9608a9f3-e6f7-4094-b625- daa7e0d3a1be</pkid><cfadestination>NULL</cfadestination> <fkcallingsearch space_cfa>NULL</fkcallingsearchspace_cfa><cfavoicemailenabled>f</cfavoicem ailenabled><fkcallingsearchspace_scfa>NULL</fkcallingsearchspace_scfa><fknu mplan>b6bc6fbb-8115-2e69-5cf9- 9d53817cab3c</fknumplan><datetimestamp>1206645668</datetimestamp></old > <new> <cfavoicemailenabled>f</cfavoicemailenabled> <cfadestination>3010</cf adestination> <fkcallingsearchspace_scfa>NULL</fkcallingsearchspace_scfa><fk callingsearchspace_cfa>NULL</fkcallingsearchspace_cfa><datetimestamp>1219 782772</datetimestamp></new></msg>| <CLID::StandAloneCluster><NID::nw035a-lnx2><LVL::Arbitrary><MASK::0002> Tracing Change Notification 2. Next we see the incoming change notification in the ccm dbnotify trace: (filename = dbnotify_ccm00000031.log). This is the same exact xml message as seen in the Dbmon traces. You can line these up exactly. If you see this it means that the change notification reached the CallManager application....
View Full Document

Page1 / 49

CallMgr Troubleshooting Day Three - Tracing Change...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online