| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu77478 | Title: | MPLS LDP crash due to invalid packet IOS-XR 5.1.3 |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptoms:
A vulnerability in MPLS LDP packet processing Cisco IOS XR could allow an unauthenticated, remote attacker to cause a reload of the MPLS LDP process on the
affected device.
The vulnerability is due to improper processing of crafted MPLS LDP packet. An attacker could exploit this vulnerability by sending crafted MPLS LDP packets to be
processed by an affected device. An exploit could allow the attacker to cause a reload of the MPLS LDP process on the affected device.
Conditions:
Cisco IOS XR device configured to process MPLS LDP packets.
Workaround:
Disable advertising of FECs with prefix length <=24
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.6:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:N/AC:M/Au:N/C:N/I:N/A:P/E:F/RL:OF/RC:C&version=2.0
CVE ID CVE-2015-4223 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: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: * | 5.2.5.25i.MPLS, 5.3.1.SP2, 5.3.2, 5.3.2.13i.MPLS, 6.0.0.10i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx33523 | Title: | LC not powering up from MBUS following an LC OIR |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
LC not powering up from MBUS following an LC OIR
Conditions:
OIR
Workaround:
process restart sysldr
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 3.8.0.BASE |
|
Known Fixed Releases: * | 4.2.1, 4.2.1.30i.BASE, 4.2.2, 4.2.2.4i.BASE, 4.2.3, 4.2.3.12i.BASE, 4.2.4, 4.3.0, 4.3.0.12i.BASE, 4.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu00270 | Title: | Memory leak in BGP because of policy clientlib for attach point add/del |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
policy_repository crash
Conditions:
after upgrade to 5.1.3
Workaround:
n/a
Further Problem Description:
there is no trigger is seen, customer is occasionally update the config by doing commit replace. This happen only on this router, other router in 5.1.3 same SMUs are working fine.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.2.5.33i.ROUT, 5.3.1.SP2, 5.3.2, 5.3.2.10i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw87427 | Title: | [UNI-C] NC4K tunnel tear down after dwdm LC OIR |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: * | Symptom:
OCHTrail GMPLS-UNI tunnel will be stuck in recovery state and none of the triggers such as LC OIR will not bring down the Tunnel.
Conditions:
OCHTrail GMPLS-UNI tunnel is created. After this te_control process restarts.
Workaround:
Delete the OCHTrail tunnel and recreate it.
Further Problem Description:
Post te_control process restart check the tunnel state using the command:
"show mpls traffic-eng tunnels detail private"
This will show that tunnel is stuck in ST_RECOVERY state:
FSM event info
Event time: Fri Oct 23 20:22:05 2015
([ST_INIT] -> [ST_RECOVERY], [EV_HA_RECOVERED_FROM_CHKPT])
Event time: Fri Oct 23 20:22:05 2015
([ST_RECOVERY] -> [ST_RECOVERY], [EV_UPSTREAM_LABEL_AVAIL])
Event time: Fri Oct 23 20:22:05 2015
([ST_RECOVERY] -> [ST_RECOVERY], [EV_LABEL_AVAILABLE])
Event time: Fri Oct 23 20:22:05 2015
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux75653 | Title: | mrib assert @ mrib_lsm_ce_eole_unlink on RPFO on new Active RP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | During/After RPFO, if mrib PD doesnt have FGID pool and mrib PI requests for FGID. PD returns error and that causing the issue.
Ideally PI should not assert the process when FGID is not available instead of that it has to add entry in retry list.
When FGID pool is available, PD pulses PI then PI has to retry the failed entries.
Issue is happening only after RPFO and before allocating FGID pool in PD. So in this specific scenario PD returns new error code. If PI sees this new error code, it should not assert the process
Symptom:
Mrib process crash immediately after RPFO.
Conditions:
During/After RPFO, if mrib PD doesn't have FGID pool/connection is not established with FGID aggregator and mrib PI requests for FGID. PD returns error and that causing the issue.
Workaround:
NA
Further Problem Description:
During/After RPFO, if mrib PD doesnt have FGID pool and mrib PI requests for FGID. PD returns error and that causing the issue.
Ideally PI should not assert the process when FGID is not available instead of that it has to add entry in retry list.
When FGID pool is available, PD pulses PI then PI has to retry the failed entries.
Issue is happening only after RPFO and before allocating FGID pool in PD. So in this specific scenario PD returns new error code. If PI sees this new error code, it should not assert the process
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: * | 5.3.3.MCAST, 6.0.1.MCAST |
|
Known Fixed Releases: | 5.3.3.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80150 | Title: | ARWEN:QOSHA Too many crash after Active RPVM switchover |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
otn_framer_digi crash and eth_intf_ea crash seen after Active RPVM switchover.
Please find the attachment for core files
Conditions:
Workaround:
Further Problem Description:
show running config
=============
RP/0/RP0:QOS_R1#show running-config
Building configuration...
!! IOS XR Configuration version = 6.0.1.12I
!! Last configuration change at Sun Oct 18 00:18:46 1970 by UNKNOWN
!
hostname QOS_R1
logging console disable
logging buffered 10000000
username root
group root-lr
group cisco-support
secret 5 $1$guvp$n1K2EYKZsdG8syl8c5It/1
!
line console
timestamp disable
exec-timeout 0 0
!
line default
timestamp disable
!
fault-profile defaultprofile
fault-identifier subsystem CALV fault-type UNKNOWN fault-tag MY_TEST_TAG_F sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_FOOBAR fault-tag MY_TEST_TAG_B sas CRITICAL nsas NONREPORTED
fault-identifier subsystem CALV fault-type SW_FOOBAR fault-tag RAISE_RELOAD_CARD_REQUEST sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_MALLOC_ERROR fault-tag MY_TEST_TAG_D sas MAJOR nsas MINOR
fault-identifier subsystem CALV fault-type SW_MALLOC_ERROR fault-tag MY_TEST_TAG_E sas CRITICAL nsas MINOR
fault-identifier subsystem CALV fault-type SW_MEMORY_FAULT fault-tag MY_TEST_TAG_C sas MAJOR nsas NONREPORTED
!
!
class-map match-any CLASS_1_COS
match cos 1
end-class-map
!
policy-map POLICY_ARWEN_L2
class CLASS_1_COS
set qos-group 5
police rate percent 50
!
!
class class-default
!
end-policy-map
!
interface MgmtEth0/RP0/CPU0/0
ipv4 address 10.77.136.31 255.255.255.0
!
interface MgmtEth0/RP1/CPU0/0
ipv4 address 10.77.136.32 255.255.255.0
!
interface TenGigE0/3/0/3
l2transport
!
!
interface TenGigE0/5/0/6
l2transport
service-policy input POLICY_ARWEN_L2
!
!
controller Optics0/3/0/3
port-mode Ethernet-packet
!
controller Optics0/5/0/6
port-mode Ethernet-packet
!
router static
address-family ipv4 unicast
0.0.0.0/0 10.77.136.1
!
!
l2vpn
xconnect group xcon0
p2p xcon0_p2p1
interface TenGigE0/3/0/3
interface TenGigE0/5/0/6
!
!
!
end
RP/0/RP0:QOS_R1#show vm
% Incomplete command.
RP/0/RP0:QOS_R1#show version
Cisco IOS XR Software, Version 6.0.1.12I
Copyright (c) 2013-2015 by Cisco Systems, Inc.
Build Information:
Built By : tinhuang
Built On : Sat Dec 19 23:56:41 PST 2015
Build Host : sjck-gold-29
Workspace : /san1/nightly/xr-dev_15.12.19C/ncs4k
Version : 6.0.1.12I
Location : /opt/cisco/XR/packages/
cisco NCS-4000 () processor
System uptime is 1 hour, 26 minutes
RP/0/RP0:QOS_R1#show platform
Node name Node type Node state Admin state Config state
-----------------------------------------------------------------------------------
0/3 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/5 NCS4K-2H10T-OP-KS OPERATIONAL UP NSHUT
0/RP0 NCS4K-RP OPERATIONAL UP NSHUT
0/RP1 NCS4K-RP OPERATIONAL UP NSHUT
0/FC0 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC1 NCS4016-FC-M OPERATIONAL UP NSHUT
0/FC3 NCS4016-FC-M OPERATIONAL UP NSHUT
0/CI0 NCS4K-CRAFT OPERATIONAL UP NSHUT
0/FT0 NCS4K-FTA OPERATIONAL UP NSHUT
0/FT1 NCS4K-FTA OPERATIONAL UP NSHUT
0/EC0 NCS4K-ECU OP
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux73473 | Title: | NCS4k, Database restore can't work thru CTC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
when trying to restore the database thru CTC, it gives an error and it can't go thru.
Conditions:
NCS4k database restore thru CTC
Workaround:
none - use CLI to restore the confi
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE, 6.0.1.17i.FWDG, 6.0.1.17i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh76229 | Title: | sysdb_mc crashed leading to dead lock condition in 4.2.3 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The process lrd blocks on sysdb after sysdb_mc restarts.
Conditions:
sysdb_mc restart when lrd in the middle of some edm operations
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.28i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.1, 5.1.1.9i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu08150 | Title: | aib crash @ bmp_prog_rx_adj_write on Taiko LCs on RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
aib process crashed after RP fail over while trying to program bundle adjacency on Taiko node..
Conditions:
This issue is observed if ifmgr returns pic node count more than 1.
Workaround:
LC reload
Further Problem Description:
This issue is seen with RP fail over while there was a network flapps.(specifically bundle member flapps)
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 5.3.1.FWDG |
|
Known Fixed Releases: | 5.3.2, 5.3.2.10i.BASE, 5.3.2.10i.FWDG, 6.0.0.5i.BASE, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux76027 | Title: | ARWEN:QOS DUT is not responding After service-polic output <name> commit |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
6. Commit service policy on egress interface . Commit is not happened . Device is not responding . Due to Script got failed.
Manually also TB is not responding properly . Unable to do commit replace .
After rack relod 0 then clear configuration inconsistency , able to commit replace . Reproduced 2 times.
RP/0/RP0:QOS_R1#
--- 12:58:35 ---
125: 2016-01-07T12:58:35: %SCRIPT-6-INFO: **************************************************************************
126: 2016-01-07T12:58:35: %SCRIPT-6-INFO: Apply policy-map on L2 | L3 interface
127: 2016-01-07T12:58:35: %SCRIPT-6-INFO: **************************************************************************
128: 2016-01-07T12:58:35: %SCRIPT-6-INFO: Configure Egress service policy
+++ 12:58:35 QOS_R1 config +++
config terminal
RP/0/RP0:QOS_R1(config)#interface TenGigE0/5/0/6
RP/0/RP0:QOS_R1(config-if)#l2transport
RP/0/RP0:QOS_R1(config-if-l2)#service-policy output egress_POLICY_ARWEN_L2
RP/0/RP0:QOS_R1(config-if-l2)#commit
^Z
--- 13:04:37 ---
129: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: result: error
130: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: error_info: econ_prepare_state config:
131: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: QOS_R1 -- sync_timeout: timeout * retrys expired
132: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: while executing
133: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "error $return_value"
134: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ("1" arm line 30)
135: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
136: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "switch -glob -- $return_code {
137: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: [02] {
138: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: _csccon_output_save $name $return_value
139: 2016-01-07T13:04:37: %autoeasy-5-NOTICE:
140: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: if { [string compare $subcmd destroy] != 0 } {
141: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: set ..."
142: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: (procedure "csccon_apply_subcmd" line 116)
143: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
144: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "csccon_apply_subcmd QOS_R1 $subcmd $args"
145: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: (procedure "QOS_R1" line 1)
146: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
147: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "$dut config "interface $dut_hdl_eggr
148: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: $cli
149: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ""
150: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ("foreach" body line 2)
151: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
152: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "foreach dut_hdl_eggr $dut_hdls_eggr {
153: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: $dut config "interface $dut_hdl_eggr
154: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: $cli
155: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ..."
156: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: invoked from within
157: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: "if {$direction_output == 1} {
158: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ########################################################################################################
159: 2016-01-07T13:04:37: %autoeasy-5-NOTICE: ..."
Log :
=====
http://earms-trade.cisco.com/tradeui/resultsviewer.faces?ats=/users/radmuthi/ats5.3.0&client=web&host=scapa-ind01-lnx&archive=at
|
|
Last Modified: | 10-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw52352 | Title: | FM clients need to use unique instance_id when reg same XML with FM |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Fake Alarms may appear at NMS side
Conditions:
RPVM, LCVM switchover or RP Reload
Workaround:
None
Further Problem Description:
reproducible 100%
Expected Resolution - Next Release
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.12i.FWDG, 6.1.0.8i.BASE, 6.1.0.8i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu93123 | Title: | NLIGHT2: SRLG under DWDM get lost after proc restart rsi_agent |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Seen in customer routers
Symptom:
1. All of the SRLG values are lost post RPFO
2. All of the SRLG values are last post rsi_agent restart
3. stand-by is not in sync with active.
Conditions:
Srlg configuration present
Workaround:
No work-around or recovery
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 5.3.1.MPLS, 6.0.0.BASE |
|
Known Fixed Releases: | 6.0.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz94698 | Title: | ipv6 prefix compression algorithm failing on Applications ACL QoS LI |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Provisioning of ipv6 prefixes failed by various applications including ACLs, QoS and Lawful Interceot
Conditions:
ipv6 prefix compression failure reported on usage of ipv6 prefixes by CRS Line card's TCAM Libraries
Workaround:
Configure the "controller pse tcam location R/S/I compression ipv6 prefix n" command where n is calculated for the specific ipv6 prefix using the following formula
In Metro,
If the original prefix length is <=64, then the compressed prefix length will be 44 * original prefix length /64.
If the original prefix length is > 64, then the compressed prefix length will be 16 * (original prefix length minus 64)/64 + 44
In Taiko,
If the original prefix length is <=64, then the compressed prefix length will be 44 * original prefix length /64.
If the original prefix length is > 64, then the compressed prefix length will be 20 * (original prefix length minus 64)/64 + 44
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.1.2.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.21i.FWDG, 4.2.4, 4.3.0, 4.3.0.20i.FWDG, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux81339 | Title: | NCS1K:Middle port mapping is not correct in 10G to 100G config. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
show hw-module slice O/P on NCs1k shows incorrect midport mapping on to Trunk Controllers.
Conditions:
This Mismatch is observed in below Ncs1k hw-module Slice configuration.
When the client bitrate is 10G and trunk bitrate is 100G.
Workaround:
None Available as it is a display issue.
Further Problem Description:
when only one trunk port in a slice is used (eg:12), the traffic from TenGigE7/1 to 7/4, TenGigE8/1 to 8/4, and TenGigE9/3 to 9/4 is passed to trunk port 12.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue05044 | Title: | CFM LT and LB are dropped at 100GigaEther Egress #CRS-3 #high |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: CFM LT and LB are dropped at 100GigaEther Egress
Conditions: Configure 100GigabitEther as CFM MEP/MIP on L2 interface
Workaround: N/A
Expected Resolution: R4.3.1
Reproducibility (%): Reproducible
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.24i.FWDG, 4.3.2, 4.3.2.5i.FWDG, 4.3.2.9i.FWDG, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug07186 | Title: | POS interface stay in down for PPLM alarm stuck |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
pos interface stay in down status for PPLM alarm, even after transport clean PPLM alarm.
Conditions:
after PPLM alarm was detected.
Workaround:
shut & not shut interface this interface.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 3.8.2.2i.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtr07133 | Title: | pkg/bin/bcdls process crashed after S13 OIR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
BCDLS process crashed.
Conditions:
The issue can happen on a temporary out of memory on route producers such RIB or MPLS LSD. This can happen on route reload.
Workaround:
No workaround.
Further Problem Description:
When the issue happens, we also observe the following BCDL/GSP errors:
RP/0/7/CPU0:Nov 17 12:31:23.914 : mpls_lsd[322]: %OS-BCDLPROD-6-MSG_GENERIC_FUNC : function msg_send_event failed: Unknown error
RP/0/7/CPU0:Nov 17 12:31:23.915 : mpls_lsd[322]: %OS-BCDLPROD-3-MSG_SEND_FAIL : Failed to send SEQ_NUM msg. gid: 2026 rc: 4
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 4.1.1.ROUT, 4.2.0.ROUT, 4.2.1.ROUT |
|
Known Fixed Releases: | 4.1.2, 4.2.0, 4.2.0.13i.BASE, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut34304 | Title: | uc_psn wrap on Topaz |
|
Status: * | Terminated |
|
Severity: | 2 Severe |
Description: | During 400G S2 OIR, we saw uc_psn wrap on one Topaz LC. This happened after 18th iteration of S2 OIR.
Symptom:
Fabricq asic reset on topaz LC card.
Conditions:
this was very rare and occured only once on 18th iteration of S2 OIR testing.
Workaround:
No Workaround. Issue recover after asic reset.
Further Problem Description:
|
|
Last Modified: | 17-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw50985 | Title: | Backout enhancement CSCui15813 as it conflicts with CU requirement. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:
Inheritance was not happening as it used to after feature(CSCui15813) got committed to 5.3.2.
Conditions:
Issue happens on 5.3.2 release.
Workaround:
Use SMU for CSCuw50985.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 3.8.3, 3.8.4, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw26855 | Title: | 5.3.2: XR tear down tunnels during FRR event with Juniper Tail End |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When Juniper is the Tail End and is in the FRR event with cisco Head End, high (6 sec to 17 sec) of FRR is seen.
Conditions:
Cisco Head End ---- Cisco PLR ---- Cisco ---- Juniper (Tail End) ______> Primary Path
Cisco Head End ---- Cisco PLR ------------>Juniper (Tail End) ______> backup path during FRR.
When the FRR happens in this condition, high convergence was noted (6 to 17 sec).
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.11i.MPLS, 6.0.0.18i.MPLS, 6.0.1.12i.MPLS, 6.1.0.2i.MPLS |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy34508 | Title: | parser_server high cpu |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom:
Login to device not possible, High CPU in parser_server process
JID TID LAST_CPU PRI STATE HH:MM:SS CPU COMMAND
360 12 3 10 Run 0:01:47 25.00% parser_server
Conditions:
while one vty is in interface-range configuration and line is cleared
Workaround:
login via aux and kill process parser_server
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu97724 | Title: | TCP process crash during RPFO on CRS-X running 5.3.1 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
TCP process crash followed by Qnet Crash during multiple RSP Failover.
Conditions:
Multiple RSP switchover , or BGP process restart
Workaround:
no workaround
Further Problem Description:
This issue is happening due to a race case in TCP socket library.
Please find the events that led to this scenario explained below, which is very rare to happen:
1. BGP is getting restarted. The master socket is getting closed, and TCP tries to cleanup the async sockets walking the PCB table
2. In this process, it takes the mutex owned by the master socket initially, and takes the respective locks while walking each PCB/Socket.
3. There is a bind_connect_batch operation happening in parallel. And the socket takes a mutex, and waits for another mutex.
4. These locks are from the pool for socket mutex and process crash and recovers.
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.1.CE |
|
Known Fixed Releases: * | 5.2.5.37i.BASE, 5.2.5.37i.FWDG, 5.3.2.SP2, 5.3.3.21i.BASE, 6.0.0.21i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40565 | Title: | LDP does not send withdraw when label changes |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When prefix is removed from routing table LDP might not send label withdraw to LDP peer to which this FEC was previously advertised (label mapping message was send).
Conditions:
- XR router running 5.3.2
- IPv4 prefix is removed from routing table
- Static route is removed
Workaround:
clear mpls ldp neighbor
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: * | 5.1.1, 5.1.11, 5.1.12, 5.1.2, 5.1.3, 5.1.4, 5.2.0, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu99081 | Title: | MPLS LDP process continuous respawn / crash with 5.3.1 FCS ASR9K |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Continuous LDP crash is seen when IPv4 mapped IPv6 addresses are used on LDP enabled interfaces.
Conditions:
IPv4 mapped IPv6 address
Workaround:
do not enable LDP on interfaces that have v4 mapped v6 addresses.
Further Problem Description:
Per RPC 7552, IPv4 mapped IPv6 addresses should not be used in LDP. Below is the excerpt from the RFC section A.3.
A.3. Why prohibit IPv4-mapped IPv6 addresses in LDP?
Per discussion with the 6MAN and V6OPS working groups, the
overwhelming consensus was to not promote IPv4-mapped IPv6 addresses
appearing in the routing table, as well as in LDP (address and label)
databases.
Also, [RFC4038], Section 4.2 suggests that IPv4-mapped IPv6-addressed
packets should never appear on the wire.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.15i.MPLS, 6.0.0.10i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu82794 | Title: | Non-negotiated unicast packets sent at the wrong rate |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When using PTP with non-negotiated unicast, a port in master state will send Announce and Sync packets at 1 packet-per-second, regardless of the configured packet rates.
Conditions:
This bug affects only affects master-role ports, slave-role ports function as expected.
Workaround:
No known workaround.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.13i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv46626 | Title: | Comm between ISIS and TE fails due to buffer/Memory exhaustion in AIPC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Customer to observe the following in syslog:
RP/0/RP0/CPU0:Aug 9 13:52:04 PST: isis[1010]:
%ROUTING-ISIS-7-ERR_SEND_TE_MSG : Failed to send a fragment announcement message to TE
RP/0/RP0/CPU0:Aug 9 14:01:50 PST: isis[1010]:
%ROUTING-IGPTE_LIB-4-DATA_QUEUE_FULL : message queue is full. Cannot accept more element.
RP/0/RP0/CPU0:Aug 9 14:01:50 PST: isis[1010]:
%ROUTING-ISIS-7-ERR_SEND_TE_MSG : Failed to send a fragment announcement message
Conditions:
Large number of TE topology change messages from ISIS peers. Issue is seen with 4000 or more tunnels.
Workaround:
Restart ISIS process
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.2.2.BASE, 5.3.0.MPLS, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.2.5.30i.BASE, 5.3.1.SP2, 5.3.2, 5.3.2.22i.BASE, 5.3.3.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw83388 | Title: | [UNI-C] NC4K tunnel creation failure when WL re-tune is required |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
OCHTrail tunnel will not come up and stays down.
Conditions:
1. Wavelength configuration isn't done on optics controller on NCS4k node.
2. To reach neighbouring NCS2k node, NCS4k has routes over multiple IPv4 interfaces.
Workaround:
Apply Wavelength configuration on optics port at NCS4k before circuit creation.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: * | 5.2.41.BASE, 6.0.1.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux71500 | Title: | OSPF adjacencies issues over ethernet unnumbered ptp links in some cases |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
OSPF adjacency does not come up over any Ethernet type of interface which has been configured as an unnumbered point-to-point link.
Conditions:
Seen on different IOS-XR platforms with different types of linecards with something like following configuration.
RP/0/RP0/CPU0:ios#sh run interface tenGigE 0/0/0/2/0
Fri Feb 12 01:10:34.657 UTC
interface TenGigE0/0/0/2/0
ipv4 point-to-point
ipv4 unnumbered Loopback0
!
RP/0/RP0/CPU0:ios#sh run router ospf 100
Fri Feb 12 01:10:43.899 UTC
router ospf 100
router-id 2.2.2.1
area 0
interface Loopback0
!
interface TenGigE0/0/0/2/0
network point-to-point
!
!
!
Workaround:
Configure IP address subnet so that the interface is still point-to-point but not unnumbered.
Further Problem Description:
This issue is applicable from 5.1.1 onwards, 5.2.x, 5.3.x and 6.0.0 releases across IOS-XR platforms.
The issue seems to have got introduce via CSCue71040 due which OSPF sends its DBD and LS pkts to unicast destination instead of the all SPF routers multicast if the point-to-point OSPF link is actually an Ethernet type of link at the media level. This was to trigger ARP resolution and reduce possible blackhole of traffic for few msec when the OSPF adjacency is formed - this however, has not been demonstrated on XR type of platforms.
When it comes to unnumbered ptp Ethernet links and sending unicast OSPF pkts as pre-route over these interfaces, we have some issues and limitations in most of the XR platforms. This causes the pkts to never go out of the router and the adjacency does not come up.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.19i.ROUT, 6.1.1.2i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy30521 | Title: * | GSR, 4.2.1, Standby PRP NSR NOT-Ready (Verizon) |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Customer was running 4.2.1 on GSR, and they observed standby PRP go into NSR NOT-Ready state after a few BGP sessions flapped.
The reason for the NSR NOT-Ready was as follows:
Details
--------
Current active rmf state: 4 (I_READY)
All standby not-ready bits clear - standby should be ready
Current active rmf state for NSR: Not ready
Reason for standby not NSR-ready
1046 0/0/CPU0 bgp BGP NSR sessions not synchronized : inst_name=default, inst_id=0
Not ready set Sun Feb 7 18:01:58 2016: 6 minutes ago
Conditions:
BGP flaps cause the standby PRP to go into NSR NOT-Ready state.
Workaround:
Shutdown and restore the peers that are causing the BGP-NSR restart on the standby PRP.
For example:
RP/0/0/CPU0:Feb 7 18:01:58.681 UTC: bgp[1046]: %ROUTING-BGP-6-NSR_RESTART: NSR has been restarted - Received tcp-oper down for nbr 159.24.197.78 while it was undergoing scoped sync
If you see the neighbor/ peer that is causing this issue, then shut and un-shutting the neighbor/ peer will help in restoring the issue.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 6.0.0.29i.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux93144 | Title: | NCS1K: ETNA PCI access recovery handling |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
SDK initialization fails for coherentDSP device due to PCI access failure. All configurations on the trunk port will fail as a result.
Conditions:
Workaround:
No workaround available.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 6.0.0.CE |
|
Known Fixed Releases: * | 6.0.1.19i.BASE, 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux97834 | Title: | 100GE traffic impact seen everytime on Ifmgr process restart on Tail |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic impacted after ifmgr restart.
Conditions:
if mgr restart.
Workaround:
none
Further Problem Description:
expected resolution : to be fixed in future releases
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE, 5.2.47.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE, 6.1.1.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39966 | Title: | M2M:Schema process is inactive after the SMU activation |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
schema-describe is not giving the schema output after mpls SMU activation and deactivation. Some schema files go inactive.
Conditions:
These issue occurs when ever the SMU is activated or deactivated.
Workaround:
Restart schema_server.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE, 6.0.0.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.1.18i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux89369 | Title: | TL1 is not reporting the alarms and conditions after alarm manager crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | TL1 is not reporting the alarms after alarm manager crash
Symptom:
Alarms not seen from TL1 after alarm manager crash.
Conditions:
Fetch alarms in TL1 after alarm manager crash.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | 6.0.1.18i.BASE, 6.0.1.18i.MPLS |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy00835 | Title: | [TL1]:Tunnel(1+1) is down created via TL1 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | [TL1]:Tunnel(1+1) is down created via TL1
Symptom:
We were setting wrong value in path protection parameter
Conditions:
Due to this Tunnel were not coming UP.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy45410 | Title: | nsh incorrecrtly encap two labels for vrf pkts, pkts dropped at next hop |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom:
On the P router, label 24006 is tag=>IP. That means the packet coming with this label should have EOS 1 set. However, in the captured packet, it comes with two labels. The top label 24006 with EOS 0. So, once it reaches the P router, the lookup of 24006 with EOS 0 will fail.
In addition to that, there are plen and original L2 header issues.
Thanks,
Ming
Packet 5
12:50:08:177165: dpdk-input
TenGigabitEthernet0/4/0 rx queue 0
buffer 0x34524f: current data 14, length 342, free-list 0, totlen-nifb 0, trace 0x4
PKT MBUF: port 1, nb_segs 1, pkt_len 356
buf_len 2304, data_len 356, ol_flags 0x0
packet_type 0x0
MPLS_UNICAST: 90:e2:ba:af:07:6c -> 90:e2:ba:9f:8c:51
ETHERNET-MPLS label 262159
12:50:08:177168: ant-input-direct-mpls
ant-input: sw_if_index 6 dst 05:dc:60:ff:07:63 src 51:ff:45:00:01:4e
12:50:08:177171: ant-ingress
ant-ingress: pkt_id 5 length 356
baf 001c5c8b0060000102005d0e01000000 vector 14 (valid 1)
first 128 bytes
00000000: 90e2ba9f8c5190e2baaf076c884705dc60ff076351ff4500014e00004000ff11 <== two labels? 24006 and 30261 plen 0x4e = 78 prot 0x11 UDP
00000020: 6c9104040404030303036b1912b6013a00000c00000400001401000601030000
00000040: 640a0000000000000000000000000000000090e2baaf076d0011010007d0803f <== original L2 header??
00000060: 0763513f45000100d7fb00003f062c56aca20102c80300ff00508a1af8bdb9e9 <== inner plen = 0?
12:50:08:177171: error-drop
ant-ingress: ant-ingress drop
With this image, for the vrf pkt traffic, it can reach to P but not forwarded to SFF:
The topology is : PE2(SC)>P >SFF
RP/0/RP0/CPU0:p#sh int TenGigE0/0/0/2 acc
TenGigE0/0/0/2
Protocol Pkts In Chars In Pkts Out Chars Out
IPV4_UNICAST 8 478 4 184 IPV4_MULTICAST 0 0 8 550
RP/0/RP0/CPU0:p#sh int GigabitEthernet0/0/0/5 acc
GigabitEthernet0/0/0/5
Protocol Pkts In Chars In Pkts Out Chars Out
IPV4_UNICAST 4 320 0 0 IPV4_MULTICAST 0 0 4 320
RP/0/RP0/CPU0:p#sh int ten 0/0/0/1 acc
TenGigE0/0/0/1
Protocol Pkts In Chars In Pkts Out Chars Out
IPV4_UNICAST 23 1532 6 314
IPV4_MULTICAST 0 0 21 1428
MPLS 2686235 918690366 0 0
RP/0/RP0/CPU0:p#
On PE2:
service-function-chaining
sff SFF
locator 1
transport vxlan-gpe
source-address ipv4 4.4.4.4 destination-address ipv4 3.3.3.3 source-port 4790 vni 20
!
!
!
path 100
10 sff SFF
!
!
Conditions:
image:
[xr-vm_node0_RP0_CPU0:~]$ cat /etc/build*txt
### XR Information
User = lucaslee
Host = ott-lb-028
Workspace = /workspace2/lucaslee/xr-dev-0321730
Lineup = xr-dev.lu%EFR-00000321730
XR version = 6.1.1.02I
### Thirdparty Information
Refpoint = thirdparty/opensource/release@tp-main/269
Hostname : calcium-99.cisco.com
Workspace : /nobackup/hetsoi/satori-wrl7.release.20160208/target-exr-gdb
Source Base : ssh://wwwin-git-sjc-2/git/thinstack/satori.git
Devline : cisco-xr-wr7
Devline Ver : 23c32d5768fa02d78079ba45b2e520791e279926
Devline Type : GIT Repository
### Calvados Information for architecture
Refpoint = calvados/release@main/17
Built By : lucaslee
Built On : Tue Feb 23 15:09:33 EST 2016
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux05164 | Title: | NCS4K :ISSU upgrade process requires too much user interaction |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Currently while performing ISSU via CTC , the ISSU dialog is opened. And after each successfull stage completion the next button has to be clicked.
Conditions:
ISSU performed via CTC.
Workaround:
Click on the next button at each successful ISSU step completion.
Further Problem Description:
Expected Resoluton:-This DDTS shall be fixed in 6.0 release.
Reproducibility (%) :- 100% ( if more than one images is present on the node in inactive list)
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw44151 | Title: | 100gige odu-flex(50,55ts..)with gfp-f mapping datapath not coming up |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
100gige odu-flex(50,55ts..)with gfp-f mapping datapath not coming up
Conditions:
Create a 100 gig odu-flex controller and xconnect it with another flex.
Workaround:
No
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.20i.BASE, 6.0.1.20i.FWDG, 6.1.1.2i.BASE, 6.1.1.2i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy20815 | Title: | [ISSU QP4]: CTC starting from XR-ISSU instead of install commit of Calv |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
CTC starting from XR-ISSU instead of install commit of sysadmin.
Conditions:
power cycle the node during the activation of Active RP at sysadmin. After reconnect to node, start ISSU from CTC.
Workaround:
commit the changes at sysadmin from sysadmin pane(install type -> sysadmin) or CLI.
Further Problem Description:
Fix available in next release.
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE, 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy45759 | Title: | pbr_ea core dump when attaching pbr policy to the bundle intf |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
------
RP/0/RP0/CPU0:p(config)#interface Bundle-Ether100
RP/0/RP0/CPU0:p(config-if)#service-policy type pbr input policy_vrf-default-mainintf_1
RP/0/RP0/CPU0:p(config-if)#commit
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RP0/CPU0:p(config-if)#show config failed errors
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface Bundle-Ether100
service-policy type pbr input policy_vrf-default-mainintf_1
!!% 'ifmgr' detected the 'try again' condition 'The operation encountered communication issues with the EA, NetIO or a remote IM. It may be retried'
!
end
RP/0/RP0/CPU0:p(config-if)#clear
Conditions:
image:
RP/0/RP0/CPU0:sff#run cat /etc/build*txt
### XR Information
User = lucaslee
Host = ott-lb-028
Workspace = /workspace2/lucaslee/xr-dev-0321730
Lineup = xr-dev.lu%EFR-00000321730
XR version = 6.1.1.02I
### Thirdparty Information
Refpoint = thirdparty/opensource/release@tp-main/269
Hostname : calcium-99.cisco.com
Workspace : /nobackup/hetsoi/satori-wrl7.release.20160208/target-exr-gdb
Source Base : ssh://wwwin-git-sjc-2/git/thinstack/satori.git
Devline : cisco-xr-wr7
Devline Ver : 23c32d5768fa02d78079ba45b2e520791e279926
Devline Type : GIT Repository
### Calvados Information for architecture
Refpoint = calvados/release@main/17
Built By : lucaslee
Built On : Tue Feb 23 15:09:33 EST 2016
Build Host : ott-lb-028
Workspace : /workspace2/lucaslee/xr-dev-0321730
Source Base : ios_ena
Devline : xr-dev.lu%EFR-00000321730
Devline Type : ACME Lineup
xr-dev EFR-00000321730 Lineup
RP/0/RP0/CPU0:sff#
Workaround:
None
Further Problem Description:
Core decode:
#0 0x00007f356dc6f5f2 in pbr_ea_pd_get_ul_ifh (ifh=134217820, ul_ifh_array=0x10, num_local_mbrs=0x7fff1476d04c) at platforms/common/gcplane/lc/feature/pbr/src/pbr_ea_gcp_iir.c:2153
2153 ul_ifh_array[ul_id] = ul_ifh;
(gdb) bt
#0 0x00007f356dc6f5f2 in pbr_ea_pd_get_ul_ifh (ifh=134217820, ul_ifh_array=0x10, num_local_mbrs=0x7fff1476d04c)
at platforms/common/gcplane/lc/feature/pbr/src/pbr_ea_gcp_iir.c:2153
#1 0x00007f356dc473a5 in caps_add_bundle_int (ifh=134217820, intf_kbps=1000000, pbr_target=0x7fff1476db00, phd=0x1b80b68, pdatahd=0x1b80c68,
intf_type=2, uidb_info=0x0) at platforms
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut35625 | Title: | rdsfs server crash on router bootup @ rdsfs_shim_plist_insert |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
rdsfs_server process crash seen on router bootup. Not seen everytime.
Conditions:
Seen on bootup
Workaround:
None. Process recovers on its own.
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.5.38i.BASE, 5.3.2.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy43587 | Title: | After nsh encap on vrf intf lookup done in vrf table instead of global |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
N/A
Conditions:
image:
RP/0/RP0/CPU0:pe2#run cat /etc/build*txt
### XR Information
User = lucaslee
Host = ott-lb-028
Workspace = /workspace2/lucaslee/xr-dev-0220
Lineup = xr-dev.lu
XR version = 6.1.1.02I
### Thirdparty Information
Refpoint = thirdparty/opensource/release@tp-main/269
Hostname : calcium-99.cisco.com
Workspace : /nobackup/hetsoi/satori-wrl7.release.20160215/target-exr-gdb
Source Base : ssh://wwwin-git-sjc-2/git/thinstack/satori.git
Devline : cisco-xr-wr7
Devline Ver : 9de2569531c938a5773add8e228d92e226534add
Devline Type : GIT Repository
### Calvados Information for architecture
Refpoint = calvados/release@main/17
Built By : lucaslee
Built On : Mon Feb 22 17:13:32 EST 2016
Build Host : ott-lb-028
Workspace : /workspace2/lucaslee/xr-dev-0220
Source Base : ios_ena
Devline : xr-dev.lu
Devline Type : ACME Lineup
xr-dev EFR-00000321691 Lineup
RP/0/RP0/CPU0:pe2#
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18272 | Title: | Incorrect value for free memory from wdsysmon reading SYSPAGE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
False alarm of critical memory state.
Conditions:
Seen rarely when free memory transitions from 4G+ (4G+100K approx) to 4G- (4G-100 approx).
If free memory is already below 4G (or physical memory it self is is < 4G) this issue will not be hit.
If free memory is well above 4G, this issue will not be hit.
Workaround:
1. When free memory is reaching 4G value, RPFO will free up the some memory which will take free memory away from 4G boundary. If free memory is already below 4G, then this issue will not be hit.
Further Problem Description:
Seen very rarely. Not hit every time free memory is around 4Gb.
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 4.1.2.BASE |
|
Known Fixed Releases: * | 6.0.1.20i.BASE, 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux87196 | Title: | skyhammer LC continuously reset due to fialc sysmgr_level_ready_timeout |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
skyhammer LC continuously reset due to fialc sysmgr_level_ready_timeout.
Conditions:
chassis reload. Reproducible
Workaround:
no
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE, 6.1.1.LC |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux74259 | Title: | FIA PON and Hardreset not working in xr-dev line up |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
FIA PON and Hard Reset is not working in xr-dev line up.
Conditions:
In present xr-dev line up code, when populating the asic instances to fit module fia the indexing of iteration of loop is wrongly initialized, that is why init for all the asic instances are not happening.
Workaround:
Corrected the indexing of for loop.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.1.20i.BASE, 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux93439 | Title: | OSPF Crash when handling LSA mask change with SR or mcast-intact enabled |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | OSPF Process crash
Symptom:
OSPF Process crash
Conditions:
OSPF Process can crash when it receives an LSA from peer where the mask got changed. for crash to happen we should have either SR or mcast intact should enable.
Workaround:
None
Further Problem Description:
Platform independent issue. Day 1 issue
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.0.ROUT, 6.1.1.ROUT |
|
Known Fixed Releases: * | 6.0.1.20i.ROUT, 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux89272 | Title: | Bundle hash for a bundle with few links down is notworking, traffic loss |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Bundle hash for a bundle with few links down is notworking, traffic loss
Conditions:
Bundle hash for a bundle with few links down is notworking, traffic loss
Workaround:
none
Further Problem Description:
Bundle hash for a bundle with few links down is notworking, traffic loss
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.FWDG |
|
Known Fixed Releases: * | 6.1.1.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux35449 | Title: | uRPF check fails for IPv6 6PE with next hop IPv4 (::ffff:ipv4) |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
CRS is dropping some IPv6 packets due to uRPF loose mode, but these packets should be forwarded, as there is entry in RIB, as below:
IPv6SrcAddr IPv6DstAddr InputInterface ForwardStatus
2600:807:320:308::3f58:64a0 2804:14c:49:2277::1 BE3 DropRPFDrop
RP/0/RP0/CPU0:intl01.atl#sh cef ipv6 2600:807:320:308::3f58:64a0
Fri Oct 2 20:47:46.643 BRA
2600:800::/27, version 47024418, internal 0x14004001 0x0 (ptr 0x74e3bf0c) [1], 0x0 (0x0), 0x410 (0x74ce9a98)
Updated Sep 9 06:58:53.917
Prefix Len 27, traffic index 0, precedence n/a, priority 4
via ::ffff:200.244.41.251, 3 dependencies, recursive [flags 0x6000]
path-idx 0 NHID 0x0 [0x720b024c 0x0]
next hop VRF - 'default', table - 0xe0000000
next hop ::ffff:200.244.41.251 via ::ffff:200.244.41.251:0
Conditions:
this happen when source IPv6 address are learned via 6PE and have a next hop as ::ffff:ipv4.
Workaround:
no workaround.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80310 | Title: | IDPROM MAC EXTN support in idprom tool |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Backplane MAC address can not be edited using the idprom_tool.
Conditions:
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.20i.BASE, 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux63412 | Title: | Unable to add an interface to a multicast vrf after sysdb_mc crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Unable to configure an interface under existing Multicast VRF after sysdb_mc crash/restart
Symptom:
Committing the config will fail with this error:
RP/0/8/CPU0:w(config-mcast-1YYY-ipv4-i)#show configuration failed
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
multicast-routing
vrf YYY
address-family ipv4
interface TenGigE0/14/0/0.43
enable
!!% Invalid VRF for this config: VRF check failed for interface
!
Conditions:
These are the conditions under which the problem can occur.
1. Configure interface under vrf A
2. Configure interface under multicast-routing vrf A
3. Restart sysdb_mc (one or more times)
4. Remove interface from multicast-routing vrf A
5. Remove and re-configure interface under vrf B
6. Configure loopback under multicast-routing vrf B
Workaround:
Restart the process ipv4_mfwd_ma on both the active and the standby RPs.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy43800 | Title: | dpc_rm has run out of thread resource with new client NSH is added |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After configuring bundle with static mac and lacp, the bundle is not up:
RP/0/RP0/CPU0:pe2#sh ipv4 int br
Interface IP-Address Status Protocol Vrf-Name
Bundle-Ether100 12.1.0.2 Down Down default
Port Device State Port ID B/W, kbps
-------------------- --------------- ----------- -------------- ----------
Gi0/0/0/2 Local Configured 0x8000, 0x0000 1000000
Bundle is in the process of being replicated to this location
Gi0/0/0/3 Local Configured 0x8000, 0x0000 1000000
Bundle is in the process of being replicated to this location
It seems dpc rm resource issue due to new feature nsh added in.
RP/0/RP0/CPU0:pe2#show controllers dpc rm trace error
2 wrapping entries (2112 possible, 64 allocated, 0 filtered, 2 total)
Feb 23 14:41:06.789 dpc_rm/error 0/RP0/CPU0 t7443 srh_send_new_thread_request : msg_send failed (0x0, 0xc)
Feb 23 14:41:06.789 dpc_rm/error 0/RP0/CPU0 t7443 gcp_prm_srh_register : send new thread request failed
RP/0/RP0/CPU0:pe2#
RP/0/RP0/CPU0:pe2#show controllers dpc rm resource thread
name work Q S msg Q M msg Q L msg Q
---------------------------------------- ---------- ---------- ---------- ----------
hq_thread 0 135 0 0
early_fast_discard_srh 0 1 0 0
uvf_mgr_dpc_rm 0 3 0 0
gcp_bundle_adj 0 0 0 0
qos_ma_ea 0 0 0 0
sunstone_tunnel_ea 0 0 0 0
sunstone_fib_mgr 0 0 0 0
qos_ea_prm_srh 0 0 0 0
sse_ipv6_ea 0 0 0 0
l3fib_ipv4 0 92382 0 0
l3fib_ipv6 0 40 0 0
sse_ip_ea 0 0 0 0
qosrm_srh 0 1 0 4
lpts_pd_prm_srh_client 0 1486 0 0
gcp_aib_prm_async_hndlr 0 10 0 0
fib_mpls_ea 0 0 0 0
sunstone_vlan 0 0 0 0
pfilter_ea_prm_srh 0 0 0 0
pfilter_ea_ipv4 0 0 0 0
sunstone_uidb_svr 0 0 0 0
licensing 0 1 0 0
sunstone_if_driver 0 0 0 0
pbr_ma_ea 0 0 0 0
pbr_ea_pd 0 0 0 0
sunstone_vether_ea 0 0 0 0
RP/0/RP0/CPU0:pe2#
Conditions:
image:
RP/0/RP0/CPU0:pe2#run cat /etc/build*txt
### XR Information
User = lucaslee
Host = ott-lb-028
Workspace = /workspace2/lucaslee/xr-dev-0220
Lineup = xr-dev.lu
XR version = 6.1.1.02I
### Thirdparty Information
Refpoint
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux31609 | Title: | Unidirectional Traffic,thru DWDM link, hit during Active RP(RP0) reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Unidirectional traffic glitch is observed during active RP reload.
Conditions:
Reload active RP
Workaround:
NONE
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.20i.MPLS, 6.1.1.3i.MPLS |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy50809 | Title: | ARP not getting resolved on glean adjacency on NCS4K |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
ARP not getting resolved on glean adjacency on NCS4K
Conditions:
ARP not getting resolved on glean adjacency on NCS4K
Workaround:
Add static ARP entry for glean adjacency
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux14938 | Title: * | NCS1K: Syncloss in 100G FEC mode |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
After preprovisioning one or more 100G client ports report sync loss
Conditions:
FEC should be enabled on both the ends
Workaround:
No reliable workaround is preset. Following are few things that can be tried
Resettign FEC configuration on client
Bring down-> bringup of Spirant ports (remote ports)
Further Problem Description:
NA
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: * | 1.0 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy50802 | Title: | ARP not getting resolved for glean adjacency |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom:
ARP not getting resolved for glean adjacency on NCS4K
Conditions:
ARP not getting resolved for glean adjacency on NSC4K
Workaround:
Add static ARP entry for glean adjacency
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv62992 | Title: | Diag Not Taking the Faulty Plane OOS |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Diag Not Taking the Faulty Plane OOS
Conditions:
-fabric card had issue,
-diag did not zero'd to correct fabric plane
- GASPP simulation method was used to get closer to customer scenario.
Workaround:
shut/unshut the respective faulty plane from admin config.
Please use the inline command for the same.
(admin-config)#controllers fabric plane <> shutdown
(admin-config)#commit
(admin-config)#no controllers fabric plane <> shutdown
(admin-config)#commit
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 5.3.3.CE |
|
Known Fixed Releases: | 6.0.0.13i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux90909 | Title: | MVPNGREv6 over v4-MRIB crash at standby encap PE on sending unjoin/join |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Mrib crash
Conditions:
We have seen mrib crashes and tracbacks in 533 release due to retry logic. Also made few changes in mrib PI and PD code. Need to apply 533 fixes into 532.
Workaround:
A
Further Problem Description:
mrib crash is observed. We have seen mrib crashes and tracbacks in 533 release due to retry logic. Also made few changes in mrib PI and PD code. Need to apply 533 fixes into 532.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 5.3.2.LC, 5.3.2.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv87636 | Title: | VZ LE1A - shelf_mgr Rack number config unavailable Shutting down rack |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
RP's are shut.
shelf_mgr Rack number config unavailable Shutting down rack
Conditions:
Power Cycle of the Chassis. Hit once in 10 back to back power cycles
Workaround:
Power Cycle the Chassis
Further Problem Description:
On some of the power cycles, when both the RP's trying to read chassis IDPROM. One of the RP's fail to read IDPROM, hence to prevent system booting with fake data, Chassis is shutdown.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux34331 | Title: | ARWEN: Configuration stuck in pre configuration mode for very long time. |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Configuration stuck in pre configuration mode for very long time.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw31471 | Title: | 10G interface down issue due to Phy Init failure |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When the SW Init fails, mechanism to reinit the hw is not present and hence the interfaces may not come up
Conditions:
The SW Init might fail due to NRS client timeout, IPC timeout. So this causes the hardware to be not initialized and hence the interface will remain in down state
Workaround:
Workaround is reload the LC. Process restart will not solve the problem as it will not reinitialize the hardware
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 5.3.3.LC |
|
Known Fixed Releases: * | 5.3.3.15i.FWDG, 6.0.1.12i.FWDG, 6.1.0.9i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj64875 | Title: | MMRP: LC L2FIB_MGR not able to recover from OLE OOR state |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Multicast and L2VPN may not pass traffic.
Also one will see " MCAST XID" in alarm for l2vpn via show l2vpn forwarding resource location <>
RP/0/RSP0/CPU0:RTR#show l2vpn forwarding resource location 0/2/cpu0
L2VPN forwarding resource availability summary state: YELLOW
shared memory resource: GREEN
AC hardware resource: GREEN
MPLS hardware resource: GREEN
PBB PORT hardware resource: GREEN
NHOP hardware resource: GREEN
L2TP hardware resource: GREEN
L2TP_SESSION hardware resource: GREEN
VFI hardware resource: GREEN
BRIDGE hardware resource: GREEN
BRIDGE SHG hardware resource: GREEN
BRIDGE PORT hardware resource: GREEN
BRIDGE MAC hardware resource: GREEN
MSTI MAIN PORT hardware resource: GREEN
BRIDGE MAIN PORT hardware resource: GREEN
MCAST TABLE hardware resource: GREEN
MCAST LEAF hardware resource: GREEN
MCAST XID hardware resource: YELLOW <<<<<<<<<< see here
PBB BMAC SA hardware resource: GREEN
DHCP hardware resource: GREEN
MCAST XID LIST hardware resource: GREEN
SPAN hardware resource: GREEN
G8032 RING hardware resource: GREEN
G8032 RING INST hardware resource: GREEN
GLOBAL hardware resource: GREEN
EVPN MCAST LEAF hardware resource: GREEN
EVPN MCAST OLE hardware resource: GREEN
Conditions:
Running L2VPN and Multicast. In addition, alot of network flaps on a L2VPN/Multicast link that is carrying traffic.
Workaround:
Recovery: Reload the line card in question with the resource alarm
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 5.1.11.BASE |
|
Known Fixed Releases: * | 5.1.11, 5.1.11.13i.FWDG, 5.1.2, 5.1.2.13i.FWDG, 5.1.3, 5.1.4, 5.2.2, 5.2.2.14i.FWDG, 5.2.21, 5.3.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22024 | Title: | inst_mgr crash at ctrace_internal on ncs1k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
process crash of inst_mgr
Conditions:
while doing install add of rpm's
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.0.0.ADMIN |
|
Known Fixed Releases: * | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux53684 | Title: | NCS4k:WaitTo Restore timer is displayed in Milliseconds in Netconf reply |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The protection profile timer - wait to restore is displayed in Milliseconds in the Netconf walkdata command .
Conditions:
While creating the Protection profile the wait to restore timer is configured in seconds with the range <0-720>. However on commit of the configuration , the wait to restore timer value is converted to Milliseconds and is displayed in Milliseconds in the Netconf o/p.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.16i.BASE, 6.0.1.16i.FWDG, 6.0.1.16i.MPLS, 6.0.1.17i.BASE, 6.0.1.17i.FWDG, 6.0.1.17i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw55367 | Title: | Breakout ODU line loopback need to be blocked in CTC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Line loopback is allowed for breakout ODU or OTU controller which should be blocked
Conditions:
Provision Line loopback on breakout ODU or OTU controller
Workaround:
NONE
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux26079 | Title: | PREFEC & POST FEC BER will show up on non supp platforms |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PREFEC & POST FEC BER will show up on non supp platforms
Conditions:
Execute show pm CLI for otu controller ,fec layer
Workaround:
None
Further Problem Description:
to be fixed in future release
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE, 6.0.1.17i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw65191 | Title: | Unicast IPv6 NS sent to mcast mac address |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IPv6 neighborship are timing out, causing potential ULP to flap
Conditions:
Problem observed on CRS-1 running 5.3.x releases
Workaround:
Hardcode IPv6 neighbors on local AND remote router(s)
Further Problem Description:
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 5.3.1.ROUT |
|
Known Fixed Releases: * | 5.3.3.16i.FWDG, 6.0.1.12i.FWDG, 6.1.0.4i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv76195 | Title: | Seeing IDT message when smart licensing is disabled |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
We are continuously seeing IDT message in every 3 minutes when smart licensing is disabled in the full images.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 5.4.0.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.0.1.7i.BASE, 6.1.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw81456 | Title: | Memory leak from responder/ippm proc show commands |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Memory leak from the ipsla responder/ippm process
Conditions:
Use on the ip sla responder box the following show commands:
show ipsla responder statistics all ports detail or
show ipsla twamp session or
show ipsla twamp connection
Workaround:
Restart the ipsla_responder/ipsla_ippm_server processes to free up the memory.
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.MGBL, 6.1.0.10i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv92854 | Title: | CSCuv92854Java 1.8 security changes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Changes required from CTC to launch on Java 1.8
Conditions:
Changes required from CTC to launch on Java 1.8
Workaround:
NA
Further Problem Description:
Changes required from CTC to launch on Java 1.8
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: * | 5.2.47.BASE, 5.4.0.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut28478 | Title: | 'show inventory raw' should indicate presense/absense of SSD's of ECU |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
The disks of ECU are listed in the inventory with no indication of their presence.
Conditions:
This is applicable to any NCS4K system with ECU module.
Workaround:
No workaround available.
Expected Resolution: Please check with the support engineer for information on which release(s) this bug is expected to be fixed.
Reproducibility (%): 100%
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv15157 | Title: | To Support new feature "Fast Circuit Creation" for release 6.0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
To introduce feature of fast circuit creation in 6.0 release.
Conditions:
now user can create the circuit through fast circuit creation wizard also.
Workaround:
circuit can also be created through Network view > OTN > Create circuit.
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: * | 6.0.0.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo74445 | Title: | Show controller fabric plane all statistics has E-D on Fc reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
UCE cells conter increase unexpectedly.
Conditions:
on FC reload
Workaround:
this is cosmetic issue, no work around is needed
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.2.1.ADMIN |
|
Known Fixed Releases: * | 5.2.1, 5.2.1.25i.BASE, 5.2.2, 5.2.2.13i.BASE, 5.2.21, 5.3.0, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz53893 | Title: | Packets interface counters are incorrect for bundle VLANs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Egress data rate seen when executing Show interface <> fluctuates drastically when the interface is a VLAN/Bundle VLAN on 10GE fixed PLIM.
Conditions:
The issue happens under following conditions:
1. Vlan interface or a bundle member is a vlan interface on 10GE Fixed PLIM card
2. The traffic flowing through the interface consists mostly of MPLS.
3. Load interval configured is 30 seconds
4. Periodic query via a script with a period less than 30seconds
Workaround:
Do not change load interval and periodic query using a CLI/XML should be done only every 60seconds.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.1.2.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.23i.BASE, 4.2.4, 4.3.0, 4.3.0.20i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus17645 | Title: | Multicast for Sparse-Mode is dropped on Egress PE after SPT switchover |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Multicast for Sparse-Mode Group is dropped on Egress PE router after SPT switchover
Conditions:
SPT switchover must occur
Switchover from mLDP-based core tree to PIM-based core tree must occur.
Workaround:
Configure spt threshold infinity so that SPT switchover does not occur.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.0.MCAST |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.17i.BASE, 5.3.1.17i.FWDG, 6.0.0.5i.BASE, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue12028 | Title: | Available lic not bound to needed LC after move out from allocated state |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After a license feature back to license pool from slot1 , it does not bound to slot0, it keeps the license in available state.
Conditions:
Licensed feature with more than one slot available where it can be configured.
Workaround:
None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 3.8.3, 3.8.4, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur11147 | Title: | 47Graceful OIR of the standby PRP causes NSR LDP sessions to Flap |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LDP sessions fail
Conditions:
Performing a graceful OIR on the Standby PRP.
Workaround:
1. Reload the Standby RP via the CLI.
2. Set the config-register of the PRP to be removed directly by using:
admin config-register location
For example:
admin config-register 0x0 location 0/RP1/CPU0
The current value can be checked through "admin show variables boot location ".
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.3.MPLS |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.10i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue79225 | Title: | admin DN L2 subIf, sh l2vp for int det rxPkt/B decr for Trid not for Typ |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After a L2 main/sub interface is shut down, the AC Receive stats counter becomes reliable in the output of "show l2vpn xconnect ".
Conditions:
When the L2 interface is on Trident LC and traffic keeps received on the interface after it is shut down.
Workaround:
None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.1.24i.BASE, 4.3.2, 4.3.2.11i.BASE, 4.3.2.9i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.2i.BASE, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue35606 | Title: | Static Route Hardware forwarding is broken, next hop flaps |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In ASR9K, hardware forwarding is broken when next hop in static route is flapped between directly connected to MP-BGP and then back to directly connected.
Conditions:
R1----PE1----R2-
PE1----PE2---R2
Above has IBGP session between PE1 and PE2.
R1 has two paths to R2, one via PE1 to PE2 to R2
and other via PE1 to R2 directly.
When PE1 to R2 link is shut, then R2 is reachable via PE1 to PE2 IBGP path which is labelled path.
When PE1 to R2 link is brought up (no shut) then R2 is accessible back again via IP nexthop of PE1
directly connected to R2.
A recursive static route which is reachable over a labelled iBGP path
transitions to a static recursive route via a directly connected IP nexthop (instead of labelled path).
ASR9K is running 4.2.1 , 4.2.3 or 4.3.0.
Workaround:
Clear the route.
Adding physical interface in the static route configuration can prevent the issue.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.FWDG |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.27i.BASE, 4.3.2, 4.3.2.11i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.3i.BASE, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtl91984 | Title: | ASIC SCAN SERVER fails to reset line card after asic scan |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom: CRS MSC-40/FP-40 card is not reset after finishing ASIC scan for any ASIC fault
Conditions:
ASIC errors, that need ASIC scan, happening on MSC-40/FP-40.
Workaround:
Manual reload of the card as board has already encountered critical ASIC error.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.0.0.BASE |
|
Known Fixed Releases: * | 4.1.1, 4.1.1.12i.BASE, 4.1.2, 4.2.0, 4.2.0.1i.BASE, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCth46827 | Title: | ROUTING-BGP-3-NEGCOUNTER : [13] : Negative path msg upon stdby reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The following ios message is seen:
RP/0/RP1/CPU0::Jun 22 16:39:29.256 : bgp[137]: %ROUTING-BGP-3-NEGCOUNTER : [13]
: Negative path or bestpath counter for peer x.x.x.x
Condition:
While working on CSCtd23495, we came to know that, unlike other counters such
as pfx_accepted, pfx_bestpaths never gets set to 0.
It means that once pfx_bestpaths gets incremented or decremented wrongly, there
is no way to clear the error and the error is inherited to subsequent sessions
even after session flaps.
Hence, to limit the error within a session's lifetime, we introduced
'pfx_bestpths = 0' when we change bgp state into established.
The assumption here is that paths learned from a certain neighbor can exist as
bestpaths only during the session's lifetime.
This DDTS reports that the assumption above fails when GR is configured.
When GR is configured, we keep the paths learned from a certain neighbor as
STALE bestpaths till route_purge_timer expires.
Workaround:
If the messages are consistent -
De-config and re-config of the neighbors should recover from the problem
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 3.9.2.ROUT |
|
Known Fixed Releases: * | 3.9.2, 3.9.2.14i.ROUT, 3.9.3, 4.0.1.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts68583 | Title: | sh tech l2vpn broken in 4.0.0.10I |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Failed to collect the output of "show controllers pse stat location " in show tech l2vpn.
Conditions:
N/A
Workaround:
Collect the information manually.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.0.0.ROUT |
|
Known Fixed Releases: * | 4.2.0, 4.2.0.20i.FWDG, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2, 4.3.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux93150 | Title: | pmipv6d crash when we execute show ipv6 mobile pmipv6 lma heartbeat |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Execute "show ipv6 mobile pmipv6 lma heartbeat" with more than 300 bindings
Conditions:
pmipv6d process crash
Workaround:
Don't execute "show ipv6 mobile pmipv6 lma heartbeat" with more than 300 bindings.
Further Problem Description:
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 5.3.3.24i.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut01674 | Title: | Commit Delay While Configuring Strict mode URPF |
|
Status: * | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
urpf configuration commit is taking time for 32 interfaces with huge scale.
Conditions:
Workaround:
The dealy is due to backwalks that's happening to igp and bgp leaves for the set of prefixes installed. The backwalks cannot be avoided and the delay is expected.
Further Problem Description:
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw82287 | Title: | Change TE flooding algorithm with fixed threshold |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:With implementation prior to this fix, the thresholds defined for flooding are hard/fixed ones. Any point the bandwidth reserved crosses up/down a defined threshold - ISIS update is triggered. These leads to significant flooding within the ISIS Domain.
The ISIS flooding update happens at the wrong time and too excessively which causes a lot of unnecessary network activity and causes RSVP-TE signaling instability and
churn.
The amount of flooding done by current cisco devices in network ~ 25-30 devices is greater than 600 Juniper devices in customer core network.
Conditions:Cisco device doing an role of an LSR or LER.
Workaround:There are no workaround.
More Info:This fix provides a relative threshold for flooding - which optimizes the amount of flooding within the ISIS domain.
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: | 6.0.1.14i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux18570 | Title: | Add minimum clock class for PTP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR9K PTP slaves/BC accepts any PTP clock class advertised by the master. This behavior results in accuracy issues during failure scenarios with GPS/Grandmaster. Need an option to control this behavior and reject inferior clock class values.
Conditions:
ASR 9K router acting as PTP Slave or boundary clock.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.24i.BASE, 6.0.1.12i.BASE, 6.1.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy10923 | Title: | pim, pim6 duplicate registration after RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
pim, pim6 duplicate registration message from new Active RP on doing RPFO.
Conditions:
Multicast-routing should be enabled
Workaround:
None. no impact.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: * | 6.0.1.19i.BASE, 6.0.1.19i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw07619 | Title: | mpls_static process gets hang and cause cpu usage increase |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
mpls_static process cpu usage spiked to 25%
Conditions:
When bundle interface flaps, the interface handle for the same interface gets changed. This might cause to be in indefinite loop which will increase cpu usage.
Workaround:
process restart mpls_static
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.11, 5.1.12, 5.1.2, 5.1.3, 5.1.4, 5.2.0, 5.2.1, 5.3.2.SP2, 5.3.3.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv84419 | Title: | 532: Seeing bundlemgr crash after router reload command was issued |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:Bundlemgr process crash on reload
Conditions:The crash is seen on router/rack reload.
Workaround:No workaround.
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 6.0.0.17i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux80461 | Title: | eXR Skyhammer not up due to ERROR while getting interface flags |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
eXR P4 Skyhammer cannot be brought up and it stuck at power-on
Conditions:
router reload
Workaround:
source ./etc/rc.d/init.d/update_mac.sh
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 6.1.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw28784 | Title: | IGMP Snooping Table Out-of-Sync on Standby |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In an nV Satellite ring topology, IGMP Snooping table is not synchronizing from active to standby node. ICCP session is up and we see IGMP Snooping as an enabled application in ICCP but the groups are not in sync.
See BigDescription note.
Conditions:
nV Satellite
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.28i.BASE, 5.3.2.SP2, 5.3.3.11i.BASE, 6.0.0.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw02159 | Title: | No schema path for show static and its options |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
No schema exists so these CLI cannot be used via json-rpc /netconf
Conditions:
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 21-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw39764 | Title: | RPL umbrella SMU |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP crash and a failover will be seen
Conditions:
RPL changes trigger the crash
Workaround:
Don't change RPL
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.SP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66931 | Title: | show tech rpl shows incorrect info for all uses all cmd output |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:RPL related issues on 5.3.1 the show tech routing rpl is in broken state and does not contain any valid information to nail down the issue.
Conditions:when customer hits RPL issues.
Workaround:None ; apart from running separate show commands.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: * | 5.2.5.37i.ROUT, 5.3.1.SP2, 5.3.3.20i.ROUT, 6.0.0.20i.ROUT, 6.0.1.12i.ROUT, 6.1.0.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv12836 | Title: | IOS XRv 9000: call-home on-demand sending inventory failed with email |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Call-home on-demand sending inventory failed with email transport method.
Conditions:
Transport method used is email.
Workaround:
Use http transport method.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.4.0.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux96718 | Title: | [533-27i]IPV6 ND not being resolved on many subinterfaces |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Post reload of the router, IPv6 ND on many of the sub-interfaces are in INCMP state.
Since the ND state in incomplete, the adjacency are not complete and results in traffic drop
Conditions:
Problem is observed after a router reload
Workaround:
OIR the linecard where the problem is seen
Further Problem Description:
Use the below command to identify if this problem has been hit.
RP/0/RP0/CPU0:ios#show ipv6 neighbors | inc INCMP
2002::6701:51fa 7 0000.0000.0000 INCMP Te0/2/0/0.2332 0/2/CPU0
2002::6701:530a 4 0000.0000.0000 INCMP Te0/2/0/0.2366 0/2/CPU0
2002::6701:3d12 0 0000.0000.0000 INCMP Te0/5/0/3.2003 0/5/CPU0
2002::6701:3d1a 4 0000.0000.0000 INCMP Te0/5/0/3.2004 0/5/CPU0
2002::6701:3d22 17 0000.0000.0000 INCMP Te0/5/0/3.2005 0/5/CPU0
2002::6701:3d2a 4 0000.0000.0000 INCMP Te0/5/0/3.2006 0/5/CPU0
2002::6701:3d32 13 0000.0000.0000 INCMP Te0/5/0/3.2007 0/5/CPU0
2002::6701:3d42 2 0000.0000.0000 INCMP Te0/5/0/3.2009 0/5/CPU0
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux62803 | Title: | PMC Channel provisioning api must not be called again if already provisi |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PMC SDK crash is seen in case channel provision API is called again for already provisioned channel.
Conditions:
In case of HA scenarios, PMC channel provision API is called again when first time channel provisioning is failed.
Workaround:
Line card reload will recover the issue.
Further Problem Description:
Issue is 100% reproducible in case channel provisioning is failed.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.2.41.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE, 6.1.1.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy01409 | Title: | G.8265.1: Clock class not updated in response to QL change |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The PTP clock-class advertised in Announce messages is not updated in response to a change in the local clock's QL value, when using G.8265.1. Note that show commands may display the correct clock-class, but the wrong value is sent in PTP packets.
Conditions:
When using the G.8265.1 PTP profile with a Synchronous Ethernet or clock-interface input, the clock-class advertised in PTP Announce messages may not change if the SyncE or clock-interface input's QL changes.
Workaround:
Restart the ptp_ctrlr process on the active RP.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux88472 | Title: | [TL1]:Not able to retrieve 10gige controller alarm |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | [TL1]:Not able to retrieve 10gige controller alarm
Symptom:
Ethernet and sonet alarms were not coming in retrieve alarm command
Conditions:
Fetch Ethernet and Sonet alarms in TL1 by retrieve alarms command.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | 6.0.1.18i.BASE, 6.0.1.18i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy42724 | Title: | NCS4K FREQ values should be compatible with that of NCS2K |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
FREQ value shown upto 1 decimal place.
Conditions:
Retrieve optics information on NE.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux95168 | Title: | CTC - Edit ciruit window working path remains grey if WTR is active |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
In Edit circuit window Working path remains Grey even if Working path is healed and WTR is active.
It is synched to purple, if the screen is refreshed.
Conditions:
CTC - Edit ciruit window working path remains grey if WTR is active
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux93543 | Title: | TL1: NA/NR should be removed from rtrv-cond-all & rtrv-cond-mod section |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | TL1: NA/NR should be removed from rtrv-cond-all & rtrv-cond-mod section
Symptom:
1.In RTRV-COND- section NA/NR has been removed and example has been corrected In TL1 inter face doc.
2. In RTRV-COND- section , NA/NR has been removed and example has been corrected in TL1 interface doc.
Conditions:
changes done in TL1 interface doc.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux88495 | Title: | [TL1]:NS is coming in notification of controller rather then NSA |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | NS is coming in notification of controller rather then NSA
Symptom:
In autonomous alarms NS were coming in place of NSA
Conditions:
Now In autonomous alarms correct value is cumming.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | 6.0.1.18i.BASE, 6.0.1.18i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux47743 | Title: | Missing EG flag on mcast egress LC cause traffic blackholing |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Multicast traffic outage for specific (S,G) entries
Conditions:
Multicast with PIM-SM deployment. PIM Assert-like scenario has to be present (packet has to be received on a Forwarding interface) and MFIB on the Linecard has to disconnect/reconnect with MRIB on the RP/RSP.
Workaround:
clear pim topology to recover from the issue
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: * | 3.8.3, 3.8.4, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux95919 | Title: | CTC EDIT ODU UNI 1+0 circuit configure a protection profile |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When CTC user try to EDIT an ODU UNI unprotected circuit wizard contains a protection profile (greyed) that is configured on the device after Apply changes.
Conditions:
CTC EDIT ODU UNI 1+0 circuit configure a protection profile.
Workaround:
Remove path-protection profile from CLI.
Further Problem Description:
Reproducibility : 100%
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy47011 | Title: | One higher value shown always in second decimal place for FREQ |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
2nd decimal place in frequency is increased by 1 even when the 3rd decimal place is less than 5.
Conditions:
Configure frequency value for which 3rd decimal place is less than 5 and retrieve the same.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy19873 | Title: | named tunnel has double path-option configure knob |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: * | Symptom:
mpls traffic-eng named tunnel has double path-option configuration knob
Conditions:
configure mpls traffic-eng named tunnel
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 26-FEB-2016 |
|
Known Affected Releases: | 6.0.1.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup96426 | Title: | OSPFv3 Max-Metric doesn't apply to inter-area router LSA(type 4) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:The router doesn't apply correct cost to inter-area router LSA (Type 4), when OSPFv3 Max-Metric is configured.
There is a mem leak also in function ospfv3_send_iartr_lsa. when we generate the inter area router LSA.
Conditions:On platforms with x86 processors, the metric of type-4 LSAs doesn't change upon entering or leaving max-metric mode.
On platforms with ppc processors, the metric is changing, but not to the desired value for type-3 and type-4 LSAs.
when we are sending the inter area router LSA via function ospfv3_send_iartr_lsa we first looks into the database to get the LSA. but the dest router ID which we passed does not convert in to host order. due to that we will not find LSA in the database. later when we again do a search we passed the converted dest rtr ID and see the LSA in DB.
due to that we are leaking memory
Workaround:There is no workaround. leak is basically for 32 bytes and if the network is not churning it will not create a big mem leak. check whether network is stable or not.
More Info:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 5.2.2, 5.2.2.23i.ROUT, 5.2.21, 5.2.3.8i.ROUT, 5.3.0, 5.3.0.8i.ROUT, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux51133 | Title: | calvados show install log modifications |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
show install log doesn't populate pkg list
Conditions:
when wild-card is given in the install operaiton
Workaround:
not to provide wild-card
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum23878 | Title: | SYSDB-SMC-7-TIMEOUT_RINFO on loading acl scale configs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Conditions:
Workaround:
Expected Resolution: Please check with the support engineer for information on which release(s) this bug is expected to be fixed.
Reproducibility (%):
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux17684 | Title: | same binding-sid config can result srte tunnel up without binding label |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
multiple srte tunnel configured with same binding-sid result some srte tunnel up without binding label
Conditions:
multiple srte tunnel configured with same binding-sid
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.1.1.MPLS |
|
Known Fixed Releases: * | 6.1.1.3i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18491 | Title: | traffic loss after nsf ietf switchover due to ISIS-LSD conn timeout |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
brief traffic loss after switchover with isis segment routing configuration and nsf ietf enabled.
Conditions:
this happens when isis nsf ietf is configured.
Workaround:
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.ROUT |
|
Known Fixed Releases: * | 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy29905 | Title: | optics info not shown in show inventory for Coral |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
inventory information is not shown for 2x100, 5x40 Flex PLIM on CRS-X when running command "show inventory location LC"
Conditions:
None. Specific to 2x100, 5x40 Flex PLIM,
Workaround:
Do a "show inventory" instead of "show inventory location <>"
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux17699 | Title: | verbatim srte tunnel should not reopt by periodic timer |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
verbatim srte tunnel re-optimize when periodic re-optimize timer expires
Conditions:
mpls periodic re-optimize timer expires
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.1.1.MPLS |
|
Known Fixed Releases: * | 6.1.1.3i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy35971 | Title: | SR: extend time period to keep a protected adj-SID after link failed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OSPF keeps a protected Adjacency-SID in the fib for five minutes after an adjacency fails, to allow TE to reprogram any tunnels that may be relying on the backup path. A customer has requested that this be extended to 15 minutes to allow more time for SDN controllers.
Conditions:
Traffic engineering tunnels using Segment Routing protected adjacency-SIDs
Workaround:
None
Further Problem Description:
This is not a bug/problem but a late change in requirement.
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: * | 6.0.1.20i.ROUT, 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy33320 | Title: | MPLS TE tunnels not seen as OSPF interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Some TE tunnels with verbatim option are not appeared in RIB after software upgrade from 4.0.3 to 5.1.2 software version (autoroute announce is configured):
Checked "show mpls traffic-eng tunnels 291 detail" output see "Signaling Area: No IGP" when "verbatim" is configured.
show mpls traffic-eng tunnels 291 detail
Instance: 9, Signaling Area: No IGP <<<<<<<<<<<<<<<<<<<
Uptime: 10:17:20 (since Wed Feb 10 02:48:15 WIB 2016)
Outgoing Interface: Bundle-Ether2, Outgoing Label: 16670
Router-IDs: local 118.98.8.140
downstream 118.98.8.139
Conditions:
Reload of the device
Workaround:
Tunnel is appeared in RIB only after deleting 'verbatim' option from explicit path
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.1.2.MPLS |
|
Known Fixed Releases: * | 6.1.1.3i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy36260 | Title: | autoroute exclude prefix set change leads to large traffic outage |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Appling a Route-policy with prefix-set under ospf mpls traffic-eng causes large traffic drop as all ospf routes are purged and need to be re-installed.
Conditions:
1. appling a Route-policy with prefix-set under ospf mpls traffic-eng 2. prefix-set is modified for existing Route-policy under ospf mpls traffic-eng
Workaround:
Cost Out the router while making these changes to avoid the impact.
Further Problem Description:
This is day 1 issue on how this feature works and is applicable for all XR platforms.
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.CE |
|
Known Fixed Releases: * | 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux51713 | Title: | Incorrect profile gets edited if sorting is done by other than name |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
After sorting the table on column other than name, editing a profile edits some other profile.
Conditions:
Open the protection profile pane.
Workaround:
Reopen the pane and edit the profile or do not sort on any other profile apart from name.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux73069 | Title: | NCS4K VZ :CTC zoom feature doesn't work with mixed NCS-2K and NSC-4K |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Switching between the nodes and then from 2K to 4K, zoom does not work on 4K node.
Conditions:
Open CTC node view in network having mixed types of nodes 2K and 4K.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu91846 | Title: | Netconf-Yang: optics-ma to migrate to edm_get_items_fn() |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Sometimes doing a 'get' on optics-oper xml or yang model will result in Invalid Argument as output.
Conditions:This is random - it seems to work initially and then starts to fail after some time.
Workaround:None
More Info:N/A
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | 6.0.1.15i.BASE, 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy31225 | Title: | Anclagon gets stuck in Powerd_ON if reloaded during CCC-Power-on upgrade |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
Anclagon gets stuck in Powerd_ON if reloaded during CCC-Power-on upgrade
Conditions:
Anclagon gets stuck in Powerd_ON if reloaded during CCC-Power-on upgrade
Workaround:
Further Problem Description:
Ancalgon fabric gets stuck in Powerd_ON state , when corresponding fabric is reloaded while CCC-Power-on FPGA upgrade is in progress.
Fabric does not get booted with golden FPGA when primary is corrupted & gets stuck in Powered ON state.
0/FC0 NCS4016-FC2-M POWERED_ON N/A NSHUT
0/FC1 NCS4016-FC2-M OPERATIONAL N/A NS
sysadmin-vm:0_RP0# show controller ccc bootflash info location 0/FC0
Mon Feb 15 13:39:23.118 UTC
CCC Bootflash information for: 0/FC0
HW Info:
Manufacturer ID: Micron (0x20)
Device Size : 32 MB
Programmed Content:
Secure
Size Boot
Image Name Version Build Date (bytes) Enabled Note
======================== ========= ========== ========= ======= ======
CCC Power-On 1.01 10/06/2015 14216 N/A Active
CCC FPGA 1.12.0 12/15/2015 3318584 N/A Active
Secure Boot Certificates 1.00 06/13/2013 1047 N/A
CCC FPGA (Backup) 1.12.0 12/15/2015 3318584 N/A
CCC Power-On (Backup) 1.01 10/06/2015 14216 N/A
|
|
Last Modified: | 01-MAR-2016 |
|
Known Affected Releases: * | 1.00 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy50384 | Title: | bgp import processing delay |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP import processing takes 10sec to kick in.
Conditions:
There are two path to the destination. There are two next-hop for the best path.
One is connected and another is BGP route.
Workaround:
filter BGP route
Further Problem Description:
|
|
Last Modified: | 01-MAR-2016 |
|
Known Affected Releases: | 4.2.3.ROUT, 5.3.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsz99203 | Title: | CRS FQ - BP enabled msg displayed on group 0 with all LC shut in group |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When no active MSC in group 0 on FullQ, permanent backpressure errors on all the MSCs available in the bottom group 0 are seen.
Conditions:
New setup FullQ w/o LCs or all LCs in the bottom group 0.
Workaround:
Have one LC brought up in slot 0-7.
Further Problem Description:
It's been seen many times upon 3.6.x new setup, not seen before 3.6.x so far.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 3.8.1.BASE, 3.8.2.BASE, 3.8.4.BASE, 4.0.0.ADMIN, 4.0.1.BASE |
|
Known Fixed Releases: * | 4.0.2.11i.BASE, 4.1.0.24i.BASE, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy10060 | Title: | NCS4K fpd server core after swapping WDM and 2x100 CPAK card |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
fpd-server restarts multiple time after swapping DWDM and 2x100 CPAK module.
Conditions:
Load the image with DWDM and 2x100 CPAK module
swap these two cards.
Workaround:
Avoid swapping above two cards.
Further Problem Description:
NCS4K fpd server on xr will restart multiple time, if you swap DWDM and 2x100 CPAK card. Avoid doing swap unless absolutely necessary. If issue is hit, reload the system.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtk77030 | Title: | Remove Default LineCode display in "show controller" output |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
"show controller" output displays the default linecode for channelized T1 lines as well.
Conditions:
It is getting displayed in the "show controller" output itself.
Workaround:
none
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 4.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy20806 | Title: | CTC is able to edit circuit with incomplete status |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
CTC allowing to edit an incomplete circuit.
Conditions:
Open circuit tab and try to edit an Incomplete circuit.
Workaround:
None
Further Problem Description:
Issue reproducible
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy14815 | Title: | CTC shall remove NCS4K-2H-W (DWDM) Line Card from PRBS config |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
PRBS config should not allow DWDM LC.
Conditions:
Configure PRBS from CTC.
Workaround:
NA
Further Problem Description:
Reproducibility 100%
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy49367 | Title: | L2VPN xconnect became cpwVcIndex:0 after removing unrelated PW |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
cpwVcIndex associated to a PW becomes 0 and as such cannot be queried from SNMP
Conditions:
When unconfiguring a PW, the cpwVcIndex mapping of an unrelated PW could be lost. Exact conditions are unknown
Workaround:
2 Workarounds:
- process restart l2pvn_mgr
- unconfigure and reconfigure the PW with cpwVcIndex=0
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.3.2.FWDG |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub15695 | Title: | SPA Silent shutdown in INVMGR on CRITICAL_HI temp |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: * |
Symptom:
SPA shutdown without any visible syslogs or alarms at extreme environmental conditions.
Conditions:
Workaround:
Further Problem Description:
invmgr shuts down the SPA's whenever critical environmental condition occur. This is done without
any syslogs or alarms being notified. This might look like a silent shutdown of SPA.
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 3.8.4.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz89430 | Title: | Misleading sys log for ipodwdm process after cluster failover |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * |
Symptom:
After cluster fail-over, ipodwdm generate misleading syslog
RP/1/RSP0/CPU0:May 14 12:08:47.312 : insthelper[65]: issuagnt_node_role_change_handler Go active
RP/1/RSP0/CPU0:May 14 12:08:47.336 : ipodwdm[277]: %L2-G709-6-INFO : /harddisk:/ipodwdm_log Already present
RP/1/RSP0/CPU0:May 14 12:08:47.379 : ipodwdm[277]: %L2-G709-4-ERROR : /harddisk:/ipodwdm_logdirectory check failure on Failed - Reason node1_RSP1_CPU0 ====> This is the syslog
RP/1/RSP0/CPU0:May 14 12:08:47.483 : ce_switch_srv[53]: %PLATFORM-CE_SWITCH-6-UPDN : Interface 8 (Peer_RSP) is down
Conditions:
This syslog is seen after a cluster fail-over.
Workaround:
Not required. No functionality impact. It's just a misleading syslog.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtn90355 | Title: | Timeslots incorrectly shown for unframed E1 controllers |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Incorrect timeslot entries shown for unframed E1 controller
Conditions:
When controller E1 is configured in unframed mode
Workaround:
N/A
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 4.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy40254 | Title: | gpb telemetry protoc not available from official doc link |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Link to download telemetry protoc not working
Conditions:
to download the app
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.0.0.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf48626 | Title: | GH Alarm Card: Change Serial Reset Codes |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: * | Symptom:
GH Alarm Card: Change Serial Reset Codes
Conditions:
It has been RC that OIR of an adjacent alarm card causes noise on the serial reset lines which
can be interpreted as a reset sequence in some scenarios (rare). An updated reset sequence
is required along with new FPGA decode to cover this.
Workaround:
NA.
Further Problem Description:
It has been RC that OIR of an adjacent alarm card causes noise on the serial reset lines which
can be interpreted as a reset sequence in some scenarios (rare). An updated reset sequence
is required along with new FPGA decode to cover this.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | 4.3.2.28i.BASE, 5.1.1.16i.BASE, 5.1.2.7i.BASE, 5.2.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug27126 | Title: | Crash in malloc() in cfgmgr-rp |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Process crash on ENXR
Conditions:
When calling open system call on enxr
Workaround:
None
More Info:
|
|
Last Modified: | 14-FEB-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy08886 | Title: | rommon upgrade failure w fail to spawnp rommon_burner errno 9 |
|
Status: * | Other |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
upgrade_daemon can fail to
run properly when using
(admin) upgrade rommon b location 0/0/CPU0
with the following error message :
LC/0/0/CPU0: upgrade_daemon[271]: fail to spawnp
rommon_burner errno 9
Conditions:
process syslog_dev has been previously restarted on the affected linecard
Workaround:
process restart upgrade_daemon loc 0/X/CPU0 (where X is the affected linecard).
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 4.3.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy51508 | Title: | Support sync option for TCL corresponding to cli event in IOS EEM applet |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
This is an enhancement request.
In IOS, cli event on EEM applet supports sync option, this makes customer to enable the availability to forbid the particular CLI.
On the other hand, in IOS XR the corresponding TCL doesn't work event after converting from EEM applet in IOS to TCL in IOS XR.
Conditions:
All of currently supported IOS XR versions
Workaround:
TACACS command authorization can forbid the particular command. However, it may be difficult depending on customer requirement.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum90283 | Title: | TL1 pm TCA autonomous message not detected |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
TCA alerts not shown in TL1.
Conditions:
Retrieve conditions on the NE. Threshold crossing alerts are not shown in the output.
Workaround:
None.
Reproducibility: 100%
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE, 5.4.0.CE |
|
Known Fixed Releases: | 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy43971 | Title: | Need improved log message for automatic LC shutdown due to temperature |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
When high temperatures are measured on LCs, currently, the router will report:
shelfmgrv2[391]: %PLATFORM-SHELFMGRV2-6-ADMIN_POWEROFF : Card x/y/z is powered off due to admin power off request
Conditions:
High temps can occur for a number of reasons, but the log message will always be the same generic log message.
Workaround:
none.
Further Problem Description:
This DDTS is to improve the log message, so it's clear to the customer why the LC was shut down, so it will be clear an RMA is not needed.
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz22224 | Title: | TE-MIB slow when polling to nonexistent LSPs |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
This is for a performance enhancement When polling TE-MIB to nonexistent LSP.
Conditions:
When polling TE-MIB to nonexistent LSP.
Workaround:
Do a discovery for each iteration so you don't poll to nonexistent LSP.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 4.2.0.MPLS |
|
Known Fixed Releases: * | 5.2.5.46i.MPLS, 5.3.2.8i.MPLS, 6.0.0.5i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux79152 | Title: * | add withdraw/update reason statistic and associated recent prefix events |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
it is enhancement reqeust to add CLI to show withdraw/update reason statistic in each update-group, in this CLI, it also show recent hundreds update events for each update/withdraw reason, this event information include prefix, time stamp.
Conditions:
N/A, it is not bug, it is enhancement request
Workaround:
N/A, it is not bug, it is enhancement request
Further Problem Description:
N/A, it is not bug, it is enhancement request
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy09895 | Title: | Add LSP name to output of "show mpls traffic-eng preemption log" output |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Currently LSP name it's not displayed in "show mpls traffic-eng preemption log" output on XR
Conditions:
MPLS TE is used on XR
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts56924 | Title: | Include SCP and SFTP as an available option in the COPY command |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom: Although SCP and SFTP file transfers are available with IOS-XR , the protocols are not valid options as part of the "COPY" command. CSCts56924 adds the SCP and SFTP option to the COPY command.
Conditions: N/A
Workaround: N/A
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy11470 | Title: | Roll feature for non-revertive circuits doesnt switch traffic back to W |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
Creation or deletion should change the revertive non revertive behavior of the circuit.
Conditions:
Try to create/delete the roll for non-revertive circuits in B&R feature
Workaround:
NONE
Further Problem Description:
Reproducibility is 100%
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.47.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy28313 | Title: | ISIS doesn't use TE tunnels for IPv6 SR routes |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
ISIS doesn't use autoroute TE tunnels for IPv6 prefixes associated with a prefix SID.
Conditions:
MPLS TE tunnels with "autoroute announce" and "include-ipv6" configured used in combination with ISIS segment routing.
Workaround:
Prefixes not associated with an SR prefix SID will work as expected.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.1.ROUT |
|
Known Fixed Releases: * | 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy18476 | Title: | FNF Netflow support export of IPFIX elemnts-PSAMP protcl elemnt 313-317 |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Can not create PSAMP network monitoring database information due to the lack of IPFIX-and PSAMP-compliant monitoring devices missing Flexible netflow sampling data, specifically IPFIX elements 313,314 and 316, 317
Conditions:
Workaround:
none
Further Problem Description:
Network adaptability, traffic analysis and performance monitoring details for Cisco devices not available without these sample netflow elements and application behavior modifications capabilities are impacted.
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 6.0.1.K9SEC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy01883 | Title: | ISIS: Allow unicast packets on p2p links |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
CSCuw96311 added mac destination address filtering to support ISIS-MI. It turns out that some ISIS implementations - notably that of a test equipment vendor - unicast ISIS packets on point-to-point links. This is not compliant with RFC 5309 section 4 which states:
"Over LAN media, the MAC header must contain the correct multicast MAC address to be received by the other side of the connection. "
and:
"Since physically the circuit is a broadcast one, the IS-IS protocol packets need to have MAC addresses for this p2p-over-lan circuit. From a link-layer point of view, those packets are IS-IS LAN packets. The Multi-destination address including AllISs, AllL1ISs, and AllL2ISs, defined in [ISO10589], can be used for link-layer encapsulation; the use of AllISs is recommended."
Nevertheless, we can allow this on p2p over LAN interfaces for purposes of interoperability without compromising ISIS-MI.
Conditions:
Interop with implementations that don't conform completely with rfc 5309.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: * | 6.0.1.17i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw87394 | Title: | shall be able to shutdown and reload single power module (ie: 0/PT1-PM2) |
|
Status: | Terminated |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
Single Power Module is not being able to shutdown using, hw-module shutdown.
hw-module location 0/PT1 shutdown is also failing.
Conditions:
Shutdown of power module using hw-module location 0/PT1-PM2 shutdown is not possible.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 5.2.41.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy30876 | Title: | "snmp-server traps sensor" not generating RX TX Low power warning traps |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
We want to send an snmp trap when we have a RX or TX Low power warning on an interface.
We have the "snmp-server traps sensor" command configured however the trap is not generated.
We cannot use "snmp-server traps syslog" to send all the syslog traps and instead just want to use that particular sensor trap.
When the threshold is reached, we get a notification in the syslog however a trap is not generated.
RP/0/RP0/CPU0:VL-LB-RF003#LC/0/7/CPU0:Jun 26 16:44:24.636 : plim_xge[286]: %L2-PLIM-4-XFP_WARN_RX_PWR : Interface TenGigE0/7/0/0, RX Low power warning occurred
RP/0/RP0/CPU0:VL-LB-RF003#LC/0/7/CPU0:Jun 26 16:46:04.880 : plim_xge[286]: %L2-PLIM-4-XFP_WARN_RX_PWR : Interface TenGigE0/7/0/0, RX Low power warning recovered
As per the support forum this is supported on ASR9000:
https://supportforums.cisco.com/discussion/11607896/asr-9010-snmp-detail
This bug is filed so that this feature can be added into CRS as well.
Conditions:
NA
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 17-FEB-2016 |
|
Known Affected Releases: | 5.1.3.CE |
|
Known Fixed Releases: | |
|
|
| |
:
没有评论:
发表评论