RE: [LANdb] Suggested schema and app changes

==> Regarding RE: [LANdb] Suggested schema and app changes; Sean Walberg <SWalberg@exchange.hsc.mb.ca> adds:

>> Yeah, the schema will have to be modified for a more correct vlan
>> implementation.  (Jacks currently don't store vlan info.)

SWalberg> I've included a .png of my current work on the schema for review.
SWalberg> Stuff that still has to go in are support for subnets, and any
SWalberg> extra information each table is to hold.  See the bottom of the
SWalberg> message for a couple of small explanations.

This looks pretty nice to me =)  A few comments:

 - Ports also should also have some kind of media type, though media type
   matching shouldn't be enforced (media converters stuck in the middle,
   etc)

 - Port settings (duplex, 10/100/1000, etc) need to be tracked.  I'm
   thinking that this might warrant a sepereate table, esp to make it
   easier to track radically different kinds of port settings - ATM port
   settings, for example (and yes, we are starting to have connected hosts
   show up here at least)

 - the switch table should also have SNMP community string info

 - I'm unclear on exactly how the VLANDetail and VLAN tables work? 

-- 
Frank Sweetser rasmusin at wpi.edu, fs at suave.net
Full-time WPI Network Tech, Part time Linux/Perl guy
Avoid the Gates of Hell.  Use Linux
(Unknown source)

-------------------------------------
LANdb - Network Management through SQL
To unsubscribe, send email to landb-request@avenir.dhs.org
	and put 'unsubscribe' in the subject line
Administrative contact: weez@avenir.dhs.org
-------------------------------------