Sofware-Defined Networking

Reply
New Contributor
Posts: 2
Registered: ‎03-25-2015

Unable to login from other PCs not bvc VM

Hello,I need your help here.

 

I install the bvc on VM of esxi.It has a public IP.

 

I can open the site "http://{IP}:9000" from other PCs which can route to the bvc VM.But when I login with admin/admin,it always says "Unable to login".

 

At the same time,I try to login with the firefox explorer on bvc VM.It appears everything is ok.I can logon with admin/admin.

 

I want to know why I cant login from other PCs?

 

What's the different between the two ways?

 

And how can I fix it?I want to login from other PCs not bvc VM.

 

Thanks.

Brocadian
Posts: 2
Registered: ‎04-27-2011

Re: Unable to login from other PCs not bvc VM

Try making sure the hostname where the controller is running is resolvable on the PC you are accessing it from - not a problem if everything is in DNS but if you are trying things in a lab add the hostname to your PC's host file (\windows\system32\drivers\etc\hosts). I don't think it is a controller specific issue since after upgrading the OS I ran into this with a previous version of the controller that I didn't experience this problem with. I used this method to gain access to 1.2.0 as well. 

New Contributor
Posts: 2
Registered: ‎03-25-2015

Re: Unable to login from other PCs not bvc VM

Thank you reply.

 

The environment is that:

1、bvc is running on ESXI with Ubuntu 12.04 and bvc1.2.0, it has IP 192.168.1.10/24 gateway 192.168.1.1

2、PC is running windows,it has IP 192.168.1.2/24 same gateway

3、PC can ping bvc and load http://192.168.1.10/9000,the site is normal.

4、Login with admin/admin,it appears “unable to login”

5、Open vSphere Clint accessing to ESXI.On the console desktop of Virtual machine named bvc open firefox explorer http://192.168.1.10/9000,it can login use admin/admin.

6、I think there isnot something wrong about DNS.It should be connected by IP.

 

It puzzled me.

Brocadian
Posts: 2
Registered: ‎04-27-2011

Re: Unable to login from other PCs not bvc VM

If you are saying you can ping the BVC controller VM by name from your PC then your issue isn't the same as mine was. If you are just pinging by IP address then it still could be the issue. I believe there is some type of name resolution done duing the connection for security purposes. It doesn't hurt to try to put 192.168.1.10 with the name of the VM (hostname) in your windows' host file to see if that fixes your issue as it did for me.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook