| |
|
Alert Type: | New |
Bug Id: | CSCuw55325 | Title: | P-PN: MPLS-TE topology discovery cause many error in vne log |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
discovering MPLS TE from ASR9k and C7600 cause many error due to DC that used to discover the topology from both devices is different
Conditions:
Model ASR9k and C7600 that configured between them MPLS TE topology
Workaround:
Further Problem Description:
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 4.2(2.0)PP2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu00250 | Title: | PN - Default Port Description CB scripts for ASR903 are empty |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
The default Command Builder scripts for an ASR903 contain empty commands strings for the following actions:
Add Port Description
Remove Port Description
Update Port Description
Conditions:
None
Workaround:
Modify the scripts manually or use CLI on device to implement desired commands.
Further Problem Description:
(release notes added by addprefcs-org.ksh)
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: * | 4.1(0X)DP1511.0.722, 4.2(0X)DP1511.0.722, 4.2(1)DP1511.0.722, 4.2(2)DP1511.0.722 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw32992 | Title: | Code example in PN "Cisco Prime OSS Integration Guide" not compile |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Code example in Prime network "Cisco Prime OSS Integration Guide" not compile.
for example there is a parameter that is not initialized
SOAPHeader header = message.getSOAPHeader;
here "message" parameter not initialized and user don't know the type of the parameter.
Any code example must be compiled and validated that it work before adding it to any doc
Conditions:
1) Open PN doc "Cisco Prime OSS Integration Guide for MTOSI and 3GPP"
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/prime/network/4-2-2/oss_integration/mtosi_3gpp/Prime_Network_OSS_Integration_Guide.pdf
2. Copy the code in "11.7.1 Useful Code Snippets for 3GPP Request Response" section
(page 210-211)
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 4.2(2.0)PP2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui35119 | Title: | NCCM - config restoration fail in device banner |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Configuration restore operation fails.
Conditions:
Device banner is configured with caret sign(^c) or ETX char or apostrophe char.
Workaround:
caret sign(^c) or ETX char or apostrophe char should not be configured in banner.
Further Problem Description:
|
|
Last Modified: | 20-OCT-2015 |
|
Known Affected Releases: | 3.11(0.999) |
|
Known Fixed Releases: * | 4.1(0)PP3, 4.2(2.0)PP2 |
|
|
| |
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论