Kilian,
Without a valid gateway, it is very likely that DNS resolution failures
will cause a delay in the login process.  The nature of those failures
changes when you altered the ip address since there is not a valid route to
the gateway.  This will cause a much quicker failure (no route to host)
rather than a timeout while querying the DNS servers.

On 24 November 2015 at 10:07, Kilian Ries <[email protected]> wrote:

> ​Hello,
>
>
> i think i found an abnormal behaviour (maybe a bug) by using the
> zlogin-command with lx-branded zones:
>
>
>
> I'm trying to setup a new lx with ip-address and gateway (the gateway
> doesn't exist yet):
>
>
>
> {
>     "alias": "lx1",
>     "hostname": "lx1",
>     "brand": "lx",
>     "kernel_version": "3.13.0",
>     "max_physical_memory": 2048,
>     "image_uuid": "d5b3865c-0804-11e5-be21-dbc4ce844ddc",
>     "quota": 10,
>     "resolvers": [
>         "8.8.8.8",
>         "8.8.4.4"
>     ],
>     "nics": [
>         {
>             "nic_tag": "admin",
>             "ip": "192.168.10.100",
>             "netmask": "255.255.255.0",
>             "gateway": "192.168.10.1"
>         }
>     ]
> }
>
>
> After creation, try to "zlogin uuid" and it will take up to 2 minutes
> until you are logged in.
>
> Just seeing:
>
> [Connected to zone 'ceeb43dd-9157-4efc-a63b-3acf3b8647d2' pts/3]
>
> then after two minutes, i'm logged in. I can repeat that multiple times,
> it always takes about 2 minutes.
>
>
> If i change my lx-config to the following:
>
> {
>     "alias": "lx1",
>     "hostname": "lx1",
>     "brand": "lx",
>     "kernel_version": "3.13.0",
>     "max_physical_memory": 2048,
>     "image_uuid": "d5b3865c-0804-11e5-be21-dbc4ce844ddc",
>     "quota": 10,
>     "resolvers": [
>         "8.8.8.8",
>         "8.8.4.4"
>     ],
>     "nics": [
>         {
>             "nic_tag": "admin",
>             "ip": "192.168.20.100",
>             "netmask": "255.255.255.0",
>             "gateway": "192.168.10.1"
>         }
>     ]
> }
>
>
> then it works normal and i can zlogin within seconds. The only difference
> is that the ip-address is on another subnet (192.168.20.xx) than the
> gateway (192.168.10.xx). If they are both on the same subnet and the
> gateway isn't reachable it slows down the zlogin massive.
>
> I'm able to reproduce that behaviour on different smartos hosts, running
> different releases (up to  build: 20151112T052215Z).
>
> Greets
> Kilian
>
>
>
>
>
> *smartos-discuss* | Archives
> <https://www.listbox.com/member/archive/184463/=now>
> <https://www.listbox.com/member/archive/rss/184463/26937779-40cf8a10> |
> Modify
> <https://www.listbox.com/member/?&;>
> Your Subscription <http://www.listbox.com>
>



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to