topic Re: SDN Controller is not listening on port TCP/8443 in Software Defined Networking

SDN Controller is not listening on port TCP/8443

drabbert — Fri, 28 Nov 2014 07:27:15 GMT

I did a fresh install of the HP SDN Controller software:

-ubuntu-14.04.1-server-amd64

-VAN_SDN_Controller_2.4.5_hp-van-sdn-ctlr-2.4.5-x64

- No errors during the installations,

- all services are running

- I've restarted the server after intsallation

But the system is not listening on port tcp/8443

What could be wrong and what is the best approach to troubleshoot this problem?

Thanks,

Erwin

Re: SDN Controller is not listening on port TCP/8443

piricchio72 — Fri, 28 Nov 2014 09:42:18 GMT

Hi,

As from the installation giude HP:

HP VAN SDN Controller This guide describes the steps for installing the HP VAN SDN (Virtual Area Network Software-Defined Networking) Controller software on a system running Ubuntu version 12.04 LTS 64-bit server.

I would suggest you to try to install the controller on Ubuntu 12.04

Let me know if further assistence is needed.

Regards,

Antonio

SDN CoE Team

Re: SDN Controller is not listening on port TCP/8443

vdeolali — Thu, 04 Dec 2014 22:06:33 GMT

On Ubuntu 12.04 it does not work either.

Both sdna and sdnc are running

No process is listening on :8443

the url https://x.x.x.x:8443/sdn/ui does not land anywhere.

Re: SDN Controller is not listening on port TCP/8443

piricchio72 — Fri, 05 Dec 2014 09:46:26 GMT

Hello,

I would like to know more about your issue.

Which version of Java are you running?

Please run following command on your server:

sudo update-java-alternatives -l

and copy the output of the command:

ps -ef | grep java

Also

Is the controller listening on port 6633?

Are you able to to retrieve an authentication token via curl?

Did you try to restart controller services?

Did you install a GUI on the server?

Is this a VM or a bare metal installation?

When trying to reach the controller interface, what happens to the page?

Does it times out? Error messages?

Did you check controller log?

Reagards,

Antonio

SDN CoE Team

Re: SDN Controller is not listening on port TCP/8443

Scott Simpson — Wed, 14 Jan 2015 17:53:27 GMT

Hi Antonio,

Apologises for hi-jacking this thread but I am having the same issue setting up the SDN controller in our lab for testing and demo purposes.

After a successful install using hp-sdn-ctl_2.4.5.0614_amd64.deb and the install guide 2.4.5 I am unable to browse to https::/<ip-address>/sdn/ui

My details are:

sudo service sdnc status
= shows start/running, process 849

sudo service sdna status
= shows start/running, process 855

sudo update-java-alternatives -l
java-1.6.0-openjdk-amd64 1061 /usr/lib/jvm/java-1.6.0-openjdk-amd64
java-1.7.0-openjdk-amd64 1051 /usr/lib/jvm/java-1.7.0-openjdk-amd64

ps -ef | grep java
sdnadmin 879 855 0 17:26 ? 00:00:05 /usr/lib/jvm/java-7-openjdk-amd64/bin/java -Xms64m -Xmx512m -Dcom.hp.sdn.admin.interface=eth0 -jar sdn-adm-admin-2.4.5.jar
1000 1840 1734 0 17:40 pts/0 00:00:00 grep --color=auto java

sudo dpkg -l hp-sdn-ctl
Shows as flag "ii" so installed OK

sudo netstat -atupvn | grep 8443
Shows no entry and cannot telnet to IP on port 8443 so it is not listening

Answers to the other things I know how to do are:

Is the controller listening on port 6633? Not from what I can tell.

Did you try to restart controller services? Yes, and rebooted VM via sudo reboot now (no errors on boot up) and rebooted the VM as well

Is this a VM or a bare metal installation? VMware, 8GB RAM, 64GB disk, quad-core. Using Ubuntu 12.04 LTS 64-bit as per install details

When trying to reach the controller interface, what happens to the page? Nothing. Port is not open.

Any ideas??? HELP!

Re: SDN Controller is not listening on port TCP/8443

piricchio72 — Wed, 14 Jan 2015 18:55:25 GMT

Hi Scott,

I suspect java version may play a role.

can you run following:

dpkg -l | grep jre

and make sure you only have version 7 installed.

