ucs healthchecks

[ravianilkhanna]

Hi All,

Can anyone help me through Cisco UCS healthchecks?

I have gone through the "UCS_Health_Check_Offline_v2.3" script but it is not working in my environment as i am not able to connect to UCS machine through that script. Would request you to please help for the same.

Thanks,

Ravi Khanna

[johnd0e88]

Simply saying "it's not working" will not help anyone help you.

Please provide the error you're receiving when trying to connect to your UCS.

[tcerling]

Could you please provide us with some more information?  What is the operating system on which you are running this script?  Can you connect manually (Connect-Ucs) from this system to your UCS environment?  What version of UCS PowerTool do you have installed on your system?  What error messages are you receiving when you try to run the script?  What parameters did you pass the script on the command line used to execute the script?  Think of the things you would like to know if someone were to come to you asking for assistance.  Those are the sort of things we need in order to provide assistance.

[ravianilkhanna]

Hi Timothy,

Appriciate your kind and prompt response.

FYI, I am using Windows 2008 R2 64 Bit platform. I am using Cisco power tool version : 2.0.1.5, Please note I am able to run the script but not able to connect to UCS server via PowerShell. I have tried using the url to connect through UCS via web browser & I am able to connect. Is there anything I am missing to connect via PowerShell console? To run your script is there any other steps to follow?

I am getting the below error “ Error connecting to UCS Domain. Please enter to retry or M to return to Main Menu:”

• <https://communities.cisco.com/servlet/JiveServlet/showImage/105-24219-94629/pastedImage_0.png>

Thankyou once again for your kind response.

Thanks,

Ravi Khanna

[tcerling]

Okay.  The script you are running was written a while ago.  Since then, there have been some changes to our PowerTool modules.  The biggest change is that with version 2, the naming convention on the module name changed.  Prior to version 2, the name of the UCS Manager PowerTool module was 'CiscoUcsPs'.  The name has been changed to Cisco.UcsManager.  I am assuming the script you are running is the one you downloaded from UCS HealthCheck v2.3.  That script was written before the release of PowerTool version 2.  Therefore, you will need to change every occurrence of 'CiscoUcsPs' to 'Cisco.UcsManager' within the script.  It should then load the proper module so you should be able to execute the script.  (If that is not the script you are running, please provide a link to the script so I can assist).

Another note... if you had installed a previous version of UCS PowerTool before installing version 2, you need to uninstall the previous version.  In fact, if you did have a previous version installed, it would be safest to uninstall any versions of UCS PowerTool you may have installed and then re-install version 2.  If the previous versions were not uninstalled, it is possible to use a cmdlet from the wrong module, and in a few rare cases that can cause issues.  Better safe than sorry.  The installation of PowerTool also changes the Windows PATH variable.  By uninstalling and reinstalling just version 2, you should end up with the properly defined PATH variable.

Once you have gotten PowerTool version 2 properly installed, and the script changed, you should be ready to go.  Before running the script, though, you can easily test if you have proper access to UCS via PowerTool from a PowerShell window.  Launch PowerShell and execute the following cmdlets:

Import-Module Cisco.UcsPowerTool

Connect-Ucs -Name <ipaddress>

where <ipaddress> is the IP address or DNS name of your UCS Manager.  It should prompt you for your credentials and then connect you to UCS Manager if you have access.  If this test is not successful, we need to resolve your access issue before you can run the health check script.  The Import-Module Cisco.UcsManager cmdlet needs only be executed once for each PowerShell session.  On my systems, I place the cmdlet into my PowerShell profile so I don't have remember to execute it.

[ravianilkhanna]

Hi Timothy,

I am again thankful for your prompt support.

I have implemented the changes as you have asked me to do so. ( “change every occurrence of 'CiscoUcsPs' to 'Cisco.UcsManager' within the script”) have been modified.

Another note: I have installed the latest version of UCS Power Tool. I have not installed any older instance. Prior installing the power tool.

But it seems, I am still not able to connect to ucs via powershell.

I am getting the below error

cmdlet Connect-Ucs at command pipeline position 1

Supply values for the following parameters:

Credential

