Cisco UCS Invicta Scaling System
Administration Guide
Version 5.0.1.1a
March 11, 2015
Cisco Systems, Inc.
www.cisco.com
Cisco has more than 200 offices worldwide.
Addresses, phone numbers, and fax numbers
are listed on the Cisco website at
www.cisco.com/go/offices.
Text Part Number:
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, Flip
Mino, 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; and
Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco 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, the
IronPort 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 are
registered 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.
CONTENTS
Preface
v
Organization
v
Conventions
v
CHAPTER
1
Overview 1-1
Prerequisite Tasks 1-1
Cisco UCS Invicta Scaling System Interface Overview 1-1
Licensed Features 1-8
Initial Steps 1-8
Logging into the Cisco UCS Invicta Scaling System 1-8
Document Roadmap 1-10
CHAPTER
2
Home
2-1
Main Dashboard 2-1
Overview Tab 2-2
Node RAID Health 2-2
Node Status 2-3
Drive Wear Monitor 2-3
Drive Tasks 2-3
Removing a Drive 2-4
Performance MB/s, IOPS, Latency, and Utilization Monitors
Detail Tab 2-5
Administration Guide 2-5
Installation Guide 2-5
CHAPTER
3
2-4
SSR Configuration 3-1
Network Settings 3-1
Heartbeat bondHB 3-2
Creating a New Bond 3-2
Default Gateway 3-3
DNS Nameservers 3-4
Static Routes 3-4
Edit Bond 3-5
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
i
Contents
Delete Bond 3-5
Enable/Disable Bond 3-6
Enable/Disable Fibre Channel Interface 3-6
Create a Virtual Interface 3-6
Create a VLAN 3-7
Configure Devices 3-8
Check Performance 3-8
MPIO Settings 3-8
Volume Group and Node Settings 3-9
Physical Space (Data Reduction) 3-9
Storage Trend (Data Reduction) 3-9
Physical Space Alerts 3-10
iSCSI Settings 3-10
Changing Initiator IP Address Availability 3-10
Error Correction 3-11
Support Settings 3-11
Support Setting Configuration 3-11
System Update 3-13
Uninstall Update 3-14
Shutdown 3-14
Reboot 3-14
Alert Admin 3-14
Address Alert 3-14
CHAPTER
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-4
Merge Snapshot 4-5
Delete Snapshot 4-5
Check Performance 4-6
Delete LUN 4-7
LUN Mirror 4-7
View LUN Performance Data 4-10
Initiator Groups 4-10
Create an Initiator Group 4-11
Add an Initiator to an Initiator Group 4-11
Map a LUN to an Initiator Group 4-11
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
ii
Contents
Unmap LUN from Initiator 4-12
Delete Initiator Group 4-13
CHAPTER
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
Update Partner Host 5-9
Async Replication Scheduling 5-10
Restore 5-11
View Log File 5-12
CHAPTER
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
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
iii
Contents
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
iv
Preface
This guide includes information about the Cisco Unified Computing System (Cisco UCS) Invicta
Scaling System for both performance and data reduction silicon storage systems.
Information applies to both types of systems unless otherwise noted. Unique content is identified within
the text.
Organization
This guide includes the following sections:
Chapter
Title
Description
1
Overview
Describes prerequisite and initial configuration
information.
2
Home
Describes the GUI Home tab including the Main
Dashboard and drive tasks.
3
SSR Configuration
Describes topics related to configuration,
including network, MPIO, and VG settings.
4
LUN Configuration
Describes LUN configuration tasks and includes
information on snapshots.
5
Asynchronous Replication
Describes how to create a duplicate version of a
LUN on a device attached to a partner host.
6
Users
Describes how to perform user-related tasks, such
as creating, editing, modifying, or deleting user
accounts and creating, deleting, or modifying user
roles.
Conventions
This document uses the following conventions:
Convention
Indication
bold font
Commands and keywords and user-entered text appear in bold font.
italic font
Document titles, new or emphasized terms, and arguments for which you supply
values are in italic font.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
v
[ ]
Elements in square brackets are optional.
{x | y | z }
Required alternative keywords are grouped in braces and separated by
vertical bars.
[x|y|z]
Optional alternative keywords are grouped in brackets and separated by
vertical bars.
string
A nonquoted set of characters. Do not use quotation marks around the string or
the string will include the quotation marks.
courier
font
Terminal sessions and information the system displays appear in courier font.
< >
Nonprinting characters such as passwords are in angle brackets.
[ ]
Default responses to system prompts are in square brackets.
!, #
An exclamation point (!) or a pound sign (#) at the beginning of a line of code
indicates a comment line.
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
manual.
Caution
Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.
Warning
IMPORTANT SAFETY INSTRUCTIONS
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you
work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar
with standard practices for preventing accidents. Use the statement number provided at the end of
each warning to locate its translation in the translated safety warnings that accompanied this device.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
vi
CH A P T E R
1
Overview
•
Prerequisite Tasks, page 1-1
•
Cisco UCS Invicta Scaling System 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
Scaling System for both performance and data reduction silicon storage systems.
Information applies to both types of systems unless otherwise noted. Unique content is identified within
the content.
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 Scaling System Management GUI is
available.
•
The Cisco UCS Invicta Management GUI recognizes the Solid State Routers (SSRs) and Solid State
Nodes (SSNs).
If you are unable to perform these tasks, contact Cisco Technical Support.
Cisco UCS Invicta Scaling System Interface Overview
The Cisco UCS Invicta Scaling System is a multi-system, high-performance, flash-based silicon storage
system.
The basic architecture consists of (Table 1-1):
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
OL-31372-01
1-1
Chapter 1
Table 1-1
Overview
Basic Scaling System Architecture
Component
Description
Silicon Storage Router (SSR)
Routes traffic to different SSNs and provides the
host with a unified storage system view.
Cisco UCS Invicta Scaling System supports two
SSRs
Silicon Storage Node (SSN)
Storage nodes of either 3,6,12, or 24TB in density.
Cisco UCS Invicta Scaling System supports up to
6 SSNs.
Table 1-2 provides a list of the Cisco UCS Invicta Scaling System GUI menu with an overview of each
menu window and the task that can be performed from them.
Table 1-2
GUI Menu
Menu Tab
Menu
Overview
Home
Main Dashboard
Displays health, wear, performance,
utilization, and node status views.
Administration
Guide
•
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 system
wear indicator
•
View Node
Status to check if
the node has Data
Reduction
capability
Links to a PDF.
—
Installation Guide Links to a PDF.
—
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-2
Tasks
Chapter 1
Overview
Table 1-2
GUI Menu (continued)
Menu Tab
Menu
Overview
SSR
Configuration
Network Settings
Displays network configuration
information including network interfaces
(individual and bonds) and Fibre Channel
interfaces.
Permission-based.
MPIO Settings
Displays the local and peer host names.
Allows for one SSR to recognize another
SSR.
Tasks
•
Change a device
configuration
•
Set a Default
Gateway
•
Set the DNS
server
•
Set Static Routes
•
Change the
network link for
the local and peer
host
•
Synchronize peer
SCST with the
local SCST
•
View the Volume
Groups
•
Create a LUN for
a Volume Group
•
Delete a Volume
Group
•
View Physical
Space (Data
Reduction)
•
View Storage
Trend (Data
Reduction)
•
View Volume
Group utilization
individual
Volume Group or
as an aggregate.
•
View Storage
Permission-based.
VG Node Settings Displays each Volume Group as one
contiguous, addressable region.
An SSN can be a stand-alone Volume
Group, i.e., there cannot be less than one
Volume Group on one SSN. However, a
Volume Group can be combined with up
to a maximum of six SSNs to form
Volume Groups.
Volume Groups cannot be created by
combining multiple Data Reduction
SSNs or by combining Data Reduction
SSN and Performance SSNs.
Right-click menu provides menu option
to create a LUN and delete a VG. Cisco
UCS Invicta Scaling Systems with Data
Reduction can also display the physical
space and storage trend from the
right-click menu.
Lists IP addresses that are available and
to which a host is allowed to connect.
Permission-based.
iSCSI Settings
Lists IP addresses that are available and
which a host is allowed to connect.
Permission-based.
Error Correction
Provides an option to reconstruct or to
rebuild the data block content using
parity.
Move IP addresses
between the
Available and
Allowed Portal
Columns
Turn on or off
Permission-based.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-3
Chapter 1
Table 1-2
Menu Tab
GUI Menu (continued)
Menu
Overview
Tasks
Support Settings
Contains configuration data including:
View:
•
Host name, mail server and user
(SMTP), and time server (NTP).
•
Cisco UCS Invicta
OS Version
•
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).
•
Complete
configuration
information
fields
•
Shutdown
•
Reboot
•
Test Auto
Support
•
Post Service
•
Perform System
Update
•
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-4
Overview
Chapter 1
Overview
Table 1-2
Menu Tab
GUI Menu (continued)
Menu
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
Scaling System. 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.
Tasks
Permission-based.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-5
Chapter 1
Table 1-2
Menu Tab
Overview
GUI Menu (continued)
Menu
Overview
Tasks
Alert Admin
Icon on the Main Dashboard indicates the Check and/or set an
alert status to
number of alerts present.
Resolved or Suppress
Alert Admin window lists short
identification and notification
timestamps of all active alerts sent during
periodic system checks.
Permission-based.
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.
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-6
•
Create LUNs
•
Increase LUN
Size
•
Create Snapshot
•
Schedule
Snapshot
•
Delete LUNs
•
Mirror/Break
Mirror LUNS
•
Check
Performance
•
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
Table 1-2
GUI Menu (continued)
Menu Tab
Menu
Overview
Async
Replication
Pairings
LUN-to-target pairing allows
management and replication scheduling.
•
Create a New
Pairing
License- and permission-based.
•
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
•
Create a New
User Account
•
Assign User
Roles
•
Edit or Delete a
User Account
Users
User Accounts
Requires that each user must have a user
account and must be assigned one or
more roles.
Tasks
Permission-based.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-7
Chapter 1
Table 1-2
Menu Tab
Overview
GUI Menu (continued)
Menu
Overview
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.
Tasks
•
Create or Delete
a Role
•
Assign or
Unassign
permissions to a
Role
•
Change User
Password
Permission-based.
Change Password
Changes the default or compromised
passwords to protect the accuracy of
audit trails. A password change is
required after the initial login.
Licensed Features
Cisco 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 Steps
Initial steps for administering and configuring the Cisco UCS Invicta Scaling System 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 Cisco UCS Invicta Scaling System
Step 1
Power on the SSNs first and wait approximately 5-8 minutes before powering on the SSRs.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-8
Chapter 1
Overview
Note
The power supply LED is amber 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
Perform login using the new user account ID.
The Cisco Installation team will have configured the Cisco UCS Invicta Scaling System. 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, “Network Configuration.”
Verify/Modify Network Configuration. To navigate to Support settings, do the following:
Step 1
Select Array Configuration > Support Settings.
The Support Settings window appears.
Review current field information and modify as necessary (for more information see, “Chapter 3, “SSR
Configuration”).
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-9
Chapter 1
Overview
Document Roadmap
The remaining sections of this document provide information on each Cisco UCS Invicta Scaling System
menu item and the tasks associated with them (see Table 1-2 on page 1-2).
Figure 1-1
Cisco UCS Invicta Scaling System Device Rear Panel Features
1
2
3
PCIe 1
PCIe 5
PCIe 2
PCIe 4
PCIe 3
PSU2
4
5
6
7
9
10 11
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 lane
PCIe 2—full-height, half-length, x16 lane
PCIe 3—full-height, half-length, x8 lane
5
Serial port (RJ-45 connector)
11 Rear Identification button/LED
6
USB port
–
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
1-10
8
331826
PSU1
CH A P T E R
2
Home
This section describes the GUI Home menu which is made up of the following sub-menu items:
•
Main Dashboard, page 2-1
•
Drive Tasks, page 2-3
•
Administration Guide, page 2-5
•
Installation Guide, page 2-5
Main Dashboard
The Main Dashboard displays important general information, as well health and performance
information. It includes:
•
Device Type
•
Name of the current SSR (to which you are logged in)
•
Online Help icon
•
Alerts icon.
The Alerts icon is displayed in the top right corner together with the number of new alerts on the
device. When clicked, a window appears with a list of device alerts.
There are two tabs:
Note
•
Overview (default)
•
Detail
If you are using a version of Internet Explorer on a Windows 98 server or above, Internet security settings
may not allow the user interface (UI) to display correctly. To see the GUI properly, perform the following
steps:
Step 1
Choose Internet Options from the IE Tools menu, and then click the Security tab.
Step 2
Choose the Internet zone.
Step 3
Click Custom Level.
Step 4
Scroll to Scripting >Active Scripting and choose Enable.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
2-1
Chapter 2
Home
Main Dashboard
Step 5
Click OK and Apply.
Step 6
To run the scripts, click Refresh.
Overview Tab
The Overview tab is a graphical representation of the SSRs, SSNs, in the Cisco UCS Invicta Scaling
System. It shows how the devices are physically connected and uses color coding to reflect health status.
It displays:
•
Note
SSR. The SSR into which you are logged-in is represented.
The SSR stack is for current SSR identification only. You cannot switch to another SSR without logging
into it.
•
SSNs. The SSNs are displayed in a scrolling carousel. You can click an SSN to view Performance
MB/s, IOPS and Latency monitors and an system wear indicator.
You can also perform various drive operations which are described in this chapter.
Node 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
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
2-2
OL-31372-01
Chapter 2
Home
Main Dashboard
Figure 2-2
Drive Status Legend
Node Status
This area conveys whether or not the Cisco UCS Invicta Scaling System 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 Tasks
To 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.
•
Caution
Choose Fail to fail a drive, if necessary.
The fail right-click menu option on a RAID 5 is only visible on the RAID set that houses the spare. When
a fail is initiated, recovery to a spare is triggered.
– 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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
OL-31372-01
2-3
Chapter 2
Home
Main Dashboard
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.
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:
Caution
•
Get drive information
•
Enable/Disable Blink On
•
Assign drive to a RAID set
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 system, if necessary.
Performance MB/s, IOPS, Latency, and Utilization Monitors
Note
Cisco UCS Invicta Scaling System 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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
2-4
OL-31372-01
Chapter 2
Home
Main Dashboard
•
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.
Detail Tab
The Detail tab provides the ability to monitor all of the devices in your Cisco UCS Invicta Scaling
System.
Administration Guide
The Administration Guide is accessible from the Home menu item that links to a PDF of this document.
Installation Guide
Installation Guide is accessible from the Home menu item that links to a PDF of this document.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
OL-31372-01
2-5
Chapter 2
Home
Main Dashboard
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
2-6
OL-31372-01
CH A P T E R
3
SSR Configuration
This section covers topics related to the Cisco UCS Invicta Scaling System SSR configuration:
•
Network Settings, page 3-1
•
Default Gateway, page 3-3
•
MPIO Settings, page 3-8
•
Volume Group and Node Settings, page 3-9
•
iSCSI Settings, page 3-10
•
Error Correction, page 3-11
•
Support Settings, page 3-11
•
System Update, page 3-13
•
Uninstall Update, page 3-14
Network Settings
Caution
Modifying network settings will cause a brief interruption of connectivity to the Cisco UCS Invicta
Scaling System. 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 Cisco UCS Invicta Scaling System. 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 Cisco UCS Invicta Scaling System
connection.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-1
Chapter 3
SSR Configuration
Heartbeat bondHB
The heartbeat bond is a monitoring mechanism that ensures both SSRs can communicate with each other
in the event of a single point of communication failure. On both SSRs, eth1 and eth2 interfaces need to
be available so that they can be used to create this network bond.
Note
eth1 and eth2 ports on both SSRs will not be visible/available on the GUI under the Network Settings.
Upon uninstall of the v5.0.1.3 WSP, the bondHB will be visible in the GUI on both SSRs. Do not edit or
delete the bondhb from any of the SSRs. Please contact Cisco Technical Support.
Creating a New Bond
To create a new bond, do the following:
Step 1
Choose SSR Configuration > Network Settings.
The Network Setting window appears.
Step 2
Click Create Bond.
The Create New Bond dialog box appears.
Step 3
Note
Step 4
Complete the fields:
•
IP Address - if verified, a check mark appears
•
Subnet Mask - if verified, a check mark appears
•
MTU
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-1 in Available Bonding Modes.
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-2
Chapter 3
SSR Configuration
Table 3-1
Bonding Modes
MODE NAME
DESCRIPTION
mode=0
Round-robin policy:
Transmit packets in
sequential order from the
first available slave
through the last. This
mode provides load
balancing and fault
tolerance.
(balance-rr)
ADDITIONAL INFORMATION
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.
mode=4
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:
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.
(802.3ad)
Link Aggregation
Control Protocol
(LACP)
mode=6
(balance-alb) [Default
setting on Cisco UCS
Invicta Scaling
Systems]
•
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.
Default Gateway
The default gateway is the device that connects the local network to another network.
To update the default gateway, do the following:
Step 1
Choose SSR Configuration > Network Settings.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-3
Chapter 3
SSR Configuration
The Network Setting window appears.
Step 2
Click Default Gateway.
The Update Default Gateway dialog box appears.
Step 3
Enter the Gateway IP address.
A check mark appears if the gateway is valid.
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:
Step 1
Choose SSR Configuration > Network Settings.
The Network Setting window appears.
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 1
Choose SSR Configuration > Network Settings.
The Network Setting window appears.
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 1
Choose SSR Configuration > Network Settings.
The Network Setting window appears.
Step 2
Click Static Routes > Add Static Route.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-4
Chapter 3
SSR Configuration
The Create New Static Route dialog box appears.
Step 3
Complete the fields:
•
Network
•
Mask
•
Gateway - if the gateway is 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
Step 1
Changing bond0 can potentially sever the scaling system connection.
Choose SSR Configuration > Network Settings.
The Network Setting window appears.
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
Step 1
The option to delete bond0 has been prevented as that could potentially sever the Cisco UCS Invicta
Scaling System connection.
Choose SSR Configuration > Network Settings.
The Network Settings window appears.
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 Delete Bond.
The Delete Bond confirmation dialog box appears.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-5
Chapter 3
Step 4
SSR Configuration
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 SSR Configuration > Network Settings.
The Network Settings window appears.
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 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 1
Choose SSR Configuration > Network Settings.
The Network Settings window appears.
Step 2
Highlight a Port from the FC Interface Status list by mousing over it and right click.
The right-click menu appears.
Step 3
Choose Enable/Disable.
The confirmation dialog box appears, for example, the Set Offline confirmation.
Note
Step 4
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.
Choose Online/Offline or choose 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 1
Choose SSR Configuration > Network Settings.
The Network Settings window appears.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-6
Chapter 3
SSR Configuration
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 Create Virtual.
The Create New Virtual dialog box appears.
Step 4
Note
Complete the fields:
•
IP Address - if the IP address is verified, a check mark appears
•
Subnet Mask
•
MTU
For most implementations, the MTU is <1500>; however, use <9000> if Jumbo Frames are required for
assignment to this bond.
•
Step 5
Onboot - Yes/No. Informs the OS if this bond is to come online during the boot process
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 1
Choose SSR Configuration > Network Settings.
The Network Settings window appears.
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 Create VLAN.
The Create New VLAN dialog box appears.
Step 4
Note
Complete the fields:
•
VLAN ID - Identification of the VLAN used by the standard 802.1Q.
•
IP Address - if the IP address is verified, a check mark appears
•
Subnet Mask
•
MTU
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-7
Chapter 3
Step 5
SSR Configuration
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
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 1
Choose SSR Configuration > Network Settings.
The Network Settings window appears.
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 Check Performance.
The Bond Performance Monitor appears. The legend definitions are displayed in Table 3-2.
Table 3-2
Bond Performance Legend
Packets Definition
Step 4
Rxpck
Number of received packets
Txpck
Number of transmitted packets
RxkB
Reception bandwidth in KB
TxkB
Transmission bandwidth in KB
Mouse over graph to see specific point-in-time information.
MPIO Settings
Displays the ID, host names and IQNs for each SSR.
To view the Host Name or IQN, choose SSR Configuration > MPIO Settings.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-8
Chapter 3
SSR Configuration
Volume Group and Node Settings
In Scaling System terminology, a Volume Group (VG) is the logical storage. VG are presented to the
system as one large storage unit. This section provides information on creating, deleting and
provisioning VG storage.
To access the Volume Groups/Node Setting window, do the following:
Step 1
Choose SSR Configuration > VG/Node Settings.
The VG/Node Settings window appears.
•
A performance graph at the bottom of the VG/Node Screen displays the logical space utilization of
each VG.
•
The ALL tab displays an aggregate logical space utilization of the Volume Groups.
Important Volume Group characteristics include:
•
Several performance-type SSNs (physical storage) can be combined to form a VG.
•
Multiple Data Reduction SSNs cannot be used to create a VG.
•
Each Data Reduction SSN should be created as a VG.
•
Combining a Data Reduction and a performance SSN to form a VG is not permitted.
The Volume Group configuration that is optimal depends on the node performance type, business/BCP/
needs and requirements.
Note
Only those who were assigned roles with the associated permissions can view and/or access these tasks.
The Volume Group/Node Settings right-click menu provides an option to create a LUN and to delete a
Volume Group. In addition, Cisco UCS Invicta Scaling System SSNs with Data Reduction also displays
the physical space and storage trend.
Physical Space (Data Reduction)
When the Physical Space option is selected from the right-click menu, the following information is
provided:
Caution
•
Total Size
•
Available Free Space
•
Data Reduction Savings
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 system is fully saturated. Trends are based on data captured daily on the amount of storage
remaining.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-9
Chapter 3
SSR Configuration
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-3. These messages can be viewed from the SSR 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 14.
Table 3-3
Capacity Alerts
Percent Full Frequency Sent
70
Once
80
Once
85
Once per hour
iSCSI Settings
The iSCSI Screen Lists the IP addresses by which an Initiator (a host) is allowed to access the Cisco
UCS Invicta Scaling System SSR.The two columns represented in 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.
Changing Initiator IP Address Availability
Step 1
Choose SSR Configuration > iSCSI Settings.
The iSCSI Information window appears.
Step 2
Note
Use the drag-and-drop functionality to move an Initiator to or from the Available and the Allowed Portal
IP addresses columns.
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
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-10
Chapter 3
SSR Configuration
Error Correction
The 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 SSR Configuration > Error Correction.
Support Settings
The Cisco Installation Team will have configured Cisco UCS Invicta Scaling System 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 in 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 SSR Configuration > Support Settings.
The Support Settings window appears.
Step 2
Complete or modify field information as necessary. See Table 3-4, for a description of the Support
Settings fields.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-11
Chapter 3
Table 3-4
SSR Configuration
Support Settings Fields
Field
Description
Host Name
Name assigned to the system.
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
Scaling System 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 Scaling System 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.
Table 3-5 displays the button functionality that is available on the Support Settings page.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-12
Chapter 3
SSR Configuration
Table 3-5
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 button is used when a
permissioned Administrator receives a file
containing an update.
Uninstall Update
Uninstall update button is visible immediately
after the update was 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
Shutdown the Cisco UCS Invicta Scaling System.
A dialog box appears to verify the Shutdown
command to avoid any unintentional action.
Reboot
Reboot the Cisco UCS Invicta Scaling System. A
dialog box appears to verify the 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.
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 the Cisco UCS Invicta Scaling System. After the file
has been authenticated by the system, the Administrator is prompted through the remaining update
process.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-13
Chapter 3
Note
Caution
SSR Configuration
Be sure to read and acknowledge the Release Notes and Instructions or the update will not initiate.
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 was 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 Scaling System. A dialog box appears to verify the
Shutdown command to avoid any unintentional action.
Reboot
Click Reboot to reboot the Cisco UCS Invicta Scaling System. 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 Admin
The 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 SSR 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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-14
Chapter 3
SSR Configuration
Step 2
Right-click the mouse.
A right-click menu appears with Suppress and Resolved options (see Table 3-6).
Step 3
Choose Suppress or Resolved.
Table 3-6
Action
Alert Admin Actions
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-15
Chapter 3
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
3-16
SSR Configuration
CH A P T E R
4
LUN Configuration
•
The LUNs List, page 4-1
•
Initiator Groups, page 4-10
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 Scaling System 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:
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-1
Chapter 4
Step 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.
Click Create LUN or click Cancel to close the dialog box without creating a new LUN.
Increase LUN Size
Note
Step 1
If a LUN has Snapshots or is part of an asynchronous replication pairing, its size cannot be increased
(see Chapter 5, “Asynchronous Replication”).
Choose LUN Configuration > LUNs.
The LUN window appears.
Step 2
Highlight a LUN from the LUNs list by mousing over it and right click.
The right-click menu appears.
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.
Note
Note the following Snapshot characteristics:
•
LUN Snapshots are differentiated in the LUN list when the LUN’sCisco UCS Invicta Scaling
System Administration and Configuration Guide, Version 5.0.1.1aCisco UCS Invicta Scaling
System Administration and Configuration Guide, Version 5.0.1.1aCisco UCS Invicta Scaling
System Administration and Configuration Guide, Version 5.0.1.1a “Origin” and “Snap%” columns
are populated.
•
Snapshots can be created either manually or on a schedule.
•
When a Snapshot is created, it resides on the same VG as the Origin LUN.
•
The number of Snapshots, from one to the maximum of ten, can be configured or set individually
on a per-LUN basis. The default value during creation or scheduling is 3 snapshots per LUN.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-2
Chapter 4
LUN Configuration
Caution
Note
•
When a Snapshot is created, its initial size is automatically calculated based upon the size of the
Origin LUN.
•
Snapshots are automatically resized based upon the number of changes to the Origin LUN and the
amount of free space left on the Origin LUN. Depending on the rate of change on the origin, the
snapshot may occasionally resize to become larger than the Origin LUN.
•
Snapshots can be mounted for read/write purposes.
•
One or more Snapshots can be deleted manually. Note that an Origin LUN cannot be deleted unless
all of its snapshots are deleted beforehand. To that extent, you cannot select to delete both the Origin
LUN and the Snapshot together.
•
When available free space on the system falls below a threshold level of 10%, the system
automatically deletes the oldest Snapshot on the device to free up space.
•
A LUN Snapshot can be merged (only) with its Origin LUN, one Snapshot at a time, without concern
about the order in which the Snapshots were created.
•
Snapshot performance under I/O can be checked.
•
Snapshot scheduling applies to the current SSR only and is not accessible from other SSRs. If the
current SSR is down, the configured Snapshot schedule is not executed during this downtime from
other SSRs.
•
When available free space on the system falls below a threshold level of 10% scheduled or manual
Snapshot creation is not permitted. To create space, the system automatically deletes the oldest
Snapshot(s) until there is at least 15% of free space on the device.
•
A LUN Snapshot can be merged (only) with its Origin LUN, one Snapshot at a time, without concern
about the order in which the Snapshots were created.
•
If the Snapshot becomes degraded for any reason (i.e., it is consistently displayed in red on the LUN
list), call the Cisco Technical Support for assistance as it is not possible to delete this Snapshot from
the user interface.
•
Snapshots cannot be used either as a Source or Destination for creating an Async Replication
pairing.
•
Increasing the size of LUNs containing Snapshot(s) is not permitted. You must delete all the
snapshots for the Origin LUN Snapshot prior to increasing its size.
You should regularly monitor the growth of the Snapshot and the amount of disk space available on the
device.
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 LUN. In addition, any mounted file systems on that Snapshot
device may be forcibly unmounted.
The following three conditions must be true for the successful operation of the Snapshot feature:
•
The maximum number of Snapshots PER SSR is limited to 254.
•
The total number of Snapshots per hour for the entire device (both SSRs) is less than 20.
•
Each LUN is scheduled at a maximum rate of one Snapshot per hour.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-3
Chapter 4
LUN Configuration
To create a snapshot, do the following:
Step 1
Choose LUN Configuration > LUNs.
The LUNs window appears.
Step 2
Highlight a LUN from the LUNs list by mousing over it and right click.
The right-click menu appears.
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
The maximum scheduling for a Snapshot is once per hour on a LUN.
Step 1
Choose LUN Configuration > LUNs.
The LUNs window appears.
Step 2
Mouse over a LUN to highlight it and right click.
The right-click menu appears.
Step 3
Choose Schedule Snapshot.
The Snapshot Schedule Setup dialog box appears.
Step 4
Note
Do one or both of the following:
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.
•
Step 5
Click Delete for any scheduled entry you want to remove.
Click Save Schedule to save the LUN Snapshot schedule.
Note
Creation of a Snapshot or the scheduling of a Snapshot is not permitted on a mirrored LUN.
Note
Snapshots for a LUN on a striped Volume Group (VG) is not supported.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-4
Chapter 4
LUN Configuration
Merge Snapshot
When a Snapshot is merged, the data on the Snapshot replaces the data on the Origin LUN. When the
merge finishes, the merged snapshot is automatically deleted from the system.
Caution
A power-loss during a merge operation on any of the SSR/SSN may render permanent data corruption
on the Origin and on the reminder of the snapshots for the Origin LUN.
Note
During the Snapshot Merge process, GUI performance may be affected until the process completes. The
larger the size and/or the changes on the Origin LUN, the more time the process may take. We
recommend merging larger LUNs during off-peak hours.
To the increase the speed of merging snapshots, we recommend to:
•
Delete other snapshots of the LUN. The fewer the number of snapshots a LUN has, the quicker the
merge.
•
Merge snapshots before large amounts of data is written to them. Smaller snapshots merge more
quickly.
To merge a Snapshot, do the following:
Note
Step 1
Before merging a LUN Snapshot with its Origin LUN:
•
We recommend that the number of Snapshots for the origin are kept to the minimum needed.
•
Make sure that both the Origin LUN and the Snapshot are closed.
Choose LUN Configuration > LUNs.
The LUNs window appears.
Step 2
Mouse over a LUN snapshot to highlight it and right click.
The right-click menu appears.
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 when the creation of a new
Snapshot is triggered, either manually or by schedules.
An exception to this process occurs when the oldest Snapshot is mapped to a host or is in use. The
Snapshot will not be automatically deleted and the Snapshot creation will fail. A “Failed Snapshot
Creation” alert is triggered.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-5
Chapter 4
LUN Configuration
However, if free disk space on the node is reduced to 10% or less and the automatic deletion of Snapshots
is triggered, the oldest Snapshots on the device are deleted whether or not they are in use or mapped to
a host and until at least 15% of free space is available.
Any Snapshot can be manually deleted. To manually delete a Snapshot, do the following:
Step 1
Choose LUN Configuration > LUNs.
The LUNs window appears.
Step 2
Mouse over a LUN snapshot to highlight it and right click.
The right-click menu appears.
Step 3
From the right-click menu, choose Delete.
The Delete Snapshot confirmation dialog box appears.
Step 4
Note
Choose Delete or choose Cancel to return to the LUNs window.
Attempting to delete Snapshots and LUNs at the same time is not permitted. We recommend that you
delete all associated Snapshots before deleting the Origin LUN.
Check Performance
Step 1
Choose LUN Configuration > LUNs.
The LUNs window appears.
Step 2
Mouse over a LUN or LUN snapshot to highlight it and right click.
The right-click menu appears.
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.
Step 5
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 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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-6
Chapter 4
LUN Configuration
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:
Step 1
Choose LUN Configuration > LUNs.
The LUN window appears.
Step 2
Highlight a LUN from the LUNs list by mousing over it and right click.
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.
LUN Mirror
LUN Mirroring is a mapping that maintains two identical data copies. Mirrored LUN are often used to
achieve better availability and to provide a degree of fault tolerance. Data is written to both LUNs
simultaneously. Should one of the LUN drives fail or becomes unavailable; the system continues to
operate using the unaffected drive.
Note
Note
•
A LUN with an existing Snapshot cannot be setup as a LUN mirror Source.
•
LUN with a Snapshot schedule (but without any snapshots) configured from either SSR cannot be
used as a LUN mirror Source.
•
Simultaneous mirror operations are not supported on the Cisco UCS Invicta Scaling System. You
must wait for the operation on one LUN to complete before performing another.
The creation or scheduling of a Snapshot is not permitted on a mirrored LUN.
Create LUN Mirror
To create a LUN Mirror, do the following:
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-7
Chapter 4
Note
Step 1
LUN Configuration
During the LUN mirror operation, The LUN I/O is paused on the partner SSR.
Choose LUN Configuration > LUNs.
The LUN window appears.
Step 2
Highlight a LUN from the LUNs list by mousing over it and right click.
The right-click menu appears.
Step 3
Choose the Mirror menu option.
The Create Mirror dialog box appears.
Step 4
Type the name of the LUN Mirror into the New LUN field.
Step 5
Choose a Volume Group from the VG drop-down list.
Step 6
Click Create Mirror, or click Cancel and return to the LUNs list.
Note
When creating the mirror, a progress dialog box appears. Click Close to exit the dialog box when the
mirror is finished.
LUN Mirror Creation Indicators
•
If a LUN Mirror is successfully created, the LUN Mirror Name text appears in green.
•
If the LUN destination to which the data would be mirrored is out of sync, the entire LUN Name
field appears in red.
•
When creating a LUN mirror, if there is not enough space left on all Volume Groups, the Volume
Group drop-down list will not be selectable. The error message, “No volume groups qualify to create
mirror,” is stated on the pop-up.
Increase Size
To increase the size on a mirrored LUN, do the following:
Step 1
Choose LUN Configuration > LUNs.
The LUN window appears.
Step 2
Highlight a mirrored LUN from the LUNs list by mousing over it and right click.
The right-click menu appears.
Step 3
Choose Increase Size.
The Increase Size dialog box appears
Step 4
Enter a valid value to increase the LUN size.
The value of the size to increase must be equal to or smaller than the Volume Group with the lowest
available space.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-8
Chapter 4
LUN Configuration
Note
•
Increasing size on a mirrored LUN will cause I/O to be interrupted. We recommend that you pause
I/O when performing this operation.
•
The Resync mirror operation will be automatically initiated when increasing size on a mirrored
LUN.
Resync Mirror
Use Resync Mirror after the LUN becomes available again ensures that both copies are the same.Should
a Source LUN or its mirror (the Destination LUN) become unavailable,
Note
The Resync Mirror right-click menu option is only visible on mirrored LUNs.
To resync a mirror do the following:
Step 1
Choose LUN Configuration > LUNs.
The LUN window appears.
Step 2
Highlight a mirrored LUN from the LUNs list by mousing over it and right click.
The right-click menu appears.
Step 3
Choose Resync Mirror.
The Resync Mirror function is initiated and a progress dialog box appears.
Step 4
Click Close to exit the dialog box when the mirror has completed resynchronization.
Break Mirror
Note
The Break Mirror right-click menu option is only visible on mirrored LUNs.
To break a LUN mirror, do the following:
Note
Step 1
When breaking a mirror, we recommend stopping the LUN I/O during the operation.
Choose LUN Configuration > LUNs.
The LUN window appears.
Step 2
Highlight a mirrored LUN from the LUNs list by mousing over it and right click.
The right-click menu appears.
Step 3
Choose Break Mirror.
The Break Mirror verification dialog box appears.
Step 4
Click Break Mirror or click Cancel and return to the LUNs list.
•
If the destination LUN is deleted the original LUN remains available as a standalone.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-9
Chapter 4
•
LUN Configuration
If the destination LUN is kept, it appears on the LUNs list and takes on the characteristics of an
independent LUN
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 1
Choose LUN Configuration > LUNs.
The LUN window appears.
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.
The right-click menu appears.
Step 3
Choose Check Performance.
The LUN Performance Information Monitor appears.
Step 4
Mouse over a performance grid to view detailed information.
Step 5
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 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 Groups
Initiator 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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-10
Chapter 4
LUN Configuration
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 1
Choose LUN Configuration > Initiator Groups.
The Initiators window appears.
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
Note
Enter in the WWN/IQN and click Create Initiator or click Cancel to return to the Initiators list.
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
Step 1
Avoid mapping a LUN until an Initiator has been added to the Initiator Group.
Choose LUN Configuration > Initiator Groups.
The Initiators window appears.
Step 2
Click an Initiator Group to highlight it and right click.
The right-click menu appears.
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-11
Chapter 4
LUN Configuration
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
Note
Step 7
Note
Repeat Steps 4 and 5 for each preferred available LUN.
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 this section.
Click Back to Initiators to return to the Initiator Groups window.
The size of the Snapshot displayed during LUN mapping will be the same as that of its Origin LUN.
Unmap LUN from Initiator
Step 1
Choose LUN Configuration > Initiator Groups.
The Initiators window appears.
Step 2
Click an Initiator Group to highlight it and right click.
The right-click menu appears.
Step 3
Choose Map/Unmap LUNs.
The Initiator LUN window appears.
Step 4
Do one of the following:
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-12
Chapter 4
LUN Configuration
•
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
Step 1
Unmap all LUNs from an Initiator Group before attempting to delete it to avoid data loss.
Choose LUN Configuration > Initiator Groups.
The Initiators window appears.
Step 2
Click an Initiator Group to highlight it and right click.
The right-click menu appears.
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-13
Chapter 4
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
4-14
LUN Configuration
CH A P T E R
5
Asynchronous 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
•
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.
•
When using the Async Replication feature, both the Source and the Target must be LUNS, except
for the Windows Pairing type where the Destination is a Windows file.
•
The Source and Target LUNs must be the same size and must be 2TB or less.
•
Use “Create New Pairings” to add a new partner host. A LUN must be present before a pairing can
be created.
•
The Cisco UCS Invicta Scaling System uses the standard remote shell facility, ssh, to send the public
key. Use "Public Key" to display this key. The key must be copied and pasted into the
authorized_keys list. See section - Communicating with the Partner Host
•
Use "Windows Installer" to obtain an installation package for software required for Windows use of
Async Replication.
•
The first replication that is performed on a pairing is always a FULL replication. Subsequent
replications reflect the delta changes, except where an "Update Partner" operation is performed. In
that case, the next replication is a FULL replication.
•
When updating a partner host, a full replication is triggered.
•
We do not recommend using Destination entities in Read-Write mode as this poses a risk to the
accuracy of the data replication and may corrupt data recovery.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-1
Chapter 5
Note
Asynchronous Replication
•
During the replication process, the Destination LUN will be unmapped and unmounted and is,
therefore, inaccessible. This state prevents possible corruption of the Source data. The replication
process will automatically remap and remount at its completion. The Source SSR will continue to
have access to the Source LUN throughout the replication process.
•
Right-click a pairing in the list to display pairing menu options to: Delete, Verify Partner, Update
Partner, Schedule, Restore (always the entire LUN), or View Log File.
•
On mouse hover, the replication schedule for that LUN pairing appears in a pop-up box.
•
Once Async Replication pairing is setup, the “Increase in Size” and “Delete” operations are not
permitted on the Source LUN used for the pairing.
•
A LUN that has been configured as a Mirror is not supported to be used either as an Async Source
or Destination for performing Async Replication.
•
When restoring the Source LUN, the Restore process will unexport and unmount the LUN and it will
not be accessible. The Restore process will automatically re-mount and re-export at its completion.
•
Pairing setup, configuration, and scheduling applies to the current SSR only and is not accessible
from other SSRs.
•
If a host and/or device is not detected when checked, the respective fields turn red. The following
actions trigger checks: page refresh, new host pairing creation, pairing deletion, pairing host update
(check is performed on a specific update entry), manual replication scheduling and replication
termination.
•
Device column displays in green for a replication that is in progress and tan when a restore is in
progress.
•
When scheduling an Async Replication, note that the higher the thread numbers the higher the
throughput the greater the impact on system processing. The default is two. Initial transmission
block size 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.
•
We do not recommend running several simultaneous replications and / or concurrent restores as
these operations will have a severe performance impact on the Source and or Destination devices.
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 Host
To 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:
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-2
Chapter 5
Asynchronous Replication
– 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
Additional
Information
Platform
Supported Releases
Cisco
Cisco UCS Invicta OS Destination LUN
>= 5.0.0
needs to be a LUN of
the same size as the
source LUN and
they both need to be
2 TB or less.
Linux-LVM
Kernel version >=
2.6.3
LVM2 version >=
2.02
Linux-RAW
Windows
Kernel version >=
2.6.3
Windows 2008 R2 or
later Server editions
Examples
•
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_CiscoPairingDestinatio
nLun
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
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
•
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
Duplicates directly
to a file.
Note
This pairing
type is not
designed for
large size or
Replication
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-3
Chapter 5
Asynchronous Replication
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:
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-4
Chapter 5
Asynchronous Replication
•
$ 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 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:
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-5
Chapter 5
Note
Asynchronous Replication
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-6
Chapter 5
Asynchronous Replication
Step 3
Note
Click Windows Installer.
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 4
Click Public Key to obtain the public key necessary for using password-less ssh access.
The SSH Public Key dialog box appears.
Step 5
Copy the ssh key and click OK.
Step 6
Open a Terminal window and navigate to the /home/Administrator/.ssh directory.
Step 7
Enter vi authorized_keys.
Step 8
Paste the Cisco Public Key copied in Step 2 into the authorized_keys list and click Enter.
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
Caution
A LUN must be present before a pairing can be created.
We do not recommended using 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, Increase Size and Delete operations are disabled on the Source
LUN used for the pairing.
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
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-7
Chapter 5
•
Schedule
•
Restore
•
View Log File
Asynchronous Replication
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:
Step 1
Choose Async Replication > Pairings.
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.)
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
Target Type
Target Device
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.
The device for storing the replication.
Note
Step 4
It is important that this directory is non-volatile for rebooting.
When replicating to a file, be sure to include the extension at the
end of the file name.
Click Create Pairing to create pairing or click Cancel to return to Async Replication window.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-8
Chapter 5
Asynchronous Replication
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 1
Choose Async Replication > Pairings.
The Pairings window appears.
Step 2
Mouse over an Async Replication pairing to highlight it and right click.
The right-click menu appears.
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 1
Choose Async Replication > Pairings.
The Pairings window appears.
Step 2
Mouse over an Async Replication pairing to highlight it and right click.
The right-click menu appears.
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
To update an existing Partner Host, do the following:
Step 1
Choose Async Replication > Pairings.
The Pairings window appears.
Step 2
Mouse over an Async Replication pairing to highlight it and right click.
The right-click menu appears.
Step 3
Choose Update.
The Update Partner Host dialog box appears.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-9
Chapter 5
Asynchronous Replication
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 1
Choose Async Replication > Pairings.
The Pairings window appears.
Step 2
Mouse over an Async Replication pairing to highlight it and right click.
The right-click menu appears.
Step 3
Choose Schedule.
The Replication Schedule Setup dialog box appears.
Step 4
Step 5
Note
Complete the fields as described in Table 5-3.
•
Threads
•
Init Block Size (MB)
Do one or both of the following:
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-10
Chapter 5
Asynchronous Replication
Step 6
Note
Click Delete for any scheduled entry you want to remove.
The choices for Thread and Init Block Size stay constant for any Async Replication that is scheduled for
this LUN Pairing.
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 two.
Tip
Init Block Size (MB)
Step 7
Use the default (2) for peak computing hours. Use higher
thread for off-peak computing hours.
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 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 1
Choose Async Replication > Pairings.
The Pairings window appears.
Step 2
Mouse over an Async Replication pairing to highlight it and right click.
The right-click menu appears.
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).
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-11
Chapter 5
Click Restore or click Cancel to return to the Async Replication window.
Table 5-4
Restore Selection Options
Source:
Threads
New
•
LUN Name
•
Volume Group
•
Threads
View Log File
To view replication and restoration log files, do the following:
Step 1
Choose Async Replication > Pairings.
The Pairing window appears.
Step 2
Mouse over an Async Replication pairing to highlight it and right click.
The right-click menu appears.
Step 3
Choose View Log File.
The Replication/Restoration Activity dialog box appears.
Step 4
Do one of the following:
•
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5-12
Asynchronous Replication
CH 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 Role
Roles 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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
6-1
Chapter 6
Users
The Role of Enterprise Administrator would likely be assigned permissions to access and perform all
actions on all windows.
Note
Roles must be created before attempting to assign them to a user. Otherwise, there will be no roles from
which to select.
To assign a role to a user account, do the following:
Step 1
Click Users > User Accounts.
The User Accounts window appears.
Step 2
Right-click a User Account.
The right-click menu appears.
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 Account
To delete a user account, do the following:
Step 1
Click Users > User Accounts.
The User Accounts window appears.
Step 2
Choose a User Account and right-click.
The right-click menu appears.
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 Account
To edit a user account, do the following:
Step 1
Click Users > User Accounts.
The User Accounts window appears.
Step 2
Choose a User Account and right-click.
The right-click menu appears.
Step 3
Choose Edit.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
6-2
Chapter 6
Users
The Edit User dialog box appears.
Step 4
Complete necessary changes to fields.
Step 5
Click Save User or click Cancel to return to User Accounts window.
Create or Modify a Role
A 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.
Step 2
Do one of the following:
•
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.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
6-3
Chapter 6
Users
Delete a Role
To 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
Step 1
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 name. To change passwords:
Choose Users > Change Password.
The Change Password window appears.
Step 2
Complete the fields and click Change Password.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
6-4