I would also try to reach the RSdocs interface and check whether you manage to get an authentication token.

Regards,

Antonio

SDN CoE Team

Re: SDN Controller is not listening on port TCP/8443

Scott Simpson — Wed, 14 Jan 2015 20:11:30 GMT

Hi Antonio,

OK, I will try that tomorrow morning when back at work (at home now - 8pm uk time) and will report back .

From memory I have only ran "sudo apt-get install openjdk-7-jre-headless" but will check, uninstall anything else and also check RSDocs (although it looks like no ports are open anyway).

Will post tomorrow...... Scott

Re: SDN Controller is not listening on port TCP/8443

Scott Simpson — Wed, 14 Jan 2015 22:24:14 GMT

Remoted into our lab..... results of the command:

sdn@ubuntu:~$ dpkg -l | grep jre
ii openjdk-7-jre-headless - 7u71-2.5.3-0ubuntu0.12.04.1 - OpenJDK Java runtime, using Hotspot JIT (headless)

So only one Java version installed.

I cannot get to RSdocs on /api or Virgo on /admin as nothing on port 8443 is running even though both sdnc and sdna services are running the install goes through without error. Other ports are open as you can remote onto the server via SSH (openssh-server) and FTP (ftpd) when installed.

I have just followed the instructions word for word and ran each command seperately on my laptop (which is Hyper-v so unsupported) but exactly the same issue on our lab VMware.

I don't understand why sdna and sdnc are running, the dpkg -l shows as "ii", no errors in logs but nothing on port 8443 is open on the server. I am obviously doing something completely wrong or missed a step. What other services should be running?

Here all the log files I can find:

sdn@ubuntu:~$ sudo tail /var/log/sdn/virgo/logs/log.log
[2015-01-14 21:52:59.154] INFO AdmDao-1-thread-1 hp.sdn.db Creation of new DataStoreService
[2015-01-14 21:52:59.422] INFO AdmDao-1-thread-1 c.n.astyanax.connectionpool.impl.ConnectionPoolMBeanManager Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,name=HP VAN SDN Controller_sdnctl_db,ServiceType=connectionpool
[2015-01-14 21:52:59.423] INFO AdmDao-1-thread-1 c.n.astyanax.connectionpool.impl.CountingConnectionPoolMonitor AddHost: 127.0.0.1
[2015-01-14 21:52:59.458] INFO AdmDao-1-thread-1 hp.general Keyspace does not exist
[2015-01-14 21:53:00.142] INFO AdmDao-1-thread-1 hp.general KeySpace Created
[2015-01-14 21:53:00.145] INFO iLogServiceListener@4cab0ac0 org.osgi.service.log.LogService Bundle com.hp.sdn.sdn-adm-dao_2.4.5, Service 349, ServiceEvent REGISTERED
[2015-01-14 21:53:23.479] WARN ros-csync-16-thread-1 hp.sdn.role DE0005I DatapathCacheBuilder: no dpinfos from controller
[2015-01-14 21:55:22.483] INFO TaskExecSched-3-thread-13 hp.sdn.general DE0005I LicenseSupportRunner thread started
[2015-01-14 21:55:22.498] INFO TaskExecSched-3-thread-13 hp.sdn.general DE0005I HP VAN SDN Ctrl Base-active base product license is not found, product license compliance failed!, licensing system posted alerts
[2015-01-14 21:55:22.499] INFO TaskExecSched-3-thread-13 hp.sdn.general DE0005I License history log file serviceability/logs/license-history.log created successfully
END

sdn@ubuntu:~$ sudo tail /var/log/sdn/virgo/stdout.log
[2015-01-14 21:52:36.614] start-signalling-4 <DE0005I> Started bundle 'com.hp.sdn.sdn-ctl-node' version '2.4.5'.
[2015-01-14 21:52:36.615] start-signalling-4 <DE0005I> Started plan 'com.hp.sdn.ctl.nodemgr' version '2.4.5'.
[2015-01-14 21:52:37.011] app-mgr <DE0000I> Installing plan 'com.hp.sdn.ctl.diag' version '2.4.5'.
[2015-01-14 21:52:37.028] app-mgr <DE0000I> Installing bundle 'com.hp.sdn.sdn-ctl-diag' version '2.4.5'.
[2015-01-14 21:52:37.078] app-mgr <DE0001I> Installed bundle 'com.hp.sdn.sdn-ctl-diag' version '2.4.5'.
[2015-01-14 21:52:37.087] app-mgr <DE0001I> Installed plan 'com.hp.sdn.ctl.diag' version '2.4.5'.
[2015-01-14 21:52:37.093] app-mgr <DE0004I> Starting plan 'com.hp.sdn.ctl.diag' version '2.4.5'.
[2015-01-14 21:52:37.094] app-mgr <DE0004I> Starting bundle 'com.hp.sdn.sdn-ctl-diag' version '2.4.5'.
[2015-01-14 21:52:37.152] start-signalling-4 <DE0005I> Started bundle 'com.hp.sdn.sdn-ctl-diag' version '2.4.5'.
[2015-01-14 21:52:37.153] start-signalling-4 <DE0005I> Started plan 'com.hp.sdn.ctl.diag' version '2.4.5'.
END

