Hey all,
I just joined an IT team at a new company, and am working on trying to implement a project that the previous sys admin had signed off on and ordered equipment for, but then left the agency.
The specific point of this post is to try to wrap my head around, and get some pointers, on a pair of new 48 port Cisco Nexus 9300 switches that were purchased for the CoLo. The CoLo's current switches support Stacking, and are regular IOS, but it doesn't look like these Nexus 9300 switches support stacking, and Cisco apparently released NX-OS, so I can't just mirror the old switches' configurations. I've seen a lot of other stacked switches in this organization, so I am trying to keep things in the same vein for consistency's sake. I've done some CLI configuration on Cisco equipment a couple decades ago, and occasionally have needed to log into an IOS device to update a port or make a small adjustment, but no "building from the ground up" since the early 2000's.
I have 6 VLANs to support:
- 10 Production
- 11 Voice
- 20 Storage (needs jumbo frames)
- 30 vMotion (needs jumbo frames)
- 98 Internet
- 99 DMZ
Looking at the other switch configurations, it looks like jumbo frames are assigned to the VLANs, but I can't seem to assign an IP or MTU size to the VLANs on the 9300s
So, my questions:
- Do 9300 switches support stacking, or is "vPC" the solution I'm looking for? Or do I just need to manage them as separate entities, and track which one is being operated on?
- The old switches made use of Channel Groups - I'm not super familiar with this, but my mental model of it so far is "port teaming." Can this be done across multiple switches without stacking? I'm trying for some redundancy with the two switches, which is another reason I'm really looking for the Stacking feature.
- These 9300 switches came with 40gb ports and cables, but other than maybe trunking between them, I don't see a purpose for it. Only our NetApp supports 10gbe, everything else is 1gb at best. Any guesses as to what the purpose of the 40gb links might be for, or if they were just included in the quote because... someone overlooked it/it was free/stock?
- well, 3a, really - if I do set up trunking between the switches, do I need to do anything crazy when I plug them into the router? Does it cause a loop/problem if I trunk router port 1 to sw1/1, sw1/2 to sw2/2, sw2/1 to router port 2?
- I've never had to manage a CoLo before - what is the group consensus regarding organizing the cabling? I have ~48 cables to plug in, and two 48 port switches, so I'm at 50% capacity. Given that we have a lot of power stuff, I'm planning to run ethernet on the left side of the rack, power on the right. Should I configure the ports on the switches clustered by device, or by VLAN? What makes it easier to manage in long run?
- I assume I just need to configure specific ports to jumbo frames, since I apparently can't configure VLANs with an IP and MTU sizes?
No comments:
Post a Comment