Several key points of configuration for direct storage and cascading with mds in the ucms manager 2.1

In a recent project, csico UCS have been installed and debugged. Compared with some related information on the Internet, the related information on the Internet is older. Generally, In the UCMS 1.4 version, the connection array is 6120XP, previously, UCSM 2.0 must connect to the FC storage switch of the cisco MDS series before connecting to the storage. However, the connection array after UCMS manager 2.0 can be directly used as a storage switch.

The implementation project uses two cisco 6296XP as the cluster and connects to two ucsboxes. The blade server does not have a local hard disk and is started from the storage through sanboot, 6296 is directly connected to the emc fc port. One 6296xp is cascade with the remote MDS 9148 (single-mode, different buildings), and The MDS9148 is connected to the backup storage.

The following figure shows the connection of the apsaradb for memcache instance:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/012330F58-0.png "style =" float: none; "title =" 1.png"/>

The internal connection of each dashboard is as follows:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123303O3-1.png "style =" float: none; "title =" 2.png"/>

The version of the apsaradb for memcache manager is as follows:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/01233051c-2.png "title =" 3.png"/>

6296 the specific configurations, such as the cluster and management interface, are not described in detail. The following describes the differences and key points between apsaradb for redis 1.4 and apsaradb for redis 6296 and apsaradb for redis 1.4 and apsaradb for redis:

1. settings for direct storage of 6296XP:

To directly store 6296 as a FC Switch, you must set 6296 to FC Switch Mode, and the other is FC End-Host. After you change the settings, the array restarts.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/012330KK-3.png "title =" 4.png"/>

Next, we need to set the specific port to FC. Here it is quite different from the previous version of 2.0. Right-click the port and find that the option is not set to FC port ,:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123301H5-4.png "title =" 5.png"/>

The correct settings are as follows: Click config Unified ports and an alarm is displayed, for example:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/01233054B-5.png "style =" float: none; "title =" 6.png"/>

Note:: There is a pull small horizontal bar in this port diagram. It is on the far right by default. It is ignored at the beginning, and the horizontal bar is pulled to the left. The port color turns purple, the purple port is changed to the FC port, that is, the FC port can only be selected at the end and is continuous. Unlike other ports, you can change the port type as needed. In addition, if the port is changed to FC port and the connection array needs to be restarted, it is recommended that you set several more ports at a time. However, note that these FC ports are used no matter whether these FC ports are connected or not, after it is set to FC, it must be regarded as license. Therefore, disable unused ports. In this way, license is enough. enable is required and the connection array does not need to be restarted.

650) this. width = 650; "src =" http://img1.51cto.com/attachment/201306/154336333.png "style =" float: none; "title =" 7.png"/>

Return to the figure above. You can set the Port type on the corresponding FC Port first, and set the Port for connection Storage to config as FC Storage Port, set the remote MDS switch to uplink Port.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123304Z3-7.png "style =" float: none; "title =" 8.png"/>

In the past, the FC zones were configured on the mds fc switch, the cisco 6120 connection array was connected to the MDS switch as the host mode, and the switch enabled the NPIV mode, but now we connect to the array 6296 for direct storage, and the partition of the zone can be on the 6296. refer to the following description in the cisco UCSM2.1 configuration document.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123302010-8.png "style =" float: none; "title =" a1.png "/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123301N8-9.png "style =" float: none; "title =" a2.png "/>

As described in the Manual, the NFS Manager-based zoning can be directly connected to the storage or directly connected to the upstream FC switch. This is exactly the mode I need. The key points are as follows:

By default, the connection array disables FC zoning. You need to enable zoning in the corresponding vsan:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123301242-10.png "title =" s5.png "/>

Zoning settings involve the Storage conection policy and vHBA initiator Group settings. They can be pre-defined or defined in the Wizard that defines the service profile template.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/012330F37-11.png "title =" s1.png "/>

For example, this zoning configuration is not available in mangager1.4. In Step 4th zoning configuration vHBA initiator Group of the manager2.1 service template wizard, click "created storage connection policy" and click "+" on the right, create FC Target Endpoit. The wwpn number is the wwpn of the FC port that needs to be directly stored. You can check the wwpn number on the storage configuration page and enter the four storage FC wwpn numbers connected to two 6296 servers, respectively, for example, a vHBA initiator Group is created and the corresponding storage connection policy is bound,

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123303328-12.png "title =" s2.png "/>

You need to bind the vHBA initiator Group to a specific vHBA card, for example:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/0123302447-13.png "title =" s3.png "/>

In this way, the UCS blade can automatically generate the corresponding zone, and the initiator connection of the UCS can be seen on the storage. When the remote Cascade MDS 9148 switch is used, we need to pass the zone information to the MDS. Therefore, do not configure the zone information on the mds. If there is a configuration, we recommend that you clear the configuration first, after the basic information of the FC switch is set in the vswitch console, set the corresponding port connecting to the vswitch 6296 to the trunk Mode, that is, the E Mode, add the wwpn of the FC to the backup storage corresponding to the FC target Endpoit configured in the storage connection policy in the NFS manager. On the MDS switch, show zoneset to view the zone information transmitted by 6296, on the backup storage, you can also see the connection information of the initiator of the ucs blade. After the information is transferred to the corresponding host, you can see the storage space.

This article is from the "czq227 blog", please be sure to keep this source http://czq227.blog.51cto.com/2395/1216779