Cisco UCS Invicta C3124SA Appliance Administration and ... · Drive Wear Monitor 2-2 Drive Tasks 2-2 Removing a Drive 2-3 Performance MB/s, IOPS, Latency, and Utilization Monitors

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco UCS Invicta C3124SA ApplianceAdministration and Configuration GuideVersion 5.0.1.2a

March 18, 2015

Text Part Number:

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on, users are encouraged to try to correct the interference by using one or more of the following measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician for help.

Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, FlipMino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work,Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; andAccess Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, theCisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, theIronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY,PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo areregistered trademarks of Cisco and/or its affiliates in the United States and certain other countries.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco UCS Invicta Appliance Installation and Service Guide© 2015 Cisco Systems, Inc. All rights reserved.

The Cisco UCS Invicta C3124SA Appliance Open Source file can be found at: https://autosupport.whiptailtech.com/documentation/OpenSource/Invicta_Appliance_5.0.0_Open_Source_Documentation.pdf

http://www.cisco.com/go/trademarks

https://autosupport.whiptailtech.com/documentation/OpenSource/Invicta_Appliance_5.0.0_Open_Source_Documentation.pdf

iiiCisco UCS Invicta C3124SA Appliance Administration and Configuration Guide

C O N T E N T S

C H A P T E R 1 Overview 1-1

Prerequisite Tasks 1-1

Cisco UCS Invicta C3124SA Appliance Interface Overview 1-1

Licensed Features 1-8

Initial Steps 1-8

Logging into the Appliance 1-8

Document Roadmap 1-10

C H A P T E R 2 Home 2-1

Main Dashboard 2-1

RAID Health 2-1

Node Status 2-2

Drive Wear Monitor 2-2

Drive Tasks 2-2

Removing a Drive 2-3

Performance MB/s, IOPS, Latency, and Utilization Monitors 2-4

Administration Guide 2-4

Installation Guide 2-4

C H A P T E R 3 Array Configuration 3-1

Network Settings 3-1

Creating a New Bond 3-1

Default Gateway 3-3

DNS Nameservers 3-3

Static Routes 3-4

Edit Bond 3-4

Delete Bond 3-5

Enable/Disable Bond 3-5

Enable/Disable Fibre Channel Interface 3-6

Create a Virtual Interface 3-6

Create a VLAN 3-7

Configure Devices 3-7

Check Performance 3-7

Host Settings 3-8

Contents

ivCisco UCS Invicta C3124SA Appliance Administration and Configuration Guide

Storage Allocation 3-8

Physical Space (Data Reduction) 3-9

Storage Trend (Data Reduction) 3-9

Physical Space Alerts 3-9

iSCSI Settings 3-9

Changing Initiator IP Address Availability 3-10

Error Correction 3-10

Support Settings 3-10

Support Setting Configuration 3-10

System Update 3-12

Uninstall Update 3-13

Shutdown 3-13

Reboot 3-13

Alert Admin 3-13

Address Alert 3-13

C H A P T E R 4 LUN Configuration 4-1

The LUNs List 4-1

Create LUN 4-1

Increase LUN Size 4-2

Create Snapshots 4-2

Schedule Snapshot 4-3

Delete LUN 4-5

View LUN Performance Data 4-6

Initiator Groups 4-6

Create an Initiator Group 4-7

Add an Initiator to an Initiator Group 4-7

Map a LUN to an Initiator Group 4-7

Unmap LUN from Initiator 4-8

Delete Initiator Group 4-9

C H A P T E R 5 Asynchronous Replication 5-1

Communicating with a Partner Host 5-2

Cisco to Cisco 5-4

Cisco to Linux-LVM 5-4

Cisco to Linux-RAW 5-5

Cisco to Windows 5-6

Create a Pairing 5-7

Delete Async Replication Pairing 5-9

Verify Partner Host 5-9

Contents

vCisco UCS Invicta C3124SA Appliance Administration and Configuration Guide

Update Partner Host 5-9

Async Replication Scheduling 5-10

Restore 5-11

View Log File 5-12

C H A P T E R 6 Users 6-1

Create a New User Account 6-1

Assign or Unassign User Role 6-1

Delete User Account 6-2

Edit User Account 6-2

Create or Modify a Role 6-3

Delete a Role 6-4

Change Password 6-4

Contents

viCisco UCS Invicta C3124SA Appliance Administration and Configuration Guide

C H A P T E R

1-1Cisco UCS Invicta C3124SA Appliance Administration and Configuration Guide, Version 5.0.1.2a

1Overview

• Prerequisite Tasks , page 1-1

• Cisco UCS Invicta C3124SA Appliance Interface Overview, page 1-1

• Licensed Features, page 1-8

• Initial Steps, page 1-8

• Document Roadmap, page 1-10

This guide includes information about the Cisco Unified Computing System (Cisco UCS) Invicta C3124SA Appliance for both performance and data reduction silicon storage arrays.

Information applies to both types of arrays unless otherwise noted. Unique content is identified within the text.

Prerequisite Tasks Before you configure the network connections, ensure that you do the following:

• Verify that the hardware cabling and installation is correct and complete.

• Verify that a Web browser for accessing the Cisco UCS Invicta C3124SA Appliance Management GUI is available.

If you are unable to perform either of these tasks, contact Cisco Technical Support at [email protected].

Cisco UCS Invicta C3124SA Appliance Interface OverviewTable 1-1 provides a list of the Cisco UCS Invicta C3124SA Appliance GUI menu with an overview of each menu window and the task that can be performed from them.


Chapter 1 Overview

Table 1-1 GUI Menu

Menu Tab Menu Overview Tasks

Home Main Dashboard Displays health, wear, performance, utilization, and node status views.

• View drive Information

• Fail or Remove a drive

• Enable or Disable the Blink On function

• View the Performance MB/s, IOPS and Latency monitors

• View array wear indicator

• View Node Status to check if the node has Data Reduction capability

Administration Guide

Links to a PDF. —

Installation Guide Links to a PDF. —


Chapter 1 Overview

Array Configuration

Network Settings Displays network configuration information including network interfaces (individual and bonds) and Fibre Channel interfaces.

Permission-based.

• Change a device configuration

• Set a Default Gateway

• Set the DNS server

• Set Static Routes

Host Settings Identifies the Ethernet link, iSCSI IQN and Host Names.

Displays hostname, network link, and IQN names

Storage Allocation

Displays storage information. The right-click menu provides a menu option to create a logical unit number (LUN). In addition, a UCS Invicta C3124SA Appliance with Data Reduction can also display the Physical Space and Storage Trend from the right-click menu.

• View Cisco UCS Invicta C3124SA Appliance Storage Information

• Create a LUN

• View Physical Space (Data Reduction)

• View Storage Trend (Data Reduction)

iSCSI Settings Lists IP addresses that are available and which a host is allowed to connect.

Permission-based.

Move IP addresses between the Available and Allowed Portal Columns

Error Correction Provides an option to reconstruct or to rebuild the data block content using parity.

Permission-based.

Turn on or off

Table 1-1 GUI Menu (continued)



Chapter 1 Overview

Support Settings Contains configuration data including:

• Host name, mail server and user (SMTP), and time server (NTP).

• Autosupport (Carbon Copy) CC address (an internal customer address to which copies of Autosupport messages are sent.This field is optional; if no address is input only the Cisco technical support team receives Autosupport messages).

• The Send from Domain field allows Cisco technical support to identify the source of the Autosupport messages.

• Proxy URL/IP is the proxy server that the customer uses to direct outgoing requests.

• Proxy Port is the port number used when sending the outgoing requests.

• Click Save to save changes to these fields.

• Test Autosupport triggers the generation of an Autosupport message that is outside of the regular schedule and tests the Autosupport relay setting. This test includes collected data but does not include performance graphs.

• Post Service button triggers communication to the Autosupport server once the service repair or maintenance action was performed on the system by technician.

• System Update is used by the Administrator for starting a Service Pack (WSP) update package application process, when available.

View:

• Cisco UCS Invicta OS Version

• Complete configuration information fields

• Shutdown

• Reboot

• Test Auto Support

• Post Service

