Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
FMW status.cmd returns no results when GlobalProtect VPN is connected
I use my laptop for OBIEE 12c development. It is running perfectly. When I run the status.cmd script, it shows that all servers are RUNNING.
When I connect to my corporate VPN (using GlobalProtect VPN), my OBIEE system keeps running just fine. But at that point, the status.cmd script returns NodeManager (machine-name:9506): NOT RUNNING, until I disconnect from the VPN, at which time status.cmd again returns all its correct information. Again, OBIEE and WLS and FMC are all good during this time - it's just status.cmd that is not able to reach NodeManager.
How might I be able to run status.cmd and get the correct results while connected to the VPN?
Answers
-
Isn't it because of your VPN profile?
Some VPN profiles change few things when they connect, for examples DNS etc.
Therefore your "machine-name" maybe can't be resolved anymore because the VPN profile uses your corporate DNS to resolve the name and it doesn't resolve anymore or things like that.
Not sure what "machine-name" is supposed to be (if it's your laptop or another host in your local network), but you have to look in the VPN profile and you can also figure out if things can't be resolved anymore by looking at the network traffic while connected to your VPN: where the request goes or if it can't be found etc.
0 -
"machine name" is my PC name where OBIEE is running.
Gianni, your explanation makes sense. The VPN is assigning a local IP address that is unknown to me (10.87.2.14). And, of course, node manager knows nothing about that IP address. I added that IP to my hosts file, and the NodeManager was still not responsive to status.cmd.
Because this isn't really causing me any meaningful amount of grief, and because I perceive that there really isn't much I can do about it anyway, I'm tagging your answer as 'Correct' and moving on to other more important things.
Thank you, sir!
0 -
That IP is one of your corporate network (still a private IP), I remember at the time of 11g the documentation for OBIEE suggested to have a loopback adapter setup in the PC before to install in the case of DHCP networks. That network adapter was a fake one pointing to the PC itself all the time, that was the workaround for system with a DHCP and the IP assigned to the PC which could be changing because of that.
Ideally if you make sure to add "machine-name" linked with 127.0.0.1 to your hosts file it could also do the job. In that way whatever IP your network adapter get (from your home router of from your corporate network when connecting the VPN) "machine-name" will always resolve to the same place.
Or having that loopback adapter will also solve things.
All in all you have to have a network setup with just doesn't move, being independent from your real network adapter which will change based on the network it's connected to (local or VPN).
0 -
It was in the 11g documentation but that was also the last version which was written with any pretense of support for running it on a local machine :-)
0
