Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Re: Support for virtual servers? (Karsten Heymann)
2. Re: Support for virtual servers? (Karsten Heymann)
3. Re: Support for virtual servers? (Karsten Heymann)
4. makefile missing (Christine Burger)
----------------------------------------------------------------------
Message: 1
Date: Thu, 5 Jun 2014 10:42:38 +0200
From: Karsten Heymann <[email protected]>
Subject: Re: [Netdot-users] Support for virtual servers?
To: Brian Candler <[email protected]>
Cc: [email protected]
Message-ID:
<CAL017hBBbPLs3Z-ULSMsTjy66d4UT_Vs62vk-yKYr=o97ao...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2014-06-04 18:18 GMT+02:00 Brian Candler <[email protected]>:
> On 04/06/2014 16:57, Karsten Heymann wrote:
>
>> Your idea of connecting the tap devices to the virtual servers sounds
>> interesting
>>
> I think you'll find your VM servers are already connected to the bridge
> with tap devices (or vnet devices or similar)
>
> Type "brctl show" on the machine where your VMs are running.
Yes, that's right. I meant to connect them in netdot :). And although the
tap devices are currently not detected by netdot in my setup (which may
very well be my setup's fault), I can enter the connection manually for now
and think about automatizing it later, either via the netdot api or by
extending/fixing the servers snmpd output. The important thing for me at
this point was to get the data structure in netdot right.
, although it would be really nice to be able to see which virtual servers
> are connected to which bridges, as there are multiple bridges for the
> different vlans we use.
>
> With regular Linux bridges that would involve enumerating the bridges.
>
> With openvswitch you can have a single openvswitch instance, have vlans
> inside openvswitch, connecting each VM to an access port with a chosen VLAN
> (or a trunk port with selected VLANs on it). I've tested this, it works
> very nicely.
>
Yes, that works well.
Running this allows to query information about the bridge:
> snmpwalk -v2c -c redacted localhost BRIDGE-MIB::dot1dBridge
> But this information does not seem to be used by netdot, at least grepping
> the netdot code for the mib did not yield any results.
>
> Netdot definitely retrieves the bridge table from switches. Whether it's
> this MIB or a different one I don't know. Search for fwt_update, dig down
> to walk_fwt.
>
I'll definitely have a deeper look into that.
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140605/b7d7a4a1/attachment-0001.html
------------------------------
Message: 2
Date: Thu, 5 Jun 2014 10:54:47 +0200
From: Karsten Heymann <[email protected]>
Subject: Re: [Netdot-users] Support for virtual servers?
To: Phil Regnauld <[email protected]>
Cc: [email protected]
Message-ID:
<CAL017hDkH9BMujFDibb7w=RwEjq=wU0f6t=gftwbj4onvjs...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2014-06-04 18:20 GMT+02:00 Phil Regnauld <[email protected]>:
> Karsten Heymann (karsten.heymann) writes:
> > thank you for the suggestions. I'm already running lldpd on the physical
> > servers. I also tried running it on the virtual servers, but the linux
> > bridge does not forward lldp (or cdp) information.
>
> The bridge doesn't appear, but I have definitely run workshops
> where virtual 7200s could see the VMs running CDPD/LLDPD as
> neighbors.
At our setup these packets does not seem to be forwarded over the linux
bridge. I think I read somewhere that it is possible to enable the
forwarding by some 'magic' /proc or /sys settings, but I never got that to
work.
> > I also tested
> > openvswitch, but it doesn't support snmp, lldp or cdp as well as far as I
> > could find out.
>
> Unfortunately not - but extending snmpd to provide this
> information using
> ovsctl and the ovsdb would be an interesting project.
>
Definitely.
> > Running this allows to query information about the bridge:
> > snmpwalk -v2c -c redacted localhost BRIDGE-MIB::dot1dBridge
> > But this information does not seem to be used by netdot, at least
> grepping
> > the netdot code for the mib did not yield any results.
>
> What have you set sysServices to on the host running the bridge ?
>
> https://osl.uoregon.edu/redmine/issues/1764
>
> sysServices has to reflect that the host is also an L2 device -
> you might want to set that to 78 and see if that helps.
>
Ok, when I set sysServices 78 in snmpd.conf and rescan the server (I
removed and re-added it to be sure), these settings in the "Management" box
change from
Layers: 0
IP Forward?: No
Collect ARP?: No
Collect FWT?: No
Collect STP Info?: No
to
Layers: 2, 3, 4, 7
IP Forward?: Yes
Collect ARP?: Yes
Collect FWT?: Yes
Collect STP Info?: Yes
And an "Arp" tab appears with some arp cache dumps, but apart from that I
could not find changes related to the bridges.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140605/3d37692a/attachment-0001.html
------------------------------
Message: 3
Date: Thu, 5 Jun 2014 10:56:16 +0200
From: Karsten Heymann <[email protected]>
Subject: Re: [Netdot-users] Support for virtual servers?
To: William Bulley <[email protected]>
Cc: [email protected], Brian Candler <[email protected]>
Message-ID:
<cal017haprfxvda3qb3ndak3oe8oq-bwz3+uzckbezgavdpw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2014-06-04 18:22 GMT+02:00 William Bulley <[email protected]>:
> According to Karsten Heymann <[email protected]> on Wed, 06/04/14
> at 11:57:
> But this information does not seem to be used by netdot, at least grepping
> > the netdot code for the mib did not yield any results.
>
> But it is part of SNMP::Info which is heavily used by Netdot.
>
> http://search.cpan.org/~oliver/SNMP-Info-3.13/Info/Bridge.pm
>
Thanks for the pointer, I'll play around with the example code to see what
actually gets exported.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140605/944a3a09/attachment-0001.html
------------------------------
Message: 4
Date: Thu, 5 Jun 2014 12:00:11 +0000
From: Christine Burger <[email protected]>
Subject: [Netdot-users] makefile missing
To: "[email protected]" <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi all,
I am new to netdot and trying a new install. Target machine is a n openSuSE
13.1.
When I try to make install I get the following errors:
cd htdocs ; make all DIR=htdocs
make[1]: Entering directory `/usr/local/netdot/htdocs'
make[1]: *** No rule to make target `all'. Stop.
make[1]: Leaving directory `/usr/local/netdot/htdocs'
make: *** [htdocs] Error 2
When I checked the archive I could not find a Makefile. Similar for make in
DIR=lib/
cd lib ; make all DIR=lib
make[1]: Entering directory `/usr/local/netdot/lib'
make[1]: *** No rule to make target `all'. Stop.
make[1]: Leaving directory `/usr/local/netdot/lib'
make: *** [lib] Error 2
Can you help me with this?
Best Regards/Viele Gr??e
Christine Burger
UMTS Network Level Test Engineer
Thurn-und-Taxis-Str. 10
D-90411 N?rnberg, Germany
(tm) E-Mail: [email protected]<mailto:[email protected]>
? Phone: +49 911 30874-6229
? Fax: +49 91130874-4006
Sitz N?rnberg, Handelsregister HRB 24701 - AG N?rnberg
Gesch?ftsf?hrer: Udo Nadolski, Dr. Markus Ermer
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140605/380b7d06/attachment.html
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 67, Issue 3
*******************************************
