@jtaylor wrote:
Good day,
I'd really like to see the maximum number of interfaces raised so that all 3 modules/48 ports on the Nexus switches are usable. The reason being is that I'd like to split them up into different VDCs (assuming VDCs are supported in VIRL), hoping to consolidate and use less resources versus having independent switches using a single VDC. It's an assumption on my part that I would have a gain in efficiency, but it was something that I was looking to try.
I'd also like to express a desire for detailed documentation on exactly what VIRL can and can't do, along with more information about back-end limitations of the VIRL platform. To me it seems like I am learning more through discovery versus having a decent grasp on where limitations exist and thus can design topologies around limitations to begin with (which is what lead to my feature request, seeing 3 48 port modules and wanting to use them for connections).If there was a definitive administrator's guide and a design guide, I would think it would be easier to make informed decisions when designing topologies versus having a go and seeing what works. Instead I'm often reading through forum posts, watching a good number of YouTube videos, and reading any blogs that I can find to cobble together a good understanding of what VIRL can and can't do. I don't mean for this to be a harsh rebuke or criticism (my apologies if it comes across that way), but I'm just trying to relay my thoughts and hopefully add to the drumbeat for thorough documentation. Thanks for reading my request!
Posts: 1
Participants: 1