Cisco Notification Alert -Cisco UCS Director - For Large Scale DC-01-Mar-2016 17:49 GMT

Feedback Sign Up Unsubscribe         Software Updates for UCS Director Product Name: UCS Director Express for Big Data 2.0 Software Type: UCS Director Virtual Appliance Software Release Version: 2 Alert Type: New File File Name: cucsde_bma_patch_5_4_0_2.zip File Description: Cisco UCS Director Baremetal Agent 5.4.0.2 Patch File Release Date: 03-FEB-2016 Find additional information in Software Downloads index. Software Updates for UCS Director Product Name: UCS Director 5.3 Software Type: UCS Director Virtual Appliance Software Release Version: 5 Alert Type: New File File Name: cucsd_patch_5_3_2_2.zip File Description: Cisco UCS Director 5.3.2.2 Upgrade Patch File Release Date: 26-FEB-2016 Find additional information in Software Downloads index. Software Updates for UCS Director Product Name: UCS Director 5.4 Software Type: UCS Director Virtual Appliance Software Release Version: 5 Alert Type: New File File Name: cucsd_patch_5_4_0_2.zip File Description: Cisco UCS Director 5.4.0.2 Upgrade Patch File Release Date: 02-FEB-2016 Find additional information in Software Downloads index. Known Bugs - UCS Director Alert Type: Updated * Bug Id: CSCux35070 Title: * Please verify this bug in 5.3.2.2 release CSCux35070 Status: Fixed Severity: 2 Severe Description: Symptom: Cisco Cloupia Unified Infrastructure Controller includes a version of java commons collections that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2015-6420 This product is affected by one of more of the listed CVE ids. Conditions: Exposure is not configuration dependent. Workaround: Not available. More-Info: PSIRT Evaluation: The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are: 7.5/7.1 http://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AV:N/AC:L/Au:N/C:C/I:C/A:C/E:H/RL:U/RC:C The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product. Additional information on Cisco's security vulnerability policy can be found at the following URL: http://www.cisco.com/web/about/security/psirt/security_vulnerability_policy.html Further Problem Description: Last Modified: 24-FEB-2016 Known Affected Releases: 5.4(0.0) Known Fixed Releases: Alert Type: New Bug Id: CSCuy33315 Title: View Details Options is not present for FC Ports of UCS Mini Status: Open Severity: 3 Moderate Description: Symptom: View Details Options is not present for FC Ports of UCS Mini Conditions: 1.Login into the UCSD 5.5 with Admin Credentials. 2. Add the UCS Mini Account under Administration -> Physical Accounts. 3. Select the Physical-> Compute -> Select the UCS Mini Account added 4. Select the Fabric Interconnect and select View Details 5. Navigate to Fiber Channel Ports. Workaround: Further Problem Description: Last Modified: 18-FEB-2016 Known Affected Releases: 5.5(0.0) Known Fixed Releases: Alert Type: New Bug Id: CSCuy33104 Title: Default cost Computation Period setting appear when Time lease disabled Status: Open Severity: 3 Moderate Description: Symptom: Default cost Computation Period setting appear when Time lease disabled Conditions: Uncheck Lease Time while creating service request Workaround: None Further Problem Description: Last Modified: 18-FEB-2016 Known Affected Releases: 5.4(0.2) Known Fixed Releases: Alert Type: New Bug Id: CSCuy35785 Title: VM Provision with non administrator user name is not working for win2k12 Status: Terminated Severity: 3 Moderate Description: Symptom: Windows 2008 and 2012 VM is not taking given user name in the HyperV deployment policy. VM will alway provision with user name "administrator" and with given password in the policy. Conditions: Workaround: None Further Problem Description: Windows 2008 and 2012 VM is not taking given user name in the HyperV deployment policy. Last Modified: 19-FEB-2016 Known Affected Releases: 5.3(2.2) Known Fixed Releases: Alert Type: New Bug Id: CSCuy39822 Title: Task Power On/Off CIMC Server 100% ends as failed Status: Open Severity: 3 Moderate Description: Symptom: When try to change power state (from On to Off, or from Off to On) of Cisco Rack server with the Power On/Off CIMC Server task it always ends with the error " Error while doing inventory collection, selectedContext=" and fails. But task execution actually makes a power state change on Rack server. Conditions: UCSD version 5.4.0.2. During worflow execution. Task - Power On/Off CIMC Server. Workaround: Don't do exit from task on failed condition. Further Problem Description: N/A Last Modified: 20-FEB-2016 Known Affected Releases: 5.4(0.2) Known Fixed Releases: Alert Type: New Bug Id: CSCux95093 Title: Evaluation of cloupia-cuic for NTP_January_2016 Status: Open Severity: 3 Moderate Description: Symptom: Cisco UCS Director includes a version of ntpd that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2015-7973, CVE-2015-7974, CVE-2015-7975, CVE-2015-7976, CVE-2015-7977, CVE-2015-7978, CVE-2015-7979, CVE-2015-8138, CVE-2015-8139, CVE-2015-8140, CVE-2015-8158 This product is affected by one of more of the listed CVE ids. Conditions: Device configured with NTP. Workaround: Not available. Further Problem Description: PSIRT Evaluation: The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are: 6.4/5.3 http://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AV:N/AC:L/Au:N/C:N/I:P/A:P/E:F/RL:OF/RC:C/CDP:N/TD:N/CR:L/IR:L/AR:L The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includ Last Modified: 23-FEB-2016 Known Affected Releases: 5.4(0.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy08435 Title: Workflows fail validation if changes ever made to Powershell Agent Status: Fixed Severity: 3 Moderate Description: Symptom: If a change is made to the Powershell Agent in a UCS Director 5.3.2.0 environment, any workflow that uses that PS agent subsequently fails validation after clicking the "Validate Workflow" button in "Workflow Designer", with a "Missing mandatory entry for: PowerShell Agent" red error message referring to an issue with the PS Agent for each task using it. Conditions: I reproduced the issue in my own UCS Director 5.3.2.0 environment by following all of the same steps as the customer with the same result. Workaround: Each workflow then has to be opened up followed by opening up the tasks and then clicking next through the task and submit for everything to work appropriately. Note: its not as if the PS Agent in the task needs to be reset as that had been tried with no different result. Further Problem Description: The customer views the issue as an annoyance that slows down work productivity. Last Modified: 24-FEB-2016 Known Affected Releases: 5.3(2.0) Known Fixed Releases: * 5.3(2.2) Alert Type: New Bug Id: CSCux74690 Title: Create VM Disk action is populating all datastores not assigned to vDC Status: Fixed Severity: 3 Moderate Description: Symptom: Create VM Disk action is populating all the datastore available in the vCenter. Conditions: Create VM Disk action on a VM Workaround: Further Problem Description: Last Modified: 04-FEB-2016 Known Affected Releases: 5.4(0.0) Known Fixed Releases: 5.4(0.2) Alert Type: Updated * Bug Id: CSCuy28778 Title: Verizon Global IP usage not cleaning up Status: Open Severity: 3 Moderate Description: * Symptom: Verizon can not deploy a Vm with the same IP when the previous VM was moved to the DMZ and re-IP'ed. The old IP stays in the Global IP Pool. it does find the VM with the new IP but does not delete the old IP in the POOL We need a SQL statement fast to clean certain IP's up. Conditions: Deploy vm re IP vm deploy vm #2 with same IP as VM #1 used to be... you will find the old IP entry still in the table and the deployment will fail with a cant allocate additional nic's and allocate IP... Workaround: need a sql statement super fast to clean up till resolved Further Problem Description: SR 680224668 opened for the global IP usage/reclaim issue. Last Modified: 15-FEB-2016 Known Affected Releases: 5.4(1.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy44778 Title: Create UCS Service Profile from Template append 1 to Service Profile Status: Open Severity: 3 Moderate Description: * Symptom: Appending prefix 1 to the Service Profile name Conditions: Using 'Create UCS Service Profile from Template task for creating Service Profile Workaround: None Further Problem Description: Last Modified: 29-FEB-2016 Known Affected Releases: 5.4(0.1) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy29334 Title: UCSD 5.4 does not detect VM's IP address info after VM deployment Status: Open Severity: 3 Moderate Description: * Symptom: Intermittently IP address of the VM is not detected in the Service Request log and Notification email. Conditions: Email notification of VM provisioning might have missing IP address information. Workaround: None Further Problem Description: Last Modified: 29-FEB-2016 Known Affected Releases: 5.4(0.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy12022 Title: Access profiles not allowing user to switch from default profile in UCSD Status: Open Severity: 3 Moderate Description: * Symptom: After selecting an alternative access profile and clicking on "re-login with profile", the interface logs into the default profile regardless of selection. Also, use is unable to change the default profile from the access profiles screen. Conditions: End user with multiple access profiles configured trying to switch between them in UCSD 5.4.0.1 Workaround: Request admin to change the default access profile for an end user. Further Problem Description: N/A Last Modified: 24-FEB-2016 Known Affected Releases: 5.4(0.1) Known Fixed Releases: Alert Type: New Bug Id: CSCuy46103 Title: CST Scirpt <- miss spelled Status: Open Severity: 3 Moderate Description: Symptom: CST Scirpt exited normally should say CST script exited normally Conditions: CST Scirpt exited normally should say CST script exited normally Workaround: CST Scirpt exited normally should say CST script exited normally Further Problem Description: CST Scirpt exited normally should say CST script exited normally Last Modified: 25-FEB-2016 Known Affected Releases: 5.4(0.2) Known Fixed Releases: Alert Type: New Bug Id: CSCuy47131 Title: VLAN and VLAN Mode are not listed on Rack Servers Status: Open Severity: 3 Moderate Description: Symptom: VLAN and VLAN Mode are not listed on Rack Servers Conditions: Workaround: NA Further Problem Description: Last Modified: 25-FEB-2016 Known Affected Releases: 5.5(0.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy33303 Title: Fabric Interconnect DN is missing under IO Modules of UCS Mini Status: Fixed Severity: 3 Moderate Description: * Symptom: Fabric Interconnect DN is missing under IO Modules of UCS Mini Conditions: 1. Login into the UCSD 5.5 with Admin Credentials. 2. Add the UCS Mini Account under Administration -> Physical Accounts. 3. Select the Physical-> Compute -> Select the UCS Mini Account added 4. Navigate to UCS Chassis Tab and select View Details. 5. Navigate to IO Modules Tab and find the details of Fabric Interconnect DN Workaround: NA Further Problem Description: FI DN level info cannot be shown at chassis level report. Hence FI DN is more granular at port level, so its been removed from IO Module Report. Last Modified: 29-FEB-2016 Known Affected Releases: 5.5(0.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy47107 Title: OVF Import to VMware Cloud task is failing with Java Heap Space error Status: Open Severity: 3 Moderate Description: * Symptom: OVF Import to VMware Cloud task is failing with Java Heap Space error Conditions: OVF Import to VMware Cloud task configured with OVF URL instead of Appliance storage Workaround: Instead of using external OVF URL, upload the OVF to UCSD - Appliance Storage and select the option "Select file from Appliance Storage' in the task. To upload the OVF - Administration --> Integration --> User OVF Management Further Problem Description: Last Modified: 29-FEB-2016 Known Affected Releases: 5.4(0.2) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy48966 Title: Resize VM Memory & CPU task throws string:'null', selectedContext=<None> Status: Fixed Severity: 3 Moderate Description: * Symptom: When 'Resize VM Memory and CPU task' is executed on a Powered-off VM (directly through VM console), the task is throwing below error: Add Additional CPU without Inventory (Resize VMware VM Memory and CPU) failed with error - For input string: 'null', selectedContext= Conditions: VM powered off directly from VM console or vCenter and UCSD does not know the VM current status. Workaround: To know the current status of the VM, Add VM Resync task before the Resize VM Memory and CPU task in the workflow. Further Problem Description: Last Modified: 29-FEB-2016 Known Affected Releases: 5.4(0.2) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCuy41966 Title: UCSD workflow SR# not present in UI when called via REST API Status: Terminated Severity: 3 Moderate Description: * Symptom: When calling a workflow via API/REST, the workflow SR# is not present in the 'organizations -> Service Requests' list. An SR# is created and can be accessed via REST but it is not listed in the GUI. This makes troubleshooting difficult and/or unusable. Conditions: It is believed to be expected behavior that when workflows are triggered from REST API then their respective SRs will not be shown on UCSD UI and only the SRs that are submitted from UI are shown in UCSD UI. There is also a belief that an enhancement request with the business unit to add the functionality of showing SRs submitted from REST API in the UCSD UI exists but was difficult to verify after searching. However, the bug is that the api allows invalid parent IDs which should error out. Workaround: The following method triggered a workflow from REST API to have it's respective SR displayed on UCSD UI and was satisfactory for the customer. 1.) Click "admin", or what ever the chosen name is at the top right and just to the left of "Log Out" , select the "Advanced" tab, click the "Enable Developer Menu" check box and click "Copy Key Value" to paste in the corresponding field for the X-Cloupia-Request-Key of a API browser add-on tool like PostMan or RESTful, or via the REST API Browser inside of UCSD. 2.) In "Policies", "Orchestration", "Rest API Browser" tab, search for the "userAPISubmitWorkflowServiceRequest" api name in the right hand search field. 3.) Expand the "ID" column in to fully view the entries in the "Legacy Tasks" folder and double click on the userAPISubmitWorkflowServiceRequest selection. 3.) At the "API Examples" tab of the next window, click the "Generate URL" 4.) Change all "sample" parts of the generated URL to the appropriately needed values and change the ending " 1000}" to " -1}" 5.) Copy the edited URL and paste it into a API browser add-on tool like PostMan or RESTful, or via the REST API Browser inside of UCSD to see the "serviceResult" value. 6.) Then navigate to "Organization" and "Service Request" in UCSD to see the same "serviceResult" value now in the UI. Further Problem Description: The customer viewed the issue as "Its just a completely unacceptable" and did not understand why workflows triggered from REST API do not display their respective SRs in the UCSD UI by default. Last Modified: 29-FEB-2016 Known Affected Releases: 5.4(0.1), 5.4(0.2) Known Fixed Releases: Alert Type: New Bug Id: CSCuy51536 Title: Create Device Cluster APIC task missing "Service Type" input Status: Open Severity: 3 Moderate Description: Symptom: When trying to create a L4-7 device with the Create Device Cluster APIC task in UCSD, the device is created with the default Service Type: Other, which is incorrect. The following fault will be displayed on APIC: dn="uni/tn-Gold-Test/lDevVip-T-BIGIP-VE-01/vnsConfIssue-function-type-mismatch-failure/fault-F1690" descr="Configuration is invalid due to invalid function type" Input for the L4-7 service type is missing from the task and cannot be set. Conditions: UCSD 5.4.0.2 APIC 1.2(1k) Issue happens each time Create Device Cluster task is executed. Workaround: No workarounds available. Further Problem Description: N/A Last Modified: 29-FEB-2016 Known Affected Releases: 5.4(0.2) Known Fixed Releases: Alert Type: New Bug Id: CSCuy47173 Title: UCSD fails to list the Battery status of storage controller Status: Open Severity: 4 Minor Description: Symptom: UCSD fails to list the Battery status of storage controller Conditions: 1. Add the Rack Server Account UCS C3160 to the UCSD. 2. Perform the inventory collection and add the rack server to the default POD. 3. Navigate to Physical -> Default Pod -> Rack Server. 4. Select the Rack Server and view Details. 5. Select the Storage Adapters. 6. The Battery Status is listed as NA Workaround: NA Further Problem Description: Last Modified: 25-FEB-2016 Known Affected Releases: 5.5(0.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCux49156 Title: UCSD unable to get UCS Central WWPN's / MAC's in time during a workflow Status: Fixed Severity: 6 Enhancement Description: Symptom: Global WWPNs and MACs are not showing up as actual values inside of a workflow in UCSD Conditions: When creating a Global Service profile in UCS central from UCS Director the WWPNs or MAC addresses from the service profile dont show up as valid outputs with actual values and instead show as "derived" . This makes them unusable for any task that relies on that output. For e.g. when running a workflow that needs to use WWPNs for zoning or masking later on cannot use "derived" and instead needs the actual value. Workaround: None other than downgrading UCS Central to 1.2.x version Further Problem Description: Last Modified: 29-FEB-2016 Known Affected Releases: * 5.4(1.0), 5.5(0.0) Known Fixed Releases: Alert Type: Updated * Bug Id: CSCux94195 Title: N5K: 5.2(1)N1(8b) and 5.2(1)N1(9) versions support Status: Fixed Severity: 6 Enhancement Description: Symptom: Only two releases of 5.2(1)N1(4) (N5548) and 6.0(2)N2(5) (N5548 and N5596) NX-OS for N5K are supported Conditions: The customer is using 5.2(1)N1(8b) and 5.2(1)N1(9) and there would be difficulty in upgrading to 6.0.x. Workaround: None that I know of. Further Problem Description: The customer wants to know if there Is there a specific reason why only two releases are supported? Last Modified: 24-FEB-2016 Known Affected Releases: 5.3(2.0) Known Fixed Releases: * 5.3(2.2) Find additional information in Bug Search index.   2015 Cisco and/or its affiliates. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks