| |
|
Alert Type: | New |
Bug Id: | CSCuy93864 | Title: | After downgrade from 611 to 524 xr prompt is not booting up |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
Only calvados prompt is coming up, Xr prompt gets stuck .
Conditions:
performed downgrade from 6.1.1.07I [xr-dev ncs6k] to 524 image
Workaround:
There is no workaround for this issue except external PXE installation. Changes were made to XR data partition location in 6.1.1. SMU is required in 5.2.x versions to created partitions in the correct location.
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv06711 | Title: | xr user is not able to login to calvados if dont have user profile |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
xr user is not able to login to calvados if user profile doesn't have user group configured.
Conditions:
If user profile doesn't have user group configured.
Workaround:
Modification in RADIUS server and it needs a server reboot
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.3i.BASE, 6.0.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75848 | Title: | sftp allows to overwrite system files |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:
A vulnerability in SCP and SFTP modules of Cisco IOS XR for could allow an authenticated, remote attacker to overwrite
system files and cause a denial of service (DoS) condition.
The vulnerability is due to improper setting of permissions on the filesystem for certain paths that include system files. An attacker could exploit this vulnerability by using scp or sftp
client to overwrite system files on the affected device. An exploit could allow the attacker to overwrite system files and cause a denial of service (DoS) condition.
Conditions:
Those services need to be enabled on the device by turning on ssh server.
An attacker has to have a valid account on the operating system of the IOS XR device. Once connected via SCP/SFTP, an attacker can browse the directories on the device and
overwrite existing system files.
Workaround:
None.
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.8/5.6:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:N/AC:L/Au:S/C:N/I:C/A:N/E:F/RL:OF/RC:C&version=2.0
CVE ID CVE-2016-1366 has 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: | 19-APR-2016 |
|
Known Affected Releases: | 5.2.4.K9SEC |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux02329 | Title: | process 'placed' took too long to respond to startup request & timed out |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When trying to load and commit saved configuration, snmp configuration commit errors are seen. Unable to commit the configuration.
Conditions:
Copy the running-config to the harddisk.
Perform "commit replace" from config mode
Login to the router thru console
Now load the saved configuration from harddisk
Execute "commit"
You will see the commit errors related to snmp config on the console
Workaround:
No Workaround
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.3.31.4i.BASE, 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux36870 | Title: | NCS-525 : FIB_MGR crash while adding second static route entry |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The issue is seen while adding a static route entry for the same destination IP twice. Once by directly specifying the interface port number and then by specifying the next hop IP address.
The fib_mgr process reloads unexpectedly and the interface ports will stop functioning and gets recovered automatically.
Conditions:
Seen when same static route to a network is added twice in two different config methods. one directly by specifying the outgoing interface name and another by specifying the IP address of the connected next Hop..
Workaround:
Configure static route only through one of the methods. Either through next hop IP or outgoing interface Port.
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut19134 | Title: | ISSU-XR: RP1 VM stuck at Unknown Band in load phase |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:For ISSU case:
ISSU will be aborting due to one of the v2 LC vm going down
Issu cleanup wont be clean the v2 vms (thats the sympom).
For all other reload cases:
-> XR LC VM will reload due to below reason and also XR VM on RP will not be coming up properly:
VM_REQUESTED_UNGRACEFUL_RELOAD:Headless SDR-No Boot Server Node
This is because the lead information from the RP will not be propagated to other nodes .
Run the below command from shell on RP
cmp_dbg -s pm
This will show 0xffffffff for both the Lead and back up lead.
Conditions:issue (where LC VM won't come up) happens during fresh boot of the system. It could be
-> Reload of all XR VMs
-> Install activate / deactivate of reload smu
-> Fresh boot up of the system
->xR ISSU
Workaround:Steps:
ISSU case:
hw mod reload of v2 xr vm
Other reload cases:
1)Restarting the CM on RP belonging to SDR lead pair (often it is running on 0/RP0) should recover all the nodes including LC's (if it happens to be CM system lead).
2) If it doesn't recover, please run this command from calvados prompt:
sdr default-sdr location all start
More Info:->Information regarding case where LC won't come up:
Race condition could occur in cmp which will cause right notifications to go out with stale identifier. Because of the same, CM is dropping the lead notification sent out by CMP on 0/RP0 since it was with stale identifier. This is turn will result in lead information not getting propagated to the other nodes. LC will wait for 10 mins to get the lead info and since it couldn't get it , it will go down due to "No Boot Server Node condition.
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.3.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.8i.BASE, 6.0.0.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux11819 | Title: | xr-issu aborted due to node going down,processmgr, notify_node_down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
XR_ISSU activation aborts when one of the node goes down during load phase
Conditions:
While trying xr-issu for image/smu upgradation
Workaround:
No workaround. Needs a fix.
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.5.ADMIN, 5.2.5.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.36i.BASE, 6.0.0.BASE, 6.0.1.12i.BASE, 6.1.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw41928 | Title: | Error handling in LPTS needs to be improved |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
lpts_pa process blocked
Conditions:
race condition
Workaround:
process restart
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | 5.2.5.29i.BASE, 5.3.3.14i.BASE, 6.0.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy48854 | Title: | (SSR-611.1i)npu_driver process crash on LC OIR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
npu_driver process crash on Lc OIR
Conditions:
Dring LC OIR
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu72972 | Title: | Hotplug not received for one asic causing S2 to reload second time |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | When we reload one chassis, FC reload twice, this happens when ESD take the slot from FC.
Symptom:
Sometimes, there's some bad state in host side. Or ESD takes Fabric card driver card slot
Conditions:
Especially on big switch, there's NTSW happen frequently.
Workaround:
no workaround
Further Problem Description:
Before, this logic was added to handle scapa LC OIR case, since Scapa LC is CPU less card.
But we added this logic in PI code, so
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.19i.BASE, 5.2.5.5i.BASE, 6.0.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz26580 | Title: | TE tunnels flap during RPFO during to overload bit set |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
TE tunnels flap on RPFO
Conditions:
IOS-XR/5.2.5 running on NCS6K , Trigger is RPFO.
Workaround:
Disable "set-overload-bit on-startup 600" under router isis when doing RPFO
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv39293 | Title: | Memory leak in inventory lib |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | This defect may have a functional impact.
Symptom:Description.
Memory leak is seen in inventory lib.
Conditions:Condition.
This issue occurred on NCS6K.
Workaround:Workaround.
There is no available workaround at this time to overcome this defect.
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.47.38i.FWDG, 5.2.5.20i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu58694 | Title: | show commands not working after router reload [RT 19037] |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In sysadmin mode of a Cisco NCS 6000 or 4000 system, some node(s) may be missing from ? completion in CLI commands, despite the node(s) being up and running.
Conditions:
This can be triggered by internode network connectivity issues. The CLI commands may be missing nodes even after the internode network connectivity issue resolves itself.
Workaround:
Reloading the missing sysadmin VM (if possible) will recover the system. Restarting the active instance of confd_helper will also recover the system:
1. Restarting admin VM of missing node(s):
sysadmin-vm:0_RP1# reload admin location X/YZ
2. Restarting active confd_helper process:
sysadmin-vm:0_RP1# show processes services confd_helper run location all
Fri Jun 26 02:13:32.823 UTC
----------------------------------------------------------------------
node: X/YZ
----------------------------------------------------------------------
Service: confd_helper
Host Process(IID) ARGS: confd_helper(0) -t token -v -d -w 400 -b 30 -p 600 -r 10 -f 10
Scope: SYSTEM
Redundancy: Y
Selected: Y
Last started: 06/26/2015 02:01:07.000
HA-Role: ACTIVE
State: Run
Last Ready Time: 677s
sysadmin-vm:0_RP1# process restart confd_helper location X/YZ
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.19i.BASE, 5.2.5.5i.BASE, 6.0.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw80514 | Title: | ESD switch reset cause HB loss and reload XR VM |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
RP XR VM reloads following switch reset due to fatal esd error
Conditions:
ESD fatal errors like FDB Flush failure cause switch reset which further cause XR VM reload due to heart beat loss
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 6.0.1.BASE, 6.1.0.ADMIN |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.47.38i.FWDG, 5.2.5.BASE, 6.0.1.25i.BASE, 6.1.1.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv53674 | Title: | [5.2.5.3I SIT] install prepare got aborted after 90 mins(timeout) |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Install [prepare|activate] issu stuck on 30% progress until timeout occurs and the operation is aborted after about 60 minutes.
Symptom:
Install [prepare|activate] issu stuck on 30% progress until timeout occurs and the operation is aborted after about 60 minutes.
Conditions:
The system is upgraded or SMUs are installed via issu.
Install activate issu or install prepare issu is executed.
Workaround:
Restart process inst_agent in sysadmin on All RPs
More Info:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.24i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy68116 | Title: | RSVP crashed in rsvp_msg_pending_add_perr during ISSU SMU install |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
RSVP on old V1 active crashed in rsvp_msg_pending_add_perr during ISSU SMU install.
Conditions:
RSVP crash is occurring on *old* V1 Active instance. This is the instance that is being destroyed during ISSU, as it was the older software version.
The crash has no impact on ISSU, or any RSVP related functionality, and is purely due to the two following items:
1. Timing Issue
2. ISSU shutdown procedure for RSVP on old V1 Active Instance
The Timing Issue is receiving a PATH_ERROR, but not having yet processed it before we change our process state from V1_ACTIVE. This means that the PATH_ERROR is in the received queue, but no action has been performed.
When we perform ISSU shutdown procedure, we stop receiving packets and subsequently, change our process state from V1_Active. This will cause RSVP to consider itself a non-master instance. When we are shutting down RSVP after the 'BIG BANG' we drain our queues. During the queue draining, the previous PATH_ERROR is now being processed - and, in addition, causes the 'non-master' (standby) code path to be exercised. This will mean that the Path state (if it still exists), will not have a slave hasi ID as it was never a slave instance. When this is occurs, the standby's code path will assert on this ID being invalid.
RSVP will need to modify it's shutdown procedure in order to handle the above gracefully.
Workaround:
none
Further Problem Description:
N/A
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu47900 | Title: | NPU_DRIVER:"ISSU_ERR_SYNC_FAILURE":Interfaces not created - ISSU load. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
NPU Driver in XR LC cannot communicate i.e. send faults and reload requests to Shelf Manager.
Conditions:
This behavior is observed after one or more shelf manager restarts. It is also observed sometimes in ISSU, however, the root cause is shelf manager restarts (fmlib service switchover due to SM restart)
Workaround:
None
Recovery:
Restart npu_driver process on LC
Example:
process restart nu_driver (location of the LC where npu driver is stuck)
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.5.ADMIN, 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.13i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv28167 | Title: | NCS6k SNMP ifAlias is not being updated after LC reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After LC reload ifAlias OID is not being updated to reflect description changes on all of the interfaces.
Conditions:
IOX 5.2.x
LC or chassis reload
Workaround:
mibd_interface process restart
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 5.2.3.BASE |
|
Known Fixed Releases: * | 5.2.5.27i.BASE, 5.3.31.4i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy45976 | Title: | NCS6K: VM_manager crashed on LC on Cal ISSU SMU deactivation |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
VM_manager crashed on LC
Conditions:
Cal ISSU SMU deactivation
Workaround:
Re-spawns itself
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv70886 | Title: | ntpdc crashed on PAT LC at lwm_iov_to_iov_memcpyv_with_offset |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ntpsc process crash seen with this specific backtrace. No specific pre-condition is known. The cause of this crash is that ntpdc uses a "aggressive timer for lwm (light weight messaging" API. This usage in ntpdc brings out a very intermittent race condition, where one thread of ntpdc is attempting to fail the request since the aggressive timer is about to expire, where as other thread in ntpdc is about to handle the response from the server process.
Process crash is due to incorrect handling of this race condiition
Conditions:
Refer to "Symptoms"/.
Workaround:
None needed. ntpdc process is automatically restarted and recovered
Further Problem Description:
|
|
Last Modified: | 16-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE, 6.1.0.BASE |
|
Known Fixed Releases: * | 6.1.1.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu66549 | Title: | ODL: check for subsys shutdown during async connect |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Crash when a protracted connection to ConfD manageability server
completes after the client daemon had shut down the ConfD session.
Conditions:
Occurred during node restart where confd service was temporarily unavailable
and client program was changing its registrations while the asynchronous connections
to the confd service were being attempted.
Workaround:
None; process restarts and reestablishes connections to the confd service
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.4.ADMIN |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.13i.BASE, 6.0.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv76361 | Title: | NCS6K PAT LC Node status in xr show platform vm changed to UNKNOWN |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
node status of NCS6K PAT LC changes to UNKNOWN in xr show platform vm
Conditions:
router reload triggered by hw-mod loc all reload
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.47.38i.BASE, 5.2.5.24i.BASE, 6.0.0.18i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuj96032 | Title: | %L2-SSE_PFILTER_EA-3-ERR_IM_CAPS : add acl failed on Bundle-Ether |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
a customer who is trying to change ACL on the CRS-16 router for LC FP-X+40-10GBE:
RP/0/RP0/CPU0:ia-sthu-bb06(config-if)#show configuration failed
interface TenGigE0/0/0/20
ipv4 access-group FOREIGN-EDGE-IN-BR-9389881-v2-ACL ingress
!!% 'ifmgr' detected the 'warning' condition 'An EA client returned:': No such file or directory
!
In the traces I have the following error:
Mar 25 07:05:32.051 pfilter_ea/ipv4_log 0/0/CPU0 t1 need to program acl FOREIGN-EDGE-IN-BR-9389881-v2-ACL on intf 0x1080360 direction 0.
Mar 25 07:05:32.053 pfilter_ea/ipv4_log 0/0/CPU0 t1 sse_pfilter_ea_compile_l4_entry: compile arl for acl FOREIGN-EDGE-IN-BR-9389881-v2-ACL seq 110 failed. 0x2
Mar 25 07:05:32.053 pfilter_ea/ipv4_log 0/0/CPU0 t1 sse_pfilter_ea_ipv4_compile_func: compile tcam entries for acl FOREIGN-EDGE-IN-BR-9389881-v2-ACL seq 110 failed. 0x2
Mar 25 07:05:32.053 pfilter_ea/ipv4_log 0/0/CPU0 t1 sse_pfilter_ea_caps_add_worker: hw resources not available for acl FOREIGN-EDGE-IN-BR-9389881-v2-ACL. 0x2
Conditions:
unknown
Workaround:
unknown
Further Problem Description:
n/a
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.0.1.LC |
|
Known Fixed Releases: | 5.0.1.9i.BASE, 5.2.1.1i.BASE, 5.2.2.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy16313 | Title: | NTP clock does not change from synchronized to unsynchronized |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
NTP association drops sys_peer/INIT after applying ACL however show ntp status still shows synchronized.
Conditions:
NCS6k running 5.2.3/5.2.4
Workaround:
Remove and re-add NTP configuration
Further Problem Description:
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 5.2.3.BASE |
|
Known Fixed Releases: * | 6.0.1.27i.BASE, 6.1.1.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw34072 | Title: | [PaniniB2B] Modify Sense Resistor from 3 Ohms to 1.5 Ohms |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The current sensor values reported for ADM1075 was not correct. It was 1/2 of what is expected.
Conditions:
Always
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 12-APR-2016 |
|
Known Affected Releases: | 6.0.0.BASE, 6.2.0.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy80059 | Title: | admin vm kdump on rp1 during install prepare from 525 to 523 |
|
Status: * | Other |
|
Severity: * | 3 Moderate |
Description: | Symptom:
admin vm kdump on rp
Conditions:
install prepare from 525 to 523
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 11-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy52581 | Title: | PAM tool reported shelf_mgr process memory leak |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
memory leak in shelf_mgr process
Conditions:
shut/unshut of lc
Workaround:
restart shelf_mgr
Further Problem Description:
|
|
Last Modified: | 09-APR-2016 |
|
Known Affected Releases: | 5.2.5.38i.BASE |
|
Known Fixed Releases: * | 5.2.5.48i.BASE, 6.1.1.10i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz04409 | Title: | 'show tech-support ethernet interfaces' taking >10mins |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
'show tech-support ethernet interfaces' taking >10mins
RP/0/RP1/CPU0:A41#show ver
Sun Apr 3 23:57:38.822 PDT
Cisco IOS XR Software, Version 5.2.5
Copyright (c) 2013-2014 by Cisco Systems, Inc.
Build Information:
Built By : ahoang
Built On : Thu Mar 17 19:26:37 PDT 2016
Build Host : iox-lnx-006
Workspace : /auto/srcarchive16/production/5.2.5/all/workspace
Version : 5.2.5
Location : /opt/cisco/XR/packages/
cisco NCS-6000 () processor
System uptime is 1 week, 5 days, 3 hours, 1 minute
RP/0/RP1/CPU0:A41#
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 5.2.5.ADMIN, 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy04404 | Title: | Periodically clear L1T cache |
|
Status: | Fixed |
|
Severity: * | 3 Moderate |
Description: | Symptom:
Please refer to CSCux48989
Conditions:
Please refer to CSCux48989
Workaround:
Please refer to CSCux48989
Further Problem Description:
NA
|
|
Last Modified: | 02-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | 6.1.1.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu06731 | Title: | Bfd not kicking in after bundle shutdown |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When interface Bundle Ether 202 on OrcWST31 is shutdown, bfd is not kicking in and the convergence time is very high. It is coming about 300-1900 ms.
Conditions:
Interface shutdown.
Workaround:
None
Further Problem Description:
When interface Bundle Ether 202 on OrcWST31 is shutdown, bfd is not kicking in and the convergence time is very high. It is coming about 300-1900 ms.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy25690 | Title: | NCS6K:slice info missing fm xr show platform after OCU from 42J v1 to v2 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
slice info missing fm xr show platform
Conditions:
after OCU from 42J v1 to v2
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.46i.BASE, 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46617 | Title: | LTC2978 SBE workaround |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
If the EEPROM single bit error (SBE) occurs, the LTC2978 will fail to come up.
Conditions:
The primary failure mode is a leakage to the charge neutral state of the EEPROM
cell, but several devices have shown leakage away from that state.
Workaround:
None
Further Problem Description:
In the event the EEPROM SBE occurs, the LTC2978 will fail to come up. It automatically verifies the checksum, and if there is a mismatch, the device goes into a "no harm" mode and will not enable any power supplies.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 5.0.0.BASE |
|
Known Fixed Releases: * | 6.1.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw69897 | Title: | Increasing the interface clean-up timer in SMP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Driver crash. Refer ddts CSCuu68353.
Conditions:
No breakout on slices 2 and 3 and pon reset on npu 4.
Workaround:
Reload lc
Further Problem Description:
The timer which waits for the clean up of the interface by NPU that value
(currently reduced to 5 mins from earlier 50 mins because of ddts CSCuu35818) needs
to be redefined for ddts CSCuu68353
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | 5.2.5.34i.BASE, 6.0.1.12i.BASE, 6.1.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz20006 | Title: | mcast encap support in panini forwarder |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
mcast ipv4 packets with - ipv4 options will be dropped.
Conditions:
data - mcast ipv4 packets with - ipv4 options packets
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 6.1.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux67535 | Title: | PON_RESET on NC6-10X100G-L-K /5.2.1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LC/0/3/CPU0:Dec 8 17:36:19.861 : fia_driver[136]: %PLATFORM-CIH-5-ASIC_ERROR_PON_RESET_START : fia[1]: PON_RESET needed 0x22064002
LC/0/3/CPU0:Dec 8 17:36:23.368 : fia_driver[136]: %PLATFORM-CIH-2-ASIC_ERROR_PON_RESET : fia[1]: A config-err error has occurred causing performance loss persistent.
Conditions:
Router reload, PON/Hard reset of FIA ASIC, LC reload or steady state. Any of the above with traffic in the system.
Workaround:
NA
Further Problem Description:
At customer site we have seen the ASIC going for PON with error code 0x22064002 i.e SCH.Interrupt_Register.ActFlow_BadParams
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 5.2.1.CE |
|
Known Fixed Releases: * | 5.2.5.45i.BASE, 6.1.1.12i.BASE, 6.1.1.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy81926 | Title: | NCS6K: show tech ds takes for ever and does not complete |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Show tech ds takes for ever and does not complete
Conditions:
Always
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 6.1.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux25375 | Title: | 525 NCS6K ISSU: More than 1M labels allocated: mpls_lsd traceback |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Following ERR log is seen on primary active during issu load phase:
RP/0/RP0/CPU0:Nov 12 00:53:23.871 EST: mpls_lsd[126]: %ROUTING-MPLS_LSD-6-ERR_LBL_OOR : More than 1M labels allocated : mpls_lsd : (PID=4342) : -Traceback= 4a65b5 4a686a 45a610 7fd0a2a5e2ad 7fd0a2a7a9b7 7fd0a2a861ee 7fd0a2f092e4 7fd0a2f0effe 4138df 7fd09ce53d3e
Conditions:
Just trigger NG-ISSU load phase
Workaround:
This error is a false alarm and does not have any functional impact. No workaround is needed. Just ignore it.
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: * | 5.2.5.36i.FWDG, 6.0.1.12i.FWDG, 6.1.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz25707 | Title: | sluggish cli execution of show interface |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
show interface location <> takes more time exponentially when number of interface increases
Conditions:
normal operation
Workaround:
n/a
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80886 | Title: | Output of 'show issu location all' is not listing rp and lc in a sequenc |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Output of show issu location all is not listing rp and lc in a sequence
Conditions:
output of 'show issu location all'
Workaround:
Further Problem Description:
|
|
Last Modified: | 01-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz22718 | Title: | NCS6008 No response from Show Interfaces ? |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
RP/0/RP0/CPU0:TLAB79-CAR2#sho interfaces ?
WORD Interface name (may use '*' or numeric range [A-B])
accounting show interface accounting option.
brief show interface brief option.
description show interface description option.
detail show interface detail option.
edm Information about the show interfaces EDM process(cisco-support)
location Specify a location
summary show interface summary option.
| Output Modifiers
RP/0/RP0/CPU0:TLAB79-CAR2#show processes blocked
Fri Apr 15 08:56:16.007 EDT
PID TID ProcessName State TimeInState MiscInfo
12014 12037 l2vpn_mgr Reply 00:12:52.503 5385 lspv_server
11881 11881 ifindex_server Reply 00:14:22.016 3842 /proc/3842/cmdline
connect failed for snmpd_1_23467 errno: 11
12496 12530 bgp Reply 253:20:46.154 5385 lspv_server
5620 5665 lpts_fm Reply 00:00:00.302 3854 lpts_pa
5393 10749 mpls_ldp Reply 253:23:58.814 5385 lspv_server
5194 5341 nfmgr Reply 00:00:10.906 3274 sysdb_mc
Conditions:
NCS6k on 5.2.5. Trigger is unknown at this time.
Workaround:
Process restart parser_server
process restart ifindex_server
Further Problem Description:
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 5.2.5.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul98475 | Title: | enhancing robustness of the nodeid lib |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
inst_mgr crashes on RP when new LC is inserted in chassis.
Conditions:
new LC insertion into working chassis
Workaround:
no workaround
Further Problem Description:
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 5.0.1.ADMIN |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui88484 | Title: | [panini] cleanup /install/tmp_staging in case of RP reset during install |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
In case install fails and node reload, packages can be left in /install/tmp_staging/. This can cause confusion, and potential failure(e.g., run out of disk space).
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 5.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui60486 | Title: | For system upgrade reload warnding should mention system reload |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
While performing System upgrade ( from release X to release Y ) using XR , the below message is printed on install activate
Sep 17 22:24:53 This install operation will reload the sdr, continue?
[yes/no]:[no] yes
..Install operation will continue in the background
This message will change to ( in future releases )
Sep 17 22:24:53 This install operation will reload the system, continue?
[yes/no]:[no] yes
Conditions:
System upgrade triggered from XR , Seen 100% of the time
Workaround:
No known workarounds
Further Problem Description:
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 5.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
没有评论:
发表评论