All services must be running before you start the upgrade procedure. If necessary, choose Start services and then verify that all services are running.

When all services are stopped, the upgrade continues.

For example, if you stored the patch file on an FTP server, enter ftp://username:password@hostname|IP_address/software_location_and_name

If the patch installation fails after the download because you did not add a second disk before the upgrade, do the following in your hypervisor manager:

1. Power off your Cisco UCS Director VM.

2. Add a second disk to the VM that meets the minimum requirements. See Database Disk Requirements. If you do not know the size of your current database, the upgrade message provides that information.

3. Power on your Cisco UCS Director VM.

After you have added the second disk, repeat this upgrade procedure, starting at step 1.

The upgrade process performs extra steps including the following:

• Unpacks the patch file.

• Installs the Release 6.5 files

• Formats the second database disk.

• Copies the existing database to the new disk.

• Initializes the database schema.

• Reboots the Cisco UCS Director appliance. The Cisco UCS Director services start automatically.

Depending upon the size of your database, the upgrade process can take several minutes to complete.

You can find the version and build in the following locations:

• Beneath the title of the Shell menu

• From the Show Version option in ShellAdmin

All services must be running before you start the upgrade procedure. If necessary, choose Start services and then verify that all services are running.

Ensure that all services are stopped on the primary and service nodes before you can upgrade the inventory and monitoring database nodes.

When all services are stopped on the database nodes, the upgrade continues.

For example, if you stored the software patch on an FTP server, enter ftp://username:password@hostname|IP_address/software_location_and_name

If the patch installation fails after the download because you did not add a second database disk to the inventory database and monitoring database nodes, do the following in your hypervisor manager:

1. Power off your Cisco UCS Director VM.

2. Add a second disk to the VM that meets the minimum requirements. See Database Disk Requirements. If you do not know the size of your current database, the upgrade message provides that information.

3. Power on your Cisco UCS Director VM.

When you have added the database disk, repeat this upgrade procedure, starting at step 1.

The upgrade process performs many steps including the following:

• Unpacks the patch file.

• Installs the Release 6.5 files

• Formats the second database disk.

• Copies the existing database to the new disk.

• Initializes the database schema.

• Reboots the Cisco UCS Director appliance. The Cisco UCS Director services start automatically.

Depending upon the size of your database, the upgrade process can take several minutes to complete.

If necessary, you can choose the Start Database option to start the services on the database nodes.

You can find the version and build in the following locations:

• Beneath the title of the Shell menu

• From the Show Version option in ShellAdmin

Username: root
Password: pxeboot

cd ucsd_bma_patch_6_5_0_0

setsebool -P samba_export_all_ro=1 samba_export_all_rw=1
find /opt/cnsaroot/templates/ -name "Win*" -exec ln -s '{}' /var/www/html/ \;

setsebool -P samba_export_all_ro=1 samba_export_all_rw=1
find /opt/cnsaroot/templates/ -name "Win*" -exec ln -s '{}' /var/www/html/ \;

If your system has more than one instance of Bare Metal Agent, you can identify the correct account by the IP address.

The PowerShell Agent is installed to the C:\Program Files (x86)\Cisco Systems\Cisco PSA Service folder. This folder is referred to as %AGENT_INSTALL_FOLDER% in the remainder of the document.

[root@localhost opt]# tar -zxvf script-analyzer.tgz -C csatool

The following files are unpacked into the csatool folder:

• data folder—This folder contains the API definition file in the JSON format. The Custom Task Script Analyzer uses this file to identify the methods that are not compatible with the methods of the current version.

• jre1.8.0_121 folder

• lib folder

• analyzer_config.properties file

• run-analyzer.sh file

• script-analyzer.jar file

# Path for the inframgr.jar file
inframgrJarPath=/opt/infra/inframgr/inframgr.jar
# Path for the lib directory where all dependencies could be found. 
# From Cisco UCS Director release 6.5,the libDirPath is /opt/infra/lib. 
# For releases prior to 6.5, the libDirPath is /opt/infra/inframgr.
libDirPath=/opt/infra/inframgr
# Path for the API definition file in the JSON format which is available in the data folder.
# For releases prior to 6.5, the inframgr_6500.json file is the API definition file.
# For the release 6.5.0.2, the inframgr_6502.json file is the API definition file.
inframgrJSONDefinitionPath=data/inframgr_6502.json
# Directory where the generated analysis report would be written
reportDirPath=output 
# Directory for the JavaScript files. The JavaScript files containing the 
CloupiaScripts are fetched using the --fetch-scripts command.
jsFileOrDirPath=javascripts
# JDBC connection URL
db.url=jdbc:mysql://localhost:3306/db_private_admin?verifyServerCertificate=false&useSSL=true
# Database user
db.username=root
# For releases prior to 6.5, use the default database password cloupia.
# For Cisco UCS Director release 6.5, use the reset MySql password. 
# You have to reset the database password in Cisco UCS Director Shell as a shell admin, after bringing up all the services and first successful login to Cisco UCS Director.
db.password=cloupia
# JDBC driver 
db.driver=com.mysql.jdbc.Driver

 [root@localhost csatool]# ./run-analyzer.sh --fetch-scripts

On execution of this command, you will get:

• JavaScript files for all CloupiaScripts in your custom tasks and any tasks that were created with the Execute Cloupia Script library task. The JavaScript files are saved along with the corresponding byte code text files in the javascripts folder identified in the jsFileOrDirPath key of the analyzer_config.properties file.

• The analysis report in the output folder identified in the reportDirPath key of the analyzer_config.properties file.

By default, these folders are created in /opt/csatool/, or whichever path you configured in the analyzer_config.properties file.

[root@localhost csatool]# ./run-analyzer.sh --file javascripts

This command generates an analysis report for all JavaScripts in the javascripts folder and saves the analysis report in the output folder as configured in the analyzer_config.properties file.

[root@localhost csatool]# ./run-analyzer.sh --file javascripts/Change_VM_Max_Boot_Wait_Time.js

Where, the Change_VM_Max_Boot_Wait_Time.js is a javascript file in the javascripts folder. This command generates an analysis report for the Change_VM_Max_Boot_Wait_Time.js in the javascripts folder and saves the analysis report in the output folder as configured in the analyzer_config.properties file.