sdn@ubuntu:~$ sudo tail /var/log/sdn/admin/stdout.log
Jan 14, 2015 9:51:36 PM org.glassfish.grizzly.http.server.NetworkListener start
INFO: Started listener bound to [0.0.0.0:8081]
Jan 14, 2015 9:51:36 PM org.glassfish.grizzly.http.server.HttpServer start
INFO: [HttpServer] Started.
Jan 14, 2015 9:51:36 PM org.glassfish.grizzly.servlet.WebappContext deploy
INFO: Starting application [context] ...
Jan 14, 2015 9:51:36 PM org.glassfish.grizzly.servlet.WebappContext initServlets
INFO: [context] Servlet [com.sun.jersey.spi.container.servlet.ServletContainer] registered for url pattern(s) [[/*]].
Jan 14, 2015 9:51:36 PM org.glassfish.grizzly.servlet.WebappContext deploy
INFO: Application [context] is ready to service requests. Root: [].

END

Re: SDN Controller is not listening on port TCP/8443

piricchio72 — Thu, 15 Jan 2015 11:59:32 GMT

Hi Scott,

Can you post the ouput of following command:

sudo cat /var/log/sdn/virgo/logs/log.log | grep -i except

Are you using a local Keystone or a remote one?

If not remember about Setting the provider type to UUID on the remote Keystone server.

Also, are you working under a proxy?

I just installed from scratch version 2.4.5 without issues and now testing using mininet.

Regards,

Antonio

SDN CoE Team

Re: SDN Controller is not listening on port TCP/8443

lirf — Tue, 20 Jan 2015 12:53:38 GMT

Hi,

I've got the SDN controller running in Hyper-V on 14.04 and also had a problem with the sdnc service showing as started, but port 8443 not listening.

The problem was caused because I had not assigned enough resource to the controller - it needs 4x CPU and 8GB RAM

It also seemed to take between 5-10 minutes to start, slower than 12.04, and I found myself restarting the service before I'd given it chance to start properly.

(Fyi - I used the juno cloud archive)

Phil

Re: SDN Controller is not listening on port TCP/8443

Scott Simpson — Wed, 21 Jan 2015 12:26:29 GMT

Hi Phil and Antonio, YES! More resources and more patience required.

I have the controller up and Lync SDN Optimizer App installed and OpenFlow running all OK.

I have installed LDL on Lync Front server and that is sending information to LSM server OK. Logs look good.

The only issue I have left is that the LSM service is not sending data to the VAN SDN controlller. You have to enter a submituri on the config file (or during the installer) which from the documentation is the HP VAN SDN Controller but what URL is required?

I cannot find anything in docs to show what the correct URL should be.....?????

(So LSM log file reports Transmission Error - cannot connect to remote server)

Have tried http://<ip address of HP VAN SDN>/ with and without port number 8443 and https etc

What should this be?

Re: SDN Controller is not listening on port TCP/8443

piricchio72 — Wed, 21 Jan 2015 16:31:11 GMT

Hello Scott,

I would like to ask you whehter the service is running in the first place (Lync SDN Manager).

If not, please, try to start the service.

Concerning the submit uri you should add, it should be :

https://VAN_CONTROLLER_HOSTNAME:8443/sdn/lyncqos/v1.0/session

(as from latest guide for version 1.2.6)Did you add this URL?

I would anyway suggest to open a new topic in the forum as this is has nothing to do with the subject.

I may want to contact support if you are deploying the solution in a production environment.

Regards,

Antonio

SDN CoE Team