On Tue, May 29, 2018 at 3:00 PM, Gareth Howell <[email protected]> wrote:
> Hi Mike
> Thanks for the help.
>
> ip a shows
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1
>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>
> inet 127.0.0.1/8 scope host lo
>
> valid_lft forever preferred_lft forever
>
> inet6 ::1/128 scope host
>
> valid_lft forever preferred_lft forever
>
> 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>
> link/ether 22:58:2c:53:ae:9f brd ff:ff:ff:ff:ff:ff
>
> inet 172.29.12.9/24 brd 172.29.12.255 scope global ens3
>
> valid_lft forever preferred_lft forever
>
> inet6 fe80::2058:2cff:fe53:ae9f/64 scope link
>
> valid_lft forever preferred_lft forever
>
> 3: as0t0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
> pfifo_fast state UNKNOWN group default qlen 200
>
> link/none
>
> inet 172.27.224.1/21 brd 172.27.231.255 scope global as0t0
>
> valid_lft forever preferred_lft forever
>
> 4: as0t1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
> pfifo_fast state UNKNOWN group default qlen 200
>
> link/none
>
> inet 172.27.232.1/21 brd 172.27.239.255 scope global as0t1
>
> valid_lft forever preferred_lft forever
>
> No sign of ens4
>
> Nothing in /etc/network/interfaces.d
> mdata-get sdc:nics shows
>
> [{"interface":"net0","mac":"22:58:2c:53:ae:9f","nic_tag":"
> admin","gateway":"172.29.12.1","gateways":["172.29.12.1"],"
> netmask":"255.255.255.0","ip":"172.29.12.9","ips":["172.29.12.9/24
> "],"model":"virtio","primary":true},{"interface":"
> net1","mac":"0c:c4:7a:75:8c:2f","nic_tag":"dmz","gateway":
> "172.29.13.1","gateways":["172.29.13.1"],"netmask":"255.
> 255.255.0","ip":"172.29.13.9","ips":["172.29.13.9/24"],"model":"virtio"}]
> Ahaa!
> How do we get it to be active though?
>
Taking a closer look at the initial output you provided, I can see that the
zone with the first NIC is 4bc5b510-2d5d-e47e-c3bc-d492dfeae320. The
"dladm show-vnic" output shows only one vnic in that zone. That makes it
completely unsurprising that you don't see the second vnic in the guest.
Did you reboot the kvm instance after updating the configuration?
Mike
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com
