Cisco UCS blade server and switch configuration


The FlexPod for Epic software is designed with fault tolerance at every level. There is no single point of failure in the system. We recommend the use of hot spare blade servers for optimal performance.

This document is intended to provide high-level guidance on the basic configuration of a FlexPod environment for Epic software. In this section, we present high-level steps with some examples to prepare the Cisco UCS compute platform element of the FlexPod configuration. A prerequisite for this guidance is that the FlexPod configuration is racked, powered, and cabled per the instructions in the FlexPod Datacenter with FC Storage.

Cisco Nexus switch configuration

A fault-tolerant pair of Cisco Nexus 9300 Series Ethernet switches is deployed for the solution. These switches should be cabled as described in the section “Cabling Diagram.” The Cisco Nexus configuration makes sure that Ethernet traffic flows are optimized for the Epic application.

  1. After the initial setup and licensing are completed, run the following commands to set global configuration parameters on both switches:

    spanning-tree port type network default
    spanning-tree port type edge bpduguard default
    spanning-tree port type edge bpdufilter default
    port-channel load-balance src-dst l4port
    ntp server <global-ntp-server-ip> use-vrf management
    ntp master 3
    ip route <ib-mgmt-vlan-gateway>
    copy run start
  2. Create the VLANs for the solution on each switch using global configuration mode:

    vlan <ib-mgmt-vlan-id>
    name IB-MGMT-VLAN
    vlan <native-vlan-id>
    name Native-VLAN
    vlan <vmotion-vlan-id>
    name vMotion-VLAN
    vlan <vm-traffic-vlan-id>
    name VM-Traffic-VLAN
    vlan <infra-nfs-vlan-id>
    name Infra-NFS-VLAN
    copy run start
  3. Create the NTP distribution interface, port channels, port channel parameters, and port descriptions for troubleshooting according to the FlexPod Datacenter with FC Cisco Validated Design.