Connect-Ucs : Connect-Ucs: ... 551:Authentication failed. <--

At line:1 char:1

+ Connect-Ucs -Name ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: ( , Exception

+ FullyQualifiedErrorId : Cisco.Ucsm.Cmdlets.ConnectUcs

Please note: ... - I have replace the ip address for security reasons.

I am getting the authentication error. Which I should not get as I am using ad account to connect to ucs. Just for my knowledge “Can I use AD credential or should I use local credential” to connect to cisco ucs.

Thanks,

Ravi Khanna

[tcerling]

"Can I use AD credential or should I use local credential” to connect to cisco ucs."

That depends upon how you have configured your UCS Manager.  If it is configured for AD authentication, and you have access to AD account that has access, then you can use those credentials.  Remember that you need to specify the AD domain with the user name, e.g. 'domain\user.  If your UCS is not configured for AD authentication, you will need to use local account.

Just to eliminate the basic ... Can you ping the UCS Manager address you are using when trying to connect?

[ravianilkhanna]

Hi Timothy,

Thanks for the prompt response. I shall check through AD credentials again.

☺ Cheers

Thanks,

Ravi Khanna

[ravianilkhanna]

Hi Timothy,

Thanks for the prompt response. I shall check through AD credentials again.

☺ Cheers

Thanks,

Ravi Khanna

[ravianilkhanna]

Hi Timothy,

I am able to generate report but it is blank. Can you please help.

UCS Health Check Report<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html>

10/25/2015

UCS Domain

• System<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#System>

• Inventory<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Inventory>

• Policies<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Policies>

• Pools<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Pools>

• Service Profiles<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Profiles>

• LAN<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#LAN>

• SAN<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#SAN>

• Fault Summary<file:///
  srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Faults>

Status

Fault Summary

8

20

30

100

Virtual IP:

UCSM Version:

HA Ready:

Backup Policy:

Config Export Policy:

Call Home State:

Chassis Power Statistics<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Chassis-Power-Collapse>

Dn

Input Pwr

Input Pwr Avg

Input Pwr Max

Output Pwr

Output Pwr Avg

Output Pwr Max

Suspect

Server Power Statistics<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Server-Power-Collapse>

Dn

Consumed Pwr

Consumed Pwr Avg

Consumed Pwr Max

Input Current

Input Current Avg

Input Voltage

Input Voltage Avg

Suspect

Server Temperature Statistics<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Server-Temp-Collapse>

Dn

Sensor-1

Sensor-1 Avg

Sensor-1 Max

Sensor-2

Sensor-2

Sensor-2

Suspect

Fabric Interconnects<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#collapse1>

Fabric ID

Cluster Role

Model

Serial

System

Kernel

IP

Ports Used

Ports Licensed

Operability

Thermal

Chassis<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Chassis-Collapse>

ID

Model

Serial

Status

Operability

Power

Power Redundancy

Thermal

PSUs

Slots Used

Slots Available

IOMs<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#collapse2>

Chassis

Fabric ID

Model

Serial

Channel

Running Firmware

Backup Firmware

Blades<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#collapse3>

Dn

Chassis

Slot

Model

Serial

Service Profile

CPU

Cores

Threads

Memory (GB)

BIOS

CIMC

Status

Rack Servers<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#collapse4>

Rack ID

Model

Serial

Service Profile

CPU

Cores

Threads

Memory (GB)

Speed

BIOS

CIMC

Rack Adapters<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#collapse5>

Rack ID

Slot

Model

Serial

Running FW

System Policies<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#SystemPoliciesCollapse>

DNS Servers:

Chassis Discovery Action:

Chassis Discovery Grouping:

Timezone:

NTP Servers:

Chassis Power Redundancy:

Default Maintenance Policy:

Maintenance Policies<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Maintenance-Policy-Collapse>

Name

Dn

Reboot Policy

Description

Schedule

Host Firmware Packages<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Host-FW-Collapse>

Name

Blade Bundle Version

Rack Bundle Version

LDAP<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#LDAP-Collapse>

Providers

Hostname

Root DN

Base DN

Attribute

Group Maps

Name

Roles

Locales

Mgmt IP Pool<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#MgmtPoolCollapse>

Pools

From

To

Size

Assigned

Allocations

Dn

IP

Subnet

Default Gateway

UUID Pools<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#UUID-Collapse>

Pools

Dn

Name

Assignment Order

Prefix

Size

Assigned

Allocation

Assigned To Dn

Id

Server Pools<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Server_Pools-Collapse>

Pools

Dn

Name

Size

Assigned

Allocation

Assigned To Dn

Name

MAC Pools<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Pools-Mac-Collapse>

Pools

Name

From

To

Size

Assigned

Allocations

ID

Assigned

Assigned To

IP Pools<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Pools-Ip-Collapse>

Pools

Name

From

To

Size

Assigned

Allocations

ID

Assigned

Assigned To

WWN Pools<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Pools-Wwn-Collapse>

Pools

Name

From

To

Size

Assigned

Allocations

ID

Assigned

Assigned To

Type: N/A

Dn

Service Profile

User Label

Assigned Server

Association State

Maint Policy

FW Policy

BIOS Policy

System QoS<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Lan-Qos-Collapse>

Priority

Enabled

CoS

Packet Drop

Weight

Weight(%)

MTU

Multicast Optimized

VLANs<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Lan-Vlan-Collapse>

Name

ID

Fabric ID

Type

Transport

Native

VLAN Sharing

Primary VLAN

Multicast Policy

LAN Uplinks<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Lan-Uplinks-Collapse>

Fabric

Port

MAC

If Type

Speed

Xcvr

Avg Mbps Rx

Avg Mbps Tx

Status

State

Server Links<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Lan-ServerPorts-Collapse>

Fabric

Port

MAC

If Type

Speed

Xcvr

Avg Mbps Rx

Avg Mbps Tx

Status

State

Network Control Policies<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Lan-Control-Collapse>

Name

DN

Description

Owner

CDP

MAC Register Mode

Action on Uplink Fail

QoS Policies<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#Lan-QosPolicy-Collapse>

Name

Owner

Priority

Burst

Rate

Host Control

VSANs<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#San-Vsan-Collapse>

ID

Name

Fabric ID

FCoE VLAN

If Role

Transport

Zoning State

FC Uplink Ports<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#San-UplinkFcPorts-Collapse>

Fabric

Port

WWN

Mode

Speed

Xcvr

Avg Mbps Rx

Avg Mbps Tx

Status

State

FCoE Uplink Ports<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#San-UplinkFcoePorts-Collapse>

Fabric

Port

MAC

If Type

Speed

Xcvr

Avg Mbps Rx

Avg Mbps Tx

Status

State

Storage Ports<file:///
srv10177\TEMPKHRAV$\Desktop\vmware%20script\new%20healthcheck\health.html#San-StoragePorts-Collapse>

Fabric

Port

MAC

If Type

Speed

Xcvr

Avg Mbps Rx

Avg Mbps Tx

Status

State

Fault Summary

Severity

Description

Affected Object

Date Created

Thanks,

Ravi Khanna

[ravianilkhanna]

Hi Timothy,

I Got it!! Thanks a ton!!!! I have to just save the file to the same location to work it.

I have some modules which are black but most of them are coming in report.

Thanks for your support all long.. ☺ You have made my day today!!!

A Big Thankyou to you !!! Cheers ☺☺☺

Thanks,

Ravi Khanna

[tcerling]

You are welcome.  Glad I could help out.

[ravianilkhanna]

Hi Timothy,

Last help needed, how to get current date and time for this report. It shows old date. I have checked on line no 78 and replaced it with string “DATE_REPLACE” but no luck.

Can you please help on the same.

Thanks,

Ravi Khanna

[tcerling]

Ravi,

I am not the author of the script, nor am I an HTML coder.  But from what I can read in the script, it looks like it can create a new report every time the report is run.  It looks like it stores UCS_Report_MM_dd_yy_HH_mm_ss.html in the local directory if you request the report to be run in silent execution mode.

[dbelcher]

This " Therefore, you will need to change every occurrence of 'CiscoUcsPs' to 'Cisco.UcsManager' within the script.  It should then load the proper module so you should be able to execute the script." worked for me.