In order to use this feature, the storage controller must have a Converged Network Adapter (CNA) that is capable of FCoE and traditional Ethernet on the same port. This type of interface is called a Unfied Storage port. In UCS Releases 2.1(1a) and later, the ability for both IP-based storage and Fibre Channel over Ethernet (FCoE) to be used on the same interface was added.
Prior to UCS Release 2.1(1a), appliance ports only worked for IP-based storage traffic, such as the Network File System (NFS) and the Internet Small Computer System Interfaces (iSCSIs). If storage is configured in Active/Passive mode and both fabric interconnects require communication to the same controller.If storage and servers are located in different subnets.If storage must be accessed outside of the UCS domain.There are number of reasons why an upstream switch should allow storage appliance port traffic. Why Appliance Port VLANs Should be Allowed on Uplinks When a VLAN is created for an appliance port in the Appliances section of LAN tab, make sure to create the same VLAN in the LAN Cloud tab. MAC addresses on these interfaces are learned by the fabric interconnect.It contains a list of allowed virtual LANs (VLANs).UCS appliance ports are used to directly connect a storage appliance to UCS fabric interconnects.Īn appliance port behave similar to virtual ethernet (vEthernet or vEth) ports: Refer to Cisco Technical Tips Conventions for information on document conventions. If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. This document is not restricted to specific software and hardware versions. There are no specific requirements for this document. This document is intended to assist Unified Computing Systems (UCS) administrators who configure direct attached storage on the Cisco UCS platform.Ĭontributed by Dmitri Filenko and Andreas Nikas, Cisco TAC Engineers.
0 kommentar(er)
