Software Defined Networking
cancel
Showing results for 
Search instead for 
Did you mean: 

Login Failure on SDN Controller 2.3

 
SOLVED
Go to solution
Highlighted
Occasional Advisor

Login Failure on SDN Controller 2.3

Hi all,

 

First, a bit of background.  I've been tasked with the deployment and demo of HP's SDN environment, and up until today I've had a reasonable amount of success with that.  The earlier versions of the controller deployed without a hitch, and the OF configuration on the switches was painless (a term I take very seriously in anything IT).  However, upon updating to 2.3, I'm finding myself stymied by a problem that I can't quite wrap my head around.

 

I started from scratch, followed the flowchart, and did everything per direction.  I created the Keystone 'sdn' user by hand and assigned its role and tenant, and I'm fairly confident that's working as it's supposed to.  More over, I'm also fairly certain that the Opeflow switching backend is working as it's supposed to as well, because a quick 'show openflow instance aggregate' shows a status of 'Connected' on every switch I'm trying to utilize.

 

The catch?  I can't get past login authentication.

 

No, before you ask, this is not a Keystone issue.  I can type fake usernames and passwords and get "invalid username/password" errors all day long.  The issue is the fact that when I log in with the correct creds that I generated through Keystone, it redirects me to 'https://<ip>:8443/sdn/ui/app/login' and stalls out completely.  Refreshes fail, other browsers fail, I can't see anything.

 

Worse yet, a quick Google search shows me a few other users experiencing a similar problem, but no tangible solution or explanation for the issue.

 

So I turn to you, O SDN experts, to help me claw through the fog.  What do I do??

 

 

-Rob

8 REPLIES 8
Highlighted
Occasional Advisor

Re: Login Failure on SDN Controller 2.3

I apologize, I broke the golden rule of support threads.  I should provide some specifics.  I behaved myself and used Ubunutu Server LTS 12.04 per instruction, I synced to an NTP server, I'm using the Icehouse repo for Keystone, my browser of choice is Chrome (up to date), but I've also tested on IE 10 with no success.

 

My SDN version is the most recent as of the 1st of October (apologies, I don't have a version number right in front of me... 2.3.0.5000 something?).

 

 

-Rob

Highlighted
Occasional Advisor
Solution

Re: Login Failure on SDN Controller 2.3

I have resolved this problem.  While I was correct in the assertion that the problem was not related to Keystone authentication, I was slightly inaccurate in that it wasn't related to Keystone at all.  Apparently this is some sort of glitch on newer versions of Keystone.  My problem directly related to the newest Icehouse release.  The newest deployment guides imply that any version of Keystone should do the trick, but upon removing Icehouse and backing down to Folsom (a build that I had validated in an earlier test), the problem vanished entirely.

 

Odd, but resolved nonetheless.

Highlighted
Trusted Contributor

Re: Login Failure on SDN Controller 2.3

Hello Rob,

 

We are glad that your problem is solved.

Please do let us know if you need further assistance.

 

Please feel free to reply incase you have more questions around the same topic or open a new thread if new topic.

 

Thanks

HP SDN Team

Highlighted
Frequent Advisor

Re: Login Failure on SDN Controller 2.3

Hi SDN TEAM,

 

Good day,

 

I am not able to access the controller UI,

When I enter the  https://controller_ip_address:8443/sdn/ui/ (where the IP address is the address of server, where I have installed controller), I am not able to access it.

 

I get the error as Unable to connect. Using Firefox browser in the server.

 

Regards,

Satish

 

Highlighted
Trusted Contributor

Re: Login Failure on SDN Controller 2.3

Hello Satish,

 

Please provide/confirm the below details-

1. Did you install the version 2.3 a fresh or upgrade from older version?

2. What is the keystone version?

3. Command used to install keystone?

4. Are you able to see REST API page?

5. Did you try with Google chrome ? Chrome is recommended.

6.Please share the screen shot for SDN UI page as well as controller logs if possible.

 

Thanks,

HP SDN Team

Highlighted
Frequent Advisor

Re: Login Failure on SDN Controller 2.3

Hi,

Thanks for the update,

Please find the details below

 

1. Did you install the version 2.3 a fresh or upgrade from older version?
Yes, I Did a fresh installation of 2.3


2. What is the keystone version?

$keystone --version
0.7.1 (Icehouse)


3. Command used to install keystone?
$ sudo add-apt-repository "deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/icehouse main"
$ sudo apt-get install keystone

 

4. Are you able to see REST API page?
Do you mean Controller api page ? https://controller-IP:8443/api
then No, I am not able to access this page too.

5. Did you try with Google chrome ? Chrome is recommended.
I dint tried with crome, I am not able to install crome in my server due to proxy restriction.
When I tried to install chrome it says refusing by the proxy server.

 

6.Please share the screen shot for SDN UI page as well as controller logs if possible.
I have shared the screenshot, for logs I will do, as they are at the servers.

 

Regards,

Satish K

Highlighted
Frequent Advisor

Re: Login Failure on SDN Controller 2.3

Also please note that,

the same prob with https://<controller_IP>:8443/sdn/v2.0/models

 

I can able to ping to the controller, from its terminal.

 

 

Highlighted
Advisor

Re: Login Failure on SDN Controller 2.3

Your situation might be explained in this thread:

 

http://h30499.www3.hp.com/t5/SDN-Discussions/Login-Failure-on-SDN-Controller-2-3/td-p/6637726#.VEVDivldUbx

 

Also, have you tried the following (from another Linux host, substitute the IP address of your controller) :

 

curl -sk -H 'Content-Type:application/json' -X POST https://15.234.166.46:8443/sdn/v2.0/auth -d '{ "login": { "user": "sdn", "password": "skyline" }}' | python -mjson.tool

 

If you see output similar to this:

 

sreeve@ubuntuIBM346:~/restapi$ curl -sk -H 'Content-Type:application/json' -X POST https://15.234.166.46:8443/sdn/v2.0/auth -d '{ "login": { "user": "sdn", "password": "skyline" }}' | python -mjson.tool
{
    "record": {
        "domainId": "",
        "domainName": "",
        "expiration": 1413890192000,
        "expirationDate": "2014-10-21 04-16-32 -0700",
        "token": "282ad1298bd54ecba7a9c39a0ec12c61",
        "userId": "0d5ab62aeb8f41389889fe7b0c9819e2",
        "userName": "sdn"
    }
}

 

 

I.e. if you're given a valid "token" or perhaps an "authentication required" message.

 

Regards,

 

Scott