Thanks for this confirmation Ethan.
-Ed
On Tue, Mar 20, 2012 at 11:58 PM, Ethan Jackson wrote:
> > 1) Now if both machines physical inetrface are member of different vlan
> then
> > also CFM works.
> >
> >
> >
> > 2) I am putting my both machines on different subnet by providing
> different
> >
> 1) Now if both machines physical inetrface are member of different vlan then
> also CFM works.
>
>
>
> 2) I am putting my both machines on different subnet by providing different
> subnet IPs, then also CFM works.
>
>
>
> Is that mean in OVS 1.2.2 CFM is not taking care vlan tagging and different
Hi,
I was using vlan command to give tag or make interface as trunk ports.
Ovs-vsctl set port eth0 trunks=2,3
1) Now if both machines physical inetrface are member of different vlan
then also CFM works.
2) I am putting my both machines on different subnet by providing different
subnet IPs
> I am using OVS 1.2.2 which is requiring cfm_remote_mpid value.
> there is no cfm_remote_mpid(s) parameter in this.
>
> now cfm working between 2 physical machine but when I am giving vlan tag 2
> on first machine physical interface and vlan tag 3 on second machine
> physical interface then also C
Oh. Perhaps Ethan can help you. I've forgotten how CFM worked in
1.2.
On Mon, Mar 19, 2012 at 01:16:56PM +0530, edward wilson wrote:
> Hi,
>
> I am using OVS 1.2.2 which is requiring cfm_remote_mpid value.
> there is no cfm_remote_mpid(s) parameter in this.
>
> now cfm working between 2 physic
Hi,
I am using OVS 1.2.2 which is requiring cfm_remote_mpid value.
there is no cfm_remote_mpid(s) parameter in this.
now cfm working between 2 physical machine but when I am giving vlan tag 2
on first machine physical interface and vlan tag 3 on second machine
physical interface then also CCM pac
CFM works on the basis of an interface. Configuring CFM on br0 is not
useful because the CFM packets transmitted on br0 do not go anywhere.
There are various ways that you could avoid using two physical machines
to set up CFM, but CFM is more useful in the presence of two (or more)
physical machi
Hi,
After installing and configuring OVS, br0 will be there.
1. is that mean I have to use its physical interface with which br0
attached like eth0.
2. is that mean I have to use 2 physical OVS machines at least for cfm
set-up.
3. configuration of cfm_remote_mpid ,I got from ovs-vsctl config book.
cfm_remote_mpids (note the "s") is not a column that you as a user
write. It is a column that ovs-vswitchd writes.
Ordinarily one would configure CFM on a physical interface or a
tunnel. br0 is an internal interface.
On Fri, Mar 16, 2012 at 09:19:44AM +0530, edward wilson wrote:
> OVS version 1
OVS version 1.2.2
following commands run on machine-
first mahine-
ovs-vsctl set Interface br0 cfm_mpid=1 cfm_remote_mpid=2
second machine--
ovs-vsctl set Interface br0 cfm_mpid=2 cfm_remote_mpid=1
-Ed
On Fri, Mar 16, 2012 at 8:53 AM, edward wilson
wrote:
>
>
> First machine-
>
> ovs-appct
First machine-
ovs-appctl cfm/show br0
MPID 1: fault recv_fault
Interval: 1000ms
Next CCM tx: 403ms
Next fault check: 2744ms
Remote MPID 2: fault
Recv since check: false
Second machime-
ovs-appctl cfm/show br0
MPID 2: fa
Maybe you should show us your configuration. It seems likely that
there is just some misunderstanding.
On Thu, Mar 15, 2012 at 05:30:19PM +0530, edward wilson wrote:
> when I am creating cfm between two ovs ( one physical and other VM on same
> machine) , CCM packet are with RDI bit set.
> connec
when I am creating cfm between two ovs ( one physical and other VM on same
machine) , CCM packet are with RDI bit set.
connection is not making between MPs.
both are on same bradcast domain.
tried with two physical machines with OVS by giving same vlan id, but
result is same.
-ed
On Sat, Feb 18,
> Ed- same broadcast domain , you mean- I have to assign all MPs in one vlan
> or same network should be provided.
The CFM module sends multicast CCMs on the interface upon which it's
configured. Presumably, multicast/broadcasts packets egressing this
interface can reach some set of other hosts
Hi Ethan,
Thanks for your quick response.
Please see inline my doubts.
Regards,
Ed
On Fri, Feb 17, 2012 at 6:03 AM, Ethan Jackson wrote:
> > If we are using cfm_interval while creating cfm mpid then--
> > 1) Is that means it is for this particular Mpid.so it means we can
> configure
> > differ
> If we are using cfm_interval while creating cfm mpid then--
> 1) Is that means it is for this particular Mpid.so it means we can configure
> different interval for different MPids?
OVS will allow you to configure each MP with whatever transmission
interval you like. However, it's recommended to
Hi,
If we are using cfm_interval while creating cfm mpid then--
1) Is that means it is for this particular Mpid.so it means we can
configure different interval for different MPids?
2) along with that I want to know how can I see the current timer value by
any show command for particular MPids, I
17 matches
Mail list logo
