[cisco-voip] CCM 3.3(3) RTMT and server process info
Wes Sisk
wsisk at cisco.com
Tue Jul 11 19:24:31 EDT 2006
in that case..
the IIS pages establish a WMI session to the remote server to check
the status of services. You can most closely simulate this by:
right click on 'my computer' on the publisher and select manage
right click on computer management at the top of the tree and select
'connect to another computer'
specify the destination by \\<computername> or \\<ipaddress>
does this connection work? can you manager services on the remote
server through this interface?
/Wes
On Jul 11, 2006, at 11:39 AM, Erick Bergquist wrote:
Already have compared all services on all nodes, hosts/LMHOSTS files,
etc. The remote registry service is started and has been restarted.
Reboots done many times.
----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Tuesday, July 11, 2006 7:45:11 AM
Subject: Re: [cisco-voip] CCM 3.3(3) RTMT and server process info
I believe this is caused by the 'remote registry service' being
deactivated on that node. If not that one, then one of the services
are not running that need to be. dump the running services on each
node and compare.
/Wes
On Jul 9, 2006, at 11:16 PM, Erick Bergquist wrote:
Got a strange issue here with a 3.3(3) cluster and RTMT. RTMT works
fine on all 3 nodes in the cluster and is able to pull up performance
counter information fine, etc. On one node however, the cluster
information and process information is not available through RTMT and
on the process activity window it is just blank. On the call manager
cluster info window for this node/server it has "Error" for the
values it is getting from the process info or on stuff where it is
looking at those items. Values in the cluster info window are
reported correctly if they come straight from the perfmon counters.
Stuff that has "Error" are uptime values, and percentage values, etc.
Anyone have any ideas on where to go with this, or seen this before?
I have a TAC case open for a few weeks also. CCM 3.3(3)es72 and OS
2000.4-2sr8. Had same issue with OS 2000.2-7sr7 and previous CCM
versions. Not sure if this was working before as it was noticed
recently. Just would like to try to get it fixed and figured out
since the servers are older.
Thanks, Erick
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list