Hello Sanjeev,
I have sent this message during 4.5.1 release voiting and got reply
that such configuration brakes down VPC tiers isolation and thus - not
supported. So I have either to create interfaces in non-VPC networks (private
or shared) or to route all traffic from one interface through VR inside VPC.
Regards,
Vadim.
-----Original Message-----
From: Sanjeev N [mailto:[email protected]]
Sent: Friday, May 08, 2015 2:18 PM
To: [email protected]
Subject: Re: VPC usage scenario
Vadim,
Whatever you have tried is a valid scenario. Please report a bug if things are
not as expected.
-Sanjeev
On Wed, May 6, 2015 at 1:09 AM, Vadim Kimlaychuk <[email protected]>
wrote:
> Hello all,
>
>
> 1. I have created VPC and 2 network tiers.
>
> 2. Added VM to the 1-st one (default). Got IP by DHCP,
> everything works so far.
>
> 3. Added 2-nd network tier to the same VM at run-time. VIF
> initialised and I run dhclient for 2nd interface and got IP from 2nd tier.
> Everything works ... until
>
> 4. Reboot
>
> 5. After reboot VM console shows :
>
> * ???that 1-st network (default) was neglected by DHCP server -- I got
> NACK for DHCP offer from VM
> * 2-nd network got ACK from DHCP server and IP, but since it is not
> default NIC - route is not provided
> * VM is waiting for default route from VR for 30 seconds and after
> timeout I have non-working configuration. 1-st interface has no IP,
> there is no default route.
>
> Am I doing something wrong? Can VM have 2 NICs in different tiers or
> this kind of scenario is prohibited? As far as VM has only 1 NIC
> everything works fine.
>
> Thank you for explaination,
>
> Vadim.
>
>
>
