08.07.2010, 00:19, "Don Greer" <Don.Greer@xxxxxxxxxxx>: > Might I suggest that, since the IP network already has a one-way relation > to the VLAN, perhaps that could be made a two-way relation, so the key would > be "VLAN:NETWORK" and, base on the two-way relation to the VLAN Campus, the > ultimate relation is "CAMPUS:VLAN:IPADDRESS". This would resolve the issue > for both the problems below, as well as myself where I want to allow > customers to us RT as a tool to manage and document their > I don't know how hard that would be, but it would change the schema of the > database, so likely a major rev type change. The matter is, VLAN-network relation is implemented as N:M (you can have IP network spanning multiple "campuses" or one VLAN with many IP prefixes assigned to it). -- Denis Ovsienko