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: Miscellaneous issues (Carlos Vicente)
2. Re: Topology issues (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Fri, 03 Aug 2012 15:04:23 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Miscellaneous issues
To: James Andrewartha <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 8/2/12 1:27 AM, James Andrewartha wrote:
> Hi again,
>
> This email is more of a grab-bag of things I've come across.
>
> What's the point of VLAN groups? Our VLANs are largely non-contiguous,
> although there are some like student labs which go from 500-526.
Some network admins like to organize their VLANs in ranges. For example,
"assign all the VOIP VLANs between IDs 2000-2500". If yours are
non-contiguous, then VLAN groups won't make much sense.
A non-contiguos grouping method would probably be useful.
We intend to address the problem of VLAN and address space reuse in the
near future, and we'll revisit this at that time.
> Clicking new in VLAN tasks only creates a VLAN group, and in the VLAN
> group view you can only add a new VLAN, not associate an existing VLAN
> with that group.
Yes. That should be fixed at some point.
> Would it be possible to have some sort of IP grouping below subnets? For
This has been requested before:
https://osl.uoregon.edu/redmine/issues/802
We actually started working on that, but it got pushed back in the
priority line.
> Also, 10.20.252.0/22 is the DHCP zone for that subnet. I worked out if
> you create dynamic IPs they will then magically appear in the DHCP
> subnet as a range within a pool, with reverses automatically created if
> you tick the box. However, I've got our DHCP server set up to update the
> forward and reverse zones and so don't want or need Netdot to create
> static records for me. Plus, deleting or managing even 10s of IPs is a
> pain through the webui.
OK. So if you don't click on the "generate DNS records" box, is that OK?
What are you suggesting?
> The login timeout seems to not be based on idle time.
>
Right. Patches welcome ;-)
--
cv
------------------------------
Message: 2
Date: Fri, 03 Aug 2012 15:17:25 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Topology issues
To: James Andrewartha <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 8/2/12 3:06 AM, James Andrewartha wrote:
> Hi once more,
>
> Looking at the output of show neighbours (we're an Enterasys shop) on
> pblock I see:
>
>> ge.1.49 00-1f-45-9c-9b-c ge.2.111 ciscodp 172.20.254.5
>> ge.1.49 00-1f-45-9c-9b-ca 172.20.254.5 cdp 172.20.254.5
>> ge.1.49 00:1F:45:9C:9B:CA ge.2.111 lldp 172.20.254.5
>
> So it looks like the CiscoCP (CDP here is the Cabletron Discovery
> Protocol) has an invalid value, and it's been put into the DP Remote ID
> field on interface 3396. Is there a way to preference which discovery
> protocol goes into the database?
I'm afraid not.
> Incidentally, it takes 35 minutes to poll for topology, as it tries to
> use SNMP to contact every single phone. I haven't set up
> update_devices.pl to run from cron yet.
If your phones are all within their own address space, you can use:
EXCLUDE_UNKNOWN_DP_DEVS_FROM_BLOCKS
to list those blocks, and the topology discovery will not try to contact
them.
> What devices are supposed to be in Netdot? Switches/routers, vmware
> hosts, servers, desktops/laptops, IP phones? My guess is
> switches/routers and nothing else, but then why is there a section for
> IP Phones in the device inventory? Is it whatever I can query via SNMP?
Netdot will discover anything that speaks SNMP. You can leverage SNMP
communities to separate your network infrastructure from junk like
printers and the like. Remove "public" from the list in Netdot's
configuration.
We do document our IP phones.
> Is it possible to exclude devices from the topology graph? Currently our
> APs are thick IOS devices and so show up, but they just add noise.
Not possible currently.
> I have a few devices with funny models - ice.132, ice.137, ice.141,
> enterprises.3955.6.5024, enterprises.3955.6.3.2024.1 - I presume these
> are because the MIBs don't have them? How do I update/install MIBs into
> Netdot?
Netdot's support for different vendors depends on a Perl module called
SNMP::Info. That's a separate project. It comes with a bundle of MIBs.
> An external request - it'd be nice to find connected interfaces with a
> mismatch in the configured VLANs:
> http://lists.ausnog.net/pipermail/ausnog/2012-July/014264.html
>
That's a good feature. I'll add it to my list.
Thanks again.
--
cv
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 45, Issue 4
*******************************************
