Known Bugs - Prime Data Center Network Manager
| | |
Alert Type: | Updated * | Bug Id: | CSCum62685 | Title: | Blank screen on DFA topology after POAP publish | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
From POAP definitions, if user edits a definition, goes through all the steps, and finally publishes it, and then tries to go to DFA topology, the screen becomes blank and unresponsive.
The same issue happens when POAP definition is saved and published, then navigated to DFA screen.
Conditions:
The POAP definition is saved/edited and published and the user goes to DFA topology screen.
Workaround:
Doing a browser reload (clicking the reload button on the browser being used) fixes the issue.
Further Problem Description:
| |
Last Modified: | 13-JAN-2016 | |
Known Affected Releases: | 7.0(1)S24 | |
Known Fixed Releases: * | 6.2(11)FI(0.8), 6.2(11)S2, 6.2(11.1)S0, 6.2(13)FM(0.13), 6.2(13)GS(0.13), 6.3(1.7)S0, 7.0(0)BZ(0.98), 7.0(1.26)S0, 7.2(0)FM(0.2), 7.3(0)D1(0.71) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCur96084 | Title: | N5K-56XX devices are not listed in config template | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
When the templates supported platform is N5600, no N56** device types are listed for config delivery
Conditions:
N56** device types are discovered and managed
Workaround:
Add N5500 to the templates supported platform and save the template. Now select the template and try creating a config delivery job in the web client, the N56** devices should be available for selection.
Further Problem Description:
| |
Last Modified: | 13-JAN-2016 | |
Known Affected Releases: | 7.1(0.46) | |
Known Fixed Releases: * | 6.2(11.4)S0, 6.2(13)FM(0.33), 6.2(13)GS(0.13), 7.0(0)BZ(0.98), 7.1(0.207)S0, 7.2(0)FM(0.2), 7.3(0)D1(0.71), 7.3(0)DHB(0.31), 7.3(0)DX(0.16), 7.3(0)EG(0.3) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuu75865 | Title: | Add global vlan profile subtype | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Changes made to Network based on Global-Vlan-Profile (no segment ID) are not refreshed on switches
Conditions:
Network created with a copy of "defaultNetworkUniversalTfGblVlanProfile" e.g. "defaultNetworkUniversalTfGblVlanProfile2"
Segment ID is configured but not used in profile.
Workaround:
Rename the profile to end with 'GblVlanProfile' (case-insensitive), e.g. 'customizedGblVlanProfile'. The network refresh will then use VLAN ID instead of Segment ID for customized global VLAN profile.
Further Problem Description:
This bug will support fully customized Global-Vlan-Profile names, as the trigger for refreshment is based on the profile subtype
| |
Last Modified: | 14-JAN-2016 | |
Known Affected Releases: | 7.2(0.39) | |
Known Fixed Releases: * | 7.0(0)BZ(0.98), 7.2(1.22)S0, 7.2(1.23)S0, 7.3(0)D1(0.140), 7.3(0)DX(0.25), 7.3(0)GLF(0.25), 7.3(0)IB(0.122), 7.3(0)OTT(0.73), 7.3(0)PDB(0.102), 7.3(0)RTG(0.115) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCut48826 | Title: | Notify Border Leaf option on BL/ER pairing is cleared in remote DB case | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
"Notify Border Leaf when relevant partitions are changed" checkbox is always cleared and the leafs do not get their configuration updated.
Conditions:
Happens when DCNM is configured with Oracle DB and partitions are extended.
Workaround:
'Manually run cli "fabric database auto-pull dci vrf VFRName node-id borderLeafIP peer-id edgeRouterIP" on the border leafs.
Further Problem Description:
| |
Last Modified: | 13-JAN-2016 | |
Known Affected Releases: | 7.1(1.81) | |
Known Fixed Releases: * | 6.2(13)FM(0.54), 6.2(13)GS(0.15), 6.2(13.1)S0, 7.0(0)BZ(0.98), 7.1(1.91)S0, 7.2(0.5)S0, 7.3(0)D1(0.71), 7.3(0)DHB(0.31), 7.3(0)DX(0.16), 7.3(0)EG(0.3) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv63735 | Title: | Topology Map not appearing correctly | |
Status: | Fixed | |
Severity: | 4 Minor | Description: | Symptom:
Topology map of SAN client shows a small dot in the upper left corner.
Conditions:
Hide Unselected VSAN Members is being used when viewing maps of VSANs.
Workaround:
If a map file from a working user is copied over to the non-working user, the non-working user can then see the map.
Alternatively, if pressing the layout button does not correct the map, setting log level to ALL before pressing the layout button worked. Set log level to All for
com.cisco.dcbu.lib.map
com.cisco.dcbu.sm.client.map
then press the layout button. NOTE this will increase data written to fm.log so change log level back to WARN afterwards.
Further Problem Description:
The bad map files (located in C:\Program Files\Cisco Systems\dcm\fm\db\) will have large negative coordinates such as (-2147483648, -2147483648)
| |
Last Modified: | 14-JAN-2016 | |
Known Affected Releases: | 7.1(2) | |
Known Fixed Releases: * | 7.0(0)BZ(0.98), 7.2(1.45)S0, 7.3(0)D1(0.140), 7.3(0)DX(0.25), 7.3(0)GLF(0.25), 7.3(0)IB(0.122), 7.3(0)OTT(0.73), 7.3(0)PDB(0.102), 7.3(0)RTG(0.115), 7.3(0)SC(0.14) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCux46475 | Title: | enum in @(IsMandatory=false) MACRO doesn't work with DCNM CLI templates | |
Status: | Open | |
Severity: | 4 Minor | Description: * | Symptom:
POAP template enum doesn't work with CLI template.
ex:@(IsMandatory=false, Enum="shut, no shut", DisplayName="shut or no shut", Description="shut or no shut")
enum doesn't work when use it in CLI template
but the following way works,
enum ADMIN_STATE {
validValues = shutdown, no shutdown;
};
Conditions:
DCNM CLI templates
Workaround:
do not use enum part of @(IsMandatory=false) macro.
use enum seprately,
enum ADMIN_STATE {
validValues = shutdown, no shutdown;
};
Further Problem Description:
| |
Last Modified: | 21-JAN-2016 | |
Known Affected Releases: | 7.2(2)ZN(99.9) | |
Known Fixed Releases: | | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCux05562 | Title: | Add option to clear networks from switch when deleting them from DCNM | |
Status: | Fixed | |
Severity: | 6 Enhancement | Description: | Symptom:
When deleting a network from DCNM we should automatically go in and delete the network from all switches
Conditions:
none
Workaround:
Delete network from DCNM and manually issue "clear fabric database host" on the switches
Further Problem Description:
| |
Last Modified: | 23-JAN-2016 | |
Known Affected Releases: | 7.2(2) | |
Known Fixed Releases: * | 7.2(2.74)S0, 7.3(0)ZD(0.236), 7.3(1)D1(0.2) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv49839 | Title: | Partition ID should be configurable | |
Status: | Fixed | |
Severity: | 6 Enhancement | Description: | Symptom:
Partition ID should be configurable and go along with the VRF/VLAN/L3VNI pool requirement
Conditions:
new install with default values
Workaround:
none
Further Problem Description:
| |
Last Modified: | 14-JAN-2016 | |
Known Affected Releases: | 7.2(1) | |
Known Fixed Releases: * | 7.0(0)BZ(0.98), 7.2(2.14)S0, 7.2(2.38)S0, 7.2(2.40)S0, 7.2(2.52)S0, 7.3(0)D1(0.140), 7.3(0)D1(0.156), 7.3(0)D1(0.179), 7.3(0)DX(0.25), 7.3(0)GLF(0.25) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCup27841 | Title: | vcenter 5.5 registration fails due to improper certs | |
Status: | Fixed | |
Severity: | 6 Enhancement | Description: | Symptom:
vcenter 5.5 registration fails in 6.3.1 due to checksum on certs.
need an option to ignore certs
Conditions:
Wireshark capture will show the VCenter certificate error.
Workaround:
Apply a valid certificate
Further Problem Description:
| |
Last Modified: | 13-JAN-2016 | |
Known Affected Releases: | 6.3(1) | |
Known Fixed Releases: * | 6.2(10)CR(0.14), 6.2(10.7)S0, 6.2(11)FM(0.7), 6.2(12)BFP(0.13), 6.2(12)FM(0.5), 6.2(8)TS(0.28), 6.3(2)S47, 7.0(0)BZ(0.98), 7.1(0.39)S0, 7.3(0)D1(0.71) | |
|
| |
|
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论