| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw44711 | Title: | ASR 9001 5.2.4 Kernel Crash |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
ASR 9001 5.2.4 Kernel Crash
Conditions:
Normal Working Condition
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 5.2.5.30i.BASE, 5.3.2.SP2, 5.3.3.22i.BASE, 6.0.0.21i.BASE, 6.0.1.12i.BASE, 6.1.0.4i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud98552 | Title: | vic_0 crash recurring on 20x1 EP with DWDM SFP |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom: Customer running XR 4.3.0 image with 20X1GE MPA card with DWDM-SFP optics will get continuous vic process crash.
Conditions:Running 4.3.0 image with DWDM-SFP on 20X1GE MPA card.
Workaround: No workaround.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.2.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw19968 | Title: | OSPF lost some summary prefixes |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:When adding one more new summary-prefix config in OSPF, some of existing OSPF
summary prefixes despair. this can happen even without adding/removing the config. bottom line here is whenever an event which cause the summary external route generation we can end up flushing, not generating the external summary routes. this happen only in case of external summary routes and not for individual routes.
Conditions:Adding new summary-prefix config in OSPF. result in the issue. and it can happen also when we learn a route or loose a route which falls in the summary range and force an event to generate/flush the summary external lsa.
Workaround:No proper workaround as such. process restart might help but not guaranteed.
More Info:
introduced via below DDTS.
http://wwwin-tools.cisco.com/prrq/viewReview.do?action=show_diff&bugId=CSCur13855&queueName=HFR-OSPFv2
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.ROUT |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.12i.BASE, 6.0.0.15i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo32371 | Title: | L3VPN pseudowire headend (PWHE) cannot pass the RSVP-TE |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
Packets will drop from pw-ether port to customer though L2 PW.
Conditions:
RSVP over LDP over PW, and one hop tunnel.
Due to one hop tunnel, TE outlabel is implicit, so need IGP label.
Workaround:
no workaround now
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.24i.BASE, 5.1.3, 5.1.3.5i.BASE, 5.1.4, 5.2.0, 5.2.0.24i.BASE, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur96302 | Title: | MOD80 cannot boot with SMU CSCul57104 |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
MOD 80 LC doesn't comes up
Conditions:
Issue happens with the SMU for CSCul57104
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.2.FWDG, 4.3.2.LC |
|
Known Fixed Releases: * | 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2, 4.3.2.SP7, 4.3.2.SP8 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux04919 | Title: | BGP crash at bgp_table_post_bestpath() while flap/bringing up neighbor |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
BGP crash after neighbor flap and receiving multiple paths for the same prefix at the same time.
Conditions:
- add-path or best-external or both,
- bring up or down a neighbor or modifying neighbor configurations,
- routes to be received by the router for the same prefix from multiple neighbors at the same time, CE and PE.
- next-hop changes, such as metric or reachability will also contribute.
- The problem occurs with VPN routes, although other route types cannot be ruled out.
Workaround:
none
Further Problem Description:
Anything that causes a path other than the best path too be sent to a neighbor is a prerequisite for the bug.
additional-path and best-external cause that.
The bug exists in all versions that have the additional-path feature.
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 4.1.2.ROUT, 5.3.1.ROUT, 5.3.2.ROUT |
|
Known Fixed Releases: | 5.2.5.41i.ROUT, 6.0.1.14i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy26887 | Title: | [601]Multiple process block on prm_server on comit replace with VRf conf |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom:
Router gets stuck on commit replace,and multiple process blocks observed.
Conditions:
when VRF configs are applied and a router reload is done then a commit replace was given the router gets stuck .and commit replace does not take place.
Workaround:
Unpower all line cards and remove the vrf configs
Further Problem Description:
NA
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc11977 | Title: | SRT_SRT_MISC_ERR_LEAF_INT_INT_TIER interrupts seen on 4.2.3.28I |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
SRT_SRT_MISC_ERR_LEAF_INT_INT_TIER2 interrupts
cpp_driver1[152]: Interrupt occurred: Node Name-SRT_SRT_MISC_ERR_LEAF_INT_INT_TIER1_REAL_DISTANCE_ERR, Node ID-0x8bb7
cpp_driver1[152]: Interrupt occurred: Node Name-SRT_SRT_MISC_ERR_LEAF_INT_INT_TIER2_REAL_DISTANCE_ERR, Node ID-0x8bb6
Conditions:
start/stop of Multicast traffic in a GRE mVPN setup.
Workaround:
None
Further Problem Description:
Issue was seen also in a not mVPN setup. Card replacement doesn't fix the issue.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.0.29i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz29758 | Title: | SFP-GE-T shows as non UDI complaint |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Two Symptom:
1. %PLATFORM-VIC-4-XCVR_WARNING and %PLATFORM-SFP-2-DEV_SFP_PID_NOT_SUPPORTED error messages for SFP-GE-T (SFP-GE-T Ext) type of the optic.
Pluggable PID Supp. : Not supported from the output of show contr g<> int
2. speed 100M/10M does not work when reboot the EP /LC with the optic inserted.
Conditions:
1. error msg only show during EP/LC/Router boot up or insert the optic.
2. Speed 100M/10M does not work only when the EP/LC/Router reload with the optic inserted.
Workaround:
1. Under interface g<>, issue CLI " transceiver permit pid all". All unsupported msg/mark can be ignored. This optic will be supported
2. After Ep/LC/Router bootup, OIR the optic.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.0.LC, 4.2.1.LC |
|
Known Fixed Releases: * | 4.2.2, 4.2.2.8i.BASE, 4.2.3, 4.2.3.16i.BASE, 4.2.4, 4.3.0, 4.3.0.13i.BASE, 4.3.1, 4.3.2, 4.3.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud84488 | Title: | 100G Link shows RFI after LC reload and re-inserting fiber |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
100 GE interface stays down after linecard reload or optics oir.
Conditions:
Problem happen after line card crash or reload, during line card initialization stage. In some rare timing condition, CFP is not initialized correctly.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.19i.BASE, 4.3.2, 4.3.2.3i.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: | CSCui72609 | Title: | ASR9k L2 unicast traffic loss between racks with 100GE module & NV Edge |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Unicast L2 bridged traffic dropped when 100G interface is used in cluster router.
Conditions:
L2 E-LAN/VPLS service is configured in the cluster router. L2 traffic goes through 100G LC card. If the l2 unicast traffic goes from a 100G card to a physical AC in the remote rack,
the traffic can be dropped.
The issue is also seen when 100GE interface is configured as routed L3/mpls interface forwarding to a BVI and L2 bridge domain.
Workaround:
1. Avoid using 100G for L2 traffic forwarding include BVI traffic. Or
2. Change all physical AC to bundle AC when using them in E-LAN (bridging) service.
Further Problem Description:
The root of the problem is 100G LC is not able to correctly sync up the MAC table when MAC is learned from physical AC on remote rack .
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE, 4.3.2.BASE, 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.0.23i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue21659 | Title: | OIR of CFP optic in 2x100GE LC results in permanent down port on 9922 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The 100G interfaces on A9K-2x100GE-TR/SE or A9K-1x100GE-TR/SE might be in down state after CFP OIR.
Conditions: The interface will not come up after CFP OIR. The interface faults would have the following two faults XCVR_TYPE_UNSUP XCVR_PID_UNSUP.
Workaround:Execute Shut & No shut on the interfaces.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.21i.BASE, 4.3.2, 4.3.2.5i.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: | CSCun26272 | Title: | TXFP - Adaptive FEC control algorithm not working in 4x10GE MPA |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In OTN mode with FEC enabled, amplitude_threshold parameter in 'sh controller tengig <> phy' is not changing when FEC errors are increasing. This issue is seen only in 4x10GE and 2x10GE MPA when used with Tunable XFP.
Conditions:
Tunable XFP with OTN mode
Workaround:
None
Further Problem Description:
This doesn't affect traffic in OTN mode
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.22i.BASE, 5.1.3, 5.1.4, 5.2.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc48596 | Title: | prm_server_ty failed to respawn, LC resets |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In rare cases, the prm_server_ty process may fail to successfully restart following a process crash or manual restart. The follow error is displayed in the sys logs:
RP/0/RSP0/CPU0:BNG1#LC/0/0/CPU0:Oct 2 18:23:44.927 : prm_server_ty[308]: %PLATFORM-NP-0-INIT_ERR : Network Processor Initialization Phase 2 Failed!!
The following errors are reported in the NP driver log which can be displayed using the "show controller np drvlog" command:
ERROR! 0x80001353 NPsrhCompFastIP_CheckSingleLineConsistency: warm-boot inconsistent result in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/srh/NPsrhFastIP.c' line 12138
ERROR! 0x80001353 NPsrhCompFastIP_CheckConsistency: NPsrhCompFastIP_CheckSingleLineConsistency failed in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/srh/NPsrhFastIP.c' line 12284
ERROR! 0x80001353 NPsrhCompFastIP_RestoreAddrHandler: NPsrhCompFastIP_CheckConsistency failed in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/srh/NPsrhFastIP.c' line 19115
ERROR! 0x80001353 NPsrhCompFastIP_RestoreAddresses: NPsrhCompFastIP_Traverse failed in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/srh/NPsrhFastIP.c' line 19191
ERROR! 0x80001353 NPsrhCompFastIP_FixAtFinishWarmboot: NPsrhCompFastIP_RestoreAddresses failed in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/srh/NPsrhFastIP.c' line 19387
ERROR! 0x80001353 NPcorDriver_FinishWarmBoot: NPsrhCompFastIP_FinishWarmboot failed in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/srh/NPsrhStruct.c' line 4831
ERROR! 0x8000110D NPcorDriver_FinishWarmBoot: NPsrhStruct_FinishWarmBoot failed. in file 'drivers/chips/np/npchip-4c/src/host/driver/src/cor/drv/NPcorDriver.c' line 624
The process will fail to restart 5 times after which the linecard will automatically be reloaded. The prm_server_ty process will come up successfully after the linecard reboots.
Conditions:
This is a secondary problem. It can only occur when the process needs to be restarted which does not occur under normal operating conditions.
Workaround:
The workaround is to avoid the initial error which causes the process to be restarted in the first place.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE, 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.20i.BASE, 4.3.2, 4.3.2.5i.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: | CSCuh10155 | Title: | continuous "cpp_qos_ss_proc_stats:121:STATS error Not enough memory" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:These continuous syslogs are being generated from the SIP700 LC
cpp_qos_ss_proc_stats:121:STATS error Not enough memory.
This issue is only applicable to SIP based LC(THOR LC).
Trident and Typhoon card are not based on CPP arch and is not affected by this issue.
Conditions:The cpp_cp_svr process is common for multiple features and on applying multiple features on the box process memory gets shared between all the features.
In the normal scenario, Qos needs to poll the h/w stats for all the policy-map applied on the interfaces. Each policy-map stats polling requires 9MB buffer allocation and it will get free post stats scrapping. Due to the contiguous 9MB memory unavailability, it leads to the qos stats allocation malloc failure.
Workaround:none
More Info:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.0.11.LC, 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.22i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.11i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud39827 | Title: | arp request is not sent if local adj in vrf is seen via different path |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When connected route is learned on other port, arp request is not sent.
Conditions:
connected interface and learned route are in non default vrf
Workaround:
LC reload
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE, 4.3.0.BASE, 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.37i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf34737 | Title: | Enhancement to improve convergence for Typhoon LCs on kernel crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic loss ocurrs on bundle members of a crashed linecard because the bundle member is not removed from the bundle until after the kernel core finishes writing. In observed event this has been in the region of 30-40 seconds.
Conditions:
Kernel crash caused by MBE (memory error) or other on Typhoon generation linecard.
Workaround:
This enhancement intends to make the same changes for Trident generation linecards in CSCts63586 for Typhoon generation linecards, which result in the bundle member being removed on kernel crash rather than after the core finishes writing
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.1.26i.BASE, 4.3.2.11i.BASE, 5.1.0.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut63675 | Title: | lda_server coredump caused by wdsysmon |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Process lda_server may be terminated by wdsysmon due to cirtical limit of more than 950 file handles used.
System messages will indicate warnings/errors with wording like the following:
wdsysmon[384]: %HA-HA_WD-4-FD_MAJ_LIM : Process lda_server, pid 53281 is using 900 file descriptors out of a max of 1000. Major limit (90%) crossed.
wdsysmon[384]: %HA-HA_WD-3-FD_CRIT_LIM : Process lda_server, pid 53281 is using 950 file descriptors out of a max of 1000. Critical limit (95%) crossed.
The show processes file command will show a high number of connection to sysdb_svr_local:
show process details location
is job id for lda_server on the failing node.
is the Rack/Slot/Instance location of the failing node.
Conditions:
This defect may occurs under very rare condition, such as:
a) 900+ changes of hw-mdoule breakout configuration.
b) Defects that will cause interface HW to fail persistently, which in turn will cause the system to retry HW initialization a large number of times.
Workaround:
The system recovers from the fail state on its own, without service impact following the forced lda_server termination and restart.
In the case of condition b) above, the issue causing the interface HW initialization failure need to be resolved as a separate issue.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.28i.BASE, 5.3.2, 5.3.2.6i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui95200 | Title: | port level MAC counter is not correct on Trident LC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
MAC learning on AC ports were disabled wrongly by mac limit configuration.
Conditions:
configure mac limit on port level
Workaround:
Reload the LC
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.2.BASE |
|
Known Fixed Releases: * | 4.3.4.4i.BASE, 5.1.1.8i.BASE, 5.1.11.4i.BASE, 5.1.2.1i.BASE, 5.2.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud51667 | Title: | qos_ma_ea crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
qos_ma_ea process on line card crashes.
Conditions:
Modifying a QoS policy with incorrect/unsupported values when the QoS policy is already applied on a bundle interface/sub-interface and bundle member interfaces are flapping.
Workaround:
Don't modify a QoS policy with incorrect/unsupported values when the QoS policy is already applied on bundle interface/sub-interface
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.17i.BASE, 4.3.2, 4.3.2.3i.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: | CSCui77683 | Title: | 511-4i PW-IW intermittent ping loss on APE (RSV_DROP_EGR_UIDB_NO_MATCH) |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IP-IW packets that are destined to egress from the router on an AC that does not have QoS or ACL configured may be dropped due to Egress UIDB Lookup miss.
Conditions:
Must be configured to pass IP-IW traffic.
Workaround:
Ensure that QoS is configured for the egress interface.
Further Problem Description:
N/A
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE, 4.3.2.BASE, 5.1.0.BASE, 5.1.1.BASE |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.4i.BASE, 5.1.1, 5.1.1.8i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12, 5.1.2, 5.1.2.1i.BASE, 5.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30678 | Title: | CEF Inconsistency between RSP and LCs due to NHipv6 compression leaking |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic forwarding across ASR9K fails. ASR9K drops traffic on ingress LC as FIB entries on LC and RSP dont match. LC showing null adjacency.
Conditions:
High number of VPNv6/IPv6 prefix learning
Workaround:
Reload LC or Reload router
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 4.3.4.MPLS, 4.3.4.ROUT |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.22i.BASE, 6.0.0.27i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux70706 | Title: | [601]-ASR9000v ICL Intf flaps after icpe_satmgr process restart on RP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ICL Intf flaps after icpe_satmgr process restart on ASR9000v
Conditions:
Could see ICL Interface flapping after icpe_satmgr process restart on RP with Bundle ICL in ASR9000v Satellite. Due to this, we are seeing traffic loss.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw59619 | Title: | syslog was not displayed when Cluster EOBC/IRL UDLD detected err-disable |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In Nv Edge on ASR9k when IRL/EOBC intermediate links are failed (Ports were actually Up/Up) , the UDLD detection goes to Unknown but this issue is not reported as a syslog.
Conditions:
Failure in the intermediate network connecting the EOBC or IRL links in an NV Edge system.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.19i.BASE, 6.0.0.25i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux58074 | Title: | VSM card mac move taking 2,5min with "hw-module mac-move police-mode on" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
VSM cards takes 2,5min to learn MAC on new port after its move.
Conditions:
"hw-module mac-move police-mode on" enabled.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.25i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux77280 | Title: | Backup SyncE sources not available for selection |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Backup SyncE sources on colossus LC are not available for selection.
'show frequency synchronisation selection' output does not show the SyncE sources on Colossus LC or the SyncE sources are shown as 'Unqualified'.
Consequently, interfaces on Colossus LC cannot be used as SyncE source inputs.
Conditions:
Following conditions should be met to hit this issue:
1. SyncE sources (input clocks) are on Colossus (24x10G) LC
2. After repeated changes (QL change, i/f flaps) on Colossus LC interface which is a SyncE selection input.
Workaround:
process restart sync_agent location
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.26i.BASE, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw30290 | Title: | Delay the backup path installation for bundle Convergence issue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | We have mixed family of line cards. The Tomahawk LCs are faster than the
Typhoon LCs. This is causing the programming (convergence) on the Typhoon LC
to take longer compared to the Tomahawk LC
??? So in the interim we have state where Ingress Tomahawk LC is programmed to
switch from Bundle 1 to Bundle 2. The packet goes to the Typhoon LC which is part
of Bundle 2 but since this card is not yet programmed it black holes the traffic.
??? NHID feature is present on the platform to address such cases where we have
speed mismatched cards. If we have LFA enabled NHID is not supported currently.
??? LSNT team has verified with LFA configuration (NHID enabled) removed we are not
seeing such high traffic loss.
??? Code changes for LFA to utilize NHID would need additional packet buffer header
memory.
??? Typhoon does not have the additional space to support this.
??? Tomahawk would need microcode work in forwarding.
Symptom:
Packet loss of 10-15 sec on some streams during traffic move from Tomahawk
Only Mixed Bundle (B1) to Typhoon/Tomahawk Mixed Bundle (B2), without LFA
FRR being triggered.
Conditions:
Convergence event without LFA trigger
??? Bundle 1 is not going down due to triggers (listed below).
??? Ingress LC is Tomahawk LC/Typhoon (Mod-80) and egress is Typhoon LC
(24x10GE LC)
Following are the triggers:
??? OSPF link manual costing out of Bundle 1.
??? Shutting of some member links of the bundle 1 which trigger OSPF cost
threshold (BW <40GE).
??? LDP failure on Bundle 2. (Seen when traffic re-convergence to Bundle-2)
Workaround:
none
Further Problem Description:
We have mixed family of line cards. The Tomahawk LCs are faster than the
Typhoon LCs. This is causing the programming (convergence) on the Typhoon LC
to take longer compared to the Tomahawk LC
??? So in the interim we have state where Ingress Tomahawk LC is programmed to
switch from Bundle 1 to Bundle 2. The packet goes to the Typhoon LC which is part
of Bundle 2 but since this card is not yet programmed it black holes the traffic.
??? NHID feature is present on the platform to address such cases where we have
speed mismatched cards. If we have LFA enabled NHID is not supported currently.
??? LSNT team has verified with LFA configuration (NHID enabled) removed we are not
seeing such high traffic loss.
??? Code changes for LFA to utilize NHID would need additional packet buffer header
memory.
??? Typhoon does not have the additional space to support this.
??? Tomahawk would need microcode work in forwarding.
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.18i.ROUT, 6.0.0.23i.ROUT, 6.0.1.12i.ROUT, 6.1.0.6i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur44662 | Title: | Modify the approach of calling nsr_initiate_fo from the signal handler |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BGP signal handler calling nsr_initiate_fo
Conditions:
Avoid having to call nsr_initiate_fo from a signal handler
Workaround:
None
Further Problem Description:
This SMU is very critical for ATT , as mentioned in DDTS , this issue is NSR library which will be trigger if any of NSR enabled process crash. As ATT is using nsr-process switchover CLI. Following are the impact because of this issue:
1. Huge Traffic Impact
2. Qnet CRASH
3. BGP/TCP stuck in MUTEX Permanently
4. BGP all the sessions down permanently
5. Most of time its recovered only by reloading the router.
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.2.5.33i.BASE, 5.3.2.SP2, 5.3.3.18i.BASE, 6.0.0.20i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux95562 | Title: | after router reload,core MDT neighbor entries missing once router is up |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
multicast traffic drops after router reload
Conditions:
After router reload Core MDT neighbor entries missing in PE5 ,Due to this multicast traffic drops
After router reload, mcast_enabled bit was not set in hardware for the bundle core interface and that caused the traffic loss.
This can occur only if an interface is explicitly enabled under multicast-routing.
During router reload, if MFIB receives multiple UP and DOWN notifications from Interface Manager (with the last state being UP), then we can hit this issue. This will not happen usually, and is a uncommon race condition.
Workaround:
None
Further Problem Description:
The issue can be recovered by one of the following methods:
remove and add multicast config
configuring interface all enable
unconfigure/re-configuring affected interface
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.3.3.ADMIN |
|
Known Fixed Releases: * | 6.0.1.19i.BASE, 6.0.1.19i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01483 | Title: | [533]-Satellite Intf struck Error Disabled after SAT Reload with UDLD |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
After a satellite reload, the satellite interface on the active asr9k in a dual head active/standby pair may be error-disabled with the error-disable reason 'udld-neighbor-mismatch'
Conditions:
This issue affects all IOS-XR releases with ASR9K Dual Head satellite topologies running UDLD. The issue may occur on satellite reload.
Workaround:
There is no way to guarantee avoiding this issue other than unconfiguring the standby prior to the reload.
There are 4 methods of recovery once the issue is hit:
1. Automated recovery.
Prior to the satellite reload, the user can configure error-disable recovery cause udld-neighbor-mismatch interval 30 this will auto recover the interface after 30 seconds.
2. Manual recovery method 1:
Use the clear error-disable interface command to recover the interface
3. Manual recovery method 2:
Use the ethernet udld reset interface command to recover the interface
4. Manual recovery method 3:
Use the shutdown configuration command to shut down the affected interface after the reload, then delete the configuration using no shutdown to bring the interface back up.
Further Problem Description:
The problem is a race condition caused by the old standby ASR9K in the dual head pair connecting to the satellite before the active ASR9K, this may result in one UDLD packet being sent to the satellite with the 'wrong' (standby) MAC address. The satellite then echoes back two MACs in its response to the real active ASR9K which declares the neighbor mismatch.
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.3.3.CE, 6.0.0.CE |
|
Known Fixed Releases: | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80640 | Title: * | SSTE: ISIS process crash when "show isis ipv6 route" command is entered |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Depending on the network topology, the ISIS process may crash and restart when the command:
show isis ipv6 route
is entered, or when an equivalent XML request is made.
Conditions:
IPv6 routes in the ISIS rib have lower-priority backups.
Workaround:
Do not use the "show isis ipv6 route" command.
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 6.0.1.ROUT |
|
Known Fixed Releases: | 5.3.3.27i.ROUT, 6.0.1.14i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu95107 | Title: | MH DCI:fib_mgr crash @ nh_compr on Tomahawk LC - 5.3.2 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
fib_mgr process crash is seen when BGP is flapping/converging at ipv6 compression library.
Conditions:
BGP is flapping/converging, on typhoon & thk LCs
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.15i.BASE, 5.3.3.3i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu96153 | Title: | FD leaks on bfd_agent process when executing 'show bfd summary' CLI |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On executing "show bfd summary" the open file descriptor counter increments.
bfd_agent process is crashed by WD after the FD exceeds the critical threshold value.
RP/0/RSP0/CPU0:s4bs-e-401#show processes files 125 location all
Thu Jun 18 22:58:32.517 EST
node: node0_0_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 121 51 bfd_agent
node: node0_1_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 121 51 bfd_agent
node: node0_4_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 124 51 bfd_agent
node: node0_5_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 124 51 bfd_agent
node: node0_RSP0_CPU0
------------------------------------------------------------------
Invalid Job id or Job not running
node: node0_RSP1_CPU0
------------------------------------------------------------------
Invalid Job id or Job not running
RP/0/RSP0/CPU0:s4bs-e-401#show bfd summary
Thu Jun 18 23:13:01.733 EST
Node All PPS usage MP PPS usage Session number
% Used Max % Used Max Total MP Max
---------- --------------- --------------- ------------------
0/0/CPU0 0 0 28000 0 0 9600 0 0 8000
0/1/CPU0 0 0 28000 0 0 9600 0 0 8000
0/4/CPU0 0 233 28000 0 0 9600 2 0 8000
0/5/CPU0 0 233 28000 0 0 9600 2 0 8000
RP/0/RSP0/CPU0:s4bs-e-401#show processes files 125 location all
Thu Jun 18 23:13:08.292 EST
node: node0_0_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 122 51 bfd_agent
node: node0_1_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 122 51 bfd_agent
node: node0_4_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 125 51 bfd_agent
node: node0_5_CPU0
------------------------------------------------------------------
JID Open-Files Open-Channels NAME
125 125 51 bfd_agent
node: node0_RSP0_CPU0
------------------------------------------------------------------
Invalid Job id or Job not running
node: node0_RSP1_CPU0
------------------------------------------------------------------
Invalid Job id or Job not running
RP/0/RSP0/CPU0:s4bs-e-401#
Conditions:
Execution of "show bfd summary" CLI
Workaround:
No Workaround
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.16i.BASE, 5.3.3.3i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut84328 | Title: | Packet loss when remote LFA is triggered in ASR9K running 5.3.0. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | ASR9K has programmed the backup path (remote LFA) to destination (10.194.62.16), I see 673 packet drops when measuring convergence using a traffic generator. The traffic generator is sending 10,000 packets per second. This results in a convergence time of 67.3 msec
Test Setup:
Traffic is sent from ASR920-3 (10.194.62.18) to ASR920-1 (10.194.62.16)
Primary Traffic path is ASR920-3 ASR9K-2 ASR9K-1 ASR920-1
Backup Traffic Path is ASR920-3 ASR920-2 ASR9k-1 ASR920-1
Remote LFA is from ASR9K-2 to ASr920-2 (via) ASR920-3.
RP/0/RSP0/CPU0:ASR9K2#sh ip cef 10.194.62.16
Fri Apr 3 18:19:15.178 CET
10.194.62.16/32, version 52643, internal 0x1000001 0x0 (ptr 0x71f4003c) [1], 0x0 (0x71eda210), 0xa28 (0x72ae8208)
Updated Apr 3 18:19:11.504
remote adjacency to TenGigE0/2/0/3
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 10.194.62.55, TenGigE0/2/0/0, 6 dependencies, weight 0, class 0, backup [flags 0x300]
path-idx 0 NHID 0x0 [0x718054f0 0x0]
next hop 10.194.62.55, PQ-node 10.194.62.17
remote adjacency
local label 24007 labels imposed {508 23} < backup path labels are visible via CEF
via 10.194.62.32, TenGigE0/2/0/3, 6 dependencies, weight 0, class 0, protected [flags 0x400]
path-idx 1 bkup-idx 0 NHID 0x0 [0x72a1a554 0x0]
next hop 10.194.62.32
local label 24007 labels imposed {24000}
Routing entry for 10.194.62.16/32
Known via "isis core", distance 115, metric 20
Tag 1, type level-2
Installed Apr 3 18:19:11.495 for 00:02:15
Routing Descriptor Blocks
10.194.62.55, from 10.194.62.16, via TenGigE0/2/0/0, Backup (remote) < Backup path via Remote LFA to 10.194.62.17
Remote LFA is 10.194.62.17
Route metric is 0
10.194.62.32, from 10.194.62.16, via TenGigE0/2/0/3, Protected
Route metric is 20
No advertising protos.
Looking at the drops on the controllers:
RP/0/RSP0/CPU0:ASR9K2#show controller np counters all | inc DROP
Fri Apr 3 18:23:01.448 CET
320 RSV_DROP_EGR_HWOFF_NO_MATCH 138959009 179659
412 RSV_DROP_IN_L3_NOT_MYMAC 2 0
518 UTURNCHECK_FRR_DROP 572 0
1214 MDF_PUNT_POLICE_DROP 56534 101
The drop counters related to UTURNCHECK_FRR_DROP (572) can be correlated to the packet drops (673) seen by the traffic generator.
The uturn bit is set for the prefix 10.194.62.16
RP/0/RSP0/CPU0:ASR9K2#sh cef 10.194.62.16 hardware ingress detail location 0/2/CPU0 | inc uturn
Fri Apr 10 04:35:45.914 CET
isMPinNR_LDI: 0 uturn_check: 1
Symptom:
Packet loss when remote LFA is triggered in ASR9K running 5.3.0
Conditions:
Remote LFA is triggered
Workaround:
None
Further Problem Description:
ASR9K has programmed the backup path (remote LFA) to destination (10.194.62.16), I see 673 packet drops when measuring convergence using a traffic generator. The traffic generator is sending 10,000 packets per second. This results in a convergence time of 67.3 msec
Test Setup:
Traffic is sent from ASR920-3 (10.194.62.18) to ASR920-1 (10.194.62.16)
Primary Traffic path is ASR920-3 ASR9K-2 ASR9K-1 ASR920-1
Backup Traffic Path is ASR920-3 ASR920-2 ASR9k-1 ASR920-1
Remote LFA is from ASR9K-2 to ASr920-2 (via) ASR920-3.
RP/0/RSP0/CPU0:ASR9K2#sh ip cef 10.194.62.16
Fri Apr 3 18:19:15.178 CET
10.194.62.16/32, version 52643, internal 0x1000001 0x0 (ptr 0x71f4003c) [1], 0x0 (0x71eda210&#
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.8i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw44751 | Title: | [ATT 532] IPv6 LI intercept sending more than requested IP range |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
LI Functionality is Broken for /126 Prefix
Issue is Lawful Intercept Functionality, its taping more prefixes which it supposed to tap. It is like a security breach.
With the /126 we should would expect to capture only packets with the
following addresses:
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
But it is tap all the addresses
caf????:1890:8a9d:9800:0:0:11b7:4
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
:
:
:
caf????:1890:8a9d:9800:0:0:11b7:f
Conditions:
every time
Workaround:
no workaround
Further Problem Description:
Issue is Lawful Intercept Functionality, its taping more prefixes which it supposed to tap. It is like a security breach.
With the /126 we should would expect to capture only packets with the
following addresses:
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
But it is tap all the addresses
caf????:1890:8a9d:9800:0:0:11b7:4
caf????:1890:8a9d:9800:0:0:11b7:5
caf????:1890:8a9d:9800:0:0:11b7:6
caf????:1890:8a9d:9800:0:0:11b7:7
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
caf????:1890:8a9d:9800:0:0:11b7:c
caf????:1890:8a9d:9800:0:0:11b7:d
caf????:1890:8a9d:9800:0:0:11b7:e
:
:
caf????:1890:8a9d:9800:0:0:11b7:f
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.SP2, 5.3.3.13i.BASE, 6.0.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv15306 | Title: | P2MP S2L branch BE OIF stop forwarding after MPA reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When MPA (hosting more than 2 P2MP OIF BE interfaces) is reloaded
(or OIRed), some S2L OIFs stop to forward P2MP traffic.
This issue is common to vpls-lsm , static p2mp-te based mvpn, and
native IPv4 multicast over p2mp-te.
Conditions:
- Equal or More than 3 Bundle-Ether OIFs in FRR Ready State
- Each BE interface is hosted on 2 MOD LCs
- MPA is reloaded (physical OIR, module reload, or config shut / no shut)
- Version 5.3.1, 5.2.4, 5.2.2
Workaround:
Removing and adding "backup-path tunnel-te" (or "auto-tunnel backup") under
the affected BE interface (in mpls traffic-eng).
Further Problem Description:
During the P2MP traffic outage on the affected OIF BE(s), there is no NP drop counter increase.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 4.1.0.MCAST, 5.3.1.FWDG |
|
Known Fixed Releases: * | 5.2.5.35i.MCAST, 5.3.1.SP2, 5.3.3.12i.MCAST, 6.0.0.11i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw49153 | Title: | Tomahawk MH Improve error correction in receive dir for x120 phy stuck |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Bringing up new links or after a fiber cut. The links get into a unidirectional traffic forwarding condition.ASR9K is able to transmit traffic. But receive packets will be dropped.
Conditions:
This is an interoperability issue between ASR 9000 (A9K-8X100-SE/TR or A9K-4X100-SE/TR) and M6 / NCS2K-100G-CK linecard.
This issue is not applicable to PIDs A9K-8X100-L-SE/TR, A9K-2X100G-SE/TR and A9K-1X100-SE/TR.
The issue happens only when link flaps or comes up in DWDM core network or trunk port.
A9K-8X100GE-TR (or A9K-8X100GE-TR) <-> CPAK-100G-SR10 (on ASR card) <-> CPAK-100G-SR10 (on optical card) <->
NCS2K-200G-CK-LIC (DWDM w/ 20% SD FEC) <-> 600 to 1000 km optical fiber with MSTP amps, ROADMs, etc. <->
NCS2K-200G-CK-LIC (DWDM w/ 20% SD FEC) <-> CPAK-100G-SR10 (on optical card) <->
CPAK-100G-SR10 (on ASR card) <-> A9K-8X100GE-TR (or A9K-8X100GE-TR)
Workaround:
There is no workaround to prevent this issue. One and only known recovery mechanism is to reload the LC
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.14i.BASE, 6.0.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw01739 | Title: | Pwrmode_change can't change from V1 to V3 PSM on RSP 880 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
while trying to change the power supply type from V1 -- > V3 in pwrmode_change script, the process[pwrmode_change] got crashed and the change did not take effect.
Root-Cause: implementation of idprom_write is missing for RSP880
admin RP/0/RSP0/CPU0:Aug 26 19:40:58.473 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : Global config: Single feed mode disabled
RP/0/RSP0/CPU0:Aug 26 19:40:58.473 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : 0/PM0/0/SP config: Single feed mode disabled
RP/0/RSP0/CPU0:Aug 26 19:40:58.473 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : 0/PM0/1/SP config: Single feed mode disabled
RP/0/RSP0/CPU0:Aug 26 19:40:58.473 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : 0/PM0/2/SP config: Single feed mode disabled
RP/0/RSP0/CPU0:Aug 26 19:40:58.473 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : 0/PM1/0/SP config: Single feed mode disabled
RP/0/RSP0/CPU0:Aug 26 19:40:58.474 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : 0/PM1/1/SP config: Single feed mode disabled
RP/0/RSP0/CPU0:Aug 26 19:40:58.474 : pwrmon[371]: %PLATFORM-PWRMON-1-SINGLE_FEED : 0/PM1/2/SP config: Single feed mode disabled
show platform
Wed Aug 26 19:41:00.520 UTC
?[KNode Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP880-TR(Active) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP880-TR(Standby) MBI-RUNNING PWR,NSHUT,MON
0/FT0/SP ASR-9010-FAN-V2 READY
0/FT1/SP ASR-9010-FAN-V2 READY
0/2/CPU0 A9K-24x10GE-TR UNPOWERED NPWR,NSHUT,MON
0/3/CPU0 A9K-MOD160-TR UNPOWERED NPWR,NSHUT,MON
0/5/CPU0 A9K-24x10GE-TR UNPOWERED NPWR,NSHUT,MON
0/7/CPU0 A9K-MOD160-TR UNPOWERED NPWR,NSHUT,MON
0/PM0/0/SP PWR-6KW-AC-V3 FAILED PWR,NSHUT,MON
0/PM0/1/SP PWR-6KW-AC-V3 FAILED PWR,NSHUT,MON
0/PM0/2/SP PWR-6KW-AC-V3 FAILED PWR,NSHUT,MON
0/PM1/0/SP PWR-6KW-AC-V3 FAILED PWR,NSHUT,MON
0/PM1/1/SP PWR-6KW-AC-V3 FAILED PWR,NSHUT,MON
0/PM1/2/SP PWR-6KW-AC-V3 FAILED PWR,NSHUT,MON
Conditions:
Upgrade power PSM to V3 on RSP880
Workaround:
work around: pwrmode_change script works well with RSP440. So, change the power supply modules from V1 to V3 while 9k is running with RSP440.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.10i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu91413 | Title: | SSTE: Observing fib_mgr crash after mpa oir test on 9k with xr5.3.210i |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Fib Manager process crashes with the following decode
0x82bff13: _Printf
/nobackup/mansonw/iox640_513/nto6.4-XR/qnx/lib/c/stdio/xprintf.c:129
Conditions:
Two conditions found.
1. on MPA oir
2. on configuration change of interface
Workaround:
No Workaround Fib manager restarts on its own
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.15i.FWDG, 6.0.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv61090 | Title: | ABF Fails to track Multiple next hope when using Object Group |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:ABF Fails to track Multiple next hops when using Object Group. If the track corresponding to nexthop1 goes down then nexthop2 is not getting programmed.
Conditions:Track used in the acl with the object group. Next-hop tracking works fine without object Group.
Workaround:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.FWDG, 5.3.1.ROUT |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.16i.FWDG, 6.0.0.21i.FWDG, 6.0.1.12i.FWDG, 6.1.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv02783 | Title: | BGP route-policy drops all prefixes after RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BGP route-policy drops all the prefixes
Conditions:
This problem occurs after an RP/RSP switchover
Workaround:
re-commit the route-policy for the affected neighbors
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 4.3.2.ROUT |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.19i.BASE, 5.3.2.19i.FWDG, 5.3.2.19i.ROUT, 5.3.3.3i.ROUT, 5.3.3.5i.BASE, 5.3.3.5i.FWDG, 5.3.3.5i.ROUT, 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut98928 | Title: | Tomawhawk: traffic drop seen at 100% line rate for certain packet sizes |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Early fast discard packet drops experienced in the ICU (portion that ?pre-parses? incoming packets and schedules them for service through the pipeline) during high packet per second load near maximum forwarding performance.
Conditions:
In typhoon Early Fast Discard was implemented as part of the pipeline processing, hence running as part of the microcode. One of the enhancements of the Tomahawk forwarding architecture is a ?pre-parse? stage that implements the the Early Fast Discard functionality outside of the hardware forwarding pipeline stages.
A software fix is to be provided to optimize the ICU packet handling in these circumstances whereby EFD is required.
Monitoring of the condition is not easy when the drops are occurring that identify the packet loss.
A separate new show command is to be developed along with the fix for this problem so that it is easier to monitor from an operational perspective.
Workaround:
No realistic workaround exists.
Further Problem Description:
The buffers used in the ICU component are 'particalized'.
It is analogus to ATM cells, a certain payload may require an extra cell, but only a small portion of that cell is actually used.
this creates extra overhead (unused space) and in this case it takes a particle/buffer spot away that could be used for another packet.
This is experienced in a lower performance, or higher drop count because lesser buffers are available at that high pps rate with that
particular packet size.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1.SP2, 5.3.2.15i.BASE, 6.0.0.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv98171 | Title: | Tomahawk 100gige interface may be limited to 10gig of through put |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A 100 gigabit ethernet interface on a tomahawk linecard may be limited to 10 gig bandwidth.
Conditions:
A very rare timing issue seen during card initialization.This can be seen by drops in the TM for traffic sent over 10gig.
Workaround:
Only way to recover is to reload the linecard.
Further Problem Description:
The smu for this ddts is marked as obsolete and is superseded.
For XR 5.3.1 running Tomahawk linecards load this set instead:
https://supportforums.cisco.com/blog/12711241/xr-531-recommended-smu-set-tomahawk-linecards
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 6.0.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.SP2, 5.3.3.11i.BASE, 6.0.0.18i.BASE, 6.0.1.12i.BASE, 6.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux07434 | Title: | unhide LER disable knob incase of cef corruption |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
This DDTS is raised to track the change in the behavior of LER disable knob.
we keep it hidden, but make it persistent in configuration
(similar as to service unsupported-tranceiver).
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux08668 | Title: | Framed IP not sent in accounting stop record |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
With BNG as dhcpv4 proxy , observing framed ip is missing in the accounting stop message.
Also circuit-id is not present in accounting stop message.
Conditions:
This is seen in 5.3.2
Workaround:
There is no workaround.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.26i.BASE, 6.0.1.12i.BASE, 6.1.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu13459 | Title: | NSR not reaching ready state bcoz IPC transport went down on stndby |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:LDP NSR not ready due to standby LDP not connected to active
Conditions:IPC transport went down and the LDP recovery mechanism failed.
Releases impacted:
5.2.4, 5.3.0 and 5.3.1
Workaround:process restart mpls_ldp on standby node.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.8i.MPLS, 6.0.0.5i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw37832 | Title: | Umbrella SMU for FIB fixes |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The trigger of the issue is the activation of BGP sessions that are less than 500 prefixes, this causes that the VSM-500 card in less than 20 minutes the memory in this card fails.
Memory Leak in process prm_server_ty, after the reload of the VSM the resources were freed but started to leak again.
The impact is high because the clients connected to it, fails the connection when this happens.
+ The memory of the VSM-500 indicates that 997MB are available, watchdog memory has 1003.222 MB available, nevertheless CEF resources of the linecard in location 0/2 are in RED. For NR_LDI is almost exhausted:
RP/0/RSP1/CPU0:EDGE-VBJ-ASR9K-02#sh cef resource loc 0/2/CPU0
DATA_TYPE_TABLE_SET hardware resource: RED
DATA_TYPE_TABLE hardware resource: RED
DATA_TYPE_IDB hardware resource: RED
.
.
.
OBJECT USED MAX AVAILABLE
NR_LDI 2097072 2097152 80
Conditions:
VSM-500 Cards in ASR9K.
Workaround:
The only workaround available is to reload the VSM-500 in which the issue appears again after 20-30 minutes.
Further Problem Description:
The smu for this ddts is marked as obsolete and is superseded.
For XR 5.3.1 running Tomahawk linecards load this set instead:
asr9k-px-5.3.1.CSCuw65671.pie
asr9k-px-5.3.1.CSCux07434.pie
asr9k-px-5.3.1.CSCuw94704.pie
asr9k-px-5.3.1.CSCuv61090.pie
asr9k-px-5.3.1.CSCuw15926.pie
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut84353 | Title: | Session bringup fails with pqos service after RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Subscriber session bringup fails
Conditions:
After RPFO
Workaround:
None
Further Problem Description:
Doing RPFO with pqos service enabled subscribers causes session setup failure of new subscriber session which uses same pqos service.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.8i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut60174 | Title: | Service Update is not updated to LC subscribers |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
CoA Service update does not reflects on LC subscribers
Conditions:
Service update via CoA is updating RP service profile however which is not populated to LC and it would affect LC subscriber sessions. Restarting of subdb_svr on LC would help to recover this problem.
Workaround:
Restart of subdb_svr on LC
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.8i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu25888 | Title: | BGP sessions flapping during RSP FO due to stale nbr-reset post-it |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BGP flaps are seen up on RSP FO
Conditions:
The Standby RP BGP has an extra NSR post-it that gets applied after the RPFO as part of BGP Go-Active
operation. Since, the post-it is for BGP Neighbor Reset as part of Address-family Activation, the neighbor
session flaps after RPFO. Show bgp neighbor nsr standby - will show any pending post-its.
Workaround:
After the neighbor session flaps, wait for at least 5mins before issuing RPFO. Make sure ?show bgp neighbor nsr standby? shows no pending post-its before RPFO.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.2.5.22i.ROUT, 5.3.1.SP2, 5.3.2.8i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv00898 | Title: | 5.3.1 fib_mgr crashes on fib_cl_idb_lookup |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
fib_mgr crashes on fib_cl_idb_lookup
Conditions:
IOS-XR 5.3.1
It's also usually seen right after an interface flap
Workaround:
unknown yet
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.2.4.ROUT, 5.3.1.FWDG |
|
Known Fixed Releases: * | 5.2.5.41i.FWDG, 5.3.1.SP2, 5.3.2.22i.FWDG, 5.3.3.4i.FWDG, 5.3.3.8i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66111 | Title: | eXR: standby RP stuck in Unknown Band after back-to-back RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Standby RP stuck in Unknown Band after back-to-back RPFO for multiple times.
Conditions:
Run script to trigger back-to-back RPFO for multiple times on a 9904 router with dual RSPs..
Workaround:
Unknown.
Further Problem Description:
This issue only affects Next Generation XR platforms (such as eXR).
The affected source code does exist in the 5.3.3 release, but will not be seen on classic XR platforms
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | 5.2.5.41i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux49092 | Title: | ASR9K/4.3.4 new PW is created and stays down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
When a new PW is created, sometimes it stays down. Verify that you have the same symptoms as below:
1) "show l2vpn xconnect detail" reports
PW: neighbor D.E.F.G, PW ID 102, state is down ( provisioned )
although all bindings have been exchanged and match:
PW Status TLV in use
MPLS Local Remote
------------ ------------------------------ -----------------------------
Label 24012 24012
Group ID 0x1000300 0x1000400
Interface GigabitEthernet0/2/0/2.102 GigabitEthernet0/2/0/2.102
MTU 1500 1500
Control word disabled disabled
PW type Ethernet VLAN Ethernet VLAN
VCCV CV type 0x2 0x2
(LSP ping verification) (LSP ping verification)
VCCV CC type 0x6 0x6
(router alert label) (router alert label)
(TTL expiry) (TTL expiry)
2) Execute "show l2vpn xconnect group <> xc-name <> private" and it shall report that the LDP session is down:
LDP session state: down
3) Execute "show mpls ldp neighbor" and it shall report that the targeted-LDP session to that neighbor is active.
Targeted Hello (A.B.C.D -> D.E.F.G, active)
Conditions:
Issue is seen on ASR9K running 4.3.4 connected to ME3600 device although it could occur on all XR platforms.
The configuration must include both, PWs using default IPv4 source address (0.0.0.0) and PWs being configured with PW-class IPv4 source address (LDP Router ID).
Unconfiguring PWs or PWs being deleted due to BGP NLRI delete message are triggers to expose this issue.
Workaround:
Unconfiguring all PWs to that specific neighbor and rollback should address the issue.
Further Problem Description:
To determine if your system could be vulnerable to this issue on a system running 4.3.4 or 5.1.1 and later, execute "show l2vpn peer-db detail" and if it reports 2 source adjacencies, one being the LDP Router ID and the other one being 0.0.0.0 then the issue could be hit if all PWs associated to one of the source adjacency get deleted. Otherwise, the issue will not be hit.
RP/0/0/CPU0:one#show l2vpn peer-db detail
Peer Addr: D.E.F.G, Flags: 0x7, Dynamic count: 2, Entity ID: 0x0
ADJ List:
Source VC Count LDP Up
_________________________________________________
A.B.C.D 1 TRUE
0.0.0.0 1 TRUE
VC List:
...
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.23i.FWDG, 6.0.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy49956 | Title: | arp resolution failure on some of my interfaces connected btb to CE side |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Arp doesnt get resolved on the CE2 side on back to back connected links.
On CE2
0/1/CPU0
-------------------------------------------------------------------------------
Address Age Hardware Addr State Type Interface
40.2.113.1 00:00:05 0000.0000.0000 Incomplete ARPA GigabitEthernet0/1/0/30.113
40.2.113.2 - 001b.53ff.a3f1 Interface ARPA GigabitEthernet0/1/0/30.113
Conditions:
Satellites are in L2FAB topology and have btb connections to CE2
Workaround:
None known at present
Further Problem Description:
Obvious Ping failure as ARP is not resolved. Please see the attached logs.
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy37335 | Title: | SSTE: Memory leak of mibd_interface by lldp_client_copy_local_ma_td |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
mibd_interface memory can increase due to memory leak of lldp OID
Conditions:
Workaround:
Process restart mibd_interface to free up memory.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.20i.FWDG, 6.1.1.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy21312 | Title: | High rate VPN route churn makes CEF adjacencies wrongly programmed in LC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic black holing for VPNv4/VPNv6, potentially for other address family prefixes also. CEF entries in line card and RSP are out of sync., hence any update in RSP is not propagated to line card.
Recovery of the problem state is through line card reset.
Conditions:
Continous churn of VPNv4/VPNv6 prefix at rate high of 60K prefix in 15 secs interval and readvertise of these prefix again in next 15 mins for a extended high time results.
Workaround:
Make network design change or other config work-around to reduce amount of VPNv4/VPNv6 route churn is a possible work-around.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.ADMIN, 5.3.3.BASE, 5.3.3.CE, 5.3.3.FWDG, 5.3.3.K9SEC, 5.3.3.LC, 5.3.3.MCAST, 5.3.3.MGBL, 5.3.3.MPLS, 5.3.3.ROUT |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83217 | Title: | ASR9k msdp peer down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After upgrade from 4.3.0 to 5.3.2. All msdp peer were down. All are in NoIntf status.
MSDP Peer Status Summary
Peer Address AS State Uptime/ Reset Peer Active Cfg.Max TLV
Downtime Count Name SA Cnt Ext.SAs recv/sent
207.231.241.21 6509 NoIntf 5w2d 0 ? 0 0 0/0
Conditions:
There is switch between two MSDP peers.
Workaround:
process restart msdp or re-configure msdp.
Further Problem Description:
none
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.2.MCAST |
|
Known Fixed Releases: * | 6.1.1.3i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux43034 | Title: | PTP with ARB mode - Slave port stays unqualified after RSP switchover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After a reload or RSP switchover, it can be observed that PTP slave port stays unqualified.
This behavior can be seen independently of the timescale that is being used (PTP or ARB)
Conditions:
This behavior can be seen after a router reload or RSP switchover
Workaround:
There is no workaround
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.4.SP3, 5.3.3.23i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw10162 | Title: | TM performance issue with multiple ingress priority. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
packet drop when we have priority level 1 with police rate percent 100 and class default with default priority level.
Conditions:
when you have 2 classes with different priority level
Workaround:
If we remove the priority level 1 then there is no traffic drop.. have all class with same prioriity..
Further Problem Description:
none
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.BASE, 6.0.1.18i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux10339 | Title: | Rollback fails on ASR-9904 with Tomahawk in 10x10 breakout mode |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The function "rollover configuration last 1" may not work on a router equipped with the MOD-400-TR cards (8x100GE) when configured in 10x10GE breakout mode.
Conditions:
Workaround:
Save Router configuration ahead of time and restore it after, if needed.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux37954 | Title: | BFD Session Fails to come up after RPFO - BFD Label missing |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BFD Session Fails to come up after RPFO - BFD Lable missing
Conditions:
RP Failover
The Issue is seen on ? RP Failover , it's not very Consistent. It has seen on first RPFO . and Some time seen after ? 4 or 5
The Impact of the Issue is very severe ? as BFD sessions fails to come UP after RPFO ? Impact Control Plane / Data Plane.
Workaround:
None
Further Problem Description:
Recovery:
process restart bfd
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv27106 | Title: | MAC secure logging fail to work in ingress NP injected traffic |
|
Status: | Fixed |
|
Severity: * | 2 Severe |
Description: * | With this bug, MAC secure logging punt (if configured) by a CFM inject gets handled incorrectly. This is incrementing stats with un-initialized pointer causing the memory collisions.Symptom:
Mac secure not working or worse case, 800G LCs crashing.
Conditions:CFM and Mac secure configuration are needed to trigger this
Workaround:Remove CFM or Mac secure configuration.
|
|
Last Modified: | 01-MAR-2016 |
|
Known Affected Releases: | 4.3.1.BASE, 5.1.3.BASE |
|
Known Fixed Releases: | 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux86240 | Title: | mpls ldp blocked on mutex after LDP crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:mpls_ldp blocked on mutex after removing mpls ldp config
Conditions:issue seen with 64ECMP paths with high scale and seen with config nsr process-failures switchover
Workaround:process restart mpls_ldp recovers the issue
More Info:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 5.3.3.ADMIN |
|
Known Fixed Releases: * | 5.2.5.43i.BASE, 6.0.1.16i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy02954 | Title: | ASR9000v ICL line protocol Down after changing Vlan Encap type in L2fab |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
ASR9000v satellite fabric link line protocol Down after changing Vlan Encapsulation type in L2fab Satellite.
Conditions:
In any version, with the satellite feature, using L2 fabric for the satellite fabric link.
If the user changes the VLAN Encapsulation while the connection to the satellite is still connected, then the satellite-fabric-link line protocol will go down and stay down.
Workaround:
Ensure that the satellite has disconnected before changing the VLAN encapsulation type.
Note: the satellite side must have disconnected (not the host side), because this is using L2 fabric and so physical link state is not taken into account, either CFM must be used for quick state notifications or the link must be left for 30 seconds for the satellite to time out.
Further Problem Description:
Recovery: disconnect the satellite (by shutting the satellite fabric link for 30 seconds)
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux08285 | Title: | mrib6 process crash after removing multicast routing |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | mrib6 crash observed after removing second time multicast routing config .There is no impact on traffic as the issue seen after removing multicast routing
Symptom:
mrib6 crash observed after removing second time multicast routing config
Conditions:
mrib6 crash observed after removing second time multicast routing config
Workaround:
Further Problem Description:
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: * | 5.2.2.MCAST, 5.3.3.ADMIN, 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.23i.FWDG, 5.3.3.23i.MCAST, 6.0.1.13i.FWDG, 6.0.1.13i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux78563 | Title: * | 5.3.2 Umbrella SMU for NP soft error handling improvements |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unrecoverable ECC errors which results in LC reset
Conditions:
ECC Errors
Workaround:
no workaround. But LC will recover after reset
Further Problem Description:
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun23856 | Title: | error code "'obflinfra" when boot 1x100G Typhoon card |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PLATFORM-ENVMON-3-OPERATION_FAIL error is continuously shown every 20 minutes.
LC/0/5/CPU0:Feb 17 18:53:50.710 UTC: env mon_lc[164]: %PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in record_obfl_on_die_temp.2934, error code 'obflinfra' detected the 'warning' condition 'An invalid argument was passed'
Unused sensor is referred causing this error, and there is no impact to traffic or system.
Conditions:
ASR9K 100G LC is installed and run.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.17i.BASE, 5.1.3, 5.1.3.1i.BASE, 5.1.4, 5.2.0, 5.2.0.15i.BASE, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy14883 | Title: | RJIL: A9K-ISM-100 tracebacks after insertion |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
A9K-ISM-100 insertion in ASR 9006 chassis.
Conditions:
RP/0/RSP0/CPU0:SAR-1#sh ver brief
Fri Feb 5 11:25:17.295 IST
Cisco IOS XR Software, Version 5.3.3[Default]
Copyright (c) 2016 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 0.75(c) 1994-2012 by Cisco Systems, Inc.
SAR-1 uptime is 3 hours, 24 minutes
System image file is "disk0:asr9k-os-mbi-5.3.3/0x100305/mbiasr9k-rsp3.vm"
cisco ASR9K Series (Intel 686 F6M14S4) processor with 12582912K bytes of memory.
Intel 686 F6M14S4 processor at 2127MHz, Revision 2.174
ASR 9006 4 Line Card Slot Chassis with V2 DC PEM
4 Management Ethernet
20 GigabitEthernet
24 TenGigE
32 DWDM controller(s)
24 WANPHY controller(s)
8 HundredGigE
4 Integrated Service Module
4 Integrated Service Module
503k bytes of non-volatile configuration memory.
6111M bytes of hard disk.
12510192k bytes of disk0: (Sector size 512 bytes).
12510192k bytes of disk1: (Sector size 512 bytes).
RP/0/RSP0/CPU0:SAR-1#sh platform
Fri Feb 5 11:25:21.468 IST
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP440-SE(Active) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP440-SE(Standby) IOS XR RUN PWR,NSHUT,MON
0/0/CPU0 A9K-24x10GE-SE IOS XR RUN PWR,NSHUT,MON
0/1/CPU0 A9K-MOD80-SE IOS XR RUN PWR,NSHUT,MON
0/1/0 A9K-MPA-20X1GE OK PWR,NSHUT,MON
0/2/CPU0 A9K-ISM-100(LCP) IOS XR RUN PWR,NSHUT,MON
0/2/CPU1 A9K-ISM-100(SE) SEOS-READY
0/3/CPU0 A9K-8X100GE-SE IOS XR RUN PWR,NSHUT,MON
RP/0/RSP0/CPU0:SAR-1#
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux92476 | Title: | eXR: "Error: FPGA didnt complete cfg" is seen in Meldun / Dalla fallback |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Meldun / Dalla Golden FPD version can not become the running version after the FPD primary version is corrupted.
"Error : FPGA did not complete configuration." is seen.
Conditions:
Perform FPD fallback testing for Meldun / Dalla FPD.
Workaround:
Primary is get corrupted here and do upgrade of primary will recover it.
Further Problem Description:
There is an erratum with the muliboot mechanism on the Artix FPGA devices. The first 1K bytes of the image contains the sync word. If a valid sync word is present, then even if the rest of the image is corrupted, the multiboot mechanism will not switch over to the golden image due to the erratum. To work around this classic FPD erases the first 1K bytes of the image first and programs it last for the upgrade image.
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur23281 | Title: | [522 25i] LC sub - Junk values present in "show sessionMon" cli. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:Command "show sessionmon location ... statistics" shows active sessions even after all the sessions are cleared and "show subscriber session all" doesn't report any active sessions.
Number of sessions displayed in the output can be an excessively large number.
Conditions:Bulk session creation then deletion (i.e. high churn of subscriber sessions)
Workaround:process restart session_mon
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux57093 | Title: | BGP crashed in RPL after policy configuration |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP crashed in RPL, right after policy configuration. Customer is unable to perform further changes unless we understand and fix the crash.
Crash was continuous until customer rolled back RPL config.
Conditions:
- customer does not use XML, only CLI to configure the box;
- crash was continuous until config was removed;
- software is 5.1.3 with SP2:
- last commit before the first occurrence was:
route-policy NEST-RP-V4_BACKUP-POD3_EVRY_TED_PUBLIC_PROTECTED_POD3_IMPORT
# BACKUP IMPORT FOR VRF EVRY_TED_PUBLIC_PROTECTED_POD3 #
if extcommunity rt matches-every (15688:50043) then
if destination in PS-V4_VRF_EVRY_TED_PUBLIC_PROTECTED_POD3 then
pass
else
drop
endif
endif
end-policy
This policy is to be used within another policy, config is:
route-policy RP-V4_SHARED-BACKUP-POD3_IMPORT
apply NEST-RP-V4_BACKUP-POD3_*
Workaround:
The crash happened to string buffer overflow. When the wildcard apply feature is used with policy-name > 50 char there is high chance of hitting the crash.
Do not use the wild-card apply policy feature and specify the policy-names directly in the route-policy RP-V4_SHARED-BACKUP-POD3_IMPORT.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut83908 | Title: | A9K-RSP880-% VP0P9A/B Voltage Alarm |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
False voltage alarm might be detected at sensor VP0P9A or VP0P9B on A9K-RSP880 card.
Conditions:
This issue can be seen during normal operation when using A9K-RSP880 card.
Workaround:
No workaround.
Voltage alarm message can be ignored when a measured voltage sensor value is within the allowable range 801 - 959 mV.
Further Problem Description:
|
|
Last Modified: | 11-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.29i.BASE, 5.3.2.6i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy22423 | Title: | lpts counters do not increment for ICMP, TCP, UDP, IPv6, Fragmented IP |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Toplogy:
IxLoad(5/1)--------0/0/2/2(ASR9001-1)0/0/2/3------(5/2)IxLoad
IxLoad sends ICMP Nuke Attacks and ICMP Ping of Death attacks to IP and MAC address of interface Ten0/0/2/3. Ingress interface Ten0/0/2/2 drops packets. But LPTS does not show the packets being accepted or dropped. The counters for ICMP in Punt or PIFIB police do not increment. The rate is
set to 10pps. IxLOad sends traffic at much higher rate 118pps or thousands of PPS. Why LPTS counters are not incrementing?
We notice the same behavior for the following additional DDoS attack type of traffic. The following traffic type is setup and sent from IxLoad:
??? Fragmented IP
??? TCP Fin Flood
??? TCP Port Scan
??? TCP Fake Session
??? UDP Port Scan
??? IPv6 Extension Header
Conditions:
XR 5.2.4 on ASR9001, ASR9006 with RSP440SE and RSP8G, for DDoS traffic types: Fragmented IP (fragments sent from IxLoad; ICMP Ping of Death; ICMP Nuke Attack; TCP Fin Flood; TCP Port Scan; TCP Fake Session; UDP Port Scan; IPv6 Extension Header (sent from IxLoad).
RP/0/RSP0/CPU0:ASR9001-1# sh ver bri
Wed Feb 10 14:56:01.526 PST
Cisco IOS XR Software, Version 5.2.4[Default]
Copyright (c) 2015 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 2.04(20140227:092320) [ASR9K ROMMON],
ASR9001-1 uptime is 2 days, 3 hours, 26 minutes
System image file is "bootflash:disk0/asr9k-os-mbi-5.2.4/0x100000/mbiasr9k-rp.vm"
cisco ASR9K Series (P4040) processor with 8388608K bytes of memory.
P4040 processor at 1500MHz, Revision 2.0
ASR-9001 Chassis
2 Management Ethernet
8 TenGigE
20 GigabitEthernet
8 DWDM controller(s)
8 WANPHY controller(s)
219k bytes of non-volatile configuration memory.
2880M bytes of hard disk.
3932144k bytes of disk0: (Sector size 512 bytes).
Workaround:
Further Problem Description:
|
|
Last Modified: | 11-FEB-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy27587 | Title: | ftp_fs process crash after commit w auto-save usage |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
ftp_fs crash as seen in logs
0 sized file on FTP server
Conditions:
commit w auto-commit to ftp enabled.
Workaround:
Further Problem Description:
|
|
Last Modified: | 12-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus08895 | Title: | ASR9K: CWDM-SFP Optics reporting -40dB RX Power |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The output of "show controller phy" for an interface with CWDM optics reports -40dB RX power
Conditions:
Port on the ASR9K with CWDM optics installed
Workaround:
None, link is up and passing traffic even though the RX power is reported as -40dB
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.23i.BASE, 5.3.2.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua05309 | Title: | NGN:%L2-CDP-4-ERR_MULTICAST_ADDR_SET on typhoon LC OIR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Following error message was observed on ASR9K XR4.2.1 router -
LC/0/2/CPU0:May 22 12:15:25.824 EDT: cdp[132]: %L2-CDP-4-ERR_MULTICAST_ADDR_SET : Error setting up the CDP multicast address on TenGigE0/2/0/0 (media cdp ether driver): 'interface attributes library' detected the 'warning' condition 'Failed to receive a response for item'
Conditions:
The error was seen on performing a linecard oir of the typhoon linecard (24*10GE) on ASR9K router.
Workaround:
None. The error message doesn't affect functionality.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.16i.BASE, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.2i.BASE, 5.1.1, 5.1.11 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq45845 | Title: | Flow QoS Summary Not supported for this Card Type - Integrated ASR9001 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The 'show qos flow-aware summary' command does not work when a flow based QoS policy is attached to an interface of the integrated LC on the ASR9001/Ironman platform.
>> Example Error Msg:
RP/0/RSP0/CPU0:ASR-121#show qos flow-aware summary location 0/0/CPU0
Tue Aug 19 17:58:15.139 BST
Node: 0/0/CPU0
--------------------------------------------
Flow QoS Summary Not supported for this Card Type
Conditions:
applicable for IRONMAN LC
Workaround:
"show controllers np struct flow-qos-hash summary location..." shows a lot of the same information.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.1.BASE, 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.4.5i.BASE, 5.3.0, 5.3.0.6i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut90976 | Title: | asr 9000 crashes UDP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
udp, ipv4_io, ipv6_io, ping, trace processes crash on the ASR9K RP including ASR9001.
Conditions:
The frequency of the occurrence of this issue is very rare and the exact circumstances under which this happen is not known.
It happens when RP generates VRF packets which can be either of the v4 or v6 address family.
Typical application packets can be ping, traceroute and few others that make use of UDP when used in the VRF context.
All IOS-XR releases "may" be impacted starting from 3.7.3 upto 5.3.1 (inclusive)
Workaround:
None
Further Problem Description:
Implemented fix significantly reduces the probability of the occurrence of this issue. This fix is also introducing a new error message to provide more information in case of reoccurrence. Example of the new error message:
RP/0/RSP0/CPU0:Apr 20 15:20:41.899 : udp[436]: %PLATFORM-PLAT_V6FIB_RP-3-ERR_INFO_TBM : PLATFORM-FIB-IPV6_TBM: Function vkg_fib_vpnv6_rp_set_leaf_size line 298 TID 21 Error: Invalid argument rc: 0x16 Root pointer: 0x9cce6888 : pkg/bin/udp : (PID=544979) : -Traceback= ...
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.7i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur35867 | Title: | MoFRR Err IOS msg: "ROUTING-MOFRR_FLOW-3-DETECT_LOSS_PRIM" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The MoFRR error "ROUTING-MOFRR_FLOW-3-DETECT_LOSS" log message is periodically shown on the router console. No traffic loss is expected.
Conditions:
1. Each MoFRR-enabled multicast route requires two RPF interfaces. The two RPF intfs are configured on two different LCs. For the RPF intf type is bundle, it has only single bundle member configured in a specific LC.
In other words, on the issue LC, it does not host both RPFs, but must host one RPF.
2. More than 2048 MoFRR routes have been ever installed in the router. For the same route, if it is deleted and created again, due to IGMP join request, control plane considers it as a completely new route installation.
3. Some existing MoFRR routes have been removed from the router in history. Starting from the 2049th MoFRR route installation, the MoFRR error message can be shown in the router console.
Workaround:
1 If both RPFs of MoFRR routes are the physical intfs, then make sure these two RPFs are in the same LC.
2. For RPF intf with bundle-intf type, add minimum a bundle member in each LC.
3. When issue happens, we need to do either above configuration and then reload the issue LC once.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.0.MCAST, 5.2.0.MCAST, 5.3.0.MCAST |
|
Known Fixed Releases: * | 5.2.3.12i.BASE, 5.3.0, 5.3.0.13i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx88470 | Title: | "show access-lists hardware" displays wrong wildcard bits |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When Ethernet Services ACL is configured with MAC address and its Mask:
The show access-list ethernet-services acl-name hardware
displays incorrect MAC Mask address. The value are displayed 1's complement.
Conditions:
When Ethernet Services ACL is configured with MAC address and its Mask.
Not with Host MAC address.
Workaround:
This is a display issue and no functionality are effected.
No workaround.
Further Problem Description:
This is a display issue and no functionality are effected.
The show command display incorrect i.e complemented info for mask.
show access-list ethernet-services acl-name hardware
The detail show command display the correct user configured for mask.
show access-list ethernet-services acl-name hardware ingress detail
show access-list ethernet-services acl-name hardware egress detail
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.2.1, 4.2.1.19i.BASE, 4.2.2, 4.2.3, 4.2.3.1i.BASE, 4.2.4, 4.3.0, 4.3.0.3i.BASE, 4.3.1, 4.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur85208 | Title: | CombineSMU 434: CSCug75299 CSCun45857 CSCur39291 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Please refer to release note of following ddts CSCug75299 CSCun45857 CSCur39291 for details.
Conditions:
Please refer to release note of following ddts CSCug75299 CSCun45857 CSCur39291 for details.
Workaround:
Please refer to release note of following ddts CSCug75299 CSCun45857 CSCur39291 for details.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 4.3.4.SP6, 4.3.4.SP7, 4.3.4.SP8, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud62965 | Title: | iosxr-ce-4.2.3online_diag_rsp traceback seen on 4.2.3 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RP/0/RP1/CPU0:Dec 11 02:55:44.771 EST: online_diag_rsp[444]: %PKT_INFRA-PAK-3-OWNERSHIP_PROCESS_FREE : Client with pid 200824 tried to access freed packet b19719d8 (pak pid -200824) : pkg/bin/online_diag_rsp : (PID=200824) : -Traceback= 420aa63 9781647 9781e98 97828c3 9780d9f 9780c47 8279010
Conditions:
These are harmless messages caused by unexpected conditions triggered by switchovers.
Switchovers some time cause unexpected amount of packets sent to diagnostic process on standby RP, diagnostic process failed to handle the unexpected amount of packets and gets stuck in an infinite loop continuously displaying the error messages.
Workaround:
Restart process online_diag_rsp at the location where this errors were originated.
Example:
process restart online_diag_rsp location 0/rp1/cpu0.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.CE |
|
Known Fixed Releases: * | 4.3.1.14i.BASE, 5.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc99135 | Title: | MetronCluster:Lic udi mismatch licDB and license_opid in nvram |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
licmgr crashes after chasis swithover in an NV-Cluster.
Conditions:
A9K-NV-CLUSTR-LIC is installed on both chassis in the NV-Cluster.
Workaround:
None
More Info:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.12i.BASE, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.2i.BASE, 5.1.1, 5.1.11 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf29568 | Title: | Green FAN LED when Fan failure is detected |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LED on FAN Tray turn on as Green although it detects fan failure.
Conditions:
When the system detects fan failure.
Workaround:
none.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.1.28i.BASE, 4.3.2.11i.BASE, 5.1.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul09693 | Title: | 20Mbps shaper improperly set at L0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Bundle interface egress transmit rate is lower than expected
Bundle subinterface egress transmit rate is lower than expected
Bundle subscriber egress transmit rate is lower than expected
Conditions:
Bundle member interface flaps with Bundle subscribers with SPI QoS policy .
Workaround:
LC Reset or apply a port shaper policy on the Bundle main interface. The port shaper value can be set to bundle member interface speed.
Further Problem Description:
The impact of this bug is that all traffic on the interface will get shaped to the subscriber QoS policy parent class-default shaper value and so the full bandwidth of the link will not be available.
Use "show qoshal entity np <> tm <> chunk <> level 4 abs-index <> hierarchy location <> " to dump the TM hierarchy and check if L0 PIR value is not what is expected. [Note: abs-index is the qid of any queue used by this port]
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.13i.BASE, 5.1.1, 5.1.1.17i.BASE, 5.1.11, 5.1.11.13i.BASE, 5.1.12, 5.1.2, 5.1.2.9i.BASE, 5.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74719 | Title: | when use FC4, only one link btw FIA and XBAR on MOD400 is used |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Only one link out of 4 between FIA and XBAR on 400MOD card is used while any FC and FC4 are present only.
Conditions:
the problem only happens when you use FC4 and any other one FCs
Workaround:
if you only use two FC in the ASR9912/ASR9922 chassis, just don't let FC4 be one of them
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.26i.BASE, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw83281 | Title: | Syslog issue with show controllers fabric fia drops ingress location |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Error messages is seen when we issue command "show controllers fabric fia drops ingress location" many times.
sysdb_svr_local[351]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'oper/pm/dwdm/if/dwdm0_0_0_0/prev/15min/otn/0' from 'pm_collector' (jid 375, node 0/RP0/CPU0). No response from 'pm_ma' (jid 297, node 0/0/CPU0) within the timeout period (100 seconds)
Conditions:
When "show controllers fabric fia drops ingress location 0/0/CPU0" runs for 1000 times.
Workaround:
None Known.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo68315 | Title: | 10GE Interface is down/ down when g709 is configured on DWDM controller |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
G709 framing on DWDM controller causes the tengige interface to be a down state without OTN mode enabled on the tengige interface.
G709 is only supported with OTN mode on the tengige interface.
Conditions:
DWDM controller configured with G709 parameters.
Workaround:
conf t
interface tengig <>
transport-mode wanphy
commit
no transport-mode
commit
Further Problem Description:
Reproduced this issue in the lab and found that there is no alert/ message generated by the ASR when one tries to configure G.709 on a tengige interface operating in LAN mode. Also, to make the ports UP/ UP, had to disable the G.709 framing and then reload the sub-slot/ SPA.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.ROUT |
|
Known Fixed Releases: * | 5.1.3.10i.BASE, 5.2.0.26i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud41075 | Title: | Cisco unsupported PID SFP+Optics not working with trans permit pid all |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In Typhoon based Line cards, unsupported PID Optics may not work even with over-ride command
'transceiver permit pid all'. Optics Transmit laser will be disabled.
Conditions:
Normal
Workaround:
None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE, 4.2.3.ADMIN, 4.2.3.BASE, 4.2.3.LC |
|
Known Fixed Releases: * | 4.3.1.14i.BASE, 5.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup14095 | Title: | bogus P-RDI alarm on wanphy port |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Path rdi on wanphy port is constantly alarming but there is no problem with traffic.
RP/0/RSP1/CPU0:ios#show controllers wanphy 0/3/0/5 all
Active Alarms[All defects]: path rdi,
Active Alarms[Highest Alarms]: path rdi
Curent Alarms: 0x800
RP/0/RSP1/CPU0:ios#
Conditions:
Wanphy port is configured.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 5.2.2, 5.2.2.14i.BASE, 5.2.21, 5.3.0, 5.3.0.1i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh59250 | Title: | Some Voltage thresholds on typhoon LCs are too tight |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Some voltage thresholds for typhoon LCs are too tight, and you will see "normal" voltage readings outside of the threshold, specifically the upper threshold.
Conditions:
This was seen in 4.2.1, but likely exists in many versions.
This was specifically seen on the LC type A9K-24x10GE-TR, for the following voltages:
VP1P0_N4_CORE
VP1P0_N3_CORE
VP1P0_N2_CORE
IBV_D
N0_CORE_DB
1.0_N1_CORE_DB
1.0_N5_CORE_DB
1.0_N6_CORE_DB
1.0_N7_CORE_DB
1.8_N67_IO_DB
Workaround:
None.
But note this does not indicate a problem with the ASR9k router. And because the ASR9k does not internally trigger an alarm on LC voltages exceeding thresholds, no false alarms are raised.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 5.1.11.17i.BASE, 5.1.2.12i.BASE, 5.2.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj36219 | Title: | show controllers fabric ltrace crossbar Returns Illegal Option |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
This DDTS doesn't impact any functional operation or traffic switching of the router. A customer doesn't need to apply fix for this DDTS to improve any operation on the router. It mainly addresses a redundant harmless cosmetic error message that gets displayed when an operator or TAC engineer executes a specific CLI command (referenced in DDTS subject line) to gather few debug logs from the router. The debug logs are still available in-spite of the harmless error message.
Conditions:
The error message is displayed only when the debug CLI command is executed. The debug logs are still available as output of the command.
Workaround:
No work around.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.11i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12, 5.1.2, 5.1.2.1i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug92501 | Title: | Additional ltrace to debug cbc version shown as "?????.?????" on TinyIM |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Can Bus Ctrl (CBC) version on rack-1 Route Switch Processor (RSP) displays "?????.?????" and subsequent attempts to upgrade the CBC fails with the following error message:
RP/1/RSP0/CPU0:May 15 20:14:18.966 : canb-server[151]: %PLATFORM-CANB_SERVER-3-OPERATION_FAIL : Failed in process_cbc_fw_upg_response.1209, error code cbc fw upg no active partition
Conditions:
The issue persists only while upgrading the XR image using px-pie image.
Workaround:
No known workaround exists other than reloading of chassis.
More Info:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.23i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.14i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup83242 | Title: | 250ms of delay switching links using LAG 1+1 with PBB |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Typhoon linecards with PBB and 1+1 LAG (1 active, 1 standby) see a 250ms delay when switching from the active and standby link.
Packets get dropped with in the NP by RSV_DROP_EGR_LAG_NO_MATCH counter.
Conditions:
* PBB
* LAG 1+1 (1 Active, 1 Standby)
* Switchover
Workaround:
None.
Further Problem Description:
After further testing, it was revealed that increased delay was due HW programming time of the bundle delete and add sequence. In addition, this delay is proportional to the number of NPs on the linecard. This DDTS covers an optimization to reduce the programming time spent deleting a bundle.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 5.2.2, 5.2.2.18i.BASE, 5.2.21, 5.2.3.6i.BASE, 5.3.0, 5.3.0.5i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud99694 | Title: | RSVP packet drop on NP after Bundle interface down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RSVP PATH message drop on NP without punting to RP.
Conditions:
Bundle interface down
Workaround:
remove Bundle interface and use physical interface
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.0.1.LC, 4.2.3.LC |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.24i.BASE, 4.3.2, 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: | CSCue84161 | Title: | AC shut on Typhoon, ucode not account PARSE_DROP_IN_UIDB_DOWN drop |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On Typhoon line card, when AC interface is shutdown, "show interface" input drop counter stops incrementing.
Conditions:
VPLS/VPWS with AC interface configured on Tyhoon line card, shut down AC interface.
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: | CSCui41536 | Title: | typhoon GE-T port enabled auto-nego though that int was shutdown |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
auto negotiation works though the interface was shutdown state.
Conditions:
configure "negotiation auto" to GE-T on typhoon LC
Workaround:
no shutdown
commit
shutdown
commit
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.29i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.1, 5.1.1.7i.BASE, 5.1.11, 5.1.11.4i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug74967 | Title: | Cluster: IF-MIB:ifOperStatus incorrect after removal & reinsert |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:Missing EOBC interfaces on ifmib query.
Conditions:After all the EOBC fibers cross cluster unplugged and re-plugged in.
Workaround:Restart mibd_interface process.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.2.17i.BASE, 5.1.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun43331 | Title: | ASR9k LC bootup cause 19 sec mcast traffic drop |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Upon ASR9k LC bootup, PIM and MRIB are all updated with new RPF, but MFIB took 18-19 sec to get programmed.
The MFIB platform init call is taking a long time to complete and that intrudes into the control plane convergence time. We see the following in the traces:
Feb 27 18:33:02.813 mfwd/ipv4_mfwd_partner 0/0/CPU0 t1 MFWD started..
Feb 27 18:33:07.143 mfwd_ipv4_hw/init 0/0/CPU0 t1 Initialized EDM backend
Feb 27 18:33:26.273 mfwd_ipv4_hw/init 0/0/CPU0 t1 Initialized fabric and registered with MGID programmer
Feb 27 18:33:27.090 mfwd_ipv4_hw/init 0/0/CPU0 t1 Initialized uIDB manager
Feb 27 18:34:34.032 mfwd_ipv4_hw/init 0/0/CPU0 t1 Initialized connection to PRM
Feb 27 18:34:51.285 mfwd_ipv4_hw/event 0/0/CPU0 t1 PRM NP State change: Event: Running; New state: Running; Previous state: Unknown State
Conditions:
none
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.20i.BASE, 5.1.3, 5.1.3.1i.BASE, 5.1.4, 5.2.0, 5.2.0.22i.BASE, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup37279 | Title: | l2fib_mgr crash in l2fib_access_field_bridge_port |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:l2fib_mgr crash:
LC/0/3/CPU0:Jun 5 03:24:41.862 MEST: dumper[56]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/l2fib_mgr
LC/0/3/CPU0:Jun 5 03:24:41.865 MEST: dumper[56]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 200 for process pkg/bin/l2fib_mgr
Conditions:Observed on ASR9000 router acting as PE in VPLS solution, when access side bundle flaps and MAC Security is enabled.
Workaround:No workaround known.
More Info:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.13i.BASE, 5.1.4, 5.2.2, 5.2.2.14i.BASE, 5.2.21, 5.3.0, 5.3.0.1i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul46311 | Title: | Process punt_switch is blocked on mdio_lc on Trident linecard |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
process punt_switch is blocked on mdio_lc on Trident linecard
Conditions:
In some linecard instances, interrupt from Clock-mux would get stuck during initialization. This was rarely seen on 8*10G Trident linecard. The condition can also occur on 16*10 Trident linecard.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.20i.BASE, 5.1.11, 5.1.11.16i.BASE, 5.1.12, 5.1.2, 5.1.2.12i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut27090 | Title: | Sysdb error from 'show controllers fabric plane all' on Tomahawk 9922 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RP/0/RP1/CPU0:Megatron#show controllers fabric plane all
Thu Feb 26 10:27:34.093 GMT
Flags: Admin State: 1-Up 2-Down 12-UnPowered 16-Shutdown
Oper State: 1-Up 2-Down 3-Admin Down
Summary for All Fabric Planes:
Plane Id Admin State Oper State Links Up Links Down In Pkt Count Out Pkt count
=============================================================================================
0 01 01 12 00 6410433084 6412414284
1 01 00 12 00 2112564071 2112564209
Error: 0x40818600 getting item from Sysdb.
Error: 0x40818600 getting item from Sysdb.
Error: 0x40818600 getting item from Sysdb.
Conditions:
Seen on an ASR9922 running 5.3.0 FCS. Chassis has RP2 and SFC2, plus a mix of Typhoon and Tomahawk linecards.
Workaround:
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.24i.BASE, 5.3.2.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun18574 | Title: | Mac addresses are taking more than the configured time to age out. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MAC sometimes ages out at half an age longer than configured. For instance, when MAC age is 10 minutes, it may take 15 minutes for the MAC to age out.
Conditions:
Assume a MAC is initially received from wire and learned on Asr9k at time 0. If the same MAC is seen again 1.5 minutes after the initial learning, the MAC age is extended with another half age. In the end, the MAC ages out at 1.5 times of the full age.
Workaround:
None
Further Problem Description:
This is day one issue. It exists on Typhoon LC in all the releases starting from 4.2.0.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.0.BASE, 4.3.2.BASE, 5.0.0.BASE, 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.18i.BASE, 5.1.3, 5.1.3.1i.BASE, 5.1.4, 5.2.0, 5.2.0.18i.BASE, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu39816 | Title: | Umbrella DDTS for CSCum07427 and CSCuo85256 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PLEASE Refer to Individual Constituent DDTS for RNE
Conditions:
PLEASE Refer to Individual Constituent DDTS for RNE
Workaround:
PLEASE Refer to Individual Constituent DDTS for RNE
Further Problem Description:
PLEASE Refer to Individual Constituent DDTS for RNE
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.4, 4.3.0, 4.3.91, 5.2.2, 5.2.21, 5.3.0, 5.3.1, 5.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur77989 | Title: | ASR9K USB not able to user after process restart devc-conaux |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
1# USB works fine initially
2# process restart for devc-conaux, after this console still work, no usb error info
3# re-plug USB device
4# USB not able to use, medie server report it is down
5# process restart umass-enum will recover
6# after 5# process restart devc-conaux will not trigger issue again.
Conditions:
process restart devc-conaux on a booted ASR9K.
as been tested, below release been affected
4.3.2
5.1.1
5.1.2
5.1.3
5.2.0
Workaround:
process restart umass-enum could recover
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.2.4.14i.BASE, 5.2.5.8i.BASE, 5.3.0, 5.3.0.17i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue46842 | Title: | FPD update for CBC on ISM fails (18.05 to 18.06 or 18.07) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CBC upgrade from 18.05 to a higher revision fails
Conditions:
A9K-ISM-100 card
Release 4.2.1, 4.2.3, or 4.3.0
Workaround:
None
More Info:
It has been determined that there is no impact by not being able to upgrade the CBC FPD on the ISM module.
FPD upgrade works in 4.3.1
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.22i.BASE, 4.3.2, 4.3.2.7i.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: | CSCug08468 | Title: | FanRunTime thresholds need to remove from show env table |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
admin show environment table location 0/FT0/* shows threshold values for Fanruntime values. But there are no thresholds for FanRunTime.
Conditions:
CLI admin show environment table location 0/FT0/*
Workaround:
None
More Info:
There are no thresholds for FanRunTime. Removed from the output.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.2.15i.BASE, 5.1.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud21216 | Title: | ASR9k Bundle-hash CLI not working correctly. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The Bundle hash CLI on a ASR9k with RSP440,24x10GE LC (New Generation of LC's) when executed to find the Bundle members that the PW flow is hashing out to provides incorrect result.
The hash results in selecting just one member link all the time even when the Load-balancing is done per VC label.
Conditions:
This is primarily seen with the new generation of LC's/RSP440.
Workaround:
There isn't a workaround to find the right member that the PW Flows are hashing out to.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.0.37i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue76149 | Title: | Hardcoded altitude config disappear from 9922 after reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
Environment altitude configuration under admin-config mode goes missing after reload of the router.
Conditions:
Router reload will cause the config to disappear.
Workaround:
To configure the environment altitude again after router reload.
Further Problem Description:
None.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.1.26i.BASE, 4.3.2.11i.BASE, 5.1.0.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub32631 | Title: | Typhoon policer: drop packet count not showing in show interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptoms
On Typhoon card, the "total drops" count is always zero when the policer configured on the port is dropping violated traffic.
It's still working on Trident card.
Conditions
Normal operation
Recovery and Workaround
N/A
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.FWDG, 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.1.12i.BASE, 5.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu18694 | Title: | ASR9922 CBC_1 of RP in RESET - leading LC 11 and above down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Line cards on lower ASR9922 shelf are not visible via show platform.
Conditions:
Seen on reload after software upgrade or chassis reload.
Workaround:
Failover RP to recover
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.9i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue45839 | Title: | 100GE Umbrella SMU for 423 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Combo SMU for critical 100GE issues (hard port down, interface flap etc) identified in 423.
Please see individual ddts Release note for more details:
CSCud82637 (100G interface Flap after reload on 430)
CSCud84488 (100G Link shows RFI after LC reload and re-inserting fiber)
CSCue29814 (100GE interface flap during remote end reload)
CSCue21659 (OIR of CFP optic in 2x100GE LC results in permanent down port)
Conditions:
During router or LC reload in 423 with C-SMU pack#2
Workaround:
None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.2.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw60002 | Title: | ASR9k Cluster: Incorrect remote rack slotmask for loopback with IC flag |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
L3 Multicast IPv4 Auto-RP mapping information not populated on an ASR9k in cluster configuration
Conditions:
This issue occurs under the following conditions:
- ASR9k in cluster configuration
- Mhost default interface is picked as Loopback interface (Loopback interface has IC flag set in 224.0.1.40 route)
- RPF interface of (S,G) entries for group 224.0.1.40 is on Rack 1
- L3 Multicast configuration and routes come up before IRL links are configured/active
Workaround:
To prevent this issue from happening, when deploying a new cluster enable the IRL links and make sure they are Up and active before enabling multicast configuration.
If the issue has already occured, the following workaround can be used:
Workaround involves toggling the IC flag on the Loopback interface associated with the the 224.0.1.40 route
1) Configure a new loopback interface (say loopback 2)
2) Enable multicast for loopback 2
3) Configure the following: mhost ipv4 default interface loopback 2
Optional: Rollback all configuration changes (remove loopback 2 and mhost config)
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.3.MCAST |
|
Known Fixed Releases: * | 5.3.3.14i.BASE, 6.0.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh82767 | Title: | NVRAM driver process should not crash when NVRAM content is corrupt |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Customer node had NVRAM corruption.
Symptom:
If NVRAM corruption should occur, ensure that the node can recover on subsequent boot.
Conditions:
The cause of the NVRAM corruption could not be determined.
Workaround:
None.
Further Problem Description:
Seen once.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.24i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.14i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun22806 | Title: | p2mp packet loss when a router changes from a transit to a bud node |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Multicast packet loss over p2mp tunnel is observed on existing receivers behind the newly added MTE destination.
Conditions:
1. p2mp is built
2. new destination for the same MTE is added
3. new destination is on the transit MTE node
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.MCAST |
|
Known Fixed Releases: * | 5.1.2.20i.BASE, 5.1.3.1i.BASE, 5.2.0.25i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj39371 | Title: | prm_server_ty process crash after NP lockup and fast reset |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
prm_server_ty process crash after multiple NP resets.
Conditions:
Multiple NP resets that would normally cause LC reload seems to crash prm_server_ty
Workaround:
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.LC |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.11i.BASE, 5.1.1, 5.1.1.13i.BASE, 5.1.11, 5.1.11.8i.BASE, 5.1.12, 5.1.2, 5.1.2.5i.BASE, 5.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui71137 | Title: | Lamptest works only on Active RSP after several RSP switchovers |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Lamptest works only on Active RSP
Conditions:
After RSP switchovers several times
Workaround:
process restart of lamptest-rp
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 5.1.1.8i.BASE, 5.1.11.4i.BASE, 5.1.2.1i.BASE, 5.2.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub88542 | Title: | Ironman:show environment altitude returns no altitude info |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On ASR9001 prior to 4.3.0, admin show environment all or admin show environment altitude doesn't show any values:
RP/0/RSP0/CPU0:ASR9001-B#admin show environment altitude
Sat Feb 23 04:16:37.684 UTC
Altitude:
RP/0/RSP0/CPU0:ASR9001-B#
Conditions:
Execute the commands, admin show environment all or admin show environment altitude on a ASR9001 running version prior to 4.3.0.
Workaround:
None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.28i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu97228 | Title: | Cluster:IF-MIB:ifOperStatus incorrect after reload with SMU CSCut11994 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On ASR9k cluster, ifOperStatus can be report link down after reload although nv edge control port is up
Conditions:
Workaround:
process restart mibd_interface
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.15i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj21109 | Title: | Fabric umbrella DDTS for 421 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
This is an Umbrella DDTS for Fabric related fixes. Check the individual DDTS RNE for details.
CSCuj10837 PUNT_FABRIC_DATA_PATH diag test failure due to fabric link retrain
CSCui46432 PuntFabricDataPath test unpredicatble recovery/alarm clear
CSCtz54145 MTRON EDVT: Pkt loss on FC OIR because of LXBAR-FIA link re-train
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 5.1.2.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo04520 | Title: | change policy-map cause qos_ma_ea Crash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
qos_ma_ea process in line card crash crash when trying to change the policy-map.
Conditions:
it happen when we are trying to change the policy-map, it sometime happened, don't always happened.
Workaround:
To be determined.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.2.LC |
|
Known Fixed Releases: * | 5.1.3.6i.BASE, 5.2.0.21i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue56003 | Title: | Port Shutdown no shutdown L2VPN donot work between trident and Typhoon |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When the remote port shutdown feature is configured, in some scenarios, the remote interface does not come up even after the local interface is up.
Conditions:
This occurs in EoMPLS port mode where the local AC status is propogated to the remote peer and remote peer does not come up.
Typical scenario involves Trident card one side and Typhoon on the other side as the access interfaces.
Workaround:
Remove and reconfigure "propogate remote-status" on each of these access interfaces.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.19i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.1, 5.1.1.10i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui31482 | Title: | traffic loss on certain flows when member links down in MGSCP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Packet forwarding does not work consistently on a bundle interface that is configured with MGSCP solution (using "lacp cisco enable link-order signaled")
Conditions:
The following conditions need to be met to see this issue:
- Configuring bundle for MGSCP solution (using "lacp cisco enable link-order signaled")
- Failing different bundle members of this bundle.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 5.1.1.11i.BASE, 5.1.11.4i.BASE, 5.1.2.1i.BASE, 5.2.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum74080 | Title: | Umbrella SMU for CSCum57888 and CSCul22468 MAC security feature abnormal |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MAC security logging message is not generated.
Conditions:
Case A: 1. The MAC security configuration is action none and logging enabled. 2. MAC move happens between two physical ACs on Trident LC. 3. The two physical ACs happen to locate on two different NP. When all three conditions are met, the problem occurs.
Case B: The problem shows up when the L2 frames which causing MAC move have frame size larger than 1024 bytes.
Workaround:
None
Further Problem Description:
The combo SMU include fix of two DDTS. For details of the two problems, please refer to the individual DDTS. CSCum57888 and CSCul22468
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.LC |
|
Known Fixed Releases: * | 5.1.2.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui41348 | Title: | New memory profile for LSR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Forwarding performance on A9K-2x100GE may not meet 192B linerate.
Conditions:
100G line rate testing.
Workaround:
Increase the average packet size.
Further Problem Description:
This SMU improves forwarding performance on A9K-2x100GE. This reduces the L2 mac scale to carve out more memory for QOS and LAG.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.1.LC |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.6i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12, 5.1.2, 5.1.2.99i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug35276 | Title: | only maximum 8 paths for a recursive prefix message displayed too much |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Log message:
LC/0/0/CPU0:Apr 13 21:38:22.333 : fib_mgr[169]: This line card supports only maximum 8 paths for a recursive prefix, please change the configs to not exceed 8 paths or else system behaviour will be sub optimal
is displayed for every path list, and may get superfluous. request to reduce frequency of message display for this one.
Conditions:
more then 8 recursive paths on trident based Linecards.
Workaround:
reduce the number of recursive paths or use typhoon based LC's that have 32 way recursive.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.9i.BASE, 5.1.1, 5.1.11, 5.1.12, 5.1.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh02312 | Title: | %QOS-QOS_EA_MODIFY_FAIL-3-ERROR : inconsistency detected due to ANCP or |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
During physical EP OIR of MOD80 Linecard the following error message was observed.
qos_ma_ea[307]: %QOS-QOS_EA_MODIFY_FAIL-3-ERROR : inconsistency detected due to ANCP or Bandwidth modification. Execute show qos inconsistency, to obtain information. Main I/F without policy-map doesn't have BW
Conditions:
EP OIR and QOS policy configuration in that linecard.
Workaround:
NONE
More Info:
ANALYSIS:
The interface manager could send bandwidth with 0 to qos-ea process when EP is removed in certain conditions, and qos-ea process treat as error and print console message, and no further process is done in qos-ea process.
Fix Description:
The console message is misleading, and change this to debug message.
IMPACT:
No Functional impact.
Recovery:
N/A
Release found:
4.3.1.28i
Release impact:
All
Platforms impact:
ASR9K
To-Be-Fixed:
4.3.2
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.19i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.11i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj78368 | Title: | shelfmgr needs to set card state upon CBC reset and power budget |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:Cards may be put in BRINGDOWN state and not recover
Conditions:This problem may be caused when a power deficiency occurs
Workaround:None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE, 5.1.1.BASE |
|
Known Fixed Releases: * | 4.3.2.SP8, 5.1.1.17i.BASE, 5.1.11.13i.BASE, 5.1.2.9i.BASE, 5.2.0, 5.2.0.5i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur97356 | Title: | lma configuration errors |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
operation not permitted for certain pmip config
Conditions:
unconfig of certain CLis when bindings are present
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz94658 | Title: | WX/Wolverine: Allow DM7041-R Copper SFP to operate |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Marvell copper SFP RevB2 is not supported on 20x1GE MPA for typhoon linecards. This revision with smu is operational on Trident.
The REV-b0 is supported.
Conditions:
copper SFP with revision B2
Workaround:
none exist for this problem.
With the Rev-B0 the Preamble is not defined correctly in teh framing. Revision B2 solves this on the copper SFP, but this optic is not supported.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.LC |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.11i.BASE, 5.1.4, 5.2.0, 5.2.0.22i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug81800 | Title: | Cluster:CLI disabled EOBC I/F is displayed as Admin ENABLED |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The output of command: "show nv edge control control-link-protocols location 0/RSP0/CPU0" displays the port as admin Enabled, even after setting SFP port as admin Disabled using the CLI command: nv edge control control-link disable 1 location 0/RSP0/CPU0.
Conditions:
The issue persists when the Cisco ASR 9000 system runs in Network Virtualization Edge (nV Edge) Cluster mode.
Workaround:
No known workaround exists.
More Info:
No Functional impact.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.21i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.11i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut20960 | Title: | ether_ctrl_msg_client is in mutex from last 6 hours on tomahawk |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ether_ctrl_msg_client is in mutex from last 6 hours on tomahawk
Conditions:
ether_ctrl_msg_client is in mutex from last 6 hours on tomahawk
all forwarding and protocols is down on line card 7
Workaround:
ether_ctrl_msg_client is in mutex from last 6 hours on tomahawk
Further Problem Description:
ether_ctrl_msg_client is in mutex from last 6 hours on tomahawk
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.23i.BASE, 5.3.2.3i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo44524 | Title: | "Unknown or Unsupported XFP Module" displayed for 100 M XFPs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Description and PID in "show inventory" is missing.
Conditions:
when executing "show inventory" command
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.11.BASE |
|
Known Fixed Releases: * | 5.1.3.11i.BASE, 5.2.2.15i.BASE, 5.2.3.1i.BASE, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul26794 | Title: | MST BPDU not forwarded over Bundle EFP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The ARS9000, on local-connect services, does not forward BPDU on egress Bundle EFP with push TAG operation:
interface Bundle-Ether44.200 l2transport
encapsulation dot1q 200
rewrite ingress tag pop 1 symmetric
Conditions:
The issue is only present on Trident based LC.
Workaround:
Tunnel the BPDU via L2PT (l2protocol cpsv tunnel).
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.2.CE |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.11i.BASE, 5.1.1, 5.1.1.17i.BASE, 5.1.11, 5.1.11.13i.BASE, 5.1.12, 5.1.2, 5.1.2.9i.BASE, 5.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus57676 | Title: | NGN:bogus %PLATFORM-ENVMON-4-FAN_SPEED_MAX msgs seen on ASR9922/RP2 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On a ASR9922/rp2 running 5.3.0.23i with latest V2 fan trays, following warning is being seen periodically on the router -
RP/0/RP0/CPU0:Jan 20 11:05:28.037 EST: envmon[205]: %PLATFORM-ENVMON-4-FAN_SPEED_MAX : One or more fans have reached the maximum speed for the current power profile. Please enable extended-temp/50C profile for better cooling
Conditions:
Normal operation. The error message appears even with the fans running at normal speed without getting near the max RPM.
Workaround:
If there is really a temperature problem in the lab environment then the message could appear in valid condition. In that case configure "power budget profile extended-temp" in the admin config mode. Otherwise ignore the error message.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.20i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj01579 | Title: | CEF Wrong RPF pointer |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Ingress traffic received by the ASR9000 router on Ethernet interfaces and IRB interfaces "may" get dropped when Strict uRPF is configured on those interfaces.
Conditions:
The ingress traffic drop is seen on ASR9000 series of routers (including ASR9001).
The impacted Line card PIDs are:
A9K-MOD*
A9K.*SE
A9K.*TR
A9K.*-L
A9K.*-B
A9K.*-LE
The affected IOS-XR releases are:
4.2.0, 4.2.1, 4.2.3, 4.3.0, 4.3.1, 4.3.4, 5.1.0
Workaround:
There is no workaround.
Based on reconfiguration of the affected interface, sometimes the traffic drop may not be seen.
However the method is unreliable.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 4.3.4.SP8, 5.1.1, 5.1.1.17i.BASE, 5.1.11, 5.1.11.13i.BASE, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur76739 | Title: | asr9k pppoe with 4 dot1q tags not forwarded on pseudowire |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Ingress PPPoE packets with 4 dot1q tags are dropped on a VPLS bridge domain.
Conditions:
Traffic ingress on asr9k VPLS PE running XR version 5.1.3 or 4.3.4
Workaround:
pppoe traffic ingress with 3 dot1q tags are forwarded
Further Problem Description:
n/a
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE, 5.1.3.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.10i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh40447 | Title: | Implement power down of LCs during reload location all |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
reload location all, may cause power sequencer on XMEN & ODIN LC LT7510 to go bust
Conditions:
reload location all or install upgrade resulting in full chassis reload
Workaround:
As a temporary workaround a SMU has been recommended to delay the reset time of LC. Please refer to CSCug92413 for more details.
More Info:
The solution to this issue would be to power-off the line-cards during reload location all instead of doing a 'power-cycle' . The line-cards will be powered up when the RP cards come up after reload.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.2.BASE, 5.1.0.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.23i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.18i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf77374 | Title: | LC reported FIA Egress drop during RSP440 OIR with 4.3.1 image |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom,
Less than 10 pkts lost on red october line cards. Drops do not occur on XMEN LCs.
Conditions,
When RSP3 either physically inserted or when RSP3 is hw-module reloaded and at the time of power up, few pkts are dropped in fabric on Red October LCs.
At the time of removal of card physically or when at the time RSP3 is powered down, there is no packet drop. Drops on Red october cards occur when RSP3 powers up or when it is inserted.
Workaround,
No workaround.
Recovery
Self recovered.
Symptom:
Multicast traffic may suffer (drop) when unrelated or more ports over-congested with unicast traffic.
Conditions:
Over congestion of one or more 10Gig ports. This will result in one VQI occupying all the buffers from fabric global pool. As a result multicast traffic may not get any fabric buffers and hence packets may get dropped.
Workaround:
One of the potential workaround is to change the priority of the multicast traffic
Further Problem Description:
This fix is required along with CSCug90300 to resolve buffer starvation.
CSCug90300 reduced global threshold value for buffers but it is still smaller then per-vqi buffer threashold. Hence in case of congestion unicast was still utilizing all the buffers in global pool leaving no buffers for multicast in the presence of congestion.
This fix reduces per-vqi
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.2.18i.BASE, 5.1.0.9i.BASE, 5.2.0, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus48063 | Title: | fabric fia soft-error-monitor command is rejected for empty slot |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
If we try to configure "fabric fia soft-error-monitor" command for empty slot, it will be rejected.
But this command will be set after reloading system.
RP/0/RSP1/CPU0:SF9006B#admin show platform
Thu Jan 22 18:02:32.504 jst
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP440-TR(Standby) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP440-TR(Active) IOS XR RUN PWR,NSHUT,MON
0/FT0/SP FAN TRAY READY
0/FT1/SP FAN TRAY READY
0/0/CPU0 A9K-8T-L IOS XR RUN PWR,NSHUT,MON
0/1/CPU0 A9K-2T20GE-E IOS XR RUN PWR,NSHUT,MON
0/2/CPU0 A9K-4T-L IOS XR RUN PWR,NSHUT,MON
0/PM0/SP A9K-3KW-AC READY PWR,NSHUT,MON
0/PM1/SP A9K-3KW-AC READY PWR,NSHUT,MON
RP/0/RSP1/CPU0:SF9006B#admin config
Thu Jan 22 18:02:36.472 jst
RP/0/RSP1/CPU0:SF9006B(admin-config)#fabric fia soft-error-monitor 2 location 0/3/CPU0
RP/0/RSP1/CPU0:SF9006B(admin-config)#commit
Thu Jan 22 18:02:58.496 jst
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed' from this session to view the errors
RP/0/RSP1/CPU0:SF9006B(admin-config)#
RP/0/RSP1/CPU0:SF9006B(admin-config)#show configuration failed
Thu Jan 22 18:03:08.085 jst
!! 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.
fabric fia soft-error-monitor 2 location 0/3/CPU0
!!% 'CfgMgr' detected the 'fatal' condition 'This configuration has not been verified and can not be accepted by the system.'
RP/0/RSP1/CPU0:SF9006B(admin-config)#
Conditions:
None
Workaround:
Reloading system
Further Problem Description:
This issue is observed when trying to apply the configuration to an empty slot, following a redundancy failover event.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.17i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue43360 | Title: | asr9k 4.2.3 IRB URPF drops packets from connected host |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Strict unicast rpf (ipv4 verify unicast source reachable-via rx) configured on a BVI is dropping ping packets from a connected host.
Conditions:
ASR9000 running 4.2.3.
Workaround:
Problem not seen with loose rpf (reachable-via any).
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.3.1.22i.BASE, 4.3.2.7i.BASE, 5.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug20193 | Title: | ASR9K: L3 Mcast packets get out of sequence when ECMP Hash Bypass is set |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:Packet reordering is seen for Multicast flows, when fabric is loaded.
Conditions:Following conditions need to be meet to observe the issue:
- Any image from 4.0.1 up till 4.3.0 will observe this issue
- Trident based Line cards are only affected
- System never had any L3 ECMP or L3 bundle configured on the box
Workaround:configure an L3 ECMP path. This should clear the ECMP Hash Bypass bit.
More Info:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.0.1.BASE |
|
Known Fixed Releases: * | 4.3.1, 4.3.1.29i.BASE, 4.3.2, 4.3.2.14i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh41940 | Title: | Packet capture facility displays packet with incorrect leading bytes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When using the command "monitor np" (a new troubleshooting feature in 4.3.1), bytes 0-4 and 0x0040-43 of the captured packet are not showing true contents of the packet on the console/packet capture
Conditions:
Only seen when using the packet capture facility in XR 4.3.1
Workaround:
Ignore the first 4 bytes of the packet contents from the packet capture (generally fabric header)
More Info:
eg, highlighted bytes below are incorrect (in between Astrix)
From Egress Fabric1: 86 byte packet, bytes[0-3] invalid!
0000: *00 11 01 00* 82 00 02 03 08 0c 00 00 02 00 0e 00 ................
0010: 26 80 00 00 00 02 00 09 85 e8 33 8b 00 8b 00 d6 &........h3....V
0020: 01 00 5e 00 00 12 00 00 5e 00 01 0d 08 00 45 c0 ..^.....^.....E@
0030: 00 28 e0 fe 00 00 ff 70 8b e2 ac 1f c1 92 e0 00 .(`~...p.b,.A.`.
0040: c0 04 40 0e 6e 01 00 01 03 3f ac 1f c1 91 00 00 @.@.n....?,.A...
0050: 00 00 00 00 00 00 ......:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.3.1.LC |
|
Known Fixed Releases: * | 5.1.0, 5.1.0.14i.BASE, 5.1.1, 5.1.11, 5.1.12, 5.1.2, 5.1.3, 5.1.4, 5.2.0, 5.2.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh65684 | Title: | SFP+ RSP LEDs stays green even afteroptic removal |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
even after optic is removed form SFP+ port0/port1 on RSP, the LED still stays green, and does not change as expected.
Conditions:
EOBC ports on RSP440
Workaround:
reload router or none.
However the issue is cosmetic and actually functionality of the EOBC ports linkstate etc are not affected.
The bug is in the SW manipulating the LED state only.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.4.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.20i.BASE, 5.1.3, 5.1.3.1i.BASE, 5.1.4, 5.2.0, 5.2.0.13i.BASE, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun95680 | Title: | DIE_OVERTEMP_CRITICAL alarm in IMUX0 & EMUX0 @ Nominal temperature |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"PLATFORM-ENVMON-2-DIE_OVERTEMP_CRITICAL" pfm message is raised and cleared immediately in 9920 chassis with 2x100GE-SE / TR board.
Conditions:
During bootup of linecard card or chassis in 5.1.1 or 5.1.2 release.
Workaround:
None.
The PFM message clears automatically within 90 secs.
Further Problem Description:
It is FALSE PFM ALARM due to software bug
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.3.11i.BASE, 5.2.2.14i.BASE, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup25092 | Title: | could not configure QoS for false TM resource error |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
configure QoS fail and prompt not enough TM resource, however this error is false error since the TM resource is not in OOR condition.
interface GigabitEthernet0/0/1/0
service-policy output qos_huge
!!% 'prm_ezhal' detected the 'warning' condition 'Not enough TM resources to satisfyrequest'
!
end
Conditions:
On WeaponX TR line card, after EP OIR and prm_server_ty process restart/crash, the counters used to track TM resource usage may be incorrect.
Workaround:
Reload the line card
Further Problem Description:
The same root cause can also cause interface default queues not created properly so that all traffic gets dropped.
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 4.2.1.LC |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.12i.BASE, 5.1.4, 5.2.0, 5.2.0.29i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq55098 | Title: | satellite fan speed missing - reports zero value |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Satellite fan speeds are reported as 0 on host.
Conditions:
When host is x86 based connected to 9000v satellite.
Workaround:
Though host displays fan speed as 0, satellite console can be used to check for actual fan speeds.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.2.BASE, 5.1.3.BASE, 5.2.0.BASE, 5.2.2.BASE |
|
Known Fixed Releases: * | 5.1.2.SP3, 5.1.2.SP4, 5.1.3, 5.1.3.23i.BASE, 5.1.3.BASE, 5.1.4, 5.1.4.5i.BASE, 5.2.2, 5.2.2.23i.BASE, 5.2.21 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy30675 | Title: | eXR: vic %OS-CHUNK-7-DESTROY_NOTEMPTY trcbacks are seen on brkout intfs |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
vic %OS-CHUNK-7-DESTROY_NOTEMPTY tracebacks are seen on breakout interfaces on OTN LC.
Conditions:
Bring up breakout interfaces on an OTN (A9K-8X100GE-SE) LC.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux33851 | Title: | CEF reporting OOR for multiple LCs affects the traffic on the router |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
error message observed on the LCs "ROUTING-FIB-2-OOR : CEF has run out of DATA_TYPE_TABLE_SET resource memory. No more route updates will be handled by CEF. Please delete routes, and then clear CEF on this node to resume normal operation"
Conditions:
error message observed on the LCs "ROUTING-FIB-2-OOR : CEF has run out of DATA_TYPE_TABLE_SET resource memory. No more route updates will be handled by CEF. Please delete routes, and then clear CEF on this node to resume normal operation"
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 4.3.4.FWDG |
|
Known Fixed Releases: * | 5.3.2.SP2, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv83731 | Title: | Process radiusd crashed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Suddenly radiusd crash. Probably due to show command from Cisco Prime Network.
1488645 -rw- 9228 Sat May 2 11:10:35 2015 first.radiusd_1124.by.radiusd.20150502-111014.node0_RSP0_CPU0.x86.txt
1488644 -rw- 181365 Sat May 2 11:10:36 2015 first.radiusd_1124.by.radiusd.20150502-111014.node0_RSP0_CPU0.x86.cpu_info.Z
1488643 -rw- 8436 Sat May 2 15:52:13 2015 first.radiusd_323.by.radiusd.20150502-153524.node0_1_CPU0.ppc.txt
1488604 -rw- 239071 Sat May 2 15:52:14 2015 first.radiusd_323.by.radiusd.20150502-153524.node0_1_CPU0.ppc.cpu_info.Z
1488606 -rw- 8436 Sat May 2 15:52:37 2015 first.radiusd_323.by.radiusd.20150502-153549.node0_2_CPU0.ppc.txt
1488607 -rw- 8436 Sat May 2 15:52:39 2015 first.radiusd_323.by.radiusd.20150502-153614.node0_3_CPU0.ppc.txt
1488608 -rw- 8436 Sat May 2 15:52:39 2015 first.radiusd_323.by.radiusd.20150502-153638.node0_5_CPU0.ppc.txt
1488640 -rw- 174655 Sat May 2 15:52:38 2015 first.radiusd_323.by.radiusd.20150502-153549.node0_2_CPU0.ppc.cpu_info.Z
1488646 -rw- 159318 Sat May 2 15:52:40 2015 first.radiusd_323.by.radiusd.20150502-153614.node0_3_CPU0.ppc.cpu_info.Z
1488647 -rw- 168143 Sat May 2 15:52:41 2015 first.radiusd_323.by.radiusd.20150502-153638.node0_5_CPU0.ppc.cpu_info.Z
1488648 -rw- 8344 Wed May 13 13:52:45 2015 first.radiusd_298.by.radiusd.20150513-135216.node0_4_CPU0.ppc.txt
1488649 -rw- 103155 Wed May 13 13:52:46 2015 first.radiusd_298.by.radiusd.20150513-135216.node0_4_CPU0.ppc.cpu_info.Z
Conditions:
Probably during aggressive show commands which was run by remote script.
Workaround:
No workaround
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.14i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv68172 | Title: | A9K-2X100-SE/TR interface flapping after "no shut" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After installing the SMU for CSCus50857, we see that the 100GE interface flaps many times before stabilizing. The delay is anywhere from 30 seconds to almost 2 minutes before the interface will stay up/up.
Conditions:
Note that in our testing we have a DWDM system between the two systems 100GE ports:
ltn-pcor-11-Hun0/2/0/1<-->DWDM<-->mnl-pcor-11-Hun0/2/0/1
Workaround:
Use interface command "carrier-delay up 2000 down 0" to reduce syslog messaging. This does not however resolve the delay.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.10i.BASE, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw43356 | Title: | Radius Attribute 95 has wrong length |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Radius authentication requests packets dropped by server.
Conditions:
IOS-XR 5.3.1
Workaround:
None
Further Problem Description:
Attribute 95 (NAS-IPv6-Address) should have a length of 18 per RFC, but XR uses a length of 22.
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.21i.BASE, 6.0.0.19i.BASE, 6.0.1.12i.BASE, 6.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux48875 | Title: | Sureshot EDVT: 1NP LC Reports Link Status Error for Depopulated NP |
|
Status: * | Other |
|
Severity: * | 3 Moderate |
Description: | Symptom:
Link Status message reported on LC console
Conditions:
LC booted into IOS XR RUN
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw16530 | Title: | show config changes causes "show_config_changes" process to crash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
show_config_changes process crashes
Conditions:
If one issues show configuration commit changes last <# of the commit> diff
Workaround:
Try to review a smaller number of commits changes. If their are 100 commit, please try "show configuration commit changes last 40 diff" instead.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.3.LC, 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.15i.BASE, 6.0.0.16i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv26647 | Title: | For-us traffic intercepted by ABF vrf-select instead of being punted |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
For-us traffic is not being punted to the router CPU
Conditions:
This problem is observed when Access-list Based Forwarding (VRF select) is configured
Workaround:
Add an access-list entry before the abf "next-hop" entries which permits the local traffic.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.10i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv06372 | Title: | 1.3.6.1.2.1.31.1.2.1.3 oid is populated with incorrect value |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:1.Some interfaces returned as bundle members even though they do not belong to particular bundle.
2 (notInService) returned even though interfaces are valid bundle members. Prior to restarting snmp and mibd_interface, valid members returned 1 (active).
Conditions:When polling for ifStackStatus for specific bundle, interfaces not being bundle members returned along with legitimate bundle members.
Workaround:reload the router will solve the problem 1 and restarted 'mibd_interface' processes fixed problem 2.
More Info:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.11.LC |
|
Known Fixed Releases: * | 5.2.5.37i.BASE, 5.3.1.SP2, 5.3.2, 5.3.2.18i.BASE, 5.3.3.3i.BASE, 6.0.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut46951 | Title: | tacacsd crash with 5.1.3 when sourcing from BE interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | - after upgrading from 4.2.1 to 5.1.3, tacasd crashed
RP/0/RSP0/CPU0:kpi-idn1-asr9k#sh run
RP/0/RSP0/CPU0:Feb 25 22:42:55.613 : dumper[60]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/tacacsd
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/tacacsd
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV : Thread 8 received SIGSEGV - Segmentation Fault
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0x4211397. Signal code 1 - SEGV_MAPPER. Address not mapped.
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-CRASH_INFO : Crashed pid = 1143043 (pkg/bin/tacacsd)
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 317
RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use
RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-DEFAULT_PATH_TMP : Setting default path to /tmp/dumper for core size less than 20971520. Core dump size 18313216, free memory size 3698614272.: default path for core dump
- after upgrading from 4.2.1 to 5.1.3, tacasd crashed
RP/0/RSP0/CPU0:kpi-idn1-asr9k#sh run
RP/0/RSP0/CPU0:Feb 25 22:42:55.613 : dumper[60]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/tacacsd
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/tacacsd
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV : Thread 8 received SIGSEGV - Segmentation Fault
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0x4211397. Signal code 1 - SEGV_MAPPER. Address not mapped.
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-CRASH_INFO : Crashed pid = 1143043 (pkg/bin/tacacsd)
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 317
RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use
RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-DEFAULT_PATH_TMP : Setting default path to /tmp/dumper for core size less than 20971520. Core dump size 18313216, free memory size 3698614272.: default path for core dump
Symptom:- after upgrading from 4.2.1 to 5.1.3, tacasd crashed
RP/0/RSP0/CPU0:kpi-idn1-asr9k#sh run
RP/0/RSP0/CPU0:Feb 25 22:42:55.613 : dumper[60]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/tacacsd
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/tacacsd
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV : Thread 8 received SIGSEGV - Segmentation Fault
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0x4211397. Signal code 1 - SEGV_MAPPER. Address not mapped.
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-4-CRASH_INFO : Crashed pid = 1143043 (pkg/bin/tacacsd)
RP/0/RSP0/CPU0:Feb 25 22:42:55.614 : dumper[60]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 317
RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use
RP/0/RSP0/CPU0:Feb 25 22:42:55.615 : dumper[60]: %OS-DUMPER-6-DEFAULT_PATH_TMP : Setting default path to /tmp/dumper for core size less than 20971520. Core dump size 18313216, free memory size 3698614272.: default path for core dump<
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.6i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30542 | Title: | Separate PI fix needed for DDTS CSCuv49005 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After router running for more than 4 days its is seen the usage by ifc-ipv6 in shwmin goes high and total shwmin usage crosses the LC max so throwing errors messages and this causes instability and might impact the programming of new prefixes.
RP/0/RP0/CPU0:LER1#sh memory location 0/5/CPU0 | i ifc
Tue Aug 11 13:34:57.526 PDT
Shared window ifc-mpls: 4M
Shared window ifc-ipv6: 1260M
Shared window ifc-ipv4: 15M
Shared window ifc-protomax: 4M
RP/0/RP0/CPU0:LER1#sh memory location 0/1/CPU0 | i ifc
Tue Aug 11 13:35:13.342 PDT
Shared window ifc-mpls: 13M
Shared window ifc-ipv6: 61M
Shared window ifc-ipv4: 259M
Shared window ifc-protomax: 4M
RP/0/RP0/CPU0:LER1#
Conditions:
Router running with ipv6 prefixes in global or user defined vrf
Workaround:
LC restart help in fixing the issue for the time-being
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.2.FWDG |
|
Known Fixed Releases: * | 5.3.1.SP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu12722 | Title: | BGP process crash when "clear bgp" for BGP neighbor with soft-reconfig |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP crashes when clear bgp is issued, when nbr has soft-reconfig configured.
Conditions:
Soft-reconfig must be configured on NBR. The crash happens only when re-populating routes from soft reconfig DB.
Workaround:
None
Further Problem Description:
Applicable to 5.3.1 onwards. Please see integrated-release field in ddts to see if fix is committed to any 5.3.X release.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.8i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu64368 | Title: | "show tech-support lpts" crashes Tomahawk LC. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"show tech-support lpts" CLI leads to crahses NP on Tomahawkas.
Conditions:
Tomahawk Linecard has some traffic. and execute "show tech lpts"
Workaround:
Don't execute "show tech-support lpts"
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.12i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw46460 | Title: | ROUTING-FIB-3-PD_FAIL FIB Cannot insert leaf for pfx pointing to Null0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Following syslog might be seen if route resolves through Null0 on ASR9K 3rd generation Ethernet line card.
fib_mgr[185]: %ROUTING-FIB-3-PD_FAIL : FIB platform error: fib_leaf_insert 5193 Cannot insert leaf
Conditions:
/32 route updated with next hop recursing through Null0
Workaround:
Disable BGP PA.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.FWDG |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2.SP2, 5.3.3.18i.BASE, 6.0.1.12i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv27376 | Title: | Add a malloc_opts API to control malloc arena truncation behavior |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:This ddts is to introduce malloc_opt MALLOC_SHRINK_OPTION to control this behavior - thus, applications not using the MALLOC_SHRINK_OPTION will see the previous behavior of shrinking to a minimal size, applications using MALLOC_SHRINK_OPTION will see the new behavior of only shrinking to the size set by MALLOC_ARENA_SIZE
Conditions:Workaround:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2, 5.3.2.19i.BASE, 5.3.3.5i.BASE, 6.0.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut47229 | Title: | radiusd crashed during longevity |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
This radius crash is happened because of the memory leak caused by CSCur45394.
Conditions:
For every Access-Accept sent by radius was leaking some amount (32 bytes) memory. So whenever it reaches max memory limit of process radius process used to get crash.
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.2.4.14i.BASE, 5.2.5.8i.BASE, 5.3.1.SP2, 5.3.2, 5.3.2.4i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw15926 | Title: | Drops on Bundle subinterface are counted as parent interface drops |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Drops on Bundle-Ether subinterface are counted on parent Bundle interface:
IOS-XR 531 outputs:
########### 2000 PING PACKETS SENT THAT SHOULD GENERATE URPF COUNTS ###########
RP/0/RP0/CPU0:RSN-SAR01#sh int bundle-ether 101 | i input drop
Fri Sep 4 16:53:41.521 BST
4762 packets input, 2772304 bytes, 2000 total input drops <<<<<<<<
RP/0/RP0/CPU0:RSN-SAR01#sh int bundle-ether 101.1115 | i input drop
Fri Sep 4 16:29:25.766 BST
4278 packets input, 791930 bytes, 2000 total input drops
RP/0/RP0/CPU0:RSN-SAR01#sh cef interface bundle-ether 101 rpf-statistics location 0/1/CPU0 <<< Not accounted in per interface RPF stats for main int
Fri Sep 4 16:54:43.368 BST
Zero Counters Found for node(0/1/CPU0).
RP/0/RP0/CPU0:RSN-SAR01#sh cef interface bundle-ether 101.1115 rpf-statistics location 0/1/CPU0
Fri Sep 4 16:30:15.392 BST
Unicast RPF drops 2000
Conditions:
This is only seen for Bundle-Ether subinterfaces. Drops on TenGig subinterfaces are not counted on parent TenGig interface.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.3.10i.BASE, 6.0.0.15i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv63743 | Title: | slingshot:VIC process restart causes interface flap |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
following SF-BER take about 1 min 45 sec to be cleared in case of cable OIR or detect LOS
%PLATFORM-VIC-4-BER_SF_ALARM : port: 0, SF-BER, status: set
%PLATFORM-VIC-4-BER_SF_ALARM : port: 0, SF-BER, status: clear
Conditions:
- RIght after LC reload
- LR4 CPAK is inserted
Workaround:
shut/no shut the interface resolve the abnormal state
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux48456 | Title: | BGP does not import some vpls prefixes after reload with bridge scale |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: |
Symptom:Some remote VPLS prefixes are not imported into bridge-domain with high bridge-domain scale.
Conditions:L2VPN VPLS address-family should be configured along with high bridge-domain scale.
Workaround:Reduce the bridge-domain scale
More Info:The problem is seen with really high bridge-domain scale in the order of tens of thousands of bridge-domains.
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 6.0.0.BASE, 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22323 | Title: | Combined SMU for CSCup86576, CSCun48934 and CSCtz68435 |
|
Status: | Fixed |
|
Severity: * | 3 Moderate |
Description: | Symptom:
Multiple different symptoms might be seen due to these issues.
1. Timing related features do not work due to I2C failure with Zarlink chip
2. BPE server and L2vpn process terminates continuously on Asr9001 cluster testbed.
3. bpe and l2vpn process crash can be seen with impact on related services, and backplane idprom information can be missing on the box. P2P Sync issues can also be observed.
Conditions:
Router reload/Rack switchover/Image upgrade etc. In short, anything which makes the 9001 RSP to reboot.
Workaround:
Usually another reload of the router resolves the issue.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18293 | Title: | The traffic blackholing due to continuous FIB traceback on LC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Continuous FIB Manager traceback
Conditions:
Not Known
Workaround:
LC Reload
Further Problem Description:
Show cef mpls adjency interface will show NHinfo in retry mode
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.3.2.MPLS |
|
Known Fixed Releases: * | 6.0.1.19i.FWDG, 6.1.1.2i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuj05069 | Title: | Partial LDP config loss on downgrade from 5.1.1.6I to 5.1.0. |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
MPLS LDP Targetted session config will be lost after downgrade from 5.1.1 to 5.1.0 or earlier images.
Conditions:
MPLS LDP Targetted session config will be lost after downgrade from 5.1.1 to 5.1.0 or earlier images.
Workaround:
None. The lost config can be seen using "show configuration failed startup" command. Re-apply the config after removing the address-family ipv4 from the config.
Further Problem Description:
In 5.1.1 the LDP configuration model was overhauled to support VRFs and anticipate IPv6. This has caused some configurations to be lost when downgrading.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.1.1.BASE, 5.1.1.MPLS, 5.3.2.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy02244 | Title: | eXR: FC IPU-FPGA stuck in "NOT READY" after upgrd is interrupted by OIR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
FC IPU-FPGA stuck in "NOT READY"..
Conditions:
When FC IPU-FPGA upgrade triggered by "upgrade hw loc 0/fc2 fpd IPU-FPGA force" command is in progress, the
FC is pulled out physically to interrupt the upgrade.
Workaround:
Restart fpd_agent process.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux17894 | Title: | SSTE: MPLS Static Flex-CLI corrpution in running config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MPLS static Flex-CLI config of "path 1 nexthop Bundle-Ether1 92.93.1.2 out-label 1000228" are corrupted in running config. The corruption only apply to this specific label of 1000228.
Conditions:
issue is seen only when label is configured inside the group
Workaround:
No workaround. The label are applied correctly , just the label are not show up correctly in show running-configuration output.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw98619 | Title: | eXR: duplex support error and link speed update issue |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
duplex support error and link speed update issue
Conditions:
Change duplex mode and speed on a MgmtEth interface.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy44103 | Title: | 533: bpm traceback upon bgp config removal |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
bpm traceback may occur on the console
Conditions:
upon removal of bgp
Workaround:
Not known
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu87189 | Title: * | RP2:Voltage alarm seen from sensor PMOD10_0_9V_VSENSE |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Voltage alarm seen from sensor PMOD10_0_9V_VSENSE.
The alarm syslog will come as well as it will show up in sh led detail.
Conditions:
The problem can occur at any time in RP2 boards.
Once the voltage value goes beyond the voltage threshold values; alarms can come.
Workaround:
These alarms can be ignored as the threshold value which are set in the sw are not the exact expected values.
The alarms can be false one as well.
If the alarm comes , we can check with the actual threshold values which are as follows and then decide if the alarms are real or false ones.
VKG_VOLT_PMOD9_0_9_V_VSENSE 783 - 971 mV (range of acceptable voltage values)
VKG_VOLT_PMOD10_0_9_V_VSENSE 783 - 971 mV (range of acceptable voltage values)
VKG_VOLT_PMOD12_0_9_V_A_VSENSE 783 - 971 mV (range of acceptable voltage values)
VKG_VOLT_PMOD11_0_9_V_A_VSENSE 783 - 971 mV (range of acceptable voltage values)
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.SP2, 5.3.2, 5.3.2.16i.BASE, 5.3.3.3i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy40875 | Title: | IOS-XR: VRF-Aware MSDP rpf lookup failure under BGP IPv4 multicast SAFI |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
IOS-XR router running VRF-Aware MSDP configuration with external neighbour fails to accept MSDP SAs, because of RPF check failure for advertised external RP address inside MSDP SAs. RP address is advertised through eMP-BGP peering with the same MSDP peer under IPv4 multicast SAFI2.
Conditions:
- VRF-Aware MSDP configured in VRF-lite manner w/o MVPN
- External RP and multicast sources addresses are advertised only through eMP-BGP IPv4 multicast SAFI2
- URIB doesn't contain neither RP nor multicast sources addresses
Workaround:
WA # 1:
- Advertise RP address under BGP IPv4 unicast SAFI1 or configure a static IPv4 route toward RPs address under particular VRF URIB
WA # 2:
- On the external eMP-BGP/MSDP peer advertise underlying BGP peering IPv4 subnet under multicast SAFI2
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy31181 | Title: | bgp_show process crashed while executing "show bgp nexthops" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
bgp_show process crash when sh bgp vrf <> nexthops is executed.
Conditions:
sh bgp vrf <> next hops with lot of next hops.
Workaround:
execute show command with exact next hop ip address.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux54623 | Title: | Partial Support for SESSION_ATTRIBUTE C_TYPE 1 as per RFC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When inter-op with 3rd Party Router that send RSVP Path messages with affinity in SESSION Attribute object, Cisco XR router will fail to parse the object and reject the messages causing LSP Set up failure
Conditions:
3rd Party router sends RSVP Path messages with affinity in SESSION Attribute object with C_TYPE 1
Workaround:
None.
Further Problem Description:
Cisco is not following RFC3209 strictly.
Cisco to Cisco is working fine because XR do not use Session Attribute Object C_TYPE 1 for affinity.
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.4.0.BASE |
|
Known Fixed Releases: * | 6.0.1.19i.MPLS, 6.0.1.20i.MPLS, 6.1.1.3i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv21952 | Title: | Thor NetFlow: incorrect OutputInterface when egress interface is BVI |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"show flow cache" output displays entries with OutputInterface as 0 (zero) or random (incorrect) interface.
Conditions:
- Netflow is applied on Ingress to POS interface on SIP-700 line card
- interface receives MPLS (L3VPN) traffic
- egress interface is BVI with ACs on 9000v satellite
Workaround:
Since IFH field is not programmed in CPP Hardware.
Included the IFH filed and read the IFH value from CPP Hardware , Updated the same to the output interface
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.1.3.LC |
|
Known Fixed Releases: * | 6.0.1.20i.BASE, 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux52913 | Title: | IPv6 prefix over IPv4 SRTE via static route: no cef entry on LC |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IPv6 prefix over IPv4 SRTE via static route: no cef entry on LC, and see the following continuous error:
LC/0/0/CPU0:Dec 13 07:56:28.948 : fib_mgr[185]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_LABEL_INFO[ptr=8ad6a988,refc=0x1,flags=0x8001930] Action=CREATE Proto=mpls. Cerr='FIB' detected the 'warning' condition 'Invalid argument' : pkg/bin/fib_mgr : (PID=376949) : -Traceback= 4ce69140 4ed9a714 4ed9af5c 401f3790 401f3d10 401f3eb0 400c6280 400c6f74 4018cbdc 4018e49c 400bdbd8 400bfc60 400c0ba4 400dba34 400dc640 40192bcc
Conditions:
ASR9K XR 6.0.0
The problem happens when destination IPv6 prefix has local label allocated by LDPv6 or BGP.
Workaround:
Use route-policy to make LDPv6/BGP not allocate local label for destination IPv6 prefix
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 6.0.0.FWDG, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.20i.FWDG, 6.1.1.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux91985 | Title: | 533 26i - MRIB crash @ mrib_platform_l2_cmp_slotmask |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MRIB process is reloaded one time during IGMP leave requests from total 4K groups on a BVI interface in MLDP setup.
Conditions:
In Rosen MLDP (Profile 0) setup with 4K multicast flows having BVI intf as outgoing interface (OLE).
200 data mdts is configured in the MLDP. Send IGMP leave for entire 4K groups on the BVI interface
at the same time.
Workaround:
There is no functionality impact observed during the MRIB process reload and its seen only once so far.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.1.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux36987 | Title: | mibd_interface leaks memory when CFM MIB is polled |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The mibd_interface process leaks memory, the output of 'show memory heap dllname ' shows the number of MakeOctetString allocations increasing.
Conditions:
This issue occurs when polling the ieee8021CfmMib (1.3.111.2.802.1.1.8), specifically when polling the dot1agCfmMepDefects field (1.3.111.2.802.1.1.8.1.7.1.1.14)
This issue can occur on all IOS-XR releases including CFM:
3.7.3 onwards for ASR9K
3.9.0 onwards for CRS
4.0 onwards for C12K
5.2.1 onwards for NCS6K
Another condition is to have CFM enabled on L2 subinterfaces used as AC with pseudowires.
Workaround:
The user can only work around this issue by excluding the dot1agCfmMepDefects field from MIB walks. If the value of dot1agCfmMepDefects is required, there is no workaround.
Exclusion is done via the following configuration command:
snmp-server view v1default 1.3.111.2.802.1.1.8.1.7.1.1.14 excluded
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 3.7.3.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuq82951 | Title: | Acct-ma encode should handle interim-interval when sent alone via COA |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:interim interval value without method-list in CoA, BNG accepted COA but expected NACK.
Conditions:
If interim interval value is sent alone without the method-list in CoA, In this scenario BNG does not handle it and coa returns ack & interim accounting triggered.
Workaround:interim interval value with the method-list in CoA request.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | 5.2.3.12i.BASE, 5.2.4.1i.BASE, 5.3.0, 5.3.0.9i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy50053 | Title: | wdsysmon crashing regularly 5.1.3 SP5 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
wdsysmon crashing on 5.1.3 SP5
Conditions:
5.1.3
Polling on (1.3.6.1.2.1)
Workaround:
snmp-server view xxxxx 1.3.6.1.2.1 excluded
Or more specific
snmp-server view xxxxx 1.3.6.1.2.1.31 excluded
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy51950 | Title: | NP_SPIN Loop with VPLS LSM + Netflow on Add / Remove BGP Config |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
NP_SPIN Loop with VPLS LSM + Netflow on Add / Remove BGP Config
Conditions:
VPLS LSM + Netflow with Add / Remove BGP Config
Workaround:
Steady state - No Lookup is seen .. Seen only with Add / Remove BGP with VPLS LSM + Netflow.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy51088 | Title: | ipv6_rib process crash in rib_server_add_path_to_nh_db - SegV |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
An asr9k may suffer from an ipv6_rib process crash
Conditions:
None
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq66583 | Title: | asr9k/4.3.1/netio_process_crashed |
|
Status: * | Other |
|
Severity: * | 3 Moderate |
Description: | Symptom:
NETIO Process crash once
Conditions:
One time
Workaround:
Occured only once, customer looking for workaround,
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE, 5.1.0.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy51621 | Title: | VRF enable ServiceInfra interface support on VSM |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
ServiceInfra interface configured under vrf cause HA packets drop at NP resulting HA failure
Conditions:
ServiceInfra interface enable under VRF.
Workaround:
Configure ServiceInfra interface in global/default vrf
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf60547 | Title: * | MPLS v6 or v4 paks with invalid len cause netio crash when require frag |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Netio process crash on ASR9000 linecards
Conditions:
This problem is triggered by the reception of EoMPLS packets containing packets whose destination MAC starts with 6.
When these packets require fragmentation due to mtu exceeding, netio trips. This is caused by the fact that these packets
are not true ipv6, but code is mislead by the leading 6 of the dmac.
The scenario is for instance BVI with VPLS and receiving a packet on the PW to be routed by the BVI.
Workaround:
Control word
Adjusting mtu so that frag is not needed
Change mac address not to start with a 6.
Further Problem Description:
this problem can occur for both v4 and v6.
the hw classifies the packet that requires fragmentation as v4 or v6 depending on what the dmac starts with (in a pw-ether scenario for instance) and handles it over to the sw stack from SPP to NETIO.
when netio is handling the frag requirement it trips on certain fields, eg ip header length, that are incorrect or non significant.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: | 4.3.2, 4.3.2.15i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.1, 5.1.1.10i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18966 | Title: | 9000v led of ICL port stayed green after all cables are plugged out |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: * | Symptom:
led of ICL port stayed green even after all cables are plugged out
Conditions:
Condition is order of removal of cable.
1. remove TX (from 9000v2) cable
2. remove RX cable
Workaround:
To avoid the issue, plugged out both cable at same time or remove RX cable first.
To resolve the issue, do OIR of SFP+
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 6.0(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw18466 | Title: | BGP umbrella SMU for 5.3.2 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
BGP umbrella SMU for 5.3.2
DDTS list:
CSCuv07420:BGP sends withdraw label (524288) due to incorrect RT filter handling
CSCuv68427:6VPE traffic drop due to missing vpnv6 nexthops in RIB opaque database
Conditions:
BGP umbrella SMU for 5.3.2
Workaround:
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: * | 5.3.2.SP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40715 | Title: | 20x1G EP port 0 flapped after shut/noshut the EP |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Interface may flap when MPA comes up online.
Conditions:
This is a timing and intermittent issue and there is no explicit condition.
Workaround:
No workaround.
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: * | 6.1.1.3i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh36018 | Title: | %L2-STP_IO-4-ERROR_DISABLING_PORT when receivng per-vlan BPDU with MSTAG |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Error message like the ones below:
LC/0/1/CPU0:May 24 17:59:09.931 : stp_io[334]: %PKT_INFRA-ERRDIS-6-ERROR_DISABLE : GigabitEthernet0/1/0/3.1: Error disabling due to reason: stp-legacy-bpdu
LC/0/1/CPU0:May 24 17:59:09.932 : stp_io[334]: %L2-STP_IO-4-ERROR_DISABLING_PORT : Error while disabling port GigabitEthernet0/1/0/3.1. Reason for disabling is 'Legacy BPDU received': 'interface attributes library' detected the 'warning' condition 'Failed to receive a response for item'.
Conditions:
This is an error message when processing a PVST+ or PVRST BPDU on an untagged subinterface where MSTAG is configured.
This is an error configuration as XR cannot be at the border between a per-vlan STP domain and MSTAG configured on XR.
The code is trying to error disable the untagged subinterface where MSTAG is configured but it fails because subinterfaces cannot be disabled.
This is an enhancement to have a clearer error message.
Workaround:
Fix the misconfiguration by configuring MST on the CE device which is sending per-vlan BPDUs to an ASR9000 configured for MSTAG.
|
|
Last Modified: | 16-FEB-2016 |
|
Known Affected Releases: | 4.2.3.CE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.4i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy35477 | Title: | parser debug appears during boot needs to be removed, |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
International functional calls and debug messages are printed during ASR 9000 bootup.
Conditions:
Node / device boot up
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv53090 | Title: | Umbrella DDTS to address BGP process health issues |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
BGP process issues
Conditions:
CSCus44940 BGP process crash during vrf migration
CSCus62099 After RPFO failure BGP stuck in bgp init sync state.
CSCuu13363 BGP crash when label thread processing rpf change list
CSCuu45529 ASR9k: BGP Notification of Admin shutdown triggers Graceful-Restart
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.1.SP2, 5.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux88095 | Title: | commit fails when macsec-service config is overwritten when intf scale |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Commit failure
Conditions:
No functionality issue
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01983 | Title: | 5.3.1 Umbrella SMU for sysdb |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Conditions:
Workaround:
Further Problem Description:
This is an Umbrella DDTS for sysdb related fixes.
[r60x] MCSAT sysdb_svr_local crashed at sms_respq_handle_resp_msg
Big verification messages crash sysdb_shared_sc
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.3.BASE |
|
Known Fixed Releases: * | 3.8.3, 3.8.4, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 5.3.1.SP2 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuh34079 | Title: | ASR9K V2 FT - False positive mismatch alarm |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: | Symptom:
Log message:
%PLATFORM-ENVMON-4-FANTRAY_VER_MISMATCH_CLEAR : Fan tray version mismatch
Conditions:
After OIR of a fan tray in ASR9010 with 2 V1 fan trays:
NAME: "fantray 0/FT0/SP", DESCR: "ASR-9010 Fan Tray"
PID: ASR-9010-FAN, VID: V02, SN: FOX1521XE37
Workaround:
N/A
Further Problem Description:
An example of V2 fan tray:
NAME: "fantray 0/FT0/SP", DESCR: "ASR-9010 Fan Tray Version 2"
PID: ASR-9010-FAN-V2, VID: V00, SN: FOC1638N2Q1
This is a cosmetic bug that can be ignored.
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq58043 | Title: | IGMP timeout on BVI interface. |
|
Status: | Terminated |
|
Severity: * | 5 Cosmetic |
Description: | Symptom:
We are seeing IGMP group deletion initiated on the ASR9k after 2 mins of the initial join
Conditions:
ASR9k interface is configured as BVI interface, IGMP joins are received on BVI
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 5.1.2.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy47493 | Title: | 5.3.3 documentation need to mention default PBR QoS processing behavior |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: | Symptom:
5.3.3 Documentation does not contain the default QoS PBTS ordering behavior in the absence of explicit knob.
Conditions:
Explicit knob (service-policy apply-order pbr qos) not configured.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf86015 | Title: | BGP to install global NH for directly conn V6 peer to help ASR9K netflow |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
For ingress flow IPv6 source AS is displayed as "0" and for egress flow the Next hop is displayed as "::" for prefixes learned via directly connected ebgpv6 neighbors.
Conditions:
IPv6 source AS is displayed as "0" for the Ingress flow and the next hop is displayed as "::" for the egress flow when the prefixes are learned via a directly connected ebgpv6 neighbor.
Workaround:
Use an ingress RPL on the EBGPv6 neighbor to set the nexthop to the neighbor's Global IPv6 address (please refer Workaround-1 enclosure for more details), or have a multi-hop eBGPv6 neighborship rather than configuring eBGPv6 neighborship towards directly connected peer (Please refer Workaround-2 enclosure for more details).
Further Problem Description:
|
|
Last Modified: | 27-FEB-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 6.1.1.3i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy51976 | Title: | Documentation: ICCP-SM Mac Flush delay 15 seconds after recovery |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Need to put documentation ICCP-SM Mac Flush delay 15 seconds after recovery.
Conditions:
ICCP-SM
Workaround:
n/a
Further Problem Description:
n/a
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuq09456 | Title: | Improve LOW_LASER_BIAS_ALARM error message |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Currently low/high power alarm or warnings syslog appear with limited information which is not user friendly to read and can be polled through NMS with correct information
LC/0/3/CPU0:Jan 6 14:44:39.607 IST: pfm_node_lc[292]: %PLATFORM-SFP-2-LOW_RX_POWER_ALARM : Clear|envmon_lc[168024]|SFP(0x1029016) |Port_1/02
LC/0/3/CPU0:Jan 6 14:44:39.607 IST: pfm_node_lc[292]: %PLATFORM-SFP-3-LOW_RX_POWER_WARNING : Set|envmon_lc[168024]|SFP(0x1029016) |Port_1/02
Conditions:
Present syslog message is not easily decoded by users and also Prime NMS tool able to help user as for which interface this message belongs to.
If existing format of syslog appearance modify to below format then user can easily interpret it so does tool like Prime able to generate information about specific ports.
LC/0/3/CPU0:Jan 6 14:44:39.607 IST: pfm_node_lc[292]: %PLATFORM-SFP-2-LOW_RX_POWER_ALARM : Clear|envmon_lc[168024]|SFP(0x1029016) (Media Type) |Port_1/02 TenGigE/GigabitEthernet 0/3/1/2
LC/0/3/CPU0:Jan 6 14:44:39.607 IST: pfm_node_lc[292]: %PLATFORM-SFP-3-LOW_RX_POWER_WARNING : Set|envmon_lc[168024]|SFP(0x1029016) (Media Type) |Port_1/02 TenGigE/GigabitEthernet 0/3/1/2
as mentioned above:-
1) SFP hex value should be change to end user readable friendly information. SFP ( instead of hex value it should be Media Type)
2) Port_1/02 in above syslog should be user readable. Instead of port_1/02 it should be type of port physical interface format: [ GigabitEthernet | TenGigE | Fourty | Hundred] R/S/I/P
Workaround:
NO WA
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo93835 | Title: | MPLS-TE tunnel flaps on making "priority" config changes. |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
TE tunnel flap
Conditions:
Priority configuration change on the TE tunnel interface
Workaround:
None
Further Problem Description:
customer experienced TE tunnel flap when they changed the priority config on the tunnel interface. This is Expected behavior but does not help customer.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.3.16i.MPLS, 5.1.3.18i.MPLS, 5.2.2.19i.MPLS, 5.2.3.6i.MPLS, 5.3.0.5i.MPLS |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw28284 | Title: | Reserved RFD leak during forwarding shd trigger NPfastReset for recovery |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Ingress NP3 on 2*100GE typhoon LC was dropping packets for long time at PARSE_FAST_DISCARD_LOW_PRIORITY_DROP counters:
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_0: 2872526839
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_0: 2872526839
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_1: 2874687659
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_1: 2874687659
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_2: 2873805447
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_2: 2873805447
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_3: 2872603712
[np:NP3] PARSE_FAST_DISCARD_LOW_PRIORITY_DROP_3: 2872603712
and there was also huge increase in PARSE_UNKNOWN_DIR_3 counters on the affected NP:
Show global stats counters for NP3, revision v2
Read 61 non-zero NP counters:
Offset Counter FrameValue Rate (pps)
-------------------------------------------------------------------------------
16 MDF_TX_LC_CPU 64275880 4
21 MDF_TX_FABRIC 42156033198363 0
29 PARSE_INTER_NP_RECEIVE_CNT 113362 0
37 PARSE_INTR_RECEIVE_CNT 1726679278 517
41 PARSE_INJ_RECEIVE_CNT 54984 0
45 PARSE_ENET_RECEIVE_CNT 42156109136879 0
49 PARSE_TM_LOOP_RECEIVE_CNT 15940858 5
59 PARSE_UNKNOWN_DIR_2 24637 0
60 PARSE_UNKNOWN_DIR_3 371604897501 0
Conditions:
Reserved RFD leak into free pool just prior the drops started:
show prm server trace init location 0/4/CPU0:
prm_server/error 0/4/CPU0 t1 prm_rfd_leak_detector_core_check: Reserved RFD memory error in NP3: RFD[70] leaked into free pool
prm_server/error 0/4/CPU0 4329# t1 prm_rfd_leak_detector_core_check: Reserved RFD memory error in NP3: Reserved RFD[70] leaked into free pool
No trigger is know at the time: No config change, no unexpected message in logs, no change in traffic pattern that has been successfully transmitted for long months on the LC
Workaround:
a) reset NP (not 100% confirmed though), example:
Here is the command to do NP reset:
RP/0/RSP0/CPU0:asr9k-3#run attach 0/5/cpu0
show_np -e -d fast_reset
LC/0/5/CPU0:Dec 5 14:31:38.053 : prm_server_ty[301]: Fast Reset NP0 - successful auto-recovery of NP
Fast Reset triggered on NP0 <==== I used -e 0 to try this out on NP0.
Done
# exit
Terminating attach to node 0/5/cpu0..
RP/0/RSP0/CPU0:asr9k-3#
b) reload the LC
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: * | 6.1.1.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux42852 | Title: | cpe-domain and ext-domain Level Statistics for CGv6 map-t-cisco |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
cpe-domain and ext-domain Level Statistics for CGv6 map-t-cisco translations are not available.
Conditions:
None.
Workaround:
None.
Further Problem Description:
cpe-domain and ext-domain Level Statistics for CGv6 map-t-cisco translations are not available.
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy34668 | Title: | ASR9K PD support for QoS IPV6 ACL optimization |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
DR-LER router with ingress QOS policy to match IPv6 traffic and mark for QoS queue has a 20% forwarding performance hit versus not applying the ingress QoS policy
Conditions:
Have specific IPv6 traffic to permit and mark with ingress policy applied to an interface
Workaround:
none
Further Problem Description:
ipv6 ingress QoS policy performance hit jepardizes large deployment of DR-LER routers
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu83507 | Title: | Provide real value of POWER SUPPLY and POWER DRAW via XML |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Provide real value of POWER SUPPLY and POWER DRAW via XML - equivalent of data available in "admin show env power-supply"
Conditions:
Collecting data about POWER SUPPLY and POWER DRAW from ASR9k via netconf
Workaround:
So customer may do the math in their application and based on value of voltage and current, their tool can calculate power value but I think it's sth that we could do too to deliver more meaningful value.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.2.SP2, 5.3.3.11i.BASE, 6.0.0.17i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut30537 | Title: | Initiate switchover upon wdsysmon detecting minor/severe/critical level |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Not a bug
Conditions:
NA
Workaround:
NA
Further Problem Description:
Good to have feature which allows to configure switchover when memory state is Minor/sever/critical.
|
|
Last Modified: | 11-FEB-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.3.2.16i.BASE, 5.3.3.3i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy18292 | Title: | ICCP-SM blackhole for few seconds after PoA recovery |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: * | Symptom:
ICCP-SM blackhole for few seconds after PoA recovery
Conditions:
n/a
Workaround:
n/a
Further Problem Description:
n/a
|
|
Last Modified: | 10-FEB-2016 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy18651 | Title: | Enhance VQI shaper to support 18G for Octane and Skyhammer |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
The VQI shaper (fabric shaper limit) is also limited to 13.5 G in tomahawk and skyhammer linecards.
Conditions:
Workaround:
Further Problem Description:
This enhancement was implemented for typhoon and needs to be done for Tomahawk/skyhammer based on a customer requirement to be able to absorb traffic from 4 x 100GE uplinks feeding into 20x10GE downlinks using the 10x10GE breakouts on Tomahawk or 4x10GE breakouts on skyhammer. The currently implemented VQI shaper will impact an output buffered operation to a degree not acceptable by some customers.The request is to improve the packet path towards the egress line cards by increasing the VQI shaper so that more traffic will reach the output card.
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy52011 | Title: | SMU to backport optics support into 5.3.3 |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Currently these optics are supported in 6.0.0, this DDTS will be used to backport the SMU support to 5.3.3
CPAK-100G-ER4L
CPAK-10x10 ER (IP-Plus)
SFP-10G-ZR-S
Conditions:
Normal conditions
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux68035 | Title: | A9K-9001-120G-LIC MPA1 and SFP+ disabling messages |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
It's not possible to figure out why ports MPA1, SFP+2, and SFP+3 are disabled by default without A9K-9001-120G-LIC license. This information mentioned in the blank on the faceplate, but it's not possible to see any warning messages while connecting remotely to the router.
All ports could be activated, but SFP 2 and 3 will never be in the UP state.
The fix could be to implemented and some warning messages could appear while activating these ports, that there is no appropriate license on the chassis or to deny enabling these SFP ports.
Conditions:
Always
Workaround:
No workaround.
Further Problem Description:
Sometimes customers got confused when they tried to configure all SFP ports, but have no enough licenses.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw14643 | Title: | PWHE forwarding stops when subint is configured on the Bundle GI member |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Traffic may stop on a PWHE sub-interfaces
Conditions:
This problem would occur after configuring a sub-interface under the interface used in the generic interface list, having the same vlan configuration as of the PWHE sub-interface.
Workaround:
If sub-interfaces are needed for GI list members, then use different vlans for member sub-interfaces and PWHE subinterfaces.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 6.0.1.17i.BASE |
|
|
| |
:
没有评论:
发表评论