Hi,
> at the beginning (like dividing the routing table to summarise it)
> quickly falls apart with the university moving departments out to
> west Cambridge, or colleges requesting their primary connection
> moves to their new out-of-centre site.
..well, you can give your depts their local IPv6 space too
which can follow them ;-)
we a re a little more 'strict' with addresses - VLANs belong to
buildings (and depts inside those buildings use those VLANs) - and
the IP addresses belong to those VLANs - thefore, if a dept moves to a
different building (which happens a few times a year) they get new IP
addresses..they dont 'own' the IP space. whilst this adds some overhead
(ACLs, access systems) ir removed a whole load of other things - such
as people printing to printers via its IP and having holey monterey jack
style DHCP scopes etc - just give the DNS entry its new IP and printing
back working again.
not that many depts care about their addresses these days as large numbers
are using their laptops/tablets/smartphones on wireless - and the wireless
IP space is completely seperate from buildings and departments - VLANs
there are assigned by what type of member of the organisation who are
(staff, student, visitor, 3rd party etc).
I do care about the routing table as network stability is the prime driver
for things we do - having the router CPU spending too much time doing
IGP convergence is a pain we can do without...and having a mapping
between IPv6 and the physical location on campus means we can look at
moving routing closer to the edge.
alan
|