Re: [netdisco-devel] Netdisco usability as device-tracking engine for our University-network.

[<A.L...@lb...>]

Hi,

>    This would be a very important improvement for us because dns-names are
>    not yet in the netdisco-database.

DNS is already  there for devices...with netbios for nodes....i guess
a similar function for populating dns for device can be done for nodes..
a small background script (housekeeper) could also be used to populate
an entry in the node_ip table or such.

>    The same is true for the dot1x and portsecurity properties of the
>    switch-ports. I got the impression that at least for these
>    security-properties a standardized MIB is available on Juniper and other
>    vendors.
>    It would be a great help to be able to see these parameters in netdisco to
>    see the security properties of all ports.

+1 for that. we have dot1x on 5-10% of ports and look to increase that but 
without the visbility at service desk it gets hard to promote this technology.
they only see the VLAN the port was on at the time of polling...ideally
the VLAN the node was on being recorded in the node table.

>    Another practical issue when using the PostgreSQL odbc interface are the
>    many text type columns used.

urgh. I'd advice you move away from the ODBC stuff and just design a web
system that talks to the postgres engine of netdisco properly. it would
be a shame for the current DB and schema to be hobbled because theres some
MS Access or such access going on. alternatively write a form of PIPE
(ie middleware) so that you can present the ODBC with what it wants.

alan