Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

mds process dies on VRU-PG whenever the server is restarted

Hi Team,

I have an issue with a newly installed PG-VRU whenever I reboot the windows 2003 operating system.

Whenever I set the PG's node manager - Cisco ICM pft PG7B - to "automatic startup"  and reboot the server, the MDS service dies on windows restart.

However if I set  the PG's node manager to "manual startup" and reboot the server, and then whenever I logon into the windows' session and manually start the he PG's node manager using the "Unified CCE Service Control" the server works perfectly well with all its services up and running.

I have captured the MDS trace bellow, but I am not sure where/how to address the issue. As a final remark, the PG is on a remote site and I don't know if there is any race condition related to the network environment.

Thank you for your help !

 

Regards

Nick

---------------------------------------------------------------------------------------------------------------------

18:40:06:218 PG7B-mds Initializing Event Management System (EMS) Library.

18:40:06:234 PG7B-mds Trace: EMS Server pipe pft\PG7B\mdsEMSPipe enabled for pft\PG7B\mds

18:40:06:234 PG7B-mds Initializing Node Manager Library.

18:40:06:234 PG7B-mds Trace: Monitor Server pipe pft\PG7B\mdsCmdPipe enabled for pft\PG7B\mds

18:40:06:234 PG7B-mds Trace: Node Manager ping received.

18:40:06:234 PG7B-mds Trace: EMT I/O completion ports: max threads=16, concurent threads=0

18:40:06:234 PG7B-mds Trace: Router Staggering Feature: Disabled

18:40:20:484 PG7B-mds Cannot resolve MDS process "MDSPort" address (node csopftpg7bp, port 43000).

  Last EMT Error [11004]: The requested name is valid, but no data of the requested type was found.

18:40:20:484 PG7B-mds Fail: Unable to read MDS process configuration data.

  Last API Error [997]: Overlapped I/O operation is in progress.

18:40:20:750 PG7B-mds Trace: CExceptionHandlerEx::GenerateMiniDump -- A Mini Dump File is available at logfiles\mdsproc.exe_20140317184020562.mdmp

18:40:21:156 PG7B-mds Unhandled Exception: Exception code: 80000003 BREAKPOINT

Fault address:  7C81A229 01:00019229 C:\WINDOWS\system32\ntdll.dll

Registers:

EAX:00000000

EBX:77E67859

ECX:7FFDF000

EDX:0048B018

ESI:0012F5A4

EDI:7C81A1A8

CS:EIP:001B:7C81A229

SS:ESP:0023:0012E8A4  EBP:00000001

DS:0023  ES:0023  FS:003B  GS:0000

Flags:00000246

 

Call stack:

Address   Frame

7C81A229  00000001  DbgBreakPoint+0

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
New Member

just notice the error

just notice the error message

18:40:20:484 PG7B-mds Cannot resolve MDS process "MDSPort" address (node csopftpg7bp, port 43000).

 

is the DNS server or host resovle issue for csopftpg7bp?

4 REPLIES
Silver

How many PGs are you running

How many PGs are you running on this particular server?

New Member

There is only one PG, but I

There is only one PG, but I have configured 2 PIMS (there will be 2 additionnal PIM I intend to configure)

New Member

just notice the error

just notice the error message

18:40:20:484 PG7B-mds Cannot resolve MDS process "MDSPort" address (node csopftpg7bp, port 43000).

 

is the DNS server or host resovle issue for csopftpg7bp?

New Member

Hi George, Finally the issue

Hi George,

 

Finally the issue was related to a name resolution issue.

I addressed the name resolution and the PG is now working normally whenever I reboot the server.

 

Regards

 

Nick

 

 

306
Views
0
Helpful
4
Replies