• Perform System Update




Chapter 1 Overview

• Click System Update to choose the WSP system update file that was sent by Cisco and then saved locally. Uploading this file loads system update onto the Cisco UCS Invicta C3124SA Appliance. After the file has been authenticated by the system, the Administrator is prompted through the remaining update process.

• Uninstall Update button displays immediately after an update is installed and is used to uninstall the last update.This button is only visible to those with administrative permission.

• Shutdown and Reboot commands are verified to prevent any unintentional action.

Permission-based.




Chapter 1 Overview

Alert Admin Icon on the Main Dashboard indicates the number of alerts present.

Alert Admin window lists short identification and notification timestamps of all active alerts sent during periodic system checks.

Permission-based.

Check and/or set an alert status to Resolved or Suppress

LUN Configuration

LUNs After the initial setup, you can create and configure LUNs.

Use the check boxes adjacent to LUNs to select an unlimited number of LUNs for deletion.

You can also use check boxes to select and view the performance of up to the first 5 selected LUNs.

Permission-based.

• Create LUNs

• Increase LUN Size

• Create Snapshot

• Schedule Snapshot

• Delete LUNs

• Check Performance

Initiator Groups Maps LUNs. The Initiator Groups list uses a tree structure that you can expand and collapse.

Right-click menus allow you to add an Initiator, map or unmap LUNs, and delete an Initiator Group.

Permission-based.

• View Initiator Groups

• Add initiator to Initiator Groups

• Add individual Initiator Groups

• View available LUNs

• Map or Unmap LUNs to or from an Initiator Group

• Delete an Initiator Group




Chapter 1 Overview

Async Replication

Pairings LUN-to-target pairing allows management and replication scheduling.

License- and permission-based.

• Create a New Pairing

• Verify the Partner Host

• Update the Async Partner Host

• Schedule (both Manual and Scheduled Replication)

• Restore (either to a New LUN or to the Original LUN)

• Replication and Restore Termination

• Download Cygwin Package needed for Windows Target

• Pairing Deletion

• View Logs (Snippets of Replication and Restore logs for each partner)

• Retrieve the device Public Key

Users User Accounts Requires that each user must have a user account and must be assigned one or more roles.

Permission-based.

• Create a New User Account

• Assign User Roles

• Edit or Delete a User Account




Chapter 1 Overview

Licensed FeaturesCisco offers optional features, such as Asynchronous Replication, that can be licensed, per device. To activate a licensed feature, please contact your Cisco sales representative or write to [email protected].

Licensed features are delivered over the Internet for clients with Autosupport during Call Home messaging or through a Cisco Service Pack Licensing download for those clients who are not connected to Autosupport over the Internet.

Initial StepsInitial steps for administering and configuring the Cisco UCS Invicta Cisco UCS Invicta C3124SA Appliance are as follows:

• Log in as the administrator

• Verify support settings (NTP, Time Zone, SMTP)

• Create roles

• Set up user accounts

• Configure LUNS and Initiator Groups

If you are responsible for the overall network administration, you must log into the Management Tool and set up the user account and role creation as follows:

Note If you experience a problem, please contact Cisco technical support.

Logging into the Appliance

Step 1 Power-on the Cisco UCS Invicta C3124SA Appliance and wait about 5 to 8 minutes.

Roles Creates roles with specific permission sets that are configurable from the Roles window. Without permission-defined roles, the default User Account permission allows the ability to view the Home Menu, Main Dashboard and the ability to change a password from the User Menu.

Permission-based.

• Cisco UCS Invicta C3124SA Appliance

Change Password Changes the default or compromised passwords to protect the accuracy of audit trails. A password change is required after the initial login.

• Change user password




Chapter 1 Overview

Note The power supply LED isamber when it is plugged in and green when it is powered on.

Step 2 Enter the IP Address of the device in the browser address bar.

Step 3 Enter the default username and password as shown:

Username: admin

Password: abc123

Note The administrator or user is required to change the login password after using the default password for the initial configuration or initial log in, as well as to accept the terms and agreement. The password “abc123” may not be reused.

A unique Login ID is needed so that the audit trail reflects a unique user. “Admin” if unchanged will not distinguish between those logged using that default name.

Step 4 Create a unique username (see Chapter 6, “Users”).

Step 5 Click Log out at the top-right of the window.

Step 6 Login using the new user account ID.

The Cisco Installation team will have configured the Cisco UCS Invicta C3124SA Appliance. The Network Configuration settings have been entered on the Support Settings window.

These settings include the following:

• Host Name

• SMTP Server and User

• Autosupport CC

• Send from Domain

• Proxy URL/IP

• Proxy Port

• NTP Server

• Time Zone

For more information about the Support settings window see Chapter 3, “Array Configuration.” Verify/Modify Network Configuration. To navigate to the Support Settings, do the following:

Step 1 Select Array Configuration > Support Settings.

The Support Settings window appears.

Step 2 Review current field information and modify as necessary. (For more information see, “Support Settings,” on page 3-10.)


Chapter 1 Overview

Document RoadmapThe remaining sections of this document provide information on each Cisco UCS Invicta C3124SA Appliance menu item and the tasks associated with them (see Table 1-1 on page 1-2).

Figure 1-1 Cisco UCS Invicta C3124SA Appliance Rear Panel Features

PSU1 PSU2

PCIe 1

PCIe 2

PCIe 3

PCIe 4PCIe 5

4 98 107 1165

2 3

3318

26

1

1 Power supplies (two) 7 1-Gb Ethernet dedicated management port

2 PCIe slot on riser 2: PCIe 5—full-height, 3/4-length, x16 lane)

8 USB 2.0 port

3 PCIe slot on riser 2:PCIe 4—half-height, 3/4-length, x8 lane)

9 Quad 1-Gb Ethernet ports(LAN1, LAN2, LAN3, and LAN4)

4 VGA video connector 10 PCIe slots on riser 1:PCIe 1—full-height, half-length, x8 lanePCIe 2—full-height, half-length, x16 lanePCIe 3—full-height, half-length, x8 lane

5 Serial port (RJ-45 connector) 11 Rear Identification button/LED

6 USB port –

C H A P T E R


2Home

• Main Dashboard, page 2-1

• Drive Tasks, page 2-2

• Administration Guide, page 2-4

• Installation Guide, page 2-4

Main DashboardThe Main Dashboard window graphically depicts the RAID health and its unused drives.

The dashboard offers right-click context menus that allows you to perform various drive operations.and to view Performance MB/s, IOPS and Latency monitors and an array wear indicator.

RAID Health

Figure 2-1and Figure 2-2 provide legends for the colors of the RAID and Drive Status:

Figure 2-1 RAID Status Legend

RAID Color Meaning

Good

Bad

Degraded

Recovering

3526

60

2-2Cisco UCS Invicta C3124SA Appliance Administration and Configuration Guide, Version 5.0.1.2a, Version 5.0.1.2a

Chapter 2 Home

Figure 2-2 Drive Status Legend

Node Status

This area conveys whether or not the Cisco UCS Invicta C3124SA Appliance has Data Reduction.

Drive Wear Monitor

This speedometer provides a pictorial view of the drive’s wear status. Drives should be replaced when the wear arrow is in the yellow area (0-20).

Drive TasksTo perform drive tasks:

Step 1 Right-click a drive in the Node Health Information window.

The drive tasks right-click menu appears.

Step 2 Do any of the following:

• If you want to view drive information, choose Info.

The Node Health Information window displays specific drive information, including drive position, device model, serial number, firmware version and LU WWN Device ID.

• Choose Fail to fail a drive, if necessary.

– If the RAID set is in a degraded mode, the Fail menu option is not available on any RAID.The verification for the fail drive appears. The failed drive will be in a “bad” state.

– The ‘Remove’ right-click menu option provides a means to safely remove a bad drive to the unused tab.

Note A spare cannot be failed. To remove a spare see, Removing a Drive .

• Choose Enable or Disable Blink On to enable or disable the Blink On feature.

Drive Color Meaning

Spare

Good

Bad

Unused

3526

90


Chapter 2 Home

A confirmation messages indicates the Blink On/Off status.

