| |
Bug Id: | CSCuq77900 |
Title: | CSCuq86662 Node unusable after RPFO due to process dead loop |
|
Description: | Symptom:
The symptom of the issue is the node becoming unusable post RPFO
Conditions:
Issue is seen with RPFO on the node with normal traffic condition.
Workaround:
none
Further Problem Description:
none
|
|
Status: | Terminated |
|
Severity: | 1 Catastrophic |
Last Modified: | 02-MAY-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuq65627 |
Title: | [530]-WildChild LC Continuously reloading |
|
Description: | Symptom:
Wild Child LC continuously reloading.
Conditions:
In 530 Image, WC LC not coming up, continuously reloading.
Workaround:
NA
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 02-MAY-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | 5.3.0.6i.BASE |
|
|
| |
| |
Bug Id: | CSCuo75825 |
Title: | DHCPv6 entries staled after expiration |
|
Description: | Symptom:
Some RIB entries are not deleted after expiration of the related DHCPv6 proxy entry
Conditions:
ASR9k running 4.3.x release
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 5.1.3.9i.FWDG, 5.2.0.27i.FWDG, 5.2.3.1i.FWDG |
|
|
| |
| |
Bug Id: | CSCuh80664 |
Title: | EPFT COPP_SAMPLER_MAX_EXCLUDED_INTERFACES not enforced by sub-cop |
|
Description: | Symptom:
System allows configuring more than 64 interfaces to be excluded from Excessive Punt Flow Trap (EPFT) monitoring.
Conditions:
Configuring more than 64 interfaces to get excluded from Excessive Punt Flow Trap (EPFT) monitoring.
Workaround:
None
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-MAY-2015 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: | 4.3.4.4i.FWDG, 5.1.1.4i.FWDG, 5.1.11.1i.FWDG, 5.2.0.1i.FWDG |
|
|
| |
| |
Bug Id: | CSCut30517 |
Title: | 5.3.0 Bundle shut on remote (LSP Mid point) did not bring the local down |
|
Description: | Symptom:
In some cases the bundle interface may not be detected to be down at the IFMGR level even if the remote bundle interface is admin shut.
Conditions:
In some cases the bundle interface may not be detected to be down at the IFMGR level even if the remote bundle interface is admin shut.
Workaround:
none
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 04-MAY-2015 |
|
Known Affected Releases: | 5.3.0.BASE, 5.3.0.FWDG |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut74477 |
Title: | 5.2.4.11i:mpls_ldp process crash on reloading a RR(Rte reflector)router. |
|
Description: | Symptom:
mpls_ldp process crashes.
Conditions:
Route reflectore reload/ control protocol (bgp, ldp ) churn.
Workaround:
No known workaround.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | 5.2.4.14i.MPLS, 5.2.5.8i.MPLS |
|
|
| |
| |
Bug Id: | CSCur31374 |
Title: | Sub stuck in disconnecting state;Callback pending in SvcAcct-Final>Stats |
|
Description: | Symptom:
this case is seen when we apply services with different precedence, using the same class-map for traffic classification.
Some subscribers are stuck in disconnecting state. For those subscribers we do not see accounting stop sent for session.
Conditions:
this has been seen in 5.1.3
Workaround:
if services with overlapping class-map is used (turbo-services, in this case), unapply the previous service and apply new service.
Further Problem Description:
Output of the sss detail internal:
show subsc sess fil mac x.x.x det int
State: Disconnecting
Disconnect Reason: Client lease expired
Disconnect Cause: AAA_DISC_CAUSE_SESSION_DISC (1)
Abort Cause: AAA_AV_ABORT_CAUSE_TS_TIMEOUT (47)
Terminate Cause: AAA_AV_TERMINATE_CAUSE_SESSION_TIMEOUT (5)
Disconnect called by: [iEdge internal]
Authentication: unauthenticated
Authorization: authorized
Accouting stop state: Waiting for final stats for all services
Pending Callbacks: PPSM-Sub>Policy-Disc,Policy-Disc>PPSM,SvcAcct-Final>StatsD,
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.2.3.12i.BASE, 5.2.4.1i.BASE, 5.3.0.14i.BASE |
|
|
| |
| |
Bug Id: | CSCus45841 |
Title: | Wildchild : Commit Arclight FPGA image for the clock squelching fix. |
|
Description: | Symptom:
Clock squelching is not working correctly on 1GE interfaces of Wildchild LCs with following PID
A9K-40GE-SE
A9K-40GE-TR
A9K-4T16GE-SE
A9K-4T16GE-TR
Conditions:
1GE interface on Wildchild LCs (PID mentioned in Symptom) used as primary syncE input clock and Loss of Signal (LOS) detected.
Workaround:
None. However the impact on syncE functionality is very low. The TIE jump due to the issue is always less than 1us.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.2.4.11i.BASE, 5.2.5.8i.BASE |
|
|
| |
| |
Bug Id: | CSCut94655 |
Title: | 5.3.1:tftp_fs process blocked, tftp copy is failing. |
|
Description: | Symptom:
Tftp copy is failing.
Conditions:
Issue may be caused by frequent tftp copy operation, 4 files (combined data is around 3 MB) every 2mins. or when a huge running config (12MB) is copied from tftp to router.
Workaround:
Restart tftp_fs process.
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut67156 |
Title: | [524] Interim accounting update failed for few sessions |
|
Description: | Symptom:
Interim accounting update failed for few sessions
Conditions:
While sending dynamic template activate service CoA
Workaround:
NA
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | 5.2.4.15i.BASE, 5.2.5.8i.BASE |
|
|
| |
| |
Bug Id: | CSCur18004 |
Title: | Tomahawk P2MP: Mid node not replicating pkts and no pkts fwded to tail. |
|
Description: | Symptom:
Traffic loss on tail/mid nodes, as no pkts are replicated, if upstream node has triggered FRR.
Conditions:
5.2.2 onwards. all platforms affected.
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | 5.2.4.11i.BASE, 5.2.4.11i.FWDG, 5.2.5.8i.BASE, 5.2.5.8i.FWDG, 5.3.0.15i.FWDG |
|
|
| |
| |
Bug Id: | CSCut68088 |
Title: | vic receiving all 0's mac-addr from can bus-server after router reload |
|
Description: | Symptom:
10GE interfaces not initialized after router reload.
Conditions:
After router reload TenGE interfaces were not initialized on an 24x10GE LC. This is due to the failure to assign mac-address to the interfaces.
Workaround:
LC/Router reload
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | 5.2.4.14i.BASE, 5.2.5.8i.BASE |
|
|
| |
| |
Bug Id: | CSCuo88998 |
Title: | qos_ma messages shown up in logs: cap-idx = 0, ifh_st member_ifh_arr |
|
Description: | Symptom:
whenever we issue show CLI for to get qos stats following log messages ill created.
example: getmany -v2c 23.1.8.3 test cbQosClassMapStats
Any time a QoS MIB - stats is polled - following log messages are created.
LC/0/0/CPU0:Jun 25 17:42:23.737 GMT: qos_ma[310]: cap-idx = 0,
ifh_st->member_ifh_arr[cap_idx]=500e8204
LC/0/0/CPU0:Jun 25 17:42:23.737 GMT: qos_ma[310]: cap-idx = 1,
ifh_st->member_ifh_arr[cap_idx]=500ab58c
RP/0/RSP0/CPU0:Jun 25 17:42:25.626 GMT: qos_ma[1162]: cap-idx = 0,
ifh_st->member_ifh_arr[cap_idx]=501c76a0
RP/0/RSP0/CPU0:Jun 25 17:42:25.626 GMT: qos_ma[1162]: cap-idx = 1,
ifh_st->member_ifh_arr[cap_idx]=501c8644
LC/0/0/CPU0:Jun 25 17:42:25.625 GMT: qos_ma[310]: cap-idx = 0,
ifh_st->member_ifh_arr[cap_idx]=500e820c
LC/0/0/CPU0:Jun 25 17:42:25.625 GMT: qos_ma[310]: cap-idx = 1,
ifh_st->member_ifh_arr[cap_idx]=500ab51c
RP/0/RSP0/CPU0:Jun 25 17:42:52.615 GMT: qos_ma[1162]: cap-idx = 0,
ifh_st->member_ifh_arr[cap_idx]=501c76a0
RP/0/RSP0/CPU0:Jun 25 17:42:52.615 GMT: qos_ma[1162]: cap-idx = 1,
ifh_st->member_ifh_arr[cap_idx]=501c86d0
Conditions:
SNMP OID pull for QoS Stats
This is regression we have to remove syslog.
Workaround:
there is no workaround
there is a SMU for this.
SMU id: AA08673
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.1.2.MGBL, 5.1.3.MGBL |
|
Known Fixed Releases: | 5.1.2.SP2, 5.1.2.SP3, 5.1.2.SP4, 5.1.3.10i.FWDG, 5.2.2.18i.FWDG, 5.2.3.6i.FWDG, 5.3.0.5i.FWDG |
|
|
| |
| |
Bug Id: | CSCus50857 |
Title: | A9K-2x100GE link stay down due to PCS Lane Mapping invalid |
|
Description: | Symptom:
When linkdown occurs due to invalid "PCS Lane Mapping", sometimes link does not go up.
Conditions:
The issue is seen when port receives two wave length signals of upto 50 msec during optical layer switchover from active to backup path.
IOS XR 5.1.2, 5.2.2
Workaround:
triggers the path failover again
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 4.3.4.LC, 5.1.2.LC, 5.2.2.LC |
|
Known Fixed Releases: | 5.2.4.11i.BASE, 5.2.5.8i.BASE, 5.3.1.24i.BASE, 5.3.2.3i.BASE |
|
|
| |
| |
Bug Id: | CSCut89724 |
Title: | LISP control packet TTL of 32 too small |
|
Description: | Symptom:
LISP control packets dropped in the network.
Conditions:
The symptom is observed when there are more than 32 hops between
sender and receiver.
Workaround:
There is no workaround.
Further Problem Description:
LISP control packets are sent with an IP TTL of
32, meaning if there is more than 32 IP hops between the sender and receiver,
they will be dropped in the network.
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut81593 |
Title: | Auto IP SATs fail to come up after RP Failover |
|
Description: | Symptom:
Auto IP SATs fail to come up after RP Failover
Conditions:
RP Failover
Workaround:
process restart icpe_satmgr
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.29i.FWDG, 5.3.2.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCus81652 |
Title: | GOLF: few VRFs have traffic loss with 2K VRF scale from PE to BL. |
|
Description: | Symptom:
Possible L3 traffic drop under scale conditions on ASR9K when the routes are learnt over IGP and EGP paths with same metric.
Conditions:
ASR9K running IOS-XR 5.3.0
The route is learnt over EGP and IGP and has same cost.
The test case is not very clear for the issue to be seen.
It is based on a code inspection.
Workaround:
There is no workaround.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.0.FWDG, 5.3.1.FWDG, 5.3.2.FWDG |
|
Known Fixed Releases: | 5.3.1.28i.BASE, 5.3.1.28i.FWDG, 5.3.2.3i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCut65403 |
Title: | interface is down for long time after PREFEC-SD-BER alarm clears |
|
Description: | With proactive protection config, interface takes 10 mins to come up after stopping prefec error injection from testing equipment
Symptom:
Port will stay down for long time than expected
Conditions:
proactive config under controller dwdm
Workaround:
Remove proactive protection and re-apply it
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.29i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCus36878 |
Title: | Mobile Route missing after ipv4_rib/ipv6_rib proc restart |
|
Description: | Symptom:
In a Cisco Router with vrf aware LMA configured, the Mobile Routes related to PMIPv6 binding might go missing from the respective VRF RIB Table.
Conditions:
This condition is seen when ipv4 or ipv6 rib process (ipv4_rib/ipv6_rib) restarts during the operation of the router.
Workaround:
Execute "process restart pmipv6d"
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.0.BASE, 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.28i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCuo17901 |
Title: | Out of order mcast packets introduced by ASR9K MLDP+bundle |
|
Description: | Symptom:
Out-of-order multicast packets in the same multicast stream when using MLDP.
Conditions:
Following conditions are required:
- the traffic must be sent over an MLDP core
- the role of the router must be a bud or mid
- there must be an egress bundle
- two or more bundle members must reside on the same NP
- the LC must be a Typhoon
Workaround:
Possible workarounds:
- Move the egress bundle members to different NPs.
- Remove the egress bundle (use ECMP links)
- Use P2MP or Rosen MVPN instead of MLDP
- Use Trident instead of Typhoon
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.MCAST |
|
Known Fixed Releases: | 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.2.23i.BASE, 5.1.3.5i.BASE |
|
|
| |
| |
Bug Id: | CSCus94707 |
Title: | XBAR_TIMEOUT_ERROR when LC is inserted with mcast on 9922 |
|
Description: | Symptom:
Linecard insertion may result in XBAR_TIMEOUT_ERROR on a different linecard
Conditions:
The DDTS is specific for ASR9922 running multicast traffic running any release beyond 4.2.1.
The trigger is an LC insertion with it also being a multicast receiver.
The LC insertion causes multicast traffic drop for existing receivers for 10 seconds.
Workaround:
None
Further Problem Description:
Sample PFM log raised by fabric/spine driver:
===========================
RP/0/RP0/CPU0:Feb 12 04:52:23.580 KST: pfm_node_rp[356]: %PLATFORM-CROSSBAR-1-XBAR_TIMEOUT_ERROR_LNK0 : Set|fab_xbar_sp0[208977]|Crossbar Switch(0x101702c)|XBAR_1_Slot_16
RP/0/RP0/CPU0:Feb 12 04:52:23.581 KST: pfm_node_rp[356]: %PLATFORM-CROSSBAR-1-XBAR_TIMEOUT_ERROR_LNK0 : Set|fab_xbar_sp0[208977]|Crossbar Switch(0x1017012)|XBAR_0_Slot_16
Sample PFM log raised by "Ingress" LC fabric driver:
===============================
LC/0/14/CPU0:Feb 12 04:52:26.674 KST: pfm_node_lc[287]: %PLATFORM-CROSSBAR-1-XBAR_TIMEOUT_ERROR_LNK0 : Set|fab_xbar[168016]|Crossbar Switch(0x1017002)|FIA_1
LC/0/14/CPU0:Feb 12 04:52:26.674 KST: pfm_node_lc[287]: %PLATFORM-CROSSBAR-1-XBAR_TIMEOUT_ERROR_LNK1 : Set|fab_xbar[168016]|Crossbar Switch(0x1017001)|FIA_1
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP7, 5.3.1.22i.BASE |
|
|
| |
| |
Bug Id: | CSCur32156 |
Title: | IPv6 ACL modification is not taking effect in HW PI-PD out of sync |
|
Description: |
Symptom:ACL may not function as expected due to mis-programming of ACL in LC.
Conditions:in-line modification of the IPv6 scale ACL (with object-groups) may fail to get programmed correctly in hardware.
Workaround:Remove the ACL from all the interfaces and reapply it.
"show access-lists ipv6 usage pfilter location " shows list of interfaces where ACL is applied.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.2.4.8i.FWDG, 5.2.5.4i.FWDG, 5.3.0.14i.FWDG |
|
|
| |
| |
Bug Id: | CSCup45536 |
Title: | CEF not updated for recur lev 2 prefix when adding static route to NULL |
|
Description: | Symptom:
When the next hop for a BGP prefix originates from BGP and a static route is added to replace the route, CEF may keep the stale entry from BGP
Example:
4.14.14.0/24, version 689, internal 0x14000001 0x0 (ptr 0x71e8a318) [1], 0x0 (0x0), 0x0 (0x0)
Updated Jun 19 07:14:43.006
Prefix Len 24, traffic index 0, precedence n/a, priority 4
gateway array (0x71450e58) reference count 2, flags 0x8020, source rib (6), 0 backups
[1 type 3 flags 0x80151 (0x71545df4) ext 0x0 (0x0)]
LW-LDI[type=0, refc=0, ptr=0x0, sh-ldi=0x0]
Level 1 - Load distribution: 0
[0] via 129.250.0.254, recursive
via 129.250.0.254, 2 dependencies, recursive [flags 0x6000]
path-idx 0 NHID 0x0 [0x71e8a240 0x0]
next hop 129.250.0.254 via 129.250.0.254/32
Load distribution: _ (refcount 1)
Hash OK Interface Address
- Y TenGigE0/1/0/13 remote
RP/0/RSP0/CPU0:ASR9010-C#sh ip rou 129.250.0.254
Thu Jun 19 07:19:40.184 UTC
Routing entry for 129.250.0.254/32
Known via "static", distance 1, metric 0 (connected)
Installed Jun 19 07:16:57.862 for 00:02:42
Routing Descriptor Blocks
directly connected, via Null0
Route metric is 0
No advertising protos.
Conditions:
Workaround:
clear route ipv4 unicast
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.3.ROUT, 5.2.0.ROUT |
|
Known Fixed Releases: | 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.3.14i.FWDG, 5.2.2.17i.FWDG, 5.2.3.6i.FWDG, 5.3.0.1i.FWDG |
|
|
| |
| |
Bug Id: | CSCun75418 |
Title: | DWDM Umbrella SMU for 4.3.4 |
|
Description: | Symptom:This DDTS is and umbrella SMU for the following bugs CSCun26272, CSCul66327, CSCun27023 and CSCud93983
Conditions:normal
Workaround:none
More Info:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.2.0.99i.BASE |
|
|
| |
| |
Bug Id: | CSCul66806 |
Title: | NP4c fast reset ; TM lockup, search lockup , RFD problems |
|
Description: | Symptom:
NP packet buffer leak happens when there is a large burst of MACs learning along with high rate traffic. Customer traffic drop can happen due to buffer leakage. As the leakage getting worse, packet forwarding on the NP can be so slow that internal heartbeat message cannot be handled in a given period of time. Thus NP is declared in lockup state.
Conditions:
High of egress learning along with high rate of NP processing occurring,
related to high rate of ingress/egress traffic into the NP.
Workaround:
None.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: | 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.1.18i.BASE, 5.1.11.13i.BASE, 5.1.2.10i.BASE |
|
|
| |
| |
Bug Id: | CSCup69488 |
Title: | Umbrella DDTS for 9001 MPA Issues |
|
Description: | Symptom:
Check release notes for CSCuo90534 and CSCuo74055
Conditions:
Using a 9001 or 9001-S, the MOD80 and MOD160 are NOT affected
CSCuo90534 is in all releases of 9001 code
CSCuo74055 is only in 4.3.1 and above
Workaround:
Reload the router.
Further Problem Description:
Check release notes for CSCuo90534 and CSCuo74055
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7 |
|
|
| |
| |
Bug Id: | CSCuo22306 |
Title: | Umbrella DDTS for NP lockup fixes |
|
Description: | Symptom:
This is an umbrella DDTS for delivering following fixes through a single production SMU:
CSCun71928 NP lockup causes ASR9000 Ethernet Line Card restart
CSCun98617 Drop IPv6 packets with inconsistent payload length
CSCun92333 PRM SMU activation on ASR9000 Ethernet Line Cards causing reload
CSCuo00061 NP lockup on ASR9000 Ethernet Line Card
CSCun71685 False NP parity errors reported on ASR9000 Ethernet Line Cards
Conditions:
Workaround:
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.LC, 5.1.1.LC |
|
Known Fixed Releases: | 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.1.SP2, 5.1.1.SP3, 5.1.1.SP4, 5.1.1.SP5, 5.1.1.SP6 |
|
|
| |
| |
Bug Id: | CSCut63675 |
Title: | lda_server coredump caused by wdsysmon |
|
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:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.LC |
|
Known Fixed Releases: | 5.3.1.28i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCut81453 |
Title: | SAT Discovery FLAP on RPFO lead to int flap, high CPU, crosslink issue |
|
Description: | Symptom:
SAT Discovery FLAP on RPFO lead to int flap, high CPU, crosslink issue
Conditions:
RP Failover
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.29i.FWDG, 5.3.2.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCur33931 |
Title: | Missing ECD marking flag for the rec-leaf in the recursive PW fwd chain |
|
Description: | Symptom:Multicast traffic not passing through bridge-domain but unicast works fine after a BGP PIC cutover. Or shut one of the ECMP path.
Conditions:Traffic can be drop. From log analysis, it shows that the interface information does not get updated in the L3 to L2 notification data.
Workaround:Clearing routes restore the impacted traffic. It has been verified in the customer routers. ( in addition need to also use the fix in PI bug CSCur14272 for complete fix)
More Info:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.2.3.ROUT |
|
Known Fixed Releases: | 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.3.0.12i.FWDG |
|
|
| |
| |
Bug Id: | CSCuo56858 |
Title: | Multicast IRB TM drops when traffic rate above 50% of line rate |
|
Description: | Symptom:
Multicast IRB traffic is dropped by the TM on ingress.
The input drops matching NP TM drops and can be verified using "show controllers np tm counters npX location ...."
Conditions:
IRB traffic must have L2 and L3 receivers
IRB traffic rate * 2 + regular traffic rate must exceed interface line rate.
- example: 60% line rate IRB traffic * 2 = 120% (bad)
- example: 40% line rate IRB traffic *2 + 40% unicast traffic = 120% (bad)
- example: 10% line rate IRB traffic * 2 + 50% unicast traffic = 70% (okay)
Workaround:
- lower traffic rate
- move traffic to different NPs
- move ingress NP to trident
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.MCAST |
|
Known Fixed Releases: | 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.3.6i.BASE |
|
|
| |
| |
Bug Id: | CSCus36817 |
Title: | CEF OOR on Trident LC with more than 4 iBGP multi-paths for VPN routes . |
|
Description: | Symptom:
The following message is seen on the ASR9K logs
LC/0/0/CPU0:Nov 6 09:07:09.591 : fib_mgr[172]: %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.
show cef platform oor location shows the "PRM CREDITS" for the following resource keep incrementing
(a) LEAF (b) TX_ADJ and (c) NR_LDI
without significant increase in IPv4_LEAF_P or IPv6_LEAF_P
Conditions:
VPN routes are learnt via iBGP over more than 4 paths and the number of those paths keep changing.
The PID for the line card is one of the following:
A9K.*-L or A9K.*-B or A9K.*-LE
The ASR9K router is running one of the following IOS-XR releases
4.2.x
4.3.x
5.1.x
5.2.x
and
5.3.0
Workaround:
Reload LC periodically (based on the "show cef platform oor location " output)
or
Limit the number of iBGP multipath to 4 if possible.
Further Problem Description:
This issue is only applicable to the LC with PID
A9K.*-L or A9K.*-B or A9K.*-LE
iBGP is configured with multi-path
The vpnv4 prefixes paths over which they are learnt keep on changing
(for example between 4 and 5 paths and vice-versa).
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.2.0.FWDG, 4.2.1.FWDG, 4.2.3.FWDG, 4.3.0.FWDG, 4.3.1.FWDG, 4.3.2.FWDG, 4.3.4.FWDG, 5.1.0.FWDG, 5.1.1.FWDG, 5.1.2.FWDG |
|
Known Fixed Releases: | 4.3.4.SP6, 4.3.4.SP7, 5.2.4.5i.BASE, 5.2.4.5i.FWDG, 5.3.1.15i.BASE |
|
|
| |
| |
Bug Id: | CSCut40515 |
Title: | 5.3.1.22i:ifmgr[246]: %PKT_INFRA-IFMGR-6-IMPLICIT_DOWNLOAD_IN_PROGRESS |
|
Description: | Symptom:
Configuration commit is stuck , does not get completed.
Conditions:
Issue might be seen only with scale config with large no. of interfaces.
Workaround:
No known work around other than reload of the router.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.28i.FWDG, 5.3.2.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCut65919 |
Title: | PBTS-LER: Default tunnel ipv6 pkts wrongly fwded on fwd-class tunnels. |
|
Description: | Symptom:
default tunnel pkts load balanced on fowarding class tunnels
Conditions:
No default class.
Workaround:
NOne
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | 5.3.2.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCut57864 |
Title: | QoS MIB skips processing remaining items in batch after encount error |
|
Description: | The SNMP index of the egress policies we have configured is missing on several Bundle-Ether Interfaces.For BE11 and BE12, there is no information about outbound qos queue bit/s. For BE16, it works fine.The SNMP index of the egress policies we have configured is missing on several Bundle-Ether Interfaces.For BE11 and BE12, there is no information about outbound qos queue bit/s. For BE16, it works fine.For BE11(ifindex 1206), we can see that we only have ingress policy index.RP/0/RP0/CPU0:bx03.iad23#show snmp interface bundle-ether 11 ifindex Mon Mar 16 14:22:06.426 PDTifName : Bundle-Ether11 ifIndex : 1206ifName : Bundle-Ether12 ifIndex : 1207ifName : Bundle-Ether16 ifIndex : 1331qideng@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1197.1 = Gauge32: 1446755488iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712>>>>>>>>>>BE11iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793>>>BE12iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965>>BE16 ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290>>BE16 egressSince Bundle-ethe 11, bundle-eth 12 on lc 0/4/cpu0 , so workaround can try restart this process only on lc 0/4/cpu0 #process restart mibd_interface location 0/4/cpu0after workaround:=======The proposed workaround appears to have worked, I see both MIBs for the interfaces in question. nwinemiller@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712---BE11-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.2 = Gauge32: 1266264741---BE11--egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793---BE12-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.2 = Gauge32: 544924422---BE12-egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965---BE16 ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290--BE16 egress
Symptom:
Missing Qos MIB entries. The configuration (show running-config ) and QoS MIB Polled result are not in sync.
Conditions:
Workaround:
=======The proposed workaround appears to have worked, I see both MIBs for the interfaces in question. nwinemiller@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net 1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712---BE11-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.2 = Gauge32: 1266264741---BE11--egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793---BE12-ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.2 = Gauge32: 544924422---BE12-egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965---BE16 ingressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290--BE16 egress
Symptom:Missing Qos MIB entries. The configuration (show running-config ) and QoS MIB Polled result are not in sync.
Conditions:
Workaround:Restart mibd_interface process on the RP. On restart the entire config will be replayed.
#process restart mibd_interface
after workaround:
=======
The proposed workaround appears to have worked, I see both MIBs for the
interfaces in question. nwinemiller@nbh1-new:~$ snmpwalk -c public -v 2c bx03.iad23.net
1.3.6.1.4.1.9.9.166.1.2.1.1iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.1 = Gauge32: 2078029712---BE11-ingress
iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1206.2 = Gauge32: 1266264741---BE11--egressiso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.1 = Gauge32: 188101793---BE12-ingress
iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1207.2 = Gauge32: 544924422---BE12-egress
iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.1 = Gauge32: 677941965---BE16 ingress
iso.3.6.1.4.1.9.9.166.1.2.1.1.1.1331.2 = Gauge32: 1827653290--BE16 egress
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.11.MGBL |
|
Known Fixed Releases: | 5.3.1.28i.FWDG, 5.3.2.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCus26923 |
Title: | traffic from SIP700 to 9000v is dropped when a link to 9000v flaps |
|
Description: | Symptom:
Traffic is not forwarded from core facing SIP card if HSRP flaps from Active to Standby and back to Active.
Conditions:
All below conditions must be met to hit the problem
Core facing card is SIP700
HSRP is configured on the ASR9k with the SIP
9000v satellite connected to the ASR9k
Bundle-ethernet is used to connect 9000v to ASR9k
Workaround:
shut/no shut bundle-member links towards the satellite. The shutting can be done on any of the Ten Gig interfaces bundled to the satellite.
or configure
bundle load-balancing localize threshold links
or
move from bundle to physical interfaces configuration between the 9000v and asr9k
or
Remove the link from l2vpn config and readd it again
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: | 4.3.4.SP7, 5.1.3.SP3, 5.2.4.5i.BASE, 5.3.0.BASE |
|
|
| |
| |
Bug Id: | CSCus59296 |
Title: | Trident Line Card High CPU due to two processes prm_server_tr and horse |
|
Description: | Symptom:
CPU utilization for one minute: 47%; five minutes: 47%; fifteen minutes: 47%
PID 1Min 5Min 15Min Process
49195 23% 23% 23% horse
155719 3% 3% 3% fialc
155731 21% 21% 21% prm_server_tr
Conditions:
show controllers np interrupts all all location 0/3/CPU0 (snipped)
Sat Jan 3 16:39:03.858 GMT
Node: 0/3/CPU0:
----------------------------------------------------------------
Ch Interrupt Name Id Cnt Brst
-- -------------------------------------------------- ---- ------- ------
1 XAUI_B_MAC 29 -1510663930 0
Workaround:
Configure the interface in "loopback internal". This will prevent the interrupt from flapping.
Also inserting optics in unused ports will prevent the problem.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE, 4.3.4.LC |
|
Known Fixed Releases: | 4.3.4.SP7, 5.2.4.4i.BASE, 5.3.1.17i.BASE |
|
|
| |
| |
Bug Id: | CSCuq13793 |
Title: | show inventory, show diag does not present output |
|
Description: | Symptom:
Concern:
show inventory, show diag does not present output
No response from 'invmgr' as per below messages
Evidence:
RP/0/RSP0/CPU0:nr11.b001049-0.iah01#show inventory
Thu Jun 12 22:20:29.480 UTC
RP/0/RSP0/CPU0:Jun 12 22:22:09.631 : sysdb_shared_nc[414]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'oper/inventory/gl/rack/0/entity/' from 'show_inventory' (jid 65776, node 0/RSP0/CPU0). No response from 'lrd' (jid 316, node 0/RSP0/CPU0) within the timeout period (100 seconds)
RP/0/RSP0/CPU0:Jun 12 22:22:09.632 : [417]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'admin/oper/inventory/rack/0/entity/' from 'lrd' (jid 316, node 0/RSP0/CPU0). No response from 'invmgr' (jid 257, node 0/RSP0/CPU0) within the timeout period (100 seconds)
RP/0/RSP0/CPU0:nr11.b001049-0.iah01#show processes block location all
Thu Jun 12 22:04:53.331 UTC
node: node0_RSP0_CPU0
------------------------------------------------------------------
65870 407023950 1 show_inventory Reply 0:00:42:0938 192605 sysdb_mc
Conditions:
unknown
Workaround:
restart invmgr process
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | 4.3.4.SP7, 5.2.4.10i.BASE, 5.2.5.4i.BASE, 5.3.1.17i.BASE |
|
|
| |
| |
Bug Id: | CSCug75299 |
Title: | PPS input to NPU should be managed as needed by chip errata |
|
Description: | Without this ddts fix NPU clock is free running and has PDV of 16 microsecond. 16Microsecond PDV is not acceptable for any mobile deployments. The ddts enables Accuracy mode on NP4. With Accuracy mode enabled PDV is around 20ns. This ddts is must for any PTP deployment.
Symptom:
PTP clock is outside the range by many folds. This impacts application which source the clock from the 9k.
Conditions:
Workaround:
None.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.0.0.1i.BASE, 4.2.0.BASE, 4.2.2.BASE, 4.3.0.BASE, 4.3.1.BASE, 4.3.2.BASE, 5.1.0.BASE |
|
Known Fixed Releases: | 4.3.4.SP1, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.2.15i.BASE, 5.2.0.9i.BASE |
|
|
| |
| |
Bug Id: | CSCui28202 |
Title: | pvrst don't converge after sh/noshut of bundle w/trident typhoon members |
|
Description: | Symptom:
L2 protocol frames are dropped if STP state is blocked if injected from a bundle interface on RSP3.
Conditions:
Bundle interface on RSP3.
Workaround:
None.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: | 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.0.18i.BASE |
|
|
| |
| |
Bug Id: | CSCui15435 |
Title: | Recovery mechanism needed for FPGA soft errors on Trident Linecards |
|
Description: | Symptom:When the FPGA memory is corrupted by a soft error it will cause inconsistent behavior or deviation from the intended functionality. In these cases the FPGA will remain in the failed state unless a reload of the configuration memory (image) is done or the line card is reloaded. This option needs to be implemented to recover from such scenarios, which can occur in the field without requiring a customer initiated reload of the affected linecard.
Soft errors are nonpermanent errors that cause the state machine to be out of sync. These are seen as Cyclic Redundancy Check (CRC), Frame Check Sequence (FCS), or errored packets on the fabric side of the NP or on the ingress side of the FIA. This issue is currently under investigation with Cisco bug ID CSCui15435.
Conditions:Here are some examples of how this issue can be seen:
RP/0/RSP0/CPU0:asr9k-1#show controllers fabric fia drops ingress location 0/3/CPU0
********** FIA-0 **********
Category: in_drop-0
DDR Rx FIFO-0 0
DDR Rx FIFO-1 32609856 <=== Errors
RP/0/RSP0/CPU0:asr9k-1#show controllers fabric fia errors ingress location 0/3/CPU0
********** FIA-0 **********
Category: in_error-0
DDR Rx CRC-0 0
DDR Rx CRC-1 32616455 <=== Errors
RP/0/RSP1/CPU0:asr9k-1#show controllers fabric fia bridge stats location 0/0/CPU0
Ingress Drop Stats (MC & UC combined)
**************************************
PriorityPacket Error Threshold
Direction Drops Drops
--------------------------------------------------
LP NP-3 to Fabric 0 0
HP NP-3 to Fabric 1750 0
RP/0/RSP1/CPU0:asr9k-1#show controllers fabric fia bridge stats location 0/6/CPU0
********** FIA-0 **********
Category: bridge_in-0
UcH Fr Np-0 16867506
UcH Fr Np-1 115685
UcH Fr Np-2 104891
UcH Fr Np-3 105103
UcL Fr Np-0 1482833391
UcL Fr Np-1 31852547525
UcL Fr Np-2 3038838776
UcL Fr Np-3 30863851758
McH Fr Np-0 194999
McH Fr Np-1 793098
McH Fr Np-2 345046
McH Fr Np-3 453957
McL Fr Np-0 27567869
McL Fr Np-1 12613863
McL Fr Np-2 663139
McL Fr Np-3 21276923
Hp ErrFrNp-0 0
Hp ErrFrNp-1 0
Hp ErrFrNp-2 0
Hp ErrFrNp-3 0
Lp ErrFrNp-0 0
Lp ErrFrNp-1 0
Lp ErrFrNp-2 0
Lp ErrFrNp-3 0
Hp ThrFrNp-0 0
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.3.BASE |
|
Known Fixed Releases: | 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.1.SP4, 5.1.1.SP5 |
|
|
| |
| |
Bug Id: | CSCus65715 |
Title: | BGP to assign unique nexthop for backup path to avoid RIB crash |
|
Description: | Symptom:
Continuous ipv4-rib process crash followed by RSP reload.
Conditions:
In BGP: If nexthop of backup-path is same as nexthop of one of multipaths, rib crash is seen.
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP7, 5.2.4.6i.ROUT, 5.3.1.24i.ROUT, 5.3.2.3i.ROUT |
|
|
| |
| |
Bug Id: | CSCuu00831 |
Title: | sysdb_mc crash |
|
Description: | Symptom:
sysdb crash
Conditions:
after upgrade 5.1.3
Workaround:
n/a
Further Problem Description:
sysdb crash without the trigger. The trigger could be caused by the way the config is update. It is by commit replace everytime the config is updated.
|
|
Status: | Other |
|
Severity: | 1 Catastrophic |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.3.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut02990 |
Title: | VPLS-LSM P2MP traffic forwrded on both links of MRIB Bundle OIF |
|
Description: | Symptom:
On nV cluster running XR5.3.0, P2MP traffic is forwarded from the both
rack member ports , when the incoming bundle member port of a rack is in
down state (and the other incoming bundle member port is up on a peer rack)
and the rack of incoming traffic differs from the rack of the outgoing port
specified by LMRIB. This occurs when PE (nV Cludter) is acting as a bud
node of VPLS-LSM and causes VPLS-LSM traffic duplication on downstream nodes.
On standalone ASR9K (running 5.3.0) of VPLS-LSM Bud role, unnecessary flooding
occurs on an outgoing bundle interface (for some set of VPLS-LSM p2mp traffic)
when VPLS-LSM P2MP entry (as bud node) has multiple (bundle-ethernet) OIFs
which have frr ready state and bunde-ethernet member ports belong to
different NPs. VPLS-LSM P2MP traffic duplication occurs on downstream PEs
of the affected bundle-ethernet.
Conditions:
VPLS-LSM bud node has Label MRIB entry with bundle-ethernet OIF which has frr ready state,
and bundle member ports belong to different NPs.
This problem is seen with ASR9K running 5.3.0, not seen with 5.2.2.
Workaround:
remove fast-reroute configuration from VPLS-LSM p2mp configuration
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.0.MCAST, 5.3.1.MCAST |
|
Known Fixed Releases: | 5.3.1.28i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCuq98778 |
Title: | ASR9001 Bay 0 disabled after SMU install |
|
Description: | Symptom:
In 9001 or Typhoon based Line card, MPA in bay# 0 may go to power down state
when CSCup14308 SMU is activated with 4.3.4 image.
No other release is affected.
Conditions:
CSCup14308 SMU is activated with 4.3.4 image.
Workaround:
Please try the following work-around and it may fix the issue. Also, pls don't install CSCup14308 SMU if
DWDM-SFP10G-C Optics is not used. If the issue is not fixed with work-around, CSCuq98778 SMU is needed.
conf t
hw-module subslot 0/0/0 shutdown unpowered
commit
no hw-module subslot 0/0/0 shutdown unpowered
commit
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.ADMIN, 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.2.3.99i.BASE |
|
|
| |
| |
Bug Id: | CSCut75650 |
Title: | BFD on Bundle Interfaces FLAP on RP Failover |
|
Description: | Symptom:
BFD on Bundle Interfaces FLAP on RP Failover
Conditions:
RP Failover
Workaround:
Not Needed
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.28i.FWDG, 5.3.2.4i.FWDG, 5.3.2.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCui67212 |
Title: | ASR9K does not generate ICMPv6 packet too big messages |
|
Description: | Symptom:
ASR9K not generate "ICMPv6 packet too big messages" when packets arrive for a destination reachable through a subscriber pppoe interface (provided that packet size > pppoe interface ipv6 mtu = 1492)
Conditions:
This behavior is specific to PPP subscriber interfaces.
Workaround:
Try to use static interface
Example:
interface Bundle-Ether12000.321
ipv6 address
encapsulation dot1q 321
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: | 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.3.9i.FWDG, 5.2.0.13i.FWDG |
|
|
| |
| |
Bug Id: | CSCun76643 |
Title: | mac entries on juggernaut LC aged out before age timer expires |
|
Description: | Symptom:
MAC addresses learned on 2x100GE line card were aged out prematurely. In stead of the 300 seconds of the default timeout value, the MAC entries on these 100GE ports are being removed within 60 seconds, causing the known unicast traffic to flood the bridge domain.
Conditions:
MAC addresses were learned on 2x100GE line cards.
Workaround:
Use other type of typhoon line cards.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE, 5.1.1.BASE, 5.1.11.BASE, 5.1.2.BASE, 5.2.0.BASE, 5.3.0.BASE |
|
Known Fixed Releases: | 4.3.4.SP7, 5.1.2.20i.BASE, 5.1.3.1i.BASE, 5.2.0.18i.BASE |
|
|
| |
| |
Bug Id: | CSCun09478 |
Title: | ASR9K: sometimes egress extended uidb lookup fails |
|
Description: | Symptom:
Egress filtering doesn't work for few frames in the egress stream.
Conditions:
Egress traffic on L2 VPWS.
Workaround:
None.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 4.3.4.SP3, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.2.20i.BASE, 5.1.3.1i.BASE, 5.2.0.22i.BASE |
|
|
| |
| |
Bug Id: | CSCur88023 |
Title: | TXFP - Adaptive FEC control algorithm not working |
|
Description: | Symptom:
MOD cards have a high preFEC error rate and the FEC control threshold is reporting the default 50%.
Conditions:
Workaround:
Assuming Line card# 1, we need to restart the VIC process.
Bay# 0
process restart vic_0 location 0/1/cpu0
Bay# 1
process restart vic_1 location 0/1/cpu0
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE, 5.3.0.BASE |
|
Known Fixed Releases: | 4.3.4.SP6, 4.3.4.SP7, 5.2.3.99i.BASE, 5.2.4.11i.BASE, 5.2.5.8i.BASE, 5.3.0.18i.BASE |
|
|
| |
| |
Bug Id: | CSCut61638 |
Title: | CRC issue - fabric fatal fault, interface in shutdown state |
|
Description: | Symptom:
CRC issue - fabric fatal fault, interface in shutdown state
Conditions:
asr9k router running 531 interim image
Workaround:
none
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.28i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCut51307 |
Title: | NSR RPSO causes traffic drop due to BGP flaps |
|
Description: | Symptom:
Traffic drop due to BGP flaps while standby RP is booting up (previous active).
Conditions:
- NSR is configured.
- RPSO because of CLI "redundancy switchover" or "process crash xx" due to "nsr process-failures switchover"
Workaround:
None.
Further Problem Description:
NSR is configured. When RPSO happens (either manually with "redundancy switchover" or "process crash xx" due to "nsr process-failures switchover"), while the current standby RP is booting up (previous active), BGP flaps which causes traffic drop which is not expected with NSR configured.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.29i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCur16251 |
Title: | Umbrella SMU for PRM issues |
|
Description: | Symptom:
Umbrella SMU for PRM issues that can lead to TCAM issues or traffic issues.
Includes CSCup73846 and CSCuq90878.
Conditions:
Workaround:
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.LC |
|
Known Fixed Releases: | 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.2.3.99i.BASE |
|
|
| |
| |
Bug Id: | CSCum70202 |
Title: | Linecard should be rebooted after non-recoverable NP errors |
|
Description: | After hitting a double ECC error :%PLATFORM-NP-2-HW_DOUBLE_ECC_ERROR : linecard is not reloading as it should.
Symptom:
The linecard is not automatically reloaded after certain types of non-recoverable NP errors.
Here is an example of a double ECC error:
%PLATFORM-NP-2-HW_DOUBLE_ECC_ERROR : Set|prm_server_tr[151636]|Network Processor Init(0x1008001)|NP DOUBLE ECC ERROR, NP=1, memId=17, subMemId=0x1
Conditions:
Workaround:
Reload the linecard. If a similar non-recoverable error is reported again on that linecard, RMA the linecard.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.2.BASE, 4.3.4.BASE, 5.1.0.BASE, 5.1.1.BASE |
|
Known Fixed Releases: | 4.3.2.SP2, 4.3.2.SP3, 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 4.3.4.SP1, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7 |
|
|
| |
| |
Bug Id: | CSCut75089 |
Title: | show inventory returns null output |
|
Description: |
Symptom:1. Inventory manager crash
2. show inventory CLI is stuck for a long duration and returns no output.
Conditions:1. "hw-module location port 0 breakout" configuration is present and CPAK is removed.
2."hw-module location port 0 breakout" configuration is removed.
Workaround:Process restart of invmgr solve the problem until it is hit again.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.28i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCum26074 |
Title: | for RPs, voltage, power & on-board temp sensors values are not available |
|
Description: | Symptom:
On IOS-XR These messages appear in the logs:
RP/0/RSP0/CPU0:Feb 16 03:47:45.287 : envmon[207]: %PLATFORM-ENVMON-2-FANTRAY_COMM_FAIL : Fan tray communication failure on slot 0/FT0/SP
RP/0/RSP0/CPU0:Feb 16 03:47:46.305 : envmon[207]: %PLATFORM-ENVMON-2-ENV_CONDITION : Outstanding environmental condition exists in the chassis
RP/0/RSP0/CPU0:Feb 16 03:47:57.287 : envmon[207]: %PLATFORM-ENVMON-2-FANTRAY_COMM_FAIL : Fan tray communication failure on slot 0/FT1/SP
RP/0/RSP0/CPU0:asr9k# show environment leds detail
Mon Feb 17 17:59:03.475 UTC
R/S/I Modules LED Status Alarm Reason
0/RSP0/*
host Critical-Alarm On FT comm. failure; < -------
host Major-Alarm Off ----
host Minor-Alarm Off ----
host ACO Off ----
host Fail Off ----
0/RSP1/*
host Critical-Alarm Off ----
host Major-Alarm Off ----
host Minor-Alarm Off ----
host ACO Off ----
host Fail Off ----
Conditions:
Running 4.3.x on any ASR9K router
Presence of any of these cards in the chassis could trigger this issue.
A9K-8T-B
A9K-8T-E
A9K-8T-L
A9K-16T/8-B
A9K-16T/8-E
A9K-16T/8-L
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.ADMIN, 4.3.4.BASE, 5.2.0.BASE |
|
Known Fixed Releases: | 4.3.4.SP1, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.1.20i.BASE, 5.1.11.16i.BASE, 5.1.2.12i.BASE, 5.2.0.11i.BASE |
|
|
| |
| |
Bug Id: | CSCut35585 |
Title: | BGP process crash on VRF unconfiguration |
|
Description: | Symptom:
The BGP process may crash on an ASR9000
Conditions:
This problem would occur when removing in one commit the VRF from the global and BGP configuration.
Workaround:
Perform the configuration removal in two steps
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.2.4.14i.ROUT, 5.2.5.8i.ROUT, 5.3.1.27i.ROUT, 5.3.1.28i.ROUT, 5.3.2.6i.ROUT |
|
|
| |
| |
Bug Id: | CSCuu10978 |
Title: | [ci-msl] All 4 Tomahawk NPs failed address bus BST testing |
|
Description: | Symptom:
All 4 Tomahawk NPs failed address bus BST testing with PRM Crash.
Conditions:
Normal Linecard boot
Workaround:
None
Further Problem Description:
Could see that all 4 Tomahawk NPs failed address bus BST testing and linecard doesnt boot normally , prm server crashes on the LC.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus06987 |
Title: | DHCP local server assign some unknown NBNS address to DHCP client |
|
Description: | Symptom:configure the command "option 44 ip X.X.X.X X.X.X.X force-insert" to ask ASR9K assign NBNS address in DHCP offer. and try to delete and re-configure this command a lot of times.
issue debug in CISCO IOS DHCP client(ASR1K):
*Nov 23 23:38:27.940: DHCP: Scan: NBNS Name Server Option: 172.16.77.100, 172.16.77.101 &208.247.45.4& &172.82.51.4& &64.82.51.4& &48.16.23.16& &73.13.0.0& &3.0.0.0&
Conditions:ASR9K is DHCP local Server and configure option 44 ip command.
Workaround:None available.
More Info:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.2.4.4i.FWDG, 5.3.1.15i.FWDG |
|
|
| |
| |
Bug Id: | CSCur39933 |
Title: | asr9k MST forwards TCN in periodic BPDU only |
|
Description: | Symptom:
When an asr9k running MST receives TCN from a downstream switch, the TCN is only forwarded when the next periodic BPDU ticks.
Conditions:
Simple L2 topology running MST spanning-tree.
Workaround:
n/a
Further Problem Description:
n/a
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 3.7.0.BASE |
|
Known Fixed Releases: | 5.2.3.12i.BASE, 5.2.3.12i.FWDG, 5.2.4.1i.BASE, 5.2.4.1i.FWDG, 5.3.0.14i.BASE |
|
|
| |
| |
Bug Id: | CSCut14295 |
Title: | 5.3.1.19J:fib_mgr process crash seen on reloading with 5.3.1.19J image |
|
Description: | Symptom:
fib_mgr process crash seen during router reload with 5.3.1.19J
Conditions:
Crash is seen only once during router reload.
Workaround:
No workaround.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.23i.FWDG, 5.3.2.3i.BASE |
|
|
| |
| |
Bug Id: | CSCut77315 |
Title: | 5.3.1.25i:System memory in critical state, most processes not running |
|
Description: | Symptom:
System memory enters into critical state, most of the processes stop running.
Conditions:
Issue is seen when tftp copy fails and dcm bulkstat keeps creating files without deleting the existing files.
Workaround:
Restart tftp_fs process which is in blocked state.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.30i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCut96949 |
Title: | mibd_interface crash observed during longevity testing |
|
Description: | Symptom:
Mibd_interface crash observed during SNMP polling
Conditions:
RSPFO followed by SNMP polling
Workaround:
None.
Process recovers after the crash
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut98919 |
Title: | 531.28I: spio and cfmd process blocked by ifmgr |
|
Description: | Symptom:
Ifmgr/cfmd processes are blocked on spio_ea process.
Control plane traffic loss is observed on the line card, which can eventually also lead to dataplane traffic loss.
CPU usage of spio_ea and SPP process goes high on the line card (15-16%)
Conditions:
More than 120 CFM HW offloaded sessions are configured on the line card.
Some client attempts to fetch CFM statistics through XML.
Workaround:
Prevent XML requests for fetching CFM statistics in this case.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.30i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCut95838 |
Title: | NP core voltage spike seen while setting AVS voltage during NP power up |
|
Description: | Symptom:
A voltage spike may be seen during the Tomahawk NP initialization sequence. This will cause the power supply to automatically reload the linecard.
Conditions:
This problem would be seen during Tomahawk linecard bootup and it's only expected to occur very rarely.
Workaround:
The linecard should be automatically reloaded in the event when this problem occurs.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.0.BASE, 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.1.30i.BASE, 5.3.2.5i.BASE, 5.3.2.6i.BASE |
|
|
| |
| |
Bug Id: | CSCum05521 |
Title: | Netio Deadlock due to Wdsysmon |
|
Description: | Symptom:
Netio gets into a deadlock condition as indicated by wdsysmon.
Conditions:
Netio indicates that it is in a deadlock and crashes.
Crashinfo and deadlock files will be generated.
Workaround:
No Workaround available
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.LC, 5.1.1.BASE |
|
Known Fixed Releases: | 4.3.4.SP7, 5.1.3.1i.BASE, 5.2.0.16i.BASE |
|
|
| |
| |
Bug Id: | CSCut66635 |
Title: | Umbrella CSCur72367 causes malloc induced crash in iedged |
|
Description: | Symptom:
After installing the umbrella SMU CSCur72367 on version 5.2.2, the process iedged will crash regularly.
Conditions:
CSCur72367 installed on version 5.2.2
Workaround:
Uninstall the SMU
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut97812 |
Title: | cfm ping is not working from ASR9k to ASR920 but working otherway |
|
Description: | Symptom:
CFM ping for a up MEP between ASR9K and ASR920 is not working.
xconnect is configured between ASr9K and ASR920 using default encapsulation
CFM is up between ASR9k and ASR920 for the xconnect.
RP/0/RSP0/CPU0:ASR9K2#sh ethernet cfm peer meps
Tue May 5 22:37:03.789 CET
Flags:
> - Ok I - Wrong interval
R - Remote Defect received V - Wrong level
L - Loop (our MAC received) T - Timed out
C - Config (our ID received) M - Missing (cross-check)
X - Cross-connect (wrong MAID) U - Unexpected (cross-check)
* - Multiple errors received S - Standby
Domain AGG (level 6), Service EPL-551
Up MEP on GigabitEthernet0/1/0/1.551 MEP-ID 302
================================================================================
St ID MAC Address Port Up/Downtime CcmRcvd SeqErr RDI Error
-- ----- -------------- ------- ----------- --------- ------ ----- -----
> 1404 84b8.0223.babf Up 00:39:14 230 0 0 0
ASR920-1#sh ethernet cfm maintenance-points remote
--------------------------------------------------------------------------------
MPID Domain Name MacAddress IfSt PtSt
Lvl Domain ID Ingress
RDI MA Name Type Id SrvcInst
EVC Name Age
Local MEP Info
--------------------------------------------------------------------------------
302 AGG 6c9c.ed0a.40eb Up Up
6 AGG Gi0/0/0:(10.194.62.1, 551)
- EPL-551 XCON N/A 551
EVC-551 7s
MPID: 1404 Domain: AGG MA: EPL-551
Total Remote MEPs: 1
CFM ping from ASR920 to ASR9K works fine.
ASR920-1#ping ethernet mpid 302 domain AGG service EPL-551 source 1404
Type escape sequence to abort.
Sending 5 Ethernet CFM loopback messages to 6c9c.ed0a.40eb, timeout is 5 seconds:!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
But CFM ping from ASR9K to ASR920 does not work
RP/0/RSP0/CPU0:ASR9K2#ping ethernet cfm domain AGG service EPL-551 mep-id 1404 source mep-id 302 interface gigabitEthernet0/1/0/1.551
Tue May 5 22:35:07.151 CET
Type escape sequence to abort.
Sending 5 CFM Loopbacks, timeout is 2 seconds -
Domain AGG (level 6), Service EPL-551
Source: MEP ID 302, interface GigabitEthernet0/1/0/1.551
Target: 84b8.0223.babf (MEP ID 1404):
Running (5s) ...
Success rate is 100.0 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Out-of-sequence: 0.0 percent (0/5)
Bad data: 0.0 percent (0/5)
Received packet rate: 1.2 pps
Conditions:
xconnect between ASR9K and ASR920 using encapsulation default
CFM up MEP configured between ASR9K and ASR920
ASR9K running 5.3.1 (eng image)
ASR920 running 3.15.0S
Workaround:
None
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 15.3(3)S3.15 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu20754 |
Title: | bgp crash at bgp_label_buffer_end when Line Card reloaded |
|
Description: | Symptom:
bgp crash and traffic drop
Conditions:
LC OIR
Workaround:
not known
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus79246 |
Title: | NP-DIAG ICFD failure due to NP's search engine lockups |
|
Description: | Symptom:
NP resets with datalog suggesting search lockup.
Conditions:
Exact condition unknown.
Workaround:
None.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 4.3.4.LC |
|
Known Fixed Releases: | 4.3.4.SP7, 5.2.4.8i.BASE, 5.2.5.4i.BASE, 5.3.1.20i.BASE |
|
|
| |
| |
Bug Id: | CSCuq74508 |
Title: | Leaf Alloc Issue: A9K-ISM-100 fib_v4pfx_upd_hdlr():290 Rc=0xcCannot |
|
Description: | Symptom:
Error messages about unable to allocate prefixes on ASR9K ISM-100 card:
A9K-ISM-100 fib_v4pfx_upd_hdlr():290 Rc=0xcCannot allocate memory
Conditions:
With close to 1M ipv4 prefixes on ISM this leaf allocation issue could be seen
Workaround:
ISM reload
Further Problem Description:
Command to check the number of ipv4 prefixes on the ISM LINUX side
[1] Attach to the ISM - Linux console
- run attachCon 115200
- root/rootroot - (username/password)
[2] show_fib_table -u
RP/0/RSP0/CPU0:CRANE#run attachCon 0/0/cpu1 115200
Mon Dec 1 20:58:51.099 UTC
attachCon: Starting console session to node 0/0/cpu1
attachCon: To quit console session type 'detach'
attachCon: WARNING - Type only 'detach' in the shell. Do not combine other keys.
Current Baud 9600
Setting Baud to 115200
localhost.localdomain login: root
Password:
Last login: Mon Dec 1 06:19:22 on ttyS0
[root@localhost ~]# show_fib_table -u
[fib_shmem_generic_allocator,141] oflag 0x2 mode 0x100
mmap successful at address 0x7000000000.
*********** node stats ******************
Table Id: 0
Root Idx: 1
Strides: 8-8-8-8 Nodes Allocated : 25
Leaves Allocated: 20
Node Alloc Fails: 0
Leaf Alloc Fails: 0
Leaf Inserts: 20
Leaf Deletes: 0
Leaf Refcount: 6395
Node Refcount: 6400
[root@localhost ~]#
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu20446 |
Title: | Single flow VQI ingress FIA tail drops for 100G subinterface |
|
Description: | Symptom:
Traffic loss observed on ASR9K with LC of type A9K-4x100GE LC when using 100G sub interfaces
Conditions:
A9K-4x100GE LC is used for Ingress and Egress
100G sub interfaces are used
ASR9K is running IOS-XR version 5.3.0
Workaround:
Only 100G interfaces can be used for > 13G traffic capacity.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 5.3.0.LC, 5.3.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCum51429 |
Title: | SW fix for power supply fan failure false alarm |
|
Description: | Symptom:
Syslog indicating power-supply failure due to either input-oring or FAN failure. These are false alarms. Following are the syslogs get generated when false alarm is hit.
ssue 1: Input Oring of A or B failure
pwr_mgmt[356]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM3/SP failure condition raised : Module input Or-ing A failure observed invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM3/SP, state: FAILED
OR
pwr_mgmt[356]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM3/SP failure condition raised : Module input Or-ing B failure observed invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM3/SP, state: FAILED
For FAN failure:
======================
pwr_mgmt[356]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM3/SP failure condition raised : Module fan failure observed invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM3/SP, state: FAILED
Conditions:
no specific trigger. Issue is due to reading incorrect values.
Workaround:
No workaround.
FAN related false alarm gets cleared within 30 seconds automatically.
Input Oring of A/B false alarm requires reseat of the power-supply. But this is very rarely seen.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 4.2.3.BASE, 5.1.1.BASE |
|
Known Fixed Releases: | 4.3.2.SP2, 4.3.2.SP3, 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 4.3.4.SP1, 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7 |
|
|
| |
| |
Bug Id: | CSCun84535 |
Title: | MPLS packets looping inside the NP during link flaps with ecmp path |
|
Description: | Symptom:Fast increment of PARSE_REDIRECT_MPLS_LoopPASS_CNT NP counter. Example:
RP/0/RSP0/CPU0:a9k#show controllers np counters all location 0/0/CPU0 | inc LoopPASS
673 PARSE_REDIRECT_MPLS_LoopPASS_CNT 2480792981007 3352505
Conditions:Observed on Ethernet Line Cards (aka Trident) of ASR 9000 series routers when an Equal Cost Multi-Path exists to a neighbor in MPLS network and one or more links on the path are flapping.
Workaround:Deploy dampening or other mechanism to eliminate the impact of link flaps on the routing tables.
More Info:Loop happens inside the NP.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 4.1.1.BASE |
|
Known Fixed Releases: | 5.2.0.18i.BASE |
|
|
| |
| |
Bug Id: | CSCuu00509 |
Title: | LOL: vlan_ea crash on applying 4K HSRP groups |
|
Description: |
Symptom:
vlan_ea crash seen while configuring/unconfiguring HSRP sessions
Conditions:
HSRP/VRRP sessions being configured on the router.
Workaround:
No workaround as such
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus91971 |
Title: | RSP keep crashing due to EOBC Tx stall |
|
Description: | Symptom:
RSP crashed
Conditions:
crashed by itself
Workaround:
No work around
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 5.3.1.25i.BASE, 5.3.2.3i.BASE |
|
|
| |
| |
Bug Id: | CSCuu05291 |
Title: | Continuous fib_mgr trace backs from VSM LC with 532-4I |
|
Description: | Symptom:
The symptom of the issue is fib_mgr trackbacks console .
Conditions:
The issue is seen upon just loading the image on the VSM line card.
Workaround:
None
Further Problem Description:
None
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus48254 |
Title: | ppp_ma crashes @ ppp_ma_iedge_af_process_event() |
|
Description: | Symptom:
PPP_MA process crashes frequently.
Conditions:
ASR9k BNG device running IOS XR 5.1.3 software
Workaround:
No known workaround at this time.
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 1 Catastrophic |
Last Modified: | 08-MAY-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus32192 |
Title: | NTP selected over PTP incase of PTP-NTP Interworking |
|
Description: | Issue was reopened by submitter after a repro has been achieved. Issue is seen only on process restart of syncctrl.
Symptom:
If PTP-NTP interworking is configured, then in a certain case, NTP (which has lower clock priority than PTP) is selected over PTP
Conditions:
The issue is seen on syncctrl process restart
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 08-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.2.7i.BASE |
|
|
| |
| |
Bug Id: | CSCut32436 |
Title: | netio crashing at vkg_cpp_fib_reformat_hash on cluster node |
|
Description: | Symptom:
netio process crash
Conditions:
This issue is seen only due to CSCut56594. If that issue is fixed, this is merely a precaution which will never be hit.
Workaround:
Need to fix CSCut56594. With that fix there is no way around.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 08-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.2.7i.BASE |
|
|
| |
| |
Bug Id: | CSCut17559 |
Title: | Invalid mac addresses generated for Mcast IP packet on 9k (Trident) |
|
Description: | Symptom:
In a Trident LC, the generated destination MAC address is calculated based on 24
bits of the Group adress rather than 23 bits as required by RFC 1122 section 6.4
An IP host group address is mapped to an Ethernet multicast address
by placing the low-order 23-bits of the IP address into the low-order
23 bits of the Ethernet multicast address 01-00-5E-00-00-00 (hex).
For example, if the group IP address is 239.129.100.141, the Mac that generated was 01:00:5e:81:64:8d
instead of 01:00:5e:01:64:8d.
The RFC doesn't require the validation of the Destination Multicast MAC address and some
Vendors may introduce different mechanisms. If validated, this bug will cause the remote
end who's receiving the packets to drop due to an invalid MAC address.
Cisco doesn't validate this in the IOS-XR platforms.
Conditions:
Trident LC as the forwarding LC and the group address 2nd MSB is greater than 127.
[224-240].[128.255].X.X
I.e 239.130.4.5
Workaround:
- use typhoon or tomahawk based LC as the core facing LC on the encap PE
- use group IP address that has the 2nd MSB < 128
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 08-MAY-2015 |
|
Known Affected Releases: | 5.1.2.MCAST |
|
Known Fixed Releases: | 5.2.4.10i.BASE, 5.2.5.4i.BASE, 5.3.1.23i.BASE, 5.3.2.3i.BASE, 5.3.2.5i.BASE |
|
|
| |
| |
Bug Id: | CSCun67616 |
Title: | process enf_broker crash non stop upon RPFO on cluster node |
|
Description: | Symptom:
The symptom of the problem is non stop crash of enf_broker
Conditions:
Issue is observed with RPFO
Workaround:
none
Further Problem Description:
none
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 09-MAY-2015 |
|
Known Affected Releases: | 5.1.2.BASE, 5.2.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCum97084 |
Title: | [520] iMDR on Typhoon card fails with node reload |
|
Description: | Symptom:
Linecard under goes a COLD reload during single LC iMDR process. And thus iMDR is failing.
Conditions:
Perform single line card iMDR with ISIS, OSPFv2 and BGP configured. Problem is not consistent, but reproducible 1 out 2 attempts in iVista Sanity.
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 09-MAY-2015 |
|
Known Affected Releases: | 5.2.0.BASE, 5.2.2.BASE |
|
Known Fixed Releases: | 5.1.3.7i.BASE, 5.2.0.15i.BASE |
|
|
| |
| |
Bug Id: | CSCut74251 |
Title: | OSPFv3 neighbors go down after ipsec authentication and never come up |
|
Description: | Symptom:Some OSPFv3 neighbors go down after enabling ipsec authentication and never come up.
Conditions:There are more than 290 OSPFv3 neighbors configured with ipsec authentication on a Trident-based line card.
Workaround:There is no workaround.
More Info:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 11-MAY-2015 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu15009 |
Title: | prm_server_to process restart fails with fast IP consistency check error |
|
Description: | Symptom:
Network processor initialization fails after the prm_server_to process is restarted:
LC/0/0/CPU0 : prm_server_to[301]: %PLATFORM-NP-0-INIT_ERR : Network processor initialization failed!!
LC/0/0/CPU0 : dumper[55]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/prm_server_to
Conditions:
This problem is very rare and is specific to Tomahawk linecards. It is a secondary problem in that it only occurs after the prm process is either manually restarted or automatically restarted due to a process crash.
Workaround:
Do not restart the prm server_to process. If the error occurs due to an automatic restart, avoid the primary problem which initiated the process restart.
Further Problem Description:
When this problem occurs, the NP driver log will contain these errors:
ERROR! 0x80001353 FinishWarmBoot_CheckSingleLineConsistency: warm-boot inconsistent result in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/srh/EZsrhFastIP.c' line 13805
ERROR! 0x80001353 EZsrhCompFastIP_CheckConsistency: EZsrhCompFastIP_CheckSingleLineConsistency failed in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/srh/EZsrhFastIP.c' line 13934
ERROR! 0x80001353 EZsrhCompFastIP_RestoreAddrHandler: EZsrhCompFastIP_CheckConsistency failed in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/srh/EZsrhFastIP.c' line 20969
ERROR! 0x80001353 EZsrhCompFastIP_RestoreAddresses: EZsrhCompFastIP_Traverse failed in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/srh/EZsrhFastIP.c' line 21045
ERROR! 0x80001353 EZsrhCompFastIP_FixAtFinishWarmboot: EZsrhCompFastIP_RestoreAddresses failed in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/srh/EZsrhFastIP.c' line 21255
ERROR! 0x80001353 EZcorDriver_FinishWarmBoot: EZsrhCompFastIP_FinishWarmboot failed in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/srh/EZsrhStruct.c' line 5648
ERROR! 0x8000110D EZcorDriver_FinishWarmBoot: EZsrhStruct_FinishWarmBoot failed. in file 'drivers/chips/np/ezchip-5c/src/host/driver/src/cor/drv/EZcorDriver.c' line 644
The NP driver log can be displayed using the "show contr np drvlog" CLI command.
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 11-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut67001 |
Title: | BNG: IP Subscriber Manager stops working |
|
Description: | Symptom:
On an ASR9k running version 5.2.2 with umbrella SMU CSCur72367 the IP Subscriber Manager (ipsub_ma) will stop functioning after several hours of operation.
Existing sessions continue to work but no new sessions can be established.
Conditions:
XR 5.2.2 with unbrella SMU CSCur72367 installed.
Workaround:
Restart ipsub_ma and iedged to recover from the failed state.
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 11-MAY-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus20753 |
Title: | ipv4_rib thread-6 crash in msg_receivev(); Due to SIGXFSZ, SEGV |
|
Description: | Symptom:
ipv4_rib crash on ASR9K
Conditions:
Traffic transiting DUT with MPLS-TE tunnels
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 11-MAY-2015 |
|
Known Affected Releases: | 5.2.2.BASE, 5.3.0.BASE |
|
Known Fixed Releases: | 5.2.4.6i.BASE, 5.3.1.20i.BASE |
|
|
| |
| |
Bug Id: | CSCur36872 |
Title: | Dual home satellite with CFM sending messages from both active and stby |
|
Description: | Symptom:
CFM loop is reported on MEPs when satellite is dual homed and CFM is configured both hosts satellite ports.
Conditions:
asr9000v running 5.2.0 with dual homed satellite and CFM configured on satellite ports
Workaround:
n/a
Further Problem Description:
n/a
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 12-MAY-2015 |
|
Known Affected Releases: | 5.2.0.CE |
|
Known Fixed Releases: | 5.2.3.12i.BASE, 5.2.3.12i.FWDG, 5.2.4.1i.BASE, 5.2.4.1i.FWDG, 5.3.0.14i.BASE |
|
|
| |
| |
Bug Id: | CSCud49605 |
Title: | ROUTING-FIB-2-OOR condition and possible forwarding drops |
|
Description: | Symptom:
ASR9K line cards running out of CEF resources with the following message.
"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:
All of the following conditions are necessary for the CEF Out Of Resource (OOR) condition:
(a)ASR9K running IOS-XR versions 4.2.0, 4.2.1, 4.2.2, 4.2.3 or 4.3.0.
(b)The Line cards have the following PIDs A9K.*SE or A9K.*TR or A9K.*-L or A9K.*-B, orA9K.*-LE.
(c)The routes are learnt via ECMP interfaces hosted by the line cards mentioned in (b).
(d)The ECMP interfaces flap such that at one time there can be only 1 interface which is used to learn the routes as in (c). Later on in time, those routes are re-learned via multiple ECMP interfaces.
Workaround:
None.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 12-MAY-2015 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.1.BASE |
|
Known Fixed Releases: | 4.3.1.14i.BASE, 5.1.0.2i.BASE |
|
|
| |
| |
Bug Id: | CSCuu08073 |
Title: | [532] ipv4_mfwd_partner crashes with BNG MCAST config |
|
Description: | Symptom:
ipv4_mfwd_partner crash
Conditions:
With BNG multicast config, while performing igmp join, ipv4_mfwd_partner crashes
Workaround:
NA
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 12-MAY-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | 5.3.2.7i.BASE |
|
|
| |
| |
Bug Id: | CSCum04100 |
Title: | Link flap or EIGRP process restart can lead to lost route in neighbor |
|
Description: | Symptom:
EIGRP not advertised some route to downstream neighbor, and check the downstream router in topology and RIB not have route.
Conditions:
Link flaps or Eigrp process restart.
Workaround:
clear route ipv4 unicast X.X.X.X/XX for issue route under ASR9K, the issue can solve.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 13-MAY-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | 4.3.2.SP1, 4.3.2.SP2, 4.3.2.SP3, 4.3.2.SP5, 4.3.2.SP6, 4.3.2.SP7, 5.1.1.19i.ROUT, 5.1.11.13i.ROUT, 5.1.2.10i.ROUT, 5.2.0.12i.ROUT |
|
|
| |
| |
Bug Id: | CSCuu30660 |
Title: | Umbrella SMU for 4.3.2 ASR9k parity error correction failure |
|
Description: | Symptom:
Error recovery process may not work correctly.
Conditions:
Single Bit ECC / Doubule Bit errors on ASR9k products.
Workaround:
Reset the failure linecard.
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 13-MAY-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut99536 |
Title: | IPv6 NS packets dropped on ingress of BE |
|
Description: | Symptom:
IPv6 NS packets sent by clients are dropped
Conditions:
Clients are connected behind a bundle-ethernet
Workaround:
Configure a static IPv6 neighborship for the router on the affected client
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 13-MAY-2015 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCut12758 |
Title: | SSTE: Observing prm_server_ty process crash after MPA oir |
|
Description: | Symptom:
wdsysmon detects and reports a deadlock within the prm_server_ty process and
as a result it restarts the prm_server_ty process. An example of the deadlock report
that appears in the syslog is:
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: DEADLOCK
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: =============================
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: node pid tid name STATE node pid tid name
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: deadlock 1 num_entries 2-----------
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: node0_2_CPU0 172114 1 prm_server_ty MUTEXnode0_2_CPU0 172114 23 prm_server_ty
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: node0_2_CPU0 172114 23 prm_server_ty MUTEXnode0_2_CPU0 172114 1 prm_server_ty
LC/0/2/CPU0:Mar 24 14:53:45 EST: wdsysmon[391]: ============================
The process id (pid) and thread id (tid) values may vary.
Conditions:
A Modular Port Adapter (MPA) in a modular linecard on the ASR9000 has been
reloaded with either a physical online insertion and removal (OIR) or with by
way of the "hw-module subslot reload" command.
Workaround:
There is no workaround. The process recovers after it is restarted by wdsysmon.
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 13-MAY-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCus34978 |
Title: | MIRROR_DISABLE=Y on rommon causes disk instability. |
|
Description: | Symptom:
RSP disk get corrupted.
Conditions:
RSP with rommon variable MIRROR_DISABLE=Y, and try to configure disk mirroring will cause the disk to get corrupted.
Workaround:
Remove the rommon variabile or turboboot.
Further Problem Description:
The following errors will be display:
RP/0/RSP0/CPU0:ios(config)#mirror location 0/RSP0/CPU0 disk0: disk1:
RP/0/RSP0/CPU0:ios(config)
|
没有评论:
发表评论