[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [LANdb] Suggested schema and app changes
> Yep, as I said, operational mode for a port, either trunk or
> not. To be
> correct I suggest that a PORT has an associated list of
> VLANs, and for
> each VLAN there has to be a variable specifying if transmitted frames
> should be tagged or untagged. OK, propably a variable
> stating the operational
> mode on a per port basis would be sufficient for now.
Agreed...
> Definitely not, (port, switch) is unique, so there should be
> no problem. Jack
Do you mean (port, module, switch)?
> should be unique in a closet, not in a building. After all,
> jack is actually
> more bound to the closet, not the building. Building
> contains closets, closets
> contain jacks. Hmm, errr, well, that's open for debate.
I agree, but in the interests of simplicity I would argue that a jack
belongs to a building. I would think that most of the queries would be
between jack and building, so making a jack relate to a closet adds an extra
join.
> IMHO (which is just what it is, humble:) we should have a
> "cable" table, with
> poatches, connectors, etc. cables could be connected to
> other cables using
> patches. Here:
>
> CABLE ( cableid, media, whatever_what_not ...)
> CONNECTOR ( cableid, connectorid (jack, closet, building), type, ...)
> PATCH ( cableid, connectorid, patchid ) or
> PATCH ( cable1id, cable2id, connector1id, connector2id )
>
> roughly translated:
>
> CABLE ( cableid, media, whatever_what_not ... )
> JACK ( jack_idx, cableid, connector type, name, closet, ... )
> PATCH ( jack1_idx, jack2_idx ) or
> PATCH ( patchid, jack_idx ) if one could patch more than
> two cables at once.
>
> Or something of the sort. This would allow one to draw a
> graph of the entire
> physical network, a feature I would value. Hmh, how would
> one document a wireless
> LAN? :)
erp... that is a good one :) I like your idea here, but I'll run through a
couple of examples on paper here before I comment.
Sean
> > No, no subnet can span more than one Vlan, that I know of
> (imagine trying to route
> > to two identical subnets that are actually on two separate
> vlans.. eck?). And
>
> eck? Not really special:
>
> router --1-- firewall --2-- subnet
> proxyarp
>
> now, 1 is subnet 192.168.0.0/24 vlan 10, and 2 is allso
> 192.168.0.0/24 vlan 11.
> the actual physical connection is quite funny:
>
> switchrouter ---vlan 11---> hosts
> |
> |
> vlan 10, 11
> |
> |
> switch --vlan 10--> firewall -+
> | ^ |
> | +-----vlan 11-------------+
> |
> +---vlan 11--> hosts
>
> if the firewall would be a router aswell, vlan 10 could
> contain several subnets.
>
>
> > Q: What subnet is that machine on? A: Duh, what's it's IP?
>
> I have a printer which IP is 10.2.10.1, which also happens
> to be my management
> station. Naturally they are in different VLANs.. Duh? The IP
> address really
> doesn't have to be unique, really.
>
> > Q: What Vlan is that machine on? A: Lemme look up its port...
>
> Yep, that's the case. This could ofcourse produce several VLANs.
>
> --
> <HTML><B>" Teddy 'tricky' Grenman " </B><SPAN
> MAILADDR=" tricky@cs.hut.fi "
> STYLE="position
> :absolute"> http://www.cs.hut.fi/~tricky <"<TABLE><TR><TD>
> <TABLE><TR><TD><TABLE> </TABLE> </TD></TR></TABLE></TABLE>
>
-------------------------------------
LANdb - The Network Management Database
To unsubscribe, send email to landb-request@avenir.dhs.org
and put 'unsubscribe' in the subject line
Administrative contact: weez@avenir.dhs.org
-------------------------------------