With default behavior, appliance ports are shut down if the uplink that is pinned to it goes down. Failover must be configured on the storage side and must be implemented with the correct network design while specific failover behavior for storage controllers are kept in mind, dependent on the storage controller model. By design, UCS fabric interconnects operate as two independent fabrics. Note: The native VLAN on the appliance port is not required in this configuration.įailover cannot be configured in the UCS side for appliance ports. For example, when you access both the NFS Shares and the iSCSI LUNs via the same appliance port, configure the appliance port in Trunk mode with two different VLANs allowed across the link (one for the NFS and another for the iSCSI). Use of the same VLAN for multiple storage protocol trafficĪs a best practice, each protocol should be placed into a separate VLAN.If a VLAN tag is added in the appliance port configuration on the UCS side (done by configuring the appliance port in either Access mode or when using the Native VLAN while in Trunk mode), then do not configure tagging for the same VLAN on the storage controller side.
Referred to as double VLAN tagging, this configuration breaks communication over the VLAN.
Configuration of the VLAN tagging on both the storage side and on the UCS side simultaneously. If the storage controller is not capable of VLAN tagging, then the use of an access port is required. In this case, multiple VLANs can be used on the same link, which allows for isolation of different protocols on the wire. The decision about whether you should configure your appliance ports in Trunk or Access mode depends on the capabilities of the storage appliance. If the storage appliance has the capability to add VLAN tags, then Cisco recommends that you configure the appliance ports in Trunk mode and configure the VLAN tagging on the storage side for maximum flexibility. However, there is no virtual Port-Channel ( vPC) support. UCS supports Static and Link Aggregation Control Protocol (LACP) port channels for appliance port configuration. In order to verify that the port is configured as a unified storage port, login to the Cisco NX-OS shell and verify the port's current configuration with this command: ucs01-A(nxos)# show running-config interface eth 1/5 Tip: For information about how to configure a Unified Storage port, refer to the Configuring an Appliance Port as a Unified Storage Port section of the Cisco UCS Manager GUI Configuration Guide, Release 2.1. 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. Show mac address table traffic curent software#
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)
