| |
Bug Id: | CSCui83818 |
Title: | ISIS 64 bytes PSNP packets are counted as "Input drop other" |
|
Description: | Symptom:
ISIS 64 bytes PSNP packets are counted as "Input drop other", though they are not really dropped.
Conditions:
ISIS router with links configured as point-to-point.
Workaround:
This problem is merely cosmetic, the PSNP's are still processed just reported incorrect due to an accumulation discrepancy in the sw.
As this problem is seen on p2p links, you can also move to non p2p links for the ISIS adj to bypass this issue.
Further Problem Description:
Partial sequence number PDU (PSNP) is used to acknowledge receipt of an LSP on point-to-point links.
When a router receives a new LSP, it floods this LSP to its neighbors, except the neighbor that sent the new LSP. On point-to-point links, the neighbors acknowledge the new LSP with a PSNP, which holds the LSP ID, sequence number, checksum, and remaining lifetime. When the acknowledgment PSNP is received from a neighbor, the originating router stops sending the new LSP to that particular neighbor although it may continue to send the new LSP to other neighbors that have not yet acknowledged it.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 01-JUN-2015 |
|
Known Affected Releases: | 4.3.2.BASE, 5.1.0.BASE |
|
Known Fixed Releases: | 5.1.0.23i.BASE |
|
|
| |
| |
Bug Id: | CSCuq63659 |
Title: | [SecGW] [SNMP] ceipSecGlobalActiveTunnels.0 is always 0 |
|
Description: | Symptom:
ceipSecGlobalActiveTunnels.0 is not updating, because of this other snmp stats related to this ceipSecTun* will not be updated
Conditions:
is enable SNMP
Workaround:
no Workarounds
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 01-JUN-2015 |
|
Known Affected Releases: | 17.0(1) |
|
Known Fixed Releases: | 17.0.0, 17.0.0.56737, 17.0.B0.56802, 17.0.H0.56823, 17.0.M0.56789, 17.1.0.57118, 18.0.0.56841, 18.0.0.56958, 18.0.A0.56947, 18.0.B0.56844 |
|
|
| |
| |
Bug Id: | CSCut35585 |
Title: | BGP process crash on VRF unconfiguration |
|
Description: | Symptom:
The BGP process may crash on an ASR9000
Conditions:
This problem would occur when removing in one commit the VRF from the global and BGP configuration.
Workaround:
Perform the configuration removal in two steps
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 01-JUN-2015 |
|
Known Affected Releases: | 5.1.3.BASE |
|
Known Fixed Releases: | 5.2.4.14i.ROUT, 5.2.5.8i.ROUT, 5.3.1.27i.ROUT, 5.3.1.28i.ROUT, 5.3.2.6i.ROUT |
|
|
| |
| |
Bug Id: | CSCup34458 |
Title: | Loss of management access to an ASR9000 |
|
Description: | Symptom:
Randomly, all management access to an ASR9000 via the console port, aux port, telnet or ssh may be lost until the router is relaoded.
Conditions:
.
Workaround:
None
Further Problem Description:
|
|
Status: | Other |
|
Severity: | 2 Severe |
Last Modified: | 02-JUN-2015 |
|
Known Affected Releases: | 4.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuo55775 |
Title: | IPSec DP VM gets deactivated in 2 mins after act due to corrupt eeprom |
|
Description: | Symptom:
IPSec DP VM gets deactivated in 2 mins after act due to corrupt eeprom
Conditions:
FPD upgrade followed by ipsec deact/activation
Workaround:
eeprom needs to re-programmed
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 02-JUN-2015 |
|
Known Affected Releases: | 5.2.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuo92661 |
Title: | Ports in A9K-8T- Line cards don't come up after installing 5.1.0 C-SMU1 |
|
Description: | Symptom:
Ports in A9K-8T-L, A9K-8T-B, A9K-8T-E Line card don't come up.
Conditions:
Following the installation of 5.1.0 C-SMU1
Workaround:
No Work Arounds
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 5.1.0.LC |
|
Known Fixed Releases: | 5.2.3.99i.BASE |
|
|
| |
| |
Bug Id: | CSCuu47350 |
Title: | NR-TE-NHID: ipv6 pkts drop with RSV_DROP_NHINDEX as nhid is not correct |
|
Description: | Symptom:
all ipv6 pkts dropped with nhid drops.
Conditions:
non-recursive over TE tunnels.
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuu64342 |
Title: | Tigershark CRC error seen with L2VPN xconnect line rate traffic |
|
Description: | Symptom:
Following PFM log reporting CRC error on Fabric interface ASIC resulting some packet drops.
FABRIC-FIA-1-SUSTAINED_CRC_ERR : Set|fialc[159810]|0x1071001|Fabric interface ASIC-1 has sustained CRC errors
Conditions:
This issue is seen only in following condition so far.
Two ports in an xconnect group sending line rate traffic at 180byte.
Setup:
Ixia ????????? Port 0 [ ASR9K] Port 1 ????????? Ixia
Port0 and Port1 are in xconnect group
Traffic :
-180 byte unicast traffic
Steps:
- Continuously run bidirectional traffic between two ports and every one minute do a start and stop of traffic .
Workaround:
Issue is seen only at 100% of line rate, workaround would be operate < 100% of line rate.
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 5.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuc34844 |
Title: | SPA in disabled state after loading ISSU SMU |
|
Description: | Symptom:
Intelligent SPA put in to DISABLED state after ISSU Completes
Conditions:
Unsupported spa during ISSU will be put into DISABLED state and once issu is complete, there are brought back up, But even after issu completes, spa fails to come back up.
Workaround:
None.
|
|
Status: | Other |
|
Severity: | 1 Catastrophic |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.2.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuf51847 |
Title: | L2VPN traceback issuing show l2vpn mstp command with incorrect parameter |
|
Description: | Symptom:
On a Cisco IOS-XR router, issuing Show CLI for L2VPN MSTP with unsupported and out-of-range parameters, the Show CLI process or L2VPN process may reload unexpectedly.
Conditions:
The following Show CLIs must explicitly (manually) be excercised with incorrect values:
show l2vpn mstp port [interface ifname] [msti msti-value
- Executing this Show CLI with an invalid MSTI will result in an unexpected reload of the L2VPN Show CLI process.
show l2vpn mstp vlan [interface ifname] [msti msti-value] [vlan-id vlan-value]
- Executing this Show CLI with an invalid MSTI will result in an unexpected reload of the L2VPN Show CLI process.
- Executing this Show CLI with an invalid VLan Id will result in an unexpected reload of the main L2VPN process. As the Show CLI does not add or modify L2VPN data or configurations, the L2VPN process will resume functioning unaltered after the restart.
Workaround:
Restrict usage of the Show CLI to valid MSTI and VLan-Id values. The MSTI range of valid values is 0..64 and the VLan-Id range of valid values is 0..4095.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.3.1.BASE, 5.1.0.BASE |
|
Known Fixed Releases: | 4.3.1.32i.FWDG, 4.3.2.13i.FWDG, 4.3.2.16i.FWDG, 5.1.0.6i.FWDG |
|
|
| |
| |
Bug Id: | CSCue88528 |
Title: | snmpd process hang every couple hours - Cisco IOS |
|
Description: | Symptom:
snmpd process hangs and no response to mibs polling
Conditions:
It happens in normal condition when customer NMS keeps on polling in production network
Workaround:
To restart process snmpd
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.0.BASE |
|
Known Fixed Releases: | 4.3.1.29i.BASE, 4.3.2.14i.BASE, 5.1.0.8i.BASE |
|
|
| |
| |
Bug Id: | CSCtt22999 |
Title: | vpnv4 prefix fails to program with connected primary and BGP backup path |
|
Description: | Symptom:
FIB traceback and forwarding error is seen for an extranet connected route.
Conditions:
(1) Connected route is redistributed into BGP in the source VRF.
(2) The connected route is exported to another VRF (as extranet route)
(3) The extranet route also has an imported IBGP path
(4) Backup path installation (PIC) is configured on the extranet VRF
(5) BGP calculates and installs a backup path for the extranet connected route
Recovery:
Backup path calculation should be prevented for extranet
Connected routes using "additional-paths selection route-policy".
Workaround:
Backup path calculation should be prevented for extranet
Connected routes using "additional-paths selection route-policy".
Further Problem Description:
FIB cannot handle backup paths when the bestpath has a
non-recursive nexthop. Use the add-path selection RPL
to control which prefixes are allowed to have a backup path.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.0.1.ROUT, 4.1.2.ROUT |
|
Known Fixed Releases: | 4.2.0.28i.ROUT |
|
|
| |
| |
Bug Id: | CSCuh13864 |
Title: | DHCPv6d crash |
|
Description: | Symptoms:
DHCPv6 process crash.
Conditions:
When RG request both DHCPv6 IANA and DHCPv6 IAPD options, DHCPv6d proxy reaches bad state and dumps core.
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
3.3/2.6:
https://intellishield.cisco.com/security/alertmanager/cvssCalculator.do?
dispatch=1&version=2&vector=AV:A/AC:L/Au:N/C:N/I:N/A:P/E:POC/RL:OF/RC:C
No CVE ID has been assigned to 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
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.3.0.BASE, 4.3.0.FWDG |
|
Known Fixed Releases: | 4.3.2.27i.FWDG, 5.0.1.99i.BASE, 5.1.0.18i.FWDG, 5.1.1.1i.FWDG |
|
|
| |
| |
Bug Id: | CSCtz87422 |
Title: | 422-SIT: Sub-interface doesn't count multicast traffic packets |
|
Description: | Symptom:
Ingress multicast and MVPN traffic rate and packet counts are not displayed under sub-interface
Conditions:
Enable multicast traffic to ingress over a sub-interface
Workaround:
None, though the statistics on the parent interface are displayed
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.2.1.BASE, 4.2.2.BASE |
|
Known Fixed Releases: | 4.2.2.12i.BASE, 4.2.3.20i.BASE, 4.3.0.20i.BASE |
|
|
| |
| |
Bug Id: | CSCut67001 |
Title: | BNG: IP Subscriber Manager stops working |
|
Description: | Symptom:
On an ASR9k running version 5.2.2 with umbrella SMU CSCur72367 the IP Subscriber Manager (ipsub_ma) will stop functioning after several hours of operation.
Existing sessions continue to work but no new sessions can be established.
Conditions:
XR 5.2.2 with unbrella SMU CSCur72367 installed.
Workaround:
Restart ipsub_ma and iedged to recover from the failed state.
Further Problem Description:
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 5.2.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCty37179 |
Title: | ACL: Incorrect handling of remark ACEs in the library |
|
Description: | <B>Symptom:</B>
ACEs that is removed from shared plane is not removed from TCAM, without any error, resulting
in the inconsistency between the shared plane and local plane ACL rules.
<B>Conditions:</B>
When a batch of ACEs of an applied ACL is deleted that contains both the remark ACEs as well as
non-remark ACEs and non-remark ACEs appear before remark ACEs, then those non-remark ACEs which
appear before remark ACEs are not getting deleted.
This issue is applicable to both IPv4 ACL (Release 4.1 onwards) and IPv6 ACL (Release 4.0 onwards)
<B>Workaround:</B>
This issue can be avoided by using any one of the below steps:
-Remark ACEs are not deleted
-Only remark ACEs or non-remark ACEs are deleted at once, but not together
-Remark aces are at the top of the ACL, before any non-remark aces
If this issue is already hit, then work around is to reapply the config or restart the
pfilter_ea process.
<B>Further Problem Description:</B>
When a batch of ACEs of an applied ACL is deleted that contains both the remark ACEs as well as
non-remark ACEs and non-remark ACEs appear before remark ACEs, then those non-remark ACEs which
appear before remark ACEs are not getting deleted.
For example:
<CmdBold>
ipv4 access-list acl1
10 permit tcp any any
20 deny icmp any any
30 remark test acl1
40 permit udp any any
</CmdBold>
Applied to an interface:
<CmdBold>
ipv4 access-group acl1 ingress
</CmdBold>
Now, if we remove the ACEs in following manner, then we will hit this issue.
<CmdBold>
ipv4 access-list acl1
no 20
no 30
no 40
</CmdBold>
In the above example config, all 3 ACEs gets removed from shared plane config, but only ACE #
20 does not get removed from the local plane config.
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via
normal resolution channels.
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another
evaluation.
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
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.0.3.BASE, 4.1.1.BASE |
|
Known Fixed Releases: | 4.2.1.25i.FWDG, 4.2.3.7i.FWDG, 4.3.0.8i.FWDG |
|
|
| |
| |
Bug Id: | CSCub18286 |
Title: | EIGRP not advertising prefix to downstream neighbors in some cases |
|
Description: | Symptom:
EIGRP not advertising prefix to downstream neighbors in some cases
Conditions:
In a router if for a prefix there are both internal and external path (via redistribution) and if the internal path is seen as "backup in RIB" and is seen before the external path in "show eigrp topology "
Workaround:
If acceptable make the internal path "not in RIB" by changing the metrics of the external path. Configure "default-metric" or "route-policy" for redistribution such that EIGRP does not install the internal path in RIB.
In the below example, if is greater than , then EIGRP will not install the internal path in RIB.
RP/0/0/CPU0:ios#show eigrp topology 100.100.100.100/32
Mon Jul 23 13:21:23.964 IST
IPv4-EIGRP AS(1): Topology entry for 100.100.100.100/32
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 28160
Routing Descriptor Blocks:
10.10.4.3, from Redistributed, Send flag is 0x0
Composite metric is (/), Route is External
Vector metric:
Minimum bandwidth is Kbit
Total delay is microseconds
Reliability is 100/255
Load is 100/255
Minimum MTU is 100
Hop count is 0
External data:
Originating router is 10.10.0.2 (this system)
AS number of route is 1
External protocol is BGP, external metric is 10
Administrator tag is 100 (0x00000064)
10.10.0.1 (GigabitEthernet0/0/0/0), from 10.10.0.1, Send flag is 0x0
Composite metric is (/), Route is Internal, not in RIB
Vector metric:
Minimum bandwidth is Kbit
Total delay is microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 3.9.0.ROUT, 4.0.1.ROUT, 4.2.0.ROUT, 4.3.0.ROUT |
|
Known Fixed Releases: | 4.2.3.24i.ROUT, 4.3.0.22i.ROUT |
|
|
| |
| |
Bug Id: | CSCuu66747 |
Title: | Process restart of eth_server results in eth_server process crash |
|
Description: | Symptom:
The symptom of the issue is eth_server dumping core upon restarting it.
Conditions:
The issue is seen with normal traffic conditions
Workaround:
None
Further Problem Description:
None
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuh59908 |
Title: | [BNG] Subscriber session are not coming up after config pppoe PTA |
|
Description: | Symptom:
Subscriber session are not coming up after config pppoe
Conditions:
basic pppoe configuration
Workaround:
sessions are not coming up
|
|
Status: | Other |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 5.1.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCud32501 |
Title: | 430:LISP traffic dropped on PETR ingress, LISP_ING_DECAP_P2_NO_UIDB_DROP |
|
Description: | Symptom:
Packet drops could be seen on ASR9K configured as a LISP ETR router
Conditions:
When ASR9K is configured with LISP and acts as ETR and when packets destined to a EID prefix land on this router, the ASR9K is unable to decap and send these out of the box. Instead they are being dropped on ingress.
Workaround:
None.
|
|
Status: | Terminated |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.3.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuc96438 |
Title: | ASR9k PWHE OS_DUMPER when changing PW-Ether config |
|
Description: | Symptom:
ASR9k OS_DUMPER when changing PWHE PW-Ether interface config
Conditions:
1.) ASR9k with PWHE configure;
2.) chaning PW-ether configure (IP, vrf etc)
3.) or clear ip route from A-PE can also create OS_DUMPER on ASR9k
Workaround:
none
|
|
Status: | Other |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.3.1.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCua50217 |
Title: | 4.2.0P -> 4.2.1 upgrade fails install verify and RSP sync; unrepairable |
|
Description: | Symptom:
After upgrading an ASR9000 router from 4.2.0 to any higher version, the install
verify failed with the following errors: (In this case higher version is 4.2.1)
Info: /install/asr9k-base-4.2.1: [ERROR] Detected anomalies.
Info:
Info: /install/asr9k-base-4.2.1/0x100401/lib/libether_ctrl_mgmt_netio.dll:
Info: does not exist.
Info: /install/asr9k-base-4.2.1/lc/0xF10402/startup/vic_2090.startup:
Info: does not exist.
Info:
Info: /install/asr9k-base-4.2.1/lc/0x380261/lib/libplatform_dev_inst.dll:
Info: does not exist.
Info:
Info: /install/asr9k-base-4.2.1/lc/0x380261/bin/test_np_lc_6tph_36p_10ge:
Info: does not exist.
Info: /install/asr9k-base-4.2.1/lc/0x380261/lib/vkg_nplib.dll: does not
Info: exist.
Info:
Info: /install/asr9k-base-4.2.1/lc/0x3A0263/lib/libplatform_dev_inst.dll:
Info: does not exist.
Info: /install/asr9k-base-4.2.1/lc/0x3A0263/lib/vkg_nplib.dll: does not
Info: exist.
It is also seen after upgrade from 4.2.0 to any higher version and a redundancy
switchover is performed. Try to compare syslog after switchover with following
logs:
RP/0/RSP0/CPU0:ASR-PE7#sh log | i %INSTALL-INSTREPL-7-FILE_OPEN_FAILED
Wed Jul 11 14:17:25.271 UTC
RP/0/RSP0/CPU0:Jun 14 16:28:13.257 : sw_dwnld_svr[410]:
%INSTALL-INSTREPL-7-FILE_OPEN_FAILED : Failed to open file
'/disk0/asr9k-base-4.2.1/0x100401/lib/libether_ctrl_mgmt_netio.dll' while
creating a file stream: No such file or directory.
RP/0/RSP0/CPU0:Jun 14 16:28:23.470 UTC: instdir[252]:
%INSTALL-INSTREPL-7-FILE_OPEN_FAILED : Failed to open file
'/disk0/asr9k-base-4.2.1/0x100401/lib/libether_ctrl_mgmt_netio.dll' while
creating a file stream: No such file or directory.
RP/0/RSP0/CPU0:Jun 14 16:28:33.589 UTC: instdir[252]:
%INSTALL-INSTREPL-7-FILE_OPEN_FAILED : Failed to open file
'/disk0/asr9k-base-4.2.1/0x100401/lib/libether_ctrl_mgmt_netio.dll' while
creating a file stream: No such file or directory.
RP/0/RSP0/CPU0:Jun 14 16:28:44.313 UTC: instdir[252]:
%INSTALL-INSTREPL-7-FILE_OPEN_FAILED : Failed to open file
'/disk0/asr9k-base-4.2.1/0x100401/lib/libether_ctrl_mgmt_netio.dll' while
creating a file stream: No such file or directory.
Conditions:
Perform upgrade from 4.2.0 to higher version using the mandatory SMUs on 4.2.0,
and then perform a install verify. On a system with Dual RSP there is no
functional impact.
On a system with a single RSP, the system will still work as expected, but if a
new RSP is placed in the system it will not completely sync all the packages,
and it will not come up as standby ready. At that stage a turboboot is required.
Workaround:
Turboboot the desired higher version ONLY if the system is running with a
single RSP, else no action is required on a dual RSP system, the output of
install verify can be ignored.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.2.1.BASE, 4.2.2.BASE, 4.3.0.BASE, 4.3.1.BASE, 5.1.0.BASE |
|
Known Fixed Releases: | 4.2.3.99i.BASE, 4.3.2.99i.BASE, 5.0.1.99i.BASE |
|
|
| |
| |
Bug Id: | CSCub56244 |
Title: | Incorrect label in packet sent to RFC3107 (labeled unicast) ebgp peer |
|
Description: | Symptom:
Traffic to a IP (v4 or v6) which is reachable through another
IP nexthop (v4 or v6) which in turn is reachable via a Labelled IGP/MPLS path
is sent with incorrect label.
For example, IPaddress1--->nexthopIPaddress2-->MPLS Label (IGP)-->outgoing interface
In this case, since IPaddress1 is recursively reachable over another IPaddress2 which in turn is
reachable from a Labelled IGP path, in such a case, incorrect labels
can be pushed on the outgoing packet because of this issue.
Conditions:
- ASR9000 routers should be running release 4.2.0 or 4.2.1 release.
- Traffic should be going to a IP address
such as "IPaddress1" described above.
- Its only applicable to Trident and Typhoon based linecards
Workaround:
None
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 03-JUN-2015 |
|
Known Affected Releases: | 4.2.0.BASE, 4.2.1.BASE |
|
Known Fixed Releases: | 4.2.3.27i.BASE, 4.3.0.26i.BASE |
|
|
| |
| |
Bug Id: | CSCuu58858 |
Title: | fpd upgrade fails and node runs golden version |
|
Description: | Symptom:
fpd upgrade fails
Conditions:
asr9k router running 532 interim imgae
Workaround:
none
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 5.3.2.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCun90088 |
Title: | ASR9K Egress EFP filtering + ACL/QOS fails |
|
Description: | Symptom:
If EFP filtering is enabled, then egress ACLs or QoS policies which match on IP address may fail to properly match on the IP address field.
Conditions:
ACL or QoS policy which matches on IP address (src or dest if IPv4, src if IPv6) will fail to match if applied in the egress direction to a port with EFP filtering.
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 4.2.3.BASE, 4.3.0.BASE, 4.3.1.BASE, 4.3.2.BASE, 4.3.4.BASE, 5.1.0.BASE, 5.1.1.TOOLS, 5.1.2.TOOLS, 5.2.0.TOOLS, 5.2.2.BASE |
|
Known Fixed Releases: | 5.1.3.6i.BASE, 5.2.0.21i.BASE |
|
|
| |
| |
Bug Id: | CSCuh88082 |
Title: | 510-SIT: Ingress LC doesn't punt BLB SH BFD packets to host LC correctly |
|
Description: | Symptom:
BLB sessions does not come up when bfd_agent host is hosted on a different LC than the bundle interface
Conditions:
With CSCud77196 fix all BFD packets received with NOT_MY_MAC address. Since BLB packets can also have a different mac address than that of the receiving interface all BLB packets are punted to local LC. So when bfd_agent is hosted on a different LC then BLB sessions will never come up
Workaround:
None.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 4.3.2.BASE, 5.1.0.BASE, 5.1.1.BASE, 5.2.0.BASE |
|
Known Fixed Releases: | 4.3.2.27i.BASE, 4.3.2.27i.FWDG, 5.1.0.16i.BASE |
|
|
| |
| |
Bug Id: | CSCtn87461 |
Title: | cpp_ucode crashed on a SIP-700 LC during router bootup |
|
Description: | Symptom:
cpp ucode crash on a SIP-700 LC
Conditions:
router bootup
Workaround:
none
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 4.0.1.BASE, 4.1.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCuh48634 |
Title: | LPTS entry incorrectly programmed causing protocols not to receive data |
|
Description: | Symptom:
Protocols which have optimized entry in the LPTS might not receive the traffic.
Examples of protocols are PIM, IGMP, OSPF.
Conditions:
This is a timing issue and might happen after the changes on the device.
Workaround:
Restart the protocol impacted.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 4.3.4.BASE, 5.1.0.BASE |
|
Known Fixed Releases: | 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.0.15i.BASE |
|
|
| |
| |
Bug Id: | CSCuq07432 |
Title: | Ingress SPAN and ABF pointing to egress BVI can cause NP lockup |
|
Description: | Symptom:
Possible to see NP lockup reported and causing NP fast reset on Typhoon based linecards.
Example:
LC/0/3/CPU0:Jun 18 00:15:50.257 GMT: pfm_node_lc[287]: %PLATFORM-NP-2-NP_DIAG : Set|prm_server_ty[176210]|Network Processor Unit(0x1008002)| NP diagnostics warning on NP2.
LC/0/3/CPU0:Jun 18 00:16:06.910 GMT: prm_server_ty[297]: %PLATFORM-NP-4-FAULT : Fast Reset NP2 - successful auto-recovery of NP
LC/0/3/CPU0:Jun 18 00:16:06.910 GMT: pfm_node_lc[287]: %PLATFORM-NP-2-NP_DIAG : Clear|prm_server_ty[176210]|Network Processor Unit(0x1008002)| NP diagnostics warning on NP2.
Conditions:
This has been seen with SPAN on ingress direction with ABF configured where the nexthop interface is a BVI. Sending packets at or near the MTU of the BVI can cause the lockup.
In the NPdatalog written you will see RSV_PUNT_IP_MTU_EXCEEDED.
Workaround:
Increase the BVI MTU so that it's larger than ingress interfaces. Or remove SPAN
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 4.3.4.BASE, 4.3.4.LC |
|
Known Fixed Releases: | 4.3.4.SP4, 4.3.4.SP5, 4.3.4.SP6, 4.3.4.SP7, 5.1.3.18i.BASE, 5.1.4.1i.BASE, 5.2.2.21i.BASE, 5.2.3.8i.BASE, 5.3.0.5i.BASE |
|
|
| |
| |
Bug Id: | CSCuq20496 |
Title: | ipv6 linklocal ping and gobal ping not working on bvi interface |
|
Description: | Symptom:
BVI v6 sessions fail on ASR9K chassis with EP based Modular LCs and ASR9001 board.
Conditions:
The issue is observed on a ASR9K chassis that hosts only MOD LCs (EP based LC) or on a ASR9001 board.
The IOS-XR version is 5.1.0, 5.1.1, 5.1.2, 5.1.3, 5.2.0.
Workaround:
Attempt restarting the "ipv6_nd" process on the RP.
If this does not work, try reloading the MOD LC on the ASR9K chassis or reload the LC on the ASR9001.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 5.1.0.BASE, 5.1.1.BASE, 5.1.2.BASE, 5.1.3.BASE, 5.2.0.BASE, 5.2.2.ADMIN |
|
Known Fixed Releases: | 5.1.3.SP2, 5.1.3.SP3, 5.1.3.SP4, 5.2.2.24i.BASE, 5.2.3.8i.BASE, 5.3.0.10i.BASE |
|
|
| |
| |
Bug Id: | CSCuu67391 |
Title: | macsec session stuck in INIT state on 40-gig interface |
|
Description: | Symptom:
remove/add macsec from single tag to double tag interface with 2 interfaces commit at once
Conditions:
Macsec stuck in INIT state
Workaround:
disable/enable on any one interface of double tagged interface, macsec session on all 5 sub interfaces will come up.
Further Problem Description:
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 04-JUN-2015 |
|
Known Affected Releases: | 6.0.0.BASE |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCul57104 |
Title: | Defensive mechanism for invalid PSID to protect TM |
|
Description: | Symptom:
In rare conditions the NP may halt and need to be restarted.
LC/0/9/CPU0:Sep 17 13:43:52.050 : prm_server_ty[304]: %PLATFORM-NP-4-FAULT : Fast Reset NP1 - successful auto-recovery of NP
LC/0/9/CPU0:Sep 17 13:43:52.050 : pfm_node_lc[294]: %PLATFORM-NP-2-NP_DIAG : Clear|prm_server_ty[168016]|0x1008001| NP diagnostics warning on NP1.
Conditions:
The use of MOD-80 LC with the 4x10Gig EP plug
BVI and core mpls flaps when BFD is configured
Apart from the fix to BFD issue, a fix also went to add general class of protection to Mod 80.
Workaround:
Further Problem Description:
This is a defensive fix to avoid NP halts due to packets being sent through the TM with an invalid internal Port ID. This resolves the issue specifically for the Mod80 linecard.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-JUN-2015 |
|
Known Affected Releases: | 4.2.3.LC |
|
Known Fixed Releases: | 4.3.2.SP7, 5.1.2.14i.BASE, 5.2.0.6i.BASE |
|
|
| |
| |
Bug Id: | CSCus34978 |
Title: | MIRROR_DISABLE=Y on rommon causes disk instability. |
|
Description: | Symptom:
RSP disk get corrupted.
Conditions:
RSP with rommon variable MIRROR_DISABLE=Y, and try to configure disk mirroring will cause the disk to get corrupted.
Workaround:
Remove the rommon variabile or turboboot.
Further Problem Description:
The following errors will be display:
RP/0/RSP0/CPU0:ios(config)#mirror location 0/RSP0/CPU0 disk0: disk1:
RP/0/RSP0/CPU0:ios(config)
|
没有评论:
发表评论