It is not needed in service chasing V2. Launching of the VM with correct
interfaces is not contrail responsibility in V2.
Users get more control over how the VMs are launched in V2.
Regards
-Harshad
> On Oct 17, 2016, at 7:06 PM, fubinghao686 wrote:
>
>i find a
This lists is for open Contrail users. If you are using juniper Contrail than
you need to contact juniper support.
Regards
-Harshad
> On Oct 14, 2016, at 6:32 AM, shyam yeduru wrote:
>
> Hi Team,
>
> We want to check the following combination in Juniper Contrail
table operational.
> No impact on end user traffic.
>
> Regards,
> Sudeep Batra
> +91 84201 96572
>
> On 30-Sep-2016, at 11:51 PM, Harshad Nakil <hna...@gmail.com> wrote:
>
>> Sudeep,
>>
>> Can you also suggest how redundant vrouters overcome this
ally like to design with High-Availability principle in
> mind.
>
> Regards,
> SUDEEP BATRA
>
>
> -Original Message-
> From: Harshad Nakil [mailto:hna...@gmail.com]
> Sent: Friday, September 30, 2016 7:09 PM
> To: Sudeep Batra
> Cc: users@lists
Sudeep,
Currently there are no plans to have redundant vrouters.
Currently the direction is to support hitless restart of vrouter agent some
time in future.
Vrouter data plane itself is single point of failure when part of kernel.
In DPDK mode we will support restart with traffic hit
ls
>
>
>
>> On Mon, Jun 27, 2016 at 7:18 PM, Harshad Nakil <hna...@gmail.com> wrote:
>> MPLS label is local to compute node (or source of the route (from SDN GW)).
>> It represents what happens to packet once it reaches the compute node (MPLS
>> label re
gt;> Thanks that answers my question
>>
>> On Mon, Jun 6, 2016 at 10:20 PM, Harshad Nakil <hna...@gmail.com> wrote:
>>> MPLS labels are unique for given compute node. Can be reused in different
>>> compute.
>>>
>>> Regards
>>> -Harshad
>>
Yes fat flow will help.
You can also try increasing the default flow table size from 512 to 2M. And
decreasing flow timeout from 3 minutes to 5seconds.
Regards
-Harshad
> On Jun 9, 2016, at 5:31 AM, Jacek Czerniak wrote:
>
> Hi All!
>
> We are testing LBaaS in
Rory,
Looks like, may be you have some misunderstanding. Vrouter is replacing
functionality of Linux bridge OR OVS for virtualized resources and it provides
distributed virtual router.
Routing between two physical subnets on different physical interfaces is a use
case that is not productized