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. And see here for current known issues.

New Member

Firewall ports for WCS to talk to controllers

I have a WCS on one side of a firewall, and a controller on the other side. What ports and protocols would I need to open in the firewall to allow the WCS to manage the controller? All I can find is info on what ports to open for a client to access the WCS. Thanks for any help!!

4 REPLIES
New Member

Re: Firewall ports for WCS to talk to controllers

I believe that you should only need to open the SNMP ports, which are 161 and 162 UDP.

New Member

Re: Firewall ports for WCS to talk to controllers

I contacted the TAC and this is what they came back with (and is working). Hope it helps somebody!

80: HTTP--optional

443:HTTPS

22: SSH

23: Telnet--optional

161: SNMP Get

162: SNMP Set

16666: Mobility Tunnel (UDP)

16667: Mobility Tunnel Secured.--optional (UDP)

New Member

Re: Firewall ports for WCS to talk to controllers

Very useful, but missing 69,21 which are used for TFTP/FTP

Re: Firewall ports for WCS to talk to controllers

When there is a conflicting port in use, WCS fails to get started with just the error message "Failed to start WCS Server." The WCS requires these ports to be available in the machine:

   *Checking for Port 1299 availability... OK
       *Checking for Port 80 availability... OK
       *Checking for Port 443 availability... OK
       *Checking for Port 8009 availability... OK
       *Checking for Port 8456 availability... OK
       *Checking for Port 8457 availability... OK
       *Checking for Port 8005 availability... OK
       *Checking for UDP Port 69 availability... OK
       *Checking for Port 21 availability... OK

Make sure that you do not run other applications on those ports, such as web server (80), TFTP Server (69), or FTP server (21). On a WCS installed on linux, go to WCS/webnms/logs/wcs-0-0.log and look for the conflicting ports. On Windows based WCS, you can run netstat -a from a DOS window to see the listening ports that are used. If this is the case, shut them down and try to restart WCS.

695
Views
10
Helpful
4
Replies
CreatePlease login to create content