WCS services

Answered Question
Mar 16th, 2010

Good day!

I need some help about WCS 6.0, I installed it on a virtual machine with Windows Server 2003 in which previously have installed CiscoWorks. I have this PC just for testing purposes so it's not a dedicated server. My question is what services are from WCS, because when I try to run WCS first I stop all the services related to CiscoWorks for avoiding any conflict but I think i'm missing some for WCS.

Thanks in advance for any help!

I have this problem too.
0 votes
Correct Answer by sschmidt about 6 years 8 months ago

Are you seeing a port conflict and WCS is not starting?

You can check the launchout.txt file to see what is still bound.

This is a succesful startup showing the ports WCS needs available:

Checking for Port 21 availability... OK
Checking for Port 8456 availability... OK
Checking for Port 8457 availability... OK
Checking for Port 1299 availability... OK
Checking for local Port 1299 availability... OK
Checking for Port 6789 availability... OK
Checking for local Port 6789 availability... OK
Checking for UDP Port 69 availability... OK
Checking for Port 8005 availability... OK
Checking for UDP Port 162 availability... OK
Checking for Port 8009 availability... OK
Starting RMI registry on port 1299
Registry started.
DB is already started
Starting NMS Server...
NMS Server Started.
Starting up TFTP server...
TFTP Server started.
Starting up FTP server
Started FTP
FTP Server started
Apache server is already started
Starting Tomcat server ...

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
sschmidt Tue, 03/16/2010 - 09:34

Are you seeing a port conflict and WCS is not starting?

You can check the launchout.txt file to see what is still bound.

This is a succesful startup showing the ports WCS needs available:

Checking for Port 21 availability... OK
Checking for Port 8456 availability... OK
Checking for Port 8457 availability... OK
Checking for Port 1299 availability... OK
Checking for local Port 1299 availability... OK
Checking for Port 6789 availability... OK
Checking for local Port 6789 availability... OK
Checking for UDP Port 69 availability... OK
Checking for Port 8005 availability... OK
Checking for UDP Port 162 availability... OK
Checking for Port 8009 availability... OK
Starting RMI registry on port 1299
Registry started.
DB is already started
Starting NMS Server...
NMS Server Started.
Starting up TFTP server...
TFTP Server started.
Starting up FTP server
Started FTP
FTP Server started
Apache server is already started
Starting Tomcat server ...

karlareyes Tue, 03/16/2010 - 10:47

Hi!

I checked that file and yes it was having some issues with some ports that then I fixed, now the WCSStatus shows that all is OK, but I still can not load it on browser.

launchout output:

Checking for Port 21 availability... OK

Checking for Port 8456 availability... OK

Checking for Port 8457 availability... OK

Checking for Port 1299 availability... OK

Checking for local Port 1299 availability... OK

Checking for Port 6789 availability... OK

Checking for local Port 6789 availability... OK

Checking for UDP Port 69 availability... OK

Checking for Port 8005 availability... OK

Checking for UDP Port 162 availability... OK

Checking for Port 8009 availability... OK

Starting RMI registry on port 1299

Registry started.

DB is already started

Starting NMS Server...

Creating schema.  This may take a minute.

Creating Predefined ACL Protocols

Schema is successfully created.

NMS Server Started.

Starting up TFTP server...

TFTP Server started.

Starting up FTP server

Started FTP

FTP Server started

Starting Apache server ...

Apache server is running.

Starting Tomcat server ...

Tomcat server is running.

hm_launchout output:
Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
Starting WCS Server
WCS server started successfully.
Don't know what else could be the problem now?
Thanks for your help
karlareyes Tue, 03/16/2010 - 11:08

Hey man! now it's working

I was just using the default shortcut that it is on desktop and it opened: http://computername:1741/ so it wasn't working.

With the http://localhost:80 and then redirect to 443 it's working. Just a quick question why the shorcut points to that?

Thanks a lot and have a very nice day

Lucien Avramov Tue, 03/16/2010 - 11:15

1741 is the port used for LMS. WCS uses port 443.

You were probably using the ciscoworks shortcut.

sschmidt Tue, 03/16/2010 - 11:17

Right click the shortcut and check the target.  Is it pointing to LMS or WCS?

karlareyes Tue, 03/16/2010 - 13:15

Oh sorry, yes I was wrong, I was clicking on LMS shortcut, i need a big cup of coffee...

Lucien Avramov Tue, 03/16/2010 - 10:56

I remember that apache services needs to get re registered if you have more than one app using tomcat, which you do with LMS and WCS.

Can you send the apache logs from WCS?

karlareyes Tue, 03/16/2010 - 13:18

Is it that possible when I have both apps using tomcat? How can you do that? Which logs exactly do you need bc I found many...

sschmidt Tue, 03/16/2010 - 17:47

WCS is supposed to run on a server by itself and is not supported running with LMS also.

karlareyes Tue, 03/16/2010 - 20:03

Thanks for all your help! This is a great community keep up this good work...

Actions

This Discussion

Related Content

 

 

Trending Topics - Security & Network