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

Topology Services error

I performed a new installation of LMS 3.1 from a scratch standalone Windows 2003 server today. All data has been successfully backed up from my existing 3.0.1 version and then retored to 3.1 version after the new installation.

However, I'm still getting errors in launching Topology Services in Campus Manager of LMS 3.1 (see attached screen shot).

I also notice that the ANIServer process state is "running with busy flag set." from the process management interface. Is this related to above error?

Thanks,

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Topology Services error

What about "telnet JuJuba.test.local 42342"?

9 REPLIES
Cisco Employee

Re: Topology Services error

Please post the Java console output as well as the NMSROOT\MDC\tomcat\logs\stdout.log and ani.log.

Community Member

Re: Topology Services error

Here are Java console output screen shot and stdout.log file.

I didn't find ani.log under above location. Where should I locate it?

Community Member

Re: Topology Services error

Here is the ani.log

Cisco Employee

Re: Topology Services error

If you have a firewall between your client and server, make sure the client can connect to tcp/42342 on the server.

Community Member

Re: Topology Services error

I don't have any firewalls between the client and server.

It was working when I deployed LMS 3.0.1. I didn't changed IPs or physical boxes of client and server.

Cisco Employee

Re: Topology Services error

The underlying technology has changed. Can you verify you can telnet to the server on port 42342 from the client?

Community Member

Re: Topology Services error

I got a black screen as attached after I run command "telnet 192.168.130.179 42342".

Cisco Employee

Re: Topology Services error

What about "telnet JuJuba.test.local 42342"?

Community Member

Re: Topology Services error

It's different this time. I got "Connecting to Jujuba.test.local...Could not open connection to the host, on port 42342: Connect failed."

I checked DNS resolution of Jujuba.test.local on the client. It failed to resolve. So I went ahead and fixed the DNS issue on the client. The Topology Services can be launched right after that.

Thank you for great help!

231
Views
0
Helpful
9
Replies
CreatePlease to create content