Cisco UCS CNA M71KR Handbuch - Seite 3

Blättern Sie online oder laden Sie pdf Handbuch für Server Cisco UCS CNA M71KR herunter. Cisco UCS CNA M71KR 14 Seiten.

Each vNIC must be associated with one or more VLANs, which means each VLAN must be globally

configured, and the default VLAN (VLAN 1) must still be specifically associated with a vNIC if any default

network traffic is to reach the adapter on the blade associated with the profile that contains the vNIC. The

most typical simple configuration is a vNIC which supports only the default VLAN.

There is a flag, most often associated with the default VLAN, that declares a VLAN the default network for a

particular vNIC. This flag indicates that traffic on that VLAN comes through to the NIC untagged, so in other

words, the NIC in the OS can remain VLAN−unaware.

If a vNIC supports VLANs, which are not the default network for that particular vNIC, traffic for those

VLANs come through to the NIC with VLAN tagging intact. This NIC must then be configured in its OS as

VLAN−aware.

Physical Adapter For adapters with only physical NICs (Cisco UCS M71KR, Cisco UCS 82598KR), you

must create a vNIC for each NIC you want to make usable on the network within Cisco UCS. Then, vNIC has

a switch setting and a failover flag. For the Cisco UCS 82598KR, you must match the physical setting so that

the first adapter goes to switch A and the second to switch B, and you cannot choose failover. For the Cisco

UCS M71KR, each vNIC is associated with a particular switch, but you can enable failover.

Virtualization Capable Adapter The Cisco UCS M81KR adapter supports NIC virtualization for either

single OS or for VMware ESX. Inside a single OS, each Cisco UCS M81KR vNIC is presented as a physical

adapter. For VMware, a special feature allows Cisco UCS M81KR vNICs to be presented directly to the guest

OS, bypassing the VMWare virtual switch layer. This allows efficiency and also allows Cisco UCS to

reconfigure network infrastructure if virtual machines migrate between ESX server instances on different

blades.

Main Task

No network or SAN connectivity for the blade server through Cisco UCS fabric exists without a service

profile. This document shows how to configure basic LAN and SAN connectivity for a Cisco UCS blade with

the creation of a Service Profile with these objects in order to enable a Cisco UCS blade for LAN and SAN

connectivity:

Create global VLAN (Make sure this is already created before the creation of a Service Profile)

Create global VSAN (Make sure this is already created before the creation of a Service Profile)

Create vHBAs within this Service Profile

Create vNICs within this Service Profile

Associate the created Service Profile to a Cisco UCS blade

This document assumes that Cisco UCS Manager connectivity works and all hardware was discovered

correctly.

For any VLAN to be supported on any blade, a VLAN object must be created in the global Cisco UCS

configuration in the LAN tab on the navigation panel. You can also create VLANs associated with only Fabric

Interconnect A or only Fabric Interconnect B; but it is more flexible to just create them globally, and for the

VLANs to be enabled on either Fabric Interconnect.

Note: You need a unique VLAN ID for each named VLAN that you create. You cannot create VLANs with

IDs from 3968 to 4048. This range of VLAN IDs is reserved.