On the KVM host you could parse the output of 'brctl show', but that is awkward to parse. Or you might be able to iterate through /sys/devices/virtual/net/* and work backwards from that.
On 12/19/13 10:16 PM, "Pradeep Cloudstack" <pradeepcloudst...@yahoo.com> wrote: >Hi Chiradeep, >the LLDP output on the switch looks something like > >************************************* >Local Interface Parent Interface Chassis Id Port info > System Name >ge-0/0/21.0 - 00:30:48:c9:54:26 eth1 > bng-p3-vmm-cloudstack.englab.juniper.net >ge-0/0/20.0 - 00:30:48:fd:e4:fc eth1 > bng-p3-vmm-vde02-dcbg.englab.juniper.net >me0.0 - 78:fe:3d:d7:f4:80 ge-0/0/2.0 > x2-sw39 >************************************* > > >Here bng-p3-vmm-cloudstack.englab.juniper.net and >bng-p3-vmm-vde02-dcbg.englab.juniper.net are the KVM hosts connected to >the switch > > >-Pradeep > > > > >On Friday, December 20, 2013 5:54 AM, Chiradeep Vittal ><chiradeep.vit...@citrix.com> wrote: > >What does the LLDP output look like? > > >On 12/18/13 11:03 PM, "Pradeep Cloudstack" <pradeepcloudst...@yahoo.com> >wrote: > >>Hi , >>on a KVM host, I have a bridge interface - cloudbr1 to which eth1 has >>been added. >>This is for guest Network. >> >> >>When we create a VM on the KVM host, the NetworkGuru plugin gets to know >>about cloudbr1 >>(via the KVM traffic label). But is there any means to figure out the >>ports (like eth1) that have been >>attached to the bridge interface(in this case cloudbr1) on the KVM? >> >>The reason I want to know this is that the lldp output on the switch >>gives information about eth1 (and not the bridge interfaces). >> >> >>-Pradeep
