Cisco UCS Director Shell Guide, Release 4.1
First Published: 2013-12-16
Last Modified: 2014-05-15
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-30565-04
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 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.
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 and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
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. (1110R)
© 2013-2014
Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
Preface v
Audience v
Conventions v
Related Documentation vii
Documentation Feedback vii
Obtaining Documentation and Submitting a Service Request vii
CHAPTER 1
Overview 1
About Cisco UCS Director 1
About Cisco UCS Director Shell Commands 2
Prerequisites 3
Logging into the Shell 3
CHAPTER 2
Using Shell Commands 5
General Administration 5
Examining the Version Information 5
Stopping Cisco Services 6
Starting Cisco Services 6
Displaying the Status of Your Services 7
Changing Your Password 8
Synchronizing the System Time 9
Pinging the Hostname and IP Address 9
Configuring a Network Interface 10
Displaying Appliance Network Details 10
Adding the BMA Hostname and IP Address 11
Viewing Tail Inframgr Logs 12
Applying a Patch to Cisco UCS Director 12
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
iii
Contents
Working with Databases 13
Stopping the Database 13
Starting the Database 14
Backing Up the Database 14
Restoring the Database 15
Enabling the Database for BMA 16
Importing Certificates 17
Importing a CA Certificate (JKS) File 17
Importing a CA Certificate (PEM) File for VNC 17
Accessing Root Privileges 18
Enabling Root Access 18
Disabling Root Access 19
Configuring Root Access 19
Logging in as Root 20
Using a Multi-Node Setup 20
Database Nodes 21
Summary of Steps for Configuring a Multi-Node Setup 21
Creating the Inventory Database 22
Creating the Monitoring Database 23
Creating the Primary Node 23
Creating a Service Node 24
Cisco UCS Director Shell Guide, Release 4.1
iv
OL-30565-04
Preface
This preface contains the following sections:
• Audience, page v
• Conventions, page v
• Related Documentation, page vii
• Documentation Feedback, page vii
• Obtaining Documentation and Submitting a Service Request, page vii
Audience
This guide is intended primarily for data center administrators who use Cisco UCS Director and/or Cisco
UCS Director Express and who have responsibilities and expertise in one or more of the following:
• Server administration
• Storage administration
• Network administration
• Network security
• Virtualization and virtual machines
Conventions
Text Type
Indication
GUI elements
GUI elements such as tab titles, area names, and field labels appear in this font.
Main titles such as window, dialog box, and wizard titles appear in this font.
Document titles
Document titles appear in this font.
TUI elements
In a Text-based User Interface, text the system displays appears in this font.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
v
Preface
Conventions
Text Type
Indication
System output
Terminal sessions and information that the system displays appear in this
font.
CLI commands
CLI command keywords appear in this font.
Variables in a CLI command appear in this font.
Note
Tip
[]
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.
<>
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.
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
Means the following information will help you solve a problem. The tips information might not be
troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Caution
Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.
Timesaver
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Cisco UCS Director Shell Guide, Release 4.1
vi
OL-30565-04
Preface
Related Documentation
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.
SAVE THESE INSTRUCTIONS
Related Documentation
Cisco UCS Director Documentation Roadmap
For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation
Roadmap available at the following URL: http://www.cisco.com/en/US/docs/unified_computing/ucs/
ucs-director/doc-roadmap/b_UCSDirectorDocRoadmap.html.
Cisco UCS Documentation Roadmaps
For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/b-series-doc.
For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap
available at the following URL: http://www.cisco.com/go/unifiedcomputing/c-series-doc.
Note
The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco
UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes
links to documentation for Cisco Integrated Management Controller.
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information,
see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco
technical documentation.
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
vii
Preface
Obtaining Documentation and Submitting a Service Request
Cisco UCS Director Shell Guide, Release 4.1
viii
OL-30565-04
CHAPTER
1
Overview
This chapter contains the following sections:
• About Cisco UCS Director, page 1
• About Cisco UCS Director Shell Commands, page 2
• Prerequisites, page 3
• Logging into the Shell, page 3
About Cisco UCS Director
Cisco UCS Director (formerly Cisco Cloupia Unified Infrastructure Controller) is a 64-bit appliance that uses
the following standard templates:
• Open Virtualization Format (OVF) for VMware vSphere
• Virtual Hard Disk (VHD) for Microsoft Hyper-V
Cisco UCS Director delivers unified, highly secure management for the industry's leading converged
infrastructure solutions, which are based on the Cisco UCS and Cisco Nexus platforms.
Cisco UCS Director extends the unification of computing and network layers through Cisco UCS to provide
data center administrators with comprehensive visibility and management capability. It supports NetApp
FlexPod and ExpressPod, EMC VSPEX, and VCE Vblock systems, based on the Cisco UCS and Cisco Nexus
platforms.
Cisco UCS Director automates the provisioning of resource pools across physical, virtual, and baremetal
environments. It delivers native, automated monitoring for health, status, and resource utilization. For example,
you can do the following using Cisco UCS Director:
• Create, clone, and deploy service profiles and templates for all servers and applications
• Monitor organizational usage, trends, and capacity across a converged infrastructure on a continuous
basis, such as by viewing heat maps that show virtual machine (VM) utilization across all your data
centers
• Deploy and add capacity to ExpressPod and FlexPod infrastructures in a consistent, repeatable manner
• Manage, monitor, and report on Cisco UCS domains and their components
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
1
Overview
About Cisco UCS Director Shell Commands
• Extend virtual service catalogs to include physical infrastructures services
• Manage secure multitenant environments to accommodate virtualized workloads that run with
nonvirtualized workloads
About Cisco UCS Director Shell Commands
This guide describes all of the commands available to you when logging into the Cisco UCS Director shell.
You can use these commands to perform the following administrative tasks:
• Stopping/starting all Cisco services
• Display Service Status
• Stopping/starting the MySQL database
• Backing up/restoring the appliance database
• Changing ShellAdmin password
• Synching up time
• Configuring network interface
• Enabling the database for a BMA Appliance
• Adding a BMA hostname/IP address to the appliance
• Displaying network details
• Pinging hostname/IP address
• Version (Cisco UCS Director appliance version)
• Importing CA (JKS) file
• Importing CA Cert (PEM) file for Virtual Network Computing (VNC)
• Shutdown of the Appliance
• Rebooting the Appliance
• Manage Root Access
• Troubleshooting Tail inframgr logs
• Applying a patch to the appliance
• Quitting the shell
• Login as Root
• Configuring Multi-node Setup
•
For additional system administration information refer to the Cisco UCS Director Administration Guide,
Release 4.0.
Cisco UCS Director Shell Guide, Release 4.1
2
OL-30565-04
Overview
Prerequisites
Prerequisites
To successfully execute the commands described in this guide, you must meet the following prerequisites:
• Cisco UCS Director should be up and running (and reachable).
Note
The information in this guide is based on Cisco UCS Director, release 4.0 and later releases.
Logging into the Shell
The login procedure requires the use of a Secure Shell (SSH) client and the proper login credentials. After
gaining access to Cisco UCS Director appliance you can perform a wide variety of system administration
tasks.
Before You Begin
Obtain proper access to a Cisco UCS Director appliance and a secure shell (SSH) application.
Step 1
Step 2
Step 3
Open your SSH application.
Enter the Cisco UCS Director appliance IP address.
In the Port field, enter 22.
The shell window displays the introductory Cisco UCS Director Shell Menu.
Step 4
Step 5
In the User field, enter shelladmin.
In the Password field, enter one of the two following choices:
• Enter changeme.
• From the CLI, enter SSH shelladmin@<IP Address>.
Step 6
Press the Enter key.
The following services are available for selection:
Cisco UCS Director Shell Menu
Select a number from the menu below
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
14)
Change ShellAdmin password
Display Services Status
Stop Services
Start Services
Stop Database
Start Database
Backup Database
Restore Database
Time Sync
Ping Hostname/IP Address
Show version
Import CA Cert (JKS) File
Import CA Cert(PEM) File for VNC
Configure Network Interface
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
3
Overview
Logging into the Shell
15)
16)
17)
18)
19)
20)
21)
22)
23)
24)
Display Network Details
Enable Database for Cisco UCS Director Baremetal Agent
Add Cisco UCS Director Baremetal Agent Hostname/IP
Tail Inframgr logs
Apply Patch
Shutdown Appliance
Reboot Appliance
Manage Root Access
Login as Root
Quit
SELECT>
Note
Some minor Cisco UCS Director releases (after release 4.0) may or may not include all of the options listed
above.
Cisco UCS Director Shell Guide, Release 4.1
4
OL-30565-04
CHAPTER
2
Using Shell Commands
This chapter contains the following sections:
• General Administration, page 5
• Working with Databases, page 13
• Importing Certificates, page 17
• Accessing Root Privileges, page 18
• Using a Multi-Node Setup, page 20
General Administration
This section describes how to execute common administration tasks such as changing your password, stopping
and starting services, as well as other common system administration tasks.
Examining the Version Information
You can verify the Cisco UCS Director version and build number by choosing Show Version. This information
is required for debugging purposes.
Step 1
From the Cisco UCS Director Shell menu choose Show Versionand press Enter.
The following information is displayed:
Cisco UCS-D
----------Version
: 4.0.0.2
Build Number : 22
Press return to continue ...
Step 2
Press Enter to complete the process.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
5
Using Shell Commands
Stopping Cisco Services
Stopping Cisco Services
You can stop all Cisco services that are part of the Cisco UCS Director appliance by choosing Stop Services.
You can verify that all services are stopped by choosing Display Service Status.
Step 1
Step 2
From the Cisco UCS Director Shell menu choose Stop Services.
Press Enter.
The following information displays:
Stopping broker [PID=17364]/[Child=17365]
Stopping controller [PID=17402]/[Child=17404]
Stopping eventmgr [PID=17471]/[Child=17473]
Stopping client [PID=17535]/[Child=17537
17615
17678]
Stopping idaccessmgr [PID=17613]/[Child=]
/opt/infra/stopInfraAll.sh: line 35: kill: (17613) - No such process
Stopping inframgr [PID=17676]/[Child=]
Tomcat is running with [PID=17779]. Stoping it and its child process
Flashpolicyd is running with [PID=17807]. Stopping it
Stopping websock[PID=17812]
Press return to continue ...
Step 3
Press Enter to complete the procedure.
Starting Cisco Services
You can execute all services that are part of Cisco UCS Director by choosing Start Services.
After using this option, you can choose Display Service Status to verify that all services are executed.
Note
Step 1
Services started in the background are not displayed.
From the Cisco UCS Director Shell menu choose Start Services.
The following information is displayed:
Press return to continue ...nohup: appending output to `nohup.out'
Step 2
Step 3
Press Enter to complete the process.
Choose Display Service Status to verify that the services are executed.
Cisco UCS Director Shell Guide, Release 4.1
6
OL-30565-04
Using Shell Commands
Displaying the Status of Your Services
Displaying the Status of Your Services
The Display Services option displays all executed services. You can execute seven services at any one time.
• Broker
• Controller
• Eventmgr
• Client
• Idaccessmgr
• Inframgr
• Tomcat
• Websock (VNC interface)
• Database (mysqld)
Note
Step 1
Ensure that all of the above services are up and operating. If a service is not executed on Cisco UCS
Director, restart the service through the shell client.
From the Cisco UCS Director Shell menu choose option Display Service Status.
The following list of services appears:
Cisco UCS Director Shell Menu
Select a number from the menu below
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
14)
15)
16)
17)
18)
19)
20)
Change ShellAdmin password
Display Services Status
Stop Services
Start Services
Stop Database
Start Database
Backup Database
Restore Database
Time Sync
Ping Hostname/IP Address
Show version
Import CA Cert (JKS) File
Import CA Cert(PEM) File for VNC
Configure Network Interface
Display Network Details
Enable Database for Cisco UCS Director Baremetal Agent
Add Cisco UCS Director Baremetal Agent Hostname/IP
Tail Inframgr logs
Apply Patch
Shutdown Appliance
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
7
Using Shell Commands
Changing Your Password
21)
22)
23)
24)
Reboot Appliance
Manage Root Access
Login As Root
Quit
SELECT> 2
Service
---------broker
controller
eventmgr
client
idaccessmgr
inframgr
TOMCAT
websock
Status
---------RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
PID
----18718
18758
18792
18891
18938
18997
19054
19083
2903 ?
00:00:00 mysqld_safe
3192 ?
7-10:59:53 mysqld
Press return to continue ...
Note
The corresponding status and process ID (PID) of each service is also displayed in the
menu.
Step 2
Changing Your Password
You can change your Cisco UCS Director shell password by choosing Change ShellAdmin password.
Step 1
From the Cisco UCS Director Shell menu choose Change ShellAdmin passwordand press Enter. The following
information is displayed:
Changing password for user shelladmin.
New UNIX password:
Step 2
Step 3
Enter your new UNIX password and press the Enter key.
Enter your new UNIX password once again and press the Enter key. The following information is displayed:
passwd: all authentication tokens updated successfully. Press return to continue...
Cisco UCS Director Shell Guide, Release 4.1
8
OL-30565-04
Using Shell Commands
Synchronizing the System Time
Synchronizing the System Time
You can synchronize the system time to the hardware time as well as the NTP server by choosingTime Sync.
Step 1
Step 2
From the Cisco UCS Director Shell menu choose Time Sync.
Press Enter.
The following information is displayed:
Time Sync......
System time is Tue Sep 17 15:57:34 UTC 2013
Hardware time is Tue Sep 17 15:57:35 2013 -0.849104 seconds
Do you want to sync systemtime [y/n]? y
NTP Server IP Address: 172.25.168.203
5 Dec 03:24:02 ntpdate[5017]: step time server 172.25.168.203 offset 25510.954857 sec
Sync'ed with NTP SERVER 172.25.168.203
Press return to continue ...
Step 3
Step 4
Step 5
Press Y and press Enter to synchronize to system time.
Press Y and press the Enter to synchronize to the NTP server.
Press Enter key to complete the process.
Pinging the Hostname and IP Address
You can ping a hostname or IP address to test your connectivity by choosing Ping Hostname/IP address.
Step 1
Step 2
From the Cisco UCS Director Shell menu choose option Ping Hostname/IP addres and press Enter.
Enter your IP address and press Enter.
The following information is displayed:
Enter IP Address : 209.165.200.224
PING 209.165.200.224 (209.165.200.224) 56(84) bytes of data.
64 bytes from 209.165.200.224: icmp_seq=1 ttl=64 time=9.90 ms
64 bytes from 209.165.200.224: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 209.165.200.224: icmp_seq=3 ttl=64 time=0.254 ms
64 bytes from 209.165.200.224: icmp_seq=4 ttl=64 time=0.198 ms
64 bytes from 209.165.200.224: icmp_seq=5 ttl=64 time=0.267 ms
--- 209.165.200.224 ping statistics --5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.198/2.187/9.901/3.857 ms
Press return to continue ...
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
9
Using Shell Commands
Configuring a Network Interface
Step 3
Press Enter to exit out of the operation.
Configuring a Network Interface
You can configure a network interface for the Cisco UCS Director appliance by choosing Configure a Network
Interface.
Step 1
From the Cisco UCS Director Shell menu choose Configure a Network Interface and press Enter.
The following information displays:
Do you want to Configure DHCP/STATIC IP
Step 2
[D/S] ? : S
Choose one of the following configuration selections:
• Choose D to configure a DHCP IP address.
• Choose S to configure a static IP address.
Step 3
Enter s to configure a static IP address and press Enter. The following information is displayed.
Configuring STATIC configuration..
Enter the ethernet interface that you want configure E.g. eth0 or eth1:
Step 4
Enter the Ethernet interface to configure (for example, eth1) and press Enter. The following information displays:
Configuring STATIC IP for eth1...
IP Address: 209.165.200.224
Netmask: 255.255.255.0
Gateway: 209.187.108.1
DNS Server1: 198.51.100.1
DNS Server2: 203.0.113.1
Configuring Network with : INTERACE(eth1), IP(209.165.200.224), Netmask(255.255.255.0),
Gateway(209.187.108.1),
DNS Server1(198.51.100.1), DNS Serverx 2(203.0.113.1)
Do you want to continue
Step 5
[y/n]? :
Enter n to discontinue the configuration process. Press Enter to return to complete the process.
Displaying Appliance Network Details
You can display the Cisco UCS Director appliance network details by choosing option 15, Display Appliance
Network Details.
Step 1
From the Cisco UCS Director Shell menu choose option 15 and press Enter.
Cisco UCS Director Shell Guide, Release 4.1
10
OL-30565-04
Using Shell Commands
Adding the BMA Hostname and IP Address
The following information is displayed:
Network details....
eth0
Link encap:Ethernet HWaddr 00:50:56:97:1E:2D
inet addr:192.0.2.23 Bcast:192.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::230:56gg:fe97:1e2d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:189818223 errors:14832 dropped:17343 overruns:0 frame:0
TX packets:71520969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:105749301003 (98.4 GiB) TX bytes:27590555706 (25.6 GiB)
Interrupt:59 Base address:0x2000
lo
Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1821636581 errors:0 dropped:0 overruns:0 frame:0
TX packets:1821636581 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:327846827946 (305.3 GiB) TX bytes:327846827946 (305.3 GiB)
Press return to continue ...
Step 2
Press Enter to complete the process.
Adding the BMA Hostname and IP Address
Choose this option to add Bare Metal Agent (BMA) appliance hostname and IP address entries into the Cisco
UCS Director appliance's /etc/hosts file.
Step 1
From the Cisco UCS Director Shell menu choose option Add Cisco VCS Director Baremetal Agent and press Enter.
The following information displays:
Adding Cisco UCS Direcor Baremetal Agent Hostname and IP Address entry to /etc/hosts
Enter Cisco UCS Director Baremetal Agent IP Address:192.0.2.1
Enter Cisco UCS Director Baremetal Agent Hostname:192.44.2.1
Adding host entry 192.3.55.1 to /etc/hosts
Entry 192.3.55.1 does not exists
Backed up old file...
Added new entry 192.3.55.1
Added 192.44.2.1 To /etc/hosts
Press return to continue ...
Step 2
Press Enter to return to complete the process.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
11
Using Shell Commands
Viewing Tail Inframgr Logs
Viewing Tail Inframgr Logs
You can view inframgr logfiles. You can choose the required logfile to view by choosing Tail Inframgr Logs.
Step 1
From the Cisco UCS Director Shell menu choose Tail Inframgr Logs and press Enter.
The following information is displayed:
Enter the logfile sequence 0, 1, 2 (Eg. 0-logfile.txt, 1-logfile.txt.1, 2-logfile.txt.2):
Step 2
Step 3
Choose the file you need to view.
Type Ctrl + C to exit the process.
Note
This step logs you out of the shelladmin. Log back in to conduct another procedure.
Applying a Patch to Cisco UCS Director
Choose this option to apply a patch to the appliance.
Note
It is recommended that you review the patch release notes before applying a patch.
Note
The patch file (zip file) is provided by Cisco UCS Director. It is also recommended that you take a snapshot
of your VM before applying a patch.
Note
It is recommended that you stop the appliance services before applying a patch.
Before You Begin
• Download the patch file
• Place the file in a web server or FTP server
• Choose Apply Patch from the Cisco UCS Director Shell menu
• Provide patch URL (http://WebServer/TestPkg.zip)
Step 1
From the Cisco UCS Director Shell menu choose Apply Patch and press Enter.
The following information is displayed:
Applying Patch...
Applying Patch:
Patch URL :xxx.xxx.x.xxx/TestPkg.zip
Cisco UCS Director Shell Guide, Release 4.1
12
OL-30565-04
Using Shell Commands
Working with Databases
Applying the Patch http://xxx.xxx.x.xxx/TestPkg.zip [y/n]? y
Step 2
Step 3
Step 4
Step 5
Enter your IP address and press Enter.
Enter the patch URL.
Press Enter.
Enter y to apply the patch. Follow the onscreen prompts to complete the process.
What to Do Next
After the patch is applied, choose Stop Services and Start Services.
Note
Refer to the Cisco UCS Director BMA Installation Guide for additional information.
Working with Databases
This section describes how to enable, start and stop, as well as backup and restore a database.
Stopping the Database
You can halt the mysql daemon (mysqld) by choosing option 5, Stop Database. This option stops all of the
following Cisco services:
• Broker
• Controller
• Eventmgr
• Client
• Idaccessmgr
• Inframgr
• Tomcat
• Websock
Step 1
From the Cisco UCS Director Shell menu choose option 5.
The following information is displayed:
Do you want to stop the database [y/n]?
Stopping database....
Database stopped....
y
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
13
Using Shell Commands
Starting the Database
Stopping broker [PID=21921]/[Child=21923]
Stopping controller [PID=21959]/[Child=21961]
Stopping eventmgr [PID=21993]/[Child=21995]
Stopping client [PID=22052]/[Child=22054
22101
22160]
Stopping idaccessmgr [PID=22099]/[Child=]
Stopping inframgr [PID=22158]/[Child=]
Tomcat is running with [PID=22213]. Stoping it and its child process
Flashpolicyd is running with [PID=22237]. Stopping it
Stopping websock[PID=22242]
Press return to continue ...
Step 2
Follow the onscreen prompts to complete the process by choosing option 6, Start Database .
Starting the Database
You can start the mysql daemon (mysqld) by choosing Start Database.
Note
Step 1
Step 2
This option starts the appliance database only.
From the Cisco UCS Director Shell menu chooseStart Database.
Press Enter.
The following information is displayed:
Starting database.....
directory (/var/lib/mysql/data/confmgr_production) exists
directory (/var/lib/mysql/data/db_private_admin) exists
the file (/var/lib/mysql/data/ib_logfile1) exists
the file (/var/lib/mysql/data/ib_logfile0) exists
the file (/var/lib/mysql/data/ibdata1) exists
Database started
Press return to continue ...130917 10:10:54 mysqld_safe Logging to '/var/log/mysqld.log'.
130917 10:10:54 mysqld_safe Starting mysqld daemon with databaes from /var/lib/mysql/data
Note
The Cisco services are not started automatically when you start the appliance database. Choose Start Services
to start the Cisco services.
Backing Up the Database
You can backup the appliance database to a FTP server. You should stop the Cisco services before you begin
the backup process. To stop the services choose Stop Services. You need the following information in order
to execute the task:
Cisco UCS Director Shell Guide, Release 4.1
14
OL-30565-04
Using Shell Commands
Restoring the Database
• FTP server's IP address (where the database is to be backed up)
• FTP server's login credentials
Note
Step 1
Step 2
After the FTP credentials are provided, the entire database of the Cisco UCS Director appliance is backed
up at the specified FTP location. You can then start the Cisco services by choosing Start Services.
From the Cisco UCS Director Shell menu choose Backup Database.
Press Enter.
The following information is displayed:
Backing database......
Backup will Upload file to an FTP server. Provide the necessary access credentials
FTP Server IP Address:
Step 3
Step 4
Step 5
Enter your FTP Server IP address and press Enter.
Enter your FTP Server login and press Enter.
Enter your FTP Server password and press Enter.
Restoring the Database
Before restoring the database, stop the Cisco services. To stop the services, choose Stop Services. Provide
the following information in order to execute the task:
• FTP server's IP address (where the database is to be restored from)
• FTP server's login credentials
• Restore filename
• Confirm to restore
Note
Step 1
Step 2
After FTP credentials are provided, the entire database of the Cisco UCS Director appliance is restored
from the specified FTP location. You can then start the Cisco services by choosing Start Services.
From the Cisco UCS Director Shell Menu choose option Restore Services.
Press Enter.
The following information displays:
Restore database......
Restore will recover file from an FTP server. Provide the necessary access credentials
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
15
Using Shell Commands
Enabling the Database for BMA
FTP Server IP Address:
FTP Server Login: root
FTP Server Password:
Step 3
Step 4
Step 5
Step 6
Step 7
Enter your FTP server IP address and press Enter.
Enter your FTP server login and press Enter.
Enter your FTP server password and press the Enter.
Follow the onscreen prompts to complete the process.
Choose option Start Services to restart the Cisco services.
Enabling the Database for BMA
You can enable remote database access for the BMA appliance by choosing Enabling the Database for BMA.
Note
Step 1
This option is required for configuration of the Cisco UCS Director appliance with the BMA appliance.
From the Cisco UCS Director Shell menu chooseEnabling the Database for Cisco UCS Directory Baremetal Agent and
press Enter.
The following information is displayed:
Do you want to enable 'remote database' access for Cisco UCS Director Baremetal Agent [y/n]? y
Cisco UCS Director Baremetal Agent Hostname/IP Address: 192.168.0.241
Step 2
Choose y and press Enter.
The following information is displayed:
Cisco UCS Director Baremetal Agent Hostname/IP Address: 192.0.2.0
Enabling 'remote database' access for 192.0.2.0
Enabling remote database access to 192.0.2.0
About to enable remote access to database - please be catious that this is only supported for Cisco
UCS Director Baremetal Agent
About to enable remote access to database (192.0.2.0) please be catious that this is only supported
for Cisco UCS Director
Baremetal Agent
INFO (DBEnableRemoteAccess.java:195) About to enable remote access to database (192.0.2.0) please
be catious that this is
only supported for Cisco UCS Director Baremetal Agent
Remote DB access enabled
INFO (DBEnableRemoteAccess.java:213) About to enable remote access to datbase - please be catious
that this is only supported
for Cisco UCS Director Baremetal Agent
flushPrivileges - About to enable remote access to database - please be catious that this is only
supported for Cisco UCS
Director Baremetal Agent
INFO (DBEnableRemoteAccess.java:119) flushPrivileges - About to enable remote access to database please be catious that
Cisco UCS Director Shell Guide, Release 4.1
16
OL-30565-04
Using Shell Commands
Importing Certificates
this is only supported for Cisco UCS Director Baremetal Agent
Enabled 'Remote' database access
INFO (DBEnableRemoteAccess.java:219) Enabled 'Remote' database access
Sucessfully added credential for ipAddress 192.0.2.01
flushPrivileges - About to enable remote access to database - please be catious that this is only
supported for Cisco UCS
Director Baremetal Agent
INFO (DBEnableRemoteAccess.java:119) flushPrivileges - About to enable remote access to database please be catious that
this is only supported for Cisco UCS Director Baremetal Agent
Enabled 'Remote' database access for: 192.0.2.0
INFO (DBEnableRemoteAccess.java:679) Enabled 'Remote' database access for: 192.0.2.0
Completed remote database access...
Press return to continue ...
Step 3
Press Enter to return to the main menu.
Importing Certificates
This section describes how to import certification authority (CA) certificates. Both the Java KeyStore (JKS)
and Privacy-enhanced Electronic Mail (PEM) certificates are utilized. A JKS certificate is a repository of
security certificates used in SSL encryption. A PEM file is a container format that may include just the public
certificate or may include an entire certificate chain that includes a public key, private key, and root certificates.
Importing a CA Certificate (JKS) File
You can import a CA signed certificate file by choosing option 12, Importing a CA Certificate (JKS) file.
Step 1
From the Cisco UCS Director Shell Menu choose option 12 and press Enter.
The following information is displayed:
Import CA signed certificate from URL.
E.g. URL --> http://host:port/cert.jks
URL:
Step 2
Enter your URL that points to the CA signed certificate file and press Enter.
Importing a CA Certificate (PEM) File for VNC
You can import a CA signed certificate (PEM) file by choosing Import CA Certificate (PEM) File for VNC.
Step 1
From the Cisco UCS Director Shell menu choose Import CA Certificate (PEM) File for VNC and press Enter.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
17
Using Shell Commands
Accessing Root Privileges
The following information is displayed:
Import CA signed certificate (in PEM format) from URL.
E.g. URL --> http://host:port/cert.pem
URL:
Step 2
Enter your URL that points to the CA signed certificate (PEM) file and press Enter.
Accessing Root Privileges
This section describes how to access root. Tasks that require root privileges include moving directories or
files into other directories, providing or revoking user privileges, general system repairs, and occasionally
installing applications.
Note
Compiling software as root is not recommended for security reasons.
Enabling Root Access
You can enable root privileges by choosing Manage Root Access.
Step 1
From the Cisco UCS Director Shell Menu chooseManage Root Access and press Enter.
The following information displays:
Enable/Disable/Configure (root privalege) [e/d/c]:
Step 2
Enter e and press Enter.
The following information is displayed:
Do you want to Enable Root Access [y/n]? :
Step 3
Enter y and press Enter.
The following information is displayed:
Enabling root access...
Unlocking password for user root.
passwd: Success.
Root access enabled successfully
Press return to continue
Step 4
Press Enter to return to compete the process.
Cisco UCS Director Shell Guide, Release 4.1
18
OL-30565-04
Using Shell Commands
Disabling Root Access
Disabling Root Access
Choose this option to disable root privileges.
Step 1
From the Cisco UCS Director Shell menu choose Manage Root Access and press the Enter key.
The following information displays:
Enable/Disable/Configure (root privalege) [e/d/c]:
Step 2
Enter d and press the Enter key.
The following information displays:
Do you want to Disable Root Access [y/n]? :
Step 3
Enter y and press the Enter key.
The following information is displayed:
disabling root access...
Locking password for user root.
Passwd: Success
Root access disabled sucessfully
Press return to continue...
Step 4
Press the Enter key to return to the main menu.
Configuring Root Access
You can enable root privileges by choosing Manage Root Access.
Step 1
From the Cisco UCS Director Shell choose Manage Root Access and press Enter.
The following information is displayed:
Enable/Disable/Configure (root privalege) [e/d/c]:
Step 2
Enter c and press Enter.
The following information is displayed:
Do you want to Configure/Set Root Privilege/Password [y/n]? :
Step 3
Enter y and press Enter.
The following information is displayed:
Changing root password...
Changing password for user root.
New UNIX password:
Step 4
Enter a new UNIX password and press Enter.
The following information is displayed:
Retype new UNIX password:
Step 5
Enter your new UNIX password and press Enter.
The following information displays:
passswd: all authentication tokens updated successfully.
Root passwd changed successfully
Press return to continue...
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
19
Using Shell Commands
Logging in as Root
Step 6
Press Enter to complete the process.
Logging in as Root
You can login in as root by choosing Login As Root.
Step 1
From the Cisco UCS Director Shell Menu chooseLogin As Root and press Enter.
The following information is displayed:
Do you want to
Step 2
Login As Root [y/n]? :
Enter y and press Enter.
The following information is displayed:
Logging in as root
password:
Step 3
Enter your root password and press Enter.
The following information is displayed:
Logging as root
Password:
[root@localhost shelladmin]#
Step 4
Step 5
Enter your password and press Enter.
Enter exit to return to the shelladmin.
The following information is displayed:
[root@localhost shelladmin]# cd /opt
[root@localhost opt]# exit
exit
Sucessful login
Press return to continue ...
Using a Multi-Node Setup
The multi-node setup is supported for Cisco UCS Director on VMware vSphere only. With a multi-node
setup, you can scale Cisco UCS Director to support a larger number of VMs than is supported by a single
installation of Cisco UCS Director. This setup has the following nodes:
• One primary node
• One or more service nodes
• One monitoring database
• One inventory database
Cisco UCS Director Shell Guide, Release 4.1
20
OL-30565-04
Using Shell Commands
Database Nodes
Note
For a multi-node setup, you have to install the license on the primary node only.
A multi-node setup improves scalability by offloading the processing of system tasks, such as inventory data
collection, form the primary node to one or more service nodes. You can assign certain systems tasks to one
or more service nodes. The number of nodes determines how the processing of system tasks are scaled.
Node pools group service nodes and enable you to assign system tasks to more than one service node. If one
service node is busy when a system task needs to be run, Cisco UCS Director uses a round-robin assignment
to determine which service node should process the system task. If all, service nodes are busy, you can have
the primary node run the system task.
For more information about how to configure the primary node and service nodes, and how to assign system
tasks, see the Cisco UCS Director Administration Guide
Database Nodes
The inventory and monitoring databases are created from the Cisco UCS Director MySQL database. The data
that Cisco UCS Director collects is divided between the two databases. The multi-node setup segregates the
data collection which is historically very heavy on the database into a separate database.
Inventory Database
A multi-node setup can have only one inventory database. This database contains the following:
• Physical and virtual accounts and their related inventory data
• Data used in the normal operation of Cisco UCS Director for all supported features
Monitoring Database
A multi-node setup can have only one monitoring database. This database contains the data that Cisco UCS
Director uses for historical computations, such as aggregations and trend reports.
The parameters of the monitoring database depend upon the number of devices and VMs you plan to configure
and manage through Cisco UCS Director
Summary of Steps for Configuring a Multi-Node Setup
This procedure provides a high-level summary of the steps involved in configuring a multi-node setup.
Note
Step 1
Plan your multi-node setup carefully. You can only change a service node to a primary node. You cannot
change any other type of node after you configure it. For example, you cannot reconfigure a primary node
as a service node or an inventory database node as a monitoring database node.
Deploy a Cisco UCS Director VM for each node in the multi-node setup.
For more information, see the relevant installation and upgrade guide.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
21
Using Shell Commands
Creating the Inventory Database
For example, if your multi-node setup, includes a primary node, an inventory database, a monitoring database, and three
service nodes, deploy six Cisco UCS Director VMs.
Step 2
In the Cisco UCS Director shelladmin, configure the nodes in the following order:
1 Creating the Inventory Database, on page 22
2 Creating the Monitoring Database, on page 23
3 Creating the Primary Node, on page 23
4 Creating a Service Node, on page 24
You must create and start the inventory database and the monitoring database nodes before you configure the
primary node and any service nodes.
Update the license file in the Cisco UCS Director node that will be the primary node.
You do not need to update the license file on any other node.
Note
Step 3
See the "Updating the License" topic in the relevant installation and upgrade guide.
Step 4
In Cisco UCS Director on the primary node, configure the system tasks as follows:
a) Create one or more node pools if you want to control the assignment of system tasks by service node, or accept the
default node pool.
b) Create one or more system task policies if you want to control the assignment of system tasks by service node, or
accept the default task policy.
c) Configure the service nodes.
d) Configure the primary node.
e) Assign the system tasks to system policies if you want to control the assignment of system tasks by service node.
See the Cisco UCS Director Administration Guide.
Creating the Inventory Database
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the inventory database node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Inventory Database and press Enter.
Step 4
Step 5
When prompted, press Enter to continue.
To verify that the services for the inventory database are up and running, choose Display Services Status and
press Enter.
You should see the following lines:
2838 ?
3172 ?
00:00:00 mysqld_safe
3-02:51:38 mysqld
After you return to the shelladmin, the menu options change to those available for an inventory database node.
Cisco UCS Director Shell Guide, Release 4.1
22
OL-30565-04
Using Shell Commands
Creating the Monitoring Database
Creating the Monitoring Database
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the monitoring database node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Monitoring Database and press Enter.
Step 4
Step 5
When prompted, press Enter to continue.
To verify that the services for the monitoring database are up and running, choose Display Services Status
and press Enter.
You should see the following lines:
2838 ?
3172 ?
00:00:00 mysqld_safe
3-02:51:38 mysqld
After you return to the shelladmin, the menu options change to those available for a monitoring database node.
Creating the Primary Node
Before You Begin
The inventory and monitoring databases must be up and running before you create the primary node.
Note
Do not run any daemons on the primary database.
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the primary node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Primary Node and press Enter.
Step 4
At the Provide Inventory DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the inventory
database.
This step registers the VM as a primary node with the inventory database.
Step 5
At the Provide Monitoring DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the monitoring
database.
This step registers the VM as a primary node with the monitoring database.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
23
Using Shell Commands
Creating a Service Node
Step 6
Step 7
When prompted, press Enter to continue.
To verify that the services for the primary node are up and running, choose Display Services Status and press
Enter.
You should see the following lines:
Service
---------broker
controller
eventmgr
client
idaccessmgr
inframgr
TOMCAT
websock
Status
---------RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
PID
----25677
25715
25749
25808
25854
25911
25967
26009
Node Type : primary
Inventory DB( 172.29.109.135:3306 ) status
Monitor DB( 172.29.109.144:3306 ) status : UP
Press return to continue ...
: UP
After you return to the shelladmin, the menu options change to those available for a primary node.
Creating a Service Node
Before You Begin
The inventory and monitoring databases must be up and running before you create the primary node.
Step 1
Step 2
Log into the Cisco UCS Director shelladmin on the service node.
From the Cisco UCS Director Shell menu, choose Configure Multi-Node Setup and press Enter.
Step 3
From the menu, choose Configure Service Node and press Enter.
Step 4
At the Provide Inventory DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the inventory
database.
This step registers the VM as a service node with the inventory database.
Step 5
At the Provide Monitoring DB IP prompt, enter the IP address assigned to the Cisco UCS Director VM for the monitoring
database.
This step registers the VM as a service node with the monitoring database.
Step 6
Step 7
When prompted, press Enter to continue.
To verify that the services for the service node are up and running, choose Display Services Status and press
Enter.
Cisco UCS Director Shell Guide, Release 4.1
24
OL-30565-04
Using Shell Commands
Creating a Service Node
You should see the following lines:
Service
---------broker
controller
eventmgr
client
idaccessmgr
inframgr
TOMCAT
websock
Status
---------RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
PID
----25677
25715
25749
25808
25854
25911
25967
26009
Node Type : service
Inventory DB( 172.29.109.135:3306 ) status
Monitor DB( 172.29.109.144:3306 ) status : UP
Press return to continue ...
: UP
After you return to the shelladmin, the menu options change to those available for a service node.
Step 8
Repeat this procedure for every service node.
Cisco UCS Director Shell Guide, Release 4.1
OL-30565-04
25
Using Shell Commands
Creating a Service Node
Cisco UCS Director Shell Guide, Release 4.1
26
OL-30565-04