Indeed, but the original question asked was about the instance limitations, and all the responses thrown out are in the 1000-4000 range, discussing virtual interfaces and RPVST. Nobody seems to have answered the fairly simple initial question. I think that answer is "either 16 or 64, depending on your code".
The separate question of "do you really need all 1000 of those instances" is a design debate which could be had at length, and would likely come out different depending on the underlying network design and requirements. At least in the case of the enterprise where I work, the "whole point of MST" is that it's a proper open standard, rather than one of those super scary Cisco Proprietary Protocols. -Geoff On Tue, Jul 14, 2009 at 8:26 AM, Jon Lewis<[email protected]> wrote: > On Tue, 14 Jul 2009, Geoffrey Pendery wrote: > >> So keep in mind that if you're moving from RPVST to MST, you're >> talking about fewer instances, by necessity. > > But isn't that the whole point of MST? Most of what I've read about it > talks about doing setups where you only have 2 or 3 instances, with all your > vlans in the 2nd and or 3rd instance. > > ---------------------------------------------------------------------- > Jon Lewis | I route > Senior Network Engineer | therefore you are > Atlantic Net | > _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
