| Author |
Message
|
| GeneRK4 |
 Posted: Thu Dec 04, 2014 7:32 pm Post subject: Unable to open WebUI of IBM MessageSight Virtual appliance |
 |
|
Master
Joined: 08 Jul 2013
Posts: 220
|
Hi,
I have setup IBM MessageSight Virtual Appliance in my PC.
I am not able to open webui with the address as "https://192.0.2.0:9087/".
As some initialtroubleshooting steps,I tried to ping the IP.
ping 192.0.2.0
But I am getting Request Timedout.
Suspecting for Firewall issues,I tried to get into ControlPanel-->Windows Firewall-->Advanced settings-->Inbound rules--> VMWare Authd service and disabled the rule and also made as public.
I tried to change the VMWare settings -->Network Adapter as NAT from Bridged.
I tried to restart the imaserver.It displays message as "IBM Messagesight is fully functional until you accept license from the WebUI.Use one of the urls "https://192.0.2.0:9087/"
I am stuck at this point.Unable to proceed...Please help on this.. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Dec 05, 2014 12:23 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
This
does not sound like a valid IP address for a server system.
Are you sure that it is correct?
what does the Virtual Appliance system say? Perhaps you may need to fiddle with the VM network settings so that it fits in with your configuration?
For example, my VMWare installation uses 192.168.27 as its NAT Subnet.
If I import a VM from somewhere else and it does not use DHCP then I have to change the fix IP address for the NAT interface so that it uses 192.168.27 subnet.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 05, 2014 5:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
This
does not sound like a valid IP address for a server system. |
Anything 192.n.n.n is typically a priviate network address that maps onto something else externally. I assume (and I should have mentioned I don't have direct experience of this Virtual Appliance and am speaking from general network knowledge) that you got the 'https://192.0.2.0:9087' URL from documentation that came with this virtual device; I would recommend speaking to someone locally with network knowledge to see how to map that onto an address your PC can resolve.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Dec 05, 2014 5:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So you first need to make sure your Virtual machine is exposed to the network of your laptop.
Then you need to make sure you configured the right things in the MessageSight startup, to make sure the MessageSight device is using the correct network adapters and correct addresses.
Then you need to double-check that the WebUI was started up - using the command line from within the virtual image.
Then you can issue "imaserver get WebUIPort" and "imaserver get WebUIHost" to find out what port and hostname the webui is listening to.
then you should be able to enter that set of information into your browser and get the login prompt for the webui. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Mon Dec 08, 2014 6:47 pm Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
After a long try,its working for me now...
In the MessageSight CLI,I set imaserver WebUIHostaddress as "All".
I just tried setting the eth0 ethernet inet address as 192.168.77.128.
Then I tried to connect to https://192.168.77.128:9087/,its working fine... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 09, 2014 6:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| GeneRK4 wrote: |
After a long try,its working for me now...
In the MessageSight CLI,I set imaserver WebUIHostaddress as "All".
I just tried setting the eth0 ethernet inet address as 192.168.77.128.
Then I tried to connect to https://192.168.77.128:9087/,its working fine... |
You should be aware that this is a security risk. You have now exposed the webui to all of the interfaces in your appliance/vi. This means, for example, that if one side of your appliance is *outside* of your firewall and exposed to the internet, then anyone on that side can now attempt to administer your appliance using the WebUI.
You should also make sure that you have created an additional user other than the default user 'admin', and that you have also changed the password on the 'admin' user to something other than the default value.
Especially if your WebUI is exposed to the internet. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Tue Dec 09, 2014 5:39 pm Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
Thank you for your valuable advice..I will take this into account and do modifications accordingly...  |
|
| Back to top |
|
|
|
|
