Forum Discussion

athmane_Bouazzo's avatar
athmane_Bouazzo
Icon for Nimbostratus rankNimbostratus
Feb 24, 2016

LROS VM connectivity issue

I downloaded the LineRate Application Proxy Software ova file and ran it in my VMware player. The VM has 3 Network interfaces, all of them are getting an IP from my DHCP server (same Vlan as my physical interface) but when I log in (CLI) and try to put the license in, I noticed that I was getting an error message: WARNING: No licenses are configured: ERROR: Failed to obtain a license: Error: : [Errno 8] hostname nor servername provided, or not known

 

I suspected the DNS and connectivity. I checked that all interfaces have an IP address, a default gateway and a DNS server. And I went to the bash and I noticed that sometimes the VM is not even able to ping its default gateway.

 

And sometimes when I reboot it, it pings the gw but not able to ping any other IP address in another VLAN (Inter Vlan routing is working perfectly).

 

So I guess this is the problem why it's not able to contact the DNS server to resolve the servers for license activation.

 

Could you help please.

 

application delivery
linerate

3 Replies

Sort By
  • Andrew_Ragone_2's avatar
    Andrew_Ragone_2
    Historic F5 Account
    Feb 24, 2016

    Hello Athmane,

     

    At first glance, this does appear to be a network connectivity issue with your VM/Host. Here are a few things to check in the config to ensure the system is configured as you expect. These commands are to be run in the LROS Shell.

     

    DNS Name Server: Ensure there is an external DNS Resolver configured in "show ip dos". If there are no servers listed here under "Name Servers:" you can configure them with "ip dns" followed up "name-server a.b.c.d" in configure mode. See this page for more detail: https://docs.lineratesystems.com/087Release_2.6.1/200CLI_Reference_Guide/Configure_Commands/IP_Mode_Commandsname-server

     

    DNS Resolution: When you have confirmed a name server is configured properly, try running a query on it. The following command will test whether you are able to successfully resolve the address of the F5 licensing server. If this doesn't work, you may want to change the name-server you are using for your DNS resolution.

     

    bash "nslookup license.f5.com"

     

    IP Config: Check "show ip interfaces brief" and ensure em0 has an IP address for the LAN that interface is on. If not, take a look at the docs to configure one: https://docs.lineratesystems.com/087Release_2.6.1/200CLI_Reference_Guide/Configure_Commands/Interface_Mode_Commandsip_address

     

    Intermittent connectivity? From your host machine (or another one on the LAN of your em0 interface), try and run a sustained ping to the IP Address of em0. If you see drops periodically, something on your network may not be behaving properly. I would troubleshoot there.

     

    These troubleshooting steps should get you started. Also, you mentioned this is using VMWare Player, so you may get some issues resolved by restarting your Host machine. Let us know how this goes!

     

    -Andrew

     

    • athmane_Bouazzo's avatar
      athmane_Bouazzo
      Icon for Nimbostratus rankNimbostratus
      Feb 24, 2016
      Hi Andrew, Thanks for your answer. I already set the DNS to my DNS server and also tried 8.8.8.8 (google ones) and connectivity is OK. But when I restart the VM everything looks good for the first few seconds (I would say a minute or two) but suddenly it all stops working. When I say it stops working, the ping to the default gw is not working. The IP address on em0 is there and I am sure there is no conflict on the network. The DNS server configuration is there (which is not needed since I am ping-ing the default gw, an IP address not a name). I restarted the host machine many times and the problem persists. Any idea ? Regards.
    • Andrew_Ragone_2's avatar
      Andrew_Ragone_2
      Historic F5 Account
      Feb 24, 2016
      While I do not know how you have your 3 interfaces configured, I suspect they are all on the same subnet. The next thing you can try is to disable all but one interface while the system activates its license. Generally you would want em0 to be the one that remains available. So in this case, em1 and em2 should be in a "shutdown" state. This can be done, for example on em2, in "configure" mode followed by "interface em2" and the command "shutdown". Repeat on em3. After licensing is successfully completed, then do "no shutdown" to re-enable the interfaces. Give that a shot and see if license activation is successful.