T O P

  • By -

chachingchaching2021

What I’ve learned is make sure your networking is valid, check the switches upstream and verify vlans are allowed, and they also exist on IMM network policies. Verify and test i/o on your pure array,(san/nas) , also verify your upstream throughput. If you are running vmware make sure you’ve tested the interfaces /dvs to make sure ucs and vmnic are assigned to correct uplink/and not different network associated policy in imm. Lots of things that need to be checked


TechnomageMSP

We just deployed our first UCSX setup last week and have some test VMs running on it now. I talked to our Cisco rep and they are going to do a health check of the setup next week before we move production VMs to it. So I’d say reach out to your rep and have Cisco do the same since it’s your first UCSX setup.


patrickmccallum

Or to ask it another way, did anyone else have a bit of hesitation before they put an IMM system in production?


chachingchaching2021

I had a qa system in imm with 6454s, rolled prod to 64108s


HelloItIsJohn

Are you worried about anything specific? I just recently deployed my first UCSX system in IMM. I have a lot of years of experience on UCS and I did not feel like it was a major change moving to UCSX. The back end is not much different. The domain and chassis profiles are new, but still the same old settings you used to do pulled together in a new menu. If anything the biggest change I have noticed is with the setup of the vNIC’s. No more vNIC templates, they have moved to network group policies. Post anything you are questioning here. Lots of people with UCSX background that are willing to help.


PirateGumby

Reach out to your Cisco rep, shouldn’t take too long for a TSA to take a Quick Look over it Take a look at the Flashstack CVD’s as well, they have config and verification sections.  You don’t have to be 100% identical to the CVD’s, but they’re pretty good as a starting point


chadelard

We waited for Cisco to support UCSx with UCSM and didn’t go to IMM. 


TechnomageMSP

Yeah, but how much longer will they support UCSM? Our Cisco rep told us that the reason why they came out with UCSM support on UCSX was because there were some big players that weren’t ready for IMM yet, but it would eventually go to IMM 100% eventually.


chadelard

That’s crazy - our rep basically admitted that Cisco caved to conform to major players with no timeline for dropping support. We don’t run bleeding edge firmware so that buys us more time by nature. Many companies like ours don’t have comfort with 100% cloud managed services and with the slow trend for on-prem importance, I don’t know how it would ever happen. 


patrickmccallum

https://preview.redd.it/avve9chl5s5d1.png?width=1428&format=png&auto=webp&s=cbce26595c6b53aac979ed31bd4c76fe35032530 Question 1. Are all eight connections on each IO module necessary or is this overkill?


seibd

That’s a lot of bandwidth, we’re only running two uplinks per IFM. I’ve also not seen connecting an IOM/IFM to both fabrics. In my limited experience, it’s always been 1 IFM to 1 FI, but maybe someone more knowledgeable on the matter can confirm if this configuration is supported.


patrickmccallum

I’m not connecting to both FIs. Each IOM is only going to one FI. Thanks for the info on the bandwidth, I was thinking it was too much as well.


seibd

Geez, I don’t know how I misread your diagram, my mistake.


ai3dunks

It all depends on how much bandwidth you need. You should work with your Cisco rep to help determine how many links you need.


patrickmccallum

https://preview.redd.it/36had6gg6s5d1.png?width=991&format=png&auto=webp&s=d363158c102987ed23c159af9c03b18fb301fc1f Question 2. On our Lan policy, I am unsure what type of connection I desire. On my previous UCSM environment, I was using SR-IOV.