Removing a Drive

The ‘Remove’ right-click menu option provides a means to safely remove a drive without causing data corruption.

Note While not encouraged, a drive other than a spare from a RAID set may be removed using the Fail menu option and the procedure described in Drive Tasks

To remove a drive, do the following:

Step 1 Right-click the drive.The right-click menu appears.

Step 2 Choose Remove.The drive is removed and placed in the Unused Tab. From the Unused Tab do any of the following:

• Get drive information

• Enable/Disable Blink On

• Assign drive to a RAID set

Caution For drives pulled from the drive slot or failed using the ‘Fail’ menu, please contact Cisco technical support before reassigning the drive.

• Physically remove drive from the array, if necessary.


Chapter 2 Home

Performance MB/s, IOPS, Latency, and Utilization Monitors

Note Cisco UCS Invicta C3124SA Appliance supports vStorage APIs for Array Integration (VAAI), which dramatically improves communication performance with VMware ESX servers.

The Performance tab provides a point-in-time rendering of MB/s, IOPS, and latency characteristics on a last-10-minutes, daily and weekly basis. The chart auto-refreshes every 10 seconds. Mouse over a performance grid to view detail.

To view performance information, do any of the following:

• To view daily performance, click the icon in the top-right-hand corner of the performance graph.

• To view weekly performance, click the icon in the top-right-hand corner of the performance graph.

This information auto refreshes every 10 seconds and displays a point-in-time view.

To view details of a particular time frame by clicking your mouse and drag it over a lower time-line interval, for example, 17:25 to 17:50.

Administration GuideClick the menu item to link to a PDF of this document.

Installation GuideClick the menu item to link to a PDF of this document.

C H A P T E R


3Array Configuration

This section covers topics related to the Cisco UCS Invicta C3124SA Appliance configuration.

• Network Settings, page 3-1

• Default Gateway, page 3-3

• Host Settings, page 3-8

• Storage Allocation, page 3-8

Network Settings

Caution Modifying network settings will cause a brief interruption of connectivity to the C3124SA Appliance. Use extreme caution when changing the settings on this window.

The Network Settings menu window displays the Ethernet Bond Status table. This is a sortable list of all bonds currently available on this array. It also displays a sortable list of Fibre Channel interfaces. Right clicking an interface presents menu options, for example, enable/disable, and so on.

The top buttons on this window can be clicked to create a new network interface bond, set a default gateway, set the DNS servers, and set static routes.

This section describes how to create, edit, and remove a bond and explains the available bonding modes.

Caution Bond0 must not be deleted. Changing bond0 can potentially sever the array connection.

Creating a New Bond

To create a new bond, do the following:

Step 1 Choose Array Configuration > Network Settings.

The Network Setting window appears.

Step 2 Click Create Bond.


Chapter 3 Array Configuration

The Create New Bond dialog box appears.

Step 3 Complete the fields:

• IP Address - if verified, a check mark appears

• Subnet Mask - if verified, a check mark appears

• MTU

Note For most implementations, the MTU is <1500>; however, use <9000> if Jumbo Frames are required for assignment to this bond.

• Onboot - Yes/No. Informs the OS if this bond is to come online during the boot process.

