- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- VAN not listening on port 8443 after install
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2015 02:38 AM
тАО04-20-2015 02:38 AM
VAN not listening on port 8443 after install
Hi,
we are trying to get 2.5 running on another box and are having similar issues to the people above. VAN doesn't want to bind to ipv4 8443. The VM has 9 GB ram and 4 vCPUs. See requested output below. This is a fresh install of Ubuntu 12.04
uname -a
Linux hyperglance 3.13.0-32-generic #57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ sudo service sdnc status
sdnc start/running, process 1093
$ sudo service sdna status
sdna start/running, process 1096
$ sudo service keystone status
keystone start/running, process 1100
$ sudo dpkg -l | grep -i sdn
ii hp-sdn-ctl 2.5.11.1149 HP VAN SDN Controller
hyperglance@hyperglance:~$ sudo dpkg -l | grep -i keystone
ii keystone 1:2014.1.4-0ubuntu2~cloud0 OpenStack identity service - Daemons
ii python-keystone 1:2014.1.4-0ubuntu2~cloud0 OpenStack identity service - Python library
ii python-keystoneclient 1:0.7.1-ubuntu1~cloud0 Client library for OpenStack Identity API
$ netstat -na | grep 8443
tcp6 0 0 :::8443 :::* LISTEN
tcp6 38 0 127.0.0.1:54266 127.0.0.1:8443 CLOSE_WAIT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2015 08:47 AM
тАО04-20-2015 08:47 AM
Re: VAN not listening on port 8443 after install
The output of the netstat command does indicate that the server is listening on port 8443 for both IPv4 and IPv6. I see the same output on my server and it is working beautifully.
I believe the issue is that many browser updates have disabled the use of DSS based certificates and that is what the controller installs by default as a self-signed cert.
Try Internet Explorer as it hasn't removed support for these certs yet.
And stay tuned for a doc to be published on how to update the self-signed cert using RSA. Or look at this post:
- Tags:
- certificate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-28-2015 10:25 AM
тАО04-28-2015 10:25 AM
Re: VAN not listening on port 8443 after install
I also encountered the same symptoms when initially attempting to upgrade from v2.4 to v2.5 and subsequently when attempting a clean install on 12.04 ubuntu.
What did work on a clean install was NOT creating the sdn user during initial setup of ubuntu. Instead, use ubuntu/ubuntu (or something other than sdn/password) to install Linux. After successfully installing Linux, login to the ubuntu account to unpack and install the HP SDN Controller software.
This allows the installation process to create the sdn user with the correct attributes and permissions.