Nortel Networks NN43001-121 manual MCM log file output, MCM Event log

230Troubleshooting

To turn off MCM logging, see "Resetting MCM debug trace" (page 231).

MCM log file output

The following shows a snippet from the log output file:

12/14/2007 11:11:37 AM: 3.0.1.76: Debug: OnCustomCom-

mand: got command: update config data

12/14/2007 11:11:38 AM: 3.0.1.76: Debug: Configura- tionData:

ReadConfigFile: Invalid secondary NRS address: 0.0.0.0

12/14/2007 11:11:38 AM: 3.0.1.76: Debug: Configura- tionData:

ReadConfigFile: Invalid LDAP server IP address: 0.0.0.0

12/14/2007 11:11:38 AM: 3.0.1.76: Debug: ServerEven-

tHandler: got Event #2

12/14/2007 11:11:38 AM: 3.0.1.76: SIP and Debug: NRSPolling:

sendPolling: request sent to the Primary NRS

12/14/2007 11:11:38 AM: 3.0.1.76: Debug: AD Cache: turning off

12/14/2007 11:11:38 AM: 3.0.1.76: Debug: AD Cache: it has been turned off

12/14/2007 11:11:38 AM: 3.0.1.76: Debug: ServerEven-

tHandler: got Event #3

12/14/2007 11:11:38 AM: 3.0.1.76: SIP and Debug:

NRSPolling: pollingResponseHandler SIP/2.0 200

via: SIP/2.0/TCP 47.11.56.54:4616;branch=z9hG4bK- 422726df-8d69b1-2ac0;received=47.11.56.54

from: <sip:MCM@ocs2007a.corp.nortel.com>;tag=a7fdb8be- c10b-44ef-9bf8-b9f6233cecb5

to: <sip:MCM@ocs2007a.corp.nortel.com>;tag=18892

call-id: 0000000-00000000-0000-00000000-000002-0000

cseq: 6 REGISTER

contact: < sip:MCM@ocs2007a.corp.nortel.com:5060>;ex- pires=300;maddr=47.11.56.54;Transport=TCP

expires: 300

content-length: 0

MCM Event log

MCM Exceptions and failures are reported in System Event Log. The following shows an example event log:

Nortel Communication Server 1000

Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Copyright © 2005–2008, Nortel Networks