• Mode - Choose a run mode from the drop-down list. (For explanations of the available modes, see Table 3.0 in Available Bonding Modes.

Step 4 Click Create Bond once all settings have been entered or click Cancel to return to the Network Settings window.

Available Bonding Modes

Table 3.1 describes the bonding modes that are configurable from the web interface.

Table 3-1 Bonding Modes

MODE NAME DESCRIPTION ADDITIONAL INFORMATION

mode=0

(balance-rr)

Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.

mode=1 (active-backup)

Active-backup policy: Only one slave in the bond is active. A different slave becomes active if and only if the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance.



Default GatewayThe default gateway is the device that connects the local network to another network.

To update the default gateway, do the following:



Step 2 Click Default Gateway.

The Update Default Gateway dialog box appears.

Step 3 Enter the Gateway IP address.

A check mark appears if it is a valid gateway.

Step 4 Click Save Gateway or click Cancel to return to the Network Settings window.

DNS Nameservers

The most important function of the Domain Name Server DNS servers is the translation (resolution) of human-memorable domain names and hostnames into the corresponding numeric Internet Protocol (IP) addresses.

To edit the Nameservers, do the following:



mode=4

(802.3ad)

Link Aggregation Control Protocol (LACP)

IEEE 802.3ad Dynamic link aggregation creates aggregation groups that share the same speed and duplex settings. This utilizes all slaves in the active aggregator according to the 802.3ad specification. Most switches require some type of configuration to enable 802.3ad mode.

Pre-requisites:

• ethtool support in the base drivers for retrieving the speed and duplex of each slave.

• A switch that supports IEEE 802.3ad Dynamic link aggregation.

mode=6

(balance-alb) [Default setting on Cisco Arrays]

Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic and does not require any special switch support.

ALB (mode 6) is the default mode.

Table 3-1 Bonding Modes (continued)

MODE NAME DESCRIPTION ADDITIONAL INFORMATION



Step 2 Click DNS Nameservers.

The Edit DNS Nameservers dialog box appears.

Step 3 Enter the DNS Nameserver IP addresses.

Step 4 Click Save DNS or click Cancel to return to the Network Settings window.

Static Routes

Static routes are routes through a data network that are described by fixed paths (statically). To create a static route, do the following:



Step 2 Click Static Routes.

The Static Routes window appears.

Add Static Route

To create a new static route for an active bond, do the following:



Step 2 Click Static Routes > Add Static Route.

The Create New Static Route dialog box appears.


• Network

• Mask

• Gateway - if verified, a check mark appears

Step 4 Choose from the Active Devices drop-down list.

Step 5 Click Create or click Cancel to return to the Static Routes table.

Edit Bond

To Edit a Bond, do the following:

Caution Changing bond0 can potentially sever the Cisco UCS Invicta C3124SA Appliance connection.





Step 2 Highlight a Bond from the Ethernet Bond Status list by mousing over it and right click.

The right-click menu appears.

Step 3 Choose Edit Bond.

The Edit Settings dialog box appears.

Step 4 Update the Bond information (see Table 3-1 for Bond Mode information).

Step 5 Click Save Bond to save edits or click Cancel to return to the Network Settings window.

Delete Bond

To delete a Bond, do the following:

Caution The option to delete bond0 has been prevented as that could potentially sever the Cisco UCS Invicta C3124SA Appliance connection.


The Network Settings window appears.



Step 3 Choose Delete Bond.

The Delete Bond confirmation dialog box appears.

Step 4 Choose Delete Bond to delete or Cancel to return to the Network Settings window.

Enable/Disable Bond

An existing Network Interface Configuration (NIC) Bond can be enabled or disabled, depending on its initial state, using the right-click menu:

Step 1 .Choose Array Configuration > Network Settings.




Step 3 Choose Enable /Disable Bond.

The confirmation dialog box appears, for example, a Disable Bond confirmation.

Step 4 Choose Enable/Disable Bond or Cancel to return to the Network Settings window.



Enable/Disable Fibre Channel Interface

To enable/disable an FC Interface, do the following:



Step 2 Highlight a Port from the FC Interface Status list by mousing over it and right click.


Step 3 Choose Enable/Disable.

The confirmation dialog box appears, for example, the Set Offline confirmation.

Note A READY status in the FC Interface Status GUI window indicates that the FC port in online but that there is an issue between the port and the FC Switch. Troubleshooting is needed to verify cable connectivity or other cause.

Step 4 Choose Online/Offline or Cancel to return to the Network Settings window.

Create a Virtual Interface

A virtual interface can be created from an existing Network Interface Configuration (NIC) Bond from the right-click menu:





Step 3 Choose Create Virtual.

The Create New Virtual dialog box appears.


• IP Address - If verified, a check mark appears

• Subnet Mask

• MTU


• Onboot - Yes/No. Informs the OS if this bond is to come online during the boot process

Step 5 Click Create Virtual once all settings have been entered or click Cancel to return to the Network Settings window.



Create a VLAN

VLANs allow a network manager to logically segment a LAN into different broadcast domains. VLANs allow users who are not physically on the same or even in the same buildings to belong to the same LAN.

A VLAN can be created from an existing Bond from the right-click menu. To create a VLAN, do the following:





Step 3 Choose Create VLAN.

The Create New VLAN dialog box appears.


• VLAN ID - Identification of the VLAN used by the standard 802.1Q.

• IP Address - If verified, a check mark appears

• Subnet Mask

• MTU


• Onboot - Yes/No. Informs the OS if this bond is to come online during the boot process.

Step 5 Click Create VLAN once all settings have been entered, or click Cancel to return to the Network Settings window.

Configure Devices

The Configure Device window displays the Slave and Unbonded interface status lists for the Bond and its virtual Bonds and VLANs selected from the Network Settings window. Bond configuration can be modified using drag-and-drop functionality.

Note Changes to the IP configuration of bonds may result in a requirement that the current browser session be closed and a new one started. The updated Network IP should be typed into the URL field to access the Web interface.

Check Performance

To view the status of bond performance, do the following:







Step 3 Choose Check Performance.

The Bond Performance Monitor appears. The legend definitions are displayed in Table 3-1, “Bond Performance Legend,” on page 8.

Step 4 Mouse over the graph to see specific point-in-time information.

Host SettingsThis section provides an option to view the Host Name, selection of a Network link, and view the IQN.

To view the Host Name or IQN or to select a Network link, do the following:

Step 1 Choose Array Configuration > Host Settings.

The Host Settings form appears.

Step 2 View the Host Name or Network Link or IQN currently configured for the device.

Step 3 You can use the Network link drop-down list to select a different Network Link that has been configured on the device.

Storage AllocationDisplays storage information. Right-click menu provides a menu option to create a LUN. Cisco UCS Invicta C3124SA Appliances with Data Reduction can also display the physical storage space and the storage trend.

Table 3-1 Bond Performance Legend

Packets Definition

Rxpck Number of received packets

Txpck Number of transmitted packets

RxkB Reception bandwidth in KB

TxkB Transmission bandwidth in KB



Physical Space (Data Reduction)

When the Physical Space option is selected from the right-click menu, the following information is provided:

• Total Size

• Available Free Space

• Data Reduction Savings

Caution Avoid filling up a LUN to its storage capacity as this may cause the system to become unresponsive.

Storage Trend (Data Reduction)

Storage Trends are used as a predictive tool to approximate how many days of storage use remain before the storage array is fully saturated. Trends are based on data captured daily on the amount of storage remaining.

Prediction strengths of high, medium and low probability are based on the quantity of data points and regression analysis validation. If enough data has been collected, the Storage Trend graph draws a statistically valid regression line, for example, 30 days of data points yields a prediction probability with a high strength.

Trend calculations without sufficient or with inconsistent data points will be calculated, but can be statistically weaker or inconclusive. If a calculation cannot be made based on the data points, a message appears to indicate this status.

Physical Space Alerts

The status of physical space is monitored on an hourly basis. Alerts are triggered at the capacities and frequencies listed in Table 3-2. These messages can be viewed from the Array Configuration menu under Alert Admin. Alerts are also sent to Autosupport and to the additional addresses provided in the Autosupport CC field on the Support Settings window. For information on alerts and how to suppress them, see See “Uninstall Update” on page 13.

iSCSI SettingsThe iSCSI Screen Lists the IP addresses by which an Initiator (a host) is allowed to access an Invicta appliance.The two columns represented on the window are:

• Allowed Portal: Lists IP addresses to which a host is allowed to connect.

• Available Portal: Lists all available IP addresses of hosts that can used to initiate a session.

Table 3-2 Capacity Alerts

Percent Full Frequency Sent

70 Once

80 Once

85 Once per hour



Changing Initiator IP Address Availability

Step 1 Choose Array Configuration > iSCSI Settings.

The iSCSI Information window appears.

Step 2 Use drag-and-drop functionality to move an Initiator to or from the Available to the Allowed Portal IP addresses columns.

Note If the Allowed Portals column is empty, there are no restrictions for access and all IPs listed in the Available column can be used for iSCSI communication

Error CorrectionThe Error Correction window provides an ability to turn Error Correction On or Off. The default is Off. If Error Correction is On and a data block becomes corrupted or inaccessible, Error Correction will reconstruct the data block content using parity. Some usage guidelines are:

• Where maximum data protection is needed, Error Correction is usually turned On.

• Where maximum performance is needed, Error Correction is usually turned Off as it has an impact on reading performance of up to 15%.

To access the Error Correction switch choose Node Configuration > Error Correction.

Support SettingsThe Cisco Installation Team will have configured UCS Invicta Scaling Array so that there is SRR communication and SSR-to-SSN communication. The SSRs are connected to the network and are now controlling the network data sent to the SSNs. Network Configuration settings have been entered on the Support Settings window.

These settings include:

• Host Name

• SMTP Server

• SMTP User

• Autosupport CC

• Send from Domain

• Proxy URL/IP

• Proxy Port

• NTP Server

• Time Zone

Support Setting Configuration

To verify or modify support settings, do the following:



Step 1 Choose Array Configuration > Support Settings.

The Support Settings window appears.

Step 2 Complete or modify field information as necessary. See Table 3-3, Support Settings Fields, for a description of the Support Settings fields.

Table 3-4 displays the button functionality that is available on the Support Settings page.

Table 3-3 Support Settings Fields

Field Description

Host Name Name assigned to array.

Simple Mail Transfer Protocol (SMTP) ServerEnter SMTP address. Used to transmit email across IP Networks. This is applicable only for email being sent directly from the Cisco Array if there is no connection to the Autosupport server over the Internet.

SMTP Username The SMTP user is the username used by the mail service to send out emails from the customer's servers.

User mail server needs to be set up to handle customer emailing.

Autosupport CC Address Enter the internal customer address to which copies of Autosupport messages are sent.

The Firewall must be configured to allow access to Port 443 outbound.

Send from Domain Applies only when emails are being sent directly from the Cisco Array if there is no connection to the Autosupport server over the Internet.

Proxy URL/IP The proxy server that the customer uses to direct outgoing requests.

Proxy Port The port number used when sending outgoing requests.

Network Time Protocol (NTP) Server Enter the NTP address. Used to synchronize the time of the clocks of computers over the network.

Time ZoneChoose location (and its associated time zone) from the drop-down list.

Time Zone Choose a location (and its associated time zone) from the drop-down list.



System Update

Clicking System Update opens a dialog box that asks the Administrator to choose the system update file that was sent by Cisco, which may have been saved locally.

Uploading this file loads the system update onto Cisco UCS Invicta C3124SA Appliance. After the file has been authenticated by the system, the Administrator is prompted through the remaining update process. For more information on system updates, see the Cisco UCS Invicta C3124SA Appliance Upgrade Procedure Guide.

Table 3-4 Support Settings Button Functionality

Button Description

Test Autosupport The Test Autosupport button is a trigger that generates an Autosupport message that is outside of the regular schedule and that tests the Autosupport relay setting. This test includes all of standardly collected data.

Post Service The Post Service button is used for triggering communication to the Autosupport server once the service repair or maintenance action was performed on the system by technician.

System Update The System Update is used when a permissioned Administrator receives a file containing an update.

Uninstall Update The Uninstall update button is visible immediately after the update is installed and is used for rolling back to the previously installed update.

Note This button is only visible if a user is permissioned to uninstall an update.

Shutdown The Shutdown button is used to shutdown the Cisco UCS Invicta C3124SA Appliance. A dialog box appears to verify Shutdown command to avoid any unintentional action.

Reboot The Reboot button is used to reboot the Cisco UCS Invicta C3124SA Appliance. A dialog box appears to verify Reboot command to avoid any unintentional action.

Caution A device reboot is required to complete an upgrade. Ensure that all hosts are disconnected from the device so that no IO is running during the upgrade installation.

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/invicta/upgradeguide/invicta-appliance-upgradeguide.html






Note Be sure to read and acknowledge the Release Notes and Instructions or the update will not initiate.

Caution Should you encounter any error or issue during the upgrade process, please contact Support before trying to uninstall the update. Doing so could potentially cause data integrity and/or performance issues.Only customer-installed upgrades can be potentially uninstalled.

Uninstall Update

The Uninstall Update button is visible immediately after the update is installed and is used for rolling back previously installed update.

This button is only visible if a user is permissioned to uninstall an update.

Shutdown

Click Shutdown to shutdown the Cisco UCS Invicta C3124SA Appliance. A dialog box appears to verify the Shutdown command to avoid any unintentional action.

Reboot

Click Reboot to reboot the Cisco UCS Invicta C3124SA Appliance. A dialog box appears to verify Reboot command to avoid any unintentional action.

Caution A device reboot is required to complete an upgrade. Ensure that all hosts are disconnected from the device so that no IO is running during the upgrade installation.

Alert AdminThe Alert Admin menu lists active alerts sent during periodic system checks. The alert entries include a short identification, last sent time and date, and status information.

To access the Alert Admin window, do one of the following:

• Click the Alerts icon on the Home window.

• Choose Array Configuration > Alert Admin.

The Alert Admin window appears.

Address Alert

To address an alert:

Step 1 Do one of the following from the Alert Admin window:

• Mouse over a unique alert.

• Use the check box to choose one or more alerts.



Step 2 Right-click the mouse.

A right-click menu appears with Suppress and Resolved options (see Table 3-5).

Step 3 Choose Suppress or Resolved.

Table 3-5 Alert Admin Actions

Action Description

Suppress Changes alert status from Active to Suppressed. Alerts are not resent during subsequent periodic System checks.

Resolved Removes selected alerts from the active list. However, should the same alerts recur during subsequent System checks, they will repeatedly appear in the active list until the issues causing these alerts are resolved.

C H A P T E R


4LUN Configuration

• The LUNs List, page 4-1

• Initiator Groups, page 4-6

Each Logical Unit Number (LUN) identifies a specific logical unit, which may be part of a drive, an entire drive or several drives in a storage array. A LUN, then, can reference an entire RAID set, a single drive or multiple drives. In any case, the logical unit is treated as if it is a single device and is identified by the LUN.

Once the initial Cisco UCS Invicta C3124SA Appliance setup has been completed, LUNs can be created and configured from the LUN Configuration window using buttons and right-click menus. The Administrator must determine the best LUN configuration.

The following section describes LUN Configuration tasks.

Note Only those who were assigned roles with the associated permissions can view and/or access these tasks.

The LUNs List

The list of LUNs has check boxes adjacent to them. These check boxes can be used for selecting an unlimited number of LUNs for deletion. Check boxes can also be used for selecting and viewing the performance of up to the first 5 selected LUNs. All columns are sortable.

Create LUN

To create a LUN:

Step 1 Choose LUN Configuration > LUNs.

The LUNs window appears.

Step 2 Click Create LUN.

The Create New LUN dialog box appears.

Step 3 Complete the Create New LUN fields:


Chapter 4 LUN Configuration

• Enter a name in the LUN Name field.

• Enter the size of the LUN presented to the operating system (expressed in gigabytes).

• Volume Group displays the free space on your array.

Step 4 Click Create LUN or click Cancel to close the dialog box without creating a new LUN.

Increase LUN Size

Note If a LUN is part of an Asynchronous Replication pairing, its size cannot be increased (see Chapter 5, “Asynchronous Replication”).


The LUN window appears.

Step 2 Highlight a LUN from the LUNs list by mousing over it and right click.


Step 3 Choose the Increase Size (GB) menu option.

Increase Size dialog box appears.

Step 4 Enter the new size into the Increase (GB) field.

Note LUN size can only be increased, not decreased.

Step 5 Click Update LUN or click Cancel and return to the LUNs list.

Create Snapshots

The Snapshot feature provides the ability to create virtual images of a LUN at a particular instant and does so without causing a service interruption.

Snapshot characteristics:

• LUN Snapshots are differentiated in the LUN list when the LUN’s “Origin” and “Snap%” columns are populated.

• Snapshots can be created either manually or on a schedule. A maximum of 10 snapshots is allowed per LUN.

• When a Snapshot is created, its initial size is automatically calculated based upon the size of the Origin volume.

• Snapshots are automatically resized based upon the number of changes to the Origin volume and the amount of free space left on the Origin volume.

• Snapshots can be mounted for read/write purposes.

• One or more Snapshots can be deleted manually.



• When available free space on the system falls below a threshold level of 10%, the system automatically deletes the oldest Snapshot(s) on the device to free up at least 15% of space. Neither manual nor scheduled Snapshots can be created until this 15% threshold is met.

• A LUN Snapshot can be merged (only) with its Origin volume, one Snapshot at a time, without concern about the order in which the Snapshots were created.

• Snapshot performance can be checked.

• When a Snapshot merge is in progress for an Origin LUN, neither manual nor scheduled Snapshots can be created until the merge is complete.

Note You should regularly monitor the growth of the Snapshot and the amount of disk space available on the device.

Caution If there is not enough free space for a Snapshot’s automatic resize, the Snapshot may become invalid and may no longer track changes on the Origin volume. In addition, any mounted file systems on that Snapshot device may be forcibly unmounted.

To create a snapshot, do the following:





Step 3 Choose Create Snapshot.

The Create LUN Snapshot dialog box appears.

Step 4 Enter the snapshot name and size, noting the available space.

Step 5 Click Create Snapshot or click Cancel to return to the LUNs window.

Schedule Snapshot



Step 2 Mouse over a LUN to highlight it and right click.


Step 3 Choose Schedule Snapshot.

The Snapshot Schedule Setup dialog box appears.

Step 4 Do one or both of the following:

Note Entries with “occurs every” interval set to “off” on the drop-down list are ignored.



• Click New Schedule Entry one or more times to schedule one-time or recurring Snapshots.

– Enter the Snapshot start time (24-hour clock) or use the Hour and Minute slide bar to choose a time.

– Choose a time interval, day of the week or calendar date from the Occurs Every drop-down list.

• Click Delete for any scheduled entry you want to remove.

Step 5 Click Save Schedule to save the LUN Snapshot schedule.

Merge Snapshot

When a Snapshot is merged, the data on the Snapshot replaces the data on the Origin volume. When the merge is complete, the merged snapshot is automatically deleted from the system.

Note Before merging a LUN Snapshot with its Origin, make sure that both the Origin LUN and the Snapshot are closed.

Note When a Snapshot merge is in progress for an Origin LUN, neither manual nor scheduled Snapshots can be created until the merge is complete.



Step 2 Mouse over a LUN snapshot to highlight it and right click.


Step 3 From the right-click menu, choose Merge Snapshot.

The Merge Snapshot confirmation dialog box appears.

Step 4 Choose Merge to complete the Snapshot merge or choose Cancel to return to the LUNs window.

Delete Snapshot

When the maximum number of Snapshots, 10, has been created either manually or automatically via schedule, the oldest Snapshot, identified by the time created, is deleted. However, any Snapshot can be manually deleted.



Step 2 Mouse over a LUN snapshot to highlight it and right click.


Step 3 From the right-click menu, choose Delete.

The Delete Snapshot confirmation dialog box appears.



Step 4 Choose Delete or choose Cancel to return to the LUNs window.

Note You must delete all associated snapshots before a LUN can be deleted.

Check Performance



Step 2 Mouse over a LUN or LUN snapshot to highlight it and right click.


Step 3 From the right-click menu, choose Check Performance.

The LUN Performance Information Monitor appears.

Step 4 Mouse over a performance grid to view detailed information.



• To view weekly performance, click the calendar icon in the top-right-hand corner of the performance graph.

• To view details of a particular time frame, click your mouse and drag it over a lower time-line interval, e.g., 17:25 to 17:50.

Delete LUN

Note If a LUN is part of an asynchronous replication pairing, it cannot be deleted until the pairing is removed. To remove the pairing, go to the Async Replication > Pairings menu (see Chapter 5, “Asynchronous Replication”).

Note You must delete all associated snapshots before a LUN can be deleted.

Tip During the LUN deletion process, GUI performance may be negatively affected until the process completes. The larger the LUN, the more time the process may take. We recommend deleting larger LUNs during off-peak hours.

To perform the LUN deletion:






The right-click menu appears

Step 3 Choose the Delete menu option.A delete confirmation dialog box appears.

Step 4 Click Delete or click Cancel and return to the LUNs list.

View LUN Performance Data

Check boxes adjacent to the LUNs can be used for selecting and viewing the performance of up to the first 5 Selected LUNs. View performance graphs for one of the first 5 LUNs on its tab, or view an aggregate graph from the “All” tab.

The performance view auto-refreshes every 10 seconds and displays point-in-time MB/s and IOPS characteristic information.

To View LUN performance graphs, do the following:



Step 2 Do one of the following:

• Highlight a LUN from the LUNs list by mousing over it and right click.

• Choose up to 5 check boxes adjacent to a LUN name and right click.


Step 3 Choose Check Performance.

The LUN Performance Information Monitor appears.

Step 4 Mouse over a performance grid to view detailed information.



• To view weekly performance, click the calendar icon in the top-right-hand corner of the performance graph.

• To view details of a particular time frame by click your mouse and drag it over a lower time-line interval, e.g., 17:25 to 17:50.

Initiator GroupsInitiator Groups are used to map LUNs. When a LUN is associated with a specific Initiator Group, the LUN is only visible to Initiators in that Group. A triangle adjacent to an Initiator Group name indicates that there are Initiators assigned to them and a tree structure can be expanded or collapsed on click.



Note A LUN may be mapped to multiple Initiator Groups while an Initiator cannot be listed as a member of more than one Initiator Group.

Create an Initiator Group

Step 1 Choose LUN Configuration > Initiator Groups.

The Initiators window appears.

Step 2 Click Create New Group.

Step 3 Enter the name of the Initiator Group in the Name field and click Create Group.

The new Initiator Group name appears on the Initiators list.

Add an Initiator to an Initiator Group



Step 2 Click an Initiator Group to highlight it and right click.

The right-click options menu appears.

Step 3 Choose Add Initiator.

The Add Initiator to <Initiator Group> dialog box appears.

Step 4 Enter in the WWN/IQN and click Create Initiator or click Cancel to return to the Initiators list.

Note Ensure that the WWN for the HBA to which the storage is attached is zoned using the standards used in your data center.

Map a LUN to an Initiator Group

Caution Avoid mapping a LUN until an Initiator has been added to the Initiator Group.





Step 3 Choose Map LUNs.

The Initiator LUN window appears.



Step 4 Do one of the following to map a LUN:

• Drag-and-drop a LUN from the Available LUNs list to the Initiator Group’s LUN list above it.

• Right click a LUN and Choose the Map/Unmap LUN option.

The Map LUN to Initiator Group Dialog Box appears.

Caution Initiators have LUNs mapped starting from Map ID ‘0’. Failure to remap a LUN to Map ID ‘0’ will result in LUN mapping issues.

Caution Deleting Map ID ‘0’ is not recommended. If it is deleted, all other LUNs mapped to this initiator group might be lost from the Initiator sight. Also, while the next LUN mapping created will automatically be assigned the Map ID ‘0’ but it would still not guarantee automatic rediscovery of the “lost” LUNs.

Note If a range of IDs for multiple LUNs is specified, a check for Map ID ‘0’ is first made and then the IDs are assigned starting with the ID provided. If the number provided is already present, the starting Map ID assigned will be incremental.

Note Map IDs from 0-255 are available for UNIX and Linux.

Note Map IDs 0-254 are available for Windows.

Step 5 Click Create or click Cancel to return to the Initiator’s Available LUN list.

The LUN appears in the Initiator’s LUN list.

Step 6 Repeat Steps 4 and 5 for each preferred available LUN.

Note To unmap a LUN, drag-and-drop it from the Initiator Group LUN list back to the Available LUNS list or follow the UnMap procedure in Chapter 4.2.4.

Step 7 Click Back to Initiators to return to the Initiator Groups window.

Unmap LUN from Initiator





Step 3 Choose Map/Unmap LUNs.

The Initiator LUN window appears.




• Choose a LUN from the Initiator’s LUN list, right click and choose the Unmap LUN menu option.

• Drag-and-drop a LUN from the Initiator Groups LUN list to the Initiator Available LUN list below it.

The LUN disappears from the Initiator Group’s LUN list and reappears on the Available LUNs list.

Delete Initiator Group

Note Unmap all LUNs from an Initiator Group before attempting to delete it to avoid data loss.





Step 3 Choose Delete Group.

A delete verification dialog box appears.

Step 4 Click Delete Group or click Cancel to return to the Initiators list.



C H A P T E R


5Asynchronous Replication

• Communicating with a Partner Host, page 5-2

• Create a Pairing, page 5-7

Asynchronous replication (hereafter referred to as Async Replication) is an optional and separately licensed feature. It provides a permission-based mechanism to create a duplicate version of a LUN on a device attached to a partner host.

Cisco uses block-level Async Replication and incorporates an Async snapshot feature to capture a point-in-time state that allows applications to continue writing their data. These features help to prevent damage from failures or disasters that may occur in one location and improves the ability to recover a copy of the data in another location.

Note • LUNs must be 2TB or less to use Async Replication.

• During Async Replication pairing creation, if the source device is a LUN then the target device must also be a LUN.

• Using target entities in Read-Write mode is not recommended as this poses a risk to the accuracy of the data replication and may corrupt data recovery.

• Before you use the Asynchronous (Async) Replication feature, make sure that you do not use the LUN or Snapshot "Snapdiff1_xyz" as the name (where 'xyz' is either the Source or Target, LUN, or Snapshot name) because the user data might get deleted during the replication process.

• During the replication process, the target LUN will be unmapped/unmounted and is therefore inaccessible. This prevents possible corruption of source data. The replication process will automatically re-map and remount at its completion. The source SSR will have access throughout the replication process.

• When available free space on the system falls below a threshold level of 10%, on both the Async Replication Source or Destination, the system automatically deletes the oldest Snapshot(s) on the device to free up at least 15% of space. Neither manual nor scheduled Snapshots can be created until this 15% threshold is met.

• If either the Source or Destination LUN used for Async Replication has a Snapshot merge in progress, neither manual nor scheduled Snapshots can be created until the merge is complete causing Async Replication to fail.


Chapter 5 Asynchronous Replication

• If an Async Replication or Restore is in progress for a given pairing, a LUN Merge operation will not be permitted on a LUN that has either been configured as an Async Source or Destination until the Replication or Restore operation is complete.

• When restoring to the original source LUN, the Restore process will unexport and unmount the LUN and will not be accessible. The Restore process will automatically re-mount and re-export at its completion.

• Once Async Replication pairing is setup, the following operations are prevented on the source LUN used for the pairing:

– Increase in size

– Delete operation

Note The first replication that is performed on a pairing is always a FULL replication. Subsequent replications reflect the delta, except where an “Update Partner” operation is performed. In that case, the immediate next replication would become a FULL replication.

Communicating with a Partner HostTo perform replication successfully, there must be a way for communicating between the local LUN and the remote replication site to establish that the client (local Cisco Array) is allowed to invoke commands on the server (remote replication site).

The Cisco Array uses the standard remote shell facility, ssh, leveraging on password-less access after putting its public key to the proper location at the remote replication site.

For LUNs, Cisco supports open-target Async Replication. It can duplicate to the following platforms:

• Cisco Array

• Linux systems:

– Linux-LVM

– Linux-RAW

• Windows 2008 R2 or later Server editions.



Table 5.1 lists the releases that are supported for LUNS. Instructions for each platform follow:

Table 5-1 Supported Releases

PlatformSupported Releases

Additional Information Examples

Cisco Cisco UCS Invicta OS >= 5.0.0

Destination LUN needs to be a LUN of the same size as the source LUN and they both need to be 2 TB or less.

• Source Device: dk_CiscoPairingSourceLun_143

• Partner Host: 192.168.200.103

• Remote IDF Directory: /var/log/dk_CiscoPairingSourceLun_143

• Target Type: Cisco

• Target Device: /dev/SSN/dk_CiscoPairingDestinationLun

Linux-LVM Kernel version >= 2.6.3

LVM2 version >= 2.02

Destination target needs to be a logical volume of the same size as the source LUN and they both need to be 2 TB or less.

• Source Device: dk_Linuxlvm_src

• Partner Host:192.168.200.119

• Remote IDF Directory: /var/log/dk_Linuxlvm_src

• Target Type: Linux-LVM

• Target Device:/dev/SSNdk_Linuxlvm_tgt

Linux-RAW Kernel version >= 2.6.3

Destination block device needs to be the same size as the source LUN and they both need to be 2 TB or less.

• Source Device: dk_LUN_LinuxRaw

• Partner Host:192.168.200.118

• Remote IDF Directory: /var/log/dk_Linuxraw_src

• Target Type: Linux-Raw

• Target Device:/dev/SSNdk_Linux_tgt

Windows Windows 2008 R2 or later Server editions

Duplicates directly to a file.

Note This pairing type is not designed for large size or Replication

• Source Device: dk_Win_143

• Partner Host: 192.168,200.103

• Remote IDF Directory: c:\dk_temp\dk_win_143

• Target Type: Windows

• Target Device: c:\dk_win_luns\dk.txt



Note When using Async Replication for Non-Cisco Pairing types (i.e., Windows, Linux-LVM, and Linux-Raw), the mounting the Destination LUN any initiator for the purposes of viewing the data is not supported. The ability to mount the Destination LUN is supported only when a Cisco-partner type is used and the Destination entity resides on a Cisco UCS Invicta Appliance or Cisco UCS Invicta Scaling System.

Note The Target device the format is /dev/<VG name>/<destination entity>.

Cisco to Cisco

Cisco-to-Cisco Async Replication is preconfigured and is complete. To create a pairing, see Create a Pairing, page 5-7.

Cisco to Linux-LVM

Step 1 Click Public Key to obtain the public key necessary for using password-less ssh access.

The SSH Public Key dialog box appears.

Step 2 Copy the ssh key and click OK.

Step 3 Open a Terminal window and navigate to the /root/.ssh directory.

Step 4 Enter vi authorized_keys.

Step 5 Paste the Cisco Public Key copied in Step 2 into the authorized_keys list and click Enter.

See the following sample procedure to configure a Linux Host to be used as a Linux ‘Open Target’ partner for Async Replication.

Sample Procedure:

Note This example uses CentOS 6.2

You need the following:

• LVM 2.0.2: yum –y install lvm2

• Install Openssh server and clients: yum -y install openssh-server openssh-clients

• Add and start sshd service daemon:

– chkconfig sshd on

– service sshd start

• If you need Multipath support for future use, configure /etc/multipath.conf file on your storage device (from the other storage vendor) as your target LUN.

5a. Make sure public key is there in the ~/.ssh folder:



• $ cd ~

• $ chmod 755 .ssh

• $ chmod 600 ~/.ssh/authorized_keys

• (Do a cat authorized_keys and make sure the public key is copied there)

• $ exec /usr/bin/ssh-agent $SHELL

• $ ssh-add

5b. As the Linux root user, type the following command to relabel all the files under the correct security context for SELinux:

restorecon -Rv /root/.ssh

(These should allow the Cisco array to communicate with the Linux host via password-less ssh)

5c. Get your target LV device ready by using LVM2 tools.

With a multipath setup mapped, the target storage array from the other vendor is mapped as:

/dev/mapper/26439363962386365

5d. Setup the LV using the following commands

• pvcreate /dev/mapper/26439363962386365 vgcreate VG1 /dev/mapper/26439363962386365

• lvcreate -L 90G -n async_lun VG1

• vgchange -a y

• (lvdisplay should now show the LV created as active)

You are now ready to use the LV you created as your Async Target device.

Step 6 Close the session on the remote replication site.

Step 7 Return to the Async Replication window to create a pairing (see Create a Pairing, page 5-7).

Cisco to Linux-RAW




Step 3 Open a Terminal window and navigate to the /root/.ssh directory.



See the following sample procedure to configure a Linux Host to be used as a Linux ‘Open Target’ partner for Async Replication.

Sample Procedure:



Note This example uses CentOS 6.2

You need the following:

• Install Openssh server and clients: yum -y install openssh-server openssh-clients

• Add and start sshd service daemon:

– chkconfig sshd on

– service sshd start

• If you need Multipath support for future use, configure /etc/multipath.conf file on your storage device (from the other storage vendor) as your target LUN.

5a. Make sure public key is there in the ~/.ssh folder:

• $ cd ~

• $ chmod 755 .ssh

• $ chmod 600 ~/.ssh/authorized_keys

• (Do a cat authorized_keys and make sure the public key is copied there)

• $ exec /usr/bin/ssh-agent $SHELL

• $ ssh-add

5b. As the Linux root user, type the following command to relabel all the files under the correct security context for SELinux:

restorecon -Rv /root/.ssh

(These should allow the Cisco array to communicate with the Linux host via password-less ssh)

Step 6 Close the session on the remote replication site.

Return to the Async Replication window to create a pairing (see Create a Pairing, page 5-7).

Cisco to Windows

Note The Windows Server firewall must be turned off before Async Replication can be set up.

Cisco-to-Windows Async Replication requires that Cygwin along with two services, sshd and cyg_server, are installed on the target Windows machine. An automated method for downloading this software is provided on the Async Replication window.

To install the Windows software package and to configure for the Async Replication to run, do the following:

Step 1 Login to the Windows 2008 R2 Server machine as Administrator and open a browser to go to Cisco page.

Step 2 Choose Async Replication > Pairings.

The Async Replication window appears.



Step 3 Click Windows Installer.

Note This step is to be used if Cygwin packages and services (sshd and cyg_server) are not already installed on the Windows Partner Host. If the Cygwin packages and services are already installed, skip to Step 4.

The software package is downloaded and executed. If your browser downloads the software but does not run automatically, click Run to install. The Cygwin packages will be downloaded from the Redhat website and installed. The services required for Async Replication will be configured and started.

This setup will take several minutes.




Step 6 Open a Terminal window and navigate to the /home/Administrator/.ssh directory.



Step 9 Close session on remote replication site.

Step 10 Return to the Async Replication window to create a pairing (Create a Pairing, page 5-7, ).

For additional information on how to run ssh-keygen and setup public keys for both Linux and Windows, see http://rcsg-gsir.imsb-dsgi.nrc-cnrc.gc.ca/documents/internet/node31.html and http://www.noah.org/ssh/cygwin-sshd.html.

Create a Pairing

Note A LUN must be present before a pairing can be created.

Caution It is not recommended to use target entities in Read-Write mode as this poses a risk to the accuracy of the data replication and may corrupt data recovery.Once Async Replication pairing is setup, the following operations are prevented on the Source LUN used for the pairing:

-Increase in size, -Delete operation

The Async Replication Pairings window displays a table of LUNs and their host pairings. Information about and the date and time of the last replication and the last restore is also displayed. From this window, create new pairings using the top left-hand window button. On mouse hover over each pairing, the replication schedule, and the source and target device info for that pairing appears in a pop-up box.

On right-click, an options menu appears for the selected pairing for the following:

• Delete

• Verify Partner Host



• Update Partner

• Schedule

• Restore

• View Log File

If a host and/or device is/are not detected when checked, the respective fields turn red. The following triggers checks:

• Async Replication window refresh

• New Host Pairing creation

• Pairing Deletion

• Pairing Host Update (check is performed on specific update entry)

• Manual replication scheduling

• Replication Termination

Additionally, the LUN column is green for replication in progress and tan when a restore is in progress.

To create an Async Pairing, do the following:


The Pairings window appears.

Step 2 Click Create New Pairing.

The Pairing Definition dialog box appears.

Step 3 Complete the Pairing Definition fields. (See Table 6.3 for field descriptions.)

Step 4 Click Create Pairing to create pairing or click Cancel to return to Async Replication window.

Table 5-2 Pairing Definition Fields

Pairing Definition Field Description

LUN Choose LUN for pairing.

Partner Host The IP address of the target server used for the replication.

Remote IDF Directory The directory on replication destination side for storing Intermediate Data Files (IDF).

Note It is important that this directory is non-volatile for rebooting.

Target Type Choose from the drop-down list.

• The target platform to which the replication is sent. Defaults to Cisco and is intended for use exclusively with Cisco storage arrays.

• Linux-LVM, Linux-RAW, and Windows are the other selections.

Target Device The device for storing the replication.

Note When replicating to a file, be sure to include the extension at the end of the file name.



Note All listed pairings are verified when a new pairing is created. If a Partner Host cannot be verified, the field displays in red.

Delete Async Replication Pairing

To delete an Async Replication pairing, do the following:



Step 2 Mouse over an Async Replication pairing to highlight it and right click.


Step 3 Choose Delete.

The Delete Async Replication Pair confirmation dialog box appears.

Step 4 Click Delete to delete the pairing and remove it from the list or click Cancel to return to the Async Replication window.

Verify Partner Host





Step 3 Choose Verify Partner.

The Partner Host Column displays a “checking” indicator.

• If the verification fails, the associated Partner Host field turns red.

• If the Target Device does not exist, that field will turn red.

Update Partner Host

Note A pairing should not be updated while an Async Replication or a Restore is in progress.

To update an existing Partner Host, do the following:







Step 3 Choose Update.

The Update Partner Host dialog box appears.

Step 4 Update the field or fields, as necessary.

Step 5 Click Update to update the pairing or click Cancel to return to the Async Replication window.

Note When updating a partner host, a full replication is triggered.

Async Replication Scheduling

Note During the occurrence of each scheduled replication the target LUN will be unmapped/dismounted and, therefore inaccessible.

Note During the replication process, the source LUN will be unmapped/unmounted on the peer SSR and is therefore inaccessible from the peer SSR. This prevents possible corruption of source data. The replication process will automatically re-map and re-mount.

The Async Replication function can be set at scheduled intervals or may be triggered for immediate replication.

To schedule an Async Replication, do the following:





Step 3 Choose Schedule.

The Replication Schedule Setup dialog box appears.

Step 4 Complete the fields as described in Table 6.4.

• Threads

• Init Block Size (MB)

Step 5 Do one or both of the following:

Note Entries with “occurs every” interval set to “off” on the drop-down list are ignored.

• Click Run Now to manually trigger an Async Replication.

• Click New Schedule Entry one or more times to schedule one-time or recurring Async Replications.



– Enter the replication start time (24-hour clock) or use the Hour and Minute slide bar to choose a time.

– Choose a time interval, day of the week or calendar date from the Occurs Every drop-down list.

Step 6 Click Delete for any scheduled entry you want to remove.

Note The choices for Thread and Init Block Size stay constant for any Async Replication that is scheduled for this LUN Pairing.

Step 7 Click Save Schedule or click Cancel to return to the Pairings window.

Restore

After replicating a LUN to a remote target device, the restore function can replicate the data copy back to the source LUN (in-place) or, if needed, can send the copy to a new LUN (out-of-place).

To Restore a Replication do the following:





Step 3 Choose Restore.

The Restore box appears for the LUN selected.

Step 4 Complete the Restore fields appropriate to the restore the selection (see Table 5.4) using the drop-down lists or typing (Name field).

Table 5-3 Schedule Replication Fields

Field Description

Threads Multiprocessing capability. The higher the thread numbers the higher the throughput but the greater the impact on system processing. The default is 2.

Tip Use the default (2) for peak computing hours. Use higher thread for off-peak computing hours.

Init Block Size (MB) Initial transmission block size only. This parameter is used for the initial replication for a device, (including if the initial replication is manually triggered). Subsequent delta replications for the device always use a 1Mb block size.



Click Restore or click Cancel to return to the Async Replication window.

View Log File

To view replication and restoration log files, do the following:


The Pairing window appears.



Step 3 Choose View Log File.

The Replication/Restoration Activity dialog box appears.


• Click Clear to clean the log for that specific pairing.

A confirmation dialog box appears.

• Click OK to close the dialog box or click Cancel to return to the log.

Table 5-4 Restore Selection Options

Source: Threads

New • LUN Name

• Volume Group

• Threads

C H A P T E R


6

Users

• Create a New User Account, page 6-1

• Assign or Unassign User Role, page 6-1

• Delete User Account, page 6-2

• Edit User Account, page 6-2

• Create or Modify a Role, page 6-3

• Delete a Role, page 6-4

• Change Password, page 6-4

The Users Menu allows any user to change passwords and permissioned-sanctioned users to add user accounts, create and assign roles.

Create a New User Account

Step 1 Click Users > User Accounts.

The User Accounts window appears.

Step 2 Click Create New User.

The Create New User dialog box appears.

Step 3 Complete the fields of the Create New User dialog box and click Create User.

The User Account Name that was input appears on the User Accounts list.

Assign or Unassign User RoleRoles are created with specific permission sets that are configurable from the Roles window. Without permission-defined roles, the default permission for a User Account is the ability to view the Home Menu, Main Dashboard and the ability to change a password from the User Menu.


Chapter 6 Users

The Role of Enterprise Administrator would likely be assigned permissions to access and perform all actions on all windows.

To assign a role to a user account, do the following:



Step 2 Right-click a User Account.


Step 3 Choose Assign Role.

The Roles window appears with the account name at the top.

Step 4 Assign a role(s) for this user account using the drag-and-drop functionality from the Unassigned Roles column to the Assigned Roles column or vice-versa to Unassign user role.

Delete User AccountTo delete a user account, do the following:



Step 2 Choose a User Account and right-click.


Step 3 Choose Delete.

The Delete User confirmation box appears.

Step 4 Click Yes to delete the user account or Cancel to return to User Accounts window.

Edit User AccountTo edit a user account, do the following:



Step 2 Choose a User Account and right-click.


Step 3 Choose Edit.

The Edit User dialog box appears.

Step 4 Complete necessary changes to fields.


Chapter 6 Users

Step 5 Click Save User or click Cancel to return to User Accounts window.

Create or Modify a RoleA Role is required for each User. Roles are a descriptive name given to a predefined set of permissions that are assigned using the Roles Menu.

Caution If you are logged in at a time when one of your assigned roles has been changed, you need to log out and then log back in to be granted permission for the modified role.

To create a role, do the following:

Step 1 Click Users > Roles.

The Role window appears.


• Choose a role from the already defined role drop-down list.

The Assigned/Unassigned Permission window appears.

• Click Create Role to create a new role.

The Create New Role dialog box appears.

– Input name for new role.

– Click Create or click Cancel to return to the Roles window.

Step 3 Assign, Unassign or modify permissions for a role using the drag-and-drop functionality to or from the Unassigned Permissions and the Assigned Permissions columns.

Note Assign and/or unassign permissions to a role by selecting the check box adjacent to one or more entries in the Assign/Unassign Permission columns.

Note The permission to access and view a window, does not automatically give permission to actions available on that page. Conversely, if permission is granted to perform an action, permission to the window where that function is located must also be granted.

For example, LUNs window access must be permissioned along with a LUN action, for example, LUNs Edit action.


Chapter 6 Users

Delete a RoleTo delete a role:

Step 1 Click Users > Roles.

The Roles window appears.

Step 2 Choose a role from the drop-down list at the top left-hand side.

Step 3 Click Delete Role.

The Delete Current Role confirmation dialog box appears.

Step 4 Click Yes to delete the role or Cancel to return to the Roles window.

Change Password

Tip The Administrator/User should only use the default password for the initial configuration or initial log in. A unique Login ID is needed so that the audit trail reflects a unique user. “Admin” if unchanged will not distinguish between those logged using that default nameTo change passwords:

Step 1 Choose Users > Change Password.

The Change Password window appears.

Step 2 Complete the fields and click Change Password.

Documents

Cisco UCS Invicta C3124SA Appliance Administration and ... · Drive Wear Monitor 2-2 Drive Tasks 2-2 Removing a Drive 2-3 Performance MB/s, IOPS, Latency, and Utilization Monitors