| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw35268 | Title: | XR: IPSLA enhanced aggregated command show output empty |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
"show ipsla statistics enhanced aggregated" command output is empty after device uptime is longer than 49 days, while "show ipsla statistics" command is working fine.
After enabling "debug sysdb access" similar error will be visible:
RP/0/RSP0/CPU0:Sep 7 07:48:24.166 UTC: sysdb_shared_nc[421]: (Req Id:4491276) EDM request - error 0x40828600 ('sysdb' detected the 'warning' condition 'A verifier or EDM callback function returned: 'not found'') returned to process 'show_ipsla_stats' (65886, 0/RSP0/CPU0, 1)
Conditions:
IOS XR 4.3.0+ with the system uptime longer that 49 days
ipsla configured with "statistics interval" for enhanced statistics
Workaround:
Process restart will not recover this situation of "show ipsla statistics enhanced aggregated" not working. However one could use "show ipsla statistics" (which works fine) at regular intervals and use one's own logic to aggregate the statistics over time (if needed).
Further Problem Description:
Issue is related to the bag pointer value in the sysdb - when value exceed 32bit, command will stop working.
|
|
Last Modified: | 26-OCT-2015 |
|
Known Affected Releases: | 5.1.3.MGBL |
|
Known Fixed Releases: | 6.1.0.2i.MGBL |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv93355 | Title: | [600]-commit failure with lpts pifib configs |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
commit failure occurs while performing lpts configuration
Conditions:
While configuring lpts pifib hardware police on icmp
Workaround:
N/A
Further Problem Description:
NA
|
|
Last Modified: | 03-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.0.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus37426 | Title: | DUI 5.3.1.20I syncctrl crashes after long run (about 5 days) |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | $$PREFCS
Symptom:
syncctrl process crashes during RSP failover.
Conditions:
Issue is typically seen on RSP failover. Issue is not seen on every RSP failover. Exact frequency is unknown. Issue was reported on two different TBs.
Workaround:
System recovers automatically. No manual intervention needed.
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 5.3.0.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo13873 | Title: | Packets to aggregate label dropped on RSV_DROP_IPV4_RXADJ_DROP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
MPLS VPN traffic to aggregate label (vrf loopback or connected CE networks)
is either dropped on NP counter RSV_DROP_IPV4_RXADJ_DROP
or is showing high round-trip delay (> 1 sec).
Conditions:
ASR9K MPLS VPN PE running 5.1.1.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.1.1.MPLS |
|
Known Fixed Releases: * | 5.1.2.SP1, 5.1.2.SP2, 5.1.2.SP3, 5.1.2.SP4, 5.1.3, 5.1.3.8i.BASE, 5.1.3.8i.FWDG, 5.1.4, 5.2.0.26i.BASE, 5.2.0.26i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw57643 | Title: | icpe_satmgr crashed multiple time with 180 simualted satellite session |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
icpe_satmgr crash
Conditions:
session bring-up with 180 simualted satellite
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 26-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.0.20i.FWDG, 6.1.0.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq70322 | Title: | openflow: of_agent crash with flow delete with scale |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
of_agent process crashed with flow delete followed by deleting the switch with scale.
Conditions:
Scale flows.
Workaround:
NOne
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.2.4.2i.BASE, 5.3.0, 5.3.0.18i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq14174 | Title: | MTU not correct on satellite side of ICL |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After setting up a satellite on 5.1.2, frames over 1514 bytes (XR MTU calculation) are not being passed to the satellite host ports when MTU is set higher than that.
Conditions:
Running satellite on 5.1.2 with MTU higher than 1514.
Workaround:
Unconfigure the MTU on the host port and reconfigure it
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 5.1(2) |
|
Known Fixed Releases: * | 15.1(3)SVG03, 15.1(3)SVG03a, 15.1(3)SVH02 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu62944 | Title: | sysdb_mc crash with SMU CSCuq13793 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
With the SMU CSCuq13793 activated there is an issue seen on occasion with SSH connections getting closed that can cause sysdb_mc to crash.
Conditions:
Have SMU for CSCuq13793 activated and use SSH.
Workaround:
Further Problem Description:
The crash is not service impacting.
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: * | 4.3.4.BASE |
|
Known Fixed Releases: | 5.3.3.10i.BASE, 5.3.3.15i.BASE, 6.0.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo31977 | Title: | CPP Driver LOCKDOWN & LC reload with control word deletion on remote PE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:SIP-700 CPP lockdown and continuous LC reload
Conditions:With MPLS Netflow applied on tail end PE core link, when Control word configuration is removed from tail and head end PE.
Workaround:LC reload stps after enable control word or remove the netflow configuration from the tail end PE.
More Info:Problem seen only with ethernet attachment circuit and onky with Netflow enabled
|
|
Last Modified: | 20-OCT-2015 |
|
Known Affected Releases: | 5.2.2.FWDG |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.16i.BASE, 5.1.3.18i.BASE, 5.1.4, 5.2.2, 5.2.2.11i.BASE, 5.2.21, 5.3.0, 5.3.0.1i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup67367 | Title: | ipv4_io process crash due to mem-leak in ip_best_local_src_addr function |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Tail drop on XIPC in regular intervals followed by ipv4_io process crash
Conditions:
This is seen on ASR9K running 4.3.4 & 5.2.2
Workaround:
NONE
Further Problem Description:
A slow memory leak to the process causes the ipv4_io to restart after the process hits the max memory.
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | 4.3.4.SP6, 4.3.4.SP7, 4.3.4.SP8, 5.2.2.17i.FWDG, 5.2.3.6i.FWDG, 5.3.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw08309 | Title: | Update handling for Typhoon and Tomahawk NP soft errors |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A Typhoon linecard is reloaded due to a non-recoverable error in TM_SC_L234 CLASS_WFQ/CLASS_IQD_WFQ memory. Here is an example of the error message:
LC/0/15/CPU0: prm_server_ty[321]: %PLATFORM-NP-3-ECC : prm_ser_check: Parity error detected: NP 0, block 0x2a (TM_SC_L234), offset 48, memid 452, name CLASS_WFQ/CLASS_IQD_WFQ, addr 0x000001cd, bit 2147483648, ext info 0xffffffff 0xffffffff 0xffffffff 0xffffffff, action 2 (Reset)
Conditions:
There is no particular trigger for this problem, but it is extremely rare. This problem is specific to Typhoon series linecards and the asr9001 chassis since it also uses Typhoon NPs.
This issue exists only in the 5.3.2 release.
Workaround:
There is no workaround, the linecard will be automatically reloaded after the problem occurs.
Further Problem Description:
This type of error should be correctable. If this type of error occurs when running an image with the fix for this bug, the memory will be corrected and the linecard will not be reloaded.
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw45876 | Title: | If ipv6 enable is not on Bundle for pppoe, bng will not send RA |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
If we do not have ipv6 enable on Bundle for PPPoE but we receive with RADIUS for subscriber or have it in dynamic template, RA will anyway not be sent from BNG.
Conditions:
in 4.3.4 if we do not have ipv6 enable on Bundle for PPPoE but we receive with RADIUS for subscriber or have it in dynamic template, RA will be sent from BNG.
in 5.2.4 if we do not have ipv6 enable on Bundle for PPPoE but we receive with RADIUS for subscriber or have it in dynamic template, RA will anyway not be sent from BNG.
Workaround:
enable ipv6 enable on Bundel interface.
Further Problem Description:
|
|
Last Modified: | 14-OCT-2015 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug52780 | Title: | session keeps connected after application got killed |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
onep session might keep as connected after application got killed.
Conditions:
start two sessions connected from the same server. After killing one application on the server, both sessions are still up.
Workaround:
reset sessions on the server
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.10i.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.2i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuu18246 | Title: | Implement serdes auto tuning for host lanes on Tomahawk cards |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:CRC errors observed on the epm-switch port connected to an NP.
Conditions:Observed on the 3rd generation of ASR9000 ethernet line cards (Tomahawk).
Workaround:There are no workarounds.
More Info:epm-switch is on the control path between NP and LC CPU.
|
|
Last Modified: | 11-OCT-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | 5.3.2, 5.3.2.7i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw24731 | Title: | 5.3.0 : Bundle-ethernet flaps causes CEF corruption |
|
Status: | Open |
|
Severity: * | 2 Severe |
Description: | Symptom:
Bundle Interface on ASR9k node migrated from one device to other brought BGP down and other traffic down
Conditions:
Bundle interface with IPv4 and IPv6 BGP neighbor
Workaround:
No Workaround
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun90460 | Title: | SSTE: Observing router lisp commands are not getting accepted |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Router lisp config is not accepted
Conditions:
sysdb process is restarted on the router
Workaround:
process restart lisp
Further Problem Description:
|
|
Last Modified: | 03-OCT-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.7i.FWDG, 5.1.4, 5.2.0, 5.2.0.19i.FWDG, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv46259 | Title: | BGP crashed after RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms:
BGP process crashes sometimes inside malloc libary free call.
Conditions:
NSR is enabled and Standby RP is ready.
Recovery:
BGP process restarts by itself after the crash.
Workaround:
None
Further Problem Description:
The crash is due to memory corruption that happens
as part of reaching NSR ready state. The exact location
and time of crash is not predictable.
|
|
Last Modified: | 09-OCT-2015 |
|
Known Affected Releases: | 5.3.2.BASE, 5.3.2.ROUT, 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCur52935 | Title: | 530: continuos fib_mgr tracebacks from A9K-8x100GE-L-SE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | After running script for some 3-4 days on adjacent node for route churning observed below logs on TMHK card.
LC/0/8/CPU0:Nov 3 09:52:13.634 : fib_mgr[181]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_NHINFO[ptr=62b782f8,refc=0x1,flags=0x800008] Action=CREATE Proto=ipv4. Cerr='prm_server' detected the 'resource not available' condition 'lack of stats counters' : pkg/bin/fib_mgr : (PID=192622) : -Traceback= afdcd3b 429c1e2 42a2040 42a55f3 42aadb1 42abe7d 42f7e22 42f815b 42f92bf 420944a 82465d7 8244724 4201676 4213b2c 828a050
LC/0/8/CPU0:Nov 3 09:52:30.670 : fib_mgr[181]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_NHINFO[ptr=62b79b78,refc=0x1,flags=0x800008] Action=CREATE Proto=ipv4. Cerr='prm_server' detected the 'resource not available' condition 'lack of stats counters' : pkg/bin/fib_mgr : (PID=192622) : -Traceback= afdcd3b 429c1e2 42a2040 42a55f3 42aadb1 42abe7d 42f7e22 42f815b 42f92bf 420944a 82465d7 8244724 4201676 4213b2c 828a050
LC/0/8/CPU0:Nov 3 09:52:44.369 : pifibm_server_lc[290]: %OS-PLATFORM_LPTS_PIFIB-5-ERR_PRM_STATS_ALLOC : Failed to allocate HW counters.
LC/0/8/CPU0:Nov 3 09:52:45.682 : fib_mgr[181]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_NHINFO[ptr=62b79558,refc=0x1,flags=0x800008] Action=CREATE Proto=ipv4. Cerr='prm_server' detected the 'resource not available' condition 'lack of stats counters' : pkg/bin/fib_mgr : (PID=192622) : -Traceback= afdcd3b 429c1e2 42a2040 42a55f3 42aadb1 42abe7d 42f7e22 42f815b 42f92bf 420944a 82465d7 8244724 4201676 4213b2c 828a050
On similar terms route churn induce from TGN resulting below logs on VSM-500 card :-
LC/0/4/CPU0:Jun 17 21:25:57.687 : l2fib[259]: %OS-SHMWIN-2-ERROR_ENCOUNTERED : SHMWIN: Error encountered: System memory state is severe, please check the availability of the system memory
LC/0/4/CPU0:Jun 17 21:25:59.368 : fib_mgr[185]: %OS-SHMWIN-2-ERROR_ENCOUNTERED : SHMWIN: Error encountered: System memory state is severe, please check the availability of the system memory
LC/0/4/CPU0:Jun 17 21:26:25.121 : l2fib[259]: %OS-SHMWIN-2-ERROR_ENCOUNTERED : SHMWIN: Error encountered: System memory state is severe, please check the availability of the system memory
LC/0/4/CPU0:Jun 17 21:26:29.365 : fib_mgr[185]: %OS-SHMWIN-2-ERROR_ENCOUNTERED : SHMWIN: Error encountered: System memory state is severe, please check the availability of the system memory
LC/0/4/CPU0:Jun 17 21:26:53.257 : l2fib[259]: %OS-SHMWIN-2-ERROR_ENCOUNTERED : SHMWIN: Error encountered: System memory state is severe, please check the availability of the system memory
LC/0/4/CPU0:Jun 17 21:26:59.363 : fib_mgr[185]: %OS-SHMWIN-2-ERROR_ENCOUNTERED : SHMWIN: Error encountered: System memory state is severe, please check the availability of the system memory
Symptom:After running script for some 3-4 days on adjacent node for route churning observed below logs on TMHK card.
LC/0/8/CPU0:Nov 3 09:52:13.634 : fib_mgr[181]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_NHINFO[ptr=62b782f8,refc=0x1,flags=0x800008] Action=CREATE Proto=ipv4. Cerr='prm_server' detected the 'resource not available' condition 'lack of stats counters' : pkg/bin/fib_mgr : (PID=192622) : -Traceback= afdcd3b 429c1e2 42a2040 42a55f3 42aadb1 42abe7d 42f7e22 42f815b 42f92bf 420944a 82465d7 8244724 4201676 4213b2c 828a050
LC/0/8/CPU0:Nov 3 09:52:30.670 : fib_mgr[181]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=DATA_TYPE_NHINFO[ptr=62b79b78,refc=0x1,flags=0x800008] Action=CREATE Proto=ipv4. Cerr='prm_server' detected the 'resource not avai
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | 5.3.0.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv42985 | Title: | BGP crash on active RSP in 5.3.1 |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: * | Symptom:
BGP crash in active RSP
Conditions:
n/a
Workaround:
n/a
Further Problem Description:
n/a
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: | 5.3.1.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun74993 | Title: | SSTE: sync API causes crash if prefix to be removed isn't same |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When using the sync API (onep_routing_art_update_routes), if a prefix is ADDed with a specific next hop but then later the API is called to remove the prefix and the prefix has a different next hop, the onep_server process on the router will crash. This is not seen with the async API (onep_routing_art_update_routes_async). Example:
PREFIX ADDED: 99.2.1.0/24 [10/0], via 50.8.11.101, GigabitEthernet0/0/0/2
PREFIX REMOVED PREFIX: 99.2.1.0/24 [10/0], via 50.8.11.102, GigabitEthernet0/0/0/2
Conditions:
Onep Application exits with return code 6:
ERROR: (rc = 6) internal system error: socket error during receive
Workaround:
Use the async API (onep_routing_art_update_routes_async)
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.2.0.BASE, 5.2.0.ROUT |
|
Known Fixed Releases: * | 5.2.0, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw44751 | Title: | [ATT 532] IPv6 LI intercept sending more than requested IP range |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
LI Functionality is Broken for /126 Prefix
Issue is Lawful Intercept Functionality, its taping more prefixes which it supposed to tap. It is like a security breach.
With the /126 we should would expect to capture only packets with the
following addresses:
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
But it is tap all the addresses
caf????:1890:8a9d:9800:0:0:11b7:4
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
:
:
:
caf????:1890:8a9d:9800:0:0:11b7:f
Conditions:
every time
Workaround:
no workaround
Further Problem Description:
Issue is Lawful Intercept Functionality, its taping more prefixes which it supposed to tap. It is like a security breach.
With the /126 we should would expect to capture only packets with the
following addresses:
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
But it is tap all the addresses
caf????:1890:8a9d:9800:0:0:11b7:4
caf????:1890:8a9d:9800:0:0:11b7:5
caf????:1890:8a9d:9800:0:0:11b7:6
caf????:1890:8a9d:9800:0:0:11b7:7
caf????:1890:8a9d:9800:0:0:11b7:8
caf????:1890:8a9d:9800:0:0:11b7:9
caf????:1890:8a9d:9800:0:0:11b7:a
caf????:1890:8a9d:9800:0:0:11b7:b
caf????:1890:8a9d:9800:0:0:11b7:c
caf????:1890:8a9d:9800:0:0:11b7:d
caf????:1890:8a9d:9800:0:0:11b7:e
:
:
caf????:1890:8a9d:9800:0:0:11b7:f
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.13i.BASE, 6.0.0.19i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui58840 | Title: | PIM Entry not refresh and delete entry when MC Source is not available. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
For one or more S,G routes, the route remains in the PIM topology, mrib route and mfib route show command output after the keepalive timer has expired.
Conditions:
1) Router is the *,G LH router for the route on on of its networks - local reciever is present on the network
2) Router became PIM assert winner on that network because another router forwarded onto that network
Workaround:
None
Further Problem Description:
This problem should rarely occur. There is a very small window of time where two routers might both elect themselves PIM DR on a network after an interface DOWN->UP transition and thus forward to a local receiver. The route will be removed if the local receiver leaves the group. The possible negative impact to a customer is if they have a large scale then this might cause them to eventually reach the out of resource limit on routes in PIM.
|
|
Last Modified: | 19-OCT-2015 |
|
Known Affected Releases: * | 4.2.1.MCAST |
|
Known Fixed Releases: | 4.3.4.13i.MCAST, 5.1.1.8i.MCAST, 5.1.11.4i.MCAST, 5.1.2.1i.MCAST, 5.2.0.2i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup10276 | Title: | pim crashd pim_mvrf_mdt_cache,on 4.3.2 iox asr9k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PIM crash
Conditions:
PIM crash can happen when downstream PE is tracking assert winner on mdt interface and there are multiple upstream PE announcing data mdt TLVs.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 19-OCT-2015 |
|
Known Affected Releases: * | 4.3.0.MCAST, 4.3.2.ROUT, 4.3.3.BASE |
|
Known Fixed Releases: | 5.1.3, 5.1.3.14i.MCAST, 5.1.4, 5.2.2, 5.2.2.14i.MCAST, 5.2.21, 5.3.0, 5.3.0.1i.MCAST, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur09680 | Title: | cfgmgr-rp traceback seen when doing rollback config last 1 |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | $$PREFCS
Symptom:
cfgmgr-rp traceback seen
Conditions:
seen after rollback config last 1
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv12614 | Title: | PW-HE egress shaper is not getting executed when LFA Backup path exist |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Egress QoS like Shaping, Marking, etc on PW-HE main (or it's subinterfaces) is not effective on ASR9K
Conditions:
The LFA paths are part of the Generic interface list associated with the PW-HE interface.
The pin down interface is the Primary for the LFA paths.
The affected IOS-XR versions are:
5.1.1
5.1.2
5.1.3
5.2.0
5.2.1
5.2.2
5.2.4
5.3.0
5.3.1
Workaround:
remove LFA FRR or change metric to force PW-HE as calculating node not having LFA,rLFA backup path
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 5.1.3.FWDG |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.19i.BASE, 5.3.3.5i.BASE, 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw60002 | Title: | ASR9k Cluster: Incorrect remote rack slotmask for loopback with IC flag |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
L3 Multicast IPv4 Auto-RP mapping information not populated on an ASR9k in cluster configuration
Conditions:
This issue occurs under the following conditions:
- ASR9k in cluster configuration
- Mhost default interface is picked as Loopback interface (Loopback interface has IC flag set in 224.0.1.40 route)
- RPF interface of (S,G) entries for group 224.0.1.40 is on Rack 1
- L3 Multicast configuration and routes come up before IRL links are configured/active
Workaround:
To prevent this issue from happening, when deploying a new cluster enable the IRL links and make sure they are Up and active before enabling multicast configuration.
If the issue has already occured, the following workaround can be used:
Workaround involves toggling the IC flag on the Loopback interface associated with the the 224.0.1.40 route
1) Configure a new loopback interface (say loopback 2)
2) Enable multicast for loopback 2
3) Configure the following: mhost ipv4 default interface loopback 2
Optional: Rollback all configuration changes (remove loopback 2 and mhost config)
Further Problem Description:
|
|
Last Modified: | 13-OCT-2015 |
|
Known Affected Releases: | 5.1.3.MCAST |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw31346 | Title: | DHCP bindings loaded from persistent storage with incorrect lease time |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
DHCP snooping bindings are seen with Remaining Lease time set to "original remaining lease time" + current time zone after router reload.
If router is in GMT+3 time zone then all bindings will get +3 hours:
Before reload:
RP/0/RSP0/CPU0:syros#show dhcp ipv4 snoop binding
Wed Sep 16 22:41:52.256 CEST
MAC IP Lease Bridge
Address Address State Remaining Interface Domain
-------------- --------------- ---------- ---------- -------------------------------- ----------------------
a89d.2105.8303 192.168.0.12 BOUND *15688* Gi0/0/0/1 vyashin_repro_sr_680125955:vyashin_repro_sr_680125955
After reload it's +3 hours (10800 seconds):
RP/0/RSP0/CPU0:syros#show dhcp ipv4 snoop binding
Wed Sep 16 22:59:23.285 CEST*<<<<<< +18 min*
MAC IP Lease Bridge
Address Address State Remaining Interface Domain
-------------- --------------- ---------- ---------- -------------------------------- ----------------------
a89d.2105.8303 192.168.0.12 BOUND 25438 Gi0/0/0/1 vyashin_repro_sr_680125955:vyashin_repro_sr_680125955
Conditions:
DHCP snooping persistance is activated. All DHCP snoop bindings are saved into DB on harddisk/disk0 and are
restored from on-disk DB after router reload.
Workaround:
If its possible to remove daylight saving and timezone config, that is a way out. No other workaround
Further Problem Description:
Will be seen only if timezone or daylight saving is configured. Will be seen in other DHCP modes - server and proxy
|
|
Last Modified: | 09-OCT-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv93296 | Title: | macsec SA continously rekeying with traffic on the vlan interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Macsec SA continous rekey
Conditions:
with traffic on clan interface, SA continuously rekeys due to MKA packet loss
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 09-OCT-2015 |
|
Known Affected Releases: | 5.3.2.K9SEC, 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut30585 | Title: | ppp_ma crashed @ ppp_ma_iedge_af_process_event() |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:ppp_ma crashes while churning sessions.
Conditions:Issue is seen when sessions are churning continuously.
Workaround:None
|
|
Last Modified: | 30-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | 5.3.2.18i.FWDG, 5.3.3.3i.FWDG, 6.0.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw57636 | Title: | TE tunnel with Juniper Head-end configured in strict mode is down |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:TE tunnel with Juniper Head-end with strict router-IDs in the path remains down.
Conditions:ASR9K running 5.1.3 is a mid-point of TE tunnel.
TE tunnel head-end is juniper with ERO consisting of router IDs in strict mode.
Workaround:Cisco developers suggest to use loose in the Junos config for the router IDs in the explicit path. Another option is to use strict hops with the link addresses and not the router IDs.
More Info:
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv97476 | Title: | cpwVcMIB.2.1 is not generated whenever VPLS PW is down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
cpwVcMIB.2.1 is not generated whenever VPLS PW is down
Conditions:
VPLS PW is down
Workaround:
n/a
Further Problem Description:
would only happen for static PWs.
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: | 5.3.1.MPLS |
|
Known Fixed Releases: * | 6.1.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw28097 | Title: | Add mesg to stop supporting cgn ova deact/act without LC reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CGN VM is activated
Conditions:
CGN VM is deactivated and then activated
Workaround:
No workaround . It is mandatory that we do a LC reload after cgn ova is deactivated/activated.
Further Problem Description:
we would like to stop supporting OVA deactivation and activation for the following reasons.
1. CGN MA is never designed to understand whether OVA is deactivated or activated .
All CGN MA can understand is whether LC goes down or comes up.
2. We have seen multiple issue on deactivating and activating OVA from 5.1.1 . We have
worked to fix those issues ,but still issues are coming and we spend good amount of time on
it.
3. Supporting deactivating and activating an OVA without LC reload makes sense only when we
have multiple VMs running on VSM . But CGN takes all resources and no other VM can be
activated on VSM.
So if we do a deactivation and activation of an OVA for either upgrade and downgrade, LC reload will be mandated just like we do in ISM.
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut02575 | Title: | BGP crash after RPFO due to wrong fragmentation handling during NPL rtx |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In very rare circumstances, Upon a RP Failover, it is seen that BGP on the new standby crashes. It has to do with dereferencing a NULL attribute-id TLV.
Attribute-ID TLVs are used to sync data structures across partner nodes, once the actual attribute has been shipped across from Active to Standby.
Conditions:
The crash occurs when a comm_id tlv (needed for syncing attributes between active and standby) sent from the Active to the Standby can't be retrieved by the latter because it is not present in its database.
A null attribute is returned in the case above and de-referencing it causes the crash. In the few times this was seen there was MVPN configuration present on the router.
It appears as a condition
Workaround:
There is no workaround when this happens.
Sometimes after a crash, the system becomes stable.
Further Problem Description:
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.2.4.BASE, 5.3.2.BASE, 5.3.2.ROUT |
|
Known Fixed Releases: | 5.3.2.ROUT, 5.3.3.8i.ROUT, 6.0.0.14i.ROUT |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw57230 | Title: | Satellite access interfaces take more than ~75 secs to come up |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
Satellite access interfaces take more than ~75 secs to come up after configuring
Conditions:
Simple Hub and Spoke Topology
Workaround:
Wait 2 minutes after icpe_cpm started to allow resync to complete
Further Problem Description:
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut08813 | Title: | Suppress interrupts after large numbers of recoverable ECC errors |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In rare cases, NP soft error will continue to detected repeatedly. If this condition occurs, the error counter displayed in the 'show contr np soft-errors' CLI output will continue to increase:
# show controller np soft-errors 98 np0 loc 0/0/cpu0
NP Blk Name Ignored Fixed Sticky Reset Spurious
-- --- ---------- --------- ---------- ---------- ---------- ----------
3 98 PSTAT1 1263214 0 0 0 0
# show controller np soft-errors 98 np0 loc 0/0/cpu0
NP Blk Name Ignored Fixed Sticky Reset Spurious
-- --- ---------- --------- ---------- ---------- ---------- ----------
3 98 PSTAT1 1263400 0 0 0 0
When this issue occurs, it can also cause a small amount of CPU time to be consumed indefinitely by the kernel and prm_server processes:
#show processes cpu location 0/0/CPU0
CPU utilization for one minute: 21%; five minutes: 21%; fifteen minutes: 21%
PID 1Min 5Min 15Min Process
1 9% 9% 9% kernel
61473 3% 3% 3% eth_server
155714 1% 1% 1% fialc
155728 8% 8% 8% prm_server_to
Conditions:
There is no specific trigger for the underlying soft error. It only occurs on a small percentage of NP soft errors which are themselves a rare occurrence. It can occur on both Typhoon and Tomahawk linecards.
Workaround:
Generally there are no functional side effects seen with this issue. If there is concern about the CPU usage, a linecard reload may be scheduled during a maintenance window.
Further Problem Description:
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE, 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw54987 | Title: | eXR: extra lines are displayed in output of "show led" - 6.1.0.01I |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Extra lines are displayed in output of "show led".
Conditions:
Execute "show led". command.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum89472 | Title: | vrrp config: 'no exclude-item message state disable' commit fails |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: | Symptom:
'no exclude-item message state disable' commit fails in case with the config being inherited from an applied group and then excluded from being inherited
Conditions:
'no exclude-item message state disable' config commit under 'vrrp/interface MgmtEthx/x/x/x" config level
Workaround:
do not exclude this configuration by 'exclude-item' to avoid the issue being hit.
Further Problem Description:
see description
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun92809 | Title: | VIC: Read the mac address from UIDB |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Operational MAC address showing as 0000.0000.0000
The issue is seen on tengig0/0/2/2 & 0/0/2/3.
RP/0/RSP0/CPU0:sc-coe-1#Show controller tengig0/0/2/2 internal
Tue Sep 1 11:00:26.477 PDT
Port Number : 2
Board Type : 0x00f10402
Port Type : 10GE
Transport mode : LAN
BIA MAC addr : 5087.891d.5552
Oper. MAC addr : 0000.0000.0000 >>>
Conditions:
The issue was seen when the interfaces were brought up for the first time
Workaround:
1. Configure a static MAC
2. Reload of the router
Further Problem Description:
|
|
Last Modified: | 06-OCT-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: | 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo10276 | Title: | SSTE: "show onep session rate-limit" causes traceback on HA asr9k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Issuing the command "show onep session rate-limit" will cause a traceback
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.23i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun32664 | Title: | Openflow: sh openflow hw capa shows unsupported swtich 133 & capability |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Wrong capability with OF show hw capability command
Conditions:
Normal
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.8i.BASE, 5.1.4, 5.2.0, 5.2.0.24i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul84640 | Title: | XR:511: IntfDelete Events are not triggered when set_type filter is set |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When filter is set on interface type, interface delete notification are not sent back to the client
Conditions:
always
Workaround:
Workaround : client must cache the interface handle, name and type. Register to listen on delete notifications without any filters and compare handles in the application context to filter on the type
Reproducibility (100%):
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.20i.BASE, 5.1.11, 5.1.11.16i.BASE, 5.1.12, 5.1.2, 5.1.2.14i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus79192 | Title: | SSTE:Show operational OSPF xml fails and throws and XML Error |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When doing "show operational OSPF xml" command the xml returned fails.
MGMT_OPQ_RRR_TYPE
........
Conditions:
This will happen only if extended admin group SUBTLV is present in opaque LSA
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 5.3.1.24i.ROUT, 5.3.2.3i.ROUT, 6.0.0.5i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu95294 | Title: | OSPFv2 receives and ICMP packet in responce to DBD. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OSPFv2 prints the messages like BAD length, invalid version
Conditions:
in response to some of the OSPF packets it might be possible that ospf receives the ICMP packet for example destination unreachable. in that case ospf should simply discard the packet rather than processing it.
Workaround:
this does not happen in normal condition. operator should check why ICMP packets are coming to OSPF. this is due to some network issue.
Further Problem Description:
I have attached the WireShark recording of the IXIA interface, in presence of the issue. Typically, the issue is created by simply reloading the Line card hosting the Satellite unit. After a line card OIR, the IXIA exchange was recorded in the attached file.
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 4.1.1.ROUT, 4.1.2.ROUT, 4.3.0.BASE, 4.3.1.ROUT, 5.2.0.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.2.5.28i.ROUT, 5.3.2, 5.3.2.18i.ROUT, 5.3.3.3i.ROUT, 6.0.0.12i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul31314 | Title: | OutputPacketRate???event is regitered when ONEP_IF_STAT_TX_LOAD specified |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Even ONEP_IF_STAT_TX_LOAD is set in InterfaceStatisticsFilter, OutputPacketRate is set as an event filter at the ASR9 router side.
Conditions:
The ASR9K image is /auto/ONE-P/mnayyar/ntt-img/ASR9K-image/asr9k-mini-px.vm.
The application is InterfaceStatisticsTutorial.java.
Workaround:
Set ONEP_IF_STAT_RESETS instead of ONEP_IF_STAT_TX_LOAD.
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 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, 5.2.0, 5.2.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul32078 | Title: | Laod and Rate gotten by OnePK interface SS are invalid |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The problem is that rxload, txload, tx rate and rx rate values are invalid when they are gotten by getTransmitLoad(), getReceiveLoad(), getTransmitRateBPS and getReceiveRateBPS respectively.
txload and rxload values are 128 times higher than actual values.
tx rate and rx rate is are a eighth of actual values.
Conditions:
The image which is tested is /auto/ONE-P/mnayyar/ntt-img/ASR9K-image/asr9k-mini-px.vm.
SDK is 1.1.0.141
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 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, 5.2.0, 5.2.0.8i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh09002 | Title: | ASR9k DPSS: Require an API for deleteing existing FLOW entry |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unable to delete an existing flow by sending a notification from the application.
Conditions:
I have 10 flow entries created in platform and offload bit is set for all flows.
I need to delete 5th flow entry by sending a request from application.
Since these flows are offloaded, the application will not receive any traffic for these flows.
How can i delete the 5th flow entry by sending a request from application.
Workaround:
None. Since a NEW API have to developed in 511.
Further Problem Description:
|
|
Last Modified: | 04-OCT-2015 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.10i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12, 5.1.2, 5.1.2.1i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw43356 | Title: | Radius Attribute 95 has wrong length |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Radius authentication requests packets dropped by server.
Conditions:
IOS-XR 5.3.1
Workaround:
None
Further Problem Description:
Attribute 95 (NAS-IPv6-Address) should have a length of 18 per RFC, but XR uses a length of 22.
|
|
Last Modified: | 09-OCT-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus09646 | Title: | Satellite 1GE ports remain in Admin down state while ICL on Host is shut |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Issue: Satellite 1GE ports remain in Admin down state while the cross-linked ICL interface on Host is made shut while Host & Satellite are in Connecting state.
Conditions:
When the cross-linked ICL interface on Host is made shut while Host & Satellite are in Connecting state.
Workaround:
Do ?no shut? & then shut on Host ICL interface while Host & satellite comes in Connected Stable state to make the system in stable state.
Further Problem Description:
Issue: Satellite 1GE ports remain in Admin down state while the cross-linked ICL interface on Host is made shut while Host & Satellite are in Connecting state.
Satellite Type: Both ASR9000v and ASR9000v2
ICL Type: 1GE and 10GE both.
Reproduction Steps:
1. Host & Satellite are in Connected stable state
2. Do Satellite type mismatch on Host & check interface state of remote ports that remains in admin down state.
3. Now correct type mismatch & immediately shut the ICL Tengig /gig interface on the host while Host is in Connecting state.
4. Check remote ports state that remains in admin down state even after Host & satellite comes connected stable state even after couple of minutes.
Expected Result
After Connected stable state if the ICL interface on Host is made shut then the ports on satellite should not act as an Access ports instead they should remain in admin up state as they are potential ICLs.
Logs:-
O/p on host after step 2.
Satellite 65534
---------------
Status: Authentication failed (Wrong chassis type)
Type: asr9000v
MAC address: 501c.bf11.535c
IPv4 address: 10.255.254.1 (auto)
Serial Number: CAT1811U1PL
Configured satellite fabric links:
TenGigE0/0/2/1
--------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/0-10
GigabitEthernet0/0/0/18
-----------------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/11-20
O/p on Satellite after step 2.
GigabitEthernet1/1 unassigned YES unset administratively down down
GigabitEthernet1/2 unassigned YES unset administratively down down
GigabitEthernet1/3 unassigned YES unset administratively down down
GigabitEthernet1/4 unassigned YES unset administratively down down
GigabitEthernet1/5 unassigned YES unset administratively down down
GigabitEthernet1/6 unassigned YES unset administratively down down
GigabitEthernet1/7 unassigned YES unset administratively down down
GigabitEthernet1/8 unassigned YES unset administratively down down
GigabitEthernet1/9 unassigned YES unset administratively down down
GigabitEthernet1/10 unassigned YES unset administratively down down
GigabitEthernet1/11 unassigned YES unset administratively down down
GigabitEthernet1/12 unassigned YES unset administratively down down
GigabitEthernet1/13 unassigned YES unset administratively down down
GigabitEthernet1/14 unassigned YES unset administratively down down
GigabitEthernet1/15 unassigned YES unset administratively down down
GigabitEthernet1/16 unassigned YES unset administratively down down
GigabitEthernet1/17 unassigned YES unset administratively down down
GigabitEthernet1/18 unassigned YES unset administratively down down
GigabitEthernet1/19 unassigned YES unset administratively down down
GigabitEthernet1/20 unassigned YES unset administratively down down
GigabitEthernet1/21 unassigned YES unset administratively down down
O/p on host after step 4.
Satellite 65534
---------------
Status: Connected (Stable)
Ty
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.1.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur93199 | Title: | asr9k BNG-iosxr 4.3.4-Memory leak at radiusd process |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:radiusd process leaks memory
Conditions:BNG terminating pppoE subscribers
Workaround:restart radiusd process
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: * | 3.8.3, 3.8.4, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.0.0, 4.0.1, 4.0.2, 4.0.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus08820 | Title: | PLATFORM-CANB_SERVER-3-MESSAGE_FAILED with ASR-9001-FAN-V2 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR9001 reports the following message:
RP/0/RSP0/CPU0:Nov 25 02:55:43.292 : canb-server[153]: %PLATFORM-CANB_SERVER-3-MESSAGE_FAILED : Unexpected CBC message received from slot 0/FT0/SP [ver 24.115] for msg type 3, id 159, len 4
Conditions:
Seen with the ASR-9001-FAN-V2.
Workaround:
Configure log suppression for message.
Example:
logging suppress rule CANB_FAN_MESSAGES
alarm PLATFORM CANB_SERVER MESSAGE_FAILED
!
logging suppress apply rule CANB_FAN_MESSAGES
all-of-router
!
Further Problem Description:
Despite message, fan tray is operating properly. Can verify with the following commands.
admin show environment fans or
admin show environment all
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: | 5.1.2.BASE, 5.1.3.BASE, 5.2.2.BASE |
|
Known Fixed Releases: | 5.2.4.5i.BASE, 5.3.1, 5.3.1.12i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw59218 | Title: | Umbrella DDTS to address PI FIB issues on ASR9K |
|
Status: | Other |
|
Severity: | 4 Minor |
Description: | Symptom:
FIB failures are seen with LER scale
Conditions:
Certain PI FIB fixes are missing in 5.3.0 due to which FIB reliability issues are seen with LER scale
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh97322 | Title: | DataPathIDL.thrift file has an xml error |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Thrift file has syntax error in it.
Conditions:
None
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 03-OCT-2015 |
|
Known Affected Releases: | 5.1.0.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.7i.BASE, 5.1.11, 5.1.11.4i.BASE, 5.1.12, 5.1.2, 5.1.3, 5.1.4, 5.2.0, 5.2.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul00458 | Title: | 4.2.x and 4.3.x HSRP Config Guides needs to mention no v2 authentication |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: * | Symptom:
The Cisco ASR 9000 Series Aggregation Services Router IP Addresses and Services Configuration Guide, Release 4.2.x -Implementing HSRP
and
The Cisco ASR 9000 Series Aggregation Services Router IP Addresses and Services Configuration Guide, Release 4.3.x -Implementing HSRP
configuration guide needs to have a Note in the Restrictions section that mention that authentication is not supported for version 2
Conditions:
attempt to configure HSRP with the configuration guide
Workaround:
authentication cannot be configured for version 2
Further Problem Description:
|
|
Last Modified: | 27-OCT-2015 |
|
Known Affected Releases: | 4.2.0.BASE, 4.2.1.BASE, 4.2.3.BASE, 4.2.4.BASE, 4.3.0.BASE, 4.3.1.BASE, 4.3.2.BASE, 4.3.3.BASE, 4.3.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun05836 | Title: | ASR9k_ISSU_Overview presentation need to be updated. |
|
Status: * | Terminated |
|
Severity: | 4 Minor |
Description: * | Symptom:
The following presentation need to be updated for 4.3.4 and beyond.
http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/ASR9K_ISSU_Overview.pdf
Update Feb 27th:
This issue is now fixed and the above presentation is fixed upto 5.1.1 on Feb 2014.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 27-OCT-2015 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw53118 | Title: | Fan Tray Alarms |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: * | Symptom:
Customer experiences multiple fantray alarms on ASR9922, alarms generate then clear themselves. DE has confirmed this to be cosmetic.
Conditions:
Fan Tray alarms self generate due to DDTSCSCus80011
Workaround:
upgrade device
Further Problem Description:
|
|
Last Modified: | 26-OCT-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus85346 | Title: | Enhance usability of the MAC address table dump |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
"show l2vpn forwarding bridge-domain mac-address location " (or the "hardware {ingress|egress}" variant of the same command) provides output at the speed that is perceived as too slow for effective troubleshooting. Re-sync of the SW and HW MAC table speeds up the output temporarily.
Conditions:
none
Workaround:
none
Further Problem Description:
This is an enhancement request to increase the usability of the facility to dump the MAC address table on asr9000 line cards.
|
|
Last Modified: | 30-OCT-2015 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.3.8i.BASE, 6.0.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw49484 | Title: | Modifying the marginal values of voltage sensors for all LCs |
|
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: | 23-OCT-2015 |
|
Known Affected Releases: * | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论