SOLVED
Hi All,
I implemented our CS300 into our existing environment a few months back with no problems, quick and easy and the thing just works great.
We're a very small office that typically buys 2 or 3 small servers a year (dell poweredge 1U, nothing crazy), so we have about a half rack of existing 1u servers.
We just made the jump to a Cisco UCS Mini with 3 blades and I have been running around in circles not only trying to understand UCS setup in general, but how to integrate it with our current server/network/san setup. We are currently running a vSphere 5.1/5.5 environment.
I've found a couple helpful documents from Nimble, but none of the topologies match what I have. Forgive my terrible Visio skills:
I have a small dell powerconnect 1gb switch stack (2 switches) for iSCSI. The Nimble has multiple 1gb connections from each controller to each switch in our iSCSI stack.
I have a larger dell powerconnect 1gb switch stack for everything else. Workstations, phones, and servers. Each server has 2 nics, each nic connecting to both the iSCSI stack and the "data" stack.
I'm having a hard time wrapping my head around the way that the nics in the UCS FI's work and how those correspond to "vNICs". It would seem in my head that I would need to use pinning to pin 2 interfaces for data and 2 interfaces for iSCSI and hook them up to the corresponding switches. Does that sound at all right to anyone? I appreciate any pointers.
Brandon,
I assume you've looked at the documentation on InfoSight which unfortunatley doesn't cover every possible configuration as you've found.
The following is designed as a getting started guide which may help explain some of the terminology: http://uploads.nimblestorage.com/wp-content/uploads/2015/05/22100349/nimblestorage-smartstack-getting-started-guide.pdf
Although it does reference the topology you appear to have it tells you to ask for help 
, so I have what I believe you need based on the information you provided above. If you have multiple iSCSI subnets then this would be done differently.
From what you have said above you need the following:
Connectivity to one or more upstream access switches. (Single iSCSI VLAN)
The Nimble array can be connected to one or more upstream switches. The upstream switch (Nexus 5K in the below example) will need to configure the connections to the Nimble array as non-tagged access ports. The connectivity from the UCS FIs to the Nexus 5K can be of type “Network Port” or “Upstream Port” with a native VLAN set to the iSCSI VLAN. Note that if desired you can additionally use UCS pinning to specify which path to a given FI a host will take. This is a legacy mechanism for MPIO traffic, but will work when you have a single subnet for iSCSI connectivity. Note: using UCS interface pinning is not a substitute for host based MPIO requirements.
I would recommend you speak to your SmartStack Partner to assist further with any configuration work.
Thanks
Phil
This probably does not help much but we recently installed a UCS Mini system. This is the network layout that we ended up with:
We have a single 10GB switch that we wanted to use (I think similar to your setup) I think we were able to make it work temporary while we transitioned off of our old servers. but in the end it was easier for us to directly attach to the UCS Mini. I would think you would need two switches if you wanted to maintain redundancy?
Nimble has a few different documents on configuration, however since I am new to the UCS world I ended up using parts of all of the documents to piece things together. I could not find one document that covered every from start to finish. I I can help please let me know. (I am no expert on UCS or Nimble, but our system seems to be running pretty well the way it is configured.
-Kris