| |
|
Alert Type: | Updated * |
Bug Id: | CSCus29299 | Title: | system dyn vlan should be mutually exclusive with global Mobility domain |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
VDP detection on nexus 5600 does not function
Conditions:
When the Global Mobility Domain detectable VLAN range is set with overlapping values of the system dynamic VLAN range
Workaround:
Set the Global Mobility Domain detectable VLAN range to be non-overlapping.
Further Problem Description:
|
|
Last Modified: | 03-SEP-2015 |
|
Known Affected Releases: | 7.1(1)S19 |
|
Known Fixed Releases: * | 7.1(1.96)S0, 7.3(0)SL(0.106), 7.3(0)ZD(0.83) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv58513 | Title: | Error seein in Selective HA upgrade from a standalone system |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Selective HA setup completes, but reports some errors and the Fabric General settings page is missing the peer LDAP IP address.
Conditions:
Install 2 DCNM 721 instances to setup a Selective HA setup.
Restore the backup from a DCNM 712 standalone on this.
Now try to setup the Selective HA, and the installation is mostly complete, however there is a duplicate DB insert error.
Workaround:
cd /usr/local/cisco/dcm/db/bin
./psql -Udcnmuser dcmdb
password --
Run the following commands:
> update svr_prop set value='' where key='dfa.ldapPeerPassWord';
> update svr_prop set value='cn=admin,dc=cisco,dc=com' where key='dfa.ldapPeerUserName';
> update svr_prop set value='eth1-ip-address-of-peer' where key='dfa.ldapPeerServer';
> update svr_prop set value='auto-config' where key='dfa.selectiveHAFeature';
Further Problem Description:
|
|
Last Modified: | 12-SEP-2015 |
|
Known Affected Releases: | 7.2(1) |
|
Known Fixed Releases: * | 7.2(1.82)S0 |
|
|
| |
| |
|
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: | 05-SEP-2015 |
|
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.1(1.91)S0, 7.2(0.5)S0, 7.3(0)D1(0.71), 7.3(0)DHB(0.31), 7.3(0)FM(0.4), 7.3(0)HM(0.5), 7.3(0)MMD(0.9) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub00716 | Title: | DCNM: TLS1.0/SSL3.0 Information Disclosure Vulnerability (CVE-2011-3389) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Cisco DCNM includes a version of OpenSSL that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures
(CVE) IDs:
CVE-2011-3389 and CVE-2008-5161
This bug was opened to address the potential impact on this product.
Conditions:
Device with default configuration.
Workaround:
Not currently available.
Further Problem Description:
Additional details about the vulnerabilities listed above can be found at http://cve.mitre.org/cve/cve.html
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 4.3/3.9:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:N/AC:M/Au:N/C:P/I:N/A:N/E:POC/RL:U/RC:C&version=2.0
CVE ID CVE-2011-3389 and CVE-2008-5161has been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 05-SEP-2015 |
|
Known Affected Releases: | 5.2(2c), 6.2(3) |
|
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.2(5)S32, 6.3(0.165)S0, 6.3(0.74)S0, 6.3(1)S5, 6.3(1.3)S0 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw12452 | Title: | DCNM-SAN: Brocade HBA is shown as switch under "switch-list" |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Brocade HBA is showing as switch in DCNM-SAN under switch list
Conditions:
Brocade HBA with OUI 0x000533
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-SEP-2015 |
|
Known Affected Releases: | 7.1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv49839 | Title: | Partition ID should be configurable |
|
Status: | Open |
|
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: | 30-SEP-2015 |
|
Known Affected Releases: | 7.2(1) |
|
Known Fixed Releases: * | 7.2(2.14)S0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv05441 | Title: | [Feature req] Option to resolve port conflicts during DCNM upgrade |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
An error is thrown during DCNM upgrade that prevents the upgrade from continuing because of unresolved port-conflicts.
Conditions:
upgrading DCNM when using non-default ports.
Workaround:
Kill services using those ports. (Although this can create a conflict later between the other non-dcnm services and the dcmm services)
Further Problem Description:
This is a feature request for the ability to auto-resolve port conflicts during upgrade
|
|
Last Modified: | 14-SEP-2015 |
|
Known Affected Releases: | 6.3(2) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv49645 | Title: | Extend Partition shows green checkmark, even if BL auto-config fails |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
Extending Partition in DCNM Auto-Config does show green check-mark, even if configuration on Switch fails. No rollback is perform in DCNM for erroneous situation
Conditions:
extending a partition
Workaround:
Disable Extension
correct failure in BL auto-config
Enable Extension
Further Problem Description:
|
|
Last Modified: | 28-SEP-2015 |
|
Known Affected Releases: | 7.1(1), 7.1(2), 7.2(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw09446 | Title: | DCNM SAN client only one user can update config on switch. |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
DCNM WebUI/Admin/Data Sources show N5K switches discovered by usrdcnm and N7K switches discovered by dcnm-operator. When in DCNM-LAN client user A (neither usrdcnm or dcnm-operator) can send configuration to N5K. On the same computer DCNM-LAN client, user B (neither usrdcnm or dcnm-operator) can not send configuration. Receives error - Delivery failed because of device
connection issues.
Conditions:
DCNM 7.1(2)
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 14-SEP-2015 |
|
Known Affected Releases: | 7.1(2.1) |
|
Known Fixed Releases: | |
|
|
| |
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论