| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj80945 | Title: | ASR9k disconnects satellite during normal operation |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
ASR9k host disconnects satellite during normal operation causing traffic impact
All ICL links go down during the event
In most cases we will see the ICL link go down followed by satellite access ports going down and an inventory message indicating 'node removed'
LC/0/7/CPU0:Sep 22 09:35:07.605 UTC: ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface TenGigE0/7/0/20, changed state to Down
LC/0/7/CPU0:Sep 22 09:35:07.606 UTC: ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet111/0/0/2, changed state to Down
LC/0/7/CPU0:Sep 22 09:35:07.606 UTC: ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet111/0/0/2, changed state to Down
LC/0/7/CPU0:Sep 22 09:35:07.608 UTC: ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface TenGigE0/7/0/21, changed state to Down
LC/0/7/CPU0:Sep 22 09:35:07.609 UTC: ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet111/0/0/13, changed state to Down
RP/0/RSP0/CPU0:Sep 22 09:35:07.617 UTC: invmgr[259]: %PLATFORM-INV-6-OIROUT : OIR: Node 111 removed
Conditions:
Occurs during normal operation
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 4.2(1), 5.2(2) |
|
Known Fixed Releases: * | 15.1(3)SVF04c, 15.1(3)SVF04d, 15.1(3)SVF04f, 15.1(3)SVG01c, 15.1(3)SVG02, 15.1(3)SVG03, 15.1(3)SVG03a, 15.1(3)SVH02, 15.1(3)SVH04 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu00818 | Title: | sysdb_shared_sc crash |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
sysdb_shared_sc crash
Conditions:
after upgrade 5.1.3
Workaround:
n/a
Further Problem Description:
This issue happens multiple times. The trigger could be the way router's config is updated. They do commit replace everytime update the config.
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.2.5.41i.BASE, 5.3.2, 5.3.2.12i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74155 | Title: | RJIL : ASR9k - Multicast RPF failure on 5.3.3.23I |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
We are unable to see RPF neighbor in the show mrib ipv6 route and show pim ipv6 rpf <>, but we have routing entry in show route ipv6.
RP/0/RSP0/CPU0:AG2-2#sh mrib ipv6 route
Thu Dec 24 11:26:11.029 IST
(2405:200:8001:101::2,ff33:4001::3)
RPF nbr: :: Flags: RPF
Up: 01:34:56
Outgoing Interface List
TenGigE0/0/0/4 Flags: F NS, Up: 01:34:56
RP/0/RSP0/CPU0:AG2-2#sh route ipv6 2405:200:8001:101::3
Thu Dec 24 11:26:33.301 IST
Routing entry for 2405:200:8001:101::/64
Known via "bgp 55836", distance 200, metric 0
Tag 65000
Number of pic paths 1 , type internal
Installed Dec 24 09:49:11.692 for 01:37:21
Routing Descriptor Blocks
2405:200:1410:32:4000::, from 2405:200:1410:32:4000::
Route metric is 0
2405:200:1410:32:4000::1, from 2405:200:1410:32:4000::1, BGP backup path
Route metric is 0
No advertising protos.
RP/0/RSP0/CPU0:AG2-2#sh pim ipv6 rpf 2405:200:8001:101::3
Thu Dec 24 11:26:54.193 IST
Table: IPv6-Multicast-default
2405:200:8001:101::3/128 [200/10]
via fe80::5287:89ff:fe2b:f8c8, Null
RP/0/RSP0/CPU0:AG2-2#
Conditions:
IPv6 multicast is present in global-table. The RPF reachability to the Source/RP/BSR should be, using a BGP route.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.3.21i.MCAST |
|
Known Fixed Releases: * | 5.3.3.26i.FWDG, 5.3.3.26i.MCAST, 6.0.1.15i.BASE, 6.0.1.15i.FWDG, 6.0.1.15i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup67926 | Title: | Satellite does not detect ICL link down on Tx cable removal |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Expected Behavior: When the Tx cable is plugged out from ICL port of satellite, the respective port on host stops receiving laser which in turn will go down and notifies satellite port on Remote fault. As satellite receives a Remote fault it should make the ICL port (from which tx is plugged out) down and at the same time as the ICL is down on host, satellites goes down.
But contrary to above mentioned the satellite port is up when we plug out tx cable.
Conditions:
We see this issue if we unplug tx cable from satellite ICL port when connected to host.
9k---------------------satellite
ICL interface
Workaround:
No Work around.
Further Problem Description:
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 5.2(2) |
|
Known Fixed Releases: * | 15.1(3)SVF04f, 15.1(3)SVG03b |
|
|
| |
| |
|
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: | 07-JAN-2016 |
|
Known Affected Releases: * | 4.3.0.FWDG, 4.3.1.FWDG, 4.3.2.FWDG, 4.3.4.FWDG, 5.0.0.FWDG, 5.1.1.FWDG, 5.1.2.FWDG, 5.1.3.FWDG, 5.2.2.FWDG, 5.2.4.FWDG |
|
Known Fixed Releases: | 5.3.0.18i.BASE, 5.3.0.18i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux26791 | Title: | SPP buffer leak on reciveing of too large packets |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
1) Punt path traffic impacted i.e. punt l3 services including l3 protocols + TCP services impact including telnet/SSH
2) Log :-
RP/0/RSP0/CPU0:Nov 21 18:54:02.479 IST: netio[342]: %PKT_INFRA-spp-4-PKT_ALLOC_FAIL : Failed to allocate 1 packets for sending
Conditions:
Invalid (too large) packets getting injected from ASR-9001 RP.
Internet Protocol Version 4, Src: 172.17.3.254 (172.17.3.254), Dst: 192.168.192.73 (192.168.192.73)
Total Length: 14986 (1508 bytes including L2 encap)
User Datagram Protocol, Src Port: 55039 (55039), Dst Port: 9 (9)
Issue is specific to ASR-9001
Workaround:
1) Blocking source of packet though ACL which is sending such invalid packets.
2) If signature is same and every time same dst port is used then Blocking dst port using ACL
3) set fragment 0 on LPTS. The impact would be global and this will no allow ip fragment marked packet on punt path (static punt path is also included)
4) Immediate recovery can be achieved through "process restart spp"
Further Problem Description:
Below Commands can help in further debugging:-
------------------------------------------------------------------
show netio drops location |
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.3.3.22i.BASE, 6.0.0.26i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux44521 | Title: | 533.19i: Snoop with local DHCP server not working |
|
Status: | Fixed |
|
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: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.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: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux32151 | Title: | bvi_ma %L2-VIF_MA_MSG-4-REPL_FAIL : interfaces failed to replicate. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
bvi ma L2-VIF_MA_MSG-4-REPL_FAIL ios messages is being printed on console which may create unnecessary confusion to customer.
Conditions:
bvi_ma failed to create/replicate on some of the linecards.
Workaround:
No workaround is required. bvi_ma will retry if it failed to create/replicate bvi interfaces until it succeeds.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux45308 | Title: | cgn_ma process crash continuously , after reloading the router |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Process cgn_ma on RSP crashes continuously after a router reload with 6.0.0-25i image. None of the CGN configurations would be successfully saved as the cgn_ma crashes continuously.
Conditions:
VSM with NAT44 Service configured and one or more pairs of ServiceApp SVI interfaces. Router reload may trigger the cgn_ma crash.
Workaround:
Shutdown the process
Remove the CGN and ServiceApp SVI configurations
Start the process
Configure only CGN service and commit
Add relevant inside-vrfs to the saved CGN instance and commit.
Later configure all related ServiceApp SVIs and commit.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
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: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux48433 | Title: | Stats are leaked due to mishandled create events for PW in created state |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Stats are leaked due to mishandled create events for PW in created state. When Stats are exhausted, new PW will not be able to come up properly and can not forward traffic. The following output can be used as a signature of Stats exhaustion:
RP/0/RSP0/CPU0:R4#sh l2vpn trace wrapping reverse location 0/0/cpu0
Wed Dec 9 12:01:10.739 EST
214618 wrapping entries (244224 possible, 215296 allocated, 0 filtered, 28165270 total)
Dec 9 12:01:01.440 l2vpn/err 0/0/CPU0 t1 FWD_ERR|ERR:1042: CREATE: XC(0xc000fa00) PW(200.0.3.1:65530:40000) 1 1 failed: 'vkg-fwd-l2vpn-trident' detected the 'warning' condition 'Error in allocating PW stat pointer'
Conditions:
PW flap. This leak issue is seen only for incoming stats types from fib/l2fib.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.25i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux43464 | Title: | Sureshot EDVT: FIA drops at >60% Linerate on 1x100GE MPA |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Large number of packet loss at FIA when sending traffic 60GE of traffic on 1x100GE MPA + MOD200 Sureshot
Conditions:
SLOT4_RSP0 | 2015/12/01 19:21:09 | RP/0/RSP0/CPU0:ios#admin show platform
SLOT4_RSP0 | 2015/12/01 19:21:09 | Tue Dec 1 19:21:09.378 UTC
SLOT4_RSP0 | 2015/12/01 19:21:09 | Node Type State Config State
SLOT4_RSP0 | 2015/12/01 19:21:09 | -----------------------------------------------------------------------------
SLOT4_RSP0 | 2015/12/01 19:21:09 | 0/0/CPU0 A9K-MOD200-SE IOS XR RUN PWR,NSHUT,NMON
SLOT4_RSP0 | 2015/12/01 19:21:09 | 0/0/0 A9K-MPA-1X100GE OK PWR,NSHUT,MON
SLOT4_RSP0 | 2015/12/01 19:21:09 | 0/0/1 A9K-MPA-1X100GE OK PWR,NSHUT,MON
Workaround:
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
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: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.ROUT |
|
Known Fixed Releases: * | 5.2.5.39i.ROUT, 5.3.3.24i.ROUT, 6.0.1.13i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux13344 | Title: | VPLS GREoMPLS: Traffic loss seen on having ECMP for the IP tunnel |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic loss is seen on having more than one path for GREoMPLS.
Conditions:
On having ECMP path for the PW going over GRE o MPLS, the traffic loss is seen.
Workaround:
For this to work as a workaround have only one path either physical or bundle for the PW going over GREoMPLS.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh43478 | Title: | "unclassified-source per-vlan" issue for IPOE by packets triger |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:when config "unclassified-source per-vlan" to 1 for IPsub, found session only establish one time, if session was be clear, will couldn't setup again.
Conditions:ASR9k + 4.3.1 + IPOE by packets trigger
Workaround:only remove "unclassified-source per-vlan".
session limited should limit client number under one VLAN, but that shouldn't limit one VLAN trigger times.
More Info:Vlan session counters not correctly incremented/decremented due to incorrect usage of flags. Flag removed.
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.2.23i.BASE, 5.1.0.14i.BASE, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv88809 | Title: | On RPFO - Continuous bundlemgr_distrib process Crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On RPFO - Continuous bundlemgr_distrib process Crash
Conditions:
RP Failover
Workaround:
Router Reload
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.FWDG, 5.3.3.8i.FWDG, 6.0.0.14i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv35166 | Title: | ASR9K/BNG/5.3.1 iedge process block because of xml queries |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IPoE subscribers are not able to connect with BNG.
Conditions:
Initiate 25-30 XML sessions with BNG to get the subscriber information and state.
Workaround:
Disable the XML agent on ASR9K.
-- Example --
RP/0/RSP0/CPU0:acdc-asr9000-4(config)#no xml agent
RP/0/RSP0/CPU0:acdc-asr9000-4(config)#commit
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.2.2.BASE, 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.19i.BASE, 5.3.3.5i.BASE, 6.0.0.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut91896 | Title: | domain_services request for core dump |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
core dump of domain_services, aka DNS server
Conditions:
Requests for DNS not closing the application socket. FD counts increase until it reaches the hard limit.
1. domain lookup vrf source-interface is configured
2. interface1 is not in VRF1
ie the VRF of domain source interface command and the actual interface VRF mismatch.
Workaround:
Correct the configuration so that domain source interface VRF is consistent with the configuration on the interface.
Further Problem Description:
This is a case configuration error.
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.5i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux07488 | Title: | A9K-MPA-4X10GE not boot after OIR or soft reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On the ASR9K with version 5.3.2 is observed that the A9K-MPA-4X10GE does not boot after performed an OIR/reload to the MPA.
Conditions:
Have Satellite configured on a interface which belongs to the MPA card,
!
interface TenGigE0/0/0/2
description ***** DESCO01-SADv-101 *****
mtu 9216
load-interval 30
nv
satellite-fabric-link network
redundancy
iccp-group 1
!
satellite 101
remote-ports GigabitEthernet 0/0/0-1,42-43
!
satellite 102
remote-ports GigabitEthernet 0/0/0-1,22,10
!
satellite 103
remote-ports GigabitEthernet 0/0/0-1
!
satellite 104
remote-ports GigabitEthernet 0/0/0-1,43
!
Workaround:
There are to posible Work arounds.
1.- Remove the Satellite configuration from the MPA and boot the MPA.
2.- Reboot the entire SIP (A9K-MOD80-SE) card.
Further Problem Description:
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.26i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc53683 | Title: | Intermittent prmserver, fialc crash on A9K-24X10GE-TR due to pcie access |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
multiple process crashes on prmserverty, fab_xbar, fialc which resulted in reloading the 24*10GE linecard
Conditions:
Normal operation or linecard bootup.
Workaround:
none
Further Problem Description:
This is a transient HW issue in PCIe switch which gets stuck in very rare scenario. This results in read & write access failure to the south bound devices attached to PCIe. So, prm_server_ty, fialc process crashes which evenly result in linecard reload.
This issue happened only at 10 different occurrences in the past 4 years after FCS.
Recommended action is to monitor the system during the first occurrence. We have never seen second occurrence of this issue on the same linecard. But if it happens, RMA the board.
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw80979 | Title: | snmpd memory leak in <N/A> |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The snmpd process may start leaking memory
Conditions:
This problem can be seen during normal polling of the router when running 5.3.1
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.5.38i.BASE, 6.0.0.27i.BASE, 6.1.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu62902 | Title: | DHCP relay fails after RSP switchover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
DHCP relay and proxy with access interface as LC and server facing interface as bundle [RP based] drops server packets after redundancy switchover.
Conditions:
Access interface should be LC and server facing interface should be bundle
Workaround:
DHCP process restart will resolve the issue.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.14i.FWDG, 6.0.0.10i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo04219 | Title: | 5.1.2.19I - sessions are not recovered after RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
iedged process may crash or sessions may be lost after rpfo or restart of policymgr_rp or iedged processes.
Conditions:
subscriber sessions with pqos attributes
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.1.2.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum35555 | Title: | 511-SIT: ppp_ma continuously crashing |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ppp_ma continuously restarts
Conditions:
After applying ICSSO Configs
Workaround:
NA
Expected Resolution: Please check with the support engineer for information on which release(s) this bug is expected to be fixed.
Reproducibility (%):
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE, 5.1.2.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.20i.FWDG, 5.1.11, 5.1.11.16i.FWDG, 5.1.12, 5.1.2, 5.1.2.12i.FWDG, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq15659 | Title: | Resource leakage fib in constrained mode |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
FIB operates in resource constraint mode.after bringing up & bringing down IPoE V6 sessions multiple times.
Conditions:
Issue only happens with IPoE V6 subscriber sessions.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.0.BASE |
|
Known Fixed Releases: * | 5.2.2.21i.BASE, 5.2.3.8i.BASE, 5.3.0, 5.3.0.4i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum45585 | Title: | [511]-Ipsub_ma process restarted after BNG pie activation |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After activate bng pie could see ipsub_ma process is restarted.
Conditions:
In 19I Image, could see ipsub_ma process is restarted after activated bng pie.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.1.20i.BASE, 5.1.11.16i.BASE, 5.1.2.12i.BASE, 5.2.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum24221 | Title: | 511.17I: iedged process crashed after RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Memory leak and eventual Memory depletion for iedged process.
iedged process crash after RPFO or process restart of poilcymgr_rp .
Conditions:
This was observed with 128k scale IPoE subscribers
There are sessions with PQoS (parameterized QoS) attributes. Creation each such session can contribute to memory leak. On process restarts (of client processes like policymgr_rp) also, these sessions contribute to leaks.
Workaround:
None
Process restart of iedged (iedged restart will remove the leaks and sessions will be intact)
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.16i.BASE, 5.1.3, 5.1.4, 5.2.0, 5.2.0.15i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu24041 | Title: | [531] iedged crashes with invalid pqos string |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
iedged crashes on RSP
Conditions:
While applying an invalid CoA with bad pqos string could see iedged is crashing
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.BASE, 5.3.2, 5.3.2.9i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup23781 | Title: | 522 RTDSUB: iedged Memory leak observed with subscriber bringup/down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Memleak observed with iedged process
Conditions:
64k Scale bringup and bringdown.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.2.14i.BASE, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80640 | Title: | ISIS process crash when "show isis ipv6 route" command is entered |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Depending on the network topology, the ISIS process may crash and restart when the command:
show isis ipv6 route
is entered, or when an equivalent XML request is made.
Conditions:
IPv6 routes in the ISIS rib have lower-priority backups.
Workaround:
Do not use the "show isis ipv6 route" command.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 6.0.1.ROUT |
|
Known Fixed Releases: * | 5.3.3.27i.ROUT, 6.0.1.14i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut67156 | Title: | [524] Interim accounting update failed for few sessions |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Interim accounting update failed for few sessions
Conditions:
While sending dynamic template activate service CoA
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 5.2.4.15i.BASE, 5.2.5.8i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul09400 | Title: | [434] Invalid CoA requests are getting acknowledged |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Invalid CoA requests are getting acknowledged
Conditions:
CoA request with only 4 arguments are Acked
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.10i.BASE, 5.1.1.16i.BASE, 5.1.2.7i.BASE, 5.2.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup82270 | Title: | [522] Duplicate entries created in radius server for PPPOE Sessions |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Duplicate entries created in radius server for PPPOE Sessions.
Conditions:
With dualstack PPPOE Sessions. This issue occurs specifically when 1st AF comes up, acct start is sent to radius and the second AF comes up before the accounting response for the first acct start message is received.
Workaround:
Configure dual-stack-delay for session accounting as below. This will make sure that acct start messages are sent when both the AFs are up and hence preventing duplicates.
Example:
"accounting aaa list default type session dual-stack-delay 5"
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.2.18i.BASE, 5.2.3.3i.BASE, 5.2.3.6i.BASE, 5.3.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu84081 | Title: | SSTE:VM is exhausted or totally fragmented after longevity IPv6 session |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
VM is exhausted or totally fragmented
Conditions:
longevity scale IPv6 sessions cycle
Workaround:
restart process
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.19i.BASE, 5.3.2.19i.FWDG, 5.3.3.5i.BASE, 5.3.3.5i.FWDG, 6.0.0.11i.BASE, 6.0.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66111 | Title: | eXR: standby RP stuck in Unknown Band after back-to-back RPFO |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Standby RP stuck in Unknown Band after back-to-back RPFO for multiple times.
Conditions:
Run script to trigger back-to-back RPFO for multiple times on a 9904 router with dual RSPs..
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 5.2.5.41i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut59790 | Title: | [5.3.1-23I] iedged crashed upon receiving access-reject |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Iedge process on LC
Conditions:
"debug subscriber manager all" enabled and when access reject is received for service logon request.
Workaround:
Disable "debug subscriber manager all"
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.5.19i.BASE, 5.2.5.5i.BASE, 5.3.2, 5.3.2.9i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf77118 | Title: | Serial DS3 - stays up when looped in HDLC - down-when-looped configured |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The command: "down-when-looped" unavailable in the Cisco IOS XR router.
The command is used to bring down the serial interface on the remote router especially in the following scenario:
The remote router is configured to loopback mode; the XR router should identify the remote loopback and bring the serial interface down.
Conditions:Currently the remote interface is identified and displayed as part of the "show interface serial" command. The issue occurs when the interface has to be brought down using a CLI command.
Workaround:No known workaround exists. The code to bring down the remote interface is currently under implementation.
More Info:NA
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: * | 4.3.2.22i.BASE, 4.3.2.22i.FWDG, 5.0.1.8i.FWDG, 5.1.0.13i.BASE, 5.1.0.13i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux76208 | Title: | [533] flow monitor fmm2 cache not showing BGPNextHopV6 entries |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
show flow monitor fmm2 cache is not showing entries under the v6 next hop field BGPNextHopV6 as expected,
Conditions:
after configuring flow monitor,and while sending v4 and v6 traffic streams.
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.26i.BASE, 6.0.1.14i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw76004 | Title: | coa service de-activate fails to remove the service[533 12i] |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:coa service deactivation fails to remove the service even though the radclient gets ACK
Conditions:create subscriber session with service activate(cisco-avpair += ?subscriber:sa=256_S) and perform COA to deactivate the service , it is failing. service is still exists on the subscriber.
Workaround:NA
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.16i.BASE, 6.0.0.22i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc32974 | Title: | during fast_reset, eCPU stop must be performed before configuration |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
fast_reset of network processor does not always clear issues relating to traffic forwarding.
Conditions:
fast_reset is part of a health monitoring process where when problem is detected in the network processor that can cause traffic related issue, a fast reset of the network processor is performed.
Work around: There is no workaround except to reload of line card.
Workaround:
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.0.28i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud65815 | Title: | qos-ea is blocked by prm_server_ty after QoS in-place modification |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
InPlace modification fails for Typhoon -TR card when modifying a policy with more than 4 queuing classes while queue is not empty.
Conditions:
This problem occurs because the Typhoon -TR card has a queue limit of 8 per port.
When the policy is being modified while traffic running, we need to wait for the queues to be completely drained before allocating queues from the modified policy. Currently we attempt to allocate the queues for the changed policy while the old queues are still being drained. This can cause queue limit to be reached (for typhoon -TR LCs) which would fail the policy modification.
Workaround:
Workaround is to either remove policy from port first, modify policy, then apply modified policy to interface.
Alternatively, stop traffic before modifying the policy.
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.0.BASE, 4.3.1.BASE, 5.1.0.BASE |
|
Known Fixed Releases: * | 4.3.0.39i.BASE, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 5.1.0, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux04919 | Title: | BGP crash at bgp_table_post_bestpath() while flap/bringing up neighbor |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BGP crash after neighbor flap and receiving multiple paths for the same prefix at the same time.
Conditions:
- add-path or best-external or both,
- bring up or down a neighbor or modifying neighbor configurations,
- routes to be received by the router for the same prefix from multiple neighbors at the same time, CE and PE.
- next-hop changes, such as metric or reachability will also contribute.
- The problem occurs with VPN routes, although other route types cannot be ruled out.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 4.1.2.ROUT, 5.3.1.ROUT, 5.3.2.ROUT |
|
Known Fixed Releases: * | 5.2.5.41i.ROUT, 6.0.1.14i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46286 | Title: | ICCP redundancy configuration affects existing MPLS LDP based services |
|
Status: | Fixed |
|
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: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.27i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux27300 | Title: | IPv6 valid lifetime not expiring when set to 0 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IPv6 valid lifetime not expiring when set to 0 for prefix 2001:xxxx:e8:xxx1::/64
Customer has been trying to move gracefully move to a new IPV6 subnet by setting the IPv6 lifetime to 0 on the existing subnet. However its not honoring the configured lifetime of 0 on 2001:xxxx:e8:xxx1::/64
Conditions:
IPv6 valid lifetime not expiring when set to 0 for prefix 2001:xxxx:xx:x1011::/64
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux26950 | Title: | RADIUS source interface config stops working when i/f removed from ISIS |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Configured RADIUS source interface not used as source IP for outgoing RADIUS packets. Outbound interface IP is used as source instead.
- AAA transactions configured to use radius as remote authentication/authorisation/accounting method.
- Radius is configured to use a fixed source interface
(radius source-interface <>, configuration present)
- Radius server will fail transactions as its not able to identify the source interface/client ip address.
(as this is selected based on best local ip look up)
Conditions:
The configured source interface has been removed from ISIS configuration.
- AAA transactions configured to use radius as remote authentication/authorisation/accounting method.
- Radius is configured to use a fixed source interface
(radius source-interface <>, configuration present)
- If the same interface is configured as source interface for protocol ISIS.
- And there is explicit "no source interface" executed for ISIS configuration.
Workaround:
Reapply RADIUS source interface configuration.
Further Problem Description:
Issue may persists when interface is added back into the ISIS configuration.
Issue may also be seen on router reload.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul53390 | Title: | 'sh snmp traps deatail' cmd not working from standby RSP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
show snmp traps command does not work from 'standby' RSP
Conditions:
No specific trigger. This happens at steady state
Workaround:
Use show snmp traps on 'active' RP which is where the output of the command makes sense
Further Problem Description:
This command is NOT required on standby RP. The output of the same command in active RP works as expected
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.2.2.5i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc64988 | Title: | ppp_ma crash due to large aaa attr buffer. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PPP MA process may crash with corrupted stack
Conditions:
One of the following three conditions can cause the crash
1. Large number of tagged attributes for a session
2. Circuit ID attribute is greater than 63 bytes
3. Tunnel-Password IETF attribute is used in the system
Workaround:
workarounds for the above conditions in order
1. Use less number of tagged attributes. Reduce the possible number of LNS destinations to less than 10.
2. Check if it is possible to change the circuit-id length to less than 63.
3. Use l2tp-tunnel-password Cisco VSA instead of IETF tunnel-password attribute
More Info:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.1.10i.BASE, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 5.0.1, 5.0.1.8i.FWDG, 5.1.0, 5.1.1, 5.1.11 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux43034 | Title: | PTP with ARB mode - Slave port stays unqualified after RSP switchover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After a reload or RSP switchover, it can be observed that PTP slave port stays unqualified.
This behavior can be seen independently of the timescale that is being used (PTP or ARB)
Conditions:
This behavior can be seen after a router reload or RSP switchover
Workaround:
There is no workaround
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux34074 | Title: | 533.19I: dhcpv6 database feature does not work as expected |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
With DHCPv6 SRPB [database command], when the full-write-interval is a multiple of incremental-write-interval, the full write file is not carrying the all the binding information.
dhcp ipv6
database full-write-interval 10 incremental-write-interval 5
Conditions:
dhcpv6 database command is configured
full-write-interval is a multiple of incremental-write-interval
Workaround:
full-write-interval should not be multiple of incremental-write-interval
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 5.3.3.23i.BASE, 5.3.3.23i.FWDG, 6.0.1.12i.BASE, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw95895 | Title: | Ingress FIA drops packets with priority 3 when ingress policy sets EXP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
An ASR 9000 Tomahawk linecard experiences poor fabric forwarding performance and FIA tail drops for ingress MPLS packets.
FIA classifies the packets as priority 3, when ingress policy sets EXP bit.
Conditions:
This may occur when an MQC service-policy with set mpls experimental topmost action is applied in the ingress direction on the Tomahawk LC.
Issue is only applicable to Tomahawk LC (ingress)
Workaround:
It may be possible to achieve the desired mpls marking behavior without ingress exp topmost marking, by using ingress exp imposition marking, ingress qos-group marking, and/or egress exp topmost marking. These actions will not trigger the bug.
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.3.19i.BASE, 6.0.0.24i.BASE, 6.0.1.12i.BASE, 6.1.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux59453 | Title: | Image downgrade aborted because a removed LC encountered errors |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
Image downgrade aborted because a removed LC encountered errors
Conditions:
swap LC on different slots
Workaround:
process restart inst_mgr
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75546 | Title: | DR/BDR changes on switchover with NSR enabled in LAN segment |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Even though OSPF NSR is enabled, neighbor DR/BDR status change after the NSR enabled node undergoes RP switchover/failover in a LAN scenario where more than 2 routers are there on a LAN segment and the node being switched over is a DR.
Neighbor DR/BDR changes because the NSR node send the Hello packet which shows the that both of DR and BDR are the old BDR neighbor.
Conditions:
If the NSR enabled node was DR and it has BDR as the neighbor, there are multiple (more than 2) routers on the LAN and the NSR enabled DR node undergoes RP switchover/failover.
Workaround:
There is no 100% reliable way to detect whether this error condition exists on the standby. One way is to check for any discrepancy for DR/BDR between the "show ospf neighbor" and "show ospf standby neighbor" command outputs - but there may be a cosmetic discrepancy even after this fix due to CSCux85138
Following workarounds are possible:
1) Before doing switchover do process restart for the standby OSPF process and wait for it to come up again and become NSR ready before doing switchover.
2) Disable and then enable of NSR at OSPF config and then wait for NSR ready before doing switchover.
3) The DR change will not happen if the router undergoing switchover is not the DR and NSR is not enabled on it
Further Problem Description:
The issue is because OSPF on standby does not setup the DR and BDR state correctly when it is the DR in certain states. So if there is any interface event (or if another NBR goes down after initially being up), then the state stored on the standby gets messed up.
If there is a switchover after this state, then the DR would flap.
This is a day 1 issue since NSR was introduced on XR for OSPFv2 onwards and is applicable to all XR platforms. However, the likelyhood of hiting this issue is only when there is a LAN (i.e. more than 2 routers on the LAN).
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 4.3.4.BASE |
|
Known Fixed Releases: | 5.2.5.31i.ROUT, 5.3.3.16i.ROUT, 6.0.0.20i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut19959 | Title: | Pause-frame injection stuck in IDMA cause Tomahawk NP reset for 10G int |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms:
A vulnerability in flow control processing of Cisco IOS XR for Cisco ASR 9000 Series Routers could allow an unauthenticated, adjacent attacker to cause a NP chip
reset and potentially a reload of the affected line card.
The vulnerability is due to improper processing of crafted IEEE 802.3x flow control pause frames. An attacker could exploit this vulnerability by sending a number of
crafted IEEE 802.3x flow control pause frames to an affected device. An exploit could allow the attacker to cause a NP chip reset and potentially a reload of the
affected line card.
Conditions:
- Cisco ASR9000 with Tomahawk based line card running post 5.3.0 software.
- Cisco IOS XR device does NOT have to be configured to process IEEE 802.3x flow control frames from an adjacent L2 device. Apart from an ethernet interface in
enabled state reachable by a L2 adjacent neighbor, no configuration is required for this vulnerability to be exploited.
Workaround:
None.
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 5.7/4.7:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:A/AC:M/Au:N/C:N/I:N/A:C/E:F/RL:OF/RC:C&version=2.0
CVE ID CVE-2015-4205 has been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.1, 5.2.2, 5.2.21, 5.3.1, 5.3.1.28i.BASE, 5.3.2.6i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw80087 | Title: | VPLS routes withdrawn after adding new bridge-domain with VFI |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
VPLS routes withdrawn are withdrawn and PW are down.
Conditions:
when "soft-reconfiguration inbound always" is configured under "address-family l2vpn vpls" and a new "Bridge-Domain" is configured, we replay the rcvd-routes and some how end up removing the existing paths too.
Workaround:
remove the soft-reconfiguration inbound always under address-family l2vpn vpls.
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.2.4.ROUT |
|
Known Fixed Releases: * | 6.0.1.16i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux85576 | Title: | RSP reload interrupted upon detection of unresponsive HD |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ahci_mon detected unresponsive SSD.
To clear unresponsive state of disk, process initiated RSP reload call but it could not get mature.
Conditions:
Disk unresponsive or hang detected by ahci_mon process.
ahci.log content in RSP hang case:
AHCI: failure /dev/hd0: npass=21, sector=0x13c50400, fail count=16/16
AHCI: My Nodeid=0x11, Partner Nodeid=0x21, Primary=1 devb-ahci_pid=45079
AHCI: redundancy_state=REDUNDANCY_ACTIVE, standby_state=STANDBY_STATE_DOWN, boot_protocol=10
AHCI(1): device not responding, reloading 0x11
ahci.log content in RSP error case:
AHCI: failure /dev/hd0: npass=29, sector=0x30e6a200, fail count=16/16
AHCI: My Nodeid=0x11, Partner Nodeid=0x21, Primary=1 devb-ahci_pid=45079
AHCI: redundancy_state=REDUNDANCY_ACTIVE, standby_state=STANDBY_STATE_DOWN, boot_protocol=10
AHCI(2): device not responding, reloading 0x11
Workaround:
NA
Further Problem Description:
AHCI_MON detected RSP not responding and triggers reload but reload call could not mature. This resulted in other processes i.e. watchdog detected wedge and crashed with core resulting RSP reload.
Jan 14 2016 02:26:08.182469 10.207.93.1 local7.critical 13278: RP/0/RSP1/CPU0:Jan 14 02:26:08.168 BKK: pfm_node_rp[356]: %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Set|ahci-mon[36889]|SATA Disk(0x1000000)|HD0 device not responding
Jan 14 2016 02:28:38.452033 10.207.93.1 local7.error 13279: RP/0/RSP1/CPU0:Jan 14 02:28:38.439 BKK: ahci-mon[65561]: AHCI: failure /dev/hd0: npass=492687, sector=0x2bd71200, fail count=16/16
Jan 14 2016 02:28:38.466985 10.207.93.1 local7.error 13280: RP/0/RSP1/CPU0:Jan 14 02:28:38.445 BKK: ahci-mon[65561]: AHCI: My Nodeid=0x51, Partner Nodeid=0x41, Primary=1 devb-ahci_pid=36887
Jan 14 2016 02:28:38.481979 10.207.93.1 local7.error 13281: RP/0/RSP1/CPU0:Jan 14 02:28:38.447 BKK: ahci-mon[65561]: AHCI: redundancy_state=REDUNDANCY_ACTIVE, standby_state=STANDBY_STATE_READY, boot_protocol=10
Jan 14 2016 02:28:38.496963 10.207.93.1 local7.emergency 13282: RP/0/RSP1/CPU0:Jan 14 02:28:38.449 BKK: ahci-mon[65561]: AHCI(1): device not responding, reloading 0x51
Seen this behavior with UNIGEN disk
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.3.3.24i.BASE |
|
Known Fixed Releases: * | 6.0.1.16i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw48958 | Title: | NP / LC Resets after CFM enabled on the SAT ICL Links |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When CFM enabled on Satellite ICL links and with CFM up MEPS on Satellite access ports, after LC/Satellite reload, CFM DMR packets going through VPLS PW causes NP resets.
Conditions:
All following conditions to be met:
- CFM enabled on Satellite ICL links.
- CFM Up MEPS on Satellite access ports.
- CFM DMR packets should go through VPLS PW path.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.16i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux92606 | Title: | BGP RR does not advertise rt-routes to non RRC without cluster-id config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When the best path is from a router reflector client neighbor, bgp may block the update. if debug bgp update is turned you, you will see following in the debug: "Deny 1 UPDATE to filter-group 0.3 (regular, pelem regular) for ... ... reason cluster id not set for RR client: 1.1.1.1"
Conditions:
This will only happen on router reflector. cluster id is not configured under router bgp.
Workaround:
restart of process bgp
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: | 6.0.1.16i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux19443 | Title: | BNG not offering new address per DHCP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Two unexpected behaviors:
1. DHCP server will continue to offer a particular address for approximately 4 minutes, on 2s intervals, then it will begin to offer a different one. At the point that it begins to offer a different address is when the BNG proxy bind state goes to from OFFER_SENT to SELECTING. However the BNG continues to record the initially offered address in the bindings table, not the new one(s) that DHCP server has switched to.
Expected behavior is to forward the new-IP OFFER if the 'server-ip' is same.
2. The beginning of the BNG selecting state coincides with the moment that the DHCP server starts offering a different address. Once the BNG goes to selecting state, it stops proxying the subsequent addresses that the DHCP server tries to offer. If the BNG is forced to clear the selecting state proxy record, then it resumes offering whatever the DHCP server is offering, until the DHCP server changes again, at which time the BNG returns to selecting state. In some cases the client accepts during the BNG offer state and the session is built. We don't know why some leases are accepted by the clients/modems and some are not. However it is evident that as long as the BNG remains stuck in selecting state, the session does not get built.
Expected: Newly offered IP from 'same' server has to be forwarded. 'Selecting' state means, either OFFER didn't reach or dropped for some reason.
Conditions:
Workaround:
Clear the older binding. New DISCOVER from client should bring-up the client properly.
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.FWDG, 6.1.0.11i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw35524 | Title: | ASR 9001 ipv4_rib crash @ rib_route_copy_to_client_route |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ipv4_rib process crash on ASR9001
Conditions:
The problem was reported on ASR9001 running 5.2.2
Workaround:
NA
Further Problem Description:
RC: This happens when there is lookup on a route, where the resolving route has backup paths (P/Q nodes).
There is an improper calculation of expected buffer size (buffer for the route to be packed on a lookup). This results in the assert and crash.
Platforms: Affects all platforms.
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.2.2.ROUT, 5.2.4.ROUT |
|
Known Fixed Releases: * | 4.1.0, 4.1.1, 4.1.2, 5.3.3.21i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy04355 | Title: | [601]-Sconbkup traceback and Router reload fails after triggered reload |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Sconbkup traceback and Router reload fails after triggered reload
Conditions:
while running satellite regression could see Sconbkup error while triggering router reload and router reload never gets triggered. Issue is inconsistent and it occurs very randomly.
Once we hit the problem, our testing is blocked, only way to recover the chassis is to perform "reload location all force".
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux08668 | Title: | Framed IP not sent in accounting stop record |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
With BNG as dhcpv4 proxy , observing framed ip is missing in the accounting stop message.
Also circuit-id is not present in accounting stop message.
Conditions:
This is seen in 5.3.2
Workaround:
There is no workaround.
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 5.3.3.26i.BASE, 6.0.1.12i.BASE, 6.1.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux79329 | Title: | OSPF process running for instance removed from config |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
The show commands ('show ospf...') are displaying info for ospf instances that were removed from configuration earlier.
Also, removed ospf instances are still running on both RSPs (in "show placement program ospf"output).
Conditions:
ASR9k running 5.3.2, with very frequent OSPF configuraton changes.
Workaround:
Not known at this time
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui95985 | Title: | CISCO-SUBSCRIBER-SESSION-MIB doesnt work after RSP FO in ASR9010 Cluster |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In the event of ASR9010 Cluster Switchover from Active to Backup or vice-versa, the CISCO-SUBSCRIBER-SESSION-MIB MIBS fail to function or respond
Conditions:
ASR9010 Cluster Switchover from Active to Backup or vice-versa
Workaround:
process restart session_mon
Further Problem Description:
CISCO-SUBSCRIBER-SESSION-MIB MIBS fail to function or respond when ASR9010 Cluster Switchover happens. Network Management Station will not be able to monitor PPPoE Subscriber sessions.
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 4.3.4.5i.BASE, 4.3.4.5i.FWDG, 5.1.1.11i.BASE, 5.1.1.11i.FWDG, 5.1.11.4i.BASE, 5.1.11.4i.FWDG, 5.1.2.1i.BASE, 5.1.2.1i.FWDG, 5.2.0.7i.BASE, 5.2.0.7i.FWDG |
|
|
| |
| |
|
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: | 31-JAN-2016 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: * | 5.3.3.22i.ROUT, 6.0.1.12i.ROUT, 6.1.0.7i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux59517 | Title: | te_control traceback @te_lmrib_process_results |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
te_control trackback pop few min
Conditions:
while core lc reload or core interface flap
Workaround:
none needed
Further Problem Description:
|
|
Last Modified: | 01-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj22280 | Title: | eem maxrun timer not handled properly |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In event manager script, maxrun timer is expiring sooner than expected when set to maximum value.
Conditions:
Workaround:
Use a watchdog of 180 seconds as trigger so if it expires the script automatically restarts immediately after expiry.
Further Problem Description:
|
|
Last Modified: | 04-JAN-2016 |
|
Known Affected Releases: | 4.2.3.MGBL |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.13i.BASE, 5.1.11, 5.1.11.8i.BASE, 5.1.12, 5.1.2, 5.1.2.5i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui40703 | Title: | PW notification msg sending different encap types (vlan,Ethernet) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Due to the different encapsulation types included in notification messages, 3rd party remote end is unable to process the notification due to encapsulation mismatch. The PW does not come up.
Conditions:
The PW transport-mode must be configured as vlan.
The Notification and MAC withdrawal messages are impacted.
These messages are issued when the interface is shutdown and no shutdown for example.
IOS-XR does not enforce the VC type received in the Notification and MAC withdrawal messages.
3rd party Huawei brings down the PW if VC type differs in the Notification message.
Workaround:
No workaround with Huawei.
The issue is not present for IOS-XR to IOS-XR.
Further Problem Description:
|
|
Last Modified: | 04-JAN-2016 |
|
Known Affected Releases: | 4.2.3.MPLS |
|
Known Fixed Releases: * | 4.3.4, 4.3.4.5i.FWDG, 5.0.1.99i.BASE, 5.1.1, 5.1.1.12i.FWDG, 5.1.11, 5.1.11.4i.FWDG, 5.1.12, 5.1.2, 5.1.2.2i.FWDG |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux22560 | Title: | Standby RP goes NOT ready state when new SFC is installed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Standby RP goes "NOT ready" briefly during the FC OIR
Conditions:
FC OIR
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | 5.3.3.23i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq89694 | Title: | Link is not comingup with hardcoded speed/duplex on pre-provisioned port |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Copper sfp link is not coming up with hard coded speed & duplex configured on port
Conditions:
1. Configure speed 100 & duplex on pre-provisioned port
2. Insert copper sfp
3. Link will not come up
Workaround:
Default the interface config and re-apply the config.
Further Problem Description:
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 5.1(3) |
|
Known Fixed Releases: * | 15.1(3)SVF04f, 15.1(3)SVG01c, 15.1(3)SVG03, 15.1(3)SVG03a, 15.1(3)SVH02 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui95665 | Title: | Remote link unexpectedly comes up for asr9000v admin-down link |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A link comes up unexpectedly on a remote switch/router even though a local link is in admn-down state on asr9000v.
Conditions:
When an SFP is removed and then inserted again.
Workaround:
No shutting down and shutting down a satellite interface or reloading an asr9000v.
Further Problem Description:
|
|
Last Modified: | 06-JAN-2016 |
|
Known Affected Releases: | 4.3(1) |
|
Known Fixed Releases: * | 15.1(3)SVF04b, 15.1(3)SVF04c, 15.1(3)SVF04f, 15.1(3)SVG02, 15.1(3)SVH |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw33091 | Title: | ASR9K netconf_agent_tty process crash |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR9K experienced a netconf_agent_tty process crash.
From 'show log' see the following:
RP/0/RP0/CPU0:Aug 25 04:14:04 PST: dumper[60]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0xffffffff at PC 0x82a9083. Signal code 2 - SEGV_ACCERR. No permission."",,null,457"
Conditions:
ASR9922
RP redundancy; ASR-9922-RP-TR
Software: 5.3.1
Netconf is configured on router and used to poll data.
Workaround:
None. Process restarts and resumes working on its own.
Further Problem Description:
Only seen one time on router running 5.3.1.
If this process crash is seen, along with other outputs, can collect the following commands:
show mda trace
show xml trace
show management netconf mda trace
show management netconf client trace
show management netconf tty trace
show management netconf trace
show management xml mda trace
show management xml trace
show management xml client trace
show management xml tty trace
|
|
Last Modified: | 07-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux20093 | Title: | Drop @PARSE_FAST_DISCARD_LOW_PRIORITY_DROP for NAT44 Performance Test |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: * | Drop @PARSE_FAST_DISCARD_LOW_PRIORITY_DROP for NAT44 Performance Test
Symptom:
Drop @PARSE_FAST_DISCARD_LOW_PRIORITY_DROP for NAT44 Performance Test
- Problem seen in the ingress LC (Typhoon)
Conditions:
Drop @PARSE_FAST_DISCARD_LOW_PRIORITY_DROP for NAT44 Performance Test
Reported in the following
- increased line rate
- certain packet lengths as mentioned in the description - on higher packet lenghts, problem is not seen.
- in the ingress LC
Workaround:
- Different packets lengths.
- Not seen in regular traffic tests.
Further Problem Description:
np_perf_;log command shows higher average utilization on the ingress LC's NP1. And less utilization on the VSM.
These drops are part of FAST_DISCARD drops in the NP code. Reasons to be ascertained on why such FAST_DISCARD drops are happening. and hence checking ucode team.
|
|
Last Modified: | 08-JAN-2016 |
|
Known Affected Releases: | 6.0.0.LC, 6.0.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc18645 | Title: | 'invalid/unused user index in db' err msgs on clearing nat64 stats |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
invalid/unused user index in db' err msgs on clearing nat64 stats
Conditions:
invalid/unused user index in db' err msgs on clearing nat64 stats
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-JAN-2016 |
|
Known Affected Releases: * | 4.3.0.BASE, 5.2.2.LC, 5.3.1.BASE, 6.0.1.LC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw79889 | Title: | LBK: show run with dwdm PM configured displays garbled log messages |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
'Show running- config' displays garbled messages when PM (Performance Monitoring) configurations exists on controller dwdm on A9K-400G-DWDM-TR line card.
RP/0/RP0/CPU0:Oct 19 12:31:40.312 : nvgen[353]: %MGBL-NVGEN-3-TOKENTYPE : nvgen_token_replace: token 1, old type:9, new:8 cmd:'controller dwdm0/7/0/0^Z201,37^C^Z202,37^C^Z203,37^C^Z204,37^C ^Z\n!if/<199>/<200>/aza=\n^C^Gpm 15-min optics threshold ^DB1^Elbc ^DB2^Emin ^Z10002,FAILSET^C50 ^DN2^Emax ^Z10002,FAILSET^C50 ^DE2,s^E ^DN1^Eopt ^DB2^Emin 50 ^DN2^Emax ^Z10002,FAILSET^C50 ^DE2,s^E ^DN1^Eopr ^DB2^Emin ^Z10002,FAILSET^C50 ^DN2^Emax ^Z10002,FAILSET^C50 ^DE2,s^E ^DN1^Ecd ^DB2^Emin ^Z10002,FAILSET^C^B1,8,-,11170,+,11170^C ^DN2^Emax ^B2,
If the PM configurations are removed, garbled messages are not shown.
Conditions:
SW image used : asr9k-mini-px-5.3.3.14I, asr9k-optic-px-5.3.3.14I
HW used : A9K-RSP880-SE or A99-RP2-SE and A9K-400G-DWDM-TR
Config : PM configs applied on controller DWDM A9K-400G-DWDM-TR line card.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux08474 | Title: | L2fab-multiple ICL-14i-traffic dropped in between and not restoring back |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Access port drops the traffic, if ICL and nv satellite configuration is removed and readded.
Conditions:
Removing ICL configuration followed by global nv satellite configuration and reapplying in same order lead traffic drop at access port in Multiple ICL feature.
Workaround:
Satellite Reload
Further Problem Description:
none
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0(0) |
|
Known Fixed Releases: * | 15.1(3)SVJ |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux24587 | Title: | eXR: sh using "ssh rsp0" hangs - ssh rsCould not determine IOFPGA |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
sh using "ssh rsp0" hangs.
Conditions:
Execute "ssh rsp0" command.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux15779 | Title: | mbi-hello crash after "reload location all" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MBI-Hello process crash is observed on ASR9k router running 5.3.3. code
Conditions:
The crash is observed when reloading the router using the CLI command "reload location all" from the admin prompt
Workaround:
This is a rare condition and is not consistently reproducible. It occured only once after 10 retries on the system. The node recovers without any other issues after the crash and all traffic resumes completely.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw46460 | Title: | ROUTING-FIB-3-PD_FAIL FIB Cannot insert leaf for pfx pointing to Null0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Following syslog might be seen if route resolves through Null0 on ASR9K 3rd generation Ethernet line card.
fib_mgr[185]: %ROUTING-FIB-3-PD_FAIL : FIB platform error: fib_leaf_insert 5193 Cannot insert leaf
Conditions:
/32 route updated with next hop recursing through Null0
Workaround:
Disable BGP PA.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.1.FWDG |
|
Known Fixed Releases: * | 5.3.3.18i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux25782 | Title: | ASR9K: TS_FBL TABLE message during boot. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
TS_FBL Table message appears during IOS-XR Boot.
Conditions:
This behavior is observed when IOS-XR boots during card reload.
So, TS_FBL Table message appears every time during IOS-XR boot.
Workaround:
The print statement displaying TS_FBL TABLE message during IOS-XR boot has to be removed.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.1.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw65230 | Title: | Failed to show o/p of specific transient pbr policy & oper schema issues |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
show policy-map transient type pbr pmap-name
Conditions:
Not displaying when the transient policy-map is available
Workaround:
N/A
Further Problem Description:
N/A
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux54800 | Title: | Unable to Remove ACL in Global mode on IOX-XR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Customer receives the below message when trying to remove an ACL from Global mode eventhough the ACL has been removed from all interfaces on the line cards.
no 10 permit icmp host 10.10.10.1 host 10..10.20.105 echo
!!% File exists: ACL is being used by the following clients,Detach the access list from all the clients and then remove ACL
process : pkg/bin/pal_pfilter_ea pid : 184424 node : node1_0_CPU0
Conditions:
Running IOS-XR. Seen on line card with POS interfaces and SIP-700.
Also the hardware-count option within an ACL was attempted to be committed (applied)
to the POS interface. For example. please see hardware-count option below
RP/0/RSP0/CPU0:Router(config)#int pos 1/0/0/3
RP/0/RSP0/CPU0:Router(config-if)#ipv4 access-group icmp egress hardware-count interface-statistics
RP/0/RSP0/CPU0:Router(config-if)#ipv4 access-group icmp ingress hardware-count interface-statistics
RP/0/RSP0/CPU0:Router(config-if)#commit
Workaround:
Two different Recoveries
1) process pal_pfilter_ea location
2) Reset the line card (hw-module location
WorkAround:
Do not try to commit an ACL with the hardware-count option to a POS interface. Please see conditions.
Further Problem Description:
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.3.25i.BASE, 6.0.1.13i.BASE |
|
|
| |
| |
|
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: | 11-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup47120 | Title: | ASR9k BNG-subscriber route not withdrawn from RIB upon initiator change |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In a IPoE dual-initiator environment (initiator dhcp + unclassified source on same access interface), if a subscriber with an established packet-trigger session suddenly changes to a DHCP client, the original /32 subscriber route from the packet-trigger session is never withdrawn, leaving a stale route in the RIB pointing to Unknown:
Routing entry for 10.1.1.5/32
Known via "subscriber", distance 2, metric 0 (connected)
Installed Jun 13 17:33:39.561 for 00:01:39
Routing Descriptor Blocks
directly connected, via Unknown
Route metric is 0
No advertising protos.
Conditions:
This occurs on ASR 9000 BNG deployments with both DHCP and unclassified source initiators on subscriber access interfaces, through XR 4.3.4 and 5.1.2.
Workaround:
None. To recover the stale subscriber is by manually clearing the stale route with "clear route ipv4 unicast x.x.x.x/32"
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.1.3.15i.BASE, 5.2.2.15i.BASE, 5.2.3.1i.BASE, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq07098 | Title: | ASR9k: iedge process crash on re-authorization failure |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
iedge process crash
Conditions:
if re-authorization fails (reject from Radius)
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.2.20i.BASE, 5.2.3.8i.BASE, 5.3.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo55811 | Title: | show pool vrf fails with 8k DAPS pool |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"show pool vrf", "show pool ipv4" and "show pool ipv6" commands produce incorrect output.
Conditions:
Issue happens only when there are more than 100 address-range entries configured on the system.
Workaround:
Use "show pool ipv4 name " and "show pool ipv6 name " commands to retrieve the required address pool information.
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.25i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur76163 | Title: | DHCP crash observed in 5.2.0 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The DHCP process may crash on the Cisco ASR9000 platform.
Conditions:
With the binding in bound state, if the client tries to rebind the address without \
setting ci-addr, when receiving ACK with different IP address than the already \
bound IP address, the current BNG session is sent for disconnect and while reinit \
fetching the profile from the interface fails as it is an ACK packet from the \
server facing interface(which does not have any profile attached), hence the packet \
is enqueued and freed. When the disconnect response is received from iedge,
dequeuing and accessing the packet leads to this crash.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.2.SP1, 5.2.4.4i.FWDG, 5.3.0.17i.FWDG, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf52825 | Title: | Fake pfm alarms against CFP-SR10, unsupported phy fields |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
======
LOW_POWER & LOW temp pfm alarm is raised for CFP-SR10 optics for which DOM feature is not supported.
Condition:
======
4.3.x release. No impact to traffic or 100G functionality.
Workaround:
=======
This is a fake pfm alarm.
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 4.3.1.BASE, 5.1.0.BASE, 5.1.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.17i.BASE, 5.1.1, 5.1.11, 5.1.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu95934 | Title: | Sessions not syncing to slave post vpdn_mgr restart on master |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
All 16k sessions not coming up on slave, after vpdn restart on master.
Conditions:
vpdn_mgr restart on master
Workaround:
Further Problem Description:
It is SRG issues and negative test case.
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu76866 | Title: | debug subscriber manager session with filter-id does not work |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Debug command 'debug subscriber manager session next-subscriber filter-id mac-address xxxx.xxxx.xxxx' does not generate any logs
Conditions:
None. All the time the command does not generate any log
Workaround:
debug command without filter id can be used:
"debug subscriber manager session all"
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.1.3.TOOLS |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.14i.BASE, 6.0.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus88647 | Title: | ASR9K/5.2.2 dhcp vendor class information is not send in radius packets |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR9K does not send the dhcp vendor class information in radius request packets.
Conditions:
ASR9K running 5.2.2.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.4.6i.FWDG, 5.3.1, 5.3.1.21i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus14705 | Title: | In-place modification of pools create duplicate entries in DAPS database |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Checkpoint deletion failures, DUPLICATE-ADDRESS errors and incorrect show pool output are side effects of this problem.
Conditions:
Issue will happen only if customer deletes/shrinks in-service address pool and reconfigures the deleted addresses under same/different pool.
Workaround:
Do not delete/shrink address pools when they are in use.
Further Problem Description:
If the issue occurs, the only way (other than reload) to recover the system is to restart 'daps' process after bringing down all existing sessions. New session requests should not be allowed when the workaround is being applied.
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 4.3.2.FWDG |
|
Known Fixed Releases: * | 5.2.4.3i.BASE, 5.3.1, 5.3.1.15i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus25426 | Title: | Request for chaddr 0000.0000.0000 clients support in IOS-XR dhcp-relay |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR9k/5.2.0 configured for dhcp-relay
DHCP Discover CU sends over MLPPP being dropped
Conditions:
DHCP Discover chaddr set to 0000.0000.0000
that packet gonna be dropped as invalid with the following log
dhcpd[164]: DHCPD: TP4809: Packet Validation failed: BAD MAC address received 0000.0000.0000
Workaround:
unknown yet
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.17i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv54038 | Title: | [513] Some sessions are stuck in disconnecting even after CSCul82895 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
sessions are stuck with "SvcAcct-Final>StatsD" in Pending Callbacks (sh subs sess all det inter)
Conditions:
generally seen with high churn of sessions with large number of services enabled with interim accountin
Workaround:
not available
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: * | 5.3.2.20i.BASE, 5.3.3.8i.BASE, 6.0.0.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur02566 | Title: | Failed in envmon_edm_sensors_get_value on polling entitySensorMIB |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
I am observing following error messages 4/5 times on console every time I poll entitySensorMIB
%PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in envmon_edm_sensors_get_value.10678, error code incorrect sensor name, quitting EDM
Conditions:
Polling entitySensorMIB
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 14-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.3.0, 5.3.0.12i.BASE, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74719 | Title: | when use FC4, only one link btw FIA and XBAR on MOD400 is used |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Only one link out of 4 between FIA and XBAR on 400MOD card is used while any FC and FC4 are present only.
Conditions:
the problem only happens when you use FC4 and any other one FCs
Workaround:
if you only use two FC in the ASR9912/ASR9922 chassis, just don't let FC4 be one of them
Further Problem Description:
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.26i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu46234 | Title: | [532]iedged traceback while sending CoA for already disconnected session |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
iedged Traceback seen while sending CoA
Conditions:
While sending CoA for an already disconnected session
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.11i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun59675 | Title: | show subscriber session all adjustment/addition |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
show subscriber session to provide an option to print username, interface and address
Conditions:
bng
Workaround:
use show subscriber session all and show subscriber session all user to derive the desired info.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 4.3.4.BASE, 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.4, 5.2.0, 5.2.0.19i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut69809 | Title: | SSTE: DHCPv6d crash by Wdsysomn due to FD leak on Trident LC. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:dhcpv6d process may crash by Wdsysmon due to FD exceed 95% threshold.
Conditions:The FD leak are triggered by dhcpv6d process try to write to harddisk and failed. Failure is caused by harddisk access issue.
Once the number of FD opened reached 85% of Wdsysmon limit of 1000, warning message from Wdsysmon will be printed. Once number FD reach 95% of Wdsysmon limit ( 1000), process will be restarted.
Workaround:Process restart dhcpv6d to free up FD.
More Info:The issue is caused by harddisk access issue. Need to ensure harddisk is not full so files can be written to harddisk.
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.2, 5.3.2.5i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun26500 | Title: | pos subinterface removal failing due to fr-uv error subinterface exists |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When removing a Serial/POS/FR interface the commit will fail
Conditions:
Normal operation
Workaround:
-- Restart fr_uv process on the affected node
The workaround has no impact on data switching
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.12i.FWDG, 5.1.4, 5.2.1, 5.2.1.25i.FWDG, 5.2.2, 5.2.2.13i.FWDG, 5.2.21, 5.3.0, 5.3.0.1i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq76508 | Title: | [522] CoA Nack'ed for SPI and policy-map name change |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CoA NACK for policy name change
Conditions:
Policy name change
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.2, 5.2.2.25i.BASE, 5.2.21, 5.2.3.12i.BASE, 5.2.4.1i.BASE, 5.3.0, 5.3.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus66426 | Title: | SSTE: DHCPv6 shoudl free memory after VRF unconfigured. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
dhcpv6d process may continue holding memory after vrf unconfigured.
Conditions:
Configuring & un-configuring VRF on the system, with DHCPv6 enabled.
Workaround:
Memory will be freed after reload.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.3.0.BASE, 5.3.1.BASE |
|
Known Fixed Releases: * | 5.3.1, 5.3.1.18i.FWDG, 6.0.0.5i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur17492 | Title: | 522-No aaa config CoA is not returning administratively-prohibited error |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Incorrect CoA reply
Conditions:
with no aaa config could see incorrect CoA reply
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.2.29i.BASE, 5.2.3.12i.BASE, 5.2.4.1i.BASE, 5.3.0.14i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul18900 | Title: | Crash seen while trying to commit a specific set of IPv6 pools twice |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
DAPS process crashes while trying to commit a set of ipv6 pool prefix-length configuration twice.
Conditions:
Issue is not consistent. The problem only happens with ipv6 prefix pool.
Workaround:
If there is a requirement to re-apply a configuration, remove the prefix pool configuration and reconfigure it, once the other configuration is commited.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.15i.BASE, 5.1.11, 5.1.12, 5.1.2, 5.1.2.7i.BASE, 5.1.3, 5.1.4, 5.2.0, 5.2.0.10i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv92521 | Title: | iedged attribute leak at policy_format_author_username |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
iedged heap memory consumption will increase periodically. iedged process will crash after heap memory consumption reaches to around 800MB.
Conditions:
periodically reauth user.
Workaround:
restart iedged process from exec command prompt.
example: process restart iedged
Further Problem Description:
this issue will be hit if we reauth user periodically. For example if we configure to reauth user every 5mins, Please check the heap memory consumption after evry 5 mins. heap memory consumption will increase same number of bytes every 5mins depending on the user profile contents. after heap memory consumption reaches around 800MB, iedged process will crash.
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.9i.BASE, 6.0.0.17i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj00903 | Title: | acct-stop for IPv6 l2 session with IA_NA&IA_PD does'nt have v6addr |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IPv6 address not included in the account-stop record.
Conditions:
Client sends a release message on an IPv6 l2connected session with both IA_NA and IA_PD.
Workaround:
No known workarounds.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: * | 5.1.1, 5.1.1.14i.BASE, 5.1.11, 5.1.11.8i.BASE, 5.1.12, 5.1.2, 5.1.2.5i.BASE, 5.1.3, 5.1.4, 5.2.0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup66694 | Title: | 522:rtdsub: Few sessions remain in disconnecting state out of 64k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Few sessions remain in disconnecting state out of 64k, during idle-timeout disconnection of 64k routed v6 subscriber sessions.
Conditions:
Idle timeout disconnection of 64k pkt triggerd routed sessions
Workaround:
Disconnection happens after 30 min
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.31, 4.3.4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo59655 | Title: | COA error cause/string add to Resp failed when previous COA in progress |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
when a coa request is received previous coa request was already in progress, hence it supposed to send NAK with "internal error? cause and error
String as "Previous COA request on subscriber still pending to complete.? but looks like there is a bug in code due to which error cause/string addition to
Response failed
Conditions:
when a coa request is received previous coa request was already in progress
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.1.3, 5.1.3.13i.BASE, 5.1.4, 5.2.0, 5.2.0.25i.BASE, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup20354 | Title: | ipsub_ma crash @ ipsub_ma_vrf_table_rib_add_callback during RPFO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ipsub_ma process crashes during RP failover
Conditions:
This is a timing issue and occurs only in a rare scenario. Issue is usually triggered by access interface flap during RP swithover
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.2.2, 5.2.2.14i.BASE, 5.2.21, 5.3.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur17509 | Title: | [522] PPPoE sessions are not going down after changing the service-type |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PPPoE sessions are not going down
Conditions:
After Service-type change, sessions are not going down
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE, 5.3.0.BASE |
|
Known Fixed Releases: * | 5.2.2.29i.FWDG, 5.2.3.12i.FWDG, 5.2.4.1i.FWDG, 5.3.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun56013 | Title: | [520] iedged crashes after incorrect framed route CoA request |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Iedged crash after CoA request
Conditions:
After sending incorrect CoA request could see iedged is crashing
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: * | 5.2.0, 5.2.0.17i.BASE, 5.2.0.17i.FWDG, 5.2.0.17i.MCAST, 5.2.0.17i.MPLS, 5.2.1, 5.2.2, 5.2.21, 5.3.0, 5.3.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv86795 | Title: | ipsub does not provide next hop info for v6 framed routes [533 DT] |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
show ipsubscriber interface dynamic-routes location will not show next hop route for framed subscribers
Conditions:
Seen for v6 framed routes.
Workaround:
none
Further Problem Description:
Bring up ds ipoe LC session with v4 & v6 framed routes from radius .
Observing the framed routes are installed .
Here ipsub does not provide the next hop info ,whereus the rib routes provides next hop LL address.
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.10i.FWDG, 6.0.0.14i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux41064 | Title: | CISCO-CONFIG-MAN-MIB timing out; slow oid's are seen |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
CISCO-CONFIG-MAN-MIB timing out; slow oid's are seen. "show snmp trace request" also confirms this.
Conditions:
Workaround:
block the impacting MIB ( CISCO-CONFIG-MAN-MIB) for NOT processing in snapped process. This can be achieved though snmp
views and you need to apply the View "CISCO" to all their SNMP communities Setup a snmp-view to exclude the below mibs. and process restart snmpd
snmp-server view CISCO 1.3 included
snmp-server view CISCO 1.3.6.1.4.1.9.9.43 excluded
snmp-server view CISCO 1.3.6.1.4.1.9.9.91 excluded
snmp-server view CISCO 1.3.6.1.4.1.9.10.106 excluded
snmp-server view CISCO 1.3.6.1.2.1.10.7.2.1 excluded
snmp-server view CISCO 1.3.6.1.4.1.9.9.84.1 excluded
snmp-server view CISCO 1.3.6.1.4.1.9.9.249.1 excluded
snmp-server view CISCO 1.3.6.1.2.1.10.166.2.1 excluded
snmp-server view CISCO 1.3.6.1.2.1.47.1.1.1 excluded
snmp-server view CISCO 1.3.6.1.4.1.9.9.109.1 excluded
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
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: | 21-JAN-2016 |
|
Known Affected Releases: * | 6.0.0.FWDG, 6.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux88135 | Title: | dot1p cos field not set for locally generated DHCP traffic |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Vlan cos is not updated in the injected DHCP packets towards the PWHE subscribers when ambiguous vlan DHCP configuration is applied.
Conditions:
DHCP configured on PWHE subinterfaces.
Ambiguous vlan configuration is applied.
Workaround:
No workaround as such
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux18150 | Title: | LCC scan shows label inconsistency after tomahawk LC reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The issue occurs on ASR9K chassis having Tomahawk Linecard. Label consistency checker background scan shows some inconsistent labels after reloading the Tomahawk LC.
Conditions:
On a stable router when the Tomahawk LC is reloaded, once the linecard comes back online completely, the label consistency scan shows certain labels as inconsistent between the FIB and LSD on this linecard. These labels are related to prefixes being advertised by both Segment routing and MPLS LDP.
Workaround:
There is no impact on traffic due to this inconsistency message on console. In order to stop these label inconsistency messages on console, the router needs to be reloaded.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.3.MCAST |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux78689 | Title: * | Restore NP fast-reset upon monitor NP counter capture |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unexpected behavior after "monitor np counter <> <> location <>" which may include NP reset or unwanted counter increments.
Conditions:
"monitor np counter" command execution.
Workaround:
Use monitor command with reset option - "monitor np counter <> location <> reset"
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 5.3.3.27i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw99907 | Title: | config process blocked on sysdb_mc after snmp config changes |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The config process may get blocked on the sysdb_mc process resulting in commit failures.
Conditions:
This problem may be triggered by changing the snmp configuration
Workaround:
Restarting the snmpd process may clear the problem
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux59969 | Title: | ASR9K DHCPv6 Proxy replies to both IAIDs with the same XID field |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Client sends a RELEASE for both IAIDs, the ASR9K(Proxy) forwards it to the server then get the reply to the server proceeds to delete both bindings and sends back to the client 2 REPLYs but with the same XID so it will be successful for one prefix but not for the other. As a result of this the Client will send out another RELEASE for the failed prefix and this time the ASR9K will reply back with a "no binding" so it will be released.
Conditions:
ASR9K running DHCP as Proxy for IPv6
Workaround:
Though it doesn't cause any functional impact (follow-up release is responded with no-binding properly)
Further Problem Description:
Two separate release packets are received from client for each IAID, both are forwarded to server and wait for responses; server's release-relay-reply didn't contain the IAID info in it, hence proxy treats first reply as response for both IAIDs and same is forwarded (ignoring the xid field). Second reply from server is consumed.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux62822 | Title: | standby rsp880 fpd info are not shown |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
sby rsp880 fpd version info is not shown
Conditions:
asr9k router running 600 interim image
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.27i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux80366 | Title: | VIDMON Counter Disc JUMP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Vidmon reports sequence errors while monitoring RTP traffic.
Conditions:
Traffic must contain enough jitter that packets arrive within nanoseconds of each other, instead of milliseconds.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.3.4.BASE, 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.27i.BASE, 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83008 | Title: | Policer ID in show lpts pifib hardware police location <> is not unique |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
policer ID is not unique
Conditions:
policer ID is not unique
Workaround:
n/a
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.1.2.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux60253 | Title: | csubAggStatsAuthSessions not supported in ASR9k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The snmpwalk of 1.3.6.1.4.1.9.9.786.1.2.1.1.6 gives a ??No Such Instance currently exists at this OID?? message.
Conditions:
ASR9k with 5.1.3 IOX version
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.1.3.FWDG |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq88828 | Title: | clear logging onboard corrupted-file automatically |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
A ASR 9000 reports %OS-OBFLMGR-7-RECORD_TYPE_UNKNOWN unknown record type errors continuously.
In addition, with obfl file corruption the obflmgr manager process may crash due to CSCui12736.
Evaluate the reasons for obfl file corruption and eliminate. In cases it occurs have system clear the obfl corrupted files automatically without user intervention and alarm.
Conditions:
Workaround:
1. Clear the corrupted files:
The system will generate new obfl files and there is no impact.
admin clear logging onboard corrupted-files location 0/RSP0/CPU0
admin clear logging onboard corrupted-files location 0/RSP1/CPU0
2. If the issue persists, remove obfl files manually.
Use "admin show logging onboard raw | in file" CLI to get the location of the files and remove the files from ksh using the rm command.
Or
3. Try to restart the obflmgr process:
process restart obflmgr location 0/RSP0/CPU0
process restart obflmgr location 0/RSP1/CPU0
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.3.4.BASE, 5.1.1.BASE, 5.1.3.BASE |
|
Known Fixed Releases: | 5.3.1, 5.3.1.12i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus47582 | Title: | eem-failed to execute cli:error reading channel:error reading "file32": |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:EEM TCL script may fail with this :
script.tcl: failed to execute cli command: error reading the channel: error reading "file32": bad file number error reading the channel: error reading "file32":
Conditions:timing condition causing router prompt to be split on 2 lines when tcl match patterns
Workaround:replace cli_read_pattern tcl lib with the fixed one in the EEM tcl script
proc ::cisco::eem::cli_read_pattern {fd ptn} {
set result ""
set is_end 0
set str1 ""
set str2 ""
set trim_last_line ""
set i 1
set last_line ""
set line2 ""
# lets not spin forever. try for maximum 50000 times
while {$is_end == 0 && $i<=50000 } {
set str [read $fd]
if {$str == ""} {
after 50
incr i;
continue
} else {
#sometimes read returns router prompt partially.
#we hope in at least 2 read() calls we get full router prompt
set last_line $line2
append last_line $str
set line2 $str
}
# double quotes (don't change to curly braces!)
set is_end [regexp "(.*)?($ptn)" $last_line str1]
if {$is_end} {
#remove last line containing routername
set trim_last_line [regexp "(.*)\n" $str1 str2]
if {$trim_last_line} {
append result $str2
}
} else {
append result $str
}
after 60
}
return $result
}
More Info:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.1.3.ROUT |
|
Known Fixed Releases: | 5.3.1, 5.3.1.20i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua57513 | Title: | [asr9k-ipiw]:Serial Interface flap once after ppp_ma process restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ppp_ma restart events (e.g. SMU activation) will result in any PPP ACs in IP interworking mode being renegotiated. i.e. this may result in traffic loss for a short period (seconds) but only on the affected PPP ACs where IP interworking is configured following the process restart.
Conditions:
This will only happen when ppp_ma is restarted *and* PPP ACs with IP interworking is configured. So only restricted to customers that use l2vpn IP interworking with PPP ACs.
Workaround:
Either avoid the restart, or allow for the fact that traffic may be dropped for in the order of seconds on PPP IP Inteworking ACs following the process restart.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 4.2.0.BASE |
|
Known Fixed Releases: * | 4.3.0, 4.3.1, 4.3.1.1i.FWDG, 4.3.2, 4.3.3, 4.3.31, 4.3.4, 4.3.91, 5.1.0, 5.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu99198 | Title: | Traffic not get forwarded to GRE tunnel by ABF next-hop |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ABF not working on GRE tunnels on Ingress side, for those paks that were punted to netio from the egress NP.
Conditions:
Configure ABF in Ingress ACL to redirect paks into GRE tunnels.
On the tunnel, have an egress ACL to deny the above paks.
Paks get punted to netio as expected.
In netio, they don't get ABF'd into the tunnel !!
Workaround:
Fixed
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 4.3.4.ROUT |
|
Known Fixed Releases: * | 5.3.3.19i.BASE, 6.0.0.26i.BASE, 6.0.1.12i.BASE, 6.1.0.9i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut09995 | Title: | apply-group verifier returns ipv4-ma error while removing apply-group |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Apply failed on ipv4-ma when removing the apply-group config
Conditions:
'ipv4-ma' detected the 'fatal' condition 'Helper address apply failed, when removing apply-group
Workaround:
N/A
Further Problem Description:
N/A
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: * | 6.0.0.23i.FWDG, 6.0.1.12i.FWDG, 6.1.0.3i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut53168 | Title: | dwdm-ui-cfg_02: returned value out of range |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When trying to remove leaf wave-channel using XML . The edit-config operation results in a bad-element error. The message is constructed from the output of get-config, which returned the value 19580 and that does not conform to schema (which says that the type of this leaf is uint32 with range 1..100
Conditions:
When wavelength Freq is configured out of range for 1-100 and tried to edit using XML ,this error is recieved.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.3.1.MGBL |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.10i.BASE |
|
|
| |
| |
|
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: | 24-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.FWDG, 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux12450 | Title: | eXR: No OBFL fpd record is seen on the board for CBC upgrade |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
No OBFL fpd record is seen on the board for CBC upgrade.
Conditions:
Execute "upgrade hw loc fpd cbc force" to upgrade CBC on a board.
Workaround:
Unknown.
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv10653 | Title: | RPL parameter issue with 4-byte ASN values |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Customer is using RPL with parameters to set RT extended community for prefixes. They call this RPL within another RPL and when they pass 4-byte format ASN to the RPL, RPL will apply the 4-byte number in IP based format. See below:
route-policy RP-VRF-EXTNET-ACTIVE-EXPORT($PrefixSet, $Global, $Local)
if destination in $PrefixSet then
set extcommunity rt ($Global:$Local) additive
set med 100
endif
end-policy
route-policy RP-TEST-1
apply RP-VRF-EXTNET-ACTIVE-EXPORT(PS-1, 133931, 2)
end-policy
In this case RT would be:
RT:0.2.11.43:2
Now the issue is, when we want to use RT 133931:2 as a match for import route-target on a VRF, it doesn't match while RT value "0.2.11.43:2? will match.
Conditions:
You will hit this only when use parameter based RPL and pass 4-byte number as a parameter to the RPL
Workaround:
We can confirm that this is RPL behavior only. if try to eliminate use of nested RPL and parameters and use RPL to set the RT directly, It will set the RT value in the correct way (4-byte number)
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.1.3.MPLS, 5.1.3.ROUT |
|
Known Fixed Releases: * | 6.0.1.12i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux41857 | Title: | far-end port has double flap right after no shutdown on near-end port |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When near-end has no shutdown, extra interface flap happen on far-end.
Conditions:
With Typhoon and Tomahawk LC, the issue can happen
Workaround:
None. carrier-delay on far-end could be help to prevent.
Further Problem Description:
Due to this bug, instantaneous laser shutdown will be inserted into middle of sequence of no shutdown operation
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 5.3.3.24i.BASE, 6.0.1.12i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut70604 | Title: | Interface counter are getting doubled after enabling URPF |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Interface counters are getting doubled
Conditions:
This problem may be observed after configuring uRPF or a monitor-session under the interface
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE, 5.3.1.BASE, 5.3.1.LC, 5.3.1.ROUT |
|
Known Fixed Releases: | 5.3.2, 5.3.2.9i.BASE, 6.0.0.5i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux67492 | Title: | netio traceback @c_regcomp.c:507 after RPFO |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traceback just appears once after RPFO. It has no identified functional impact.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.3.ADMIN |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur19923 | Title: | Optics not detected when interface is in shutdown state |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Optics not detected when interface is in shutdown state. show inventory will not show the optics PID and syslog message regarding optics insertion or removal will not be displayed when optics is pulled in or removed respectively.
Conditions:
Interface in shutdown condition.
A9K-24X10GE, A9K-36X10GE, A9K-8X100GE-L-SE/TR, A9K-8X100-SE/TR
Workaround:
Under interface config, do "no shutdown".
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: * | 5.3.0.BASE, 5.3.2.BASE, 5.3.2.LC, 5.3.3.BASE |
|
Known Fixed Releases: | 5.3.3.11i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux87138 | Title: | PBTS fallback CLI not accepting multiple FC values |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Fallback to CLI not accepting multiple FC values
Conditions:
Configure multiple FC values to cef pbts class x fallback-to y command
Workaround:
Use 1 value per fallback-to line
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.3.3.24i.BASE |
|
Known Fixed Releases: * | 5.3.3.FWDG, 6.0.1.15i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux44754 | Title: | Console Clean-up - cfgmgr_cfs_check[65900]: wd_set_rlimit:rlimit |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
During the reload/OIR of a line card or during the reboot of the router, these messages may show up on the User console.These messages are harmless and are just a nuisance for the users.
Conditions:
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: * | 5.3.3.BASE, 6.0.0.BASE |
|
Known Fixed Releases: | 6.0.1.13i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux99139 | Title: | OSPFv3 go down with ipsec authentication sha1 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
OSPFv3 neighborship goes down when configured for ipsec authentication
Conditions:
Routers connected via bundle of hundredgig interfaces
Workaround:
disable authentication and ospfv3 peering comes up
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.2.4.K9SEC |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux08992 | Title: | Incorrect prefix received after l2vpn_mgr restart |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Incorrect Local L2VPN VPLS prefix may be observed in BGP's table after restart l2vpn_mgr process
Conditions:
Restart of l2vpn_mgr process
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.3.3.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw17040 | Title: | devb-umass process crash on mod80 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
devb-umass process crash on mod80.
Conditions:
Router reload/upgrade with 13J image
Workaround:
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 5.3.3.10i.BASE, 6.0.0.18i.BASE, 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux77775 | Title: | ASR9K: Fantrays to be used in all the FT slots when Tomahawk LC present |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
If 9k is reloaded with single Fan Tray, Tomahawk LineCard stays down.
Following console logs were reported:
RP/0/RSP0/CPU0:Jan 7 19:21:56.437 : shelfmgr[410]: %PLATFORM-SHELFMGR-3-INCOMPATIBLE_FT_FOR_LC : All the Fantrays must be V2 in order to provide cooling for the A9K-NP300-LC. Chassis has incompatible Fantray for Node 0/5/CPU0.
RP/0/RSP1/CPU0:Jan 7 14:24:20.451 : canb-server[153]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/5/CPU0 , Power Cycle (0x05000000)
RP/0/RSP0/CPU0:Jan 7 14:24:20.475 : canb-server[153]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/5/CPU0 , Power Cycle (0x05000000)
RP/0/RSP1/CPU0:Jan 7 14:24:24.025 : canb-server[153]: %PLATFORM-CANB_SERVER-7-CBC_POST_RESET_NOTIFICATION : Node 0/5/CPU0 , Power Cycle (0x05000000)re
Conditions:
If ASR9k is reloaded with single Fan Tray, Tomahawk LineCard stays down.
Following console logs were reported:
RP/0/RSP0/CPU0:Jan 7 19:21:56.437 : shelfmgr[410]: %PLATFORM-SHELFMGR-3-INCOMPATIBLE_FT_FOR_LC : All the Fantrays must be V2 in order to provide cooling for the A9K-NP300-LC. Chassis has incompatible Fantray for Node 0/5/CPU0.
RP/0/RSP1/CPU0:Jan 7 14:24:20.451 : canb-server[153]: %PLATFORM-CANB_SERVER-7-CBC_PRE_RESET_NOTIFICATION : Node 0/5/CPU0 , Power Cycle (0x05000000)
Workaround:
To have Fan Trays installed in all the FT slots when Tomahawk LC is present in the chassis.
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux92476 | Title: | eXR: "Error: FPGA didnt complete cfg" is seen in Meldun / Dalla fallback |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Meldun / Dalla Golden FPD version can not become the running version after the FPD primary version is corrupted.
"Error : FPGA did not complete configuration." is seen.
Conditions:
Perform FPD fallback testing for Meldun / Dalla FPD.
Workaround:
Primary is get corrupted here and do upgrade of primary will recover it.
Further Problem Description:
There is an erratum with the muliboot mechanism on the Artix FPGA devices. The first 1K bytes of the image contains the sync word. If a valid sync word is present, then even if the rest of the image is corrupted, the multiboot mechanism will not switch over to the golden image due to the erratum. To work around this classic FPD erases the first 1K bytes of the image first and programs it last for the upgrade image.
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 6.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux27591 | Title: | Token $(line) substitution does not work for ssh telnet |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When using banner motd or 'banner exec' command with $(line) substitution around various network devices it was found it works on Cisco 7600 but does not work on ASR9000 in 4.2.3
Conditions:
banner motd or 'banner exec' command with $(line) substitution
Workaround:
if using 4.2.3 upgrade to 5.1.3 for telnet.
For ssh there is no workaround. You have to see the line then please configure the $(line) as a part of exec banner. Since before authentication in XR we dont allocate VTY.
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy00751 | Title: | ASR9001: tty_mgmt_terminal_cmd crash after 'terminal length 0' |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
tty_mgmt_terminal_cmd process may crash after 'terminal length 0' command is issued.
Conditions:
Issue 'terminal length 0' command.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux90513 | Title: | 533 26I - ipv4_mfwd_partner crash @ rn_delete during interface down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MFIB crashes on a Linecard after a SMU installation + interface down event.
Conditions:
Multicast should be running over BVI interfaces. If a SMU that involves changes in certain MFIB DLLs is installed, we may run into a crash during subsequent flap of BVI group membership info.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 4.1.1.MCAST, 5.3.3.MCAST |
|
Known Fixed Releases: * | 5.3.3.MCAST, 6.0.1.16i.MCAST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux89263 | Title: | prm_ezhal 'Not enough TM resources to satisfyrequest' error on typhoon. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On TR card, after removing a queuing policy. Reconfigure the same policy back is rejected due to the following error
!!% 'prm_ezhal' detected the 'warning' condition 'Not enough TM resources to satisfyrequest'
Conditions:
The following sequence could trigger this issue when line card is Typhoon or Tomahawk -TR card
1. Apply the queuing policy on multiple interfaces hosted by the same NP (This will succeed)
2. prm_server_ty (for Typhoon) or prm_server_to (for Tomahawk) process restart due to restart SMU installation or crash or manual restart from CLI
3. Remove policy-map from multiple interfaces applied in step 1
4. Apply the same or any other queuing policy on the interfaces involved in step 3. Configuration may be rejected with "Not enough TM resources to satisfyrequest"
Workaround:
Reload the line card
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 6.1.1.BASE |
|
Known Fixed Releases: * | 5.3.3.BASE, 6.0.1.16i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy03455 | Title: | Excessive punt flow trap not recognizing-reporting DHCP correctly |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
On ASR9000 device running Excessive punt flow trap feature on subscriber interfaces, malicious DHCP traffic will be penalized, but in log following message could be seen:
LC/0/1/CPU0:Jan 25 02:48:53.838 : flowtrap[197]: %OS-FLOWTRAP-4-BAD_ACTOR_INTF_DETECTED : Excessive ?^?sX?^?s^H flow detected on interface Bundle-Ether32.99990.ip107926. The interface will be penalty-policed at 10 pps for 15 minutes.
Conditions:
ASR9000 device running 5.2.2 with BNG and Excessive punt flow trap feature enabled for subscriber interfaces.
Workaround:
None known at this time.
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun01818 | Title: | snmpwalk timeout after ospfv3 process deleted |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ospfv3 mib guery may take long time to timeout
Conditions:
- ospfv3 process was configured and later unconfigured
Workaround:
process restart snmpd
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 4.2.3.BASE |
|
Known Fixed Releases: * | 5.1.2, 5.1.2.20i.ROUT, 5.1.3, 5.1.3.1i.ROUT, 5.1.4, 5.2.0, 5.2.0.15i.ROUT, 5.2.1, 5.2.2, 5.2.21 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46204 | Title: | SNMP trap on power feed down event - umbrella SMU |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
SNMP traps are not raised when a single power feed is removed or added.
Conditions:
ASR9k power feed is turned off
Workaround:
N/A
Further Problem Description:
None
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw10253 | Title: | show bgp policy neighbor <> commands are not working properly |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Few nbr commands are not working:
show bgp neighbor x.x.x.x advertise/receive route returns error
% Neighbor not found
show bgp policy neighbor x.x.x.x commands return error
Conditions:
This issue happens for the last neighbor shown under show bgp summary. For example in show bgp summary if x.x.x.x is last entry, then if you issue show bgp policy neighbor x.x.x.x the error will be seen.
Workaround:
1. Create a dummy neighbor with higher IP address so that it becomes the last entry under show bgp summary.
2. Execute these commands without neighbor option and filter the resulting output based on the neighbor. If there are too many number of routes advertised, then this will take some time to display. output.
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 5.3.2.ROUT, 6.0.0.ROUT |
|
Known Fixed Releases: * | 5.3.3.15i.ROUT, 6.0.0.19i.ROUT, 6.0.1.12i.ROUT, 6.1.0.2i.ROUT |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw97473 | Title: | False alarm "PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING" on VSM blade |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | %PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Set|ahci-mon[32789]|0x1000000|HD0 device not responding
then (typically 30 sec later)
%PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Clear|ahci-mon[32789]|0x1000000|HD0 device not responding
Symptom:
%PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Set|ahci-mon[32789]|0x1000000|HD0 device not responding
then (typically 30 sec later)
%PLATFORM-AHCI-2-DEV_HD0_NOT_RESPONDING : Clear|ahci-mon[32789]|0x1000000|HD0 device not responding
Conditions:
- seen with A9K-VSM-500
- messages do not start immediately after reload of VSM, typically takes several days/weeks before it starts
Workaround:
Reload VSM blade
Further Problem Description:
As long as alrm is cleared at next read test, these messages are false alarms and do not have any impact.
|
|
Last Modified: | 30-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: * | 5.3.3.18i.BASE, 6.0.0.23i.BASE, 6.0.1.12i.BASE, 6.1.0.7i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux20499 | Title: | Tomahawk:Improve the time to notify shelfmgr after non-recoverable error |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When a tomahawk linecard has to reload due to a non-recoverable error, it takes around 4-5 seconds to to notify shelf manager.
Conditions:
non-recoverable error (parity error)
Workaround:
none
Further Problem Description:
This behaviour affects recovery mechanisms like BFD, FRR. For instance, FRR is not being triggered until shelf manger gets the notification that the card has been brought down.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 5.3.3.BASE, 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut22497 | Title: | ASR9k qos transmit statistics be N/A from command and mib |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
1.configuration:
policy-map test_for_qos
class test_for_qos
police rate 8000000 bps
!
!
class class-default
RP/0/RSP0/CPU0:nmtgs9010a#sh run interface gigabitEthernet 0/2/0/6
Thu Mar 5 16:44:29.174 CHINA
interface GigabitEthernet0/2/0/6
service-policy input test_for_qos
2.show interface to check traffic
5 minute input rate 9243000 bits/sec, 1434 packets/sec
3.show policy statistics
RP/0/RSP0/CPU0:nmtgs9010a#show policy-map interface gigabitEthernet 0/2/0/6
Thu Mar 5 16:45:23.627 CHINA
GigabitEthernet0/2/0/6 input: test_for_qos
Class test_for_qos
Classification statistics (packets/bytes) (rate - kbps)
Matched : 14655941/11871312210 9285
Transmitted : N/A
Total Dropped : 2025970/1641035700 1281
Policing statistics (packets/bytes) (rate - kbps)
Policed(conform) : 12629971/10230276510 8004
Policed(exceed) : 2025970/1641035700 1281
Policed(violate) : 0/0 0
Policed and dropped : 2025970/1641035700
we can see that transmit packets no is zero.. that's not true..
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 09-JAN-2016 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy03335 | Title: | Optic vendor name not displayed for 3rd party optics |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Behavior change in inventory for 533, Description fields (DESCR: in inventory) for 3rd party optics are displayed as "Unknown or Unsupported SFP Module". Previous behavior was to display the Vendor Name when Product ID is missing:
Port 1 IDPROM Data:
Product Id :
Product Name : 1GE/1FC/2FC
Version ID :
CLEI Code :
Top Assembly Part No. :
Serial Number : xxxxxxx
PCB Revision : A
Vendor Name : FINISAR CORP.
Port 2 IDPROM Data:
Product Id :
Product Name : 1GE/1FC/2FC
Version ID :
CLEI Code :
Top Assembly Part No. :
Serial Number : xxxxxx
PCB Revision : A
Vendor Name : CHAMPION ONE
Example of inventory output:
NAME: "module mau GigabitEthernet101/0/CPU0/14", DESCR: "Unknown or Unsupported SFP Module"
Conditions:
intended results after after CSCux18672
Workaround:
no workarounds
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.3.3.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw49047 | Title: | locald_DSC on standby RP |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom:
A locald_DSC process crash was observed on the standby RP
Conditions:
This was observed after the cable connected to the MgmtEth interface and the Aux port was unintentionally swapped on the standby RP.
Workaround:
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux97736 | Title: | HSRPv1 hellos processed when HSRPv2 enabled on interface |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
Interface configured with HSRPv2 listen to HSRPv1 hellos
Conditions:
HSRPv2 is enabled on interface or sub-interface
Workaround:
Apply inbound access-list to filter HSRPv1 hello (224.0.0.2/udp port 1985)
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66872 | Title: | Show CLI for frequency synchronization on sat acces int is not working |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Show CLI for frequency synchronization on sat acces int is not working
Conditions:
With 6.0.0-17i image on satellite interface
Workaround:
Further Problem Description:
|
|
Last Modified: | 24-JAN-2016 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux38055 | Title: | ASR9K as GM should set utcOffsetValid flag to TRUE |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
ASR 9K acting as PTP Grandmaster sets utcOffsetValid flag to FALSE in announce messages sent to downstream slaves.
Conditions:
ASR 9K acting as PTP Grandmaster.
Workaround:
The slave can use the current leapseconds (36 after Jun 30, 2015) as the offset between PTP and UTC timescale is not implementation dependent.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux01983 | Title: | 5.3.1 Umbrella SMU for sysdb |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Conditions:
Workaround:
Further Problem Description:
This is an Umbrella DDTS for sysdb related fixes.
[r60x] MCSAT sysdb_svr_local crashed at sms_respq_handle_resp_msg
Big verification messages crash sysdb_shared_sc
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE, 5.3.3.BASE |
|
Known Fixed Releases: | 3.8.3, 3.8.4, 3.9.0, 3.9.1, 3.9.2, 3.9.3 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux88095 | Title: | commit fails when macsec-service config is overwritten when intf scale |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Commit failure
Conditions:
No functionality issue
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux78596 | Title: | Suspect Flag always set to Yes in "sh ethernet sla statistics brief" |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Suspect Flag is always set to Yes in the output of sh ethernet sla statistics brief.
Conditions:
Y.1731 SLM/LMM/DMM probes generated by an ASR9k sender.
Workaround:
Omit the brief keyword from the command.
Further Problem Description:
It's a cosmetic issue. Only the brief" version (sh ethernet sla statistics brief) of output is affected. No other operational impact.
|
|
Last Modified: | 15-JAN-2016 |
|
Known Affected Releases: | 5.2.0.CE |
|
Known Fixed Releases: * | 5.3.3.26i.BASE |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux83178 | Title: | Umbrella Defect to address some critical BGP issues in 5.2.4 |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
BGP instability
Conditions:
CSCuw98437 ASR9K L3VPN Dynamic Load-share btw local and remote VRF fix
CSCut02575 BGP crash after RPFO due to wrong fragmentation handling during NPL rtx
CSCux07255 BGP route withdrawal issue
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 5.2.4.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux43977 | Title: | Downgrade from 6.0.1 Image throws Inconsistent config error |
|
Status: | Terminated |
|
Severity: | 4 Minor |
Description: | Symptom:
Configuration inconsistency alarms being raised during downgrade from 6.0.1 image to older images due to
interface PTP related configuration.
RP/0/RP0/CPU0:Sep 17 19:25:40.819 : cfgmgr-rp[162]: %MGBL-CONFIG-3-INCONSISTENCY_ALARM : A configuration inconsistency alarm has been raised. Configuration commits will be blocked until 'clear configuration inconsistency' command has been run to synchronize persistent configuration with running configuration.
Conditions:
Downgrade from XR 6.0.1 or later release to older ones on ASR9000 routers with A9K-RSP440-SE/TR or A9K-RP-SE/TR RSPs.
Workaround:
Do "clear configuration inconsistency" before proceeding with further configuration after the downgrade.
Further Problem Description:
This error message is expected as interface PTP is not supported on A9K-RSP-440 and A9K-RP RSPs in releases older than 6.0.1. Users can do clear configuration inconsistency safely to continue with the configuration.
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 6.0.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCto99989 | Title: | SNMP bulk config, or load from saved config, or rollback will show error |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: * | Symptom:
SNMP bulk configuration, or load from saved configuration, or rollback (which include multiple SNMP commands) can cause following messages to print on console.
RP/0/RSP0/CPU0:Apr 27 19:26:59.446 : snmpd[1112]: %SNMP-SNMP-4-VIEWOID_NOT_FOUND : The command "snmp view li-view ifMIB included" could not be applied at this time because the oid "ifMIB" does not belong to a known MIB module.
RP/0/RSP0/CPU0:Apr 27 19:26:59.481 : snmpd[1112]: %SNMP-SNMP-4-VIEWOID_NOT_FOUND : The command "snmp view li-view ciscoTap2MIB included" could not be applied at this time because the oid "ciscoTap2MIB" does not belong to a known MIB module.
RP/0/RSP0/CPU0:Apr 27 19:26:59.495 : snmpd[1112]: %SNMP-SNMP-4-VIEWOID_NOT_FOUND : The command "snmp view li-view ciscoIpTapMIB included" could not be applied at this time because the oid "ciscoIpTapMIB" does not belong to a known MIB module.
Conditions:
SNMP bulk configuration, or load from saved configuration, or rollback (which include multiple SNMP commands) can cause the error messages.
This behaviour is observed since MIB is not loaded and the OID translation is not in place.
After few seconds, this get resolved and you could query the MIB successfully.
Workaround:
None. When this behavior observed during SNMP configuration for lawful intercept; it still allowed adding taps and lawful intercept functionality did not impact in any manner.
Recovery:
None. These are harmless messages and does not impact any functionality
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 4.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux88549 | Title: | Replace the unknown Icon |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: * | Symptom:
to see the relevant icon
Conditions:
when node connected correct icon has to be display
Workaround:
no
Further Problem Description:
no
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 99.99.99.MPLS |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy00237 | Title: | Rquest to add nodeID for ether-ctrl CLOG messages |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
CLOG message for the corresponding SYSLOG does not contain any LC info only the PORT info. Not able to identify on which LC the SFP port is experiencing an issue from just the CLOG message.
LC/0/0/CPU0:Nov 9 18:04:16.157 : ETHER_CTRL[161]: %PLATFORM-ETHER_CTRL-4-XCVR_WARNING : SFP for port 6 is disabled - Auto-Neg is not supported
enterprises.cisco.ciscoMgmt.ciscoSyslogMIB.ciscoSyslogMIBObjects.clogHistory.clogHistoryTable.clogHistoryEntry.clogHistMsgText.0 = SFP for port 6 is disabled - Auto-Neg is not supported
.1.3.6.1.4.1.9.9.41.1.2.3.1.6.0
Conditions:
Normal conditions
Workaround:
Syslog message will indicate the LC and specific Port
Further Problem Description:
|
|
Last Modified: | 27-JAN-2016 |
|
Known Affected Releases: | 5.1.11.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23668 | Title: | ASR9k BNG. DHCPv6 VLAN ID lost when using geo red vMAC + ambiguous vlan |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
VLAN id is changed to 1 for DHCPv6 ADVERTISE packets
Conditions:
when doing IPoE for dual-stack or IPv6 sessions and using geo redundancy vMAC together with ambiguous VLAN on access interface
Workaround:
issue does not occur if vMAC is not used
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: * | 6.0.1.15i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux92100 | Title: | SSTE: SRTE tunnel w/ BGP LU label conflict: ROUTING-RIB-3-LABEL_ERR_ADD |
|
Status: * | Other |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
A traceroute to an SRTE tunnel destination follows a path other than the configured path
Conditions:
If the router has learned a label from BGP Labeled-Unicast in addition to the ISIS segment-routing label a "local-label conflict" can occur leaving the forwarding table out of sync with the routing table for the tunnel destination prefix.
Workaround:
This is not seen when the IBGP routers aren't advertising labeled-unicast for prefixes configured as SRTE tunnel destinations.
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv10167 | Title: | ASR9K(9000v) LLDP dot1ad nni doesn't work with 3750-ME |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
SR9K(9000v) sends and expects dest MAC address 01-80-C2-00-00-0E regardless dot1d nni is configured or not. This causes interworking issue with Cisco 3750-ME device which sends and expects 01-80-C2-00-00-03 when dot1ad nni is configured. There is no problem when dot1ad nni is not configured, ethertype 0x8100.
Conditions:
3750-ME ethernet dot1ad nni is configured
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 23-JAN-2016 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.FWDG, 6.1.0.6i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtf25353 | Title: | 3.9.1:20K:MSTAG/MSTP Need to clear STP/Topology-change Flush counters |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
There is no way to clear the statistics displayed the show spanning-tree ... commands.
Conditions:
No clear commands exist. This may be a problem if spanning-tree is configured and it is necessary to clear some of the recorded counters.
Workaround:
None.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 3.9.1.BASE |
|
Known Fixed Releases: * | 6.0.1.12i.BASE, 6.1.0.1i.BASE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq98340 | Title: | Fix syslog format for low power alarms |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
Port_1/00 not following traditional r/s/s/i format
Conditions:
Rx power warning / alarm on optical interfaces
Workaround:
Use EEM TCL script
Further Problem Description:
|
|
Last Modified: | 19-JAN-2016 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux95760 | Title: | Need a mechanism to prevent all l2vpn pw-class from being removed |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
All l2vpn pw-class configuration may be deleted from the router configuration without warning
Conditions:
This problem would occur when committing "no pw-class" without specifying a pseudo-wire class name under the IOS-XR l2vpn configuration
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux83936 | Title: | MPLS LSD NSR sync taking almost 45mins after RPFO with 64 ECMP paths |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
MPLS LSD takes 45mins for NSR sync after RPFO with around 12k IGP 64 ECMP routes
Conditions:
It is due to the 64ECMP paths for 12K IGP routes. This adds up lots of memory that needs to be synced from active LSD to standby LSD before it could declare NSR ready. Due to the slowness of underneath AIPC transport layer, it takes LSD around 40 mins to finish all the message sync.
This behaviour has been there since 5.2.0, and so far we only see it with massive 64 ECMP IGP routes. Do not see it on other testbed, even with over 20K IGP routes(not 64 ECMP for every route).
Workaround:
no workaround. Just need to wait for 45 mins to trigger RPFO. The NSR sync could eventually be done, and no functional impact.
Further Problem Description:
|
|
Last Modified: | 25-JAN-2016 |
|
Known Affected Releases: | 5.3.3.ADMIN |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua88441 | Title: | Config DB enhancements for handling multiple AVpairs of the same type |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
On a IOS-XR platform it is only possible to push one per-user static route via radius.
Multiple AVpairs of the same type are not supported.
This includes Framed-Route or cisco-avpair "ipv4:route" or "ip:route" radius AVpairs.
The debug ppp negotiation will show the an error similar to the following:
PPP-MA[365]: %L2-PPP_MA-4-ERR_AAA_SESSION_IF : Bundle-Ether1.49.pppoe17167: Unexpected error encountered whilst receiving an activate response: 'TmplMgr' detected the 'fatal' condition 'Duplicate AAA attribute enum in attribute list'
Conditions:
This issue is seen in all versions of IOS-XR.
Workaround:
If you need multiple routes for the interface you can push one via radius and any additional ones must be configured on the router.
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 4.3.1.ROUT |
|
Known Fixed Releases: * | 5.1.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu47149 | Title: | Need netflow export to be smaller than 1500bytes |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Netflow PDU's are packed into a UDP packet until the frame is 1500 bytes, this can cause fragmentation or drops when the path to the collector has a lower MTU ceiling.
Conditions:
Netflow component is able to pack PDU's all the way to 1500 bytes, this generally happens with ipv4 packets, not generally with MPLS or IPv6.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 5.1.11.BASE |
|
Known Fixed Releases: * | 5.3.3.27i.FWDG, 6.0.1.16i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui20038 | Title: | implement MRU ignore for PPP sessions |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
When the client signals a low MRU we honor that value and apply that as MTU on the subscriber interface.
This can lead to a need for fragmentation, for which XR has no support in general.
Conditions:
client signaling low MRU
Workaround:
fix the MTU config statically (has limtiations).
Further Problem Description:
Need the ability to override and ignore the client signaled MRU and use the BNG lcoally defined MRU/MTU value.
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: * | 4.3.4.13i.FWDG, 5.1.1.9i.FWDG, 5.1.11.4i.FWDG, 5.1.2.1i.FWDG, 5.2.0.2i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup73586 | Title: | Support for default route installation via Framed-IPv6-Route on BNG |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Currently, on ASR9k platform it is impossible to install default route through Framed-IPv6-Route attribute sent from Radius.
Conditions:
ASR9k with BNG
Workaround:
Configure static default route manually on device.
Further Problem Description:
|
|
Last Modified: | 12-JAN-2016 |
|
Known Affected Releases: | 5.1.2.BASE |
|
Known Fixed Releases: * | 5.3.0.12i.FWDG |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux81504 | Title: | No PPPoE subscribers authentication and accounting info in BNG Syslog |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
No PPPoE subscribers authentication and accounting info in Syslog
Conditions:
using BNG
Workaround:
No workaround
Further Problem Description:
|
|
Last Modified: | 21-JAN-2016 |
|
Known Affected Releases: | 5.3.2.ROUT |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux98447 | Title: | ASR9K: Remove L2 padding for incoming ipv6 packets |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
BFD v6 fails to come up on Typhoon and Tomahawk Line cards if the peer sends BFD v6 packets with unwanted L2 padding
Conditions:
The BFD v6 peer is sending packets with around 100 bytes of additional L2 padding.
It is applicable to Tomahawk and Typhoon Line cards.
All IOS-XR versions are impacted.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 26-JAN-2016 |
|
Known Affected Releases: | 5.3.2.FWDG |
|
Known Fixed Releases: | |
|
|
| |
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论