| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw79368 | Title: | max rlimit for BGP decrease in RSP-8G |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
max rlimit for BGP decrease after several days. BGP takes ~1.6Gig without an issue and after several days it started to crash at 1.4Gig.
Conditions:
This is in RSP-8G, platform API is returning the wrong rlimit to BGP
Workaround:
With the current RSP none given the customer scale - 2M routers/5M paths, 1 VRF 14 peerings.
However, it has been observed that the rlimit is higher with RSP-440/880, and hence it is recommended to use them instead.
Althernatively, an RR-based topology (instead of full mesh) would reduces the number of neighbours and hence reduces the route scale to some degree. This has to be validated.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.2.BASE, 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.22i.BASE, 6.0.0.26i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux17399 | Title: | eXR: Update ixgbe and ixgbevf versions in WRL7 SDK |
|
Status: | Open |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
RSP1 does not boot UP.
Conditions:
Do reimage to load image on the RSP.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv42837 | Title: | FLEXR: Can not add SMU when Active confd & inst_mgr are on diff RSPs |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: | Symptom:
Can not add SMU
Conditions:
Add SMU when Active confd & inst_mgr are on diff RSPs
Workaround:
Reload Calvados VM on the RSP which has Active inst_mgr.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu72532 | Title: | standby RP cannot be ready due to bgp BGP NSR sessions not synchronized |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
standby RP cannot be ready. It stuck at "bgp BGP NSR sessions not synchronized : inst_name=default, inst_id=0"
Conditions:
It can be hit by router reload and RP FO
Workaround:
No
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv78456 | Title: | unable to recover card from sw_inactive state |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
All LC in sw_inactive state
Conditions:
copied the library and then did shelf mgr restart..
Workaround:
Router reload
Further Problem Description:
try process restart of shelf_mgr if it helps recover
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu93156 | Title: | ipv6 static routes over tunnel-te interfaces not installed |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR9k running 5.3.0 code will experience some Ipv6 over Ipv4 packet drop
Conditions:
IPv6 static routes over Ipv4 TE tunnel forwarding chain corruption
Workaround:
no work around
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.15i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv34748 | Title: | BGP process heap corruption crash on vrf removal |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
bgp process crash could happen on vrf removal under router BGP
Conditions:
VRF is configured under BGP
Workaround:
Do not have more than 7 BGP sessions with vpn address families configured with default-originate while creating VRFs.
This is not really possible in all cases in production networks and depends on network design, topo and scale
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: * | 5.3.3.22i.ROUT, 6.1.0.7i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv82701 | Title: | eXR: backup rommon does not kick in after fpd upgrade is interrupted |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
Backup rommon does not kick in
Conditions:
The RSP4 board stuck in POWERED_ON / SW_INACTIVE after doing power cycle on router while upgrading rommon fpd is in progress.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv94339 | Title: | eXR: "show led" is broken in 6.0.0.12AG image |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
"show led" is broken.
Conditions:
Execute "show led" command.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.2, 6.0.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux21948 | Title: | ASR9k rejecting complete IKEv1 proposal with unsupported algorithms |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A Site-to-Site IPSec tunnel stays in down / down state and is never established.
This condition is caused by a complete rejection of an IKEv1 proposal if it contains crypto algorithms unsupported by the Cisco ASR9000 Series router with Virtualized Services Module [A9K-VSM-500].
Conditions:
A Site-to-Site IPSec tunnel is established between Cisco ASR9000 Series router with Virtualized Services Module [A9K-VSM-500] and peers advertising unsupported crypto algorithms.
The Cisco ASR9000 Series router acts as IPSec responder-only.
Workaround:
Configure the Cisco ASR9000 Series router as Initiator :
crypto ipsec profile PROFILE_NAME
no responder-only
NOTE: This is the DEFAULT configuration
Further Problem Description:
The following debug messages are seen on Cisco ASR9000 Series router
debug crypto service ipsec condition tunnel tunnel-ip
debug crypto isakmp main-mode all
debug crypto isakmp responder all
debug crypto isakmp initiator all
debug crypto isakmp quick-mode all
RP/0/RSP0/CPU0:Nov 13 08:49:13.723 : mbma[65908]: %OS-IKEV1COMPONENT-7-IKEV1_SM_RESPONDER_PARSING_NEW_SAI : Ikev1SessionManager Responder Exception parsing new SAI: Bad crypto algorithm or key length attributes
RP/0/RSP0/CPU0:Nov 13 08:49:23.722 : mbma[65908]: %OS-IKEV1COMPONENT-7-SM_DEMUX_LOOKUP_MISS : (tunnel-ip51) Received packet from unknown instance with i-SPI: 8D4B7875AD2EEF88, parsing in session manager
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.3.2.K9SEC |
|
Known Fixed Releases: | 5.3.3.20i.BASE, 6.0.0.26i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux44863 | Title: | SVS Fb 532: sshd_child_handler process crash |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Conditions:
Workaround:
Further Problem Description:
RP/0/RSP0/CPU0:asr9k-5#sh context
Fri Nov 20 10:38:17.232 EST
node: node0_0_CPU0
------------------------------------------------------------------
node: node0_1_CPU0
------------------------------------------------------------------
node: node0_2_CPU0
------------------------------------------------------------------
node: node0_RSP0_CPU0
------------------------------------------------------------------
Crashed pid = 1849016932 (pkg/bin/sshd_child_handler)
Crashed tid = 1
Crash time: Thu Nov 12, 2015: 19:54:32
Process thread:1 received signal: 6 - Unknown signal. Sender pid:1849016932
Signal specific information: Signal code 0 - Unknown signal
Core for process at harddisk:/dumper/sshd_child_handler.abort.20151112-195432.node0_RSP0_CPU0.x86.Z
Stack Trace
#0 0xe8c7ec2
#1 0xe8b7ff6
#2 0xe8c8d75
#3 0xea677d0
#4 0xea65689
#5 0xea65740
#6 0xea60757
#7 0x4212dda
#8 0x420a8b8
Registers info
EDI ESI EBP(fp) EXX
R0 10004524 041ff50c 041ff4ec fb3dccd0
EBX EDX ECX EAX
R4 00000001 0e8c7ec2 041ff4c0 00000000
EIP(pc) CS EFL ESP
R8 0e8c7ec2 000000f3 80001246 041ff4c0
SS
R12 000000fb
Crash Package Information
Package: iosxr-gcp-fwding, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-common-pd-fib, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-scfclient, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-os-mbi-5.3.2.CSCuw03715, Source: By iox-lnx-008 in /san1/smu/EFR/smu_r53x_5_3_2/workspace for pie
Package: asr9k-os-mbi, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9K-doc-supp, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-security, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-cpp, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-ce, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-ce, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-fpd, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-diags-supp, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-diags, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-mgbl-supp, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-mgbl, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-mcast-supp, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-mcast, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: iosxr-mpls-5.3.2.CSCuw96537, Source: By build-lnx-031 in /san1/SMU_BLD_WS/151029163036.4050 for pie
Package: iosxr-mpls-5.3.2.CSCuw26855, Source: By iox-lnx-008 in /san1/smu/EFR/smu_r53x_5_3_2/workspace for pie
Package: iosxr-mpls, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-k9sec-supp, Source: By iox-lnx-006 in /auto/srcarchive16/production/5.3.2/asr9k/workspace for pie
Package: asr9k-fwding-5.3.2.CSCuv98171, Source: By iox-lnx-008 in /san
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw82064 | Title: | OIR of A9K-MPA-4X10GE in Ironman - NP IN_RESET |
|
Status: * | Other |
|
Severity: * | 2 Severe |
Description: | Symptom:
No ingress nor egress traffic on interfaces related to NP In Reset:
RP/0/RSP0/CPU0:THBAMARRUECOS#show prm server context location 0/0/CPU0
Wed Sep 23 06:13:41.208 UTC
Node: 0/0/CPU0:
----------------------------------------------------------------
PRM Server Process Context :
Restarted Since Bringup : No
Thread Info :
TID Name Channel
--- ---- -------
1 prm_main /dev/prm_server
8 prm_stats /dev/prmLwmPath/evm_stats
9 prm_tm /dev/prmLwmPath/evm_tm
10 prm_tcam /dev/prmLwmPath/evm_tcam
11 prm_ss /dev/prmLwmPath/evm_ss
12 prm_show_np /dev/prmLwmPath/evm_show_np
13 prm_mac_plus /dev/prmLwmPath/evm_mac_plus
14 prm_poll /dev/prmLwmPath/evm_poll
15 prm_npdbg /dev/prmLwmPath/evm_npdbg
16 prm_srh_lp /dev/prmLwmPath/evm_low_priorit
17 prm_mac_cache /dev/prmLwmPath/evm_mac_cache
NP State :
NP0 : IN_RESET >>>>>>>>>>>>>
NP1 : RUNNING
RP/0/RSP0/CPU0:THBAMARRUECOS#show controllers NP ports all location 0/0/CPU0
Wed Sep 23 06:13:51.862 UTC
Node: 0/0/CPU0:
----------------------------------------------------------------
NP Bridge Fia Ports
-- ------ --- ---------------------------------------------------
0 0 0 TenGigE0/0/0/0, TenGigE0/0/0/1, TenGigE0/0/0/2, TenGigE0/0/0/3
0 0 0 TenGigE0/0/2/0, TenGigE0/0/2/1
1 1 1 GigabitEthernet0/0/1/0 - GigabitEthernet0/0/1/19
1 1 1 TenGigE0/0/2/2, TenGigE0/0/2/3
Conditions:
OIR of A9K-MPA-4X10GE in ASR-9001 running 4.3.4.
Workaround:
Reload of the box.
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 4.3.4.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur87691 | Title: | BNG: gigawords Accounting Radius reports high counter value |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
The Cisco ASR9k series routers may report high accounting information for the subscriber.
Example:
Acct-Input-Octets [42] 6 1354107856
RP/0/RSP0/CPU0:Sep 24 22:28:50.831 : radiusd[1108]: RADIUS: Acct-Input-Giga-Words[52] 6 1354107868
RP/0/RSP0/CPU0:Sep 24 22:28:50.831 : radiusd[1108]: RADIUS: Acct-Input-Packets [47] 6 1354107880
RP/0/RSP0/CPU0:Sep 24 22:28:50.831 : radiusd[1108]: RADIUS: Acct-Output-Octets [43] 6 1363273508
RP/0/RSP0/CPU0:Sep 24 22:28:50.831 : radiusd[1108]: RADIUS: Acct-Output-Giga-Words[53] 6 1354107904
RP/0/RSP0/CPU0:Sep 24 22:28:50.831 : radiusd[1108]: RADIUS: Nas-Identifier [32] 16 ACDC-ASR9000-1
Conditions:
when subscriber send multicast packets
Workaround:
n/a
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE, 5.2.2.LC |
|
Known Fixed Releases: | 5.2.4.5i.BASE, 5.3.1, 5.3.1.20i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw81641 | Title: | New 40 gig QSFP-40G-LR4-S support for ASR9k |
|
Status: * | Fixed |
|
Severity: * | 2 Severe |
Description: | Symptom:
New feature request to support new 40 gig optic
Conditions:
LC/0/3/CPU0:Oct 16 20:26:15.103 UTC: pfm_node_lc[294]: %PLATFORM-QSFP_PLUS-2-DEV_QSFP_PID_NOT_SUPPORTED : Set|vic_0[528556]|0x102c000|QSFP+ Module for port 00 is not a supported Product ID (PID)
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw67457 | Title: | PPPoE LAC session establishment delay with interfaces down on rack0 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PPPoE LAC session creation was delayed and fills up in flight queue.
Conditions:
In nV edge environment with control plane traffic forwarded to primary dsc through IRL link and go out through IRL.
For example,
Primary dsc was in rack0, but all the other interfaces except IRL are in down state.
Workaround:
No workaround found so far
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.3.21i.FWDG, 6.1.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux51854 | Title: | [600]traffic loss v4/v6 taps with Typhoon is ingress and Tomah is egress |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
more traffic loss seen
Conditions:
v4/v6 taps with Typhoon is ingress and Tomah is egress
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw43558 | Title: | [6.0.0] - interface is not getting detected while configuring on T1 spa |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Interface is not getting detected interface Serial0/1/0/0:0
Conditions:
While trying to configure the interface on the t1 spa
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.0.28i.BASE, 6.1.0.6i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux49683 | Title: | ASR9k - MPLS LDP local label assignment delayed - traffic loss |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Issue is that it takes quite some time for LDP to assign local labels. Therefore an initial ldp update is sent without labels assigned to the prefixes. This leads to a broken LSP (no end-to-end LSP) -> Traffic loss. After about 90 seconds an ldp update is sent with the labels assignments and the LSP is established end-to-end.
Conditions:
ASR9k as PE router using ISIS as core IGP and MPLS/LDP for label distribution. PE-CE protocol is eBGP.
Workaround:
None
In case of eBGP as PE-CE protocol the bgp update delay can be used to mitigate this issue.
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.3.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux51718 | Title: | NV satellite ring topology interface unknown |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
"show nv satellite topology" reports UnknownIntf for satellites in a ring
Satellite 143 (BVID 6)
Satellite fabric links:
TenGE/0/0/45 (Remote ID: 0x2e):
Sat 155 (TenGE/0/0/44 (nVFabric-TenGigE155/0/0/44) (Remote ID: 0x2d))
UnknownIntf (Remote ID: 0x0):
Host (UnknownIntf)
Conditions:
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur72095 | Title: | ASR9K doesn't relay OFFER messages with broadcase policy check flag. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In this case we can observe initial arp entry is installed after the first OFFER arrives from the server. After 5 minutes it goes into "probe" state and OFFERs are still arriving on the ASR9K, but ARP entry doesn't get renewed by OFFER messages.
Conditions:
1. We have DHCP relay configured with broadcast policy check flag
2. Client is sending DISCOVERs constantly, but cannot get an ip address for some reason.
Workaround:
Remove "Broadcast policy check flag"
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 4.3.4.SP7, 4.3.4.SP8, 5.3.0, 5.3.0.16i.FWDG, 5.3.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux51411 | Title: | 5.3.2 Umbrella SMU request for radiusd/bng |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
CSCux16976 BNG: radiusd crashed after coa via cli
CSCuv83731 Process radiusd crashed
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 14-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux44521 | Title: | 533.19i: Snoop with local DHCP server not working |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Session not coming up with local DHCP ipv4 server and snoop enabled
Conditions:
Snoop and Server config
Workaround:
NA.
Further Problem Description:
|
|
Last Modified: | 13-DEC-2015 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux50154 | Title: | 533.21I: Envmon errors out while performing walk thru SensorMIB |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The issue was seen during mib walk of 20x10EP.
The error message comes for incorrect spelling for the sensor.
Conditions:
During the mib walk of the voltage sensors for 20x10EP, error messages are seen.
Workaround:
The error messages do not have any functional impact. The voltage values of one voltage sensor "VP3P3_LDO" for EP will not be monitored in mib walk.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz72477 | Title: | "Packet too big" icmpv6 message not generated by Thor LC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
"Packet too big" icmpv6 messages are not generated towards the packet source when the size of the received packet is bigger than the MTU of the egress interface on A9K-SIP-700 linecards.
Conditions:
When the size of the received packet is bigger than the MTU of the egress interface on A9K-SIP-700 linecards.
Workaround:
No.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.0.25i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua48772 | Title: | Show env temp displays negative temp for fan trays |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On ASR9k device temperature readings might be wrong:
#sh environment all
Temperature Information
---------------------------------------------
R/S/I Modules Sensor (deg C)
...
0/FT0/*
host Inlet0 -50.0
host Hotspot0 -50.0
0/FT1/*
host Inlet0 -50.0
host Hotspot0 -50.0
Conditions:
Issue seen during normal operation.
Workaround:
There is no workaround.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.25i.BASE, 4.2.4, 4.3.0, 4.3.0.21i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua31485 | Title: | IOS XR: wrong ospf N2 route selection |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR9K may occasionally select the wrong path towards an N2 prefix. The issue is local on the ASR9k and, depending by the topology, it may generate routing loops for traffic of the specific N2 prefix.
Conditions:
This is often triggered by an OSPF recalculation, after which an higher cost path may be wrongly selected in the routing tables. This is a timing issue, which may occasionally show up.
Workaround:
An OSPF recalculation may restore the right route, but issue can show up again after a new OSPF recalculation.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.0.ROUT |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.19i.ROUT, 4.2.4, 4.3.0, 4.3.0.17i.ROUT, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux70706 | Title: | [601]-ASR9000v ICL Intf flaps after icpe_satmgr process restart on RP |
|
Status: | Open |
|
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: | 31-DEC-2015 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCto42983 | Title: | Thor ipv4_mfwd_partner crash when "show mfib hardware resource-counter" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: ipv4_mfwd_partner process crash seen on 4.0.1 FCS with SMU AA04700
installed.
Conditions: "show mfib hardware resource-counter loc"
Workaround: Use the corrected smu (or no smu)
Recovery: Sometimes it recovers on its own after multiple crashes. Other
timers, LC may be necessary
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.1.BASE, 4.0.1.ROUT |
|
Known Fixed Releases: | 4.1.0.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtr38918 | Title: | Multicast falls into wrong queue on CHOC3 when mapped by discard-class |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
MVPN multicast traffic falls into wrong queue at CHOC3 egress when mapping by discard-class. The discard-class was set correctly at input but then cleared to 0 at output, thus mutlicast packet never goes to the right queue.
Conditions:
1. MVPN packet decap
2. Egress is at CHOC3 LC
Workaround:
No workaorund
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.3.BASE |
|
Known Fixed Releases: * | 4.2.0, 4.2.0.12i.BASE, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2, 4.3.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul54537 | Title: | ASR9K SIP-700 sends RTP unicast traffic out of order in MPLS L3VPN Setup |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In a ASR9K SIP-700 Linecard, RTP Unicast packets with MPLS encapsulation can be forwarded out of order, with the smaller packet over taking the bigger packet occasionally.
The out of order packets can destabilize the Video applications like Telepresence from functioning correctly.
Conditions:
Only packets with MPLS Encapsulation with SIP-700 as Egress LC would hit the issue.
Workaround:
None except for redirecting such sensitive streams via another path bypassing SIP-700.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.LC |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.13i.BASE, 5.1.1, 5.1.1.16i.BASE, 5.1.11, 5.1.12, 5.1.2, 5.1.2.9i.BASE, 5.1.3, 5.1.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtq07754 | Title: | 410 SIT:Missing Src XID for punted IGMP pkts leads queries to wrong BD |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
IGMP queries are going to wrong BD
Conditions:
There are multiple bridge domains and pseudo-wires on SIP700 LC interfaces and
IGMP snooping is enabled.
Workaround:
None
Recovery:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 4.1.0.BASE |
|
Known Fixed Releases: * | 4.1.1, 4.1.1.21i.BASE, 4.1.2, 4.2.0, 4.2.0.5i.BASE, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui93782 | Title: | [CI 511 bugfix] Thor LC goes IN-RESET on TURBOBOOT due to multiple reset |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Thor LC crashes during bootup
Conditions:
Always
Workaround:
None
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtd78472 | Title: | IPSLA fails on SIP-700 and ICMP's are all failing over the SIP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
If IPSLA is used over a SIP700 based linecard, pings executed from the router
prompt will fail over that circuit and ipsla is not operational due to ping
timeouts.
Conditions:
Only when IPSLA is running over a SIP based circuit, that is an interface that
resides on the SIP700 SPA carrier card (eg CHOC12/DS1 circuits/MLP)
Workaround:
Disable IPSLA over SIP700 based circuits
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 3.9.0.BASE, 3.9.1.BASE |
|
Known Fixed Releases: * | 3.9.1, 3.9.1.14i.LC, 3.9.1.23i.LC, 3.9.2, 3.9.3, 4.0.0, 4.0.0.99i.BASE, 4.0.1, 4.0.2, 4.0.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub09660 | Title: | ASR9000: Traffic not sent from AC to PW for ATM Port-mode |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
port mode ATMoMPLS may fail to pass traffic from AC to PW, those packet drops are on counted on BadUidbSubIdx counter under pse qfp drops.
RP/0/RSP0/CPU0:ios#show controllers pse qfp statistics drop location 0/0/CPU0 $
Global Drop Statistics for QFP 0
----------------------------------------------------------------
Global Drop Stats Packets Octets
----------------------------------------------------------------
BadUidbSubIdx 18264 1022784
Conditions:
N/A
Workaround:
N/A
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.26i.BASE, 4.2.4, 4.3.0, 4.3.0.24i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu75739 | Title: | UDP DHCP(dport 67,68) over PW dropped by ASR9K whenDHCP snoop disabled |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
DHCP client - L3 router (relay agent) - ASR9K#1 --- PW(L2VPN) -- ASR9K#2 - L3 router - DHCP Server
When DHCP snooping is disabled, UDP packet(port 67,68) should be transferred over L2VPN, but it is getting dropped at the egress.
Conditions:
L2 VPN(PW) should be configured between DHCP server and client.
And, L3 router located between DHCP client and ASR9K works as relay agent.
Refer to the topology.
Workaround:
Enable DHCP snoop and trust PW interface on ASR9K located in DHCP server side.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.3.1.LC, 4.3.4.LC |
|
Known Fixed Releases: * | 5.3.3.10i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt18617 | Title: | .asr9k mvpn PE does not cache auto-rp discovery when receiving from CE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Unpon receiving the auto-rp discovery packet from its directly connected CE acting as RP, ASR PE does not cache the packet. No auto-rp information in "show pim vrf xyz group-map". ASR does forward the discovery packet to other downstream PE's.
Conditions:
Workaround:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.1.BASE |
|
Known Fixed Releases: * | 4.0.11.4i.BASE, 4.1.2, 4.1.2.20i.BASE, 4.2.0.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCti12549 | Title: | prm_server crashes with broadcast storm control config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On a Cisco 9000 series, prm_server repeatedly crashes on the linecard.
Conditions:
Application of a large broadcast storm control config.
Recovery:
Remove/reduce the broadcast storm control config. Reload the linecard if problems persist.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 3.9.0.BASE, 3.9.1.BASE, 4.0.0.BASE |
|
Known Fixed Releases: * | 4.0.0, 4.0.0.29i.BASE, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0, 4.1.1, 4.1.2, 4.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv74321 | Title: | 9000v SAT - Memory Leak Observed |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
9000v SAT - Memory Leak Observed
Conditions:
Steady state ..
Workaround:
Not known
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.3(2) |
|
Known Fixed Releases: * | 15.1(3)SVI02 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux52200 | Title: | SSTE:show tech-support access-lists invalid command |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
show tech-support access-lists give following error:
Invalid input detected at '^' marker
Conditions:
this behavior is observed when turboboot the 27I and 28I
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 19-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua19968 | Title: | L3 Load balance on MGSCP for L3VPN not working. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
For MGSCP enabled system, if IPv4 traffic is received from L3VPN deagg on Trident LC and targets to MGSCP enabled bundle, the load balance over egress bundle will not meet MGSCP load balance requirement.
Conditions:
1. MGSCP enabled in the system
2. IPv4 traffic received from L3VPN deagg on a Trident LC and targets to MGSCP enabled bundle.
Workaround:
None
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.0, 4.2.3.99i.BASE, 4.3.0, 4.3.0.15i.BASE, 4.3.91, 5.0.0, 5.0.1, 5.0.90 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux62126 | Title: | VPN def-orig withdraw w wrong label sent after ~16 mins after BGP NSR FO |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Wrong vpnv4 0.0.0.0/0 withdrawn w normal label (non 524288) could be send to subset of peers by VPN def-orignate feature
after RSP switchover w BGP NSR.
Causes 0.0.0.0/0 vpnv4 removal on affected peers.
Conditions:
1) VPN def-orignate enabled fro vpnv4.
2) More then 7 peers in vrf;
3) vpnv4 0.0.0.0/0 withdrawn will be sent to last peers after frist 7
Workaround:
1) After issue happens - soft clear for affected peers;
2) Potentially avoid more then 7 peers in vrf.
Further Problem Description:
|
|
Last Modified: | 19-DEC-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux55506 | Title: | Process xml_tty_agent crashed at xml_mda_get_operation_type |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
Process xml_tty_agent crashed at xml_mda_get_operation_type
Conditions:
node with 600-28I image during the day -1 longevity test. No active testing on the node, it has below monitoring tools integrated to monitor memory and cpu process. ACT tool is the one using the xml.
Monitoring tools:
??? X-Scale MIB Poller / SNMP Poller for monitoring SNMP
??? PAM tool for detecting memory leak in RSP and LC
??? ACT Tool is running
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.MGBL |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw48933 | Title: | SSTE:mibd_entity process crash during longevity snmp testing |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:When polling snmp via a script, the mibd_entity process crashes.
Crashed pid:1188207 (mibd_entity) Time:Tue Sep 29 10:12:55 2015
Thread:2 received signal:31 - Unknown signal. Sender:mibd_entity pid:1188207
Signal specific information: Signal code 0 - Unknown signal
Conditions:This issue is seen when polling ceImageMIB or when it is not excluded from polling in longevity test
Workaround:1) If not interested in polling ceImageMIB, please exclude ceImageMIB via SNMP view configurations we could exclude ceImage MIB from view with following CLIs
snmp-server view 1 included
snmp-server view 1.3.6.1.4.1.9.9.249 excluded
2) running software version and image details are pretty static, you could configure separate SNMP view for querying ceImageMIB with very low frequency, lets say once in 30 minutes/hour(as running image will not change within this frequency in customer place)
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46286 | Title: | ICCP redundancy configuration affects existing MPLS LDP based services |
|
Status: | Open |
|
Severity: * | 2 Severe |
Description: | Symptom:
When a Redundancy Group is configured on a router, MPLS LDP based services are affected and a significant traffic outage is seen on IPv4 over OSPFv2, IPv4 over BGP and IPv4 over IS-IS.
In presence of the Redundancy Group, RSP failovers will also trigger teh same traffic outage.
Conditions:
Redundancy Group must be present in the configuration of the router.
Workaround:
Do not configure a Redundancy Group and avoid configuring 9000v Satellites in a RING topology. Instead, use Hub and Spoke for the 9000v satellites.
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur71262 | Title: | PWHE L3 sub-interface: Incoming CE ARP RSV_DROP_MPLS_NRLDI_NO_MATCH |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
PWHE ARP responses from CE are dropped by ASR9K which is acting as the SPE.
Conditions:
ASR9K is running one of the following IOS-XR releases:
4.3.0
4.3.1
4.3.2
4.3.4
5.1.0
5.1.1
5.1.2
5.1.3
5.2.0
5.2.2
5.2.4
This issue may not be seen all the time and is applicable in theory to the above releases.
Workaround:
Flap the PWHE interface associated with problem scenario.
Or
Restart fib_mgr process on the LC where the ARP packets are dropped with reason RSV_DROP_MPLS_NRLDI_NO_MATCH.
(this drop reason will be known to be ARP related only after some debugging is done).
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: * | 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, 5.1.3.FWDG, 5.2.0.FWDG, 5.2.2.FWDG |
|
Known Fixed Releases: | 5.3.0.18i.BASE, 5.3.0.18i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw47244 | Title: | Slingshot EDVT: Erroneous BIP errors on PHY PCS Receive-Side from optics |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
'show controller hundredGigE 0/0/0/0 phy' reports BIP Errors
Conditions:
Board in IOS-XR RUN state. Aproximately 85% of interface power-ons/config
If once interface have few BIP Error, then as PHY is not clearing the error register conters and XR logic expects only delta from the PHY during read is performed. BIP Error in XR display will keep on incrementing (although these are bogus, there is no real problem), no functionality impact is expected with this.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux65231 | Title: | Process may get deadlocked when running commands that resync mac cache |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
May see l2fib_mgr and vkg_l2fib_mac_cache processes get blocked when a resync command fails/times out. These processes being blocked can cause other system or service impact.
node: node0_4_CPU0
------------------------------------------------------------------
92 40984 2 umass-enum Reply 898:29:34:0442 1 kernel
92 40984 5 umass-enum Reply 898:29:23:0695 45084 io-usb
92 40984 6 umass-enum Reply 898:29:23:0697 1 kernel
52 40985 1 ksh Reply 898:29:34:0497 12297 serdrvr
51 49179 2 attachd Reply 898:29:31:0674 45090 eth_server
51 49179 3 attachd Reply 898:29:31:0674 16398 mqueue
65571 45091 2 devb-umass Reply 898:29:23:0549 45084 io-usb
85 49188 6 qnet Reply 0:00:00:0000 45090 eth_server
85 49188 7 qnet Reply 0:00:00:0000 45090 eth_server
50 49193 2 attach_server Reply 898:29:31:0758 16398 mqueue
249 487549 1 l2fib_mgr Mutex 1:18:13:0374 487549-11 #1
249 487549 11 l2fib_mgr Reply 0:01:33:0455 159749 sysdb_svr_local
363 487550 4 vkg_l2fib_mac_cache Mutex 333:03:49:0129 487550-05 #1
Conditions:
if a resync fails when we run a mac-address show command (which could happen if the resync is taking too long), we will continue to try to run the show command anyway, which will in-turn lock the l2fib mac cache.
Workaround:
restart the processes to recover.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.1.2.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46731 | Title: | Second level recursion broken upon IGP level ECMP change. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
RP/0/RSP0/CPU0:ASR9904-D#show cef 8.8.8.8 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:41:27.164 UTC
leaf_ptr: 0x3466(LE) bgp_next_hop: 0x7070707 <<< leaf doesn't match with index
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3408 (BE)] <<<
Conditions:
Upon changing number of nexthops/ECMP count, the second level recursion doesn't back walk completely which causes leaf to point to old NRLDI pointer.
This issue will happen only when you have global BGP, no LDP and all the IGP paths are only tunnels.
Workaround:
Clear route ipv4
or
clear cef ipv4 linecard location <>
Further Problem Description:
RP/0/RSP0/CPU0:ASR9904-D#show cef 6.6.6.6 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:39:37.077 UTC
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3466 (BE)]
fastNR-LDI H/W Result for path 1 [Common to all NPs: index: 0x3467 (BE)]
RP/0/RSP0/CPU0:ASR9904-D#
RP/0/RSP0/CPU0:ASR9904-D#show cef 7.7.7.7 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:39:39.192 UTC
leaf_ptr: 0x3466(LE) bgp_next_hop: 0x6060606
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3466 (BE)]
fastNR-LDI H/W Result for path 1 [Common to all NPs: index: 0x3467 (BE)]
RP/0/RSP0/CPU0:ASR9904-D#
RP/0/RSP0/CPU0:ASR9904-D#show cef 8.8.8.8 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:39:52.494 UTC
leaf_ptr: 0x3466(LE) bgp_next_hop: 0x7070707
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3466 (BE)] <<<<<<< Matches
fastNR-LDI H/W Result for path 1 [Common to all NPs: index: 0x3467 (BE)]
Upon changing number of nexthops/ECMP count, the second level recursion doesn't back walk completely which causes leaf to point to old NRLDI pointer
RP/0/RSP0/CPU0:ASR9904-D(config)#router static
RP/0/RSP0/CPU0:ASR9904-D(config-static)# address-family ipv4 unicast
RP/0/RSP0/CPU0:ASR9904-D(config-static-afi)# 0.0.0.0/0 172.18.120.129
RP/0/RSP0/CPU0:ASR9904-D(config-static-afi)#no 6.6.6.6/32 tunnel-te8110 permanent <<< removed
RP/0/RSP0/CPU0:ASR9904-D(config-static-afi)#commit
RP/0/RSP0/CPU0:ASR9904-D#
RP/0/RSP0/CPU0:ASR9904-D#show cef 6.6.6.6 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:41:16.111 UTC
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3408 (BE)]
RP/0/RSP0/CPU0:ASR9904-D#show cef 7.7.7.7 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:41:20.575 UTC
leaf_ptr: 0x3408(LE) bgp_next_hop: 0x6060606
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3408 (BE)]
RP/0/RSP0/CPU0:ASR9904-D#show cef 8.8.8.8 hardware ingress detail location 0/0/CPU0 | include "leaf_ptr|fastNR-LDI"
Tue Dec 8 13:41:27.164 UTC
leaf_ptr: 0x3466(LE) bgp_next_hop: 0x7070707 <<<< leaf doesn't match with index
fastNR-LDI H/W Result for path 0 [Common to all NPs: index: 0x3408 (BE)] <<<<
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux03904 | Title: | SSTE: Observing mpls_ldp crash on XR6.0.0 21i image after switchover |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:mpls_ldp crash on new active after RP failover.
Conditions:crash noticed after many failovers(1 in 8 to 10 times)
The crash is happening only on setup with CSC and segmented multicast both being tested. Customer is unlikely to use both features together. They would either have CSC or segmented multicast but not both.
Workaround:mpls_ldp process recovers automatically (i.e without any manual intervention)
More Info:No functional or traffic impact
Issue not easily reproducible. Possible heap corruption.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux47741 | Title: | Router stops advertising BGP rtfilter |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Peers stop advertising routes to ASR9k
Conditions:
ASR9k running 5.3.2 and using ipv4 rtfilter address family.
Configuration change in one of the peers of the update-group (TBC)
Workaround:
clear bgp vpvn4 session
Further Problem Description:
Advertising stops due to the ASR9k not sending any rtfilter anymore.
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux49645 | Title: | Config crash oberved while commit replace |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
This issue seen once we commit replace the startup config file on router with current configuration.
After observing this issue , router stuck with any commit replace , it always crashes so unable to proceed in script run as well.
Following message is observed before crash of config process.
RP/0/0/CPU0:Dec 18 13:08:42.923 : config[66745]: %MGBL-CONFIG-6-INT_UNRESOLVED : Some of the interface configuration was moved to pre configuration automatically as these interfaces does not exist.could not be mapped to any cards
Conditions:
This issue seen with commit replace when non-existent interfaces being configured and it's being moved to pre-configure after commit replace.
Workaround:
Workaround is to not commit replace non-existing interfaces.
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23412 | Title: | eXR: Fabric card stuck in POWERED_ON state in slot 0 in multiple chassis |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Fabric card stuck in POWERED_ON state after reimage.
Conditions:
Load 6.1.0.08I / EFR-00000317345 image on a 9912 router using reimage_chassis.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv30073 | Title: | SSTE: Observing BFD process crash on ASR9k running XR5.3.2 15i |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BFD process crash will be observed in this problem state.
Conditions:
Some times back to back RPFO causes this problem
Workaround:
No known workaround.
Further Problem Description:
Even without RPFO,this problem might happen when the BFD process is continuously restarted within a short time say for example restart BFD ~10 times within 2-3 seconds
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE, 6.0.0.BASE, 6.0.0.LC |
|
Known Fixed Releases: * | 5.2.5.39i.FWDG, 5.3.2, 5.3.2.20i.FWDG, 5.3.3.6i.FWDG, 6.0.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46652 | Title: | NSR ISIS fails - neighborship restarted on switchover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ISIS sessions are restarted on RP switchover
Conditions:
NSR isis activated
On switchover
Workaround:
Use "NSF Cisco" which seems to be working fine
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.3.ROUT |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.3.24i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux63393 | Title: | QOS policy-map not applied on new sessions. |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
When we apply QOS policy-map on physical interface new bng sessions on sub interfaces are not matched by those policies.
If we remove the policy-map from physical interface, commit, add it again, commit, then all sessions will be matched.
Conditions:
This has been seen in 5.2.4 with and without SP1.
Workaround:
Remove the policy-map from physical interface, commit, add it again, commit, then all sessions will be matched.
Further Problem Description:
|
|
Last Modified: | 25-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw11099 | Title: | p2mp imp null: multicast traffic drop on tail nodes with imp null label |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
tail nodes drop all the multicast traffoc with RSV_P2MP_RPF_FAIL with implicit null label.
Conditions:
implicit null label.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu82001 | Title: | FLEXR: xr vm on RSP is not spawned after fpd upgr reload - sdr_mgr recvr |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
xr vm on RSP is not spawned after fpd upgrade reload - sdr_mgr should have recovered from this error.
Conditions:
Executed "upgrade hw-module loc 0/RSP1 fpd IPU\ FPGA force" and "hw loc 0/RSP1 reload"
commands to do fpd upgrade on RSP.
Workaround:
Unknown
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua73510 | Title: | L2TP packets inspected even they're not destined for router |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
L2TP traffic might be inspected even it's not destined for local router.
Conditions:
L2TP traffic switched through the box.
Workaround:
There is no workaround.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.24i.BASE, 4.2.4, 4.3.0, 4.3.0.21i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw12380 | Title: | Unmbrella DDTS for XR 5.1.3 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
This is umbrella bug required to create a common SMU for all constituent bugs.
Conditions:
No conditions
Workaround:
No workarounds
Further Problem Description:
|
|
Last Modified: | 03-DEC-2015 |
|
Known Affected Releases: | 5.1(3) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv96168 | Title: | eXR: Need enhancements to read info of Golden version of FPDs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Need enhancements to read info of Golden version of FPDs.
Conditions:
We need enhancements to read info of Golden version of FPDs for checking if FPD falls back to Golden version on a board.
Workaround:
Only for testing purpose and not real need.
Further Problem Description:
test tool for Read the golden version of FPD
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux26077 | Title: | eXR: CLI registration issue - RSP1 / FT is not seen in OBFL commands |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
RSP1 / FT is not seen in OBFL commands.
Conditions:
Try to execute "show logging onboard uptime loc 0/RSP1" command.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu80394 | Title: | FLEXR: Umbrella DDTS of fixes from R52X for issues found in envm testing |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
Need to include fixes from R52X for issues found in envm testing in bnb-54-flex lineup.
Conditions:
Need to include fixes from R52X for issues found in envm testing in bnb-54-flex lineup.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv22980 | Title: | Copy files from calvados to external servers |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
User can not copy any file directly from sysadmin LXC to external location.
Conditions:
The candidate file has to be present on sysadmin LXC.
Workaround:
User has to scp the target file to XR LXC file system. The file can be copied to external location from XR LXC.
Further Problem Description:
Sysadmin LXC does not have external port connectivity. This results in no route available from sysadmin to any location out of the router.
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv66096 | Title: | eXR: calvados_login_shell_ crash in is_valid_tty - 6.0.0.10I image |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
calvados_login_shell_ crash in is_valid_tty
Conditions:
Upgrading fpd versions followed by executing "reload rack 0".
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv64079 | Title: | eXR: RSP IPU FPGA stuck in UPGD FAIL after executing "upgrade fpd all" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RSP IPU FPGA stuck in UPGD FAIL after executing "upgrade fpd all".
Conditions:
Executing "upgrade fpd all" command to upgrade all fpd versions on all boards in the chassis.
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.0.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv68252 | Title: | eXR: "show context" picks up old crash info - 6.0.0.X13 image |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
"show context" picks up old crash info
Conditions:
Execute "reload admin loc 0/0" command to trigger a process crash.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv86165 | Title: | eXR: ACO LED stops working in 6.0.0.10I image |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
ACO LED stops working.
Conditions:
Press ACO button on RSP4.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw61409 | Title: | eXR: Last Event fields in "show platform detail" show UNKNOWN |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Last Event and Last Event Reason show UNKNOWN in outputs of
"show platform detail loc 0/RSP0" command.
Conditions:
Execute "show platform detail loc 0/RSP0" command.
Workaround:
Unknown
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv48938 | Title: | FLEXR: Debug messages are seen when executing "sh tech alarm_mgr" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Debug messages are seen when executing "sh tech alarm_mgr"
Conditions:
Execute "sh tech alarm_mgr" command.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv22574 | Title: | FLEXR: fpdserv crash in calvados_ds_handle_destroy |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
fpdserv crash in calvados_ds_handle_destroy is seen in 6.0.0.x12 / EFR-00000306594 image.
Conditions:
Reload 9904 router which has 2 RSPs and 1 A9K-8X100GE-L-SE linecard.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv46968 | Title: | FLEXR: Integrate FPD_Agent with OBFL |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
%INFRA-FPD_Driver-1-UPGRADE_ALERT is seen in syslog.
Conditions:
Do FPD driver process restart (like canbus_driver, fpd_agent).
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw93388 | Title: | 'placed' took too long to respond to a startup request and was timed out |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
After several restarts of netconf it does not start or it is configured by cli commands (netconf-yang agent ssh) but does not work.
Conditions:
Test steps:
1. Configure router with minimal configuration (see attached)
2. Load an oper yang by requesting oper data from a component using netconf
3. Check the response
4. Restart netconf
5. Repeat steps 2 to 4
After 66 restarts of netconf it is not possible to proceed.
If we skip loading of oper yangs, it needs approx. 170 restarts to get stuck.
Workaround:
Do not restart Netconf Many times in a short time
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw11732 | Title: | eXR: Can not login to calvados after reload admin location 0/RP1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Can not login to Calvados VM.
Conditions:
Execute " reload admin location 0/RP1" command on Megatron router with dual RPs.
Workaround:
Unknown.
Further Problem Description:
System configuration restore takes more time at times. During that time, we'll hit this issue and new user cannot be created. Need to wait until the configuration completes.
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.0.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | 6.0.0.19i.BASE, 6.1.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv38075 | Title: | Viking ASR-9910/A99-RSP, copy problem from ext USB to internal disk |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Not able to copy files from external USB to internal disk of RSP.
Conditions:
Not able to copy files from external USB to internal disk of RSP.
Workaround:
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv08571 | Title: | FLEXR: Issues in node reload reason in output of "show redundancy" |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
Issues in node reload reason in output of "show redundancy"
Conditions:
Trigger RSP failover.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv68234 | Title: | eXR: canbus_driver crash in canb_oal_main_wait - 6.0.0.X13 image |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
canbus_driver crash in canb_oal_main_wait.
Conditions:
Do fpd upgrade on A9K-8X100GE-L-SE linecard then execute "reload rack 0" command.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux32649 | Title: | eem_server pcocess keeps crashing after RPSO |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:eem_server process keeps crashing
Conditions:After RPFO
Workaround:
1) shut down both active and standby processes
process shutdown eem_server location 0/RSP0/CPU0
process shutdown eem_server location 0/RSP1/CPU0
2) attach to shell and remove files
Run attach 0/RSP0/CPU0
rm /dev/shmem/chkpt/*eem_server*
Run attach 0/RSP1/CPU0
rm /dev/shmem/chkpt/*eem_server*
3) restart active and then standby.
process start eem_server location 0/RSP0/CPU0
process start eem_server location 0/RSP1/CPU0
More Info:process restart eem_server/ RPFO again is not working
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux36987 | Title: | mibd_interface leaks memory when CFM MIB is polled |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Process mibd_interface is leaking memory
Conditions:
CFM configured and CFM MIB is polled regularly
Workaround:
none, except excluding CFM MIB from the view
Further Problem Description:
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: * | 5.1.3.CE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux15670 | Title: | [FlexR]: RSP's DIE_CPU Reads False Temp Value at -5C |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Conditions:
Workaround:
Further Problem Description:
0/RSP1
! DIE_CPU 255 -10 -5 0 73 84 98
DIE_FabArbiter0 5 -10 -5 0 107 114 122
DIE_FIA 9 -10 -5 0 110 113 115
DIE_PCH 8 -10 -5 0 65 75 85
DIE_DIMM0 1 -10 -5 0 55 65 75
DIE_DIMM1 1 -10 -5 0 55 65 75
DIE_DIMM2 1 -10 -5 0 55 65 75
DIE_DIMM3 1 -10 -5 0 55 65 75
DIE_FabSwitch0 10 -10 -5 0 110 113 115
DIE_FabSwitch1 8 -10 -5 0 110 113 115
! AIR_Inlet 0 -10 -5 0 55 65 75
SM15_0_Downstream 7 -10 -5 0 75 85 95
SM15_0_Inlet 2 -10 -5 0 55 65 75
SM15_1_Upstream 1 -10 -5 0 55 65 75
AIR_Outlet 6 -10 -5 0 65 75 85
! Inlet -1 -10 -5 0 55 65 75
Hotspot 7 -10 -5 0 81 83 86
RP/0/RSP0/CPU0:ios#show log | inc CRITICAL
:Nov 12 12:15:35.026 : envmon[1812]: %PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :temperature alarm :DECLARE :0/RSP1: DIE_CPU has raised a temperature alarm with value of 255
:Nov 12 12:22:16.065 : envmon[1812]: %PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :temperature alarm :CLEAR :0/RSP1: DIE_CPU has cleared a temperature alarm with value of 1
:Nov 12 12:25:57.081 : envmon[1812]: %PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :temperature alarm :DECLARE :0/RSP1: DIE_CPU has raised a temperature alarm with value of 255
:Nov 12 12:28:17.094 : envmon[1812]: %PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :temperature alarm :CLEAR :0/RSP1: DIE_CPU has cleared a temperature alarm with value of 1
:Nov 12 12:30:38.105 : envmon[1812]: %PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :temperature alarm :DECLARE :0/RSP1: DIE_CPU has raised a temperature alarm with value of 255
sysadmin-vm:0_RSP0# show install active
Sun Nov 12 13:31:04.558 UTC
Node 0/RSP0 [RP]
Active Packages: 2
asr9k-sysadmin-6.1.0.04I version=6.1.0.04I [Boot image]
asr9k-sysadmin-asr9k-6.1.0.05-r61004I.CSCux11237
Node 0/RSP1 [RP]
Active Packages: 2
asr9k-sysadmin-6.1.0.04I version=6.1.0.04I [Boot image]
asr9k-sysadmin-asr9k-6.1.0.05-r61004I.CSCux11237
Node 0/0 [LC]
Active Packages: 2
asr9k-sysadmin-6.1.0.04I version=6.1.0.04I [Boot image]
asr9k-sysadmin-asr9k-6.1.0.05-r61004I.CSCux11237
Node 0/1 [LC]
Active Packages: 2
asr9k-sysadmin-6.1.0.04I version=6.1.0.04I [Boot image]
asr9k-sysadmin-asr9k-6.1.0.05-r61004I.CSCux11237
Node 0/2 [LC]
Active Packages: 2
asr9k-sysadmin-6.1.0.04I version=6.1.0.04I [Boot image]
asr9k-sysadmin-asr9k-6.1.0.05-r61004I.CSCux11237
Node 0/3 [LC]
Active Packages: 2
asr9k-sysadmin-6.1.0.04I version=6.1.0.04I [Boot image]
asr9k-sysadmin-asr9k-6.1.0.05-r61004I.CSCux11237
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux26768 | Title: | Console Displaying Messages Indicating BGP NSR Disabled |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: |
Symptom:
BGP Sessions with 1/3 timers are getting NSR disabled frequently
Conditions:
unknown
Workaround:
Not-avaiable . Use recommonded timers
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux17472 | Title: | AutoBW LSP_BW_CHANGE and REOPT missing |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Auto-bw the LSP_BW_CHANGE and LSP_REOPT syslog is not reported in MPLS-TE logging
Conditions:
Change traffic rate through MPLS-TE tunnel with auto-bw
Workaround:
None
Further Problem Description:
Heavy flood of syslog messages (4000 tunnels x 4 syslogs per tunnel) in a few seconds
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux41951 | Title: | ACL-TCAM resource leak rarely after a failed commit due to OOR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After ACL object group manipulation, number of free acl entries from command "show prm server tcam summary all all location " might be lower compared to "sh pfilter-ea fea summary location ".
Conditions:
This was observed on 5.2.4 using scaled ipv4 ACL setup with object groups.
Workaround:
Linecard reload clears the issue.
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 6.1.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux28412 | Title: | ethernet uni id command is absent for a satellite interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ethernet uni id is not availbe for satellite interfaces
Conditions:
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 6.1.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
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: | 17-DEC-2015 |
|
Known Affected Releases: | 5.3.3.ADMIN, 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.23i.FWDG, 5.3.3.23i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux55626 | Title: | XR: memory leak in the eem_server process |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Memory leak is visible in the eem_server process.
After each execution of the tcl script xos_ipc_alloc_msg_ctx is allocating more blocks.
Conditions:
IOS XR running TCL script (exact root cause is unknown yet)
Workaround:
eem_server process restart
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw43329 | Title: | ASR9k DWDM-XFP-C V02 wavelength is not programmed on A9K-8T-L linecard |
|
Status: * | Other |
|
Severity: * | 3 Moderate |
Description: | Symptom:
Tunable DWDM-XFP-C does not transmit the configured wavelength. In "show controller dwdm a/b/c/d" output wavelength is always shown as 1561.826nm (default) regardless of configured value:
RP/0/RSP0/CPU0#show run controller dwdm 0/1/0/3
controller dwdm0/1/0/3
wavelength 50GHz-Grid 39
admin-state in-service
!
RP/0/RSP0/CPU0:#sh controllers dwdm 0/1/0/3
....
Optics Status
Optics Type: 10G-TUNABLE-by-CHANNEL,
Wavelength Info: C-Band, MSA ITU Channel=84, Frequency=191.95THz, Wavelength=1561.826nm
Wavelength Owner: Configuration, ITU Channel: GMPLS Signaled=None, Configured=39, Hardware Default=84
TX Power = 1.50 dBm
RX Power = -15.01 dBm
Conditions:
- ASR9000 with tunable DWDM XFP (DWDM-XFP-C V02) configured with specific wavelength.
- The issue is seen in 5.3.2, while this works as expected in 5.3.1.
Workaround:
There is no workaround
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua69819 | Title: | SIA happens on the network with detour. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
SIA happens on a set of routers on a network with detour.
Condition:
there are detours on the network.
Workaround:
there is no workaround.
Trigger:
Withdrawal of a prefix.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.23i.ROUT, 4.2.4, 4.3.0, 4.3.0.20i.ROUT, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua66583 | Title: | ASR9k multicast traffic soft switched on egress FR subintf |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR9k does not HW forwarding the traffic to FR subintf to CE receiver instead the traffic is soft switched.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.MCAST, 4.3.0.MCAST |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.28i.BASE, 4.2.4, 4.3.0, 4.3.0.18i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua96099 | Title: | ASR9K - gratuitous arp with wrong MAC address |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR9K generates gratuitous arp with wrong MAC address
Conditions:
Using duplicate IP addresses on ASR9k
Workaround:
none
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.28i.FWDG, 4.2.4, 4.3.0, 4.3.0.24i.FWDG, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub55611 | Title: | traffic punted unexpectedly after LC reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Reloading LC where a bundle interface has a member causes the traffic via that member to drop.
Conditions:
High number of routers, e.g. 50k.
Workaround:
shut/no-shut of the member interface
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.28i.BASE, 4.2.4, 4.3.0, 4.3.0.25i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40082 | Title: | lda_server restart,macsec db corruption which in turn fails sa rekey |
|
Status: * | Fixed |
|
Severity: * | 3 Moderate |
Description: * | Symptom:
Flow adding failed in Rekey process on 100G macsec enabled vlan interface.
Conditions:
This behaviour observed if lda_server process was restarted and then rekey happen.
This issue is observing only on 100G. Also number of macsec configured sub-interface should be more than
40 on 100G interface.
Workaround:
None
Recovery:
Need to reload the LC.
Example:
hw location 0/0/cpu0 reload
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: * | 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua04907 | Title: | ASR9K: Bundle-Ether & Members not showing corect interface traffic stats |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"show interface " does not show
expected packet drop stats while "show interface "
does.
There is no packet forwarding impact due to this issue.
The issue is with drop statistics accumulation.
Conditions:
The asr9000 router is running an ios xr version 4.2.1.15I or later.
Workaround:
No workaround.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.2.2, 4.2.2.13i.BASE, 4.2.3, 4.2.3.23i.BASE, 4.2.4, 4.3.0, 4.3.0.20i.BASE, 4.3.1, 4.3.2, 4.3.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua74791 | Title: | Bundle IF does not come up with CSCty99912 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When the router is reloaded with bundle configuration, Bundle interface is not coming as LACP packets are not received.
Conditions:
This condition happens with CSCty99912 SMU.
Workaround:
Remove and reapply the bundle configuration.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.1.2.BASE, 4.1.2.MGBL |
|
Known Fixed Releases: * | 4.2.3.21i.BASE, 4.3.0.20i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum03261 | Title: | Need to drop traffic when lineproto is down on SIP700 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When the line protocol is down on the serial HDLC or PPP link the CPP continues to forward
traffic and accept packets.
while this is generally not an issue, the problem is that Y cable redundancy sees packet duplication.
Conditions:
serial PPP/HDLC links on the SIP700 with a lineprotocol down
Workaround:
For Y cable, admin shutdown the interface and use EEM to enable the interface on a failover scenario.
Alternatively MR-APS is an option too.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.3.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, 4.3.4.SP8, 5.1.2, 5.1.2.12i.BASE, 5.1.3, 5.1.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz96537 | Title: | Few packet leaks with ACE having deny for L4 port number in Thor |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
L4 ACL is applied, and few of the IPV6 packets with extension header MOBILITY are getting leaked though all the packets are hitting the applied ACE in THOR card alone.
Condition:
This issue is seen only when EH header is selected as MOBILITY( EH with other type has no problem) and next ACE is IPv6 permit any any. In other condition this issue is not observed.
Workaround:
The immediate ACE IPv6 permit any any should be taken out.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.28i.BASE, 4.2.4, 4.3.0, 4.3.0.19i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua79845 | Title: | DHCPv4 Standalone Bindings Stuck Selecting (Missing REQUESTs) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"show dhcp ipv4 proxy binding summary" shows persistent count of bindings in SELECTING state
Conditions:
The root cause of this condition is not well understood, but it appears to involve problems with DHCP-installed ARP entries.
Workaround:
Unfortunately, there is no way to clear DHCP-installed ARP entries from the CLI.
An alternative, though cumbersome, workaround exists. Periodically collect all of the MAC addresses of the bindings stuck in SELECTING state ("show dhcp ipv4 proxy binding | include SELECTING") and then manually clear all of those bindings ("clear dhcp ipv4 proxy binding mac-address ".
A production SMU is in the works to automatically clear DHCP-installed ARP entries when processing a repeated DISCOVER.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.2.3.23i.FWDG, 4.3.0, 4.3.0.23i.FWDG, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.0.1.99i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub18407 | Title: | fantray OIR causes stuck alarm and speed increment on all fans |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
after a fan fault is detected and later on fixed, the alarm stays active.
Furthermore the RPM of the fans does not decrease after the fault is cleared.
Conditions:
none
Workaround:
execute "process restart envmon"
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.2.1.K9SEC, 4.3.0.BASE |
|
Known Fixed Releases: * | 4.2.3, 4.2.3.28i.BASE, 4.2.4, 4.3.0, 4.3.0.25i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux52309 | Title: | fib_mgr Traceback seen after RSP FO in MERIT |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
fib_mgr Traceback would be seen on Typhoon LC occasionally with RSP fail over.
Conditions:
fib_mgr Traceback would be seen on Typhoon LC occasionally with RSP fail over. The issue is not reproducible easily with 1 RSP fail-over. It is seen with series of trigger events.
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu94675 | Title: | ASR-9001 under 5.3.0 fib_mgr multiple crashes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
fib_mgr crash
Conditions:
5.2.4 or 5.3.0 release
and subscriber session configuration
Platform update failure related to subscriber session happens before.
Workaround:
unknown yet
Further Problem Description:
Another bug is the direct cause to the crash. This fix is to address why code was executing in an error path.
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.3.0.FWDG |
|
Known Fixed Releases: | 5.3.2.18i.FWDG, 5.3.3.3i.FWDG, 6.0.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv54221 | Title: | Access Ports RED LEDs always glowing even in SHUT DOWN state |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Access Ports RED LEDs always glowing even in SHUT DOWN state
Conditions:
when the access ports led are in shut down mode , the ports leds are glowing red.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 6.0(0) |
|
Known Fixed Releases: * | 15.1(3)SVI02 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux60607 | Title: | eXR: CBC-1 on RP0 stuck in 49% UPGD during fpd upgrade |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
CBC-1 on RP0 stuck in 49% UPGD during fpd upgrade
Conditions:
Execute "upgrade hw loc all fpd all force" on a 9922 router to upgrade FPDs.
Workaround:
Uknown.
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv55938 | Title: | 9000v Silently Crashes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
9000v Silently Crashes.
Conditions:
Not known
Workaround:
Not needed , As SAT recovered after the Crash.
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.4(0) |
|
Known Fixed Releases: * | 15.1(3)SVI02 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux61790 | Title: | HSRP/VRRP virtual mac stuck in reserving state |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
The issue is that when the RP comes up (post reload or ISSU), the interface (on which HSRP is configured) comes up after HSRP is initialized. Before the interface comes up, the VMAC goes into reserving state trying to unsuccessfully set VMAC in the interface which does not exist still and stays there even when the interface comes up.
Conditions:
- Generally observed after reload or ISSU
- Applies to HSRP & VRRP
Workaround:
All we need is an extra configuration of 'delay minimum reload ' to a void this issue.
Further Problem Description:
N/A
|
|
Last Modified: | 19-DEC-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux53896 | Title: | qos_ma_ea process crash when modifying ACL |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When modifying ACL applied to PWHE and Bundle BNG subsribers, PWHE qos removal procedures are applied on bundle subscribers causing an inconsistency in database. qos_ma_ea process crashes do to this inconsistency and break QoS.
Conditions:
BNG Subscribers connecting via Bundle and PWHE and modifying ACL applied to subscribers.
Workaround:
Once in problem state, router reload is required to fix QoS.
Further Problem Description:
RCA Provided by DE
There was bug in the code. The bug gets exposed only when we have PWHE and Bundle subscribers. The bug is that it was trying to apply PWHE qos removal (hardware programming removal) on bundle subscribers. So, this was causing inconsistent database issue in the code and qos_ma_ea was crashing. The below debug logs I collected helped to confirm this problem.
LC/0/0/CPU0:Dec 11 13:07:30.476 CET: qos_ma_ea[324]: caps_remove_pwhe_sub_int - get the pwhe if_qos from the SPI hash instance_id: 0x1 ul_id: 128
LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: qos_ea_pwhe_db_search - entry pwhe_ifh 0x10e0 dir 1
LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: qos_ea_pwhe_db_hash - entry
LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: qos_ea_pwhe_db_search - Returning 0x0
LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: caps_remove_pwhe_sub_int - NULL PWHE DB
LC/0/0/CPU0:Dec 11 13:07:30.477 CET: qos_ma_ea[324]: verify_best_effort_cleanup - Internal error. Restarting to recover....
The ifhandle I have highlighted is a bundle subscriber. But as you see the APIs, we are tryign to remove the PWHE qos programming on this subscriber, which never was programmed. So, this resulted the inconsisteny and qos_ma_ea was getting restarted to remove this inconsistency.
The bug was exposed only when PWHE subscribers were procssed first and then bundle subscribers are processed. On my setup where I tried to repro this issue with same config, it was not happening. This is because, on my setup, bundle subscribers were processed first and then PWHE subscribers. So, when I applied this behaviour in the code, I found that we have a variable which gets set when PWHE subscriber is processed. This is supposed to be reset after all PWHE subscribers are processed. But, it was never getting reset. So, even when bundle subscribers are processed, this flag was still TRUE and we are applying PWHE procedures on this bundle subscriber as well which is wrong.
So, the fix is to reset this flag to FALSE when all PWHE subscribers are procssed. So, when we start to process the bundle subscribers, only bundle specifc actions are done. This solved the inconsistency issue and hence no crash.
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux61065 | Title: | ASR-9001/4.3.4 bfd flaps upon MPA OIR |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
bfd session flap
Conditions:
MPA OIR
Workaround:
unknown yet
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 4.3.4.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw51592 | Title: | NP4c driver version 12.46a build 4 throttle 4 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
All customer visible changes in this NP driver commit are described under the release notes for these two fixes:
CSCuw08309 - Update handling for Typhoon and Tomahawk NP soft errors
CSCut08813 - Suppress interrupts after large numbers of recoverable ECC errors
Conditions:
Not applicable, refer to the release notes for these two fixes:
CSCuw08309 - Update handling for Typhoon and Tomahawk NP soft errors
CSCut08813 - Suppress interrupts after large numbers of recoverable ECC errors
Workaround:
Not applicable, refer to the release notes for these two fixes:
CSCuw08309 - Update handling for Typhoon and Tomahawk NP soft errors
CSCut08813 - Suppress interrupts after large numbers of recoverable ECC errors
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.3.13i.BASE, 6.0.0.18i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux46405 | Title: | L3/L2VPN over Static/SR with SRTE AA: cef unresolved |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
L3/L2VPN over Static SR cef remains unresolved when another SRTE AA (Autoroute Announce) to same NH destination also presents
Conditions:
XR 6.0.0
Workaround:
Remove AA from SRTE which is to same NH destination
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux64831 | Title: | OSPF command to check the down interfaces configured in ASR9K |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Down interface are not coming using the command show (ospf | ospf3) interface
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 5.1.3.ADMIN |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01391 | Title: | ASR9k Wrong bfd echo latency counter |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Wrong values in output. - cosmetic
Symptom:
#show bfd session agent detail interface location
The latency value is calculated in wrong way.
Desired echo tx interval: 300 ms, local negotiated echo tx interval: 300 ms
Latency of echo packets (time between tx and rx):
Number of packets: 2, min=2 ms, max=302 ms, avg=152 ms
Conditions:
BFD on BOB:
bfd
multipath include location 0/4/CPU0
interface TenGigE0/4/0/3
bundle id 13 mode active
interface Bundle-Ether13
bfd address-family ipv4 multiplier 3
bfd address-family ipv4 destination 1.1.1.2
bfd address-family ipv4 fast-detect
bfd address-family ipv4 minimum-interval 50
ipv4 address 1.1.1.1 255.255.255.252
Workaround:
none
Further Problem Description:
Currently the for BOB Echo packets the SeqNum associated with packet is not being considered while updating timestamp table hence the confusion happens.
This needs correction in finding correct tx/rx packet and update the timestamp table, which can help in getting proper latency for BOB echo packets.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux45006 | Title: | eXR: IPU FPDs on fabric card stuck in "RLOAD REQ" after upgrade |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
IPU FPDs on fabric card stuck in "RLOAD REQ" after upgrade.
Conditions:
Triggered fallback to Golden version during IPU-FPGA upgrade on the fabric card.
After recovering IPU-FPGA to normal version, performed IPU-Linux upgrade on
the fabric card.
Workaround:
restart fpd_agent process
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCus00717 | Title: | SSTE: SYSDB-SYSDB-6-TIMEOUT_EDM FB SMU test. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Syslogs gets printed.
RP/0/RSP0/CPU0:Nov 23 13:15:12.963 EST: sysdb_shared_nc[421]: %SYSDB-SYSDB-6-TIMEOUT_EDM : EDM request for 'oper/tty/gl/________/________/vty/10/stats/conn-out/' from 'exec' (jid 65918, node 0/RSP0/CPU0). No response from 'exec' (jid 65918, node 0/RSP0/CPU0) within the timeout period (100 seconds)
Conditions:
The key to trigger timeout seems to be stressing the process exec
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | 5.3.2.8i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux52913 | Title: | IPv6 prefix over IPv4 SRTE via static route: no cef entry on LC |
|
Status: | Open |
|
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: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0.0.FWDG |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux18986 | Title: | Implement the change to honor RESV message from MP during FRR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
There is discrepancy between control plane and forwarding plane
Conditions:
when downstream router updates with same LSP ID.
Workaround:
re-opt at headend fixes the issue
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 5.2.2.MPLS |
|
Known Fixed Releases: * | 5.3.3.24i.MPLS |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux66146 | Title: | ASR9001 Memory Exhaustion due to ipsec_pp process |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR9001 reports memory exhaustion due to ipsec_pp process
Conditions:
Problem was seen on ASR9001 running 5.1.3 + service pack 2
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux66283 | Title: | fib_mgr tracaback caused by Bundle member flap |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
fib_mgr traceback followed by fib reset
Conditions:
bundle-member interface flaps
Workaround:
n/a
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux49788 | Title: | 9000v issues with Cisco SFP GLC-T at A-FULL 100 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
When we have two copper SFPs connected, one 100M capable and the other 1G capable, and Auto negotiation enabled on both sides, if the interface goes down due to some reason, it will not come up.
Conditions:
Two copper SFPs connected to each other, one 100M capable and the other 1G capable, and auto negotiation enable on both sides.
Workaround:
Reapplying auto negotiation or satellite reload.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: * | 6.1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23172 | Title: | CPAK OIR and PCIE link flap causing DB Recovery to fail |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Interfaces do not come up with CPAK oir when PCIE link flap happens.
User may see the below error messages in show logging during CPAK OIR.
LC/0/1/CPU0:Oct 4 20:38:13.371 : pciesvr[75]: %PLATFORM-PCIE-1-ERROR : B/D/F 0/1/0 dev name:IB 1a & 1b: AER| UES: 0x00004000 CES: 0x00000000 RES: 0x00000024 IDS: 0x00080a00| HDRS: 0x00000000 0x00000000 0x00000000 0x00000000
Conditions:
Both CPAK oir and PCIE link flap should happen at the same time.
Workaround:
reload Linecard
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut59078 | Title: | parser_server crash when using tab-key or help ? in "interface-range" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
parser_server crash seen when using tab key or help ? in interface-range CLI
Conditions:
parser_server crash seen when using tab key or help ? in interface-range CLI
Workaround:
1. connect to active RSP on AUX port.
2. issue "sysmgr_control -r parser_server".
Further Problem Description:
N/A
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.2.21i.BASE, 5.3.3.6i.BASE, 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux65064 | Title: | Installation of SP1 on 5.3.2 prevents subscriber to be authorised |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
After installing or removing SP1 on version 5.3.2 subscriber cannot be authorised.
Conditions:
Version 5.3.2 installed and SP1 installed or removed
Workaround:
Reload the ASR9k again or restart Radiusd.
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu90459 | Title: | Dynamic Route Leaking issue in Global table |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Issue with way vrf route is leaked to global table causing routing issues.
Conditions:
When route is leaked to global table, route shows "directly connected, via ServiceApp'x'". The serviceapp interface is the next-hop for vrf default route. When this condition exists, customer is unable to ping public DNS from within VRF sourcing address on leaked subnet.
Workaround:
Customer workaround was to statically route the leaked prefix to null within the VRF, and refresh the vrf routing table.
Further Problem Description:
Customer is leaking "Public" services into VRF and "CGN Pools" to global table. The suspect node learns the Public prefixs via OSFP. In order to dynamically leak into VRF, customer redistributes public pools into BGP. They import into vrf from default using RP that allows public prefixes. Customer has a /17 allocated for CGN Pools. They have created a loopback in the vrf within that subnet for testing. There are other nodes advertising /24's of the CGN Pool via iBGP. Therefore in order for suspect node to advertise the /17, they do so by configuring aggregate-address under vrf bgp config. They then export /17 to default under vrf config using a RP.
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.3.15i.ROUT, 6.0.0.11i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut67904 | Title: | 524-11I bgp traceback at bgp_rib_table_close on standby RP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
bgp traceback is seen on removing and adding bgp vrf config , there is no funcitonal impact
Conditions:
Workaround:
no work around
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.4.ROUT |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.2.5i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw94757 | Title: | BGP bumps net version when L2VPN Mgr replays VPLS nlri |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
BGP VPLS/VPWS net version is bumped when L2VPN Mgr. is restarted or on RP switchover.
Unless router has high VPLS/VPWS bridge-domain configuration this does not have impact. However during high VPLS/VPWS bridge-domain scale this can result in momentary higher CPU utilization.
Conditions:
Requires VPLS/VPWS configuration. and L2VPN Mgr. process is restarted or RP switchover is initiated.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.3.ROUT |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.3.18i.ROUT, 6.0.0.23i.ROUT, 6.1.0.7i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw26572 | Title: | loopback IP is not coming under the BGP table when ASR9K is reloaded. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Connected routes corresponding to Loopback interfaces i.e. /32 or /128
prefixes are not redistributed into BGP sometimes.
Conditions:
Loopback interfaces are configured under OSPF protocol.
BGP config has "redistribute connected route-policy <>" and
"redistribute ospf route-policy <>" statements. The Connected
redistribution route-policy allows the prefix while OSPF redistribution
route-policy drops the prefix.
Workaround:
Avoid configuration mentioned in "Conditions" section above.
Further Problem Description:
In order to recover, remove "redistribute connected route-policy <>"
configuration and re-apply the same configuration.
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 4.2.3.ROUT, 5.1.3.ROUT |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.3.18i.ROUT, 6.0.0.23i.ROUT, 6.1.0.6i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug20137 | Title: | radiusd: %OS-DATACORRUPTION-1-DATAINCONSISTENCY : copy error |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
While bringing up fresh IPOE sessions over LC , observing the following tracebacks in 511 2i Image .
But sessions came up fine.
LC/0/1/CPU0:Jul 30 15:10:11.897 : radiusd[320]: %OS-DATACORRUPTION-1-DATAINCONSISTENCY : copy error : pkg/bin/radiusd : (PID=524464) : -Traceback= 4efbb404 4bacc38c 40015a4c 40016190 40011348 4001209c 40018d34 4e61c660 4e61bc40 4e615ca0 4e613cf4 4e61cba4 4e61fa58 4c545bf8 4c553ba8 4c54bfa0
First noticed the trace backs upon first time bring up of sessions after reload.
No errors seen on second /futher attempts.
Then observed the same trace backs while bringing up sessions after LC OIR.
Conditions:
N/A
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 31-DEC-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 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, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux48875 | Title: | Sureshot EDVT: 1NP LC Reports Link Status Error for Depopulated NP |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Link Status message reported on LC console
Conditions:
LC booted into IOS XR RUN
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 10-DEC-2015 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf63251 | Title: | Avago SFP-GE-S module flapping when working with A9K-MPA-20X1GE |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Interface flapping with %PLATFORM-SFP-2-LOW_LASER_BIAS_ALARM error message.
Conditions:
When SFP is made by AVAGO and the card is A9K-MPA-20X1GE.
Workaround:
Use SFP made by Finisar.
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.2, 4.3.2.17i.BASE, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.0.7i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux31279 | Title: | Firestorm stuck in connecting state after tcp process crash on satellite |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
On doing a process crash of tcp process on the firestorm satellite, it is seen that the satellite gets stuck in connecting state on the host and does not recover.
Conditions:
RP/0/RP0/CPU0:Sat200#sh sdac internal trace control adapter reverse
Wed Nov 25 04:31:18.007 UTC
10366 wrapping entries (20608 possible, 10624 allocated, 0 filtered, 24767544 total)
Nov 25 04:31:18.366 nvsat-ctrl-fast 0/RP0/CPU0 816# t4377 [nvsat-ctrl-tcp:0410] Error accepting connection on listen fd 180: Bad file descriptor
Nov 25 04:31:18.366 nvsat-ctrl-fast 0/RP0/CPU0 t4377 [nvsat-ctrl-tcp:0410] Error accepting connection on listen fd 180: Bad file descriptor
Nov 25 04:31:18.366 nvsat-ctrl-fast 0/RP0/CPU0 t4377 [nvsat-ctrl-tcp:0410] Error accepting connection on listen fd 180: Bad file descriptor
Nov 25 04:31:18.365 nvsat-ctrl-fast 0/RP0/CPU0 814# t4377 [nvsat-ctrl-tcp:0410] Error accepting connection on listen fd 180: Bad file descriptor
Nov 25 04:31:18.365 nvsat-ctrl-fast 0/RP0/CPU0 t4377 [nvsat-ctrl-tcp:0410] Error accepting connection on listen fd 180: Bad file descriptor
Workaround:
reload the satellite to recover from this issue
Further Problem Description:
none
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE, 6.1.0.BASE |
|
Known Fixed Releases: | 6.1.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup53020 | Title: | [HQoS]:bandwidth config on "qos-group 3" does not return proper err info |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
In Qos, Bandwidth configuration on "qos-group 3" is not returning proper error message to host.
Conditions:
On "qos-group 3" match criteria, only the priority action is supported under policymap.
But, configuring bandwidth on "Qos-group 3" is not returning proper error message to host, even configuration is failed.
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 5.1(2) |
|
Known Fixed Releases: * | 15.1(3)SVI02 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur97036 | Title: | clear bgp ipv6 unicast <> is not working |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
RP/0/RSP0/CPU0:PHLASR2#clear bgp ipv6 unicast cafe:1890:c07:940::bece:ce
Tue Dec 2 10:22:53.765 EST
% 'sysdb' detected the 'warning' condition 'A SysDB client passed a path for an item where a directory path was expected, or vice versa, or a path containing incorrectly placed '/' or reserved characters'
RP/0/RSP0/CPU0:PHLASR2#clear bgp 10.154.37.2
Tue Dec 2 10:23:35.652 EST
RP/0/RSP0/CPU0:Dec 2 10:23:35.728 : bgp[1052]: %ROUTING-BGP-5-ADJCHANGE : neighbor 10.154.37.2 Down - User clear requested (CEASE notification sent - administrative reset) (VRF: default) (AS: 104)
RP/0/RSP0/CPU0:PHLASR2#RP/0/RSP1/CPU0:Dec 2 10:23:35.728 : bgp[1052]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor 10.154.37.2 on standby RP due to User clear requested (VRF: default)
RP/0/RSP0/CPU0:Dec 2 10:24:11.214 : bgp[1052]: %ROUTING-BGP-5-ADJCHANGE : neighbor 10.154.37.2 Up (VRF: default) (AS: 104)
RP/0/RSP0/CPU0:PHLASR2#
RP/0/RSP0/CPU0:PHLASR2#clear bgp ipv6 unicast ?
* Clear all peers and all routes from the BGP table
A.B.C.D or X:X::X BGP neighbor address to clear
as Clear peers in a specific AS
dampening Clear route flap dampening information
external Clear all external peers
flap-statistics Clear flap statistics
nexthop Clear nexthop
self-originated Clear redistributed, network and aggregate routes originated here
shutdown Clear all peers which were shut down due to low memory
update Clear Update information (Do NOT execute without cisco support)(cisco-support)
RP/0/RSP0/CPU0:PHLASR2#clear bgp ipv6 unicast cafe:1890:c07:150d::beea:ea ?
long-lived-stale Clear long-lived-stale routes
soft Soft reconfig
Conditions:
every time
Workaround:
use soft
Further Problem Description:
minor issue
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 5.3.0.ROUT |
|
Known Fixed Releases: * | 5.3.3.22i.ROUT, 6.1.0.2i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu50793 | Title: | Umbrella for MPLS traceroute fixes on A9K-SIP-700 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
This is an umbrella for the following fixes required for MPLS traceroute to work properly on A9K-SIP-700:
CSCun11455 [asr9k-thor-fwding] Need changes in cpp ucode to send eng type for punt pkt.
CSCut82797 [asr9k-thor-fwding] Maintain MPLS<->MPLS TTL propagation when IP<->MPLS TTL prop is disabled
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39322 | Title: | FIB vs LFIB is not matching after link is recovered with BGP PIC edge. |
|
Status: | Terminated |
|
Severity: | 4 Minor |
Description: * | Symptom:
On a ASR9k/5.2.4 there is timming delay between FIB vs LFIB tables. When the FIB has changed the next-hop the LFIB not change after the failure is recovered, waiting for around 3 minutes the LFIB is updated.
Using BGP PIC edge the primary route is eBGP and back route is iBGP.
HW is RSP440/RSP-8G + Typhoon Linecards
following steps:
1.- SHUT on remote PE_1
2.- wait 10 or 20 seconds
3.- Validate the BGP PIC changed to backup path, FIB and LFIB tables on local PE_A
4.- NO-SHUT on remote PE_1
5.- Validate the BGP PIC changes to primary path on this step the FIB and LFIB are mismatch. FIB point the primary path while LFIB point to backup path on PE_A
Conditions:
none
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw49484 | Title: * | Voltage marginal value modification |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Comparing "show environment table" and "show environment", voltage sensors show out of range but actually they have no impact.
Conditions:
Workaround:
under investigation
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux30405 | Title: | Improve handling of Layer1 cache parity issues on Typhoon linecards. |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
This ddts is to see how we can improve parity errors seen in the L1 cache on the PPC P4040 cpu of the typhoon linecards. The L1 errors would be seen as DCPERR and ICPERR.
Conditions:
Specific conditions which cause the L1 errors are unknown and extremely rare.
Workaround:
None. Card reload occurs.
So far, there is no occurrence of a card encountering another L1 error subsequently.
Further Problem Description:
We have been unable to reproduce the L1 issue.
Because it shares the same P4040 processor, A9001 is also susceptible to L1 issue - However, there are no reports of L1 issue with A9001 (aka Ironman).
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 5.3.3.LC |
|
Known Fixed Releases: | 5.3.3.21i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul03873 | Title: | NPH Changes to add support for FGID/MGID expansion for Thor |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | It is an Enhancement.
Symptom:
NA
Conditions:
The NPH changes required from 5.2.0 onwards for an interoperability with other asr9k linecards.
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt45587 | Title: | mVPN THOR drop mcast fragment on decap PE |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
mVPN THOR drop mcast fragment on decap PE
Conditions:
Workaround:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 4.0.1.BASE, 4.2.0.BASE |
|
Known Fixed Releases: | 4.2.1.15i.BASE, 4.3.0.2i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup44799 | Title: | ASR9k BNG-Suppress local ARP entries for each IPoE subscriber interface |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
On an ASR9k acting as a BNG aggregating IPoE subscribers, a local ARP entry is added for each spawned IPoE subscriber interface, for each local IP address on the associated unnumbered subscriber loopback, contributing to ARP scale limitations:
RP/0/RSP0/CPU0:ASR9010-C#sh arp | i Bundle-Ether333.210.ip2
Tue Jun 17 21:08:50.043 UTC
10.1.1.1 - 8478.ac2e.1eb6 Interface ARPA Bundle-Ether333.210.ip2
10.2.2.1 - 8478.ac2e.1eb6 Interface ARPA Bundle-Ether333.210.ip2
10.3.3.1 - 8478.ac2e.1eb6 Interface ARPA Bundle-Ether333.210.ip2
10.4.4.1 - 8478.ac2e.1eb6 Interface ARPA Bundle-Ether333.210.ip2
10.5.5.1 - 8478.ac2e.1eb6 Interface ARPA Bundle-Ether333.210.ip2
interface Loopback64
ipv4 address 10.1.1.1 255.255.255.0
ipv4 address 10.2.2.1 255.255.255.0 secondary
ipv4 address 10.3.3.1 255.255.255.0 secondary
ipv4 address 10.4.4.1 255.255.255.0 secondary
ipv4 address 10.5.5.1 255.255.255.0 secondary
Conditions:
This is behavior is present in IOS-XR through 4.3.4 and 5.1.2 for ASR 9000s acting as a BNG aggregating IPoE subscribers.
Workaround:
There is no current way to suppress the local ARP entries for IPoE subscriber interfaces.
Further Problem Description:
This optimisation introduces a new configuration command: "subscriber arp scale-mode-enable". This command disables the creation of local ARP entries associated with subscriber interface. ARP operation remains unchanged, i.e. ARP replies received on subscriber interfaces are responded to; proxy ARP operation also remains unchanged.
|
|
Last Modified: | 14-DEC-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: | 5.3.3.18i.FWDG, 6.0.0.26i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug56191 | Title: | EP OIR on rack np0 brings IRL on other np down |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
EP-OIR on rack0 causes ports (which are up/up) on rack1 to go error disabled. The ports comes back (up/up) within seconds when EP OIR is complete.
Conditions:
EP-OIR on rack0 of ASR9001
Workaround:
No workaround.
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv94150 | Title: | eXR: No warning / log messages for interrupion in fpd upgrade |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
No warning / log messages for interrupion in fpd upgrade
Conditions:
When fpd upgrade is in progress, trigger reload on the board / power cycle on the router.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: * | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul22056 | Title: | DDTS to address all CRPG failures... |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
CRPG tool is not in a condition to run our test scripts and decided to fix those problems.
Conditions:
NA
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.0.5i.BASE |
|
|
| |
:
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论