Hello All

The ofp_phy_port hw_addr field refers to the MAC addresses that I was
referring to. When a datapath joins, I extract it from the ofp_phy_port and
it works fine.

Thanks everyone.
Sriram

On Tue, Mar 1, 2011 at 3:46 PM, kk yap <[email protected]> wrote:

> Hi Sriram,
>
> The hw_addr is that of the switch ports.  If you look at the
> switch_features message, there is an entire array of the ofp_phy_port.
>  The datapathmem component (from zaku on) does keep track of this and
> handles port_status to update it too.
>
> FYI.
>
> Regards
> KK
>
> On 1 March 2011 12:41, Sriram <[email protected]> wrote:
> > I was assuming that the MAC in ofp_phy_port refers to the interface
> between
> > the switch and the controller. Is this right?
> > But I am looking to get the hw_addresses for the switch - to - switch
> > interfaces.
> > Thanks
> > Sriram
> > On Tue, Mar 1, 2011 at 3:37 PM, Kyriakos Zarifis <[email protected]>
> > wrote:
> >>
> >> No, you are right, this is the MAC. I meant that they are not stored
> >> somewhere on NOX by default, you'd have to collect the MACs
> programmatically
> >> with some queries. (But this is indeed easier than sending ARPs)
> >>
> >> On Tue, Mar 1, 2011 at 12:29 PM, Niky Riga <[email protected]> wrote:
> >>>
> >>> Hi,
> >>>
> >>> In ofp_phy_port data structure, that includes per port info, there is a
> >>> hw_addr field, which I always assumed is the MAC address of the port,
> is
> >>> this something different?
> >>>
> >>> --niky
> >>>
> >>> On 3/1/11 3:17 PM, Kyriakos Zarifis wrote:
> >>>>
> >>>> Hi Sriram,
> >>>>
> >>>> I don't think there is any mapping to switch port MACs on the
> controller
> >>>> by default. You'd probably have to do something like what you
> described.
> >>>>
> >>>> But why do you need the MAC addresses of the switch ports in order to
> >>>> setup flows?
> >>>>
> >>>> (Or did I misunderstand you and you referring to the MAC addresses of
> H1
> >>>> and H2?)
> >>>>
> >>>> On Tue, Mar 1, 2011 at 11:35 AM, Sriram <[email protected]
> >>>> <mailto:[email protected]>> wrote:
> >>>>
> >>>>    Hello All,
> >>>>
> >>>>    I have the following topology setup
> >>>>    H1-S1-S2...-Sn-H2 (n varies from 1 to 20 in my testbed).
> >>>>
> >>>>    I need to pre-install set of flows in each switch (when I receive a
> >>>>    Datapath Join Event). To achieve this i need to know the MAC
> address
> >>>>    of the connected interfaces in the switches.
> >>>>
> >>>>    I was thinking to send an ARP request from the controller to all
> >>>>    switches when I receive the datapath_join_event and the switch can
> >>>>    FLOOD the request to all connected ports. With the ARP reply I can
> >>>>    determine the MAC addresses.
> >>>>
> >>>>    However I would like to know if there is a better way to get this
> >>>>    information (dynamically determine the MAC addresses of all
> >>>>    connected switch links). Is there an API which gives this
> >>>>    information already?
> >>>>
> >>>>    Thanks for your help
> >>>>    Sriram
> >>>>
> >>>>
> >>>>
> >>>>    _______________________________________________
> >>>>    nox-dev mailing list
> >>>>    [email protected] <mailto:[email protected]>
> >>>>    http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> nox-dev mailing list
> >>>> [email protected]
> >>>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >>>
> >>> _______________________________________________
> >>> nox-dev mailing list
> >>> [email protected]
> >>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >>
> >>
> >> _______________________________________________
> >> nox-dev mailing list
> >> [email protected]
> >> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >>
> >
> >
> > _______________________________________________
> > nox-dev mailing list
> > [email protected]
> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >
> >
>
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to