Niles Pyelshak is a Customer Support Engineer for Cisco TAC works in Server Virtualization Team. She has several years of networking and virtualization experience. She recently passed her CCIE Certification in Data Center (#44608). As a Network Engineer, Niles was accustomed to getting on the command line interface (CLI) to configure and build her network. In server virtualization it is a little different. She is always amazed at how servers are mostly managed by Graphical User Interface(GUI) interfaces and CLI. One can not underestimate the power of both interfaces and in this Webcast, Niles will leverage both GUI and CLI to demonstrate the UCS life of a packet.
The following expert was helping Niles to answer few of the questions asked during the session: Robert Burns. Robert is and expert in Data Center technologies and has vast knowledge in this topic.
A: Correct. IOMs are essentially MUXes. No local switching functionality.
A: Correct. If there is a southbound switch before the IOMs, in the case of VMware vSS or vDS, then yes local switch is possible.
A: Correct. There's no routing on the FI's, they are L2 only.
A: The 20 chassis limit includes the 5108 B-series chassis as well as FEXes.
A: Yes, FEXes would count as a Chassis. Keep in mind, though a FEX counts as a chassis, each can support another 32 10G connections. The reason we limit it to 160 servers or 20 chassis, is to limit the possible failure domain.
A: The VIC1240 + Expander expands the bandwidth without creating another adapter on the host. The 1240 + 1280 would show up as two separate adapters on the host. Functionally they operate at the same total speed, just across one single or multiple ints.
A: Twinax (copper) or Optic OM3 10G cable
A: Just choose B in that case. Not a big deal.
A: Depends on the host. The OS will have an two interfaces, one to FI-A, one to FI-B. In the case of VMware, it would depend which Uplink you attach to the vSwitch or vDS. But yes you can manage this.
A: Can you elaborate what you're asking?
A: Are you talking about the 2 socket and 4 socket blades? or the blade we codenamed as "Yosemite"? I assume you're referring to the full width Intel Brickland platform known as the UCS B260 M4. This will not be specifically covered in this session, but we can speak to full width considerations.
A: Correct. The internal traces are channeled, unknown to the host. That's what gives the 10G, 20G or 40G total bandwidth (depending on the IOM model)
A: Only to any blades that need to be re-pinned. If the pinning doesn't change, the server's networking will be unaffected.
A: Correct. The IOM <--> adapter Port channels aren't configurable (automatic), but the FI <--> IOM is configurable. Discreet vs. PC mode.
A: It's not. PC is a fat shared pipe, whereas discreet will guarantee at least 10G dedicated, but I've never seen any customer saturate 80G of bandwidth sustained. Always use PC if the HW supports it.
A: If you have 2 IOM -> FI links, blades it would go Odds/Evens across the two links. 1,3,5,7 -> Link1, 2,4,6,8 -> Link 4. With four links its 2 per link, round robin.
A: I usually start from the host, and work outward up the IOM, then FI, to external from UCS.
A: The VIF# will identify it as a vnic or vhba (eth vs. fc) traffic.
A: The UCSPE (Platform Emulator) can be found on the developer network.
A: Its auto tagged. When you assign an FCoE VLAN to a VSAN, it will take all the storage traffic with this VLAN tag for you. The FCoE VLAN ID is only significant with the UCS domain, it will never leave the UCS domain.
A: That's completely possible. You just need a compatible Adapter.
A: YES. UCSM 3.0 is HTML5 based.
A: FW auto install is the preferred way, but otherwise we do an inside-to-outside manner. Starting with the inner most device (adapters) and work outwards to the FI's being last. The FW Upgrade/Downgrade guide details all the best practices.
A: Hopefully by this summer.
Cisco UCS Faults and Error Messages
Ask the Expert: Demystifying Unified Computing System (UCS) Interfaces for troubleshooting
Webcast Slides: Demystifying Unified Computing System (UCS) Interfaces for troubleshooting